Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Date:	Sat, 02 Oct 2004 12:15:43 +0400
From:	Maarten Boekhold <boekhold AT emirates DOT net DOT ae>
Subject:	Memory debugging under cygwin
To:	cygwin AT cygwin DOT com
Message-id:	<415E63AF.30403@emirates.net.ae>
MIME-version:	1.0
User-Agent:	Mozilla Thunderbird 0.8 (Windows/20040918)
X-IsSubscribed:	yes

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/

- Raw text -