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 From: Chris Faylor Date: Wed, 7 Jun 2000 15:57:08 -0400 To: cygwin developers Subject: Re: Bad address Message-ID: <20000607155708.B16397@cygnus.com> Reply-To: cygwin-developers AT sourceware DOT cygnus DOT com Mail-Followup-To: cygwin developers References: <20000607195254 DOT 1341 DOT qmail AT web125 DOT yahoomail DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000607195254.1341.qmail@web125.yahoomail.com>; from earnie_boyd@yahoo.com on Wed, Jun 07, 2000 at 12:52:54PM -0700 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. cgf