On Sat, 02 Aug 2008 11:41:26 +0100
Richard Porter <ricp(a)minijem.plus.com> wrote:
I've had numerous occasions on which NetSurf has spontaneously
crashed when I've tried to quit it or shut down the system or when
I'm doing something else altogether. It's very difficult to give very
much contextual information, but the log should give you some idea of
what ultimately caused the crash (usually but not always a
segmentation fault), what pages were last visited, what objects were
last requested and what various registers were pointing to.
Sure, but often they're huge and nearly impossible to extract that soft
of information out of usefully. Knowing which site you were visiting
is fabulously useful. The developers know what's useful to them, and
just the log is not.
I agree that the tracker is the place to report such problems despite
it's irritating login problems. However apart from the management
capabilities it provides, including the ability to add further
information, it's not really that different from an email message
with a subject (summary), body (description) and attachment (log). In
fact email doesn't normally choke on attachments over 300 kBytes!
It's very different from an email message, for reasons we've discussed
at length already.
(Incidentally, I hope to get started in Lurgi, our new BTS, this
weekend. I'll be developing it with NetSurf in mind and testing it
almost exclusively with NetSurf in the hope we can abandon the last of
SourceForge's functionality that we use.)