equis software
2007-Jul-17 17:54 UTC
[asterisk-users] Asterisk 1.4.6 crash using queue app
I'm using Queue app with Asterisk 1.4.6 It was working 5 days without problems and then it crash. When I did #gdb asterisk core.xxx I see... #0 ast_senddigit_end (chan=0x0, digit=54 '6', duration=0) at channel.c:2691 #1 0xb780c7d5 in agent_answer (ast=0x925cb78) at chan_agent.c:398 #2 0x08081877 in ast_senddigit (chan=0x57, digit=54 '6') at channel.c:2692 #3 0x0805d20d in ast_dtmf_stream (chan=0x925cb78, peer=0xb6a2d0e0, digits=0xb6940bf4 "6", between=100) at app.c:243 #4 0xb79086ca in ast_bridge_call (chan=0xb6a2d0e0, peer=0x925cb78, config=0xb69424d4) at res_features.c:1473 #5 0xb6e011ae in try_calling (qe=0xb6942784, options=0x925cb78 "@`\201?\2205&\b?N#\t\003O#\t(r)?\023\b(r)?\023\b(r)?\023\b?N#\t?N#\t\200", announceoverride=0xb694270e "", url=0xb694270d "", go_on=0xb6942770, agi=0x0) at app_queue.c:2651 #6 0xb6df9fda in queue_exec (chan=0xb6a2d0e0, data=0xb694270e) at lock.h :532 #7 0x080c315b in pbx_extension_helper (c=0xb6a2d0e0, con=0x0, context=0xb6a2d260 "telpin-112", exten=0xb6a2d2b0 "80", priority=10, label=0x0, callerid=0xb6a22e08 "402385", action=E_MATCHMORE) at pbx.c :532 #8 0x080c3e21 in __ast_pbx_run (c=0xb6a2d0e0) at pbx.c:2288 #9 0x080c4cc1 in pbx_thread (data=0x0) at pbx.c:2601 #10 0x080f3679 in dummy_start (data=0x0) at utils.c:545 #11 0xb7e9413d in pthread_join () from /lib/libpthread.so.0 #12 0xb7cfa1ba in profil () from /lib/libc.so.6 Any ideas?? -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20070717/8a3073fc/attachment.htm
Russell Bryant
2007-Jul-19 02:04 UTC
[asterisk-users] Asterisk 1.4.6 crash using queue app
equis software wrote:> I'm using Queue app with Asterisk 1.4.6 > > It was working 5 days without problems and then it crash. > When I did #gdb asterisk core.xxx > I see...<snip> There is some weird stuff in that backtrace which makes me think it is not accurate. You have to build without optimizations to get a good backtrace. So, 1) Update to the latest version - currently 1.4.8 2) If you still have a problem, disable optimizations $ make menuselect Compiler Flags -> DONT_OPTIMIZE 'x' to save and quit 3) Run Asterisk with the -g option and retrieve the backtrace (both bt and bt full). 4) Post the backtrace to bugs.digium.com with as much information as you can regarding your configuration, console output before the crash, as well as any other information you can provide about what was going on when it crashed. -- Russell Bryant Software Engineer Digium, Inc.