delorie.com/archives/browse.cgi | search |
Mailing-List: | contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm |
List-Subscribe: | <mailto:cygwin-developers-subscribe AT sourceware DOT cygnus DOT com> |
List-Archive: | <http://sourceware.cygnus.com/ml/cygwin-developers/> |
List-Post: | <mailto:cygwin-developers AT sourceware DOT cygnus DOT com> |
List-Help: | <mailto:cygwin-developers-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs> |
Sender: | cygwin-developers-owner AT sourceware DOT cygnus DOT com |
Delivered-To: | mailing list cygwin-developers AT sourceware DOT cygnus DOT com |
Message-ID: | <20000607195254.1341.qmail@web125.yahoomail.com> |
Date: | Wed, 7 Jun 2000 12:52:54 -0700 (PDT) |
From: | Earnie Boyd <earnie_boyd AT yahoo DOT com> |
Reply-To: | earnie_boyd AT yahoo DOT com |
Subject: | Re: Bad address |
To: | cygwin developers <cygwin-developers AT sourceware DOT cygnus DOT com> |
MIME-Version: | 1.0 |
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. Cheers, ===== --- Earnie Boyd: <mailto:earnie_boyd AT yahoo DOT com> __Cygwin: POSIX on Windows__ Cygwin Newbies: <http://www.freeyellow.com/members5/gw32/index.html> __Minimalist GNU for Windows__ Mingw32 List: <http://www.egroups.com/group/mingw32/> Mingw Home: <http://www.mingw.org/> __________________________________________________ Do You Yahoo!? Yahoo! Photos -- now, 100 FREE prints! http://photos.yahoo.com
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |