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
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
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
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
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
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:
- d
6 matches
Mail list logo
