X-Spam-Check-By: sourceware.org Message-ID: <462E7390.3DC65869@dessent.net> Date: Tue, 24 Apr 2007 14:16:00 -0700 From: Brian Dessent X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) MIME-Version: 1.0 To: cygwin AT cygwin DOT com Subject: Re: Can I tell which version of newlib I have? References: <462E734D DOT F08DE9A AT dessent DOT net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Reply-To: cygwin AT cygwin DOT com Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list 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/