- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- traceback information
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
Forums
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
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
03-16-2006 01:16 AM
03-16-2006 01:16 AM
traceback information
I can get the stack information via LIB$GET_CURR_INVO_CONTEXT and LIB$GET_PREV_INVO_CONTEXT. From this I can get to the PDSC but how do I now get the NAME of each module? Is this the correct approach or is there a simple way to get the traceback information?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-16-2006 01:43 AM
03-16-2006 01:43 AM
Re: traceback information
The calling standard and related things are somewhat different on I64, Alpha and VAX.
There was talk of a callable interface to trace. The symbol table information is in the .EXE but its format is not documented.
Purely Personal Opinion
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-16-2006 02:03 AM
03-16-2006 02:03 AM
Re: traceback information
What a blast from the past!
Happened to mention your name recently (17-Jan) on the www.decnet.nl organized 'Digital' reunion/newyears drink.
Met vriendelijke groetjes uit Nashua, NH,
Hein.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-16-2006 02:16 AM
03-16-2006 02:16 AM
Re: traceback information
OpenVMS V7.2-1H1 on Alpha
Hein,
Good to hear from you after all this time.
Digital right-sized me 11 year ago, now with VXcompany.
Regards
John.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-16-2006 03:00 AM
03-16-2006 03:00 AM
Re: traceback information
there is an undocumented interface to TBK$SHOW_TRACEBACK, see ATW 5175:
http://h71000.www7.hp.com/wizard/wiz_5175.html
It may be possible to use the user action routine (USER_ACTION_PROCEDURE) to write the traceback info to some user specific log file instead of SYS$OUTPUT.
Volker.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-16-2006 01:24 PM
03-16-2006 01:24 PM
Re: traceback information
The TBK$ routines can work, but aren't necessarily architecture independent and subject to change.
It may be simpler and more reliable just to use the LIB$*INVO_CONTEXT routines and dump out non-symbolic information. Worry about correlating it to routine names only if actually necessary. How often do you need to do it? It's fairly straightforward - use the MAP file for the image.
My preference is to keep error handing routines as simple as possible, to avoid the issue of trying to debug "meta" problems, or having logic errors in the handling code mask or misrepresent the real problem.