- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Core dump due to identifiers "TRY, CATCH, RAISE, E...
Operating System - Linux
1754365
Members
4431
Online
108813
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
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
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
04-22-2007 07:31 PM
04-22-2007 07:31 PM
Core dump due to identifiers "TRY, CATCH, RAISE, ENDTRY, FINALLY, CATCH_ALL" in HP-UX 11V2
Hello,
We are working on migrating our application from HP-UX 11i to HP-UX 11v2.
We were using the identifiers "TRY, CATCH, RAISE, ENDTRY, FINALLY, CATCH_ALL" to build our executable in 11i version.
In 11V2, though we are able to build the executable, it throws core dump while running our application. While debugging,
we found that it throws error when the code flow reach calling "TRY, CATCH, RAISE, ENDTRY, FINALLY, CATCH_ALL". Could you
please let us know the way to handle this?
E.g:
if (status)
{
RAISE(genericServerInitialize_ex);
}
CATCH(genericServerInitialize_ex)
serverJournalDceErrorReport(status, "Error from DCE_server", errstat);
RERAISE;
......
.....
.....
CATCH(genericServerInitialize_ex)
TRACE1("[%s] -SB TMP Exception = |\n", functionName);
serverJournalDceErrorReport(status, "Error from venus_DCE_server", errstat);
RERAISE;
ENDTRY
Thanks in advance for your help,
Sathish
We are working on migrating our application from HP-UX 11i to HP-UX 11v2.
We were using the identifiers "TRY, CATCH, RAISE, ENDTRY, FINALLY, CATCH_ALL" to build our executable in 11i version.
In 11V2, though we are able to build the executable, it throws core dump while running our application. While debugging,
we found that it throws error when the code flow reach calling "TRY, CATCH, RAISE, ENDTRY, FINALLY, CATCH_ALL". Could you
please let us know the way to handle this?
E.g:
if (status)
{
RAISE(genericServerInitialize_ex);
}
CATCH(genericServerInitialize_ex)
serverJournalDceErrorReport(status, "Error from DCE_server", errstat);
RERAISE;
......
.....
.....
CATCH(genericServerInitialize_ex)
TRACE1("[%s] -SB TMP Exception = |\n", functionName);
serverJournalDceErrorReport(status, "Error from venus_DCE_server", errstat);
RERAISE;
ENDTRY
Thanks in advance for your help,
Sathish
- Tags:
- DCE
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