Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Date:	Fri, 10 Dec 2004 15:36:34 -0800
From:	Lester Ingber <ingber AT ingber DOT com>, Lester Ingber <ingber AT ingber DOT com>
To:	cygwin AT cygwin DOT com, cygwin AT cygwin DOT com
Subject:	Re: cygwin-gcc-fopen bug?
Message-ID:	<20041210233633.GA5428@ingber.com>
Mime-Version:	1.0
User-Agent:	Mutt/1.4.1i

Jim:

Hi.   On Solaris9 I use leak and there are no leaks, and I see no errors
at all.

One of the errors on Cywin, using the most Current Cygwin1.dll occurs
before any memory is created, ner the top of main():
  if ((Portfolio->ptr_err = fopen (infoFile, "a")) == NULL) {
     ...

Now, I do have a large set of structs (mostly full of pointers for
memory to be created later in the program), e.g., several enum's with
about 40 entries, and several nested structs with about 225 entries,
in an include file common to about 50 .c files.  Could this be too
many for the Cygwin gcc default?

BTW, it is "NULL" that mangles the filename, not "NUL", likely
because I'm using sprintf() to string together paths and files.

Thanks.

Lester


-- 
 Prof. Lester Ingber  lester AT ingber DOT com  ingber AT alumni DOT caltech DOT edu
 www.ingber.com                     www.alumni.caltech.edu/~ingber

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -