“skid mark”
by Christopher Blizzard
A new phrase that I learned yesterday. Probably something that’s been around computers for a long time, but it was my first exposure to it.
Basically a “skid mark” is something you leave in code as a signature so that in a crash dump you can figure out how you got there.
We’ve been doing a huge amount of work in Firefox 3.5 and 3.6 to reduce the number of crashes. For some crashes we have stack traces, but not a lot of data on how we got to that stack. So we’re actually checking in code changes and and shipping them into the wild to see how they change crash signatures.
The interesting thing is that it’s working – we’ve been able to track down some pretty serious crashes with this technique.
I’ve always called them “breadcrumbs” but I think I like “skid marks” better.
This sounds more sophisticated than the usual “dump warnings to the terminal when things start to go downhill” approach. Can you elaborate on the technique?
i thought skid mark has been used for something totally else:
http://www.urbandictionary.com/define.php?term=skid+mark
Is there any chance you will fix the nasty database bug that causes a traceless crash every single time you open the History sidebar? Surely you can search and display an sql table while it is updated? No? Disable the updates until the sidebar closes?
Grumpy!
Do you know if there’s a bug open on that?
I assume so as many others reported the same – “clean” crash with no error message, no coredump, but tabs restored on restarting. It is described by several here http://ubuntuforums.org/showthread.php?t=1257910
The solution given is to not use the history sidebar. The fault is replicated soon after opening the history sidebar.
My favorite skid mark usually involves some permutation of 0xdeadbeef.