''ISO8859-1-x)( 9&`abc6d:+C+BIOW)u       ' E d v    !! !-!:!M!c !x+!!"!! 1!!"("1">#"p$-"%"&!"'!"( #) #3*.#T+#,[#-#.($/ $)0#$31 $W21$a3$4$$5$6$7$8$9%:%#;%@<%R=,%g>!%?+%@!%A<&B6&AC.&x&&@&!'#.'E$"'t''/'!'%((.&(J -(q ,( ( ( ) )();)N2)i")))))**4*R*f/*g?*4*+ +* +D!"+`""+#2+$;+',,=,,>',k$,&,!, - -" %-# %-I 1-o ?-+--. .;2.[1.,.0.:/Y/Y!/#/ /00,0B)0Z000 0 0 0 0 ;0 116#1P!1t1111 1 "1 2 $202U$2k22)22&2 3 #3 3A 3U 3j3k343 33$4 645$4l$4"4445 ,5 5M 5N (5O 5x 5y,5z%5555D516*6G>6r6'6$6#77<C7L  7 77777F7U8% *8{>8(899+9' ^9S9)99%9:::4 :O #:k !: : *:A:;0$;?0;d<;U;><(&>E>l>m >n > $> 6> 8??A?P?n?`?>@P@B[@5@LA%UAr6AATB(BsIB+B'C 3C: Cn&C CLC2DzD5AD!D E E Fs-GGGuGG*G=GH$HD Hb &H H H HH6IIIIJJ#J2JN J_ Ju 5Jv J J(JCK4KH9K}KK'K'K6L"LY~LoLcLeMcMNP NN OO(*OB$OmOO O6OPPP9PXPY Pw!P 1P HP Q5 QT QnQiQQQQQRR# R4 "RU "Rx 0R ,R RS /S 2S<So S!S"S%S1T3TF/TzTTT)TU&)U>Uh Ui!,Uj"!U#U$JU%7V&:VV':V(6V)@W*+WD+-Wp,<W-4W.5X/6XF0;X}15X2=X3?Y-44Ym5:Y6*Y7-Z8!Z69!ZX:Zz; Z<3Z=+Z>3[ ?*[@@.[kA1[BS[C<\ D-\]E&\F1\G>\H.]#I.]RJ:]K1]L6]M=^%N)^cO^P9^Q+^RD_S,_ST/_U"_V*_W!_X` Y`4Z `S[`_\`u]`^@`_7``7a!aaYbapc!ad+ae2af(bgb8hbib /b*c#-cN,c|.cc#cc c d -d& *dT 4dd)d1d|e@eee9e @f4 fu f f ffIf'g =gHghQ-h?iiB(iZiiiii#i jj j0 jC j[ jt "jjjj k'k k5kEk_#k`kkkkkk k k k k *ll0$l1lVlWlklllml"llllllll l l l l l lm2mmH*memmmmmmmmmmBmn#n n7!,nS"@n*n(n0o&oF2om:o ,o-p/p6'pfppp!p "p 'q -q: qh +qJq7qtv7xx|%k}T?/ f (+ T V }ScGFn<aZH#9>] F@!P"%#$%r&y'z(:d)Mğ*W+qE,Ʒ-|.-M/0{0ʬ18˞2a3X94̒5 6?7t8T9n:k};<$҆=ӫ>H?@݇A7߉BC LDXE(FGHIJxK|&LMlN "O3PQRkS,T6!U:XV8WXYZ[\Z]})^;_`#a%bV&c(d )we+f,Ug|,h)1{i?jC9kHlBIjmJnL?ohMZpNqRRrWSs,U8tVeuWvXwZ\x[yV[zZ\2{`|!e#}jE~ {)9j n{X~pd WZg  bc ,b/gEF#I\7st%tC 9t]1t!t"t,u=u;!uyu!"*u1u!v #v.'vR.vz#vv v v /w /w@ %wpw8w/w&x"x<&x_9x#x'x2y ;y?<y{+y2y?z%zW-z}$z z!z"z"{ {{%# -{4/{b*{{+}g$}7}   -:$ h} (4 ] i %#&O! 22J ^3k $ "   &/DUt"!03du!"'#$%%D&X'*m()*+,-!./.-0 \16f2-3+4+5+#6+O7+{89:-;-<* =?K>"?;@ A, BN8CDEFG HI J)KBL"M @NJO_P3oQ' p$_" 2 !L n D Icannot step through protected code at 0x%llx cannot step through breakpoint at 0x%llx 1283-240 error %d trying to step processprogram exited program exited with code %d could not locate trace table from starting address 0x%llx[internal error: nil function containing parameter %s][internal error: nil paramlist for function containing %s][internal error: bad size %d in pushretval] Invalid opcode.[bad size in extractField -- word assumed] Bit(s)FieldMeaningFailure due to context switchIllegal System Call in Transactional ModeIllegal FP operation performedProcess was terminatedIllegal VMX operation performedThread was forkedIllegal VSX operation performedProcess-thread was terminatedFacility Unavailable InterruptPrgram was exec'dFailed due to CPU sparingUnsupported libc call madeProcess-thread was suspendedM:N pthread context switchFailed due to signal deliveryFailed upon start of threadKDB was enteredFailure CodeFailure PersistentFailure is persistentFailure is transientDisallowedInstruction of access type is not permittedNesting OverflowMaximum transaction level exceededFootprint OverflowTracking limit for transactional storage exceededSelf-induced ConflictSelf-induced conflict occurred in Suspended stateNon-Transactional ConflictNon-transactional access by another processorTransaction ConflictConflict with another transactionTranslation Invalidation ConflictConflict with a TLB invalidationImplementation Specific ConflictFailed due to implementation specific conflictInstruction Fetch ConflictAn instruction fetch was performed from a block that was previously written transactionallyAbortExecution of TM instruction caused AbortSuspendedFailure recorded in Suspended StatePrivilegeDuring Failure process-thread privilege state wasFailure SummaryFailure recording has been performedTFIAR (in)exactTFIAR is exactTFIAR is inexactRollback Only TransactionROT is initiatednon-ROT tbegin. is initiatedTransaction LevelIllegal TEXASR valueFailed due to delivery of synchronous signalReceived bad thing Exception typeFailed due to invalid instruction executionFailed due to alignment interruptTransaction has failed due to late binding of floating pointTransaction has failed due to processor dispatch cycleTransaction has failed due to LPAR terminationcannot take address of registerexpected variable, found "1283-245 Cannot display evaluation tree for unknown operation %dtoo many arguments to type renamecannot take address of an enumeration constant1283-241 delete of non-symbol '%s'"%s" is not currently defined[internal error: unexpected nil frame for "%s"]1283-242 address: bad symbol "%s"could not find link to type referencecould not resolve referencedynamic bounds not currently available[internal error: unexpected array bound type]1283-243 missing size information for recordexpected range for set base type1283-244 size: bad class (%d)cannot compute size of a %s " is not a pointer" is improper typeoperation not defined on "non-numeric operand for division or exponentiationnon-integer operand for div or mod"%s" is not defined in Too many subscripts." is not an arrayToo many subscripts for "Not enough subscripts for ", expected boolean expression"%s" is not definedelements of a set must be of the same base typeelements of a set must be of type char, int, or scalar constantOperation not defined on edited or alpha data types.%1$s"%2$s" is not defined in %1$s"%2$s" is not defined"%1$s" is not %2$sfield in missing size information for classInvalid wildcard expression given Operation between types dfp and bfp is not allowedexp operation not defined on decimal floating point numbers1283-228 expected char '%c', found '%s'[internal error: unknown constant type '%c']1283-229 bad input on type "%s" at "%s"1283-230 too many types in file "%s"1283-231 bad input on tag "%s" at "%s"missing ';' after type attributes1283-232 index("%s", ':') failed1283-233 bad import symbol entry '%s'1283-234 bad opaque symbol entry '%s'1283-235 consPic: unknown cobol storage type '%c'1283-236 consPic: cobol picture definition had no internal size1283-237 consPic: expected edit description1283-238 consPic: wrong size edit description1283-014 consPic: malloc error!1283-239 consPic: expected cobol decimal alignmentexpected access type 'i', 'o', or 'u', saw '%1$s'expected member function types, found '%1$s'expected member function attribute, found '%1$s'expected member attribute 's', 'p', 'r' or 'b', found '%s'1283-016 type limit (%d) exceeded in file "%s". Use the -t option to increase type limit.Unexpected end of string for "%s"1283-246 string_alloc: malloc errorcould not read "%s" line number must be positive "%s" has only 1 line "%s" has only %d lines second number must be greater than first cannot read "%s"no source for "%s"no source file invalid regular expression no match warning: could not read command file "%s", action ignored. alias expansion too largemissing ')' in macro callnot enough parameters in macro calltoo many parameters in macro callmissing actuals for macro^ unrecognized command^ syntax errornon-terminated stringcannot open %sunreasonable input nesting on "%s"argument too longFrame information in error at 0x%llxprogram is not activeCould not determine current functionno current functionnot that many levelsFrame information in error, %d levels up.cannot find _exitNesting of "call" commands is illegal."%s" is not a procedure or functiontoo many parameterstype mismatch for %snot enough parameters to %s returns successfully "%s" has no return value. Use call instead of print."this" pointer evaluates to nil."this" object not required!Cannot call a pure virtual function.Core file "%s" is older than current program (ignored)1283-013 could not attach to pid %d Waiting to attach to process %d ... Attaching to process from exec... 1283-225 cannot forkwarning: cannot execute %s program is not active1283-226 error %d trying to continue processUnreadable instruction at address 0x%llxstore: could not write instruction at 0x%llxstore: could not write data at 0x%llxCore file "%s" program "%s" does not match current program (ignored)Core file "%s" is not a valid core file (ignored)%s does not contain a stack (core ignored)Invalid trace table. Unreadable instruction at address 0x%llxInvalid module number %d Invalid symbol type for this operation Could not locate module for address Could not locate module for symbol Invalid pid %d The alternate library %s does not match the running copy. (Ignored) entering %s leaving %s *** expression too large ***record has no fields1283-224 unable to evaluate floating point variable of length %d bytesThe conversion between code set %s and code set %s is not supported by implementation1283-223 unexpected class %d for parameterinternal error: expected range or enumerated base type for setsubscript %lld out of range [%lld..%lld]set member out of rangemust specify index when printing space type1283-011 nesting depth limit (%d) exceeded. Use the -d option to increase nesting depth limit.1283-010 cannot open member %s in file %s%1$s is newer than %2$s1283-221 nesting depth underflow (%d)1283-012 cannot open %sno source compiled with -gno source compiled with -g warning: stab entry unrecognized: 1283-222 chain not nil in deffuncglobal %s ignored1283-017 invalid value for include file %sunsupported binder stabstring compaction level %d, resetting to 1cannot open %s"%s" has changed since core creation"%s" has changed since core creation (discarded)Unable to open stab file %s. Some info may not be available.The stabfile %s doesn't match with that of executable. Some info may not be availableUnable to access the stab file. Some info may not be available1283-218 unexpected class %d for parameter1283-219 expected range or enumerated base type for setsubscript value %d out of range [%d..%d]subscript %d out of range [%d..%d][internal error: expected array in evalaref]1283-220 initial Modula-2 type number too large for '%s'source file "%s" not compiled with -gdbx is initializing ... reading symbolic information ...[using memory image in %s] 1283-004 missing directory for -I1283-005 missing command file name for -c1283-006 missing proc id number for -a1283-008 extraneous argument %sSuccessfully attached to %s. Could not determine object file nameenter object file name (default is `%s', ^D to exit): 1283-002 exiting due to failure to determine object filecannot read %s1283-206 cannot open /dev/mem1283-009 unknown option '%c'Type 'help' for help. Directory containing %s could not be determined. Apply 'use' command to initialize source path. 1283-007 Nesting depth limit was not specified after -d optionSpecified nesting limit could not be interpreted. Nesting limit used will be 25.Specified nesting limit is greater than maximum of 32767. Nesting limit used will be 32767.1283-015 Type limit was not specified after -t optionSpecified type limit could not be interpreted. Type limit used will be 5000.Specified type limit is greater than maximum of 32767. Type limit used will be 32767.enter object file name (default is `%s', %s to exit): Unable to open object file %s.The specified alternate object file %s does not match the running process. (Ignored)missing alternate debug file name for -BThe alternate object file can be specifed only while attaching. (Ignored)Object file %s is overwritten (Ignored)... Object file %s is deleted (Ignored)... (Use -B flag to specify an alternate object file). %s is not aliased"%s" is a program symbol -- use assign%s is not setInvalid value Usage: set $mapformat = {"abbr", "normal", "raw", "verbose"} Valid values are "function", "module", and "none" Invalid value Usage: set $instructionset = {"pwr", "pwrx", "ppc", "601", "603", "604", "970", "com", "any", "default"} Invalid value Usage: set $mnemonics = {"pwr", "ppc", "default"} A valid code set must be providedInvalid value Usage: set $instructionset = {"pwr", "pwrx", "ppc", "601", "603", "604", "970", "pwr6", "pwr7", "com", "any", "default"} Invalid value Usage: set $compact_bt_ident= where is a positive integer between 4 and 128. example : 'set $compact_bt_ident=16' 'set $compact_bt_ident' would imply the default = 8. Invalid value Usage: set $compact_bt_string= where is a positive integer between 4 and 128. example : 'set $compact_bt_string=16' 'set $compact_bt_string' would imply the default = 8. Error: element size is %d characters, not %d source file "%s.f"executable file "%s"class %s in fortran_printdecl1283-215 unexpected class %d for parameter1283-216 cannot evaluate "%d" byte logical, complex, or real1283-217 printval: bad class %ddo not know how to print a %sunknown type in fortran printintdynamic bounds not currently availablesubscript out of rangedata type "%s"$vardim must be positiveInvalid value Usage: set $instructionset = {"pwr", "pwrx", "ppc", "601", "603", "604", "970", "pwr6", "pwr7", "pwr8","pwr9" , "com", "any", "default"} Attempt to resolve "wildcards" in run or rerun failed.too many argumentsmultiple input redirectscannot continue executionprogram terminated by signal %dprogram exitedprogram exited with code %d%s is not activeno place to return toFailed establishing calling point (libg.a not linked) Entering debugger ... no process to write tocannot write to process (address 0x%llx)application forked, child pid=%d, process stopped, awaiting input 1283-003 Could not reattach to child process on forkdebugging child, pid=%d, process stopped, waiting input 1283-001 cannot read "%s"Address out of bounds for text section.Address out of bounds for data section.Unable to locate linkage symbol for out-of-module callsignal "%1$s" unknownNon-breakpoint trap instruction with handler encountered (set $ignorenonbptrap to disable future notification of such events) cannot run/rerunProcess %d may have failed a transaction - $texasr , $tfiar, $tfhar are valid and may be inspected Process %d may have performed a transaction - $texasr, $tfiar, $tfhar are valid and may be inspected Process %d is in Transactional State - debugging efforts through dbx may result in repeated transaction failure or undefined behavior Process %d is in Suspended State - debugging efforts through dbx may result in repeated transaction failure or undefined behavior non-positive repetition countbad print format "%s"first address larger than second"%s" terminated normally "%s" terminated abnormally (exit code %d) execution completed (exit code %d) execution completed Instruction is valid on: %s Unable to access address 0x%llx1283-213 cannot find symbol for program counter ($pc) no executable code at line 1283-214 bad ancestry for "%s"no breakpoints found at line no breakpoints found at address hardware watchpoint not availablecannot create new event in conflict with event %uinvalid region for trace (maximum size for address 0x%0*llx is %u bytes)Processing deferred event# %d Remaining tskip counts: count of [%u] is already %u unknown event [%u] 1283-207 stack underflow"%s" is not activecannot evaluate a %sreference through nil pointererror: division by 0error: mod by 0cannot read "%s"Symbols are not folded (mixed). Symbols are folded to lower case. Symbols are folded to upper case. Symbols are folded based upon current language. run or rerun allowed only on initial processunknown event %ld1283-208 Could not alter multi-processing mode.1283-209 Could not detach from process. Use quit.1283-210 eval: bad op %dexpression too large to evaluate1283-211 bad size %d in pushsmall[internal error: nil frame for %s][internal error: size %d in popsmall]expression too large to trace (limit is %d bytes)%s is an unusual operand for examining modificationUnable to allocate memory for character pointer$frame must be an addressno source lines for "%s"line numbers must be positive second number must be greater than first No file to move within Line specified is not within range of %s No assembly code for that source line number%s is not a procedure or functionprogram is not executableGoto address is not within current function. (set $unsafegoto to override)run - begin execution of the programprint - print the value of the expressionwhere - print currently active proceduresstop at - suspend execution at the linestop in - suspend execution when is calledcont - continue executionstep - single step one linenext - step to next line (skip over calls)trace - trace execution of the linetrace - trace calls to the proceduretrace - trace changes to the variabletrace at - print when is reachedstatus - print trace/stop's in effectdelete - remove trace or stop of given numberscreen - switch dbx to another virtual terminalcall - call a procedure in programwhatis - print the declaration of the namelist , - list source linesregisters - display register setquit - exit dbx%s: file already exists, use ">!"cannot create %s1283-212 standard out dup failed [unset $noflregs to view floating point registers]Subarray of pointer to array not supported.Cannot set a breakpoint in a pure virtual function.Cannot assign a value to a const variable.Cannot assign to a pointer to member variable.Cannot trace an uninitialized reference variable.Goto address is not within current function or block. (set $unsafegoto to override)Usage: "thread [run | ready | susp | term] [-]" takes no id Usage: "thread current" takes zero or one id Usage: "thread run_next" takes one id Usage: "condition { wait | nowait }" takes no id Usage: "mutex { wait | nowait | lock | unlock }" takes no id thread - list existing threadsmutex - list existing mutexescondition - list existing condition variablesattribute - list existing attributesquit - exit dbx (program terminated)detach - exit dbx without terminating programCannot assign to a subarray of variables.Cannot trace or stop a %s.dbx multproc fails. dbx continued with multproc disabled dbx subcommand screen fails. dbx continued screen subcommand can only be invoked from the originating process. screen subcommand can only be invoked once. Usage: "barrier { wait | nowait }" takes no id Current session is not a core file [unset $novregs to view vector registers] [vector registers are not valid]unknown command %ldcannot call procedure/functioncannot jump"%1$s" is not loaded. Creating deferred event: Threads are not active The thread $t%llu is not active or is not a system-scope thread The current thread $t%llu is not a system-scope thread The running thread $t%llu is not a system-scope thread $t%llu has terminated $t%llu has changed its scope The running thread has been held "%s" thread-local variable is not allocated [unset $novsregs to view vector scalar registers] [vector scalar registers are not valid] [VSRs are a superset of legacy FRs and VRs The legacy alias is shown in () Note that the FR aliases correspond to the low 64-bits only.]source file: %sno source file for 0x%LLXMemory allocation error in mangle_member_name()Memory allocation error in buildFuncList()Memory allocation error in SymList insertsl()Memory allocation error in fix_mf_arg_list()Memory allocation error in printClassMembers()unexpected missing type informationsource file "%s.C"executable file "%s"static data member %1$s not defined; removingmember function %1$s not defined; removingRTTI not present; Dynamic type can not be determinedUnable to access address 0x%llx from coreCore file "%s" is not a valid core file (ignored)The core file is truncated. You may need to increasethe ulimit for file and coredump, or free some space on the filesystem.Unable to access address 0x%llx from missing dependent module %s[inaccessible: missing %s][untrusted: %s]The core file does not contain the information requested.The core file is not a fullcore. Some info may not be available. Process Name: %s Version: %s Flags: %s Signal: Process Mode: %s %s section of the core file is not valid. Some info may not be available.Core file "%s" is not a valid core file[Object file is not specified. Using "%s" as an object file] Object file is not specified, and the object file "%s" mentioned in the core file doesn't exist in the current directory or doesn't match with the core file (ignored). Some info may not be available.Object file is not specified, and couldn't able to retrieve the object file name from core file. Some info may not be available.Core file "%s" is older than current program.Core file "%s" for program "%s" does not match current program.Mapping not available. invalid core path specification for '-p'incompatible sizesincompatible typesinvalid signal number"%s" is not a blockexpected a symbol, found ""%s" is not a procedure or function"%s" is empty" not call-ablesymbol not definedunexpected "at" or "in"cannot trace expressionsmissing variable to watchexpected variable to watch, found expected variable, found expected subprogram, found "%s" is not a subprogrammissing lineexpected source line number, found "%t"missing addressexpected address, found "unexpected missing type informationsource file "%s.c"executable file "%s"1283-201 printtype: class %s%ld byte real%d byte real unresolved tag %s(class %d)1283-202 unexpected class %d for parametersubscript must be integer-compatible" is the wrong typesubscript out of rangebad decimal float size %ldsource file "%s.cbl"executable file "%s"no range for an OCCURSTYPEREF in cobol(class %d)out of memory no more memory while creating a cobol level record1283-203 printtype: class %s1283-204 unexpected class %d for parameter1283-205 printval: bad class %dsubscript out of range%1$cD %2$s Record Size %3$d. Organization is %4$s, Access is %5$s. requires %1$d or %2$d subscripts. requires %d subscript(s). Subarrays in COBOL not currently supported. Operation results in an integer overflow or underflow condition.Unexpected type name as function argument.Failed to successfully read window size.Window too small to select C++ objects. Enlarge.Too many function calls in expression.Function(s) contain compiler generated parameters.Given argument list fails to match any definition of %1$s.Ambiguous base class "%1$s"; please qualify.Please qualify ambiguous reference to "%1$s". does not contain a definition of class "%1$s"."%1$s" is not a nested class of "%2$s"." is not a class."%1$s" is not a class."%1$s" is not definedToo few arguments to type rename.Too many arguments to type rename.The current module is not a C++ module.'s type is not "%1$s" or derived from "%2$s"." is not a pointer to a member." does not point to member of class "%1$s". Type "help " or "help " for help on a command or topic. Execution subcommands: run - begin execution of the program rerun - begin execution of program with previous arguments cont - continue execution step - single step one line next - step to next line (skip over calls) return - continue until a return to specified procedure is reached skip - continue execution ignoring next breakpoint goto - change execution to specified source line stepi - single step one instruction nexti - step to next instruction (skip over calls) gotoi - change execution to specified address up - move current function up the stack down - move current function down the stack where - print currently active procedures call - execute a procedure in program print - execute a procedure and print return code catch - trap the signal before it is sent to program ignore - stop trapping the signal before it is sent to program detach - exit dbx without terminating program quit - exit dbx (program terminated) When displaying variables and expressions, dbx resolves names first using the static scope of the current function. The dynamic scope is used if the name is not defined in the first scope. If static and dynamic searches do not yield a result an arbitrary symbol is chosen and dbx prints the message [using ]. The is the name of an identifier qualified with a block name. Override the name resolution procedure by qualifying an identifier with a block name. Source files are treated as modules named by the file name without the language suffix (such as, the .c suffix on a C language program) Expressions are specified with a subset of C and Pascal syntax. A prefix * or a postfix ^ denotes indirection. Use [ ] or ( ) to enclose array subscripts. Use the field reference operator . (period) with pointers and records. This makes the C operator "->" unnecessary (although it is supported). Types of expressions are checked; the type of an expression may be overridden by using "type-name(expression)". When there is no corresponding named type use the special construct &type-name to represent a pointer to the named type. "$type-name" and "$$tag-name" can be used to represent a pointer to a named type or enum, struct or union tag. The following operators are valid in expressions: Algebraic +, -, *, / (float), div (integral), mod, exp Bitwise -, |, bitand, xor, ~, <<, >> Logical or, and, not, ||, && Comparison <, >, <=, >=, <>, !=, =, == Other sizeof File subcommands: use - set directories to be searched for source file list - list lines of current source file file - change or display current source file func - change or display current function search(/?) - search forward or backward in current file for a pattern edit - invoke an editor on specifed file or function move - change next line to be displayed by list command Machine level subcommands: display(/) - display contents of memory cleari - remove all stop/trace points at given address listi - list instruction from application stopi - set a breakpoint at a specified address tracei - turn on instruction tracing stepi - single step one instruction nexti - step to next instruction (skip over calls) registers - display register set gotoi - change execution to specified address map - display address maps and loader information stophwp - set a hardware watchpoint stop tracehwp - set a hardware watchpoint trace Basic dbx command usage: run - begin execution of the program print - print the value of the expression where - print currently active procedures stop at - suspend execution at the line stop in - suspend execution when is called cont - continue execution step - single step one line next - step to next line (skip over calls) trace - trace execution of the line trace - trace calls to the procedure trace - trace changes to the variable trace at - print when is reached status - print trace/stop's in effect delete - remove trace or stop of given number screen - switch dbx to another virtual terminal call - call a procedure in program whatis - print the declaration of the name list , - list source lines registers - display register set quit - exit dbx The following "set" variables have special meanings: $catchbp When set, dbx catches breakpoints during execution of the next command. $frame Setting this variable to an address alters dbx's idea of the current stack frame. $expandunions Causes dbx to display values of each part of variant records or unions. $hexin $octin When set, dbx interprets addresses in hexadecimal or octal. $hexchars $hexints $hexstrings When set, dbx prints characters, integers or character pointers in hexadecimal. $noargs When set, dbx omits arguments from subcommands, such as where, up, down, and dump. $noflregs When set, dbx omits the display of floating-point registers from the registers subcommand. $novregs When set, dbx omits the display of vector registers from the registers subcommand. $octints When set, dbx prints integers in octal. $ignoreifhandler When set, dbx suppresses notification of signals which have a registered handler. $ignoreload When set, dbx ignores load(), unload(), or loadbind() subroutines performed by your program. $ignorenonbptrap When set, dbx suppresses notification of non-breakpoint trap instructions that trigger when a SIGTRAP handler is registered. $instructionset Specifies the default disassembly mode. To change the value, the user should type 'set $instructionset = ""'. If the $instructionset variable is unset, it will behave as if the value was "default". The following are the valid values for $instructionset: "default" - Disassemble using the instruction set for the hardware architecture dbx is running on. "com" - Disassemble using the instruction set that is common between Power and PowerPC architectures. The mnemonics will default to PowerPC mnemonics. "pwr" - Disassemble using the instruction set for the RS1 implementation of the Power architecture. The mnemonics will default to Power mnemonics. "pwrx" - Disassemble using the instruction set for the RS2 implementation of Power architecture. The mnemonics will default to Power mnemonics. "ppc" - Disassemble using the instruction set for the PowerPC architecture. The mnemonics will default to PowerPC mnemonics. "601" - Disassemble using the instruction set for the 601 implementation of PowerPC architecture. The mnemonics will default to PowerPC mnemonics. "603" - Disassemble using the instruction set for the 603 implementation of PowerPC architecture. The mnemonics will default to PowerPC mnemonics. "604" - Disassemble using the instruction set for the 604 implementation of PowerPC architecture. The mnemonics will default to PowerPC mnemonics. "970" - Disassemble using the instruction set for the 970 implementation of PowerPC architecture. The mnemonics will default to PowerPC mnemonics. "any" - Disassemble using any valid instruction from either Power or PowerPC architecture. The mnemonics will default to PowerPC mnemonics $java When set, also sets the following variables, placing dbx in a mode to debug Java applications. When unset, also unsets the following variables: $ignorenonbptrap Suppresses notification of trap instructions generated by the Java Just-In-Time (JIT) compiler. $listwindow Specifies the number of lines to list and listi commands. $mapaddrs When set, dbx starts address mapping, useful for kernel debugging. $mapformat Specifies the default output format for the map subcommand. To change the value, the user should type 'set $mapformat = ""'. If the $mapformat variable is unset, it will behave as if the value was "normal". The following are the valid values for $mapformat: "abbr" - Map output will consist of a single line containing the entry number, module name, and member name. "normal" - Map output will consist of the entry number, module name, member name, text origin, text length, data origin, data length, and file descriptor. "raw" - Map output will consist of a single unformatted line containing the following space-separated fields: entry number, module name with optional member name, text origin, text end, text length, data origin, data end, data length, and file descriptor. "verbose" - Map output will consist of the entry number, module name, member name, text origin, text end, text length, data origin, data end, data length, and file descriptor. $menuwindow Specifies the number of lines to list when prompting users for choices. $mnemonics Specifies the set of mnemonics used for disassembly. To change the value, the user should type 'set $mnemonics = ""'. If the $mnemonics variable is unset, it will behave as if the value was "default". The following are the valid values for $mnemonics: "default" - Disassemble using the mnemonics which most closely match the specified instruction set. "pwr" - Disassemble using the mnemonics for the Power architecture. "ppc" - Disassemble using the mnemonics for the PowerPC architecture. $print_fullname When set, dbx prints the fully-qualified identifier, even in cases where there is no apparent ambiguity. $print_mangled When debugging c++ code, setting this variable causes dbx to print mangled identifiers. $repeat When set, dbx repeats the previous command if no command was entered. $sigblock When set, dbx blocks signals to your program. $showbases When set, dbx displays base classes of C++ class types. $showblocks When set, dbx prints unnamed blocks in location output. $stepignore Specifies the behavior of the "step" subcommand on a source line calling another routine with no debugging information. To change the value, the user should type 'set $stepignore = ""'. If the $stepignore variable is unset, it will behave as if the value was "function". The following are the valid values for $stepignore: "function" - dbx will behave as if subcommand "next" was issued. "module" - if function is in load module with no debug information (such as a system library), dbx will behave as if subcommand "next" was issued. "none" - dbx will "stepi" until it reaches an instruction with source information. $unsafecall $unsafeassign $unsafegoto $unsafebounds Turn off type checking for calls, assignments, goto and array bounds checking. $vardim Specifies the dimension length to use when printing arrays with unknown bounds %s is not a known help topic or command alias alias alias alias "" alias ( ) "" When commands are processed, dbx first checks to see if the word is an alias for either a command or a string. If it is an alias, then dbx treats the input as though the corresponding string (with values substituted for any parameters) had been entered. Alias with no arguments prints the alias definition list. assign = Assign the value of the expression to the variable. call ( ) Execute the object code associated with the named procedure or function See also: print case case mixed case lower case upper case default Set character case sensitivity. Case with no arguments prints the current case sensitivity. catch catch catch Catch with no arguments prints all signals currently being caught. If a signal is specified, dbx start trapping the signal before it is sent to the program. This is useful when a program being debugged has signal handlers. A signal may be specified by number or name. Signal names are by default case insensitive and the "SIG" prefix is optional. By default all signals are caught except SIGHUP, SIGCHLD, SIGALRM and SIGKILL. ignore ignore ignore Ignore with no arguments prints all signals currently being ignored. If a signal is specified, dbx stops trapping the signal before it is sent to the program. A signal may be specified by number or name. Signal names are by default case insensitive and the "SIG" prefix is optional. By default all signals are trapped except SIGHUP, SIGCHLD, SIGALRM and SIGKILL. cont cont cont Continue execution from where it stopped. If a signal is specified, the process continues as though it received the signal. Otherwise, the process is continued as though it had not been stopped. delete delete all The traces or stops corresponding to the given numbers are removed. The numbers associated with traces and stops can be printed with the "status" command. up up down down Move the current function, which is used for resolving names, up or down the stack levels. The default is one. dump [ > ] dump . [ > ] dump [ > ] dump [ > ] Print the names and values of variables in the given procedure, or the current one if none is specified. If the procedure given is '.', then all active variables are dumped. If a module name is given, all variables in the module are dumped. edit edit edit Invoke an editor on or the current source file if none is specified. If a procedure or function name is specified the editor is invoked on the file that contains it. The default editor is the vi editor. The default can be overridden by setting the environment variable EDITOR to the name of the desired editor. file file Change the current source file name to . If none is specified then the current source file name is printed. func func Change the current function. If none is specified then print the current function. Changing the current function implicitly changes the current source file to the one that contains the function; it also changes the current scope used for name resolution. clear Remove all breakpoints and traces at a given line number. See also: delete cleari
Remove all breakpoints and traces at a given address. See also: delete goto goto "" : gotoi
Change the program counter to
or an address near . The variable $unsafegoto must be set if a goto out of the current function is desired. help [> ] help [> ] help [> ] Print information about command or topic. (The string describing a topic may be abbreviated.) Long messages can be paged using the default "pg" alias. For example: "pg (help set_variables)". list [ [, ]] list List the lines in the current source file from the first line number to the second inclusive. If no lines are specified, the next 10 lines are listed. If the name of a procedure or function is given lines n-k to n+k are listed where n is the first statement in the procedure or function and k is defined by $listwindow listi listi [
[ ,
]] listi at listi List the instructions from the current program counter location or given address, line number or procedure. The number of instructions printed is controlled by the dbx internal variable $listwindow. next next Execute up to the next source line. If a count is supplied execute the next count source lines. The difference between this and "step" is that if the line contains a call to a procedure or function the "step" command will stop at the beginning of that block, while the "next" command will not. nexti nexti Single step as in "next", but do a single instruction rather than source line. If a count is supplied execute the nexti count instructions. print [, ] print () Prints the value of specified expression. Values of general purpose registers and floating point registers can also be printed using this command. "print ()" executes the object code associated with the procedure and prints the return value. Names are resolved first using the static scope of the current function, then using the dynamic scope if the name is not defined in the static scope. If static and dynamic searches do not yield a result, an arbitrary symbol is chosen and the message "[using ]" is printed. The name resolution procedure may be overridden by qualifying an identifier with a block name, e.g., "module.variable". For C, source files are treated as modules named by the file name without ".c" prompt prompt "string" Displays the dbx prompt, or changes prompt to "string". quit Exit dbx (program terminated). registers Print the contents of all general purpose registers, system control registers, floating-point registers, vector registers, and the current instruction register. To display floating-point registers, use the "unset $noflregs" dbx subcommand. To display vector registers, use the "unset $novregs" dbx subcommand Registers can be displayed or assigned to individually by using the following predefined register names: $r0 through $r31 for the general purpose registers $fr0 through $fr31 for the floating point registers $sp, $iar, $cr, $link for, respectively, the stack pointer, the program counter, condition register, and the link register. Vector registers can be displayed or assigned individually by vector element type using the following predefined register names: $vr0 through $vr31, for vector registers of type vector int $vr0c through $vr31c, for vector char $vr0s through $vr31s, for vector short $vr0f through $vr31f, for vector float $vrsave for the vrsave special purpose register $vscr for the vector status and control register Assigning a vector register can either be done a whole register at a time, for example, assign $vr0 = $vr31, or must be done an individual element at a time, using array subscripts. For example, to assign the third float element of vr15, assign $vr15f[2] = . To assign the sixteenth character element of vr30, assign $vr30c[15] = . run [] [< ] [> ] [>> ] [>! ] [2> ] [2>> ] [>& ] [>>& ] rerun [] [< ] [> ] [>> ] [>! ] [2> ] [2>> ] [>& ] [>>& ] Start executing the object file, passing arguments as command line arguments; < or > can be used to redirect input or output in a shell-like manner. When "rerun" is used without any arguments the previous argument list is passed to the program; otherwise it is identical to run. return return Continue until a return to is executed, or until the current procedure returns if none is specified. set set = The set command defines values for dbx variables. The names of these variables cannot conflict with names in the program being debugged, and are expanded to the corresponding expression within other commands. Use "unset" to remove a set variable definition. See also "help set_variables" for definitions of predefined set variables. sh sh Pass the command line to the shell for execution. The SHELL environment variable determines which shell is used. The default is the sh shell. If no argument is specified, control is transferred to the shell. source Read dbx commands from the given file. status [> ] Display the currently active trace and stop commands. step step Execute one source line. If a count is supplied, execute the next count source lines. The difference between this and "next" is that if the line contains a call to a procedure or function the "step" command will enter that procedure or function, while the "next" command will not. See also: set_variables $stepignore stepi stepi Execute a single instruction. If a count is supplied, execute the next count instructions. stop if stop at [if ] stop in [if ] stop [if ] stop at [if ] stop in [if ] stop on load [""] [if ] stop on load ["()"] [if ] Stop execution when the given line is reached, procedure or function entered, variable changed, module loaded or unloaded, or condition true. stopi if stopi
[if ] stopi at
[if ] stopi in [if ] stopi
in [if ] "stopi at
" stops execution when the given
is reached. "stopi
" stops execution when the value located at the given
changes. unalias Remove the alias for . unset Remove the definition for . use use { + | | '[' = ']' } ... Set the list of directories to be searched when looking for source files. If no argument is specified, the current list if directories to be searched is displayed. whatis Print the declaration of the given name. where [> ] Print out a stack trace of the currently active procedures and functions. whereis Print the full qualification of all symbols whose name matches . which Print the full qualification of the given . Full qualification of a symbol is its name plus names of its outer blocks. trace [in ] [if ] trace [if ] trace [in ] [if ] trace [in ] [if ] trace at [if ] trace on load [""] [if ] trace on load ["()"] [if ] Have tracing information printed when the program is executed. A number is associated with the command so that tracing can be turned off with the delete command. tracei [
] [if ] tracei [] [at
] [if ] Turn on tracing using a machine instruction address. See also: trace screen Switch dbx to another virtual terminal. Program continues to operate in the window in which it originated. no help available for %s detach detach detach Continues execution from where it stopped without debugger control. If a signal is specified, the process continues as though it received a signal. Otherwise, the debugger will exit, but the debugged process shall continue. move Change the next line to be displayed by the list command to source_line_number skip [] Continues execution of the program where it stopped, ignoring the next breakpoint. If "num" is supplied, ignore the next "num" breakpoints. /[/] ?[?] Search (respectively) forward or backward in the current source file for the given . Both forms of search wrap around. The previous regular expression is used if no regular expression is given to the current command.
,
/ [] [> ]
/ [] [] [> ] Display contents of memory starting at the first
up to the second
or until items are printed. If the address is ".", the address following the one most recently printed is used. The mode specifies how memory is to be printed; if it is omitted the previous mode specified is used. The initial mode is "X". The following modes are supported: i print the machine instruction d print a short word in decimal D print a long word in decimal o print a short word in octal O print a long word in octal x print a short word in hexadecimal X print a long word in hexadecimal b print a byte in octal c print a byte as a character h print a byte in hexadecimal s print a string (terminated by a null byte) f print a single precision real number g print a double precision real number q print a quad precision real number lld print an 8 byte signed decimal number llu print an 8 byte unsigned decimal number llx print an 8 byte unsigned hexadecimal number llo print an 8 byte unsigned octal number DBX Startup Options: dbx [-a ProcessID] [-c CommandFile] [-d NestingDepth] [-I Directory] [-p [OldPath=NewPath:... | File]] [-u] [-x] [-F] [-L] [-r] [ObjectFile [CoreFile]] -a ProcessID Attach to specified process -c CommandFile Run dbx subcommands in specified file first -d NestingDepth Set limit for nesting of program blocks -I Directory Include Directory in list of directories searched for source files -p OldPath=NewPath Substitute library path for core examination File Read library path substitutions for core examination from File -u Prepend file name symbols with an '@' -x Strip postfix '_' from FORTRAN symbols -F Read all symbols at start-up time -L Keep linkage symbols -r Run object file immediately Breakpoint/Trace subcommands: stop - set breakpoint in program trace - set trace in program status - print active breakpoints and traces delete - remove traces or breakpoints of given numbers clear - remove all breakpoints and traces at given line stopi - set a breakpoint at a specified address tracei - turn on instruction tracing cleari - remove all breakpoints and traces at given address Data/Variable subcommands: print - print the value of the expression display(/) - display contents of memory dump - display names and values of variables in procedure assign - assign a value to a variable whatis - print declaration of specified name which - print full qualification of specified name whereis - print full qualification of all symbols with specified name set - define a value to a non-program variable unset - delete a non-program variable Environment subcommands: alias - display and assign aliases for dbx subcommands unalias - remove an alias prompt - change dbx prompt to specified string screen - open virtual terminal for dbx command interaction case - change the way in which dbx interprets symbols help - display help for specified subcommand or topic multproc - enable and disable multiprocess debugging sh - pass a command to shell for execution source - read dbx commands from a file set - change a value to a dbx environment set variable unset - delete a dbx environment set variable use - set directories to be searched for source file catch - trap the signal before it is sent to program ignore - stop trapping the signal before it is sent to program Debugging application program with threads: No special option is needed for debugging application program with threads; however, a full core file is required for thread related subcommands when debugging a core file. DBX provides five commands ("thread", "mutex", "condition", "rwlock" and "attribute") for listing thread related objects and attributes. Users can also reference individual thread related objects using their DBX names in other normal dbx subcommands. For example: (dbx) whatis $t3 (dbx) print $t3.state (dbx) assign $m2.type = fast Other normal dbx subcommands behave as usual, when debugging application program with threads, but in the context of the current thread (indicated by ">" in the thread list). The running thread is defaulted to be the dbx current thread, but users can specify the current thread using the "thread current " command. Normal dbx breakpoints are not specific to any one thread. If any one thread hits a breakpoint, all threads will stop. However, conditional breakpoints can be used to specify breakpoints for any one particular thread by checking the execution state of the threads. For example: (dbx) stop at 42 if $t3.state == run Thread subcommands: attribute - list existing attributes condition - list existing condition variables mutex - list existing mutexes rwlock - list existing rwlocks thread - list existing threads map [format] [> ] map [format] entry [, ] [> ] map [format]
[> ] map [format] [> ] Displays characteristics of loaded portions of the application from the first up to the second , inclusive. If no module numbers are specified, the entire list of loaded modules is displayed. The address and symbol variations display characteristics of the module associated with the given address or symbol. The optional [format] argument can be one of the following: "abbr", "normal", "raw", or "verbose". This option controls the level of detail with which the loaded module is described. The default map format can be set with the $mapformat internal variable. Module information can include the object name, member name, text origin, text end, text length, data origin, data end, data length, and file descriptor. multproc multproc on multproc parent multproc child multproc off Specifies the behavior of the dbx debug program when forked and execed processes are created. The "on" flag is used to specify that a new dbx session will be created to debug the child path of a fork. The original dbx will continue to debug the parent path. The "parent" and "child" flags are used to specify a single path of a fork to follow. All flags except "off" enable dbx to follow an execed process. The "off" flag disables multiprocess debugging. If no flags are specified, the multproc subcommand returns the current status of multiprocess debugging. thread [> ] thread [ ...] [> ] thread [info] [ ...] [> ] thread [run | ready | susp | term] [> ] thread [hold | unhold] [ ...] [> ] thread [current] [] [> ] thread [run_next] [] [> ] Print the current status of all known threads in the process. Threads to be listed can be specified through the parameters, or all threads will be listed. Threads can also be selected by states using the run, ready, susp, term, or current options. The info option can be used to display full information about a thread, and threads can be held or unheld with the hold or unhold option. The current thread is defaulted to be the running thread and is used by dbx as the context for normal dbx subcommand, such as where or registers. The current option can be used to switch the dbx current thread. If users wish to run any one thread next, the run_next option can be used. mutex [> ] mutex [ ...] [> ] mutex [wait | nowait | lock | unlock] [> ] Print the current status of all known mutexes in the process. Mutexes to be listed can be specified through the parameters, or all mutexes will be listed. Users can also select only locked or unlocked mutexes, or mutexes with or without waiters by using the lock, unlock, wait, or nowait options. condition [> ] condition [ ...] [> ] condition [wait | nowait] [> ] Print the current status of all known condition in the process. Condition variables to be listed can be specified through the parameters, or all condition variables will be listed. Users can also select only condition variables with or without waiters by using the wait or nowait options attribute [> ] attribute [ ...] [> ] Print the current status of all known attributes in the process. Attributes to be listed can be specified through the parameters, or all attributes will be listed. thread [> ] thread [ ...] [> ] thread [info] [ ...] [> ] thread [run | ready | susp | term] [> ] thread [hold | unhold] [ ...] [> ] thread [current] [] [> ] Print the current status of all known threads in the process. Threads to be listed can be specified through the parameters, or all threads will be listed. Threads can also be selected by states using the run, wait, susp, term, or current options. The info option can be used to display full information about a thread, and threads can be held or unheld with the hold or unhold option. The current thread defaults to be the running thread and is used by dbx as the context for normal dbx subcommands, such as where or registers. The current option can be used to switch the dbx current thread. The help option tells what each field means when the 'th -' command is run. mutex [> ] mutex [ ...] [> ] mutex [lock | unlock] [> ] Print the current status of all known mutexes in the process. Mutexes to be listed can be specified through the parameters, or all mutexes will be listed. Users can also select only locked or unlocked mutexes, or mutexes by using the lock, unlock options. Debugging application program with threads: No special option is needed for debugging application program with threads; however, a full core file is required for thread related subcommands when debugging a core file. DBX provides five commands ("thread", "mutex", "condition", and "attribute") for listing thread related objects and attributes. Users can also reference individual thread related objects using their DBX names in other normal dbx subcommands. For example: (dbx) whatis $t3 (dbx) print $t3.state (dbx) assign $m2.islock = 1 Other normal dbx subcommands behave as usual, when debugging application program with threads, but in the context of the current thread (indicated by ">" in the thread list). The running thread (indicated by "*" in the thread list) is the thread responsible of stopping process. The running thread defaults to be the dbx current thread, but users can specify the current thread using the "thread current " command. Normal dbx breakpoints are not specific to any one thread. If any one thread hits a breakpoint, all threads will stop. However, conditional breakpoints can be used to specify breakpoints for any one particular thread by checking the execution state of the threads. Two aliases are given to help the user : blth(f,x) stop at f if ($running_thread == x) bfth(f,x) stopi at &f if ($running_thread == x) For example: (dbx) stop at 42 if ($running_thread == 3) (dbx) blth (42,3) (dbx) bfth (thread1,3) Thread subcommands: attribute - list existing attributes condition - list existing condition variables mutex - list existing mutexes thread - list existing threads thread [> ] thread [-] [ ...] [> ] thread [info] [-] [ ...] [> ] thread [run | ready | susp | term] [-] [> ] thread [hold | unhold] [-] [ ...] [> ] thread [current] [-] [] [> ] thread [help] [> ] Print the current status of all known threads in the process. Threads to be listed can be specified through the parameters, or all threads will be listed. If the '-' option is given then a different format of thread information is displayed which has more information about each thread. Threads can also be selected by states using the run, wait, susp, term, or current options. The info option can be used to display full information about a thread, and threads can be held or unheld with the hold or unhold option. The current thread defaults to be the running thread and is used by dbx as the context for normal dbx subcommands, such as where or registers. The current option can be used to switch the dbx current thread. The help option tells what each field means when the 'th -' command is run. mutex [> ] mutex [ ...] [> ] mutex [thnum | utid] [ ...] [> ] mutex [lock | unlock] [> ] Print the current status of all known mutexes in the process. Mutexes to be listed can be specified through the parameters, or all mutexes will be listed. Mutexes held by a particular thread can be displayed by giving the thread number. Users can display all the mutexes held by a particular user thread id by giving the id either in hex(e.g 0x0001) or a number. Users can also select only locked or unlocked mutexes, or mutexes by using the lock, unlock options. Debugging application program with threads: No special option is needed for debugging application program with threads; however, a full core file is required for thread related subcommands when debugging a core file. DBX provides seven commands ("thread", "mutex", "condition", "rwlock", "spinlock", "barrier", and "attribute") for listing thread related objects and attributes. Users can also reference individual thread related objects using their DBX names in other normal dbx subcommands. For example: (dbx) whatis $t3 (dbx) print $t3.state (dbx) assign $m2.islock = 1 Other normal dbx subcommands behave as usual, when debugging application program with threads, but in the context of the current thread (indicated by ">" in the thread list). The running thread (indicated by "*" in the thread list) is the thread responsible of stopping process. The running thread defaults to be the dbx current thread, but users can specify the current thread using the "thread current " command. Normal dbx breakpoints are not specific to any one thread. If any one thread hits a breakpoint, all threads will stop. However, conditional breakpoints can be used to specify breakpoints for any one particular thread by checking the execution state of the threads. Two aliases are given to help the user : blth(f,x) stop at f if ($running_thread == x) bfth(f,x) stopi at &f if ($running_thread == x) For example: (dbx) stop at 42 if ($running_thread == 3) (dbx) blth (42,3) (dbx) bfth (thread1,3) Thread subcommands: attribute - list existing attributes condition - list existing condition variables barrier - list existing barrier spinlock - list existing spinlocks mutex - list existing mutexes thread - list existing threads rwlock - list existing rwlocks stophwp
Stop execution when the contents of the specified memory region change. This is a accomplished in hardware and may not be available on all models. tracehwp
Have tracing information printed when the contents of the specified memory region change. This is accomplished in hardware and may not be available on all models. disable disable all The traces or stops corresponding to the given numbers are disabled. The numbers associated with traces and stops can be printed with the "status" command. enable enable all The traces or stops corresponding to the given numbers are enabled. The numbers associated with traces and stops can be printed with the "status" command. plugin [> ] plugin [> ] Pass the subcommand line to the specified plug-in for execution. If no arguments are specified, displays the list of active plug-ins. pluginload Load the specified plug-in. pluginunload Unload the specified plug-in. fd [raw] [ []] Displays file descriptor(s) kthread [raw] [info | ru] [] Display kernel threads. If "raw" is used, output is in raw format. "info" displays detail, "ru" shows resource usage. If "tid" is used, only info for that particular thread is shown. proc [raw] [cred | cru | rlimit | ru | sigflags | signal] Display process information. "raw" displays in raw hex format. "cred" shows credentials, "cru", "ru" and "rlimit" resource info, "sigflags" and "signal" information about signals and handlers. handler { atfork | cancel_cleanup [ all | pthread id ] } Display information about atfork or cancellation cleanup handlers. For "cancel_cleanup" version, default is to display those registered for the current pthread. Optionally, "all" or a pthread id may be specified. onceblock [ uninit | done ] Display information about blocks of initialization code registered using the pthread_once routine. Optionally specify to only display those that have executed ("done") or that have not ("uninit"). resource { owner | waiter } [ all | pthread id ] Display information about which resources pthreads currently hold or are waiting on. Optionally specify all or a specific pthread id. spinlock [> ] spinlock [ ...] [> ] spinlock [thnum | utid] [ ...] [> ] spinlock [lock | unlock] [> ] Print the current status of all known spinlocks in the process. Spinlocks to be listed can be specified through the parameters, or all spinlocks will be listed. Spinlocks held by a particular thread can be displayed by giving the thread number. Users can display all the spinlocks held by a particular user thread id by giving the id either in hex(e.g 0x0001) or a number. Users can also select only locked or unlocked spinlocks, or spinlocks by using the lock, unlock options. barrier [> ] barrier [ ...] [> ] barrier [wait | nowait] [> ] Print the current status of all known barrier in the process. Barrier to be listed can be specified through the parameters, or all barrier will be listed. Users can also select only barrier with or without waiters by using the wait or nowait options corefile Displays high-level information about a corefile Debugging corefiles with DBX Much of the information available for live processes can also be obtained from a corefile. Here are some of the most useful subcommands to use with corefiles: corefile - high-level info, including corefile version and flags where - stack trace (defaults to faulting thread)* proc - traits of the process when it coredumped thread - pthreads data (only available for FULL_CORE) kthread - information about kernel threads fd - file descriptors at the time of the dump map - shows which modules were loaded at time of dump (/) display - memory display available for some locations *The thread command can be used to switch the "current" thread, allowing for display of stack traces of the other threads. Note: In order to provide the greatest amount of utility, dbx must have the executable present with its corefile at the time of debugging. For more information, please see help on the individual subcommands listed above. addcmd <"command-string"> addcmd all <"command-string"> Add dbx subcommands to the given event, which will be executed whenever the breakpoint, tracepoint, or watchpoint corresponding to the event is hit. The dbx subcommands can be specified through the "command-string" parameter, which is a group of dbx subcommands separated by the ; (semicolon) character. The numbers associated with the events can be printed with the "status" command. delcmd delcmd all Remove dbx subcommands associated with the given event-number. The numbers associated with the events and commands can be printed with the "status" command. Breakpoint/Trace subcommands: stop - set breakpoint in program trace - set trace in program status - print active breakpoints and traces with associated dbx subcommands addcmd - add dbx subcommands to given event numbers delcmd - delete dbx subcommands from given event number delete - remove traces or breakpoints of given numbers clear - remove all breakpoints and traces at given line stopi - set a breakpoint at a specified address tracei - turn on instruction tracing cleari - remove all breakpoints and traces at given address status [> ] status more [> ] Display the currently active trace and stop commands with associated dbx subcommands. dump [ > ] dump . [ > ] dump [ > ] dump [ > ] dump "PATTERN" [ > ] Print the names and values of variables in the given procedure, or the current one if none is specified. If the procedure given is '.', then all active variables are dumped. If a module name is given, all variables in the module are dumped, and if a wildcard PATTERN is given, all the matching symbols in the global space are dumped. where [startframe endframe] [> ] Print out a stack trace of the active procedures and functions associated with the frame numbers startframe to endframe. Set $stack_details for verbose stack trace. frame [num] Change the current function to the function corresponding to the specified stack frame number num. If none is specified then print the current function. Execution subcommands: run - begin execution of the program rerun - begin execution of program with previous arguments cont - continue execution step - single step one line next - step to next line (skip over calls) return - continue until a return to specified procedure is reached skip - continue execution ignoring next breakpoint goto - change execution to specified source line stepi - single step one instruction nexti - step to next instruction (skip over calls) gotoi - change execution to specified address up - move current function up the stack down - move current function down the stack frame - move current function to specified frame in the stack where - print currently active procedures call - execute a procedure in program print - execute a procedure and print return code catch - trap the signal before it is sent to program ignore - stop trapping the signal before it is sent to program detach - exit dbx without terminating program quit - exit dbx (program terminated) $mapaddrs When set, dbx starts address mapping, useful for kernel debugging. $mapformat Specifies the default output format for the map subcommand. To change the value, the user should type 'set $mapformat = ""'. If the $mapformat variable is unset, it will behave as if the value was "normal". The following are the valid values for $mapformat: "abbr" - Map output will consist of a single line containing the entry number, module name, and member name. "normal" - Map output will consist of the entry number, module name, member name, text origin, text length, data origin, data length, and file descriptor. "raw" - Map output will consist of a single unformatted line containing the following space-separated fields: entry number, module name with optional member name, text origin, text end, text length, data origin, data end, data length, and file descriptor. "verbose" - Map output will consist of the entry number, module name, member name, text origin, text end, text length, data origin, data end, data length, and file descriptor. $menuwindow Specifies the number of lines to list when prompting users for choices. $mnemonics Specifies the set of mnemonics used for disassembly. To change the value, the user should type 'set $mnemonics = ""'. If the $mnemonics variable is unset, it will behave as if the value was "default". The following are the valid values for $mnemonics: "default" - Disassemble using the mnemonics which most closely match the specified instruction set. "pwr" - Disassemble using the mnemonics for the Power architecture. "ppc" - Disassemble using the mnemonics for the PowerPC architecture. $print_fullname When set, dbx prints the fully-qualified identifier, even in cases where there is no apparent ambiguity. $print_mangled When debugging C++ code, setting this variable causes dbx to print mangled identifiers. $repeat When set, dbx repeats the previous command if no command was entered. $sigblock When set, dbx blocks signals to your program. $showbases When set, dbx displays base classes of C++ class types. $showblocks When set, dbx prints unnamed blocks in location output. $stepignore Specifies the behavior of the "step" subcommand on a source line calling another routine with no debugging information. To change the value, the user should type 'set $stepignore = ""'. If the $stepignore variable is unset, it will behave as if the value was "function". The following are the valid values for $stepignore: "function" - dbx will behave as if subcommand "next" was issued. "module" - if function is in load module with no debug information (such as a system library), dbx will behave as if subcommand "next" was issued. "none" - dbx will "stepi" until it reaches an instruction with source information. $unsafecall $unsafeassign $unsafegoto $unsafebounds Turn off type checking for calls, assignments, goto and array bounds checking. $vardim Specifies the dimension length to use when printing arrays with unknown bounds $deferevents Turns on the deferred events feature. $stack_details Displays the frame number and the register set for each active function/procedure displayed by the "where" subcommand. Breakpoint/Trace subcommands: stop - set breakpoint in program trace - set trace in program status - print active breakpoints and traces with associated dbx subcommands and remaining thread tskip counts addcmd - add dbx subcommands to given event numbers delcmd - delete dbx subcommands from given event number delete - remove traces or breakpoints of given numbers and remaining thread tskip counts clear - remove all breakpoints and traces at given line stopi - set a breakpoint at a specified address tracei - turn on instruction tracing cleari - remove all breakpoints and traces at given address tstop - set source-level breakpoint for a thread tstopi - set instruction-level breakpoint for a thread ttrace - set a source-level trace for a thread ttracei - set a instruction-level trace for a thread Execution subcommands: run - begin execution of the program rerun - begin execution of program with previous arguments cont - continue execution step - single step one line next - step to next line (skip over calls) return - continue until a return to specified procedure is reached skip - continue execution ignoring next breakpoint goto - change execution to specified source line stepi - single step one instruction nexti - step to next instruction (skip over calls) gotoi - change execution to specified address up - move current function up the stack down - move current function down the stack frame - move current function to specified frame in the stack where - print currently active procedures call - execute a procedure in program print - execute a procedure and print return code catch - trap the signal before it is sent to program ignore - stop trapping the signal before it is sent to program detach - exit dbx without terminating program quit - exit dbx (program terminated) tnext - Runs a thread up to the next source line tnexti - Runs a thread up to the next machine instruction tskip - skips breakpoints for a thread tstep - Runs a thread one source line tstepi - Runs a thread one machine instruction status [> ] status more [> ] Display the currently active trace and stop commands with associated dbx subcommands and the remaining thread tskip counts delete delete all delete tskip [ for $t ] The traces or stops corresponding to the given numbers or the remaining tskip count for the specified thread are removed. The numbers associated with traces, stops and the remaining thread tskip counts can be printed with the "status" command. tstop at [if ] [for $t] tstop in [if ] [for $t] tstop at [if ] [for $t] Stop execution of a system scope thread when the given line is reached, procedure or function entered, variable changed, or condition true. If no thread is specified, current thread will be used. tstophwp
[for $t] Stop execution of a system scope thread when the contents of the specified memory region change. This is a accomplished in hardware and may not be available on all models. If no thread is specified, current thread will be used. tstopi at
[if ] [for $t] tstopi in [if ] [for $t] tstopi
at
[if ] [for $t] Stops execution of a system scope thread when the specified address is reached and the condition is true. If no thread is specified, current thread will be used. Machine level subcommands: display(/) - display contents of memory cleari - remove all stop/trace points at given address listi - list instruction from application stopi - set a breakpoint at a specified address tracei - turn on instruction tracing stepi - single step one instruction nexti - step to next instruction (skip over calls) registers - display register set gotoi - change execution to specified address map - display address maps and loader information stophwp - set a hardware watchpoint stop tracehwp - set a hardware watchpoint trace tstopi - set instruction-level breakpoint for a thread ttracei - set a source-level trace for a thread tnexti - Runs a thread up to the next machine instruction tstepi - Runs a thread one machine instruction tstophwp - set a hardware watchpoint trace for a thread ttracehwp - Set a hardware watchpoint stop for a thread ttrace [if ] ttrace [if ] ttrace variable at [if ] Prints tracing information for a system scope thread when the given line is reached, procedure or function entered, variable changed, or condition true. If no thread is specified, current thread will be used. ttracei at Address [ if Condition ] [ for $t ] ttracei Address at Address [ if Condition ] [ for $t ] Prints tracing information for a system scope thread when the given address is reached, the value at the given address changes or condition is true. If no thread is specified, current thread will be used. ttracehwp address size [ for $t ] Have tracing information printed for a system scope thread when the contents of the specified memory region change. This is accomplished in hardware and may not be available on all models. If no thread is specified, current thread will be used. tnext [ count ] Execute the running thread up to the next source line. The running thread should be a system scope thread. If a count is supplied, executes the next count source lines. The difference between this and "tstep" is that if the line contains a call to a procedure or function the "tstep" command will stop at the beginning of that block, while the "tnext" command will not. tnexti [ count ] Single step the running thread a single instruction. The running thread should be a system scope thread. If a count is supplied, tnexti subcommand will be repeated count number of times. tstep [ count ] Execute the running thread one source line. The running thread should be a system scope thread. If a count is supplied, execute the next count source lines. The difference between this and "tnext" is that if the line contains a call to a procedure or function the "tstep" command will enter that procedure or function, while the "tnext" command will not. See also: set_variables $stepignore tstepi [ count ] Executes the running thread a single instruction. The running thread should be a system scope thread. If a count is supplied, executes the next count instructions. tskip [ count ] Executes the running thread from the current stopping point ignoring the next count number of breakpoints for the thread. The running thread should be a system scope thread. tls map Prints the TLS initialization template and its size for loaded TLS modules. Machine level subcommands: display(/) - display contents of memory cleari - remove all stop/trace points at given address listi - list instruction from application stopi - set a breakpoint at a specified address tracei - turn on instruction tracing stepi - single step one instruction nexti - step to next instruction (skip over calls) registers - display register set gotoi - change execution to specified address malloc - displays information about the program's usage of the malloc subsystem map - display address maps and loader information stophwp - set a hardware watchpoint stop tls - display TLS initialization template information tracehwp - set a hardware watchpoint trace tstopi - set instruction-level breakpoint for a thread ttracei - set a source-level trace for a thread tnexti - Runs a thread up to the next machine instruction tstepi - Runs a thread one machine instruction tstophwp - set a hardware watchpoint trace for a thread ttracehwp - Set a hardware watchpoint stop for a thread Debugging corefiles with DBX Much of the information available for live processes can also be obtained from a corefile. Here are some of the most useful subcommands to use with corefiles: corefile - high-level info, including corefile version and flags where - stack trace (defaults to faulting thread)* proc - traits of the process when it coredumped thread - pthreads data (only available for FULL_CORE) kthread - information about kernel threads fd - file descriptors at the time of the dump malloc - displays information about the program's usage of the malloc subsystem map - shows which modules were loaded at time of dump (/) display - memory display available for some locations tls - display TLS initialization template information *The thread command can be used to switch the "current" thread, allowing for display of stack traces of the other threads. Note: In order to provide the greatest amount of utility, dbx must have the executable present with its corefile at the time of debugging. For more information, please see help on the individual subcommands listed above. map [format] [ for $t ][> ] map [format] entry [, ] [ for $t ][> ] map [format]
[ for $t ][> ] map [format] [ for $t ][> ] Displays characteristics of loaded portions of the application from the first up to the second , inclusive. If no module numbers are specified, the entire list of loaded modules is displayed. The address and symbol variations display characteristics of the module associated with the given address or symbol. The optional [format] argument can be one of the following: "abbr", "normal", "raw", or "verbose". This option controls the level of detail with which the loaded module is described. The default map format can be set with the $mapformat internal variable. Module information can include the object name, member name, text origin, text end, text length, data origin, data end, data length, TLS data origin, TLS data end, TLS data length and file descriptor. The TLS data information will be displayed for the specified thread. If no thread is specified, the current thread will be used. $mapaddrs When set, dbx starts address mapping, useful for kernel debugging. $mapformat Specifies the default output format for the map subcommand. To change the value, the user should type 'set $mapformat = ""'. If the $mapformat variable is unset, it will behave as if the value was "normal". The following are the valid values for $mapformat: "abbr" - Map output will consist of a single line containing the entry number, module name, and member name. "normal" - Map output will consist of the entry number, module name, member name, text origin, text length, data origin, data length, and file descriptor. If the module has TLS data, then TLS data origin and TLS data length will also be for the specified thread or the current thread, if no thread has been specified. "raw" - Map output will consist of a single unformatted line containing the following space-separated fields: entry number, module name with optional member name, text origin, text end, text length, data origin, data end, data length, and file descriptor. If the module has TLS data, then TLS data origin, TLS data end and the TLS data length will be displayed for the specified thread or the current thread, if no thread has been specified. "verbose" - Map output will consist of the entry number, module name, member name, text origin, text end, text length, data origin, data end, data length, and file descriptor. If the module has TLS data, then TLS data origin, TLS data end and the TLS data length will be displayed for the specified thread or the current thread, if no thread has been specified. $menuwindow Specifies the number of lines to list when prompting users for choices. $mnemonics Specifies the set of mnemonics used for disassembly. To change the value, the user should type 'set $mnemonics = ""'. If the $mnemonics variable is unset, it will behave as if the value was "default". The following are the valid values for $mnemonics: "default" - Disassemble using the mnemonics which most closely match the specified instruction set. "pwr" - Disassemble using the mnemonics for the Power architecture. "ppc" - Disassemble using the mnemonics for the PowerPC architecture. $print_fullname When set, dbx prints the fully-qualified identifier, even in cases where there is no apparent ambiguity. $print_mangled When debugging C++ code, setting this variable causes dbx to print mangled identifiers. $repeat When set, dbx repeats the previous command if no command was entered. $sigblock When set, dbx blocks signals to your program. $showbases When set, dbx displays base classes of C++ class types. $showblocks When set, dbx prints unnamed blocks in location output. $stepignore Specifies the behavior of the "step\tstep" subcommand on a source line calling another routine with no debugging information. To change the value, the user should type 'set $stepignore = ""'. If the $stepignore variable is unset, it will behave as if the value was "function". The following are the valid values for $stepignore: "function" - dbx will behave as if subcommand "next\tnext" was issued. "module" - if function is in load module with no debug information (such as a system library), dbx will behave as if subcommand "next\tnext" was issued. "none" - dbx will "stepi\tstepi" until it reaches an instruction with source information. $unsafecall $unsafeassign $unsafegoto $unsafebounds Turn off type checking for calls, assignments, goto and array bounds checking. $vardim Specifies the dimension length to use when printing arrays with unknown bounds $deferevents Turns on the deferred events feature. $stack_details Displays the frame number and the register set for each active function/procedure displayed by the "where" subcommand. Debugging application program with threads: No special option is needed for debugging application program with threads; however, a full core file is required for thread related subcommands when debugging a core file. DBX provides seven commands ("thread", "mutex", "condition", "rwlock", "spinlock", "barrier", and "attribute") for listing thread related objects and attributes. Users can also reference individual thread related objects using their DBX names in other normal dbx subcommands. For example: (dbx) whatis $t3 (dbx) print $t3.state (dbx) assign $m2.islock = 1 Other normal dbx subcommands behave as usual, when debugging application program with threads, but in the context of the current thread (indicated by ">" in the thread list). The running thread (indicated by "*" in the thread list) is the thread responsible of stopping process. The running thread defaults to be the dbx current thread, but users can specify the current thread using the "thread current " command. Normal dbx breakpoints are not specific to any one thread. If any one thread hits a breakpoint, all threads will stop. However, conditional breakpoints can be used to specify breakpoints for any one particular thread by checking the execution state of the threads. Two aliases are given to help the user : blth(f,x) stop at f if ($running_thread == x) bfth(f,x) stopi at &f if ($running_thread == x) For example: (dbx) stop at 42 if ($running_thread == 3) (dbx) blth (42,3) (dbx) bfth (thread1,3) Debugging system-scope threads dbx provides additional support for debugging system scope threads.Each user thread should have exactly one kernel thread mapped to it. Creating thread-level events To set source/instruction level breakpoints for a thread, use the tstop/tstopi subcommands. To set a source/instruction level trace for a thread, use the ttrace/ttracei subcommands. To set a thread-level watchpoint stop, use the tstophwp subcommand. To set a thread-level watchpoint trace, use the ttracehwp subcommand. Displaying and manipulating thread-level events To view the thread-level events, use the status subcommand. To delete thread-level events, use the delete subcommand. Running a thread To continue the running thread to the next source line or instruction, use the tnext/tnexti subcommand. To make the running thread execute a source line or machine instruction from the current stopping point, use the tstep/tstepi subcommand. To skip the thread-level breakpoints for the running thread, use the tskip subcommand. Thread subcommands: attribute - list existing attributes condition - list existing condition variables barrier - list existing barrier spinlock - list existing spinlocks mutex - list existing mutexes thread - list existing threads rwlock - list existing rwlocks tstophwp - Sets a thread-level hardware watchpoint stop ttracehwp - Sets a thread-level hardware watchpoint trace tstop - Sets a source-level breakpoint stop for a thread tstopi - Sets an instruction-level breakpoint stop for a thread ttrace - Sets a source-level trace for a thread ttracei - Sets an instruction-level trace for a thread tnext - Runs a thread up to the next source line tnexti - Runs a thread up to the next machine instruction tstep - Runs a thread one source line tstepi - Runs a thread one machine instruction tskip - Skips breakpoints for a thread.
,
/ [] [> ]
/ [] [] [> ] Display contents of memory starting at the first
up to the second
or until items are printed. If the address is ".", the address following the one most recently printed is used. The mode specifies how memory is to be printed; if it is omitted the previous mode specified is used. The initial mode is "X". The following modes are supported: i print the machine instruction d print a short word in decimal D print a long word in decimal o print a short word in octal O print a long word in octal x print a short word in hexadecimal X print a long word in hexadecimal b print a byte in octal c print a byte as a character h print a byte in hexadecimal s print a string (terminated by a null byte) f print a single precision real number g print a double precision real number q print a quad precision real number lld print an 8 byte signed decimal number llu print an 8 byte unsigned decimal number llx print an 8 byte unsigned hexadecimal number llo print an 8 byte unsigned octal number Hf Prints a single precision decimal float number Df Prints a double precision decimal float number DDf Prints a quad precision decimal float number The following "set" variables have special meanings: $catchbp When set, dbx catches breakpoints during execution of the next command. $frame Setting this variable to an address alters dbx's idea of the current stack frame. $expandunions Causes dbx to display values of each part of variant records or unions. $hexin $octin When set, dbx interprets addresses in hexadecimal or octal. $hexchars $hexints $hexstrings When set, dbx prints characters, integers or character pointers in hexadecimal. $noargs When set, dbx omits arguments from subcommands, such as where, up, down, and dump. $noflregs When set, dbx omits the display of floating-point registers from the registers subcommand. $novregs When set, dbx omits the display of vector registers from the registers subcommand. $octints When set, dbx prints integers in octal. $ignoreifhandler When set, dbx suppresses notification of signals which have a registered handler. $ignoreload When set, dbx ignores load(), unload(), or loadbind() subroutines performed by your program. $ignorenonbptrap When set, dbx suppresses notification of non-breakpoint trap instructions that trigger when a SIGTRAP handler is registered. $instructionset Specifies the default disassembly mode. To change the value, the user should type 'set $instructionset = ""'. If the $instructionset variable is unset, it will behave as if the value was "default". The following are the valid values for $instructionset: "default" - Disassemble using the instruction set for the hardware architecture dbx is running on. "com" - Disassemble using the instruction set that is common between Power and PowerPC architectures. The mnemonics will default to PowerPC mnemonics. "pwr" - Disassemble using the instruction set for the RS1 implementation of the Power architecture. The mnemonics will default to Power mnemonics. "pwrx" - Disassemble using the instruction set for the RS2 implementation of Power architecture. The mnemonics will default to Power mnemonics. "pwr6" - Disassemble using the instruction set for the POWER6 implementation of PowerPC architecture. The mnemonics will default to PowerPC mnemonics. "ppc" - Disassemble using the instruction set for the PowerPC architecture. The mnemonics will default to PowerPC mnemonics. "601" - Disassemble using the instruction set for the 601 implementation of PowerPC architecture. The mnemonics will default to PowerPC mnemonics. "603" - Disassemble using the instruction set for the 603 implementation of PowerPC architecture. The mnemonics will default to PowerPC mnemonics. "604" - Disassemble using the instruction set for the 604 implementation of PowerPC architecture. The mnemonics will default to PowerPC mnemonics. "970" - Disassemble using the instruction set for the 970 implementation of PowerPC architecture. The mnemonics will default to PowerPC mnemonics. "any" - Disassemble using any valid instruction from either Power or PowerPC architecture. The mnemonics will default to PowerPC mnemonics $java When set, also sets the following variables, placing dbx in a mode to debug Java applications. When unset, also unsets the following variables: $ignorenonbptrap Suppresses notification of trap instructions generated by the Java Just-In-Time (JIT) compiler. $listwindow Specifies the number of lines to list and listi commands. malloc malloc [ allocation [ { } { } ] value ] ] malloc [ freespace [ { } { } ] value ] ] The malloc subcommand with no options prints out a list of enabled options and allocation policies as well as a statistical summary of malloc usage since process startup. The allocation option to the malloc subcommand displays a sorted list of all the allocations currently held by the process. The allocation attributes can be any of "address", "size", "heap", "pid", "tid", "time". The condition checking options can be any of ">", "<", "==", "!=". Using an optional attribute RELOP value argument allows for a more narrow selection of active allocations. The freespace option to the malloc subcommand displays a sorted list of all the free space available in the process heap. The freespace attributes can be any of "address", "size", "heap". The condition checking attribute can be any of "<", ">", "==", "!=". Using an optional attribute RELOP value argument allows for a more narrow selection of free space nodes. DBX Startup Options: dbx [-a ProcessID] [-c CommandFile] [-d NestingDepth] [-I Directory] [-p [OldPath=NewPath:... | File]] [-v] [-u] [-x] [-F] [-L] [-r] [-C CoreFile | ObjectFile [CoreFile]] -a ProcessID Attach to specified process -c CommandFile Run dbx subcommands in specified file first -d NestingDepth Set limit for nesting of program blocks -I Directory Include Directory in list of directories searched for source files -p OldPath=NewPath Substitute library path for core examination File Read library path substitutions for core examination from File -C CoreFile Allow to analyze core dump without ObjectFile -v Relax core file validity checking -u Prepend file name symbols with an '@' -x Strip postfix '_' from FORTRAN symbols -F Read all symbols at start-up time -L Keep linkage symbols -r Run object file immediately Debugging corefiles with DBX Much of the information available for live processes can also be obtained from a corefile. Here are some of the most useful subcommands to use with corefiles: corefile - high-level info, including corefile version and flags coremap - displays the mapping of a given address space region where - stack trace (defaults to faulting thread)* proc - traits of the process when it coredumped thread - pthreads data (only available for FULL_CORE) kthread - information about kernel threads fd - file descriptors at the time of the dump malloc - displays information about the program's usage of the malloc subsystem map - shows which modules were loaded at time of dump (/) display - memory display available for some locations tls - display TLS initialization template information *The thread command can be used to switch the "current" thread, allowing for display of stack traces of the other threads. Note: In order to provide the greatest amount of utility, dbx must have the executable present with its corefile at the time of debugging. For more information, please see help on the individual subcommands listed above. coremap [ stack | data | sdata | mmap | shm | loader ] Displays the mapping of a given address space region. If the region name is not specified, then all available mappings will be displayed. The following "set" variables have special meanings: $catchbp When set, dbx catches breakpoints during execution of the next command. $codepage Specifies the code set the characters of the debugee are encoded to. The code page is set by typing 'set $codepage = ""'. $frame Setting this variable to an address alters dbx's idea of the current stack frame. $expandunions Causes dbx to display values of each part of variant records or unions. $hexin $octin When set, dbx interprets addresses in hexadecimal or octal. $hexchars $hexints $hexstrings When set, dbx prints characters, integers or character pointers in hexadecimal. $noargs When set, dbx omits arguments from subcommands, such as where, up, down, and dump. $noflregs When set, dbx omits the display of floating-point registers from the registers subcommand. $novregs When set, dbx omits the display of vector registers from the registers subcommand. $octints When set, dbx prints integers in octal. $ignoreifhandler When set, dbx suppresses notification of signals which have a registered handler. $ignoreload When set, dbx ignores load(), unload(), or loadbind() subroutines performed by your program. $ignorenonbptrap When set, dbx suppresses notification of non-breakpoint trap instructions that trigger when a SIGTRAP handler is registered. $instructionset Specifies the default disassembly mode. To change the value, the user should type 'set $instructionset = ""'. If the $instructionset variable is unset, it will behave as if the value was "default". The following are the valid values for $instructionset: "default" - Disassemble using the instruction set for the hardware architecture dbx is running on. "com" - Disassemble using the instruction set that is common between Power and PowerPC architectures. The mnemonics will default to PowerPC mnemonics. "pwr" - Disassemble using the instruction set for the RS1 implementation of the Power architecture. The mnemonics will default to Power mnemonics. "pwrx" - Disassemble using the instruction set for the RS2 implementation of Power architecture. The mnemonics will default to Power mnemonics. "pwr6" - Disassemble using the instruction set for the POWER6 implementation of PowerPC architecture. The mnemonics will default to PowerPC mnemonics. "ppc" - Disassemble using the instruction set for the PowerPC architecture. The mnemonics will default to PowerPC mnemonics. "601" - Disassemble using the instruction set for the 601 implementation of PowerPC architecture. The mnemonics will default to PowerPC mnemonics. "603" - Disassemble using the instruction set for the 603 implementation of PowerPC architecture. The mnemonics will default to PowerPC mnemonics. "604" - Disassemble using the instruction set for the 604 implementation of PowerPC architecture. The mnemonics will default to PowerPC mnemonics. "970" - Disassemble using the instruction set for the 970 implementation of PowerPC architecture. The mnemonics will default to PowerPC mnemonics. "any" - Disassemble using any valid instruction from either Power or PowerPC architecture. The mnemonics will default to PowerPC mnemonics $java When set, also sets the following variables, placing dbx in a mode to debug Java applications. When unset, also unsets the following variables: $ignorenonbptrap Suppresses notification of trap instructions generated by the Java Just-In-Time (JIT) compiler. $listwindow Specifies the number of lines to list and listi commands. DBX Startup Options: dbx [-a ProcessID] [-B DebugFile] [-c CommandFile] [-I Directory] [ -E DebugEnvironment ] [-p [OldPath=NewPath:... | File]] [-v] [-u] [-x] [-F] [-L] [-r] [-C CoreFile | ObjectFile [CoreFile]] -a ProcessID Attach to specified process -c CommandFile Run dbx subcommands in specified file first -I Directory Include Directory in list of directories searched for source files -C CoreFile Allow to analyze core dump without ObjectFile -p OldPath=NewPath Substitute library path for core examination or when attaching to a process File Read library path substitutions for core examination or when attaching to a process from File -E DebugEnvironment Specifies the environment variable for the debug program -B DebugFile Specify an alternate debug file on startup -v Relax core file validity checking -u Prepend file name symbols with an '@' -x Strip postfix '_' from FORTRAN symbols -F Read all symbols at start-up time -L Keep linkage symbols -r Run object file immediately $mapaddrs When set, dbx starts address mapping, useful for kernel debugging. $mapformat Specifies the default output format for the map subcommand. To change the value, the user should type 'set $mapformat = ""'. If the $mapformat variable is unset, it will behave as if the value was "normal". The following are the valid values for $mapformat: "abbr" - Map output will consist of a single line containing the entry number, module name, and member name. "normal" - Map output will consist of the entry number, module name, member name, text origin, text length, data origin, data length, and file descriptor. If the module has TLS data, then TLS data origin and TLS data length will also be for the specified thread or the current thread, if no thread has been specified. "raw" - Map output will consist of a single unformatted line containing the following space-separated fields: entry number, module name with optional member name, text origin, text end, text length, data origin, data end, data length, and file descriptor. If the module has TLS data, then TLS data origin, TLS data end and the TLS data length will be displayed for the specified thread or the current thread, if no thread has been specified. "verbose" - Map output will consist of the entry number, module name, member name, text origin, text end, text length, data origin, data end, data length, and file descriptor. If the module has TLS data, then TLS data origin, TLS data end and the TLS data length will be displayed for the specified thread or the current thread, if no thread has been specified. $menuwindow Specifies the number of lines to list when prompting users for choices. $mnemonics Specifies the set of mnemonics used for disassembly. To change the value, the user should type 'set $mnemonics = ""'. If the $mnemonics variable is unset, it will behave as if the value was "default". The following are the valid values for $mnemonics: "default" - Disassemble using the mnemonics which most closely match the specified instruction set. "pwr" - Disassemble using the mnemonics for the Power architecture. "ppc" - Disassemble using the mnemonics for the PowerPC architecture. $print_dynamic When set, prints the dynamic type of an object in C++. Code has to be compiled with -qrtti option for the RTTI data to be present. $print_fullname When set, dbx prints the fully-qualified identifier, even in cases where there is no apparent ambiguity. $print_mangled When debugging C++ code, setting this variable causes dbx to print mangled identifiers. $repeat When set, dbx repeats the previous command if no command was entered. $sigblock When set, dbx blocks signals to your program. $showbases When set, dbx displays base classes of C++ class types. $show_vft When set, prints Virtual Function table present in C++ objects, if available. $showblocks When set, dbx prints unnamed blocks in location output. $stepignore Specifies the behavior of the "step\tstep" subcommand on a source line calling another routine with no debugging information. To change the value, the user should type 'set $stepignore = ""'. If the $stepignore variable is unset, it will behave as if the value was "function". The following are the valid values for $stepignore: "function" - dbx will behave as if subcommand "next\tnext" was issued. "module" - if function is in load module with no debug information (such as a system library), dbx will behave as if subcommand "next\tnext" was issued. "none" - dbx will "stepi\tstepi" until it reaches an instruction with source information. $unsafecall $unsafeassign $unsafegoto $unsafebounds Turn off type checking for calls, assignments, goto and array bounds checking. $vardim Specifies the dimension length to use when printing arrays with unknown bounds $deferevents Turns on the deferred events feature. $stack_details Displays the frame number and the register set for each active function/procedure displayed by the "where" subcommand. where [ all | [$tthreadumber [(startframe endframe)] ...] ] [ startframe endframe ] [ >File ] Print out a stack trace of the active procedures and functions associated with the frame numbers startframe to endframe. Set $stack_details for verbose stack trace. In multi-threaded environment option all displays the stack details for all available threads. The stack details of individual threads can be displayed by specifying the thread number along with where subcommand. If start and end frames for individual threads are not specified, stack frames will be displayed as per the global start and end frame numbers. registers [ all | $tthreadnumber ...] [ >File ] Print the contents of all general purpose registers, system control registers, floating-point registers, vector registers, and the current instruction register. To display floating-point registers, use the "unset $noflregs" dbx subcommand. To display vector registers, use the "unset $novregs" dbx subcommand Registers can be displayed or assigned to individually by using the following predefined register names: $r0 through $r31 for the general purpose registers $fr0 through $fr31 for the floating point registers $sp, $iar, $cr, $link for, respectively, the stack pointer, the program counter, condition register, and the link register. Vector registers can be displayed or assigned individually by vector element type using the following predefined register names: $vr0 through $vr31, for vector registers of type vector int $vr0c through $vr31c, for vector char $vr0s through $vr31s, for vector short $vr0f through $vr31f, for vector float $vrsave for the vrsave special purpose register $vscr for the vector status and control register Assigning a vector register can either be done a whole register at a time, for example, assign $vr0 = $vr31, or must be done an individual element at a time, using array subscripts. For example, to assign the third float element of vr15, assign $vr15f[2] = . To assign the sixteenth character element of vr30, assign $vr30c[15] = . In multi-threaded environment option all displays the register details for all available threads. The register details of individual threads can be displayed by specifying the thread number along with registers subcommand. The registers subcommand with no options will display the registers for the current thread. The following "set" variables have special meanings: $catchbp When set, dbx catches breakpoints during execution of the next command. $codepage Specifies the code set the characters of the debugee are encoded to. The code page is set by typing 'set $codepage = ""'. $frame Setting this variable to an address alters dbx's idea of the current stack frame. $expandunions Causes dbx to display values of each part of variant records or unions. $hexin $octin When set, dbx interprets addresses in hexadecimal or octal. $hexchars $hexints $hexstrings When set, dbx prints characters, integers or character pointers in hexadecimal. $noargs When set, dbx omits arguments from subcommands, such as where, up, down, and dump. $noflregs When set, dbx omits the display of floating-point registers from the registers subcommand. $novregs When set, dbx omits the display of vector registers from the registers subcommand. $novsregs When set, dbx omits the display of vector scalar registers from the registers subcommand. $octints When set, dbx prints integers in octal. $ignoreifhandler When set, dbx suppresses notification of signals which have a registered handler. $ignoreload When set, dbx ignores load(), unload(), or loadbind() subroutines performed by your program. $ignorenonbptrap When set, dbx suppresses notification of non-breakpoint trap instructions that trigger when a SIGTRAP handler is registered. $instructionset Specifies the default disassembly mode. To change the value, the user should type 'set $instructionset = ""'. If the $instructionset variable is unset, it will behave as if the value was "default". The following are the valid values for $instructionset: "default" - Disassemble using the instruction set for the hardware architecture dbx is running on. "com" - Disassemble using the instruction set that is common between Power and PowerPC architectures. The mnemonics will default to PowerPC mnemonics. "pwr" - Disassemble using the instruction set for the RS1 implementation of the Power architecture. The mnemonics will default to Power mnemonics. "pwrx" - Disassemble using the instruction set for the RS2 implementation of Power architecture. The mnemonics will default to Power mnemonics. "pwr6" - Disassemble using the instruction set for the POWER6 implementation of PowerPC architecture. The mnemonics will default to PowerPC mnemonics. "pwr7" - Disassemble using the instruction set for the Power 7 implementation of PowerPC architecture. The mnemonics will default to PowerPC mnemonics. "ppc" - Disassemble using the instruction set for the PowerPC architecture. The mnemonics will default to PowerPC mnemonics. "601" - Disassemble using the instruction set for the 601 implementation of PowerPC architecture. The mnemonics will default to PowerPC mnemonics. "603" - Disassemble using the instruction set for the 603 implementation of PowerPC architecture. The mnemonics will default to PowerPC mnemonics. "604" - Disassemble using the instruction set for the 604 implementation of PowerPC architecture. The mnemonics will default to PowerPC mnemonics. "970" - Disassemble using the instruction set for the 970 implementation of PowerPC architecture. The mnemonics will default to PowerPC mnemonics. "any" - Disassemble using any valid instruction from either Power or PowerPC architecture. The mnemonics will default to PowerPC mnemonics $java When set, also sets the following variables, placing dbx in a mode to debug Java applications. When unset, also unsets the following variables: $ignorenonbptrap Suppresses notification of trap instructions generated by the Java Just-In-Time (JIT) compiler. $listwindow Specifies the number of lines to list and listi commands. registers [ all | $tthreadnumber ...] [ >File ] Print the contents of all general purpose registers, system control registers, floating-point registers, vector registers, and the current instruction register. To display floating-point registers, use the "unset $noflregs" dbx subcommand. To display vector registers, use the "unset $novregs" dbx subcommand To display vector scalar registers, use the "unset $novsregs" dbx subcommand. As vector scalar registers are a superset of legacy floating point registers and vector registers, when unset, the registers subcommand will display the vector scalar registers along with GPRs with legacy FPR and VR aliases in braces. Registers can be displayed or assigned to individually by using the following predefined register names: $r0 through $r31 for the general purpose registers $fr0 through $fr31 for the floating point registers $sp, $iar, $cr, $link for, respectively, the stack pointer, the program counter, condition register, and the link register. Vector registers can be displayed or assigned individually by vector element type using the following predefined register names: $vr0 through $vr31, for vector registers of type vector int $vr0c through $vr31c, for vector char $vr0s through $vr31s, for vector short $vr0f through $vr31f, for vector float $vrsave for the vrsave special purpose register $vscr for the vector status and control register Assigning a vector register can either be done a whole register at a time, for example, assign $vr0 = $vr31, or must be done an individual element at a time, using array subscripts. For example, to assign the third float element of vr15, assign $vr15f[2] = . To assign the sixteenth character element of vr30, assign $vr30c[15] = . The following predefined register types hold for Vector scalar registers $vsr0 through $vsr63, for vector scalar registers of type vector int $vsr0c through $vsr63c, for vector char $vsr0s through $vsr63s, for vector short $vsr0f through $vsr63f, for vector float $vsr0g through $vsr63g, for vector double $vsr0ll through $vsr63ll, for vector long long In multi-threaded environment option all displays the register details for all available threads. The register details of individual threads can be displayed by specifying the thread number along with registers subcommand. The registers subcommand with no options will display the registers for the current thread. limitbp (, ) ... limitbp (, +) ... The limitbp subcommand instructs DBX to stop execution of the debuggee only when the breakpoint has been hit a specified number of times. DBX will stop execution of the debuggee when the breakpoint is hit for time before execution of the code at breakpoint printbp [, breakpoint] printbp all The printbp subcommand instructs DBX to print the number of times that each of the breakpoints or all the subcommands were hit and the details of the limit on the breakpoint if a limit was set on it. The following "set" variables have special meanings: $catchbp When set, dbx catches breakpoints during execution of the next command. $codepage Specifies the code set the characters of the debugee are encoded to. The code page is set by typing 'set $codepage = ""'. $display_address_name Instructs dbx to try to display the variable/function names when examining memory addresses. For information on examining addresses refer "display" functionality. $frame Setting this variable to an address alters dbx's idea of the current stack frame. $expandunions Causes dbx to display values of each part of variant records or unions. $hexin $octin When set, dbx interprets addresses in hexadecimal or octal. $hexchars $hexints $hexstrings When set, dbx prints characters, integers or character pointers in hexadecimal. $noargs When set, dbx omits arguments from subcommands, such as where, up, down, and dump. $noflregs When set, dbx omits the display of floating-point registers from the registers subcommand. $novregs When set, dbx omits the display of vector registers from the registers subcommand. $novsregs When set, dbx omits the display of vector scalar registers from the registers subcommand. $octints When set, dbx prints integers in octal. $ignoreifhandler When set, dbx suppresses notification of signals which have a registered handler. $ignoreload When set, dbx ignores load(), unload(), or loadbind() subroutines performed by your program. $ignorenonbptrap When set, dbx suppresses notification of non-breakpoint trap instructions that trigger when a SIGTRAP handler is registered. $instructionset Specifies the default disassembly mode. To change the value, the user should type 'set $instructionset = ""'. If the $instructionset variable is unset, it will behave as if the value was "default". The following are the valid values for $instructionset: "default" - Disassemble using the instruction set for the hardware architecture dbx is running on. "com" - Disassemble using the instruction set that is common between Power and PowerPC architectures. The mnemonics will default to PowerPC mnemonics. "pwr" - Disassemble using the instruction set for the RS1 implementation of the Power architecture. The mnemonics will default to Power mnemonics. "pwrx" - Disassemble using the instruction set for the RS2 implementation of Power architecture. The mnemonics will default to Power mnemonics. "pwr6" - Disassemble using the instruction set for the POWER6 implementation of PowerPC architecture. The mnemonics will default to PowerPC mnemonics. "pwr7" - Disassemble using the instruction set for the Power 7 implementation of PowerPC architecture. The mnemonics will default to PowerPC mnemonics. "ppc" - Disassemble using the instruction set for the PowerPC architecture. The mnemonics will default to PowerPC mnemonics. "601" - Disassemble using the instruction set for the 601 implementation of PowerPC architecture. The mnemonics will default to PowerPC mnemonics. "603" - Disassemble using the instruction set for the 603 implementation of PowerPC architecture. The mnemonics will default to PowerPC mnemonics. "604" - Disassemble using the instruction set for the 604 implementation of PowerPC architecture. The mnemonics will default to PowerPC mnemonics. "970" - Disassemble using the instruction set for the 970 implementation of PowerPC architecture. The mnemonics will default to PowerPC mnemonics. "any" - Disassemble using any valid instruction from either Power or PowerPC architecture. The mnemonics will default to PowerPC mnemonics $java When set, also sets the following variables, placing dbx in a mode to debug Java applications. When unset, also unsets the following variables: $ignorenonbptrap Suppresses notification of trap instructions generated by the Java Just-In-Time (JIT) compiler. $listwindow Specifies the number of lines to list and listi commands. stop if [{}] stop at [if ] [{}] stop in [if ] [{}] stop [if ] [{}] stop at [if ] [{}] stop in [if ] [{}] stop on load [""] [if ] [{}] stop on load ["()"] [if ] [{}] Stop execution when the given line is reached, procedure or function entered, variable changed, module loaded or unloaded, or condition true. When is specified, execution of the debuggee is stopped just before the breakpoint executes for the time.
,
/ [] [> ]
/ [] [] [> ]
/ () [] [> ]
= [] [>] Display contents of memory starting at the first
up to the second
or until items are printed. If the address is ".", the address following the one most recently printed is used. The mode specifies how memory is to be printed; if it is omitted the previous mode specified is used. The initial mode is "X".
can be of the form & where is a member variable of the debuggee. The following modes are supported: i print the machine instruction d print a short word in decimal D print a long word in decimal o print a short word in octal O print a long word in octal x print a short word in hexadecimal X print a long word in hexadecimal b print a byte in octal c print a byte as a character h print a byte in hexadecimal s print a string (terminated by a null byte) f print a single precision real number g print a double precision real number q print a quad precision real number lld print an 8 byte signed decimal number llu print an 8 byte unsigned decimal number llx print an 8 byte unsigned hexadecimal number llo print an 8 byte unsigned octal number Hf Prints a single precision decimal float number Df Prints a double precision decimal float number DDf Prints a quad precision decimal float number Breakpoint/Trace subcommands: stop - set breakpoint in program trace - set trace in program status - print active breakpoints and traces with associated dbx subcommands and remaining tskip counts for threads addcmd - add dbx subcommands to given event numbers delcmd - delete dbx subcommands from given event number delete - remove traces or breakpoints of given numbers and remaining thread tskip counts limitbp - ignore the breakpoint until it has been hit a specified number of times printbp - print the number of hits of a breakpoint and the limit if any set on the breakpoint clear - remove all breakpoints and traces at given line stopi - set a breakpoint at a specified address tracei - turn on instruction tracing cleari - remove all breakpoints and traces at given address tstop - set source-level breakpoint for a thread tstopi - set instruction-level breakpoint for a thread ttrace - set a source-level trace for a thread ttracei - set a instruction-level trace for a thread assign = assign
= Assign the value of the expression to the variable or to the memory location denoted by the address. The following "set" variables have special meanings: $catchbp When set, dbx catches breakpoints during execution of the next command. $codepage Specifies the code set the characters of the debugee are encoded to. The code page is set by typing 'set $codepage = ""'. $compact_bt_ident Specifies a limit on the number of characters of the identifier name to be printed when showing a stack trace. To assign a value, type 'set $compact_bt_ident=' where is a positive integer between 4 and 128. If 'set $compact_bt_ident' is entered, default will be taken as 8. Once specified, when printing a stack trace, dbx will print number of characters of an identifier and then print three '.' if the original identifier's length is three more than . $compact_bt_string Specifies a limit on the number of characters of a function argument that is a string is to be printed when showing a stack trace. To assign a value type 'set $compact_bt_string=' where is a positive integer between 4 and 128. If 'set $compact_bt_string' is entered, default will be taken as 8. Once specified, when printing a stack trace, dbx will print number of characters of a function argument string and then print three '.' if the original string's length is three more than . $display_address_name Instructs dbx to try to display the variable/function names when examining memory addresses. For information on examining addresses refer "display" functionality. $frame Setting this variable to an address alters dbx's idea of the current stack frame. $expandunions Causes dbx to display values of each part of variant records or unions. $hexin $octin When set, dbx interprets addresses in hexadecimal or octal. $hexchars $hexints $hexstrings When set, dbx prints characters, integers or character pointers in hexadecimal. $noargs When set, dbx omits arguments from subcommands, such as where, up, down, and dump. $noflregs When set, dbx omits the display of floating-point registers from the registers subcommand. $novregs When set, dbx omits the display of vector registers from the registers subcommand. $novsregs When set, dbx omits the display of vector scalar registers from the registers subcommand. $octints When set, dbx prints integers in octal. $ignoreifhandler When set, dbx suppresses notification of signals which have a registered handler. $ignoreload When set, dbx ignores load(), unload(), or loadbind() subroutines performed by your program. $ignorenonbptrap When set, dbx suppresses notification of non-breakpoint trap instructions that trigger when a SIGTRAP handler is registered. $instructionset Specifies the default disassembly mode. To change the value, the user should type 'set $instructionset = ""'. If the $instructionset variable is unset, it will behave as if the value was "default". The following are the valid values for $instructionset: "default" - Disassemble using the instruction set for the hardware architecture dbx is running on. "com" - Disassemble using the instruction set that is common between Power and PowerPC architectures. The mnemonics will default to PowerPC mnemonics. "pwr" - Disassemble using the instruction set for the RS1 implementation of the Power architecture. The mnemonics will default to Power mnemonics. "pwrx" - Disassemble using the instruction set for the RS2 implementation of Power architecture. The mnemonics will default to Power mnemonics. "pwr6" - Disassemble using the instruction set for the POWER6 implementation of PowerPC architecture. The mnemonics will default to PowerPC mnemonics. "pwr7" - Disassemble using the instruction set for the Power 7 implementation of PowerPC architecture. The mnemonics will default to PowerPC mnemonics. "ppc" - Disassemble using the instruction set for the PowerPC architecture. The mnemonics will default to PowerPC mnemonics. "601" - Disassemble using the instruction set for the 601 implementation of PowerPC architecture. The mnemonics will default to PowerPC mnemonics. "603" - Disassemble using the instruction set for the 603 implementation of PowerPC architecture. The mnemonics will default to PowerPC mnemonics. "604" - Disassemble using the instruction set for the 604 implementation of PowerPC architecture. The mnemonics will default to PowerPC mnemonics. "970" - Disassemble using the instruction set for the 970 implementation of PowerPC architecture. The mnemonics will default to PowerPC mnemonics. "any" - Disassemble using any valid instruction from either Power or PowerPC architecture. The mnemonics will default to PowerPC mnemonics $java When set, also sets the following variables, placing dbx in a mode to debug Java applications. When unset, also unsets the following variables: $ignorenonbptrap Suppresses notification of trap instructions generated by the Java Just-In-Time (JIT) compiler. $listwindow Specifies the number of lines to list and listi commands. Breakpoint/Trace subcommands: stop - set breakpoint in program stophwp - set a hardware watchpoint stop trace - set trace in program tracehwp - set a hardware watchpoint trace status - print active breakpoints and traces with associated dbx subcommands addcmd - add dbx subcommands to given event numbers delcmd - delete dbx subcommands from given event number delete - remove traces or breakpoints of given numbers clear - remove all breakpoints and traces at given line stopi - set a breakpoint at a specified address tracei - turn on instruction tracing cleari - remove all breakpoints and traces at given address The following "set" variables have special meanings: $catchbp When set, dbx catches breakpoints during execution of the next command. $codepage Specifies the code set the characters of the debugee are encoded to. The code page is set by typing 'set $codepage = ""'. $compact_bt_ident Specifies a limit on the number of characters of the identifier name to be printed when showing a stack trace. To assign a value, type 'set $compact_bt_ident=' where is a positive integer between 4 and 128. If 'set $compact_bt_ident' is entered, default will be taken as 8. Once specified, when printing a stack trace, dbx will print number of characters of an identifier and then print three '.' if the original identifier's length is three more than . $compact_bt_string Specifies a limit on the number of characters of a function argument that is a string is to be printed when showing a stack trace. To assign a value type 'set $compact_bt_string=' where is a positive integer between 4 and 128. If 'set $compact_bt_string' is entered, default will be taken as 8. Once specified, when printing a stack trace, dbx will print number of characters of a function argument string and then print three '.' if the original string's length is three more than . $display_address_name Instructs dbx to try to display the variable/function names when examining memory addresses. For information on examining addresses refer "display" functionality. $frame Setting this variable to an address alters dbx's idea of the current stack frame. $expandunions Causes dbx to display values of each part of variant records or unions. $hexin $octin When set, dbx interprets addresses in hexadecimal or octal. $hexchars $hexints $hexstrings When set, dbx prints characters, integers or character pointers in hexadecimal. $noargs When set, dbx omits arguments from subcommands, such as where, up, down, and dump. $noflregs When set, dbx omits the display of floating-point registers from the registers subcommand. $novregs When set, dbx omits the display of vector registers from the registers subcommand. $novsregs When set, dbx omits the display of vector scalar registers from the registers subcommand. $octints When set, dbx prints integers in octal. $ignoreifhandler When set, dbx suppresses notification of signals which have a registered handler. $ignoreload When set, dbx ignores load(), unload(), or loadbind() subroutines performed by your program. $ignorenonbptrap When set, dbx suppresses notification of non-breakpoint trap instructions that trigger when a SIGTRAP handler is registered. $instructionset Specifies the default disassembly mode. To change the value, the user should type 'set $instructionset = ""'. If the $instructionset variable is unset, it will behave as if the value was "default". The following are the valid values for $instructionset: "default" - Disassemble using the instruction set for the hardware architecture dbx is running on. "com" - Disassemble using the instruction set that is common between Power and PowerPC architectures. The mnemonics will default to PowerPC mnemonics. "pwr" - Disassemble using the instruction set for the RS1 implementation of the Power architecture. The mnemonics will default to Power mnemonics. "pwrx" - Disassemble using the instruction set for the RS2 implementation of Power architecture. The mnemonics will default to Power mnemonics. "pwr6" - Disassemble using the instruction set for the POWER6 implementation of PowerPC architecture. The mnemonics will default to PowerPC mnemonics. "pwr7" - Disassemble using the instruction set for the Power 7 implementation of PowerPC architecture. The mnemonics will default to PowerPC mnemonics. "pwr8" - Disassemble using the instruction set for the Power 8 implementation of PowerPC architecture. The mnemonics will default to PowerPC mnemonics. "ppc" - Disassemble using the instruction set for the PowerPC architecture. The mnemonics will default to PowerPC mnemonics. "601" - Disassemble using the instruction set for the 601 implementation of PowerPC architecture. The mnemonics will default to PowerPC mnemonics. "603" - Disassemble using the instruction set for the 603 implementation of PowerPC architecture. The mnemonics will default to PowerPC mnemonics. "604" - Disassemble using the instruction set for the 604 implementation of PowerPC architecture. The mnemonics will default to PowerPC mnemonics. "970" - Disassemble using the instruction set for the 970 implementation of PowerPC architecture. The mnemonics will default to PowerPC mnemonics. "any" - Disassemble using any valid instruction from either Power or PowerPC architecture. The mnemonics will default to PowerPC mnemonics $java When set, also sets the following variables, placing dbx in a mode to debug Java applications. When unset, also unsets the following variables: $ignorenonbptrap Suppresses notification of trap instructions generated by the Java Just-In-Time (JIT) compiler. $listwindow Specifies the number of lines to list and listi commands. tm_status The tm_status command displays the contents of the $texasr (Transaction Exception And Summary Register) and interprets it to explain the cause and nature of a Transaction failure. list [ [, ]] list list at
List the lines in the current source file from the first line number to the second inclusive. If no lines are specified, the next 10 lines are listed. If the name of a procedure or function is given lines n-k to n+k are listed where n is the first statement in the procedure or function and k is defined by $listwindow By specifying an address in the text segment of the debuggee as the Address parameter preceded by "at", the list subcommand displays the source lines that correspond to the Address from the debuggee's text segment. Address can be specified as decimal or hexadecimal unsigned integer, or mnemonic corresponding to registers ($iar, $tfiar, $tfhar etc.) or debuggee variables. $mapaddrs When set, dbx starts address mapping, useful for kernel debugging. $mapformat Specifies the default output format for the map subcommand. To change the value, the user should type 'set $mapformat = ""'. If the $mapformat variable is unset, it will behave as if the value was "normal". The following are the valid values for $mapformat: "abbr" - Map output will consist of a single line containing the entry number, module name, and member name. "normal" - Map output will consist of the entry number, module name, member name, text origin, text length, data origin, data length, and file descriptor. If the module has TLS data, then TLS data origin and TLS data length will also be for the specified thread or the current thread, if no thread has been specified. "raw" - Map output will consist of a single unformatted line containing the following space-separated fields: entry number, module name with optional member name, text origin, text end, text length, data origin, data end, data length, and file descriptor. If the module has TLS data, then TLS data origin, TLS data end and the TLS data length will be displayed for the specified thread or the current thread, if no thread has been specified. "verbose" - Map output will consist of the entry number, module name, member name, text origin, text end, text length, data origin, data end, data length, and file descriptor. If the module has TLS data, then TLS data origin, TLS data end and the TLS data length will be displayed for the specified thread or the current thread, if no thread has been specified. $menuwindow Specifies the number of lines to list when prompting users for choices. $mnemonics Specifies the set of mnemonics used for disassembly. To change the value, the user should type 'set $mnemonics = ""'. If the $mnemonics variable is unset, it will behave as if the value was "default". The following are the valid values for $mnemonics: "default" - Disassemble using the mnemonics which most closely match the specified instruction set. "pwr" - Disassemble using the mnemonics for the Power architecture. "ppc" - Disassemble using the mnemonics for the PowerPC architecture. $print_dynamic When set, prints the dynamic type of an object in C++. Code has to be compiled with -qrtti option for the RTTI data to be present. $print_fullname When set, dbx prints the fully-qualified identifier, even in cases where there is no apparent ambiguity. $print_mangled When debugging C++ code, setting this variable causes dbx to print mangled identifiers. $repeat When set, dbx repeats the previous command if no command was entered. $sigblock When set, dbx blocks signals to your program. $showbases When set, dbx displays base classes of C++ class types. $show_vft When set, prints Virtual Function table present in C++ objects, if available. $showblocks When set, dbx prints unnamed blocks in location output. $stepignore Specifies the behavior of the "step\tstep" subcommand on a source line calling another routine with no debugging information. To change the value, the user should type 'set $stepignore = ""'. If the $stepignore variable is unset, it will behave as if the value was "function". The following are the valid values for $stepignore: "function" - dbx will behave as if subcommand "next\tnext" was issued. "module" - if function is in load module with no debug information (such as a system library), dbx will behave as if subcommand "next\tnext" was issued. "none" - dbx will "stepi\tstepi" until it reaches an instruction with source information. $unsafecall $unsafeassign $unsafegoto $unsafebounds Turn off type checking for calls, assignments, goto and array bounds checking. $vardim Specifies the dimension length to use when printing arrays with unknown bounds $deferevents Turns on the deferred events feature. $stack_details Displays the frame number and the register set for each active function/procedure displayed by the "where" subcommand. $trace_good_transaction Instructs dbx to display the message "Process {PID} may have performed a transaction $texasr, $tfiar and $tfhar are valid and may be inspected", every time a TM Transaction is completed successfully. This variable is disabled by default and therefore successful transactions are not reported. The following "set" variables have special meanings: $catchbp When set, dbx catches breakpoints during execution of the next command. $codepage Specifies the code set the characters of the debugee are encoded to. The code page is set by typing 'set $codepage = ""'. $compact_bt_ident Specifies a limit on the number of characters of the identifier name to be printed when showing a stack trace. To assign a value, type 'set $compact_bt_ident=' where is a positive integer between 4 and 128. If 'set $compact_bt_ident' is entered, default will be taken as 8. Once specified, when printing a stack trace, dbx will print number of characters of an identifier and then print three '.' if the original identifier's length is three more than . $compact_bt_string Specifies a limit on the number of characters of a function argument that is a string is to be printed when showing a stack trace. To assign a value type 'set $compact_bt_string=' where is a positive integer between 4 and 128. If 'set $compact_bt_string' is entered, default will be taken as 8. Once specified, when printing a stack trace, dbx will print number of characters of a function argument string and then print three '.' if the original string's length is three more than . $display_address_name Instructs dbx to try to display the variable/function names when examining memory addresses. For information on examining addresses refer "display" functionality. $frame Setting this variable to an address alters dbx's idea of the current stack frame. $expandunions Causes dbx to display values of each part of variant records or unions. $hexin $octin When set, dbx interprets addresses in hexadecimal or octal. $hexchars $hexints $hexstrings When set, dbx prints characters, integers or character pointers in hexadecimal. $noargs When set, dbx omits arguments from subcommands, such as where, up, down, and dump. $noflregs When set, dbx omits the display of floating-point registers from the registers subcommand. $novregs When set, dbx omits the display of vector registers from the registers subcommand. $novsregs When set, dbx omits the display of vector scalar registers from the registers subcommand. $octints When set, dbx prints integers in octal. $ignoreifhandler When set, dbx suppresses notification of signals which have a registered handler. $ignoreload When set, dbx ignores load(), unload(), or loadbind() subroutines performed by your program. $ignorenonbptrap When set, dbx suppresses notification of non-breakpoint trap instructions that trigger when a SIGTRAP handler is registered. $instructionset Specifies the default disassembly mode. To change the value, the user should type 'set $instructionset = ""'. If the $instructionset variable is unset, it will behave as if the value was "default". The following are the valid values for $instructionset: "default" - Disassemble using the instruction set for the hardware architecture dbx is running on. "com" - Disassemble using the instruction set that is common between Power and PowerPC architectures. The mnemonics will default to PowerPC mnemonics. "pwr" - Disassemble using the instruction set for the RS1 implementation of the Power architecture. The mnemonics will default to Power mnemonics. "pwrx" - Disassemble using the instruction set for the RS2 implementation of Power architecture. The mnemonics will default to Power mnemonics. "pwr6" - Disassemble using the instruction set for the POWER6 implementation of PowerPC architecture. The mnemonics will default to PowerPC mnemonics. "pwr7" - Disassemble using the instruction set for the Power 7 implementation of PowerPC architecture. The mnemonics will default to PowerPC mnemonics. "pwr8" - Disassemble using the instruction set for the Power 8 implementation of PowerPC architecture. The mnemonics will default to PowerPC mnemonics. "pwr9" - Disassemble using the instruction set for the Power 9 implementation of PowerPC architecture. The mnemonics will default to PowerPC mnemonics. "ppc" - Disassemble using the instruction set for the PowerPC architecture. The mnemonics will default to PowerPC mnemonics. "601" - Disassemble using the instruction set for the 601 implementation of PowerPC architecture. The mnemonics will default to PowerPC mnemonics. "603" - Disassemble using the instruction set for the 603 implementation of PowerPC architecture. The mnemonics will default to PowerPC mnemonics. "604" - Disassemble using the instruction set for the 604 implementation of PowerPC architecture. The mnemonics will default to PowerPC mnemonics. "970" - Disassemble using the instruction set for the 970 implementation of PowerPC architecture. The mnemonics will default to PowerPC mnemonics. "any" - Disassemble using any valid instruction from either Power or PowerPC architecture. The mnemonics will default to PowerPC mnemonics $java When set, also sets the following variables, placing dbx in a mode to debug Java applications. When unset, also unsets the following variables: $ignorenonbptrap Suppresses notification of trap instructions generated by the Java Just-In-Time (JIT) compiler. $listwindow Specifies the number of lines to list and listi commands. run and rerun may be used only on originating process. Nested subarrays are illegal.Illegal use of subarrays.Usage: mutex [wait | nowait | lock | unlock | ] Usage: condition [wait | nowait | ] Usage: attribute [] Usage: thread [ hold | unhold | info | current | run_next | run | ready | susp | term ] [thread#] '$t%d' is not an existing thread.no thread availableUsage: mutex [ lock | unlock | ] Usage: condition [wait | nowait | ] Usage: attribute [] Usage: thread [ hold | unhold | info | current | wait run | susp | term ] [thread#] '$t%lld' is not an existing thread.no thread availablekernel thread id=%d not foundall threads held1283-246 could not access to procsinfo errno %d1283-247 could not access to thrdsinfo errno %d1283-248 thread with signal not found1283-249 malloc errorUsage: "thread [run | wait | susp | term] " takes no id Usage: "mutex { lock | unlock }" takes no id '$a%lld' is not an existing attribute.'$m%lld' is not an existing mutex.'$c%lld' is not an existing condition.Usage: mutex [ lock | unlock | thnum | utid | ] Usage: thread [ hold | unhold | info | current | wait run | susp | term ] [-] [thread#] Usage: "thread [run | wait | susp | term] [-]" takes no id Thread is in kernel mode, not all registers can be accessed.Cannot modify registers for current thread.Usage: "spinlock { lock | unlock }" takes no id Usage: spinlock [ lock | unlock | thnum | utid | ] '$s%lld' is not an existing spinlock.Usage: barrier [wait | nowait | ] '$b%lld' is not an existing barrier.Thread = %lld: Key %lld : Data Ptr = 0x%pKey %lld is Invalid. warningfatal errorinternal errorUsage: "rwlock { read | write }" takes no id rwlock - list existing rw locksUsage: "mutex { thnum | utid }" takes id rwlock [> ] rwlock [ ...] [> ] rwlock [read | write] [> ] Print the current status of all known rwlocks in the process. RWlocks to be listed can be specified through the parameters, or all rwlocks will be listed. Users can also select rwlocks only in either read mode or in write mode using the options read or write. Usage: rwlock [ read | write | ] '$rw%lld' is not an existing rwlock.thread '-' The information displayed by the 'th -' subcommand is given below. By default the 'th -' subcommand displays the information in the long form. thread Indicates the symbolic name of the user thread, in the form $t ThreadNumber. (kernel thread related information) tid Indicates the kernel thread identifier (if the user thread is attached to a kernel thread). pri Indicates the priority of the kernel thread. sched Indicates the scheduling policy of the kernel thread. This can be fif, oth, rr, for fifo, other, or round robin scheduling policies. state Indicates the state of the kernel thread (if the user thread is attached to a kernel thread). This can be run , wait , susp , or zomb , for running, waiting, suspended, or zombie. (user thread realted information) tid Indicates the user thread identifier. pri Indicates the priority of the user thread. nice Indicates the nice value of a user thread. sched Indicates the scheduling policy of the user thread. This can be fif, oth, rr, for fifo, other, or round robin scheduling policies. state Indicates the state of the user thread.This can be running, creating, suspended, blocked, runnable or terminated. state Indicates the user state in hex. flags Indicates the values for pthread flags in hex. wchan Indicates the event on which the kernel thread is waiting or sleeping (if the user thread is attached to a kernel thread). mode Indicates the mode (kernel or user) in which the user thread is stopped (if the user thread is attached to a kernel thread). held Indicates whether the user thread has been held. scope Indicates the contention scope of the user thread; this can be sys or pro for system or process contention scope. cancellation pending Indicates if cancellation is pending or not. state Indicates the mode and state of cancellation. If the cancellation is not pending and the state and mode is enabled and deferred respectively, then it is represented by 'ed', if cancellation state and mode is enabled and asynchronous then it is represented by 'ea', and if mode is not enabled then it is represented by 'd'. If the cancellation is pending and the cancellation state and mode is enabled and deferred respectively, then it is represented by 'ED', if cancellation state and mode is enabled and asynchronous then it is represented by 'EA', and if mode is not enabled then it is represented by 'D'. joinable Indicates whether the thread is joinable or not. boosted Indicates the boosted value of the thread. function Indicates the name of the user thread function. cursig Indicates the current signal value. If the option 'set $thcomp' is set then the information is displayed in the compressed form as shown below. m mode (k)ernel (u)ser k k-state (r)unning (w)aiting (s)uspended (z)ombie u u-state (r)unning (R)unnable (s)uspended (t)erminated (b)locked (c)reating h held (y)es (n)o s scope (s)ystem (p)rocess c cancellation not pending: (e)nabled & (d)eferred, (e)nabled & (a)sync, (d)isabled pending : (E)nabled & (D)eferred, (E)nabled & (A)sync, (D)isabled j joinable (y)es (n)o b boosted value of boosted field in pthread structure kpl kernel thread (oth)er (fif)o (rr)-> round-robin policy upl user thread (oth)er (fif)o (rr)-> round-robin policy kpr kernel thread hex number policy upr user thread hex number policy unc user thread hex number nice value k-tid kernel thread id in hex u-tid pthread id in hex fl value of flags field in pthread structure in hex sta value of state field in pthread structure in hex cs value of current signal wchan event for which thread is waiting function function name Invalid tid requested.Invalid fd(s) requested.No file descriptors open.Usage: "spinlock { thnum | utid }" takes id plug-in "%s" loaded plug-in "%s" unloaded could not load plug-in "%s": load operation failed function "%s" not exported plug-in "%s" already loaded unrecognized version (%x) initialization failed plug-in "%s" cannot redefine alias "%s" no plugins no such plugin: "%s" invalid plug-in name libcdebug.a cannot be initialized. Process is not user-key enabled. Enabled keys:No user-key exception structure in the core file. User Exception Data: Exception Address Key: Exception Address: Bad Address.The malloc subsystem has not been initialized yet. The following options are enabled: Implementation Algorithm........ Default Allocator (Yorktown) 3.1 Allocator Watson Allocator Unknown Malloc Threadcache Malloc Buckets Number of Buckets....... %d Blocks per Bucket....... %d Bucket Sizing Factor.... %d Largest Bucket Size..... %d Bucket Statistics....... 0x%llx Malloc Adaptive Buckets Malloc Heapcache Malloc Disclaim Malloc Multiheap Number of Heaps......... %d Consider Size atexit Heap Statistics Malloc Detect Check Arena Verbose Error Messages Malloc Catch Overflow Debug Range............. %lld.. %lld Function Set............ Alignment............... %d Override Signals Allow Overreading Malloc Log Stack Depth............. %d Extended Log Data Report Allocations Validate Pointers Post-Free Checking Malloc Trace Debug Output.............. %32s Debug Continue Statistical Report on the Malloc Subsystem: Heap %d heap lock held by................ pthread ID 0x%llx heap lock held by................ UNLOCKED bytes acquired from sbrk()....... %12lld bytes in the freespace tree...... %12lld bytes held by the user........... %12lld allocations currently active..... %12lld allocations since process start.. %12lld Total: The Process Heap Initial process brk value........ 0x%0*llx current process brk value........ 0x%0*llx sbrk()s called by malloc......... %*lld Malloc Log must be enabled in order to view active allocations Allocations Held by the Process: Allocations Held by the Process Matching Search Criteria: %*s %*s %*s %*s STACK TRACEBACK %*s %*s %*s %*s %*s %*s %*s STACK TRACEBACK Queries on the %s field are only possible when Extended Malloc Log is enabled ADDRESSSIZEHEAPPIDPTHREAD_TSEQCLOCKTIMEFreespace Held by the Malloc Subsystem: Freespace Held by the Malloc Subsystem Matching Search Criteria: Address 0x%p node details : ALLOCATORStatus : ALLOCATED Status : FREE ~= operator can be only used with address option. Watson2 Allocator Undefined Extended opcode 0x%x Undefined Special opcode 0x%x Undefined TAG value 0x%x Failed to get debug information entry offset: 0x%08x for compilation unit %s . Some info many not be available.Undefined attribute 0x%x Failed to memory map for %s section Invalid parent entry for child offest 0x%08x(Skipping). Some information may not be available.Line pool errorImproper end of sequence.Invalid dwarf header version : %dInvalid dwarf address size : %dUnable to obtain the abbreviation table for the compilation unit %s The .dwline section doesn't contain line number information for file %s Invalid dwarf line version : %d