Conference azur::mcc

Bill,

	1. What version are you running?
	2. What were you doing when whr XtWarning appeared?
	3. Can you consistently duplicate the XtWarning?

My guess is that the XtWarning is directly responsible for the ensuing
acc-vio, even though they were spaced out in time.

Fred

    
    V1.1 SSB 
    
    With a new session I got the following while doing a simple close of a
    window after showing the char for a phy ent.
    
    
    $ MAN/ENT/INT=DECW
    %SYSTEM-F-ACCVIO, access violation, reason mask=01, virtual
    address=03268009, PC
    =003ABAF8, PSL=03C00000
    
    
    The window  doesn't close and if I do another sh char I get another
    accvio.
    

    Other relevant info is -
    
    
VIRTUALPAGECNT             123536       9216       512   1000000 Pages      

Username: WADE                             Owner:  BILL WADE
Account:  NIT                              UIC:    [66,1] ([WADE])
CLI:      DCL                              Tables: DCLTABLES
Default:  USER$DISK:[WADE]
LGICMD:   LOGIN
Flags: 
Primary days:   Mon Tue Wed Thu Fri        
Secondary days:                     Sat Sun
No access restrictions
Expiration:            (none)    Pwdminimum:  6   Login Fails:     0
Pwdlifetime:         90 00:00    Pwdchange:  21-MAR-1991 10:50 
Last Login:  5-JUN-1991 08:47 (interactive),  5-JUN-1991 13:26 (non-interactive)
Maxjobs:         0  Fillm:       100  Bytlm:        40000
Maxacctjobs:     0  Shrfillm:      0  Pbytlm:           0
Maxdetach:       0  BIOlm:        40  JTquota:       1024
Prclm:           2  DIOlm:        18  WSdef:         2048
Prio:            4  ASTlm:        48  WSquo:        10000
Queprio:         0  TQElm:       128  WSextent:     20000
CPU:        (none)  Enqlm:       512  Pgflquo:      40000
                      

    
    Bill,
    Had you enabled notification from the FILE menu?
    I presume this is the sequence that lead to the acc-vio:
      1. man/enter/i=d                                         
      2. open domain
      3. double-click on a bridge icon
      4. select physical entry
      5. pull down Operations menu
      6. select show char
      7. pull down FILE in the map window
      8. select close
    Is this the minimum sequence neede to cause the acc-vio?
    
    Fred

    Fred,
    
    Notification was enabled and that is the sequence.
    

    addendum to .4
    
    I was closing the management window not  the map window.
    

      1. man/enter/i=d                                         
      2. open domain
      3. double-click on a bridge icon
      4a. select forw data
      4b. select physical entry
      4c. click on an instance of physical entry
      5. pull down Operations menu
      6. select show char
      7. click on close window
   

Bill,

Try the same sequence without enabling notification.

Fred

Bill,

A few more questions:

	Each time this acc-vio occurs, is it always preceded by X errors?
	Does the same thing occur if notification is not enabled?
	Does the same thing occur if you show another partition?
	Are you closing the management window after the operation has completed
	and the information is displayed?
	Does the same thing occur if you close the map window?

Thanks,
Verna

   re. 6
   >      
   > Try the same sequence without enabling notification.
   >      
	With notification disabled - no change.

    	bill
    

    
    re .7

   > 
   > Each time this acc-vio occurs, is it always preceded by X errors?

	no - re .2

   > Does the same thing occur if notification is not enabled?

	yes

   >  Does the same thing occur if you show another partition?

     	yes

   > Are you closing the management window after the operation has completed
   > and information is displayed?

	yes

   > Does the same thing occur if you close the map window?

	if I select "Close Window" from the File option (after an accvio
        has been returned from a close management window operation) I get -

	"Map window Mesage: Software error:An internal error has occurred in
	the Iconic Map PM."        

	and the window is frozen.  I have to CTRL/Y from the DCL window
	to get out.  This is the output when I CTRL/Y -

$ man/ent/int=decw
X Toolkit Warning: BadMatch - parameter mismatch
%SYSTEM-F-ACCVIO, access violation, reason mask=01, virtual address=03268009,
PC
=003ABAF8, PSL=03C00000
%SYSTEM-F-ACCVIO, access violation, reason mask=01, virtual address=03268009,
PC
=003ABAF8, PSL=03C00000
%MCC-F-FATAL_FW, fatal framework condition:  Failed to dequeue next ready
thread
%MCC-F-FATAL_FW, fatal framework condition:  Failed to dequeue next ready
thread
%MCC-E-ABORTCTRLY, image aborted by Ctrl\Y
$

bill