Yea that is one of the worst things about memory leaks is waiting on a crash from it, which it can take awhile since you have to wait on the memory to leak bad enough to cause issues. Then half the time the actual crash is else where and doesn't point to where the actual leak is lol.

That's why, if you really believe it's a memory leak, valgrind's a better tool than gdb, but if you don't know what you're doing with valgrind.. well, it's a complex tool too.

Pee Ess I'm fairly certain they didn't mean don't code at all until it crashes, just don't recompile after it dumps the core until you've had
a chance to gdb =P

I msn'd you the same thing.

Well even editing the source files can make a core file give you incorrect data. Sad but true it seems. If your not getting crashes like once a day or something though you might as well continue on until they become more annoying to bother with. Why wait a week or two for a crash when you could have gotten a lot done in that time.

Just after you get the changes in how you want and your going to log out for the day go ahead and do a reboot so its running a good fresh run so if it crashes while your not around you have a good core to use when you get back on.

Okay, I think I'll be doing that then...would hate to slow down on fixing things up when I really only just got started doing them. heh