[asterisk-bugs] [JIRA] (ASTERISK-20227) Segfault (possible memory corruption?)

[Matt Jordan (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-20227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Matt Jordan updated ASTERISK-20227:
-----------------------------------

    Attachment: malloc-enhancements-1.8.15.0.diff

Attaching a patch (malloc-enhancements-1.8.15.0.diff) that provides Richard's MALLOC_DEBUG enhancements for this version.

There are two ways to use this patch:
1) Enable MALLOC_DEBUG.  This will create a mmlog file that will log out information related to a memory corruption that will be useful in the case that one happens.
2) Along with MALLOC_DEBUG, enable DO_CRASH.  This will cause Asterisk to immediately crash when a memory corruption is detected, as opposed to waiting for something to access the now corrupted memory.  If you can tolerate what may potentially be a 'quicker' crash, this would help as well.

                
> Segfault (possible memory corruption?)
> --------------------------------------
>
>                 Key: ASTERISK-20227
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-20227
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: General
>    Affects Versions: 1.8.15.0
>         Environment: Linux
>            Reporter: Jared Smith
>         Attachments: another_backtrace.20120820, asterisk_backtrace_09032012.txt, asterisk_configs.tgz, backtrace_20227.txt, backtrace.3975, malloc-enhancements-1.8.15.0.diff
>
>
> Another segfault I'm seeing (not the same one as ASTERISK-20226). Opening this bug at the request of mjordan.
> [Edit by Rusty Newton - removed older backtrace *from description* and attached as backtrace_20227.txt]

--
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