Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com Date: Sat, 17 Feb 2001 13:30:15 -0500 From: Christopher Faylor To: cygwin-developers AT cygwin DOT com Subject: Re: mktime() seting errno ?? Message-ID: <20010217133014.A32369@redhat.com> Reply-To: cygwin-developers AT cygwin DOT com Mail-Followup-To: cygwin-developers AT cygwin DOT com References: <20010216224954 DOT B19214 AT redhat DOT com> <000001c098f5$a863dbe0$a300a8c0 AT nhv> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <000001c098f5$a863dbe0$a300a8c0@nhv>; from nhv@cape.com on Sat, Feb 17, 2001 at 10:24:00AM -0500 On Sat, Feb 17, 2001 at 10:24:00AM -0500, Norman Vine wrote: >Christopher Faylor writes: >> >>On Fri, Feb 16, 2001 at 09:55:07PM -0500, Norman Vine wrote: >>>The attached test program demonstrates this. >>>I have looked at the mktime source in newlib >>>and can not see why this should be happening ? >> >>Have you debugged the problem in gdb? It should be fairly easy >>to figure out what is going on. > >Yes I have stepped thru this in gdb >And it wasn't 'obvious' to me how to find out >how errno was even being touched. Do a "display impure_ptr->_errno" (or whatever errno translates to) and step into mktime. You should be able to see which instruction changes errno. cgf