Manuals / HP / Computer Equipment / Computer Hardware

HP gnu source-level debugger 5992-4701 manual Commonblockname, Block, Fortran special issues

Models: gnu source-level debugger 5992-4701

1 369

Page 114

info common	Lists values of variables in the named common
<common_block_name>	block.
Fortran entry points are supported.

You can set a break point specifying an entry point name.

9.4.2.3 Fortran special issues

Fortran allows main to be a non-main procedure; therefore, to set a breakpoint in the main program, use break _MAIN_ or break <program_name>.

Do not use break main unless it is the name of a non-main procedure.

114 Using GDB with Different Languages

Page 114

Image 114

HP gnu source-level debugger 5992-4701 manual Commonblockname, Block, Fortran special issues

Contents

Debugging with GDB Manual Page Table of Contents Breakpoints Continuing and stepping SignalsPrint settings Value history Stack framesExamining the Symbol Table Specifying a Debugging Target Batch Mode Stop when freeing unallocated or deallocated blocksScramble previous memory contents at malloc/free calls Commands for heap profilingEnhancements to the dumpcore command Support for the info target CommandSupport for the dumpcore command Example Illustrating Execution Path RecoveryDebugging the application using GDB under Aries Command for evaluating the address of an expressionSupport for steplast command for C and C++ Detecting memory leaks using GDB under AriesHP-UX Terminal User Interface User-defined commands 287 18.2 Miscellaneous commands 265 16.3Setting Command History Feature in GDB 281 17.4 Command files 289 Commands for controlled output 29020.9 Invalidation notices 303 20.7 Errors 302 20.822.2 How to report bugs 361 304List of Tables List of Examples Summary of GDB Free SoftwareContributors to GDB Page Contributors to GDB Page Let us use GDB to try to see what is going on Sample GDB SessionLoading the Executable Here we describe how to set a breakpoint Setting Display widthSetting Breakpoints Running the executable under GDBStepping into a subroutine Examining the StackPrinting Variable Values Setting Variable Values During a Session Listing Source CodeGdb c Continuing Definebaz,defnQUOTEfooUNQUOTE Baz Page Getting In and Out of GDB Invoking GDBChoosing files FilesProcessed. See Command files Choosing modesTime a stack frame is displayed which includes each GNU Emacs sets this option when it runs GDB as aLine number in a standard, recognizable fashion each Like two `\032 characters, followed by the file nameEmacs Quitting GDB Redirecting WDB input and output to a fileInterface Shell commands Page GDB Commands Command syntaxCommand completion GDB sounds bell press TAB again, to see Short list of named classes of commands Getting helpHelp , h Complete Apropos reloadResults This is intended for use by GNU EmacsGetting help Page Starting your program Running Programs Under GDBCompiling for debugging Arguments, so that you may use normalSee Arguments To Your Program Your program. SeeProgram EnvironmentDirectory Arguments To Your Program Program EnvironmentProgram. See Program Input and Output Path environment variable For example, this commandDisplay the list of search paths for executables Do not supply varname, print the namesWorking directory Program Input and OutputDebugging a Running Process Killing the child process Debugging programs with multiple threads New process 35 thread With the command argument threadno Here are commands to get more information about threadsThread apply command allows you to Display a summary of all threads currentlyDebugging programs with multiple processes Set the debugger response to a program call New process. The mode can beUnimpeded. This is the default Fork. The child process runsStopping and Continuing BreakpointsSetting breakpoints See Break conditions page 59, for more BreakpointsWhether BreakpointCatchpoint Breakpoint isMarked to be When hitEnabled Breakpoints areSetting catchpoints Unloading of any dynamically loaded Call to vfork. This is currently onlyIs currently only available for HP-UX Shared library, or the unloadingDeleting breakpoints Disabling breakpointsSelecting a frame page 73 . When Break conditions Stops your program only if the value Breakpoint, GDB prints an error messageNo symbol foo in current context Use condition, GDB checks expressionBreakpoint command lists Breakpoint menus Cannot insert breakpoints Continuing and stepping ConditionsFunction Setting breakpoints page 52. This form of the command Signals Stops. See Automatic displayInfo handle is an alias for info signals Stopping and starting multi-thread programs Stopping and Continuing Examining the Stack Stack framesCommands for Examining the Stack Stacks Without framesBacktraces Selecting a frame With an argument, this command is used to select a stack Have existed longer. n defaults to oneWhen used without any argument, this command does not Information about a frameSetting catchpoints Page List Examining Source FilesPrinting source lines Show listsizeSearching source files Specifying source directories Source and machine code Show directoriesContains Select the instruction set to use when Set disassembly-flavorDisassemble or x/i commands Disassembling the program viaPage Expressions Following forms of print command are supportedExamining Data To See Artificial arrays page 85, for more informationType addr Where it is defined. See Program variablesProgram variables Normally supposed to reside at addrYou can print the contents of array with Artificial arraysOutput formats Print, s null-terminated string, or Machine instruction. The default isExamining memory Time you use either x or printHowever, the count n must come first wx4 does not work See Output formats Automatic displayFor fmt specifying only a display format and not a size or For fmt i or s, or including a unit-size or a numberPrint settings Symbolic form of an address A symbol. This is the defaultFile name and line number of a symbol AddressSetting number-of-elementsto zero Default is offStrings. When GDB starts, this limit is set to Short strings. The default is offPrint using only seven-bit characters if this This is the default formatShow which format GDB is using to print DefaultShow whether C++ names in assembly listings These settings are of interest when debugging C++ programsDefault is on Would printValue history Convenience variables $exitcode Command, in which case it is a pointer to the type of $Format in which the data was printed Program being debugged terminatesOr print the instruction to be executed next with RegistersInfo registers Info all-registers Info registers regname Or add four to the stack pointer3 with3withTo get the bit pattern, try the following macro Printing Floating Point ValuesFloating point hardware This is what the macro produces100 List of filename extensions and languages Using GDB with Different LanguagesSwitching between source languages CppHaving GDB infer the source language Setting the working languageNot skip over function prologues when stepping FilesDisplaying the language Type and range checkingAn overview of type checking An overview of range checking Supported languages C++ Left shift, and right shift. Defined on integral types Expressions is 0 for false and non-zero for trueNon-zero for true Types and pointer typesExpressions page 83. Same precedence as , above Class typesDouble colons also represent the GDB scope operator see C++ constants1.3 C++ expressions GDB expression handling can interpret most C++ expressionsC++ defaults Printing the variable or class returnsC++ type and range checks Breakpoint menus GDB features for C++GDB and C See Breakpoint menusFortran Fortran typesFortran types supported Greater than Less thanLess than or equal to Greater than or equal toFortran special issues CommonblocknameBlock Examining the Symbol Table Symbols will be read when needed Two commands give this outputAs with whatis, using ptype without an For example, for this variable declarationDo not replace symbol Allow GDB to reload the symbols forReplace symbol definitions Once. This is the defaultTell GDB to resolve opaque types. An opaque SettingIs in another source file. The default is on Class, or union―for example, structAltering Execution Assignment to variablesContinuing at a different address Stores the value 4 into that memory locationGiving your program a signal You can use the following command to return from a functionReturning from a function Return , return Calling program functionsPatching programs Is used as the return value from the function valuePatching programs 124 Commands to specify files GDB FilesSee Optional warnings and messages Write the symbols for your program into a Option with any of the commands that loadGDB has the entire symbol table available Map in symbol information from this auxiliarySection If threshold is nonzero, symbols from all Symbols were loaded. Both the commands listTo display or set the threshold, use the commands New library has been loaded, until the symbolSpecifying shared library locations Names where the desired shared libraries reside. GDBSearching the default system directories MegabytesErrors reading symbol files Verbose on. See Optional warningsMessages GDB circumvents the error by ignoring this Symbol scope block as starting on the previousIs the symbol type of the uncomprehended Debug your program, though certain symbolsCommands for managing targets Specifying a Debugging TargetActive targets See Commands to specify files Choosing target byte order Executable Instruct GDB to assume the target is big-endianInstruct GDB to assume the target is little-endian Display GDBs current idea of the target byte orderHP-UX Configuration-Specific Information Summary of HP Enhancements to GDBImplementation of ask mode for set follow-fork-mode Support for setting breakpoints using shared library nameCommand watchtarget HP-UX dependencies Linker DependenciesDependent Standard Library Routines for Run Time Checking Abort Unlink Atoi Getpid Close Srand StrchrSupported Platforms and Modes WDB Location HP-UX targetsSupport for Alternate root GDB locationNone Specifying object file directoriesLibrtc.sl location $WDBROOT/bin Opt/langtools/ n/a Bin $WDBROOT/binFix and continue debugging Fix and Continue compiler dependencies Fix and Continue restrictionsUsing Fix and Continue Example Fix and Continue session Compile the programRun the program Gdb edit Gdb b mainGdb run Make the necessary changes. In this case, add return totalInline Support Inline Debugging in HP 9000 SystemsGdb q Inline Debugging in Integrity Systems Breakpoint info frame disassemblyFollowing options available for the set inline-debugcommand Step next list backtrace frame n info locals info argsLimitations Debugging Inline Functions in Integrity SystemsInfo frame disassembly Debugging MacrosViewing and Evaluating Macro Definitions Compiler Options to Enable Macro Debugging Evaluating MacrosDebug=none Examples for Macro Debugging HP-UX Configuration-Specific Information Debugging Memory Problems When to suspect a memory leak Memory debugging restrictionsMemory Debugging Methodologies Debugging Memory in Interactive Mode Heap growth. The default value is 100. Every Displays all current settings for memoryThis command are ignored from report. If Command discards the data existing in the fileDebugging Memory Problems Specific pattern when it is allocated or Debugging when the string option is set forHave occurred and WDB reports the problem Such as attempting to access space that is freedNumber of bytes, the debugger ignores it Use the info command to show list of memory leaksIf the user specifies a value less than 16 for User-specified valueDebugging Memory in Batch Mode Setting Configuration Options for Batch ModeGdb info leak Framecount=noframes or set heap-check frame-count noframes Sets the number of frames to be printed for leak contextFor 64 bit PA applications For 32 bit IPF applicationsFor 64 bit IPF applications For 64-bit IPF applicationsEnvironment variable setting for Batch mode debugging LdpreloadLog file for batch mode must be Aborts execution when heap objectsAborts execution when out of memory Stderr error message goes to stderrExample for Batch Mode RTC Complete one of the following steps Rtcconfig file should contain entries such as the following Preload the librtc library as followsRun the program as follows For 32 bit PA applications Specifying the stack depth Configuring memory debugging settingsRun the program Start a debugging session as follows Specifying minimum leak sizeFor example, if you use Stop when freeing unallocated or deallocated blocksScenarios in memory debugging Specifying minimum block sizeSyntax Scramble previous memory contents at malloc/free callsInteractive debugging mode set heap-check scramble on off Detect dangling pointers and dangling blocksDetect in-block corruption of freed blocks Memory Debugging Commands in Interactive and Batch Mode OffHeap Profiling Commands for heap profilingPoint you use the info heap command As the start of the heap, end of the heap, heapThis example shows how to use this feature on HP-UX Set a breakpointCommands to track the change in data segment value Changes for a given runThread Debugging Support Support for Enabling and Disabling Specific ThreadsBacktrace Support for Thread Debugging Advanced Thread Debugging SupportEnabling and Disabling Advanced Thread Debugging Features Pre-requisites for Advanced Thread DebuggingMixed-sched-policy onoff The set thread-check Onoff command checks if an applicationUnlock-not-own onoff The set thread-check unlock-not-own Cv-multiple-mxs onoff The set thread-check cv-multiple-mxsCommand checks if any thread has terminated This returns an Einval error toUser and prints a warning message when this Different mutexes. The debugger transfersException or a cancel without joining or When this condition is detected. This situationCommand checks if a thread has terminated Created with the detach attribute. When anCondvar-id is provided, the command displays Provided, the command displays extendedIs provided, the command displays extended Rwlock-id is provided, the command displaysFor 64-bit PA applications Thread Debugging in Batch Mode Pre-requisites for Batch mode of Thread Debugging For 64 bit IPF applications, setFor 64-bit PA applications, set And/Or Set the environment variable Batchrtc to on asOpt/langtools/lib/hpux64/librtc.so Thread Debugging in +check Mode Where Pid is the process idLimitations in Batch mode of thread debugging Where pid is the process identifier IssueDebugging MPI Programs Support for showing unwind info Ask mode for set follow-fork-modeSerial mode for set follow-fork-mode Debugger response to a program call to fork or vfork is askCommand to Search for a Pattern in the Memory Address Space Printing CFM and PFS registersString value. The character pattern must be enclosed Parameter is mandatory when end-addressis notSpecifies the length of the memory address range. This Within double quotes. This parameter is mandatoryExample 14-1 Sample Output for the find command Str0 Specifies the starting address Using the /max-countparameterUsing the /size-charparameter Specifies the pattern expr1Debugging Core Files Generating core files with packcore /unpackcore/getcoreSupport for the info target Command When starting from the shell prompt Support for the dumpcore commandWhen starting from the HP WDB command line Enhancements to the dumpcore commandInfo rtti address When starting from shell promptSupport for display of run time type information Sample OutputInfo exec-path summary Info global-exec-path summaryExec-path updownpathindex aliased to ep Example Illustrating Execution Path Recovery Sample ProgramSample Debugging Session Command to Unwind Beyond 10000 Frames Aborting a Command Line Call Invoking GDB Before a Program AbortsDeferred watchpoints Instruction Level SteppingEnhanced support for watchpoints and breakpoints Hardware watchpointsRbp Support for procedural breakpointsSupport for template breakpoints RdpUsing shared library as main program Debugging support for shared librariesSetting Deferred Breakpoints in Shared Library Using catch loadPrivately mapping shared libraries Selectively Mapping Shared Libraries As Private Opt/langtools/bin/pxdb -s on executable-nameDebugging support for Decimal Floating Point data type Setting breakpoints in shared libraryEnhancement to the info shared Command Printing Decimal Floating point data typesHandling Decimal Floating Point Data types Following are sample commands to print NaT registersPrinting NaT Registers Evaluating Decimal Floating Point data typesComparison Operations Assignment of Decimal floating point value to variableArithmetic Operations Printing type of Decimal Floating Point variableThis prints the binary floating point value as oat Additional Support for binary floating point data typeSupport for Binary Floating Point constants f, l This prints the binary floating point value as doubleJava Stack Unwind Features Language supportEnhanced Java Debugging Support Gdb Subcommands for Java VM Debugging Gdb help javaInfo frame Frame command of GDB has been enhanced to interpret a JavaJava and native stack frames Stack frameJava attach mode debugging support Java corefile debugging supportEnhanced support for C++ templates SyntaxSupport for fpreg data type on IPF Support for Complex variables in HP CSupport for debugging namespaces Command for evaluating the address of an expression Viewing Wide Character StringsThis is equivalent to executing Support for output logging Support for dumping array in an Ascii fileDisplaying enumerators Support for steplast command for C and C++Support for Fortran array slices Support for debugging typedefsGetting information from a non-debug executable Debugging optimized code Break Call Clear Disassem ListBreak Call Cond Jump Return Print Set var Watch Whatis HP-UX Configuration-Specific Information Debugging Optimized Code at Various Optimization Levels 14.29.1.1 +O0 and +O114.29.1.2 +O2/+O3/+O4/-ipo Following limitations apply when debugging optimized code Debugging with Aries+O2 or -O Debugging the application using GDB under Aries Limitations of GDB Support under AriesDetecting memory leaks using GDB under Aries Attaching GDB to an already running emulated processVisual Interface for WDB Starting and stopping Visual Interface for WDBNavigating the Visual Interface for WDB display Visual Interface for WDB GUI displayUsing the X-window graphical interface Specifying foreground and background colorsUsing the TUI mode Changing the size of the source or debugger paneFor dterm, use the following Saving the contents of a debugging session to a file Using commands to browse through source filesEditing the command line and command-line history Loading source filesSupport for command line calls in a stripped executable Support for XDB commandsGNU GDB Logging Commands Stop in/at dbx commandsExecute the chatr -B immediate executable command For 32-bit applicationsFor 64-bit applications Command line calls to non-stripped librarySupport for debugging stripped binaries Printing of locals and globals in a stripped moduleDisplaying the current block scope information Linux supportSyntax 242 Starting the TUI Invoke the debugger using a command like the followingHP-UX Terminal User Interface MainAutomatically running a program at startup Screen LayoutsSource pane Disassembly paneDisassembly pane appears when you issue the command Pane looks like thisSource/Disassembly pane Disassembly/Register paneSource/Disassembly pane appears when you issue the command Source/Register pane appears when you issue the command Source/Register paneCycling through the panes Use the commandsToggle split-screen mode Changing pane focusFs regs Foc next Scrolling panes Changing the register displayChanging the pane size Refreshing and updating the window By-function lists of XDB commands and HP WDB equivalents XDB to WDB Transition GuideInvocation commands Invocation commandsWindow mode commands Window mode commandsFile viewing commands File viewing commandsSource directory mapping commands Data Viewing and modification commandsData viewing and modification commands Ll string Lm stringStack viewing commands Stack viewing commandsStatus viewing commands Status-viewing commandJob control commands Job control commandsOverall breakpoint commands Auxiliary breakpoint commandsOverall breakpoint commands Breakpoint creation commands Auxillary breakpoint commands10 Breakpoint creation commands Breakpoint status commands 11 Overall breakpoint commands12 Global breakpoint commands All-procedures breakpoint commandsGlobal breakpoint commands Bp bpt bpx dp Dpt DpxAssertion control commands Record and playback commandsMacro facility commands 13 Macro facility commands Signal control commandsMiscellaneous commands 14 Signal control commandsFormat of the print command is different in XDB and GDB 16 Data format commandsXDB data formats and HP WDB equivalents Decimal integer 17 Macro facility commands XDB location syntax and HP WDB equivalentsXDB special language operators and HP WDB equivalents XDB special variables and HP WDB equivalents 18 Special language operators19 Special variables 16.8.1 a Alphabetical lists of XDB commands and HP WDB equivalentsXDB variable identifiers and HP WDB equivalents 20 Variable Identifiers16.8.2 B 22 BThrough D 23 C through D24 F through K Through K16.8.5 L 25 LThrough P 26 M through P27 Q through S Through S16.8.8 T 28 TThrough Z 29 U through ZSymbols 30 SymbolsAny string Control-C # text 280 Setting Command History Feature in GDB Setting the GDB PromptSetting Command Editing Options in GDB Controlling GDBExits. You can access this list through history Control the settingsTo fname. This is the file where GDB reads an Expansion or through the history commandSetting the GDB Screen Size Supported Number FormatsOptional warnings and messages Optional messages about internal happenings Set confirm onShow confirm Displays state of confirmation requests Show debug varobj Object debugging infoCanned Sequences of Commands User-defined commandsUser-defined command hooks Command files To add source directories orCommands for controlled output Expressions Output formats292 Using GDB under gnu Emacs Update display window accordingly Calls, like the GDB next command. Then update the displayExecute to next instruction, using the GDB nexti command GDB up command295 296 What is an annotation? GDB AnnotationsServer prefix When printing a structure, GDB annotates it as follows ValuesWhen printing an array, GDB annotates it as follows FramesFrame annotation begins with Then comes Displays Annotation for GDB inputErrors Information on breakpointsInvalidation notices Running the programDisplaying source Annotations We Might Want in the Future Target-invalid306 21.1 GDB/MI Command Syntax GDB/MI InterfaceDone running connected error exit 21.1.2 GDB/MI Output syntaxPragmatics Value Const tuple list String Tuple → Simple examples of GDB/MI interaction Here is what happens if you pass a bad command21.2 GDB/MI compatibility with CLI Here is an example to evaluate an expression21.3.1 GDB/MI result records 21.4 GDB/MI command description format21.3 GDB/MI output records 21.3.2 GDB/MI stream records21.5 GDB/MI breakpoint table commands -break-after Command-break-condition command Corresponding GDB command is conditionCorresponding GDB command is delete -break-delete command-break-disable command Corresponding GDB command is disable-break-enable command -break-info Command-break-insert command Result-break-list command -break-watch command Corresponding GDB commands are watch, awatch, and rwatchSetting a watchpoint on a variable in the main function Exec-continue running gdb -data-disassemble command 21.6 GDB/MI Data manipulationThere is no direct mapping from this command to the CLI Disassemble from the current value of $pc to $pc +Disassemble 3 instructions from the start of main -data-evaluate-expression command Display a list of the registers that have changed -data-list-changed-registers Command-data-list-register-names command On a PPC MBX board-data-list-register-values command -data-read-memory command Space should be quoted using the C conventionTo be read. Complex expressions containing embedded white Word-format Word-sizenr-rowsnr-cols aschar -display-delete command -display-disable Command-display-list command -display-enable command-display-insert Command -environment-cd command-environment-directory command -environment-path command21.7 GDB/MI program control -environment-pwd commandCorresponding GDB command is pwd Show the current working directory-exec-abort command -exec-arguments command-exec-continue command Corresponding GDB command is finish -exec-finish command-exec-interrupt command Corresponding GDB command is interruptCorresponding GDB command is next -exec-nextcommand Synopsis-exec-next-instruction command Corresponding GDB command is nextiCorresponding GDB command is return -exec-return command-exec-runcommand Synopsis Corresponding GDB command is run-exec-show-arguments command Example -exec-stepCommand SynopsisCorresponding GDB command is stepi -exec-step-instruction command-exec-until command Regular steppingCorresponding GDB command is until -file-exec-and-symbols command-file-exec-file command Corresponding GDB command is file-file-list-exec-sections command -file-list-exec-source-files command-file-list-shared-libraries command -file-symbol-file command Miscellaneous GDB commands in GDB/MI-file-list-symbol-files command -gdb-exitcommand Synopsis-gdb-setcommand Synopsis -gdb-showcommand Synopsis-gdb-version command 21.9 GDB/MI Stack Manipulation Commands -stack-info-frame command-stack-info-depth command -stack-list-arguments command Synopsis For a stack with frame levels 0 through-stack-list-frames command Show frames between lowframe and highframe Corresponding GDB commands are backtrace and whereFull stack backtrace Show a single frame-stack-list-locals command -stack-select-frame commandInfo locals in GDB, gdbgetlocals in gdbtk -symbol-info-file command 21.10 GDB/MI Symbol query commands-symbol-info-address command -symbol-info-function command-symbol-list-functions command -symbol-info-line command-symbol-info-symbol command -symbol-list-types command-symbol-list-variables command -symbol-locate command-symbol-type command -target-compare-sections command 21.11 GDB/MI Target Manipulation Commands-target-attach command -target-detach commandName of the section -target-download commandCorresponding GDB command is load At the end, a summary is printed-target-exec-status command -target-list-available-targets command -target-list-current-targets command-target-list-parameters command -thread-info command 21.12 GDB/MI thread commands-target-select command -thread-list-all-threads command-thread-list-ids command -thread-select command21.13 GDB/MI tracepoint commands Tracepoint commands are not yet implemented21.14 GDB/MI variable objects -var-create command GDB/MI OperationsDescription and use of operations on variable objects -var-show-format command -var-delete command-var-set-format command -var-info-num-children command-var-info-expression command -var-list-children command-var-info-type command -var-show-attributes command-var-assign command -var-update command360 How to report bugs Reporting Bugs in GDBHave you found a bug? Reporting Bugs in GDB How to report bugs 364 Installing GDB Compiling GDB in another directory Gdb-gdb-199991101/mmallocPackage Specifying names for hosts and targets To use the source in the directory dirname. configure Configure optionsSeparate directories. configure writes configuration Srcdir= dirnameTarget=target All available targets

<common_block_name>

block.

9.4.2.3 Fortran special issues