Tue Apr 2 10:31:00 GMT 2002
On Tue, Apr 02, 2002 at 10:24:11AM -0500, Earnie Boyd wrote:
>Christopher Faylor wrote:
>> On Tue, Apr 02, 2002 at 07:44:25AM -0500, Earnie Boyd wrote:
>> >In my modifying Cygwin source for MSYS I began having issues with malloc
>> >and the offending pieces being within this source. I noticed that the
>> >HAVE_MMAP macro was set to 0 by default instead of 1 by default as
>> >Dave's documentation says that it does. Modifying the macro value to 1
>> >caused all of the problems I was experiencing to disappear.
>> >Do other Cygwin developers see benefit for a patch to newlib?
>> Can you describe the problem? I guess it's possible that allowing this code
>> would fix the out-of-memory heap issues we continually have but, the last time
>> I benchmarked this, using mmap had a performance hit. This was on UNIX but
>> I can't imagine it isn't the same on cygwin.
>I would get segmentation faults within mallocr.c. The first time it
>occurred was the originating call was within the code I was adding. I
>modified the code a bit and that caused the malloc's in environ.cc to
>issue the segmentation faults in mallocr.c. If you need to know exactly
>where in mallocr.c that was causing the problem I can most likely
>reproduce it to get the failure point.
SEGVs are invariably a sign of attempts to free memory that hasn't been
More information about the Cygwin-developers