Closed
Bug 1554043
Opened 5 years ago
Closed 5 years ago
Make the valgrind-test error when valgrind exits with a non-zero code slightly more useful
Categories
(Firefox Build System :: General, defect)
Firefox Build System
General
Tracking
(firefox69 fixed)
RESOLVED
FIXED
mozilla69
| Tracking | Status | |
|---|---|---|
| firefox69 | --- | fixed |
People
(Reporter: glandium, Assigned: glandium)
Details
Attachments
(1 file)
The exit code from valgrind may subtly indicate how it failed (like, if it's 139 or 137, which would mean respectively segfault or killed by something external), which is currently completely hidden, making diagnostics of things like bug 1545094 harder.
|
Assignee | |
Comment 1•5 years ago
|
||
The exit code from valgrind may subtly indicate how it failed (like, if
it's 139 or 137, which would mean respectively segfault or killed by
something external), which is currently completely hidden, making
diagnostics of things like bug 1545094 harder.
Pushed by mh@glandium.org: https://hg.mozilla.org/integration/autoland/rev/a2d0fd91ab23 Make the valgrind-test error when valgrind exits with a non-zero code slightly more useful. r=dmajor
|
||
Comment 3•5 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 5 years ago
status-firefox69:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla69
You need to log in
before you can comment on or make changes to this bug.
Description
•