[asterisk-bugs] [JIRA] (ASTERISK-20227) Segfault (possible memory corruption?)
Jared Smith (JIRA)
noreply at issues.asterisk.org
Fri Nov 9 18:07:21 CST 2012
[ https://issues.asterisk.org/jira/browse/ASTERISK-20227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=199520#comment-199520 ]
Jared Smith commented on ASTERISK-20227:
----------------------------------------
Right -- I understand that the patch wouldn't catch this type of crash. What I'm saying is that the patch appears to be *causing* this type of crash, at least in our lab testing. With the patch, we can easily crash the system with backtraces similar to the latest one attached to this ticket -- without it, we can go much longer without a segfault.
> 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_backtrace.txt, 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
More information about the asterisk-bugs
mailing list