- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Rare heap corruption
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
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
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
08-13-2013 05:46 AM - edited 08-14-2013 03:50 AM
08-13-2013 05:46 AM - edited 08-14-2013 03:50 AM
We have coredumps from time to time on one of our customer's servers. It seems to be caused by a heap corruption. On our servers we have not managed to reproduce this problem so far. What approached (besides analyzing corefiles) can be used on a customer server to localize the problem?
I thoght that it could be librtc and tested the program with these settings:
>more rtcconfig
set heap-check off
set heap-check free on
set heap-check leaks off
set heap-check bounds on
abort_on_bounds=1
abort_on_bad_free=1
but using librtc results in significant performance decrease and I am not sure I can recomend to install librtc on a real customer server.
What is HP recomendation for localizing problems in this situations?
Solved! Go to Solution.
- Tags:
- heap corruption
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-14-2013 02:46 AM
08-14-2013 02:46 AM
Solution>It seems to be caused by a heap corruption.
I would hope you have figured out it is more than just "seems" and be more positive. If it isn't heap corruption, then using librtc won't help.
>What approached (besides analyzing corefiles) can be used on a customer server to localize the problem?
Have you learned anything from the corefiles?
>I thought that it could be librtc and tested the program with these settings:
>more rtcconfig
>set heap-check off
Any reason you have off here?
Make sure "show heap-check" shows it is on. Though this file may not be the same syntax as gdb's.
>using librtc results in significant performance decrease and I am not sure I can recommend to install librtc on a real customer server. What is HP recommendation for localizing problems in this situations?
librtc is the only automated way of checking. Really nothing else to recommend except to find patterns in the aborts you have.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-14-2013 02:58 AM
08-14-2013 02:58 AM
Re: Seldom heap corruption
Definitely there will be performance impact.
The best you can do is run the application in Batch mode of librtc, you can use nudge feature to get the memory reports at any point of time by just sending a signal to the process.
You can obtain the reports at multiple times during the same application run.
It might be possible that the corruption happens but the crash is rare, such corruption cases could be found.
Even if the application crashes before you could obtain memory report, you can still obtain the corruption report from the core file as the process that dumped core had librtc preloaded.
You need not explicitly turn on/off individual rtc parameters you can just do "set heap-check on". It by default enables the required parameters.
But if the corruption itself happens rarely, they will be difficult to track down.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-14-2013 04:55 AM - edited 08-14-2013 05:23 AM
08-14-2013 04:55 AM - edited 08-14-2013 05:23 AM
Re: Rare heap corruption
>>I thought that it could be librtc and tested the program with these settings:
>>more rtcconfig
>>set heap-check off
>Any reason you have off here?
Dennis, yes, there is a reason. I am interested in librtc reports about memory corruption and not interested about memory leaks and memory consumption. When "set heap-check off" I only get *.mem files and I don't get *.heap files.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-14-2013 05:21 AM - edited 08-14-2013 05:21 AM
08-14-2013 05:21 AM - edited 08-14-2013 05:21 AM
Re: Seldom heap corruption
nitinjain,
> you can use nudge feature to get the memory reports at any point of time by just sending a signal to the process
Please explain how to get a memory report when a process run with LD_PRELOAD=librts.so by sending a signal?
I could not find it in the HP wd 6.1 documention.