- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Re: ovms8.1 Linker lib$signal Traceback
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
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
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
тАО07-03-2004 06:35 AM
тАО07-03-2004 06:35 AM
image /module /routine /line information with
lib$signal or with a FORTRAN Access Violation.
The Debugger seems similarly hobbled.
>> Is this just not yet implemented in 8.1, or
are there settings/workarounds available?
Specifically, on ovms8.1
Program Crash_Test
call sub1( )
End
Subroutine sub1( z )
type *, 'calling lib$signal...'
call lib$signal( %val(0) )
type *, z
Return
End
$ Fortran /obj /lis crash_test /noopt /debug
$ Link /exe /map crash_test /Traceback
$ Run crash_test
calling lib$signal...
%NONAME-W-NOMSG, Message number 00000000
%TRACE-W-TRACEBACK, symbolic stack dump follows
Traceback - Exception frame found. Mechanism vector address 000000007AC06FC0
Traceback - Condition handler called with exception 0000000000000000:
%NONAME-W-NOMSG, Message number 00000000
image module routine line rel PC abs PC
0000000000010180
0000000000010090
FFFFFFFF80947E10
000000007ADEADB0
Traceback - Bottom of call stack
0.0000000E+00
-----------------------------------------------
whereas same code built on ovms7.3 gives
calling lib$signal...
%NONAME-W-NOMSG, Message number 00000000
%TRACE-W-TRACEBACK, symbolic stack dump follows
image module routine line rel PC abs PC
CRASH_TEST CRASH_TEST SUB1 7 ...
CRASH_TEST CRASH_TEST CRASH_TEST 2 ....
...
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-03-2004 04:00 PM
тАО07-03-2004 04:00 PM
Solution$ r crash_test
calling lib$signal...
%NONAME-W-NOMSG, Message number 00000000
%TRACE-W-TRACEBACK, symbolic stack dump follows
image module routine line rel PC abs PC
CRASH_TEST 0 0000000000010170 0000000000010170
CRASH_TEST 0 0000000000010080 0000000000010080
0 0000000000000000 FFFFFFFF80B38AB0
0 0000000000000000 000000007AD4FE90
%SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=0000000000000000, PC=0000000000010170, PS=0000001B
%TRACE-F-TRACEBACK, symbolic stack dump follows
image module routine line rel PC abs PC
CRASH_TEST 0 0000000000010170 0000000000010170
CRASH_TEST 0 0000000000010080 0000000000010080
0 0000000000000000 FFFFFFFF80B38AB0
0 0000000000000000 000000007AD4FE90
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-04-2004 01:34 AM
тАО07-04-2004 01:34 AM
Re: ovms8.1 Linker lib$signal Traceback
Purely Personal Opinion
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-04-2004 03:13 PM
тАО07-04-2004 03:13 PM
Re: ovms8.1 Linker lib$signal Traceback
On Itanium systems even something as fundamental as the concept of a "PC" has changed. Compilers, DEBUG, exception handling and all that stuff has to change accordingly. There's also been an issue that the Intel object language doesn't have provision for source line correlation as we know it (which is what TRACE uses to generate detailed traceback information).
This is being (very) actively worked. You will see full traceback information eventually, but I don't think anyone's in a position to make any promises at the moment.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО07-08-2004 02:41 AM
тАО07-08-2004 02:41 AM
Re: ovms8.1 Linker lib$signal Traceback
I look forward to the vms8.2 release.
So far, my rx2600 seems to be doing pretty
well with a range of physics simulation programs written in standard Fortran...
Also, for a little shop in academia, it's heartening to see such a healthy VMS forum.
Cheers...
Charles Driscoll