[asterisk-bugs] [JIRA] (ASTERISK-20792) Segfault during calloc, core dump shows logging string at requested pointer address

[Emiel Suilen (JIRA)]

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

Emiel Suilen edited comment on ASTERISK-20792 at 12/17/12 10:19 AM:
--------------------------------------------------------------------

Matt, you want the valgrind output of version 1.8.7.2 or 1.8.17.0? Or another version?

Note that we will do this with inhouse testing, on the same physical system, as we cannot ask the customer to operate while asterisk is running under valgrind.

[edit]started asterisk1.8.17.0 on valgrind.
                
      was (Author: esuilen):
    Matt, you want the valgrind output of version 1.8.7.2 or 1.8.17.2? Or another version?

Note that we will do this with inhouse testing, on the same physical system, as we cannot ask the customer to operate while asterisk is running under valgrind.
                  
> Segfault during calloc, core dump shows logging string at requested pointer address
> -----------------------------------------------------------------------------------
>
>                 Key: ASTERISK-20792
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-20792
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: General
>         Environment: CentOS 6.3 (Final)
> Kernel 2.6.32-279.9.1el6.x86_64
> 4 Gb memory, single Intel Xeon E6520
> Asterisk 1.8.7.2
>            Reporter: Emiel Suilen
>            Assignee: Emiel Suilen
>            Severity: Critical
>         Attachments: bt, bt_full, edited_full, edited_full_short, p_addr
>
>
> In an environment with many calls (>4k calls/24 hours)  and full logging turned on, our customer experiences occasional crashes. A backtrace of the core dump shows this happens during channel creation, and that the pointer used for the channel is overwriting a string used by the logger.
> Attached are the backtrace, full backtrace, and an examination of the relevant frame in GDB, which shows that the allocated pointer already holds information, that starts several blocks earlier.
> A full core dump cannot be provided, due to the size. The core dump originated from 1.8.7.2, but the same core dumps were also found in higher versions. Unfortunately, these were compiled without debug info. We are unable to reproduce this for other customers, or on single user machines.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira