HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: libdcekt throws exception I cannot catch
Operating System - HP-UX
1827892
Members
1707
Online
109969
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
Forums
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
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
01-06-2005 02:10 AM
01-06-2005 02:10 AM
libdcekt throws exception I cannot catch
We have a C++ multi-threaded application that uses pthreads, along with the DCE library (kernel threaded version) for user validation.
Quite often the application exits with an abort signal after some function in libdcekt prints
"Unhandled exception; exiting!
^@Exception kind is status,value is 10. Thread N"
where ^@ is a null character and N is the thread number. libdcekt.a and its dynamic cousins are the only libraries the app is linked with that contain that "Unhandled" string.
Any idea how how I can catch this DCE exception?
I have tried using the TRY/CATCH_ALL/ENDTRY macros around the DCE functions that we're using (sec_login_setup_identity, sec_login_validate_identity), but the macros have no effect when libdcekt aborts. That is, the CATCH_ALL macro does not catch anyting. We're not using C++ exceptions in this app, and we're compiling with -AP, not -AA (not using the new stdlib).
After scouring the HP DCE docs, I've tried quite a few different combinations of #defines that are available in the DCE headers, but nothing makes a difference.
Just wondering if anyone has successfully caught a DCE exception from libdcekt, in a C++ app, and how did you do it. (Note that the application does not run if I link it with the CMA DCE library, libdce.a).
Host: HP 9000/800 HPUX 11i (B.11.11)
Compiler: HP aCC A.03.50
Thanks for any help,
Dan O'Connell
Quite often the application exits with an abort signal after some function in libdcekt prints
"Unhandled exception; exiting!
^@Exception kind is status,value is 10. Thread N"
where ^@ is a null character and N is the thread number. libdcekt.a and its dynamic cousins are the only libraries the app is linked with that contain that "Unhandled" string.
Any idea how how I can catch this DCE exception?
I have tried using the TRY/CATCH_ALL/ENDTRY macros around the DCE functions that we're using (sec_login_setup_identity, sec_login_validate_identity), but the macros have no effect when libdcekt aborts. That is, the CATCH_ALL macro does not catch anyting. We're not using C++ exceptions in this app, and we're compiling with -AP, not -AA (not using the new stdlib).
After scouring the HP DCE docs, I've tried quite a few different combinations of #defines that are available in the DCE headers, but nothing makes a difference.
Just wondering if anyone has successfully caught a DCE exception from libdcekt, in a C++ app, and how did you do it. (Note that the application does not run if I link it with the CMA DCE library, libdce.a).
Host: HP 9000/800 HPUX 11i (B.11.11)
Compiler: HP aCC A.03.50
Thanks for any help,
Dan O'Connell
- Tags:
- libdcekt
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-07-2005 03:20 AM
01-07-2005 03:20 AM
Re: libdcekt throws exception I cannot catch
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-07-2005 05:57 AM
01-07-2005 05:57 AM
Re: libdcekt throws exception I cannot catch
Yes, I've studied that document many times. It does state that HP DCE is only supported with ANSI C. However, there is also a section that discusses using DCE with C++, so I'm assuming that's ok.
I have read in other HP DCE docs that you can use the "standard" function return values, or you can use the exception-handling interface, which the doc stated was a non-standard extension. But there is no combination of CPP flags that I've been able to devise to *not* use the exception-handling interface.
The DCE 1.8 release notes seems to be focused on the deprecated CMA version, not the kernel threads version. Indeed, all of the sample code in the release is also for the CMA interface; none of it is for the kernel-threads versions.
I have read in other HP DCE docs that you can use the "standard" function return values, or you can use the exception-handling interface, which the doc stated was a non-standard extension. But there is no combination of CPP flags that I've been able to devise to *not* use the exception-handling interface.
The DCE 1.8 release notes seems to be focused on the deprecated CMA version, not the kernel threads version. Indeed, all of the sample code in the release is also for the CMA interface; none of it is for the kernel-threads versions.
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.
Company
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP