Re: Memory debugging under cygwin

2004-10-11 Thread Reini Urban
Dan Osborne schrieb: Reini Urban wrote: 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 Hmmm, I've yet to bite the libtool bullet but if it gets dmalloc working maybe nows the tim

RE: Memory debugging under cygwin

2004-10-11 Thread Dan Osborne
Reini Urban wrote: >>> 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 Hmmm, I've yet to bite the libtool bullet but if it gets dmalloc working maybe nows the time to do

Re: Memory debugging under cygwin

2004-10-08 Thread Reini Urban
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

Re: Memory debugging under cygwin

2004-10-07 Thread Maarten Boekhold
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 c

Re: Memory debugging under cygwin

2004-10-02 Thread Reid Thompson
splint is available via setup also. www.splint.org Maarten Boekhold wrote: 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 b

RE: Memory debugging under cygwin

2004-10-02 Thread Dan Osborne
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

Memory debugging under cygwin

2004-10-02 Thread Maarten Boekhold
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