[asterisk-bugs] [JIRA] (ASTERISK-22079) Segfault: INTERNAL_OBJ (user_data=0x6374652f) at astobj2.c:120
Leif Madsen (JIRA)
noreply at issues.asterisk.org
Wed Mar 12 13:45:19 CDT 2014
[ https://issues.asterisk.org/jira/browse/ASTERISK-22079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=216434#comment-216434 ]
Leif Madsen commented on ASTERISK-22079:
----------------------------------------
[~one47] you can start here: https://wiki.asterisk.org/wiki/display/AST/Code+Review
Basically all you need to do is login to https://reviewboard.asterisk.org with your same credentials as you use on JIRA, then upload your patch to a new review. There are a few fields that need to be filled in. I think the documentation I provided you should help you define the values for those fields.
> Segfault: INTERNAL_OBJ (user_data=0x6374652f) at astobj2.c:120
> --------------------------------------------------------------
>
> Key: ASTERISK-22079
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-22079
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: Core/General
> Affects Versions: 1.8.23.0
> Environment: Linux CentOS 5.9 32-bit as a VM on XenServer 5.6 SP2
> Reporter: Jamuel Starkey
> Assignee: Kinsey Moore
> Attachments: asterisk-22079-backtrace-leif.txt, asterisk-22079-gdb-output.txt, backtrace_asterisk.11.2.certified.txt, provisional_keepalive_fix.diff
>
>
> We discovered this segfault while running a debug build 1.8.23.0-rc1. Although not entirely clear it's likely that this issue was triggered during an asterisk "reload" operation that would have been sent over AMI.
> Attaching the output of gdb (bt, bt full, thread apply all bt) as per the Debug guidelines found on the wiki.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
More information about the asterisk-bugs
mailing list