Brian Dessent wrote:
Brian Dessent wrote:
The version you are using is whatever was current in CVS when the
version of Cygwin you're using was built. Newlib doesn't really do
versions, other than a token release every year around December.
But that's completely irrelevant for anything relating to malloc, as
Cygwin does not use newlib for malloc.
Oh and as for the second part of the question, here is a quote from
how-to-debug-cygwin.txt:
7. Heap corruption
If your program crashes at malloc() or free() or when it references
some
malloc()'ed memory, it looks like heap corruption. You can configure
and
build special version of cygwin1.dll which includes heap sanity
checking.
To do it, just add --enable-malloc-debugging option to configure. Be
warned,
however, that this version of dll is _very_ slow (10-100 times slower
than
normal), so use it only when absolutely necessary.
Brian
Brian,
It was my understanding that if I write a C program and compiled it with
gcc that gcc used newlib for all of the stdlib functions including
malloc, realloc and free.
Ray
--
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/
