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: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Maarten Boekhold Sent: 02 October 2004 09:16 To: [EMAIL PROTECTED] 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/
