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
From:	"Dan Osborne" <dan DOT osborne AT ramesys DOT com>
To:	<cygwin AT cygwin DOT com>
Subject:	RE: Memory debugging under cygwin
Date:	Sat, 2 Oct 2004 13:31:55 +0100
Message-ID:	<MLECJOCAOOEMHIHMOACLKELLCCAA.dan.osborne@ramesys.com>
MIME-Version:	1.0
In-Reply-To:	<415E63AF.30403@emirates.net.ae>
X-Ramesys-Professional-Services-MailScanner-Information:	Please contact the ISP for more information
X-Ramesys-Professional-Services-MailScanner:	Found to be clean
X-Ramesys-Professional-Services-MailScanner-SpamCheck:	not spam (whitelisted), SpamAssassin (score=-0.8, required 5, IN_REP_TO -3.38, UNSUB_PAGE 2.59)
Note-from-DJ:	This may be spam

There's a package called Memory Watcher/memwatch designed for cygwin which
I've used.

I can't find a URL but this is from the README and a web search should find
it ...

Memory Watcher
==============

This is a little library for tracing memory related api calls on cygwin
using gcc.

Features:
- detection of unfree'd memory regions
- traces each malloc(), calloc(), realloc() and free() call
- collects size and addresses of allocated area
- runtime switchable logging support of hooked function

Dan

-----Original Message-----
From: cygwin-owner AT cygwin DOT com [mailto:cygwin-owner AT cygwin DOT com]On Behalf
Of Maarten Boekhold
Sent: 02 October 2004 09:16
To: cygwin AT cygwin DOT com
Subject: Memory debugging under cygwin


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/
---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.768 / Virus Database: 515 - Release Date: 22/09/2004

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.768 / Virus Database: 515 - Release Date: 22/09/2004


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