signal 11

[Javier Ortiz Guajardo]

Do you know something about this message?

(9716) **** 2004/09/16 10:16:11 Child 9808 died due to Signal 11 (core dumped). ****

i did´nt find a core file.

signal 11 Is a unix error?

Thank

[Sundar_7]

Signal 11 is SEGV - Segment Voilation. any process that is sent SIGSEV will dump core and exit.

[John Poff]

Hi,

You might check your 'ulimit -c' setting (in the POSIX shell) to make sure that it isn't set to zero. That setting is for the maximum number of 512 byte blocks allowed for core dumps.

JP

[Kyri Pilavakis]

The trap command can be used in a shell script in order to trap incoming signals :

trap

kyris

[Muthukumar_5]

Signal 11 indicates SIGSEGV ( signal segmentation violation ).

It will be raised when ever your application tried to access unallocated memory or accessing not known memory segments.

But core file will be created there. Else try to check application binary directory.. with find command.

Else, check as ulimit -c

did you enable core file size there,

ulimit -c unlimited to give unlimited size to core file.

Debug the core file as,

file core
what core

gdb binary core
gdb> bt

And if you are tying new program give here to analyse to help

We can trap all signal's with trap on shell script's there.

Try to run your application in a shell script as,

#!/usr/bin/sh
message()
{

echo "SIGSEGV signal got there"
exit 1;
}

trap 'message' 11

# application execution..

Regards
Muthu