[asterisk-bugs] [Asterisk 0016038]: Various valgrind errors in 1.6.0.16-rc2

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=16038 
====================================================================== 
Reported By:                amorsen
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   16038
Category:                   Core/General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     acknowledged
Asterisk Version:           1.6.0.16-rc2 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-10-07 13:57 CDT
Last Modified:              2009-10-27 05:55 CDT
====================================================================== 
Summary:                    Various valgrind errors in 1.6.0.16-rc2
Description: 
I ran Asterisk on our test system in valgrind with the suppression file
from issue 16007. I'm attaching the result.
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0016007 [patch] Clean valgrind output by suppre...
====================================================================== 

---------------------------------------------------------------------- 
 (0112799) amorsen (reporter) - 2009-10-27 05:55
 https://issues.asterisk.org/view.php?id=16038#c112799 
---------------------------------------------------------------------- 
Ok, here's another dump. I have run fgrep -v 'invalid file' on it to keep
the size down.

It would be nice if we could get rid of these:

==32516== Thread 17:
==32516== Syscall param capget(data) points to unaddressable byte(s)
==32516==    at 0x54DC837: capget (in /lib64/libc-2.10.1.so)

as they happen a lot. Also, I haven't disabled loading of the speex
module, which has quite a few valgrind problems. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-10-27 05:55 amorsen        Note Added: 0112799                          
======================================================================