STEPS TO REPRODUCE: 1. Crash, e.g. by loading the testcase on bug 537157 2. View crash report ACTUAL RESULTS: Crash report has no stack info, and instead says: { /home/processor/stackwalk/bin/stackwalk.sh returned no header lines for reportid: 82210745; No thread was identified as the cause of the crash; No signature could be created because we do not know which thread crashed; /home/processor/stackwalk/bin/stackwalk.sh returned no frame lines for reportid: 82210745; /home/processor/stackwalk/bin/stackwalk.sh failed with return code 1 when processing dump 7a60ccc9-dfe0-4ab7-a5f9-fd2fa2091229 } http://crash-stats.mozilla.com/report/index/7a60ccc9-dfe0-4ab7-a5f9-fd2fa2091229 NOTES: I'd thought that this issue was fixed with ted's backout in bug 514188 Comment 25, but apparently something's still broken... I did get at least one good stack report since that backout -- on 12-21: http://crash-stats.mozilla.com/report/index/bp-2fcf90b2-a807-41b0-b79d-558e82091221 So, maybe something else broke after the backout?

Just confirmed this with "Crash Me Now" extension, using the "null deref crash" option. http://crash-stats.mozilla.com/report/index/b278a47a-3628-4f52-8318-a46dd2091229

(in comment 1, by "confirmed this" I meant "confirmed that this is a general issue rather than a special-case issue with bug 537157's testcase")

This is likely to be fixed by bug 514188, actually. I think the existing Linux client code is not very good, and the rewrite is much better. I'm going to reland that ASAP.

(In reply to comment #3) > This is likely to be fixed by bug 514188, actually. That landed yesterday and appears to have fixed it. I just tested bug 537157's crash with nightlies from yesterday & today, and yesterday's exhibited the bug: http://crash-stats.mozilla.com/report/index/b215c368-0647-4235-b283-d537d2100105 while today's is fine: http://crash-stats.mozilla.com/report/index/1a7b6e28-df99-4b21-8af6-5375c2100105 Resolving as FIXED by bug 514188.