[Info-vax] %SYSTEM-F-ACCVIO again

Arne Vajhøj arne at vajhoej.dk
Sun Apr 7 22:20:42 EDT 2024


On 4/7/2024 9:36 PM, motk wrote:
> $ help analyze
> 
>    Improperly handled condition, bad stack or no handler specified.
>      Signal arguments:   Number = 0000000000000005
>                          Name   = 000000000000000C
>                                   0000000000000004
>                                   00000000000007D8
>                                   FFFF830007C02367
>                                   0000000000000012
>      Register dump:
>      RAX = 000000007FF9DC80  RDI = 000000007FF9DC80  RSI = 00000000000007D8
>      RDX = 0000000000000000  RCX = 00000000000007D8  R8  = 00000000FFFF8F84
>      R9  = 000000000808080D  RBX = 000000007FFABE00  RBP = 000000007FF9E4A0
>      R10 = 000000007FFABDB0  R11 = 000000007FFA4D18  R12 = 000000007FF9C648
>      R13 = 0000000000000018  R14 = 000000007FF9C800  R15 = 0000000000008301
>      RIP = FFFF830007C02367  RSP = 000000007FF9E440  SS  = 000000000000001B
> %SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual 
> address=000000000000000C, PC=0000000000000002, PS=7AD44D2F
> 
>    Improperly handled condition, bad stack or no handler specified.
>      Signal arguments:   Number = 0000000000000005
>                          Name   = 000000000000000C
>                                   0000000000000014
>                                   0000000000000000
>                                   0000000000000000
>                                   0000000000000012
>      Register dump:
>      RAX = 0000000000000001  RDI = FFFFFFFF776521E8  RSI = 00000000020C0001
>      RDX = 0000000000000000  RCX = FFFFFFFF8AC09B5E  R8  = 000000007ACBD11F
>      R9  = 0000000004000106  RBX = 000000007FFABE00  RBP = 000000007FF9D568
>      R10 = 000000007FFA4D18  R11 = 000000007FFA4D18  R12 = 000000007FF9D520
>      R13 = 000000007FFCDCAC  R14 = 0000000000000002  R15 = 000000004B9E8301
> Connection to 192.168.188.121 closed.000007FF9CA30  SS  = 000000000000001B

I am getting the idea that VMS does not like your VM.

It seems unlikely to me that:

$ product list *
$ help analyze

trigger some x86-64 specific DCL or RMS bug that nobody else has
encountered.

I consider it more likely that VMS and the CPU/virtual memory
environment your VM provide disagree on something causing
random sporadic memory related errors.

But then this stuff is way outside of my expertise area
so I am probably wrong.

Arne




More information about the Info-vax mailing list