[asterisk-bugs] [JIRA] Updated: (ASTERISK-20227) Segfault (possible memory corruption?)
Jared Smith (JIRA)
noreply at issues.asterisk.org
Thu Sep 20 02:34:27 CDT 2012
[ https://issues.asterisk.org/jira/browse/ASTERISK-20227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jared Smith updated ASTERISK-20227:
-----------------------------------
Attachment: asterisk_backtrace_09032012.txt
Sure, I have a bunch of them. I've attached another example here, this one should have both DONT_OPTIMIZE and BETTER_BACKTRACES turned on.
For the record, we're in the process of swapping out the hardware as well, just to verify that it's not a hardware issue.
> 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
> Attachments: another_backtrace.20120820, asterisk_backtrace_09032012.txt, backtrace_20227.txt, backtrace.3975
>
>
> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the asterisk-bugs
mailing list