Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Sat, 02 Oct 2004 12:15:43 +0400
From: Maarten Boekhold <boekhold@emirates.net.ae>
Subject: Memory debugging under cygwin
To: cygwin@cygwin.com
Message-id: <415E63AF.30403@emirates.net.ae>
MIME-version: 1.0
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7BIT
User-Agent: Mozilla Thunderbird 0.8 (Windows/20040918)

Hi all,

I have a program that segfaults, and it's quite obvious that this is 
caused due to some memory corruption. Except it segfaults at a place 
where, if running it in gdb, there shouldn't be a problem. There seems 
to be some memory corruption somewhere, and I can't figure out where.

I tried linking the app with dmalloc, but I can't get it to generate a 
log file, even if I explicitly request one by including calls to the 
dmalloc library in the application. Valgrind doesn't seem to be 
available on cygwin either.

Can anybody recommend a way to debug this sort of error? Are there any 
other memory debuggers available that work with cygwin?

Maarten

--
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/