- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Stack Overflow error in HPUX11iv2
Operating System - HP-UX
1755755
Members
5227
Online
108838
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-30-2010 06:53 PM
тАО03-30-2010 06:53 PM
Stack Overflow error in HPUX11iv2
Hi All,
Getting following error in Application while doing the EOD Operation.
failure in writing the signal contec-possible stack overflow.
sendsig: useracc failed.
Can anybody help me in this issue? and how to increase the stack?
Thanks & regards,
Sujeet Joshi
Getting following error in Application while doing the EOD Operation.
failure in writing the signal contec-possible stack overflow.
sendsig: useracc failed.
Can anybody help me in this issue? and how to increase the stack?
Thanks & regards,
Sujeet Joshi
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-30-2010 08:59 PM
тАО03-30-2010 08:59 PM
Re: Stack Overflow error in HPUX11iv2
Hi Jishi,
you either have a main stack or a thread stack overflow.
You need to get a stack trace (use gdb) to determine which.
On the WDB page you can find this document:
Debugging core files using HP WDB
http://www.hp.com/go/wdb
Basically on the same system that caused the core dump:
$ file core
(Gives you the signal and up to 14 bytes of the basename of the executable.
$ gdb path-to/executable core
(gdb) bt
(gdb) q
If it is a main thread, you should see main at the bottom. If it is a thread, you should see some pthread on the bottom.
By taking the difference in the $sp register from the top and bottom frames, you can compute your current stack size.
There are two possibilities:
1) The user's shell (or a parent of that shell) has lowered the hard limit
using ulimit -h - at which point you have to find this and modify it.
Note, this is very rare -- you are much more likely to have to:
2) The system-wide hard limit is determined by the kernel tunable "maxssiz" and/or "maxssiz_64bit". maxssiz is the limit for 32-bit processes, maxssiz_64bit for 64-bit.
Note that maxssiz_64bit trumps maxssiz_32bit (i.e. a lower 64-bit limit will be used instead of the 32-bit limit.. this is a consequence of the parent bitness as the system comes up), so you'll want to consider both.
On 11.23, maxssiz / maxssiz_64bit are dynamic - changes to them take effect immediately for any new processes. So "kctune -u -s maxssiz=" and that should do it.
As a side note - if the user believes they need a very large stack, make sure that they understand why. Fortran and Java are both legitimate use cases -- for normal C programming, large stacks are usually a sign of poor recursion. Not saying there's a problem, but just worth a mention.
Cheers,
taifur
you either have a main stack or a thread stack overflow.
You need to get a stack trace (use gdb) to determine which.
On the WDB page you can find this document:
Debugging core files using HP WDB
http://www.hp.com/go/wdb
Basically on the same system that caused the core dump:
$ file core
(Gives you the signal and up to 14 bytes of the basename of the executable.
$ gdb path-to/executable core
(gdb) bt
(gdb) q
If it is a main thread, you should see main at the bottom. If it is a thread, you should see some pthread on the bottom.
By taking the difference in the $sp register from the top and bottom frames, you can compute your current stack size.
There are two possibilities:
1) The user's shell (or a parent of that shell) has lowered the hard limit
using ulimit -h - at which point you have to find this and modify it.
Note, this is very rare -- you are much more likely to have to:
2) The system-wide hard limit is determined by the kernel tunable "maxssiz" and/or "maxssiz_64bit". maxssiz is the limit for 32-bit processes, maxssiz_64bit for 64-bit.
Note that maxssiz_64bit trumps maxssiz_32bit (i.e. a lower 64-bit limit will be used instead of the 32-bit limit.. this is a consequence of the parent bitness as the system comes up), so you'll want to consider both.
On 11.23, maxssiz / maxssiz_64bit are dynamic - changes to them take effect immediately for any new processes. So "kctune -u -s maxssiz=
As a side note - if the user believes they need a very large stack, make sure that they understand why. Fortran and Java are both legitimate use cases -- for normal C programming, large stacks are usually a sign of poor recursion. Not saying there's a problem, but just worth a mention.
Cheers,
taifur
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО03-30-2010 09:56 PM
тАО03-30-2010 09:56 PM
Re: Stack Overflow error in HPUX11iv2
>Taifur: you either have a main stack or a thread stack overflow. You need to get a stack trace (use gdb) to determine which.
Exactly.
>So "kctune -u -s maxssiz=
-u and -s are obsolete kmtune(1m) options. You should leave both off.
Exactly.
>So "kctune -u -s maxssiz=
-u and -s are obsolete kmtune(1m) options. You should leave both off.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP