Re: Memory debugging -- which tool?

2007-12-14 Thread Murray Cumming
On Fri, 2007-12-14 at 14:18 +1100, Michael Lamothe wrote: > Valgrind for most of it. However, be warned, if you have a > multi-threaded application and you're trying to debug a > multi-threading issue, Valgrind is not going to work for you. > Valgrind does some hocus-pocus to simulate multi-thread

Re: Memory debugging -- which tool?

2007-12-13 Thread Michael Lamothe
Valgrind for most of it. However, be warned, if you have a multi-threaded application and you're trying to debug a multi-threading issue, Valgrind is not going to work for you. Valgrind does some hocus-pocus to simulate multi-threading, but you will not get the same conditions as when your applica

Re: Memory debugging -- which tool?

2007-12-13 Thread jcupitt
On Dec 13, 2007 9:25 AM, Dan H <[EMAIL PROTECTED]> wrote: > I'm trying to use valgrind to track down this issue; however, this slows down > my app to the point where it takes close to a minute for the GUI to start up, > and then another minute to get to the crash. I've used ccmalloc with good >

Memory debugging -- which tool?

2007-12-13 Thread Dan H
Hello, I've written some C code which at some point seems to be trampling over memory that belongs to GTK-related stuff, which causes erratic crashed at some unrelated point much later. This is of course not a GTK issue, just a well-known phenomenon in general. I'm trying to use valgrind to tr