| 1 | @c Copyright (C) 2008-2018 Free Software Foundation, Inc. |
| 2 | @c Permission is granted to copy, distribute and/or modify this document |
| 3 | @c under the terms of the GNU Free Documentation License, Version 1.3 or |
| 4 | @c any later version published by the Free Software Foundation; with the |
| 5 | @c Invariant Sections being ``Free Software'' and ``Free Software Needs |
| 6 | @c Free Documentation'', with the Front-Cover Texts being ``A GNU Manual,'' |
| 7 | @c and with the Back-Cover Texts as in (a) below. |
| 8 | @c |
| 9 | @c (a) The FSF's Back-Cover Text is: ``You are free to copy and modify |
| 10 | @c this GNU Manual. Buying copies from GNU Press supports the FSF in |
| 11 | @c developing GNU and promoting software freedom.'' |
| 12 | |
| 13 | @node Python |
| 14 | @section Extending @value{GDBN} using Python |
| 15 | @cindex python scripting |
| 16 | @cindex scripting with python |
| 17 | |
| 18 | You can extend @value{GDBN} using the @uref{http://www.python.org/, |
| 19 | Python programming language}. This feature is available only if |
| 20 | @value{GDBN} was configured using @option{--with-python}. |
| 21 | @value{GDBN} can be built against either Python 2 or Python 3; which |
| 22 | one you have depends on this configure-time option. |
| 23 | |
| 24 | @cindex python directory |
| 25 | Python scripts used by @value{GDBN} should be installed in |
| 26 | @file{@var{data-directory}/python}, where @var{data-directory} is |
| 27 | the data directory as determined at @value{GDBN} startup (@pxref{Data Files}). |
| 28 | This directory, known as the @dfn{python directory}, |
| 29 | is automatically added to the Python Search Path in order to allow |
| 30 | the Python interpreter to locate all scripts installed at this location. |
| 31 | |
| 32 | Additionally, @value{GDBN} commands and convenience functions which |
| 33 | are written in Python and are located in the |
| 34 | @file{@var{data-directory}/python/gdb/command} or |
| 35 | @file{@var{data-directory}/python/gdb/function} directories are |
| 36 | automatically imported when @value{GDBN} starts. |
| 37 | |
| 38 | @menu |
| 39 | * Python Commands:: Accessing Python from @value{GDBN}. |
| 40 | * Python API:: Accessing @value{GDBN} from Python. |
| 41 | * Python Auto-loading:: Automatically loading Python code. |
| 42 | * Python modules:: Python modules provided by @value{GDBN}. |
| 43 | @end menu |
| 44 | |
| 45 | @node Python Commands |
| 46 | @subsection Python Commands |
| 47 | @cindex python commands |
| 48 | @cindex commands to access python |
| 49 | |
| 50 | @value{GDBN} provides two commands for accessing the Python interpreter, |
| 51 | and one related setting: |
| 52 | |
| 53 | @table @code |
| 54 | @kindex python-interactive |
| 55 | @kindex pi |
| 56 | @item python-interactive @r{[}@var{command}@r{]} |
| 57 | @itemx pi @r{[}@var{command}@r{]} |
| 58 | Without an argument, the @code{python-interactive} command can be used |
| 59 | to start an interactive Python prompt. To return to @value{GDBN}, |
| 60 | type the @code{EOF} character (e.g., @kbd{Ctrl-D} on an empty prompt). |
| 61 | |
| 62 | Alternatively, a single-line Python command can be given as an |
| 63 | argument and evaluated. If the command is an expression, the result |
| 64 | will be printed; otherwise, nothing will be printed. For example: |
| 65 | |
| 66 | @smallexample |
| 67 | (@value{GDBP}) python-interactive 2 + 3 |
| 68 | 5 |
| 69 | @end smallexample |
| 70 | |
| 71 | @kindex python |
| 72 | @kindex py |
| 73 | @item python @r{[}@var{command}@r{]} |
| 74 | @itemx py @r{[}@var{command}@r{]} |
| 75 | The @code{python} command can be used to evaluate Python code. |
| 76 | |
| 77 | If given an argument, the @code{python} command will evaluate the |
| 78 | argument as a Python command. For example: |
| 79 | |
| 80 | @smallexample |
| 81 | (@value{GDBP}) python print 23 |
| 82 | 23 |
| 83 | @end smallexample |
| 84 | |
| 85 | If you do not provide an argument to @code{python}, it will act as a |
| 86 | multi-line command, like @code{define}. In this case, the Python |
| 87 | script is made up of subsequent command lines, given after the |
| 88 | @code{python} command. This command list is terminated using a line |
| 89 | containing @code{end}. For example: |
| 90 | |
| 91 | @smallexample |
| 92 | (@value{GDBP}) python |
| 93 | Type python script |
| 94 | End with a line saying just "end". |
| 95 | >print 23 |
| 96 | >end |
| 97 | 23 |
| 98 | @end smallexample |
| 99 | |
| 100 | @kindex set python print-stack |
| 101 | @item set python print-stack |
| 102 | By default, @value{GDBN} will print only the message component of a |
| 103 | Python exception when an error occurs in a Python script. This can be |
| 104 | controlled using @code{set python print-stack}: if @code{full}, then |
| 105 | full Python stack printing is enabled; if @code{none}, then Python stack |
| 106 | and message printing is disabled; if @code{message}, the default, only |
| 107 | the message component of the error is printed. |
| 108 | @end table |
| 109 | |
| 110 | It is also possible to execute a Python script from the @value{GDBN} |
| 111 | interpreter: |
| 112 | |
| 113 | @table @code |
| 114 | @item source @file{script-name} |
| 115 | The script name must end with @samp{.py} and @value{GDBN} must be configured |
| 116 | to recognize the script language based on filename extension using |
| 117 | the @code{script-extension} setting. @xref{Extending GDB, ,Extending GDB}. |
| 118 | @end table |
| 119 | |
| 120 | @node Python API |
| 121 | @subsection Python API |
| 122 | @cindex python api |
| 123 | @cindex programming in python |
| 124 | |
| 125 | You can get quick online help for @value{GDBN}'s Python API by issuing |
| 126 | the command @w{@kbd{python help (gdb)}}. |
| 127 | |
| 128 | Functions and methods which have two or more optional arguments allow |
| 129 | them to be specified using keyword syntax. This allows passing some |
| 130 | optional arguments while skipping others. Example: |
| 131 | @w{@code{gdb.some_function ('foo', bar = 1, baz = 2)}}. |
| 132 | |
| 133 | @menu |
| 134 | * Basic Python:: Basic Python Functions. |
| 135 | * Exception Handling:: How Python exceptions are translated. |
| 136 | * Values From Inferior:: Python representation of values. |
| 137 | * Types In Python:: Python representation of types. |
| 138 | * Pretty Printing API:: Pretty-printing values. |
| 139 | * Selecting Pretty-Printers:: How GDB chooses a pretty-printer. |
| 140 | * Writing a Pretty-Printer:: Writing a Pretty-Printer. |
| 141 | * Type Printing API:: Pretty-printing types. |
| 142 | * Frame Filter API:: Filtering Frames. |
| 143 | * Frame Decorator API:: Decorating Frames. |
| 144 | * Writing a Frame Filter:: Writing a Frame Filter. |
| 145 | * Unwinding Frames in Python:: Writing frame unwinder. |
| 146 | * Xmethods In Python:: Adding and replacing methods of C++ classes. |
| 147 | * Xmethod API:: Xmethod types. |
| 148 | * Writing an Xmethod:: Writing an xmethod. |
| 149 | * Inferiors In Python:: Python representation of inferiors (processes) |
| 150 | * Events In Python:: Listening for events from @value{GDBN}. |
| 151 | * Threads In Python:: Accessing inferior threads from Python. |
| 152 | * Recordings In Python:: Accessing recordings from Python. |
| 153 | * Commands In Python:: Implementing new commands in Python. |
| 154 | * Parameters In Python:: Adding new @value{GDBN} parameters. |
| 155 | * Functions In Python:: Writing new convenience functions. |
| 156 | * Progspaces In Python:: Program spaces. |
| 157 | * Objfiles In Python:: Object files. |
| 158 | * Frames In Python:: Accessing inferior stack frames from Python. |
| 159 | * Blocks In Python:: Accessing blocks from Python. |
| 160 | * Symbols In Python:: Python representation of symbols. |
| 161 | * Symbol Tables In Python:: Python representation of symbol tables. |
| 162 | * Line Tables In Python:: Python representation of line tables. |
| 163 | * Breakpoints In Python:: Manipulating breakpoints using Python. |
| 164 | * Finish Breakpoints in Python:: Setting Breakpoints on function return |
| 165 | using Python. |
| 166 | * Lazy Strings In Python:: Python representation of lazy strings. |
| 167 | * Architectures In Python:: Python representation of architectures. |
| 168 | @end menu |
| 169 | |
| 170 | @node Basic Python |
| 171 | @subsubsection Basic Python |
| 172 | |
| 173 | @cindex python stdout |
| 174 | @cindex python pagination |
| 175 | At startup, @value{GDBN} overrides Python's @code{sys.stdout} and |
| 176 | @code{sys.stderr} to print using @value{GDBN}'s output-paging streams. |
| 177 | A Python program which outputs to one of these streams may have its |
| 178 | output interrupted by the user (@pxref{Screen Size}). In this |
| 179 | situation, a Python @code{KeyboardInterrupt} exception is thrown. |
| 180 | |
| 181 | Some care must be taken when writing Python code to run in |
| 182 | @value{GDBN}. Two things worth noting in particular: |
| 183 | |
| 184 | @itemize @bullet |
| 185 | @item |
| 186 | @value{GDBN} install handlers for @code{SIGCHLD} and @code{SIGINT}. |
| 187 | Python code must not override these, or even change the options using |
| 188 | @code{sigaction}. If your program changes the handling of these |
| 189 | signals, @value{GDBN} will most likely stop working correctly. Note |
| 190 | that it is unfortunately common for GUI toolkits to install a |
| 191 | @code{SIGCHLD} handler. |
| 192 | |
| 193 | @item |
| 194 | @value{GDBN} takes care to mark its internal file descriptors as |
| 195 | close-on-exec. However, this cannot be done in a thread-safe way on |
| 196 | all platforms. Your Python programs should be aware of this and |
| 197 | should both create new file descriptors with the close-on-exec flag |
| 198 | set and arrange to close unneeded file descriptors before starting a |
| 199 | child process. |
| 200 | @end itemize |
| 201 | |
| 202 | @cindex python functions |
| 203 | @cindex python module |
| 204 | @cindex gdb module |
| 205 | @value{GDBN} introduces a new Python module, named @code{gdb}. All |
| 206 | methods and classes added by @value{GDBN} are placed in this module. |
| 207 | @value{GDBN} automatically @code{import}s the @code{gdb} module for |
| 208 | use in all scripts evaluated by the @code{python} command. |
| 209 | |
| 210 | Some types of the @code{gdb} module come with a textual representation |
| 211 | (accessible through the @code{repr} or @code{str} functions). These are |
| 212 | offered for debugging purposes only, expect them to change over time. |
| 213 | |
| 214 | @findex gdb.PYTHONDIR |
| 215 | @defvar gdb.PYTHONDIR |
| 216 | A string containing the python directory (@pxref{Python}). |
| 217 | @end defvar |
| 218 | |
| 219 | @findex gdb.execute |
| 220 | @defun gdb.execute (command @r{[}, from_tty @r{[}, to_string@r{]]}) |
| 221 | Evaluate @var{command}, a string, as a @value{GDBN} CLI command. |
| 222 | If a GDB exception happens while @var{command} runs, it is |
| 223 | translated as described in @ref{Exception Handling,,Exception Handling}. |
| 224 | |
| 225 | The @var{from_tty} flag specifies whether @value{GDBN} ought to consider this |
| 226 | command as having originated from the user invoking it interactively. |
| 227 | It must be a boolean value. If omitted, it defaults to @code{False}. |
| 228 | |
| 229 | By default, any output produced by @var{command} is sent to |
| 230 | @value{GDBN}'s standard output (and to the log output if logging is |
| 231 | turned on). If the @var{to_string} parameter is |
| 232 | @code{True}, then output will be collected by @code{gdb.execute} and |
| 233 | returned as a string. The default is @code{False}, in which case the |
| 234 | return value is @code{None}. If @var{to_string} is @code{True}, the |
| 235 | @value{GDBN} virtual terminal will be temporarily set to unlimited width |
| 236 | and height, and its pagination will be disabled; @pxref{Screen Size}. |
| 237 | @end defun |
| 238 | |
| 239 | @findex gdb.breakpoints |
| 240 | @defun gdb.breakpoints () |
| 241 | Return a sequence holding all of @value{GDBN}'s breakpoints. |
| 242 | @xref{Breakpoints In Python}, for more information. In @value{GDBN} |
| 243 | version 7.11 and earlier, this function returned @code{None} if there |
| 244 | were no breakpoints. This peculiarity was subsequently fixed, and now |
| 245 | @code{gdb.breakpoints} returns an empty sequence in this case. |
| 246 | @end defun |
| 247 | |
| 248 | @defun gdb.rbreak (regex @r{[}, minsyms @r{[}, throttle, @r{[}, symtabs @r{]]]}) |
| 249 | Return a Python list holding a collection of newly set |
| 250 | @code{gdb.Breakpoint} objects matching function names defined by the |
| 251 | @var{regex} pattern. If the @var{minsyms} keyword is @code{True}, all |
| 252 | system functions (those not explicitly defined in the inferior) will |
| 253 | also be included in the match. The @var{throttle} keyword takes an |
| 254 | integer that defines the maximum number of pattern matches for |
| 255 | functions matched by the @var{regex} pattern. If the number of |
| 256 | matches exceeds the integer value of @var{throttle}, a |
| 257 | @code{RuntimeError} will be raised and no breakpoints will be created. |
| 258 | If @var{throttle} is not defined then there is no imposed limit on the |
| 259 | maximum number of matches and breakpoints to be created. The |
| 260 | @var{symtabs} keyword takes a Python iterable that yields a collection |
| 261 | of @code{gdb.Symtab} objects and will restrict the search to those |
| 262 | functions only contained within the @code{gdb.Symtab} objects. |
| 263 | @end defun |
| 264 | |
| 265 | @findex gdb.parameter |
| 266 | @defun gdb.parameter (parameter) |
| 267 | Return the value of a @value{GDBN} @var{parameter} given by its name, |
| 268 | a string; the parameter name string may contain spaces if the parameter has a |
| 269 | multi-part name. For example, @samp{print object} is a valid |
| 270 | parameter name. |
| 271 | |
| 272 | If the named parameter does not exist, this function throws a |
| 273 | @code{gdb.error} (@pxref{Exception Handling}). Otherwise, the |
| 274 | parameter's value is converted to a Python value of the appropriate |
| 275 | type, and returned. |
| 276 | @end defun |
| 277 | |
| 278 | @findex gdb.history |
| 279 | @defun gdb.history (number) |
| 280 | Return a value from @value{GDBN}'s value history (@pxref{Value |
| 281 | History}). The @var{number} argument indicates which history element to return. |
| 282 | If @var{number} is negative, then @value{GDBN} will take its absolute value |
| 283 | and count backward from the last element (i.e., the most recent element) to |
| 284 | find the value to return. If @var{number} is zero, then @value{GDBN} will |
| 285 | return the most recent element. If the element specified by @var{number} |
| 286 | doesn't exist in the value history, a @code{gdb.error} exception will be |
| 287 | raised. |
| 288 | |
| 289 | If no exception is raised, the return value is always an instance of |
| 290 | @code{gdb.Value} (@pxref{Values From Inferior}). |
| 291 | @end defun |
| 292 | |
| 293 | @findex gdb.convenience_variable |
| 294 | @defun gdb.convenience_variable (name) |
| 295 | Return the value of the convenience variable (@pxref{Convenience |
| 296 | Vars}) named @var{name}. @var{name} must be a string. The name |
| 297 | should not include the @samp{$} that is used to mark a convenience |
| 298 | variable in an expression. If the convenience variable does not |
| 299 | exist, then @code{None} is returned. |
| 300 | @end defun |
| 301 | |
| 302 | @findex gdb.set_convenience_variable |
| 303 | @defun gdb.set_convenience_variable (name, value) |
| 304 | Set the value of the convenience variable (@pxref{Convenience Vars}) |
| 305 | named @var{name}. @var{name} must be a string. The name should not |
| 306 | include the @samp{$} that is used to mark a convenience variable in an |
| 307 | expression. If @var{value} is @code{None}, then the convenience |
| 308 | variable is removed. Otherwise, if @var{value} is not a |
| 309 | @code{gdb.Value} (@pxref{Values From Inferior}), it is is converted |
| 310 | using the @code{gdb.Value} constructor. |
| 311 | @end defun |
| 312 | |
| 313 | @findex gdb.parse_and_eval |
| 314 | @defun gdb.parse_and_eval (expression) |
| 315 | Parse @var{expression}, which must be a string, as an expression in |
| 316 | the current language, evaluate it, and return the result as a |
| 317 | @code{gdb.Value}. |
| 318 | |
| 319 | This function can be useful when implementing a new command |
| 320 | (@pxref{Commands In Python}), as it provides a way to parse the |
| 321 | command's argument as an expression. It is also useful simply to |
| 322 | compute values. |
| 323 | @end defun |
| 324 | |
| 325 | @findex gdb.find_pc_line |
| 326 | @defun gdb.find_pc_line (pc) |
| 327 | Return the @code{gdb.Symtab_and_line} object corresponding to the |
| 328 | @var{pc} value. @xref{Symbol Tables In Python}. If an invalid |
| 329 | value of @var{pc} is passed as an argument, then the @code{symtab} and |
| 330 | @code{line} attributes of the returned @code{gdb.Symtab_and_line} object |
| 331 | will be @code{None} and 0 respectively. This is identical to |
| 332 | @code{gdb.current_progspace().find_pc_line(pc)} and is included for |
| 333 | historical compatibility. |
| 334 | @end defun |
| 335 | |
| 336 | @findex gdb.post_event |
| 337 | @defun gdb.post_event (event) |
| 338 | Put @var{event}, a callable object taking no arguments, into |
| 339 | @value{GDBN}'s internal event queue. This callable will be invoked at |
| 340 | some later point, during @value{GDBN}'s event processing. Events |
| 341 | posted using @code{post_event} will be run in the order in which they |
| 342 | were posted; however, there is no way to know when they will be |
| 343 | processed relative to other events inside @value{GDBN}. |
| 344 | |
| 345 | @value{GDBN} is not thread-safe. If your Python program uses multiple |
| 346 | threads, you must be careful to only call @value{GDBN}-specific |
| 347 | functions in the @value{GDBN} thread. @code{post_event} ensures |
| 348 | this. For example: |
| 349 | |
| 350 | @smallexample |
| 351 | (@value{GDBP}) python |
| 352 | >import threading |
| 353 | > |
| 354 | >class Writer(): |
| 355 | > def __init__(self, message): |
| 356 | > self.message = message; |
| 357 | > def __call__(self): |
| 358 | > gdb.write(self.message) |
| 359 | > |
| 360 | >class MyThread1 (threading.Thread): |
| 361 | > def run (self): |
| 362 | > gdb.post_event(Writer("Hello ")) |
| 363 | > |
| 364 | >class MyThread2 (threading.Thread): |
| 365 | > def run (self): |
| 366 | > gdb.post_event(Writer("World\n")) |
| 367 | > |
| 368 | >MyThread1().start() |
| 369 | >MyThread2().start() |
| 370 | >end |
| 371 | (@value{GDBP}) Hello World |
| 372 | @end smallexample |
| 373 | @end defun |
| 374 | |
| 375 | @findex gdb.write |
| 376 | @defun gdb.write (string @r{[}, stream{]}) |
| 377 | Print a string to @value{GDBN}'s paginated output stream. The |
| 378 | optional @var{stream} determines the stream to print to. The default |
| 379 | stream is @value{GDBN}'s standard output stream. Possible stream |
| 380 | values are: |
| 381 | |
| 382 | @table @code |
| 383 | @findex STDOUT |
| 384 | @findex gdb.STDOUT |
| 385 | @item gdb.STDOUT |
| 386 | @value{GDBN}'s standard output stream. |
| 387 | |
| 388 | @findex STDERR |
| 389 | @findex gdb.STDERR |
| 390 | @item gdb.STDERR |
| 391 | @value{GDBN}'s standard error stream. |
| 392 | |
| 393 | @findex STDLOG |
| 394 | @findex gdb.STDLOG |
| 395 | @item gdb.STDLOG |
| 396 | @value{GDBN}'s log stream (@pxref{Logging Output}). |
| 397 | @end table |
| 398 | |
| 399 | Writing to @code{sys.stdout} or @code{sys.stderr} will automatically |
| 400 | call this function and will automatically direct the output to the |
| 401 | relevant stream. |
| 402 | @end defun |
| 403 | |
| 404 | @findex gdb.flush |
| 405 | @defun gdb.flush () |
| 406 | Flush the buffer of a @value{GDBN} paginated stream so that the |
| 407 | contents are displayed immediately. @value{GDBN} will flush the |
| 408 | contents of a stream automatically when it encounters a newline in the |
| 409 | buffer. The optional @var{stream} determines the stream to flush. The |
| 410 | default stream is @value{GDBN}'s standard output stream. Possible |
| 411 | stream values are: |
| 412 | |
| 413 | @table @code |
| 414 | @findex STDOUT |
| 415 | @findex gdb.STDOUT |
| 416 | @item gdb.STDOUT |
| 417 | @value{GDBN}'s standard output stream. |
| 418 | |
| 419 | @findex STDERR |
| 420 | @findex gdb.STDERR |
| 421 | @item gdb.STDERR |
| 422 | @value{GDBN}'s standard error stream. |
| 423 | |
| 424 | @findex STDLOG |
| 425 | @findex gdb.STDLOG |
| 426 | @item gdb.STDLOG |
| 427 | @value{GDBN}'s log stream (@pxref{Logging Output}). |
| 428 | |
| 429 | @end table |
| 430 | |
| 431 | Flushing @code{sys.stdout} or @code{sys.stderr} will automatically |
| 432 | call this function for the relevant stream. |
| 433 | @end defun |
| 434 | |
| 435 | @findex gdb.target_charset |
| 436 | @defun gdb.target_charset () |
| 437 | Return the name of the current target character set (@pxref{Character |
| 438 | Sets}). This differs from @code{gdb.parameter('target-charset')} in |
| 439 | that @samp{auto} is never returned. |
| 440 | @end defun |
| 441 | |
| 442 | @findex gdb.target_wide_charset |
| 443 | @defun gdb.target_wide_charset () |
| 444 | Return the name of the current target wide character set |
| 445 | (@pxref{Character Sets}). This differs from |
| 446 | @code{gdb.parameter('target-wide-charset')} in that @samp{auto} is |
| 447 | never returned. |
| 448 | @end defun |
| 449 | |
| 450 | @findex gdb.solib_name |
| 451 | @defun gdb.solib_name (address) |
| 452 | Return the name of the shared library holding the given @var{address} |
| 453 | as a string, or @code{None}. This is identical to |
| 454 | @code{gdb.current_progspace().solib_name(address)} and is included for |
| 455 | historical compatibility. |
| 456 | @end defun |
| 457 | |
| 458 | @findex gdb.decode_line |
| 459 | @defun gdb.decode_line (@r{[}expression@r{]}) |
| 460 | Return locations of the line specified by @var{expression}, or of the |
| 461 | current line if no argument was given. This function returns a Python |
| 462 | tuple containing two elements. The first element contains a string |
| 463 | holding any unparsed section of @var{expression} (or @code{None} if |
| 464 | the expression has been fully parsed). The second element contains |
| 465 | either @code{None} or another tuple that contains all the locations |
| 466 | that match the expression represented as @code{gdb.Symtab_and_line} |
| 467 | objects (@pxref{Symbol Tables In Python}). If @var{expression} is |
| 468 | provided, it is decoded the way that @value{GDBN}'s inbuilt |
| 469 | @code{break} or @code{edit} commands do (@pxref{Specify Location}). |
| 470 | @end defun |
| 471 | |
| 472 | @defun gdb.prompt_hook (current_prompt) |
| 473 | @anchor{prompt_hook} |
| 474 | |
| 475 | If @var{prompt_hook} is callable, @value{GDBN} will call the method |
| 476 | assigned to this operation before a prompt is displayed by |
| 477 | @value{GDBN}. |
| 478 | |
| 479 | The parameter @code{current_prompt} contains the current @value{GDBN} |
| 480 | prompt. This method must return a Python string, or @code{None}. If |
| 481 | a string is returned, the @value{GDBN} prompt will be set to that |
| 482 | string. If @code{None} is returned, @value{GDBN} will continue to use |
| 483 | the current prompt. |
| 484 | |
| 485 | Some prompts cannot be substituted in @value{GDBN}. Secondary prompts |
| 486 | such as those used by readline for command input, and annotation |
| 487 | related prompts are prohibited from being changed. |
| 488 | @end defun |
| 489 | |
| 490 | @node Exception Handling |
| 491 | @subsubsection Exception Handling |
| 492 | @cindex python exceptions |
| 493 | @cindex exceptions, python |
| 494 | |
| 495 | When executing the @code{python} command, Python exceptions |
| 496 | uncaught within the Python code are translated to calls to |
| 497 | @value{GDBN} error-reporting mechanism. If the command that called |
| 498 | @code{python} does not handle the error, @value{GDBN} will |
| 499 | terminate it and print an error message containing the Python |
| 500 | exception name, the associated value, and the Python call stack |
| 501 | backtrace at the point where the exception was raised. Example: |
| 502 | |
| 503 | @smallexample |
| 504 | (@value{GDBP}) python print foo |
| 505 | Traceback (most recent call last): |
| 506 | File "<string>", line 1, in <module> |
| 507 | NameError: name 'foo' is not defined |
| 508 | @end smallexample |
| 509 | |
| 510 | @value{GDBN} errors that happen in @value{GDBN} commands invoked by |
| 511 | Python code are converted to Python exceptions. The type of the |
| 512 | Python exception depends on the error. |
| 513 | |
| 514 | @ftable @code |
| 515 | @item gdb.error |
| 516 | This is the base class for most exceptions generated by @value{GDBN}. |
| 517 | It is derived from @code{RuntimeError}, for compatibility with earlier |
| 518 | versions of @value{GDBN}. |
| 519 | |
| 520 | If an error occurring in @value{GDBN} does not fit into some more |
| 521 | specific category, then the generated exception will have this type. |
| 522 | |
| 523 | @item gdb.MemoryError |
| 524 | This is a subclass of @code{gdb.error} which is thrown when an |
| 525 | operation tried to access invalid memory in the inferior. |
| 526 | |
| 527 | @item KeyboardInterrupt |
| 528 | User interrupt (via @kbd{C-c} or by typing @kbd{q} at a pagination |
| 529 | prompt) is translated to a Python @code{KeyboardInterrupt} exception. |
| 530 | @end ftable |
| 531 | |
| 532 | In all cases, your exception handler will see the @value{GDBN} error |
| 533 | message as its value and the Python call stack backtrace at the Python |
| 534 | statement closest to where the @value{GDBN} error occured as the |
| 535 | traceback. |
| 536 | |
| 537 | |
| 538 | When implementing @value{GDBN} commands in Python via |
| 539 | @code{gdb.Command}, or functions via @code{gdb.Function}, it is useful |
| 540 | to be able to throw an exception that doesn't cause a traceback to be |
| 541 | printed. For example, the user may have invoked the command |
| 542 | incorrectly. @value{GDBN} provides a special exception class that can |
| 543 | be used for this purpose. |
| 544 | |
| 545 | @ftable @code |
| 546 | @item gdb.GdbError |
| 547 | When thrown from a command or function, this exception will cause the |
| 548 | command or function to fail, but the Python stack will not be |
| 549 | displayed. @value{GDBN} does not throw this exception itself, but |
| 550 | rather recognizes it when thrown from user Python code. Example: |
| 551 | |
| 552 | @smallexample |
| 553 | (gdb) python |
| 554 | >class HelloWorld (gdb.Command): |
| 555 | > """Greet the whole world.""" |
| 556 | > def __init__ (self): |
| 557 | > super (HelloWorld, self).__init__ ("hello-world", gdb.COMMAND_USER) |
| 558 | > def invoke (self, args, from_tty): |
| 559 | > argv = gdb.string_to_argv (args) |
| 560 | > if len (argv) != 0: |
| 561 | > raise gdb.GdbError ("hello-world takes no arguments") |
| 562 | > print "Hello, World!" |
| 563 | >HelloWorld () |
| 564 | >end |
| 565 | (gdb) hello-world 42 |
| 566 | hello-world takes no arguments |
| 567 | @end smallexample |
| 568 | @end ftable |
| 569 | |
| 570 | @node Values From Inferior |
| 571 | @subsubsection Values From Inferior |
| 572 | @cindex values from inferior, with Python |
| 573 | @cindex python, working with values from inferior |
| 574 | |
| 575 | @cindex @code{gdb.Value} |
| 576 | @value{GDBN} provides values it obtains from the inferior program in |
| 577 | an object of type @code{gdb.Value}. @value{GDBN} uses this object |
| 578 | for its internal bookkeeping of the inferior's values, and for |
| 579 | fetching values when necessary. |
| 580 | |
| 581 | Inferior values that are simple scalars can be used directly in |
| 582 | Python expressions that are valid for the value's data type. Here's |
| 583 | an example for an integer or floating-point value @code{some_val}: |
| 584 | |
| 585 | @smallexample |
| 586 | bar = some_val + 2 |
| 587 | @end smallexample |
| 588 | |
| 589 | @noindent |
| 590 | As result of this, @code{bar} will also be a @code{gdb.Value} object |
| 591 | whose values are of the same type as those of @code{some_val}. Valid |
| 592 | Python operations can also be performed on @code{gdb.Value} objects |
| 593 | representing a @code{struct} or @code{class} object. For such cases, |
| 594 | the overloaded operator (if present), is used to perform the operation. |
| 595 | For example, if @code{val1} and @code{val2} are @code{gdb.Value} objects |
| 596 | representing instances of a @code{class} which overloads the @code{+} |
| 597 | operator, then one can use the @code{+} operator in their Python script |
| 598 | as follows: |
| 599 | |
| 600 | @smallexample |
| 601 | val3 = val1 + val2 |
| 602 | @end smallexample |
| 603 | |
| 604 | @noindent |
| 605 | The result of the operation @code{val3} is also a @code{gdb.Value} |
| 606 | object corresponding to the value returned by the overloaded @code{+} |
| 607 | operator. In general, overloaded operators are invoked for the |
| 608 | following operations: @code{+} (binary addition), @code{-} (binary |
| 609 | subtraction), @code{*} (multiplication), @code{/}, @code{%}, @code{<<}, |
| 610 | @code{>>}, @code{|}, @code{&}, @code{^}. |
| 611 | |
| 612 | Inferior values that are structures or instances of some class can |
| 613 | be accessed using the Python @dfn{dictionary syntax}. For example, if |
| 614 | @code{some_val} is a @code{gdb.Value} instance holding a structure, you |
| 615 | can access its @code{foo} element with: |
| 616 | |
| 617 | @smallexample |
| 618 | bar = some_val['foo'] |
| 619 | @end smallexample |
| 620 | |
| 621 | @cindex getting structure elements using gdb.Field objects as subscripts |
| 622 | Again, @code{bar} will also be a @code{gdb.Value} object. Structure |
| 623 | elements can also be accessed by using @code{gdb.Field} objects as |
| 624 | subscripts (@pxref{Types In Python}, for more information on |
| 625 | @code{gdb.Field} objects). For example, if @code{foo_field} is a |
| 626 | @code{gdb.Field} object corresponding to element @code{foo} of the above |
| 627 | structure, then @code{bar} can also be accessed as follows: |
| 628 | |
| 629 | @smallexample |
| 630 | bar = some_val[foo_field] |
| 631 | @end smallexample |
| 632 | |
| 633 | A @code{gdb.Value} that represents a function can be executed via |
| 634 | inferior function call. Any arguments provided to the call must match |
| 635 | the function's prototype, and must be provided in the order specified |
| 636 | by that prototype. |
| 637 | |
| 638 | For example, @code{some_val} is a @code{gdb.Value} instance |
| 639 | representing a function that takes two integers as arguments. To |
| 640 | execute this function, call it like so: |
| 641 | |
| 642 | @smallexample |
| 643 | result = some_val (10,20) |
| 644 | @end smallexample |
| 645 | |
| 646 | Any values returned from a function call will be stored as a |
| 647 | @code{gdb.Value}. |
| 648 | |
| 649 | The following attributes are provided: |
| 650 | |
| 651 | @defvar Value.address |
| 652 | If this object is addressable, this read-only attribute holds a |
| 653 | @code{gdb.Value} object representing the address. Otherwise, |
| 654 | this attribute holds @code{None}. |
| 655 | @end defvar |
| 656 | |
| 657 | @cindex optimized out value in Python |
| 658 | @defvar Value.is_optimized_out |
| 659 | This read-only boolean attribute is true if the compiler optimized out |
| 660 | this value, thus it is not available for fetching from the inferior. |
| 661 | @end defvar |
| 662 | |
| 663 | @defvar Value.type |
| 664 | The type of this @code{gdb.Value}. The value of this attribute is a |
| 665 | @code{gdb.Type} object (@pxref{Types In Python}). |
| 666 | @end defvar |
| 667 | |
| 668 | @defvar Value.dynamic_type |
| 669 | The dynamic type of this @code{gdb.Value}. This uses the object's |
| 670 | virtual table and the C@t{++} run-time type information |
| 671 | (@acronym{RTTI}) to determine the dynamic type of the value. If this |
| 672 | value is of class type, it will return the class in which the value is |
| 673 | embedded, if any. If this value is of pointer or reference to a class |
| 674 | type, it will compute the dynamic type of the referenced object, and |
| 675 | return a pointer or reference to that type, respectively. In all |
| 676 | other cases, it will return the value's static type. |
| 677 | |
| 678 | Note that this feature will only work when debugging a C@t{++} program |
| 679 | that includes @acronym{RTTI} for the object in question. Otherwise, |
| 680 | it will just return the static type of the value as in @kbd{ptype foo} |
| 681 | (@pxref{Symbols, ptype}). |
| 682 | @end defvar |
| 683 | |
| 684 | @defvar Value.is_lazy |
| 685 | The value of this read-only boolean attribute is @code{True} if this |
| 686 | @code{gdb.Value} has not yet been fetched from the inferior. |
| 687 | @value{GDBN} does not fetch values until necessary, for efficiency. |
| 688 | For example: |
| 689 | |
| 690 | @smallexample |
| 691 | myval = gdb.parse_and_eval ('somevar') |
| 692 | @end smallexample |
| 693 | |
| 694 | The value of @code{somevar} is not fetched at this time. It will be |
| 695 | fetched when the value is needed, or when the @code{fetch_lazy} |
| 696 | method is invoked. |
| 697 | @end defvar |
| 698 | |
| 699 | The following methods are provided: |
| 700 | |
| 701 | @defun Value.__init__ (@var{val}) |
| 702 | Many Python values can be converted directly to a @code{gdb.Value} via |
| 703 | this object initializer. Specifically: |
| 704 | |
| 705 | @table @asis |
| 706 | @item Python boolean |
| 707 | A Python boolean is converted to the boolean type from the current |
| 708 | language. |
| 709 | |
| 710 | @item Python integer |
| 711 | A Python integer is converted to the C @code{long} type for the |
| 712 | current architecture. |
| 713 | |
| 714 | @item Python long |
| 715 | A Python long is converted to the C @code{long long} type for the |
| 716 | current architecture. |
| 717 | |
| 718 | @item Python float |
| 719 | A Python float is converted to the C @code{double} type for the |
| 720 | current architecture. |
| 721 | |
| 722 | @item Python string |
| 723 | A Python string is converted to a target string in the current target |
| 724 | language using the current target encoding. |
| 725 | If a character cannot be represented in the current target encoding, |
| 726 | then an exception is thrown. |
| 727 | |
| 728 | @item @code{gdb.Value} |
| 729 | If @code{val} is a @code{gdb.Value}, then a copy of the value is made. |
| 730 | |
| 731 | @item @code{gdb.LazyString} |
| 732 | If @code{val} is a @code{gdb.LazyString} (@pxref{Lazy Strings In |
| 733 | Python}), then the lazy string's @code{value} method is called, and |
| 734 | its result is used. |
| 735 | @end table |
| 736 | @end defun |
| 737 | |
| 738 | @defun Value.cast (type) |
| 739 | Return a new instance of @code{gdb.Value} that is the result of |
| 740 | casting this instance to the type described by @var{type}, which must |
| 741 | be a @code{gdb.Type} object. If the cast cannot be performed for some |
| 742 | reason, this method throws an exception. |
| 743 | @end defun |
| 744 | |
| 745 | @defun Value.dereference () |
| 746 | For pointer data types, this method returns a new @code{gdb.Value} object |
| 747 | whose contents is the object pointed to by the pointer. For example, if |
| 748 | @code{foo} is a C pointer to an @code{int}, declared in your C program as |
| 749 | |
| 750 | @smallexample |
| 751 | int *foo; |
| 752 | @end smallexample |
| 753 | |
| 754 | @noindent |
| 755 | then you can use the corresponding @code{gdb.Value} to access what |
| 756 | @code{foo} points to like this: |
| 757 | |
| 758 | @smallexample |
| 759 | bar = foo.dereference () |
| 760 | @end smallexample |
| 761 | |
| 762 | The result @code{bar} will be a @code{gdb.Value} object holding the |
| 763 | value pointed to by @code{foo}. |
| 764 | |
| 765 | A similar function @code{Value.referenced_value} exists which also |
| 766 | returns @code{gdb.Value} objects corresonding to the values pointed to |
| 767 | by pointer values (and additionally, values referenced by reference |
| 768 | values). However, the behavior of @code{Value.dereference} |
| 769 | differs from @code{Value.referenced_value} by the fact that the |
| 770 | behavior of @code{Value.dereference} is identical to applying the C |
| 771 | unary operator @code{*} on a given value. For example, consider a |
| 772 | reference to a pointer @code{ptrref}, declared in your C@t{++} program |
| 773 | as |
| 774 | |
| 775 | @smallexample |
| 776 | typedef int *intptr; |
| 777 | ... |
| 778 | int val = 10; |
| 779 | intptr ptr = &val; |
| 780 | intptr &ptrref = ptr; |
| 781 | @end smallexample |
| 782 | |
| 783 | Though @code{ptrref} is a reference value, one can apply the method |
| 784 | @code{Value.dereference} to the @code{gdb.Value} object corresponding |
| 785 | to it and obtain a @code{gdb.Value} which is identical to that |
| 786 | corresponding to @code{val}. However, if you apply the method |
| 787 | @code{Value.referenced_value}, the result would be a @code{gdb.Value} |
| 788 | object identical to that corresponding to @code{ptr}. |
| 789 | |
| 790 | @smallexample |
| 791 | py_ptrref = gdb.parse_and_eval ("ptrref") |
| 792 | py_val = py_ptrref.dereference () |
| 793 | py_ptr = py_ptrref.referenced_value () |
| 794 | @end smallexample |
| 795 | |
| 796 | The @code{gdb.Value} object @code{py_val} is identical to that |
| 797 | corresponding to @code{val}, and @code{py_ptr} is identical to that |
| 798 | corresponding to @code{ptr}. In general, @code{Value.dereference} can |
| 799 | be applied whenever the C unary operator @code{*} can be applied |
| 800 | to the corresponding C value. For those cases where applying both |
| 801 | @code{Value.dereference} and @code{Value.referenced_value} is allowed, |
| 802 | the results obtained need not be identical (as we have seen in the above |
| 803 | example). The results are however identical when applied on |
| 804 | @code{gdb.Value} objects corresponding to pointers (@code{gdb.Value} |
| 805 | objects with type code @code{TYPE_CODE_PTR}) in a C/C@t{++} program. |
| 806 | @end defun |
| 807 | |
| 808 | @defun Value.referenced_value () |
| 809 | For pointer or reference data types, this method returns a new |
| 810 | @code{gdb.Value} object corresponding to the value referenced by the |
| 811 | pointer/reference value. For pointer data types, |
| 812 | @code{Value.dereference} and @code{Value.referenced_value} produce |
| 813 | identical results. The difference between these methods is that |
| 814 | @code{Value.dereference} cannot get the values referenced by reference |
| 815 | values. For example, consider a reference to an @code{int}, declared |
| 816 | in your C@t{++} program as |
| 817 | |
| 818 | @smallexample |
| 819 | int val = 10; |
| 820 | int &ref = val; |
| 821 | @end smallexample |
| 822 | |
| 823 | @noindent |
| 824 | then applying @code{Value.dereference} to the @code{gdb.Value} object |
| 825 | corresponding to @code{ref} will result in an error, while applying |
| 826 | @code{Value.referenced_value} will result in a @code{gdb.Value} object |
| 827 | identical to that corresponding to @code{val}. |
| 828 | |
| 829 | @smallexample |
| 830 | py_ref = gdb.parse_and_eval ("ref") |
| 831 | er_ref = py_ref.dereference () # Results in error |
| 832 | py_val = py_ref.referenced_value () # Returns the referenced value |
| 833 | @end smallexample |
| 834 | |
| 835 | The @code{gdb.Value} object @code{py_val} is identical to that |
| 836 | corresponding to @code{val}. |
| 837 | @end defun |
| 838 | |
| 839 | @defun Value.reference_value () |
| 840 | Return a @code{gdb.Value} object which is a reference to the value |
| 841 | encapsulated by this instance. |
| 842 | @end defun |
| 843 | |
| 844 | @defun Value.const_value () |
| 845 | Return a @code{gdb.Value} object which is a @code{const} version of the |
| 846 | value encapsulated by this instance. |
| 847 | @end defun |
| 848 | |
| 849 | @defun Value.dynamic_cast (type) |
| 850 | Like @code{Value.cast}, but works as if the C@t{++} @code{dynamic_cast} |
| 851 | operator were used. Consult a C@t{++} reference for details. |
| 852 | @end defun |
| 853 | |
| 854 | @defun Value.reinterpret_cast (type) |
| 855 | Like @code{Value.cast}, but works as if the C@t{++} @code{reinterpret_cast} |
| 856 | operator were used. Consult a C@t{++} reference for details. |
| 857 | @end defun |
| 858 | |
| 859 | @defun Value.string (@r{[}encoding@r{[}, errors@r{[}, length@r{]]]}) |
| 860 | If this @code{gdb.Value} represents a string, then this method |
| 861 | converts the contents to a Python string. Otherwise, this method will |
| 862 | throw an exception. |
| 863 | |
| 864 | Values are interpreted as strings according to the rules of the |
| 865 | current language. If the optional length argument is given, the |
| 866 | string will be converted to that length, and will include any embedded |
| 867 | zeroes that the string may contain. Otherwise, for languages |
| 868 | where the string is zero-terminated, the entire string will be |
| 869 | converted. |
| 870 | |
| 871 | For example, in C-like languages, a value is a string if it is a pointer |
| 872 | to or an array of characters or ints of type @code{wchar_t}, @code{char16_t}, |
| 873 | or @code{char32_t}. |
| 874 | |
| 875 | If the optional @var{encoding} argument is given, it must be a string |
| 876 | naming the encoding of the string in the @code{gdb.Value}, such as |
| 877 | @code{"ascii"}, @code{"iso-8859-6"} or @code{"utf-8"}. It accepts |
| 878 | the same encodings as the corresponding argument to Python's |
| 879 | @code{string.decode} method, and the Python codec machinery will be used |
| 880 | to convert the string. If @var{encoding} is not given, or if |
| 881 | @var{encoding} is the empty string, then either the @code{target-charset} |
| 882 | (@pxref{Character Sets}) will be used, or a language-specific encoding |
| 883 | will be used, if the current language is able to supply one. |
| 884 | |
| 885 | The optional @var{errors} argument is the same as the corresponding |
| 886 | argument to Python's @code{string.decode} method. |
| 887 | |
| 888 | If the optional @var{length} argument is given, the string will be |
| 889 | fetched and converted to the given length. |
| 890 | @end defun |
| 891 | |
| 892 | @defun Value.lazy_string (@r{[}encoding @r{[}, length@r{]]}) |
| 893 | If this @code{gdb.Value} represents a string, then this method |
| 894 | converts the contents to a @code{gdb.LazyString} (@pxref{Lazy Strings |
| 895 | In Python}). Otherwise, this method will throw an exception. |
| 896 | |
| 897 | If the optional @var{encoding} argument is given, it must be a string |
| 898 | naming the encoding of the @code{gdb.LazyString}. Some examples are: |
| 899 | @samp{ascii}, @samp{iso-8859-6} or @samp{utf-8}. If the |
| 900 | @var{encoding} argument is an encoding that @value{GDBN} does |
| 901 | recognize, @value{GDBN} will raise an error. |
| 902 | |
| 903 | When a lazy string is printed, the @value{GDBN} encoding machinery is |
| 904 | used to convert the string during printing. If the optional |
| 905 | @var{encoding} argument is not provided, or is an empty string, |
| 906 | @value{GDBN} will automatically select the encoding most suitable for |
| 907 | the string type. For further information on encoding in @value{GDBN} |
| 908 | please see @ref{Character Sets}. |
| 909 | |
| 910 | If the optional @var{length} argument is given, the string will be |
| 911 | fetched and encoded to the length of characters specified. If |
| 912 | the @var{length} argument is not provided, the string will be fetched |
| 913 | and encoded until a null of appropriate width is found. |
| 914 | @end defun |
| 915 | |
| 916 | @defun Value.fetch_lazy () |
| 917 | If the @code{gdb.Value} object is currently a lazy value |
| 918 | (@code{gdb.Value.is_lazy} is @code{True}), then the value is |
| 919 | fetched from the inferior. Any errors that occur in the process |
| 920 | will produce a Python exception. |
| 921 | |
| 922 | If the @code{gdb.Value} object is not a lazy value, this method |
| 923 | has no effect. |
| 924 | |
| 925 | This method does not return a value. |
| 926 | @end defun |
| 927 | |
| 928 | |
| 929 | @node Types In Python |
| 930 | @subsubsection Types In Python |
| 931 | @cindex types in Python |
| 932 | @cindex Python, working with types |
| 933 | |
| 934 | @tindex gdb.Type |
| 935 | @value{GDBN} represents types from the inferior using the class |
| 936 | @code{gdb.Type}. |
| 937 | |
| 938 | The following type-related functions are available in the @code{gdb} |
| 939 | module: |
| 940 | |
| 941 | @findex gdb.lookup_type |
| 942 | @defun gdb.lookup_type (name @r{[}, block@r{]}) |
| 943 | This function looks up a type by its @var{name}, which must be a string. |
| 944 | |
| 945 | If @var{block} is given, then @var{name} is looked up in that scope. |
| 946 | Otherwise, it is searched for globally. |
| 947 | |
| 948 | Ordinarily, this function will return an instance of @code{gdb.Type}. |
| 949 | If the named type cannot be found, it will throw an exception. |
| 950 | @end defun |
| 951 | |
| 952 | If the type is a structure or class type, or an enum type, the fields |
| 953 | of that type can be accessed using the Python @dfn{dictionary syntax}. |
| 954 | For example, if @code{some_type} is a @code{gdb.Type} instance holding |
| 955 | a structure type, you can access its @code{foo} field with: |
| 956 | |
| 957 | @smallexample |
| 958 | bar = some_type['foo'] |
| 959 | @end smallexample |
| 960 | |
| 961 | @code{bar} will be a @code{gdb.Field} object; see below under the |
| 962 | description of the @code{Type.fields} method for a description of the |
| 963 | @code{gdb.Field} class. |
| 964 | |
| 965 | An instance of @code{Type} has the following attributes: |
| 966 | |
| 967 | @defvar Type.alignof |
| 968 | The alignment of this type, in bytes. Type alignment comes from the |
| 969 | debugging information; if it was not specified, then @value{GDBN} will |
| 970 | use the relevant ABI to try to determine the alignment. In some |
| 971 | cases, even this is not possible, and zero will be returned. |
| 972 | @end defvar |
| 973 | |
| 974 | @defvar Type.code |
| 975 | The type code for this type. The type code will be one of the |
| 976 | @code{TYPE_CODE_} constants defined below. |
| 977 | @end defvar |
| 978 | |
| 979 | @defvar Type.name |
| 980 | The name of this type. If this type has no name, then @code{None} |
| 981 | is returned. |
| 982 | @end defvar |
| 983 | |
| 984 | @defvar Type.sizeof |
| 985 | The size of this type, in target @code{char} units. Usually, a |
| 986 | target's @code{char} type will be an 8-bit byte. However, on some |
| 987 | unusual platforms, this type may have a different size. |
| 988 | @end defvar |
| 989 | |
| 990 | @defvar Type.tag |
| 991 | The tag name for this type. The tag name is the name after |
| 992 | @code{struct}, @code{union}, or @code{enum} in C and C@t{++}; not all |
| 993 | languages have this concept. If this type has no tag name, then |
| 994 | @code{None} is returned. |
| 995 | @end defvar |
| 996 | |
| 997 | The following methods are provided: |
| 998 | |
| 999 | @defun Type.fields () |
| 1000 | For structure and union types, this method returns the fields. Range |
| 1001 | types have two fields, the minimum and maximum values. Enum types |
| 1002 | have one field per enum constant. Function and method types have one |
| 1003 | field per parameter. The base types of C@t{++} classes are also |
| 1004 | represented as fields. If the type has no fields, or does not fit |
| 1005 | into one of these categories, an empty sequence will be returned. |
| 1006 | |
| 1007 | Each field is a @code{gdb.Field} object, with some pre-defined attributes: |
| 1008 | @table @code |
| 1009 | @item bitpos |
| 1010 | This attribute is not available for @code{enum} or @code{static} |
| 1011 | (as in C@t{++}) fields. The value is the position, counting |
| 1012 | in bits, from the start of the containing type. |
| 1013 | |
| 1014 | @item enumval |
| 1015 | This attribute is only available for @code{enum} fields, and its value |
| 1016 | is the enumeration member's integer representation. |
| 1017 | |
| 1018 | @item name |
| 1019 | The name of the field, or @code{None} for anonymous fields. |
| 1020 | |
| 1021 | @item artificial |
| 1022 | This is @code{True} if the field is artificial, usually meaning that |
| 1023 | it was provided by the compiler and not the user. This attribute is |
| 1024 | always provided, and is @code{False} if the field is not artificial. |
| 1025 | |
| 1026 | @item is_base_class |
| 1027 | This is @code{True} if the field represents a base class of a C@t{++} |
| 1028 | structure. This attribute is always provided, and is @code{False} |
| 1029 | if the field is not a base class of the type that is the argument of |
| 1030 | @code{fields}, or if that type was not a C@t{++} class. |
| 1031 | |
| 1032 | @item bitsize |
| 1033 | If the field is packed, or is a bitfield, then this will have a |
| 1034 | non-zero value, which is the size of the field in bits. Otherwise, |
| 1035 | this will be zero; in this case the field's size is given by its type. |
| 1036 | |
| 1037 | @item type |
| 1038 | The type of the field. This is usually an instance of @code{Type}, |
| 1039 | but it can be @code{None} in some situations. |
| 1040 | |
| 1041 | @item parent_type |
| 1042 | The type which contains this field. This is an instance of |
| 1043 | @code{gdb.Type}. |
| 1044 | @end table |
| 1045 | @end defun |
| 1046 | |
| 1047 | @defun Type.array (@var{n1} @r{[}, @var{n2}@r{]}) |
| 1048 | Return a new @code{gdb.Type} object which represents an array of this |
| 1049 | type. If one argument is given, it is the inclusive upper bound of |
| 1050 | the array; in this case the lower bound is zero. If two arguments are |
| 1051 | given, the first argument is the lower bound of the array, and the |
| 1052 | second argument is the upper bound of the array. An array's length |
| 1053 | must not be negative, but the bounds can be. |
| 1054 | @end defun |
| 1055 | |
| 1056 | @defun Type.vector (@var{n1} @r{[}, @var{n2}@r{]}) |
| 1057 | Return a new @code{gdb.Type} object which represents a vector of this |
| 1058 | type. If one argument is given, it is the inclusive upper bound of |
| 1059 | the vector; in this case the lower bound is zero. If two arguments are |
| 1060 | given, the first argument is the lower bound of the vector, and the |
| 1061 | second argument is the upper bound of the vector. A vector's length |
| 1062 | must not be negative, but the bounds can be. |
| 1063 | |
| 1064 | The difference between an @code{array} and a @code{vector} is that |
| 1065 | arrays behave like in C: when used in expressions they decay to a pointer |
| 1066 | to the first element whereas vectors are treated as first class values. |
| 1067 | @end defun |
| 1068 | |
| 1069 | @defun Type.const () |
| 1070 | Return a new @code{gdb.Type} object which represents a |
| 1071 | @code{const}-qualified variant of this type. |
| 1072 | @end defun |
| 1073 | |
| 1074 | @defun Type.volatile () |
| 1075 | Return a new @code{gdb.Type} object which represents a |
| 1076 | @code{volatile}-qualified variant of this type. |
| 1077 | @end defun |
| 1078 | |
| 1079 | @defun Type.unqualified () |
| 1080 | Return a new @code{gdb.Type} object which represents an unqualified |
| 1081 | variant of this type. That is, the result is neither @code{const} nor |
| 1082 | @code{volatile}. |
| 1083 | @end defun |
| 1084 | |
| 1085 | @defun Type.range () |
| 1086 | Return a Python @code{Tuple} object that contains two elements: the |
| 1087 | low bound of the argument type and the high bound of that type. If |
| 1088 | the type does not have a range, @value{GDBN} will raise a |
| 1089 | @code{gdb.error} exception (@pxref{Exception Handling}). |
| 1090 | @end defun |
| 1091 | |
| 1092 | @defun Type.reference () |
| 1093 | Return a new @code{gdb.Type} object which represents a reference to this |
| 1094 | type. |
| 1095 | @end defun |
| 1096 | |
| 1097 | @defun Type.pointer () |
| 1098 | Return a new @code{gdb.Type} object which represents a pointer to this |
| 1099 | type. |
| 1100 | @end defun |
| 1101 | |
| 1102 | @defun Type.strip_typedefs () |
| 1103 | Return a new @code{gdb.Type} that represents the real type, |
| 1104 | after removing all layers of typedefs. |
| 1105 | @end defun |
| 1106 | |
| 1107 | @defun Type.target () |
| 1108 | Return a new @code{gdb.Type} object which represents the target type |
| 1109 | of this type. |
| 1110 | |
| 1111 | For a pointer type, the target type is the type of the pointed-to |
| 1112 | object. For an array type (meaning C-like arrays), the target type is |
| 1113 | the type of the elements of the array. For a function or method type, |
| 1114 | the target type is the type of the return value. For a complex type, |
| 1115 | the target type is the type of the elements. For a typedef, the |
| 1116 | target type is the aliased type. |
| 1117 | |
| 1118 | If the type does not have a target, this method will throw an |
| 1119 | exception. |
| 1120 | @end defun |
| 1121 | |
| 1122 | @defun Type.template_argument (n @r{[}, block@r{]}) |
| 1123 | If this @code{gdb.Type} is an instantiation of a template, this will |
| 1124 | return a new @code{gdb.Value} or @code{gdb.Type} which represents the |
| 1125 | value of the @var{n}th template argument (indexed starting at 0). |
| 1126 | |
| 1127 | If this @code{gdb.Type} is not a template type, or if the type has fewer |
| 1128 | than @var{n} template arguments, this will throw an exception. |
| 1129 | Ordinarily, only C@t{++} code will have template types. |
| 1130 | |
| 1131 | If @var{block} is given, then @var{name} is looked up in that scope. |
| 1132 | Otherwise, it is searched for globally. |
| 1133 | @end defun |
| 1134 | |
| 1135 | @defun Type.optimized_out () |
| 1136 | Return @code{gdb.Value} instance of this type whose value is optimized |
| 1137 | out. This allows a frame decorator to indicate that the value of an |
| 1138 | argument or a local variable is not known. |
| 1139 | @end defun |
| 1140 | |
| 1141 | Each type has a code, which indicates what category this type falls |
| 1142 | into. The available type categories are represented by constants |
| 1143 | defined in the @code{gdb} module: |
| 1144 | |
| 1145 | @vtable @code |
| 1146 | @vindex TYPE_CODE_PTR |
| 1147 | @item gdb.TYPE_CODE_PTR |
| 1148 | The type is a pointer. |
| 1149 | |
| 1150 | @vindex TYPE_CODE_ARRAY |
| 1151 | @item gdb.TYPE_CODE_ARRAY |
| 1152 | The type is an array. |
| 1153 | |
| 1154 | @vindex TYPE_CODE_STRUCT |
| 1155 | @item gdb.TYPE_CODE_STRUCT |
| 1156 | The type is a structure. |
| 1157 | |
| 1158 | @vindex TYPE_CODE_UNION |
| 1159 | @item gdb.TYPE_CODE_UNION |
| 1160 | The type is a union. |
| 1161 | |
| 1162 | @vindex TYPE_CODE_ENUM |
| 1163 | @item gdb.TYPE_CODE_ENUM |
| 1164 | The type is an enum. |
| 1165 | |
| 1166 | @vindex TYPE_CODE_FLAGS |
| 1167 | @item gdb.TYPE_CODE_FLAGS |
| 1168 | A bit flags type, used for things such as status registers. |
| 1169 | |
| 1170 | @vindex TYPE_CODE_FUNC |
| 1171 | @item gdb.TYPE_CODE_FUNC |
| 1172 | The type is a function. |
| 1173 | |
| 1174 | @vindex TYPE_CODE_INT |
| 1175 | @item gdb.TYPE_CODE_INT |
| 1176 | The type is an integer type. |
| 1177 | |
| 1178 | @vindex TYPE_CODE_FLT |
| 1179 | @item gdb.TYPE_CODE_FLT |
| 1180 | A floating point type. |
| 1181 | |
| 1182 | @vindex TYPE_CODE_VOID |
| 1183 | @item gdb.TYPE_CODE_VOID |
| 1184 | The special type @code{void}. |
| 1185 | |
| 1186 | @vindex TYPE_CODE_SET |
| 1187 | @item gdb.TYPE_CODE_SET |
| 1188 | A Pascal set type. |
| 1189 | |
| 1190 | @vindex TYPE_CODE_RANGE |
| 1191 | @item gdb.TYPE_CODE_RANGE |
| 1192 | A range type, that is, an integer type with bounds. |
| 1193 | |
| 1194 | @vindex TYPE_CODE_STRING |
| 1195 | @item gdb.TYPE_CODE_STRING |
| 1196 | A string type. Note that this is only used for certain languages with |
| 1197 | language-defined string types; C strings are not represented this way. |
| 1198 | |
| 1199 | @vindex TYPE_CODE_BITSTRING |
| 1200 | @item gdb.TYPE_CODE_BITSTRING |
| 1201 | A string of bits. It is deprecated. |
| 1202 | |
| 1203 | @vindex TYPE_CODE_ERROR |
| 1204 | @item gdb.TYPE_CODE_ERROR |
| 1205 | An unknown or erroneous type. |
| 1206 | |
| 1207 | @vindex TYPE_CODE_METHOD |
| 1208 | @item gdb.TYPE_CODE_METHOD |
| 1209 | A method type, as found in C@t{++}. |
| 1210 | |
| 1211 | @vindex TYPE_CODE_METHODPTR |
| 1212 | @item gdb.TYPE_CODE_METHODPTR |
| 1213 | A pointer-to-member-function. |
| 1214 | |
| 1215 | @vindex TYPE_CODE_MEMBERPTR |
| 1216 | @item gdb.TYPE_CODE_MEMBERPTR |
| 1217 | A pointer-to-member. |
| 1218 | |
| 1219 | @vindex TYPE_CODE_REF |
| 1220 | @item gdb.TYPE_CODE_REF |
| 1221 | A reference type. |
| 1222 | |
| 1223 | @vindex TYPE_CODE_RVALUE_REF |
| 1224 | @item gdb.TYPE_CODE_RVALUE_REF |
| 1225 | A C@t{++}11 rvalue reference type. |
| 1226 | |
| 1227 | @vindex TYPE_CODE_CHAR |
| 1228 | @item gdb.TYPE_CODE_CHAR |
| 1229 | A character type. |
| 1230 | |
| 1231 | @vindex TYPE_CODE_BOOL |
| 1232 | @item gdb.TYPE_CODE_BOOL |
| 1233 | A boolean type. |
| 1234 | |
| 1235 | @vindex TYPE_CODE_COMPLEX |
| 1236 | @item gdb.TYPE_CODE_COMPLEX |
| 1237 | A complex float type. |
| 1238 | |
| 1239 | @vindex TYPE_CODE_TYPEDEF |
| 1240 | @item gdb.TYPE_CODE_TYPEDEF |
| 1241 | A typedef to some other type. |
| 1242 | |
| 1243 | @vindex TYPE_CODE_NAMESPACE |
| 1244 | @item gdb.TYPE_CODE_NAMESPACE |
| 1245 | A C@t{++} namespace. |
| 1246 | |
| 1247 | @vindex TYPE_CODE_DECFLOAT |
| 1248 | @item gdb.TYPE_CODE_DECFLOAT |
| 1249 | A decimal floating point type. |
| 1250 | |
| 1251 | @vindex TYPE_CODE_INTERNAL_FUNCTION |
| 1252 | @item gdb.TYPE_CODE_INTERNAL_FUNCTION |
| 1253 | A function internal to @value{GDBN}. This is the type used to represent |
| 1254 | convenience functions. |
| 1255 | @end vtable |
| 1256 | |
| 1257 | Further support for types is provided in the @code{gdb.types} |
| 1258 | Python module (@pxref{gdb.types}). |
| 1259 | |
| 1260 | @node Pretty Printing API |
| 1261 | @subsubsection Pretty Printing API |
| 1262 | @cindex python pretty printing api |
| 1263 | |
| 1264 | A pretty-printer is just an object that holds a value and implements a |
| 1265 | specific interface, defined here. An example output is provided |
| 1266 | (@pxref{Pretty Printing}). |
| 1267 | |
| 1268 | @defun pretty_printer.children (self) |
| 1269 | @value{GDBN} will call this method on a pretty-printer to compute the |
| 1270 | children of the pretty-printer's value. |
| 1271 | |
| 1272 | This method must return an object conforming to the Python iterator |
| 1273 | protocol. Each item returned by the iterator must be a tuple holding |
| 1274 | two elements. The first element is the ``name'' of the child; the |
| 1275 | second element is the child's value. The value can be any Python |
| 1276 | object which is convertible to a @value{GDBN} value. |
| 1277 | |
| 1278 | This method is optional. If it does not exist, @value{GDBN} will act |
| 1279 | as though the value has no children. |
| 1280 | @end defun |
| 1281 | |
| 1282 | @defun pretty_printer.display_hint (self) |
| 1283 | The CLI may call this method and use its result to change the |
| 1284 | formatting of a value. The result will also be supplied to an MI |
| 1285 | consumer as a @samp{displayhint} attribute of the variable being |
| 1286 | printed. |
| 1287 | |
| 1288 | This method is optional. If it does exist, this method must return a |
| 1289 | string. |
| 1290 | |
| 1291 | Some display hints are predefined by @value{GDBN}: |
| 1292 | |
| 1293 | @table @samp |
| 1294 | @item array |
| 1295 | Indicate that the object being printed is ``array-like''. The CLI |
| 1296 | uses this to respect parameters such as @code{set print elements} and |
| 1297 | @code{set print array}. |
| 1298 | |
| 1299 | @item map |
| 1300 | Indicate that the object being printed is ``map-like'', and that the |
| 1301 | children of this value can be assumed to alternate between keys and |
| 1302 | values. |
| 1303 | |
| 1304 | @item string |
| 1305 | Indicate that the object being printed is ``string-like''. If the |
| 1306 | printer's @code{to_string} method returns a Python string of some |
| 1307 | kind, then @value{GDBN} will call its internal language-specific |
| 1308 | string-printing function to format the string. For the CLI this means |
| 1309 | adding quotation marks, possibly escaping some characters, respecting |
| 1310 | @code{set print elements}, and the like. |
| 1311 | @end table |
| 1312 | @end defun |
| 1313 | |
| 1314 | @defun pretty_printer.to_string (self) |
| 1315 | @value{GDBN} will call this method to display the string |
| 1316 | representation of the value passed to the object's constructor. |
| 1317 | |
| 1318 | When printing from the CLI, if the @code{to_string} method exists, |
| 1319 | then @value{GDBN} will prepend its result to the values returned by |
| 1320 | @code{children}. Exactly how this formatting is done is dependent on |
| 1321 | the display hint, and may change as more hints are added. Also, |
| 1322 | depending on the print settings (@pxref{Print Settings}), the CLI may |
| 1323 | print just the result of @code{to_string} in a stack trace, omitting |
| 1324 | the result of @code{children}. |
| 1325 | |
| 1326 | If this method returns a string, it is printed verbatim. |
| 1327 | |
| 1328 | Otherwise, if this method returns an instance of @code{gdb.Value}, |
| 1329 | then @value{GDBN} prints this value. This may result in a call to |
| 1330 | another pretty-printer. |
| 1331 | |
| 1332 | If instead the method returns a Python value which is convertible to a |
| 1333 | @code{gdb.Value}, then @value{GDBN} performs the conversion and prints |
| 1334 | the resulting value. Again, this may result in a call to another |
| 1335 | pretty-printer. Python scalars (integers, floats, and booleans) and |
| 1336 | strings are convertible to @code{gdb.Value}; other types are not. |
| 1337 | |
| 1338 | Finally, if this method returns @code{None} then no further operations |
| 1339 | are peformed in this method and nothing is printed. |
| 1340 | |
| 1341 | If the result is not one of these types, an exception is raised. |
| 1342 | @end defun |
| 1343 | |
| 1344 | @value{GDBN} provides a function which can be used to look up the |
| 1345 | default pretty-printer for a @code{gdb.Value}: |
| 1346 | |
| 1347 | @findex gdb.default_visualizer |
| 1348 | @defun gdb.default_visualizer (value) |
| 1349 | This function takes a @code{gdb.Value} object as an argument. If a |
| 1350 | pretty-printer for this value exists, then it is returned. If no such |
| 1351 | printer exists, then this returns @code{None}. |
| 1352 | @end defun |
| 1353 | |
| 1354 | @node Selecting Pretty-Printers |
| 1355 | @subsubsection Selecting Pretty-Printers |
| 1356 | @cindex selecting python pretty-printers |
| 1357 | |
| 1358 | The Python list @code{gdb.pretty_printers} contains an array of |
| 1359 | functions or callable objects that have been registered via addition |
| 1360 | as a pretty-printer. Printers in this list are called @code{global} |
| 1361 | printers, they're available when debugging all inferiors. |
| 1362 | Each @code{gdb.Progspace} contains a @code{pretty_printers} attribute. |
| 1363 | Each @code{gdb.Objfile} also contains a @code{pretty_printers} |
| 1364 | attribute. |
| 1365 | |
| 1366 | Each function on these lists is passed a single @code{gdb.Value} |
| 1367 | argument and should return a pretty-printer object conforming to the |
| 1368 | interface definition above (@pxref{Pretty Printing API}). If a function |
| 1369 | cannot create a pretty-printer for the value, it should return |
| 1370 | @code{None}. |
| 1371 | |
| 1372 | @value{GDBN} first checks the @code{pretty_printers} attribute of each |
| 1373 | @code{gdb.Objfile} in the current program space and iteratively calls |
| 1374 | each enabled lookup routine in the list for that @code{gdb.Objfile} |
| 1375 | until it receives a pretty-printer object. |
| 1376 | If no pretty-printer is found in the objfile lists, @value{GDBN} then |
| 1377 | searches the pretty-printer list of the current program space, |
| 1378 | calling each enabled function until an object is returned. |
| 1379 | After these lists have been exhausted, it tries the global |
| 1380 | @code{gdb.pretty_printers} list, again calling each enabled function until an |
| 1381 | object is returned. |
| 1382 | |
| 1383 | The order in which the objfiles are searched is not specified. For a |
| 1384 | given list, functions are always invoked from the head of the list, |
| 1385 | and iterated over sequentially until the end of the list, or a printer |
| 1386 | object is returned. |
| 1387 | |
| 1388 | For various reasons a pretty-printer may not work. |
| 1389 | For example, the underlying data structure may have changed and |
| 1390 | the pretty-printer is out of date. |
| 1391 | |
| 1392 | The consequences of a broken pretty-printer are severe enough that |
| 1393 | @value{GDBN} provides support for enabling and disabling individual |
| 1394 | printers. For example, if @code{print frame-arguments} is on, |
| 1395 | a backtrace can become highly illegible if any argument is printed |
| 1396 | with a broken printer. |
| 1397 | |
| 1398 | Pretty-printers are enabled and disabled by attaching an @code{enabled} |
| 1399 | attribute to the registered function or callable object. If this attribute |
| 1400 | is present and its value is @code{False}, the printer is disabled, otherwise |
| 1401 | the printer is enabled. |
| 1402 | |
| 1403 | @node Writing a Pretty-Printer |
| 1404 | @subsubsection Writing a Pretty-Printer |
| 1405 | @cindex writing a pretty-printer |
| 1406 | |
| 1407 | A pretty-printer consists of two parts: a lookup function to detect |
| 1408 | if the type is supported, and the printer itself. |
| 1409 | |
| 1410 | Here is an example showing how a @code{std::string} printer might be |
| 1411 | written. @xref{Pretty Printing API}, for details on the API this class |
| 1412 | must provide. |
| 1413 | |
| 1414 | @smallexample |
| 1415 | class StdStringPrinter(object): |
| 1416 | "Print a std::string" |
| 1417 | |
| 1418 | def __init__(self, val): |
| 1419 | self.val = val |
| 1420 | |
| 1421 | def to_string(self): |
| 1422 | return self.val['_M_dataplus']['_M_p'] |
| 1423 | |
| 1424 | def display_hint(self): |
| 1425 | return 'string' |
| 1426 | @end smallexample |
| 1427 | |
| 1428 | And here is an example showing how a lookup function for the printer |
| 1429 | example above might be written. |
| 1430 | |
| 1431 | @smallexample |
| 1432 | def str_lookup_function(val): |
| 1433 | lookup_tag = val.type.tag |
| 1434 | if lookup_tag == None: |
| 1435 | return None |
| 1436 | regex = re.compile("^std::basic_string<char,.*>$") |
| 1437 | if regex.match(lookup_tag): |
| 1438 | return StdStringPrinter(val) |
| 1439 | return None |
| 1440 | @end smallexample |
| 1441 | |
| 1442 | The example lookup function extracts the value's type, and attempts to |
| 1443 | match it to a type that it can pretty-print. If it is a type the |
| 1444 | printer can pretty-print, it will return a printer object. If not, it |
| 1445 | returns @code{None}. |
| 1446 | |
| 1447 | We recommend that you put your core pretty-printers into a Python |
| 1448 | package. If your pretty-printers are for use with a library, we |
| 1449 | further recommend embedding a version number into the package name. |
| 1450 | This practice will enable @value{GDBN} to load multiple versions of |
| 1451 | your pretty-printers at the same time, because they will have |
| 1452 | different names. |
| 1453 | |
| 1454 | You should write auto-loaded code (@pxref{Python Auto-loading}) such that it |
| 1455 | can be evaluated multiple times without changing its meaning. An |
| 1456 | ideal auto-load file will consist solely of @code{import}s of your |
| 1457 | printer modules, followed by a call to a register pretty-printers with |
| 1458 | the current objfile. |
| 1459 | |
| 1460 | Taken as a whole, this approach will scale nicely to multiple |
| 1461 | inferiors, each potentially using a different library version. |
| 1462 | Embedding a version number in the Python package name will ensure that |
| 1463 | @value{GDBN} is able to load both sets of printers simultaneously. |
| 1464 | Then, because the search for pretty-printers is done by objfile, and |
| 1465 | because your auto-loaded code took care to register your library's |
| 1466 | printers with a specific objfile, @value{GDBN} will find the correct |
| 1467 | printers for the specific version of the library used by each |
| 1468 | inferior. |
| 1469 | |
| 1470 | To continue the @code{std::string} example (@pxref{Pretty Printing API}), |
| 1471 | this code might appear in @code{gdb.libstdcxx.v6}: |
| 1472 | |
| 1473 | @smallexample |
| 1474 | def register_printers(objfile): |
| 1475 | objfile.pretty_printers.append(str_lookup_function) |
| 1476 | @end smallexample |
| 1477 | |
| 1478 | @noindent |
| 1479 | And then the corresponding contents of the auto-load file would be: |
| 1480 | |
| 1481 | @smallexample |
| 1482 | import gdb.libstdcxx.v6 |
| 1483 | gdb.libstdcxx.v6.register_printers(gdb.current_objfile()) |
| 1484 | @end smallexample |
| 1485 | |
| 1486 | The previous example illustrates a basic pretty-printer. |
| 1487 | There are a few things that can be improved on. |
| 1488 | The printer doesn't have a name, making it hard to identify in a |
| 1489 | list of installed printers. The lookup function has a name, but |
| 1490 | lookup functions can have arbitrary, even identical, names. |
| 1491 | |
| 1492 | Second, the printer only handles one type, whereas a library typically has |
| 1493 | several types. One could install a lookup function for each desired type |
| 1494 | in the library, but one could also have a single lookup function recognize |
| 1495 | several types. The latter is the conventional way this is handled. |
| 1496 | If a pretty-printer can handle multiple data types, then its |
| 1497 | @dfn{subprinters} are the printers for the individual data types. |
| 1498 | |
| 1499 | The @code{gdb.printing} module provides a formal way of solving these |
| 1500 | problems (@pxref{gdb.printing}). |
| 1501 | Here is another example that handles multiple types. |
| 1502 | |
| 1503 | These are the types we are going to pretty-print: |
| 1504 | |
| 1505 | @smallexample |
| 1506 | struct foo @{ int a, b; @}; |
| 1507 | struct bar @{ struct foo x, y; @}; |
| 1508 | @end smallexample |
| 1509 | |
| 1510 | Here are the printers: |
| 1511 | |
| 1512 | @smallexample |
| 1513 | class fooPrinter: |
| 1514 | """Print a foo object.""" |
| 1515 | |
| 1516 | def __init__(self, val): |
| 1517 | self.val = val |
| 1518 | |
| 1519 | def to_string(self): |
| 1520 | return ("a=<" + str(self.val["a"]) + |
| 1521 | "> b=<" + str(self.val["b"]) + ">") |
| 1522 | |
| 1523 | class barPrinter: |
| 1524 | """Print a bar object.""" |
| 1525 | |
| 1526 | def __init__(self, val): |
| 1527 | self.val = val |
| 1528 | |
| 1529 | def to_string(self): |
| 1530 | return ("x=<" + str(self.val["x"]) + |
| 1531 | "> y=<" + str(self.val["y"]) + ">") |
| 1532 | @end smallexample |
| 1533 | |
| 1534 | This example doesn't need a lookup function, that is handled by the |
| 1535 | @code{gdb.printing} module. Instead a function is provided to build up |
| 1536 | the object that handles the lookup. |
| 1537 | |
| 1538 | @smallexample |
| 1539 | import gdb.printing |
| 1540 | |
| 1541 | def build_pretty_printer(): |
| 1542 | pp = gdb.printing.RegexpCollectionPrettyPrinter( |
| 1543 | "my_library") |
| 1544 | pp.add_printer('foo', '^foo$', fooPrinter) |
| 1545 | pp.add_printer('bar', '^bar$', barPrinter) |
| 1546 | return pp |
| 1547 | @end smallexample |
| 1548 | |
| 1549 | And here is the autoload support: |
| 1550 | |
| 1551 | @smallexample |
| 1552 | import gdb.printing |
| 1553 | import my_library |
| 1554 | gdb.printing.register_pretty_printer( |
| 1555 | gdb.current_objfile(), |
| 1556 | my_library.build_pretty_printer()) |
| 1557 | @end smallexample |
| 1558 | |
| 1559 | Finally, when this printer is loaded into @value{GDBN}, here is the |
| 1560 | corresponding output of @samp{info pretty-printer}: |
| 1561 | |
| 1562 | @smallexample |
| 1563 | (gdb) info pretty-printer |
| 1564 | my_library.so: |
| 1565 | my_library |
| 1566 | foo |
| 1567 | bar |
| 1568 | @end smallexample |
| 1569 | |
| 1570 | @node Type Printing API |
| 1571 | @subsubsection Type Printing API |
| 1572 | @cindex type printing API for Python |
| 1573 | |
| 1574 | @value{GDBN} provides a way for Python code to customize type display. |
| 1575 | This is mainly useful for substituting canonical typedef names for |
| 1576 | types. |
| 1577 | |
| 1578 | @cindex type printer |
| 1579 | A @dfn{type printer} is just a Python object conforming to a certain |
| 1580 | protocol. A simple base class implementing the protocol is provided; |
| 1581 | see @ref{gdb.types}. A type printer must supply at least: |
| 1582 | |
| 1583 | @defivar type_printer enabled |
| 1584 | A boolean which is True if the printer is enabled, and False |
| 1585 | otherwise. This is manipulated by the @code{enable type-printer} |
| 1586 | and @code{disable type-printer} commands. |
| 1587 | @end defivar |
| 1588 | |
| 1589 | @defivar type_printer name |
| 1590 | The name of the type printer. This must be a string. This is used by |
| 1591 | the @code{enable type-printer} and @code{disable type-printer} |
| 1592 | commands. |
| 1593 | @end defivar |
| 1594 | |
| 1595 | @defmethod type_printer instantiate (self) |
| 1596 | This is called by @value{GDBN} at the start of type-printing. It is |
| 1597 | only called if the type printer is enabled. This method must return a |
| 1598 | new object that supplies a @code{recognize} method, as described below. |
| 1599 | @end defmethod |
| 1600 | |
| 1601 | |
| 1602 | When displaying a type, say via the @code{ptype} command, @value{GDBN} |
| 1603 | will compute a list of type recognizers. This is done by iterating |
| 1604 | first over the per-objfile type printers (@pxref{Objfiles In Python}), |
| 1605 | followed by the per-progspace type printers (@pxref{Progspaces In |
| 1606 | Python}), and finally the global type printers. |
| 1607 | |
| 1608 | @value{GDBN} will call the @code{instantiate} method of each enabled |
| 1609 | type printer. If this method returns @code{None}, then the result is |
| 1610 | ignored; otherwise, it is appended to the list of recognizers. |
| 1611 | |
| 1612 | Then, when @value{GDBN} is going to display a type name, it iterates |
| 1613 | over the list of recognizers. For each one, it calls the recognition |
| 1614 | function, stopping if the function returns a non-@code{None} value. |
| 1615 | The recognition function is defined as: |
| 1616 | |
| 1617 | @defmethod type_recognizer recognize (self, type) |
| 1618 | If @var{type} is not recognized, return @code{None}. Otherwise, |
| 1619 | return a string which is to be printed as the name of @var{type}. |
| 1620 | The @var{type} argument will be an instance of @code{gdb.Type} |
| 1621 | (@pxref{Types In Python}). |
| 1622 | @end defmethod |
| 1623 | |
| 1624 | @value{GDBN} uses this two-pass approach so that type printers can |
| 1625 | efficiently cache information without holding on to it too long. For |
| 1626 | example, it can be convenient to look up type information in a type |
| 1627 | printer and hold it for a recognizer's lifetime; if a single pass were |
| 1628 | done then type printers would have to make use of the event system in |
| 1629 | order to avoid holding information that could become stale as the |
| 1630 | inferior changed. |
| 1631 | |
| 1632 | @node Frame Filter API |
| 1633 | @subsubsection Filtering Frames |
| 1634 | @cindex frame filters api |
| 1635 | |
| 1636 | Frame filters are Python objects that manipulate the visibility of a |
| 1637 | frame or frames when a backtrace (@pxref{Backtrace}) is printed by |
| 1638 | @value{GDBN}. |
| 1639 | |
| 1640 | Only commands that print a backtrace, or, in the case of @sc{gdb/mi} |
| 1641 | commands (@pxref{GDB/MI}), those that return a collection of frames |
| 1642 | are affected. The commands that work with frame filters are: |
| 1643 | |
| 1644 | @code{backtrace} (@pxref{backtrace-command,, The backtrace command}), |
| 1645 | @code{-stack-list-frames} |
| 1646 | (@pxref{-stack-list-frames,, The -stack-list-frames command}), |
| 1647 | @code{-stack-list-variables} (@pxref{-stack-list-variables,, The |
| 1648 | -stack-list-variables command}), @code{-stack-list-arguments} |
| 1649 | @pxref{-stack-list-arguments,, The -stack-list-arguments command}) and |
| 1650 | @code{-stack-list-locals} (@pxref{-stack-list-locals,, The |
| 1651 | -stack-list-locals command}). |
| 1652 | |
| 1653 | A frame filter works by taking an iterator as an argument, applying |
| 1654 | actions to the contents of that iterator, and returning another |
| 1655 | iterator (or, possibly, the same iterator it was provided in the case |
| 1656 | where the filter does not perform any operations). Typically, frame |
| 1657 | filters utilize tools such as the Python's @code{itertools} module to |
| 1658 | work with and create new iterators from the source iterator. |
| 1659 | Regardless of how a filter chooses to apply actions, it must not alter |
| 1660 | the underlying @value{GDBN} frame or frames, or attempt to alter the |
| 1661 | call-stack within @value{GDBN}. This preserves data integrity within |
| 1662 | @value{GDBN}. Frame filters are executed on a priority basis and care |
| 1663 | should be taken that some frame filters may have been executed before, |
| 1664 | and that some frame filters will be executed after. |
| 1665 | |
| 1666 | An important consideration when designing frame filters, and well |
| 1667 | worth reflecting upon, is that frame filters should avoid unwinding |
| 1668 | the call stack if possible. Some stacks can run very deep, into the |
| 1669 | tens of thousands in some cases. To search every frame when a frame |
| 1670 | filter executes may be too expensive at that step. The frame filter |
| 1671 | cannot know how many frames it has to iterate over, and it may have to |
| 1672 | iterate through them all. This ends up duplicating effort as |
| 1673 | @value{GDBN} performs this iteration when it prints the frames. If |
| 1674 | the filter can defer unwinding frames until frame decorators are |
| 1675 | executed, after the last filter has executed, it should. @xref{Frame |
| 1676 | Decorator API}, for more information on decorators. Also, there are |
| 1677 | examples for both frame decorators and filters in later chapters. |
| 1678 | @xref{Writing a Frame Filter}, for more information. |
| 1679 | |
| 1680 | The Python dictionary @code{gdb.frame_filters} contains key/object |
| 1681 | pairings that comprise a frame filter. Frame filters in this |
| 1682 | dictionary are called @code{global} frame filters, and they are |
| 1683 | available when debugging all inferiors. These frame filters must |
| 1684 | register with the dictionary directly. In addition to the |
| 1685 | @code{global} dictionary, there are other dictionaries that are loaded |
| 1686 | with different inferiors via auto-loading (@pxref{Python |
| 1687 | Auto-loading}). The two other areas where frame filter dictionaries |
| 1688 | can be found are: @code{gdb.Progspace} which contains a |
| 1689 | @code{frame_filters} dictionary attribute, and each @code{gdb.Objfile} |
| 1690 | object which also contains a @code{frame_filters} dictionary |
| 1691 | attribute. |
| 1692 | |
| 1693 | When a command is executed from @value{GDBN} that is compatible with |
| 1694 | frame filters, @value{GDBN} combines the @code{global}, |
| 1695 | @code{gdb.Progspace} and all @code{gdb.Objfile} dictionaries currently |
| 1696 | loaded. All of the @code{gdb.Objfile} dictionaries are combined, as |
| 1697 | several frames, and thus several object files, might be in use. |
| 1698 | @value{GDBN} then prunes any frame filter whose @code{enabled} |
| 1699 | attribute is @code{False}. This pruned list is then sorted according |
| 1700 | to the @code{priority} attribute in each filter. |
| 1701 | |
| 1702 | Once the dictionaries are combined, pruned and sorted, @value{GDBN} |
| 1703 | creates an iterator which wraps each frame in the call stack in a |
| 1704 | @code{FrameDecorator} object, and calls each filter in order. The |
| 1705 | output from the previous filter will always be the input to the next |
| 1706 | filter, and so on. |
| 1707 | |
| 1708 | Frame filters have a mandatory interface which each frame filter must |
| 1709 | implement, defined here: |
| 1710 | |
| 1711 | @defun FrameFilter.filter (iterator) |
| 1712 | @value{GDBN} will call this method on a frame filter when it has |
| 1713 | reached the order in the priority list for that filter. |
| 1714 | |
| 1715 | For example, if there are four frame filters: |
| 1716 | |
| 1717 | @smallexample |
| 1718 | Name Priority |
| 1719 | |
| 1720 | Filter1 5 |
| 1721 | Filter2 10 |
| 1722 | Filter3 100 |
| 1723 | Filter4 1 |
| 1724 | @end smallexample |
| 1725 | |
| 1726 | The order that the frame filters will be called is: |
| 1727 | |
| 1728 | @smallexample |
| 1729 | Filter3 -> Filter2 -> Filter1 -> Filter4 |
| 1730 | @end smallexample |
| 1731 | |
| 1732 | Note that the output from @code{Filter3} is passed to the input of |
| 1733 | @code{Filter2}, and so on. |
| 1734 | |
| 1735 | This @code{filter} method is passed a Python iterator. This iterator |
| 1736 | contains a sequence of frame decorators that wrap each |
| 1737 | @code{gdb.Frame}, or a frame decorator that wraps another frame |
| 1738 | decorator. The first filter that is executed in the sequence of frame |
| 1739 | filters will receive an iterator entirely comprised of default |
| 1740 | @code{FrameDecorator} objects. However, after each frame filter is |
| 1741 | executed, the previous frame filter may have wrapped some or all of |
| 1742 | the frame decorators with their own frame decorator. As frame |
| 1743 | decorators must also conform to a mandatory interface, these |
| 1744 | decorators can be assumed to act in a uniform manner (@pxref{Frame |
| 1745 | Decorator API}). |
| 1746 | |
| 1747 | This method must return an object conforming to the Python iterator |
| 1748 | protocol. Each item in the iterator must be an object conforming to |
| 1749 | the frame decorator interface. If a frame filter does not wish to |
| 1750 | perform any operations on this iterator, it should return that |
| 1751 | iterator untouched. |
| 1752 | |
| 1753 | This method is not optional. If it does not exist, @value{GDBN} will |
| 1754 | raise and print an error. |
| 1755 | @end defun |
| 1756 | |
| 1757 | @defvar FrameFilter.name |
| 1758 | The @code{name} attribute must be Python string which contains the |
| 1759 | name of the filter displayed by @value{GDBN} (@pxref{Frame Filter |
| 1760 | Management}). This attribute may contain any combination of letters |
| 1761 | or numbers. Care should be taken to ensure that it is unique. This |
| 1762 | attribute is mandatory. |
| 1763 | @end defvar |
| 1764 | |
| 1765 | @defvar FrameFilter.enabled |
| 1766 | The @code{enabled} attribute must be Python boolean. This attribute |
| 1767 | indicates to @value{GDBN} whether the frame filter is enabled, and |
| 1768 | should be considered when frame filters are executed. If |
| 1769 | @code{enabled} is @code{True}, then the frame filter will be executed |
| 1770 | when any of the backtrace commands detailed earlier in this chapter |
| 1771 | are executed. If @code{enabled} is @code{False}, then the frame |
| 1772 | filter will not be executed. This attribute is mandatory. |
| 1773 | @end defvar |
| 1774 | |
| 1775 | @defvar FrameFilter.priority |
| 1776 | The @code{priority} attribute must be Python integer. This attribute |
| 1777 | controls the order of execution in relation to other frame filters. |
| 1778 | There are no imposed limits on the range of @code{priority} other than |
| 1779 | it must be a valid integer. The higher the @code{priority} attribute, |
| 1780 | the sooner the frame filter will be executed in relation to other |
| 1781 | frame filters. Although @code{priority} can be negative, it is |
| 1782 | recommended practice to assume zero is the lowest priority that a |
| 1783 | frame filter can be assigned. Frame filters that have the same |
| 1784 | priority are executed in unsorted order in that priority slot. This |
| 1785 | attribute is mandatory. 100 is a good default priority. |
| 1786 | @end defvar |
| 1787 | |
| 1788 | @node Frame Decorator API |
| 1789 | @subsubsection Decorating Frames |
| 1790 | @cindex frame decorator api |
| 1791 | |
| 1792 | Frame decorators are sister objects to frame filters (@pxref{Frame |
| 1793 | Filter API}). Frame decorators are applied by a frame filter and can |
| 1794 | only be used in conjunction with frame filters. |
| 1795 | |
| 1796 | The purpose of a frame decorator is to customize the printed content |
| 1797 | of each @code{gdb.Frame} in commands where frame filters are executed. |
| 1798 | This concept is called decorating a frame. Frame decorators decorate |
| 1799 | a @code{gdb.Frame} with Python code contained within each API call. |
| 1800 | This separates the actual data contained in a @code{gdb.Frame} from |
| 1801 | the decorated data produced by a frame decorator. This abstraction is |
| 1802 | necessary to maintain integrity of the data contained in each |
| 1803 | @code{gdb.Frame}. |
| 1804 | |
| 1805 | Frame decorators have a mandatory interface, defined below. |
| 1806 | |
| 1807 | @value{GDBN} already contains a frame decorator called |
| 1808 | @code{FrameDecorator}. This contains substantial amounts of |
| 1809 | boilerplate code to decorate the content of a @code{gdb.Frame}. It is |
| 1810 | recommended that other frame decorators inherit and extend this |
| 1811 | object, and only to override the methods needed. |
| 1812 | |
| 1813 | @tindex gdb.FrameDecorator |
| 1814 | @code{FrameDecorator} is defined in the Python module |
| 1815 | @code{gdb.FrameDecorator}, so your code can import it like: |
| 1816 | @smallexample |
| 1817 | from gdb.FrameDecorator import FrameDecorator |
| 1818 | @end smallexample |
| 1819 | |
| 1820 | @defun FrameDecorator.elided (self) |
| 1821 | |
| 1822 | The @code{elided} method groups frames together in a hierarchical |
| 1823 | system. An example would be an interpreter, where multiple low-level |
| 1824 | frames make up a single call in the interpreted language. In this |
| 1825 | example, the frame filter would elide the low-level frames and present |
| 1826 | a single high-level frame, representing the call in the interpreted |
| 1827 | language, to the user. |
| 1828 | |
| 1829 | The @code{elided} function must return an iterable and this iterable |
| 1830 | must contain the frames that are being elided wrapped in a suitable |
| 1831 | frame decorator. If no frames are being elided this function may |
| 1832 | return an empty iterable, or @code{None}. Elided frames are indented |
| 1833 | from normal frames in a @code{CLI} backtrace, or in the case of |
| 1834 | @code{GDB/MI}, are placed in the @code{children} field of the eliding |
| 1835 | frame. |
| 1836 | |
| 1837 | It is the frame filter's task to also filter out the elided frames from |
| 1838 | the source iterator. This will avoid printing the frame twice. |
| 1839 | @end defun |
| 1840 | |
| 1841 | @defun FrameDecorator.function (self) |
| 1842 | |
| 1843 | This method returns the name of the function in the frame that is to |
| 1844 | be printed. |
| 1845 | |
| 1846 | This method must return a Python string describing the function, or |
| 1847 | @code{None}. |
| 1848 | |
| 1849 | If this function returns @code{None}, @value{GDBN} will not print any |
| 1850 | data for this field. |
| 1851 | @end defun |
| 1852 | |
| 1853 | @defun FrameDecorator.address (self) |
| 1854 | |
| 1855 | This method returns the address of the frame that is to be printed. |
| 1856 | |
| 1857 | This method must return a Python numeric integer type of sufficient |
| 1858 | size to describe the address of the frame, or @code{None}. |
| 1859 | |
| 1860 | If this function returns a @code{None}, @value{GDBN} will not print |
| 1861 | any data for this field. |
| 1862 | @end defun |
| 1863 | |
| 1864 | @defun FrameDecorator.filename (self) |
| 1865 | |
| 1866 | This method returns the filename and path associated with this frame. |
| 1867 | |
| 1868 | This method must return a Python string containing the filename and |
| 1869 | the path to the object file backing the frame, or @code{None}. |
| 1870 | |
| 1871 | If this function returns a @code{None}, @value{GDBN} will not print |
| 1872 | any data for this field. |
| 1873 | @end defun |
| 1874 | |
| 1875 | @defun FrameDecorator.line (self): |
| 1876 | |
| 1877 | This method returns the line number associated with the current |
| 1878 | position within the function addressed by this frame. |
| 1879 | |
| 1880 | This method must return a Python integer type, or @code{None}. |
| 1881 | |
| 1882 | If this function returns a @code{None}, @value{GDBN} will not print |
| 1883 | any data for this field. |
| 1884 | @end defun |
| 1885 | |
| 1886 | @defun FrameDecorator.frame_args (self) |
| 1887 | @anchor{frame_args} |
| 1888 | |
| 1889 | This method must return an iterable, or @code{None}. Returning an |
| 1890 | empty iterable, or @code{None} means frame arguments will not be |
| 1891 | printed for this frame. This iterable must contain objects that |
| 1892 | implement two methods, described here. |
| 1893 | |
| 1894 | This object must implement a @code{argument} method which takes a |
| 1895 | single @code{self} parameter and must return a @code{gdb.Symbol} |
| 1896 | (@pxref{Symbols In Python}), or a Python string. The object must also |
| 1897 | implement a @code{value} method which takes a single @code{self} |
| 1898 | parameter and must return a @code{gdb.Value} (@pxref{Values From |
| 1899 | Inferior}), a Python value, or @code{None}. If the @code{value} |
| 1900 | method returns @code{None}, and the @code{argument} method returns a |
| 1901 | @code{gdb.Symbol}, @value{GDBN} will look-up and print the value of |
| 1902 | the @code{gdb.Symbol} automatically. |
| 1903 | |
| 1904 | A brief example: |
| 1905 | |
| 1906 | @smallexample |
| 1907 | class SymValueWrapper(): |
| 1908 | |
| 1909 | def __init__(self, symbol, value): |
| 1910 | self.sym = symbol |
| 1911 | self.val = value |
| 1912 | |
| 1913 | def value(self): |
| 1914 | return self.val |
| 1915 | |
| 1916 | def symbol(self): |
| 1917 | return self.sym |
| 1918 | |
| 1919 | class SomeFrameDecorator() |
| 1920 | ... |
| 1921 | ... |
| 1922 | def frame_args(self): |
| 1923 | args = [] |
| 1924 | try: |
| 1925 | block = self.inferior_frame.block() |
| 1926 | except: |
| 1927 | return None |
| 1928 | |
| 1929 | # Iterate over all symbols in a block. Only add |
| 1930 | # symbols that are arguments. |
| 1931 | for sym in block: |
| 1932 | if not sym.is_argument: |
| 1933 | continue |
| 1934 | args.append(SymValueWrapper(sym,None)) |
| 1935 | |
| 1936 | # Add example synthetic argument. |
| 1937 | args.append(SymValueWrapper(``foo'', 42)) |
| 1938 | |
| 1939 | return args |
| 1940 | @end smallexample |
| 1941 | @end defun |
| 1942 | |
| 1943 | @defun FrameDecorator.frame_locals (self) |
| 1944 | |
| 1945 | This method must return an iterable or @code{None}. Returning an |
| 1946 | empty iterable, or @code{None} means frame local arguments will not be |
| 1947 | printed for this frame. |
| 1948 | |
| 1949 | The object interface, the description of the various strategies for |
| 1950 | reading frame locals, and the example are largely similar to those |
| 1951 | described in the @code{frame_args} function, (@pxref{frame_args,,The |
| 1952 | frame filter frame_args function}). Below is a modified example: |
| 1953 | |
| 1954 | @smallexample |
| 1955 | class SomeFrameDecorator() |
| 1956 | ... |
| 1957 | ... |
| 1958 | def frame_locals(self): |
| 1959 | vars = [] |
| 1960 | try: |
| 1961 | block = self.inferior_frame.block() |
| 1962 | except: |
| 1963 | return None |
| 1964 | |
| 1965 | # Iterate over all symbols in a block. Add all |
| 1966 | # symbols, except arguments. |
| 1967 | for sym in block: |
| 1968 | if sym.is_argument: |
| 1969 | continue |
| 1970 | vars.append(SymValueWrapper(sym,None)) |
| 1971 | |
| 1972 | # Add an example of a synthetic local variable. |
| 1973 | vars.append(SymValueWrapper(``bar'', 99)) |
| 1974 | |
| 1975 | return vars |
| 1976 | @end smallexample |
| 1977 | @end defun |
| 1978 | |
| 1979 | @defun FrameDecorator.inferior_frame (self): |
| 1980 | |
| 1981 | This method must return the underlying @code{gdb.Frame} that this |
| 1982 | frame decorator is decorating. @value{GDBN} requires the underlying |
| 1983 | frame for internal frame information to determine how to print certain |
| 1984 | values when printing a frame. |
| 1985 | @end defun |
| 1986 | |
| 1987 | @node Writing a Frame Filter |
| 1988 | @subsubsection Writing a Frame Filter |
| 1989 | @cindex writing a frame filter |
| 1990 | |
| 1991 | There are three basic elements that a frame filter must implement: it |
| 1992 | must correctly implement the documented interface (@pxref{Frame Filter |
| 1993 | API}), it must register itself with @value{GDBN}, and finally, it must |
| 1994 | decide if it is to work on the data provided by @value{GDBN}. In all |
| 1995 | cases, whether it works on the iterator or not, each frame filter must |
| 1996 | return an iterator. A bare-bones frame filter follows the pattern in |
| 1997 | the following example. |
| 1998 | |
| 1999 | @smallexample |
| 2000 | import gdb |
| 2001 | |
| 2002 | class FrameFilter(): |
| 2003 | |
| 2004 | def __init__(self): |
| 2005 | # Frame filter attribute creation. |
| 2006 | # |
| 2007 | # 'name' is the name of the filter that GDB will display. |
| 2008 | # |
| 2009 | # 'priority' is the priority of the filter relative to other |
| 2010 | # filters. |
| 2011 | # |
| 2012 | # 'enabled' is a boolean that indicates whether this filter is |
| 2013 | # enabled and should be executed. |
| 2014 | |
| 2015 | self.name = "Foo" |
| 2016 | self.priority = 100 |
| 2017 | self.enabled = True |
| 2018 | |
| 2019 | # Register this frame filter with the global frame_filters |
| 2020 | # dictionary. |
| 2021 | gdb.frame_filters[self.name] = self |
| 2022 | |
| 2023 | def filter(self, frame_iter): |
| 2024 | # Just return the iterator. |
| 2025 | return frame_iter |
| 2026 | @end smallexample |
| 2027 | |
| 2028 | The frame filter in the example above implements the three |
| 2029 | requirements for all frame filters. It implements the API, self |
| 2030 | registers, and makes a decision on the iterator (in this case, it just |
| 2031 | returns the iterator untouched). |
| 2032 | |
| 2033 | The first step is attribute creation and assignment, and as shown in |
| 2034 | the comments the filter assigns the following attributes: @code{name}, |
| 2035 | @code{priority} and whether the filter should be enabled with the |
| 2036 | @code{enabled} attribute. |
| 2037 | |
| 2038 | The second step is registering the frame filter with the dictionary or |
| 2039 | dictionaries that the frame filter has interest in. As shown in the |
| 2040 | comments, this filter just registers itself with the global dictionary |
| 2041 | @code{gdb.frame_filters}. As noted earlier, @code{gdb.frame_filters} |
| 2042 | is a dictionary that is initialized in the @code{gdb} module when |
| 2043 | @value{GDBN} starts. What dictionary a filter registers with is an |
| 2044 | important consideration. Generally, if a filter is specific to a set |
| 2045 | of code, it should be registered either in the @code{objfile} or |
| 2046 | @code{progspace} dictionaries as they are specific to the program |
| 2047 | currently loaded in @value{GDBN}. The global dictionary is always |
| 2048 | present in @value{GDBN} and is never unloaded. Any filters registered |
| 2049 | with the global dictionary will exist until @value{GDBN} exits. To |
| 2050 | avoid filters that may conflict, it is generally better to register |
| 2051 | frame filters against the dictionaries that more closely align with |
| 2052 | the usage of the filter currently in question. @xref{Python |
| 2053 | Auto-loading}, for further information on auto-loading Python scripts. |
| 2054 | |
| 2055 | @value{GDBN} takes a hands-off approach to frame filter registration, |
| 2056 | therefore it is the frame filter's responsibility to ensure |
| 2057 | registration has occurred, and that any exceptions are handled |
| 2058 | appropriately. In particular, you may wish to handle exceptions |
| 2059 | relating to Python dictionary key uniqueness. It is mandatory that |
| 2060 | the dictionary key is the same as frame filter's @code{name} |
| 2061 | attribute. When a user manages frame filters (@pxref{Frame Filter |
| 2062 | Management}), the names @value{GDBN} will display are those contained |
| 2063 | in the @code{name} attribute. |
| 2064 | |
| 2065 | The final step of this example is the implementation of the |
| 2066 | @code{filter} method. As shown in the example comments, we define the |
| 2067 | @code{filter} method and note that the method must take an iterator, |
| 2068 | and also must return an iterator. In this bare-bones example, the |
| 2069 | frame filter is not very useful as it just returns the iterator |
| 2070 | untouched. However this is a valid operation for frame filters that |
| 2071 | have the @code{enabled} attribute set, but decide not to operate on |
| 2072 | any frames. |
| 2073 | |
| 2074 | In the next example, the frame filter operates on all frames and |
| 2075 | utilizes a frame decorator to perform some work on the frames. |
| 2076 | @xref{Frame Decorator API}, for further information on the frame |
| 2077 | decorator interface. |
| 2078 | |
| 2079 | This example works on inlined frames. It highlights frames which are |
| 2080 | inlined by tagging them with an ``[inlined]'' tag. By applying a |
| 2081 | frame decorator to all frames with the Python @code{itertools imap} |
| 2082 | method, the example defers actions to the frame decorator. Frame |
| 2083 | decorators are only processed when @value{GDBN} prints the backtrace. |
| 2084 | |
| 2085 | This introduces a new decision making topic: whether to perform |
| 2086 | decision making operations at the filtering step, or at the printing |
| 2087 | step. In this example's approach, it does not perform any filtering |
| 2088 | decisions at the filtering step beyond mapping a frame decorator to |
| 2089 | each frame. This allows the actual decision making to be performed |
| 2090 | when each frame is printed. This is an important consideration, and |
| 2091 | well worth reflecting upon when designing a frame filter. An issue |
| 2092 | that frame filters should avoid is unwinding the stack if possible. |
| 2093 | Some stacks can run very deep, into the tens of thousands in some |
| 2094 | cases. To search every frame to determine if it is inlined ahead of |
| 2095 | time may be too expensive at the filtering step. The frame filter |
| 2096 | cannot know how many frames it has to iterate over, and it would have |
| 2097 | to iterate through them all. This ends up duplicating effort as |
| 2098 | @value{GDBN} performs this iteration when it prints the frames. |
| 2099 | |
| 2100 | In this example decision making can be deferred to the printing step. |
| 2101 | As each frame is printed, the frame decorator can examine each frame |
| 2102 | in turn when @value{GDBN} iterates. From a performance viewpoint, |
| 2103 | this is the most appropriate decision to make as it avoids duplicating |
| 2104 | the effort that the printing step would undertake anyway. Also, if |
| 2105 | there are many frame filters unwinding the stack during filtering, it |
| 2106 | can substantially delay the printing of the backtrace which will |
| 2107 | result in large memory usage, and a poor user experience. |
| 2108 | |
| 2109 | @smallexample |
| 2110 | class InlineFilter(): |
| 2111 | |
| 2112 | def __init__(self): |
| 2113 | self.name = "InlinedFrameFilter" |
| 2114 | self.priority = 100 |
| 2115 | self.enabled = True |
| 2116 | gdb.frame_filters[self.name] = self |
| 2117 | |
| 2118 | def filter(self, frame_iter): |
| 2119 | frame_iter = itertools.imap(InlinedFrameDecorator, |
| 2120 | frame_iter) |
| 2121 | return frame_iter |
| 2122 | @end smallexample |
| 2123 | |
| 2124 | This frame filter is somewhat similar to the earlier example, except |
| 2125 | that the @code{filter} method applies a frame decorator object called |
| 2126 | @code{InlinedFrameDecorator} to each element in the iterator. The |
| 2127 | @code{imap} Python method is light-weight. It does not proactively |
| 2128 | iterate over the iterator, but rather creates a new iterator which |
| 2129 | wraps the existing one. |
| 2130 | |
| 2131 | Below is the frame decorator for this example. |
| 2132 | |
| 2133 | @smallexample |
| 2134 | class InlinedFrameDecorator(FrameDecorator): |
| 2135 | |
| 2136 | def __init__(self, fobj): |
| 2137 | super(InlinedFrameDecorator, self).__init__(fobj) |
| 2138 | |
| 2139 | def function(self): |
| 2140 | frame = fobj.inferior_frame() |
| 2141 | name = str(frame.name()) |
| 2142 | |
| 2143 | if frame.type() == gdb.INLINE_FRAME: |
| 2144 | name = name + " [inlined]" |
| 2145 | |
| 2146 | return name |
| 2147 | @end smallexample |
| 2148 | |
| 2149 | This frame decorator only defines and overrides the @code{function} |
| 2150 | method. It lets the supplied @code{FrameDecorator}, which is shipped |
| 2151 | with @value{GDBN}, perform the other work associated with printing |
| 2152 | this frame. |
| 2153 | |
| 2154 | The combination of these two objects create this output from a |
| 2155 | backtrace: |
| 2156 | |
| 2157 | @smallexample |
| 2158 | #0 0x004004e0 in bar () at inline.c:11 |
| 2159 | #1 0x00400566 in max [inlined] (b=6, a=12) at inline.c:21 |
| 2160 | #2 0x00400566 in main () at inline.c:31 |
| 2161 | @end smallexample |
| 2162 | |
| 2163 | So in the case of this example, a frame decorator is applied to all |
| 2164 | frames, regardless of whether they may be inlined or not. As |
| 2165 | @value{GDBN} iterates over the iterator produced by the frame filters, |
| 2166 | @value{GDBN} executes each frame decorator which then makes a decision |
| 2167 | on what to print in the @code{function} callback. Using a strategy |
| 2168 | like this is a way to defer decisions on the frame content to printing |
| 2169 | time. |
| 2170 | |
| 2171 | @subheading Eliding Frames |
| 2172 | |
| 2173 | It might be that the above example is not desirable for representing |
| 2174 | inlined frames, and a hierarchical approach may be preferred. If we |
| 2175 | want to hierarchically represent frames, the @code{elided} frame |
| 2176 | decorator interface might be preferable. |
| 2177 | |
| 2178 | This example approaches the issue with the @code{elided} method. This |
| 2179 | example is quite long, but very simplistic. It is out-of-scope for |
| 2180 | this section to write a complete example that comprehensively covers |
| 2181 | all approaches of finding and printing inlined frames. However, this |
| 2182 | example illustrates the approach an author might use. |
| 2183 | |
| 2184 | This example comprises of three sections. |
| 2185 | |
| 2186 | @smallexample |
| 2187 | class InlineFrameFilter(): |
| 2188 | |
| 2189 | def __init__(self): |
| 2190 | self.name = "InlinedFrameFilter" |
| 2191 | self.priority = 100 |
| 2192 | self.enabled = True |
| 2193 | gdb.frame_filters[self.name] = self |
| 2194 | |
| 2195 | def filter(self, frame_iter): |
| 2196 | return ElidingInlineIterator(frame_iter) |
| 2197 | @end smallexample |
| 2198 | |
| 2199 | This frame filter is very similar to the other examples. The only |
| 2200 | difference is this frame filter is wrapping the iterator provided to |
| 2201 | it (@code{frame_iter}) with a custom iterator called |
| 2202 | @code{ElidingInlineIterator}. This again defers actions to when |
| 2203 | @value{GDBN} prints the backtrace, as the iterator is not traversed |
| 2204 | until printing. |
| 2205 | |
| 2206 | The iterator for this example is as follows. It is in this section of |
| 2207 | the example where decisions are made on the content of the backtrace. |
| 2208 | |
| 2209 | @smallexample |
| 2210 | class ElidingInlineIterator: |
| 2211 | def __init__(self, ii): |
| 2212 | self.input_iterator = ii |
| 2213 | |
| 2214 | def __iter__(self): |
| 2215 | return self |
| 2216 | |
| 2217 | def next(self): |
| 2218 | frame = next(self.input_iterator) |
| 2219 | |
| 2220 | if frame.inferior_frame().type() != gdb.INLINE_FRAME: |
| 2221 | return frame |
| 2222 | |
| 2223 | try: |
| 2224 | eliding_frame = next(self.input_iterator) |
| 2225 | except StopIteration: |
| 2226 | return frame |
| 2227 | return ElidingFrameDecorator(eliding_frame, [frame]) |
| 2228 | @end smallexample |
| 2229 | |
| 2230 | This iterator implements the Python iterator protocol. When the |
| 2231 | @code{next} function is called (when @value{GDBN} prints each frame), |
| 2232 | the iterator checks if this frame decorator, @code{frame}, is wrapping |
| 2233 | an inlined frame. If it is not, it returns the existing frame decorator |
| 2234 | untouched. If it is wrapping an inlined frame, it assumes that the |
| 2235 | inlined frame was contained within the next oldest frame, |
| 2236 | @code{eliding_frame}, which it fetches. It then creates and returns a |
| 2237 | frame decorator, @code{ElidingFrameDecorator}, which contains both the |
| 2238 | elided frame, and the eliding frame. |
| 2239 | |
| 2240 | @smallexample |
| 2241 | class ElidingInlineDecorator(FrameDecorator): |
| 2242 | |
| 2243 | def __init__(self, frame, elided_frames): |
| 2244 | super(ElidingInlineDecorator, self).__init__(frame) |
| 2245 | self.frame = frame |
| 2246 | self.elided_frames = elided_frames |
| 2247 | |
| 2248 | def elided(self): |
| 2249 | return iter(self.elided_frames) |
| 2250 | @end smallexample |
| 2251 | |
| 2252 | This frame decorator overrides one function and returns the inlined |
| 2253 | frame in the @code{elided} method. As before it lets |
| 2254 | @code{FrameDecorator} do the rest of the work involved in printing |
| 2255 | this frame. This produces the following output. |
| 2256 | |
| 2257 | @smallexample |
| 2258 | #0 0x004004e0 in bar () at inline.c:11 |
| 2259 | #2 0x00400529 in main () at inline.c:25 |
| 2260 | #1 0x00400529 in max (b=6, a=12) at inline.c:15 |
| 2261 | @end smallexample |
| 2262 | |
| 2263 | In that output, @code{max} which has been inlined into @code{main} is |
| 2264 | printed hierarchically. Another approach would be to combine the |
| 2265 | @code{function} method, and the @code{elided} method to both print a |
| 2266 | marker in the inlined frame, and also show the hierarchical |
| 2267 | relationship. |
| 2268 | |
| 2269 | @node Unwinding Frames in Python |
| 2270 | @subsubsection Unwinding Frames in Python |
| 2271 | @cindex unwinding frames in Python |
| 2272 | |
| 2273 | In @value{GDBN} terminology ``unwinding'' is the process of finding |
| 2274 | the previous frame (that is, caller's) from the current one. An |
| 2275 | unwinder has three methods. The first one checks if it can handle |
| 2276 | given frame (``sniff'' it). For the frames it can sniff an unwinder |
| 2277 | provides two additional methods: it can return frame's ID, and it can |
| 2278 | fetch registers from the previous frame. A running @value{GDBN} |
| 2279 | mantains a list of the unwinders and calls each unwinder's sniffer in |
| 2280 | turn until it finds the one that recognizes the current frame. There |
| 2281 | is an API to register an unwinder. |
| 2282 | |
| 2283 | The unwinders that come with @value{GDBN} handle standard frames. |
| 2284 | However, mixed language applications (for example, an application |
| 2285 | running Java Virtual Machine) sometimes use frame layouts that cannot |
| 2286 | be handled by the @value{GDBN} unwinders. You can write Python code |
| 2287 | that can handle such custom frames. |
| 2288 | |
| 2289 | You implement a frame unwinder in Python as a class with which has two |
| 2290 | attributes, @code{name} and @code{enabled}, with obvious meanings, and |
| 2291 | a single method @code{__call__}, which examines a given frame and |
| 2292 | returns an object (an instance of @code{gdb.UnwindInfo class)} |
| 2293 | describing it. If an unwinder does not recognize a frame, it should |
| 2294 | return @code{None}. The code in @value{GDBN} that enables writing |
| 2295 | unwinders in Python uses this object to return frame's ID and previous |
| 2296 | frame registers when @value{GDBN} core asks for them. |
| 2297 | |
| 2298 | An unwinder should do as little work as possible. Some otherwise |
| 2299 | innocuous operations can cause problems (even crashes, as this code is |
| 2300 | not not well-hardened yet). For example, making an inferior call from |
| 2301 | an unwinder is unadvisable, as an inferior call will reset |
| 2302 | @value{GDBN}'s stack unwinding process, potentially causing re-entrant |
| 2303 | unwinding. |
| 2304 | |
| 2305 | @subheading Unwinder Input |
| 2306 | |
| 2307 | An object passed to an unwinder (a @code{gdb.PendingFrame} instance) |
| 2308 | provides a method to read frame's registers: |
| 2309 | |
| 2310 | @defun PendingFrame.read_register (reg) |
| 2311 | This method returns the contents of the register @var{reg} in the |
| 2312 | frame as a @code{gdb.Value} object. @var{reg} can be either a |
| 2313 | register number or a register name; the values are platform-specific. |
| 2314 | They are usually found in the corresponding |
| 2315 | @file{@var{platform}-tdep.h} file in the @value{GDBN} source tree. If |
| 2316 | @var{reg} does not name a register for the current architecture, this |
| 2317 | method will throw an exception. |
| 2318 | |
| 2319 | Note that this method will always return a @code{gdb.Value} for a |
| 2320 | valid register name. This does not mean that the value will be valid. |
| 2321 | For example, you may request a register that an earlier unwinder could |
| 2322 | not unwind---the value will be unavailable. Instead, the |
| 2323 | @code{gdb.Value} returned from this method will be lazy; that is, its |
| 2324 | underlying bits will not be fetched until it is first used. So, |
| 2325 | attempting to use such a value will cause an exception at the point of |
| 2326 | use. |
| 2327 | |
| 2328 | The type of the returned @code{gdb.Value} depends on the register and |
| 2329 | the architecture. It is common for registers to have a scalar type, |
| 2330 | like @code{long long}; but many other types are possible, such as |
| 2331 | pointer, pointer-to-function, floating point or vector types. |
| 2332 | @end defun |
| 2333 | |
| 2334 | It also provides a factory method to create a @code{gdb.UnwindInfo} |
| 2335 | instance to be returned to @value{GDBN}: |
| 2336 | |
| 2337 | @defun PendingFrame.create_unwind_info (frame_id) |
| 2338 | Returns a new @code{gdb.UnwindInfo} instance identified by given |
| 2339 | @var{frame_id}. The argument is used to build @value{GDBN}'s frame ID |
| 2340 | using one of functions provided by @value{GDBN}. @var{frame_id}'s attributes |
| 2341 | determine which function will be used, as follows: |
| 2342 | |
| 2343 | @table @code |
| 2344 | @item sp, pc |
| 2345 | The frame is identified by the given stack address and PC. The stack |
| 2346 | address must be chosen so that it is constant throughout the lifetime |
| 2347 | of the frame, so a typical choice is the value of the stack pointer at |
| 2348 | the start of the function---in the DWARF standard, this would be the |
| 2349 | ``Call Frame Address''. |
| 2350 | |
| 2351 | This is the most common case by far. The other cases are documented |
| 2352 | for completeness but are only useful in specialized situations. |
| 2353 | |
| 2354 | @item sp, pc, special |
| 2355 | The frame is identified by the stack address, the PC, and a |
| 2356 | ``special'' address. The special address is used on architectures |
| 2357 | that can have frames that do not change the stack, but which are still |
| 2358 | distinct, for example the IA-64, which has a second stack for |
| 2359 | registers. Both @var{sp} and @var{special} must be constant |
| 2360 | throughout the lifetime of the frame. |
| 2361 | |
| 2362 | @item sp |
| 2363 | The frame is identified by the stack address only. Any other stack |
| 2364 | frame with a matching @var{sp} will be considered to match this frame. |
| 2365 | Inside gdb, this is called a ``wild frame''. You will never need |
| 2366 | this. |
| 2367 | @end table |
| 2368 | |
| 2369 | Each attribute value should be an instance of @code{gdb.Value}. |
| 2370 | |
| 2371 | @end defun |
| 2372 | |
| 2373 | @subheading Unwinder Output: UnwindInfo |
| 2374 | |
| 2375 | Use @code{PendingFrame.create_unwind_info} method described above to |
| 2376 | create a @code{gdb.UnwindInfo} instance. Use the following method to |
| 2377 | specify caller registers that have been saved in this frame: |
| 2378 | |
| 2379 | @defun gdb.UnwindInfo.add_saved_register (reg, value) |
| 2380 | @var{reg} identifies the register. It can be a number or a name, just |
| 2381 | as for the @code{PendingFrame.read_register} method above. |
| 2382 | @var{value} is a register value (a @code{gdb.Value} object). |
| 2383 | @end defun |
| 2384 | |
| 2385 | @subheading Unwinder Skeleton Code |
| 2386 | |
| 2387 | @value{GDBN} comes with the module containing the base @code{Unwinder} |
| 2388 | class. Derive your unwinder class from it and structure the code as |
| 2389 | follows: |
| 2390 | |
| 2391 | @smallexample |
| 2392 | from gdb.unwinders import Unwinder |
| 2393 | |
| 2394 | class FrameId(object): |
| 2395 | def __init__(self, sp, pc): |
| 2396 | self.sp = sp |
| 2397 | self.pc = pc |
| 2398 | |
| 2399 | |
| 2400 | class MyUnwinder(Unwinder): |
| 2401 | def __init__(....): |
| 2402 | supe(MyUnwinder, self).__init___(<expects unwinder name argument>) |
| 2403 | |
| 2404 | def __call__(pending_frame): |
| 2405 | if not <we recognize frame>: |
| 2406 | return None |
| 2407 | # Create UnwindInfo. Usually the frame is identified by the stack |
| 2408 | # pointer and the program counter. |
| 2409 | sp = pending_frame.read_register(<SP number>) |
| 2410 | pc = pending_frame.read_register(<PC number>) |
| 2411 | unwind_info = pending_frame.create_unwind_info(FrameId(sp, pc)) |
| 2412 | |
| 2413 | # Find the values of the registers in the caller's frame and |
| 2414 | # save them in the result: |
| 2415 | unwind_info.add_saved_register(<register>, <value>) |
| 2416 | .... |
| 2417 | |
| 2418 | # Return the result: |
| 2419 | return unwind_info |
| 2420 | |
| 2421 | @end smallexample |
| 2422 | |
| 2423 | @subheading Registering a Unwinder |
| 2424 | |
| 2425 | An object file, a program space, and the @value{GDBN} proper can have |
| 2426 | unwinders registered with it. |
| 2427 | |
| 2428 | The @code{gdb.unwinders} module provides the function to register a |
| 2429 | unwinder: |
| 2430 | |
| 2431 | @defun gdb.unwinder.register_unwinder (locus, unwinder, replace=False) |
| 2432 | @var{locus} is specifies an object file or a program space to which |
| 2433 | @var{unwinder} is added. Passing @code{None} or @code{gdb} adds |
| 2434 | @var{unwinder} to the @value{GDBN}'s global unwinder list. The newly |
| 2435 | added @var{unwinder} will be called before any other unwinder from the |
| 2436 | same locus. Two unwinders in the same locus cannot have the same |
| 2437 | name. An attempt to add a unwinder with already existing name raises |
| 2438 | an exception unless @var{replace} is @code{True}, in which case the |
| 2439 | old unwinder is deleted. |
| 2440 | @end defun |
| 2441 | |
| 2442 | @subheading Unwinder Precedence |
| 2443 | |
| 2444 | @value{GDBN} first calls the unwinders from all the object files in no |
| 2445 | particular order, then the unwinders from the current program space, |
| 2446 | and finally the unwinders from @value{GDBN}. |
| 2447 | |
| 2448 | @node Xmethods In Python |
| 2449 | @subsubsection Xmethods In Python |
| 2450 | @cindex xmethods in Python |
| 2451 | |
| 2452 | @dfn{Xmethods} are additional methods or replacements for existing |
| 2453 | methods of a C@t{++} class. This feature is useful for those cases |
| 2454 | where a method defined in C@t{++} source code could be inlined or |
| 2455 | optimized out by the compiler, making it unavailable to @value{GDBN}. |
| 2456 | For such cases, one can define an xmethod to serve as a replacement |
| 2457 | for the method defined in the C@t{++} source code. @value{GDBN} will |
| 2458 | then invoke the xmethod, instead of the C@t{++} method, to |
| 2459 | evaluate expressions. One can also use xmethods when debugging |
| 2460 | with core files. Moreover, when debugging live programs, invoking an |
| 2461 | xmethod need not involve running the inferior (which can potentially |
| 2462 | perturb its state). Hence, even if the C@t{++} method is available, it |
| 2463 | is better to use its replacement xmethod if one is defined. |
| 2464 | |
| 2465 | The xmethods feature in Python is available via the concepts of an |
| 2466 | @dfn{xmethod matcher} and an @dfn{xmethod worker}. To |
| 2467 | implement an xmethod, one has to implement a matcher and a |
| 2468 | corresponding worker for it (more than one worker can be |
| 2469 | implemented, each catering to a different overloaded instance of the |
| 2470 | method). Internally, @value{GDBN} invokes the @code{match} method of a |
| 2471 | matcher to match the class type and method name. On a match, the |
| 2472 | @code{match} method returns a list of matching @emph{worker} objects. |
| 2473 | Each worker object typically corresponds to an overloaded instance of |
| 2474 | the xmethod. They implement a @code{get_arg_types} method which |
| 2475 | returns a sequence of types corresponding to the arguments the xmethod |
| 2476 | requires. @value{GDBN} uses this sequence of types to perform |
| 2477 | overload resolution and picks a winning xmethod worker. A winner |
| 2478 | is also selected from among the methods @value{GDBN} finds in the |
| 2479 | C@t{++} source code. Next, the winning xmethod worker and the |
| 2480 | winning C@t{++} method are compared to select an overall winner. In |
| 2481 | case of a tie between a xmethod worker and a C@t{++} method, the |
| 2482 | xmethod worker is selected as the winner. That is, if a winning |
| 2483 | xmethod worker is found to be equivalent to the winning C@t{++} |
| 2484 | method, then the xmethod worker is treated as a replacement for |
| 2485 | the C@t{++} method. @value{GDBN} uses the overall winner to invoke the |
| 2486 | method. If the winning xmethod worker is the overall winner, then |
| 2487 | the corresponding xmethod is invoked via the @code{__call__} method |
| 2488 | of the worker object. |
| 2489 | |
| 2490 | If one wants to implement an xmethod as a replacement for an |
| 2491 | existing C@t{++} method, then they have to implement an equivalent |
| 2492 | xmethod which has exactly the same name and takes arguments of |
| 2493 | exactly the same type as the C@t{++} method. If the user wants to |
| 2494 | invoke the C@t{++} method even though a replacement xmethod is |
| 2495 | available for that method, then they can disable the xmethod. |
| 2496 | |
| 2497 | @xref{Xmethod API}, for API to implement xmethods in Python. |
| 2498 | @xref{Writing an Xmethod}, for implementing xmethods in Python. |
| 2499 | |
| 2500 | @node Xmethod API |
| 2501 | @subsubsection Xmethod API |
| 2502 | @cindex xmethod API |
| 2503 | |
| 2504 | The @value{GDBN} Python API provides classes, interfaces and functions |
| 2505 | to implement, register and manipulate xmethods. |
| 2506 | @xref{Xmethods In Python}. |
| 2507 | |
| 2508 | An xmethod matcher should be an instance of a class derived from |
| 2509 | @code{XMethodMatcher} defined in the module @code{gdb.xmethod}, or an |
| 2510 | object with similar interface and attributes. An instance of |
| 2511 | @code{XMethodMatcher} has the following attributes: |
| 2512 | |
| 2513 | @defvar name |
| 2514 | The name of the matcher. |
| 2515 | @end defvar |
| 2516 | |
| 2517 | @defvar enabled |
| 2518 | A boolean value indicating whether the matcher is enabled or disabled. |
| 2519 | @end defvar |
| 2520 | |
| 2521 | @defvar methods |
| 2522 | A list of named methods managed by the matcher. Each object in the list |
| 2523 | is an instance of the class @code{XMethod} defined in the module |
| 2524 | @code{gdb.xmethod}, or any object with the following attributes: |
| 2525 | |
| 2526 | @table @code |
| 2527 | |
| 2528 | @item name |
| 2529 | Name of the xmethod which should be unique for each xmethod |
| 2530 | managed by the matcher. |
| 2531 | |
| 2532 | @item enabled |
| 2533 | A boolean value indicating whether the xmethod is enabled or |
| 2534 | disabled. |
| 2535 | |
| 2536 | @end table |
| 2537 | |
| 2538 | The class @code{XMethod} is a convenience class with same |
| 2539 | attributes as above along with the following constructor: |
| 2540 | |
| 2541 | @defun XMethod.__init__ (self, name) |
| 2542 | Constructs an enabled xmethod with name @var{name}. |
| 2543 | @end defun |
| 2544 | @end defvar |
| 2545 | |
| 2546 | @noindent |
| 2547 | The @code{XMethodMatcher} class has the following methods: |
| 2548 | |
| 2549 | @defun XMethodMatcher.__init__ (self, name) |
| 2550 | Constructs an enabled xmethod matcher with name @var{name}. The |
| 2551 | @code{methods} attribute is initialized to @code{None}. |
| 2552 | @end defun |
| 2553 | |
| 2554 | @defun XMethodMatcher.match (self, class_type, method_name) |
| 2555 | Derived classes should override this method. It should return a |
| 2556 | xmethod worker object (or a sequence of xmethod worker |
| 2557 | objects) matching the @var{class_type} and @var{method_name}. |
| 2558 | @var{class_type} is a @code{gdb.Type} object, and @var{method_name} |
| 2559 | is a string value. If the matcher manages named methods as listed in |
| 2560 | its @code{methods} attribute, then only those worker objects whose |
| 2561 | corresponding entries in the @code{methods} list are enabled should be |
| 2562 | returned. |
| 2563 | @end defun |
| 2564 | |
| 2565 | An xmethod worker should be an instance of a class derived from |
| 2566 | @code{XMethodWorker} defined in the module @code{gdb.xmethod}, |
| 2567 | or support the following interface: |
| 2568 | |
| 2569 | @defun XMethodWorker.get_arg_types (self) |
| 2570 | This method returns a sequence of @code{gdb.Type} objects corresponding |
| 2571 | to the arguments that the xmethod takes. It can return an empty |
| 2572 | sequence or @code{None} if the xmethod does not take any arguments. |
| 2573 | If the xmethod takes a single argument, then a single |
| 2574 | @code{gdb.Type} object corresponding to it can be returned. |
| 2575 | @end defun |
| 2576 | |
| 2577 | @defun XMethodWorker.get_result_type (self, *args) |
| 2578 | This method returns a @code{gdb.Type} object representing the type |
| 2579 | of the result of invoking this xmethod. |
| 2580 | The @var{args} argument is the same tuple of arguments that would be |
| 2581 | passed to the @code{__call__} method of this worker. |
| 2582 | @end defun |
| 2583 | |
| 2584 | @defun XMethodWorker.__call__ (self, *args) |
| 2585 | This is the method which does the @emph{work} of the xmethod. The |
| 2586 | @var{args} arguments is the tuple of arguments to the xmethod. Each |
| 2587 | element in this tuple is a gdb.Value object. The first element is |
| 2588 | always the @code{this} pointer value. |
| 2589 | @end defun |
| 2590 | |
| 2591 | For @value{GDBN} to lookup xmethods, the xmethod matchers |
| 2592 | should be registered using the following function defined in the module |
| 2593 | @code{gdb.xmethod}: |
| 2594 | |
| 2595 | @defun register_xmethod_matcher (locus, matcher, replace=False) |
| 2596 | The @code{matcher} is registered with @code{locus}, replacing an |
| 2597 | existing matcher with the same name as @code{matcher} if |
| 2598 | @code{replace} is @code{True}. @code{locus} can be a |
| 2599 | @code{gdb.Objfile} object (@pxref{Objfiles In Python}), or a |
| 2600 | @code{gdb.Progspace} object (@pxref{Progspaces In Python}), or |
| 2601 | @code{None}. If it is @code{None}, then @code{matcher} is registered |
| 2602 | globally. |
| 2603 | @end defun |
| 2604 | |
| 2605 | @node Writing an Xmethod |
| 2606 | @subsubsection Writing an Xmethod |
| 2607 | @cindex writing xmethods in Python |
| 2608 | |
| 2609 | Implementing xmethods in Python will require implementing xmethod |
| 2610 | matchers and xmethod workers (@pxref{Xmethods In Python}). Consider |
| 2611 | the following C@t{++} class: |
| 2612 | |
| 2613 | @smallexample |
| 2614 | class MyClass |
| 2615 | @{ |
| 2616 | public: |
| 2617 | MyClass (int a) : a_(a) @{ @} |
| 2618 | |
| 2619 | int geta (void) @{ return a_; @} |
| 2620 | int operator+ (int b); |
| 2621 | |
| 2622 | private: |
| 2623 | int a_; |
| 2624 | @}; |
| 2625 | |
| 2626 | int |
| 2627 | MyClass::operator+ (int b) |
| 2628 | @{ |
| 2629 | return a_ + b; |
| 2630 | @} |
| 2631 | @end smallexample |
| 2632 | |
| 2633 | @noindent |
| 2634 | Let us define two xmethods for the class @code{MyClass}, one |
| 2635 | replacing the method @code{geta}, and another adding an overloaded |
| 2636 | flavor of @code{operator+} which takes a @code{MyClass} argument (the |
| 2637 | C@t{++} code above already has an overloaded @code{operator+} |
| 2638 | which takes an @code{int} argument). The xmethod matcher can be |
| 2639 | defined as follows: |
| 2640 | |
| 2641 | @smallexample |
| 2642 | class MyClass_geta(gdb.xmethod.XMethod): |
| 2643 | def __init__(self): |
| 2644 | gdb.xmethod.XMethod.__init__(self, 'geta') |
| 2645 | |
| 2646 | def get_worker(self, method_name): |
| 2647 | if method_name == 'geta': |
| 2648 | return MyClassWorker_geta() |
| 2649 | |
| 2650 | |
| 2651 | class MyClass_sum(gdb.xmethod.XMethod): |
| 2652 | def __init__(self): |
| 2653 | gdb.xmethod.XMethod.__init__(self, 'sum') |
| 2654 | |
| 2655 | def get_worker(self, method_name): |
| 2656 | if method_name == 'operator+': |
| 2657 | return MyClassWorker_plus() |
| 2658 | |
| 2659 | |
| 2660 | class MyClassMatcher(gdb.xmethod.XMethodMatcher): |
| 2661 | def __init__(self): |
| 2662 | gdb.xmethod.XMethodMatcher.__init__(self, 'MyClassMatcher') |
| 2663 | # List of methods 'managed' by this matcher |
| 2664 | self.methods = [MyClass_geta(), MyClass_sum()] |
| 2665 | |
| 2666 | def match(self, class_type, method_name): |
| 2667 | if class_type.tag != 'MyClass': |
| 2668 | return None |
| 2669 | workers = [] |
| 2670 | for method in self.methods: |
| 2671 | if method.enabled: |
| 2672 | worker = method.get_worker(method_name) |
| 2673 | if worker: |
| 2674 | workers.append(worker) |
| 2675 | |
| 2676 | return workers |
| 2677 | @end smallexample |
| 2678 | |
| 2679 | @noindent |
| 2680 | Notice that the @code{match} method of @code{MyClassMatcher} returns |
| 2681 | a worker object of type @code{MyClassWorker_geta} for the @code{geta} |
| 2682 | method, and a worker object of type @code{MyClassWorker_plus} for the |
| 2683 | @code{operator+} method. This is done indirectly via helper classes |
| 2684 | derived from @code{gdb.xmethod.XMethod}. One does not need to use the |
| 2685 | @code{methods} attribute in a matcher as it is optional. However, if a |
| 2686 | matcher manages more than one xmethod, it is a good practice to list the |
| 2687 | xmethods in the @code{methods} attribute of the matcher. This will then |
| 2688 | facilitate enabling and disabling individual xmethods via the |
| 2689 | @code{enable/disable} commands. Notice also that a worker object is |
| 2690 | returned only if the corresponding entry in the @code{methods} attribute |
| 2691 | of the matcher is enabled. |
| 2692 | |
| 2693 | The implementation of the worker classes returned by the matcher setup |
| 2694 | above is as follows: |
| 2695 | |
| 2696 | @smallexample |
| 2697 | class MyClassWorker_geta(gdb.xmethod.XMethodWorker): |
| 2698 | def get_arg_types(self): |
| 2699 | return None |
| 2700 | |
| 2701 | def get_result_type(self, obj): |
| 2702 | return gdb.lookup_type('int') |
| 2703 | |
| 2704 | def __call__(self, obj): |
| 2705 | return obj['a_'] |
| 2706 | |
| 2707 | |
| 2708 | class MyClassWorker_plus(gdb.xmethod.XMethodWorker): |
| 2709 | def get_arg_types(self): |
| 2710 | return gdb.lookup_type('MyClass') |
| 2711 | |
| 2712 | def get_result_type(self, obj): |
| 2713 | return gdb.lookup_type('int') |
| 2714 | |
| 2715 | def __call__(self, obj, other): |
| 2716 | return obj['a_'] + other['a_'] |
| 2717 | @end smallexample |
| 2718 | |
| 2719 | For @value{GDBN} to actually lookup a xmethod, it has to be |
| 2720 | registered with it. The matcher defined above is registered with |
| 2721 | @value{GDBN} globally as follows: |
| 2722 | |
| 2723 | @smallexample |
| 2724 | gdb.xmethod.register_xmethod_matcher(None, MyClassMatcher()) |
| 2725 | @end smallexample |
| 2726 | |
| 2727 | If an object @code{obj} of type @code{MyClass} is initialized in C@t{++} |
| 2728 | code as follows: |
| 2729 | |
| 2730 | @smallexample |
| 2731 | MyClass obj(5); |
| 2732 | @end smallexample |
| 2733 | |
| 2734 | @noindent |
| 2735 | then, after loading the Python script defining the xmethod matchers |
| 2736 | and workers into @code{GDBN}, invoking the method @code{geta} or using |
| 2737 | the operator @code{+} on @code{obj} will invoke the xmethods |
| 2738 | defined above: |
| 2739 | |
| 2740 | @smallexample |
| 2741 | (gdb) p obj.geta() |
| 2742 | $1 = 5 |
| 2743 | |
| 2744 | (gdb) p obj + obj |
| 2745 | $2 = 10 |
| 2746 | @end smallexample |
| 2747 | |
| 2748 | Consider another example with a C++ template class: |
| 2749 | |
| 2750 | @smallexample |
| 2751 | template <class T> |
| 2752 | class MyTemplate |
| 2753 | @{ |
| 2754 | public: |
| 2755 | MyTemplate () : dsize_(10), data_ (new T [10]) @{ @} |
| 2756 | ~MyTemplate () @{ delete [] data_; @} |
| 2757 | |
| 2758 | int footprint (void) |
| 2759 | @{ |
| 2760 | return sizeof (T) * dsize_ + sizeof (MyTemplate<T>); |
| 2761 | @} |
| 2762 | |
| 2763 | private: |
| 2764 | int dsize_; |
| 2765 | T *data_; |
| 2766 | @}; |
| 2767 | @end smallexample |
| 2768 | |
| 2769 | Let us implement an xmethod for the above class which serves as a |
| 2770 | replacement for the @code{footprint} method. The full code listing |
| 2771 | of the xmethod workers and xmethod matchers is as follows: |
| 2772 | |
| 2773 | @smallexample |
| 2774 | class MyTemplateWorker_footprint(gdb.xmethod.XMethodWorker): |
| 2775 | def __init__(self, class_type): |
| 2776 | self.class_type = class_type |
| 2777 | |
| 2778 | def get_arg_types(self): |
| 2779 | return None |
| 2780 | |
| 2781 | def get_result_type(self): |
| 2782 | return gdb.lookup_type('int') |
| 2783 | |
| 2784 | def __call__(self, obj): |
| 2785 | return (self.class_type.sizeof + |
| 2786 | obj['dsize_'] * |
| 2787 | self.class_type.template_argument(0).sizeof) |
| 2788 | |
| 2789 | |
| 2790 | class MyTemplateMatcher_footprint(gdb.xmethod.XMethodMatcher): |
| 2791 | def __init__(self): |
| 2792 | gdb.xmethod.XMethodMatcher.__init__(self, 'MyTemplateMatcher') |
| 2793 | |
| 2794 | def match(self, class_type, method_name): |
| 2795 | if (re.match('MyTemplate<[ \t\n]*[_a-zA-Z][ _a-zA-Z0-9]*>', |
| 2796 | class_type.tag) and |
| 2797 | method_name == 'footprint'): |
| 2798 | return MyTemplateWorker_footprint(class_type) |
| 2799 | @end smallexample |
| 2800 | |
| 2801 | Notice that, in this example, we have not used the @code{methods} |
| 2802 | attribute of the matcher as the matcher manages only one xmethod. The |
| 2803 | user can enable/disable this xmethod by enabling/disabling the matcher |
| 2804 | itself. |
| 2805 | |
| 2806 | @node Inferiors In Python |
| 2807 | @subsubsection Inferiors In Python |
| 2808 | @cindex inferiors in Python |
| 2809 | |
| 2810 | @findex gdb.Inferior |
| 2811 | Programs which are being run under @value{GDBN} are called inferiors |
| 2812 | (@pxref{Inferiors and Programs}). Python scripts can access |
| 2813 | information about and manipulate inferiors controlled by @value{GDBN} |
| 2814 | via objects of the @code{gdb.Inferior} class. |
| 2815 | |
| 2816 | The following inferior-related functions are available in the @code{gdb} |
| 2817 | module: |
| 2818 | |
| 2819 | @defun gdb.inferiors () |
| 2820 | Return a tuple containing all inferior objects. |
| 2821 | @end defun |
| 2822 | |
| 2823 | @defun gdb.selected_inferior () |
| 2824 | Return an object representing the current inferior. |
| 2825 | @end defun |
| 2826 | |
| 2827 | A @code{gdb.Inferior} object has the following attributes: |
| 2828 | |
| 2829 | @defvar Inferior.num |
| 2830 | ID of inferior, as assigned by GDB. |
| 2831 | @end defvar |
| 2832 | |
| 2833 | @defvar Inferior.pid |
| 2834 | Process ID of the inferior, as assigned by the underlying operating |
| 2835 | system. |
| 2836 | @end defvar |
| 2837 | |
| 2838 | @defvar Inferior.was_attached |
| 2839 | Boolean signaling whether the inferior was created using `attach', or |
| 2840 | started by @value{GDBN} itself. |
| 2841 | @end defvar |
| 2842 | |
| 2843 | @defvar Inferior.progspace |
| 2844 | The inferior's program space. @xref{Progspaces In Python}. |
| 2845 | @end defvar |
| 2846 | |
| 2847 | A @code{gdb.Inferior} object has the following methods: |
| 2848 | |
| 2849 | @defun Inferior.is_valid () |
| 2850 | Returns @code{True} if the @code{gdb.Inferior} object is valid, |
| 2851 | @code{False} if not. A @code{gdb.Inferior} object will become invalid |
| 2852 | if the inferior no longer exists within @value{GDBN}. All other |
| 2853 | @code{gdb.Inferior} methods will throw an exception if it is invalid |
| 2854 | at the time the method is called. |
| 2855 | @end defun |
| 2856 | |
| 2857 | @defun Inferior.threads () |
| 2858 | This method returns a tuple holding all the threads which are valid |
| 2859 | when it is called. If there are no valid threads, the method will |
| 2860 | return an empty tuple. |
| 2861 | @end defun |
| 2862 | |
| 2863 | @findex Inferior.read_memory |
| 2864 | @defun Inferior.read_memory (address, length) |
| 2865 | Read @var{length} addressable memory units from the inferior, starting at |
| 2866 | @var{address}. Returns a buffer object, which behaves much like an array |
| 2867 | or a string. It can be modified and given to the |
| 2868 | @code{Inferior.write_memory} function. In Python 3, the return |
| 2869 | value is a @code{memoryview} object. |
| 2870 | @end defun |
| 2871 | |
| 2872 | @findex Inferior.write_memory |
| 2873 | @defun Inferior.write_memory (address, buffer @r{[}, length@r{]}) |
| 2874 | Write the contents of @var{buffer} to the inferior, starting at |
| 2875 | @var{address}. The @var{buffer} parameter must be a Python object |
| 2876 | which supports the buffer protocol, i.e., a string, an array or the |
| 2877 | object returned from @code{Inferior.read_memory}. If given, @var{length} |
| 2878 | determines the number of addressable memory units from @var{buffer} to be |
| 2879 | written. |
| 2880 | @end defun |
| 2881 | |
| 2882 | @findex gdb.search_memory |
| 2883 | @defun Inferior.search_memory (address, length, pattern) |
| 2884 | Search a region of the inferior memory starting at @var{address} with |
| 2885 | the given @var{length} using the search pattern supplied in |
| 2886 | @var{pattern}. The @var{pattern} parameter must be a Python object |
| 2887 | which supports the buffer protocol, i.e., a string, an array or the |
| 2888 | object returned from @code{gdb.read_memory}. Returns a Python @code{Long} |
| 2889 | containing the address where the pattern was found, or @code{None} if |
| 2890 | the pattern could not be found. |
| 2891 | @end defun |
| 2892 | |
| 2893 | @findex Inferior.thread_from_thread_handle |
| 2894 | @defun Inferior.thread_from_thread_handle (thread_handle) |
| 2895 | Return the thread object corresponding to @var{thread_handle}, a thread |
| 2896 | library specific data structure such as @code{pthread_t} for pthreads |
| 2897 | library implementations. |
| 2898 | @end defun |
| 2899 | |
| 2900 | @node Events In Python |
| 2901 | @subsubsection Events In Python |
| 2902 | @cindex inferior events in Python |
| 2903 | |
| 2904 | @value{GDBN} provides a general event facility so that Python code can be |
| 2905 | notified of various state changes, particularly changes that occur in |
| 2906 | the inferior. |
| 2907 | |
| 2908 | An @dfn{event} is just an object that describes some state change. The |
| 2909 | type of the object and its attributes will vary depending on the details |
| 2910 | of the change. All the existing events are described below. |
| 2911 | |
| 2912 | In order to be notified of an event, you must register an event handler |
| 2913 | with an @dfn{event registry}. An event registry is an object in the |
| 2914 | @code{gdb.events} module which dispatches particular events. A registry |
| 2915 | provides methods to register and unregister event handlers: |
| 2916 | |
| 2917 | @defun EventRegistry.connect (object) |
| 2918 | Add the given callable @var{object} to the registry. This object will be |
| 2919 | called when an event corresponding to this registry occurs. |
| 2920 | @end defun |
| 2921 | |
| 2922 | @defun EventRegistry.disconnect (object) |
| 2923 | Remove the given @var{object} from the registry. Once removed, the object |
| 2924 | will no longer receive notifications of events. |
| 2925 | @end defun |
| 2926 | |
| 2927 | Here is an example: |
| 2928 | |
| 2929 | @smallexample |
| 2930 | def exit_handler (event): |
| 2931 | print "event type: exit" |
| 2932 | print "exit code: %d" % (event.exit_code) |
| 2933 | |
| 2934 | gdb.events.exited.connect (exit_handler) |
| 2935 | @end smallexample |
| 2936 | |
| 2937 | In the above example we connect our handler @code{exit_handler} to the |
| 2938 | registry @code{events.exited}. Once connected, @code{exit_handler} gets |
| 2939 | called when the inferior exits. The argument @dfn{event} in this example is |
| 2940 | of type @code{gdb.ExitedEvent}. As you can see in the example the |
| 2941 | @code{ExitedEvent} object has an attribute which indicates the exit code of |
| 2942 | the inferior. |
| 2943 | |
| 2944 | The following is a listing of the event registries that are available and |
| 2945 | details of the events they emit: |
| 2946 | |
| 2947 | @table @code |
| 2948 | |
| 2949 | @item events.cont |
| 2950 | Emits @code{gdb.ThreadEvent}. |
| 2951 | |
| 2952 | Some events can be thread specific when @value{GDBN} is running in non-stop |
| 2953 | mode. When represented in Python, these events all extend |
| 2954 | @code{gdb.ThreadEvent}. Note, this event is not emitted directly; instead, |
| 2955 | events which are emitted by this or other modules might extend this event. |
| 2956 | Examples of these events are @code{gdb.BreakpointEvent} and |
| 2957 | @code{gdb.ContinueEvent}. |
| 2958 | |
| 2959 | @defvar ThreadEvent.inferior_thread |
| 2960 | In non-stop mode this attribute will be set to the specific thread which was |
| 2961 | involved in the emitted event. Otherwise, it will be set to @code{None}. |
| 2962 | @end defvar |
| 2963 | |
| 2964 | Emits @code{gdb.ContinueEvent} which extends @code{gdb.ThreadEvent}. |
| 2965 | |
| 2966 | This event indicates that the inferior has been continued after a stop. For |
| 2967 | inherited attribute refer to @code{gdb.ThreadEvent} above. |
| 2968 | |
| 2969 | @item events.exited |
| 2970 | Emits @code{events.ExitedEvent} which indicates that the inferior has exited. |
| 2971 | @code{events.ExitedEvent} has two attributes: |
| 2972 | @defvar ExitedEvent.exit_code |
| 2973 | An integer representing the exit code, if available, which the inferior |
| 2974 | has returned. (The exit code could be unavailable if, for example, |
| 2975 | @value{GDBN} detaches from the inferior.) If the exit code is unavailable, |
| 2976 | the attribute does not exist. |
| 2977 | @end defvar |
| 2978 | @defvar ExitedEvent.inferior |
| 2979 | A reference to the inferior which triggered the @code{exited} event. |
| 2980 | @end defvar |
| 2981 | |
| 2982 | @item events.stop |
| 2983 | Emits @code{gdb.StopEvent} which extends @code{gdb.ThreadEvent}. |
| 2984 | |
| 2985 | Indicates that the inferior has stopped. All events emitted by this registry |
| 2986 | extend StopEvent. As a child of @code{gdb.ThreadEvent}, @code{gdb.StopEvent} |
| 2987 | will indicate the stopped thread when @value{GDBN} is running in non-stop |
| 2988 | mode. Refer to @code{gdb.ThreadEvent} above for more details. |
| 2989 | |
| 2990 | Emits @code{gdb.SignalEvent} which extends @code{gdb.StopEvent}. |
| 2991 | |
| 2992 | This event indicates that the inferior or one of its threads has received as |
| 2993 | signal. @code{gdb.SignalEvent} has the following attributes: |
| 2994 | |
| 2995 | @defvar SignalEvent.stop_signal |
| 2996 | A string representing the signal received by the inferior. A list of possible |
| 2997 | signal values can be obtained by running the command @code{info signals} in |
| 2998 | the @value{GDBN} command prompt. |
| 2999 | @end defvar |
| 3000 | |
| 3001 | Also emits @code{gdb.BreakpointEvent} which extends @code{gdb.StopEvent}. |
| 3002 | |
| 3003 | @code{gdb.BreakpointEvent} event indicates that one or more breakpoints have |
| 3004 | been hit, and has the following attributes: |
| 3005 | |
| 3006 | @defvar BreakpointEvent.breakpoints |
| 3007 | A sequence containing references to all the breakpoints (type |
| 3008 | @code{gdb.Breakpoint}) that were hit. |
| 3009 | @xref{Breakpoints In Python}, for details of the @code{gdb.Breakpoint} object. |
| 3010 | @end defvar |
| 3011 | @defvar BreakpointEvent.breakpoint |
| 3012 | A reference to the first breakpoint that was hit. |
| 3013 | This function is maintained for backward compatibility and is now deprecated |
| 3014 | in favor of the @code{gdb.BreakpointEvent.breakpoints} attribute. |
| 3015 | @end defvar |
| 3016 | |
| 3017 | @item events.new_objfile |
| 3018 | Emits @code{gdb.NewObjFileEvent} which indicates that a new object file has |
| 3019 | been loaded by @value{GDBN}. @code{gdb.NewObjFileEvent} has one attribute: |
| 3020 | |
| 3021 | @defvar NewObjFileEvent.new_objfile |
| 3022 | A reference to the object file (@code{gdb.Objfile}) which has been loaded. |
| 3023 | @xref{Objfiles In Python}, for details of the @code{gdb.Objfile} object. |
| 3024 | @end defvar |
| 3025 | |
| 3026 | @item events.clear_objfiles |
| 3027 | Emits @code{gdb.ClearObjFilesEvent} which indicates that the list of object |
| 3028 | files for a program space has been reset. |
| 3029 | @code{gdb.ClearObjFilesEvent} has one attribute: |
| 3030 | |
| 3031 | @defvar ClearObjFilesEvent.progspace |
| 3032 | A reference to the program space (@code{gdb.Progspace}) whose objfile list has |
| 3033 | been cleared. @xref{Progspaces In Python}. |
| 3034 | @end defvar |
| 3035 | |
| 3036 | @item events.inferior_call |
| 3037 | Emits events just before and after a function in the inferior is |
| 3038 | called by @value{GDBN}. Before an inferior call, this emits an event |
| 3039 | of type @code{gdb.InferiorCallPreEvent}, and after an inferior call, |
| 3040 | this emits an event of type @code{gdb.InferiorCallPostEvent}. |
| 3041 | |
| 3042 | @table @code |
| 3043 | @tindex gdb.InferiorCallPreEvent |
| 3044 | @item @code{gdb.InferiorCallPreEvent} |
| 3045 | Indicates that a function in the inferior is about to be called. |
| 3046 | |
| 3047 | @defvar InferiorCallPreEvent.ptid |
| 3048 | The thread in which the call will be run. |
| 3049 | @end defvar |
| 3050 | |
| 3051 | @defvar InferiorCallPreEvent.address |
| 3052 | The location of the function to be called. |
| 3053 | @end defvar |
| 3054 | |
| 3055 | @tindex gdb.InferiorCallPostEvent |
| 3056 | @item @code{gdb.InferiorCallPostEvent} |
| 3057 | Indicates that a function in the inferior has just been called. |
| 3058 | |
| 3059 | @defvar InferiorCallPostEvent.ptid |
| 3060 | The thread in which the call was run. |
| 3061 | @end defvar |
| 3062 | |
| 3063 | @defvar InferiorCallPostEvent.address |
| 3064 | The location of the function that was called. |
| 3065 | @end defvar |
| 3066 | @end table |
| 3067 | |
| 3068 | @item events.memory_changed |
| 3069 | Emits @code{gdb.MemoryChangedEvent} which indicates that the memory of the |
| 3070 | inferior has been modified by the @value{GDBN} user, for instance via a |
| 3071 | command like @w{@code{set *addr = value}}. The event has the following |
| 3072 | attributes: |
| 3073 | |
| 3074 | @defvar MemoryChangedEvent.address |
| 3075 | The start address of the changed region. |
| 3076 | @end defvar |
| 3077 | |
| 3078 | @defvar MemoryChangedEvent.length |
| 3079 | Length in bytes of the changed region. |
| 3080 | @end defvar |
| 3081 | |
| 3082 | @item events.register_changed |
| 3083 | Emits @code{gdb.RegisterChangedEvent} which indicates that a register in the |
| 3084 | inferior has been modified by the @value{GDBN} user. |
| 3085 | |
| 3086 | @defvar RegisterChangedEvent.frame |
| 3087 | A gdb.Frame object representing the frame in which the register was modified. |
| 3088 | @end defvar |
| 3089 | @defvar RegisterChangedEvent.regnum |
| 3090 | Denotes which register was modified. |
| 3091 | @end defvar |
| 3092 | |
| 3093 | @item events.breakpoint_created |
| 3094 | This is emitted when a new breakpoint has been created. The argument |
| 3095 | that is passed is the new @code{gdb.Breakpoint} object. |
| 3096 | |
| 3097 | @item events.breakpoint_modified |
| 3098 | This is emitted when a breakpoint has been modified in some way. The |
| 3099 | argument that is passed is the new @code{gdb.Breakpoint} object. |
| 3100 | |
| 3101 | @item events.breakpoint_deleted |
| 3102 | This is emitted when a breakpoint has been deleted. The argument that |
| 3103 | is passed is the @code{gdb.Breakpoint} object. When this event is |
| 3104 | emitted, the @code{gdb.Breakpoint} object will already be in its |
| 3105 | invalid state; that is, the @code{is_valid} method will return |
| 3106 | @code{False}. |
| 3107 | |
| 3108 | @item events.before_prompt |
| 3109 | This event carries no payload. It is emitted each time @value{GDBN} |
| 3110 | presents a prompt to the user. |
| 3111 | |
| 3112 | @item events.new_inferior |
| 3113 | This is emitted when a new inferior is created. Note that the |
| 3114 | inferior is not necessarily running; in fact, it may not even have an |
| 3115 | associated executable. |
| 3116 | |
| 3117 | The event is of type @code{gdb.NewInferiorEvent}. This has a single |
| 3118 | attribute: |
| 3119 | |
| 3120 | @defvar NewInferiorEvent.inferior |
| 3121 | The new inferior, a @code{gdb.Inferior} object. |
| 3122 | @end defvar |
| 3123 | |
| 3124 | @item events.inferior_deleted |
| 3125 | This is emitted when an inferior has been deleted. Note that this is |
| 3126 | not the same as process exit; it is notified when the inferior itself |
| 3127 | is removed, say via @code{remove-inferiors}. |
| 3128 | |
| 3129 | The event is of type @code{gdb.InferiorDeletedEvent}. This has a single |
| 3130 | attribute: |
| 3131 | |
| 3132 | @defvar NewInferiorEvent.inferior |
| 3133 | The inferior that is being removed, a @code{gdb.Inferior} object. |
| 3134 | @end defvar |
| 3135 | |
| 3136 | @item events.new_thread |
| 3137 | This is emitted when @value{GDBN} notices a new thread. The event is of |
| 3138 | type @code{gdb.NewThreadEvent}, which extends @code{gdb.ThreadEvent}. |
| 3139 | This has a single attribute: |
| 3140 | |
| 3141 | @defvar NewThreadEvent.inferior_thread |
| 3142 | The new thread. |
| 3143 | @end defvar |
| 3144 | |
| 3145 | @end table |
| 3146 | |
| 3147 | @node Threads In Python |
| 3148 | @subsubsection Threads In Python |
| 3149 | @cindex threads in python |
| 3150 | |
| 3151 | @findex gdb.InferiorThread |
| 3152 | Python scripts can access information about, and manipulate inferior threads |
| 3153 | controlled by @value{GDBN}, via objects of the @code{gdb.InferiorThread} class. |
| 3154 | |
| 3155 | The following thread-related functions are available in the @code{gdb} |
| 3156 | module: |
| 3157 | |
| 3158 | @findex gdb.selected_thread |
| 3159 | @defun gdb.selected_thread () |
| 3160 | This function returns the thread object for the selected thread. If there |
| 3161 | is no selected thread, this will return @code{None}. |
| 3162 | @end defun |
| 3163 | |
| 3164 | A @code{gdb.InferiorThread} object has the following attributes: |
| 3165 | |
| 3166 | @defvar InferiorThread.name |
| 3167 | The name of the thread. If the user specified a name using |
| 3168 | @code{thread name}, then this returns that name. Otherwise, if an |
| 3169 | OS-supplied name is available, then it is returned. Otherwise, this |
| 3170 | returns @code{None}. |
| 3171 | |
| 3172 | This attribute can be assigned to. The new value must be a string |
| 3173 | object, which sets the new name, or @code{None}, which removes any |
| 3174 | user-specified thread name. |
| 3175 | @end defvar |
| 3176 | |
| 3177 | @defvar InferiorThread.num |
| 3178 | The per-inferior number of the thread, as assigned by GDB. |
| 3179 | @end defvar |
| 3180 | |
| 3181 | @defvar InferiorThread.global_num |
| 3182 | The global ID of the thread, as assigned by GDB. You can use this to |
| 3183 | make Python breakpoints thread-specific, for example |
| 3184 | (@pxref{python_breakpoint_thread,,The Breakpoint.thread attribute}). |
| 3185 | @end defvar |
| 3186 | |
| 3187 | @defvar InferiorThread.ptid |
| 3188 | ID of the thread, as assigned by the operating system. This attribute is a |
| 3189 | tuple containing three integers. The first is the Process ID (PID); the second |
| 3190 | is the Lightweight Process ID (LWPID), and the third is the Thread ID (TID). |
| 3191 | Either the LWPID or TID may be 0, which indicates that the operating system |
| 3192 | does not use that identifier. |
| 3193 | @end defvar |
| 3194 | |
| 3195 | @defvar InferiorThread.inferior |
| 3196 | The inferior this thread belongs to. This attribute is represented as |
| 3197 | a @code{gdb.Inferior} object. This attribute is not writable. |
| 3198 | @end defvar |
| 3199 | |
| 3200 | A @code{gdb.InferiorThread} object has the following methods: |
| 3201 | |
| 3202 | @defun InferiorThread.is_valid () |
| 3203 | Returns @code{True} if the @code{gdb.InferiorThread} object is valid, |
| 3204 | @code{False} if not. A @code{gdb.InferiorThread} object will become |
| 3205 | invalid if the thread exits, or the inferior that the thread belongs |
| 3206 | is deleted. All other @code{gdb.InferiorThread} methods will throw an |
| 3207 | exception if it is invalid at the time the method is called. |
| 3208 | @end defun |
| 3209 | |
| 3210 | @defun InferiorThread.switch () |
| 3211 | This changes @value{GDBN}'s currently selected thread to the one represented |
| 3212 | by this object. |
| 3213 | @end defun |
| 3214 | |
| 3215 | @defun InferiorThread.is_stopped () |
| 3216 | Return a Boolean indicating whether the thread is stopped. |
| 3217 | @end defun |
| 3218 | |
| 3219 | @defun InferiorThread.is_running () |
| 3220 | Return a Boolean indicating whether the thread is running. |
| 3221 | @end defun |
| 3222 | |
| 3223 | @defun InferiorThread.is_exited () |
| 3224 | Return a Boolean indicating whether the thread is exited. |
| 3225 | @end defun |
| 3226 | |
| 3227 | @node Recordings In Python |
| 3228 | @subsubsection Recordings In Python |
| 3229 | @cindex recordings in python |
| 3230 | |
| 3231 | The following recordings-related functions |
| 3232 | (@pxref{Process Record and Replay}) are available in the @code{gdb} |
| 3233 | module: |
| 3234 | |
| 3235 | @defun gdb.start_recording (@r{[}method@r{]}, @r{[}format@r{]}) |
| 3236 | Start a recording using the given @var{method} and @var{format}. If |
| 3237 | no @var{format} is given, the default format for the recording method |
| 3238 | is used. If no @var{method} is given, the default method will be used. |
| 3239 | Returns a @code{gdb.Record} object on success. Throw an exception on |
| 3240 | failure. |
| 3241 | |
| 3242 | The following strings can be passed as @var{method}: |
| 3243 | |
| 3244 | @itemize @bullet |
| 3245 | @item |
| 3246 | @code{"full"} |
| 3247 | @item |
| 3248 | @code{"btrace"}: Possible values for @var{format}: @code{"pt"}, |
| 3249 | @code{"bts"} or leave out for default format. |
| 3250 | @end itemize |
| 3251 | @end defun |
| 3252 | |
| 3253 | @defun gdb.current_recording () |
| 3254 | Access a currently running recording. Return a @code{gdb.Record} |
| 3255 | object on success. Return @code{None} if no recording is currently |
| 3256 | active. |
| 3257 | @end defun |
| 3258 | |
| 3259 | @defun gdb.stop_recording () |
| 3260 | Stop the current recording. Throw an exception if no recording is |
| 3261 | currently active. All record objects become invalid after this call. |
| 3262 | @end defun |
| 3263 | |
| 3264 | A @code{gdb.Record} object has the following attributes: |
| 3265 | |
| 3266 | @defvar Record.method |
| 3267 | A string with the current recording method, e.g.@: @code{full} or |
| 3268 | @code{btrace}. |
| 3269 | @end defvar |
| 3270 | |
| 3271 | @defvar Record.format |
| 3272 | A string with the current recording format, e.g.@: @code{bt}, @code{pts} or |
| 3273 | @code{None}. |
| 3274 | @end defvar |
| 3275 | |
| 3276 | @defvar Record.begin |
| 3277 | A method specific instruction object representing the first instruction |
| 3278 | in this recording. |
| 3279 | @end defvar |
| 3280 | |
| 3281 | @defvar Record.end |
| 3282 | A method specific instruction object representing the current |
| 3283 | instruction, that is not actually part of the recording. |
| 3284 | @end defvar |
| 3285 | |
| 3286 | @defvar Record.replay_position |
| 3287 | The instruction representing the current replay position. If there is |
| 3288 | no replay active, this will be @code{None}. |
| 3289 | @end defvar |
| 3290 | |
| 3291 | @defvar Record.instruction_history |
| 3292 | A list with all recorded instructions. |
| 3293 | @end defvar |
| 3294 | |
| 3295 | @defvar Record.function_call_history |
| 3296 | A list with all recorded function call segments. |
| 3297 | @end defvar |
| 3298 | |
| 3299 | A @code{gdb.Record} object has the following methods: |
| 3300 | |
| 3301 | @defun Record.goto (instruction) |
| 3302 | Move the replay position to the given @var{instruction}. |
| 3303 | @end defun |
| 3304 | |
| 3305 | The common @code{gdb.Instruction} class that recording method specific |
| 3306 | instruction objects inherit from, has the following attributes: |
| 3307 | |
| 3308 | @defvar Instruction.pc |
| 3309 | An integer representing this instruction's address. |
| 3310 | @end defvar |
| 3311 | |
| 3312 | @defvar Instruction.data |
| 3313 | A buffer with the raw instruction data. In Python 3, the return value is a |
| 3314 | @code{memoryview} object. |
| 3315 | @end defvar |
| 3316 | |
| 3317 | @defvar Instruction.decoded |
| 3318 | A human readable string with the disassembled instruction. |
| 3319 | @end defvar |
| 3320 | |
| 3321 | @defvar Instruction.size |
| 3322 | The size of the instruction in bytes. |
| 3323 | @end defvar |
| 3324 | |
| 3325 | Additionally @code{gdb.RecordInstruction} has the following attributes: |
| 3326 | |
| 3327 | @defvar RecordInstruction.number |
| 3328 | An integer identifying this instruction. @code{number} corresponds to |
| 3329 | the numbers seen in @code{record instruction-history} |
| 3330 | (@pxref{Process Record and Replay}). |
| 3331 | @end defvar |
| 3332 | |
| 3333 | @defvar RecordInstruction.sal |
| 3334 | A @code{gdb.Symtab_and_line} object representing the associated symtab |
| 3335 | and line of this instruction. May be @code{None} if no debug information is |
| 3336 | available. |
| 3337 | @end defvar |
| 3338 | |
| 3339 | @defvar RecordInstruction.is_speculative |
| 3340 | A boolean indicating whether the instruction was executed speculatively. |
| 3341 | @end defvar |
| 3342 | |
| 3343 | If an error occured during recording or decoding a recording, this error is |
| 3344 | represented by a @code{gdb.RecordGap} object in the instruction list. It has |
| 3345 | the following attributes: |
| 3346 | |
| 3347 | @defvar RecordGap.number |
| 3348 | An integer identifying this gap. @code{number} corresponds to the numbers seen |
| 3349 | in @code{record instruction-history} (@pxref{Process Record and Replay}). |
| 3350 | @end defvar |
| 3351 | |
| 3352 | @defvar RecordGap.error_code |
| 3353 | A numerical representation of the reason for the gap. The value is specific to |
| 3354 | the current recording method. |
| 3355 | @end defvar |
| 3356 | |
| 3357 | @defvar RecordGap.error_string |
| 3358 | A human readable string with the reason for the gap. |
| 3359 | @end defvar |
| 3360 | |
| 3361 | A @code{gdb.RecordFunctionSegment} object has the following attributes: |
| 3362 | |
| 3363 | @defvar RecordFunctionSegment.number |
| 3364 | An integer identifying this function segment. @code{number} corresponds to |
| 3365 | the numbers seen in @code{record function-call-history} |
| 3366 | (@pxref{Process Record and Replay}). |
| 3367 | @end defvar |
| 3368 | |
| 3369 | @defvar RecordFunctionSegment.symbol |
| 3370 | A @code{gdb.Symbol} object representing the associated symbol. May be |
| 3371 | @code{None} if no debug information is available. |
| 3372 | @end defvar |
| 3373 | |
| 3374 | @defvar RecordFunctionSegment.level |
| 3375 | An integer representing the function call's stack level. May be |
| 3376 | @code{None} if the function call is a gap. |
| 3377 | @end defvar |
| 3378 | |
| 3379 | @defvar RecordFunctionSegment.instructions |
| 3380 | A list of @code{gdb.RecordInstruction} or @code{gdb.RecordGap} objects |
| 3381 | associated with this function call. |
| 3382 | @end defvar |
| 3383 | |
| 3384 | @defvar RecordFunctionSegment.up |
| 3385 | A @code{gdb.RecordFunctionSegment} object representing the caller's |
| 3386 | function segment. If the call has not been recorded, this will be the |
| 3387 | function segment to which control returns. If neither the call nor the |
| 3388 | return have been recorded, this will be @code{None}. |
| 3389 | @end defvar |
| 3390 | |
| 3391 | @defvar RecordFunctionSegment.prev |
| 3392 | A @code{gdb.RecordFunctionSegment} object representing the previous |
| 3393 | segment of this function call. May be @code{None}. |
| 3394 | @end defvar |
| 3395 | |
| 3396 | @defvar RecordFunctionSegment.next |
| 3397 | A @code{gdb.RecordFunctionSegment} object representing the next segment of |
| 3398 | this function call. May be @code{None}. |
| 3399 | @end defvar |
| 3400 | |
| 3401 | The following example demonstrates the usage of these objects and |
| 3402 | functions to create a function that will rewind a record to the last |
| 3403 | time a function in a different file was executed. This would typically |
| 3404 | be used to track the execution of user provided callback functions in a |
| 3405 | library which typically are not visible in a back trace. |
| 3406 | |
| 3407 | @smallexample |
| 3408 | def bringback (): |
| 3409 | rec = gdb.current_recording () |
| 3410 | if not rec: |
| 3411 | return |
| 3412 | |
| 3413 | insn = rec.instruction_history |
| 3414 | if len (insn) == 0: |
| 3415 | return |
| 3416 | |
| 3417 | try: |
| 3418 | position = insn.index (rec.replay_position) |
| 3419 | except: |
| 3420 | position = -1 |
| 3421 | try: |
| 3422 | filename = insn[position].sal.symtab.fullname () |
| 3423 | except: |
| 3424 | filename = None |
| 3425 | |
| 3426 | for i in reversed (insn[:position]): |
| 3427 | try: |
| 3428 | current = i.sal.symtab.fullname () |
| 3429 | except: |
| 3430 | current = None |
| 3431 | |
| 3432 | if filename == current: |
| 3433 | continue |
| 3434 | |
| 3435 | rec.goto (i) |
| 3436 | return |
| 3437 | @end smallexample |
| 3438 | |
| 3439 | Another possible application is to write a function that counts the |
| 3440 | number of code executions in a given line range. This line range can |
| 3441 | contain parts of functions or span across several functions and is not |
| 3442 | limited to be contiguous. |
| 3443 | |
| 3444 | @smallexample |
| 3445 | def countrange (filename, linerange): |
| 3446 | count = 0 |
| 3447 | |
| 3448 | def filter_only (file_name): |
| 3449 | for call in gdb.current_recording ().function_call_history: |
| 3450 | try: |
| 3451 | if file_name in call.symbol.symtab.fullname (): |
| 3452 | yield call |
| 3453 | except: |
| 3454 | pass |
| 3455 | |
| 3456 | for c in filter_only (filename): |
| 3457 | for i in c.instructions: |
| 3458 | try: |
| 3459 | if i.sal.line in linerange: |
| 3460 | count += 1 |
| 3461 | break; |
| 3462 | except: |
| 3463 | pass |
| 3464 | |
| 3465 | return count |
| 3466 | @end smallexample |
| 3467 | |
| 3468 | @node Commands In Python |
| 3469 | @subsubsection Commands In Python |
| 3470 | |
| 3471 | @cindex commands in python |
| 3472 | @cindex python commands |
| 3473 | You can implement new @value{GDBN} CLI commands in Python. A CLI |
| 3474 | command is implemented using an instance of the @code{gdb.Command} |
| 3475 | class, most commonly using a subclass. |
| 3476 | |
| 3477 | @defun Command.__init__ (name, @var{command_class} @r{[}, @var{completer_class} @r{[}, @var{prefix}@r{]]}) |
| 3478 | The object initializer for @code{Command} registers the new command |
| 3479 | with @value{GDBN}. This initializer is normally invoked from the |
| 3480 | subclass' own @code{__init__} method. |
| 3481 | |
| 3482 | @var{name} is the name of the command. If @var{name} consists of |
| 3483 | multiple words, then the initial words are looked for as prefix |
| 3484 | commands. In this case, if one of the prefix commands does not exist, |
| 3485 | an exception is raised. |
| 3486 | |
| 3487 | There is no support for multi-line commands. |
| 3488 | |
| 3489 | @var{command_class} should be one of the @samp{COMMAND_} constants |
| 3490 | defined below. This argument tells @value{GDBN} how to categorize the |
| 3491 | new command in the help system. |
| 3492 | |
| 3493 | @var{completer_class} is an optional argument. If given, it should be |
| 3494 | one of the @samp{COMPLETE_} constants defined below. This argument |
| 3495 | tells @value{GDBN} how to perform completion for this command. If not |
| 3496 | given, @value{GDBN} will attempt to complete using the object's |
| 3497 | @code{complete} method (see below); if no such method is found, an |
| 3498 | error will occur when completion is attempted. |
| 3499 | |
| 3500 | @var{prefix} is an optional argument. If @code{True}, then the new |
| 3501 | command is a prefix command; sub-commands of this command may be |
| 3502 | registered. |
| 3503 | |
| 3504 | The help text for the new command is taken from the Python |
| 3505 | documentation string for the command's class, if there is one. If no |
| 3506 | documentation string is provided, the default value ``This command is |
| 3507 | not documented.'' is used. |
| 3508 | @end defun |
| 3509 | |
| 3510 | @cindex don't repeat Python command |
| 3511 | @defun Command.dont_repeat () |
| 3512 | By default, a @value{GDBN} command is repeated when the user enters a |
| 3513 | blank line at the command prompt. A command can suppress this |
| 3514 | behavior by invoking the @code{dont_repeat} method. This is similar |
| 3515 | to the user command @code{dont-repeat}, see @ref{Define, dont-repeat}. |
| 3516 | @end defun |
| 3517 | |
| 3518 | @defun Command.invoke (argument, from_tty) |
| 3519 | This method is called by @value{GDBN} when this command is invoked. |
| 3520 | |
| 3521 | @var{argument} is a string. It is the argument to the command, after |
| 3522 | leading and trailing whitespace has been stripped. |
| 3523 | |
| 3524 | @var{from_tty} is a boolean argument. When true, this means that the |
| 3525 | command was entered by the user at the terminal; when false it means |
| 3526 | that the command came from elsewhere. |
| 3527 | |
| 3528 | If this method throws an exception, it is turned into a @value{GDBN} |
| 3529 | @code{error} call. Otherwise, the return value is ignored. |
| 3530 | |
| 3531 | @findex gdb.string_to_argv |
| 3532 | To break @var{argument} up into an argv-like string use |
| 3533 | @code{gdb.string_to_argv}. This function behaves identically to |
| 3534 | @value{GDBN}'s internal argument lexer @code{buildargv}. |
| 3535 | It is recommended to use this for consistency. |
| 3536 | Arguments are separated by spaces and may be quoted. |
| 3537 | Example: |
| 3538 | |
| 3539 | @smallexample |
| 3540 | print gdb.string_to_argv ("1 2\ \\\"3 '4 \"5' \"6 '7\"") |
| 3541 | ['1', '2 "3', '4 "5', "6 '7"] |
| 3542 | @end smallexample |
| 3543 | |
| 3544 | @end defun |
| 3545 | |
| 3546 | @cindex completion of Python commands |
| 3547 | @defun Command.complete (text, word) |
| 3548 | This method is called by @value{GDBN} when the user attempts |
| 3549 | completion on this command. All forms of completion are handled by |
| 3550 | this method, that is, the @key{TAB} and @key{M-?} key bindings |
| 3551 | (@pxref{Completion}), and the @code{complete} command (@pxref{Help, |
| 3552 | complete}). |
| 3553 | |
| 3554 | The arguments @var{text} and @var{word} are both strings; @var{text} |
| 3555 | holds the complete command line up to the cursor's location, while |
| 3556 | @var{word} holds the last word of the command line; this is computed |
| 3557 | using a word-breaking heuristic. |
| 3558 | |
| 3559 | The @code{complete} method can return several values: |
| 3560 | @itemize @bullet |
| 3561 | @item |
| 3562 | If the return value is a sequence, the contents of the sequence are |
| 3563 | used as the completions. It is up to @code{complete} to ensure that the |
| 3564 | contents actually do complete the word. A zero-length sequence is |
| 3565 | allowed, it means that there were no completions available. Only |
| 3566 | string elements of the sequence are used; other elements in the |
| 3567 | sequence are ignored. |
| 3568 | |
| 3569 | @item |
| 3570 | If the return value is one of the @samp{COMPLETE_} constants defined |
| 3571 | below, then the corresponding @value{GDBN}-internal completion |
| 3572 | function is invoked, and its result is used. |
| 3573 | |
| 3574 | @item |
| 3575 | All other results are treated as though there were no available |
| 3576 | completions. |
| 3577 | @end itemize |
| 3578 | @end defun |
| 3579 | |
| 3580 | When a new command is registered, it must be declared as a member of |
| 3581 | some general class of commands. This is used to classify top-level |
| 3582 | commands in the on-line help system; note that prefix commands are not |
| 3583 | listed under their own category but rather that of their top-level |
| 3584 | command. The available classifications are represented by constants |
| 3585 | defined in the @code{gdb} module: |
| 3586 | |
| 3587 | @table @code |
| 3588 | @findex COMMAND_NONE |
| 3589 | @findex gdb.COMMAND_NONE |
| 3590 | @item gdb.COMMAND_NONE |
| 3591 | The command does not belong to any particular class. A command in |
| 3592 | this category will not be displayed in any of the help categories. |
| 3593 | |
| 3594 | @findex COMMAND_RUNNING |
| 3595 | @findex gdb.COMMAND_RUNNING |
| 3596 | @item gdb.COMMAND_RUNNING |
| 3597 | The command is related to running the inferior. For example, |
| 3598 | @code{start}, @code{step}, and @code{continue} are in this category. |
| 3599 | Type @kbd{help running} at the @value{GDBN} prompt to see a list of |
| 3600 | commands in this category. |
| 3601 | |
| 3602 | @findex COMMAND_DATA |
| 3603 | @findex gdb.COMMAND_DATA |
| 3604 | @item gdb.COMMAND_DATA |
| 3605 | The command is related to data or variables. For example, |
| 3606 | @code{call}, @code{find}, and @code{print} are in this category. Type |
| 3607 | @kbd{help data} at the @value{GDBN} prompt to see a list of commands |
| 3608 | in this category. |
| 3609 | |
| 3610 | @findex COMMAND_STACK |
| 3611 | @findex gdb.COMMAND_STACK |
| 3612 | @item gdb.COMMAND_STACK |
| 3613 | The command has to do with manipulation of the stack. For example, |
| 3614 | @code{backtrace}, @code{frame}, and @code{return} are in this |
| 3615 | category. Type @kbd{help stack} at the @value{GDBN} prompt to see a |
| 3616 | list of commands in this category. |
| 3617 | |
| 3618 | @findex COMMAND_FILES |
| 3619 | @findex gdb.COMMAND_FILES |
| 3620 | @item gdb.COMMAND_FILES |
| 3621 | This class is used for file-related commands. For example, |
| 3622 | @code{file}, @code{list} and @code{section} are in this category. |
| 3623 | Type @kbd{help files} at the @value{GDBN} prompt to see a list of |
| 3624 | commands in this category. |
| 3625 | |
| 3626 | @findex COMMAND_SUPPORT |
| 3627 | @findex gdb.COMMAND_SUPPORT |
| 3628 | @item gdb.COMMAND_SUPPORT |
| 3629 | This should be used for ``support facilities'', generally meaning |
| 3630 | things that are useful to the user when interacting with @value{GDBN}, |
| 3631 | but not related to the state of the inferior. For example, |
| 3632 | @code{help}, @code{make}, and @code{shell} are in this category. Type |
| 3633 | @kbd{help support} at the @value{GDBN} prompt to see a list of |
| 3634 | commands in this category. |
| 3635 | |
| 3636 | @findex COMMAND_STATUS |
| 3637 | @findex gdb.COMMAND_STATUS |
| 3638 | @item gdb.COMMAND_STATUS |
| 3639 | The command is an @samp{info}-related command, that is, related to the |
| 3640 | state of @value{GDBN} itself. For example, @code{info}, @code{macro}, |
| 3641 | and @code{show} are in this category. Type @kbd{help status} at the |
| 3642 | @value{GDBN} prompt to see a list of commands in this category. |
| 3643 | |
| 3644 | @findex COMMAND_BREAKPOINTS |
| 3645 | @findex gdb.COMMAND_BREAKPOINTS |
| 3646 | @item gdb.COMMAND_BREAKPOINTS |
| 3647 | The command has to do with breakpoints. For example, @code{break}, |
| 3648 | @code{clear}, and @code{delete} are in this category. Type @kbd{help |
| 3649 | breakpoints} at the @value{GDBN} prompt to see a list of commands in |
| 3650 | this category. |
| 3651 | |
| 3652 | @findex COMMAND_TRACEPOINTS |
| 3653 | @findex gdb.COMMAND_TRACEPOINTS |
| 3654 | @item gdb.COMMAND_TRACEPOINTS |
| 3655 | The command has to do with tracepoints. For example, @code{trace}, |
| 3656 | @code{actions}, and @code{tfind} are in this category. Type |
| 3657 | @kbd{help tracepoints} at the @value{GDBN} prompt to see a list of |
| 3658 | commands in this category. |
| 3659 | |
| 3660 | @findex COMMAND_USER |
| 3661 | @findex gdb.COMMAND_USER |
| 3662 | @item gdb.COMMAND_USER |
| 3663 | The command is a general purpose command for the user, and typically |
| 3664 | does not fit in one of the other categories. |
| 3665 | Type @kbd{help user-defined} at the @value{GDBN} prompt to see |
| 3666 | a list of commands in this category, as well as the list of gdb macros |
| 3667 | (@pxref{Sequences}). |
| 3668 | |
| 3669 | @findex COMMAND_OBSCURE |
| 3670 | @findex gdb.COMMAND_OBSCURE |
| 3671 | @item gdb.COMMAND_OBSCURE |
| 3672 | The command is only used in unusual circumstances, or is not of |
| 3673 | general interest to users. For example, @code{checkpoint}, |
| 3674 | @code{fork}, and @code{stop} are in this category. Type @kbd{help |
| 3675 | obscure} at the @value{GDBN} prompt to see a list of commands in this |
| 3676 | category. |
| 3677 | |
| 3678 | @findex COMMAND_MAINTENANCE |
| 3679 | @findex gdb.COMMAND_MAINTENANCE |
| 3680 | @item gdb.COMMAND_MAINTENANCE |
| 3681 | The command is only useful to @value{GDBN} maintainers. The |
| 3682 | @code{maintenance} and @code{flushregs} commands are in this category. |
| 3683 | Type @kbd{help internals} at the @value{GDBN} prompt to see a list of |
| 3684 | commands in this category. |
| 3685 | @end table |
| 3686 | |
| 3687 | A new command can use a predefined completion function, either by |
| 3688 | specifying it via an argument at initialization, or by returning it |
| 3689 | from the @code{complete} method. These predefined completion |
| 3690 | constants are all defined in the @code{gdb} module: |
| 3691 | |
| 3692 | @vtable @code |
| 3693 | @vindex COMPLETE_NONE |
| 3694 | @item gdb.COMPLETE_NONE |
| 3695 | This constant means that no completion should be done. |
| 3696 | |
| 3697 | @vindex COMPLETE_FILENAME |
| 3698 | @item gdb.COMPLETE_FILENAME |
| 3699 | This constant means that filename completion should be performed. |
| 3700 | |
| 3701 | @vindex COMPLETE_LOCATION |
| 3702 | @item gdb.COMPLETE_LOCATION |
| 3703 | This constant means that location completion should be done. |
| 3704 | @xref{Specify Location}. |
| 3705 | |
| 3706 | @vindex COMPLETE_COMMAND |
| 3707 | @item gdb.COMPLETE_COMMAND |
| 3708 | This constant means that completion should examine @value{GDBN} |
| 3709 | command names. |
| 3710 | |
| 3711 | @vindex COMPLETE_SYMBOL |
| 3712 | @item gdb.COMPLETE_SYMBOL |
| 3713 | This constant means that completion should be done using symbol names |
| 3714 | as the source. |
| 3715 | |
| 3716 | @vindex COMPLETE_EXPRESSION |
| 3717 | @item gdb.COMPLETE_EXPRESSION |
| 3718 | This constant means that completion should be done on expressions. |
| 3719 | Often this means completing on symbol names, but some language |
| 3720 | parsers also have support for completing on field names. |
| 3721 | @end vtable |
| 3722 | |
| 3723 | The following code snippet shows how a trivial CLI command can be |
| 3724 | implemented in Python: |
| 3725 | |
| 3726 | @smallexample |
| 3727 | class HelloWorld (gdb.Command): |
| 3728 | """Greet the whole world.""" |
| 3729 | |
| 3730 | def __init__ (self): |
| 3731 | super (HelloWorld, self).__init__ ("hello-world", gdb.COMMAND_USER) |
| 3732 | |
| 3733 | def invoke (self, arg, from_tty): |
| 3734 | print "Hello, World!" |
| 3735 | |
| 3736 | HelloWorld () |
| 3737 | @end smallexample |
| 3738 | |
| 3739 | The last line instantiates the class, and is necessary to trigger the |
| 3740 | registration of the command with @value{GDBN}. Depending on how the |
| 3741 | Python code is read into @value{GDBN}, you may need to import the |
| 3742 | @code{gdb} module explicitly. |
| 3743 | |
| 3744 | @node Parameters In Python |
| 3745 | @subsubsection Parameters In Python |
| 3746 | |
| 3747 | @cindex parameters in python |
| 3748 | @cindex python parameters |
| 3749 | @tindex gdb.Parameter |
| 3750 | @tindex Parameter |
| 3751 | You can implement new @value{GDBN} parameters using Python. A new |
| 3752 | parameter is implemented as an instance of the @code{gdb.Parameter} |
| 3753 | class. |
| 3754 | |
| 3755 | Parameters are exposed to the user via the @code{set} and |
| 3756 | @code{show} commands. @xref{Help}. |
| 3757 | |
| 3758 | There are many parameters that already exist and can be set in |
| 3759 | @value{GDBN}. Two examples are: @code{set follow fork} and |
| 3760 | @code{set charset}. Setting these parameters influences certain |
| 3761 | behavior in @value{GDBN}. Similarly, you can define parameters that |
| 3762 | can be used to influence behavior in custom Python scripts and commands. |
| 3763 | |
| 3764 | @defun Parameter.__init__ (name, @var{command-class}, @var{parameter-class} @r{[}, @var{enum-sequence}@r{]}) |
| 3765 | The object initializer for @code{Parameter} registers the new |
| 3766 | parameter with @value{GDBN}. This initializer is normally invoked |
| 3767 | from the subclass' own @code{__init__} method. |
| 3768 | |
| 3769 | @var{name} is the name of the new parameter. If @var{name} consists |
| 3770 | of multiple words, then the initial words are looked for as prefix |
| 3771 | parameters. An example of this can be illustrated with the |
| 3772 | @code{set print} set of parameters. If @var{name} is |
| 3773 | @code{print foo}, then @code{print} will be searched as the prefix |
| 3774 | parameter. In this case the parameter can subsequently be accessed in |
| 3775 | @value{GDBN} as @code{set print foo}. |
| 3776 | |
| 3777 | If @var{name} consists of multiple words, and no prefix parameter group |
| 3778 | can be found, an exception is raised. |
| 3779 | |
| 3780 | @var{command-class} should be one of the @samp{COMMAND_} constants |
| 3781 | (@pxref{Commands In Python}). This argument tells @value{GDBN} how to |
| 3782 | categorize the new parameter in the help system. |
| 3783 | |
| 3784 | @var{parameter-class} should be one of the @samp{PARAM_} constants |
| 3785 | defined below. This argument tells @value{GDBN} the type of the new |
| 3786 | parameter; this information is used for input validation and |
| 3787 | completion. |
| 3788 | |
| 3789 | If @var{parameter-class} is @code{PARAM_ENUM}, then |
| 3790 | @var{enum-sequence} must be a sequence of strings. These strings |
| 3791 | represent the possible values for the parameter. |
| 3792 | |
| 3793 | If @var{parameter-class} is not @code{PARAM_ENUM}, then the presence |
| 3794 | of a fourth argument will cause an exception to be thrown. |
| 3795 | |
| 3796 | The help text for the new parameter is taken from the Python |
| 3797 | documentation string for the parameter's class, if there is one. If |
| 3798 | there is no documentation string, a default value is used. |
| 3799 | @end defun |
| 3800 | |
| 3801 | @defvar Parameter.set_doc |
| 3802 | If this attribute exists, and is a string, then its value is used as |
| 3803 | the help text for this parameter's @code{set} command. The value is |
| 3804 | examined when @code{Parameter.__init__} is invoked; subsequent changes |
| 3805 | have no effect. |
| 3806 | @end defvar |
| 3807 | |
| 3808 | @defvar Parameter.show_doc |
| 3809 | If this attribute exists, and is a string, then its value is used as |
| 3810 | the help text for this parameter's @code{show} command. The value is |
| 3811 | examined when @code{Parameter.__init__} is invoked; subsequent changes |
| 3812 | have no effect. |
| 3813 | @end defvar |
| 3814 | |
| 3815 | @defvar Parameter.value |
| 3816 | The @code{value} attribute holds the underlying value of the |
| 3817 | parameter. It can be read and assigned to just as any other |
| 3818 | attribute. @value{GDBN} does validation when assignments are made. |
| 3819 | @end defvar |
| 3820 | |
| 3821 | There are two methods that may be implemented in any @code{Parameter} |
| 3822 | class. These are: |
| 3823 | |
| 3824 | @defun Parameter.get_set_string (self) |
| 3825 | If this method exists, @value{GDBN} will call it when a |
| 3826 | @var{parameter}'s value has been changed via the @code{set} API (for |
| 3827 | example, @kbd{set foo off}). The @code{value} attribute has already |
| 3828 | been populated with the new value and may be used in output. This |
| 3829 | method must return a string. If the returned string is not empty, |
| 3830 | @value{GDBN} will present it to the user. |
| 3831 | @end defun |
| 3832 | |
| 3833 | @defun Parameter.get_show_string (self, svalue) |
| 3834 | @value{GDBN} will call this method when a @var{parameter}'s |
| 3835 | @code{show} API has been invoked (for example, @kbd{show foo}). The |
| 3836 | argument @code{svalue} receives the string representation of the |
| 3837 | current value. This method must return a string. |
| 3838 | @end defun |
| 3839 | |
| 3840 | When a new parameter is defined, its type must be specified. The |
| 3841 | available types are represented by constants defined in the @code{gdb} |
| 3842 | module: |
| 3843 | |
| 3844 | @table @code |
| 3845 | @findex PARAM_BOOLEAN |
| 3846 | @findex gdb.PARAM_BOOLEAN |
| 3847 | @item gdb.PARAM_BOOLEAN |
| 3848 | The value is a plain boolean. The Python boolean values, @code{True} |
| 3849 | and @code{False} are the only valid values. |
| 3850 | |
| 3851 | @findex PARAM_AUTO_BOOLEAN |
| 3852 | @findex gdb.PARAM_AUTO_BOOLEAN |
| 3853 | @item gdb.PARAM_AUTO_BOOLEAN |
| 3854 | The value has three possible states: true, false, and @samp{auto}. In |
| 3855 | Python, true and false are represented using boolean constants, and |
| 3856 | @samp{auto} is represented using @code{None}. |
| 3857 | |
| 3858 | @findex PARAM_UINTEGER |
| 3859 | @findex gdb.PARAM_UINTEGER |
| 3860 | @item gdb.PARAM_UINTEGER |
| 3861 | The value is an unsigned integer. The value of 0 should be |
| 3862 | interpreted to mean ``unlimited''. |
| 3863 | |
| 3864 | @findex PARAM_INTEGER |
| 3865 | @findex gdb.PARAM_INTEGER |
| 3866 | @item gdb.PARAM_INTEGER |
| 3867 | The value is a signed integer. The value of 0 should be interpreted |
| 3868 | to mean ``unlimited''. |
| 3869 | |
| 3870 | @findex PARAM_STRING |
| 3871 | @findex gdb.PARAM_STRING |
| 3872 | @item gdb.PARAM_STRING |
| 3873 | The value is a string. When the user modifies the string, any escape |
| 3874 | sequences, such as @samp{\t}, @samp{\f}, and octal escapes, are |
| 3875 | translated into corresponding characters and encoded into the current |
| 3876 | host charset. |
| 3877 | |
| 3878 | @findex PARAM_STRING_NOESCAPE |
| 3879 | @findex gdb.PARAM_STRING_NOESCAPE |
| 3880 | @item gdb.PARAM_STRING_NOESCAPE |
| 3881 | The value is a string. When the user modifies the string, escapes are |
| 3882 | passed through untranslated. |
| 3883 | |
| 3884 | @findex PARAM_OPTIONAL_FILENAME |
| 3885 | @findex gdb.PARAM_OPTIONAL_FILENAME |
| 3886 | @item gdb.PARAM_OPTIONAL_FILENAME |
| 3887 | The value is a either a filename (a string), or @code{None}. |
| 3888 | |
| 3889 | @findex PARAM_FILENAME |
| 3890 | @findex gdb.PARAM_FILENAME |
| 3891 | @item gdb.PARAM_FILENAME |
| 3892 | The value is a filename. This is just like |
| 3893 | @code{PARAM_STRING_NOESCAPE}, but uses file names for completion. |
| 3894 | |
| 3895 | @findex PARAM_ZINTEGER |
| 3896 | @findex gdb.PARAM_ZINTEGER |
| 3897 | @item gdb.PARAM_ZINTEGER |
| 3898 | The value is an integer. This is like @code{PARAM_INTEGER}, except 0 |
| 3899 | is interpreted as itself. |
| 3900 | |
| 3901 | @findex PARAM_ZUINTEGER |
| 3902 | @findex gdb.PARAM_ZUINTEGER |
| 3903 | @item gdb.PARAM_ZUINTEGER |
| 3904 | The value is an unsigned integer. This is like @code{PARAM_INTEGER}, |
| 3905 | except 0 is interpreted as itself, and the value cannot be negative. |
| 3906 | |
| 3907 | @findex PARAM_ZUINTEGER_UNLIMITED |
| 3908 | @findex gdb.PARAM_ZUINTEGER_UNLIMITED |
| 3909 | @item gdb.PARAM_ZUINTEGER_UNLIMITED |
| 3910 | The value is a signed integer. This is like @code{PARAM_ZUINTEGER}, |
| 3911 | except the special value -1 should be interpreted to mean |
| 3912 | ``unlimited''. Other negative values are not allowed. |
| 3913 | |
| 3914 | @findex PARAM_ENUM |
| 3915 | @findex gdb.PARAM_ENUM |
| 3916 | @item gdb.PARAM_ENUM |
| 3917 | The value is a string, which must be one of a collection string |
| 3918 | constants provided when the parameter is created. |
| 3919 | @end table |
| 3920 | |
| 3921 | @node Functions In Python |
| 3922 | @subsubsection Writing new convenience functions |
| 3923 | |
| 3924 | @cindex writing convenience functions |
| 3925 | @cindex convenience functions in python |
| 3926 | @cindex python convenience functions |
| 3927 | @tindex gdb.Function |
| 3928 | @tindex Function |
| 3929 | You can implement new convenience functions (@pxref{Convenience Vars}) |
| 3930 | in Python. A convenience function is an instance of a subclass of the |
| 3931 | class @code{gdb.Function}. |
| 3932 | |
| 3933 | @defun Function.__init__ (name) |
| 3934 | The initializer for @code{Function} registers the new function with |
| 3935 | @value{GDBN}. The argument @var{name} is the name of the function, |
| 3936 | a string. The function will be visible to the user as a convenience |
| 3937 | variable of type @code{internal function}, whose name is the same as |
| 3938 | the given @var{name}. |
| 3939 | |
| 3940 | The documentation for the new function is taken from the documentation |
| 3941 | string for the new class. |
| 3942 | @end defun |
| 3943 | |
| 3944 | @defun Function.invoke (@var{*args}) |
| 3945 | When a convenience function is evaluated, its arguments are converted |
| 3946 | to instances of @code{gdb.Value}, and then the function's |
| 3947 | @code{invoke} method is called. Note that @value{GDBN} does not |
| 3948 | predetermine the arity of convenience functions. Instead, all |
| 3949 | available arguments are passed to @code{invoke}, following the |
| 3950 | standard Python calling convention. In particular, a convenience |
| 3951 | function can have default values for parameters without ill effect. |
| 3952 | |
| 3953 | The return value of this method is used as its value in the enclosing |
| 3954 | expression. If an ordinary Python value is returned, it is converted |
| 3955 | to a @code{gdb.Value} following the usual rules. |
| 3956 | @end defun |
| 3957 | |
| 3958 | The following code snippet shows how a trivial convenience function can |
| 3959 | be implemented in Python: |
| 3960 | |
| 3961 | @smallexample |
| 3962 | class Greet (gdb.Function): |
| 3963 | """Return string to greet someone. |
| 3964 | Takes a name as argument.""" |
| 3965 | |
| 3966 | def __init__ (self): |
| 3967 | super (Greet, self).__init__ ("greet") |
| 3968 | |
| 3969 | def invoke (self, name): |
| 3970 | return "Hello, %s!" % name.string () |
| 3971 | |
| 3972 | Greet () |
| 3973 | @end smallexample |
| 3974 | |
| 3975 | The last line instantiates the class, and is necessary to trigger the |
| 3976 | registration of the function with @value{GDBN}. Depending on how the |
| 3977 | Python code is read into @value{GDBN}, you may need to import the |
| 3978 | @code{gdb} module explicitly. |
| 3979 | |
| 3980 | Now you can use the function in an expression: |
| 3981 | |
| 3982 | @smallexample |
| 3983 | (gdb) print $greet("Bob") |
| 3984 | $1 = "Hello, Bob!" |
| 3985 | @end smallexample |
| 3986 | |
| 3987 | @node Progspaces In Python |
| 3988 | @subsubsection Program Spaces In Python |
| 3989 | |
| 3990 | @cindex progspaces in python |
| 3991 | @tindex gdb.Progspace |
| 3992 | @tindex Progspace |
| 3993 | A program space, or @dfn{progspace}, represents a symbolic view |
| 3994 | of an address space. |
| 3995 | It consists of all of the objfiles of the program. |
| 3996 | @xref{Objfiles In Python}. |
| 3997 | @xref{Inferiors and Programs, program spaces}, for more details |
| 3998 | about program spaces. |
| 3999 | |
| 4000 | The following progspace-related functions are available in the |
| 4001 | @code{gdb} module: |
| 4002 | |
| 4003 | @findex gdb.current_progspace |
| 4004 | @defun gdb.current_progspace () |
| 4005 | This function returns the program space of the currently selected inferior. |
| 4006 | @xref{Inferiors and Programs}. This is identical to |
| 4007 | @code{gdb.selected_inferior().progspace} (@pxref{Inferiors In Python}) and is |
| 4008 | included for historical compatibility. |
| 4009 | @end defun |
| 4010 | |
| 4011 | @findex gdb.progspaces |
| 4012 | @defun gdb.progspaces () |
| 4013 | Return a sequence of all the progspaces currently known to @value{GDBN}. |
| 4014 | @end defun |
| 4015 | |
| 4016 | Each progspace is represented by an instance of the @code{gdb.Progspace} |
| 4017 | class. |
| 4018 | |
| 4019 | @defvar Progspace.filename |
| 4020 | The file name of the progspace as a string. |
| 4021 | @end defvar |
| 4022 | |
| 4023 | @defvar Progspace.pretty_printers |
| 4024 | The @code{pretty_printers} attribute is a list of functions. It is |
| 4025 | used to look up pretty-printers. A @code{Value} is passed to each |
| 4026 | function in order; if the function returns @code{None}, then the |
| 4027 | search continues. Otherwise, the return value should be an object |
| 4028 | which is used to format the value. @xref{Pretty Printing API}, for more |
| 4029 | information. |
| 4030 | @end defvar |
| 4031 | |
| 4032 | @defvar Progspace.type_printers |
| 4033 | The @code{type_printers} attribute is a list of type printer objects. |
| 4034 | @xref{Type Printing API}, for more information. |
| 4035 | @end defvar |
| 4036 | |
| 4037 | @defvar Progspace.frame_filters |
| 4038 | The @code{frame_filters} attribute is a dictionary of frame filter |
| 4039 | objects. @xref{Frame Filter API}, for more information. |
| 4040 | @end defvar |
| 4041 | |
| 4042 | A program space has the following methods: |
| 4043 | |
| 4044 | @findex Progspace.block_for_pc |
| 4045 | @defun Progspace.block_for_pc (pc) |
| 4046 | Return the innermost @code{gdb.Block} containing the given @var{pc} |
| 4047 | value. If the block cannot be found for the @var{pc} value specified, |
| 4048 | the function will return @code{None}. |
| 4049 | @end defun |
| 4050 | |
| 4051 | @findex Progspace.find_pc_line |
| 4052 | @defun Progspace.find_pc_line (pc) |
| 4053 | Return the @code{gdb.Symtab_and_line} object corresponding to the |
| 4054 | @var{pc} value. @xref{Symbol Tables In Python}. If an invalid value |
| 4055 | of @var{pc} is passed as an argument, then the @code{symtab} and |
| 4056 | @code{line} attributes of the returned @code{gdb.Symtab_and_line} |
| 4057 | object will be @code{None} and 0 respectively. |
| 4058 | @end defun |
| 4059 | |
| 4060 | @findex Progspace.is_valid |
| 4061 | @defun Progspace.is_valid () |
| 4062 | Returns @code{True} if the @code{gdb.Progspace} object is valid, |
| 4063 | @code{False} if not. A @code{gdb.Progspace} object can become invalid |
| 4064 | if the program space file it refers to is not referenced by any |
| 4065 | inferior. All other @code{gdb.Progspace} methods will throw an |
| 4066 | exception if it is invalid at the time the method is called. |
| 4067 | @end defun |
| 4068 | |
| 4069 | @findex Progspace.objfiles |
| 4070 | @defun Progspace.objfiles () |
| 4071 | Return a sequence of all the objfiles referenced by this program |
| 4072 | space. @xref{Objfiles In Python}. |
| 4073 | @end defun |
| 4074 | |
| 4075 | @findex Progspace.solib_name |
| 4076 | @defun Progspace.solib_name (address) |
| 4077 | Return the name of the shared library holding the given @var{address} |
| 4078 | as a string, or @code{None}. |
| 4079 | @end defun |
| 4080 | |
| 4081 | One may add arbitrary attributes to @code{gdb.Progspace} objects |
| 4082 | in the usual Python way. |
| 4083 | This is useful if, for example, one needs to do some extra record keeping |
| 4084 | associated with the program space. |
| 4085 | |
| 4086 | In this contrived example, we want to perform some processing when |
| 4087 | an objfile with a certain symbol is loaded, but we only want to do |
| 4088 | this once because it is expensive. To achieve this we record the results |
| 4089 | with the program space because we can't predict when the desired objfile |
| 4090 | will be loaded. |
| 4091 | |
| 4092 | @smallexample |
| 4093 | (gdb) python |
| 4094 | def clear_objfiles_handler(event): |
| 4095 | event.progspace.expensive_computation = None |
| 4096 | def expensive(symbol): |
| 4097 | """A mock routine to perform an "expensive" computation on symbol.""" |
| 4098 | print "Computing the answer to the ultimate question ..." |
| 4099 | return 42 |
| 4100 | def new_objfile_handler(event): |
| 4101 | objfile = event.new_objfile |
| 4102 | progspace = objfile.progspace |
| 4103 | if not hasattr(progspace, 'expensive_computation') or \ |
| 4104 | progspace.expensive_computation is None: |
| 4105 | # We use 'main' for the symbol to keep the example simple. |
| 4106 | # Note: There's no current way to constrain the lookup |
| 4107 | # to one objfile. |
| 4108 | symbol = gdb.lookup_global_symbol('main') |
| 4109 | if symbol is not None: |
| 4110 | progspace.expensive_computation = expensive(symbol) |
| 4111 | gdb.events.clear_objfiles.connect(clear_objfiles_handler) |
| 4112 | gdb.events.new_objfile.connect(new_objfile_handler) |
| 4113 | end |
| 4114 | (gdb) file /tmp/hello |
| 4115 | Reading symbols from /tmp/hello...done. |
| 4116 | Computing the answer to the ultimate question ... |
| 4117 | (gdb) python print gdb.current_progspace().expensive_computation |
| 4118 | 42 |
| 4119 | (gdb) run |
| 4120 | Starting program: /tmp/hello |
| 4121 | Hello. |
| 4122 | [Inferior 1 (process 4242) exited normally] |
| 4123 | @end smallexample |
| 4124 | |
| 4125 | @node Objfiles In Python |
| 4126 | @subsubsection Objfiles In Python |
| 4127 | |
| 4128 | @cindex objfiles in python |
| 4129 | @tindex gdb.Objfile |
| 4130 | @tindex Objfile |
| 4131 | @value{GDBN} loads symbols for an inferior from various |
| 4132 | symbol-containing files (@pxref{Files}). These include the primary |
| 4133 | executable file, any shared libraries used by the inferior, and any |
| 4134 | separate debug info files (@pxref{Separate Debug Files}). |
| 4135 | @value{GDBN} calls these symbol-containing files @dfn{objfiles}. |
| 4136 | |
| 4137 | The following objfile-related functions are available in the |
| 4138 | @code{gdb} module: |
| 4139 | |
| 4140 | @findex gdb.current_objfile |
| 4141 | @defun gdb.current_objfile () |
| 4142 | When auto-loading a Python script (@pxref{Python Auto-loading}), @value{GDBN} |
| 4143 | sets the ``current objfile'' to the corresponding objfile. This |
| 4144 | function returns the current objfile. If there is no current objfile, |
| 4145 | this function returns @code{None}. |
| 4146 | @end defun |
| 4147 | |
| 4148 | @findex gdb.objfiles |
| 4149 | @defun gdb.objfiles () |
| 4150 | Return a sequence of objfiles referenced by the current program space. |
| 4151 | @xref{Objfiles In Python}, and @ref{Progspaces In Python}. This is identical |
| 4152 | to @code{gdb.selected_inferior().progspace.objfiles()} and is included for |
| 4153 | historical compatibility. |
| 4154 | @end defun |
| 4155 | |
| 4156 | @findex gdb.lookup_objfile |
| 4157 | @defun gdb.lookup_objfile (name @r{[}, by_build_id{]}) |
| 4158 | Look up @var{name}, a file name or build ID, in the list of objfiles |
| 4159 | for the current program space (@pxref{Progspaces In Python}). |
| 4160 | If the objfile is not found throw the Python @code{ValueError} exception. |
| 4161 | |
| 4162 | If @var{name} is a relative file name, then it will match any |
| 4163 | source file name with the same trailing components. For example, if |
| 4164 | @var{name} is @samp{gcc/expr.c}, then it will match source file |
| 4165 | name of @file{/build/trunk/gcc/expr.c}, but not |
| 4166 | @file{/build/trunk/libcpp/expr.c} or @file{/build/trunk/gcc/x-expr.c}. |
| 4167 | |
| 4168 | If @var{by_build_id} is provided and is @code{True} then @var{name} |
| 4169 | is the build ID of the objfile. Otherwise, @var{name} is a file name. |
| 4170 | This is supported only on some operating systems, notably those which use |
| 4171 | the ELF format for binary files and the @sc{gnu} Binutils. For more details |
| 4172 | about this feature, see the description of the @option{--build-id} |
| 4173 | command-line option in @ref{Options, , Command Line Options, ld, |
| 4174 | The GNU Linker}. |
| 4175 | @end defun |
| 4176 | |
| 4177 | Each objfile is represented by an instance of the @code{gdb.Objfile} |
| 4178 | class. |
| 4179 | |
| 4180 | @defvar Objfile.filename |
| 4181 | The file name of the objfile as a string, with symbolic links resolved. |
| 4182 | |
| 4183 | The value is @code{None} if the objfile is no longer valid. |
| 4184 | See the @code{gdb.Objfile.is_valid} method, described below. |
| 4185 | @end defvar |
| 4186 | |
| 4187 | @defvar Objfile.username |
| 4188 | The file name of the objfile as specified by the user as a string. |
| 4189 | |
| 4190 | The value is @code{None} if the objfile is no longer valid. |
| 4191 | See the @code{gdb.Objfile.is_valid} method, described below. |
| 4192 | @end defvar |
| 4193 | |
| 4194 | @defvar Objfile.owner |
| 4195 | For separate debug info objfiles this is the corresponding @code{gdb.Objfile} |
| 4196 | object that debug info is being provided for. |
| 4197 | Otherwise this is @code{None}. |
| 4198 | Separate debug info objfiles are added with the |
| 4199 | @code{gdb.Objfile.add_separate_debug_file} method, described below. |
| 4200 | @end defvar |
| 4201 | |
| 4202 | @defvar Objfile.build_id |
| 4203 | The build ID of the objfile as a string. |
| 4204 | If the objfile does not have a build ID then the value is @code{None}. |
| 4205 | |
| 4206 | This is supported only on some operating systems, notably those which use |
| 4207 | the ELF format for binary files and the @sc{gnu} Binutils. For more details |
| 4208 | about this feature, see the description of the @option{--build-id} |
| 4209 | command-line option in @ref{Options, , Command Line Options, ld, |
| 4210 | The GNU Linker}. |
| 4211 | @end defvar |
| 4212 | |
| 4213 | @defvar Objfile.progspace |
| 4214 | The containing program space of the objfile as a @code{gdb.Progspace} |
| 4215 | object. @xref{Progspaces In Python}. |
| 4216 | @end defvar |
| 4217 | |
| 4218 | @defvar Objfile.pretty_printers |
| 4219 | The @code{pretty_printers} attribute is a list of functions. It is |
| 4220 | used to look up pretty-printers. A @code{Value} is passed to each |
| 4221 | function in order; if the function returns @code{None}, then the |
| 4222 | search continues. Otherwise, the return value should be an object |
| 4223 | which is used to format the value. @xref{Pretty Printing API}, for more |
| 4224 | information. |
| 4225 | @end defvar |
| 4226 | |
| 4227 | @defvar Objfile.type_printers |
| 4228 | The @code{type_printers} attribute is a list of type printer objects. |
| 4229 | @xref{Type Printing API}, for more information. |
| 4230 | @end defvar |
| 4231 | |
| 4232 | @defvar Objfile.frame_filters |
| 4233 | The @code{frame_filters} attribute is a dictionary of frame filter |
| 4234 | objects. @xref{Frame Filter API}, for more information. |
| 4235 | @end defvar |
| 4236 | |
| 4237 | One may add arbitrary attributes to @code{gdb.Objfile} objects |
| 4238 | in the usual Python way. |
| 4239 | This is useful if, for example, one needs to do some extra record keeping |
| 4240 | associated with the objfile. |
| 4241 | |
| 4242 | In this contrived example we record the time when @value{GDBN} |
| 4243 | loaded the objfile. |
| 4244 | |
| 4245 | @smallexample |
| 4246 | (gdb) python |
| 4247 | import datetime |
| 4248 | def new_objfile_handler(event): |
| 4249 | # Set the time_loaded attribute of the new objfile. |
| 4250 | event.new_objfile.time_loaded = datetime.datetime.today() |
| 4251 | gdb.events.new_objfile.connect(new_objfile_handler) |
| 4252 | end |
| 4253 | (gdb) file ./hello |
| 4254 | Reading symbols from ./hello...done. |
| 4255 | (gdb) python print gdb.objfiles()[0].time_loaded |
| 4256 | 2014-10-09 11:41:36.770345 |
| 4257 | @end smallexample |
| 4258 | |
| 4259 | A @code{gdb.Objfile} object has the following methods: |
| 4260 | |
| 4261 | @defun Objfile.is_valid () |
| 4262 | Returns @code{True} if the @code{gdb.Objfile} object is valid, |
| 4263 | @code{False} if not. A @code{gdb.Objfile} object can become invalid |
| 4264 | if the object file it refers to is not loaded in @value{GDBN} any |
| 4265 | longer. All other @code{gdb.Objfile} methods will throw an exception |
| 4266 | if it is invalid at the time the method is called. |
| 4267 | @end defun |
| 4268 | |
| 4269 | @defun Objfile.add_separate_debug_file (file) |
| 4270 | Add @var{file} to the list of files that @value{GDBN} will search for |
| 4271 | debug information for the objfile. |
| 4272 | This is useful when the debug info has been removed from the program |
| 4273 | and stored in a separate file. @value{GDBN} has built-in support for |
| 4274 | finding separate debug info files (@pxref{Separate Debug Files}), but if |
| 4275 | the file doesn't live in one of the standard places that @value{GDBN} |
| 4276 | searches then this function can be used to add a debug info file |
| 4277 | from a different place. |
| 4278 | @end defun |
| 4279 | |
| 4280 | @node Frames In Python |
| 4281 | @subsubsection Accessing inferior stack frames from Python |
| 4282 | |
| 4283 | @cindex frames in python |
| 4284 | When the debugged program stops, @value{GDBN} is able to analyze its call |
| 4285 | stack (@pxref{Frames,,Stack frames}). The @code{gdb.Frame} class |
| 4286 | represents a frame in the stack. A @code{gdb.Frame} object is only valid |
| 4287 | while its corresponding frame exists in the inferior's stack. If you try |
| 4288 | to use an invalid frame object, @value{GDBN} will throw a @code{gdb.error} |
| 4289 | exception (@pxref{Exception Handling}). |
| 4290 | |
| 4291 | Two @code{gdb.Frame} objects can be compared for equality with the @code{==} |
| 4292 | operator, like: |
| 4293 | |
| 4294 | @smallexample |
| 4295 | (@value{GDBP}) python print gdb.newest_frame() == gdb.selected_frame () |
| 4296 | True |
| 4297 | @end smallexample |
| 4298 | |
| 4299 | The following frame-related functions are available in the @code{gdb} module: |
| 4300 | |
| 4301 | @findex gdb.selected_frame |
| 4302 | @defun gdb.selected_frame () |
| 4303 | Return the selected frame object. (@pxref{Selection,,Selecting a Frame}). |
| 4304 | @end defun |
| 4305 | |
| 4306 | @findex gdb.newest_frame |
| 4307 | @defun gdb.newest_frame () |
| 4308 | Return the newest frame object for the selected thread. |
| 4309 | @end defun |
| 4310 | |
| 4311 | @defun gdb.frame_stop_reason_string (reason) |
| 4312 | Return a string explaining the reason why @value{GDBN} stopped unwinding |
| 4313 | frames, as expressed by the given @var{reason} code (an integer, see the |
| 4314 | @code{unwind_stop_reason} method further down in this section). |
| 4315 | @end defun |
| 4316 | |
| 4317 | @findex gdb.invalidate_cached_frames |
| 4318 | @defun gdb.invalidate_cached_frames |
| 4319 | @value{GDBN} internally keeps a cache of the frames that have been |
| 4320 | unwound. This function invalidates this cache. |
| 4321 | |
| 4322 | This function should not generally be called by ordinary Python code. |
| 4323 | It is documented for the sake of completeness. |
| 4324 | @end defun |
| 4325 | |
| 4326 | A @code{gdb.Frame} object has the following methods: |
| 4327 | |
| 4328 | @defun Frame.is_valid () |
| 4329 | Returns true if the @code{gdb.Frame} object is valid, false if not. |
| 4330 | A frame object can become invalid if the frame it refers to doesn't |
| 4331 | exist anymore in the inferior. All @code{gdb.Frame} methods will throw |
| 4332 | an exception if it is invalid at the time the method is called. |
| 4333 | @end defun |
| 4334 | |
| 4335 | @defun Frame.name () |
| 4336 | Returns the function name of the frame, or @code{None} if it can't be |
| 4337 | obtained. |
| 4338 | @end defun |
| 4339 | |
| 4340 | @defun Frame.architecture () |
| 4341 | Returns the @code{gdb.Architecture} object corresponding to the frame's |
| 4342 | architecture. @xref{Architectures In Python}. |
| 4343 | @end defun |
| 4344 | |
| 4345 | @defun Frame.type () |
| 4346 | Returns the type of the frame. The value can be one of: |
| 4347 | @table @code |
| 4348 | @item gdb.NORMAL_FRAME |
| 4349 | An ordinary stack frame. |
| 4350 | |
| 4351 | @item gdb.DUMMY_FRAME |
| 4352 | A fake stack frame that was created by @value{GDBN} when performing an |
| 4353 | inferior function call. |
| 4354 | |
| 4355 | @item gdb.INLINE_FRAME |
| 4356 | A frame representing an inlined function. The function was inlined |
| 4357 | into a @code{gdb.NORMAL_FRAME} that is older than this one. |
| 4358 | |
| 4359 | @item gdb.TAILCALL_FRAME |
| 4360 | A frame representing a tail call. @xref{Tail Call Frames}. |
| 4361 | |
| 4362 | @item gdb.SIGTRAMP_FRAME |
| 4363 | A signal trampoline frame. This is the frame created by the OS when |
| 4364 | it calls into a signal handler. |
| 4365 | |
| 4366 | @item gdb.ARCH_FRAME |
| 4367 | A fake stack frame representing a cross-architecture call. |
| 4368 | |
| 4369 | @item gdb.SENTINEL_FRAME |
| 4370 | This is like @code{gdb.NORMAL_FRAME}, but it is only used for the |
| 4371 | newest frame. |
| 4372 | @end table |
| 4373 | @end defun |
| 4374 | |
| 4375 | @defun Frame.unwind_stop_reason () |
| 4376 | Return an integer representing the reason why it's not possible to find |
| 4377 | more frames toward the outermost frame. Use |
| 4378 | @code{gdb.frame_stop_reason_string} to convert the value returned by this |
| 4379 | function to a string. The value can be one of: |
| 4380 | |
| 4381 | @table @code |
| 4382 | @item gdb.FRAME_UNWIND_NO_REASON |
| 4383 | No particular reason (older frames should be available). |
| 4384 | |
| 4385 | @item gdb.FRAME_UNWIND_NULL_ID |
| 4386 | The previous frame's analyzer returns an invalid result. This is no |
| 4387 | longer used by @value{GDBN}, and is kept only for backward |
| 4388 | compatibility. |
| 4389 | |
| 4390 | @item gdb.FRAME_UNWIND_OUTERMOST |
| 4391 | This frame is the outermost. |
| 4392 | |
| 4393 | @item gdb.FRAME_UNWIND_UNAVAILABLE |
| 4394 | Cannot unwind further, because that would require knowing the |
| 4395 | values of registers or memory that have not been collected. |
| 4396 | |
| 4397 | @item gdb.FRAME_UNWIND_INNER_ID |
| 4398 | This frame ID looks like it ought to belong to a NEXT frame, |
| 4399 | but we got it for a PREV frame. Normally, this is a sign of |
| 4400 | unwinder failure. It could also indicate stack corruption. |
| 4401 | |
| 4402 | @item gdb.FRAME_UNWIND_SAME_ID |
| 4403 | This frame has the same ID as the previous one. That means |
| 4404 | that unwinding further would almost certainly give us another |
| 4405 | frame with exactly the same ID, so break the chain. Normally, |
| 4406 | this is a sign of unwinder failure. It could also indicate |
| 4407 | stack corruption. |
| 4408 | |
| 4409 | @item gdb.FRAME_UNWIND_NO_SAVED_PC |
| 4410 | The frame unwinder did not find any saved PC, but we needed |
| 4411 | one to unwind further. |
| 4412 | |
| 4413 | @item gdb.FRAME_UNWIND_MEMORY_ERROR |
| 4414 | The frame unwinder caused an error while trying to access memory. |
| 4415 | |
| 4416 | @item gdb.FRAME_UNWIND_FIRST_ERROR |
| 4417 | Any stop reason greater or equal to this value indicates some kind |
| 4418 | of error. This special value facilitates writing code that tests |
| 4419 | for errors in unwinding in a way that will work correctly even if |
| 4420 | the list of the other values is modified in future @value{GDBN} |
| 4421 | versions. Using it, you could write: |
| 4422 | @smallexample |
| 4423 | reason = gdb.selected_frame().unwind_stop_reason () |
| 4424 | reason_str = gdb.frame_stop_reason_string (reason) |
| 4425 | if reason >= gdb.FRAME_UNWIND_FIRST_ERROR: |
| 4426 | print "An error occured: %s" % reason_str |
| 4427 | @end smallexample |
| 4428 | @end table |
| 4429 | |
| 4430 | @end defun |
| 4431 | |
| 4432 | @defun Frame.pc () |
| 4433 | Returns the frame's resume address. |
| 4434 | @end defun |
| 4435 | |
| 4436 | @defun Frame.block () |
| 4437 | Return the frame's code block. @xref{Blocks In Python}. If the frame |
| 4438 | does not have a block -- for example, if there is no debugging |
| 4439 | information for the code in question -- then this will throw an |
| 4440 | exception. |
| 4441 | @end defun |
| 4442 | |
| 4443 | @defun Frame.function () |
| 4444 | Return the symbol for the function corresponding to this frame. |
| 4445 | @xref{Symbols In Python}. |
| 4446 | @end defun |
| 4447 | |
| 4448 | @defun Frame.older () |
| 4449 | Return the frame that called this frame. |
| 4450 | @end defun |
| 4451 | |
| 4452 | @defun Frame.newer () |
| 4453 | Return the frame called by this frame. |
| 4454 | @end defun |
| 4455 | |
| 4456 | @defun Frame.find_sal () |
| 4457 | Return the frame's symtab and line object. |
| 4458 | @xref{Symbol Tables In Python}. |
| 4459 | @end defun |
| 4460 | |
| 4461 | @defun Frame.read_register (register) |
| 4462 | Return the value of @var{register} in this frame. The @var{register} |
| 4463 | argument must be a string (e.g., @code{'sp'} or @code{'rax'}). |
| 4464 | Returns a @code{Gdb.Value} object. Throws an exception if @var{register} |
| 4465 | does not exist. |
| 4466 | @end defun |
| 4467 | |
| 4468 | @defun Frame.read_var (variable @r{[}, block@r{]}) |
| 4469 | Return the value of @var{variable} in this frame. If the optional |
| 4470 | argument @var{block} is provided, search for the variable from that |
| 4471 | block; otherwise start at the frame's current block (which is |
| 4472 | determined by the frame's current program counter). The @var{variable} |
| 4473 | argument must be a string or a @code{gdb.Symbol} object; @var{block} must be a |
| 4474 | @code{gdb.Block} object. |
| 4475 | @end defun |
| 4476 | |
| 4477 | @defun Frame.select () |
| 4478 | Set this frame to be the selected frame. @xref{Stack, ,Examining the |
| 4479 | Stack}. |
| 4480 | @end defun |
| 4481 | |
| 4482 | @node Blocks In Python |
| 4483 | @subsubsection Accessing blocks from Python |
| 4484 | |
| 4485 | @cindex blocks in python |
| 4486 | @tindex gdb.Block |
| 4487 | |
| 4488 | In @value{GDBN}, symbols are stored in blocks. A block corresponds |
| 4489 | roughly to a scope in the source code. Blocks are organized |
| 4490 | hierarchically, and are represented individually in Python as a |
| 4491 | @code{gdb.Block}. Blocks rely on debugging information being |
| 4492 | available. |
| 4493 | |
| 4494 | A frame has a block. Please see @ref{Frames In Python}, for a more |
| 4495 | in-depth discussion of frames. |
| 4496 | |
| 4497 | The outermost block is known as the @dfn{global block}. The global |
| 4498 | block typically holds public global variables and functions. |
| 4499 | |
| 4500 | The block nested just inside the global block is the @dfn{static |
| 4501 | block}. The static block typically holds file-scoped variables and |
| 4502 | functions. |
| 4503 | |
| 4504 | @value{GDBN} provides a method to get a block's superblock, but there |
| 4505 | is currently no way to examine the sub-blocks of a block, or to |
| 4506 | iterate over all the blocks in a symbol table (@pxref{Symbol Tables In |
| 4507 | Python}). |
| 4508 | |
| 4509 | Here is a short example that should help explain blocks: |
| 4510 | |
| 4511 | @smallexample |
| 4512 | /* This is in the global block. */ |
| 4513 | int global; |
| 4514 | |
| 4515 | /* This is in the static block. */ |
| 4516 | static int file_scope; |
| 4517 | |
| 4518 | /* 'function' is in the global block, and 'argument' is |
| 4519 | in a block nested inside of 'function'. */ |
| 4520 | int function (int argument) |
| 4521 | @{ |
| 4522 | /* 'local' is in a block inside 'function'. It may or may |
| 4523 | not be in the same block as 'argument'. */ |
| 4524 | int local; |
| 4525 | |
| 4526 | @{ |
| 4527 | /* 'inner' is in a block whose superblock is the one holding |
| 4528 | 'local'. */ |
| 4529 | int inner; |
| 4530 | |
| 4531 | /* If this call is expanded by the compiler, you may see |
| 4532 | a nested block here whose function is 'inline_function' |
| 4533 | and whose superblock is the one holding 'inner'. */ |
| 4534 | inline_function (); |
| 4535 | @} |
| 4536 | @} |
| 4537 | @end smallexample |
| 4538 | |
| 4539 | A @code{gdb.Block} is iterable. The iterator returns the symbols |
| 4540 | (@pxref{Symbols In Python}) local to the block. Python programs |
| 4541 | should not assume that a specific block object will always contain a |
| 4542 | given symbol, since changes in @value{GDBN} features and |
| 4543 | infrastructure may cause symbols move across blocks in a symbol |
| 4544 | table. |
| 4545 | |
| 4546 | The following block-related functions are available in the @code{gdb} |
| 4547 | module: |
| 4548 | |
| 4549 | @findex gdb.block_for_pc |
| 4550 | @defun gdb.block_for_pc (pc) |
| 4551 | Return the innermost @code{gdb.Block} containing the given @var{pc} |
| 4552 | value. If the block cannot be found for the @var{pc} value specified, |
| 4553 | the function will return @code{None}. This is identical to |
| 4554 | @code{gdb.current_progspace().block_for_pc(pc)} and is included for |
| 4555 | historical compatibility. |
| 4556 | @end defun |
| 4557 | |
| 4558 | A @code{gdb.Block} object has the following methods: |
| 4559 | |
| 4560 | @defun Block.is_valid () |
| 4561 | Returns @code{True} if the @code{gdb.Block} object is valid, |
| 4562 | @code{False} if not. A block object can become invalid if the block it |
| 4563 | refers to doesn't exist anymore in the inferior. All other |
| 4564 | @code{gdb.Block} methods will throw an exception if it is invalid at |
| 4565 | the time the method is called. The block's validity is also checked |
| 4566 | during iteration over symbols of the block. |
| 4567 | @end defun |
| 4568 | |
| 4569 | A @code{gdb.Block} object has the following attributes: |
| 4570 | |
| 4571 | @defvar Block.start |
| 4572 | The start address of the block. This attribute is not writable. |
| 4573 | @end defvar |
| 4574 | |
| 4575 | @defvar Block.end |
| 4576 | One past the last address that appears in the block. This attribute |
| 4577 | is not writable. |
| 4578 | @end defvar |
| 4579 | |
| 4580 | @defvar Block.function |
| 4581 | The name of the block represented as a @code{gdb.Symbol}. If the |
| 4582 | block is not named, then this attribute holds @code{None}. This |
| 4583 | attribute is not writable. |
| 4584 | |
| 4585 | For ordinary function blocks, the superblock is the static block. |
| 4586 | However, you should note that it is possible for a function block to |
| 4587 | have a superblock that is not the static block -- for instance this |
| 4588 | happens for an inlined function. |
| 4589 | @end defvar |
| 4590 | |
| 4591 | @defvar Block.superblock |
| 4592 | The block containing this block. If this parent block does not exist, |
| 4593 | this attribute holds @code{None}. This attribute is not writable. |
| 4594 | @end defvar |
| 4595 | |
| 4596 | @defvar Block.global_block |
| 4597 | The global block associated with this block. This attribute is not |
| 4598 | writable. |
| 4599 | @end defvar |
| 4600 | |
| 4601 | @defvar Block.static_block |
| 4602 | The static block associated with this block. This attribute is not |
| 4603 | writable. |
| 4604 | @end defvar |
| 4605 | |
| 4606 | @defvar Block.is_global |
| 4607 | @code{True} if the @code{gdb.Block} object is a global block, |
| 4608 | @code{False} if not. This attribute is not |
| 4609 | writable. |
| 4610 | @end defvar |
| 4611 | |
| 4612 | @defvar Block.is_static |
| 4613 | @code{True} if the @code{gdb.Block} object is a static block, |
| 4614 | @code{False} if not. This attribute is not writable. |
| 4615 | @end defvar |
| 4616 | |
| 4617 | @node Symbols In Python |
| 4618 | @subsubsection Python representation of Symbols |
| 4619 | |
| 4620 | @cindex symbols in python |
| 4621 | @tindex gdb.Symbol |
| 4622 | |
| 4623 | @value{GDBN} represents every variable, function and type as an |
| 4624 | entry in a symbol table. @xref{Symbols, ,Examining the Symbol Table}. |
| 4625 | Similarly, Python represents these symbols in @value{GDBN} with the |
| 4626 | @code{gdb.Symbol} object. |
| 4627 | |
| 4628 | The following symbol-related functions are available in the @code{gdb} |
| 4629 | module: |
| 4630 | |
| 4631 | @findex gdb.lookup_symbol |
| 4632 | @defun gdb.lookup_symbol (name @r{[}, block @r{[}, domain@r{]]}) |
| 4633 | This function searches for a symbol by name. The search scope can be |
| 4634 | restricted to the parameters defined in the optional domain and block |
| 4635 | arguments. |
| 4636 | |
| 4637 | @var{name} is the name of the symbol. It must be a string. The |
| 4638 | optional @var{block} argument restricts the search to symbols visible |
| 4639 | in that @var{block}. The @var{block} argument must be a |
| 4640 | @code{gdb.Block} object. If omitted, the block for the current frame |
| 4641 | is used. The optional @var{domain} argument restricts |
| 4642 | the search to the domain type. The @var{domain} argument must be a |
| 4643 | domain constant defined in the @code{gdb} module and described later |
| 4644 | in this chapter. |
| 4645 | |
| 4646 | The result is a tuple of two elements. |
| 4647 | The first element is a @code{gdb.Symbol} object or @code{None} if the symbol |
| 4648 | is not found. |
| 4649 | If the symbol is found, the second element is @code{True} if the symbol |
| 4650 | is a field of a method's object (e.g., @code{this} in C@t{++}), |
| 4651 | otherwise it is @code{False}. |
| 4652 | If the symbol is not found, the second element is @code{False}. |
| 4653 | @end defun |
| 4654 | |
| 4655 | @findex gdb.lookup_global_symbol |
| 4656 | @defun gdb.lookup_global_symbol (name @r{[}, domain@r{]}) |
| 4657 | This function searches for a global symbol by name. |
| 4658 | The search scope can be restricted to by the domain argument. |
| 4659 | |
| 4660 | @var{name} is the name of the symbol. It must be a string. |
| 4661 | The optional @var{domain} argument restricts the search to the domain type. |
| 4662 | The @var{domain} argument must be a domain constant defined in the @code{gdb} |
| 4663 | module and described later in this chapter. |
| 4664 | |
| 4665 | The result is a @code{gdb.Symbol} object or @code{None} if the symbol |
| 4666 | is not found. |
| 4667 | @end defun |
| 4668 | |
| 4669 | A @code{gdb.Symbol} object has the following attributes: |
| 4670 | |
| 4671 | @defvar Symbol.type |
| 4672 | The type of the symbol or @code{None} if no type is recorded. |
| 4673 | This attribute is represented as a @code{gdb.Type} object. |
| 4674 | @xref{Types In Python}. This attribute is not writable. |
| 4675 | @end defvar |
| 4676 | |
| 4677 | @defvar Symbol.symtab |
| 4678 | The symbol table in which the symbol appears. This attribute is |
| 4679 | represented as a @code{gdb.Symtab} object. @xref{Symbol Tables In |
| 4680 | Python}. This attribute is not writable. |
| 4681 | @end defvar |
| 4682 | |
| 4683 | @defvar Symbol.line |
| 4684 | The line number in the source code at which the symbol was defined. |
| 4685 | This is an integer. |
| 4686 | @end defvar |
| 4687 | |
| 4688 | @defvar Symbol.name |
| 4689 | The name of the symbol as a string. This attribute is not writable. |
| 4690 | @end defvar |
| 4691 | |
| 4692 | @defvar Symbol.linkage_name |
| 4693 | The name of the symbol, as used by the linker (i.e., may be mangled). |
| 4694 | This attribute is not writable. |
| 4695 | @end defvar |
| 4696 | |
| 4697 | @defvar Symbol.print_name |
| 4698 | The name of the symbol in a form suitable for output. This is either |
| 4699 | @code{name} or @code{linkage_name}, depending on whether the user |
| 4700 | asked @value{GDBN} to display demangled or mangled names. |
| 4701 | @end defvar |
| 4702 | |
| 4703 | @defvar Symbol.addr_class |
| 4704 | The address class of the symbol. This classifies how to find the value |
| 4705 | of a symbol. Each address class is a constant defined in the |
| 4706 | @code{gdb} module and described later in this chapter. |
| 4707 | @end defvar |
| 4708 | |
| 4709 | @defvar Symbol.needs_frame |
| 4710 | This is @code{True} if evaluating this symbol's value requires a frame |
| 4711 | (@pxref{Frames In Python}) and @code{False} otherwise. Typically, |
| 4712 | local variables will require a frame, but other symbols will not. |
| 4713 | @end defvar |
| 4714 | |
| 4715 | @defvar Symbol.is_argument |
| 4716 | @code{True} if the symbol is an argument of a function. |
| 4717 | @end defvar |
| 4718 | |
| 4719 | @defvar Symbol.is_constant |
| 4720 | @code{True} if the symbol is a constant. |
| 4721 | @end defvar |
| 4722 | |
| 4723 | @defvar Symbol.is_function |
| 4724 | @code{True} if the symbol is a function or a method. |
| 4725 | @end defvar |
| 4726 | |
| 4727 | @defvar Symbol.is_variable |
| 4728 | @code{True} if the symbol is a variable. |
| 4729 | @end defvar |
| 4730 | |
| 4731 | A @code{gdb.Symbol} object has the following methods: |
| 4732 | |
| 4733 | @defun Symbol.is_valid () |
| 4734 | Returns @code{True} if the @code{gdb.Symbol} object is valid, |
| 4735 | @code{False} if not. A @code{gdb.Symbol} object can become invalid if |
| 4736 | the symbol it refers to does not exist in @value{GDBN} any longer. |
| 4737 | All other @code{gdb.Symbol} methods will throw an exception if it is |
| 4738 | invalid at the time the method is called. |
| 4739 | @end defun |
| 4740 | |
| 4741 | @defun Symbol.value (@r{[}frame@r{]}) |
| 4742 | Compute the value of the symbol, as a @code{gdb.Value}. For |
| 4743 | functions, this computes the address of the function, cast to the |
| 4744 | appropriate type. If the symbol requires a frame in order to compute |
| 4745 | its value, then @var{frame} must be given. If @var{frame} is not |
| 4746 | given, or if @var{frame} is invalid, then this method will throw an |
| 4747 | exception. |
| 4748 | @end defun |
| 4749 | |
| 4750 | The available domain categories in @code{gdb.Symbol} are represented |
| 4751 | as constants in the @code{gdb} module: |
| 4752 | |
| 4753 | @vtable @code |
| 4754 | @vindex SYMBOL_UNDEF_DOMAIN |
| 4755 | @item gdb.SYMBOL_UNDEF_DOMAIN |
| 4756 | This is used when a domain has not been discovered or none of the |
| 4757 | following domains apply. This usually indicates an error either |
| 4758 | in the symbol information or in @value{GDBN}'s handling of symbols. |
| 4759 | |
| 4760 | @vindex SYMBOL_VAR_DOMAIN |
| 4761 | @item gdb.SYMBOL_VAR_DOMAIN |
| 4762 | This domain contains variables, function names, typedef names and enum |
| 4763 | type values. |
| 4764 | |
| 4765 | @vindex SYMBOL_STRUCT_DOMAIN |
| 4766 | @item gdb.SYMBOL_STRUCT_DOMAIN |
| 4767 | This domain holds struct, union and enum type names. |
| 4768 | |
| 4769 | @vindex SYMBOL_LABEL_DOMAIN |
| 4770 | @item gdb.SYMBOL_LABEL_DOMAIN |
| 4771 | This domain contains names of labels (for gotos). |
| 4772 | |
| 4773 | @vindex SYMBOL_VARIABLES_DOMAIN |
| 4774 | @item gdb.SYMBOL_VARIABLES_DOMAIN |
| 4775 | This domain holds a subset of the @code{SYMBOLS_VAR_DOMAIN}; it |
| 4776 | contains everything minus functions and types. |
| 4777 | |
| 4778 | @vindex SYMBOL_FUNCTIONS_DOMAIN |
| 4779 | @item gdb.SYMBOL_FUNCTIONS_DOMAIN |
| 4780 | This domain contains all functions. |
| 4781 | |
| 4782 | @vindex SYMBOL_TYPES_DOMAIN |
| 4783 | @item gdb.SYMBOL_TYPES_DOMAIN |
| 4784 | This domain contains all types. |
| 4785 | @end vtable |
| 4786 | |
| 4787 | The available address class categories in @code{gdb.Symbol} are represented |
| 4788 | as constants in the @code{gdb} module: |
| 4789 | |
| 4790 | @vtable @code |
| 4791 | @vindex SYMBOL_LOC_UNDEF |
| 4792 | @item gdb.SYMBOL_LOC_UNDEF |
| 4793 | If this is returned by address class, it indicates an error either in |
| 4794 | the symbol information or in @value{GDBN}'s handling of symbols. |
| 4795 | |
| 4796 | @vindex SYMBOL_LOC_CONST |
| 4797 | @item gdb.SYMBOL_LOC_CONST |
| 4798 | Value is constant int. |
| 4799 | |
| 4800 | @vindex SYMBOL_LOC_STATIC |
| 4801 | @item gdb.SYMBOL_LOC_STATIC |
| 4802 | Value is at a fixed address. |
| 4803 | |
| 4804 | @vindex SYMBOL_LOC_REGISTER |
| 4805 | @item gdb.SYMBOL_LOC_REGISTER |
| 4806 | Value is in a register. |
| 4807 | |
| 4808 | @vindex SYMBOL_LOC_ARG |
| 4809 | @item gdb.SYMBOL_LOC_ARG |
| 4810 | Value is an argument. This value is at the offset stored within the |
| 4811 | symbol inside the frame's argument list. |
| 4812 | |
| 4813 | @vindex SYMBOL_LOC_REF_ARG |
| 4814 | @item gdb.SYMBOL_LOC_REF_ARG |
| 4815 | Value address is stored in the frame's argument list. Just like |
| 4816 | @code{LOC_ARG} except that the value's address is stored at the |
| 4817 | offset, not the value itself. |
| 4818 | |
| 4819 | @vindex SYMBOL_LOC_REGPARM_ADDR |
| 4820 | @item gdb.SYMBOL_LOC_REGPARM_ADDR |
| 4821 | Value is a specified register. Just like @code{LOC_REGISTER} except |
| 4822 | the register holds the address of the argument instead of the argument |
| 4823 | itself. |
| 4824 | |
| 4825 | @vindex SYMBOL_LOC_LOCAL |
| 4826 | @item gdb.SYMBOL_LOC_LOCAL |
| 4827 | Value is a local variable. |
| 4828 | |
| 4829 | @vindex SYMBOL_LOC_TYPEDEF |
| 4830 | @item gdb.SYMBOL_LOC_TYPEDEF |
| 4831 | Value not used. Symbols in the domain @code{SYMBOL_STRUCT_DOMAIN} all |
| 4832 | have this class. |
| 4833 | |
| 4834 | @vindex SYMBOL_LOC_BLOCK |
| 4835 | @item gdb.SYMBOL_LOC_BLOCK |
| 4836 | Value is a block. |
| 4837 | |
| 4838 | @vindex SYMBOL_LOC_CONST_BYTES |
| 4839 | @item gdb.SYMBOL_LOC_CONST_BYTES |
| 4840 | Value is a byte-sequence. |
| 4841 | |
| 4842 | @vindex SYMBOL_LOC_UNRESOLVED |
| 4843 | @item gdb.SYMBOL_LOC_UNRESOLVED |
| 4844 | Value is at a fixed address, but the address of the variable has to be |
| 4845 | determined from the minimal symbol table whenever the variable is |
| 4846 | referenced. |
| 4847 | |
| 4848 | @vindex SYMBOL_LOC_OPTIMIZED_OUT |
| 4849 | @item gdb.SYMBOL_LOC_OPTIMIZED_OUT |
| 4850 | The value does not actually exist in the program. |
| 4851 | |
| 4852 | @vindex SYMBOL_LOC_COMPUTED |
| 4853 | @item gdb.SYMBOL_LOC_COMPUTED |
| 4854 | The value's address is a computed location. |
| 4855 | @end vtable |
| 4856 | |
| 4857 | @node Symbol Tables In Python |
| 4858 | @subsubsection Symbol table representation in Python |
| 4859 | |
| 4860 | @cindex symbol tables in python |
| 4861 | @tindex gdb.Symtab |
| 4862 | @tindex gdb.Symtab_and_line |
| 4863 | |
| 4864 | Access to symbol table data maintained by @value{GDBN} on the inferior |
| 4865 | is exposed to Python via two objects: @code{gdb.Symtab_and_line} and |
| 4866 | @code{gdb.Symtab}. Symbol table and line data for a frame is returned |
| 4867 | from the @code{find_sal} method in @code{gdb.Frame} object. |
| 4868 | @xref{Frames In Python}. |
| 4869 | |
| 4870 | For more information on @value{GDBN}'s symbol table management, see |
| 4871 | @ref{Symbols, ,Examining the Symbol Table}, for more information. |
| 4872 | |
| 4873 | A @code{gdb.Symtab_and_line} object has the following attributes: |
| 4874 | |
| 4875 | @defvar Symtab_and_line.symtab |
| 4876 | The symbol table object (@code{gdb.Symtab}) for this frame. |
| 4877 | This attribute is not writable. |
| 4878 | @end defvar |
| 4879 | |
| 4880 | @defvar Symtab_and_line.pc |
| 4881 | Indicates the start of the address range occupied by code for the |
| 4882 | current source line. This attribute is not writable. |
| 4883 | @end defvar |
| 4884 | |
| 4885 | @defvar Symtab_and_line.last |
| 4886 | Indicates the end of the address range occupied by code for the current |
| 4887 | source line. This attribute is not writable. |
| 4888 | @end defvar |
| 4889 | |
| 4890 | @defvar Symtab_and_line.line |
| 4891 | Indicates the current line number for this object. This |
| 4892 | attribute is not writable. |
| 4893 | @end defvar |
| 4894 | |
| 4895 | A @code{gdb.Symtab_and_line} object has the following methods: |
| 4896 | |
| 4897 | @defun Symtab_and_line.is_valid () |
| 4898 | Returns @code{True} if the @code{gdb.Symtab_and_line} object is valid, |
| 4899 | @code{False} if not. A @code{gdb.Symtab_and_line} object can become |
| 4900 | invalid if the Symbol table and line object it refers to does not |
| 4901 | exist in @value{GDBN} any longer. All other |
| 4902 | @code{gdb.Symtab_and_line} methods will throw an exception if it is |
| 4903 | invalid at the time the method is called. |
| 4904 | @end defun |
| 4905 | |
| 4906 | A @code{gdb.Symtab} object has the following attributes: |
| 4907 | |
| 4908 | @defvar Symtab.filename |
| 4909 | The symbol table's source filename. This attribute is not writable. |
| 4910 | @end defvar |
| 4911 | |
| 4912 | @defvar Symtab.objfile |
| 4913 | The symbol table's backing object file. @xref{Objfiles In Python}. |
| 4914 | This attribute is not writable. |
| 4915 | @end defvar |
| 4916 | |
| 4917 | @defvar Symtab.producer |
| 4918 | The name and possibly version number of the program that |
| 4919 | compiled the code in the symbol table. |
| 4920 | The contents of this string is up to the compiler. |
| 4921 | If no producer information is available then @code{None} is returned. |
| 4922 | This attribute is not writable. |
| 4923 | @end defvar |
| 4924 | |
| 4925 | A @code{gdb.Symtab} object has the following methods: |
| 4926 | |
| 4927 | @defun Symtab.is_valid () |
| 4928 | Returns @code{True} if the @code{gdb.Symtab} object is valid, |
| 4929 | @code{False} if not. A @code{gdb.Symtab} object can become invalid if |
| 4930 | the symbol table it refers to does not exist in @value{GDBN} any |
| 4931 | longer. All other @code{gdb.Symtab} methods will throw an exception |
| 4932 | if it is invalid at the time the method is called. |
| 4933 | @end defun |
| 4934 | |
| 4935 | @defun Symtab.fullname () |
| 4936 | Return the symbol table's source absolute file name. |
| 4937 | @end defun |
| 4938 | |
| 4939 | @defun Symtab.global_block () |
| 4940 | Return the global block of the underlying symbol table. |
| 4941 | @xref{Blocks In Python}. |
| 4942 | @end defun |
| 4943 | |
| 4944 | @defun Symtab.static_block () |
| 4945 | Return the static block of the underlying symbol table. |
| 4946 | @xref{Blocks In Python}. |
| 4947 | @end defun |
| 4948 | |
| 4949 | @defun Symtab.linetable () |
| 4950 | Return the line table associated with the symbol table. |
| 4951 | @xref{Line Tables In Python}. |
| 4952 | @end defun |
| 4953 | |
| 4954 | @node Line Tables In Python |
| 4955 | @subsubsection Manipulating line tables using Python |
| 4956 | |
| 4957 | @cindex line tables in python |
| 4958 | @tindex gdb.LineTable |
| 4959 | |
| 4960 | Python code can request and inspect line table information from a |
| 4961 | symbol table that is loaded in @value{GDBN}. A line table is a |
| 4962 | mapping of source lines to their executable locations in memory. To |
| 4963 | acquire the line table information for a particular symbol table, use |
| 4964 | the @code{linetable} function (@pxref{Symbol Tables In Python}). |
| 4965 | |
| 4966 | A @code{gdb.LineTable} is iterable. The iterator returns |
| 4967 | @code{LineTableEntry} objects that correspond to the source line and |
| 4968 | address for each line table entry. @code{LineTableEntry} objects have |
| 4969 | the following attributes: |
| 4970 | |
| 4971 | @defvar LineTableEntry.line |
| 4972 | The source line number for this line table entry. This number |
| 4973 | corresponds to the actual line of source. This attribute is not |
| 4974 | writable. |
| 4975 | @end defvar |
| 4976 | |
| 4977 | @defvar LineTableEntry.pc |
| 4978 | The address that is associated with the line table entry where the |
| 4979 | executable code for that source line resides in memory. This |
| 4980 | attribute is not writable. |
| 4981 | @end defvar |
| 4982 | |
| 4983 | As there can be multiple addresses for a single source line, you may |
| 4984 | receive multiple @code{LineTableEntry} objects with matching |
| 4985 | @code{line} attributes, but with different @code{pc} attributes. The |
| 4986 | iterator is sorted in ascending @code{pc} order. Here is a small |
| 4987 | example illustrating iterating over a line table. |
| 4988 | |
| 4989 | @smallexample |
| 4990 | symtab = gdb.selected_frame().find_sal().symtab |
| 4991 | linetable = symtab.linetable() |
| 4992 | for line in linetable: |
| 4993 | print "Line: "+str(line.line)+" Address: "+hex(line.pc) |
| 4994 | @end smallexample |
| 4995 | |
| 4996 | This will have the following output: |
| 4997 | |
| 4998 | @smallexample |
| 4999 | Line: 33 Address: 0x4005c8L |
| 5000 | Line: 37 Address: 0x4005caL |
| 5001 | Line: 39 Address: 0x4005d2L |
| 5002 | Line: 40 Address: 0x4005f8L |
| 5003 | Line: 42 Address: 0x4005ffL |
| 5004 | Line: 44 Address: 0x400608L |
| 5005 | Line: 42 Address: 0x40060cL |
| 5006 | Line: 45 Address: 0x400615L |
| 5007 | @end smallexample |
| 5008 | |
| 5009 | In addition to being able to iterate over a @code{LineTable}, it also |
| 5010 | has the following direct access methods: |
| 5011 | |
| 5012 | @defun LineTable.line (line) |
| 5013 | Return a Python @code{Tuple} of @code{LineTableEntry} objects for any |
| 5014 | entries in the line table for the given @var{line}, which specifies |
| 5015 | the source code line. If there are no entries for that source code |
| 5016 | @var{line}, the Python @code{None} is returned. |
| 5017 | @end defun |
| 5018 | |
| 5019 | @defun LineTable.has_line (line) |
| 5020 | Return a Python @code{Boolean} indicating whether there is an entry in |
| 5021 | the line table for this source line. Return @code{True} if an entry |
| 5022 | is found, or @code{False} if not. |
| 5023 | @end defun |
| 5024 | |
| 5025 | @defun LineTable.source_lines () |
| 5026 | Return a Python @code{List} of the source line numbers in the symbol |
| 5027 | table. Only lines with executable code locations are returned. The |
| 5028 | contents of the @code{List} will just be the source line entries |
| 5029 | represented as Python @code{Long} values. |
| 5030 | @end defun |
| 5031 | |
| 5032 | @node Breakpoints In Python |
| 5033 | @subsubsection Manipulating breakpoints using Python |
| 5034 | |
| 5035 | @cindex breakpoints in python |
| 5036 | @tindex gdb.Breakpoint |
| 5037 | |
| 5038 | Python code can manipulate breakpoints via the @code{gdb.Breakpoint} |
| 5039 | class. |
| 5040 | |
| 5041 | A breakpoint can be created using one of the two forms of the |
| 5042 | @code{gdb.Breakpoint} constructor. The first one accepts a string |
| 5043 | like one would pass to the @code{break} |
| 5044 | (@pxref{Set Breaks,,Setting Breakpoints}) and @code{watch} |
| 5045 | (@pxref{Set Watchpoints, , Setting Watchpoints}) commands, and can be used to |
| 5046 | create both breakpoints and watchpoints. The second accepts separate Python |
| 5047 | arguments similar to @ref{Explicit Locations}, and can only be used to create |
| 5048 | breakpoints. |
| 5049 | |
| 5050 | @defun Breakpoint.__init__ (spec @r{[}, type @r{][}, wp_class @r{][}, internal @r{][}, temporary @r{][}, qualified @r{]}) |
| 5051 | Create a new breakpoint according to @var{spec}, which is a string naming the |
| 5052 | location of a breakpoint, or an expression that defines a watchpoint. The |
| 5053 | string should describe a location in a format recognized by the @code{break} |
| 5054 | command (@pxref{Set Breaks,,Setting Breakpoints}) or, in the case of a |
| 5055 | watchpoint, by the @code{watch} command |
| 5056 | (@pxref{Set Watchpoints, , Setting Watchpoints}). |
| 5057 | |
| 5058 | The optional @var{type} argument specifies the type of the breakpoint to create, |
| 5059 | as defined below. |
| 5060 | |
| 5061 | The optional @var{wp_class} argument defines the class of watchpoint to create, |
| 5062 | if @var{type} is @code{gdb.BP_WATCHPOINT}. If @var{wp_class} is omitted, it |
| 5063 | defaults to @code{gdb.WP_WRITE}. |
| 5064 | |
| 5065 | The optional @var{internal} argument allows the breakpoint to become invisible |
| 5066 | to the user. The breakpoint will neither be reported when created, nor will it |
| 5067 | be listed in the output from @code{info breakpoints} (but will be listed with |
| 5068 | the @code{maint info breakpoints} command). |
| 5069 | |
| 5070 | The optional @var{temporary} argument makes the breakpoint a temporary |
| 5071 | breakpoint. Temporary breakpoints are deleted after they have been hit. Any |
| 5072 | further access to the Python breakpoint after it has been hit will result in a |
| 5073 | runtime error (as that breakpoint has now been automatically deleted). |
| 5074 | |
| 5075 | The optional @var{qualified} argument is a boolean that allows interpreting |
| 5076 | the function passed in @code{spec} as a fully-qualified name. It is equivalent |
| 5077 | to @code{break}'s @code{-qualified} flag (@pxref{Linespec Locations} and |
| 5078 | @ref{Explicit Locations}). |
| 5079 | |
| 5080 | @end defun |
| 5081 | |
| 5082 | @defun Breakpoint.__init__ (@r{[} source @r{][}, function @r{][}, label @r{][}, line @r{]}, @r{][} internal @r{][}, temporary @r{][}, qualified @r{]}) |
| 5083 | This second form of creating a new breakpoint specifies the explicit |
| 5084 | location (@pxref{Explicit Locations}) using keywords. The new breakpoint will |
| 5085 | be created in the specified source file @var{source}, at the specified |
| 5086 | @var{function}, @var{label} and @var{line}. |
| 5087 | |
| 5088 | @var{internal}, @var{temporary} and @var{qualified} have the same usage as |
| 5089 | explained previously. |
| 5090 | @end defun |
| 5091 | |
| 5092 | The available types are represented by constants defined in the @code{gdb} |
| 5093 | module: |
| 5094 | |
| 5095 | @vtable @code |
| 5096 | @vindex BP_BREAKPOINT |
| 5097 | @item gdb.BP_BREAKPOINT |
| 5098 | Normal code breakpoint. |
| 5099 | |
| 5100 | @vindex BP_WATCHPOINT |
| 5101 | @item gdb.BP_WATCHPOINT |
| 5102 | Watchpoint breakpoint. |
| 5103 | |
| 5104 | @vindex BP_HARDWARE_WATCHPOINT |
| 5105 | @item gdb.BP_HARDWARE_WATCHPOINT |
| 5106 | Hardware assisted watchpoint. |
| 5107 | |
| 5108 | @vindex BP_READ_WATCHPOINT |
| 5109 | @item gdb.BP_READ_WATCHPOINT |
| 5110 | Hardware assisted read watchpoint. |
| 5111 | |
| 5112 | @vindex BP_ACCESS_WATCHPOINT |
| 5113 | @item gdb.BP_ACCESS_WATCHPOINT |
| 5114 | Hardware assisted access watchpoint. |
| 5115 | @end vtable |
| 5116 | |
| 5117 | The available watchpoint types represented by constants are defined in the |
| 5118 | @code{gdb} module: |
| 5119 | |
| 5120 | @vtable @code |
| 5121 | @vindex WP_READ |
| 5122 | @item gdb.WP_READ |
| 5123 | Read only watchpoint. |
| 5124 | |
| 5125 | @vindex WP_WRITE |
| 5126 | @item gdb.WP_WRITE |
| 5127 | Write only watchpoint. |
| 5128 | |
| 5129 | @vindex WP_ACCESS |
| 5130 | @item gdb.WP_ACCESS |
| 5131 | Read/Write watchpoint. |
| 5132 | @end vtable |
| 5133 | |
| 5134 | @defun Breakpoint.stop (self) |
| 5135 | The @code{gdb.Breakpoint} class can be sub-classed and, in |
| 5136 | particular, you may choose to implement the @code{stop} method. |
| 5137 | If this method is defined in a sub-class of @code{gdb.Breakpoint}, |
| 5138 | it will be called when the inferior reaches any location of a |
| 5139 | breakpoint which instantiates that sub-class. If the method returns |
| 5140 | @code{True}, the inferior will be stopped at the location of the |
| 5141 | breakpoint, otherwise the inferior will continue. |
| 5142 | |
| 5143 | If there are multiple breakpoints at the same location with a |
| 5144 | @code{stop} method, each one will be called regardless of the |
| 5145 | return status of the previous. This ensures that all @code{stop} |
| 5146 | methods have a chance to execute at that location. In this scenario |
| 5147 | if one of the methods returns @code{True} but the others return |
| 5148 | @code{False}, the inferior will still be stopped. |
| 5149 | |
| 5150 | You should not alter the execution state of the inferior (i.e.@:, step, |
| 5151 | next, etc.), alter the current frame context (i.e.@:, change the current |
| 5152 | active frame), or alter, add or delete any breakpoint. As a general |
| 5153 | rule, you should not alter any data within @value{GDBN} or the inferior |
| 5154 | at this time. |
| 5155 | |
| 5156 | Example @code{stop} implementation: |
| 5157 | |
| 5158 | @smallexample |
| 5159 | class MyBreakpoint (gdb.Breakpoint): |
| 5160 | def stop (self): |
| 5161 | inf_val = gdb.parse_and_eval("foo") |
| 5162 | if inf_val == 3: |
| 5163 | return True |
| 5164 | return False |
| 5165 | @end smallexample |
| 5166 | @end defun |
| 5167 | |
| 5168 | @defun Breakpoint.is_valid () |
| 5169 | Return @code{True} if this @code{Breakpoint} object is valid, |
| 5170 | @code{False} otherwise. A @code{Breakpoint} object can become invalid |
| 5171 | if the user deletes the breakpoint. In this case, the object still |
| 5172 | exists, but the underlying breakpoint does not. In the cases of |
| 5173 | watchpoint scope, the watchpoint remains valid even if execution of the |
| 5174 | inferior leaves the scope of that watchpoint. |
| 5175 | @end defun |
| 5176 | |
| 5177 | @defun Breakpoint.delete () |
| 5178 | Permanently deletes the @value{GDBN} breakpoint. This also |
| 5179 | invalidates the Python @code{Breakpoint} object. Any further access |
| 5180 | to this object's attributes or methods will raise an error. |
| 5181 | @end defun |
| 5182 | |
| 5183 | @defvar Breakpoint.enabled |
| 5184 | This attribute is @code{True} if the breakpoint is enabled, and |
| 5185 | @code{False} otherwise. This attribute is writable. You can use it to enable |
| 5186 | or disable the breakpoint. |
| 5187 | @end defvar |
| 5188 | |
| 5189 | @defvar Breakpoint.silent |
| 5190 | This attribute is @code{True} if the breakpoint is silent, and |
| 5191 | @code{False} otherwise. This attribute is writable. |
| 5192 | |
| 5193 | Note that a breakpoint can also be silent if it has commands and the |
| 5194 | first command is @code{silent}. This is not reported by the |
| 5195 | @code{silent} attribute. |
| 5196 | @end defvar |
| 5197 | |
| 5198 | @defvar Breakpoint.pending |
| 5199 | This attribute is @code{True} if the breakpoint is pending, and |
| 5200 | @code{False} otherwise. @xref{Set Breaks}. This attribute is |
| 5201 | read-only. |
| 5202 | @end defvar |
| 5203 | |
| 5204 | @anchor{python_breakpoint_thread} |
| 5205 | @defvar Breakpoint.thread |
| 5206 | If the breakpoint is thread-specific, this attribute holds the |
| 5207 | thread's global id. If the breakpoint is not thread-specific, this |
| 5208 | attribute is @code{None}. This attribute is writable. |
| 5209 | @end defvar |
| 5210 | |
| 5211 | @defvar Breakpoint.task |
| 5212 | If the breakpoint is Ada task-specific, this attribute holds the Ada task |
| 5213 | id. If the breakpoint is not task-specific (or the underlying |
| 5214 | language is not Ada), this attribute is @code{None}. This attribute |
| 5215 | is writable. |
| 5216 | @end defvar |
| 5217 | |
| 5218 | @defvar Breakpoint.ignore_count |
| 5219 | This attribute holds the ignore count for the breakpoint, an integer. |
| 5220 | This attribute is writable. |
| 5221 | @end defvar |
| 5222 | |
| 5223 | @defvar Breakpoint.number |
| 5224 | This attribute holds the breakpoint's number --- the identifier used by |
| 5225 | the user to manipulate the breakpoint. This attribute is not writable. |
| 5226 | @end defvar |
| 5227 | |
| 5228 | @defvar Breakpoint.type |
| 5229 | This attribute holds the breakpoint's type --- the identifier used to |
| 5230 | determine the actual breakpoint type or use-case. This attribute is not |
| 5231 | writable. |
| 5232 | @end defvar |
| 5233 | |
| 5234 | @defvar Breakpoint.visible |
| 5235 | This attribute tells whether the breakpoint is visible to the user |
| 5236 | when set, or when the @samp{info breakpoints} command is run. This |
| 5237 | attribute is not writable. |
| 5238 | @end defvar |
| 5239 | |
| 5240 | @defvar Breakpoint.temporary |
| 5241 | This attribute indicates whether the breakpoint was created as a |
| 5242 | temporary breakpoint. Temporary breakpoints are automatically deleted |
| 5243 | after that breakpoint has been hit. Access to this attribute, and all |
| 5244 | other attributes and functions other than the @code{is_valid} |
| 5245 | function, will result in an error after the breakpoint has been hit |
| 5246 | (as it has been automatically deleted). This attribute is not |
| 5247 | writable. |
| 5248 | @end defvar |
| 5249 | |
| 5250 | @defvar Breakpoint.hit_count |
| 5251 | This attribute holds the hit count for the breakpoint, an integer. |
| 5252 | This attribute is writable, but currently it can only be set to zero. |
| 5253 | @end defvar |
| 5254 | |
| 5255 | @defvar Breakpoint.location |
| 5256 | This attribute holds the location of the breakpoint, as specified by |
| 5257 | the user. It is a string. If the breakpoint does not have a location |
| 5258 | (that is, it is a watchpoint) the attribute's value is @code{None}. This |
| 5259 | attribute is not writable. |
| 5260 | @end defvar |
| 5261 | |
| 5262 | @defvar Breakpoint.expression |
| 5263 | This attribute holds a breakpoint expression, as specified by |
| 5264 | the user. It is a string. If the breakpoint does not have an |
| 5265 | expression (the breakpoint is not a watchpoint) the attribute's value |
| 5266 | is @code{None}. This attribute is not writable. |
| 5267 | @end defvar |
| 5268 | |
| 5269 | @defvar Breakpoint.condition |
| 5270 | This attribute holds the condition of the breakpoint, as specified by |
| 5271 | the user. It is a string. If there is no condition, this attribute's |
| 5272 | value is @code{None}. This attribute is writable. |
| 5273 | @end defvar |
| 5274 | |
| 5275 | @defvar Breakpoint.commands |
| 5276 | This attribute holds the commands attached to the breakpoint. If |
| 5277 | there are commands, this attribute's value is a string holding all the |
| 5278 | commands, separated by newlines. If there are no commands, this |
| 5279 | attribute is @code{None}. This attribute is writable. |
| 5280 | @end defvar |
| 5281 | |
| 5282 | @node Finish Breakpoints in Python |
| 5283 | @subsubsection Finish Breakpoints |
| 5284 | |
| 5285 | @cindex python finish breakpoints |
| 5286 | @tindex gdb.FinishBreakpoint |
| 5287 | |
| 5288 | A finish breakpoint is a temporary breakpoint set at the return address of |
| 5289 | a frame, based on the @code{finish} command. @code{gdb.FinishBreakpoint} |
| 5290 | extends @code{gdb.Breakpoint}. The underlying breakpoint will be disabled |
| 5291 | and deleted when the execution will run out of the breakpoint scope (i.e.@: |
| 5292 | @code{Breakpoint.stop} or @code{FinishBreakpoint.out_of_scope} triggered). |
| 5293 | Finish breakpoints are thread specific and must be create with the right |
| 5294 | thread selected. |
| 5295 | |
| 5296 | @defun FinishBreakpoint.__init__ (@r{[}frame@r{]} @r{[}, internal@r{]}) |
| 5297 | Create a finish breakpoint at the return address of the @code{gdb.Frame} |
| 5298 | object @var{frame}. If @var{frame} is not provided, this defaults to the |
| 5299 | newest frame. The optional @var{internal} argument allows the breakpoint to |
| 5300 | become invisible to the user. @xref{Breakpoints In Python}, for further |
| 5301 | details about this argument. |
| 5302 | @end defun |
| 5303 | |
| 5304 | @defun FinishBreakpoint.out_of_scope (self) |
| 5305 | In some circumstances (e.g.@: @code{longjmp}, C@t{++} exceptions, @value{GDBN} |
| 5306 | @code{return} command, @dots{}), a function may not properly terminate, and |
| 5307 | thus never hit the finish breakpoint. When @value{GDBN} notices such a |
| 5308 | situation, the @code{out_of_scope} callback will be triggered. |
| 5309 | |
| 5310 | You may want to sub-class @code{gdb.FinishBreakpoint} and override this |
| 5311 | method: |
| 5312 | |
| 5313 | @smallexample |
| 5314 | class MyFinishBreakpoint (gdb.FinishBreakpoint) |
| 5315 | def stop (self): |
| 5316 | print "normal finish" |
| 5317 | return True |
| 5318 | |
| 5319 | def out_of_scope (): |
| 5320 | print "abnormal finish" |
| 5321 | @end smallexample |
| 5322 | @end defun |
| 5323 | |
| 5324 | @defvar FinishBreakpoint.return_value |
| 5325 | When @value{GDBN} is stopped at a finish breakpoint and the frame |
| 5326 | used to build the @code{gdb.FinishBreakpoint} object had debug symbols, this |
| 5327 | attribute will contain a @code{gdb.Value} object corresponding to the return |
| 5328 | value of the function. The value will be @code{None} if the function return |
| 5329 | type is @code{void} or if the return value was not computable. This attribute |
| 5330 | is not writable. |
| 5331 | @end defvar |
| 5332 | |
| 5333 | @node Lazy Strings In Python |
| 5334 | @subsubsection Python representation of lazy strings |
| 5335 | |
| 5336 | @cindex lazy strings in python |
| 5337 | @tindex gdb.LazyString |
| 5338 | |
| 5339 | A @dfn{lazy string} is a string whose contents is not retrieved or |
| 5340 | encoded until it is needed. |
| 5341 | |
| 5342 | A @code{gdb.LazyString} is represented in @value{GDBN} as an |
| 5343 | @code{address} that points to a region of memory, an @code{encoding} |
| 5344 | that will be used to encode that region of memory, and a @code{length} |
| 5345 | to delimit the region of memory that represents the string. The |
| 5346 | difference between a @code{gdb.LazyString} and a string wrapped within |
| 5347 | a @code{gdb.Value} is that a @code{gdb.LazyString} will be treated |
| 5348 | differently by @value{GDBN} when printing. A @code{gdb.LazyString} is |
| 5349 | retrieved and encoded during printing, while a @code{gdb.Value} |
| 5350 | wrapping a string is immediately retrieved and encoded on creation. |
| 5351 | |
| 5352 | A @code{gdb.LazyString} object has the following functions: |
| 5353 | |
| 5354 | @defun LazyString.value () |
| 5355 | Convert the @code{gdb.LazyString} to a @code{gdb.Value}. This value |
| 5356 | will point to the string in memory, but will lose all the delayed |
| 5357 | retrieval, encoding and handling that @value{GDBN} applies to a |
| 5358 | @code{gdb.LazyString}. |
| 5359 | @end defun |
| 5360 | |
| 5361 | @defvar LazyString.address |
| 5362 | This attribute holds the address of the string. This attribute is not |
| 5363 | writable. |
| 5364 | @end defvar |
| 5365 | |
| 5366 | @defvar LazyString.length |
| 5367 | This attribute holds the length of the string in characters. If the |
| 5368 | length is -1, then the string will be fetched and encoded up to the |
| 5369 | first null of appropriate width. This attribute is not writable. |
| 5370 | @end defvar |
| 5371 | |
| 5372 | @defvar LazyString.encoding |
| 5373 | This attribute holds the encoding that will be applied to the string |
| 5374 | when the string is printed by @value{GDBN}. If the encoding is not |
| 5375 | set, or contains an empty string, then @value{GDBN} will select the |
| 5376 | most appropriate encoding when the string is printed. This attribute |
| 5377 | is not writable. |
| 5378 | @end defvar |
| 5379 | |
| 5380 | @defvar LazyString.type |
| 5381 | This attribute holds the type that is represented by the lazy string's |
| 5382 | type. For a lazy string this is a pointer or array type. To |
| 5383 | resolve this to the lazy string's character type, use the type's |
| 5384 | @code{target} method. @xref{Types In Python}. This attribute is not |
| 5385 | writable. |
| 5386 | @end defvar |
| 5387 | |
| 5388 | @node Architectures In Python |
| 5389 | @subsubsection Python representation of architectures |
| 5390 | @cindex Python architectures |
| 5391 | |
| 5392 | @value{GDBN} uses architecture specific parameters and artifacts in a |
| 5393 | number of its various computations. An architecture is represented |
| 5394 | by an instance of the @code{gdb.Architecture} class. |
| 5395 | |
| 5396 | A @code{gdb.Architecture} class has the following methods: |
| 5397 | |
| 5398 | @defun Architecture.name () |
| 5399 | Return the name (string value) of the architecture. |
| 5400 | @end defun |
| 5401 | |
| 5402 | @defun Architecture.disassemble (@var{start_pc} @r{[}, @var{end_pc} @r{[}, @var{count}@r{]]}) |
| 5403 | Return a list of disassembled instructions starting from the memory |
| 5404 | address @var{start_pc}. The optional arguments @var{end_pc} and |
| 5405 | @var{count} determine the number of instructions in the returned list. |
| 5406 | If both the optional arguments @var{end_pc} and @var{count} are |
| 5407 | specified, then a list of at most @var{count} disassembled instructions |
| 5408 | whose start address falls in the closed memory address interval from |
| 5409 | @var{start_pc} to @var{end_pc} are returned. If @var{end_pc} is not |
| 5410 | specified, but @var{count} is specified, then @var{count} number of |
| 5411 | instructions starting from the address @var{start_pc} are returned. If |
| 5412 | @var{count} is not specified but @var{end_pc} is specified, then all |
| 5413 | instructions whose start address falls in the closed memory address |
| 5414 | interval from @var{start_pc} to @var{end_pc} are returned. If neither |
| 5415 | @var{end_pc} nor @var{count} are specified, then a single instruction at |
| 5416 | @var{start_pc} is returned. For all of these cases, each element of the |
| 5417 | returned list is a Python @code{dict} with the following string keys: |
| 5418 | |
| 5419 | @table @code |
| 5420 | |
| 5421 | @item addr |
| 5422 | The value corresponding to this key is a Python long integer capturing |
| 5423 | the memory address of the instruction. |
| 5424 | |
| 5425 | @item asm |
| 5426 | The value corresponding to this key is a string value which represents |
| 5427 | the instruction with assembly language mnemonics. The assembly |
| 5428 | language flavor used is the same as that specified by the current CLI |
| 5429 | variable @code{disassembly-flavor}. @xref{Machine Code}. |
| 5430 | |
| 5431 | @item length |
| 5432 | The value corresponding to this key is the length (integer value) of the |
| 5433 | instruction in bytes. |
| 5434 | |
| 5435 | @end table |
| 5436 | @end defun |
| 5437 | |
| 5438 | @node Python Auto-loading |
| 5439 | @subsection Python Auto-loading |
| 5440 | @cindex Python auto-loading |
| 5441 | |
| 5442 | When a new object file is read (for example, due to the @code{file} |
| 5443 | command, or because the inferior has loaded a shared library), |
| 5444 | @value{GDBN} will look for Python support scripts in several ways: |
| 5445 | @file{@var{objfile}-gdb.py} and @code{.debug_gdb_scripts} section. |
| 5446 | @xref{Auto-loading extensions}. |
| 5447 | |
| 5448 | The auto-loading feature is useful for supplying application-specific |
| 5449 | debugging commands and scripts. |
| 5450 | |
| 5451 | Auto-loading can be enabled or disabled, |
| 5452 | and the list of auto-loaded scripts can be printed. |
| 5453 | |
| 5454 | @table @code |
| 5455 | @anchor{set auto-load python-scripts} |
| 5456 | @kindex set auto-load python-scripts |
| 5457 | @item set auto-load python-scripts [on|off] |
| 5458 | Enable or disable the auto-loading of Python scripts. |
| 5459 | |
| 5460 | @anchor{show auto-load python-scripts} |
| 5461 | @kindex show auto-load python-scripts |
| 5462 | @item show auto-load python-scripts |
| 5463 | Show whether auto-loading of Python scripts is enabled or disabled. |
| 5464 | |
| 5465 | @anchor{info auto-load python-scripts} |
| 5466 | @kindex info auto-load python-scripts |
| 5467 | @cindex print list of auto-loaded Python scripts |
| 5468 | @item info auto-load python-scripts [@var{regexp}] |
| 5469 | Print the list of all Python scripts that @value{GDBN} auto-loaded. |
| 5470 | |
| 5471 | Also printed is the list of Python scripts that were mentioned in |
| 5472 | the @code{.debug_gdb_scripts} section and were either not found |
| 5473 | (@pxref{dotdebug_gdb_scripts section}) or were not auto-loaded due to |
| 5474 | @code{auto-load safe-path} rejection (@pxref{Auto-loading}). |
| 5475 | This is useful because their names are not printed when @value{GDBN} |
| 5476 | tries to load them and fails. There may be many of them, and printing |
| 5477 | an error message for each one is problematic. |
| 5478 | |
| 5479 | If @var{regexp} is supplied only Python scripts with matching names are printed. |
| 5480 | |
| 5481 | Example: |
| 5482 | |
| 5483 | @smallexample |
| 5484 | (gdb) info auto-load python-scripts |
| 5485 | Loaded Script |
| 5486 | Yes py-section-script.py |
| 5487 | full name: /tmp/py-section-script.py |
| 5488 | No my-foo-pretty-printers.py |
| 5489 | @end smallexample |
| 5490 | @end table |
| 5491 | |
| 5492 | When reading an auto-loaded file or script, @value{GDBN} sets the |
| 5493 | @dfn{current objfile}. This is available via the @code{gdb.current_objfile} |
| 5494 | function (@pxref{Objfiles In Python}). This can be useful for |
| 5495 | registering objfile-specific pretty-printers and frame-filters. |
| 5496 | |
| 5497 | @node Python modules |
| 5498 | @subsection Python modules |
| 5499 | @cindex python modules |
| 5500 | |
| 5501 | @value{GDBN} comes with several modules to assist writing Python code. |
| 5502 | |
| 5503 | @menu |
| 5504 | * gdb.printing:: Building and registering pretty-printers. |
| 5505 | * gdb.types:: Utilities for working with types. |
| 5506 | * gdb.prompt:: Utilities for prompt value substitution. |
| 5507 | @end menu |
| 5508 | |
| 5509 | @node gdb.printing |
| 5510 | @subsubsection gdb.printing |
| 5511 | @cindex gdb.printing |
| 5512 | |
| 5513 | This module provides a collection of utilities for working with |
| 5514 | pretty-printers. |
| 5515 | |
| 5516 | @table @code |
| 5517 | @item PrettyPrinter (@var{name}, @var{subprinters}=None) |
| 5518 | This class specifies the API that makes @samp{info pretty-printer}, |
| 5519 | @samp{enable pretty-printer} and @samp{disable pretty-printer} work. |
| 5520 | Pretty-printers should generally inherit from this class. |
| 5521 | |
| 5522 | @item SubPrettyPrinter (@var{name}) |
| 5523 | For printers that handle multiple types, this class specifies the |
| 5524 | corresponding API for the subprinters. |
| 5525 | |
| 5526 | @item RegexpCollectionPrettyPrinter (@var{name}) |
| 5527 | Utility class for handling multiple printers, all recognized via |
| 5528 | regular expressions. |
| 5529 | @xref{Writing a Pretty-Printer}, for an example. |
| 5530 | |
| 5531 | @item FlagEnumerationPrinter (@var{name}) |
| 5532 | A pretty-printer which handles printing of @code{enum} values. Unlike |
| 5533 | @value{GDBN}'s built-in @code{enum} printing, this printer attempts to |
| 5534 | work properly when there is some overlap between the enumeration |
| 5535 | constants. The argument @var{name} is the name of the printer and |
| 5536 | also the name of the @code{enum} type to look up. |
| 5537 | |
| 5538 | @item register_pretty_printer (@var{obj}, @var{printer}, @var{replace}=False) |
| 5539 | Register @var{printer} with the pretty-printer list of @var{obj}. |
| 5540 | If @var{replace} is @code{True} then any existing copy of the printer |
| 5541 | is replaced. Otherwise a @code{RuntimeError} exception is raised |
| 5542 | if a printer with the same name already exists. |
| 5543 | @end table |
| 5544 | |
| 5545 | @node gdb.types |
| 5546 | @subsubsection gdb.types |
| 5547 | @cindex gdb.types |
| 5548 | |
| 5549 | This module provides a collection of utilities for working with |
| 5550 | @code{gdb.Type} objects. |
| 5551 | |
| 5552 | @table @code |
| 5553 | @item get_basic_type (@var{type}) |
| 5554 | Return @var{type} with const and volatile qualifiers stripped, |
| 5555 | and with typedefs and C@t{++} references converted to the underlying type. |
| 5556 | |
| 5557 | C@t{++} example: |
| 5558 | |
| 5559 | @smallexample |
| 5560 | typedef const int const_int; |
| 5561 | const_int foo (3); |
| 5562 | const_int& foo_ref (foo); |
| 5563 | int main () @{ return 0; @} |
| 5564 | @end smallexample |
| 5565 | |
| 5566 | Then in gdb: |
| 5567 | |
| 5568 | @smallexample |
| 5569 | (gdb) start |
| 5570 | (gdb) python import gdb.types |
| 5571 | (gdb) python foo_ref = gdb.parse_and_eval("foo_ref") |
| 5572 | (gdb) python print gdb.types.get_basic_type(foo_ref.type) |
| 5573 | int |
| 5574 | @end smallexample |
| 5575 | |
| 5576 | @item has_field (@var{type}, @var{field}) |
| 5577 | Return @code{True} if @var{type}, assumed to be a type with fields |
| 5578 | (e.g., a structure or union), has field @var{field}. |
| 5579 | |
| 5580 | @item make_enum_dict (@var{enum_type}) |
| 5581 | Return a Python @code{dictionary} type produced from @var{enum_type}. |
| 5582 | |
| 5583 | @item deep_items (@var{type}) |
| 5584 | Returns a Python iterator similar to the standard |
| 5585 | @code{gdb.Type.iteritems} method, except that the iterator returned |
| 5586 | by @code{deep_items} will recursively traverse anonymous struct or |
| 5587 | union fields. For example: |
| 5588 | |
| 5589 | @smallexample |
| 5590 | struct A |
| 5591 | @{ |
| 5592 | int a; |
| 5593 | union @{ |
| 5594 | int b0; |
| 5595 | int b1; |
| 5596 | @}; |
| 5597 | @}; |
| 5598 | @end smallexample |
| 5599 | |
| 5600 | @noindent |
| 5601 | Then in @value{GDBN}: |
| 5602 | @smallexample |
| 5603 | (@value{GDBP}) python import gdb.types |
| 5604 | (@value{GDBP}) python struct_a = gdb.lookup_type("struct A") |
| 5605 | (@value{GDBP}) python print struct_a.keys () |
| 5606 | @{['a', '']@} |
| 5607 | (@value{GDBP}) python print [k for k,v in gdb.types.deep_items(struct_a)] |
| 5608 | @{['a', 'b0', 'b1']@} |
| 5609 | @end smallexample |
| 5610 | |
| 5611 | @item get_type_recognizers () |
| 5612 | Return a list of the enabled type recognizers for the current context. |
| 5613 | This is called by @value{GDBN} during the type-printing process |
| 5614 | (@pxref{Type Printing API}). |
| 5615 | |
| 5616 | @item apply_type_recognizers (recognizers, type_obj) |
| 5617 | Apply the type recognizers, @var{recognizers}, to the type object |
| 5618 | @var{type_obj}. If any recognizer returns a string, return that |
| 5619 | string. Otherwise, return @code{None}. This is called by |
| 5620 | @value{GDBN} during the type-printing process (@pxref{Type Printing |
| 5621 | API}). |
| 5622 | |
| 5623 | @item register_type_printer (locus, printer) |
| 5624 | This is a convenience function to register a type printer |
| 5625 | @var{printer}. The printer must implement the type printer protocol. |
| 5626 | The @var{locus} argument is either a @code{gdb.Objfile}, in which case |
| 5627 | the printer is registered with that objfile; a @code{gdb.Progspace}, |
| 5628 | in which case the printer is registered with that progspace; or |
| 5629 | @code{None}, in which case the printer is registered globally. |
| 5630 | |
| 5631 | @item TypePrinter |
| 5632 | This is a base class that implements the type printer protocol. Type |
| 5633 | printers are encouraged, but not required, to derive from this class. |
| 5634 | It defines a constructor: |
| 5635 | |
| 5636 | @defmethod TypePrinter __init__ (self, name) |
| 5637 | Initialize the type printer with the given name. The new printer |
| 5638 | starts in the enabled state. |
| 5639 | @end defmethod |
| 5640 | |
| 5641 | @end table |
| 5642 | |
| 5643 | @node gdb.prompt |
| 5644 | @subsubsection gdb.prompt |
| 5645 | @cindex gdb.prompt |
| 5646 | |
| 5647 | This module provides a method for prompt value-substitution. |
| 5648 | |
| 5649 | @table @code |
| 5650 | @item substitute_prompt (@var{string}) |
| 5651 | Return @var{string} with escape sequences substituted by values. Some |
| 5652 | escape sequences take arguments. You can specify arguments inside |
| 5653 | ``@{@}'' immediately following the escape sequence. |
| 5654 | |
| 5655 | The escape sequences you can pass to this function are: |
| 5656 | |
| 5657 | @table @code |
| 5658 | @item \\ |
| 5659 | Substitute a backslash. |
| 5660 | @item \e |
| 5661 | Substitute an ESC character. |
| 5662 | @item \f |
| 5663 | Substitute the selected frame; an argument names a frame parameter. |
| 5664 | @item \n |
| 5665 | Substitute a newline. |
| 5666 | @item \p |
| 5667 | Substitute a parameter's value; the argument names the parameter. |
| 5668 | @item \r |
| 5669 | Substitute a carriage return. |
| 5670 | @item \t |
| 5671 | Substitute the selected thread; an argument names a thread parameter. |
| 5672 | @item \v |
| 5673 | Substitute the version of GDB. |
| 5674 | @item \w |
| 5675 | Substitute the current working directory. |
| 5676 | @item \[ |
| 5677 | Begin a sequence of non-printing characters. These sequences are |
| 5678 | typically used with the ESC character, and are not counted in the string |
| 5679 | length. Example: ``\[\e[0;34m\](gdb)\[\e[0m\]'' will return a |
| 5680 | blue-colored ``(gdb)'' prompt where the length is five. |
| 5681 | @item \] |
| 5682 | End a sequence of non-printing characters. |
| 5683 | @end table |
| 5684 | |
| 5685 | For example: |
| 5686 | |
| 5687 | @smallexample |
| 5688 | substitute_prompt (``frame: \f, |
| 5689 | print arguments: \p@{print frame-arguments@}'') |
| 5690 | @end smallexample |
| 5691 | |
| 5692 | @exdent will return the string: |
| 5693 | |
| 5694 | @smallexample |
| 5695 | "frame: main, print arguments: scalars" |
| 5696 | @end smallexample |
| 5697 | @end table |