🚀 go-pugleaf

In article <299@cgi.UUCP>, baw@cgi.UUCP (Barry Waters) writes:
> I have a problem that >seems< to be internals oriented so I will
> post it here. I have a program that is linked with several shareable
> images (RTLs). This program is submitted to a batch queue nightly.
> Every fouth or fifth night the guy suffers an access violation and
> produces a trace back dump in the .LOG file produced by the batch 
> handler.
> 

From your example, I would guess that your test method is flawed and that
you are looking at two different problems:

> 	%SYSTEM-F-ACCVIO, access violation, reason mask=00,
>         virtual address=00000018, PC=0011037f, PSL=03c00004
> 

> 	%SYSTEM-F-ACCVIO, access violation, reason mask=00,
>         virtual address=0000000, PC=00095632, PSL=03c00004
> 


Regardless of where the shareable image lands in memory, the address of
the failure modulo 512 (200 hex) should always be the same. Note in
your examples that they are not. (17f != 032)


Have you tried enabling process image dumping (SET PROC/DUMP)?


I have some practice in hunting these kinds of things down. (Ever hear
of the DECUS UUCP "Infamous Access Violation"?) Let me know if you need
some further assistance.

--- Tom
Tom Allebrandi             | Mail guru   - DECUS UUCP Development Team
Inland Steel Research Labs | NFS grunt   - CMU/Tek-IP
East Chicago, IN           | Chairperson - VMSnet Working Group, DECUS VAX SIG
219 399 6306               | Internet:  allebrandi@inland.com
DECUServe: allebrandi      | UUCP:      ...!uunet!inland!allebrandi