DEBUG (DECwindows) MESSAGE — VMS 5.5
=Title Non-Debugger Message
No online help is available for this diagnostic
message.
Diagnostic messages for all VMS components and
utilities are explained in the VMS System Messages
and Recovery Procedures Volume, where they are
listed alphabetically by ident.
Additional information available:
DEBUG-ABORTEDDEBUG-ABSDATSYNDEBUG-ACCADDCOMDEBUG-ACTIVATING
DEBUG-ADDRANCOVDEBUG-ADDRESSMODEDEBUG-ADDRMBZDEBUG-ADDRREG
DEBUG-AMBFIELDDEBUG-AMBIGQUALDEBUG-AMPERSANDDEBUG-ASTWASDISABLED
DEBUG-ASTWASENABLEDDEBUG-ATTACHEDDEBUG-ATTREQREF
DEBUG-BADADDSPADEBUG-BADADDSTADEBUG-BADBODPACKDEBUG-BADDESCR
DEBUG-BADDISCVALDEBUG-BADDSTDEBUG-BADEVNPARDEBUG-BADEXH
DEBUG-BADFRAMEDEBUG-BADHANDLEDEBUG-BADOPCODEDEBUG-BADPARAM
DEBUG-BADSCOPEDEBUG-BADSIGARGDEBUG-BADSTACKDEBUG-BADSTARTPC
DEBUG-BADSTATUSDEBUG-BADSUBPARDEBUG-BADTAGVALDEBUG-BADTARGET
DEBUG-BADUSEPACKDEBUG-BADUSREVNTDEBUG-BADWATCHDEBUG-BADWIDGET
DEBUG-BASVARNOTSETDEBUG-BITRANGEDEBUG-BPTDIFMOD
DEBUG-BPTONDATADEBUG-BUFFEROVFDEBUG-BWLGISMUSDEBUG-CANBRKWAT
DEBUG-CANTACCESSMAINDEBUG-CANTCREATEMAINDEBUG-CANTGETFID
DEBUG-CANTINTPRODEBUG-CANTOPNIMGDEBUG-CANTPASTDEBUG-CIREXLST
DEBUG-CLIBRDFAIDEBUG-CLIBRDLCKDEBUG-CMDISCORDEBUG-CMDISOBS
DEBUG-CMDNOTDWDEBUG-CMDNOTONEDEBUG-CMDSYNERRDEBUG-CMPNOTFND
DEBUG-CNTRLWRDNOTACCESSDEBUG-CONFLICTDEBUG-CONFROMEXC
DEBUG-CONSTRCOMPDEBUG-CPOSTDECRDEBUG-CPOSTINCRDEBUG-CPREDECR
DEBUG-CPREINCRDEBUG-CRMPSCFAILDEBUG-CVTNEGUNSDEBUG-DBGERR
DEBUG-DBGSTOPPEDDEBUG-DECLARERRDEBUG-DECOVFDEBUG-DECROPRAND
DEBUG-DEFKEYDEBUG-DEFKEYERRDEBUG-DEFTOORECDEBUG-DELKEY
DEBUG-DELKEYERRDEBUG-DELTIMTOODEBUG-DESCNOTSETDEBUG-DISABLEAST
DEBUG-DISNAMREQDEBUG-DISNOTSELDEBUG-DISPEXISTSDEBUG-DISPRLENSIZ
DEBUG-DIVBYZERODEBUG-DSTERRGDEBUG-DSTNESDEPDEBUG-DUPLVQUAL
DEBUG-DWERRDEBUG-DWNOT1PROCDEBUG-DYNIMGSETDEBUG-DYNMODSET
DEBUG-EDITDISVERDEBUG-EDITERRORDEBUG-EDITFILEDEBUG-EDITNOFILE
DEBUG-EDITREVVERDEBUG-ENABLEASTDEBUG-ENTRYMASKDEBUG-ENUMRANGE
DEBUG-ERRACTIMGDEBUG-ERRASSIGNDEBUG-ERRCLSFILEDEBUG-ERRCRELNM
DEBUG-ERRDEASSIGNDEBUG-ERRFAODEBUG-ERRGETDVIDEBUG-ERRGETEF
DEBUG-ERRINSDECDEBUG-ERRINSIGNALDEBUG-ERRINVEDITDEBUG-ERROR
DEBUG-ERRORLIMITDEBUG-ERROR_BLOCKDEBUG-ERRQIOW
DEBUG-ERRSMGDEBUG-ERRSYSSERVDEBUG-ERRTARGOPDEBUG-ERRUSREVNT
DEBUG-EXABEYREGDEBUG-EXARANGEDEBUG-EXCBREREPDEBUG-EXCDURCAL
DEBUG-EXITARGDEBUG-EXITERRDEBUG-EXITSTATUSDEBUG-EXPMEMPOOL
DEBUG-FAILFINDIMGDEBUG-FAILHEIRKYDEBUG-FAILXTINITDEBUG-FATALSTATUS
DEBUG-FILEUNALDEBUG-FLTOVFDEBUG-HEIGHTDIFFDEBUG-IDENTLONG
DEBUG-IFIXUNDDEBUG-IFLTUNDDEBUG-IINTOVFDEBUG-ILLADDCON
DEBUG-ILLASTERDEBUG-ILLDEFNAMDEBUG-ILLENUMVALDEBUG-ILLEVNSTR
DEBUG-ILLFILPTRDEBUG-ILLFLOATDEBUG-ILLINVNUMDEBUG-ILLLENGTH
DEBUG-ILLNUMPATHDEBUG-ILLPACSIZDEBUG-ILLPATH1DEBUG-ILLPATH2
DEBUG-ILLPATHELEMDEBUG-ILLPATHIDENTDEBUG-ILLPOSFLDDEBUG-ILLQUALIF
DEBUG-ILLRANGEDEBUG-ILLSETCONDEBUG-ILLSIGEXTDEBUG-ILLSIZFLD
DEBUG-ILLSUBLENDEBUG-ILLSUBSTRDEBUG-ILLTYPEDEBUG-ILLVQUAL
DEBUG-INCDSTNESDEBUG-INCOMPOPRDEBUG-INCOMPPTRDEBUG-INCOMQUAL
DEBUG-INCOMTARGETDEBUG-INCOMVERSIONDEBUG-INDBASEQL
DEBUG-INITERRDEBUG-INITIALDEBUG-INPREADERRDEBUG-INSVIRMEM
DEBUG-INTERRDEBUG-INTERRUPTEDDEBUG-INTMEMERRDEBUG-INTOVF
DEBUG-INTVECERRDEBUG-INUMTRUNCDEBUG-INVARGLISDEBUG-INVARRDIM
DEBUG-INVARRDSCDEBUG-INVCHARDEBUG-INVCHRCONDEBUG-INVDESC
DEBUG-INVDIGBINDEBUG-INVDIGDECDEBUG-INVDIGHEXDEBUG-INVDIGOCT
DEBUG-INVDIRNAMDEBUG-INVDMTPTRDEBUG-INVDSPSIZDEBUG-INVDSTREC
DEBUG-INVEXPRDEBUG-INVFIXDSTDEBUG-INVFLDREFDEBUG-INVGSTREC
DEBUG-INVGSTTYPDEBUG-INVMARDEBUG-INVNUMBERDEBUG-INVNUMSRC
DEBUG-INVNUMSTRDEBUG-INVOPADDRDEBUG-INVOPSYMDEBUG-INVPAGE
DEBUG-INVPRCSYNDEBUG-INVPRIORDEBUG-INVRANSPECDEBUG-INVSELDIS
DEBUG-INVSRCLINDEBUG-INVTIMSLIDEBUG-INVWIDTHDEBUG-INVWINPAR
DEBUG-IRFAOVFDEBUG-ISTRTRUDEBUG-ITMNOTAVADEBUG-ITMTRUNC
DEBUG-IVALNOFITDEBUG-IVALOUTBNDSDEBUG-IVPRCLOGDEBUG-KERFUNCNYI
DEBUG-KEYNAMERRDEBUG-KEYSTATERRDEBUG-LASTCHANCEDEBUG-LINEINFO
DEBUG-LOGFILEISDEBUG-LONGSTRINGDEBUG-LOOPINCRDEBUG-LOOPVAR
DEBUG-LOWBNDOPTDEBUG-MASKMISMATCHDEBUG-MASKNOTUSED
DEBUG-MASKNOTVMRDEBUG-MASKPARNREQDEBUG-MATQUOMIS
DEBUG-MISCLOSUBDEBUG-MISINVNUMDEBUG-MISINVOPERDEBUG-MISMODBEG
DEBUG-MISMODENDDEBUG-MISOPEMISDEBUG-MODUSCOPEDEBUG-MOVED_1
DEBUG-MOVED_2DEBUG-MOVED_3DEBUG-MOVED_4DEBUG-MOVED_5
DEBUG-MOVED_6DEBUG-MPARENREQDEBUG-MPCOMMANDDEBUG-NAMSTRMIS
DEBUG-NAMTOOLONGDEBUG-NEEDMOREDEBUG-NEEDPARENDEBUG-NOACCESSR
DEBUG-NOACCESSWDEBUG-NOADDRREGDEBUG-NOALTERSPDEBUG-NOATTACH
DEBUG-NOBREAGGRDEBUG-NOBREAKATDEBUG-NOBREAKSDEBUG-NOCALLS
DEBUG-NOCANMAINDEBUG-NOCLIDEBUG-NOCONNECTDEBUG-NOCURLOC
DEBUG-NODEFSCPEDEBUG-NODELIMTRDEBUG-NODEPDEBUGDEBUG-NODIRLISM
DEBUG-NODIRLISTDEBUG-NOELABBODYDEBUG-NOELABSPECDEBUG-NOEND
DEBUG-NOEPTSPECDEBUG-NOEVALEXPRDEBUG-NOEVENTFACDEBUG-NOEXCBRE
DEBUG-NOEXHNDDEBUG-NOFIELDDEBUG-NOFREEDEBUG-NOGLOBALS
DEBUG-NOHLPLIBDEBUG-NOINPAVAILDEBUG-NOINPFOCDEBUG-NOINSTRAN
DEBUG-NOKEYDEFDEBUG-NOKEYPADDEBUG-NOLASTVALDEBUG-NOLINXXX
DEBUG-NOLISTDEBUG-NOLOCALSDEBUG-NOMAINDEBUG-NOMARKCHNG
DEBUG-NOMATCHDEBUG-NOMOREDEBUG-NONEXPRDEBUG-NONEXPRC
DEBUG-NONUMSCOPEDEBUG-NONXTLINDEBUG-NOOCCLDISPDEBUG-NOOUTAVAIL
DEBUG-NOPACKMEMBODYDEBUG-NOPACKMEMSPECDEBUG-NOPRED
DEBUG-NOPROMPTDEBUG-NORECSYMDEBUG-NORMALDEBUG-NORSTBLD
DEBUG-NOSAVPROGDEBUG-NOSCOPEDEBUG-NOSCOPELISTDEBUG-NOSCRDEV
DEBUG-NOSCRMODEDEBUG-NOSCROLLDEBUG-NOSCROLLDISPDEBUG-NOSETTERM
DEBUG-NOSPAWNDEBUG-NOSRCHSTRDEBUG-NOSRCLINDEBUG-NOSTEPGO
DEBUG-NOSUCCDEBUG-NOSUCHBPTDEBUG-NOSUCHDISPDEBUG-NOSUCHELP
DEBUG-NOSUCHIMGDEBUG-NOSUCHMODUDEBUG-NOSUCHPACKDEBUG-NOSUCHSCOPE
DEBUG-NOSUCHTASKDEBUG-NOSUCHTPTDEBUG-NOSUCHWINDDEBUG-NOSUCHWPT
DEBUG-NOSYMBOLDEBUG-NOSYMBOLRDEBUG-NOTADAPROGDEBUG-NOTARRAY
DEBUG-NOTASTRUCTDEBUG-NOTATMAINDEBUG-NOTCURPCDEBUG-NOTDECTHREADS
DEBUG-NOTDEFINEDEBUG-NOTIMPLANDEBUG-NOTINLOOPDEBUG-NOTINSCOPE
DEBUG-NOTINSTDEBUG-NOTNUMSCOPEDEBUG-NOTORIGSRC
DEBUG-NOTPTRDEBUG-NOTRACESDEBUG-NOTRAZERODEBUG-NOTRECORD
DEBUG-NOTREEDEBUG-NOTRUNDWDEBUG-NOTTASKVALDEBUG-NOTUISOSC
DEBUG-NOTUISV30DEBUG-NOTUNQOVRDEBUG-NOTUPDATEDEBUG-NOTYPEINFO
DEBUG-NOUNIQUEDEBUG-NOUNIVERSALSDEBUG-NOUSREVNT
DEBUG-NOVALATPCDEBUG-NOVALTYPDEBUG-NOVALUEDEBUG-NOVECT
DEBUG-NOWATCHESDEBUG-NOWATONOPTDEBUG-NOWATTARDEBUG-NOWATVARIA
DEBUG-NOWATVARSTGDEBUG-NOWBPTDEBUG-NOWILD
DEBUG-NOWILDFILDEBUG-NOWOPCODEBUG-NOWPROTDEBUG-NO_SYNC_FROM_EXC_BRE
DEBUG-NPROMPTDEBUG-NULLPTRDEBUG-NUMCONLONGDEBUG-NUMTRUNC
DEBUG-OBJECTINVDEBUG-OBJPTRINVDEBUG-OBJTYPMISDEBUG-OBSOLETE_1
DEBUG-OBSOLETE_10DEBUG-OBSOLETE_11DEBUG-OBSOLETE_12DEBUG-OBSOLETE_13
DEBUG-OBSOLETE_14DEBUG-OBSOLETE_15DEBUG-OBSOLETE_16DEBUG-OBSOLETE_17
DEBUG-OBSOLETE_18DEBUG-OBSOLETE_19DEBUG-OBSOLETE_20DEBUG-OBSOLETE_21
DEBUG-OBSOLETE_22DEBUG-OBSOLETE_23DEBUG-OBSOLETE_24DEBUG-OBSOLETE_25
DEBUG-OBSOLETE_28DEBUG-OBSOLETE_29DEBUG-OBSOLETE_30DEBUG-OBSOLETE_7
DEBUG-OBSOLETE_8DEBUG-OBSOLETE_9DEBUG-OPCDECDEBUG-OPNOTALLOW
DEBUG-OPSYNTAXDEBUG-OUTPUTLOSTDEBUG-PACSIZREQDEBUG-PARENREQ
DEBUG-PARSTKOVRDEBUG-PASTHRUDEBUG-PATHNOTACPDEBUG-PATHTLONG
DEBUG-PATHTOOLONGDEBUG-PCNOTALLDEBUG-PLICVTERRDEBUG-PREDEPTNOT
DEBUG-PROFRANOTDEBUG-PROMPTCLENDEBUG-PROMPTOCCLDEBUG-PROMPTRLEN
DEBUG-PROVRFLOWDEBUG-PSHINARYNYIDEBUG-PSHVALNYIDEBUG-PXCN
DEBUG-QUALREQDEBUG-QUOSTRLONGDEBUG-READERRDEBUG-REFUSED
DEBUG-REGMASKHIDDENDEBUG-REGMASKMISSINGDEBUG-REGREQ
DEBUG-RENAMENOTDEBUG-RESUMERRDEBUG-RETURNEDDEBUG-RNDFCTROUT
DEBUG-ROPRANDFDEBUG-RPCDBBDTDEBUG-RPCERRDEBUG-RPCINVDSC
DEBUG-RPCOVFDEBUG-RPCUNFDEBUG-RPCUNKARGDEBUG-RSTERR
DEBUG-SCALEADDDEBUG-SCALESUBDEBUG-SCRNOACCESSR
DEBUG-SCRNOSRCLINDEBUG-SCRNOTORIGSRCDEBUG-SCRTOBIG
DEBUG-SCRTOSMALLDEBUG-SCRUNAOPNSRCDEBUG-SCRUNAREASRC
DEBUG-SETKEYDEBUG-SETKEYERRDEBUG-SFCNTNEGDEBUG-SHOKEYERR
DEBUG-SHRPRCDEBUG-SIDEFFECTDEBUG-SIGVECTRUNCDEBUG-SIZEATOMIC
DEBUG-SIZETRUNCDEBUG-SOURCESCOPEDEBUG-SPAWNEDDEBUG-SRCLINNOT
DEBUG-SS_INTDEBUG-STEPINTODEBUG-STGTRUNCDEBUG-STRNGPAD
DEBUG-STRTOOLONGDEBUG-STRUCSIZEDEBUG-SUBOUTBNDDEBUG-SUBSCRNG
DEBUG-SUBSTRINGDEBUG-SUPERDEBUGDEBUG-SYMNOTACTDEBUG-SYMNOTFND
DEBUG-SYNCDONEDEBUG-SYNCREPCOMDEBUG-SYNC_ALREADY_IN_PROGRESS
DEBUG-SYNERREXPRDEBUG-SYNERRLABELDEBUG-SYNERRLINEDEBUG-SYNTAX
DEBUG-TASKERRORDEBUG-TASKNONULLDEBUG-TASKNOREGSDEBUG-TASKNOTABORT
DEBUG-TASKNOTACTDEBUG-TASKNULLDEBUG-TERMINATINGDEBUG-TIMESLICE
DEBUG-TOOFEWSUBDEBUG-TOOMANDIMDEBUG-TOOMANERRDEBUG-TOOMANINV
DEBUG-TOOMANPARMDEBUG-TOOMANSUBDEBUG-UNAACCREGDEBUG-UNACREDBGO
DEBUG-UNACVTDEBUG-UNACVTBYTTAUDEBUG-UNALIGNED
DEBUG-UNALLOCATEDDEBUG-UNAOPEDBGIDEBUG-UNAOPESCRDEBUG-UNAOPNHLP
DEBUG-UNAOPNINIDEBUG-UNAOPNSRCDEBUG-UNAREASRCDEBUG-UNASAVVAL
DEBUG-UNASETIMGDEBUG-UNASETTASDEBUG-UNASWISTADEBUG-UNBPAREN
DEBUG-UNDEXPNDEBUG-UNDKEYDEBUG-UNHANDLEDDEBUG-UNIMPLENT
DEBUG-UNMTCHPARNDEBUG-UNREQVQUALDEBUG-UPBNDOPTDEBUG-USREVNTERR
DEBUG-VALNOTADDRDEBUG-VALRNGDEBUG-VARNESDEPDEBUG-VECDIS
DEBUG-VECREASONDEBUG-VECSCP0DEBUG-VECTSUBRNGDEBUG-VERIFYICF
DEBUG-VERSIONNUMDEBUG-VFLTDIVDEBUG-VFLTOVFDEBUG-VFLTROP
DEBUG-VFLTUNDDEBUG-WATCHSETUPDEBUG-WATCHSIZEDEBUG-WATNOWCAN
DEBUG-WATNOWWATDEBUG-WATVARGSGONEDEBUG-WATVARGSOVR
DEBUG-WATVARNOWGBLDEBUG-WATVARPROTDEBUG-WATVARPTR
DEBUG-WATVARREMAPDEBUG-WATVARSCPDEBUG-WIDTHDIFF
DEBUG-WORKSTACMDDEBUG-WPTTRACEDEBUG-WRITE_FAILED
DEBUG-WRITE_INTO_KERNELDEBUG-WRITE_INTO_KERNEL_STACK
DEBUG-ZERLENDSTDEBUG-ZEROINCR
DEBUG-ABORTED
=Title VAX DEBUG Message
Ident: ABORTED
Message Text:
Command aborted by user request
Severity: Warning
Explanation:
The command being executed was stopped when you
typed CTRL-C.
No action necessary.
DEBUG-ABSDATSYN
=Title VAX DEBUG Message
Ident: ABSDATSYN
Message Text:
Absolute date-time syntax error
Severity: Warning
Explanation:
The date-time value could not be converted because
it is not in the proper VMS format.
Re-enter the date-time value using the correct VMS
date-time format.
DEBUG-ACCADDCOM
=Title VAX DEBUG Message
Ident: ACCADDCOM
Message Text:
Access violation in address computation for
address_value
Severity: Warning
Explanation:
The address computation for the specified variable
resulted in an access violation. This normally
means that a register value or a descriptor needed
in the address computation is uninitialized or
corrupted.
If the necessary register or descriptor is not yet
initialized, the variable is not available at this
point in the code. If the register or descriptor
is corrupted, the cause of this error should be
located and corrected.
DEBUG-ACTIVATING
=Title VAX DEBUG Message
Ident: ACTIVATING
Message Text:
Process-specification is activating
Severity: Informational
Explanation:
The process process-specification has just
activated, and is now connected to the main
debugger. Any SET BREAK/ACTIVATING or SET
TRACE/ACTIVATING events will now take effect.
Submit an SPR. This message is handled internally,
and should never be signaled to the user.
DEBUG-ADDRANCOV
=Title VAX DEBUG Message
Ident: ADDRANCOV
Message Text:
Address range covers more than one module
address_value is in path_name address_value is in
path_name
Severity: Warning
Explanation:
The address range specified in a debugger
EXAMINE/SOURCE command covers more than a single
module. This is not allowed. The start address CZ
is in module mod1 and the end address yyy is in
module mod2.
Re-enter the command with a valid address range.
DEBUG-ADDRESSMODE
=Title VAX DEBUG Message
Ident: ADDRESSMODE
Message Text:
Instruction uses illegal or undefined addressing
modes
Severity: Error
DEBUG-ADDRMBZ
=Title VAX DEBUG Message
Ident: ADDRMBZ
Message Text:
A must-be-zero field in an address was not zero
Severity: Error
Explanation:
This is an internal debugger error.
If the error is reproducible, submit a Software
Performance Report and, if possible, enclose both a
copy of the program being debugged and a logged
debugging session that reproduces the error.
DEBUG-ADDRREG
=Title VAX DEBUG Message
Ident: ADDRREG
Message Text:
& not allowed on register variables: operand bound
to register_name
Severity: Warning
Explanation:
The C language & operator could not be applied to
the given operand because the operand is a register
variable. This is not allowed in the C language
definition.
Do not use the & operator on a register variable.
DEBUG-AMBFIELD
=Title VAX DEBUG Message
Ident: AMBFIELD
Message Text:
Field_name is an ambiguous field name
Severity: Warning
Explanation:
The reference to the given field cannot be resolved
because there is more than one field with the given
name.
Fully qualify the reference with a complete name
for the desired field.
DEBUG-AMBIGQUAL
=Title VAX DEBUG Message
Ident: AMBIGQUAL
Message Text:
Qualifier qualifier_name is ambiguous
Severity: Warning
Explanation:
The qualifier cannot be resolved to a single
option. There is more than one option to the
command that starts with these characters.
Add more of the characters to the qualifier string
to make the option unambiguous. The qualifier
should be unambiguous when it has at least four
characters.
DEBUG-AMPERSAND
=Title VAX DEBUG Message
Ident: AMPERSAND
Message Text:
Operand of ampersand must be lvalue
Severity: Warning
Explanation:
The C language & operator cannot be applied to the
result of an expression. This is not allowed in
the C language definition.
Do not use the & operator in this context.
DEBUG-ASTWASDISABLED
=Title VAX DEBUG Message
Ident: ASTWASDISABLED
Message Text:
ASTs were disabled, are still disabled
Severity: Informational
Explanation:
The delivery of asynchronous system traps ASTs were
already turned off in your program when the DISABLE
AST command was issued.
None
DEBUG-ASTWASENABLED
=Title VAX DEBUG Message
Ident: ASTWASENABLED
Message Text:
ASTs were enabled, are still enabled
Severity: Informational
Explanation:
The delivery of asynchronous system traps ASTs were
already turned on in your program when the ENABLE
AST command was issued.
None
DEBUG-ATTACHED
=Title VAX DEBUG Message
Ident: ATTACHED
Message Text:
Terminal now attached to process process_name
Severity: Informational
Explanation:
The control of your terminal is being passed from
the current process to another process by means of
the ATTACH command.
None
DEBUG-ATTREQREF
=Title VAX DEBUG Message
Ident: ATTREQREF
Message Text:
Attach request refused
Severity: Error
Explanation:
The specified process could not be attached to.
Either it was not detached or it did not belong to
the caller's job.
Ensure that the specified process is detached and
belongs to the caller's job.
DEBUG-BADADDSPA
=Title VAX DEBUG Message
Ident: BADADDSPA
Message Text:
Attempted to compare addresses in different address
spaces
Severity: Error
Explanation:
This is an internal debugger error.
If the error is reproducible, submit a Software
Performance Report and, if possible, enclose both a
copy of the program being debugged and a logged
debugging session that reproduces the error.
DEBUG-BADADDSTA
=Title VAX DEBUG Message
Ident: BADADDSTA
Message Text:
Attempted to compare addresses with different
address states
Severity: Error
Explanation:
This is an internal debugger error.
If the error is reproducible, submit a Software
Performance Report and, if possible, enclose both a
copy of the program being debugged and a logged
debugging session that reproduces the error.
DEBUG-BADBODPACK
=Title VAX DEBUG Message
Ident: BADBODPACK
Message Text:
Incorrect package spec name in body-spec spec-name,
module mod-name
Severity: Informational
Explanation:
The compiler has generated invalid Debug Symbol
Table information.
Please submit a Software Performance Report against
the compiler.
DEBUG-BADDESCR
=Title VAX DEBUG Message
Ident: BADDESCR
Message Text:
Descriptor for 'symbol_name' is bad or is not set
up yet
Severity: Warning
Explanation:
The descriptor for the given symbol points into
memory that cannot be read by the Debugger.
Correct the descriptor.
DEBUG-BADDISCVAL
=Title VAX DEBUG Message
Ident: BADDISCVAL
Message Text:
Incorrect value of tag_value in discriminant field
tag_name.
Severity: Informational
Explanation:
The discriminate value you gave was out of range.
Supply a discriminate value that is within the
correct range.
DEBUG-BADDST
=Title VAX DEBUG Message
Ident: BADDST
Message Text:
Bad debugger symbol table (compiler error)
Severity: Error
Explanation:
The debugger has detected an error in the Debug
Symbol Table of your program. This indicates an
internal error in either the debugger or the
compiler of this module.
Please submit a Software Performance Report.
DEBUG-BADEVNPAR
=Title VAX DEBUG Message
Ident: BADEVNPAR
Message Text:
Parameter does not have permitted data type for
this event
Severity: Error
Explanation:
The event you specified cannot be used with the
specified symbol. For example, you cannot specify
the RUN event except on TASK type symbols. Please
see the documentation for details on which events
can be specified with which symbol types.
Specify the correct symbol type for this event.
DEBUG-BADEXH
=Title VAX DEBUG Message
Ident: BADEXH
Message Text:
The user-mode exit handler list is corrupt
Severity: Error
Explanation:
While walking the list of user-mode exit handlers,
the debugger detected a forward link which pointed
to an inaccessible exit control block.
Check for a call to the SYS$DCLEXH system service
that specifies an illegal exit control block
argument. Also verify that exit control blocks are
not getting corrupted later in the program.
DEBUG-BADFRAME
=Title VAX DEBUG Message
Ident: BADFRAME
Message Text:
Bad FP or bad saved FP at pointer-addr in call
stack, can't read frame near frame-addr
Severity: Informational
Explanation:
The debugger is attempting to chain down the call
stack, following frame pointers. The FP register
(if pointer-addris "FFFFFFFF") or the saved frame
pointer at location pointer-addr points to a frame
at least part of which is not read accessible near
location frame-addr.
Determine what part of your code is writing into
the FP register or overwriting the saved frame
pointer on the call stack (or a preceding saved
frame pointer) and correct it. Since the debugger
looks at the call stack to symbolize addresses, you
may suppress some of these messages by typing the
command "SET MODE NOSYMBOLIC".
DEBUG-BADHANDLE
=Title VAX DEBUG Message
Ident: BADHANDLE
Message Text:
Non-existent object handle passed to routine
Severity: Error
Explanation:
The debugger uses object handles for passing
information around within itself. The debugger has
used a non-existent or corrupt handle for an
operation. The user should never see this message.
Submit a Software Performance Report (SPR)
DEBUG-BADOPCODE
=Title VAX DEBUG Message
Ident: BADOPCODE
Message Text:
Opcode opcode_name is unknown
Severity: Error
Explanation:
The opcode opcode_name specified as a command
parameter is unknown to the debugger. It may be
the case that an opcode synonym has been specified
which is not recognized by the debugger.
Specify a valid opcode or specify an opcode synonym
that the debugger recognizes.
DEBUG-BADPARAM
=Title VAX DEBUG Message
Ident: BADPARAM
Message Text:
Bad parameter value
Severity: Error
Explanation:
This message indicates an internal debugger error.
Submit a Software Performance Report.
DEBUG-BADSCOPE
=Title VAX DEBUG Message
Ident: BADSCOPE
Message Text:
Invalid pathname path_name, SCOPE not changed
Severity: Error
Explanation:
The scope path_name specified in the SET SCOPE
command contained a pathname that does not exist.
Specify a valid scope.
DEBUG-BADSIGARG
=Title VAX DEBUG Message
Ident: BADSIGARG
Message Text:
Bad sigarg pointer at pointer-addr or bad sigarg
vector, can't read sigarg vector near sigarg-addr
Severity: Informational
Explanation:
The debugger is attempting to chain down the call
stack, following frame pointers, and has
encountered an exception handler. The signal
argument pointer at location pointer-addrpoints to
a signal argument vector at least part of which is
not read accessible near location sigarg-addr.
Determine what part of your code is overwriting the
stored signal argument pointer on the call stack,
or part of the signal argument vector itself, and
correct it. Since the debugger looks at the call
stack to symbolize addresses, you may suppress some
of these messages by typing the command "SET MODE
NOSYMBOLIC".
DEBUG-BADSTACK
=Title VAX DEBUG Message
Ident: BADSTACK
Message Text:
Stack corrupted - no further data available
Severity: Warning
Explanation:
While displaying part of the call stack, the
debugger has determined that the stack is corrupted
and cannot continue executing the command.
See the secondary message for more information.
DEBUG-BADSTARTPC
=Title VAX DEBUG Message
Ident: BADSTARTPC
Message Text:
Cannot access start PC = address_value
Severity: Error
Explanation:
Location address_value is not an accessible address
and therefore cannot be executed. This is often
caused when a GO command with no address
specification is entered after the program has
terminated. The debugger tries to execute an
instruction at location 0, which is not accessible.
Specify a different address specification in the GO
command or, if the program has terminated, you can
exit from the debugger and initiate the program
with the DCL command RUN.
DEBUG-BADSTATUS
=Title VAX DEBUG Message
Ident: BADSTATUS
Message Text:
Bad status returned from routine-name
Severity: Error
Explanation:
The debugger got an unexpected error status from
the system service or RTL routine routine-name.
Examine the error message and consider if the
problem is related to a lack of quota or otherwise
related to your program's behavior. If so, then
take corrective action. If, after this evaluation,
you believe that the problem lies in the debugger,
then submit a Software Performance Report.
DEBUG-BADSUBPAR
=Title VAX DEBUG Message
Ident: BADSUBPAR
Message Text:
Incorrect parent name in subunit sym-name, in
module mod-name
Severity: Informational
Explanation:
The compiler has generated invalid Debug Symbol
Table information.
Please submit a Software Performance Report against
the compiler.
DEBUG-BADTAGVAL
=Title VAX DEBUG Message
Ident: BADTAGVAL
Message Text:
Incorrect value of tag_value in tag field tag_name.
Severity: Informational
Explanation:
The tag value you gave was out of range.
Supply a tag that is within the correct range.
DEBUG-BADTARGET
=Title VAX DEBUG Message
Ident: BADTARGET
Message Text:
Target location protected, cannot perform deposit
Severity: Warning
Explanation:
The target address of the DEPOSIT command cannot be
made writeable. The DEPOSIT command cannot be
performed.
None.
DEBUG-BADUSEPACK
=Title VAX DEBUG Message
Ident: BADUSEPACK
Message Text:
Incorrect package name in use clause use-name,
module module-name
Severity: Informational
Explanation:
The compiler has generated invalid Debug Symbol
Table information.
Please submit a Software Performance Report against
the compiler.
DEBUG-BADUSREVNT
=Title VAX DEBUG Message
Ident: BADUSREVNT
Message Text:
Bad user-specified event table or event entry in
user RTL
Severity: Error
Explanation:
The debugger has detected an internal inconsistency
in the event tables of the Run Time Library. This
indicates an internal error in either the debugger
or the Run Time Library.
Please submit a Software Performance Report.
DEBUG-BADWATCH
=Title VAX DEBUG Message
Ident: BADWATCH
Message Text:
Cannot watch protect address address_value
Severity: Error
Explanation:
A SET WATCH command specified a protected address.
Note that you cannot place a watchpoint on a
dynamically allocated variable because these
variables are stored on the stack.
Do not use watchpoint on this address.
DEBUG-BADWIDGET
=Title VAX DEBUG Message
Ident: BADWIDGET
Message Text:
The debugger can not write to the command dialog
box, is not initialized.
Severity: Fatal
Explanation:
The debugger got an unexpected status when trying
to write to the command dialog box. This prevents
the debugger from continuing this session.
Try the debugger again, if the same results exist
submit a Software Performance Report (SPR).
DEBUG-BASVARNOTSET
=Title VAX DEBUG Message
Ident: BASVARNOTSET
Message Text:
Base variable not set up yet
Severity: Warning
Explanation:
The pointer to the based variable has not been set
up by an ALLOCATE statement. Without a valid
pointer, the reference cannot be made.
Execute the ALLOCATE statement that defines the
pointer for this based variable and then use the
pointer to dereference the desired variable.
DEBUG-BITRANGE
=Title VAX DEBUG Message
Ident: BITRANGE
Message Text:
Bit range out of limits
Severity: Error
Explanation:
The EVALUATE command specified a bit field that is
too wide.
The low limit of the bit field is 0 and the high
limit is 31; the maximum range is 31:0.
DEBUG-BPTDIFMOD
=Title VAX DEBUG Message
Ident: BPTDIFMOD
Message Text:
Breakpoint or tracepoint being set in a different
module.
Severity: Informational
Explanation:
The specified line number was not found in the
current module. Consequently, Debug is setting the
breakpoint or tracepoint in a module later in the
call stack or in a set module not on the call
stack.
If the breakpoint or tracepoint was intended to be
set in the current module, cancel the breakpoint or
tracepoint and specify a line number in the current
module.
DEBUG-BPTONDATA
=Title VAX DEBUG Message
Ident: BPTONDATA
Message Text:
Execution breakpoint or tracepoint set on data item
Severity: Informational
Explanation:
The command requested a breakpoint or tracepoint
for a data item. Typically breakpoints are set
only on code locations.
See the following message.
DEBUG-BUFFEROVF
=Title VAX DEBUG Message
Ident: BUFFEROVF
Message Text:
Buffer overflow
Severity: Error
Explanation:
This message indicates an internal debugger error.
Submit a Software Performance Report.
DEBUG-BWLGISMUS
=Title VAX DEBUG Message
Ident: BWLGISMUS
Message Text:
B, W, L, G, I, or S must precede ^ for operand
number operand_number
Severity: Error
Explanation:
You must specify the type of offset as either B
(byte), W (word), or L (longword). You must
specify the type of literal as either I (immediate)
or S (short). You may specify the addressing mode
as G (general).
Enter the instruction again, specifying the operand
using one of the above modes.
DEBUG-CANBRKWAT
=Title VAX DEBUG Message
Ident: CANBRKWAT
Message Text:
Cancel it and set a watchpoint if that is what was
intended
Severity: Informational
Explanation:
If you intended to get notified when the specified
location was modified rather than executed, then a
watchpoint should have been set rather than a
breakpoint.
If a watchpoint was intended, then cancel the
breakpoint and set a watchpoint.
DEBUG-CANTACCESSMAIN
=Title VAX DEBUG Message
Ident: CANTACCESSMAIN
Message Text:
Cannot access the main debugger
Severity: Fatal
Explanation:
The kernel debugger cannot access the main
debugger. The reason is given in the message
following this message.
Correct the problem given by the messages following
this message. If the problem cannot be solved,
submit a Software Performance Report.
DEBUG-CANTCREATEMAIN
=Title VAX DEBUG Message
Ident: CANTCREATEMAIN
Message Text:
Could not create the debugger subprocess
Severity: Fatal
Explanation:
An error occurred while trying to create a
subprocess to run the sharable main debugger image.
The reason is given in the message following this
message.
Correct the problem given by the messages following
this message. If the problem cannot be solved,
submit a Software Performance Report.
DEBUG-CANTGETFID
=Title VAX DEBUG Message
Ident: CANTGETFID
Message Text:
Cannot get file-id for image file opened on channel
channel-number
Severity: Fatal
Explanation:
An error occurred while trying to get the file-id
of the image file opened on channel channel-number.
The reason is given in the message following this
message.
Correct the problem given by the messages following
this message. If the problem cannot be solved,
submit a Software Performance Report.
DEBUG-CANTINTPRO
=Title VAX DEBUG Message
Ident: CANTINTPRO
Message Text:
Cannot interrupt process !AC
Severity: Informational
Explanation:
The debugger could not interrupt the specified
process because it was deleted. This message
usually indicates that the specified process
terminated abnormally -- either via the DCL STOP
command or via a call to $DELPRC.
The debugger failed to interrupt the process.
Unless the reason for this is apparent, submit a
Software Performance Report (SPR).
DEBUG-CANTOPNIMG
=Title VAX DEBUG Message
Ident: CANTOPNIMG
Message Text:
Cannot open image image_name (File:
device_name:(file_id,file_id,file_id))
Severity: Informational
Explanation:
The information the debugger needs to allow you to
debug this section of code is in an image file that
could not be opened.
Check for the existence of the specified file
and/or its associated file protection attributes.
DEBUG-CANTPAST
=Title VAX DEBUG Message
Ident: CANTPAST
Message Text:
Cannot paste to read-only window.
Severity: Warning
Explanation:
The window which has the input focus is a read-only
window. You cannot paste to a read-only window.
Assign the input focus to a writeable window and,
if applicable, to the appropriate text-entry field.
DEBUG-CIREXLST
=Title VAX DEBUG Message
Ident: CIREXLST
Message Text:
Command aborted after number_of_handlers exit
handlers displayed circular exit handler list
suspected
Severity: Error
Explanation:
After displaying information about 100 exit
handlers, the debugger suspects a circular exit
handler list.
If there is a circular exit handler list, then
identify and correct the error in the user program.
DEBUG-CLIBRDFAI
=Title VAX DEBUG Message
Ident: CLIBRDFAI
Message Text:
Clipboard operation failure
Severity: Warning
Explanation:
One of the DECtoolkit clipboard routines has
failed. The attempt to write to the clipboard may
not have completed successfully.
Verify that the clipboard contains the data that
you wrote to it. If it does not, attempt the
operation again.
DEBUG-CLIBRDLCK
=Title VAX DEBUG Message
Ident: CLIBRDLCK
Message Text:
Clipboard locked
Severity: Warning
Explanation:
Some other DECWINDOWS application has locked the
clipboard.
Wait until the other application has released the
clipboard.
DEBUG-CMDISCOR
=Title VAX DEBUG Message
Ident: CMDISCOR
Message Text:
The correct command is command_name
Severity: Informational
Explanation:
The previous message shows the obsolete command.
The command replacing it is shown in this message.
Use the correct command as shown. The obsolete
command will not be available in a future release
of the debugger.
DEBUG-CMDISOBS
=Title VAX DEBUG Message
Ident: CMDISOBS
Message Text:
Command command_name is obsolete
Severity: Informational
Explanation:
This command is obsolete.
Do not use this command, it will not be available
in a future release of the debugger.
DEBUG-CMDNOTDW
=Title VAX DEBUG Message
Ident: CMDNOTDW
Message Text:
The !AC command is not allowed in the DECWindows
debugger
Severity: Error
Explanation:
The specified command may not be used with the
DECWindows debugger.
Do not use the command with the DECWindows
debugger.
DEBUG-CMDNOTONE
=Title VAX DEBUG Message
Ident: CMDNOTONE
Message Text:
The !AC command is not allowed in the one process
debugger
Severity: Error
Explanation:
The specified command may not be used with the
single process debugger.
Do not use the command with the one process
debugger.
DEBUG-CMDSYNERR
=Title VAX DEBUG Message
Ident: CMDSYNERR
Message Text:
Command syntax error at or near 'the
debugger_command_segment'
Severity: Warning
Explanation:
There is a syntax error in the Debug command
somewhere near the string shown in the message.
Correct the syntax error and re-enter the command.
DEBUG-CMPNOTFND
=Title VAX DEBUG Message
Ident: CMPNOTFND
Message Text:
Specified component not found in this type
Severity: Warning
Explanation:
The enumeration component named in this operation
could not be found in the list of components
defined for this type.
Correct the name of the enumeration component or
correct the expression.
DEBUG-CNTRLWRDNOTACCESS
=Title VAX DEBUG Message
Ident: CNTRLWRDNOTACCESS
Message Text:
The vector control word is not accessible
Severity: Error
Explanation:
The debugger does not have direct access to the
vector control word. Therefore the operands of
this instruction cannot be displayed correctly.
Do not attempt to display the operands of vector
instructions whose control word is not accessible
to the debugger.
DEBUG-CONFLICT
=Title VAX DEBUG Message
Ident: CONFLICT
Message Text:
Illegal combination of command elements - check
documentation
Severity: Warning
Explanation:
Command line elements conflict in their
operations. The command will not be performed.
Do not specify conflicting command line elements.
DEBUG-CONFROMEXC
=Title VAX DEBUG Message
Ident: CONFROMEXC
Message Text:
Warning: you are continuing from a severe error
Severity: Informational
Explanation:
The debugger has encountered a severe error and is
continuing. The validity of this debugging session
can no longer be guaranteed.
Determine and correct the cause of the severe
error. If the problem cannot be solved, submit a
Software Performance Report (SPR).
DEBUG-CONSTRCOMP
=Title VAX DEBUG Message
Ident: CONSTRCOMP
Message Text:
Illegal deposit to a constrained record component
Severity: Error
Explanation:
The debugger cannot DEPOSIT into a constrained
record component.
Do not attempt to deposit into a constrained record
component.
DEBUG-CPOSTDECR
=Title VAX DEBUG Message
Ident: CPOSTDECR
Message Text:
Side effect on post-decrement operation not
performed
Severity: Informational
Explanation:
The debugger does not support the evaluation of a
post-decrement expression.
None
DEBUG-CPOSTINCR
=Title VAX DEBUG Message
Ident: CPOSTINCR
Message Text:
Side effect on post-increment operation not
performed
Severity: Informational
Explanation:
The debugger does not support the evaluation of a
post-increment expression.
None
DEBUG-CPREDECR
=Title VAX DEBUG Message
Ident: CPREDECR
Message Text:
Side effect on pre-decrement operation not
performed
Severity: Informational
Explanation:
The debugger does not support the evaluation of a
pre-decrement expression.
None
DEBUG-CPREINCR
=Title VAX DEBUG Message
Ident: CPREINCR
Message Text:
Side effect on pre-increment operation not
performed
Severity: Informational
Explanation:
The debugger does not support the evaluation of a
pre-increment expression.
None
DEBUG-CRMPSCFAIL
=Title VAX DEBUG Message
Ident: CRMPSCFAIL
Message Text:
Failed to map-in the debugger Symbol Table (DST)
Severity: Informational
Explanation:
There will always be a secondary message describing
why the debugger failed to map-in the debugger
symbol table (DST) or global symbol table (GST).
Please refer to the secondary message to take the
appropriate action.
DEBUG-CVTNEGUNS
=Title VAX DEBUG Message
Ident: CVTNEGUNS
Message Text:
Cannot convert negative value to unsigned value at
or near opcode_name
Severity: Warning
Explanation:
The command is attempting to assign a negative
value to an unsigned type. This is not allowed.
Do not attempt to put a negative value into an
unsigned variable.
DEBUG-DBGERR
=Title VAX DEBUG Message
Ident: DBGERR
Message Text:
Internal debugger coding error.
Severity: Error
Explanation:
An internal debugger error has been encountered.
If the error is reproducible, submit a Software
Performance Report and, if possible, enclose both a
copy of the program being debugged and a logged
debugging session that reproduces the error.
DEBUG-DBGSTOPPED
=Title VAX DEBUG Message
Ident: DBGSTOPPED
Message Text:
A debugger process from a previous debugging
session has been terminated
Severity: Warning
Explanation:
While attempting to create a process to run the
debugger, a debug process from a previous debugging
session was found and terminated.
Under normal circumstances, the debugger process
will exit when a debugging session ends via the
EXIT or QUIT commands. If the previous debugging
session was terminated with an EXIT or QUIT command
and this error is reproducable, then submit a
Software Performance Report (SPR)
DEBUG-DECLARERR
=Title VAX DEBUG Message
Ident: DECLARERR
Message Text:
Too many declarations, parameter_name ignored
Severity: Warning
Explanation:
There is a mismatch between the number of
declarations in a command procedure and the number
of parameters passed to that command procedure.
Check the command procedure and the DECLARE
statements within to see if they agree with the
number of parameters on the command line.
DEBUG-DECOVF
=Title VAX DEBUG Message
Ident: DECOVF
Message Text:
Decimal overflow at or near opcode_name
Severity: Error
Explanation:
The value being deposited does not fit into the
specified address.
Specify either a smaller value or a different
target address.
DEBUG-DECROPRAND
=Title VAX DEBUG Message
Ident: DECROPRAND
Message Text:
Illegal packed or decimal string value (Reserved
Operand fault occurred during conversion)
Severity: Error
Explanation:
The debugger encountered a Reserved Operand Fault
when attempting to convert the specified value.
This indicates that the packed or decimal string
value did not contain a valid number.
Ensure that the string value contains only valid
digits.
DEBUG-DEFKEY
=Title VAX DEBUG Message
Ident: DEFKEY
Message Text:
State_name key key_name has been defined
Severity: Informational
Explanation:
The defining of functions keys has just been
performed using the DEFINE/KEY command. This
command assigns a string to function key. This is
the logging message for the DEFINE/KEY command.
None
DEBUG-DEFKEYERR
=Title VAX DEBUG Message
Ident: DEFKEYERR
Message Text:
Error in processing DEFINE/KEY command:
Severity: Warning
Explanation:
There was an error in defining the given key in the
display system. The key may not be redefinable,
either because the display system will not allow it
or because there are protections that prevent it.
The key definition may be invalid.
Correct the error in the key definition.
DEBUG-DEFTOOREC
=Title VAX DEBUG Message
Ident: DEFTOOREC
Message Text:
Command defined with too many levels of recursion.
Severity: Error
Explanation:
Commands may only be defined to a specified depth
of recursion (now set at 100).
Redefine your command such that it uses less levels
of recursion.
DEBUG-DELKEY
=Title VAX DEBUG Message
Ident: DELKEY
Message Text:
State_name key key_name has been deleted
Severity: Informational
Explanation:
The undefining of functions keys has just been
performed using the DELETE/KEY command. This
command deletes the key definitions that were
established by the DEFINE/KEY command or, by
default by the debugger.This is the logging message
for the DELETE/KEY command.
None
DEBUG-DELKEYERR
=Title VAX DEBUG Message
Ident: DELKEYERR
Message Text:
Error in processing DELETE/KEY command:
Severity: Warning
Explanation:
There was an error in deleting the given key
definition from the display mechanism. The key may
not be a defined key. The key definition might
also be protected against deletions.
Correct the error in the command or correct the
protections of the key in the display mechanism
being used.
DEBUG-DELTIMTOO
=Title VAX DEBUG Message
Ident: DELTIMTOO
Message Text:
Delta time too large
Severity: Error
Explanation:
The debugger encountered an error when attempting
to convert the string form of the delta time to
binary.
Enter the delta time specifying a smaller value.
DEBUG-DESCNOTSET
=Title VAX DEBUG Message
Ident: DESCNOTSET
Message Text:
Descriptor not set up yet
Severity: Warning
Explanation:
A descriptor used in an expression in the command
is not yet fully initialized. Some of the fields
are not valid, which means that the Debugger cannot
completely evaluate the expression.
Examine the descriptor that caused the problem and
determine which fields are not correct. Fill in
these fields with the correct values.
DEBUG-DISABLEAST
=Title VAX DEBUG Message
Ident: DISABLEAST
Message Text:
ASTs were enabled, are now disabled
Severity: Informational
Explanation:
Delivery of asynchronous system traps (ASTs) has
been turned off in your program by a DISABLE AST
command.
None
DEBUG-DISNAMREQ
=Title VAX DEBUG Message
Ident: DISNAMREQ
Message Text:
Display name required with this command
Severity: Error
Explanation:
user did not specify a display name with this
command
enter a display name with this command
DEBUG-DISNOTSEL
=Title VAX DEBUG Message
Ident: DISNOTSEL
Message Text:
Display not selected because removed from screen
Severity: Error
Explanation:
You specified a display which is removed from the
screen.
Either specify a display which is not removed from
the screen, or place the specified display onto the
screen and attempt the operation again.
DEBUG-DISPEXISTS
=Title VAX DEBUG Message
Ident: DISPEXISTS
Message Text:
Display_name display already exists; cannot be set
until canceled
Severity: Error
Explanation:
You attempted to create a display which already
exists, either by explicitly creating the display
or by trying to save the contents of a display into
currently existing display.
Specify a display which does not exist.
DEBUG-DISPRLENSIZ
=Title VAX DEBUG Message
Ident: DISPRLENSIZ
Message Text:
Length of display_name display cannot exceed
maximum size increase /SIZE or specify fewer lines
Severity: Error
Explanation:
You attempted to resize the display so that the
number of visible lines in the display is larger
than the number of lines which are saved for the
display. The debugger has set the number of
visible lines of the display to the SIZE value of
the display.
Either decrease the number of visible lines in the
display, or increase the number of lines which are
saved for this display by the use of the SIZE
value.
DEBUG-DIVBYZERO
=Title VAX DEBUG Message
Ident: DIVBYZERO
Message Text:
Attempted to divide by zero
Severity: Error
Explanation:
During the evaluation of an expression, the
debugger noticed an attempt to divide by zero.
Correct the expression so that it does not divide
by zero.
DEBUG-DSTERRG
=Title VAX DEBUG Message
Ident: DSTERRG
Message Text:
Error in DST (compiler error). GOTO DST has been
ignored
Severity: Informational
Explanation:
This represents an internal compiler, linker or
debugger error. If this can be reproduced please
submit an Software Performance Report (SPR).
If this can be reproduced please submit an Software
Performance Report (SPR).
DEBUG-DSTNESDEP
=Title VAX DEBUG Message
Ident: DSTNESDEP
Message Text:
DST nesting depth too deep in module path_name
Severity: Error
Explanation:
Symbol table nesting depth is too deep in the
specified module. This occurs if routine nesting
or data record nesting is very deep in the user
program.
Simplify the user program and run again.
DEBUG-DUPLVQUAL
=Title VAX DEBUG Message
Ident: DUPLVQUAL
Message Text:
Duplicate or conflicting vector qualifier specified
at 'command_line'
Severity: Error
Explanation:
The qualifier indicated in the shown command line
fragment has already been specified, or is
conflicting with an earlier specified qualifier.
Delete the qualifier in error.
DEBUG-DWERR
=Title VAX DEBUG Message
Ident: DWERR
Message Text:
A DECwindows toolkit error has occurred the message
text is '!AS'
Severity: Informational
Explanation:
An error has been reported by the DECwindows
toolkit. This indicates that either the toolkit or
the X server has detected a problem with the
debuggers DECwindows display(s).
Try to correct the problem specified in the
message. For further information or assistance on
this problem, contact your System Manager.
DEBUG-DWNOT1PROC
=Title VAX DEBUG Message
Ident: DWNOT1PROC
Message Text:
The 1 process debugger cannot be run in DECwindows
mode
Severity: Warning
Explanation:
The debugger must have ASTs enabled at all times in
order to properly run as a DECwindows program.
This is not possible for a 1 process debugger.
Therefore, the debugger is defaulting to not run as
a DECwindows debugger.
Correct the logical name assignment for DBG$PROCESS
to be either "MULTIPROCESS" or "DEFAULT", and try
again.
DEBUG-DYNIMGSET
=Title VAX DEBUG Message
Ident: DYNIMGSET
Message Text:
Setting image image_name
Severity: Informational
Explanation:
The debugger is automatically setting to the image
containing the current PC. This is only an
informational message.
None
DEBUG-DYNMODSET
=Title VAX DEBUG Message
Ident: DYNMODSET
Message Text:
Setting module path_name
Severity: Informational
Explanation:
The debugger is automatically setting to the module
containing the current PC. This is only an
informational message.
None
DEBUG-EDITDISVER
=Title VAX DEBUG Message
Ident: EDITDISVER
Message Text:
The original version is file_specification
Severity: Informational
Explanation:
The original file has been revised since the start
of the debug session. This message indicates that
source lines may not correspond to the ones used to
compile this module
Use SET SOURCE command to point to the original
source file if possible and re-attempt operation.
DEBUG-EDITERROR
=Title VAX DEBUG Message
Ident: EDITERROR
Message Text:
Error while trying to EDIT
Severity: Informational
Explanation:
An error occurred because of specifying a bad
command line or because of choosing an editor which
is not installed on this system.
Check command line syntax and re-enter, or select
an editor which is installed on the system. For
further information on the installed editors
contact your system manager.
DEBUG-EDITFILE
=Title VAX DEBUG Message
Ident: EDITFILE
Message Text:
Editing file file_specification
Severity: Informational
Explanation:
The debugger is currently setup to edit the file as
specified in the message. This is only an
informational message.
None
DEBUG-EDITNOFILE
=Title VAX DEBUG Message
Ident: EDITNOFILE
Message Text:
No source file to use for editing
Severity: Informational
Explanation:
This messages indicates that the debugger could not
find the specified source file to use for editing.
Use SET SOURCE command to point to the original
source file if possible and reattempt operation.
DEBUG-EDITREVVER
=Title VAX DEBUG Message
Ident: EDITREVVER
Message Text:
Editing a revised version of the original source
file
Severity: Informational
Explanation:
The original source file has been revised since the
start of the debug session. This message indicates
that future source line may not correspond to the
ones used to compile this module.
Use SET SOURCE command to point to the original
source file if possible and reattempt operation.
DEBUG-ENABLEAST
=Title VAX DEBUG Message
Ident: ENABLEAST
Message Text:
ASTs were disabled, are now enabled
Severity: Informational
Explanation:
Delivery of asynchronous system traps (ASTs) has
been turned off in your program by a DISABLE AST
command.
None
DEBUG-ENTRYMASK
=Title VAX DEBUG Message
Ident: ENTRYMASK
Message Text:
Entry mask has non-zero value in bits 12:13
Severity: Informational
Explanation:
This is an internal status signal, it should never
be seen by the user. If this message does occur
please submit a Software Performance Report (SPR).
Submit a Software Performance Report (SPR).
DEBUG-ENUMRANGE
=Title VAX DEBUG Message
Ident: ENUMRANGE
Message Text:
Enumeration value out of range
Severity: Informational
Explanation:
An error in your program indicates that the value
of this enumeration is out of range.
Examine this field in numeric format to determine
its value. Determine the error in your code and
make the appropriate corrections.
DEBUG-ERRACTIMG
=Title VAX DEBUG Message
Ident: ERRACTIMG
Message Text:
Unable to activate image
Severity: Informational
Explanation:
A bad status was returned from
LIB$FIND_IMAGE_SYMBOL. This message should be
issued in the $DBG_INFO context.
The image the debugger was trying to activate could
not be activated. The following error should help
to resolve the problem.
DEBUG-ERRASSIGN
=Title VAX DEBUG Message
Ident: ERRASSIGN
Message Text:
The attempt to acquire an I/O channel for the
debugger failed
Severity: Informational
Explanation:
A bad status was returned from a $ASSIGN type of
call. This message should be issued in the
$DBG_INFO context.
The debugger needs to acquire I/O channels to do
I/O. In this case the debugger failed to acquire
such a channel. Check your process quotas.
DEBUG-ERRCLSFILE
=Title VAX DEBUG Message
Ident: ERRCLSFILE
Message Text:
Unable to close file
Severity: Informational
Explanation:
A bad status was returned from a call to close a
file. This message should be issued in the
$DBG_INFO context.
The debugger failed to close a file. Unless the
reason for this is apparent, submit a Software
Performance Report (SPR).
DEBUG-ERRCRELNM
=Title VAX DEBUG Message
Ident: ERRCRELNM
Message Text:
Unable to create a logical name
Severity: Informational
Explanation:
The debugger creates logical names for input and
output redirection. This message should be issued
in the $DBG_INFO context.
Submit a Software Performance Report (SPR).
DEBUG-ERRDEASSIGN
=Title VAX DEBUG Message
Ident: ERRDEASSIGN
Message Text:
Attempt to deassign an I/O channel acquired by the
debugger failed
Severity: Informational
Explanation:
The debugger wanted to deassign an I/O channel that
is acquired for internal purposes. This error
notes the failure of the SYS$DASSGN system service,
probably due to an invalid channel.
Submit a Software Performance Report (SPR).
DEBUG-ERRFAO
=Title VAX DEBUG Message
Ident: ERRFAO
Message Text:
Unable to format output string
Severity: Informational
Explanation:
An error was returned from a call to $FAO.
Submit a Software Performance Report (SPR).
DEBUG-ERRGETDVI
=Title VAX DEBUG Message
Ident: ERRGETDVI
Message Text:
Unable to get device information
Severity: Informational
Explanation:
The debugger needed some information from $GETDVI
and the call failed. This indicates a programming
error. No doubt bad parameters were passed in.
Submit a Software Performance Report (SPR).
DEBUG-ERRGETEF
=Title VAX DEBUG Message
Ident: ERRGETEF
Message Text:
Attempt to allocate an event flag failed
Severity: Informational
Explanation:
The debugger wanted to allocate a local event flag
for it's own use. For some reason the routine
called to allocate the event flag failed. This
message is usually issued in the $DBG_INFO context.
The debugger needs event flags to operate. Check
the program being debugged for excessive allocation
of event flags.
DEBUG-ERRINSDEC
=Title VAX DEBUG Message
Ident: ERRINSDEC
Message Text:
Error occurred while decoding instruction at
current PC
Severity: Informational
Explanation:
The debugger has encountered an error during
decoding an instruction at the current PC
The address may be an entry mask, examine the
instruction 2 bytes beyond the specified address.
DEBUG-ERRINSIGNAL
=Title VAX DEBUG Message
Ident: ERRINSIGNAL
Message Text:
Signal arguments were incorrect, signal cannot be
decoded
Severity: Warning
Explanation:
The arguments which were passed as part of the
signal in your program were incorrect. The
debugger encountered an error in trying to analyze
the signal arguments. The error is shown in the
message following this message.
Analyze the arguments passed to LIB$SIGNAL by your
program, and correct the error.
DEBUG-ERRINVEDIT
=Title VAX DEBUG Message
Ident: ERRINVEDIT
Message Text:
Error invoking editor
Severity: Informational
Explanation:
While trying to invoke an editor a bad status was
returned.
Is the requested editor available and working
properly. If so, submit a Software Performance
Report (SPR).
DEBUG-ERROR
=Title VAX DEBUG Message
Ident: ERROR
Message Text:
Internal debugger error detected
Severity: Error
Explanation:
This message indicates an internal debugger error.
Correct the problem given by the messages following
this message. If the problem cannot be solved,
submit a Software Performance Report.
DEBUG-ERRORLIMIT
=Title VAX DEBUG Message
Ident: ERRORLIMIT
Message Text:
Error limit = error-limit, dumping terminated
Severity: Fatal
Explanation:
The error limit specified for the DST dump was
exceeded; the dumper was unable to continue
processing the input file. By default, the error
limit is set at 5. Use the /ERROR_LIMIT qualifier
to change the value.
DEBUG-ERROR_BLOCK
=Title VAX DEBUG Message
Ident: ERROR_BLOCK
Message Text:
Error handle signalled, address = address
Severity: Error
Explanation:
The debugger signalled an error handle. This
should never happen. The error handles are an
internal construct which are used to obtain
information within the debugger. They should never
appear in user-visible messages.
Submit a Software Performance Report (SPR)
DEBUG-ERRQIOW
=Title VAX DEBUG Message
Ident: ERRQIOW
Message Text:
Error from $QIOW
Severity: Informational
Explanation:
A bad status was returned from a call to $QIOW.
Submit a Software Performance Report (SPR).
DEBUG-ERRSMG
=Title VAX DEBUG Message
Ident: ERRSMG
Message Text:
Error returned from a call to the Screen Management
Facility (SMG)
Severity: Informational
Explanation:
A bad status was returned from a call to SMG. This
could be a result of any number of things which may
or may not be a debugger problem.
Check the user program for potential interactions
between it and the debugger; pasteboard sharing and
the like. Also, check the set up of the terminal
which might cause SMG some problem. If the error
still can't be explained submit a Software
Performance Report (SPR).
DEBUG-ERRSYSSERV
=Title VAX DEBUG Message
Ident: ERRSYSSERV
Message Text:
Error returned from an internal debugger system
service call
Severity: Informational
Explanation:
A bad status was returned from a call to a system
service. This message is to be in the context of
the $DBG_INFO macro which will list the particular
system service.
Submit a Software Performance Report (SPR).
DEBUG-ERRTARGOP
=Title VAX DEBUG Message
Ident: ERRTARGOP
Message Text:
Unable to perform operation for current target
system
Severity: Error
Explanation:
This is an internal debugger error.
If the error is reproducible, submit a Software
Performance Report and, if possible, enclose both a
copy of the program being debugged and a logged
debugging session that reproduces the error.
DEBUG-ERRUSREVNT
=Title VAX DEBUG Message
Ident: ERRUSREVNT
Message Text:
Error in user-specified event
Severity: Error
Explanation:
When attempting to process the specified event, the
debugger called the Run Time Library, which
returned an error status. The error status
returned by the Run Time Library follows this
message.
Correct the problem based on the associated message
which follows the debugger error message.
DEBUG-EXABEYREG
=Title VAX DEBUG Message
Ident: EXABEYREG
Message Text:
Attempt to examine beyond the end of a register
detected.
Severity: Error
Explanation:
A ranged examine command was specified that
attempted to examine beyond the end of a bounded
register.
Respecify the command so that it does not go past
the end of the register.
DEBUG-EXARANGE
=Title VAX DEBUG Message
Ident: EXARANGE
Message Text:
Invalid range of addresses
Severity: Error
Explanation:
The first address of a range to examine must be
less than the second address in this range.
Enter the address range specifying the addresses in
increasing order.
DEBUG-EXCBREREP
=Title VAX DEBUG Message
Ident: EXCBREREP
Message Text:
Exception breakpoint replaced
Severity: Informational
Explanation:
A SET BREAK/EXCEPTION was done when exception
breaks were already in effect. The old exception
break was replaced with the new one.
Submit an SPR. This message is handled internally,
and should never be signaled to the user.
DEBUG-EXCDURCAL
=Title VAX DEBUG Message
Ident: EXCDURCAL
Message Text:
Error occurred while executing routine called from
exception break
Severity: Error
Explanation:
While executing a routine called from an exception
break using the CALL command, an exception
occurred. Any exceptions from routines called from
an exception break cause this message to be
displayed followed by the text of the exception.
Execution of the called routine is then terminated.
Either correct the CALL command if it was in error,
or correct the routine that caused the exception.
To use the debugger to help find the cause of the
exception, try calling the routine while not at an
exception break.
DEBUG-EXITARG
=Title VAX DEBUG Message
Ident: EXITARG
Message Text:
Exitloop argument num_levels is too large
Severity: Warning
Explanation:
The parameter specified on the EXITLOOP command is
greater than the number of loops nested at this
time. It is also possible that you have specified
an EXITLOOP command when you are not inside of a
loop.
Reduce the parameter on the EXITLOOP command to no
more than the number of loops nested at the time
the EXITLOOP command is to be executed. If there
are no loops currently being executed, then the
EXITLOOP command is redundant.
DEBUG-EXITERR
=Title VAX DEBUG Message
Ident: EXITERR
Message Text:
An error occurred while trying to exit the program
Severity: Error
Explanation:
An error status was returned from the call to the
debugger-kernel service that terminates program
execution. Depending on the severity of the error,
the program may or may not have terminated.
Examine the error message after this message and
consider if the problem is related to a lack of
quota or otherwise related to your program's
behavior. If so, then take corrective action. If,
after this evaluation, you believe that the problem
lies in the debugger, then submit a Software
Performance Report.
DEBUG-EXITSTATUS
=Title VAX DEBUG Message
Ident: EXITSTATUS
Message Text:
Is 'status_value'
Severity: Informational
Explanation:
The program has exited with the status
status_value.
None.
DEBUG-EXPMEMPOOL
=Title VAX DEBUG Message
Ident: EXPMEMPOOL
Message Text:
Expanding debugger memory pool
Severity: Informational
Explanation:
The debugger kernel maintains a memory pool from
which it allocates data structures to keep track of
breakpoints, tracepoints, watchpoints, and so on.
The initial size of the memory pool is 256 pages.
The memory pool is expanded automatically when
needed, and this informational is signaled when
memory pool expansion occurs. If you have set a
large number of breakpoints, tracepoints, or
watchpoints, this message is to be expected.
If this message appears for no evident reason
(i.e., you have not set a large number of
breakpoints, tracepoints, or watchpoints), there
may be something wrong with the debugger. In this
case, submit an SPR.
DEBUG-FAILFINDIMG
=Title VAX DEBUG Message
Ident: FAILFINDIMG
Message Text:
The debugger could not find the DECwindows image to
be initialized.
Severity: Fatal
Explanation:
The debugger could not find the DECwindows image
that it was trying to initialize.
Try the debugger again, if the same results exist
submit a Software Performance Report (SPR).
DEBUG-FAILHEIRKY
=Title VAX DEBUG Message
Ident: FAILHEIRKY
Message Text:
The debugger could not open the user interface
definition file, SYS$LIBRARY:DEBUGUIL.UID.
Severity: Fatal
Explanation:
The debugger could not find one of the necessary
file to support the DECWindows interface,
preventing the debugger from continuing this
session.
Check for the exsistance and accessability of
SYS$LIBRARY:DEBUGUIL.UID. For further assistance
and information on this probelm check with your
system manager.
DEBUG-FAILXTINIT
=Title VAX DEBUG Message
Ident: FAILXTINIT
Message Text:
The debugger detected an error when trying to
connect to the DECWindow software.
Severity: Fatal
Explanation:
The debugger failed to establish a connection to
the X server preventing the debugger from
continuing this session.
Try the debugger again, if the same results exist
submit a Software Performance Report (SPR).
DEBUG-FATALSTATUS
=Title VAX DEBUG Message
Ident: FATALSTATUS
Message Text:
A fatal condition was detected by the debugger.
Severity: Fatal
Explanation:
The debugger got an unexpected status from the
system service or RTL routine routine-name which
prevents this DEBUG session from continuing.
Examine the error message and consider if the
problem is related to a lack of quota or otherwise
related to your program's behavior. If so, then
take corrective action. If, after this evaluation,
you believe that the problem lies in the debugger,
then submit a Software Performance Report.
DEBUG-FILEUNAL
=Title VAX DEBUG Message
Ident: FILEUNAL
Message Text:
File not available
Severity: Warning
Explanation:
The source file for the given program cannot be
read.
Change the protections on the source file, or use
SET SOURCE to tell the Debugger where the source
file really exists.
DEBUG-FLTOVF
=Title VAX DEBUG Message
Ident: FLTOVF
Message Text:
Floating overflow at or near opcode_name
Severity: Error
Explanation:
The value being deposited does not fit into the
specified address.
Specify either a smaller value or a different
target address.
DEBUG-HEIGHTDIFF
=Title VAX DEBUG Message
Ident: HEIGHTDIFF
Message Text:
Desired height of specified_height is not allowed,
height is set to actual_height
Severity: Informational
Explanation:
The device specified by DBG$OUTPUT had a screen
height that wasn't in the range of 18-100.
Use SHOW TERMINAL command and verify that the
terminal height is correct, it is in the range
18-100, and is pointing to a valid terminal type.
DEBUG-IDENTLONG
=Title VAX DEBUG Message
Ident: IDENTLONG
Message Text:
Identifier too long, please shorten
Severity: Error
Explanation:
Identifiers in address expressions must be shorter
than 256 characters.
Enter a shorter identifier.
DEBUG-IFIXUND
=Title VAX DEBUG Message
Ident: IFIXUND
Message Text:
Precision lost during fixed point operation
Severity: Informational
Explanation:
While doing operations on fixed point data items,
the debugger recognized that some precision was
lost.
You should understand that the result of the
operation is imprecise and may not be exactly what
you expect.
DEBUG-IFLTUND
=Title VAX DEBUG Message
Ident: IFLTUND
Message Text:
Floating underflow at or near opcode_name
Severity: Informational
Explanation:
While performing the arithmetic operation, a
floating-point value became less than the smallest
representable value for that data type.
You should understand that the result of the
operation is imprecise and may not be exactly what
you expect.
DEBUG-IINTOVF
=Title VAX DEBUG Message
Ident: IINTOVF
Message Text:
Integer overflow at or near opcode_name
Severity: Informational
Explanation:
While performing the arithmetic operation, a
floating-point value exceeded the largest
representable value for that data type.
You should understand that the result of the
operation is imprecise and may not be exactly what
you expect.
DEBUG-ILLADDCON
=Title VAX DEBUG Message
Ident: ILLADDCON
Message Text:
Illegal constant constant_name in address
expression
Severity: Warning
Explanation:
The constant in the message evaluates to a
non-integer type. Only integer types can be used
in an address expression.
Change the constant to the appropriate integer
value.
DEBUG-ILLASTER
=Title VAX DEBUG Message
Ident: ILLASTER
Message Text:
Subscript range ('*') not permitted here (must be
at lowest level of data structure)
Severity: Warning
Explanation:
The debugger does not allow an asterisk as a range
in an EXAMINE except as the last index in the
array. That is, the memory to examine must be a
contiguous region. Unconnected slices of arrays
are not allowed.
Remove the asterisk from the expression to examine.
Placing the corrected EXAMINE inside a Debugger FOR
loop command could provide the functionality needed
to do the command as originally desired.
DEBUG-ILLDEFNAM
=Title VAX DEBUG Message
Ident: ILLDEFNAM
Message Text:
Illegal name for DEFINE: defined_name
Severity: Warning
Explanation:
A defined name must be non-null.
Enter a non-null name to DEFINE.
DEBUG-ILLENUMVAL
=Title VAX DEBUG Message
Ident: ILLENUMVAL
Message Text:
Enumeration value out of legal range
Severity: Warning
Explanation:
The predecessor (or successor) function has been
used on the first (or last) component of the
enumeration. The result would not be a valid value
of the enumeration.
Do not use the predecessor (or successor) function
on the first (or last) component of the
enumeration.
DEBUG-ILLEVNSTR
=Title VAX DEBUG Message
Ident: ILLEVNSTR
Message Text:
Attempt to pass an illegal event structure, name =
structure-name
Severity: Fatal
Explanation:
This message indicates an internal debugger error.
Submit an SPR.
DEBUG-ILLFILPTR
=Title VAX DEBUG Message
Ident: ILLFILPTR
Message Text:
File variable points to invalid file descriptor
Severity: Warning
Explanation:
The file variable references a file descriptor that
cannot be read, is incomplete, or points to a file
that is not open.
Correct the file descriptor.
DEBUG-ILLFLOAT
=Title VAX DEBUG Message
Ident: ILLFLOAT
Message Text:
Float_value is an illegal floating point value
Severity: Warning
Explanation:
The Debugger attempted to parse the given floating
point number and encountered an illegal character.
Correct the floating point number.
DEBUG-ILLINVNUM
=Title VAX DEBUG Message
Ident: ILLINVNUM
Message Text:
Invalid invocation number at invoc_num
Severity: Error
Explanation:
An illegal invocation number was specified (must be
in decimal radix).
Specify a legal decimal invocation number.
DEBUG-ILLLENGTH
=Title VAX DEBUG Message
Ident: ILLLENGTH
Message Text:
Illegal length field length_value in structure
reference
Severity: Warning
Explanation:
A negative value was given for the length of a
field in a structure reference.
Change the field length to a non-negative value.
DEBUG-ILLNUMPATH
=Title VAX DEBUG Message
Ident: ILLNUMPATH
Message Text:
Illegal numeric pathname at path_name
Severity: Error
Explanation:
An illegal numeric pathname was specified (must be
in decimal radix).
Specify a legal decimal numeric pathname.
DEBUG-ILLPACSIZ
=Title VAX DEBUG Message
Ident: ILLPACSIZ
Message Text:
Illegal packed size size_value; must be 0..31
Severity: Warning
Explanation:
The specified size on a /PACKED qualifier is
illegal. It must be a value between 0 and 31.
Specify a legal value with the /PACKED qualifier.
DEBUG-ILLPATH1
=Title VAX DEBUG Message
Ident: ILLPATH1
Message Text:
Illegal use of %SOURCE_SCOPE (must not be combined
with invocation numbers)
Warning %SOURCE_SCOPE has been used in the same
path with other scope numbers.
Remove all but one of the references to the desired
scope.
DEBUG-ILLPATH2
=Title VAX DEBUG Message
Ident: ILLPATH2
Message Text:
Illegal use of %SOURCE_SCOPE (must appear at the
start of the pathname)
Warning %SOURCE_SCOPE has been used in a path name
in an illegal position. The %SOURCE_SCOPE lexical
must be the first item in the path list.
Move the %SOURCE_SCOPE lexical to the first
position in the pathname.
DEBUG-ILLPATHELEM
=Title VAX DEBUG Message
Ident: ILLPATHELEM
Message Text:
Illegal pathname element at path_name
Severity: Error
Explanation:
Invocation numbers cannot be used with other
pathnames.
Eliminate the continuation of the pathname after
the invocation number.
DEBUG-ILLPATHIDENT
=Title VAX DEBUG Message
Ident: ILLPATHIDENT
Message Text:
Unknown identifier in pathname at path_name
Severity: Error
Explanation:
An illegal identifier was specified in the
pathname.
Specify a legal identifier.
DEBUG-ILLPOSFLD
=Title VAX DEBUG Message
Ident: ILLPOSFLD
Message Text:
Position field value position_value is too large
Severity: Warning
Explanation:
The value of the position specifier in the BLISS
field reference is an incredibly large number,
larger than the Debugger can handle. The value may
be negative, which is also illegal.
Change the value of the position specifier in the
BLISS field reference to a smaller (or positive)
value.
DEBUG-ILLQUALIF
=Title VAX DEBUG Message
Ident: ILLQUALIF
Message Text:
Illegal or unsupported qualifier on SPAWN command
Severity: Warning
Explanation:
One of the qualifiers to the SPAWN command is
incorrect.
Remove the incorrect qualifier to the SPAWN
command.
DEBUG-ILLRANGE
=Title VAX DEBUG Message
Ident: ILLRANGE
Message Text:
Subscript range not permitted here (must be at
lowest level of data structure)
Severity: Warning
Explanation:
The Debugger does not allow a range in an EXAMINE
except as the last index in the array. That is,
the memory to examine must be a contiguous region.
Unconnected slices of arrays are not allowed.
Remove the range from the expression to examine.
Placing the corrected EXAMINE inside a Debugger FOR
loop command could provide the functionality needed
to do the command as originally desired.
DEBUG-ILLSETCON
=Title VAX DEBUG Message
Ident: ILLSETCON
Message Text:
Illegal set constant in expression
Severity: Warning
Explanation:
One of the constants specified in the given set
expression has a type that is inconsistent with the
set type.
Change the erroneous set constant value to a
constant with a type that agrees with the set type.
DEBUG-ILLSIGEXT
=Title VAX DEBUG Message
Ident: ILLSIGEXT
Message Text:
Illegal sign extension field value extension_value
Severity: Warning
Explanation:
An illegal value has been entered for the sign
extension field in a field reference.
Re-enter the command using a valid sign extension
field value.
DEBUG-ILLSIZFLD
=Title VAX DEBUG Message
Ident: ILLSIZFLD
Message Text:
Illegal size field size_value; must be 0..32
Severity: Warning
Explanation:
The size value for a BLISS field reference contains
an illegal value.
Change the size value of the field reference to an
integer between 0 and 32, inclusive.
DEBUG-ILLSUBLEN
=Title VAX DEBUG Message
Ident: ILLSUBLEN
Message Text:
Substring length larger than 32K not supported
Severity: Warning
Explanation:
The calculated length of a substring in the
expression is larger than can be handled by the
Debugger.
Do not use a substring with a length greater than
32K in an expression to be evaluated by the
Debugger.
DEBUG-ILLSUBSTR
=Title VAX DEBUG Message
Ident: ILLSUBSTR
Message Text:
Can only apply substring operation to string data
types
Severity: Warning
Explanation:
The Debugger has found a substring operation, but
the data type of the operand is not a string type.
Correct the data type of the string operand in the
substring expression.
DEBUG-ILLTYPE
=Title VAX DEBUG Message
Ident: ILLTYPE
Message Text:
Illegal type of operand(s)
Severity: Warning
Explanation:
The type of the operand is illegal for the operator
specified.
Change the operand.
DEBUG-ILLVQUAL
=Title VAX DEBUG Message
Ident: ILLVQUAL
Message Text:
Illegal vector instruction qualifier specified at
'command_line'
Severity: Error
Explanation:
A vector instruction qualifier that is illegal for
this vector instruction was specified during a
DEPOSIT/INSTRUCTION command.
Do not specify that illegal qualifier on that
instruction.
DEBUG-INCDSTNES
=Title VAX DEBUG Message
Ident: INCDSTNES
Message Text:
Incorrect DST nesting in module path_name, compiler
error
Severity: Error
Explanation:
Incorrect symbol table nesting occurred, such as
improper routine or data record nesting in the
specified module. This message normally indicates
a compiler error.
Submit a Software Performance Report.
DEBUG-INCOMPOPR
=Title VAX DEBUG Message
Ident: INCOMPOPR
Message Text:
Operand number operand_number incomplete
Severity: Error
Explanation:
When parsing an instruction, the debugger found an
incomplete operand.
Specify complete operands when entering machine
instructions.
DEBUG-INCOMPPTR
=Title VAX DEBUG Message
Ident: INCOMPPTR
Message Text:
Pointers of different size, cannot perform
subtraction
Severity: Warning
Explanation:
The two pointers point to objects with incompatible
types. A computation involving these pointers does
not have a meaningful result.
Do not attempt to mix pointers of different types
in arithmetic computations.
DEBUG-INCOMQUAL
=Title VAX DEBUG Message
Ident: INCOMQUAL
Message Text:
Qualifier qualifier_name is not compatible with
qualifier_name(s)
Severity: Warning
Explanation:
Qualifiers specified with the command conflict in
their operations.
Specify non-conflicting qualifiers.
DEBUG-INCOMTARGET
=Title VAX DEBUG Message
Ident: INCOMTARGET
Message Text:
A debugger_type kernel debugger is incompatible
with a debugger_type main debugger
Severity: Error
Explanation:
A kernel debugger attempted to connect to a main
debugger with which it is not compatible.
Make sure that the logical names used to point at
the sharable and non_sharable debugger images are
defined to point to the same type of debuggers.
DEBUG-INCOMVERSION
=Title VAX DEBUG Message
Ident: INCOMVERSION
Message Text:
The RPC versions of the main and kernel debuggers
are incompatible
Severity: Error
Explanation:
A kernel debugger attempted to connect to a main
debugger with which it is not compatible.
Make sure that the logical names used to point at
the sharable and non_sharable debugger images are
defined to point to the same type of debuggers.
DEBUG-INDBASEQL
=Title VAX DEBUG Message
Ident: INDBASEQL
Message Text:
Index and base registers are equal for operand
number operand_number
Severity: Error
Explanation:
When parsing an instruction, the debugger found an
operand whose base register and index registers
were the same. The VAX instruction architecture
forbids this construction.
Specify different registers for the base and index
registers.
DEBUG-INITERR
=Title VAX DEBUG Message
Ident: INITERR
Message Text:
An error has occurred during debugger
initialization, unable to continue this session.
Severity: Fatal
Explanation:
The debugger encountered an error during
initialization which does not allow this debugging
session to proceed.
Use the message which preceded this message to
analyze and correct the error, and try again.
DEBUG-INITIAL
=Title VAX DEBUG Message
Ident: INITIAL
Message Text:
Language is language_name, module set to path_name
Severity: Informational
Explanation:
This message is displayed when the debugger is
invoked by the image activator. The language is
set to language_name, and the module to path_name.
Module path_name is the first module specified in
the LINK command, and language language_name is the
language used in that module.
None.
DEBUG-INPREADERR
=Title VAX DEBUG Message
Ident: INPREADERR
Message Text:
Error reading input line:
Severity: Warning
Explanation:
There was an error from the system while trying to
read the input line.
Re-enter the command line. Check to see that the
Debugger has read access to the input source. If
the problem persists, submit a Software Performance
Report (SPR).
DEBUG-INSVIRMEM
=Title VAX DEBUG Message
Ident: INSVIRMEM
Message Text:
Insufficient virtual memory for the debugger memory
pool
Severity: Informational
Explanation:
An attempt to allocate additional memory for
working storage failed.
Cancel set modules to free space in memory.
DEBUG-INTERR
=Title VAX DEBUG Message
Ident: INTERR
Message Text:
Internal debugger error in debugger_routine_name
Severity: Error
Explanation:
An internal debugger error has been encountered.
If the error is reproducible, submit a Software
Performance Report and, if possible, enclose both a
copy of the program being debugged and a logged
debugging session that reproduces the error.
DEBUG-INTERRUPTED
=Title VAX DEBUG Message
Ident: INTERRUPTED
Message Text:
Process interrupted via cross-process signal
Severity: Fatal
Explanation:
This signal is delivered asyncronously to a process
to cause the debugger to be invoked in that
process.
Submit an SPR. This message is handled internally,
and should never be signaled to the user.
DEBUG-INTMEMERR
=Title VAX DEBUG Message
Ident: INTMEMERR
Message Text:
Internal memory-pool error
Severity: Fatal
Explanation:
The debugger's internal memory area has been
corrupted or is inconsistent. This can be caused
by an internal debugger error or by random stores
by the user program.
Correct the user program or submit a Software
Performance Report.
DEBUG-INTOVF
=Title VAX DEBUG Message
Ident: INTOVF
Message Text:
Integer overflow at or near opcode_name
Severity: Error
Explanation:
The value being deposited does not fit into the
specified address.
Specify either a smaller value or a different
target address.
DEBUG-INTVECERR
=Title VAX DEBUG Message
Ident: INTVECERR
Message Text:
Internal debugger coding error in using vector
instruction(s)
Severity: Error
Explanation:
An internal debugger error has been encountered
when attempting to execute a vector instruction.
Messages will follow this text which will more
fully explain the error.
If the error is reproducible, submit a Software
Performance Report and, if possible, enclose both a
copy of the program being debugged and a logged
debugging session that reproduces the error.
DEBUG-INUMTRUNC
=Title VAX DEBUG Message
Ident: INUMTRUNC
Message Text:
Number truncated at or near opcode_name
Severity: Informational
Explanation:
On some conversions packed numbers need to be
truncated to fit into their destination.
Truncation is done from the least significant digit
to the most significant digit.
You should understand that the result of the
operation is imprecise and may not be exactly what
you expect.
DEBUG-INVARGLIS
=Title VAX DEBUG Message
Ident: INVARGLIS
Message Text:
Invalid argument list for 'the
debugger_command_segment'
Severity: Warning
Explanation:
There is an error with the argument list. The
Debugger may be expecting an argument list when
none was supplied. The Debugger may have found an
argument list where one was not expected. The
Debugger may have found an argument list that was
too long or too short. Finally, the Debugger may
have found an inconsistency in the argument list.
Correct the command. Supply the correct argument
list if one was missing or in error. Delete the
inappropriate argument list, if one was present.
DEBUG-INVARRDIM
=Title VAX DEBUG Message
Ident: INVARRDIM
Message Text:
Array dimension is out of range
Severity: Warning
Explanation:
The array dimension is out of the range of the
declared size and shape of the array. Either the
dimension requested is less than zero, or it is
greater than the number of dimensions the array was
declared with.
Correct the invalid array dimension.
DEBUG-INVARRDSC
=Title VAX DEBUG Message
Ident: INVARRDSC
Message Text:
Invalid array descriptor
Severity: Error
Explanation:
An array descriptor in the image does not have the
correct format. This can be caused by a reference
to a VAX BASIC array when the first line of the
program has not been executed. The array is not
set up correctly until the BASIC program
initialization is done. This message can also be
caused by a user program or DEPOSIT commands
altering a compiler generated array descriptor.
If the reference is to a VAX BASIC array, enter a
STEP or GO command to ensure that the BASIC program
initialization is done and then repeat the
reference. Otherwise, if an array descriptor has
not been altered, submit a Software Performance
Report.
DEBUG-INVCHAR
=Title VAX DEBUG Message
Ident: INVCHAR
Message Text:
Invalid character
Severity: Error
Explanation:
When parsing the command, an invalid character was
detected.
Enter the command specifying only valid characters.
DEBUG-INVCHRCON
=Title VAX DEBUG Message
Ident: INVCHRCON
Message Text:
Invalid character constant in expression
Severity: Error
Explanation:
When evaluating a language expression, the debugger
expected to find a closing single quote mark, or
the end of the command. Some other character was
found, which resulted in an illegal language
expression.
Enter a valid language expression.
DEBUG-INVDESC
=Title VAX DEBUG Message
Ident: INVDESC
Message Text:
Invalid string descriptor
Severity: Error
Explanation:
This message indicates an internal debugger error.
Submit a Software Performance Report.
DEBUG-INVDIGBIN
=Title VAX DEBUG Message
Ident: INVDIGBIN
Message Text:
Invalid digit in binary number: number_value
Severity: Error
Explanation:
A numeric value other than '0' and '1' was found in
a binary number.
Enter binary numbers specifying only digits '0' and
'1'.
DEBUG-INVDIGDEC
=Title VAX DEBUG Message
Ident: INVDIGDEC
Message Text:
Invalid digit in decimal number: number_value
Severity: Error
Explanation:
A numeric value other than in the range '0' through
'9' was found in a decimal number.
Enter decimal numbers specifying only digits '0'
through '9'.
DEBUG-INVDIGHEX
=Title VAX DEBUG Message
Ident: INVDIGHEX
Message Text:
Invalid digit in hexadecimal number: number_value
Severity: Error
Explanation:
A numeric value other than in the range '0' through
'9' or an alphabetic value other than in the range
'A' through 'F' was found in a hexadecimal number.
Hexadecimal numbers must also start with a numeric
character, for example '0F'.
Enter hexadecimal numbers specifying only digits
'0' through '9' and alphabetic values 'A' through
'F'.
DEBUG-INVDIGOCT
=Title VAX DEBUG Message
Ident: INVDIGOCT
Message Text:
Invalid digit in octal number: number_value
Severity: Error
Explanation:
A numeric value other than in the range '0' through
'7' was found in a decimal number.
Enter decimal numbers specifying only digits '0'
through '7'.
DEBUG-INVDIRNAM
=Title VAX DEBUG Message
Ident: INVDIRNAM
Message Text:
Invalid directory name: file_specification
Severity: Error
Explanation:
The directory name 'file_specification' given in a
DEBUGGER command SET SOURCE is not valid. Either
the directory syntax is incorrect or the directory
does not exist.
Ensure that the directory exists and that the
syntax is correct.
DEBUG-INVDMTPTR
=Title VAX DEBUG Message
Ident: INVDMTPTR
Message Text:
Invalid DMT pointer; internal linker or debugger
error
Severity: Informational
Explanation:
The debugger found that the pointer in the image
header to the Debug Module Table (DMT) was invalid.
The debugger will continue from this error trying
to initialize based on the Debug Symbol Table
(DST).
Check that the image file hasn't been modified or
corrupted in some way. If not, submit a Software
Performance Report (SPR).
DEBUG-INVDSPSIZ
=Title VAX DEBUG Message
Ident: INVDSPSIZ
Message Text:
Invalid display size: display_size
Severity: Error
Explanation:
The SIZE value for a display must be between 1 and
1000.
Specify the SIZE value between 1 and 1000.
DEBUG-INVDSTREC
=Title VAX DEBUG Message
Ident: INVDSTREC
Message Text:
Invalid DST record
Severity: Error
Explanation:
The debugger has detected an error in the Debug
Symbol Table of your program. This indicates an
internal error in either the debugger or the
compiler of this module.
Please submit a Software Performance Report.
DEBUG-INVEXPR
=Title VAX DEBUG Message
Ident: INVEXPR
Message Text:
Invalid expression for operand number
operand_number
Severity: Error
Explanation:
The specified operand was not correct for this
instruction.
Please check the documentation for the correct
operands for this instruction, and re-enter the
instruction with the correct operands.
DEBUG-INVFIXDST
=Title VAX DEBUG Message
Ident: INVFIXDST
Message Text:
Invalid DST fixup records in image image_name,
symbol references to shareable images may be
erroneous
Severity: Informational
Explanation:
While attempting to read the symbol table
information in the specified image, the debugger
found errors in the symbol table address fixup
records. These records are used to adjust for the
base addresses of shareable images. This means
that any symbols in this image which point to
addresses in other (shareable) images will most
likely be incorrect. Symbols which refer to
addresses in this image will be correct unless this
is also a shareable image.
Relink the image and, if the error is reproducible,
submit a Software Performance Report explaining how
the image file was created.
DEBUG-INVFLDREF
=Title VAX DEBUG Message
Ident: INVFLDREF
Message Text:
Invalid field reference; too many or few parameters
Severity: Warning
Explanation:
The Debugger could not complete the parse of the
BLISS field reference specification. Either the
closing angle bracket terminator was found too
soon, or it was not found when it was expected.
Correct the field reference.
DEBUG-INVGSTREC
=Title VAX DEBUG Message
Ident: INVGSTREC
Message Text:
Invalid GST record
Severity: Error
Explanation:
The debugger has detected an error in the Global
Symbol Table of your program. This indicates an
internal error in either the debugger or the
compiler of this module.
Please submit a Software Performance Report.
DEBUG-INVGSTTYP
=Title VAX DEBUG Message
Ident: INVGSTTYP
Message Text:
Invalid GST record; GST is partially built
Severity: Informational
Explanation:
The debugger found an invalid Global Symbol Table
(GST) record in the image. The debugger will
discontinue initializing the GST at this point.
The debugger will continue from this error, however
global symbol information may not be complete.
Check that the image file hasn't been modified or
corrupted in some way. If not, submit a Software
Performance Report (SPR).
DEBUG-INVMAR
=Title VAX DEBUG Message
Ident: INVMAR
Message Text:
Right margin must be greater than left
Severity: Warning
Explanation:
You specified a right margin that was less than the
left margin in the debugger command SET MARGIN.
The right margin must be greater than the left
margin.
Re-enter the command specifying a valid margin
range.
DEBUG-INVNUMBER
=Title VAX DEBUG Message
Ident: INVNUMBER
Message Text:
Invalid numeric string 'number_value'
Severity: Error
Explanation:
A numeric value which was not in the specified
radix was found in the language expression.
Enter numbers specifying only valid digits for that
radix.
DEBUG-INVNUMSRC
=Title VAX DEBUG Message
Ident: INVNUMSRC
Message Text:
Invalid number of source files
Severity: Warning
Explanation:
An invalid number of source files was specified on
the SET MAX_SOURCE_FILES command. The maximum
number of source files that the debugger will keep
open simultaneously must be in the range of 1
through 20.
Re-enter the command specifying a valid number
within the range.
DEBUG-INVNUMSTR
=Title VAX DEBUG Message
Ident: INVNUMSTR
Message Text:
Invalid numeric string at or near 'number_value'
Severity: Error
Explanation:
The debugger encountered an error when
attempting to convert the specified value.
This indicates that the string value did not
contain a valid number.
Ensure that the string value contains only valid
digits.
DEBUG-INVOPADDR
=Title VAX DEBUG Message
Ident: INVOPADDR
Message Text:
Invalid operator 'operator_symbol' in address
expression
Severity: Error
Explanation:
Address expressions cannot contain operators.
Enter the address expression without operators.
DEBUG-INVOPSYM
=Title VAX DEBUG Message
Ident: INVOPSYM
Message Text:
Invalid operator symbol 'operator_symbol' in
expression
Severity: Error
Explanation:
Identifiers in address expressions must be shorter
than 256 characters.
Enter a shorter identifier.
DEBUG-INVPAGE
=Title VAX DEBUG Message
Ident: INVPAGE
Message Text:
Invalid screen height, value must be between
minimum_height and maximum_height
Severity: Error
Explanation:
The height of the terminal which the debugger uses
to place it's windows must be between the values
specified.
Specify the page size of the screen to be between
the values specified.
DEBUG-INVPRCSYN
=Title VAX DEBUG Message
Ident: INVPRCSYN
Message Text:
Process specification syntax error
Severity: Error
Explanation:
The specified process specification is
syntactically invalid
Re-enter the command specifying a correct process
specification
DEBUG-INVPRIOR
=Title VAX DEBUG Message
Ident: INVPRIOR
Message Text:
Invalid task priority value specified
Severity: Error
Explanation:
The priority of an Ada task must be between 0 and
15.
Specify a valid priority for the task.
DEBUG-INVRANSPEC
=Title VAX DEBUG Message
Ident: INVRANSPEC
Message Text:
Invalid range specification in array subscript
Severity: Warning
Explanation:
A range specification in an array reference is
illegal. The Debugger may have found a range where
none is allowed. An asterisk may have been used as
a range where it is not allowed. The array
subscripts may have more than one set of ranges,
which is not allowed. The range may be invalid,
with bounds greater than the declared bounds of the
array. Finally, the lower bound of the range may
be greater than the upper bound of the array.
Correct the range specification in the array
subscript.
DEBUG-INVSELDIS
=Title VAX DEBUG Message
Ident: INVSELDIS
Message Text:
Invalid selection of display_name display; wrong
display kind
Severity: Error
Explanation:
Some attributes can only be placed on certain types
of displays. For example, the SOURCE attribute can
only be placed on source displays. The attribute
you specified cannot be placed on the display you
specified.
See the debugger documentation of the SELECT
command for details on which attributes can be
placed on which displays. Specify attributes which
are compatible with the display kind.
DEBUG-INVSRCLIN
=Title VAX DEBUG Message
Ident: INVSRCLIN
Message Text:
Invalid source line range
Severity: Warning
Explanation:
An invalid source line range was entered in the
debugger TYPE command. The first line number of
the range must be non-negative and less than or
equal to the second number in the range.
Re-enter the command specifying a valid line number
range.
DEBUG-INVTIMSLI
=Title VAX DEBUG Message
Ident: INVTIMSLI
Message Text:
Time slice was not set, parameter is out of range
of Ada type DURATION
Severity: Error
Explanation:
The value specified for the time slice was out of
range of the Ada type DURATION.
See the Ada documentation for the range of the
DURATION type. Specify time slice values which are
in range of type DURATION.
DEBUG-INVWIDTH
=Title VAX DEBUG Message
Ident: INVWIDTH
Message Text:
Invalid screen width, value must be between
minimum_width and maximum_width
Severity: Error
Explanation:
The width of the terminal which the debugger uses
to place its windows must be between the values
specified.
Specify the width of the screen to be between the
values specified.
DEBUG-INVWINPAR
=Title VAX DEBUG Message
Ident: INVWINPAR
Message Text:
Invalid window parameter: number_value
Severity: Error
Explanation:
The value specified was out of range of the screen
on which the window will be placed. If the
debugger is placing its windows on a terminal
screen, the beginning row and column numbers must
be between 1 and the height and width of the
screen, and the beginning value plus the height or
width of the window must not exceed the height or
width of the terminal screen. If the debugger is
running with the DECwindows interface, the
beginning row and column numbers must be greater
than 0.
Specify valid parameters for the window row and
column values, and for the height and width of the
window.
DEBUG-IRFAOVF
=Title VAX DEBUG Message
Ident: IRFAOVF
Message Text:
Record file address overflow at or near opcode_name
Severity: Informational
Explanation:
The conversion of the ASCII string to a record file
address caused an overflow. The conversion was
performed however.
Check the value to make sure the conversion
performed as expected.
DEBUG-ISTRTRU
=Title VAX DEBUG Message
Ident: ISTRTRU
Message Text:
String truncated at or near opcode_name
Severity: Informational
Explanation:
The string did not fit into the specified
destination resulting in lost trailing characters.
The conversion was performed however.
Check the value to make sure the conversion
performed as expected.
DEBUG-ITMNOTAVA
=Title VAX DEBUG Message
Ident: ITMNOTAVA
Message Text:
Item not available
Severity: Warning
Explanation:
The user should never see this message. The
debugger uses an item list construct for passing
information between its parts. This message
indicates that the requesting routine requested
data which the target routine was not capable of
providing. Appearance of this message indicates an
internal problem in the debugger.
Submit a Software Performance Report (SPR)
DEBUG-ITMTRUNC
=Title VAX DEBUG Message
Ident: ITMTRUNC
Message Text:
Item truncated - buffer of insufficient size
Severity: Warning
Explanation:
The user should never see this message. The
debugger uses an item list construct for passing
information between its parts. This message
indicates that the requesting routine allocated a
buffer which was too small for the requested data.
Appearance of this message indicates an internal
problem in the debugger.
Submit a Software Performance Report (SPR)
DEBUG-IVALNOFIT
=Title VAX DEBUG Message
Ident: IVALNOFIT
Message Text:
Value does not fit into target location at or near
opcode_name
Severity: Informational
Explanation:
The value can not be represented in the target
location and may be truncated. The bit field is
not large enough to hold the value.
Check the value in the target location.
DEBUG-IVALOUTBNDS
=Title VAX DEBUG Message
Ident: IVALOUTBNDS
Message Text:
Value assigned is out of bounds at or near
opcode_name
Severity: Informational
Explanation:
The value is out of the bounds defined for the
data. The operation was performed however.
Check the results of the operation to make sure
they are as you expected.
DEBUG-IVPRCLOG
=Title VAX DEBUG Message
Ident: IVPRCLOG
Message Text:
Logical name DBG$PROCESS must be either
MULTIPROCESS or DEFAULT
Severity: Fatal
Explanation:
The logical name DBG$PROCESS translates to
something other than "MULTIPROCESS" or "DEFAULT".
Correct the logical name assignment for DBG$PROCESS
and try again.
DEBUG-KERFUNCNYI
=Title VAX DEBUG Message
Ident: KERFUNCNYI
Message Text:
Kernel Function function_name not yet implemented
on this architecture
Severity: Error
Explanation:
This message indicates an internal debugger error.
Submit a Software Performance Report.
DEBUG-KEYNAMERR
=Title VAX DEBUG Message
Ident: KEYNAMERR
Message Text:
Unrecognized key name: key_name
Severity: Error
Explanation:
This keyname <key_name, !AS> is in error. It can
not be defined by the user.
Check spelling of the key name.
DEBUG-KEYSTATERR
=Title VAX DEBUG Message
Ident: KEYSTATERR
Message Text:
Unrecognized state name: state_name
Severity: Error
Explanation:
This key state <state_name, !AS> is in error. It
has not been defined by the user.
Check spelling of the state name or define the
state.
DEBUG-LASTCHANCE
=Title VAX DEBUG Message
Ident: LASTCHANCE
Message Text:
Stack exception handlers lost, re-initializing
stack
Severity: Error
Explanation:
The user's program contained an error that caused
the exception handling mechanism to fail. This
error occurs when the stack is overwritten by the
user program or by deposit commands.
Identify and correct the error in the user program.
DEBUG-LINEINFO
=Title VAX DEBUG Message
Ident: LINEINFO
Message Text:
Line-description
Severity: Error
Explanation:
This is either 'No line information available', or
'No line <line_number, !UL>, previous line is
<line_number, !UL>, next line is <line_number,
!UL>'
DEBUG-LOGFILEIS
=Title VAX DEBUG Message
Ident: LOGFILEIS
Message Text:
The error log is in file file_specification
Severity: Informational
Explanation:
An internal debugger error has occurred, and
information which will be useful in locating the
error has been written to file_specification.
If the error is reproducible, submit a Software
Performance Report and, if possible, enclose both a
copy of the program being debugged and a logged
debugging session that reproduces the error.
DEBUG-LONGSTRING
=Title VAX DEBUG Message
Ident: LONGSTRING
Message Text:
Strings longer than 2**16 characters not supported
Severity: Warning
Explanation:
The length of a string or the range of one array
bound is greater than 2**16. The string or array
is too large for the Debugger.
Do not use strings of this length with the
Debugger.
DEBUG-LOOPINCR
=Title VAX DEBUG Message
Ident: LOOPINCR
Message Text:
Loop increment cannot be zero
Severity: Warning
Explanation:
The loop increment specified on the FOR command is
zero.
Change the loop increment to be a non-zero value.
DEBUG-LOOPVAR
=Title VAX DEBUG Message
Ident: LOOPVAR
Message Text:
Loop var loop_variable has been redefined; exiting
for loop
Severity: Informational
Explanation:
Since the loop variable has been redefined, the
debugger will exit the loop. No further comparison
is possible.
None.
DEBUG-LOWBNDOPT
=Title VAX DEBUG Message
Ident: LOWBNDOPT
Message Text:
Lower bound of subrange was optimized away
Severity: Informational
Explanation:
The lower bound of the subrange was optimized away.
The largest negative number on the machine is being
used as the lower bound.
You may wish to recompile the program without
optimizations.
DEBUG-MASKMISMATCH
=Title VAX DEBUG Message
Ident: MASKMISMATCH
Message Text:
Mask/target subscripts do not match, displaying
mask
Severity: Informational
Explanation:
The subscript values for the supplied mask value
are different then the subscript values for the
target value. To minimize confusion, Debug is
showing the mask values as well as the target
values.
None, this message is informational.
DEBUG-MASKNOTUSED
=Title VAX DEBUG Message
Ident: MASKNOTUSED
Message Text:
Mask operations not allowed on record and SCAN tree
objects
Severity: Informational
Explanation:
A mask operation (as specified by the /TMASK or
/FMASK qualifiers) cannot be performed on a record
or SCAN tree object.
Specify an array or address range to perform the
mask operation on.
DEBUG-MASKNOTVMR
=Title VAX DEBUG Message
Ident: MASKNOTVMR
Message Text:
Mask used is not %VMR, displaying specified mask
Severity: Informational
Explanation:
The supplied mask is not %VMR. To minimize
confusion, Debug is showing the mask values as well
as the target values.
None, this message is informational.
DEBUG-MASKPARNREQ
=Title VAX DEBUG Message
Ident: MASKPARNREQ
Message Text:
Parenthesis required in 'EXAMINE/xMASK=(x)'
Severity: Warning
Explanation:
Parentheses are required around the mask expression
specified with the /TMASK or /FMASK qualifiers on
the Examine command.
Include parantheses when specifying a mask
expression.
DEBUG-MATQUOMIS
=Title VAX DEBUG Message
Ident: MATQUOMIS
Message Text:
Matching quote is missing
Severity: Warning
Explanation:
The matching quote at the end of a quoted string is
missing.
Correct the error and re-enter the command.
DEBUG-MISCLOSUB
=Title VAX DEBUG Message
Ident: MISCLOSUB
Message Text:
Missing closing subscript parenthesis
Severity: Warning
Explanation:
This is a syntax error in a Debug command
Reinvoke the command with the proper syntax
DEBUG-MISINVNUM
=Title VAX DEBUG Message
Ident: MISINVNUM
Message Text:
Misplaced invocation number in path_name
Severity: Warning
Explanation:
The invocation number was not placed after the
innermost (rightmost) routine name in the specified
pathname.
Correct the pathname and re-enter the command.
DEBUG-MISINVOPER
=Title VAX DEBUG Message
Ident: MISINVOPER
Message Text:
Missing or invalid operator at 'operator_symbol'
Severity: Error
Explanation:
An operand was encountered in a language expression
when an operator was expected. For example,
'EVALUATE A B' instead of 'EVALUATE A + B'.
Specify valid operators between operands.
DEBUG-MISMODBEG
=Title VAX DEBUG Message
Ident: MISMODBEG
Message Text:
Missing Module-Begin record in DST (compiler error)
Severity: Informational
Explanation:
An expected Module-Begin record was not found in
the debugger Symbol Table. This indicates a
probable error in the compiler output.
Submit a Software Performance Report.
DEBUG-MISMODEND
=Title VAX DEBUG Message
Ident: MISMODEND
Message Text:
Missing Module-End in DST for path_name (compiler
error)
Severity: Informational
Explanation:
An expected Module-End record was not found in the
debugger Symbol Table. This indicates a probable
error in the compiler output.
Submit a Software Performance Report.
DEBUG-MISOPEMIS
=Title VAX DEBUG Message
Ident: MISOPEMIS
Message Text:
Misplaced operator or missing operand at
'operator_symbol'
Severity: Error
Explanation:
An operand was encountered in a language expression
when an operator was expected, or an operand did
not follow an operator. For example, 'EVALUATE A
B' or 'EVALUATE A + ' instead of 'EVALUATE A + B'.
Specify valid operators between operands.
DEBUG-MODUSCOPE
=Title VAX DEBUG Message
Ident: MODUSCOPE
Message Text:
A module name was expected; path_name not valid
Severity: Warning
Explanation:
This is a syntax error in a Debug command
Reinvoke the command with the proper syntax
DEBUG-MOVED_1
=Title VAX DEBUG Message
Ident: MOVED_1
Message Text:
This message is available for reuse
Severity: Informational
Explanation:
This message has been moved, and should not be
seen.
Please submit a Software Performance Report.
DEBUG-MOVED_2
=Title VAX DEBUG Message
Ident: MOVED_2
Message Text:
This message is available for reuse
Severity: Informational
Explanation:
This message has been moved, and should not be
seen.
Please submit a Software Performance Report.
DEBUG-MOVED_3
=Title VAX DEBUG Message
Ident: MOVED_3
Message Text:
This message is available for reuse
Severity: Informational
Explanation:
This message has been moved, and should not be
seen.
Please submit a Software Performance Report.
DEBUG-MOVED_4
=Title VAX DEBUG Message
Ident: MOVED_4
Message Text:
This message is available for reuse
Severity: Warning
Explanation:
This message has been moved, and should not be
seen.
Please submit a Software Performance Report.
DEBUG-MOVED_5
=Title VAX DEBUG Message
Ident: MOVED_5
Message Text:
This message is available for reuse
Severity: Fatal
Explanation:
This message has been moved, and should not be
seen.
Please submit a Software Performance Report.
DEBUG-MOVED_6
=Title VAX DEBUG Message
Ident: MOVED_6
Message Text:
This message is available for reuse
Severity: Fatal
Explanation:
This message has been moved, and should not be
seen.
Please submit a Software Performance Report.
DEBUG-MPARENREQ
=Title VAX DEBUG Message
Ident: MPARENREQ
Message Text:
Parenthesis required around process list in
debug_command
Severity: Warning
Explanation:
Parentheses must be placed around the process list
for debugger commands SET/PROCESS=(process-list) or
DO/PROCESS=(process-list).
Place parentheses around the process list in the
command.
DEBUG-MPCOMMAND
=Title VAX DEBUG Message
Ident: MPCOMMAND
Message Text:
Command is only valid when multiprocess support is
enabled
Severity: Error
Explanation:
The debugger was unable to execute the specified
command since it is only valid when the debugger's
multiprocess support is enabled.
Restart the debugging session with multiprocess
support enabled. Multiprocess support is enabled
by defining the logical name DBG$PROCESS as
follows: ($ DEFINE/JOB DBG$PROCESS MULTIPROCESS)
DEBUG-NAMSTRMIS
=Title VAX DEBUG Message
Ident: NAMSTRMIS
Message Text:
Name string missing or invalid in %NAME construct
Severity: Error
Explanation:
The %NAME construct requires either a quoted string
or a name to be supplied.
Specify a valid name after the %NAME construct.
DEBUG-NAMTOOLONG
=Title VAX DEBUG Message
Ident: NAMTOOLONG
Message Text:
Name is too long: 'symbol_name'
Severity: Error
Explanation:
Display and window names must be less than 80
characters in length.
Shorten the name to be less than 80 characters
long.
DEBUG-NEEDMORE
=Title VAX DEBUG Message
Ident: NEEDMORE
Message Text:
Unexpected end of command line
Severity: Warning
Explanation:
The command entered was not complete. A required
part of the command was omitted.
Re-enter the complete command.
DEBUG-NEEDPAREN
=Title VAX DEBUG Message
Ident: NEEDPAREN
Message Text:
Parenthesis required in THEN, ELSE, and DO clauses
Severity: Informational
Explanation:
Parenthesis are required in THEN, ELSE, and DO
clauses to group the containing debugger commands.
Correct the THEN, ELSE, or DO clause by including
parenthesis.
DEBUG-NOACCESSR
=Title VAX DEBUG Message
Ident: NOACCESSR
Message Text:
No read access to address address_value
Severity: Error
Explanation:
The address you specified cannot be read by the
debugger. Therefore the operation you requested
cannot be performed.
Verify that the address being read is correct. One
way to do this is to use EVALUATE to find the
address of the specified symbol, or to EXAMINE the
descriptor to see if it specifies a valid address.
DEBUG-NOACCESSW
=Title VAX DEBUG Message
Ident: NOACCESSW
Message Text:
No write access to address address_value
Severity: Error
Explanation:
A DEPOSIT, SET BREAK, or SET TRACE command
specified the address address_value. The debugger
does not have write access to that page. The
debugger requires write access in order to be able
to set up breakpoints and tracepoints.
None. You cannot do the requested operation
without proper access.
DEBUG-NOADDRREG
=Title VAX DEBUG Message
Ident: NOADDRREG
Message Text:
Register register_name does not have an address use
@register_name to obtain the contents of register
register_name
Severity: Warning
Explanation:
The user has requested the address of a register
but registers do not have addresses
Examine the register directly
DEBUG-NOALTERSP
=Title VAX DEBUG Message
Ident: NOALTERSP
Message Text:
Deposit into register 14 (stack pointer) not
allowed
Severity: Informational
Explanation:
You can not deposit into the stack pointer register
because the debugger is on the stack and it would
corrupt the debugger or program stack frames.
None.
DEBUG-NOATTACH
=Title VAX DEBUG Message
Ident: NOATTACH
Message Text:
Attach command failed
Severity: Error
Explanation:
The ATTACH command could be not performed because
of an error which was returned by the system
service called by the debugger. The error status
returned by the system service routine follows this
message.
Correct the problem based on the associated message
which follows the debugger error message.
DEBUG-NOBREAGGR
=Title VAX DEBUG Message
Ident: NOBREAGGR
Message Text:
Breakpoints or tracepoints on registers, records or
arrays are not allowed
Severity: Error
Explanation:
Only watchpoints are allowed on registers, records
or arrays.
Either change the address of the breakpoint or
tracepoint, or specify a watchpoint on the address.
DEBUG-NOBREAKAT
=Title VAX DEBUG Message
Ident: NOBREAKAT
Message Text:
Cannot set breakpoint or tracepoint at address
address_value
Severity: Warning
Explanation:
The user has requested that a breakpoint be set at
an address that is either non-writable, in Debug,
or invalid in some other way.
Correct the address and reissue the command
DEBUG-NOBREAKS
=Title VAX DEBUG Message
Ident: NOBREAKS
Message Text:
No breakpoints are set
Severity: Informational
Explanation:
The SHOW BREAK command was entered and no
breakpoints were set.
None.
DEBUG-NOCALLS
=Title VAX DEBUG Message
Ident: NOCALLS
Message Text:
No active call frames
Severity: Error
Explanation:
The call stack cannot be displayed because your
program has run to completion, and there are no
call frames on the stack.
None.
DEBUG-NOCANMAIN
=Title VAX DEBUG Message
Ident: NOCANMAIN
Message Text:
Cannot cancel main image
Severity: Warning
Explanation:
The user has requested that the main image symbols
be canceled. This is an invalid operation.
No action required - operation invalid.
DEBUG-NOCLI
=Title VAX DEBUG Message
Ident: NOCLI
Message Text:
No CLI present to perform function
Severity: Error
Explanation:
There is no command line interpreter in the target
process from which to perform the operation.
None. You cannot perform the attempted operation.
DEBUG-NOCONNECT
=Title VAX DEBUG Message
Ident: NOCONNECT
Message Text:
CONNECT command failed
Severity: Error
Explanation:
The debugger was unable to execute the connect
command. The reason is given in the message
following this message.
Correct the problem given by the messages following
this message. Most often, the problem is due to
specifying a process that does not exist, or
specifying a process that is not in the same VMS
job as the process being debugged. If the problem
cannot be solved, submit a Software Performance
Report.
DEBUG-NOCURLOC
=Title VAX DEBUG Message
Ident: NOCURLOC
Message Text:
Current location not defined
Warning '.' is not currently defined.
Do not reference '.' until an EXAMINE or
EVALUATE/ADDRESS command has been performed.
DEBUG-NODEFSCPE
=Title VAX DEBUG Message
Ident: NODEFSCPE
Message Text:
No default scope list: error performing !AC
Severity: Error
Explanation:
The specified command or built-in symbol requires
that the default scope list be established.
To establish the default scope list, perform a
CANCEL SCOPE command.
DEBUG-NODELIMTR
=Title VAX DEBUG Message
Ident: NODELIMTR
Message Text:
Missing or invalid instruction operand delimiter
Severity: Error
Explanation:
A DEPOSIT command specified an invalid instruction
operand format.
Re-enter the command with valid operands.
DEBUG-NODEPDEBUG
=Title VAX DEBUG Message
Ident: NODEPDEBUG
Message Text:
DEPOSIT into the debugger's address space is not
allowed
Severity: Warning
Explanation:
The user has tried to deposit into addresses
occupied by the Debugger. This is not allowed.
Correct the address and reissue the command.
DEBUG-NODIRLISM
=Title VAX DEBUG Message
Ident: NODIRLISM
Message Text:
No source directory list in effect for path_name
Severity: Warning
Explanation:
The debugger command CANCEL SOURCE/MODULE=path_name
failed because there is no source directory search
list in effect for module path_name.
This is an informational message. However, if the
wrong module was specified, the command should be
re-entered with the correct name.
DEBUG-NODIRLIST
=Title VAX DEBUG Message
Ident: NODIRLIST
Message Text:
No source directory list in effect
Severity: Warning
Explanation:
The debugger command CANCEL SOURCE had no effect
because no source directory search list is
currently in effect.
None. This message is informational.
DEBUG-NOELABBODY
=Title VAX DEBUG Message
Ident: NOELABBODY
Message Text:
Package body path_name has no executable code
Severity: Warning
DEBUG-NOELABSPEC
=Title VAX DEBUG Message
Ident: NOELABSPEC
Message Text:
Package spec path_name has no executable code
Severity: Warning
DEBUG-NOEND
=Title VAX DEBUG Message
Ident: NOEND
Message Text:
String beginning with 'string_value' is missing end
delimiter delimiter_character
Severity: Error
Explanation:
A DEPOSIT command specified an ASCII string or
INSTRUCTION string beginning with characters
string_value that do not have a terminating
apostrophe.
Re-enter the command with characters containing a
terminating apostrophe.
DEBUG-NOEPTSPEC
=Title VAX DEBUG Message
Ident: NOEPTSPEC
Message Text:
No eventpoints were specified with a SHOW or CANCEL
command.
Severity: Error
Explanation:
Eventpoints were not given with a SHOW or CANCEL
command.
Try the command again, specifying eventpoints to
operate on.
DEBUG-NOEVALEXPR
=Title VAX DEBUG Message
Ident: NOEVALEXPR
Message Text:
Unable to evaluate expression for following reason
Severity: Informational
Explanation:
The expression could not be evaluated. The
following message indicates why.
See the following message.
DEBUG-NOEVENTFAC
=Title VAX DEBUG Message
Ident: NOEVENTFAC
Message Text:
/EVENT qualifier not allowed: first type 'SET
EVENT facility' to specify an event facility
Severity: Error
Explanation:
No event facility has been set up yet, therefore no
events which use an event facility can be set,
canceled, or displayed.
Set an event facility, and try the operation again.
DEBUG-NOEXCBRE
=Title VAX DEBUG Message
Ident: NOEXCBRE
Message Text:
No exception breaks were set
Severity: Informational
Explanation:
A CANCEL BREAK/EXCEPTION command was entered when
exception breaks were not in effect. The CANCEL
BREAK/EXCEPTION command had no effect.
None. This message is informational.
DEBUG-NOEXHND
=Title VAX DEBUG Message
Ident: NOEXHND
Message Text:
No exit handlers are declared
Severity: Informational
Explanation:
There are no user-mode exit handlers currently
declared.
None. This message is informational.
DEBUG-NOFIELD
=Title VAX DEBUG Message
Ident: NOFIELD
Message Text:
'field_name' is not a field in this record
Severity: Warning
Explanation:
An attempt was made to reference a field that is
not defined in the record.
Check the field specified to ensure that it is
defined in the record.
DEBUG-NOFREE
=Title VAX DEBUG Message
Ident: NOFREE
Message Text:
No free storage available
Severity: Error
Explanation:
The debugger has used all memory available.
Memory must be made available before the debugger
can continue executing. SET modules could be
canceled, or the debugging session can be stopped
and system management can increase the virtual
memory on your system.
DEBUG-NOGLOBALS
=Title VAX DEBUG Message
Ident: NOGLOBALS
Message Text:
Some or all global symbols not accessible
Severity: Informational
Explanation:
The image was linked with the /NODEBUG qualifier,
and there are no global symbols in the symbol
table.
Relink the image with the /DEBUG qualifier.
DEBUG-NOHLPLIB
=Title VAX DEBUG Message
Ident: NOHLPLIB
Message Text:
The debugger could not open the help library file
Severity: Warning
Explanation:
The debugger could not open the help library file
because there was some low level file open error.
Check for user quotas being exceeded. For further
assistance and information on this problem check
with your system manager.
DEBUG-NOINPAVAIL
=Title VAX DEBUG Message
Ident: NOINPAVAIL
Message Text:
Input objects not available
Severity: Fatal
Explanation:
The debugger was unable to open either DBG$INPUT or
SYS$INPUT.
Check that logicals used to point at input files or
devices are properly defined.
DEBUG-NOINPFOC
=Title VAX DEBUG Message
Ident: NOINPFOC
Message Text:
Debugger must have input focus to accept paste
operation
Severity: Warning
Explanation:
A writeable debugger window and, if applicable, a
text-entry field in that window must have the input
focus before the selection can be pasted to it from
the clipboard.
Assign the input focus to a writeable window and,
if applicable, to the appropriate text-entry field.
DEBUG-NOINSTRAN
=Title VAX DEBUG Message
Ident: NOINSTRAN
Message Text:
Cannot translate opcode at location address_value
Severity: Error
Explanation:
The address specified in the EXAMINE command is not
the beginning of a valid instruction. This can be
caused by specifying an address that is in the
middle of an instruction or by an address that is
in a data area.
Specify an address that contains a valid
instruction.
DEBUG-NOKEYDEF
=Title VAX DEBUG Message
Ident: NOKEYDEF
Message Text:
Cannot do keypad input, mode is set to NOKEYPAD
Severity: Warning
Explanation:
The user is trying to define or set a keypad
definition which can not be performed due to the
current operating mode.
Use a terminal that supports keypad operations.
DEBUG-NOKEYPAD
=Title VAX DEBUG Message
Ident: NOKEYPAD
Message Text:
Unable to set up keypad definitions
Severity: Informational
Explanation:
An error status was returned from the Screen
Management Facility that indicates that the
debugger keypad definitions are corrupted.
Try to set keypad mode again (SET MODE KEYPAD). If
this fails to correct the problem submit a Software
Performance Report (SPR).
DEBUG-NOLASTVAL
=Title VAX DEBUG Message
Ident: NOLASTVAL
Message Text:
Last value is not defined
Warning '\' is not currently defined.
Do not reference '\' until a DEPOSIT or EVALUATE
command has been performed.
DEBUG-NOLINXXX
=Title VAX DEBUG Message
Ident: NOLINXXX
Message Text:
Line_descriptor
Severity: Warning
Explanation:
The line number range CZ:yyy specified on the
DEBUGGER command TYPE does not exist. There are no
such line numbers in the specified module (or the
default module).
Re-enter the command specifying line numbers that
do exist.
DEBUG-NOLIST
=Title VAX DEBUG Message
Ident: NOLIST
Message Text:
List of parameter values not allowed - check use of
comma (,)
Severity: Error
Explanation:
A command that only accepts a single input value
for a parameter contains multiple values separated
by commas (,).
Re-enter the command; specify one value. If
necessary, issue the command once for each value.
DEBUG-NOLOCALS
=Title VAX DEBUG Message
Ident: NOLOCALS
Message Text:
Image does not contain local symbols
Severity: Informational
Explanation:
All the modules in the image were compiled or
assembled without traceback information. There is
no local symbol information in the image.
Recompile or reassemble the modules using the
/DEBUG qualifier and then relink them.
DEBUG-NOMAIN
=Title VAX DEBUG Message
Ident: NOMAIN
Message Text:
The debugger detected an error when trying to fetch
the main window from the Digital Resource Manager
(DRM).
Severity: Fatal
Explanation:
The debugger detected an error when trying to fetch
debuggers main window from the Digital Resource
Manager (DRM). This prevents the debugger from
continuing this session.
Try the debugger again, if the same results exist
submit a Software Performance Report (SPR).
DEBUG-NOMARKCHNG
=Title VAX DEBUG Message
Ident: NOMARKCHNG
Message Text:
[NO]MARK_CHANGE qualifier not applicable to
display_name display
Severity: Informational
Explanation:
The /MARK_CHANGE and /NOMARK_CHANGE qualifiers can
not be applied to the indicated kind of display.
None.
DEBUG-NOMATCH
=Title VAX DEBUG Message
Ident: NOMATCH
Message Text:
No matches
Severity: Warning
Explanation:
A SEARCH command was being used and no matches were
found
No action required
DEBUG-NOMORE
=Title VAX DEBUG Message
Ident: NOMORE
Message Text:
Wildcard request complete
Severity: Warning
Explanation:
This is a debugger internal error code.
If the debugger reports this error please submit a
Software Performance Report.
DEBUG-NONEXPR
=Title VAX DEBUG Message
Ident: NONEXPR
Message Text:
Nonexistent process
Severity: Error
Explanation:
A process name or process identification specified
in a command is not valid.
Verify that the process name or identification is
correct and that the process was not already
deleted. Also verify that you have the required
privilege to access the process.
DEBUG-NONEXPRC
=Title VAX DEBUG Message
Ident: NONEXPRC
Message Text:
Process process-specification does not exist
Severity: Error
Explanation:
The process-specification was not valid or the
specified process did not exist.
Verify that the process specification is correct
and that the process still exists and then re-enter
the command.
DEBUG-NONUMSCOPE
=Title VAX DEBUG Message
Ident: NONUMSCOPE
Message Text:
Scope does not exist or is not in set module:
scope_number
Severity: Informational
Explanation:
The debugger could not find the scope indicated by
the numbered scope in the scope list.
Set the module that contains that scope.
DEBUG-NONXTLIN
=Title VAX DEBUG Message
Ident: NONXTLIN
Message Text:
Next line for source display not defined
Severity: Warning
Explanation:
The debugger command TYPE or SEARCH was entered
without specifying a line number (for example, the
next line after the last source line printed should
be used). But no next source line is currently
defined.
Re-enter the command explicitly specifying the
desired line number.
DEBUG-NOOCCLDISP
=Title VAX DEBUG Message
Ident: NOOCCLDISP
Message Text:
Display_name display may not be occluded
Severity: Informational
Explanation:
A display was positioned over the indicated display
that is not allowed to be occluded. The indicated
display was popped to the front.
You may wish to move the display so it is not
occluded by the display named in the message.
DEBUG-NOOUTAVAIL
=Title VAX DEBUG Message
Ident: NOOUTAVAIL
Message Text:
Output objects are not available
Severity: Fatal
Explanation:
The debugger was unable to open either DBG$OUTPUT
or SYS$OUTPUT.
Check that logicals used to point at output files
or devices are properly defined.
DEBUG-NOPACKMEMBODY
=Title VAX DEBUG Message
Ident: NOPACKMEMBODY
Message Text:
'symbol_name' is not a member of package body
path_name
Severity: Warning
DEBUG-NOPACKMEMSPEC
=Title VAX DEBUG Message
Ident: NOPACKMEMSPEC
Message Text:
'symbol_name' is not a member of package spec
path_name
Severity: Warning
DEBUG-NOPRED
=Title VAX DEBUG Message
Ident: NOPRED
Message Text:
Logical predecessor not defined
Severity: Warning
Explanation:
The logical predecessor of the identifier or
instruction referenced is not defined.
None. This message is informational.
DEBUG-NOPROMPT
=Title VAX DEBUG Message
Ident: NOPROMPT
Message Text:
Cannot delete, remove, unselect, or change kind of
the display_name display
Severity: Informational
Explanation:
This display can not be deleted, removed,
unselected, or have it's kind changed.
None.
DEBUG-NORECSYM
=Title VAX DEBUG Message
Ident: NORECSYM
Message Text:
Recursive symbol_type symbol definition encountered
at or near 'debugger_command_segment'
Severity: Error
Explanation:
While attempting to expand a defined symbol, a
recursive symbol definition was encountered.
Redefine the symbol specified in the error message
so that it does not contain any circular
dependencies and then re-enter the command.
DEBUG-NORMAL
=Title VAX DEBUG Message
Ident: NORMAL
Message Text:
Successful debugger status
Severity: Success
Explanation:
This is an internal status signal, it should never
be seen by the user. If this message does occur
please submit a Software Performance Report (SPR).
Submit a Software Performance Report (SPR).
DEBUG-NORSTBLD
=Title VAX DEBUG Message
Ident: NORSTBLD
Message Text:
Cannot build symbol table
Severity: Error
Explanation:
The debugger is unable to build a symbol table
because of errors in the format of the image file.
Relink the image and, if the error is reproducible,
submit a Software Performance Report explaining how
the image file was created.
DEBUG-NOSAVPROG
=Title VAX DEBUG Message
Ident: NOSAVPROG
Message Text:
Cannot save a program I/O display
Severity: Informational
Explanation:
The SAVE command is not allowed on a program I/O
display since the debugger does not know the
contents of the display.
None.
DEBUG-NOSCOPE
=Title VAX DEBUG Message
Ident: NOSCOPE
Message Text:
No scope exists to look up line line_number
Severity: Error
Explanation:
The specified line_number cannot be found because
there is no current scope to look it up in.
Specify the module explicitly and retry the
operation.
DEBUG-NOSCOPELIST
=Title VAX DEBUG Message
Ident: NOSCOPELIST
Message Text:
A list of scopes is not allowed with this command.
Severity: Error
Explanation:
You cannot enter a list of scopes with the
previously executed command.
Enter the command with only one scope item.
DEBUG-NOSCRDEV
=Title VAX DEBUG Message
Ident: NOSCRDEV
Message Text:
Screen mode is not supported on this device screen
mode output is being lost
Severity: Informational
Explanation:
The debugger output is being sent to a device that
the Screen Management Facility does can not write
to. While the debugger will continue to process
commands, the screen mode output will be lost.
Make sure the logical DBG$OUTPUT is pointed to a
device that the Screen Management Facility can
write to.
DEBUG-NOSCRMODE
=Title VAX DEBUG Message
Ident: NOSCRMODE
Message Text:
Screen mode is not supported on this terminal
screen mode is not set
Severity: Warning
Explanation:
Screen mode is not allowed on the terminal type
used by the current session.
Use another terminal if screen mode is desired
DEBUG-NOSCROLL
=Title VAX DEBUG Message
Ident: NOSCROLL
Message Text:
No scrolling display selected or missing display
name
Severity: Error
Explanation:
The user did not enter a display name with the
command, and the debugger attempted to use the
display with the SCROLL attribute. However, no
display currently has the SCROLL attribute.
Either reenter the command, specifying a display
name, or SELECT a display to have the SCROLL
attribute and reenter the command.
DEBUG-NOSCROLLDISP
=Title VAX DEBUG Message
Ident: NOSCROLLDISP
Message Text:
Display_name display may not be scrolled
Severity: Informational
Explanation:
This display can not be scrolled.
None.
DEBUG-NOSETTERM
=Title VAX DEBUG Message
Ident: NOSETTERM
Message Text:
The SET TERMINAL command is not supported on this
terminal
Severity: Warning
Explanation:
The SET TERMINAL command is not allowed on the
terminal being used for the current session
Use another type of terminal
DEBUG-NOSPAWN
=Title VAX DEBUG Message
Ident: NOSPAWN
Message Text:
Spawn command failed
Severity: Error
Explanation:
The debugger failed to perform a SPAWN command or
SPAWN an editor. The error status returned from
the SPAWN command is appended to this error
message.
If the SPAWN error is correctable, correct the
problem and reenter the command. If not, the SPAWN
command is unavailable.
DEBUG-NOSRCHSTR
=Title VAX DEBUG Message
Ident: NOSRCHSTR
Message Text:
Search string not set
Severity: Warning
Explanation:
No current search string is defined for the
debugger command SEARCH. The SEARCH command was
entered without a search string indicating that the
current search string should be used. But no
previous SEARCH command has been entered to define
a current search string.
Explicitly specify the desired search string on the
command.
DEBUG-NOSRCLIN
=Title VAX DEBUG Message
Ident: NOSRCLIN
Message Text:
No source line for address address_value
Severity: Warning
Explanation:
No source line corresponds to the address
address_value specified on the debugger command
EXAMINE/SOURCE.
None. This message is informational.
DEBUG-NOSTEPGO
=Title VAX DEBUG Message
Ident: NOSTEPGO
Message Text:
No STEP, GO, SET PROCESS/VISIBLE or CALL commands
allowed in screen displays
Severity: Error
Explanation:
A STEP, GO, SET PROCESS/VISIBLE or CALL command was
used in a screen display command list. The
debugger does not allow the use of such commands in
display command lists.
Re-specify the screen display command list without
using any of the disallowed commands.
DEBUG-NOSUCC
=Title VAX DEBUG Message
Ident: NOSUCC
Message Text:
Logical successor not defined
Severity: Warning
Explanation:
The logical successor of the referenced instruction
or identifier is not defined.
None. This message is informational.
DEBUG-NOSUCHBPT
=Title VAX DEBUG Message
Ident: NOSUCHBPT
Message Text:
No such breakpoint
Severity: Informational
Explanation:
The CANCEL BREAK command specified an address that
is not the address of a breakpoint.
Use the SHOW BREAK command to find the location of
the current breakpoints, and then cancel any of
these breakpoints that you want to cancel.
DEBUG-NOSUCHDISP
=Title VAX DEBUG Message
Ident: NOSUCHDISP
Message Text:
No such display defined: display_name
Severity: Error
Explanation:
The specified display <display_name, !AC> does not
exist.
Re-enter the command, specifying an existing
display.
DEBUG-NOSUCHELP
=Title VAX DEBUG Message
Ident: NOSUCHELP
Message Text:
No such help topic or invalid HELP command
Severity: Warning
Explanation:
The user has requested help for a topic for which
there is no help or the syntax used to request the
help was invalid
Try another topic or just type HELP for a topic
list
DEBUG-NOSUCHIMG
=Title VAX DEBUG Message
Ident: NOSUCHIMG
Message Text:
Image image_name not found
Severity: Error
Explanation:
The specified image <image_name, !AC> does not
exist.
Re-enter the command, specifying an existing image.
DEBUG-NOSUCHMODU
=Title VAX DEBUG Message
Ident: NOSUCHMODU
Message Text:
Module path_name is not in module chain
Severity: Error
Explanation:
The module path_name, specified in the SET MODULE
command, does not exist in the image. This message
can be caused when: (1) a module name has been
entered incorrectly or (2) a module is compiled
with the /NOTRACE switch.
Specify a module that is in the image.
DEBUG-NOSUCHPACK
=Title VAX DEBUG Message
Ident: NOSUCHPACK
Message Text:
Library package path_name is not in the symbol
table
Severity: Warning
DEBUG-NOSUCHSCOPE
=Title VAX DEBUG Message
Ident: NOSUCHSCOPE
Message Text:
Scope does not exist or is not in set module:
scope_name
Severity: Warning
Explanation:
The user has requested that the current scope be
set to a scope that is invalid for the current
module
Correct the scope specification and reissue the
command
DEBUG-NOSUCHTASK
=Title VAX DEBUG Message
Ident: NOSUCHTASK
Message Text:
No such task exists or no task satisfies criteria
Severity: Error
Explanation:
The user entered a task expression that does not
correspond to an existing task, or no existing task
satisfies the task expression.
Reenter the command with a task expression that
specifies an existing task.
DEBUG-NOSUCHTPT
=Title VAX DEBUG Message
Ident: NOSUCHTPT
Message Text:
No such tracepoint
Severity: Informational
Explanation:
The CANCEL TRACE command specified an address that
was not the address of a tracepoint.
Use the SHOW TRACE command to display the current
tracepoints and then cancel any that you want to
cancel.
DEBUG-NOSUCHWIND
=Title VAX DEBUG Message
Ident: NOSUCHWIND
Message Text:
No such window defined: display_name
Severity: Error
Explanation:
The specified, or defaulted window <window_name,
!AC> does not exist.
Reenter the command, specifying an existing window
name.
DEBUG-NOSUCHWPT
=Title VAX DEBUG Message
Ident: NOSUCHWPT
Message Text:
No such watchpoint
Severity: Informational
Explanation:
The CANCEL WATCH command specified an address that
was not the address of a watchpoint.
Use the SHOW WATCH command to display the current
watchpoints and then cancel any that you want to
cancel.
DEBUG-NOSYMBOL
=Title VAX DEBUG Message
Ident: NOSYMBOL
Message Text:
Symbol 'symbol_name' is not in the symbol table
Severity: Error
Explanation:
The debugger could not find the symbol
'<symbol_name, !AC>' in its symbol table.
The symbol may have been entered incorrectly, in
which case the fix is to enter the symbol
correctly. The other possibility is that the
module the symbol is defined in has not been loaded
into the debugger's symbol table; perform a SET
MODULE of the appropriate module.
DEBUG-NOSYMBOLR
=Title VAX DEBUG Message
Ident: NOSYMBOLR
Message Text:
No symbol 'symbol_name' was declared in routine
path_name
Severity: Warning
DEBUG-NOTADAPROG
=Title VAX DEBUG Message
Ident: NOTADAPROG
Message Text:
Program is not an ADA program; command ignored
Severity: Error
Explanation:
The entered command applies only to Ada programs ;
since this is not an Ada program, the command
cannot be executed.
No user action required.
DEBUG-NOTARRAY
=Title VAX DEBUG Message
Ident: NOTARRAY
Message Text:
Type of variable is not array
Severity: Warning
Explanation:
The variable being treated as an array has not been
defined as one.
Check that the correct variable reference is being
made.
DEBUG-NOTASTRUCT
=Title VAX DEBUG Message
Ident: NOTASTRUCT
Message Text:
'symbol_name' was not declared as a structure
Severity: Error
Explanation:
A VAX BLISS-32 structure reference specified a
symbol symbol_name that was not declared a
structure.
Re-enter the command with a valid symbol reference.
DEBUG-NOTATMAIN
=Title VAX DEBUG Message
Ident: NOTATMAIN
Message Text:
Type GO to get to start of main program
Severity: Informational
Explanation:
The debugger has started at the beginning of
LIB$INITIALIZE code.
If you want to get to the actual start of the main
program you should type GO at the debug prompt.
The debugger will allow the program to execute the
LIB$INITIALIZE code and then break at the start of
the main program. If you'd like to debug the
LIB$INITIALIZE code you are positioned to do so at
this point.
DEBUG-NOTCURPC
=Title VAX DEBUG Message
Ident: NOTCURPC
Message Text:
Target of EXAMINE/OPERANDS is not the current PC
results may be unexpected
Severity: Informational
Explanation:
The operands being examined will probably give
incorrect results, because the context for the
instruction is probably not set up properly.
Specifically, the values of registers used in
address computations depend on the previous series
of instructions being executed, which was not done
in this case.
Only use EXAMINE/OPERANDS with .0\%PC
DEBUG-NOTDECTHREADS
=Title VAX DEBUG Message
Ident: NOTDECTHREADS
Message Text:
Program does not use DECthreads services.
Severity: Error
Explanation:
The entered command applies only to programs using
DECthreads services.
No user action required.
DEBUG-NOTDEFINE
=Title VAX DEBUG Message
Ident: NOTDEFINE
Message Text:
Defined_symbol was not defined
Severity: Informational
Explanation:
The symbol was not found in the defined symbol
table.
Check your spelling or use SHOW DEFINE to see what
symbols have been defined.
DEBUG-NOTIMPLAN
=Title VAX DEBUG Message
Ident: NOTIMPLAN
Message Text:
Expression_type is not implemented at command level
Severity: Error
Explanation:
The expression_type is not supported at this type.
Specify a type of expression that the debugger
supports.
DEBUG-NOTINLOOP
=Title VAX DEBUG Message
Ident: NOTINLOOP
Message Text:
Exitloop encountered when not in a loop
Severity: Warning
Explanation:
An incorrect nesting of loops exist in the command
stream currently being executed.
Correct the command stream
DEBUG-NOTINSCOPE
=Title VAX DEBUG Message
Ident: NOTINSCOPE
Message Text:
Specified scope cannot be found in the default
scope list
Severity: Error
Explanation:
The specified scope was not in the current default
scope list.
Enter the command with a scope that is in the
default scope list.
DEBUG-NOTINST
=Title VAX DEBUG Message
Ident: NOTINST
Message Text:
Examined address is not the start of an instruction
Severity: Informational
Explanation:
The examined address does not denote the start of
an instruction.
Specify an address that does denote the start of an
instruction.
DEBUG-NOTNUMSCOPE
=Title VAX DEBUG Message
Ident: NOTNUMSCOPE
Message Text:
Specified scope is not a numbered scope.
Severity: Error
Explanation:
The SET SCOPE/CURRENT command requires a numbered
scope.
Enter the command with a numbered scope.
DEBUG-NOTORIGSRC
=Title VAX DEBUG Message
Ident: NOTORIGSRC
Message Text:
Original version of source file not found file used
is file_specification
Severity: Informational
Explanation:
A source file was found for some module. But the
revision date and time or the file size indicates
that this may not be the same version of the file
that was used in the original compilation of the
module. This warning message indicates that future
source line displays from this source file may not
correspond to the actual source used to compile the
module.
None, unless the original source is available.
Then you can use the debugger command SET SOURCE to
indicate the location of the source to the
debugger.
DEBUG-NOTPTR
=Title VAX DEBUG Message
Ident: NOTPTR
Message Text:
Variable must be of pointer or file type
Severity: Warning
Explanation:
The variable should be a pointer or a file type.
Specify a variable of pointer or file type.
DEBUG-NOTRACES
=Title VAX DEBUG Message
Ident: NOTRACES
Message Text:
No tracepoints are set, no opcode tracing
Severity: Informational
Explanation:
There are no tracepoints or opcode tracing set.
None. This message is informational.
DEBUG-NOTRAZERO
=Title VAX DEBUG Message
Ident: NOTRAZERO
Message Text:
Unable to find a trailing zero for ASCIZ object at
address address_value
Severity: Error
Explanation:
The debugger was unable to find a trailing zero for
the specified ASCIZ string.
The ASCIZ string is missing a trailing zero, or the
object examined is not an ASCIZ string.
DEBUG-NOTRECORD
=Title VAX DEBUG Message
Ident: NOTRECORD
Message Text:
Variable is not record; cannot select component
component_name
Severity: Warning
Explanation:
The user has requested a record operation on a
variable which is not a record.
Correct the command and reissue it
DEBUG-NOTREE
=Title VAX DEBUG Message
Ident: NOTREE
Message Text:
SCAN tree or subtree not found SCAN error message
Severity: Warning
DEBUG-NOTRUNDW
=Title VAX DEBUG Message
Ident: NOTRUNDW
Message Text:
The debugger is uncertain about the DECWindow
configuration.
Severity: Fatal
Explanation:
The debugger is uncertain about the systems
DECWindow configuration
Try the debugger again, if the same results exist
submit a Software Performance Report (SPR).
DEBUG-NOTTASKVAL
=Title VAX DEBUG Message
Ident: NOTTASKVAL
Message Text:
Expression does not specify an Ada task value
Severity: Informational
Explanation:
The expression entered does not specify an Ada task
value. Only Ada task values are known as such in
the symbol table - CMA thread values are considered
to be pointers.
Unless you are debugging CMA threads, reenter the
command, correctly specifying a task value.
DEBUG-NOTUISOSC
=Title VAX DEBUG Message
Ident: NOTUISOSC
Message Text:
The debugger will be unable to create a separate
window; OSC not enabled.
Severity: Informational
Explanation:
The debugger requires OSC support enabled to create
a separate window (see SET MODE SEPARATE).
To allow the debugger to create a separate window,
type at DCL: DEFINE/SYSTEM
UIS$VT_ENABLE_OSC_STRINGS TRUE. You may wish to
put this line in your private startup file.
DEBUG-NOTUISV30
=Title VAX DEBUG Message
Ident: NOTUISV30
Message Text:
The debugger will be unable to create a separate
window; UIS too old.
Severity: Informational
Explanation:
The debugger requires VWS V3.0 or later to create a
separate window (see SET MODE SEPERATE).
To allow the debugger to create a separate window,
install VWS V3.0 or later, and in your private
startup file (or at DCL), DEFINE/SYSTEM
UIS$VT_ENABLE_OSC_STRINGS TRUE.
DEBUG-NOTUNQOVR
=Title VAX DEBUG Message
Ident: NOTUNQOVR
Message Text:
Symbol 'symbol_name' is overloaded use SHOW SYMBOL
to find the unique symbol names
Severity: Error
Explanation:
More than one instance of the specified symbol
'<symbol_name, !AC>' exists in the user program.
Without further information, the debugger cannot
determine which symbol to use.
Re-enter the command, uniquely specifying the
symbol to be used. The SHOW SYMBOL command can be
used to find the unique symbol names.
DEBUG-NOTUPDATE
=Title VAX DEBUG Message
Ident: NOTUPDATE
Message Text:
Instruction screen display not updated
Severity: Informational
Explanation:
The instruction screen display was not updated
because of the preceding error message.
See the preceding error message.
DEBUG-NOTYPEINFO
=Title VAX DEBUG Message
Ident: NOTYPEINFO
Message Text:
Symbol type information not available please SET
the module that describes this type
Severity: Warning
Explanation:
The user has requested information about a symbol
which cannot be provided in the current context.
SET the module containing the information and
reissue the command
DEBUG-NOUNIQUE
=Title VAX DEBUG Message
Ident: NOUNIQUE
Message Text:
Symbol 'symbol_name' is not unique
Severity: Error
Explanation:
The symbol specified was not in a default scope or
was defined in more than one scope.
Specify the scope of the symbol in a pathname or
change the default scope.
DEBUG-NOUNIVERSALS
=Title VAX DEBUG Message
Ident: NOUNIVERSALS
Message Text:
Shareable image contains no universal symbols
Severity: Informational
Explanation:
No universal symbols were found in the image.
None.
DEBUG-NOUSREVNT
=Title VAX DEBUG Message
Ident: NOUSREVNT
Message Text:
No user-specified events are allowed; none are
declared
Severity: Error
Explanation:
A reference was made to an event, when no such
event had been defined (language not SCAN).
Reenter the last command, without specifying any
events.
DEBUG-NOVALATPC
=Title VAX DEBUG Message
Ident: NOVALATPC
Message Text:
Entity 'symbol_name' does not have a value at the
current PC (was optimized away)
Severity: Warning
Explanation:
The value of the specified variable does not exist
at this point in the program's execution. For
example, the variable might be assigned to a
register that is currently being used for some
other purpose.
Retry the operation at a point in the program's
execution when the variable is being referenced.
DEBUG-NOVALTYP
=Title VAX DEBUG Message
Ident: NOVALTYP
Message Text:
'symbol_name' does not have a value because it is a
type name
Severity: Warning
DEBUG-NOVALUE
=Title VAX DEBUG Message
Ident: NOVALUE
Message Text:
Reference does not have a value
Severity: Warning
Explanation:
The command specified a reference that has no
value.
Change the reference.
DEBUG-NOVECT
=Title VAX DEBUG Message
Ident: NOVECT
Message Text:
No vector support - command cannot be performed
Severity: Error
Explanation:
An attempt was made to modify vector state on a
system which has neither hardware vector
capabilities nor the VVIEF. This includes the
EXAMINE vector-register, DEPOSIT vector-register,
and SET VECTOR_MODE commands.
Do not attempt to modify vector state on a system
which does not have vector capabilities.
DEBUG-NOWATCHES
=Title VAX DEBUG Message
Ident: NOWATCHES
Message Text:
No watchpoints are set
Severity: Informational
Explanation:
No watchpoints are set.
None. This message is informational.
DEBUG-NOWATONOPT
=Title VAX DEBUG Message
Ident: NOWATONOPT
Message Text:
You cannot watch that entity, because it was not
allocated in m
Severity: Warning
Explanation:
A watchpoint cannot be set on that entity due to
optimizations performed by the compiler
Recompile the program with no optimizations in
effect
DEBUG-NOWATTAR
=Title VAX DEBUG Message
Ident: NOWATTAR
Message Text:
Cannot watch-protect target
Severity: Error
Explanation:
You are attempting to set a /STATIC watchpoint on a
location that is either a register, is not in your
program, or is on the stack (P1 space). These
kinds of locations cannot be watchpointed with the
/STATIC qualifier.
Either use the /NOSTATIC qualifier, or do not
watch-point this location.
DEBUG-NOWATVARIA
=Title VAX DEBUG Message
Ident: NOWATVARIA
Message Text:
Cannot set watchpoints on variant records
Severity: Warning
Explanation:
The user has requested that a watchpoint be set on
a variant record. This operation is not currently
supported
No user action required
DEBUG-NOWATVARSTG
=Title VAX DEBUG Message
Ident: NOWATVARSTG
Message Text:
Watchpoints not allowed after SET TYPE ASCIC,
ASCIW, or ASCIZ
Severity: Warning
DEBUG-NOWBPT
=Title VAX DEBUG Message
Ident: NOWBPT
Message Text:
Cannot insert breakpoint
Severity: Informational
Explanation:
This message indicates an internal debugger error.
Submit a Software Performance Report.
DEBUG-NOWILD
=Title VAX DEBUG Message
Ident: NOWILD
Message Text:
No wildcard permitted
Severity: Error
Explanation:
Wildcards are not permitted in this context
Re-enter the command without using wildcards
DEBUG-NOWILDFIL
=Title VAX DEBUG Message
Ident: NOWILDFIL
Message Text:
File name, type, and version cannot be wildcarded
Severity: Error
Explanation:
The components of a file specification entered in a
SET SOURCE command may not be wildcarded.
Reenter the command without wildcarding any file
specification components.
DEBUG-NOWOPCO
=Title VAX DEBUG Message
Ident: NOWOPCO
Message Text:
Cannot replace breakpoint with opcode
Severity: Fatal
Explanation:
This message indicates an internal debugger error.
Submit a Software Performance Report.
DEBUG-NOWPROT
=Title VAX DEBUG Message
Ident: NOWPROT
Message Text:
Cannot set protection
Severity: Fatal
Explanation:
This message indicates an internal debugger error.
Submit a Software Performance Report.
DEBUG-NO_SYNC_FROM_EXC_BRE
=Title VAX DEBUG Message
Ident: NO_SYNC_FROM_EXC_BRE
Message Text:
Synchronize can not be done from an exception
break.
Severity: Error
Explanation:
A synchronize command can not be done from an
exception break.
Do not perform a synchronization command when at an
exception break.
DEBUG-NPROMPT
=Title VAX DEBUG Message
Ident: NPROMPT
Message Text:
The debugger could not properly setup the state to
accept input.
Severity: Fatal
Explanation:
The debugger it could not properly setup the state
to accept input. This prevents the debugger from
continuing this session.
Try the debugger again, if the same results exist
submit a Software Performance Report (SPR).
DEBUG-NULLPTR
=Title VAX DEBUG Message
Ident: NULLPTR
Message Text:
Cannot dereference null pointer
Severity: Warning
DEBUG-NUMCONLONG
=Title VAX DEBUG Message
Ident: NUMCONLONG
Message Text:
Numeric constant too long, please shorten
Severity: Error
Explanation:
A number entered in the command line is too long.
Reenter the command, shortening the long number.
DEBUG-NUMTRUNC
=Title VAX DEBUG Message
Ident: NUMTRUNC
Message Text:
Number truncated
Severity: Informational
Explanation:
The number entered is greater than the largest
signed longword integer. The value has been
truncated to the the largest signed integer.
None.
DEBUG-OBJECTINV
=Title VAX DEBUG Message
Ident: OBJECTINV
Message Text:
Requested object is invalid
Severity: Fatal
Explanation:
This message indicates an internal debugger error.
Submit an SPR.
DEBUG-OBJPTRINV
=Title VAX DEBUG Message
Ident: OBJPTRINV
Message Text:
The pointer associated with the requested object is
invalid
Severity: Fatal
Explanation:
This message indicates an internal debugger error.
Submit an SPR.
DEBUG-OBJTYPMIS
=Title VAX DEBUG Message
Ident: OBJTYPMIS
Message Text:
The type associated with the requested object is
incorrect
Severity: Fatal
Explanation:
This message indicates an internal debugger error.
Submit an SPR.
DEBUG-OBSOLETE_1
=Title VAX DEBUG Message
Ident: OBSOLETE_1
Message Text:
This message is available for reuse
Severity: Warning
Explanation:
This message is obsolete, and should never be seen.
Please submit a Software Performance Report.
DEBUG-OBSOLETE_10
=Title VAX DEBUG Message
Ident: OBSOLETE_10
Message Text:
This message is available for reuse
Severity: Informational
Explanation:
This message is obsolete, and should never be seen.
Please submit a Software Performance Report.
DEBUG-OBSOLETE_11
=Title VAX DEBUG Message
Ident: OBSOLETE_11
Message Text:
This message is available for reuse
Severity: Informational
Explanation:
This message is obsolete, and should never be seen.
Please submit a Software Performance Report.
DEBUG-OBSOLETE_12
=Title VAX DEBUG Message
Ident: OBSOLETE_12
Message Text:
This message is available for reuse
Severity: Informational
Explanation:
This message is obsolete, and should never be seen.
Please submit a Software Performance Report.
DEBUG-OBSOLETE_13
=Title VAX DEBUG Message
Ident: OBSOLETE_13
Message Text:
This message is available for reuse
Severity: Informational
Explanation:
This message is obsolete, and should never be seen.
Please submit a Software Performance Report.
DEBUG-OBSOLETE_14
=Title VAX DEBUG Message
Ident: OBSOLETE_14
Message Text:
This message is available for reuse
Severity: Informational
Explanation:
This message is obsolete, and should never be seen.
Please submit a Software Performance Report.
DEBUG-OBSOLETE_15
=Title VAX DEBUG Message
Ident: OBSOLETE_15
Message Text:
This message is available for reuse
Severity: Informational
Explanation:
This message is obsolete, and should never be seen.
Please submit a Software Performance Report.
DEBUG-OBSOLETE_16
=Title VAX DEBUG Message
Ident: OBSOLETE_16
Message Text:
This message is available for reuse
Severity: Informational
Explanation:
This message is obsolete, and should never be seen.
Please submit a Software Performance Report.
DEBUG-OBSOLETE_17
=Title VAX DEBUG Message
Ident: OBSOLETE_17
Message Text:
This message is available for reuse
Severity: Informational
Explanation:
This message is obsolete, and should never be seen.
Please submit a Software Performance Report.
DEBUG-OBSOLETE_18
=Title VAX DEBUG Message
Ident: OBSOLETE_18
Message Text:
This message is available for reuse
Severity: Informational
Explanation:
This message is obsolete, and should never be seen.
Please submit a Software Performance Report.
DEBUG-OBSOLETE_19
=Title VAX DEBUG Message
Ident: OBSOLETE_19
Message Text:
This message is available for reuse
Severity: Informational
Explanation:
This message is obsolete, and should never be seen.
Please submit a Software Performance Report.
DEBUG-OBSOLETE_20
=Title VAX DEBUG Message
Ident: OBSOLETE_20
Message Text:
This message is available for reuse
Severity: Informational
Explanation:
This message is obsolete, and should never be seen.
Please submit a Software Performance Report.
DEBUG-OBSOLETE_21
=Title VAX DEBUG Message
Ident: OBSOLETE_21
Message Text:
This message is available for reuse
Severity: Informational
Explanation:
This message is obsolete, and should never be seen.
Please submit a Software Performance Report.
DEBUG-OBSOLETE_22
=Title VAX DEBUG Message
Ident: OBSOLETE_22
Message Text:
This message is available for reuse
Severity: Informational
Explanation:
This message is obsolete, and should never be seen.
Please submit a Software Performance Report.
DEBUG-OBSOLETE_23
=Title VAX DEBUG Message
Ident: OBSOLETE_23
Message Text:
This message is available for reuse
Severity: Informational
Explanation:
This message is obsolete, and should never be seen.
Please submit a Software Performance Report.
DEBUG-OBSOLETE_24
=Title VAX DEBUG Message
Ident: OBSOLETE_24
Message Text:
This message is available for reuse
Severity: Informational
Explanation:
This message is obsolete, and should never be seen.
Please submit a Software Performance Report.
DEBUG-OBSOLETE_25
=Title VAX DEBUG Message
Ident: OBSOLETE_25
Message Text:
This message is available for reuse
Severity: Informational
Explanation:
This message is obsolete, and should never be seen.
Please submit a Software Performance Report.
DEBUG-OBSOLETE_28
=Title VAX DEBUG Message
Ident: OBSOLETE_28
Message Text:
This message is available for reuse
Severity: Warning
Explanation:
This message is obsolete, and should never be seen.
Please submit a Software Performance Report.
DEBUG-OBSOLETE_29
=Title VAX DEBUG Message
Ident: OBSOLETE_29
Message Text:
This message is available for reuse
Severity: Warning
Explanation:
This message is obsolete, and should never be seen.
Please submit a Software Performance Report.
DEBUG-OBSOLETE_30
=Title VAX DEBUG Message
Ident: OBSOLETE_30
Message Text:
Expression does not specify a task value
Severity: Error
Explanation:
The expression entered does not specify a task
value. The command entered requires a task value.
Reenter the command, correctly specifying a task
value.
DEBUG-OBSOLETE_7
=Title VAX DEBUG Message
Ident: OBSOLETE_7
Message Text:
This message is available for reuse
Severity: Informational
Explanation:
This message is obsolete, and should never be seen.
Please submit a Software Performance Report.
DEBUG-OBSOLETE_8
=Title VAX DEBUG Message
Ident: OBSOLETE_8
Message Text:
This message is available for reuse
Severity: Informational
Explanation:
This message is obsolete, and should never be seen.
Please submit a Software Performance Report.
DEBUG-OBSOLETE_9
=Title VAX DEBUG Message
Ident: OBSOLETE_9
Message Text:
This message is available for reuse
Severity: Informational
Explanation:
This message is obsolete, and should never be seen.
Please submit a Software Performance Report.
DEBUG-OPCDEC
=Title VAX DEBUG Message
Ident: OPCDEC
Message Text:
No support for G/H instructions at or near
opcode_name
Severity: Warning
DEBUG-OPNOTALLOW
=Title VAX DEBUG Message
Ident: OPNOTALLOW
Message Text:
Operator 'operator_symbol' not allowed on given
data types
Severity: Error
Explanation:
The debugger encountered a problem when performing
the operation '<operator_symbol, !AC>' on the
specified operands. This may be a data type
conversion error.
Reenter the command, specifying compatible
operands.
DEBUG-OPSYNTAX
=Title VAX DEBUG Message
Ident: OPSYNTAX
Message Text:
Instruction operand syntax error for operand number
operand_number
Severity: Error
Explanation:
The debugger encountered an error in one of the
operands of a VAX instruction.
If the instruction was entered by the user, reenter
the instruction, correcting the operand error. If
not, then there may be an error in the user program
instructions.
DEBUG-OUTPUTLOST
=Title VAX DEBUG Message
Ident: OUTPUTLOST
Message Text:
Output being lost, both NOTERMINAL and NOLOG are in
effect
Severity: Informational
Explanation:
The SET OUTPUT command has set the output
conditions to NOTERMINAL and NOLOG; consequently,
the output is not displayed on the terminal or
written to a log file. The output normally
displayed by the debugger will not be available.
Use the SET OUTPUT command to send output to the
terminal or to a log file.
DEBUG-PACSIZREQ
=Title VAX DEBUG Message
Ident: PACSIZREQ
Message Text:
Packed size required
Severity: Warning
Explanation:
A size parameter is required
Supply a size parameter and reissue the command
DEBUG-PARENREQ
=Title VAX DEBUG Message
Ident: PARENREQ
Message Text:
Parenthesis required in 'debugger_command_segment
/TYPE=(X)'
Severity: Warning
Explanation:
The debugger_command_segment is either SET TYPE,
DEPOSIT, or EXAMINE.
Place parentheses around the type of expression
specified
DEBUG-PARSTKOVR
=Title VAX DEBUG Message
Ident: PARSTKOVR
Message Text:
Parse stack overflow, simplify expression
Severity: Warning
Explanation:
The expression was too complex for the debugger to
evaluate.
Simplify the expression.
DEBUG-PASTHRU
=Title VAX DEBUG Message
Ident: PASTHRU
Message Text:
The primary handler should ignore this signal
Severity: Success
Explanation:
This is an internal status signal, it should never
be seen by the user. If this message does occur
please submit a Software Performance Report (SPR).
Submit a Software Performance Report (SPR).
DEBUG-PATHNOTACP
=Title VAX DEBUG Message
Ident: PATHNOTACP
Message Text:
Pathname qualifiers (path_name) not allowed in SHOW
SYMBOL data name
Severity: Warning
Explanation:
The user has issued a command with invalid syntax
No user action required
DEBUG-PATHTLONG
=Title VAX DEBUG Message
Ident: PATHTLONG
Message Text:
Too many qualifiers on name
Severity: Error
Explanation:
There are too many pathname elements in the entered
pathname for the debugger to handle.
Shorten the pathname entered, either by
abbreviating the pathname, defining a symbol for
the pathname, or setting a search scope so that you
can use a shorter pathname.
DEBUG-PATHTOOLONG
=Title VAX DEBUG Message
Ident: PATHTOOLONG
Message Text:
Pathname too long at path_name
Severity: Error
Explanation:
The entered pathname is too long for the debugger
to handle.
Shorten the pathname entered, either by
abbreviating the pathname, defining a symbol for
the pathname, or setting a search scope so that you
can use a shorter pathname.
DEBUG-PCNOTALL
=Title VAX DEBUG Message
Ident: PCNOTALL
Message Text:
PC not allowed in context for operand number
operand_number
Severity: Error
Explanation:
Using the PC as an operand in the entered
instruction is not allowed.
If the instruction was entered by the user, reenter
the instruction, without using the PC in the
operand. If not, then there may be an error in the
user program instructions.
DEBUG-PLICVTERR
=Title VAX DEBUG Message
Ident: PLICVTERR
Message Text:
PLI conversion error at or near opcode_name
Severity: Error
Explanation:
An error occurred in the PL/I RTL performing a data
type conversion, for the object <opcode_name, !AC>.
Reenter the command, specifying a legitimate object
for the operation desired.
DEBUG-PREDEPTNOT
=Title VAX DEBUG Message
Ident: PREDEPTNOT
Message Text:
Predefined eventpoint(s) not canceled
Severity: Informational
Explanation:
Any existing predefined eventpoints have not been
canceled as the result of a CANCEL command.
Specify the /PREDEFINED qualifier with the CANCEL
command to cancel predefined eventpoints.
DEBUG-PROFRANOT
=Title VAX DEBUG Message
Ident: PROFRANOT
Message Text:
Proper frame not found on call stack for path_name
Severity: Warning
Explanation:
You attempted to look at a variable in a routine
invocation that does not exist.
Specify a routine or routine invocation that is
currently active.
DEBUG-PROMPTCLEN
=Title VAX DEBUG Message
Ident: PROMPTCLEN
Message Text:
Display_name display width not changed, must be
full width of screen
Severity: Informational
Explanation:
This display's width can not be changed. It must
be the full width of the screen.
None.
DEBUG-PROMPTOCCL
=Title VAX DEBUG Message
Ident: PROMPTOCCL
Message Text:
Display_name display now occludes some or all of
display_name display's text
Severity: Informational
Explanation:
This display now occludes some or all of the
specified display.
None.
DEBUG-PROMPTRLEN
=Title VAX DEBUG Message
Ident: PROMPTRLEN
Message Text:
Display_name display length not changed, must be at
least 2 lines long
Severity: Informational
Explanation:
This display's length can not be changed to less
than the minimum value specified.
None.
DEBUG-PROVRFLOW
=Title VAX DEBUG Message
Ident: PROVRFLOW
Message Text:
Too many levels of @ procedure nesting
Severity: Warning
Explanation:
The user has nested indirect command processing too
deeply
Try to eliminate some of the levels of indirection
or look for a recursive invocation
DEBUG-PSHINARYNYI
=Title VAX DEBUG Message
Ident: PSHINARYNYI
Message Text:
PUSH_INNER_ARRAY DST stack machine operator for
array 'symbol_name' is not yet implemented
Severity: Error
Explanation:
The named array is unconstrained, and its subscript
bounds live in different places at different points
in the program's execution. This cannot be denoted
using DEBUG Symbol Table (DST) features which this
version of the debugger supports.
Verify that you are using the latest releases of
the compiler and debugger. Examine the nearest
object code which references the variable and
simulate the access algorithm by hand.
DEBUG-PSHVALNYI
=Title VAX DEBUG Message
Ident: PSHVALNYI
Message Text:
PUSH_VALSPEC DST stack machine operator for
variable 'symbol_name' is not yet implemented
Severity: Error
Explanation:
The named variable's address is complex, and its
computation uses operands which live in different
places at different points in the program's
execution. This cannot be denoted using DEBUG
Symbol Table (DST) features which this version of
the debugger supports.
Verify that you are using the latest releases of
the compiler and debugger. Try recompiling the
application without optimization. Examine the
nearest object code which references the variable
and simulate the access algorithm by hand.
DEBUG-PXCN
=Title VAX DEBUG Message
Ident: PXCN
Message Text:
Record object or record formal parameter must
prefix 'CONSTRAINED
Severity: Warning
DEBUG-QUALREQ
=Title VAX DEBUG Message
Ident: QUALREQ
Message Text:
A direction qualifier must be specified with the
EXPAND and MOVE commands.
Severity: Error
Explanation:
Direction ( UP, DOWN, LEFT, RIGHT ) information is
missing from the command.
Provide a direction with the command and try again.
DEBUG-QUOSTRLONG
=Title VAX DEBUG Message
Ident: QUOSTRLONG
Message Text:
Quoted string too long, please shorten
Severity: Error
Explanation:
A quoted string was entered in a debugger command
that was too large for the debugger to handle.
Reenter the command, shortening the string entered.
DEBUG-READERR
=Title VAX DEBUG Message
Ident: READERR
Message Text:
Debugger input read error, force to exit
Severity: Warning
Explanation:
Too many read errors have occurred from the input
command stream. The Debugger will exit after
printing this message
Check the physical integrity of the device
containing the input stream.
DEBUG-REFUSED
=Title VAX DEBUG Message
Ident: REFUSED
Message Text:
Attach request refused
Severity: Error
Explanation:
Either you have attempted to attach to a process
that is your own process or that is not part of
your process tree.
None. You cannot perform the attempted operation.
DEBUG-REGMASKHIDDEN
=Title VAX DEBUG Message
Ident: REGMASKHIDDEN
Message Text:
Register save mask hidden for stack frame
frame_number
Severity: Warning
Explanation:
Information on where the designated routine
invocation might save registers is in a module
which has not been set. Symbolic references to
non-static variables of callers of this routine may
not be resolved correction by the debugger.
Set the module by using the SET MODULE or SET
MODULE/CALLS commands, or enable dynamic module
setting with the SET MODE DYNAMIC command. Then
retry the action which produced this message.
DEBUG-REGMASKMISSING
=Title VAX DEBUG Message
Ident: REGMASKMISSING
Message Text:
Register save mask missing for stack frame
frame_number
Severity: Warning
Explanation:
Information on where the designated routine
invocation might save registers is not available.
Symbolic references to non-static variables of
callers of this routine may not be resolved
correction by the debugger.
Recompile or reassemble the modules using the
/DEBUG qualifier and then relink them.
DEBUG-REGREQ
=Title VAX DEBUG Message
Ident: REGREQ
Message Text:
Register required in context for operand number
operand_number
Severity: Error
Explanation:
A register is required to establish context for the
specified operand.
If the instruction was entered by the user, reenter
the instruction, using a register with the
specified operand. If not, then there may be an
error in the user program instructions.
DEBUG-RENAMENOT
=Title VAX DEBUG Message
Ident: RENAMENOT
Message Text:
Unable to look up 'symbol_name', object being
renamed not found in symbol table
Severity: Warning
Explanation:
The user has requested an operation on an object
that was not found in the symbol table.
Correct and reissue the command
DEBUG-RESUMERR
=Title VAX DEBUG Message
Ident: RESUMERR
Message Text:
An error occurred while trying to resume execution
of the program
Severity: Error
Explanation:
An error status was returned from the call to the
debugger-kernel service that resumes program
execution. Depending on the severity of the error,
the program may or may not have resumed execution.
Examine the error message after this message and
consider if the problem is related to a lack of
quota or otherwise related to your program's
behavior. If so, then take corrective action. If,
after this evaluation, you believe that the problem
lies in the debugger, then submit a Software
Performance Report.
DEBUG-RETURNED
=Title VAX DEBUG Message
Ident: RETURNED
Message Text:
Control returned to process process_name
Severity: Informational
Explanation:
Control has returned to the parent process.
None.
DEBUG-RNDFCTROUT
=Title VAX DEBUG Message
Ident: RNDFCTROUT
Message Text:
Round factor out of range
Severity: Warning
Explanation:
The DIBOL scale factor is out of the acceptable
range
DEBUG-ROPRANDF
=Title VAX DEBUG Message
Ident: ROPRANDF
Message Text:
Reserved operand fault at or near opcode_name
Severity: Error
Explanation:
The debugger encountered an opcode that is reserved
to Digital.
If the instruction was entered by the user, reenter
the instruction, without using an opcode reserved
to Digital. If not, then there may be an error in
the user program instructions.
DEBUG-RPCDBBDT
=Title VAX DEBUG Message
Ident: RPCDBBDT
Message Text:
Bad DTYPE for RPC Data Blocking.
Severity: Error
Explanation:
This message indicates an internal debugger error.
Submit a Software Performance Report.
DEBUG-RPCERR
=Title VAX DEBUG Message
Ident: RPCERR
Message Text:
An internal inter-process communications error has
occurred
Severity: Error
Explanation:
An internal communications error has occurred. The
reason is given in the message following this
message.
If the error is reproducible, submit a Software
Performance Report and, if possible, enclose both a
copy of the program being debugged and a logged
debugging session that reproduces the error.
DEBUG-RPCINVDSC
=Title VAX DEBUG Message
Ident: RPCINVDSC
Message Text:
Invalid RPC descriptor
Severity: Error
Explanation:
This message indicates an internal debugger error.
Submit a Software Performance Report.
DEBUG-RPCOVF
=Title VAX DEBUG Message
Ident: RPCOVF
Message Text:
RPC packet overflow
Severity: Error
Explanation:
This message indicates an internal debugger error.
Submit a Software Performance Report.
DEBUG-RPCUNF
=Title VAX DEBUG Message
Ident: RPCUNF
Message Text:
Undefined RPC function encountered
Severity: Error
Explanation:
This message indicates an internal debugger error.
Submit a Software Performance Report.
DEBUG-RPCUNKARG
=Title VAX DEBUG Message
Ident: RPCUNKARG
Message Text:
Undefined RPC argument encountered
Severity: Error
Explanation:
This message indicates an internal debugger error.
Submit a Software Performance Report.
DEBUG-RSTERR
=Title VAX DEBUG Message
Ident: RSTERR
Message Text:
Error in symbol table
Severity: Error
Explanation:
There is a format error in the symbol table.
If the format error is not caused by a user program
error or a DEPOSIT command, submit a Software
Performance Report.
DEBUG-SCALEADD
=Title VAX DEBUG Message
Ident: SCALEADD
Message Text:
Pointer addition: scale factor of scale_factor
applied to right/left argument
Severity: Informational
Explanation:
Indicates the scale factor applied in computing the
address.
None.
DEBUG-SCALESUB
=Title VAX DEBUG Message
Ident: SCALESUB
Message Text:
Pointer subtraction: scale factor of scale_factor
applied to right/left
Severity: Informational
Explanation:
Indicates the scale factor applied in computing the
address.
None.
DEBUG-SCRNOACCESSR
=Title VAX DEBUG Message
Ident: SCRNOACCESSR
Message Text:
No read access to address address_value for display
in display_name
Severity: Error
DEBUG-SCRNOSRCLIN
=Title VAX DEBUG Message
Ident: SCRNOSRCLIN
Message Text:
No source line for address address_value for
display in display_name
Severity: Warning
Explanation:
No source line corresponds to the address
address_value specified on the debugger command
EXAMINE/SOURCE.
None. This message is informational.
DEBUG-SCRNOTORIGSRC
=Title VAX DEBUG Message
Ident: SCRNOTORIGSRC
Message Text:
Original version of source file not found for
display in display_name file used is
file_specification
Severity: Informational
Explanation:
A source file was found for some module. But the
revision date and time or the file size indicates
that this may not be the same version of the file
that was used in the original compilation of the
module. This warning message indicates that future
source line displays from this source file may not
correspond to the actual source used to compile the
module.
None, unless the original source is available.
Then you can use the debugger command SET SOURCE to
indicate the location of the source to the
debugger.
DEBUG-SCRTOBIG
=Title VAX DEBUG Message
Ident: SCRTOBIG
Message Text:
Screen too big for Screen Mode width must be less
than maximum_width, height less than maximum_height
Severity: Error
Explanation:
The current screen dimensions are too large for
debugger screen mode.
Change the screen dimensions to be small enough for
debugger screen mode.
DEBUG-SCRTOSMALL
=Title VAX DEBUG Message
Ident: SCRTOSMALL
Message Text:
Screen too small for Screen Mode width must be at
least minimum_width, height must be at least
minimum_height
Severity: Error
Explanation:
The current screen dimensions are too small for
debugger screen mode.
Change the screen dimensions to be large enough for
debugger screen mode.
DEBUG-SCRUNAOPNSRC
=Title VAX DEBUG Message
Ident: SCRUNAOPNSRC
Message Text:
Unable to open source file file_specification for
display in display_name
Severity: Warning
Explanation:
Source lines from the file file_specification
cannot be displayed because the debugger was unable
to open the source file (represented as
file_specification). The accompanying VAX RMS
status message gives more information about the
reasons for the source file not being opened.
Examine the VAX RMS status message to determine the
reasons for the source file not being opened, and
take the appropriate action based on that
information.
DEBUG-SCRUNAREASRC
=Title VAX DEBUG Message
Ident: SCRUNAREASRC
Message Text:
Unable to read source file file_specification for
display in display_name
Severity: Warning
Explanation:
Source lines from the file file_specification
cannot be displayed because the debugger was unable
to read the source file (represented as
file_specification). The accompanying VAX RMS
status message gives more information about the
reasons for the source file not being opened.
Examine the VAX RMS status message to determine the
reasons for the source file not being read, and
take the appropriate action based on that
information.
DEBUG-SETKEY
=Title VAX DEBUG Message
Ident: SETKEY
Message Text:
Keypad state has been set to state_name
Severity: Informational
Explanation:
The specified keypad state has been set.
None.
DEBUG-SETKEYERR
=Title VAX DEBUG Message
Ident: SETKEYERR
Message Text:
Error in processing SET KEY command:
Severity: Warning
Explanation:
An error has occurred during a SET KEY command
DEBUG-SFCNTNEG
=Title VAX DEBUG Message
Ident: SFCNTNEG
Message Text:
Shift count is negative
Severity: Warning
DEBUG-SHOKEYERR
=Title VAX DEBUG Message
Ident: SHOKEYERR
Message Text:
Error in processing SHOW KEY command:
Severity: Warning
Explanation:
An error has occurred during the processing of a
SHOW KEY command
DEBUG-SHRPRC
=Title VAX DEBUG Message
Ident: SHRPRC
Message Text:
Debugger will share user process
Severity: Informational
Explanation:
An error occured while trying to create a
subprocess to run the main debugger image. This
message indicates that the debugger is reverting
back to the old behavior of running in the user
process.
Correct the problem specified in the messages
preceding this message. If the problem cannot be
solved, submit a Software Performance Report (SPR).
DEBUG-SIDEFFECT
=Title VAX DEBUG Message
Ident: SIDEFFECT
Message Text:
Operators with side effects not supported (++, --)
Severity: Warning
Explanation:
The user has requested the use of an operator that
has side effects. This operation is not currently
supported by the Debugger.
Issue the operation and the side effects as
individual commands
DEBUG-SIGVECTRUNC
=Title VAX DEBUG Message
Ident: SIGVECTRUNC
Message Text:
Signal vector was truncated
Severity: Warning
Explanation:
The signal vector on this stack frame was too big
to fit into the DEBUG buffer.
Submit an SPR. This message is handled internally,
and should never be signaled to the user.
DEBUG-SIZEATOMIC
=Title VAX DEBUG Message
Ident: SIZEATOMIC
Message Text:
Only atomic data types are supported with 'SIZE
Severity: Warning
Explanation:
SIZE is not supported on the item requested
No user action required
DEBUG-SIZETRUNC
=Title VAX DEBUG Message
Ident: SIZETRUNC
Message Text:
Size field truncated to 32 bits
Severity: Informational
Explanation:
The size of the entry in a VAX BLISS-32 field
specification was larger then 32. The debugger set
the entry size to 32 and executed the command.
None. This message is informational.
DEBUG-SOURCESCOPE
=Title VAX DEBUG Message
Ident: SOURCESCOPE
Message Text:
Source lines not available for .0
%PC Displaying source in a caller of the current
routine
Severity: Informational
Explanation:
There were no source lines available for the
current PC, so the debugger displayed the source
lines for the calling routine. The source lines
may be unavailable because the code associated with
the current PC is not available (e.g. is in a
Digital-supplied shareable image) or was compiled
or linked /NODEBUG.
If source modules is available, then recompile and
relink the application using the /DEBUG qualifier.
DEBUG-SPAWNED
=Title VAX DEBUG Message
Ident: SPAWNED
Message Text:
Subprocess spawned
Severity: Informational
Explanation:
This message is output by the DEBUG command SPAWN
when it spawns a subprocess.
None. This message is informational.
DEBUG-SRCLINNOT
=Title VAX DEBUG Message
Ident: SRCLINNOT
Message Text:
Source lines not available for module path_name
Severity: Warning
Explanation:
The source lines from module CZ cannot be displayed
or searched because there is no source line
information in the symbol table for that module.
Either the compiler is not able to generate such
information or the /DEBUG qualifier was not used on
the compilation or link command.
If the language in question supports source line
display, recompile and relink with the /DEBUG
qualifier. If the language does not support source
line display, source lines will not be available to
the debugger for modules written in that language.
DEBUG-SS_INT
=Title VAX DEBUG Message
Ident: SS_INT
Message Text:
System service intercepted
Severity: Informational
Explanation:
This error code is used by the debugger to indicate
that a system service has been intercepted.
Submit an SPR. This message is handled internally,
and should never be signaled to the user.
DEBUG-STEPINTO
=Title VAX DEBUG Message
Ident: STEPINTO
Message Text:
Cannot step over PC = address_value
Severity: Informational
Explanation:
The debugger was unable to step over the routine
and executed a step into the routine instead.
None. This message is informational.
DEBUG-STGTRUNC
=Title VAX DEBUG Message
Ident: STGTRUNC
Message Text:
String truncated
Severity: Informational
Explanation:
While processing the command, the debugger
truncated a text string.
The debugger failed to allocate a large enough
buffer to store the command output. Unless the
reason for this is apparent, submit a Software
Performance Report (SPR).
DEBUG-STRNGPAD
=Title VAX DEBUG Message
Ident: STRNGPAD
Message Text:
String operand lengths don't match, shorter padded
with blanks on the right
Severity: Informational
Explanation:
The operands of a string comparison ( 'ABC' < 'AB'
) did not have the same length. The shorter one is
blank extended on the right.
Use strings of the same length.
DEBUG-STRTOOLONG
=Title VAX DEBUG Message
Ident: STRTOOLONG
Message Text:
Strings longer than 255 characters not supported
Severity: Warning
Explanation:
The string that was specified by the user is too
large for the debugger to handle
Try to redo the operation with a shorter string
DEBUG-STRUCSIZE
=Title VAX DEBUG Message
Ident: STRUCSIZE
Message Text:
Structure size declared as num_units allocation
units, num_units was given
Severity: Informational
Explanation:
The VAX BLISS-32 structure size was declared to be
num_units units but was referenced with num_units
units.
None. This message is informational.
DEBUG-SUBOUTBND
=Title VAX DEBUG Message
Ident: SUBOUTBND
Message Text:
Subscript subscript_number is out of bounds
Severity: Informational
Explanation:
An attempt to subscript out of the bounds of an
array was made.
Change the value of the subscript.
DEBUG-SUBSCRNG
=Title VAX DEBUG Message
Ident: SUBSCRNG
Message Text:
Subscript out of range, low/high bound for
dimension subscript_number is subscript_bound
Severity: Informational
Explanation:
The subscript specification is not within the
bounds of the array.
Reenter the command, specifying a subscript
specification that is within the bounds defined for
the array.
DEBUG-SUBSTRING
=Title VAX DEBUG Message
Ident: SUBSTRING
Message Text:
Invalid substring (start: low_bound, end:
high_bound), object has length string_size
Severity: Warning
Explanation:
The substring specification (start: low_bound,
end: high_bound ) is not within the bounds defined
for the data type.
Specify a substring specification within the bounds
defined for the data type.
DEBUG-SUPERDEBUG
=Title VAX DEBUG Message
Ident: SUPERDEBUG
Message Text:
SUPERDEBUG not available
Severity: Error
Explanation:
This is a Debug internal message. The user should
never see this message.
If you see this message, please submit an SPR
describing the circumstances.
DEBUG-SYMNOTACT
=Title VAX DEBUG Message
Ident: SYMNOTACT
Message Text:
Non-static variable 'symbol_name' is not active
Severity: Warning
Explanation:
The symbol symbol_name is not defined in an active
call frame.
Check the symbol specified; if correct, ensure that
you have defined the scope correctly.
DEBUG-SYMNOTFND
=Title VAX DEBUG Message
Ident: SYMNOTFND
Message Text:
No symbols matching defined_symbol are defined
Severity: Informational
Explanation:
You attempted to use the SHOW SYMBOL command to
show a symbol that is not defined.
Verify that the symbol is defined and reenter the
command.
DEBUG-SYNCDONE
=Title VAX DEBUG Message
Ident: SYNCDONE
Message Text:
Vector synchronization complete
Severity: Error
Explanation:
This signal is generated by the debugger kernel
after it has executed the synchronization
instruction(s) necessary to insure that all vector
exceptions have been reported.
Submit an SPR. This message is handled internally,
and should never be signaled to the user.
DEBUG-SYNCREPCOM
=Title VAX DEBUG Message
Ident: SYNCREPCOM
Message Text:
Synchronize reporting complete
Severity: Informational
Explanation:
All current vector exceptions have been reported.
None, this message is informational.
DEBUG-SYNC_ALREADY_IN_PROGRESS
=Title VAX DEBUG Message
Ident: SYNC_ALREADY_IN_PROGRESS
Message Text:
Synchronize already in progress.
Severity: Error
Explanation:
Only one synchronize command is allowed at a time.
Do not perform a synchronization command until the
previous command has completed.
DEBUG-SYNERREXPR
=Title VAX DEBUG Message
Ident: SYNERREXPR
Message Text:
Syntax error in expression at or near
'debugger_command_segment'
Severity: Error
Explanation:
The debugger encountered text it does not
understand near '<debugger_command_segment, !AC>'.
Reenter the command, correcting the syntax error.
DEBUG-SYNERRLABEL
=Title VAX DEBUG Message
Ident: SYNERRLABEL
Message Text:
Syntax error in %LABEL construct, see HELP
Built_in_Symbols %LABEL
Severity: Error
Explanation:
The debugger encountered an error in the use of the
%LABEL built-in symbol.
Reenter the command line, correcting the error in
the %LABEL construct.
DEBUG-SYNERRLINE
=Title VAX DEBUG Message
Ident: SYNERRLINE
Message Text:
Syntax error in %LINE construct, see HELP
Built_in_Symbols %LINE
Severity: Error
Explanation:
The debugger encountered an error in the use of the
%LINE built-in symbol.
Reenter the command line, correcting the error in
the %LINE construct.
DEBUG-SYNTAX
=Title VAX DEBUG Message
Ident: SYNTAX
Message Text:
Command syntax error at or near
'debugger_command_segment'
Severity: Error
Explanation:
The debugger encountered a command syntax error
near the element debugger_command_segment.
Re-enter the command.
DEBUG-TASKERROR
=Title VAX DEBUG Message
Ident: TASKERROR
Message Text:
Error error_code from ADA multitasking
Severity: Error
Explanation:
An unexpected error was returned to the debugger
from the Ada RTL. Additional information from the
Ada RTL is appended to this error message.
User action is dependent on the information
returned from the Ada RTL. If the error is not
recoverable, the user may wish to enter an SPR on
the Ada compiler.
DEBUG-TASKNONULL
=Title VAX DEBUG Message
Ident: TASKNONULL
Message Text:
Null task cannot be selected or modified
Severity: Error
DEBUG-TASKNOREGS
=Title VAX DEBUG Message
Ident: TASKNOREGS
Message Text:
Task has no registers (it is the Null task)
Severity: Error
DEBUG-TASKNOTABORT
=Title VAX DEBUG Message
Ident: TASKNOTABORT
Message Text:
Task not aborted; ADA multitasking is executing
critical section
Severity: Error
Explanation:
The task specified may not be aborted at this time.
Retry the abort at a later time.
DEBUG-TASKNOTACT
=Title VAX DEBUG Message
Ident: TASKNOTACT
Message Text:
Task cannot be made the active task; task is not
ready or running
Severity: Error
Explanation:
The task specified to made the active task is not
in either the READY nor the RUNNING state. Tasks
not in those states cannot be made the active task.
To determine the state of the task, perform a SHOW
TASK command.
If the task is in the TERMINATED state, no action
is possible. If the task is in the SUSPENDED
state, the action required to get the task in the
READY or RUNNING state depends on the user program
and the state of the debugging session.
DEBUG-TASKNULL
=Title VAX DEBUG Message
Ident: TASKNULL
Message Text:
Task is null; cannot set attributes of null task
Severity: Error
DEBUG-TERMINATING
=Title VAX DEBUG Message
Ident: TERMINATING
Message Text:
Process-specification is terminating
Severity: Informational
Explanation:
The process process-specification has just finished
execution. All exit handlers in your program have
run. Any SET BREAK/TERMINATING or SET
TRACE/TERMINATING events will now take effect.
Submit an SPR. This message is handled internally,
and should never be signaled to the user.
DEBUG-TIMESLICE
=Title VAX DEBUG Message
Ident: TIMESLICE
Message Text:
Time slice interval has been slowed to 10.0 seconds
Severity: Informational
Explanation:
DEBUG has changed the ADA time slice interval to
10.0 seconds. When you set watchpoints, DEBUG
automatically increases the value of pragma
TIME_SLICE to 10.0. This is because of interaction
between the watchpoint implementation and VAX Ada's
time slicing. Slowing down the time-slice rate
prevents problems from occurring.
If the change in time-slice setting is undesirable,
then avoid the use of watchpoints.
DEBUG-TOOFEWSUB
=Title VAX DEBUG Message
Ident: TOOFEWSUB
Message Text:
Too few subscripts, array has num_dimensions
dimensions
Severity: Warning
Explanation:
The user has specified a symbol reference with too
few subscripts
Correct and reissue the command
DEBUG-TOOMANDIM
=Title VAX DEBUG Message
Ident: TOOMANDIM
Message Text:
Too many dimensions in array
Severity: Warning
DEBUG-TOOMANERR
=Title VAX DEBUG Message
Ident: TOOMANERR
Message Text:
Too many errors, some errors not reported
Severity: Informational
Explanation:
Too many MISMODBEG or certain other errors
occurred. Other similar errors are not reported.
None. This message is informational.
DEBUG-TOOMANINV
=Title VAX DEBUG Message
Ident: TOOMANINV
Message Text:
Too many invocation numbers in symbol pathname
Severity: Error
DEBUG-TOOMANPARM
=Title VAX DEBUG Message
Ident: TOOMANPARM
Message Text:
Too many parameters on command
Severity: Error
DEBUG-TOOMANSUB
=Title VAX DEBUG Message
Ident: TOOMANSUB
Message Text:
Too many subscripts, array has num_dimensions
dimensions
Severity: Warning
Explanation:
The user has specified a symbol reference with too
many subscripts
Correct and reissue the command
DEBUG-UNAACCREG
=Title VAX DEBUG Message
Ident: UNAACCREG
Message Text:
Unable to access beyond end of register set
Severity: Error
Explanation:
The command entered attempted to read or write
beyond the end of a register or register set.
Re-enter the command, insuring that you do not
attempt to access beyond the end of the register
set.
DEBUG-UNACREDBGO
=Title VAX DEBUG Message
Ident: UNACREDBGO
Message Text:
Unable to create DBG$OUTPUT, SYS$OUTPUT used
Severity: Informational
DEBUG-UNACVT
=Title VAX DEBUG Message
Ident: UNACVT
Message Text:
Unable to convert radixvalue to datatype_name
Severity: Warning
Explanation:
Debug was unable to perform the requested
conversion
No user action required
DEBUG-UNACVTBYTTAU
=Title VAX DEBUG Message
Ident: UNACVTBYTTAU
Message Text:
Error converting byte count into target addressable
units
Severity: Error
Explanation:
This is an internal debugger error.
If the error is reproducible, submit a Software
Performance Report and, if possible, enclose both a
copy of the program being debugged and a logged
debugging session that reproduces the error.
DEBUG-UNALIGNED
=Title VAX DEBUG Message
Ident: UNALIGNED
Message Text:
Data is not aligned on a byte boundary
Severity: Warning
Explanation:
The user has requested a type override that can not
be performed
No user action required
DEBUG-UNALLOCATED
=Title VAX DEBUG Message
Ident: UNALLOCATED
Message Text:
Entity 'symbol_name' was not allocated in memory
(was optimized away)
Severity: Warning
Explanation:
The requested entity is not available for use due
to optimizations performed by the compiler
Recompile the program with no optimizations in
effect
DEBUG-UNAOPEDBGI
=Title VAX DEBUG Message
Ident: UNAOPEDBGI
Message Text:
Unable to open DBG$INPUT, SYS$INPUT used
Severity: Informational
DEBUG-UNAOPESCR
=Title VAX DEBUG Message
Ident: UNAOPESCR
Message Text:
Unable to open DBG$OUTPUT for screen output
Severity: Informational
DEBUG-UNAOPNHLP
=Title VAX DEBUG Message
Ident: UNAOPNHLP
Message Text:
Unable to open help library file_specification
Severity: Warning
Explanation:
The help library file_specification cannot be
opened to look for the help you requested. The
accompanying VAX RMS status message gives you more
information about the reasons for the library not
being opened.
Examine the VAX RMS status message to determine the
reasons for the help library not being opened, and
take the appropriate action based on that
information. Also, verify that the logical name
DBG$HELP is either not defined, or is defined to
indicate the proper file.
DEBUG-UNAOPNINI
=Title VAX DEBUG Message
Ident: UNAOPNINI
Message Text:
Unable to open initialization file
file_specification
Severity: Informational
Explanation:
The initialization file cannot be opened. The
accompanying VMS RMS status message gives you more
information about the reasons for the file not
being opened.
Examine the VMS RMS status message to determine the
reasons for the initialization file not being
opened, and take action based on that information.
Also, verify that the logical name DBG$INIT is
defined to indicate the proper file.
DEBUG-UNAOPNSRC
=Title VAX DEBUG Message
Ident: UNAOPNSRC
Message Text:
Unable to open source file file_specification
Severity: Warning
Explanation:
Source lines from the file file_specification
cannot be displayed because the debugger was unable
to open the source file (represented as
file_specification). The accompanying VAX RMS
status message gives more information about the
reasons for the source file not being opened.
Examine the VAX RMS status message to determine the
reasons for the source file not being opened, and
take the appropriate action based on that
information.
DEBUG-UNAREASRC
=Title VAX DEBUG Message
Ident: UNAREASRC
Message Text:
Unable to read source file file_specification
Severity: Warning
Explanation:
Source lines from the file file_specification
cannot be displayed because the debugger was unable
to read the source file (represented as
file_specification). The accompanying VAX RMS
status message gives more information about the
reasons for the source file not being opened.
Examine the VAX RMS status message to determine the
reasons for the source file not being read, and
take the appropriate action based on that
information.
DEBUG-UNASAVVAL
=Title VAX DEBUG Message
Ident: UNASAVVAL
Message Text:
Unable to save value for defined_symbol, definition
ignored
Severity: Warning
DEBUG-UNASETIMG
=Title VAX DEBUG Message
Ident: UNASETIMG
Message Text:
Unable to set image image_name because it has no
symbol table
Severity: Informational
Explanation:
The image is linked with the /NODEBUG qualifier, so
there is no symbol table.
Relink the image with the /DEBUG qualifier.
DEBUG-UNASETTAS
=Title VAX DEBUG Message
Ident: UNASETTAS
Message Text:
Unable to set visible task: registers not
available
Severity: Error
DEBUG-UNASWISTA
=Title VAX DEBUG Message
Ident: UNASWISTA
Message Text:
Unable to create debugger stack, using program
stack
Severity: Informational
Explanation:
DEBUG failed to set the protection ($SETPRT) on the
DEBUG stack's guard pages. This message indicates
an internal debugger error.
Submit an SPR.
DEBUG-UNBPAREN
=Title VAX DEBUG Message
Ident: UNBPAREN
Message Text:
Unbalanced parentheses in expression
Severity: Error
DEBUG-UNDEXPN
=Title VAX DEBUG Message
Ident: UNDEXPN
Message Text:
Undefined exponentiation at or near opcode_name
Severity: Warning
DEBUG-UNDKEY
=Title VAX DEBUG Message
Ident: UNDKEY
Message Text:
State_name key key_name is undefined
Severity: Informational
Explanation:
You attempted to use the SHOW/KEY or the DELETE/KEY
command to show or delete the definition of a key
that is not defined.
Verify that the key is defined and reenter the
command.
DEBUG-UNHANDLED
=Title VAX DEBUG Message
Ident: UNHANDLED
Message Text:
The primary handler should now handle this
unhandled exception
Severity: Success
Explanation:
This is an internal status signal, it should never
be seen by the user. If this message does occur
please submit a Software Performance Report (SPR).
Submit a Software Performance Report (SPR).
DEBUG-UNIMPLENT
=Title VAX DEBUG Message
Ident: UNIMPLENT
Message Text:
Attempt to evaluate unimplemented type
Severity: Warning
DEBUG-UNMTCHPARN
=Title VAX DEBUG Message
Ident: UNMTCHPARN
Message Text:
Unmatched left parenthesis found
Severity: Warning
Explanation:
A left parenthesis (() was found, but the matching
right parenthesis ()) is missing.
Include the right parenthesis ()).
DEBUG-UNREQVQUAL
=Title VAX DEBUG Message
Ident: UNREQVQUAL
Message Text:
Unreqcognized vector instruction qualifier
specified at 'command_line'
Severity: Error
Explanation:
The qualifier indicated in the shown command line
fragment is unreqcognized.
Specify a legal vector instruction qualifier.
DEBUG-UPBNDOPT
=Title VAX DEBUG Message
Ident: UPBNDOPT
Message Text:
Upper bound of subrange was optimized away
Severity: Informational
Explanation:
The upper bound of the specified subrange was
optimized away by the compiler. In place of the
actual upper bound, DEBUG used the hex value
7FFFFFFF.
None. This message is informational.
DEBUG-USREVNTERR
=Title VAX DEBUG Message
Ident: USREVNTERR
Message Text:
User-specified event error code error_code returned
by user RTL
Severity: Error
DEBUG-VALNOTADDR
=Title VAX DEBUG Message
Ident: VALNOTADDR
Message Text:
Value of variable 'symbol_name' not usable as
address
Severity: Warning
Explanation:
The value of the specified variable is not usable
as an address. The address must be a longword.
Modify the address and retry the operation.
DEBUG-VALRNG
=Title VAX DEBUG Message
Ident: VALRNG
Message Text:
Value is subscript_value, bounds are
low_bound..high_bound
Severity: Informational
Explanation:
An attempt to subscript out of the bounds of an
array was made.
Change the value of the subscript.
DEBUG-VARNESDEP
=Title VAX DEBUG Message
Ident: VARNESDEP
Message Text:
Variant nesting depth exceeds 20, cannot access
record component
Severity: Error
DEBUG-VECDIS
=Title VAX DEBUG Message
Ident: VECDIS
Message Text:
Debugger-generated vector disabled fault
Severity: Error
Explanation:
This signal is generated by the debugger kernel
while it is processing a vector disabled fault that
it has caused.
Submit an SPR. This message is handled internally,
and should never be signaled to the user.
DEBUG-VECREASON
=Title VAX DEBUG Message
Ident: VECREASON
Message Text:
The reason values for this vector error are
reason_values
Severity: Informational
Explanation:
An internal error has occurred with the debuggers
use of vector instructions. The particular error
code has two values which are associated with it,
which more fully explain what went wrong.
None.
DEBUG-VECSCP0
=Title VAX DEBUG Message
Ident: VECSCP0
Message Text:
Vector registers can be accessed only in scope 0
Severity: Error
Explanation:
An attempt was made to reference a vector register
from a scope other than scope 0. DEBUG will not
accept a command which specifies any other scope
for a vector register.
If the current scope has been set to a scope other
than scope 0 (using the SET SCOPE command), use an
explicit 0\ pathname to access the vector register.
DEBUG-VECTSUBRNG
=Title VAX DEBUG Message
Ident: VECTSUBRNG
Message Text:
Vector register subscript out of bounds, bounds are
low_bound..high_bound
Severity: Error
Explanation:
An attempt to subscript out of the bounds of an
array was made.
Change the value of the subscript.
DEBUG-VERIFYICF
=Title VAX DEBUG Message
Ident: VERIFYICF
Message Text:
Opening/closing command procedure
file_specification
Severity: Informational
Explanation:
The debugger is verifying a command procedure.
This message is displayed before the command
procedure is executed and after all the commands
have been displayed.
None. This message is informational.
DEBUG-VERSIONNUM
=Title VAX DEBUG Message
Ident: VERSIONNUM
Message Text:
The debugger_type debugger has RPC version
major_version/minor_version
Severity: Informational
Explanation:
This message is to inform you of the version
number(s) of the main and kernel debuggers. It
will only appear as part of another message, such
as INCOMVERSION.
Submit an SPR. This message is handled internally,
and should never be signaled to the user.
DEBUG-VFLTDIV
=Title VAX DEBUG Message
Ident: VFLTDIV
Message Text:
Reserved operand, encoded as floating divide by
zero
Severity: Error
Explanation:
During a floating-point operation, an attempt was
made to divide by zero.
Examine the code that caused the fault. Verify
that the operands or variables are specified
correctly. Verify that the encoded reserved
operand was not deposited by a non-floating-point
operation.
DEBUG-VFLTOVF
=Title VAX DEBUG Message
Ident: VFLTOVF
Message Text:
Reserved operand, encoded as floating overflow
Severity: Error
Explanation:
During a floating-point operation, a floating point
value exceeded the largest representable value for
that data type.
Examine the code that caused the fault. Verify
that the operands or variables are specified
correctly. Verify that the encoded reserved
operand was not deposited by a non-floating-point
operation.
DEBUG-VFLTROP
=Title VAX DEBUG Message
Ident: VFLTROP
Message Text:
Reserved operand, encoded as floating reserved
operand
Severity: Error
Explanation:
During a floating-point operation, an attempt is
made to divide by zero.
Examine the code that caused the fault. Verify
that the operands or variables are specified
correctly. Verify that the encoded reserved
operand was not deposited by a non-floating-point
operation.
DEBUG-VFLTUND
=Title VAX DEBUG Message
Ident: VFLTUND
Message Text:
Reserved operand, encoded as floating underflow
Severity: Error
Explanation:
An arithmetic exception condition occurred as a
result of floating-point underflow.
Examine the code that caused the fault. Verify
that the operands or variables are specified
correctly. Verify that the encoded reserved
operand was not deposited by a non-floating-point
operation.
DEBUG-WATCHSETUP
=Title VAX DEBUG Message
Ident: WATCHSETUP
Message Text:
Instruction at current PC may trigger a watchpoint
Severity: Error
Explanation:
This signal is generated by the debugger kernel
when it is about to execute an instruction that may
trigger a watchpoint.
Submit an SPR. This message is handled internally,
and should never be signaled to the user.
DEBUG-WATCHSIZE
=Title VAX DEBUG Message
Ident: WATCHSIZE
Message Text:
Cannot WATCH variables longer than 512 bytes
Severity: Error
DEBUG-WATNOWCAN
=Title VAX DEBUG Message
Ident: WATNOWCAN
Message Text:
Watchpoint now cancelled
Severity: Informational
Explanation:
This message is a sub-message to WATVARSCP,
WATVARPTR, and WATVARPROT. This message indicates
that the original watchpoint has been cancelled (is
no longer active).
None. This message is informational.
DEBUG-WATNOWWAT
=Title VAX DEBUG Message
Ident: WATNOWWAT
Message Text:
Now watching variable name
Severity: Informational
Explanation:
This message is a sub-message to WATVARSCP and
WATVARPTR. This message indicates the new name
under which a variable which either went out of
scope or whose pointer(s) changed is addressed by
the debugger. If this message appears, the
watchpoint is still active under this new name.
None. This message is informational.
DEBUG-WATVARGSGONE
=Title VAX DEBUG Message
Ident: WATVARGSGONE
Message Text:
Global section associated with watched variable
variable name has been unmapped
Severity: Informational
Explanation:
The global-section which contained a global-section
watchpoint is no longer mapped by any process that
is under debugger control. This message is always
followed by the WATNOWCAN message, since the
debugger must delete the watchpoint.
No action necessary.
DEBUG-WATVARGSOVR
=Title VAX DEBUG Message
Ident: WATVARGSOVR
Message Text:
Watched variable overlaps into a global section
Severity: Error
Explanation:
The specified variable spans a range of virtual
memory which includes a global-section and a
private-section. A watched variable must either be
entirely in a global-section or entirely in a
private-section.
Do not use watchpoint on this address.
DEBUG-WATVARNOWGBL
=Title VAX DEBUG Message
Ident: WATVARNOWGBL
Message Text:
Watched variable variable name has been re-mapped
to a global section
Severity: Informational
Explanation:
The program mapped a global-section over a watched
variable. This message indicates that the debugger
made the watchpoint a global-section watchpoint.
If the global-section is mapped by more than one
process that is under the debugger control, the
watched variable will be watched in each process
that is mapped to the global section.
No action necessary.
DEBUG-WATVARPROT
=Title VAX DEBUG Message
Ident: WATVARPROT
Message Text:
Watched variable variable name is no longer
accessible
Severity: Informational
Explanation:
Some action by the program has made the target
variable inaccessible to the debugger. The program
might have deleted the virtual memory which
contains some part of the variable or one of the
pointers in the pointer chain to the variable, or
the program might have set the protection of such
virtual memory such that the debugger can not read
it. This message is always followed by the
WATNOWCAN message, since the debugger must delete
the watchpoint.
None. This message is informational.
DEBUG-WATVARPTR
=Title VAX DEBUG Message
Ident: WATVARPTR
Message Text:
Watched variable variable name now points to a
different address
Severity: Informational
Explanation:
Some pointer in the variable reference has changed
value. This message is accompanied by a further
message indicating whether the debugger has
cancelled the watchpoint or re-defined the
watchpoint to address the original data by a
different name.
None. This message is informational.
DEBUG-WATVARREMAP
=Title VAX DEBUG Message
Ident: WATVARREMAP
Message Text:
Watched variable variable name touches a page which
has been re-mapped by the user program
Severity: Informational
Explanation:
Some action by the user program has made it
impossible for the debugger to set the protection
on part or all of the variable. The debugger will
therefore not detect changes to the variable. This
message is always followed by the WATNOWCAN
message, since the debugger must delete the
watchpoint.
None. This message is informational.
DEBUG-WATVARSCP
=Title VAX DEBUG Message
Ident: WATVARSCP
Message Text:
Watched variable variable name has gone out of
scope
Severity: Informational
Explanation:
The identified variable is no longer accessible by
its original name. The program may have returned
from the routine in which the variable was defined,
or it may have called another routine. This
message is accompanied by a further message
indicating whether the debugger has cancelled the
watchpoint (in the case that the variable is truly
gone) or re-defined the watchpoint to address the
same data by a different name.
None. This message is informational.
DEBUG-WIDTHDIFF
=Title VAX DEBUG Message
Ident: WIDTHDIFF
Message Text:
Desired width of display_width is not allowed,
width is set to display_width
Severity: Informational
Explanation:
After creating the display pasteboard using the SMG
routine SMG$CREATE_PASTEBOARD, DEBUG found that the
display width was not in the range 20-255.
Issue the DCL command SHOW TERMINAL and verify that
the terminal width is correct and in the range
20-255.
DEBUG-WORKSTACMD
=Title VAX DEBUG Message
Ident: WORKSTACMD
Message Text:
The command debugger-command is only supported on
VWS workstations
Severity: Warning
Explanation:
The debugger only supports the command
debugger-commandon workstations running VWS.
None. This capability of the debugger does not
exist for your terminal or machine.
DEBUG-WPTTRACE
=Title VAX DEBUG Message
Ident: WPTTRACE
Message Text:
Non-static watchpoint, tracing every instruction
Severity: Informational
Explanation:
Setting a watchpoint on a non-static location such
as the stack or on a register forces the debugger
to trace every instruction that is executed. This
will slow down execution of your program by a
considerable amount.
If you do not want execution of your program slowed
down, then you must cancel the watchpoint.
DEBUG-WRITE_FAILED
=Title VAX DEBUG Message
Ident: WRITE_FAILED
Message Text:
An attempt to write into a memory location failed
Severity: Error
Explanation:
This message indicates an internal debugger error.
Submit a Software Performance Report.
DEBUG-WRITE_INTO_KERNEL
=Title VAX DEBUG Message
Ident: WRITE_INTO_KERNEL
Message Text:
Cannot write into the debugger kernel's address
space
Severity: Error
Explanation:
This message indicates an internal debugger error.
Submit a Software Performance Report.
DEBUG-WRITE_INTO_KERNEL_STACK
=Title VAX DEBUG Message
Ident: WRITE_INTO_KERNEL_STACK
Message Text:
Cannot write into the debugger kernel's stack
Severity: Error
Explanation:
This message indicates an internal debugger error.
Submit a Software Performance Report.
DEBUG-ZERLENDST
=Title VAX DEBUG Message
Ident: ZERLENDST
Message Text:
Zero length DST record has been ignored (compiler
error)
Severity: Informational
Explanation:
A zero-length DST record was encountered within a
module. This message normally indicates a compiler
error.
Submit a Software Performance Report.
DEBUG-ZEROINCR
=Title VAX DEBUG Message
Ident: ZEROINCR
Message Text:
Increment for ranged examine is zero; exiting loop
Severity: Informational
Explanation:
While performing a ranged examine, DEBUG no
successor to the current data item was found
because the length of the current data item was
zero bytes.
None. This message is informational.