| Summary: | ASTERISK-01177: Zapscan coredump | ||
| Reporter: | zoa (zoa) | Labels: | |
| Date Opened: | 2004-03-09 10:11:22.000-0600 | Date Closed: | 2004-09-25 02:54:39 |
| Priority: | Critical | Regression? | No |
| Status: | Closed/Complete | Components: | Core/General |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ||
| Description: | Zapscan seems to coredump in some circumstances. any suggestions on how to debug this ? ****** ADDITIONAL INFORMATION ****** Loaded symbols for /usr/lib/asterisk/modules/app_random.so #0 0x407fb7c7 in conf_exec (chan=0x80ee4f8, data=0xbd7ff7b4) at app_zapscan.c:258 258 if ( tempchan && (!strcmp(tempchan->type, "Zap")) && (tempchan != chan) ) { (gdb) bt #0 0x407fb7c7 in conf_exec (chan=0x80ee4f8, data=0xbd7ff7b4) at app_zapscan.c:258 #1 0x08061a30 in pbx_exec (c=0x80ee4f8, app=0x403aa7c8, data=0xbd7ff7b4, newstack=1) at pbx.c:396 #2 0x08063af3 in pbx_extension_helper (c=0x80ee4f8, context=0x80ee650 "iax-scx", exten=0x80ee744 "666", priority=1, callerid=0x80db760 "\"1\" <cisco1>", action=1) at pbx.c:1171 #3 0x0806482d in ast_pbx_run (c=0x80ee4f8) at pbx.c:1655 #4 0x0806ad9e in pbx_thread (data=0x80ee4f8) at pbx.c:1880 ASTERISK-1 0x400200ba in pthread_start_thread () from /lib/libpthread.so.0 | ||
| Comments: | By: James Golovich (jamesgolovich) 2004-03-09 12:32:44.000-0600 Unless there is some stack corruption, which doesn't seem to be the case here. I'd have to guess that tempchan->type is NULL somehow By: James Golovich (jamesgolovich) 2004-03-09 23:01:38.000-0600 I commited some fixes to Zapscan, but I don't think they will affect this problem at all. Unless it was related to the calling channel being hungup. I was trying to reproduce this segfault and the app never would exit if conf_run was never called. So the channel the app was run on was blocked until somehow it was hungup (and soft hangup wouldn't work) If by some chance this did fix the problem, let me know and I'll close the bug out By: zoa (zoa) 2004-03-10 06:37:01.000-0600 i think it coredumped on a hangup of the channel, will close this for now and reopen if it happens again. By: zoa (zoa) 2004-03-10 16:52:34.000-0600 I suspect these patches sometimes cause following bug: http://bugs.digium.com/bug_view_page.php?bug_id=0001111 By: James Golovich (jamesgolovich) 2004-03-14 04:58:52.000-0600 Ok, the iax2_read error should be gone now. When there were no channels active the for loop ran like crazy emptying the readq. | ||