This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Can I tell which version of newlib I have?
- From: Brian Dessent <brian at dessent dot net>
- To: cygwin at cygwin dot com
- Date: Tue, 24 Apr 2007 14:16:00 -0700
- Subject: Re: Can I tell which version of newlib I have?
- References: <f0lqsf$pp1$1@sea.gmane.org> <462E734D.F08DE9A@dessent.net>
- Reply-to: cygwin at cygwin dot com
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
--
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/