On Tue, Oct 16, 2007 at 09:20:32PM -0500, Brian West wrote:
> You'll need to compile with debug symbols and have ulimited -c
> unlimited set. Then you can examine the core and find out what
> exactly caused the crash... Segfaults either are easy to find or very
> hard to find, depending on what is happening. It could also be bad ram.
Just a note: gdb is also capable of using separate debug symbols, which
is quite useful in the case of binary packages: you keep the debug
symbols in a separate package and save mmuch space and download time you
don't need to run something with gdb.
rpm has for quite some time generated those -debug packages by default.
If your binary distribution of Asterisk (or whatever) does not include
them, ask for them to be included.
On Debian it has been possible to generate them rather painlessley as of
Etch. Sadly the package in Etch still misses them. This has been fixed
in the current Unstable package.
--
Tzafrir Cohen
icq#16849755 jabber:[EMAIL PROTECTED]
+972-50-7952406 mailto:[EMAIL PROTECTED]
http://www.xorcom.com iax:[EMAIL PROTECTED]/tzafrir
_______________________________________________
--Bandwidth and Colocation Provided by http://www.api-digital.com--
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
