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