In bug 510505, shaver proposes allowing client code to store and send "skidmark" values along with the crash report. These would be simple pointer values as integers. This would let client code record potentially useful information in tricky bits of code (like cycle collection classes, or JIT-related info). We'll clearly need to be able to collect and display this info in crash reports to make it useful. I'll propose that the client will send up to 4 values, with names Skidmark{1,2,3,4}, values to be decimal integers (potentially up to 64 bits). The collector should collect these, and display them in individual report pages as decimal and hexadecimal, as a start. Displaying them as symbol+offset will be impossible with our current setup, so I'll file a followup bug on that.

Talked to Ted, there are better tools now, so WONTFIX