On 09/16/2010 12:41 PM, Philipp von Klitzing wrote: > Hi! > >> Does this shine new light to the problem ?! >> > No. Once more: Go and read doc/backtrace.txt. > > And check if you have any meaningful information in /var/log/messages for > the timestamp when asterisk crashed. > > Philipp >
I get so little output : Core was generated by `/usr/sbin/asterisk -f -vvvg -c'. Program terminated with signal 6, Aborted. #0 0x00002b4f70970265 in ?? () (gdb) set logging on Copying output to gdb.txt. (gdb) bt #0 0x00002b4f70970265 in ?? () (gdb) bt full #0 0x00002b4f70970265 in ?? () No symbol table info available. (gdb) The generated files are also very small : bash-3.2# ls -lh total 408M -rw-rw-r-- 1 root root 4.0K Sep 16 14:17 backtrace.txt -rw------- 1 root root 42M Sep 15 21:46 core.4569 -rw-rw-r-- 1 root root 2.6K Sep 16 14:17 gdb.txt I followed the steps in : ------------------------------------------------------------------------------- --- Getting Information After A Crash ------------------------------------------------------------------------------- Jonas. -- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users