HP gnu source-level debugger 5992-4701 User Manual Page 175
- Page / 369
- Table of contents
- BOOKMARKS
Rated. / 5. Based on customer reviews
Syntax:
info corruption [<file name>]
The run time memory checking must be enabled before using the info corruption
command to detect memory corruption. The corruption information is written to a file
specified in the .file name argument if provided. Otherwise, it is printed to the
stdout.
NOTE: Turning on bounds checking increases the program's memory requirements
because the extra guard bytes must be allocated at the beginning and end of each block.
14.10.8.3 Stop when a specified block address is allocated or deallocated
To stop a program whenever a block at a specified address is allocated or deallocated,
use the command:
set heap-check watch address
You can use this to debug situations such as multiple free() calls to the same block.
Limitation : This is not supported in batch mode debugging.
14.10.8.4 Scramble previous memory contents at malloc/free calls
WDB enables you to potentially expose latent memory access defects with the command:
– In Interactive debugging mode: set heap-check scramble [on | off]
– In batch mode debugging: scramble_blocks [on | off].
When this setting is turned on, any time a memory block is allocated or deallocated,
WDB scrambles the space and overwrites it with a specific pattern.
This change to the memory contents increases the chance that erroneous behaviors will
cause the program to fail. Examples of such behavior include attempting to access space
that is freed or depending on initial values of malloc() blocks.
You can now look at the stack trace to understand where and how the problem occurred.
NOTE: Turning on scrambling slows down the program slightly, because at every
malloc() and free() call, the space involved must be overwritten.
14.10.8.5 Detect dangling pointers and dangling blocks
A pointer is a Dangling pointer if the block of memory it points to, has been freed by
the application. The block is called Dangling Block.
The same freed block could be subsequently allocated to the application in response
to another memory allocation request. In this scenario, if the application incorrectly
tries to write into the freed memory block using the dangling pointer, it could result
in incorrect or an undefined program behavior, as the new owner or function owning
the same allocated block would nd different values in the heap block.
14.10 Debugging Memory Problems 175
- Debugging with GDB Manual 1
- Table of Contents 3
- 4 Table of Contents 4
- Table of Contents 5 5
- 6 Table of Contents 6
- Table of Contents 7 7
- 8 Table of Contents 8
- Table of Contents 9 9
- 10 Table of Contents 10
- Table of Contents 11 11
- 12 Table of Contents 12
- List of Tables 13
- List of Examples 14
- Summary of GDB 15
- Contributors to GDB 17 17
- 1 A Sample GDB Session 19
- 1.2 Setting Display width 20
- 1.3 Setting Breakpoints 20
- 1.7 Examining the Stack 21
- 1.8 Printing Variable Values 21
- 1.9 Listing Source Code 22
- 2 Getting In and Out of GDB 25
- 2.1.1 Choosing files 26
- 2.1.2 Choosing modes 27
- Program exited normally 28
- 2.1 Invoking GDB 29 29
- 2.2 Quitting GDB 30
- 2.3 Shell commands 31
- 3 GDB Commands 33
- 34 GDB Commands 34
- 3.3 Getting help 35
- 36 GDB Commands 36
- 3.3 Getting help 37 37
- 4 Running Programs Under GDB 39
- 40 Running Programs Under GDB 40
- 4.3 Arguments To Your Program 41
- 4.4 Program Environment 41
- 42 Running Programs Under GDB 42
- 4.5 Working directory 43
- 4.6 Program Input and Output 43
- 44 Running Programs Under GDB 44
- 4.8 Killing the child process 45
- ((gdb)) info threads 46
- ((gdb)) thread 1 46
- 48 Running Programs Under GDB 48
- 50 Running Programs Under GDB 50
- 5 Stopping and Continuing 51
- 5.1.1 Setting breakpoints 52
- 5.1 Breakpoints 53 53
- 54 Stopping and Continuing 54
- 5.1 Breakpoints 55 55
- 5.1.2 Setting catchpoints 56
- 5.1 Breakpoints 57 57
- 5.1.3 Deleting breakpoints 58
- 5.1.4 Disabling breakpoints 58
- 5.1.5 Break conditions 59
- 60 Stopping and Continuing 60
- 5.1 Breakpoints 61 61
- 5.1.7 Breakpoint menus 62
- 5.1 Breakpoints 63 63
- 5.2 Continuing and stepping 64
- ((gdb)) f 66
- 206 expand_input(); 66
- ((gdb)) until 66
- 5.3 Signals 67
- 68 Stopping and Continuing 68
- 70 Stopping and Continuing 70
- 6 Examining the Stack 71
- 6.2 Stacks Without frames 72
- 6.4 Backtraces 72
- 6.5 Selecting a frame 73
- 6.6 Information about a frame 74
- 7 Examining Source Files 77
- 7.2 Searching source files 78
- 7.4 Source and machine code 80
- 8 Examining Data 83
- 8.2 Program variables 84
- 8.3 Artificial arrays 85
- 8.4 Output formats 86
- 8.5 Examining memory 87
- 88 Examining Data 88
- 8.6 Automatic display 89
- 8.7 Print settings 90
- ((gdb)) set print addr off 91
- 530 if (lquote != def_lquote) 91
- 92 Examining Data 92
- 8.7 Print settings 93 93
- 94 Examining Data 94
- 8.8 Value history 95
- 8.9 Convenience variables 96
- 8.9 Convenience variables 97 97
- 8.10 Registers 98
- 8.12 Floating point hardware 99
- 9.2 Displaying the language 103
- 9.3 Type and range checking 103
- 9.4 Supported languages 105
- 9.4.1 C and C++ 106
- 9.4 Supported languages 107 107
- 9.4 Supported languages 109 109
- 9.4 Supported languages 111 111
- 9.4.2 Fortran 112
- 9.4 Supported languages 113 113
- 10 Examining the Symbol Table 115
- {<no data fields>} 118
- 11 Altering Execution 119
- 120 Altering Execution 120
- 11.6 Patching programs 122
- 11.6 Patching programs 123 123
- 12 GDB Files 125
- 126 GDB Files 126
- 128 GDB Files 128
- 130 GDB Files 130
- 132 GDB Files 132
- 13.1 Active targets 133
- 14.2 HP-UX dependencies 140
- 14.2 HP-UX dependencies 141 141
- 14.4 HP-UX targets 143
- 14.7.3 Using Fix and Continue 147
- 14.8 Inline Support 150
- 14.8 Inline Support 151 151
- /opt/aCC/bin/aCC -g test.c 152
- (gdb) set inline-debug on 152
- $ gdb --inline = on 152
- 14.9 Debugging Macros 153
- 14.9 Debugging Macros 155 155
- <arguments if any> 170
- 14.10.10 Heap Profiling 178
- (gdb) set heap-check on 179
- (gdb) b myfunction 179
- (gdb) thread disable 1 181
- (gdb) thread enable 1 181
- Enabling thread 1 181
- Set BATCH_RTC=on 191
- 14.12 Debugging MPI Programs 194
- 0x61, 0x61, 0x61, 0x61 199
- 14.15 Debugging Core Files 200
- (gdb) i ep 4 10 204
- Sample Program: 205
- Sample Debugging Session: 205
- 14.21.1 Deferred watchpoints 208
- 14.21.2 Hardware watchpoints 208
- 14.21.3 Hardware breakpoints 208
- (gdb) break :: 209
- (gdb) b main 210
- 14.22.3 Using catch load 211
- (gdb) set mapshared on 212
- (gdb) set mapshared off 212
- /usr/lib/hpux32/dld.so 213
- 14.25 Language support 217
- (gdb) help java 218
- Java VM Debugging Commands 219
- Java subcommands 219
- 14.25 Language support 221 221
- 14.30 Debugging with ARIES 230
- /opt/langtools/bin/vdb 233
- /opt/langtools/bin/vdb -tui 233
- HPterm*foreground: white 235
- 14.31.5 Using the TUI mode 236
- 14.31.8 Loading source files 237
- 14.31.9 Editing source files 237
- 14.32 Support for ddd 238
- 14.37 Linux support 241
- 15.1 Starting the TUI 243
- 15.3 Screen Layouts 244
- 15.3.1 Source pane 245
- 15.3.2 Disassembly pane 245
- 15.3.5 Source/Register pane 247
- 15.5 Changing pane focus 248
- 15.6 Scrolling panes 250
- 15.8 Changing the pane size 251
- 16.1.1 Invocation commands 254
- 16.1.2 Window mode commands 254
- 16.1.3 File viewing commands 255
- 16.1.6 Stack viewing commands 258
- 16.1.7 Status-viewing command 259
- 16.1.8 Job control commands 259
- XDB: p expr\fmt 266
- GDB: p/fmt expr 266
- Table 16-19 Special variables 269
- 16.8.1 A 270
- 16.8.2 B 271
- 16.8.3 C through D 272
- 16.8.4 F through K 273
- 16.8.5 L 273
- 16.8.6 M through P 274
- 16.8.7 Q through S 275
- 16.8.8 T 275
- 16.8.9 U through Z 276
- 16.8.10 Symbols 277
- 17 Controlling GDB 281
- 282 Controlling GDB 282
- 17.5 Supported Number Formats 283
- ((gdb)) run 284
- 286 Controlling GDB 286
- 18.1 User-defined commands 287
- 18.3 Command files 289
- 19 Using GDB under gnu Emacs 293
- 294 Using GDB under gnu Emacs 294
- 20 GDB Annotations 297
- 20.3 Values 298
- 20.4 Frames 299
- 300 GDB Annotations 300
- 20.5 Displays 301
- 20.6 Annotation for GDB input 301
- 20.7 Errors 302
- 20.9 Invalidation notices 303
- 20.10 Running the program 303
- 20.11 Displaying source 304
- 21 The GDB/MI Interface 307
- 21.1.2 GDB/MI Output syntax 308
- 310 The GDB/MI Interface 310
- 21.3 GDB/MI output records 311
- -command args 312
- -break-after number count 312
- The -break-condition command 313
- Synopsis 313
- GDB command 313
- 314 The GDB/MI Interface 314
- [ -p thread ] [ line 316
- The -break-list command 317
- The -break-watch command 318
- 21.6 GDB/MI Data manipulation 320
- The -data-read-memory command 325
- -display-enable number 328
- -display-insert expression 328
- -display-list 328
- -environment-cd pathdir 328
- 21.7 GDB/MI program control 330
- -exec-abort 331
- -exec-arguments args 331
- -exec-continue 331
- -exec-return 334
- -exec-run 334
- -exec-show-arguments 335
- -exec-step 335
- -exec-step-instruction 336
- -exec-until [ location ] 336
- 338 The GDB/MI Interface 338
- 340 The GDB/MI Interface 340
- -symbol-info-address symbol 346
- -symbol-info-file 346
- -symbol-info-function 346
- -symbol-info-line 347
- -symbol-info-symbol addr 347
- -symbol-list-functions 347
- -symbol-list-types 347
- -symbol-list-variables 348
- -symbol-locate 348
- -symbol-type variable 348
- -target-attach pid 349
- -target-detach 349
- The -target-download command 350
- -target-list-current-targets 352
- -target-list-parameters 352
- 21.12 GDB/MI thread commands 353
- 354 The GDB/MI Interface 354
- 21.14 GDB/MI variable objects 355
- The -var-create command 356
- 358 The GDB/MI Interface 358
- The -var-assign command 359
- The -var-update command 359
- 22 Reporting Bugs in GDB 361
- 362 Reporting Bugs in GDB 362
- 22.2 How to report bugs 363 363
- A Installing GDB 365
- 366 Installing GDB 366
- A.3 configure options 368
- A.3 configure options 369 369
Related products and manuals for Software HP gnu source-level debugger 5992-4701
Software HP 39g Graphing Calculator User's Guide
(288 pages)
(288 pages)
Software HP Vectra VE5 2 User's Guide
(102 pages)
(102 pages)
Software HP Photo Pro User's Guide
(16 pages)
(16 pages)
Software HP 5300 Technical Information
(442 pages)
(442 pages)
Software Hp 9000 Servers User Manual
(5 pages)
(5 pages)
Software Hp Storage Area Manager User Manual
(13 pages)
(13 pages)
(83 pages)Foremost AV equipment stands user manuals
The list of Foremost AV equipment stands products contains 12 user manuals for 12 models. All pdf user’s guides are available for download or viewing online.
© 2020, manymanuals.com. All rights reserved. | 0.038 s |
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Comments to this Manuals