- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: U_STACK_TRACE in signal handler recurses deepl...
Operating System - HP-UX
1753880
Members
7604
Online
108809
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
тАО11-17-2005 01:31 AM
тАО11-17-2005 01:31 AM
U_STACK_TRACE in signal handler recurses deeply if signal handler in a different object file
A common practice of handling crash signals (SIGBUS/SIGSEGV/etc) is to use U_STACK_TRACE in signal handler.
Everything is fine until we separate the code that actually causes the crash, and the signal handler that calls U_STACK_TRACE, to separate source code files, compile them separately and then link the object files.
Then, the call to U_STACK_TRACE may recurse deeply and even crash again with SIGILL, for example. Still, the crash that happens in the same object file that has signal handler, works as designed.
I've attached source files, makefile, system versioning information.
Maybe, someone can help me.
Everything is fine until we separate the code that actually causes the crash, and the signal handler that calls U_STACK_TRACE, to separate source code files, compile them separately and then link the object files.
Then, the call to U_STACK_TRACE may recurse deeply and even crash again with SIGILL, for example. Still, the crash that happens in the same object file that has signal handler, works as designed.
I've attached source files, makefile, system versioning information.
Maybe, someone can help me.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-27-2007 04:53 PM
тАО08-27-2007 04:53 PM
Re: U_STACK_TRACE in signal handler recurses deeply if signal handler in a different object file
The problem with "s" and "r" occurs because the Unwindlib knows nothing about sigaltstack(2) and thinks the framesize is larger than SP and then calls U_PRINT_ERR and gets into a recursive loop. If there is a difference because of the different object file, it's more likely due to the fact there is an extra frame.
Please contact the Response Center and file a bug report.
Probably the only reason "R" works is because it doesn't trace all of the recursive crash frames?
On IPF, "R" and "r" fail because sigaltstack(2) doesn't seem to handle RSE stack overflows. I see no evidence of it getting to the signal handler.
Please contact the Response Center and file a bug report.
Probably the only reason "R" works is because it doesn't trace all of the recursive crash frames?
On IPF, "R" and "r" fail because sigaltstack(2) doesn't seem to handle RSE stack overflows. I see no evidence of it getting to the signal handler.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-27-2009 05:28 AM
тАО04-27-2009 05:28 AM
Re: U_STACK_TRACE in signal handler recurses deeply if signal handler in a different object file
>because the Unwindlib knows nothing about sigaltstack(2)
This was fixed last year.
This was fixed last year.
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