This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Memory debugging under cygwin


Maarten Boekhold schrieb:
Dan Osborne wrote:
Could you get the test program to work? That shows how it wants to play.

The only problem I found with it was that it wouldn't follow shared objects.


Yeah, that seems to be the problem I have to. Unfortunately the memory corruption I'm looking for is *in* a shared object. And compiling the whole app static isn't an option, because it also involves a dynamically loaded module :(

Great shame that valgrind isn't ported to cygwin!

but dmalloc is. after libtoolizing and autoreconf with latest autotools just add AM_WITH_DMALLOC to your configure.in

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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]