[sldev] Just askin': How are we doing?
dale at daleglass.net
dale at daleglass.net
Mon Jun 25 06:00:45 PDT 2007
On Mon, Jun 25, 2007 at 02:51:59PM +0200, Nicholaz Beresford wrote:
> Access to the crash logs: Maybe I'm the only one who's looking at
> crashes instead of doing Sudoku, but I think it's beyond the time
> where the stack dump alone will help fixing crashes (at least for the
> top 10). I think crash reports will go back by an order of magnitue
> with the leak fixed (at least that's what I'm hearing from people
> using my viewer) but they will most likely become more and more
> obscure (which again, it is what I'm seeing from the crash dumps
> from my viewer). Dunno how to approach this exactly, but it's
> something I noticed.
That would be nice indeed. A stack trace shouldn't contain anything very
private. Only potential problem is the arguments to the functions, if
the stacktrace sent includes that (haven't looked at it). This could
contain passwords or something else that's sensitive.
Short term fix would not giving that info at all, but that makes
debugging harder. Perhaps there could be some sort of blacklist with
functions that take sensitive data to have it scrubbed, but something
could be missed.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.secondlife.com/pipermail/sldev/attachments/20070625/2fb3a13f/attachment-0001.pgp
More information about the SLDev
mailing list