[asterisk-bugs] [Asterisk 0016007]: [patch] Clean valgrind output by suppressing false errors
Asterisk Bug Tracker
noreply at bugs.digium.com
Thu Oct 8 07:22:03 CDT 2009
A NOTE has been added to this issue.
======================================================================
https://issues.asterisk.org/view.php?id=16007
======================================================================
Reported By: atis
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 16007
Category: Documentation
Reproducibility: N/A
Severity: tweak
Priority: normal
Status: ready for review
Asterisk Version: SVN
JIRA:
Regression: No
Reviewboard Link:
SVN Branch (only for SVN checkouts, not tarball releases): trunk
SVN Revision (number only!): 221627
Request Review:
======================================================================
Date Submitted: 2009-10-01 13:06 CDT
Last Modified: 2009-10-08 07:22 CDT
======================================================================
Summary: [patch] Clean valgrind output by suppressing false
errors
Description:
There are some false errors that are flooding valgrind log.
Attached small valgrind suppression file that filters out most common
errors. It's supposed to be placed in utils/asterisk.supp but if other dir
is chosen, it should be updated in valgrind.txt
Also updated valgrind.txt so that
* it doesn't write malloc_debug.txt from stderr (which never ever
contained anything useful).
* --log-fd is used instead of --log-file. This helps to avoid flood with
"Use --log-fd=<number> to select an alternative log fd" messages.
======================================================================
Relationships ID Summary
----------------------------------------------------------------------
related to 0016038 Various valgrind errors in 1.6.0.16-rc2
======================================================================
----------------------------------------------------------------------
(0112049) atis (reporter) - 2009-10-08 07:22
https://issues.asterisk.org/view.php?id=16007#c112049
----------------------------------------------------------------------
amorsen: did you mean - you cannot reproduce crashing, or crash occurs but
there's no core dump? I usually have file named vgcore.<pid> on valgrind
3.5.0, written in dir from where valgrind is invoked.
Issue History
Date Modified Username Field Change
======================================================================
2009-10-08 07:22 atis Note Added: 0112049
======================================================================
More information about the asterisk-bugs
mailing list