[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference azur::mcc

Title:DECmcc user notes file. Does not replace IPMT.
Notice:Use IPMT for problems. Newsletter location in note 6187
Moderator:TAEC::BEROUD
Created:Mon Aug 21 1989
Last Modified:Wed Jun 04 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:6497
Total number of notes:27359

5467.0. "Access Violation (from a Thread?)" by SUBWAY::YANNIOS () Wed Aug 11 1993 15:47

    While running DECmcc in command line mode, the following error ocurrs:

    MCC V1.3 access violation occurs:
    
MCC>
%CMA-F-EXCCOP, exception raised; VMS condition code follows
-SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=00000000, PC
=009FF48A, PSL=03C00009

%TRACE-F-TRACEBACK, symbolic stack dump follows
module name     routine name                     line       rel PC    abs PC

                                                           0004B8C4  0004B8C4
                                                           0007C782  0007C782
                                                           000775DC  000775DC
                                                           0007AC78  0007AC78
%SMG-F-INVKBD_ID, invalid keyboard-id

T.RTitleUserPersonal
Name
DateLines
5467.1Threads version?TRKWSH::COMFORTHere beside the rising tideWed Aug 11 1993 18:3011
    
    Just to check, do have the CMA threads library
    
    	SYS$COMMON:[SYSLIB]CMA$OPEN_RTL.EXE
    
    	image name: "CMA$OPEN_RTL"
        image file identification: "CMA V1.10-030"
    
    Installed from the MCC distribution?
    
    Dave 
5467.2we have correct versionSUBWAY::YANNIOSThu Aug 12 1993 00:3911
    Yup.  this is the correct version.
    
    This happened on a window running MCC command line mode.  In this
    window, we had over 50 alarm rules active and polling various areas
    of the network.  We suspect that it occurred when one of the systems
    that was being polled for X.25 Circuit information ran out of
    process control slots because there were  many NML processes
    running.  
    
    /nick