Conference turris::lse_bugs

1544.0. "LSE Accvio when exit-ing from DecWindows" by UTRTSC::DORLAND (The Wizard of Odz2) Mon Apr 14 1997 10:42

    Hello,
    
    a customer reports a bug which I cannot reproduce , but maybe
    someone knows about it...
    
    When running LSE in a DecWindows environment, and starting LSE
    directly from the session manager, the session will end with
    an ACCVIO when you exit or quit the LSE session.
    (See 'log' below)
    
    This problem does not occur if you start LSE from a Decterm with
    $LSE/INTERF=DECWINDOWS. This is LSE 4.4-5 on VAX/VMS 5.5-2H4.
    
    Has anyone seen this before?
    
    Thanks in advance,
    
    Ton Dorland
    

Memory address or size is NULL

Fatal LSEDIT internal error, please submit an SPR including:

     1.  A description of the actions that revealed the bug
     2.  The versions of LSE and the operating system you are running
     3.  Machine-readable media containing:
        a. The source files of your LSE section, command,
           initialization, and environment files
        b. Copies of the data files used during the session
        c. The journal file if one exists
        d. The LSE_ERROR.LOG and SCA_ERROR.LOG files if they exist
     4.  Your terminal characteristics, if applicable
     5.  A description of the command line used to invoke LSE

Message number 00000004
Memory deallocation failure
Memory already free
Message number 000BFCA0
Disk quotas not enabled on this volume
Normal successful completion
Message number 0047AE10
Disk quotas not enabled on this volume
Message number 014B6948
Message number 000BB018
Magnetic tape volume label can be no more than six characters
Normal successful completion
Magnetic tape volume label can be no more than six characters
Message number 014B6948
%LSE-I-ERRORINFO1, Please see the LSE release notes for information on reporting
 problems.
%LSE-I-ERRORINFO2, Please include the following information in the problem repor
t:


LSESHR base:          003410BC
Screen updater ident: DECTPU X3.1  1992-08-25 07:20
Screen updater base:  004E6034
Screen updater file:  DECWINDOWS

%SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=7EE78E20, PC
=80474CBC, PS=0000001B
%TRACE-F-TRACEBACK, symbolic stack dump follows
 Image Name   Module Name     Routine Name    Line Number  rel PC      abs PC
                                                        0 80474CBC    80474CBC
                                                        0 804754A8    804754A8
 TRACE                                                  0 00023704    0038B704
 LSESHR       LSE$$TRACEBACK  LSE$$TRACEBACK         1065 000002C0    000F8AA0
 LSESHR       LSE$SHARE       LSE$$HANDLER           2780 00003198    000B7048
 LSESHR                                                 0 002E328C    0032528C
 LSESHR       LSE$SHARE       LSE$HANDLER            1478 00000858    000B4708
                                                        0 80495D44    80495D44
%SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=7EE78E20, PC
=80474CBC, PS=0000001B

  Improperly handled condition, image exit forced.
    Signal arguments:   Number = 00000005
                        Name   = 0000000C
                                 00000000
                                 7EE78E20
                                 80474CBC
                                 0000001B

    Hi Ton,
    
    That's a rather strange set of error messages. :-) What was the
    customer editing, and on what kind of device? If the customer is on a
    cluster, does this occur from other workstations in the cluster?
    
    Looking through the LSE conferences, I found a couple of other reports
    of LSE crashes after exiting from a session initiated via the Session
    Manager. However, they were from back in LSE V4.0 days, and the
    messages bear no resemblence to the ones you posted. Was there an
    LSE_ERROR.LOG file?
    
    What we really need in order to diagnose this is a reproducible
    example.
    
    -- Daryl