Closed Bug 554028 Opened 15 years ago Closed 15 years ago

update the minidump_stackwalk binaries in build/tools to Breakpad r556

Categories

(Release Engineering :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: ted, Assigned: ted)

References

Details

jimb landed some changes to the stackwalker to be able to walk x86-64 and ARM stacks. We'll want these changes for unit tests and Talos on those platforms.
I guess we need this as well before we do bug 554024 so stacks on unittest crashes continue to work.
Blocks: 554024
Assignee: nobody → ted.mielczarek
r=me on updating them
Pushed to build/tools: http://hg.mozilla.org/build/tools/rev/0f223b443876 Alice: do you want to handle Talos in a separate bug? I'm never sure of what's involved there.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → FIXED
Summary: update the minidump_stackwalk binaries in build/tools and Talos to the latest Breakpad SVN → update the minidump_stackwalk binaries in build/tools to Breakpad r556
Reopening this on suspicion that it's caused missing symbols on linux, for example http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1269471349.1269473741.31266.gz
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
(In reply to comment #4) > Reopening this on suspicion that it's caused missing symbols on linux, for > example > Ok, so I'm just dumber than can be. Please completely disregard this. Hope these start filtering onto the slaves soon.
Status: REOPENED → RESOLVED
Closed: 15 years ago15 years ago
Resolution: --- → FIXED
All unit test jobs on mozilla-central which started after Wed Mar 24 08:52:05 2010 -0700 would have picked this up. Talos has not been updated yet.
Hmm, so then do we actually have a problem per comment 4?
The symbols archives used by the unit test runs are empty for at least 24 hours, presumably from a recent breakpad landing. Lets assume the stack walker is fine in the absence of any contrary evidence.
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.