On Sat, 2006-03-25 at 12:38 -0700, Steve wrote: > I'm just looking for troubleshooting ideas, like where I might want to > start looking the code base is over 50 MBs of C++ and I'm only now > just familiarizing myself. > Sadly since it is a closed source app I can't use the many eyes > approach, but I'm hoping there is a clue somewhere that can let me > know where the memory is getting corrupted.
Probably you'll want to run valgrind. Valgrind can detect these types of double-free situations (very common errors in C and C++). Michael > > Any tips, tricks, ideas, thoughts etc would be greatly appreciated. > > /* > PLUG: http://plug.org, #utah on irc.freenode.net > Unsubscribe: http://plug.org/mailman/options/plug > Don't fear the penguin. > */ > /* PLUG: http://plug.org, #utah on irc.freenode.net Unsubscribe: http://plug.org/mailman/options/plug Don't fear the penguin. */
