[Home]

Summary:ASTERISK-18922: crash when you call 'core show channel <channel's name>'
Reporter:Nicolò Mazzon (nmazzon)Labels:
Date Opened:2011-11-25 02:33:20.000-0600Date Closed:2011-12-20 09:06:49.000-0600
Priority:MajorRegression?No
Status:Closed/CompleteComponents:CDR/General
Versions:1.8.5.0 Frequency of
Occurrence		Frequent
Related
Issues:
Environment:CentOS 5.6Attachments:( 0) backtrace.txt
Description:On many installations there often is a crash when we call 'core show channel <channel's name>'.
After retrieved core dump, gdb returned:
{noformat}
Core was generated by `/usr/sbin/asterisk -f -U asterisk -G asterisk -vvvg -c'.
Program terminated with signal 11, Segmentation fault.
#0  0x0000000000459f2e in ast_cdr_serialize_variables ()
{noformat}

Comments:By: Nicolò Mazzon (nmazzon) 2011-11-25 02:40:45.954-0600

backtrace:
{noformat}
#0  0x0000000000459f2e in ast_cdr_serialize_variables ()
#1  0x000000000047ab4b in handle_showchan ()
#2  0x0000000000479c90 in ast_cli_command_full ()
#3  0x00000000004d80d1 in action_command ()
#4  0x00000000004d3baf in process_message ()
#5  0x00000000004d57a3 in do_message ()
#6  0x00000000004ddf5d in session_do ()
#7  0x00000000005277b5 in handle_tcptls_connection ()
#8  0x00000000005330dc in dummy_start ()
#9  0x0000003e1dc0673d in start_thread () from /lib64/libpthread.so.0
#10 0x0000003e1d4d3d1d in ?? ()
#11 0x0000000000000000 in ?? ()
{noformat}
By: Nicolò Mazzon (nmazzon) 2011-11-25 03:35:33.244-0600

file attached after read notes on https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace
By: Leif Madsen (lmadsen) 2011-11-29 14:31:08.716-0600

Sorry your backtrace is optimized. Please provide an unoptimized backtrace.
By: Nicolò Mazzon (nmazzon) 2011-11-30 02:53:33.746-0600

Sorry but I have not any unoptimized core after crash..

I retrieved other core from many crashes from other customers' server, and every core has got 'Segmentation fault' on ast_cdr_serialize_variables.

What other useful info can I retrieve?


By: Leif Madsen (lmadsen) 2011-12-02 13:47:21.329-0600

Sounds like it might be memory corruption then. You'll need to be able to reproduce this on a development system using valgrind. Please note that valgrind is not suitable for use on production.
By: Leif Madsen (lmadsen) 2011-12-02 13:47:40.482-0600

Your backtrace appears to contain memory corruption and we require valgrind output in order to move this issue forward. Please see https://wiki.asterisk.org/wiki/display/AST/Valgrind for more information about how to produce debugging information. Thanks!


By: Leif Madsen (lmadsen) 2011-12-20 09:06:40.051-0600

Suspended due to lack of activity. Please request a bug marshal in #asterisk-bugs on the IRC network irc.freenode.net to reopen the issue should you have the additional information requested.  Further information can be found at http://www.asterisk.org/developers/bug-guidelines