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

[Richard Mudgett (JIRA)]

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

Richard Mudgett edited comment on ASTERISK-20227 at 12/19/12 6:52 PM:
----------------------------------------------------------------------

Assuming the patch from bug ASTERISK-20226 is added to the 1.8.20.0 release, I don't see any reason to keep this bug open.  The problem doesn't seem to happen any more after applying the patch.
                
      was (Author: jsmith):
    Assuming the patch from bug 20226 is added to the 1.8.20.0 release, I don't see any reason to keep this bug open.  The problem doesn't seem to happen any more after applying the patch.
                  
> 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
>            Assignee: Jared Smith
>      Target Release: 1.8.20.0
>
>         Attachments: another_backtrace.20120820, asterisk_backtrace_09032012.txt, asterisk_configs.tgz, backtrace_20227.txt, backtrace.3975, malloc_backtrace.txt, malloc-enhancements-1.8.15.0.diff, test_configs.tgz
>
>
> 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