[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

11.0. "PROBLEM - SOME VERBS cause an ACCESS VIOLATION" by KETJE::PACCO () Fri Sep 22 1989 04:44

    I am writing a test AM called "TIMER" using the T1.0.0 field test SW.
    
    I defined e.g. the verbs SHOW,CREATE,DELETE,ENABLE,...
    
    All SHOW commands works as expected.
    CREATE, DELETE, ENABLE e.g. gives a problem.  The command line is
    beeing parsed without error, and then I get immediately the ACCVIO.  I
    cannot locate where the error is produced, but it is BEFORE the access
    module is beeing accessed.
    
    If I give the commands:
    $MCC <return>
    MCC> CREATE TIMER "xxx"
    this results in an access violation:
    %SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual
    addres=00000004, PC=0031792A, PSL=03C00004
    
    However, if I give the following command:
    $ MCC CREATE TIMER "xxx"
    the CONTROL FM passes the call correctly to my access module.
    
    The use of MCCDEB works also as expected.
    
    Has anybody an Idea for this difference in behaviour of MCC ?
    
    	Dominique.
T.RTitleUserPersonal
Name		DateLines
11.1PROBLEM - additional findings.KETJE::PACCOFri Sep 22 1989 07:1912
    Another finding around this problem is:
    
    If I create a command file MCC.COM containing:
    SHOW TIMER "xxx" ALL CHARACTERISTICS
    CREATE TIMER "xxx"
    SHOW TIMER "xxx" ALL CHARACTERISTICS
    
    and execute the command
    $MCC DO MCC.COM
    then everything works fine !
    
    Dominique.
11.2INFO - Known bugTOOK::CHANLIZARDOMon Sep 25 1989 14:0313
    This is the same problem as QAR #140.  The problem occurs in the
    command completion section of the TRM.  It happens in the case when
    arguments are all optional, and none of them are specified at the
    user interface.  The access violation will not occur if you enter
    at least one argument in the command.
    
    The reason why it works in a command file, is because command prompting
    is turned off in the command file mode.
    
    This bug should have been fixed in the X0.08.0 build.
    
    Christine