LVM and VxVM

Re: SIGSEGV for stack growth failure

 
Amber Goel
Occasional Contributor

SIGSEGV for stack growth failure

Hi ,
currently I am using HP-Unix 9000/800/L1000-36.I have install Sybase 11.9 on this server. Since past 4 years this application working fine.But Since past 2 days i am getting this error in my Sybase 11.9 application.
PID 1561 Received a SIGSEGV for stack growth failure,
Possible Causes : insufficent memory or swap space,
or stack size exceed maxsize.
RUN_SYBASE[8]:1561 memory fault (coredump).


please provied your suggestions
4 REPLIES 4
Laurent Menase
Honored Contributor

Re: SIGSEGV for stack growth failure

Get the core file and contact Sybase support.
because it can be just because the application data is corrupted.

You can also check your "dmesg", maxssize, limits (rlimit).

with the core file you may try to see what is the size of the different part your program.

# adb core
PA-32 adb ($h help $q quit)
adb>$M
? map `core'
b1 = 0 e1 = -1 f1 = 0
b2 = 0 e2 = 0 f2 = 0
/ map `core'
Kernel:b = 0xFFFF10B8 e = 0xFFFF10F4 f = 10
Exec: b = 0xFFFF10F4 e = 0xFFFF1138 f = 5C
Core: b = 0xFFFF1140 e = 0xFFFF1144 f = 0xB0
Registers:b = 5EC0F040 e = 5EC0F4D8 f = 0xC4
Data: b = 40001000 e = 40002000 f = 56C
MMF: b = 7B035000 e = 7B036000 f = 157C
MMF: b = 7B036000 e = 7B037000 f = 258C
Stack:b = 7F7F0000 e = 7F7F8000 f = 205EC


If stack of the above segment size is about rlimit configs, maxssize( if it is Stack segment), then it can be the cause.
( the size of a segment is e-f)
Ramesh S
Esteemed Contributor

Re: SIGSEGV for stack growth failure

Hi

as it clearly says

May be due to "insufficent memory or swap space,or stack size exceed maxsize."

You could check it by

kmtune
swapinfo -tam

Thanks & Regards

Ramesh
Dennis Handly
Acclaimed Contributor

Re: SIGSEGV for stack growth failure

>Received a SIGSEGV for stack growth failure,

This is typically a coding problem, recursive stack overflow. By using gdb (bt) on your core file you can quickly check this.

>Laurent: # adb core

It is a lot easier to use gdb than adb.
(You neglected to mention using "$q" to exit.)

>If stack of the above segment size is about rlimit configs, maxssiz (if it is Stack segment), then it can be the cause.

It will always be that unless out of swapspace.

> (the size of a segment is e-f)

That should be e - b.
Dennis Handly
Acclaimed Contributor

Re: SIGSEGV for stack growth failure