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 an "ulimit -c unlimited", but I entered it in the terminal again. A # ps -ef | grep asterisk tells me that Asterisk is running as root and with the g-option for writing a coredump: root 21622 1 0 20:15 pts/0 00:00:00 /bin/bash /usr/sbin/safe_asterisk root 21627 21622 1 20:15 pts/0 00:00:00 /usr/sbin/asterisk -f -vvvg -c In the asterisk-start-script, the coredump-dir is configured as: DUMPDROP=/tmp Unfortunately, if I kill all asterisk-processes with "kill -9 ...", a coredump never is writen to "/tmp", I also looked in other dirs. Any idea what is going wrong here? Some links I found, but they do not help me: http://www.asterisk.org/doxygen/trunk/AstDebug.html http://www.voip-info.org/wiki/view/Asterisk+debugging http://man.sourcentral.org/centos5/5+core http://de.w3support.net/index.php?db=so&id=17965 Thanks a lot, -- Chau y hasta luego, Thorolf -- _____________________________________________________________________ -- 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