[asterisk-bugs] [Asterisk 0013555]: Joining a MeetMe conference and hanging up shortly after results in SIGSEGV
Asterisk Bug Tracker
noreply at bugs.digium.com
Wed Sep 24 20:40:50 CDT 2008
A NOTE has been added to this issue.
======================================================================
http://bugs.digium.com/view.php?id=13555
======================================================================
Reported By: jeffg
Assigned To:
======================================================================
Project: Asterisk
Issue ID: 13555
Category: Applications/app_meetme
Reproducibility: always
Severity: crash
Priority: normal
Status: new
Asterisk Version: 1.6.0-rc6
SVN Branch (only for SVN checkouts, not tarball releases): N/A
SVN Revision (number only!):
Disclaimer on File?: N/A
Request Review:
======================================================================
Date Submitted: 2008-09-24 20:08 CDT
Last Modified: 2008-09-24 20:40 CDT
======================================================================
Summary: Joining a MeetMe conference and hanging up shortly
after results in SIGSEGV
Description:
In my 1.6.0-rc6 installation, if a user joins a conference and then hangs
up shortly afterward (i.e. during the only-person announcement or during or
shortly after the join chime), Asterisk takes a SIGSEGV to the head.
Sometimes I can reproduce this on the first try, sometimes it takes two or
three consecutive quick join-hangup to reproduce the issue. It seems to
occur regardless of whether I enter MeetMe with no arguments or with a
conference ID and PIN specified.
I'm running almost exclusively SIP on this system, haven't tried to
reproduce issue with any other technologies. Timing source is a TDM410P,
crash happens with dahdi-linux 2.0.0rc4 and trunk.
======================================================================
----------------------------------------------------------------------
(0092852) jeffg (reporter) - 2008-09-24 20:40
http://bugs.digium.com/view.php?id=13555#c92852
----------------------------------------------------------------------
Here's a full backtrace from gdb. Despite rebuilding with DONT_OPTIMIZE
and running Asterisk with the -g flag, I can't get a core out of it, but
I'm able to attach gdb to the running process.
(gdb) continue
Continuing.
[New Thread 1081358672 (LWP 7672)]
[Thread 1081358672 (LWP 7672) exited]
[New Thread 1081358672 (LWP 7673)]
[Thread 1081358672 (LWP 7673) exited]
[New Thread 1081358672 (LWP 7674)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1081358672 (LWP 7674)]
0x00002b3c8834c0ca in pthread_rwlock_wrlock () from /lib/libpthread.so.0
(gdb) bt
http://bugs.digium.com/view.php?id=0 0x00002b3c8834c0ca in
pthread_rwlock_wrlock () from
/lib/libpthread.so.0
http://bugs.digium.com/view.php?id=1 0x0000000000474c5c in ast_rwlock_wrlock
(prwlock=0x2108a63be8) at
/home/jeffg/wc/asterisk-1.6.0-rc6/include/asterisk/lock.h:1132
http://bugs.digium.com/view.php?id=2 0x0000000000474d0d in
ast_event_unsubscribe (sub=0xa29930) at
event.c:355
http://bugs.digium.com/view.php?id=3 0x00002aaac006275e in destroy_dahdi_pvt
(pvt=0x4073e240) at
chan_dahdi.c:2770
http://bugs.digium.com/view.php?id=4 0x00002aaac006290a in destroy_channel
(prev=0x0, cur=0xa11530, now=0)
at chan_dahdi.c:2812
http://bugs.digium.com/view.php?id=5 0x00002aaac00640a9 in dahdi_hangup
(ast=0xa12880) at
chan_dahdi.c:3341
http://bugs.digium.com/view.php?id=6 0x000000000044ab88 in ast_hangup
(chan=0xa12880) at channel.c:1638
http://bugs.digium.com/view.php?id=7 0x00002aaab1824076 in conf_free
(conf=0xa549c0) at app_meetme.c:1352
http://bugs.digium.com/view.php?id=8 0x00002aaab18245cb in dispose_conf
(conf=0xa549c0) at
app_meetme.c:1455
http://bugs.digium.com/view.php?id=9 0x00002aaab182c56e in conf_exec
(chan=0xa53980, data=0x40740d80) at
app_meetme.c:3197
http://bugs.digium.com/view.php?id=10 0x00000000004aac30 in pbx_exec
(c=0xa53980, app=0x910eb0,
data=0x40740d80) at pbx.c:944
http://bugs.digium.com/view.php?id=11 0x00000000004b22db in pbx_extension_helper
(c=0xa53980, con=0x0,
context=0xa53bd8 "opennmsgroup-trusted", exten=0xa53c28 "scrum",
priority=1, label=0x0,
callerid=0xa4f7d0 "7754", action=E_SPAWN, found=0x40742f14,
combined_find_spawn=1) at pbx.c:3113
http://bugs.digium.com/view.php?id=12 0x00000000004b3860 in ast_spawn_extension
(c=0xa53980,
context=0xa53bd8 "opennmsgroup-trusted", exten=0xa53c28 "scrum",
priority=1,
callerid=0xa4f7d0 "7754", found=0x40742f14, combined_find_spawn=1) at
pbx.c:3604
http://bugs.digium.com/view.php?id=13 0x00000000004b3fa2 in __ast_pbx_run
(c=0xa53980) at pbx.c:3690
http://bugs.digium.com/view.php?id=14 0x00000000004b5325 in pbx_thread
(data=0xa53980) at pbx.c:3954
http://bugs.digium.com/view.php?id=15 0x0000000000506b61 in dummy_start
(data=0xa29950) at utils.c:917
http://bugs.digium.com/view.php?id=16 0x00002b3c88348317 in start_thread () from
/lib/libpthread.so.0
http://bugs.digium.com/view.php?id=17 0x00002b3c87eb5d5d in clone () from
/lib/libc.so.6
http://bugs.digium.com/view.php?id=18 0x0000000000000000 in ?? ()
(gdb)
Hope this is helpful.
Issue History
Date Modified Username Field Change
======================================================================
2008-09-24 20:40 jeffg Note Added: 0092852
======================================================================
More information about the asterisk-bugs
mailing list