Hi Luki an all others who answered,
Try kill -6 (i.e. SIGABRT). That usually triggers a core dump for me.
yes, that works for testing and creates a coredump.
Thank you very much for your answer!
PS: Running Asterisk under GDB unfortunately is not an option, because
it is a production system
On 12 September 2010 23:56, Thorolf Godawa nos...@godawa.de wrote:
Hi Luki an all others who answered,
Try kill -6 (i.e. SIGABRT). That usually triggers a core dump for me.
yes, that works for testing and creates a coredump.
Thank you very much for your answer!
PS: Running Asterisk under
On Thu, Sep 2, 2010 at 2:26 PM, Thorolf Godawa nos...@godawa.de wrote:
Any idea what is going wrong here?
Read doc/backtrace.txt
If you cannot get Asterisk to coredump, try running it under gdb to
see what is happening.
--
Paul Belanger | dCAP
Polybeacon | Consultant
Jabber:
Hi everybody,
sometimes we have an Asterisk-crash, but no clue why this is happening,
so I'm trying to make a coredump to analyse it.
I compiled Asterisk 1.4.20.1 on CentOS 5.4 i386 with DEBUG_THREADS and
DONT_OPTIMIZE, then I start it with:
# /bin/bash /usr/sbin/safe_asterisk
This should do
From: asterisk-users-boun...@lists.digium.com
[mailto:asterisk-users-boun...@lists.digium.com] On Behalf Of Thorolf Godawa
Subject: [asterisk-users] How to create a coredump for Asterisk
snip
Just my opinion, but Asterisk probably isn't going to dump when you kill the
process; something internal
Unfortunately, if I kill all asterisk-processes with kill -9 ..., a
coredump never is writen to /tmp, I also looked in other dirs.
Try kill -6 (i.e. SIGABRT). That usually triggers a core dump for me.
Luki
--
_
-- Bandwidth
