failure in writing the signal context

[rana sarkar]

What is the meaning of this warnings in syslog:

Apr 8 12:36:45 bgbmap01 vmunix: Pid 6975 was killed due to failure in writing the signal context.
Apr 8 12:49:08 bgbmap01 vmunix: Pid 2985 was killed due to failure in writing the signal context.
Apr 8 12:50:03 bgbmap01 vmunix: Pid 2065 was killed due to failure in writing the signal context.
Apr 8 13:00:26 bgbmap01 vmunix: Pid 3672 was killed due to failure in writing the signal context.
Apr 8 13:03:23 bgbmap01 vmunix: Pid 5280 was killed due to failure in writing the signal context.
Apr 8 13:05:00 bgbmap01 vmunix: Pid 23421 was killed due to failure in writing the signal context.
Apr 8 13:05:04 bgbmap01 vmunix: Pid 6280 was killed due to failure in writing the signal context.
Apr 8 13:05:23 bgbmap01 vmunix: Pid 10249 was killed due to failure in writing the signal context.
Apr 8 13:05:26 bgbmap01 vmunix: Pid 6469 was killed due to failure in writing the signal context.
Apr 8 13:05:30 bgbmap01 vmunix: Pid 15596 was killed due to failure in writing the signal context.
Apr 8 13:05:38 bgbmap01 vmunix: Pid 3222 was killed due to failure in writing the signal context.
Apr 8 13:05:41 bgbmap01 vmunix: Pid 12735 was killed due to failure in writing the signal context.
Apr 8 13:05:45 bgbmap01 vmunix: Pid 6085 was killed due to failure in writing the signal context.
Apr 8 13:06:28 bgbmap01 vmunix: Pid 16019 was killed due to failure in writing the signal context.
Apr 8 13:06:30 bgbmap01 vmunix: Pid 15313 was killed due to failure in writing the signal context.

[Dennis Handly]

This probably means there was a stack overflow or thread stack overflow where there wasn't room to write the context.
Unless you know which were those PIDs or find corefiles, this is useless.

[rana sarkar]

How to diagonise the problem.

[smatador]

Hi,
You have to find the core file of this issue, { check the date of the core } after you could analyse the core for example by
file core
what core
strings -a core
to see what could be the cause of the creation. When you have the program, check for patch or tuning of the stack
Hope it helps

[Dennis Handly]

>smatador: what core; strings -a core

These are typically useless. You need to use a debugger to get a stack trace to start:
gdb executable core
(gdb) bt