Closed
Bug 601114
Opened 14 years ago
Closed 14 years ago
update minidump_stackwalk in Socorro production to latest Breakpad SVN (r704)
Categories
(mozilla.org Graveyard :: Server Operations, task)
mozilla.org Graveyard
Server Operations
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: ted, Assigned: jabba)
References
Details
I landed some stackwalker fixes in Breakpad for bug 571578 (which is a Firefox 4 blocker). We need to update the production minidump_stackwalk binaries to the latest Breakpad SVN (r704 or newer) to pick these changes up.
Updated•14 years ago
|
Assignee: server-ops → jdow
Assignee | ||
Comment 1•14 years ago
|
||
I updated this in staging. Can I get a verification that everything is working before I push to production?
Comment 2•14 years ago
|
||
Chofmann, do you know how to verify this?
Comment 3•14 years ago
|
||
ted should say for sure, but verifying that we get good stacks out of 64-bit Linux and OS X seems like what is going on in bug 571587. I'd say this bug is only about landing those changes and the verification should be done over there.
some sample reports from 64 bit OSes could be run through the processor to verify on stage. I think lars does this kind of testing of feeding the processor, but I don't know if we have a sample of reports from 64 bit systems.
Reporter | ||
Comment 4•14 years ago
|
||
I can try verifying this on stage tomorrow. Should be enough to submit a crash using "Crash me now!" on Linux64 or Mac64 and look at the full thread list. Without this change the non-crashing threads would probably all have just one frame, in some system library. With this change we should have a few more frames.
Reporter | ||
Comment 5•14 years ago
|
||
I submitted a report to stage but it seems to be hung up:
http://crash-stats.stage.mozilla.com/report/pending/0d143352-c3d7-42b1-b1c0-a7c022101006
There's some error message in there, perhaps processing on stage is busted?
Comment 6•14 years ago
|
||
(In reply to comment #1)
> I updated this in staging. Can I get a verification that everything is working
> before I push to production?
Don't push it until we sort out these issues on staging, please, thanks Jabba!
Reporter | ||
Comment 7•14 years ago
|
||
Ok, this looks good in staging! Compare:
https://crash-stats.mozilla.com/report/index/a48afce6-c7d4-45a0-91eb-853b52101006
http://crash-stats.stage.mozilla.com/report/index/ae4a83f0-9364-40ab-ae41-4dce42101006
Specifically, click "Other threads" and note the length of the stack traces.
Assignee | ||
Comment 8•14 years ago
|
||
I updated production.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Reporter | ||
Comment 9•14 years ago
|
||
Looks good in production:
http://crash-stats.mozilla.com/report/index/bp-3bd4810d-79da-478e-99bc-9e5572101006
Thanks!
Status: RESOLVED → VERIFIED
Updated•10 years ago
|
Product: mozilla.org → mozilla.org Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•