HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Stack exceeds maximum size
Operating System - HP-UX
1830956
Members
1779
Online
110017
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
Forums
Discussions
Discussions
Discussions
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
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
06-03-2007 08:29 PM
06-03-2007 08:29 PM
Hi,
I get the "Memory Fault" error when running an executable. I dont see any core dump but the program aborts. When explored using GDB, we get the following error.
Pid 18574 received a SIGSEGV for stack growth failure.
Possible causes: insufficient memory or swap space,
or stack size exceeded maxssiz.
Please help me.
Thanks,
nan
I get the "Memory Fault" error when running an executable. I dont see any core dump but the program aborts. When explored using GDB, we get the following error.
Pid 18574 received a SIGSEGV for stack growth failure.
Possible causes: insufficient memory or swap space,
or stack size exceeded maxssiz.
Please help me.
Thanks,
nan
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-03-2007 08:46 PM
06-03-2007 08:46 PM
Re: Stack exceeds maximum size
Shalom,
Increase the parameters in the kernel maxssiz maxdsiz
If the program is 64 bit then maxssiz_64 and maxdsiz_64
Can be done with sam or kmtune/kctune depending on your actual OS, which you do not reveal to us.
Requires root access.
SEP
Increase the parameters in the kernel maxssiz maxdsiz
If the program is 64 bit then maxssiz_64 and maxdsiz_64
Can be done with sam or kmtune/kctune depending on your actual OS, which you do not reveal to us.
Requires root access.
SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-03-2007 09:14 PM
06-03-2007 09:14 PM
Re: Stack exceeds maximum size
Before you go as far as increasing maxssiz, you should make sure you are not in an infinite recursive loop. I.e. in gdb look at a stack trace, bt.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-04-2007 02:11 AM
06-04-2007 02:11 AM
Solution
If your maxssiz is set to the default (8MiB) then it may need to be increased; however, only in extremely rare cases does it ever need to exceed 32MiB --- even in 64-bit land. The only time I have ever seen a legitimate need to increase maxssiz beyond 32 MIB was in some code that linked in some FORTRAN libraries but otherwise only extremely poorly written code needs a large stack. The suggestion to examine the stack trace is a good one because you may be entering extremely deep recursion as a result of some data condition. If not then if large stacks are needed the answer is to fix the code rather than increasing maxssiz to ludicrous levels.
If it ain't broke, I can fix that.
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.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP