Hi, it seems you have a process which is a big stack memory consumer. It receives the signal SIGSEGV. This means your process has broken up the RLIMIT_STACK value.
Extract from getrlimit command man:
RLIMIT_STACK This is the maximum size of a process stack
in bytes. The implementation will not
automatically grow the stack beyond this
limit. If this limit is exceeded, SIGSEGV is
generated for the process. If the process is
blocking or ignoring SIGSEGV, or is catching
SIGSEGV and has not made arrangements to use
an alternate stack, the disposition of
SIGSEGV will be set to SIG_DFL before it is
generated
Philippe