Conference turris::debug

1859.0. "Accvio in windows debug - is vms 7.0 needed?" by CSC32::D_BUTLER () Wed Apr 16 1997 13:33

Hi my customer is getting a debugger error the info is below:

------------------------------------------------------------------------
------------------------------------------------------------------------

Access violation is from the debugger when it comes on the decwindows
not the program... Can you help or is this dec windows.

      System JOE is a AlphaServer 2100 4/233 running VMS V6.2 in a
    VAXcluster.

Logging enabled - this is being written to log file DBGERR.LOG

The following information may be helpful to the DEBUG maintainers.

If you wish to report this problem please include:

     o The stack dump that follows.
     o The debugger version number.
     o The program being debugged, both source and image.
     o The last, if not all, commands entered to the debugger.
     o Any other information that may be helpful.

The version of the debugger is: OpenVMS Alpha DEBUG Version V6.2-100

When I run the debugger on an alpha 2100 with vms 6-2 i get this stack dump
when the debugger opens on a exported display ( vaxstation 3100 ).  


%DEBUG-I-INITIAL, language is C, module set to FINWFRYLD
%DEBUG-I-NOTATMAIN, type GO to get to start of main program
%DEBUG-W-SCRNOSRCLIN, no source line for address 00030000 for display in
Source View
DBG>
%DEBUG-F-ACCVIO, access violation, reason mask=04, virtual address=00000000,


Due to this internal error this debugging session may be unreliable.
------------------------------------------------------------------------
------------------------------------------------------------------------


I realize that the info is a little scattered but I am not familiar with 
debugging in windows mode. Any comment appreciated.

DB/CSC

Are they getting the source browser ACCVIO after RERUNing a 
program, or after RUNing a program.  If the former, there is
an ECO kit out there which fixes this problem.

Mary