[sldev] JIRA: Blockers (crash after login)]

Nicholaz Beresford nicholaz at blueflash.cc
Wed Jun 20 01:55:18 PDT 2007



I'm doing the crash report thing with the users of
my version.   The normal crash reports LL is using
have probably outlived their usefulness because they
show only where the crash happens with the stack
(see the Wiki or JIRA).

This IS helpful for simple situations, like not
checking for a null pointer before doing something,
but even if someone loaded them into a debugger and
spent time on them, they just show the stack, the
registers and that was it (you're lucky if you get
a variable occacsionally).

I'm justing the crash logger with MediumDumps (2MB-
8MB)and even there it is hard and time consuming.


Someone with a reproduceable hard crashe is usually
an excellent source for bug swatting, but it takes
time and dedication to do so.


Nick


Second Life from the inside out:
http://nicholaz-beresford.blogspot.com/





More information about the SLDev mailing list