| Summary: | ASTERISK-08832: CLI bad core show command crash Asterisk | ||
| Reporter: | tootai (tootai) | Labels: | |
| Date Opened: | 2007-02-18 03:59:30.000-0600 | Date Closed: | 2007-02-19 10:24:21.000-0600 |
| Priority: | Critical | Regression? | No |
| Status: | Closed/Complete | Components: | Core/General |
| Versions: | Frequency of Occurrence | ||
| Related Issues: | |||
| Environment: | Attachments: | ( 0) debug.txt | |
| Description: | CLI> core show <enter non existent command> crash the application. | ||
| Comments: | By: Olle Johansson (oej) 2007-02-18 04:33:52.000-0600 Please read the bug guidelines. If you have a crash, we would like a backtrace. Get one, then upload it as a text file attachment to this bug report! Thanks for reporting bugs. The bug guidelines are there to make sure we can help you faster, it's not just to annoy you or make it more complicated. They're based on a lot of experience and you make yourself a favour by reading them and following them. /Olle By: tootai (tootai) 2007-02-18 05:24:27.000-0600 Sorry. The uploaded file is gdb output from core file. By: Olle Johansson (oej) 2007-02-18 05:43:11.000-0600 No, it's not. It shows you staring GDB and then immediately quitting. By: tootai (tootai) 2007-02-18 06:43:38.000-0600 Don't understand what you mean. I see this in the uploaded file, at the begining: Core was generated by `/usr/sbin/asterisk -vvv -c'. Program terminated with signal 11, Segmentation fault. warning: current_sos: Can't read pathname for load map: Erreur d'entr?e/sortie I ran sudo gdb asterisk <core file name> By: Joshua C. Colp (jcolp) 2007-02-19 09:33:15.000-0600 The attached backtrace is useless and I haven't been able to recreate this issue. Can you try to get a backtrace again or give more information that may help reproduce the issue? By: Tilghman Lesher (tilghman) 2007-02-19 09:45:26.000-0600 Are you running any additional patches and/or additional modules? One of them may be the culprit. By: tootai (tootai) 2007-02-19 10:00:30.000-0600 We run the trunk version as usually for our side: with NVFaxDetect and NVBackgroundDetect applications added, and zaptel stuff. We updated today to latest SVN and are on compiling stage. We tried immediately after the crash a fresh SVN 1.4 (with the same setup) and didn't notice this behaviour. Will come back as soon as fresh version is up. Daniel By: tootai (tootai) 2007-02-19 10:19:29.000-0600 SVN-trunk-r55375 is the one installed now and problem disappear. The only difference between the previous version is codec_zap not loaded (can't get compile it) as well as zaptel (compile error too). As I will leave office for a 10 days business trip, I can't look further. Please close the bug. Thanks Daniel By: Joshua C. Colp (jcolp) 2007-02-19 10:24:20.000-0600 Since you can't reproduce it under latest version, and I can't either this shall be closed out. | ||