[asterisk-bugs] [Asterisk 0016007]: [patch] Clean valgrind output by suppressing false errors
Asterisk Bug Tracker
noreply at bugs.digium.com
Tue Oct 6 04:04:25 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-06 04:04 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.
======================================================================
----------------------------------------------------------------------
(0111898) amorsen (reporter) - 2009-10-06 04:04
https://issues.asterisk.org/view.php?id=16007#c111898
----------------------------------------------------------------------
--log-fd is nice, but it means that a new start of Asterisk overwrites the
log file of the crashed one... That isn't very convenient. The previous
--log-file-exactly had the same problem.
It would be ideal if valgrind could combine --log-fd and --log-file, so it
opened the file itself but at a particular fd.
Issue History
Date Modified Username Field Change
======================================================================
2009-10-06 04:04 amorsen Note Added: 0111898
======================================================================
More information about the asterisk-bugs
mailing list