[asterisk-bugs] [JIRA] (ASTERISK-22079) Segfault: INTERNAL_OBJ (user_data=0x6374652f) at astobj2.c:120

[Leif Madsen (JIRA)]

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

Leif Madsen edited comment on ASTERISK-22079 at 3/12/14 1:27 PM:
-----------------------------------------------------------------

Hi [~one47],
Thanks for the patch! It looks like it will solve the issue. Could you go ahead and post this to reviewboard (now authenticates via crowd for those with signed license agreements)?


was (Author: kmoore):
Hi Steve,
Thanks for the patch! It looks like it will solve the issue. Could you go ahead and post this to reviewboard (now authenticates via crowd for those with signed license agreements)?

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