update breakpad processor code on production to revision 226

RESOLVED FIXED

Status

mozilla.org Graveyard
Server Operations
RESOLVED FIXED
10 years ago
3 years ago

People

(Reporter: ted, Assigned: aravind)

Tracking

Details

(URL)

(Reporter)

Description

10 years ago
I fixed a processor bug that has been causing broken crash reports for some people.  I'd like to get the processor updated on production to pick this up.  Details on the fix are in the URL.
(Assignee)

Comment 1

10 years ago
Shouldn't this go to the stage env first?
(Reporter)

Comment 2

10 years ago
That's fine, I can have the users from bug 399645 test submitting there to verify the fix.
(Assignee)

Comment 3

10 years ago
Okay, upgraded stackwalk in staging to version 226.  Let me know if it works and I will push it to production.
(Reporter)

Updated

10 years ago
Summary: update breakpad processor code on production to revision 225 → update breakpad processor code on production to revision 226
(Assignee)

Comment 4

10 years ago
Waiting on a bug fix to reporter so we can verify that this actually works (processor actually processed the dump).  Once we have that fix, I will push this to production.
(Assignee)

Comment 5

10 years ago
morgamic: any eta on this fix?
Is bug 399645 comment 6 enough verification ?
Otherwise, what (more) do you need ?
(Reporter)

Comment 7

10 years ago
Serge: we're seeing problems viewing the report in the web app, and we want to make sure they're not related.
(Assignee)

Comment 8

10 years ago
We did a code upgrade last week.  The processor code is now at Revision 260 and the repository root has been switched as well.  I tried to update the stackwalk code again, but an svn up there Updated to revision 234.

Is this okay or do I need to pull revision 226?
(Reporter)

Comment 9

10 years ago
234 should be fine, 226 just happened to be the latest when I filed this.  If you've compiled the new minidump_stackwalk and are using it in production, feel free to resolve this bug.
Status: NEW → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → FIXED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.