cancel
Showing results for 
Search instead for 
Did you mean: 

possible stack overflow

 
Highlighted
Regular Advisor

possible stack overflow

Hi experts !!

getting below in dmesg output: hpux 11iv3:

 

Pid 13743 was killed due to failure in writing the signal context - possible stack overflow.

 

# swapinfo -tam
             Mb      Mb      Mb   PCT  START/      Mb
TYPE      AVAIL    USED    FREE  USED   LIMIT RESERVE  PRI  NAME
dev       16384       4   16380    0%       0       -    1  /dev/vg00/lvol2
reserve       -   15489  -15489
memory    15553    3230   12323   21%
total     31937   18723   13214   59%       -       0    -

 

help plz.

 

Rgds,

 

Morshed.

13 REPLIES 13
Highlighted
Acclaimed Contributor

Re: stack overflow

>getting below in dmesg output: HP-UX 11.31.

>Pid 13743 was killed due to failure in writing the signal context - possible stack overflow.

 

So what was PID 13743?  Do you have a corefile lying around?

And when was the dmesg error created?

 

 

Highlighted
Regular Advisor

Re: possible stack overflow

HI,

 

reconfigure "maxssiz" and its gone. seems problem resolve.

 

Regards,

 

Morshed.

Highlighted
Acclaimed Contributor

Re: stack overflow

>reconfigure "maxssiz" and it's gone.

 

What were the old and new values?

Highlighted
Regular Advisor

Re: possible stack overflow

this is current :

 

Tunable      Value  Expression  Changes
maxssiz  134217728  134217728   Immed

 

 

Rgds,

MOrshed

Highlighted
Acclaimed Contributor

Re: stack overflow

>this is current: 134,217,728

 

That's way too big unless you have some wacko recursive application.  Each byte here preallocated for the stack reduces the size of the heap, if maxdsiz already set to 1 GB.

Highlighted
Regular Advisor

Re: stack overflow

Hi ,

 

i'm getting the same again. not actually solved:

 

reapting in dmesg output:

 

 

Pid 27717 was killed due to failure in writing the signal context - possible stack overflow.

 

Regards,

Morshed.

Highlighted
Acclaimed Contributor

Re: stack overflow

You have to know what PID that was.  Any user complaining?

Highlighted
Regular Advisor

Re: stack overflow

 

Hi,

 

yes, when user compiling application  geeting problem.  plesae  see the attached part of dmesg and kmeminfo.  high memory use.

 

 

Regards,

Morshed.

Highlighted
Acclaimed Contributor

Re: stack overflow

>when user compiling application getting problem.

 

Do you have that error output?  Using gcc or aC++?

 

 >high memory use.

 

If you have high memory use, you need more swap.  What does "swapinfo -tam" show during this time?

I only add up to 59%.