- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- No getting any trace stack dump of exception occu...
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
09-21-2018 08:11 AM
09-21-2018 08:11 AM
Using OpenVMS 8.3 version Itegrity Server.
I have Server program in C, here we are setting error handler. Now this program calls some FORTRAN programs, here main calling fortran program again set error handler.
Some Exceptional conditions are occurring in FORTRAN module which results in call transfer to Fortran error handler, here in debug mode I am able to get call trace where exception generated however once call transferred to C error handler I am not getting any call trace from where this exception is generated. Even I have checked it by commenting the error handler establish at FORTRAN end. So, during execution mode I am not at all getting any trace back dump.
To get the trace back dump during execution mode at Fortran end I used following commands but no result.
CMND='SHOW CALLS;GO;EXIT' --->CALL LIB$SIGNAL(SS$_DEBUG,1,CMND)
CALL LIB$SIGNAL ( %VAL(SS$_ACCVIO) )
CALL SYS$PUTMSG (SIGARGS,0,0,0)
CALL SYS$UNWIND(MECHARGS(5),)
===============================================
I want trace back dump as shown below but nothing getting except out generated msg
%SYSTEM-F-SUBRNG1, subscript 1 range error, PC=0000000000000000, PS=0E870610
%TRACE-F-TRACEBACK, symbolic stack dump follows
image module routine line rel PC abs PC
CHMENU_MAIN CH_ERROR_HANDLER_ROUTINE CH_ERROR_HANDLER_ROUTINE
2867 00000000000042A0 000000000E870610
DEC$FORRTL 0 00000000000DA822 FFFFFFFF8528E822
0 FFFFFFFF803A6AE2 FFFFFFFF803A6AE2
----- Above condition handler called with exception 00000574
%SYSTEM-F-SUBRNG1, subscript 1 range error, PC=000000000E9880F1, PS=0000001B
----- End of Exception message
0 FFFFFFFF80398E92 FFFFFFFF80398E92
CHMENU_MAIN CHCREATEMEMTABLES CHCREATEMEMTABLES
4341 0000000000004400 000000000E9880F0
CHMENU_MAIN NW_CHARTSUB NW_CHARTSUB 5341 000000000000F4A2 000000000E8A9412
CHMENU_MAIN CHMENU_NEW CHMENU_NEW 3246 0000000000003621 000000000E812BA1
CHMENU_MAIN CHMENU_MAIN main 8942 0000000000000B60 000000000E800B60
CHMENU_MAIN CHMENU_MAIN __main 8853 0000000000000101 000000000E800101
0 FFFFFFFF80A327D2 FFFFFFFF80A327D2
DCL 0 000000000007D472 000000007AE2D472
%TRACE-I-END, end of TRACE stack dump
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-22-2018 09:13 AM
09-22-2018 09:13 AM
SolutionProblem get resolved. As, I have mentioned in problem that we have 2 different error handler and I was trying to catch trace back stack dump during exception handler in Fortran but in fact call was getting transferred to C error handler whenever any of above written commands were getting executed. I got the the traceback dump in C error handler using below command -
CMND='SHOW CALLS;GO;EXIT' --->CALL LIB$SIGNAL(SS$_DEBUG,1,CMND)