Re: Xephyr (on Linux host) and VMS keyboard

Le 19-06-2025, hb0815 <mw40171@mucweb.de> a écrit :

On 6/18/25 12:33, JKB wrote:

...
Thanks, I have set term/inquire in sys$login:login.com. Modification
done, but doesn't fix access violation error.
...

>
I didn't expect this to fix the ACCVIO. To me, it only proves that your
login.com is being executed here.
>

$ analyze /process_dump DECW$WSINIT.DMP
Condition signalled to take dump:
%SYSTEM-F-ACCVIO, access violation, reason mask=01, virtual address=1211100F, PC
=80000010, PSL=03C00004
 
         OpenVMS VAX Debug Version V7.3-017
 
 
DBG> examine/instruction 2147483664
2147483664:     CALLG    B^4(SP),(R1)
DBG> display reg
DBG>
 
How can I display registers ?

>
You already know their exact contents from the register dump.
>
To match with the register dump and/or the above ACCVIO message:
DBG> set rad hex
>
To see all register contents
DBG> ex %r0:r15

Done:

DBG> ex %r0:r15
0\%R0:  03C00000
0\%R1:  1211100F
0\%R2:  00000020
0\%R3:  00000000
0\%R4:  002EA6D0
0\%R5:  00000000
0\%R6:  000034E0
0\%R7:  00000210
0\%R8:  00000210
0\%R9:  00000001
0\%R10: 7FFED7D4
0\%R11: 7FFE2BDC
0\%AP:  7FE95E58
0\%FP:  7FE95F10
0\%SP:  7FE95E58
0\%PC:  80000010

The CALLG uses an argument list, which is on the stack. Maybe you can
find something useful on the stack.

Unfortunately...
DBG> show stack
%DEBUG-W-BADSTACK, WARNING: stack corrupted; session integrity not guaranteed

In the log file, is there any message about not being able to create a
process dump?
>

 
Nope 🙁

>
You connect to XDM on the VAX, correct?

Right.

That is, DECW$WSINIT runs in the
context of the TCPIP$XDM user. In case there is a resource problem, it
may not be possible to write a process dump, just because doing so
requires resources, too. It's not obvious whether that is the case or
not. The fact that you get a process dump for the same ACCVIO when
running DECW$WSINIT interactively, indicates that the underlying problem
for the ACCVIO is not a resources problem.
>

I have set accounting before posting. Strangely, all ACCVIO are
not loggued.

>
I'm not sure I understand what you mean.

I have set accounting/image. Thus, all ACCVIO should be stored. To
be clear, as DECW$WSINIT crashes with ACCVIO after xdm connection, I
must have one new record with ACCVIO error after each connection.
Only a few ACCVIO seem to be recorded.

 
DECW$WSINIT Image Termination
-----------------------------
Username:          BERTRAND          UIC:               [BERTRAND]            
Account:                             Finish time:       14-JUN-2025 15:23:09.75
Process ID:        00000131          Start time:        14-JUN-2025 15:23:07.67
Owner ID:                            Elapsed time:                0 00:00:02.08
Terminal name:                       Processor time:              0 00:00:01.52
Remote node addr:                    Priority:          4 
Remote node name:                    Privilege <31-00>: 00108000
Remote ID:                           Privilege <63-32>: 00000000
Remote full name:                                                             
Queue entry:                         Final status code: 1000000C
Queue name:                                      
Job name:                                                
Final status text: %SYSTEM-F-ACCVIO, access violation, reason mask=!XB, virtual
 
Page faults:              939        Direct IO:                  8
Page fault reads:          42        Buffered IO:              121
Peak working set:        1482        Volumes mounted:            0
Peak page file:          2578        Images executed:            3
                                                                             
Image name: FERMAT$DUA0:[SYS0.SYSCOMMON.][SYSEXE]DECW$WSINIT.EXE       

>
The ACCVIO is logged - as well as it can be logged by the accounting
facility. The “Final status code” is translaated to “%SYSTEM-F-ACCVIO”,
but information about the PC etc. is not available at the time the
program terminates.

Best regards,

JB