Path: news.eternal-september.org!eternal-september.org!.POSTED!not-for-mail
From: hb0815 <mw40171@mucweb.de>
Newsgroups: comp.os.vms
Subject: Re: Xephyr (on Linux host) and VMS keyboard
Date: Thu, 19 Jun 2025 12:55:27 +0200
Organization: A noiseless patient Spider
Lines: 83
Message-ID: <1030qav$3qpvm$1@dont-email.me>
References: <slrn104g8g6.3jp.JKB@hilbert.systella.fr>
 <1029tt4$1drvn$3@dont-email.me> <slrn104oi98.343.JKB@hilbert.systella.fr>
 <102hoo1$3j0ir$1@dont-email.me> <slrn104qtl9.rn4.JKB@hilbert.systella.fr>
 <102k4a3$8u3d$2@dont-email.me> <slrn104vi88.rn4.JKB@hilbert.systella.fr>
 <102pbi9$1m0b0$1@dont-email.me> <slrn1052600.rn4.JKB@hilbert.systella.fr>
 <102sp76$2lchr$4@dont-email.me> <slrn1054sog.rn4.JKB@hilbert.systella.fr>
 <102tuei$318iu$1@dont-email.me> <slrn10555f6.rn4.JKB@hilbert.systella.fr>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Thu, 19 Jun 2025 12:55:27 +0200 (CEST)
Injection-Info: dont-email.me; posting-host="c2185c84541f09ee44ec825470fe9b2f";
	logging-data="4024310"; mail-complaints-to="abuse@eternal-september.org";	posting-account="U2FsdGVkX1/pWbIaBayPqxtWf1yKmOVX"
User-Agent: Mozilla Thunderbird
Cancel-Lock: sha1:p5kAgMrgE+4XtGGHesx+JA6W4dY=
In-Reply-To: <slrn10555f6.rn4.JKB@hilbert.systella.fr>
Content-Language: en-US

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

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

>> 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? 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.

> 
> 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.