Closed Bug 1421988 Opened 4 years ago Closed 4 years ago

Update Breakpad snapshot to at least b1226959a25b6a5311801d6f204b088c706e7c25

Categories

(Socorro :: Processor, task, P2)

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: ted, Assigned: osmose)

References

Details

A Breakpad change landed yesterday that will change the format of .sym files in a non-backwards-compatible way:
https://groups.google.com/forum/#!topic/google-breakpad-dev/0btnFh3o-TY

We'll need to update the Breakpad snapshot that the processor uses to at least this changeset in order to future-proof against the new symbol format:
https://chromium.googlesource.com/breakpad/breakpad/+/b1226959a25b6a5311801d6f204b088c706e7c25

This isn't super pressing right now, we won't get symbols in that format until we update the vendored Breakpad in mozilla-central to pick up those changes, but it should be simple to update, so we should just get it out of the way.
I'm making this a P2 so it's on the radar.

Mike: Is this something you can do in the next week?
Priority: -- → P2
Yeah, I can take this.
Assignee: nobody → mkelly
Blocking bug 1309172 so we don't update breakpad in mozilla-central before this is fixed.
Blocks: 1309172
(In reply to Gabriele Svelto [:gsvelto] from comment #3)
> Blocking bug 1309172 so we don't update breakpad in mozilla-central before
> this is fixed.

Thanks! I meant to ask whether we had a bug like that on file.
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → FIXED
I submitted the Breakpad build task to TaskCluster and it completed successfully: https://tools.taskcluster.net/groups/JEwKmRHsS2mowkWNl935tQ

The new breakpad version should be picked up by tomorrow's deploy.
You need to log in before you can comment on or make changes to this bug.