- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: SIGSEGV
Categories
Company
Local Language
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
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
Community
Resources
Forums
Blogs
- 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-08-2004 11:04 PM
06-08-2004 11:04 PM
SIGSEGV
Pid 16740 received a SIGSEGV for stack growth failure.
Possible causes: insufficient memory or swap space,
or stack size exceeded maxssiz.
The system is running UX11i,
Hardware = rp2430
Memory = 3gb
Swap = 5gb
I know swap and memory are not getting hit as I have watched the values in glance during the time the process runs.
The OS is runnning 64bits,
Now thepart which has confused me, I have been reading various posts on ITRC which suggest increasing maxssiz , others suggest maxdsiz. I increase maxdsiz from
0x10000000 to 0x40000000
Actual parameters are,
maxdsiz 0x40000000 - 0X40000000
maxdsiz_64bit 0x40000000 - 0X40000000
maxssiz 16777216 - 16777216
maxssiz_64bit 16777216 - 16777216
maxtsiz 134217728 Y 134217728
maxtsiz_64bit 0x40000000 Y 0X40000000
The fact I have done this and yet still the process produces a core file, it there anything else I can do ?
Also , the value 0x40000000 relates in hex to 1073741824 , this is in bytes I assume, so this gives a GB stack size ?
Should I increase maxssiz too ?
Thanks for any replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-08-2004 11:20 PM
06-08-2004 11:20 PM
Re: SIGSEGV
What is your dbc_max_pct value? consider to tune that one also.
regards,
Richard
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-08-2004 11:30 PM
06-08-2004 11:30 PM
Re: SIGSEGV
# kmtune | grep dbc
dbc_max_pct 10 - 10
dbc_min_pct 5 - 5
Bufpages is 0.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-09-2004 12:33 AM
06-09-2004 12:33 AM
Re: SIGSEGV
So, don't try to increase kernel parameters, but find the faulting function, I would say. Try looking into debuggers and such (which is best depends on the language used in the application).
A simple question: did the size of the core file increase after increasing the kernel parameter for maxdsiz ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-09-2004 12:34 AM
06-09-2004 12:34 AM
Re: SIGSEGV
Looking at the kernel parameters you've given, maxssize (stack size) is
maxssiz 16777216 - 16777216
maxssiz_64bit 16777216 - 16777216
This equates to 16Mb. Try increasing this to see if it helps.
a value of 33554432 will give you a 32MB stack size.
for reference, maxdsiz is the data segment size, and maxtsiz is the text segment size.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-09-2004 01:50 AM
06-09-2004 01:50 AM