Summary:ASTERISK-14957: Various valgrind errors in
Reporter:Benny Amorsen (amorsen)Labels:
Date Opened:2009-10-07 13:57:30Date Closed:2011-06-07 14:07:49
Versions:Frequency of
Environment:Attachments:( 0) valgrind.0sSJaDfOUgO
( 1) valgrind.log
Description:I ran Asterisk on our test system in valgrind with the suppression file from issue 16007. I'm attaching the result.
Comments:By: Atis Lezdins (atis) 2009-10-22 17:19:53

Please try with DONT_OPTIMIZE and MALLOC_DEBUG as described in valgrind.txt

By: Benny Amorsen (amorsen) 2009-10-27 05:55:25

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.

By: Clod Patry (junky) 2009-12-03 23:22:13.000-0600

what's app_voicemail_plain.so exactly?

By: Benny Amorsen (amorsen) 2009-12-04 02:36:46.000-0600

It's simply app_voicemail renamed so you can build it several times with various options and just load the appropriate one.

By: Paul Belanger (pabelanger) 2010-06-29 07:02:37

Please retest with 1.6.2
Per the Asterisk maintenance timeline page at http://www.asterisk.org/asterisk-versions maintenance (bug) support for the 1.6.0 and 1.6.1 branches has ended. For continued maintenance support please move to the 1.6.2 branch.

More information on this change can be found in the release announcement: http://www.asterisk.org/node/49924

By: Benny Amorsen (amorsen) 2010-06-29 08:02:58

I don't see any point in retesting with 1.6.2. I can't fix the problems myself, and there is zero interest in the community. Please close the bug.

By: Paul Belanger (pabelanger) 2010-06-29 08:29:23

Suspended due to lack of interest by reporter.

Suspended due to lack of activity. Please request a bug marshal in #asterisk-bugs on the IRC network irc.freenode.net to reopen the issue should you have the additional information requested.

Further information can be found at http://www.asterisk.org/developers/bug-guidelines