VSI BASIC x86-64 V1.9-001

[cct]

Just installed this on VMS9.2-2 with VMS922X_UPDATE V2.0

Recompiled all basic source - no errors

However I got a memory management error in a routine I wrote to analyse source code to map modules and calls - when my previous employer moved to I64, I lost SCA.
There were a whole series of them after the first 20 or so files.

This opens a large number of source files, and reads through them, within an error trap.

So I compiled and link with debug and tried to run...

Long series of %DEBUG-I-EXPMEMPOOL, expanding debugger memory pool, following by:

%SYSTEM-F-ACCVIO, access violation, reason mask=04, virtual address=000000000000
004F, PC=000000008002B8E1, PS=0000001B

before I got into any of the code.

Is the debug issues unresolved? Will this come in V9.2-3?

[jreagan]

There is a DEBUG ECO for V9.2-2 systems that should be out very soon. That is MUCH better and should resolve that expanding memory pool bug and lots of other debugger-related issues (ACCVIOs, looping, etc)

[cct]

Brilliant, many thanks

Chris

[jreagan]

Great. Let us know if you need anything.

[jorozco@siatecmex.com]

We have our system running on an HP Itanium X86 server. We are now testing OpenVMS V9.2-2 running on ESXI V7.0. with VSI-X86VMS-BASIC-X0108-5-1
Today I compiled and linked all our source programs, and when I ran them, I got the error: %BAS-F-MEMMANVIO, Memory management violation.

It's good to know that it's being reviewed and that there will be a fix soon. I'll be waiting to install the update as soon as it's released.


jorozco

[cct]

There is a DEBUG ECO for V9.2-2 systems that should be out very soon. That is MUCH better and should resolve that expanding memory pool bug and lots of other debugger-related issues (ACCVIOs, looping, etc)

Installed on an up to date V9,2-2, but doesn't seem to help

Code: Select all

1 $ prod show hist/sin=01-aug
------------------------------------ ----------- ----------- --- -----------
PRODUCT                              KIT TYPE    OPERATION   VAL DATE
------------------------------------ ----------- ----------- --- -----------
VSI X86VMS VMS922X_DEBUG V1.0        Patch       Install     Val 12-AUG-2024
VSI X86VMS BASIC V1.9-1              Full LP     Install     Val 01-AUG-2024
VSI X86VMS BASIC X1.8-5              Full LP     Remove       -  01-AUG-2024
------------------------------------ ----------- ----------- --- -----------
3 items found

I did notice that I had to reboot before the debugger saw any source code - weird

Running under debug gives, after an initial STEP:

Code: Select all

DBG> Step
%DEBUG-W-BADSTACK, WARNING: stack corrupted; session integrity not guaranteed
%SYSTEM-F-ACCVIO, access violation, reason mask=04, virtual address=000000000000
004F, PC=000000008002B8E1, PS=0000001B
SP 1 $

The install log looked ok:

Code: Select all

SYS-1> PRODUCT INSTALL VMS922X_DEBUG

Performing product kit validation of signed kits ...
%PCSI-I-VSIVALPASSED, validation of DKA0:[TOWNLEYC.KITS]VSI-X86VMS-VMS922X_DEBUG-V0100--4.PCSI$COMPRESSED;1 succeeded

The following product has been selected:
    VSI X86VMS VMS922X_DEBUG V1.0          Patch (remedial update)

Do you want to continue? [YES]

Configuration phase starting ...

You will be asked to choose options, if any, for each selected product and for
any products that may be installed to satisfy software dependency requirements.

Configuring VSI X86VMS VMS922X_DEBUG V1.0: Remedial ECO patch kit DEBUG V1.0

    Copyright 2024 VMS Software, Inc.

  VMS Software, Inc. recommends that you backup your system disk
  before installing any patches.

    This ECO kit will make functional changes to your system.
    Before installing this kit, you should make a backup copy of your
    system disk.  Without a backup copy, you may not be able to restore
    your system to a pre-installation state should the need arise.

  Do you want to continue? [YES]

  This ECO kit does not require a system reboot after installation.

  Do you want to continue? [YES]

  Recovery data will automatically be saved which will allow you to un-install
  this kit using PRODUCT UNDO PATCH, should that be necessary.

    The UNDO PATCH mechanism has a limited lifetime, since any saved recovery
    data is deleted when any new or updated full product kit is installed.
    Recovery data from multiple patch kits can be saved for any potential
    UNDO PATCH operations until that time.

  In the past, kit installations provided some limited help for manually
  un-installing particular images or files from a patch kit.
  This was accomplished by keeping a copy of replaced images or files,
  with the string "_OLD" added to the end of the file name.

    These saved copies are not restored by any automated process.  It would
    depend on an experienced system manager to rename or copy any key images
    or files back to their original name to workaround a particular
    incompatibility or other issue.

    If you wish, you may continue keeping a copy of replaced files with "_OLD"
    appended to the name.  VMS Software, Inc. recommends that this technique
    only be used by an experienced system manager.  Note that this will triple
    the disk space required for this kit:  once for the installed kit files,
    once for the saved recovery data, and once for the saved "_OLD" files.

  Should an "_OLD" copy of each replaced file be saved? [NO]

    Copies of replaced files will not be saved.

* This product does not have any configuration options.

Execution phase starting ...

The following product will be installed to destination:
    VSI X86VMS VMS922X_DEBUG V1.0          DISK$X86SYS:[VMS$COMMON.]

Portion done: 0%...30%...80%...90%
...100%

The following product has been installed (and a recovery data set created):
    VSI X86VMS VMS922X_DEBUG V1.0          Patch (maintenance update)

VSI X86VMS VMS922X_DEBUG V1.0: Remedial ECO patch kit DEBUG V1.0

    Release notes from this patch kit are available in SYS$HELP.

    The PCSI kit release notes are copied to the system disk during kit
    installation and are available as a standard text file which may be
    read using the TYPE command or from an editor:

        SYS$HELP:VMS922X_DEBUG-V0100.RELEASE_NOTES

SYS-1>

Any ideas?

[jreagan]

I don't get the reboot to see sources.

The ACCVIO only occurs with the debugger? Doing a RUN/NODEBUG and it still ACCVIOs?

(The BADSTACK is a known issue and is only actually cosmetic)

Just guessing, but can you try to LINK with /SEG=CODE=p0 and see if that makes a difference?

If not, then we'll need a reproducer of some kind to sort it out.

John

[cct]

I am linking /SEGMENT=CODE=P0

I was also getting:

%DEBUG-I-EXPMEMPOOL, expanding debugger memory pool
%BAS-F-PROLOSSOR, Internal error in BASIC Run-Time Library. Please submit an SPR

and just dropping to the command prompt.

I will try to create a reproducer

[jreagan]

I thought the new debugger would resolve the EXPMEMPOOL, but who knows?

I've never seen that PROLOSSOR error before. Please for a reproducer.

[dgordon]

PROLOSSOR - Hah! I remember when some ancient DEC (pretty sure BASIC) compiler would occasionally emit "Program lost, Sorry." as a message.