Closed
Bug 631950
Opened 14 years ago
Closed 14 years ago
Suppress leaks from system libraries in Valgrind builds
Categories
(Testing :: General, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: philor, Unassigned)
References
Details
Attachments
(1 file)
(deleted),
patch
|
Details | Diff | Splinter Review |
See, for example, http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1296881401.1296881977.18466.gz and http://tinderbox.mozilla.org/showlog.cgi?log=Firefox/1296961774.1296962474.6394.gz
Of the 4,472 loss records for 32-bit, and 4,557 for 64-bit, some fairly large number are from things that show no sign of us being involved at all, which seems to me to be the simplest place to start suppressing them down to a number small enough to look at.
Reporter | ||
Comment 1•14 years ago
|
||
Despite seeming like it ought to be enough to suppress every bit of output any program will ever produce, this is just the 32-bit version of "get rid of the things that don't mention us at all, so we can see what the rest look like." Depends on bug 631841 to apply, and bug 631838 to have been used even once.
Reporter | ||
Comment 2•14 years ago
|
||
Good thing nobody at all ever saw this bug, so nobody will ever know just how
little I understood about Valgrind's default value for --num-callers.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•