On Mon, Mar 16, 2015 at 6:12 PM, Toufic Khreish (Gmail) <[email protected]> wrote: > Hello Matthew, > > I have compiled Asterisk 13.2 with the following compiler Flags enabled: > DON'T_OPTIMIZE > DEBUG THREADS > BETTER_BACKTRACES > > > My asterisk is running with the asterisk_script: > root 24048 39.4 2.4 128564 50640 pts/1 Sl 00:02 2:21 > /usr/sbin/asterisk -f -vvvg -c > > core show locks > > ======================================================================= > === 13.2.0 > === Currently Held Locks > ======================================================================= > === > === <pending> <lock#> (<file>): <lock type> <line num> <function> <lock > name> <lock addr> (times locked) > === > ======================================================================= > > When my asterisk crashes there is no file called core. > > The results of gdb -se "asterisk" -ex "bt full" -ex "thread apply all bt" > --batch -c core > /tmp/backtrace.txt > > /usr/src/asterisk-13.2.0/core: No such file or directory. > No stack. > > What could be the problem ? >
(1) Asterisk only generates a core file if started with the '-g' option (2) Your core file may not be located in the directory that you are running gdb from. You will need to find where the core file was located - this is typically determined by /proc/sys/kernel/core_pattern -- Matthew Jordan Digium, Inc. | Director of Technology 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA Check us out at: http://digium.com & http://asterisk.org -- _____________________________________________________________________ -- 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
