HP-UX SYMBOLIC DEBUGGER ERRORS AND WARNINGS ABBREVIATIONS CMD A debugger command. FILE The name of a file. NAME The name of a data object. NUM A number. PROC A user program or debugger internal procedure name. TEXT A text string of some kind. MESSAGES AND MEANINGS These are sorted case-independently, with punctuation marks (like quote) and abbreviations (like TEXT) significant. For example, some error messages start with "TEXT" or "NUM". Each explanation tries to be helpful, complete, and self-contained. "." must be followed by a depth "Proc.depth" was entered incorrectly. See the quick reference (use the "help" command). "a" must be followed by "a", "d", or "s" only If "a" is preceded by a modifier (expression), it must apply to an existing assertion which is to be activated, deleted, or suspended. See the quick reference (use the "help" command). "CMD" not allowed while running assertions Given command cannot be executed while assertions are active. If it appears in an assertion command list, it must follow an "x" (exit) command with a non-zero modifier. "D", "D a", or "D b" is required Command was followed by something other than null, "a", or "b". See the quick reference (use the "help" command). "dir" command needs a directory name (in quotes) The "dir" command was invoked without specifying a directory name surrounded by double-quote marks. "f" command needs a string argument Command was followed by something other than null or a string in "". See the quick reference (use the "help" command). "g" must be followed by a linenumber Command was given without a numeric argument. See the quick reference (use the "help" command). "NAME" is not a field name Named object was used improperly as a structure field, which it is not. Use the "/t" format to find the type of NAME. "x" is only allowed while running assertions Attempt to exit assertions mode while assertions were not running. See the manual entry. (file unknown) Current viewing location does not correspond to any known (debuggable) sourcefile. It may be in an unknown (non- debuggable) procedure. (line unknown) Current viewing location does not correspond to any known (debuggable) sourceline. It may be in procedure prologue code or in an unknown (non-debuggable) procedure. (not a real number) The item to be displayed does not contain a valid real- number bit pattern. Address is required before "CMD" Break-on-address commands must be preceded by a code address (a constant, the name of a procedure, or some other expression). See the quick reference (use the "help" command). Address not found Given address (result of a command) is invalid in the current corefile. Argument list too long Arguments to the "r" command were expanded by the shell to more than 1024 bytes. Assigning to NUM byte object from NUM byte object; moved NUM bytes Object on the left-hand-side of an assignment is bigger than a double, and not equal to the size of the right- hand-side expression. Debugger copies a series of bytes equal in size to the left-hand-side. Attempt to assign into NUM byte object; limit is NUM bytes Object on the left-hand-side of an assignment is bigger than the debugger can assign, due to a limit on buffer space. This is also a safety precaution. Attempt to write to ODD address Ptrace(2) failed; can't write to an odd address on a system which does not support it. Bad access to child process Failed to read data from or write data to a child process for unknown reasons. Most likely due to an invalid address, e.g. dereferencing an invalid pointer. Might be due to an attempt to plant a breakpoint in unwritable child process code space before running the process. Bad magic number in InitSymfile() (NUM) Objectfile is not marked (in the first few bytes) as containing executable object code. NUM is the magic number found. Bad procedure address in IbpFRun() (NUM) Failed command-line procedure call due to an invalid procedure address, for unknown reasons. Debugger or linker symbol table might be corrupt. NUM is the address which could not be called. Can't find end of "PROC" Failed to find break-on-exit address in the symbol table for procedure PROC. Symbol table might be corrupt. Can't find idb in ifd in IssFIdb() (NUM, NUM) Definition of a DBX type (first NUM) not found in a given file (second NUM). Can't find [address of] main procedure in debug symbol table in InitAll() (NUM, NUM) Could not find a procedure with the proper name (i.e. "main" or "_MAIN_", depending on version), or could not find an address for that procedure. Might be due to a non-debuggable, missing, mis-named, or mis-aliased main procedure (main program), or to an include of a sourcefile between the procedure declaration (or begin statement) and its first executable line. Parameters are file number (see "lf" command) and source line number which did not have a valid code address. Can't find '_u' entry in /hp-ux The debugger could not find the Uarea offset in the system file "/hp-ux". The '_u' entry must be an external, absolute symbol. Execution terminates. Can't goto a line outside of the current procedure Line number given to the "g" command is not an executable source line in the top procedure on the child process stack (not necessarily the same as the current viewing procedure). Can't handle bit fields for this machine Symbol table supported by your version of the debugger is deficient. Can't handle constant in VT in AdrFIsym() (NUM) Constants can be stored in code, as initialized globals, or in the value table. The debugger encountered one stored in the value table that it could not handle. The only type of constants handled in the VT are: 4- and 8- byte reals, Series 200 and Series 500 "strings", and Pascal packed arrays of char. NUM is the symbol table index of the unsupported symbol. Can't handle decimal reals Debugger does not support decimal-format real numbers, but it encountered one in the symbol table. No compilers are supposed to support them either. Can't open "FILE" as playback file Can't open "FILE" as record file Fopen(3s) of FILE with an appropriate mode ("r" for playback, "w" or "a" for record) failed. Check file path and permissions. Can't pass more than NUM arguments to called procedure There is a (large) limit (NUM) on how many parameters can be passed to a procedure called from the command line. Can't read "FILE"; ignoring it Attempt to read from corefile (FILE) during initialization failed for some reason. Debugger continues, but ignores corefile. Can't read header of FILE Read(2) from header of objectfile (FILE) failed for some reason. Possibly the file is smaller than the size of the header. Can't save string constant (no end.o buffer) /usr/lib/end.o was not linked with objectfile, or for some reason the magic symbols "__buffer" and "__bufMax" were not found in the symbol table. /usr/lib/end.o is automatically linked for you on some systems if you give the "-g" option to the compiler front end. However, it might not be linked if you invoke the linker directly. Also, the symbol table might be corrupt. Can't set any registers Setting registers incorrectly on some systems is very dangerous and could potentially lead to complete lockup of the operating system. You can use "g" (goto) to make limited, safe changes to $pc. Can't set breakpoint (invalid address) However a breakpoint set command was specified, the resulting address is invalid or unknown (-1). Can't store into a constant Left-hand-side of assign statement is marked as a constant, which cannot be modified. Use the "/t" display format for more information. Can't take the address of a constant Operand of "&" operator is marked as a constant, which has no address. Use the "/t" display format for more information. Can't take the address of a register Operand of "&" operator is marked as a register type, which has no address. Use the "/t" display format for more information. cannot continue Some error occurred during debugger initialization, which is the only time the debugger cannot attempt to restart. Only given following some other error report. Cannot open "FILE" Fopen(3s) of FILE (a sourcefile and/or argument to "e" command) for reading failed. Check file path and permissions. Cannot read that location Cannot write that location For some reason, probably invalid address, access to a child process failed. Character constant is missing ending ' Token parsed as a character constant is missing a trailing single quote. Applies to unquoted single quote followed by a single character or equivalent (backslash sequence). Child process out of memory in PushWord() (0) Unable to push words on the child process stack in preparation for a command line procedure call, because its stack is too big. Command line or portion ignored: "TEXT" Debugger hit a breakpoint or otherwise entered interactive command mode while there were commands left to do from the previous command line. Old commands (TEXT) are tossed, with this warning given. Confused looking at bit field NAME @ NUM The bit field NAME described at location NUM in the string table has invalid type information. Possibly due to a corrupt string table. Data too big to put in the child process[; see "end.c"] String constant or other data is larger than the total size of the buffer in /usr/lib/end.o. On some systems you can modify /usr/lib/end.c, recompile, and relink. Empty assertion not added "a" command given without associated assertion commands (rest of line or portion within "{}" is null). End of file in LabelFAdr() (0) Objectfile ended before end of linker symbol table (according to header). Possibly due to a corrupt objectfile. end of file on non-interactive standard input Debugger terminates (instead of going into an infinite loop) if gets(3s) returns no characters from standard input and isatty(3c) says stdin is not a terminal. Errno may be wrong, but here is the error Debugger internal error occurred and errno(2) was nonzero, so debugger calls perror(3) to try to explain it. error Unspecified user error occurred. Should never happen: All user errors have descriptions. Escape NUM from called procedure "PROC" Procedure PROC called from the command line, or some procedure it called in turn, exited via the Series 500 escape mechanism, with a value of NUM. Exiting command line procedure call Command-line procedure call environment terminated for an unusual reason, such as hitting BREAK, or encountering an error before calling the procedure. Extra token ignored: "TEXT" After parsing a command, unexpected token (TEXT) was found before end of line or command terminator (";", or "}"). See the quick reference (use the "help" command). Fgets() failed in Find() (NUM) Fgets() failed in PrintLine() (NUM) Attempt to read one line (up to 1024 bytes) from the current viewing file failed for unknown reasons. Probably due to corrupt file or filesystem. NUM is the FILE* of the file to read. fork() failed Failed call to fork(2), for unknown reasons, attempting to generate a child process for debugging objectfile. Fseek() failed in Find() (NUM) Fseek() failed in PrintLine() (NUM) Attempt to seek to a line in the current viewing file failed for unknown reasons. Probably due to corrupt file or filesystem. NUM is the file offset of the seek. Format is missing No display format given after "/" or "?" following an expression. Remember that "//" is used for division. See the quick reference (use the "help" command). FORTRAN variable not pure array Attempt to dereference an array which also has pointer or function qualifiers while the current language is set to FORTRAN, which does not support them. Try again with $lang set to a different language. GetUser() failed (NUM, -1) Attempt to read from child process user space failed for some reason, probably invalid address (NUM). Illegal fp == 0 in AdrFIsym() (NUM) Attempt to get the address of a dynamic (stack-relative) data object with no frame pointer supplied. Probably due to a corrupt symbol table. NUM is the symbol table index of the bad symbol. Illegal indirection Arguments to the "r" command attempt to redirect I/O using "<" or ">" with no filename supplied. Immediate subscript type in BoundsFDntt() (NUM, NUM) Attempt to dereference an array which has an immediate index type (not a subrange) that is not CHAR. Probably due to a corrupt symbol table. Parameters are the immediate index type and the symbol table index of the bad symbol. Incompatible operands for string assignment Attempted to assign to a FORTRAN CHAR*, Pascal string or Pascal packed array of char something other than a FORTRAN CHAR*, Pascal string, Pascal packed array of char, a string constant or a character constant. InstallBp: Dup Inst but no Dup Bpt While installing a breakpoint (planting an illegal instruction in the code), cdb found an illegal instruction already there and no other breakpoint at the same location. Possibly due to a corrupt code image. Insufficient information to do a structure dump Symbol table supported by your version of the debugger is deficient. interrupt (use "q" to quit or the QUIT signal to abort) The debugger caught a SIGINT signal (from BREAK key or equivalent) and reset itself to command input state. Use the "q" command to quit gracefully. If all else fails, give the SIGQUIT signal (try control-backslash for starters). Invalid basetype in TyFImmedHp() (NUM, NUM) Symbol table entry has an unrecognized basetype. Probably due to a corrupt symbol table. Parameters are the type information and the symbol table index of the bad symbol. Invalid breakpoint type "CMD" Given CMD is an invalid breakpoint command type. See the quick reference (use the "help" command). Invalid combination of operator and operands Attempt to do a numeric operation on one or more non- numeric operands. Invalid display format "TEXT" Given data display format or portion thereof (TEXT) has invalid syntax. See the quick reference (use the "help" command). Invalid field access: "NAME" Attempt to do a field dereference from an object (NAME) which is not a structure or union. Use the "/t" display format for more information. Invalid immediate type for set in PxSet() Invalid non-immediate type for set in PxSet() Attempt to print the value of a Pascal set with an invalid basetype. Basetypes cdb recognizes for sets are: enum's (includes boolean), subranges, and char. Probably due to a corrupt symbol table. Invalid local name "Proc[.depth].var" entered incorrectly; "var" must be a variable name (string). See the quick reference (use the "help" command). Invalid pointer in Free() (NUM) Debugger attempted to return malloc(3c) memory, but the pointer (NUM) was invalid. Probably due to a corrupt environment. Invalid segment maps Debugger attempted to map a Series 500 data pointer while a child process was supposedly active, but for some reason (possibly fork(2) failure), segment maps were not current. Try terminating and re-running the child process. Invalid size for Boolean in TyFImmedHp() (NUM, NUM) Invalid size for real number in TyFImmedHp() (NUM, NUM) Symbol table entry has an invalid bit size for a Boolean object (must be 1, 16, or 32) or floating point number (must be sizeof (float) or sizeof (double)). Probably due to a corrupt symbol table. Parameters are the bit size and the symbol table index of the bad symbol. Invalid stack frame pointer in NextFrame() (NUM) Top four bits of $fp are not equal to 0111 on certain systems. NUM is the bad frame pointer. Invalid stack marker delta Q in NextFrame() (NUM, NUM) Child process stack frame pointer to next frame is too large or not a multiple of four. Parameters are the pointer to the bad frame and the bad delta Q value. Invalid stack? Bottom of child process stack reached before finding a stack frame which saved a specific register value. Invalid token in PsFOperator() (NUM) Debugger tried to do math with an invalid operator token (internal number NUM). Probably due to a corrupt environment. Islt out of bounds in SetNextSlt() (NUM) Islt out of bounds in SetSlt() (NUM) Source line table index NUM out of the limits in objectfile header trying to set to that table entry. Probably due to a corrupt symbol table. Iss out of bounds in SetIss() (NUM) Iss out of bounds in VTInCore() (NUM) String table (value table) index NUM out of the limits in objectfile header trying to set to that location. Probably due to a corrupt symbol table. Isym out of bounds in SetNext() (NUM) Isym out of bounds in SetSym() (NUM) Symbol table index NUM out of the limits in objectfile header trying to set to that table entry. Probably due to a corrupt symbol table. It appears that there's no debugging information in FILE Symbol table sections (probably) exist in objectfile FILE but appear to contain no procedure references. Probably due to a corrupt symbol table or an objectfile compiled with no debuggable procedures (at least the main procedure must be debuggable). It's not C, it's not Pascal, what is it? Can't find a main program named "main" or "program" in the BSD version. Ity out of bounds in SetTy() (NUM) Ity out of bounds in SetTyNext() (NUM) Type record index NUM out of the limits in objectfile header trying to set to that record. Probably due to a corrupt symbol table. Length not allowed with "TEXT" format Given data display format (TEXT) does not allow data length specification because it's irrelevant or implicit in the format. See the quick reference (use the "help" command). List Labels is not supported "l l" command is not supported by your version of the debugger. Local is not active Local variable name is recognized but the procedure it belongs to is not currently active on the child process stack. Local labels not supported yet in AdrFLabel() (0) Local labels not supported yet in LabelFAdr() (NUM) Linker symbol table lookup is not supported by your version of the debugger. NUM is the address to find. Lost in array spec Array description in string table is invalid. Probably due to a corrupt symbol table. Malloc() failed in PROC() (NUM) Debugger attempt to obtain more heap memory using malloc(3c) failed for unknown reasons in internal procedure PROC. NUM is the number of bytes requested. Use the "I" command to see the number of bytes currently in use. Map is not supported. "M" command is not supported by your version of the debugger, probably because corefiles are not supported. Misformed expression Expression was entered incorrectly. In this and other cases the debugger shows you where the error was detected in the command line, which is usually at or one token beyond the actual error. See the manual entry for details. Misformed global name ":" must be followed by a variable name (string). See the quick reference (use the "help" command). Misformed hex number "0x" or "0X" was given with no following digits. Misformed octal number Octal number (starting with "0") contains "8" or "9". Missing "{" "If" command does not have a "{" following the conditional expression. Possibly expression was entered wrong. Modifier is not allowed before "CMD" command Given command (CMD) does not allow a leading modifier (expression). See the quick reference (use the "help" command). More than NUM args; ignoring "TEXT" More than 100 command-line arguments given with an "r" command; remainder are not passed. TEXT is the portion which is ignored. Must specify which assertion to modify Assertion modification commands ("a a", "a d", and "a s") must have a leading modifier (expression). See the quick reference (use the "help" command). Need a "." after the number "Proc.depth.var" entered incompletely (".var" missing). See the quick reference (use the "help" command). Need a line number after the "#" "Proc#line" entered incompletely ("line" missing or not a simple line number). See the quick reference (use the "help" command). NUM (value not defined for "enum NAME") Enumeration variable (NAME) is set to a value (NUM) not listed in the symbol table. Probably the value was set incorrectly by the program or the debugger. Possibly due to a corrupt symbol table. No alternate directories None to list because debugger was invoked without the "-d" option. See the quick reference (use the "help" command). No assertion number NUM Attempt to apply assertion modification command ("a a", "a d", or "a s") to a non-existent assertion. Use the "l a" command to list all existing assertions, or see the quick reference (use the "help" command). No assertions Attempt to list or delete all assertions when none are defined. See the quick reference (use the "help" command). No breakpoints Attempt to list or delete all breakpoints when none are defined. See the quick reference (use the "help" command). No child process No child process AND no corefile No core file Attempt to do an operation requiring the existence of a child process and/or a corefile when none exists. Use the "r" or "s" commands to start a child process. Corefile must be given as a command-line argument to the debugger, or a file named "core" must exist when the debugger starts up, or a child process must terminate in a way which leaves a corefile. (Some versions do not support corefiles.) No current procedure Attempt to list locals ("l") for the current viewing procedure when none is defined. Specify a procedure name. See the quick reference (use the "help" command). No globals No labels No locals No matching globals No matching labels Attempt to list globals, labels, or locals (of the current viewing procedure if none specified) when there are none, or when none match a given pattern. See the quick reference (use the "help" command). No match for "TEXT" Search pattern (TEXT) for "/", "?", "n", or "N" not found anywhere in the current viewing file (give an "e" command to see what it is). Remember that pattern is literal, not a regular expression. No matching SLT_END in AdrFEndOfProc() (NUM, NUM) Failed to find break-on-exit address in the symbol table for a procedure because no matching END was found in the source line table. Probably due to a corrupt symbol table. Parameters are the procedure number and its symbol table index. No playback name specified "<" or "<<" command given without filename argument before end of line or command separator (";" or "}"). See the quick reference (use the "help" command). No search pattern Search command ("/", "?", "n", or "N") given without a search pattern (in the case of "n" and "N", no previous "/" or "?" given with a pattern). See the quick reference (use the "help" command). No source file for current address Command given which requires a current viewing file when there is none set, or the current child process address does not map back to a known (debuggable) sourcefile. No such breakpoint Attempt to delete a non-existent breakpoint. Use the "l b" command to list all existing breakpoints, or see the quick reference (use the "help" command). No such field name "NAME" No such field name "NAME" for that record No such field name "NAME" for that struct No such field name "NAME" for that union Struct (union, record) does not contain a field of that NAME. No such procedure "PROC" Attempt to list locals of a non-existent (or non- debuggable) procedure PROC. Use "l p" to list all known (debuggable) procedures. No such procedure or file name "TEXT" Attempt to view (with "e" command) a procedure or file (TEXT) which does not exist (or is non-debuggable). Use "l p" to list all known (debuggable) procedures. Use "l f" to list all known (debuggable) files. No symbols for that procedure Attempt to set a breakpoint using a stack depth when the procedure at that stack depth is non-debuggable. Try setting a break-on-address by the name of the procedure (e.g. "xxx ba"). (Addresses of non-debuggable procedures are not usable this way on some systems.) One or more symbol table sections missing: Code is not debuggable. Objectfile header gives a size of zero or less for one or more symbol table sections, so the debugger cannot be used. Be sure that at least the main procedure (program) is compiled with debug on and that no program (including the linker) strips out the symbol tables. One or more symbol table sections not a whole number of records Objectfile header gives an invalid size for one or more symbol table sections. Probably due to a corrupt or improper objectfile. Operand stack overflow Operator stack overflow Expression too complicated for expression handler to parse. Virtually impossible, but a combination of more than 15 nested parentheses and/or pending operators might cause it. Operator stack underflow Expression handler ran out of operators. Should be impossible; probably due to bug in parser, or corrupt environment. pipe() failed Failed call to pipe(2) for unknown reasons, attempting to pass "r" command arguments to a shell for expansion. Postfix "++" not supported Postfix "--" not supported Prefix "++" not supported Prefix "--" not supported Attempt to use unsupported operator. For addition/subtraction with unary sign, separate the characters, e.g. "2- -5". Procedure not active In "proc[.depth].var", procedure "proc" is not active on the child process stack, so its locals have no current values. Procedure "PROC" not found at stack depth NUM In "proc.depth", procedure PROC is not on the child process stack at depth NUM. The stack is that deep but the procedure at that depth is not PROC. Use the "t" command to list the stack. (If NUM is 10000 and no depth was specified, then PROC was not found anywhere in the top NUM procedures.) Ptrace() failed in GetSegMaps() (NUM) Attempt to read child process segment maps for a new child process failed for unknown reasons (possibly fork(2) failure). NUM is the child process number. (Following this, attempts to access the child process lead to "Invalid segment maps" until the child process is restarted and the maps successfully read.) Ptrace() failed in PushWord() (NUM) Attempt to push words on the child process stack in preparation for a command line procedure call failed for unknown reasons. NUM is the system error number (errno). PutUser() failed (NUM, NUM) Attempt to write to child process user space failed for some reason, probably invalid address (first NUM). Second parameter is data value to be written. Read() failed in AdrFLabel() (NUM) Read() failed in InitLSTPd() (NUM) Read() failed in LabelFAdr() (NUM) Read() failed in ListLabels() (NUM) Read() failed in UareaFLst() (NUM) Attempt to read from the linker symbol table in objectfile failed for unknown reasons. Probably due to corrupt file or filesystem. NUM is the number of bytes to read. Read() failed in SbFInp() (NUM) Attempt to read from the linker name pool in objectfile failed for unknown reasons. Probably due to corrupt file or filesystem. NUM is the number of bytes to read. Read() failed in SetCache() (NUM) Attempt to read from the symbol table in objectfile failed for unknown reasons. Probably due to corrupt file or filesystem. NUM is the number of bytes to read. Read() failed in SetIss() (NUM) Attempt to read from the string table (value table) in objectfile failed for unknown reasons. Probably due to corrupt file or filesystem. NUM is the number of bytes to read. Read() failed in SetSltCache() (NUM) Attempt to read from the source line table in objectfile failed for unknown reasons. Probably due to corrupt file or filesystem. NUM is the number of bytes to read. Read() failed in SetTyCache() (NUM) Attempt to read from the type table failed for unknown reasons. Probably due to corrupt file or filesystem. NUM is the number of bytes to read. Received signal NUM Debugger received non-handled signal NUM while waiting for a child process. It avoids handling certain signals, including SIGHUP, SIGQUIT, SIGTRAP, SIGKILL, SIGPIPE, SIGALRM, SIGTERM, SIGCLD, and SIGPWR, since they might reasonably be expected to terminate the debugger. RestoreRegs() failed SaveRegs() failed Ptrace(2) failed for unknown reasons while attempting to reset or save child process registers. Child process status is questionable. Seek() failed in AdrFLabel() (NUM) Seek() failed in InitLSTPd() (NUM) Seek() failed in LabelFAdr() (NUM) Seek() failed in ListLabels() (NUM) Seek() failed in UareaFLst() (NUM) Attempt to seek in the linker symbol table in objectfile failed for unknown reasons. Probably due to corrupt file or filesystem. NUM is the file offset of the seek. Seek() failed in SbFInp() (NUM) Attempt to seek in the linker name pool in objectfile failed for unknown reasons. Probably due to corrupt file or filesystem. NUM is the file offset of the seek. Seek() failed in SetCache() (NUM) Attempt to seek in the symbol table in objectfile failed for unknown reasons. Probably due to corrupt file or filesystem. NUM is the file offset of the seek. Seek() failed in SetIss() (NUM) Attempt to seek in the string table (value table) in objectfile failed for unknown reasons. Probably due to corrupt file or filesystem. NUM is the file offset of the seek. Seek() failed in SetSltCache() (NUM) Attempt to seek in the source line table in objectfile failed for unknown reasons. Probably due to corrupt file or filesystem. NUM is the file offset of the seek. Seek() failed in SetTyCache() (NUM) Attempt to seek in the type table failed for unknown reasons. Probably due to corrupt file or filesystem. NUM is the file offset of the seek. Signal actions are "i", "r", "s", "Q" "z" command given with improper arguments. See the quick reference (use the "help" command). Signal NUM unknown "z" command given with a modifier out of range of the defined signal numbers for your system. Use the "l z" command to list all known signals. Sorry, BSD Pascal does not provide field names You can't look up field names in programs compiled with that compiler. Sorry, you can't access a naked field Attempt to refer to a field by name without specifying the host struct (union, record, pointer, etc.). Normally you get an "Unknown name" error, not this one. Stack isn't that deep Attempt to set a breakpoint or view a procedure at a specified depth when the child process stack is not that deep. Use the "t" command to list the child process stack. String constant is missing ending " Token parsed as a string constant is missing a trailing double quote before end of the command line. String too large for buffer in SbSafe() (NUM) Debugger attempted to make a safe copy of some internal character string, typically a variable name or command line token, which was bigger than 1024 or 256 bytes (depending on version). Should never happen. NUM is the size of the string to be saved. String too long for assignment Attempted to assign a string over 1024 bytes to a FORTRAN CHAR*, Pascal string, or Pascal packed array of char. Subscript not valid type in BoundsFDntt() (NUM, NUM) Array bounds specifier symbol table entry is of the wrong type (not subrange, enumeration, or char). Probably due to a corrupt symbol table. Parameters are the kind and symbol table index of the bad symbol. TEXT signal; please try a different command. Debugger itself caught (and ignored) the signal described by TEXT. Most commonly a floating point exception due to looking at random bits as a floating point number. The -S option only applies to BSD or HP symbol tables The -u option only applies to System III symbol tables Your version of the debugger does not support these options. See the manual entry. This does not appear to be a struct or union Attempt to dump the contents of a data object which is not a struct (union, record). Some versions of the debugger try to dump it anyway and give a more arcane error, such as "Invalid field access". Too many subscripts Attempt to dereference an array with more dimensions than it's declared to have according to the symbol table. However, C language does allow you to dereference pointers in this manner. Two operands in a row Two operators in a row Expression handler detected an improper construct in an expression. See the manual entry. Type information overflow (more than 6 type qualifiers) Symbol table entries for a data object indicate that it has more levels of qualification (data-pointer, function-pointer, and/or array-dimension) than the debugger can handle internally, or you attempted to add a level (using "&") to an object already at the limit. There is no easy way to reference such data objects. Unknown command "CMD" (NUM) Debugger internal confusion; somehow it thinks a character (CMD, decimal value NUM) is a command not in the supported list. Normally you get "Unknown name or command" instead. Unknown display format in DispVal() (NUM) Debugger internal confusion; somehow the display format (NUM) got set to an unsupported value. Unknown global Variable specified with ":var" is not a recognized global variable name. Use "l g" to list all known global variables. Remember that no leading "_" is required on "var" unless actually part of the name. Unknown local Variable specified with "proc[.depth].var" is not a recognized local variable of "proc". Use "l proc" to list all known local variables of "proc". Remember that no leading "_" is required on "var" unless actually part of the name. Unknown name Unrecognized string (procedure or variable name) encountered in an expression. Unknown name or command "NAME" Unrecognized string (NAME) encountered at the beginning of a command. Unknown operator (NUM) Debugger internal confusion; somehow an unsupported operator (decimal value NUM) was pushed on the operator stack. Unnamed symbol type in NameFCurSym() (NUM, NUM) Debugger internal confusion; somehow an attempt was made to look up the name of an unnamed symbol table entry. Possibly due to a corrupt symbol table. Parameters are the kind and symbol table index of the bad entry. Unrecognized "l" command List command given with a second part which is neither a known procedure name nor a valid option. See the quick reference (use the "help" command). Usage: Debugger invoked improperly. Progname is the base part of the invocation pathname. See the manual entry. usage: M (t | c) [expr; [expr;...]] (up to 6 values) "M" command given improperly. See the manual entry. Value table too big in InitSymfile() (NUM) Value tables bigger than 2^23-1 (8388607) bytes are not supported, so the debugger can distinguish value table pointers from code and data pointers. In the very unlikely event you run into this, try relinking objectfile with one or more ".o" files recompiled non- debuggable. NUM is the actual size of the value table. WARNING: "end.o" was not linked with this program Special procedure "_end_" not found in the symbol table during initialization. /usr/lib/end.o is automatically linked for you on some systems if you give the "-g" option to the compiler front end. However, it might not be linked if you invoke the linker directly. Also, the symbol table might be corrupt. (If end.o is missing, string constants and some other values cannot be stored in the child process address space when required, resulting in a similar error at that time.) WARNING: "FILE1" cannot be the core file for "FILE2"; ignoring "FILE1" Header of FILE1 is not correct for a corefile, so it can't be the corefile for objectfile FILE2. Possibly corrupt file. WARNING: "FILE" does not appear to have line symbols When opening the sourcefile (FILE) associated with a procedure, no entries in the source line table could be found for the procedure. The procedure might not have any executable lines, or the symbol table or source line table might be corrupt. WARNING: "FILE1" is older than "FILE2"; ignoring "FILE1". Corefile (FILE1) modification time is older than objectfile (FILE2) modification time, so corefile is not opened (it's irrelevant). WARNING: "FILE1" is younger than "FILE2" Sourcefile (FILE1) modification time is newer than objectfile (FILE2) modification time, so sourcefile may not correspond to the code in objectfile. WARNING: Code is READ ONLY; you can't set breakpoints so you can't run. WARNING: Code is SHARED; you can't set breakpoints so you can't run. Either message, depending on the version, means that objectfile is set to a mode (read only or shared) which prevents the debugger from writing breakpoints into child process code in memory. Since an initial breakpoint is required when starting a child process, you can't do any useful debugging with one. (If you attempt to start a child process you probably get "Bad access".) On some systems you can modify objectfile without relinking. WARNING: Modifying the breakpoint signal! Use of "z" command to modify (or even just examine) the handling of SIGTRAP, the breakpoint signal. This signal is used by the debugger internally to control the child process. If you change the default settings, unpredictable things can happen. WARNING: Too few parameters WARNING: Too many parameters Attempt to call a debuggable procedure from the command line with a different number of parameters than specified in the symbol table. You can go ahead and call it anyway, which can lead to strange results depending on the language and the called procedure. Wrong symbol type in PROC() (NUM, NUM) Debugger internal procedure PROC called with a symbol table index (second NUM) of a symbol of the wrong kind (first NUM) to be handled by the procedure. Specific error depends on PROC, i.e. AdrFIsym: not a symbol with an address; CbFDntt: not a symbol which can be the element type of an array; IsltFIsym: not a symbol which points to a source line table entry; IsymFNextTqSym: not a symbol which is a qualifier type or points to a subtype; TyFHp: not a symbol which is a named data type; or TyFScanHp: not a symbol which is an unnamed data type. Possibly due to corrupt symbol table.