Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Date: Tue, 24 Jul 2001 22:31:09 +0200 From: Kurt Roeckx To: Larisa A Stephan Cc: cygwin AT cygwin DOT com Subject: Re: 1.3.2 bug on NT 4: localtime() & timestring() set errno on success Message-ID: <20010724223108.A4550@ping.be> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: On Tue, Jul 24, 2001 at 11:41:26AM -0700, Larisa A Stephan wrote: > I notice that localtime() and timestring() tend to set errno to 0x2 even > though they succeed (return a non-NULL pointer). I THINK this is a bug, > but maybe someone can correct me. I checked the archives and found one > mention of this issue, but no one followed up to tell the guy he was nuts, > so maybe it is really a bug. They themself are no system calls, but probably do call system calls. Any of the system calls it might have called could have change errno. My guess is that it's trying to open some file, but didn't find it. Kurt -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/