[asterisk-bugs] [JIRA] (ASTERISK-27243) contrib: valgrind.supp doesn't suppress what it's supposed to due to invalid syntax

[Rusty Newton (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-27243?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=238892#comment-238892 ] 

Rusty Newton commented on ASTERISK-27243:
-----------------------------------------

Awesome! Looks like an easy patch then. I'm going to open it up, so you or any other community member can contribute a patch and tackle it at your leisure.

> contrib: valgrind.supp doesn't suppress what it's supposed to due to invalid syntax
> -----------------------------------------------------------------------------------
>
>                 Key: ASTERISK-27243
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-27243
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Contrib/General
>    Affects Versions: 14.6.0
>         Environment: CentOS 7
>            Reporter: Richard Kenner
>            Assignee: Unassigned
>            Severity: Trivial
>
> contrib/valgrind.supp appears to be trying to suppress this error:
> {noformat}
> ==11012== Conditional jump or move depends on uninitialised value(s)
> ==11012==    at 0x28217588: speex_decode_int (in /usr/lib64/libspeex.so.1.5.0)
> ==11012==    by 0x2800AFDB: speextolin_framein (codec_speex.c:229)
> ==11012==    by 0x608A45: framein (translate.c:423)
> ==11012==    by 0x609628: generate_computational_cost (translate.c:678)
> ==11012==    by 0x60B08F: __ast_register_translator (translate.c:1223)
> ==11012==    by 0x2800C13F: load_module (codec_speex.c:626)
> ==11012==    by 0x544755: start_resource (loader.c:988)
> ==11012==    by 0x54537A: load_resource_list (loader.c:1240)
> ==11012==    by 0x545A71: load_modules (loader.c:1375)
> ==11012==    by 0x45DD48: asterisk_daemon (asterisk.c:4647)
> ==11012==    by 0x45D299: main (asterisk.c:4396)
> {noformat}
> but it actually doesn't and the error is still reported.



--
This message was sent by Atlassian JIRA
(v6.2#6252)