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 sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com Message-ID: <20000607200636.3839.qmail@web125.yahoomail.com> Date: Wed, 7 Jun 2000 13:06:36 -0700 (PDT) From: Earnie Boyd Reply-To: earnie_boyd AT yahoo DOT com Subject: Re: Bad address To: cygwin-developers AT sourceware DOT cygnus DOT com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii --- Chris Faylor wrote: > On Wed, Jun 07, 2000 at 12:52:54PM -0700, Earnie Boyd wrote: > >I found the bug in texinfo-4.0. :) However, a call to perror is causing the > >associated output of "Bad address". I didn't see anything obvious with > perror, > >but I also haven't gotten down to the puts and putc calls either. The data > >types being passed from texinfo to perror are declared as char * so I'm > >assuming this has to do with the REENT portion of the function. > > I believe that this error was discussed in cygwin or cygwin-developers a > month or two ago. Someone had a patch that was rejected by the texinfo > maintainer. I wasn't trying to report the texinfo bug, I was trying to report the perror bug which is a function existing in the newlib/libc/stdio/perror.c file. I'll see if I can work up a simple test program that exhibits the problem. Regards, ===== --- Earnie Boyd: __Cygwin: POSIX on Windows__ Cygwin Newbies: __Minimalist GNU for Windows__ Mingw32 List: Mingw Home: __________________________________________________ Do You Yahoo!? Yahoo! Photos -- now, 100 FREE prints! http://photos.yahoo.com