[asterisk-bugs] [JIRA] (ASTERISK-21157) Asterisk 1.8.20.0 Crash when unloading chan_dahdi
Saleh Madi (JIRA)
noreply at issues.asterisk.org
Wed Feb 27 00:38:18 CST 2013
[ https://issues.asterisk.org/jira/browse/ASTERISK-21157?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=203501#comment-203501 ]
Saleh Madi commented on ASTERISK-21157:
---------------------------------------
After I install asterisk-debuginfo and I have enable the backtrack and this is what i got from the bt and bt full log:
warning: no loadable sections found in added symbol-file system-supplied DSO at 0x7fff64ffd000
Core was generated by `/usr/sbin/asterisk -f -U asterisk -G asterisk -vvvg -c'.
Program terminated with signal 11, Segmentation fault.
#0 0x0000000000471db0 in category_get (config=0x4aa893, category_name=0x2b37980f6400 "", ignored=0) at config.c:664
664 for (cat = config->root; cat; cat = cat->next) {
(gdb) bt
#0 0x0000000000471db0 in category_get (config=0x4aa893, category_name=0x2b37980f6400 "", ignored=0) at config.c:664
0000001 0x00000000004ca5dd in handle_updates (s=0x1, m=0x32) at manager.c:2751
0000002 action_updateconfig (s=0x1, m=0x32) at manager.c:2823
0000003 0x0000000000000000 in ?? ()
(gdb) bt full
#0 0x0000000000471db0 in category_get (config=0x4aa893, category_name=0x2b37980f6400 "", ignored=0) at config.c:664
cat = 0xf685c5894840738b
0000001 0x00000000004ca5dd in handle_updates (s=0x1, m=0x32) at manager.c:2751
__PRETTY_FUNCTION__ = "handle_updates"
0000002 action_updateconfig (s=0x1, m=0x32) at manager.c:2823
cfg = 0x4aa893
sfn = 0x32 <Address 0x32 out of bounds>
dfn = 0x2b37487cfe60 "\330\376|H7+"
res = <value optimized out>
rld = 0x2b37980f64f0 "`f\017\230\067+"
config_flags = <value optimized out>
0000003 0x0000000000000000 in ?? ()
No symbol table info available.
> Asterisk 1.8.20.0 Crash when unloading chan_dahdi
> -------------------------------------------------
>
> Key: ASTERISK-21157
> URL: https://issues.asterisk.org/jira/browse/ASTERISK-21157
> Project: Asterisk
> Issue Type: Bug
> Security Level: None
> Components: Channels/chan_dahdi
> Reporter: Saleh Madi
> Assignee: Saleh Madi
> Severity: Critical
>
> Hello,
> We're running Elastix 2.4.0, with Asterisk 1.8.20.0 on CentOS. We are running into frequent Segmentation faults, which usually crashes once or twice a day and automatically restart asterisk.
> I have enable the backtrack and this is what i got from the bt and bt full log:
> {noformat}
> warning: no loadable sections found in added symbol-file system-supplied DSO at 0x7fffedbfd000
> Core was generated by `/usr/sbin/asterisk -f -U asterisk -G asterisk -vvvg -c'.
> Program terminated with signal 11, Segmentation fault.
> #0 0x00000036c9e7b5eb in memcpy () from /lib64/libc.so.6
> (gdb) bt
> #0 0x00000036c9e7b5eb in memcpy () from /lib64/libc.so.6
> 0000001 0x0000000000445e2c in callerid_feed ()
> 0000002 0x00002b8c410c71f3 in ast_unregister_file_version () from /usr/lib64/asterisk/modules/chan_dahdi.so
> 0000003 0x00002b8c410f07d3 in ast_unregister_file_version () from /usr/lib64/asterisk/modules/chan_dahdi.so
> 0000004 0x000000000051f3de in ?? ()
> 0000005 0x00000036caa0683d in start_thread () from /lib64/libpthread.so.0
> 0000006 0x00000036c9ed503d in clone () from /lib64/libc.so.6
> (gdb) bt full
> #0 0x00000036c9e7b5eb in memcpy () from /lib64/libc.so.6
> No symbol table info available.
> 0000001 0x0000000000445e2c in callerid_feed ()
> No symbol table info available.
> 0000002 0x00002ba10cc6a1f3 in ast_unregister_file_version () from /usr/lib64/asterisk/modules/chan_dahdi.so
> No symbol table info available.
> 0000003 0x00002ba10cc937d3 in ast_unregister_file_version () from /usr/lib64/asterisk/modules/chan_dahdi.so
> No symbol table info available.
> 0000004 0x000000000051f3de in ?? ()
> No symbol table info available.
> 0000005 0x00000036caa0683d in start_thread () from /lib64/libpthread.so.0
> No symbol table info available.
> 0000006 0x00000036c9ed503d in clone () from /lib64/libc.so.6
> {noformat}
> Many thanks and Best Regards,
> Saleh Madi
--
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