Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
Message-Id: <199902231624.KAA04714@modi.xraylith.wisc.edu>
X-Authentication-Warning: modi.xraylith.wisc.edu: localhost.xraylith.wisc.edu [127.0.0.1] didn't use HELO protocol
To: "Morgan D. Jones" <mjones AT pobox DOT com>
cc: cygwin mailing list <cygwin AT sourceware DOT cygnus DOT com>
Subject: Re: nt fclose() question... 
In-reply-to: Your message of "Tue, 23 Feb 1999 10:48:35 PST."
             <36D2F803 DOT 53E7DDAF AT pobox DOT com> 
Date: Tue, 23 Feb 1999 10:24:47 -0600
From: Mumit Khan <khan AT xraylith DOT wisc DOT EDU>

"Morgan D. Jones" <mjones AT pobox DOT com> writes:
> hi all...
> 
> i've looked (not exhaustively) for an answer to this question, to no
> avail...
> I had a ANSI C console program on a mac that I wanted to port to NT...
> 
> First I moved it to Linux and got it to work with gcc there...
> (basically no modifications)
> I then moved it to NT running cygwin 20.1...
> 
> now I get a STATUS_ACCESS_VIOLATION when I perform an fclose()??  Mind
> you this code worked fine under linux and Metrowerks C on a power Mac...

More often than not, this type of access violation error typically arise 
due to a memory corruption bug in user's code. Please understand that
just because a piece of code runs under a few systems, doesn't mean that
it doesn't have bugs.

Here's my suggestion: use a memory debugger and see if your code is clean.
If it is, then it's possibly a bug in Cygwin or newlib (C library); please 
see if you can put together a bug report that we can look at.

Since you have access to Linux, you can use ElectricFence to see if it
catches anything. You can find prebuilt RPMs in various sites (search
in http://www.rpmfind.net/).

Regards,
Mumit


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com