Queries about stack traces

[birdy]

The 4.11.1 beta lost connection for me sometime during the night (so I'm not sure when). Ran for 13 hours continuously before that without a problem, pretty much constant uploads but only 3 downloads.

Sam (or anyone), if you could answer a few queries I have about stack traces then I might be able to give you some better feedback. See my thread here
http://www.gnutellaforums.com/showthread.php?t=56507

I don't really know what I'm doing.

Thanks!

[Sam]

Full stack traces are very hit or miss. In a few scenarios, they'll be a tremendous help at pinpointing what went wrong, but in the vast majority they won't be useful. The same goes with logging -- most logging after the fact won't help, but logging while a problem is happening (if the logging is in the right package) is usually invaluable. It's difficult, because running with too much logging can slow things down, but you have no clue when bugs are going to happen... What I tend to do is try and create problematic scenarios, but make sure that logging is on first.

The absolute most useful thing is the error that goes along with an internal error. If there's no error dialog, though, the bugs are a lot harder to diagnose. Good detective work and an eye for noticing, "If I do this, that happens" is usually best.