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

motk meh at meh.meh
Sat Apr 6 05:39:20 EDT 2024


On 5/04/2024 11:20 pm, Simon Clubley wrote:

> Another idea: If this really is an executive mode failure, I wonder if
> setting BUGCHECKFATAL to 1 would be useful here ?
> 
> Alex: What this would do is to turn the failure into a failure that
> crashes the system (and writes a dumpfile, assuming the VSI virtual
> image is setup correctly) instead of just deleting the current process.
> 
> It would also mean anything in memory (including command history, etc)
> would be written to the dumpfile, so make sure there's nothing private
> in the memory of your system before performing more tests.
> 
> What you could do then is to compress the dumpfile and send it to VSI
> privately via some means they give you.
> 
> BTW, another idea: does x86-64 VMS currently write an entry into the
> errorlog on an executive mode bugcheck ? I wonder if it would be useful
> to check the errorlog to see if there is anything useful there from the
> previous failure ?

Found some time today to try installing Apache, trying random 
half-remembered commands and looking through documentation that just 
talks about AXP and Integrity stuff, and lo:

$ show proc

   Improperly handled condition, bad stack or no handler specified.
     Signal arguments:   Number = 0000000000000005
                         Name   = 000000000000000C
                                  0000000000000004
                                  0000000000000878
                                  FFFF830007C02367
                                  0000000000000012
     Register dump:
     RAX = 000000007FF9DC80  RDI = 000000007FF9DC80  RSI = 0000000000000878
     RDX = 0000000000000000  RCX = 0000000000000878  R8  = 00000000FFFF8F81
     R9  = 000000000808080D  RBX = 000000007FFABE00  RBP = 000000007FF9E540
     R10 = 000000007FFABDB0  R11 = 000000007FFA4D18  R12 = 000000007FF9C648
     R13 = 0000000000000018  R14 = 000000007FF9C800  R15 = 0000000000000201
     RIP = FFFF830007C02367  RSP = 000000007FF9E4E0  SS  = 000000000000001B
%SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual 
address=000000000000
000C, PC=0000000000000002, PS=7AD82CC6

   Improperly handled condition, bad stack or no handler specified.
     Signal arguments:   Number = 0000000000000005
                         Name   = 000000000000000C
                                  0000000000000000
                                  8000000000000000
                                  000000007AE15900
                                  0000000000000012
     Register dump:
     RAX = 0000000000000001  RDI = FFFFFFFF77761C88  RSI = 0000000002040001
     RDX = 0000000000000000  RCX = FFFFFFFF8AC09B5E  R8  = 000000007ACBD11F
     R9  = 0000000000000106  RBX = 000000007FFABE00  RBP = 000000007FF9D608
     R10 = 000000007FFA4D18  R11 = 000000007FFA4D18  R12 = 000000007FF9D5C0
     R13 = 000000007FFCDCAC  R14 = 0000000000000002  R15 = 0000000045178301
Connection closed by foreign host.000000007FF9CA28  SS  = 000000000000001B

Now I'll try and work out where dumpfiles go - I did turn on 
SYSTEM_CHECK and write it to CURRENT so hopefully it's there somewhere.

> Simon.
> 
> PS: pointed message to VSI management: A hobbyist has just appeared to
> find a process-deleting bug within VMS that your testing has missed so far.
> _This_ is an example of why the hobbyist program is important, and of
> benefit, to you.

Yeah, noobs do non-obvious stuff and find weird edge cases.
  --
motk




More information about the Info-vax mailing list