This portal is to open public enhancement requests against products and services offered by the IBM Data & AI organization. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas that matter most to you
Get feedback from the IBM team to refine your idea
Specific links you will want to bookmark for future use
better logging for stack overflow, ulimit stack to small
With this PMR we were searching quite hard for the reason, why a 3rd-party-software was dying with segmentation fault in dynamic linked shared library libdb1.so
We could only see: Feb 18 09:01:56 smtcb00254 kernel: [1270273.292859] os4x_licinfo: segfault at 7fffff7fe728 ip 00007ffff509d258 sp 00007fffff7fe730 error 6 in libdb2.so.1[7ffff4aef000+23ce000] And: --- SIGSEGV (Segmentation fault) @ 0 (0) --- ==10541== Process terminating with default action of signal 11 (SIGSEGV): dumping core ==10541== Access not within mapped region at address 0x7FE800808
But nothing, except the IBM Support with this PMR, was giving a hint, that the stacksize was a problem. Solution was at the end to increase default kernel stack size from 8MB to a bigger value. (ulimit -s)
Further information should be available in the PMR.
Request: please increase and optimze logging in this failure-situation and catch this failure, eg. like this: printk(KERN_ALERT "stack size $stack too small, increase with ulimit â€“s ... . EXIT\n");
Do not place IBM confidential, company confidential, or personal information into any field.