Hello,
some extra notes about the location of the core files. Kamailio changes the working directory to / (the root of file system) if no -w parameter is given. So it is very likely the core is in /. Also, on some operating system, the core files are written in a special directory, which is a kernel option.
The syslog messages showed that core file was generated, so you can just look for it in / or the working directory for kamailio or the special path of the OS for corefiles.
Cheers, Daniel
On 9/14/11 4:34 PM, marius zbihlei wrote:
On 09/14/2011 05:01 PM, Phillman25 Kyriacou wrote:
Dear Marius
Thank you for your prompt reply. I apologise, As i am a newbie could you please explain how to produce the below output that you require?
if you can reproduce the crash, in a shell write
ulimit -c unlimited #to allow unlimited size of coredump kamailio -f ../path/to/cfg #any other options you give to kamailio <here the crash happens - make it happen>
In the directory that you lunch the commands you will find several core.kamailio.<pid> (or simply just core) file, that are called coredumps (they should be fairly large so don't worry)
After that :
gdb /path/to/kamailio core.kamailo.<pid> #or how the core was called
bt full info reg
(these commands are in gdb prompt) Paste the output of the gdb commands and lets see what happens. It would really help if kamailio already has debug symbols when compilling (should be enabled by default).
Cheers Marius
Thanking you in advance for your help!
Regards Phillip
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users