Process crashes and does not dump core

traene · 10-12-2008, 03:27 AM

A process occasionally crashes and it does not dump core. ulimit settings should allow this, because we do a 'ulimit -c unlimited'. Write permissions on the CWD are given.

However, I understand that the core is only written on distinct signals: ABRT, SEGV, etc. By what means can i check which signal was recieved by the process, when it crashed?

jlliagre · 10-12-2008, 08:58 AM

Perhaps the process is just exiting without crashing. You can launch the process under the control of a debugger and you'll know why it ended.

jim mcnamara · 10-12-2008, 09:35 AM

You cannot see what signal was sent unless you add signal handling to the original process, so that it writes something to a logfile. Are there any logs? Did you check syslog to see if something else is going on?

traene · 10-13-2008, 02:46 PM

I'll try adding signal handling to the process.

jlliagre · 10-13-2008, 03:37 PM

What makes you believe the program crashes ? Is there an error message telling it ?
Does it happen shortly after starting of only after a while ?
Did you check for system messages ?
What OS are you running ?
Did you try my gdb suggestion ?