1 \input texinfo @c -*-texinfo-*-
2 @c Copyright (C) 1988-2013 Free Software Foundation, Inc.
5 @c makeinfo ignores cmds prev to setfilename, so its arg cannot make use
6 @c of @set vars. However, you can override filename with makeinfo -o.
11 @settitle Debugging with @value{GDBN}
12 @setchapternewpage odd
21 @c To avoid file-name clashes between index.html and Index.html, when
22 @c the manual is produced on a Posix host and then moved to a
23 @c case-insensitive filesystem (e.g., MS-Windows), we separate the
24 @c indices into two: Concept Index and all the rest.
28 @c readline appendices use @vindex, @findex and @ftable,
29 @c annotate.texi and gdbmi use @findex.
32 @c !!set GDB manual's edition---not the same as GDB version!
33 @c This is updated by GNU Press.
36 @c !!set GDB edit command default editor
39 @c THIS MANUAL REQUIRES TEXINFO 4.0 OR LATER.
41 @c This is a dir.info fragment to support semi-automated addition of
42 @c manuals to an info tree.
43 @dircategory Software development
45 * Gdb: (gdb). The GNU debugger.
49 Copyright @copyright{} 1988-2013 Free Software Foundation, Inc.
51 Permission is granted to copy, distribute and/or modify this document
52 under the terms of the GNU Free Documentation License, Version 1.3 or
53 any later version published by the Free Software Foundation; with the
54 Invariant Sections being ``Free Software'' and ``Free Software Needs
55 Free Documentation'', with the Front-Cover Texts being ``A GNU Manual,''
56 and with the Back-Cover Texts as in (a) below.
58 (a) The FSF's Back-Cover Text is: ``You are free to copy and modify
59 this GNU Manual. Buying copies from GNU Press supports the FSF in
60 developing GNU and promoting software freedom.''
64 This file documents the @sc{gnu} debugger @value{GDBN}.
66 This is the @value{EDITION} Edition, of @cite{Debugging with
67 @value{GDBN}: the @sc{gnu} Source-Level Debugger} for @value{GDBN}
68 @ifset VERSION_PACKAGE
69 @value{VERSION_PACKAGE}
71 Version @value{GDBVN}.
77 @title Debugging with @value{GDBN}
78 @subtitle The @sc{gnu} Source-Level Debugger
80 @subtitle @value{EDITION} Edition, for @value{GDBN} version @value{GDBVN}
81 @ifset VERSION_PACKAGE
83 @subtitle @value{VERSION_PACKAGE}
85 @author Richard Stallman, Roland Pesch, Stan Shebs, et al.
89 \hfill (Send bugs and comments on @value{GDBN} to @value{BUGURL}.)\par
90 \hfill {\it Debugging with @value{GDBN}}\par
91 \hfill \TeX{}info \texinfoversion\par
95 @vskip 0pt plus 1filll
96 Published by the Free Software Foundation @*
97 51 Franklin Street, Fifth Floor,
98 Boston, MA 02110-1301, USA@*
99 ISBN 978-0-9831592-3-0 @*
106 @node Top, Summary, (dir), (dir)
108 @top Debugging with @value{GDBN}
110 This file describes @value{GDBN}, the @sc{gnu} symbolic debugger.
112 This is the @value{EDITION} Edition, for @value{GDBN}
113 @ifset VERSION_PACKAGE
114 @value{VERSION_PACKAGE}
116 Version @value{GDBVN}.
118 Copyright (C) 1988-2013 Free Software Foundation, Inc.
120 This edition of the GDB manual is dedicated to the memory of Fred
121 Fish. Fred was a long-standing contributor to GDB and to Free
122 software in general. We will miss him.
125 * Summary:: Summary of @value{GDBN}
126 * Sample Session:: A sample @value{GDBN} session
128 * Invocation:: Getting in and out of @value{GDBN}
129 * Commands:: @value{GDBN} commands
130 * Running:: Running programs under @value{GDBN}
131 * Stopping:: Stopping and continuing
132 * Reverse Execution:: Running programs backward
133 * Process Record and Replay:: Recording inferior's execution and replaying it
134 * Stack:: Examining the stack
135 * Source:: Examining source files
136 * Data:: Examining data
137 * Optimized Code:: Debugging optimized code
138 * Macros:: Preprocessor Macros
139 * Tracepoints:: Debugging remote targets non-intrusively
140 * Overlays:: Debugging programs that use overlays
142 * Languages:: Using @value{GDBN} with different languages
144 * Symbols:: Examining the symbol table
145 * Altering:: Altering execution
146 * GDB Files:: @value{GDBN} files
147 * Targets:: Specifying a debugging target
148 * Remote Debugging:: Debugging remote programs
149 * Configurations:: Configuration-specific information
150 * Controlling GDB:: Controlling @value{GDBN}
151 * Extending GDB:: Extending @value{GDBN}
152 * Interpreters:: Command Interpreters
153 * TUI:: @value{GDBN} Text User Interface
154 * Emacs:: Using @value{GDBN} under @sc{gnu} Emacs
155 * GDB/MI:: @value{GDBN}'s Machine Interface.
156 * Annotations:: @value{GDBN}'s annotation interface.
157 * JIT Interface:: Using the JIT debugging interface.
158 * In-Process Agent:: In-Process Agent
160 * GDB Bugs:: Reporting bugs in @value{GDBN}
162 @ifset SYSTEM_READLINE
163 * Command Line Editing: (rluserman). Command Line Editing
164 * Using History Interactively: (history). Using History Interactively
166 @ifclear SYSTEM_READLINE
167 * Command Line Editing:: Command Line Editing
168 * Using History Interactively:: Using History Interactively
170 * In Memoriam:: In Memoriam
171 * Formatting Documentation:: How to format and print @value{GDBN} documentation
172 * Installing GDB:: Installing GDB
173 * Maintenance Commands:: Maintenance Commands
174 * Remote Protocol:: GDB Remote Serial Protocol
175 * Agent Expressions:: The GDB Agent Expression Mechanism
176 * Target Descriptions:: How targets can describe themselves to
178 * Operating System Information:: Getting additional information from
180 * Trace File Format:: GDB trace file format
181 * Index Section Format:: .gdb_index section format
182 * Copying:: GNU General Public License says
183 how you can copy and share GDB
184 * GNU Free Documentation License:: The license for this documentation
185 * Concept Index:: Index of @value{GDBN} concepts
186 * Command and Variable Index:: Index of @value{GDBN} commands, variables,
187 functions, and Python data types
195 @unnumbered Summary of @value{GDBN}
197 The purpose of a debugger such as @value{GDBN} is to allow you to see what is
198 going on ``inside'' another program while it executes---or what another
199 program was doing at the moment it crashed.
201 @value{GDBN} can do four main kinds of things (plus other things in support of
202 these) to help you catch bugs in the act:
206 Start your program, specifying anything that might affect its behavior.
209 Make your program stop on specified conditions.
212 Examine what has happened, when your program has stopped.
215 Change things in your program, so you can experiment with correcting the
216 effects of one bug and go on to learn about another.
219 You can use @value{GDBN} to debug programs written in C and C@t{++}.
220 For more information, see @ref{Supported Languages,,Supported Languages}.
221 For more information, see @ref{C,,C and C++}.
223 Support for D is partial. For information on D, see
227 Support for Modula-2 is partial. For information on Modula-2, see
228 @ref{Modula-2,,Modula-2}.
230 Support for OpenCL C is partial. For information on OpenCL C, see
231 @ref{OpenCL C,,OpenCL C}.
234 Debugging Pascal programs which use sets, subranges, file variables, or
235 nested functions does not currently work. @value{GDBN} does not support
236 entering expressions, printing values, or similar features using Pascal
240 @value{GDBN} can be used to debug programs written in Fortran, although
241 it may be necessary to refer to some variables with a trailing
244 @value{GDBN} can be used to debug programs written in Objective-C,
245 using either the Apple/NeXT or the GNU Objective-C runtime.
248 * Free Software:: Freely redistributable software
249 * Free Documentation:: Free Software Needs Free Documentation
250 * Contributors:: Contributors to GDB
254 @unnumberedsec Free Software
256 @value{GDBN} is @dfn{free software}, protected by the @sc{gnu}
257 General Public License
258 (GPL). The GPL gives you the freedom to copy or adapt a licensed
259 program---but every person getting a copy also gets with it the
260 freedom to modify that copy (which means that they must get access to
261 the source code), and the freedom to distribute further copies.
262 Typical software companies use copyrights to limit your freedoms; the
263 Free Software Foundation uses the GPL to preserve these freedoms.
265 Fundamentally, the General Public License is a license which says that
266 you have these freedoms and that you cannot take these freedoms away
269 @node Free Documentation
270 @unnumberedsec Free Software Needs Free Documentation
272 The biggest deficiency in the free software community today is not in
273 the software---it is the lack of good free documentation that we can
274 include with the free software. Many of our most important
275 programs do not come with free reference manuals and free introductory
276 texts. Documentation is an essential part of any software package;
277 when an important free software package does not come with a free
278 manual and a free tutorial, that is a major gap. We have many such
281 Consider Perl, for instance. The tutorial manuals that people
282 normally use are non-free. How did this come about? Because the
283 authors of those manuals published them with restrictive terms---no
284 copying, no modification, source files not available---which exclude
285 them from the free software world.
287 That wasn't the first time this sort of thing happened, and it was far
288 from the last. Many times we have heard a GNU user eagerly describe a
289 manual that he is writing, his intended contribution to the community,
290 only to learn that he had ruined everything by signing a publication
291 contract to make it non-free.
293 Free documentation, like free software, is a matter of freedom, not
294 price. The problem with the non-free manual is not that publishers
295 charge a price for printed copies---that in itself is fine. (The Free
296 Software Foundation sells printed copies of manuals, too.) The
297 problem is the restrictions on the use of the manual. Free manuals
298 are available in source code form, and give you permission to copy and
299 modify. Non-free manuals do not allow this.
301 The criteria of freedom for a free manual are roughly the same as for
302 free software. Redistribution (including the normal kinds of
303 commercial redistribution) must be permitted, so that the manual can
304 accompany every copy of the program, both on-line and on paper.
306 Permission for modification of the technical content is crucial too.
307 When people modify the software, adding or changing features, if they
308 are conscientious they will change the manual too---so they can
309 provide accurate and clear documentation for the modified program. A
310 manual that leaves you no choice but to write a new manual to document
311 a changed version of the program is not really available to our
314 Some kinds of limits on the way modification is handled are
315 acceptable. For example, requirements to preserve the original
316 author's copyright notice, the distribution terms, or the list of
317 authors, are ok. It is also no problem to require modified versions
318 to include notice that they were modified. Even entire sections that
319 may not be deleted or changed are acceptable, as long as they deal
320 with nontechnical topics (like this one). These kinds of restrictions
321 are acceptable because they don't obstruct the community's normal use
324 However, it must be possible to modify all the @emph{technical}
325 content of the manual, and then distribute the result in all the usual
326 media, through all the usual channels. Otherwise, the restrictions
327 obstruct the use of the manual, it is not free, and we need another
328 manual to replace it.
330 Please spread the word about this issue. Our community continues to
331 lose manuals to proprietary publishing. If we spread the word that
332 free software needs free reference manuals and free tutorials, perhaps
333 the next person who wants to contribute by writing documentation will
334 realize, before it is too late, that only free manuals contribute to
335 the free software community.
337 If you are writing documentation, please insist on publishing it under
338 the GNU Free Documentation License or another free documentation
339 license. Remember that this decision requires your approval---you
340 don't have to let the publisher decide. Some commercial publishers
341 will use a free license if you insist, but they will not propose the
342 option; it is up to you to raise the issue and say firmly that this is
343 what you want. If the publisher you are dealing with refuses, please
344 try other publishers. If you're not sure whether a proposed license
345 is free, write to @email{licensing@@gnu.org}.
347 You can encourage commercial publishers to sell more free, copylefted
348 manuals and tutorials by buying them, and particularly by buying
349 copies from the publishers that paid for their writing or for major
350 improvements. Meanwhile, try to avoid buying non-free documentation
351 at all. Check the distribution terms of a manual before you buy it,
352 and insist that whoever seeks your business must respect your freedom.
353 Check the history of the book, and try to reward the publishers that
354 have paid or pay the authors to work on it.
356 The Free Software Foundation maintains a list of free documentation
357 published by other publishers, at
358 @url{http://www.fsf.org/doc/other-free-books.html}.
361 @unnumberedsec Contributors to @value{GDBN}
363 Richard Stallman was the original author of @value{GDBN}, and of many
364 other @sc{gnu} programs. Many others have contributed to its
365 development. This section attempts to credit major contributors. One
366 of the virtues of free software is that everyone is free to contribute
367 to it; with regret, we cannot actually acknowledge everyone here. The
368 file @file{ChangeLog} in the @value{GDBN} distribution approximates a
369 blow-by-blow account.
371 Changes much prior to version 2.0 are lost in the mists of time.
374 @emph{Plea:} Additions to this section are particularly welcome. If you
375 or your friends (or enemies, to be evenhanded) have been unfairly
376 omitted from this list, we would like to add your names!
379 So that they may not regard their many labors as thankless, we
380 particularly thank those who shepherded @value{GDBN} through major
382 Andrew Cagney (releases 6.3, 6.2, 6.1, 6.0, 5.3, 5.2, 5.1 and 5.0);
383 Jim Blandy (release 4.18);
384 Jason Molenda (release 4.17);
385 Stan Shebs (release 4.14);
386 Fred Fish (releases 4.16, 4.15, 4.13, 4.12, 4.11, 4.10, and 4.9);
387 Stu Grossman and John Gilmore (releases 4.8, 4.7, 4.6, 4.5, and 4.4);
388 John Gilmore (releases 4.3, 4.2, 4.1, 4.0, and 3.9);
389 Jim Kingdon (releases 3.5, 3.4, and 3.3);
390 and Randy Smith (releases 3.2, 3.1, and 3.0).
392 Richard Stallman, assisted at various times by Peter TerMaat, Chris
393 Hanson, and Richard Mlynarik, handled releases through 2.8.
395 Michael Tiemann is the author of most of the @sc{gnu} C@t{++} support
396 in @value{GDBN}, with significant additional contributions from Per
397 Bothner and Daniel Berlin. James Clark wrote the @sc{gnu} C@t{++}
398 demangler. Early work on C@t{++} was by Peter TerMaat (who also did
399 much general update work leading to release 3.0).
401 @value{GDBN} uses the BFD subroutine library to examine multiple
402 object-file formats; BFD was a joint project of David V.
403 Henkel-Wallace, Rich Pixley, Steve Chamberlain, and John Gilmore.
405 David Johnson wrote the original COFF support; Pace Willison did
406 the original support for encapsulated COFF.
408 Brent Benson of Harris Computer Systems contributed DWARF 2 support.
410 Adam de Boor and Bradley Davis contributed the ISI Optimum V support.
411 Per Bothner, Noboyuki Hikichi, and Alessandro Forin contributed MIPS
413 Jean-Daniel Fekete contributed Sun 386i support.
414 Chris Hanson improved the HP9000 support.
415 Noboyuki Hikichi and Tomoyuki Hasei contributed Sony/News OS 3 support.
416 David Johnson contributed Encore Umax support.
417 Jyrki Kuoppala contributed Altos 3068 support.
418 Jeff Law contributed HP PA and SOM support.
419 Keith Packard contributed NS32K support.
420 Doug Rabson contributed Acorn Risc Machine support.
421 Bob Rusk contributed Harris Nighthawk CX-UX support.
422 Chris Smith contributed Convex support (and Fortran debugging).
423 Jonathan Stone contributed Pyramid support.
424 Michael Tiemann contributed SPARC support.
425 Tim Tucker contributed support for the Gould NP1 and Gould Powernode.
426 Pace Willison contributed Intel 386 support.
427 Jay Vosburgh contributed Symmetry support.
428 Marko Mlinar contributed OpenRISC 1000 support.
430 Andreas Schwab contributed M68K @sc{gnu}/Linux support.
432 Rich Schaefer and Peter Schauer helped with support of SunOS shared
435 Jay Fenlason and Roland McGrath ensured that @value{GDBN} and GAS agree
436 about several machine instruction sets.
438 Patrick Duval, Ted Goldstein, Vikram Koka and Glenn Engel helped develop
439 remote debugging. Intel Corporation, Wind River Systems, AMD, and ARM
440 contributed remote debugging modules for the i960, VxWorks, A29K UDI,
441 and RDI targets, respectively.
443 Brian Fox is the author of the readline libraries providing
444 command-line editing and command history.
446 Andrew Beers of SUNY Buffalo wrote the language-switching code, the
447 Modula-2 support, and contributed the Languages chapter of this manual.
449 Fred Fish wrote most of the support for Unix System Vr4.
450 He also enhanced the command-completion support to cover C@t{++} overloaded
453 Hitachi America (now Renesas America), Ltd. sponsored the support for
454 H8/300, H8/500, and Super-H processors.
456 NEC sponsored the support for the v850, Vr4xxx, and Vr5xxx processors.
458 Mitsubishi (now Renesas) sponsored the support for D10V, D30V, and M32R/D
461 Toshiba sponsored the support for the TX39 Mips processor.
463 Matsushita sponsored the support for the MN10200 and MN10300 processors.
465 Fujitsu sponsored the support for SPARClite and FR30 processors.
467 Kung Hsu, Jeff Law, and Rick Sladkey added support for hardware
470 Michael Snyder added support for tracepoints.
472 Stu Grossman wrote gdbserver.
474 Jim Kingdon, Peter Schauer, Ian Taylor, and Stu Grossman made
475 nearly innumerable bug fixes and cleanups throughout @value{GDBN}.
477 The following people at the Hewlett-Packard Company contributed
478 support for the PA-RISC 2.0 architecture, HP-UX 10.20, 10.30, and 11.0
479 (narrow mode), HP's implementation of kernel threads, HP's aC@t{++}
480 compiler, and the Text User Interface (nee Terminal User Interface):
481 Ben Krepp, Richard Title, John Bishop, Susan Macchia, Kathy Mann,
482 Satish Pai, India Paul, Steve Rehrauer, and Elena Zannoni. Kim Haase
483 provided HP-specific information in this manual.
485 DJ Delorie ported @value{GDBN} to MS-DOS, for the DJGPP project.
486 Robert Hoehne made significant contributions to the DJGPP port.
488 Cygnus Solutions has sponsored @value{GDBN} maintenance and much of its
489 development since 1991. Cygnus engineers who have worked on @value{GDBN}
490 fulltime include Mark Alexander, Jim Blandy, Per Bothner, Kevin
491 Buettner, Edith Epstein, Chris Faylor, Fred Fish, Martin Hunt, Jim
492 Ingham, John Gilmore, Stu Grossman, Kung Hsu, Jim Kingdon, John Metzler,
493 Fernando Nasser, Geoffrey Noer, Dawn Perchik, Rich Pixley, Zdenek
494 Radouch, Keith Seitz, Stan Shebs, David Taylor, and Elena Zannoni. In
495 addition, Dave Brolley, Ian Carmichael, Steve Chamberlain, Nick Clifton,
496 JT Conklin, Stan Cox, DJ Delorie, Ulrich Drepper, Frank Eigler, Doug
497 Evans, Sean Fagan, David Henkel-Wallace, Richard Henderson, Jeff
498 Holcomb, Jeff Law, Jim Lemke, Tom Lord, Bob Manson, Michael Meissner,
499 Jason Merrill, Catherine Moore, Drew Moseley, Ken Raeburn, Gavin
500 Romig-Koch, Rob Savoye, Jamie Smith, Mike Stump, Ian Taylor, Angela
501 Thomas, Michael Tiemann, Tom Tromey, Ron Unrau, Jim Wilson, and David
502 Zuhn have made contributions both large and small.
504 Andrew Cagney, Fernando Nasser, and Elena Zannoni, while working for
505 Cygnus Solutions, implemented the original @sc{gdb/mi} interface.
507 Jim Blandy added support for preprocessor macros, while working for Red
510 Andrew Cagney designed @value{GDBN}'s architecture vector. Many
511 people including Andrew Cagney, Stephane Carrez, Randolph Chung, Nick
512 Duffek, Richard Henderson, Mark Kettenis, Grace Sainsbury, Kei
513 Sakamoto, Yoshinori Sato, Michael Snyder, Andreas Schwab, Jason
514 Thorpe, Corinna Vinschen, Ulrich Weigand, and Elena Zannoni, helped
515 with the migration of old architectures to this new framework.
517 Andrew Cagney completely re-designed and re-implemented @value{GDBN}'s
518 unwinder framework, this consisting of a fresh new design featuring
519 frame IDs, independent frame sniffers, and the sentinel frame. Mark
520 Kettenis implemented the @sc{dwarf 2} unwinder, Jeff Johnston the
521 libunwind unwinder, and Andrew Cagney the dummy, sentinel, tramp, and
522 trad unwinders. The architecture-specific changes, each involving a
523 complete rewrite of the architecture's frame code, were carried out by
524 Jim Blandy, Joel Brobecker, Kevin Buettner, Andrew Cagney, Stephane
525 Carrez, Randolph Chung, Orjan Friberg, Richard Henderson, Daniel
526 Jacobowitz, Jeff Johnston, Mark Kettenis, Theodore A. Roth, Kei
527 Sakamoto, Yoshinori Sato, Michael Snyder, Corinna Vinschen, and Ulrich
530 Christian Zankel, Ross Morley, Bob Wilson, and Maxim Grigoriev from
531 Tensilica, Inc.@: contributed support for Xtensa processors. Others
532 who have worked on the Xtensa port of @value{GDBN} in the past include
533 Steve Tjiang, John Newlin, and Scott Foehner.
535 Michael Eager and staff of Xilinx, Inc., contributed support for the
536 Xilinx MicroBlaze architecture.
539 @chapter A Sample @value{GDBN} Session
541 You can use this manual at your leisure to read all about @value{GDBN}.
542 However, a handful of commands are enough to get started using the
543 debugger. This chapter illustrates those commands.
546 In this sample session, we emphasize user input like this: @b{input},
547 to make it easier to pick out from the surrounding output.
550 @c FIXME: this example may not be appropriate for some configs, where
551 @c FIXME...primary interest is in remote use.
553 One of the preliminary versions of @sc{gnu} @code{m4} (a generic macro
554 processor) exhibits the following bug: sometimes, when we change its
555 quote strings from the default, the commands used to capture one macro
556 definition within another stop working. In the following short @code{m4}
557 session, we define a macro @code{foo} which expands to @code{0000}; we
558 then use the @code{m4} built-in @code{defn} to define @code{bar} as the
559 same thing. However, when we change the open quote string to
560 @code{<QUOTE>} and the close quote string to @code{<UNQUOTE>}, the same
561 procedure fails to define a new synonym @code{baz}:
570 @b{define(bar,defn(`foo'))}
574 @b{changequote(<QUOTE>,<UNQUOTE>)}
576 @b{define(baz,defn(<QUOTE>foo<UNQUOTE>))}
579 m4: End of input: 0: fatal error: EOF in string
583 Let us use @value{GDBN} to try to see what is going on.
586 $ @b{@value{GDBP} m4}
587 @c FIXME: this falsifies the exact text played out, to permit smallbook
588 @c FIXME... format to come out better.
589 @value{GDBN} is free software and you are welcome to distribute copies
590 of it under certain conditions; type "show copying" to see
592 There is absolutely no warranty for @value{GDBN}; type "show warranty"
595 @value{GDBN} @value{GDBVN}, Copyright 1999 Free Software Foundation, Inc...
600 @value{GDBN} reads only enough symbol data to know where to find the
601 rest when needed; as a result, the first prompt comes up very quickly.
602 We now tell @value{GDBN} to use a narrower display width than usual, so
603 that examples fit in this manual.
606 (@value{GDBP}) @b{set width 70}
610 We need to see how the @code{m4} built-in @code{changequote} works.
611 Having looked at the source, we know the relevant subroutine is
612 @code{m4_changequote}, so we set a breakpoint there with the @value{GDBN}
613 @code{break} command.
616 (@value{GDBP}) @b{break m4_changequote}
617 Breakpoint 1 at 0x62f4: file builtin.c, line 879.
621 Using the @code{run} command, we start @code{m4} running under @value{GDBN}
622 control; as long as control does not reach the @code{m4_changequote}
623 subroutine, the program runs as usual:
626 (@value{GDBP}) @b{run}
627 Starting program: /work/Editorial/gdb/gnu/m4/m4
635 To trigger the breakpoint, we call @code{changequote}. @value{GDBN}
636 suspends execution of @code{m4}, displaying information about the
637 context where it stops.
640 @b{changequote(<QUOTE>,<UNQUOTE>)}
642 Breakpoint 1, m4_changequote (argc=3, argv=0x33c70)
644 879 if (bad_argc(TOKEN_DATA_TEXT(argv[0]),argc,1,3))
648 Now we use the command @code{n} (@code{next}) to advance execution to
649 the next line of the current function.
653 882 set_quotes((argc >= 2) ? TOKEN_DATA_TEXT(argv[1])\
658 @code{set_quotes} looks like a promising subroutine. We can go into it
659 by using the command @code{s} (@code{step}) instead of @code{next}.
660 @code{step} goes to the next line to be executed in @emph{any}
661 subroutine, so it steps into @code{set_quotes}.
665 set_quotes (lq=0x34c78 "<QUOTE>", rq=0x34c88 "<UNQUOTE>")
667 530 if (lquote != def_lquote)
671 The display that shows the subroutine where @code{m4} is now
672 suspended (and its arguments) is called a stack frame display. It
673 shows a summary of the stack. We can use the @code{backtrace}
674 command (which can also be spelled @code{bt}), to see where we are
675 in the stack as a whole: the @code{backtrace} command displays a
676 stack frame for each active subroutine.
679 (@value{GDBP}) @b{bt}
680 #0 set_quotes (lq=0x34c78 "<QUOTE>", rq=0x34c88 "<UNQUOTE>")
682 #1 0x6344 in m4_changequote (argc=3, argv=0x33c70)
684 #2 0x8174 in expand_macro (sym=0x33320) at macro.c:242
685 #3 0x7a88 in expand_token (obs=0x0, t=209696, td=0xf7fffa30)
687 #4 0x79dc in expand_input () at macro.c:40
688 #5 0x2930 in main (argc=0, argv=0xf7fffb20) at m4.c:195
692 We step through a few more lines to see what happens. The first two
693 times, we can use @samp{s}; the next two times we use @code{n} to avoid
694 falling into the @code{xstrdup} subroutine.
698 0x3b5c 532 if (rquote != def_rquote)
700 0x3b80 535 lquote = (lq == nil || *lq == '\0') ? \
701 def_lquote : xstrdup(lq);
703 536 rquote = (rq == nil || *rq == '\0') ? def_rquote\
706 538 len_lquote = strlen(rquote);
710 The last line displayed looks a little odd; we can examine the variables
711 @code{lquote} and @code{rquote} to see if they are in fact the new left
712 and right quotes we specified. We use the command @code{p}
713 (@code{print}) to see their values.
716 (@value{GDBP}) @b{p lquote}
717 $1 = 0x35d40 "<QUOTE>"
718 (@value{GDBP}) @b{p rquote}
719 $2 = 0x35d50 "<UNQUOTE>"
723 @code{lquote} and @code{rquote} are indeed the new left and right quotes.
724 To look at some context, we can display ten lines of source
725 surrounding the current line with the @code{l} (@code{list}) command.
731 535 lquote = (lq == nil || *lq == '\0') ? def_lquote\
733 536 rquote = (rq == nil || *rq == '\0') ? def_rquote\
736 538 len_lquote = strlen(rquote);
737 539 len_rquote = strlen(lquote);
744 Let us step past the two lines that set @code{len_lquote} and
745 @code{len_rquote}, and then examine the values of those variables.
749 539 len_rquote = strlen(lquote);
752 (@value{GDBP}) @b{p len_lquote}
754 (@value{GDBP}) @b{p len_rquote}
759 That certainly looks wrong, assuming @code{len_lquote} and
760 @code{len_rquote} are meant to be the lengths of @code{lquote} and
761 @code{rquote} respectively. We can set them to better values using
762 the @code{p} command, since it can print the value of
763 any expression---and that expression can include subroutine calls and
767 (@value{GDBP}) @b{p len_lquote=strlen(lquote)}
769 (@value{GDBP}) @b{p len_rquote=strlen(rquote)}
774 Is that enough to fix the problem of using the new quotes with the
775 @code{m4} built-in @code{defn}? We can allow @code{m4} to continue
776 executing with the @code{c} (@code{continue}) command, and then try the
777 example that caused trouble initially:
783 @b{define(baz,defn(<QUOTE>foo<UNQUOTE>))}
790 Success! The new quotes now work just as well as the default ones. The
791 problem seems to have been just the two typos defining the wrong
792 lengths. We allow @code{m4} exit by giving it an EOF as input:
796 Program exited normally.
800 The message @samp{Program exited normally.} is from @value{GDBN}; it
801 indicates @code{m4} has finished executing. We can end our @value{GDBN}
802 session with the @value{GDBN} @code{quit} command.
805 (@value{GDBP}) @b{quit}
809 @chapter Getting In and Out of @value{GDBN}
811 This chapter discusses how to start @value{GDBN}, and how to get out of it.
815 type @samp{@value{GDBP}} to start @value{GDBN}.
817 type @kbd{quit} or @kbd{Ctrl-d} to exit.
821 * Invoking GDB:: How to start @value{GDBN}
822 * Quitting GDB:: How to quit @value{GDBN}
823 * Shell Commands:: How to use shell commands inside @value{GDBN}
824 * Logging Output:: How to log @value{GDBN}'s output to a file
828 @section Invoking @value{GDBN}
830 Invoke @value{GDBN} by running the program @code{@value{GDBP}}. Once started,
831 @value{GDBN} reads commands from the terminal until you tell it to exit.
833 You can also run @code{@value{GDBP}} with a variety of arguments and options,
834 to specify more of your debugging environment at the outset.
836 The command-line options described here are designed
837 to cover a variety of situations; in some environments, some of these
838 options may effectively be unavailable.
840 The most usual way to start @value{GDBN} is with one argument,
841 specifying an executable program:
844 @value{GDBP} @var{program}
848 You can also start with both an executable program and a core file
852 @value{GDBP} @var{program} @var{core}
855 You can, instead, specify a process ID as a second argument, if you want
856 to debug a running process:
859 @value{GDBP} @var{program} 1234
863 would attach @value{GDBN} to process @code{1234} (unless you also have a file
864 named @file{1234}; @value{GDBN} does check for a core file first).
866 Taking advantage of the second command-line argument requires a fairly
867 complete operating system; when you use @value{GDBN} as a remote
868 debugger attached to a bare board, there may not be any notion of
869 ``process'', and there is often no way to get a core dump. @value{GDBN}
870 will warn you if it is unable to attach or to read core dumps.
872 You can optionally have @code{@value{GDBP}} pass any arguments after the
873 executable file to the inferior using @code{--args}. This option stops
876 @value{GDBP} --args gcc -O2 -c foo.c
878 This will cause @code{@value{GDBP}} to debug @code{gcc}, and to set
879 @code{gcc}'s command-line arguments (@pxref{Arguments}) to @samp{-O2 -c foo.c}.
881 You can run @code{@value{GDBP}} without printing the front material, which describes
882 @value{GDBN}'s non-warranty, by specifying @code{-silent}:
889 You can further control how @value{GDBN} starts up by using command-line
890 options. @value{GDBN} itself can remind you of the options available.
900 to display all available options and briefly describe their use
901 (@samp{@value{GDBP} -h} is a shorter equivalent).
903 All options and command line arguments you give are processed
904 in sequential order. The order makes a difference when the
905 @samp{-x} option is used.
909 * File Options:: Choosing files
910 * Mode Options:: Choosing modes
911 * Startup:: What @value{GDBN} does during startup
915 @subsection Choosing Files
917 When @value{GDBN} starts, it reads any arguments other than options as
918 specifying an executable file and core file (or process ID). This is
919 the same as if the arguments were specified by the @samp{-se} and
920 @samp{-c} (or @samp{-p}) options respectively. (@value{GDBN} reads the
921 first argument that does not have an associated option flag as
922 equivalent to the @samp{-se} option followed by that argument; and the
923 second argument that does not have an associated option flag, if any, as
924 equivalent to the @samp{-c}/@samp{-p} option followed by that argument.)
925 If the second argument begins with a decimal digit, @value{GDBN} will
926 first attempt to attach to it as a process, and if that fails, attempt
927 to open it as a corefile. If you have a corefile whose name begins with
928 a digit, you can prevent @value{GDBN} from treating it as a pid by
929 prefixing it with @file{./}, e.g.@: @file{./12345}.
931 If @value{GDBN} has not been configured to included core file support,
932 such as for most embedded targets, then it will complain about a second
933 argument and ignore it.
935 Many options have both long and short forms; both are shown in the
936 following list. @value{GDBN} also recognizes the long forms if you truncate
937 them, so long as enough of the option is present to be unambiguous.
938 (If you prefer, you can flag option arguments with @samp{--} rather
939 than @samp{-}, though we illustrate the more usual convention.)
941 @c NOTE: the @cindex entries here use double dashes ON PURPOSE. This
942 @c way, both those who look for -foo and --foo in the index, will find
946 @item -symbols @var{file}
948 @cindex @code{--symbols}
950 Read symbol table from file @var{file}.
952 @item -exec @var{file}
954 @cindex @code{--exec}
956 Use file @var{file} as the executable file to execute when appropriate,
957 and for examining pure data in conjunction with a core dump.
961 Read symbol table from file @var{file} and use it as the executable
964 @item -core @var{file}
966 @cindex @code{--core}
968 Use file @var{file} as a core dump to examine.
970 @item -pid @var{number}
971 @itemx -p @var{number}
974 Connect to process ID @var{number}, as with the @code{attach} command.
976 @item -command @var{file}
978 @cindex @code{--command}
980 Execute commands from file @var{file}. The contents of this file is
981 evaluated exactly as the @code{source} command would.
982 @xref{Command Files,, Command files}.
984 @item -eval-command @var{command}
985 @itemx -ex @var{command}
986 @cindex @code{--eval-command}
988 Execute a single @value{GDBN} command.
990 This option may be used multiple times to call multiple commands. It may
991 also be interleaved with @samp{-command} as required.
994 @value{GDBP} -ex 'target sim' -ex 'load' \
995 -x setbreakpoints -ex 'run' a.out
998 @item -init-command @var{file}
999 @itemx -ix @var{file}
1000 @cindex @code{--init-command}
1002 Execute commands from file @var{file} before loading the inferior (but
1003 after loading gdbinit files).
1006 @item -init-eval-command @var{command}
1007 @itemx -iex @var{command}
1008 @cindex @code{--init-eval-command}
1010 Execute a single @value{GDBN} command before loading the inferior (but
1011 after loading gdbinit files).
1014 @item -directory @var{directory}
1015 @itemx -d @var{directory}
1016 @cindex @code{--directory}
1018 Add @var{directory} to the path to search for source and script files.
1022 @cindex @code{--readnow}
1024 Read each symbol file's entire symbol table immediately, rather than
1025 the default, which is to read it incrementally as it is needed.
1026 This makes startup slower, but makes future operations faster.
1031 @subsection Choosing Modes
1033 You can run @value{GDBN} in various alternative modes---for example, in
1034 batch mode or quiet mode.
1042 Do not execute commands found in any initialization file.
1043 There are three init files, loaded in the following order:
1046 @item @file{system.gdbinit}
1047 This is the system-wide init file.
1048 Its location is specified with the @code{--with-system-gdbinit}
1049 configure option (@pxref{System-wide configuration}).
1050 It is loaded first when @value{GDBN} starts, before command line options
1051 have been processed.
1052 @item @file{~/.gdbinit}
1053 This is the init file in your home directory.
1054 It is loaded next, after @file{system.gdbinit}, and before
1055 command options have been processed.
1056 @item @file{./.gdbinit}
1057 This is the init file in the current directory.
1058 It is loaded last, after command line options other than @code{-x} and
1059 @code{-ex} have been processed. Command line options @code{-x} and
1060 @code{-ex} are processed last, after @file{./.gdbinit} has been loaded.
1063 For further documentation on startup processing, @xref{Startup}.
1064 For documentation on how to write command files,
1065 @xref{Command Files,,Command Files}.
1070 Do not execute commands found in @file{~/.gdbinit}, the init file
1071 in your home directory.
1077 @cindex @code{--quiet}
1078 @cindex @code{--silent}
1080 ``Quiet''. Do not print the introductory and copyright messages. These
1081 messages are also suppressed in batch mode.
1084 @cindex @code{--batch}
1085 Run in batch mode. Exit with status @code{0} after processing all the
1086 command files specified with @samp{-x} (and all commands from
1087 initialization files, if not inhibited with @samp{-n}). Exit with
1088 nonzero status if an error occurs in executing the @value{GDBN} commands
1089 in the command files. Batch mode also disables pagination, sets unlimited
1090 terminal width and height @pxref{Screen Size}, and acts as if @kbd{set confirm
1091 off} were in effect (@pxref{Messages/Warnings}).
1093 Batch mode may be useful for running @value{GDBN} as a filter, for
1094 example to download and run a program on another computer; in order to
1095 make this more useful, the message
1098 Program exited normally.
1102 (which is ordinarily issued whenever a program running under
1103 @value{GDBN} control terminates) is not issued when running in batch
1107 @cindex @code{--batch-silent}
1108 Run in batch mode exactly like @samp{-batch}, but totally silently. All
1109 @value{GDBN} output to @code{stdout} is prevented (@code{stderr} is
1110 unaffected). This is much quieter than @samp{-silent} and would be useless
1111 for an interactive session.
1113 This is particularly useful when using targets that give @samp{Loading section}
1114 messages, for example.
1116 Note that targets that give their output via @value{GDBN}, as opposed to
1117 writing directly to @code{stdout}, will also be made silent.
1119 @item -return-child-result
1120 @cindex @code{--return-child-result}
1121 The return code from @value{GDBN} will be the return code from the child
1122 process (the process being debugged), with the following exceptions:
1126 @value{GDBN} exits abnormally. E.g., due to an incorrect argument or an
1127 internal error. In this case the exit code is the same as it would have been
1128 without @samp{-return-child-result}.
1130 The user quits with an explicit value. E.g., @samp{quit 1}.
1132 The child process never runs, or is not allowed to terminate, in which case
1133 the exit code will be -1.
1136 This option is useful in conjunction with @samp{-batch} or @samp{-batch-silent},
1137 when @value{GDBN} is being used as a remote program loader or simulator
1142 @cindex @code{--nowindows}
1144 ``No windows''. If @value{GDBN} comes with a graphical user interface
1145 (GUI) built in, then this option tells @value{GDBN} to only use the command-line
1146 interface. If no GUI is available, this option has no effect.
1150 @cindex @code{--windows}
1152 If @value{GDBN} includes a GUI, then this option requires it to be
1155 @item -cd @var{directory}
1157 Run @value{GDBN} using @var{directory} as its working directory,
1158 instead of the current directory.
1160 @item -data-directory @var{directory}
1161 @cindex @code{--data-directory}
1162 Run @value{GDBN} using @var{directory} as its data directory.
1163 The data directory is where @value{GDBN} searches for its
1164 auxiliary files. @xref{Data Files}.
1168 @cindex @code{--fullname}
1170 @sc{gnu} Emacs sets this option when it runs @value{GDBN} as a
1171 subprocess. It tells @value{GDBN} to output the full file name and line
1172 number in a standard, recognizable fashion each time a stack frame is
1173 displayed (which includes each time your program stops). This
1174 recognizable format looks like two @samp{\032} characters, followed by
1175 the file name, line number and character position separated by colons,
1176 and a newline. The Emacs-to-@value{GDBN} interface program uses the two
1177 @samp{\032} characters as a signal to display the source code for the
1180 @item -annotate @var{level}
1181 @cindex @code{--annotate}
1182 This option sets the @dfn{annotation level} inside @value{GDBN}. Its
1183 effect is identical to using @samp{set annotate @var{level}}
1184 (@pxref{Annotations}). The annotation @var{level} controls how much
1185 information @value{GDBN} prints together with its prompt, values of
1186 expressions, source lines, and other types of output. Level 0 is the
1187 normal, level 1 is for use when @value{GDBN} is run as a subprocess of
1188 @sc{gnu} Emacs, level 3 is the maximum annotation suitable for programs
1189 that control @value{GDBN}, and level 2 has been deprecated.
1191 The annotation mechanism has largely been superseded by @sc{gdb/mi}
1195 @cindex @code{--args}
1196 Change interpretation of command line so that arguments following the
1197 executable file are passed as command line arguments to the inferior.
1198 This option stops option processing.
1200 @item -baud @var{bps}
1202 @cindex @code{--baud}
1204 Set the line speed (baud rate or bits per second) of any serial
1205 interface used by @value{GDBN} for remote debugging.
1207 @item -l @var{timeout}
1209 Set the timeout (in seconds) of any communication used by @value{GDBN}
1210 for remote debugging.
1212 @item -tty @var{device}
1213 @itemx -t @var{device}
1214 @cindex @code{--tty}
1216 Run using @var{device} for your program's standard input and output.
1217 @c FIXME: kingdon thinks there is more to -tty. Investigate.
1219 @c resolve the situation of these eventually
1221 @cindex @code{--tui}
1222 Activate the @dfn{Text User Interface} when starting. The Text User
1223 Interface manages several text windows on the terminal, showing
1224 source, assembly, registers and @value{GDBN} command outputs
1225 (@pxref{TUI, ,@value{GDBN} Text User Interface}). Do not use this
1226 option if you run @value{GDBN} from Emacs (@pxref{Emacs, ,
1227 Using @value{GDBN} under @sc{gnu} Emacs}).
1230 @c @cindex @code{--xdb}
1231 @c Run in XDB compatibility mode, allowing the use of certain XDB commands.
1232 @c For information, see the file @file{xdb_trans.html}, which is usually
1233 @c installed in the directory @code{/opt/langtools/wdb/doc} on HP-UX
1236 @item -interpreter @var{interp}
1237 @cindex @code{--interpreter}
1238 Use the interpreter @var{interp} for interface with the controlling
1239 program or device. This option is meant to be set by programs which
1240 communicate with @value{GDBN} using it as a back end.
1241 @xref{Interpreters, , Command Interpreters}.
1243 @samp{--interpreter=mi} (or @samp{--interpreter=mi2}) causes
1244 @value{GDBN} to use the @dfn{@sc{gdb/mi} interface} (@pxref{GDB/MI, ,
1245 The @sc{gdb/mi} Interface}) included since @value{GDBN} version 6.0. The
1246 previous @sc{gdb/mi} interface, included in @value{GDBN} version 5.3 and
1247 selected with @samp{--interpreter=mi1}, is deprecated. Earlier
1248 @sc{gdb/mi} interfaces are no longer supported.
1251 @cindex @code{--write}
1252 Open the executable and core files for both reading and writing. This
1253 is equivalent to the @samp{set write on} command inside @value{GDBN}
1257 @cindex @code{--statistics}
1258 This option causes @value{GDBN} to print statistics about time and
1259 memory usage after it completes each command and returns to the prompt.
1262 @cindex @code{--version}
1263 This option causes @value{GDBN} to print its version number and
1264 no-warranty blurb, and exit.
1269 @subsection What @value{GDBN} Does During Startup
1270 @cindex @value{GDBN} startup
1272 Here's the description of what @value{GDBN} does during session startup:
1276 Sets up the command interpreter as specified by the command line
1277 (@pxref{Mode Options, interpreter}).
1281 Reads the system-wide @dfn{init file} (if @option{--with-system-gdbinit} was
1282 used when building @value{GDBN}; @pxref{System-wide configuration,
1283 ,System-wide configuration and settings}) and executes all the commands in
1286 @anchor{Home Directory Init File}
1288 Reads the init file (if any) in your home directory@footnote{On
1289 DOS/Windows systems, the home directory is the one pointed to by the
1290 @code{HOME} environment variable.} and executes all the commands in
1293 @anchor{Option -init-eval-command}
1295 Executes commands and command files specified by the @samp{-iex} and
1296 @samp{-ix} options in their specified order. Usually you should use the
1297 @samp{-ex} and @samp{-x} options instead, but this way you can apply
1298 settings before @value{GDBN} init files get executed and before inferior
1302 Processes command line options and operands.
1304 @anchor{Init File in the Current Directory during Startup}
1306 Reads and executes the commands from init file (if any) in the current
1307 working directory as long as @samp{set auto-load local-gdbinit} is set to
1308 @samp{on} (@pxref{Init File in the Current Directory}).
1309 This is only done if the current directory is
1310 different from your home directory. Thus, you can have more than one
1311 init file, one generic in your home directory, and another, specific
1312 to the program you are debugging, in the directory where you invoke
1316 If the command line specified a program to debug, or a process to
1317 attach to, or a core file, @value{GDBN} loads any auto-loaded
1318 scripts provided for the program or for its loaded shared libraries.
1319 @xref{Auto-loading}.
1321 If you wish to disable the auto-loading during startup,
1322 you must do something like the following:
1325 $ gdb -iex "set auto-load python-scripts off" myprogram
1328 Option @samp{-ex} does not work because the auto-loading is then turned
1332 Executes commands and command files specified by the @samp{-ex} and
1333 @samp{-x} options in their specified order. @xref{Command Files}, for
1334 more details about @value{GDBN} command files.
1337 Reads the command history recorded in the @dfn{history file}.
1338 @xref{Command History}, for more details about the command history and the
1339 files where @value{GDBN} records it.
1342 Init files use the same syntax as @dfn{command files} (@pxref{Command
1343 Files}) and are processed by @value{GDBN} in the same way. The init
1344 file in your home directory can set options (such as @samp{set
1345 complaints}) that affect subsequent processing of command line options
1346 and operands. Init files are not executed if you use the @samp{-nx}
1347 option (@pxref{Mode Options, ,Choosing Modes}).
1349 To display the list of init files loaded by gdb at startup, you
1350 can use @kbd{gdb --help}.
1352 @cindex init file name
1353 @cindex @file{.gdbinit}
1354 @cindex @file{gdb.ini}
1355 The @value{GDBN} init files are normally called @file{.gdbinit}.
1356 The DJGPP port of @value{GDBN} uses the name @file{gdb.ini}, due to
1357 the limitations of file names imposed by DOS filesystems. The Windows
1358 port of @value{GDBN} uses the standard name, but if it finds a
1359 @file{gdb.ini} file in your home directory, it warns you about that
1360 and suggests to rename the file to the standard name.
1364 @section Quitting @value{GDBN}
1365 @cindex exiting @value{GDBN}
1366 @cindex leaving @value{GDBN}
1369 @kindex quit @r{[}@var{expression}@r{]}
1370 @kindex q @r{(@code{quit})}
1371 @item quit @r{[}@var{expression}@r{]}
1373 To exit @value{GDBN}, use the @code{quit} command (abbreviated
1374 @code{q}), or type an end-of-file character (usually @kbd{Ctrl-d}). If you
1375 do not supply @var{expression}, @value{GDBN} will terminate normally;
1376 otherwise it will terminate using the result of @var{expression} as the
1381 An interrupt (often @kbd{Ctrl-c}) does not exit from @value{GDBN}, but rather
1382 terminates the action of any @value{GDBN} command that is in progress and
1383 returns to @value{GDBN} command level. It is safe to type the interrupt
1384 character at any time because @value{GDBN} does not allow it to take effect
1385 until a time when it is safe.
1387 If you have been using @value{GDBN} to control an attached process or
1388 device, you can release it with the @code{detach} command
1389 (@pxref{Attach, ,Debugging an Already-running Process}).
1391 @node Shell Commands
1392 @section Shell Commands
1394 If you need to execute occasional shell commands during your
1395 debugging session, there is no need to leave or suspend @value{GDBN}; you can
1396 just use the @code{shell} command.
1401 @cindex shell escape
1402 @item shell @var{command-string}
1403 @itemx !@var{command-string}
1404 Invoke a standard shell to execute @var{command-string}.
1405 Note that no space is needed between @code{!} and @var{command-string}.
1406 If it exists, the environment variable @code{SHELL} determines which
1407 shell to run. Otherwise @value{GDBN} uses the default shell
1408 (@file{/bin/sh} on Unix systems, @file{COMMAND.COM} on MS-DOS, etc.).
1411 The utility @code{make} is often needed in development environments.
1412 You do not have to use the @code{shell} command for this purpose in
1417 @cindex calling make
1418 @item make @var{make-args}
1419 Execute the @code{make} program with the specified
1420 arguments. This is equivalent to @samp{shell make @var{make-args}}.
1423 @node Logging Output
1424 @section Logging Output
1425 @cindex logging @value{GDBN} output
1426 @cindex save @value{GDBN} output to a file
1428 You may want to save the output of @value{GDBN} commands to a file.
1429 There are several commands to control @value{GDBN}'s logging.
1433 @item set logging on
1435 @item set logging off
1437 @cindex logging file name
1438 @item set logging file @var{file}
1439 Change the name of the current logfile. The default logfile is @file{gdb.txt}.
1440 @item set logging overwrite [on|off]
1441 By default, @value{GDBN} will append to the logfile. Set @code{overwrite} if
1442 you want @code{set logging on} to overwrite the logfile instead.
1443 @item set logging redirect [on|off]
1444 By default, @value{GDBN} output will go to both the terminal and the logfile.
1445 Set @code{redirect} if you want output to go only to the log file.
1446 @kindex show logging
1448 Show the current values of the logging settings.
1452 @chapter @value{GDBN} Commands
1454 You can abbreviate a @value{GDBN} command to the first few letters of the command
1455 name, if that abbreviation is unambiguous; and you can repeat certain
1456 @value{GDBN} commands by typing just @key{RET}. You can also use the @key{TAB}
1457 key to get @value{GDBN} to fill out the rest of a word in a command (or to
1458 show you the alternatives available, if there is more than one possibility).
1461 * Command Syntax:: How to give commands to @value{GDBN}
1462 * Completion:: Command completion
1463 * Help:: How to ask @value{GDBN} for help
1466 @node Command Syntax
1467 @section Command Syntax
1469 A @value{GDBN} command is a single line of input. There is no limit on
1470 how long it can be. It starts with a command name, which is followed by
1471 arguments whose meaning depends on the command name. For example, the
1472 command @code{step} accepts an argument which is the number of times to
1473 step, as in @samp{step 5}. You can also use the @code{step} command
1474 with no arguments. Some commands do not allow any arguments.
1476 @cindex abbreviation
1477 @value{GDBN} command names may always be truncated if that abbreviation is
1478 unambiguous. Other possible command abbreviations are listed in the
1479 documentation for individual commands. In some cases, even ambiguous
1480 abbreviations are allowed; for example, @code{s} is specially defined as
1481 equivalent to @code{step} even though there are other commands whose
1482 names start with @code{s}. You can test abbreviations by using them as
1483 arguments to the @code{help} command.
1485 @cindex repeating commands
1486 @kindex RET @r{(repeat last command)}
1487 A blank line as input to @value{GDBN} (typing just @key{RET}) means to
1488 repeat the previous command. Certain commands (for example, @code{run})
1489 will not repeat this way; these are commands whose unintentional
1490 repetition might cause trouble and which you are unlikely to want to
1491 repeat. User-defined commands can disable this feature; see
1492 @ref{Define, dont-repeat}.
1494 The @code{list} and @code{x} commands, when you repeat them with
1495 @key{RET}, construct new arguments rather than repeating
1496 exactly as typed. This permits easy scanning of source or memory.
1498 @value{GDBN} can also use @key{RET} in another way: to partition lengthy
1499 output, in a way similar to the common utility @code{more}
1500 (@pxref{Screen Size,,Screen Size}). Since it is easy to press one
1501 @key{RET} too many in this situation, @value{GDBN} disables command
1502 repetition after any command that generates this sort of display.
1504 @kindex # @r{(a comment)}
1506 Any text from a @kbd{#} to the end of the line is a comment; it does
1507 nothing. This is useful mainly in command files (@pxref{Command
1508 Files,,Command Files}).
1510 @cindex repeating command sequences
1511 @kindex Ctrl-o @r{(operate-and-get-next)}
1512 The @kbd{Ctrl-o} binding is useful for repeating a complex sequence of
1513 commands. This command accepts the current line, like @key{RET}, and
1514 then fetches the next line relative to the current line from the history
1518 @section Command Completion
1521 @cindex word completion
1522 @value{GDBN} can fill in the rest of a word in a command for you, if there is
1523 only one possibility; it can also show you what the valid possibilities
1524 are for the next word in a command, at any time. This works for @value{GDBN}
1525 commands, @value{GDBN} subcommands, and the names of symbols in your program.
1527 Press the @key{TAB} key whenever you want @value{GDBN} to fill out the rest
1528 of a word. If there is only one possibility, @value{GDBN} fills in the
1529 word, and waits for you to finish the command (or press @key{RET} to
1530 enter it). For example, if you type
1532 @c FIXME "@key" does not distinguish its argument sufficiently to permit
1533 @c complete accuracy in these examples; space introduced for clarity.
1534 @c If texinfo enhancements make it unnecessary, it would be nice to
1535 @c replace " @key" by "@key" in the following...
1537 (@value{GDBP}) info bre @key{TAB}
1541 @value{GDBN} fills in the rest of the word @samp{breakpoints}, since that is
1542 the only @code{info} subcommand beginning with @samp{bre}:
1545 (@value{GDBP}) info breakpoints
1549 You can either press @key{RET} at this point, to run the @code{info
1550 breakpoints} command, or backspace and enter something else, if
1551 @samp{breakpoints} does not look like the command you expected. (If you
1552 were sure you wanted @code{info breakpoints} in the first place, you
1553 might as well just type @key{RET} immediately after @samp{info bre},
1554 to exploit command abbreviations rather than command completion).
1556 If there is more than one possibility for the next word when you press
1557 @key{TAB}, @value{GDBN} sounds a bell. You can either supply more
1558 characters and try again, or just press @key{TAB} a second time;
1559 @value{GDBN} displays all the possible completions for that word. For
1560 example, you might want to set a breakpoint on a subroutine whose name
1561 begins with @samp{make_}, but when you type @kbd{b make_@key{TAB}} @value{GDBN}
1562 just sounds the bell. Typing @key{TAB} again displays all the
1563 function names in your program that begin with those characters, for
1567 (@value{GDBP}) b make_ @key{TAB}
1568 @exdent @value{GDBN} sounds bell; press @key{TAB} again, to see:
1569 make_a_section_from_file make_environ
1570 make_abs_section make_function_type
1571 make_blockvector make_pointer_type
1572 make_cleanup make_reference_type
1573 make_command make_symbol_completion_list
1574 (@value{GDBP}) b make_
1578 After displaying the available possibilities, @value{GDBN} copies your
1579 partial input (@samp{b make_} in the example) so you can finish the
1582 If you just want to see the list of alternatives in the first place, you
1583 can press @kbd{M-?} rather than pressing @key{TAB} twice. @kbd{M-?}
1584 means @kbd{@key{META} ?}. You can type this either by holding down a
1585 key designated as the @key{META} shift on your keyboard (if there is
1586 one) while typing @kbd{?}, or as @key{ESC} followed by @kbd{?}.
1588 @cindex quotes in commands
1589 @cindex completion of quoted strings
1590 Sometimes the string you need, while logically a ``word'', may contain
1591 parentheses or other characters that @value{GDBN} normally excludes from
1592 its notion of a word. To permit word completion to work in this
1593 situation, you may enclose words in @code{'} (single quote marks) in
1594 @value{GDBN} commands.
1596 The most likely situation where you might need this is in typing the
1597 name of a C@t{++} function. This is because C@t{++} allows function
1598 overloading (multiple definitions of the same function, distinguished
1599 by argument type). For example, when you want to set a breakpoint you
1600 may need to distinguish whether you mean the version of @code{name}
1601 that takes an @code{int} parameter, @code{name(int)}, or the version
1602 that takes a @code{float} parameter, @code{name(float)}. To use the
1603 word-completion facilities in this situation, type a single quote
1604 @code{'} at the beginning of the function name. This alerts
1605 @value{GDBN} that it may need to consider more information than usual
1606 when you press @key{TAB} or @kbd{M-?} to request word completion:
1609 (@value{GDBP}) b 'bubble( @kbd{M-?}
1610 bubble(double,double) bubble(int,int)
1611 (@value{GDBP}) b 'bubble(
1614 In some cases, @value{GDBN} can tell that completing a name requires using
1615 quotes. When this happens, @value{GDBN} inserts the quote for you (while
1616 completing as much as it can) if you do not type the quote in the first
1620 (@value{GDBP}) b bub @key{TAB}
1621 @exdent @value{GDBN} alters your input line to the following, and rings a bell:
1622 (@value{GDBP}) b 'bubble(
1626 In general, @value{GDBN} can tell that a quote is needed (and inserts it) if
1627 you have not yet started typing the argument list when you ask for
1628 completion on an overloaded symbol.
1630 For more information about overloaded functions, see @ref{C Plus Plus
1631 Expressions, ,C@t{++} Expressions}. You can use the command @code{set
1632 overload-resolution off} to disable overload resolution;
1633 see @ref{Debugging C Plus Plus, ,@value{GDBN} Features for C@t{++}}.
1635 @cindex completion of structure field names
1636 @cindex structure field name completion
1637 @cindex completion of union field names
1638 @cindex union field name completion
1639 When completing in an expression which looks up a field in a
1640 structure, @value{GDBN} also tries@footnote{The completer can be
1641 confused by certain kinds of invalid expressions. Also, it only
1642 examines the static type of the expression, not the dynamic type.} to
1643 limit completions to the field names available in the type of the
1647 (@value{GDBP}) p gdb_stdout.@kbd{M-?}
1648 magic to_fputs to_rewind
1649 to_data to_isatty to_write
1650 to_delete to_put to_write_async_safe
1655 This is because the @code{gdb_stdout} is a variable of the type
1656 @code{struct ui_file} that is defined in @value{GDBN} sources as
1663 ui_file_flush_ftype *to_flush;
1664 ui_file_write_ftype *to_write;
1665 ui_file_write_async_safe_ftype *to_write_async_safe;
1666 ui_file_fputs_ftype *to_fputs;
1667 ui_file_read_ftype *to_read;
1668 ui_file_delete_ftype *to_delete;
1669 ui_file_isatty_ftype *to_isatty;
1670 ui_file_rewind_ftype *to_rewind;
1671 ui_file_put_ftype *to_put;
1678 @section Getting Help
1679 @cindex online documentation
1682 You can always ask @value{GDBN} itself for information on its commands,
1683 using the command @code{help}.
1686 @kindex h @r{(@code{help})}
1689 You can use @code{help} (abbreviated @code{h}) with no arguments to
1690 display a short list of named classes of commands:
1694 List of classes of commands:
1696 aliases -- Aliases of other commands
1697 breakpoints -- Making program stop at certain points
1698 data -- Examining data
1699 files -- Specifying and examining files
1700 internals -- Maintenance commands
1701 obscure -- Obscure features
1702 running -- Running the program
1703 stack -- Examining the stack
1704 status -- Status inquiries
1705 support -- Support facilities
1706 tracepoints -- Tracing of program execution without
1707 stopping the program
1708 user-defined -- User-defined commands
1710 Type "help" followed by a class name for a list of
1711 commands in that class.
1712 Type "help" followed by command name for full
1714 Command name abbreviations are allowed if unambiguous.
1717 @c the above line break eliminates huge line overfull...
1719 @item help @var{class}
1720 Using one of the general help classes as an argument, you can get a
1721 list of the individual commands in that class. For example, here is the
1722 help display for the class @code{status}:
1725 (@value{GDBP}) help status
1730 @c Line break in "show" line falsifies real output, but needed
1731 @c to fit in smallbook page size.
1732 info -- Generic command for showing things
1733 about the program being debugged
1734 show -- Generic command for showing things
1737 Type "help" followed by command name for full
1739 Command name abbreviations are allowed if unambiguous.
1743 @item help @var{command}
1744 With a command name as @code{help} argument, @value{GDBN} displays a
1745 short paragraph on how to use that command.
1748 @item apropos @var{args}
1749 The @code{apropos} command searches through all of the @value{GDBN}
1750 commands, and their documentation, for the regular expression specified in
1751 @var{args}. It prints out all matches found. For example:
1762 alias -- Define a new command that is an alias of an existing command
1763 aliases -- Aliases of other commands
1764 d -- Delete some breakpoints or auto-display expressions
1765 del -- Delete some breakpoints or auto-display expressions
1766 delete -- Delete some breakpoints or auto-display expressions
1771 @item complete @var{args}
1772 The @code{complete @var{args}} command lists all the possible completions
1773 for the beginning of a command. Use @var{args} to specify the beginning of the
1774 command you want completed. For example:
1780 @noindent results in:
1791 @noindent This is intended for use by @sc{gnu} Emacs.
1794 In addition to @code{help}, you can use the @value{GDBN} commands @code{info}
1795 and @code{show} to inquire about the state of your program, or the state
1796 of @value{GDBN} itself. Each command supports many topics of inquiry; this
1797 manual introduces each of them in the appropriate context. The listings
1798 under @code{info} and under @code{show} in the Command, Variable, and
1799 Function Index point to all the sub-commands. @xref{Command and Variable
1805 @kindex i @r{(@code{info})}
1807 This command (abbreviated @code{i}) is for describing the state of your
1808 program. For example, you can show the arguments passed to a function
1809 with @code{info args}, list the registers currently in use with @code{info
1810 registers}, or list the breakpoints you have set with @code{info breakpoints}.
1811 You can get a complete list of the @code{info} sub-commands with
1812 @w{@code{help info}}.
1816 You can assign the result of an expression to an environment variable with
1817 @code{set}. For example, you can set the @value{GDBN} prompt to a $-sign with
1818 @code{set prompt $}.
1822 In contrast to @code{info}, @code{show} is for describing the state of
1823 @value{GDBN} itself.
1824 You can change most of the things you can @code{show}, by using the
1825 related command @code{set}; for example, you can control what number
1826 system is used for displays with @code{set radix}, or simply inquire
1827 which is currently in use with @code{show radix}.
1830 To display all the settable parameters and their current
1831 values, you can use @code{show} with no arguments; you may also use
1832 @code{info set}. Both commands produce the same display.
1833 @c FIXME: "info set" violates the rule that "info" is for state of
1834 @c FIXME...program. Ck w/ GNU: "info set" to be called something else,
1835 @c FIXME...or change desc of rule---eg "state of prog and debugging session"?
1839 Here are three miscellaneous @code{show} subcommands, all of which are
1840 exceptional in lacking corresponding @code{set} commands:
1843 @kindex show version
1844 @cindex @value{GDBN} version number
1846 Show what version of @value{GDBN} is running. You should include this
1847 information in @value{GDBN} bug-reports. If multiple versions of
1848 @value{GDBN} are in use at your site, you may need to determine which
1849 version of @value{GDBN} you are running; as @value{GDBN} evolves, new
1850 commands are introduced, and old ones may wither away. Also, many
1851 system vendors ship variant versions of @value{GDBN}, and there are
1852 variant versions of @value{GDBN} in @sc{gnu}/Linux distributions as well.
1853 The version number is the same as the one announced when you start
1856 @kindex show copying
1857 @kindex info copying
1858 @cindex display @value{GDBN} copyright
1861 Display information about permission for copying @value{GDBN}.
1863 @kindex show warranty
1864 @kindex info warranty
1866 @itemx info warranty
1867 Display the @sc{gnu} ``NO WARRANTY'' statement, or a warranty,
1868 if your version of @value{GDBN} comes with one.
1873 @chapter Running Programs Under @value{GDBN}
1875 When you run a program under @value{GDBN}, you must first generate
1876 debugging information when you compile it.
1878 You may start @value{GDBN} with its arguments, if any, in an environment
1879 of your choice. If you are doing native debugging, you may redirect
1880 your program's input and output, debug an already running process, or
1881 kill a child process.
1884 * Compilation:: Compiling for debugging
1885 * Starting:: Starting your program
1886 * Arguments:: Your program's arguments
1887 * Environment:: Your program's environment
1889 * Working Directory:: Your program's working directory
1890 * Input/Output:: Your program's input and output
1891 * Attach:: Debugging an already-running process
1892 * Kill Process:: Killing the child process
1894 * Inferiors and Programs:: Debugging multiple inferiors and programs
1895 * Threads:: Debugging programs with multiple threads
1896 * Forks:: Debugging forks
1897 * Checkpoint/Restart:: Setting a @emph{bookmark} to return to later
1901 @section Compiling for Debugging
1903 In order to debug a program effectively, you need to generate
1904 debugging information when you compile it. This debugging information
1905 is stored in the object file; it describes the data type of each
1906 variable or function and the correspondence between source line numbers
1907 and addresses in the executable code.
1909 To request debugging information, specify the @samp{-g} option when you run
1912 Programs that are to be shipped to your customers are compiled with
1913 optimizations, using the @samp{-O} compiler option. However, some
1914 compilers are unable to handle the @samp{-g} and @samp{-O} options
1915 together. Using those compilers, you cannot generate optimized
1916 executables containing debugging information.
1918 @value{NGCC}, the @sc{gnu} C/C@t{++} compiler, supports @samp{-g} with or
1919 without @samp{-O}, making it possible to debug optimized code. We
1920 recommend that you @emph{always} use @samp{-g} whenever you compile a
1921 program. You may think your program is correct, but there is no sense
1922 in pushing your luck. For more information, see @ref{Optimized Code}.
1924 Older versions of the @sc{gnu} C compiler permitted a variant option
1925 @w{@samp{-gg}} for debugging information. @value{GDBN} no longer supports this
1926 format; if your @sc{gnu} C compiler has this option, do not use it.
1928 @value{GDBN} knows about preprocessor macros and can show you their
1929 expansion (@pxref{Macros}). Most compilers do not include information
1930 about preprocessor macros in the debugging information if you specify
1931 the @option{-g} flag alone. Version 3.1 and later of @value{NGCC},
1932 the @sc{gnu} C compiler, provides macro information if you are using
1933 the DWARF debugging format, and specify the option @option{-g3}.
1935 @xref{Debugging Options,,Options for Debugging Your Program or GCC,
1936 gcc.info, Using the @sc{gnu} Compiler Collection (GCC)}, for more
1937 information on @value{NGCC} options affecting debug information.
1939 You will have the best debugging experience if you use the latest
1940 version of the DWARF debugging format that your compiler supports.
1941 DWARF is currently the most expressive and best supported debugging
1942 format in @value{GDBN}.
1946 @section Starting your Program
1952 @kindex r @r{(@code{run})}
1955 Use the @code{run} command to start your program under @value{GDBN}.
1956 You must first specify the program name (except on VxWorks) with an
1957 argument to @value{GDBN} (@pxref{Invocation, ,Getting In and Out of
1958 @value{GDBN}}), or by using the @code{file} or @code{exec-file} command
1959 (@pxref{Files, ,Commands to Specify Files}).
1963 If you are running your program in an execution environment that
1964 supports processes, @code{run} creates an inferior process and makes
1965 that process run your program. In some environments without processes,
1966 @code{run} jumps to the start of your program. Other targets,
1967 like @samp{remote}, are always running. If you get an error
1968 message like this one:
1971 The "remote" target does not support "run".
1972 Try "help target" or "continue".
1976 then use @code{continue} to run your program. You may need @code{load}
1977 first (@pxref{load}).
1979 The execution of a program is affected by certain information it
1980 receives from its superior. @value{GDBN} provides ways to specify this
1981 information, which you must do @emph{before} starting your program. (You
1982 can change it after starting your program, but such changes only affect
1983 your program the next time you start it.) This information may be
1984 divided into four categories:
1987 @item The @emph{arguments.}
1988 Specify the arguments to give your program as the arguments of the
1989 @code{run} command. If a shell is available on your target, the shell
1990 is used to pass the arguments, so that you may use normal conventions
1991 (such as wildcard expansion or variable substitution) in describing
1993 In Unix systems, you can control which shell is used with the
1994 @code{SHELL} environment variable.
1995 @xref{Arguments, ,Your Program's Arguments}.
1997 @item The @emph{environment.}
1998 Your program normally inherits its environment from @value{GDBN}, but you can
1999 use the @value{GDBN} commands @code{set environment} and @code{unset
2000 environment} to change parts of the environment that affect
2001 your program. @xref{Environment, ,Your Program's Environment}.
2003 @item The @emph{working directory.}
2004 Your program inherits its working directory from @value{GDBN}. You can set
2005 the @value{GDBN} working directory with the @code{cd} command in @value{GDBN}.
2006 @xref{Working Directory, ,Your Program's Working Directory}.
2008 @item The @emph{standard input and output.}
2009 Your program normally uses the same device for standard input and
2010 standard output as @value{GDBN} is using. You can redirect input and output
2011 in the @code{run} command line, or you can use the @code{tty} command to
2012 set a different device for your program.
2013 @xref{Input/Output, ,Your Program's Input and Output}.
2016 @emph{Warning:} While input and output redirection work, you cannot use
2017 pipes to pass the output of the program you are debugging to another
2018 program; if you attempt this, @value{GDBN} is likely to wind up debugging the
2022 When you issue the @code{run} command, your program begins to execute
2023 immediately. @xref{Stopping, ,Stopping and Continuing}, for discussion
2024 of how to arrange for your program to stop. Once your program has
2025 stopped, you may call functions in your program, using the @code{print}
2026 or @code{call} commands. @xref{Data, ,Examining Data}.
2028 If the modification time of your symbol file has changed since the last
2029 time @value{GDBN} read its symbols, @value{GDBN} discards its symbol
2030 table, and reads it again. When it does this, @value{GDBN} tries to retain
2031 your current breakpoints.
2036 @cindex run to main procedure
2037 The name of the main procedure can vary from language to language.
2038 With C or C@t{++}, the main procedure name is always @code{main}, but
2039 other languages such as Ada do not require a specific name for their
2040 main procedure. The debugger provides a convenient way to start the
2041 execution of the program and to stop at the beginning of the main
2042 procedure, depending on the language used.
2044 The @samp{start} command does the equivalent of setting a temporary
2045 breakpoint at the beginning of the main procedure and then invoking
2046 the @samp{run} command.
2048 @cindex elaboration phase
2049 Some programs contain an @dfn{elaboration} phase where some startup code is
2050 executed before the main procedure is called. This depends on the
2051 languages used to write your program. In C@t{++}, for instance,
2052 constructors for static and global objects are executed before
2053 @code{main} is called. It is therefore possible that the debugger stops
2054 before reaching the main procedure. However, the temporary breakpoint
2055 will remain to halt execution.
2057 Specify the arguments to give to your program as arguments to the
2058 @samp{start} command. These arguments will be given verbatim to the
2059 underlying @samp{run} command. Note that the same arguments will be
2060 reused if no argument is provided during subsequent calls to
2061 @samp{start} or @samp{run}.
2063 It is sometimes necessary to debug the program during elaboration. In
2064 these cases, using the @code{start} command would stop the execution of
2065 your program too late, as the program would have already completed the
2066 elaboration phase. Under these circumstances, insert breakpoints in your
2067 elaboration code before running your program.
2069 @kindex set exec-wrapper
2070 @item set exec-wrapper @var{wrapper}
2071 @itemx show exec-wrapper
2072 @itemx unset exec-wrapper
2073 When @samp{exec-wrapper} is set, the specified wrapper is used to
2074 launch programs for debugging. @value{GDBN} starts your program
2075 with a shell command of the form @kbd{exec @var{wrapper}
2076 @var{program}}. Quoting is added to @var{program} and its
2077 arguments, but not to @var{wrapper}, so you should add quotes if
2078 appropriate for your shell. The wrapper runs until it executes
2079 your program, and then @value{GDBN} takes control.
2081 You can use any program that eventually calls @code{execve} with
2082 its arguments as a wrapper. Several standard Unix utilities do
2083 this, e.g.@: @code{env} and @code{nohup}. Any Unix shell script ending
2084 with @code{exec "$@@"} will also work.
2086 For example, you can use @code{env} to pass an environment variable to
2087 the debugged program, without setting the variable in your shell's
2091 (@value{GDBP}) set exec-wrapper env 'LD_PRELOAD=libtest.so'
2095 This command is available when debugging locally on most targets, excluding
2096 @sc{djgpp}, Cygwin, MS Windows, and QNX Neutrino.
2098 @kindex set disable-randomization
2099 @item set disable-randomization
2100 @itemx set disable-randomization on
2101 This option (enabled by default in @value{GDBN}) will turn off the native
2102 randomization of the virtual address space of the started program. This option
2103 is useful for multiple debugging sessions to make the execution better
2104 reproducible and memory addresses reusable across debugging sessions.
2106 This feature is implemented only on certain targets, including @sc{gnu}/Linux.
2107 On @sc{gnu}/Linux you can get the same behavior using
2110 (@value{GDBP}) set exec-wrapper setarch `uname -m` -R
2113 @item set disable-randomization off
2114 Leave the behavior of the started executable unchanged. Some bugs rear their
2115 ugly heads only when the program is loaded at certain addresses. If your bug
2116 disappears when you run the program under @value{GDBN}, that might be because
2117 @value{GDBN} by default disables the address randomization on platforms, such
2118 as @sc{gnu}/Linux, which do that for stand-alone programs. Use @kbd{set
2119 disable-randomization off} to try to reproduce such elusive bugs.
2121 On targets where it is available, virtual address space randomization
2122 protects the programs against certain kinds of security attacks. In these
2123 cases the attacker needs to know the exact location of a concrete executable
2124 code. Randomizing its location makes it impossible to inject jumps misusing
2125 a code at its expected addresses.
2127 Prelinking shared libraries provides a startup performance advantage but it
2128 makes addresses in these libraries predictable for privileged processes by
2129 having just unprivileged access at the target system. Reading the shared
2130 library binary gives enough information for assembling the malicious code
2131 misusing it. Still even a prelinked shared library can get loaded at a new
2132 random address just requiring the regular relocation process during the
2133 startup. Shared libraries not already prelinked are always loaded at
2134 a randomly chosen address.
2136 Position independent executables (PIE) contain position independent code
2137 similar to the shared libraries and therefore such executables get loaded at
2138 a randomly chosen address upon startup. PIE executables always load even
2139 already prelinked shared libraries at a random address. You can build such
2140 executable using @command{gcc -fPIE -pie}.
2142 Heap (malloc storage), stack and custom mmap areas are always placed randomly
2143 (as long as the randomization is enabled).
2145 @item show disable-randomization
2146 Show the current setting of the explicit disable of the native randomization of
2147 the virtual address space of the started program.
2152 @section Your Program's Arguments
2154 @cindex arguments (to your program)
2155 The arguments to your program can be specified by the arguments of the
2157 They are passed to a shell, which expands wildcard characters and
2158 performs redirection of I/O, and thence to your program. Your
2159 @code{SHELL} environment variable (if it exists) specifies what shell
2160 @value{GDBN} uses. If you do not define @code{SHELL}, @value{GDBN} uses
2161 the default shell (@file{/bin/sh} on Unix).
2163 On non-Unix systems, the program is usually invoked directly by
2164 @value{GDBN}, which emulates I/O redirection via the appropriate system
2165 calls, and the wildcard characters are expanded by the startup code of
2166 the program, not by the shell.
2168 @code{run} with no arguments uses the same arguments used by the previous
2169 @code{run}, or those set by the @code{set args} command.
2174 Specify the arguments to be used the next time your program is run. If
2175 @code{set args} has no arguments, @code{run} executes your program
2176 with no arguments. Once you have run your program with arguments,
2177 using @code{set args} before the next @code{run} is the only way to run
2178 it again without arguments.
2182 Show the arguments to give your program when it is started.
2186 @section Your Program's Environment
2188 @cindex environment (of your program)
2189 The @dfn{environment} consists of a set of environment variables and
2190 their values. Environment variables conventionally record such things as
2191 your user name, your home directory, your terminal type, and your search
2192 path for programs to run. Usually you set up environment variables with
2193 the shell and they are inherited by all the other programs you run. When
2194 debugging, it can be useful to try running your program with a modified
2195 environment without having to start @value{GDBN} over again.
2199 @item path @var{directory}
2200 Add @var{directory} to the front of the @code{PATH} environment variable
2201 (the search path for executables) that will be passed to your program.
2202 The value of @code{PATH} used by @value{GDBN} does not change.
2203 You may specify several directory names, separated by whitespace or by a
2204 system-dependent separator character (@samp{:} on Unix, @samp{;} on
2205 MS-DOS and MS-Windows). If @var{directory} is already in the path, it
2206 is moved to the front, so it is searched sooner.
2208 You can use the string @samp{$cwd} to refer to whatever is the current
2209 working directory at the time @value{GDBN} searches the path. If you
2210 use @samp{.} instead, it refers to the directory where you executed the
2211 @code{path} command. @value{GDBN} replaces @samp{.} in the
2212 @var{directory} argument (with the current path) before adding
2213 @var{directory} to the search path.
2214 @c 'path' is explicitly nonrepeatable, but RMS points out it is silly to
2215 @c document that, since repeating it would be a no-op.
2219 Display the list of search paths for executables (the @code{PATH}
2220 environment variable).
2222 @kindex show environment
2223 @item show environment @r{[}@var{varname}@r{]}
2224 Print the value of environment variable @var{varname} to be given to
2225 your program when it starts. If you do not supply @var{varname},
2226 print the names and values of all environment variables to be given to
2227 your program. You can abbreviate @code{environment} as @code{env}.
2229 @kindex set environment
2230 @item set environment @var{varname} @r{[}=@var{value}@r{]}
2231 Set environment variable @var{varname} to @var{value}. The value
2232 changes for your program only, not for @value{GDBN} itself. @var{value} may
2233 be any string; the values of environment variables are just strings, and
2234 any interpretation is supplied by your program itself. The @var{value}
2235 parameter is optional; if it is eliminated, the variable is set to a
2237 @c "any string" here does not include leading, trailing
2238 @c blanks. Gnu asks: does anyone care?
2240 For example, this command:
2247 tells the debugged program, when subsequently run, that its user is named
2248 @samp{foo}. (The spaces around @samp{=} are used for clarity here; they
2249 are not actually required.)
2251 @kindex unset environment
2252 @item unset environment @var{varname}
2253 Remove variable @var{varname} from the environment to be passed to your
2254 program. This is different from @samp{set env @var{varname} =};
2255 @code{unset environment} removes the variable from the environment,
2256 rather than assigning it an empty value.
2259 @emph{Warning:} On Unix systems, @value{GDBN} runs your program using
2261 by your @code{SHELL} environment variable if it exists (or
2262 @code{/bin/sh} if not). If your @code{SHELL} variable names a shell
2263 that runs an initialization file---such as @file{.cshrc} for C-shell, or
2264 @file{.bashrc} for BASH---any variables you set in that file affect
2265 your program. You may wish to move setting of environment variables to
2266 files that are only run when you sign on, such as @file{.login} or
2269 @node Working Directory
2270 @section Your Program's Working Directory
2272 @cindex working directory (of your program)
2273 Each time you start your program with @code{run}, it inherits its
2274 working directory from the current working directory of @value{GDBN}.
2275 The @value{GDBN} working directory is initially whatever it inherited
2276 from its parent process (typically the shell), but you can specify a new
2277 working directory in @value{GDBN} with the @code{cd} command.
2279 The @value{GDBN} working directory also serves as a default for the commands
2280 that specify files for @value{GDBN} to operate on. @xref{Files, ,Commands to
2285 @cindex change working directory
2286 @item cd @r{[}@var{directory}@r{]}
2287 Set the @value{GDBN} working directory to @var{directory}. If not
2288 given, @var{directory} uses @file{'~'}.
2292 Print the @value{GDBN} working directory.
2295 It is generally impossible to find the current working directory of
2296 the process being debugged (since a program can change its directory
2297 during its run). If you work on a system where @value{GDBN} is
2298 configured with the @file{/proc} support, you can use the @code{info
2299 proc} command (@pxref{SVR4 Process Information}) to find out the
2300 current working directory of the debuggee.
2303 @section Your Program's Input and Output
2308 By default, the program you run under @value{GDBN} does input and output to
2309 the same terminal that @value{GDBN} uses. @value{GDBN} switches the terminal
2310 to its own terminal modes to interact with you, but it records the terminal
2311 modes your program was using and switches back to them when you continue
2312 running your program.
2315 @kindex info terminal
2317 Displays information recorded by @value{GDBN} about the terminal modes your
2321 You can redirect your program's input and/or output using shell
2322 redirection with the @code{run} command. For example,
2329 starts your program, diverting its output to the file @file{outfile}.
2332 @cindex controlling terminal
2333 Another way to specify where your program should do input and output is
2334 with the @code{tty} command. This command accepts a file name as
2335 argument, and causes this file to be the default for future @code{run}
2336 commands. It also resets the controlling terminal for the child
2337 process, for future @code{run} commands. For example,
2344 directs that processes started with subsequent @code{run} commands
2345 default to do input and output on the terminal @file{/dev/ttyb} and have
2346 that as their controlling terminal.
2348 An explicit redirection in @code{run} overrides the @code{tty} command's
2349 effect on the input/output device, but not its effect on the controlling
2352 When you use the @code{tty} command or redirect input in the @code{run}
2353 command, only the input @emph{for your program} is affected. The input
2354 for @value{GDBN} still comes from your terminal. @code{tty} is an alias
2355 for @code{set inferior-tty}.
2357 @cindex inferior tty
2358 @cindex set inferior controlling terminal
2359 You can use the @code{show inferior-tty} command to tell @value{GDBN} to
2360 display the name of the terminal that will be used for future runs of your
2364 @item set inferior-tty /dev/ttyb
2365 @kindex set inferior-tty
2366 Set the tty for the program being debugged to /dev/ttyb.
2368 @item show inferior-tty
2369 @kindex show inferior-tty
2370 Show the current tty for the program being debugged.
2374 @section Debugging an Already-running Process
2379 @item attach @var{process-id}
2380 This command attaches to a running process---one that was started
2381 outside @value{GDBN}. (@code{info files} shows your active
2382 targets.) The command takes as argument a process ID. The usual way to
2383 find out the @var{process-id} of a Unix process is with the @code{ps} utility,
2384 or with the @samp{jobs -l} shell command.
2386 @code{attach} does not repeat if you press @key{RET} a second time after
2387 executing the command.
2390 To use @code{attach}, your program must be running in an environment
2391 which supports processes; for example, @code{attach} does not work for
2392 programs on bare-board targets that lack an operating system. You must
2393 also have permission to send the process a signal.
2395 When you use @code{attach}, the debugger finds the program running in
2396 the process first by looking in the current working directory, then (if
2397 the program is not found) by using the source file search path
2398 (@pxref{Source Path, ,Specifying Source Directories}). You can also use
2399 the @code{file} command to load the program. @xref{Files, ,Commands to
2402 The first thing @value{GDBN} does after arranging to debug the specified
2403 process is to stop it. You can examine and modify an attached process
2404 with all the @value{GDBN} commands that are ordinarily available when
2405 you start processes with @code{run}. You can insert breakpoints; you
2406 can step and continue; you can modify storage. If you would rather the
2407 process continue running, you may use the @code{continue} command after
2408 attaching @value{GDBN} to the process.
2413 When you have finished debugging the attached process, you can use the
2414 @code{detach} command to release it from @value{GDBN} control. Detaching
2415 the process continues its execution. After the @code{detach} command,
2416 that process and @value{GDBN} become completely independent once more, and you
2417 are ready to @code{attach} another process or start one with @code{run}.
2418 @code{detach} does not repeat if you press @key{RET} again after
2419 executing the command.
2422 If you exit @value{GDBN} while you have an attached process, you detach
2423 that process. If you use the @code{run} command, you kill that process.
2424 By default, @value{GDBN} asks for confirmation if you try to do either of these
2425 things; you can control whether or not you need to confirm by using the
2426 @code{set confirm} command (@pxref{Messages/Warnings, ,Optional Warnings and
2430 @section Killing the Child Process
2435 Kill the child process in which your program is running under @value{GDBN}.
2438 This command is useful if you wish to debug a core dump instead of a
2439 running process. @value{GDBN} ignores any core dump file while your program
2442 On some operating systems, a program cannot be executed outside @value{GDBN}
2443 while you have breakpoints set on it inside @value{GDBN}. You can use the
2444 @code{kill} command in this situation to permit running your program
2445 outside the debugger.
2447 The @code{kill} command is also useful if you wish to recompile and
2448 relink your program, since on many systems it is impossible to modify an
2449 executable file while it is running in a process. In this case, when you
2450 next type @code{run}, @value{GDBN} notices that the file has changed, and
2451 reads the symbol table again (while trying to preserve your current
2452 breakpoint settings).
2454 @node Inferiors and Programs
2455 @section Debugging Multiple Inferiors and Programs
2457 @value{GDBN} lets you run and debug multiple programs in a single
2458 session. In addition, @value{GDBN} on some systems may let you run
2459 several programs simultaneously (otherwise you have to exit from one
2460 before starting another). In the most general case, you can have
2461 multiple threads of execution in each of multiple processes, launched
2462 from multiple executables.
2465 @value{GDBN} represents the state of each program execution with an
2466 object called an @dfn{inferior}. An inferior typically corresponds to
2467 a process, but is more general and applies also to targets that do not
2468 have processes. Inferiors may be created before a process runs, and
2469 may be retained after a process exits. Inferiors have unique
2470 identifiers that are different from process ids. Usually each
2471 inferior will also have its own distinct address space, although some
2472 embedded targets may have several inferiors running in different parts
2473 of a single address space. Each inferior may in turn have multiple
2474 threads running in it.
2476 To find out what inferiors exist at any moment, use @w{@code{info
2480 @kindex info inferiors
2481 @item info inferiors
2482 Print a list of all inferiors currently being managed by @value{GDBN}.
2484 @value{GDBN} displays for each inferior (in this order):
2488 the inferior number assigned by @value{GDBN}
2491 the target system's inferior identifier
2494 the name of the executable the inferior is running.
2499 An asterisk @samp{*} preceding the @value{GDBN} inferior number
2500 indicates the current inferior.
2504 @c end table here to get a little more width for example
2507 (@value{GDBP}) info inferiors
2508 Num Description Executable
2509 2 process 2307 hello
2510 * 1 process 3401 goodbye
2513 To switch focus between inferiors, use the @code{inferior} command:
2516 @kindex inferior @var{infno}
2517 @item inferior @var{infno}
2518 Make inferior number @var{infno} the current inferior. The argument
2519 @var{infno} is the inferior number assigned by @value{GDBN}, as shown
2520 in the first field of the @samp{info inferiors} display.
2524 You can get multiple executables into a debugging session via the
2525 @code{add-inferior} and @w{@code{clone-inferior}} commands. On some
2526 systems @value{GDBN} can add inferiors to the debug session
2527 automatically by following calls to @code{fork} and @code{exec}. To
2528 remove inferiors from the debugging session use the
2529 @w{@code{remove-inferiors}} command.
2532 @kindex add-inferior
2533 @item add-inferior [ -copies @var{n} ] [ -exec @var{executable} ]
2534 Adds @var{n} inferiors to be run using @var{executable} as the
2535 executable. @var{n} defaults to 1. If no executable is specified,
2536 the inferiors begins empty, with no program. You can still assign or
2537 change the program assigned to the inferior at any time by using the
2538 @code{file} command with the executable name as its argument.
2540 @kindex clone-inferior
2541 @item clone-inferior [ -copies @var{n} ] [ @var{infno} ]
2542 Adds @var{n} inferiors ready to execute the same program as inferior
2543 @var{infno}. @var{n} defaults to 1. @var{infno} defaults to the
2544 number of the current inferior. This is a convenient command when you
2545 want to run another instance of the inferior you are debugging.
2548 (@value{GDBP}) info inferiors
2549 Num Description Executable
2550 * 1 process 29964 helloworld
2551 (@value{GDBP}) clone-inferior
2554 (@value{GDBP}) info inferiors
2555 Num Description Executable
2557 * 1 process 29964 helloworld
2560 You can now simply switch focus to inferior 2 and run it.
2562 @kindex remove-inferiors
2563 @item remove-inferiors @var{infno}@dots{}
2564 Removes the inferior or inferiors @var{infno}@dots{}. It is not
2565 possible to remove an inferior that is running with this command. For
2566 those, use the @code{kill} or @code{detach} command first.
2570 To quit debugging one of the running inferiors that is not the current
2571 inferior, you can either detach from it by using the @w{@code{detach
2572 inferior}} command (allowing it to run independently), or kill it
2573 using the @w{@code{kill inferiors}} command:
2576 @kindex detach inferiors @var{infno}@dots{}
2577 @item detach inferior @var{infno}@dots{}
2578 Detach from the inferior or inferiors identified by @value{GDBN}
2579 inferior number(s) @var{infno}@dots{}. Note that the inferior's entry
2580 still stays on the list of inferiors shown by @code{info inferiors},
2581 but its Description will show @samp{<null>}.
2583 @kindex kill inferiors @var{infno}@dots{}
2584 @item kill inferiors @var{infno}@dots{}
2585 Kill the inferior or inferiors identified by @value{GDBN} inferior
2586 number(s) @var{infno}@dots{}. Note that the inferior's entry still
2587 stays on the list of inferiors shown by @code{info inferiors}, but its
2588 Description will show @samp{<null>}.
2591 After the successful completion of a command such as @code{detach},
2592 @code{detach inferiors}, @code{kill} or @code{kill inferiors}, or after
2593 a normal process exit, the inferior is still valid and listed with
2594 @code{info inferiors}, ready to be restarted.
2597 To be notified when inferiors are started or exit under @value{GDBN}'s
2598 control use @w{@code{set print inferior-events}}:
2601 @kindex set print inferior-events
2602 @cindex print messages on inferior start and exit
2603 @item set print inferior-events
2604 @itemx set print inferior-events on
2605 @itemx set print inferior-events off
2606 The @code{set print inferior-events} command allows you to enable or
2607 disable printing of messages when @value{GDBN} notices that new
2608 inferiors have started or that inferiors have exited or have been
2609 detached. By default, these messages will not be printed.
2611 @kindex show print inferior-events
2612 @item show print inferior-events
2613 Show whether messages will be printed when @value{GDBN} detects that
2614 inferiors have started, exited or have been detached.
2617 Many commands will work the same with multiple programs as with a
2618 single program: e.g., @code{print myglobal} will simply display the
2619 value of @code{myglobal} in the current inferior.
2622 Occasionaly, when debugging @value{GDBN} itself, it may be useful to
2623 get more info about the relationship of inferiors, programs, address
2624 spaces in a debug session. You can do that with the @w{@code{maint
2625 info program-spaces}} command.
2628 @kindex maint info program-spaces
2629 @item maint info program-spaces
2630 Print a list of all program spaces currently being managed by
2633 @value{GDBN} displays for each program space (in this order):
2637 the program space number assigned by @value{GDBN}
2640 the name of the executable loaded into the program space, with e.g.,
2641 the @code{file} command.
2646 An asterisk @samp{*} preceding the @value{GDBN} program space number
2647 indicates the current program space.
2649 In addition, below each program space line, @value{GDBN} prints extra
2650 information that isn't suitable to display in tabular form. For
2651 example, the list of inferiors bound to the program space.
2654 (@value{GDBP}) maint info program-spaces
2657 Bound inferiors: ID 1 (process 21561)
2661 Here we can see that no inferior is running the program @code{hello},
2662 while @code{process 21561} is running the program @code{goodbye}. On
2663 some targets, it is possible that multiple inferiors are bound to the
2664 same program space. The most common example is that of debugging both
2665 the parent and child processes of a @code{vfork} call. For example,
2668 (@value{GDBP}) maint info program-spaces
2671 Bound inferiors: ID 2 (process 18050), ID 1 (process 18045)
2674 Here, both inferior 2 and inferior 1 are running in the same program
2675 space as a result of inferior 1 having executed a @code{vfork} call.
2679 @section Debugging Programs with Multiple Threads
2681 @cindex threads of execution
2682 @cindex multiple threads
2683 @cindex switching threads
2684 In some operating systems, such as HP-UX and Solaris, a single program
2685 may have more than one @dfn{thread} of execution. The precise semantics
2686 of threads differ from one operating system to another, but in general
2687 the threads of a single program are akin to multiple processes---except
2688 that they share one address space (that is, they can all examine and
2689 modify the same variables). On the other hand, each thread has its own
2690 registers and execution stack, and perhaps private memory.
2692 @value{GDBN} provides these facilities for debugging multi-thread
2696 @item automatic notification of new threads
2697 @item @samp{thread @var{threadno}}, a command to switch among threads
2698 @item @samp{info threads}, a command to inquire about existing threads
2699 @item @samp{thread apply [@var{threadno}] [@var{all}] @var{args}},
2700 a command to apply a command to a list of threads
2701 @item thread-specific breakpoints
2702 @item @samp{set print thread-events}, which controls printing of
2703 messages on thread start and exit.
2704 @item @samp{set libthread-db-search-path @var{path}}, which lets
2705 the user specify which @code{libthread_db} to use if the default choice
2706 isn't compatible with the program.
2710 @emph{Warning:} These facilities are not yet available on every
2711 @value{GDBN} configuration where the operating system supports threads.
2712 If your @value{GDBN} does not support threads, these commands have no
2713 effect. For example, a system without thread support shows no output
2714 from @samp{info threads}, and always rejects the @code{thread} command,
2718 (@value{GDBP}) info threads
2719 (@value{GDBP}) thread 1
2720 Thread ID 1 not known. Use the "info threads" command to
2721 see the IDs of currently known threads.
2723 @c FIXME to implementors: how hard would it be to say "sorry, this GDB
2724 @c doesn't support threads"?
2727 @cindex focus of debugging
2728 @cindex current thread
2729 The @value{GDBN} thread debugging facility allows you to observe all
2730 threads while your program runs---but whenever @value{GDBN} takes
2731 control, one thread in particular is always the focus of debugging.
2732 This thread is called the @dfn{current thread}. Debugging commands show
2733 program information from the perspective of the current thread.
2735 @cindex @code{New} @var{systag} message
2736 @cindex thread identifier (system)
2737 @c FIXME-implementors!! It would be more helpful if the [New...] message
2738 @c included GDB's numeric thread handle, so you could just go to that
2739 @c thread without first checking `info threads'.
2740 Whenever @value{GDBN} detects a new thread in your program, it displays
2741 the target system's identification for the thread with a message in the
2742 form @samp{[New @var{systag}]}. @var{systag} is a thread identifier
2743 whose form varies depending on the particular system. For example, on
2744 @sc{gnu}/Linux, you might see
2747 [New Thread 0x41e02940 (LWP 25582)]
2751 when @value{GDBN} notices a new thread. In contrast, on an SGI system,
2752 the @var{systag} is simply something like @samp{process 368}, with no
2755 @c FIXME!! (1) Does the [New...] message appear even for the very first
2756 @c thread of a program, or does it only appear for the
2757 @c second---i.e.@: when it becomes obvious we have a multithread
2759 @c (2) *Is* there necessarily a first thread always? Or do some
2760 @c multithread systems permit starting a program with multiple
2761 @c threads ab initio?
2763 @cindex thread number
2764 @cindex thread identifier (GDB)
2765 For debugging purposes, @value{GDBN} associates its own thread
2766 number---always a single integer---with each thread in your program.
2769 @kindex info threads
2770 @item info threads @r{[}@var{id}@dots{}@r{]}
2771 Display a summary of all threads currently in your program. Optional
2772 argument @var{id}@dots{} is one or more thread ids separated by spaces, and
2773 means to print information only about the specified thread or threads.
2774 @value{GDBN} displays for each thread (in this order):
2778 the thread number assigned by @value{GDBN}
2781 the target system's thread identifier (@var{systag})
2784 the thread's name, if one is known. A thread can either be named by
2785 the user (see @code{thread name}, below), or, in some cases, by the
2789 the current stack frame summary for that thread
2793 An asterisk @samp{*} to the left of the @value{GDBN} thread number
2794 indicates the current thread.
2798 @c end table here to get a little more width for example
2801 (@value{GDBP}) info threads
2803 3 process 35 thread 27 0x34e5 in sigpause ()
2804 2 process 35 thread 23 0x34e5 in sigpause ()
2805 * 1 process 35 thread 13 main (argc=1, argv=0x7ffffff8)
2809 On Solaris, you can display more information about user threads with a
2810 Solaris-specific command:
2813 @item maint info sol-threads
2814 @kindex maint info sol-threads
2815 @cindex thread info (Solaris)
2816 Display info on Solaris user threads.
2820 @kindex thread @var{threadno}
2821 @item thread @var{threadno}
2822 Make thread number @var{threadno} the current thread. The command
2823 argument @var{threadno} is the internal @value{GDBN} thread number, as
2824 shown in the first field of the @samp{info threads} display.
2825 @value{GDBN} responds by displaying the system identifier of the thread
2826 you selected, and its current stack frame summary:
2829 (@value{GDBP}) thread 2
2830 [Switching to thread 2 (Thread 0xb7fdab70 (LWP 12747))]
2831 #0 some_function (ignore=0x0) at example.c:8
2832 8 printf ("hello\n");
2836 As with the @samp{[New @dots{}]} message, the form of the text after
2837 @samp{Switching to} depends on your system's conventions for identifying
2840 @vindex $_thread@r{, convenience variable}
2841 The debugger convenience variable @samp{$_thread} contains the number
2842 of the current thread. You may find this useful in writing breakpoint
2843 conditional expressions, command scripts, and so forth. See
2844 @xref{Convenience Vars,, Convenience Variables}, for general
2845 information on convenience variables.
2847 @kindex thread apply
2848 @cindex apply command to several threads
2849 @item thread apply [@var{threadno} | all] @var{command}
2850 The @code{thread apply} command allows you to apply the named
2851 @var{command} to one or more threads. Specify the numbers of the
2852 threads that you want affected with the command argument
2853 @var{threadno}. It can be a single thread number, one of the numbers
2854 shown in the first field of the @samp{info threads} display; or it
2855 could be a range of thread numbers, as in @code{2-4}. To apply a
2856 command to all threads, type @kbd{thread apply all @var{command}}.
2859 @cindex name a thread
2860 @item thread name [@var{name}]
2861 This command assigns a name to the current thread. If no argument is
2862 given, any existing user-specified name is removed. The thread name
2863 appears in the @samp{info threads} display.
2865 On some systems, such as @sc{gnu}/Linux, @value{GDBN} is able to
2866 determine the name of the thread as given by the OS. On these
2867 systems, a name specified with @samp{thread name} will override the
2868 system-give name, and removing the user-specified name will cause
2869 @value{GDBN} to once again display the system-specified name.
2872 @cindex search for a thread
2873 @item thread find [@var{regexp}]
2874 Search for and display thread ids whose name or @var{systag}
2875 matches the supplied regular expression.
2877 As well as being the complement to the @samp{thread name} command,
2878 this command also allows you to identify a thread by its target
2879 @var{systag}. For instance, on @sc{gnu}/Linux, the target @var{systag}
2883 (@value{GDBN}) thread find 26688
2884 Thread 4 has target id 'Thread 0x41e02940 (LWP 26688)'
2885 (@value{GDBN}) info thread 4
2887 4 Thread 0x41e02940 (LWP 26688) 0x00000031ca6cd372 in select ()
2890 @kindex set print thread-events
2891 @cindex print messages on thread start and exit
2892 @item set print thread-events
2893 @itemx set print thread-events on
2894 @itemx set print thread-events off
2895 The @code{set print thread-events} command allows you to enable or
2896 disable printing of messages when @value{GDBN} notices that new threads have
2897 started or that threads have exited. By default, these messages will
2898 be printed if detection of these events is supported by the target.
2899 Note that these messages cannot be disabled on all targets.
2901 @kindex show print thread-events
2902 @item show print thread-events
2903 Show whether messages will be printed when @value{GDBN} detects that threads
2904 have started and exited.
2907 @xref{Thread Stops,,Stopping and Starting Multi-thread Programs}, for
2908 more information about how @value{GDBN} behaves when you stop and start
2909 programs with multiple threads.
2911 @xref{Set Watchpoints,,Setting Watchpoints}, for information about
2912 watchpoints in programs with multiple threads.
2914 @anchor{set libthread-db-search-path}
2916 @kindex set libthread-db-search-path
2917 @cindex search path for @code{libthread_db}
2918 @item set libthread-db-search-path @r{[}@var{path}@r{]}
2919 If this variable is set, @var{path} is a colon-separated list of
2920 directories @value{GDBN} will use to search for @code{libthread_db}.
2921 If you omit @var{path}, @samp{libthread-db-search-path} will be reset to
2922 its default value (@code{$sdir:$pdir} on @sc{gnu}/Linux and Solaris systems).
2923 Internally, the default value comes from the @code{LIBTHREAD_DB_SEARCH_PATH}
2926 On @sc{gnu}/Linux and Solaris systems, @value{GDBN} uses a ``helper''
2927 @code{libthread_db} library to obtain information about threads in the
2928 inferior process. @value{GDBN} will use @samp{libthread-db-search-path}
2929 to find @code{libthread_db}. @value{GDBN} also consults first if inferior
2930 specific thread debugging library loading is enabled
2931 by @samp{set auto-load libthread-db} (@pxref{libthread_db.so.1 file}).
2933 A special entry @samp{$sdir} for @samp{libthread-db-search-path}
2934 refers to the default system directories that are
2935 normally searched for loading shared libraries. The @samp{$sdir} entry
2936 is the only kind not needing to be enabled by @samp{set auto-load libthread-db}
2937 (@pxref{libthread_db.so.1 file}).
2939 A special entry @samp{$pdir} for @samp{libthread-db-search-path}
2940 refers to the directory from which @code{libpthread}
2941 was loaded in the inferior process.
2943 For any @code{libthread_db} library @value{GDBN} finds in above directories,
2944 @value{GDBN} attempts to initialize it with the current inferior process.
2945 If this initialization fails (which could happen because of a version
2946 mismatch between @code{libthread_db} and @code{libpthread}), @value{GDBN}
2947 will unload @code{libthread_db}, and continue with the next directory.
2948 If none of @code{libthread_db} libraries initialize successfully,
2949 @value{GDBN} will issue a warning and thread debugging will be disabled.
2951 Setting @code{libthread-db-search-path} is currently implemented
2952 only on some platforms.
2954 @kindex show libthread-db-search-path
2955 @item show libthread-db-search-path
2956 Display current libthread_db search path.
2958 @kindex set debug libthread-db
2959 @kindex show debug libthread-db
2960 @cindex debugging @code{libthread_db}
2961 @item set debug libthread-db
2962 @itemx show debug libthread-db
2963 Turns on or off display of @code{libthread_db}-related events.
2964 Use @code{1} to enable, @code{0} to disable.
2968 @section Debugging Forks
2970 @cindex fork, debugging programs which call
2971 @cindex multiple processes
2972 @cindex processes, multiple
2973 On most systems, @value{GDBN} has no special support for debugging
2974 programs which create additional processes using the @code{fork}
2975 function. When a program forks, @value{GDBN} will continue to debug the
2976 parent process and the child process will run unimpeded. If you have
2977 set a breakpoint in any code which the child then executes, the child
2978 will get a @code{SIGTRAP} signal which (unless it catches the signal)
2979 will cause it to terminate.
2981 However, if you want to debug the child process there is a workaround
2982 which isn't too painful. Put a call to @code{sleep} in the code which
2983 the child process executes after the fork. It may be useful to sleep
2984 only if a certain environment variable is set, or a certain file exists,
2985 so that the delay need not occur when you don't want to run @value{GDBN}
2986 on the child. While the child is sleeping, use the @code{ps} program to
2987 get its process ID. Then tell @value{GDBN} (a new invocation of
2988 @value{GDBN} if you are also debugging the parent process) to attach to
2989 the child process (@pxref{Attach}). From that point on you can debug
2990 the child process just like any other process which you attached to.
2992 On some systems, @value{GDBN} provides support for debugging programs that
2993 create additional processes using the @code{fork} or @code{vfork} functions.
2994 Currently, the only platforms with this feature are HP-UX (11.x and later
2995 only?) and @sc{gnu}/Linux (kernel version 2.5.60 and later).
2997 By default, when a program forks, @value{GDBN} will continue to debug
2998 the parent process and the child process will run unimpeded.
3000 If you want to follow the child process instead of the parent process,
3001 use the command @w{@code{set follow-fork-mode}}.
3004 @kindex set follow-fork-mode
3005 @item set follow-fork-mode @var{mode}
3006 Set the debugger response to a program call of @code{fork} or
3007 @code{vfork}. A call to @code{fork} or @code{vfork} creates a new
3008 process. The @var{mode} argument can be:
3012 The original process is debugged after a fork. The child process runs
3013 unimpeded. This is the default.
3016 The new process is debugged after a fork. The parent process runs
3021 @kindex show follow-fork-mode
3022 @item show follow-fork-mode
3023 Display the current debugger response to a @code{fork} or @code{vfork} call.
3026 @cindex debugging multiple processes
3027 On Linux, if you want to debug both the parent and child processes, use the
3028 command @w{@code{set detach-on-fork}}.
3031 @kindex set detach-on-fork
3032 @item set detach-on-fork @var{mode}
3033 Tells gdb whether to detach one of the processes after a fork, or
3034 retain debugger control over them both.
3038 The child process (or parent process, depending on the value of
3039 @code{follow-fork-mode}) will be detached and allowed to run
3040 independently. This is the default.
3043 Both processes will be held under the control of @value{GDBN}.
3044 One process (child or parent, depending on the value of
3045 @code{follow-fork-mode}) is debugged as usual, while the other
3050 @kindex show detach-on-fork
3051 @item show detach-on-fork
3052 Show whether detach-on-fork mode is on/off.
3055 If you choose to set @samp{detach-on-fork} mode off, then @value{GDBN}
3056 will retain control of all forked processes (including nested forks).
3057 You can list the forked processes under the control of @value{GDBN} by
3058 using the @w{@code{info inferiors}} command, and switch from one fork
3059 to another by using the @code{inferior} command (@pxref{Inferiors and
3060 Programs, ,Debugging Multiple Inferiors and Programs}).
3062 To quit debugging one of the forked processes, you can either detach
3063 from it by using the @w{@code{detach inferiors}} command (allowing it
3064 to run independently), or kill it using the @w{@code{kill inferiors}}
3065 command. @xref{Inferiors and Programs, ,Debugging Multiple Inferiors
3068 If you ask to debug a child process and a @code{vfork} is followed by an
3069 @code{exec}, @value{GDBN} executes the new target up to the first
3070 breakpoint in the new target. If you have a breakpoint set on
3071 @code{main} in your original program, the breakpoint will also be set on
3072 the child process's @code{main}.
3074 On some systems, when a child process is spawned by @code{vfork}, you
3075 cannot debug the child or parent until an @code{exec} call completes.
3077 If you issue a @code{run} command to @value{GDBN} after an @code{exec}
3078 call executes, the new target restarts. To restart the parent
3079 process, use the @code{file} command with the parent executable name
3080 as its argument. By default, after an @code{exec} call executes,
3081 @value{GDBN} discards the symbols of the previous executable image.
3082 You can change this behaviour with the @w{@code{set follow-exec-mode}}
3086 @kindex set follow-exec-mode
3087 @item set follow-exec-mode @var{mode}
3089 Set debugger response to a program call of @code{exec}. An
3090 @code{exec} call replaces the program image of a process.
3092 @code{follow-exec-mode} can be:
3096 @value{GDBN} creates a new inferior and rebinds the process to this
3097 new inferior. The program the process was running before the
3098 @code{exec} call can be restarted afterwards by restarting the
3104 (@value{GDBP}) info inferiors
3106 Id Description Executable
3109 process 12020 is executing new program: prog2
3110 Program exited normally.
3111 (@value{GDBP}) info inferiors
3112 Id Description Executable
3118 @value{GDBN} keeps the process bound to the same inferior. The new
3119 executable image replaces the previous executable loaded in the
3120 inferior. Restarting the inferior after the @code{exec} call, with
3121 e.g., the @code{run} command, restarts the executable the process was
3122 running after the @code{exec} call. This is the default mode.
3127 (@value{GDBP}) info inferiors
3128 Id Description Executable
3131 process 12020 is executing new program: prog2
3132 Program exited normally.
3133 (@value{GDBP}) info inferiors
3134 Id Description Executable
3141 You can use the @code{catch} command to make @value{GDBN} stop whenever
3142 a @code{fork}, @code{vfork}, or @code{exec} call is made. @xref{Set
3143 Catchpoints, ,Setting Catchpoints}.
3145 @node Checkpoint/Restart
3146 @section Setting a @emph{Bookmark} to Return to Later
3151 @cindex snapshot of a process
3152 @cindex rewind program state
3154 On certain operating systems@footnote{Currently, only
3155 @sc{gnu}/Linux.}, @value{GDBN} is able to save a @dfn{snapshot} of a
3156 program's state, called a @dfn{checkpoint}, and come back to it
3159 Returning to a checkpoint effectively undoes everything that has
3160 happened in the program since the @code{checkpoint} was saved. This
3161 includes changes in memory, registers, and even (within some limits)
3162 system state. Effectively, it is like going back in time to the
3163 moment when the checkpoint was saved.
3165 Thus, if you're stepping thru a program and you think you're
3166 getting close to the point where things go wrong, you can save
3167 a checkpoint. Then, if you accidentally go too far and miss
3168 the critical statement, instead of having to restart your program
3169 from the beginning, you can just go back to the checkpoint and
3170 start again from there.
3172 This can be especially useful if it takes a lot of time or
3173 steps to reach the point where you think the bug occurs.
3175 To use the @code{checkpoint}/@code{restart} method of debugging:
3180 Save a snapshot of the debugged program's current execution state.
3181 The @code{checkpoint} command takes no arguments, but each checkpoint
3182 is assigned a small integer id, similar to a breakpoint id.
3184 @kindex info checkpoints
3185 @item info checkpoints
3186 List the checkpoints that have been saved in the current debugging
3187 session. For each checkpoint, the following information will be
3194 @item Source line, or label
3197 @kindex restart @var{checkpoint-id}
3198 @item restart @var{checkpoint-id}
3199 Restore the program state that was saved as checkpoint number
3200 @var{checkpoint-id}. All program variables, registers, stack frames
3201 etc.@: will be returned to the values that they had when the checkpoint
3202 was saved. In essence, gdb will ``wind back the clock'' to the point
3203 in time when the checkpoint was saved.
3205 Note that breakpoints, @value{GDBN} variables, command history etc.
3206 are not affected by restoring a checkpoint. In general, a checkpoint
3207 only restores things that reside in the program being debugged, not in
3210 @kindex delete checkpoint @var{checkpoint-id}
3211 @item delete checkpoint @var{checkpoint-id}
3212 Delete the previously-saved checkpoint identified by @var{checkpoint-id}.
3216 Returning to a previously saved checkpoint will restore the user state
3217 of the program being debugged, plus a significant subset of the system
3218 (OS) state, including file pointers. It won't ``un-write'' data from
3219 a file, but it will rewind the file pointer to the previous location,
3220 so that the previously written data can be overwritten. For files
3221 opened in read mode, the pointer will also be restored so that the
3222 previously read data can be read again.
3224 Of course, characters that have been sent to a printer (or other
3225 external device) cannot be ``snatched back'', and characters received
3226 from eg.@: a serial device can be removed from internal program buffers,
3227 but they cannot be ``pushed back'' into the serial pipeline, ready to
3228 be received again. Similarly, the actual contents of files that have
3229 been changed cannot be restored (at this time).
3231 However, within those constraints, you actually can ``rewind'' your
3232 program to a previously saved point in time, and begin debugging it
3233 again --- and you can change the course of events so as to debug a
3234 different execution path this time.
3236 @cindex checkpoints and process id
3237 Finally, there is one bit of internal program state that will be
3238 different when you return to a checkpoint --- the program's process
3239 id. Each checkpoint will have a unique process id (or @var{pid}),
3240 and each will be different from the program's original @var{pid}.
3241 If your program has saved a local copy of its process id, this could
3242 potentially pose a problem.
3244 @subsection A Non-obvious Benefit of Using Checkpoints
3246 On some systems such as @sc{gnu}/Linux, address space randomization
3247 is performed on new processes for security reasons. This makes it
3248 difficult or impossible to set a breakpoint, or watchpoint, on an
3249 absolute address if you have to restart the program, since the
3250 absolute location of a symbol will change from one execution to the
3253 A checkpoint, however, is an @emph{identical} copy of a process.
3254 Therefore if you create a checkpoint at (eg.@:) the start of main,
3255 and simply return to that checkpoint instead of restarting the
3256 process, you can avoid the effects of address randomization and
3257 your symbols will all stay in the same place.
3260 @chapter Stopping and Continuing
3262 The principal purposes of using a debugger are so that you can stop your
3263 program before it terminates; or so that, if your program runs into
3264 trouble, you can investigate and find out why.
3266 Inside @value{GDBN}, your program may stop for any of several reasons,
3267 such as a signal, a breakpoint, or reaching a new line after a
3268 @value{GDBN} command such as @code{step}. You may then examine and
3269 change variables, set new breakpoints or remove old ones, and then
3270 continue execution. Usually, the messages shown by @value{GDBN} provide
3271 ample explanation of the status of your program---but you can also
3272 explicitly request this information at any time.
3275 @kindex info program
3277 Display information about the status of your program: whether it is
3278 running or not, what process it is, and why it stopped.
3282 * Breakpoints:: Breakpoints, watchpoints, and catchpoints
3283 * Continuing and Stepping:: Resuming execution
3284 * Skipping Over Functions and Files::
3285 Skipping over functions and files
3287 * Thread Stops:: Stopping and starting multi-thread programs
3291 @section Breakpoints, Watchpoints, and Catchpoints
3294 A @dfn{breakpoint} makes your program stop whenever a certain point in
3295 the program is reached. For each breakpoint, you can add conditions to
3296 control in finer detail whether your program stops. You can set
3297 breakpoints with the @code{break} command and its variants (@pxref{Set
3298 Breaks, ,Setting Breakpoints}), to specify the place where your program
3299 should stop by line number, function name or exact address in the
3302 On some systems, you can set breakpoints in shared libraries before
3303 the executable is run. There is a minor limitation on HP-UX systems:
3304 you must wait until the executable is run in order to set breakpoints
3305 in shared library routines that are not called directly by the program
3306 (for example, routines that are arguments in a @code{pthread_create}
3310 @cindex data breakpoints
3311 @cindex memory tracing
3312 @cindex breakpoint on memory address
3313 @cindex breakpoint on variable modification
3314 A @dfn{watchpoint} is a special breakpoint that stops your program
3315 when the value of an expression changes. The expression may be a value
3316 of a variable, or it could involve values of one or more variables
3317 combined by operators, such as @samp{a + b}. This is sometimes called
3318 @dfn{data breakpoints}. You must use a different command to set
3319 watchpoints (@pxref{Set Watchpoints, ,Setting Watchpoints}), but aside
3320 from that, you can manage a watchpoint like any other breakpoint: you
3321 enable, disable, and delete both breakpoints and watchpoints using the
3324 You can arrange to have values from your program displayed automatically
3325 whenever @value{GDBN} stops at a breakpoint. @xref{Auto Display,,
3329 @cindex breakpoint on events
3330 A @dfn{catchpoint} is another special breakpoint that stops your program
3331 when a certain kind of event occurs, such as the throwing of a C@t{++}
3332 exception or the loading of a library. As with watchpoints, you use a
3333 different command to set a catchpoint (@pxref{Set Catchpoints, ,Setting
3334 Catchpoints}), but aside from that, you can manage a catchpoint like any
3335 other breakpoint. (To stop when your program receives a signal, use the
3336 @code{handle} command; see @ref{Signals, ,Signals}.)
3338 @cindex breakpoint numbers
3339 @cindex numbers for breakpoints
3340 @value{GDBN} assigns a number to each breakpoint, watchpoint, or
3341 catchpoint when you create it; these numbers are successive integers
3342 starting with one. In many of the commands for controlling various
3343 features of breakpoints you use the breakpoint number to say which
3344 breakpoint you want to change. Each breakpoint may be @dfn{enabled} or
3345 @dfn{disabled}; if disabled, it has no effect on your program until you
3348 @cindex breakpoint ranges
3349 @cindex ranges of breakpoints
3350 Some @value{GDBN} commands accept a range of breakpoints on which to
3351 operate. A breakpoint range is either a single breakpoint number, like
3352 @samp{5}, or two such numbers, in increasing order, separated by a
3353 hyphen, like @samp{5-7}. When a breakpoint range is given to a command,
3354 all breakpoints in that range are operated on.
3357 * Set Breaks:: Setting breakpoints
3358 * Set Watchpoints:: Setting watchpoints
3359 * Set Catchpoints:: Setting catchpoints
3360 * Delete Breaks:: Deleting breakpoints
3361 * Disabling:: Disabling breakpoints
3362 * Conditions:: Break conditions
3363 * Break Commands:: Breakpoint command lists
3364 * Dynamic Printf:: Dynamic printf
3365 * Save Breakpoints:: How to save breakpoints in a file
3366 * Static Probe Points:: Listing static probe points
3367 * Error in Breakpoints:: ``Cannot insert breakpoints''
3368 * Breakpoint-related Warnings:: ``Breakpoint address adjusted...''
3372 @subsection Setting Breakpoints
3374 @c FIXME LMB what does GDB do if no code on line of breakpt?
3375 @c consider in particular declaration with/without initialization.
3377 @c FIXME 2 is there stuff on this already? break at fun start, already init?
3380 @kindex b @r{(@code{break})}
3381 @vindex $bpnum@r{, convenience variable}
3382 @cindex latest breakpoint
3383 Breakpoints are set with the @code{break} command (abbreviated
3384 @code{b}). The debugger convenience variable @samp{$bpnum} records the
3385 number of the breakpoint you've set most recently; see @ref{Convenience
3386 Vars,, Convenience Variables}, for a discussion of what you can do with
3387 convenience variables.
3390 @item break @var{location}
3391 Set a breakpoint at the given @var{location}, which can specify a
3392 function name, a line number, or an address of an instruction.
3393 (@xref{Specify Location}, for a list of all the possible ways to
3394 specify a @var{location}.) The breakpoint will stop your program just
3395 before it executes any of the code in the specified @var{location}.
3397 When using source languages that permit overloading of symbols, such as
3398 C@t{++}, a function name may refer to more than one possible place to break.
3399 @xref{Ambiguous Expressions,,Ambiguous Expressions}, for a discussion of
3402 It is also possible to insert a breakpoint that will stop the program
3403 only if a specific thread (@pxref{Thread-Specific Breakpoints})
3404 or a specific task (@pxref{Ada Tasks}) hits that breakpoint.
3407 When called without any arguments, @code{break} sets a breakpoint at
3408 the next instruction to be executed in the selected stack frame
3409 (@pxref{Stack, ,Examining the Stack}). In any selected frame but the
3410 innermost, this makes your program stop as soon as control
3411 returns to that frame. This is similar to the effect of a
3412 @code{finish} command in the frame inside the selected frame---except
3413 that @code{finish} does not leave an active breakpoint. If you use
3414 @code{break} without an argument in the innermost frame, @value{GDBN} stops
3415 the next time it reaches the current location; this may be useful
3418 @value{GDBN} normally ignores breakpoints when it resumes execution, until at
3419 least one instruction has been executed. If it did not do this, you
3420 would be unable to proceed past a breakpoint without first disabling the
3421 breakpoint. This rule applies whether or not the breakpoint already
3422 existed when your program stopped.
3424 @item break @dots{} if @var{cond}
3425 Set a breakpoint with condition @var{cond}; evaluate the expression
3426 @var{cond} each time the breakpoint is reached, and stop only if the
3427 value is nonzero---that is, if @var{cond} evaluates as true.
3428 @samp{@dots{}} stands for one of the possible arguments described
3429 above (or no argument) specifying where to break. @xref{Conditions,
3430 ,Break Conditions}, for more information on breakpoint conditions.
3433 @item tbreak @var{args}
3434 Set a breakpoint enabled only for one stop. @var{args} are the
3435 same as for the @code{break} command, and the breakpoint is set in the same
3436 way, but the breakpoint is automatically deleted after the first time your
3437 program stops there. @xref{Disabling, ,Disabling Breakpoints}.
3440 @cindex hardware breakpoints
3441 @item hbreak @var{args}
3442 Set a hardware-assisted breakpoint. @var{args} are the same as for the
3443 @code{break} command and the breakpoint is set in the same way, but the
3444 breakpoint requires hardware support and some target hardware may not
3445 have this support. The main purpose of this is EPROM/ROM code
3446 debugging, so you can set a breakpoint at an instruction without
3447 changing the instruction. This can be used with the new trap-generation
3448 provided by SPARClite DSU and most x86-based targets. These targets
3449 will generate traps when a program accesses some data or instruction
3450 address that is assigned to the debug registers. However the hardware
3451 breakpoint registers can take a limited number of breakpoints. For
3452 example, on the DSU, only two data breakpoints can be set at a time, and
3453 @value{GDBN} will reject this command if more than two are used. Delete
3454 or disable unused hardware breakpoints before setting new ones
3455 (@pxref{Disabling, ,Disabling Breakpoints}).
3456 @xref{Conditions, ,Break Conditions}.
3457 For remote targets, you can restrict the number of hardware
3458 breakpoints @value{GDBN} will use, see @ref{set remote
3459 hardware-breakpoint-limit}.
3462 @item thbreak @var{args}
3463 Set a hardware-assisted breakpoint enabled only for one stop. @var{args}
3464 are the same as for the @code{hbreak} command and the breakpoint is set in
3465 the same way. However, like the @code{tbreak} command,
3466 the breakpoint is automatically deleted after the
3467 first time your program stops there. Also, like the @code{hbreak}
3468 command, the breakpoint requires hardware support and some target hardware
3469 may not have this support. @xref{Disabling, ,Disabling Breakpoints}.
3470 See also @ref{Conditions, ,Break Conditions}.
3473 @cindex regular expression
3474 @cindex breakpoints at functions matching a regexp
3475 @cindex set breakpoints in many functions
3476 @item rbreak @var{regex}
3477 Set breakpoints on all functions matching the regular expression
3478 @var{regex}. This command sets an unconditional breakpoint on all
3479 matches, printing a list of all breakpoints it set. Once these
3480 breakpoints are set, they are treated just like the breakpoints set with
3481 the @code{break} command. You can delete them, disable them, or make
3482 them conditional the same way as any other breakpoint.
3484 The syntax of the regular expression is the standard one used with tools
3485 like @file{grep}. Note that this is different from the syntax used by
3486 shells, so for instance @code{foo*} matches all functions that include
3487 an @code{fo} followed by zero or more @code{o}s. There is an implicit
3488 @code{.*} leading and trailing the regular expression you supply, so to
3489 match only functions that begin with @code{foo}, use @code{^foo}.
3491 @cindex non-member C@t{++} functions, set breakpoint in
3492 When debugging C@t{++} programs, @code{rbreak} is useful for setting
3493 breakpoints on overloaded functions that are not members of any special
3496 @cindex set breakpoints on all functions
3497 The @code{rbreak} command can be used to set breakpoints in
3498 @strong{all} the functions in a program, like this:
3501 (@value{GDBP}) rbreak .
3504 @item rbreak @var{file}:@var{regex}
3505 If @code{rbreak} is called with a filename qualification, it limits
3506 the search for functions matching the given regular expression to the
3507 specified @var{file}. This can be used, for example, to set breakpoints on
3508 every function in a given file:
3511 (@value{GDBP}) rbreak file.c:.
3514 The colon separating the filename qualifier from the regex may
3515 optionally be surrounded by spaces.
3517 @kindex info breakpoints
3518 @cindex @code{$_} and @code{info breakpoints}
3519 @item info breakpoints @r{[}@var{n}@dots{}@r{]}
3520 @itemx info break @r{[}@var{n}@dots{}@r{]}
3521 Print a table of all breakpoints, watchpoints, and catchpoints set and
3522 not deleted. Optional argument @var{n} means print information only
3523 about the specified breakpoint(s) (or watchpoint(s) or catchpoint(s)).
3524 For each breakpoint, following columns are printed:
3527 @item Breakpoint Numbers
3529 Breakpoint, watchpoint, or catchpoint.
3531 Whether the breakpoint is marked to be disabled or deleted when hit.
3532 @item Enabled or Disabled
3533 Enabled breakpoints are marked with @samp{y}. @samp{n} marks breakpoints
3534 that are not enabled.
3536 Where the breakpoint is in your program, as a memory address. For a
3537 pending breakpoint whose address is not yet known, this field will
3538 contain @samp{<PENDING>}. Such breakpoint won't fire until a shared
3539 library that has the symbol or line referred by breakpoint is loaded.
3540 See below for details. A breakpoint with several locations will
3541 have @samp{<MULTIPLE>} in this field---see below for details.
3543 Where the breakpoint is in the source for your program, as a file and
3544 line number. For a pending breakpoint, the original string passed to
3545 the breakpoint command will be listed as it cannot be resolved until
3546 the appropriate shared library is loaded in the future.
3550 If a breakpoint is conditional, there are two evaluation modes: ``host'' and
3551 ``target''. If mode is ``host'', breakpoint condition evaluation is done by
3552 @value{GDBN} on the host's side. If it is ``target'', then the condition
3553 is evaluated by the target. The @code{info break} command shows
3554 the condition on the line following the affected breakpoint, together with
3555 its condition evaluation mode in between parentheses.
3557 Breakpoint commands, if any, are listed after that. A pending breakpoint is
3558 allowed to have a condition specified for it. The condition is not parsed for
3559 validity until a shared library is loaded that allows the pending
3560 breakpoint to resolve to a valid location.
3563 @code{info break} with a breakpoint
3564 number @var{n} as argument lists only that breakpoint. The
3565 convenience variable @code{$_} and the default examining-address for
3566 the @code{x} command are set to the address of the last breakpoint
3567 listed (@pxref{Memory, ,Examining Memory}).
3570 @code{info break} displays a count of the number of times the breakpoint
3571 has been hit. This is especially useful in conjunction with the
3572 @code{ignore} command. You can ignore a large number of breakpoint
3573 hits, look at the breakpoint info to see how many times the breakpoint
3574 was hit, and then run again, ignoring one less than that number. This
3575 will get you quickly to the last hit of that breakpoint.
3578 For a breakpoints with an enable count (xref) greater than 1,
3579 @code{info break} also displays that count.
3583 @value{GDBN} allows you to set any number of breakpoints at the same place in
3584 your program. There is nothing silly or meaningless about this. When
3585 the breakpoints are conditional, this is even useful
3586 (@pxref{Conditions, ,Break Conditions}).
3588 @cindex multiple locations, breakpoints
3589 @cindex breakpoints, multiple locations
3590 It is possible that a breakpoint corresponds to several locations
3591 in your program. Examples of this situation are:
3595 Multiple functions in the program may have the same name.
3598 For a C@t{++} constructor, the @value{NGCC} compiler generates several
3599 instances of the function body, used in different cases.
3602 For a C@t{++} template function, a given line in the function can
3603 correspond to any number of instantiations.
3606 For an inlined function, a given source line can correspond to
3607 several places where that function is inlined.
3610 In all those cases, @value{GDBN} will insert a breakpoint at all
3611 the relevant locations.
3613 A breakpoint with multiple locations is displayed in the breakpoint
3614 table using several rows---one header row, followed by one row for
3615 each breakpoint location. The header row has @samp{<MULTIPLE>} in the
3616 address column. The rows for individual locations contain the actual
3617 addresses for locations, and show the functions to which those
3618 locations belong. The number column for a location is of the form
3619 @var{breakpoint-number}.@var{location-number}.
3624 Num Type Disp Enb Address What
3625 1 breakpoint keep y <MULTIPLE>
3627 breakpoint already hit 1 time
3628 1.1 y 0x080486a2 in void foo<int>() at t.cc:8
3629 1.2 y 0x080486ca in void foo<double>() at t.cc:8
3632 Each location can be individually enabled or disabled by passing
3633 @var{breakpoint-number}.@var{location-number} as argument to the
3634 @code{enable} and @code{disable} commands. Note that you cannot
3635 delete the individual locations from the list, you can only delete the
3636 entire list of locations that belong to their parent breakpoint (with
3637 the @kbd{delete @var{num}} command, where @var{num} is the number of
3638 the parent breakpoint, 1 in the above example). Disabling or enabling
3639 the parent breakpoint (@pxref{Disabling}) affects all of the locations
3640 that belong to that breakpoint.
3642 @cindex pending breakpoints
3643 It's quite common to have a breakpoint inside a shared library.
3644 Shared libraries can be loaded and unloaded explicitly,
3645 and possibly repeatedly, as the program is executed. To support
3646 this use case, @value{GDBN} updates breakpoint locations whenever
3647 any shared library is loaded or unloaded. Typically, you would
3648 set a breakpoint in a shared library at the beginning of your
3649 debugging session, when the library is not loaded, and when the
3650 symbols from the library are not available. When you try to set
3651 breakpoint, @value{GDBN} will ask you if you want to set
3652 a so called @dfn{pending breakpoint}---breakpoint whose address
3653 is not yet resolved.
3655 After the program is run, whenever a new shared library is loaded,
3656 @value{GDBN} reevaluates all the breakpoints. When a newly loaded
3657 shared library contains the symbol or line referred to by some
3658 pending breakpoint, that breakpoint is resolved and becomes an
3659 ordinary breakpoint. When a library is unloaded, all breakpoints
3660 that refer to its symbols or source lines become pending again.
3662 This logic works for breakpoints with multiple locations, too. For
3663 example, if you have a breakpoint in a C@t{++} template function, and
3664 a newly loaded shared library has an instantiation of that template,
3665 a new location is added to the list of locations for the breakpoint.
3667 Except for having unresolved address, pending breakpoints do not
3668 differ from regular breakpoints. You can set conditions or commands,
3669 enable and disable them and perform other breakpoint operations.
3671 @value{GDBN} provides some additional commands for controlling what
3672 happens when the @samp{break} command cannot resolve breakpoint
3673 address specification to an address:
3675 @kindex set breakpoint pending
3676 @kindex show breakpoint pending
3678 @item set breakpoint pending auto
3679 This is the default behavior. When @value{GDBN} cannot find the breakpoint
3680 location, it queries you whether a pending breakpoint should be created.
3682 @item set breakpoint pending on
3683 This indicates that an unrecognized breakpoint location should automatically
3684 result in a pending breakpoint being created.
3686 @item set breakpoint pending off
3687 This indicates that pending breakpoints are not to be created. Any
3688 unrecognized breakpoint location results in an error. This setting does
3689 not affect any pending breakpoints previously created.
3691 @item show breakpoint pending
3692 Show the current behavior setting for creating pending breakpoints.
3695 The settings above only affect the @code{break} command and its
3696 variants. Once breakpoint is set, it will be automatically updated
3697 as shared libraries are loaded and unloaded.
3699 @cindex automatic hardware breakpoints
3700 For some targets, @value{GDBN} can automatically decide if hardware or
3701 software breakpoints should be used, depending on whether the
3702 breakpoint address is read-only or read-write. This applies to
3703 breakpoints set with the @code{break} command as well as to internal
3704 breakpoints set by commands like @code{next} and @code{finish}. For
3705 breakpoints set with @code{hbreak}, @value{GDBN} will always use hardware
3708 You can control this automatic behaviour with the following commands::
3710 @kindex set breakpoint auto-hw
3711 @kindex show breakpoint auto-hw
3713 @item set breakpoint auto-hw on
3714 This is the default behavior. When @value{GDBN} sets a breakpoint, it
3715 will try to use the target memory map to decide if software or hardware
3716 breakpoint must be used.
3718 @item set breakpoint auto-hw off
3719 This indicates @value{GDBN} should not automatically select breakpoint
3720 type. If the target provides a memory map, @value{GDBN} will warn when
3721 trying to set software breakpoint at a read-only address.
3724 @value{GDBN} normally implements breakpoints by replacing the program code
3725 at the breakpoint address with a special instruction, which, when
3726 executed, given control to the debugger. By default, the program
3727 code is so modified only when the program is resumed. As soon as
3728 the program stops, @value{GDBN} restores the original instructions. This
3729 behaviour guards against leaving breakpoints inserted in the
3730 target should gdb abrubptly disconnect. However, with slow remote
3731 targets, inserting and removing breakpoint can reduce the performance.
3732 This behavior can be controlled with the following commands::
3734 @kindex set breakpoint always-inserted
3735 @kindex show breakpoint always-inserted
3737 @item set breakpoint always-inserted off
3738 All breakpoints, including newly added by the user, are inserted in
3739 the target only when the target is resumed. All breakpoints are
3740 removed from the target when it stops.
3742 @item set breakpoint always-inserted on
3743 Causes all breakpoints to be inserted in the target at all times. If
3744 the user adds a new breakpoint, or changes an existing breakpoint, the
3745 breakpoints in the target are updated immediately. A breakpoint is
3746 removed from the target only when breakpoint itself is removed.
3748 @cindex non-stop mode, and @code{breakpoint always-inserted}
3749 @item set breakpoint always-inserted auto
3750 This is the default mode. If @value{GDBN} is controlling the inferior
3751 in non-stop mode (@pxref{Non-Stop Mode}), gdb behaves as if
3752 @code{breakpoint always-inserted} mode is on. If @value{GDBN} is
3753 controlling the inferior in all-stop mode, @value{GDBN} behaves as if
3754 @code{breakpoint always-inserted} mode is off.
3757 @value{GDBN} handles conditional breakpoints by evaluating these conditions
3758 when a breakpoint breaks. If the condition is true, then the process being
3759 debugged stops, otherwise the process is resumed.
3761 If the target supports evaluating conditions on its end, @value{GDBN} may
3762 download the breakpoint, together with its conditions, to it.
3764 This feature can be controlled via the following commands:
3766 @kindex set breakpoint condition-evaluation
3767 @kindex show breakpoint condition-evaluation
3769 @item set breakpoint condition-evaluation host
3770 This option commands @value{GDBN} to evaluate the breakpoint
3771 conditions on the host's side. Unconditional breakpoints are sent to
3772 the target which in turn receives the triggers and reports them back to GDB
3773 for condition evaluation. This is the standard evaluation mode.
3775 @item set breakpoint condition-evaluation target
3776 This option commands @value{GDBN} to download breakpoint conditions
3777 to the target at the moment of their insertion. The target
3778 is responsible for evaluating the conditional expression and reporting
3779 breakpoint stop events back to @value{GDBN} whenever the condition
3780 is true. Due to limitations of target-side evaluation, some conditions
3781 cannot be evaluated there, e.g., conditions that depend on local data
3782 that is only known to the host. Examples include
3783 conditional expressions involving convenience variables, complex types
3784 that cannot be handled by the agent expression parser and expressions
3785 that are too long to be sent over to the target, specially when the
3786 target is a remote system. In these cases, the conditions will be
3787 evaluated by @value{GDBN}.
3789 @item set breakpoint condition-evaluation auto
3790 This is the default mode. If the target supports evaluating breakpoint
3791 conditions on its end, @value{GDBN} will download breakpoint conditions to
3792 the target (limitations mentioned previously apply). If the target does
3793 not support breakpoint condition evaluation, then @value{GDBN} will fallback
3794 to evaluating all these conditions on the host's side.
3798 @cindex negative breakpoint numbers
3799 @cindex internal @value{GDBN} breakpoints
3800 @value{GDBN} itself sometimes sets breakpoints in your program for
3801 special purposes, such as proper handling of @code{longjmp} (in C
3802 programs). These internal breakpoints are assigned negative numbers,
3803 starting with @code{-1}; @samp{info breakpoints} does not display them.
3804 You can see these breakpoints with the @value{GDBN} maintenance command
3805 @samp{maint info breakpoints} (@pxref{maint info breakpoints}).
3808 @node Set Watchpoints
3809 @subsection Setting Watchpoints
3811 @cindex setting watchpoints
3812 You can use a watchpoint to stop execution whenever the value of an
3813 expression changes, without having to predict a particular place where
3814 this may happen. (This is sometimes called a @dfn{data breakpoint}.)
3815 The expression may be as simple as the value of a single variable, or
3816 as complex as many variables combined by operators. Examples include:
3820 A reference to the value of a single variable.
3823 An address cast to an appropriate data type. For example,
3824 @samp{*(int *)0x12345678} will watch a 4-byte region at the specified
3825 address (assuming an @code{int} occupies 4 bytes).
3828 An arbitrarily complex expression, such as @samp{a*b + c/d}. The
3829 expression can use any operators valid in the program's native
3830 language (@pxref{Languages}).
3833 You can set a watchpoint on an expression even if the expression can
3834 not be evaluated yet. For instance, you can set a watchpoint on
3835 @samp{*global_ptr} before @samp{global_ptr} is initialized.
3836 @value{GDBN} will stop when your program sets @samp{global_ptr} and
3837 the expression produces a valid value. If the expression becomes
3838 valid in some other way than changing a variable (e.g.@: if the memory
3839 pointed to by @samp{*global_ptr} becomes readable as the result of a
3840 @code{malloc} call), @value{GDBN} may not stop until the next time
3841 the expression changes.
3843 @cindex software watchpoints
3844 @cindex hardware watchpoints
3845 Depending on your system, watchpoints may be implemented in software or
3846 hardware. @value{GDBN} does software watchpointing by single-stepping your
3847 program and testing the variable's value each time, which is hundreds of
3848 times slower than normal execution. (But this may still be worth it, to
3849 catch errors where you have no clue what part of your program is the
3852 On some systems, such as HP-UX, PowerPC, @sc{gnu}/Linux and most other
3853 x86-based targets, @value{GDBN} includes support for hardware
3854 watchpoints, which do not slow down the running of your program.
3858 @item watch @r{[}-l@r{|}-location@r{]} @var{expr} @r{[}thread @var{threadnum}@r{]} @r{[}mask @var{maskvalue}@r{]}
3859 Set a watchpoint for an expression. @value{GDBN} will break when the
3860 expression @var{expr} is written into by the program and its value
3861 changes. The simplest (and the most popular) use of this command is
3862 to watch the value of a single variable:
3865 (@value{GDBP}) watch foo
3868 If the command includes a @code{@r{[}thread @var{threadnum}@r{]}}
3869 argument, @value{GDBN} breaks only when the thread identified by
3870 @var{threadnum} changes the value of @var{expr}. If any other threads
3871 change the value of @var{expr}, @value{GDBN} will not break. Note
3872 that watchpoints restricted to a single thread in this way only work
3873 with Hardware Watchpoints.
3875 Ordinarily a watchpoint respects the scope of variables in @var{expr}
3876 (see below). The @code{-location} argument tells @value{GDBN} to
3877 instead watch the memory referred to by @var{expr}. In this case,
3878 @value{GDBN} will evaluate @var{expr}, take the address of the result,
3879 and watch the memory at that address. The type of the result is used
3880 to determine the size of the watched memory. If the expression's
3881 result does not have an address, then @value{GDBN} will print an
3884 The @code{@r{[}mask @var{maskvalue}@r{]}} argument allows creation
3885 of masked watchpoints, if the current architecture supports this
3886 feature (e.g., PowerPC Embedded architecture, see @ref{PowerPC
3887 Embedded}.) A @dfn{masked watchpoint} specifies a mask in addition
3888 to an address to watch. The mask specifies that some bits of an address
3889 (the bits which are reset in the mask) should be ignored when matching
3890 the address accessed by the inferior against the watchpoint address.
3891 Thus, a masked watchpoint watches many addresses simultaneously---those
3892 addresses whose unmasked bits are identical to the unmasked bits in the
3893 watchpoint address. The @code{mask} argument implies @code{-location}.
3897 (@value{GDBP}) watch foo mask 0xffff00ff
3898 (@value{GDBP}) watch *0xdeadbeef mask 0xffffff00
3902 @item rwatch @r{[}-l@r{|}-location@r{]} @var{expr} @r{[}thread @var{threadnum}@r{]} @r{[}mask @var{maskvalue}@r{]}
3903 Set a watchpoint that will break when the value of @var{expr} is read
3907 @item awatch @r{[}-l@r{|}-location@r{]} @var{expr} @r{[}thread @var{threadnum}@r{]} @r{[}mask @var{maskvalue}@r{]}
3908 Set a watchpoint that will break when @var{expr} is either read from
3909 or written into by the program.
3911 @kindex info watchpoints @r{[}@var{n}@dots{}@r{]}
3912 @item info watchpoints @r{[}@var{n}@dots{}@r{]}
3913 This command prints a list of watchpoints, using the same format as
3914 @code{info break} (@pxref{Set Breaks}).
3917 If you watch for a change in a numerically entered address you need to
3918 dereference it, as the address itself is just a constant number which will
3919 never change. @value{GDBN} refuses to create a watchpoint that watches
3920 a never-changing value:
3923 (@value{GDBP}) watch 0x600850
3924 Cannot watch constant value 0x600850.
3925 (@value{GDBP}) watch *(int *) 0x600850
3926 Watchpoint 1: *(int *) 6293584
3929 @value{GDBN} sets a @dfn{hardware watchpoint} if possible. Hardware
3930 watchpoints execute very quickly, and the debugger reports a change in
3931 value at the exact instruction where the change occurs. If @value{GDBN}
3932 cannot set a hardware watchpoint, it sets a software watchpoint, which
3933 executes more slowly and reports the change in value at the next
3934 @emph{statement}, not the instruction, after the change occurs.
3936 @cindex use only software watchpoints
3937 You can force @value{GDBN} to use only software watchpoints with the
3938 @kbd{set can-use-hw-watchpoints 0} command. With this variable set to
3939 zero, @value{GDBN} will never try to use hardware watchpoints, even if
3940 the underlying system supports them. (Note that hardware-assisted
3941 watchpoints that were set @emph{before} setting
3942 @code{can-use-hw-watchpoints} to zero will still use the hardware
3943 mechanism of watching expression values.)
3946 @item set can-use-hw-watchpoints
3947 @kindex set can-use-hw-watchpoints
3948 Set whether or not to use hardware watchpoints.
3950 @item show can-use-hw-watchpoints
3951 @kindex show can-use-hw-watchpoints
3952 Show the current mode of using hardware watchpoints.
3955 For remote targets, you can restrict the number of hardware
3956 watchpoints @value{GDBN} will use, see @ref{set remote
3957 hardware-breakpoint-limit}.
3959 When you issue the @code{watch} command, @value{GDBN} reports
3962 Hardware watchpoint @var{num}: @var{expr}
3966 if it was able to set a hardware watchpoint.
3968 Currently, the @code{awatch} and @code{rwatch} commands can only set
3969 hardware watchpoints, because accesses to data that don't change the
3970 value of the watched expression cannot be detected without examining
3971 every instruction as it is being executed, and @value{GDBN} does not do
3972 that currently. If @value{GDBN} finds that it is unable to set a
3973 hardware breakpoint with the @code{awatch} or @code{rwatch} command, it
3974 will print a message like this:
3977 Expression cannot be implemented with read/access watchpoint.
3980 Sometimes, @value{GDBN} cannot set a hardware watchpoint because the
3981 data type of the watched expression is wider than what a hardware
3982 watchpoint on the target machine can handle. For example, some systems
3983 can only watch regions that are up to 4 bytes wide; on such systems you
3984 cannot set hardware watchpoints for an expression that yields a
3985 double-precision floating-point number (which is typically 8 bytes
3986 wide). As a work-around, it might be possible to break the large region
3987 into a series of smaller ones and watch them with separate watchpoints.
3989 If you set too many hardware watchpoints, @value{GDBN} might be unable
3990 to insert all of them when you resume the execution of your program.
3991 Since the precise number of active watchpoints is unknown until such
3992 time as the program is about to be resumed, @value{GDBN} might not be
3993 able to warn you about this when you set the watchpoints, and the
3994 warning will be printed only when the program is resumed:
3997 Hardware watchpoint @var{num}: Could not insert watchpoint
4001 If this happens, delete or disable some of the watchpoints.
4003 Watching complex expressions that reference many variables can also
4004 exhaust the resources available for hardware-assisted watchpoints.
4005 That's because @value{GDBN} needs to watch every variable in the
4006 expression with separately allocated resources.
4008 If you call a function interactively using @code{print} or @code{call},
4009 any watchpoints you have set will be inactive until @value{GDBN} reaches another
4010 kind of breakpoint or the call completes.
4012 @value{GDBN} automatically deletes watchpoints that watch local
4013 (automatic) variables, or expressions that involve such variables, when
4014 they go out of scope, that is, when the execution leaves the block in
4015 which these variables were defined. In particular, when the program
4016 being debugged terminates, @emph{all} local variables go out of scope,
4017 and so only watchpoints that watch global variables remain set. If you
4018 rerun the program, you will need to set all such watchpoints again. One
4019 way of doing that would be to set a code breakpoint at the entry to the
4020 @code{main} function and when it breaks, set all the watchpoints.
4022 @cindex watchpoints and threads
4023 @cindex threads and watchpoints
4024 In multi-threaded programs, watchpoints will detect changes to the
4025 watched expression from every thread.
4028 @emph{Warning:} In multi-threaded programs, software watchpoints
4029 have only limited usefulness. If @value{GDBN} creates a software
4030 watchpoint, it can only watch the value of an expression @emph{in a
4031 single thread}. If you are confident that the expression can only
4032 change due to the current thread's activity (and if you are also
4033 confident that no other thread can become current), then you can use
4034 software watchpoints as usual. However, @value{GDBN} may not notice
4035 when a non-current thread's activity changes the expression. (Hardware
4036 watchpoints, in contrast, watch an expression in all threads.)
4039 @xref{set remote hardware-watchpoint-limit}.
4041 @node Set Catchpoints
4042 @subsection Setting Catchpoints
4043 @cindex catchpoints, setting
4044 @cindex exception handlers
4045 @cindex event handling
4047 You can use @dfn{catchpoints} to cause the debugger to stop for certain
4048 kinds of program events, such as C@t{++} exceptions or the loading of a
4049 shared library. Use the @code{catch} command to set a catchpoint.
4053 @item catch @var{event}
4054 Stop when @var{event} occurs. @var{event} can be any of the following:
4057 @cindex stop on C@t{++} exceptions
4058 The throwing of a C@t{++} exception.
4061 The catching of a C@t{++} exception.
4064 @cindex Ada exception catching
4065 @cindex catch Ada exceptions
4066 An Ada exception being raised. If an exception name is specified
4067 at the end of the command (eg @code{catch exception Program_Error}),
4068 the debugger will stop only when this specific exception is raised.
4069 Otherwise, the debugger stops execution when any Ada exception is raised.
4071 When inserting an exception catchpoint on a user-defined exception whose
4072 name is identical to one of the exceptions defined by the language, the
4073 fully qualified name must be used as the exception name. Otherwise,
4074 @value{GDBN} will assume that it should stop on the pre-defined exception
4075 rather than the user-defined one. For instance, assuming an exception
4076 called @code{Constraint_Error} is defined in package @code{Pck}, then
4077 the command to use to catch such exceptions is @kbd{catch exception
4078 Pck.Constraint_Error}.
4080 @item exception unhandled
4081 An exception that was raised but is not handled by the program.
4084 A failed Ada assertion.
4087 @cindex break on fork/exec
4088 A call to @code{exec}. This is currently only available for HP-UX
4092 @itemx syscall @r{[}@var{name} @r{|} @var{number}@r{]} @dots{}
4093 @cindex break on a system call.
4094 A call to or return from a system call, a.k.a.@: @dfn{syscall}. A
4095 syscall is a mechanism for application programs to request a service
4096 from the operating system (OS) or one of the OS system services.
4097 @value{GDBN} can catch some or all of the syscalls issued by the
4098 debuggee, and show the related information for each syscall. If no
4099 argument is specified, calls to and returns from all system calls
4102 @var{name} can be any system call name that is valid for the
4103 underlying OS. Just what syscalls are valid depends on the OS. On
4104 GNU and Unix systems, you can find the full list of valid syscall
4105 names on @file{/usr/include/asm/unistd.h}.
4107 @c For MS-Windows, the syscall names and the corresponding numbers
4108 @c can be found, e.g., on this URL:
4109 @c http://www.metasploit.com/users/opcode/syscalls.html
4110 @c but we don't support Windows syscalls yet.
4112 Normally, @value{GDBN} knows in advance which syscalls are valid for
4113 each OS, so you can use the @value{GDBN} command-line completion
4114 facilities (@pxref{Completion,, command completion}) to list the
4117 You may also specify the system call numerically. A syscall's
4118 number is the value passed to the OS's syscall dispatcher to
4119 identify the requested service. When you specify the syscall by its
4120 name, @value{GDBN} uses its database of syscalls to convert the name
4121 into the corresponding numeric code, but using the number directly
4122 may be useful if @value{GDBN}'s database does not have the complete
4123 list of syscalls on your system (e.g., because @value{GDBN} lags
4124 behind the OS upgrades).
4126 The example below illustrates how this command works if you don't provide
4130 (@value{GDBP}) catch syscall
4131 Catchpoint 1 (syscall)
4133 Starting program: /tmp/catch-syscall
4135 Catchpoint 1 (call to syscall 'close'), \
4136 0xffffe424 in __kernel_vsyscall ()
4140 Catchpoint 1 (returned from syscall 'close'), \
4141 0xffffe424 in __kernel_vsyscall ()
4145 Here is an example of catching a system call by name:
4148 (@value{GDBP}) catch syscall chroot
4149 Catchpoint 1 (syscall 'chroot' [61])
4151 Starting program: /tmp/catch-syscall
4153 Catchpoint 1 (call to syscall 'chroot'), \
4154 0xffffe424 in __kernel_vsyscall ()
4158 Catchpoint 1 (returned from syscall 'chroot'), \
4159 0xffffe424 in __kernel_vsyscall ()
4163 An example of specifying a system call numerically. In the case
4164 below, the syscall number has a corresponding entry in the XML
4165 file, so @value{GDBN} finds its name and prints it:
4168 (@value{GDBP}) catch syscall 252
4169 Catchpoint 1 (syscall(s) 'exit_group')
4171 Starting program: /tmp/catch-syscall
4173 Catchpoint 1 (call to syscall 'exit_group'), \
4174 0xffffe424 in __kernel_vsyscall ()
4178 Program exited normally.
4182 However, there can be situations when there is no corresponding name
4183 in XML file for that syscall number. In this case, @value{GDBN} prints
4184 a warning message saying that it was not able to find the syscall name,
4185 but the catchpoint will be set anyway. See the example below:
4188 (@value{GDBP}) catch syscall 764
4189 warning: The number '764' does not represent a known syscall.
4190 Catchpoint 2 (syscall 764)
4194 If you configure @value{GDBN} using the @samp{--without-expat} option,
4195 it will not be able to display syscall names. Also, if your
4196 architecture does not have an XML file describing its system calls,
4197 you will not be able to see the syscall names. It is important to
4198 notice that these two features are used for accessing the syscall
4199 name database. In either case, you will see a warning like this:
4202 (@value{GDBP}) catch syscall
4203 warning: Could not open "syscalls/i386-linux.xml"
4204 warning: Could not load the syscall XML file 'syscalls/i386-linux.xml'.
4205 GDB will not be able to display syscall names.
4206 Catchpoint 1 (syscall)
4210 Of course, the file name will change depending on your architecture and system.
4212 Still using the example above, you can also try to catch a syscall by its
4213 number. In this case, you would see something like:
4216 (@value{GDBP}) catch syscall 252
4217 Catchpoint 1 (syscall(s) 252)
4220 Again, in this case @value{GDBN} would not be able to display syscall's names.
4223 A call to @code{fork}. This is currently only available for HP-UX
4227 A call to @code{vfork}. This is currently only available for HP-UX
4230 @item load @r{[}regexp@r{]}
4231 @itemx unload @r{[}regexp@r{]}
4232 The loading or unloading of a shared library. If @var{regexp} is
4233 given, then the catchpoint will stop only if the regular expression
4234 matches one of the affected libraries.
4236 @item signal @r{[}@var{signal}@dots{} @r{|} @samp{all}@r{]}
4237 The delivery of a signal.
4239 With no arguments, this catchpoint will catch any signal that is not
4240 used internally by @value{GDBN}, specifically, all signals except
4241 @samp{SIGTRAP} and @samp{SIGINT}.
4243 With the argument @samp{all}, all signals, including those used by
4244 @value{GDBN}, will be caught. This argument cannot be used with other
4247 Otherwise, the arguments are a list of signal names as given to
4248 @code{handle} (@pxref{Signals}). Only signals specified in this list
4251 One reason that @code{catch signal} can be more useful than
4252 @code{handle} is that you can attach commands and conditions to the
4255 When a signal is caught by a catchpoint, the signal's @code{stop} and
4256 @code{print} settings, as specified by @code{handle}, are ignored.
4257 However, whether the signal is still delivered to the inferior depends
4258 on the @code{pass} setting; this can be changed in the catchpoint's
4263 @item tcatch @var{event}
4264 Set a catchpoint that is enabled only for one stop. The catchpoint is
4265 automatically deleted after the first time the event is caught.
4269 Use the @code{info break} command to list the current catchpoints.
4271 There are currently some limitations to C@t{++} exception handling
4272 (@code{catch throw} and @code{catch catch}) in @value{GDBN}:
4276 If you call a function interactively, @value{GDBN} normally returns
4277 control to you when the function has finished executing. If the call
4278 raises an exception, however, the call may bypass the mechanism that
4279 returns control to you and cause your program either to abort or to
4280 simply continue running until it hits a breakpoint, catches a signal
4281 that @value{GDBN} is listening for, or exits. This is the case even if
4282 you set a catchpoint for the exception; catchpoints on exceptions are
4283 disabled within interactive calls.
4286 You cannot raise an exception interactively.
4289 You cannot install an exception handler interactively.
4292 @cindex raise exceptions
4293 Sometimes @code{catch} is not the best way to debug exception handling:
4294 if you need to know exactly where an exception is raised, it is better to
4295 stop @emph{before} the exception handler is called, since that way you
4296 can see the stack before any unwinding takes place. If you set a
4297 breakpoint in an exception handler instead, it may not be easy to find
4298 out where the exception was raised.
4300 To stop just before an exception handler is called, you need some
4301 knowledge of the implementation. In the case of @sc{gnu} C@t{++}, exceptions are
4302 raised by calling a library function named @code{__raise_exception}
4303 which has the following ANSI C interface:
4306 /* @var{addr} is where the exception identifier is stored.
4307 @var{id} is the exception identifier. */
4308 void __raise_exception (void **addr, void *id);
4312 To make the debugger catch all exceptions before any stack
4313 unwinding takes place, set a breakpoint on @code{__raise_exception}
4314 (@pxref{Breakpoints, ,Breakpoints; Watchpoints; and Exceptions}).
4316 With a conditional breakpoint (@pxref{Conditions, ,Break Conditions})
4317 that depends on the value of @var{id}, you can stop your program when
4318 a specific exception is raised. You can use multiple conditional
4319 breakpoints to stop your program when any of a number of exceptions are
4324 @subsection Deleting Breakpoints
4326 @cindex clearing breakpoints, watchpoints, catchpoints
4327 @cindex deleting breakpoints, watchpoints, catchpoints
4328 It is often necessary to eliminate a breakpoint, watchpoint, or
4329 catchpoint once it has done its job and you no longer want your program
4330 to stop there. This is called @dfn{deleting} the breakpoint. A
4331 breakpoint that has been deleted no longer exists; it is forgotten.
4333 With the @code{clear} command you can delete breakpoints according to
4334 where they are in your program. With the @code{delete} command you can
4335 delete individual breakpoints, watchpoints, or catchpoints by specifying
4336 their breakpoint numbers.
4338 It is not necessary to delete a breakpoint to proceed past it. @value{GDBN}
4339 automatically ignores breakpoints on the first instruction to be executed
4340 when you continue execution without changing the execution address.
4345 Delete any breakpoints at the next instruction to be executed in the
4346 selected stack frame (@pxref{Selection, ,Selecting a Frame}). When
4347 the innermost frame is selected, this is a good way to delete a
4348 breakpoint where your program just stopped.
4350 @item clear @var{location}
4351 Delete any breakpoints set at the specified @var{location}.
4352 @xref{Specify Location}, for the various forms of @var{location}; the
4353 most useful ones are listed below:
4356 @item clear @var{function}
4357 @itemx clear @var{filename}:@var{function}
4358 Delete any breakpoints set at entry to the named @var{function}.
4360 @item clear @var{linenum}
4361 @itemx clear @var{filename}:@var{linenum}
4362 Delete any breakpoints set at or within the code of the specified
4363 @var{linenum} of the specified @var{filename}.
4366 @cindex delete breakpoints
4368 @kindex d @r{(@code{delete})}
4369 @item delete @r{[}breakpoints@r{]} @r{[}@var{range}@dots{}@r{]}
4370 Delete the breakpoints, watchpoints, or catchpoints of the breakpoint
4371 ranges specified as arguments. If no argument is specified, delete all
4372 breakpoints (@value{GDBN} asks confirmation, unless you have @code{set
4373 confirm off}). You can abbreviate this command as @code{d}.
4377 @subsection Disabling Breakpoints
4379 @cindex enable/disable a breakpoint
4380 Rather than deleting a breakpoint, watchpoint, or catchpoint, you might
4381 prefer to @dfn{disable} it. This makes the breakpoint inoperative as if
4382 it had been deleted, but remembers the information on the breakpoint so
4383 that you can @dfn{enable} it again later.
4385 You disable and enable breakpoints, watchpoints, and catchpoints with
4386 the @code{enable} and @code{disable} commands, optionally specifying
4387 one or more breakpoint numbers as arguments. Use @code{info break} to
4388 print a list of all breakpoints, watchpoints, and catchpoints if you
4389 do not know which numbers to use.
4391 Disabling and enabling a breakpoint that has multiple locations
4392 affects all of its locations.
4394 A breakpoint, watchpoint, or catchpoint can have any of several
4395 different states of enablement:
4399 Enabled. The breakpoint stops your program. A breakpoint set
4400 with the @code{break} command starts out in this state.
4402 Disabled. The breakpoint has no effect on your program.
4404 Enabled once. The breakpoint stops your program, but then becomes
4407 Enabled for a count. The breakpoint stops your program for the next
4408 N times, then becomes disabled.
4410 Enabled for deletion. The breakpoint stops your program, but
4411 immediately after it does so it is deleted permanently. A breakpoint
4412 set with the @code{tbreak} command starts out in this state.
4415 You can use the following commands to enable or disable breakpoints,
4416 watchpoints, and catchpoints:
4420 @kindex dis @r{(@code{disable})}
4421 @item disable @r{[}breakpoints@r{]} @r{[}@var{range}@dots{}@r{]}
4422 Disable the specified breakpoints---or all breakpoints, if none are
4423 listed. A disabled breakpoint has no effect but is not forgotten. All
4424 options such as ignore-counts, conditions and commands are remembered in
4425 case the breakpoint is enabled again later. You may abbreviate
4426 @code{disable} as @code{dis}.
4429 @item enable @r{[}breakpoints@r{]} @r{[}@var{range}@dots{}@r{]}
4430 Enable the specified breakpoints (or all defined breakpoints). They
4431 become effective once again in stopping your program.
4433 @item enable @r{[}breakpoints@r{]} once @var{range}@dots{}
4434 Enable the specified breakpoints temporarily. @value{GDBN} disables any
4435 of these breakpoints immediately after stopping your program.
4437 @item enable @r{[}breakpoints@r{]} count @var{count} @var{range}@dots{}
4438 Enable the specified breakpoints temporarily. @value{GDBN} records
4439 @var{count} with each of the specified breakpoints, and decrements a
4440 breakpoint's count when it is hit. When any count reaches 0,
4441 @value{GDBN} disables that breakpoint. If a breakpoint has an ignore
4442 count (@pxref{Conditions, ,Break Conditions}), that will be
4443 decremented to 0 before @var{count} is affected.
4445 @item enable @r{[}breakpoints@r{]} delete @var{range}@dots{}
4446 Enable the specified breakpoints to work once, then die. @value{GDBN}
4447 deletes any of these breakpoints as soon as your program stops there.
4448 Breakpoints set by the @code{tbreak} command start out in this state.
4451 @c FIXME: I think the following ``Except for [...] @code{tbreak}'' is
4452 @c confusing: tbreak is also initially enabled.
4453 Except for a breakpoint set with @code{tbreak} (@pxref{Set Breaks,
4454 ,Setting Breakpoints}), breakpoints that you set are initially enabled;
4455 subsequently, they become disabled or enabled only when you use one of
4456 the commands above. (The command @code{until} can set and delete a
4457 breakpoint of its own, but it does not change the state of your other
4458 breakpoints; see @ref{Continuing and Stepping, ,Continuing and
4462 @subsection Break Conditions
4463 @cindex conditional breakpoints
4464 @cindex breakpoint conditions
4466 @c FIXME what is scope of break condition expr? Context where wanted?
4467 @c in particular for a watchpoint?
4468 The simplest sort of breakpoint breaks every time your program reaches a
4469 specified place. You can also specify a @dfn{condition} for a
4470 breakpoint. A condition is just a Boolean expression in your
4471 programming language (@pxref{Expressions, ,Expressions}). A breakpoint with
4472 a condition evaluates the expression each time your program reaches it,
4473 and your program stops only if the condition is @emph{true}.
4475 This is the converse of using assertions for program validation; in that
4476 situation, you want to stop when the assertion is violated---that is,
4477 when the condition is false. In C, if you want to test an assertion expressed
4478 by the condition @var{assert}, you should set the condition
4479 @samp{! @var{assert}} on the appropriate breakpoint.
4481 Conditions are also accepted for watchpoints; you may not need them,
4482 since a watchpoint is inspecting the value of an expression anyhow---but
4483 it might be simpler, say, to just set a watchpoint on a variable name,
4484 and specify a condition that tests whether the new value is an interesting
4487 Break conditions can have side effects, and may even call functions in
4488 your program. This can be useful, for example, to activate functions
4489 that log program progress, or to use your own print functions to
4490 format special data structures. The effects are completely predictable
4491 unless there is another enabled breakpoint at the same address. (In
4492 that case, @value{GDBN} might see the other breakpoint first and stop your
4493 program without checking the condition of this one.) Note that
4494 breakpoint commands are usually more convenient and flexible than break
4496 purpose of performing side effects when a breakpoint is reached
4497 (@pxref{Break Commands, ,Breakpoint Command Lists}).
4499 Breakpoint conditions can also be evaluated on the target's side if
4500 the target supports it. Instead of evaluating the conditions locally,
4501 @value{GDBN} encodes the expression into an agent expression
4502 (@pxref{Agent Expressions}) suitable for execution on the target,
4503 independently of @value{GDBN}. Global variables become raw memory
4504 locations, locals become stack accesses, and so forth.
4506 In this case, @value{GDBN} will only be notified of a breakpoint trigger
4507 when its condition evaluates to true. This mechanism may provide faster
4508 response times depending on the performance characteristics of the target
4509 since it does not need to keep @value{GDBN} informed about
4510 every breakpoint trigger, even those with false conditions.
4512 Break conditions can be specified when a breakpoint is set, by using
4513 @samp{if} in the arguments to the @code{break} command. @xref{Set
4514 Breaks, ,Setting Breakpoints}. They can also be changed at any time
4515 with the @code{condition} command.
4517 You can also use the @code{if} keyword with the @code{watch} command.
4518 The @code{catch} command does not recognize the @code{if} keyword;
4519 @code{condition} is the only way to impose a further condition on a
4524 @item condition @var{bnum} @var{expression}
4525 Specify @var{expression} as the break condition for breakpoint,
4526 watchpoint, or catchpoint number @var{bnum}. After you set a condition,
4527 breakpoint @var{bnum} stops your program only if the value of
4528 @var{expression} is true (nonzero, in C). When you use
4529 @code{condition}, @value{GDBN} checks @var{expression} immediately for
4530 syntactic correctness, and to determine whether symbols in it have
4531 referents in the context of your breakpoint. If @var{expression} uses
4532 symbols not referenced in the context of the breakpoint, @value{GDBN}
4533 prints an error message:
4536 No symbol "foo" in current context.
4541 not actually evaluate @var{expression} at the time the @code{condition}
4542 command (or a command that sets a breakpoint with a condition, like
4543 @code{break if @dots{}}) is given, however. @xref{Expressions, ,Expressions}.
4545 @item condition @var{bnum}
4546 Remove the condition from breakpoint number @var{bnum}. It becomes
4547 an ordinary unconditional breakpoint.
4550 @cindex ignore count (of breakpoint)
4551 A special case of a breakpoint condition is to stop only when the
4552 breakpoint has been reached a certain number of times. This is so
4553 useful that there is a special way to do it, using the @dfn{ignore
4554 count} of the breakpoint. Every breakpoint has an ignore count, which
4555 is an integer. Most of the time, the ignore count is zero, and
4556 therefore has no effect. But if your program reaches a breakpoint whose
4557 ignore count is positive, then instead of stopping, it just decrements
4558 the ignore count by one and continues. As a result, if the ignore count
4559 value is @var{n}, the breakpoint does not stop the next @var{n} times
4560 your program reaches it.
4564 @item ignore @var{bnum} @var{count}
4565 Set the ignore count of breakpoint number @var{bnum} to @var{count}.
4566 The next @var{count} times the breakpoint is reached, your program's
4567 execution does not stop; other than to decrement the ignore count, @value{GDBN}
4570 To make the breakpoint stop the next time it is reached, specify
4573 When you use @code{continue} to resume execution of your program from a
4574 breakpoint, you can specify an ignore count directly as an argument to
4575 @code{continue}, rather than using @code{ignore}. @xref{Continuing and
4576 Stepping,,Continuing and Stepping}.
4578 If a breakpoint has a positive ignore count and a condition, the
4579 condition is not checked. Once the ignore count reaches zero,
4580 @value{GDBN} resumes checking the condition.
4582 You could achieve the effect of the ignore count with a condition such
4583 as @w{@samp{$foo-- <= 0}} using a debugger convenience variable that
4584 is decremented each time. @xref{Convenience Vars, ,Convenience
4588 Ignore counts apply to breakpoints, watchpoints, and catchpoints.
4591 @node Break Commands
4592 @subsection Breakpoint Command Lists
4594 @cindex breakpoint commands
4595 You can give any breakpoint (or watchpoint or catchpoint) a series of
4596 commands to execute when your program stops due to that breakpoint. For
4597 example, you might want to print the values of certain expressions, or
4598 enable other breakpoints.
4602 @kindex end@r{ (breakpoint commands)}
4603 @item commands @r{[}@var{range}@dots{}@r{]}
4604 @itemx @dots{} @var{command-list} @dots{}
4606 Specify a list of commands for the given breakpoints. The commands
4607 themselves appear on the following lines. Type a line containing just
4608 @code{end} to terminate the commands.
4610 To remove all commands from a breakpoint, type @code{commands} and
4611 follow it immediately with @code{end}; that is, give no commands.
4613 With no argument, @code{commands} refers to the last breakpoint,
4614 watchpoint, or catchpoint set (not to the breakpoint most recently
4615 encountered). If the most recent breakpoints were set with a single
4616 command, then the @code{commands} will apply to all the breakpoints
4617 set by that command. This applies to breakpoints set by
4618 @code{rbreak}, and also applies when a single @code{break} command
4619 creates multiple breakpoints (@pxref{Ambiguous Expressions,,Ambiguous
4623 Pressing @key{RET} as a means of repeating the last @value{GDBN} command is
4624 disabled within a @var{command-list}.
4626 You can use breakpoint commands to start your program up again. Simply
4627 use the @code{continue} command, or @code{step}, or any other command
4628 that resumes execution.
4630 Any other commands in the command list, after a command that resumes
4631 execution, are ignored. This is because any time you resume execution
4632 (even with a simple @code{next} or @code{step}), you may encounter
4633 another breakpoint---which could have its own command list, leading to
4634 ambiguities about which list to execute.
4637 If the first command you specify in a command list is @code{silent}, the
4638 usual message about stopping at a breakpoint is not printed. This may
4639 be desirable for breakpoints that are to print a specific message and
4640 then continue. If none of the remaining commands print anything, you
4641 see no sign that the breakpoint was reached. @code{silent} is
4642 meaningful only at the beginning of a breakpoint command list.
4644 The commands @code{echo}, @code{output}, and @code{printf} allow you to
4645 print precisely controlled output, and are often useful in silent
4646 breakpoints. @xref{Output, ,Commands for Controlled Output}.
4648 For example, here is how you could use breakpoint commands to print the
4649 value of @code{x} at entry to @code{foo} whenever @code{x} is positive.
4655 printf "x is %d\n",x
4660 One application for breakpoint commands is to compensate for one bug so
4661 you can test for another. Put a breakpoint just after the erroneous line
4662 of code, give it a condition to detect the case in which something
4663 erroneous has been done, and give it commands to assign correct values
4664 to any variables that need them. End with the @code{continue} command
4665 so that your program does not stop, and start with the @code{silent}
4666 command so that no output is produced. Here is an example:
4677 @node Dynamic Printf
4678 @subsection Dynamic Printf
4680 @cindex dynamic printf
4682 The dynamic printf command @code{dprintf} combines a breakpoint with
4683 formatted printing of your program's data to give you the effect of
4684 inserting @code{printf} calls into your program on-the-fly, without
4685 having to recompile it.
4687 In its most basic form, the output goes to the GDB console. However,
4688 you can set the variable @code{dprintf-style} for alternate handling.
4689 For instance, you can ask to format the output by calling your
4690 program's @code{printf} function. This has the advantage that the
4691 characters go to the program's output device, so they can recorded in
4692 redirects to files and so forth.
4694 If you are doing remote debugging with a stub or agent, you can also
4695 ask to have the printf handled by the remote agent. In addition to
4696 ensuring that the output goes to the remote program's device along
4697 with any other output the program might produce, you can also ask that
4698 the dprintf remain active even after disconnecting from the remote
4699 target. Using the stub/agent is also more efficient, as it can do
4700 everything without needing to communicate with @value{GDBN}.
4704 @item dprintf @var{location},@var{template},@var{expression}[,@var{expression}@dots{}]
4705 Whenever execution reaches @var{location}, print the values of one or
4706 more @var{expressions} under the control of the string @var{template}.
4707 To print several values, separate them with commas.
4709 @item set dprintf-style @var{style}
4710 Set the dprintf output to be handled in one of several different
4711 styles enumerated below. A change of style affects all existing
4712 dynamic printfs immediately. (If you need individual control over the
4713 print commands, simply define normal breakpoints with
4714 explicitly-supplied command lists.)
4717 @kindex dprintf-style gdb
4718 Handle the output using the @value{GDBN} @code{printf} command.
4721 @kindex dprintf-style call
4722 Handle the output by calling a function in your program (normally
4726 @kindex dprintf-style agent
4727 Have the remote debugging agent (such as @code{gdbserver}) handle
4728 the output itself. This style is only available for agents that
4729 support running commands on the target.
4731 @item set dprintf-function @var{function}
4732 Set the function to call if the dprintf style is @code{call}. By
4733 default its value is @code{printf}. You may set it to any expression.
4734 that @value{GDBN} can evaluate to a function, as per the @code{call}
4737 @item set dprintf-channel @var{channel}
4738 Set a ``channel'' for dprintf. If set to a non-empty value,
4739 @value{GDBN} will evaluate it as an expression and pass the result as
4740 a first argument to the @code{dprintf-function}, in the manner of
4741 @code{fprintf} and similar functions. Otherwise, the dprintf format
4742 string will be the first argument, in the manner of @code{printf}.
4744 As an example, if you wanted @code{dprintf} output to go to a logfile
4745 that is a standard I/O stream assigned to the variable @code{mylog},
4746 you could do the following:
4749 (gdb) set dprintf-style call
4750 (gdb) set dprintf-function fprintf
4751 (gdb) set dprintf-channel mylog
4752 (gdb) dprintf 25,"at line 25, glob=%d\n",glob
4753 Dprintf 1 at 0x123456: file main.c, line 25.
4755 1 dprintf keep y 0x00123456 in main at main.c:25
4756 call (void) fprintf (mylog,"at line 25, glob=%d\n",glob)
4761 Note that the @code{info break} displays the dynamic printf commands
4762 as normal breakpoint commands; you can thus easily see the effect of
4763 the variable settings.
4765 @item set disconnected-dprintf on
4766 @itemx set disconnected-dprintf off
4767 @kindex set disconnected-dprintf
4768 Choose whether @code{dprintf} commands should continue to run if
4769 @value{GDBN} has disconnected from the target. This only applies
4770 if the @code{dprintf-style} is @code{agent}.
4772 @item show disconnected-dprintf off
4773 @kindex show disconnected-dprintf
4774 Show the current choice for disconnected @code{dprintf}.
4778 @value{GDBN} does not check the validity of function and channel,
4779 relying on you to supply values that are meaningful for the contexts
4780 in which they are being used. For instance, the function and channel
4781 may be the values of local variables, but if that is the case, then
4782 all enabled dynamic prints must be at locations within the scope of
4783 those locals. If evaluation fails, @value{GDBN} will report an error.
4785 @node Save Breakpoints
4786 @subsection How to save breakpoints to a file
4788 To save breakpoint definitions to a file use the @w{@code{save
4789 breakpoints}} command.
4792 @kindex save breakpoints
4793 @cindex save breakpoints to a file for future sessions
4794 @item save breakpoints [@var{filename}]
4795 This command saves all current breakpoint definitions together with
4796 their commands and ignore counts, into a file @file{@var{filename}}
4797 suitable for use in a later debugging session. This includes all
4798 types of breakpoints (breakpoints, watchpoints, catchpoints,
4799 tracepoints). To read the saved breakpoint definitions, use the
4800 @code{source} command (@pxref{Command Files}). Note that watchpoints
4801 with expressions involving local variables may fail to be recreated
4802 because it may not be possible to access the context where the
4803 watchpoint is valid anymore. Because the saved breakpoint definitions
4804 are simply a sequence of @value{GDBN} commands that recreate the
4805 breakpoints, you can edit the file in your favorite editing program,
4806 and remove the breakpoint definitions you're not interested in, or
4807 that can no longer be recreated.
4810 @node Static Probe Points
4811 @subsection Static Probe Points
4813 @cindex static probe point, SystemTap
4814 @value{GDBN} supports @dfn{SDT} probes in the code. @acronym{SDT} stands
4815 for Statically Defined Tracing, and the probes are designed to have a tiny
4816 runtime code and data footprint, and no dynamic relocations. They are
4817 usable from assembly, C and C@t{++} languages. See
4818 @uref{http://sourceware.org/systemtap/wiki/UserSpaceProbeImplementation}
4819 for a good reference on how the @acronym{SDT} probes are implemented.
4821 Currently, @code{SystemTap} (@uref{http://sourceware.org/systemtap/})
4822 @acronym{SDT} probes are supported on ELF-compatible systems. See
4823 @uref{http://sourceware.org/systemtap/wiki/AddingUserSpaceProbingToApps}
4824 for more information on how to add @code{SystemTap} @acronym{SDT} probes
4825 in your applications.
4827 @cindex semaphores on static probe points
4828 Some probes have an associated semaphore variable; for instance, this
4829 happens automatically if you defined your probe using a DTrace-style
4830 @file{.d} file. If your probe has a semaphore, @value{GDBN} will
4831 automatically enable it when you specify a breakpoint using the
4832 @samp{-probe-stap} notation. But, if you put a breakpoint at a probe's
4833 location by some other method (e.g., @code{break file:line}), then
4834 @value{GDBN} will not automatically set the semaphore.
4836 You can examine the available static static probes using @code{info
4837 probes}, with optional arguments:
4841 @item info probes stap @r{[}@var{provider} @r{[}@var{name} @r{[}@var{objfile}@r{]}@r{]}@r{]}
4842 If given, @var{provider} is a regular expression used to match against provider
4843 names when selecting which probes to list. If omitted, probes by all
4844 probes from all providers are listed.
4846 If given, @var{name} is a regular expression to match against probe names
4847 when selecting which probes to list. If omitted, probe names are not
4848 considered when deciding whether to display them.
4850 If given, @var{objfile} is a regular expression used to select which
4851 object files (executable or shared libraries) to examine. If not
4852 given, all object files are considered.
4854 @item info probes all
4855 List the available static probes, from all types.
4858 @vindex $_probe_arg@r{, convenience variable}
4859 A probe may specify up to twelve arguments. These are available at the
4860 point at which the probe is defined---that is, when the current PC is
4861 at the probe's location. The arguments are available using the
4862 convenience variables (@pxref{Convenience Vars})
4863 @code{$_probe_arg0}@dots{}@code{$_probe_arg11}. Each probe argument is
4864 an integer of the appropriate size; types are not preserved. The
4865 convenience variable @code{$_probe_argc} holds the number of arguments
4866 at the current probe point.
4868 These variables are always available, but attempts to access them at
4869 any location other than a probe point will cause @value{GDBN} to give
4873 @c @ifclear BARETARGET
4874 @node Error in Breakpoints
4875 @subsection ``Cannot insert breakpoints''
4877 If you request too many active hardware-assisted breakpoints and
4878 watchpoints, you will see this error message:
4880 @c FIXME: the precise wording of this message may change; the relevant
4881 @c source change is not committed yet (Sep 3, 1999).
4883 Stopped; cannot insert breakpoints.
4884 You may have requested too many hardware breakpoints and watchpoints.
4888 This message is printed when you attempt to resume the program, since
4889 only then @value{GDBN} knows exactly how many hardware breakpoints and
4890 watchpoints it needs to insert.
4892 When this message is printed, you need to disable or remove some of the
4893 hardware-assisted breakpoints and watchpoints, and then continue.
4895 @node Breakpoint-related Warnings
4896 @subsection ``Breakpoint address adjusted...''
4897 @cindex breakpoint address adjusted
4899 Some processor architectures place constraints on the addresses at
4900 which breakpoints may be placed. For architectures thus constrained,
4901 @value{GDBN} will attempt to adjust the breakpoint's address to comply
4902 with the constraints dictated by the architecture.
4904 One example of such an architecture is the Fujitsu FR-V. The FR-V is
4905 a VLIW architecture in which a number of RISC-like instructions may be
4906 bundled together for parallel execution. The FR-V architecture
4907 constrains the location of a breakpoint instruction within such a
4908 bundle to the instruction with the lowest address. @value{GDBN}
4909 honors this constraint by adjusting a breakpoint's address to the
4910 first in the bundle.
4912 It is not uncommon for optimized code to have bundles which contain
4913 instructions from different source statements, thus it may happen that
4914 a breakpoint's address will be adjusted from one source statement to
4915 another. Since this adjustment may significantly alter @value{GDBN}'s
4916 breakpoint related behavior from what the user expects, a warning is
4917 printed when the breakpoint is first set and also when the breakpoint
4920 A warning like the one below is printed when setting a breakpoint
4921 that's been subject to address adjustment:
4924 warning: Breakpoint address adjusted from 0x00010414 to 0x00010410.
4927 Such warnings are printed both for user settable and @value{GDBN}'s
4928 internal breakpoints. If you see one of these warnings, you should
4929 verify that a breakpoint set at the adjusted address will have the
4930 desired affect. If not, the breakpoint in question may be removed and
4931 other breakpoints may be set which will have the desired behavior.
4932 E.g., it may be sufficient to place the breakpoint at a later
4933 instruction. A conditional breakpoint may also be useful in some
4934 cases to prevent the breakpoint from triggering too often.
4936 @value{GDBN} will also issue a warning when stopping at one of these
4937 adjusted breakpoints:
4940 warning: Breakpoint 1 address previously adjusted from 0x00010414
4944 When this warning is encountered, it may be too late to take remedial
4945 action except in cases where the breakpoint is hit earlier or more
4946 frequently than expected.
4948 @node Continuing and Stepping
4949 @section Continuing and Stepping
4953 @cindex resuming execution
4954 @dfn{Continuing} means resuming program execution until your program
4955 completes normally. In contrast, @dfn{stepping} means executing just
4956 one more ``step'' of your program, where ``step'' may mean either one
4957 line of source code, or one machine instruction (depending on what
4958 particular command you use). Either when continuing or when stepping,
4959 your program may stop even sooner, due to a breakpoint or a signal. (If
4960 it stops due to a signal, you may want to use @code{handle}, or use
4961 @samp{signal 0} to resume execution. @xref{Signals, ,Signals}.)
4965 @kindex c @r{(@code{continue})}
4966 @kindex fg @r{(resume foreground execution)}
4967 @item continue @r{[}@var{ignore-count}@r{]}
4968 @itemx c @r{[}@var{ignore-count}@r{]}
4969 @itemx fg @r{[}@var{ignore-count}@r{]}
4970 Resume program execution, at the address where your program last stopped;
4971 any breakpoints set at that address are bypassed. The optional argument
4972 @var{ignore-count} allows you to specify a further number of times to
4973 ignore a breakpoint at this location; its effect is like that of
4974 @code{ignore} (@pxref{Conditions, ,Break Conditions}).
4976 The argument @var{ignore-count} is meaningful only when your program
4977 stopped due to a breakpoint. At other times, the argument to
4978 @code{continue} is ignored.
4980 The synonyms @code{c} and @code{fg} (for @dfn{foreground}, as the
4981 debugged program is deemed to be the foreground program) are provided
4982 purely for convenience, and have exactly the same behavior as
4986 To resume execution at a different place, you can use @code{return}
4987 (@pxref{Returning, ,Returning from a Function}) to go back to the
4988 calling function; or @code{jump} (@pxref{Jumping, ,Continuing at a
4989 Different Address}) to go to an arbitrary location in your program.
4991 A typical technique for using stepping is to set a breakpoint
4992 (@pxref{Breakpoints, ,Breakpoints; Watchpoints; and Catchpoints}) at the
4993 beginning of the function or the section of your program where a problem
4994 is believed to lie, run your program until it stops at that breakpoint,
4995 and then step through the suspect area, examining the variables that are
4996 interesting, until you see the problem happen.
5000 @kindex s @r{(@code{step})}
5002 Continue running your program until control reaches a different source
5003 line, then stop it and return control to @value{GDBN}. This command is
5004 abbreviated @code{s}.
5007 @c "without debugging information" is imprecise; actually "without line
5008 @c numbers in the debugging information". (gcc -g1 has debugging info but
5009 @c not line numbers). But it seems complex to try to make that
5010 @c distinction here.
5011 @emph{Warning:} If you use the @code{step} command while control is
5012 within a function that was compiled without debugging information,
5013 execution proceeds until control reaches a function that does have
5014 debugging information. Likewise, it will not step into a function which
5015 is compiled without debugging information. To step through functions
5016 without debugging information, use the @code{stepi} command, described
5020 The @code{step} command only stops at the first instruction of a source
5021 line. This prevents the multiple stops that could otherwise occur in
5022 @code{switch} statements, @code{for} loops, etc. @code{step} continues
5023 to stop if a function that has debugging information is called within
5024 the line. In other words, @code{step} @emph{steps inside} any functions
5025 called within the line.
5027 Also, the @code{step} command only enters a function if there is line
5028 number information for the function. Otherwise it acts like the
5029 @code{next} command. This avoids problems when using @code{cc -gl}
5030 on @acronym{MIPS} machines. Previously, @code{step} entered subroutines if there
5031 was any debugging information about the routine.
5033 @item step @var{count}
5034 Continue running as in @code{step}, but do so @var{count} times. If a
5035 breakpoint is reached, or a signal not related to stepping occurs before
5036 @var{count} steps, stepping stops right away.
5039 @kindex n @r{(@code{next})}
5040 @item next @r{[}@var{count}@r{]}
5041 Continue to the next source line in the current (innermost) stack frame.
5042 This is similar to @code{step}, but function calls that appear within
5043 the line of code are executed without stopping. Execution stops when
5044 control reaches a different line of code at the original stack level
5045 that was executing when you gave the @code{next} command. This command
5046 is abbreviated @code{n}.
5048 An argument @var{count} is a repeat count, as for @code{step}.
5051 @c FIX ME!! Do we delete this, or is there a way it fits in with
5052 @c the following paragraph? --- Vctoria
5054 @c @code{next} within a function that lacks debugging information acts like
5055 @c @code{step}, but any function calls appearing within the code of the
5056 @c function are executed without stopping.
5058 The @code{next} command only stops at the first instruction of a
5059 source line. This prevents multiple stops that could otherwise occur in
5060 @code{switch} statements, @code{for} loops, etc.
5062 @kindex set step-mode
5064 @cindex functions without line info, and stepping
5065 @cindex stepping into functions with no line info
5066 @itemx set step-mode on
5067 The @code{set step-mode on} command causes the @code{step} command to
5068 stop at the first instruction of a function which contains no debug line
5069 information rather than stepping over it.
5071 This is useful in cases where you may be interested in inspecting the
5072 machine instructions of a function which has no symbolic info and do not
5073 want @value{GDBN} to automatically skip over this function.
5075 @item set step-mode off
5076 Causes the @code{step} command to step over any functions which contains no
5077 debug information. This is the default.
5079 @item show step-mode
5080 Show whether @value{GDBN} will stop in or step over functions without
5081 source line debug information.
5084 @kindex fin @r{(@code{finish})}
5086 Continue running until just after function in the selected stack frame
5087 returns. Print the returned value (if any). This command can be
5088 abbreviated as @code{fin}.
5090 Contrast this with the @code{return} command (@pxref{Returning,
5091 ,Returning from a Function}).
5094 @kindex u @r{(@code{until})}
5095 @cindex run until specified location
5098 Continue running until a source line past the current line, in the
5099 current stack frame, is reached. This command is used to avoid single
5100 stepping through a loop more than once. It is like the @code{next}
5101 command, except that when @code{until} encounters a jump, it
5102 automatically continues execution until the program counter is greater
5103 than the address of the jump.
5105 This means that when you reach the end of a loop after single stepping
5106 though it, @code{until} makes your program continue execution until it
5107 exits the loop. In contrast, a @code{next} command at the end of a loop
5108 simply steps back to the beginning of the loop, which forces you to step
5109 through the next iteration.
5111 @code{until} always stops your program if it attempts to exit the current
5114 @code{until} may produce somewhat counterintuitive results if the order
5115 of machine code does not match the order of the source lines. For
5116 example, in the following excerpt from a debugging session, the @code{f}
5117 (@code{frame}) command shows that execution is stopped at line
5118 @code{206}; yet when we use @code{until}, we get to line @code{195}:
5122 #0 main (argc=4, argv=0xf7fffae8) at m4.c:206
5124 (@value{GDBP}) until
5125 195 for ( ; argc > 0; NEXTARG) @{
5128 This happened because, for execution efficiency, the compiler had
5129 generated code for the loop closure test at the end, rather than the
5130 start, of the loop---even though the test in a C @code{for}-loop is
5131 written before the body of the loop. The @code{until} command appeared
5132 to step back to the beginning of the loop when it advanced to this
5133 expression; however, it has not really gone to an earlier
5134 statement---not in terms of the actual machine code.
5136 @code{until} with no argument works by means of single
5137 instruction stepping, and hence is slower than @code{until} with an
5140 @item until @var{location}
5141 @itemx u @var{location}
5142 Continue running your program until either the specified location is
5143 reached, or the current stack frame returns. @var{location} is any of
5144 the forms described in @ref{Specify Location}.
5145 This form of the command uses temporary breakpoints, and
5146 hence is quicker than @code{until} without an argument. The specified
5147 location is actually reached only if it is in the current frame. This
5148 implies that @code{until} can be used to skip over recursive function
5149 invocations. For instance in the code below, if the current location is
5150 line @code{96}, issuing @code{until 99} will execute the program up to
5151 line @code{99} in the same invocation of factorial, i.e., after the inner
5152 invocations have returned.
5155 94 int factorial (int value)
5157 96 if (value > 1) @{
5158 97 value *= factorial (value - 1);
5165 @kindex advance @var{location}
5166 @item advance @var{location}
5167 Continue running the program up to the given @var{location}. An argument is
5168 required, which should be of one of the forms described in
5169 @ref{Specify Location}.
5170 Execution will also stop upon exit from the current stack
5171 frame. This command is similar to @code{until}, but @code{advance} will
5172 not skip over recursive function calls, and the target location doesn't
5173 have to be in the same frame as the current one.
5177 @kindex si @r{(@code{stepi})}
5179 @itemx stepi @var{arg}
5181 Execute one machine instruction, then stop and return to the debugger.
5183 It is often useful to do @samp{display/i $pc} when stepping by machine
5184 instructions. This makes @value{GDBN} automatically display the next
5185 instruction to be executed, each time your program stops. @xref{Auto
5186 Display,, Automatic Display}.
5188 An argument is a repeat count, as in @code{step}.
5192 @kindex ni @r{(@code{nexti})}
5194 @itemx nexti @var{arg}
5196 Execute one machine instruction, but if it is a function call,
5197 proceed until the function returns.
5199 An argument is a repeat count, as in @code{next}.
5202 @node Skipping Over Functions and Files
5203 @section Skipping Over Functions and Files
5204 @cindex skipping over functions and files
5206 The program you are debugging may contain some functions which are
5207 uninteresting to debug. The @code{skip} comand lets you tell @value{GDBN} to
5208 skip a function or all functions in a file when stepping.
5210 For example, consider the following C function:
5221 Suppose you wish to step into the functions @code{foo} and @code{bar}, but you
5222 are not interested in stepping through @code{boring}. If you run @code{step}
5223 at line 103, you'll enter @code{boring()}, but if you run @code{next}, you'll
5224 step over both @code{foo} and @code{boring}!
5226 One solution is to @code{step} into @code{boring} and use the @code{finish}
5227 command to immediately exit it. But this can become tedious if @code{boring}
5228 is called from many places.
5230 A more flexible solution is to execute @kbd{skip boring}. This instructs
5231 @value{GDBN} never to step into @code{boring}. Now when you execute
5232 @code{step} at line 103, you'll step over @code{boring} and directly into
5235 You can also instruct @value{GDBN} to skip all functions in a file, with, for
5236 example, @code{skip file boring.c}.
5239 @kindex skip function
5240 @item skip @r{[}@var{linespec}@r{]}
5241 @itemx skip function @r{[}@var{linespec}@r{]}
5242 After running this command, the function named by @var{linespec} or the
5243 function containing the line named by @var{linespec} will be skipped over when
5244 stepping. @xref{Specify Location}.
5246 If you do not specify @var{linespec}, the function you're currently debugging
5249 (If you have a function called @code{file} that you want to skip, use
5250 @kbd{skip function file}.)
5253 @item skip file @r{[}@var{filename}@r{]}
5254 After running this command, any function whose source lives in @var{filename}
5255 will be skipped over when stepping.
5257 If you do not specify @var{filename}, functions whose source lives in the file
5258 you're currently debugging will be skipped.
5261 Skips can be listed, deleted, disabled, and enabled, much like breakpoints.
5262 These are the commands for managing your list of skips:
5266 @item info skip @r{[}@var{range}@r{]}
5267 Print details about the specified skip(s). If @var{range} is not specified,
5268 print a table with details about all functions and files marked for skipping.
5269 @code{info skip} prints the following information about each skip:
5273 A number identifying this skip.
5275 The type of this skip, either @samp{function} or @samp{file}.
5276 @item Enabled or Disabled
5277 Enabled skips are marked with @samp{y}. Disabled skips are marked with @samp{n}.
5279 For function skips, this column indicates the address in memory of the function
5280 being skipped. If you've set a function skip on a function which has not yet
5281 been loaded, this field will contain @samp{<PENDING>}. Once a shared library
5282 which has the function is loaded, @code{info skip} will show the function's
5285 For file skips, this field contains the filename being skipped. For functions
5286 skips, this field contains the function name and its line number in the file
5287 where it is defined.
5291 @item skip delete @r{[}@var{range}@r{]}
5292 Delete the specified skip(s). If @var{range} is not specified, delete all
5296 @item skip enable @r{[}@var{range}@r{]}
5297 Enable the specified skip(s). If @var{range} is not specified, enable all
5300 @kindex skip disable
5301 @item skip disable @r{[}@var{range}@r{]}
5302 Disable the specified skip(s). If @var{range} is not specified, disable all
5311 A signal is an asynchronous event that can happen in a program. The
5312 operating system defines the possible kinds of signals, and gives each
5313 kind a name and a number. For example, in Unix @code{SIGINT} is the
5314 signal a program gets when you type an interrupt character (often @kbd{Ctrl-c});
5315 @code{SIGSEGV} is the signal a program gets from referencing a place in
5316 memory far away from all the areas in use; @code{SIGALRM} occurs when
5317 the alarm clock timer goes off (which happens only if your program has
5318 requested an alarm).
5320 @cindex fatal signals
5321 Some signals, including @code{SIGALRM}, are a normal part of the
5322 functioning of your program. Others, such as @code{SIGSEGV}, indicate
5323 errors; these signals are @dfn{fatal} (they kill your program immediately) if the
5324 program has not specified in advance some other way to handle the signal.
5325 @code{SIGINT} does not indicate an error in your program, but it is normally
5326 fatal so it can carry out the purpose of the interrupt: to kill the program.
5328 @value{GDBN} has the ability to detect any occurrence of a signal in your
5329 program. You can tell @value{GDBN} in advance what to do for each kind of
5332 @cindex handling signals
5333 Normally, @value{GDBN} is set up to let the non-erroneous signals like
5334 @code{SIGALRM} be silently passed to your program
5335 (so as not to interfere with their role in the program's functioning)
5336 but to stop your program immediately whenever an error signal happens.
5337 You can change these settings with the @code{handle} command.
5340 @kindex info signals
5344 Print a table of all the kinds of signals and how @value{GDBN} has been told to
5345 handle each one. You can use this to see the signal numbers of all
5346 the defined types of signals.
5348 @item info signals @var{sig}
5349 Similar, but print information only about the specified signal number.
5351 @code{info handle} is an alias for @code{info signals}.
5353 @item catch signal @r{[}@var{signal}@dots{} @r{|} @samp{all}@r{]}
5354 Set a catchpoint for the indicated signals. @xref{Set Catchpoints},
5355 for details about this command.
5358 @item handle @var{signal} @r{[}@var{keywords}@dots{}@r{]}
5359 Change the way @value{GDBN} handles signal @var{signal}. @var{signal}
5360 can be the number of a signal or its name (with or without the
5361 @samp{SIG} at the beginning); a list of signal numbers of the form
5362 @samp{@var{low}-@var{high}}; or the word @samp{all}, meaning all the
5363 known signals. Optional arguments @var{keywords}, described below,
5364 say what change to make.
5368 The keywords allowed by the @code{handle} command can be abbreviated.
5369 Their full names are:
5373 @value{GDBN} should not stop your program when this signal happens. It may
5374 still print a message telling you that the signal has come in.
5377 @value{GDBN} should stop your program when this signal happens. This implies
5378 the @code{print} keyword as well.
5381 @value{GDBN} should print a message when this signal happens.
5384 @value{GDBN} should not mention the occurrence of the signal at all. This
5385 implies the @code{nostop} keyword as well.
5389 @value{GDBN} should allow your program to see this signal; your program
5390 can handle the signal, or else it may terminate if the signal is fatal
5391 and not handled. @code{pass} and @code{noignore} are synonyms.
5395 @value{GDBN} should not allow your program to see this signal.
5396 @code{nopass} and @code{ignore} are synonyms.
5400 When a signal stops your program, the signal is not visible to the
5402 continue. Your program sees the signal then, if @code{pass} is in
5403 effect for the signal in question @emph{at that time}. In other words,
5404 after @value{GDBN} reports a signal, you can use the @code{handle}
5405 command with @code{pass} or @code{nopass} to control whether your
5406 program sees that signal when you continue.
5408 The default is set to @code{nostop}, @code{noprint}, @code{pass} for
5409 non-erroneous signals such as @code{SIGALRM}, @code{SIGWINCH} and
5410 @code{SIGCHLD}, and to @code{stop}, @code{print}, @code{pass} for the
5413 You can also use the @code{signal} command to prevent your program from
5414 seeing a signal, or cause it to see a signal it normally would not see,
5415 or to give it any signal at any time. For example, if your program stopped
5416 due to some sort of memory reference error, you might store correct
5417 values into the erroneous variables and continue, hoping to see more
5418 execution; but your program would probably terminate immediately as
5419 a result of the fatal signal once it saw the signal. To prevent this,
5420 you can continue with @samp{signal 0}. @xref{Signaling, ,Giving your
5423 @cindex extra signal information
5424 @anchor{extra signal information}
5426 On some targets, @value{GDBN} can inspect extra signal information
5427 associated with the intercepted signal, before it is actually
5428 delivered to the program being debugged. This information is exported
5429 by the convenience variable @code{$_siginfo}, and consists of data
5430 that is passed by the kernel to the signal handler at the time of the
5431 receipt of a signal. The data type of the information itself is
5432 target dependent. You can see the data type using the @code{ptype
5433 $_siginfo} command. On Unix systems, it typically corresponds to the
5434 standard @code{siginfo_t} type, as defined in the @file{signal.h}
5437 Here's an example, on a @sc{gnu}/Linux system, printing the stray
5438 referenced address that raised a segmentation fault.
5442 (@value{GDBP}) continue
5443 Program received signal SIGSEGV, Segmentation fault.
5444 0x0000000000400766 in main ()
5446 (@value{GDBP}) ptype $_siginfo
5453 struct @{...@} _kill;
5454 struct @{...@} _timer;
5456 struct @{...@} _sigchld;
5457 struct @{...@} _sigfault;
5458 struct @{...@} _sigpoll;
5461 (@value{GDBP}) ptype $_siginfo._sifields._sigfault
5465 (@value{GDBP}) p $_siginfo._sifields._sigfault.si_addr
5466 $1 = (void *) 0x7ffff7ff7000
5470 Depending on target support, @code{$_siginfo} may also be writable.
5473 @section Stopping and Starting Multi-thread Programs
5475 @cindex stopped threads
5476 @cindex threads, stopped
5478 @cindex continuing threads
5479 @cindex threads, continuing
5481 @value{GDBN} supports debugging programs with multiple threads
5482 (@pxref{Threads,, Debugging Programs with Multiple Threads}). There
5483 are two modes of controlling execution of your program within the
5484 debugger. In the default mode, referred to as @dfn{all-stop mode},
5485 when any thread in your program stops (for example, at a breakpoint
5486 or while being stepped), all other threads in the program are also stopped by
5487 @value{GDBN}. On some targets, @value{GDBN} also supports
5488 @dfn{non-stop mode}, in which other threads can continue to run freely while
5489 you examine the stopped thread in the debugger.
5492 * All-Stop Mode:: All threads stop when GDB takes control
5493 * Non-Stop Mode:: Other threads continue to execute
5494 * Background Execution:: Running your program asynchronously
5495 * Thread-Specific Breakpoints:: Controlling breakpoints
5496 * Interrupted System Calls:: GDB may interfere with system calls
5497 * Observer Mode:: GDB does not alter program behavior
5501 @subsection All-Stop Mode
5503 @cindex all-stop mode
5505 In all-stop mode, whenever your program stops under @value{GDBN} for any reason,
5506 @emph{all} threads of execution stop, not just the current thread. This
5507 allows you to examine the overall state of the program, including
5508 switching between threads, without worrying that things may change
5511 Conversely, whenever you restart the program, @emph{all} threads start
5512 executing. @emph{This is true even when single-stepping} with commands
5513 like @code{step} or @code{next}.
5515 In particular, @value{GDBN} cannot single-step all threads in lockstep.
5516 Since thread scheduling is up to your debugging target's operating
5517 system (not controlled by @value{GDBN}), other threads may
5518 execute more than one statement while the current thread completes a
5519 single step. Moreover, in general other threads stop in the middle of a
5520 statement, rather than at a clean statement boundary, when the program
5523 You might even find your program stopped in another thread after
5524 continuing or even single-stepping. This happens whenever some other
5525 thread runs into a breakpoint, a signal, or an exception before the
5526 first thread completes whatever you requested.
5528 @cindex automatic thread selection
5529 @cindex switching threads automatically
5530 @cindex threads, automatic switching
5531 Whenever @value{GDBN} stops your program, due to a breakpoint or a
5532 signal, it automatically selects the thread where that breakpoint or
5533 signal happened. @value{GDBN} alerts you to the context switch with a
5534 message such as @samp{[Switching to Thread @var{n}]} to identify the
5537 On some OSes, you can modify @value{GDBN}'s default behavior by
5538 locking the OS scheduler to allow only a single thread to run.
5541 @item set scheduler-locking @var{mode}
5542 @cindex scheduler locking mode
5543 @cindex lock scheduler
5544 Set the scheduler locking mode. If it is @code{off}, then there is no
5545 locking and any thread may run at any time. If @code{on}, then only the
5546 current thread may run when the inferior is resumed. The @code{step}
5547 mode optimizes for single-stepping; it prevents other threads
5548 from preempting the current thread while you are stepping, so that
5549 the focus of debugging does not change unexpectedly.
5550 Other threads only rarely (or never) get a chance to run
5551 when you step. They are more likely to run when you @samp{next} over a
5552 function call, and they are completely free to run when you use commands
5553 like @samp{continue}, @samp{until}, or @samp{finish}. However, unless another
5554 thread hits a breakpoint during its timeslice, @value{GDBN} does not change
5555 the current thread away from the thread that you are debugging.
5557 @item show scheduler-locking
5558 Display the current scheduler locking mode.
5561 @cindex resume threads of multiple processes simultaneously
5562 By default, when you issue one of the execution commands such as
5563 @code{continue}, @code{next} or @code{step}, @value{GDBN} allows only
5564 threads of the current inferior to run. For example, if @value{GDBN}
5565 is attached to two inferiors, each with two threads, the
5566 @code{continue} command resumes only the two threads of the current
5567 inferior. This is useful, for example, when you debug a program that
5568 forks and you want to hold the parent stopped (so that, for instance,
5569 it doesn't run to exit), while you debug the child. In other
5570 situations, you may not be interested in inspecting the current state
5571 of any of the processes @value{GDBN} is attached to, and you may want
5572 to resume them all until some breakpoint is hit. In the latter case,
5573 you can instruct @value{GDBN} to allow all threads of all the
5574 inferiors to run with the @w{@code{set schedule-multiple}} command.
5577 @kindex set schedule-multiple
5578 @item set schedule-multiple
5579 Set the mode for allowing threads of multiple processes to be resumed
5580 when an execution command is issued. When @code{on}, all threads of
5581 all processes are allowed to run. When @code{off}, only the threads
5582 of the current process are resumed. The default is @code{off}. The
5583 @code{scheduler-locking} mode takes precedence when set to @code{on},
5584 or while you are stepping and set to @code{step}.
5586 @item show schedule-multiple
5587 Display the current mode for resuming the execution of threads of
5592 @subsection Non-Stop Mode
5594 @cindex non-stop mode
5596 @c This section is really only a place-holder, and needs to be expanded
5597 @c with more details.
5599 For some multi-threaded targets, @value{GDBN} supports an optional
5600 mode of operation in which you can examine stopped program threads in
5601 the debugger while other threads continue to execute freely. This
5602 minimizes intrusion when debugging live systems, such as programs
5603 where some threads have real-time constraints or must continue to
5604 respond to external events. This is referred to as @dfn{non-stop} mode.
5606 In non-stop mode, when a thread stops to report a debugging event,
5607 @emph{only} that thread is stopped; @value{GDBN} does not stop other
5608 threads as well, in contrast to the all-stop mode behavior. Additionally,
5609 execution commands such as @code{continue} and @code{step} apply by default
5610 only to the current thread in non-stop mode, rather than all threads as
5611 in all-stop mode. This allows you to control threads explicitly in
5612 ways that are not possible in all-stop mode --- for example, stepping
5613 one thread while allowing others to run freely, stepping
5614 one thread while holding all others stopped, or stepping several threads
5615 independently and simultaneously.
5617 To enter non-stop mode, use this sequence of commands before you run
5618 or attach to your program:
5621 # Enable the async interface.
5624 # If using the CLI, pagination breaks non-stop.
5627 # Finally, turn it on!
5631 You can use these commands to manipulate the non-stop mode setting:
5634 @kindex set non-stop
5635 @item set non-stop on
5636 Enable selection of non-stop mode.
5637 @item set non-stop off
5638 Disable selection of non-stop mode.
5639 @kindex show non-stop
5641 Show the current non-stop enablement setting.
5644 Note these commands only reflect whether non-stop mode is enabled,
5645 not whether the currently-executing program is being run in non-stop mode.
5646 In particular, the @code{set non-stop} preference is only consulted when
5647 @value{GDBN} starts or connects to the target program, and it is generally
5648 not possible to switch modes once debugging has started. Furthermore,
5649 since not all targets support non-stop mode, even when you have enabled
5650 non-stop mode, @value{GDBN} may still fall back to all-stop operation by
5653 In non-stop mode, all execution commands apply only to the current thread
5654 by default. That is, @code{continue} only continues one thread.
5655 To continue all threads, issue @code{continue -a} or @code{c -a}.
5657 You can use @value{GDBN}'s background execution commands
5658 (@pxref{Background Execution}) to run some threads in the background
5659 while you continue to examine or step others from @value{GDBN}.
5660 The MI execution commands (@pxref{GDB/MI Program Execution}) are
5661 always executed asynchronously in non-stop mode.
5663 Suspending execution is done with the @code{interrupt} command when
5664 running in the background, or @kbd{Ctrl-c} during foreground execution.
5665 In all-stop mode, this stops the whole process;
5666 but in non-stop mode the interrupt applies only to the current thread.
5667 To stop the whole program, use @code{interrupt -a}.
5669 Other execution commands do not currently support the @code{-a} option.
5671 In non-stop mode, when a thread stops, @value{GDBN} doesn't automatically make
5672 that thread current, as it does in all-stop mode. This is because the
5673 thread stop notifications are asynchronous with respect to @value{GDBN}'s
5674 command interpreter, and it would be confusing if @value{GDBN} unexpectedly
5675 changed to a different thread just as you entered a command to operate on the
5676 previously current thread.
5678 @node Background Execution
5679 @subsection Background Execution
5681 @cindex foreground execution
5682 @cindex background execution
5683 @cindex asynchronous execution
5684 @cindex execution, foreground, background and asynchronous
5686 @value{GDBN}'s execution commands have two variants: the normal
5687 foreground (synchronous) behavior, and a background
5688 (asynchronous) behavior. In foreground execution, @value{GDBN} waits for
5689 the program to report that some thread has stopped before prompting for
5690 another command. In background execution, @value{GDBN} immediately gives
5691 a command prompt so that you can issue other commands while your program runs.
5693 You need to explicitly enable asynchronous mode before you can use
5694 background execution commands. You can use these commands to
5695 manipulate the asynchronous mode setting:
5698 @kindex set target-async
5699 @item set target-async on
5700 Enable asynchronous mode.
5701 @item set target-async off
5702 Disable asynchronous mode.
5703 @kindex show target-async
5704 @item show target-async
5705 Show the current target-async setting.
5708 If the target doesn't support async mode, @value{GDBN} issues an error
5709 message if you attempt to use the background execution commands.
5711 To specify background execution, add a @code{&} to the command. For example,
5712 the background form of the @code{continue} command is @code{continue&}, or
5713 just @code{c&}. The execution commands that accept background execution
5719 @xref{Starting, , Starting your Program}.
5723 @xref{Attach, , Debugging an Already-running Process}.
5727 @xref{Continuing and Stepping, step}.
5731 @xref{Continuing and Stepping, stepi}.
5735 @xref{Continuing and Stepping, next}.
5739 @xref{Continuing and Stepping, nexti}.
5743 @xref{Continuing and Stepping, continue}.
5747 @xref{Continuing and Stepping, finish}.
5751 @xref{Continuing and Stepping, until}.
5755 Background execution is especially useful in conjunction with non-stop
5756 mode for debugging programs with multiple threads; see @ref{Non-Stop Mode}.
5757 However, you can also use these commands in the normal all-stop mode with
5758 the restriction that you cannot issue another execution command until the
5759 previous one finishes. Examples of commands that are valid in all-stop
5760 mode while the program is running include @code{help} and @code{info break}.
5762 You can interrupt your program while it is running in the background by
5763 using the @code{interrupt} command.
5770 Suspend execution of the running program. In all-stop mode,
5771 @code{interrupt} stops the whole process, but in non-stop mode, it stops
5772 only the current thread. To stop the whole program in non-stop mode,
5773 use @code{interrupt -a}.
5776 @node Thread-Specific Breakpoints
5777 @subsection Thread-Specific Breakpoints
5779 When your program has multiple threads (@pxref{Threads,, Debugging
5780 Programs with Multiple Threads}), you can choose whether to set
5781 breakpoints on all threads, or on a particular thread.
5784 @cindex breakpoints and threads
5785 @cindex thread breakpoints
5786 @kindex break @dots{} thread @var{threadno}
5787 @item break @var{linespec} thread @var{threadno}
5788 @itemx break @var{linespec} thread @var{threadno} if @dots{}
5789 @var{linespec} specifies source lines; there are several ways of
5790 writing them (@pxref{Specify Location}), but the effect is always to
5791 specify some source line.
5793 Use the qualifier @samp{thread @var{threadno}} with a breakpoint command
5794 to specify that you only want @value{GDBN} to stop the program when a
5795 particular thread reaches this breakpoint. @var{threadno} is one of the
5796 numeric thread identifiers assigned by @value{GDBN}, shown in the first
5797 column of the @samp{info threads} display.
5799 If you do not specify @samp{thread @var{threadno}} when you set a
5800 breakpoint, the breakpoint applies to @emph{all} threads of your
5803 You can use the @code{thread} qualifier on conditional breakpoints as
5804 well; in this case, place @samp{thread @var{threadno}} before or
5805 after the breakpoint condition, like this:
5808 (@value{GDBP}) break frik.c:13 thread 28 if bartab > lim
5813 @node Interrupted System Calls
5814 @subsection Interrupted System Calls
5816 @cindex thread breakpoints and system calls
5817 @cindex system calls and thread breakpoints
5818 @cindex premature return from system calls
5819 There is an unfortunate side effect when using @value{GDBN} to debug
5820 multi-threaded programs. If one thread stops for a
5821 breakpoint, or for some other reason, and another thread is blocked in a
5822 system call, then the system call may return prematurely. This is a
5823 consequence of the interaction between multiple threads and the signals
5824 that @value{GDBN} uses to implement breakpoints and other events that
5827 To handle this problem, your program should check the return value of
5828 each system call and react appropriately. This is good programming
5831 For example, do not write code like this:
5837 The call to @code{sleep} will return early if a different thread stops
5838 at a breakpoint or for some other reason.
5840 Instead, write this:
5845 unslept = sleep (unslept);
5848 A system call is allowed to return early, so the system is still
5849 conforming to its specification. But @value{GDBN} does cause your
5850 multi-threaded program to behave differently than it would without
5853 Also, @value{GDBN} uses internal breakpoints in the thread library to
5854 monitor certain events such as thread creation and thread destruction.
5855 When such an event happens, a system call in another thread may return
5856 prematurely, even though your program does not appear to stop.
5859 @subsection Observer Mode
5861 If you want to build on non-stop mode and observe program behavior
5862 without any chance of disruption by @value{GDBN}, you can set
5863 variables to disable all of the debugger's attempts to modify state,
5864 whether by writing memory, inserting breakpoints, etc. These operate
5865 at a low level, intercepting operations from all commands.
5867 When all of these are set to @code{off}, then @value{GDBN} is said to
5868 be @dfn{observer mode}. As a convenience, the variable
5869 @code{observer} can be set to disable these, plus enable non-stop
5872 Note that @value{GDBN} will not prevent you from making nonsensical
5873 combinations of these settings. For instance, if you have enabled
5874 @code{may-insert-breakpoints} but disabled @code{may-write-memory},
5875 then breakpoints that work by writing trap instructions into the code
5876 stream will still not be able to be placed.
5881 @item set observer on
5882 @itemx set observer off
5883 When set to @code{on}, this disables all the permission variables
5884 below (except for @code{insert-fast-tracepoints}), plus enables
5885 non-stop debugging. Setting this to @code{off} switches back to
5886 normal debugging, though remaining in non-stop mode.
5889 Show whether observer mode is on or off.
5891 @kindex may-write-registers
5892 @item set may-write-registers on
5893 @itemx set may-write-registers off
5894 This controls whether @value{GDBN} will attempt to alter the values of
5895 registers, such as with assignment expressions in @code{print}, or the
5896 @code{jump} command. It defaults to @code{on}.
5898 @item show may-write-registers
5899 Show the current permission to write registers.
5901 @kindex may-write-memory
5902 @item set may-write-memory on
5903 @itemx set may-write-memory off
5904 This controls whether @value{GDBN} will attempt to alter the contents
5905 of memory, such as with assignment expressions in @code{print}. It
5906 defaults to @code{on}.
5908 @item show may-write-memory
5909 Show the current permission to write memory.
5911 @kindex may-insert-breakpoints
5912 @item set may-insert-breakpoints on
5913 @itemx set may-insert-breakpoints off
5914 This controls whether @value{GDBN} will attempt to insert breakpoints.
5915 This affects all breakpoints, including internal breakpoints defined
5916 by @value{GDBN}. It defaults to @code{on}.
5918 @item show may-insert-breakpoints
5919 Show the current permission to insert breakpoints.
5921 @kindex may-insert-tracepoints
5922 @item set may-insert-tracepoints on
5923 @itemx set may-insert-tracepoints off
5924 This controls whether @value{GDBN} will attempt to insert (regular)
5925 tracepoints at the beginning of a tracing experiment. It affects only
5926 non-fast tracepoints, fast tracepoints being under the control of
5927 @code{may-insert-fast-tracepoints}. It defaults to @code{on}.
5929 @item show may-insert-tracepoints
5930 Show the current permission to insert tracepoints.
5932 @kindex may-insert-fast-tracepoints
5933 @item set may-insert-fast-tracepoints on
5934 @itemx set may-insert-fast-tracepoints off
5935 This controls whether @value{GDBN} will attempt to insert fast
5936 tracepoints at the beginning of a tracing experiment. It affects only
5937 fast tracepoints, regular (non-fast) tracepoints being under the
5938 control of @code{may-insert-tracepoints}. It defaults to @code{on}.
5940 @item show may-insert-fast-tracepoints
5941 Show the current permission to insert fast tracepoints.
5943 @kindex may-interrupt
5944 @item set may-interrupt on
5945 @itemx set may-interrupt off
5946 This controls whether @value{GDBN} will attempt to interrupt or stop
5947 program execution. When this variable is @code{off}, the
5948 @code{interrupt} command will have no effect, nor will
5949 @kbd{Ctrl-c}. It defaults to @code{on}.
5951 @item show may-interrupt
5952 Show the current permission to interrupt or stop the program.
5956 @node Reverse Execution
5957 @chapter Running programs backward
5958 @cindex reverse execution
5959 @cindex running programs backward
5961 When you are debugging a program, it is not unusual to realize that
5962 you have gone too far, and some event of interest has already happened.
5963 If the target environment supports it, @value{GDBN} can allow you to
5964 ``rewind'' the program by running it backward.
5966 A target environment that supports reverse execution should be able
5967 to ``undo'' the changes in machine state that have taken place as the
5968 program was executing normally. Variables, registers etc.@: should
5969 revert to their previous values. Obviously this requires a great
5970 deal of sophistication on the part of the target environment; not
5971 all target environments can support reverse execution.
5973 When a program is executed in reverse, the instructions that
5974 have most recently been executed are ``un-executed'', in reverse
5975 order. The program counter runs backward, following the previous
5976 thread of execution in reverse. As each instruction is ``un-executed'',
5977 the values of memory and/or registers that were changed by that
5978 instruction are reverted to their previous states. After executing
5979 a piece of source code in reverse, all side effects of that code
5980 should be ``undone'', and all variables should be returned to their
5981 prior values@footnote{
5982 Note that some side effects are easier to undo than others. For instance,
5983 memory and registers are relatively easy, but device I/O is hard. Some
5984 targets may be able undo things like device I/O, and some may not.
5986 The contract between @value{GDBN} and the reverse executing target
5987 requires only that the target do something reasonable when
5988 @value{GDBN} tells it to execute backwards, and then report the
5989 results back to @value{GDBN}. Whatever the target reports back to
5990 @value{GDBN}, @value{GDBN} will report back to the user. @value{GDBN}
5991 assumes that the memory and registers that the target reports are in a
5992 consistant state, but @value{GDBN} accepts whatever it is given.
5995 If you are debugging in a target environment that supports
5996 reverse execution, @value{GDBN} provides the following commands.
5999 @kindex reverse-continue
6000 @kindex rc @r{(@code{reverse-continue})}
6001 @item reverse-continue @r{[}@var{ignore-count}@r{]}
6002 @itemx rc @r{[}@var{ignore-count}@r{]}
6003 Beginning at the point where your program last stopped, start executing
6004 in reverse. Reverse execution will stop for breakpoints and synchronous
6005 exceptions (signals), just like normal execution. Behavior of
6006 asynchronous signals depends on the target environment.
6008 @kindex reverse-step
6009 @kindex rs @r{(@code{step})}
6010 @item reverse-step @r{[}@var{count}@r{]}
6011 Run the program backward until control reaches the start of a
6012 different source line; then stop it, and return control to @value{GDBN}.
6014 Like the @code{step} command, @code{reverse-step} will only stop
6015 at the beginning of a source line. It ``un-executes'' the previously
6016 executed source line. If the previous source line included calls to
6017 debuggable functions, @code{reverse-step} will step (backward) into
6018 the called function, stopping at the beginning of the @emph{last}
6019 statement in the called function (typically a return statement).
6021 Also, as with the @code{step} command, if non-debuggable functions are
6022 called, @code{reverse-step} will run thru them backward without stopping.
6024 @kindex reverse-stepi
6025 @kindex rsi @r{(@code{reverse-stepi})}
6026 @item reverse-stepi @r{[}@var{count}@r{]}
6027 Reverse-execute one machine instruction. Note that the instruction
6028 to be reverse-executed is @emph{not} the one pointed to by the program
6029 counter, but the instruction executed prior to that one. For instance,
6030 if the last instruction was a jump, @code{reverse-stepi} will take you
6031 back from the destination of the jump to the jump instruction itself.
6033 @kindex reverse-next
6034 @kindex rn @r{(@code{reverse-next})}
6035 @item reverse-next @r{[}@var{count}@r{]}
6036 Run backward to the beginning of the previous line executed in
6037 the current (innermost) stack frame. If the line contains function
6038 calls, they will be ``un-executed'' without stopping. Starting from
6039 the first line of a function, @code{reverse-next} will take you back
6040 to the caller of that function, @emph{before} the function was called,
6041 just as the normal @code{next} command would take you from the last
6042 line of a function back to its return to its caller
6043 @footnote{Unless the code is too heavily optimized.}.
6045 @kindex reverse-nexti
6046 @kindex rni @r{(@code{reverse-nexti})}
6047 @item reverse-nexti @r{[}@var{count}@r{]}
6048 Like @code{nexti}, @code{reverse-nexti} executes a single instruction
6049 in reverse, except that called functions are ``un-executed'' atomically.
6050 That is, if the previously executed instruction was a return from
6051 another function, @code{reverse-nexti} will continue to execute
6052 in reverse until the call to that function (from the current stack
6055 @kindex reverse-finish
6056 @item reverse-finish
6057 Just as the @code{finish} command takes you to the point where the
6058 current function returns, @code{reverse-finish} takes you to the point
6059 where it was called. Instead of ending up at the end of the current
6060 function invocation, you end up at the beginning.
6062 @kindex set exec-direction
6063 @item set exec-direction
6064 Set the direction of target execution.
6065 @item set exec-direction reverse
6066 @cindex execute forward or backward in time
6067 @value{GDBN} will perform all execution commands in reverse, until the
6068 exec-direction mode is changed to ``forward''. Affected commands include
6069 @code{step, stepi, next, nexti, continue, and finish}. The @code{return}
6070 command cannot be used in reverse mode.
6071 @item set exec-direction forward
6072 @value{GDBN} will perform all execution commands in the normal fashion.
6073 This is the default.
6077 @node Process Record and Replay
6078 @chapter Recording Inferior's Execution and Replaying It
6079 @cindex process record and replay
6080 @cindex recording inferior's execution and replaying it
6082 On some platforms, @value{GDBN} provides a special @dfn{process record
6083 and replay} target that can record a log of the process execution, and
6084 replay it later with both forward and reverse execution commands.
6087 When this target is in use, if the execution log includes the record
6088 for the next instruction, @value{GDBN} will debug in @dfn{replay
6089 mode}. In the replay mode, the inferior does not really execute code
6090 instructions. Instead, all the events that normally happen during
6091 code execution are taken from the execution log. While code is not
6092 really executed in replay mode, the values of registers (including the
6093 program counter register) and the memory of the inferior are still
6094 changed as they normally would. Their contents are taken from the
6098 If the record for the next instruction is not in the execution log,
6099 @value{GDBN} will debug in @dfn{record mode}. In this mode, the
6100 inferior executes normally, and @value{GDBN} records the execution log
6103 The process record and replay target supports reverse execution
6104 (@pxref{Reverse Execution}), even if the platform on which the
6105 inferior runs does not. However, the reverse execution is limited in
6106 this case by the range of the instructions recorded in the execution
6107 log. In other words, reverse execution on platforms that don't
6108 support it directly can only be done in the replay mode.
6110 When debugging in the reverse direction, @value{GDBN} will work in
6111 replay mode as long as the execution log includes the record for the
6112 previous instruction; otherwise, it will work in record mode, if the
6113 platform supports reverse execution, or stop if not.
6115 For architecture environments that support process record and replay,
6116 @value{GDBN} provides the following commands:
6119 @kindex target record
6120 @kindex target record-full
6121 @kindex target record-btrace
6124 @kindex record btrace
6128 @item record @var{method}
6129 This command starts the process record and replay target. The
6130 recording method can be specified as parameter. Without a parameter
6131 the command uses the @code{full} recording method. The following
6132 recording methods are available:
6136 Full record/replay recording using @value{GDBN}'s software record and
6137 replay implementation. This method allows replaying and reverse
6141 Hardware-supported instruction recording. This method does not allow
6142 replaying and reverse execution.
6144 This recording method may not be available on all processors.
6147 The process record and replay target can only debug a process that is
6148 already running. Therefore, you need first to start the process with
6149 the @kbd{run} or @kbd{start} commands, and then start the recording
6150 with the @kbd{record @var{method}} command.
6152 Both @code{record @var{method}} and @code{rec @var{method}} are
6153 aliases of @code{target record-@var{method}}.
6155 @cindex displaced stepping, and process record and replay
6156 Displaced stepping (@pxref{Maintenance Commands,, displaced stepping})
6157 will be automatically disabled when process record and replay target
6158 is started. That's because the process record and replay target
6159 doesn't support displaced stepping.
6161 @cindex non-stop mode, and process record and replay
6162 @cindex asynchronous execution, and process record and replay
6163 If the inferior is in the non-stop mode (@pxref{Non-Stop Mode}) or in
6164 the asynchronous execution mode (@pxref{Background Execution}), not
6165 all recording methods are available. The @code{full} recording method
6166 does not support these two modes.
6171 Stop the process record and replay target. When process record and
6172 replay target stops, the entire execution log will be deleted and the
6173 inferior will either be terminated, or will remain in its final state.
6175 When you stop the process record and replay target in record mode (at
6176 the end of the execution log), the inferior will be stopped at the
6177 next instruction that would have been recorded. In other words, if
6178 you record for a while and then stop recording, the inferior process
6179 will be left in the same state as if the recording never happened.
6181 On the other hand, if the process record and replay target is stopped
6182 while in replay mode (that is, not at the end of the execution log,
6183 but at some earlier point), the inferior process will become ``live''
6184 at that earlier state, and it will then be possible to continue the
6185 usual ``live'' debugging of the process from that state.
6187 When the inferior process exits, or @value{GDBN} detaches from it,
6188 process record and replay target will automatically stop itself.
6191 @item record save @var{filename}
6192 Save the execution log to a file @file{@var{filename}}.
6193 Default filename is @file{gdb_record.@var{process_id}}, where
6194 @var{process_id} is the process ID of the inferior.
6196 This command may not be available for all recording methods.
6198 @kindex record restore
6199 @item record restore @var{filename}
6200 Restore the execution log from a file @file{@var{filename}}.
6201 File must have been created with @code{record save}.
6203 @kindex set record full
6204 @item set record full insn-number-max @var{limit}
6205 Set the limit of instructions to be recorded for the @code{full}
6206 recording method. Default value is 200000.
6208 If @var{limit} is a positive number, then @value{GDBN} will start
6209 deleting instructions from the log once the number of the record
6210 instructions becomes greater than @var{limit}. For every new recorded
6211 instruction, @value{GDBN} will delete the earliest recorded
6212 instruction to keep the number of recorded instructions at the limit.
6213 (Since deleting recorded instructions loses information, @value{GDBN}
6214 lets you control what happens when the limit is reached, by means of
6215 the @code{stop-at-limit} option, described below.)
6217 If @var{limit} is zero, @value{GDBN} will never delete recorded
6218 instructions from the execution log. The number of recorded
6219 instructions is unlimited in this case.
6221 @kindex show record full
6222 @item show record full insn-number-max
6223 Show the limit of instructions to be recorded with the @code{full}
6226 @item set record full stop-at-limit
6227 Control the behavior of the @code{full} recording method when the
6228 number of recorded instructions reaches the limit. If ON (the
6229 default), @value{GDBN} will stop when the limit is reached for the
6230 first time and ask you whether you want to stop the inferior or
6231 continue running it and recording the execution log. If you decide
6232 to continue recording, each new recorded instruction will cause the
6233 oldest one to be deleted.
6235 If this option is OFF, @value{GDBN} will automatically delete the
6236 oldest record to make room for each new one, without asking.
6238 @item show record full stop-at-limit
6239 Show the current setting of @code{stop-at-limit}.
6241 @item set record full memory-query
6242 Control the behavior when @value{GDBN} is unable to record memory
6243 changes caused by an instruction for the @code{full} recording method.
6244 If ON, @value{GDBN} will query whether to stop the inferior in that
6247 If this option is OFF (the default), @value{GDBN} will automatically
6248 ignore the effect of such instructions on memory. Later, when
6249 @value{GDBN} replays this execution log, it will mark the log of this
6250 instruction as not accessible, and it will not affect the replay
6253 @item show record full memory-query
6254 Show the current setting of @code{memory-query}.
6258 Show various statistics about the recording depending on the recording
6263 For the @code{full} recording method, it shows the state of process
6264 record and its in-memory execution log buffer, including:
6268 Whether in record mode or replay mode.
6270 Lowest recorded instruction number (counting from when the current execution log started recording instructions).
6272 Highest recorded instruction number.
6274 Current instruction about to be replayed (if in replay mode).
6276 Number of instructions contained in the execution log.
6278 Maximum number of instructions that may be contained in the execution log.
6282 For the @code{btrace} recording method, it shows the number of
6283 instructions that have been recorded and the number of blocks of
6284 sequential control-flow that is formed by the recorded instructions.
6287 @kindex record delete
6290 When record target runs in replay mode (``in the past''), delete the
6291 subsequent execution log and begin to record a new execution log starting
6292 from the current address. This means you will abandon the previously
6293 recorded ``future'' and begin recording a new ``future''.
6295 @kindex record instruction-history
6296 @kindex rec instruction-history
6297 @item record instruction-history
6298 Disassembles instructions from the recorded execution log. By
6299 default, ten instructions are disassembled. This can be changed using
6300 the @code{set record instruction-history-size} command. Instructions
6301 are printed in execution order. There are several ways to specify
6302 what part of the execution log to disassemble:
6305 @item record instruction-history @var{insn}
6306 Disassembles ten instructions starting from instruction number
6309 @item record instruction-history @var{insn}, +/-@var{n}
6310 Disassembles @var{n} instructions around instruction number
6311 @var{insn}. If @var{n} is preceded with @code{+}, disassembles
6312 @var{n} instructions after instruction number @var{insn}. If
6313 @var{n} is preceded with @code{-}, disassembles @var{n}
6314 instructions before instruction number @var{insn}.
6316 @item record instruction-history
6317 Disassembles ten more instructions after the last disassembly.
6319 @item record instruction-history -
6320 Disassembles ten more instructions before the last disassembly.
6322 @item record instruction-history @var{begin} @var{end}
6323 Disassembles instructions beginning with instruction number
6324 @var{begin} until instruction number @var{end}. The instruction
6325 number @var{end} is not included.
6328 This command may not be available for all recording methods.
6331 @item set record instruction-history-size
6332 Define how many instructions to disassemble in the @code{record
6333 instruction-history} command. The default value is 10.
6336 @item show record instruction-history-size
6337 Show how many instructions to disassemble in the @code{record
6338 instruction-history} command.
6340 @kindex record function-call-history
6341 @kindex rec function-call-history
6342 @item record function-call-history
6343 Prints the execution history at function granularity. It prints one
6344 line for each sequence of instructions that belong to the same
6345 function giving the name of that function, the source lines
6346 for this instruction sequence (if the @code{/l} modifier is
6347 specified), and the instructions numbers that form the sequence (if
6348 the @code{/i} modifier is specified).
6351 (@value{GDBP}) @b{list 1, 10}
6362 (@value{GDBP}) @b{record function-call-history /l}
6368 By default, ten lines are printed. This can be changed using the
6369 @code{set record function-call-history-size} command. Functions are
6370 printed in execution order. There are several ways to specify what
6374 @item record function-call-history @var{func}
6375 Prints ten functions starting from function number @var{func}.
6377 @item record function-call-history @var{func}, +/-@var{n}
6378 Prints @var{n} functions around function number @var{func}. If
6379 @var{n} is preceded with @code{+}, prints @var{n} functions after
6380 function number @var{func}. If @var{n} is preceded with @code{-},
6381 prints @var{n} functions before function number @var{func}.
6383 @item record function-call-history
6384 Prints ten more functions after the last ten-line print.
6386 @item record function-call-history -
6387 Prints ten more functions before the last ten-line print.
6389 @item record function-call-history @var{begin} @var{end}
6390 Prints functions beginning with function number @var{begin} until
6391 function number @var{end}. The function number @var{end} is not
6395 This command may not be available for all recording methods.
6397 @item set record function-call-history-size
6398 Define how many lines to print in the
6399 @code{record function-call-history} command. The default value is 10.
6401 @item show record function-call-history-size
6402 Show how many lines to print in the
6403 @code{record function-call-history} command.
6408 @chapter Examining the Stack
6410 When your program has stopped, the first thing you need to know is where it
6411 stopped and how it got there.
6414 Each time your program performs a function call, information about the call
6416 That information includes the location of the call in your program,
6417 the arguments of the call,
6418 and the local variables of the function being called.
6419 The information is saved in a block of data called a @dfn{stack frame}.
6420 The stack frames are allocated in a region of memory called the @dfn{call
6423 When your program stops, the @value{GDBN} commands for examining the
6424 stack allow you to see all of this information.
6426 @cindex selected frame
6427 One of the stack frames is @dfn{selected} by @value{GDBN} and many
6428 @value{GDBN} commands refer implicitly to the selected frame. In
6429 particular, whenever you ask @value{GDBN} for the value of a variable in
6430 your program, the value is found in the selected frame. There are
6431 special @value{GDBN} commands to select whichever frame you are
6432 interested in. @xref{Selection, ,Selecting a Frame}.
6434 When your program stops, @value{GDBN} automatically selects the
6435 currently executing frame and describes it briefly, similar to the
6436 @code{frame} command (@pxref{Frame Info, ,Information about a Frame}).
6439 * Frames:: Stack frames
6440 * Backtrace:: Backtraces
6441 * Selection:: Selecting a frame
6442 * Frame Info:: Information on a frame
6447 @section Stack Frames
6449 @cindex frame, definition
6451 The call stack is divided up into contiguous pieces called @dfn{stack
6452 frames}, or @dfn{frames} for short; each frame is the data associated
6453 with one call to one function. The frame contains the arguments given
6454 to the function, the function's local variables, and the address at
6455 which the function is executing.
6457 @cindex initial frame
6458 @cindex outermost frame
6459 @cindex innermost frame
6460 When your program is started, the stack has only one frame, that of the
6461 function @code{main}. This is called the @dfn{initial} frame or the
6462 @dfn{outermost} frame. Each time a function is called, a new frame is
6463 made. Each time a function returns, the frame for that function invocation
6464 is eliminated. If a function is recursive, there can be many frames for
6465 the same function. The frame for the function in which execution is
6466 actually occurring is called the @dfn{innermost} frame. This is the most
6467 recently created of all the stack frames that still exist.
6469 @cindex frame pointer
6470 Inside your program, stack frames are identified by their addresses. A
6471 stack frame consists of many bytes, each of which has its own address; each
6472 kind of computer has a convention for choosing one byte whose
6473 address serves as the address of the frame. Usually this address is kept
6474 in a register called the @dfn{frame pointer register}
6475 (@pxref{Registers, $fp}) while execution is going on in that frame.
6477 @cindex frame number
6478 @value{GDBN} assigns numbers to all existing stack frames, starting with
6479 zero for the innermost frame, one for the frame that called it,
6480 and so on upward. These numbers do not really exist in your program;
6481 they are assigned by @value{GDBN} to give you a way of designating stack
6482 frames in @value{GDBN} commands.
6484 @c The -fomit-frame-pointer below perennially causes hbox overflow
6485 @c underflow problems.
6486 @cindex frameless execution
6487 Some compilers provide a way to compile functions so that they operate
6488 without stack frames. (For example, the @value{NGCC} option
6490 @samp{-fomit-frame-pointer}
6492 generates functions without a frame.)
6493 This is occasionally done with heavily used library functions to save
6494 the frame setup time. @value{GDBN} has limited facilities for dealing
6495 with these function invocations. If the innermost function invocation
6496 has no stack frame, @value{GDBN} nevertheless regards it as though
6497 it had a separate frame, which is numbered zero as usual, allowing
6498 correct tracing of the function call chain. However, @value{GDBN} has
6499 no provision for frameless functions elsewhere in the stack.
6502 @kindex frame@r{, command}
6503 @cindex current stack frame
6504 @item frame @var{args}
6505 The @code{frame} command allows you to move from one stack frame to another,
6506 and to print the stack frame you select. @var{args} may be either the
6507 address of the frame or the stack frame number. Without an argument,
6508 @code{frame} prints the current stack frame.
6510 @kindex select-frame
6511 @cindex selecting frame silently
6513 The @code{select-frame} command allows you to move from one stack frame
6514 to another without printing the frame. This is the silent version of
6522 @cindex call stack traces
6523 A backtrace is a summary of how your program got where it is. It shows one
6524 line per frame, for many frames, starting with the currently executing
6525 frame (frame zero), followed by its caller (frame one), and on up the
6530 @kindex bt @r{(@code{backtrace})}
6533 Print a backtrace of the entire stack: one line per frame for all
6534 frames in the stack.
6536 You can stop the backtrace at any time by typing the system interrupt
6537 character, normally @kbd{Ctrl-c}.
6539 @item backtrace @var{n}
6541 Similar, but print only the innermost @var{n} frames.
6543 @item backtrace -@var{n}
6545 Similar, but print only the outermost @var{n} frames.
6547 @item backtrace full
6549 @itemx bt full @var{n}
6550 @itemx bt full -@var{n}
6551 Print the values of the local variables also. @var{n} specifies the
6552 number of frames to print, as described above.
6557 The names @code{where} and @code{info stack} (abbreviated @code{info s})
6558 are additional aliases for @code{backtrace}.
6560 @cindex multiple threads, backtrace
6561 In a multi-threaded program, @value{GDBN} by default shows the
6562 backtrace only for the current thread. To display the backtrace for
6563 several or all of the threads, use the command @code{thread apply}
6564 (@pxref{Threads, thread apply}). For example, if you type @kbd{thread
6565 apply all backtrace}, @value{GDBN} will display the backtrace for all
6566 the threads; this is handy when you debug a core dump of a
6567 multi-threaded program.
6569 Each line in the backtrace shows the frame number and the function name.
6570 The program counter value is also shown---unless you use @code{set
6571 print address off}. The backtrace also shows the source file name and
6572 line number, as well as the arguments to the function. The program
6573 counter value is omitted if it is at the beginning of the code for that
6576 Here is an example of a backtrace. It was made with the command
6577 @samp{bt 3}, so it shows the innermost three frames.
6581 #0 m4_traceon (obs=0x24eb0, argc=1, argv=0x2b8c8)
6583 #1 0x6e38 in expand_macro (sym=0x2b600, data=...) at macro.c:242
6584 #2 0x6840 in expand_token (obs=0x0, t=177664, td=0xf7fffb08)
6586 (More stack frames follow...)
6591 The display for frame zero does not begin with a program counter
6592 value, indicating that your program has stopped at the beginning of the
6593 code for line @code{993} of @code{builtin.c}.
6596 The value of parameter @code{data} in frame 1 has been replaced by
6597 @code{@dots{}}. By default, @value{GDBN} prints the value of a parameter
6598 only if it is a scalar (integer, pointer, enumeration, etc). See command
6599 @kbd{set print frame-arguments} in @ref{Print Settings} for more details
6600 on how to configure the way function parameter values are printed.
6602 @cindex optimized out, in backtrace
6603 @cindex function call arguments, optimized out
6604 If your program was compiled with optimizations, some compilers will
6605 optimize away arguments passed to functions if those arguments are
6606 never used after the call. Such optimizations generate code that
6607 passes arguments through registers, but doesn't store those arguments
6608 in the stack frame. @value{GDBN} has no way of displaying such
6609 arguments in stack frames other than the innermost one. Here's what
6610 such a backtrace might look like:
6614 #0 m4_traceon (obs=0x24eb0, argc=1, argv=0x2b8c8)
6616 #1 0x6e38 in expand_macro (sym=<optimized out>) at macro.c:242
6617 #2 0x6840 in expand_token (obs=0x0, t=<optimized out>, td=0xf7fffb08)
6619 (More stack frames follow...)
6624 The values of arguments that were not saved in their stack frames are
6625 shown as @samp{<optimized out>}.
6627 If you need to display the values of such optimized-out arguments,
6628 either deduce that from other variables whose values depend on the one
6629 you are interested in, or recompile without optimizations.
6631 @cindex backtrace beyond @code{main} function
6632 @cindex program entry point
6633 @cindex startup code, and backtrace
6634 Most programs have a standard user entry point---a place where system
6635 libraries and startup code transition into user code. For C this is
6636 @code{main}@footnote{
6637 Note that embedded programs (the so-called ``free-standing''
6638 environment) are not required to have a @code{main} function as the
6639 entry point. They could even have multiple entry points.}.
6640 When @value{GDBN} finds the entry function in a backtrace
6641 it will terminate the backtrace, to avoid tracing into highly
6642 system-specific (and generally uninteresting) code.
6644 If you need to examine the startup code, or limit the number of levels
6645 in a backtrace, you can change this behavior:
6648 @item set backtrace past-main
6649 @itemx set backtrace past-main on
6650 @kindex set backtrace
6651 Backtraces will continue past the user entry point.
6653 @item set backtrace past-main off
6654 Backtraces will stop when they encounter the user entry point. This is the
6657 @item show backtrace past-main
6658 @kindex show backtrace
6659 Display the current user entry point backtrace policy.
6661 @item set backtrace past-entry
6662 @itemx set backtrace past-entry on
6663 Backtraces will continue past the internal entry point of an application.
6664 This entry point is encoded by the linker when the application is built,
6665 and is likely before the user entry point @code{main} (or equivalent) is called.
6667 @item set backtrace past-entry off
6668 Backtraces will stop when they encounter the internal entry point of an
6669 application. This is the default.
6671 @item show backtrace past-entry
6672 Display the current internal entry point backtrace policy.
6674 @item set backtrace limit @var{n}
6675 @itemx set backtrace limit 0
6676 @cindex backtrace limit
6677 Limit the backtrace to @var{n} levels. A value of zero means
6680 @item show backtrace limit
6681 Display the current limit on backtrace levels.
6684 You can control how file names are displayed.
6687 @item set filename-display
6688 @itemx set filename-display relative
6689 @cindex filename-display
6690 Display file names relative to the compilation directory. This is the default.
6692 @item set filename-display basename
6693 Display only basename of a filename.
6695 @item set filename-display absolute
6696 Display an absolute filename.
6698 @item show filename-display
6699 Show the current way to display filenames.
6703 @section Selecting a Frame
6705 Most commands for examining the stack and other data in your program work on
6706 whichever stack frame is selected at the moment. Here are the commands for
6707 selecting a stack frame; all of them finish by printing a brief description
6708 of the stack frame just selected.
6711 @kindex frame@r{, selecting}
6712 @kindex f @r{(@code{frame})}
6715 Select frame number @var{n}. Recall that frame zero is the innermost
6716 (currently executing) frame, frame one is the frame that called the
6717 innermost one, and so on. The highest-numbered frame is the one for
6720 @item frame @var{addr}
6722 Select the frame at address @var{addr}. This is useful mainly if the
6723 chaining of stack frames has been damaged by a bug, making it
6724 impossible for @value{GDBN} to assign numbers properly to all frames. In
6725 addition, this can be useful when your program has multiple stacks and
6726 switches between them.
6728 On the SPARC architecture, @code{frame} needs two addresses to
6729 select an arbitrary frame: a frame pointer and a stack pointer.
6731 On the @acronym{MIPS} and Alpha architecture, it needs two addresses: a stack
6732 pointer and a program counter.
6734 On the 29k architecture, it needs three addresses: a register stack
6735 pointer, a program counter, and a memory stack pointer.
6739 Move @var{n} frames up the stack. For positive numbers @var{n}, this
6740 advances toward the outermost frame, to higher frame numbers, to frames
6741 that have existed longer. @var{n} defaults to one.
6744 @kindex do @r{(@code{down})}
6746 Move @var{n} frames down the stack. For positive numbers @var{n}, this
6747 advances toward the innermost frame, to lower frame numbers, to frames
6748 that were created more recently. @var{n} defaults to one. You may
6749 abbreviate @code{down} as @code{do}.
6752 All of these commands end by printing two lines of output describing the
6753 frame. The first line shows the frame number, the function name, the
6754 arguments, and the source file and line number of execution in that
6755 frame. The second line shows the text of that source line.
6763 #1 0x22f0 in main (argc=1, argv=0xf7fffbf4, env=0xf7fffbfc)
6765 10 read_input_file (argv[i]);
6769 After such a printout, the @code{list} command with no arguments
6770 prints ten lines centered on the point of execution in the frame.
6771 You can also edit the program at the point of execution with your favorite
6772 editing program by typing @code{edit}.
6773 @xref{List, ,Printing Source Lines},
6777 @kindex down-silently
6779 @item up-silently @var{n}
6780 @itemx down-silently @var{n}
6781 These two commands are variants of @code{up} and @code{down},
6782 respectively; they differ in that they do their work silently, without
6783 causing display of the new frame. They are intended primarily for use
6784 in @value{GDBN} command scripts, where the output might be unnecessary and
6789 @section Information About a Frame
6791 There are several other commands to print information about the selected
6797 When used without any argument, this command does not change which
6798 frame is selected, but prints a brief description of the currently
6799 selected stack frame. It can be abbreviated @code{f}. With an
6800 argument, this command is used to select a stack frame.
6801 @xref{Selection, ,Selecting a Frame}.
6804 @kindex info f @r{(@code{info frame})}
6807 This command prints a verbose description of the selected stack frame,
6812 the address of the frame
6814 the address of the next frame down (called by this frame)
6816 the address of the next frame up (caller of this frame)
6818 the language in which the source code corresponding to this frame is written
6820 the address of the frame's arguments
6822 the address of the frame's local variables
6824 the program counter saved in it (the address of execution in the caller frame)
6826 which registers were saved in the frame
6829 @noindent The verbose description is useful when
6830 something has gone wrong that has made the stack format fail to fit
6831 the usual conventions.
6833 @item info frame @var{addr}
6834 @itemx info f @var{addr}
6835 Print a verbose description of the frame at address @var{addr}, without
6836 selecting that frame. The selected frame remains unchanged by this
6837 command. This requires the same kind of address (more than one for some
6838 architectures) that you specify in the @code{frame} command.
6839 @xref{Selection, ,Selecting a Frame}.
6843 Print the arguments of the selected frame, each on a separate line.
6847 Print the local variables of the selected frame, each on a separate
6848 line. These are all variables (declared either static or automatic)
6849 accessible at the point of execution of the selected frame.
6855 @chapter Examining Source Files
6857 @value{GDBN} can print parts of your program's source, since the debugging
6858 information recorded in the program tells @value{GDBN} what source files were
6859 used to build it. When your program stops, @value{GDBN} spontaneously prints
6860 the line where it stopped. Likewise, when you select a stack frame
6861 (@pxref{Selection, ,Selecting a Frame}), @value{GDBN} prints the line where
6862 execution in that frame has stopped. You can print other portions of
6863 source files by explicit command.
6865 If you use @value{GDBN} through its @sc{gnu} Emacs interface, you may
6866 prefer to use Emacs facilities to view source; see @ref{Emacs, ,Using
6867 @value{GDBN} under @sc{gnu} Emacs}.
6870 * List:: Printing source lines
6871 * Specify Location:: How to specify code locations
6872 * Edit:: Editing source files
6873 * Search:: Searching source files
6874 * Source Path:: Specifying source directories
6875 * Machine Code:: Source and machine code
6879 @section Printing Source Lines
6882 @kindex l @r{(@code{list})}
6883 To print lines from a source file, use the @code{list} command
6884 (abbreviated @code{l}). By default, ten lines are printed.
6885 There are several ways to specify what part of the file you want to
6886 print; see @ref{Specify Location}, for the full list.
6888 Here are the forms of the @code{list} command most commonly used:
6891 @item list @var{linenum}
6892 Print lines centered around line number @var{linenum} in the
6893 current source file.
6895 @item list @var{function}
6896 Print lines centered around the beginning of function
6900 Print more lines. If the last lines printed were printed with a
6901 @code{list} command, this prints lines following the last lines
6902 printed; however, if the last line printed was a solitary line printed
6903 as part of displaying a stack frame (@pxref{Stack, ,Examining the
6904 Stack}), this prints lines centered around that line.
6907 Print lines just before the lines last printed.
6910 @cindex @code{list}, how many lines to display
6911 By default, @value{GDBN} prints ten source lines with any of these forms of
6912 the @code{list} command. You can change this using @code{set listsize}:
6915 @kindex set listsize
6916 @item set listsize @var{count}
6917 Make the @code{list} command display @var{count} source lines (unless
6918 the @code{list} argument explicitly specifies some other number).
6919 Setting @var{count} to -1 means there's no limit and 0 means suppress
6920 display of source lines.
6922 @kindex show listsize
6924 Display the number of lines that @code{list} prints.
6927 Repeating a @code{list} command with @key{RET} discards the argument,
6928 so it is equivalent to typing just @code{list}. This is more useful
6929 than listing the same lines again. An exception is made for an
6930 argument of @samp{-}; that argument is preserved in repetition so that
6931 each repetition moves up in the source file.
6933 In general, the @code{list} command expects you to supply zero, one or two
6934 @dfn{linespecs}. Linespecs specify source lines; there are several ways
6935 of writing them (@pxref{Specify Location}), but the effect is always
6936 to specify some source line.
6938 Here is a complete description of the possible arguments for @code{list}:
6941 @item list @var{linespec}
6942 Print lines centered around the line specified by @var{linespec}.
6944 @item list @var{first},@var{last}
6945 Print lines from @var{first} to @var{last}. Both arguments are
6946 linespecs. When a @code{list} command has two linespecs, and the
6947 source file of the second linespec is omitted, this refers to
6948 the same source file as the first linespec.
6950 @item list ,@var{last}
6951 Print lines ending with @var{last}.
6953 @item list @var{first},
6954 Print lines starting with @var{first}.
6957 Print lines just after the lines last printed.
6960 Print lines just before the lines last printed.
6963 As described in the preceding table.
6966 @node Specify Location
6967 @section Specifying a Location
6968 @cindex specifying location
6971 Several @value{GDBN} commands accept arguments that specify a location
6972 of your program's code. Since @value{GDBN} is a source-level
6973 debugger, a location usually specifies some line in the source code;
6974 for that reason, locations are also known as @dfn{linespecs}.
6976 Here are all the different ways of specifying a code location that
6977 @value{GDBN} understands:
6981 Specifies the line number @var{linenum} of the current source file.
6984 @itemx +@var{offset}
6985 Specifies the line @var{offset} lines before or after the @dfn{current
6986 line}. For the @code{list} command, the current line is the last one
6987 printed; for the breakpoint commands, this is the line at which
6988 execution stopped in the currently selected @dfn{stack frame}
6989 (@pxref{Frames, ,Frames}, for a description of stack frames.) When
6990 used as the second of the two linespecs in a @code{list} command,
6991 this specifies the line @var{offset} lines up or down from the first
6994 @item @var{filename}:@var{linenum}
6995 Specifies the line @var{linenum} in the source file @var{filename}.
6996 If @var{filename} is a relative file name, then it will match any
6997 source file name with the same trailing components. For example, if
6998 @var{filename} is @samp{gcc/expr.c}, then it will match source file
6999 name of @file{/build/trunk/gcc/expr.c}, but not
7000 @file{/build/trunk/libcpp/expr.c} or @file{/build/trunk/gcc/x-expr.c}.
7002 @item @var{function}
7003 Specifies the line that begins the body of the function @var{function}.
7004 For example, in C, this is the line with the open brace.
7006 @item @var{function}:@var{label}
7007 Specifies the line where @var{label} appears in @var{function}.
7009 @item @var{filename}:@var{function}
7010 Specifies the line that begins the body of the function @var{function}
7011 in the file @var{filename}. You only need the file name with a
7012 function name to avoid ambiguity when there are identically named
7013 functions in different source files.
7016 Specifies the line at which the label named @var{label} appears.
7017 @value{GDBN} searches for the label in the function corresponding to
7018 the currently selected stack frame. If there is no current selected
7019 stack frame (for instance, if the inferior is not running), then
7020 @value{GDBN} will not search for a label.
7022 @item *@var{address}
7023 Specifies the program address @var{address}. For line-oriented
7024 commands, such as @code{list} and @code{edit}, this specifies a source
7025 line that contains @var{address}. For @code{break} and other
7026 breakpoint oriented commands, this can be used to set breakpoints in
7027 parts of your program which do not have debugging information or
7030 Here @var{address} may be any expression valid in the current working
7031 language (@pxref{Languages, working language}) that specifies a code
7032 address. In addition, as a convenience, @value{GDBN} extends the
7033 semantics of expressions used in locations to cover the situations
7034 that frequently happen during debugging. Here are the various forms
7038 @item @var{expression}
7039 Any expression valid in the current working language.
7041 @item @var{funcaddr}
7042 An address of a function or procedure derived from its name. In C,
7043 C@t{++}, Java, Objective-C, Fortran, minimal, and assembly, this is
7044 simply the function's name @var{function} (and actually a special case
7045 of a valid expression). In Pascal and Modula-2, this is
7046 @code{&@var{function}}. In Ada, this is @code{@var{function}'Address}
7047 (although the Pascal form also works).
7049 This form specifies the address of the function's first instruction,
7050 before the stack frame and arguments have been set up.
7052 @item '@var{filename}'::@var{funcaddr}
7053 Like @var{funcaddr} above, but also specifies the name of the source
7054 file explicitly. This is useful if the name of the function does not
7055 specify the function unambiguously, e.g., if there are several
7056 functions with identical names in different source files.
7059 @cindex breakpoint at static probe point
7060 @item -pstap|-probe-stap @r{[}@var{objfile}:@r{[}@var{provider}:@r{]}@r{]}@var{name}
7061 The @sc{gnu}/Linux tool @code{SystemTap} provides a way for
7062 applications to embed static probes. @xref{Static Probe Points}, for more
7063 information on finding and using static probes. This form of linespec
7064 specifies the location of such a static probe.
7066 If @var{objfile} is given, only probes coming from that shared library
7067 or executable matching @var{objfile} as a regular expression are considered.
7068 If @var{provider} is given, then only probes from that provider are considered.
7069 If several probes match the spec, @value{GDBN} will insert a breakpoint at
7070 each one of those probes.
7076 @section Editing Source Files
7077 @cindex editing source files
7080 @kindex e @r{(@code{edit})}
7081 To edit the lines in a source file, use the @code{edit} command.
7082 The editing program of your choice
7083 is invoked with the current line set to
7084 the active line in the program.
7085 Alternatively, there are several ways to specify what part of the file you
7086 want to print if you want to see other parts of the program:
7089 @item edit @var{location}
7090 Edit the source file specified by @code{location}. Editing starts at
7091 that @var{location}, e.g., at the specified source line of the
7092 specified file. @xref{Specify Location}, for all the possible forms
7093 of the @var{location} argument; here are the forms of the @code{edit}
7094 command most commonly used:
7097 @item edit @var{number}
7098 Edit the current source file with @var{number} as the active line number.
7100 @item edit @var{function}
7101 Edit the file containing @var{function} at the beginning of its definition.
7106 @subsection Choosing your Editor
7107 You can customize @value{GDBN} to use any editor you want
7109 The only restriction is that your editor (say @code{ex}), recognizes the
7110 following command-line syntax:
7112 ex +@var{number} file
7114 The optional numeric value +@var{number} specifies the number of the line in
7115 the file where to start editing.}.
7116 By default, it is @file{@value{EDITOR}}, but you can change this
7117 by setting the environment variable @code{EDITOR} before using
7118 @value{GDBN}. For example, to configure @value{GDBN} to use the
7119 @code{vi} editor, you could use these commands with the @code{sh} shell:
7125 or in the @code{csh} shell,
7127 setenv EDITOR /usr/bin/vi
7132 @section Searching Source Files
7133 @cindex searching source files
7135 There are two commands for searching through the current source file for a
7140 @kindex forward-search
7141 @kindex fo @r{(@code{forward-search})}
7142 @item forward-search @var{regexp}
7143 @itemx search @var{regexp}
7144 The command @samp{forward-search @var{regexp}} checks each line,
7145 starting with the one following the last line listed, for a match for
7146 @var{regexp}. It lists the line that is found. You can use the
7147 synonym @samp{search @var{regexp}} or abbreviate the command name as
7150 @kindex reverse-search
7151 @item reverse-search @var{regexp}
7152 The command @samp{reverse-search @var{regexp}} checks each line, starting
7153 with the one before the last line listed and going backward, for a match
7154 for @var{regexp}. It lists the line that is found. You can abbreviate
7155 this command as @code{rev}.
7159 @section Specifying Source Directories
7162 @cindex directories for source files
7163 Executable programs sometimes do not record the directories of the source
7164 files from which they were compiled, just the names. Even when they do,
7165 the directories could be moved between the compilation and your debugging
7166 session. @value{GDBN} has a list of directories to search for source files;
7167 this is called the @dfn{source path}. Each time @value{GDBN} wants a source file,
7168 it tries all the directories in the list, in the order they are present
7169 in the list, until it finds a file with the desired name.
7171 For example, suppose an executable references the file
7172 @file{/usr/src/foo-1.0/lib/foo.c}, and our source path is
7173 @file{/mnt/cross}. The file is first looked up literally; if this
7174 fails, @file{/mnt/cross/usr/src/foo-1.0/lib/foo.c} is tried; if this
7175 fails, @file{/mnt/cross/foo.c} is opened; if this fails, an error
7176 message is printed. @value{GDBN} does not look up the parts of the
7177 source file name, such as @file{/mnt/cross/src/foo-1.0/lib/foo.c}.
7178 Likewise, the subdirectories of the source path are not searched: if
7179 the source path is @file{/mnt/cross}, and the binary refers to
7180 @file{foo.c}, @value{GDBN} would not find it under
7181 @file{/mnt/cross/usr/src/foo-1.0/lib}.
7183 Plain file names, relative file names with leading directories, file
7184 names containing dots, etc.@: are all treated as described above; for
7185 instance, if the source path is @file{/mnt/cross}, and the source file
7186 is recorded as @file{../lib/foo.c}, @value{GDBN} would first try
7187 @file{../lib/foo.c}, then @file{/mnt/cross/../lib/foo.c}, and after
7188 that---@file{/mnt/cross/foo.c}.
7190 Note that the executable search path is @emph{not} used to locate the
7193 Whenever you reset or rearrange the source path, @value{GDBN} clears out
7194 any information it has cached about where source files are found and where
7195 each line is in the file.
7199 When you start @value{GDBN}, its source path includes only @samp{cdir}
7200 and @samp{cwd}, in that order.
7201 To add other directories, use the @code{directory} command.
7203 The search path is used to find both program source files and @value{GDBN}
7204 script files (read using the @samp{-command} option and @samp{source} command).
7206 In addition to the source path, @value{GDBN} provides a set of commands
7207 that manage a list of source path substitution rules. A @dfn{substitution
7208 rule} specifies how to rewrite source directories stored in the program's
7209 debug information in case the sources were moved to a different
7210 directory between compilation and debugging. A rule is made of
7211 two strings, the first specifying what needs to be rewritten in
7212 the path, and the second specifying how it should be rewritten.
7213 In @ref{set substitute-path}, we name these two parts @var{from} and
7214 @var{to} respectively. @value{GDBN} does a simple string replacement
7215 of @var{from} with @var{to} at the start of the directory part of the
7216 source file name, and uses that result instead of the original file
7217 name to look up the sources.
7219 Using the previous example, suppose the @file{foo-1.0} tree has been
7220 moved from @file{/usr/src} to @file{/mnt/cross}, then you can tell
7221 @value{GDBN} to replace @file{/usr/src} in all source path names with
7222 @file{/mnt/cross}. The first lookup will then be
7223 @file{/mnt/cross/foo-1.0/lib/foo.c} in place of the original location
7224 of @file{/usr/src/foo-1.0/lib/foo.c}. To define a source path
7225 substitution rule, use the @code{set substitute-path} command
7226 (@pxref{set substitute-path}).
7228 To avoid unexpected substitution results, a rule is applied only if the
7229 @var{from} part of the directory name ends at a directory separator.
7230 For instance, a rule substituting @file{/usr/source} into
7231 @file{/mnt/cross} will be applied to @file{/usr/source/foo-1.0} but
7232 not to @file{/usr/sourceware/foo-2.0}. And because the substitution
7233 is applied only at the beginning of the directory name, this rule will
7234 not be applied to @file{/root/usr/source/baz.c} either.
7236 In many cases, you can achieve the same result using the @code{directory}
7237 command. However, @code{set substitute-path} can be more efficient in
7238 the case where the sources are organized in a complex tree with multiple
7239 subdirectories. With the @code{directory} command, you need to add each
7240 subdirectory of your project. If you moved the entire tree while
7241 preserving its internal organization, then @code{set substitute-path}
7242 allows you to direct the debugger to all the sources with one single
7245 @code{set substitute-path} is also more than just a shortcut command.
7246 The source path is only used if the file at the original location no
7247 longer exists. On the other hand, @code{set substitute-path} modifies
7248 the debugger behavior to look at the rewritten location instead. So, if
7249 for any reason a source file that is not relevant to your executable is
7250 located at the original location, a substitution rule is the only
7251 method available to point @value{GDBN} at the new location.
7253 @cindex @samp{--with-relocated-sources}
7254 @cindex default source path substitution
7255 You can configure a default source path substitution rule by
7256 configuring @value{GDBN} with the
7257 @samp{--with-relocated-sources=@var{dir}} option. The @var{dir}
7258 should be the name of a directory under @value{GDBN}'s configured
7259 prefix (set with @samp{--prefix} or @samp{--exec-prefix}), and
7260 directory names in debug information under @var{dir} will be adjusted
7261 automatically if the installed @value{GDBN} is moved to a new
7262 location. This is useful if @value{GDBN}, libraries or executables
7263 with debug information and corresponding source code are being moved
7267 @item directory @var{dirname} @dots{}
7268 @item dir @var{dirname} @dots{}
7269 Add directory @var{dirname} to the front of the source path. Several
7270 directory names may be given to this command, separated by @samp{:}
7271 (@samp{;} on MS-DOS and MS-Windows, where @samp{:} usually appears as
7272 part of absolute file names) or
7273 whitespace. You may specify a directory that is already in the source
7274 path; this moves it forward, so @value{GDBN} searches it sooner.
7278 @vindex $cdir@r{, convenience variable}
7279 @vindex $cwd@r{, convenience variable}
7280 @cindex compilation directory
7281 @cindex current directory
7282 @cindex working directory
7283 @cindex directory, current
7284 @cindex directory, compilation
7285 You can use the string @samp{$cdir} to refer to the compilation
7286 directory (if one is recorded), and @samp{$cwd} to refer to the current
7287 working directory. @samp{$cwd} is not the same as @samp{.}---the former
7288 tracks the current working directory as it changes during your @value{GDBN}
7289 session, while the latter is immediately expanded to the current
7290 directory at the time you add an entry to the source path.
7293 Reset the source path to its default value (@samp{$cdir:$cwd} on Unix systems). This requires confirmation.
7295 @c RET-repeat for @code{directory} is explicitly disabled, but since
7296 @c repeating it would be a no-op we do not say that. (thanks to RMS)
7298 @item set directories @var{path-list}
7299 @kindex set directories
7300 Set the source path to @var{path-list}.
7301 @samp{$cdir:$cwd} are added if missing.
7303 @item show directories
7304 @kindex show directories
7305 Print the source path: show which directories it contains.
7307 @anchor{set substitute-path}
7308 @item set substitute-path @var{from} @var{to}
7309 @kindex set substitute-path
7310 Define a source path substitution rule, and add it at the end of the
7311 current list of existing substitution rules. If a rule with the same
7312 @var{from} was already defined, then the old rule is also deleted.
7314 For example, if the file @file{/foo/bar/baz.c} was moved to
7315 @file{/mnt/cross/baz.c}, then the command
7318 (@value{GDBP}) set substitute-path /usr/src /mnt/cross
7322 will tell @value{GDBN} to replace @samp{/usr/src} with
7323 @samp{/mnt/cross}, which will allow @value{GDBN} to find the file
7324 @file{baz.c} even though it was moved.
7326 In the case when more than one substitution rule have been defined,
7327 the rules are evaluated one by one in the order where they have been
7328 defined. The first one matching, if any, is selected to perform
7331 For instance, if we had entered the following commands:
7334 (@value{GDBP}) set substitute-path /usr/src/include /mnt/include
7335 (@value{GDBP}) set substitute-path /usr/src /mnt/src
7339 @value{GDBN} would then rewrite @file{/usr/src/include/defs.h} into
7340 @file{/mnt/include/defs.h} by using the first rule. However, it would
7341 use the second rule to rewrite @file{/usr/src/lib/foo.c} into
7342 @file{/mnt/src/lib/foo.c}.
7345 @item unset substitute-path [path]
7346 @kindex unset substitute-path
7347 If a path is specified, search the current list of substitution rules
7348 for a rule that would rewrite that path. Delete that rule if found.
7349 A warning is emitted by the debugger if no rule could be found.
7351 If no path is specified, then all substitution rules are deleted.
7353 @item show substitute-path [path]
7354 @kindex show substitute-path
7355 If a path is specified, then print the source path substitution rule
7356 which would rewrite that path, if any.
7358 If no path is specified, then print all existing source path substitution
7363 If your source path is cluttered with directories that are no longer of
7364 interest, @value{GDBN} may sometimes cause confusion by finding the wrong
7365 versions of source. You can correct the situation as follows:
7369 Use @code{directory} with no argument to reset the source path to its default value.
7372 Use @code{directory} with suitable arguments to reinstall the
7373 directories you want in the source path. You can add all the
7374 directories in one command.
7378 @section Source and Machine Code
7379 @cindex source line and its code address
7381 You can use the command @code{info line} to map source lines to program
7382 addresses (and vice versa), and the command @code{disassemble} to display
7383 a range of addresses as machine instructions. You can use the command
7384 @code{set disassemble-next-line} to set whether to disassemble next
7385 source line when execution stops. When run under @sc{gnu} Emacs
7386 mode, the @code{info line} command causes the arrow to point to the
7387 line specified. Also, @code{info line} prints addresses in symbolic form as
7392 @item info line @var{linespec}
7393 Print the starting and ending addresses of the compiled code for
7394 source line @var{linespec}. You can specify source lines in any of
7395 the ways documented in @ref{Specify Location}.
7398 For example, we can use @code{info line} to discover the location of
7399 the object code for the first line of function
7400 @code{m4_changequote}:
7402 @c FIXME: I think this example should also show the addresses in
7403 @c symbolic form, as they usually would be displayed.
7405 (@value{GDBP}) info line m4_changequote
7406 Line 895 of "builtin.c" starts at pc 0x634c and ends at 0x6350.
7410 @cindex code address and its source line
7411 We can also inquire (using @code{*@var{addr}} as the form for
7412 @var{linespec}) what source line covers a particular address:
7414 (@value{GDBP}) info line *0x63ff
7415 Line 926 of "builtin.c" starts at pc 0x63e4 and ends at 0x6404.
7418 @cindex @code{$_} and @code{info line}
7419 @cindex @code{x} command, default address
7420 @kindex x@r{(examine), and} info line
7421 After @code{info line}, the default address for the @code{x} command
7422 is changed to the starting address of the line, so that @samp{x/i} is
7423 sufficient to begin examining the machine code (@pxref{Memory,
7424 ,Examining Memory}). Also, this address is saved as the value of the
7425 convenience variable @code{$_} (@pxref{Convenience Vars, ,Convenience
7430 @cindex assembly instructions
7431 @cindex instructions, assembly
7432 @cindex machine instructions
7433 @cindex listing machine instructions
7435 @itemx disassemble /m
7436 @itemx disassemble /r
7437 This specialized command dumps a range of memory as machine
7438 instructions. It can also print mixed source+disassembly by specifying
7439 the @code{/m} modifier and print the raw instructions in hex as well as
7440 in symbolic form by specifying the @code{/r}.
7441 The default memory range is the function surrounding the
7442 program counter of the selected frame. A single argument to this
7443 command is a program counter value; @value{GDBN} dumps the function
7444 surrounding this value. When two arguments are given, they should
7445 be separated by a comma, possibly surrounded by whitespace. The
7446 arguments specify a range of addresses to dump, in one of two forms:
7449 @item @var{start},@var{end}
7450 the addresses from @var{start} (inclusive) to @var{end} (exclusive)
7451 @item @var{start},+@var{length}
7452 the addresses from @var{start} (inclusive) to
7453 @code{@var{start}+@var{length}} (exclusive).
7457 When 2 arguments are specified, the name of the function is also
7458 printed (since there could be several functions in the given range).
7460 The argument(s) can be any expression yielding a numeric value, such as
7461 @samp{0x32c4}, @samp{&main+10} or @samp{$pc - 8}.
7463 If the range of memory being disassembled contains current program counter,
7464 the instruction at that location is shown with a @code{=>} marker.
7467 The following example shows the disassembly of a range of addresses of
7468 HP PA-RISC 2.0 code:
7471 (@value{GDBP}) disas 0x32c4, 0x32e4
7472 Dump of assembler code from 0x32c4 to 0x32e4:
7473 0x32c4 <main+204>: addil 0,dp
7474 0x32c8 <main+208>: ldw 0x22c(sr0,r1),r26
7475 0x32cc <main+212>: ldil 0x3000,r31
7476 0x32d0 <main+216>: ble 0x3f8(sr4,r31)
7477 0x32d4 <main+220>: ldo 0(r31),rp
7478 0x32d8 <main+224>: addil -0x800,dp
7479 0x32dc <main+228>: ldo 0x588(r1),r26
7480 0x32e0 <main+232>: ldil 0x3000,r31
7481 End of assembler dump.
7484 Here is an example showing mixed source+assembly for Intel x86, when the
7485 program is stopped just after function prologue:
7488 (@value{GDBP}) disas /m main
7489 Dump of assembler code for function main:
7491 0x08048330 <+0>: push %ebp
7492 0x08048331 <+1>: mov %esp,%ebp
7493 0x08048333 <+3>: sub $0x8,%esp
7494 0x08048336 <+6>: and $0xfffffff0,%esp
7495 0x08048339 <+9>: sub $0x10,%esp
7497 6 printf ("Hello.\n");
7498 => 0x0804833c <+12>: movl $0x8048440,(%esp)
7499 0x08048343 <+19>: call 0x8048284 <puts@@plt>
7503 0x08048348 <+24>: mov $0x0,%eax
7504 0x0804834d <+29>: leave
7505 0x0804834e <+30>: ret
7507 End of assembler dump.
7510 Here is another example showing raw instructions in hex for AMD x86-64,
7513 (gdb) disas /r 0x400281,+10
7514 Dump of assembler code from 0x400281 to 0x40028b:
7515 0x0000000000400281: 38 36 cmp %dh,(%rsi)
7516 0x0000000000400283: 2d 36 34 2e 73 sub $0x732e3436,%eax
7517 0x0000000000400288: 6f outsl %ds:(%rsi),(%dx)
7518 0x0000000000400289: 2e 32 00 xor %cs:(%rax),%al
7519 End of assembler dump.
7522 Addresses cannot be specified as a linespec (@pxref{Specify Location}).
7523 So, for example, if you want to disassemble function @code{bar}
7524 in file @file{foo.c}, you must type @samp{disassemble 'foo.c'::bar}
7525 and not @samp{disassemble foo.c:bar}.
7527 Some architectures have more than one commonly-used set of instruction
7528 mnemonics or other syntax.
7530 For programs that were dynamically linked and use shared libraries,
7531 instructions that call functions or branch to locations in the shared
7532 libraries might show a seemingly bogus location---it's actually a
7533 location of the relocation table. On some architectures, @value{GDBN}
7534 might be able to resolve these to actual function names.
7537 @kindex set disassembly-flavor
7538 @cindex Intel disassembly flavor
7539 @cindex AT&T disassembly flavor
7540 @item set disassembly-flavor @var{instruction-set}
7541 Select the instruction set to use when disassembling the
7542 program via the @code{disassemble} or @code{x/i} commands.
7544 Currently this command is only defined for the Intel x86 family. You
7545 can set @var{instruction-set} to either @code{intel} or @code{att}.
7546 The default is @code{att}, the AT&T flavor used by default by Unix
7547 assemblers for x86-based targets.
7549 @kindex show disassembly-flavor
7550 @item show disassembly-flavor
7551 Show the current setting of the disassembly flavor.
7555 @kindex set disassemble-next-line
7556 @kindex show disassemble-next-line
7557 @item set disassemble-next-line
7558 @itemx show disassemble-next-line
7559 Control whether or not @value{GDBN} will disassemble the next source
7560 line or instruction when execution stops. If ON, @value{GDBN} will
7561 display disassembly of the next source line when execution of the
7562 program being debugged stops. This is @emph{in addition} to
7563 displaying the source line itself, which @value{GDBN} always does if
7564 possible. If the next source line cannot be displayed for some reason
7565 (e.g., if @value{GDBN} cannot find the source file, or there's no line
7566 info in the debug info), @value{GDBN} will display disassembly of the
7567 next @emph{instruction} instead of showing the next source line. If
7568 AUTO, @value{GDBN} will display disassembly of next instruction only
7569 if the source line cannot be displayed. This setting causes
7570 @value{GDBN} to display some feedback when you step through a function
7571 with no line info or whose source file is unavailable. The default is
7572 OFF, which means never display the disassembly of the next line or
7578 @chapter Examining Data
7580 @cindex printing data
7581 @cindex examining data
7584 The usual way to examine data in your program is with the @code{print}
7585 command (abbreviated @code{p}), or its synonym @code{inspect}. It
7586 evaluates and prints the value of an expression of the language your
7587 program is written in (@pxref{Languages, ,Using @value{GDBN} with
7588 Different Languages}). It may also print the expression using a
7589 Python-based pretty-printer (@pxref{Pretty Printing}).
7592 @item print @var{expr}
7593 @itemx print /@var{f} @var{expr}
7594 @var{expr} is an expression (in the source language). By default the
7595 value of @var{expr} is printed in a format appropriate to its data type;
7596 you can choose a different format by specifying @samp{/@var{f}}, where
7597 @var{f} is a letter specifying the format; see @ref{Output Formats,,Output
7601 @itemx print /@var{f}
7602 @cindex reprint the last value
7603 If you omit @var{expr}, @value{GDBN} displays the last value again (from the
7604 @dfn{value history}; @pxref{Value History, ,Value History}). This allows you to
7605 conveniently inspect the same value in an alternative format.
7608 A more low-level way of examining data is with the @code{x} command.
7609 It examines data in memory at a specified address and prints it in a
7610 specified format. @xref{Memory, ,Examining Memory}.
7612 If you are interested in information about types, or about how the
7613 fields of a struct or a class are declared, use the @code{ptype @var{exp}}
7614 command rather than @code{print}. @xref{Symbols, ,Examining the Symbol
7617 @cindex exploring hierarchical data structures
7619 Another way of examining values of expressions and type information is
7620 through the Python extension command @code{explore} (available only if
7621 the @value{GDBN} build is configured with @code{--with-python}). It
7622 offers an interactive way to start at the highest level (or, the most
7623 abstract level) of the data type of an expression (or, the data type
7624 itself) and explore all the way down to leaf scalar values/fields
7625 embedded in the higher level data types.
7628 @item explore @var{arg}
7629 @var{arg} is either an expression (in the source language), or a type
7630 visible in the current context of the program being debugged.
7633 The working of the @code{explore} command can be illustrated with an
7634 example. If a data type @code{struct ComplexStruct} is defined in your
7644 struct ComplexStruct
7646 struct SimpleStruct *ss_p;
7652 followed by variable declarations as
7655 struct SimpleStruct ss = @{ 10, 1.11 @};
7656 struct ComplexStruct cs = @{ &ss, @{ 0, 1, 2, 3, 4, 5, 6, 7, 8, 9 @} @};
7660 then, the value of the variable @code{cs} can be explored using the
7661 @code{explore} command as follows.
7665 The value of `cs' is a struct/class of type `struct ComplexStruct' with
7666 the following fields:
7668 ss_p = <Enter 0 to explore this field of type `struct SimpleStruct *'>
7669 arr = <Enter 1 to explore this field of type `int [10]'>
7671 Enter the field number of choice:
7675 Since the fields of @code{cs} are not scalar values, you are being
7676 prompted to chose the field you want to explore. Let's say you choose
7677 the field @code{ss_p} by entering @code{0}. Then, since this field is a
7678 pointer, you will be asked if it is pointing to a single value. From
7679 the declaration of @code{cs} above, it is indeed pointing to a single
7680 value, hence you enter @code{y}. If you enter @code{n}, then you will
7681 be asked if it were pointing to an array of values, in which case this
7682 field will be explored as if it were an array.
7685 `cs.ss_p' is a pointer to a value of type `struct SimpleStruct'
7686 Continue exploring it as a pointer to a single value [y/n]: y
7687 The value of `*(cs.ss_p)' is a struct/class of type `struct
7688 SimpleStruct' with the following fields:
7690 i = 10 .. (Value of type `int')
7691 d = 1.1100000000000001 .. (Value of type `double')
7693 Press enter to return to parent value:
7697 If the field @code{arr} of @code{cs} was chosen for exploration by
7698 entering @code{1} earlier, then since it is as array, you will be
7699 prompted to enter the index of the element in the array that you want
7703 `cs.arr' is an array of `int'.
7704 Enter the index of the element you want to explore in `cs.arr': 5
7706 `(cs.arr)[5]' is a scalar value of type `int'.
7710 Press enter to return to parent value:
7713 In general, at any stage of exploration, you can go deeper towards the
7714 leaf values by responding to the prompts appropriately, or hit the
7715 return key to return to the enclosing data structure (the @i{higher}
7716 level data structure).
7718 Similar to exploring values, you can use the @code{explore} command to
7719 explore types. Instead of specifying a value (which is typically a
7720 variable name or an expression valid in the current context of the
7721 program being debugged), you specify a type name. If you consider the
7722 same example as above, your can explore the type
7723 @code{struct ComplexStruct} by passing the argument
7724 @code{struct ComplexStruct} to the @code{explore} command.
7727 (gdb) explore struct ComplexStruct
7731 By responding to the prompts appropriately in the subsequent interactive
7732 session, you can explore the type @code{struct ComplexStruct} in a
7733 manner similar to how the value @code{cs} was explored in the above
7736 The @code{explore} command also has two sub-commands,
7737 @code{explore value} and @code{explore type}. The former sub-command is
7738 a way to explicitly specify that value exploration of the argument is
7739 being invoked, while the latter is a way to explicitly specify that type
7740 exploration of the argument is being invoked.
7743 @item explore value @var{expr}
7744 @cindex explore value
7745 This sub-command of @code{explore} explores the value of the
7746 expression @var{expr} (if @var{expr} is an expression valid in the
7747 current context of the program being debugged). The behavior of this
7748 command is identical to that of the behavior of the @code{explore}
7749 command being passed the argument @var{expr}.
7751 @item explore type @var{arg}
7752 @cindex explore type
7753 This sub-command of @code{explore} explores the type of @var{arg} (if
7754 @var{arg} is a type visible in the current context of program being
7755 debugged), or the type of the value/expression @var{arg} (if @var{arg}
7756 is an expression valid in the current context of the program being
7757 debugged). If @var{arg} is a type, then the behavior of this command is
7758 identical to that of the @code{explore} command being passed the
7759 argument @var{arg}. If @var{arg} is an expression, then the behavior of
7760 this command will be identical to that of the @code{explore} command
7761 being passed the type of @var{arg} as the argument.
7765 * Expressions:: Expressions
7766 * Ambiguous Expressions:: Ambiguous Expressions
7767 * Variables:: Program variables
7768 * Arrays:: Artificial arrays
7769 * Output Formats:: Output formats
7770 * Memory:: Examining memory
7771 * Auto Display:: Automatic display
7772 * Print Settings:: Print settings
7773 * Pretty Printing:: Python pretty printing
7774 * Value History:: Value history
7775 * Convenience Vars:: Convenience variables
7776 * Convenience Funs:: Convenience functions
7777 * Registers:: Registers
7778 * Floating Point Hardware:: Floating point hardware
7779 * Vector Unit:: Vector Unit
7780 * OS Information:: Auxiliary data provided by operating system
7781 * Memory Region Attributes:: Memory region attributes
7782 * Dump/Restore Files:: Copy between memory and a file
7783 * Core File Generation:: Cause a program dump its core
7784 * Character Sets:: Debugging programs that use a different
7785 character set than GDB does
7786 * Caching Remote Data:: Data caching for remote targets
7787 * Searching Memory:: Searching memory for a sequence of bytes
7791 @section Expressions
7794 @code{print} and many other @value{GDBN} commands accept an expression and
7795 compute its value. Any kind of constant, variable or operator defined
7796 by the programming language you are using is valid in an expression in
7797 @value{GDBN}. This includes conditional expressions, function calls,
7798 casts, and string constants. It also includes preprocessor macros, if
7799 you compiled your program to include this information; see
7802 @cindex arrays in expressions
7803 @value{GDBN} supports array constants in expressions input by
7804 the user. The syntax is @{@var{element}, @var{element}@dots{}@}. For example,
7805 you can use the command @code{print @{1, 2, 3@}} to create an array
7806 of three integers. If you pass an array to a function or assign it
7807 to a program variable, @value{GDBN} copies the array to memory that
7808 is @code{malloc}ed in the target program.
7810 Because C is so widespread, most of the expressions shown in examples in
7811 this manual are in C. @xref{Languages, , Using @value{GDBN} with Different
7812 Languages}, for information on how to use expressions in other
7815 In this section, we discuss operators that you can use in @value{GDBN}
7816 expressions regardless of your programming language.
7818 @cindex casts, in expressions
7819 Casts are supported in all languages, not just in C, because it is so
7820 useful to cast a number into a pointer in order to examine a structure
7821 at that address in memory.
7822 @c FIXME: casts supported---Mod2 true?
7824 @value{GDBN} supports these operators, in addition to those common
7825 to programming languages:
7829 @samp{@@} is a binary operator for treating parts of memory as arrays.
7830 @xref{Arrays, ,Artificial Arrays}, for more information.
7833 @samp{::} allows you to specify a variable in terms of the file or
7834 function where it is defined. @xref{Variables, ,Program Variables}.
7836 @cindex @{@var{type}@}
7837 @cindex type casting memory
7838 @cindex memory, viewing as typed object
7839 @cindex casts, to view memory
7840 @item @{@var{type}@} @var{addr}
7841 Refers to an object of type @var{type} stored at address @var{addr} in
7842 memory. @var{addr} may be any expression whose value is an integer or
7843 pointer (but parentheses are required around binary operators, just as in
7844 a cast). This construct is allowed regardless of what kind of data is
7845 normally supposed to reside at @var{addr}.
7848 @node Ambiguous Expressions
7849 @section Ambiguous Expressions
7850 @cindex ambiguous expressions
7852 Expressions can sometimes contain some ambiguous elements. For instance,
7853 some programming languages (notably Ada, C@t{++} and Objective-C) permit
7854 a single function name to be defined several times, for application in
7855 different contexts. This is called @dfn{overloading}. Another example
7856 involving Ada is generics. A @dfn{generic package} is similar to C@t{++}
7857 templates and is typically instantiated several times, resulting in
7858 the same function name being defined in different contexts.
7860 In some cases and depending on the language, it is possible to adjust
7861 the expression to remove the ambiguity. For instance in C@t{++}, you
7862 can specify the signature of the function you want to break on, as in
7863 @kbd{break @var{function}(@var{types})}. In Ada, using the fully
7864 qualified name of your function often makes the expression unambiguous
7867 When an ambiguity that needs to be resolved is detected, the debugger
7868 has the capability to display a menu of numbered choices for each
7869 possibility, and then waits for the selection with the prompt @samp{>}.
7870 The first option is always @samp{[0] cancel}, and typing @kbd{0 @key{RET}}
7871 aborts the current command. If the command in which the expression was
7872 used allows more than one choice to be selected, the next option in the
7873 menu is @samp{[1] all}, and typing @kbd{1 @key{RET}} selects all possible
7876 For example, the following session excerpt shows an attempt to set a
7877 breakpoint at the overloaded symbol @code{String::after}.
7878 We choose three particular definitions of that function name:
7880 @c FIXME! This is likely to change to show arg type lists, at least
7883 (@value{GDBP}) b String::after
7886 [2] file:String.cc; line number:867
7887 [3] file:String.cc; line number:860
7888 [4] file:String.cc; line number:875
7889 [5] file:String.cc; line number:853
7890 [6] file:String.cc; line number:846
7891 [7] file:String.cc; line number:735
7893 Breakpoint 1 at 0xb26c: file String.cc, line 867.
7894 Breakpoint 2 at 0xb344: file String.cc, line 875.
7895 Breakpoint 3 at 0xafcc: file String.cc, line 846.
7896 Multiple breakpoints were set.
7897 Use the "delete" command to delete unwanted
7904 @kindex set multiple-symbols
7905 @item set multiple-symbols @var{mode}
7906 @cindex multiple-symbols menu
7908 This option allows you to adjust the debugger behavior when an expression
7911 By default, @var{mode} is set to @code{all}. If the command with which
7912 the expression is used allows more than one choice, then @value{GDBN}
7913 automatically selects all possible choices. For instance, inserting
7914 a breakpoint on a function using an ambiguous name results in a breakpoint
7915 inserted on each possible match. However, if a unique choice must be made,
7916 then @value{GDBN} uses the menu to help you disambiguate the expression.
7917 For instance, printing the address of an overloaded function will result
7918 in the use of the menu.
7920 When @var{mode} is set to @code{ask}, the debugger always uses the menu
7921 when an ambiguity is detected.
7923 Finally, when @var{mode} is set to @code{cancel}, the debugger reports
7924 an error due to the ambiguity and the command is aborted.
7926 @kindex show multiple-symbols
7927 @item show multiple-symbols
7928 Show the current value of the @code{multiple-symbols} setting.
7932 @section Program Variables
7934 The most common kind of expression to use is the name of a variable
7937 Variables in expressions are understood in the selected stack frame
7938 (@pxref{Selection, ,Selecting a Frame}); they must be either:
7942 global (or file-static)
7949 visible according to the scope rules of the
7950 programming language from the point of execution in that frame
7953 @noindent This means that in the function
7968 you can examine and use the variable @code{a} whenever your program is
7969 executing within the function @code{foo}, but you can only use or
7970 examine the variable @code{b} while your program is executing inside
7971 the block where @code{b} is declared.
7973 @cindex variable name conflict
7974 There is an exception: you can refer to a variable or function whose
7975 scope is a single source file even if the current execution point is not
7976 in this file. But it is possible to have more than one such variable or
7977 function with the same name (in different source files). If that
7978 happens, referring to that name has unpredictable effects. If you wish,
7979 you can specify a static variable in a particular function or file by
7980 using the colon-colon (@code{::}) notation:
7982 @cindex colon-colon, context for variables/functions
7984 @c info cannot cope with a :: index entry, but why deprive hard copy readers?
7985 @cindex @code{::}, context for variables/functions
7988 @var{file}::@var{variable}
7989 @var{function}::@var{variable}
7993 Here @var{file} or @var{function} is the name of the context for the
7994 static @var{variable}. In the case of file names, you can use quotes to
7995 make sure @value{GDBN} parses the file name as a single word---for example,
7996 to print a global value of @code{x} defined in @file{f2.c}:
7999 (@value{GDBP}) p 'f2.c'::x
8002 The @code{::} notation is normally used for referring to
8003 static variables, since you typically disambiguate uses of local variables
8004 in functions by selecting the appropriate frame and using the
8005 simple name of the variable. However, you may also use this notation
8006 to refer to local variables in frames enclosing the selected frame:
8015 process (a); /* Stop here */
8026 For example, if there is a breakpoint at the commented line,
8027 here is what you might see
8028 when the program stops after executing the call @code{bar(0)}:
8033 (@value{GDBP}) p bar::a
8036 #2 0x080483d0 in foo (a=5) at foobar.c:12
8039 (@value{GDBP}) p bar::a
8043 @cindex C@t{++} scope resolution
8044 These uses of @samp{::} are very rarely in conflict with the very similar
8045 use of the same notation in C@t{++}. @value{GDBN} also supports use of the C@t{++}
8046 scope resolution operator in @value{GDBN} expressions.
8047 @c FIXME: Um, so what happens in one of those rare cases where it's in
8050 @cindex wrong values
8051 @cindex variable values, wrong
8052 @cindex function entry/exit, wrong values of variables
8053 @cindex optimized code, wrong values of variables
8055 @emph{Warning:} Occasionally, a local variable may appear to have the
8056 wrong value at certain points in a function---just after entry to a new
8057 scope, and just before exit.
8059 You may see this problem when you are stepping by machine instructions.
8060 This is because, on most machines, it takes more than one instruction to
8061 set up a stack frame (including local variable definitions); if you are
8062 stepping by machine instructions, variables may appear to have the wrong
8063 values until the stack frame is completely built. On exit, it usually
8064 also takes more than one machine instruction to destroy a stack frame;
8065 after you begin stepping through that group of instructions, local
8066 variable definitions may be gone.
8068 This may also happen when the compiler does significant optimizations.
8069 To be sure of always seeing accurate values, turn off all optimization
8072 @cindex ``No symbol "foo" in current context''
8073 Another possible effect of compiler optimizations is to optimize
8074 unused variables out of existence, or assign variables to registers (as
8075 opposed to memory addresses). Depending on the support for such cases
8076 offered by the debug info format used by the compiler, @value{GDBN}
8077 might not be able to display values for such local variables. If that
8078 happens, @value{GDBN} will print a message like this:
8081 No symbol "foo" in current context.
8084 To solve such problems, either recompile without optimizations, or use a
8085 different debug info format, if the compiler supports several such
8086 formats. @xref{Compilation}, for more information on choosing compiler
8087 options. @xref{C, ,C and C@t{++}}, for more information about debug
8088 info formats that are best suited to C@t{++} programs.
8090 If you ask to print an object whose contents are unknown to
8091 @value{GDBN}, e.g., because its data type is not completely specified
8092 by the debug information, @value{GDBN} will say @samp{<incomplete
8093 type>}. @xref{Symbols, incomplete type}, for more about this.
8095 If you append @kbd{@@entry} string to a function parameter name you get its
8096 value at the time the function got called. If the value is not available an
8097 error message is printed. Entry values are available only with some compilers.
8098 Entry values are normally also printed at the function parameter list according
8099 to @ref{set print entry-values}.
8102 Breakpoint 1, d (i=30) at gdb.base/entry-value.c:29
8108 (gdb) print i@@entry
8112 Strings are identified as arrays of @code{char} values without specified
8113 signedness. Arrays of either @code{signed char} or @code{unsigned char} get
8114 printed as arrays of 1 byte sized integers. @code{-fsigned-char} or
8115 @code{-funsigned-char} @value{NGCC} options have no effect as @value{GDBN}
8116 defines literal string type @code{"char"} as @code{char} without a sign.
8121 signed char var1[] = "A";
8124 You get during debugging
8129 $2 = @{65 'A', 0 '\0'@}
8133 @section Artificial Arrays
8135 @cindex artificial array
8137 @kindex @@@r{, referencing memory as an array}
8138 It is often useful to print out several successive objects of the
8139 same type in memory; a section of an array, or an array of
8140 dynamically determined size for which only a pointer exists in the
8143 You can do this by referring to a contiguous span of memory as an
8144 @dfn{artificial array}, using the binary operator @samp{@@}. The left
8145 operand of @samp{@@} should be the first element of the desired array
8146 and be an individual object. The right operand should be the desired length
8147 of the array. The result is an array value whose elements are all of
8148 the type of the left argument. The first element is actually the left
8149 argument; the second element comes from bytes of memory immediately
8150 following those that hold the first element, and so on. Here is an
8151 example. If a program says
8154 int *array = (int *) malloc (len * sizeof (int));
8158 you can print the contents of @code{array} with
8164 The left operand of @samp{@@} must reside in memory. Array values made
8165 with @samp{@@} in this way behave just like other arrays in terms of
8166 subscripting, and are coerced to pointers when used in expressions.
8167 Artificial arrays most often appear in expressions via the value history
8168 (@pxref{Value History, ,Value History}), after printing one out.
8170 Another way to create an artificial array is to use a cast.
8171 This re-interprets a value as if it were an array.
8172 The value need not be in memory:
8174 (@value{GDBP}) p/x (short[2])0x12345678
8175 $1 = @{0x1234, 0x5678@}
8178 As a convenience, if you leave the array length out (as in
8179 @samp{(@var{type}[])@var{value}}) @value{GDBN} calculates the size to fill
8180 the value (as @samp{sizeof(@var{value})/sizeof(@var{type})}:
8182 (@value{GDBP}) p/x (short[])0x12345678
8183 $2 = @{0x1234, 0x5678@}
8186 Sometimes the artificial array mechanism is not quite enough; in
8187 moderately complex data structures, the elements of interest may not
8188 actually be adjacent---for example, if you are interested in the values
8189 of pointers in an array. One useful work-around in this situation is
8190 to use a convenience variable (@pxref{Convenience Vars, ,Convenience
8191 Variables}) as a counter in an expression that prints the first
8192 interesting value, and then repeat that expression via @key{RET}. For
8193 instance, suppose you have an array @code{dtab} of pointers to
8194 structures, and you are interested in the values of a field @code{fv}
8195 in each structure. Here is an example of what you might type:
8205 @node Output Formats
8206 @section Output Formats
8208 @cindex formatted output
8209 @cindex output formats
8210 By default, @value{GDBN} prints a value according to its data type. Sometimes
8211 this is not what you want. For example, you might want to print a number
8212 in hex, or a pointer in decimal. Or you might want to view data in memory
8213 at a certain address as a character string or as an instruction. To do
8214 these things, specify an @dfn{output format} when you print a value.
8216 The simplest use of output formats is to say how to print a value
8217 already computed. This is done by starting the arguments of the
8218 @code{print} command with a slash and a format letter. The format
8219 letters supported are:
8223 Regard the bits of the value as an integer, and print the integer in
8227 Print as integer in signed decimal.
8230 Print as integer in unsigned decimal.
8233 Print as integer in octal.
8236 Print as integer in binary. The letter @samp{t} stands for ``two''.
8237 @footnote{@samp{b} cannot be used because these format letters are also
8238 used with the @code{x} command, where @samp{b} stands for ``byte'';
8239 see @ref{Memory,,Examining Memory}.}
8242 @cindex unknown address, locating
8243 @cindex locate address
8244 Print as an address, both absolute in hexadecimal and as an offset from
8245 the nearest preceding symbol. You can use this format used to discover
8246 where (in what function) an unknown address is located:
8249 (@value{GDBP}) p/a 0x54320
8250 $3 = 0x54320 <_initialize_vx+396>
8254 The command @code{info symbol 0x54320} yields similar results.
8255 @xref{Symbols, info symbol}.
8258 Regard as an integer and print it as a character constant. This
8259 prints both the numerical value and its character representation. The
8260 character representation is replaced with the octal escape @samp{\nnn}
8261 for characters outside the 7-bit @sc{ascii} range.
8263 Without this format, @value{GDBN} displays @code{char},
8264 @w{@code{unsigned char}}, and @w{@code{signed char}} data as character
8265 constants. Single-byte members of vectors are displayed as integer
8269 Regard the bits of the value as a floating point number and print
8270 using typical floating point syntax.
8273 @cindex printing strings
8274 @cindex printing byte arrays
8275 Regard as a string, if possible. With this format, pointers to single-byte
8276 data are displayed as null-terminated strings and arrays of single-byte data
8277 are displayed as fixed-length strings. Other values are displayed in their
8280 Without this format, @value{GDBN} displays pointers to and arrays of
8281 @code{char}, @w{@code{unsigned char}}, and @w{@code{signed char}} as
8282 strings. Single-byte members of a vector are displayed as an integer
8286 @cindex raw printing
8287 Print using the @samp{raw} formatting. By default, @value{GDBN} will
8288 use a Python-based pretty-printer, if one is available (@pxref{Pretty
8289 Printing}). This typically results in a higher-level display of the
8290 value's contents. The @samp{r} format bypasses any Python
8291 pretty-printer which might exist.
8294 For example, to print the program counter in hex (@pxref{Registers}), type
8301 Note that no space is required before the slash; this is because command
8302 names in @value{GDBN} cannot contain a slash.
8304 To reprint the last value in the value history with a different format,
8305 you can use the @code{print} command with just a format and no
8306 expression. For example, @samp{p/x} reprints the last value in hex.
8309 @section Examining Memory
8311 You can use the command @code{x} (for ``examine'') to examine memory in
8312 any of several formats, independently of your program's data types.
8314 @cindex examining memory
8316 @kindex x @r{(examine memory)}
8317 @item x/@var{nfu} @var{addr}
8320 Use the @code{x} command to examine memory.
8323 @var{n}, @var{f}, and @var{u} are all optional parameters that specify how
8324 much memory to display and how to format it; @var{addr} is an
8325 expression giving the address where you want to start displaying memory.
8326 If you use defaults for @var{nfu}, you need not type the slash @samp{/}.
8327 Several commands set convenient defaults for @var{addr}.
8330 @item @var{n}, the repeat count
8331 The repeat count is a decimal integer; the default is 1. It specifies
8332 how much memory (counting by units @var{u}) to display.
8333 @c This really is **decimal**; unaffected by 'set radix' as of GDB
8336 @item @var{f}, the display format
8337 The display format is one of the formats used by @code{print}
8338 (@samp{x}, @samp{d}, @samp{u}, @samp{o}, @samp{t}, @samp{a}, @samp{c},
8339 @samp{f}, @samp{s}), and in addition @samp{i} (for machine instructions).
8340 The default is @samp{x} (hexadecimal) initially. The default changes
8341 each time you use either @code{x} or @code{print}.
8343 @item @var{u}, the unit size
8344 The unit size is any of
8350 Halfwords (two bytes).
8352 Words (four bytes). This is the initial default.
8354 Giant words (eight bytes).
8357 Each time you specify a unit size with @code{x}, that size becomes the
8358 default unit the next time you use @code{x}. For the @samp{i} format,
8359 the unit size is ignored and is normally not written. For the @samp{s} format,
8360 the unit size defaults to @samp{b}, unless it is explicitly given.
8361 Use @kbd{x /hs} to display 16-bit char strings and @kbd{x /ws} to display
8362 32-bit strings. The next use of @kbd{x /s} will again display 8-bit strings.
8363 Note that the results depend on the programming language of the
8364 current compilation unit. If the language is C, the @samp{s}
8365 modifier will use the UTF-16 encoding while @samp{w} will use
8366 UTF-32. The encoding is set by the programming language and cannot
8369 @item @var{addr}, starting display address
8370 @var{addr} is the address where you want @value{GDBN} to begin displaying
8371 memory. The expression need not have a pointer value (though it may);
8372 it is always interpreted as an integer address of a byte of memory.
8373 @xref{Expressions, ,Expressions}, for more information on expressions. The default for
8374 @var{addr} is usually just after the last address examined---but several
8375 other commands also set the default address: @code{info breakpoints} (to
8376 the address of the last breakpoint listed), @code{info line} (to the
8377 starting address of a line), and @code{print} (if you use it to display
8378 a value from memory).
8381 For example, @samp{x/3uh 0x54320} is a request to display three halfwords
8382 (@code{h}) of memory, formatted as unsigned decimal integers (@samp{u}),
8383 starting at address @code{0x54320}. @samp{x/4xw $sp} prints the four
8384 words (@samp{w}) of memory above the stack pointer (here, @samp{$sp};
8385 @pxref{Registers, ,Registers}) in hexadecimal (@samp{x}).
8387 Since the letters indicating unit sizes are all distinct from the
8388 letters specifying output formats, you do not have to remember whether
8389 unit size or format comes first; either order works. The output
8390 specifications @samp{4xw} and @samp{4wx} mean exactly the same thing.
8391 (However, the count @var{n} must come first; @samp{wx4} does not work.)
8393 Even though the unit size @var{u} is ignored for the formats @samp{s}
8394 and @samp{i}, you might still want to use a count @var{n}; for example,
8395 @samp{3i} specifies that you want to see three machine instructions,
8396 including any operands. For convenience, especially when used with
8397 the @code{display} command, the @samp{i} format also prints branch delay
8398 slot instructions, if any, beyond the count specified, which immediately
8399 follow the last instruction that is within the count. The command
8400 @code{disassemble} gives an alternative way of inspecting machine
8401 instructions; see @ref{Machine Code,,Source and Machine Code}.
8403 All the defaults for the arguments to @code{x} are designed to make it
8404 easy to continue scanning memory with minimal specifications each time
8405 you use @code{x}. For example, after you have inspected three machine
8406 instructions with @samp{x/3i @var{addr}}, you can inspect the next seven
8407 with just @samp{x/7}. If you use @key{RET} to repeat the @code{x} command,
8408 the repeat count @var{n} is used again; the other arguments default as
8409 for successive uses of @code{x}.
8411 When examining machine instructions, the instruction at current program
8412 counter is shown with a @code{=>} marker. For example:
8415 (@value{GDBP}) x/5i $pc-6
8416 0x804837f <main+11>: mov %esp,%ebp
8417 0x8048381 <main+13>: push %ecx
8418 0x8048382 <main+14>: sub $0x4,%esp
8419 => 0x8048385 <main+17>: movl $0x8048460,(%esp)
8420 0x804838c <main+24>: call 0x80482d4 <puts@@plt>
8423 @cindex @code{$_}, @code{$__}, and value history
8424 The addresses and contents printed by the @code{x} command are not saved
8425 in the value history because there is often too much of them and they
8426 would get in the way. Instead, @value{GDBN} makes these values available for
8427 subsequent use in expressions as values of the convenience variables
8428 @code{$_} and @code{$__}. After an @code{x} command, the last address
8429 examined is available for use in expressions in the convenience variable
8430 @code{$_}. The contents of that address, as examined, are available in
8431 the convenience variable @code{$__}.
8433 If the @code{x} command has a repeat count, the address and contents saved
8434 are from the last memory unit printed; this is not the same as the last
8435 address printed if several units were printed on the last line of output.
8437 @cindex remote memory comparison
8438 @cindex verify remote memory image
8439 When you are debugging a program running on a remote target machine
8440 (@pxref{Remote Debugging}), you may wish to verify the program's image in the
8441 remote machine's memory against the executable file you downloaded to
8442 the target. The @code{compare-sections} command is provided for such
8446 @kindex compare-sections
8447 @item compare-sections @r{[}@var{section-name}@r{]}
8448 Compare the data of a loadable section @var{section-name} in the
8449 executable file of the program being debugged with the same section in
8450 the remote machine's memory, and report any mismatches. With no
8451 arguments, compares all loadable sections. This command's
8452 availability depends on the target's support for the @code{"qCRC"}
8457 @section Automatic Display
8458 @cindex automatic display
8459 @cindex display of expressions
8461 If you find that you want to print the value of an expression frequently
8462 (to see how it changes), you might want to add it to the @dfn{automatic
8463 display list} so that @value{GDBN} prints its value each time your program stops.
8464 Each expression added to the list is given a number to identify it;
8465 to remove an expression from the list, you specify that number.
8466 The automatic display looks like this:
8470 3: bar[5] = (struct hack *) 0x3804
8474 This display shows item numbers, expressions and their current values. As with
8475 displays you request manually using @code{x} or @code{print}, you can
8476 specify the output format you prefer; in fact, @code{display} decides
8477 whether to use @code{print} or @code{x} depending your format
8478 specification---it uses @code{x} if you specify either the @samp{i}
8479 or @samp{s} format, or a unit size; otherwise it uses @code{print}.
8483 @item display @var{expr}
8484 Add the expression @var{expr} to the list of expressions to display
8485 each time your program stops. @xref{Expressions, ,Expressions}.
8487 @code{display} does not repeat if you press @key{RET} again after using it.
8489 @item display/@var{fmt} @var{expr}
8490 For @var{fmt} specifying only a display format and not a size or
8491 count, add the expression @var{expr} to the auto-display list but
8492 arrange to display it each time in the specified format @var{fmt}.
8493 @xref{Output Formats,,Output Formats}.
8495 @item display/@var{fmt} @var{addr}
8496 For @var{fmt} @samp{i} or @samp{s}, or including a unit-size or a
8497 number of units, add the expression @var{addr} as a memory address to
8498 be examined each time your program stops. Examining means in effect
8499 doing @samp{x/@var{fmt} @var{addr}}. @xref{Memory, ,Examining Memory}.
8502 For example, @samp{display/i $pc} can be helpful, to see the machine
8503 instruction about to be executed each time execution stops (@samp{$pc}
8504 is a common name for the program counter; @pxref{Registers, ,Registers}).
8507 @kindex delete display
8509 @item undisplay @var{dnums}@dots{}
8510 @itemx delete display @var{dnums}@dots{}
8511 Remove items from the list of expressions to display. Specify the
8512 numbers of the displays that you want affected with the command
8513 argument @var{dnums}. It can be a single display number, one of the
8514 numbers shown in the first field of the @samp{info display} display;
8515 or it could be a range of display numbers, as in @code{2-4}.
8517 @code{undisplay} does not repeat if you press @key{RET} after using it.
8518 (Otherwise you would just get the error @samp{No display number @dots{}}.)
8520 @kindex disable display
8521 @item disable display @var{dnums}@dots{}
8522 Disable the display of item numbers @var{dnums}. A disabled display
8523 item is not printed automatically, but is not forgotten. It may be
8524 enabled again later. Specify the numbers of the displays that you
8525 want affected with the command argument @var{dnums}. It can be a
8526 single display number, one of the numbers shown in the first field of
8527 the @samp{info display} display; or it could be a range of display
8528 numbers, as in @code{2-4}.
8530 @kindex enable display
8531 @item enable display @var{dnums}@dots{}
8532 Enable display of item numbers @var{dnums}. It becomes effective once
8533 again in auto display of its expression, until you specify otherwise.
8534 Specify the numbers of the displays that you want affected with the
8535 command argument @var{dnums}. It can be a single display number, one
8536 of the numbers shown in the first field of the @samp{info display}
8537 display; or it could be a range of display numbers, as in @code{2-4}.
8540 Display the current values of the expressions on the list, just as is
8541 done when your program stops.
8543 @kindex info display
8545 Print the list of expressions previously set up to display
8546 automatically, each one with its item number, but without showing the
8547 values. This includes disabled expressions, which are marked as such.
8548 It also includes expressions which would not be displayed right now
8549 because they refer to automatic variables not currently available.
8552 @cindex display disabled out of scope
8553 If a display expression refers to local variables, then it does not make
8554 sense outside the lexical context for which it was set up. Such an
8555 expression is disabled when execution enters a context where one of its
8556 variables is not defined. For example, if you give the command
8557 @code{display last_char} while inside a function with an argument
8558 @code{last_char}, @value{GDBN} displays this argument while your program
8559 continues to stop inside that function. When it stops elsewhere---where
8560 there is no variable @code{last_char}---the display is disabled
8561 automatically. The next time your program stops where @code{last_char}
8562 is meaningful, you can enable the display expression once again.
8564 @node Print Settings
8565 @section Print Settings
8567 @cindex format options
8568 @cindex print settings
8569 @value{GDBN} provides the following ways to control how arrays, structures,
8570 and symbols are printed.
8573 These settings are useful for debugging programs in any language:
8577 @item set print address
8578 @itemx set print address on
8579 @cindex print/don't print memory addresses
8580 @value{GDBN} prints memory addresses showing the location of stack
8581 traces, structure values, pointer values, breakpoints, and so forth,
8582 even when it also displays the contents of those addresses. The default
8583 is @code{on}. For example, this is what a stack frame display looks like with
8584 @code{set print address on}:
8589 #0 set_quotes (lq=0x34c78 "<<", rq=0x34c88 ">>")
8591 530 if (lquote != def_lquote)
8595 @item set print address off
8596 Do not print addresses when displaying their contents. For example,
8597 this is the same stack frame displayed with @code{set print address off}:
8601 (@value{GDBP}) set print addr off
8603 #0 set_quotes (lq="<<", rq=">>") at input.c:530
8604 530 if (lquote != def_lquote)
8608 You can use @samp{set print address off} to eliminate all machine
8609 dependent displays from the @value{GDBN} interface. For example, with
8610 @code{print address off}, you should get the same text for backtraces on
8611 all machines---whether or not they involve pointer arguments.
8614 @item show print address
8615 Show whether or not addresses are to be printed.
8618 When @value{GDBN} prints a symbolic address, it normally prints the
8619 closest earlier symbol plus an offset. If that symbol does not uniquely
8620 identify the address (for example, it is a name whose scope is a single
8621 source file), you may need to clarify. One way to do this is with
8622 @code{info line}, for example @samp{info line *0x4537}. Alternately,
8623 you can set @value{GDBN} to print the source file and line number when
8624 it prints a symbolic address:
8627 @item set print symbol-filename on
8628 @cindex source file and line of a symbol
8629 @cindex symbol, source file and line
8630 Tell @value{GDBN} to print the source file name and line number of a
8631 symbol in the symbolic form of an address.
8633 @item set print symbol-filename off
8634 Do not print source file name and line number of a symbol. This is the
8637 @item show print symbol-filename
8638 Show whether or not @value{GDBN} will print the source file name and
8639 line number of a symbol in the symbolic form of an address.
8642 Another situation where it is helpful to show symbol filenames and line
8643 numbers is when disassembling code; @value{GDBN} shows you the line
8644 number and source file that corresponds to each instruction.
8646 Also, you may wish to see the symbolic form only if the address being
8647 printed is reasonably close to the closest earlier symbol:
8650 @item set print max-symbolic-offset @var{max-offset}
8651 @cindex maximum value for offset of closest symbol
8652 Tell @value{GDBN} to only display the symbolic form of an address if the
8653 offset between the closest earlier symbol and the address is less than
8654 @var{max-offset}. The default is 0, which tells @value{GDBN}
8655 to always print the symbolic form of an address if any symbol precedes it.
8657 @item show print max-symbolic-offset
8658 Ask how large the maximum offset is that @value{GDBN} prints in a
8662 @cindex wild pointer, interpreting
8663 @cindex pointer, finding referent
8664 If you have a pointer and you are not sure where it points, try
8665 @samp{set print symbol-filename on}. Then you can determine the name
8666 and source file location of the variable where it points, using
8667 @samp{p/a @var{pointer}}. This interprets the address in symbolic form.
8668 For example, here @value{GDBN} shows that a variable @code{ptt} points
8669 at another variable @code{t}, defined in @file{hi2.c}:
8672 (@value{GDBP}) set print symbol-filename on
8673 (@value{GDBP}) p/a ptt
8674 $4 = 0xe008 <t in hi2.c>
8678 @emph{Warning:} For pointers that point to a local variable, @samp{p/a}
8679 does not show the symbol name and filename of the referent, even with
8680 the appropriate @code{set print} options turned on.
8683 You can also enable @samp{/a}-like formatting all the time using
8684 @samp{set print symbol on}:
8687 @item set print symbol on
8688 Tell @value{GDBN} to print the symbol corresponding to an address, if
8691 @item set print symbol off
8692 Tell @value{GDBN} not to print the symbol corresponding to an
8693 address. In this mode, @value{GDBN} will still print the symbol
8694 corresponding to pointers to functions. This is the default.
8696 @item show print symbol
8697 Show whether @value{GDBN} will display the symbol corresponding to an
8701 Other settings control how different kinds of objects are printed:
8704 @item set print array
8705 @itemx set print array on
8706 @cindex pretty print arrays
8707 Pretty print arrays. This format is more convenient to read,
8708 but uses more space. The default is off.
8710 @item set print array off
8711 Return to compressed format for arrays.
8713 @item show print array
8714 Show whether compressed or pretty format is selected for displaying
8717 @cindex print array indexes
8718 @item set print array-indexes
8719 @itemx set print array-indexes on
8720 Print the index of each element when displaying arrays. May be more
8721 convenient to locate a given element in the array or quickly find the
8722 index of a given element in that printed array. The default is off.
8724 @item set print array-indexes off
8725 Stop printing element indexes when displaying arrays.
8727 @item show print array-indexes
8728 Show whether the index of each element is printed when displaying
8731 @item set print elements @var{number-of-elements}
8732 @cindex number of array elements to print
8733 @cindex limit on number of printed array elements
8734 Set a limit on how many elements of an array @value{GDBN} will print.
8735 If @value{GDBN} is printing a large array, it stops printing after it has
8736 printed the number of elements set by the @code{set print elements} command.
8737 This limit also applies to the display of strings.
8738 When @value{GDBN} starts, this limit is set to 200.
8739 Setting @var{number-of-elements} to zero means that the printing is unlimited.
8741 @item show print elements
8742 Display the number of elements of a large array that @value{GDBN} will print.
8743 If the number is 0, then the printing is unlimited.
8745 @item set print frame-arguments @var{value}
8746 @kindex set print frame-arguments
8747 @cindex printing frame argument values
8748 @cindex print all frame argument values
8749 @cindex print frame argument values for scalars only
8750 @cindex do not print frame argument values
8751 This command allows to control how the values of arguments are printed
8752 when the debugger prints a frame (@pxref{Frames}). The possible
8757 The values of all arguments are printed.
8760 Print the value of an argument only if it is a scalar. The value of more
8761 complex arguments such as arrays, structures, unions, etc, is replaced
8762 by @code{@dots{}}. This is the default. Here is an example where
8763 only scalar arguments are shown:
8766 #1 0x08048361 in call_me (i=3, s=@dots{}, ss=0xbf8d508c, u=@dots{}, e=green)
8771 None of the argument values are printed. Instead, the value of each argument
8772 is replaced by @code{@dots{}}. In this case, the example above now becomes:
8775 #1 0x08048361 in call_me (i=@dots{}, s=@dots{}, ss=@dots{}, u=@dots{}, e=@dots{})
8780 By default, only scalar arguments are printed. This command can be used
8781 to configure the debugger to print the value of all arguments, regardless
8782 of their type. However, it is often advantageous to not print the value
8783 of more complex parameters. For instance, it reduces the amount of
8784 information printed in each frame, making the backtrace more readable.
8785 Also, it improves performance when displaying Ada frames, because
8786 the computation of large arguments can sometimes be CPU-intensive,
8787 especially in large applications. Setting @code{print frame-arguments}
8788 to @code{scalars} (the default) or @code{none} avoids this computation,
8789 thus speeding up the display of each Ada frame.
8791 @item show print frame-arguments
8792 Show how the value of arguments should be displayed when printing a frame.
8794 @anchor{set print entry-values}
8795 @item set print entry-values @var{value}
8796 @kindex set print entry-values
8797 Set printing of frame argument values at function entry. In some cases
8798 @value{GDBN} can determine the value of function argument which was passed by
8799 the function caller, even if the value was modified inside the called function
8800 and therefore is different. With optimized code, the current value could be
8801 unavailable, but the entry value may still be known.
8803 The default value is @code{default} (see below for its description). Older
8804 @value{GDBN} behaved as with the setting @code{no}. Compilers not supporting
8805 this feature will behave in the @code{default} setting the same way as with the
8808 This functionality is currently supported only by DWARF 2 debugging format and
8809 the compiler has to produce @samp{DW_TAG_GNU_call_site} tags. With
8810 @value{NGCC}, you need to specify @option{-O -g} during compilation, to get
8813 The @var{value} parameter can be one of the following:
8817 Print only actual parameter values, never print values from function entry
8821 #0 different (val=6)
8822 #0 lost (val=<optimized out>)
8824 #0 invalid (val=<optimized out>)
8828 Print only parameter values from function entry point. The actual parameter
8829 values are never printed.
8831 #0 equal (val@@entry=5)
8832 #0 different (val@@entry=5)
8833 #0 lost (val@@entry=5)
8834 #0 born (val@@entry=<optimized out>)
8835 #0 invalid (val@@entry=<optimized out>)
8839 Print only parameter values from function entry point. If value from function
8840 entry point is not known while the actual value is known, print the actual
8841 value for such parameter.
8843 #0 equal (val@@entry=5)
8844 #0 different (val@@entry=5)
8845 #0 lost (val@@entry=5)
8847 #0 invalid (val@@entry=<optimized out>)
8851 Print actual parameter values. If actual parameter value is not known while
8852 value from function entry point is known, print the entry point value for such
8856 #0 different (val=6)
8857 #0 lost (val@@entry=5)
8859 #0 invalid (val=<optimized out>)
8863 Always print both the actual parameter value and its value from function entry
8864 point, even if values of one or both are not available due to compiler
8867 #0 equal (val=5, val@@entry=5)
8868 #0 different (val=6, val@@entry=5)
8869 #0 lost (val=<optimized out>, val@@entry=5)
8870 #0 born (val=10, val@@entry=<optimized out>)
8871 #0 invalid (val=<optimized out>, val@@entry=<optimized out>)
8875 Print the actual parameter value if it is known and also its value from
8876 function entry point if it is known. If neither is known, print for the actual
8877 value @code{<optimized out>}. If not in MI mode (@pxref{GDB/MI}) and if both
8878 values are known and identical, print the shortened
8879 @code{param=param@@entry=VALUE} notation.
8881 #0 equal (val=val@@entry=5)
8882 #0 different (val=6, val@@entry=5)
8883 #0 lost (val@@entry=5)
8885 #0 invalid (val=<optimized out>)
8889 Always print the actual parameter value. Print also its value from function
8890 entry point, but only if it is known. If not in MI mode (@pxref{GDB/MI}) and
8891 if both values are known and identical, print the shortened
8892 @code{param=param@@entry=VALUE} notation.
8894 #0 equal (val=val@@entry=5)
8895 #0 different (val=6, val@@entry=5)
8896 #0 lost (val=<optimized out>, val@@entry=5)
8898 #0 invalid (val=<optimized out>)
8902 For analysis messages on possible failures of frame argument values at function
8903 entry resolution see @ref{set debug entry-values}.
8905 @item show print entry-values
8906 Show the method being used for printing of frame argument values at function
8909 @item set print repeats
8910 @cindex repeated array elements
8911 Set the threshold for suppressing display of repeated array
8912 elements. When the number of consecutive identical elements of an
8913 array exceeds the threshold, @value{GDBN} prints the string
8914 @code{"<repeats @var{n} times>"}, where @var{n} is the number of
8915 identical repetitions, instead of displaying the identical elements
8916 themselves. Setting the threshold to zero will cause all elements to
8917 be individually printed. The default threshold is 10.
8919 @item show print repeats
8920 Display the current threshold for printing repeated identical
8923 @item set print null-stop
8924 @cindex @sc{null} elements in arrays
8925 Cause @value{GDBN} to stop printing the characters of an array when the first
8926 @sc{null} is encountered. This is useful when large arrays actually
8927 contain only short strings.
8930 @item show print null-stop
8931 Show whether @value{GDBN} stops printing an array on the first
8932 @sc{null} character.
8934 @item set print pretty on
8935 @cindex print structures in indented form
8936 @cindex indentation in structure display
8937 Cause @value{GDBN} to print structures in an indented format with one member
8938 per line, like this:
8953 @item set print pretty off
8954 Cause @value{GDBN} to print structures in a compact format, like this:
8958 $1 = @{next = 0x0, flags = @{sweet = 1, sour = 1@}, \
8959 meat = 0x54 "Pork"@}
8964 This is the default format.
8966 @item show print pretty
8967 Show which format @value{GDBN} is using to print structures.
8969 @item set print sevenbit-strings on
8970 @cindex eight-bit characters in strings
8971 @cindex octal escapes in strings
8972 Print using only seven-bit characters; if this option is set,
8973 @value{GDBN} displays any eight-bit characters (in strings or
8974 character values) using the notation @code{\}@var{nnn}. This setting is
8975 best if you are working in English (@sc{ascii}) and you use the
8976 high-order bit of characters as a marker or ``meta'' bit.
8978 @item set print sevenbit-strings off
8979 Print full eight-bit characters. This allows the use of more
8980 international character sets, and is the default.
8982 @item show print sevenbit-strings
8983 Show whether or not @value{GDBN} is printing only seven-bit characters.
8985 @item set print union on
8986 @cindex unions in structures, printing
8987 Tell @value{GDBN} to print unions which are contained in structures
8988 and other unions. This is the default setting.
8990 @item set print union off
8991 Tell @value{GDBN} not to print unions which are contained in
8992 structures and other unions. @value{GDBN} will print @code{"@{...@}"}
8995 @item show print union
8996 Ask @value{GDBN} whether or not it will print unions which are contained in
8997 structures and other unions.
8999 For example, given the declarations
9002 typedef enum @{Tree, Bug@} Species;
9003 typedef enum @{Big_tree, Acorn, Seedling@} Tree_forms;
9004 typedef enum @{Caterpillar, Cocoon, Butterfly@}
9015 struct thing foo = @{Tree, @{Acorn@}@};
9019 with @code{set print union on} in effect @samp{p foo} would print
9022 $1 = @{it = Tree, form = @{tree = Acorn, bug = Cocoon@}@}
9026 and with @code{set print union off} in effect it would print
9029 $1 = @{it = Tree, form = @{...@}@}
9033 @code{set print union} affects programs written in C-like languages
9039 These settings are of interest when debugging C@t{++} programs:
9042 @cindex demangling C@t{++} names
9043 @item set print demangle
9044 @itemx set print demangle on
9045 Print C@t{++} names in their source form rather than in the encoded
9046 (``mangled'') form passed to the assembler and linker for type-safe
9047 linkage. The default is on.
9049 @item show print demangle
9050 Show whether C@t{++} names are printed in mangled or demangled form.
9052 @item set print asm-demangle
9053 @itemx set print asm-demangle on
9054 Print C@t{++} names in their source form rather than their mangled form, even
9055 in assembler code printouts such as instruction disassemblies.
9058 @item show print asm-demangle
9059 Show whether C@t{++} names in assembly listings are printed in mangled
9062 @cindex C@t{++} symbol decoding style
9063 @cindex symbol decoding style, C@t{++}
9064 @kindex set demangle-style
9065 @item set demangle-style @var{style}
9066 Choose among several encoding schemes used by different compilers to
9067 represent C@t{++} names. The choices for @var{style} are currently:
9071 Allow @value{GDBN} to choose a decoding style by inspecting your program.
9072 This is the default.
9075 Decode based on the @sc{gnu} C@t{++} compiler (@code{g++}) encoding algorithm.
9078 Decode based on the HP ANSI C@t{++} (@code{aCC}) encoding algorithm.
9081 Decode based on the Lucid C@t{++} compiler (@code{lcc}) encoding algorithm.
9084 Decode using the algorithm in the @cite{C@t{++} Annotated Reference Manual}.
9085 @strong{Warning:} this setting alone is not sufficient to allow
9086 debugging @code{cfront}-generated executables. @value{GDBN} would
9087 require further enhancement to permit that.
9090 If you omit @var{style}, you will see a list of possible formats.
9092 @item show demangle-style
9093 Display the encoding style currently in use for decoding C@t{++} symbols.
9095 @item set print object
9096 @itemx set print object on
9097 @cindex derived type of an object, printing
9098 @cindex display derived types
9099 When displaying a pointer to an object, identify the @emph{actual}
9100 (derived) type of the object rather than the @emph{declared} type, using
9101 the virtual function table. Note that the virtual function table is
9102 required---this feature can only work for objects that have run-time
9103 type identification; a single virtual method in the object's declared
9104 type is sufficient. Note that this setting is also taken into account when
9105 working with variable objects via MI (@pxref{GDB/MI}).
9107 @item set print object off
9108 Display only the declared type of objects, without reference to the
9109 virtual function table. This is the default setting.
9111 @item show print object
9112 Show whether actual, or declared, object types are displayed.
9114 @item set print static-members
9115 @itemx set print static-members on
9116 @cindex static members of C@t{++} objects
9117 Print static members when displaying a C@t{++} object. The default is on.
9119 @item set print static-members off
9120 Do not print static members when displaying a C@t{++} object.
9122 @item show print static-members
9123 Show whether C@t{++} static members are printed or not.
9125 @item set print pascal_static-members
9126 @itemx set print pascal_static-members on
9127 @cindex static members of Pascal objects
9128 @cindex Pascal objects, static members display
9129 Print static members when displaying a Pascal object. The default is on.
9131 @item set print pascal_static-members off
9132 Do not print static members when displaying a Pascal object.
9134 @item show print pascal_static-members
9135 Show whether Pascal static members are printed or not.
9137 @c These don't work with HP ANSI C++ yet.
9138 @item set print vtbl
9139 @itemx set print vtbl on
9140 @cindex pretty print C@t{++} virtual function tables
9141 @cindex virtual functions (C@t{++}) display
9142 @cindex VTBL display
9143 Pretty print C@t{++} virtual function tables. The default is off.
9144 (The @code{vtbl} commands do not work on programs compiled with the HP
9145 ANSI C@t{++} compiler (@code{aCC}).)
9147 @item set print vtbl off
9148 Do not pretty print C@t{++} virtual function tables.
9150 @item show print vtbl
9151 Show whether C@t{++} virtual function tables are pretty printed, or not.
9154 @node Pretty Printing
9155 @section Pretty Printing
9157 @value{GDBN} provides a mechanism to allow pretty-printing of values using
9158 Python code. It greatly simplifies the display of complex objects. This
9159 mechanism works for both MI and the CLI.
9162 * Pretty-Printer Introduction:: Introduction to pretty-printers
9163 * Pretty-Printer Example:: An example pretty-printer
9164 * Pretty-Printer Commands:: Pretty-printer commands
9167 @node Pretty-Printer Introduction
9168 @subsection Pretty-Printer Introduction
9170 When @value{GDBN} prints a value, it first sees if there is a pretty-printer
9171 registered for the value. If there is then @value{GDBN} invokes the
9172 pretty-printer to print the value. Otherwise the value is printed normally.
9174 Pretty-printers are normally named. This makes them easy to manage.
9175 The @samp{info pretty-printer} command will list all the installed
9176 pretty-printers with their names.
9177 If a pretty-printer can handle multiple data types, then its
9178 @dfn{subprinters} are the printers for the individual data types.
9179 Each such subprinter has its own name.
9180 The format of the name is @var{printer-name};@var{subprinter-name}.
9182 Pretty-printers are installed by @dfn{registering} them with @value{GDBN}.
9183 Typically they are automatically loaded and registered when the corresponding
9184 debug information is loaded, thus making them available without having to
9185 do anything special.
9187 There are three places where a pretty-printer can be registered.
9191 Pretty-printers registered globally are available when debugging
9195 Pretty-printers registered with a program space are available only
9196 when debugging that program.
9197 @xref{Progspaces In Python}, for more details on program spaces in Python.
9200 Pretty-printers registered with an objfile are loaded and unloaded
9201 with the corresponding objfile (e.g., shared library).
9202 @xref{Objfiles In Python}, for more details on objfiles in Python.
9205 @xref{Selecting Pretty-Printers}, for further information on how
9206 pretty-printers are selected,
9208 @xref{Writing a Pretty-Printer}, for implementing pretty printers
9211 @node Pretty-Printer Example
9212 @subsection Pretty-Printer Example
9214 Here is how a C@t{++} @code{std::string} looks without a pretty-printer:
9217 (@value{GDBP}) print s
9219 static npos = 4294967295,
9221 <std::allocator<char>> = @{
9222 <__gnu_cxx::new_allocator<char>> = @{
9223 <No data fields>@}, <No data fields>
9225 members of std::basic_string<char, std::char_traits<char>,
9226 std::allocator<char> >::_Alloc_hider:
9227 _M_p = 0x804a014 "abcd"
9232 With a pretty-printer for @code{std::string} only the contents are printed:
9235 (@value{GDBP}) print s
9239 @node Pretty-Printer Commands
9240 @subsection Pretty-Printer Commands
9241 @cindex pretty-printer commands
9244 @kindex info pretty-printer
9245 @item info pretty-printer [@var{object-regexp} [@var{name-regexp}]]
9246 Print the list of installed pretty-printers.
9247 This includes disabled pretty-printers, which are marked as such.
9249 @var{object-regexp} is a regular expression matching the objects
9250 whose pretty-printers to list.
9251 Objects can be @code{global}, the program space's file
9252 (@pxref{Progspaces In Python}),
9253 and the object files within that program space (@pxref{Objfiles In Python}).
9254 @xref{Selecting Pretty-Printers}, for details on how @value{GDBN}
9255 looks up a printer from these three objects.
9257 @var{name-regexp} is a regular expression matching the name of the printers
9260 @kindex disable pretty-printer
9261 @item disable pretty-printer [@var{object-regexp} [@var{name-regexp}]]
9262 Disable pretty-printers matching @var{object-regexp} and @var{name-regexp}.
9263 A disabled pretty-printer is not forgotten, it may be enabled again later.
9265 @kindex enable pretty-printer
9266 @item enable pretty-printer [@var{object-regexp} [@var{name-regexp}]]
9267 Enable pretty-printers matching @var{object-regexp} and @var{name-regexp}.
9272 Suppose we have three pretty-printers installed: one from library1.so
9273 named @code{foo} that prints objects of type @code{foo}, and
9274 another from library2.so named @code{bar} that prints two types of objects,
9275 @code{bar1} and @code{bar2}.
9278 (gdb) info pretty-printer
9285 (gdb) info pretty-printer library2
9290 (gdb) disable pretty-printer library1
9292 2 of 3 printers enabled
9293 (gdb) info pretty-printer
9300 (gdb) disable pretty-printer library2 bar:bar1
9302 1 of 3 printers enabled
9303 (gdb) info pretty-printer library2
9310 (gdb) disable pretty-printer library2 bar
9312 0 of 3 printers enabled
9313 (gdb) info pretty-printer library2
9322 Note that for @code{bar} the entire printer can be disabled,
9323 as can each individual subprinter.
9326 @section Value History
9328 @cindex value history
9329 @cindex history of values printed by @value{GDBN}
9330 Values printed by the @code{print} command are saved in the @value{GDBN}
9331 @dfn{value history}. This allows you to refer to them in other expressions.
9332 Values are kept until the symbol table is re-read or discarded
9333 (for example with the @code{file} or @code{symbol-file} commands).
9334 When the symbol table changes, the value history is discarded,
9335 since the values may contain pointers back to the types defined in the
9340 @cindex history number
9341 The values printed are given @dfn{history numbers} by which you can
9342 refer to them. These are successive integers starting with one.
9343 @code{print} shows you the history number assigned to a value by
9344 printing @samp{$@var{num} = } before the value; here @var{num} is the
9347 To refer to any previous value, use @samp{$} followed by the value's
9348 history number. The way @code{print} labels its output is designed to
9349 remind you of this. Just @code{$} refers to the most recent value in
9350 the history, and @code{$$} refers to the value before that.
9351 @code{$$@var{n}} refers to the @var{n}th value from the end; @code{$$2}
9352 is the value just prior to @code{$$}, @code{$$1} is equivalent to
9353 @code{$$}, and @code{$$0} is equivalent to @code{$}.
9355 For example, suppose you have just printed a pointer to a structure and
9356 want to see the contents of the structure. It suffices to type
9362 If you have a chain of structures where the component @code{next} points
9363 to the next one, you can print the contents of the next one with this:
9370 You can print successive links in the chain by repeating this
9371 command---which you can do by just typing @key{RET}.
9373 Note that the history records values, not expressions. If the value of
9374 @code{x} is 4 and you type these commands:
9382 then the value recorded in the value history by the @code{print} command
9383 remains 4 even though the value of @code{x} has changed.
9388 Print the last ten values in the value history, with their item numbers.
9389 This is like @samp{p@ $$9} repeated ten times, except that @code{show
9390 values} does not change the history.
9392 @item show values @var{n}
9393 Print ten history values centered on history item number @var{n}.
9396 Print ten history values just after the values last printed. If no more
9397 values are available, @code{show values +} produces no display.
9400 Pressing @key{RET} to repeat @code{show values @var{n}} has exactly the
9401 same effect as @samp{show values +}.
9403 @node Convenience Vars
9404 @section Convenience Variables
9406 @cindex convenience variables
9407 @cindex user-defined variables
9408 @value{GDBN} provides @dfn{convenience variables} that you can use within
9409 @value{GDBN} to hold on to a value and refer to it later. These variables
9410 exist entirely within @value{GDBN}; they are not part of your program, and
9411 setting a convenience variable has no direct effect on further execution
9412 of your program. That is why you can use them freely.
9414 Convenience variables are prefixed with @samp{$}. Any name preceded by
9415 @samp{$} can be used for a convenience variable, unless it is one of
9416 the predefined machine-specific register names (@pxref{Registers, ,Registers}).
9417 (Value history references, in contrast, are @emph{numbers} preceded
9418 by @samp{$}. @xref{Value History, ,Value History}.)
9420 You can save a value in a convenience variable with an assignment
9421 expression, just as you would set a variable in your program.
9425 set $foo = *object_ptr
9429 would save in @code{$foo} the value contained in the object pointed to by
9432 Using a convenience variable for the first time creates it, but its
9433 value is @code{void} until you assign a new value. You can alter the
9434 value with another assignment at any time.
9436 Convenience variables have no fixed types. You can assign a convenience
9437 variable any type of value, including structures and arrays, even if
9438 that variable already has a value of a different type. The convenience
9439 variable, when used as an expression, has the type of its current value.
9442 @kindex show convenience
9443 @cindex show all user variables and functions
9444 @item show convenience
9445 Print a list of convenience variables used so far, and their values,
9446 as well as a list of the convenience functions.
9447 Abbreviated @code{show conv}.
9449 @kindex init-if-undefined
9450 @cindex convenience variables, initializing
9451 @item init-if-undefined $@var{variable} = @var{expression}
9452 Set a convenience variable if it has not already been set. This is useful
9453 for user-defined commands that keep some state. It is similar, in concept,
9454 to using local static variables with initializers in C (except that
9455 convenience variables are global). It can also be used to allow users to
9456 override default values used in a command script.
9458 If the variable is already defined then the expression is not evaluated so
9459 any side-effects do not occur.
9462 One of the ways to use a convenience variable is as a counter to be
9463 incremented or a pointer to be advanced. For example, to print
9464 a field from successive elements of an array of structures:
9468 print bar[$i++]->contents
9472 Repeat that command by typing @key{RET}.
9474 Some convenience variables are created automatically by @value{GDBN} and given
9475 values likely to be useful.
9478 @vindex $_@r{, convenience variable}
9480 The variable @code{$_} is automatically set by the @code{x} command to
9481 the last address examined (@pxref{Memory, ,Examining Memory}). Other
9482 commands which provide a default address for @code{x} to examine also
9483 set @code{$_} to that address; these commands include @code{info line}
9484 and @code{info breakpoint}. The type of @code{$_} is @code{void *}
9485 except when set by the @code{x} command, in which case it is a pointer
9486 to the type of @code{$__}.
9488 @vindex $__@r{, convenience variable}
9490 The variable @code{$__} is automatically set by the @code{x} command
9491 to the value found in the last address examined. Its type is chosen
9492 to match the format in which the data was printed.
9495 @vindex $_exitcode@r{, convenience variable}
9496 The variable @code{$_exitcode} is automatically set to the exit code when
9497 the program being debugged terminates.
9500 @itemx $_probe_arg0@dots{}$_probe_arg11
9501 Arguments to a static probe. @xref{Static Probe Points}.
9504 @vindex $_sdata@r{, inspect, convenience variable}
9505 The variable @code{$_sdata} contains extra collected static tracepoint
9506 data. @xref{Tracepoint Actions,,Tracepoint Action Lists}. Note that
9507 @code{$_sdata} could be empty, if not inspecting a trace buffer, or
9508 if extra static tracepoint data has not been collected.
9511 @vindex $_siginfo@r{, convenience variable}
9512 The variable @code{$_siginfo} contains extra signal information
9513 (@pxref{extra signal information}). Note that @code{$_siginfo}
9514 could be empty, if the application has not yet received any signals.
9515 For example, it will be empty before you execute the @code{run} command.
9518 @vindex $_tlb@r{, convenience variable}
9519 The variable @code{$_tlb} is automatically set when debugging
9520 applications running on MS-Windows in native mode or connected to
9521 gdbserver that supports the @code{qGetTIBAddr} request.
9522 @xref{General Query Packets}.
9523 This variable contains the address of the thread information block.
9527 On HP-UX systems, if you refer to a function or variable name that
9528 begins with a dollar sign, @value{GDBN} searches for a user or system
9529 name first, before it searches for a convenience variable.
9531 @node Convenience Funs
9532 @section Convenience Functions
9534 @cindex convenience functions
9535 @value{GDBN} also supplies some @dfn{convenience functions}. These
9536 have a syntax similar to convenience variables. A convenience
9537 function can be used in an expression just like an ordinary function;
9538 however, a convenience function is implemented internally to
9541 These functions require @value{GDBN} to be configured with
9542 @code{Python} support.
9546 @item $_memeq(@var{buf1}, @var{buf2}, @var{length})
9547 @findex $_memeq@r{, convenience function}
9548 Returns one if the @var{length} bytes at the addresses given by
9549 @var{buf1} and @var{buf2} are equal.
9550 Otherwise it returns zero.
9552 @item $_regex(@var{str}, @var{regex})
9553 @findex $_regex@r{, convenience function}
9554 Returns one if the string @var{str} matches the regular expression
9555 @var{regex}. Otherwise it returns zero.
9556 The syntax of the regular expression is that specified by @code{Python}'s
9557 regular expression support.
9559 @item $_streq(@var{str1}, @var{str2})
9560 @findex $_streq@r{, convenience function}
9561 Returns one if the strings @var{str1} and @var{str2} are equal.
9562 Otherwise it returns zero.
9564 @item $_strlen(@var{str})
9565 @findex $_strlen@r{, convenience function}
9566 Returns the length of string @var{str}.
9570 @value{GDBN} provides the ability to list and get help on
9571 convenience functions.
9575 @kindex help function
9576 @cindex show all convenience functions
9577 Print a list of all convenience functions.
9584 You can refer to machine register contents, in expressions, as variables
9585 with names starting with @samp{$}. The names of registers are different
9586 for each machine; use @code{info registers} to see the names used on
9590 @kindex info registers
9591 @item info registers
9592 Print the names and values of all registers except floating-point
9593 and vector registers (in the selected stack frame).
9595 @kindex info all-registers
9596 @cindex floating point registers
9597 @item info all-registers
9598 Print the names and values of all registers, including floating-point
9599 and vector registers (in the selected stack frame).
9601 @item info registers @var{regname} @dots{}
9602 Print the @dfn{relativized} value of each specified register @var{regname}.
9603 As discussed in detail below, register values are normally relative to
9604 the selected stack frame. @var{regname} may be any register name valid on
9605 the machine you are using, with or without the initial @samp{$}.
9608 @cindex stack pointer register
9609 @cindex program counter register
9610 @cindex process status register
9611 @cindex frame pointer register
9612 @cindex standard registers
9613 @value{GDBN} has four ``standard'' register names that are available (in
9614 expressions) on most machines---whenever they do not conflict with an
9615 architecture's canonical mnemonics for registers. The register names
9616 @code{$pc} and @code{$sp} are used for the program counter register and
9617 the stack pointer. @code{$fp} is used for a register that contains a
9618 pointer to the current stack frame, and @code{$ps} is used for a
9619 register that contains the processor status. For example,
9620 you could print the program counter in hex with
9627 or print the instruction to be executed next with
9634 or add four to the stack pointer@footnote{This is a way of removing
9635 one word from the stack, on machines where stacks grow downward in
9636 memory (most machines, nowadays). This assumes that the innermost
9637 stack frame is selected; setting @code{$sp} is not allowed when other
9638 stack frames are selected. To pop entire frames off the stack,
9639 regardless of machine architecture, use @code{return};
9640 see @ref{Returning, ,Returning from a Function}.} with
9646 Whenever possible, these four standard register names are available on
9647 your machine even though the machine has different canonical mnemonics,
9648 so long as there is no conflict. The @code{info registers} command
9649 shows the canonical names. For example, on the SPARC, @code{info
9650 registers} displays the processor status register as @code{$psr} but you
9651 can also refer to it as @code{$ps}; and on x86-based machines @code{$ps}
9652 is an alias for the @sc{eflags} register.
9654 @value{GDBN} always considers the contents of an ordinary register as an
9655 integer when the register is examined in this way. Some machines have
9656 special registers which can hold nothing but floating point; these
9657 registers are considered to have floating point values. There is no way
9658 to refer to the contents of an ordinary register as floating point value
9659 (although you can @emph{print} it as a floating point value with
9660 @samp{print/f $@var{regname}}).
9662 Some registers have distinct ``raw'' and ``virtual'' data formats. This
9663 means that the data format in which the register contents are saved by
9664 the operating system is not the same one that your program normally
9665 sees. For example, the registers of the 68881 floating point
9666 coprocessor are always saved in ``extended'' (raw) format, but all C
9667 programs expect to work with ``double'' (virtual) format. In such
9668 cases, @value{GDBN} normally works with the virtual format only (the format
9669 that makes sense for your program), but the @code{info registers} command
9670 prints the data in both formats.
9672 @cindex SSE registers (x86)
9673 @cindex MMX registers (x86)
9674 Some machines have special registers whose contents can be interpreted
9675 in several different ways. For example, modern x86-based machines
9676 have SSE and MMX registers that can hold several values packed
9677 together in several different formats. @value{GDBN} refers to such
9678 registers in @code{struct} notation:
9681 (@value{GDBP}) print $xmm1
9683 v4_float = @{0, 3.43859137e-038, 1.54142831e-044, 1.821688e-044@},
9684 v2_double = @{9.92129282474342e-303, 2.7585945287983262e-313@},
9685 v16_int8 = "\000\000\000\000\3706;\001\v\000\000\000\r\000\000",
9686 v8_int16 = @{0, 0, 14072, 315, 11, 0, 13, 0@},
9687 v4_int32 = @{0, 20657912, 11, 13@},
9688 v2_int64 = @{88725056443645952, 55834574859@},
9689 uint128 = 0x0000000d0000000b013b36f800000000
9694 To set values of such registers, you need to tell @value{GDBN} which
9695 view of the register you wish to change, as if you were assigning
9696 value to a @code{struct} member:
9699 (@value{GDBP}) set $xmm1.uint128 = 0x000000000000000000000000FFFFFFFF
9702 Normally, register values are relative to the selected stack frame
9703 (@pxref{Selection, ,Selecting a Frame}). This means that you get the
9704 value that the register would contain if all stack frames farther in
9705 were exited and their saved registers restored. In order to see the
9706 true contents of hardware registers, you must select the innermost
9707 frame (with @samp{frame 0}).
9709 However, @value{GDBN} must deduce where registers are saved, from the machine
9710 code generated by your compiler. If some registers are not saved, or if
9711 @value{GDBN} is unable to locate the saved registers, the selected stack
9712 frame makes no difference.
9714 @node Floating Point Hardware
9715 @section Floating Point Hardware
9716 @cindex floating point
9718 Depending on the configuration, @value{GDBN} may be able to give
9719 you more information about the status of the floating point hardware.
9724 Display hardware-dependent information about the floating
9725 point unit. The exact contents and layout vary depending on the
9726 floating point chip. Currently, @samp{info float} is supported on
9727 the ARM and x86 machines.
9731 @section Vector Unit
9734 Depending on the configuration, @value{GDBN} may be able to give you
9735 more information about the status of the vector unit.
9740 Display information about the vector unit. The exact contents and
9741 layout vary depending on the hardware.
9744 @node OS Information
9745 @section Operating System Auxiliary Information
9746 @cindex OS information
9748 @value{GDBN} provides interfaces to useful OS facilities that can help
9749 you debug your program.
9751 @cindex auxiliary vector
9752 @cindex vector, auxiliary
9753 Some operating systems supply an @dfn{auxiliary vector} to programs at
9754 startup. This is akin to the arguments and environment that you
9755 specify for a program, but contains a system-dependent variety of
9756 binary values that tell system libraries important details about the
9757 hardware, operating system, and process. Each value's purpose is
9758 identified by an integer tag; the meanings are well-known but system-specific.
9759 Depending on the configuration and operating system facilities,
9760 @value{GDBN} may be able to show you this information. For remote
9761 targets, this functionality may further depend on the remote stub's
9762 support of the @samp{qXfer:auxv:read} packet, see
9763 @ref{qXfer auxiliary vector read}.
9768 Display the auxiliary vector of the inferior, which can be either a
9769 live process or a core dump file. @value{GDBN} prints each tag value
9770 numerically, and also shows names and text descriptions for recognized
9771 tags. Some values in the vector are numbers, some bit masks, and some
9772 pointers to strings or other data. @value{GDBN} displays each value in the
9773 most appropriate form for a recognized tag, and in hexadecimal for
9774 an unrecognized tag.
9777 On some targets, @value{GDBN} can access operating system-specific
9778 information and show it to you. The types of information available
9779 will differ depending on the type of operating system running on the
9780 target. The mechanism used to fetch the data is described in
9781 @ref{Operating System Information}. For remote targets, this
9782 functionality depends on the remote stub's support of the
9783 @samp{qXfer:osdata:read} packet, see @ref{qXfer osdata read}.
9787 @item info os @var{infotype}
9789 Display OS information of the requested type.
9791 On @sc{gnu}/Linux, the following values of @var{infotype} are valid:
9793 @anchor{linux info os infotypes}
9795 @kindex info os processes
9797 Display the list of processes on the target. For each process,
9798 @value{GDBN} prints the process identifier, the name of the user, the
9799 command corresponding to the process, and the list of processor cores
9800 that the process is currently running on. (To understand what these
9801 properties mean, for this and the following info types, please consult
9802 the general @sc{gnu}/Linux documentation.)
9804 @kindex info os procgroups
9806 Display the list of process groups on the target. For each process,
9807 @value{GDBN} prints the identifier of the process group that it belongs
9808 to, the command corresponding to the process group leader, the process
9809 identifier, and the command line of the process. The list is sorted
9810 first by the process group identifier, then by the process identifier,
9811 so that processes belonging to the same process group are grouped together
9812 and the process group leader is listed first.
9814 @kindex info os threads
9816 Display the list of threads running on the target. For each thread,
9817 @value{GDBN} prints the identifier of the process that the thread
9818 belongs to, the command of the process, the thread identifier, and the
9819 processor core that it is currently running on. The main thread of a
9820 process is not listed.
9822 @kindex info os files
9824 Display the list of open file descriptors on the target. For each
9825 file descriptor, @value{GDBN} prints the identifier of the process
9826 owning the descriptor, the command of the owning process, the value
9827 of the descriptor, and the target of the descriptor.
9829 @kindex info os sockets
9831 Display the list of Internet-domain sockets on the target. For each
9832 socket, @value{GDBN} prints the address and port of the local and
9833 remote endpoints, the current state of the connection, the creator of
9834 the socket, the IP address family of the socket, and the type of the
9839 Display the list of all System V shared-memory regions on the target.
9840 For each shared-memory region, @value{GDBN} prints the region key,
9841 the shared-memory identifier, the access permissions, the size of the
9842 region, the process that created the region, the process that last
9843 attached to or detached from the region, the current number of live
9844 attaches to the region, and the times at which the region was last
9845 attached to, detach from, and changed.
9847 @kindex info os semaphores
9849 Display the list of all System V semaphore sets on the target. For each
9850 semaphore set, @value{GDBN} prints the semaphore set key, the semaphore
9851 set identifier, the access permissions, the number of semaphores in the
9852 set, the user and group of the owner and creator of the semaphore set,
9853 and the times at which the semaphore set was operated upon and changed.
9857 Display the list of all System V message queues on the target. For each
9858 message queue, @value{GDBN} prints the message queue key, the message
9859 queue identifier, the access permissions, the current number of bytes
9860 on the queue, the current number of messages on the queue, the processes
9861 that last sent and received a message on the queue, the user and group
9862 of the owner and creator of the message queue, the times at which a
9863 message was last sent and received on the queue, and the time at which
9864 the message queue was last changed.
9866 @kindex info os modules
9868 Display the list of all loaded kernel modules on the target. For each
9869 module, @value{GDBN} prints the module name, the size of the module in
9870 bytes, the number of times the module is used, the dependencies of the
9871 module, the status of the module, and the address of the loaded module
9876 If @var{infotype} is omitted, then list the possible values for
9877 @var{infotype} and the kind of OS information available for each
9878 @var{infotype}. If the target does not return a list of possible
9879 types, this command will report an error.
9882 @node Memory Region Attributes
9883 @section Memory Region Attributes
9884 @cindex memory region attributes
9886 @dfn{Memory region attributes} allow you to describe special handling
9887 required by regions of your target's memory. @value{GDBN} uses
9888 attributes to determine whether to allow certain types of memory
9889 accesses; whether to use specific width accesses; and whether to cache
9890 target memory. By default the description of memory regions is
9891 fetched from the target (if the current target supports this), but the
9892 user can override the fetched regions.
9894 Defined memory regions can be individually enabled and disabled. When a
9895 memory region is disabled, @value{GDBN} uses the default attributes when
9896 accessing memory in that region. Similarly, if no memory regions have
9897 been defined, @value{GDBN} uses the default attributes when accessing
9900 When a memory region is defined, it is given a number to identify it;
9901 to enable, disable, or remove a memory region, you specify that number.
9905 @item mem @var{lower} @var{upper} @var{attributes}@dots{}
9906 Define a memory region bounded by @var{lower} and @var{upper} with
9907 attributes @var{attributes}@dots{}, and add it to the list of regions
9908 monitored by @value{GDBN}. Note that @var{upper} == 0 is a special
9909 case: it is treated as the target's maximum memory address.
9910 (0xffff on 16 bit targets, 0xffffffff on 32 bit targets, etc.)
9913 Discard any user changes to the memory regions and use target-supplied
9914 regions, if available, or no regions if the target does not support.
9917 @item delete mem @var{nums}@dots{}
9918 Remove memory regions @var{nums}@dots{} from the list of regions
9919 monitored by @value{GDBN}.
9922 @item disable mem @var{nums}@dots{}
9923 Disable monitoring of memory regions @var{nums}@dots{}.
9924 A disabled memory region is not forgotten.
9925 It may be enabled again later.
9928 @item enable mem @var{nums}@dots{}
9929 Enable monitoring of memory regions @var{nums}@dots{}.
9933 Print a table of all defined memory regions, with the following columns
9937 @item Memory Region Number
9938 @item Enabled or Disabled.
9939 Enabled memory regions are marked with @samp{y}.
9940 Disabled memory regions are marked with @samp{n}.
9943 The address defining the inclusive lower bound of the memory region.
9946 The address defining the exclusive upper bound of the memory region.
9949 The list of attributes set for this memory region.
9954 @subsection Attributes
9956 @subsubsection Memory Access Mode
9957 The access mode attributes set whether @value{GDBN} may make read or
9958 write accesses to a memory region.
9960 While these attributes prevent @value{GDBN} from performing invalid
9961 memory accesses, they do nothing to prevent the target system, I/O DMA,
9962 etc.@: from accessing memory.
9966 Memory is read only.
9968 Memory is write only.
9970 Memory is read/write. This is the default.
9973 @subsubsection Memory Access Size
9974 The access size attribute tells @value{GDBN} to use specific sized
9975 accesses in the memory region. Often memory mapped device registers
9976 require specific sized accesses. If no access size attribute is
9977 specified, @value{GDBN} may use accesses of any size.
9981 Use 8 bit memory accesses.
9983 Use 16 bit memory accesses.
9985 Use 32 bit memory accesses.
9987 Use 64 bit memory accesses.
9990 @c @subsubsection Hardware/Software Breakpoints
9991 @c The hardware/software breakpoint attributes set whether @value{GDBN}
9992 @c will use hardware or software breakpoints for the internal breakpoints
9993 @c used by the step, next, finish, until, etc. commands.
9997 @c Always use hardware breakpoints
9998 @c @item swbreak (default)
10001 @subsubsection Data Cache
10002 The data cache attributes set whether @value{GDBN} will cache target
10003 memory. While this generally improves performance by reducing debug
10004 protocol overhead, it can lead to incorrect results because @value{GDBN}
10005 does not know about volatile variables or memory mapped device
10010 Enable @value{GDBN} to cache target memory.
10012 Disable @value{GDBN} from caching target memory. This is the default.
10015 @subsection Memory Access Checking
10016 @value{GDBN} can be instructed to refuse accesses to memory that is
10017 not explicitly described. This can be useful if accessing such
10018 regions has undesired effects for a specific target, or to provide
10019 better error checking. The following commands control this behaviour.
10022 @kindex set mem inaccessible-by-default
10023 @item set mem inaccessible-by-default [on|off]
10024 If @code{on} is specified, make @value{GDBN} treat memory not
10025 explicitly described by the memory ranges as non-existent and refuse accesses
10026 to such memory. The checks are only performed if there's at least one
10027 memory range defined. If @code{off} is specified, make @value{GDBN}
10028 treat the memory not explicitly described by the memory ranges as RAM.
10029 The default value is @code{on}.
10030 @kindex show mem inaccessible-by-default
10031 @item show mem inaccessible-by-default
10032 Show the current handling of accesses to unknown memory.
10036 @c @subsubsection Memory Write Verification
10037 @c The memory write verification attributes set whether @value{GDBN}
10038 @c will re-reads data after each write to verify the write was successful.
10042 @c @item noverify (default)
10045 @node Dump/Restore Files
10046 @section Copy Between Memory and a File
10047 @cindex dump/restore files
10048 @cindex append data to a file
10049 @cindex dump data to a file
10050 @cindex restore data from a file
10052 You can use the commands @code{dump}, @code{append}, and
10053 @code{restore} to copy data between target memory and a file. The
10054 @code{dump} and @code{append} commands write data to a file, and the
10055 @code{restore} command reads data from a file back into the inferior's
10056 memory. Files may be in binary, Motorola S-record, Intel hex, or
10057 Tektronix Hex format; however, @value{GDBN} can only append to binary
10063 @item dump @r{[}@var{format}@r{]} memory @var{filename} @var{start_addr} @var{end_addr}
10064 @itemx dump @r{[}@var{format}@r{]} value @var{filename} @var{expr}
10065 Dump the contents of memory from @var{start_addr} to @var{end_addr},
10066 or the value of @var{expr}, to @var{filename} in the given format.
10068 The @var{format} parameter may be any one of:
10075 Motorola S-record format.
10077 Tektronix Hex format.
10080 @value{GDBN} uses the same definitions of these formats as the
10081 @sc{gnu} binary utilities, like @samp{objdump} and @samp{objcopy}. If
10082 @var{format} is omitted, @value{GDBN} dumps the data in raw binary
10086 @item append @r{[}binary@r{]} memory @var{filename} @var{start_addr} @var{end_addr}
10087 @itemx append @r{[}binary@r{]} value @var{filename} @var{expr}
10088 Append the contents of memory from @var{start_addr} to @var{end_addr},
10089 or the value of @var{expr}, to the file @var{filename}, in raw binary form.
10090 (@value{GDBN} can only append data to files in raw binary form.)
10093 @item restore @var{filename} @r{[}binary@r{]} @var{bias} @var{start} @var{end}
10094 Restore the contents of file @var{filename} into memory. The
10095 @code{restore} command can automatically recognize any known @sc{bfd}
10096 file format, except for raw binary. To restore a raw binary file you
10097 must specify the optional keyword @code{binary} after the filename.
10099 If @var{bias} is non-zero, its value will be added to the addresses
10100 contained in the file. Binary files always start at address zero, so
10101 they will be restored at address @var{bias}. Other bfd files have
10102 a built-in location; they will be restored at offset @var{bias}
10103 from that location.
10105 If @var{start} and/or @var{end} are non-zero, then only data between
10106 file offset @var{start} and file offset @var{end} will be restored.
10107 These offsets are relative to the addresses in the file, before
10108 the @var{bias} argument is applied.
10112 @node Core File Generation
10113 @section How to Produce a Core File from Your Program
10114 @cindex dump core from inferior
10116 A @dfn{core file} or @dfn{core dump} is a file that records the memory
10117 image of a running process and its process status (register values
10118 etc.). Its primary use is post-mortem debugging of a program that
10119 crashed while it ran outside a debugger. A program that crashes
10120 automatically produces a core file, unless this feature is disabled by
10121 the user. @xref{Files}, for information on invoking @value{GDBN} in
10122 the post-mortem debugging mode.
10124 Occasionally, you may wish to produce a core file of the program you
10125 are debugging in order to preserve a snapshot of its state.
10126 @value{GDBN} has a special command for that.
10130 @kindex generate-core-file
10131 @item generate-core-file [@var{file}]
10132 @itemx gcore [@var{file}]
10133 Produce a core dump of the inferior process. The optional argument
10134 @var{file} specifies the file name where to put the core dump. If not
10135 specified, the file name defaults to @file{core.@var{pid}}, where
10136 @var{pid} is the inferior process ID.
10138 Note that this command is implemented only for some systems (as of
10139 this writing, @sc{gnu}/Linux, FreeBSD, Solaris, and S390).
10142 @node Character Sets
10143 @section Character Sets
10144 @cindex character sets
10146 @cindex translating between character sets
10147 @cindex host character set
10148 @cindex target character set
10150 If the program you are debugging uses a different character set to
10151 represent characters and strings than the one @value{GDBN} uses itself,
10152 @value{GDBN} can automatically translate between the character sets for
10153 you. The character set @value{GDBN} uses we call the @dfn{host
10154 character set}; the one the inferior program uses we call the
10155 @dfn{target character set}.
10157 For example, if you are running @value{GDBN} on a @sc{gnu}/Linux system, which
10158 uses the ISO Latin 1 character set, but you are using @value{GDBN}'s
10159 remote protocol (@pxref{Remote Debugging}) to debug a program
10160 running on an IBM mainframe, which uses the @sc{ebcdic} character set,
10161 then the host character set is Latin-1, and the target character set is
10162 @sc{ebcdic}. If you give @value{GDBN} the command @code{set
10163 target-charset EBCDIC-US}, then @value{GDBN} translates between
10164 @sc{ebcdic} and Latin 1 as you print character or string values, or use
10165 character and string literals in expressions.
10167 @value{GDBN} has no way to automatically recognize which character set
10168 the inferior program uses; you must tell it, using the @code{set
10169 target-charset} command, described below.
10171 Here are the commands for controlling @value{GDBN}'s character set
10175 @item set target-charset @var{charset}
10176 @kindex set target-charset
10177 Set the current target character set to @var{charset}. To display the
10178 list of supported target character sets, type
10179 @kbd{@w{set target-charset @key{TAB}@key{TAB}}}.
10181 @item set host-charset @var{charset}
10182 @kindex set host-charset
10183 Set the current host character set to @var{charset}.
10185 By default, @value{GDBN} uses a host character set appropriate to the
10186 system it is running on; you can override that default using the
10187 @code{set host-charset} command. On some systems, @value{GDBN} cannot
10188 automatically determine the appropriate host character set. In this
10189 case, @value{GDBN} uses @samp{UTF-8}.
10191 @value{GDBN} can only use certain character sets as its host character
10192 set. If you type @kbd{@w{set host-charset @key{TAB}@key{TAB}}},
10193 @value{GDBN} will list the host character sets it supports.
10195 @item set charset @var{charset}
10196 @kindex set charset
10197 Set the current host and target character sets to @var{charset}. As
10198 above, if you type @kbd{@w{set charset @key{TAB}@key{TAB}}},
10199 @value{GDBN} will list the names of the character sets that can be used
10200 for both host and target.
10203 @kindex show charset
10204 Show the names of the current host and target character sets.
10206 @item show host-charset
10207 @kindex show host-charset
10208 Show the name of the current host character set.
10210 @item show target-charset
10211 @kindex show target-charset
10212 Show the name of the current target character set.
10214 @item set target-wide-charset @var{charset}
10215 @kindex set target-wide-charset
10216 Set the current target's wide character set to @var{charset}. This is
10217 the character set used by the target's @code{wchar_t} type. To
10218 display the list of supported wide character sets, type
10219 @kbd{@w{set target-wide-charset @key{TAB}@key{TAB}}}.
10221 @item show target-wide-charset
10222 @kindex show target-wide-charset
10223 Show the name of the current target's wide character set.
10226 Here is an example of @value{GDBN}'s character set support in action.
10227 Assume that the following source code has been placed in the file
10228 @file{charset-test.c}:
10234 = @{72, 101, 108, 108, 111, 44, 32, 119,
10235 111, 114, 108, 100, 33, 10, 0@};
10236 char ibm1047_hello[]
10237 = @{200, 133, 147, 147, 150, 107, 64, 166,
10238 150, 153, 147, 132, 90, 37, 0@};
10242 printf ("Hello, world!\n");
10246 In this program, @code{ascii_hello} and @code{ibm1047_hello} are arrays
10247 containing the string @samp{Hello, world!} followed by a newline,
10248 encoded in the @sc{ascii} and @sc{ibm1047} character sets.
10250 We compile the program, and invoke the debugger on it:
10253 $ gcc -g charset-test.c -o charset-test
10254 $ gdb -nw charset-test
10255 GNU gdb 2001-12-19-cvs
10256 Copyright 2001 Free Software Foundation, Inc.
10261 We can use the @code{show charset} command to see what character sets
10262 @value{GDBN} is currently using to interpret and display characters and
10266 (@value{GDBP}) show charset
10267 The current host and target character set is `ISO-8859-1'.
10271 For the sake of printing this manual, let's use @sc{ascii} as our
10272 initial character set:
10274 (@value{GDBP}) set charset ASCII
10275 (@value{GDBP}) show charset
10276 The current host and target character set is `ASCII'.
10280 Let's assume that @sc{ascii} is indeed the correct character set for our
10281 host system --- in other words, let's assume that if @value{GDBN} prints
10282 characters using the @sc{ascii} character set, our terminal will display
10283 them properly. Since our current target character set is also
10284 @sc{ascii}, the contents of @code{ascii_hello} print legibly:
10287 (@value{GDBP}) print ascii_hello
10288 $1 = 0x401698 "Hello, world!\n"
10289 (@value{GDBP}) print ascii_hello[0]
10294 @value{GDBN} uses the target character set for character and string
10295 literals you use in expressions:
10298 (@value{GDBP}) print '+'
10303 The @sc{ascii} character set uses the number 43 to encode the @samp{+}
10306 @value{GDBN} relies on the user to tell it which character set the
10307 target program uses. If we print @code{ibm1047_hello} while our target
10308 character set is still @sc{ascii}, we get jibberish:
10311 (@value{GDBP}) print ibm1047_hello
10312 $4 = 0x4016a8 "\310\205\223\223\226k@@\246\226\231\223\204Z%"
10313 (@value{GDBP}) print ibm1047_hello[0]
10318 If we invoke the @code{set target-charset} followed by @key{TAB}@key{TAB},
10319 @value{GDBN} tells us the character sets it supports:
10322 (@value{GDBP}) set target-charset
10323 ASCII EBCDIC-US IBM1047 ISO-8859-1
10324 (@value{GDBP}) set target-charset
10327 We can select @sc{ibm1047} as our target character set, and examine the
10328 program's strings again. Now the @sc{ascii} string is wrong, but
10329 @value{GDBN} translates the contents of @code{ibm1047_hello} from the
10330 target character set, @sc{ibm1047}, to the host character set,
10331 @sc{ascii}, and they display correctly:
10334 (@value{GDBP}) set target-charset IBM1047
10335 (@value{GDBP}) show charset
10336 The current host character set is `ASCII'.
10337 The current target character set is `IBM1047'.
10338 (@value{GDBP}) print ascii_hello
10339 $6 = 0x401698 "\110\145%%?\054\040\167?\162%\144\041\012"
10340 (@value{GDBP}) print ascii_hello[0]
10342 (@value{GDBP}) print ibm1047_hello
10343 $8 = 0x4016a8 "Hello, world!\n"
10344 (@value{GDBP}) print ibm1047_hello[0]
10349 As above, @value{GDBN} uses the target character set for character and
10350 string literals you use in expressions:
10353 (@value{GDBP}) print '+'
10358 The @sc{ibm1047} character set uses the number 78 to encode the @samp{+}
10361 @node Caching Remote Data
10362 @section Caching Data of Remote Targets
10363 @cindex caching data of remote targets
10365 @value{GDBN} caches data exchanged between the debugger and a
10366 remote target (@pxref{Remote Debugging}). Such caching generally improves
10367 performance, because it reduces the overhead of the remote protocol by
10368 bundling memory reads and writes into large chunks. Unfortunately, simply
10369 caching everything would lead to incorrect results, since @value{GDBN}
10370 does not necessarily know anything about volatile values, memory-mapped I/O
10371 addresses, etc. Furthermore, in non-stop mode (@pxref{Non-Stop Mode})
10372 memory can be changed @emph{while} a gdb command is executing.
10373 Therefore, by default, @value{GDBN} only caches data
10374 known to be on the stack@footnote{In non-stop mode, it is moderately
10375 rare for a running thread to modify the stack of a stopped thread
10376 in a way that would interfere with a backtrace, and caching of
10377 stack reads provides a significant speed up of remote backtraces.}.
10378 Other regions of memory can be explicitly marked as
10379 cacheable; see @pxref{Memory Region Attributes}.
10382 @kindex set remotecache
10383 @item set remotecache on
10384 @itemx set remotecache off
10385 This option no longer does anything; it exists for compatibility
10388 @kindex show remotecache
10389 @item show remotecache
10390 Show the current state of the obsolete remotecache flag.
10392 @kindex set stack-cache
10393 @item set stack-cache on
10394 @itemx set stack-cache off
10395 Enable or disable caching of stack accesses. When @code{ON}, use
10396 caching. By default, this option is @code{ON}.
10398 @kindex show stack-cache
10399 @item show stack-cache
10400 Show the current state of data caching for memory accesses.
10402 @kindex info dcache
10403 @item info dcache @r{[}line@r{]}
10404 Print the information about the data cache performance. The
10405 information displayed includes the dcache width and depth, and for
10406 each cache line, its number, address, and how many times it was
10407 referenced. This command is useful for debugging the data cache
10410 If a line number is specified, the contents of that line will be
10413 @item set dcache size @var{size}
10414 @cindex dcache size
10415 @kindex set dcache size
10416 Set maximum number of entries in dcache (dcache depth above).
10418 @item set dcache line-size @var{line-size}
10419 @cindex dcache line-size
10420 @kindex set dcache line-size
10421 Set number of bytes each dcache entry caches (dcache width above).
10422 Must be a power of 2.
10424 @item show dcache size
10425 @kindex show dcache size
10426 Show maximum number of dcache entries. See also @ref{Caching Remote Data, info dcache}.
10428 @item show dcache line-size
10429 @kindex show dcache line-size
10430 Show default size of dcache lines. See also @ref{Caching Remote Data, info dcache}.
10434 @node Searching Memory
10435 @section Search Memory
10436 @cindex searching memory
10438 Memory can be searched for a particular sequence of bytes with the
10439 @code{find} command.
10443 @item find @r{[}/@var{sn}@r{]} @var{start_addr}, +@var{len}, @var{val1} @r{[}, @var{val2}, @dots{}@r{]}
10444 @itemx find @r{[}/@var{sn}@r{]} @var{start_addr}, @var{end_addr}, @var{val1} @r{[}, @var{val2}, @dots{}@r{]}
10445 Search memory for the sequence of bytes specified by @var{val1}, @var{val2},
10446 etc. The search begins at address @var{start_addr} and continues for either
10447 @var{len} bytes or through to @var{end_addr} inclusive.
10450 @var{s} and @var{n} are optional parameters.
10451 They may be specified in either order, apart or together.
10454 @item @var{s}, search query size
10455 The size of each search query value.
10461 halfwords (two bytes)
10465 giant words (eight bytes)
10468 All values are interpreted in the current language.
10469 This means, for example, that if the current source language is C/C@t{++}
10470 then searching for the string ``hello'' includes the trailing '\0'.
10472 If the value size is not specified, it is taken from the
10473 value's type in the current language.
10474 This is useful when one wants to specify the search
10475 pattern as a mixture of types.
10476 Note that this means, for example, that in the case of C-like languages
10477 a search for an untyped 0x42 will search for @samp{(int) 0x42}
10478 which is typically four bytes.
10480 @item @var{n}, maximum number of finds
10481 The maximum number of matches to print. The default is to print all finds.
10484 You can use strings as search values. Quote them with double-quotes
10486 The string value is copied into the search pattern byte by byte,
10487 regardless of the endianness of the target and the size specification.
10489 The address of each match found is printed as well as a count of the
10490 number of matches found.
10492 The address of the last value found is stored in convenience variable
10494 A count of the number of matches is stored in @samp{$numfound}.
10496 For example, if stopped at the @code{printf} in this function:
10502 static char hello[] = "hello-hello";
10503 static struct @{ char c; short s; int i; @}
10504 __attribute__ ((packed)) mixed
10505 = @{ 'c', 0x1234, 0x87654321 @};
10506 printf ("%s\n", hello);
10511 you get during debugging:
10514 (gdb) find &hello[0], +sizeof(hello), "hello"
10515 0x804956d <hello.1620+6>
10517 (gdb) find &hello[0], +sizeof(hello), 'h', 'e', 'l', 'l', 'o'
10518 0x8049567 <hello.1620>
10519 0x804956d <hello.1620+6>
10521 (gdb) find /b1 &hello[0], +sizeof(hello), 'h', 0x65, 'l'
10522 0x8049567 <hello.1620>
10524 (gdb) find &mixed, +sizeof(mixed), (char) 'c', (short) 0x1234, (int) 0x87654321
10525 0x8049560 <mixed.1625>
10527 (gdb) print $numfound
10530 $2 = (void *) 0x8049560
10533 @node Optimized Code
10534 @chapter Debugging Optimized Code
10535 @cindex optimized code, debugging
10536 @cindex debugging optimized code
10538 Almost all compilers support optimization. With optimization
10539 disabled, the compiler generates assembly code that corresponds
10540 directly to your source code, in a simplistic way. As the compiler
10541 applies more powerful optimizations, the generated assembly code
10542 diverges from your original source code. With help from debugging
10543 information generated by the compiler, @value{GDBN} can map from
10544 the running program back to constructs from your original source.
10546 @value{GDBN} is more accurate with optimization disabled. If you
10547 can recompile without optimization, it is easier to follow the
10548 progress of your program during debugging. But, there are many cases
10549 where you may need to debug an optimized version.
10551 When you debug a program compiled with @samp{-g -O}, remember that the
10552 optimizer has rearranged your code; the debugger shows you what is
10553 really there. Do not be too surprised when the execution path does not
10554 exactly match your source file! An extreme example: if you define a
10555 variable, but never use it, @value{GDBN} never sees that
10556 variable---because the compiler optimizes it out of existence.
10558 Some things do not work as well with @samp{-g -O} as with just
10559 @samp{-g}, particularly on machines with instruction scheduling. If in
10560 doubt, recompile with @samp{-g} alone, and if this fixes the problem,
10561 please report it to us as a bug (including a test case!).
10562 @xref{Variables}, for more information about debugging optimized code.
10565 * Inline Functions:: How @value{GDBN} presents inlining
10566 * Tail Call Frames:: @value{GDBN} analysis of jumps to functions
10569 @node Inline Functions
10570 @section Inline Functions
10571 @cindex inline functions, debugging
10573 @dfn{Inlining} is an optimization that inserts a copy of the function
10574 body directly at each call site, instead of jumping to a shared
10575 routine. @value{GDBN} displays inlined functions just like
10576 non-inlined functions. They appear in backtraces. You can view their
10577 arguments and local variables, step into them with @code{step}, skip
10578 them with @code{next}, and escape from them with @code{finish}.
10579 You can check whether a function was inlined by using the
10580 @code{info frame} command.
10582 For @value{GDBN} to support inlined functions, the compiler must
10583 record information about inlining in the debug information ---
10584 @value{NGCC} using the @sc{dwarf 2} format does this, and several
10585 other compilers do also. @value{GDBN} only supports inlined functions
10586 when using @sc{dwarf 2}. Versions of @value{NGCC} before 4.1
10587 do not emit two required attributes (@samp{DW_AT_call_file} and
10588 @samp{DW_AT_call_line}); @value{GDBN} does not display inlined
10589 function calls with earlier versions of @value{NGCC}. It instead
10590 displays the arguments and local variables of inlined functions as
10591 local variables in the caller.
10593 The body of an inlined function is directly included at its call site;
10594 unlike a non-inlined function, there are no instructions devoted to
10595 the call. @value{GDBN} still pretends that the call site and the
10596 start of the inlined function are different instructions. Stepping to
10597 the call site shows the call site, and then stepping again shows
10598 the first line of the inlined function, even though no additional
10599 instructions are executed.
10601 This makes source-level debugging much clearer; you can see both the
10602 context of the call and then the effect of the call. Only stepping by
10603 a single instruction using @code{stepi} or @code{nexti} does not do
10604 this; single instruction steps always show the inlined body.
10606 There are some ways that @value{GDBN} does not pretend that inlined
10607 function calls are the same as normal calls:
10611 Setting breakpoints at the call site of an inlined function may not
10612 work, because the call site does not contain any code. @value{GDBN}
10613 may incorrectly move the breakpoint to the next line of the enclosing
10614 function, after the call. This limitation will be removed in a future
10615 version of @value{GDBN}; until then, set a breakpoint on an earlier line
10616 or inside the inlined function instead.
10619 @value{GDBN} cannot locate the return value of inlined calls after
10620 using the @code{finish} command. This is a limitation of compiler-generated
10621 debugging information; after @code{finish}, you can step to the next line
10622 and print a variable where your program stored the return value.
10626 @node Tail Call Frames
10627 @section Tail Call Frames
10628 @cindex tail call frames, debugging
10630 Function @code{B} can call function @code{C} in its very last statement. In
10631 unoptimized compilation the call of @code{C} is immediately followed by return
10632 instruction at the end of @code{B} code. Optimizing compiler may replace the
10633 call and return in function @code{B} into one jump to function @code{C}
10634 instead. Such use of a jump instruction is called @dfn{tail call}.
10636 During execution of function @code{C}, there will be no indication in the
10637 function call stack frames that it was tail-called from @code{B}. If function
10638 @code{A} regularly calls function @code{B} which tail-calls function @code{C},
10639 then @value{GDBN} will see @code{A} as the caller of @code{C}. However, in
10640 some cases @value{GDBN} can determine that @code{C} was tail-called from
10641 @code{B}, and it will then create fictitious call frame for that, with the
10642 return address set up as if @code{B} called @code{C} normally.
10644 This functionality is currently supported only by DWARF 2 debugging format and
10645 the compiler has to produce @samp{DW_TAG_GNU_call_site} tags. With
10646 @value{NGCC}, you need to specify @option{-O -g} during compilation, to get
10649 @kbd{info frame} command (@pxref{Frame Info}) will indicate the tail call frame
10650 kind by text @code{tail call frame} such as in this sample @value{GDBN} output:
10654 0x40066b <b(int, double)+11>: jmp 0x400640 <c(int, double)>
10656 Stack level 1, frame at 0x7fffffffda30:
10657 rip = 0x40066d in b (amd64-entry-value.cc:59); saved rip 0x4004c5
10658 tail call frame, caller of frame at 0x7fffffffda30
10659 source language c++.
10660 Arglist at unknown address.
10661 Locals at unknown address, Previous frame's sp is 0x7fffffffda30
10664 The detection of all the possible code path executions can find them ambiguous.
10665 There is no execution history stored (possible @ref{Reverse Execution} is never
10666 used for this purpose) and the last known caller could have reached the known
10667 callee by multiple different jump sequences. In such case @value{GDBN} still
10668 tries to show at least all the unambiguous top tail callers and all the
10669 unambiguous bottom tail calees, if any.
10672 @anchor{set debug entry-values}
10673 @item set debug entry-values
10674 @kindex set debug entry-values
10675 When set to on, enables printing of analysis messages for both frame argument
10676 values at function entry and tail calls. It will show all the possible valid
10677 tail calls code paths it has considered. It will also print the intersection
10678 of them with the final unambiguous (possibly partial or even empty) code path
10681 @item show debug entry-values
10682 @kindex show debug entry-values
10683 Show the current state of analysis messages printing for both frame argument
10684 values at function entry and tail calls.
10687 The analysis messages for tail calls can for example show why the virtual tail
10688 call frame for function @code{c} has not been recognized (due to the indirect
10689 reference by variable @code{x}):
10692 static void __attribute__((noinline, noclone)) c (void);
10693 void (*x) (void) = c;
10694 static void __attribute__((noinline, noclone)) a (void) @{ x++; @}
10695 static void __attribute__((noinline, noclone)) c (void) @{ a (); @}
10696 int main (void) @{ x (); return 0; @}
10698 Breakpoint 1, DW_OP_GNU_entry_value resolving cannot find
10699 DW_TAG_GNU_call_site 0x40039a in main
10701 3 static void __attribute__((noinline, noclone)) a (void) @{ x++; @}
10704 #1 0x000000000040039a in main () at t.c:5
10707 Another possibility is an ambiguous virtual tail call frames resolution:
10711 static void __attribute__((noinline, noclone)) f (void) @{ i++; @}
10712 static void __attribute__((noinline, noclone)) e (void) @{ f (); @}
10713 static void __attribute__((noinline, noclone)) d (void) @{ f (); @}
10714 static void __attribute__((noinline, noclone)) c (void) @{ d (); @}
10715 static void __attribute__((noinline, noclone)) b (void)
10716 @{ if (i) c (); else e (); @}
10717 static void __attribute__((noinline, noclone)) a (void) @{ b (); @}
10718 int main (void) @{ a (); return 0; @}
10720 tailcall: initial: 0x4004d2(a) 0x4004ce(b) 0x4004b2(c) 0x4004a2(d)
10721 tailcall: compare: 0x4004d2(a) 0x4004cc(b) 0x400492(e)
10722 tailcall: reduced: 0x4004d2(a) |
10725 #1 0x00000000004004d2 in a () at t.c:8
10726 #2 0x0000000000400395 in main () at t.c:9
10729 @set CALLSEQ1A @code{main@value{ARROW}a@value{ARROW}b@value{ARROW}c@value{ARROW}d@value{ARROW}f}
10730 @set CALLSEQ2A @code{main@value{ARROW}a@value{ARROW}b@value{ARROW}e@value{ARROW}f}
10732 @c Convert CALLSEQ#A to CALLSEQ#B depending on HAVE_MAKEINFO_CLICK.
10733 @ifset HAVE_MAKEINFO_CLICK
10734 @set ARROW @click{}
10735 @set CALLSEQ1B @clicksequence{@value{CALLSEQ1A}}
10736 @set CALLSEQ2B @clicksequence{@value{CALLSEQ2A}}
10738 @ifclear HAVE_MAKEINFO_CLICK
10740 @set CALLSEQ1B @value{CALLSEQ1A}
10741 @set CALLSEQ2B @value{CALLSEQ2A}
10744 Frames #0 and #2 are real, #1 is a virtual tail call frame.
10745 The code can have possible execution paths @value{CALLSEQ1B} or
10746 @value{CALLSEQ2B}, @value{GDBN} cannot find which one from the inferior state.
10748 @code{initial:} state shows some random possible calling sequence @value{GDBN}
10749 has found. It then finds another possible calling sequcen - that one is
10750 prefixed by @code{compare:}. The non-ambiguous intersection of these two is
10751 printed as the @code{reduced:} calling sequence. That one could have many
10752 futher @code{compare:} and @code{reduced:} statements as long as there remain
10753 any non-ambiguous sequence entries.
10755 For the frame of function @code{b} in both cases there are different possible
10756 @code{$pc} values (@code{0x4004cc} or @code{0x4004ce}), therefore this frame is
10757 also ambigous. The only non-ambiguous frame is the one for function @code{a},
10758 therefore this one is displayed to the user while the ambiguous frames are
10761 There can be also reasons why printing of frame argument values at function
10766 static void __attribute__((noinline, noclone)) c (int i) @{ v++; @}
10767 static void __attribute__((noinline, noclone)) a (int i);
10768 static void __attribute__((noinline, noclone)) b (int i) @{ a (i); @}
10769 static void __attribute__((noinline, noclone)) a (int i)
10770 @{ if (i) b (i - 1); else c (0); @}
10771 int main (void) @{ a (5); return 0; @}
10774 #0 c (i=i@@entry=0) at t.c:2
10775 #1 0x0000000000400428 in a (DW_OP_GNU_entry_value resolving has found
10776 function "a" at 0x400420 can call itself via tail calls
10777 i=<optimized out>) at t.c:6
10778 #2 0x000000000040036e in main () at t.c:7
10781 @value{GDBN} cannot find out from the inferior state if and how many times did
10782 function @code{a} call itself (via function @code{b}) as these calls would be
10783 tail calls. Such tail calls would modify thue @code{i} variable, therefore
10784 @value{GDBN} cannot be sure the value it knows would be right - @value{GDBN}
10785 prints @code{<optimized out>} instead.
10788 @chapter C Preprocessor Macros
10790 Some languages, such as C and C@t{++}, provide a way to define and invoke
10791 ``preprocessor macros'' which expand into strings of tokens.
10792 @value{GDBN} can evaluate expressions containing macro invocations, show
10793 the result of macro expansion, and show a macro's definition, including
10794 where it was defined.
10796 You may need to compile your program specially to provide @value{GDBN}
10797 with information about preprocessor macros. Most compilers do not
10798 include macros in their debugging information, even when you compile
10799 with the @option{-g} flag. @xref{Compilation}.
10801 A program may define a macro at one point, remove that definition later,
10802 and then provide a different definition after that. Thus, at different
10803 points in the program, a macro may have different definitions, or have
10804 no definition at all. If there is a current stack frame, @value{GDBN}
10805 uses the macros in scope at that frame's source code line. Otherwise,
10806 @value{GDBN} uses the macros in scope at the current listing location;
10809 Whenever @value{GDBN} evaluates an expression, it always expands any
10810 macro invocations present in the expression. @value{GDBN} also provides
10811 the following commands for working with macros explicitly.
10815 @kindex macro expand
10816 @cindex macro expansion, showing the results of preprocessor
10817 @cindex preprocessor macro expansion, showing the results of
10818 @cindex expanding preprocessor macros
10819 @item macro expand @var{expression}
10820 @itemx macro exp @var{expression}
10821 Show the results of expanding all preprocessor macro invocations in
10822 @var{expression}. Since @value{GDBN} simply expands macros, but does
10823 not parse the result, @var{expression} need not be a valid expression;
10824 it can be any string of tokens.
10827 @item macro expand-once @var{expression}
10828 @itemx macro exp1 @var{expression}
10829 @cindex expand macro once
10830 @i{(This command is not yet implemented.)} Show the results of
10831 expanding those preprocessor macro invocations that appear explicitly in
10832 @var{expression}. Macro invocations appearing in that expansion are
10833 left unchanged. This command allows you to see the effect of a
10834 particular macro more clearly, without being confused by further
10835 expansions. Since @value{GDBN} simply expands macros, but does not
10836 parse the result, @var{expression} need not be a valid expression; it
10837 can be any string of tokens.
10840 @cindex macro definition, showing
10841 @cindex definition of a macro, showing
10842 @cindex macros, from debug info
10843 @item info macro [-a|-all] [--] @var{macro}
10844 Show the current definition or all definitions of the named @var{macro},
10845 and describe the source location or compiler command-line where that
10846 definition was established. The optional double dash is to signify the end of
10847 argument processing and the beginning of @var{macro} for non C-like macros where
10848 the macro may begin with a hyphen.
10850 @kindex info macros
10851 @item info macros @var{linespec}
10852 Show all macro definitions that are in effect at the location specified
10853 by @var{linespec}, and describe the source location or compiler
10854 command-line where those definitions were established.
10856 @kindex macro define
10857 @cindex user-defined macros
10858 @cindex defining macros interactively
10859 @cindex macros, user-defined
10860 @item macro define @var{macro} @var{replacement-list}
10861 @itemx macro define @var{macro}(@var{arglist}) @var{replacement-list}
10862 Introduce a definition for a preprocessor macro named @var{macro},
10863 invocations of which are replaced by the tokens given in
10864 @var{replacement-list}. The first form of this command defines an
10865 ``object-like'' macro, which takes no arguments; the second form
10866 defines a ``function-like'' macro, which takes the arguments given in
10869 A definition introduced by this command is in scope in every
10870 expression evaluated in @value{GDBN}, until it is removed with the
10871 @code{macro undef} command, described below. The definition overrides
10872 all definitions for @var{macro} present in the program being debugged,
10873 as well as any previous user-supplied definition.
10875 @kindex macro undef
10876 @item macro undef @var{macro}
10877 Remove any user-supplied definition for the macro named @var{macro}.
10878 This command only affects definitions provided with the @code{macro
10879 define} command, described above; it cannot remove definitions present
10880 in the program being debugged.
10884 List all the macros defined using the @code{macro define} command.
10887 @cindex macros, example of debugging with
10888 Here is a transcript showing the above commands in action. First, we
10889 show our source files:
10894 #include "sample.h"
10897 #define ADD(x) (M + x)
10902 printf ("Hello, world!\n");
10904 printf ("We're so creative.\n");
10906 printf ("Goodbye, world!\n");
10913 Now, we compile the program using the @sc{gnu} C compiler,
10914 @value{NGCC}. We pass the @option{-gdwarf-2}@footnote{This is the
10915 minimum. Recent versions of @value{NGCC} support @option{-gdwarf-3}
10916 and @option{-gdwarf-4}; we recommend always choosing the most recent
10917 version of DWARF.} @emph{and} @option{-g3} flags to ensure the compiler
10918 includes information about preprocessor macros in the debugging
10922 $ gcc -gdwarf-2 -g3 sample.c -o sample
10926 Now, we start @value{GDBN} on our sample program:
10930 GNU gdb 2002-05-06-cvs
10931 Copyright 2002 Free Software Foundation, Inc.
10932 GDB is free software, @dots{}
10936 We can expand macros and examine their definitions, even when the
10937 program is not running. @value{GDBN} uses the current listing position
10938 to decide which macro definitions are in scope:
10941 (@value{GDBP}) list main
10944 5 #define ADD(x) (M + x)
10949 10 printf ("Hello, world!\n");
10951 12 printf ("We're so creative.\n");
10952 (@value{GDBP}) info macro ADD
10953 Defined at /home/jimb/gdb/macros/play/sample.c:5
10954 #define ADD(x) (M + x)
10955 (@value{GDBP}) info macro Q
10956 Defined at /home/jimb/gdb/macros/play/sample.h:1
10957 included at /home/jimb/gdb/macros/play/sample.c:2
10959 (@value{GDBP}) macro expand ADD(1)
10960 expands to: (42 + 1)
10961 (@value{GDBP}) macro expand-once ADD(1)
10962 expands to: once (M + 1)
10966 In the example above, note that @code{macro expand-once} expands only
10967 the macro invocation explicit in the original text --- the invocation of
10968 @code{ADD} --- but does not expand the invocation of the macro @code{M},
10969 which was introduced by @code{ADD}.
10971 Once the program is running, @value{GDBN} uses the macro definitions in
10972 force at the source line of the current stack frame:
10975 (@value{GDBP}) break main
10976 Breakpoint 1 at 0x8048370: file sample.c, line 10.
10978 Starting program: /home/jimb/gdb/macros/play/sample
10980 Breakpoint 1, main () at sample.c:10
10981 10 printf ("Hello, world!\n");
10985 At line 10, the definition of the macro @code{N} at line 9 is in force:
10988 (@value{GDBP}) info macro N
10989 Defined at /home/jimb/gdb/macros/play/sample.c:9
10991 (@value{GDBP}) macro expand N Q M
10992 expands to: 28 < 42
10993 (@value{GDBP}) print N Q M
10998 As we step over directives that remove @code{N}'s definition, and then
10999 give it a new definition, @value{GDBN} finds the definition (or lack
11000 thereof) in force at each point:
11003 (@value{GDBP}) next
11005 12 printf ("We're so creative.\n");
11006 (@value{GDBP}) info macro N
11007 The symbol `N' has no definition as a C/C++ preprocessor macro
11008 at /home/jimb/gdb/macros/play/sample.c:12
11009 (@value{GDBP}) next
11011 14 printf ("Goodbye, world!\n");
11012 (@value{GDBP}) info macro N
11013 Defined at /home/jimb/gdb/macros/play/sample.c:13
11015 (@value{GDBP}) macro expand N Q M
11016 expands to: 1729 < 42
11017 (@value{GDBP}) print N Q M
11022 In addition to source files, macros can be defined on the compilation command
11023 line using the @option{-D@var{name}=@var{value}} syntax. For macros defined in
11024 such a way, @value{GDBN} displays the location of their definition as line zero
11025 of the source file submitted to the compiler.
11028 (@value{GDBP}) info macro __STDC__
11029 Defined at /home/jimb/gdb/macros/play/sample.c:0
11036 @chapter Tracepoints
11037 @c This chapter is based on the documentation written by Michael
11038 @c Snyder, David Taylor, Jim Blandy, and Elena Zannoni.
11040 @cindex tracepoints
11041 In some applications, it is not feasible for the debugger to interrupt
11042 the program's execution long enough for the developer to learn
11043 anything helpful about its behavior. If the program's correctness
11044 depends on its real-time behavior, delays introduced by a debugger
11045 might cause the program to change its behavior drastically, or perhaps
11046 fail, even when the code itself is correct. It is useful to be able
11047 to observe the program's behavior without interrupting it.
11049 Using @value{GDBN}'s @code{trace} and @code{collect} commands, you can
11050 specify locations in the program, called @dfn{tracepoints}, and
11051 arbitrary expressions to evaluate when those tracepoints are reached.
11052 Later, using the @code{tfind} command, you can examine the values
11053 those expressions had when the program hit the tracepoints. The
11054 expressions may also denote objects in memory---structures or arrays,
11055 for example---whose values @value{GDBN} should record; while visiting
11056 a particular tracepoint, you may inspect those objects as if they were
11057 in memory at that moment. However, because @value{GDBN} records these
11058 values without interacting with you, it can do so quickly and
11059 unobtrusively, hopefully not disturbing the program's behavior.
11061 The tracepoint facility is currently available only for remote
11062 targets. @xref{Targets}. In addition, your remote target must know
11063 how to collect trace data. This functionality is implemented in the
11064 remote stub; however, none of the stubs distributed with @value{GDBN}
11065 support tracepoints as of this writing. The format of the remote
11066 packets used to implement tracepoints are described in @ref{Tracepoint
11069 It is also possible to get trace data from a file, in a manner reminiscent
11070 of corefiles; you specify the filename, and use @code{tfind} to search
11071 through the file. @xref{Trace Files}, for more details.
11073 This chapter describes the tracepoint commands and features.
11076 * Set Tracepoints::
11077 * Analyze Collected Data::
11078 * Tracepoint Variables::
11082 @node Set Tracepoints
11083 @section Commands to Set Tracepoints
11085 Before running such a @dfn{trace experiment}, an arbitrary number of
11086 tracepoints can be set. A tracepoint is actually a special type of
11087 breakpoint (@pxref{Set Breaks}), so you can manipulate it using
11088 standard breakpoint commands. For instance, as with breakpoints,
11089 tracepoint numbers are successive integers starting from one, and many
11090 of the commands associated with tracepoints take the tracepoint number
11091 as their argument, to identify which tracepoint to work on.
11093 For each tracepoint, you can specify, in advance, some arbitrary set
11094 of data that you want the target to collect in the trace buffer when
11095 it hits that tracepoint. The collected data can include registers,
11096 local variables, or global data. Later, you can use @value{GDBN}
11097 commands to examine the values these data had at the time the
11098 tracepoint was hit.
11100 Tracepoints do not support every breakpoint feature. Ignore counts on
11101 tracepoints have no effect, and tracepoints cannot run @value{GDBN}
11102 commands when they are hit. Tracepoints may not be thread-specific
11105 @cindex fast tracepoints
11106 Some targets may support @dfn{fast tracepoints}, which are inserted in
11107 a different way (such as with a jump instead of a trap), that is
11108 faster but possibly restricted in where they may be installed.
11110 @cindex static tracepoints
11111 @cindex markers, static tracepoints
11112 @cindex probing markers, static tracepoints
11113 Regular and fast tracepoints are dynamic tracing facilities, meaning
11114 that they can be used to insert tracepoints at (almost) any location
11115 in the target. Some targets may also support controlling @dfn{static
11116 tracepoints} from @value{GDBN}. With static tracing, a set of
11117 instrumentation points, also known as @dfn{markers}, are embedded in
11118 the target program, and can be activated or deactivated by name or
11119 address. These are usually placed at locations which facilitate
11120 investigating what the target is actually doing. @value{GDBN}'s
11121 support for static tracing includes being able to list instrumentation
11122 points, and attach them with @value{GDBN} defined high level
11123 tracepoints that expose the whole range of convenience of
11124 @value{GDBN}'s tracepoints support. Namely, support for collecting
11125 registers values and values of global or local (to the instrumentation
11126 point) variables; tracepoint conditions and trace state variables.
11127 The act of installing a @value{GDBN} static tracepoint on an
11128 instrumentation point, or marker, is referred to as @dfn{probing} a
11129 static tracepoint marker.
11131 @code{gdbserver} supports tracepoints on some target systems.
11132 @xref{Server,,Tracepoints support in @code{gdbserver}}.
11134 This section describes commands to set tracepoints and associated
11135 conditions and actions.
11138 * Create and Delete Tracepoints::
11139 * Enable and Disable Tracepoints::
11140 * Tracepoint Passcounts::
11141 * Tracepoint Conditions::
11142 * Trace State Variables::
11143 * Tracepoint Actions::
11144 * Listing Tracepoints::
11145 * Listing Static Tracepoint Markers::
11146 * Starting and Stopping Trace Experiments::
11147 * Tracepoint Restrictions::
11150 @node Create and Delete Tracepoints
11151 @subsection Create and Delete Tracepoints
11154 @cindex set tracepoint
11156 @item trace @var{location}
11157 The @code{trace} command is very similar to the @code{break} command.
11158 Its argument @var{location} can be a source line, a function name, or
11159 an address in the target program. @xref{Specify Location}. The
11160 @code{trace} command defines a tracepoint, which is a point in the
11161 target program where the debugger will briefly stop, collect some
11162 data, and then allow the program to continue. Setting a tracepoint or
11163 changing its actions takes effect immediately if the remote stub
11164 supports the @samp{InstallInTrace} feature (@pxref{install tracepoint
11166 If remote stub doesn't support the @samp{InstallInTrace} feature, all
11167 these changes don't take effect until the next @code{tstart}
11168 command, and once a trace experiment is running, further changes will
11169 not have any effect until the next trace experiment starts. In addition,
11170 @value{GDBN} supports @dfn{pending tracepoints}---tracepoints whose
11171 address is not yet resolved. (This is similar to pending breakpoints.)
11172 Pending tracepoints are not downloaded to the target and not installed
11173 until they are resolved. The resolution of pending tracepoints requires
11174 @value{GDBN} support---when debugging with the remote target, and
11175 @value{GDBN} disconnects from the remote stub (@pxref{disconnected
11176 tracing}), pending tracepoints can not be resolved (and downloaded to
11177 the remote stub) while @value{GDBN} is disconnected.
11179 Here are some examples of using the @code{trace} command:
11182 (@value{GDBP}) @b{trace foo.c:121} // a source file and line number
11184 (@value{GDBP}) @b{trace +2} // 2 lines forward
11186 (@value{GDBP}) @b{trace my_function} // first source line of function
11188 (@value{GDBP}) @b{trace *my_function} // EXACT start address of function
11190 (@value{GDBP}) @b{trace *0x2117c4} // an address
11194 You can abbreviate @code{trace} as @code{tr}.
11196 @item trace @var{location} if @var{cond}
11197 Set a tracepoint with condition @var{cond}; evaluate the expression
11198 @var{cond} each time the tracepoint is reached, and collect data only
11199 if the value is nonzero---that is, if @var{cond} evaluates as true.
11200 @xref{Tracepoint Conditions, ,Tracepoint Conditions}, for more
11201 information on tracepoint conditions.
11203 @item ftrace @var{location} [ if @var{cond} ]
11204 @cindex set fast tracepoint
11205 @cindex fast tracepoints, setting
11207 The @code{ftrace} command sets a fast tracepoint. For targets that
11208 support them, fast tracepoints will use a more efficient but possibly
11209 less general technique to trigger data collection, such as a jump
11210 instruction instead of a trap, or some sort of hardware support. It
11211 may not be possible to create a fast tracepoint at the desired
11212 location, in which case the command will exit with an explanatory
11215 @value{GDBN} handles arguments to @code{ftrace} exactly as for
11218 On 32-bit x86-architecture systems, fast tracepoints normally need to
11219 be placed at an instruction that is 5 bytes or longer, but can be
11220 placed at 4-byte instructions if the low 64K of memory of the target
11221 program is available to install trampolines. Some Unix-type systems,
11222 such as @sc{gnu}/Linux, exclude low addresses from the program's
11223 address space; but for instance with the Linux kernel it is possible
11224 to let @value{GDBN} use this area by doing a @command{sysctl} command
11225 to set the @code{mmap_min_addr} kernel parameter, as in
11228 sudo sysctl -w vm.mmap_min_addr=32768
11232 which sets the low address to 32K, which leaves plenty of room for
11233 trampolines. The minimum address should be set to a page boundary.
11235 @item strace @var{location} [ if @var{cond} ]
11236 @cindex set static tracepoint
11237 @cindex static tracepoints, setting
11238 @cindex probe static tracepoint marker
11240 The @code{strace} command sets a static tracepoint. For targets that
11241 support it, setting a static tracepoint probes a static
11242 instrumentation point, or marker, found at @var{location}. It may not
11243 be possible to set a static tracepoint at the desired location, in
11244 which case the command will exit with an explanatory message.
11246 @value{GDBN} handles arguments to @code{strace} exactly as for
11247 @code{trace}, with the addition that the user can also specify
11248 @code{-m @var{marker}} as @var{location}. This probes the marker
11249 identified by the @var{marker} string identifier. This identifier
11250 depends on the static tracepoint backend library your program is
11251 using. You can find all the marker identifiers in the @samp{ID} field
11252 of the @code{info static-tracepoint-markers} command output.
11253 @xref{Listing Static Tracepoint Markers,,Listing Static Tracepoint
11254 Markers}. For example, in the following small program using the UST
11260 trace_mark(ust, bar33, "str %s", "FOOBAZ");
11265 the marker id is composed of joining the first two arguments to the
11266 @code{trace_mark} call with a slash, which translates to:
11269 (@value{GDBP}) info static-tracepoint-markers
11270 Cnt Enb ID Address What
11271 1 n ust/bar33 0x0000000000400ddc in main at stexample.c:22
11277 so you may probe the marker above with:
11280 (@value{GDBP}) strace -m ust/bar33
11283 Static tracepoints accept an extra collect action --- @code{collect
11284 $_sdata}. This collects arbitrary user data passed in the probe point
11285 call to the tracing library. In the UST example above, you'll see
11286 that the third argument to @code{trace_mark} is a printf-like format
11287 string. The user data is then the result of running that formating
11288 string against the following arguments. Note that @code{info
11289 static-tracepoint-markers} command output lists that format string in
11290 the @samp{Data:} field.
11292 You can inspect this data when analyzing the trace buffer, by printing
11293 the $_sdata variable like any other variable available to
11294 @value{GDBN}. @xref{Tracepoint Actions,,Tracepoint Action Lists}.
11297 @cindex last tracepoint number
11298 @cindex recent tracepoint number
11299 @cindex tracepoint number
11300 The convenience variable @code{$tpnum} records the tracepoint number
11301 of the most recently set tracepoint.
11303 @kindex delete tracepoint
11304 @cindex tracepoint deletion
11305 @item delete tracepoint @r{[}@var{num}@r{]}
11306 Permanently delete one or more tracepoints. With no argument, the
11307 default is to delete all tracepoints. Note that the regular
11308 @code{delete} command can remove tracepoints also.
11313 (@value{GDBP}) @b{delete trace 1 2 3} // remove three tracepoints
11315 (@value{GDBP}) @b{delete trace} // remove all tracepoints
11319 You can abbreviate this command as @code{del tr}.
11322 @node Enable and Disable Tracepoints
11323 @subsection Enable and Disable Tracepoints
11325 These commands are deprecated; they are equivalent to plain @code{disable} and @code{enable}.
11328 @kindex disable tracepoint
11329 @item disable tracepoint @r{[}@var{num}@r{]}
11330 Disable tracepoint @var{num}, or all tracepoints if no argument
11331 @var{num} is given. A disabled tracepoint will have no effect during
11332 a trace experiment, but it is not forgotten. You can re-enable
11333 a disabled tracepoint using the @code{enable tracepoint} command.
11334 If the command is issued during a trace experiment and the debug target
11335 has support for disabling tracepoints during a trace experiment, then the
11336 change will be effective immediately. Otherwise, it will be applied to the
11337 next trace experiment.
11339 @kindex enable tracepoint
11340 @item enable tracepoint @r{[}@var{num}@r{]}
11341 Enable tracepoint @var{num}, or all tracepoints. If this command is
11342 issued during a trace experiment and the debug target supports enabling
11343 tracepoints during a trace experiment, then the enabled tracepoints will
11344 become effective immediately. Otherwise, they will become effective the
11345 next time a trace experiment is run.
11348 @node Tracepoint Passcounts
11349 @subsection Tracepoint Passcounts
11353 @cindex tracepoint pass count
11354 @item passcount @r{[}@var{n} @r{[}@var{num}@r{]]}
11355 Set the @dfn{passcount} of a tracepoint. The passcount is a way to
11356 automatically stop a trace experiment. If a tracepoint's passcount is
11357 @var{n}, then the trace experiment will be automatically stopped on
11358 the @var{n}'th time that tracepoint is hit. If the tracepoint number
11359 @var{num} is not specified, the @code{passcount} command sets the
11360 passcount of the most recently defined tracepoint. If no passcount is
11361 given, the trace experiment will run until stopped explicitly by the
11367 (@value{GDBP}) @b{passcount 5 2} // Stop on the 5th execution of
11368 @exdent @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @code{// tracepoint 2}
11370 (@value{GDBP}) @b{passcount 12} // Stop on the 12th execution of the
11371 @exdent @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @code{// most recently defined tracepoint.}
11372 (@value{GDBP}) @b{trace foo}
11373 (@value{GDBP}) @b{pass 3}
11374 (@value{GDBP}) @b{trace bar}
11375 (@value{GDBP}) @b{pass 2}
11376 (@value{GDBP}) @b{trace baz}
11377 (@value{GDBP}) @b{pass 1} // Stop tracing when foo has been
11378 @exdent @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @code{// executed 3 times OR when bar has}
11379 @exdent @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @code{// been executed 2 times}
11380 @exdent @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @code{// OR when baz has been executed 1 time.}
11384 @node Tracepoint Conditions
11385 @subsection Tracepoint Conditions
11386 @cindex conditional tracepoints
11387 @cindex tracepoint conditions
11389 The simplest sort of tracepoint collects data every time your program
11390 reaches a specified place. You can also specify a @dfn{condition} for
11391 a tracepoint. A condition is just a Boolean expression in your
11392 programming language (@pxref{Expressions, ,Expressions}). A
11393 tracepoint with a condition evaluates the expression each time your
11394 program reaches it, and data collection happens only if the condition
11397 Tracepoint conditions can be specified when a tracepoint is set, by
11398 using @samp{if} in the arguments to the @code{trace} command.
11399 @xref{Create and Delete Tracepoints, ,Setting Tracepoints}. They can
11400 also be set or changed at any time with the @code{condition} command,
11401 just as with breakpoints.
11403 Unlike breakpoint conditions, @value{GDBN} does not actually evaluate
11404 the conditional expression itself. Instead, @value{GDBN} encodes the
11405 expression into an agent expression (@pxref{Agent Expressions})
11406 suitable for execution on the target, independently of @value{GDBN}.
11407 Global variables become raw memory locations, locals become stack
11408 accesses, and so forth.
11410 For instance, suppose you have a function that is usually called
11411 frequently, but should not be called after an error has occurred. You
11412 could use the following tracepoint command to collect data about calls
11413 of that function that happen while the error code is propagating
11414 through the program; an unconditional tracepoint could end up
11415 collecting thousands of useless trace frames that you would have to
11419 (@value{GDBP}) @kbd{trace normal_operation if errcode > 0}
11422 @node Trace State Variables
11423 @subsection Trace State Variables
11424 @cindex trace state variables
11426 A @dfn{trace state variable} is a special type of variable that is
11427 created and managed by target-side code. The syntax is the same as
11428 that for GDB's convenience variables (a string prefixed with ``$''),
11429 but they are stored on the target. They must be created explicitly,
11430 using a @code{tvariable} command. They are always 64-bit signed
11433 Trace state variables are remembered by @value{GDBN}, and downloaded
11434 to the target along with tracepoint information when the trace
11435 experiment starts. There are no intrinsic limits on the number of
11436 trace state variables, beyond memory limitations of the target.
11438 @cindex convenience variables, and trace state variables
11439 Although trace state variables are managed by the target, you can use
11440 them in print commands and expressions as if they were convenience
11441 variables; @value{GDBN} will get the current value from the target
11442 while the trace experiment is running. Trace state variables share
11443 the same namespace as other ``$'' variables, which means that you
11444 cannot have trace state variables with names like @code{$23} or
11445 @code{$pc}, nor can you have a trace state variable and a convenience
11446 variable with the same name.
11450 @item tvariable $@var{name} [ = @var{expression} ]
11452 The @code{tvariable} command creates a new trace state variable named
11453 @code{$@var{name}}, and optionally gives it an initial value of
11454 @var{expression}. @var{expression} is evaluated when this command is
11455 entered; the result will be converted to an integer if possible,
11456 otherwise @value{GDBN} will report an error. A subsequent
11457 @code{tvariable} command specifying the same name does not create a
11458 variable, but instead assigns the supplied initial value to the
11459 existing variable of that name, overwriting any previous initial
11460 value. The default initial value is 0.
11462 @item info tvariables
11463 @kindex info tvariables
11464 List all the trace state variables along with their initial values.
11465 Their current values may also be displayed, if the trace experiment is
11468 @item delete tvariable @r{[} $@var{name} @dots{} @r{]}
11469 @kindex delete tvariable
11470 Delete the given trace state variables, or all of them if no arguments
11475 @node Tracepoint Actions
11476 @subsection Tracepoint Action Lists
11480 @cindex tracepoint actions
11481 @item actions @r{[}@var{num}@r{]}
11482 This command will prompt for a list of actions to be taken when the
11483 tracepoint is hit. If the tracepoint number @var{num} is not
11484 specified, this command sets the actions for the one that was most
11485 recently defined (so that you can define a tracepoint and then say
11486 @code{actions} without bothering about its number). You specify the
11487 actions themselves on the following lines, one action at a time, and
11488 terminate the actions list with a line containing just @code{end}. So
11489 far, the only defined actions are @code{collect}, @code{teval}, and
11490 @code{while-stepping}.
11492 @code{actions} is actually equivalent to @code{commands} (@pxref{Break
11493 Commands, ,Breakpoint Command Lists}), except that only the defined
11494 actions are allowed; any other @value{GDBN} command is rejected.
11496 @cindex remove actions from a tracepoint
11497 To remove all actions from a tracepoint, type @samp{actions @var{num}}
11498 and follow it immediately with @samp{end}.
11501 (@value{GDBP}) @b{collect @var{data}} // collect some data
11503 (@value{GDBP}) @b{while-stepping 5} // single-step 5 times, collect data
11505 (@value{GDBP}) @b{end} // signals the end of actions.
11508 In the following example, the action list begins with @code{collect}
11509 commands indicating the things to be collected when the tracepoint is
11510 hit. Then, in order to single-step and collect additional data
11511 following the tracepoint, a @code{while-stepping} command is used,
11512 followed by the list of things to be collected after each step in a
11513 sequence of single steps. The @code{while-stepping} command is
11514 terminated by its own separate @code{end} command. Lastly, the action
11515 list is terminated by an @code{end} command.
11518 (@value{GDBP}) @b{trace foo}
11519 (@value{GDBP}) @b{actions}
11520 Enter actions for tracepoint 1, one per line:
11523 > while-stepping 12
11524 > collect $pc, arr[i]
11529 @kindex collect @r{(tracepoints)}
11530 @item collect@r{[}/@var{mods}@r{]} @var{expr1}, @var{expr2}, @dots{}
11531 Collect values of the given expressions when the tracepoint is hit.
11532 This command accepts a comma-separated list of any valid expressions.
11533 In addition to global, static, or local variables, the following
11534 special arguments are supported:
11538 Collect all registers.
11541 Collect all function arguments.
11544 Collect all local variables.
11547 Collect the return address. This is helpful if you want to see more
11551 Collects the number of arguments from the static probe at which the
11552 tracepoint is located.
11553 @xref{Static Probe Points}.
11555 @item $_probe_arg@var{n}
11556 @var{n} is an integer between 0 and 11. Collects the @var{n}th argument
11557 from the static probe at which the tracepoint is located.
11558 @xref{Static Probe Points}.
11561 @vindex $_sdata@r{, collect}
11562 Collect static tracepoint marker specific data. Only available for
11563 static tracepoints. @xref{Tracepoint Actions,,Tracepoint Action
11564 Lists}. On the UST static tracepoints library backend, an
11565 instrumentation point resembles a @code{printf} function call. The
11566 tracing library is able to collect user specified data formatted to a
11567 character string using the format provided by the programmer that
11568 instrumented the program. Other backends have similar mechanisms.
11569 Here's an example of a UST marker call:
11572 const char master_name[] = "$your_name";
11573 trace_mark(channel1, marker1, "hello %s", master_name)
11576 In this case, collecting @code{$_sdata} collects the string
11577 @samp{hello $yourname}. When analyzing the trace buffer, you can
11578 inspect @samp{$_sdata} like any other variable available to
11582 You can give several consecutive @code{collect} commands, each one
11583 with a single argument, or one @code{collect} command with several
11584 arguments separated by commas; the effect is the same.
11586 The optional @var{mods} changes the usual handling of the arguments.
11587 @code{s} requests that pointers to chars be handled as strings, in
11588 particular collecting the contents of the memory being pointed at, up
11589 to the first zero. The upper bound is by default the value of the
11590 @code{print elements} variable; if @code{s} is followed by a decimal
11591 number, that is the upper bound instead. So for instance
11592 @samp{collect/s25 mystr} collects as many as 25 characters at
11595 The command @code{info scope} (@pxref{Symbols, info scope}) is
11596 particularly useful for figuring out what data to collect.
11598 @kindex teval @r{(tracepoints)}
11599 @item teval @var{expr1}, @var{expr2}, @dots{}
11600 Evaluate the given expressions when the tracepoint is hit. This
11601 command accepts a comma-separated list of expressions. The results
11602 are discarded, so this is mainly useful for assigning values to trace
11603 state variables (@pxref{Trace State Variables}) without adding those
11604 values to the trace buffer, as would be the case if the @code{collect}
11607 @kindex while-stepping @r{(tracepoints)}
11608 @item while-stepping @var{n}
11609 Perform @var{n} single-step instruction traces after the tracepoint,
11610 collecting new data after each step. The @code{while-stepping}
11611 command is followed by the list of what to collect while stepping
11612 (followed by its own @code{end} command):
11615 > while-stepping 12
11616 > collect $regs, myglobal
11622 Note that @code{$pc} is not automatically collected by
11623 @code{while-stepping}; you need to explicitly collect that register if
11624 you need it. You may abbreviate @code{while-stepping} as @code{ws} or
11627 @item set default-collect @var{expr1}, @var{expr2}, @dots{}
11628 @kindex set default-collect
11629 @cindex default collection action
11630 This variable is a list of expressions to collect at each tracepoint
11631 hit. It is effectively an additional @code{collect} action prepended
11632 to every tracepoint action list. The expressions are parsed
11633 individually for each tracepoint, so for instance a variable named
11634 @code{xyz} may be interpreted as a global for one tracepoint, and a
11635 local for another, as appropriate to the tracepoint's location.
11637 @item show default-collect
11638 @kindex show default-collect
11639 Show the list of expressions that are collected by default at each
11644 @node Listing Tracepoints
11645 @subsection Listing Tracepoints
11648 @kindex info tracepoints @r{[}@var{n}@dots{}@r{]}
11649 @kindex info tp @r{[}@var{n}@dots{}@r{]}
11650 @cindex information about tracepoints
11651 @item info tracepoints @r{[}@var{num}@dots{}@r{]}
11652 Display information about the tracepoint @var{num}. If you don't
11653 specify a tracepoint number, displays information about all the
11654 tracepoints defined so far. The format is similar to that used for
11655 @code{info breakpoints}; in fact, @code{info tracepoints} is the same
11656 command, simply restricting itself to tracepoints.
11658 A tracepoint's listing may include additional information specific to
11663 its passcount as given by the @code{passcount @var{n}} command
11666 the state about installed on target of each location
11670 (@value{GDBP}) @b{info trace}
11671 Num Type Disp Enb Address What
11672 1 tracepoint keep y 0x0804ab57 in foo() at main.cxx:7
11674 collect globfoo, $regs
11679 2 tracepoint keep y <MULTIPLE>
11681 2.1 y 0x0804859c in func4 at change-loc.h:35
11682 installed on target
11683 2.2 y 0xb7ffc480 in func4 at change-loc.h:35
11684 installed on target
11685 2.3 y <PENDING> set_tracepoint
11686 3 tracepoint keep y 0x080485b1 in foo at change-loc.c:29
11687 not installed on target
11692 This command can be abbreviated @code{info tp}.
11695 @node Listing Static Tracepoint Markers
11696 @subsection Listing Static Tracepoint Markers
11699 @kindex info static-tracepoint-markers
11700 @cindex information about static tracepoint markers
11701 @item info static-tracepoint-markers
11702 Display information about all static tracepoint markers defined in the
11705 For each marker, the following columns are printed:
11709 An incrementing counter, output to help readability. This is not a
11712 The marker ID, as reported by the target.
11713 @item Enabled or Disabled
11714 Probed markers are tagged with @samp{y}. @samp{n} identifies marks
11715 that are not enabled.
11717 Where the marker is in your program, as a memory address.
11719 Where the marker is in the source for your program, as a file and line
11720 number. If the debug information included in the program does not
11721 allow @value{GDBN} to locate the source of the marker, this column
11722 will be left blank.
11726 In addition, the following information may be printed for each marker:
11730 User data passed to the tracing library by the marker call. In the
11731 UST backend, this is the format string passed as argument to the
11733 @item Static tracepoints probing the marker
11734 The list of static tracepoints attached to the marker.
11738 (@value{GDBP}) info static-tracepoint-markers
11739 Cnt ID Enb Address What
11740 1 ust/bar2 y 0x0000000000400e1a in main at stexample.c:25
11741 Data: number1 %d number2 %d
11742 Probed by static tracepoints: #2
11743 2 ust/bar33 n 0x0000000000400c87 in main at stexample.c:24
11749 @node Starting and Stopping Trace Experiments
11750 @subsection Starting and Stopping Trace Experiments
11753 @kindex tstart [ @var{notes} ]
11754 @cindex start a new trace experiment
11755 @cindex collected data discarded
11757 This command starts the trace experiment, and begins collecting data.
11758 It has the side effect of discarding all the data collected in the
11759 trace buffer during the previous trace experiment. If any arguments
11760 are supplied, they are taken as a note and stored with the trace
11761 experiment's state. The notes may be arbitrary text, and are
11762 especially useful with disconnected tracing in a multi-user context;
11763 the notes can explain what the trace is doing, supply user contact
11764 information, and so forth.
11766 @kindex tstop [ @var{notes} ]
11767 @cindex stop a running trace experiment
11769 This command stops the trace experiment. If any arguments are
11770 supplied, they are recorded with the experiment as a note. This is
11771 useful if you are stopping a trace started by someone else, for
11772 instance if the trace is interfering with the system's behavior and
11773 needs to be stopped quickly.
11775 @strong{Note}: a trace experiment and data collection may stop
11776 automatically if any tracepoint's passcount is reached
11777 (@pxref{Tracepoint Passcounts}), or if the trace buffer becomes full.
11780 @cindex status of trace data collection
11781 @cindex trace experiment, status of
11783 This command displays the status of the current trace data
11787 Here is an example of the commands we described so far:
11790 (@value{GDBP}) @b{trace gdb_c_test}
11791 (@value{GDBP}) @b{actions}
11792 Enter actions for tracepoint #1, one per line.
11793 > collect $regs,$locals,$args
11794 > while-stepping 11
11798 (@value{GDBP}) @b{tstart}
11799 [time passes @dots{}]
11800 (@value{GDBP}) @b{tstop}
11803 @anchor{disconnected tracing}
11804 @cindex disconnected tracing
11805 You can choose to continue running the trace experiment even if
11806 @value{GDBN} disconnects from the target, voluntarily or
11807 involuntarily. For commands such as @code{detach}, the debugger will
11808 ask what you want to do with the trace. But for unexpected
11809 terminations (@value{GDBN} crash, network outage), it would be
11810 unfortunate to lose hard-won trace data, so the variable
11811 @code{disconnected-tracing} lets you decide whether the trace should
11812 continue running without @value{GDBN}.
11815 @item set disconnected-tracing on
11816 @itemx set disconnected-tracing off
11817 @kindex set disconnected-tracing
11818 Choose whether a tracing run should continue to run if @value{GDBN}
11819 has disconnected from the target. Note that @code{detach} or
11820 @code{quit} will ask you directly what to do about a running trace no
11821 matter what this variable's setting, so the variable is mainly useful
11822 for handling unexpected situations, such as loss of the network.
11824 @item show disconnected-tracing
11825 @kindex show disconnected-tracing
11826 Show the current choice for disconnected tracing.
11830 When you reconnect to the target, the trace experiment may or may not
11831 still be running; it might have filled the trace buffer in the
11832 meantime, or stopped for one of the other reasons. If it is running,
11833 it will continue after reconnection.
11835 Upon reconnection, the target will upload information about the
11836 tracepoints in effect. @value{GDBN} will then compare that
11837 information to the set of tracepoints currently defined, and attempt
11838 to match them up, allowing for the possibility that the numbers may
11839 have changed due to creation and deletion in the meantime. If one of
11840 the target's tracepoints does not match any in @value{GDBN}, the
11841 debugger will create a new tracepoint, so that you have a number with
11842 which to specify that tracepoint. This matching-up process is
11843 necessarily heuristic, and it may result in useless tracepoints being
11844 created; you may simply delete them if they are of no use.
11846 @cindex circular trace buffer
11847 If your target agent supports a @dfn{circular trace buffer}, then you
11848 can run a trace experiment indefinitely without filling the trace
11849 buffer; when space runs out, the agent deletes already-collected trace
11850 frames, oldest first, until there is enough room to continue
11851 collecting. This is especially useful if your tracepoints are being
11852 hit too often, and your trace gets terminated prematurely because the
11853 buffer is full. To ask for a circular trace buffer, simply set
11854 @samp{circular-trace-buffer} to on. You can set this at any time,
11855 including during tracing; if the agent can do it, it will change
11856 buffer handling on the fly, otherwise it will not take effect until
11860 @item set circular-trace-buffer on
11861 @itemx set circular-trace-buffer off
11862 @kindex set circular-trace-buffer
11863 Choose whether a tracing run should use a linear or circular buffer
11864 for trace data. A linear buffer will not lose any trace data, but may
11865 fill up prematurely, while a circular buffer will discard old trace
11866 data, but it will have always room for the latest tracepoint hits.
11868 @item show circular-trace-buffer
11869 @kindex show circular-trace-buffer
11870 Show the current choice for the trace buffer. Note that this may not
11871 match the agent's current buffer handling, nor is it guaranteed to
11872 match the setting that might have been in effect during a past run,
11873 for instance if you are looking at frames from a trace file.
11878 @item set trace-buffer-size @var{n}
11879 @kindex set trace-buffer-size
11880 Request that the target use a trace buffer of @var{n} bytes. Not all
11881 targets will honor the request; they may have a compiled-in size for
11882 the trace buffer, or some other limitation. Set to a value of
11883 @code{-1} to let the target use whatever size it likes. This is also
11886 @item show trace-buffer-size
11887 @kindex show trace-buffer-size
11888 Show the current requested size for the trace buffer. Note that this
11889 will only match the actual size if the target supports size-setting,
11890 and was able to handle the requested size. For instance, if the
11891 target can only change buffer size between runs, this variable will
11892 not reflect the change until the next run starts. Use @code{tstatus}
11893 to get a report of the actual buffer size.
11897 @item set trace-user @var{text}
11898 @kindex set trace-user
11900 @item show trace-user
11901 @kindex show trace-user
11903 @item set trace-notes @var{text}
11904 @kindex set trace-notes
11905 Set the trace run's notes.
11907 @item show trace-notes
11908 @kindex show trace-notes
11909 Show the trace run's notes.
11911 @item set trace-stop-notes @var{text}
11912 @kindex set trace-stop-notes
11913 Set the trace run's stop notes. The handling of the note is as for
11914 @code{tstop} arguments; the set command is convenient way to fix a
11915 stop note that is mistaken or incomplete.
11917 @item show trace-stop-notes
11918 @kindex show trace-stop-notes
11919 Show the trace run's stop notes.
11923 @node Tracepoint Restrictions
11924 @subsection Tracepoint Restrictions
11926 @cindex tracepoint restrictions
11927 There are a number of restrictions on the use of tracepoints. As
11928 described above, tracepoint data gathering occurs on the target
11929 without interaction from @value{GDBN}. Thus the full capabilities of
11930 the debugger are not available during data gathering, and then at data
11931 examination time, you will be limited by only having what was
11932 collected. The following items describe some common problems, but it
11933 is not exhaustive, and you may run into additional difficulties not
11939 Tracepoint expressions are intended to gather objects (lvalues). Thus
11940 the full flexibility of GDB's expression evaluator is not available.
11941 You cannot call functions, cast objects to aggregate types, access
11942 convenience variables or modify values (except by assignment to trace
11943 state variables). Some language features may implicitly call
11944 functions (for instance Objective-C fields with accessors), and therefore
11945 cannot be collected either.
11948 Collection of local variables, either individually or in bulk with
11949 @code{$locals} or @code{$args}, during @code{while-stepping} may
11950 behave erratically. The stepping action may enter a new scope (for
11951 instance by stepping into a function), or the location of the variable
11952 may change (for instance it is loaded into a register). The
11953 tracepoint data recorded uses the location information for the
11954 variables that is correct for the tracepoint location. When the
11955 tracepoint is created, it is not possible, in general, to determine
11956 where the steps of a @code{while-stepping} sequence will advance the
11957 program---particularly if a conditional branch is stepped.
11960 Collection of an incompletely-initialized or partially-destroyed object
11961 may result in something that @value{GDBN} cannot display, or displays
11962 in a misleading way.
11965 When @value{GDBN} displays a pointer to character it automatically
11966 dereferences the pointer to also display characters of the string
11967 being pointed to. However, collecting the pointer during tracing does
11968 not automatically collect the string. You need to explicitly
11969 dereference the pointer and provide size information if you want to
11970 collect not only the pointer, but the memory pointed to. For example,
11971 @code{*ptr@@50} can be used to collect the 50 element array pointed to
11975 It is not possible to collect a complete stack backtrace at a
11976 tracepoint. Instead, you may collect the registers and a few hundred
11977 bytes from the stack pointer with something like @code{*(unsigned char *)$esp@@300}
11978 (adjust to use the name of the actual stack pointer register on your
11979 target architecture, and the amount of stack you wish to capture).
11980 Then the @code{backtrace} command will show a partial backtrace when
11981 using a trace frame. The number of stack frames that can be examined
11982 depends on the sizes of the frames in the collected stack. Note that
11983 if you ask for a block so large that it goes past the bottom of the
11984 stack, the target agent may report an error trying to read from an
11988 If you do not collect registers at a tracepoint, @value{GDBN} can
11989 infer that the value of @code{$pc} must be the same as the address of
11990 the tracepoint and use that when you are looking at a trace frame
11991 for that tracepoint. However, this cannot work if the tracepoint has
11992 multiple locations (for instance if it was set in a function that was
11993 inlined), or if it has a @code{while-stepping} loop. In those cases
11994 @value{GDBN} will warn you that it can't infer @code{$pc}, and default
11999 @node Analyze Collected Data
12000 @section Using the Collected Data
12002 After the tracepoint experiment ends, you use @value{GDBN} commands
12003 for examining the trace data. The basic idea is that each tracepoint
12004 collects a trace @dfn{snapshot} every time it is hit and another
12005 snapshot every time it single-steps. All these snapshots are
12006 consecutively numbered from zero and go into a buffer, and you can
12007 examine them later. The way you examine them is to @dfn{focus} on a
12008 specific trace snapshot. When the remote stub is focused on a trace
12009 snapshot, it will respond to all @value{GDBN} requests for memory and
12010 registers by reading from the buffer which belongs to that snapshot,
12011 rather than from @emph{real} memory or registers of the program being
12012 debugged. This means that @strong{all} @value{GDBN} commands
12013 (@code{print}, @code{info registers}, @code{backtrace}, etc.) will
12014 behave as if we were currently debugging the program state as it was
12015 when the tracepoint occurred. Any requests for data that are not in
12016 the buffer will fail.
12019 * tfind:: How to select a trace snapshot
12020 * tdump:: How to display all data for a snapshot
12021 * save tracepoints:: How to save tracepoints for a future run
12025 @subsection @code{tfind @var{n}}
12028 @cindex select trace snapshot
12029 @cindex find trace snapshot
12030 The basic command for selecting a trace snapshot from the buffer is
12031 @code{tfind @var{n}}, which finds trace snapshot number @var{n},
12032 counting from zero. If no argument @var{n} is given, the next
12033 snapshot is selected.
12035 Here are the various forms of using the @code{tfind} command.
12039 Find the first snapshot in the buffer. This is a synonym for
12040 @code{tfind 0} (since 0 is the number of the first snapshot).
12043 Stop debugging trace snapshots, resume @emph{live} debugging.
12046 Same as @samp{tfind none}.
12049 No argument means find the next trace snapshot.
12052 Find the previous trace snapshot before the current one. This permits
12053 retracing earlier steps.
12055 @item tfind tracepoint @var{num}
12056 Find the next snapshot associated with tracepoint @var{num}. Search
12057 proceeds forward from the last examined trace snapshot. If no
12058 argument @var{num} is given, it means find the next snapshot collected
12059 for the same tracepoint as the current snapshot.
12061 @item tfind pc @var{addr}
12062 Find the next snapshot associated with the value @var{addr} of the
12063 program counter. Search proceeds forward from the last examined trace
12064 snapshot. If no argument @var{addr} is given, it means find the next
12065 snapshot with the same value of PC as the current snapshot.
12067 @item tfind outside @var{addr1}, @var{addr2}
12068 Find the next snapshot whose PC is outside the given range of
12069 addresses (exclusive).
12071 @item tfind range @var{addr1}, @var{addr2}
12072 Find the next snapshot whose PC is between @var{addr1} and
12073 @var{addr2} (inclusive).
12075 @item tfind line @r{[}@var{file}:@r{]}@var{n}
12076 Find the next snapshot associated with the source line @var{n}. If
12077 the optional argument @var{file} is given, refer to line @var{n} in
12078 that source file. Search proceeds forward from the last examined
12079 trace snapshot. If no argument @var{n} is given, it means find the
12080 next line other than the one currently being examined; thus saying
12081 @code{tfind line} repeatedly can appear to have the same effect as
12082 stepping from line to line in a @emph{live} debugging session.
12085 The default arguments for the @code{tfind} commands are specifically
12086 designed to make it easy to scan through the trace buffer. For
12087 instance, @code{tfind} with no argument selects the next trace
12088 snapshot, and @code{tfind -} with no argument selects the previous
12089 trace snapshot. So, by giving one @code{tfind} command, and then
12090 simply hitting @key{RET} repeatedly you can examine all the trace
12091 snapshots in order. Or, by saying @code{tfind -} and then hitting
12092 @key{RET} repeatedly you can examine the snapshots in reverse order.
12093 The @code{tfind line} command with no argument selects the snapshot
12094 for the next source line executed. The @code{tfind pc} command with
12095 no argument selects the next snapshot with the same program counter
12096 (PC) as the current frame. The @code{tfind tracepoint} command with
12097 no argument selects the next trace snapshot collected by the same
12098 tracepoint as the current one.
12100 In addition to letting you scan through the trace buffer manually,
12101 these commands make it easy to construct @value{GDBN} scripts that
12102 scan through the trace buffer and print out whatever collected data
12103 you are interested in. Thus, if we want to examine the PC, FP, and SP
12104 registers from each trace frame in the buffer, we can say this:
12107 (@value{GDBP}) @b{tfind start}
12108 (@value{GDBP}) @b{while ($trace_frame != -1)}
12109 > printf "Frame %d, PC = %08X, SP = %08X, FP = %08X\n", \
12110 $trace_frame, $pc, $sp, $fp
12114 Frame 0, PC = 0020DC64, SP = 0030BF3C, FP = 0030BF44
12115 Frame 1, PC = 0020DC6C, SP = 0030BF38, FP = 0030BF44
12116 Frame 2, PC = 0020DC70, SP = 0030BF34, FP = 0030BF44
12117 Frame 3, PC = 0020DC74, SP = 0030BF30, FP = 0030BF44
12118 Frame 4, PC = 0020DC78, SP = 0030BF2C, FP = 0030BF44
12119 Frame 5, PC = 0020DC7C, SP = 0030BF28, FP = 0030BF44
12120 Frame 6, PC = 0020DC80, SP = 0030BF24, FP = 0030BF44
12121 Frame 7, PC = 0020DC84, SP = 0030BF20, FP = 0030BF44
12122 Frame 8, PC = 0020DC88, SP = 0030BF1C, FP = 0030BF44
12123 Frame 9, PC = 0020DC8E, SP = 0030BF18, FP = 0030BF44
12124 Frame 10, PC = 00203F6C, SP = 0030BE3C, FP = 0030BF14
12127 Or, if we want to examine the variable @code{X} at each source line in
12131 (@value{GDBP}) @b{tfind start}
12132 (@value{GDBP}) @b{while ($trace_frame != -1)}
12133 > printf "Frame %d, X == %d\n", $trace_frame, X
12143 @subsection @code{tdump}
12145 @cindex dump all data collected at tracepoint
12146 @cindex tracepoint data, display
12148 This command takes no arguments. It prints all the data collected at
12149 the current trace snapshot.
12152 (@value{GDBP}) @b{trace 444}
12153 (@value{GDBP}) @b{actions}
12154 Enter actions for tracepoint #2, one per line:
12155 > collect $regs, $locals, $args, gdb_long_test
12158 (@value{GDBP}) @b{tstart}
12160 (@value{GDBP}) @b{tfind line 444}
12161 #0 gdb_test (p1=0x11, p2=0x22, p3=0x33, p4=0x44, p5=0x55, p6=0x66)
12163 444 printp( "%s: arguments = 0x%X 0x%X 0x%X 0x%X 0x%X 0x%X\n", )
12165 (@value{GDBP}) @b{tdump}
12166 Data collected at tracepoint 2, trace frame 1:
12167 d0 0xc4aa0085 -995491707
12171 d4 0x71aea3d 119204413
12174 d7 0x380035 3670069
12175 a0 0x19e24a 1696330
12176 a1 0x3000668 50333288
12178 a3 0x322000 3284992
12179 a4 0x3000698 50333336
12180 a5 0x1ad3cc 1758156
12181 fp 0x30bf3c 0x30bf3c
12182 sp 0x30bf34 0x30bf34
12184 pc 0x20b2c8 0x20b2c8
12188 p = 0x20e5b4 "gdb-test"
12195 gdb_long_test = 17 '\021'
12200 @code{tdump} works by scanning the tracepoint's current collection
12201 actions and printing the value of each expression listed. So
12202 @code{tdump} can fail, if after a run, you change the tracepoint's
12203 actions to mention variables that were not collected during the run.
12205 Also, for tracepoints with @code{while-stepping} loops, @code{tdump}
12206 uses the collected value of @code{$pc} to distinguish between trace
12207 frames that were collected at the tracepoint hit, and frames that were
12208 collected while stepping. This allows it to correctly choose whether
12209 to display the basic list of collections, or the collections from the
12210 body of the while-stepping loop. However, if @code{$pc} was not collected,
12211 then @code{tdump} will always attempt to dump using the basic collection
12212 list, and may fail if a while-stepping frame does not include all the
12213 same data that is collected at the tracepoint hit.
12214 @c This is getting pretty arcane, example would be good.
12216 @node save tracepoints
12217 @subsection @code{save tracepoints @var{filename}}
12218 @kindex save tracepoints
12219 @kindex save-tracepoints
12220 @cindex save tracepoints for future sessions
12222 This command saves all current tracepoint definitions together with
12223 their actions and passcounts, into a file @file{@var{filename}}
12224 suitable for use in a later debugging session. To read the saved
12225 tracepoint definitions, use the @code{source} command (@pxref{Command
12226 Files}). The @w{@code{save-tracepoints}} command is a deprecated
12227 alias for @w{@code{save tracepoints}}
12229 @node Tracepoint Variables
12230 @section Convenience Variables for Tracepoints
12231 @cindex tracepoint variables
12232 @cindex convenience variables for tracepoints
12235 @vindex $trace_frame
12236 @item (int) $trace_frame
12237 The current trace snapshot (a.k.a.@: @dfn{frame}) number, or -1 if no
12238 snapshot is selected.
12240 @vindex $tracepoint
12241 @item (int) $tracepoint
12242 The tracepoint for the current trace snapshot.
12244 @vindex $trace_line
12245 @item (int) $trace_line
12246 The line number for the current trace snapshot.
12248 @vindex $trace_file
12249 @item (char []) $trace_file
12250 The source file for the current trace snapshot.
12252 @vindex $trace_func
12253 @item (char []) $trace_func
12254 The name of the function containing @code{$tracepoint}.
12257 Note: @code{$trace_file} is not suitable for use in @code{printf},
12258 use @code{output} instead.
12260 Here's a simple example of using these convenience variables for
12261 stepping through all the trace snapshots and printing some of their
12262 data. Note that these are not the same as trace state variables,
12263 which are managed by the target.
12266 (@value{GDBP}) @b{tfind start}
12268 (@value{GDBP}) @b{while $trace_frame != -1}
12269 > output $trace_file
12270 > printf ", line %d (tracepoint #%d)\n", $trace_line, $tracepoint
12276 @section Using Trace Files
12277 @cindex trace files
12279 In some situations, the target running a trace experiment may no
12280 longer be available; perhaps it crashed, or the hardware was needed
12281 for a different activity. To handle these cases, you can arrange to
12282 dump the trace data into a file, and later use that file as a source
12283 of trace data, via the @code{target tfile} command.
12288 @item tsave [ -r ] @var{filename}
12289 @itemx tsave [-ctf] @var{dirname}
12290 Save the trace data to @var{filename}. By default, this command
12291 assumes that @var{filename} refers to the host filesystem, so if
12292 necessary @value{GDBN} will copy raw trace data up from the target and
12293 then save it. If the target supports it, you can also supply the
12294 optional argument @code{-r} (``remote'') to direct the target to save
12295 the data directly into @var{filename} in its own filesystem, which may be
12296 more efficient if the trace buffer is very large. (Note, however, that
12297 @code{target tfile} can only read from files accessible to the host.)
12298 By default, this command will save trace frame in tfile format.
12299 You can supply the optional argument @code{-ctf} to save date in CTF
12300 format. The @dfn{Common Trace Format} (CTF) is proposed as a trace format
12301 that can be shared by multiple debugging and tracing tools. Please go to
12302 @indicateurl{http://www.efficios.com/ctf} to get more information.
12304 @kindex target tfile
12306 @item target tfile @var{filename}
12307 Use the file named @var{filename} as a source of trace data. Commands
12308 that examine data work as they do with a live target, but it is not
12309 possible to run any new trace experiments. @code{tstatus} will report
12310 the state of the trace run at the moment the data was saved, as well
12311 as the current trace frame you are examining. @var{filename} must be
12312 on a filesystem accessible to the host.
12317 @chapter Debugging Programs That Use Overlays
12320 If your program is too large to fit completely in your target system's
12321 memory, you can sometimes use @dfn{overlays} to work around this
12322 problem. @value{GDBN} provides some support for debugging programs that
12326 * How Overlays Work:: A general explanation of overlays.
12327 * Overlay Commands:: Managing overlays in @value{GDBN}.
12328 * Automatic Overlay Debugging:: @value{GDBN} can find out which overlays are
12329 mapped by asking the inferior.
12330 * Overlay Sample Program:: A sample program using overlays.
12333 @node How Overlays Work
12334 @section How Overlays Work
12335 @cindex mapped overlays
12336 @cindex unmapped overlays
12337 @cindex load address, overlay's
12338 @cindex mapped address
12339 @cindex overlay area
12341 Suppose you have a computer whose instruction address space is only 64
12342 kilobytes long, but which has much more memory which can be accessed by
12343 other means: special instructions, segment registers, or memory
12344 management hardware, for example. Suppose further that you want to
12345 adapt a program which is larger than 64 kilobytes to run on this system.
12347 One solution is to identify modules of your program which are relatively
12348 independent, and need not call each other directly; call these modules
12349 @dfn{overlays}. Separate the overlays from the main program, and place
12350 their machine code in the larger memory. Place your main program in
12351 instruction memory, but leave at least enough space there to hold the
12352 largest overlay as well.
12354 Now, to call a function located in an overlay, you must first copy that
12355 overlay's machine code from the large memory into the space set aside
12356 for it in the instruction memory, and then jump to its entry point
12359 @c NB: In the below the mapped area's size is greater or equal to the
12360 @c size of all overlays. This is intentional to remind the developer
12361 @c that overlays don't necessarily need to be the same size.
12365 Data Instruction Larger
12366 Address Space Address Space Address Space
12367 +-----------+ +-----------+ +-----------+
12369 +-----------+ +-----------+ +-----------+<-- overlay 1
12370 | program | | main | .----| overlay 1 | load address
12371 | variables | | program | | +-----------+
12372 | and heap | | | | | |
12373 +-----------+ | | | +-----------+<-- overlay 2
12374 | | +-----------+ | | | load address
12375 +-----------+ | | | .-| overlay 2 |
12377 mapped --->+-----------+ | | +-----------+
12378 address | | | | | |
12379 | overlay | <-' | | |
12380 | area | <---' +-----------+<-- overlay 3
12381 | | <---. | | load address
12382 +-----------+ `--| overlay 3 |
12389 @anchor{A code overlay}A code overlay
12393 The diagram (@pxref{A code overlay}) shows a system with separate data
12394 and instruction address spaces. To map an overlay, the program copies
12395 its code from the larger address space to the instruction address space.
12396 Since the overlays shown here all use the same mapped address, only one
12397 may be mapped at a time. For a system with a single address space for
12398 data and instructions, the diagram would be similar, except that the
12399 program variables and heap would share an address space with the main
12400 program and the overlay area.
12402 An overlay loaded into instruction memory and ready for use is called a
12403 @dfn{mapped} overlay; its @dfn{mapped address} is its address in the
12404 instruction memory. An overlay not present (or only partially present)
12405 in instruction memory is called @dfn{unmapped}; its @dfn{load address}
12406 is its address in the larger memory. The mapped address is also called
12407 the @dfn{virtual memory address}, or @dfn{VMA}; the load address is also
12408 called the @dfn{load memory address}, or @dfn{LMA}.
12410 Unfortunately, overlays are not a completely transparent way to adapt a
12411 program to limited instruction memory. They introduce a new set of
12412 global constraints you must keep in mind as you design your program:
12417 Before calling or returning to a function in an overlay, your program
12418 must make sure that overlay is actually mapped. Otherwise, the call or
12419 return will transfer control to the right address, but in the wrong
12420 overlay, and your program will probably crash.
12423 If the process of mapping an overlay is expensive on your system, you
12424 will need to choose your overlays carefully to minimize their effect on
12425 your program's performance.
12428 The executable file you load onto your system must contain each
12429 overlay's instructions, appearing at the overlay's load address, not its
12430 mapped address. However, each overlay's instructions must be relocated
12431 and its symbols defined as if the overlay were at its mapped address.
12432 You can use GNU linker scripts to specify different load and relocation
12433 addresses for pieces of your program; see @ref{Overlay Description,,,
12434 ld.info, Using ld: the GNU linker}.
12437 The procedure for loading executable files onto your system must be able
12438 to load their contents into the larger address space as well as the
12439 instruction and data spaces.
12443 The overlay system described above is rather simple, and could be
12444 improved in many ways:
12449 If your system has suitable bank switch registers or memory management
12450 hardware, you could use those facilities to make an overlay's load area
12451 contents simply appear at their mapped address in instruction space.
12452 This would probably be faster than copying the overlay to its mapped
12453 area in the usual way.
12456 If your overlays are small enough, you could set aside more than one
12457 overlay area, and have more than one overlay mapped at a time.
12460 You can use overlays to manage data, as well as instructions. In
12461 general, data overlays are even less transparent to your design than
12462 code overlays: whereas code overlays only require care when you call or
12463 return to functions, data overlays require care every time you access
12464 the data. Also, if you change the contents of a data overlay, you
12465 must copy its contents back out to its load address before you can copy a
12466 different data overlay into the same mapped area.
12471 @node Overlay Commands
12472 @section Overlay Commands
12474 To use @value{GDBN}'s overlay support, each overlay in your program must
12475 correspond to a separate section of the executable file. The section's
12476 virtual memory address and load memory address must be the overlay's
12477 mapped and load addresses. Identifying overlays with sections allows
12478 @value{GDBN} to determine the appropriate address of a function or
12479 variable, depending on whether the overlay is mapped or not.
12481 @value{GDBN}'s overlay commands all start with the word @code{overlay};
12482 you can abbreviate this as @code{ov} or @code{ovly}. The commands are:
12487 Disable @value{GDBN}'s overlay support. When overlay support is
12488 disabled, @value{GDBN} assumes that all functions and variables are
12489 always present at their mapped addresses. By default, @value{GDBN}'s
12490 overlay support is disabled.
12492 @item overlay manual
12493 @cindex manual overlay debugging
12494 Enable @dfn{manual} overlay debugging. In this mode, @value{GDBN}
12495 relies on you to tell it which overlays are mapped, and which are not,
12496 using the @code{overlay map-overlay} and @code{overlay unmap-overlay}
12497 commands described below.
12499 @item overlay map-overlay @var{overlay}
12500 @itemx overlay map @var{overlay}
12501 @cindex map an overlay
12502 Tell @value{GDBN} that @var{overlay} is now mapped; @var{overlay} must
12503 be the name of the object file section containing the overlay. When an
12504 overlay is mapped, @value{GDBN} assumes it can find the overlay's
12505 functions and variables at their mapped addresses. @value{GDBN} assumes
12506 that any other overlays whose mapped ranges overlap that of
12507 @var{overlay} are now unmapped.
12509 @item overlay unmap-overlay @var{overlay}
12510 @itemx overlay unmap @var{overlay}
12511 @cindex unmap an overlay
12512 Tell @value{GDBN} that @var{overlay} is no longer mapped; @var{overlay}
12513 must be the name of the object file section containing the overlay.
12514 When an overlay is unmapped, @value{GDBN} assumes it can find the
12515 overlay's functions and variables at their load addresses.
12518 Enable @dfn{automatic} overlay debugging. In this mode, @value{GDBN}
12519 consults a data structure the overlay manager maintains in the inferior
12520 to see which overlays are mapped. For details, see @ref{Automatic
12521 Overlay Debugging}.
12523 @item overlay load-target
12524 @itemx overlay load
12525 @cindex reloading the overlay table
12526 Re-read the overlay table from the inferior. Normally, @value{GDBN}
12527 re-reads the table @value{GDBN} automatically each time the inferior
12528 stops, so this command should only be necessary if you have changed the
12529 overlay mapping yourself using @value{GDBN}. This command is only
12530 useful when using automatic overlay debugging.
12532 @item overlay list-overlays
12533 @itemx overlay list
12534 @cindex listing mapped overlays
12535 Display a list of the overlays currently mapped, along with their mapped
12536 addresses, load addresses, and sizes.
12540 Normally, when @value{GDBN} prints a code address, it includes the name
12541 of the function the address falls in:
12544 (@value{GDBP}) print main
12545 $3 = @{int ()@} 0x11a0 <main>
12548 When overlay debugging is enabled, @value{GDBN} recognizes code in
12549 unmapped overlays, and prints the names of unmapped functions with
12550 asterisks around them. For example, if @code{foo} is a function in an
12551 unmapped overlay, @value{GDBN} prints it this way:
12554 (@value{GDBP}) overlay list
12555 No sections are mapped.
12556 (@value{GDBP}) print foo
12557 $5 = @{int (int)@} 0x100000 <*foo*>
12560 When @code{foo}'s overlay is mapped, @value{GDBN} prints the function's
12564 (@value{GDBP}) overlay list
12565 Section .ov.foo.text, loaded at 0x100000 - 0x100034,
12566 mapped at 0x1016 - 0x104a
12567 (@value{GDBP}) print foo
12568 $6 = @{int (int)@} 0x1016 <foo>
12571 When overlay debugging is enabled, @value{GDBN} can find the correct
12572 address for functions and variables in an overlay, whether or not the
12573 overlay is mapped. This allows most @value{GDBN} commands, like
12574 @code{break} and @code{disassemble}, to work normally, even on unmapped
12575 code. However, @value{GDBN}'s breakpoint support has some limitations:
12579 @cindex breakpoints in overlays
12580 @cindex overlays, setting breakpoints in
12581 You can set breakpoints in functions in unmapped overlays, as long as
12582 @value{GDBN} can write to the overlay at its load address.
12584 @value{GDBN} can not set hardware or simulator-based breakpoints in
12585 unmapped overlays. However, if you set a breakpoint at the end of your
12586 overlay manager (and tell @value{GDBN} which overlays are now mapped, if
12587 you are using manual overlay management), @value{GDBN} will re-set its
12588 breakpoints properly.
12592 @node Automatic Overlay Debugging
12593 @section Automatic Overlay Debugging
12594 @cindex automatic overlay debugging
12596 @value{GDBN} can automatically track which overlays are mapped and which
12597 are not, given some simple co-operation from the overlay manager in the
12598 inferior. If you enable automatic overlay debugging with the
12599 @code{overlay auto} command (@pxref{Overlay Commands}), @value{GDBN}
12600 looks in the inferior's memory for certain variables describing the
12601 current state of the overlays.
12603 Here are the variables your overlay manager must define to support
12604 @value{GDBN}'s automatic overlay debugging:
12608 @item @code{_ovly_table}:
12609 This variable must be an array of the following structures:
12614 /* The overlay's mapped address. */
12617 /* The size of the overlay, in bytes. */
12618 unsigned long size;
12620 /* The overlay's load address. */
12623 /* Non-zero if the overlay is currently mapped;
12625 unsigned long mapped;
12629 @item @code{_novlys}:
12630 This variable must be a four-byte signed integer, holding the total
12631 number of elements in @code{_ovly_table}.
12635 To decide whether a particular overlay is mapped or not, @value{GDBN}
12636 looks for an entry in @w{@code{_ovly_table}} whose @code{vma} and
12637 @code{lma} members equal the VMA and LMA of the overlay's section in the
12638 executable file. When @value{GDBN} finds a matching entry, it consults
12639 the entry's @code{mapped} member to determine whether the overlay is
12642 In addition, your overlay manager may define a function called
12643 @code{_ovly_debug_event}. If this function is defined, @value{GDBN}
12644 will silently set a breakpoint there. If the overlay manager then
12645 calls this function whenever it has changed the overlay table, this
12646 will enable @value{GDBN} to accurately keep track of which overlays
12647 are in program memory, and update any breakpoints that may be set
12648 in overlays. This will allow breakpoints to work even if the
12649 overlays are kept in ROM or other non-writable memory while they
12650 are not being executed.
12652 @node Overlay Sample Program
12653 @section Overlay Sample Program
12654 @cindex overlay example program
12656 When linking a program which uses overlays, you must place the overlays
12657 at their load addresses, while relocating them to run at their mapped
12658 addresses. To do this, you must write a linker script (@pxref{Overlay
12659 Description,,, ld.info, Using ld: the GNU linker}). Unfortunately,
12660 since linker scripts are specific to a particular host system, target
12661 architecture, and target memory layout, this manual cannot provide
12662 portable sample code demonstrating @value{GDBN}'s overlay support.
12664 However, the @value{GDBN} source distribution does contain an overlaid
12665 program, with linker scripts for a few systems, as part of its test
12666 suite. The program consists of the following files from
12667 @file{gdb/testsuite/gdb.base}:
12671 The main program file.
12673 A simple overlay manager, used by @file{overlays.c}.
12678 Overlay modules, loaded and used by @file{overlays.c}.
12681 Linker scripts for linking the test program on the @code{d10v-elf}
12682 and @code{m32r-elf} targets.
12685 You can build the test program using the @code{d10v-elf} GCC
12686 cross-compiler like this:
12689 $ d10v-elf-gcc -g -c overlays.c
12690 $ d10v-elf-gcc -g -c ovlymgr.c
12691 $ d10v-elf-gcc -g -c foo.c
12692 $ d10v-elf-gcc -g -c bar.c
12693 $ d10v-elf-gcc -g -c baz.c
12694 $ d10v-elf-gcc -g -c grbx.c
12695 $ d10v-elf-gcc -g overlays.o ovlymgr.o foo.o bar.o \
12696 baz.o grbx.o -Wl,-Td10v.ld -o overlays
12699 The build process is identical for any other architecture, except that
12700 you must substitute the appropriate compiler and linker script for the
12701 target system for @code{d10v-elf-gcc} and @code{d10v.ld}.
12705 @chapter Using @value{GDBN} with Different Languages
12708 Although programming languages generally have common aspects, they are
12709 rarely expressed in the same manner. For instance, in ANSI C,
12710 dereferencing a pointer @code{p} is accomplished by @code{*p}, but in
12711 Modula-2, it is accomplished by @code{p^}. Values can also be
12712 represented (and displayed) differently. Hex numbers in C appear as
12713 @samp{0x1ae}, while in Modula-2 they appear as @samp{1AEH}.
12715 @cindex working language
12716 Language-specific information is built into @value{GDBN} for some languages,
12717 allowing you to express operations like the above in your program's
12718 native language, and allowing @value{GDBN} to output values in a manner
12719 consistent with the syntax of your program's native language. The
12720 language you use to build expressions is called the @dfn{working
12724 * Setting:: Switching between source languages
12725 * Show:: Displaying the language
12726 * Checks:: Type and range checks
12727 * Supported Languages:: Supported languages
12728 * Unsupported Languages:: Unsupported languages
12732 @section Switching Between Source Languages
12734 There are two ways to control the working language---either have @value{GDBN}
12735 set it automatically, or select it manually yourself. You can use the
12736 @code{set language} command for either purpose. On startup, @value{GDBN}
12737 defaults to setting the language automatically. The working language is
12738 used to determine how expressions you type are interpreted, how values
12741 In addition to the working language, every source file that
12742 @value{GDBN} knows about has its own working language. For some object
12743 file formats, the compiler might indicate which language a particular
12744 source file is in. However, most of the time @value{GDBN} infers the
12745 language from the name of the file. The language of a source file
12746 controls whether C@t{++} names are demangled---this way @code{backtrace} can
12747 show each frame appropriately for its own language. There is no way to
12748 set the language of a source file from within @value{GDBN}, but you can
12749 set the language associated with a filename extension. @xref{Show, ,
12750 Displaying the Language}.
12752 This is most commonly a problem when you use a program, such
12753 as @code{cfront} or @code{f2c}, that generates C but is written in
12754 another language. In that case, make the
12755 program use @code{#line} directives in its C output; that way
12756 @value{GDBN} will know the correct language of the source code of the original
12757 program, and will display that source code, not the generated C code.
12760 * Filenames:: Filename extensions and languages.
12761 * Manually:: Setting the working language manually
12762 * Automatically:: Having @value{GDBN} infer the source language
12766 @subsection List of Filename Extensions and Languages
12768 If a source file name ends in one of the following extensions, then
12769 @value{GDBN} infers that its language is the one indicated.
12787 C@t{++} source file
12793 Objective-C source file
12797 Fortran source file
12800 Modula-2 source file
12804 Assembler source file. This actually behaves almost like C, but
12805 @value{GDBN} does not skip over function prologues when stepping.
12808 In addition, you may set the language associated with a filename
12809 extension. @xref{Show, , Displaying the Language}.
12812 @subsection Setting the Working Language
12814 If you allow @value{GDBN} to set the language automatically,
12815 expressions are interpreted the same way in your debugging session and
12818 @kindex set language
12819 If you wish, you may set the language manually. To do this, issue the
12820 command @samp{set language @var{lang}}, where @var{lang} is the name of
12821 a language, such as
12822 @code{c} or @code{modula-2}.
12823 For a list of the supported languages, type @samp{set language}.
12825 Setting the language manually prevents @value{GDBN} from updating the working
12826 language automatically. This can lead to confusion if you try
12827 to debug a program when the working language is not the same as the
12828 source language, when an expression is acceptable to both
12829 languages---but means different things. For instance, if the current
12830 source file were written in C, and @value{GDBN} was parsing Modula-2, a
12838 might not have the effect you intended. In C, this means to add
12839 @code{b} and @code{c} and place the result in @code{a}. The result
12840 printed would be the value of @code{a}. In Modula-2, this means to compare
12841 @code{a} to the result of @code{b+c}, yielding a @code{BOOLEAN} value.
12843 @node Automatically
12844 @subsection Having @value{GDBN} Infer the Source Language
12846 To have @value{GDBN} set the working language automatically, use
12847 @samp{set language local} or @samp{set language auto}. @value{GDBN}
12848 then infers the working language. That is, when your program stops in a
12849 frame (usually by encountering a breakpoint), @value{GDBN} sets the
12850 working language to the language recorded for the function in that
12851 frame. If the language for a frame is unknown (that is, if the function
12852 or block corresponding to the frame was defined in a source file that
12853 does not have a recognized extension), the current working language is
12854 not changed, and @value{GDBN} issues a warning.
12856 This may not seem necessary for most programs, which are written
12857 entirely in one source language. However, program modules and libraries
12858 written in one source language can be used by a main program written in
12859 a different source language. Using @samp{set language auto} in this
12860 case frees you from having to set the working language manually.
12863 @section Displaying the Language
12865 The following commands help you find out which language is the
12866 working language, and also what language source files were written in.
12869 @item show language
12870 @kindex show language
12871 Display the current working language. This is the
12872 language you can use with commands such as @code{print} to
12873 build and compute expressions that may involve variables in your program.
12876 @kindex info frame@r{, show the source language}
12877 Display the source language for this frame. This language becomes the
12878 working language if you use an identifier from this frame.
12879 @xref{Frame Info, ,Information about a Frame}, to identify the other
12880 information listed here.
12883 @kindex info source@r{, show the source language}
12884 Display the source language of this source file.
12885 @xref{Symbols, ,Examining the Symbol Table}, to identify the other
12886 information listed here.
12889 In unusual circumstances, you may have source files with extensions
12890 not in the standard list. You can then set the extension associated
12891 with a language explicitly:
12894 @item set extension-language @var{ext} @var{language}
12895 @kindex set extension-language
12896 Tell @value{GDBN} that source files with extension @var{ext} are to be
12897 assumed as written in the source language @var{language}.
12899 @item info extensions
12900 @kindex info extensions
12901 List all the filename extensions and the associated languages.
12905 @section Type and Range Checking
12907 Some languages are designed to guard you against making seemingly common
12908 errors through a series of compile- and run-time checks. These include
12909 checking the type of arguments to functions and operators and making
12910 sure mathematical overflows are caught at run time. Checks such as
12911 these help to ensure a program's correctness once it has been compiled
12912 by eliminating type mismatches and providing active checks for range
12913 errors when your program is running.
12915 By default @value{GDBN} checks for these errors according to the
12916 rules of the current source language. Although @value{GDBN} does not check
12917 the statements in your program, it can check expressions entered directly
12918 into @value{GDBN} for evaluation via the @code{print} command, for example.
12921 * Type Checking:: An overview of type checking
12922 * Range Checking:: An overview of range checking
12925 @cindex type checking
12926 @cindex checks, type
12927 @node Type Checking
12928 @subsection An Overview of Type Checking
12930 Some languages, such as C and C@t{++}, are strongly typed, meaning that the
12931 arguments to operators and functions have to be of the correct type,
12932 otherwise an error occurs. These checks prevent type mismatch
12933 errors from ever causing any run-time problems. For example,
12936 int klass::my_method(char *b) @{ return b ? 1 : 2; @}
12938 (@value{GDBP}) print obj.my_method (0)
12941 (@value{GDBP}) print obj.my_method (0x1234)
12942 Cannot resolve method klass::my_method to any overloaded instance
12945 The second example fails because in C@t{++} the integer constant
12946 @samp{0x1234} is not type-compatible with the pointer parameter type.
12948 For the expressions you use in @value{GDBN} commands, you can tell
12949 @value{GDBN} to not enforce strict type checking or
12950 to treat any mismatches as errors and abandon the expression;
12951 When type checking is disabled, @value{GDBN} successfully evaluates
12952 expressions like the second example above.
12954 Even if type checking is off, there may be other reasons
12955 related to type that prevent @value{GDBN} from evaluating an expression.
12956 For instance, @value{GDBN} does not know how to add an @code{int} and
12957 a @code{struct foo}. These particular type errors have nothing to do
12958 with the language in use and usually arise from expressions which make
12959 little sense to evaluate anyway.
12961 @value{GDBN} provides some additional commands for controlling type checking:
12963 @kindex set check type
12964 @kindex show check type
12966 @item set check type on
12967 @itemx set check type off
12968 Set strict type checking on or off. If any type mismatches occur in
12969 evaluating an expression while type checking is on, @value{GDBN} prints a
12970 message and aborts evaluation of the expression.
12972 @item show check type
12973 Show the current setting of type checking and whether @value{GDBN}
12974 is enforcing strict type checking rules.
12977 @cindex range checking
12978 @cindex checks, range
12979 @node Range Checking
12980 @subsection An Overview of Range Checking
12982 In some languages (such as Modula-2), it is an error to exceed the
12983 bounds of a type; this is enforced with run-time checks. Such range
12984 checking is meant to ensure program correctness by making sure
12985 computations do not overflow, or indices on an array element access do
12986 not exceed the bounds of the array.
12988 For expressions you use in @value{GDBN} commands, you can tell
12989 @value{GDBN} to treat range errors in one of three ways: ignore them,
12990 always treat them as errors and abandon the expression, or issue
12991 warnings but evaluate the expression anyway.
12993 A range error can result from numerical overflow, from exceeding an
12994 array index bound, or when you type a constant that is not a member
12995 of any type. Some languages, however, do not treat overflows as an
12996 error. In many implementations of C, mathematical overflow causes the
12997 result to ``wrap around'' to lower values---for example, if @var{m} is
12998 the largest integer value, and @var{s} is the smallest, then
13001 @var{m} + 1 @result{} @var{s}
13004 This, too, is specific to individual languages, and in some cases
13005 specific to individual compilers or machines. @xref{Supported Languages, ,
13006 Supported Languages}, for further details on specific languages.
13008 @value{GDBN} provides some additional commands for controlling the range checker:
13010 @kindex set check range
13011 @kindex show check range
13013 @item set check range auto
13014 Set range checking on or off based on the current working language.
13015 @xref{Supported Languages, ,Supported Languages}, for the default settings for
13018 @item set check range on
13019 @itemx set check range off
13020 Set range checking on or off, overriding the default setting for the
13021 current working language. A warning is issued if the setting does not
13022 match the language default. If a range error occurs and range checking is on,
13023 then a message is printed and evaluation of the expression is aborted.
13025 @item set check range warn
13026 Output messages when the @value{GDBN} range checker detects a range error,
13027 but attempt to evaluate the expression anyway. Evaluating the
13028 expression may still be impossible for other reasons, such as accessing
13029 memory that the process does not own (a typical example from many Unix
13033 Show the current setting of the range checker, and whether or not it is
13034 being set automatically by @value{GDBN}.
13037 @node Supported Languages
13038 @section Supported Languages
13040 @value{GDBN} supports C, C@t{++}, D, Go, Objective-C, Fortran, Java,
13041 OpenCL C, Pascal, assembly, Modula-2, and Ada.
13042 @c This is false ...
13043 Some @value{GDBN} features may be used in expressions regardless of the
13044 language you use: the @value{GDBN} @code{@@} and @code{::} operators,
13045 and the @samp{@{type@}addr} construct (@pxref{Expressions,
13046 ,Expressions}) can be used with the constructs of any supported
13049 The following sections detail to what degree each source language is
13050 supported by @value{GDBN}. These sections are not meant to be language
13051 tutorials or references, but serve only as a reference guide to what the
13052 @value{GDBN} expression parser accepts, and what input and output
13053 formats should look like for different languages. There are many good
13054 books written on each of these languages; please look to these for a
13055 language reference or tutorial.
13058 * C:: C and C@t{++}
13061 * Objective-C:: Objective-C
13062 * OpenCL C:: OpenCL C
13063 * Fortran:: Fortran
13065 * Modula-2:: Modula-2
13070 @subsection C and C@t{++}
13072 @cindex C and C@t{++}
13073 @cindex expressions in C or C@t{++}
13075 Since C and C@t{++} are so closely related, many features of @value{GDBN} apply
13076 to both languages. Whenever this is the case, we discuss those languages
13080 @cindex @code{g++}, @sc{gnu} C@t{++} compiler
13081 @cindex @sc{gnu} C@t{++}
13082 The C@t{++} debugging facilities are jointly implemented by the C@t{++}
13083 compiler and @value{GDBN}. Therefore, to debug your C@t{++} code
13084 effectively, you must compile your C@t{++} programs with a supported
13085 C@t{++} compiler, such as @sc{gnu} @code{g++}, or the HP ANSI C@t{++}
13086 compiler (@code{aCC}).
13089 * C Operators:: C and C@t{++} operators
13090 * C Constants:: C and C@t{++} constants
13091 * C Plus Plus Expressions:: C@t{++} expressions
13092 * C Defaults:: Default settings for C and C@t{++}
13093 * C Checks:: C and C@t{++} type and range checks
13094 * Debugging C:: @value{GDBN} and C
13095 * Debugging C Plus Plus:: @value{GDBN} features for C@t{++}
13096 * Decimal Floating Point:: Numbers in Decimal Floating Point format
13100 @subsubsection C and C@t{++} Operators
13102 @cindex C and C@t{++} operators
13104 Operators must be defined on values of specific types. For instance,
13105 @code{+} is defined on numbers, but not on structures. Operators are
13106 often defined on groups of types.
13108 For the purposes of C and C@t{++}, the following definitions hold:
13113 @emph{Integral types} include @code{int} with any of its storage-class
13114 specifiers; @code{char}; @code{enum}; and, for C@t{++}, @code{bool}.
13117 @emph{Floating-point types} include @code{float}, @code{double}, and
13118 @code{long double} (if supported by the target platform).
13121 @emph{Pointer types} include all types defined as @code{(@var{type} *)}.
13124 @emph{Scalar types} include all of the above.
13129 The following operators are supported. They are listed here
13130 in order of increasing precedence:
13134 The comma or sequencing operator. Expressions in a comma-separated list
13135 are evaluated from left to right, with the result of the entire
13136 expression being the last expression evaluated.
13139 Assignment. The value of an assignment expression is the value
13140 assigned. Defined on scalar types.
13143 Used in an expression of the form @w{@code{@var{a} @var{op}= @var{b}}},
13144 and translated to @w{@code{@var{a} = @var{a op b}}}.
13145 @w{@code{@var{op}=}} and @code{=} have the same precedence.
13146 @var{op} is any one of the operators @code{|}, @code{^}, @code{&},
13147 @code{<<}, @code{>>}, @code{+}, @code{-}, @code{*}, @code{/}, @code{%}.
13150 The ternary operator. @code{@var{a} ? @var{b} : @var{c}} can be thought
13151 of as: if @var{a} then @var{b} else @var{c}. @var{a} should be of an
13155 Logical @sc{or}. Defined on integral types.
13158 Logical @sc{and}. Defined on integral types.
13161 Bitwise @sc{or}. Defined on integral types.
13164 Bitwise exclusive-@sc{or}. Defined on integral types.
13167 Bitwise @sc{and}. Defined on integral types.
13170 Equality and inequality. Defined on scalar types. The value of these
13171 expressions is 0 for false and non-zero for true.
13173 @item <@r{, }>@r{, }<=@r{, }>=
13174 Less than, greater than, less than or equal, greater than or equal.
13175 Defined on scalar types. The value of these expressions is 0 for false
13176 and non-zero for true.
13179 left shift, and right shift. Defined on integral types.
13182 The @value{GDBN} ``artificial array'' operator (@pxref{Expressions, ,Expressions}).
13185 Addition and subtraction. Defined on integral types, floating-point types and
13188 @item *@r{, }/@r{, }%
13189 Multiplication, division, and modulus. Multiplication and division are
13190 defined on integral and floating-point types. Modulus is defined on
13194 Increment and decrement. When appearing before a variable, the
13195 operation is performed before the variable is used in an expression;
13196 when appearing after it, the variable's value is used before the
13197 operation takes place.
13200 Pointer dereferencing. Defined on pointer types. Same precedence as
13204 Address operator. Defined on variables. Same precedence as @code{++}.
13206 For debugging C@t{++}, @value{GDBN} implements a use of @samp{&} beyond what is
13207 allowed in the C@t{++} language itself: you can use @samp{&(&@var{ref})}
13208 to examine the address
13209 where a C@t{++} reference variable (declared with @samp{&@var{ref}}) is
13213 Negative. Defined on integral and floating-point types. Same
13214 precedence as @code{++}.
13217 Logical negation. Defined on integral types. Same precedence as
13221 Bitwise complement operator. Defined on integral types. Same precedence as
13226 Structure member, and pointer-to-structure member. For convenience,
13227 @value{GDBN} regards the two as equivalent, choosing whether to dereference a
13228 pointer based on the stored type information.
13229 Defined on @code{struct} and @code{union} data.
13232 Dereferences of pointers to members.
13235 Array indexing. @code{@var{a}[@var{i}]} is defined as
13236 @code{*(@var{a}+@var{i})}. Same precedence as @code{->}.
13239 Function parameter list. Same precedence as @code{->}.
13242 C@t{++} scope resolution operator. Defined on @code{struct}, @code{union},
13243 and @code{class} types.
13246 Doubled colons also represent the @value{GDBN} scope operator
13247 (@pxref{Expressions, ,Expressions}). Same precedence as @code{::},
13251 If an operator is redefined in the user code, @value{GDBN} usually
13252 attempts to invoke the redefined version instead of using the operator's
13253 predefined meaning.
13256 @subsubsection C and C@t{++} Constants
13258 @cindex C and C@t{++} constants
13260 @value{GDBN} allows you to express the constants of C and C@t{++} in the
13265 Integer constants are a sequence of digits. Octal constants are
13266 specified by a leading @samp{0} (i.e.@: zero), and hexadecimal constants
13267 by a leading @samp{0x} or @samp{0X}. Constants may also end with a letter
13268 @samp{l}, specifying that the constant should be treated as a
13272 Floating point constants are a sequence of digits, followed by a decimal
13273 point, followed by a sequence of digits, and optionally followed by an
13274 exponent. An exponent is of the form:
13275 @samp{@w{e@r{[[}+@r{]|}-@r{]}@var{nnn}}}, where @var{nnn} is another
13276 sequence of digits. The @samp{+} is optional for positive exponents.
13277 A floating-point constant may also end with a letter @samp{f} or
13278 @samp{F}, specifying that the constant should be treated as being of
13279 the @code{float} (as opposed to the default @code{double}) type; or with
13280 a letter @samp{l} or @samp{L}, which specifies a @code{long double}
13284 Enumerated constants consist of enumerated identifiers, or their
13285 integral equivalents.
13288 Character constants are a single character surrounded by single quotes
13289 (@code{'}), or a number---the ordinal value of the corresponding character
13290 (usually its @sc{ascii} value). Within quotes, the single character may
13291 be represented by a letter or by @dfn{escape sequences}, which are of
13292 the form @samp{\@var{nnn}}, where @var{nnn} is the octal representation
13293 of the character's ordinal value; or of the form @samp{\@var{x}}, where
13294 @samp{@var{x}} is a predefined special character---for example,
13295 @samp{\n} for newline.
13297 Wide character constants can be written by prefixing a character
13298 constant with @samp{L}, as in C. For example, @samp{L'x'} is the wide
13299 form of @samp{x}. The target wide character set is used when
13300 computing the value of this constant (@pxref{Character Sets}).
13303 String constants are a sequence of character constants surrounded by
13304 double quotes (@code{"}). Any valid character constant (as described
13305 above) may appear. Double quotes within the string must be preceded by
13306 a backslash, so for instance @samp{"a\"b'c"} is a string of five
13309 Wide string constants can be written by prefixing a string constant
13310 with @samp{L}, as in C. The target wide character set is used when
13311 computing the value of this constant (@pxref{Character Sets}).
13314 Pointer constants are an integral value. You can also write pointers
13315 to constants using the C operator @samp{&}.
13318 Array constants are comma-separated lists surrounded by braces @samp{@{}
13319 and @samp{@}}; for example, @samp{@{1,2,3@}} is a three-element array of
13320 integers, @samp{@{@{1,2@}, @{3,4@}, @{5,6@}@}} is a three-by-two array,
13321 and @samp{@{&"hi", &"there", &"fred"@}} is a three-element array of pointers.
13324 @node C Plus Plus Expressions
13325 @subsubsection C@t{++} Expressions
13327 @cindex expressions in C@t{++}
13328 @value{GDBN} expression handling can interpret most C@t{++} expressions.
13330 @cindex debugging C@t{++} programs
13331 @cindex C@t{++} compilers
13332 @cindex debug formats and C@t{++}
13333 @cindex @value{NGCC} and C@t{++}
13335 @emph{Warning:} @value{GDBN} can only debug C@t{++} code if you use
13336 the proper compiler and the proper debug format. Currently,
13337 @value{GDBN} works best when debugging C@t{++} code that is compiled
13338 with the most recent version of @value{NGCC} possible. The DWARF
13339 debugging format is preferred; @value{NGCC} defaults to this on most
13340 popular platforms. Other compilers and/or debug formats are likely to
13341 work badly or not at all when using @value{GDBN} to debug C@t{++}
13342 code. @xref{Compilation}.
13347 @cindex member functions
13349 Member function calls are allowed; you can use expressions like
13352 count = aml->GetOriginal(x, y)
13355 @vindex this@r{, inside C@t{++} member functions}
13356 @cindex namespace in C@t{++}
13358 While a member function is active (in the selected stack frame), your
13359 expressions have the same namespace available as the member function;
13360 that is, @value{GDBN} allows implicit references to the class instance
13361 pointer @code{this} following the same rules as C@t{++}. @code{using}
13362 declarations in the current scope are also respected by @value{GDBN}.
13364 @cindex call overloaded functions
13365 @cindex overloaded functions, calling
13366 @cindex type conversions in C@t{++}
13368 You can call overloaded functions; @value{GDBN} resolves the function
13369 call to the right definition, with some restrictions. @value{GDBN} does not
13370 perform overload resolution involving user-defined type conversions,
13371 calls to constructors, or instantiations of templates that do not exist
13372 in the program. It also cannot handle ellipsis argument lists or
13375 It does perform integral conversions and promotions, floating-point
13376 promotions, arithmetic conversions, pointer conversions, conversions of
13377 class objects to base classes, and standard conversions such as those of
13378 functions or arrays to pointers; it requires an exact match on the
13379 number of function arguments.
13381 Overload resolution is always performed, unless you have specified
13382 @code{set overload-resolution off}. @xref{Debugging C Plus Plus,
13383 ,@value{GDBN} Features for C@t{++}}.
13385 You must specify @code{set overload-resolution off} in order to use an
13386 explicit function signature to call an overloaded function, as in
13388 p 'foo(char,int)'('x', 13)
13391 The @value{GDBN} command-completion facility can simplify this;
13392 see @ref{Completion, ,Command Completion}.
13394 @cindex reference declarations
13396 @value{GDBN} understands variables declared as C@t{++} references; you can use
13397 them in expressions just as you do in C@t{++} source---they are automatically
13400 In the parameter list shown when @value{GDBN} displays a frame, the values of
13401 reference variables are not displayed (unlike other variables); this
13402 avoids clutter, since references are often used for large structures.
13403 The @emph{address} of a reference variable is always shown, unless
13404 you have specified @samp{set print address off}.
13407 @value{GDBN} supports the C@t{++} name resolution operator @code{::}---your
13408 expressions can use it just as expressions in your program do. Since
13409 one scope may be defined in another, you can use @code{::} repeatedly if
13410 necessary, for example in an expression like
13411 @samp{@var{scope1}::@var{scope2}::@var{name}}. @value{GDBN} also allows
13412 resolving name scope by reference to source files, in both C and C@t{++}
13413 debugging (@pxref{Variables, ,Program Variables}).
13416 @value{GDBN} performs argument-dependent lookup, following the C@t{++}
13421 @subsubsection C and C@t{++} Defaults
13423 @cindex C and C@t{++} defaults
13425 If you allow @value{GDBN} to set range checking automatically, it
13426 defaults to @code{off} whenever the working language changes to
13427 C or C@t{++}. This happens regardless of whether you or @value{GDBN}
13428 selects the working language.
13430 If you allow @value{GDBN} to set the language automatically, it
13431 recognizes source files whose names end with @file{.c}, @file{.C}, or
13432 @file{.cc}, etc, and when @value{GDBN} enters code compiled from one of
13433 these files, it sets the working language to C or C@t{++}.
13434 @xref{Automatically, ,Having @value{GDBN} Infer the Source Language},
13435 for further details.
13438 @subsubsection C and C@t{++} Type and Range Checks
13440 @cindex C and C@t{++} checks
13442 By default, when @value{GDBN} parses C or C@t{++} expressions, strict type
13443 checking is used. However, if you turn type checking off, @value{GDBN}
13444 will allow certain non-standard conversions, such as promoting integer
13445 constants to pointers.
13447 Range checking, if turned on, is done on mathematical operations. Array
13448 indices are not checked, since they are often used to index a pointer
13449 that is not itself an array.
13452 @subsubsection @value{GDBN} and C
13454 The @code{set print union} and @code{show print union} commands apply to
13455 the @code{union} type. When set to @samp{on}, any @code{union} that is
13456 inside a @code{struct} or @code{class} is also printed. Otherwise, it
13457 appears as @samp{@{...@}}.
13459 The @code{@@} operator aids in the debugging of dynamic arrays, formed
13460 with pointers and a memory allocation function. @xref{Expressions,
13463 @node Debugging C Plus Plus
13464 @subsubsection @value{GDBN} Features for C@t{++}
13466 @cindex commands for C@t{++}
13468 Some @value{GDBN} commands are particularly useful with C@t{++}, and some are
13469 designed specifically for use with C@t{++}. Here is a summary:
13472 @cindex break in overloaded functions
13473 @item @r{breakpoint menus}
13474 When you want a breakpoint in a function whose name is overloaded,
13475 @value{GDBN} has the capability to display a menu of possible breakpoint
13476 locations to help you specify which function definition you want.
13477 @xref{Ambiguous Expressions,,Ambiguous Expressions}.
13479 @cindex overloading in C@t{++}
13480 @item rbreak @var{regex}
13481 Setting breakpoints using regular expressions is helpful for setting
13482 breakpoints on overloaded functions that are not members of any special
13484 @xref{Set Breaks, ,Setting Breakpoints}.
13486 @cindex C@t{++} exception handling
13489 Debug C@t{++} exception handling using these commands. @xref{Set
13490 Catchpoints, , Setting Catchpoints}.
13492 @cindex inheritance
13493 @item ptype @var{typename}
13494 Print inheritance relationships as well as other information for type
13496 @xref{Symbols, ,Examining the Symbol Table}.
13498 @item info vtbl @var{expression}.
13499 The @code{info vtbl} command can be used to display the virtual
13500 method tables of the object computed by @var{expression}. This shows
13501 one entry per virtual table; there may be multiple virtual tables when
13502 multiple inheritance is in use.
13504 @cindex C@t{++} symbol display
13505 @item set print demangle
13506 @itemx show print demangle
13507 @itemx set print asm-demangle
13508 @itemx show print asm-demangle
13509 Control whether C@t{++} symbols display in their source form, both when
13510 displaying code as C@t{++} source and when displaying disassemblies.
13511 @xref{Print Settings, ,Print Settings}.
13513 @item set print object
13514 @itemx show print object
13515 Choose whether to print derived (actual) or declared types of objects.
13516 @xref{Print Settings, ,Print Settings}.
13518 @item set print vtbl
13519 @itemx show print vtbl
13520 Control the format for printing virtual function tables.
13521 @xref{Print Settings, ,Print Settings}.
13522 (The @code{vtbl} commands do not work on programs compiled with the HP
13523 ANSI C@t{++} compiler (@code{aCC}).)
13525 @kindex set overload-resolution
13526 @cindex overloaded functions, overload resolution
13527 @item set overload-resolution on
13528 Enable overload resolution for C@t{++} expression evaluation. The default
13529 is on. For overloaded functions, @value{GDBN} evaluates the arguments
13530 and searches for a function whose signature matches the argument types,
13531 using the standard C@t{++} conversion rules (see @ref{C Plus Plus
13532 Expressions, ,C@t{++} Expressions}, for details).
13533 If it cannot find a match, it emits a message.
13535 @item set overload-resolution off
13536 Disable overload resolution for C@t{++} expression evaluation. For
13537 overloaded functions that are not class member functions, @value{GDBN}
13538 chooses the first function of the specified name that it finds in the
13539 symbol table, whether or not its arguments are of the correct type. For
13540 overloaded functions that are class member functions, @value{GDBN}
13541 searches for a function whose signature @emph{exactly} matches the
13544 @kindex show overload-resolution
13545 @item show overload-resolution
13546 Show the current setting of overload resolution.
13548 @item @r{Overloaded symbol names}
13549 You can specify a particular definition of an overloaded symbol, using
13550 the same notation that is used to declare such symbols in C@t{++}: type
13551 @code{@var{symbol}(@var{types})} rather than just @var{symbol}. You can
13552 also use the @value{GDBN} command-line word completion facilities to list the
13553 available choices, or to finish the type list for you.
13554 @xref{Completion,, Command Completion}, for details on how to do this.
13557 @node Decimal Floating Point
13558 @subsubsection Decimal Floating Point format
13559 @cindex decimal floating point format
13561 @value{GDBN} can examine, set and perform computations with numbers in
13562 decimal floating point format, which in the C language correspond to the
13563 @code{_Decimal32}, @code{_Decimal64} and @code{_Decimal128} types as
13564 specified by the extension to support decimal floating-point arithmetic.
13566 There are two encodings in use, depending on the architecture: BID (Binary
13567 Integer Decimal) for x86 and x86-64, and DPD (Densely Packed Decimal) for
13568 PowerPC. @value{GDBN} will use the appropriate encoding for the configured
13571 Because of a limitation in @file{libdecnumber}, the library used by @value{GDBN}
13572 to manipulate decimal floating point numbers, it is not possible to convert
13573 (using a cast, for example) integers wider than 32-bit to decimal float.
13575 In addition, in order to imitate @value{GDBN}'s behaviour with binary floating
13576 point computations, error checking in decimal float operations ignores
13577 underflow, overflow and divide by zero exceptions.
13579 In the PowerPC architecture, @value{GDBN} provides a set of pseudo-registers
13580 to inspect @code{_Decimal128} values stored in floating point registers.
13581 See @ref{PowerPC,,PowerPC} for more details.
13587 @value{GDBN} can be used to debug programs written in D and compiled with
13588 GDC, LDC or DMD compilers. Currently @value{GDBN} supports only one D
13589 specific feature --- dynamic arrays.
13594 @cindex Go (programming language)
13595 @value{GDBN} can be used to debug programs written in Go and compiled with
13596 @file{gccgo} or @file{6g} compilers.
13598 Here is a summary of the Go-specific features and restrictions:
13601 @cindex current Go package
13602 @item The current Go package
13603 The name of the current package does not need to be specified when
13604 specifying global variables and functions.
13606 For example, given the program:
13610 var myglob = "Shall we?"
13616 When stopped inside @code{main} either of these work:
13620 (gdb) p main.myglob
13623 @cindex builtin Go types
13624 @item Builtin Go types
13625 The @code{string} type is recognized by @value{GDBN} and is printed
13628 @cindex builtin Go functions
13629 @item Builtin Go functions
13630 The @value{GDBN} expression parser recognizes the @code{unsafe.Sizeof}
13631 function and handles it internally.
13633 @cindex restrictions on Go expressions
13634 @item Restrictions on Go expressions
13635 All Go operators are supported except @code{&^}.
13636 The Go @code{_} ``blank identifier'' is not supported.
13637 Automatic dereferencing of pointers is not supported.
13641 @subsection Objective-C
13643 @cindex Objective-C
13644 This section provides information about some commands and command
13645 options that are useful for debugging Objective-C code. See also
13646 @ref{Symbols, info classes}, and @ref{Symbols, info selectors}, for a
13647 few more commands specific to Objective-C support.
13650 * Method Names in Commands::
13651 * The Print Command with Objective-C::
13654 @node Method Names in Commands
13655 @subsubsection Method Names in Commands
13657 The following commands have been extended to accept Objective-C method
13658 names as line specifications:
13660 @kindex clear@r{, and Objective-C}
13661 @kindex break@r{, and Objective-C}
13662 @kindex info line@r{, and Objective-C}
13663 @kindex jump@r{, and Objective-C}
13664 @kindex list@r{, and Objective-C}
13668 @item @code{info line}
13673 A fully qualified Objective-C method name is specified as
13676 -[@var{Class} @var{methodName}]
13679 where the minus sign is used to indicate an instance method and a
13680 plus sign (not shown) is used to indicate a class method. The class
13681 name @var{Class} and method name @var{methodName} are enclosed in
13682 brackets, similar to the way messages are specified in Objective-C
13683 source code. For example, to set a breakpoint at the @code{create}
13684 instance method of class @code{Fruit} in the program currently being
13688 break -[Fruit create]
13691 To list ten program lines around the @code{initialize} class method,
13695 list +[NSText initialize]
13698 In the current version of @value{GDBN}, the plus or minus sign is
13699 required. In future versions of @value{GDBN}, the plus or minus
13700 sign will be optional, but you can use it to narrow the search. It
13701 is also possible to specify just a method name:
13707 You must specify the complete method name, including any colons. If
13708 your program's source files contain more than one @code{create} method,
13709 you'll be presented with a numbered list of classes that implement that
13710 method. Indicate your choice by number, or type @samp{0} to exit if
13713 As another example, to clear a breakpoint established at the
13714 @code{makeKeyAndOrderFront:} method of the @code{NSWindow} class, enter:
13717 clear -[NSWindow makeKeyAndOrderFront:]
13720 @node The Print Command with Objective-C
13721 @subsubsection The Print Command With Objective-C
13722 @cindex Objective-C, print objects
13723 @kindex print-object
13724 @kindex po @r{(@code{print-object})}
13726 The print command has also been extended to accept methods. For example:
13729 print -[@var{object} hash]
13732 @cindex print an Objective-C object description
13733 @cindex @code{_NSPrintForDebugger}, and printing Objective-C objects
13735 will tell @value{GDBN} to send the @code{hash} message to @var{object}
13736 and print the result. Also, an additional command has been added,
13737 @code{print-object} or @code{po} for short, which is meant to print
13738 the description of an object. However, this command may only work
13739 with certain Objective-C libraries that have a particular hook
13740 function, @code{_NSPrintForDebugger}, defined.
13743 @subsection OpenCL C
13746 This section provides information about @value{GDBN}s OpenCL C support.
13749 * OpenCL C Datatypes::
13750 * OpenCL C Expressions::
13751 * OpenCL C Operators::
13754 @node OpenCL C Datatypes
13755 @subsubsection OpenCL C Datatypes
13757 @cindex OpenCL C Datatypes
13758 @value{GDBN} supports the builtin scalar and vector datatypes specified
13759 by OpenCL 1.1. In addition the half- and double-precision floating point
13760 data types of the @code{cl_khr_fp16} and @code{cl_khr_fp64} OpenCL
13761 extensions are also known to @value{GDBN}.
13763 @node OpenCL C Expressions
13764 @subsubsection OpenCL C Expressions
13766 @cindex OpenCL C Expressions
13767 @value{GDBN} supports accesses to vector components including the access as
13768 lvalue where possible. Since OpenCL C is based on C99 most C expressions
13769 supported by @value{GDBN} can be used as well.
13771 @node OpenCL C Operators
13772 @subsubsection OpenCL C Operators
13774 @cindex OpenCL C Operators
13775 @value{GDBN} supports the operators specified by OpenCL 1.1 for scalar and
13779 @subsection Fortran
13780 @cindex Fortran-specific support in @value{GDBN}
13782 @value{GDBN} can be used to debug programs written in Fortran, but it
13783 currently supports only the features of Fortran 77 language.
13785 @cindex trailing underscore, in Fortran symbols
13786 Some Fortran compilers (@sc{gnu} Fortran 77 and Fortran 95 compilers
13787 among them) append an underscore to the names of variables and
13788 functions. When you debug programs compiled by those compilers, you
13789 will need to refer to variables and functions with a trailing
13793 * Fortran Operators:: Fortran operators and expressions
13794 * Fortran Defaults:: Default settings for Fortran
13795 * Special Fortran Commands:: Special @value{GDBN} commands for Fortran
13798 @node Fortran Operators
13799 @subsubsection Fortran Operators and Expressions
13801 @cindex Fortran operators and expressions
13803 Operators must be defined on values of specific types. For instance,
13804 @code{+} is defined on numbers, but not on characters or other non-
13805 arithmetic types. Operators are often defined on groups of types.
13809 The exponentiation operator. It raises the first operand to the power
13813 The range operator. Normally used in the form of array(low:high) to
13814 represent a section of array.
13817 The access component operator. Normally used to access elements in derived
13818 types. Also suitable for unions. As unions aren't part of regular Fortran,
13819 this can only happen when accessing a register that uses a gdbarch-defined
13823 @node Fortran Defaults
13824 @subsubsection Fortran Defaults
13826 @cindex Fortran Defaults
13828 Fortran symbols are usually case-insensitive, so @value{GDBN} by
13829 default uses case-insensitive matches for Fortran symbols. You can
13830 change that with the @samp{set case-insensitive} command, see
13831 @ref{Symbols}, for the details.
13833 @node Special Fortran Commands
13834 @subsubsection Special Fortran Commands
13836 @cindex Special Fortran commands
13838 @value{GDBN} has some commands to support Fortran-specific features,
13839 such as displaying common blocks.
13842 @cindex @code{COMMON} blocks, Fortran
13843 @kindex info common
13844 @item info common @r{[}@var{common-name}@r{]}
13845 This command prints the values contained in the Fortran @code{COMMON}
13846 block whose name is @var{common-name}. With no argument, the names of
13847 all @code{COMMON} blocks visible at the current program location are
13854 @cindex Pascal support in @value{GDBN}, limitations
13855 Debugging Pascal programs which use sets, subranges, file variables, or
13856 nested functions does not currently work. @value{GDBN} does not support
13857 entering expressions, printing values, or similar features using Pascal
13860 The Pascal-specific command @code{set print pascal_static-members}
13861 controls whether static members of Pascal objects are displayed.
13862 @xref{Print Settings, pascal_static-members}.
13865 @subsection Modula-2
13867 @cindex Modula-2, @value{GDBN} support
13869 The extensions made to @value{GDBN} to support Modula-2 only support
13870 output from the @sc{gnu} Modula-2 compiler (which is currently being
13871 developed). Other Modula-2 compilers are not currently supported, and
13872 attempting to debug executables produced by them is most likely
13873 to give an error as @value{GDBN} reads in the executable's symbol
13876 @cindex expressions in Modula-2
13878 * M2 Operators:: Built-in operators
13879 * Built-In Func/Proc:: Built-in functions and procedures
13880 * M2 Constants:: Modula-2 constants
13881 * M2 Types:: Modula-2 types
13882 * M2 Defaults:: Default settings for Modula-2
13883 * Deviations:: Deviations from standard Modula-2
13884 * M2 Checks:: Modula-2 type and range checks
13885 * M2 Scope:: The scope operators @code{::} and @code{.}
13886 * GDB/M2:: @value{GDBN} and Modula-2
13890 @subsubsection Operators
13891 @cindex Modula-2 operators
13893 Operators must be defined on values of specific types. For instance,
13894 @code{+} is defined on numbers, but not on structures. Operators are
13895 often defined on groups of types. For the purposes of Modula-2, the
13896 following definitions hold:
13901 @emph{Integral types} consist of @code{INTEGER}, @code{CARDINAL}, and
13905 @emph{Character types} consist of @code{CHAR} and its subranges.
13908 @emph{Floating-point types} consist of @code{REAL}.
13911 @emph{Pointer types} consist of anything declared as @code{POINTER TO
13915 @emph{Scalar types} consist of all of the above.
13918 @emph{Set types} consist of @code{SET} and @code{BITSET} types.
13921 @emph{Boolean types} consist of @code{BOOLEAN}.
13925 The following operators are supported, and appear in order of
13926 increasing precedence:
13930 Function argument or array index separator.
13933 Assignment. The value of @var{var} @code{:=} @var{value} is
13937 Less than, greater than on integral, floating-point, or enumerated
13941 Less than or equal to, greater than or equal to
13942 on integral, floating-point and enumerated types, or set inclusion on
13943 set types. Same precedence as @code{<}.
13945 @item =@r{, }<>@r{, }#
13946 Equality and two ways of expressing inequality, valid on scalar types.
13947 Same precedence as @code{<}. In @value{GDBN} scripts, only @code{<>} is
13948 available for inequality, since @code{#} conflicts with the script
13952 Set membership. Defined on set types and the types of their members.
13953 Same precedence as @code{<}.
13956 Boolean disjunction. Defined on boolean types.
13959 Boolean conjunction. Defined on boolean types.
13962 The @value{GDBN} ``artificial array'' operator (@pxref{Expressions, ,Expressions}).
13965 Addition and subtraction on integral and floating-point types, or union
13966 and difference on set types.
13969 Multiplication on integral and floating-point types, or set intersection
13973 Division on floating-point types, or symmetric set difference on set
13974 types. Same precedence as @code{*}.
13977 Integer division and remainder. Defined on integral types. Same
13978 precedence as @code{*}.
13981 Negative. Defined on @code{INTEGER} and @code{REAL} data.
13984 Pointer dereferencing. Defined on pointer types.
13987 Boolean negation. Defined on boolean types. Same precedence as
13991 @code{RECORD} field selector. Defined on @code{RECORD} data. Same
13992 precedence as @code{^}.
13995 Array indexing. Defined on @code{ARRAY} data. Same precedence as @code{^}.
13998 Procedure argument list. Defined on @code{PROCEDURE} objects. Same precedence
14002 @value{GDBN} and Modula-2 scope operators.
14006 @emph{Warning:} Set expressions and their operations are not yet supported, so @value{GDBN}
14007 treats the use of the operator @code{IN}, or the use of operators
14008 @code{+}, @code{-}, @code{*}, @code{/}, @code{=}, , @code{<>}, @code{#},
14009 @code{<=}, and @code{>=} on sets as an error.
14013 @node Built-In Func/Proc
14014 @subsubsection Built-in Functions and Procedures
14015 @cindex Modula-2 built-ins
14017 Modula-2 also makes available several built-in procedures and functions.
14018 In describing these, the following metavariables are used:
14023 represents an @code{ARRAY} variable.
14026 represents a @code{CHAR} constant or variable.
14029 represents a variable or constant of integral type.
14032 represents an identifier that belongs to a set. Generally used in the
14033 same function with the metavariable @var{s}. The type of @var{s} should
14034 be @code{SET OF @var{mtype}} (where @var{mtype} is the type of @var{m}).
14037 represents a variable or constant of integral or floating-point type.
14040 represents a variable or constant of floating-point type.
14046 represents a variable.
14049 represents a variable or constant of one of many types. See the
14050 explanation of the function for details.
14053 All Modula-2 built-in procedures also return a result, described below.
14057 Returns the absolute value of @var{n}.
14060 If @var{c} is a lower case letter, it returns its upper case
14061 equivalent, otherwise it returns its argument.
14064 Returns the character whose ordinal value is @var{i}.
14067 Decrements the value in the variable @var{v} by one. Returns the new value.
14069 @item DEC(@var{v},@var{i})
14070 Decrements the value in the variable @var{v} by @var{i}. Returns the
14073 @item EXCL(@var{m},@var{s})
14074 Removes the element @var{m} from the set @var{s}. Returns the new
14077 @item FLOAT(@var{i})
14078 Returns the floating point equivalent of the integer @var{i}.
14080 @item HIGH(@var{a})
14081 Returns the index of the last member of @var{a}.
14084 Increments the value in the variable @var{v} by one. Returns the new value.
14086 @item INC(@var{v},@var{i})
14087 Increments the value in the variable @var{v} by @var{i}. Returns the
14090 @item INCL(@var{m},@var{s})
14091 Adds the element @var{m} to the set @var{s} if it is not already
14092 there. Returns the new set.
14095 Returns the maximum value of the type @var{t}.
14098 Returns the minimum value of the type @var{t}.
14101 Returns boolean TRUE if @var{i} is an odd number.
14104 Returns the ordinal value of its argument. For example, the ordinal
14105 value of a character is its @sc{ascii} value (on machines supporting the
14106 @sc{ascii} character set). @var{x} must be of an ordered type, which include
14107 integral, character and enumerated types.
14109 @item SIZE(@var{x})
14110 Returns the size of its argument. @var{x} can be a variable or a type.
14112 @item TRUNC(@var{r})
14113 Returns the integral part of @var{r}.
14115 @item TSIZE(@var{x})
14116 Returns the size of its argument. @var{x} can be a variable or a type.
14118 @item VAL(@var{t},@var{i})
14119 Returns the member of the type @var{t} whose ordinal value is @var{i}.
14123 @emph{Warning:} Sets and their operations are not yet supported, so
14124 @value{GDBN} treats the use of procedures @code{INCL} and @code{EXCL} as
14128 @cindex Modula-2 constants
14130 @subsubsection Constants
14132 @value{GDBN} allows you to express the constants of Modula-2 in the following
14138 Integer constants are simply a sequence of digits. When used in an
14139 expression, a constant is interpreted to be type-compatible with the
14140 rest of the expression. Hexadecimal integers are specified by a
14141 trailing @samp{H}, and octal integers by a trailing @samp{B}.
14144 Floating point constants appear as a sequence of digits, followed by a
14145 decimal point and another sequence of digits. An optional exponent can
14146 then be specified, in the form @samp{E@r{[}+@r{|}-@r{]}@var{nnn}}, where
14147 @samp{@r{[}+@r{|}-@r{]}@var{nnn}} is the desired exponent. All of the
14148 digits of the floating point constant must be valid decimal (base 10)
14152 Character constants consist of a single character enclosed by a pair of
14153 like quotes, either single (@code{'}) or double (@code{"}). They may
14154 also be expressed by their ordinal value (their @sc{ascii} value, usually)
14155 followed by a @samp{C}.
14158 String constants consist of a sequence of characters enclosed by a
14159 pair of like quotes, either single (@code{'}) or double (@code{"}).
14160 Escape sequences in the style of C are also allowed. @xref{C
14161 Constants, ,C and C@t{++} Constants}, for a brief explanation of escape
14165 Enumerated constants consist of an enumerated identifier.
14168 Boolean constants consist of the identifiers @code{TRUE} and
14172 Pointer constants consist of integral values only.
14175 Set constants are not yet supported.
14179 @subsubsection Modula-2 Types
14180 @cindex Modula-2 types
14182 Currently @value{GDBN} can print the following data types in Modula-2
14183 syntax: array types, record types, set types, pointer types, procedure
14184 types, enumerated types, subrange types and base types. You can also
14185 print the contents of variables declared using these type.
14186 This section gives a number of simple source code examples together with
14187 sample @value{GDBN} sessions.
14189 The first example contains the following section of code:
14198 and you can request @value{GDBN} to interrogate the type and value of
14199 @code{r} and @code{s}.
14202 (@value{GDBP}) print s
14204 (@value{GDBP}) ptype s
14206 (@value{GDBP}) print r
14208 (@value{GDBP}) ptype r
14213 Likewise if your source code declares @code{s} as:
14217 s: SET ['A'..'Z'] ;
14221 then you may query the type of @code{s} by:
14224 (@value{GDBP}) ptype s
14225 type = SET ['A'..'Z']
14229 Note that at present you cannot interactively manipulate set
14230 expressions using the debugger.
14232 The following example shows how you might declare an array in Modula-2
14233 and how you can interact with @value{GDBN} to print its type and contents:
14237 s: ARRAY [-10..10] OF CHAR ;
14241 (@value{GDBP}) ptype s
14242 ARRAY [-10..10] OF CHAR
14245 Note that the array handling is not yet complete and although the type
14246 is printed correctly, expression handling still assumes that all
14247 arrays have a lower bound of zero and not @code{-10} as in the example
14250 Here are some more type related Modula-2 examples:
14254 colour = (blue, red, yellow, green) ;
14255 t = [blue..yellow] ;
14263 The @value{GDBN} interaction shows how you can query the data type
14264 and value of a variable.
14267 (@value{GDBP}) print s
14269 (@value{GDBP}) ptype t
14270 type = [blue..yellow]
14274 In this example a Modula-2 array is declared and its contents
14275 displayed. Observe that the contents are written in the same way as
14276 their @code{C} counterparts.
14280 s: ARRAY [1..5] OF CARDINAL ;
14286 (@value{GDBP}) print s
14287 $1 = @{1, 0, 0, 0, 0@}
14288 (@value{GDBP}) ptype s
14289 type = ARRAY [1..5] OF CARDINAL
14292 The Modula-2 language interface to @value{GDBN} also understands
14293 pointer types as shown in this example:
14297 s: POINTER TO ARRAY [1..5] OF CARDINAL ;
14304 and you can request that @value{GDBN} describes the type of @code{s}.
14307 (@value{GDBP}) ptype s
14308 type = POINTER TO ARRAY [1..5] OF CARDINAL
14311 @value{GDBN} handles compound types as we can see in this example.
14312 Here we combine array types, record types, pointer types and subrange
14323 myarray = ARRAY myrange OF CARDINAL ;
14324 myrange = [-2..2] ;
14326 s: POINTER TO ARRAY myrange OF foo ;
14330 and you can ask @value{GDBN} to describe the type of @code{s} as shown
14334 (@value{GDBP}) ptype s
14335 type = POINTER TO ARRAY [-2..2] OF foo = RECORD
14338 f3 : ARRAY [-2..2] OF CARDINAL;
14343 @subsubsection Modula-2 Defaults
14344 @cindex Modula-2 defaults
14346 If type and range checking are set automatically by @value{GDBN}, they
14347 both default to @code{on} whenever the working language changes to
14348 Modula-2. This happens regardless of whether you or @value{GDBN}
14349 selected the working language.
14351 If you allow @value{GDBN} to set the language automatically, then entering
14352 code compiled from a file whose name ends with @file{.mod} sets the
14353 working language to Modula-2. @xref{Automatically, ,Having @value{GDBN}
14354 Infer the Source Language}, for further details.
14357 @subsubsection Deviations from Standard Modula-2
14358 @cindex Modula-2, deviations from
14360 A few changes have been made to make Modula-2 programs easier to debug.
14361 This is done primarily via loosening its type strictness:
14365 Unlike in standard Modula-2, pointer constants can be formed by
14366 integers. This allows you to modify pointer variables during
14367 debugging. (In standard Modula-2, the actual address contained in a
14368 pointer variable is hidden from you; it can only be modified
14369 through direct assignment to another pointer variable or expression that
14370 returned a pointer.)
14373 C escape sequences can be used in strings and characters to represent
14374 non-printable characters. @value{GDBN} prints out strings with these
14375 escape sequences embedded. Single non-printable characters are
14376 printed using the @samp{CHR(@var{nnn})} format.
14379 The assignment operator (@code{:=}) returns the value of its right-hand
14383 All built-in procedures both modify @emph{and} return their argument.
14387 @subsubsection Modula-2 Type and Range Checks
14388 @cindex Modula-2 checks
14391 @emph{Warning:} in this release, @value{GDBN} does not yet perform type or
14394 @c FIXME remove warning when type/range checks added
14396 @value{GDBN} considers two Modula-2 variables type equivalent if:
14400 They are of types that have been declared equivalent via a @code{TYPE
14401 @var{t1} = @var{t2}} statement
14404 They have been declared on the same line. (Note: This is true of the
14405 @sc{gnu} Modula-2 compiler, but it may not be true of other compilers.)
14408 As long as type checking is enabled, any attempt to combine variables
14409 whose types are not equivalent is an error.
14411 Range checking is done on all mathematical operations, assignment, array
14412 index bounds, and all built-in functions and procedures.
14415 @subsubsection The Scope Operators @code{::} and @code{.}
14417 @cindex @code{.}, Modula-2 scope operator
14418 @cindex colon, doubled as scope operator
14420 @vindex colon-colon@r{, in Modula-2}
14421 @c Info cannot handle :: but TeX can.
14424 @vindex ::@r{, in Modula-2}
14427 There are a few subtle differences between the Modula-2 scope operator
14428 (@code{.}) and the @value{GDBN} scope operator (@code{::}). The two have
14433 @var{module} . @var{id}
14434 @var{scope} :: @var{id}
14438 where @var{scope} is the name of a module or a procedure,
14439 @var{module} the name of a module, and @var{id} is any declared
14440 identifier within your program, except another module.
14442 Using the @code{::} operator makes @value{GDBN} search the scope
14443 specified by @var{scope} for the identifier @var{id}. If it is not
14444 found in the specified scope, then @value{GDBN} searches all scopes
14445 enclosing the one specified by @var{scope}.
14447 Using the @code{.} operator makes @value{GDBN} search the current scope for
14448 the identifier specified by @var{id} that was imported from the
14449 definition module specified by @var{module}. With this operator, it is
14450 an error if the identifier @var{id} was not imported from definition
14451 module @var{module}, or if @var{id} is not an identifier in
14455 @subsubsection @value{GDBN} and Modula-2
14457 Some @value{GDBN} commands have little use when debugging Modula-2 programs.
14458 Five subcommands of @code{set print} and @code{show print} apply
14459 specifically to C and C@t{++}: @samp{vtbl}, @samp{demangle},
14460 @samp{asm-demangle}, @samp{object}, and @samp{union}. The first four
14461 apply to C@t{++}, and the last to the C @code{union} type, which has no direct
14462 analogue in Modula-2.
14464 The @code{@@} operator (@pxref{Expressions, ,Expressions}), while available
14465 with any language, is not useful with Modula-2. Its
14466 intent is to aid the debugging of @dfn{dynamic arrays}, which cannot be
14467 created in Modula-2 as they can in C or C@t{++}. However, because an
14468 address can be specified by an integral constant, the construct
14469 @samp{@{@var{type}@}@var{adrexp}} is still useful.
14471 @cindex @code{#} in Modula-2
14472 In @value{GDBN} scripts, the Modula-2 inequality operator @code{#} is
14473 interpreted as the beginning of a comment. Use @code{<>} instead.
14479 The extensions made to @value{GDBN} for Ada only support
14480 output from the @sc{gnu} Ada (GNAT) compiler.
14481 Other Ada compilers are not currently supported, and
14482 attempting to debug executables produced by them is most likely
14486 @cindex expressions in Ada
14488 * Ada Mode Intro:: General remarks on the Ada syntax
14489 and semantics supported by Ada mode
14491 * Omissions from Ada:: Restrictions on the Ada expression syntax.
14492 * Additions to Ada:: Extensions of the Ada expression syntax.
14493 * Stopping Before Main Program:: Debugging the program during elaboration.
14494 * Ada Tasks:: Listing and setting breakpoints in tasks.
14495 * Ada Tasks and Core Files:: Tasking Support when Debugging Core Files
14496 * Ravenscar Profile:: Tasking Support when using the Ravenscar
14498 * Ada Glitches:: Known peculiarities of Ada mode.
14501 @node Ada Mode Intro
14502 @subsubsection Introduction
14503 @cindex Ada mode, general
14505 The Ada mode of @value{GDBN} supports a fairly large subset of Ada expression
14506 syntax, with some extensions.
14507 The philosophy behind the design of this subset is
14511 That @value{GDBN} should provide basic literals and access to operations for
14512 arithmetic, dereferencing, field selection, indexing, and subprogram calls,
14513 leaving more sophisticated computations to subprograms written into the
14514 program (which therefore may be called from @value{GDBN}).
14517 That type safety and strict adherence to Ada language restrictions
14518 are not particularly important to the @value{GDBN} user.
14521 That brevity is important to the @value{GDBN} user.
14524 Thus, for brevity, the debugger acts as if all names declared in
14525 user-written packages are directly visible, even if they are not visible
14526 according to Ada rules, thus making it unnecessary to fully qualify most
14527 names with their packages, regardless of context. Where this causes
14528 ambiguity, @value{GDBN} asks the user's intent.
14530 The debugger will start in Ada mode if it detects an Ada main program.
14531 As for other languages, it will enter Ada mode when stopped in a program that
14532 was translated from an Ada source file.
14534 While in Ada mode, you may use `@t{--}' for comments. This is useful
14535 mostly for documenting command files. The standard @value{GDBN} comment
14536 (@samp{#}) still works at the beginning of a line in Ada mode, but not in the
14537 middle (to allow based literals).
14539 The debugger supports limited overloading. Given a subprogram call in which
14540 the function symbol has multiple definitions, it will use the number of
14541 actual parameters and some information about their types to attempt to narrow
14542 the set of definitions. It also makes very limited use of context, preferring
14543 procedures to functions in the context of the @code{call} command, and
14544 functions to procedures elsewhere.
14546 @node Omissions from Ada
14547 @subsubsection Omissions from Ada
14548 @cindex Ada, omissions from
14550 Here are the notable omissions from the subset:
14554 Only a subset of the attributes are supported:
14558 @t{'First}, @t{'Last}, and @t{'Length}
14559 on array objects (not on types and subtypes).
14562 @t{'Min} and @t{'Max}.
14565 @t{'Pos} and @t{'Val}.
14571 @t{'Range} on array objects (not subtypes), but only as the right
14572 operand of the membership (@code{in}) operator.
14575 @t{'Access}, @t{'Unchecked_Access}, and
14576 @t{'Unrestricted_Access} (a GNAT extension).
14584 @code{Characters.Latin_1} are not available and
14585 concatenation is not implemented. Thus, escape characters in strings are
14586 not currently available.
14589 Equality tests (@samp{=} and @samp{/=}) on arrays test for bitwise
14590 equality of representations. They will generally work correctly
14591 for strings and arrays whose elements have integer or enumeration types.
14592 They may not work correctly for arrays whose element
14593 types have user-defined equality, for arrays of real values
14594 (in particular, IEEE-conformant floating point, because of negative
14595 zeroes and NaNs), and for arrays whose elements contain unused bits with
14596 indeterminate values.
14599 The other component-by-component array operations (@code{and}, @code{or},
14600 @code{xor}, @code{not}, and relational tests other than equality)
14601 are not implemented.
14604 @cindex array aggregates (Ada)
14605 @cindex record aggregates (Ada)
14606 @cindex aggregates (Ada)
14607 There is limited support for array and record aggregates. They are
14608 permitted only on the right sides of assignments, as in these examples:
14611 (@value{GDBP}) set An_Array := (1, 2, 3, 4, 5, 6)
14612 (@value{GDBP}) set An_Array := (1, others => 0)
14613 (@value{GDBP}) set An_Array := (0|4 => 1, 1..3 => 2, 5 => 6)
14614 (@value{GDBP}) set A_2D_Array := ((1, 2, 3), (4, 5, 6), (7, 8, 9))
14615 (@value{GDBP}) set A_Record := (1, "Peter", True);
14616 (@value{GDBP}) set A_Record := (Name => "Peter", Id => 1, Alive => True)
14620 discriminant's value by assigning an aggregate has an
14621 undefined effect if that discriminant is used within the record.
14622 However, you can first modify discriminants by directly assigning to
14623 them (which normally would not be allowed in Ada), and then performing an
14624 aggregate assignment. For example, given a variable @code{A_Rec}
14625 declared to have a type such as:
14628 type Rec (Len : Small_Integer := 0) is record
14630 Vals : IntArray (1 .. Len);
14634 you can assign a value with a different size of @code{Vals} with two
14638 (@value{GDBP}) set A_Rec.Len := 4
14639 (@value{GDBP}) set A_Rec := (Id => 42, Vals => (1, 2, 3, 4))
14642 As this example also illustrates, @value{GDBN} is very loose about the usual
14643 rules concerning aggregates. You may leave out some of the
14644 components of an array or record aggregate (such as the @code{Len}
14645 component in the assignment to @code{A_Rec} above); they will retain their
14646 original values upon assignment. You may freely use dynamic values as
14647 indices in component associations. You may even use overlapping or
14648 redundant component associations, although which component values are
14649 assigned in such cases is not defined.
14652 Calls to dispatching subprograms are not implemented.
14655 The overloading algorithm is much more limited (i.e., less selective)
14656 than that of real Ada. It makes only limited use of the context in
14657 which a subexpression appears to resolve its meaning, and it is much
14658 looser in its rules for allowing type matches. As a result, some
14659 function calls will be ambiguous, and the user will be asked to choose
14660 the proper resolution.
14663 The @code{new} operator is not implemented.
14666 Entry calls are not implemented.
14669 Aside from printing, arithmetic operations on the native VAX floating-point
14670 formats are not supported.
14673 It is not possible to slice a packed array.
14676 The names @code{True} and @code{False}, when not part of a qualified name,
14677 are interpreted as if implicitly prefixed by @code{Standard}, regardless of
14679 Should your program
14680 redefine these names in a package or procedure (at best a dubious practice),
14681 you will have to use fully qualified names to access their new definitions.
14684 @node Additions to Ada
14685 @subsubsection Additions to Ada
14686 @cindex Ada, deviations from
14688 As it does for other languages, @value{GDBN} makes certain generic
14689 extensions to Ada (@pxref{Expressions}):
14693 If the expression @var{E} is a variable residing in memory (typically
14694 a local variable or array element) and @var{N} is a positive integer,
14695 then @code{@var{E}@@@var{N}} displays the values of @var{E} and the
14696 @var{N}-1 adjacent variables following it in memory as an array. In
14697 Ada, this operator is generally not necessary, since its prime use is
14698 in displaying parts of an array, and slicing will usually do this in
14699 Ada. However, there are occasional uses when debugging programs in
14700 which certain debugging information has been optimized away.
14703 @code{@var{B}::@var{var}} means ``the variable named @var{var} that
14704 appears in function or file @var{B}.'' When @var{B} is a file name,
14705 you must typically surround it in single quotes.
14708 The expression @code{@{@var{type}@} @var{addr}} means ``the variable of type
14709 @var{type} that appears at address @var{addr}.''
14712 A name starting with @samp{$} is a convenience variable
14713 (@pxref{Convenience Vars}) or a machine register (@pxref{Registers}).
14716 In addition, @value{GDBN} provides a few other shortcuts and outright
14717 additions specific to Ada:
14721 The assignment statement is allowed as an expression, returning
14722 its right-hand operand as its value. Thus, you may enter
14725 (@value{GDBP}) set x := y + 3
14726 (@value{GDBP}) print A(tmp := y + 1)
14730 The semicolon is allowed as an ``operator,'' returning as its value
14731 the value of its right-hand operand.
14732 This allows, for example,
14733 complex conditional breaks:
14736 (@value{GDBP}) break f
14737 (@value{GDBP}) condition 1 (report(i); k += 1; A(k) > 100)
14741 Rather than use catenation and symbolic character names to introduce special
14742 characters into strings, one may instead use a special bracket notation,
14743 which is also used to print strings. A sequence of characters of the form
14744 @samp{["@var{XX}"]} within a string or character literal denotes the
14745 (single) character whose numeric encoding is @var{XX} in hexadecimal. The
14746 sequence of characters @samp{["""]} also denotes a single quotation mark
14747 in strings. For example,
14749 "One line.["0a"]Next line.["0a"]"
14752 contains an ASCII newline character (@code{Ada.Characters.Latin_1.LF})
14756 The subtype used as a prefix for the attributes @t{'Pos}, @t{'Min}, and
14757 @t{'Max} is optional (and is ignored in any case). For example, it is valid
14761 (@value{GDBP}) print 'max(x, y)
14765 When printing arrays, @value{GDBN} uses positional notation when the
14766 array has a lower bound of 1, and uses a modified named notation otherwise.
14767 For example, a one-dimensional array of three integers with a lower bound
14768 of 3 might print as
14775 That is, in contrast to valid Ada, only the first component has a @code{=>}
14779 You may abbreviate attributes in expressions with any unique,
14780 multi-character subsequence of
14781 their names (an exact match gets preference).
14782 For example, you may use @t{a'len}, @t{a'gth}, or @t{a'lh}
14783 in place of @t{a'length}.
14786 @cindex quoting Ada internal identifiers
14787 Since Ada is case-insensitive, the debugger normally maps identifiers you type
14788 to lower case. The GNAT compiler uses upper-case characters for
14789 some of its internal identifiers, which are normally of no interest to users.
14790 For the rare occasions when you actually have to look at them,
14791 enclose them in angle brackets to avoid the lower-case mapping.
14794 (@value{GDBP}) print <JMPBUF_SAVE>[0]
14798 Printing an object of class-wide type or dereferencing an
14799 access-to-class-wide value will display all the components of the object's
14800 specific type (as indicated by its run-time tag). Likewise, component
14801 selection on such a value will operate on the specific type of the
14806 @node Stopping Before Main Program
14807 @subsubsection Stopping at the Very Beginning
14809 @cindex breakpointing Ada elaboration code
14810 It is sometimes necessary to debug the program during elaboration, and
14811 before reaching the main procedure.
14812 As defined in the Ada Reference
14813 Manual, the elaboration code is invoked from a procedure called
14814 @code{adainit}. To run your program up to the beginning of
14815 elaboration, simply use the following two commands:
14816 @code{tbreak adainit} and @code{run}.
14819 @subsubsection Extensions for Ada Tasks
14820 @cindex Ada, tasking
14822 Support for Ada tasks is analogous to that for threads (@pxref{Threads}).
14823 @value{GDBN} provides the following task-related commands:
14828 This command shows a list of current Ada tasks, as in the following example:
14835 (@value{GDBP}) info tasks
14836 ID TID P-ID Pri State Name
14837 1 8088000 0 15 Child Activation Wait main_task
14838 2 80a4000 1 15 Accept Statement b
14839 3 809a800 1 15 Child Activation Wait a
14840 * 4 80ae800 3 15 Runnable c
14845 In this listing, the asterisk before the last task indicates it to be the
14846 task currently being inspected.
14850 Represents @value{GDBN}'s internal task number.
14856 The parent's task ID (@value{GDBN}'s internal task number).
14859 The base priority of the task.
14862 Current state of the task.
14866 The task has been created but has not been activated. It cannot be
14870 The task is not blocked for any reason known to Ada. (It may be waiting
14871 for a mutex, though.) It is conceptually "executing" in normal mode.
14874 The task is terminated, in the sense of ARM 9.3 (5). Any dependents
14875 that were waiting on terminate alternatives have been awakened and have
14876 terminated themselves.
14878 @item Child Activation Wait
14879 The task is waiting for created tasks to complete activation.
14881 @item Accept Statement
14882 The task is waiting on an accept or selective wait statement.
14884 @item Waiting on entry call
14885 The task is waiting on an entry call.
14887 @item Async Select Wait
14888 The task is waiting to start the abortable part of an asynchronous
14892 The task is waiting on a select statement with only a delay
14895 @item Child Termination Wait
14896 The task is sleeping having completed a master within itself, and is
14897 waiting for the tasks dependent on that master to become terminated or
14898 waiting on a terminate Phase.
14900 @item Wait Child in Term Alt
14901 The task is sleeping waiting for tasks on terminate alternatives to
14902 finish terminating.
14904 @item Accepting RV with @var{taskno}
14905 The task is accepting a rendez-vous with the task @var{taskno}.
14909 Name of the task in the program.
14913 @kindex info task @var{taskno}
14914 @item info task @var{taskno}
14915 This command shows detailled informations on the specified task, as in
14916 the following example:
14921 (@value{GDBP}) info tasks
14922 ID TID P-ID Pri State Name
14923 1 8077880 0 15 Child Activation Wait main_task
14924 * 2 807c468 1 15 Runnable task_1
14925 (@value{GDBP}) info task 2
14926 Ada Task: 0x807c468
14929 Parent: 1 (main_task)
14935 @kindex task@r{ (Ada)}
14936 @cindex current Ada task ID
14937 This command prints the ID of the current task.
14943 (@value{GDBP}) info tasks
14944 ID TID P-ID Pri State Name
14945 1 8077870 0 15 Child Activation Wait main_task
14946 * 2 807c458 1 15 Runnable t
14947 (@value{GDBP}) task
14948 [Current task is 2]
14951 @item task @var{taskno}
14952 @cindex Ada task switching
14953 This command is like the @code{thread @var{threadno}}
14954 command (@pxref{Threads}). It switches the context of debugging
14955 from the current task to the given task.
14961 (@value{GDBP}) info tasks
14962 ID TID P-ID Pri State Name
14963 1 8077870 0 15 Child Activation Wait main_task
14964 * 2 807c458 1 15 Runnable t
14965 (@value{GDBP}) task 1
14966 [Switching to task 1]
14967 #0 0x8067726 in pthread_cond_wait ()
14969 #0 0x8067726 in pthread_cond_wait ()
14970 #1 0x8056714 in system.os_interface.pthread_cond_wait ()
14971 #2 0x805cb63 in system.task_primitives.operations.sleep ()
14972 #3 0x806153e in system.tasking.stages.activate_tasks ()
14973 #4 0x804aacc in un () at un.adb:5
14976 @item break @var{linespec} task @var{taskno}
14977 @itemx break @var{linespec} task @var{taskno} if @dots{}
14978 @cindex breakpoints and tasks, in Ada
14979 @cindex task breakpoints, in Ada
14980 @kindex break @dots{} task @var{taskno}@r{ (Ada)}
14981 These commands are like the @code{break @dots{} thread @dots{}}
14982 command (@pxref{Thread Stops}).
14983 @var{linespec} specifies source lines, as described
14984 in @ref{Specify Location}.
14986 Use the qualifier @samp{task @var{taskno}} with a breakpoint command
14987 to specify that you only want @value{GDBN} to stop the program when a
14988 particular Ada task reaches this breakpoint. @var{taskno} is one of the
14989 numeric task identifiers assigned by @value{GDBN}, shown in the first
14990 column of the @samp{info tasks} display.
14992 If you do not specify @samp{task @var{taskno}} when you set a
14993 breakpoint, the breakpoint applies to @emph{all} tasks of your
14996 You can use the @code{task} qualifier on conditional breakpoints as
14997 well; in this case, place @samp{task @var{taskno}} before the
14998 breakpoint condition (before the @code{if}).
15006 (@value{GDBP}) info tasks
15007 ID TID P-ID Pri State Name
15008 1 140022020 0 15 Child Activation Wait main_task
15009 2 140045060 1 15 Accept/Select Wait t2
15010 3 140044840 1 15 Runnable t1
15011 * 4 140056040 1 15 Runnable t3
15012 (@value{GDBP}) b 15 task 2
15013 Breakpoint 5 at 0x120044cb0: file test_task_debug.adb, line 15.
15014 (@value{GDBP}) cont
15019 Breakpoint 5, test_task_debug () at test_task_debug.adb:15
15021 (@value{GDBP}) info tasks
15022 ID TID P-ID Pri State Name
15023 1 140022020 0 15 Child Activation Wait main_task
15024 * 2 140045060 1 15 Runnable t2
15025 3 140044840 1 15 Runnable t1
15026 4 140056040 1 15 Delay Sleep t3
15030 @node Ada Tasks and Core Files
15031 @subsubsection Tasking Support when Debugging Core Files
15032 @cindex Ada tasking and core file debugging
15034 When inspecting a core file, as opposed to debugging a live program,
15035 tasking support may be limited or even unavailable, depending on
15036 the platform being used.
15037 For instance, on x86-linux, the list of tasks is available, but task
15038 switching is not supported. On Tru64, however, task switching will work
15041 On certain platforms, including Tru64, the debugger needs to perform some
15042 memory writes in order to provide Ada tasking support. When inspecting
15043 a core file, this means that the core file must be opened with read-write
15044 privileges, using the command @samp{"set write on"} (@pxref{Patching}).
15045 Under these circumstances, you should make a backup copy of the core
15046 file before inspecting it with @value{GDBN}.
15048 @node Ravenscar Profile
15049 @subsubsection Tasking Support when using the Ravenscar Profile
15050 @cindex Ravenscar Profile
15052 The @dfn{Ravenscar Profile} is a subset of the Ada tasking features,
15053 specifically designed for systems with safety-critical real-time
15057 @kindex set ravenscar task-switching on
15058 @cindex task switching with program using Ravenscar Profile
15059 @item set ravenscar task-switching on
15060 Allows task switching when debugging a program that uses the Ravenscar
15061 Profile. This is the default.
15063 @kindex set ravenscar task-switching off
15064 @item set ravenscar task-switching off
15065 Turn off task switching when debugging a program that uses the Ravenscar
15066 Profile. This is mostly intended to disable the code that adds support
15067 for the Ravenscar Profile, in case a bug in either @value{GDBN} or in
15068 the Ravenscar runtime is preventing @value{GDBN} from working properly.
15069 To be effective, this command should be run before the program is started.
15071 @kindex show ravenscar task-switching
15072 @item show ravenscar task-switching
15073 Show whether it is possible to switch from task to task in a program
15074 using the Ravenscar Profile.
15079 @subsubsection Known Peculiarities of Ada Mode
15080 @cindex Ada, problems
15082 Besides the omissions listed previously (@pxref{Omissions from Ada}),
15083 we know of several problems with and limitations of Ada mode in
15085 some of which will be fixed with planned future releases of the debugger
15086 and the GNU Ada compiler.
15090 Static constants that the compiler chooses not to materialize as objects in
15091 storage are invisible to the debugger.
15094 Named parameter associations in function argument lists are ignored (the
15095 argument lists are treated as positional).
15098 Many useful library packages are currently invisible to the debugger.
15101 Fixed-point arithmetic, conversions, input, and output is carried out using
15102 floating-point arithmetic, and may give results that only approximate those on
15106 The GNAT compiler never generates the prefix @code{Standard} for any of
15107 the standard symbols defined by the Ada language. @value{GDBN} knows about
15108 this: it will strip the prefix from names when you use it, and will never
15109 look for a name you have so qualified among local symbols, nor match against
15110 symbols in other packages or subprograms. If you have
15111 defined entities anywhere in your program other than parameters and
15112 local variables whose simple names match names in @code{Standard},
15113 GNAT's lack of qualification here can cause confusion. When this happens,
15114 you can usually resolve the confusion
15115 by qualifying the problematic names with package
15116 @code{Standard} explicitly.
15119 Older versions of the compiler sometimes generate erroneous debugging
15120 information, resulting in the debugger incorrectly printing the value
15121 of affected entities. In some cases, the debugger is able to work
15122 around an issue automatically. In other cases, the debugger is able
15123 to work around the issue, but the work-around has to be specifically
15126 @kindex set ada trust-PAD-over-XVS
15127 @kindex show ada trust-PAD-over-XVS
15130 @item set ada trust-PAD-over-XVS on
15131 Configure GDB to strictly follow the GNAT encoding when computing the
15132 value of Ada entities, particularly when @code{PAD} and @code{PAD___XVS}
15133 types are involved (see @code{ada/exp_dbug.ads} in the GCC sources for
15134 a complete description of the encoding used by the GNAT compiler).
15135 This is the default.
15137 @item set ada trust-PAD-over-XVS off
15138 This is related to the encoding using by the GNAT compiler. If @value{GDBN}
15139 sometimes prints the wrong value for certain entities, changing @code{ada
15140 trust-PAD-over-XVS} to @code{off} activates a work-around which may fix
15141 the issue. It is always safe to set @code{ada trust-PAD-over-XVS} to
15142 @code{off}, but this incurs a slight performance penalty, so it is
15143 recommended to leave this setting to @code{on} unless necessary.
15147 @node Unsupported Languages
15148 @section Unsupported Languages
15150 @cindex unsupported languages
15151 @cindex minimal language
15152 In addition to the other fully-supported programming languages,
15153 @value{GDBN} also provides a pseudo-language, called @code{minimal}.
15154 It does not represent a real programming language, but provides a set
15155 of capabilities close to what the C or assembly languages provide.
15156 This should allow most simple operations to be performed while debugging
15157 an application that uses a language currently not supported by @value{GDBN}.
15159 If the language is set to @code{auto}, @value{GDBN} will automatically
15160 select this language if the current frame corresponds to an unsupported
15164 @chapter Examining the Symbol Table
15166 The commands described in this chapter allow you to inquire about the
15167 symbols (names of variables, functions and types) defined in your
15168 program. This information is inherent in the text of your program and
15169 does not change as your program executes. @value{GDBN} finds it in your
15170 program's symbol table, in the file indicated when you started @value{GDBN}
15171 (@pxref{File Options, ,Choosing Files}), or by one of the
15172 file-management commands (@pxref{Files, ,Commands to Specify Files}).
15174 @cindex symbol names
15175 @cindex names of symbols
15176 @cindex quoting names
15177 Occasionally, you may need to refer to symbols that contain unusual
15178 characters, which @value{GDBN} ordinarily treats as word delimiters. The
15179 most frequent case is in referring to static variables in other
15180 source files (@pxref{Variables,,Program Variables}). File names
15181 are recorded in object files as debugging symbols, but @value{GDBN} would
15182 ordinarily parse a typical file name, like @file{foo.c}, as the three words
15183 @samp{foo} @samp{.} @samp{c}. To allow @value{GDBN} to recognize
15184 @samp{foo.c} as a single symbol, enclose it in single quotes; for example,
15191 looks up the value of @code{x} in the scope of the file @file{foo.c}.
15194 @cindex case-insensitive symbol names
15195 @cindex case sensitivity in symbol names
15196 @kindex set case-sensitive
15197 @item set case-sensitive on
15198 @itemx set case-sensitive off
15199 @itemx set case-sensitive auto
15200 Normally, when @value{GDBN} looks up symbols, it matches their names
15201 with case sensitivity determined by the current source language.
15202 Occasionally, you may wish to control that. The command @code{set
15203 case-sensitive} lets you do that by specifying @code{on} for
15204 case-sensitive matches or @code{off} for case-insensitive ones. If
15205 you specify @code{auto}, case sensitivity is reset to the default
15206 suitable for the source language. The default is case-sensitive
15207 matches for all languages except for Fortran, for which the default is
15208 case-insensitive matches.
15210 @kindex show case-sensitive
15211 @item show case-sensitive
15212 This command shows the current setting of case sensitivity for symbols
15215 @kindex set print type methods
15216 @item set print type methods
15217 @itemx set print type methods on
15218 @itemx set print type methods off
15219 Normally, when @value{GDBN} prints a class, it displays any methods
15220 declared in that class. You can control this behavior either by
15221 passing the appropriate flag to @code{ptype}, or using @command{set
15222 print type methods}. Specifying @code{on} will cause @value{GDBN} to
15223 display the methods; this is the default. Specifying @code{off} will
15224 cause @value{GDBN} to omit the methods.
15226 @kindex show print type methods
15227 @item show print type methods
15228 This command shows the current setting of method display when printing
15231 @kindex set print type typedefs
15232 @item set print type typedefs
15233 @itemx set print type typedefs on
15234 @itemx set print type typedefs off
15236 Normally, when @value{GDBN} prints a class, it displays any typedefs
15237 defined in that class. You can control this behavior either by
15238 passing the appropriate flag to @code{ptype}, or using @command{set
15239 print type typedefs}. Specifying @code{on} will cause @value{GDBN} to
15240 display the typedef definitions; this is the default. Specifying
15241 @code{off} will cause @value{GDBN} to omit the typedef definitions.
15242 Note that this controls whether the typedef definition itself is
15243 printed, not whether typedef names are substituted when printing other
15246 @kindex show print type typedefs
15247 @item show print type typedefs
15248 This command shows the current setting of typedef display when
15251 @kindex info address
15252 @cindex address of a symbol
15253 @item info address @var{symbol}
15254 Describe where the data for @var{symbol} is stored. For a register
15255 variable, this says which register it is kept in. For a non-register
15256 local variable, this prints the stack-frame offset at which the variable
15259 Note the contrast with @samp{print &@var{symbol}}, which does not work
15260 at all for a register variable, and for a stack local variable prints
15261 the exact address of the current instantiation of the variable.
15263 @kindex info symbol
15264 @cindex symbol from address
15265 @cindex closest symbol and offset for an address
15266 @item info symbol @var{addr}
15267 Print the name of a symbol which is stored at the address @var{addr}.
15268 If no symbol is stored exactly at @var{addr}, @value{GDBN} prints the
15269 nearest symbol and an offset from it:
15272 (@value{GDBP}) info symbol 0x54320
15273 _initialize_vx + 396 in section .text
15277 This is the opposite of the @code{info address} command. You can use
15278 it to find out the name of a variable or a function given its address.
15280 For dynamically linked executables, the name of executable or shared
15281 library containing the symbol is also printed:
15284 (@value{GDBP}) info symbol 0x400225
15285 _start + 5 in section .text of /tmp/a.out
15286 (@value{GDBP}) info symbol 0x2aaaac2811cf
15287 __read_nocancel + 6 in section .text of /usr/lib64/libc.so.6
15291 @item whatis[/@var{flags}] [@var{arg}]
15292 Print the data type of @var{arg}, which can be either an expression
15293 or a name of a data type. With no argument, print the data type of
15294 @code{$}, the last value in the value history.
15296 If @var{arg} is an expression (@pxref{Expressions, ,Expressions}), it
15297 is not actually evaluated, and any side-effecting operations (such as
15298 assignments or function calls) inside it do not take place.
15300 If @var{arg} is a variable or an expression, @code{whatis} prints its
15301 literal type as it is used in the source code. If the type was
15302 defined using a @code{typedef}, @code{whatis} will @emph{not} print
15303 the data type underlying the @code{typedef}. If the type of the
15304 variable or the expression is a compound data type, such as
15305 @code{struct} or @code{class}, @code{whatis} never prints their
15306 fields or methods. It just prints the @code{struct}/@code{class}
15307 name (a.k.a.@: its @dfn{tag}). If you want to see the members of
15308 such a compound data type, use @code{ptype}.
15310 If @var{arg} is a type name that was defined using @code{typedef},
15311 @code{whatis} @dfn{unrolls} only one level of that @code{typedef}.
15312 Unrolling means that @code{whatis} will show the underlying type used
15313 in the @code{typedef} declaration of @var{arg}. However, if that
15314 underlying type is also a @code{typedef}, @code{whatis} will not
15317 For C code, the type names may also have the form @samp{class
15318 @var{class-name}}, @samp{struct @var{struct-tag}}, @samp{union
15319 @var{union-tag}} or @samp{enum @var{enum-tag}}.
15321 @var{flags} can be used to modify how the type is displayed.
15322 Available flags are:
15326 Display in ``raw'' form. Normally, @value{GDBN} substitutes template
15327 parameters and typedefs defined in a class when printing the class'
15328 members. The @code{/r} flag disables this.
15331 Do not print methods defined in the class.
15334 Print methods defined in the class. This is the default, but the flag
15335 exists in case you change the default with @command{set print type methods}.
15338 Do not print typedefs defined in the class. Note that this controls
15339 whether the typedef definition itself is printed, not whether typedef
15340 names are substituted when printing other types.
15343 Print typedefs defined in the class. This is the default, but the flag
15344 exists in case you change the default with @command{set print type typedefs}.
15348 @item ptype[/@var{flags}] [@var{arg}]
15349 @code{ptype} accepts the same arguments as @code{whatis}, but prints a
15350 detailed description of the type, instead of just the name of the type.
15351 @xref{Expressions, ,Expressions}.
15353 Contrary to @code{whatis}, @code{ptype} always unrolls any
15354 @code{typedef}s in its argument declaration, whether the argument is
15355 a variable, expression, or a data type. This means that @code{ptype}
15356 of a variable or an expression will not print literally its type as
15357 present in the source code---use @code{whatis} for that. @code{typedef}s at
15358 the pointer or reference targets are also unrolled. Only @code{typedef}s of
15359 fields, methods and inner @code{class typedef}s of @code{struct}s,
15360 @code{class}es and @code{union}s are not unrolled even with @code{ptype}.
15362 For example, for this variable declaration:
15365 typedef double real_t;
15366 struct complex @{ real_t real; double imag; @};
15367 typedef struct complex complex_t;
15369 real_t *real_pointer_var;
15373 the two commands give this output:
15377 (@value{GDBP}) whatis var
15379 (@value{GDBP}) ptype var
15380 type = struct complex @{
15384 (@value{GDBP}) whatis complex_t
15385 type = struct complex
15386 (@value{GDBP}) whatis struct complex
15387 type = struct complex
15388 (@value{GDBP}) ptype struct complex
15389 type = struct complex @{
15393 (@value{GDBP}) whatis real_pointer_var
15395 (@value{GDBP}) ptype real_pointer_var
15401 As with @code{whatis}, using @code{ptype} without an argument refers to
15402 the type of @code{$}, the last value in the value history.
15404 @cindex incomplete type
15405 Sometimes, programs use opaque data types or incomplete specifications
15406 of complex data structure. If the debug information included in the
15407 program does not allow @value{GDBN} to display a full declaration of
15408 the data type, it will say @samp{<incomplete type>}. For example,
15409 given these declarations:
15413 struct foo *fooptr;
15417 but no definition for @code{struct foo} itself, @value{GDBN} will say:
15420 (@value{GDBP}) ptype foo
15421 $1 = <incomplete type>
15425 ``Incomplete type'' is C terminology for data types that are not
15426 completely specified.
15429 @item info types @var{regexp}
15431 Print a brief description of all types whose names match the regular
15432 expression @var{regexp} (or all types in your program, if you supply
15433 no argument). Each complete typename is matched as though it were a
15434 complete line; thus, @samp{i type value} gives information on all
15435 types in your program whose names include the string @code{value}, but
15436 @samp{i type ^value$} gives information only on types whose complete
15437 name is @code{value}.
15439 This command differs from @code{ptype} in two ways: first, like
15440 @code{whatis}, it does not print a detailed description; second, it
15441 lists all source files where a type is defined.
15443 @kindex info type-printers
15444 @item info type-printers
15445 Versions of @value{GDBN} that ship with Python scripting enabled may
15446 have ``type printers'' available. When using @command{ptype} or
15447 @command{whatis}, these printers are consulted when the name of a type
15448 is needed. @xref{Type Printing API}, for more information on writing
15451 @code{info type-printers} displays all the available type printers.
15453 @kindex enable type-printer
15454 @kindex disable type-printer
15455 @item enable type-printer @var{name}@dots{}
15456 @item disable type-printer @var{name}@dots{}
15457 These commands can be used to enable or disable type printers.
15460 @cindex local variables
15461 @item info scope @var{location}
15462 List all the variables local to a particular scope. This command
15463 accepts a @var{location} argument---a function name, a source line, or
15464 an address preceded by a @samp{*}, and prints all the variables local
15465 to the scope defined by that location. (@xref{Specify Location}, for
15466 details about supported forms of @var{location}.) For example:
15469 (@value{GDBP}) @b{info scope command_line_handler}
15470 Scope for command_line_handler:
15471 Symbol rl is an argument at stack/frame offset 8, length 4.
15472 Symbol linebuffer is in static storage at address 0x150a18, length 4.
15473 Symbol linelength is in static storage at address 0x150a1c, length 4.
15474 Symbol p is a local variable in register $esi, length 4.
15475 Symbol p1 is a local variable in register $ebx, length 4.
15476 Symbol nline is a local variable in register $edx, length 4.
15477 Symbol repeat is a local variable at frame offset -8, length 4.
15481 This command is especially useful for determining what data to collect
15482 during a @dfn{trace experiment}, see @ref{Tracepoint Actions,
15485 @kindex info source
15487 Show information about the current source file---that is, the source file for
15488 the function containing the current point of execution:
15491 the name of the source file, and the directory containing it,
15493 the directory it was compiled in,
15495 its length, in lines,
15497 which programming language it is written in,
15499 whether the executable includes debugging information for that file, and
15500 if so, what format the information is in (e.g., STABS, Dwarf 2, etc.), and
15502 whether the debugging information includes information about
15503 preprocessor macros.
15507 @kindex info sources
15509 Print the names of all source files in your program for which there is
15510 debugging information, organized into two lists: files whose symbols
15511 have already been read, and files whose symbols will be read when needed.
15513 @kindex info functions
15514 @item info functions
15515 Print the names and data types of all defined functions.
15517 @item info functions @var{regexp}
15518 Print the names and data types of all defined functions
15519 whose names contain a match for regular expression @var{regexp}.
15520 Thus, @samp{info fun step} finds all functions whose names
15521 include @code{step}; @samp{info fun ^step} finds those whose names
15522 start with @code{step}. If a function name contains characters
15523 that conflict with the regular expression language (e.g.@:
15524 @samp{operator*()}), they may be quoted with a backslash.
15526 @kindex info variables
15527 @item info variables
15528 Print the names and data types of all variables that are defined
15529 outside of functions (i.e.@: excluding local variables).
15531 @item info variables @var{regexp}
15532 Print the names and data types of all variables (except for local
15533 variables) whose names contain a match for regular expression
15536 @kindex info classes
15537 @cindex Objective-C, classes and selectors
15539 @itemx info classes @var{regexp}
15540 Display all Objective-C classes in your program, or
15541 (with the @var{regexp} argument) all those matching a particular regular
15544 @kindex info selectors
15545 @item info selectors
15546 @itemx info selectors @var{regexp}
15547 Display all Objective-C selectors in your program, or
15548 (with the @var{regexp} argument) all those matching a particular regular
15552 This was never implemented.
15553 @kindex info methods
15555 @itemx info methods @var{regexp}
15556 The @code{info methods} command permits the user to examine all defined
15557 methods within C@t{++} program, or (with the @var{regexp} argument) a
15558 specific set of methods found in the various C@t{++} classes. Many
15559 C@t{++} classes provide a large number of methods. Thus, the output
15560 from the @code{ptype} command can be overwhelming and hard to use. The
15561 @code{info-methods} command filters the methods, printing only those
15562 which match the regular-expression @var{regexp}.
15565 @cindex opaque data types
15566 @kindex set opaque-type-resolution
15567 @item set opaque-type-resolution on
15568 Tell @value{GDBN} to resolve opaque types. An opaque type is a type
15569 declared as a pointer to a @code{struct}, @code{class}, or
15570 @code{union}---for example, @code{struct MyType *}---that is used in one
15571 source file although the full declaration of @code{struct MyType} is in
15572 another source file. The default is on.
15574 A change in the setting of this subcommand will not take effect until
15575 the next time symbols for a file are loaded.
15577 @item set opaque-type-resolution off
15578 Tell @value{GDBN} not to resolve opaque types. In this case, the type
15579 is printed as follows:
15581 @{<no data fields>@}
15584 @kindex show opaque-type-resolution
15585 @item show opaque-type-resolution
15586 Show whether opaque types are resolved or not.
15588 @kindex maint print symbols
15589 @cindex symbol dump
15590 @kindex maint print psymbols
15591 @cindex partial symbol dump
15592 @item maint print symbols @var{filename}
15593 @itemx maint print psymbols @var{filename}
15594 @itemx maint print msymbols @var{filename}
15595 Write a dump of debugging symbol data into the file @var{filename}.
15596 These commands are used to debug the @value{GDBN} symbol-reading code. Only
15597 symbols with debugging data are included. If you use @samp{maint print
15598 symbols}, @value{GDBN} includes all the symbols for which it has already
15599 collected full details: that is, @var{filename} reflects symbols for
15600 only those files whose symbols @value{GDBN} has read. You can use the
15601 command @code{info sources} to find out which files these are. If you
15602 use @samp{maint print psymbols} instead, the dump shows information about
15603 symbols that @value{GDBN} only knows partially---that is, symbols defined in
15604 files that @value{GDBN} has skimmed, but not yet read completely. Finally,
15605 @samp{maint print msymbols} dumps just the minimal symbol information
15606 required for each object file from which @value{GDBN} has read some symbols.
15607 @xref{Files, ,Commands to Specify Files}, for a discussion of how
15608 @value{GDBN} reads symbols (in the description of @code{symbol-file}).
15610 @kindex maint info symtabs
15611 @kindex maint info psymtabs
15612 @cindex listing @value{GDBN}'s internal symbol tables
15613 @cindex symbol tables, listing @value{GDBN}'s internal
15614 @cindex full symbol tables, listing @value{GDBN}'s internal
15615 @cindex partial symbol tables, listing @value{GDBN}'s internal
15616 @item maint info symtabs @r{[} @var{regexp} @r{]}
15617 @itemx maint info psymtabs @r{[} @var{regexp} @r{]}
15619 List the @code{struct symtab} or @code{struct partial_symtab}
15620 structures whose names match @var{regexp}. If @var{regexp} is not
15621 given, list them all. The output includes expressions which you can
15622 copy into a @value{GDBN} debugging this one to examine a particular
15623 structure in more detail. For example:
15626 (@value{GDBP}) maint info psymtabs dwarf2read
15627 @{ objfile /home/gnu/build/gdb/gdb
15628 ((struct objfile *) 0x82e69d0)
15629 @{ psymtab /home/gnu/src/gdb/dwarf2read.c
15630 ((struct partial_symtab *) 0x8474b10)
15633 text addresses 0x814d3c8 -- 0x8158074
15634 globals (* (struct partial_symbol **) 0x8507a08 @@ 9)
15635 statics (* (struct partial_symbol **) 0x40e95b78 @@ 2882)
15636 dependencies (none)
15639 (@value{GDBP}) maint info symtabs
15643 We see that there is one partial symbol table whose filename contains
15644 the string @samp{dwarf2read}, belonging to the @samp{gdb} executable;
15645 and we see that @value{GDBN} has not read in any symtabs yet at all.
15646 If we set a breakpoint on a function, that will cause @value{GDBN} to
15647 read the symtab for the compilation unit containing that function:
15650 (@value{GDBP}) break dwarf2_psymtab_to_symtab
15651 Breakpoint 1 at 0x814e5da: file /home/gnu/src/gdb/dwarf2read.c,
15653 (@value{GDBP}) maint info symtabs
15654 @{ objfile /home/gnu/build/gdb/gdb
15655 ((struct objfile *) 0x82e69d0)
15656 @{ symtab /home/gnu/src/gdb/dwarf2read.c
15657 ((struct symtab *) 0x86c1f38)
15660 blockvector ((struct blockvector *) 0x86c1bd0) (primary)
15661 linetable ((struct linetable *) 0x8370fa0)
15662 debugformat DWARF 2
15671 @chapter Altering Execution
15673 Once you think you have found an error in your program, you might want to
15674 find out for certain whether correcting the apparent error would lead to
15675 correct results in the rest of the run. You can find the answer by
15676 experiment, using the @value{GDBN} features for altering execution of the
15679 For example, you can store new values into variables or memory
15680 locations, give your program a signal, restart it at a different
15681 address, or even return prematurely from a function.
15684 * Assignment:: Assignment to variables
15685 * Jumping:: Continuing at a different address
15686 * Signaling:: Giving your program a signal
15687 * Returning:: Returning from a function
15688 * Calling:: Calling your program's functions
15689 * Patching:: Patching your program
15693 @section Assignment to Variables
15696 @cindex setting variables
15697 To alter the value of a variable, evaluate an assignment expression.
15698 @xref{Expressions, ,Expressions}. For example,
15705 stores the value 4 into the variable @code{x}, and then prints the
15706 value of the assignment expression (which is 4).
15707 @xref{Languages, ,Using @value{GDBN} with Different Languages}, for more
15708 information on operators in supported languages.
15710 @kindex set variable
15711 @cindex variables, setting
15712 If you are not interested in seeing the value of the assignment, use the
15713 @code{set} command instead of the @code{print} command. @code{set} is
15714 really the same as @code{print} except that the expression's value is
15715 not printed and is not put in the value history (@pxref{Value History,
15716 ,Value History}). The expression is evaluated only for its effects.
15718 If the beginning of the argument string of the @code{set} command
15719 appears identical to a @code{set} subcommand, use the @code{set
15720 variable} command instead of just @code{set}. This command is identical
15721 to @code{set} except for its lack of subcommands. For example, if your
15722 program has a variable @code{width}, you get an error if you try to set
15723 a new value with just @samp{set width=13}, because @value{GDBN} has the
15724 command @code{set width}:
15727 (@value{GDBP}) whatis width
15729 (@value{GDBP}) p width
15731 (@value{GDBP}) set width=47
15732 Invalid syntax in expression.
15736 The invalid expression, of course, is @samp{=47}. In
15737 order to actually set the program's variable @code{width}, use
15740 (@value{GDBP}) set var width=47
15743 Because the @code{set} command has many subcommands that can conflict
15744 with the names of program variables, it is a good idea to use the
15745 @code{set variable} command instead of just @code{set}. For example, if
15746 your program has a variable @code{g}, you run into problems if you try
15747 to set a new value with just @samp{set g=4}, because @value{GDBN} has
15748 the command @code{set gnutarget}, abbreviated @code{set g}:
15752 (@value{GDBP}) whatis g
15756 (@value{GDBP}) set g=4
15760 The program being debugged has been started already.
15761 Start it from the beginning? (y or n) y
15762 Starting program: /home/smith/cc_progs/a.out
15763 "/home/smith/cc_progs/a.out": can't open to read symbols:
15764 Invalid bfd target.
15765 (@value{GDBP}) show g
15766 The current BFD target is "=4".
15771 The program variable @code{g} did not change, and you silently set the
15772 @code{gnutarget} to an invalid value. In order to set the variable
15776 (@value{GDBP}) set var g=4
15779 @value{GDBN} allows more implicit conversions in assignments than C; you can
15780 freely store an integer value into a pointer variable or vice versa,
15781 and you can convert any structure to any other structure that is the
15782 same length or shorter.
15783 @comment FIXME: how do structs align/pad in these conversions?
15784 @comment /doc@cygnus.com 18dec1990
15786 To store values into arbitrary places in memory, use the @samp{@{@dots{}@}}
15787 construct to generate a value of specified type at a specified address
15788 (@pxref{Expressions, ,Expressions}). For example, @code{@{int@}0x83040} refers
15789 to memory location @code{0x83040} as an integer (which implies a certain size
15790 and representation in memory), and
15793 set @{int@}0x83040 = 4
15797 stores the value 4 into that memory location.
15800 @section Continuing at a Different Address
15802 Ordinarily, when you continue your program, you do so at the place where
15803 it stopped, with the @code{continue} command. You can instead continue at
15804 an address of your own choosing, with the following commands:
15808 @kindex j @r{(@code{jump})}
15809 @item jump @var{linespec}
15810 @itemx j @var{linespec}
15811 @itemx jump @var{location}
15812 @itemx j @var{location}
15813 Resume execution at line @var{linespec} or at address given by
15814 @var{location}. Execution stops again immediately if there is a
15815 breakpoint there. @xref{Specify Location}, for a description of the
15816 different forms of @var{linespec} and @var{location}. It is common
15817 practice to use the @code{tbreak} command in conjunction with
15818 @code{jump}. @xref{Set Breaks, ,Setting Breakpoints}.
15820 The @code{jump} command does not change the current stack frame, or
15821 the stack pointer, or the contents of any memory location or any
15822 register other than the program counter. If line @var{linespec} is in
15823 a different function from the one currently executing, the results may
15824 be bizarre if the two functions expect different patterns of arguments or
15825 of local variables. For this reason, the @code{jump} command requests
15826 confirmation if the specified line is not in the function currently
15827 executing. However, even bizarre results are predictable if you are
15828 well acquainted with the machine-language code of your program.
15831 @c Doesn't work on HP-UX; have to set $pcoqh and $pcoqt.
15832 On many systems, you can get much the same effect as the @code{jump}
15833 command by storing a new value into the register @code{$pc}. The
15834 difference is that this does not start your program running; it only
15835 changes the address of where it @emph{will} run when you continue. For
15843 makes the next @code{continue} command or stepping command execute at
15844 address @code{0x485}, rather than at the address where your program stopped.
15845 @xref{Continuing and Stepping, ,Continuing and Stepping}.
15847 The most common occasion to use the @code{jump} command is to back
15848 up---perhaps with more breakpoints set---over a portion of a program
15849 that has already executed, in order to examine its execution in more
15854 @section Giving your Program a Signal
15855 @cindex deliver a signal to a program
15859 @item signal @var{signal}
15860 Resume execution where your program stopped, but immediately give it the
15861 signal @var{signal}. @var{signal} can be the name or the number of a
15862 signal. For example, on many systems @code{signal 2} and @code{signal
15863 SIGINT} are both ways of sending an interrupt signal.
15865 Alternatively, if @var{signal} is zero, continue execution without
15866 giving a signal. This is useful when your program stopped on account of
15867 a signal and would ordinarily see the signal when resumed with the
15868 @code{continue} command; @samp{signal 0} causes it to resume without a
15871 @code{signal} does not repeat when you press @key{RET} a second time
15872 after executing the command.
15876 Invoking the @code{signal} command is not the same as invoking the
15877 @code{kill} utility from the shell. Sending a signal with @code{kill}
15878 causes @value{GDBN} to decide what to do with the signal depending on
15879 the signal handling tables (@pxref{Signals}). The @code{signal} command
15880 passes the signal directly to your program.
15884 @section Returning from a Function
15887 @cindex returning from a function
15890 @itemx return @var{expression}
15891 You can cancel execution of a function call with the @code{return}
15892 command. If you give an
15893 @var{expression} argument, its value is used as the function's return
15897 When you use @code{return}, @value{GDBN} discards the selected stack frame
15898 (and all frames within it). You can think of this as making the
15899 discarded frame return prematurely. If you wish to specify a value to
15900 be returned, give that value as the argument to @code{return}.
15902 This pops the selected stack frame (@pxref{Selection, ,Selecting a
15903 Frame}), and any other frames inside of it, leaving its caller as the
15904 innermost remaining frame. That frame becomes selected. The
15905 specified value is stored in the registers used for returning values
15908 The @code{return} command does not resume execution; it leaves the
15909 program stopped in the state that would exist if the function had just
15910 returned. In contrast, the @code{finish} command (@pxref{Continuing
15911 and Stepping, ,Continuing and Stepping}) resumes execution until the
15912 selected stack frame returns naturally.
15914 @value{GDBN} needs to know how the @var{expression} argument should be set for
15915 the inferior. The concrete registers assignment depends on the OS ABI and the
15916 type being returned by the selected stack frame. For example it is common for
15917 OS ABI to return floating point values in FPU registers while integer values in
15918 CPU registers. Still some ABIs return even floating point values in CPU
15919 registers. Larger integer widths (such as @code{long long int}) also have
15920 specific placement rules. @value{GDBN} already knows the OS ABI from its
15921 current target so it needs to find out also the type being returned to make the
15922 assignment into the right register(s).
15924 Normally, the selected stack frame has debug info. @value{GDBN} will always
15925 use the debug info instead of the implicit type of @var{expression} when the
15926 debug info is available. For example, if you type @kbd{return -1}, and the
15927 function in the current stack frame is declared to return a @code{long long
15928 int}, @value{GDBN} transparently converts the implicit @code{int} value of -1
15929 into a @code{long long int}:
15932 Breakpoint 1, func () at gdb.base/return-nodebug.c:29
15934 (@value{GDBP}) return -1
15935 Make func return now? (y or n) y
15936 #0 0x004004f6 in main () at gdb.base/return-nodebug.c:43
15937 43 printf ("result=%lld\n", func ());
15941 However, if the selected stack frame does not have a debug info, e.g., if the
15942 function was compiled without debug info, @value{GDBN} has to find out the type
15943 to return from user. Specifying a different type by mistake may set the value
15944 in different inferior registers than the caller code expects. For example,
15945 typing @kbd{return -1} with its implicit type @code{int} would set only a part
15946 of a @code{long long int} result for a debug info less function (on 32-bit
15947 architectures). Therefore the user is required to specify the return type by
15948 an appropriate cast explicitly:
15951 Breakpoint 2, 0x0040050b in func ()
15952 (@value{GDBP}) return -1
15953 Return value type not available for selected stack frame.
15954 Please use an explicit cast of the value to return.
15955 (@value{GDBP}) return (long long int) -1
15956 Make selected stack frame return now? (y or n) y
15957 #0 0x00400526 in main ()
15962 @section Calling Program Functions
15965 @cindex calling functions
15966 @cindex inferior functions, calling
15967 @item print @var{expr}
15968 Evaluate the expression @var{expr} and display the resulting value.
15969 @var{expr} may include calls to functions in the program being
15973 @item call @var{expr}
15974 Evaluate the expression @var{expr} without displaying @code{void}
15977 You can use this variant of the @code{print} command if you want to
15978 execute a function from your program that does not return anything
15979 (a.k.a.@: @dfn{a void function}), but without cluttering the output
15980 with @code{void} returned values that @value{GDBN} will otherwise
15981 print. If the result is not void, it is printed and saved in the
15985 It is possible for the function you call via the @code{print} or
15986 @code{call} command to generate a signal (e.g., if there's a bug in
15987 the function, or if you passed it incorrect arguments). What happens
15988 in that case is controlled by the @code{set unwindonsignal} command.
15990 Similarly, with a C@t{++} program it is possible for the function you
15991 call via the @code{print} or @code{call} command to generate an
15992 exception that is not handled due to the constraints of the dummy
15993 frame. In this case, any exception that is raised in the frame, but has
15994 an out-of-frame exception handler will not be found. GDB builds a
15995 dummy-frame for the inferior function call, and the unwinder cannot
15996 seek for exception handlers outside of this dummy-frame. What happens
15997 in that case is controlled by the
15998 @code{set unwind-on-terminating-exception} command.
16001 @item set unwindonsignal
16002 @kindex set unwindonsignal
16003 @cindex unwind stack in called functions
16004 @cindex call dummy stack unwinding
16005 Set unwinding of the stack if a signal is received while in a function
16006 that @value{GDBN} called in the program being debugged. If set to on,
16007 @value{GDBN} unwinds the stack it created for the call and restores
16008 the context to what it was before the call. If set to off (the
16009 default), @value{GDBN} stops in the frame where the signal was
16012 @item show unwindonsignal
16013 @kindex show unwindonsignal
16014 Show the current setting of stack unwinding in the functions called by
16017 @item set unwind-on-terminating-exception
16018 @kindex set unwind-on-terminating-exception
16019 @cindex unwind stack in called functions with unhandled exceptions
16020 @cindex call dummy stack unwinding on unhandled exception.
16021 Set unwinding of the stack if a C@t{++} exception is raised, but left
16022 unhandled while in a function that @value{GDBN} called in the program being
16023 debugged. If set to on (the default), @value{GDBN} unwinds the stack
16024 it created for the call and restores the context to what it was before
16025 the call. If set to off, @value{GDBN} the exception is delivered to
16026 the default C@t{++} exception handler and the inferior terminated.
16028 @item show unwind-on-terminating-exception
16029 @kindex show unwind-on-terminating-exception
16030 Show the current setting of stack unwinding in the functions called by
16035 @cindex weak alias functions
16036 Sometimes, a function you wish to call is actually a @dfn{weak alias}
16037 for another function. In such case, @value{GDBN} might not pick up
16038 the type information, including the types of the function arguments,
16039 which causes @value{GDBN} to call the inferior function incorrectly.
16040 As a result, the called function will function erroneously and may
16041 even crash. A solution to that is to use the name of the aliased
16045 @section Patching Programs
16047 @cindex patching binaries
16048 @cindex writing into executables
16049 @cindex writing into corefiles
16051 By default, @value{GDBN} opens the file containing your program's
16052 executable code (or the corefile) read-only. This prevents accidental
16053 alterations to machine code; but it also prevents you from intentionally
16054 patching your program's binary.
16056 If you'd like to be able to patch the binary, you can specify that
16057 explicitly with the @code{set write} command. For example, you might
16058 want to turn on internal debugging flags, or even to make emergency
16064 @itemx set write off
16065 If you specify @samp{set write on}, @value{GDBN} opens executable and
16066 core files for both reading and writing; if you specify @kbd{set write
16067 off} (the default), @value{GDBN} opens them read-only.
16069 If you have already loaded a file, you must load it again (using the
16070 @code{exec-file} or @code{core-file} command) after changing @code{set
16071 write}, for your new setting to take effect.
16075 Display whether executable files and core files are opened for writing
16076 as well as reading.
16080 @chapter @value{GDBN} Files
16082 @value{GDBN} needs to know the file name of the program to be debugged,
16083 both in order to read its symbol table and in order to start your
16084 program. To debug a core dump of a previous run, you must also tell
16085 @value{GDBN} the name of the core dump file.
16088 * Files:: Commands to specify files
16089 * Separate Debug Files:: Debugging information in separate files
16090 * MiniDebugInfo:: Debugging information in a special section
16091 * Index Files:: Index files speed up GDB
16092 * Symbol Errors:: Errors reading symbol files
16093 * Data Files:: GDB data files
16097 @section Commands to Specify Files
16099 @cindex symbol table
16100 @cindex core dump file
16102 You may want to specify executable and core dump file names. The usual
16103 way to do this is at start-up time, using the arguments to
16104 @value{GDBN}'s start-up commands (@pxref{Invocation, , Getting In and
16105 Out of @value{GDBN}}).
16107 Occasionally it is necessary to change to a different file during a
16108 @value{GDBN} session. Or you may run @value{GDBN} and forget to
16109 specify a file you want to use. Or you are debugging a remote target
16110 via @code{gdbserver} (@pxref{Server, file, Using the @code{gdbserver}
16111 Program}). In these situations the @value{GDBN} commands to specify
16112 new files are useful.
16115 @cindex executable file
16117 @item file @var{filename}
16118 Use @var{filename} as the program to be debugged. It is read for its
16119 symbols and for the contents of pure memory. It is also the program
16120 executed when you use the @code{run} command. If you do not specify a
16121 directory and the file is not found in the @value{GDBN} working directory,
16122 @value{GDBN} uses the environment variable @code{PATH} as a list of
16123 directories to search, just as the shell does when looking for a program
16124 to run. You can change the value of this variable, for both @value{GDBN}
16125 and your program, using the @code{path} command.
16127 @cindex unlinked object files
16128 @cindex patching object files
16129 You can load unlinked object @file{.o} files into @value{GDBN} using
16130 the @code{file} command. You will not be able to ``run'' an object
16131 file, but you can disassemble functions and inspect variables. Also,
16132 if the underlying BFD functionality supports it, you could use
16133 @kbd{gdb -write} to patch object files using this technique. Note
16134 that @value{GDBN} can neither interpret nor modify relocations in this
16135 case, so branches and some initialized variables will appear to go to
16136 the wrong place. But this feature is still handy from time to time.
16139 @code{file} with no argument makes @value{GDBN} discard any information it
16140 has on both executable file and the symbol table.
16143 @item exec-file @r{[} @var{filename} @r{]}
16144 Specify that the program to be run (but not the symbol table) is found
16145 in @var{filename}. @value{GDBN} searches the environment variable @code{PATH}
16146 if necessary to locate your program. Omitting @var{filename} means to
16147 discard information on the executable file.
16149 @kindex symbol-file
16150 @item symbol-file @r{[} @var{filename} @r{]}
16151 Read symbol table information from file @var{filename}. @code{PATH} is
16152 searched when necessary. Use the @code{file} command to get both symbol
16153 table and program to run from the same file.
16155 @code{symbol-file} with no argument clears out @value{GDBN} information on your
16156 program's symbol table.
16158 The @code{symbol-file} command causes @value{GDBN} to forget the contents of
16159 some breakpoints and auto-display expressions. This is because they may
16160 contain pointers to the internal data recording symbols and data types,
16161 which are part of the old symbol table data being discarded inside
16164 @code{symbol-file} does not repeat if you press @key{RET} again after
16167 When @value{GDBN} is configured for a particular environment, it
16168 understands debugging information in whatever format is the standard
16169 generated for that environment; you may use either a @sc{gnu} compiler, or
16170 other compilers that adhere to the local conventions.
16171 Best results are usually obtained from @sc{gnu} compilers; for example,
16172 using @code{@value{NGCC}} you can generate debugging information for
16175 For most kinds of object files, with the exception of old SVR3 systems
16176 using COFF, the @code{symbol-file} command does not normally read the
16177 symbol table in full right away. Instead, it scans the symbol table
16178 quickly to find which source files and which symbols are present. The
16179 details are read later, one source file at a time, as they are needed.
16181 The purpose of this two-stage reading strategy is to make @value{GDBN}
16182 start up faster. For the most part, it is invisible except for
16183 occasional pauses while the symbol table details for a particular source
16184 file are being read. (The @code{set verbose} command can turn these
16185 pauses into messages if desired. @xref{Messages/Warnings, ,Optional
16186 Warnings and Messages}.)
16188 We have not implemented the two-stage strategy for COFF yet. When the
16189 symbol table is stored in COFF format, @code{symbol-file} reads the
16190 symbol table data in full right away. Note that ``stabs-in-COFF''
16191 still does the two-stage strategy, since the debug info is actually
16195 @cindex reading symbols immediately
16196 @cindex symbols, reading immediately
16197 @item symbol-file @r{[} -readnow @r{]} @var{filename}
16198 @itemx file @r{[} -readnow @r{]} @var{filename}
16199 You can override the @value{GDBN} two-stage strategy for reading symbol
16200 tables by using the @samp{-readnow} option with any of the commands that
16201 load symbol table information, if you want to be sure @value{GDBN} has the
16202 entire symbol table available.
16204 @c FIXME: for now no mention of directories, since this seems to be in
16205 @c flux. 13mar1992 status is that in theory GDB would look either in
16206 @c current dir or in same dir as myprog; but issues like competing
16207 @c GDB's, or clutter in system dirs, mean that in practice right now
16208 @c only current dir is used. FFish says maybe a special GDB hierarchy
16209 @c (eg rooted in val of env var GDBSYMS) could exist for mappable symbol
16213 @item core-file @r{[}@var{filename}@r{]}
16215 Specify the whereabouts of a core dump file to be used as the ``contents
16216 of memory''. Traditionally, core files contain only some parts of the
16217 address space of the process that generated them; @value{GDBN} can access the
16218 executable file itself for other parts.
16220 @code{core-file} with no argument specifies that no core file is
16223 Note that the core file is ignored when your program is actually running
16224 under @value{GDBN}. So, if you have been running your program and you
16225 wish to debug a core file instead, you must kill the subprocess in which
16226 the program is running. To do this, use the @code{kill} command
16227 (@pxref{Kill Process, ,Killing the Child Process}).
16229 @kindex add-symbol-file
16230 @cindex dynamic linking
16231 @item add-symbol-file @var{filename} @var{address}
16232 @itemx add-symbol-file @var{filename} @var{address} @r{[} -readnow @r{]}
16233 @itemx add-symbol-file @var{filename} @var{address} -s @var{section} @var{address} @dots{}
16234 The @code{add-symbol-file} command reads additional symbol table
16235 information from the file @var{filename}. You would use this command
16236 when @var{filename} has been dynamically loaded (by some other means)
16237 into the program that is running. @var{address} should be the memory
16238 address at which the file has been loaded; @value{GDBN} cannot figure
16239 this out for itself. You can additionally specify an arbitrary number
16240 of @samp{-s @var{section} @var{address}} pairs, to give an explicit
16241 section name and base address for that section. You can specify any
16242 @var{address} as an expression.
16244 The symbol table of the file @var{filename} is added to the symbol table
16245 originally read with the @code{symbol-file} command. You can use the
16246 @code{add-symbol-file} command any number of times; the new symbol data
16247 thus read keeps adding to the old. To discard all old symbol data
16248 instead, use the @code{symbol-file} command without any arguments.
16250 @cindex relocatable object files, reading symbols from
16251 @cindex object files, relocatable, reading symbols from
16252 @cindex reading symbols from relocatable object files
16253 @cindex symbols, reading from relocatable object files
16254 @cindex @file{.o} files, reading symbols from
16255 Although @var{filename} is typically a shared library file, an
16256 executable file, or some other object file which has been fully
16257 relocated for loading into a process, you can also load symbolic
16258 information from relocatable @file{.o} files, as long as:
16262 the file's symbolic information refers only to linker symbols defined in
16263 that file, not to symbols defined by other object files,
16265 every section the file's symbolic information refers to has actually
16266 been loaded into the inferior, as it appears in the file, and
16268 you can determine the address at which every section was loaded, and
16269 provide these to the @code{add-symbol-file} command.
16273 Some embedded operating systems, like Sun Chorus and VxWorks, can load
16274 relocatable files into an already running program; such systems
16275 typically make the requirements above easy to meet. However, it's
16276 important to recognize that many native systems use complex link
16277 procedures (@code{.linkonce} section factoring and C@t{++} constructor table
16278 assembly, for example) that make the requirements difficult to meet. In
16279 general, one cannot assume that using @code{add-symbol-file} to read a
16280 relocatable object file's symbolic information will have the same effect
16281 as linking the relocatable object file into the program in the normal
16284 @code{add-symbol-file} does not repeat if you press @key{RET} after using it.
16286 @kindex add-symbol-file-from-memory
16287 @cindex @code{syscall DSO}
16288 @cindex load symbols from memory
16289 @item add-symbol-file-from-memory @var{address}
16290 Load symbols from the given @var{address} in a dynamically loaded
16291 object file whose image is mapped directly into the inferior's memory.
16292 For example, the Linux kernel maps a @code{syscall DSO} into each
16293 process's address space; this DSO provides kernel-specific code for
16294 some system calls. The argument can be any expression whose
16295 evaluation yields the address of the file's shared object file header.
16296 For this command to work, you must have used @code{symbol-file} or
16297 @code{exec-file} commands in advance.
16299 @kindex add-shared-symbol-files
16301 @item add-shared-symbol-files @var{library-file}
16302 @itemx assf @var{library-file}
16303 The @code{add-shared-symbol-files} command can currently be used only
16304 in the Cygwin build of @value{GDBN} on MS-Windows OS, where it is an
16305 alias for the @code{dll-symbols} command (@pxref{Cygwin Native}).
16306 @value{GDBN} automatically looks for shared libraries, however if
16307 @value{GDBN} does not find yours, you can invoke
16308 @code{add-shared-symbol-files}. It takes one argument: the shared
16309 library's file name. @code{assf} is a shorthand alias for
16310 @code{add-shared-symbol-files}.
16313 @item section @var{section} @var{addr}
16314 The @code{section} command changes the base address of the named
16315 @var{section} of the exec file to @var{addr}. This can be used if the
16316 exec file does not contain section addresses, (such as in the
16317 @code{a.out} format), or when the addresses specified in the file
16318 itself are wrong. Each section must be changed separately. The
16319 @code{info files} command, described below, lists all the sections and
16323 @kindex info target
16326 @code{info files} and @code{info target} are synonymous; both print the
16327 current target (@pxref{Targets, ,Specifying a Debugging Target}),
16328 including the names of the executable and core dump files currently in
16329 use by @value{GDBN}, and the files from which symbols were loaded. The
16330 command @code{help target} lists all possible targets rather than
16333 @kindex maint info sections
16334 @item maint info sections
16335 Another command that can give you extra information about program sections
16336 is @code{maint info sections}. In addition to the section information
16337 displayed by @code{info files}, this command displays the flags and file
16338 offset of each section in the executable and core dump files. In addition,
16339 @code{maint info sections} provides the following command options (which
16340 may be arbitrarily combined):
16344 Display sections for all loaded object files, including shared libraries.
16345 @item @var{sections}
16346 Display info only for named @var{sections}.
16347 @item @var{section-flags}
16348 Display info only for sections for which @var{section-flags} are true.
16349 The section flags that @value{GDBN} currently knows about are:
16352 Section will have space allocated in the process when loaded.
16353 Set for all sections except those containing debug information.
16355 Section will be loaded from the file into the child process memory.
16356 Set for pre-initialized code and data, clear for @code{.bss} sections.
16358 Section needs to be relocated before loading.
16360 Section cannot be modified by the child process.
16362 Section contains executable code only.
16364 Section contains data only (no executable code).
16366 Section will reside in ROM.
16368 Section contains data for constructor/destructor lists.
16370 Section is not empty.
16372 An instruction to the linker to not output the section.
16373 @item COFF_SHARED_LIBRARY
16374 A notification to the linker that the section contains
16375 COFF shared library information.
16377 Section contains common symbols.
16380 @kindex set trust-readonly-sections
16381 @cindex read-only sections
16382 @item set trust-readonly-sections on
16383 Tell @value{GDBN} that readonly sections in your object file
16384 really are read-only (i.e.@: that their contents will not change).
16385 In that case, @value{GDBN} can fetch values from these sections
16386 out of the object file, rather than from the target program.
16387 For some targets (notably embedded ones), this can be a significant
16388 enhancement to debugging performance.
16390 The default is off.
16392 @item set trust-readonly-sections off
16393 Tell @value{GDBN} not to trust readonly sections. This means that
16394 the contents of the section might change while the program is running,
16395 and must therefore be fetched from the target when needed.
16397 @item show trust-readonly-sections
16398 Show the current setting of trusting readonly sections.
16401 All file-specifying commands allow both absolute and relative file names
16402 as arguments. @value{GDBN} always converts the file name to an absolute file
16403 name and remembers it that way.
16405 @cindex shared libraries
16406 @anchor{Shared Libraries}
16407 @value{GDBN} supports @sc{gnu}/Linux, MS-Windows, HP-UX, SunOS, SVr4, Irix,
16408 and IBM RS/6000 AIX shared libraries.
16410 On MS-Windows @value{GDBN} must be linked with the Expat library to support
16411 shared libraries. @xref{Expat}.
16413 @value{GDBN} automatically loads symbol definitions from shared libraries
16414 when you use the @code{run} command, or when you examine a core file.
16415 (Before you issue the @code{run} command, @value{GDBN} does not understand
16416 references to a function in a shared library, however---unless you are
16417 debugging a core file).
16419 On HP-UX, if the program loads a library explicitly, @value{GDBN}
16420 automatically loads the symbols at the time of the @code{shl_load} call.
16422 @c FIXME: some @value{GDBN} release may permit some refs to undef
16423 @c FIXME...symbols---eg in a break cmd---assuming they are from a shared
16424 @c FIXME...lib; check this from time to time when updating manual
16426 There are times, however, when you may wish to not automatically load
16427 symbol definitions from shared libraries, such as when they are
16428 particularly large or there are many of them.
16430 To control the automatic loading of shared library symbols, use the
16434 @kindex set auto-solib-add
16435 @item set auto-solib-add @var{mode}
16436 If @var{mode} is @code{on}, symbols from all shared object libraries
16437 will be loaded automatically when the inferior begins execution, you
16438 attach to an independently started inferior, or when the dynamic linker
16439 informs @value{GDBN} that a new library has been loaded. If @var{mode}
16440 is @code{off}, symbols must be loaded manually, using the
16441 @code{sharedlibrary} command. The default value is @code{on}.
16443 @cindex memory used for symbol tables
16444 If your program uses lots of shared libraries with debug info that
16445 takes large amounts of memory, you can decrease the @value{GDBN}
16446 memory footprint by preventing it from automatically loading the
16447 symbols from shared libraries. To that end, type @kbd{set
16448 auto-solib-add off} before running the inferior, then load each
16449 library whose debug symbols you do need with @kbd{sharedlibrary
16450 @var{regexp}}, where @var{regexp} is a regular expression that matches
16451 the libraries whose symbols you want to be loaded.
16453 @kindex show auto-solib-add
16454 @item show auto-solib-add
16455 Display the current autoloading mode.
16458 @cindex load shared library
16459 To explicitly load shared library symbols, use the @code{sharedlibrary}
16463 @kindex info sharedlibrary
16465 @item info share @var{regex}
16466 @itemx info sharedlibrary @var{regex}
16467 Print the names of the shared libraries which are currently loaded
16468 that match @var{regex}. If @var{regex} is omitted then print
16469 all shared libraries that are loaded.
16471 @kindex sharedlibrary
16473 @item sharedlibrary @var{regex}
16474 @itemx share @var{regex}
16475 Load shared object library symbols for files matching a
16476 Unix regular expression.
16477 As with files loaded automatically, it only loads shared libraries
16478 required by your program for a core file or after typing @code{run}. If
16479 @var{regex} is omitted all shared libraries required by your program are
16482 @item nosharedlibrary
16483 @kindex nosharedlibrary
16484 @cindex unload symbols from shared libraries
16485 Unload all shared object library symbols. This discards all symbols
16486 that have been loaded from all shared libraries. Symbols from shared
16487 libraries that were loaded by explicit user requests are not
16491 Sometimes you may wish that @value{GDBN} stops and gives you control
16492 when any of shared library events happen. The best way to do this is
16493 to use @code{catch load} and @code{catch unload} (@pxref{Set
16496 @value{GDBN} also supports the the @code{set stop-on-solib-events}
16497 command for this. This command exists for historical reasons. It is
16498 less useful than setting a catchpoint, because it does not allow for
16499 conditions or commands as a catchpoint does.
16502 @item set stop-on-solib-events
16503 @kindex set stop-on-solib-events
16504 This command controls whether @value{GDBN} should give you control
16505 when the dynamic linker notifies it about some shared library event.
16506 The most common event of interest is loading or unloading of a new
16509 @item show stop-on-solib-events
16510 @kindex show stop-on-solib-events
16511 Show whether @value{GDBN} stops and gives you control when shared
16512 library events happen.
16515 Shared libraries are also supported in many cross or remote debugging
16516 configurations. @value{GDBN} needs to have access to the target's libraries;
16517 this can be accomplished either by providing copies of the libraries
16518 on the host system, or by asking @value{GDBN} to automatically retrieve the
16519 libraries from the target. If copies of the target libraries are
16520 provided, they need to be the same as the target libraries, although the
16521 copies on the target can be stripped as long as the copies on the host are
16524 @cindex where to look for shared libraries
16525 For remote debugging, you need to tell @value{GDBN} where the target
16526 libraries are, so that it can load the correct copies---otherwise, it
16527 may try to load the host's libraries. @value{GDBN} has two variables
16528 to specify the search directories for target libraries.
16531 @cindex prefix for shared library file names
16532 @cindex system root, alternate
16533 @kindex set solib-absolute-prefix
16534 @kindex set sysroot
16535 @item set sysroot @var{path}
16536 Use @var{path} as the system root for the program being debugged. Any
16537 absolute shared library paths will be prefixed with @var{path}; many
16538 runtime loaders store the absolute paths to the shared library in the
16539 target program's memory. If you use @code{set sysroot} to find shared
16540 libraries, they need to be laid out in the same way that they are on
16541 the target, with e.g.@: a @file{/lib} and @file{/usr/lib} hierarchy
16544 If @var{path} starts with the sequence @file{remote:}, @value{GDBN} will
16545 retrieve the target libraries from the remote system. This is only
16546 supported when using a remote target that supports the @code{remote get}
16547 command (@pxref{File Transfer,,Sending files to a remote system}).
16548 The part of @var{path} following the initial @file{remote:}
16549 (if present) is used as system root prefix on the remote file system.
16550 @footnote{If you want to specify a local system root using a directory
16551 that happens to be named @file{remote:}, you need to use some equivalent
16552 variant of the name like @file{./remote:}.}
16554 For targets with an MS-DOS based filesystem, such as MS-Windows and
16555 SymbianOS, @value{GDBN} tries prefixing a few variants of the target
16556 absolute file name with @var{path}. But first, on Unix hosts,
16557 @value{GDBN} converts all backslash directory separators into forward
16558 slashes, because the backslash is not a directory separator on Unix:
16561 c:\foo\bar.dll @result{} c:/foo/bar.dll
16564 Then, @value{GDBN} attempts prefixing the target file name with
16565 @var{path}, and looks for the resulting file name in the host file
16569 c:/foo/bar.dll @result{} /path/to/sysroot/c:/foo/bar.dll
16572 If that does not find the shared library, @value{GDBN} tries removing
16573 the @samp{:} character from the drive spec, both for convenience, and,
16574 for the case of the host file system not supporting file names with
16578 c:/foo/bar.dll @result{} /path/to/sysroot/c/foo/bar.dll
16581 This makes it possible to have a system root that mirrors a target
16582 with more than one drive. E.g., you may want to setup your local
16583 copies of the target system shared libraries like so (note @samp{c} vs
16587 @file{/path/to/sysroot/c/sys/bin/foo.dll}
16588 @file{/path/to/sysroot/c/sys/bin/bar.dll}
16589 @file{/path/to/sysroot/z/sys/bin/bar.dll}
16593 and point the system root at @file{/path/to/sysroot}, so that
16594 @value{GDBN} can find the correct copies of both
16595 @file{c:\sys\bin\foo.dll}, and @file{z:\sys\bin\bar.dll}.
16597 If that still does not find the shared library, @value{GDBN} tries
16598 removing the whole drive spec from the target file name:
16601 c:/foo/bar.dll @result{} /path/to/sysroot/foo/bar.dll
16604 This last lookup makes it possible to not care about the drive name,
16605 if you don't want or need to.
16607 The @code{set solib-absolute-prefix} command is an alias for @code{set
16610 @cindex default system root
16611 @cindex @samp{--with-sysroot}
16612 You can set the default system root by using the configure-time
16613 @samp{--with-sysroot} option. If the system root is inside
16614 @value{GDBN}'s configured binary prefix (set with @samp{--prefix} or
16615 @samp{--exec-prefix}), then the default system root will be updated
16616 automatically if the installed @value{GDBN} is moved to a new
16619 @kindex show sysroot
16621 Display the current shared library prefix.
16623 @kindex set solib-search-path
16624 @item set solib-search-path @var{path}
16625 If this variable is set, @var{path} is a colon-separated list of
16626 directories to search for shared libraries. @samp{solib-search-path}
16627 is used after @samp{sysroot} fails to locate the library, or if the
16628 path to the library is relative instead of absolute. If you want to
16629 use @samp{solib-search-path} instead of @samp{sysroot}, be sure to set
16630 @samp{sysroot} to a nonexistent directory to prevent @value{GDBN} from
16631 finding your host's libraries. @samp{sysroot} is preferred; setting
16632 it to a nonexistent directory may interfere with automatic loading
16633 of shared library symbols.
16635 @kindex show solib-search-path
16636 @item show solib-search-path
16637 Display the current shared library search path.
16639 @cindex DOS file-name semantics of file names.
16640 @kindex set target-file-system-kind (unix|dos-based|auto)
16641 @kindex show target-file-system-kind
16642 @item set target-file-system-kind @var{kind}
16643 Set assumed file system kind for target reported file names.
16645 Shared library file names as reported by the target system may not
16646 make sense as is on the system @value{GDBN} is running on. For
16647 example, when remote debugging a target that has MS-DOS based file
16648 system semantics, from a Unix host, the target may be reporting to
16649 @value{GDBN} a list of loaded shared libraries with file names such as
16650 @file{c:\Windows\kernel32.dll}. On Unix hosts, there's no concept of
16651 drive letters, so the @samp{c:\} prefix is not normally understood as
16652 indicating an absolute file name, and neither is the backslash
16653 normally considered a directory separator character. In that case,
16654 the native file system would interpret this whole absolute file name
16655 as a relative file name with no directory components. This would make
16656 it impossible to point @value{GDBN} at a copy of the remote target's
16657 shared libraries on the host using @code{set sysroot}, and impractical
16658 with @code{set solib-search-path}. Setting
16659 @code{target-file-system-kind} to @code{dos-based} tells @value{GDBN}
16660 to interpret such file names similarly to how the target would, and to
16661 map them to file names valid on @value{GDBN}'s native file system
16662 semantics. The value of @var{kind} can be @code{"auto"}, in addition
16663 to one of the supported file system kinds. In that case, @value{GDBN}
16664 tries to determine the appropriate file system variant based on the
16665 current target's operating system (@pxref{ABI, ,Configuring the
16666 Current ABI}). The supported file system settings are:
16670 Instruct @value{GDBN} to assume the target file system is of Unix
16671 kind. Only file names starting the forward slash (@samp{/}) character
16672 are considered absolute, and the directory separator character is also
16676 Instruct @value{GDBN} to assume the target file system is DOS based.
16677 File names starting with either a forward slash, or a drive letter
16678 followed by a colon (e.g., @samp{c:}), are considered absolute, and
16679 both the slash (@samp{/}) and the backslash (@samp{\\}) characters are
16680 considered directory separators.
16683 Instruct @value{GDBN} to use the file system kind associated with the
16684 target operating system (@pxref{ABI, ,Configuring the Current ABI}).
16685 This is the default.
16689 @cindex file name canonicalization
16690 @cindex base name differences
16691 When processing file names provided by the user, @value{GDBN}
16692 frequently needs to compare them to the file names recorded in the
16693 program's debug info. Normally, @value{GDBN} compares just the
16694 @dfn{base names} of the files as strings, which is reasonably fast
16695 even for very large programs. (The base name of a file is the last
16696 portion of its name, after stripping all the leading directories.)
16697 This shortcut in comparison is based upon the assumption that files
16698 cannot have more than one base name. This is usually true, but
16699 references to files that use symlinks or similar filesystem
16700 facilities violate that assumption. If your program records files
16701 using such facilities, or if you provide file names to @value{GDBN}
16702 using symlinks etc., you can set @code{basenames-may-differ} to
16703 @code{true} to instruct @value{GDBN} to completely canonicalize each
16704 pair of file names it needs to compare. This will make file-name
16705 comparisons accurate, but at a price of a significant slowdown.
16708 @item set basenames-may-differ
16709 @kindex set basenames-may-differ
16710 Set whether a source file may have multiple base names.
16712 @item show basenames-may-differ
16713 @kindex show basenames-may-differ
16714 Show whether a source file may have multiple base names.
16717 @node Separate Debug Files
16718 @section Debugging Information in Separate Files
16719 @cindex separate debugging information files
16720 @cindex debugging information in separate files
16721 @cindex @file{.debug} subdirectories
16722 @cindex debugging information directory, global
16723 @cindex global debugging information directories
16724 @cindex build ID, and separate debugging files
16725 @cindex @file{.build-id} directory
16727 @value{GDBN} allows you to put a program's debugging information in a
16728 file separate from the executable itself, in a way that allows
16729 @value{GDBN} to find and load the debugging information automatically.
16730 Since debugging information can be very large---sometimes larger
16731 than the executable code itself---some systems distribute debugging
16732 information for their executables in separate files, which users can
16733 install only when they need to debug a problem.
16735 @value{GDBN} supports two ways of specifying the separate debug info
16740 The executable contains a @dfn{debug link} that specifies the name of
16741 the separate debug info file. The separate debug file's name is
16742 usually @file{@var{executable}.debug}, where @var{executable} is the
16743 name of the corresponding executable file without leading directories
16744 (e.g., @file{ls.debug} for @file{/usr/bin/ls}). In addition, the
16745 debug link specifies a 32-bit @dfn{Cyclic Redundancy Check} (CRC)
16746 checksum for the debug file, which @value{GDBN} uses to validate that
16747 the executable and the debug file came from the same build.
16750 The executable contains a @dfn{build ID}, a unique bit string that is
16751 also present in the corresponding debug info file. (This is supported
16752 only on some operating systems, notably those which use the ELF format
16753 for binary files and the @sc{gnu} Binutils.) For more details about
16754 this feature, see the description of the @option{--build-id}
16755 command-line option in @ref{Options, , Command Line Options, ld.info,
16756 The GNU Linker}. The debug info file's name is not specified
16757 explicitly by the build ID, but can be computed from the build ID, see
16761 Depending on the way the debug info file is specified, @value{GDBN}
16762 uses two different methods of looking for the debug file:
16766 For the ``debug link'' method, @value{GDBN} looks up the named file in
16767 the directory of the executable file, then in a subdirectory of that
16768 directory named @file{.debug}, and finally under each one of the global debug
16769 directories, in a subdirectory whose name is identical to the leading
16770 directories of the executable's absolute file name.
16773 For the ``build ID'' method, @value{GDBN} looks in the
16774 @file{.build-id} subdirectory of each one of the global debug directories for
16775 a file named @file{@var{nn}/@var{nnnnnnnn}.debug}, where @var{nn} are the
16776 first 2 hex characters of the build ID bit string, and @var{nnnnnnnn}
16777 are the rest of the bit string. (Real build ID strings are 32 or more
16778 hex characters, not 10.)
16781 So, for example, suppose you ask @value{GDBN} to debug
16782 @file{/usr/bin/ls}, which has a debug link that specifies the
16783 file @file{ls.debug}, and a build ID whose value in hex is
16784 @code{abcdef1234}. If the list of the global debug directories includes
16785 @file{/usr/lib/debug}, then @value{GDBN} will look for the following
16786 debug information files, in the indicated order:
16790 @file{/usr/lib/debug/.build-id/ab/cdef1234.debug}
16792 @file{/usr/bin/ls.debug}
16794 @file{/usr/bin/.debug/ls.debug}
16796 @file{/usr/lib/debug/usr/bin/ls.debug}.
16799 @anchor{debug-file-directory}
16800 Global debugging info directories default to what is set by @value{GDBN}
16801 configure option @option{--with-separate-debug-dir}. During @value{GDBN} run
16802 you can also set the global debugging info directories, and view the list
16803 @value{GDBN} is currently using.
16807 @kindex set debug-file-directory
16808 @item set debug-file-directory @var{directories}
16809 Set the directories which @value{GDBN} searches for separate debugging
16810 information files to @var{directory}. Multiple path components can be set
16811 concatenating them by a path separator.
16813 @kindex show debug-file-directory
16814 @item show debug-file-directory
16815 Show the directories @value{GDBN} searches for separate debugging
16820 @cindex @code{.gnu_debuglink} sections
16821 @cindex debug link sections
16822 A debug link is a special section of the executable file named
16823 @code{.gnu_debuglink}. The section must contain:
16827 A filename, with any leading directory components removed, followed by
16830 zero to three bytes of padding, as needed to reach the next four-byte
16831 boundary within the section, and
16833 a four-byte CRC checksum, stored in the same endianness used for the
16834 executable file itself. The checksum is computed on the debugging
16835 information file's full contents by the function given below, passing
16836 zero as the @var{crc} argument.
16839 Any executable file format can carry a debug link, as long as it can
16840 contain a section named @code{.gnu_debuglink} with the contents
16843 @cindex @code{.note.gnu.build-id} sections
16844 @cindex build ID sections
16845 The build ID is a special section in the executable file (and in other
16846 ELF binary files that @value{GDBN} may consider). This section is
16847 often named @code{.note.gnu.build-id}, but that name is not mandatory.
16848 It contains unique identification for the built files---the ID remains
16849 the same across multiple builds of the same build tree. The default
16850 algorithm SHA1 produces 160 bits (40 hexadecimal characters) of the
16851 content for the build ID string. The same section with an identical
16852 value is present in the original built binary with symbols, in its
16853 stripped variant, and in the separate debugging information file.
16855 The debugging information file itself should be an ordinary
16856 executable, containing a full set of linker symbols, sections, and
16857 debugging information. The sections of the debugging information file
16858 should have the same names, addresses, and sizes as the original file,
16859 but they need not contain any data---much like a @code{.bss} section
16860 in an ordinary executable.
16862 The @sc{gnu} binary utilities (Binutils) package includes the
16863 @samp{objcopy} utility that can produce
16864 the separated executable / debugging information file pairs using the
16865 following commands:
16868 @kbd{objcopy --only-keep-debug foo foo.debug}
16873 These commands remove the debugging
16874 information from the executable file @file{foo} and place it in the file
16875 @file{foo.debug}. You can use the first, second or both methods to link the
16880 The debug link method needs the following additional command to also leave
16881 behind a debug link in @file{foo}:
16884 @kbd{objcopy --add-gnu-debuglink=foo.debug foo}
16887 Ulrich Drepper's @file{elfutils} package, starting with version 0.53, contains
16888 a version of the @code{strip} command such that the command @kbd{strip foo -f
16889 foo.debug} has the same functionality as the two @code{objcopy} commands and
16890 the @code{ln -s} command above, together.
16893 Build ID gets embedded into the main executable using @code{ld --build-id} or
16894 the @value{NGCC} counterpart @code{gcc -Wl,--build-id}. Build ID support plus
16895 compatibility fixes for debug files separation are present in @sc{gnu} binary
16896 utilities (Binutils) package since version 2.18.
16901 @cindex CRC algorithm definition
16902 The CRC used in @code{.gnu_debuglink} is the CRC-32 defined in
16903 IEEE 802.3 using the polynomial:
16905 @c TexInfo requires naked braces for multi-digit exponents for Tex
16906 @c output, but this causes HTML output to barf. HTML has to be set using
16907 @c raw commands. So we end up having to specify this equation in 2
16912 <em>x</em><sup>32</sup> + <em>x</em><sup>26</sup> + <em>x</em><sup>23</sup> + <em>x</em><sup>22</sup> + <em>x</em><sup>16</sup> + <em>x</em><sup>12</sup> + <em>x</em><sup>11</sup>
16913 + <em>x</em><sup>10</sup> + <em>x</em><sup>8</sup> + <em>x</em><sup>7</sup> + <em>x</em><sup>5</sup> + <em>x</em><sup>4</sup> + <em>x</em><sup>2</sup> + <em>x</em> + 1
16919 @math{x^{32} + x^{26} + x^{23} + x^{22} + x^{16} + x^{12} + x^{11}}
16920 @math{+ x^{10} + x^8 + x^7 + x^5 + x^4 + x^2 + x + 1}
16924 The function is computed byte at a time, taking the least
16925 significant bit of each byte first. The initial pattern
16926 @code{0xffffffff} is used, to ensure leading zeros affect the CRC and
16927 the final result is inverted to ensure trailing zeros also affect the
16930 @emph{Note:} This is the same CRC polynomial as used in handling the
16931 @dfn{Remote Serial Protocol} @code{qCRC} packet (@pxref{Remote Protocol,
16932 , @value{GDBN} Remote Serial Protocol}). However in the
16933 case of the Remote Serial Protocol, the CRC is computed @emph{most}
16934 significant bit first, and the result is not inverted, so trailing
16935 zeros have no effect on the CRC value.
16937 To complete the description, we show below the code of the function
16938 which produces the CRC used in @code{.gnu_debuglink}. Inverting the
16939 initially supplied @code{crc} argument means that an initial call to
16940 this function passing in zero will start computing the CRC using
16943 @kindex gnu_debuglink_crc32
16946 gnu_debuglink_crc32 (unsigned long crc,
16947 unsigned char *buf, size_t len)
16949 static const unsigned long crc32_table[256] =
16951 0x00000000, 0x77073096, 0xee0e612c, 0x990951ba, 0x076dc419,
16952 0x706af48f, 0xe963a535, 0x9e6495a3, 0x0edb8832, 0x79dcb8a4,
16953 0xe0d5e91e, 0x97d2d988, 0x09b64c2b, 0x7eb17cbd, 0xe7b82d07,
16954 0x90bf1d91, 0x1db71064, 0x6ab020f2, 0xf3b97148, 0x84be41de,
16955 0x1adad47d, 0x6ddde4eb, 0xf4d4b551, 0x83d385c7, 0x136c9856,
16956 0x646ba8c0, 0xfd62f97a, 0x8a65c9ec, 0x14015c4f, 0x63066cd9,
16957 0xfa0f3d63, 0x8d080df5, 0x3b6e20c8, 0x4c69105e, 0xd56041e4,
16958 0xa2677172, 0x3c03e4d1, 0x4b04d447, 0xd20d85fd, 0xa50ab56b,
16959 0x35b5a8fa, 0x42b2986c, 0xdbbbc9d6, 0xacbcf940, 0x32d86ce3,
16960 0x45df5c75, 0xdcd60dcf, 0xabd13d59, 0x26d930ac, 0x51de003a,
16961 0xc8d75180, 0xbfd06116, 0x21b4f4b5, 0x56b3c423, 0xcfba9599,
16962 0xb8bda50f, 0x2802b89e, 0x5f058808, 0xc60cd9b2, 0xb10be924,
16963 0x2f6f7c87, 0x58684c11, 0xc1611dab, 0xb6662d3d, 0x76dc4190,
16964 0x01db7106, 0x98d220bc, 0xefd5102a, 0x71b18589, 0x06b6b51f,
16965 0x9fbfe4a5, 0xe8b8d433, 0x7807c9a2, 0x0f00f934, 0x9609a88e,
16966 0xe10e9818, 0x7f6a0dbb, 0x086d3d2d, 0x91646c97, 0xe6635c01,
16967 0x6b6b51f4, 0x1c6c6162, 0x856530d8, 0xf262004e, 0x6c0695ed,
16968 0x1b01a57b, 0x8208f4c1, 0xf50fc457, 0x65b0d9c6, 0x12b7e950,
16969 0x8bbeb8ea, 0xfcb9887c, 0x62dd1ddf, 0x15da2d49, 0x8cd37cf3,
16970 0xfbd44c65, 0x4db26158, 0x3ab551ce, 0xa3bc0074, 0xd4bb30e2,
16971 0x4adfa541, 0x3dd895d7, 0xa4d1c46d, 0xd3d6f4fb, 0x4369e96a,
16972 0x346ed9fc, 0xad678846, 0xda60b8d0, 0x44042d73, 0x33031de5,
16973 0xaa0a4c5f, 0xdd0d7cc9, 0x5005713c, 0x270241aa, 0xbe0b1010,
16974 0xc90c2086, 0x5768b525, 0x206f85b3, 0xb966d409, 0xce61e49f,
16975 0x5edef90e, 0x29d9c998, 0xb0d09822, 0xc7d7a8b4, 0x59b33d17,
16976 0x2eb40d81, 0xb7bd5c3b, 0xc0ba6cad, 0xedb88320, 0x9abfb3b6,
16977 0x03b6e20c, 0x74b1d29a, 0xead54739, 0x9dd277af, 0x04db2615,
16978 0x73dc1683, 0xe3630b12, 0x94643b84, 0x0d6d6a3e, 0x7a6a5aa8,
16979 0xe40ecf0b, 0x9309ff9d, 0x0a00ae27, 0x7d079eb1, 0xf00f9344,
16980 0x8708a3d2, 0x1e01f268, 0x6906c2fe, 0xf762575d, 0x806567cb,
16981 0x196c3671, 0x6e6b06e7, 0xfed41b76, 0x89d32be0, 0x10da7a5a,
16982 0x67dd4acc, 0xf9b9df6f, 0x8ebeeff9, 0x17b7be43, 0x60b08ed5,
16983 0xd6d6a3e8, 0xa1d1937e, 0x38d8c2c4, 0x4fdff252, 0xd1bb67f1,
16984 0xa6bc5767, 0x3fb506dd, 0x48b2364b, 0xd80d2bda, 0xaf0a1b4c,
16985 0x36034af6, 0x41047a60, 0xdf60efc3, 0xa867df55, 0x316e8eef,
16986 0x4669be79, 0xcb61b38c, 0xbc66831a, 0x256fd2a0, 0x5268e236,
16987 0xcc0c7795, 0xbb0b4703, 0x220216b9, 0x5505262f, 0xc5ba3bbe,
16988 0xb2bd0b28, 0x2bb45a92, 0x5cb36a04, 0xc2d7ffa7, 0xb5d0cf31,
16989 0x2cd99e8b, 0x5bdeae1d, 0x9b64c2b0, 0xec63f226, 0x756aa39c,
16990 0x026d930a, 0x9c0906a9, 0xeb0e363f, 0x72076785, 0x05005713,
16991 0x95bf4a82, 0xe2b87a14, 0x7bb12bae, 0x0cb61b38, 0x92d28e9b,
16992 0xe5d5be0d, 0x7cdcefb7, 0x0bdbdf21, 0x86d3d2d4, 0xf1d4e242,
16993 0x68ddb3f8, 0x1fda836e, 0x81be16cd, 0xf6b9265b, 0x6fb077e1,
16994 0x18b74777, 0x88085ae6, 0xff0f6a70, 0x66063bca, 0x11010b5c,
16995 0x8f659eff, 0xf862ae69, 0x616bffd3, 0x166ccf45, 0xa00ae278,
16996 0xd70dd2ee, 0x4e048354, 0x3903b3c2, 0xa7672661, 0xd06016f7,
16997 0x4969474d, 0x3e6e77db, 0xaed16a4a, 0xd9d65adc, 0x40df0b66,
16998 0x37d83bf0, 0xa9bcae53, 0xdebb9ec5, 0x47b2cf7f, 0x30b5ffe9,
16999 0xbdbdf21c, 0xcabac28a, 0x53b39330, 0x24b4a3a6, 0xbad03605,
17000 0xcdd70693, 0x54de5729, 0x23d967bf, 0xb3667a2e, 0xc4614ab8,
17001 0x5d681b02, 0x2a6f2b94, 0xb40bbe37, 0xc30c8ea1, 0x5a05df1b,
17004 unsigned char *end;
17006 crc = ~crc & 0xffffffff;
17007 for (end = buf + len; buf < end; ++buf)
17008 crc = crc32_table[(crc ^ *buf) & 0xff] ^ (crc >> 8);
17009 return ~crc & 0xffffffff;
17014 This computation does not apply to the ``build ID'' method.
17016 @node MiniDebugInfo
17017 @section Debugging information in a special section
17018 @cindex separate debug sections
17019 @cindex @samp{.gnu_debugdata} section
17021 Some systems ship pre-built executables and libraries that have a
17022 special @samp{.gnu_debugdata} section. This feature is called
17023 @dfn{MiniDebugInfo}. This section holds an LZMA-compressed object and
17024 is used to supply extra symbols for backtraces.
17026 The intent of this section is to provide extra minimal debugging
17027 information for use in simple backtraces. It is not intended to be a
17028 replacement for full separate debugging information (@pxref{Separate
17029 Debug Files}). The example below shows the intended use; however,
17030 @value{GDBN} does not currently put restrictions on what sort of
17031 debugging information might be included in the section.
17033 @value{GDBN} has support for this extension. If the section exists,
17034 then it is used provided that no other source of debugging information
17035 can be found, and that @value{GDBN} was configured with LZMA support.
17037 This section can be easily created using @command{objcopy} and other
17038 standard utilities:
17041 # Extract the dynamic symbols from the main binary, there is no need
17042 # to also have these in the normal symbol table
17043 nm -D @var{binary} --format=posix --defined-only \
17044 | awk '@{ print $1 @}' | sort > dynsyms
17046 # Extract all the text (i.e. function) symbols from the debuginfo .
17047 nm @var{binary} --format=posix --defined-only \
17048 | awk '@{ if ($2 == "T" || $2 == "t") print $1 @}' \
17051 # Keep all the function symbols not already in the dynamic symbol
17053 comm -13 dynsyms funcsyms > keep_symbols
17055 # Copy the full debuginfo, keeping only a minimal set of symbols and
17056 # removing some unnecessary sections.
17057 objcopy -S --remove-section .gdb_index --remove-section .comment \
17058 --keep-symbols=keep_symbols @var{binary} mini_debuginfo
17060 # Inject the compressed data into the .gnu_debugdata section of the
17063 objcopy --add-section .gnu_debugdata=mini_debuginfo.xz @var{binary}
17067 @section Index Files Speed Up @value{GDBN}
17068 @cindex index files
17069 @cindex @samp{.gdb_index} section
17071 When @value{GDBN} finds a symbol file, it scans the symbols in the
17072 file in order to construct an internal symbol table. This lets most
17073 @value{GDBN} operations work quickly---at the cost of a delay early
17074 on. For large programs, this delay can be quite lengthy, so
17075 @value{GDBN} provides a way to build an index, which speeds up
17078 The index is stored as a section in the symbol file. @value{GDBN} can
17079 write the index to a file, then you can put it into the symbol file
17080 using @command{objcopy}.
17082 To create an index file, use the @code{save gdb-index} command:
17085 @item save gdb-index @var{directory}
17086 @kindex save gdb-index
17087 Create an index file for each symbol file currently known by
17088 @value{GDBN}. Each file is named after its corresponding symbol file,
17089 with @samp{.gdb-index} appended, and is written into the given
17093 Once you have created an index file you can merge it into your symbol
17094 file, here named @file{symfile}, using @command{objcopy}:
17097 $ objcopy --add-section .gdb_index=symfile.gdb-index \
17098 --set-section-flags .gdb_index=readonly symfile symfile
17101 @value{GDBN} will normally ignore older versions of @file{.gdb_index}
17102 sections that have been deprecated. Usually they are deprecated because
17103 they are missing a new feature or have performance issues.
17104 To tell @value{GDBN} to use a deprecated index section anyway
17105 specify @code{set use-deprecated-index-sections on}.
17106 The default is @code{off}.
17107 This can speed up startup, but may result in some functionality being lost.
17108 @xref{Index Section Format}.
17110 @emph{Warning:} Setting @code{use-deprecated-index-sections} to @code{on}
17111 must be done before gdb reads the file. The following will not work:
17114 $ gdb -ex "set use-deprecated-index-sections on" <program>
17117 Instead you must do, for example,
17120 $ gdb -iex "set use-deprecated-index-sections on" <program>
17123 There are currently some limitation on indices. They only work when
17124 for DWARF debugging information, not stabs. And, they do not
17125 currently work for programs using Ada.
17127 @node Symbol Errors
17128 @section Errors Reading Symbol Files
17130 While reading a symbol file, @value{GDBN} occasionally encounters problems,
17131 such as symbol types it does not recognize, or known bugs in compiler
17132 output. By default, @value{GDBN} does not notify you of such problems, since
17133 they are relatively common and primarily of interest to people
17134 debugging compilers. If you are interested in seeing information
17135 about ill-constructed symbol tables, you can either ask @value{GDBN} to print
17136 only one message about each such type of problem, no matter how many
17137 times the problem occurs; or you can ask @value{GDBN} to print more messages,
17138 to see how many times the problems occur, with the @code{set
17139 complaints} command (@pxref{Messages/Warnings, ,Optional Warnings and
17142 The messages currently printed, and their meanings, include:
17145 @item inner block not inside outer block in @var{symbol}
17147 The symbol information shows where symbol scopes begin and end
17148 (such as at the start of a function or a block of statements). This
17149 error indicates that an inner scope block is not fully contained
17150 in its outer scope blocks.
17152 @value{GDBN} circumvents the problem by treating the inner block as if it had
17153 the same scope as the outer block. In the error message, @var{symbol}
17154 may be shown as ``@code{(don't know)}'' if the outer block is not a
17157 @item block at @var{address} out of order
17159 The symbol information for symbol scope blocks should occur in
17160 order of increasing addresses. This error indicates that it does not
17163 @value{GDBN} does not circumvent this problem, and has trouble
17164 locating symbols in the source file whose symbols it is reading. (You
17165 can often determine what source file is affected by specifying
17166 @code{set verbose on}. @xref{Messages/Warnings, ,Optional Warnings and
17169 @item bad block start address patched
17171 The symbol information for a symbol scope block has a start address
17172 smaller than the address of the preceding source line. This is known
17173 to occur in the SunOS 4.1.1 (and earlier) C compiler.
17175 @value{GDBN} circumvents the problem by treating the symbol scope block as
17176 starting on the previous source line.
17178 @item bad string table offset in symbol @var{n}
17181 Symbol number @var{n} contains a pointer into the string table which is
17182 larger than the size of the string table.
17184 @value{GDBN} circumvents the problem by considering the symbol to have the
17185 name @code{foo}, which may cause other problems if many symbols end up
17188 @item unknown symbol type @code{0x@var{nn}}
17190 The symbol information contains new data types that @value{GDBN} does
17191 not yet know how to read. @code{0x@var{nn}} is the symbol type of the
17192 uncomprehended information, in hexadecimal.
17194 @value{GDBN} circumvents the error by ignoring this symbol information.
17195 This usually allows you to debug your program, though certain symbols
17196 are not accessible. If you encounter such a problem and feel like
17197 debugging it, you can debug @code{@value{GDBP}} with itself, breakpoint
17198 on @code{complain}, then go up to the function @code{read_dbx_symtab}
17199 and examine @code{*bufp} to see the symbol.
17201 @item stub type has NULL name
17203 @value{GDBN} could not find the full definition for a struct or class.
17205 @item const/volatile indicator missing (ok if using g++ v1.x), got@dots{}
17206 The symbol information for a C@t{++} member function is missing some
17207 information that recent versions of the compiler should have output for
17210 @item info mismatch between compiler and debugger
17212 @value{GDBN} could not parse a type specification output by the compiler.
17217 @section GDB Data Files
17219 @cindex prefix for data files
17220 @value{GDBN} will sometimes read an auxiliary data file. These files
17221 are kept in a directory known as the @dfn{data directory}.
17223 You can set the data directory's name, and view the name @value{GDBN}
17224 is currently using.
17227 @kindex set data-directory
17228 @item set data-directory @var{directory}
17229 Set the directory which @value{GDBN} searches for auxiliary data files
17230 to @var{directory}.
17232 @kindex show data-directory
17233 @item show data-directory
17234 Show the directory @value{GDBN} searches for auxiliary data files.
17237 @cindex default data directory
17238 @cindex @samp{--with-gdb-datadir}
17239 You can set the default data directory by using the configure-time
17240 @samp{--with-gdb-datadir} option. If the data directory is inside
17241 @value{GDBN}'s configured binary prefix (set with @samp{--prefix} or
17242 @samp{--exec-prefix}), then the default data directory will be updated
17243 automatically if the installed @value{GDBN} is moved to a new
17246 The data directory may also be specified with the
17247 @code{--data-directory} command line option.
17248 @xref{Mode Options}.
17251 @chapter Specifying a Debugging Target
17253 @cindex debugging target
17254 A @dfn{target} is the execution environment occupied by your program.
17256 Often, @value{GDBN} runs in the same host environment as your program;
17257 in that case, the debugging target is specified as a side effect when
17258 you use the @code{file} or @code{core} commands. When you need more
17259 flexibility---for example, running @value{GDBN} on a physically separate
17260 host, or controlling a standalone system over a serial port or a
17261 realtime system over a TCP/IP connection---you can use the @code{target}
17262 command to specify one of the target types configured for @value{GDBN}
17263 (@pxref{Target Commands, ,Commands for Managing Targets}).
17265 @cindex target architecture
17266 It is possible to build @value{GDBN} for several different @dfn{target
17267 architectures}. When @value{GDBN} is built like that, you can choose
17268 one of the available architectures with the @kbd{set architecture}
17272 @kindex set architecture
17273 @kindex show architecture
17274 @item set architecture @var{arch}
17275 This command sets the current target architecture to @var{arch}. The
17276 value of @var{arch} can be @code{"auto"}, in addition to one of the
17277 supported architectures.
17279 @item show architecture
17280 Show the current target architecture.
17282 @item set processor
17284 @kindex set processor
17285 @kindex show processor
17286 These are alias commands for, respectively, @code{set architecture}
17287 and @code{show architecture}.
17291 * Active Targets:: Active targets
17292 * Target Commands:: Commands for managing targets
17293 * Byte Order:: Choosing target byte order
17296 @node Active Targets
17297 @section Active Targets
17299 @cindex stacking targets
17300 @cindex active targets
17301 @cindex multiple targets
17303 There are multiple classes of targets such as: processes, executable files or
17304 recording sessions. Core files belong to the process class, making core file
17305 and process mutually exclusive. Otherwise, @value{GDBN} can work concurrently
17306 on multiple active targets, one in each class. This allows you to (for
17307 example) start a process and inspect its activity, while still having access to
17308 the executable file after the process finishes. Or if you start process
17309 recording (@pxref{Reverse Execution}) and @code{reverse-step} there, you are
17310 presented a virtual layer of the recording target, while the process target
17311 remains stopped at the chronologically last point of the process execution.
17313 Use the @code{core-file} and @code{exec-file} commands to select a new core
17314 file or executable target (@pxref{Files, ,Commands to Specify Files}). To
17315 specify as a target a process that is already running, use the @code{attach}
17316 command (@pxref{Attach, ,Debugging an Already-running Process}).
17318 @node Target Commands
17319 @section Commands for Managing Targets
17322 @item target @var{type} @var{parameters}
17323 Connects the @value{GDBN} host environment to a target machine or
17324 process. A target is typically a protocol for talking to debugging
17325 facilities. You use the argument @var{type} to specify the type or
17326 protocol of the target machine.
17328 Further @var{parameters} are interpreted by the target protocol, but
17329 typically include things like device names or host names to connect
17330 with, process numbers, and baud rates.
17332 The @code{target} command does not repeat if you press @key{RET} again
17333 after executing the command.
17335 @kindex help target
17337 Displays the names of all targets available. To display targets
17338 currently selected, use either @code{info target} or @code{info files}
17339 (@pxref{Files, ,Commands to Specify Files}).
17341 @item help target @var{name}
17342 Describe a particular target, including any parameters necessary to
17345 @kindex set gnutarget
17346 @item set gnutarget @var{args}
17347 @value{GDBN} uses its own library BFD to read your files. @value{GDBN}
17348 knows whether it is reading an @dfn{executable},
17349 a @dfn{core}, or a @dfn{.o} file; however, you can specify the file format
17350 with the @code{set gnutarget} command. Unlike most @code{target} commands,
17351 with @code{gnutarget} the @code{target} refers to a program, not a machine.
17354 @emph{Warning:} To specify a file format with @code{set gnutarget},
17355 you must know the actual BFD name.
17359 @xref{Files, , Commands to Specify Files}.
17361 @kindex show gnutarget
17362 @item show gnutarget
17363 Use the @code{show gnutarget} command to display what file format
17364 @code{gnutarget} is set to read. If you have not set @code{gnutarget},
17365 @value{GDBN} will determine the file format for each file automatically,
17366 and @code{show gnutarget} displays @samp{The current BFD target is "auto"}.
17369 @cindex common targets
17370 Here are some common targets (available, or not, depending on the GDB
17375 @item target exec @var{program}
17376 @cindex executable file target
17377 An executable file. @samp{target exec @var{program}} is the same as
17378 @samp{exec-file @var{program}}.
17380 @item target core @var{filename}
17381 @cindex core dump file target
17382 A core dump file. @samp{target core @var{filename}} is the same as
17383 @samp{core-file @var{filename}}.
17385 @item target remote @var{medium}
17386 @cindex remote target
17387 A remote system connected to @value{GDBN} via a serial line or network
17388 connection. This command tells @value{GDBN} to use its own remote
17389 protocol over @var{medium} for debugging. @xref{Remote Debugging}.
17391 For example, if you have a board connected to @file{/dev/ttya} on the
17392 machine running @value{GDBN}, you could say:
17395 target remote /dev/ttya
17398 @code{target remote} supports the @code{load} command. This is only
17399 useful if you have some other way of getting the stub to the target
17400 system, and you can put it somewhere in memory where it won't get
17401 clobbered by the download.
17403 @item target sim @r{[}@var{simargs}@r{]} @dots{}
17404 @cindex built-in simulator target
17405 Builtin CPU simulator. @value{GDBN} includes simulators for most architectures.
17413 works; however, you cannot assume that a specific memory map, device
17414 drivers, or even basic I/O is available, although some simulators do
17415 provide these. For info about any processor-specific simulator details,
17416 see the appropriate section in @ref{Embedded Processors, ,Embedded
17421 Some configurations may include these targets as well:
17425 @item target nrom @var{dev}
17426 @cindex NetROM ROM emulator target
17427 NetROM ROM emulator. This target only supports downloading.
17431 Different targets are available on different configurations of @value{GDBN};
17432 your configuration may have more or fewer targets.
17434 Many remote targets require you to download the executable's code once
17435 you've successfully established a connection. You may wish to control
17436 various aspects of this process.
17441 @kindex set hash@r{, for remote monitors}
17442 @cindex hash mark while downloading
17443 This command controls whether a hash mark @samp{#} is displayed while
17444 downloading a file to the remote monitor. If on, a hash mark is
17445 displayed after each S-record is successfully downloaded to the
17449 @kindex show hash@r{, for remote monitors}
17450 Show the current status of displaying the hash mark.
17452 @item set debug monitor
17453 @kindex set debug monitor
17454 @cindex display remote monitor communications
17455 Enable or disable display of communications messages between
17456 @value{GDBN} and the remote monitor.
17458 @item show debug monitor
17459 @kindex show debug monitor
17460 Show the current status of displaying communications between
17461 @value{GDBN} and the remote monitor.
17466 @kindex load @var{filename}
17467 @item load @var{filename}
17469 Depending on what remote debugging facilities are configured into
17470 @value{GDBN}, the @code{load} command may be available. Where it exists, it
17471 is meant to make @var{filename} (an executable) available for debugging
17472 on the remote system---by downloading, or dynamic linking, for example.
17473 @code{load} also records the @var{filename} symbol table in @value{GDBN}, like
17474 the @code{add-symbol-file} command.
17476 If your @value{GDBN} does not have a @code{load} command, attempting to
17477 execute it gets the error message ``@code{You can't do that when your
17478 target is @dots{}}''
17480 The file is loaded at whatever address is specified in the executable.
17481 For some object file formats, you can specify the load address when you
17482 link the program; for other formats, like a.out, the object file format
17483 specifies a fixed address.
17484 @c FIXME! This would be a good place for an xref to the GNU linker doc.
17486 Depending on the remote side capabilities, @value{GDBN} may be able to
17487 load programs into flash memory.
17489 @code{load} does not repeat if you press @key{RET} again after using it.
17493 @section Choosing Target Byte Order
17495 @cindex choosing target byte order
17496 @cindex target byte order
17498 Some types of processors, such as the @acronym{MIPS}, PowerPC, and Renesas SH,
17499 offer the ability to run either big-endian or little-endian byte
17500 orders. Usually the executable or symbol will include a bit to
17501 designate the endian-ness, and you will not need to worry about
17502 which to use. However, you may still find it useful to adjust
17503 @value{GDBN}'s idea of processor endian-ness manually.
17507 @item set endian big
17508 Instruct @value{GDBN} to assume the target is big-endian.
17510 @item set endian little
17511 Instruct @value{GDBN} to assume the target is little-endian.
17513 @item set endian auto
17514 Instruct @value{GDBN} to use the byte order associated with the
17518 Display @value{GDBN}'s current idea of the target byte order.
17522 Note that these commands merely adjust interpretation of symbolic
17523 data on the host, and that they have absolutely no effect on the
17527 @node Remote Debugging
17528 @chapter Debugging Remote Programs
17529 @cindex remote debugging
17531 If you are trying to debug a program running on a machine that cannot run
17532 @value{GDBN} in the usual way, it is often useful to use remote debugging.
17533 For example, you might use remote debugging on an operating system kernel,
17534 or on a small system which does not have a general purpose operating system
17535 powerful enough to run a full-featured debugger.
17537 Some configurations of @value{GDBN} have special serial or TCP/IP interfaces
17538 to make this work with particular debugging targets. In addition,
17539 @value{GDBN} comes with a generic serial protocol (specific to @value{GDBN},
17540 but not specific to any particular target system) which you can use if you
17541 write the remote stubs---the code that runs on the remote system to
17542 communicate with @value{GDBN}.
17544 Other remote targets may be available in your
17545 configuration of @value{GDBN}; use @code{help target} to list them.
17548 * Connecting:: Connecting to a remote target
17549 * File Transfer:: Sending files to a remote system
17550 * Server:: Using the gdbserver program
17551 * Remote Configuration:: Remote configuration
17552 * Remote Stub:: Implementing a remote stub
17556 @section Connecting to a Remote Target
17558 On the @value{GDBN} host machine, you will need an unstripped copy of
17559 your program, since @value{GDBN} needs symbol and debugging information.
17560 Start up @value{GDBN} as usual, using the name of the local copy of your
17561 program as the first argument.
17563 @cindex @code{target remote}
17564 @value{GDBN} can communicate with the target over a serial line, or
17565 over an @acronym{IP} network using @acronym{TCP} or @acronym{UDP}. In
17566 each case, @value{GDBN} uses the same protocol for debugging your
17567 program; only the medium carrying the debugging packets varies. The
17568 @code{target remote} command establishes a connection to the target.
17569 Its arguments indicate which medium to use:
17573 @item target remote @var{serial-device}
17574 @cindex serial line, @code{target remote}
17575 Use @var{serial-device} to communicate with the target. For example,
17576 to use a serial line connected to the device named @file{/dev/ttyb}:
17579 target remote /dev/ttyb
17582 If you're using a serial line, you may want to give @value{GDBN} the
17583 @w{@samp{--baud}} option, or use the @code{set remotebaud} command
17584 (@pxref{Remote Configuration, set remotebaud}) before the
17585 @code{target} command.
17587 @item target remote @code{@var{host}:@var{port}}
17588 @itemx target remote @code{tcp:@var{host}:@var{port}}
17589 @cindex @acronym{TCP} port, @code{target remote}
17590 Debug using a @acronym{TCP} connection to @var{port} on @var{host}.
17591 The @var{host} may be either a host name or a numeric @acronym{IP}
17592 address; @var{port} must be a decimal number. The @var{host} could be
17593 the target machine itself, if it is directly connected to the net, or
17594 it might be a terminal server which in turn has a serial line to the
17597 For example, to connect to port 2828 on a terminal server named
17601 target remote manyfarms:2828
17604 If your remote target is actually running on the same machine as your
17605 debugger session (e.g.@: a simulator for your target running on the
17606 same host), you can omit the hostname. For example, to connect to
17607 port 1234 on your local machine:
17610 target remote :1234
17614 Note that the colon is still required here.
17616 @item target remote @code{udp:@var{host}:@var{port}}
17617 @cindex @acronym{UDP} port, @code{target remote}
17618 Debug using @acronym{UDP} packets to @var{port} on @var{host}. For example, to
17619 connect to @acronym{UDP} port 2828 on a terminal server named @code{manyfarms}:
17622 target remote udp:manyfarms:2828
17625 When using a @acronym{UDP} connection for remote debugging, you should
17626 keep in mind that the `U' stands for ``Unreliable''. @acronym{UDP}
17627 can silently drop packets on busy or unreliable networks, which will
17628 cause havoc with your debugging session.
17630 @item target remote | @var{command}
17631 @cindex pipe, @code{target remote} to
17632 Run @var{command} in the background and communicate with it using a
17633 pipe. The @var{command} is a shell command, to be parsed and expanded
17634 by the system's command shell, @code{/bin/sh}; it should expect remote
17635 protocol packets on its standard input, and send replies on its
17636 standard output. You could use this to run a stand-alone simulator
17637 that speaks the remote debugging protocol, to make net connections
17638 using programs like @code{ssh}, or for other similar tricks.
17640 If @var{command} closes its standard output (perhaps by exiting),
17641 @value{GDBN} will try to send it a @code{SIGTERM} signal. (If the
17642 program has already exited, this will have no effect.)
17646 Once the connection has been established, you can use all the usual
17647 commands to examine and change data. The remote program is already
17648 running; you can use @kbd{step} and @kbd{continue}, and you do not
17649 need to use @kbd{run}.
17651 @cindex interrupting remote programs
17652 @cindex remote programs, interrupting
17653 Whenever @value{GDBN} is waiting for the remote program, if you type the
17654 interrupt character (often @kbd{Ctrl-c}), @value{GDBN} attempts to stop the
17655 program. This may or may not succeed, depending in part on the hardware
17656 and the serial drivers the remote system uses. If you type the
17657 interrupt character once again, @value{GDBN} displays this prompt:
17660 Interrupted while waiting for the program.
17661 Give up (and stop debugging it)? (y or n)
17664 If you type @kbd{y}, @value{GDBN} abandons the remote debugging session.
17665 (If you decide you want to try again later, you can use @samp{target
17666 remote} again to connect once more.) If you type @kbd{n}, @value{GDBN}
17667 goes back to waiting.
17670 @kindex detach (remote)
17672 When you have finished debugging the remote program, you can use the
17673 @code{detach} command to release it from @value{GDBN} control.
17674 Detaching from the target normally resumes its execution, but the results
17675 will depend on your particular remote stub. After the @code{detach}
17676 command, @value{GDBN} is free to connect to another target.
17680 The @code{disconnect} command behaves like @code{detach}, except that
17681 the target is generally not resumed. It will wait for @value{GDBN}
17682 (this instance or another one) to connect and continue debugging. After
17683 the @code{disconnect} command, @value{GDBN} is again free to connect to
17686 @cindex send command to remote monitor
17687 @cindex extend @value{GDBN} for remote targets
17688 @cindex add new commands for external monitor
17690 @item monitor @var{cmd}
17691 This command allows you to send arbitrary commands directly to the
17692 remote monitor. Since @value{GDBN} doesn't care about the commands it
17693 sends like this, this command is the way to extend @value{GDBN}---you
17694 can add new commands that only the external monitor will understand
17698 @node File Transfer
17699 @section Sending files to a remote system
17700 @cindex remote target, file transfer
17701 @cindex file transfer
17702 @cindex sending files to remote systems
17704 Some remote targets offer the ability to transfer files over the same
17705 connection used to communicate with @value{GDBN}. This is convenient
17706 for targets accessible through other means, e.g.@: @sc{gnu}/Linux systems
17707 running @code{gdbserver} over a network interface. For other targets,
17708 e.g.@: embedded devices with only a single serial port, this may be
17709 the only way to upload or download files.
17711 Not all remote targets support these commands.
17715 @item remote put @var{hostfile} @var{targetfile}
17716 Copy file @var{hostfile} from the host system (the machine running
17717 @value{GDBN}) to @var{targetfile} on the target system.
17720 @item remote get @var{targetfile} @var{hostfile}
17721 Copy file @var{targetfile} from the target system to @var{hostfile}
17722 on the host system.
17724 @kindex remote delete
17725 @item remote delete @var{targetfile}
17726 Delete @var{targetfile} from the target system.
17731 @section Using the @code{gdbserver} Program
17734 @cindex remote connection without stubs
17735 @code{gdbserver} is a control program for Unix-like systems, which
17736 allows you to connect your program with a remote @value{GDBN} via
17737 @code{target remote}---but without linking in the usual debugging stub.
17739 @code{gdbserver} is not a complete replacement for the debugging stubs,
17740 because it requires essentially the same operating-system facilities
17741 that @value{GDBN} itself does. In fact, a system that can run
17742 @code{gdbserver} to connect to a remote @value{GDBN} could also run
17743 @value{GDBN} locally! @code{gdbserver} is sometimes useful nevertheless,
17744 because it is a much smaller program than @value{GDBN} itself. It is
17745 also easier to port than all of @value{GDBN}, so you may be able to get
17746 started more quickly on a new system by using @code{gdbserver}.
17747 Finally, if you develop code for real-time systems, you may find that
17748 the tradeoffs involved in real-time operation make it more convenient to
17749 do as much development work as possible on another system, for example
17750 by cross-compiling. You can use @code{gdbserver} to make a similar
17751 choice for debugging.
17753 @value{GDBN} and @code{gdbserver} communicate via either a serial line
17754 or a TCP connection, using the standard @value{GDBN} remote serial
17758 @emph{Warning:} @code{gdbserver} does not have any built-in security.
17759 Do not run @code{gdbserver} connected to any public network; a
17760 @value{GDBN} connection to @code{gdbserver} provides access to the
17761 target system with the same privileges as the user running
17765 @subsection Running @code{gdbserver}
17766 @cindex arguments, to @code{gdbserver}
17767 @cindex @code{gdbserver}, command-line arguments
17769 Run @code{gdbserver} on the target system. You need a copy of the
17770 program you want to debug, including any libraries it requires.
17771 @code{gdbserver} does not need your program's symbol table, so you can
17772 strip the program if necessary to save space. @value{GDBN} on the host
17773 system does all the symbol handling.
17775 To use the server, you must tell it how to communicate with @value{GDBN};
17776 the name of your program; and the arguments for your program. The usual
17780 target> gdbserver @var{comm} @var{program} [ @var{args} @dots{} ]
17783 @var{comm} is either a device name (to use a serial line), or a TCP
17784 hostname and portnumber, or @code{-} or @code{stdio} to use
17785 stdin/stdout of @code{gdbserver}.
17786 For example, to debug Emacs with the argument
17787 @samp{foo.txt} and communicate with @value{GDBN} over the serial port
17791 target> gdbserver /dev/com1 emacs foo.txt
17794 @code{gdbserver} waits passively for the host @value{GDBN} to communicate
17797 To use a TCP connection instead of a serial line:
17800 target> gdbserver host:2345 emacs foo.txt
17803 The only difference from the previous example is the first argument,
17804 specifying that you are communicating with the host @value{GDBN} via
17805 TCP. The @samp{host:2345} argument means that @code{gdbserver} is to
17806 expect a TCP connection from machine @samp{host} to local TCP port 2345.
17807 (Currently, the @samp{host} part is ignored.) You can choose any number
17808 you want for the port number as long as it does not conflict with any
17809 TCP ports already in use on the target system (for example, @code{23} is
17810 reserved for @code{telnet}).@footnote{If you choose a port number that
17811 conflicts with another service, @code{gdbserver} prints an error message
17812 and exits.} You must use the same port number with the host @value{GDBN}
17813 @code{target remote} command.
17815 The @code{stdio} connection is useful when starting @code{gdbserver}
17819 (gdb) target remote | ssh -T hostname gdbserver - hello
17822 The @samp{-T} option to ssh is provided because we don't need a remote pty,
17823 and we don't want escape-character handling. Ssh does this by default when
17824 a command is provided, the flag is provided to make it explicit.
17825 You could elide it if you want to.
17827 Programs started with stdio-connected gdbserver have @file{/dev/null} for
17828 @code{stdin}, and @code{stdout},@code{stderr} are sent back to gdb for
17829 display through a pipe connected to gdbserver.
17830 Both @code{stdout} and @code{stderr} use the same pipe.
17832 @subsubsection Attaching to a Running Program
17833 @cindex attach to a program, @code{gdbserver}
17834 @cindex @option{--attach}, @code{gdbserver} option
17836 On some targets, @code{gdbserver} can also attach to running programs.
17837 This is accomplished via the @code{--attach} argument. The syntax is:
17840 target> gdbserver --attach @var{comm} @var{pid}
17843 @var{pid} is the process ID of a currently running process. It isn't necessary
17844 to point @code{gdbserver} at a binary for the running process.
17847 You can debug processes by name instead of process ID if your target has the
17848 @code{pidof} utility:
17851 target> gdbserver --attach @var{comm} `pidof @var{program}`
17854 In case more than one copy of @var{program} is running, or @var{program}
17855 has multiple threads, most versions of @code{pidof} support the
17856 @code{-s} option to only return the first process ID.
17858 @subsubsection Multi-Process Mode for @code{gdbserver}
17859 @cindex @code{gdbserver}, multiple processes
17860 @cindex multiple processes with @code{gdbserver}
17862 When you connect to @code{gdbserver} using @code{target remote},
17863 @code{gdbserver} debugs the specified program only once. When the
17864 program exits, or you detach from it, @value{GDBN} closes the connection
17865 and @code{gdbserver} exits.
17867 If you connect using @kbd{target extended-remote}, @code{gdbserver}
17868 enters multi-process mode. When the debugged program exits, or you
17869 detach from it, @value{GDBN} stays connected to @code{gdbserver} even
17870 though no program is running. The @code{run} and @code{attach}
17871 commands instruct @code{gdbserver} to run or attach to a new program.
17872 The @code{run} command uses @code{set remote exec-file} (@pxref{set
17873 remote exec-file}) to select the program to run. Command line
17874 arguments are supported, except for wildcard expansion and I/O
17875 redirection (@pxref{Arguments}).
17877 @cindex @option{--multi}, @code{gdbserver} option
17878 To start @code{gdbserver} without supplying an initial command to run
17879 or process ID to attach, use the @option{--multi} command line option.
17880 Then you can connect using @kbd{target extended-remote} and start
17881 the program you want to debug.
17883 In multi-process mode @code{gdbserver} does not automatically exit unless you
17884 use the option @option{--once}. You can terminate it by using
17885 @code{monitor exit} (@pxref{Monitor Commands for gdbserver}). Note that the
17886 conditions under which @code{gdbserver} terminates depend on how @value{GDBN}
17887 connects to it (@kbd{target remote} or @kbd{target extended-remote}). The
17888 @option{--multi} option to @code{gdbserver} has no influence on that.
17890 @subsubsection TCP port allocation lifecycle of @code{gdbserver}
17892 This section applies only when @code{gdbserver} is run to listen on a TCP port.
17894 @code{gdbserver} normally terminates after all of its debugged processes have
17895 terminated in @kbd{target remote} mode. On the other hand, for @kbd{target
17896 extended-remote}, @code{gdbserver} stays running even with no processes left.
17897 @value{GDBN} normally terminates the spawned debugged process on its exit,
17898 which normally also terminates @code{gdbserver} in the @kbd{target remote}
17899 mode. Therefore, when the connection drops unexpectedly, and @value{GDBN}
17900 cannot ask @code{gdbserver} to kill its debugged processes, @code{gdbserver}
17901 stays running even in the @kbd{target remote} mode.
17903 When @code{gdbserver} stays running, @value{GDBN} can connect to it again later.
17904 Such reconnecting is useful for features like @ref{disconnected tracing}. For
17905 completeness, at most one @value{GDBN} can be connected at a time.
17907 @cindex @option{--once}, @code{gdbserver} option
17908 By default, @code{gdbserver} keeps the listening TCP port open, so that
17909 additional connections are possible. However, if you start @code{gdbserver}
17910 with the @option{--once} option, it will stop listening for any further
17911 connection attempts after connecting to the first @value{GDBN} session. This
17912 means no further connections to @code{gdbserver} will be possible after the
17913 first one. It also means @code{gdbserver} will terminate after the first
17914 connection with remote @value{GDBN} has closed, even for unexpectedly closed
17915 connections and even in the @kbd{target extended-remote} mode. The
17916 @option{--once} option allows reusing the same port number for connecting to
17917 multiple instances of @code{gdbserver} running on the same host, since each
17918 instance closes its port after the first connection.
17920 @subsubsection Other Command-Line Arguments for @code{gdbserver}
17922 @cindex @option{--debug}, @code{gdbserver} option
17923 The @option{--debug} option tells @code{gdbserver} to display extra
17924 status information about the debugging process.
17925 @cindex @option{--remote-debug}, @code{gdbserver} option
17926 The @option{--remote-debug} option tells @code{gdbserver} to display
17927 remote protocol debug output. These options are intended for
17928 @code{gdbserver} development and for bug reports to the developers.
17930 @cindex @option{--wrapper}, @code{gdbserver} option
17931 The @option{--wrapper} option specifies a wrapper to launch programs
17932 for debugging. The option should be followed by the name of the
17933 wrapper, then any command-line arguments to pass to the wrapper, then
17934 @kbd{--} indicating the end of the wrapper arguments.
17936 @code{gdbserver} runs the specified wrapper program with a combined
17937 command line including the wrapper arguments, then the name of the
17938 program to debug, then any arguments to the program. The wrapper
17939 runs until it executes your program, and then @value{GDBN} gains control.
17941 You can use any program that eventually calls @code{execve} with
17942 its arguments as a wrapper. Several standard Unix utilities do
17943 this, e.g.@: @code{env} and @code{nohup}. Any Unix shell script ending
17944 with @code{exec "$@@"} will also work.
17946 For example, you can use @code{env} to pass an environment variable to
17947 the debugged program, without setting the variable in @code{gdbserver}'s
17951 $ gdbserver --wrapper env LD_PRELOAD=libtest.so -- :2222 ./testprog
17954 @subsection Connecting to @code{gdbserver}
17956 Run @value{GDBN} on the host system.
17958 First make sure you have the necessary symbol files. Load symbols for
17959 your application using the @code{file} command before you connect. Use
17960 @code{set sysroot} to locate target libraries (unless your @value{GDBN}
17961 was compiled with the correct sysroot using @code{--with-sysroot}).
17963 The symbol file and target libraries must exactly match the executable
17964 and libraries on the target, with one exception: the files on the host
17965 system should not be stripped, even if the files on the target system
17966 are. Mismatched or missing files will lead to confusing results
17967 during debugging. On @sc{gnu}/Linux targets, mismatched or missing
17968 files may also prevent @code{gdbserver} from debugging multi-threaded
17971 Connect to your target (@pxref{Connecting,,Connecting to a Remote Target}).
17972 For TCP connections, you must start up @code{gdbserver} prior to using
17973 the @code{target remote} command. Otherwise you may get an error whose
17974 text depends on the host system, but which usually looks something like
17975 @samp{Connection refused}. Don't use the @code{load}
17976 command in @value{GDBN} when using @code{gdbserver}, since the program is
17977 already on the target.
17979 @subsection Monitor Commands for @code{gdbserver}
17980 @cindex monitor commands, for @code{gdbserver}
17981 @anchor{Monitor Commands for gdbserver}
17983 During a @value{GDBN} session using @code{gdbserver}, you can use the
17984 @code{monitor} command to send special requests to @code{gdbserver}.
17985 Here are the available commands.
17989 List the available monitor commands.
17991 @item monitor set debug 0
17992 @itemx monitor set debug 1
17993 Disable or enable general debugging messages.
17995 @item monitor set remote-debug 0
17996 @itemx monitor set remote-debug 1
17997 Disable or enable specific debugging messages associated with the remote
17998 protocol (@pxref{Remote Protocol}).
18000 @item monitor set libthread-db-search-path [PATH]
18001 @cindex gdbserver, search path for @code{libthread_db}
18002 When this command is issued, @var{path} is a colon-separated list of
18003 directories to search for @code{libthread_db} (@pxref{Threads,,set
18004 libthread-db-search-path}). If you omit @var{path},
18005 @samp{libthread-db-search-path} will be reset to its default value.
18007 The special entry @samp{$pdir} for @samp{libthread-db-search-path} is
18008 not supported in @code{gdbserver}.
18011 Tell gdbserver to exit immediately. This command should be followed by
18012 @code{disconnect} to close the debugging session. @code{gdbserver} will
18013 detach from any attached processes and kill any processes it created.
18014 Use @code{monitor exit} to terminate @code{gdbserver} at the end
18015 of a multi-process mode debug session.
18019 @subsection Tracepoints support in @code{gdbserver}
18020 @cindex tracepoints support in @code{gdbserver}
18022 On some targets, @code{gdbserver} supports tracepoints, fast
18023 tracepoints and static tracepoints.
18025 For fast or static tracepoints to work, a special library called the
18026 @dfn{in-process agent} (IPA), must be loaded in the inferior process.
18027 This library is built and distributed as an integral part of
18028 @code{gdbserver}. In addition, support for static tracepoints
18029 requires building the in-process agent library with static tracepoints
18030 support. At present, the UST (LTTng Userspace Tracer,
18031 @url{http://lttng.org/ust}) tracing engine is supported. This support
18032 is automatically available if UST development headers are found in the
18033 standard include path when @code{gdbserver} is built, or if
18034 @code{gdbserver} was explicitly configured using @option{--with-ust}
18035 to point at such headers. You can explicitly disable the support
18036 using @option{--with-ust=no}.
18038 There are several ways to load the in-process agent in your program:
18041 @item Specifying it as dependency at link time
18043 You can link your program dynamically with the in-process agent
18044 library. On most systems, this is accomplished by adding
18045 @code{-linproctrace} to the link command.
18047 @item Using the system's preloading mechanisms
18049 You can force loading the in-process agent at startup time by using
18050 your system's support for preloading shared libraries. Many Unixes
18051 support the concept of preloading user defined libraries. In most
18052 cases, you do that by specifying @code{LD_PRELOAD=libinproctrace.so}
18053 in the environment. See also the description of @code{gdbserver}'s
18054 @option{--wrapper} command line option.
18056 @item Using @value{GDBN} to force loading the agent at run time
18058 On some systems, you can force the inferior to load a shared library,
18059 by calling a dynamic loader function in the inferior that takes care
18060 of dynamically looking up and loading a shared library. On most Unix
18061 systems, the function is @code{dlopen}. You'll use the @code{call}
18062 command for that. For example:
18065 (@value{GDBP}) call dlopen ("libinproctrace.so", ...)
18068 Note that on most Unix systems, for the @code{dlopen} function to be
18069 available, the program needs to be linked with @code{-ldl}.
18072 On systems that have a userspace dynamic loader, like most Unix
18073 systems, when you connect to @code{gdbserver} using @code{target
18074 remote}, you'll find that the program is stopped at the dynamic
18075 loader's entry point, and no shared library has been loaded in the
18076 program's address space yet, including the in-process agent. In that
18077 case, before being able to use any of the fast or static tracepoints
18078 features, you need to let the loader run and load the shared
18079 libraries. The simplest way to do that is to run the program to the
18080 main procedure. E.g., if debugging a C or C@t{++} program, start
18081 @code{gdbserver} like so:
18084 $ gdbserver :9999 myprogram
18087 Start GDB and connect to @code{gdbserver} like so, and run to main:
18091 (@value{GDBP}) target remote myhost:9999
18092 0x00007f215893ba60 in ?? () from /lib64/ld-linux-x86-64.so.2
18093 (@value{GDBP}) b main
18094 (@value{GDBP}) continue
18097 The in-process tracing agent library should now be loaded into the
18098 process; you can confirm it with the @code{info sharedlibrary}
18099 command, which will list @file{libinproctrace.so} as loaded in the
18100 process. You are now ready to install fast tracepoints, list static
18101 tracepoint markers, probe static tracepoints markers, and start
18104 @node Remote Configuration
18105 @section Remote Configuration
18108 @kindex show remote
18109 This section documents the configuration options available when
18110 debugging remote programs. For the options related to the File I/O
18111 extensions of the remote protocol, see @ref{system,
18112 system-call-allowed}.
18115 @item set remoteaddresssize @var{bits}
18116 @cindex address size for remote targets
18117 @cindex bits in remote address
18118 Set the maximum size of address in a memory packet to the specified
18119 number of bits. @value{GDBN} will mask off the address bits above
18120 that number, when it passes addresses to the remote target. The
18121 default value is the number of bits in the target's address.
18123 @item show remoteaddresssize
18124 Show the current value of remote address size in bits.
18126 @item set remotebaud @var{n}
18127 @cindex baud rate for remote targets
18128 Set the baud rate for the remote serial I/O to @var{n} baud. The
18129 value is used to set the speed of the serial port used for debugging
18132 @item show remotebaud
18133 Show the current speed of the remote connection.
18135 @item set remotebreak
18136 @cindex interrupt remote programs
18137 @cindex BREAK signal instead of Ctrl-C
18138 @anchor{set remotebreak}
18139 If set to on, @value{GDBN} sends a @code{BREAK} signal to the remote
18140 when you type @kbd{Ctrl-c} to interrupt the program running
18141 on the remote. If set to off, @value{GDBN} sends the @samp{Ctrl-C}
18142 character instead. The default is off, since most remote systems
18143 expect to see @samp{Ctrl-C} as the interrupt signal.
18145 @item show remotebreak
18146 Show whether @value{GDBN} sends @code{BREAK} or @samp{Ctrl-C} to
18147 interrupt the remote program.
18149 @item set remoteflow on
18150 @itemx set remoteflow off
18151 @kindex set remoteflow
18152 Enable or disable hardware flow control (@code{RTS}/@code{CTS})
18153 on the serial port used to communicate to the remote target.
18155 @item show remoteflow
18156 @kindex show remoteflow
18157 Show the current setting of hardware flow control.
18159 @item set remotelogbase @var{base}
18160 Set the base (a.k.a.@: radix) of logging serial protocol
18161 communications to @var{base}. Supported values of @var{base} are:
18162 @code{ascii}, @code{octal}, and @code{hex}. The default is
18165 @item show remotelogbase
18166 Show the current setting of the radix for logging remote serial
18169 @item set remotelogfile @var{file}
18170 @cindex record serial communications on file
18171 Record remote serial communications on the named @var{file}. The
18172 default is not to record at all.
18174 @item show remotelogfile.
18175 Show the current setting of the file name on which to record the
18176 serial communications.
18178 @item set remotetimeout @var{num}
18179 @cindex timeout for serial communications
18180 @cindex remote timeout
18181 Set the timeout limit to wait for the remote target to respond to
18182 @var{num} seconds. The default is 2 seconds.
18184 @item show remotetimeout
18185 Show the current number of seconds to wait for the remote target
18188 @cindex limit hardware breakpoints and watchpoints
18189 @cindex remote target, limit break- and watchpoints
18190 @anchor{set remote hardware-watchpoint-limit}
18191 @anchor{set remote hardware-breakpoint-limit}
18192 @item set remote hardware-watchpoint-limit @var{limit}
18193 @itemx set remote hardware-breakpoint-limit @var{limit}
18194 Restrict @value{GDBN} to using @var{limit} remote hardware breakpoint or
18195 watchpoints. A limit of -1, the default, is treated as unlimited.
18197 @cindex limit hardware watchpoints length
18198 @cindex remote target, limit watchpoints length
18199 @anchor{set remote hardware-watchpoint-length-limit}
18200 @item set remote hardware-watchpoint-length-limit @var{limit}
18201 Restrict @value{GDBN} to using @var{limit} bytes for the maximum length of
18202 a remote hardware watchpoint. A limit of -1, the default, is treated
18205 @item show remote hardware-watchpoint-length-limit
18206 Show the current limit (in bytes) of the maximum length of
18207 a remote hardware watchpoint.
18209 @item set remote exec-file @var{filename}
18210 @itemx show remote exec-file
18211 @anchor{set remote exec-file}
18212 @cindex executable file, for remote target
18213 Select the file used for @code{run} with @code{target
18214 extended-remote}. This should be set to a filename valid on the
18215 target system. If it is not set, the target will use a default
18216 filename (e.g.@: the last program run).
18218 @item set remote interrupt-sequence
18219 @cindex interrupt remote programs
18220 @cindex select Ctrl-C, BREAK or BREAK-g
18221 Allow the user to select one of @samp{Ctrl-C}, a @code{BREAK} or
18222 @samp{BREAK-g} as the
18223 sequence to the remote target in order to interrupt the execution.
18224 @samp{Ctrl-C} is a default. Some system prefers @code{BREAK} which
18225 is high level of serial line for some certain time.
18226 Linux kernel prefers @samp{BREAK-g}, a.k.a Magic SysRq g.
18227 It is @code{BREAK} signal followed by character @code{g}.
18229 @item show interrupt-sequence
18230 Show which of @samp{Ctrl-C}, @code{BREAK} or @code{BREAK-g}
18231 is sent by @value{GDBN} to interrupt the remote program.
18232 @code{BREAK-g} is BREAK signal followed by @code{g} and
18233 also known as Magic SysRq g.
18235 @item set remote interrupt-on-connect
18236 @cindex send interrupt-sequence on start
18237 Specify whether interrupt-sequence is sent to remote target when
18238 @value{GDBN} connects to it. This is mostly needed when you debug
18239 Linux kernel. Linux kernel expects @code{BREAK} followed by @code{g}
18240 which is known as Magic SysRq g in order to connect @value{GDBN}.
18242 @item show interrupt-on-connect
18243 Show whether interrupt-sequence is sent
18244 to remote target when @value{GDBN} connects to it.
18248 @item set tcp auto-retry on
18249 @cindex auto-retry, for remote TCP target
18250 Enable auto-retry for remote TCP connections. This is useful if the remote
18251 debugging agent is launched in parallel with @value{GDBN}; there is a race
18252 condition because the agent may not become ready to accept the connection
18253 before @value{GDBN} attempts to connect. When auto-retry is
18254 enabled, if the initial attempt to connect fails, @value{GDBN} reattempts
18255 to establish the connection using the timeout specified by
18256 @code{set tcp connect-timeout}.
18258 @item set tcp auto-retry off
18259 Do not auto-retry failed TCP connections.
18261 @item show tcp auto-retry
18262 Show the current auto-retry setting.
18264 @item set tcp connect-timeout @var{seconds}
18265 @cindex connection timeout, for remote TCP target
18266 @cindex timeout, for remote target connection
18267 Set the timeout for establishing a TCP connection to the remote target to
18268 @var{seconds}. The timeout affects both polling to retry failed connections
18269 (enabled by @code{set tcp auto-retry on}) and waiting for connections
18270 that are merely slow to complete, and represents an approximate cumulative
18273 @item show tcp connect-timeout
18274 Show the current connection timeout setting.
18277 @cindex remote packets, enabling and disabling
18278 The @value{GDBN} remote protocol autodetects the packets supported by
18279 your debugging stub. If you need to override the autodetection, you
18280 can use these commands to enable or disable individual packets. Each
18281 packet can be set to @samp{on} (the remote target supports this
18282 packet), @samp{off} (the remote target does not support this packet),
18283 or @samp{auto} (detect remote target support for this packet). They
18284 all default to @samp{auto}. For more information about each packet,
18285 see @ref{Remote Protocol}.
18287 During normal use, you should not have to use any of these commands.
18288 If you do, that may be a bug in your remote debugging stub, or a bug
18289 in @value{GDBN}. You may want to report the problem to the
18290 @value{GDBN} developers.
18292 For each packet @var{name}, the command to enable or disable the
18293 packet is @code{set remote @var{name}-packet}. The available settings
18296 @multitable @columnfractions 0.28 0.32 0.25
18299 @tab Related Features
18301 @item @code{fetch-register}
18303 @tab @code{info registers}
18305 @item @code{set-register}
18309 @item @code{binary-download}
18311 @tab @code{load}, @code{set}
18313 @item @code{read-aux-vector}
18314 @tab @code{qXfer:auxv:read}
18315 @tab @code{info auxv}
18317 @item @code{symbol-lookup}
18318 @tab @code{qSymbol}
18319 @tab Detecting multiple threads
18321 @item @code{attach}
18322 @tab @code{vAttach}
18325 @item @code{verbose-resume}
18327 @tab Stepping or resuming multiple threads
18333 @item @code{software-breakpoint}
18337 @item @code{hardware-breakpoint}
18341 @item @code{write-watchpoint}
18345 @item @code{read-watchpoint}
18349 @item @code{access-watchpoint}
18353 @item @code{target-features}
18354 @tab @code{qXfer:features:read}
18355 @tab @code{set architecture}
18357 @item @code{library-info}
18358 @tab @code{qXfer:libraries:read}
18359 @tab @code{info sharedlibrary}
18361 @item @code{memory-map}
18362 @tab @code{qXfer:memory-map:read}
18363 @tab @code{info mem}
18365 @item @code{read-sdata-object}
18366 @tab @code{qXfer:sdata:read}
18367 @tab @code{print $_sdata}
18369 @item @code{read-spu-object}
18370 @tab @code{qXfer:spu:read}
18371 @tab @code{info spu}
18373 @item @code{write-spu-object}
18374 @tab @code{qXfer:spu:write}
18375 @tab @code{info spu}
18377 @item @code{read-siginfo-object}
18378 @tab @code{qXfer:siginfo:read}
18379 @tab @code{print $_siginfo}
18381 @item @code{write-siginfo-object}
18382 @tab @code{qXfer:siginfo:write}
18383 @tab @code{set $_siginfo}
18385 @item @code{threads}
18386 @tab @code{qXfer:threads:read}
18387 @tab @code{info threads}
18389 @item @code{get-thread-local-@*storage-address}
18390 @tab @code{qGetTLSAddr}
18391 @tab Displaying @code{__thread} variables
18393 @item @code{get-thread-information-block-address}
18394 @tab @code{qGetTIBAddr}
18395 @tab Display MS-Windows Thread Information Block.
18397 @item @code{search-memory}
18398 @tab @code{qSearch:memory}
18401 @item @code{supported-packets}
18402 @tab @code{qSupported}
18403 @tab Remote communications parameters
18405 @item @code{pass-signals}
18406 @tab @code{QPassSignals}
18407 @tab @code{handle @var{signal}}
18409 @item @code{program-signals}
18410 @tab @code{QProgramSignals}
18411 @tab @code{handle @var{signal}}
18413 @item @code{hostio-close-packet}
18414 @tab @code{vFile:close}
18415 @tab @code{remote get}, @code{remote put}
18417 @item @code{hostio-open-packet}
18418 @tab @code{vFile:open}
18419 @tab @code{remote get}, @code{remote put}
18421 @item @code{hostio-pread-packet}
18422 @tab @code{vFile:pread}
18423 @tab @code{remote get}, @code{remote put}
18425 @item @code{hostio-pwrite-packet}
18426 @tab @code{vFile:pwrite}
18427 @tab @code{remote get}, @code{remote put}
18429 @item @code{hostio-unlink-packet}
18430 @tab @code{vFile:unlink}
18431 @tab @code{remote delete}
18433 @item @code{hostio-readlink-packet}
18434 @tab @code{vFile:readlink}
18437 @item @code{noack-packet}
18438 @tab @code{QStartNoAckMode}
18439 @tab Packet acknowledgment
18441 @item @code{osdata}
18442 @tab @code{qXfer:osdata:read}
18443 @tab @code{info os}
18445 @item @code{query-attached}
18446 @tab @code{qAttached}
18447 @tab Querying remote process attach state.
18449 @item @code{traceframe-info}
18450 @tab @code{qXfer:traceframe-info:read}
18451 @tab Traceframe info
18453 @item @code{install-in-trace}
18454 @tab @code{InstallInTrace}
18455 @tab Install tracepoint in tracing
18457 @item @code{disable-randomization}
18458 @tab @code{QDisableRandomization}
18459 @tab @code{set disable-randomization}
18461 @item @code{conditional-breakpoints-packet}
18462 @tab @code{Z0 and Z1}
18463 @tab @code{Support for target-side breakpoint condition evaluation}
18467 @section Implementing a Remote Stub
18469 @cindex debugging stub, example
18470 @cindex remote stub, example
18471 @cindex stub example, remote debugging
18472 The stub files provided with @value{GDBN} implement the target side of the
18473 communication protocol, and the @value{GDBN} side is implemented in the
18474 @value{GDBN} source file @file{remote.c}. Normally, you can simply allow
18475 these subroutines to communicate, and ignore the details. (If you're
18476 implementing your own stub file, you can still ignore the details: start
18477 with one of the existing stub files. @file{sparc-stub.c} is the best
18478 organized, and therefore the easiest to read.)
18480 @cindex remote serial debugging, overview
18481 To debug a program running on another machine (the debugging
18482 @dfn{target} machine), you must first arrange for all the usual
18483 prerequisites for the program to run by itself. For example, for a C
18488 A startup routine to set up the C runtime environment; these usually
18489 have a name like @file{crt0}. The startup routine may be supplied by
18490 your hardware supplier, or you may have to write your own.
18493 A C subroutine library to support your program's
18494 subroutine calls, notably managing input and output.
18497 A way of getting your program to the other machine---for example, a
18498 download program. These are often supplied by the hardware
18499 manufacturer, but you may have to write your own from hardware
18503 The next step is to arrange for your program to use a serial port to
18504 communicate with the machine where @value{GDBN} is running (the @dfn{host}
18505 machine). In general terms, the scheme looks like this:
18509 @value{GDBN} already understands how to use this protocol; when everything
18510 else is set up, you can simply use the @samp{target remote} command
18511 (@pxref{Targets,,Specifying a Debugging Target}).
18513 @item On the target,
18514 you must link with your program a few special-purpose subroutines that
18515 implement the @value{GDBN} remote serial protocol. The file containing these
18516 subroutines is called a @dfn{debugging stub}.
18518 On certain remote targets, you can use an auxiliary program
18519 @code{gdbserver} instead of linking a stub into your program.
18520 @xref{Server,,Using the @code{gdbserver} Program}, for details.
18523 The debugging stub is specific to the architecture of the remote
18524 machine; for example, use @file{sparc-stub.c} to debug programs on
18527 @cindex remote serial stub list
18528 These working remote stubs are distributed with @value{GDBN}:
18533 @cindex @file{i386-stub.c}
18536 For Intel 386 and compatible architectures.
18539 @cindex @file{m68k-stub.c}
18540 @cindex Motorola 680x0
18542 For Motorola 680x0 architectures.
18545 @cindex @file{sh-stub.c}
18548 For Renesas SH architectures.
18551 @cindex @file{sparc-stub.c}
18553 For @sc{sparc} architectures.
18555 @item sparcl-stub.c
18556 @cindex @file{sparcl-stub.c}
18559 For Fujitsu @sc{sparclite} architectures.
18563 The @file{README} file in the @value{GDBN} distribution may list other
18564 recently added stubs.
18567 * Stub Contents:: What the stub can do for you
18568 * Bootstrapping:: What you must do for the stub
18569 * Debug Session:: Putting it all together
18572 @node Stub Contents
18573 @subsection What the Stub Can Do for You
18575 @cindex remote serial stub
18576 The debugging stub for your architecture supplies these three
18580 @item set_debug_traps
18581 @findex set_debug_traps
18582 @cindex remote serial stub, initialization
18583 This routine arranges for @code{handle_exception} to run when your
18584 program stops. You must call this subroutine explicitly in your
18585 program's startup code.
18587 @item handle_exception
18588 @findex handle_exception
18589 @cindex remote serial stub, main routine
18590 This is the central workhorse, but your program never calls it
18591 explicitly---the setup code arranges for @code{handle_exception} to
18592 run when a trap is triggered.
18594 @code{handle_exception} takes control when your program stops during
18595 execution (for example, on a breakpoint), and mediates communications
18596 with @value{GDBN} on the host machine. This is where the communications
18597 protocol is implemented; @code{handle_exception} acts as the @value{GDBN}
18598 representative on the target machine. It begins by sending summary
18599 information on the state of your program, then continues to execute,
18600 retrieving and transmitting any information @value{GDBN} needs, until you
18601 execute a @value{GDBN} command that makes your program resume; at that point,
18602 @code{handle_exception} returns control to your own code on the target
18606 @cindex @code{breakpoint} subroutine, remote
18607 Use this auxiliary subroutine to make your program contain a
18608 breakpoint. Depending on the particular situation, this may be the only
18609 way for @value{GDBN} to get control. For instance, if your target
18610 machine has some sort of interrupt button, you won't need to call this;
18611 pressing the interrupt button transfers control to
18612 @code{handle_exception}---in effect, to @value{GDBN}. On some machines,
18613 simply receiving characters on the serial port may also trigger a trap;
18614 again, in that situation, you don't need to call @code{breakpoint} from
18615 your own program---simply running @samp{target remote} from the host
18616 @value{GDBN} session gets control.
18618 Call @code{breakpoint} if none of these is true, or if you simply want
18619 to make certain your program stops at a predetermined point for the
18620 start of your debugging session.
18623 @node Bootstrapping
18624 @subsection What You Must Do for the Stub
18626 @cindex remote stub, support routines
18627 The debugging stubs that come with @value{GDBN} are set up for a particular
18628 chip architecture, but they have no information about the rest of your
18629 debugging target machine.
18631 First of all you need to tell the stub how to communicate with the
18635 @item int getDebugChar()
18636 @findex getDebugChar
18637 Write this subroutine to read a single character from the serial port.
18638 It may be identical to @code{getchar} for your target system; a
18639 different name is used to allow you to distinguish the two if you wish.
18641 @item void putDebugChar(int)
18642 @findex putDebugChar
18643 Write this subroutine to write a single character to the serial port.
18644 It may be identical to @code{putchar} for your target system; a
18645 different name is used to allow you to distinguish the two if you wish.
18648 @cindex control C, and remote debugging
18649 @cindex interrupting remote targets
18650 If you want @value{GDBN} to be able to stop your program while it is
18651 running, you need to use an interrupt-driven serial driver, and arrange
18652 for it to stop when it receives a @code{^C} (@samp{\003}, the control-C
18653 character). That is the character which @value{GDBN} uses to tell the
18654 remote system to stop.
18656 Getting the debugging target to return the proper status to @value{GDBN}
18657 probably requires changes to the standard stub; one quick and dirty way
18658 is to just execute a breakpoint instruction (the ``dirty'' part is that
18659 @value{GDBN} reports a @code{SIGTRAP} instead of a @code{SIGINT}).
18661 Other routines you need to supply are:
18664 @item void exceptionHandler (int @var{exception_number}, void *@var{exception_address})
18665 @findex exceptionHandler
18666 Write this function to install @var{exception_address} in the exception
18667 handling tables. You need to do this because the stub does not have any
18668 way of knowing what the exception handling tables on your target system
18669 are like (for example, the processor's table might be in @sc{rom},
18670 containing entries which point to a table in @sc{ram}).
18671 @var{exception_number} is the exception number which should be changed;
18672 its meaning is architecture-dependent (for example, different numbers
18673 might represent divide by zero, misaligned access, etc). When this
18674 exception occurs, control should be transferred directly to
18675 @var{exception_address}, and the processor state (stack, registers,
18676 and so on) should be just as it is when a processor exception occurs. So if
18677 you want to use a jump instruction to reach @var{exception_address}, it
18678 should be a simple jump, not a jump to subroutine.
18680 For the 386, @var{exception_address} should be installed as an interrupt
18681 gate so that interrupts are masked while the handler runs. The gate
18682 should be at privilege level 0 (the most privileged level). The
18683 @sc{sparc} and 68k stubs are able to mask interrupts themselves without
18684 help from @code{exceptionHandler}.
18686 @item void flush_i_cache()
18687 @findex flush_i_cache
18688 On @sc{sparc} and @sc{sparclite} only, write this subroutine to flush the
18689 instruction cache, if any, on your target machine. If there is no
18690 instruction cache, this subroutine may be a no-op.
18692 On target machines that have instruction caches, @value{GDBN} requires this
18693 function to make certain that the state of your program is stable.
18697 You must also make sure this library routine is available:
18700 @item void *memset(void *, int, int)
18702 This is the standard library function @code{memset} that sets an area of
18703 memory to a known value. If you have one of the free versions of
18704 @code{libc.a}, @code{memset} can be found there; otherwise, you must
18705 either obtain it from your hardware manufacturer, or write your own.
18708 If you do not use the GNU C compiler, you may need other standard
18709 library subroutines as well; this varies from one stub to another,
18710 but in general the stubs are likely to use any of the common library
18711 subroutines which @code{@value{NGCC}} generates as inline code.
18714 @node Debug Session
18715 @subsection Putting it All Together
18717 @cindex remote serial debugging summary
18718 In summary, when your program is ready to debug, you must follow these
18723 Make sure you have defined the supporting low-level routines
18724 (@pxref{Bootstrapping,,What You Must Do for the Stub}):
18726 @code{getDebugChar}, @code{putDebugChar},
18727 @code{flush_i_cache}, @code{memset}, @code{exceptionHandler}.
18731 Insert these lines in your program's startup code, before the main
18732 procedure is called:
18739 On some machines, when a breakpoint trap is raised, the hardware
18740 automatically makes the PC point to the instruction after the
18741 breakpoint. If your machine doesn't do that, you may need to adjust
18742 @code{handle_exception} to arrange for it to return to the instruction
18743 after the breakpoint on this first invocation, so that your program
18744 doesn't keep hitting the initial breakpoint instead of making
18748 For the 680x0 stub only, you need to provide a variable called
18749 @code{exceptionHook}. Normally you just use:
18752 void (*exceptionHook)() = 0;
18756 but if before calling @code{set_debug_traps}, you set it to point to a
18757 function in your program, that function is called when
18758 @code{@value{GDBN}} continues after stopping on a trap (for example, bus
18759 error). The function indicated by @code{exceptionHook} is called with
18760 one parameter: an @code{int} which is the exception number.
18763 Compile and link together: your program, the @value{GDBN} debugging stub for
18764 your target architecture, and the supporting subroutines.
18767 Make sure you have a serial connection between your target machine and
18768 the @value{GDBN} host, and identify the serial port on the host.
18771 @c The "remote" target now provides a `load' command, so we should
18772 @c document that. FIXME.
18773 Download your program to your target machine (or get it there by
18774 whatever means the manufacturer provides), and start it.
18777 Start @value{GDBN} on the host, and connect to the target
18778 (@pxref{Connecting,,Connecting to a Remote Target}).
18782 @node Configurations
18783 @chapter Configuration-Specific Information
18785 While nearly all @value{GDBN} commands are available for all native and
18786 cross versions of the debugger, there are some exceptions. This chapter
18787 describes things that are only available in certain configurations.
18789 There are three major categories of configurations: native
18790 configurations, where the host and target are the same, embedded
18791 operating system configurations, which are usually the same for several
18792 different processor architectures, and bare embedded processors, which
18793 are quite different from each other.
18798 * Embedded Processors::
18805 This section describes details specific to particular native
18810 * BSD libkvm Interface:: Debugging BSD kernel memory images
18811 * SVR4 Process Information:: SVR4 process information
18812 * DJGPP Native:: Features specific to the DJGPP port
18813 * Cygwin Native:: Features specific to the Cygwin port
18814 * Hurd Native:: Features specific to @sc{gnu} Hurd
18815 * Darwin:: Features specific to Darwin
18821 On HP-UX systems, if you refer to a function or variable name that
18822 begins with a dollar sign, @value{GDBN} searches for a user or system
18823 name first, before it searches for a convenience variable.
18826 @node BSD libkvm Interface
18827 @subsection BSD libkvm Interface
18830 @cindex kernel memory image
18831 @cindex kernel crash dump
18833 BSD-derived systems (FreeBSD/NetBSD/OpenBSD) have a kernel memory
18834 interface that provides a uniform interface for accessing kernel virtual
18835 memory images, including live systems and crash dumps. @value{GDBN}
18836 uses this interface to allow you to debug live kernels and kernel crash
18837 dumps on many native BSD configurations. This is implemented as a
18838 special @code{kvm} debugging target. For debugging a live system, load
18839 the currently running kernel into @value{GDBN} and connect to the
18843 (@value{GDBP}) @b{target kvm}
18846 For debugging crash dumps, provide the file name of the crash dump as an
18850 (@value{GDBP}) @b{target kvm /var/crash/bsd.0}
18853 Once connected to the @code{kvm} target, the following commands are
18859 Set current context from the @dfn{Process Control Block} (PCB) address.
18862 Set current context from proc address. This command isn't available on
18863 modern FreeBSD systems.
18866 @node SVR4 Process Information
18867 @subsection SVR4 Process Information
18869 @cindex examine process image
18870 @cindex process info via @file{/proc}
18872 Many versions of SVR4 and compatible systems provide a facility called
18873 @samp{/proc} that can be used to examine the image of a running
18874 process using file-system subroutines.
18876 If @value{GDBN} is configured for an operating system with this
18877 facility, the command @code{info proc} is available to report
18878 information about the process running your program, or about any
18879 process running on your system. This includes, as of this writing,
18880 @sc{gnu}/Linux, OSF/1 (Digital Unix), Solaris, and Irix, but
18881 not HP-UX, for example.
18883 This command may also work on core files that were created on a system
18884 that has the @samp{/proc} facility.
18890 @itemx info proc @var{process-id}
18891 Summarize available information about any running process. If a
18892 process ID is specified by @var{process-id}, display information about
18893 that process; otherwise display information about the program being
18894 debugged. The summary includes the debugged process ID, the command
18895 line used to invoke it, its current working directory, and its
18896 executable file's absolute file name.
18898 On some systems, @var{process-id} can be of the form
18899 @samp{[@var{pid}]/@var{tid}} which specifies a certain thread ID
18900 within a process. If the optional @var{pid} part is missing, it means
18901 a thread from the process being debugged (the leading @samp{/} still
18902 needs to be present, or else @value{GDBN} will interpret the number as
18903 a process ID rather than a thread ID).
18905 @item info proc cmdline
18906 @cindex info proc cmdline
18907 Show the original command line of the process. This command is
18908 specific to @sc{gnu}/Linux.
18910 @item info proc cwd
18911 @cindex info proc cwd
18912 Show the current working directory of the process. This command is
18913 specific to @sc{gnu}/Linux.
18915 @item info proc exe
18916 @cindex info proc exe
18917 Show the name of executable of the process. This command is specific
18920 @item info proc mappings
18921 @cindex memory address space mappings
18922 Report the memory address space ranges accessible in the program, with
18923 information on whether the process has read, write, or execute access
18924 rights to each range. On @sc{gnu}/Linux systems, each memory range
18925 includes the object file which is mapped to that range, instead of the
18926 memory access rights to that range.
18928 @item info proc stat
18929 @itemx info proc status
18930 @cindex process detailed status information
18931 These subcommands are specific to @sc{gnu}/Linux systems. They show
18932 the process-related information, including the user ID and group ID;
18933 how many threads are there in the process; its virtual memory usage;
18934 the signals that are pending, blocked, and ignored; its TTY; its
18935 consumption of system and user time; its stack size; its @samp{nice}
18936 value; etc. For more information, see the @samp{proc} man page
18937 (type @kbd{man 5 proc} from your shell prompt).
18939 @item info proc all
18940 Show all the information about the process described under all of the
18941 above @code{info proc} subcommands.
18944 @comment These sub-options of 'info proc' were not included when
18945 @comment procfs.c was re-written. Keep their descriptions around
18946 @comment against the day when someone finds the time to put them back in.
18947 @kindex info proc times
18948 @item info proc times
18949 Starting time, user CPU time, and system CPU time for your program and
18952 @kindex info proc id
18954 Report on the process IDs related to your program: its own process ID,
18955 the ID of its parent, the process group ID, and the session ID.
18958 @item set procfs-trace
18959 @kindex set procfs-trace
18960 @cindex @code{procfs} API calls
18961 This command enables and disables tracing of @code{procfs} API calls.
18963 @item show procfs-trace
18964 @kindex show procfs-trace
18965 Show the current state of @code{procfs} API call tracing.
18967 @item set procfs-file @var{file}
18968 @kindex set procfs-file
18969 Tell @value{GDBN} to write @code{procfs} API trace to the named
18970 @var{file}. @value{GDBN} appends the trace info to the previous
18971 contents of the file. The default is to display the trace on the
18974 @item show procfs-file
18975 @kindex show procfs-file
18976 Show the file to which @code{procfs} API trace is written.
18978 @item proc-trace-entry
18979 @itemx proc-trace-exit
18980 @itemx proc-untrace-entry
18981 @itemx proc-untrace-exit
18982 @kindex proc-trace-entry
18983 @kindex proc-trace-exit
18984 @kindex proc-untrace-entry
18985 @kindex proc-untrace-exit
18986 These commands enable and disable tracing of entries into and exits
18987 from the @code{syscall} interface.
18990 @kindex info pidlist
18991 @cindex process list, QNX Neutrino
18992 For QNX Neutrino only, this command displays the list of all the
18993 processes and all the threads within each process.
18996 @kindex info meminfo
18997 @cindex mapinfo list, QNX Neutrino
18998 For QNX Neutrino only, this command displays the list of all mapinfos.
19002 @subsection Features for Debugging @sc{djgpp} Programs
19003 @cindex @sc{djgpp} debugging
19004 @cindex native @sc{djgpp} debugging
19005 @cindex MS-DOS-specific commands
19008 @sc{djgpp} is a port of the @sc{gnu} development tools to MS-DOS and
19009 MS-Windows. @sc{djgpp} programs are 32-bit protected-mode programs
19010 that use the @dfn{DPMI} (DOS Protected-Mode Interface) API to run on
19011 top of real-mode DOS systems and their emulations.
19013 @value{GDBN} supports native debugging of @sc{djgpp} programs, and
19014 defines a few commands specific to the @sc{djgpp} port. This
19015 subsection describes those commands.
19020 This is a prefix of @sc{djgpp}-specific commands which print
19021 information about the target system and important OS structures.
19024 @cindex MS-DOS system info
19025 @cindex free memory information (MS-DOS)
19026 @item info dos sysinfo
19027 This command displays assorted information about the underlying
19028 platform: the CPU type and features, the OS version and flavor, the
19029 DPMI version, and the available conventional and DPMI memory.
19034 @cindex segment descriptor tables
19035 @cindex descriptor tables display
19037 @itemx info dos ldt
19038 @itemx info dos idt
19039 These 3 commands display entries from, respectively, Global, Local,
19040 and Interrupt Descriptor Tables (GDT, LDT, and IDT). The descriptor
19041 tables are data structures which store a descriptor for each segment
19042 that is currently in use. The segment's selector is an index into a
19043 descriptor table; the table entry for that index holds the
19044 descriptor's base address and limit, and its attributes and access
19047 A typical @sc{djgpp} program uses 3 segments: a code segment, a data
19048 segment (used for both data and the stack), and a DOS segment (which
19049 allows access to DOS/BIOS data structures and absolute addresses in
19050 conventional memory). However, the DPMI host will usually define
19051 additional segments in order to support the DPMI environment.
19053 @cindex garbled pointers
19054 These commands allow to display entries from the descriptor tables.
19055 Without an argument, all entries from the specified table are
19056 displayed. An argument, which should be an integer expression, means
19057 display a single entry whose index is given by the argument. For
19058 example, here's a convenient way to display information about the
19059 debugged program's data segment:
19062 @exdent @code{(@value{GDBP}) info dos ldt $ds}
19063 @exdent @code{0x13f: base=0x11970000 limit=0x0009ffff 32-Bit Data (Read/Write, Exp-up)}
19067 This comes in handy when you want to see whether a pointer is outside
19068 the data segment's limit (i.e.@: @dfn{garbled}).
19070 @cindex page tables display (MS-DOS)
19072 @itemx info dos pte
19073 These two commands display entries from, respectively, the Page
19074 Directory and the Page Tables. Page Directories and Page Tables are
19075 data structures which control how virtual memory addresses are mapped
19076 into physical addresses. A Page Table includes an entry for every
19077 page of memory that is mapped into the program's address space; there
19078 may be several Page Tables, each one holding up to 4096 entries. A
19079 Page Directory has up to 4096 entries, one each for every Page Table
19080 that is currently in use.
19082 Without an argument, @kbd{info dos pde} displays the entire Page
19083 Directory, and @kbd{info dos pte} displays all the entries in all of
19084 the Page Tables. An argument, an integer expression, given to the
19085 @kbd{info dos pde} command means display only that entry from the Page
19086 Directory table. An argument given to the @kbd{info dos pte} command
19087 means display entries from a single Page Table, the one pointed to by
19088 the specified entry in the Page Directory.
19090 @cindex direct memory access (DMA) on MS-DOS
19091 These commands are useful when your program uses @dfn{DMA} (Direct
19092 Memory Access), which needs physical addresses to program the DMA
19095 These commands are supported only with some DPMI servers.
19097 @cindex physical address from linear address
19098 @item info dos address-pte @var{addr}
19099 This command displays the Page Table entry for a specified linear
19100 address. The argument @var{addr} is a linear address which should
19101 already have the appropriate segment's base address added to it,
19102 because this command accepts addresses which may belong to @emph{any}
19103 segment. For example, here's how to display the Page Table entry for
19104 the page where a variable @code{i} is stored:
19107 @exdent @code{(@value{GDBP}) info dos address-pte __djgpp_base_address + (char *)&i}
19108 @exdent @code{Page Table entry for address 0x11a00d30:}
19109 @exdent @code{Base=0x02698000 Dirty Acc. Not-Cached Write-Back Usr Read-Write +0xd30}
19113 This says that @code{i} is stored at offset @code{0xd30} from the page
19114 whose physical base address is @code{0x02698000}, and shows all the
19115 attributes of that page.
19117 Note that you must cast the addresses of variables to a @code{char *},
19118 since otherwise the value of @code{__djgpp_base_address}, the base
19119 address of all variables and functions in a @sc{djgpp} program, will
19120 be added using the rules of C pointer arithmetics: if @code{i} is
19121 declared an @code{int}, @value{GDBN} will add 4 times the value of
19122 @code{__djgpp_base_address} to the address of @code{i}.
19124 Here's another example, it displays the Page Table entry for the
19128 @exdent @code{(@value{GDBP}) info dos address-pte *((unsigned *)&_go32_info_block + 3)}
19129 @exdent @code{Page Table entry for address 0x29110:}
19130 @exdent @code{Base=0x00029000 Dirty Acc. Not-Cached Write-Back Usr Read-Write +0x110}
19134 (The @code{+ 3} offset is because the transfer buffer's address is the
19135 3rd member of the @code{_go32_info_block} structure.) The output
19136 clearly shows that this DPMI server maps the addresses in conventional
19137 memory 1:1, i.e.@: the physical (@code{0x00029000} + @code{0x110}) and
19138 linear (@code{0x29110}) addresses are identical.
19140 This command is supported only with some DPMI servers.
19143 @cindex DOS serial data link, remote debugging
19144 In addition to native debugging, the DJGPP port supports remote
19145 debugging via a serial data link. The following commands are specific
19146 to remote serial debugging in the DJGPP port of @value{GDBN}.
19149 @kindex set com1base
19150 @kindex set com1irq
19151 @kindex set com2base
19152 @kindex set com2irq
19153 @kindex set com3base
19154 @kindex set com3irq
19155 @kindex set com4base
19156 @kindex set com4irq
19157 @item set com1base @var{addr}
19158 This command sets the base I/O port address of the @file{COM1} serial
19161 @item set com1irq @var{irq}
19162 This command sets the @dfn{Interrupt Request} (@code{IRQ}) line to use
19163 for the @file{COM1} serial port.
19165 There are similar commands @samp{set com2base}, @samp{set com3irq},
19166 etc.@: for setting the port address and the @code{IRQ} lines for the
19169 @kindex show com1base
19170 @kindex show com1irq
19171 @kindex show com2base
19172 @kindex show com2irq
19173 @kindex show com3base
19174 @kindex show com3irq
19175 @kindex show com4base
19176 @kindex show com4irq
19177 The related commands @samp{show com1base}, @samp{show com1irq} etc.@:
19178 display the current settings of the base address and the @code{IRQ}
19179 lines used by the COM ports.
19182 @kindex info serial
19183 @cindex DOS serial port status
19184 This command prints the status of the 4 DOS serial ports. For each
19185 port, it prints whether it's active or not, its I/O base address and
19186 IRQ number, whether it uses a 16550-style FIFO, its baudrate, and the
19187 counts of various errors encountered so far.
19191 @node Cygwin Native
19192 @subsection Features for Debugging MS Windows PE Executables
19193 @cindex MS Windows debugging
19194 @cindex native Cygwin debugging
19195 @cindex Cygwin-specific commands
19197 @value{GDBN} supports native debugging of MS Windows programs, including
19198 DLLs with and without symbolic debugging information.
19200 @cindex Ctrl-BREAK, MS-Windows
19201 @cindex interrupt debuggee on MS-Windows
19202 MS-Windows programs that call @code{SetConsoleMode} to switch off the
19203 special meaning of the @samp{Ctrl-C} keystroke cannot be interrupted
19204 by typing @kbd{C-c}. For this reason, @value{GDBN} on MS-Windows
19205 supports @kbd{C-@key{BREAK}} as an alternative interrupt key
19206 sequence, which can be used to interrupt the debuggee even if it
19209 There are various additional Cygwin-specific commands, described in
19210 this section. Working with DLLs that have no debugging symbols is
19211 described in @ref{Non-debug DLL Symbols}.
19216 This is a prefix of MS Windows-specific commands which print
19217 information about the target system and important OS structures.
19219 @item info w32 selector
19220 This command displays information returned by
19221 the Win32 API @code{GetThreadSelectorEntry} function.
19222 It takes an optional argument that is evaluated to
19223 a long value to give the information about this given selector.
19224 Without argument, this command displays information
19225 about the six segment registers.
19227 @item info w32 thread-information-block
19228 This command displays thread specific information stored in the
19229 Thread Information Block (readable on the X86 CPU family using @code{$fs}
19230 selector for 32-bit programs and @code{$gs} for 64-bit programs).
19234 This is a Cygwin-specific alias of @code{info shared}.
19236 @kindex dll-symbols
19238 This command loads symbols from a dll similarly to
19239 add-sym command but without the need to specify a base address.
19241 @kindex set cygwin-exceptions
19242 @cindex debugging the Cygwin DLL
19243 @cindex Cygwin DLL, debugging
19244 @item set cygwin-exceptions @var{mode}
19245 If @var{mode} is @code{on}, @value{GDBN} will break on exceptions that
19246 happen inside the Cygwin DLL. If @var{mode} is @code{off},
19247 @value{GDBN} will delay recognition of exceptions, and may ignore some
19248 exceptions which seem to be caused by internal Cygwin DLL
19249 ``bookkeeping''. This option is meant primarily for debugging the
19250 Cygwin DLL itself; the default value is @code{off} to avoid annoying
19251 @value{GDBN} users with false @code{SIGSEGV} signals.
19253 @kindex show cygwin-exceptions
19254 @item show cygwin-exceptions
19255 Displays whether @value{GDBN} will break on exceptions that happen
19256 inside the Cygwin DLL itself.
19258 @kindex set new-console
19259 @item set new-console @var{mode}
19260 If @var{mode} is @code{on} the debuggee will
19261 be started in a new console on next start.
19262 If @var{mode} is @code{off}, the debuggee will
19263 be started in the same console as the debugger.
19265 @kindex show new-console
19266 @item show new-console
19267 Displays whether a new console is used
19268 when the debuggee is started.
19270 @kindex set new-group
19271 @item set new-group @var{mode}
19272 This boolean value controls whether the debuggee should
19273 start a new group or stay in the same group as the debugger.
19274 This affects the way the Windows OS handles
19277 @kindex show new-group
19278 @item show new-group
19279 Displays current value of new-group boolean.
19281 @kindex set debugevents
19282 @item set debugevents
19283 This boolean value adds debug output concerning kernel events related
19284 to the debuggee seen by the debugger. This includes events that
19285 signal thread and process creation and exit, DLL loading and
19286 unloading, console interrupts, and debugging messages produced by the
19287 Windows @code{OutputDebugString} API call.
19289 @kindex set debugexec
19290 @item set debugexec
19291 This boolean value adds debug output concerning execute events
19292 (such as resume thread) seen by the debugger.
19294 @kindex set debugexceptions
19295 @item set debugexceptions
19296 This boolean value adds debug output concerning exceptions in the
19297 debuggee seen by the debugger.
19299 @kindex set debugmemory
19300 @item set debugmemory
19301 This boolean value adds debug output concerning debuggee memory reads
19302 and writes by the debugger.
19306 This boolean values specifies whether the debuggee is called
19307 via a shell or directly (default value is on).
19311 Displays if the debuggee will be started with a shell.
19316 * Non-debug DLL Symbols:: Support for DLLs without debugging symbols
19319 @node Non-debug DLL Symbols
19320 @subsubsection Support for DLLs without Debugging Symbols
19321 @cindex DLLs with no debugging symbols
19322 @cindex Minimal symbols and DLLs
19324 Very often on windows, some of the DLLs that your program relies on do
19325 not include symbolic debugging information (for example,
19326 @file{kernel32.dll}). When @value{GDBN} doesn't recognize any debugging
19327 symbols in a DLL, it relies on the minimal amount of symbolic
19328 information contained in the DLL's export table. This section
19329 describes working with such symbols, known internally to @value{GDBN} as
19330 ``minimal symbols''.
19332 Note that before the debugged program has started execution, no DLLs
19333 will have been loaded. The easiest way around this problem is simply to
19334 start the program --- either by setting a breakpoint or letting the
19335 program run once to completion. It is also possible to force
19336 @value{GDBN} to load a particular DLL before starting the executable ---
19337 see the shared library information in @ref{Files}, or the
19338 @code{dll-symbols} command in @ref{Cygwin Native}. Currently,
19339 explicitly loading symbols from a DLL with no debugging information will
19340 cause the symbol names to be duplicated in @value{GDBN}'s lookup table,
19341 which may adversely affect symbol lookup performance.
19343 @subsubsection DLL Name Prefixes
19345 In keeping with the naming conventions used by the Microsoft debugging
19346 tools, DLL export symbols are made available with a prefix based on the
19347 DLL name, for instance @code{KERNEL32!CreateFileA}. The plain name is
19348 also entered into the symbol table, so @code{CreateFileA} is often
19349 sufficient. In some cases there will be name clashes within a program
19350 (particularly if the executable itself includes full debugging symbols)
19351 necessitating the use of the fully qualified name when referring to the
19352 contents of the DLL. Use single-quotes around the name to avoid the
19353 exclamation mark (``!'') being interpreted as a language operator.
19355 Note that the internal name of the DLL may be all upper-case, even
19356 though the file name of the DLL is lower-case, or vice-versa. Since
19357 symbols within @value{GDBN} are @emph{case-sensitive} this may cause
19358 some confusion. If in doubt, try the @code{info functions} and
19359 @code{info variables} commands or even @code{maint print msymbols}
19360 (@pxref{Symbols}). Here's an example:
19363 (@value{GDBP}) info function CreateFileA
19364 All functions matching regular expression "CreateFileA":
19366 Non-debugging symbols:
19367 0x77e885f4 CreateFileA
19368 0x77e885f4 KERNEL32!CreateFileA
19372 (@value{GDBP}) info function !
19373 All functions matching regular expression "!":
19375 Non-debugging symbols:
19376 0x6100114c cygwin1!__assert
19377 0x61004034 cygwin1!_dll_crt0@@0
19378 0x61004240 cygwin1!dll_crt0(per_process *)
19382 @subsubsection Working with Minimal Symbols
19384 Symbols extracted from a DLL's export table do not contain very much
19385 type information. All that @value{GDBN} can do is guess whether a symbol
19386 refers to a function or variable depending on the linker section that
19387 contains the symbol. Also note that the actual contents of the memory
19388 contained in a DLL are not available unless the program is running. This
19389 means that you cannot examine the contents of a variable or disassemble
19390 a function within a DLL without a running program.
19392 Variables are generally treated as pointers and dereferenced
19393 automatically. For this reason, it is often necessary to prefix a
19394 variable name with the address-of operator (``&'') and provide explicit
19395 type information in the command. Here's an example of the type of
19399 (@value{GDBP}) print 'cygwin1!__argv'
19404 (@value{GDBP}) x 'cygwin1!__argv'
19405 0x10021610: "\230y\""
19408 And two possible solutions:
19411 (@value{GDBP}) print ((char **)'cygwin1!__argv')[0]
19412 $2 = 0x22fd98 "/cygdrive/c/mydirectory/myprogram"
19416 (@value{GDBP}) x/2x &'cygwin1!__argv'
19417 0x610c0aa8 <cygwin1!__argv>: 0x10021608 0x00000000
19418 (@value{GDBP}) x/x 0x10021608
19419 0x10021608: 0x0022fd98
19420 (@value{GDBP}) x/s 0x0022fd98
19421 0x22fd98: "/cygdrive/c/mydirectory/myprogram"
19424 Setting a break point within a DLL is possible even before the program
19425 starts execution. However, under these circumstances, @value{GDBN} can't
19426 examine the initial instructions of the function in order to skip the
19427 function's frame set-up code. You can work around this by using ``*&''
19428 to set the breakpoint at a raw memory address:
19431 (@value{GDBP}) break *&'python22!PyOS_Readline'
19432 Breakpoint 1 at 0x1e04eff0
19435 The author of these extensions is not entirely convinced that setting a
19436 break point within a shared DLL like @file{kernel32.dll} is completely
19440 @subsection Commands Specific to @sc{gnu} Hurd Systems
19441 @cindex @sc{gnu} Hurd debugging
19443 This subsection describes @value{GDBN} commands specific to the
19444 @sc{gnu} Hurd native debugging.
19449 @kindex set signals@r{, Hurd command}
19450 @kindex set sigs@r{, Hurd command}
19451 This command toggles the state of inferior signal interception by
19452 @value{GDBN}. Mach exceptions, such as breakpoint traps, are not
19453 affected by this command. @code{sigs} is a shorthand alias for
19458 @kindex show signals@r{, Hurd command}
19459 @kindex show sigs@r{, Hurd command}
19460 Show the current state of intercepting inferior's signals.
19462 @item set signal-thread
19463 @itemx set sigthread
19464 @kindex set signal-thread
19465 @kindex set sigthread
19466 This command tells @value{GDBN} which thread is the @code{libc} signal
19467 thread. That thread is run when a signal is delivered to a running
19468 process. @code{set sigthread} is the shorthand alias of @code{set
19471 @item show signal-thread
19472 @itemx show sigthread
19473 @kindex show signal-thread
19474 @kindex show sigthread
19475 These two commands show which thread will run when the inferior is
19476 delivered a signal.
19479 @kindex set stopped@r{, Hurd command}
19480 This commands tells @value{GDBN} that the inferior process is stopped,
19481 as with the @code{SIGSTOP} signal. The stopped process can be
19482 continued by delivering a signal to it.
19485 @kindex show stopped@r{, Hurd command}
19486 This command shows whether @value{GDBN} thinks the debuggee is
19489 @item set exceptions
19490 @kindex set exceptions@r{, Hurd command}
19491 Use this command to turn off trapping of exceptions in the inferior.
19492 When exception trapping is off, neither breakpoints nor
19493 single-stepping will work. To restore the default, set exception
19496 @item show exceptions
19497 @kindex show exceptions@r{, Hurd command}
19498 Show the current state of trapping exceptions in the inferior.
19500 @item set task pause
19501 @kindex set task@r{, Hurd commands}
19502 @cindex task attributes (@sc{gnu} Hurd)
19503 @cindex pause current task (@sc{gnu} Hurd)
19504 This command toggles task suspension when @value{GDBN} has control.
19505 Setting it to on takes effect immediately, and the task is suspended
19506 whenever @value{GDBN} gets control. Setting it to off will take
19507 effect the next time the inferior is continued. If this option is set
19508 to off, you can use @code{set thread default pause on} or @code{set
19509 thread pause on} (see below) to pause individual threads.
19511 @item show task pause
19512 @kindex show task@r{, Hurd commands}
19513 Show the current state of task suspension.
19515 @item set task detach-suspend-count
19516 @cindex task suspend count
19517 @cindex detach from task, @sc{gnu} Hurd
19518 This command sets the suspend count the task will be left with when
19519 @value{GDBN} detaches from it.
19521 @item show task detach-suspend-count
19522 Show the suspend count the task will be left with when detaching.
19524 @item set task exception-port
19525 @itemx set task excp
19526 @cindex task exception port, @sc{gnu} Hurd
19527 This command sets the task exception port to which @value{GDBN} will
19528 forward exceptions. The argument should be the value of the @dfn{send
19529 rights} of the task. @code{set task excp} is a shorthand alias.
19531 @item set noninvasive
19532 @cindex noninvasive task options
19533 This command switches @value{GDBN} to a mode that is the least
19534 invasive as far as interfering with the inferior is concerned. This
19535 is the same as using @code{set task pause}, @code{set exceptions}, and
19536 @code{set signals} to values opposite to the defaults.
19538 @item info send-rights
19539 @itemx info receive-rights
19540 @itemx info port-rights
19541 @itemx info port-sets
19542 @itemx info dead-names
19545 @cindex send rights, @sc{gnu} Hurd
19546 @cindex receive rights, @sc{gnu} Hurd
19547 @cindex port rights, @sc{gnu} Hurd
19548 @cindex port sets, @sc{gnu} Hurd
19549 @cindex dead names, @sc{gnu} Hurd
19550 These commands display information about, respectively, send rights,
19551 receive rights, port rights, port sets, and dead names of a task.
19552 There are also shorthand aliases: @code{info ports} for @code{info
19553 port-rights} and @code{info psets} for @code{info port-sets}.
19555 @item set thread pause
19556 @kindex set thread@r{, Hurd command}
19557 @cindex thread properties, @sc{gnu} Hurd
19558 @cindex pause current thread (@sc{gnu} Hurd)
19559 This command toggles current thread suspension when @value{GDBN} has
19560 control. Setting it to on takes effect immediately, and the current
19561 thread is suspended whenever @value{GDBN} gets control. Setting it to
19562 off will take effect the next time the inferior is continued.
19563 Normally, this command has no effect, since when @value{GDBN} has
19564 control, the whole task is suspended. However, if you used @code{set
19565 task pause off} (see above), this command comes in handy to suspend
19566 only the current thread.
19568 @item show thread pause
19569 @kindex show thread@r{, Hurd command}
19570 This command shows the state of current thread suspension.
19572 @item set thread run
19573 This command sets whether the current thread is allowed to run.
19575 @item show thread run
19576 Show whether the current thread is allowed to run.
19578 @item set thread detach-suspend-count
19579 @cindex thread suspend count, @sc{gnu} Hurd
19580 @cindex detach from thread, @sc{gnu} Hurd
19581 This command sets the suspend count @value{GDBN} will leave on a
19582 thread when detaching. This number is relative to the suspend count
19583 found by @value{GDBN} when it notices the thread; use @code{set thread
19584 takeover-suspend-count} to force it to an absolute value.
19586 @item show thread detach-suspend-count
19587 Show the suspend count @value{GDBN} will leave on the thread when
19590 @item set thread exception-port
19591 @itemx set thread excp
19592 Set the thread exception port to which to forward exceptions. This
19593 overrides the port set by @code{set task exception-port} (see above).
19594 @code{set thread excp} is the shorthand alias.
19596 @item set thread takeover-suspend-count
19597 Normally, @value{GDBN}'s thread suspend counts are relative to the
19598 value @value{GDBN} finds when it notices each thread. This command
19599 changes the suspend counts to be absolute instead.
19601 @item set thread default
19602 @itemx show thread default
19603 @cindex thread default settings, @sc{gnu} Hurd
19604 Each of the above @code{set thread} commands has a @code{set thread
19605 default} counterpart (e.g., @code{set thread default pause}, @code{set
19606 thread default exception-port}, etc.). The @code{thread default}
19607 variety of commands sets the default thread properties for all
19608 threads; you can then change the properties of individual threads with
19609 the non-default commands.
19616 @value{GDBN} provides the following commands specific to the Darwin target:
19619 @item set debug darwin @var{num}
19620 @kindex set debug darwin
19621 When set to a non zero value, enables debugging messages specific to
19622 the Darwin support. Higher values produce more verbose output.
19624 @item show debug darwin
19625 @kindex show debug darwin
19626 Show the current state of Darwin messages.
19628 @item set debug mach-o @var{num}
19629 @kindex set debug mach-o
19630 When set to a non zero value, enables debugging messages while
19631 @value{GDBN} is reading Darwin object files. (@dfn{Mach-O} is the
19632 file format used on Darwin for object and executable files.) Higher
19633 values produce more verbose output. This is a command to diagnose
19634 problems internal to @value{GDBN} and should not be needed in normal
19637 @item show debug mach-o
19638 @kindex show debug mach-o
19639 Show the current state of Mach-O file messages.
19641 @item set mach-exceptions on
19642 @itemx set mach-exceptions off
19643 @kindex set mach-exceptions
19644 On Darwin, faults are first reported as a Mach exception and are then
19645 mapped to a Posix signal. Use this command to turn on trapping of
19646 Mach exceptions in the inferior. This might be sometimes useful to
19647 better understand the cause of a fault. The default is off.
19649 @item show mach-exceptions
19650 @kindex show mach-exceptions
19651 Show the current state of exceptions trapping.
19656 @section Embedded Operating Systems
19658 This section describes configurations involving the debugging of
19659 embedded operating systems that are available for several different
19663 * VxWorks:: Using @value{GDBN} with VxWorks
19666 @value{GDBN} includes the ability to debug programs running on
19667 various real-time operating systems.
19670 @subsection Using @value{GDBN} with VxWorks
19676 @kindex target vxworks
19677 @item target vxworks @var{machinename}
19678 A VxWorks system, attached via TCP/IP. The argument @var{machinename}
19679 is the target system's machine name or IP address.
19683 On VxWorks, @code{load} links @var{filename} dynamically on the
19684 current target system as well as adding its symbols in @value{GDBN}.
19686 @value{GDBN} enables developers to spawn and debug tasks running on networked
19687 VxWorks targets from a Unix host. Already-running tasks spawned from
19688 the VxWorks shell can also be debugged. @value{GDBN} uses code that runs on
19689 both the Unix host and on the VxWorks target. The program
19690 @code{@value{GDBP}} is installed and executed on the Unix host. (It may be
19691 installed with the name @code{vxgdb}, to distinguish it from a
19692 @value{GDBN} for debugging programs on the host itself.)
19695 @item VxWorks-timeout @var{args}
19696 @kindex vxworks-timeout
19697 All VxWorks-based targets now support the option @code{vxworks-timeout}.
19698 This option is set by the user, and @var{args} represents the number of
19699 seconds @value{GDBN} waits for responses to rpc's. You might use this if
19700 your VxWorks target is a slow software simulator or is on the far side
19701 of a thin network line.
19704 The following information on connecting to VxWorks was current when
19705 this manual was produced; newer releases of VxWorks may use revised
19708 @findex INCLUDE_RDB
19709 To use @value{GDBN} with VxWorks, you must rebuild your VxWorks kernel
19710 to include the remote debugging interface routines in the VxWorks
19711 library @file{rdb.a}. To do this, define @code{INCLUDE_RDB} in the
19712 VxWorks configuration file @file{configAll.h} and rebuild your VxWorks
19713 kernel. The resulting kernel contains @file{rdb.a}, and spawns the
19714 source debugging task @code{tRdbTask} when VxWorks is booted. For more
19715 information on configuring and remaking VxWorks, see the manufacturer's
19717 @c VxWorks, see the @cite{VxWorks Programmer's Guide}.
19719 Once you have included @file{rdb.a} in your VxWorks system image and set
19720 your Unix execution search path to find @value{GDBN}, you are ready to
19721 run @value{GDBN}. From your Unix host, run @code{@value{GDBP}} (or
19722 @code{vxgdb}, depending on your installation).
19724 @value{GDBN} comes up showing the prompt:
19731 * VxWorks Connection:: Connecting to VxWorks
19732 * VxWorks Download:: VxWorks download
19733 * VxWorks Attach:: Running tasks
19736 @node VxWorks Connection
19737 @subsubsection Connecting to VxWorks
19739 The @value{GDBN} command @code{target} lets you connect to a VxWorks target on the
19740 network. To connect to a target whose host name is ``@code{tt}'', type:
19743 (vxgdb) target vxworks tt
19747 @value{GDBN} displays messages like these:
19750 Attaching remote machine across net...
19755 @value{GDBN} then attempts to read the symbol tables of any object modules
19756 loaded into the VxWorks target since it was last booted. @value{GDBN} locates
19757 these files by searching the directories listed in the command search
19758 path (@pxref{Environment, ,Your Program's Environment}); if it fails
19759 to find an object file, it displays a message such as:
19762 prog.o: No such file or directory.
19765 When this happens, add the appropriate directory to the search path with
19766 the @value{GDBN} command @code{path}, and execute the @code{target}
19769 @node VxWorks Download
19770 @subsubsection VxWorks Download
19772 @cindex download to VxWorks
19773 If you have connected to the VxWorks target and you want to debug an
19774 object that has not yet been loaded, you can use the @value{GDBN}
19775 @code{load} command to download a file from Unix to VxWorks
19776 incrementally. The object file given as an argument to the @code{load}
19777 command is actually opened twice: first by the VxWorks target in order
19778 to download the code, then by @value{GDBN} in order to read the symbol
19779 table. This can lead to problems if the current working directories on
19780 the two systems differ. If both systems have NFS mounted the same
19781 filesystems, you can avoid these problems by using absolute paths.
19782 Otherwise, it is simplest to set the working directory on both systems
19783 to the directory in which the object file resides, and then to reference
19784 the file by its name, without any path. For instance, a program
19785 @file{prog.o} may reside in @file{@var{vxpath}/vw/demo/rdb} in VxWorks
19786 and in @file{@var{hostpath}/vw/demo/rdb} on the host. To load this
19787 program, type this on VxWorks:
19790 -> cd "@var{vxpath}/vw/demo/rdb"
19794 Then, in @value{GDBN}, type:
19797 (vxgdb) cd @var{hostpath}/vw/demo/rdb
19798 (vxgdb) load prog.o
19801 @value{GDBN} displays a response similar to this:
19804 Reading symbol data from wherever/vw/demo/rdb/prog.o... done.
19807 You can also use the @code{load} command to reload an object module
19808 after editing and recompiling the corresponding source file. Note that
19809 this makes @value{GDBN} delete all currently-defined breakpoints,
19810 auto-displays, and convenience variables, and to clear the value
19811 history. (This is necessary in order to preserve the integrity of
19812 debugger's data structures that reference the target system's symbol
19815 @node VxWorks Attach
19816 @subsubsection Running Tasks
19818 @cindex running VxWorks tasks
19819 You can also attach to an existing task using the @code{attach} command as
19823 (vxgdb) attach @var{task}
19827 where @var{task} is the VxWorks hexadecimal task ID. The task can be running
19828 or suspended when you attach to it. Running tasks are suspended at
19829 the time of attachment.
19831 @node Embedded Processors
19832 @section Embedded Processors
19834 This section goes into details specific to particular embedded
19837 @cindex send command to simulator
19838 Whenever a specific embedded processor has a simulator, @value{GDBN}
19839 allows to send an arbitrary command to the simulator.
19842 @item sim @var{command}
19843 @kindex sim@r{, a command}
19844 Send an arbitrary @var{command} string to the simulator. Consult the
19845 documentation for the specific simulator in use for information about
19846 acceptable commands.
19852 * M32R/D:: Renesas M32R/D
19853 * M68K:: Motorola M68K
19854 * MicroBlaze:: Xilinx MicroBlaze
19855 * MIPS Embedded:: MIPS Embedded
19856 * OpenRISC 1000:: OpenRisc 1000
19857 * PowerPC Embedded:: PowerPC Embedded
19858 * PA:: HP PA Embedded
19859 * Sparclet:: Tsqware Sparclet
19860 * Sparclite:: Fujitsu Sparclite
19861 * Z8000:: Zilog Z8000
19864 * Super-H:: Renesas Super-H
19873 @item target rdi @var{dev}
19874 ARM Angel monitor, via RDI library interface to ADP protocol. You may
19875 use this target to communicate with both boards running the Angel
19876 monitor, or with the EmbeddedICE JTAG debug device.
19879 @item target rdp @var{dev}
19884 @value{GDBN} provides the following ARM-specific commands:
19887 @item set arm disassembler
19889 This commands selects from a list of disassembly styles. The
19890 @code{"std"} style is the standard style.
19892 @item show arm disassembler
19894 Show the current disassembly style.
19896 @item set arm apcs32
19897 @cindex ARM 32-bit mode
19898 This command toggles ARM operation mode between 32-bit and 26-bit.
19900 @item show arm apcs32
19901 Display the current usage of the ARM 32-bit mode.
19903 @item set arm fpu @var{fputype}
19904 This command sets the ARM floating-point unit (FPU) type. The
19905 argument @var{fputype} can be one of these:
19909 Determine the FPU type by querying the OS ABI.
19911 Software FPU, with mixed-endian doubles on little-endian ARM
19914 GCC-compiled FPA co-processor.
19916 Software FPU with pure-endian doubles.
19922 Show the current type of the FPU.
19925 This command forces @value{GDBN} to use the specified ABI.
19928 Show the currently used ABI.
19930 @item set arm fallback-mode (arm|thumb|auto)
19931 @value{GDBN} uses the symbol table, when available, to determine
19932 whether instructions are ARM or Thumb. This command controls
19933 @value{GDBN}'s default behavior when the symbol table is not
19934 available. The default is @samp{auto}, which causes @value{GDBN} to
19935 use the current execution mode (from the @code{T} bit in the @code{CPSR}
19938 @item show arm fallback-mode
19939 Show the current fallback instruction mode.
19941 @item set arm force-mode (arm|thumb|auto)
19942 This command overrides use of the symbol table to determine whether
19943 instructions are ARM or Thumb. The default is @samp{auto}, which
19944 causes @value{GDBN} to use the symbol table and then the setting
19945 of @samp{set arm fallback-mode}.
19947 @item show arm force-mode
19948 Show the current forced instruction mode.
19950 @item set debug arm
19951 Toggle whether to display ARM-specific debugging messages from the ARM
19952 target support subsystem.
19954 @item show debug arm
19955 Show whether ARM-specific debugging messages are enabled.
19958 The following commands are available when an ARM target is debugged
19959 using the RDI interface:
19962 @item rdilogfile @r{[}@var{file}@r{]}
19964 @cindex ADP (Angel Debugger Protocol) logging
19965 Set the filename for the ADP (Angel Debugger Protocol) packet log.
19966 With an argument, sets the log file to the specified @var{file}. With
19967 no argument, show the current log file name. The default log file is
19970 @item rdilogenable @r{[}@var{arg}@r{]}
19971 @kindex rdilogenable
19972 Control logging of ADP packets. With an argument of 1 or @code{"yes"}
19973 enables logging, with an argument 0 or @code{"no"} disables it. With
19974 no arguments displays the current setting. When logging is enabled,
19975 ADP packets exchanged between @value{GDBN} and the RDI target device
19976 are logged to a file.
19978 @item set rdiromatzero
19979 @kindex set rdiromatzero
19980 @cindex ROM at zero address, RDI
19981 Tell @value{GDBN} whether the target has ROM at address 0. If on,
19982 vector catching is disabled, so that zero address can be used. If off
19983 (the default), vector catching is enabled. For this command to take
19984 effect, it needs to be invoked prior to the @code{target rdi} command.
19986 @item show rdiromatzero
19987 @kindex show rdiromatzero
19988 Show the current setting of ROM at zero address.
19990 @item set rdiheartbeat
19991 @kindex set rdiheartbeat
19992 @cindex RDI heartbeat
19993 Enable or disable RDI heartbeat packets. It is not recommended to
19994 turn on this option, since it confuses ARM and EPI JTAG interface, as
19995 well as the Angel monitor.
19997 @item show rdiheartbeat
19998 @kindex show rdiheartbeat
19999 Show the setting of RDI heartbeat packets.
20003 @item target sim @r{[}@var{simargs}@r{]} @dots{}
20004 The @value{GDBN} ARM simulator accepts the following optional arguments.
20007 @item --swi-support=@var{type}
20008 Tell the simulator which SWI interfaces to support.
20009 @var{type} may be a comma separated list of the following values.
20010 The default value is @code{all}.
20023 @subsection Renesas M32R/D and M32R/SDI
20026 @kindex target m32r
20027 @item target m32r @var{dev}
20028 Renesas M32R/D ROM monitor.
20030 @kindex target m32rsdi
20031 @item target m32rsdi @var{dev}
20032 Renesas M32R SDI server, connected via parallel port to the board.
20035 The following @value{GDBN} commands are specific to the M32R monitor:
20038 @item set download-path @var{path}
20039 @kindex set download-path
20040 @cindex find downloadable @sc{srec} files (M32R)
20041 Set the default path for finding downloadable @sc{srec} files.
20043 @item show download-path
20044 @kindex show download-path
20045 Show the default path for downloadable @sc{srec} files.
20047 @item set board-address @var{addr}
20048 @kindex set board-address
20049 @cindex M32-EVA target board address
20050 Set the IP address for the M32R-EVA target board.
20052 @item show board-address
20053 @kindex show board-address
20054 Show the current IP address of the target board.
20056 @item set server-address @var{addr}
20057 @kindex set server-address
20058 @cindex download server address (M32R)
20059 Set the IP address for the download server, which is the @value{GDBN}'s
20062 @item show server-address
20063 @kindex show server-address
20064 Display the IP address of the download server.
20066 @item upload @r{[}@var{file}@r{]}
20067 @kindex upload@r{, M32R}
20068 Upload the specified @sc{srec} @var{file} via the monitor's Ethernet
20069 upload capability. If no @var{file} argument is given, the current
20070 executable file is uploaded.
20072 @item tload @r{[}@var{file}@r{]}
20073 @kindex tload@r{, M32R}
20074 Test the @code{upload} command.
20077 The following commands are available for M32R/SDI:
20082 @cindex reset SDI connection, M32R
20083 This command resets the SDI connection.
20087 This command shows the SDI connection status.
20090 @kindex debug_chaos
20091 @cindex M32R/Chaos debugging
20092 Instructs the remote that M32R/Chaos debugging is to be used.
20094 @item use_debug_dma
20095 @kindex use_debug_dma
20096 Instructs the remote to use the DEBUG_DMA method of accessing memory.
20099 @kindex use_mon_code
20100 Instructs the remote to use the MON_CODE method of accessing memory.
20103 @kindex use_ib_break
20104 Instructs the remote to set breakpoints by IB break.
20106 @item use_dbt_break
20107 @kindex use_dbt_break
20108 Instructs the remote to set breakpoints by DBT.
20114 The Motorola m68k configuration includes ColdFire support, and a
20115 target command for the following ROM monitor.
20119 @kindex target dbug
20120 @item target dbug @var{dev}
20121 dBUG ROM monitor for Motorola ColdFire.
20126 @subsection MicroBlaze
20127 @cindex Xilinx MicroBlaze
20128 @cindex XMD, Xilinx Microprocessor Debugger
20130 The MicroBlaze is a soft-core processor supported on various Xilinx
20131 FPGAs, such as Spartan or Virtex series. Boards with these processors
20132 usually have JTAG ports which connect to a host system running the Xilinx
20133 Embedded Development Kit (EDK) or Software Development Kit (SDK).
20134 This host system is used to download the configuration bitstream to
20135 the target FPGA. The Xilinx Microprocessor Debugger (XMD) program
20136 communicates with the target board using the JTAG interface and
20137 presents a @code{gdbserver} interface to the board. By default
20138 @code{xmd} uses port @code{1234}. (While it is possible to change
20139 this default port, it requires the use of undocumented @code{xmd}
20140 commands. Contact Xilinx support if you need to do this.)
20142 Use these GDB commands to connect to the MicroBlaze target processor.
20145 @item target remote :1234
20146 Use this command to connect to the target if you are running @value{GDBN}
20147 on the same system as @code{xmd}.
20149 @item target remote @var{xmd-host}:1234
20150 Use this command to connect to the target if it is connected to @code{xmd}
20151 running on a different system named @var{xmd-host}.
20154 Use this command to download a program to the MicroBlaze target.
20156 @item set debug microblaze @var{n}
20157 Enable MicroBlaze-specific debugging messages if non-zero.
20159 @item show debug microblaze @var{n}
20160 Show MicroBlaze-specific debugging level.
20163 @node MIPS Embedded
20164 @subsection @acronym{MIPS} Embedded
20166 @cindex @acronym{MIPS} boards
20167 @value{GDBN} can use the @acronym{MIPS} remote debugging protocol to talk to a
20168 @acronym{MIPS} board attached to a serial line. This is available when
20169 you configure @value{GDBN} with @samp{--target=mips-elf}.
20172 Use these @value{GDBN} commands to specify the connection to your target board:
20175 @item target mips @var{port}
20176 @kindex target mips @var{port}
20177 To run a program on the board, start up @code{@value{GDBP}} with the
20178 name of your program as the argument. To connect to the board, use the
20179 command @samp{target mips @var{port}}, where @var{port} is the name of
20180 the serial port connected to the board. If the program has not already
20181 been downloaded to the board, you may use the @code{load} command to
20182 download it. You can then use all the usual @value{GDBN} commands.
20184 For example, this sequence connects to the target board through a serial
20185 port, and loads and runs a program called @var{prog} through the
20189 host$ @value{GDBP} @var{prog}
20190 @value{GDBN} is free software and @dots{}
20191 (@value{GDBP}) target mips /dev/ttyb
20192 (@value{GDBP}) load @var{prog}
20196 @item target mips @var{hostname}:@var{portnumber}
20197 On some @value{GDBN} host configurations, you can specify a TCP
20198 connection (for instance, to a serial line managed by a terminal
20199 concentrator) instead of a serial port, using the syntax
20200 @samp{@var{hostname}:@var{portnumber}}.
20202 @item target pmon @var{port}
20203 @kindex target pmon @var{port}
20206 @item target ddb @var{port}
20207 @kindex target ddb @var{port}
20208 NEC's DDB variant of PMON for Vr4300.
20210 @item target lsi @var{port}
20211 @kindex target lsi @var{port}
20212 LSI variant of PMON.
20214 @kindex target r3900
20215 @item target r3900 @var{dev}
20216 Densan DVE-R3900 ROM monitor for Toshiba R3900 Mips.
20218 @kindex target array
20219 @item target array @var{dev}
20220 Array Tech LSI33K RAID controller board.
20226 @value{GDBN} also supports these special commands for @acronym{MIPS} targets:
20229 @item set mipsfpu double
20230 @itemx set mipsfpu single
20231 @itemx set mipsfpu none
20232 @itemx set mipsfpu auto
20233 @itemx show mipsfpu
20234 @kindex set mipsfpu
20235 @kindex show mipsfpu
20236 @cindex @acronym{MIPS} remote floating point
20237 @cindex floating point, @acronym{MIPS} remote
20238 If your target board does not support the @acronym{MIPS} floating point
20239 coprocessor, you should use the command @samp{set mipsfpu none} (if you
20240 need this, you may wish to put the command in your @value{GDBN} init
20241 file). This tells @value{GDBN} how to find the return value of
20242 functions which return floating point values. It also allows
20243 @value{GDBN} to avoid saving the floating point registers when calling
20244 functions on the board. If you are using a floating point coprocessor
20245 with only single precision floating point support, as on the @sc{r4650}
20246 processor, use the command @samp{set mipsfpu single}. The default
20247 double precision floating point coprocessor may be selected using
20248 @samp{set mipsfpu double}.
20250 In previous versions the only choices were double precision or no
20251 floating point, so @samp{set mipsfpu on} will select double precision
20252 and @samp{set mipsfpu off} will select no floating point.
20254 As usual, you can inquire about the @code{mipsfpu} variable with
20255 @samp{show mipsfpu}.
20257 @item set timeout @var{seconds}
20258 @itemx set retransmit-timeout @var{seconds}
20259 @itemx show timeout
20260 @itemx show retransmit-timeout
20261 @cindex @code{timeout}, @acronym{MIPS} protocol
20262 @cindex @code{retransmit-timeout}, @acronym{MIPS} protocol
20263 @kindex set timeout
20264 @kindex show timeout
20265 @kindex set retransmit-timeout
20266 @kindex show retransmit-timeout
20267 You can control the timeout used while waiting for a packet, in the @acronym{MIPS}
20268 remote protocol, with the @code{set timeout @var{seconds}} command. The
20269 default is 5 seconds. Similarly, you can control the timeout used while
20270 waiting for an acknowledgment of a packet with the @code{set
20271 retransmit-timeout @var{seconds}} command. The default is 3 seconds.
20272 You can inspect both values with @code{show timeout} and @code{show
20273 retransmit-timeout}. (These commands are @emph{only} available when
20274 @value{GDBN} is configured for @samp{--target=mips-elf}.)
20276 The timeout set by @code{set timeout} does not apply when @value{GDBN}
20277 is waiting for your program to stop. In that case, @value{GDBN} waits
20278 forever because it has no way of knowing how long the program is going
20279 to run before stopping.
20281 @item set syn-garbage-limit @var{num}
20282 @kindex set syn-garbage-limit@r{, @acronym{MIPS} remote}
20283 @cindex synchronize with remote @acronym{MIPS} target
20284 Limit the maximum number of characters @value{GDBN} should ignore when
20285 it tries to synchronize with the remote target. The default is 10
20286 characters. Setting the limit to -1 means there's no limit.
20288 @item show syn-garbage-limit
20289 @kindex show syn-garbage-limit@r{, @acronym{MIPS} remote}
20290 Show the current limit on the number of characters to ignore when
20291 trying to synchronize with the remote system.
20293 @item set monitor-prompt @var{prompt}
20294 @kindex set monitor-prompt@r{, @acronym{MIPS} remote}
20295 @cindex remote monitor prompt
20296 Tell @value{GDBN} to expect the specified @var{prompt} string from the
20297 remote monitor. The default depends on the target:
20307 @item show monitor-prompt
20308 @kindex show monitor-prompt@r{, @acronym{MIPS} remote}
20309 Show the current strings @value{GDBN} expects as the prompt from the
20312 @item set monitor-warnings
20313 @kindex set monitor-warnings@r{, @acronym{MIPS} remote}
20314 Enable or disable monitor warnings about hardware breakpoints. This
20315 has effect only for the @code{lsi} target. When on, @value{GDBN} will
20316 display warning messages whose codes are returned by the @code{lsi}
20317 PMON monitor for breakpoint commands.
20319 @item show monitor-warnings
20320 @kindex show monitor-warnings@r{, @acronym{MIPS} remote}
20321 Show the current setting of printing monitor warnings.
20323 @item pmon @var{command}
20324 @kindex pmon@r{, @acronym{MIPS} remote}
20325 @cindex send PMON command
20326 This command allows sending an arbitrary @var{command} string to the
20327 monitor. The monitor must be in debug mode for this to work.
20330 @node OpenRISC 1000
20331 @subsection OpenRISC 1000
20332 @cindex OpenRISC 1000
20334 @cindex or1k boards
20335 See OR1k Architecture document (@uref{www.opencores.org}) for more information
20336 about platform and commands.
20340 @kindex target jtag
20341 @item target jtag jtag://@var{host}:@var{port}
20343 Connects to remote JTAG server.
20344 JTAG remote server can be either an or1ksim or JTAG server,
20345 connected via parallel port to the board.
20347 Example: @code{target jtag jtag://localhost:9999}
20350 @item or1ksim @var{command}
20351 If connected to @code{or1ksim} OpenRISC 1000 Architectural
20352 Simulator, proprietary commands can be executed.
20354 @kindex info or1k spr
20355 @item info or1k spr
20356 Displays spr groups.
20358 @item info or1k spr @var{group}
20359 @itemx info or1k spr @var{groupno}
20360 Displays register names in selected group.
20362 @item info or1k spr @var{group} @var{register}
20363 @itemx info or1k spr @var{register}
20364 @itemx info or1k spr @var{groupno} @var{registerno}
20365 @itemx info or1k spr @var{registerno}
20366 Shows information about specified spr register.
20369 @item spr @var{group} @var{register} @var{value}
20370 @itemx spr @var{register @var{value}}
20371 @itemx spr @var{groupno} @var{registerno @var{value}}
20372 @itemx spr @var{registerno @var{value}}
20373 Writes @var{value} to specified spr register.
20376 Some implementations of OpenRISC 1000 Architecture also have hardware trace.
20377 It is very similar to @value{GDBN} trace, except it does not interfere with normal
20378 program execution and is thus much faster. Hardware breakpoints/watchpoint
20379 triggers can be set using:
20382 Load effective address/data
20384 Store effective address/data
20386 Access effective address ($SEA or $LEA) or data ($SDATA/$LDATA)
20391 When triggered, it can capture low level data, like: @code{PC}, @code{LSEA},
20392 @code{LDATA}, @code{SDATA}, @code{READSPR}, @code{WRITESPR}, @code{INSTR}.
20394 @code{htrace} commands:
20395 @cindex OpenRISC 1000 htrace
20398 @item hwatch @var{conditional}
20399 Set hardware watchpoint on combination of Load/Store Effective Address(es)
20400 or Data. For example:
20402 @code{hwatch ($LEA == my_var) && ($LDATA < 50) || ($SEA == my_var) && ($SDATA >= 50)}
20404 @code{hwatch ($LEA == my_var) && ($LDATA < 50) || ($SEA == my_var) && ($SDATA >= 50)}
20408 Display information about current HW trace configuration.
20410 @item htrace trigger @var{conditional}
20411 Set starting criteria for HW trace.
20413 @item htrace qualifier @var{conditional}
20414 Set acquisition qualifier for HW trace.
20416 @item htrace stop @var{conditional}
20417 Set HW trace stopping criteria.
20419 @item htrace record [@var{data}]*
20420 Selects the data to be recorded, when qualifier is met and HW trace was
20423 @item htrace enable
20424 @itemx htrace disable
20425 Enables/disables the HW trace.
20427 @item htrace rewind [@var{filename}]
20428 Clears currently recorded trace data.
20430 If filename is specified, new trace file is made and any newly collected data
20431 will be written there.
20433 @item htrace print [@var{start} [@var{len}]]
20434 Prints trace buffer, using current record configuration.
20436 @item htrace mode continuous
20437 Set continuous trace mode.
20439 @item htrace mode suspend
20440 Set suspend trace mode.
20444 @node PowerPC Embedded
20445 @subsection PowerPC Embedded
20447 @cindex DVC register
20448 @value{GDBN} supports using the DVC (Data Value Compare) register to
20449 implement in hardware simple hardware watchpoint conditions of the form:
20452 (@value{GDBP}) watch @var{ADDRESS|VARIABLE} \
20453 if @var{ADDRESS|VARIABLE} == @var{CONSTANT EXPRESSION}
20456 The DVC register will be automatically used when @value{GDBN} detects
20457 such pattern in a condition expression, and the created watchpoint uses one
20458 debug register (either the @code{exact-watchpoints} option is on and the
20459 variable is scalar, or the variable has a length of one byte). This feature
20460 is available in native @value{GDBN} running on a Linux kernel version 2.6.34
20463 When running on PowerPC embedded processors, @value{GDBN} automatically uses
20464 ranged hardware watchpoints, unless the @code{exact-watchpoints} option is on,
20465 in which case watchpoints using only one debug register are created when
20466 watching variables of scalar types.
20468 You can create an artificial array to watch an arbitrary memory
20469 region using one of the following commands (@pxref{Expressions}):
20472 (@value{GDBP}) watch *((char *) @var{address})@@@var{length}
20473 (@value{GDBP}) watch @{char[@var{length}]@} @var{address}
20476 PowerPC embedded processors support masked watchpoints. See the discussion
20477 about the @code{mask} argument in @ref{Set Watchpoints}.
20479 @cindex ranged breakpoint
20480 PowerPC embedded processors support hardware accelerated
20481 @dfn{ranged breakpoints}. A ranged breakpoint stops execution of
20482 the inferior whenever it executes an instruction at any address within
20483 the range it specifies. To set a ranged breakpoint in @value{GDBN},
20484 use the @code{break-range} command.
20486 @value{GDBN} provides the following PowerPC-specific commands:
20489 @kindex break-range
20490 @item break-range @var{start-location}, @var{end-location}
20491 Set a breakpoint for an address range.
20492 @var{start-location} and @var{end-location} can specify a function name,
20493 a line number, an offset of lines from the current line or from the start
20494 location, or an address of an instruction (see @ref{Specify Location},
20495 for a list of all the possible ways to specify a @var{location}.)
20496 The breakpoint will stop execution of the inferior whenever it
20497 executes an instruction at any address within the specified range,
20498 (including @var{start-location} and @var{end-location}.)
20500 @kindex set powerpc
20501 @item set powerpc soft-float
20502 @itemx show powerpc soft-float
20503 Force @value{GDBN} to use (or not use) a software floating point calling
20504 convention. By default, @value{GDBN} selects the calling convention based
20505 on the selected architecture and the provided executable file.
20507 @item set powerpc vector-abi
20508 @itemx show powerpc vector-abi
20509 Force @value{GDBN} to use the specified calling convention for vector
20510 arguments and return values. The valid options are @samp{auto};
20511 @samp{generic}, to avoid vector registers even if they are present;
20512 @samp{altivec}, to use AltiVec registers; and @samp{spe} to use SPE
20513 registers. By default, @value{GDBN} selects the calling convention
20514 based on the selected architecture and the provided executable file.
20516 @item set powerpc exact-watchpoints
20517 @itemx show powerpc exact-watchpoints
20518 Allow @value{GDBN} to use only one debug register when watching a variable
20519 of scalar type, thus assuming that the variable is accessed through the
20520 address of its first byte.
20522 @kindex target dink32
20523 @item target dink32 @var{dev}
20524 DINK32 ROM monitor.
20526 @kindex target ppcbug
20527 @item target ppcbug @var{dev}
20528 @kindex target ppcbug1
20529 @item target ppcbug1 @var{dev}
20530 PPCBUG ROM monitor for PowerPC.
20533 @item target sds @var{dev}
20534 SDS monitor, running on a PowerPC board (such as Motorola's ADS).
20537 @cindex SDS protocol
20538 The following commands specific to the SDS protocol are supported
20542 @item set sdstimeout @var{nsec}
20543 @kindex set sdstimeout
20544 Set the timeout for SDS protocol reads to be @var{nsec} seconds. The
20545 default is 2 seconds.
20547 @item show sdstimeout
20548 @kindex show sdstimeout
20549 Show the current value of the SDS timeout.
20551 @item sds @var{command}
20552 @kindex sds@r{, a command}
20553 Send the specified @var{command} string to the SDS monitor.
20558 @subsection HP PA Embedded
20562 @kindex target op50n
20563 @item target op50n @var{dev}
20564 OP50N monitor, running on an OKI HPPA board.
20566 @kindex target w89k
20567 @item target w89k @var{dev}
20568 W89K monitor, running on a Winbond HPPA board.
20573 @subsection Tsqware Sparclet
20577 @value{GDBN} enables developers to debug tasks running on
20578 Sparclet targets from a Unix host.
20579 @value{GDBN} uses code that runs on
20580 both the Unix host and on the Sparclet target. The program
20581 @code{@value{GDBP}} is installed and executed on the Unix host.
20584 @item remotetimeout @var{args}
20585 @kindex remotetimeout
20586 @value{GDBN} supports the option @code{remotetimeout}.
20587 This option is set by the user, and @var{args} represents the number of
20588 seconds @value{GDBN} waits for responses.
20591 @cindex compiling, on Sparclet
20592 When compiling for debugging, include the options @samp{-g} to get debug
20593 information and @samp{-Ttext} to relocate the program to where you wish to
20594 load it on the target. You may also want to add the options @samp{-n} or
20595 @samp{-N} in order to reduce the size of the sections. Example:
20598 sparclet-aout-gcc prog.c -Ttext 0x12010000 -g -o prog -N
20601 You can use @code{objdump} to verify that the addresses are what you intended:
20604 sparclet-aout-objdump --headers --syms prog
20607 @cindex running, on Sparclet
20609 your Unix execution search path to find @value{GDBN}, you are ready to
20610 run @value{GDBN}. From your Unix host, run @code{@value{GDBP}}
20611 (or @code{sparclet-aout-gdb}, depending on your installation).
20613 @value{GDBN} comes up showing the prompt:
20620 * Sparclet File:: Setting the file to debug
20621 * Sparclet Connection:: Connecting to Sparclet
20622 * Sparclet Download:: Sparclet download
20623 * Sparclet Execution:: Running and debugging
20626 @node Sparclet File
20627 @subsubsection Setting File to Debug
20629 The @value{GDBN} command @code{file} lets you choose with program to debug.
20632 (gdbslet) file prog
20636 @value{GDBN} then attempts to read the symbol table of @file{prog}.
20637 @value{GDBN} locates
20638 the file by searching the directories listed in the command search
20640 If the file was compiled with debug information (option @samp{-g}), source
20641 files will be searched as well.
20642 @value{GDBN} locates
20643 the source files by searching the directories listed in the directory search
20644 path (@pxref{Environment, ,Your Program's Environment}).
20646 to find a file, it displays a message such as:
20649 prog: No such file or directory.
20652 When this happens, add the appropriate directories to the search paths with
20653 the @value{GDBN} commands @code{path} and @code{dir}, and execute the
20654 @code{target} command again.
20656 @node Sparclet Connection
20657 @subsubsection Connecting to Sparclet
20659 The @value{GDBN} command @code{target} lets you connect to a Sparclet target.
20660 To connect to a target on serial port ``@code{ttya}'', type:
20663 (gdbslet) target sparclet /dev/ttya
20664 Remote target sparclet connected to /dev/ttya
20665 main () at ../prog.c:3
20669 @value{GDBN} displays messages like these:
20675 @node Sparclet Download
20676 @subsubsection Sparclet Download
20678 @cindex download to Sparclet
20679 Once connected to the Sparclet target,
20680 you can use the @value{GDBN}
20681 @code{load} command to download the file from the host to the target.
20682 The file name and load offset should be given as arguments to the @code{load}
20684 Since the file format is aout, the program must be loaded to the starting
20685 address. You can use @code{objdump} to find out what this value is. The load
20686 offset is an offset which is added to the VMA (virtual memory address)
20687 of each of the file's sections.
20688 For instance, if the program
20689 @file{prog} was linked to text address 0x1201000, with data at 0x12010160
20690 and bss at 0x12010170, in @value{GDBN}, type:
20693 (gdbslet) load prog 0x12010000
20694 Loading section .text, size 0xdb0 vma 0x12010000
20697 If the code is loaded at a different address then what the program was linked
20698 to, you may need to use the @code{section} and @code{add-symbol-file} commands
20699 to tell @value{GDBN} where to map the symbol table.
20701 @node Sparclet Execution
20702 @subsubsection Running and Debugging
20704 @cindex running and debugging Sparclet programs
20705 You can now begin debugging the task using @value{GDBN}'s execution control
20706 commands, @code{b}, @code{step}, @code{run}, etc. See the @value{GDBN}
20707 manual for the list of commands.
20711 Breakpoint 1 at 0x12010000: file prog.c, line 3.
20713 Starting program: prog
20714 Breakpoint 1, main (argc=1, argv=0xeffff21c) at prog.c:3
20715 3 char *symarg = 0;
20717 4 char *execarg = "hello!";
20722 @subsection Fujitsu Sparclite
20726 @kindex target sparclite
20727 @item target sparclite @var{dev}
20728 Fujitsu sparclite boards, used only for the purpose of loading.
20729 You must use an additional command to debug the program.
20730 For example: target remote @var{dev} using @value{GDBN} standard
20736 @subsection Zilog Z8000
20739 @cindex simulator, Z8000
20740 @cindex Zilog Z8000 simulator
20742 When configured for debugging Zilog Z8000 targets, @value{GDBN} includes
20745 For the Z8000 family, @samp{target sim} simulates either the Z8002 (the
20746 unsegmented variant of the Z8000 architecture) or the Z8001 (the
20747 segmented variant). The simulator recognizes which architecture is
20748 appropriate by inspecting the object code.
20751 @item target sim @var{args}
20753 @kindex target sim@r{, with Z8000}
20754 Debug programs on a simulated CPU. If the simulator supports setup
20755 options, specify them via @var{args}.
20759 After specifying this target, you can debug programs for the simulated
20760 CPU in the same style as programs for your host computer; use the
20761 @code{file} command to load a new program image, the @code{run} command
20762 to run your program, and so on.
20764 As well as making available all the usual machine registers
20765 (@pxref{Registers, ,Registers}), the Z8000 simulator provides three
20766 additional items of information as specially named registers:
20771 Counts clock-ticks in the simulator.
20774 Counts instructions run in the simulator.
20777 Execution time in 60ths of a second.
20781 You can refer to these values in @value{GDBN} expressions with the usual
20782 conventions; for example, @w{@samp{b fputc if $cycles>5000}} sets a
20783 conditional breakpoint that suspends only after at least 5000
20784 simulated clock ticks.
20787 @subsection Atmel AVR
20790 When configured for debugging the Atmel AVR, @value{GDBN} supports the
20791 following AVR-specific commands:
20794 @item info io_registers
20795 @kindex info io_registers@r{, AVR}
20796 @cindex I/O registers (Atmel AVR)
20797 This command displays information about the AVR I/O registers. For
20798 each register, @value{GDBN} prints its number and value.
20805 When configured for debugging CRIS, @value{GDBN} provides the
20806 following CRIS-specific commands:
20809 @item set cris-version @var{ver}
20810 @cindex CRIS version
20811 Set the current CRIS version to @var{ver}, either @samp{10} or @samp{32}.
20812 The CRIS version affects register names and sizes. This command is useful in
20813 case autodetection of the CRIS version fails.
20815 @item show cris-version
20816 Show the current CRIS version.
20818 @item set cris-dwarf2-cfi
20819 @cindex DWARF-2 CFI and CRIS
20820 Set the usage of DWARF-2 CFI for CRIS debugging. The default is @samp{on}.
20821 Change to @samp{off} when using @code{gcc-cris} whose version is below
20824 @item show cris-dwarf2-cfi
20825 Show the current state of using DWARF-2 CFI.
20827 @item set cris-mode @var{mode}
20829 Set the current CRIS mode to @var{mode}. It should only be changed when
20830 debugging in guru mode, in which case it should be set to
20831 @samp{guru} (the default is @samp{normal}).
20833 @item show cris-mode
20834 Show the current CRIS mode.
20838 @subsection Renesas Super-H
20841 For the Renesas Super-H processor, @value{GDBN} provides these
20845 @item set sh calling-convention @var{convention}
20846 @kindex set sh calling-convention
20847 Set the calling-convention used when calling functions from @value{GDBN}.
20848 Allowed values are @samp{gcc}, which is the default setting, and @samp{renesas}.
20849 With the @samp{gcc} setting, functions are called using the @value{NGCC} calling
20850 convention. If the DWARF-2 information of the called function specifies
20851 that the function follows the Renesas calling convention, the function
20852 is called using the Renesas calling convention. If the calling convention
20853 is set to @samp{renesas}, the Renesas calling convention is always used,
20854 regardless of the DWARF-2 information. This can be used to override the
20855 default of @samp{gcc} if debug information is missing, or the compiler
20856 does not emit the DWARF-2 calling convention entry for a function.
20858 @item show sh calling-convention
20859 @kindex show sh calling-convention
20860 Show the current calling convention setting.
20865 @node Architectures
20866 @section Architectures
20868 This section describes characteristics of architectures that affect
20869 all uses of @value{GDBN} with the architecture, both native and cross.
20876 * HPPA:: HP PA architecture
20877 * SPU:: Cell Broadband Engine SPU architecture
20882 @subsection AArch64
20883 @cindex AArch64 support
20885 When @value{GDBN} is debugging the AArch64 architecture, it provides the
20886 following special commands:
20889 @item set debug aarch64
20890 @kindex set debug aarch64
20891 This command determines whether AArch64 architecture-specific debugging
20892 messages are to be displayed.
20894 @item show debug aarch64
20895 Show whether AArch64 debugging messages are displayed.
20900 @subsection x86 Architecture-specific Issues
20903 @item set struct-convention @var{mode}
20904 @kindex set struct-convention
20905 @cindex struct return convention
20906 @cindex struct/union returned in registers
20907 Set the convention used by the inferior to return @code{struct}s and
20908 @code{union}s from functions to @var{mode}. Possible values of
20909 @var{mode} are @code{"pcc"}, @code{"reg"}, and @code{"default"} (the
20910 default). @code{"default"} or @code{"pcc"} means that @code{struct}s
20911 are returned on the stack, while @code{"reg"} means that a
20912 @code{struct} or a @code{union} whose size is 1, 2, 4, or 8 bytes will
20913 be returned in a register.
20915 @item show struct-convention
20916 @kindex show struct-convention
20917 Show the current setting of the convention to return @code{struct}s
20924 See the following section.
20927 @subsection @acronym{MIPS}
20929 @cindex stack on Alpha
20930 @cindex stack on @acronym{MIPS}
20931 @cindex Alpha stack
20932 @cindex @acronym{MIPS} stack
20933 Alpha- and @acronym{MIPS}-based computers use an unusual stack frame, which
20934 sometimes requires @value{GDBN} to search backward in the object code to
20935 find the beginning of a function.
20937 @cindex response time, @acronym{MIPS} debugging
20938 To improve response time (especially for embedded applications, where
20939 @value{GDBN} may be restricted to a slow serial line for this search)
20940 you may want to limit the size of this search, using one of these
20944 @cindex @code{heuristic-fence-post} (Alpha, @acronym{MIPS})
20945 @item set heuristic-fence-post @var{limit}
20946 Restrict @value{GDBN} to examining at most @var{limit} bytes in its
20947 search for the beginning of a function. A value of @var{0} (the
20948 default) means there is no limit. However, except for @var{0}, the
20949 larger the limit the more bytes @code{heuristic-fence-post} must search
20950 and therefore the longer it takes to run. You should only need to use
20951 this command when debugging a stripped executable.
20953 @item show heuristic-fence-post
20954 Display the current limit.
20958 These commands are available @emph{only} when @value{GDBN} is configured
20959 for debugging programs on Alpha or @acronym{MIPS} processors.
20961 Several @acronym{MIPS}-specific commands are available when debugging @acronym{MIPS}
20965 @item set mips abi @var{arg}
20966 @kindex set mips abi
20967 @cindex set ABI for @acronym{MIPS}
20968 Tell @value{GDBN} which @acronym{MIPS} ABI is used by the inferior. Possible
20969 values of @var{arg} are:
20973 The default ABI associated with the current binary (this is the
20983 @item show mips abi
20984 @kindex show mips abi
20985 Show the @acronym{MIPS} ABI used by @value{GDBN} to debug the inferior.
20987 @item set mips compression @var{arg}
20988 @kindex set mips compression
20989 @cindex code compression, @acronym{MIPS}
20990 Tell @value{GDBN} which @acronym{MIPS} compressed
20991 @acronym{ISA, Instruction Set Architecture} encoding is used by the
20992 inferior. @value{GDBN} uses this for code disassembly and other
20993 internal interpretation purposes. This setting is only referred to
20994 when no executable has been associated with the debugging session or
20995 the executable does not provide information about the encoding it uses.
20996 Otherwise this setting is automatically updated from information
20997 provided by the executable.
20999 Possible values of @var{arg} are @samp{mips16} and @samp{micromips}.
21000 The default compressed @acronym{ISA} encoding is @samp{mips16}, as
21001 executables containing @acronym{MIPS16} code frequently are not
21002 identified as such.
21004 This setting is ``sticky''; that is, it retains its value across
21005 debugging sessions until reset either explicitly with this command or
21006 implicitly from an executable.
21008 The compiler and/or assembler typically add symbol table annotations to
21009 identify functions compiled for the @acronym{MIPS16} or
21010 @acronym{microMIPS} @acronym{ISA}s. If these function-scope annotations
21011 are present, @value{GDBN} uses them in preference to the global
21012 compressed @acronym{ISA} encoding setting.
21014 @item show mips compression
21015 @kindex show mips compression
21016 Show the @acronym{MIPS} compressed @acronym{ISA} encoding used by
21017 @value{GDBN} to debug the inferior.
21020 @itemx show mipsfpu
21021 @xref{MIPS Embedded, set mipsfpu}.
21023 @item set mips mask-address @var{arg}
21024 @kindex set mips mask-address
21025 @cindex @acronym{MIPS} addresses, masking
21026 This command determines whether the most-significant 32 bits of 64-bit
21027 @acronym{MIPS} addresses are masked off. The argument @var{arg} can be
21028 @samp{on}, @samp{off}, or @samp{auto}. The latter is the default
21029 setting, which lets @value{GDBN} determine the correct value.
21031 @item show mips mask-address
21032 @kindex show mips mask-address
21033 Show whether the upper 32 bits of @acronym{MIPS} addresses are masked off or
21036 @item set remote-mips64-transfers-32bit-regs
21037 @kindex set remote-mips64-transfers-32bit-regs
21038 This command controls compatibility with 64-bit @acronym{MIPS} targets that
21039 transfer data in 32-bit quantities. If you have an old @acronym{MIPS} 64 target
21040 that transfers 32 bits for some registers, like @sc{sr} and @sc{fsr},
21041 and 64 bits for other registers, set this option to @samp{on}.
21043 @item show remote-mips64-transfers-32bit-regs
21044 @kindex show remote-mips64-transfers-32bit-regs
21045 Show the current setting of compatibility with older @acronym{MIPS} 64 targets.
21047 @item set debug mips
21048 @kindex set debug mips
21049 This command turns on and off debugging messages for the @acronym{MIPS}-specific
21050 target code in @value{GDBN}.
21052 @item show debug mips
21053 @kindex show debug mips
21054 Show the current setting of @acronym{MIPS} debugging messages.
21060 @cindex HPPA support
21062 When @value{GDBN} is debugging the HP PA architecture, it provides the
21063 following special commands:
21066 @item set debug hppa
21067 @kindex set debug hppa
21068 This command determines whether HPPA architecture-specific debugging
21069 messages are to be displayed.
21071 @item show debug hppa
21072 Show whether HPPA debugging messages are displayed.
21074 @item maint print unwind @var{address}
21075 @kindex maint print unwind@r{, HPPA}
21076 This command displays the contents of the unwind table entry at the
21077 given @var{address}.
21083 @subsection Cell Broadband Engine SPU architecture
21084 @cindex Cell Broadband Engine
21087 When @value{GDBN} is debugging the Cell Broadband Engine SPU architecture,
21088 it provides the following special commands:
21091 @item info spu event
21093 Display SPU event facility status. Shows current event mask
21094 and pending event status.
21096 @item info spu signal
21097 Display SPU signal notification facility status. Shows pending
21098 signal-control word and signal notification mode of both signal
21099 notification channels.
21101 @item info spu mailbox
21102 Display SPU mailbox facility status. Shows all pending entries,
21103 in order of processing, in each of the SPU Write Outbound,
21104 SPU Write Outbound Interrupt, and SPU Read Inbound mailboxes.
21107 Display MFC DMA status. Shows all pending commands in the MFC
21108 DMA queue. For each entry, opcode, tag, class IDs, effective
21109 and local store addresses and transfer size are shown.
21111 @item info spu proxydma
21112 Display MFC Proxy-DMA status. Shows all pending commands in the MFC
21113 Proxy-DMA queue. For each entry, opcode, tag, class IDs, effective
21114 and local store addresses and transfer size are shown.
21118 When @value{GDBN} is debugging a combined PowerPC/SPU application
21119 on the Cell Broadband Engine, it provides in addition the following
21123 @item set spu stop-on-load @var{arg}
21125 Set whether to stop for new SPE threads. When set to @code{on}, @value{GDBN}
21126 will give control to the user when a new SPE thread enters its @code{main}
21127 function. The default is @code{off}.
21129 @item show spu stop-on-load
21131 Show whether to stop for new SPE threads.
21133 @item set spu auto-flush-cache @var{arg}
21134 Set whether to automatically flush the software-managed cache. When set to
21135 @code{on}, @value{GDBN} will automatically cause the SPE software-managed
21136 cache to be flushed whenever SPE execution stops. This provides a consistent
21137 view of PowerPC memory that is accessed via the cache. If an application
21138 does not use the software-managed cache, this option has no effect.
21140 @item show spu auto-flush-cache
21141 Show whether to automatically flush the software-managed cache.
21146 @subsection PowerPC
21147 @cindex PowerPC architecture
21149 When @value{GDBN} is debugging the PowerPC architecture, it provides a set of
21150 pseudo-registers to enable inspection of 128-bit wide Decimal Floating Point
21151 numbers stored in the floating point registers. These values must be stored
21152 in two consecutive registers, always starting at an even register like
21153 @code{f0} or @code{f2}.
21155 The pseudo-registers go from @code{$dl0} through @code{$dl15}, and are formed
21156 by joining the even/odd register pairs @code{f0} and @code{f1} for @code{$dl0},
21157 @code{f2} and @code{f3} for @code{$dl1} and so on.
21159 For POWER7 processors, @value{GDBN} provides a set of pseudo-registers, the 64-bit
21160 wide Extended Floating Point Registers (@samp{f32} through @samp{f63}).
21163 @node Controlling GDB
21164 @chapter Controlling @value{GDBN}
21166 You can alter the way @value{GDBN} interacts with you by using the
21167 @code{set} command. For commands controlling how @value{GDBN} displays
21168 data, see @ref{Print Settings, ,Print Settings}. Other settings are
21173 * Editing:: Command editing
21174 * Command History:: Command history
21175 * Screen Size:: Screen size
21176 * Numbers:: Numbers
21177 * ABI:: Configuring the current ABI
21178 * Auto-loading:: Automatically loading associated files
21179 * Messages/Warnings:: Optional warnings and messages
21180 * Debugging Output:: Optional messages about internal happenings
21181 * Other Misc Settings:: Other Miscellaneous Settings
21189 @value{GDBN} indicates its readiness to read a command by printing a string
21190 called the @dfn{prompt}. This string is normally @samp{(@value{GDBP})}. You
21191 can change the prompt string with the @code{set prompt} command. For
21192 instance, when debugging @value{GDBN} with @value{GDBN}, it is useful to change
21193 the prompt in one of the @value{GDBN} sessions so that you can always tell
21194 which one you are talking to.
21196 @emph{Note:} @code{set prompt} does not add a space for you after the
21197 prompt you set. This allows you to set a prompt which ends in a space
21198 or a prompt that does not.
21202 @item set prompt @var{newprompt}
21203 Directs @value{GDBN} to use @var{newprompt} as its prompt string henceforth.
21205 @kindex show prompt
21207 Prints a line of the form: @samp{Gdb's prompt is: @var{your-prompt}}
21210 Versions of @value{GDBN} that ship with Python scripting enabled have
21211 prompt extensions. The commands for interacting with these extensions
21215 @kindex set extended-prompt
21216 @item set extended-prompt @var{prompt}
21217 Set an extended prompt that allows for substitutions.
21218 @xref{gdb.prompt}, for a list of escape sequences that can be used for
21219 substitution. Any escape sequences specified as part of the prompt
21220 string are replaced with the corresponding strings each time the prompt
21226 set extended-prompt Current working directory: \w (gdb)
21229 Note that when an extended-prompt is set, it takes control of the
21230 @var{prompt_hook} hook. @xref{prompt_hook}, for further information.
21232 @kindex show extended-prompt
21233 @item show extended-prompt
21234 Prints the extended prompt. Any escape sequences specified as part of
21235 the prompt string with @code{set extended-prompt}, are replaced with the
21236 corresponding strings each time the prompt is displayed.
21240 @section Command Editing
21242 @cindex command line editing
21244 @value{GDBN} reads its input commands via the @dfn{Readline} interface. This
21245 @sc{gnu} library provides consistent behavior for programs which provide a
21246 command line interface to the user. Advantages are @sc{gnu} Emacs-style
21247 or @dfn{vi}-style inline editing of commands, @code{csh}-like history
21248 substitution, and a storage and recall of command history across
21249 debugging sessions.
21251 You may control the behavior of command line editing in @value{GDBN} with the
21252 command @code{set}.
21255 @kindex set editing
21258 @itemx set editing on
21259 Enable command line editing (enabled by default).
21261 @item set editing off
21262 Disable command line editing.
21264 @kindex show editing
21266 Show whether command line editing is enabled.
21269 @ifset SYSTEM_READLINE
21270 @xref{Command Line Editing, , , rluserman, GNU Readline Library},
21272 @ifclear SYSTEM_READLINE
21273 @xref{Command Line Editing},
21275 for more details about the Readline
21276 interface. Users unfamiliar with @sc{gnu} Emacs or @code{vi} are
21277 encouraged to read that chapter.
21279 @node Command History
21280 @section Command History
21281 @cindex command history
21283 @value{GDBN} can keep track of the commands you type during your
21284 debugging sessions, so that you can be certain of precisely what
21285 happened. Use these commands to manage the @value{GDBN} command
21288 @value{GDBN} uses the @sc{gnu} History library, a part of the Readline
21289 package, to provide the history facility.
21290 @ifset SYSTEM_READLINE
21291 @xref{Using History Interactively, , , history, GNU History Library},
21293 @ifclear SYSTEM_READLINE
21294 @xref{Using History Interactively},
21296 for the detailed description of the History library.
21298 To issue a command to @value{GDBN} without affecting certain aspects of
21299 the state which is seen by users, prefix it with @samp{server }
21300 (@pxref{Server Prefix}). This
21301 means that this command will not affect the command history, nor will it
21302 affect @value{GDBN}'s notion of which command to repeat if @key{RET} is
21303 pressed on a line by itself.
21305 @cindex @code{server}, command prefix
21306 The server prefix does not affect the recording of values into the value
21307 history; to print a value without recording it into the value history,
21308 use the @code{output} command instead of the @code{print} command.
21310 Here is the description of @value{GDBN} commands related to command
21314 @cindex history substitution
21315 @cindex history file
21316 @kindex set history filename
21317 @cindex @env{GDBHISTFILE}, environment variable
21318 @item set history filename @var{fname}
21319 Set the name of the @value{GDBN} command history file to @var{fname}.
21320 This is the file where @value{GDBN} reads an initial command history
21321 list, and where it writes the command history from this session when it
21322 exits. You can access this list through history expansion or through
21323 the history command editing characters listed below. This file defaults
21324 to the value of the environment variable @code{GDBHISTFILE}, or to
21325 @file{./.gdb_history} (@file{./_gdb_history} on MS-DOS) if this variable
21328 @cindex save command history
21329 @kindex set history save
21330 @item set history save
21331 @itemx set history save on
21332 Record command history in a file, whose name may be specified with the
21333 @code{set history filename} command. By default, this option is disabled.
21335 @item set history save off
21336 Stop recording command history in a file.
21338 @cindex history size
21339 @kindex set history size
21340 @cindex @env{HISTSIZE}, environment variable
21341 @item set history size @var{size}
21342 Set the number of commands which @value{GDBN} keeps in its history list.
21343 This defaults to the value of the environment variable
21344 @code{HISTSIZE}, or to 256 if this variable is not set.
21347 History expansion assigns special meaning to the character @kbd{!}.
21348 @ifset SYSTEM_READLINE
21349 @xref{Event Designators, , , history, GNU History Library},
21351 @ifclear SYSTEM_READLINE
21352 @xref{Event Designators},
21356 @cindex history expansion, turn on/off
21357 Since @kbd{!} is also the logical not operator in C, history expansion
21358 is off by default. If you decide to enable history expansion with the
21359 @code{set history expansion on} command, you may sometimes need to
21360 follow @kbd{!} (when it is used as logical not, in an expression) with
21361 a space or a tab to prevent it from being expanded. The readline
21362 history facilities do not attempt substitution on the strings
21363 @kbd{!=} and @kbd{!(}, even when history expansion is enabled.
21365 The commands to control history expansion are:
21368 @item set history expansion on
21369 @itemx set history expansion
21370 @kindex set history expansion
21371 Enable history expansion. History expansion is off by default.
21373 @item set history expansion off
21374 Disable history expansion.
21377 @kindex show history
21379 @itemx show history filename
21380 @itemx show history save
21381 @itemx show history size
21382 @itemx show history expansion
21383 These commands display the state of the @value{GDBN} history parameters.
21384 @code{show history} by itself displays all four states.
21389 @kindex show commands
21390 @cindex show last commands
21391 @cindex display command history
21392 @item show commands
21393 Display the last ten commands in the command history.
21395 @item show commands @var{n}
21396 Print ten commands centered on command number @var{n}.
21398 @item show commands +
21399 Print ten commands just after the commands last printed.
21403 @section Screen Size
21404 @cindex size of screen
21405 @cindex pauses in output
21407 Certain commands to @value{GDBN} may produce large amounts of
21408 information output to the screen. To help you read all of it,
21409 @value{GDBN} pauses and asks you for input at the end of each page of
21410 output. Type @key{RET} when you want to continue the output, or @kbd{q}
21411 to discard the remaining output. Also, the screen width setting
21412 determines when to wrap lines of output. Depending on what is being
21413 printed, @value{GDBN} tries to break the line at a readable place,
21414 rather than simply letting it overflow onto the following line.
21416 Normally @value{GDBN} knows the size of the screen from the terminal
21417 driver software. For example, on Unix @value{GDBN} uses the termcap data base
21418 together with the value of the @code{TERM} environment variable and the
21419 @code{stty rows} and @code{stty cols} settings. If this is not correct,
21420 you can override it with the @code{set height} and @code{set
21427 @kindex show height
21428 @item set height @var{lpp}
21430 @itemx set width @var{cpl}
21432 These @code{set} commands specify a screen height of @var{lpp} lines and
21433 a screen width of @var{cpl} characters. The associated @code{show}
21434 commands display the current settings.
21436 If you specify a height of zero lines, @value{GDBN} does not pause during
21437 output no matter how long the output is. This is useful if output is to a
21438 file or to an editor buffer.
21440 Likewise, you can specify @samp{set width 0} to prevent @value{GDBN}
21441 from wrapping its output.
21443 @item set pagination on
21444 @itemx set pagination off
21445 @kindex set pagination
21446 Turn the output pagination on or off; the default is on. Turning
21447 pagination off is the alternative to @code{set height 0}. Note that
21448 running @value{GDBN} with the @option{--batch} option (@pxref{Mode
21449 Options, -batch}) also automatically disables pagination.
21451 @item show pagination
21452 @kindex show pagination
21453 Show the current pagination mode.
21458 @cindex number representation
21459 @cindex entering numbers
21461 You can always enter numbers in octal, decimal, or hexadecimal in
21462 @value{GDBN} by the usual conventions: octal numbers begin with
21463 @samp{0}, decimal numbers end with @samp{.}, and hexadecimal numbers
21464 begin with @samp{0x}. Numbers that neither begin with @samp{0} or
21465 @samp{0x}, nor end with a @samp{.} are, by default, entered in base
21466 10; likewise, the default display for numbers---when no particular
21467 format is specified---is base 10. You can change the default base for
21468 both input and output with the commands described below.
21471 @kindex set input-radix
21472 @item set input-radix @var{base}
21473 Set the default base for numeric input. Supported choices
21474 for @var{base} are decimal 8, 10, or 16. @var{base} must itself be
21475 specified either unambiguously or using the current input radix; for
21479 set input-radix 012
21480 set input-radix 10.
21481 set input-radix 0xa
21485 sets the input base to decimal. On the other hand, @samp{set input-radix 10}
21486 leaves the input radix unchanged, no matter what it was, since
21487 @samp{10}, being without any leading or trailing signs of its base, is
21488 interpreted in the current radix. Thus, if the current radix is 16,
21489 @samp{10} is interpreted in hex, i.e.@: as 16 decimal, which doesn't
21492 @kindex set output-radix
21493 @item set output-radix @var{base}
21494 Set the default base for numeric display. Supported choices
21495 for @var{base} are decimal 8, 10, or 16. @var{base} must itself be
21496 specified either unambiguously or using the current input radix.
21498 @kindex show input-radix
21499 @item show input-radix
21500 Display the current default base for numeric input.
21502 @kindex show output-radix
21503 @item show output-radix
21504 Display the current default base for numeric display.
21506 @item set radix @r{[}@var{base}@r{]}
21510 These commands set and show the default base for both input and output
21511 of numbers. @code{set radix} sets the radix of input and output to
21512 the same base; without an argument, it resets the radix back to its
21513 default value of 10.
21518 @section Configuring the Current ABI
21520 @value{GDBN} can determine the @dfn{ABI} (Application Binary Interface) of your
21521 application automatically. However, sometimes you need to override its
21522 conclusions. Use these commands to manage @value{GDBN}'s view of the
21528 @cindex Newlib OS ABI and its influence on the longjmp handling
21530 One @value{GDBN} configuration can debug binaries for multiple operating
21531 system targets, either via remote debugging or native emulation.
21532 @value{GDBN} will autodetect the @dfn{OS ABI} (Operating System ABI) in use,
21533 but you can override its conclusion using the @code{set osabi} command.
21534 One example where this is useful is in debugging of binaries which use
21535 an alternate C library (e.g.@: @sc{uClibc} for @sc{gnu}/Linux) which does
21536 not have the same identifying marks that the standard C library for your
21539 When @value{GDBN} is debugging the AArch64 architecture, it provides a
21540 ``Newlib'' OS ABI. This is useful for handling @code{setjmp} and
21541 @code{longjmp} when debugging binaries that use the @sc{newlib} C library.
21542 The ``Newlib'' OS ABI can be selected by @code{set osabi Newlib}.
21546 Show the OS ABI currently in use.
21549 With no argument, show the list of registered available OS ABI's.
21551 @item set osabi @var{abi}
21552 Set the current OS ABI to @var{abi}.
21555 @cindex float promotion
21557 Generally, the way that an argument of type @code{float} is passed to a
21558 function depends on whether the function is prototyped. For a prototyped
21559 (i.e.@: ANSI/ISO style) function, @code{float} arguments are passed unchanged,
21560 according to the architecture's convention for @code{float}. For unprototyped
21561 (i.e.@: K&R style) functions, @code{float} arguments are first promoted to type
21562 @code{double} and then passed.
21564 Unfortunately, some forms of debug information do not reliably indicate whether
21565 a function is prototyped. If @value{GDBN} calls a function that is not marked
21566 as prototyped, it consults @kbd{set coerce-float-to-double}.
21569 @kindex set coerce-float-to-double
21570 @item set coerce-float-to-double
21571 @itemx set coerce-float-to-double on
21572 Arguments of type @code{float} will be promoted to @code{double} when passed
21573 to an unprototyped function. This is the default setting.
21575 @item set coerce-float-to-double off
21576 Arguments of type @code{float} will be passed directly to unprototyped
21579 @kindex show coerce-float-to-double
21580 @item show coerce-float-to-double
21581 Show the current setting of promoting @code{float} to @code{double}.
21585 @kindex show cp-abi
21586 @value{GDBN} needs to know the ABI used for your program's C@t{++}
21587 objects. The correct C@t{++} ABI depends on which C@t{++} compiler was
21588 used to build your application. @value{GDBN} only fully supports
21589 programs with a single C@t{++} ABI; if your program contains code using
21590 multiple C@t{++} ABI's or if @value{GDBN} can not identify your
21591 program's ABI correctly, you can tell @value{GDBN} which ABI to use.
21592 Currently supported ABI's include ``gnu-v2'', for @code{g++} versions
21593 before 3.0, ``gnu-v3'', for @code{g++} versions 3.0 and later, and
21594 ``hpaCC'' for the HP ANSI C@t{++} compiler. Other C@t{++} compilers may
21595 use the ``gnu-v2'' or ``gnu-v3'' ABI's as well. The default setting is
21600 Show the C@t{++} ABI currently in use.
21603 With no argument, show the list of supported C@t{++} ABI's.
21605 @item set cp-abi @var{abi}
21606 @itemx set cp-abi auto
21607 Set the current C@t{++} ABI to @var{abi}, or return to automatic detection.
21611 @section Automatically loading associated files
21612 @cindex auto-loading
21614 @value{GDBN} sometimes reads files with commands and settings automatically,
21615 without being explicitly told so by the user. We call this feature
21616 @dfn{auto-loading}. While auto-loading is useful for automatically adapting
21617 @value{GDBN} to the needs of your project, it can sometimes produce unexpected
21618 results or introduce security risks (e.g., if the file comes from untrusted
21621 Note that loading of these associated files (including the local @file{.gdbinit}
21622 file) requires accordingly configured @code{auto-load safe-path}
21623 (@pxref{Auto-loading safe path}).
21625 For these reasons, @value{GDBN} includes commands and options to let you
21626 control when to auto-load files and which files should be auto-loaded.
21629 @anchor{set auto-load off}
21630 @kindex set auto-load off
21631 @item set auto-load off
21632 Globally disable loading of all auto-loaded files.
21633 You may want to use this command with the @samp{-iex} option
21634 (@pxref{Option -init-eval-command}) such as:
21636 $ @kbd{gdb -iex "set auto-load off" untrusted-executable corefile}
21639 Be aware that system init file (@pxref{System-wide configuration})
21640 and init files from your home directory (@pxref{Home Directory Init File})
21641 still get read (as they come from generally trusted directories).
21642 To prevent @value{GDBN} from auto-loading even those init files, use the
21643 @option{-nx} option (@pxref{Mode Options}), in addition to
21644 @code{set auto-load no}.
21646 @anchor{show auto-load}
21647 @kindex show auto-load
21648 @item show auto-load
21649 Show whether auto-loading of each specific @samp{auto-load} file(s) is enabled
21653 (gdb) show auto-load
21654 gdb-scripts: Auto-loading of canned sequences of commands scripts is on.
21655 libthread-db: Auto-loading of inferior specific libthread_db is on.
21656 local-gdbinit: Auto-loading of .gdbinit script from current directory
21658 python-scripts: Auto-loading of Python scripts is on.
21659 safe-path: List of directories from which it is safe to auto-load files
21660 is $debugdir:$datadir/auto-load.
21661 scripts-directory: List of directories from which to load auto-loaded scripts
21662 is $debugdir:$datadir/auto-load.
21665 @anchor{info auto-load}
21666 @kindex info auto-load
21667 @item info auto-load
21668 Print whether each specific @samp{auto-load} file(s) have been auto-loaded or
21672 (gdb) info auto-load
21675 Yes /home/user/gdb/gdb-gdb.gdb
21676 libthread-db: No auto-loaded libthread-db.
21677 local-gdbinit: Local .gdbinit file "/home/user/gdb/.gdbinit" has been
21681 Yes /home/user/gdb/gdb-gdb.py
21685 These are various kinds of files @value{GDBN} can automatically load:
21689 @xref{objfile-gdb.py file}, controlled by @ref{set auto-load python-scripts}.
21691 @xref{objfile-gdb.gdb file}, controlled by @ref{set auto-load gdb-scripts}.
21693 @xref{dotdebug_gdb_scripts section},
21694 controlled by @ref{set auto-load python-scripts}.
21696 @xref{Init File in the Current Directory},
21697 controlled by @ref{set auto-load local-gdbinit}.
21699 @xref{libthread_db.so.1 file}, controlled by @ref{set auto-load libthread-db}.
21702 These are @value{GDBN} control commands for the auto-loading:
21704 @multitable @columnfractions .5 .5
21705 @item @xref{set auto-load off}.
21706 @tab Disable auto-loading globally.
21707 @item @xref{show auto-load}.
21708 @tab Show setting of all kinds of files.
21709 @item @xref{info auto-load}.
21710 @tab Show state of all kinds of files.
21711 @item @xref{set auto-load gdb-scripts}.
21712 @tab Control for @value{GDBN} command scripts.
21713 @item @xref{show auto-load gdb-scripts}.
21714 @tab Show setting of @value{GDBN} command scripts.
21715 @item @xref{info auto-load gdb-scripts}.
21716 @tab Show state of @value{GDBN} command scripts.
21717 @item @xref{set auto-load python-scripts}.
21718 @tab Control for @value{GDBN} Python scripts.
21719 @item @xref{show auto-load python-scripts}.
21720 @tab Show setting of @value{GDBN} Python scripts.
21721 @item @xref{info auto-load python-scripts}.
21722 @tab Show state of @value{GDBN} Python scripts.
21723 @item @xref{set auto-load scripts-directory}.
21724 @tab Control for @value{GDBN} auto-loaded scripts location.
21725 @item @xref{show auto-load scripts-directory}.
21726 @tab Show @value{GDBN} auto-loaded scripts location.
21727 @item @xref{set auto-load local-gdbinit}.
21728 @tab Control for init file in the current directory.
21729 @item @xref{show auto-load local-gdbinit}.
21730 @tab Show setting of init file in the current directory.
21731 @item @xref{info auto-load local-gdbinit}.
21732 @tab Show state of init file in the current directory.
21733 @item @xref{set auto-load libthread-db}.
21734 @tab Control for thread debugging library.
21735 @item @xref{show auto-load libthread-db}.
21736 @tab Show setting of thread debugging library.
21737 @item @xref{info auto-load libthread-db}.
21738 @tab Show state of thread debugging library.
21739 @item @xref{set auto-load safe-path}.
21740 @tab Control directories trusted for automatic loading.
21741 @item @xref{show auto-load safe-path}.
21742 @tab Show directories trusted for automatic loading.
21743 @item @xref{add-auto-load-safe-path}.
21744 @tab Add directory trusted for automatic loading.
21748 * Init File in the Current Directory:: @samp{set/show/info auto-load local-gdbinit}
21749 * libthread_db.so.1 file:: @samp{set/show/info auto-load libthread-db}
21750 * objfile-gdb.gdb file:: @samp{set/show/info auto-load gdb-script}
21751 * Auto-loading safe path:: @samp{set/show/info auto-load safe-path}
21752 * Auto-loading verbose mode:: @samp{set/show debug auto-load}
21753 @xref{Python Auto-loading}.
21756 @node Init File in the Current Directory
21757 @subsection Automatically loading init file in the current directory
21758 @cindex auto-loading init file in the current directory
21760 By default, @value{GDBN} reads and executes the canned sequences of commands
21761 from init file (if any) in the current working directory,
21762 see @ref{Init File in the Current Directory during Startup}.
21764 Note that loading of this local @file{.gdbinit} file also requires accordingly
21765 configured @code{auto-load safe-path} (@pxref{Auto-loading safe path}).
21768 @anchor{set auto-load local-gdbinit}
21769 @kindex set auto-load local-gdbinit
21770 @item set auto-load local-gdbinit [on|off]
21771 Enable or disable the auto-loading of canned sequences of commands
21772 (@pxref{Sequences}) found in init file in the current directory.
21774 @anchor{show auto-load local-gdbinit}
21775 @kindex show auto-load local-gdbinit
21776 @item show auto-load local-gdbinit
21777 Show whether auto-loading of canned sequences of commands from init file in the
21778 current directory is enabled or disabled.
21780 @anchor{info auto-load local-gdbinit}
21781 @kindex info auto-load local-gdbinit
21782 @item info auto-load local-gdbinit
21783 Print whether canned sequences of commands from init file in the
21784 current directory have been auto-loaded.
21787 @node libthread_db.so.1 file
21788 @subsection Automatically loading thread debugging library
21789 @cindex auto-loading libthread_db.so.1
21791 This feature is currently present only on @sc{gnu}/Linux native hosts.
21793 @value{GDBN} reads in some cases thread debugging library from places specific
21794 to the inferior (@pxref{set libthread-db-search-path}).
21796 The special @samp{libthread-db-search-path} entry @samp{$sdir} is processed
21797 without checking this @samp{set auto-load libthread-db} switch as system
21798 libraries have to be trusted in general. In all other cases of
21799 @samp{libthread-db-search-path} entries @value{GDBN} checks first if @samp{set
21800 auto-load libthread-db} is enabled before trying to open such thread debugging
21803 Note that loading of this debugging library also requires accordingly configured
21804 @code{auto-load safe-path} (@pxref{Auto-loading safe path}).
21807 @anchor{set auto-load libthread-db}
21808 @kindex set auto-load libthread-db
21809 @item set auto-load libthread-db [on|off]
21810 Enable or disable the auto-loading of inferior specific thread debugging library.
21812 @anchor{show auto-load libthread-db}
21813 @kindex show auto-load libthread-db
21814 @item show auto-load libthread-db
21815 Show whether auto-loading of inferior specific thread debugging library is
21816 enabled or disabled.
21818 @anchor{info auto-load libthread-db}
21819 @kindex info auto-load libthread-db
21820 @item info auto-load libthread-db
21821 Print the list of all loaded inferior specific thread debugging libraries and
21822 for each such library print list of inferior @var{pid}s using it.
21825 @node objfile-gdb.gdb file
21826 @subsection The @file{@var{objfile}-gdb.gdb} file
21827 @cindex auto-loading @file{@var{objfile}-gdb.gdb}
21829 @value{GDBN} tries to load an @file{@var{objfile}-gdb.gdb} file containing
21830 canned sequences of commands (@pxref{Sequences}), as long as @samp{set
21831 auto-load gdb-scripts} is set to @samp{on}.
21833 Note that loading of this script file also requires accordingly configured
21834 @code{auto-load safe-path} (@pxref{Auto-loading safe path}).
21836 For more background refer to the similar Python scripts auto-loading
21837 description (@pxref{objfile-gdb.py file}).
21840 @anchor{set auto-load gdb-scripts}
21841 @kindex set auto-load gdb-scripts
21842 @item set auto-load gdb-scripts [on|off]
21843 Enable or disable the auto-loading of canned sequences of commands scripts.
21845 @anchor{show auto-load gdb-scripts}
21846 @kindex show auto-load gdb-scripts
21847 @item show auto-load gdb-scripts
21848 Show whether auto-loading of canned sequences of commands scripts is enabled or
21851 @anchor{info auto-load gdb-scripts}
21852 @kindex info auto-load gdb-scripts
21853 @cindex print list of auto-loaded canned sequences of commands scripts
21854 @item info auto-load gdb-scripts [@var{regexp}]
21855 Print the list of all canned sequences of commands scripts that @value{GDBN}
21859 If @var{regexp} is supplied only canned sequences of commands scripts with
21860 matching names are printed.
21862 @node Auto-loading safe path
21863 @subsection Security restriction for auto-loading
21864 @cindex auto-loading safe-path
21866 As the files of inferior can come from untrusted source (such as submitted by
21867 an application user) @value{GDBN} does not always load any files automatically.
21868 @value{GDBN} provides the @samp{set auto-load safe-path} setting to list
21869 directories trusted for loading files not explicitly requested by user.
21870 Each directory can also be a shell wildcard pattern.
21872 If the path is not set properly you will see a warning and the file will not
21877 Reading symbols from /home/user/gdb/gdb...done.
21878 warning: File "/home/user/gdb/gdb-gdb.gdb" auto-loading has been
21879 declined by your `auto-load safe-path' set
21880 to "$debugdir:$datadir/auto-load".
21881 warning: File "/home/user/gdb/gdb-gdb.py" auto-loading has been
21882 declined by your `auto-load safe-path' set
21883 to "$debugdir:$datadir/auto-load".
21886 The list of trusted directories is controlled by the following commands:
21889 @anchor{set auto-load safe-path}
21890 @kindex set auto-load safe-path
21891 @item set auto-load safe-path @r{[}@var{directories}@r{]}
21892 Set the list of directories (and their subdirectories) trusted for automatic
21893 loading and execution of scripts. You can also enter a specific trusted file.
21894 Each directory can also be a shell wildcard pattern; wildcards do not match
21895 directory separator - see @code{FNM_PATHNAME} for system function @code{fnmatch}
21896 (@pxref{Wildcard Matching, fnmatch, , libc, GNU C Library Reference Manual}).
21897 If you omit @var{directories}, @samp{auto-load safe-path} will be reset to
21898 its default value as specified during @value{GDBN} compilation.
21900 The list of directories uses path separator (@samp{:} on GNU and Unix
21901 systems, @samp{;} on MS-Windows and MS-DOS) to separate directories, similarly
21902 to the @env{PATH} environment variable.
21904 @anchor{show auto-load safe-path}
21905 @kindex show auto-load safe-path
21906 @item show auto-load safe-path
21907 Show the list of directories trusted for automatic loading and execution of
21910 @anchor{add-auto-load-safe-path}
21911 @kindex add-auto-load-safe-path
21912 @item add-auto-load-safe-path
21913 Add an entry (or list of entries) the list of directories trusted for automatic
21914 loading and execution of scripts. Multiple entries may be delimited by the
21915 host platform path separator in use.
21918 This variable defaults to what @code{--with-auto-load-dir} has been configured
21919 to (@pxref{with-auto-load-dir}). @file{$debugdir} and @file{$datadir}
21920 substitution applies the same as for @ref{set auto-load scripts-directory}.
21921 The default @code{set auto-load safe-path} value can be also overriden by
21922 @value{GDBN} configuration option @option{--with-auto-load-safe-path}.
21924 Setting this variable to @file{/} disables this security protection,
21925 corresponding @value{GDBN} configuration option is
21926 @option{--without-auto-load-safe-path}.
21927 This variable is supposed to be set to the system directories writable by the
21928 system superuser only. Users can add their source directories in init files in
21929 their home directories (@pxref{Home Directory Init File}). See also deprecated
21930 init file in the current directory
21931 (@pxref{Init File in the Current Directory during Startup}).
21933 To force @value{GDBN} to load the files it declined to load in the previous
21934 example, you could use one of the following ways:
21937 @item @file{~/.gdbinit}: @samp{add-auto-load-safe-path ~/src/gdb}
21938 Specify this trusted directory (or a file) as additional component of the list.
21939 You have to specify also any existing directories displayed by
21940 by @samp{show auto-load safe-path} (such as @samp{/usr:/bin} in this example).
21942 @item @kbd{gdb -iex "set auto-load safe-path /usr:/bin:~/src/gdb" @dots{}}
21943 Specify this directory as in the previous case but just for a single
21944 @value{GDBN} session.
21946 @item @kbd{gdb -iex "set auto-load safe-path /" @dots{}}
21947 Disable auto-loading safety for a single @value{GDBN} session.
21948 This assumes all the files you debug during this @value{GDBN} session will come
21949 from trusted sources.
21951 @item @kbd{./configure --without-auto-load-safe-path}
21952 During compilation of @value{GDBN} you may disable any auto-loading safety.
21953 This assumes all the files you will ever debug with this @value{GDBN} come from
21957 On the other hand you can also explicitly forbid automatic files loading which
21958 also suppresses any such warning messages:
21961 @item @kbd{gdb -iex "set auto-load no" @dots{}}
21962 You can use @value{GDBN} command-line option for a single @value{GDBN} session.
21964 @item @file{~/.gdbinit}: @samp{set auto-load no}
21965 Disable auto-loading globally for the user
21966 (@pxref{Home Directory Init File}). While it is improbable, you could also
21967 use system init file instead (@pxref{System-wide configuration}).
21970 This setting applies to the file names as entered by user. If no entry matches
21971 @value{GDBN} tries as a last resort to also resolve all the file names into
21972 their canonical form (typically resolving symbolic links) and compare the
21973 entries again. @value{GDBN} already canonicalizes most of the filenames on its
21974 own before starting the comparison so a canonical form of directories is
21975 recommended to be entered.
21977 @node Auto-loading verbose mode
21978 @subsection Displaying files tried for auto-load
21979 @cindex auto-loading verbose mode
21981 For better visibility of all the file locations where you can place scripts to
21982 be auto-loaded with inferior --- or to protect yourself against accidental
21983 execution of untrusted scripts --- @value{GDBN} provides a feature for printing
21984 all the files attempted to be loaded. Both existing and non-existing files may
21987 For example the list of directories from which it is safe to auto-load files
21988 (@pxref{Auto-loading safe path}) applies also to canonicalized filenames which
21989 may not be too obvious while setting it up.
21992 (gdb) set debug auto-load on
21993 (gdb) file ~/src/t/true
21994 auto-load: Loading canned sequences of commands script "/tmp/true-gdb.gdb"
21995 for objfile "/tmp/true".
21996 auto-load: Updating directories of "/usr:/opt".
21997 auto-load: Using directory "/usr".
21998 auto-load: Using directory "/opt".
21999 warning: File "/tmp/true-gdb.gdb" auto-loading has been declined
22000 by your `auto-load safe-path' set to "/usr:/opt".
22004 @anchor{set debug auto-load}
22005 @kindex set debug auto-load
22006 @item set debug auto-load [on|off]
22007 Set whether to print the filenames attempted to be auto-loaded.
22009 @anchor{show debug auto-load}
22010 @kindex show debug auto-load
22011 @item show debug auto-load
22012 Show whether printing of the filenames attempted to be auto-loaded is turned
22016 @node Messages/Warnings
22017 @section Optional Warnings and Messages
22019 @cindex verbose operation
22020 @cindex optional warnings
22021 By default, @value{GDBN} is silent about its inner workings. If you are
22022 running on a slow machine, you may want to use the @code{set verbose}
22023 command. This makes @value{GDBN} tell you when it does a lengthy
22024 internal operation, so you will not think it has crashed.
22026 Currently, the messages controlled by @code{set verbose} are those
22027 which announce that the symbol table for a source file is being read;
22028 see @code{symbol-file} in @ref{Files, ,Commands to Specify Files}.
22031 @kindex set verbose
22032 @item set verbose on
22033 Enables @value{GDBN} output of certain informational messages.
22035 @item set verbose off
22036 Disables @value{GDBN} output of certain informational messages.
22038 @kindex show verbose
22040 Displays whether @code{set verbose} is on or off.
22043 By default, if @value{GDBN} encounters bugs in the symbol table of an
22044 object file, it is silent; but if you are debugging a compiler, you may
22045 find this information useful (@pxref{Symbol Errors, ,Errors Reading
22050 @kindex set complaints
22051 @item set complaints @var{limit}
22052 Permits @value{GDBN} to output @var{limit} complaints about each type of
22053 unusual symbols before becoming silent about the problem. Set
22054 @var{limit} to zero to suppress all complaints; set it to a large number
22055 to prevent complaints from being suppressed.
22057 @kindex show complaints
22058 @item show complaints
22059 Displays how many symbol complaints @value{GDBN} is permitted to produce.
22063 @anchor{confirmation requests}
22064 By default, @value{GDBN} is cautious, and asks what sometimes seems to be a
22065 lot of stupid questions to confirm certain commands. For example, if
22066 you try to run a program which is already running:
22070 The program being debugged has been started already.
22071 Start it from the beginning? (y or n)
22074 If you are willing to unflinchingly face the consequences of your own
22075 commands, you can disable this ``feature'':
22079 @kindex set confirm
22081 @cindex confirmation
22082 @cindex stupid questions
22083 @item set confirm off
22084 Disables confirmation requests. Note that running @value{GDBN} with
22085 the @option{--batch} option (@pxref{Mode Options, -batch}) also
22086 automatically disables confirmation requests.
22088 @item set confirm on
22089 Enables confirmation requests (the default).
22091 @kindex show confirm
22093 Displays state of confirmation requests.
22097 @cindex command tracing
22098 If you need to debug user-defined commands or sourced files you may find it
22099 useful to enable @dfn{command tracing}. In this mode each command will be
22100 printed as it is executed, prefixed with one or more @samp{+} symbols, the
22101 quantity denoting the call depth of each command.
22104 @kindex set trace-commands
22105 @cindex command scripts, debugging
22106 @item set trace-commands on
22107 Enable command tracing.
22108 @item set trace-commands off
22109 Disable command tracing.
22110 @item show trace-commands
22111 Display the current state of command tracing.
22114 @node Debugging Output
22115 @section Optional Messages about Internal Happenings
22116 @cindex optional debugging messages
22118 @value{GDBN} has commands that enable optional debugging messages from
22119 various @value{GDBN} subsystems; normally these commands are of
22120 interest to @value{GDBN} maintainers, or when reporting a bug. This
22121 section documents those commands.
22124 @kindex set exec-done-display
22125 @item set exec-done-display
22126 Turns on or off the notification of asynchronous commands'
22127 completion. When on, @value{GDBN} will print a message when an
22128 asynchronous command finishes its execution. The default is off.
22129 @kindex show exec-done-display
22130 @item show exec-done-display
22131 Displays the current setting of asynchronous command completion
22134 @cindex gdbarch debugging info
22135 @cindex architecture debugging info
22136 @item set debug arch
22137 Turns on or off display of gdbarch debugging info. The default is off
22139 @item show debug arch
22140 Displays the current state of displaying gdbarch debugging info.
22141 @item set debug aix-thread
22142 @cindex AIX threads
22143 Display debugging messages about inner workings of the AIX thread
22145 @item show debug aix-thread
22146 Show the current state of AIX thread debugging info display.
22147 @item set debug check-physname
22149 Check the results of the ``physname'' computation. When reading DWARF
22150 debugging information for C@t{++}, @value{GDBN} attempts to compute
22151 each entity's name. @value{GDBN} can do this computation in two
22152 different ways, depending on exactly what information is present.
22153 When enabled, this setting causes @value{GDBN} to compute the names
22154 both ways and display any discrepancies.
22155 @item show debug check-physname
22156 Show the current state of ``physname'' checking.
22157 @item set debug dwarf2-die
22158 @cindex DWARF2 DIEs
22159 Dump DWARF2 DIEs after they are read in.
22160 The value is the number of nesting levels to print.
22161 A value of zero turns off the display.
22162 @item show debug dwarf2-die
22163 Show the current state of DWARF2 DIE debugging.
22164 @item set debug dwarf2-read
22165 @cindex DWARF2 Reading
22166 Turns on or off display of debugging messages related to reading
22167 DWARF debug info. The default is off.
22168 @item show debug dwarf2-read
22169 Show the current state of DWARF2 reader debugging.
22170 @item set debug displaced
22171 @cindex displaced stepping debugging info
22172 Turns on or off display of @value{GDBN} debugging info for the
22173 displaced stepping support. The default is off.
22174 @item show debug displaced
22175 Displays the current state of displaying @value{GDBN} debugging info
22176 related to displaced stepping.
22177 @item set debug event
22178 @cindex event debugging info
22179 Turns on or off display of @value{GDBN} event debugging info. The
22181 @item show debug event
22182 Displays the current state of displaying @value{GDBN} event debugging
22184 @item set debug expression
22185 @cindex expression debugging info
22186 Turns on or off display of debugging info about @value{GDBN}
22187 expression parsing. The default is off.
22188 @item show debug expression
22189 Displays the current state of displaying debugging info about
22190 @value{GDBN} expression parsing.
22191 @item set debug frame
22192 @cindex frame debugging info
22193 Turns on or off display of @value{GDBN} frame debugging info. The
22195 @item show debug frame
22196 Displays the current state of displaying @value{GDBN} frame debugging
22198 @item set debug gnu-nat
22199 @cindex @sc{gnu}/Hurd debug messages
22200 Turns on or off debugging messages from the @sc{gnu}/Hurd debug support.
22201 @item show debug gnu-nat
22202 Show the current state of @sc{gnu}/Hurd debugging messages.
22203 @item set debug infrun
22204 @cindex inferior debugging info
22205 Turns on or off display of @value{GDBN} debugging info for running the inferior.
22206 The default is off. @file{infrun.c} contains GDB's runtime state machine used
22207 for implementing operations such as single-stepping the inferior.
22208 @item show debug infrun
22209 Displays the current state of @value{GDBN} inferior debugging.
22210 @item set debug jit
22211 @cindex just-in-time compilation, debugging messages
22212 Turns on or off debugging messages from JIT debug support.
22213 @item show debug jit
22214 Displays the current state of @value{GDBN} JIT debugging.
22215 @item set debug lin-lwp
22216 @cindex @sc{gnu}/Linux LWP debug messages
22217 @cindex Linux lightweight processes
22218 Turns on or off debugging messages from the Linux LWP debug support.
22219 @item show debug lin-lwp
22220 Show the current state of Linux LWP debugging messages.
22221 @item set debug notification
22222 @cindex remote async notification debugging info
22223 Turns on or off debugging messages about remote async notification.
22224 The default is off.
22225 @item show debug notification
22226 Displays the current state of remote async notification debugging messages.
22227 @item set debug observer
22228 @cindex observer debugging info
22229 Turns on or off display of @value{GDBN} observer debugging. This
22230 includes info such as the notification of observable events.
22231 @item show debug observer
22232 Displays the current state of observer debugging.
22233 @item set debug overload
22234 @cindex C@t{++} overload debugging info
22235 Turns on or off display of @value{GDBN} C@t{++} overload debugging
22236 info. This includes info such as ranking of functions, etc. The default
22238 @item show debug overload
22239 Displays the current state of displaying @value{GDBN} C@t{++} overload
22241 @cindex expression parser, debugging info
22242 @cindex debug expression parser
22243 @item set debug parser
22244 Turns on or off the display of expression parser debugging output.
22245 Internally, this sets the @code{yydebug} variable in the expression
22246 parser. @xref{Tracing, , Tracing Your Parser, bison, Bison}, for
22247 details. The default is off.
22248 @item show debug parser
22249 Show the current state of expression parser debugging.
22250 @cindex packets, reporting on stdout
22251 @cindex serial connections, debugging
22252 @cindex debug remote protocol
22253 @cindex remote protocol debugging
22254 @cindex display remote packets
22255 @item set debug remote
22256 Turns on or off display of reports on all packets sent back and forth across
22257 the serial line to the remote machine. The info is printed on the
22258 @value{GDBN} standard output stream. The default is off.
22259 @item show debug remote
22260 Displays the state of display of remote packets.
22261 @item set debug serial
22262 Turns on or off display of @value{GDBN} serial debugging info. The
22264 @item show debug serial
22265 Displays the current state of displaying @value{GDBN} serial debugging
22267 @item set debug solib-frv
22268 @cindex FR-V shared-library debugging
22269 Turns on or off debugging messages for FR-V shared-library code.
22270 @item show debug solib-frv
22271 Display the current state of FR-V shared-library code debugging
22273 @item set debug symtab-create
22274 @cindex symbol table creation
22275 Turns on or off display of debugging messages related to symbol table creation.
22276 The default is off.
22277 @item show debug symtab-create
22278 Show the current state of symbol table creation debugging.
22279 @item set debug target
22280 @cindex target debugging info
22281 Turns on or off display of @value{GDBN} target debugging info. This info
22282 includes what is going on at the target level of GDB, as it happens. The
22283 default is 0. Set it to 1 to track events, and to 2 to also track the
22284 value of large memory transfers. Changes to this flag do not take effect
22285 until the next time you connect to a target or use the @code{run} command.
22286 @item show debug target
22287 Displays the current state of displaying @value{GDBN} target debugging
22289 @item set debug timestamp
22290 @cindex timestampping debugging info
22291 Turns on or off display of timestamps with @value{GDBN} debugging info.
22292 When enabled, seconds and microseconds are displayed before each debugging
22294 @item show debug timestamp
22295 Displays the current state of displaying timestamps with @value{GDBN}
22297 @item set debugvarobj
22298 @cindex variable object debugging info
22299 Turns on or off display of @value{GDBN} variable object debugging
22300 info. The default is off.
22301 @item show debugvarobj
22302 Displays the current state of displaying @value{GDBN} variable object
22304 @item set debug xml
22305 @cindex XML parser debugging
22306 Turns on or off debugging messages for built-in XML parsers.
22307 @item show debug xml
22308 Displays the current state of XML debugging messages.
22311 @node Other Misc Settings
22312 @section Other Miscellaneous Settings
22313 @cindex miscellaneous settings
22316 @kindex set interactive-mode
22317 @item set interactive-mode
22318 If @code{on}, forces @value{GDBN} to assume that GDB was started
22319 in a terminal. In practice, this means that @value{GDBN} should wait
22320 for the user to answer queries generated by commands entered at
22321 the command prompt. If @code{off}, forces @value{GDBN} to operate
22322 in the opposite mode, and it uses the default answers to all queries.
22323 If @code{auto} (the default), @value{GDBN} tries to determine whether
22324 its standard input is a terminal, and works in interactive-mode if it
22325 is, non-interactively otherwise.
22327 In the vast majority of cases, the debugger should be able to guess
22328 correctly which mode should be used. But this setting can be useful
22329 in certain specific cases, such as running a MinGW @value{GDBN}
22330 inside a cygwin window.
22332 @kindex show interactive-mode
22333 @item show interactive-mode
22334 Displays whether the debugger is operating in interactive mode or not.
22337 @node Extending GDB
22338 @chapter Extending @value{GDBN}
22339 @cindex extending GDB
22341 @value{GDBN} provides three mechanisms for extension. The first is based
22342 on composition of @value{GDBN} commands, the second is based on the
22343 Python scripting language, and the third is for defining new aliases of
22346 To facilitate the use of the first two extensions, @value{GDBN} is capable
22347 of evaluating the contents of a file. When doing so, @value{GDBN}
22348 can recognize which scripting language is being used by looking at
22349 the filename extension. Files with an unrecognized filename extension
22350 are always treated as a @value{GDBN} Command Files.
22351 @xref{Command Files,, Command files}.
22353 You can control how @value{GDBN} evaluates these files with the following
22357 @kindex set script-extension
22358 @kindex show script-extension
22359 @item set script-extension off
22360 All scripts are always evaluated as @value{GDBN} Command Files.
22362 @item set script-extension soft
22363 The debugger determines the scripting language based on filename
22364 extension. If this scripting language is supported, @value{GDBN}
22365 evaluates the script using that language. Otherwise, it evaluates
22366 the file as a @value{GDBN} Command File.
22368 @item set script-extension strict
22369 The debugger determines the scripting language based on filename
22370 extension, and evaluates the script using that language. If the
22371 language is not supported, then the evaluation fails.
22373 @item show script-extension
22374 Display the current value of the @code{script-extension} option.
22379 * Sequences:: Canned Sequences of Commands
22380 * Python:: Scripting @value{GDBN} using Python
22381 * Aliases:: Creating new spellings of existing commands
22385 @section Canned Sequences of Commands
22387 Aside from breakpoint commands (@pxref{Break Commands, ,Breakpoint
22388 Command Lists}), @value{GDBN} provides two ways to store sequences of
22389 commands for execution as a unit: user-defined commands and command
22393 * Define:: How to define your own commands
22394 * Hooks:: Hooks for user-defined commands
22395 * Command Files:: How to write scripts of commands to be stored in a file
22396 * Output:: Commands for controlled output
22400 @subsection User-defined Commands
22402 @cindex user-defined command
22403 @cindex arguments, to user-defined commands
22404 A @dfn{user-defined command} is a sequence of @value{GDBN} commands to
22405 which you assign a new name as a command. This is done with the
22406 @code{define} command. User commands may accept up to 10 arguments
22407 separated by whitespace. Arguments are accessed within the user command
22408 via @code{$arg0@dots{}$arg9}. A trivial example:
22412 print $arg0 + $arg1 + $arg2
22417 To execute the command use:
22424 This defines the command @code{adder}, which prints the sum of
22425 its three arguments. Note the arguments are text substitutions, so they may
22426 reference variables, use complex expressions, or even perform inferior
22429 @cindex argument count in user-defined commands
22430 @cindex how many arguments (user-defined commands)
22431 In addition, @code{$argc} may be used to find out how many arguments have
22432 been passed. This expands to a number in the range 0@dots{}10.
22437 print $arg0 + $arg1
22440 print $arg0 + $arg1 + $arg2
22448 @item define @var{commandname}
22449 Define a command named @var{commandname}. If there is already a command
22450 by that name, you are asked to confirm that you want to redefine it.
22451 @var{commandname} may be a bare command name consisting of letters,
22452 numbers, dashes, and underscores. It may also start with any predefined
22453 prefix command. For example, @samp{define target my-target} creates
22454 a user-defined @samp{target my-target} command.
22456 The definition of the command is made up of other @value{GDBN} command lines,
22457 which are given following the @code{define} command. The end of these
22458 commands is marked by a line containing @code{end}.
22461 @kindex end@r{ (user-defined commands)}
22462 @item document @var{commandname}
22463 Document the user-defined command @var{commandname}, so that it can be
22464 accessed by @code{help}. The command @var{commandname} must already be
22465 defined. This command reads lines of documentation just as @code{define}
22466 reads the lines of the command definition, ending with @code{end}.
22467 After the @code{document} command is finished, @code{help} on command
22468 @var{commandname} displays the documentation you have written.
22470 You may use the @code{document} command again to change the
22471 documentation of a command. Redefining the command with @code{define}
22472 does not change the documentation.
22474 @kindex dont-repeat
22475 @cindex don't repeat command
22477 Used inside a user-defined command, this tells @value{GDBN} that this
22478 command should not be repeated when the user hits @key{RET}
22479 (@pxref{Command Syntax, repeat last command}).
22481 @kindex help user-defined
22482 @item help user-defined
22483 List all user-defined commands and all python commands defined in class
22484 COMAND_USER. The first line of the documentation or docstring is
22489 @itemx show user @var{commandname}
22490 Display the @value{GDBN} commands used to define @var{commandname} (but
22491 not its documentation). If no @var{commandname} is given, display the
22492 definitions for all user-defined commands.
22493 This does not work for user-defined python commands.
22495 @cindex infinite recursion in user-defined commands
22496 @kindex show max-user-call-depth
22497 @kindex set max-user-call-depth
22498 @item show max-user-call-depth
22499 @itemx set max-user-call-depth
22500 The value of @code{max-user-call-depth} controls how many recursion
22501 levels are allowed in user-defined commands before @value{GDBN} suspects an
22502 infinite recursion and aborts the command.
22503 This does not apply to user-defined python commands.
22506 In addition to the above commands, user-defined commands frequently
22507 use control flow commands, described in @ref{Command Files}.
22509 When user-defined commands are executed, the
22510 commands of the definition are not printed. An error in any command
22511 stops execution of the user-defined command.
22513 If used interactively, commands that would ask for confirmation proceed
22514 without asking when used inside a user-defined command. Many @value{GDBN}
22515 commands that normally print messages to say what they are doing omit the
22516 messages when used in a user-defined command.
22519 @subsection User-defined Command Hooks
22520 @cindex command hooks
22521 @cindex hooks, for commands
22522 @cindex hooks, pre-command
22525 You may define @dfn{hooks}, which are a special kind of user-defined
22526 command. Whenever you run the command @samp{foo}, if the user-defined
22527 command @samp{hook-foo} exists, it is executed (with no arguments)
22528 before that command.
22530 @cindex hooks, post-command
22532 A hook may also be defined which is run after the command you executed.
22533 Whenever you run the command @samp{foo}, if the user-defined command
22534 @samp{hookpost-foo} exists, it is executed (with no arguments) after
22535 that command. Post-execution hooks may exist simultaneously with
22536 pre-execution hooks, for the same command.
22538 It is valid for a hook to call the command which it hooks. If this
22539 occurs, the hook is not re-executed, thereby avoiding infinite recursion.
22541 @c It would be nice if hookpost could be passed a parameter indicating
22542 @c if the command it hooks executed properly or not. FIXME!
22544 @kindex stop@r{, a pseudo-command}
22545 In addition, a pseudo-command, @samp{stop} exists. Defining
22546 (@samp{hook-stop}) makes the associated commands execute every time
22547 execution stops in your program: before breakpoint commands are run,
22548 displays are printed, or the stack frame is printed.
22550 For example, to ignore @code{SIGALRM} signals while
22551 single-stepping, but treat them normally during normal execution,
22556 handle SIGALRM nopass
22560 handle SIGALRM pass
22563 define hook-continue
22564 handle SIGALRM pass
22568 As a further example, to hook at the beginning and end of the @code{echo}
22569 command, and to add extra text to the beginning and end of the message,
22577 define hookpost-echo
22581 (@value{GDBP}) echo Hello World
22582 <<<---Hello World--->>>
22587 You can define a hook for any single-word command in @value{GDBN}, but
22588 not for command aliases; you should define a hook for the basic command
22589 name, e.g.@: @code{backtrace} rather than @code{bt}.
22590 @c FIXME! So how does Joe User discover whether a command is an alias
22592 You can hook a multi-word command by adding @code{hook-} or
22593 @code{hookpost-} to the last word of the command, e.g.@:
22594 @samp{define target hook-remote} to add a hook to @samp{target remote}.
22596 If an error occurs during the execution of your hook, execution of
22597 @value{GDBN} commands stops and @value{GDBN} issues a prompt
22598 (before the command that you actually typed had a chance to run).
22600 If you try to define a hook which does not match any known command, you
22601 get a warning from the @code{define} command.
22603 @node Command Files
22604 @subsection Command Files
22606 @cindex command files
22607 @cindex scripting commands
22608 A command file for @value{GDBN} is a text file made of lines that are
22609 @value{GDBN} commands. Comments (lines starting with @kbd{#}) may
22610 also be included. An empty line in a command file does nothing; it
22611 does not mean to repeat the last command, as it would from the
22614 You can request the execution of a command file with the @code{source}
22615 command. Note that the @code{source} command is also used to evaluate
22616 scripts that are not Command Files. The exact behavior can be configured
22617 using the @code{script-extension} setting.
22618 @xref{Extending GDB,, Extending GDB}.
22622 @cindex execute commands from a file
22623 @item source [-s] [-v] @var{filename}
22624 Execute the command file @var{filename}.
22627 The lines in a command file are generally executed sequentially,
22628 unless the order of execution is changed by one of the
22629 @emph{flow-control commands} described below. The commands are not
22630 printed as they are executed. An error in any command terminates
22631 execution of the command file and control is returned to the console.
22633 @value{GDBN} first searches for @var{filename} in the current directory.
22634 If the file is not found there, and @var{filename} does not specify a
22635 directory, then @value{GDBN} also looks for the file on the source search path
22636 (specified with the @samp{directory} command);
22637 except that @file{$cdir} is not searched because the compilation directory
22638 is not relevant to scripts.
22640 If @code{-s} is specified, then @value{GDBN} searches for @var{filename}
22641 on the search path even if @var{filename} specifies a directory.
22642 The search is done by appending @var{filename} to each element of the
22643 search path. So, for example, if @var{filename} is @file{mylib/myscript}
22644 and the search path contains @file{/home/user} then @value{GDBN} will
22645 look for the script @file{/home/user/mylib/myscript}.
22646 The search is also done if @var{filename} is an absolute path.
22647 For example, if @var{filename} is @file{/tmp/myscript} and
22648 the search path contains @file{/home/user} then @value{GDBN} will
22649 look for the script @file{/home/user/tmp/myscript}.
22650 For DOS-like systems, if @var{filename} contains a drive specification,
22651 it is stripped before concatenation. For example, if @var{filename} is
22652 @file{d:myscript} and the search path contains @file{c:/tmp} then @value{GDBN}
22653 will look for the script @file{c:/tmp/myscript}.
22655 If @code{-v}, for verbose mode, is given then @value{GDBN} displays
22656 each command as it is executed. The option must be given before
22657 @var{filename}, and is interpreted as part of the filename anywhere else.
22659 Commands that would ask for confirmation if used interactively proceed
22660 without asking when used in a command file. Many @value{GDBN} commands that
22661 normally print messages to say what they are doing omit the messages
22662 when called from command files.
22664 @value{GDBN} also accepts command input from standard input. In this
22665 mode, normal output goes to standard output and error output goes to
22666 standard error. Errors in a command file supplied on standard input do
22667 not terminate execution of the command file---execution continues with
22671 gdb < cmds > log 2>&1
22674 (The syntax above will vary depending on the shell used.) This example
22675 will execute commands from the file @file{cmds}. All output and errors
22676 would be directed to @file{log}.
22678 Since commands stored on command files tend to be more general than
22679 commands typed interactively, they frequently need to deal with
22680 complicated situations, such as different or unexpected values of
22681 variables and symbols, changes in how the program being debugged is
22682 built, etc. @value{GDBN} provides a set of flow-control commands to
22683 deal with these complexities. Using these commands, you can write
22684 complex scripts that loop over data structures, execute commands
22685 conditionally, etc.
22692 This command allows to include in your script conditionally executed
22693 commands. The @code{if} command takes a single argument, which is an
22694 expression to evaluate. It is followed by a series of commands that
22695 are executed only if the expression is true (its value is nonzero).
22696 There can then optionally be an @code{else} line, followed by a series
22697 of commands that are only executed if the expression was false. The
22698 end of the list is marked by a line containing @code{end}.
22702 This command allows to write loops. Its syntax is similar to
22703 @code{if}: the command takes a single argument, which is an expression
22704 to evaluate, and must be followed by the commands to execute, one per
22705 line, terminated by an @code{end}. These commands are called the
22706 @dfn{body} of the loop. The commands in the body of @code{while} are
22707 executed repeatedly as long as the expression evaluates to true.
22711 This command exits the @code{while} loop in whose body it is included.
22712 Execution of the script continues after that @code{while}s @code{end}
22715 @kindex loop_continue
22716 @item loop_continue
22717 This command skips the execution of the rest of the body of commands
22718 in the @code{while} loop in whose body it is included. Execution
22719 branches to the beginning of the @code{while} loop, where it evaluates
22720 the controlling expression.
22722 @kindex end@r{ (if/else/while commands)}
22724 Terminate the block of commands that are the body of @code{if},
22725 @code{else}, or @code{while} flow-control commands.
22730 @subsection Commands for Controlled Output
22732 During the execution of a command file or a user-defined command, normal
22733 @value{GDBN} output is suppressed; the only output that appears is what is
22734 explicitly printed by the commands in the definition. This section
22735 describes three commands useful for generating exactly the output you
22740 @item echo @var{text}
22741 @c I do not consider backslash-space a standard C escape sequence
22742 @c because it is not in ANSI.
22743 Print @var{text}. Nonprinting characters can be included in
22744 @var{text} using C escape sequences, such as @samp{\n} to print a
22745 newline. @strong{No newline is printed unless you specify one.}
22746 In addition to the standard C escape sequences, a backslash followed
22747 by a space stands for a space. This is useful for displaying a
22748 string with spaces at the beginning or the end, since leading and
22749 trailing spaces are otherwise trimmed from all arguments.
22750 To print @samp{@w{ }and foo =@w{ }}, use the command
22751 @samp{echo \@w{ }and foo = \@w{ }}.
22753 A backslash at the end of @var{text} can be used, as in C, to continue
22754 the command onto subsequent lines. For example,
22757 echo This is some text\n\
22758 which is continued\n\
22759 onto several lines.\n
22762 produces the same output as
22765 echo This is some text\n
22766 echo which is continued\n
22767 echo onto several lines.\n
22771 @item output @var{expression}
22772 Print the value of @var{expression} and nothing but that value: no
22773 newlines, no @samp{$@var{nn} = }. The value is not entered in the
22774 value history either. @xref{Expressions, ,Expressions}, for more information
22777 @item output/@var{fmt} @var{expression}
22778 Print the value of @var{expression} in format @var{fmt}. You can use
22779 the same formats as for @code{print}. @xref{Output Formats,,Output
22780 Formats}, for more information.
22783 @item printf @var{template}, @var{expressions}@dots{}
22784 Print the values of one or more @var{expressions} under the control of
22785 the string @var{template}. To print several values, make
22786 @var{expressions} be a comma-separated list of individual expressions,
22787 which may be either numbers or pointers. Their values are printed as
22788 specified by @var{template}, exactly as a C program would do by
22789 executing the code below:
22792 printf (@var{template}, @var{expressions}@dots{});
22795 As in @code{C} @code{printf}, ordinary characters in @var{template}
22796 are printed verbatim, while @dfn{conversion specification} introduced
22797 by the @samp{%} character cause subsequent @var{expressions} to be
22798 evaluated, their values converted and formatted according to type and
22799 style information encoded in the conversion specifications, and then
22802 For example, you can print two values in hex like this:
22805 printf "foo, bar-foo = 0x%x, 0x%x\n", foo, bar-foo
22808 @code{printf} supports all the standard @code{C} conversion
22809 specifications, including the flags and modifiers between the @samp{%}
22810 character and the conversion letter, with the following exceptions:
22814 The argument-ordering modifiers, such as @samp{2$}, are not supported.
22817 The modifier @samp{*} is not supported for specifying precision or
22821 The @samp{'} flag (for separation of digits into groups according to
22822 @code{LC_NUMERIC'}) is not supported.
22825 The type modifiers @samp{hh}, @samp{j}, @samp{t}, and @samp{z} are not
22829 The conversion letter @samp{n} (as in @samp{%n}) is not supported.
22832 The conversion letters @samp{a} and @samp{A} are not supported.
22836 Note that the @samp{ll} type modifier is supported only if the
22837 underlying @code{C} implementation used to build @value{GDBN} supports
22838 the @code{long long int} type, and the @samp{L} type modifier is
22839 supported only if @code{long double} type is available.
22841 As in @code{C}, @code{printf} supports simple backslash-escape
22842 sequences, such as @code{\n}, @samp{\t}, @samp{\\}, @samp{\"},
22843 @samp{\a}, and @samp{\f}, that consist of backslash followed by a
22844 single character. Octal and hexadecimal escape sequences are not
22847 Additionally, @code{printf} supports conversion specifications for DFP
22848 (@dfn{Decimal Floating Point}) types using the following length modifiers
22849 together with a floating point specifier.
22854 @samp{H} for printing @code{Decimal32} types.
22857 @samp{D} for printing @code{Decimal64} types.
22860 @samp{DD} for printing @code{Decimal128} types.
22863 If the underlying @code{C} implementation used to build @value{GDBN} has
22864 support for the three length modifiers for DFP types, other modifiers
22865 such as width and precision will also be available for @value{GDBN} to use.
22867 In case there is no such @code{C} support, no additional modifiers will be
22868 available and the value will be printed in the standard way.
22870 Here's an example of printing DFP types using the above conversion letters:
22872 printf "D32: %Hf - D64: %Df - D128: %DDf\n",1.2345df,1.2E10dd,1.2E1dl
22876 @item eval @var{template}, @var{expressions}@dots{}
22877 Convert the values of one or more @var{expressions} under the control of
22878 the string @var{template} to a command line, and call it.
22883 @section Scripting @value{GDBN} using Python
22884 @cindex python scripting
22885 @cindex scripting with python
22887 You can script @value{GDBN} using the @uref{http://www.python.org/,
22888 Python programming language}. This feature is available only if
22889 @value{GDBN} was configured using @option{--with-python}.
22891 @cindex python directory
22892 Python scripts used by @value{GDBN} should be installed in
22893 @file{@var{data-directory}/python}, where @var{data-directory} is
22894 the data directory as determined at @value{GDBN} startup (@pxref{Data Files}).
22895 This directory, known as the @dfn{python directory},
22896 is automatically added to the Python Search Path in order to allow
22897 the Python interpreter to locate all scripts installed at this location.
22899 Additionally, @value{GDBN} commands and convenience functions which
22900 are written in Python and are located in the
22901 @file{@var{data-directory}/python/gdb/command} or
22902 @file{@var{data-directory}/python/gdb/function} directories are
22903 automatically imported when @value{GDBN} starts.
22906 * Python Commands:: Accessing Python from @value{GDBN}.
22907 * Python API:: Accessing @value{GDBN} from Python.
22908 * Python Auto-loading:: Automatically loading Python code.
22909 * Python modules:: Python modules provided by @value{GDBN}.
22912 @node Python Commands
22913 @subsection Python Commands
22914 @cindex python commands
22915 @cindex commands to access python
22917 @value{GDBN} provides two commands for accessing the Python interpreter,
22918 and one related setting:
22921 @kindex python-interactive
22923 @item python-interactive @r{[}@var{command}@r{]}
22924 @itemx pi @r{[}@var{command}@r{]}
22925 Without an argument, the @code{python-interactive} command can be used
22926 to start an interactive Python prompt. To return to @value{GDBN},
22927 type the @code{EOF} character (e.g., @kbd{Ctrl-D} on an empty prompt).
22929 Alternatively, a single-line Python command can be given as an
22930 argument and evaluated. If the command is an expression, the result
22931 will be printed; otherwise, nothing will be printed. For example:
22934 (@value{GDBP}) python-interactive 2 + 3
22940 @item python @r{[}@var{command}@r{]}
22941 @itemx py @r{[}@var{command}@r{]}
22942 The @code{python} command can be used to evaluate Python code.
22944 If given an argument, the @code{python} command will evaluate the
22945 argument as a Python command. For example:
22948 (@value{GDBP}) python print 23
22952 If you do not provide an argument to @code{python}, it will act as a
22953 multi-line command, like @code{define}. In this case, the Python
22954 script is made up of subsequent command lines, given after the
22955 @code{python} command. This command list is terminated using a line
22956 containing @code{end}. For example:
22959 (@value{GDBP}) python
22961 End with a line saying just "end".
22967 @kindex set python print-stack
22968 @item set python print-stack
22969 By default, @value{GDBN} will print only the message component of a
22970 Python exception when an error occurs in a Python script. This can be
22971 controlled using @code{set python print-stack}: if @code{full}, then
22972 full Python stack printing is enabled; if @code{none}, then Python stack
22973 and message printing is disabled; if @code{message}, the default, only
22974 the message component of the error is printed.
22977 It is also possible to execute a Python script from the @value{GDBN}
22981 @item source @file{script-name}
22982 The script name must end with @samp{.py} and @value{GDBN} must be configured
22983 to recognize the script language based on filename extension using
22984 the @code{script-extension} setting. @xref{Extending GDB, ,Extending GDB}.
22986 @item python execfile ("script-name")
22987 This method is based on the @code{execfile} Python built-in function,
22988 and thus is always available.
22992 @subsection Python API
22994 @cindex programming in python
22996 @cindex python stdout
22997 @cindex python pagination
22998 At startup, @value{GDBN} overrides Python's @code{sys.stdout} and
22999 @code{sys.stderr} to print using @value{GDBN}'s output-paging streams.
23000 A Python program which outputs to one of these streams may have its
23001 output interrupted by the user (@pxref{Screen Size}). In this
23002 situation, a Python @code{KeyboardInterrupt} exception is thrown.
23005 * Basic Python:: Basic Python Functions.
23006 * Exception Handling:: How Python exceptions are translated.
23007 * Values From Inferior:: Python representation of values.
23008 * Types In Python:: Python representation of types.
23009 * Pretty Printing API:: Pretty-printing values.
23010 * Selecting Pretty-Printers:: How GDB chooses a pretty-printer.
23011 * Writing a Pretty-Printer:: Writing a Pretty-Printer.
23012 * Type Printing API:: Pretty-printing types.
23013 * Inferiors In Python:: Python representation of inferiors (processes)
23014 * Events In Python:: Listening for events from @value{GDBN}.
23015 * Threads In Python:: Accessing inferior threads from Python.
23016 * Commands In Python:: Implementing new commands in Python.
23017 * Parameters In Python:: Adding new @value{GDBN} parameters.
23018 * Functions In Python:: Writing new convenience functions.
23019 * Progspaces In Python:: Program spaces.
23020 * Objfiles In Python:: Object files.
23021 * Frames In Python:: Accessing inferior stack frames from Python.
23022 * Blocks In Python:: Accessing frame blocks from Python.
23023 * Symbols In Python:: Python representation of symbols.
23024 * Symbol Tables In Python:: Python representation of symbol tables.
23025 * Breakpoints In Python:: Manipulating breakpoints using Python.
23026 * Finish Breakpoints in Python:: Setting Breakpoints on function return
23028 * Lazy Strings In Python:: Python representation of lazy strings.
23029 * Architectures In Python:: Python representation of architectures.
23033 @subsubsection Basic Python
23035 @cindex python functions
23036 @cindex python module
23038 @value{GDBN} introduces a new Python module, named @code{gdb}. All
23039 methods and classes added by @value{GDBN} are placed in this module.
23040 @value{GDBN} automatically @code{import}s the @code{gdb} module for
23041 use in all scripts evaluated by the @code{python} command.
23043 @findex gdb.PYTHONDIR
23044 @defvar gdb.PYTHONDIR
23045 A string containing the python directory (@pxref{Python}).
23048 @findex gdb.execute
23049 @defun gdb.execute (command @r{[}, from_tty @r{[}, to_string@r{]]})
23050 Evaluate @var{command}, a string, as a @value{GDBN} CLI command.
23051 If a GDB exception happens while @var{command} runs, it is
23052 translated as described in @ref{Exception Handling,,Exception Handling}.
23054 @var{from_tty} specifies whether @value{GDBN} ought to consider this
23055 command as having originated from the user invoking it interactively.
23056 It must be a boolean value. If omitted, it defaults to @code{False}.
23058 By default, any output produced by @var{command} is sent to
23059 @value{GDBN}'s standard output. If the @var{to_string} parameter is
23060 @code{True}, then output will be collected by @code{gdb.execute} and
23061 returned as a string. The default is @code{False}, in which case the
23062 return value is @code{None}. If @var{to_string} is @code{True}, the
23063 @value{GDBN} virtual terminal will be temporarily set to unlimited width
23064 and height, and its pagination will be disabled; @pxref{Screen Size}.
23067 @findex gdb.breakpoints
23068 @defun gdb.breakpoints ()
23069 Return a sequence holding all of @value{GDBN}'s breakpoints.
23070 @xref{Breakpoints In Python}, for more information.
23073 @findex gdb.parameter
23074 @defun gdb.parameter (parameter)
23075 Return the value of a @value{GDBN} parameter. @var{parameter} is a
23076 string naming the parameter to look up; @var{parameter} may contain
23077 spaces if the parameter has a multi-part name. For example,
23078 @samp{print object} is a valid parameter name.
23080 If the named parameter does not exist, this function throws a
23081 @code{gdb.error} (@pxref{Exception Handling}). Otherwise, the
23082 parameter's value is converted to a Python value of the appropriate
23083 type, and returned.
23086 @findex gdb.history
23087 @defun gdb.history (number)
23088 Return a value from @value{GDBN}'s value history (@pxref{Value
23089 History}). @var{number} indicates which history element to return.
23090 If @var{number} is negative, then @value{GDBN} will take its absolute value
23091 and count backward from the last element (i.e., the most recent element) to
23092 find the value to return. If @var{number} is zero, then @value{GDBN} will
23093 return the most recent element. If the element specified by @var{number}
23094 doesn't exist in the value history, a @code{gdb.error} exception will be
23097 If no exception is raised, the return value is always an instance of
23098 @code{gdb.Value} (@pxref{Values From Inferior}).
23101 @findex gdb.parse_and_eval
23102 @defun gdb.parse_and_eval (expression)
23103 Parse @var{expression} as an expression in the current language,
23104 evaluate it, and return the result as a @code{gdb.Value}.
23105 @var{expression} must be a string.
23107 This function can be useful when implementing a new command
23108 (@pxref{Commands In Python}), as it provides a way to parse the
23109 command's argument as an expression. It is also useful simply to
23110 compute values, for example, it is the only way to get the value of a
23111 convenience variable (@pxref{Convenience Vars}) as a @code{gdb.Value}.
23114 @findex gdb.find_pc_line
23115 @defun gdb.find_pc_line (pc)
23116 Return the @code{gdb.Symtab_and_line} object corresponding to the
23117 @var{pc} value. @xref{Symbol Tables In Python}. If an invalid
23118 value of @var{pc} is passed as an argument, then the @code{symtab} and
23119 @code{line} attributes of the returned @code{gdb.Symtab_and_line} object
23120 will be @code{None} and 0 respectively.
23123 @findex gdb.post_event
23124 @defun gdb.post_event (event)
23125 Put @var{event}, a callable object taking no arguments, into
23126 @value{GDBN}'s internal event queue. This callable will be invoked at
23127 some later point, during @value{GDBN}'s event processing. Events
23128 posted using @code{post_event} will be run in the order in which they
23129 were posted; however, there is no way to know when they will be
23130 processed relative to other events inside @value{GDBN}.
23132 @value{GDBN} is not thread-safe. If your Python program uses multiple
23133 threads, you must be careful to only call @value{GDBN}-specific
23134 functions in the main @value{GDBN} thread. @code{post_event} ensures
23138 (@value{GDBP}) python
23142 > def __init__(self, message):
23143 > self.message = message;
23144 > def __call__(self):
23145 > gdb.write(self.message)
23147 >class MyThread1 (threading.Thread):
23149 > gdb.post_event(Writer("Hello "))
23151 >class MyThread2 (threading.Thread):
23153 > gdb.post_event(Writer("World\n"))
23155 >MyThread1().start()
23156 >MyThread2().start()
23158 (@value{GDBP}) Hello World
23163 @defun gdb.write (string @r{[}, stream{]})
23164 Print a string to @value{GDBN}'s paginated output stream. The
23165 optional @var{stream} determines the stream to print to. The default
23166 stream is @value{GDBN}'s standard output stream. Possible stream
23173 @value{GDBN}'s standard output stream.
23178 @value{GDBN}'s standard error stream.
23183 @value{GDBN}'s log stream (@pxref{Logging Output}).
23186 Writing to @code{sys.stdout} or @code{sys.stderr} will automatically
23187 call this function and will automatically direct the output to the
23192 @defun gdb.flush ()
23193 Flush the buffer of a @value{GDBN} paginated stream so that the
23194 contents are displayed immediately. @value{GDBN} will flush the
23195 contents of a stream automatically when it encounters a newline in the
23196 buffer. The optional @var{stream} determines the stream to flush. The
23197 default stream is @value{GDBN}'s standard output stream. Possible
23204 @value{GDBN}'s standard output stream.
23209 @value{GDBN}'s standard error stream.
23214 @value{GDBN}'s log stream (@pxref{Logging Output}).
23218 Flushing @code{sys.stdout} or @code{sys.stderr} will automatically
23219 call this function for the relevant stream.
23222 @findex gdb.target_charset
23223 @defun gdb.target_charset ()
23224 Return the name of the current target character set (@pxref{Character
23225 Sets}). This differs from @code{gdb.parameter('target-charset')} in
23226 that @samp{auto} is never returned.
23229 @findex gdb.target_wide_charset
23230 @defun gdb.target_wide_charset ()
23231 Return the name of the current target wide character set
23232 (@pxref{Character Sets}). This differs from
23233 @code{gdb.parameter('target-wide-charset')} in that @samp{auto} is
23237 @findex gdb.solib_name
23238 @defun gdb.solib_name (address)
23239 Return the name of the shared library holding the given @var{address}
23240 as a string, or @code{None}.
23243 @findex gdb.decode_line
23244 @defun gdb.decode_line @r{[}expression@r{]}
23245 Return locations of the line specified by @var{expression}, or of the
23246 current line if no argument was given. This function returns a Python
23247 tuple containing two elements. The first element contains a string
23248 holding any unparsed section of @var{expression} (or @code{None} if
23249 the expression has been fully parsed). The second element contains
23250 either @code{None} or another tuple that contains all the locations
23251 that match the expression represented as @code{gdb.Symtab_and_line}
23252 objects (@pxref{Symbol Tables In Python}). If @var{expression} is
23253 provided, it is decoded the way that @value{GDBN}'s inbuilt
23254 @code{break} or @code{edit} commands do (@pxref{Specify Location}).
23257 @defun gdb.prompt_hook (current_prompt)
23258 @anchor{prompt_hook}
23260 If @var{prompt_hook} is callable, @value{GDBN} will call the method
23261 assigned to this operation before a prompt is displayed by
23264 The parameter @code{current_prompt} contains the current @value{GDBN}
23265 prompt. This method must return a Python string, or @code{None}. If
23266 a string is returned, the @value{GDBN} prompt will be set to that
23267 string. If @code{None} is returned, @value{GDBN} will continue to use
23268 the current prompt.
23270 Some prompts cannot be substituted in @value{GDBN}. Secondary prompts
23271 such as those used by readline for command input, and annotation
23272 related prompts are prohibited from being changed.
23275 @node Exception Handling
23276 @subsubsection Exception Handling
23277 @cindex python exceptions
23278 @cindex exceptions, python
23280 When executing the @code{python} command, Python exceptions
23281 uncaught within the Python code are translated to calls to
23282 @value{GDBN} error-reporting mechanism. If the command that called
23283 @code{python} does not handle the error, @value{GDBN} will
23284 terminate it and print an error message containing the Python
23285 exception name, the associated value, and the Python call stack
23286 backtrace at the point where the exception was raised. Example:
23289 (@value{GDBP}) python print foo
23290 Traceback (most recent call last):
23291 File "<string>", line 1, in <module>
23292 NameError: name 'foo' is not defined
23295 @value{GDBN} errors that happen in @value{GDBN} commands invoked by
23296 Python code are converted to Python exceptions. The type of the
23297 Python exception depends on the error.
23301 This is the base class for most exceptions generated by @value{GDBN}.
23302 It is derived from @code{RuntimeError}, for compatibility with earlier
23303 versions of @value{GDBN}.
23305 If an error occurring in @value{GDBN} does not fit into some more
23306 specific category, then the generated exception will have this type.
23308 @item gdb.MemoryError
23309 This is a subclass of @code{gdb.error} which is thrown when an
23310 operation tried to access invalid memory in the inferior.
23312 @item KeyboardInterrupt
23313 User interrupt (via @kbd{C-c} or by typing @kbd{q} at a pagination
23314 prompt) is translated to a Python @code{KeyboardInterrupt} exception.
23317 In all cases, your exception handler will see the @value{GDBN} error
23318 message as its value and the Python call stack backtrace at the Python
23319 statement closest to where the @value{GDBN} error occured as the
23322 @findex gdb.GdbError
23323 When implementing @value{GDBN} commands in Python via @code{gdb.Command},
23324 it is useful to be able to throw an exception that doesn't cause a
23325 traceback to be printed. For example, the user may have invoked the
23326 command incorrectly. Use the @code{gdb.GdbError} exception
23327 to handle this case. Example:
23331 >class HelloWorld (gdb.Command):
23332 > """Greet the whole world."""
23333 > def __init__ (self):
23334 > super (HelloWorld, self).__init__ ("hello-world", gdb.COMMAND_USER)
23335 > def invoke (self, args, from_tty):
23336 > argv = gdb.string_to_argv (args)
23337 > if len (argv) != 0:
23338 > raise gdb.GdbError ("hello-world takes no arguments")
23339 > print "Hello, World!"
23342 (gdb) hello-world 42
23343 hello-world takes no arguments
23346 @node Values From Inferior
23347 @subsubsection Values From Inferior
23348 @cindex values from inferior, with Python
23349 @cindex python, working with values from inferior
23351 @cindex @code{gdb.Value}
23352 @value{GDBN} provides values it obtains from the inferior program in
23353 an object of type @code{gdb.Value}. @value{GDBN} uses this object
23354 for its internal bookkeeping of the inferior's values, and for
23355 fetching values when necessary.
23357 Inferior values that are simple scalars can be used directly in
23358 Python expressions that are valid for the value's data type. Here's
23359 an example for an integer or floating-point value @code{some_val}:
23366 As result of this, @code{bar} will also be a @code{gdb.Value} object
23367 whose values are of the same type as those of @code{some_val}.
23369 Inferior values that are structures or instances of some class can
23370 be accessed using the Python @dfn{dictionary syntax}. For example, if
23371 @code{some_val} is a @code{gdb.Value} instance holding a structure, you
23372 can access its @code{foo} element with:
23375 bar = some_val['foo']
23378 Again, @code{bar} will also be a @code{gdb.Value} object.
23380 A @code{gdb.Value} that represents a function can be executed via
23381 inferior function call. Any arguments provided to the call must match
23382 the function's prototype, and must be provided in the order specified
23385 For example, @code{some_val} is a @code{gdb.Value} instance
23386 representing a function that takes two integers as arguments. To
23387 execute this function, call it like so:
23390 result = some_val (10,20)
23393 Any values returned from a function call will be stored as a
23396 The following attributes are provided:
23398 @defvar Value.address
23399 If this object is addressable, this read-only attribute holds a
23400 @code{gdb.Value} object representing the address. Otherwise,
23401 this attribute holds @code{None}.
23404 @cindex optimized out value in Python
23405 @defvar Value.is_optimized_out
23406 This read-only boolean attribute is true if the compiler optimized out
23407 this value, thus it is not available for fetching from the inferior.
23411 The type of this @code{gdb.Value}. The value of this attribute is a
23412 @code{gdb.Type} object (@pxref{Types In Python}).
23415 @defvar Value.dynamic_type
23416 The dynamic type of this @code{gdb.Value}. This uses C@t{++} run-time
23417 type information (@acronym{RTTI}) to determine the dynamic type of the
23418 value. If this value is of class type, it will return the class in
23419 which the value is embedded, if any. If this value is of pointer or
23420 reference to a class type, it will compute the dynamic type of the
23421 referenced object, and return a pointer or reference to that type,
23422 respectively. In all other cases, it will return the value's static
23425 Note that this feature will only work when debugging a C@t{++} program
23426 that includes @acronym{RTTI} for the object in question. Otherwise,
23427 it will just return the static type of the value as in @kbd{ptype foo}
23428 (@pxref{Symbols, ptype}).
23431 @defvar Value.is_lazy
23432 The value of this read-only boolean attribute is @code{True} if this
23433 @code{gdb.Value} has not yet been fetched from the inferior.
23434 @value{GDBN} does not fetch values until necessary, for efficiency.
23438 myval = gdb.parse_and_eval ('somevar')
23441 The value of @code{somevar} is not fetched at this time. It will be
23442 fetched when the value is needed, or when the @code{fetch_lazy}
23446 The following methods are provided:
23448 @defun Value.__init__ (@var{val})
23449 Many Python values can be converted directly to a @code{gdb.Value} via
23450 this object initializer. Specifically:
23453 @item Python boolean
23454 A Python boolean is converted to the boolean type from the current
23457 @item Python integer
23458 A Python integer is converted to the C @code{long} type for the
23459 current architecture.
23462 A Python long is converted to the C @code{long long} type for the
23463 current architecture.
23466 A Python float is converted to the C @code{double} type for the
23467 current architecture.
23469 @item Python string
23470 A Python string is converted to a target string, using the current
23473 @item @code{gdb.Value}
23474 If @code{val} is a @code{gdb.Value}, then a copy of the value is made.
23476 @item @code{gdb.LazyString}
23477 If @code{val} is a @code{gdb.LazyString} (@pxref{Lazy Strings In
23478 Python}), then the lazy string's @code{value} method is called, and
23479 its result is used.
23483 @defun Value.cast (type)
23484 Return a new instance of @code{gdb.Value} that is the result of
23485 casting this instance to the type described by @var{type}, which must
23486 be a @code{gdb.Type} object. If the cast cannot be performed for some
23487 reason, this method throws an exception.
23490 @defun Value.dereference ()
23491 For pointer data types, this method returns a new @code{gdb.Value} object
23492 whose contents is the object pointed to by the pointer. For example, if
23493 @code{foo} is a C pointer to an @code{int}, declared in your C program as
23500 then you can use the corresponding @code{gdb.Value} to access what
23501 @code{foo} points to like this:
23504 bar = foo.dereference ()
23507 The result @code{bar} will be a @code{gdb.Value} object holding the
23508 value pointed to by @code{foo}.
23510 A similar function @code{Value.referenced_value} exists which also
23511 returns @code{gdb.Value} objects corresonding to the values pointed to
23512 by pointer values (and additionally, values referenced by reference
23513 values). However, the behavior of @code{Value.dereference}
23514 differs from @code{Value.referenced_value} by the fact that the
23515 behavior of @code{Value.dereference} is identical to applying the C
23516 unary operator @code{*} on a given value. For example, consider a
23517 reference to a pointer @code{ptrref}, declared in your C@t{++} program
23521 typedef int *intptr;
23525 intptr &ptrref = ptr;
23528 Though @code{ptrref} is a reference value, one can apply the method
23529 @code{Value.dereference} to the @code{gdb.Value} object corresponding
23530 to it and obtain a @code{gdb.Value} which is identical to that
23531 corresponding to @code{val}. However, if you apply the method
23532 @code{Value.referenced_value}, the result would be a @code{gdb.Value}
23533 object identical to that corresponding to @code{ptr}.
23536 py_ptrref = gdb.parse_and_eval ("ptrref")
23537 py_val = py_ptrref.dereference ()
23538 py_ptr = py_ptrref.referenced_value ()
23541 The @code{gdb.Value} object @code{py_val} is identical to that
23542 corresponding to @code{val}, and @code{py_ptr} is identical to that
23543 corresponding to @code{ptr}. In general, @code{Value.dereference} can
23544 be applied whenever the C unary operator @code{*} can be applied
23545 to the corresponding C value. For those cases where applying both
23546 @code{Value.dereference} and @code{Value.referenced_value} is allowed,
23547 the results obtained need not be identical (as we have seen in the above
23548 example). The results are however identical when applied on
23549 @code{gdb.Value} objects corresponding to pointers (@code{gdb.Value}
23550 objects with type code @code{TYPE_CODE_PTR}) in a C/C@t{++} program.
23553 @defun Value.referenced_value ()
23554 For pointer or reference data types, this method returns a new
23555 @code{gdb.Value} object corresponding to the value referenced by the
23556 pointer/reference value. For pointer data types,
23557 @code{Value.dereference} and @code{Value.referenced_value} produce
23558 identical results. The difference between these methods is that
23559 @code{Value.dereference} cannot get the values referenced by reference
23560 values. For example, consider a reference to an @code{int}, declared
23561 in your C@t{++} program as
23569 then applying @code{Value.dereference} to the @code{gdb.Value} object
23570 corresponding to @code{ref} will result in an error, while applying
23571 @code{Value.referenced_value} will result in a @code{gdb.Value} object
23572 identical to that corresponding to @code{val}.
23575 py_ref = gdb.parse_and_eval ("ref")
23576 er_ref = py_ref.dereference () # Results in error
23577 py_val = py_ref.referenced_value () # Returns the referenced value
23580 The @code{gdb.Value} object @code{py_val} is identical to that
23581 corresponding to @code{val}.
23584 @defun Value.dynamic_cast (type)
23585 Like @code{Value.cast}, but works as if the C@t{++} @code{dynamic_cast}
23586 operator were used. Consult a C@t{++} reference for details.
23589 @defun Value.reinterpret_cast (type)
23590 Like @code{Value.cast}, but works as if the C@t{++} @code{reinterpret_cast}
23591 operator were used. Consult a C@t{++} reference for details.
23594 @defun Value.string (@r{[}encoding@r{[}, errors@r{[}, length@r{]]]})
23595 If this @code{gdb.Value} represents a string, then this method
23596 converts the contents to a Python string. Otherwise, this method will
23597 throw an exception.
23599 Strings are recognized in a language-specific way; whether a given
23600 @code{gdb.Value} represents a string is determined by the current
23603 For C-like languages, a value is a string if it is a pointer to or an
23604 array of characters or ints. The string is assumed to be terminated
23605 by a zero of the appropriate width. However if the optional length
23606 argument is given, the string will be converted to that given length,
23607 ignoring any embedded zeros that the string may contain.
23609 If the optional @var{encoding} argument is given, it must be a string
23610 naming the encoding of the string in the @code{gdb.Value}, such as
23611 @code{"ascii"}, @code{"iso-8859-6"} or @code{"utf-8"}. It accepts
23612 the same encodings as the corresponding argument to Python's
23613 @code{string.decode} method, and the Python codec machinery will be used
23614 to convert the string. If @var{encoding} is not given, or if
23615 @var{encoding} is the empty string, then either the @code{target-charset}
23616 (@pxref{Character Sets}) will be used, or a language-specific encoding
23617 will be used, if the current language is able to supply one.
23619 The optional @var{errors} argument is the same as the corresponding
23620 argument to Python's @code{string.decode} method.
23622 If the optional @var{length} argument is given, the string will be
23623 fetched and converted to the given length.
23626 @defun Value.lazy_string (@r{[}encoding @r{[}, length@r{]]})
23627 If this @code{gdb.Value} represents a string, then this method
23628 converts the contents to a @code{gdb.LazyString} (@pxref{Lazy Strings
23629 In Python}). Otherwise, this method will throw an exception.
23631 If the optional @var{encoding} argument is given, it must be a string
23632 naming the encoding of the @code{gdb.LazyString}. Some examples are:
23633 @samp{ascii}, @samp{iso-8859-6} or @samp{utf-8}. If the
23634 @var{encoding} argument is an encoding that @value{GDBN} does
23635 recognize, @value{GDBN} will raise an error.
23637 When a lazy string is printed, the @value{GDBN} encoding machinery is
23638 used to convert the string during printing. If the optional
23639 @var{encoding} argument is not provided, or is an empty string,
23640 @value{GDBN} will automatically select the encoding most suitable for
23641 the string type. For further information on encoding in @value{GDBN}
23642 please see @ref{Character Sets}.
23644 If the optional @var{length} argument is given, the string will be
23645 fetched and encoded to the length of characters specified. If
23646 the @var{length} argument is not provided, the string will be fetched
23647 and encoded until a null of appropriate width is found.
23650 @defun Value.fetch_lazy ()
23651 If the @code{gdb.Value} object is currently a lazy value
23652 (@code{gdb.Value.is_lazy} is @code{True}), then the value is
23653 fetched from the inferior. Any errors that occur in the process
23654 will produce a Python exception.
23656 If the @code{gdb.Value} object is not a lazy value, this method
23659 This method does not return a value.
23663 @node Types In Python
23664 @subsubsection Types In Python
23665 @cindex types in Python
23666 @cindex Python, working with types
23669 @value{GDBN} represents types from the inferior using the class
23672 The following type-related functions are available in the @code{gdb}
23675 @findex gdb.lookup_type
23676 @defun gdb.lookup_type (name @r{[}, block@r{]})
23677 This function looks up a type by name. @var{name} is the name of the
23678 type to look up. It must be a string.
23680 If @var{block} is given, then @var{name} is looked up in that scope.
23681 Otherwise, it is searched for globally.
23683 Ordinarily, this function will return an instance of @code{gdb.Type}.
23684 If the named type cannot be found, it will throw an exception.
23687 If the type is a structure or class type, or an enum type, the fields
23688 of that type can be accessed using the Python @dfn{dictionary syntax}.
23689 For example, if @code{some_type} is a @code{gdb.Type} instance holding
23690 a structure type, you can access its @code{foo} field with:
23693 bar = some_type['foo']
23696 @code{bar} will be a @code{gdb.Field} object; see below under the
23697 description of the @code{Type.fields} method for a description of the
23698 @code{gdb.Field} class.
23700 An instance of @code{Type} has the following attributes:
23703 The type code for this type. The type code will be one of the
23704 @code{TYPE_CODE_} constants defined below.
23707 @defvar Type.sizeof
23708 The size of this type, in target @code{char} units. Usually, a
23709 target's @code{char} type will be an 8-bit byte. However, on some
23710 unusual platforms, this type may have a different size.
23714 The tag name for this type. The tag name is the name after
23715 @code{struct}, @code{union}, or @code{enum} in C and C@t{++}; not all
23716 languages have this concept. If this type has no tag name, then
23717 @code{None} is returned.
23720 The following methods are provided:
23722 @defun Type.fields ()
23723 For structure and union types, this method returns the fields. Range
23724 types have two fields, the minimum and maximum values. Enum types
23725 have one field per enum constant. Function and method types have one
23726 field per parameter. The base types of C@t{++} classes are also
23727 represented as fields. If the type has no fields, or does not fit
23728 into one of these categories, an empty sequence will be returned.
23730 Each field is a @code{gdb.Field} object, with some pre-defined attributes:
23733 This attribute is not available for @code{static} fields (as in
23734 C@t{++} or Java). For non-@code{static} fields, the value is the bit
23735 position of the field. For @code{enum} fields, the value is the
23736 enumeration member's integer representation.
23739 The name of the field, or @code{None} for anonymous fields.
23742 This is @code{True} if the field is artificial, usually meaning that
23743 it was provided by the compiler and not the user. This attribute is
23744 always provided, and is @code{False} if the field is not artificial.
23746 @item is_base_class
23747 This is @code{True} if the field represents a base class of a C@t{++}
23748 structure. This attribute is always provided, and is @code{False}
23749 if the field is not a base class of the type that is the argument of
23750 @code{fields}, or if that type was not a C@t{++} class.
23753 If the field is packed, or is a bitfield, then this will have a
23754 non-zero value, which is the size of the field in bits. Otherwise,
23755 this will be zero; in this case the field's size is given by its type.
23758 The type of the field. This is usually an instance of @code{Type},
23759 but it can be @code{None} in some situations.
23763 @defun Type.array (@var{n1} @r{[}, @var{n2}@r{]})
23764 Return a new @code{gdb.Type} object which represents an array of this
23765 type. If one argument is given, it is the inclusive upper bound of
23766 the array; in this case the lower bound is zero. If two arguments are
23767 given, the first argument is the lower bound of the array, and the
23768 second argument is the upper bound of the array. An array's length
23769 must not be negative, but the bounds can be.
23772 @defun Type.vector (@var{n1} @r{[}, @var{n2}@r{]})
23773 Return a new @code{gdb.Type} object which represents a vector of this
23774 type. If one argument is given, it is the inclusive upper bound of
23775 the vector; in this case the lower bound is zero. If two arguments are
23776 given, the first argument is the lower bound of the vector, and the
23777 second argument is the upper bound of the vector. A vector's length
23778 must not be negative, but the bounds can be.
23780 The difference between an @code{array} and a @code{vector} is that
23781 arrays behave like in C: when used in expressions they decay to a pointer
23782 to the first element whereas vectors are treated as first class values.
23785 @defun Type.const ()
23786 Return a new @code{gdb.Type} object which represents a
23787 @code{const}-qualified variant of this type.
23790 @defun Type.volatile ()
23791 Return a new @code{gdb.Type} object which represents a
23792 @code{volatile}-qualified variant of this type.
23795 @defun Type.unqualified ()
23796 Return a new @code{gdb.Type} object which represents an unqualified
23797 variant of this type. That is, the result is neither @code{const} nor
23801 @defun Type.range ()
23802 Return a Python @code{Tuple} object that contains two elements: the
23803 low bound of the argument type and the high bound of that type. If
23804 the type does not have a range, @value{GDBN} will raise a
23805 @code{gdb.error} exception (@pxref{Exception Handling}).
23808 @defun Type.reference ()
23809 Return a new @code{gdb.Type} object which represents a reference to this
23813 @defun Type.pointer ()
23814 Return a new @code{gdb.Type} object which represents a pointer to this
23818 @defun Type.strip_typedefs ()
23819 Return a new @code{gdb.Type} that represents the real type,
23820 after removing all layers of typedefs.
23823 @defun Type.target ()
23824 Return a new @code{gdb.Type} object which represents the target type
23827 For a pointer type, the target type is the type of the pointed-to
23828 object. For an array type (meaning C-like arrays), the target type is
23829 the type of the elements of the array. For a function or method type,
23830 the target type is the type of the return value. For a complex type,
23831 the target type is the type of the elements. For a typedef, the
23832 target type is the aliased type.
23834 If the type does not have a target, this method will throw an
23838 @defun Type.template_argument (n @r{[}, block@r{]})
23839 If this @code{gdb.Type} is an instantiation of a template, this will
23840 return a new @code{gdb.Type} which represents the type of the
23841 @var{n}th template argument.
23843 If this @code{gdb.Type} is not a template type, this will throw an
23844 exception. Ordinarily, only C@t{++} code will have template types.
23846 If @var{block} is given, then @var{name} is looked up in that scope.
23847 Otherwise, it is searched for globally.
23851 Each type has a code, which indicates what category this type falls
23852 into. The available type categories are represented by constants
23853 defined in the @code{gdb} module:
23856 @findex TYPE_CODE_PTR
23857 @findex gdb.TYPE_CODE_PTR
23858 @item gdb.TYPE_CODE_PTR
23859 The type is a pointer.
23861 @findex TYPE_CODE_ARRAY
23862 @findex gdb.TYPE_CODE_ARRAY
23863 @item gdb.TYPE_CODE_ARRAY
23864 The type is an array.
23866 @findex TYPE_CODE_STRUCT
23867 @findex gdb.TYPE_CODE_STRUCT
23868 @item gdb.TYPE_CODE_STRUCT
23869 The type is a structure.
23871 @findex TYPE_CODE_UNION
23872 @findex gdb.TYPE_CODE_UNION
23873 @item gdb.TYPE_CODE_UNION
23874 The type is a union.
23876 @findex TYPE_CODE_ENUM
23877 @findex gdb.TYPE_CODE_ENUM
23878 @item gdb.TYPE_CODE_ENUM
23879 The type is an enum.
23881 @findex TYPE_CODE_FLAGS
23882 @findex gdb.TYPE_CODE_FLAGS
23883 @item gdb.TYPE_CODE_FLAGS
23884 A bit flags type, used for things such as status registers.
23886 @findex TYPE_CODE_FUNC
23887 @findex gdb.TYPE_CODE_FUNC
23888 @item gdb.TYPE_CODE_FUNC
23889 The type is a function.
23891 @findex TYPE_CODE_INT
23892 @findex gdb.TYPE_CODE_INT
23893 @item gdb.TYPE_CODE_INT
23894 The type is an integer type.
23896 @findex TYPE_CODE_FLT
23897 @findex gdb.TYPE_CODE_FLT
23898 @item gdb.TYPE_CODE_FLT
23899 A floating point type.
23901 @findex TYPE_CODE_VOID
23902 @findex gdb.TYPE_CODE_VOID
23903 @item gdb.TYPE_CODE_VOID
23904 The special type @code{void}.
23906 @findex TYPE_CODE_SET
23907 @findex gdb.TYPE_CODE_SET
23908 @item gdb.TYPE_CODE_SET
23911 @findex TYPE_CODE_RANGE
23912 @findex gdb.TYPE_CODE_RANGE
23913 @item gdb.TYPE_CODE_RANGE
23914 A range type, that is, an integer type with bounds.
23916 @findex TYPE_CODE_STRING
23917 @findex gdb.TYPE_CODE_STRING
23918 @item gdb.TYPE_CODE_STRING
23919 A string type. Note that this is only used for certain languages with
23920 language-defined string types; C strings are not represented this way.
23922 @findex TYPE_CODE_BITSTRING
23923 @findex gdb.TYPE_CODE_BITSTRING
23924 @item gdb.TYPE_CODE_BITSTRING
23925 A string of bits. It is deprecated.
23927 @findex TYPE_CODE_ERROR
23928 @findex gdb.TYPE_CODE_ERROR
23929 @item gdb.TYPE_CODE_ERROR
23930 An unknown or erroneous type.
23932 @findex TYPE_CODE_METHOD
23933 @findex gdb.TYPE_CODE_METHOD
23934 @item gdb.TYPE_CODE_METHOD
23935 A method type, as found in C@t{++} or Java.
23937 @findex TYPE_CODE_METHODPTR
23938 @findex gdb.TYPE_CODE_METHODPTR
23939 @item gdb.TYPE_CODE_METHODPTR
23940 A pointer-to-member-function.
23942 @findex TYPE_CODE_MEMBERPTR
23943 @findex gdb.TYPE_CODE_MEMBERPTR
23944 @item gdb.TYPE_CODE_MEMBERPTR
23945 A pointer-to-member.
23947 @findex TYPE_CODE_REF
23948 @findex gdb.TYPE_CODE_REF
23949 @item gdb.TYPE_CODE_REF
23952 @findex TYPE_CODE_CHAR
23953 @findex gdb.TYPE_CODE_CHAR
23954 @item gdb.TYPE_CODE_CHAR
23957 @findex TYPE_CODE_BOOL
23958 @findex gdb.TYPE_CODE_BOOL
23959 @item gdb.TYPE_CODE_BOOL
23962 @findex TYPE_CODE_COMPLEX
23963 @findex gdb.TYPE_CODE_COMPLEX
23964 @item gdb.TYPE_CODE_COMPLEX
23965 A complex float type.
23967 @findex TYPE_CODE_TYPEDEF
23968 @findex gdb.TYPE_CODE_TYPEDEF
23969 @item gdb.TYPE_CODE_TYPEDEF
23970 A typedef to some other type.
23972 @findex TYPE_CODE_NAMESPACE
23973 @findex gdb.TYPE_CODE_NAMESPACE
23974 @item gdb.TYPE_CODE_NAMESPACE
23975 A C@t{++} namespace.
23977 @findex TYPE_CODE_DECFLOAT
23978 @findex gdb.TYPE_CODE_DECFLOAT
23979 @item gdb.TYPE_CODE_DECFLOAT
23980 A decimal floating point type.
23982 @findex TYPE_CODE_INTERNAL_FUNCTION
23983 @findex gdb.TYPE_CODE_INTERNAL_FUNCTION
23984 @item gdb.TYPE_CODE_INTERNAL_FUNCTION
23985 A function internal to @value{GDBN}. This is the type used to represent
23986 convenience functions.
23989 Further support for types is provided in the @code{gdb.types}
23990 Python module (@pxref{gdb.types}).
23992 @node Pretty Printing API
23993 @subsubsection Pretty Printing API
23995 An example output is provided (@pxref{Pretty Printing}).
23997 A pretty-printer is just an object that holds a value and implements a
23998 specific interface, defined here.
24000 @defun pretty_printer.children (self)
24001 @value{GDBN} will call this method on a pretty-printer to compute the
24002 children of the pretty-printer's value.
24004 This method must return an object conforming to the Python iterator
24005 protocol. Each item returned by the iterator must be a tuple holding
24006 two elements. The first element is the ``name'' of the child; the
24007 second element is the child's value. The value can be any Python
24008 object which is convertible to a @value{GDBN} value.
24010 This method is optional. If it does not exist, @value{GDBN} will act
24011 as though the value has no children.
24014 @defun pretty_printer.display_hint (self)
24015 The CLI may call this method and use its result to change the
24016 formatting of a value. The result will also be supplied to an MI
24017 consumer as a @samp{displayhint} attribute of the variable being
24020 This method is optional. If it does exist, this method must return a
24023 Some display hints are predefined by @value{GDBN}:
24027 Indicate that the object being printed is ``array-like''. The CLI
24028 uses this to respect parameters such as @code{set print elements} and
24029 @code{set print array}.
24032 Indicate that the object being printed is ``map-like'', and that the
24033 children of this value can be assumed to alternate between keys and
24037 Indicate that the object being printed is ``string-like''. If the
24038 printer's @code{to_string} method returns a Python string of some
24039 kind, then @value{GDBN} will call its internal language-specific
24040 string-printing function to format the string. For the CLI this means
24041 adding quotation marks, possibly escaping some characters, respecting
24042 @code{set print elements}, and the like.
24046 @defun pretty_printer.to_string (self)
24047 @value{GDBN} will call this method to display the string
24048 representation of the value passed to the object's constructor.
24050 When printing from the CLI, if the @code{to_string} method exists,
24051 then @value{GDBN} will prepend its result to the values returned by
24052 @code{children}. Exactly how this formatting is done is dependent on
24053 the display hint, and may change as more hints are added. Also,
24054 depending on the print settings (@pxref{Print Settings}), the CLI may
24055 print just the result of @code{to_string} in a stack trace, omitting
24056 the result of @code{children}.
24058 If this method returns a string, it is printed verbatim.
24060 Otherwise, if this method returns an instance of @code{gdb.Value},
24061 then @value{GDBN} prints this value. This may result in a call to
24062 another pretty-printer.
24064 If instead the method returns a Python value which is convertible to a
24065 @code{gdb.Value}, then @value{GDBN} performs the conversion and prints
24066 the resulting value. Again, this may result in a call to another
24067 pretty-printer. Python scalars (integers, floats, and booleans) and
24068 strings are convertible to @code{gdb.Value}; other types are not.
24070 Finally, if this method returns @code{None} then no further operations
24071 are peformed in this method and nothing is printed.
24073 If the result is not one of these types, an exception is raised.
24076 @value{GDBN} provides a function which can be used to look up the
24077 default pretty-printer for a @code{gdb.Value}:
24079 @findex gdb.default_visualizer
24080 @defun gdb.default_visualizer (value)
24081 This function takes a @code{gdb.Value} object as an argument. If a
24082 pretty-printer for this value exists, then it is returned. If no such
24083 printer exists, then this returns @code{None}.
24086 @node Selecting Pretty-Printers
24087 @subsubsection Selecting Pretty-Printers
24089 The Python list @code{gdb.pretty_printers} contains an array of
24090 functions or callable objects that have been registered via addition
24091 as a pretty-printer. Printers in this list are called @code{global}
24092 printers, they're available when debugging all inferiors.
24093 Each @code{gdb.Progspace} contains a @code{pretty_printers} attribute.
24094 Each @code{gdb.Objfile} also contains a @code{pretty_printers}
24097 Each function on these lists is passed a single @code{gdb.Value}
24098 argument and should return a pretty-printer object conforming to the
24099 interface definition above (@pxref{Pretty Printing API}). If a function
24100 cannot create a pretty-printer for the value, it should return
24103 @value{GDBN} first checks the @code{pretty_printers} attribute of each
24104 @code{gdb.Objfile} in the current program space and iteratively calls
24105 each enabled lookup routine in the list for that @code{gdb.Objfile}
24106 until it receives a pretty-printer object.
24107 If no pretty-printer is found in the objfile lists, @value{GDBN} then
24108 searches the pretty-printer list of the current program space,
24109 calling each enabled function until an object is returned.
24110 After these lists have been exhausted, it tries the global
24111 @code{gdb.pretty_printers} list, again calling each enabled function until an
24112 object is returned.
24114 The order in which the objfiles are searched is not specified. For a
24115 given list, functions are always invoked from the head of the list,
24116 and iterated over sequentially until the end of the list, or a printer
24117 object is returned.
24119 For various reasons a pretty-printer may not work.
24120 For example, the underlying data structure may have changed and
24121 the pretty-printer is out of date.
24123 The consequences of a broken pretty-printer are severe enough that
24124 @value{GDBN} provides support for enabling and disabling individual
24125 printers. For example, if @code{print frame-arguments} is on,
24126 a backtrace can become highly illegible if any argument is printed
24127 with a broken printer.
24129 Pretty-printers are enabled and disabled by attaching an @code{enabled}
24130 attribute to the registered function or callable object. If this attribute
24131 is present and its value is @code{False}, the printer is disabled, otherwise
24132 the printer is enabled.
24134 @node Writing a Pretty-Printer
24135 @subsubsection Writing a Pretty-Printer
24136 @cindex writing a pretty-printer
24138 A pretty-printer consists of two parts: a lookup function to detect
24139 if the type is supported, and the printer itself.
24141 Here is an example showing how a @code{std::string} printer might be
24142 written. @xref{Pretty Printing API}, for details on the API this class
24146 class StdStringPrinter(object):
24147 "Print a std::string"
24149 def __init__(self, val):
24152 def to_string(self):
24153 return self.val['_M_dataplus']['_M_p']
24155 def display_hint(self):
24159 And here is an example showing how a lookup function for the printer
24160 example above might be written.
24163 def str_lookup_function(val):
24164 lookup_tag = val.type.tag
24165 if lookup_tag == None:
24167 regex = re.compile("^std::basic_string<char,.*>$")
24168 if regex.match(lookup_tag):
24169 return StdStringPrinter(val)
24173 The example lookup function extracts the value's type, and attempts to
24174 match it to a type that it can pretty-print. If it is a type the
24175 printer can pretty-print, it will return a printer object. If not, it
24176 returns @code{None}.
24178 We recommend that you put your core pretty-printers into a Python
24179 package. If your pretty-printers are for use with a library, we
24180 further recommend embedding a version number into the package name.
24181 This practice will enable @value{GDBN} to load multiple versions of
24182 your pretty-printers at the same time, because they will have
24185 You should write auto-loaded code (@pxref{Python Auto-loading}) such that it
24186 can be evaluated multiple times without changing its meaning. An
24187 ideal auto-load file will consist solely of @code{import}s of your
24188 printer modules, followed by a call to a register pretty-printers with
24189 the current objfile.
24191 Taken as a whole, this approach will scale nicely to multiple
24192 inferiors, each potentially using a different library version.
24193 Embedding a version number in the Python package name will ensure that
24194 @value{GDBN} is able to load both sets of printers simultaneously.
24195 Then, because the search for pretty-printers is done by objfile, and
24196 because your auto-loaded code took care to register your library's
24197 printers with a specific objfile, @value{GDBN} will find the correct
24198 printers for the specific version of the library used by each
24201 To continue the @code{std::string} example (@pxref{Pretty Printing API}),
24202 this code might appear in @code{gdb.libstdcxx.v6}:
24205 def register_printers(objfile):
24206 objfile.pretty_printers.append(str_lookup_function)
24210 And then the corresponding contents of the auto-load file would be:
24213 import gdb.libstdcxx.v6
24214 gdb.libstdcxx.v6.register_printers(gdb.current_objfile())
24217 The previous example illustrates a basic pretty-printer.
24218 There are a few things that can be improved on.
24219 The printer doesn't have a name, making it hard to identify in a
24220 list of installed printers. The lookup function has a name, but
24221 lookup functions can have arbitrary, even identical, names.
24223 Second, the printer only handles one type, whereas a library typically has
24224 several types. One could install a lookup function for each desired type
24225 in the library, but one could also have a single lookup function recognize
24226 several types. The latter is the conventional way this is handled.
24227 If a pretty-printer can handle multiple data types, then its
24228 @dfn{subprinters} are the printers for the individual data types.
24230 The @code{gdb.printing} module provides a formal way of solving these
24231 problems (@pxref{gdb.printing}).
24232 Here is another example that handles multiple types.
24234 These are the types we are going to pretty-print:
24237 struct foo @{ int a, b; @};
24238 struct bar @{ struct foo x, y; @};
24241 Here are the printers:
24245 """Print a foo object."""
24247 def __init__(self, val):
24250 def to_string(self):
24251 return ("a=<" + str(self.val["a"]) +
24252 "> b=<" + str(self.val["b"]) + ">")
24255 """Print a bar object."""
24257 def __init__(self, val):
24260 def to_string(self):
24261 return ("x=<" + str(self.val["x"]) +
24262 "> y=<" + str(self.val["y"]) + ">")
24265 This example doesn't need a lookup function, that is handled by the
24266 @code{gdb.printing} module. Instead a function is provided to build up
24267 the object that handles the lookup.
24270 import gdb.printing
24272 def build_pretty_printer():
24273 pp = gdb.printing.RegexpCollectionPrettyPrinter(
24275 pp.add_printer('foo', '^foo$', fooPrinter)
24276 pp.add_printer('bar', '^bar$', barPrinter)
24280 And here is the autoload support:
24283 import gdb.printing
24285 gdb.printing.register_pretty_printer(
24286 gdb.current_objfile(),
24287 my_library.build_pretty_printer())
24290 Finally, when this printer is loaded into @value{GDBN}, here is the
24291 corresponding output of @samp{info pretty-printer}:
24294 (gdb) info pretty-printer
24301 @node Type Printing API
24302 @subsubsection Type Printing API
24303 @cindex type printing API for Python
24305 @value{GDBN} provides a way for Python code to customize type display.
24306 This is mainly useful for substituting canonical typedef names for
24309 @cindex type printer
24310 A @dfn{type printer} is just a Python object conforming to a certain
24311 protocol. A simple base class implementing the protocol is provided;
24312 see @ref{gdb.types}. A type printer must supply at least:
24314 @defivar type_printer enabled
24315 A boolean which is True if the printer is enabled, and False
24316 otherwise. This is manipulated by the @code{enable type-printer}
24317 and @code{disable type-printer} commands.
24320 @defivar type_printer name
24321 The name of the type printer. This must be a string. This is used by
24322 the @code{enable type-printer} and @code{disable type-printer}
24326 @defmethod type_printer instantiate (self)
24327 This is called by @value{GDBN} at the start of type-printing. It is
24328 only called if the type printer is enabled. This method must return a
24329 new object that supplies a @code{recognize} method, as described below.
24333 When displaying a type, say via the @code{ptype} command, @value{GDBN}
24334 will compute a list of type recognizers. This is done by iterating
24335 first over the per-objfile type printers (@pxref{Objfiles In Python}),
24336 followed by the per-progspace type printers (@pxref{Progspaces In
24337 Python}), and finally the global type printers.
24339 @value{GDBN} will call the @code{instantiate} method of each enabled
24340 type printer. If this method returns @code{None}, then the result is
24341 ignored; otherwise, it is appended to the list of recognizers.
24343 Then, when @value{GDBN} is going to display a type name, it iterates
24344 over the list of recognizers. For each one, it calls the recognition
24345 function, stopping if the function returns a non-@code{None} value.
24346 The recognition function is defined as:
24348 @defmethod type_recognizer recognize (self, type)
24349 If @var{type} is not recognized, return @code{None}. Otherwise,
24350 return a string which is to be printed as the name of @var{type}.
24351 @var{type} will be an instance of @code{gdb.Type} (@pxref{Types In
24355 @value{GDBN} uses this two-pass approach so that type printers can
24356 efficiently cache information without holding on to it too long. For
24357 example, it can be convenient to look up type information in a type
24358 printer and hold it for a recognizer's lifetime; if a single pass were
24359 done then type printers would have to make use of the event system in
24360 order to avoid holding information that could become stale as the
24363 @node Inferiors In Python
24364 @subsubsection Inferiors In Python
24365 @cindex inferiors in Python
24367 @findex gdb.Inferior
24368 Programs which are being run under @value{GDBN} are called inferiors
24369 (@pxref{Inferiors and Programs}). Python scripts can access
24370 information about and manipulate inferiors controlled by @value{GDBN}
24371 via objects of the @code{gdb.Inferior} class.
24373 The following inferior-related functions are available in the @code{gdb}
24376 @defun gdb.inferiors ()
24377 Return a tuple containing all inferior objects.
24380 @defun gdb.selected_inferior ()
24381 Return an object representing the current inferior.
24384 A @code{gdb.Inferior} object has the following attributes:
24386 @defvar Inferior.num
24387 ID of inferior, as assigned by GDB.
24390 @defvar Inferior.pid
24391 Process ID of the inferior, as assigned by the underlying operating
24395 @defvar Inferior.was_attached
24396 Boolean signaling whether the inferior was created using `attach', or
24397 started by @value{GDBN} itself.
24400 A @code{gdb.Inferior} object has the following methods:
24402 @defun Inferior.is_valid ()
24403 Returns @code{True} if the @code{gdb.Inferior} object is valid,
24404 @code{False} if not. A @code{gdb.Inferior} object will become invalid
24405 if the inferior no longer exists within @value{GDBN}. All other
24406 @code{gdb.Inferior} methods will throw an exception if it is invalid
24407 at the time the method is called.
24410 @defun Inferior.threads ()
24411 This method returns a tuple holding all the threads which are valid
24412 when it is called. If there are no valid threads, the method will
24413 return an empty tuple.
24416 @findex Inferior.read_memory
24417 @defun Inferior.read_memory (address, length)
24418 Read @var{length} bytes of memory from the inferior, starting at
24419 @var{address}. Returns a buffer object, which behaves much like an array
24420 or a string. It can be modified and given to the
24421 @code{Inferior.write_memory} function. In @code{Python} 3, the return
24422 value is a @code{memoryview} object.
24425 @findex Inferior.write_memory
24426 @defun Inferior.write_memory (address, buffer @r{[}, length@r{]})
24427 Write the contents of @var{buffer} to the inferior, starting at
24428 @var{address}. The @var{buffer} parameter must be a Python object
24429 which supports the buffer protocol, i.e., a string, an array or the
24430 object returned from @code{Inferior.read_memory}. If given, @var{length}
24431 determines the number of bytes from @var{buffer} to be written.
24434 @findex gdb.search_memory
24435 @defun Inferior.search_memory (address, length, pattern)
24436 Search a region of the inferior memory starting at @var{address} with
24437 the given @var{length} using the search pattern supplied in
24438 @var{pattern}. The @var{pattern} parameter must be a Python object
24439 which supports the buffer protocol, i.e., a string, an array or the
24440 object returned from @code{gdb.read_memory}. Returns a Python @code{Long}
24441 containing the address where the pattern was found, or @code{None} if
24442 the pattern could not be found.
24445 @node Events In Python
24446 @subsubsection Events In Python
24447 @cindex inferior events in Python
24449 @value{GDBN} provides a general event facility so that Python code can be
24450 notified of various state changes, particularly changes that occur in
24453 An @dfn{event} is just an object that describes some state change. The
24454 type of the object and its attributes will vary depending on the details
24455 of the change. All the existing events are described below.
24457 In order to be notified of an event, you must register an event handler
24458 with an @dfn{event registry}. An event registry is an object in the
24459 @code{gdb.events} module which dispatches particular events. A registry
24460 provides methods to register and unregister event handlers:
24462 @defun EventRegistry.connect (object)
24463 Add the given callable @var{object} to the registry. This object will be
24464 called when an event corresponding to this registry occurs.
24467 @defun EventRegistry.disconnect (object)
24468 Remove the given @var{object} from the registry. Once removed, the object
24469 will no longer receive notifications of events.
24472 Here is an example:
24475 def exit_handler (event):
24476 print "event type: exit"
24477 print "exit code: %d" % (event.exit_code)
24479 gdb.events.exited.connect (exit_handler)
24482 In the above example we connect our handler @code{exit_handler} to the
24483 registry @code{events.exited}. Once connected, @code{exit_handler} gets
24484 called when the inferior exits. The argument @dfn{event} in this example is
24485 of type @code{gdb.ExitedEvent}. As you can see in the example the
24486 @code{ExitedEvent} object has an attribute which indicates the exit code of
24489 The following is a listing of the event registries that are available and
24490 details of the events they emit:
24495 Emits @code{gdb.ThreadEvent}.
24497 Some events can be thread specific when @value{GDBN} is running in non-stop
24498 mode. When represented in Python, these events all extend
24499 @code{gdb.ThreadEvent}. Note, this event is not emitted directly; instead,
24500 events which are emitted by this or other modules might extend this event.
24501 Examples of these events are @code{gdb.BreakpointEvent} and
24502 @code{gdb.ContinueEvent}.
24504 @defvar ThreadEvent.inferior_thread
24505 In non-stop mode this attribute will be set to the specific thread which was
24506 involved in the emitted event. Otherwise, it will be set to @code{None}.
24509 Emits @code{gdb.ContinueEvent} which extends @code{gdb.ThreadEvent}.
24511 This event indicates that the inferior has been continued after a stop. For
24512 inherited attribute refer to @code{gdb.ThreadEvent} above.
24514 @item events.exited
24515 Emits @code{events.ExitedEvent} which indicates that the inferior has exited.
24516 @code{events.ExitedEvent} has two attributes:
24517 @defvar ExitedEvent.exit_code
24518 An integer representing the exit code, if available, which the inferior
24519 has returned. (The exit code could be unavailable if, for example,
24520 @value{GDBN} detaches from the inferior.) If the exit code is unavailable,
24521 the attribute does not exist.
24523 @defvar ExitedEvent inferior
24524 A reference to the inferior which triggered the @code{exited} event.
24528 Emits @code{gdb.StopEvent} which extends @code{gdb.ThreadEvent}.
24530 Indicates that the inferior has stopped. All events emitted by this registry
24531 extend StopEvent. As a child of @code{gdb.ThreadEvent}, @code{gdb.StopEvent}
24532 will indicate the stopped thread when @value{GDBN} is running in non-stop
24533 mode. Refer to @code{gdb.ThreadEvent} above for more details.
24535 Emits @code{gdb.SignalEvent} which extends @code{gdb.StopEvent}.
24537 This event indicates that the inferior or one of its threads has received as
24538 signal. @code{gdb.SignalEvent} has the following attributes:
24540 @defvar SignalEvent.stop_signal
24541 A string representing the signal received by the inferior. A list of possible
24542 signal values can be obtained by running the command @code{info signals} in
24543 the @value{GDBN} command prompt.
24546 Also emits @code{gdb.BreakpointEvent} which extends @code{gdb.StopEvent}.
24548 @code{gdb.BreakpointEvent} event indicates that one or more breakpoints have
24549 been hit, and has the following attributes:
24551 @defvar BreakpointEvent.breakpoints
24552 A sequence containing references to all the breakpoints (type
24553 @code{gdb.Breakpoint}) that were hit.
24554 @xref{Breakpoints In Python}, for details of the @code{gdb.Breakpoint} object.
24556 @defvar BreakpointEvent.breakpoint
24557 A reference to the first breakpoint that was hit.
24558 This function is maintained for backward compatibility and is now deprecated
24559 in favor of the @code{gdb.BreakpointEvent.breakpoints} attribute.
24562 @item events.new_objfile
24563 Emits @code{gdb.NewObjFileEvent} which indicates that a new object file has
24564 been loaded by @value{GDBN}. @code{gdb.NewObjFileEvent} has one attribute:
24566 @defvar NewObjFileEvent.new_objfile
24567 A reference to the object file (@code{gdb.Objfile}) which has been loaded.
24568 @xref{Objfiles In Python}, for details of the @code{gdb.Objfile} object.
24573 @node Threads In Python
24574 @subsubsection Threads In Python
24575 @cindex threads in python
24577 @findex gdb.InferiorThread
24578 Python scripts can access information about, and manipulate inferior threads
24579 controlled by @value{GDBN}, via objects of the @code{gdb.InferiorThread} class.
24581 The following thread-related functions are available in the @code{gdb}
24584 @findex gdb.selected_thread
24585 @defun gdb.selected_thread ()
24586 This function returns the thread object for the selected thread. If there
24587 is no selected thread, this will return @code{None}.
24590 A @code{gdb.InferiorThread} object has the following attributes:
24592 @defvar InferiorThread.name
24593 The name of the thread. If the user specified a name using
24594 @code{thread name}, then this returns that name. Otherwise, if an
24595 OS-supplied name is available, then it is returned. Otherwise, this
24596 returns @code{None}.
24598 This attribute can be assigned to. The new value must be a string
24599 object, which sets the new name, or @code{None}, which removes any
24600 user-specified thread name.
24603 @defvar InferiorThread.num
24604 ID of the thread, as assigned by GDB.
24607 @defvar InferiorThread.ptid
24608 ID of the thread, as assigned by the operating system. This attribute is a
24609 tuple containing three integers. The first is the Process ID (PID); the second
24610 is the Lightweight Process ID (LWPID), and the third is the Thread ID (TID).
24611 Either the LWPID or TID may be 0, which indicates that the operating system
24612 does not use that identifier.
24615 A @code{gdb.InferiorThread} object has the following methods:
24617 @defun InferiorThread.is_valid ()
24618 Returns @code{True} if the @code{gdb.InferiorThread} object is valid,
24619 @code{False} if not. A @code{gdb.InferiorThread} object will become
24620 invalid if the thread exits, or the inferior that the thread belongs
24621 is deleted. All other @code{gdb.InferiorThread} methods will throw an
24622 exception if it is invalid at the time the method is called.
24625 @defun InferiorThread.switch ()
24626 This changes @value{GDBN}'s currently selected thread to the one represented
24630 @defun InferiorThread.is_stopped ()
24631 Return a Boolean indicating whether the thread is stopped.
24634 @defun InferiorThread.is_running ()
24635 Return a Boolean indicating whether the thread is running.
24638 @defun InferiorThread.is_exited ()
24639 Return a Boolean indicating whether the thread is exited.
24642 @node Commands In Python
24643 @subsubsection Commands In Python
24645 @cindex commands in python
24646 @cindex python commands
24647 You can implement new @value{GDBN} CLI commands in Python. A CLI
24648 command is implemented using an instance of the @code{gdb.Command}
24649 class, most commonly using a subclass.
24651 @defun Command.__init__ (name, @var{command_class} @r{[}, @var{completer_class} @r{[}, @var{prefix}@r{]]})
24652 The object initializer for @code{Command} registers the new command
24653 with @value{GDBN}. This initializer is normally invoked from the
24654 subclass' own @code{__init__} method.
24656 @var{name} is the name of the command. If @var{name} consists of
24657 multiple words, then the initial words are looked for as prefix
24658 commands. In this case, if one of the prefix commands does not exist,
24659 an exception is raised.
24661 There is no support for multi-line commands.
24663 @var{command_class} should be one of the @samp{COMMAND_} constants
24664 defined below. This argument tells @value{GDBN} how to categorize the
24665 new command in the help system.
24667 @var{completer_class} is an optional argument. If given, it should be
24668 one of the @samp{COMPLETE_} constants defined below. This argument
24669 tells @value{GDBN} how to perform completion for this command. If not
24670 given, @value{GDBN} will attempt to complete using the object's
24671 @code{complete} method (see below); if no such method is found, an
24672 error will occur when completion is attempted.
24674 @var{prefix} is an optional argument. If @code{True}, then the new
24675 command is a prefix command; sub-commands of this command may be
24678 The help text for the new command is taken from the Python
24679 documentation string for the command's class, if there is one. If no
24680 documentation string is provided, the default value ``This command is
24681 not documented.'' is used.
24684 @cindex don't repeat Python command
24685 @defun Command.dont_repeat ()
24686 By default, a @value{GDBN} command is repeated when the user enters a
24687 blank line at the command prompt. A command can suppress this
24688 behavior by invoking the @code{dont_repeat} method. This is similar
24689 to the user command @code{dont-repeat}, see @ref{Define, dont-repeat}.
24692 @defun Command.invoke (argument, from_tty)
24693 This method is called by @value{GDBN} when this command is invoked.
24695 @var{argument} is a string. It is the argument to the command, after
24696 leading and trailing whitespace has been stripped.
24698 @var{from_tty} is a boolean argument. When true, this means that the
24699 command was entered by the user at the terminal; when false it means
24700 that the command came from elsewhere.
24702 If this method throws an exception, it is turned into a @value{GDBN}
24703 @code{error} call. Otherwise, the return value is ignored.
24705 @findex gdb.string_to_argv
24706 To break @var{argument} up into an argv-like string use
24707 @code{gdb.string_to_argv}. This function behaves identically to
24708 @value{GDBN}'s internal argument lexer @code{buildargv}.
24709 It is recommended to use this for consistency.
24710 Arguments are separated by spaces and may be quoted.
24714 print gdb.string_to_argv ("1 2\ \\\"3 '4 \"5' \"6 '7\"")
24715 ['1', '2 "3', '4 "5', "6 '7"]
24720 @cindex completion of Python commands
24721 @defun Command.complete (text, word)
24722 This method is called by @value{GDBN} when the user attempts
24723 completion on this command. All forms of completion are handled by
24724 this method, that is, the @key{TAB} and @key{M-?} key bindings
24725 (@pxref{Completion}), and the @code{complete} command (@pxref{Help,
24728 The arguments @var{text} and @var{word} are both strings. @var{text}
24729 holds the complete command line up to the cursor's location.
24730 @var{word} holds the last word of the command line; this is computed
24731 using a word-breaking heuristic.
24733 The @code{complete} method can return several values:
24736 If the return value is a sequence, the contents of the sequence are
24737 used as the completions. It is up to @code{complete} to ensure that the
24738 contents actually do complete the word. A zero-length sequence is
24739 allowed, it means that there were no completions available. Only
24740 string elements of the sequence are used; other elements in the
24741 sequence are ignored.
24744 If the return value is one of the @samp{COMPLETE_} constants defined
24745 below, then the corresponding @value{GDBN}-internal completion
24746 function is invoked, and its result is used.
24749 All other results are treated as though there were no available
24754 When a new command is registered, it must be declared as a member of
24755 some general class of commands. This is used to classify top-level
24756 commands in the on-line help system; note that prefix commands are not
24757 listed under their own category but rather that of their top-level
24758 command. The available classifications are represented by constants
24759 defined in the @code{gdb} module:
24762 @findex COMMAND_NONE
24763 @findex gdb.COMMAND_NONE
24764 @item gdb.COMMAND_NONE
24765 The command does not belong to any particular class. A command in
24766 this category will not be displayed in any of the help categories.
24768 @findex COMMAND_RUNNING
24769 @findex gdb.COMMAND_RUNNING
24770 @item gdb.COMMAND_RUNNING
24771 The command is related to running the inferior. For example,
24772 @code{start}, @code{step}, and @code{continue} are in this category.
24773 Type @kbd{help running} at the @value{GDBN} prompt to see a list of
24774 commands in this category.
24776 @findex COMMAND_DATA
24777 @findex gdb.COMMAND_DATA
24778 @item gdb.COMMAND_DATA
24779 The command is related to data or variables. For example,
24780 @code{call}, @code{find}, and @code{print} are in this category. Type
24781 @kbd{help data} at the @value{GDBN} prompt to see a list of commands
24784 @findex COMMAND_STACK
24785 @findex gdb.COMMAND_STACK
24786 @item gdb.COMMAND_STACK
24787 The command has to do with manipulation of the stack. For example,
24788 @code{backtrace}, @code{frame}, and @code{return} are in this
24789 category. Type @kbd{help stack} at the @value{GDBN} prompt to see a
24790 list of commands in this category.
24792 @findex COMMAND_FILES
24793 @findex gdb.COMMAND_FILES
24794 @item gdb.COMMAND_FILES
24795 This class is used for file-related commands. For example,
24796 @code{file}, @code{list} and @code{section} are in this category.
24797 Type @kbd{help files} at the @value{GDBN} prompt to see a list of
24798 commands in this category.
24800 @findex COMMAND_SUPPORT
24801 @findex gdb.COMMAND_SUPPORT
24802 @item gdb.COMMAND_SUPPORT
24803 This should be used for ``support facilities'', generally meaning
24804 things that are useful to the user when interacting with @value{GDBN},
24805 but not related to the state of the inferior. For example,
24806 @code{help}, @code{make}, and @code{shell} are in this category. Type
24807 @kbd{help support} at the @value{GDBN} prompt to see a list of
24808 commands in this category.
24810 @findex COMMAND_STATUS
24811 @findex gdb.COMMAND_STATUS
24812 @item gdb.COMMAND_STATUS
24813 The command is an @samp{info}-related command, that is, related to the
24814 state of @value{GDBN} itself. For example, @code{info}, @code{macro},
24815 and @code{show} are in this category. Type @kbd{help status} at the
24816 @value{GDBN} prompt to see a list of commands in this category.
24818 @findex COMMAND_BREAKPOINTS
24819 @findex gdb.COMMAND_BREAKPOINTS
24820 @item gdb.COMMAND_BREAKPOINTS
24821 The command has to do with breakpoints. For example, @code{break},
24822 @code{clear}, and @code{delete} are in this category. Type @kbd{help
24823 breakpoints} at the @value{GDBN} prompt to see a list of commands in
24826 @findex COMMAND_TRACEPOINTS
24827 @findex gdb.COMMAND_TRACEPOINTS
24828 @item gdb.COMMAND_TRACEPOINTS
24829 The command has to do with tracepoints. For example, @code{trace},
24830 @code{actions}, and @code{tfind} are in this category. Type
24831 @kbd{help tracepoints} at the @value{GDBN} prompt to see a list of
24832 commands in this category.
24834 @findex COMMAND_USER
24835 @findex gdb.COMMAND_USER
24836 @item gdb.COMMAND_USER
24837 The command is a general purpose command for the user, and typically
24838 does not fit in one of the other categories.
24839 Type @kbd{help user-defined} at the @value{GDBN} prompt to see
24840 a list of commands in this category, as well as the list of gdb macros
24841 (@pxref{Sequences}).
24843 @findex COMMAND_OBSCURE
24844 @findex gdb.COMMAND_OBSCURE
24845 @item gdb.COMMAND_OBSCURE
24846 The command is only used in unusual circumstances, or is not of
24847 general interest to users. For example, @code{checkpoint},
24848 @code{fork}, and @code{stop} are in this category. Type @kbd{help
24849 obscure} at the @value{GDBN} prompt to see a list of commands in this
24852 @findex COMMAND_MAINTENANCE
24853 @findex gdb.COMMAND_MAINTENANCE
24854 @item gdb.COMMAND_MAINTENANCE
24855 The command is only useful to @value{GDBN} maintainers. The
24856 @code{maintenance} and @code{flushregs} commands are in this category.
24857 Type @kbd{help internals} at the @value{GDBN} prompt to see a list of
24858 commands in this category.
24861 A new command can use a predefined completion function, either by
24862 specifying it via an argument at initialization, or by returning it
24863 from the @code{complete} method. These predefined completion
24864 constants are all defined in the @code{gdb} module:
24867 @findex COMPLETE_NONE
24868 @findex gdb.COMPLETE_NONE
24869 @item gdb.COMPLETE_NONE
24870 This constant means that no completion should be done.
24872 @findex COMPLETE_FILENAME
24873 @findex gdb.COMPLETE_FILENAME
24874 @item gdb.COMPLETE_FILENAME
24875 This constant means that filename completion should be performed.
24877 @findex COMPLETE_LOCATION
24878 @findex gdb.COMPLETE_LOCATION
24879 @item gdb.COMPLETE_LOCATION
24880 This constant means that location completion should be done.
24881 @xref{Specify Location}.
24883 @findex COMPLETE_COMMAND
24884 @findex gdb.COMPLETE_COMMAND
24885 @item gdb.COMPLETE_COMMAND
24886 This constant means that completion should examine @value{GDBN}
24889 @findex COMPLETE_SYMBOL
24890 @findex gdb.COMPLETE_SYMBOL
24891 @item gdb.COMPLETE_SYMBOL
24892 This constant means that completion should be done using symbol names
24896 The following code snippet shows how a trivial CLI command can be
24897 implemented in Python:
24900 class HelloWorld (gdb.Command):
24901 """Greet the whole world."""
24903 def __init__ (self):
24904 super (HelloWorld, self).__init__ ("hello-world", gdb.COMMAND_USER)
24906 def invoke (self, arg, from_tty):
24907 print "Hello, World!"
24912 The last line instantiates the class, and is necessary to trigger the
24913 registration of the command with @value{GDBN}. Depending on how the
24914 Python code is read into @value{GDBN}, you may need to import the
24915 @code{gdb} module explicitly.
24917 @node Parameters In Python
24918 @subsubsection Parameters In Python
24920 @cindex parameters in python
24921 @cindex python parameters
24922 @tindex gdb.Parameter
24924 You can implement new @value{GDBN} parameters using Python. A new
24925 parameter is implemented as an instance of the @code{gdb.Parameter}
24928 Parameters are exposed to the user via the @code{set} and
24929 @code{show} commands. @xref{Help}.
24931 There are many parameters that already exist and can be set in
24932 @value{GDBN}. Two examples are: @code{set follow fork} and
24933 @code{set charset}. Setting these parameters influences certain
24934 behavior in @value{GDBN}. Similarly, you can define parameters that
24935 can be used to influence behavior in custom Python scripts and commands.
24937 @defun Parameter.__init__ (name, @var{command-class}, @var{parameter-class} @r{[}, @var{enum-sequence}@r{]})
24938 The object initializer for @code{Parameter} registers the new
24939 parameter with @value{GDBN}. This initializer is normally invoked
24940 from the subclass' own @code{__init__} method.
24942 @var{name} is the name of the new parameter. If @var{name} consists
24943 of multiple words, then the initial words are looked for as prefix
24944 parameters. An example of this can be illustrated with the
24945 @code{set print} set of parameters. If @var{name} is
24946 @code{print foo}, then @code{print} will be searched as the prefix
24947 parameter. In this case the parameter can subsequently be accessed in
24948 @value{GDBN} as @code{set print foo}.
24950 If @var{name} consists of multiple words, and no prefix parameter group
24951 can be found, an exception is raised.
24953 @var{command-class} should be one of the @samp{COMMAND_} constants
24954 (@pxref{Commands In Python}). This argument tells @value{GDBN} how to
24955 categorize the new parameter in the help system.
24957 @var{parameter-class} should be one of the @samp{PARAM_} constants
24958 defined below. This argument tells @value{GDBN} the type of the new
24959 parameter; this information is used for input validation and
24962 If @var{parameter-class} is @code{PARAM_ENUM}, then
24963 @var{enum-sequence} must be a sequence of strings. These strings
24964 represent the possible values for the parameter.
24966 If @var{parameter-class} is not @code{PARAM_ENUM}, then the presence
24967 of a fourth argument will cause an exception to be thrown.
24969 The help text for the new parameter is taken from the Python
24970 documentation string for the parameter's class, if there is one. If
24971 there is no documentation string, a default value is used.
24974 @defvar Parameter.set_doc
24975 If this attribute exists, and is a string, then its value is used as
24976 the help text for this parameter's @code{set} command. The value is
24977 examined when @code{Parameter.__init__} is invoked; subsequent changes
24981 @defvar Parameter.show_doc
24982 If this attribute exists, and is a string, then its value is used as
24983 the help text for this parameter's @code{show} command. The value is
24984 examined when @code{Parameter.__init__} is invoked; subsequent changes
24988 @defvar Parameter.value
24989 The @code{value} attribute holds the underlying value of the
24990 parameter. It can be read and assigned to just as any other
24991 attribute. @value{GDBN} does validation when assignments are made.
24994 There are two methods that should be implemented in any
24995 @code{Parameter} class. These are:
24997 @defun Parameter.get_set_string (self)
24998 @value{GDBN} will call this method when a @var{parameter}'s value has
24999 been changed via the @code{set} API (for example, @kbd{set foo off}).
25000 The @code{value} attribute has already been populated with the new
25001 value and may be used in output. This method must return a string.
25004 @defun Parameter.get_show_string (self, svalue)
25005 @value{GDBN} will call this method when a @var{parameter}'s
25006 @code{show} API has been invoked (for example, @kbd{show foo}). The
25007 argument @code{svalue} receives the string representation of the
25008 current value. This method must return a string.
25011 When a new parameter is defined, its type must be specified. The
25012 available types are represented by constants defined in the @code{gdb}
25016 @findex PARAM_BOOLEAN
25017 @findex gdb.PARAM_BOOLEAN
25018 @item gdb.PARAM_BOOLEAN
25019 The value is a plain boolean. The Python boolean values, @code{True}
25020 and @code{False} are the only valid values.
25022 @findex PARAM_AUTO_BOOLEAN
25023 @findex gdb.PARAM_AUTO_BOOLEAN
25024 @item gdb.PARAM_AUTO_BOOLEAN
25025 The value has three possible states: true, false, and @samp{auto}. In
25026 Python, true and false are represented using boolean constants, and
25027 @samp{auto} is represented using @code{None}.
25029 @findex PARAM_UINTEGER
25030 @findex gdb.PARAM_UINTEGER
25031 @item gdb.PARAM_UINTEGER
25032 The value is an unsigned integer. The value of 0 should be
25033 interpreted to mean ``unlimited''.
25035 @findex PARAM_INTEGER
25036 @findex gdb.PARAM_INTEGER
25037 @item gdb.PARAM_INTEGER
25038 The value is a signed integer. The value of 0 should be interpreted
25039 to mean ``unlimited''.
25041 @findex PARAM_STRING
25042 @findex gdb.PARAM_STRING
25043 @item gdb.PARAM_STRING
25044 The value is a string. When the user modifies the string, any escape
25045 sequences, such as @samp{\t}, @samp{\f}, and octal escapes, are
25046 translated into corresponding characters and encoded into the current
25049 @findex PARAM_STRING_NOESCAPE
25050 @findex gdb.PARAM_STRING_NOESCAPE
25051 @item gdb.PARAM_STRING_NOESCAPE
25052 The value is a string. When the user modifies the string, escapes are
25053 passed through untranslated.
25055 @findex PARAM_OPTIONAL_FILENAME
25056 @findex gdb.PARAM_OPTIONAL_FILENAME
25057 @item gdb.PARAM_OPTIONAL_FILENAME
25058 The value is a either a filename (a string), or @code{None}.
25060 @findex PARAM_FILENAME
25061 @findex gdb.PARAM_FILENAME
25062 @item gdb.PARAM_FILENAME
25063 The value is a filename. This is just like
25064 @code{PARAM_STRING_NOESCAPE}, but uses file names for completion.
25066 @findex PARAM_ZINTEGER
25067 @findex gdb.PARAM_ZINTEGER
25068 @item gdb.PARAM_ZINTEGER
25069 The value is an integer. This is like @code{PARAM_INTEGER}, except 0
25070 is interpreted as itself.
25073 @findex gdb.PARAM_ENUM
25074 @item gdb.PARAM_ENUM
25075 The value is a string, which must be one of a collection string
25076 constants provided when the parameter is created.
25079 @node Functions In Python
25080 @subsubsection Writing new convenience functions
25082 @cindex writing convenience functions
25083 @cindex convenience functions in python
25084 @cindex python convenience functions
25085 @tindex gdb.Function
25087 You can implement new convenience functions (@pxref{Convenience Vars})
25088 in Python. A convenience function is an instance of a subclass of the
25089 class @code{gdb.Function}.
25091 @defun Function.__init__ (name)
25092 The initializer for @code{Function} registers the new function with
25093 @value{GDBN}. The argument @var{name} is the name of the function,
25094 a string. The function will be visible to the user as a convenience
25095 variable of type @code{internal function}, whose name is the same as
25096 the given @var{name}.
25098 The documentation for the new function is taken from the documentation
25099 string for the new class.
25102 @defun Function.invoke (@var{*args})
25103 When a convenience function is evaluated, its arguments are converted
25104 to instances of @code{gdb.Value}, and then the function's
25105 @code{invoke} method is called. Note that @value{GDBN} does not
25106 predetermine the arity of convenience functions. Instead, all
25107 available arguments are passed to @code{invoke}, following the
25108 standard Python calling convention. In particular, a convenience
25109 function can have default values for parameters without ill effect.
25111 The return value of this method is used as its value in the enclosing
25112 expression. If an ordinary Python value is returned, it is converted
25113 to a @code{gdb.Value} following the usual rules.
25116 The following code snippet shows how a trivial convenience function can
25117 be implemented in Python:
25120 class Greet (gdb.Function):
25121 """Return string to greet someone.
25122 Takes a name as argument."""
25124 def __init__ (self):
25125 super (Greet, self).__init__ ("greet")
25127 def invoke (self, name):
25128 return "Hello, %s!" % name.string ()
25133 The last line instantiates the class, and is necessary to trigger the
25134 registration of the function with @value{GDBN}. Depending on how the
25135 Python code is read into @value{GDBN}, you may need to import the
25136 @code{gdb} module explicitly.
25138 Now you can use the function in an expression:
25141 (gdb) print $greet("Bob")
25145 @node Progspaces In Python
25146 @subsubsection Program Spaces In Python
25148 @cindex progspaces in python
25149 @tindex gdb.Progspace
25151 A program space, or @dfn{progspace}, represents a symbolic view
25152 of an address space.
25153 It consists of all of the objfiles of the program.
25154 @xref{Objfiles In Python}.
25155 @xref{Inferiors and Programs, program spaces}, for more details
25156 about program spaces.
25158 The following progspace-related functions are available in the
25161 @findex gdb.current_progspace
25162 @defun gdb.current_progspace ()
25163 This function returns the program space of the currently selected inferior.
25164 @xref{Inferiors and Programs}.
25167 @findex gdb.progspaces
25168 @defun gdb.progspaces ()
25169 Return a sequence of all the progspaces currently known to @value{GDBN}.
25172 Each progspace is represented by an instance of the @code{gdb.Progspace}
25175 @defvar Progspace.filename
25176 The file name of the progspace as a string.
25179 @defvar Progspace.pretty_printers
25180 The @code{pretty_printers} attribute is a list of functions. It is
25181 used to look up pretty-printers. A @code{Value} is passed to each
25182 function in order; if the function returns @code{None}, then the
25183 search continues. Otherwise, the return value should be an object
25184 which is used to format the value. @xref{Pretty Printing API}, for more
25188 @defvar Progspace.type_printers
25189 The @code{type_printers} attribute is a list of type printer objects.
25190 @xref{Type Printing API}, for more information.
25193 @node Objfiles In Python
25194 @subsubsection Objfiles In Python
25196 @cindex objfiles in python
25197 @tindex gdb.Objfile
25199 @value{GDBN} loads symbols for an inferior from various
25200 symbol-containing files (@pxref{Files}). These include the primary
25201 executable file, any shared libraries used by the inferior, and any
25202 separate debug info files (@pxref{Separate Debug Files}).
25203 @value{GDBN} calls these symbol-containing files @dfn{objfiles}.
25205 The following objfile-related functions are available in the
25208 @findex gdb.current_objfile
25209 @defun gdb.current_objfile ()
25210 When auto-loading a Python script (@pxref{Python Auto-loading}), @value{GDBN}
25211 sets the ``current objfile'' to the corresponding objfile. This
25212 function returns the current objfile. If there is no current objfile,
25213 this function returns @code{None}.
25216 @findex gdb.objfiles
25217 @defun gdb.objfiles ()
25218 Return a sequence of all the objfiles current known to @value{GDBN}.
25219 @xref{Objfiles In Python}.
25222 Each objfile is represented by an instance of the @code{gdb.Objfile}
25225 @defvar Objfile.filename
25226 The file name of the objfile as a string.
25229 @defvar Objfile.pretty_printers
25230 The @code{pretty_printers} attribute is a list of functions. It is
25231 used to look up pretty-printers. A @code{Value} is passed to each
25232 function in order; if the function returns @code{None}, then the
25233 search continues. Otherwise, the return value should be an object
25234 which is used to format the value. @xref{Pretty Printing API}, for more
25238 @defvar Objfile.type_printers
25239 The @code{type_printers} attribute is a list of type printer objects.
25240 @xref{Type Printing API}, for more information.
25243 A @code{gdb.Objfile} object has the following methods:
25245 @defun Objfile.is_valid ()
25246 Returns @code{True} if the @code{gdb.Objfile} object is valid,
25247 @code{False} if not. A @code{gdb.Objfile} object can become invalid
25248 if the object file it refers to is not loaded in @value{GDBN} any
25249 longer. All other @code{gdb.Objfile} methods will throw an exception
25250 if it is invalid at the time the method is called.
25253 @node Frames In Python
25254 @subsubsection Accessing inferior stack frames from Python.
25256 @cindex frames in python
25257 When the debugged program stops, @value{GDBN} is able to analyze its call
25258 stack (@pxref{Frames,,Stack frames}). The @code{gdb.Frame} class
25259 represents a frame in the stack. A @code{gdb.Frame} object is only valid
25260 while its corresponding frame exists in the inferior's stack. If you try
25261 to use an invalid frame object, @value{GDBN} will throw a @code{gdb.error}
25262 exception (@pxref{Exception Handling}).
25264 Two @code{gdb.Frame} objects can be compared for equality with the @code{==}
25268 (@value{GDBP}) python print gdb.newest_frame() == gdb.selected_frame ()
25272 The following frame-related functions are available in the @code{gdb} module:
25274 @findex gdb.selected_frame
25275 @defun gdb.selected_frame ()
25276 Return the selected frame object. (@pxref{Selection,,Selecting a Frame}).
25279 @findex gdb.newest_frame
25280 @defun gdb.newest_frame ()
25281 Return the newest frame object for the selected thread.
25284 @defun gdb.frame_stop_reason_string (reason)
25285 Return a string explaining the reason why @value{GDBN} stopped unwinding
25286 frames, as expressed by the given @var{reason} code (an integer, see the
25287 @code{unwind_stop_reason} method further down in this section).
25290 A @code{gdb.Frame} object has the following methods:
25292 @defun Frame.is_valid ()
25293 Returns true if the @code{gdb.Frame} object is valid, false if not.
25294 A frame object can become invalid if the frame it refers to doesn't
25295 exist anymore in the inferior. All @code{gdb.Frame} methods will throw
25296 an exception if it is invalid at the time the method is called.
25299 @defun Frame.name ()
25300 Returns the function name of the frame, or @code{None} if it can't be
25304 @defun Frame.architecture ()
25305 Returns the @code{gdb.Architecture} object corresponding to the frame's
25306 architecture. @xref{Architectures In Python}.
25309 @defun Frame.type ()
25310 Returns the type of the frame. The value can be one of:
25312 @item gdb.NORMAL_FRAME
25313 An ordinary stack frame.
25315 @item gdb.DUMMY_FRAME
25316 A fake stack frame that was created by @value{GDBN} when performing an
25317 inferior function call.
25319 @item gdb.INLINE_FRAME
25320 A frame representing an inlined function. The function was inlined
25321 into a @code{gdb.NORMAL_FRAME} that is older than this one.
25323 @item gdb.TAILCALL_FRAME
25324 A frame representing a tail call. @xref{Tail Call Frames}.
25326 @item gdb.SIGTRAMP_FRAME
25327 A signal trampoline frame. This is the frame created by the OS when
25328 it calls into a signal handler.
25330 @item gdb.ARCH_FRAME
25331 A fake stack frame representing a cross-architecture call.
25333 @item gdb.SENTINEL_FRAME
25334 This is like @code{gdb.NORMAL_FRAME}, but it is only used for the
25339 @defun Frame.unwind_stop_reason ()
25340 Return an integer representing the reason why it's not possible to find
25341 more frames toward the outermost frame. Use
25342 @code{gdb.frame_stop_reason_string} to convert the value returned by this
25343 function to a string. The value can be one of:
25346 @item gdb.FRAME_UNWIND_NO_REASON
25347 No particular reason (older frames should be available).
25349 @item gdb.FRAME_UNWIND_NULL_ID
25350 The previous frame's analyzer returns an invalid result.
25352 @item gdb.FRAME_UNWIND_OUTERMOST
25353 This frame is the outermost.
25355 @item gdb.FRAME_UNWIND_UNAVAILABLE
25356 Cannot unwind further, because that would require knowing the
25357 values of registers or memory that have not been collected.
25359 @item gdb.FRAME_UNWIND_INNER_ID
25360 This frame ID looks like it ought to belong to a NEXT frame,
25361 but we got it for a PREV frame. Normally, this is a sign of
25362 unwinder failure. It could also indicate stack corruption.
25364 @item gdb.FRAME_UNWIND_SAME_ID
25365 This frame has the same ID as the previous one. That means
25366 that unwinding further would almost certainly give us another
25367 frame with exactly the same ID, so break the chain. Normally,
25368 this is a sign of unwinder failure. It could also indicate
25371 @item gdb.FRAME_UNWIND_NO_SAVED_PC
25372 The frame unwinder did not find any saved PC, but we needed
25373 one to unwind further.
25375 @item gdb.FRAME_UNWIND_FIRST_ERROR
25376 Any stop reason greater or equal to this value indicates some kind
25377 of error. This special value facilitates writing code that tests
25378 for errors in unwinding in a way that will work correctly even if
25379 the list of the other values is modified in future @value{GDBN}
25380 versions. Using it, you could write:
25382 reason = gdb.selected_frame().unwind_stop_reason ()
25383 reason_str = gdb.frame_stop_reason_string (reason)
25384 if reason >= gdb.FRAME_UNWIND_FIRST_ERROR:
25385 print "An error occured: %s" % reason_str
25392 Returns the frame's resume address.
25395 @defun Frame.block ()
25396 Return the frame's code block. @xref{Blocks In Python}.
25399 @defun Frame.function ()
25400 Return the symbol for the function corresponding to this frame.
25401 @xref{Symbols In Python}.
25404 @defun Frame.older ()
25405 Return the frame that called this frame.
25408 @defun Frame.newer ()
25409 Return the frame called by this frame.
25412 @defun Frame.find_sal ()
25413 Return the frame's symtab and line object.
25414 @xref{Symbol Tables In Python}.
25417 @defun Frame.read_var (variable @r{[}, block@r{]})
25418 Return the value of @var{variable} in this frame. If the optional
25419 argument @var{block} is provided, search for the variable from that
25420 block; otherwise start at the frame's current block (which is
25421 determined by the frame's current program counter). @var{variable}
25422 must be a string or a @code{gdb.Symbol} object. @var{block} must be a
25423 @code{gdb.Block} object.
25426 @defun Frame.select ()
25427 Set this frame to be the selected frame. @xref{Stack, ,Examining the
25431 @node Blocks In Python
25432 @subsubsection Accessing frame blocks from Python.
25434 @cindex blocks in python
25437 Within each frame, @value{GDBN} maintains information on each block
25438 stored in that frame. These blocks are organized hierarchically, and
25439 are represented individually in Python as a @code{gdb.Block}.
25440 Please see @ref{Frames In Python}, for a more in-depth discussion on
25441 frames. Furthermore, see @ref{Stack, ,Examining the Stack}, for more
25442 detailed technical information on @value{GDBN}'s book-keeping of the
25445 A @code{gdb.Block} is iterable. The iterator returns the symbols
25446 (@pxref{Symbols In Python}) local to the block. Python programs
25447 should not assume that a specific block object will always contain a
25448 given symbol, since changes in @value{GDBN} features and
25449 infrastructure may cause symbols move across blocks in a symbol
25452 The following block-related functions are available in the @code{gdb}
25455 @findex gdb.block_for_pc
25456 @defun gdb.block_for_pc (pc)
25457 Return the @code{gdb.Block} containing the given @var{pc} value. If the
25458 block cannot be found for the @var{pc} value specified, the function
25459 will return @code{None}.
25462 A @code{gdb.Block} object has the following methods:
25464 @defun Block.is_valid ()
25465 Returns @code{True} if the @code{gdb.Block} object is valid,
25466 @code{False} if not. A block object can become invalid if the block it
25467 refers to doesn't exist anymore in the inferior. All other
25468 @code{gdb.Block} methods will throw an exception if it is invalid at
25469 the time the method is called. The block's validity is also checked
25470 during iteration over symbols of the block.
25473 A @code{gdb.Block} object has the following attributes:
25475 @defvar Block.start
25476 The start address of the block. This attribute is not writable.
25480 The end address of the block. This attribute is not writable.
25483 @defvar Block.function
25484 The name of the block represented as a @code{gdb.Symbol}. If the
25485 block is not named, then this attribute holds @code{None}. This
25486 attribute is not writable.
25489 @defvar Block.superblock
25490 The block containing this block. If this parent block does not exist,
25491 this attribute holds @code{None}. This attribute is not writable.
25494 @defvar Block.global_block
25495 The global block associated with this block. This attribute is not
25499 @defvar Block.static_block
25500 The static block associated with this block. This attribute is not
25504 @defvar Block.is_global
25505 @code{True} if the @code{gdb.Block} object is a global block,
25506 @code{False} if not. This attribute is not
25510 @defvar Block.is_static
25511 @code{True} if the @code{gdb.Block} object is a static block,
25512 @code{False} if not. This attribute is not writable.
25515 @node Symbols In Python
25516 @subsubsection Python representation of Symbols.
25518 @cindex symbols in python
25521 @value{GDBN} represents every variable, function and type as an
25522 entry in a symbol table. @xref{Symbols, ,Examining the Symbol Table}.
25523 Similarly, Python represents these symbols in @value{GDBN} with the
25524 @code{gdb.Symbol} object.
25526 The following symbol-related functions are available in the @code{gdb}
25529 @findex gdb.lookup_symbol
25530 @defun gdb.lookup_symbol (name @r{[}, block @r{[}, domain@r{]]})
25531 This function searches for a symbol by name. The search scope can be
25532 restricted to the parameters defined in the optional domain and block
25535 @var{name} is the name of the symbol. It must be a string. The
25536 optional @var{block} argument restricts the search to symbols visible
25537 in that @var{block}. The @var{block} argument must be a
25538 @code{gdb.Block} object. If omitted, the block for the current frame
25539 is used. The optional @var{domain} argument restricts
25540 the search to the domain type. The @var{domain} argument must be a
25541 domain constant defined in the @code{gdb} module and described later
25544 The result is a tuple of two elements.
25545 The first element is a @code{gdb.Symbol} object or @code{None} if the symbol
25547 If the symbol is found, the second element is @code{True} if the symbol
25548 is a field of a method's object (e.g., @code{this} in C@t{++}),
25549 otherwise it is @code{False}.
25550 If the symbol is not found, the second element is @code{False}.
25553 @findex gdb.lookup_global_symbol
25554 @defun gdb.lookup_global_symbol (name @r{[}, domain@r{]})
25555 This function searches for a global symbol by name.
25556 The search scope can be restricted to by the domain argument.
25558 @var{name} is the name of the symbol. It must be a string.
25559 The optional @var{domain} argument restricts the search to the domain type.
25560 The @var{domain} argument must be a domain constant defined in the @code{gdb}
25561 module and described later in this chapter.
25563 The result is a @code{gdb.Symbol} object or @code{None} if the symbol
25567 A @code{gdb.Symbol} object has the following attributes:
25569 @defvar Symbol.type
25570 The type of the symbol or @code{None} if no type is recorded.
25571 This attribute is represented as a @code{gdb.Type} object.
25572 @xref{Types In Python}. This attribute is not writable.
25575 @defvar Symbol.symtab
25576 The symbol table in which the symbol appears. This attribute is
25577 represented as a @code{gdb.Symtab} object. @xref{Symbol Tables In
25578 Python}. This attribute is not writable.
25581 @defvar Symbol.line
25582 The line number in the source code at which the symbol was defined.
25583 This is an integer.
25586 @defvar Symbol.name
25587 The name of the symbol as a string. This attribute is not writable.
25590 @defvar Symbol.linkage_name
25591 The name of the symbol, as used by the linker (i.e., may be mangled).
25592 This attribute is not writable.
25595 @defvar Symbol.print_name
25596 The name of the symbol in a form suitable for output. This is either
25597 @code{name} or @code{linkage_name}, depending on whether the user
25598 asked @value{GDBN} to display demangled or mangled names.
25601 @defvar Symbol.addr_class
25602 The address class of the symbol. This classifies how to find the value
25603 of a symbol. Each address class is a constant defined in the
25604 @code{gdb} module and described later in this chapter.
25607 @defvar Symbol.needs_frame
25608 This is @code{True} if evaluating this symbol's value requires a frame
25609 (@pxref{Frames In Python}) and @code{False} otherwise. Typically,
25610 local variables will require a frame, but other symbols will not.
25613 @defvar Symbol.is_argument
25614 @code{True} if the symbol is an argument of a function.
25617 @defvar Symbol.is_constant
25618 @code{True} if the symbol is a constant.
25621 @defvar Symbol.is_function
25622 @code{True} if the symbol is a function or a method.
25625 @defvar Symbol.is_variable
25626 @code{True} if the symbol is a variable.
25629 A @code{gdb.Symbol} object has the following methods:
25631 @defun Symbol.is_valid ()
25632 Returns @code{True} if the @code{gdb.Symbol} object is valid,
25633 @code{False} if not. A @code{gdb.Symbol} object can become invalid if
25634 the symbol it refers to does not exist in @value{GDBN} any longer.
25635 All other @code{gdb.Symbol} methods will throw an exception if it is
25636 invalid at the time the method is called.
25639 @defun Symbol.value (@r{[}frame@r{]})
25640 Compute the value of the symbol, as a @code{gdb.Value}. For
25641 functions, this computes the address of the function, cast to the
25642 appropriate type. If the symbol requires a frame in order to compute
25643 its value, then @var{frame} must be given. If @var{frame} is not
25644 given, or if @var{frame} is invalid, then this method will throw an
25648 The available domain categories in @code{gdb.Symbol} are represented
25649 as constants in the @code{gdb} module:
25652 @findex SYMBOL_UNDEF_DOMAIN
25653 @findex gdb.SYMBOL_UNDEF_DOMAIN
25654 @item gdb.SYMBOL_UNDEF_DOMAIN
25655 This is used when a domain has not been discovered or none of the
25656 following domains apply. This usually indicates an error either
25657 in the symbol information or in @value{GDBN}'s handling of symbols.
25658 @findex SYMBOL_VAR_DOMAIN
25659 @findex gdb.SYMBOL_VAR_DOMAIN
25660 @item gdb.SYMBOL_VAR_DOMAIN
25661 This domain contains variables, function names, typedef names and enum
25663 @findex SYMBOL_STRUCT_DOMAIN
25664 @findex gdb.SYMBOL_STRUCT_DOMAIN
25665 @item gdb.SYMBOL_STRUCT_DOMAIN
25666 This domain holds struct, union and enum type names.
25667 @findex SYMBOL_LABEL_DOMAIN
25668 @findex gdb.SYMBOL_LABEL_DOMAIN
25669 @item gdb.SYMBOL_LABEL_DOMAIN
25670 This domain contains names of labels (for gotos).
25671 @findex SYMBOL_VARIABLES_DOMAIN
25672 @findex gdb.SYMBOL_VARIABLES_DOMAIN
25673 @item gdb.SYMBOL_VARIABLES_DOMAIN
25674 This domain holds a subset of the @code{SYMBOLS_VAR_DOMAIN}; it
25675 contains everything minus functions and types.
25676 @findex SYMBOL_FUNCTIONS_DOMAIN
25677 @findex gdb.SYMBOL_FUNCTIONS_DOMAIN
25678 @item gdb.SYMBOL_FUNCTION_DOMAIN
25679 This domain contains all functions.
25680 @findex SYMBOL_TYPES_DOMAIN
25681 @findex gdb.SYMBOL_TYPES_DOMAIN
25682 @item gdb.SYMBOL_TYPES_DOMAIN
25683 This domain contains all types.
25686 The available address class categories in @code{gdb.Symbol} are represented
25687 as constants in the @code{gdb} module:
25690 @findex SYMBOL_LOC_UNDEF
25691 @findex gdb.SYMBOL_LOC_UNDEF
25692 @item gdb.SYMBOL_LOC_UNDEF
25693 If this is returned by address class, it indicates an error either in
25694 the symbol information or in @value{GDBN}'s handling of symbols.
25695 @findex SYMBOL_LOC_CONST
25696 @findex gdb.SYMBOL_LOC_CONST
25697 @item gdb.SYMBOL_LOC_CONST
25698 Value is constant int.
25699 @findex SYMBOL_LOC_STATIC
25700 @findex gdb.SYMBOL_LOC_STATIC
25701 @item gdb.SYMBOL_LOC_STATIC
25702 Value is at a fixed address.
25703 @findex SYMBOL_LOC_REGISTER
25704 @findex gdb.SYMBOL_LOC_REGISTER
25705 @item gdb.SYMBOL_LOC_REGISTER
25706 Value is in a register.
25707 @findex SYMBOL_LOC_ARG
25708 @findex gdb.SYMBOL_LOC_ARG
25709 @item gdb.SYMBOL_LOC_ARG
25710 Value is an argument. This value is at the offset stored within the
25711 symbol inside the frame's argument list.
25712 @findex SYMBOL_LOC_REF_ARG
25713 @findex gdb.SYMBOL_LOC_REF_ARG
25714 @item gdb.SYMBOL_LOC_REF_ARG
25715 Value address is stored in the frame's argument list. Just like
25716 @code{LOC_ARG} except that the value's address is stored at the
25717 offset, not the value itself.
25718 @findex SYMBOL_LOC_REGPARM_ADDR
25719 @findex gdb.SYMBOL_LOC_REGPARM_ADDR
25720 @item gdb.SYMBOL_LOC_REGPARM_ADDR
25721 Value is a specified register. Just like @code{LOC_REGISTER} except
25722 the register holds the address of the argument instead of the argument
25724 @findex SYMBOL_LOC_LOCAL
25725 @findex gdb.SYMBOL_LOC_LOCAL
25726 @item gdb.SYMBOL_LOC_LOCAL
25727 Value is a local variable.
25728 @findex SYMBOL_LOC_TYPEDEF
25729 @findex gdb.SYMBOL_LOC_TYPEDEF
25730 @item gdb.SYMBOL_LOC_TYPEDEF
25731 Value not used. Symbols in the domain @code{SYMBOL_STRUCT_DOMAIN} all
25733 @findex SYMBOL_LOC_BLOCK
25734 @findex gdb.SYMBOL_LOC_BLOCK
25735 @item gdb.SYMBOL_LOC_BLOCK
25737 @findex SYMBOL_LOC_CONST_BYTES
25738 @findex gdb.SYMBOL_LOC_CONST_BYTES
25739 @item gdb.SYMBOL_LOC_CONST_BYTES
25740 Value is a byte-sequence.
25741 @findex SYMBOL_LOC_UNRESOLVED
25742 @findex gdb.SYMBOL_LOC_UNRESOLVED
25743 @item gdb.SYMBOL_LOC_UNRESOLVED
25744 Value is at a fixed address, but the address of the variable has to be
25745 determined from the minimal symbol table whenever the variable is
25747 @findex SYMBOL_LOC_OPTIMIZED_OUT
25748 @findex gdb.SYMBOL_LOC_OPTIMIZED_OUT
25749 @item gdb.SYMBOL_LOC_OPTIMIZED_OUT
25750 The value does not actually exist in the program.
25751 @findex SYMBOL_LOC_COMPUTED
25752 @findex gdb.SYMBOL_LOC_COMPUTED
25753 @item gdb.SYMBOL_LOC_COMPUTED
25754 The value's address is a computed location.
25757 @node Symbol Tables In Python
25758 @subsubsection Symbol table representation in Python.
25760 @cindex symbol tables in python
25762 @tindex gdb.Symtab_and_line
25764 Access to symbol table data maintained by @value{GDBN} on the inferior
25765 is exposed to Python via two objects: @code{gdb.Symtab_and_line} and
25766 @code{gdb.Symtab}. Symbol table and line data for a frame is returned
25767 from the @code{find_sal} method in @code{gdb.Frame} object.
25768 @xref{Frames In Python}.
25770 For more information on @value{GDBN}'s symbol table management, see
25771 @ref{Symbols, ,Examining the Symbol Table}, for more information.
25773 A @code{gdb.Symtab_and_line} object has the following attributes:
25775 @defvar Symtab_and_line.symtab
25776 The symbol table object (@code{gdb.Symtab}) for this frame.
25777 This attribute is not writable.
25780 @defvar Symtab_and_line.pc
25781 Indicates the start of the address range occupied by code for the
25782 current source line. This attribute is not writable.
25785 @defvar Symtab_and_line.last
25786 Indicates the end of the address range occupied by code for the current
25787 source line. This attribute is not writable.
25790 @defvar Symtab_and_line.line
25791 Indicates the current line number for this object. This
25792 attribute is not writable.
25795 A @code{gdb.Symtab_and_line} object has the following methods:
25797 @defun Symtab_and_line.is_valid ()
25798 Returns @code{True} if the @code{gdb.Symtab_and_line} object is valid,
25799 @code{False} if not. A @code{gdb.Symtab_and_line} object can become
25800 invalid if the Symbol table and line object it refers to does not
25801 exist in @value{GDBN} any longer. All other
25802 @code{gdb.Symtab_and_line} methods will throw an exception if it is
25803 invalid at the time the method is called.
25806 A @code{gdb.Symtab} object has the following attributes:
25808 @defvar Symtab.filename
25809 The symbol table's source filename. This attribute is not writable.
25812 @defvar Symtab.objfile
25813 The symbol table's backing object file. @xref{Objfiles In Python}.
25814 This attribute is not writable.
25817 A @code{gdb.Symtab} object has the following methods:
25819 @defun Symtab.is_valid ()
25820 Returns @code{True} if the @code{gdb.Symtab} object is valid,
25821 @code{False} if not. A @code{gdb.Symtab} object can become invalid if
25822 the symbol table it refers to does not exist in @value{GDBN} any
25823 longer. All other @code{gdb.Symtab} methods will throw an exception
25824 if it is invalid at the time the method is called.
25827 @defun Symtab.fullname ()
25828 Return the symbol table's source absolute file name.
25831 @defun Symtab.global_block ()
25832 Return the global block of the underlying symbol table.
25833 @xref{Blocks In Python}.
25836 @defun Symtab.static_block ()
25837 Return the static block of the underlying symbol table.
25838 @xref{Blocks In Python}.
25841 @node Breakpoints In Python
25842 @subsubsection Manipulating breakpoints using Python
25844 @cindex breakpoints in python
25845 @tindex gdb.Breakpoint
25847 Python code can manipulate breakpoints via the @code{gdb.Breakpoint}
25850 @defun Breakpoint.__init__ (spec @r{[}, type @r{[}, wp_class @r{[},internal@r{]]]})
25851 Create a new breakpoint. @var{spec} is a string naming the
25852 location of the breakpoint, or an expression that defines a
25853 watchpoint. The contents can be any location recognized by the
25854 @code{break} command, or in the case of a watchpoint, by the @code{watch}
25855 command. The optional @var{type} denotes the breakpoint to create
25856 from the types defined later in this chapter. This argument can be
25857 either: @code{gdb.BP_BREAKPOINT} or @code{gdb.BP_WATCHPOINT}. @var{type}
25858 defaults to @code{gdb.BP_BREAKPOINT}. The optional @var{internal} argument
25859 allows the breakpoint to become invisible to the user. The breakpoint
25860 will neither be reported when created, nor will it be listed in the
25861 output from @code{info breakpoints} (but will be listed with the
25862 @code{maint info breakpoints} command). The optional @var{wp_class}
25863 argument defines the class of watchpoint to create, if @var{type} is
25864 @code{gdb.BP_WATCHPOINT}. If a watchpoint class is not provided, it is
25865 assumed to be a @code{gdb.WP_WRITE} class.
25868 @defun Breakpoint.stop (self)
25869 The @code{gdb.Breakpoint} class can be sub-classed and, in
25870 particular, you may choose to implement the @code{stop} method.
25871 If this method is defined as a sub-class of @code{gdb.Breakpoint},
25872 it will be called when the inferior reaches any location of a
25873 breakpoint which instantiates that sub-class. If the method returns
25874 @code{True}, the inferior will be stopped at the location of the
25875 breakpoint, otherwise the inferior will continue.
25877 If there are multiple breakpoints at the same location with a
25878 @code{stop} method, each one will be called regardless of the
25879 return status of the previous. This ensures that all @code{stop}
25880 methods have a chance to execute at that location. In this scenario
25881 if one of the methods returns @code{True} but the others return
25882 @code{False}, the inferior will still be stopped.
25884 You should not alter the execution state of the inferior (i.e.@:, step,
25885 next, etc.), alter the current frame context (i.e.@:, change the current
25886 active frame), or alter, add or delete any breakpoint. As a general
25887 rule, you should not alter any data within @value{GDBN} or the inferior
25890 Example @code{stop} implementation:
25893 class MyBreakpoint (gdb.Breakpoint):
25895 inf_val = gdb.parse_and_eval("foo")
25902 The available watchpoint types represented by constants are defined in the
25907 @findex gdb.WP_READ
25909 Read only watchpoint.
25912 @findex gdb.WP_WRITE
25914 Write only watchpoint.
25917 @findex gdb.WP_ACCESS
25918 @item gdb.WP_ACCESS
25919 Read/Write watchpoint.
25922 @defun Breakpoint.is_valid ()
25923 Return @code{True} if this @code{Breakpoint} object is valid,
25924 @code{False} otherwise. A @code{Breakpoint} object can become invalid
25925 if the user deletes the breakpoint. In this case, the object still
25926 exists, but the underlying breakpoint does not. In the cases of
25927 watchpoint scope, the watchpoint remains valid even if execution of the
25928 inferior leaves the scope of that watchpoint.
25931 @defun Breakpoint.delete
25932 Permanently deletes the @value{GDBN} breakpoint. This also
25933 invalidates the Python @code{Breakpoint} object. Any further access
25934 to this object's attributes or methods will raise an error.
25937 @defvar Breakpoint.enabled
25938 This attribute is @code{True} if the breakpoint is enabled, and
25939 @code{False} otherwise. This attribute is writable.
25942 @defvar Breakpoint.silent
25943 This attribute is @code{True} if the breakpoint is silent, and
25944 @code{False} otherwise. This attribute is writable.
25946 Note that a breakpoint can also be silent if it has commands and the
25947 first command is @code{silent}. This is not reported by the
25948 @code{silent} attribute.
25951 @defvar Breakpoint.thread
25952 If the breakpoint is thread-specific, this attribute holds the thread
25953 id. If the breakpoint is not thread-specific, this attribute is
25954 @code{None}. This attribute is writable.
25957 @defvar Breakpoint.task
25958 If the breakpoint is Ada task-specific, this attribute holds the Ada task
25959 id. If the breakpoint is not task-specific (or the underlying
25960 language is not Ada), this attribute is @code{None}. This attribute
25964 @defvar Breakpoint.ignore_count
25965 This attribute holds the ignore count for the breakpoint, an integer.
25966 This attribute is writable.
25969 @defvar Breakpoint.number
25970 This attribute holds the breakpoint's number --- the identifier used by
25971 the user to manipulate the breakpoint. This attribute is not writable.
25974 @defvar Breakpoint.type
25975 This attribute holds the breakpoint's type --- the identifier used to
25976 determine the actual breakpoint type or use-case. This attribute is not
25980 @defvar Breakpoint.visible
25981 This attribute tells whether the breakpoint is visible to the user
25982 when set, or when the @samp{info breakpoints} command is run. This
25983 attribute is not writable.
25986 The available types are represented by constants defined in the @code{gdb}
25990 @findex BP_BREAKPOINT
25991 @findex gdb.BP_BREAKPOINT
25992 @item gdb.BP_BREAKPOINT
25993 Normal code breakpoint.
25995 @findex BP_WATCHPOINT
25996 @findex gdb.BP_WATCHPOINT
25997 @item gdb.BP_WATCHPOINT
25998 Watchpoint breakpoint.
26000 @findex BP_HARDWARE_WATCHPOINT
26001 @findex gdb.BP_HARDWARE_WATCHPOINT
26002 @item gdb.BP_HARDWARE_WATCHPOINT
26003 Hardware assisted watchpoint.
26005 @findex BP_READ_WATCHPOINT
26006 @findex gdb.BP_READ_WATCHPOINT
26007 @item gdb.BP_READ_WATCHPOINT
26008 Hardware assisted read watchpoint.
26010 @findex BP_ACCESS_WATCHPOINT
26011 @findex gdb.BP_ACCESS_WATCHPOINT
26012 @item gdb.BP_ACCESS_WATCHPOINT
26013 Hardware assisted access watchpoint.
26016 @defvar Breakpoint.hit_count
26017 This attribute holds the hit count for the breakpoint, an integer.
26018 This attribute is writable, but currently it can only be set to zero.
26021 @defvar Breakpoint.location
26022 This attribute holds the location of the breakpoint, as specified by
26023 the user. It is a string. If the breakpoint does not have a location
26024 (that is, it is a watchpoint) the attribute's value is @code{None}. This
26025 attribute is not writable.
26028 @defvar Breakpoint.expression
26029 This attribute holds a breakpoint expression, as specified by
26030 the user. It is a string. If the breakpoint does not have an
26031 expression (the breakpoint is not a watchpoint) the attribute's value
26032 is @code{None}. This attribute is not writable.
26035 @defvar Breakpoint.condition
26036 This attribute holds the condition of the breakpoint, as specified by
26037 the user. It is a string. If there is no condition, this attribute's
26038 value is @code{None}. This attribute is writable.
26041 @defvar Breakpoint.commands
26042 This attribute holds the commands attached to the breakpoint. If
26043 there are commands, this attribute's value is a string holding all the
26044 commands, separated by newlines. If there are no commands, this
26045 attribute is @code{None}. This attribute is not writable.
26048 @node Finish Breakpoints in Python
26049 @subsubsection Finish Breakpoints
26051 @cindex python finish breakpoints
26052 @tindex gdb.FinishBreakpoint
26054 A finish breakpoint is a temporary breakpoint set at the return address of
26055 a frame, based on the @code{finish} command. @code{gdb.FinishBreakpoint}
26056 extends @code{gdb.Breakpoint}. The underlying breakpoint will be disabled
26057 and deleted when the execution will run out of the breakpoint scope (i.e.@:
26058 @code{Breakpoint.stop} or @code{FinishBreakpoint.out_of_scope} triggered).
26059 Finish breakpoints are thread specific and must be create with the right
26062 @defun FinishBreakpoint.__init__ (@r{[}frame@r{]} @r{[}, internal@r{]})
26063 Create a finish breakpoint at the return address of the @code{gdb.Frame}
26064 object @var{frame}. If @var{frame} is not provided, this defaults to the
26065 newest frame. The optional @var{internal} argument allows the breakpoint to
26066 become invisible to the user. @xref{Breakpoints In Python}, for further
26067 details about this argument.
26070 @defun FinishBreakpoint.out_of_scope (self)
26071 In some circumstances (e.g.@: @code{longjmp}, C@t{++} exceptions, @value{GDBN}
26072 @code{return} command, @dots{}), a function may not properly terminate, and
26073 thus never hit the finish breakpoint. When @value{GDBN} notices such a
26074 situation, the @code{out_of_scope} callback will be triggered.
26076 You may want to sub-class @code{gdb.FinishBreakpoint} and override this
26080 class MyFinishBreakpoint (gdb.FinishBreakpoint)
26082 print "normal finish"
26085 def out_of_scope ():
26086 print "abnormal finish"
26090 @defvar FinishBreakpoint.return_value
26091 When @value{GDBN} is stopped at a finish breakpoint and the frame
26092 used to build the @code{gdb.FinishBreakpoint} object had debug symbols, this
26093 attribute will contain a @code{gdb.Value} object corresponding to the return
26094 value of the function. The value will be @code{None} if the function return
26095 type is @code{void} or if the return value was not computable. This attribute
26099 @node Lazy Strings In Python
26100 @subsubsection Python representation of lazy strings.
26102 @cindex lazy strings in python
26103 @tindex gdb.LazyString
26105 A @dfn{lazy string} is a string whose contents is not retrieved or
26106 encoded until it is needed.
26108 A @code{gdb.LazyString} is represented in @value{GDBN} as an
26109 @code{address} that points to a region of memory, an @code{encoding}
26110 that will be used to encode that region of memory, and a @code{length}
26111 to delimit the region of memory that represents the string. The
26112 difference between a @code{gdb.LazyString} and a string wrapped within
26113 a @code{gdb.Value} is that a @code{gdb.LazyString} will be treated
26114 differently by @value{GDBN} when printing. A @code{gdb.LazyString} is
26115 retrieved and encoded during printing, while a @code{gdb.Value}
26116 wrapping a string is immediately retrieved and encoded on creation.
26118 A @code{gdb.LazyString} object has the following functions:
26120 @defun LazyString.value ()
26121 Convert the @code{gdb.LazyString} to a @code{gdb.Value}. This value
26122 will point to the string in memory, but will lose all the delayed
26123 retrieval, encoding and handling that @value{GDBN} applies to a
26124 @code{gdb.LazyString}.
26127 @defvar LazyString.address
26128 This attribute holds the address of the string. This attribute is not
26132 @defvar LazyString.length
26133 This attribute holds the length of the string in characters. If the
26134 length is -1, then the string will be fetched and encoded up to the
26135 first null of appropriate width. This attribute is not writable.
26138 @defvar LazyString.encoding
26139 This attribute holds the encoding that will be applied to the string
26140 when the string is printed by @value{GDBN}. If the encoding is not
26141 set, or contains an empty string, then @value{GDBN} will select the
26142 most appropriate encoding when the string is printed. This attribute
26146 @defvar LazyString.type
26147 This attribute holds the type that is represented by the lazy string's
26148 type. For a lazy string this will always be a pointer type. To
26149 resolve this to the lazy string's character type, use the type's
26150 @code{target} method. @xref{Types In Python}. This attribute is not
26154 @node Architectures In Python
26155 @subsubsection Python representation of architectures
26156 @cindex Python architectures
26158 @value{GDBN} uses architecture specific parameters and artifacts in a
26159 number of its various computations. An architecture is represented
26160 by an instance of the @code{gdb.Architecture} class.
26162 A @code{gdb.Architecture} class has the following methods:
26164 @defun Architecture.name ()
26165 Return the name (string value) of the architecture.
26168 @defun Architecture.disassemble (@var{start_pc} @r{[}, @var{end_pc} @r{[}, @var{count}@r{]]})
26169 Return a list of disassembled instructions starting from the memory
26170 address @var{start_pc}. The optional arguments @var{end_pc} and
26171 @var{count} determine the number of instructions in the returned list.
26172 If both the optional arguments @var{end_pc} and @var{count} are
26173 specified, then a list of at most @var{count} disassembled instructions
26174 whose start address falls in the closed memory address interval from
26175 @var{start_pc} to @var{end_pc} are returned. If @var{end_pc} is not
26176 specified, but @var{count} is specified, then @var{count} number of
26177 instructions starting from the address @var{start_pc} are returned. If
26178 @var{count} is not specified but @var{end_pc} is specified, then all
26179 instructions whose start address falls in the closed memory address
26180 interval from @var{start_pc} to @var{end_pc} are returned. If neither
26181 @var{end_pc} nor @var{count} are specified, then a single instruction at
26182 @var{start_pc} is returned. For all of these cases, each element of the
26183 returned list is a Python @code{dict} with the following string keys:
26188 The value corresponding to this key is a Python long integer capturing
26189 the memory address of the instruction.
26192 The value corresponding to this key is a string value which represents
26193 the instruction with assembly language mnemonics. The assembly
26194 language flavor used is the same as that specified by the current CLI
26195 variable @code{disassembly-flavor}. @xref{Machine Code}.
26198 The value corresponding to this key is the length (integer value) of the
26199 instruction in bytes.
26204 @node Python Auto-loading
26205 @subsection Python Auto-loading
26206 @cindex Python auto-loading
26208 When a new object file is read (for example, due to the @code{file}
26209 command, or because the inferior has loaded a shared library),
26210 @value{GDBN} will look for Python support scripts in several ways:
26211 @file{@var{objfile}-gdb.py} (@pxref{objfile-gdb.py file})
26212 and @code{.debug_gdb_scripts} section
26213 (@pxref{dotdebug_gdb_scripts section}).
26215 The auto-loading feature is useful for supplying application-specific
26216 debugging commands and scripts.
26218 Auto-loading can be enabled or disabled,
26219 and the list of auto-loaded scripts can be printed.
26222 @anchor{set auto-load python-scripts}
26223 @kindex set auto-load python-scripts
26224 @item set auto-load python-scripts [on|off]
26225 Enable or disable the auto-loading of Python scripts.
26227 @anchor{show auto-load python-scripts}
26228 @kindex show auto-load python-scripts
26229 @item show auto-load python-scripts
26230 Show whether auto-loading of Python scripts is enabled or disabled.
26232 @anchor{info auto-load python-scripts}
26233 @kindex info auto-load python-scripts
26234 @cindex print list of auto-loaded Python scripts
26235 @item info auto-load python-scripts [@var{regexp}]
26236 Print the list of all Python scripts that @value{GDBN} auto-loaded.
26238 Also printed is the list of Python scripts that were mentioned in
26239 the @code{.debug_gdb_scripts} section and were not found
26240 (@pxref{dotdebug_gdb_scripts section}).
26241 This is useful because their names are not printed when @value{GDBN}
26242 tries to load them and fails. There may be many of them, and printing
26243 an error message for each one is problematic.
26245 If @var{regexp} is supplied only Python scripts with matching names are printed.
26250 (gdb) info auto-load python-scripts
26252 Yes py-section-script.py
26253 full name: /tmp/py-section-script.py
26254 No my-foo-pretty-printers.py
26258 When reading an auto-loaded file, @value{GDBN} sets the
26259 @dfn{current objfile}. This is available via the @code{gdb.current_objfile}
26260 function (@pxref{Objfiles In Python}). This can be useful for
26261 registering objfile-specific pretty-printers.
26264 * objfile-gdb.py file:: The @file{@var{objfile}-gdb.py} file
26265 * dotdebug_gdb_scripts section:: The @code{.debug_gdb_scripts} section
26266 * Which flavor to choose?::
26269 @node objfile-gdb.py file
26270 @subsubsection The @file{@var{objfile}-gdb.py} file
26271 @cindex @file{@var{objfile}-gdb.py}
26273 When a new object file is read, @value{GDBN} looks for
26274 a file named @file{@var{objfile}-gdb.py} (we call it @var{script-name} below),
26275 where @var{objfile} is the object file's real name, formed by ensuring
26276 that the file name is absolute, following all symlinks, and resolving
26277 @code{.} and @code{..} components. If this file exists and is
26278 readable, @value{GDBN} will evaluate it as a Python script.
26280 If this file does not exist, then @value{GDBN} will look for
26281 @var{script-name} file in all of the directories as specified below.
26283 Note that loading of this script file also requires accordingly configured
26284 @code{auto-load safe-path} (@pxref{Auto-loading safe path}).
26286 For object files using @file{.exe} suffix @value{GDBN} tries to load first the
26287 scripts normally according to its @file{.exe} filename. But if no scripts are
26288 found @value{GDBN} also tries script filenames matching the object file without
26289 its @file{.exe} suffix. This @file{.exe} stripping is case insensitive and it
26290 is attempted on any platform. This makes the script filenames compatible
26291 between Unix and MS-Windows hosts.
26294 @anchor{set auto-load scripts-directory}
26295 @kindex set auto-load scripts-directory
26296 @item set auto-load scripts-directory @r{[}@var{directories}@r{]}
26297 Control @value{GDBN} auto-loaded scripts location. Multiple directory entries
26298 may be delimited by the host platform path separator in use
26299 (@samp{:} on Unix, @samp{;} on MS-Windows and MS-DOS).
26301 Each entry here needs to be covered also by the security setting
26302 @code{set auto-load safe-path} (@pxref{set auto-load safe-path}).
26304 @anchor{with-auto-load-dir}
26305 This variable defaults to @file{$debugdir:$datadir/auto-load}. The default
26306 @code{set auto-load safe-path} value can be also overriden by @value{GDBN}
26307 configuration option @option{--with-auto-load-dir}.
26309 Any reference to @file{$debugdir} will get replaced by
26310 @var{debug-file-directory} value (@pxref{Separate Debug Files}) and any
26311 reference to @file{$datadir} will get replaced by @var{data-directory} which is
26312 determined at @value{GDBN} startup (@pxref{Data Files}). @file{$debugdir} and
26313 @file{$datadir} must be placed as a directory component --- either alone or
26314 delimited by @file{/} or @file{\} directory separators, depending on the host
26317 The list of directories uses path separator (@samp{:} on GNU and Unix
26318 systems, @samp{;} on MS-Windows and MS-DOS) to separate directories, similarly
26319 to the @env{PATH} environment variable.
26321 @anchor{show auto-load scripts-directory}
26322 @kindex show auto-load scripts-directory
26323 @item show auto-load scripts-directory
26324 Show @value{GDBN} auto-loaded scripts location.
26327 @value{GDBN} does not track which files it has already auto-loaded this way.
26328 @value{GDBN} will load the associated script every time the corresponding
26329 @var{objfile} is opened.
26330 So your @file{-gdb.py} file should be careful to avoid errors if it
26331 is evaluated more than once.
26333 @node dotdebug_gdb_scripts section
26334 @subsubsection The @code{.debug_gdb_scripts} section
26335 @cindex @code{.debug_gdb_scripts} section
26337 For systems using file formats like ELF and COFF,
26338 when @value{GDBN} loads a new object file
26339 it will look for a special section named @samp{.debug_gdb_scripts}.
26340 If this section exists, its contents is a list of names of scripts to load.
26342 @value{GDBN} will look for each specified script file first in the
26343 current directory and then along the source search path
26344 (@pxref{Source Path, ,Specifying Source Directories}),
26345 except that @file{$cdir} is not searched, since the compilation
26346 directory is not relevant to scripts.
26348 Entries can be placed in section @code{.debug_gdb_scripts} with,
26349 for example, this GCC macro:
26352 /* Note: The "MS" section flags are to remove duplicates. */
26353 #define DEFINE_GDB_SCRIPT(script_name) \
26355 .pushsection \".debug_gdb_scripts\", \"MS\",@@progbits,1\n\
26357 .asciz \"" script_name "\"\n\
26363 Then one can reference the macro in a header or source file like this:
26366 DEFINE_GDB_SCRIPT ("my-app-scripts.py")
26369 The script name may include directories if desired.
26371 Note that loading of this script file also requires accordingly configured
26372 @code{auto-load safe-path} (@pxref{Auto-loading safe path}).
26374 If the macro is put in a header, any application or library
26375 using this header will get a reference to the specified script.
26377 @node Which flavor to choose?
26378 @subsubsection Which flavor to choose?
26380 Given the multiple ways of auto-loading Python scripts, it might not always
26381 be clear which one to choose. This section provides some guidance.
26383 Benefits of the @file{-gdb.py} way:
26387 Can be used with file formats that don't support multiple sections.
26390 Ease of finding scripts for public libraries.
26392 Scripts specified in the @code{.debug_gdb_scripts} section are searched for
26393 in the source search path.
26394 For publicly installed libraries, e.g., @file{libstdc++}, there typically
26395 isn't a source directory in which to find the script.
26398 Doesn't require source code additions.
26401 Benefits of the @code{.debug_gdb_scripts} way:
26405 Works with static linking.
26407 Scripts for libraries done the @file{-gdb.py} way require an objfile to
26408 trigger their loading. When an application is statically linked the only
26409 objfile available is the executable, and it is cumbersome to attach all the
26410 scripts from all the input libraries to the executable's @file{-gdb.py} script.
26413 Works with classes that are entirely inlined.
26415 Some classes can be entirely inlined, and thus there may not be an associated
26416 shared library to attach a @file{-gdb.py} script to.
26419 Scripts needn't be copied out of the source tree.
26421 In some circumstances, apps can be built out of large collections of internal
26422 libraries, and the build infrastructure necessary to install the
26423 @file{-gdb.py} scripts in a place where @value{GDBN} can find them is
26424 cumbersome. It may be easier to specify the scripts in the
26425 @code{.debug_gdb_scripts} section as relative paths, and add a path to the
26426 top of the source tree to the source search path.
26429 @node Python modules
26430 @subsection Python modules
26431 @cindex python modules
26433 @value{GDBN} comes with several modules to assist writing Python code.
26436 * gdb.printing:: Building and registering pretty-printers.
26437 * gdb.types:: Utilities for working with types.
26438 * gdb.prompt:: Utilities for prompt value substitution.
26442 @subsubsection gdb.printing
26443 @cindex gdb.printing
26445 This module provides a collection of utilities for working with
26449 @item PrettyPrinter (@var{name}, @var{subprinters}=None)
26450 This class specifies the API that makes @samp{info pretty-printer},
26451 @samp{enable pretty-printer} and @samp{disable pretty-printer} work.
26452 Pretty-printers should generally inherit from this class.
26454 @item SubPrettyPrinter (@var{name})
26455 For printers that handle multiple types, this class specifies the
26456 corresponding API for the subprinters.
26458 @item RegexpCollectionPrettyPrinter (@var{name})
26459 Utility class for handling multiple printers, all recognized via
26460 regular expressions.
26461 @xref{Writing a Pretty-Printer}, for an example.
26463 @item FlagEnumerationPrinter (@var{name})
26464 A pretty-printer which handles printing of @code{enum} values. Unlike
26465 @value{GDBN}'s built-in @code{enum} printing, this printer attempts to
26466 work properly when there is some overlap between the enumeration
26467 constants. @var{name} is the name of the printer and also the name of
26468 the @code{enum} type to look up.
26470 @item register_pretty_printer (@var{obj}, @var{printer}, @var{replace}=False)
26471 Register @var{printer} with the pretty-printer list of @var{obj}.
26472 If @var{replace} is @code{True} then any existing copy of the printer
26473 is replaced. Otherwise a @code{RuntimeError} exception is raised
26474 if a printer with the same name already exists.
26478 @subsubsection gdb.types
26481 This module provides a collection of utilities for working with
26482 @code{gdb.Type} objects.
26485 @item get_basic_type (@var{type})
26486 Return @var{type} with const and volatile qualifiers stripped,
26487 and with typedefs and C@t{++} references converted to the underlying type.
26492 typedef const int const_int;
26494 const_int& foo_ref (foo);
26495 int main () @{ return 0; @}
26502 (gdb) python import gdb.types
26503 (gdb) python foo_ref = gdb.parse_and_eval("foo_ref")
26504 (gdb) python print gdb.types.get_basic_type(foo_ref.type)
26508 @item has_field (@var{type}, @var{field})
26509 Return @code{True} if @var{type}, assumed to be a type with fields
26510 (e.g., a structure or union), has field @var{field}.
26512 @item make_enum_dict (@var{enum_type})
26513 Return a Python @code{dictionary} type produced from @var{enum_type}.
26515 @item deep_items (@var{type})
26516 Returns a Python iterator similar to the standard
26517 @code{gdb.Type.iteritems} method, except that the iterator returned
26518 by @code{deep_items} will recursively traverse anonymous struct or
26519 union fields. For example:
26533 Then in @value{GDBN}:
26535 (@value{GDBP}) python import gdb.types
26536 (@value{GDBP}) python struct_a = gdb.lookup_type("struct A")
26537 (@value{GDBP}) python print struct_a.keys ()
26539 (@value{GDBP}) python print [k for k,v in gdb.types.deep_items(struct_a)]
26540 @{['a', 'b0', 'b1']@}
26543 @item get_type_recognizers ()
26544 Return a list of the enabled type recognizers for the current context.
26545 This is called by @value{GDBN} during the type-printing process
26546 (@pxref{Type Printing API}).
26548 @item apply_type_recognizers (recognizers, type_obj)
26549 Apply the type recognizers, @var{recognizers}, to the type object
26550 @var{type_obj}. If any recognizer returns a string, return that
26551 string. Otherwise, return @code{None}. This is called by
26552 @value{GDBN} during the type-printing process (@pxref{Type Printing
26555 @item register_type_printer (locus, printer)
26556 This is a convenience function to register a type printer.
26557 @var{printer} is the type printer to register. It must implement the
26558 type printer protocol. @var{locus} is either a @code{gdb.Objfile}, in
26559 which case the printer is registered with that objfile; a
26560 @code{gdb.Progspace}, in which case the printer is registered with
26561 that progspace; or @code{None}, in which case the printer is
26562 registered globally.
26565 This is a base class that implements the type printer protocol. Type
26566 printers are encouraged, but not required, to derive from this class.
26567 It defines a constructor:
26569 @defmethod TypePrinter __init__ (self, name)
26570 Initialize the type printer with the given name. The new printer
26571 starts in the enabled state.
26577 @subsubsection gdb.prompt
26580 This module provides a method for prompt value-substitution.
26583 @item substitute_prompt (@var{string})
26584 Return @var{string} with escape sequences substituted by values. Some
26585 escape sequences take arguments. You can specify arguments inside
26586 ``@{@}'' immediately following the escape sequence.
26588 The escape sequences you can pass to this function are:
26592 Substitute a backslash.
26594 Substitute an ESC character.
26596 Substitute the selected frame; an argument names a frame parameter.
26598 Substitute a newline.
26600 Substitute a parameter's value; the argument names the parameter.
26602 Substitute a carriage return.
26604 Substitute the selected thread; an argument names a thread parameter.
26606 Substitute the version of GDB.
26608 Substitute the current working directory.
26610 Begin a sequence of non-printing characters. These sequences are
26611 typically used with the ESC character, and are not counted in the string
26612 length. Example: ``\[\e[0;34m\](gdb)\[\e[0m\]'' will return a
26613 blue-colored ``(gdb)'' prompt where the length is five.
26615 End a sequence of non-printing characters.
26621 substitute_prompt (``frame: \f,
26622 print arguments: \p@{print frame-arguments@}'')
26625 @exdent will return the string:
26628 "frame: main, print arguments: scalars"
26633 @section Creating new spellings of existing commands
26634 @cindex aliases for commands
26636 It is often useful to define alternate spellings of existing commands.
26637 For example, if a new @value{GDBN} command defined in Python has
26638 a long name to type, it is handy to have an abbreviated version of it
26639 that involves less typing.
26641 @value{GDBN} itself uses aliases. For example @samp{s} is an alias
26642 of the @samp{step} command even though it is otherwise an ambiguous
26643 abbreviation of other commands like @samp{set} and @samp{show}.
26645 Aliases are also used to provide shortened or more common versions
26646 of multi-word commands. For example, @value{GDBN} provides the
26647 @samp{tty} alias of the @samp{set inferior-tty} command.
26649 You can define a new alias with the @samp{alias} command.
26654 @item alias [-a] [--] @var{ALIAS} = @var{COMMAND}
26658 @var{ALIAS} specifies the name of the new alias.
26659 Each word of @var{ALIAS} must consist of letters, numbers, dashes and
26662 @var{COMMAND} specifies the name of an existing command
26663 that is being aliased.
26665 The @samp{-a} option specifies that the new alias is an abbreviation
26666 of the command. Abbreviations are not shown in command
26667 lists displayed by the @samp{help} command.
26669 The @samp{--} option specifies the end of options,
26670 and is useful when @var{ALIAS} begins with a dash.
26672 Here is a simple example showing how to make an abbreviation
26673 of a command so that there is less to type.
26674 Suppose you were tired of typing @samp{disas}, the current
26675 shortest unambiguous abbreviation of the @samp{disassemble} command
26676 and you wanted an even shorter version named @samp{di}.
26677 The following will accomplish this.
26680 (gdb) alias -a di = disas
26683 Note that aliases are different from user-defined commands.
26684 With a user-defined command, you also need to write documentation
26685 for it with the @samp{document} command.
26686 An alias automatically picks up the documentation of the existing command.
26688 Here is an example where we make @samp{elms} an abbreviation of
26689 @samp{elements} in the @samp{set print elements} command.
26690 This is to show that you can make an abbreviation of any part
26694 (gdb) alias -a set print elms = set print elements
26695 (gdb) alias -a show print elms = show print elements
26696 (gdb) set p elms 20
26698 Limit on string chars or array elements to print is 200.
26701 Note that if you are defining an alias of a @samp{set} command,
26702 and you want to have an alias for the corresponding @samp{show}
26703 command, then you need to define the latter separately.
26705 Unambiguously abbreviated commands are allowed in @var{COMMAND} and
26706 @var{ALIAS}, just as they are normally.
26709 (gdb) alias -a set pr elms = set p ele
26712 Finally, here is an example showing the creation of a one word
26713 alias for a more complex command.
26714 This creates alias @samp{spe} of the command @samp{set print elements}.
26717 (gdb) alias spe = set print elements
26722 @chapter Command Interpreters
26723 @cindex command interpreters
26725 @value{GDBN} supports multiple command interpreters, and some command
26726 infrastructure to allow users or user interface writers to switch
26727 between interpreters or run commands in other interpreters.
26729 @value{GDBN} currently supports two command interpreters, the console
26730 interpreter (sometimes called the command-line interpreter or @sc{cli})
26731 and the machine interface interpreter (or @sc{gdb/mi}). This manual
26732 describes both of these interfaces in great detail.
26734 By default, @value{GDBN} will start with the console interpreter.
26735 However, the user may choose to start @value{GDBN} with another
26736 interpreter by specifying the @option{-i} or @option{--interpreter}
26737 startup options. Defined interpreters include:
26741 @cindex console interpreter
26742 The traditional console or command-line interpreter. This is the most often
26743 used interpreter with @value{GDBN}. With no interpreter specified at runtime,
26744 @value{GDBN} will use this interpreter.
26747 @cindex mi interpreter
26748 The newest @sc{gdb/mi} interface (currently @code{mi2}). Used primarily
26749 by programs wishing to use @value{GDBN} as a backend for a debugger GUI
26750 or an IDE. For more information, see @ref{GDB/MI, ,The @sc{gdb/mi}
26754 @cindex mi2 interpreter
26755 The current @sc{gdb/mi} interface.
26758 @cindex mi1 interpreter
26759 The @sc{gdb/mi} interface included in @value{GDBN} 5.1, 5.2, and 5.3.
26763 @cindex invoke another interpreter
26764 The interpreter being used by @value{GDBN} may not be dynamically
26765 switched at runtime. Although possible, this could lead to a very
26766 precarious situation. Consider an IDE using @sc{gdb/mi}. If a user
26767 enters the command "interpreter-set console" in a console view,
26768 @value{GDBN} would switch to using the console interpreter, rendering
26769 the IDE inoperable!
26771 @kindex interpreter-exec
26772 Although you may only choose a single interpreter at startup, you may execute
26773 commands in any interpreter from the current interpreter using the appropriate
26774 command. If you are running the console interpreter, simply use the
26775 @code{interpreter-exec} command:
26778 interpreter-exec mi "-data-list-register-names"
26781 @sc{gdb/mi} has a similar command, although it is only available in versions of
26782 @value{GDBN} which support @sc{gdb/mi} version 2 (or greater).
26785 @chapter @value{GDBN} Text User Interface
26787 @cindex Text User Interface
26790 * TUI Overview:: TUI overview
26791 * TUI Keys:: TUI key bindings
26792 * TUI Single Key Mode:: TUI single key mode
26793 * TUI Commands:: TUI-specific commands
26794 * TUI Configuration:: TUI configuration variables
26797 The @value{GDBN} Text User Interface (TUI) is a terminal
26798 interface which uses the @code{curses} library to show the source
26799 file, the assembly output, the program registers and @value{GDBN}
26800 commands in separate text windows. The TUI mode is supported only
26801 on platforms where a suitable version of the @code{curses} library
26804 The TUI mode is enabled by default when you invoke @value{GDBN} as
26805 @samp{@value{GDBP} -tui}.
26806 You can also switch in and out of TUI mode while @value{GDBN} runs by
26807 using various TUI commands and key bindings, such as @kbd{C-x C-a}.
26808 @xref{TUI Keys, ,TUI Key Bindings}.
26811 @section TUI Overview
26813 In TUI mode, @value{GDBN} can display several text windows:
26817 This window is the @value{GDBN} command window with the @value{GDBN}
26818 prompt and the @value{GDBN} output. The @value{GDBN} input is still
26819 managed using readline.
26822 The source window shows the source file of the program. The current
26823 line and active breakpoints are displayed in this window.
26826 The assembly window shows the disassembly output of the program.
26829 This window shows the processor registers. Registers are highlighted
26830 when their values change.
26833 The source and assembly windows show the current program position
26834 by highlighting the current line and marking it with a @samp{>} marker.
26835 Breakpoints are indicated with two markers. The first marker
26836 indicates the breakpoint type:
26840 Breakpoint which was hit at least once.
26843 Breakpoint which was never hit.
26846 Hardware breakpoint which was hit at least once.
26849 Hardware breakpoint which was never hit.
26852 The second marker indicates whether the breakpoint is enabled or not:
26856 Breakpoint is enabled.
26859 Breakpoint is disabled.
26862 The source, assembly and register windows are updated when the current
26863 thread changes, when the frame changes, or when the program counter
26866 These windows are not all visible at the same time. The command
26867 window is always visible. The others can be arranged in several
26878 source and assembly,
26881 source and registers, or
26884 assembly and registers.
26887 A status line above the command window shows the following information:
26891 Indicates the current @value{GDBN} target.
26892 (@pxref{Targets, ,Specifying a Debugging Target}).
26895 Gives the current process or thread number.
26896 When no process is being debugged, this field is set to @code{No process}.
26899 Gives the current function name for the selected frame.
26900 The name is demangled if demangling is turned on (@pxref{Print Settings}).
26901 When there is no symbol corresponding to the current program counter,
26902 the string @code{??} is displayed.
26905 Indicates the current line number for the selected frame.
26906 When the current line number is not known, the string @code{??} is displayed.
26909 Indicates the current program counter address.
26913 @section TUI Key Bindings
26914 @cindex TUI key bindings
26916 The TUI installs several key bindings in the readline keymaps
26917 @ifset SYSTEM_READLINE
26918 (@pxref{Command Line Editing, , , rluserman, GNU Readline Library}).
26920 @ifclear SYSTEM_READLINE
26921 (@pxref{Command Line Editing}).
26923 The following key bindings are installed for both TUI mode and the
26924 @value{GDBN} standard mode.
26933 Enter or leave the TUI mode. When leaving the TUI mode,
26934 the curses window management stops and @value{GDBN} operates using
26935 its standard mode, writing on the terminal directly. When reentering
26936 the TUI mode, control is given back to the curses windows.
26937 The screen is then refreshed.
26941 Use a TUI layout with only one window. The layout will
26942 either be @samp{source} or @samp{assembly}. When the TUI mode
26943 is not active, it will switch to the TUI mode.
26945 Think of this key binding as the Emacs @kbd{C-x 1} binding.
26949 Use a TUI layout with at least two windows. When the current
26950 layout already has two windows, the next layout with two windows is used.
26951 When a new layout is chosen, one window will always be common to the
26952 previous layout and the new one.
26954 Think of it as the Emacs @kbd{C-x 2} binding.
26958 Change the active window. The TUI associates several key bindings
26959 (like scrolling and arrow keys) with the active window. This command
26960 gives the focus to the next TUI window.
26962 Think of it as the Emacs @kbd{C-x o} binding.
26966 Switch in and out of the TUI SingleKey mode that binds single
26967 keys to @value{GDBN} commands (@pxref{TUI Single Key Mode}).
26970 The following key bindings only work in the TUI mode:
26975 Scroll the active window one page up.
26979 Scroll the active window one page down.
26983 Scroll the active window one line up.
26987 Scroll the active window one line down.
26991 Scroll the active window one column left.
26995 Scroll the active window one column right.
26999 Refresh the screen.
27002 Because the arrow keys scroll the active window in the TUI mode, they
27003 are not available for their normal use by readline unless the command
27004 window has the focus. When another window is active, you must use
27005 other readline key bindings such as @kbd{C-p}, @kbd{C-n}, @kbd{C-b}
27006 and @kbd{C-f} to control the command window.
27008 @node TUI Single Key Mode
27009 @section TUI Single Key Mode
27010 @cindex TUI single key mode
27012 The TUI also provides a @dfn{SingleKey} mode, which binds several
27013 frequently used @value{GDBN} commands to single keys. Type @kbd{C-x s} to
27014 switch into this mode, where the following key bindings are used:
27017 @kindex c @r{(SingleKey TUI key)}
27021 @kindex d @r{(SingleKey TUI key)}
27025 @kindex f @r{(SingleKey TUI key)}
27029 @kindex n @r{(SingleKey TUI key)}
27033 @kindex q @r{(SingleKey TUI key)}
27035 exit the SingleKey mode.
27037 @kindex r @r{(SingleKey TUI key)}
27041 @kindex s @r{(SingleKey TUI key)}
27045 @kindex u @r{(SingleKey TUI key)}
27049 @kindex v @r{(SingleKey TUI key)}
27053 @kindex w @r{(SingleKey TUI key)}
27058 Other keys temporarily switch to the @value{GDBN} command prompt.
27059 The key that was pressed is inserted in the editing buffer so that
27060 it is possible to type most @value{GDBN} commands without interaction
27061 with the TUI SingleKey mode. Once the command is entered the TUI
27062 SingleKey mode is restored. The only way to permanently leave
27063 this mode is by typing @kbd{q} or @kbd{C-x s}.
27067 @section TUI-specific Commands
27068 @cindex TUI commands
27070 The TUI has specific commands to control the text windows.
27071 These commands are always available, even when @value{GDBN} is not in
27072 the TUI mode. When @value{GDBN} is in the standard mode, most
27073 of these commands will automatically switch to the TUI mode.
27075 Note that if @value{GDBN}'s @code{stdout} is not connected to a
27076 terminal, or @value{GDBN} has been started with the machine interface
27077 interpreter (@pxref{GDB/MI, ,The @sc{gdb/mi} Interface}), most of
27078 these commands will fail with an error, because it would not be
27079 possible or desirable to enable curses window management.
27084 List and give the size of all displayed windows.
27088 Display the next layout.
27091 Display the previous layout.
27094 Display the source window only.
27097 Display the assembly window only.
27100 Display the source and assembly window.
27103 Display the register window together with the source or assembly window.
27107 Make the next window active for scrolling.
27110 Make the previous window active for scrolling.
27113 Make the source window active for scrolling.
27116 Make the assembly window active for scrolling.
27119 Make the register window active for scrolling.
27122 Make the command window active for scrolling.
27126 Refresh the screen. This is similar to typing @kbd{C-L}.
27128 @item tui reg float
27130 Show the floating point registers in the register window.
27132 @item tui reg general
27133 Show the general registers in the register window.
27136 Show the next register group. The list of register groups as well as
27137 their order is target specific. The predefined register groups are the
27138 following: @code{general}, @code{float}, @code{system}, @code{vector},
27139 @code{all}, @code{save}, @code{restore}.
27141 @item tui reg system
27142 Show the system registers in the register window.
27146 Update the source window and the current execution point.
27148 @item winheight @var{name} +@var{count}
27149 @itemx winheight @var{name} -@var{count}
27151 Change the height of the window @var{name} by @var{count}
27152 lines. Positive counts increase the height, while negative counts
27155 @item tabset @var{nchars}
27157 Set the width of tab stops to be @var{nchars} characters.
27160 @node TUI Configuration
27161 @section TUI Configuration Variables
27162 @cindex TUI configuration variables
27164 Several configuration variables control the appearance of TUI windows.
27167 @item set tui border-kind @var{kind}
27168 @kindex set tui border-kind
27169 Select the border appearance for the source, assembly and register windows.
27170 The possible values are the following:
27173 Use a space character to draw the border.
27176 Use @sc{ascii} characters @samp{+}, @samp{-} and @samp{|} to draw the border.
27179 Use the Alternate Character Set to draw the border. The border is
27180 drawn using character line graphics if the terminal supports them.
27183 @item set tui border-mode @var{mode}
27184 @kindex set tui border-mode
27185 @itemx set tui active-border-mode @var{mode}
27186 @kindex set tui active-border-mode
27187 Select the display attributes for the borders of the inactive windows
27188 or the active window. The @var{mode} can be one of the following:
27191 Use normal attributes to display the border.
27197 Use reverse video mode.
27200 Use half bright mode.
27202 @item half-standout
27203 Use half bright and standout mode.
27206 Use extra bright or bold mode.
27208 @item bold-standout
27209 Use extra bright or bold and standout mode.
27214 @chapter Using @value{GDBN} under @sc{gnu} Emacs
27217 @cindex @sc{gnu} Emacs
27218 A special interface allows you to use @sc{gnu} Emacs to view (and
27219 edit) the source files for the program you are debugging with
27222 To use this interface, use the command @kbd{M-x gdb} in Emacs. Give the
27223 executable file you want to debug as an argument. This command starts
27224 @value{GDBN} as a subprocess of Emacs, with input and output through a newly
27225 created Emacs buffer.
27226 @c (Do not use the @code{-tui} option to run @value{GDBN} from Emacs.)
27228 Running @value{GDBN} under Emacs can be just like running @value{GDBN} normally except for two
27233 All ``terminal'' input and output goes through an Emacs buffer, called
27236 This applies both to @value{GDBN} commands and their output, and to the input
27237 and output done by the program you are debugging.
27239 This is useful because it means that you can copy the text of previous
27240 commands and input them again; you can even use parts of the output
27243 All the facilities of Emacs' Shell mode are available for interacting
27244 with your program. In particular, you can send signals the usual
27245 way---for example, @kbd{C-c C-c} for an interrupt, @kbd{C-c C-z} for a
27249 @value{GDBN} displays source code through Emacs.
27251 Each time @value{GDBN} displays a stack frame, Emacs automatically finds the
27252 source file for that frame and puts an arrow (@samp{=>}) at the
27253 left margin of the current line. Emacs uses a separate buffer for
27254 source display, and splits the screen to show both your @value{GDBN} session
27257 Explicit @value{GDBN} @code{list} or search commands still produce output as
27258 usual, but you probably have no reason to use them from Emacs.
27261 We call this @dfn{text command mode}. Emacs 22.1, and later, also uses
27262 a graphical mode, enabled by default, which provides further buffers
27263 that can control the execution and describe the state of your program.
27264 @xref{GDB Graphical Interface,,, Emacs, The @sc{gnu} Emacs Manual}.
27266 If you specify an absolute file name when prompted for the @kbd{M-x
27267 gdb} argument, then Emacs sets your current working directory to where
27268 your program resides. If you only specify the file name, then Emacs
27269 sets your current working directory to the directory associated
27270 with the previous buffer. In this case, @value{GDBN} may find your
27271 program by searching your environment's @code{PATH} variable, but on
27272 some operating systems it might not find the source. So, although the
27273 @value{GDBN} input and output session proceeds normally, the auxiliary
27274 buffer does not display the current source and line of execution.
27276 The initial working directory of @value{GDBN} is printed on the top
27277 line of the GUD buffer and this serves as a default for the commands
27278 that specify files for @value{GDBN} to operate on. @xref{Files,
27279 ,Commands to Specify Files}.
27281 By default, @kbd{M-x gdb} calls the program called @file{gdb}. If you
27282 need to call @value{GDBN} by a different name (for example, if you
27283 keep several configurations around, with different names) you can
27284 customize the Emacs variable @code{gud-gdb-command-name} to run the
27287 In the GUD buffer, you can use these special Emacs commands in
27288 addition to the standard Shell mode commands:
27292 Describe the features of Emacs' GUD Mode.
27295 Execute to another source line, like the @value{GDBN} @code{step} command; also
27296 update the display window to show the current file and location.
27299 Execute to next source line in this function, skipping all function
27300 calls, like the @value{GDBN} @code{next} command. Then update the display window
27301 to show the current file and location.
27304 Execute one instruction, like the @value{GDBN} @code{stepi} command; update
27305 display window accordingly.
27308 Execute until exit from the selected stack frame, like the @value{GDBN}
27309 @code{finish} command.
27312 Continue execution of your program, like the @value{GDBN} @code{continue}
27316 Go up the number of frames indicated by the numeric argument
27317 (@pxref{Arguments, , Numeric Arguments, Emacs, The @sc{gnu} Emacs Manual}),
27318 like the @value{GDBN} @code{up} command.
27321 Go down the number of frames indicated by the numeric argument, like the
27322 @value{GDBN} @code{down} command.
27325 In any source file, the Emacs command @kbd{C-x @key{SPC}} (@code{gud-break})
27326 tells @value{GDBN} to set a breakpoint on the source line point is on.
27328 In text command mode, if you type @kbd{M-x speedbar}, Emacs displays a
27329 separate frame which shows a backtrace when the GUD buffer is current.
27330 Move point to any frame in the stack and type @key{RET} to make it
27331 become the current frame and display the associated source in the
27332 source buffer. Alternatively, click @kbd{Mouse-2} to make the
27333 selected frame become the current one. In graphical mode, the
27334 speedbar displays watch expressions.
27336 If you accidentally delete the source-display buffer, an easy way to get
27337 it back is to type the command @code{f} in the @value{GDBN} buffer, to
27338 request a frame display; when you run under Emacs, this recreates
27339 the source buffer if necessary to show you the context of the current
27342 The source files displayed in Emacs are in ordinary Emacs buffers
27343 which are visiting the source files in the usual way. You can edit
27344 the files with these buffers if you wish; but keep in mind that @value{GDBN}
27345 communicates with Emacs in terms of line numbers. If you add or
27346 delete lines from the text, the line numbers that @value{GDBN} knows cease
27347 to correspond properly with the code.
27349 A more detailed description of Emacs' interaction with @value{GDBN} is
27350 given in the Emacs manual (@pxref{Debuggers,,, Emacs, The @sc{gnu}
27354 @chapter The @sc{gdb/mi} Interface
27356 @unnumberedsec Function and Purpose
27358 @cindex @sc{gdb/mi}, its purpose
27359 @sc{gdb/mi} is a line based machine oriented text interface to
27360 @value{GDBN} and is activated by specifying using the
27361 @option{--interpreter} command line option (@pxref{Mode Options}). It
27362 is specifically intended to support the development of systems which
27363 use the debugger as just one small component of a larger system.
27365 This chapter is a specification of the @sc{gdb/mi} interface. It is written
27366 in the form of a reference manual.
27368 Note that @sc{gdb/mi} is still under construction, so some of the
27369 features described below are incomplete and subject to change
27370 (@pxref{GDB/MI Development and Front Ends, , @sc{gdb/mi} Development and Front Ends}).
27372 @unnumberedsec Notation and Terminology
27374 @cindex notational conventions, for @sc{gdb/mi}
27375 This chapter uses the following notation:
27379 @code{|} separates two alternatives.
27382 @code{[ @var{something} ]} indicates that @var{something} is optional:
27383 it may or may not be given.
27386 @code{( @var{group} )*} means that @var{group} inside the parentheses
27387 may repeat zero or more times.
27390 @code{( @var{group} )+} means that @var{group} inside the parentheses
27391 may repeat one or more times.
27394 @code{"@var{string}"} means a literal @var{string}.
27398 @heading Dependencies
27402 * GDB/MI General Design::
27403 * GDB/MI Command Syntax::
27404 * GDB/MI Compatibility with CLI::
27405 * GDB/MI Development and Front Ends::
27406 * GDB/MI Output Records::
27407 * GDB/MI Simple Examples::
27408 * GDB/MI Command Description Format::
27409 * GDB/MI Breakpoint Commands::
27410 * GDB/MI Catchpoint Commands::
27411 * GDB/MI Program Context::
27412 * GDB/MI Thread Commands::
27413 * GDB/MI Ada Tasking Commands::
27414 * GDB/MI Program Execution::
27415 * GDB/MI Stack Manipulation::
27416 * GDB/MI Variable Objects::
27417 * GDB/MI Data Manipulation::
27418 * GDB/MI Tracepoint Commands::
27419 * GDB/MI Symbol Query::
27420 * GDB/MI File Commands::
27422 * GDB/MI Kod Commands::
27423 * GDB/MI Memory Overlay Commands::
27424 * GDB/MI Signal Handling Commands::
27426 * GDB/MI Target Manipulation::
27427 * GDB/MI File Transfer Commands::
27428 * GDB/MI Miscellaneous Commands::
27431 @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
27432 @node GDB/MI General Design
27433 @section @sc{gdb/mi} General Design
27434 @cindex GDB/MI General Design
27436 Interaction of a @sc{GDB/MI} frontend with @value{GDBN} involves three
27437 parts---commands sent to @value{GDBN}, responses to those commands
27438 and notifications. Each command results in exactly one response,
27439 indicating either successful completion of the command, or an error.
27440 For the commands that do not resume the target, the response contains the
27441 requested information. For the commands that resume the target, the
27442 response only indicates whether the target was successfully resumed.
27443 Notifications is the mechanism for reporting changes in the state of the
27444 target, or in @value{GDBN} state, that cannot conveniently be associated with
27445 a command and reported as part of that command response.
27447 The important examples of notifications are:
27451 Exec notifications. These are used to report changes in
27452 target state---when a target is resumed, or stopped. It would not
27453 be feasible to include this information in response of resuming
27454 commands, because one resume commands can result in multiple events in
27455 different threads. Also, quite some time may pass before any event
27456 happens in the target, while a frontend needs to know whether the resuming
27457 command itself was successfully executed.
27460 Console output, and status notifications. Console output
27461 notifications are used to report output of CLI commands, as well as
27462 diagnostics for other commands. Status notifications are used to
27463 report the progress of a long-running operation. Naturally, including
27464 this information in command response would mean no output is produced
27465 until the command is finished, which is undesirable.
27468 General notifications. Commands may have various side effects on
27469 the @value{GDBN} or target state beyond their official purpose. For example,
27470 a command may change the selected thread. Although such changes can
27471 be included in command response, using notification allows for more
27472 orthogonal frontend design.
27476 There's no guarantee that whenever an MI command reports an error,
27477 @value{GDBN} or the target are in any specific state, and especially,
27478 the state is not reverted to the state before the MI command was
27479 processed. Therefore, whenever an MI command results in an error,
27480 we recommend that the frontend refreshes all the information shown in
27481 the user interface.
27485 * Context management::
27486 * Asynchronous and non-stop modes::
27490 @node Context management
27491 @subsection Context management
27493 In most cases when @value{GDBN} accesses the target, this access is
27494 done in context of a specific thread and frame (@pxref{Frames}).
27495 Often, even when accessing global data, the target requires that a thread
27496 be specified. The CLI interface maintains the selected thread and frame,
27497 and supplies them to target on each command. This is convenient,
27498 because a command line user would not want to specify that information
27499 explicitly on each command, and because user interacts with
27500 @value{GDBN} via a single terminal, so no confusion is possible as
27501 to what thread and frame are the current ones.
27503 In the case of MI, the concept of selected thread and frame is less
27504 useful. First, a frontend can easily remember this information
27505 itself. Second, a graphical frontend can have more than one window,
27506 each one used for debugging a different thread, and the frontend might
27507 want to access additional threads for internal purposes. This
27508 increases the risk that by relying on implicitly selected thread, the
27509 frontend may be operating on a wrong one. Therefore, each MI command
27510 should explicitly specify which thread and frame to operate on. To
27511 make it possible, each MI command accepts the @samp{--thread} and
27512 @samp{--frame} options, the value to each is @value{GDBN} identifier
27513 for thread and frame to operate on.
27515 Usually, each top-level window in a frontend allows the user to select
27516 a thread and a frame, and remembers the user selection for further
27517 operations. However, in some cases @value{GDBN} may suggest that the
27518 current thread be changed. For example, when stopping on a breakpoint
27519 it is reasonable to switch to the thread where breakpoint is hit. For
27520 another example, if the user issues the CLI @samp{thread} command via
27521 the frontend, it is desirable to change the frontend's selected thread to the
27522 one specified by user. @value{GDBN} communicates the suggestion to
27523 change current thread using the @samp{=thread-selected} notification.
27524 No such notification is available for the selected frame at the moment.
27526 Note that historically, MI shares the selected thread with CLI, so
27527 frontends used the @code{-thread-select} to execute commands in the
27528 right context. However, getting this to work right is cumbersome. The
27529 simplest way is for frontend to emit @code{-thread-select} command
27530 before every command. This doubles the number of commands that need
27531 to be sent. The alternative approach is to suppress @code{-thread-select}
27532 if the selected thread in @value{GDBN} is supposed to be identical to the
27533 thread the frontend wants to operate on. However, getting this
27534 optimization right can be tricky. In particular, if the frontend
27535 sends several commands to @value{GDBN}, and one of the commands changes the
27536 selected thread, then the behaviour of subsequent commands will
27537 change. So, a frontend should either wait for response from such
27538 problematic commands, or explicitly add @code{-thread-select} for
27539 all subsequent commands. No frontend is known to do this exactly
27540 right, so it is suggested to just always pass the @samp{--thread} and
27541 @samp{--frame} options.
27543 @node Asynchronous and non-stop modes
27544 @subsection Asynchronous command execution and non-stop mode
27546 On some targets, @value{GDBN} is capable of processing MI commands
27547 even while the target is running. This is called @dfn{asynchronous
27548 command execution} (@pxref{Background Execution}). The frontend may
27549 specify a preferrence for asynchronous execution using the
27550 @code{-gdb-set target-async 1} command, which should be emitted before
27551 either running the executable or attaching to the target. After the
27552 frontend has started the executable or attached to the target, it can
27553 find if asynchronous execution is enabled using the
27554 @code{-list-target-features} command.
27556 Even if @value{GDBN} can accept a command while target is running,
27557 many commands that access the target do not work when the target is
27558 running. Therefore, asynchronous command execution is most useful
27559 when combined with non-stop mode (@pxref{Non-Stop Mode}). Then,
27560 it is possible to examine the state of one thread, while other threads
27563 When a given thread is running, MI commands that try to access the
27564 target in the context of that thread may not work, or may work only on
27565 some targets. In particular, commands that try to operate on thread's
27566 stack will not work, on any target. Commands that read memory, or
27567 modify breakpoints, may work or not work, depending on the target. Note
27568 that even commands that operate on global state, such as @code{print},
27569 @code{set}, and breakpoint commands, still access the target in the
27570 context of a specific thread, so frontend should try to find a
27571 stopped thread and perform the operation on that thread (using the
27572 @samp{--thread} option).
27574 Which commands will work in the context of a running thread is
27575 highly target dependent. However, the two commands
27576 @code{-exec-interrupt}, to stop a thread, and @code{-thread-info},
27577 to find the state of a thread, will always work.
27579 @node Thread groups
27580 @subsection Thread groups
27581 @value{GDBN} may be used to debug several processes at the same time.
27582 On some platfroms, @value{GDBN} may support debugging of several
27583 hardware systems, each one having several cores with several different
27584 processes running on each core. This section describes the MI
27585 mechanism to support such debugging scenarios.
27587 The key observation is that regardless of the structure of the
27588 target, MI can have a global list of threads, because most commands that
27589 accept the @samp{--thread} option do not need to know what process that
27590 thread belongs to. Therefore, it is not necessary to introduce
27591 neither additional @samp{--process} option, nor an notion of the
27592 current process in the MI interface. The only strictly new feature
27593 that is required is the ability to find how the threads are grouped
27596 To allow the user to discover such grouping, and to support arbitrary
27597 hierarchy of machines/cores/processes, MI introduces the concept of a
27598 @dfn{thread group}. Thread group is a collection of threads and other
27599 thread groups. A thread group always has a string identifier, a type,
27600 and may have additional attributes specific to the type. A new
27601 command, @code{-list-thread-groups}, returns the list of top-level
27602 thread groups, which correspond to processes that @value{GDBN} is
27603 debugging at the moment. By passing an identifier of a thread group
27604 to the @code{-list-thread-groups} command, it is possible to obtain
27605 the members of specific thread group.
27607 To allow the user to easily discover processes, and other objects, he
27608 wishes to debug, a concept of @dfn{available thread group} is
27609 introduced. Available thread group is an thread group that
27610 @value{GDBN} is not debugging, but that can be attached to, using the
27611 @code{-target-attach} command. The list of available top-level thread
27612 groups can be obtained using @samp{-list-thread-groups --available}.
27613 In general, the content of a thread group may be only retrieved only
27614 after attaching to that thread group.
27616 Thread groups are related to inferiors (@pxref{Inferiors and
27617 Programs}). Each inferior corresponds to a thread group of a special
27618 type @samp{process}, and some additional operations are permitted on
27619 such thread groups.
27621 @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
27622 @node GDB/MI Command Syntax
27623 @section @sc{gdb/mi} Command Syntax
27626 * GDB/MI Input Syntax::
27627 * GDB/MI Output Syntax::
27630 @node GDB/MI Input Syntax
27631 @subsection @sc{gdb/mi} Input Syntax
27633 @cindex input syntax for @sc{gdb/mi}
27634 @cindex @sc{gdb/mi}, input syntax
27636 @item @var{command} @expansion{}
27637 @code{@var{cli-command} | @var{mi-command}}
27639 @item @var{cli-command} @expansion{}
27640 @code{[ @var{token} ] @var{cli-command} @var{nl}}, where
27641 @var{cli-command} is any existing @value{GDBN} CLI command.
27643 @item @var{mi-command} @expansion{}
27644 @code{[ @var{token} ] "-" @var{operation} ( " " @var{option} )*
27645 @code{[} " --" @code{]} ( " " @var{parameter} )* @var{nl}}
27647 @item @var{token} @expansion{}
27648 "any sequence of digits"
27650 @item @var{option} @expansion{}
27651 @code{"-" @var{parameter} [ " " @var{parameter} ]}
27653 @item @var{parameter} @expansion{}
27654 @code{@var{non-blank-sequence} | @var{c-string}}
27656 @item @var{operation} @expansion{}
27657 @emph{any of the operations described in this chapter}
27659 @item @var{non-blank-sequence} @expansion{}
27660 @emph{anything, provided it doesn't contain special characters such as
27661 "-", @var{nl}, """ and of course " "}
27663 @item @var{c-string} @expansion{}
27664 @code{""" @var{seven-bit-iso-c-string-content} """}
27666 @item @var{nl} @expansion{}
27675 The CLI commands are still handled by the @sc{mi} interpreter; their
27676 output is described below.
27679 The @code{@var{token}}, when present, is passed back when the command
27683 Some @sc{mi} commands accept optional arguments as part of the parameter
27684 list. Each option is identified by a leading @samp{-} (dash) and may be
27685 followed by an optional argument parameter. Options occur first in the
27686 parameter list and can be delimited from normal parameters using
27687 @samp{--} (this is useful when some parameters begin with a dash).
27694 We want easy access to the existing CLI syntax (for debugging).
27697 We want it to be easy to spot a @sc{mi} operation.
27700 @node GDB/MI Output Syntax
27701 @subsection @sc{gdb/mi} Output Syntax
27703 @cindex output syntax of @sc{gdb/mi}
27704 @cindex @sc{gdb/mi}, output syntax
27705 The output from @sc{gdb/mi} consists of zero or more out-of-band records
27706 followed, optionally, by a single result record. This result record
27707 is for the most recent command. The sequence of output records is
27708 terminated by @samp{(gdb)}.
27710 If an input command was prefixed with a @code{@var{token}} then the
27711 corresponding output for that command will also be prefixed by that same
27715 @item @var{output} @expansion{}
27716 @code{( @var{out-of-band-record} )* [ @var{result-record} ] "(gdb)" @var{nl}}
27718 @item @var{result-record} @expansion{}
27719 @code{ [ @var{token} ] "^" @var{result-class} ( "," @var{result} )* @var{nl}}
27721 @item @var{out-of-band-record} @expansion{}
27722 @code{@var{async-record} | @var{stream-record}}
27724 @item @var{async-record} @expansion{}
27725 @code{@var{exec-async-output} | @var{status-async-output} | @var{notify-async-output}}
27727 @item @var{exec-async-output} @expansion{}
27728 @code{[ @var{token} ] "*" @var{async-output}}
27730 @item @var{status-async-output} @expansion{}
27731 @code{[ @var{token} ] "+" @var{async-output}}
27733 @item @var{notify-async-output} @expansion{}
27734 @code{[ @var{token} ] "=" @var{async-output}}
27736 @item @var{async-output} @expansion{}
27737 @code{@var{async-class} ( "," @var{result} )* @var{nl}}
27739 @item @var{result-class} @expansion{}
27740 @code{"done" | "running" | "connected" | "error" | "exit"}
27742 @item @var{async-class} @expansion{}
27743 @code{"stopped" | @var{others}} (where @var{others} will be added
27744 depending on the needs---this is still in development).
27746 @item @var{result} @expansion{}
27747 @code{ @var{variable} "=" @var{value}}
27749 @item @var{variable} @expansion{}
27750 @code{ @var{string} }
27752 @item @var{value} @expansion{}
27753 @code{ @var{const} | @var{tuple} | @var{list} }
27755 @item @var{const} @expansion{}
27756 @code{@var{c-string}}
27758 @item @var{tuple} @expansion{}
27759 @code{ "@{@}" | "@{" @var{result} ( "," @var{result} )* "@}" }
27761 @item @var{list} @expansion{}
27762 @code{ "[]" | "[" @var{value} ( "," @var{value} )* "]" | "["
27763 @var{result} ( "," @var{result} )* "]" }
27765 @item @var{stream-record} @expansion{}
27766 @code{@var{console-stream-output} | @var{target-stream-output} | @var{log-stream-output}}
27768 @item @var{console-stream-output} @expansion{}
27769 @code{"~" @var{c-string}}
27771 @item @var{target-stream-output} @expansion{}
27772 @code{"@@" @var{c-string}}
27774 @item @var{log-stream-output} @expansion{}
27775 @code{"&" @var{c-string}}
27777 @item @var{nl} @expansion{}
27780 @item @var{token} @expansion{}
27781 @emph{any sequence of digits}.
27789 All output sequences end in a single line containing a period.
27792 The @code{@var{token}} is from the corresponding request. Note that
27793 for all async output, while the token is allowed by the grammar and
27794 may be output by future versions of @value{GDBN} for select async
27795 output messages, it is generally omitted. Frontends should treat
27796 all async output as reporting general changes in the state of the
27797 target and there should be no need to associate async output to any
27801 @cindex status output in @sc{gdb/mi}
27802 @var{status-async-output} contains on-going status information about the
27803 progress of a slow operation. It can be discarded. All status output is
27804 prefixed by @samp{+}.
27807 @cindex async output in @sc{gdb/mi}
27808 @var{exec-async-output} contains asynchronous state change on the target
27809 (stopped, started, disappeared). All async output is prefixed by
27813 @cindex notify output in @sc{gdb/mi}
27814 @var{notify-async-output} contains supplementary information that the
27815 client should handle (e.g., a new breakpoint information). All notify
27816 output is prefixed by @samp{=}.
27819 @cindex console output in @sc{gdb/mi}
27820 @var{console-stream-output} is output that should be displayed as is in the
27821 console. It is the textual response to a CLI command. All the console
27822 output is prefixed by @samp{~}.
27825 @cindex target output in @sc{gdb/mi}
27826 @var{target-stream-output} is the output produced by the target program.
27827 All the target output is prefixed by @samp{@@}.
27830 @cindex log output in @sc{gdb/mi}
27831 @var{log-stream-output} is output text coming from @value{GDBN}'s internals, for
27832 instance messages that should be displayed as part of an error log. All
27833 the log output is prefixed by @samp{&}.
27836 @cindex list output in @sc{gdb/mi}
27837 New @sc{gdb/mi} commands should only output @var{lists} containing
27843 @xref{GDB/MI Stream Records, , @sc{gdb/mi} Stream Records}, for more
27844 details about the various output records.
27846 @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
27847 @node GDB/MI Compatibility with CLI
27848 @section @sc{gdb/mi} Compatibility with CLI
27850 @cindex compatibility, @sc{gdb/mi} and CLI
27851 @cindex @sc{gdb/mi}, compatibility with CLI
27853 For the developers convenience CLI commands can be entered directly,
27854 but there may be some unexpected behaviour. For example, commands
27855 that query the user will behave as if the user replied yes, breakpoint
27856 command lists are not executed and some CLI commands, such as
27857 @code{if}, @code{when} and @code{define}, prompt for further input with
27858 @samp{>}, which is not valid MI output.
27860 This feature may be removed at some stage in the future and it is
27861 recommended that front ends use the @code{-interpreter-exec} command
27862 (@pxref{-interpreter-exec}).
27864 @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
27865 @node GDB/MI Development and Front Ends
27866 @section @sc{gdb/mi} Development and Front Ends
27867 @cindex @sc{gdb/mi} development
27869 The application which takes the MI output and presents the state of the
27870 program being debugged to the user is called a @dfn{front end}.
27872 Although @sc{gdb/mi} is still incomplete, it is currently being used
27873 by a variety of front ends to @value{GDBN}. This makes it difficult
27874 to introduce new functionality without breaking existing usage. This
27875 section tries to minimize the problems by describing how the protocol
27878 Some changes in MI need not break a carefully designed front end, and
27879 for these the MI version will remain unchanged. The following is a
27880 list of changes that may occur within one level, so front ends should
27881 parse MI output in a way that can handle them:
27885 New MI commands may be added.
27888 New fields may be added to the output of any MI command.
27891 The range of values for fields with specified values, e.g.,
27892 @code{in_scope} (@pxref{-var-update}) may be extended.
27894 @c The format of field's content e.g type prefix, may change so parse it
27895 @c at your own risk. Yes, in general?
27897 @c The order of fields may change? Shouldn't really matter but it might
27898 @c resolve inconsistencies.
27901 If the changes are likely to break front ends, the MI version level
27902 will be increased by one. This will allow the front end to parse the
27903 output according to the MI version. Apart from mi0, new versions of
27904 @value{GDBN} will not support old versions of MI and it will be the
27905 responsibility of the front end to work with the new one.
27907 @c Starting with mi3, add a new command -mi-version that prints the MI
27910 The best way to avoid unexpected changes in MI that might break your front
27911 end is to make your project known to @value{GDBN} developers and
27912 follow development on @email{gdb@@sourceware.org} and
27913 @email{gdb-patches@@sourceware.org}.
27914 @cindex mailing lists
27916 @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
27917 @node GDB/MI Output Records
27918 @section @sc{gdb/mi} Output Records
27921 * GDB/MI Result Records::
27922 * GDB/MI Stream Records::
27923 * GDB/MI Async Records::
27924 * GDB/MI Breakpoint Information::
27925 * GDB/MI Frame Information::
27926 * GDB/MI Thread Information::
27927 * GDB/MI Ada Exception Information::
27930 @node GDB/MI Result Records
27931 @subsection @sc{gdb/mi} Result Records
27933 @cindex result records in @sc{gdb/mi}
27934 @cindex @sc{gdb/mi}, result records
27935 In addition to a number of out-of-band notifications, the response to a
27936 @sc{gdb/mi} command includes one of the following result indications:
27940 @item "^done" [ "," @var{results} ]
27941 The synchronous operation was successful, @code{@var{results}} are the return
27946 This result record is equivalent to @samp{^done}. Historically, it
27947 was output instead of @samp{^done} if the command has resumed the
27948 target. This behaviour is maintained for backward compatibility, but
27949 all frontends should treat @samp{^done} and @samp{^running}
27950 identically and rely on the @samp{*running} output record to determine
27951 which threads are resumed.
27955 @value{GDBN} has connected to a remote target.
27957 @item "^error" "," @var{c-string}
27959 The operation failed. The @code{@var{c-string}} contains the corresponding
27964 @value{GDBN} has terminated.
27968 @node GDB/MI Stream Records
27969 @subsection @sc{gdb/mi} Stream Records
27971 @cindex @sc{gdb/mi}, stream records
27972 @cindex stream records in @sc{gdb/mi}
27973 @value{GDBN} internally maintains a number of output streams: the console, the
27974 target, and the log. The output intended for each of these streams is
27975 funneled through the @sc{gdb/mi} interface using @dfn{stream records}.
27977 Each stream record begins with a unique @dfn{prefix character} which
27978 identifies its stream (@pxref{GDB/MI Output Syntax, , @sc{gdb/mi} Output
27979 Syntax}). In addition to the prefix, each stream record contains a
27980 @code{@var{string-output}}. This is either raw text (with an implicit new
27981 line) or a quoted C string (which does not contain an implicit newline).
27984 @item "~" @var{string-output}
27985 The console output stream contains text that should be displayed in the
27986 CLI console window. It contains the textual responses to CLI commands.
27988 @item "@@" @var{string-output}
27989 The target output stream contains any textual output from the running
27990 target. This is only present when GDB's event loop is truly
27991 asynchronous, which is currently only the case for remote targets.
27993 @item "&" @var{string-output}
27994 The log stream contains debugging messages being produced by @value{GDBN}'s
27998 @node GDB/MI Async Records
27999 @subsection @sc{gdb/mi} Async Records
28001 @cindex async records in @sc{gdb/mi}
28002 @cindex @sc{gdb/mi}, async records
28003 @dfn{Async} records are used to notify the @sc{gdb/mi} client of
28004 additional changes that have occurred. Those changes can either be a
28005 consequence of @sc{gdb/mi} commands (e.g., a breakpoint modified) or a result of
28006 target activity (e.g., target stopped).
28008 The following is the list of possible async records:
28012 @item *running,thread-id="@var{thread}"
28013 The target is now running. The @var{thread} field tells which
28014 specific thread is now running, and can be @samp{all} if all threads
28015 are running. The frontend should assume that no interaction with a
28016 running thread is possible after this notification is produced.
28017 The frontend should not assume that this notification is output
28018 only once for any command. @value{GDBN} may emit this notification
28019 several times, either for different threads, because it cannot resume
28020 all threads together, or even for a single thread, if the thread must
28021 be stepped though some code before letting it run freely.
28023 @item *stopped,reason="@var{reason}",thread-id="@var{id}",stopped-threads="@var{stopped}",core="@var{core}"
28024 The target has stopped. The @var{reason} field can have one of the
28028 @item breakpoint-hit
28029 A breakpoint was reached.
28030 @item watchpoint-trigger
28031 A watchpoint was triggered.
28032 @item read-watchpoint-trigger
28033 A read watchpoint was triggered.
28034 @item access-watchpoint-trigger
28035 An access watchpoint was triggered.
28036 @item function-finished
28037 An -exec-finish or similar CLI command was accomplished.
28038 @item location-reached
28039 An -exec-until or similar CLI command was accomplished.
28040 @item watchpoint-scope
28041 A watchpoint has gone out of scope.
28042 @item end-stepping-range
28043 An -exec-next, -exec-next-instruction, -exec-step, -exec-step-instruction or
28044 similar CLI command was accomplished.
28045 @item exited-signalled
28046 The inferior exited because of a signal.
28048 The inferior exited.
28049 @item exited-normally
28050 The inferior exited normally.
28051 @item signal-received
28052 A signal was received by the inferior.
28054 The inferior has stopped due to a library being loaded or unloaded.
28055 This can happen when @code{stop-on-solib-events} (@pxref{Files}) is
28056 set or when a @code{catch load} or @code{catch unload} catchpoint is
28057 in use (@pxref{Set Catchpoints}).
28059 The inferior has forked. This is reported when @code{catch fork}
28060 (@pxref{Set Catchpoints}) has been used.
28062 The inferior has vforked. This is reported in when @code{catch vfork}
28063 (@pxref{Set Catchpoints}) has been used.
28064 @item syscall-entry
28065 The inferior entered a system call. This is reported when @code{catch
28066 syscall} (@pxref{Set Catchpoints}) has been used.
28067 @item syscall-entry
28068 The inferior returned from a system call. This is reported when
28069 @code{catch syscall} (@pxref{Set Catchpoints}) has been used.
28071 The inferior called @code{exec}. This is reported when @code{catch exec}
28072 (@pxref{Set Catchpoints}) has been used.
28075 The @var{id} field identifies the thread that directly caused the stop
28076 -- for example by hitting a breakpoint. Depending on whether all-stop
28077 mode is in effect (@pxref{All-Stop Mode}), @value{GDBN} may either
28078 stop all threads, or only the thread that directly triggered the stop.
28079 If all threads are stopped, the @var{stopped} field will have the
28080 value of @code{"all"}. Otherwise, the value of the @var{stopped}
28081 field will be a list of thread identifiers. Presently, this list will
28082 always include a single thread, but frontend should be prepared to see
28083 several threads in the list. The @var{core} field reports the
28084 processor core on which the stop event has happened. This field may be absent
28085 if such information is not available.
28087 @item =thread-group-added,id="@var{id}"
28088 @itemx =thread-group-removed,id="@var{id}"
28089 A thread group was either added or removed. The @var{id} field
28090 contains the @value{GDBN} identifier of the thread group. When a thread
28091 group is added, it generally might not be associated with a running
28092 process. When a thread group is removed, its id becomes invalid and
28093 cannot be used in any way.
28095 @item =thread-group-started,id="@var{id}",pid="@var{pid}"
28096 A thread group became associated with a running program,
28097 either because the program was just started or the thread group
28098 was attached to a program. The @var{id} field contains the
28099 @value{GDBN} identifier of the thread group. The @var{pid} field
28100 contains process identifier, specific to the operating system.
28102 @item =thread-group-exited,id="@var{id}"[,exit-code="@var{code}"]
28103 A thread group is no longer associated with a running program,
28104 either because the program has exited, or because it was detached
28105 from. The @var{id} field contains the @value{GDBN} identifier of the
28106 thread group. @var{code} is the exit code of the inferior; it exists
28107 only when the inferior exited with some code.
28109 @item =thread-created,id="@var{id}",group-id="@var{gid}"
28110 @itemx =thread-exited,id="@var{id}",group-id="@var{gid}"
28111 A thread either was created, or has exited. The @var{id} field
28112 contains the @value{GDBN} identifier of the thread. The @var{gid}
28113 field identifies the thread group this thread belongs to.
28115 @item =thread-selected,id="@var{id}"
28116 Informs that the selected thread was changed as result of the last
28117 command. This notification is not emitted as result of @code{-thread-select}
28118 command but is emitted whenever an MI command that is not documented
28119 to change the selected thread actually changes it. In particular,
28120 invoking, directly or indirectly (via user-defined command), the CLI
28121 @code{thread} command, will generate this notification.
28123 We suggest that in response to this notification, front ends
28124 highlight the selected thread and cause subsequent commands to apply to
28127 @item =library-loaded,...
28128 Reports that a new library file was loaded by the program. This
28129 notification has 4 fields---@var{id}, @var{target-name},
28130 @var{host-name}, and @var{symbols-loaded}. The @var{id} field is an
28131 opaque identifier of the library. For remote debugging case,
28132 @var{target-name} and @var{host-name} fields give the name of the
28133 library file on the target, and on the host respectively. For native
28134 debugging, both those fields have the same value. The
28135 @var{symbols-loaded} field is emitted only for backward compatibility
28136 and should not be relied on to convey any useful information. The
28137 @var{thread-group} field, if present, specifies the id of the thread
28138 group in whose context the library was loaded. If the field is
28139 absent, it means the library was loaded in the context of all present
28142 @item =library-unloaded,...
28143 Reports that a library was unloaded by the program. This notification
28144 has 3 fields---@var{id}, @var{target-name} and @var{host-name} with
28145 the same meaning as for the @code{=library-loaded} notification.
28146 The @var{thread-group} field, if present, specifies the id of the
28147 thread group in whose context the library was unloaded. If the field is
28148 absent, it means the library was unloaded in the context of all present
28151 @item =traceframe-changed,num=@var{tfnum},tracepoint=@var{tpnum}
28152 @itemx =traceframe-changed,end
28153 Reports that the trace frame was changed and its new number is
28154 @var{tfnum}. The number of the tracepoint associated with this trace
28155 frame is @var{tpnum}.
28157 @item =tsv-created,name=@var{name},initial=@var{initial}
28158 Reports that the new trace state variable @var{name} is created with
28159 initial value @var{initial}.
28161 @item =tsv-deleted,name=@var{name}
28162 @itemx =tsv-deleted
28163 Reports that the trace state variable @var{name} is deleted or all
28164 trace state variables are deleted.
28166 @item =tsv-modified,name=@var{name},initial=@var{initial}[,current=@var{current}]
28167 Reports that the trace state variable @var{name} is modified with
28168 the initial value @var{initial}. The current value @var{current} of
28169 trace state variable is optional and is reported if the current
28170 value of trace state variable is known.
28172 @item =breakpoint-created,bkpt=@{...@}
28173 @itemx =breakpoint-modified,bkpt=@{...@}
28174 @itemx =breakpoint-deleted,id=@var{number}
28175 Reports that a breakpoint was created, modified, or deleted,
28176 respectively. Only user-visible breakpoints are reported to the MI
28179 The @var{bkpt} argument is of the same form as returned by the various
28180 breakpoint commands; @xref{GDB/MI Breakpoint Commands}. The
28181 @var{number} is the ordinal number of the breakpoint.
28183 Note that if a breakpoint is emitted in the result record of a
28184 command, then it will not also be emitted in an async record.
28186 @item =record-started,thread-group="@var{id}"
28187 @itemx =record-stopped,thread-group="@var{id}"
28188 Execution log recording was either started or stopped on an
28189 inferior. The @var{id} is the @value{GDBN} identifier of the thread
28190 group corresponding to the affected inferior.
28192 @item =cmd-param-changed,param=@var{param},value=@var{value}
28193 Reports that a parameter of the command @code{set @var{param}} is
28194 changed to @var{value}. In the multi-word @code{set} command,
28195 the @var{param} is the whole parameter list to @code{set} command.
28196 For example, In command @code{set check type on}, @var{param}
28197 is @code{check type} and @var{value} is @code{on}.
28199 @item =memory-changed,thread-group=@var{id},addr=@var{addr},len=@var{len}[,type="code"]
28200 Reports that bytes from @var{addr} to @var{data} + @var{len} were
28201 written in an inferior. The @var{id} is the identifier of the
28202 thread group corresponding to the affected inferior. The optional
28203 @code{type="code"} part is reported if the memory written to holds
28207 @node GDB/MI Breakpoint Information
28208 @subsection @sc{gdb/mi} Breakpoint Information
28210 When @value{GDBN} reports information about a breakpoint, a
28211 tracepoint, a watchpoint, or a catchpoint, it uses a tuple with the
28216 The breakpoint number. For a breakpoint that represents one location
28217 of a multi-location breakpoint, this will be a dotted pair, like
28221 The type of the breakpoint. For ordinary breakpoints this will be
28222 @samp{breakpoint}, but many values are possible.
28225 If the type of the breakpoint is @samp{catchpoint}, then this
28226 indicates the exact type of catchpoint.
28229 This is the breakpoint disposition---either @samp{del}, meaning that
28230 the breakpoint will be deleted at the next stop, or @samp{keep},
28231 meaning that the breakpoint will not be deleted.
28234 This indicates whether the breakpoint is enabled, in which case the
28235 value is @samp{y}, or disabled, in which case the value is @samp{n}.
28236 Note that this is not the same as the field @code{enable}.
28239 The address of the breakpoint. This may be a hexidecimal number,
28240 giving the address; or the string @samp{<PENDING>}, for a pending
28241 breakpoint; or the string @samp{<MULTIPLE>}, for a breakpoint with
28242 multiple locations. This field will not be present if no address can
28243 be determined. For example, a watchpoint does not have an address.
28246 If known, the function in which the breakpoint appears.
28247 If not known, this field is not present.
28250 The name of the source file which contains this function, if known.
28251 If not known, this field is not present.
28254 The full file name of the source file which contains this function, if
28255 known. If not known, this field is not present.
28258 The line number at which this breakpoint appears, if known.
28259 If not known, this field is not present.
28262 If the source file is not known, this field may be provided. If
28263 provided, this holds the address of the breakpoint, possibly followed
28267 If this breakpoint is pending, this field is present and holds the
28268 text used to set the breakpoint, as entered by the user.
28271 Where this breakpoint's condition is evaluated, either @samp{host} or
28275 If this is a thread-specific breakpoint, then this identifies the
28276 thread in which the breakpoint can trigger.
28279 If this breakpoint is restricted to a particular Ada task, then this
28280 field will hold the task identifier.
28283 If the breakpoint is conditional, this is the condition expression.
28286 The ignore count of the breakpoint.
28289 The enable count of the breakpoint.
28291 @item traceframe-usage
28294 @item static-tracepoint-marker-string-id
28295 For a static tracepoint, the name of the static tracepoint marker.
28298 For a masked watchpoint, this is the mask.
28301 A tracepoint's pass count.
28303 @item original-location
28304 The location of the breakpoint as originally specified by the user.
28305 This field is optional.
28308 The number of times the breakpoint has been hit.
28311 This field is only given for tracepoints. This is either @samp{y},
28312 meaning that the tracepoint is installed, or @samp{n}, meaning that it
28316 Some extra data, the exact contents of which are type-dependent.
28320 For example, here is what the output of @code{-break-insert}
28321 (@pxref{GDB/MI Breakpoint Commands}) might be:
28324 -> -break-insert main
28325 <- ^done,bkpt=@{number="1",type="breakpoint",disp="keep",
28326 enabled="y",addr="0x08048564",func="main",file="myprog.c",
28327 fullname="/home/nickrob/myprog.c",line="68",thread-groups=["i1"],
28332 @node GDB/MI Frame Information
28333 @subsection @sc{gdb/mi} Frame Information
28335 Response from many MI commands includes an information about stack
28336 frame. This information is a tuple that may have the following
28341 The level of the stack frame. The innermost frame has the level of
28342 zero. This field is always present.
28345 The name of the function corresponding to the frame. This field may
28346 be absent if @value{GDBN} is unable to determine the function name.
28349 The code address for the frame. This field is always present.
28352 The name of the source files that correspond to the frame's code
28353 address. This field may be absent.
28356 The source line corresponding to the frames' code address. This field
28360 The name of the binary file (either executable or shared library) the
28361 corresponds to the frame's code address. This field may be absent.
28365 @node GDB/MI Thread Information
28366 @subsection @sc{gdb/mi} Thread Information
28368 Whenever @value{GDBN} has to report an information about a thread, it
28369 uses a tuple with the following fields:
28373 The numeric id assigned to the thread by @value{GDBN}. This field is
28377 Target-specific string identifying the thread. This field is always present.
28380 Additional information about the thread provided by the target.
28381 It is supposed to be human-readable and not interpreted by the
28382 frontend. This field is optional.
28385 Either @samp{stopped} or @samp{running}, depending on whether the
28386 thread is presently running. This field is always present.
28389 The value of this field is an integer number of the processor core the
28390 thread was last seen on. This field is optional.
28393 @node GDB/MI Ada Exception Information
28394 @subsection @sc{gdb/mi} Ada Exception Information
28396 Whenever a @code{*stopped} record is emitted because the program
28397 stopped after hitting an exception catchpoint (@pxref{Set Catchpoints}),
28398 @value{GDBN} provides the name of the exception that was raised via
28399 the @code{exception-name} field.
28401 @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
28402 @node GDB/MI Simple Examples
28403 @section Simple Examples of @sc{gdb/mi} Interaction
28404 @cindex @sc{gdb/mi}, simple examples
28406 This subsection presents several simple examples of interaction using
28407 the @sc{gdb/mi} interface. In these examples, @samp{->} means that the
28408 following line is passed to @sc{gdb/mi} as input, while @samp{<-} means
28409 the output received from @sc{gdb/mi}.
28411 Note the line breaks shown in the examples are here only for
28412 readability, they don't appear in the real output.
28414 @subheading Setting a Breakpoint
28416 Setting a breakpoint generates synchronous output which contains detailed
28417 information of the breakpoint.
28420 -> -break-insert main
28421 <- ^done,bkpt=@{number="1",type="breakpoint",disp="keep",
28422 enabled="y",addr="0x08048564",func="main",file="myprog.c",
28423 fullname="/home/nickrob/myprog.c",line="68",thread-groups=["i1"],
28428 @subheading Program Execution
28430 Program execution generates asynchronous records and MI gives the
28431 reason that execution stopped.
28437 <- *stopped,reason="breakpoint-hit",disp="keep",bkptno="1",thread-id="0",
28438 frame=@{addr="0x08048564",func="main",
28439 args=[@{name="argc",value="1"@},@{name="argv",value="0xbfc4d4d4"@}],
28440 file="myprog.c",fullname="/home/nickrob/myprog.c",line="68"@}
28445 <- *stopped,reason="exited-normally"
28449 @subheading Quitting @value{GDBN}
28451 Quitting @value{GDBN} just prints the result class @samp{^exit}.
28459 Please note that @samp{^exit} is printed immediately, but it might
28460 take some time for @value{GDBN} to actually exit. During that time, @value{GDBN}
28461 performs necessary cleanups, including killing programs being debugged
28462 or disconnecting from debug hardware, so the frontend should wait till
28463 @value{GDBN} exits and should only forcibly kill @value{GDBN} if it
28464 fails to exit in reasonable time.
28466 @subheading A Bad Command
28468 Here's what happens if you pass a non-existent command:
28472 <- ^error,msg="Undefined MI command: rubbish"
28477 @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
28478 @node GDB/MI Command Description Format
28479 @section @sc{gdb/mi} Command Description Format
28481 The remaining sections describe blocks of commands. Each block of
28482 commands is laid out in a fashion similar to this section.
28484 @subheading Motivation
28486 The motivation for this collection of commands.
28488 @subheading Introduction
28490 A brief introduction to this collection of commands as a whole.
28492 @subheading Commands
28494 For each command in the block, the following is described:
28496 @subsubheading Synopsis
28499 -command @var{args}@dots{}
28502 @subsubheading Result
28504 @subsubheading @value{GDBN} Command
28506 The corresponding @value{GDBN} CLI command(s), if any.
28508 @subsubheading Example
28510 Example(s) formatted for readability. Some of the described commands have
28511 not been implemented yet and these are labeled N.A.@: (not available).
28514 @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
28515 @node GDB/MI Breakpoint Commands
28516 @section @sc{gdb/mi} Breakpoint Commands
28518 @cindex breakpoint commands for @sc{gdb/mi}
28519 @cindex @sc{gdb/mi}, breakpoint commands
28520 This section documents @sc{gdb/mi} commands for manipulating
28523 @subheading The @code{-break-after} Command
28524 @findex -break-after
28526 @subsubheading Synopsis
28529 -break-after @var{number} @var{count}
28532 The breakpoint number @var{number} is not in effect until it has been
28533 hit @var{count} times. To see how this is reflected in the output of
28534 the @samp{-break-list} command, see the description of the
28535 @samp{-break-list} command below.
28537 @subsubheading @value{GDBN} Command
28539 The corresponding @value{GDBN} command is @samp{ignore}.
28541 @subsubheading Example
28546 ^done,bkpt=@{number="1",type="breakpoint",disp="keep",
28547 enabled="y",addr="0x000100d0",func="main",file="hello.c",
28548 fullname="/home/foo/hello.c",line="5",thread-groups=["i1"],
28556 ^done,BreakpointTable=@{nr_rows="1",nr_cols="6",
28557 hdr=[@{width="3",alignment="-1",col_name="number",colhdr="Num"@},
28558 @{width="14",alignment="-1",col_name="type",colhdr="Type"@},
28559 @{width="4",alignment="-1",col_name="disp",colhdr="Disp"@},
28560 @{width="3",alignment="-1",col_name="enabled",colhdr="Enb"@},
28561 @{width="10",alignment="-1",col_name="addr",colhdr="Address"@},
28562 @{width="40",alignment="2",col_name="what",colhdr="What"@}],
28563 body=[bkpt=@{number="1",type="breakpoint",disp="keep",enabled="y",
28564 addr="0x000100d0",func="main",file="hello.c",fullname="/home/foo/hello.c",
28565 line="5",thread-groups=["i1"],times="0",ignore="3"@}]@}
28570 @subheading The @code{-break-catch} Command
28571 @findex -break-catch
28574 @subheading The @code{-break-commands} Command
28575 @findex -break-commands
28577 @subsubheading Synopsis
28580 -break-commands @var{number} [ @var{command1} ... @var{commandN} ]
28583 Specifies the CLI commands that should be executed when breakpoint
28584 @var{number} is hit. The parameters @var{command1} to @var{commandN}
28585 are the commands. If no command is specified, any previously-set
28586 commands are cleared. @xref{Break Commands}. Typical use of this
28587 functionality is tracing a program, that is, printing of values of
28588 some variables whenever breakpoint is hit and then continuing.
28590 @subsubheading @value{GDBN} Command
28592 The corresponding @value{GDBN} command is @samp{commands}.
28594 @subsubheading Example
28599 ^done,bkpt=@{number="1",type="breakpoint",disp="keep",
28600 enabled="y",addr="0x000100d0",func="main",file="hello.c",
28601 fullname="/home/foo/hello.c",line="5",thread-groups=["i1"],
28604 -break-commands 1 "print v" "continue"
28609 @subheading The @code{-break-condition} Command
28610 @findex -break-condition
28612 @subsubheading Synopsis
28615 -break-condition @var{number} @var{expr}
28618 Breakpoint @var{number} will stop the program only if the condition in
28619 @var{expr} is true. The condition becomes part of the
28620 @samp{-break-list} output (see the description of the @samp{-break-list}
28623 @subsubheading @value{GDBN} Command
28625 The corresponding @value{GDBN} command is @samp{condition}.
28627 @subsubheading Example
28631 -break-condition 1 1
28635 ^done,BreakpointTable=@{nr_rows="1",nr_cols="6",
28636 hdr=[@{width="3",alignment="-1",col_name="number",colhdr="Num"@},
28637 @{width="14",alignment="-1",col_name="type",colhdr="Type"@},
28638 @{width="4",alignment="-1",col_name="disp",colhdr="Disp"@},
28639 @{width="3",alignment="-1",col_name="enabled",colhdr="Enb"@},
28640 @{width="10",alignment="-1",col_name="addr",colhdr="Address"@},
28641 @{width="40",alignment="2",col_name="what",colhdr="What"@}],
28642 body=[bkpt=@{number="1",type="breakpoint",disp="keep",enabled="y",
28643 addr="0x000100d0",func="main",file="hello.c",fullname="/home/foo/hello.c",
28644 line="5",cond="1",thread-groups=["i1"],times="0",ignore="3"@}]@}
28648 @subheading The @code{-break-delete} Command
28649 @findex -break-delete
28651 @subsubheading Synopsis
28654 -break-delete ( @var{breakpoint} )+
28657 Delete the breakpoint(s) whose number(s) are specified in the argument
28658 list. This is obviously reflected in the breakpoint list.
28660 @subsubheading @value{GDBN} Command
28662 The corresponding @value{GDBN} command is @samp{delete}.
28664 @subsubheading Example
28672 ^done,BreakpointTable=@{nr_rows="0",nr_cols="6",
28673 hdr=[@{width="3",alignment="-1",col_name="number",colhdr="Num"@},
28674 @{width="14",alignment="-1",col_name="type",colhdr="Type"@},
28675 @{width="4",alignment="-1",col_name="disp",colhdr="Disp"@},
28676 @{width="3",alignment="-1",col_name="enabled",colhdr="Enb"@},
28677 @{width="10",alignment="-1",col_name="addr",colhdr="Address"@},
28678 @{width="40",alignment="2",col_name="what",colhdr="What"@}],
28683 @subheading The @code{-break-disable} Command
28684 @findex -break-disable
28686 @subsubheading Synopsis
28689 -break-disable ( @var{breakpoint} )+
28692 Disable the named @var{breakpoint}(s). The field @samp{enabled} in the
28693 break list is now set to @samp{n} for the named @var{breakpoint}(s).
28695 @subsubheading @value{GDBN} Command
28697 The corresponding @value{GDBN} command is @samp{disable}.
28699 @subsubheading Example
28707 ^done,BreakpointTable=@{nr_rows="1",nr_cols="6",
28708 hdr=[@{width="3",alignment="-1",col_name="number",colhdr="Num"@},
28709 @{width="14",alignment="-1",col_name="type",colhdr="Type"@},
28710 @{width="4",alignment="-1",col_name="disp",colhdr="Disp"@},
28711 @{width="3",alignment="-1",col_name="enabled",colhdr="Enb"@},
28712 @{width="10",alignment="-1",col_name="addr",colhdr="Address"@},
28713 @{width="40",alignment="2",col_name="what",colhdr="What"@}],
28714 body=[bkpt=@{number="2",type="breakpoint",disp="keep",enabled="n",
28715 addr="0x000100d0",func="main",file="hello.c",fullname="/home/foo/hello.c",
28716 line="5",thread-groups=["i1"],times="0"@}]@}
28720 @subheading The @code{-break-enable} Command
28721 @findex -break-enable
28723 @subsubheading Synopsis
28726 -break-enable ( @var{breakpoint} )+
28729 Enable (previously disabled) @var{breakpoint}(s).
28731 @subsubheading @value{GDBN} Command
28733 The corresponding @value{GDBN} command is @samp{enable}.
28735 @subsubheading Example
28743 ^done,BreakpointTable=@{nr_rows="1",nr_cols="6",
28744 hdr=[@{width="3",alignment="-1",col_name="number",colhdr="Num"@},
28745 @{width="14",alignment="-1",col_name="type",colhdr="Type"@},
28746 @{width="4",alignment="-1",col_name="disp",colhdr="Disp"@},
28747 @{width="3",alignment="-1",col_name="enabled",colhdr="Enb"@},
28748 @{width="10",alignment="-1",col_name="addr",colhdr="Address"@},
28749 @{width="40",alignment="2",col_name="what",colhdr="What"@}],
28750 body=[bkpt=@{number="2",type="breakpoint",disp="keep",enabled="y",
28751 addr="0x000100d0",func="main",file="hello.c",fullname="/home/foo/hello.c",
28752 line="5",thread-groups=["i1"],times="0"@}]@}
28756 @subheading The @code{-break-info} Command
28757 @findex -break-info
28759 @subsubheading Synopsis
28762 -break-info @var{breakpoint}
28766 Get information about a single breakpoint.
28768 The result is a table of breakpoints. @xref{GDB/MI Breakpoint
28769 Information}, for details on the format of each breakpoint in the
28772 @subsubheading @value{GDBN} Command
28774 The corresponding @value{GDBN} command is @samp{info break @var{breakpoint}}.
28776 @subsubheading Example
28779 @subheading The @code{-break-insert} Command
28780 @findex -break-insert
28782 @subsubheading Synopsis
28785 -break-insert [ -t ] [ -h ] [ -f ] [ -d ] [ -a ]
28786 [ -c @var{condition} ] [ -i @var{ignore-count} ]
28787 [ -p @var{thread-id} ] [ @var{location} ]
28791 If specified, @var{location}, can be one of:
28798 @item filename:linenum
28799 @item filename:function
28803 The possible optional parameters of this command are:
28807 Insert a temporary breakpoint.
28809 Insert a hardware breakpoint.
28811 If @var{location} cannot be parsed (for example if it
28812 refers to unknown files or functions), create a pending
28813 breakpoint. Without this flag, @value{GDBN} will report
28814 an error, and won't create a breakpoint, if @var{location}
28817 Create a disabled breakpoint.
28819 Create a tracepoint. @xref{Tracepoints}. When this parameter
28820 is used together with @samp{-h}, a fast tracepoint is created.
28821 @item -c @var{condition}
28822 Make the breakpoint conditional on @var{condition}.
28823 @item -i @var{ignore-count}
28824 Initialize the @var{ignore-count}.
28825 @item -p @var{thread-id}
28826 Restrict the breakpoint to the specified @var{thread-id}.
28829 @subsubheading Result
28831 @xref{GDB/MI Breakpoint Information}, for details on the format of the
28832 resulting breakpoint.
28834 Note: this format is open to change.
28835 @c An out-of-band breakpoint instead of part of the result?
28837 @subsubheading @value{GDBN} Command
28839 The corresponding @value{GDBN} commands are @samp{break}, @samp{tbreak},
28840 @samp{hbreak}, and @samp{thbreak}. @c and @samp{rbreak}.
28842 @subsubheading Example
28847 ^done,bkpt=@{number="1",addr="0x0001072c",file="recursive2.c",
28848 fullname="/home/foo/recursive2.c,line="4",thread-groups=["i1"],
28851 -break-insert -t foo
28852 ^done,bkpt=@{number="2",addr="0x00010774",file="recursive2.c",
28853 fullname="/home/foo/recursive2.c,line="11",thread-groups=["i1"],
28857 ^done,BreakpointTable=@{nr_rows="2",nr_cols="6",
28858 hdr=[@{width="3",alignment="-1",col_name="number",colhdr="Num"@},
28859 @{width="14",alignment="-1",col_name="type",colhdr="Type"@},
28860 @{width="4",alignment="-1",col_name="disp",colhdr="Disp"@},
28861 @{width="3",alignment="-1",col_name="enabled",colhdr="Enb"@},
28862 @{width="10",alignment="-1",col_name="addr",colhdr="Address"@},
28863 @{width="40",alignment="2",col_name="what",colhdr="What"@}],
28864 body=[bkpt=@{number="1",type="breakpoint",disp="keep",enabled="y",
28865 addr="0x0001072c", func="main",file="recursive2.c",
28866 fullname="/home/foo/recursive2.c,"line="4",thread-groups=["i1"],
28868 bkpt=@{number="2",type="breakpoint",disp="del",enabled="y",
28869 addr="0x00010774",func="foo",file="recursive2.c",
28870 fullname="/home/foo/recursive2.c",line="11",thread-groups=["i1"],
28873 @c -break-insert -r foo.*
28874 @c ~int foo(int, int);
28875 @c ^done,bkpt=@{number="3",addr="0x00010774",file="recursive2.c,
28876 @c "fullname="/home/foo/recursive2.c",line="11",thread-groups=["i1"],
28881 @subheading The @code{-break-list} Command
28882 @findex -break-list
28884 @subsubheading Synopsis
28890 Displays the list of inserted breakpoints, showing the following fields:
28894 number of the breakpoint
28896 type of the breakpoint: @samp{breakpoint} or @samp{watchpoint}
28898 should the breakpoint be deleted or disabled when it is hit: @samp{keep}
28901 is the breakpoint enabled or no: @samp{y} or @samp{n}
28903 memory location at which the breakpoint is set
28905 logical location of the breakpoint, expressed by function name, file
28907 @item Thread-groups
28908 list of thread groups to which this breakpoint applies
28910 number of times the breakpoint has been hit
28913 If there are no breakpoints or watchpoints, the @code{BreakpointTable}
28914 @code{body} field is an empty list.
28916 @subsubheading @value{GDBN} Command
28918 The corresponding @value{GDBN} command is @samp{info break}.
28920 @subsubheading Example
28925 ^done,BreakpointTable=@{nr_rows="2",nr_cols="6",
28926 hdr=[@{width="3",alignment="-1",col_name="number",colhdr="Num"@},
28927 @{width="14",alignment="-1",col_name="type",colhdr="Type"@},
28928 @{width="4",alignment="-1",col_name="disp",colhdr="Disp"@},
28929 @{width="3",alignment="-1",col_name="enabled",colhdr="Enb"@},
28930 @{width="10",alignment="-1",col_name="addr",colhdr="Address"@},
28931 @{width="40",alignment="2",col_name="what",colhdr="What"@}],
28932 body=[bkpt=@{number="1",type="breakpoint",disp="keep",enabled="y",
28933 addr="0x000100d0",func="main",file="hello.c",line="5",thread-groups=["i1"],
28935 bkpt=@{number="2",type="breakpoint",disp="keep",enabled="y",
28936 addr="0x00010114",func="foo",file="hello.c",fullname="/home/foo/hello.c",
28937 line="13",thread-groups=["i1"],times="0"@}]@}
28941 Here's an example of the result when there are no breakpoints:
28946 ^done,BreakpointTable=@{nr_rows="0",nr_cols="6",
28947 hdr=[@{width="3",alignment="-1",col_name="number",colhdr="Num"@},
28948 @{width="14",alignment="-1",col_name="type",colhdr="Type"@},
28949 @{width="4",alignment="-1",col_name="disp",colhdr="Disp"@},
28950 @{width="3",alignment="-1",col_name="enabled",colhdr="Enb"@},
28951 @{width="10",alignment="-1",col_name="addr",colhdr="Address"@},
28952 @{width="40",alignment="2",col_name="what",colhdr="What"@}],
28957 @subheading The @code{-break-passcount} Command
28958 @findex -break-passcount
28960 @subsubheading Synopsis
28963 -break-passcount @var{tracepoint-number} @var{passcount}
28966 Set the passcount for tracepoint @var{tracepoint-number} to
28967 @var{passcount}. If the breakpoint referred to by @var{tracepoint-number}
28968 is not a tracepoint, error is emitted. This corresponds to CLI
28969 command @samp{passcount}.
28971 @subheading The @code{-break-watch} Command
28972 @findex -break-watch
28974 @subsubheading Synopsis
28977 -break-watch [ -a | -r ]
28980 Create a watchpoint. With the @samp{-a} option it will create an
28981 @dfn{access} watchpoint, i.e., a watchpoint that triggers either on a
28982 read from or on a write to the memory location. With the @samp{-r}
28983 option, the watchpoint created is a @dfn{read} watchpoint, i.e., it will
28984 trigger only when the memory location is accessed for reading. Without
28985 either of the options, the watchpoint created is a regular watchpoint,
28986 i.e., it will trigger when the memory location is accessed for writing.
28987 @xref{Set Watchpoints, , Setting Watchpoints}.
28989 Note that @samp{-break-list} will report a single list of watchpoints and
28990 breakpoints inserted.
28992 @subsubheading @value{GDBN} Command
28994 The corresponding @value{GDBN} commands are @samp{watch}, @samp{awatch}, and
28997 @subsubheading Example
28999 Setting a watchpoint on a variable in the @code{main} function:
29004 ^done,wpt=@{number="2",exp="x"@}
29009 *stopped,reason="watchpoint-trigger",wpt=@{number="2",exp="x"@},
29010 value=@{old="-268439212",new="55"@},
29011 frame=@{func="main",args=[],file="recursive2.c",
29012 fullname="/home/foo/bar/recursive2.c",line="5"@}
29016 Setting a watchpoint on a variable local to a function. @value{GDBN} will stop
29017 the program execution twice: first for the variable changing value, then
29018 for the watchpoint going out of scope.
29023 ^done,wpt=@{number="5",exp="C"@}
29028 *stopped,reason="watchpoint-trigger",
29029 wpt=@{number="5",exp="C"@},value=@{old="-276895068",new="3"@},
29030 frame=@{func="callee4",args=[],
29031 file="../../../devo/gdb/testsuite/gdb.mi/basics.c",
29032 fullname="/home/foo/bar/devo/gdb/testsuite/gdb.mi/basics.c",line="13"@}
29037 *stopped,reason="watchpoint-scope",wpnum="5",
29038 frame=@{func="callee3",args=[@{name="strarg",
29039 value="0x11940 \"A string argument.\""@}],
29040 file="../../../devo/gdb/testsuite/gdb.mi/basics.c",
29041 fullname="/home/foo/bar/devo/gdb/testsuite/gdb.mi/basics.c",line="18"@}
29045 Listing breakpoints and watchpoints, at different points in the program
29046 execution. Note that once the watchpoint goes out of scope, it is
29052 ^done,wpt=@{number="2",exp="C"@}
29055 ^done,BreakpointTable=@{nr_rows="2",nr_cols="6",
29056 hdr=[@{width="3",alignment="-1",col_name="number",colhdr="Num"@},
29057 @{width="14",alignment="-1",col_name="type",colhdr="Type"@},
29058 @{width="4",alignment="-1",col_name="disp",colhdr="Disp"@},
29059 @{width="3",alignment="-1",col_name="enabled",colhdr="Enb"@},
29060 @{width="10",alignment="-1",col_name="addr",colhdr="Address"@},
29061 @{width="40",alignment="2",col_name="what",colhdr="What"@}],
29062 body=[bkpt=@{number="1",type="breakpoint",disp="keep",enabled="y",
29063 addr="0x00010734",func="callee4",
29064 file="../../../devo/gdb/testsuite/gdb.mi/basics.c",
29065 fullname="/home/foo/devo/gdb/testsuite/gdb.mi/basics.c"line="8",thread-groups=["i1"],
29067 bkpt=@{number="2",type="watchpoint",disp="keep",
29068 enabled="y",addr="",what="C",thread-groups=["i1"],times="0"@}]@}
29073 *stopped,reason="watchpoint-trigger",wpt=@{number="2",exp="C"@},
29074 value=@{old="-276895068",new="3"@},
29075 frame=@{func="callee4",args=[],
29076 file="../../../devo/gdb/testsuite/gdb.mi/basics.c",
29077 fullname="/home/foo/bar/devo/gdb/testsuite/gdb.mi/basics.c",line="13"@}
29080 ^done,BreakpointTable=@{nr_rows="2",nr_cols="6",
29081 hdr=[@{width="3",alignment="-1",col_name="number",colhdr="Num"@},
29082 @{width="14",alignment="-1",col_name="type",colhdr="Type"@},
29083 @{width="4",alignment="-1",col_name="disp",colhdr="Disp"@},
29084 @{width="3",alignment="-1",col_name="enabled",colhdr="Enb"@},
29085 @{width="10",alignment="-1",col_name="addr",colhdr="Address"@},
29086 @{width="40",alignment="2",col_name="what",colhdr="What"@}],
29087 body=[bkpt=@{number="1",type="breakpoint",disp="keep",enabled="y",
29088 addr="0x00010734",func="callee4",
29089 file="../../../devo/gdb/testsuite/gdb.mi/basics.c",
29090 fullname="/home/foo/devo/gdb/testsuite/gdb.mi/basics.c",line="8",thread-groups=["i1"],
29092 bkpt=@{number="2",type="watchpoint",disp="keep",
29093 enabled="y",addr="",what="C",thread-groups=["i1"],times="-5"@}]@}
29097 ^done,reason="watchpoint-scope",wpnum="2",
29098 frame=@{func="callee3",args=[@{name="strarg",
29099 value="0x11940 \"A string argument.\""@}],
29100 file="../../../devo/gdb/testsuite/gdb.mi/basics.c",
29101 fullname="/home/foo/bar/devo/gdb/testsuite/gdb.mi/basics.c",line="18"@}
29104 ^done,BreakpointTable=@{nr_rows="1",nr_cols="6",
29105 hdr=[@{width="3",alignment="-1",col_name="number",colhdr="Num"@},
29106 @{width="14",alignment="-1",col_name="type",colhdr="Type"@},
29107 @{width="4",alignment="-1",col_name="disp",colhdr="Disp"@},
29108 @{width="3",alignment="-1",col_name="enabled",colhdr="Enb"@},
29109 @{width="10",alignment="-1",col_name="addr",colhdr="Address"@},
29110 @{width="40",alignment="2",col_name="what",colhdr="What"@}],
29111 body=[bkpt=@{number="1",type="breakpoint",disp="keep",enabled="y",
29112 addr="0x00010734",func="callee4",
29113 file="../../../devo/gdb/testsuite/gdb.mi/basics.c",
29114 fullname="/home/foo/devo/gdb/testsuite/gdb.mi/basics.c",line="8",
29115 thread-groups=["i1"],times="1"@}]@}
29120 @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
29121 @node GDB/MI Catchpoint Commands
29122 @section @sc{gdb/mi} Catchpoint Commands
29124 This section documents @sc{gdb/mi} commands for manipulating
29127 @subheading The @code{-catch-load} Command
29128 @findex -catch-load
29130 @subsubheading Synopsis
29133 -catch-load [ -t ] [ -d ] @var{regexp}
29136 Add a catchpoint for library load events. If the @samp{-t} option is used,
29137 the catchpoint is a temporary one (@pxref{Set Breaks, ,Setting
29138 Breakpoints}). If the @samp{-d} option is used, the catchpoint is created
29139 in a disabled state. The @samp{regexp} argument is a regular
29140 expression used to match the name of the loaded library.
29143 @subsubheading @value{GDBN} Command
29145 The corresponding @value{GDBN} command is @samp{catch load}.
29147 @subsubheading Example
29150 -catch-load -t foo.so
29151 ^done,bkpt=@{number="1",type="catchpoint",disp="del",enabled="y",
29152 what="load of library matching foo.so",catch-type="load",times="0"@}
29157 @subheading The @code{-catch-unload} Command
29158 @findex -catch-unload
29160 @subsubheading Synopsis
29163 -catch-unload [ -t ] [ -d ] @var{regexp}
29166 Add a catchpoint for library unload events. If the @samp{-t} option is
29167 used, the catchpoint is a temporary one (@pxref{Set Breaks, ,Setting
29168 Breakpoints}). If the @samp{-d} option is used, the catchpoint is
29169 created in a disabled state. The @samp{regexp} argument is a regular
29170 expression used to match the name of the unloaded library.
29172 @subsubheading @value{GDBN} Command
29174 The corresponding @value{GDBN} command is @samp{catch unload}.
29176 @subsubheading Example
29179 -catch-unload -d bar.so
29180 ^done,bkpt=@{number="2",type="catchpoint",disp="keep",enabled="n",
29181 what="load of library matching bar.so",catch-type="unload",times="0"@}
29186 @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
29187 @node GDB/MI Program Context
29188 @section @sc{gdb/mi} Program Context
29190 @subheading The @code{-exec-arguments} Command
29191 @findex -exec-arguments
29194 @subsubheading Synopsis
29197 -exec-arguments @var{args}
29200 Set the inferior program arguments, to be used in the next
29203 @subsubheading @value{GDBN} Command
29205 The corresponding @value{GDBN} command is @samp{set args}.
29207 @subsubheading Example
29211 -exec-arguments -v word
29218 @subheading The @code{-exec-show-arguments} Command
29219 @findex -exec-show-arguments
29221 @subsubheading Synopsis
29224 -exec-show-arguments
29227 Print the arguments of the program.
29229 @subsubheading @value{GDBN} Command
29231 The corresponding @value{GDBN} command is @samp{show args}.
29233 @subsubheading Example
29238 @subheading The @code{-environment-cd} Command
29239 @findex -environment-cd
29241 @subsubheading Synopsis
29244 -environment-cd @var{pathdir}
29247 Set @value{GDBN}'s working directory.
29249 @subsubheading @value{GDBN} Command
29251 The corresponding @value{GDBN} command is @samp{cd}.
29253 @subsubheading Example
29257 -environment-cd /kwikemart/marge/ezannoni/flathead-dev/devo/gdb
29263 @subheading The @code{-environment-directory} Command
29264 @findex -environment-directory
29266 @subsubheading Synopsis
29269 -environment-directory [ -r ] [ @var{pathdir} ]+
29272 Add directories @var{pathdir} to beginning of search path for source files.
29273 If the @samp{-r} option is used, the search path is reset to the default
29274 search path. If directories @var{pathdir} are supplied in addition to the
29275 @samp{-r} option, the search path is first reset and then addition
29277 Multiple directories may be specified, separated by blanks. Specifying
29278 multiple directories in a single command
29279 results in the directories added to the beginning of the
29280 search path in the same order they were presented in the command.
29281 If blanks are needed as
29282 part of a directory name, double-quotes should be used around
29283 the name. In the command output, the path will show up separated
29284 by the system directory-separator character. The directory-separator
29285 character must not be used
29286 in any directory name.
29287 If no directories are specified, the current search path is displayed.
29289 @subsubheading @value{GDBN} Command
29291 The corresponding @value{GDBN} command is @samp{dir}.
29293 @subsubheading Example
29297 -environment-directory /kwikemart/marge/ezannoni/flathead-dev/devo/gdb
29298 ^done,source-path="/kwikemart/marge/ezannoni/flathead-dev/devo/gdb:$cdir:$cwd"
29300 -environment-directory ""
29301 ^done,source-path="/kwikemart/marge/ezannoni/flathead-dev/devo/gdb:$cdir:$cwd"
29303 -environment-directory -r /home/jjohnstn/src/gdb /usr/src
29304 ^done,source-path="/home/jjohnstn/src/gdb:/usr/src:$cdir:$cwd"
29306 -environment-directory -r
29307 ^done,source-path="$cdir:$cwd"
29312 @subheading The @code{-environment-path} Command
29313 @findex -environment-path
29315 @subsubheading Synopsis
29318 -environment-path [ -r ] [ @var{pathdir} ]+
29321 Add directories @var{pathdir} to beginning of search path for object files.
29322 If the @samp{-r} option is used, the search path is reset to the original
29323 search path that existed at gdb start-up. If directories @var{pathdir} are
29324 supplied in addition to the
29325 @samp{-r} option, the search path is first reset and then addition
29327 Multiple directories may be specified, separated by blanks. Specifying
29328 multiple directories in a single command
29329 results in the directories added to the beginning of the
29330 search path in the same order they were presented in the command.
29331 If blanks are needed as
29332 part of a directory name, double-quotes should be used around
29333 the name. In the command output, the path will show up separated
29334 by the system directory-separator character. The directory-separator
29335 character must not be used
29336 in any directory name.
29337 If no directories are specified, the current path is displayed.
29340 @subsubheading @value{GDBN} Command
29342 The corresponding @value{GDBN} command is @samp{path}.
29344 @subsubheading Example
29349 ^done,path="/usr/bin"
29351 -environment-path /kwikemart/marge/ezannoni/flathead-dev/ppc-eabi/gdb /bin
29352 ^done,path="/kwikemart/marge/ezannoni/flathead-dev/ppc-eabi/gdb:/bin:/usr/bin"
29354 -environment-path -r /usr/local/bin
29355 ^done,path="/usr/local/bin:/usr/bin"
29360 @subheading The @code{-environment-pwd} Command
29361 @findex -environment-pwd
29363 @subsubheading Synopsis
29369 Show the current working directory.
29371 @subsubheading @value{GDBN} Command
29373 The corresponding @value{GDBN} command is @samp{pwd}.
29375 @subsubheading Example
29380 ^done,cwd="/kwikemart/marge/ezannoni/flathead-dev/devo/gdb"
29384 @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
29385 @node GDB/MI Thread Commands
29386 @section @sc{gdb/mi} Thread Commands
29389 @subheading The @code{-thread-info} Command
29390 @findex -thread-info
29392 @subsubheading Synopsis
29395 -thread-info [ @var{thread-id} ]
29398 Reports information about either a specific thread, if
29399 the @var{thread-id} parameter is present, or about all
29400 threads. When printing information about all threads,
29401 also reports the current thread.
29403 @subsubheading @value{GDBN} Command
29405 The @samp{info thread} command prints the same information
29408 @subsubheading Result
29410 The result is a list of threads. The following attributes are
29411 defined for a given thread:
29415 This field exists only for the current thread. It has the value @samp{*}.
29418 The identifier that @value{GDBN} uses to refer to the thread.
29421 The identifier that the target uses to refer to the thread.
29424 Extra information about the thread, in a target-specific format. This
29428 The name of the thread. If the user specified a name using the
29429 @code{thread name} command, then this name is given. Otherwise, if
29430 @value{GDBN} can extract the thread name from the target, then that
29431 name is given. If @value{GDBN} cannot find the thread name, then this
29435 The stack frame currently executing in the thread.
29438 The thread's state. The @samp{state} field may have the following
29443 The thread is stopped. Frame information is available for stopped
29447 The thread is running. There's no frame information for running
29453 If @value{GDBN} can find the CPU core on which this thread is running,
29454 then this field is the core identifier. This field is optional.
29458 @subsubheading Example
29463 @{id="2",target-id="Thread 0xb7e14b90 (LWP 21257)",
29464 frame=@{level="0",addr="0xffffe410",func="__kernel_vsyscall",
29465 args=[]@},state="running"@},
29466 @{id="1",target-id="Thread 0xb7e156b0 (LWP 21254)",
29467 frame=@{level="0",addr="0x0804891f",func="foo",
29468 args=[@{name="i",value="10"@}],
29469 file="/tmp/a.c",fullname="/tmp/a.c",line="158"@},
29470 state="running"@}],
29471 current-thread-id="1"
29475 @subheading The @code{-thread-list-ids} Command
29476 @findex -thread-list-ids
29478 @subsubheading Synopsis
29484 Produces a list of the currently known @value{GDBN} thread ids. At the
29485 end of the list it also prints the total number of such threads.
29487 This command is retained for historical reasons, the
29488 @code{-thread-info} command should be used instead.
29490 @subsubheading @value{GDBN} Command
29492 Part of @samp{info threads} supplies the same information.
29494 @subsubheading Example
29499 ^done,thread-ids=@{thread-id="3",thread-id="2",thread-id="1"@},
29500 current-thread-id="1",number-of-threads="3"
29505 @subheading The @code{-thread-select} Command
29506 @findex -thread-select
29508 @subsubheading Synopsis
29511 -thread-select @var{threadnum}
29514 Make @var{threadnum} the current thread. It prints the number of the new
29515 current thread, and the topmost frame for that thread.
29517 This command is deprecated in favor of explicitly using the
29518 @samp{--thread} option to each command.
29520 @subsubheading @value{GDBN} Command
29522 The corresponding @value{GDBN} command is @samp{thread}.
29524 @subsubheading Example
29531 *stopped,reason="end-stepping-range",thread-id="2",line="187",
29532 file="../../../devo/gdb/testsuite/gdb.threads/linux-dp.c"
29536 thread-ids=@{thread-id="3",thread-id="2",thread-id="1"@},
29537 number-of-threads="3"
29540 ^done,new-thread-id="3",
29541 frame=@{level="0",func="vprintf",
29542 args=[@{name="format",value="0x8048e9c \"%*s%c %d %c\\n\""@},
29543 @{name="arg",value="0x2"@}],file="vprintf.c",line="31"@}
29547 @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
29548 @node GDB/MI Ada Tasking Commands
29549 @section @sc{gdb/mi} Ada Tasking Commands
29551 @subheading The @code{-ada-task-info} Command
29552 @findex -ada-task-info
29554 @subsubheading Synopsis
29557 -ada-task-info [ @var{task-id} ]
29560 Reports information about either a specific Ada task, if the
29561 @var{task-id} parameter is present, or about all Ada tasks.
29563 @subsubheading @value{GDBN} Command
29565 The @samp{info tasks} command prints the same information
29566 about all Ada tasks (@pxref{Ada Tasks}).
29568 @subsubheading Result
29570 The result is a table of Ada tasks. The following columns are
29571 defined for each Ada task:
29575 This field exists only for the current thread. It has the value @samp{*}.
29578 The identifier that @value{GDBN} uses to refer to the Ada task.
29581 The identifier that the target uses to refer to the Ada task.
29584 The identifier of the thread corresponding to the Ada task.
29586 This field should always exist, as Ada tasks are always implemented
29587 on top of a thread. But if @value{GDBN} cannot find this corresponding
29588 thread for any reason, the field is omitted.
29591 This field exists only when the task was created by another task.
29592 In this case, it provides the ID of the parent task.
29595 The base priority of the task.
29598 The current state of the task. For a detailed description of the
29599 possible states, see @ref{Ada Tasks}.
29602 The name of the task.
29606 @subsubheading Example
29610 ^done,tasks=@{nr_rows="3",nr_cols="8",
29611 hdr=[@{width="1",alignment="-1",col_name="current",colhdr=""@},
29612 @{width="3",alignment="1",col_name="id",colhdr="ID"@},
29613 @{width="9",alignment="1",col_name="task-id",colhdr="TID"@},
29614 @{width="4",alignment="1",col_name="thread-id",colhdr=""@},
29615 @{width="4",alignment="1",col_name="parent-id",colhdr="P-ID"@},
29616 @{width="3",alignment="1",col_name="priority",colhdr="Pri"@},
29617 @{width="22",alignment="-1",col_name="state",colhdr="State"@},
29618 @{width="1",alignment="2",col_name="name",colhdr="Name"@}],
29619 body=[@{current="*",id="1",task-id=" 644010",thread-id="1",priority="48",
29620 state="Child Termination Wait",name="main_task"@}]@}
29624 @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
29625 @node GDB/MI Program Execution
29626 @section @sc{gdb/mi} Program Execution
29628 These are the asynchronous commands which generate the out-of-band
29629 record @samp{*stopped}. Currently @value{GDBN} only really executes
29630 asynchronously with remote targets and this interaction is mimicked in
29633 @subheading The @code{-exec-continue} Command
29634 @findex -exec-continue
29636 @subsubheading Synopsis
29639 -exec-continue [--reverse] [--all|--thread-group N]
29642 Resumes the execution of the inferior program, which will continue
29643 to execute until it reaches a debugger stop event. If the
29644 @samp{--reverse} option is specified, execution resumes in reverse until
29645 it reaches a stop event. Stop events may include
29648 breakpoints or watchpoints
29650 signals or exceptions
29652 the end of the process (or its beginning under @samp{--reverse})
29654 the end or beginning of a replay log if one is being used.
29656 In all-stop mode (@pxref{All-Stop
29657 Mode}), may resume only one thread, or all threads, depending on the
29658 value of the @samp{scheduler-locking} variable. If @samp{--all} is
29659 specified, all threads (in all inferiors) will be resumed. The @samp{--all} option is
29660 ignored in all-stop mode. If the @samp{--thread-group} options is
29661 specified, then all threads in that thread group are resumed.
29663 @subsubheading @value{GDBN} Command
29665 The corresponding @value{GDBN} corresponding is @samp{continue}.
29667 @subsubheading Example
29674 *stopped,reason="breakpoint-hit",disp="keep",bkptno="2",frame=@{
29675 func="foo",args=[],file="hello.c",fullname="/home/foo/bar/hello.c",
29681 @subheading The @code{-exec-finish} Command
29682 @findex -exec-finish
29684 @subsubheading Synopsis
29687 -exec-finish [--reverse]
29690 Resumes the execution of the inferior program until the current
29691 function is exited. Displays the results returned by the function.
29692 If the @samp{--reverse} option is specified, resumes the reverse
29693 execution of the inferior program until the point where current
29694 function was called.
29696 @subsubheading @value{GDBN} Command
29698 The corresponding @value{GDBN} command is @samp{finish}.
29700 @subsubheading Example
29702 Function returning @code{void}.
29709 *stopped,reason="function-finished",frame=@{func="main",args=[],
29710 file="hello.c",fullname="/home/foo/bar/hello.c",line="7"@}
29714 Function returning other than @code{void}. The name of the internal
29715 @value{GDBN} variable storing the result is printed, together with the
29722 *stopped,reason="function-finished",frame=@{addr="0x000107b0",func="foo",
29723 args=[@{name="a",value="1"],@{name="b",value="9"@}@},
29724 file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@},
29725 gdb-result-var="$1",return-value="0"
29730 @subheading The @code{-exec-interrupt} Command
29731 @findex -exec-interrupt
29733 @subsubheading Synopsis
29736 -exec-interrupt [--all|--thread-group N]
29739 Interrupts the background execution of the target. Note how the token
29740 associated with the stop message is the one for the execution command
29741 that has been interrupted. The token for the interrupt itself only
29742 appears in the @samp{^done} output. If the user is trying to
29743 interrupt a non-running program, an error message will be printed.
29745 Note that when asynchronous execution is enabled, this command is
29746 asynchronous just like other execution commands. That is, first the
29747 @samp{^done} response will be printed, and the target stop will be
29748 reported after that using the @samp{*stopped} notification.
29750 In non-stop mode, only the context thread is interrupted by default.
29751 All threads (in all inferiors) will be interrupted if the
29752 @samp{--all} option is specified. If the @samp{--thread-group}
29753 option is specified, all threads in that group will be interrupted.
29755 @subsubheading @value{GDBN} Command
29757 The corresponding @value{GDBN} command is @samp{interrupt}.
29759 @subsubheading Example
29770 111*stopped,signal-name="SIGINT",signal-meaning="Interrupt",
29771 frame=@{addr="0x00010140",func="foo",args=[],file="try.c",
29772 fullname="/home/foo/bar/try.c",line="13"@}
29777 ^error,msg="mi_cmd_exec_interrupt: Inferior not executing."
29781 @subheading The @code{-exec-jump} Command
29784 @subsubheading Synopsis
29787 -exec-jump @var{location}
29790 Resumes execution of the inferior program at the location specified by
29791 parameter. @xref{Specify Location}, for a description of the
29792 different forms of @var{location}.
29794 @subsubheading @value{GDBN} Command
29796 The corresponding @value{GDBN} command is @samp{jump}.
29798 @subsubheading Example
29801 -exec-jump foo.c:10
29802 *running,thread-id="all"
29807 @subheading The @code{-exec-next} Command
29810 @subsubheading Synopsis
29813 -exec-next [--reverse]
29816 Resumes execution of the inferior program, stopping when the beginning
29817 of the next source line is reached.
29819 If the @samp{--reverse} option is specified, resumes reverse execution
29820 of the inferior program, stopping at the beginning of the previous
29821 source line. If you issue this command on the first line of a
29822 function, it will take you back to the caller of that function, to the
29823 source line where the function was called.
29826 @subsubheading @value{GDBN} Command
29828 The corresponding @value{GDBN} command is @samp{next}.
29830 @subsubheading Example
29836 *stopped,reason="end-stepping-range",line="8",file="hello.c"
29841 @subheading The @code{-exec-next-instruction} Command
29842 @findex -exec-next-instruction
29844 @subsubheading Synopsis
29847 -exec-next-instruction [--reverse]
29850 Executes one machine instruction. If the instruction is a function
29851 call, continues until the function returns. If the program stops at an
29852 instruction in the middle of a source line, the address will be
29855 If the @samp{--reverse} option is specified, resumes reverse execution
29856 of the inferior program, stopping at the previous instruction. If the
29857 previously executed instruction was a return from another function,
29858 it will continue to execute in reverse until the call to that function
29859 (from the current stack frame) is reached.
29861 @subsubheading @value{GDBN} Command
29863 The corresponding @value{GDBN} command is @samp{nexti}.
29865 @subsubheading Example
29869 -exec-next-instruction
29873 *stopped,reason="end-stepping-range",
29874 addr="0x000100d4",line="5",file="hello.c"
29879 @subheading The @code{-exec-return} Command
29880 @findex -exec-return
29882 @subsubheading Synopsis
29888 Makes current function return immediately. Doesn't execute the inferior.
29889 Displays the new current frame.
29891 @subsubheading @value{GDBN} Command
29893 The corresponding @value{GDBN} command is @samp{return}.
29895 @subsubheading Example
29899 200-break-insert callee4
29900 200^done,bkpt=@{number="1",addr="0x00010734",
29901 file="../../../devo/gdb/testsuite/gdb.mi/basics.c",line="8"@}
29906 000*stopped,reason="breakpoint-hit",disp="keep",bkptno="1",
29907 frame=@{func="callee4",args=[],
29908 file="../../../devo/gdb/testsuite/gdb.mi/basics.c",
29909 fullname="/home/foo/bar/devo/gdb/testsuite/gdb.mi/basics.c",line="8"@}
29915 111^done,frame=@{level="0",func="callee3",
29916 args=[@{name="strarg",
29917 value="0x11940 \"A string argument.\""@}],
29918 file="../../../devo/gdb/testsuite/gdb.mi/basics.c",
29919 fullname="/home/foo/bar/devo/gdb/testsuite/gdb.mi/basics.c",line="18"@}
29924 @subheading The @code{-exec-run} Command
29927 @subsubheading Synopsis
29930 -exec-run [--all | --thread-group N]
29933 Starts execution of the inferior from the beginning. The inferior
29934 executes until either a breakpoint is encountered or the program
29935 exits. In the latter case the output will include an exit code, if
29936 the program has exited exceptionally.
29938 When no option is specified, the current inferior is started. If the
29939 @samp{--thread-group} option is specified, it should refer to a thread
29940 group of type @samp{process}, and that thread group will be started.
29941 If the @samp{--all} option is specified, then all inferiors will be started.
29943 @subsubheading @value{GDBN} Command
29945 The corresponding @value{GDBN} command is @samp{run}.
29947 @subsubheading Examples
29952 ^done,bkpt=@{number="1",addr="0x0001072c",file="recursive2.c",line="4"@}
29957 *stopped,reason="breakpoint-hit",disp="keep",bkptno="1",
29958 frame=@{func="main",args=[],file="recursive2.c",
29959 fullname="/home/foo/bar/recursive2.c",line="4"@}
29964 Program exited normally:
29972 *stopped,reason="exited-normally"
29977 Program exited exceptionally:
29985 *stopped,reason="exited",exit-code="01"
29989 Another way the program can terminate is if it receives a signal such as
29990 @code{SIGINT}. In this case, @sc{gdb/mi} displays this:
29994 *stopped,reason="exited-signalled",signal-name="SIGINT",
29995 signal-meaning="Interrupt"
29999 @c @subheading -exec-signal
30002 @subheading The @code{-exec-step} Command
30005 @subsubheading Synopsis
30008 -exec-step [--reverse]
30011 Resumes execution of the inferior program, stopping when the beginning
30012 of the next source line is reached, if the next source line is not a
30013 function call. If it is, stop at the first instruction of the called
30014 function. If the @samp{--reverse} option is specified, resumes reverse
30015 execution of the inferior program, stopping at the beginning of the
30016 previously executed source line.
30018 @subsubheading @value{GDBN} Command
30020 The corresponding @value{GDBN} command is @samp{step}.
30022 @subsubheading Example
30024 Stepping into a function:
30030 *stopped,reason="end-stepping-range",
30031 frame=@{func="foo",args=[@{name="a",value="10"@},
30032 @{name="b",value="0"@}],file="recursive2.c",
30033 fullname="/home/foo/bar/recursive2.c",line="11"@}
30043 *stopped,reason="end-stepping-range",line="14",file="recursive2.c"
30048 @subheading The @code{-exec-step-instruction} Command
30049 @findex -exec-step-instruction
30051 @subsubheading Synopsis
30054 -exec-step-instruction [--reverse]
30057 Resumes the inferior which executes one machine instruction. If the
30058 @samp{--reverse} option is specified, resumes reverse execution of the
30059 inferior program, stopping at the previously executed instruction.
30060 The output, once @value{GDBN} has stopped, will vary depending on
30061 whether we have stopped in the middle of a source line or not. In the
30062 former case, the address at which the program stopped will be printed
30065 @subsubheading @value{GDBN} Command
30067 The corresponding @value{GDBN} command is @samp{stepi}.
30069 @subsubheading Example
30073 -exec-step-instruction
30077 *stopped,reason="end-stepping-range",
30078 frame=@{func="foo",args=[],file="try.c",
30079 fullname="/home/foo/bar/try.c",line="10"@}
30081 -exec-step-instruction
30085 *stopped,reason="end-stepping-range",
30086 frame=@{addr="0x000100f4",func="foo",args=[],file="try.c",
30087 fullname="/home/foo/bar/try.c",line="10"@}
30092 @subheading The @code{-exec-until} Command
30093 @findex -exec-until
30095 @subsubheading Synopsis
30098 -exec-until [ @var{location} ]
30101 Executes the inferior until the @var{location} specified in the
30102 argument is reached. If there is no argument, the inferior executes
30103 until a source line greater than the current one is reached. The
30104 reason for stopping in this case will be @samp{location-reached}.
30106 @subsubheading @value{GDBN} Command
30108 The corresponding @value{GDBN} command is @samp{until}.
30110 @subsubheading Example
30114 -exec-until recursive2.c:6
30118 *stopped,reason="location-reached",frame=@{func="main",args=[],
30119 file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="6"@}
30124 @subheading -file-clear
30125 Is this going away????
30128 @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
30129 @node GDB/MI Stack Manipulation
30130 @section @sc{gdb/mi} Stack Manipulation Commands
30133 @subheading The @code{-stack-info-frame} Command
30134 @findex -stack-info-frame
30136 @subsubheading Synopsis
30142 Get info on the selected frame.
30144 @subsubheading @value{GDBN} Command
30146 The corresponding @value{GDBN} command is @samp{info frame} or @samp{frame}
30147 (without arguments).
30149 @subsubheading Example
30154 ^done,frame=@{level="1",addr="0x0001076c",func="callee3",
30155 file="../../../devo/gdb/testsuite/gdb.mi/basics.c",
30156 fullname="/home/foo/bar/devo/gdb/testsuite/gdb.mi/basics.c",line="17"@}
30160 @subheading The @code{-stack-info-depth} Command
30161 @findex -stack-info-depth
30163 @subsubheading Synopsis
30166 -stack-info-depth [ @var{max-depth} ]
30169 Return the depth of the stack. If the integer argument @var{max-depth}
30170 is specified, do not count beyond @var{max-depth} frames.
30172 @subsubheading @value{GDBN} Command
30174 There's no equivalent @value{GDBN} command.
30176 @subsubheading Example
30178 For a stack with frame levels 0 through 11:
30185 -stack-info-depth 4
30188 -stack-info-depth 12
30191 -stack-info-depth 11
30194 -stack-info-depth 13
30199 @subheading The @code{-stack-list-arguments} Command
30200 @findex -stack-list-arguments
30202 @subsubheading Synopsis
30205 -stack-list-arguments @var{print-values}
30206 [ @var{low-frame} @var{high-frame} ]
30209 Display a list of the arguments for the frames between @var{low-frame}
30210 and @var{high-frame} (inclusive). If @var{low-frame} and
30211 @var{high-frame} are not provided, list the arguments for the whole
30212 call stack. If the two arguments are equal, show the single frame
30213 at the corresponding level. It is an error if @var{low-frame} is
30214 larger than the actual number of frames. On the other hand,
30215 @var{high-frame} may be larger than the actual number of frames, in
30216 which case only existing frames will be returned.
30218 If @var{print-values} is 0 or @code{--no-values}, print only the names of
30219 the variables; if it is 1 or @code{--all-values}, print also their
30220 values; and if it is 2 or @code{--simple-values}, print the name,
30221 type and value for simple data types, and the name and type for arrays,
30222 structures and unions.
30224 Use of this command to obtain arguments in a single frame is
30225 deprecated in favor of the @samp{-stack-list-variables} command.
30227 @subsubheading @value{GDBN} Command
30229 @value{GDBN} does not have an equivalent command. @code{gdbtk} has a
30230 @samp{gdb_get_args} command which partially overlaps with the
30231 functionality of @samp{-stack-list-arguments}.
30233 @subsubheading Example
30240 frame=@{level="0",addr="0x00010734",func="callee4",
30241 file="../../../devo/gdb/testsuite/gdb.mi/basics.c",
30242 fullname="/home/foo/bar/devo/gdb/testsuite/gdb.mi/basics.c",line="8"@},
30243 frame=@{level="1",addr="0x0001076c",func="callee3",
30244 file="../../../devo/gdb/testsuite/gdb.mi/basics.c",
30245 fullname="/home/foo/bar/devo/gdb/testsuite/gdb.mi/basics.c",line="17"@},
30246 frame=@{level="2",addr="0x0001078c",func="callee2",
30247 file="../../../devo/gdb/testsuite/gdb.mi/basics.c",
30248 fullname="/home/foo/bar/devo/gdb/testsuite/gdb.mi/basics.c",line="22"@},
30249 frame=@{level="3",addr="0x000107b4",func="callee1",
30250 file="../../../devo/gdb/testsuite/gdb.mi/basics.c",
30251 fullname="/home/foo/bar/devo/gdb/testsuite/gdb.mi/basics.c",line="27"@},
30252 frame=@{level="4",addr="0x000107e0",func="main",
30253 file="../../../devo/gdb/testsuite/gdb.mi/basics.c",
30254 fullname="/home/foo/bar/devo/gdb/testsuite/gdb.mi/basics.c",line="32"@}]
30256 -stack-list-arguments 0
30259 frame=@{level="0",args=[]@},
30260 frame=@{level="1",args=[name="strarg"]@},
30261 frame=@{level="2",args=[name="intarg",name="strarg"]@},
30262 frame=@{level="3",args=[name="intarg",name="strarg",name="fltarg"]@},
30263 frame=@{level="4",args=[]@}]
30265 -stack-list-arguments 1
30268 frame=@{level="0",args=[]@},
30270 args=[@{name="strarg",value="0x11940 \"A string argument.\""@}]@},
30271 frame=@{level="2",args=[
30272 @{name="intarg",value="2"@},
30273 @{name="strarg",value="0x11940 \"A string argument.\""@}]@},
30274 @{frame=@{level="3",args=[
30275 @{name="intarg",value="2"@},
30276 @{name="strarg",value="0x11940 \"A string argument.\""@},
30277 @{name="fltarg",value="3.5"@}]@},
30278 frame=@{level="4",args=[]@}]
30280 -stack-list-arguments 0 2 2
30281 ^done,stack-args=[frame=@{level="2",args=[name="intarg",name="strarg"]@}]
30283 -stack-list-arguments 1 2 2
30284 ^done,stack-args=[frame=@{level="2",
30285 args=[@{name="intarg",value="2"@},
30286 @{name="strarg",value="0x11940 \"A string argument.\""@}]@}]
30290 @c @subheading -stack-list-exception-handlers
30293 @subheading The @code{-stack-list-frames} Command
30294 @findex -stack-list-frames
30296 @subsubheading Synopsis
30299 -stack-list-frames [ @var{low-frame} @var{high-frame} ]
30302 List the frames currently on the stack. For each frame it displays the
30307 The frame number, 0 being the topmost frame, i.e., the innermost function.
30309 The @code{$pc} value for that frame.
30313 File name of the source file where the function lives.
30314 @item @var{fullname}
30315 The full file name of the source file where the function lives.
30317 Line number corresponding to the @code{$pc}.
30319 The shared library where this function is defined. This is only given
30320 if the frame's function is not known.
30323 If invoked without arguments, this command prints a backtrace for the
30324 whole stack. If given two integer arguments, it shows the frames whose
30325 levels are between the two arguments (inclusive). If the two arguments
30326 are equal, it shows the single frame at the corresponding level. It is
30327 an error if @var{low-frame} is larger than the actual number of
30328 frames. On the other hand, @var{high-frame} may be larger than the
30329 actual number of frames, in which case only existing frames will be returned.
30331 @subsubheading @value{GDBN} Command
30333 The corresponding @value{GDBN} commands are @samp{backtrace} and @samp{where}.
30335 @subsubheading Example
30337 Full stack backtrace:
30343 [frame=@{level="0",addr="0x0001076c",func="foo",
30344 file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="11"@},
30345 frame=@{level="1",addr="0x000107a4",func="foo",
30346 file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@},
30347 frame=@{level="2",addr="0x000107a4",func="foo",
30348 file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@},
30349 frame=@{level="3",addr="0x000107a4",func="foo",
30350 file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@},
30351 frame=@{level="4",addr="0x000107a4",func="foo",
30352 file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@},
30353 frame=@{level="5",addr="0x000107a4",func="foo",
30354 file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@},
30355 frame=@{level="6",addr="0x000107a4",func="foo",
30356 file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@},
30357 frame=@{level="7",addr="0x000107a4",func="foo",
30358 file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@},
30359 frame=@{level="8",addr="0x000107a4",func="foo",
30360 file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@},
30361 frame=@{level="9",addr="0x000107a4",func="foo",
30362 file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@},
30363 frame=@{level="10",addr="0x000107a4",func="foo",
30364 file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@},
30365 frame=@{level="11",addr="0x00010738",func="main",
30366 file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="4"@}]
30370 Show frames between @var{low_frame} and @var{high_frame}:
30374 -stack-list-frames 3 5
30376 [frame=@{level="3",addr="0x000107a4",func="foo",
30377 file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@},
30378 frame=@{level="4",addr="0x000107a4",func="foo",
30379 file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@},
30380 frame=@{level="5",addr="0x000107a4",func="foo",
30381 file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@}]
30385 Show a single frame:
30389 -stack-list-frames 3 3
30391 [frame=@{level="3",addr="0x000107a4",func="foo",
30392 file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@}]
30397 @subheading The @code{-stack-list-locals} Command
30398 @findex -stack-list-locals
30400 @subsubheading Synopsis
30403 -stack-list-locals @var{print-values}
30406 Display the local variable names for the selected frame. If
30407 @var{print-values} is 0 or @code{--no-values}, print only the names of
30408 the variables; if it is 1 or @code{--all-values}, print also their
30409 values; and if it is 2 or @code{--simple-values}, print the name,
30410 type and value for simple data types, and the name and type for arrays,
30411 structures and unions. In this last case, a frontend can immediately
30412 display the value of simple data types and create variable objects for
30413 other data types when the user wishes to explore their values in
30416 This command is deprecated in favor of the
30417 @samp{-stack-list-variables} command.
30419 @subsubheading @value{GDBN} Command
30421 @samp{info locals} in @value{GDBN}, @samp{gdb_get_locals} in @code{gdbtk}.
30423 @subsubheading Example
30427 -stack-list-locals 0
30428 ^done,locals=[name="A",name="B",name="C"]
30430 -stack-list-locals --all-values
30431 ^done,locals=[@{name="A",value="1"@},@{name="B",value="2"@},
30432 @{name="C",value="@{1, 2, 3@}"@}]
30433 -stack-list-locals --simple-values
30434 ^done,locals=[@{name="A",type="int",value="1"@},
30435 @{name="B",type="int",value="2"@},@{name="C",type="int [3]"@}]
30439 @subheading The @code{-stack-list-variables} Command
30440 @findex -stack-list-variables
30442 @subsubheading Synopsis
30445 -stack-list-variables @var{print-values}
30448 Display the names of local variables and function arguments for the selected frame. If
30449 @var{print-values} is 0 or @code{--no-values}, print only the names of
30450 the variables; if it is 1 or @code{--all-values}, print also their
30451 values; and if it is 2 or @code{--simple-values}, print the name,
30452 type and value for simple data types, and the name and type for arrays,
30453 structures and unions.
30455 @subsubheading Example
30459 -stack-list-variables --thread 1 --frame 0 --all-values
30460 ^done,variables=[@{name="x",value="11"@},@{name="s",value="@{a = 1, b = 2@}"@}]
30465 @subheading The @code{-stack-select-frame} Command
30466 @findex -stack-select-frame
30468 @subsubheading Synopsis
30471 -stack-select-frame @var{framenum}
30474 Change the selected frame. Select a different frame @var{framenum} on
30477 This command in deprecated in favor of passing the @samp{--frame}
30478 option to every command.
30480 @subsubheading @value{GDBN} Command
30482 The corresponding @value{GDBN} commands are @samp{frame}, @samp{up},
30483 @samp{down}, @samp{select-frame}, @samp{up-silent}, and @samp{down-silent}.
30485 @subsubheading Example
30489 -stack-select-frame 2
30494 @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
30495 @node GDB/MI Variable Objects
30496 @section @sc{gdb/mi} Variable Objects
30500 @subheading Motivation for Variable Objects in @sc{gdb/mi}
30502 For the implementation of a variable debugger window (locals, watched
30503 expressions, etc.), we are proposing the adaptation of the existing code
30504 used by @code{Insight}.
30506 The two main reasons for that are:
30510 It has been proven in practice (it is already on its second generation).
30513 It will shorten development time (needless to say how important it is
30517 The original interface was designed to be used by Tcl code, so it was
30518 slightly changed so it could be used through @sc{gdb/mi}. This section
30519 describes the @sc{gdb/mi} operations that will be available and gives some
30520 hints about their use.
30522 @emph{Note}: In addition to the set of operations described here, we
30523 expect the @sc{gui} implementation of a variable window to require, at
30524 least, the following operations:
30527 @item @code{-gdb-show} @code{output-radix}
30528 @item @code{-stack-list-arguments}
30529 @item @code{-stack-list-locals}
30530 @item @code{-stack-select-frame}
30535 @subheading Introduction to Variable Objects
30537 @cindex variable objects in @sc{gdb/mi}
30539 Variable objects are "object-oriented" MI interface for examining and
30540 changing values of expressions. Unlike some other MI interfaces that
30541 work with expressions, variable objects are specifically designed for
30542 simple and efficient presentation in the frontend. A variable object
30543 is identified by string name. When a variable object is created, the
30544 frontend specifies the expression for that variable object. The
30545 expression can be a simple variable, or it can be an arbitrary complex
30546 expression, and can even involve CPU registers. After creating a
30547 variable object, the frontend can invoke other variable object
30548 operations---for example to obtain or change the value of a variable
30549 object, or to change display format.
30551 Variable objects have hierarchical tree structure. Any variable object
30552 that corresponds to a composite type, such as structure in C, has
30553 a number of child variable objects, for example corresponding to each
30554 element of a structure. A child variable object can itself have
30555 children, recursively. Recursion ends when we reach
30556 leaf variable objects, which always have built-in types. Child variable
30557 objects are created only by explicit request, so if a frontend
30558 is not interested in the children of a particular variable object, no
30559 child will be created.
30561 For a leaf variable object it is possible to obtain its value as a
30562 string, or set the value from a string. String value can be also
30563 obtained for a non-leaf variable object, but it's generally a string
30564 that only indicates the type of the object, and does not list its
30565 contents. Assignment to a non-leaf variable object is not allowed.
30567 A frontend does not need to read the values of all variable objects each time
30568 the program stops. Instead, MI provides an update command that lists all
30569 variable objects whose values has changed since the last update
30570 operation. This considerably reduces the amount of data that must
30571 be transferred to the frontend. As noted above, children variable
30572 objects are created on demand, and only leaf variable objects have a
30573 real value. As result, gdb will read target memory only for leaf
30574 variables that frontend has created.
30576 The automatic update is not always desirable. For example, a frontend
30577 might want to keep a value of some expression for future reference,
30578 and never update it. For another example, fetching memory is
30579 relatively slow for embedded targets, so a frontend might want
30580 to disable automatic update for the variables that are either not
30581 visible on the screen, or ``closed''. This is possible using so
30582 called ``frozen variable objects''. Such variable objects are never
30583 implicitly updated.
30585 Variable objects can be either @dfn{fixed} or @dfn{floating}. For the
30586 fixed variable object, the expression is parsed when the variable
30587 object is created, including associating identifiers to specific
30588 variables. The meaning of expression never changes. For a floating
30589 variable object the values of variables whose names appear in the
30590 expressions are re-evaluated every time in the context of the current
30591 frame. Consider this example:
30596 struct work_state state;
30603 If a fixed variable object for the @code{state} variable is created in
30604 this function, and we enter the recursive call, the variable
30605 object will report the value of @code{state} in the top-level
30606 @code{do_work} invocation. On the other hand, a floating variable
30607 object will report the value of @code{state} in the current frame.
30609 If an expression specified when creating a fixed variable object
30610 refers to a local variable, the variable object becomes bound to the
30611 thread and frame in which the variable object is created. When such
30612 variable object is updated, @value{GDBN} makes sure that the
30613 thread/frame combination the variable object is bound to still exists,
30614 and re-evaluates the variable object in context of that thread/frame.
30616 The following is the complete set of @sc{gdb/mi} operations defined to
30617 access this functionality:
30619 @multitable @columnfractions .4 .6
30620 @item @strong{Operation}
30621 @tab @strong{Description}
30623 @item @code{-enable-pretty-printing}
30624 @tab enable Python-based pretty-printing
30625 @item @code{-var-create}
30626 @tab create a variable object
30627 @item @code{-var-delete}
30628 @tab delete the variable object and/or its children
30629 @item @code{-var-set-format}
30630 @tab set the display format of this variable
30631 @item @code{-var-show-format}
30632 @tab show the display format of this variable
30633 @item @code{-var-info-num-children}
30634 @tab tells how many children this object has
30635 @item @code{-var-list-children}
30636 @tab return a list of the object's children
30637 @item @code{-var-info-type}
30638 @tab show the type of this variable object
30639 @item @code{-var-info-expression}
30640 @tab print parent-relative expression that this variable object represents
30641 @item @code{-var-info-path-expression}
30642 @tab print full expression that this variable object represents
30643 @item @code{-var-show-attributes}
30644 @tab is this variable editable? does it exist here?
30645 @item @code{-var-evaluate-expression}
30646 @tab get the value of this variable
30647 @item @code{-var-assign}
30648 @tab set the value of this variable
30649 @item @code{-var-update}
30650 @tab update the variable and its children
30651 @item @code{-var-set-frozen}
30652 @tab set frozeness attribute
30653 @item @code{-var-set-update-range}
30654 @tab set range of children to display on update
30657 In the next subsection we describe each operation in detail and suggest
30658 how it can be used.
30660 @subheading Description And Use of Operations on Variable Objects
30662 @subheading The @code{-enable-pretty-printing} Command
30663 @findex -enable-pretty-printing
30666 -enable-pretty-printing
30669 @value{GDBN} allows Python-based visualizers to affect the output of the
30670 MI variable object commands. However, because there was no way to
30671 implement this in a fully backward-compatible way, a front end must
30672 request that this functionality be enabled.
30674 Once enabled, this feature cannot be disabled.
30676 Note that if Python support has not been compiled into @value{GDBN},
30677 this command will still succeed (and do nothing).
30679 This feature is currently (as of @value{GDBN} 7.0) experimental, and
30680 may work differently in future versions of @value{GDBN}.
30682 @subheading The @code{-var-create} Command
30683 @findex -var-create
30685 @subsubheading Synopsis
30688 -var-create @{@var{name} | "-"@}
30689 @{@var{frame-addr} | "*" | "@@"@} @var{expression}
30692 This operation creates a variable object, which allows the monitoring of
30693 a variable, the result of an expression, a memory cell or a CPU
30696 The @var{name} parameter is the string by which the object can be
30697 referenced. It must be unique. If @samp{-} is specified, the varobj
30698 system will generate a string ``varNNNNNN'' automatically. It will be
30699 unique provided that one does not specify @var{name} of that format.
30700 The command fails if a duplicate name is found.
30702 The frame under which the expression should be evaluated can be
30703 specified by @var{frame-addr}. A @samp{*} indicates that the current
30704 frame should be used. A @samp{@@} indicates that a floating variable
30705 object must be created.
30707 @var{expression} is any expression valid on the current language set (must not
30708 begin with a @samp{*}), or one of the following:
30712 @samp{*@var{addr}}, where @var{addr} is the address of a memory cell
30715 @samp{*@var{addr}-@var{addr}} --- a memory address range (TBD)
30718 @samp{$@var{regname}} --- a CPU register name
30721 @cindex dynamic varobj
30722 A varobj's contents may be provided by a Python-based pretty-printer. In this
30723 case the varobj is known as a @dfn{dynamic varobj}. Dynamic varobjs
30724 have slightly different semantics in some cases. If the
30725 @code{-enable-pretty-printing} command is not sent, then @value{GDBN}
30726 will never create a dynamic varobj. This ensures backward
30727 compatibility for existing clients.
30729 @subsubheading Result
30731 This operation returns attributes of the newly-created varobj. These
30736 The name of the varobj.
30739 The number of children of the varobj. This number is not necessarily
30740 reliable for a dynamic varobj. Instead, you must examine the
30741 @samp{has_more} attribute.
30744 The varobj's scalar value. For a varobj whose type is some sort of
30745 aggregate (e.g., a @code{struct}), or for a dynamic varobj, this value
30746 will not be interesting.
30749 The varobj's type. This is a string representation of the type, as
30750 would be printed by the @value{GDBN} CLI. If @samp{print object}
30751 (@pxref{Print Settings, set print object}) is set to @code{on}, the
30752 @emph{actual} (derived) type of the object is shown rather than the
30753 @emph{declared} one.
30756 If a variable object is bound to a specific thread, then this is the
30757 thread's identifier.
30760 For a dynamic varobj, this indicates whether there appear to be any
30761 children available. For a non-dynamic varobj, this will be 0.
30764 This attribute will be present and have the value @samp{1} if the
30765 varobj is a dynamic varobj. If the varobj is not a dynamic varobj,
30766 then this attribute will not be present.
30769 A dynamic varobj can supply a display hint to the front end. The
30770 value comes directly from the Python pretty-printer object's
30771 @code{display_hint} method. @xref{Pretty Printing API}.
30774 Typical output will look like this:
30777 name="@var{name}",numchild="@var{N}",type="@var{type}",thread-id="@var{M}",
30778 has_more="@var{has_more}"
30782 @subheading The @code{-var-delete} Command
30783 @findex -var-delete
30785 @subsubheading Synopsis
30788 -var-delete [ -c ] @var{name}
30791 Deletes a previously created variable object and all of its children.
30792 With the @samp{-c} option, just deletes the children.
30794 Returns an error if the object @var{name} is not found.
30797 @subheading The @code{-var-set-format} Command
30798 @findex -var-set-format
30800 @subsubheading Synopsis
30803 -var-set-format @var{name} @var{format-spec}
30806 Sets the output format for the value of the object @var{name} to be
30809 @anchor{-var-set-format}
30810 The syntax for the @var{format-spec} is as follows:
30813 @var{format-spec} @expansion{}
30814 @{binary | decimal | hexadecimal | octal | natural@}
30817 The natural format is the default format choosen automatically
30818 based on the variable type (like decimal for an @code{int}, hex
30819 for pointers, etc.).
30821 For a variable with children, the format is set only on the
30822 variable itself, and the children are not affected.
30824 @subheading The @code{-var-show-format} Command
30825 @findex -var-show-format
30827 @subsubheading Synopsis
30830 -var-show-format @var{name}
30833 Returns the format used to display the value of the object @var{name}.
30836 @var{format} @expansion{}
30841 @subheading The @code{-var-info-num-children} Command
30842 @findex -var-info-num-children
30844 @subsubheading Synopsis
30847 -var-info-num-children @var{name}
30850 Returns the number of children of a variable object @var{name}:
30856 Note that this number is not completely reliable for a dynamic varobj.
30857 It will return the current number of children, but more children may
30861 @subheading The @code{-var-list-children} Command
30862 @findex -var-list-children
30864 @subsubheading Synopsis
30867 -var-list-children [@var{print-values}] @var{name} [@var{from} @var{to}]
30869 @anchor{-var-list-children}
30871 Return a list of the children of the specified variable object and
30872 create variable objects for them, if they do not already exist. With
30873 a single argument or if @var{print-values} has a value of 0 or
30874 @code{--no-values}, print only the names of the variables; if
30875 @var{print-values} is 1 or @code{--all-values}, also print their
30876 values; and if it is 2 or @code{--simple-values} print the name and
30877 value for simple data types and just the name for arrays, structures
30880 @var{from} and @var{to}, if specified, indicate the range of children
30881 to report. If @var{from} or @var{to} is less than zero, the range is
30882 reset and all children will be reported. Otherwise, children starting
30883 at @var{from} (zero-based) and up to and excluding @var{to} will be
30886 If a child range is requested, it will only affect the current call to
30887 @code{-var-list-children}, but not future calls to @code{-var-update}.
30888 For this, you must instead use @code{-var-set-update-range}. The
30889 intent of this approach is to enable a front end to implement any
30890 update approach it likes; for example, scrolling a view may cause the
30891 front end to request more children with @code{-var-list-children}, and
30892 then the front end could call @code{-var-set-update-range} with a
30893 different range to ensure that future updates are restricted to just
30896 For each child the following results are returned:
30901 Name of the variable object created for this child.
30904 The expression to be shown to the user by the front end to designate this child.
30905 For example this may be the name of a structure member.
30907 For a dynamic varobj, this value cannot be used to form an
30908 expression. There is no way to do this at all with a dynamic varobj.
30910 For C/C@t{++} structures there are several pseudo children returned to
30911 designate access qualifiers. For these pseudo children @var{exp} is
30912 @samp{public}, @samp{private}, or @samp{protected}. In this case the
30913 type and value are not present.
30915 A dynamic varobj will not report the access qualifying
30916 pseudo-children, regardless of the language. This information is not
30917 available at all with a dynamic varobj.
30920 Number of children this child has. For a dynamic varobj, this will be
30924 The type of the child. If @samp{print object}
30925 (@pxref{Print Settings, set print object}) is set to @code{on}, the
30926 @emph{actual} (derived) type of the object is shown rather than the
30927 @emph{declared} one.
30930 If values were requested, this is the value.
30933 If this variable object is associated with a thread, this is the thread id.
30934 Otherwise this result is not present.
30937 If the variable object is frozen, this variable will be present with a value of 1.
30940 The result may have its own attributes:
30944 A dynamic varobj can supply a display hint to the front end. The
30945 value comes directly from the Python pretty-printer object's
30946 @code{display_hint} method. @xref{Pretty Printing API}.
30949 This is an integer attribute which is nonzero if there are children
30950 remaining after the end of the selected range.
30953 @subsubheading Example
30957 -var-list-children n
30958 ^done,numchild=@var{n},children=[child=@{name=@var{name},exp=@var{exp},
30959 numchild=@var{n},type=@var{type}@},@r{(repeats N times)}]
30961 -var-list-children --all-values n
30962 ^done,numchild=@var{n},children=[child=@{name=@var{name},exp=@var{exp},
30963 numchild=@var{n},value=@var{value},type=@var{type}@},@r{(repeats N times)}]
30967 @subheading The @code{-var-info-type} Command
30968 @findex -var-info-type
30970 @subsubheading Synopsis
30973 -var-info-type @var{name}
30976 Returns the type of the specified variable @var{name}. The type is
30977 returned as a string in the same format as it is output by the
30981 type=@var{typename}
30985 @subheading The @code{-var-info-expression} Command
30986 @findex -var-info-expression
30988 @subsubheading Synopsis
30991 -var-info-expression @var{name}
30994 Returns a string that is suitable for presenting this
30995 variable object in user interface. The string is generally
30996 not valid expression in the current language, and cannot be evaluated.
30998 For example, if @code{a} is an array, and variable object
30999 @code{A} was created for @code{a}, then we'll get this output:
31002 (gdb) -var-info-expression A.1
31003 ^done,lang="C",exp="1"
31007 Here, the values of @code{lang} can be @code{@{"C" | "C++" | "Java"@}}.
31009 Note that the output of the @code{-var-list-children} command also
31010 includes those expressions, so the @code{-var-info-expression} command
31013 @subheading The @code{-var-info-path-expression} Command
31014 @findex -var-info-path-expression
31016 @subsubheading Synopsis
31019 -var-info-path-expression @var{name}
31022 Returns an expression that can be evaluated in the current
31023 context and will yield the same value that a variable object has.
31024 Compare this with the @code{-var-info-expression} command, which
31025 result can be used only for UI presentation. Typical use of
31026 the @code{-var-info-path-expression} command is creating a
31027 watchpoint from a variable object.
31029 This command is currently not valid for children of a dynamic varobj,
31030 and will give an error when invoked on one.
31032 For example, suppose @code{C} is a C@t{++} class, derived from class
31033 @code{Base}, and that the @code{Base} class has a member called
31034 @code{m_size}. Assume a variable @code{c} is has the type of
31035 @code{C} and a variable object @code{C} was created for variable
31036 @code{c}. Then, we'll get this output:
31038 (gdb) -var-info-path-expression C.Base.public.m_size
31039 ^done,path_expr=((Base)c).m_size)
31042 @subheading The @code{-var-show-attributes} Command
31043 @findex -var-show-attributes
31045 @subsubheading Synopsis
31048 -var-show-attributes @var{name}
31051 List attributes of the specified variable object @var{name}:
31054 status=@var{attr} [ ( ,@var{attr} )* ]
31058 where @var{attr} is @code{@{ @{ editable | noneditable @} | TBD @}}.
31060 @subheading The @code{-var-evaluate-expression} Command
31061 @findex -var-evaluate-expression
31063 @subsubheading Synopsis
31066 -var-evaluate-expression [-f @var{format-spec}] @var{name}
31069 Evaluates the expression that is represented by the specified variable
31070 object and returns its value as a string. The format of the string
31071 can be specified with the @samp{-f} option. The possible values of
31072 this option are the same as for @code{-var-set-format}
31073 (@pxref{-var-set-format}). If the @samp{-f} option is not specified,
31074 the current display format will be used. The current display format
31075 can be changed using the @code{-var-set-format} command.
31081 Note that one must invoke @code{-var-list-children} for a variable
31082 before the value of a child variable can be evaluated.
31084 @subheading The @code{-var-assign} Command
31085 @findex -var-assign
31087 @subsubheading Synopsis
31090 -var-assign @var{name} @var{expression}
31093 Assigns the value of @var{expression} to the variable object specified
31094 by @var{name}. The object must be @samp{editable}. If the variable's
31095 value is altered by the assign, the variable will show up in any
31096 subsequent @code{-var-update} list.
31098 @subsubheading Example
31106 ^done,changelist=[@{name="var1",in_scope="true",type_changed="false"@}]
31110 @subheading The @code{-var-update} Command
31111 @findex -var-update
31113 @subsubheading Synopsis
31116 -var-update [@var{print-values}] @{@var{name} | "*"@}
31119 Reevaluate the expressions corresponding to the variable object
31120 @var{name} and all its direct and indirect children, and return the
31121 list of variable objects whose values have changed; @var{name} must
31122 be a root variable object. Here, ``changed'' means that the result of
31123 @code{-var-evaluate-expression} before and after the
31124 @code{-var-update} is different. If @samp{*} is used as the variable
31125 object names, all existing variable objects are updated, except
31126 for frozen ones (@pxref{-var-set-frozen}). The option
31127 @var{print-values} determines whether both names and values, or just
31128 names are printed. The possible values of this option are the same
31129 as for @code{-var-list-children} (@pxref{-var-list-children}). It is
31130 recommended to use the @samp{--all-values} option, to reduce the
31131 number of MI commands needed on each program stop.
31133 With the @samp{*} parameter, if a variable object is bound to a
31134 currently running thread, it will not be updated, without any
31137 If @code{-var-set-update-range} was previously used on a varobj, then
31138 only the selected range of children will be reported.
31140 @code{-var-update} reports all the changed varobjs in a tuple named
31143 Each item in the change list is itself a tuple holding:
31147 The name of the varobj.
31150 If values were requested for this update, then this field will be
31151 present and will hold the value of the varobj.
31154 @anchor{-var-update}
31155 This field is a string which may take one of three values:
31159 The variable object's current value is valid.
31162 The variable object does not currently hold a valid value but it may
31163 hold one in the future if its associated expression comes back into
31167 The variable object no longer holds a valid value.
31168 This can occur when the executable file being debugged has changed,
31169 either through recompilation or by using the @value{GDBN} @code{file}
31170 command. The front end should normally choose to delete these variable
31174 In the future new values may be added to this list so the front should
31175 be prepared for this possibility. @xref{GDB/MI Development and Front Ends, ,@sc{GDB/MI} Development and Front Ends}.
31178 This is only present if the varobj is still valid. If the type
31179 changed, then this will be the string @samp{true}; otherwise it will
31182 When a varobj's type changes, its children are also likely to have
31183 become incorrect. Therefore, the varobj's children are automatically
31184 deleted when this attribute is @samp{true}. Also, the varobj's update
31185 range, when set using the @code{-var-set-update-range} command, is
31189 If the varobj's type changed, then this field will be present and will
31192 @item new_num_children
31193 For a dynamic varobj, if the number of children changed, or if the
31194 type changed, this will be the new number of children.
31196 The @samp{numchild} field in other varobj responses is generally not
31197 valid for a dynamic varobj -- it will show the number of children that
31198 @value{GDBN} knows about, but because dynamic varobjs lazily
31199 instantiate their children, this will not reflect the number of
31200 children which may be available.
31202 The @samp{new_num_children} attribute only reports changes to the
31203 number of children known by @value{GDBN}. This is the only way to
31204 detect whether an update has removed children (which necessarily can
31205 only happen at the end of the update range).
31208 The display hint, if any.
31211 This is an integer value, which will be 1 if there are more children
31212 available outside the varobj's update range.
31215 This attribute will be present and have the value @samp{1} if the
31216 varobj is a dynamic varobj. If the varobj is not a dynamic varobj,
31217 then this attribute will not be present.
31220 If new children were added to a dynamic varobj within the selected
31221 update range (as set by @code{-var-set-update-range}), then they will
31222 be listed in this attribute.
31225 @subsubheading Example
31232 -var-update --all-values var1
31233 ^done,changelist=[@{name="var1",value="3",in_scope="true",
31234 type_changed="false"@}]
31238 @subheading The @code{-var-set-frozen} Command
31239 @findex -var-set-frozen
31240 @anchor{-var-set-frozen}
31242 @subsubheading Synopsis
31245 -var-set-frozen @var{name} @var{flag}
31248 Set the frozenness flag on the variable object @var{name}. The
31249 @var{flag} parameter should be either @samp{1} to make the variable
31250 frozen or @samp{0} to make it unfrozen. If a variable object is
31251 frozen, then neither itself, nor any of its children, are
31252 implicitly updated by @code{-var-update} of
31253 a parent variable or by @code{-var-update *}. Only
31254 @code{-var-update} of the variable itself will update its value and
31255 values of its children. After a variable object is unfrozen, it is
31256 implicitly updated by all subsequent @code{-var-update} operations.
31257 Unfreezing a variable does not update it, only subsequent
31258 @code{-var-update} does.
31260 @subsubheading Example
31264 -var-set-frozen V 1
31269 @subheading The @code{-var-set-update-range} command
31270 @findex -var-set-update-range
31271 @anchor{-var-set-update-range}
31273 @subsubheading Synopsis
31276 -var-set-update-range @var{name} @var{from} @var{to}
31279 Set the range of children to be returned by future invocations of
31280 @code{-var-update}.
31282 @var{from} and @var{to} indicate the range of children to report. If
31283 @var{from} or @var{to} is less than zero, the range is reset and all
31284 children will be reported. Otherwise, children starting at @var{from}
31285 (zero-based) and up to and excluding @var{to} will be reported.
31287 @subsubheading Example
31291 -var-set-update-range V 1 2
31295 @subheading The @code{-var-set-visualizer} command
31296 @findex -var-set-visualizer
31297 @anchor{-var-set-visualizer}
31299 @subsubheading Synopsis
31302 -var-set-visualizer @var{name} @var{visualizer}
31305 Set a visualizer for the variable object @var{name}.
31307 @var{visualizer} is the visualizer to use. The special value
31308 @samp{None} means to disable any visualizer in use.
31310 If not @samp{None}, @var{visualizer} must be a Python expression.
31311 This expression must evaluate to a callable object which accepts a
31312 single argument. @value{GDBN} will call this object with the value of
31313 the varobj @var{name} as an argument (this is done so that the same
31314 Python pretty-printing code can be used for both the CLI and MI).
31315 When called, this object must return an object which conforms to the
31316 pretty-printing interface (@pxref{Pretty Printing API}).
31318 The pre-defined function @code{gdb.default_visualizer} may be used to
31319 select a visualizer by following the built-in process
31320 (@pxref{Selecting Pretty-Printers}). This is done automatically when
31321 a varobj is created, and so ordinarily is not needed.
31323 This feature is only available if Python support is enabled. The MI
31324 command @code{-list-features} (@pxref{GDB/MI Miscellaneous Commands})
31325 can be used to check this.
31327 @subsubheading Example
31329 Resetting the visualizer:
31333 -var-set-visualizer V None
31337 Reselecting the default (type-based) visualizer:
31341 -var-set-visualizer V gdb.default_visualizer
31345 Suppose @code{SomeClass} is a visualizer class. A lambda expression
31346 can be used to instantiate this class for a varobj:
31350 -var-set-visualizer V "lambda val: SomeClass()"
31354 @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
31355 @node GDB/MI Data Manipulation
31356 @section @sc{gdb/mi} Data Manipulation
31358 @cindex data manipulation, in @sc{gdb/mi}
31359 @cindex @sc{gdb/mi}, data manipulation
31360 This section describes the @sc{gdb/mi} commands that manipulate data:
31361 examine memory and registers, evaluate expressions, etc.
31363 @c REMOVED FROM THE INTERFACE.
31364 @c @subheading -data-assign
31365 @c Change the value of a program variable. Plenty of side effects.
31366 @c @subsubheading GDB Command
31368 @c @subsubheading Example
31371 @subheading The @code{-data-disassemble} Command
31372 @findex -data-disassemble
31374 @subsubheading Synopsis
31378 [ -s @var{start-addr} -e @var{end-addr} ]
31379 | [ -f @var{filename} -l @var{linenum} [ -n @var{lines} ] ]
31387 @item @var{start-addr}
31388 is the beginning address (or @code{$pc})
31389 @item @var{end-addr}
31391 @item @var{filename}
31392 is the name of the file to disassemble
31393 @item @var{linenum}
31394 is the line number to disassemble around
31396 is the number of disassembly lines to be produced. If it is -1,
31397 the whole function will be disassembled, in case no @var{end-addr} is
31398 specified. If @var{end-addr} is specified as a non-zero value, and
31399 @var{lines} is lower than the number of disassembly lines between
31400 @var{start-addr} and @var{end-addr}, only @var{lines} lines are
31401 displayed; if @var{lines} is higher than the number of lines between
31402 @var{start-addr} and @var{end-addr}, only the lines up to @var{end-addr}
31405 is either 0 (meaning only disassembly), 1 (meaning mixed source and
31406 disassembly), 2 (meaning disassembly with raw opcodes), or 3 (meaning
31407 mixed source and disassembly with raw opcodes).
31410 @subsubheading Result
31412 The result of the @code{-data-disassemble} command will be a list named
31413 @samp{asm_insns}, the contents of this list depend on the @var{mode}
31414 used with the @code{-data-disassemble} command.
31416 For modes 0 and 2 the @samp{asm_insns} list contains tuples with the
31421 The address at which this instruction was disassembled.
31424 The name of the function this instruction is within.
31427 The decimal offset in bytes from the start of @samp{func-name}.
31430 The text disassembly for this @samp{address}.
31433 This field is only present for mode 2. This contains the raw opcode
31434 bytes for the @samp{inst} field.
31438 For modes 1 and 3 the @samp{asm_insns} list contains tuples named
31439 @samp{src_and_asm_line}, each of which has the following fields:
31443 The line number within @samp{file}.
31446 The file name from the compilation unit. This might be an absolute
31447 file name or a relative file name depending on the compile command
31451 Absolute file name of @samp{file}. It is converted to a canonical form
31452 using the source file search path
31453 (@pxref{Source Path, ,Specifying Source Directories})
31454 and after resolving all the symbolic links.
31456 If the source file is not found this field will contain the path as
31457 present in the debug information.
31459 @item line_asm_insn
31460 This is a list of tuples containing the disassembly for @samp{line} in
31461 @samp{file}. The fields of each tuple are the same as for
31462 @code{-data-disassemble} in @var{mode} 0 and 2, so @samp{address},
31463 @samp{func-name}, @samp{offset}, @samp{inst}, and optionally
31468 Note that whatever included in the @samp{inst} field, is not
31469 manipulated directly by @sc{gdb/mi}, i.e., it is not possible to
31472 @subsubheading @value{GDBN} Command
31474 The corresponding @value{GDBN} command is @samp{disassemble}.
31476 @subsubheading Example
31478 Disassemble from the current value of @code{$pc} to @code{$pc + 20}:
31482 -data-disassemble -s $pc -e "$pc + 20" -- 0
31485 @{address="0x000107c0",func-name="main",offset="4",
31486 inst="mov 2, %o0"@},
31487 @{address="0x000107c4",func-name="main",offset="8",
31488 inst="sethi %hi(0x11800), %o2"@},
31489 @{address="0x000107c8",func-name="main",offset="12",
31490 inst="or %o2, 0x140, %o1\t! 0x11940 <_lib_version+8>"@},
31491 @{address="0x000107cc",func-name="main",offset="16",
31492 inst="sethi %hi(0x11800), %o2"@},
31493 @{address="0x000107d0",func-name="main",offset="20",
31494 inst="or %o2, 0x168, %o4\t! 0x11968 <_lib_version+48>"@}]
31498 Disassemble the whole @code{main} function. Line 32 is part of
31502 -data-disassemble -f basics.c -l 32 -- 0
31504 @{address="0x000107bc",func-name="main",offset="0",
31505 inst="save %sp, -112, %sp"@},
31506 @{address="0x000107c0",func-name="main",offset="4",
31507 inst="mov 2, %o0"@},
31508 @{address="0x000107c4",func-name="main",offset="8",
31509 inst="sethi %hi(0x11800), %o2"@},
31511 @{address="0x0001081c",func-name="main",offset="96",inst="ret "@},
31512 @{address="0x00010820",func-name="main",offset="100",inst="restore "@}]
31516 Disassemble 3 instructions from the start of @code{main}:
31520 -data-disassemble -f basics.c -l 32 -n 3 -- 0
31522 @{address="0x000107bc",func-name="main",offset="0",
31523 inst="save %sp, -112, %sp"@},
31524 @{address="0x000107c0",func-name="main",offset="4",
31525 inst="mov 2, %o0"@},
31526 @{address="0x000107c4",func-name="main",offset="8",
31527 inst="sethi %hi(0x11800), %o2"@}]
31531 Disassemble 3 instructions from the start of @code{main} in mixed mode:
31535 -data-disassemble -f basics.c -l 32 -n 3 -- 1
31537 src_and_asm_line=@{line="31",
31538 file="../../../src/gdb/testsuite/gdb.mi/basics.c",
31539 fullname="/absolute/path/to/src/gdb/testsuite/gdb.mi/basics.c",
31540 line_asm_insn=[@{address="0x000107bc",
31541 func-name="main",offset="0",inst="save %sp, -112, %sp"@}]@},
31542 src_and_asm_line=@{line="32",
31543 file="../../../src/gdb/testsuite/gdb.mi/basics.c",
31544 fullname="/absolute/path/to/src/gdb/testsuite/gdb.mi/basics.c",
31545 line_asm_insn=[@{address="0x000107c0",
31546 func-name="main",offset="4",inst="mov 2, %o0"@},
31547 @{address="0x000107c4",func-name="main",offset="8",
31548 inst="sethi %hi(0x11800), %o2"@}]@}]
31553 @subheading The @code{-data-evaluate-expression} Command
31554 @findex -data-evaluate-expression
31556 @subsubheading Synopsis
31559 -data-evaluate-expression @var{expr}
31562 Evaluate @var{expr} as an expression. The expression could contain an
31563 inferior function call. The function call will execute synchronously.
31564 If the expression contains spaces, it must be enclosed in double quotes.
31566 @subsubheading @value{GDBN} Command
31568 The corresponding @value{GDBN} commands are @samp{print}, @samp{output}, and
31569 @samp{call}. In @code{gdbtk} only, there's a corresponding
31570 @samp{gdb_eval} command.
31572 @subsubheading Example
31574 In the following example, the numbers that precede the commands are the
31575 @dfn{tokens} described in @ref{GDB/MI Command Syntax, ,@sc{gdb/mi}
31576 Command Syntax}. Notice how @sc{gdb/mi} returns the same tokens in its
31580 211-data-evaluate-expression A
31583 311-data-evaluate-expression &A
31584 311^done,value="0xefffeb7c"
31586 411-data-evaluate-expression A+3
31589 511-data-evaluate-expression "A + 3"
31595 @subheading The @code{-data-list-changed-registers} Command
31596 @findex -data-list-changed-registers
31598 @subsubheading Synopsis
31601 -data-list-changed-registers
31604 Display a list of the registers that have changed.
31606 @subsubheading @value{GDBN} Command
31608 @value{GDBN} doesn't have a direct analog for this command; @code{gdbtk}
31609 has the corresponding command @samp{gdb_changed_register_list}.
31611 @subsubheading Example
31613 On a PPC MBX board:
31621 *stopped,reason="breakpoint-hit",disp="keep",bkptno="1",frame=@{
31622 func="main",args=[],file="try.c",fullname="/home/foo/bar/try.c",
31625 -data-list-changed-registers
31626 ^done,changed-registers=["0","1","2","4","5","6","7","8","9",
31627 "10","11","13","14","15","16","17","18","19","20","21","22","23",
31628 "24","25","26","27","28","30","31","64","65","66","67","69"]
31633 @subheading The @code{-data-list-register-names} Command
31634 @findex -data-list-register-names
31636 @subsubheading Synopsis
31639 -data-list-register-names [ ( @var{regno} )+ ]
31642 Show a list of register names for the current target. If no arguments
31643 are given, it shows a list of the names of all the registers. If
31644 integer numbers are given as arguments, it will print a list of the
31645 names of the registers corresponding to the arguments. To ensure
31646 consistency between a register name and its number, the output list may
31647 include empty register names.
31649 @subsubheading @value{GDBN} Command
31651 @value{GDBN} does not have a command which corresponds to
31652 @samp{-data-list-register-names}. In @code{gdbtk} there is a
31653 corresponding command @samp{gdb_regnames}.
31655 @subsubheading Example
31657 For the PPC MBX board:
31660 -data-list-register-names
31661 ^done,register-names=["r0","r1","r2","r3","r4","r5","r6","r7",
31662 "r8","r9","r10","r11","r12","r13","r14","r15","r16","r17","r18",
31663 "r19","r20","r21","r22","r23","r24","r25","r26","r27","r28","r29",
31664 "r30","r31","f0","f1","f2","f3","f4","f5","f6","f7","f8","f9",
31665 "f10","f11","f12","f13","f14","f15","f16","f17","f18","f19","f20",
31666 "f21","f22","f23","f24","f25","f26","f27","f28","f29","f30","f31",
31667 "", "pc","ps","cr","lr","ctr","xer"]
31669 -data-list-register-names 1 2 3
31670 ^done,register-names=["r1","r2","r3"]
31674 @subheading The @code{-data-list-register-values} Command
31675 @findex -data-list-register-values
31677 @subsubheading Synopsis
31680 -data-list-register-values @var{fmt} [ ( @var{regno} )*]
31683 Display the registers' contents. @var{fmt} is the format according to
31684 which the registers' contents are to be returned, followed by an optional
31685 list of numbers specifying the registers to display. A missing list of
31686 numbers indicates that the contents of all the registers must be returned.
31688 Allowed formats for @var{fmt} are:
31705 @subsubheading @value{GDBN} Command
31707 The corresponding @value{GDBN} commands are @samp{info reg}, @samp{info
31708 all-reg}, and (in @code{gdbtk}) @samp{gdb_fetch_registers}.
31710 @subsubheading Example
31712 For a PPC MBX board (note: line breaks are for readability only, they
31713 don't appear in the actual output):
31717 -data-list-register-values r 64 65
31718 ^done,register-values=[@{number="64",value="0xfe00a300"@},
31719 @{number="65",value="0x00029002"@}]
31721 -data-list-register-values x
31722 ^done,register-values=[@{number="0",value="0xfe0043c8"@},
31723 @{number="1",value="0x3fff88"@},@{number="2",value="0xfffffffe"@},
31724 @{number="3",value="0x0"@},@{number="4",value="0xa"@},
31725 @{number="5",value="0x3fff68"@},@{number="6",value="0x3fff58"@},
31726 @{number="7",value="0xfe011e98"@},@{number="8",value="0x2"@},
31727 @{number="9",value="0xfa202820"@},@{number="10",value="0xfa202808"@},
31728 @{number="11",value="0x1"@},@{number="12",value="0x0"@},
31729 @{number="13",value="0x4544"@},@{number="14",value="0xffdfffff"@},
31730 @{number="15",value="0xffffffff"@},@{number="16",value="0xfffffeff"@},
31731 @{number="17",value="0xefffffed"@},@{number="18",value="0xfffffffe"@},
31732 @{number="19",value="0xffffffff"@},@{number="20",value="0xffffffff"@},
31733 @{number="21",value="0xffffffff"@},@{number="22",value="0xfffffff7"@},
31734 @{number="23",value="0xffffffff"@},@{number="24",value="0xffffffff"@},
31735 @{number="25",value="0xffffffff"@},@{number="26",value="0xfffffffb"@},
31736 @{number="27",value="0xffffffff"@},@{number="28",value="0xf7bfffff"@},
31737 @{number="29",value="0x0"@},@{number="30",value="0xfe010000"@},
31738 @{number="31",value="0x0"@},@{number="32",value="0x0"@},
31739 @{number="33",value="0x0"@},@{number="34",value="0x0"@},
31740 @{number="35",value="0x0"@},@{number="36",value="0x0"@},
31741 @{number="37",value="0x0"@},@{number="38",value="0x0"@},
31742 @{number="39",value="0x0"@},@{number="40",value="0x0"@},
31743 @{number="41",value="0x0"@},@{number="42",value="0x0"@},
31744 @{number="43",value="0x0"@},@{number="44",value="0x0"@},
31745 @{number="45",value="0x0"@},@{number="46",value="0x0"@},
31746 @{number="47",value="0x0"@},@{number="48",value="0x0"@},
31747 @{number="49",value="0x0"@},@{number="50",value="0x0"@},
31748 @{number="51",value="0x0"@},@{number="52",value="0x0"@},
31749 @{number="53",value="0x0"@},@{number="54",value="0x0"@},
31750 @{number="55",value="0x0"@},@{number="56",value="0x0"@},
31751 @{number="57",value="0x0"@},@{number="58",value="0x0"@},
31752 @{number="59",value="0x0"@},@{number="60",value="0x0"@},
31753 @{number="61",value="0x0"@},@{number="62",value="0x0"@},
31754 @{number="63",value="0x0"@},@{number="64",value="0xfe00a300"@},
31755 @{number="65",value="0x29002"@},@{number="66",value="0x202f04b5"@},
31756 @{number="67",value="0xfe0043b0"@},@{number="68",value="0xfe00b3e4"@},
31757 @{number="69",value="0x20002b03"@}]
31762 @subheading The @code{-data-read-memory} Command
31763 @findex -data-read-memory
31765 This command is deprecated, use @code{-data-read-memory-bytes} instead.
31767 @subsubheading Synopsis
31770 -data-read-memory [ -o @var{byte-offset} ]
31771 @var{address} @var{word-format} @var{word-size}
31772 @var{nr-rows} @var{nr-cols} [ @var{aschar} ]
31779 @item @var{address}
31780 An expression specifying the address of the first memory word to be
31781 read. Complex expressions containing embedded white space should be
31782 quoted using the C convention.
31784 @item @var{word-format}
31785 The format to be used to print the memory words. The notation is the
31786 same as for @value{GDBN}'s @code{print} command (@pxref{Output Formats,
31789 @item @var{word-size}
31790 The size of each memory word in bytes.
31792 @item @var{nr-rows}
31793 The number of rows in the output table.
31795 @item @var{nr-cols}
31796 The number of columns in the output table.
31799 If present, indicates that each row should include an @sc{ascii} dump. The
31800 value of @var{aschar} is used as a padding character when a byte is not a
31801 member of the printable @sc{ascii} character set (printable @sc{ascii}
31802 characters are those whose code is between 32 and 126, inclusively).
31804 @item @var{byte-offset}
31805 An offset to add to the @var{address} before fetching memory.
31808 This command displays memory contents as a table of @var{nr-rows} by
31809 @var{nr-cols} words, each word being @var{word-size} bytes. In total,
31810 @code{@var{nr-rows} * @var{nr-cols} * @var{word-size}} bytes are read
31811 (returned as @samp{total-bytes}). Should less than the requested number
31812 of bytes be returned by the target, the missing words are identified
31813 using @samp{N/A}. The number of bytes read from the target is returned
31814 in @samp{nr-bytes} and the starting address used to read memory in
31817 The address of the next/previous row or page is available in
31818 @samp{next-row} and @samp{prev-row}, @samp{next-page} and
31821 @subsubheading @value{GDBN} Command
31823 The corresponding @value{GDBN} command is @samp{x}. @code{gdbtk} has
31824 @samp{gdb_get_mem} memory read command.
31826 @subsubheading Example
31828 Read six bytes of memory starting at @code{bytes+6} but then offset by
31829 @code{-6} bytes. Format as three rows of two columns. One byte per
31830 word. Display each word in hex.
31834 9-data-read-memory -o -6 -- bytes+6 x 1 3 2
31835 9^done,addr="0x00001390",nr-bytes="6",total-bytes="6",
31836 next-row="0x00001396",prev-row="0x0000138e",next-page="0x00001396",
31837 prev-page="0x0000138a",memory=[
31838 @{addr="0x00001390",data=["0x00","0x01"]@},
31839 @{addr="0x00001392",data=["0x02","0x03"]@},
31840 @{addr="0x00001394",data=["0x04","0x05"]@}]
31844 Read two bytes of memory starting at address @code{shorts + 64} and
31845 display as a single word formatted in decimal.
31849 5-data-read-memory shorts+64 d 2 1 1
31850 5^done,addr="0x00001510",nr-bytes="2",total-bytes="2",
31851 next-row="0x00001512",prev-row="0x0000150e",
31852 next-page="0x00001512",prev-page="0x0000150e",memory=[
31853 @{addr="0x00001510",data=["128"]@}]
31857 Read thirty two bytes of memory starting at @code{bytes+16} and format
31858 as eight rows of four columns. Include a string encoding with @samp{x}
31859 used as the non-printable character.
31863 4-data-read-memory bytes+16 x 1 8 4 x
31864 4^done,addr="0x000013a0",nr-bytes="32",total-bytes="32",
31865 next-row="0x000013c0",prev-row="0x0000139c",
31866 next-page="0x000013c0",prev-page="0x00001380",memory=[
31867 @{addr="0x000013a0",data=["0x10","0x11","0x12","0x13"],ascii="xxxx"@},
31868 @{addr="0x000013a4",data=["0x14","0x15","0x16","0x17"],ascii="xxxx"@},
31869 @{addr="0x000013a8",data=["0x18","0x19","0x1a","0x1b"],ascii="xxxx"@},
31870 @{addr="0x000013ac",data=["0x1c","0x1d","0x1e","0x1f"],ascii="xxxx"@},
31871 @{addr="0x000013b0",data=["0x20","0x21","0x22","0x23"],ascii=" !\"#"@},
31872 @{addr="0x000013b4",data=["0x24","0x25","0x26","0x27"],ascii="$%&'"@},
31873 @{addr="0x000013b8",data=["0x28","0x29","0x2a","0x2b"],ascii="()*+"@},
31874 @{addr="0x000013bc",data=["0x2c","0x2d","0x2e","0x2f"],ascii=",-./"@}]
31878 @subheading The @code{-data-read-memory-bytes} Command
31879 @findex -data-read-memory-bytes
31881 @subsubheading Synopsis
31884 -data-read-memory-bytes [ -o @var{byte-offset} ]
31885 @var{address} @var{count}
31892 @item @var{address}
31893 An expression specifying the address of the first memory word to be
31894 read. Complex expressions containing embedded white space should be
31895 quoted using the C convention.
31898 The number of bytes to read. This should be an integer literal.
31900 @item @var{byte-offset}
31901 The offsets in bytes relative to @var{address} at which to start
31902 reading. This should be an integer literal. This option is provided
31903 so that a frontend is not required to first evaluate address and then
31904 perform address arithmetics itself.
31908 This command attempts to read all accessible memory regions in the
31909 specified range. First, all regions marked as unreadable in the memory
31910 map (if one is defined) will be skipped. @xref{Memory Region
31911 Attributes}. Second, @value{GDBN} will attempt to read the remaining
31912 regions. For each one, if reading full region results in an errors,
31913 @value{GDBN} will try to read a subset of the region.
31915 In general, every single byte in the region may be readable or not,
31916 and the only way to read every readable byte is to try a read at
31917 every address, which is not practical. Therefore, @value{GDBN} will
31918 attempt to read all accessible bytes at either beginning or the end
31919 of the region, using a binary division scheme. This heuristic works
31920 well for reading accross a memory map boundary. Note that if a region
31921 has a readable range that is neither at the beginning or the end,
31922 @value{GDBN} will not read it.
31924 The result record (@pxref{GDB/MI Result Records}) that is output of
31925 the command includes a field named @samp{memory} whose content is a
31926 list of tuples. Each tuple represent a successfully read memory block
31927 and has the following fields:
31931 The start address of the memory block, as hexadecimal literal.
31934 The end address of the memory block, as hexadecimal literal.
31937 The offset of the memory block, as hexadecimal literal, relative to
31938 the start address passed to @code{-data-read-memory-bytes}.
31941 The contents of the memory block, in hex.
31947 @subsubheading @value{GDBN} Command
31949 The corresponding @value{GDBN} command is @samp{x}.
31951 @subsubheading Example
31955 -data-read-memory-bytes &a 10
31956 ^done,memory=[@{begin="0xbffff154",offset="0x00000000",
31958 contents="01000000020000000300"@}]
31963 @subheading The @code{-data-write-memory-bytes} Command
31964 @findex -data-write-memory-bytes
31966 @subsubheading Synopsis
31969 -data-write-memory-bytes @var{address} @var{contents}
31970 -data-write-memory-bytes @var{address} @var{contents} @r{[}@var{count}@r{]}
31977 @item @var{address}
31978 An expression specifying the address of the first memory word to be
31979 read. Complex expressions containing embedded white space should be
31980 quoted using the C convention.
31982 @item @var{contents}
31983 The hex-encoded bytes to write.
31986 Optional argument indicating the number of bytes to be written. If @var{count}
31987 is greater than @var{contents}' length, @value{GDBN} will repeatedly
31988 write @var{contents} until it fills @var{count} bytes.
31992 @subsubheading @value{GDBN} Command
31994 There's no corresponding @value{GDBN} command.
31996 @subsubheading Example
32000 -data-write-memory-bytes &a "aabbccdd"
32007 -data-write-memory-bytes &a "aabbccdd" 16e
32012 @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
32013 @node GDB/MI Tracepoint Commands
32014 @section @sc{gdb/mi} Tracepoint Commands
32016 The commands defined in this section implement MI support for
32017 tracepoints. For detailed introduction, see @ref{Tracepoints}.
32019 @subheading The @code{-trace-find} Command
32020 @findex -trace-find
32022 @subsubheading Synopsis
32025 -trace-find @var{mode} [@var{parameters}@dots{}]
32028 Find a trace frame using criteria defined by @var{mode} and
32029 @var{parameters}. The following table lists permissible
32030 modes and their parameters. For details of operation, see @ref{tfind}.
32035 No parameters are required. Stops examining trace frames.
32038 An integer is required as parameter. Selects tracepoint frame with
32041 @item tracepoint-number
32042 An integer is required as parameter. Finds next
32043 trace frame that corresponds to tracepoint with the specified number.
32046 An address is required as parameter. Finds
32047 next trace frame that corresponds to any tracepoint at the specified
32050 @item pc-inside-range
32051 Two addresses are required as parameters. Finds next trace
32052 frame that corresponds to a tracepoint at an address inside the
32053 specified range. Both bounds are considered to be inside the range.
32055 @item pc-outside-range
32056 Two addresses are required as parameters. Finds
32057 next trace frame that corresponds to a tracepoint at an address outside
32058 the specified range. Both bounds are considered to be inside the range.
32061 Line specification is required as parameter. @xref{Specify Location}.
32062 Finds next trace frame that corresponds to a tracepoint at
32063 the specified location.
32067 If @samp{none} was passed as @var{mode}, the response does not
32068 have fields. Otherwise, the response may have the following fields:
32072 This field has either @samp{0} or @samp{1} as the value, depending
32073 on whether a matching tracepoint was found.
32076 The index of the found traceframe. This field is present iff
32077 the @samp{found} field has value of @samp{1}.
32080 The index of the found tracepoint. This field is present iff
32081 the @samp{found} field has value of @samp{1}.
32084 The information about the frame corresponding to the found trace
32085 frame. This field is present only if a trace frame was found.
32086 @xref{GDB/MI Frame Information}, for description of this field.
32090 @subsubheading @value{GDBN} Command
32092 The corresponding @value{GDBN} command is @samp{tfind}.
32094 @subheading -trace-define-variable
32095 @findex -trace-define-variable
32097 @subsubheading Synopsis
32100 -trace-define-variable @var{name} [ @var{value} ]
32103 Create trace variable @var{name} if it does not exist. If
32104 @var{value} is specified, sets the initial value of the specified
32105 trace variable to that value. Note that the @var{name} should start
32106 with the @samp{$} character.
32108 @subsubheading @value{GDBN} Command
32110 The corresponding @value{GDBN} command is @samp{tvariable}.
32112 @subheading -trace-list-variables
32113 @findex -trace-list-variables
32115 @subsubheading Synopsis
32118 -trace-list-variables
32121 Return a table of all defined trace variables. Each element of the
32122 table has the following fields:
32126 The name of the trace variable. This field is always present.
32129 The initial value. This is a 64-bit signed integer. This
32130 field is always present.
32133 The value the trace variable has at the moment. This is a 64-bit
32134 signed integer. This field is absent iff current value is
32135 not defined, for example if the trace was never run, or is
32140 @subsubheading @value{GDBN} Command
32142 The corresponding @value{GDBN} command is @samp{tvariables}.
32144 @subsubheading Example
32148 -trace-list-variables
32149 ^done,trace-variables=@{nr_rows="1",nr_cols="3",
32150 hdr=[@{width="15",alignment="-1",col_name="name",colhdr="Name"@},
32151 @{width="11",alignment="-1",col_name="initial",colhdr="Initial"@},
32152 @{width="11",alignment="-1",col_name="current",colhdr="Current"@}],
32153 body=[variable=@{name="$trace_timestamp",initial="0"@}
32154 variable=@{name="$foo",initial="10",current="15"@}]@}
32158 @subheading -trace-save
32159 @findex -trace-save
32161 @subsubheading Synopsis
32164 -trace-save [-r ] @var{filename}
32167 Saves the collected trace data to @var{filename}. Without the
32168 @samp{-r} option, the data is downloaded from the target and saved
32169 in a local file. With the @samp{-r} option the target is asked
32170 to perform the save.
32172 @subsubheading @value{GDBN} Command
32174 The corresponding @value{GDBN} command is @samp{tsave}.
32177 @subheading -trace-start
32178 @findex -trace-start
32180 @subsubheading Synopsis
32186 Starts a tracing experiments. The result of this command does not
32189 @subsubheading @value{GDBN} Command
32191 The corresponding @value{GDBN} command is @samp{tstart}.
32193 @subheading -trace-status
32194 @findex -trace-status
32196 @subsubheading Synopsis
32202 Obtains the status of a tracing experiment. The result may include
32203 the following fields:
32208 May have a value of either @samp{0}, when no tracing operations are
32209 supported, @samp{1}, when all tracing operations are supported, or
32210 @samp{file} when examining trace file. In the latter case, examining
32211 of trace frame is possible but new tracing experiement cannot be
32212 started. This field is always present.
32215 May have a value of either @samp{0} or @samp{1} depending on whether
32216 tracing experiement is in progress on target. This field is present
32217 if @samp{supported} field is not @samp{0}.
32220 Report the reason why the tracing was stopped last time. This field
32221 may be absent iff tracing was never stopped on target yet. The
32222 value of @samp{request} means the tracing was stopped as result of
32223 the @code{-trace-stop} command. The value of @samp{overflow} means
32224 the tracing buffer is full. The value of @samp{disconnection} means
32225 tracing was automatically stopped when @value{GDBN} has disconnected.
32226 The value of @samp{passcount} means tracing was stopped when a
32227 tracepoint was passed a maximal number of times for that tracepoint.
32228 This field is present if @samp{supported} field is not @samp{0}.
32230 @item stopping-tracepoint
32231 The number of tracepoint whose passcount as exceeded. This field is
32232 present iff the @samp{stop-reason} field has the value of
32236 @itemx frames-created
32237 The @samp{frames} field is a count of the total number of trace frames
32238 in the trace buffer, while @samp{frames-created} is the total created
32239 during the run, including ones that were discarded, such as when a
32240 circular trace buffer filled up. Both fields are optional.
32244 These fields tell the current size of the tracing buffer and the
32245 remaining space. These fields are optional.
32248 The value of the circular trace buffer flag. @code{1} means that the
32249 trace buffer is circular and old trace frames will be discarded if
32250 necessary to make room, @code{0} means that the trace buffer is linear
32254 The value of the disconnected tracing flag. @code{1} means that
32255 tracing will continue after @value{GDBN} disconnects, @code{0} means
32256 that the trace run will stop.
32259 The filename of the trace file being examined. This field is
32260 optional, and only present when examining a trace file.
32264 @subsubheading @value{GDBN} Command
32266 The corresponding @value{GDBN} command is @samp{tstatus}.
32268 @subheading -trace-stop
32269 @findex -trace-stop
32271 @subsubheading Synopsis
32277 Stops a tracing experiment. The result of this command has the same
32278 fields as @code{-trace-status}, except that the @samp{supported} and
32279 @samp{running} fields are not output.
32281 @subsubheading @value{GDBN} Command
32283 The corresponding @value{GDBN} command is @samp{tstop}.
32286 @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
32287 @node GDB/MI Symbol Query
32288 @section @sc{gdb/mi} Symbol Query Commands
32292 @subheading The @code{-symbol-info-address} Command
32293 @findex -symbol-info-address
32295 @subsubheading Synopsis
32298 -symbol-info-address @var{symbol}
32301 Describe where @var{symbol} is stored.
32303 @subsubheading @value{GDBN} Command
32305 The corresponding @value{GDBN} command is @samp{info address}.
32307 @subsubheading Example
32311 @subheading The @code{-symbol-info-file} Command
32312 @findex -symbol-info-file
32314 @subsubheading Synopsis
32320 Show the file for the symbol.
32322 @subsubheading @value{GDBN} Command
32324 There's no equivalent @value{GDBN} command. @code{gdbtk} has
32325 @samp{gdb_find_file}.
32327 @subsubheading Example
32331 @subheading The @code{-symbol-info-function} Command
32332 @findex -symbol-info-function
32334 @subsubheading Synopsis
32337 -symbol-info-function
32340 Show which function the symbol lives in.
32342 @subsubheading @value{GDBN} Command
32344 @samp{gdb_get_function} in @code{gdbtk}.
32346 @subsubheading Example
32350 @subheading The @code{-symbol-info-line} Command
32351 @findex -symbol-info-line
32353 @subsubheading Synopsis
32359 Show the core addresses of the code for a source line.
32361 @subsubheading @value{GDBN} Command
32363 The corresponding @value{GDBN} command is @samp{info line}.
32364 @code{gdbtk} has the @samp{gdb_get_line} and @samp{gdb_get_file} commands.
32366 @subsubheading Example
32370 @subheading The @code{-symbol-info-symbol} Command
32371 @findex -symbol-info-symbol
32373 @subsubheading Synopsis
32376 -symbol-info-symbol @var{addr}
32379 Describe what symbol is at location @var{addr}.
32381 @subsubheading @value{GDBN} Command
32383 The corresponding @value{GDBN} command is @samp{info symbol}.
32385 @subsubheading Example
32389 @subheading The @code{-symbol-list-functions} Command
32390 @findex -symbol-list-functions
32392 @subsubheading Synopsis
32395 -symbol-list-functions
32398 List the functions in the executable.
32400 @subsubheading @value{GDBN} Command
32402 @samp{info functions} in @value{GDBN}, @samp{gdb_listfunc} and
32403 @samp{gdb_search} in @code{gdbtk}.
32405 @subsubheading Example
32410 @subheading The @code{-symbol-list-lines} Command
32411 @findex -symbol-list-lines
32413 @subsubheading Synopsis
32416 -symbol-list-lines @var{filename}
32419 Print the list of lines that contain code and their associated program
32420 addresses for the given source filename. The entries are sorted in
32421 ascending PC order.
32423 @subsubheading @value{GDBN} Command
32425 There is no corresponding @value{GDBN} command.
32427 @subsubheading Example
32430 -symbol-list-lines basics.c
32431 ^done,lines=[@{pc="0x08048554",line="7"@},@{pc="0x0804855a",line="8"@}]
32437 @subheading The @code{-symbol-list-types} Command
32438 @findex -symbol-list-types
32440 @subsubheading Synopsis
32446 List all the type names.
32448 @subsubheading @value{GDBN} Command
32450 The corresponding commands are @samp{info types} in @value{GDBN},
32451 @samp{gdb_search} in @code{gdbtk}.
32453 @subsubheading Example
32457 @subheading The @code{-symbol-list-variables} Command
32458 @findex -symbol-list-variables
32460 @subsubheading Synopsis
32463 -symbol-list-variables
32466 List all the global and static variable names.
32468 @subsubheading @value{GDBN} Command
32470 @samp{info variables} in @value{GDBN}, @samp{gdb_search} in @code{gdbtk}.
32472 @subsubheading Example
32476 @subheading The @code{-symbol-locate} Command
32477 @findex -symbol-locate
32479 @subsubheading Synopsis
32485 @subsubheading @value{GDBN} Command
32487 @samp{gdb_loc} in @code{gdbtk}.
32489 @subsubheading Example
32493 @subheading The @code{-symbol-type} Command
32494 @findex -symbol-type
32496 @subsubheading Synopsis
32499 -symbol-type @var{variable}
32502 Show type of @var{variable}.
32504 @subsubheading @value{GDBN} Command
32506 The corresponding @value{GDBN} command is @samp{ptype}, @code{gdbtk} has
32507 @samp{gdb_obj_variable}.
32509 @subsubheading Example
32514 @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
32515 @node GDB/MI File Commands
32516 @section @sc{gdb/mi} File Commands
32518 This section describes the GDB/MI commands to specify executable file names
32519 and to read in and obtain symbol table information.
32521 @subheading The @code{-file-exec-and-symbols} Command
32522 @findex -file-exec-and-symbols
32524 @subsubheading Synopsis
32527 -file-exec-and-symbols @var{file}
32530 Specify the executable file to be debugged. This file is the one from
32531 which the symbol table is also read. If no file is specified, the
32532 command clears the executable and symbol information. If breakpoints
32533 are set when using this command with no arguments, @value{GDBN} will produce
32534 error messages. Otherwise, no output is produced, except a completion
32537 @subsubheading @value{GDBN} Command
32539 The corresponding @value{GDBN} command is @samp{file}.
32541 @subsubheading Example
32545 -file-exec-and-symbols /kwikemart/marge/ezannoni/TRUNK/mbx/hello.mbx
32551 @subheading The @code{-file-exec-file} Command
32552 @findex -file-exec-file
32554 @subsubheading Synopsis
32557 -file-exec-file @var{file}
32560 Specify the executable file to be debugged. Unlike
32561 @samp{-file-exec-and-symbols}, the symbol table is @emph{not} read
32562 from this file. If used without argument, @value{GDBN} clears the information
32563 about the executable file. No output is produced, except a completion
32566 @subsubheading @value{GDBN} Command
32568 The corresponding @value{GDBN} command is @samp{exec-file}.
32570 @subsubheading Example
32574 -file-exec-file /kwikemart/marge/ezannoni/TRUNK/mbx/hello.mbx
32581 @subheading The @code{-file-list-exec-sections} Command
32582 @findex -file-list-exec-sections
32584 @subsubheading Synopsis
32587 -file-list-exec-sections
32590 List the sections of the current executable file.
32592 @subsubheading @value{GDBN} Command
32594 The @value{GDBN} command @samp{info file} shows, among the rest, the same
32595 information as this command. @code{gdbtk} has a corresponding command
32596 @samp{gdb_load_info}.
32598 @subsubheading Example
32603 @subheading The @code{-file-list-exec-source-file} Command
32604 @findex -file-list-exec-source-file
32606 @subsubheading Synopsis
32609 -file-list-exec-source-file
32612 List the line number, the current source file, and the absolute path
32613 to the current source file for the current executable. The macro
32614 information field has a value of @samp{1} or @samp{0} depending on
32615 whether or not the file includes preprocessor macro information.
32617 @subsubheading @value{GDBN} Command
32619 The @value{GDBN} equivalent is @samp{info source}
32621 @subsubheading Example
32625 123-file-list-exec-source-file
32626 123^done,line="1",file="foo.c",fullname="/home/bar/foo.c,macro-info="1"
32631 @subheading The @code{-file-list-exec-source-files} Command
32632 @findex -file-list-exec-source-files
32634 @subsubheading Synopsis
32637 -file-list-exec-source-files
32640 List the source files for the current executable.
32642 It will always output both the filename and fullname (absolute file
32643 name) of a source file.
32645 @subsubheading @value{GDBN} Command
32647 The @value{GDBN} equivalent is @samp{info sources}.
32648 @code{gdbtk} has an analogous command @samp{gdb_listfiles}.
32650 @subsubheading Example
32653 -file-list-exec-source-files
32655 @{file=foo.c,fullname=/home/foo.c@},
32656 @{file=/home/bar.c,fullname=/home/bar.c@},
32657 @{file=gdb_could_not_find_fullpath.c@}]
32662 @subheading The @code{-file-list-shared-libraries} Command
32663 @findex -file-list-shared-libraries
32665 @subsubheading Synopsis
32668 -file-list-shared-libraries
32671 List the shared libraries in the program.
32673 @subsubheading @value{GDBN} Command
32675 The corresponding @value{GDBN} command is @samp{info shared}.
32677 @subsubheading Example
32681 @subheading The @code{-file-list-symbol-files} Command
32682 @findex -file-list-symbol-files
32684 @subsubheading Synopsis
32687 -file-list-symbol-files
32692 @subsubheading @value{GDBN} Command
32694 The corresponding @value{GDBN} command is @samp{info file} (part of it).
32696 @subsubheading Example
32701 @subheading The @code{-file-symbol-file} Command
32702 @findex -file-symbol-file
32704 @subsubheading Synopsis
32707 -file-symbol-file @var{file}
32710 Read symbol table info from the specified @var{file} argument. When
32711 used without arguments, clears @value{GDBN}'s symbol table info. No output is
32712 produced, except for a completion notification.
32714 @subsubheading @value{GDBN} Command
32716 The corresponding @value{GDBN} command is @samp{symbol-file}.
32718 @subsubheading Example
32722 -file-symbol-file /kwikemart/marge/ezannoni/TRUNK/mbx/hello.mbx
32728 @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
32729 @node GDB/MI Memory Overlay Commands
32730 @section @sc{gdb/mi} Memory Overlay Commands
32732 The memory overlay commands are not implemented.
32734 @c @subheading -overlay-auto
32736 @c @subheading -overlay-list-mapping-state
32738 @c @subheading -overlay-list-overlays
32740 @c @subheading -overlay-map
32742 @c @subheading -overlay-off
32744 @c @subheading -overlay-on
32746 @c @subheading -overlay-unmap
32748 @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
32749 @node GDB/MI Signal Handling Commands
32750 @section @sc{gdb/mi} Signal Handling Commands
32752 Signal handling commands are not implemented.
32754 @c @subheading -signal-handle
32756 @c @subheading -signal-list-handle-actions
32758 @c @subheading -signal-list-signal-types
32762 @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
32763 @node GDB/MI Target Manipulation
32764 @section @sc{gdb/mi} Target Manipulation Commands
32767 @subheading The @code{-target-attach} Command
32768 @findex -target-attach
32770 @subsubheading Synopsis
32773 -target-attach @var{pid} | @var{gid} | @var{file}
32776 Attach to a process @var{pid} or a file @var{file} outside of
32777 @value{GDBN}, or a thread group @var{gid}. If attaching to a thread
32778 group, the id previously returned by
32779 @samp{-list-thread-groups --available} must be used.
32781 @subsubheading @value{GDBN} Command
32783 The corresponding @value{GDBN} command is @samp{attach}.
32785 @subsubheading Example
32789 =thread-created,id="1"
32790 *stopped,thread-id="1",frame=@{addr="0xb7f7e410",func="bar",args=[]@}
32796 @subheading The @code{-target-compare-sections} Command
32797 @findex -target-compare-sections
32799 @subsubheading Synopsis
32802 -target-compare-sections [ @var{section} ]
32805 Compare data of section @var{section} on target to the exec file.
32806 Without the argument, all sections are compared.
32808 @subsubheading @value{GDBN} Command
32810 The @value{GDBN} equivalent is @samp{compare-sections}.
32812 @subsubheading Example
32817 @subheading The @code{-target-detach} Command
32818 @findex -target-detach
32820 @subsubheading Synopsis
32823 -target-detach [ @var{pid} | @var{gid} ]
32826 Detach from the remote target which normally resumes its execution.
32827 If either @var{pid} or @var{gid} is specified, detaches from either
32828 the specified process, or specified thread group. There's no output.
32830 @subsubheading @value{GDBN} Command
32832 The corresponding @value{GDBN} command is @samp{detach}.
32834 @subsubheading Example
32844 @subheading The @code{-target-disconnect} Command
32845 @findex -target-disconnect
32847 @subsubheading Synopsis
32853 Disconnect from the remote target. There's no output and the target is
32854 generally not resumed.
32856 @subsubheading @value{GDBN} Command
32858 The corresponding @value{GDBN} command is @samp{disconnect}.
32860 @subsubheading Example
32870 @subheading The @code{-target-download} Command
32871 @findex -target-download
32873 @subsubheading Synopsis
32879 Loads the executable onto the remote target.
32880 It prints out an update message every half second, which includes the fields:
32884 The name of the section.
32886 The size of what has been sent so far for that section.
32888 The size of the section.
32890 The total size of what was sent so far (the current and the previous sections).
32892 The size of the overall executable to download.
32896 Each message is sent as status record (@pxref{GDB/MI Output Syntax, ,
32897 @sc{gdb/mi} Output Syntax}).
32899 In addition, it prints the name and size of the sections, as they are
32900 downloaded. These messages include the following fields:
32904 The name of the section.
32906 The size of the section.
32908 The size of the overall executable to download.
32912 At the end, a summary is printed.
32914 @subsubheading @value{GDBN} Command
32916 The corresponding @value{GDBN} command is @samp{load}.
32918 @subsubheading Example
32920 Note: each status message appears on a single line. Here the messages
32921 have been broken down so that they can fit onto a page.
32926 +download,@{section=".text",section-size="6668",total-size="9880"@}
32927 +download,@{section=".text",section-sent="512",section-size="6668",
32928 total-sent="512",total-size="9880"@}
32929 +download,@{section=".text",section-sent="1024",section-size="6668",
32930 total-sent="1024",total-size="9880"@}
32931 +download,@{section=".text",section-sent="1536",section-size="6668",
32932 total-sent="1536",total-size="9880"@}
32933 +download,@{section=".text",section-sent="2048",section-size="6668",
32934 total-sent="2048",total-size="9880"@}
32935 +download,@{section=".text",section-sent="2560",section-size="6668",
32936 total-sent="2560",total-size="9880"@}
32937 +download,@{section=".text",section-sent="3072",section-size="6668",
32938 total-sent="3072",total-size="9880"@}
32939 +download,@{section=".text",section-sent="3584",section-size="6668",
32940 total-sent="3584",total-size="9880"@}
32941 +download,@{section=".text",section-sent="4096",section-size="6668",
32942 total-sent="4096",total-size="9880"@}
32943 +download,@{section=".text",section-sent="4608",section-size="6668",
32944 total-sent="4608",total-size="9880"@}
32945 +download,@{section=".text",section-sent="5120",section-size="6668",
32946 total-sent="5120",total-size="9880"@}
32947 +download,@{section=".text",section-sent="5632",section-size="6668",
32948 total-sent="5632",total-size="9880"@}
32949 +download,@{section=".text",section-sent="6144",section-size="6668",
32950 total-sent="6144",total-size="9880"@}
32951 +download,@{section=".text",section-sent="6656",section-size="6668",
32952 total-sent="6656",total-size="9880"@}
32953 +download,@{section=".init",section-size="28",total-size="9880"@}
32954 +download,@{section=".fini",section-size="28",total-size="9880"@}
32955 +download,@{section=".data",section-size="3156",total-size="9880"@}
32956 +download,@{section=".data",section-sent="512",section-size="3156",
32957 total-sent="7236",total-size="9880"@}
32958 +download,@{section=".data",section-sent="1024",section-size="3156",
32959 total-sent="7748",total-size="9880"@}
32960 +download,@{section=".data",section-sent="1536",section-size="3156",
32961 total-sent="8260",total-size="9880"@}
32962 +download,@{section=".data",section-sent="2048",section-size="3156",
32963 total-sent="8772",total-size="9880"@}
32964 +download,@{section=".data",section-sent="2560",section-size="3156",
32965 total-sent="9284",total-size="9880"@}
32966 +download,@{section=".data",section-sent="3072",section-size="3156",
32967 total-sent="9796",total-size="9880"@}
32968 ^done,address="0x10004",load-size="9880",transfer-rate="6586",
32975 @subheading The @code{-target-exec-status} Command
32976 @findex -target-exec-status
32978 @subsubheading Synopsis
32981 -target-exec-status
32984 Provide information on the state of the target (whether it is running or
32985 not, for instance).
32987 @subsubheading @value{GDBN} Command
32989 There's no equivalent @value{GDBN} command.
32991 @subsubheading Example
32995 @subheading The @code{-target-list-available-targets} Command
32996 @findex -target-list-available-targets
32998 @subsubheading Synopsis
33001 -target-list-available-targets
33004 List the possible targets to connect to.
33006 @subsubheading @value{GDBN} Command
33008 The corresponding @value{GDBN} command is @samp{help target}.
33010 @subsubheading Example
33014 @subheading The @code{-target-list-current-targets} Command
33015 @findex -target-list-current-targets
33017 @subsubheading Synopsis
33020 -target-list-current-targets
33023 Describe the current target.
33025 @subsubheading @value{GDBN} Command
33027 The corresponding information is printed by @samp{info file} (among
33030 @subsubheading Example
33034 @subheading The @code{-target-list-parameters} Command
33035 @findex -target-list-parameters
33037 @subsubheading Synopsis
33040 -target-list-parameters
33046 @subsubheading @value{GDBN} Command
33050 @subsubheading Example
33054 @subheading The @code{-target-select} Command
33055 @findex -target-select
33057 @subsubheading Synopsis
33060 -target-select @var{type} @var{parameters @dots{}}
33063 Connect @value{GDBN} to the remote target. This command takes two args:
33067 The type of target, for instance @samp{remote}, etc.
33068 @item @var{parameters}
33069 Device names, host names and the like. @xref{Target Commands, ,
33070 Commands for Managing Targets}, for more details.
33073 The output is a connection notification, followed by the address at
33074 which the target program is, in the following form:
33077 ^connected,addr="@var{address}",func="@var{function name}",
33078 args=[@var{arg list}]
33081 @subsubheading @value{GDBN} Command
33083 The corresponding @value{GDBN} command is @samp{target}.
33085 @subsubheading Example
33089 -target-select remote /dev/ttya
33090 ^connected,addr="0xfe00a300",func="??",args=[]
33094 @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
33095 @node GDB/MI File Transfer Commands
33096 @section @sc{gdb/mi} File Transfer Commands
33099 @subheading The @code{-target-file-put} Command
33100 @findex -target-file-put
33102 @subsubheading Synopsis
33105 -target-file-put @var{hostfile} @var{targetfile}
33108 Copy file @var{hostfile} from the host system (the machine running
33109 @value{GDBN}) to @var{targetfile} on the target system.
33111 @subsubheading @value{GDBN} Command
33113 The corresponding @value{GDBN} command is @samp{remote put}.
33115 @subsubheading Example
33119 -target-file-put localfile remotefile
33125 @subheading The @code{-target-file-get} Command
33126 @findex -target-file-get
33128 @subsubheading Synopsis
33131 -target-file-get @var{targetfile} @var{hostfile}
33134 Copy file @var{targetfile} from the target system to @var{hostfile}
33135 on the host system.
33137 @subsubheading @value{GDBN} Command
33139 The corresponding @value{GDBN} command is @samp{remote get}.
33141 @subsubheading Example
33145 -target-file-get remotefile localfile
33151 @subheading The @code{-target-file-delete} Command
33152 @findex -target-file-delete
33154 @subsubheading Synopsis
33157 -target-file-delete @var{targetfile}
33160 Delete @var{targetfile} from the target system.
33162 @subsubheading @value{GDBN} Command
33164 The corresponding @value{GDBN} command is @samp{remote delete}.
33166 @subsubheading Example
33170 -target-file-delete remotefile
33176 @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
33177 @node GDB/MI Miscellaneous Commands
33178 @section Miscellaneous @sc{gdb/mi} Commands
33180 @c @subheading -gdb-complete
33182 @subheading The @code{-gdb-exit} Command
33185 @subsubheading Synopsis
33191 Exit @value{GDBN} immediately.
33193 @subsubheading @value{GDBN} Command
33195 Approximately corresponds to @samp{quit}.
33197 @subsubheading Example
33207 @subheading The @code{-exec-abort} Command
33208 @findex -exec-abort
33210 @subsubheading Synopsis
33216 Kill the inferior running program.
33218 @subsubheading @value{GDBN} Command
33220 The corresponding @value{GDBN} command is @samp{kill}.
33222 @subsubheading Example
33227 @subheading The @code{-gdb-set} Command
33230 @subsubheading Synopsis
33236 Set an internal @value{GDBN} variable.
33237 @c IS THIS A DOLLAR VARIABLE? OR SOMETHING LIKE ANNOTATE ?????
33239 @subsubheading @value{GDBN} Command
33241 The corresponding @value{GDBN} command is @samp{set}.
33243 @subsubheading Example
33253 @subheading The @code{-gdb-show} Command
33256 @subsubheading Synopsis
33262 Show the current value of a @value{GDBN} variable.
33264 @subsubheading @value{GDBN} Command
33266 The corresponding @value{GDBN} command is @samp{show}.
33268 @subsubheading Example
33277 @c @subheading -gdb-source
33280 @subheading The @code{-gdb-version} Command
33281 @findex -gdb-version
33283 @subsubheading Synopsis
33289 Show version information for @value{GDBN}. Used mostly in testing.
33291 @subsubheading @value{GDBN} Command
33293 The @value{GDBN} equivalent is @samp{show version}. @value{GDBN} by
33294 default shows this information when you start an interactive session.
33296 @subsubheading Example
33298 @c This example modifies the actual output from GDB to avoid overfull
33304 ~Copyright 2000 Free Software Foundation, Inc.
33305 ~GDB is free software, covered by the GNU General Public License, and
33306 ~you are welcome to change it and/or distribute copies of it under
33307 ~ certain conditions.
33308 ~Type "show copying" to see the conditions.
33309 ~There is absolutely no warranty for GDB. Type "show warranty" for
33311 ~This GDB was configured as
33312 "--host=sparc-sun-solaris2.5.1 --target=ppc-eabi".
33317 @subheading The @code{-list-features} Command
33318 @findex -list-features
33320 Returns a list of particular features of the MI protocol that
33321 this version of gdb implements. A feature can be a command,
33322 or a new field in an output of some command, or even an
33323 important bugfix. While a frontend can sometimes detect presence
33324 of a feature at runtime, it is easier to perform detection at debugger
33327 The command returns a list of strings, with each string naming an
33328 available feature. Each returned string is just a name, it does not
33329 have any internal structure. The list of possible feature names
33335 (gdb) -list-features
33336 ^done,result=["feature1","feature2"]
33339 The current list of features is:
33342 @item frozen-varobjs
33343 Indicates support for the @code{-var-set-frozen} command, as well
33344 as possible presense of the @code{frozen} field in the output
33345 of @code{-varobj-create}.
33346 @item pending-breakpoints
33347 Indicates support for the @option{-f} option to the @code{-break-insert}
33350 Indicates Python scripting support, Python-based
33351 pretty-printing commands, and possible presence of the
33352 @samp{display_hint} field in the output of @code{-var-list-children}
33354 Indicates support for the @code{-thread-info} command.
33355 @item data-read-memory-bytes
33356 Indicates support for the @code{-data-read-memory-bytes} and the
33357 @code{-data-write-memory-bytes} commands.
33358 @item breakpoint-notifications
33359 Indicates that changes to breakpoints and breakpoints created via the
33360 CLI will be announced via async records.
33361 @item ada-task-info
33362 Indicates support for the @code{-ada-task-info} command.
33365 @subheading The @code{-list-target-features} Command
33366 @findex -list-target-features
33368 Returns a list of particular features that are supported by the
33369 target. Those features affect the permitted MI commands, but
33370 unlike the features reported by the @code{-list-features} command, the
33371 features depend on which target GDB is using at the moment. Whenever
33372 a target can change, due to commands such as @code{-target-select},
33373 @code{-target-attach} or @code{-exec-run}, the list of target features
33374 may change, and the frontend should obtain it again.
33378 (gdb) -list-features
33379 ^done,result=["async"]
33382 The current list of features is:
33386 Indicates that the target is capable of asynchronous command
33387 execution, which means that @value{GDBN} will accept further commands
33388 while the target is running.
33391 Indicates that the target is capable of reverse execution.
33392 @xref{Reverse Execution}, for more information.
33396 @subheading The @code{-list-thread-groups} Command
33397 @findex -list-thread-groups
33399 @subheading Synopsis
33402 -list-thread-groups [ --available ] [ --recurse 1 ] [ @var{group} ... ]
33405 Lists thread groups (@pxref{Thread groups}). When a single thread
33406 group is passed as the argument, lists the children of that group.
33407 When several thread group are passed, lists information about those
33408 thread groups. Without any parameters, lists information about all
33409 top-level thread groups.
33411 Normally, thread groups that are being debugged are reported.
33412 With the @samp{--available} option, @value{GDBN} reports thread groups
33413 available on the target.
33415 The output of this command may have either a @samp{threads} result or
33416 a @samp{groups} result. The @samp{thread} result has a list of tuples
33417 as value, with each tuple describing a thread (@pxref{GDB/MI Thread
33418 Information}). The @samp{groups} result has a list of tuples as value,
33419 each tuple describing a thread group. If top-level groups are
33420 requested (that is, no parameter is passed), or when several groups
33421 are passed, the output always has a @samp{groups} result. The format
33422 of the @samp{group} result is described below.
33424 To reduce the number of roundtrips it's possible to list thread groups
33425 together with their children, by passing the @samp{--recurse} option
33426 and the recursion depth. Presently, only recursion depth of 1 is
33427 permitted. If this option is present, then every reported thread group
33428 will also include its children, either as @samp{group} or
33429 @samp{threads} field.
33431 In general, any combination of option and parameters is permitted, with
33432 the following caveats:
33436 When a single thread group is passed, the output will typically
33437 be the @samp{threads} result. Because threads may not contain
33438 anything, the @samp{recurse} option will be ignored.
33441 When the @samp{--available} option is passed, limited information may
33442 be available. In particular, the list of threads of a process might
33443 be inaccessible. Further, specifying specific thread groups might
33444 not give any performance advantage over listing all thread groups.
33445 The frontend should assume that @samp{-list-thread-groups --available}
33446 is always an expensive operation and cache the results.
33450 The @samp{groups} result is a list of tuples, where each tuple may
33451 have the following fields:
33455 Identifier of the thread group. This field is always present.
33456 The identifier is an opaque string; frontends should not try to
33457 convert it to an integer, even though it might look like one.
33460 The type of the thread group. At present, only @samp{process} is a
33464 The target-specific process identifier. This field is only present
33465 for thread groups of type @samp{process} and only if the process exists.
33468 The number of children this thread group has. This field may be
33469 absent for an available thread group.
33472 This field has a list of tuples as value, each tuple describing a
33473 thread. It may be present if the @samp{--recurse} option is
33474 specified, and it's actually possible to obtain the threads.
33477 This field is a list of integers, each identifying a core that one
33478 thread of the group is running on. This field may be absent if
33479 such information is not available.
33482 The name of the executable file that corresponds to this thread group.
33483 The field is only present for thread groups of type @samp{process},
33484 and only if there is a corresponding executable file.
33488 @subheading Example
33492 -list-thread-groups
33493 ^done,groups=[@{id="17",type="process",pid="yyy",num_children="2"@}]
33494 -list-thread-groups 17
33495 ^done,threads=[@{id="2",target-id="Thread 0xb7e14b90 (LWP 21257)",
33496 frame=@{level="0",addr="0xffffe410",func="__kernel_vsyscall",args=[]@},state="running"@},
33497 @{id="1",target-id="Thread 0xb7e156b0 (LWP 21254)",
33498 frame=@{level="0",addr="0x0804891f",func="foo",args=[@{name="i",value="10"@}],
33499 file="/tmp/a.c",fullname="/tmp/a.c",line="158"@},state="running"@}]]
33500 -list-thread-groups --available
33501 ^done,groups=[@{id="17",type="process",pid="yyy",num_children="2",cores=[1,2]@}]
33502 -list-thread-groups --available --recurse 1
33503 ^done,groups=[@{id="17", types="process",pid="yyy",num_children="2",cores=[1,2],
33504 threads=[@{id="1",target-id="Thread 0xb7e14b90",cores=[1]@},
33505 @{id="2",target-id="Thread 0xb7e14b90",cores=[2]@}]@},..]
33506 -list-thread-groups --available --recurse 1 17 18
33507 ^done,groups=[@{id="17", types="process",pid="yyy",num_children="2",cores=[1,2],
33508 threads=[@{id="1",target-id="Thread 0xb7e14b90",cores=[1]@},
33509 @{id="2",target-id="Thread 0xb7e14b90",cores=[2]@}]@},...]
33512 @subheading The @code{-info-os} Command
33515 @subsubheading Synopsis
33518 -info-os [ @var{type} ]
33521 If no argument is supplied, the command returns a table of available
33522 operating-system-specific information types. If one of these types is
33523 supplied as an argument @var{type}, then the command returns a table
33524 of data of that type.
33526 The types of information available depend on the target operating
33529 @subsubheading @value{GDBN} Command
33531 The corresponding @value{GDBN} command is @samp{info os}.
33533 @subsubheading Example
33535 When run on a @sc{gnu}/Linux system, the output will look something
33541 ^done,OSDataTable=@{nr_rows="9",nr_cols="3",
33542 hdr=[@{width="10",alignment="-1",col_name="col0",colhdr="Type"@},
33543 @{width="10",alignment="-1",col_name="col1",colhdr="Description"@},
33544 @{width="10",alignment="-1",col_name="col2",colhdr="Title"@}],
33545 body=[item=@{col0="processes",col1="Listing of all processes",
33546 col2="Processes"@},
33547 item=@{col0="procgroups",col1="Listing of all process groups",
33548 col2="Process groups"@},
33549 item=@{col0="threads",col1="Listing of all threads",
33551 item=@{col0="files",col1="Listing of all file descriptors",
33552 col2="File descriptors"@},
33553 item=@{col0="sockets",col1="Listing of all internet-domain sockets",
33555 item=@{col0="shm",col1="Listing of all shared-memory regions",
33556 col2="Shared-memory regions"@},
33557 item=@{col0="semaphores",col1="Listing of all semaphores",
33558 col2="Semaphores"@},
33559 item=@{col0="msg",col1="Listing of all message queues",
33560 col2="Message queues"@},
33561 item=@{col0="modules",col1="Listing of all loaded kernel modules",
33562 col2="Kernel modules"@}]@}
33565 ^done,OSDataTable=@{nr_rows="190",nr_cols="4",
33566 hdr=[@{width="10",alignment="-1",col_name="col0",colhdr="pid"@},
33567 @{width="10",alignment="-1",col_name="col1",colhdr="user"@},
33568 @{width="10",alignment="-1",col_name="col2",colhdr="command"@},
33569 @{width="10",alignment="-1",col_name="col3",colhdr="cores"@}],
33570 body=[item=@{col0="1",col1="root",col2="/sbin/init",col3="0"@},
33571 item=@{col0="2",col1="root",col2="[kthreadd]",col3="1"@},
33572 item=@{col0="3",col1="root",col2="[ksoftirqd/0]",col3="0"@},
33574 item=@{col0="26446",col1="stan",col2="bash",col3="0"@},
33575 item=@{col0="28152",col1="stan",col2="bash",col3="1"@}]@}
33579 (Note that the MI output here includes a @code{"Title"} column that
33580 does not appear in command-line @code{info os}; this column is useful
33581 for MI clients that want to enumerate the types of data, such as in a
33582 popup menu, but is needless clutter on the command line, and
33583 @code{info os} omits it.)
33585 @subheading The @code{-add-inferior} Command
33586 @findex -add-inferior
33588 @subheading Synopsis
33594 Creates a new inferior (@pxref{Inferiors and Programs}). The created
33595 inferior is not associated with any executable. Such association may
33596 be established with the @samp{-file-exec-and-symbols} command
33597 (@pxref{GDB/MI File Commands}). The command response has a single
33598 field, @samp{thread-group}, whose value is the identifier of the
33599 thread group corresponding to the new inferior.
33601 @subheading Example
33606 ^done,thread-group="i3"
33609 @subheading The @code{-interpreter-exec} Command
33610 @findex -interpreter-exec
33612 @subheading Synopsis
33615 -interpreter-exec @var{interpreter} @var{command}
33617 @anchor{-interpreter-exec}
33619 Execute the specified @var{command} in the given @var{interpreter}.
33621 @subheading @value{GDBN} Command
33623 The corresponding @value{GDBN} command is @samp{interpreter-exec}.
33625 @subheading Example
33629 -interpreter-exec console "break main"
33630 &"During symbol reading, couldn't parse type; debugger out of date?.\n"
33631 &"During symbol reading, bad structure-type format.\n"
33632 ~"Breakpoint 1 at 0x8074fc6: file ../../src/gdb/main.c, line 743.\n"
33637 @subheading The @code{-inferior-tty-set} Command
33638 @findex -inferior-tty-set
33640 @subheading Synopsis
33643 -inferior-tty-set /dev/pts/1
33646 Set terminal for future runs of the program being debugged.
33648 @subheading @value{GDBN} Command
33650 The corresponding @value{GDBN} command is @samp{set inferior-tty} /dev/pts/1.
33652 @subheading Example
33656 -inferior-tty-set /dev/pts/1
33661 @subheading The @code{-inferior-tty-show} Command
33662 @findex -inferior-tty-show
33664 @subheading Synopsis
33670 Show terminal for future runs of program being debugged.
33672 @subheading @value{GDBN} Command
33674 The corresponding @value{GDBN} command is @samp{show inferior-tty}.
33676 @subheading Example
33680 -inferior-tty-set /dev/pts/1
33684 ^done,inferior_tty_terminal="/dev/pts/1"
33688 @subheading The @code{-enable-timings} Command
33689 @findex -enable-timings
33691 @subheading Synopsis
33694 -enable-timings [yes | no]
33697 Toggle the printing of the wallclock, user and system times for an MI
33698 command as a field in its output. This command is to help frontend
33699 developers optimize the performance of their code. No argument is
33700 equivalent to @samp{yes}.
33702 @subheading @value{GDBN} Command
33706 @subheading Example
33714 ^done,bkpt=@{number="1",type="breakpoint",disp="keep",enabled="y",
33715 addr="0x080484ed",func="main",file="myprog.c",
33716 fullname="/home/nickrob/myprog.c",line="73",thread-groups=["i1"],
33718 time=@{wallclock="0.05185",user="0.00800",system="0.00000"@}
33726 *stopped,reason="breakpoint-hit",disp="keep",bkptno="1",thread-id="0",
33727 frame=@{addr="0x080484ed",func="main",args=[@{name="argc",value="1"@},
33728 @{name="argv",value="0xbfb60364"@}],file="myprog.c",
33729 fullname="/home/nickrob/myprog.c",line="73"@}
33734 @chapter @value{GDBN} Annotations
33736 This chapter describes annotations in @value{GDBN}. Annotations were
33737 designed to interface @value{GDBN} to graphical user interfaces or other
33738 similar programs which want to interact with @value{GDBN} at a
33739 relatively high level.
33741 The annotation mechanism has largely been superseded by @sc{gdb/mi}
33745 This is Edition @value{EDITION}, @value{DATE}.
33749 * Annotations Overview:: What annotations are; the general syntax.
33750 * Server Prefix:: Issuing a command without affecting user state.
33751 * Prompting:: Annotations marking @value{GDBN}'s need for input.
33752 * Errors:: Annotations for error messages.
33753 * Invalidation:: Some annotations describe things now invalid.
33754 * Annotations for Running::
33755 Whether the program is running, how it stopped, etc.
33756 * Source Annotations:: Annotations describing source code.
33759 @node Annotations Overview
33760 @section What is an Annotation?
33761 @cindex annotations
33763 Annotations start with a newline character, two @samp{control-z}
33764 characters, and the name of the annotation. If there is no additional
33765 information associated with this annotation, the name of the annotation
33766 is followed immediately by a newline. If there is additional
33767 information, the name of the annotation is followed by a space, the
33768 additional information, and a newline. The additional information
33769 cannot contain newline characters.
33771 Any output not beginning with a newline and two @samp{control-z}
33772 characters denotes literal output from @value{GDBN}. Currently there is
33773 no need for @value{GDBN} to output a newline followed by two
33774 @samp{control-z} characters, but if there was such a need, the
33775 annotations could be extended with an @samp{escape} annotation which
33776 means those three characters as output.
33778 The annotation @var{level}, which is specified using the
33779 @option{--annotate} command line option (@pxref{Mode Options}), controls
33780 how much information @value{GDBN} prints together with its prompt,
33781 values of expressions, source lines, and other types of output. Level 0
33782 is for no annotations, level 1 is for use when @value{GDBN} is run as a
33783 subprocess of @sc{gnu} Emacs, level 3 is the maximum annotation suitable
33784 for programs that control @value{GDBN}, and level 2 annotations have
33785 been made obsolete (@pxref{Limitations, , Limitations of the Annotation
33786 Interface, annotate, GDB's Obsolete Annotations}).
33789 @kindex set annotate
33790 @item set annotate @var{level}
33791 The @value{GDBN} command @code{set annotate} sets the level of
33792 annotations to the specified @var{level}.
33794 @item show annotate
33795 @kindex show annotate
33796 Show the current annotation level.
33799 This chapter describes level 3 annotations.
33801 A simple example of starting up @value{GDBN} with annotations is:
33804 $ @kbd{gdb --annotate=3}
33806 Copyright 2003 Free Software Foundation, Inc.
33807 GDB is free software, covered by the GNU General Public License,
33808 and you are welcome to change it and/or distribute copies of it
33809 under certain conditions.
33810 Type "show copying" to see the conditions.
33811 There is absolutely no warranty for GDB. Type "show warranty"
33813 This GDB was configured as "i386-pc-linux-gnu"
33824 Here @samp{quit} is input to @value{GDBN}; the rest is output from
33825 @value{GDBN}. The three lines beginning @samp{^Z^Z} (where @samp{^Z}
33826 denotes a @samp{control-z} character) are annotations; the rest is
33827 output from @value{GDBN}.
33829 @node Server Prefix
33830 @section The Server Prefix
33831 @cindex server prefix
33833 If you prefix a command with @samp{server } then it will not affect
33834 the command history, nor will it affect @value{GDBN}'s notion of which
33835 command to repeat if @key{RET} is pressed on a line by itself. This
33836 means that commands can be run behind a user's back by a front-end in
33837 a transparent manner.
33839 The @code{server } prefix does not affect the recording of values into
33840 the value history; to print a value without recording it into the
33841 value history, use the @code{output} command instead of the
33842 @code{print} command.
33844 Using this prefix also disables confirmation requests
33845 (@pxref{confirmation requests}).
33848 @section Annotation for @value{GDBN} Input
33850 @cindex annotations for prompts
33851 When @value{GDBN} prompts for input, it annotates this fact so it is possible
33852 to know when to send output, when the output from a given command is
33855 Different kinds of input each have a different @dfn{input type}. Each
33856 input type has three annotations: a @code{pre-} annotation, which
33857 denotes the beginning of any prompt which is being output, a plain
33858 annotation, which denotes the end of the prompt, and then a @code{post-}
33859 annotation which denotes the end of any echo which may (or may not) be
33860 associated with the input. For example, the @code{prompt} input type
33861 features the following annotations:
33869 The input types are
33872 @findex pre-prompt annotation
33873 @findex prompt annotation
33874 @findex post-prompt annotation
33876 When @value{GDBN} is prompting for a command (the main @value{GDBN} prompt).
33878 @findex pre-commands annotation
33879 @findex commands annotation
33880 @findex post-commands annotation
33882 When @value{GDBN} prompts for a set of commands, like in the @code{commands}
33883 command. The annotations are repeated for each command which is input.
33885 @findex pre-overload-choice annotation
33886 @findex overload-choice annotation
33887 @findex post-overload-choice annotation
33888 @item overload-choice
33889 When @value{GDBN} wants the user to select between various overloaded functions.
33891 @findex pre-query annotation
33892 @findex query annotation
33893 @findex post-query annotation
33895 When @value{GDBN} wants the user to confirm a potentially dangerous operation.
33897 @findex pre-prompt-for-continue annotation
33898 @findex prompt-for-continue annotation
33899 @findex post-prompt-for-continue annotation
33900 @item prompt-for-continue
33901 When @value{GDBN} is asking the user to press return to continue. Note: Don't
33902 expect this to work well; instead use @code{set height 0} to disable
33903 prompting. This is because the counting of lines is buggy in the
33904 presence of annotations.
33909 @cindex annotations for errors, warnings and interrupts
33911 @findex quit annotation
33916 This annotation occurs right before @value{GDBN} responds to an interrupt.
33918 @findex error annotation
33923 This annotation occurs right before @value{GDBN} responds to an error.
33925 Quit and error annotations indicate that any annotations which @value{GDBN} was
33926 in the middle of may end abruptly. For example, if a
33927 @code{value-history-begin} annotation is followed by a @code{error}, one
33928 cannot expect to receive the matching @code{value-history-end}. One
33929 cannot expect not to receive it either, however; an error annotation
33930 does not necessarily mean that @value{GDBN} is immediately returning all the way
33933 @findex error-begin annotation
33934 A quit or error annotation may be preceded by
33940 Any output between that and the quit or error annotation is the error
33943 Warning messages are not yet annotated.
33944 @c If we want to change that, need to fix warning(), type_error(),
33945 @c range_error(), and possibly other places.
33948 @section Invalidation Notices
33950 @cindex annotations for invalidation messages
33951 The following annotations say that certain pieces of state may have
33955 @findex frames-invalid annotation
33956 @item ^Z^Zframes-invalid
33958 The frames (for example, output from the @code{backtrace} command) may
33961 @findex breakpoints-invalid annotation
33962 @item ^Z^Zbreakpoints-invalid
33964 The breakpoints may have changed. For example, the user just added or
33965 deleted a breakpoint.
33968 @node Annotations for Running
33969 @section Running the Program
33970 @cindex annotations for running programs
33972 @findex starting annotation
33973 @findex stopping annotation
33974 When the program starts executing due to a @value{GDBN} command such as
33975 @code{step} or @code{continue},
33981 is output. When the program stops,
33987 is output. Before the @code{stopped} annotation, a variety of
33988 annotations describe how the program stopped.
33991 @findex exited annotation
33992 @item ^Z^Zexited @var{exit-status}
33993 The program exited, and @var{exit-status} is the exit status (zero for
33994 successful exit, otherwise nonzero).
33996 @findex signalled annotation
33997 @findex signal-name annotation
33998 @findex signal-name-end annotation
33999 @findex signal-string annotation
34000 @findex signal-string-end annotation
34001 @item ^Z^Zsignalled
34002 The program exited with a signal. After the @code{^Z^Zsignalled}, the
34003 annotation continues:
34009 ^Z^Zsignal-name-end
34013 ^Z^Zsignal-string-end
34018 where @var{name} is the name of the signal, such as @code{SIGILL} or
34019 @code{SIGSEGV}, and @var{string} is the explanation of the signal, such
34020 as @code{Illegal Instruction} or @code{Segmentation fault}.
34021 @var{intro-text}, @var{middle-text}, and @var{end-text} are for the
34022 user's benefit and have no particular format.
34024 @findex signal annotation
34026 The syntax of this annotation is just like @code{signalled}, but @value{GDBN} is
34027 just saying that the program received the signal, not that it was
34028 terminated with it.
34030 @findex breakpoint annotation
34031 @item ^Z^Zbreakpoint @var{number}
34032 The program hit breakpoint number @var{number}.
34034 @findex watchpoint annotation
34035 @item ^Z^Zwatchpoint @var{number}
34036 The program hit watchpoint number @var{number}.
34039 @node Source Annotations
34040 @section Displaying Source
34041 @cindex annotations for source display
34043 @findex source annotation
34044 The following annotation is used instead of displaying source code:
34047 ^Z^Zsource @var{filename}:@var{line}:@var{character}:@var{middle}:@var{addr}
34050 where @var{filename} is an absolute file name indicating which source
34051 file, @var{line} is the line number within that file (where 1 is the
34052 first line in the file), @var{character} is the character position
34053 within the file (where 0 is the first character in the file) (for most
34054 debug formats this will necessarily point to the beginning of a line),
34055 @var{middle} is @samp{middle} if @var{addr} is in the middle of the
34056 line, or @samp{beg} if @var{addr} is at the beginning of the line, and
34057 @var{addr} is the address in the target program associated with the
34058 source which is being displayed. @var{addr} is in the form @samp{0x}
34059 followed by one or more lowercase hex digits (note that this does not
34060 depend on the language).
34062 @node JIT Interface
34063 @chapter JIT Compilation Interface
34064 @cindex just-in-time compilation
34065 @cindex JIT compilation interface
34067 This chapter documents @value{GDBN}'s @dfn{just-in-time} (JIT) compilation
34068 interface. A JIT compiler is a program or library that generates native
34069 executable code at runtime and executes it, usually in order to achieve good
34070 performance while maintaining platform independence.
34072 Programs that use JIT compilation are normally difficult to debug because
34073 portions of their code are generated at runtime, instead of being loaded from
34074 object files, which is where @value{GDBN} normally finds the program's symbols
34075 and debug information. In order to debug programs that use JIT compilation,
34076 @value{GDBN} has an interface that allows the program to register in-memory
34077 symbol files with @value{GDBN} at runtime.
34079 If you are using @value{GDBN} to debug a program that uses this interface, then
34080 it should work transparently so long as you have not stripped the binary. If
34081 you are developing a JIT compiler, then the interface is documented in the rest
34082 of this chapter. At this time, the only known client of this interface is the
34085 Broadly speaking, the JIT interface mirrors the dynamic loader interface. The
34086 JIT compiler communicates with @value{GDBN} by writing data into a global
34087 variable and calling a fuction at a well-known symbol. When @value{GDBN}
34088 attaches, it reads a linked list of symbol files from the global variable to
34089 find existing code, and puts a breakpoint in the function so that it can find
34090 out about additional code.
34093 * Declarations:: Relevant C struct declarations
34094 * Registering Code:: Steps to register code
34095 * Unregistering Code:: Steps to unregister code
34096 * Custom Debug Info:: Emit debug information in a custom format
34100 @section JIT Declarations
34102 These are the relevant struct declarations that a C program should include to
34103 implement the interface:
34113 struct jit_code_entry
34115 struct jit_code_entry *next_entry;
34116 struct jit_code_entry *prev_entry;
34117 const char *symfile_addr;
34118 uint64_t symfile_size;
34121 struct jit_descriptor
34124 /* This type should be jit_actions_t, but we use uint32_t
34125 to be explicit about the bitwidth. */
34126 uint32_t action_flag;
34127 struct jit_code_entry *relevant_entry;
34128 struct jit_code_entry *first_entry;
34131 /* GDB puts a breakpoint in this function. */
34132 void __attribute__((noinline)) __jit_debug_register_code() @{ @};
34134 /* Make sure to specify the version statically, because the
34135 debugger may check the version before we can set it. */
34136 struct jit_descriptor __jit_debug_descriptor = @{ 1, 0, 0, 0 @};
34139 If the JIT is multi-threaded, then it is important that the JIT synchronize any
34140 modifications to this global data properly, which can easily be done by putting
34141 a global mutex around modifications to these structures.
34143 @node Registering Code
34144 @section Registering Code
34146 To register code with @value{GDBN}, the JIT should follow this protocol:
34150 Generate an object file in memory with symbols and other desired debug
34151 information. The file must include the virtual addresses of the sections.
34154 Create a code entry for the file, which gives the start and size of the symbol
34158 Add it to the linked list in the JIT descriptor.
34161 Point the relevant_entry field of the descriptor at the entry.
34164 Set @code{action_flag} to @code{JIT_REGISTER} and call
34165 @code{__jit_debug_register_code}.
34168 When @value{GDBN} is attached and the breakpoint fires, @value{GDBN} uses the
34169 @code{relevant_entry} pointer so it doesn't have to walk the list looking for
34170 new code. However, the linked list must still be maintained in order to allow
34171 @value{GDBN} to attach to a running process and still find the symbol files.
34173 @node Unregistering Code
34174 @section Unregistering Code
34176 If code is freed, then the JIT should use the following protocol:
34180 Remove the code entry corresponding to the code from the linked list.
34183 Point the @code{relevant_entry} field of the descriptor at the code entry.
34186 Set @code{action_flag} to @code{JIT_UNREGISTER} and call
34187 @code{__jit_debug_register_code}.
34190 If the JIT frees or recompiles code without unregistering it, then @value{GDBN}
34191 and the JIT will leak the memory used for the associated symbol files.
34193 @node Custom Debug Info
34194 @section Custom Debug Info
34195 @cindex custom JIT debug info
34196 @cindex JIT debug info reader
34198 Generating debug information in platform-native file formats (like ELF
34199 or COFF) may be an overkill for JIT compilers; especially if all the
34200 debug info is used for is displaying a meaningful backtrace. The
34201 issue can be resolved by having the JIT writers decide on a debug info
34202 format and also provide a reader that parses the debug info generated
34203 by the JIT compiler. This section gives a brief overview on writing
34204 such a parser. More specific details can be found in the source file
34205 @file{gdb/jit-reader.in}, which is also installed as a header at
34206 @file{@var{includedir}/gdb/jit-reader.h} for easy inclusion.
34208 The reader is implemented as a shared object (so this functionality is
34209 not available on platforms which don't allow loading shared objects at
34210 runtime). Two @value{GDBN} commands, @code{jit-reader-load} and
34211 @code{jit-reader-unload} are provided, to be used to load and unload
34212 the readers from a preconfigured directory. Once loaded, the shared
34213 object is used the parse the debug information emitted by the JIT
34217 * Using JIT Debug Info Readers:: How to use supplied readers correctly
34218 * Writing JIT Debug Info Readers:: Creating a debug-info reader
34221 @node Using JIT Debug Info Readers
34222 @subsection Using JIT Debug Info Readers
34223 @kindex jit-reader-load
34224 @kindex jit-reader-unload
34226 Readers can be loaded and unloaded using the @code{jit-reader-load}
34227 and @code{jit-reader-unload} commands.
34230 @item jit-reader-load @var{reader}
34231 Load the JIT reader named @var{reader}. @var{reader} is a shared
34232 object specified as either an absolute or a relative file name. In
34233 the latter case, @value{GDBN} will try to load the reader from a
34234 pre-configured directory, usually @file{@var{libdir}/gdb/} on a UNIX
34235 system (here @var{libdir} is the system library directory, often
34236 @file{/usr/local/lib}).
34238 Only one reader can be active at a time; trying to load a second
34239 reader when one is already loaded will result in @value{GDBN}
34240 reporting an error. A new JIT reader can be loaded by first unloading
34241 the current one using @code{jit-reader-unload} and then invoking
34242 @code{jit-reader-load}.
34244 @item jit-reader-unload
34245 Unload the currently loaded JIT reader.
34249 @node Writing JIT Debug Info Readers
34250 @subsection Writing JIT Debug Info Readers
34251 @cindex writing JIT debug info readers
34253 As mentioned, a reader is essentially a shared object conforming to a
34254 certain ABI. This ABI is described in @file{jit-reader.h}.
34256 @file{jit-reader.h} defines the structures, macros and functions
34257 required to write a reader. It is installed (along with
34258 @value{GDBN}), in @file{@var{includedir}/gdb} where @var{includedir} is
34259 the system include directory.
34261 Readers need to be released under a GPL compatible license. A reader
34262 can be declared as released under such a license by placing the macro
34263 @code{GDB_DECLARE_GPL_COMPATIBLE_READER} in a source file.
34265 The entry point for readers is the symbol @code{gdb_init_reader},
34266 which is expected to be a function with the prototype
34268 @findex gdb_init_reader
34270 extern struct gdb_reader_funcs *gdb_init_reader (void);
34273 @cindex @code{struct gdb_reader_funcs}
34275 @code{struct gdb_reader_funcs} contains a set of pointers to callback
34276 functions. These functions are executed to read the debug info
34277 generated by the JIT compiler (@code{read}), to unwind stack frames
34278 (@code{unwind}) and to create canonical frame IDs
34279 (@code{get_Frame_id}). It also has a callback that is called when the
34280 reader is being unloaded (@code{destroy}). The struct looks like this
34283 struct gdb_reader_funcs
34285 /* Must be set to GDB_READER_INTERFACE_VERSION. */
34286 int reader_version;
34288 /* For use by the reader. */
34291 gdb_read_debug_info *read;
34292 gdb_unwind_frame *unwind;
34293 gdb_get_frame_id *get_frame_id;
34294 gdb_destroy_reader *destroy;
34298 @cindex @code{struct gdb_symbol_callbacks}
34299 @cindex @code{struct gdb_unwind_callbacks}
34301 The callbacks are provided with another set of callbacks by
34302 @value{GDBN} to do their job. For @code{read}, these callbacks are
34303 passed in a @code{struct gdb_symbol_callbacks} and for @code{unwind}
34304 and @code{get_frame_id}, in a @code{struct gdb_unwind_callbacks}.
34305 @code{struct gdb_symbol_callbacks} has callbacks to create new object
34306 files and new symbol tables inside those object files. @code{struct
34307 gdb_unwind_callbacks} has callbacks to read registers off the current
34308 frame and to write out the values of the registers in the previous
34309 frame. Both have a callback (@code{target_read}) to read bytes off the
34310 target's address space.
34312 @node In-Process Agent
34313 @chapter In-Process Agent
34314 @cindex debugging agent
34315 The traditional debugging model is conceptually low-speed, but works fine,
34316 because most bugs can be reproduced in debugging-mode execution. However,
34317 as multi-core or many-core processors are becoming mainstream, and
34318 multi-threaded programs become more and more popular, there should be more
34319 and more bugs that only manifest themselves at normal-mode execution, for
34320 example, thread races, because debugger's interference with the program's
34321 timing may conceal the bugs. On the other hand, in some applications,
34322 it is not feasible for the debugger to interrupt the program's execution
34323 long enough for the developer to learn anything helpful about its behavior.
34324 If the program's correctness depends on its real-time behavior, delays
34325 introduced by a debugger might cause the program to fail, even when the
34326 code itself is correct. It is useful to be able to observe the program's
34327 behavior without interrupting it.
34329 Therefore, traditional debugging model is too intrusive to reproduce
34330 some bugs. In order to reduce the interference with the program, we can
34331 reduce the number of operations performed by debugger. The
34332 @dfn{In-Process Agent}, a shared library, is running within the same
34333 process with inferior, and is able to perform some debugging operations
34334 itself. As a result, debugger is only involved when necessary, and
34335 performance of debugging can be improved accordingly. Note that
34336 interference with program can be reduced but can't be removed completely,
34337 because the in-process agent will still stop or slow down the program.
34339 The in-process agent can interpret and execute Agent Expressions
34340 (@pxref{Agent Expressions}) during performing debugging operations. The
34341 agent expressions can be used for different purposes, such as collecting
34342 data in tracepoints, and condition evaluation in breakpoints.
34344 @anchor{Control Agent}
34345 You can control whether the in-process agent is used as an aid for
34346 debugging with the following commands:
34349 @kindex set agent on
34351 Causes the in-process agent to perform some operations on behalf of the
34352 debugger. Just which operations requested by the user will be done
34353 by the in-process agent depends on the its capabilities. For example,
34354 if you request to evaluate breakpoint conditions in the in-process agent,
34355 and the in-process agent has such capability as well, then breakpoint
34356 conditions will be evaluated in the in-process agent.
34358 @kindex set agent off
34359 @item set agent off
34360 Disables execution of debugging operations by the in-process agent. All
34361 of the operations will be performed by @value{GDBN}.
34365 Display the current setting of execution of debugging operations by
34366 the in-process agent.
34370 * In-Process Agent Protocol::
34373 @node In-Process Agent Protocol
34374 @section In-Process Agent Protocol
34375 @cindex in-process agent protocol
34377 The in-process agent is able to communicate with both @value{GDBN} and
34378 GDBserver (@pxref{In-Process Agent}). This section documents the protocol
34379 used for communications between @value{GDBN} or GDBserver and the IPA.
34380 In general, @value{GDBN} or GDBserver sends commands
34381 (@pxref{IPA Protocol Commands}) and data to in-process agent, and then
34382 in-process agent replies back with the return result of the command, or
34383 some other information. The data sent to in-process agent is composed
34384 of primitive data types, such as 4-byte or 8-byte type, and composite
34385 types, which are called objects (@pxref{IPA Protocol Objects}).
34388 * IPA Protocol Objects::
34389 * IPA Protocol Commands::
34392 @node IPA Protocol Objects
34393 @subsection IPA Protocol Objects
34394 @cindex ipa protocol objects
34396 The commands sent to and results received from agent may contain some
34397 complex data types called @dfn{objects}.
34399 The in-process agent is running on the same machine with @value{GDBN}
34400 or GDBserver, so it doesn't have to handle as much differences between
34401 two ends as remote protocol (@pxref{Remote Protocol}) tries to handle.
34402 However, there are still some differences of two ends in two processes:
34406 word size. On some 64-bit machines, @value{GDBN} or GDBserver can be
34407 compiled as a 64-bit executable, while in-process agent is a 32-bit one.
34409 ABI. Some machines may have multiple types of ABI, @value{GDBN} or
34410 GDBserver is compiled with one, and in-process agent is compiled with
34414 Here are the IPA Protocol Objects:
34418 agent expression object. It represents an agent expression
34419 (@pxref{Agent Expressions}).
34420 @anchor{agent expression object}
34422 tracepoint action object. It represents a tracepoint action
34423 (@pxref{Tracepoint Actions,,Tracepoint Action Lists}) to collect registers,
34424 memory, static trace data and to evaluate expression.
34425 @anchor{tracepoint action object}
34427 tracepoint object. It represents a tracepoint (@pxref{Tracepoints}).
34428 @anchor{tracepoint object}
34432 The following table describes important attributes of each IPA protocol
34435 @multitable @columnfractions .30 .20 .50
34436 @headitem Name @tab Size @tab Description
34437 @item @emph{agent expression object} @tab @tab
34438 @item length @tab 4 @tab length of bytes code
34439 @item byte code @tab @var{length} @tab contents of byte code
34440 @item @emph{tracepoint action for collecting memory} @tab @tab
34441 @item 'M' @tab 1 @tab type of tracepoint action
34442 @item addr @tab 8 @tab if @var{basereg} is @samp{-1}, @var{addr} is the
34443 address of the lowest byte to collect, otherwise @var{addr} is the offset
34444 of @var{basereg} for memory collecting.
34445 @item len @tab 8 @tab length of memory for collecting
34446 @item basereg @tab 4 @tab the register number containing the starting
34447 memory address for collecting.
34448 @item @emph{tracepoint action for collecting registers} @tab @tab
34449 @item 'R' @tab 1 @tab type of tracepoint action
34450 @item @emph{tracepoint action for collecting static trace data} @tab @tab
34451 @item 'L' @tab 1 @tab type of tracepoint action
34452 @item @emph{tracepoint action for expression evaluation} @tab @tab
34453 @item 'X' @tab 1 @tab type of tracepoint action
34454 @item agent expression @tab length of @tab @ref{agent expression object}
34455 @item @emph{tracepoint object} @tab @tab
34456 @item number @tab 4 @tab number of tracepoint
34457 @item address @tab 8 @tab address of tracepoint inserted on
34458 @item type @tab 4 @tab type of tracepoint
34459 @item enabled @tab 1 @tab enable or disable of tracepoint
34460 @item step_count @tab 8 @tab step
34461 @item pass_count @tab 8 @tab pass
34462 @item numactions @tab 4 @tab number of tracepoint actions
34463 @item hit count @tab 8 @tab hit count
34464 @item trace frame usage @tab 8 @tab trace frame usage
34465 @item compiled_cond @tab 8 @tab compiled condition
34466 @item orig_size @tab 8 @tab orig size
34467 @item condition @tab 4 if condition is NULL otherwise length of
34468 @ref{agent expression object}
34469 @tab zero if condition is NULL, otherwise is
34470 @ref{agent expression object}
34471 @item actions @tab variable
34472 @tab numactions number of @ref{tracepoint action object}
34475 @node IPA Protocol Commands
34476 @subsection IPA Protocol Commands
34477 @cindex ipa protocol commands
34479 The spaces in each command are delimiters to ease reading this commands
34480 specification. They don't exist in real commands.
34484 @item FastTrace:@var{tracepoint_object} @var{gdb_jump_pad_head}
34485 Installs a new fast tracepoint described by @var{tracepoint_object}
34486 (@pxref{tracepoint object}). @var{gdb_jump_pad_head}, 8-byte long, is the
34487 head of @dfn{jumppad}, which is used to jump to data collection routine
34492 @item OK @var{target_address} @var{gdb_jump_pad_head} @var{fjump_size} @var{fjump}
34493 @var{target_address} is address of tracepoint in the inferior.
34494 @var{gdb_jump_pad_head} is updated head of jumppad. Both of
34495 @var{target_address} and @var{gdb_jump_pad_head} are 8-byte long.
34496 @var{fjump} contains a sequence of instructions jump to jumppad entry.
34497 @var{fjump_size}, 4-byte long, is the size of @var{fjump}.
34504 Closes the in-process agent. This command is sent when @value{GDBN} or GDBserver
34505 is about to kill inferiors.
34513 @item probe_marker_at:@var{address}
34514 Asks in-process agent to probe the marker at @var{address}.
34521 @item unprobe_marker_at:@var{address}
34522 Asks in-process agent to unprobe the marker at @var{address}.
34526 @chapter Reporting Bugs in @value{GDBN}
34527 @cindex bugs in @value{GDBN}
34528 @cindex reporting bugs in @value{GDBN}
34530 Your bug reports play an essential role in making @value{GDBN} reliable.
34532 Reporting a bug may help you by bringing a solution to your problem, or it
34533 may not. But in any case the principal function of a bug report is to help
34534 the entire community by making the next version of @value{GDBN} work better. Bug
34535 reports are your contribution to the maintenance of @value{GDBN}.
34537 In order for a bug report to serve its purpose, you must include the
34538 information that enables us to fix the bug.
34541 * Bug Criteria:: Have you found a bug?
34542 * Bug Reporting:: How to report bugs
34546 @section Have You Found a Bug?
34547 @cindex bug criteria
34549 If you are not sure whether you have found a bug, here are some guidelines:
34552 @cindex fatal signal
34553 @cindex debugger crash
34554 @cindex crash of debugger
34556 If the debugger gets a fatal signal, for any input whatever, that is a
34557 @value{GDBN} bug. Reliable debuggers never crash.
34559 @cindex error on valid input
34561 If @value{GDBN} produces an error message for valid input, that is a
34562 bug. (Note that if you're cross debugging, the problem may also be
34563 somewhere in the connection to the target.)
34565 @cindex invalid input
34567 If @value{GDBN} does not produce an error message for invalid input,
34568 that is a bug. However, you should note that your idea of
34569 ``invalid input'' might be our idea of ``an extension'' or ``support
34570 for traditional practice''.
34573 If you are an experienced user of debugging tools, your suggestions
34574 for improvement of @value{GDBN} are welcome in any case.
34577 @node Bug Reporting
34578 @section How to Report Bugs
34579 @cindex bug reports
34580 @cindex @value{GDBN} bugs, reporting
34582 A number of companies and individuals offer support for @sc{gnu} products.
34583 If you obtained @value{GDBN} from a support organization, we recommend you
34584 contact that organization first.
34586 You can find contact information for many support companies and
34587 individuals in the file @file{etc/SERVICE} in the @sc{gnu} Emacs
34589 @c should add a web page ref...
34592 @ifset BUGURL_DEFAULT
34593 In any event, we also recommend that you submit bug reports for
34594 @value{GDBN}. The preferred method is to submit them directly using
34595 @uref{http://www.gnu.org/software/gdb/bugs/, @value{GDBN}'s Bugs web
34596 page}. Alternatively, the @email{bug-gdb@@gnu.org, e-mail gateway} can
34599 @strong{Do not send bug reports to @samp{info-gdb}, or to
34600 @samp{help-gdb}, or to any newsgroups.} Most users of @value{GDBN} do
34601 not want to receive bug reports. Those that do have arranged to receive
34604 The mailing list @samp{bug-gdb} has a newsgroup @samp{gnu.gdb.bug} which
34605 serves as a repeater. The mailing list and the newsgroup carry exactly
34606 the same messages. Often people think of posting bug reports to the
34607 newsgroup instead of mailing them. This appears to work, but it has one
34608 problem which can be crucial: a newsgroup posting often lacks a mail
34609 path back to the sender. Thus, if we need to ask for more information,
34610 we may be unable to reach you. For this reason, it is better to send
34611 bug reports to the mailing list.
34613 @ifclear BUGURL_DEFAULT
34614 In any event, we also recommend that you submit bug reports for
34615 @value{GDBN} to @value{BUGURL}.
34619 The fundamental principle of reporting bugs usefully is this:
34620 @strong{report all the facts}. If you are not sure whether to state a
34621 fact or leave it out, state it!
34623 Often people omit facts because they think they know what causes the
34624 problem and assume that some details do not matter. Thus, you might
34625 assume that the name of the variable you use in an example does not matter.
34626 Well, probably it does not, but one cannot be sure. Perhaps the bug is a
34627 stray memory reference which happens to fetch from the location where that
34628 name is stored in memory; perhaps, if the name were different, the contents
34629 of that location would fool the debugger into doing the right thing despite
34630 the bug. Play it safe and give a specific, complete example. That is the
34631 easiest thing for you to do, and the most helpful.
34633 Keep in mind that the purpose of a bug report is to enable us to fix the
34634 bug. It may be that the bug has been reported previously, but neither
34635 you nor we can know that unless your bug report is complete and
34638 Sometimes people give a few sketchy facts and ask, ``Does this ring a
34639 bell?'' Those bug reports are useless, and we urge everyone to
34640 @emph{refuse to respond to them} except to chide the sender to report
34643 To enable us to fix the bug, you should include all these things:
34647 The version of @value{GDBN}. @value{GDBN} announces it if you start
34648 with no arguments; you can also print it at any time using @code{show
34651 Without this, we will not know whether there is any point in looking for
34652 the bug in the current version of @value{GDBN}.
34655 The type of machine you are using, and the operating system name and
34659 What compiler (and its version) was used to compile @value{GDBN}---e.g.@:
34660 ``@value{GCC}--2.8.1''.
34663 What compiler (and its version) was used to compile the program you are
34664 debugging---e.g.@: ``@value{GCC}--2.8.1'', or ``HP92453-01 A.10.32.03 HP
34665 C Compiler''. For @value{NGCC}, you can say @kbd{@value{GCC} --version}
34666 to get this information; for other compilers, see the documentation for
34670 The command arguments you gave the compiler to compile your example and
34671 observe the bug. For example, did you use @samp{-O}? To guarantee
34672 you will not omit something important, list them all. A copy of the
34673 Makefile (or the output from make) is sufficient.
34675 If we were to try to guess the arguments, we would probably guess wrong
34676 and then we might not encounter the bug.
34679 A complete input script, and all necessary source files, that will
34683 A description of what behavior you observe that you believe is
34684 incorrect. For example, ``It gets a fatal signal.''
34686 Of course, if the bug is that @value{GDBN} gets a fatal signal, then we
34687 will certainly notice it. But if the bug is incorrect output, we might
34688 not notice unless it is glaringly wrong. You might as well not give us
34689 a chance to make a mistake.
34691 Even if the problem you experience is a fatal signal, you should still
34692 say so explicitly. Suppose something strange is going on, such as, your
34693 copy of @value{GDBN} is out of synch, or you have encountered a bug in
34694 the C library on your system. (This has happened!) Your copy might
34695 crash and ours would not. If you told us to expect a crash, then when
34696 ours fails to crash, we would know that the bug was not happening for
34697 us. If you had not told us to expect a crash, then we would not be able
34698 to draw any conclusion from our observations.
34701 @cindex recording a session script
34702 To collect all this information, you can use a session recording program
34703 such as @command{script}, which is available on many Unix systems.
34704 Just run your @value{GDBN} session inside @command{script} and then
34705 include the @file{typescript} file with your bug report.
34707 Another way to record a @value{GDBN} session is to run @value{GDBN}
34708 inside Emacs and then save the entire buffer to a file.
34711 If you wish to suggest changes to the @value{GDBN} source, send us context
34712 diffs. If you even discuss something in the @value{GDBN} source, refer to
34713 it by context, not by line number.
34715 The line numbers in our development sources will not match those in your
34716 sources. Your line numbers would convey no useful information to us.
34720 Here are some things that are not necessary:
34724 A description of the envelope of the bug.
34726 Often people who encounter a bug spend a lot of time investigating
34727 which changes to the input file will make the bug go away and which
34728 changes will not affect it.
34730 This is often time consuming and not very useful, because the way we
34731 will find the bug is by running a single example under the debugger
34732 with breakpoints, not by pure deduction from a series of examples.
34733 We recommend that you save your time for something else.
34735 Of course, if you can find a simpler example to report @emph{instead}
34736 of the original one, that is a convenience for us. Errors in the
34737 output will be easier to spot, running under the debugger will take
34738 less time, and so on.
34740 However, simplification is not vital; if you do not want to do this,
34741 report the bug anyway and send us the entire test case you used.
34744 A patch for the bug.
34746 A patch for the bug does help us if it is a good one. But do not omit
34747 the necessary information, such as the test case, on the assumption that
34748 a patch is all we need. We might see problems with your patch and decide
34749 to fix the problem another way, or we might not understand it at all.
34751 Sometimes with a program as complicated as @value{GDBN} it is very hard to
34752 construct an example that will make the program follow a certain path
34753 through the code. If you do not send us the example, we will not be able
34754 to construct one, so we will not be able to verify that the bug is fixed.
34756 And if we cannot understand what bug you are trying to fix, or why your
34757 patch should be an improvement, we will not install it. A test case will
34758 help us to understand.
34761 A guess about what the bug is or what it depends on.
34763 Such guesses are usually wrong. Even we cannot guess right about such
34764 things without first using the debugger to find the facts.
34767 @c The readline documentation is distributed with the readline code
34768 @c and consists of the two following files:
34771 @c Use -I with makeinfo to point to the appropriate directory,
34772 @c environment var TEXINPUTS with TeX.
34773 @ifclear SYSTEM_READLINE
34774 @include rluser.texi
34775 @include hsuser.texi
34779 @appendix In Memoriam
34781 The @value{GDBN} project mourns the loss of the following long-time
34786 Fred was a long-standing contributor to @value{GDBN} (1991-2006), and
34787 to Free Software in general. Outside of @value{GDBN}, he was known in
34788 the Amiga world for his series of Fish Disks, and the GeekGadget project.
34790 @item Michael Snyder
34791 Michael was one of the Global Maintainers of the @value{GDBN} project,
34792 with contributions recorded as early as 1996, until 2011. In addition
34793 to his day to day participation, he was a large driving force behind
34794 adding Reverse Debugging to @value{GDBN}.
34797 Beyond their technical contributions to the project, they were also
34798 enjoyable members of the Free Software Community. We will miss them.
34800 @node Formatting Documentation
34801 @appendix Formatting Documentation
34803 @cindex @value{GDBN} reference card
34804 @cindex reference card
34805 The @value{GDBN} 4 release includes an already-formatted reference card, ready
34806 for printing with PostScript or Ghostscript, in the @file{gdb}
34807 subdirectory of the main source directory@footnote{In
34808 @file{gdb-@value{GDBVN}/gdb/refcard.ps} of the version @value{GDBVN}
34809 release.}. If you can use PostScript or Ghostscript with your printer,
34810 you can print the reference card immediately with @file{refcard.ps}.
34812 The release also includes the source for the reference card. You
34813 can format it, using @TeX{}, by typing:
34819 The @value{GDBN} reference card is designed to print in @dfn{landscape}
34820 mode on US ``letter'' size paper;
34821 that is, on a sheet 11 inches wide by 8.5 inches
34822 high. You will need to specify this form of printing as an option to
34823 your @sc{dvi} output program.
34825 @cindex documentation
34827 All the documentation for @value{GDBN} comes as part of the machine-readable
34828 distribution. The documentation is written in Texinfo format, which is
34829 a documentation system that uses a single source file to produce both
34830 on-line information and a printed manual. You can use one of the Info
34831 formatting commands to create the on-line version of the documentation
34832 and @TeX{} (or @code{texi2roff}) to typeset the printed version.
34834 @value{GDBN} includes an already formatted copy of the on-line Info
34835 version of this manual in the @file{gdb} subdirectory. The main Info
34836 file is @file{gdb-@value{GDBVN}/gdb/gdb.info}, and it refers to
34837 subordinate files matching @samp{gdb.info*} in the same directory. If
34838 necessary, you can print out these files, or read them with any editor;
34839 but they are easier to read using the @code{info} subsystem in @sc{gnu}
34840 Emacs or the standalone @code{info} program, available as part of the
34841 @sc{gnu} Texinfo distribution.
34843 If you want to format these Info files yourself, you need one of the
34844 Info formatting programs, such as @code{texinfo-format-buffer} or
34847 If you have @code{makeinfo} installed, and are in the top level
34848 @value{GDBN} source directory (@file{gdb-@value{GDBVN}}, in the case of
34849 version @value{GDBVN}), you can make the Info file by typing:
34856 If you want to typeset and print copies of this manual, you need @TeX{},
34857 a program to print its @sc{dvi} output files, and @file{texinfo.tex}, the
34858 Texinfo definitions file.
34860 @TeX{} is a typesetting program; it does not print files directly, but
34861 produces output files called @sc{dvi} files. To print a typeset
34862 document, you need a program to print @sc{dvi} files. If your system
34863 has @TeX{} installed, chances are it has such a program. The precise
34864 command to use depends on your system; @kbd{lpr -d} is common; another
34865 (for PostScript devices) is @kbd{dvips}. The @sc{dvi} print command may
34866 require a file name without any extension or a @samp{.dvi} extension.
34868 @TeX{} also requires a macro definitions file called
34869 @file{texinfo.tex}. This file tells @TeX{} how to typeset a document
34870 written in Texinfo format. On its own, @TeX{} cannot either read or
34871 typeset a Texinfo file. @file{texinfo.tex} is distributed with GDB
34872 and is located in the @file{gdb-@var{version-number}/texinfo}
34875 If you have @TeX{} and a @sc{dvi} printer program installed, you can
34876 typeset and print this manual. First switch to the @file{gdb}
34877 subdirectory of the main source directory (for example, to
34878 @file{gdb-@value{GDBVN}/gdb}) and type:
34884 Then give @file{gdb.dvi} to your @sc{dvi} printing program.
34886 @node Installing GDB
34887 @appendix Installing @value{GDBN}
34888 @cindex installation
34891 * Requirements:: Requirements for building @value{GDBN}
34892 * Running Configure:: Invoking the @value{GDBN} @file{configure} script
34893 * Separate Objdir:: Compiling @value{GDBN} in another directory
34894 * Config Names:: Specifying names for hosts and targets
34895 * Configure Options:: Summary of options for configure
34896 * System-wide configuration:: Having a system-wide init file
34900 @section Requirements for Building @value{GDBN}
34901 @cindex building @value{GDBN}, requirements for
34903 Building @value{GDBN} requires various tools and packages to be available.
34904 Other packages will be used only if they are found.
34906 @heading Tools/Packages Necessary for Building @value{GDBN}
34908 @item ISO C90 compiler
34909 @value{GDBN} is written in ISO C90. It should be buildable with any
34910 working C90 compiler, e.g.@: GCC.
34914 @heading Tools/Packages Optional for Building @value{GDBN}
34918 @value{GDBN} can use the Expat XML parsing library. This library may be
34919 included with your operating system distribution; if it is not, you
34920 can get the latest version from @url{http://expat.sourceforge.net}.
34921 The @file{configure} script will search for this library in several
34922 standard locations; if it is installed in an unusual path, you can
34923 use the @option{--with-libexpat-prefix} option to specify its location.
34929 Remote protocol memory maps (@pxref{Memory Map Format})
34931 Target descriptions (@pxref{Target Descriptions})
34933 Remote shared library lists (@xref{Library List Format},
34934 or alternatively @pxref{Library List Format for SVR4 Targets})
34936 MS-Windows shared libraries (@pxref{Shared Libraries})
34938 Traceframe info (@pxref{Traceframe Info Format})
34940 Branch trace (@pxref{Branch Trace Format})
34944 @cindex compressed debug sections
34945 @value{GDBN} will use the @samp{zlib} library, if available, to read
34946 compressed debug sections. Some linkers, such as GNU gold, are capable
34947 of producing binaries with compressed debug sections. If @value{GDBN}
34948 is compiled with @samp{zlib}, it will be able to read the debug
34949 information in such binaries.
34951 The @samp{zlib} library is likely included with your operating system
34952 distribution; if it is not, you can get the latest version from
34953 @url{http://zlib.net}.
34956 @value{GDBN}'s features related to character sets (@pxref{Character
34957 Sets}) require a functioning @code{iconv} implementation. If you are
34958 on a GNU system, then this is provided by the GNU C Library. Some
34959 other systems also provide a working @code{iconv}.
34961 If @value{GDBN} is using the @code{iconv} program which is installed
34962 in a non-standard place, you will need to tell @value{GDBN} where to find it.
34963 This is done with @option{--with-iconv-bin} which specifies the
34964 directory that contains the @code{iconv} program.
34966 On systems without @code{iconv}, you can install GNU Libiconv. If you
34967 have previously installed Libiconv, you can use the
34968 @option{--with-libiconv-prefix} option to configure.
34970 @value{GDBN}'s top-level @file{configure} and @file{Makefile} will
34971 arrange to build Libiconv if a directory named @file{libiconv} appears
34972 in the top-most source directory. If Libiconv is built this way, and
34973 if the operating system does not provide a suitable @code{iconv}
34974 implementation, then the just-built library will automatically be used
34975 by @value{GDBN}. One easy way to set this up is to download GNU
34976 Libiconv, unpack it, and then rename the directory holding the
34977 Libiconv source code to @samp{libiconv}.
34980 @node Running Configure
34981 @section Invoking the @value{GDBN} @file{configure} Script
34982 @cindex configuring @value{GDBN}
34983 @value{GDBN} comes with a @file{configure} script that automates the process
34984 of preparing @value{GDBN} for installation; you can then use @code{make} to
34985 build the @code{gdb} program.
34987 @c irrelevant in info file; it's as current as the code it lives with.
34988 @footnote{If you have a more recent version of @value{GDBN} than @value{GDBVN},
34989 look at the @file{README} file in the sources; we may have improved the
34990 installation procedures since publishing this manual.}
34993 The @value{GDBN} distribution includes all the source code you need for
34994 @value{GDBN} in a single directory, whose name is usually composed by
34995 appending the version number to @samp{gdb}.
34997 For example, the @value{GDBN} version @value{GDBVN} distribution is in the
34998 @file{gdb-@value{GDBVN}} directory. That directory contains:
35001 @item gdb-@value{GDBVN}/configure @r{(and supporting files)}
35002 script for configuring @value{GDBN} and all its supporting libraries
35004 @item gdb-@value{GDBVN}/gdb
35005 the source specific to @value{GDBN} itself
35007 @item gdb-@value{GDBVN}/bfd
35008 source for the Binary File Descriptor library
35010 @item gdb-@value{GDBVN}/include
35011 @sc{gnu} include files
35013 @item gdb-@value{GDBVN}/libiberty
35014 source for the @samp{-liberty} free software library
35016 @item gdb-@value{GDBVN}/opcodes
35017 source for the library of opcode tables and disassemblers
35019 @item gdb-@value{GDBVN}/readline
35020 source for the @sc{gnu} command-line interface
35022 @item gdb-@value{GDBVN}/glob
35023 source for the @sc{gnu} filename pattern-matching subroutine
35025 @item gdb-@value{GDBVN}/mmalloc
35026 source for the @sc{gnu} memory-mapped malloc package
35029 The simplest way to configure and build @value{GDBN} is to run @file{configure}
35030 from the @file{gdb-@var{version-number}} source directory, which in
35031 this example is the @file{gdb-@value{GDBVN}} directory.
35033 First switch to the @file{gdb-@var{version-number}} source directory
35034 if you are not already in it; then run @file{configure}. Pass the
35035 identifier for the platform on which @value{GDBN} will run as an
35041 cd gdb-@value{GDBVN}
35042 ./configure @var{host}
35047 where @var{host} is an identifier such as @samp{sun4} or
35048 @samp{decstation}, that identifies the platform where @value{GDBN} will run.
35049 (You can often leave off @var{host}; @file{configure} tries to guess the
35050 correct value by examining your system.)
35052 Running @samp{configure @var{host}} and then running @code{make} builds the
35053 @file{bfd}, @file{readline}, @file{mmalloc}, and @file{libiberty}
35054 libraries, then @code{gdb} itself. The configured source files, and the
35055 binaries, are left in the corresponding source directories.
35058 @file{configure} is a Bourne-shell (@code{/bin/sh}) script; if your
35059 system does not recognize this automatically when you run a different
35060 shell, you may need to run @code{sh} on it explicitly:
35063 sh configure @var{host}
35066 If you run @file{configure} from a directory that contains source
35067 directories for multiple libraries or programs, such as the
35068 @file{gdb-@value{GDBVN}} source directory for version @value{GDBVN},
35070 creates configuration files for every directory level underneath (unless
35071 you tell it not to, with the @samp{--norecursion} option).
35073 You should run the @file{configure} script from the top directory in the
35074 source tree, the @file{gdb-@var{version-number}} directory. If you run
35075 @file{configure} from one of the subdirectories, you will configure only
35076 that subdirectory. That is usually not what you want. In particular,
35077 if you run the first @file{configure} from the @file{gdb} subdirectory
35078 of the @file{gdb-@var{version-number}} directory, you will omit the
35079 configuration of @file{bfd}, @file{readline}, and other sibling
35080 directories of the @file{gdb} subdirectory. This leads to build errors
35081 about missing include files such as @file{bfd/bfd.h}.
35083 You can install @code{@value{GDBP}} anywhere; it has no hardwired paths.
35084 However, you should make sure that the shell on your path (named by
35085 the @samp{SHELL} environment variable) is publicly readable. Remember
35086 that @value{GDBN} uses the shell to start your program---some systems refuse to
35087 let @value{GDBN} debug child processes whose programs are not readable.
35089 @node Separate Objdir
35090 @section Compiling @value{GDBN} in Another Directory
35092 If you want to run @value{GDBN} versions for several host or target machines,
35093 you need a different @code{gdb} compiled for each combination of
35094 host and target. @file{configure} is designed to make this easy by
35095 allowing you to generate each configuration in a separate subdirectory,
35096 rather than in the source directory. If your @code{make} program
35097 handles the @samp{VPATH} feature (@sc{gnu} @code{make} does), running
35098 @code{make} in each of these directories builds the @code{gdb}
35099 program specified there.
35101 To build @code{gdb} in a separate directory, run @file{configure}
35102 with the @samp{--srcdir} option to specify where to find the source.
35103 (You also need to specify a path to find @file{configure}
35104 itself from your working directory. If the path to @file{configure}
35105 would be the same as the argument to @samp{--srcdir}, you can leave out
35106 the @samp{--srcdir} option; it is assumed.)
35108 For example, with version @value{GDBVN}, you can build @value{GDBN} in a
35109 separate directory for a Sun 4 like this:
35113 cd gdb-@value{GDBVN}
35116 ../gdb-@value{GDBVN}/configure sun4
35121 When @file{configure} builds a configuration using a remote source
35122 directory, it creates a tree for the binaries with the same structure
35123 (and using the same names) as the tree under the source directory. In
35124 the example, you'd find the Sun 4 library @file{libiberty.a} in the
35125 directory @file{gdb-sun4/libiberty}, and @value{GDBN} itself in
35126 @file{gdb-sun4/gdb}.
35128 Make sure that your path to the @file{configure} script has just one
35129 instance of @file{gdb} in it. If your path to @file{configure} looks
35130 like @file{../gdb-@value{GDBVN}/gdb/configure}, you are configuring only
35131 one subdirectory of @value{GDBN}, not the whole package. This leads to
35132 build errors about missing include files such as @file{bfd/bfd.h}.
35134 One popular reason to build several @value{GDBN} configurations in separate
35135 directories is to configure @value{GDBN} for cross-compiling (where
35136 @value{GDBN} runs on one machine---the @dfn{host}---while debugging
35137 programs that run on another machine---the @dfn{target}).
35138 You specify a cross-debugging target by
35139 giving the @samp{--target=@var{target}} option to @file{configure}.
35141 When you run @code{make} to build a program or library, you must run
35142 it in a configured directory---whatever directory you were in when you
35143 called @file{configure} (or one of its subdirectories).
35145 The @code{Makefile} that @file{configure} generates in each source
35146 directory also runs recursively. If you type @code{make} in a source
35147 directory such as @file{gdb-@value{GDBVN}} (or in a separate configured
35148 directory configured with @samp{--srcdir=@var{dirname}/gdb-@value{GDBVN}}), you
35149 will build all the required libraries, and then build GDB.
35151 When you have multiple hosts or targets configured in separate
35152 directories, you can run @code{make} on them in parallel (for example,
35153 if they are NFS-mounted on each of the hosts); they will not interfere
35157 @section Specifying Names for Hosts and Targets
35159 The specifications used for hosts and targets in the @file{configure}
35160 script are based on a three-part naming scheme, but some short predefined
35161 aliases are also supported. The full naming scheme encodes three pieces
35162 of information in the following pattern:
35165 @var{architecture}-@var{vendor}-@var{os}
35168 For example, you can use the alias @code{sun4} as a @var{host} argument,
35169 or as the value for @var{target} in a @code{--target=@var{target}}
35170 option. The equivalent full name is @samp{sparc-sun-sunos4}.
35172 The @file{configure} script accompanying @value{GDBN} does not provide
35173 any query facility to list all supported host and target names or
35174 aliases. @file{configure} calls the Bourne shell script
35175 @code{config.sub} to map abbreviations to full names; you can read the
35176 script, if you wish, or you can use it to test your guesses on
35177 abbreviations---for example:
35180 % sh config.sub i386-linux
35182 % sh config.sub alpha-linux
35183 alpha-unknown-linux-gnu
35184 % sh config.sub hp9k700
35186 % sh config.sub sun4
35187 sparc-sun-sunos4.1.1
35188 % sh config.sub sun3
35189 m68k-sun-sunos4.1.1
35190 % sh config.sub i986v
35191 Invalid configuration `i986v': machine `i986v' not recognized
35195 @code{config.sub} is also distributed in the @value{GDBN} source
35196 directory (@file{gdb-@value{GDBVN}}, for version @value{GDBVN}).
35198 @node Configure Options
35199 @section @file{configure} Options
35201 Here is a summary of the @file{configure} options and arguments that
35202 are most often useful for building @value{GDBN}. @file{configure} also has
35203 several other options not listed here. @inforef{What Configure
35204 Does,,configure.info}, for a full explanation of @file{configure}.
35207 configure @r{[}--help@r{]}
35208 @r{[}--prefix=@var{dir}@r{]}
35209 @r{[}--exec-prefix=@var{dir}@r{]}
35210 @r{[}--srcdir=@var{dirname}@r{]}
35211 @r{[}--norecursion@r{]} @r{[}--rm@r{]}
35212 @r{[}--target=@var{target}@r{]}
35217 You may introduce options with a single @samp{-} rather than
35218 @samp{--} if you prefer; but you may abbreviate option names if you use
35223 Display a quick summary of how to invoke @file{configure}.
35225 @item --prefix=@var{dir}
35226 Configure the source to install programs and files under directory
35229 @item --exec-prefix=@var{dir}
35230 Configure the source to install programs under directory
35233 @c avoid splitting the warning from the explanation:
35235 @item --srcdir=@var{dirname}
35236 @strong{Warning: using this option requires @sc{gnu} @code{make}, or another
35237 @code{make} that implements the @code{VPATH} feature.}@*
35238 Use this option to make configurations in directories separate from the
35239 @value{GDBN} source directories. Among other things, you can use this to
35240 build (or maintain) several configurations simultaneously, in separate
35241 directories. @file{configure} writes configuration-specific files in
35242 the current directory, but arranges for them to use the source in the
35243 directory @var{dirname}. @file{configure} creates directories under
35244 the working directory in parallel to the source directories below
35247 @item --norecursion
35248 Configure only the directory level where @file{configure} is executed; do not
35249 propagate configuration to subdirectories.
35251 @item --target=@var{target}
35252 Configure @value{GDBN} for cross-debugging programs running on the specified
35253 @var{target}. Without this option, @value{GDBN} is configured to debug
35254 programs that run on the same machine (@var{host}) as @value{GDBN} itself.
35256 There is no convenient way to generate a list of all available targets.
35258 @item @var{host} @dots{}
35259 Configure @value{GDBN} to run on the specified @var{host}.
35261 There is no convenient way to generate a list of all available hosts.
35264 There are many other options available as well, but they are generally
35265 needed for special purposes only.
35267 @node System-wide configuration
35268 @section System-wide configuration and settings
35269 @cindex system-wide init file
35271 @value{GDBN} can be configured to have a system-wide init file;
35272 this file will be read and executed at startup (@pxref{Startup, , What
35273 @value{GDBN} does during startup}).
35275 Here is the corresponding configure option:
35278 @item --with-system-gdbinit=@var{file}
35279 Specify that the default location of the system-wide init file is
35283 If @value{GDBN} has been configured with the option @option{--prefix=$prefix},
35284 it may be subject to relocation. Two possible cases:
35288 If the default location of this init file contains @file{$prefix},
35289 it will be subject to relocation. Suppose that the configure options
35290 are @option{--prefix=$prefix --with-system-gdbinit=$prefix/etc/gdbinit};
35291 if @value{GDBN} is moved from @file{$prefix} to @file{$install}, the system
35292 init file is looked for as @file{$install/etc/gdbinit} instead of
35293 @file{$prefix/etc/gdbinit}.
35296 By contrast, if the default location does not contain the prefix,
35297 it will not be relocated. E.g.@: if @value{GDBN} has been configured with
35298 @option{--prefix=/usr/local --with-system-gdbinit=/usr/share/gdb/gdbinit},
35299 then @value{GDBN} will always look for @file{/usr/share/gdb/gdbinit},
35300 wherever @value{GDBN} is installed.
35303 If the configured location of the system-wide init file (as given by the
35304 @option{--with-system-gdbinit} option at configure time) is in the
35305 data-directory (as specified by @option{--with-gdb-datadir} at configure
35306 time) or in one of its subdirectories, then @value{GDBN} will look for the
35307 system-wide init file in the directory specified by the
35308 @option{--data-directory} command-line option.
35309 Note that the system-wide init file is only read once, during @value{GDBN}
35310 initialization. If the data-directory is changed after @value{GDBN} has
35311 started with the @code{set data-directory} command, the file will not be
35314 @node Maintenance Commands
35315 @appendix Maintenance Commands
35316 @cindex maintenance commands
35317 @cindex internal commands
35319 In addition to commands intended for @value{GDBN} users, @value{GDBN}
35320 includes a number of commands intended for @value{GDBN} developers,
35321 that are not documented elsewhere in this manual. These commands are
35322 provided here for reference. (For commands that turn on debugging
35323 messages, see @ref{Debugging Output}.)
35326 @kindex maint agent
35327 @kindex maint agent-eval
35328 @item maint agent @r{[}-at @var{location}@r{,}@r{]} @var{expression}
35329 @itemx maint agent-eval @r{[}-at @var{location}@r{,}@r{]} @var{expression}
35330 Translate the given @var{expression} into remote agent bytecodes.
35331 This command is useful for debugging the Agent Expression mechanism
35332 (@pxref{Agent Expressions}). The @samp{agent} version produces an
35333 expression useful for data collection, such as by tracepoints, while
35334 @samp{maint agent-eval} produces an expression that evaluates directly
35335 to a result. For instance, a collection expression for @code{globa +
35336 globb} will include bytecodes to record four bytes of memory at each
35337 of the addresses of @code{globa} and @code{globb}, while discarding
35338 the result of the addition, while an evaluation expression will do the
35339 addition and return the sum.
35340 If @code{-at} is given, generate remote agent bytecode for @var{location}.
35341 If not, generate remote agent bytecode for current frame PC address.
35343 @kindex maint agent-printf
35344 @item maint agent-printf @var{format},@var{expr},...
35345 Translate the given format string and list of argument expressions
35346 into remote agent bytecodes and display them as a disassembled list.
35347 This command is useful for debugging the agent version of dynamic
35348 printf (@pxref{Dynamic Printf}).
35350 @kindex maint info breakpoints
35351 @item @anchor{maint info breakpoints}maint info breakpoints
35352 Using the same format as @samp{info breakpoints}, display both the
35353 breakpoints you've set explicitly, and those @value{GDBN} is using for
35354 internal purposes. Internal breakpoints are shown with negative
35355 breakpoint numbers. The type column identifies what kind of breakpoint
35360 Normal, explicitly set breakpoint.
35363 Normal, explicitly set watchpoint.
35366 Internal breakpoint, used to handle correctly stepping through
35367 @code{longjmp} calls.
35369 @item longjmp resume
35370 Internal breakpoint at the target of a @code{longjmp}.
35373 Temporary internal breakpoint used by the @value{GDBN} @code{until} command.
35376 Temporary internal breakpoint used by the @value{GDBN} @code{finish} command.
35379 Shared library events.
35383 @kindex maint info bfds
35384 @item maint info bfds
35385 This prints information about each @code{bfd} object that is known to
35386 @value{GDBN}. @xref{Top, , BFD, bfd, The Binary File Descriptor Library}.
35388 @kindex set displaced-stepping
35389 @kindex show displaced-stepping
35390 @cindex displaced stepping support
35391 @cindex out-of-line single-stepping
35392 @item set displaced-stepping
35393 @itemx show displaced-stepping
35394 Control whether or not @value{GDBN} will do @dfn{displaced stepping}
35395 if the target supports it. Displaced stepping is a way to single-step
35396 over breakpoints without removing them from the inferior, by executing
35397 an out-of-line copy of the instruction that was originally at the
35398 breakpoint location. It is also known as out-of-line single-stepping.
35401 @item set displaced-stepping on
35402 If the target architecture supports it, @value{GDBN} will use
35403 displaced stepping to step over breakpoints.
35405 @item set displaced-stepping off
35406 @value{GDBN} will not use displaced stepping to step over breakpoints,
35407 even if such is supported by the target architecture.
35409 @cindex non-stop mode, and @samp{set displaced-stepping}
35410 @item set displaced-stepping auto
35411 This is the default mode. @value{GDBN} will use displaced stepping
35412 only if non-stop mode is active (@pxref{Non-Stop Mode}) and the target
35413 architecture supports displaced stepping.
35416 @kindex maint check-symtabs
35417 @item maint check-symtabs
35418 Check the consistency of psymtabs and symtabs.
35420 @kindex maint cplus first_component
35421 @item maint cplus first_component @var{name}
35422 Print the first C@t{++} class/namespace component of @var{name}.
35424 @kindex maint cplus namespace
35425 @item maint cplus namespace
35426 Print the list of possible C@t{++} namespaces.
35428 @kindex maint demangle
35429 @item maint demangle @var{name}
35430 Demangle a C@t{++} or Objective-C mangled @var{name}.
35432 @kindex maint deprecate
35433 @kindex maint undeprecate
35434 @cindex deprecated commands
35435 @item maint deprecate @var{command} @r{[}@var{replacement}@r{]}
35436 @itemx maint undeprecate @var{command}
35437 Deprecate or undeprecate the named @var{command}. Deprecated commands
35438 cause @value{GDBN} to issue a warning when you use them. The optional
35439 argument @var{replacement} says which newer command should be used in
35440 favor of the deprecated one; if it is given, @value{GDBN} will mention
35441 the replacement as part of the warning.
35443 @kindex maint dump-me
35444 @item maint dump-me
35445 @cindex @code{SIGQUIT} signal, dump core of @value{GDBN}
35446 Cause a fatal signal in the debugger and force it to dump its core.
35447 This is supported only on systems which support aborting a program
35448 with the @code{SIGQUIT} signal.
35450 @kindex maint internal-error
35451 @kindex maint internal-warning
35452 @item maint internal-error @r{[}@var{message-text}@r{]}
35453 @itemx maint internal-warning @r{[}@var{message-text}@r{]}
35454 Cause @value{GDBN} to call the internal function @code{internal_error}
35455 or @code{internal_warning} and hence behave as though an internal error
35456 or internal warning has been detected. In addition to reporting the
35457 internal problem, these functions give the user the opportunity to
35458 either quit @value{GDBN} or create a core file of the current
35459 @value{GDBN} session.
35461 These commands take an optional parameter @var{message-text} that is
35462 used as the text of the error or warning message.
35464 Here's an example of using @code{internal-error}:
35467 (@value{GDBP}) @kbd{maint internal-error testing, 1, 2}
35468 @dots{}/maint.c:121: internal-error: testing, 1, 2
35469 A problem internal to GDB has been detected. Further
35470 debugging may prove unreliable.
35471 Quit this debugging session? (y or n) @kbd{n}
35472 Create a core file? (y or n) @kbd{n}
35476 @cindex @value{GDBN} internal error
35477 @cindex internal errors, control of @value{GDBN} behavior
35479 @kindex maint set internal-error
35480 @kindex maint show internal-error
35481 @kindex maint set internal-warning
35482 @kindex maint show internal-warning
35483 @item maint set internal-error @var{action} [ask|yes|no]
35484 @itemx maint show internal-error @var{action}
35485 @itemx maint set internal-warning @var{action} [ask|yes|no]
35486 @itemx maint show internal-warning @var{action}
35487 When @value{GDBN} reports an internal problem (error or warning) it
35488 gives the user the opportunity to both quit @value{GDBN} and create a
35489 core file of the current @value{GDBN} session. These commands let you
35490 override the default behaviour for each particular @var{action},
35491 described in the table below.
35495 You can specify that @value{GDBN} should always (yes) or never (no)
35496 quit. The default is to ask the user what to do.
35499 You can specify that @value{GDBN} should always (yes) or never (no)
35500 create a core file. The default is to ask the user what to do.
35503 @kindex maint packet
35504 @item maint packet @var{text}
35505 If @value{GDBN} is talking to an inferior via the serial protocol,
35506 then this command sends the string @var{text} to the inferior, and
35507 displays the response packet. @value{GDBN} supplies the initial
35508 @samp{$} character, the terminating @samp{#} character, and the
35511 @kindex maint print architecture
35512 @item maint print architecture @r{[}@var{file}@r{]}
35513 Print the entire architecture configuration. The optional argument
35514 @var{file} names the file where the output goes.
35516 @kindex maint print c-tdesc
35517 @item maint print c-tdesc
35518 Print the current target description (@pxref{Target Descriptions}) as
35519 a C source file. The created source file can be used in @value{GDBN}
35520 when an XML parser is not available to parse the description.
35522 @kindex maint print dummy-frames
35523 @item maint print dummy-frames
35524 Prints the contents of @value{GDBN}'s internal dummy-frame stack.
35527 (@value{GDBP}) @kbd{b add}
35529 (@value{GDBP}) @kbd{print add(2,3)}
35530 Breakpoint 2, add (a=2, b=3) at @dots{}
35532 The program being debugged stopped while in a function called from GDB.
35534 (@value{GDBP}) @kbd{maint print dummy-frames}
35535 0x1a57c80: pc=0x01014068 fp=0x0200bddc sp=0x0200bdd6
35536 top=0x0200bdd4 id=@{stack=0x200bddc,code=0x101405c@}
35537 call_lo=0x01014000 call_hi=0x01014001
35541 Takes an optional file parameter.
35543 @kindex maint print registers
35544 @kindex maint print raw-registers
35545 @kindex maint print cooked-registers
35546 @kindex maint print register-groups
35547 @kindex maint print remote-registers
35548 @item maint print registers @r{[}@var{file}@r{]}
35549 @itemx maint print raw-registers @r{[}@var{file}@r{]}
35550 @itemx maint print cooked-registers @r{[}@var{file}@r{]}
35551 @itemx maint print register-groups @r{[}@var{file}@r{]}
35552 @itemx maint print remote-registers @r{[}@var{file}@r{]}
35553 Print @value{GDBN}'s internal register data structures.
35555 The command @code{maint print raw-registers} includes the contents of
35556 the raw register cache; the command @code{maint print
35557 cooked-registers} includes the (cooked) value of all registers,
35558 including registers which aren't available on the target nor visible
35559 to user; the command @code{maint print register-groups} includes the
35560 groups that each register is a member of; and the command @code{maint
35561 print remote-registers} includes the remote target's register numbers
35562 and offsets in the `G' packets. @xref{Registers,, Registers, gdbint,
35563 @value{GDBN} Internals}.
35565 These commands take an optional parameter, a file name to which to
35566 write the information.
35568 @kindex maint print reggroups
35569 @item maint print reggroups @r{[}@var{file}@r{]}
35570 Print @value{GDBN}'s internal register group data structures. The
35571 optional argument @var{file} tells to what file to write the
35574 The register groups info looks like this:
35577 (@value{GDBP}) @kbd{maint print reggroups}
35590 This command forces @value{GDBN} to flush its internal register cache.
35592 @kindex maint print objfiles
35593 @cindex info for known object files
35594 @item maint print objfiles
35595 Print a dump of all known object files. For each object file, this
35596 command prints its name, address in memory, and all of its psymtabs
35599 @kindex maint print section-scripts
35600 @cindex info for known .debug_gdb_scripts-loaded scripts
35601 @item maint print section-scripts [@var{regexp}]
35602 Print a dump of scripts specified in the @code{.debug_gdb_section} section.
35603 If @var{regexp} is specified, only print scripts loaded by object files
35604 matching @var{regexp}.
35605 For each script, this command prints its name as specified in the objfile,
35606 and the full path if known.
35607 @xref{dotdebug_gdb_scripts section}.
35609 @kindex maint print statistics
35610 @cindex bcache statistics
35611 @item maint print statistics
35612 This command prints, for each object file in the program, various data
35613 about that object file followed by the byte cache (@dfn{bcache})
35614 statistics for the object file. The objfile data includes the number
35615 of minimal, partial, full, and stabs symbols, the number of types
35616 defined by the objfile, the number of as yet unexpanded psym tables,
35617 the number of line tables and string tables, and the amount of memory
35618 used by the various tables. The bcache statistics include the counts,
35619 sizes, and counts of duplicates of all and unique objects, max,
35620 average, and median entry size, total memory used and its overhead and
35621 savings, and various measures of the hash table size and chain
35624 @kindex maint print target-stack
35625 @cindex target stack description
35626 @item maint print target-stack
35627 A @dfn{target} is an interface between the debugger and a particular
35628 kind of file or process. Targets can be stacked in @dfn{strata},
35629 so that more than one target can potentially respond to a request.
35630 In particular, memory accesses will walk down the stack of targets
35631 until they find a target that is interested in handling that particular
35634 This command prints a short description of each layer that was pushed on
35635 the @dfn{target stack}, starting from the top layer down to the bottom one.
35637 @kindex maint print type
35638 @cindex type chain of a data type
35639 @item maint print type @var{expr}
35640 Print the type chain for a type specified by @var{expr}. The argument
35641 can be either a type name or a symbol. If it is a symbol, the type of
35642 that symbol is described. The type chain produced by this command is
35643 a recursive definition of the data type as stored in @value{GDBN}'s
35644 data structures, including its flags and contained types.
35646 @kindex maint set dwarf2 always-disassemble
35647 @kindex maint show dwarf2 always-disassemble
35648 @item maint set dwarf2 always-disassemble
35649 @item maint show dwarf2 always-disassemble
35650 Control the behavior of @code{info address} when using DWARF debugging
35653 The default is @code{off}, which means that @value{GDBN} should try to
35654 describe a variable's location in an easily readable format. When
35655 @code{on}, @value{GDBN} will instead display the DWARF location
35656 expression in an assembly-like format. Note that some locations are
35657 too complex for @value{GDBN} to describe simply; in this case you will
35658 always see the disassembly form.
35660 Here is an example of the resulting disassembly:
35663 (gdb) info addr argc
35664 Symbol "argc" is a complex DWARF expression:
35668 For more information on these expressions, see
35669 @uref{http://www.dwarfstd.org/, the DWARF standard}.
35671 @kindex maint set dwarf2 max-cache-age
35672 @kindex maint show dwarf2 max-cache-age
35673 @item maint set dwarf2 max-cache-age
35674 @itemx maint show dwarf2 max-cache-age
35675 Control the DWARF 2 compilation unit cache.
35677 @cindex DWARF 2 compilation units cache
35678 In object files with inter-compilation-unit references, such as those
35679 produced by the GCC option @samp{-feliminate-dwarf2-dups}, the DWARF 2
35680 reader needs to frequently refer to previously read compilation units.
35681 This setting controls how long a compilation unit will remain in the
35682 cache if it is not referenced. A higher limit means that cached
35683 compilation units will be stored in memory longer, and more total
35684 memory will be used. Setting it to zero disables caching, which will
35685 slow down @value{GDBN} startup, but reduce memory consumption.
35687 @kindex maint set profile
35688 @kindex maint show profile
35689 @cindex profiling GDB
35690 @item maint set profile
35691 @itemx maint show profile
35692 Control profiling of @value{GDBN}.
35694 Profiling will be disabled until you use the @samp{maint set profile}
35695 command to enable it. When you enable profiling, the system will begin
35696 collecting timing and execution count data; when you disable profiling or
35697 exit @value{GDBN}, the results will be written to a log file. Remember that
35698 if you use profiling, @value{GDBN} will overwrite the profiling log file
35699 (often called @file{gmon.out}). If you have a record of important profiling
35700 data in a @file{gmon.out} file, be sure to move it to a safe location.
35702 Configuring with @samp{--enable-profiling} arranges for @value{GDBN} to be
35703 compiled with the @samp{-pg} compiler option.
35705 @kindex maint set show-debug-regs
35706 @kindex maint show show-debug-regs
35707 @cindex hardware debug registers
35708 @item maint set show-debug-regs
35709 @itemx maint show show-debug-regs
35710 Control whether to show variables that mirror the hardware debug
35711 registers. Use @code{ON} to enable, @code{OFF} to disable. If
35712 enabled, the debug registers values are shown when @value{GDBN} inserts or
35713 removes a hardware breakpoint or watchpoint, and when the inferior
35714 triggers a hardware-assisted breakpoint or watchpoint.
35716 @kindex maint set show-all-tib
35717 @kindex maint show show-all-tib
35718 @item maint set show-all-tib
35719 @itemx maint show show-all-tib
35720 Control whether to show all non zero areas within a 1k block starting
35721 at thread local base, when using the @samp{info w32 thread-information-block}
35724 @kindex maint space
35725 @cindex memory used by commands
35727 Control whether to display memory usage for each command. If set to a
35728 nonzero value, @value{GDBN} will display how much memory each command
35729 took, following the command's own output. This can also be requested
35730 by invoking @value{GDBN} with the @option{--statistics} command-line
35731 switch (@pxref{Mode Options}).
35734 @cindex time of command execution
35736 Control whether to display the execution time of @value{GDBN} for each command.
35737 If set to a nonzero value, @value{GDBN} will display how much time it
35738 took to execute each command, following the command's own output.
35739 Both CPU time and wallclock time are printed.
35740 Printing both is useful when trying to determine whether the cost is
35741 CPU or, e.g., disk/network, latency.
35742 Note that the CPU time printed is for @value{GDBN} only, it does not include
35743 the execution time of the inferior because there's no mechanism currently
35744 to compute how much time was spent by @value{GDBN} and how much time was
35745 spent by the program been debugged.
35746 This can also be requested by invoking @value{GDBN} with the
35747 @option{--statistics} command-line switch (@pxref{Mode Options}).
35749 @kindex maint translate-address
35750 @item maint translate-address @r{[}@var{section}@r{]} @var{addr}
35751 Find the symbol stored at the location specified by the address
35752 @var{addr} and an optional section name @var{section}. If found,
35753 @value{GDBN} prints the name of the closest symbol and an offset from
35754 the symbol's location to the specified address. This is similar to
35755 the @code{info address} command (@pxref{Symbols}), except that this
35756 command also allows to find symbols in other sections.
35758 If section was not specified, the section in which the symbol was found
35759 is also printed. For dynamically linked executables, the name of
35760 executable or shared library containing the symbol is printed as well.
35764 The following command is useful for non-interactive invocations of
35765 @value{GDBN}, such as in the test suite.
35768 @item set watchdog @var{nsec}
35769 @kindex set watchdog
35770 @cindex watchdog timer
35771 @cindex timeout for commands
35772 Set the maximum number of seconds @value{GDBN} will wait for the
35773 target operation to finish. If this time expires, @value{GDBN}
35774 reports and error and the command is aborted.
35776 @item show watchdog
35777 Show the current setting of the target wait timeout.
35780 @node Remote Protocol
35781 @appendix @value{GDBN} Remote Serial Protocol
35786 * Stop Reply Packets::
35787 * General Query Packets::
35788 * Architecture-Specific Protocol Details::
35789 * Tracepoint Packets::
35790 * Host I/O Packets::
35792 * Notification Packets::
35793 * Remote Non-Stop::
35794 * Packet Acknowledgment::
35796 * File-I/O Remote Protocol Extension::
35797 * Library List Format::
35798 * Library List Format for SVR4 Targets::
35799 * Memory Map Format::
35800 * Thread List Format::
35801 * Traceframe Info Format::
35802 * Branch Trace Format::
35808 There may be occasions when you need to know something about the
35809 protocol---for example, if there is only one serial port to your target
35810 machine, you might want your program to do something special if it
35811 recognizes a packet meant for @value{GDBN}.
35813 In the examples below, @samp{->} and @samp{<-} are used to indicate
35814 transmitted and received data, respectively.
35816 @cindex protocol, @value{GDBN} remote serial
35817 @cindex serial protocol, @value{GDBN} remote
35818 @cindex remote serial protocol
35819 All @value{GDBN} commands and responses (other than acknowledgments
35820 and notifications, see @ref{Notification Packets}) are sent as a
35821 @var{packet}. A @var{packet} is introduced with the character
35822 @samp{$}, the actual @var{packet-data}, and the terminating character
35823 @samp{#} followed by a two-digit @var{checksum}:
35826 @code{$}@var{packet-data}@code{#}@var{checksum}
35830 @cindex checksum, for @value{GDBN} remote
35832 The two-digit @var{checksum} is computed as the modulo 256 sum of all
35833 characters between the leading @samp{$} and the trailing @samp{#} (an
35834 eight bit unsigned checksum).
35836 Implementors should note that prior to @value{GDBN} 5.0 the protocol
35837 specification also included an optional two-digit @var{sequence-id}:
35840 @code{$}@var{sequence-id}@code{:}@var{packet-data}@code{#}@var{checksum}
35843 @cindex sequence-id, for @value{GDBN} remote
35845 That @var{sequence-id} was appended to the acknowledgment. @value{GDBN}
35846 has never output @var{sequence-id}s. Stubs that handle packets added
35847 since @value{GDBN} 5.0 must not accept @var{sequence-id}.
35849 When either the host or the target machine receives a packet, the first
35850 response expected is an acknowledgment: either @samp{+} (to indicate
35851 the package was received correctly) or @samp{-} (to request
35855 -> @code{$}@var{packet-data}@code{#}@var{checksum}
35860 The @samp{+}/@samp{-} acknowledgments can be disabled
35861 once a connection is established.
35862 @xref{Packet Acknowledgment}, for details.
35864 The host (@value{GDBN}) sends @var{command}s, and the target (the
35865 debugging stub incorporated in your program) sends a @var{response}. In
35866 the case of step and continue @var{command}s, the response is only sent
35867 when the operation has completed, and the target has again stopped all
35868 threads in all attached processes. This is the default all-stop mode
35869 behavior, but the remote protocol also supports @value{GDBN}'s non-stop
35870 execution mode; see @ref{Remote Non-Stop}, for details.
35872 @var{packet-data} consists of a sequence of characters with the
35873 exception of @samp{#} and @samp{$} (see @samp{X} packet for additional
35876 @cindex remote protocol, field separator
35877 Fields within the packet should be separated using @samp{,} @samp{;} or
35878 @samp{:}. Except where otherwise noted all numbers are represented in
35879 @sc{hex} with leading zeros suppressed.
35881 Implementors should note that prior to @value{GDBN} 5.0, the character
35882 @samp{:} could not appear as the third character in a packet (as it
35883 would potentially conflict with the @var{sequence-id}).
35885 @cindex remote protocol, binary data
35886 @anchor{Binary Data}
35887 Binary data in most packets is encoded either as two hexadecimal
35888 digits per byte of binary data. This allowed the traditional remote
35889 protocol to work over connections which were only seven-bit clean.
35890 Some packets designed more recently assume an eight-bit clean
35891 connection, and use a more efficient encoding to send and receive
35894 The binary data representation uses @code{7d} (@sc{ascii} @samp{@}})
35895 as an escape character. Any escaped byte is transmitted as the escape
35896 character followed by the original character XORed with @code{0x20}.
35897 For example, the byte @code{0x7d} would be transmitted as the two
35898 bytes @code{0x7d 0x5d}. The bytes @code{0x23} (@sc{ascii} @samp{#}),
35899 @code{0x24} (@sc{ascii} @samp{$}), and @code{0x7d} (@sc{ascii}
35900 @samp{@}}) must always be escaped. Responses sent by the stub
35901 must also escape @code{0x2a} (@sc{ascii} @samp{*}), so that it
35902 is not interpreted as the start of a run-length encoded sequence
35905 Response @var{data} can be run-length encoded to save space.
35906 Run-length encoding replaces runs of identical characters with one
35907 instance of the repeated character, followed by a @samp{*} and a
35908 repeat count. The repeat count is itself sent encoded, to avoid
35909 binary characters in @var{data}: a value of @var{n} is sent as
35910 @code{@var{n}+29}. For a repeat count greater or equal to 3, this
35911 produces a printable @sc{ascii} character, e.g.@: a space (@sc{ascii}
35912 code 32) for a repeat count of 3. (This is because run-length
35913 encoding starts to win for counts 3 or more.) Thus, for example,
35914 @samp{0* } is a run-length encoding of ``0000'': the space character
35915 after @samp{*} means repeat the leading @code{0} @w{@code{32 - 29 =
35918 The printable characters @samp{#} and @samp{$} or with a numeric value
35919 greater than 126 must not be used. Runs of six repeats (@samp{#}) or
35920 seven repeats (@samp{$}) can be expanded using a repeat count of only
35921 five (@samp{"}). For example, @samp{00000000} can be encoded as
35924 The error response returned for some packets includes a two character
35925 error number. That number is not well defined.
35927 @cindex empty response, for unsupported packets
35928 For any @var{command} not supported by the stub, an empty response
35929 (@samp{$#00}) should be returned. That way it is possible to extend the
35930 protocol. A newer @value{GDBN} can tell if a packet is supported based
35933 At a minimum, a stub is required to support the @samp{g} and @samp{G}
35934 commands for register access, and the @samp{m} and @samp{M} commands
35935 for memory access. Stubs that only control single-threaded targets
35936 can implement run control with the @samp{c} (continue), and @samp{s}
35937 (step) commands. Stubs that support multi-threading targets should
35938 support the @samp{vCont} command. All other commands are optional.
35943 The following table provides a complete list of all currently defined
35944 @var{command}s and their corresponding response @var{data}.
35945 @xref{File-I/O Remote Protocol Extension}, for details about the File
35946 I/O extension of the remote protocol.
35948 Each packet's description has a template showing the packet's overall
35949 syntax, followed by an explanation of the packet's meaning. We
35950 include spaces in some of the templates for clarity; these are not
35951 part of the packet's syntax. No @value{GDBN} packet uses spaces to
35952 separate its components. For example, a template like @samp{foo
35953 @var{bar} @var{baz}} describes a packet beginning with the three ASCII
35954 bytes @samp{foo}, followed by a @var{bar}, followed directly by a
35955 @var{baz}. @value{GDBN} does not transmit a space character between the
35956 @samp{foo} and the @var{bar}, or between the @var{bar} and the
35959 @cindex @var{thread-id}, in remote protocol
35960 @anchor{thread-id syntax}
35961 Several packets and replies include a @var{thread-id} field to identify
35962 a thread. Normally these are positive numbers with a target-specific
35963 interpretation, formatted as big-endian hex strings. A @var{thread-id}
35964 can also be a literal @samp{-1} to indicate all threads, or @samp{0} to
35967 In addition, the remote protocol supports a multiprocess feature in
35968 which the @var{thread-id} syntax is extended to optionally include both
35969 process and thread ID fields, as @samp{p@var{pid}.@var{tid}}.
35970 The @var{pid} (process) and @var{tid} (thread) components each have the
35971 format described above: a positive number with target-specific
35972 interpretation formatted as a big-endian hex string, literal @samp{-1}
35973 to indicate all processes or threads (respectively), or @samp{0} to
35974 indicate an arbitrary process or thread. Specifying just a process, as
35975 @samp{p@var{pid}}, is equivalent to @samp{p@var{pid}.-1}. It is an
35976 error to specify all processes but a specific thread, such as
35977 @samp{p-1.@var{tid}}. Note that the @samp{p} prefix is @emph{not} used
35978 for those packets and replies explicitly documented to include a process
35979 ID, rather than a @var{thread-id}.
35981 The multiprocess @var{thread-id} syntax extensions are only used if both
35982 @value{GDBN} and the stub report support for the @samp{multiprocess}
35983 feature using @samp{qSupported}. @xref{multiprocess extensions}, for
35986 Note that all packet forms beginning with an upper- or lower-case
35987 letter, other than those described here, are reserved for future use.
35989 Here are the packet descriptions.
35994 @cindex @samp{!} packet
35995 @anchor{extended mode}
35996 Enable extended mode. In extended mode, the remote server is made
35997 persistent. The @samp{R} packet is used to restart the program being
36003 The remote target both supports and has enabled extended mode.
36007 @cindex @samp{?} packet
36008 Indicate the reason the target halted. The reply is the same as for
36009 step and continue. This packet has a special interpretation when the
36010 target is in non-stop mode; see @ref{Remote Non-Stop}.
36013 @xref{Stop Reply Packets}, for the reply specifications.
36015 @item A @var{arglen},@var{argnum},@var{arg},@dots{}
36016 @cindex @samp{A} packet
36017 Initialized @code{argv[]} array passed into program. @var{arglen}
36018 specifies the number of bytes in the hex encoded byte stream
36019 @var{arg}. See @code{gdbserver} for more details.
36024 The arguments were set.
36030 @cindex @samp{b} packet
36031 (Don't use this packet; its behavior is not well-defined.)
36032 Change the serial line speed to @var{baud}.
36034 JTC: @emph{When does the transport layer state change? When it's
36035 received, or after the ACK is transmitted. In either case, there are
36036 problems if the command or the acknowledgment packet is dropped.}
36038 Stan: @emph{If people really wanted to add something like this, and get
36039 it working for the first time, they ought to modify ser-unix.c to send
36040 some kind of out-of-band message to a specially-setup stub and have the
36041 switch happen "in between" packets, so that from remote protocol's point
36042 of view, nothing actually happened.}
36044 @item B @var{addr},@var{mode}
36045 @cindex @samp{B} packet
36046 Set (@var{mode} is @samp{S}) or clear (@var{mode} is @samp{C}) a
36047 breakpoint at @var{addr}.
36049 Don't use this packet. Use the @samp{Z} and @samp{z} packets instead
36050 (@pxref{insert breakpoint or watchpoint packet}).
36052 @cindex @samp{bc} packet
36055 Backward continue. Execute the target system in reverse. No parameter.
36056 @xref{Reverse Execution}, for more information.
36059 @xref{Stop Reply Packets}, for the reply specifications.
36061 @cindex @samp{bs} packet
36064 Backward single step. Execute one instruction in reverse. No parameter.
36065 @xref{Reverse Execution}, for more information.
36068 @xref{Stop Reply Packets}, for the reply specifications.
36070 @item c @r{[}@var{addr}@r{]}
36071 @cindex @samp{c} packet
36072 Continue. @var{addr} is address to resume. If @var{addr} is omitted,
36073 resume at current address.
36075 This packet is deprecated for multi-threading support. @xref{vCont
36079 @xref{Stop Reply Packets}, for the reply specifications.
36081 @item C @var{sig}@r{[};@var{addr}@r{]}
36082 @cindex @samp{C} packet
36083 Continue with signal @var{sig} (hex signal number). If
36084 @samp{;@var{addr}} is omitted, resume at same address.
36086 This packet is deprecated for multi-threading support. @xref{vCont
36090 @xref{Stop Reply Packets}, for the reply specifications.
36093 @cindex @samp{d} packet
36096 Don't use this packet; instead, define a general set packet
36097 (@pxref{General Query Packets}).
36101 @cindex @samp{D} packet
36102 The first form of the packet is used to detach @value{GDBN} from the
36103 remote system. It is sent to the remote target
36104 before @value{GDBN} disconnects via the @code{detach} command.
36106 The second form, including a process ID, is used when multiprocess
36107 protocol extensions are enabled (@pxref{multiprocess extensions}), to
36108 detach only a specific process. The @var{pid} is specified as a
36109 big-endian hex string.
36119 @item F @var{RC},@var{EE},@var{CF};@var{XX}
36120 @cindex @samp{F} packet
36121 A reply from @value{GDBN} to an @samp{F} packet sent by the target.
36122 This is part of the File-I/O protocol extension. @xref{File-I/O
36123 Remote Protocol Extension}, for the specification.
36126 @anchor{read registers packet}
36127 @cindex @samp{g} packet
36128 Read general registers.
36132 @item @var{XX@dots{}}
36133 Each byte of register data is described by two hex digits. The bytes
36134 with the register are transmitted in target byte order. The size of
36135 each register and their position within the @samp{g} packet are
36136 determined by the @value{GDBN} internal gdbarch functions
36137 @code{DEPRECATED_REGISTER_RAW_SIZE} and @code{gdbarch_register_name}. The
36138 specification of several standard @samp{g} packets is specified below.
36140 When reading registers from a trace frame (@pxref{Analyze Collected
36141 Data,,Using the Collected Data}), the stub may also return a string of
36142 literal @samp{x}'s in place of the register data digits, to indicate
36143 that the corresponding register has not been collected, thus its value
36144 is unavailable. For example, for an architecture with 4 registers of
36145 4 bytes each, the following reply indicates to @value{GDBN} that
36146 registers 0 and 2 have not been collected, while registers 1 and 3
36147 have been collected, and both have zero value:
36151 <- @code{xxxxxxxx00000000xxxxxxxx00000000}
36158 @item G @var{XX@dots{}}
36159 @cindex @samp{G} packet
36160 Write general registers. @xref{read registers packet}, for a
36161 description of the @var{XX@dots{}} data.
36171 @item H @var{op} @var{thread-id}
36172 @cindex @samp{H} packet
36173 Set thread for subsequent operations (@samp{m}, @samp{M}, @samp{g},
36174 @samp{G}, et.al.). @var{op} depends on the operation to be performed:
36175 it should be @samp{c} for step and continue operations (note that this
36176 is deprecated, supporting the @samp{vCont} command is a better
36177 option), @samp{g} for other operations. The thread designator
36178 @var{thread-id} has the format and interpretation described in
36179 @ref{thread-id syntax}.
36190 @c 'H': How restrictive (or permissive) is the thread model. If a
36191 @c thread is selected and stopped, are other threads allowed
36192 @c to continue to execute? As I mentioned above, I think the
36193 @c semantics of each command when a thread is selected must be
36194 @c described. For example:
36196 @c 'g': If the stub supports threads and a specific thread is
36197 @c selected, returns the register block from that thread;
36198 @c otherwise returns current registers.
36200 @c 'G' If the stub supports threads and a specific thread is
36201 @c selected, sets the registers of the register block of
36202 @c that thread; otherwise sets current registers.
36204 @item i @r{[}@var{addr}@r{[},@var{nnn}@r{]]}
36205 @anchor{cycle step packet}
36206 @cindex @samp{i} packet
36207 Step the remote target by a single clock cycle. If @samp{,@var{nnn}} is
36208 present, cycle step @var{nnn} cycles. If @var{addr} is present, cycle
36209 step starting at that address.
36212 @cindex @samp{I} packet
36213 Signal, then cycle step. @xref{step with signal packet}. @xref{cycle
36217 @cindex @samp{k} packet
36220 FIXME: @emph{There is no description of how to operate when a specific
36221 thread context has been selected (i.e.@: does 'k' kill only that
36224 @item m @var{addr},@var{length}
36225 @cindex @samp{m} packet
36226 Read @var{length} bytes of memory starting at address @var{addr}.
36227 Note that @var{addr} may not be aligned to any particular boundary.
36229 The stub need not use any particular size or alignment when gathering
36230 data from memory for the response; even if @var{addr} is word-aligned
36231 and @var{length} is a multiple of the word size, the stub is free to
36232 use byte accesses, or not. For this reason, this packet may not be
36233 suitable for accessing memory-mapped I/O devices.
36234 @cindex alignment of remote memory accesses
36235 @cindex size of remote memory accesses
36236 @cindex memory, alignment and size of remote accesses
36240 @item @var{XX@dots{}}
36241 Memory contents; each byte is transmitted as a two-digit hexadecimal
36242 number. The reply may contain fewer bytes than requested if the
36243 server was able to read only part of the region of memory.
36248 @item M @var{addr},@var{length}:@var{XX@dots{}}
36249 @cindex @samp{M} packet
36250 Write @var{length} bytes of memory starting at address @var{addr}.
36251 @var{XX@dots{}} is the data; each byte is transmitted as a two-digit
36252 hexadecimal number.
36259 for an error (this includes the case where only part of the data was
36264 @cindex @samp{p} packet
36265 Read the value of register @var{n}; @var{n} is in hex.
36266 @xref{read registers packet}, for a description of how the returned
36267 register value is encoded.
36271 @item @var{XX@dots{}}
36272 the register's value
36276 Indicating an unrecognized @var{query}.
36279 @item P @var{n@dots{}}=@var{r@dots{}}
36280 @anchor{write register packet}
36281 @cindex @samp{P} packet
36282 Write register @var{n@dots{}} with value @var{r@dots{}}. The register
36283 number @var{n} is in hexadecimal, and @var{r@dots{}} contains two hex
36284 digits for each byte in the register (target byte order).
36294 @item q @var{name} @var{params}@dots{}
36295 @itemx Q @var{name} @var{params}@dots{}
36296 @cindex @samp{q} packet
36297 @cindex @samp{Q} packet
36298 General query (@samp{q}) and set (@samp{Q}). These packets are
36299 described fully in @ref{General Query Packets}.
36302 @cindex @samp{r} packet
36303 Reset the entire system.
36305 Don't use this packet; use the @samp{R} packet instead.
36308 @cindex @samp{R} packet
36309 Restart the program being debugged. @var{XX}, while needed, is ignored.
36310 This packet is only available in extended mode (@pxref{extended mode}).
36312 The @samp{R} packet has no reply.
36314 @item s @r{[}@var{addr}@r{]}
36315 @cindex @samp{s} packet
36316 Single step. @var{addr} is the address at which to resume. If
36317 @var{addr} is omitted, resume at same address.
36319 This packet is deprecated for multi-threading support. @xref{vCont
36323 @xref{Stop Reply Packets}, for the reply specifications.
36325 @item S @var{sig}@r{[};@var{addr}@r{]}
36326 @anchor{step with signal packet}
36327 @cindex @samp{S} packet
36328 Step with signal. This is analogous to the @samp{C} packet, but
36329 requests a single-step, rather than a normal resumption of execution.
36331 This packet is deprecated for multi-threading support. @xref{vCont
36335 @xref{Stop Reply Packets}, for the reply specifications.
36337 @item t @var{addr}:@var{PP},@var{MM}
36338 @cindex @samp{t} packet
36339 Search backwards starting at address @var{addr} for a match with pattern
36340 @var{PP} and mask @var{MM}. @var{PP} and @var{MM} are 4 bytes.
36341 @var{addr} must be at least 3 digits.
36343 @item T @var{thread-id}
36344 @cindex @samp{T} packet
36345 Find out if the thread @var{thread-id} is alive. @xref{thread-id syntax}.
36350 thread is still alive
36356 Packets starting with @samp{v} are identified by a multi-letter name,
36357 up to the first @samp{;} or @samp{?} (or the end of the packet).
36359 @item vAttach;@var{pid}
36360 @cindex @samp{vAttach} packet
36361 Attach to a new process with the specified process ID @var{pid}.
36362 The process ID is a
36363 hexadecimal integer identifying the process. In all-stop mode, all
36364 threads in the attached process are stopped; in non-stop mode, it may be
36365 attached without being stopped if that is supported by the target.
36367 @c In non-stop mode, on a successful vAttach, the stub should set the
36368 @c current thread to a thread of the newly-attached process. After
36369 @c attaching, GDB queries for the attached process's thread ID with qC.
36370 @c Also note that, from a user perspective, whether or not the
36371 @c target is stopped on attach in non-stop mode depends on whether you
36372 @c use the foreground or background version of the attach command, not
36373 @c on what vAttach does; GDB does the right thing with respect to either
36374 @c stopping or restarting threads.
36376 This packet is only available in extended mode (@pxref{extended mode}).
36382 @item @r{Any stop packet}
36383 for success in all-stop mode (@pxref{Stop Reply Packets})
36385 for success in non-stop mode (@pxref{Remote Non-Stop})
36388 @item vCont@r{[};@var{action}@r{[}:@var{thread-id}@r{]]}@dots{}
36389 @cindex @samp{vCont} packet
36390 @anchor{vCont packet}
36391 Resume the inferior, specifying different actions for each thread.
36392 If an action is specified with no @var{thread-id}, then it is applied to any
36393 threads that don't have a specific action specified; if no default action is
36394 specified then other threads should remain stopped in all-stop mode and
36395 in their current state in non-stop mode.
36396 Specifying multiple
36397 default actions is an error; specifying no actions is also an error.
36398 Thread IDs are specified using the syntax described in @ref{thread-id syntax}.
36400 Currently supported actions are:
36406 Continue with signal @var{sig}. The signal @var{sig} should be two hex digits.
36410 Step with signal @var{sig}. The signal @var{sig} should be two hex digits.
36415 The optional argument @var{addr} normally associated with the
36416 @samp{c}, @samp{C}, @samp{s}, and @samp{S} packets is
36417 not supported in @samp{vCont}.
36419 The @samp{t} action is only relevant in non-stop mode
36420 (@pxref{Remote Non-Stop}) and may be ignored by the stub otherwise.
36421 A stop reply should be generated for any affected thread not already stopped.
36422 When a thread is stopped by means of a @samp{t} action,
36423 the corresponding stop reply should indicate that the thread has stopped with
36424 signal @samp{0}, regardless of whether the target uses some other signal
36425 as an implementation detail.
36427 The stub must support @samp{vCont} if it reports support for
36428 multiprocess extensions (@pxref{multiprocess extensions}). Note that in
36429 this case @samp{vCont} actions can be specified to apply to all threads
36430 in a process by using the @samp{p@var{pid}.-1} form of the
36434 @xref{Stop Reply Packets}, for the reply specifications.
36437 @cindex @samp{vCont?} packet
36438 Request a list of actions supported by the @samp{vCont} packet.
36442 @item vCont@r{[};@var{action}@dots{}@r{]}
36443 The @samp{vCont} packet is supported. Each @var{action} is a supported
36444 command in the @samp{vCont} packet.
36446 The @samp{vCont} packet is not supported.
36449 @item vFile:@var{operation}:@var{parameter}@dots{}
36450 @cindex @samp{vFile} packet
36451 Perform a file operation on the target system. For details,
36452 see @ref{Host I/O Packets}.
36454 @item vFlashErase:@var{addr},@var{length}
36455 @cindex @samp{vFlashErase} packet
36456 Direct the stub to erase @var{length} bytes of flash starting at
36457 @var{addr}. The region may enclose any number of flash blocks, but
36458 its start and end must fall on block boundaries, as indicated by the
36459 flash block size appearing in the memory map (@pxref{Memory Map
36460 Format}). @value{GDBN} groups flash memory programming operations
36461 together, and sends a @samp{vFlashDone} request after each group; the
36462 stub is allowed to delay erase operation until the @samp{vFlashDone}
36463 packet is received.
36473 @item vFlashWrite:@var{addr}:@var{XX@dots{}}
36474 @cindex @samp{vFlashWrite} packet
36475 Direct the stub to write data to flash address @var{addr}. The data
36476 is passed in binary form using the same encoding as for the @samp{X}
36477 packet (@pxref{Binary Data}). The memory ranges specified by
36478 @samp{vFlashWrite} packets preceding a @samp{vFlashDone} packet must
36479 not overlap, and must appear in order of increasing addresses
36480 (although @samp{vFlashErase} packets for higher addresses may already
36481 have been received; the ordering is guaranteed only between
36482 @samp{vFlashWrite} packets). If a packet writes to an address that was
36483 neither erased by a preceding @samp{vFlashErase} packet nor by some other
36484 target-specific method, the results are unpredictable.
36492 for vFlashWrite addressing non-flash memory
36498 @cindex @samp{vFlashDone} packet
36499 Indicate to the stub that flash programming operation is finished.
36500 The stub is permitted to delay or batch the effects of a group of
36501 @samp{vFlashErase} and @samp{vFlashWrite} packets until a
36502 @samp{vFlashDone} packet is received. The contents of the affected
36503 regions of flash memory are unpredictable until the @samp{vFlashDone}
36504 request is completed.
36506 @item vKill;@var{pid}
36507 @cindex @samp{vKill} packet
36508 Kill the process with the specified process ID. @var{pid} is a
36509 hexadecimal integer identifying the process. This packet is used in
36510 preference to @samp{k} when multiprocess protocol extensions are
36511 supported; see @ref{multiprocess extensions}.
36521 @item vRun;@var{filename}@r{[};@var{argument}@r{]}@dots{}
36522 @cindex @samp{vRun} packet
36523 Run the program @var{filename}, passing it each @var{argument} on its
36524 command line. The file and arguments are hex-encoded strings. If
36525 @var{filename} is an empty string, the stub may use a default program
36526 (e.g.@: the last program run). The program is created in the stopped
36529 @c FIXME: What about non-stop mode?
36531 This packet is only available in extended mode (@pxref{extended mode}).
36537 @item @r{Any stop packet}
36538 for success (@pxref{Stop Reply Packets})
36542 @cindex @samp{vStopped} packet
36543 @xref{Notification Packets}.
36545 @item X @var{addr},@var{length}:@var{XX@dots{}}
36547 @cindex @samp{X} packet
36548 Write data to memory, where the data is transmitted in binary.
36549 @var{addr} is address, @var{length} is number of bytes,
36550 @samp{@var{XX}@dots{}} is binary data (@pxref{Binary Data}).
36560 @item z @var{type},@var{addr},@var{kind}
36561 @itemx Z @var{type},@var{addr},@var{kind}
36562 @anchor{insert breakpoint or watchpoint packet}
36563 @cindex @samp{z} packet
36564 @cindex @samp{Z} packets
36565 Insert (@samp{Z}) or remove (@samp{z}) a @var{type} breakpoint or
36566 watchpoint starting at address @var{address} of kind @var{kind}.
36568 Each breakpoint and watchpoint packet @var{type} is documented
36571 @emph{Implementation notes: A remote target shall return an empty string
36572 for an unrecognized breakpoint or watchpoint packet @var{type}. A
36573 remote target shall support either both or neither of a given
36574 @samp{Z@var{type}@dots{}} and @samp{z@var{type}@dots{}} packet pair. To
36575 avoid potential problems with duplicate packets, the operations should
36576 be implemented in an idempotent way.}
36578 @item z0,@var{addr},@var{kind}
36579 @itemx Z0,@var{addr},@var{kind}@r{[};@var{cond_list}@dots{}@r{]}@r{[};cmds:@var{persist},@var{cmd_list}@dots{}@r{]}
36580 @cindex @samp{z0} packet
36581 @cindex @samp{Z0} packet
36582 Insert (@samp{Z0}) or remove (@samp{z0}) a memory breakpoint at address
36583 @var{addr} of type @var{kind}.
36585 A memory breakpoint is implemented by replacing the instruction at
36586 @var{addr} with a software breakpoint or trap instruction. The
36587 @var{kind} is target-specific and typically indicates the size of
36588 the breakpoint in bytes that should be inserted. E.g., the @sc{arm}
36589 and @sc{mips} can insert either a 2 or 4 byte breakpoint. Some
36590 architectures have additional meanings for @var{kind};
36591 @var{cond_list} is an optional list of conditional expressions in bytecode
36592 form that should be evaluated on the target's side. These are the
36593 conditions that should be taken into consideration when deciding if
36594 the breakpoint trigger should be reported back to @var{GDBN}.
36596 The @var{cond_list} parameter is comprised of a series of expressions,
36597 concatenated without separators. Each expression has the following form:
36601 @item X @var{len},@var{expr}
36602 @var{len} is the length of the bytecode expression and @var{expr} is the
36603 actual conditional expression in bytecode form.
36607 The optional @var{cmd_list} parameter introduces commands that may be
36608 run on the target, rather than being reported back to @value{GDBN}.
36609 The parameter starts with a numeric flag @var{persist}; if the flag is
36610 nonzero, then the breakpoint may remain active and the commands
36611 continue to be run even when @value{GDBN} disconnects from the target.
36612 Following this flag is a series of expressions concatenated with no
36613 separators. Each expression has the following form:
36617 @item X @var{len},@var{expr}
36618 @var{len} is the length of the bytecode expression and @var{expr} is the
36619 actual conditional expression in bytecode form.
36623 see @ref{Architecture-Specific Protocol Details}.
36625 @emph{Implementation note: It is possible for a target to copy or move
36626 code that contains memory breakpoints (e.g., when implementing
36627 overlays). The behavior of this packet, in the presence of such a
36628 target, is not defined.}
36640 @item z1,@var{addr},@var{kind}
36641 @itemx Z1,@var{addr},@var{kind}@r{[};@var{cond_list}@dots{}@r{]}
36642 @cindex @samp{z1} packet
36643 @cindex @samp{Z1} packet
36644 Insert (@samp{Z1}) or remove (@samp{z1}) a hardware breakpoint at
36645 address @var{addr}.
36647 A hardware breakpoint is implemented using a mechanism that is not
36648 dependant on being able to modify the target's memory. @var{kind}
36649 and @var{cond_list} have the same meaning as in @samp{Z0} packets.
36651 @emph{Implementation note: A hardware breakpoint is not affected by code
36664 @item z2,@var{addr},@var{kind}
36665 @itemx Z2,@var{addr},@var{kind}
36666 @cindex @samp{z2} packet
36667 @cindex @samp{Z2} packet
36668 Insert (@samp{Z2}) or remove (@samp{z2}) a write watchpoint at @var{addr}.
36669 @var{kind} is interpreted as the number of bytes to watch.
36681 @item z3,@var{addr},@var{kind}
36682 @itemx Z3,@var{addr},@var{kind}
36683 @cindex @samp{z3} packet
36684 @cindex @samp{Z3} packet
36685 Insert (@samp{Z3}) or remove (@samp{z3}) a read watchpoint at @var{addr}.
36686 @var{kind} is interpreted as the number of bytes to watch.
36698 @item z4,@var{addr},@var{kind}
36699 @itemx Z4,@var{addr},@var{kind}
36700 @cindex @samp{z4} packet
36701 @cindex @samp{Z4} packet
36702 Insert (@samp{Z4}) or remove (@samp{z4}) an access watchpoint at @var{addr}.
36703 @var{kind} is interpreted as the number of bytes to watch.
36717 @node Stop Reply Packets
36718 @section Stop Reply Packets
36719 @cindex stop reply packets
36721 The @samp{C}, @samp{c}, @samp{S}, @samp{s}, @samp{vCont},
36722 @samp{vAttach}, @samp{vRun}, @samp{vStopped}, and @samp{?} packets can
36723 receive any of the below as a reply. Except for @samp{?}
36724 and @samp{vStopped}, that reply is only returned
36725 when the target halts. In the below the exact meaning of @dfn{signal
36726 number} is defined by the header @file{include/gdb/signals.h} in the
36727 @value{GDBN} source code.
36729 As in the description of request packets, we include spaces in the
36730 reply templates for clarity; these are not part of the reply packet's
36731 syntax. No @value{GDBN} stop reply packet uses spaces to separate its
36737 The program received signal number @var{AA} (a two-digit hexadecimal
36738 number). This is equivalent to a @samp{T} response with no
36739 @var{n}:@var{r} pairs.
36741 @item T @var{AA} @var{n1}:@var{r1};@var{n2}:@var{r2};@dots{}
36742 @cindex @samp{T} packet reply
36743 The program received signal number @var{AA} (a two-digit hexadecimal
36744 number). This is equivalent to an @samp{S} response, except that the
36745 @samp{@var{n}:@var{r}} pairs can carry values of important registers
36746 and other information directly in the stop reply packet, reducing
36747 round-trip latency. Single-step and breakpoint traps are reported
36748 this way. Each @samp{@var{n}:@var{r}} pair is interpreted as follows:
36752 If @var{n} is a hexadecimal number, it is a register number, and the
36753 corresponding @var{r} gives that register's value. @var{r} is a
36754 series of bytes in target byte order, with each byte given by a
36755 two-digit hex number.
36758 If @var{n} is @samp{thread}, then @var{r} is the @var{thread-id} of
36759 the stopped thread, as specified in @ref{thread-id syntax}.
36762 If @var{n} is @samp{core}, then @var{r} is the hexadecimal number of
36763 the core on which the stop event was detected.
36766 If @var{n} is a recognized @dfn{stop reason}, it describes a more
36767 specific event that stopped the target. The currently defined stop
36768 reasons are listed below. @var{aa} should be @samp{05}, the trap
36769 signal. At most one stop reason should be present.
36772 Otherwise, @value{GDBN} should ignore this @samp{@var{n}:@var{r}} pair
36773 and go on to the next; this allows us to extend the protocol in the
36777 The currently defined stop reasons are:
36783 The packet indicates a watchpoint hit, and @var{r} is the data address, in
36786 @cindex shared library events, remote reply
36788 The packet indicates that the loaded libraries have changed.
36789 @value{GDBN} should use @samp{qXfer:libraries:read} to fetch a new
36790 list of loaded libraries. @var{r} is ignored.
36792 @cindex replay log events, remote reply
36794 The packet indicates that the target cannot continue replaying
36795 logged execution events, because it has reached the end (or the
36796 beginning when executing backward) of the log. The value of @var{r}
36797 will be either @samp{begin} or @samp{end}. @xref{Reverse Execution},
36798 for more information.
36802 @itemx W @var{AA} ; process:@var{pid}
36803 The process exited, and @var{AA} is the exit status. This is only
36804 applicable to certain targets.
36806 The second form of the response, including the process ID of the exited
36807 process, can be used only when @value{GDBN} has reported support for
36808 multiprocess protocol extensions; see @ref{multiprocess extensions}.
36809 The @var{pid} is formatted as a big-endian hex string.
36812 @itemx X @var{AA} ; process:@var{pid}
36813 The process terminated with signal @var{AA}.
36815 The second form of the response, including the process ID of the
36816 terminated process, can be used only when @value{GDBN} has reported
36817 support for multiprocess protocol extensions; see @ref{multiprocess
36818 extensions}. The @var{pid} is formatted as a big-endian hex string.
36820 @item O @var{XX}@dots{}
36821 @samp{@var{XX}@dots{}} is hex encoding of @sc{ascii} data, to be
36822 written as the program's console output. This can happen at any time
36823 while the program is running and the debugger should continue to wait
36824 for @samp{W}, @samp{T}, etc. This reply is not permitted in non-stop mode.
36826 @item F @var{call-id},@var{parameter}@dots{}
36827 @var{call-id} is the identifier which says which host system call should
36828 be called. This is just the name of the function. Translation into the
36829 correct system call is only applicable as it's defined in @value{GDBN}.
36830 @xref{File-I/O Remote Protocol Extension}, for a list of implemented
36833 @samp{@var{parameter}@dots{}} is a list of parameters as defined for
36834 this very system call.
36836 The target replies with this packet when it expects @value{GDBN} to
36837 call a host system call on behalf of the target. @value{GDBN} replies
36838 with an appropriate @samp{F} packet and keeps up waiting for the next
36839 reply packet from the target. The latest @samp{C}, @samp{c}, @samp{S}
36840 or @samp{s} action is expected to be continued. @xref{File-I/O Remote
36841 Protocol Extension}, for more details.
36845 @node General Query Packets
36846 @section General Query Packets
36847 @cindex remote query requests
36849 Packets starting with @samp{q} are @dfn{general query packets};
36850 packets starting with @samp{Q} are @dfn{general set packets}. General
36851 query and set packets are a semi-unified form for retrieving and
36852 sending information to and from the stub.
36854 The initial letter of a query or set packet is followed by a name
36855 indicating what sort of thing the packet applies to. For example,
36856 @value{GDBN} may use a @samp{qSymbol} packet to exchange symbol
36857 definitions with the stub. These packet names follow some
36862 The name must not contain commas, colons or semicolons.
36864 Most @value{GDBN} query and set packets have a leading upper case
36867 The names of custom vendor packets should use a company prefix, in
36868 lower case, followed by a period. For example, packets designed at
36869 the Acme Corporation might begin with @samp{qacme.foo} (for querying
36870 foos) or @samp{Qacme.bar} (for setting bars).
36873 The name of a query or set packet should be separated from any
36874 parameters by a @samp{:}; the parameters themselves should be
36875 separated by @samp{,} or @samp{;}. Stubs must be careful to match the
36876 full packet name, and check for a separator or the end of the packet,
36877 in case two packet names share a common prefix. New packets should not begin
36878 with @samp{qC}, @samp{qP}, or @samp{qL}@footnote{The @samp{qP} and @samp{qL}
36879 packets predate these conventions, and have arguments without any terminator
36880 for the packet name; we suspect they are in widespread use in places that
36881 are difficult to upgrade. The @samp{qC} packet has no arguments, but some
36882 existing stubs (e.g.@: RedBoot) are known to not check for the end of the
36885 Like the descriptions of the other packets, each description here
36886 has a template showing the packet's overall syntax, followed by an
36887 explanation of the packet's meaning. We include spaces in some of the
36888 templates for clarity; these are not part of the packet's syntax. No
36889 @value{GDBN} packet uses spaces to separate its components.
36891 Here are the currently defined query and set packets:
36897 Turn on or off the agent as a helper to perform some debugging operations
36898 delegated from @value{GDBN} (@pxref{Control Agent}).
36900 @item QAllow:@var{op}:@var{val}@dots{}
36901 @cindex @samp{QAllow} packet
36902 Specify which operations @value{GDBN} expects to request of the
36903 target, as a semicolon-separated list of operation name and value
36904 pairs. Possible values for @var{op} include @samp{WriteReg},
36905 @samp{WriteMem}, @samp{InsertBreak}, @samp{InsertTrace},
36906 @samp{InsertFastTrace}, and @samp{Stop}. @var{val} is either 0,
36907 indicating that @value{GDBN} will not request the operation, or 1,
36908 indicating that it may. (The target can then use this to set up its
36909 own internals optimally, for instance if the debugger never expects to
36910 insert breakpoints, it may not need to install its own trap handler.)
36913 @cindex current thread, remote request
36914 @cindex @samp{qC} packet
36915 Return the current thread ID.
36919 @item QC @var{thread-id}
36920 Where @var{thread-id} is a thread ID as documented in
36921 @ref{thread-id syntax}.
36922 @item @r{(anything else)}
36923 Any other reply implies the old thread ID.
36926 @item qCRC:@var{addr},@var{length}
36927 @cindex CRC of memory block, remote request
36928 @cindex @samp{qCRC} packet
36929 Compute the CRC checksum of a block of memory using CRC-32 defined in
36930 IEEE 802.3. The CRC is computed byte at a time, taking the most
36931 significant bit of each byte first. The initial pattern code
36932 @code{0xffffffff} is used to ensure leading zeros affect the CRC.
36934 @emph{Note:} This is the same CRC used in validating separate debug
36935 files (@pxref{Separate Debug Files, , Debugging Information in Separate
36936 Files}). However the algorithm is slightly different. When validating
36937 separate debug files, the CRC is computed taking the @emph{least}
36938 significant bit of each byte first, and the final result is inverted to
36939 detect trailing zeros.
36944 An error (such as memory fault)
36945 @item C @var{crc32}
36946 The specified memory region's checksum is @var{crc32}.
36949 @item QDisableRandomization:@var{value}
36950 @cindex disable address space randomization, remote request
36951 @cindex @samp{QDisableRandomization} packet
36952 Some target operating systems will randomize the virtual address space
36953 of the inferior process as a security feature, but provide a feature
36954 to disable such randomization, e.g.@: to allow for a more deterministic
36955 debugging experience. On such systems, this packet with a @var{value}
36956 of 1 directs the target to disable address space randomization for
36957 processes subsequently started via @samp{vRun} packets, while a packet
36958 with a @var{value} of 0 tells the target to enable address space
36961 This packet is only available in extended mode (@pxref{extended mode}).
36966 The request succeeded.
36969 An error occurred. @var{nn} are hex digits.
36972 An empty reply indicates that @samp{QDisableRandomization} is not supported
36976 This packet is not probed by default; the remote stub must request it,
36977 by supplying an appropriate @samp{qSupported} response (@pxref{qSupported}).
36978 This should only be done on targets that actually support disabling
36979 address space randomization.
36982 @itemx qsThreadInfo
36983 @cindex list active threads, remote request
36984 @cindex @samp{qfThreadInfo} packet
36985 @cindex @samp{qsThreadInfo} packet
36986 Obtain a list of all active thread IDs from the target (OS). Since there
36987 may be too many active threads to fit into one reply packet, this query
36988 works iteratively: it may require more than one query/reply sequence to
36989 obtain the entire list of threads. The first query of the sequence will
36990 be the @samp{qfThreadInfo} query; subsequent queries in the
36991 sequence will be the @samp{qsThreadInfo} query.
36993 NOTE: This packet replaces the @samp{qL} query (see below).
36997 @item m @var{thread-id}
36999 @item m @var{thread-id},@var{thread-id}@dots{}
37000 a comma-separated list of thread IDs
37002 (lower case letter @samp{L}) denotes end of list.
37005 In response to each query, the target will reply with a list of one or
37006 more thread IDs, separated by commas.
37007 @value{GDBN} will respond to each reply with a request for more thread
37008 ids (using the @samp{qs} form of the query), until the target responds
37009 with @samp{l} (lower-case ell, for @dfn{last}).
37010 Refer to @ref{thread-id syntax}, for the format of the @var{thread-id}
37013 @item qGetTLSAddr:@var{thread-id},@var{offset},@var{lm}
37014 @cindex get thread-local storage address, remote request
37015 @cindex @samp{qGetTLSAddr} packet
37016 Fetch the address associated with thread local storage specified
37017 by @var{thread-id}, @var{offset}, and @var{lm}.
37019 @var{thread-id} is the thread ID associated with the
37020 thread for which to fetch the TLS address. @xref{thread-id syntax}.
37022 @var{offset} is the (big endian, hex encoded) offset associated with the
37023 thread local variable. (This offset is obtained from the debug
37024 information associated with the variable.)
37026 @var{lm} is the (big endian, hex encoded) OS/ABI-specific encoding of the
37027 load module associated with the thread local storage. For example,
37028 a @sc{gnu}/Linux system will pass the link map address of the shared
37029 object associated with the thread local storage under consideration.
37030 Other operating environments may choose to represent the load module
37031 differently, so the precise meaning of this parameter will vary.
37035 @item @var{XX}@dots{}
37036 Hex encoded (big endian) bytes representing the address of the thread
37037 local storage requested.
37040 An error occurred. @var{nn} are hex digits.
37043 An empty reply indicates that @samp{qGetTLSAddr} is not supported by the stub.
37046 @item qGetTIBAddr:@var{thread-id}
37047 @cindex get thread information block address
37048 @cindex @samp{qGetTIBAddr} packet
37049 Fetch address of the Windows OS specific Thread Information Block.
37051 @var{thread-id} is the thread ID associated with the thread.
37055 @item @var{XX}@dots{}
37056 Hex encoded (big endian) bytes representing the linear address of the
37057 thread information block.
37060 An error occured. This means that either the thread was not found, or the
37061 address could not be retrieved.
37064 An empty reply indicates that @samp{qGetTIBAddr} is not supported by the stub.
37067 @item qL @var{startflag} @var{threadcount} @var{nextthread}
37068 Obtain thread information from RTOS. Where: @var{startflag} (one hex
37069 digit) is one to indicate the first query and zero to indicate a
37070 subsequent query; @var{threadcount} (two hex digits) is the maximum
37071 number of threads the response packet can contain; and @var{nextthread}
37072 (eight hex digits), for subsequent queries (@var{startflag} is zero), is
37073 returned in the response as @var{argthread}.
37075 Don't use this packet; use the @samp{qfThreadInfo} query instead (see above).
37079 @item qM @var{count} @var{done} @var{argthread} @var{thread}@dots{}
37080 Where: @var{count} (two hex digits) is the number of threads being
37081 returned; @var{done} (one hex digit) is zero to indicate more threads
37082 and one indicates no further threads; @var{argthreadid} (eight hex
37083 digits) is @var{nextthread} from the request packet; @var{thread}@dots{}
37084 is a sequence of thread IDs from the target. @var{threadid} (eight hex
37085 digits). See @code{remote.c:parse_threadlist_response()}.
37089 @cindex section offsets, remote request
37090 @cindex @samp{qOffsets} packet
37091 Get section offsets that the target used when relocating the downloaded
37096 @item Text=@var{xxx};Data=@var{yyy}@r{[};Bss=@var{zzz}@r{]}
37097 Relocate the @code{Text} section by @var{xxx} from its original address.
37098 Relocate the @code{Data} section by @var{yyy} from its original address.
37099 If the object file format provides segment information (e.g.@: @sc{elf}
37100 @samp{PT_LOAD} program headers), @value{GDBN} will relocate entire
37101 segments by the supplied offsets.
37103 @emph{Note: while a @code{Bss} offset may be included in the response,
37104 @value{GDBN} ignores this and instead applies the @code{Data} offset
37105 to the @code{Bss} section.}
37107 @item TextSeg=@var{xxx}@r{[};DataSeg=@var{yyy}@r{]}
37108 Relocate the first segment of the object file, which conventionally
37109 contains program code, to a starting address of @var{xxx}. If
37110 @samp{DataSeg} is specified, relocate the second segment, which
37111 conventionally contains modifiable data, to a starting address of
37112 @var{yyy}. @value{GDBN} will report an error if the object file
37113 does not contain segment information, or does not contain at least
37114 as many segments as mentioned in the reply. Extra segments are
37115 kept at fixed offsets relative to the last relocated segment.
37118 @item qP @var{mode} @var{thread-id}
37119 @cindex thread information, remote request
37120 @cindex @samp{qP} packet
37121 Returns information on @var{thread-id}. Where: @var{mode} is a hex
37122 encoded 32 bit mode; @var{thread-id} is a thread ID
37123 (@pxref{thread-id syntax}).
37125 Don't use this packet; use the @samp{qThreadExtraInfo} query instead
37128 Reply: see @code{remote.c:remote_unpack_thread_info_response()}.
37132 @cindex non-stop mode, remote request
37133 @cindex @samp{QNonStop} packet
37135 Enter non-stop (@samp{QNonStop:1}) or all-stop (@samp{QNonStop:0}) mode.
37136 @xref{Remote Non-Stop}, for more information.
37141 The request succeeded.
37144 An error occurred. @var{nn} are hex digits.
37147 An empty reply indicates that @samp{QNonStop} is not supported by
37151 This packet is not probed by default; the remote stub must request it,
37152 by supplying an appropriate @samp{qSupported} response (@pxref{qSupported}).
37153 Use of this packet is controlled by the @code{set non-stop} command;
37154 @pxref{Non-Stop Mode}.
37156 @item QPassSignals: @var{signal} @r{[};@var{signal}@r{]}@dots{}
37157 @cindex pass signals to inferior, remote request
37158 @cindex @samp{QPassSignals} packet
37159 @anchor{QPassSignals}
37160 Each listed @var{signal} should be passed directly to the inferior process.
37161 Signals are numbered identically to continue packets and stop replies
37162 (@pxref{Stop Reply Packets}). Each @var{signal} list item should be
37163 strictly greater than the previous item. These signals do not need to stop
37164 the inferior, or be reported to @value{GDBN}. All other signals should be
37165 reported to @value{GDBN}. Multiple @samp{QPassSignals} packets do not
37166 combine; any earlier @samp{QPassSignals} list is completely replaced by the
37167 new list. This packet improves performance when using @samp{handle
37168 @var{signal} nostop noprint pass}.
37173 The request succeeded.
37176 An error occurred. @var{nn} are hex digits.
37179 An empty reply indicates that @samp{QPassSignals} is not supported by
37183 Use of this packet is controlled by the @code{set remote pass-signals}
37184 command (@pxref{Remote Configuration, set remote pass-signals}).
37185 This packet is not probed by default; the remote stub must request it,
37186 by supplying an appropriate @samp{qSupported} response (@pxref{qSupported}).
37188 @item QProgramSignals: @var{signal} @r{[};@var{signal}@r{]}@dots{}
37189 @cindex signals the inferior may see, remote request
37190 @cindex @samp{QProgramSignals} packet
37191 @anchor{QProgramSignals}
37192 Each listed @var{signal} may be delivered to the inferior process.
37193 Others should be silently discarded.
37195 In some cases, the remote stub may need to decide whether to deliver a
37196 signal to the program or not without @value{GDBN} involvement. One
37197 example of that is while detaching --- the program's threads may have
37198 stopped for signals that haven't yet had a chance of being reported to
37199 @value{GDBN}, and so the remote stub can use the signal list specified
37200 by this packet to know whether to deliver or ignore those pending
37203 This does not influence whether to deliver a signal as requested by a
37204 resumption packet (@pxref{vCont packet}).
37206 Signals are numbered identically to continue packets and stop replies
37207 (@pxref{Stop Reply Packets}). Each @var{signal} list item should be
37208 strictly greater than the previous item. Multiple
37209 @samp{QProgramSignals} packets do not combine; any earlier
37210 @samp{QProgramSignals} list is completely replaced by the new list.
37215 The request succeeded.
37218 An error occurred. @var{nn} are hex digits.
37221 An empty reply indicates that @samp{QProgramSignals} is not supported
37225 Use of this packet is controlled by the @code{set remote program-signals}
37226 command (@pxref{Remote Configuration, set remote program-signals}).
37227 This packet is not probed by default; the remote stub must request it,
37228 by supplying an appropriate @samp{qSupported} response (@pxref{qSupported}).
37230 @item qRcmd,@var{command}
37231 @cindex execute remote command, remote request
37232 @cindex @samp{qRcmd} packet
37233 @var{command} (hex encoded) is passed to the local interpreter for
37234 execution. Invalid commands should be reported using the output
37235 string. Before the final result packet, the target may also respond
37236 with a number of intermediate @samp{O@var{output}} console output
37237 packets. @emph{Implementors should note that providing access to a
37238 stubs's interpreter may have security implications}.
37243 A command response with no output.
37245 A command response with the hex encoded output string @var{OUTPUT}.
37247 Indicate a badly formed request.
37249 An empty reply indicates that @samp{qRcmd} is not recognized.
37252 (Note that the @code{qRcmd} packet's name is separated from the
37253 command by a @samp{,}, not a @samp{:}, contrary to the naming
37254 conventions above. Please don't use this packet as a model for new
37257 @item qSearch:memory:@var{address};@var{length};@var{search-pattern}
37258 @cindex searching memory, in remote debugging
37260 @cindex @samp{qSearch:memory} packet
37262 @cindex @samp{qSearch memory} packet
37263 @anchor{qSearch memory}
37264 Search @var{length} bytes at @var{address} for @var{search-pattern}.
37265 @var{address} and @var{length} are encoded in hex.
37266 @var{search-pattern} is a sequence of bytes, hex encoded.
37271 The pattern was not found.
37273 The pattern was found at @var{address}.
37275 A badly formed request or an error was encountered while searching memory.
37277 An empty reply indicates that @samp{qSearch:memory} is not recognized.
37280 @item QStartNoAckMode
37281 @cindex @samp{QStartNoAckMode} packet
37282 @anchor{QStartNoAckMode}
37283 Request that the remote stub disable the normal @samp{+}/@samp{-}
37284 protocol acknowledgments (@pxref{Packet Acknowledgment}).
37289 The stub has switched to no-acknowledgment mode.
37290 @value{GDBN} acknowledges this reponse,
37291 but neither the stub nor @value{GDBN} shall send or expect further
37292 @samp{+}/@samp{-} acknowledgments in the current connection.
37294 An empty reply indicates that the stub does not support no-acknowledgment mode.
37297 @item qSupported @r{[}:@var{gdbfeature} @r{[};@var{gdbfeature}@r{]}@dots{} @r{]}
37298 @cindex supported packets, remote query
37299 @cindex features of the remote protocol
37300 @cindex @samp{qSupported} packet
37301 @anchor{qSupported}
37302 Tell the remote stub about features supported by @value{GDBN}, and
37303 query the stub for features it supports. This packet allows
37304 @value{GDBN} and the remote stub to take advantage of each others'
37305 features. @samp{qSupported} also consolidates multiple feature probes
37306 at startup, to improve @value{GDBN} performance---a single larger
37307 packet performs better than multiple smaller probe packets on
37308 high-latency links. Some features may enable behavior which must not
37309 be on by default, e.g.@: because it would confuse older clients or
37310 stubs. Other features may describe packets which could be
37311 automatically probed for, but are not. These features must be
37312 reported before @value{GDBN} will use them. This ``default
37313 unsupported'' behavior is not appropriate for all packets, but it
37314 helps to keep the initial connection time under control with new
37315 versions of @value{GDBN} which support increasing numbers of packets.
37319 @item @var{stubfeature} @r{[};@var{stubfeature}@r{]}@dots{}
37320 The stub supports or does not support each returned @var{stubfeature},
37321 depending on the form of each @var{stubfeature} (see below for the
37324 An empty reply indicates that @samp{qSupported} is not recognized,
37325 or that no features needed to be reported to @value{GDBN}.
37328 The allowed forms for each feature (either a @var{gdbfeature} in the
37329 @samp{qSupported} packet, or a @var{stubfeature} in the response)
37333 @item @var{name}=@var{value}
37334 The remote protocol feature @var{name} is supported, and associated
37335 with the specified @var{value}. The format of @var{value} depends
37336 on the feature, but it must not include a semicolon.
37338 The remote protocol feature @var{name} is supported, and does not
37339 need an associated value.
37341 The remote protocol feature @var{name} is not supported.
37343 The remote protocol feature @var{name} may be supported, and
37344 @value{GDBN} should auto-detect support in some other way when it is
37345 needed. This form will not be used for @var{gdbfeature} notifications,
37346 but may be used for @var{stubfeature} responses.
37349 Whenever the stub receives a @samp{qSupported} request, the
37350 supplied set of @value{GDBN} features should override any previous
37351 request. This allows @value{GDBN} to put the stub in a known
37352 state, even if the stub had previously been communicating with
37353 a different version of @value{GDBN}.
37355 The following values of @var{gdbfeature} (for the packet sent by @value{GDBN})
37360 This feature indicates whether @value{GDBN} supports multiprocess
37361 extensions to the remote protocol. @value{GDBN} does not use such
37362 extensions unless the stub also reports that it supports them by
37363 including @samp{multiprocess+} in its @samp{qSupported} reply.
37364 @xref{multiprocess extensions}, for details.
37367 This feature indicates that @value{GDBN} supports the XML target
37368 description. If the stub sees @samp{xmlRegisters=} with target
37369 specific strings separated by a comma, it will report register
37373 This feature indicates whether @value{GDBN} supports the
37374 @samp{qRelocInsn} packet (@pxref{Tracepoint Packets,,Relocate
37375 instruction reply packet}).
37378 Stubs should ignore any unknown values for
37379 @var{gdbfeature}. Any @value{GDBN} which sends a @samp{qSupported}
37380 packet supports receiving packets of unlimited length (earlier
37381 versions of @value{GDBN} may reject overly long responses). Additional values
37382 for @var{gdbfeature} may be defined in the future to let the stub take
37383 advantage of new features in @value{GDBN}, e.g.@: incompatible
37384 improvements in the remote protocol---the @samp{multiprocess} feature is
37385 an example of such a feature. The stub's reply should be independent
37386 of the @var{gdbfeature} entries sent by @value{GDBN}; first @value{GDBN}
37387 describes all the features it supports, and then the stub replies with
37388 all the features it supports.
37390 Similarly, @value{GDBN} will silently ignore unrecognized stub feature
37391 responses, as long as each response uses one of the standard forms.
37393 Some features are flags. A stub which supports a flag feature
37394 should respond with a @samp{+} form response. Other features
37395 require values, and the stub should respond with an @samp{=}
37398 Each feature has a default value, which @value{GDBN} will use if
37399 @samp{qSupported} is not available or if the feature is not mentioned
37400 in the @samp{qSupported} response. The default values are fixed; a
37401 stub is free to omit any feature responses that match the defaults.
37403 Not all features can be probed, but for those which can, the probing
37404 mechanism is useful: in some cases, a stub's internal
37405 architecture may not allow the protocol layer to know some information
37406 about the underlying target in advance. This is especially common in
37407 stubs which may be configured for multiple targets.
37409 These are the currently defined stub features and their properties:
37411 @multitable @columnfractions 0.35 0.2 0.12 0.2
37412 @c NOTE: The first row should be @headitem, but we do not yet require
37413 @c a new enough version of Texinfo (4.7) to use @headitem.
37415 @tab Value Required
37419 @item @samp{PacketSize}
37424 @item @samp{qXfer:auxv:read}
37429 @item @samp{qXfer:btrace:read}
37434 @item @samp{qXfer:features:read}
37439 @item @samp{qXfer:libraries:read}
37444 @item @samp{qXfer:memory-map:read}
37449 @item @samp{qXfer:sdata:read}
37454 @item @samp{qXfer:spu:read}
37459 @item @samp{qXfer:spu:write}
37464 @item @samp{qXfer:siginfo:read}
37469 @item @samp{qXfer:siginfo:write}
37474 @item @samp{qXfer:threads:read}
37479 @item @samp{qXfer:traceframe-info:read}
37484 @item @samp{qXfer:uib:read}
37489 @item @samp{qXfer:fdpic:read}
37494 @item @samp{Qbtrace:off}
37499 @item @samp{Qbtrace:bts}
37504 @item @samp{QNonStop}
37509 @item @samp{QPassSignals}
37514 @item @samp{QStartNoAckMode}
37519 @item @samp{multiprocess}
37524 @item @samp{ConditionalBreakpoints}
37529 @item @samp{ConditionalTracepoints}
37534 @item @samp{ReverseContinue}
37539 @item @samp{ReverseStep}
37544 @item @samp{TracepointSource}
37549 @item @samp{QAgent}
37554 @item @samp{QAllow}
37559 @item @samp{QDisableRandomization}
37564 @item @samp{EnableDisableTracepoints}
37569 @item @samp{QTBuffer:size}
37574 @item @samp{tracenz}
37579 @item @samp{BreakpointCommands}
37586 These are the currently defined stub features, in more detail:
37589 @cindex packet size, remote protocol
37590 @item PacketSize=@var{bytes}
37591 The remote stub can accept packets up to at least @var{bytes} in
37592 length. @value{GDBN} will send packets up to this size for bulk
37593 transfers, and will never send larger packets. This is a limit on the
37594 data characters in the packet, including the frame and checksum.
37595 There is no trailing NUL byte in a remote protocol packet; if the stub
37596 stores packets in a NUL-terminated format, it should allow an extra
37597 byte in its buffer for the NUL. If this stub feature is not supported,
37598 @value{GDBN} guesses based on the size of the @samp{g} packet response.
37600 @item qXfer:auxv:read
37601 The remote stub understands the @samp{qXfer:auxv:read} packet
37602 (@pxref{qXfer auxiliary vector read}).
37604 @item qXfer:btrace:read
37605 The remote stub understands the @samp{qXfer:btrace:read}
37606 packet (@pxref{qXfer btrace read}).
37608 @item qXfer:features:read
37609 The remote stub understands the @samp{qXfer:features:read} packet
37610 (@pxref{qXfer target description read}).
37612 @item qXfer:libraries:read
37613 The remote stub understands the @samp{qXfer:libraries:read} packet
37614 (@pxref{qXfer library list read}).
37616 @item qXfer:libraries-svr4:read
37617 The remote stub understands the @samp{qXfer:libraries-svr4:read} packet
37618 (@pxref{qXfer svr4 library list read}).
37620 @item qXfer:memory-map:read
37621 The remote stub understands the @samp{qXfer:memory-map:read} packet
37622 (@pxref{qXfer memory map read}).
37624 @item qXfer:sdata:read
37625 The remote stub understands the @samp{qXfer:sdata:read} packet
37626 (@pxref{qXfer sdata read}).
37628 @item qXfer:spu:read
37629 The remote stub understands the @samp{qXfer:spu:read} packet
37630 (@pxref{qXfer spu read}).
37632 @item qXfer:spu:write
37633 The remote stub understands the @samp{qXfer:spu:write} packet
37634 (@pxref{qXfer spu write}).
37636 @item qXfer:siginfo:read
37637 The remote stub understands the @samp{qXfer:siginfo:read} packet
37638 (@pxref{qXfer siginfo read}).
37640 @item qXfer:siginfo:write
37641 The remote stub understands the @samp{qXfer:siginfo:write} packet
37642 (@pxref{qXfer siginfo write}).
37644 @item qXfer:threads:read
37645 The remote stub understands the @samp{qXfer:threads:read} packet
37646 (@pxref{qXfer threads read}).
37648 @item qXfer:traceframe-info:read
37649 The remote stub understands the @samp{qXfer:traceframe-info:read}
37650 packet (@pxref{qXfer traceframe info read}).
37652 @item qXfer:uib:read
37653 The remote stub understands the @samp{qXfer:uib:read}
37654 packet (@pxref{qXfer unwind info block}).
37656 @item qXfer:fdpic:read
37657 The remote stub understands the @samp{qXfer:fdpic:read}
37658 packet (@pxref{qXfer fdpic loadmap read}).
37661 The remote stub understands the @samp{QNonStop} packet
37662 (@pxref{QNonStop}).
37665 The remote stub understands the @samp{QPassSignals} packet
37666 (@pxref{QPassSignals}).
37668 @item QStartNoAckMode
37669 The remote stub understands the @samp{QStartNoAckMode} packet and
37670 prefers to operate in no-acknowledgment mode. @xref{Packet Acknowledgment}.
37673 @anchor{multiprocess extensions}
37674 @cindex multiprocess extensions, in remote protocol
37675 The remote stub understands the multiprocess extensions to the remote
37676 protocol syntax. The multiprocess extensions affect the syntax of
37677 thread IDs in both packets and replies (@pxref{thread-id syntax}), and
37678 add process IDs to the @samp{D} packet and @samp{W} and @samp{X}
37679 replies. Note that reporting this feature indicates support for the
37680 syntactic extensions only, not that the stub necessarily supports
37681 debugging of more than one process at a time. The stub must not use
37682 multiprocess extensions in packet replies unless @value{GDBN} has also
37683 indicated it supports them in its @samp{qSupported} request.
37685 @item qXfer:osdata:read
37686 The remote stub understands the @samp{qXfer:osdata:read} packet
37687 ((@pxref{qXfer osdata read}).
37689 @item ConditionalBreakpoints
37690 The target accepts and implements evaluation of conditional expressions
37691 defined for breakpoints. The target will only report breakpoint triggers
37692 when such conditions are true (@pxref{Conditions, ,Break Conditions}).
37694 @item ConditionalTracepoints
37695 The remote stub accepts and implements conditional expressions defined
37696 for tracepoints (@pxref{Tracepoint Conditions}).
37698 @item ReverseContinue
37699 The remote stub accepts and implements the reverse continue packet
37703 The remote stub accepts and implements the reverse step packet
37706 @item TracepointSource
37707 The remote stub understands the @samp{QTDPsrc} packet that supplies
37708 the source form of tracepoint definitions.
37711 The remote stub understands the @samp{QAgent} packet.
37714 The remote stub understands the @samp{QAllow} packet.
37716 @item QDisableRandomization
37717 The remote stub understands the @samp{QDisableRandomization} packet.
37719 @item StaticTracepoint
37720 @cindex static tracepoints, in remote protocol
37721 The remote stub supports static tracepoints.
37723 @item InstallInTrace
37724 @anchor{install tracepoint in tracing}
37725 The remote stub supports installing tracepoint in tracing.
37727 @item EnableDisableTracepoints
37728 The remote stub supports the @samp{QTEnable} (@pxref{QTEnable}) and
37729 @samp{QTDisable} (@pxref{QTDisable}) packets that allow tracepoints
37730 to be enabled and disabled while a trace experiment is running.
37732 @item QTBuffer:size
37733 The remote stub supports the @samp{QTBuffer:size} (@pxref{QTBuffer-size})
37734 packet that allows to change the size of the trace buffer.
37737 @cindex string tracing, in remote protocol
37738 The remote stub supports the @samp{tracenz} bytecode for collecting strings.
37739 See @ref{Bytecode Descriptions} for details about the bytecode.
37741 @item BreakpointCommands
37742 @cindex breakpoint commands, in remote protocol
37743 The remote stub supports running a breakpoint's command list itself,
37744 rather than reporting the hit to @value{GDBN}.
37747 The remote stub understands the @samp{Qbtrace:off} packet.
37750 The remote stub understands the @samp{Qbtrace:bts} packet.
37755 @cindex symbol lookup, remote request
37756 @cindex @samp{qSymbol} packet
37757 Notify the target that @value{GDBN} is prepared to serve symbol lookup
37758 requests. Accept requests from the target for the values of symbols.
37763 The target does not need to look up any (more) symbols.
37764 @item qSymbol:@var{sym_name}
37765 The target requests the value of symbol @var{sym_name} (hex encoded).
37766 @value{GDBN} may provide the value by using the
37767 @samp{qSymbol:@var{sym_value}:@var{sym_name}} message, described
37771 @item qSymbol:@var{sym_value}:@var{sym_name}
37772 Set the value of @var{sym_name} to @var{sym_value}.
37774 @var{sym_name} (hex encoded) is the name of a symbol whose value the
37775 target has previously requested.
37777 @var{sym_value} (hex) is the value for symbol @var{sym_name}. If
37778 @value{GDBN} cannot supply a value for @var{sym_name}, then this field
37784 The target does not need to look up any (more) symbols.
37785 @item qSymbol:@var{sym_name}
37786 The target requests the value of a new symbol @var{sym_name} (hex
37787 encoded). @value{GDBN} will continue to supply the values of symbols
37788 (if available), until the target ceases to request them.
37793 @itemx QTDisconnected
37800 @itemx qTMinFTPILen
37802 @xref{Tracepoint Packets}.
37804 @item qThreadExtraInfo,@var{thread-id}
37805 @cindex thread attributes info, remote request
37806 @cindex @samp{qThreadExtraInfo} packet
37807 Obtain a printable string description of a thread's attributes from
37808 the target OS. @var{thread-id} is a thread ID;
37809 see @ref{thread-id syntax}. This
37810 string may contain anything that the target OS thinks is interesting
37811 for @value{GDBN} to tell the user about the thread. The string is
37812 displayed in @value{GDBN}'s @code{info threads} display. Some
37813 examples of possible thread extra info strings are @samp{Runnable}, or
37814 @samp{Blocked on Mutex}.
37818 @item @var{XX}@dots{}
37819 Where @samp{@var{XX}@dots{}} is a hex encoding of @sc{ascii} data,
37820 comprising the printable string containing the extra information about
37821 the thread's attributes.
37824 (Note that the @code{qThreadExtraInfo} packet's name is separated from
37825 the command by a @samp{,}, not a @samp{:}, contrary to the naming
37826 conventions above. Please don't use this packet as a model for new
37845 @xref{Tracepoint Packets}.
37847 @item qXfer:@var{object}:read:@var{annex}:@var{offset},@var{length}
37848 @cindex read special object, remote request
37849 @cindex @samp{qXfer} packet
37850 @anchor{qXfer read}
37851 Read uninterpreted bytes from the target's special data area
37852 identified by the keyword @var{object}. Request @var{length} bytes
37853 starting at @var{offset} bytes into the data. The content and
37854 encoding of @var{annex} is specific to @var{object}; it can supply
37855 additional details about what data to access.
37857 Here are the specific requests of this form defined so far. All
37858 @samp{qXfer:@var{object}:read:@dots{}} requests use the same reply
37859 formats, listed below.
37862 @item qXfer:auxv:read::@var{offset},@var{length}
37863 @anchor{qXfer auxiliary vector read}
37864 Access the target's @dfn{auxiliary vector}. @xref{OS Information,
37865 auxiliary vector}. Note @var{annex} must be empty.
37867 This packet is not probed by default; the remote stub must request it,
37868 by supplying an appropriate @samp{qSupported} response (@pxref{qSupported}).
37870 @item qXfer:btrace:read:@var{annex}:@var{offset},@var{length}
37871 @anchor{qXfer btrace read}
37873 Return a description of the current branch trace.
37874 @xref{Branch Trace Format}. The annex part of the generic @samp{qXfer}
37875 packet may have one of the following values:
37879 Returns all available branch trace.
37882 Returns all available branch trace if the branch trace changed since
37883 the last read request.
37886 This packet is not probed by default; the remote stub must request it
37887 by supplying an appropriate @samp{qSupported} response (@pxref{qSupported}).
37889 @item qXfer:features:read:@var{annex}:@var{offset},@var{length}
37890 @anchor{qXfer target description read}
37891 Access the @dfn{target description}. @xref{Target Descriptions}. The
37892 annex specifies which XML document to access. The main description is
37893 always loaded from the @samp{target.xml} annex.
37895 This packet is not probed by default; the remote stub must request it,
37896 by supplying an appropriate @samp{qSupported} response (@pxref{qSupported}).
37898 @item qXfer:libraries:read:@var{annex}:@var{offset},@var{length}
37899 @anchor{qXfer library list read}
37900 Access the target's list of loaded libraries. @xref{Library List Format}.
37901 The annex part of the generic @samp{qXfer} packet must be empty
37902 (@pxref{qXfer read}).
37904 Targets which maintain a list of libraries in the program's memory do
37905 not need to implement this packet; it is designed for platforms where
37906 the operating system manages the list of loaded libraries.
37908 This packet is not probed by default; the remote stub must request it,
37909 by supplying an appropriate @samp{qSupported} response (@pxref{qSupported}).
37911 @item qXfer:libraries-svr4:read:@var{annex}:@var{offset},@var{length}
37912 @anchor{qXfer svr4 library list read}
37913 Access the target's list of loaded libraries when the target is an SVR4
37914 platform. @xref{Library List Format for SVR4 Targets}. The annex part
37915 of the generic @samp{qXfer} packet must be empty (@pxref{qXfer read}).
37917 This packet is optional for better performance on SVR4 targets.
37918 @value{GDBN} uses memory read packets to read the SVR4 library list otherwise.
37920 This packet is not probed by default; the remote stub must request it,
37921 by supplying an appropriate @samp{qSupported} response (@pxref{qSupported}).
37923 @item qXfer:memory-map:read::@var{offset},@var{length}
37924 @anchor{qXfer memory map read}
37925 Access the target's @dfn{memory-map}. @xref{Memory Map Format}. The
37926 annex part of the generic @samp{qXfer} packet must be empty
37927 (@pxref{qXfer read}).
37929 This packet is not probed by default; the remote stub must request it,
37930 by supplying an appropriate @samp{qSupported} response (@pxref{qSupported}).
37932 @item qXfer:sdata:read::@var{offset},@var{length}
37933 @anchor{qXfer sdata read}
37935 Read contents of the extra collected static tracepoint marker
37936 information. The annex part of the generic @samp{qXfer} packet must
37937 be empty (@pxref{qXfer read}). @xref{Tracepoint Actions,,Tracepoint
37940 This packet is not probed by default; the remote stub must request it,
37941 by supplying an appropriate @samp{qSupported} response
37942 (@pxref{qSupported}).
37944 @item qXfer:siginfo:read::@var{offset},@var{length}
37945 @anchor{qXfer siginfo read}
37946 Read contents of the extra signal information on the target
37947 system. The annex part of the generic @samp{qXfer} packet must be
37948 empty (@pxref{qXfer read}).
37950 This packet is not probed by default; the remote stub must request it,
37951 by supplying an appropriate @samp{qSupported} response
37952 (@pxref{qSupported}).
37954 @item qXfer:spu:read:@var{annex}:@var{offset},@var{length}
37955 @anchor{qXfer spu read}
37956 Read contents of an @code{spufs} file on the target system. The
37957 annex specifies which file to read; it must be of the form
37958 @file{@var{id}/@var{name}}, where @var{id} specifies an SPU context ID
37959 in the target process, and @var{name} identifes the @code{spufs} file
37960 in that context to be accessed.
37962 This packet is not probed by default; the remote stub must request it,
37963 by supplying an appropriate @samp{qSupported} response
37964 (@pxref{qSupported}).
37966 @item qXfer:threads:read::@var{offset},@var{length}
37967 @anchor{qXfer threads read}
37968 Access the list of threads on target. @xref{Thread List Format}. The
37969 annex part of the generic @samp{qXfer} packet must be empty
37970 (@pxref{qXfer read}).
37972 This packet is not probed by default; the remote stub must request it,
37973 by supplying an appropriate @samp{qSupported} response (@pxref{qSupported}).
37975 @item qXfer:traceframe-info:read::@var{offset},@var{length}
37976 @anchor{qXfer traceframe info read}
37978 Return a description of the current traceframe's contents.
37979 @xref{Traceframe Info Format}. The annex part of the generic
37980 @samp{qXfer} packet must be empty (@pxref{qXfer read}).
37982 This packet is not probed by default; the remote stub must request it,
37983 by supplying an appropriate @samp{qSupported} response (@pxref{qSupported}).
37985 @item qXfer:uib:read:@var{pc}:@var{offset},@var{length}
37986 @anchor{qXfer unwind info block}
37988 Return the unwind information block for @var{pc}. This packet is used
37989 on OpenVMS/ia64 to ask the kernel unwind information.
37991 This packet is not probed by default.
37993 @item qXfer:fdpic:read:@var{annex}:@var{offset},@var{length}
37994 @anchor{qXfer fdpic loadmap read}
37995 Read contents of @code{loadmap}s on the target system. The
37996 annex, either @samp{exec} or @samp{interp}, specifies which @code{loadmap},
37997 executable @code{loadmap} or interpreter @code{loadmap} to read.
37999 This packet is not probed by default; the remote stub must request it,
38000 by supplying an appropriate @samp{qSupported} response (@pxref{qSupported}).
38002 @item qXfer:osdata:read::@var{offset},@var{length}
38003 @anchor{qXfer osdata read}
38004 Access the target's @dfn{operating system information}.
38005 @xref{Operating System Information}.
38012 Data @var{data} (@pxref{Binary Data}) has been read from the
38013 target. There may be more data at a higher address (although
38014 it is permitted to return @samp{m} even for the last valid
38015 block of data, as long as at least one byte of data was read).
38016 @var{data} may have fewer bytes than the @var{length} in the
38020 Data @var{data} (@pxref{Binary Data}) has been read from the target.
38021 There is no more data to be read. @var{data} may have fewer bytes
38022 than the @var{length} in the request.
38025 The @var{offset} in the request is at the end of the data.
38026 There is no more data to be read.
38029 The request was malformed, or @var{annex} was invalid.
38032 The offset was invalid, or there was an error encountered reading the data.
38033 @var{nn} is a hex-encoded @code{errno} value.
38036 An empty reply indicates the @var{object} string was not recognized by
38037 the stub, or that the object does not support reading.
38040 @item qXfer:@var{object}:write:@var{annex}:@var{offset}:@var{data}@dots{}
38041 @cindex write data into object, remote request
38042 @anchor{qXfer write}
38043 Write uninterpreted bytes into the target's special data area
38044 identified by the keyword @var{object}, starting at @var{offset} bytes
38045 into the data. @var{data}@dots{} is the binary-encoded data
38046 (@pxref{Binary Data}) to be written. The content and encoding of @var{annex}
38047 is specific to @var{object}; it can supply additional details about what data
38050 Here are the specific requests of this form defined so far. All
38051 @samp{qXfer:@var{object}:write:@dots{}} requests use the same reply
38052 formats, listed below.
38055 @item qXfer:siginfo:write::@var{offset}:@var{data}@dots{}
38056 @anchor{qXfer siginfo write}
38057 Write @var{data} to the extra signal information on the target system.
38058 The annex part of the generic @samp{qXfer} packet must be
38059 empty (@pxref{qXfer write}).
38061 This packet is not probed by default; the remote stub must request it,
38062 by supplying an appropriate @samp{qSupported} response
38063 (@pxref{qSupported}).
38065 @item qXfer:spu:write:@var{annex}:@var{offset}:@var{data}@dots{}
38066 @anchor{qXfer spu write}
38067 Write @var{data} to an @code{spufs} file on the target system. The
38068 annex specifies which file to write; it must be of the form
38069 @file{@var{id}/@var{name}}, where @var{id} specifies an SPU context ID
38070 in the target process, and @var{name} identifes the @code{spufs} file
38071 in that context to be accessed.
38073 This packet is not probed by default; the remote stub must request it,
38074 by supplying an appropriate @samp{qSupported} response (@pxref{qSupported}).
38080 @var{nn} (hex encoded) is the number of bytes written.
38081 This may be fewer bytes than supplied in the request.
38084 The request was malformed, or @var{annex} was invalid.
38087 The offset was invalid, or there was an error encountered writing the data.
38088 @var{nn} is a hex-encoded @code{errno} value.
38091 An empty reply indicates the @var{object} string was not
38092 recognized by the stub, or that the object does not support writing.
38095 @item qXfer:@var{object}:@var{operation}:@dots{}
38096 Requests of this form may be added in the future. When a stub does
38097 not recognize the @var{object} keyword, or its support for
38098 @var{object} does not recognize the @var{operation} keyword, the stub
38099 must respond with an empty packet.
38101 @item qAttached:@var{pid}
38102 @cindex query attached, remote request
38103 @cindex @samp{qAttached} packet
38104 Return an indication of whether the remote server attached to an
38105 existing process or created a new process. When the multiprocess
38106 protocol extensions are supported (@pxref{multiprocess extensions}),
38107 @var{pid} is an integer in hexadecimal format identifying the target
38108 process. Otherwise, @value{GDBN} will omit the @var{pid} field and
38109 the query packet will be simplified as @samp{qAttached}.
38111 This query is used, for example, to know whether the remote process
38112 should be detached or killed when a @value{GDBN} session is ended with
38113 the @code{quit} command.
38118 The remote server attached to an existing process.
38120 The remote server created a new process.
38122 A badly formed request or an error was encountered.
38126 Enable branch tracing for the current thread using bts tracing.
38131 Branch tracing has been enabled.
38133 A badly formed request or an error was encountered.
38137 Disable branch tracing for the current thread.
38142 Branch tracing has been disabled.
38144 A badly formed request or an error was encountered.
38149 @node Architecture-Specific Protocol Details
38150 @section Architecture-Specific Protocol Details
38152 This section describes how the remote protocol is applied to specific
38153 target architectures. Also see @ref{Standard Target Features}, for
38154 details of XML target descriptions for each architecture.
38157 * ARM-Specific Protocol Details::
38158 * MIPS-Specific Protocol Details::
38161 @node ARM-Specific Protocol Details
38162 @subsection @acronym{ARM}-specific Protocol Details
38165 * ARM Breakpoint Kinds::
38168 @node ARM Breakpoint Kinds
38169 @subsubsection @acronym{ARM} Breakpoint Kinds
38170 @cindex breakpoint kinds, @acronym{ARM}
38172 These breakpoint kinds are defined for the @samp{Z0} and @samp{Z1} packets.
38177 16-bit Thumb mode breakpoint.
38180 32-bit Thumb mode (Thumb-2) breakpoint.
38183 32-bit @acronym{ARM} mode breakpoint.
38187 @node MIPS-Specific Protocol Details
38188 @subsection @acronym{MIPS}-specific Protocol Details
38191 * MIPS Register packet Format::
38192 * MIPS Breakpoint Kinds::
38195 @node MIPS Register packet Format
38196 @subsubsection @acronym{MIPS} Register Packet Format
38197 @cindex register packet format, @acronym{MIPS}
38199 The following @code{g}/@code{G} packets have previously been defined.
38200 In the below, some thirty-two bit registers are transferred as
38201 sixty-four bits. Those registers should be zero/sign extended (which?)
38202 to fill the space allocated. Register bytes are transferred in target
38203 byte order. The two nibbles within a register byte are transferred
38204 most-significant -- least-significant.
38209 All registers are transferred as thirty-two bit quantities in the order:
38210 32 general-purpose; sr; lo; hi; bad; cause; pc; 32 floating-point
38211 registers; fsr; fir; fp.
38214 All registers are transferred as sixty-four bit quantities (including
38215 thirty-two bit registers such as @code{sr}). The ordering is the same
38220 @node MIPS Breakpoint Kinds
38221 @subsubsection @acronym{MIPS} Breakpoint Kinds
38222 @cindex breakpoint kinds, @acronym{MIPS}
38224 These breakpoint kinds are defined for the @samp{Z0} and @samp{Z1} packets.
38229 16-bit @acronym{MIPS16} mode breakpoint.
38232 16-bit @acronym{microMIPS} mode breakpoint.
38235 32-bit standard @acronym{MIPS} mode breakpoint.
38238 32-bit @acronym{microMIPS} mode breakpoint.
38242 @node Tracepoint Packets
38243 @section Tracepoint Packets
38244 @cindex tracepoint packets
38245 @cindex packets, tracepoint
38247 Here we describe the packets @value{GDBN} uses to implement
38248 tracepoints (@pxref{Tracepoints}).
38252 @item QTDP:@var{n}:@var{addr}:@var{ena}:@var{step}:@var{pass}[:F@var{flen}][:X@var{len},@var{bytes}]@r{[}-@r{]}
38253 @cindex @samp{QTDP} packet
38254 Create a new tracepoint, number @var{n}, at @var{addr}. If @var{ena}
38255 is @samp{E}, then the tracepoint is enabled; if it is @samp{D}, then
38256 the tracepoint is disabled. @var{step} is the tracepoint's step
38257 count, and @var{pass} is its pass count. If an @samp{F} is present,
38258 then the tracepoint is to be a fast tracepoint, and the @var{flen} is
38259 the number of bytes that the target should copy elsewhere to make room
38260 for the tracepoint. If an @samp{X} is present, it introduces a
38261 tracepoint condition, which consists of a hexadecimal length, followed
38262 by a comma and hex-encoded bytes, in a manner similar to action
38263 encodings as described below. If the trailing @samp{-} is present,
38264 further @samp{QTDP} packets will follow to specify this tracepoint's
38270 The packet was understood and carried out.
38272 @xref{Tracepoint Packets,,Relocate instruction reply packet}.
38274 The packet was not recognized.
38277 @item QTDP:-@var{n}:@var{addr}:@r{[}S@r{]}@var{action}@dots{}@r{[}-@r{]}
38278 Define actions to be taken when a tracepoint is hit. @var{n} and
38279 @var{addr} must be the same as in the initial @samp{QTDP} packet for
38280 this tracepoint. This packet may only be sent immediately after
38281 another @samp{QTDP} packet that ended with a @samp{-}. If the
38282 trailing @samp{-} is present, further @samp{QTDP} packets will follow,
38283 specifying more actions for this tracepoint.
38285 In the series of action packets for a given tracepoint, at most one
38286 can have an @samp{S} before its first @var{action}. If such a packet
38287 is sent, it and the following packets define ``while-stepping''
38288 actions. Any prior packets define ordinary actions --- that is, those
38289 taken when the tracepoint is first hit. If no action packet has an
38290 @samp{S}, then all the packets in the series specify ordinary
38291 tracepoint actions.
38293 The @samp{@var{action}@dots{}} portion of the packet is a series of
38294 actions, concatenated without separators. Each action has one of the
38300 Collect the registers whose bits are set in @var{mask}. @var{mask} is
38301 a hexadecimal number whose @var{i}'th bit is set if register number
38302 @var{i} should be collected. (The least significant bit is numbered
38303 zero.) Note that @var{mask} may be any number of digits long; it may
38304 not fit in a 32-bit word.
38306 @item M @var{basereg},@var{offset},@var{len}
38307 Collect @var{len} bytes of memory starting at the address in register
38308 number @var{basereg}, plus @var{offset}. If @var{basereg} is
38309 @samp{-1}, then the range has a fixed address: @var{offset} is the
38310 address of the lowest byte to collect. The @var{basereg},
38311 @var{offset}, and @var{len} parameters are all unsigned hexadecimal
38312 values (the @samp{-1} value for @var{basereg} is a special case).
38314 @item X @var{len},@var{expr}
38315 Evaluate @var{expr}, whose length is @var{len}, and collect memory as
38316 it directs. @var{expr} is an agent expression, as described in
38317 @ref{Agent Expressions}. Each byte of the expression is encoded as a
38318 two-digit hex number in the packet; @var{len} is the number of bytes
38319 in the expression (and thus one-half the number of hex digits in the
38324 Any number of actions may be packed together in a single @samp{QTDP}
38325 packet, as long as the packet does not exceed the maximum packet
38326 length (400 bytes, for many stubs). There may be only one @samp{R}
38327 action per tracepoint, and it must precede any @samp{M} or @samp{X}
38328 actions. Any registers referred to by @samp{M} and @samp{X} actions
38329 must be collected by a preceding @samp{R} action. (The
38330 ``while-stepping'' actions are treated as if they were attached to a
38331 separate tracepoint, as far as these restrictions are concerned.)
38336 The packet was understood and carried out.
38338 @xref{Tracepoint Packets,,Relocate instruction reply packet}.
38340 The packet was not recognized.
38343 @item QTDPsrc:@var{n}:@var{addr}:@var{type}:@var{start}:@var{slen}:@var{bytes}
38344 @cindex @samp{QTDPsrc} packet
38345 Specify a source string of tracepoint @var{n} at address @var{addr}.
38346 This is useful to get accurate reproduction of the tracepoints
38347 originally downloaded at the beginning of the trace run. @var{type}
38348 is the name of the tracepoint part, such as @samp{cond} for the
38349 tracepoint's conditional expression (see below for a list of types), while
38350 @var{bytes} is the string, encoded in hexadecimal.
38352 @var{start} is the offset of the @var{bytes} within the overall source
38353 string, while @var{slen} is the total length of the source string.
38354 This is intended for handling source strings that are longer than will
38355 fit in a single packet.
38356 @c Add detailed example when this info is moved into a dedicated
38357 @c tracepoint descriptions section.
38359 The available string types are @samp{at} for the location,
38360 @samp{cond} for the conditional, and @samp{cmd} for an action command.
38361 @value{GDBN} sends a separate packet for each command in the action
38362 list, in the same order in which the commands are stored in the list.
38364 The target does not need to do anything with source strings except
38365 report them back as part of the replies to the @samp{qTfP}/@samp{qTsP}
38368 Although this packet is optional, and @value{GDBN} will only send it
38369 if the target replies with @samp{TracepointSource} @xref{General
38370 Query Packets}, it makes both disconnected tracing and trace files
38371 much easier to use. Otherwise the user must be careful that the
38372 tracepoints in effect while looking at trace frames are identical to
38373 the ones in effect during the trace run; even a small discrepancy
38374 could cause @samp{tdump} not to work, or a particular trace frame not
38377 @item QTDV:@var{n}:@var{value}
38378 @cindex define trace state variable, remote request
38379 @cindex @samp{QTDV} packet
38380 Create a new trace state variable, number @var{n}, with an initial
38381 value of @var{value}, which is a 64-bit signed integer. Both @var{n}
38382 and @var{value} are encoded as hexadecimal values. @value{GDBN} has
38383 the option of not using this packet for initial values of zero; the
38384 target should simply create the trace state variables as they are
38385 mentioned in expressions.
38387 @item QTFrame:@var{n}
38388 @cindex @samp{QTFrame} packet
38389 Select the @var{n}'th tracepoint frame from the buffer, and use the
38390 register and memory contents recorded there to answer subsequent
38391 request packets from @value{GDBN}.
38393 A successful reply from the stub indicates that the stub has found the
38394 requested frame. The response is a series of parts, concatenated
38395 without separators, describing the frame we selected. Each part has
38396 one of the following forms:
38400 The selected frame is number @var{n} in the trace frame buffer;
38401 @var{f} is a hexadecimal number. If @var{f} is @samp{-1}, then there
38402 was no frame matching the criteria in the request packet.
38405 The selected trace frame records a hit of tracepoint number @var{t};
38406 @var{t} is a hexadecimal number.
38410 @item QTFrame:pc:@var{addr}
38411 Like @samp{QTFrame:@var{n}}, but select the first tracepoint frame after the
38412 currently selected frame whose PC is @var{addr};
38413 @var{addr} is a hexadecimal number.
38415 @item QTFrame:tdp:@var{t}
38416 Like @samp{QTFrame:@var{n}}, but select the first tracepoint frame after the
38417 currently selected frame that is a hit of tracepoint @var{t}; @var{t}
38418 is a hexadecimal number.
38420 @item QTFrame:range:@var{start}:@var{end}
38421 Like @samp{QTFrame:@var{n}}, but select the first tracepoint frame after the
38422 currently selected frame whose PC is between @var{start} (inclusive)
38423 and @var{end} (inclusive); @var{start} and @var{end} are hexadecimal
38426 @item QTFrame:outside:@var{start}:@var{end}
38427 Like @samp{QTFrame:range:@var{start}:@var{end}}, but select the first
38428 frame @emph{outside} the given range of addresses (exclusive).
38431 @cindex @samp{qTMinFTPILen} packet
38432 This packet requests the minimum length of instruction at which a fast
38433 tracepoint (@pxref{Set Tracepoints}) may be placed. For instance, on
38434 the 32-bit x86 architecture, it is possible to use a 4-byte jump, but
38435 it depends on the target system being able to create trampolines in
38436 the first 64K of memory, which might or might not be possible for that
38437 system. So the reply to this packet will be 4 if it is able to
38444 The minimum instruction length is currently unknown.
38446 The minimum instruction length is @var{length}, where @var{length} is greater
38447 or equal to 1. @var{length} is a hexadecimal number. A reply of 1 means
38448 that a fast tracepoint may be placed on any instruction regardless of size.
38450 An error has occurred.
38452 An empty reply indicates that the request is not supported by the stub.
38456 @cindex @samp{QTStart} packet
38457 Begin the tracepoint experiment. Begin collecting data from
38458 tracepoint hits in the trace frame buffer. This packet supports the
38459 @samp{qRelocInsn} reply (@pxref{Tracepoint Packets,,Relocate
38460 instruction reply packet}).
38463 @cindex @samp{QTStop} packet
38464 End the tracepoint experiment. Stop collecting trace frames.
38466 @item QTEnable:@var{n}:@var{addr}
38468 @cindex @samp{QTEnable} packet
38469 Enable tracepoint @var{n} at address @var{addr} in a started tracepoint
38470 experiment. If the tracepoint was previously disabled, then collection
38471 of data from it will resume.
38473 @item QTDisable:@var{n}:@var{addr}
38475 @cindex @samp{QTDisable} packet
38476 Disable tracepoint @var{n} at address @var{addr} in a started tracepoint
38477 experiment. No more data will be collected from the tracepoint unless
38478 @samp{QTEnable:@var{n}:@var{addr}} is subsequently issued.
38481 @cindex @samp{QTinit} packet
38482 Clear the table of tracepoints, and empty the trace frame buffer.
38484 @item QTro:@var{start1},@var{end1}:@var{start2},@var{end2}:@dots{}
38485 @cindex @samp{QTro} packet
38486 Establish the given ranges of memory as ``transparent''. The stub
38487 will answer requests for these ranges from memory's current contents,
38488 if they were not collected as part of the tracepoint hit.
38490 @value{GDBN} uses this to mark read-only regions of memory, like those
38491 containing program code. Since these areas never change, they should
38492 still have the same contents they did when the tracepoint was hit, so
38493 there's no reason for the stub to refuse to provide their contents.
38495 @item QTDisconnected:@var{value}
38496 @cindex @samp{QTDisconnected} packet
38497 Set the choice to what to do with the tracing run when @value{GDBN}
38498 disconnects from the target. A @var{value} of 1 directs the target to
38499 continue the tracing run, while 0 tells the target to stop tracing if
38500 @value{GDBN} is no longer in the picture.
38503 @cindex @samp{qTStatus} packet
38504 Ask the stub if there is a trace experiment running right now.
38506 The reply has the form:
38510 @item T@var{running}@r{[};@var{field}@r{]}@dots{}
38511 @var{running} is a single digit @code{1} if the trace is presently
38512 running, or @code{0} if not. It is followed by semicolon-separated
38513 optional fields that an agent may use to report additional status.
38517 If the trace is not running, the agent may report any of several
38518 explanations as one of the optional fields:
38523 No trace has been run yet.
38525 @item tstop[:@var{text}]:0
38526 The trace was stopped by a user-originated stop command. The optional
38527 @var{text} field is a user-supplied string supplied as part of the
38528 stop command (for instance, an explanation of why the trace was
38529 stopped manually). It is hex-encoded.
38532 The trace stopped because the trace buffer filled up.
38534 @item tdisconnected:0
38535 The trace stopped because @value{GDBN} disconnected from the target.
38537 @item tpasscount:@var{tpnum}
38538 The trace stopped because tracepoint @var{tpnum} exceeded its pass count.
38540 @item terror:@var{text}:@var{tpnum}
38541 The trace stopped because tracepoint @var{tpnum} had an error. The
38542 string @var{text} is available to describe the nature of the error
38543 (for instance, a divide by zero in the condition expression).
38544 @var{text} is hex encoded.
38547 The trace stopped for some other reason.
38551 Additional optional fields supply statistical and other information.
38552 Although not required, they are extremely useful for users monitoring
38553 the progress of a trace run. If a trace has stopped, and these
38554 numbers are reported, they must reflect the state of the just-stopped
38559 @item tframes:@var{n}
38560 The number of trace frames in the buffer.
38562 @item tcreated:@var{n}
38563 The total number of trace frames created during the run. This may
38564 be larger than the trace frame count, if the buffer is circular.
38566 @item tsize:@var{n}
38567 The total size of the trace buffer, in bytes.
38569 @item tfree:@var{n}
38570 The number of bytes still unused in the buffer.
38572 @item circular:@var{n}
38573 The value of the circular trace buffer flag. @code{1} means that the
38574 trace buffer is circular and old trace frames will be discarded if
38575 necessary to make room, @code{0} means that the trace buffer is linear
38578 @item disconn:@var{n}
38579 The value of the disconnected tracing flag. @code{1} means that
38580 tracing will continue after @value{GDBN} disconnects, @code{0} means
38581 that the trace run will stop.
38585 @item qTP:@var{tp}:@var{addr}
38586 @cindex tracepoint status, remote request
38587 @cindex @samp{qTP} packet
38588 Ask the stub for the current state of tracepoint number @var{tp} at
38589 address @var{addr}.
38593 @item V@var{hits}:@var{usage}
38594 The tracepoint has been hit @var{hits} times so far during the trace
38595 run, and accounts for @var{usage} in the trace buffer. Note that
38596 @code{while-stepping} steps are not counted as separate hits, but the
38597 steps' space consumption is added into the usage number.
38601 @item qTV:@var{var}
38602 @cindex trace state variable value, remote request
38603 @cindex @samp{qTV} packet
38604 Ask the stub for the value of the trace state variable number @var{var}.
38609 The value of the variable is @var{value}. This will be the current
38610 value of the variable if the user is examining a running target, or a
38611 saved value if the variable was collected in the trace frame that the
38612 user is looking at. Note that multiple requests may result in
38613 different reply values, such as when requesting values while the
38614 program is running.
38617 The value of the variable is unknown. This would occur, for example,
38618 if the user is examining a trace frame in which the requested variable
38623 @cindex @samp{qTfP} packet
38625 @cindex @samp{qTsP} packet
38626 These packets request data about tracepoints that are being used by
38627 the target. @value{GDBN} sends @code{qTfP} to get the first piece
38628 of data, and multiple @code{qTsP} to get additional pieces. Replies
38629 to these packets generally take the form of the @code{QTDP} packets
38630 that define tracepoints. (FIXME add detailed syntax)
38633 @cindex @samp{qTfV} packet
38635 @cindex @samp{qTsV} packet
38636 These packets request data about trace state variables that are on the
38637 target. @value{GDBN} sends @code{qTfV} to get the first vari of data,
38638 and multiple @code{qTsV} to get additional variables. Replies to
38639 these packets follow the syntax of the @code{QTDV} packets that define
38640 trace state variables.
38646 @cindex @samp{qTfSTM} packet
38647 @cindex @samp{qTsSTM} packet
38648 These packets request data about static tracepoint markers that exist
38649 in the target program. @value{GDBN} sends @code{qTfSTM} to get the
38650 first piece of data, and multiple @code{qTsSTM} to get additional
38651 pieces. Replies to these packets take the following form:
38655 @item m @var{address}:@var{id}:@var{extra}
38657 @item m @var{address}:@var{id}:@var{extra},@var{address}:@var{id}:@var{extra}@dots{}
38658 a comma-separated list of markers
38660 (lower case letter @samp{L}) denotes end of list.
38662 An error occurred. @var{nn} are hex digits.
38664 An empty reply indicates that the request is not supported by the
38668 @var{address} is encoded in hex.
38669 @var{id} and @var{extra} are strings encoded in hex.
38671 In response to each query, the target will reply with a list of one or
38672 more markers, separated by commas. @value{GDBN} will respond to each
38673 reply with a request for more markers (using the @samp{qs} form of the
38674 query), until the target responds with @samp{l} (lower-case ell, for
38677 @item qTSTMat:@var{address}
38679 @cindex @samp{qTSTMat} packet
38680 This packets requests data about static tracepoint markers in the
38681 target program at @var{address}. Replies to this packet follow the
38682 syntax of the @samp{qTfSTM} and @code{qTsSTM} packets that list static
38683 tracepoint markers.
38685 @item QTSave:@var{filename}
38686 @cindex @samp{QTSave} packet
38687 This packet directs the target to save trace data to the file name
38688 @var{filename} in the target's filesystem. @var{filename} is encoded
38689 as a hex string; the interpretation of the file name (relative vs
38690 absolute, wild cards, etc) is up to the target.
38692 @item qTBuffer:@var{offset},@var{len}
38693 @cindex @samp{qTBuffer} packet
38694 Return up to @var{len} bytes of the current contents of trace buffer,
38695 starting at @var{offset}. The trace buffer is treated as if it were
38696 a contiguous collection of traceframes, as per the trace file format.
38697 The reply consists as many hex-encoded bytes as the target can deliver
38698 in a packet; it is not an error to return fewer than were asked for.
38699 A reply consisting of just @code{l} indicates that no bytes are
38702 @item QTBuffer:circular:@var{value}
38703 This packet directs the target to use a circular trace buffer if
38704 @var{value} is 1, or a linear buffer if the value is 0.
38706 @item QTBuffer:size:@var{size}
38707 @anchor{QTBuffer-size}
38708 @cindex @samp{QTBuffer size} packet
38709 This packet directs the target to make the trace buffer be of size
38710 @var{size} if possible. A value of @code{-1} tells the target to
38711 use whatever size it prefers.
38713 @item QTNotes:@r{[}@var{type}:@var{text}@r{]}@r{[};@var{type}:@var{text}@r{]}@dots{}
38714 @cindex @samp{QTNotes} packet
38715 This packet adds optional textual notes to the trace run. Allowable
38716 types include @code{user}, @code{notes}, and @code{tstop}, the
38717 @var{text} fields are arbitrary strings, hex-encoded.
38721 @subsection Relocate instruction reply packet
38722 When installing fast tracepoints in memory, the target may need to
38723 relocate the instruction currently at the tracepoint address to a
38724 different address in memory. For most instructions, a simple copy is
38725 enough, but, for example, call instructions that implicitly push the
38726 return address on the stack, and relative branches or other
38727 PC-relative instructions require offset adjustment, so that the effect
38728 of executing the instruction at a different address is the same as if
38729 it had executed in the original location.
38731 In response to several of the tracepoint packets, the target may also
38732 respond with a number of intermediate @samp{qRelocInsn} request
38733 packets before the final result packet, to have @value{GDBN} handle
38734 this relocation operation. If a packet supports this mechanism, its
38735 documentation will explicitly say so. See for example the above
38736 descriptions for the @samp{QTStart} and @samp{QTDP} packets. The
38737 format of the request is:
38740 @item qRelocInsn:@var{from};@var{to}
38742 This requests @value{GDBN} to copy instruction at address @var{from}
38743 to address @var{to}, possibly adjusted so that executing the
38744 instruction at @var{to} has the same effect as executing it at
38745 @var{from}. @value{GDBN} writes the adjusted instruction to target
38746 memory starting at @var{to}.
38751 @item qRelocInsn:@var{adjusted_size}
38752 Informs the stub the relocation is complete. @var{adjusted_size} is
38753 the length in bytes of resulting relocated instruction sequence.
38755 A badly formed request was detected, or an error was encountered while
38756 relocating the instruction.
38759 @node Host I/O Packets
38760 @section Host I/O Packets
38761 @cindex Host I/O, remote protocol
38762 @cindex file transfer, remote protocol
38764 The @dfn{Host I/O} packets allow @value{GDBN} to perform I/O
38765 operations on the far side of a remote link. For example, Host I/O is
38766 used to upload and download files to a remote target with its own
38767 filesystem. Host I/O uses the same constant values and data structure
38768 layout as the target-initiated File-I/O protocol. However, the
38769 Host I/O packets are structured differently. The target-initiated
38770 protocol relies on target memory to store parameters and buffers.
38771 Host I/O requests are initiated by @value{GDBN}, and the
38772 target's memory is not involved. @xref{File-I/O Remote Protocol
38773 Extension}, for more details on the target-initiated protocol.
38775 The Host I/O request packets all encode a single operation along with
38776 its arguments. They have this format:
38780 @item vFile:@var{operation}: @var{parameter}@dots{}
38781 @var{operation} is the name of the particular request; the target
38782 should compare the entire packet name up to the second colon when checking
38783 for a supported operation. The format of @var{parameter} depends on
38784 the operation. Numbers are always passed in hexadecimal. Negative
38785 numbers have an explicit minus sign (i.e.@: two's complement is not
38786 used). Strings (e.g.@: filenames) are encoded as a series of
38787 hexadecimal bytes. The last argument to a system call may be a
38788 buffer of escaped binary data (@pxref{Binary Data}).
38792 The valid responses to Host I/O packets are:
38796 @item F @var{result} [, @var{errno}] [; @var{attachment}]
38797 @var{result} is the integer value returned by this operation, usually
38798 non-negative for success and -1 for errors. If an error has occured,
38799 @var{errno} will be included in the result. @var{errno} will have a
38800 value defined by the File-I/O protocol (@pxref{Errno Values}). For
38801 operations which return data, @var{attachment} supplies the data as a
38802 binary buffer. Binary buffers in response packets are escaped in the
38803 normal way (@pxref{Binary Data}). See the individual packet
38804 documentation for the interpretation of @var{result} and
38808 An empty response indicates that this operation is not recognized.
38812 These are the supported Host I/O operations:
38815 @item vFile:open: @var{pathname}, @var{flags}, @var{mode}
38816 Open a file at @var{pathname} and return a file descriptor for it, or
38817 return -1 if an error occurs. @var{pathname} is a string,
38818 @var{flags} is an integer indicating a mask of open flags
38819 (@pxref{Open Flags}), and @var{mode} is an integer indicating a mask
38820 of mode bits to use if the file is created (@pxref{mode_t Values}).
38821 @xref{open}, for details of the open flags and mode values.
38823 @item vFile:close: @var{fd}
38824 Close the open file corresponding to @var{fd} and return 0, or
38825 -1 if an error occurs.
38827 @item vFile:pread: @var{fd}, @var{count}, @var{offset}
38828 Read data from the open file corresponding to @var{fd}. Up to
38829 @var{count} bytes will be read from the file, starting at @var{offset}
38830 relative to the start of the file. The target may read fewer bytes;
38831 common reasons include packet size limits and an end-of-file
38832 condition. The number of bytes read is returned. Zero should only be
38833 returned for a successful read at the end of the file, or if
38834 @var{count} was zero.
38836 The data read should be returned as a binary attachment on success.
38837 If zero bytes were read, the response should include an empty binary
38838 attachment (i.e.@: a trailing semicolon). The return value is the
38839 number of target bytes read; the binary attachment may be longer if
38840 some characters were escaped.
38842 @item vFile:pwrite: @var{fd}, @var{offset}, @var{data}
38843 Write @var{data} (a binary buffer) to the open file corresponding
38844 to @var{fd}. Start the write at @var{offset} from the start of the
38845 file. Unlike many @code{write} system calls, there is no
38846 separate @var{count} argument; the length of @var{data} in the
38847 packet is used. @samp{vFile:write} returns the number of bytes written,
38848 which may be shorter than the length of @var{data}, or -1 if an
38851 @item vFile:unlink: @var{pathname}
38852 Delete the file at @var{pathname} on the target. Return 0,
38853 or -1 if an error occurs. @var{pathname} is a string.
38855 @item vFile:readlink: @var{filename}
38856 Read value of symbolic link @var{filename} on the target. Return
38857 the number of bytes read, or -1 if an error occurs.
38859 The data read should be returned as a binary attachment on success.
38860 If zero bytes were read, the response should include an empty binary
38861 attachment (i.e.@: a trailing semicolon). The return value is the
38862 number of target bytes read; the binary attachment may be longer if
38863 some characters were escaped.
38868 @section Interrupts
38869 @cindex interrupts (remote protocol)
38871 When a program on the remote target is running, @value{GDBN} may
38872 attempt to interrupt it by sending a @samp{Ctrl-C}, @code{BREAK} or
38873 a @code{BREAK} followed by @code{g},
38874 control of which is specified via @value{GDBN}'s @samp{interrupt-sequence}.
38876 The precise meaning of @code{BREAK} is defined by the transport
38877 mechanism and may, in fact, be undefined. @value{GDBN} does not
38878 currently define a @code{BREAK} mechanism for any of the network
38879 interfaces except for TCP, in which case @value{GDBN} sends the
38880 @code{telnet} BREAK sequence.
38882 @samp{Ctrl-C}, on the other hand, is defined and implemented for all
38883 transport mechanisms. It is represented by sending the single byte
38884 @code{0x03} without any of the usual packet overhead described in
38885 the Overview section (@pxref{Overview}). When a @code{0x03} byte is
38886 transmitted as part of a packet, it is considered to be packet data
38887 and does @emph{not} represent an interrupt. E.g., an @samp{X} packet
38888 (@pxref{X packet}), used for binary downloads, may include an unescaped
38889 @code{0x03} as part of its packet.
38891 @code{BREAK} followed by @code{g} is also known as Magic SysRq g.
38892 When Linux kernel receives this sequence from serial port,
38893 it stops execution and connects to gdb.
38895 Stubs are not required to recognize these interrupt mechanisms and the
38896 precise meaning associated with receipt of the interrupt is
38897 implementation defined. If the target supports debugging of multiple
38898 threads and/or processes, it should attempt to interrupt all
38899 currently-executing threads and processes.
38900 If the stub is successful at interrupting the
38901 running program, it should send one of the stop
38902 reply packets (@pxref{Stop Reply Packets}) to @value{GDBN} as a result
38903 of successfully stopping the program in all-stop mode, and a stop reply
38904 for each stopped thread in non-stop mode.
38905 Interrupts received while the
38906 program is stopped are discarded.
38908 @node Notification Packets
38909 @section Notification Packets
38910 @cindex notification packets
38911 @cindex packets, notification
38913 The @value{GDBN} remote serial protocol includes @dfn{notifications},
38914 packets that require no acknowledgment. Both the GDB and the stub
38915 may send notifications (although the only notifications defined at
38916 present are sent by the stub). Notifications carry information
38917 without incurring the round-trip latency of an acknowledgment, and so
38918 are useful for low-impact communications where occasional packet loss
38921 A notification packet has the form @samp{% @var{data} #
38922 @var{checksum}}, where @var{data} is the content of the notification,
38923 and @var{checksum} is a checksum of @var{data}, computed and formatted
38924 as for ordinary @value{GDBN} packets. A notification's @var{data}
38925 never contains @samp{$}, @samp{%} or @samp{#} characters. Upon
38926 receiving a notification, the recipient sends no @samp{+} or @samp{-}
38927 to acknowledge the notification's receipt or to report its corruption.
38929 Every notification's @var{data} begins with a name, which contains no
38930 colon characters, followed by a colon character.
38932 Recipients should silently ignore corrupted notifications and
38933 notifications they do not understand. Recipients should restart
38934 timeout periods on receipt of a well-formed notification, whether or
38935 not they understand it.
38937 Senders should only send the notifications described here when this
38938 protocol description specifies that they are permitted. In the
38939 future, we may extend the protocol to permit existing notifications in
38940 new contexts; this rule helps older senders avoid confusing newer
38943 (Older versions of @value{GDBN} ignore bytes received until they see
38944 the @samp{$} byte that begins an ordinary packet, so new stubs may
38945 transmit notifications without fear of confusing older clients. There
38946 are no notifications defined for @value{GDBN} to send at the moment, but we
38947 assume that most older stubs would ignore them, as well.)
38949 Each notification is comprised of three parts:
38951 @item @var{name}:@var{event}
38952 The notification packet is sent by the side that initiates the
38953 exchange (currently, only the stub does that), with @var{event}
38954 carrying the specific information about the notification.
38955 @var{name} is the name of the notification.
38957 The acknowledge sent by the other side, usually @value{GDBN}, to
38958 acknowledge the exchange and request the event.
38961 The purpose of an asynchronous notification mechanism is to report to
38962 @value{GDBN} that something interesting happened in the remote stub.
38964 The remote stub may send notification @var{name}:@var{event}
38965 at any time, but @value{GDBN} acknowledges the notification when
38966 appropriate. The notification event is pending before @value{GDBN}
38967 acknowledges. Only one notification at a time may be pending; if
38968 additional events occur before @value{GDBN} has acknowledged the
38969 previous notification, they must be queued by the stub for later
38970 synchronous transmission in response to @var{ack} packets from
38971 @value{GDBN}. Because the notification mechanism is unreliable,
38972 the stub is permitted to resend a notification if it believes
38973 @value{GDBN} may not have received it.
38975 Specifically, notifications may appear when @value{GDBN} is not
38976 otherwise reading input from the stub, or when @value{GDBN} is
38977 expecting to read a normal synchronous response or a
38978 @samp{+}/@samp{-} acknowledgment to a packet it has sent.
38979 Notification packets are distinct from any other communication from
38980 the stub so there is no ambiguity.
38982 After receiving a notification, @value{GDBN} shall acknowledge it by
38983 sending a @var{ack} packet as a regular, synchronous request to the
38984 stub. Such acknowledgment is not required to happen immediately, as
38985 @value{GDBN} is permitted to send other, unrelated packets to the
38986 stub first, which the stub should process normally.
38988 Upon receiving a @var{ack} packet, if the stub has other queued
38989 events to report to @value{GDBN}, it shall respond by sending a
38990 normal @var{event}. @value{GDBN} shall then send another @var{ack}
38991 packet to solicit further responses; again, it is permitted to send
38992 other, unrelated packets as well which the stub should process
38995 If the stub receives a @var{ack} packet and there are no additional
38996 @var{event} to report, the stub shall return an @samp{OK} response.
38997 At this point, @value{GDBN} has finished processing a notification
38998 and the stub has completed sending any queued events. @value{GDBN}
38999 won't accept any new notifications until the final @samp{OK} is
39000 received . If further notification events occur, the stub shall send
39001 a new notification, @value{GDBN} shall accept the notification, and
39002 the process shall be repeated.
39004 The process of asynchronous notification can be illustrated by the
39007 <- @code{%%Stop:T0505:98e7ffbf;04:4ce6ffbf;08:b1b6e54c;thread:p7526.7526;core:0;}
39010 <- @code{T0505:68f37db7;04:40f37db7;08:63850408;thread:p7526.7528;core:0;}
39012 <- @code{T0505:68e3fdb6;04:40e3fdb6;08:63850408;thread:p7526.7529;core:0;}
39017 The following notifications are defined:
39018 @multitable @columnfractions 0.12 0.12 0.38 0.38
39027 @tab @var{reply}. The @var{reply} has the form of a stop reply, as
39028 described in @ref{Stop Reply Packets}. Refer to @ref{Remote Non-Stop},
39029 for information on how these notifications are acknowledged by
39031 @tab Report an asynchronous stop event in non-stop mode.
39035 @node Remote Non-Stop
39036 @section Remote Protocol Support for Non-Stop Mode
39038 @value{GDBN}'s remote protocol supports non-stop debugging of
39039 multi-threaded programs, as described in @ref{Non-Stop Mode}. If the stub
39040 supports non-stop mode, it should report that to @value{GDBN} by including
39041 @samp{QNonStop+} in its @samp{qSupported} response (@pxref{qSupported}).
39043 @value{GDBN} typically sends a @samp{QNonStop} packet only when
39044 establishing a new connection with the stub. Entering non-stop mode
39045 does not alter the state of any currently-running threads, but targets
39046 must stop all threads in any already-attached processes when entering
39047 all-stop mode. @value{GDBN} uses the @samp{?} packet as necessary to
39048 probe the target state after a mode change.
39050 In non-stop mode, when an attached process encounters an event that
39051 would otherwise be reported with a stop reply, it uses the
39052 asynchronous notification mechanism (@pxref{Notification Packets}) to
39053 inform @value{GDBN}. In contrast to all-stop mode, where all threads
39054 in all processes are stopped when a stop reply is sent, in non-stop
39055 mode only the thread reporting the stop event is stopped. That is,
39056 when reporting a @samp{S} or @samp{T} response to indicate completion
39057 of a step operation, hitting a breakpoint, or a fault, only the
39058 affected thread is stopped; any other still-running threads continue
39059 to run. When reporting a @samp{W} or @samp{X} response, all running
39060 threads belonging to other attached processes continue to run.
39062 In non-stop mode, the target shall respond to the @samp{?} packet as
39063 follows. First, any incomplete stop reply notification/@samp{vStopped}
39064 sequence in progress is abandoned. The target must begin a new
39065 sequence reporting stop events for all stopped threads, whether or not
39066 it has previously reported those events to @value{GDBN}. The first
39067 stop reply is sent as a synchronous reply to the @samp{?} packet, and
39068 subsequent stop replies are sent as responses to @samp{vStopped} packets
39069 using the mechanism described above. The target must not send
39070 asynchronous stop reply notifications until the sequence is complete.
39071 If all threads are running when the target receives the @samp{?} packet,
39072 or if the target is not attached to any process, it shall respond
39075 @node Packet Acknowledgment
39076 @section Packet Acknowledgment
39078 @cindex acknowledgment, for @value{GDBN} remote
39079 @cindex packet acknowledgment, for @value{GDBN} remote
39080 By default, when either the host or the target machine receives a packet,
39081 the first response expected is an acknowledgment: either @samp{+} (to indicate
39082 the package was received correctly) or @samp{-} (to request retransmission).
39083 This mechanism allows the @value{GDBN} remote protocol to operate over
39084 unreliable transport mechanisms, such as a serial line.
39086 In cases where the transport mechanism is itself reliable (such as a pipe or
39087 TCP connection), the @samp{+}/@samp{-} acknowledgments are redundant.
39088 It may be desirable to disable them in that case to reduce communication
39089 overhead, or for other reasons. This can be accomplished by means of the
39090 @samp{QStartNoAckMode} packet; @pxref{QStartNoAckMode}.
39092 When in no-acknowledgment mode, neither the stub nor @value{GDBN} shall send or
39093 expect @samp{+}/@samp{-} protocol acknowledgments. The packet
39094 and response format still includes the normal checksum, as described in
39095 @ref{Overview}, but the checksum may be ignored by the receiver.
39097 If the stub supports @samp{QStartNoAckMode} and prefers to operate in
39098 no-acknowledgment mode, it should report that to @value{GDBN}
39099 by including @samp{QStartNoAckMode+} in its response to @samp{qSupported};
39100 @pxref{qSupported}.
39101 If @value{GDBN} also supports @samp{QStartNoAckMode} and it has not been
39102 disabled via the @code{set remote noack-packet off} command
39103 (@pxref{Remote Configuration}),
39104 @value{GDBN} may then send a @samp{QStartNoAckMode} packet to the stub.
39105 Only then may the stub actually turn off packet acknowledgments.
39106 @value{GDBN} sends a final @samp{+} acknowledgment of the stub's @samp{OK}
39107 response, which can be safely ignored by the stub.
39109 Note that @code{set remote noack-packet} command only affects negotiation
39110 between @value{GDBN} and the stub when subsequent connections are made;
39111 it does not affect the protocol acknowledgment state for any current
39113 Since @samp{+}/@samp{-} acknowledgments are enabled by default when a
39114 new connection is established,
39115 there is also no protocol request to re-enable the acknowledgments
39116 for the current connection, once disabled.
39121 Example sequence of a target being re-started. Notice how the restart
39122 does not get any direct output:
39127 @emph{target restarts}
39130 <- @code{T001:1234123412341234}
39134 Example sequence of a target being stepped by a single instruction:
39137 -> @code{G1445@dots{}}
39142 <- @code{T001:1234123412341234}
39146 <- @code{1455@dots{}}
39150 @node File-I/O Remote Protocol Extension
39151 @section File-I/O Remote Protocol Extension
39152 @cindex File-I/O remote protocol extension
39155 * File-I/O Overview::
39156 * Protocol Basics::
39157 * The F Request Packet::
39158 * The F Reply Packet::
39159 * The Ctrl-C Message::
39161 * List of Supported Calls::
39162 * Protocol-specific Representation of Datatypes::
39164 * File-I/O Examples::
39167 @node File-I/O Overview
39168 @subsection File-I/O Overview
39169 @cindex file-i/o overview
39171 The @dfn{File I/O remote protocol extension} (short: File-I/O) allows the
39172 target to use the host's file system and console I/O to perform various
39173 system calls. System calls on the target system are translated into a
39174 remote protocol packet to the host system, which then performs the needed
39175 actions and returns a response packet to the target system.
39176 This simulates file system operations even on targets that lack file systems.
39178 The protocol is defined to be independent of both the host and target systems.
39179 It uses its own internal representation of datatypes and values. Both
39180 @value{GDBN} and the target's @value{GDBN} stub are responsible for
39181 translating the system-dependent value representations into the internal
39182 protocol representations when data is transmitted.
39184 The communication is synchronous. A system call is possible only when
39185 @value{GDBN} is waiting for a response from the @samp{C}, @samp{c}, @samp{S}
39186 or @samp{s} packets. While @value{GDBN} handles the request for a system call,
39187 the target is stopped to allow deterministic access to the target's
39188 memory. Therefore File-I/O is not interruptible by target signals. On
39189 the other hand, it is possible to interrupt File-I/O by a user interrupt
39190 (@samp{Ctrl-C}) within @value{GDBN}.
39192 The target's request to perform a host system call does not finish
39193 the latest @samp{C}, @samp{c}, @samp{S} or @samp{s} action. That means,
39194 after finishing the system call, the target returns to continuing the
39195 previous activity (continue, step). No additional continue or step
39196 request from @value{GDBN} is required.
39199 (@value{GDBP}) continue
39200 <- target requests 'system call X'
39201 target is stopped, @value{GDBN} executes system call
39202 -> @value{GDBN} returns result
39203 ... target continues, @value{GDBN} returns to wait for the target
39204 <- target hits breakpoint and sends a Txx packet
39207 The protocol only supports I/O on the console and to regular files on
39208 the host file system. Character or block special devices, pipes,
39209 named pipes, sockets or any other communication method on the host
39210 system are not supported by this protocol.
39212 File I/O is not supported in non-stop mode.
39214 @node Protocol Basics
39215 @subsection Protocol Basics
39216 @cindex protocol basics, file-i/o
39218 The File-I/O protocol uses the @code{F} packet as the request as well
39219 as reply packet. Since a File-I/O system call can only occur when
39220 @value{GDBN} is waiting for a response from the continuing or stepping target,
39221 the File-I/O request is a reply that @value{GDBN} has to expect as a result
39222 of a previous @samp{C}, @samp{c}, @samp{S} or @samp{s} packet.
39223 This @code{F} packet contains all information needed to allow @value{GDBN}
39224 to call the appropriate host system call:
39228 A unique identifier for the requested system call.
39231 All parameters to the system call. Pointers are given as addresses
39232 in the target memory address space. Pointers to strings are given as
39233 pointer/length pair. Numerical values are given as they are.
39234 Numerical control flags are given in a protocol-specific representation.
39238 At this point, @value{GDBN} has to perform the following actions.
39242 If the parameters include pointer values to data needed as input to a
39243 system call, @value{GDBN} requests this data from the target with a
39244 standard @code{m} packet request. This additional communication has to be
39245 expected by the target implementation and is handled as any other @code{m}
39249 @value{GDBN} translates all value from protocol representation to host
39250 representation as needed. Datatypes are coerced into the host types.
39253 @value{GDBN} calls the system call.
39256 It then coerces datatypes back to protocol representation.
39259 If the system call is expected to return data in buffer space specified
39260 by pointer parameters to the call, the data is transmitted to the
39261 target using a @code{M} or @code{X} packet. This packet has to be expected
39262 by the target implementation and is handled as any other @code{M} or @code{X}
39267 Eventually @value{GDBN} replies with another @code{F} packet which contains all
39268 necessary information for the target to continue. This at least contains
39275 @code{errno}, if has been changed by the system call.
39282 After having done the needed type and value coercion, the target continues
39283 the latest continue or step action.
39285 @node The F Request Packet
39286 @subsection The @code{F} Request Packet
39287 @cindex file-i/o request packet
39288 @cindex @code{F} request packet
39290 The @code{F} request packet has the following format:
39293 @item F@var{call-id},@var{parameter@dots{}}
39295 @var{call-id} is the identifier to indicate the host system call to be called.
39296 This is just the name of the function.
39298 @var{parameter@dots{}} are the parameters to the system call.
39299 Parameters are hexadecimal integer values, either the actual values in case
39300 of scalar datatypes, pointers to target buffer space in case of compound
39301 datatypes and unspecified memory areas, or pointer/length pairs in case
39302 of string parameters. These are appended to the @var{call-id} as a
39303 comma-delimited list. All values are transmitted in ASCII
39304 string representation, pointer/length pairs separated by a slash.
39310 @node The F Reply Packet
39311 @subsection The @code{F} Reply Packet
39312 @cindex file-i/o reply packet
39313 @cindex @code{F} reply packet
39315 The @code{F} reply packet has the following format:
39319 @item F@var{retcode},@var{errno},@var{Ctrl-C flag};@var{call-specific attachment}
39321 @var{retcode} is the return code of the system call as hexadecimal value.
39323 @var{errno} is the @code{errno} set by the call, in protocol-specific
39325 This parameter can be omitted if the call was successful.
39327 @var{Ctrl-C flag} is only sent if the user requested a break. In this
39328 case, @var{errno} must be sent as well, even if the call was successful.
39329 The @var{Ctrl-C flag} itself consists of the character @samp{C}:
39336 or, if the call was interrupted before the host call has been performed:
39343 assuming 4 is the protocol-specific representation of @code{EINTR}.
39348 @node The Ctrl-C Message
39349 @subsection The @samp{Ctrl-C} Message
39350 @cindex ctrl-c message, in file-i/o protocol
39352 If the @samp{Ctrl-C} flag is set in the @value{GDBN}
39353 reply packet (@pxref{The F Reply Packet}),
39354 the target should behave as if it had
39355 gotten a break message. The meaning for the target is ``system call
39356 interrupted by @code{SIGINT}''. Consequentially, the target should actually stop
39357 (as with a break message) and return to @value{GDBN} with a @code{T02}
39360 It's important for the target to know in which
39361 state the system call was interrupted. There are two possible cases:
39365 The system call hasn't been performed on the host yet.
39368 The system call on the host has been finished.
39372 These two states can be distinguished by the target by the value of the
39373 returned @code{errno}. If it's the protocol representation of @code{EINTR}, the system
39374 call hasn't been performed. This is equivalent to the @code{EINTR} handling
39375 on POSIX systems. In any other case, the target may presume that the
39376 system call has been finished --- successfully or not --- and should behave
39377 as if the break message arrived right after the system call.
39379 @value{GDBN} must behave reliably. If the system call has not been called
39380 yet, @value{GDBN} may send the @code{F} reply immediately, setting @code{EINTR} as
39381 @code{errno} in the packet. If the system call on the host has been finished
39382 before the user requests a break, the full action must be finished by
39383 @value{GDBN}. This requires sending @code{M} or @code{X} packets as necessary.
39384 The @code{F} packet may only be sent when either nothing has happened
39385 or the full action has been completed.
39388 @subsection Console I/O
39389 @cindex console i/o as part of file-i/o
39391 By default and if not explicitly closed by the target system, the file
39392 descriptors 0, 1 and 2 are connected to the @value{GDBN} console. Output
39393 on the @value{GDBN} console is handled as any other file output operation
39394 (@code{write(1, @dots{})} or @code{write(2, @dots{})}). Console input is handled
39395 by @value{GDBN} so that after the target read request from file descriptor
39396 0 all following typing is buffered until either one of the following
39401 The user types @kbd{Ctrl-c}. The behaviour is as explained above, and the
39403 system call is treated as finished.
39406 The user presses @key{RET}. This is treated as end of input with a trailing
39410 The user types @kbd{Ctrl-d}. This is treated as end of input. No trailing
39411 character (neither newline nor @samp{Ctrl-D}) is appended to the input.
39415 If the user has typed more characters than fit in the buffer given to
39416 the @code{read} call, the trailing characters are buffered in @value{GDBN} until
39417 either another @code{read(0, @dots{})} is requested by the target, or debugging
39418 is stopped at the user's request.
39421 @node List of Supported Calls
39422 @subsection List of Supported Calls
39423 @cindex list of supported file-i/o calls
39440 @unnumberedsubsubsec open
39441 @cindex open, file-i/o system call
39446 int open(const char *pathname, int flags);
39447 int open(const char *pathname, int flags, mode_t mode);
39451 @samp{Fopen,@var{pathptr}/@var{len},@var{flags},@var{mode}}
39454 @var{flags} is the bitwise @code{OR} of the following values:
39458 If the file does not exist it will be created. The host
39459 rules apply as far as file ownership and time stamps
39463 When used with @code{O_CREAT}, if the file already exists it is
39464 an error and open() fails.
39467 If the file already exists and the open mode allows
39468 writing (@code{O_RDWR} or @code{O_WRONLY} is given) it will be
39469 truncated to zero length.
39472 The file is opened in append mode.
39475 The file is opened for reading only.
39478 The file is opened for writing only.
39481 The file is opened for reading and writing.
39485 Other bits are silently ignored.
39489 @var{mode} is the bitwise @code{OR} of the following values:
39493 User has read permission.
39496 User has write permission.
39499 Group has read permission.
39502 Group has write permission.
39505 Others have read permission.
39508 Others have write permission.
39512 Other bits are silently ignored.
39515 @item Return value:
39516 @code{open} returns the new file descriptor or -1 if an error
39523 @var{pathname} already exists and @code{O_CREAT} and @code{O_EXCL} were used.
39526 @var{pathname} refers to a directory.
39529 The requested access is not allowed.
39532 @var{pathname} was too long.
39535 A directory component in @var{pathname} does not exist.
39538 @var{pathname} refers to a device, pipe, named pipe or socket.
39541 @var{pathname} refers to a file on a read-only filesystem and
39542 write access was requested.
39545 @var{pathname} is an invalid pointer value.
39548 No space on device to create the file.
39551 The process already has the maximum number of files open.
39554 The limit on the total number of files open on the system
39558 The call was interrupted by the user.
39564 @unnumberedsubsubsec close
39565 @cindex close, file-i/o system call
39574 @samp{Fclose,@var{fd}}
39576 @item Return value:
39577 @code{close} returns zero on success, or -1 if an error occurred.
39583 @var{fd} isn't a valid open file descriptor.
39586 The call was interrupted by the user.
39592 @unnumberedsubsubsec read
39593 @cindex read, file-i/o system call
39598 int read(int fd, void *buf, unsigned int count);
39602 @samp{Fread,@var{fd},@var{bufptr},@var{count}}
39604 @item Return value:
39605 On success, the number of bytes read is returned.
39606 Zero indicates end of file. If count is zero, read
39607 returns zero as well. On error, -1 is returned.
39613 @var{fd} is not a valid file descriptor or is not open for
39617 @var{bufptr} is an invalid pointer value.
39620 The call was interrupted by the user.
39626 @unnumberedsubsubsec write
39627 @cindex write, file-i/o system call
39632 int write(int fd, const void *buf, unsigned int count);
39636 @samp{Fwrite,@var{fd},@var{bufptr},@var{count}}
39638 @item Return value:
39639 On success, the number of bytes written are returned.
39640 Zero indicates nothing was written. On error, -1
39647 @var{fd} is not a valid file descriptor or is not open for
39651 @var{bufptr} is an invalid pointer value.
39654 An attempt was made to write a file that exceeds the
39655 host-specific maximum file size allowed.
39658 No space on device to write the data.
39661 The call was interrupted by the user.
39667 @unnumberedsubsubsec lseek
39668 @cindex lseek, file-i/o system call
39673 long lseek (int fd, long offset, int flag);
39677 @samp{Flseek,@var{fd},@var{offset},@var{flag}}
39679 @var{flag} is one of:
39683 The offset is set to @var{offset} bytes.
39686 The offset is set to its current location plus @var{offset}
39690 The offset is set to the size of the file plus @var{offset}
39694 @item Return value:
39695 On success, the resulting unsigned offset in bytes from
39696 the beginning of the file is returned. Otherwise, a
39697 value of -1 is returned.
39703 @var{fd} is not a valid open file descriptor.
39706 @var{fd} is associated with the @value{GDBN} console.
39709 @var{flag} is not a proper value.
39712 The call was interrupted by the user.
39718 @unnumberedsubsubsec rename
39719 @cindex rename, file-i/o system call
39724 int rename(const char *oldpath, const char *newpath);
39728 @samp{Frename,@var{oldpathptr}/@var{len},@var{newpathptr}/@var{len}}
39730 @item Return value:
39731 On success, zero is returned. On error, -1 is returned.
39737 @var{newpath} is an existing directory, but @var{oldpath} is not a
39741 @var{newpath} is a non-empty directory.
39744 @var{oldpath} or @var{newpath} is a directory that is in use by some
39748 An attempt was made to make a directory a subdirectory
39752 A component used as a directory in @var{oldpath} or new
39753 path is not a directory. Or @var{oldpath} is a directory
39754 and @var{newpath} exists but is not a directory.
39757 @var{oldpathptr} or @var{newpathptr} are invalid pointer values.
39760 No access to the file or the path of the file.
39764 @var{oldpath} or @var{newpath} was too long.
39767 A directory component in @var{oldpath} or @var{newpath} does not exist.
39770 The file is on a read-only filesystem.
39773 The device containing the file has no room for the new
39777 The call was interrupted by the user.
39783 @unnumberedsubsubsec unlink
39784 @cindex unlink, file-i/o system call
39789 int unlink(const char *pathname);
39793 @samp{Funlink,@var{pathnameptr}/@var{len}}
39795 @item Return value:
39796 On success, zero is returned. On error, -1 is returned.
39802 No access to the file or the path of the file.
39805 The system does not allow unlinking of directories.
39808 The file @var{pathname} cannot be unlinked because it's
39809 being used by another process.
39812 @var{pathnameptr} is an invalid pointer value.
39815 @var{pathname} was too long.
39818 A directory component in @var{pathname} does not exist.
39821 A component of the path is not a directory.
39824 The file is on a read-only filesystem.
39827 The call was interrupted by the user.
39833 @unnumberedsubsubsec stat/fstat
39834 @cindex fstat, file-i/o system call
39835 @cindex stat, file-i/o system call
39840 int stat(const char *pathname, struct stat *buf);
39841 int fstat(int fd, struct stat *buf);
39845 @samp{Fstat,@var{pathnameptr}/@var{len},@var{bufptr}}@*
39846 @samp{Ffstat,@var{fd},@var{bufptr}}
39848 @item Return value:
39849 On success, zero is returned. On error, -1 is returned.
39855 @var{fd} is not a valid open file.
39858 A directory component in @var{pathname} does not exist or the
39859 path is an empty string.
39862 A component of the path is not a directory.
39865 @var{pathnameptr} is an invalid pointer value.
39868 No access to the file or the path of the file.
39871 @var{pathname} was too long.
39874 The call was interrupted by the user.
39880 @unnumberedsubsubsec gettimeofday
39881 @cindex gettimeofday, file-i/o system call
39886 int gettimeofday(struct timeval *tv, void *tz);
39890 @samp{Fgettimeofday,@var{tvptr},@var{tzptr}}
39892 @item Return value:
39893 On success, 0 is returned, -1 otherwise.
39899 @var{tz} is a non-NULL pointer.
39902 @var{tvptr} and/or @var{tzptr} is an invalid pointer value.
39908 @unnumberedsubsubsec isatty
39909 @cindex isatty, file-i/o system call
39914 int isatty(int fd);
39918 @samp{Fisatty,@var{fd}}
39920 @item Return value:
39921 Returns 1 if @var{fd} refers to the @value{GDBN} console, 0 otherwise.
39927 The call was interrupted by the user.
39932 Note that the @code{isatty} call is treated as a special case: it returns
39933 1 to the target if the file descriptor is attached
39934 to the @value{GDBN} console, 0 otherwise. Implementing through system calls
39935 would require implementing @code{ioctl} and would be more complex than
39940 @unnumberedsubsubsec system
39941 @cindex system, file-i/o system call
39946 int system(const char *command);
39950 @samp{Fsystem,@var{commandptr}/@var{len}}
39952 @item Return value:
39953 If @var{len} is zero, the return value indicates whether a shell is
39954 available. A zero return value indicates a shell is not available.
39955 For non-zero @var{len}, the value returned is -1 on error and the
39956 return status of the command otherwise. Only the exit status of the
39957 command is returned, which is extracted from the host's @code{system}
39958 return value by calling @code{WEXITSTATUS(retval)}. In case
39959 @file{/bin/sh} could not be executed, 127 is returned.
39965 The call was interrupted by the user.
39970 @value{GDBN} takes over the full task of calling the necessary host calls
39971 to perform the @code{system} call. The return value of @code{system} on
39972 the host is simplified before it's returned
39973 to the target. Any termination signal information from the child process
39974 is discarded, and the return value consists
39975 entirely of the exit status of the called command.
39977 Due to security concerns, the @code{system} call is by default refused
39978 by @value{GDBN}. The user has to allow this call explicitly with the
39979 @code{set remote system-call-allowed 1} command.
39982 @item set remote system-call-allowed
39983 @kindex set remote system-call-allowed
39984 Control whether to allow the @code{system} calls in the File I/O
39985 protocol for the remote target. The default is zero (disabled).
39987 @item show remote system-call-allowed
39988 @kindex show remote system-call-allowed
39989 Show whether the @code{system} calls are allowed in the File I/O
39993 @node Protocol-specific Representation of Datatypes
39994 @subsection Protocol-specific Representation of Datatypes
39995 @cindex protocol-specific representation of datatypes, in file-i/o protocol
39998 * Integral Datatypes::
40000 * Memory Transfer::
40005 @node Integral Datatypes
40006 @unnumberedsubsubsec Integral Datatypes
40007 @cindex integral datatypes, in file-i/o protocol
40009 The integral datatypes used in the system calls are @code{int},
40010 @code{unsigned int}, @code{long}, @code{unsigned long},
40011 @code{mode_t}, and @code{time_t}.
40013 @code{int}, @code{unsigned int}, @code{mode_t} and @code{time_t} are
40014 implemented as 32 bit values in this protocol.
40016 @code{long} and @code{unsigned long} are implemented as 64 bit types.
40018 @xref{Limits}, for corresponding MIN and MAX values (similar to those
40019 in @file{limits.h}) to allow range checking on host and target.
40021 @code{time_t} datatypes are defined as seconds since the Epoch.
40023 All integral datatypes transferred as part of a memory read or write of a
40024 structured datatype e.g.@: a @code{struct stat} have to be given in big endian
40027 @node Pointer Values
40028 @unnumberedsubsubsec Pointer Values
40029 @cindex pointer values, in file-i/o protocol
40031 Pointers to target data are transmitted as they are. An exception
40032 is made for pointers to buffers for which the length isn't
40033 transmitted as part of the function call, namely strings. Strings
40034 are transmitted as a pointer/length pair, both as hex values, e.g.@:
40041 which is a pointer to data of length 18 bytes at position 0x1aaf.
40042 The length is defined as the full string length in bytes, including
40043 the trailing null byte. For example, the string @code{"hello world"}
40044 at address 0x123456 is transmitted as
40050 @node Memory Transfer
40051 @unnumberedsubsubsec Memory Transfer
40052 @cindex memory transfer, in file-i/o protocol
40054 Structured data which is transferred using a memory read or write (for
40055 example, a @code{struct stat}) is expected to be in a protocol-specific format
40056 with all scalar multibyte datatypes being big endian. Translation to
40057 this representation needs to be done both by the target before the @code{F}
40058 packet is sent, and by @value{GDBN} before
40059 it transfers memory to the target. Transferred pointers to structured
40060 data should point to the already-coerced data at any time.
40064 @unnumberedsubsubsec struct stat
40065 @cindex struct stat, in file-i/o protocol
40067 The buffer of type @code{struct stat} used by the target and @value{GDBN}
40068 is defined as follows:
40072 unsigned int st_dev; /* device */
40073 unsigned int st_ino; /* inode */
40074 mode_t st_mode; /* protection */
40075 unsigned int st_nlink; /* number of hard links */
40076 unsigned int st_uid; /* user ID of owner */
40077 unsigned int st_gid; /* group ID of owner */
40078 unsigned int st_rdev; /* device type (if inode device) */
40079 unsigned long st_size; /* total size, in bytes */
40080 unsigned long st_blksize; /* blocksize for filesystem I/O */
40081 unsigned long st_blocks; /* number of blocks allocated */
40082 time_t st_atime; /* time of last access */
40083 time_t st_mtime; /* time of last modification */
40084 time_t st_ctime; /* time of last change */
40088 The integral datatypes conform to the definitions given in the
40089 appropriate section (see @ref{Integral Datatypes}, for details) so this
40090 structure is of size 64 bytes.
40092 The values of several fields have a restricted meaning and/or
40098 A value of 0 represents a file, 1 the console.
40101 No valid meaning for the target. Transmitted unchanged.
40104 Valid mode bits are described in @ref{Constants}. Any other
40105 bits have currently no meaning for the target.
40110 No valid meaning for the target. Transmitted unchanged.
40115 These values have a host and file system dependent
40116 accuracy. Especially on Windows hosts, the file system may not
40117 support exact timing values.
40120 The target gets a @code{struct stat} of the above representation and is
40121 responsible for coercing it to the target representation before
40124 Note that due to size differences between the host, target, and protocol
40125 representations of @code{struct stat} members, these members could eventually
40126 get truncated on the target.
40128 @node struct timeval
40129 @unnumberedsubsubsec struct timeval
40130 @cindex struct timeval, in file-i/o protocol
40132 The buffer of type @code{struct timeval} used by the File-I/O protocol
40133 is defined as follows:
40137 time_t tv_sec; /* second */
40138 long tv_usec; /* microsecond */
40142 The integral datatypes conform to the definitions given in the
40143 appropriate section (see @ref{Integral Datatypes}, for details) so this
40144 structure is of size 8 bytes.
40147 @subsection Constants
40148 @cindex constants, in file-i/o protocol
40150 The following values are used for the constants inside of the
40151 protocol. @value{GDBN} and target are responsible for translating these
40152 values before and after the call as needed.
40163 @unnumberedsubsubsec Open Flags
40164 @cindex open flags, in file-i/o protocol
40166 All values are given in hexadecimal representation.
40178 @node mode_t Values
40179 @unnumberedsubsubsec mode_t Values
40180 @cindex mode_t values, in file-i/o protocol
40182 All values are given in octal representation.
40199 @unnumberedsubsubsec Errno Values
40200 @cindex errno values, in file-i/o protocol
40202 All values are given in decimal representation.
40227 @code{EUNKNOWN} is used as a fallback error value if a host system returns
40228 any error value not in the list of supported error numbers.
40231 @unnumberedsubsubsec Lseek Flags
40232 @cindex lseek flags, in file-i/o protocol
40241 @unnumberedsubsubsec Limits
40242 @cindex limits, in file-i/o protocol
40244 All values are given in decimal representation.
40247 INT_MIN -2147483648
40249 UINT_MAX 4294967295
40250 LONG_MIN -9223372036854775808
40251 LONG_MAX 9223372036854775807
40252 ULONG_MAX 18446744073709551615
40255 @node File-I/O Examples
40256 @subsection File-I/O Examples
40257 @cindex file-i/o examples
40259 Example sequence of a write call, file descriptor 3, buffer is at target
40260 address 0x1234, 6 bytes should be written:
40263 <- @code{Fwrite,3,1234,6}
40264 @emph{request memory read from target}
40267 @emph{return "6 bytes written"}
40271 Example sequence of a read call, file descriptor 3, buffer is at target
40272 address 0x1234, 6 bytes should be read:
40275 <- @code{Fread,3,1234,6}
40276 @emph{request memory write to target}
40277 -> @code{X1234,6:XXXXXX}
40278 @emph{return "6 bytes read"}
40282 Example sequence of a read call, call fails on the host due to invalid
40283 file descriptor (@code{EBADF}):
40286 <- @code{Fread,3,1234,6}
40290 Example sequence of a read call, user presses @kbd{Ctrl-c} before syscall on
40294 <- @code{Fread,3,1234,6}
40299 Example sequence of a read call, user presses @kbd{Ctrl-c} after syscall on
40303 <- @code{Fread,3,1234,6}
40304 -> @code{X1234,6:XXXXXX}
40308 @node Library List Format
40309 @section Library List Format
40310 @cindex library list format, remote protocol
40312 On some platforms, a dynamic loader (e.g.@: @file{ld.so}) runs in the
40313 same process as your application to manage libraries. In this case,
40314 @value{GDBN} can use the loader's symbol table and normal memory
40315 operations to maintain a list of shared libraries. On other
40316 platforms, the operating system manages loaded libraries.
40317 @value{GDBN} can not retrieve the list of currently loaded libraries
40318 through memory operations, so it uses the @samp{qXfer:libraries:read}
40319 packet (@pxref{qXfer library list read}) instead. The remote stub
40320 queries the target's operating system and reports which libraries
40323 The @samp{qXfer:libraries:read} packet returns an XML document which
40324 lists loaded libraries and their offsets. Each library has an
40325 associated name and one or more segment or section base addresses,
40326 which report where the library was loaded in memory.
40328 For the common case of libraries that are fully linked binaries, the
40329 library should have a list of segments. If the target supports
40330 dynamic linking of a relocatable object file, its library XML element
40331 should instead include a list of allocated sections. The segment or
40332 section bases are start addresses, not relocation offsets; they do not
40333 depend on the library's link-time base addresses.
40335 @value{GDBN} must be linked with the Expat library to support XML
40336 library lists. @xref{Expat}.
40338 A simple memory map, with one loaded library relocated by a single
40339 offset, looks like this:
40343 <library name="/lib/libc.so.6">
40344 <segment address="0x10000000"/>
40349 Another simple memory map, with one loaded library with three
40350 allocated sections (.text, .data, .bss), looks like this:
40354 <library name="sharedlib.o">
40355 <section address="0x10000000"/>
40356 <section address="0x20000000"/>
40357 <section address="0x30000000"/>
40362 The format of a library list is described by this DTD:
40365 <!-- library-list: Root element with versioning -->
40366 <!ELEMENT library-list (library)*>
40367 <!ATTLIST library-list version CDATA #FIXED "1.0">
40368 <!ELEMENT library (segment*, section*)>
40369 <!ATTLIST library name CDATA #REQUIRED>
40370 <!ELEMENT segment EMPTY>
40371 <!ATTLIST segment address CDATA #REQUIRED>
40372 <!ELEMENT section EMPTY>
40373 <!ATTLIST section address CDATA #REQUIRED>
40376 In addition, segments and section descriptors cannot be mixed within a
40377 single library element, and you must supply at least one segment or
40378 section for each library.
40380 @node Library List Format for SVR4 Targets
40381 @section Library List Format for SVR4 Targets
40382 @cindex library list format, remote protocol
40384 On SVR4 platforms @value{GDBN} can use the symbol table of a dynamic loader
40385 (e.g.@: @file{ld.so}) and normal memory operations to maintain a list of
40386 shared libraries. Still a special library list provided by this packet is
40387 more efficient for the @value{GDBN} remote protocol.
40389 The @samp{qXfer:libraries-svr4:read} packet returns an XML document which lists
40390 loaded libraries and their SVR4 linker parameters. For each library on SVR4
40391 target, the following parameters are reported:
40395 @code{name}, the absolute file name from the @code{l_name} field of
40396 @code{struct link_map}.
40398 @code{lm} with address of @code{struct link_map} used for TLS
40399 (Thread Local Storage) access.
40401 @code{l_addr}, the displacement as read from the field @code{l_addr} of
40402 @code{struct link_map}. For prelinked libraries this is not an absolute
40403 memory address. It is a displacement of absolute memory address against
40404 address the file was prelinked to during the library load.
40406 @code{l_ld}, which is memory address of the @code{PT_DYNAMIC} segment
40409 Additionally the single @code{main-lm} attribute specifies address of
40410 @code{struct link_map} used for the main executable. This parameter is used
40411 for TLS access and its presence is optional.
40413 @value{GDBN} must be linked with the Expat library to support XML
40414 SVR4 library lists. @xref{Expat}.
40416 A simple memory map, with two loaded libraries (which do not use prelink),
40420 <library-list-svr4 version="1.0" main-lm="0xe4f8f8">
40421 <library name="/lib/ld-linux.so.2" lm="0xe4f51c" l_addr="0xe2d000"
40423 <library name="/lib/libc.so.6" lm="0xe4fbe8" l_addr="0x154000"
40425 </library-list-svr>
40428 The format of an SVR4 library list is described by this DTD:
40431 <!-- library-list-svr4: Root element with versioning -->
40432 <!ELEMENT library-list-svr4 (library)*>
40433 <!ATTLIST library-list-svr4 version CDATA #FIXED "1.0">
40434 <!ATTLIST library-list-svr4 main-lm CDATA #IMPLIED>
40435 <!ELEMENT library EMPTY>
40436 <!ATTLIST library name CDATA #REQUIRED>
40437 <!ATTLIST library lm CDATA #REQUIRED>
40438 <!ATTLIST library l_addr CDATA #REQUIRED>
40439 <!ATTLIST library l_ld CDATA #REQUIRED>
40442 @node Memory Map Format
40443 @section Memory Map Format
40444 @cindex memory map format
40446 To be able to write into flash memory, @value{GDBN} needs to obtain a
40447 memory map from the target. This section describes the format of the
40450 The memory map is obtained using the @samp{qXfer:memory-map:read}
40451 (@pxref{qXfer memory map read}) packet and is an XML document that
40452 lists memory regions.
40454 @value{GDBN} must be linked with the Expat library to support XML
40455 memory maps. @xref{Expat}.
40457 The top-level structure of the document is shown below:
40460 <?xml version="1.0"?>
40461 <!DOCTYPE memory-map
40462 PUBLIC "+//IDN gnu.org//DTD GDB Memory Map V1.0//EN"
40463 "http://sourceware.org/gdb/gdb-memory-map.dtd">
40469 Each region can be either:
40474 A region of RAM starting at @var{addr} and extending for @var{length}
40478 <memory type="ram" start="@var{addr}" length="@var{length}"/>
40483 A region of read-only memory:
40486 <memory type="rom" start="@var{addr}" length="@var{length}"/>
40491 A region of flash memory, with erasure blocks @var{blocksize}
40495 <memory type="flash" start="@var{addr}" length="@var{length}">
40496 <property name="blocksize">@var{blocksize}</property>
40502 Regions must not overlap. @value{GDBN} assumes that areas of memory not covered
40503 by the memory map are RAM, and uses the ordinary @samp{M} and @samp{X}
40504 packets to write to addresses in such ranges.
40506 The formal DTD for memory map format is given below:
40509 <!-- ................................................... -->
40510 <!-- Memory Map XML DTD ................................ -->
40511 <!-- File: memory-map.dtd .............................. -->
40512 <!-- .................................... .............. -->
40513 <!-- memory-map.dtd -->
40514 <!-- memory-map: Root element with versioning -->
40515 <!ELEMENT memory-map (memory | property)>
40516 <!ATTLIST memory-map version CDATA #FIXED "1.0.0">
40517 <!ELEMENT memory (property)>
40518 <!-- memory: Specifies a memory region,
40519 and its type, or device. -->
40520 <!ATTLIST memory type CDATA #REQUIRED
40521 start CDATA #REQUIRED
40522 length CDATA #REQUIRED
40523 device CDATA #IMPLIED>
40524 <!-- property: Generic attribute tag -->
40525 <!ELEMENT property (#PCDATA | property)*>
40526 <!ATTLIST property name CDATA #REQUIRED>
40529 @node Thread List Format
40530 @section Thread List Format
40531 @cindex thread list format
40533 To efficiently update the list of threads and their attributes,
40534 @value{GDBN} issues the @samp{qXfer:threads:read} packet
40535 (@pxref{qXfer threads read}) and obtains the XML document with
40536 the following structure:
40539 <?xml version="1.0"?>
40541 <thread id="id" core="0">
40542 ... description ...
40547 Each @samp{thread} element must have the @samp{id} attribute that
40548 identifies the thread (@pxref{thread-id syntax}). The
40549 @samp{core} attribute, if present, specifies which processor core
40550 the thread was last executing on. The content of the of @samp{thread}
40551 element is interpreted as human-readable auxilliary information.
40553 @node Traceframe Info Format
40554 @section Traceframe Info Format
40555 @cindex traceframe info format
40557 To be able to know which objects in the inferior can be examined when
40558 inspecting a tracepoint hit, @value{GDBN} needs to obtain the list of
40559 memory ranges, registers and trace state variables that have been
40560 collected in a traceframe.
40562 This list is obtained using the @samp{qXfer:traceframe-info:read}
40563 (@pxref{qXfer traceframe info read}) packet and is an XML document.
40565 @value{GDBN} must be linked with the Expat library to support XML
40566 traceframe info discovery. @xref{Expat}.
40568 The top-level structure of the document is shown below:
40571 <?xml version="1.0"?>
40572 <!DOCTYPE traceframe-info
40573 PUBLIC "+//IDN gnu.org//DTD GDB Memory Map V1.0//EN"
40574 "http://sourceware.org/gdb/gdb-traceframe-info.dtd">
40580 Each traceframe block can be either:
40585 A region of collected memory starting at @var{addr} and extending for
40586 @var{length} bytes from there:
40589 <memory start="@var{addr}" length="@var{length}"/>
40594 The formal DTD for the traceframe info format is given below:
40597 <!ELEMENT traceframe-info (memory)* >
40598 <!ATTLIST traceframe-info version CDATA #FIXED "1.0">
40600 <!ELEMENT memory EMPTY>
40601 <!ATTLIST memory start CDATA #REQUIRED
40602 length CDATA #REQUIRED>
40605 @node Branch Trace Format
40606 @section Branch Trace Format
40607 @cindex branch trace format
40609 In order to display the branch trace of an inferior thread,
40610 @value{GDBN} needs to obtain the list of branches. This list is
40611 represented as list of sequential code blocks that are connected via
40612 branches. The code in each block has been executed sequentially.
40614 This list is obtained using the @samp{qXfer:btrace:read}
40615 (@pxref{qXfer btrace read}) packet and is an XML document.
40617 @value{GDBN} must be linked with the Expat library to support XML
40618 traceframe info discovery. @xref{Expat}.
40620 The top-level structure of the document is shown below:
40623 <?xml version="1.0"?>
40625 PUBLIC "+//IDN gnu.org//DTD GDB Branch Trace V1.0//EN"
40626 "http://sourceware.org/gdb/gdb-btrace.dtd">
40635 A block of sequentially executed instructions starting at @var{begin}
40636 and ending at @var{end}:
40639 <block begin="@var{begin}" end="@var{end}"/>
40644 The formal DTD for the branch trace format is given below:
40647 <!ELEMENT btrace (block)* >
40648 <!ATTLIST btrace version CDATA #FIXED "1.0">
40650 <!ELEMENT block EMPTY>
40651 <!ATTLIST block begin CDATA #REQUIRED
40652 end CDATA #REQUIRED>
40655 @include agentexpr.texi
40657 @node Target Descriptions
40658 @appendix Target Descriptions
40659 @cindex target descriptions
40661 One of the challenges of using @value{GDBN} to debug embedded systems
40662 is that there are so many minor variants of each processor
40663 architecture in use. It is common practice for vendors to start with
40664 a standard processor core --- ARM, PowerPC, or @acronym{MIPS}, for example ---
40665 and then make changes to adapt it to a particular market niche. Some
40666 architectures have hundreds of variants, available from dozens of
40667 vendors. This leads to a number of problems:
40671 With so many different customized processors, it is difficult for
40672 the @value{GDBN} maintainers to keep up with the changes.
40674 Since individual variants may have short lifetimes or limited
40675 audiences, it may not be worthwhile to carry information about every
40676 variant in the @value{GDBN} source tree.
40678 When @value{GDBN} does support the architecture of the embedded system
40679 at hand, the task of finding the correct architecture name to give the
40680 @command{set architecture} command can be error-prone.
40683 To address these problems, the @value{GDBN} remote protocol allows a
40684 target system to not only identify itself to @value{GDBN}, but to
40685 actually describe its own features. This lets @value{GDBN} support
40686 processor variants it has never seen before --- to the extent that the
40687 descriptions are accurate, and that @value{GDBN} understands them.
40689 @value{GDBN} must be linked with the Expat library to support XML
40690 target descriptions. @xref{Expat}.
40693 * Retrieving Descriptions:: How descriptions are fetched from a target.
40694 * Target Description Format:: The contents of a target description.
40695 * Predefined Target Types:: Standard types available for target
40697 * Standard Target Features:: Features @value{GDBN} knows about.
40700 @node Retrieving Descriptions
40701 @section Retrieving Descriptions
40703 Target descriptions can be read from the target automatically, or
40704 specified by the user manually. The default behavior is to read the
40705 description from the target. @value{GDBN} retrieves it via the remote
40706 protocol using @samp{qXfer} requests (@pxref{General Query Packets,
40707 qXfer}). The @var{annex} in the @samp{qXfer} packet will be
40708 @samp{target.xml}. The contents of the @samp{target.xml} annex are an
40709 XML document, of the form described in @ref{Target Description
40712 Alternatively, you can specify a file to read for the target description.
40713 If a file is set, the target will not be queried. The commands to
40714 specify a file are:
40717 @cindex set tdesc filename
40718 @item set tdesc filename @var{path}
40719 Read the target description from @var{path}.
40721 @cindex unset tdesc filename
40722 @item unset tdesc filename
40723 Do not read the XML target description from a file. @value{GDBN}
40724 will use the description supplied by the current target.
40726 @cindex show tdesc filename
40727 @item show tdesc filename
40728 Show the filename to read for a target description, if any.
40732 @node Target Description Format
40733 @section Target Description Format
40734 @cindex target descriptions, XML format
40736 A target description annex is an @uref{http://www.w3.org/XML/, XML}
40737 document which complies with the Document Type Definition provided in
40738 the @value{GDBN} sources in @file{gdb/features/gdb-target.dtd}. This
40739 means you can use generally available tools like @command{xmllint} to
40740 check that your feature descriptions are well-formed and valid.
40741 However, to help people unfamiliar with XML write descriptions for
40742 their targets, we also describe the grammar here.
40744 Target descriptions can identify the architecture of the remote target
40745 and (for some architectures) provide information about custom register
40746 sets. They can also identify the OS ABI of the remote target.
40747 @value{GDBN} can use this information to autoconfigure for your
40748 target, or to warn you if you connect to an unsupported target.
40750 Here is a simple target description:
40753 <target version="1.0">
40754 <architecture>i386:x86-64</architecture>
40759 This minimal description only says that the target uses
40760 the x86-64 architecture.
40762 A target description has the following overall form, with [ ] marking
40763 optional elements and @dots{} marking repeatable elements. The elements
40764 are explained further below.
40767 <?xml version="1.0"?>
40768 <!DOCTYPE target SYSTEM "gdb-target.dtd">
40769 <target version="1.0">
40770 @r{[}@var{architecture}@r{]}
40771 @r{[}@var{osabi}@r{]}
40772 @r{[}@var{compatible}@r{]}
40773 @r{[}@var{feature}@dots{}@r{]}
40778 The description is generally insensitive to whitespace and line
40779 breaks, under the usual common-sense rules. The XML version
40780 declaration and document type declaration can generally be omitted
40781 (@value{GDBN} does not require them), but specifying them may be
40782 useful for XML validation tools. The @samp{version} attribute for
40783 @samp{<target>} may also be omitted, but we recommend
40784 including it; if future versions of @value{GDBN} use an incompatible
40785 revision of @file{gdb-target.dtd}, they will detect and report
40786 the version mismatch.
40788 @subsection Inclusion
40789 @cindex target descriptions, inclusion
40792 @cindex <xi:include>
40795 It can sometimes be valuable to split a target description up into
40796 several different annexes, either for organizational purposes, or to
40797 share files between different possible target descriptions. You can
40798 divide a description into multiple files by replacing any element of
40799 the target description with an inclusion directive of the form:
40802 <xi:include href="@var{document}"/>
40806 When @value{GDBN} encounters an element of this form, it will retrieve
40807 the named XML @var{document}, and replace the inclusion directive with
40808 the contents of that document. If the current description was read
40809 using @samp{qXfer}, then so will be the included document;
40810 @var{document} will be interpreted as the name of an annex. If the
40811 current description was read from a file, @value{GDBN} will look for
40812 @var{document} as a file in the same directory where it found the
40813 original description.
40815 @subsection Architecture
40816 @cindex <architecture>
40818 An @samp{<architecture>} element has this form:
40821 <architecture>@var{arch}</architecture>
40824 @var{arch} is one of the architectures from the set accepted by
40825 @code{set architecture} (@pxref{Targets, ,Specifying a Debugging Target}).
40828 @cindex @code{<osabi>}
40830 This optional field was introduced in @value{GDBN} version 7.0.
40831 Previous versions of @value{GDBN} ignore it.
40833 An @samp{<osabi>} element has this form:
40836 <osabi>@var{abi-name}</osabi>
40839 @var{abi-name} is an OS ABI name from the same selection accepted by
40840 @w{@code{set osabi}} (@pxref{ABI, ,Configuring the Current ABI}).
40842 @subsection Compatible Architecture
40843 @cindex @code{<compatible>}
40845 This optional field was introduced in @value{GDBN} version 7.0.
40846 Previous versions of @value{GDBN} ignore it.
40848 A @samp{<compatible>} element has this form:
40851 <compatible>@var{arch}</compatible>
40854 @var{arch} is one of the architectures from the set accepted by
40855 @code{set architecture} (@pxref{Targets, ,Specifying a Debugging Target}).
40857 A @samp{<compatible>} element is used to specify that the target
40858 is able to run binaries in some other than the main target architecture
40859 given by the @samp{<architecture>} element. For example, on the
40860 Cell Broadband Engine, the main architecture is @code{powerpc:common}
40861 or @code{powerpc:common64}, but the system is able to run binaries
40862 in the @code{spu} architecture as well. The way to describe this
40863 capability with @samp{<compatible>} is as follows:
40866 <architecture>powerpc:common</architecture>
40867 <compatible>spu</compatible>
40870 @subsection Features
40873 Each @samp{<feature>} describes some logical portion of the target
40874 system. Features are currently used to describe available CPU
40875 registers and the types of their contents. A @samp{<feature>} element
40879 <feature name="@var{name}">
40880 @r{[}@var{type}@dots{}@r{]}
40886 Each feature's name should be unique within the description. The name
40887 of a feature does not matter unless @value{GDBN} has some special
40888 knowledge of the contents of that feature; if it does, the feature
40889 should have its standard name. @xref{Standard Target Features}.
40893 Any register's value is a collection of bits which @value{GDBN} must
40894 interpret. The default interpretation is a two's complement integer,
40895 but other types can be requested by name in the register description.
40896 Some predefined types are provided by @value{GDBN} (@pxref{Predefined
40897 Target Types}), and the description can define additional composite types.
40899 Each type element must have an @samp{id} attribute, which gives
40900 a unique (within the containing @samp{<feature>}) name to the type.
40901 Types must be defined before they are used.
40904 Some targets offer vector registers, which can be treated as arrays
40905 of scalar elements. These types are written as @samp{<vector>} elements,
40906 specifying the array element type, @var{type}, and the number of elements,
40910 <vector id="@var{id}" type="@var{type}" count="@var{count}"/>
40914 If a register's value is usefully viewed in multiple ways, define it
40915 with a union type containing the useful representations. The
40916 @samp{<union>} element contains one or more @samp{<field>} elements,
40917 each of which has a @var{name} and a @var{type}:
40920 <union id="@var{id}">
40921 <field name="@var{name}" type="@var{type}"/>
40927 If a register's value is composed from several separate values, define
40928 it with a structure type. There are two forms of the @samp{<struct>}
40929 element; a @samp{<struct>} element must either contain only bitfields
40930 or contain no bitfields. If the structure contains only bitfields,
40931 its total size in bytes must be specified, each bitfield must have an
40932 explicit start and end, and bitfields are automatically assigned an
40933 integer type. The field's @var{start} should be less than or
40934 equal to its @var{end}, and zero represents the least significant bit.
40937 <struct id="@var{id}" size="@var{size}">
40938 <field name="@var{name}" start="@var{start}" end="@var{end}"/>
40943 If the structure contains no bitfields, then each field has an
40944 explicit type, and no implicit padding is added.
40947 <struct id="@var{id}">
40948 <field name="@var{name}" type="@var{type}"/>
40954 If a register's value is a series of single-bit flags, define it with
40955 a flags type. The @samp{<flags>} element has an explicit @var{size}
40956 and contains one or more @samp{<field>} elements. Each field has a
40957 @var{name}, a @var{start}, and an @var{end}. Only single-bit flags
40961 <flags id="@var{id}" size="@var{size}">
40962 <field name="@var{name}" start="@var{start}" end="@var{end}"/>
40967 @subsection Registers
40970 Each register is represented as an element with this form:
40973 <reg name="@var{name}"
40974 bitsize="@var{size}"
40975 @r{[}regnum="@var{num}"@r{]}
40976 @r{[}save-restore="@var{save-restore}"@r{]}
40977 @r{[}type="@var{type}"@r{]}
40978 @r{[}group="@var{group}"@r{]}/>
40982 The components are as follows:
40987 The register's name; it must be unique within the target description.
40990 The register's size, in bits.
40993 The register's number. If omitted, a register's number is one greater
40994 than that of the previous register (either in the current feature or in
40995 a preceding feature); the first register in the target description
40996 defaults to zero. This register number is used to read or write
40997 the register; e.g.@: it is used in the remote @code{p} and @code{P}
40998 packets, and registers appear in the @code{g} and @code{G} packets
40999 in order of increasing register number.
41002 Whether the register should be preserved across inferior function
41003 calls; this must be either @code{yes} or @code{no}. The default is
41004 @code{yes}, which is appropriate for most registers except for
41005 some system control registers; this is not related to the target's
41009 The type of the register. @var{type} may be a predefined type, a type
41010 defined in the current feature, or one of the special types @code{int}
41011 and @code{float}. @code{int} is an integer type of the correct size
41012 for @var{bitsize}, and @code{float} is a floating point type (in the
41013 architecture's normal floating point format) of the correct size for
41014 @var{bitsize}. The default is @code{int}.
41017 The register group to which this register belongs. @var{group} must
41018 be either @code{general}, @code{float}, or @code{vector}. If no
41019 @var{group} is specified, @value{GDBN} will not display the register
41020 in @code{info registers}.
41024 @node Predefined Target Types
41025 @section Predefined Target Types
41026 @cindex target descriptions, predefined types
41028 Type definitions in the self-description can build up composite types
41029 from basic building blocks, but can not define fundamental types. Instead,
41030 standard identifiers are provided by @value{GDBN} for the fundamental
41031 types. The currently supported types are:
41040 Signed integer types holding the specified number of bits.
41047 Unsigned integer types holding the specified number of bits.
41051 Pointers to unspecified code and data. The program counter and
41052 any dedicated return address register may be marked as code
41053 pointers; printing a code pointer converts it into a symbolic
41054 address. The stack pointer and any dedicated address registers
41055 may be marked as data pointers.
41058 Single precision IEEE floating point.
41061 Double precision IEEE floating point.
41064 The 12-byte extended precision format used by ARM FPA registers.
41067 The 10-byte extended precision format used by x87 registers.
41070 32bit @sc{eflags} register used by x86.
41073 32bit @sc{mxcsr} register used by x86.
41077 @node Standard Target Features
41078 @section Standard Target Features
41079 @cindex target descriptions, standard features
41081 A target description must contain either no registers or all the
41082 target's registers. If the description contains no registers, then
41083 @value{GDBN} will assume a default register layout, selected based on
41084 the architecture. If the description contains any registers, the
41085 default layout will not be used; the standard registers must be
41086 described in the target description, in such a way that @value{GDBN}
41087 can recognize them.
41089 This is accomplished by giving specific names to feature elements
41090 which contain standard registers. @value{GDBN} will look for features
41091 with those names and verify that they contain the expected registers;
41092 if any known feature is missing required registers, or if any required
41093 feature is missing, @value{GDBN} will reject the target
41094 description. You can add additional registers to any of the
41095 standard features --- @value{GDBN} will display them just as if
41096 they were added to an unrecognized feature.
41098 This section lists the known features and their expected contents.
41099 Sample XML documents for these features are included in the
41100 @value{GDBN} source tree, in the directory @file{gdb/features}.
41102 Names recognized by @value{GDBN} should include the name of the
41103 company or organization which selected the name, and the overall
41104 architecture to which the feature applies; so e.g.@: the feature
41105 containing ARM core registers is named @samp{org.gnu.gdb.arm.core}.
41107 The names of registers are not case sensitive for the purpose
41108 of recognizing standard features, but @value{GDBN} will only display
41109 registers using the capitalization used in the description.
41112 * AArch64 Features::
41117 * PowerPC Features::
41122 @node AArch64 Features
41123 @subsection AArch64 Features
41124 @cindex target descriptions, AArch64 features
41126 The @samp{org.gnu.gdb.aarch64.core} feature is required for AArch64
41127 targets. It should contain registers @samp{x0} through @samp{x30},
41128 @samp{sp}, @samp{pc}, and @samp{cpsr}.
41130 The @samp{org.gnu.gdb.aarch64.fpu} feature is optional. If present,
41131 it should contain registers @samp{v0} through @samp{v31}, @samp{fpsr},
41135 @subsection ARM Features
41136 @cindex target descriptions, ARM features
41138 The @samp{org.gnu.gdb.arm.core} feature is required for non-M-profile
41140 It should contain registers @samp{r0} through @samp{r13}, @samp{sp},
41141 @samp{lr}, @samp{pc}, and @samp{cpsr}.
41143 For M-profile targets (e.g. Cortex-M3), the @samp{org.gnu.gdb.arm.core}
41144 feature is replaced by @samp{org.gnu.gdb.arm.m-profile}. It should contain
41145 registers @samp{r0} through @samp{r13}, @samp{sp}, @samp{lr}, @samp{pc},
41148 The @samp{org.gnu.gdb.arm.fpa} feature is optional. If present, it
41149 should contain registers @samp{f0} through @samp{f7} and @samp{fps}.
41151 The @samp{org.gnu.gdb.xscale.iwmmxt} feature is optional. If present,
41152 it should contain at least registers @samp{wR0} through @samp{wR15} and
41153 @samp{wCGR0} through @samp{wCGR3}. The @samp{wCID}, @samp{wCon},
41154 @samp{wCSSF}, and @samp{wCASF} registers are optional.
41156 The @samp{org.gnu.gdb.arm.vfp} feature is optional. If present, it
41157 should contain at least registers @samp{d0} through @samp{d15}. If
41158 they are present, @samp{d16} through @samp{d31} should also be included.
41159 @value{GDBN} will synthesize the single-precision registers from
41160 halves of the double-precision registers.
41162 The @samp{org.gnu.gdb.arm.neon} feature is optional. It does not
41163 need to contain registers; it instructs @value{GDBN} to display the
41164 VFP double-precision registers as vectors and to synthesize the
41165 quad-precision registers from pairs of double-precision registers.
41166 If this feature is present, @samp{org.gnu.gdb.arm.vfp} must also
41167 be present and include 32 double-precision registers.
41169 @node i386 Features
41170 @subsection i386 Features
41171 @cindex target descriptions, i386 features
41173 The @samp{org.gnu.gdb.i386.core} feature is required for i386/amd64
41174 targets. It should describe the following registers:
41178 @samp{eax} through @samp{edi} plus @samp{eip} for i386
41180 @samp{rax} through @samp{r15} plus @samp{rip} for amd64
41182 @samp{eflags}, @samp{cs}, @samp{ss}, @samp{ds}, @samp{es},
41183 @samp{fs}, @samp{gs}
41185 @samp{st0} through @samp{st7}
41187 @samp{fctrl}, @samp{fstat}, @samp{ftag}, @samp{fiseg}, @samp{fioff},
41188 @samp{foseg}, @samp{fooff} and @samp{fop}
41191 The register sets may be different, depending on the target.
41193 The @samp{org.gnu.gdb.i386.sse} feature is optional. It should
41194 describe registers:
41198 @samp{xmm0} through @samp{xmm7} for i386
41200 @samp{xmm0} through @samp{xmm15} for amd64
41205 The @samp{org.gnu.gdb.i386.avx} feature is optional and requires the
41206 @samp{org.gnu.gdb.i386.sse} feature. It should
41207 describe the upper 128 bits of @sc{ymm} registers:
41211 @samp{ymm0h} through @samp{ymm7h} for i386
41213 @samp{ymm0h} through @samp{ymm15h} for amd64
41216 The @samp{org.gnu.gdb.i386.linux} feature is optional. It should
41217 describe a single register, @samp{orig_eax}.
41219 @node MIPS Features
41220 @subsection @acronym{MIPS} Features
41221 @cindex target descriptions, @acronym{MIPS} features
41223 The @samp{org.gnu.gdb.mips.cpu} feature is required for @acronym{MIPS} targets.
41224 It should contain registers @samp{r0} through @samp{r31}, @samp{lo},
41225 @samp{hi}, and @samp{pc}. They may be 32-bit or 64-bit depending
41228 The @samp{org.gnu.gdb.mips.cp0} feature is also required. It should
41229 contain at least the @samp{status}, @samp{badvaddr}, and @samp{cause}
41230 registers. They may be 32-bit or 64-bit depending on the target.
41232 The @samp{org.gnu.gdb.mips.fpu} feature is currently required, though
41233 it may be optional in a future version of @value{GDBN}. It should
41234 contain registers @samp{f0} through @samp{f31}, @samp{fcsr}, and
41235 @samp{fir}. They may be 32-bit or 64-bit depending on the target.
41237 The @samp{org.gnu.gdb.mips.dsp} feature is optional. It should
41238 contain registers @samp{hi1} through @samp{hi3}, @samp{lo1} through
41239 @samp{lo3}, and @samp{dspctl}. The @samp{dspctl} register should
41240 be 32-bit and the rest may be 32-bit or 64-bit depending on the target.
41242 The @samp{org.gnu.gdb.mips.linux} feature is optional. It should
41243 contain a single register, @samp{restart}, which is used by the
41244 Linux kernel to control restartable syscalls.
41246 @node M68K Features
41247 @subsection M68K Features
41248 @cindex target descriptions, M68K features
41251 @item @samp{org.gnu.gdb.m68k.core}
41252 @itemx @samp{org.gnu.gdb.coldfire.core}
41253 @itemx @samp{org.gnu.gdb.fido.core}
41254 One of those features must be always present.
41255 The feature that is present determines which flavor of m68k is
41256 used. The feature that is present should contain registers
41257 @samp{d0} through @samp{d7}, @samp{a0} through @samp{a5}, @samp{fp},
41258 @samp{sp}, @samp{ps} and @samp{pc}.
41260 @item @samp{org.gnu.gdb.coldfire.fp}
41261 This feature is optional. If present, it should contain registers
41262 @samp{fp0} through @samp{fp7}, @samp{fpcontrol}, @samp{fpstatus} and
41266 @node PowerPC Features
41267 @subsection PowerPC Features
41268 @cindex target descriptions, PowerPC features
41270 The @samp{org.gnu.gdb.power.core} feature is required for PowerPC
41271 targets. It should contain registers @samp{r0} through @samp{r31},
41272 @samp{pc}, @samp{msr}, @samp{cr}, @samp{lr}, @samp{ctr}, and
41273 @samp{xer}. They may be 32-bit or 64-bit depending on the target.
41275 The @samp{org.gnu.gdb.power.fpu} feature is optional. It should
41276 contain registers @samp{f0} through @samp{f31} and @samp{fpscr}.
41278 The @samp{org.gnu.gdb.power.altivec} feature is optional. It should
41279 contain registers @samp{vr0} through @samp{vr31}, @samp{vscr},
41282 The @samp{org.gnu.gdb.power.vsx} feature is optional. It should
41283 contain registers @samp{vs0h} through @samp{vs31h}. @value{GDBN}
41284 will combine these registers with the floating point registers
41285 (@samp{f0} through @samp{f31}) and the altivec registers (@samp{vr0}
41286 through @samp{vr31}) to present the 128-bit wide registers @samp{vs0}
41287 through @samp{vs63}, the set of vector registers for POWER7.
41289 The @samp{org.gnu.gdb.power.spe} feature is optional. It should
41290 contain registers @samp{ev0h} through @samp{ev31h}, @samp{acc}, and
41291 @samp{spefscr}. SPE targets should provide 32-bit registers in
41292 @samp{org.gnu.gdb.power.core} and provide the upper halves in
41293 @samp{ev0h} through @samp{ev31h}. @value{GDBN} will combine
41294 these to present registers @samp{ev0} through @samp{ev31} to the
41297 @node TIC6x Features
41298 @subsection TMS320C6x Features
41299 @cindex target descriptions, TIC6x features
41300 @cindex target descriptions, TMS320C6x features
41301 The @samp{org.gnu.gdb.tic6x.core} feature is required for TMS320C6x
41302 targets. It should contain registers @samp{A0} through @samp{A15},
41303 registers @samp{B0} through @samp{B15}, @samp{CSR} and @samp{PC}.
41305 The @samp{org.gnu.gdb.tic6x.gp} feature is optional. It should
41306 contain registers @samp{A16} through @samp{A31} and @samp{B16}
41307 through @samp{B31}.
41309 The @samp{org.gnu.gdb.tic6x.c6xp} feature is optional. It should
41310 contain registers @samp{TSR}, @samp{ILC} and @samp{RILC}.
41312 @node Operating System Information
41313 @appendix Operating System Information
41314 @cindex operating system information
41320 Users of @value{GDBN} often wish to obtain information about the state of
41321 the operating system running on the target---for example the list of
41322 processes, or the list of open files. This section describes the
41323 mechanism that makes it possible. This mechanism is similar to the
41324 target features mechanism (@pxref{Target Descriptions}), but focuses
41325 on a different aspect of target.
41327 Operating system information is retrived from the target via the
41328 remote protocol, using @samp{qXfer} requests (@pxref{qXfer osdata
41329 read}). The object name in the request should be @samp{osdata}, and
41330 the @var{annex} identifies the data to be fetched.
41333 @appendixsection Process list
41334 @cindex operating system information, process list
41336 When requesting the process list, the @var{annex} field in the
41337 @samp{qXfer} request should be @samp{processes}. The returned data is
41338 an XML document. The formal syntax of this document is defined in
41339 @file{gdb/features/osdata.dtd}.
41341 An example document is:
41344 <?xml version="1.0"?>
41345 <!DOCTYPE target SYSTEM "osdata.dtd">
41346 <osdata type="processes">
41348 <column name="pid">1</column>
41349 <column name="user">root</column>
41350 <column name="command">/sbin/init</column>
41351 <column name="cores">1,2,3</column>
41356 Each item should include a column whose name is @samp{pid}. The value
41357 of that column should identify the process on the target. The
41358 @samp{user} and @samp{command} columns are optional, and will be
41359 displayed by @value{GDBN}. The @samp{cores} column, if present,
41360 should contain a comma-separated list of cores that this process
41361 is running on. Target may provide additional columns,
41362 which @value{GDBN} currently ignores.
41364 @node Trace File Format
41365 @appendix Trace File Format
41366 @cindex trace file format
41368 The trace file comes in three parts: a header, a textual description
41369 section, and a trace frame section with binary data.
41371 The header has the form @code{\x7fTRACE0\n}. The first byte is
41372 @code{0x7f} so as to indicate that the file contains binary data,
41373 while the @code{0} is a version number that may have different values
41376 The description section consists of multiple lines of @sc{ascii} text
41377 separated by newline characters (@code{0xa}). The lines may include a
41378 variety of optional descriptive or context-setting information, such
41379 as tracepoint definitions or register set size. @value{GDBN} will
41380 ignore any line that it does not recognize. An empty line marks the end
41383 @c FIXME add some specific types of data
41385 The trace frame section consists of a number of consecutive frames.
41386 Each frame begins with a two-byte tracepoint number, followed by a
41387 four-byte size giving the amount of data in the frame. The data in
41388 the frame consists of a number of blocks, each introduced by a
41389 character indicating its type (at least register, memory, and trace
41390 state variable). The data in this section is raw binary, not a
41391 hexadecimal or other encoding; its endianness matches the target's
41394 @c FIXME bi-arch may require endianness/arch info in description section
41397 @item R @var{bytes}
41398 Register block. The number and ordering of bytes matches that of a
41399 @code{g} packet in the remote protocol. Note that these are the
41400 actual bytes, in target order and @value{GDBN} register order, not a
41401 hexadecimal encoding.
41403 @item M @var{address} @var{length} @var{bytes}...
41404 Memory block. This is a contiguous block of memory, at the 8-byte
41405 address @var{address}, with a 2-byte length @var{length}, followed by
41406 @var{length} bytes.
41408 @item V @var{number} @var{value}
41409 Trace state variable block. This records the 8-byte signed value
41410 @var{value} of trace state variable numbered @var{number}.
41414 Future enhancements of the trace file format may include additional types
41417 @node Index Section Format
41418 @appendix @code{.gdb_index} section format
41419 @cindex .gdb_index section format
41420 @cindex index section format
41422 This section documents the index section that is created by @code{save
41423 gdb-index} (@pxref{Index Files}). The index section is
41424 DWARF-specific; some knowledge of DWARF is assumed in this
41427 The mapped index file format is designed to be directly
41428 @code{mmap}able on any architecture. In most cases, a datum is
41429 represented using a little-endian 32-bit integer value, called an
41430 @code{offset_type}. Big endian machines must byte-swap the values
41431 before using them. Exceptions to this rule are noted. The data is
41432 laid out such that alignment is always respected.
41434 A mapped index consists of several areas, laid out in order.
41438 The file header. This is a sequence of values, of @code{offset_type}
41439 unless otherwise noted:
41443 The version number, currently 8. Versions 1, 2 and 3 are obsolete.
41444 Version 4 uses a different hashing function from versions 5 and 6.
41445 Version 6 includes symbols for inlined functions, whereas versions 4
41446 and 5 do not. Version 7 adds attributes to the CU indices in the
41447 symbol table. Version 8 specifies that symbols from DWARF type units
41448 (@samp{DW_TAG_type_unit}) refer to the type unit's symbol table and not the
41449 compilation unit (@samp{DW_TAG_comp_unit}) using the type.
41451 @value{GDBN} will only read version 4, 5, or 6 indices
41452 by specifying @code{set use-deprecated-index-sections on}.
41453 GDB has a workaround for potentially broken version 7 indices so it is
41454 currently not flagged as deprecated.
41457 The offset, from the start of the file, of the CU list.
41460 The offset, from the start of the file, of the types CU list. Note
41461 that this area can be empty, in which case this offset will be equal
41462 to the next offset.
41465 The offset, from the start of the file, of the address area.
41468 The offset, from the start of the file, of the symbol table.
41471 The offset, from the start of the file, of the constant pool.
41475 The CU list. This is a sequence of pairs of 64-bit little-endian
41476 values, sorted by the CU offset. The first element in each pair is
41477 the offset of a CU in the @code{.debug_info} section. The second
41478 element in each pair is the length of that CU. References to a CU
41479 elsewhere in the map are done using a CU index, which is just the
41480 0-based index into this table. Note that if there are type CUs, then
41481 conceptually CUs and type CUs form a single list for the purposes of
41485 The types CU list. This is a sequence of triplets of 64-bit
41486 little-endian values. In a triplet, the first value is the CU offset,
41487 the second value is the type offset in the CU, and the third value is
41488 the type signature. The types CU list is not sorted.
41491 The address area. The address area consists of a sequence of address
41492 entries. Each address entry has three elements:
41496 The low address. This is a 64-bit little-endian value.
41499 The high address. This is a 64-bit little-endian value. Like
41500 @code{DW_AT_high_pc}, the value is one byte beyond the end.
41503 The CU index. This is an @code{offset_type} value.
41507 The symbol table. This is an open-addressed hash table. The size of
41508 the hash table is always a power of 2.
41510 Each slot in the hash table consists of a pair of @code{offset_type}
41511 values. The first value is the offset of the symbol's name in the
41512 constant pool. The second value is the offset of the CU vector in the
41515 If both values are 0, then this slot in the hash table is empty. This
41516 is ok because while 0 is a valid constant pool index, it cannot be a
41517 valid index for both a string and a CU vector.
41519 The hash value for a table entry is computed by applying an
41520 iterative hash function to the symbol's name. Starting with an
41521 initial value of @code{r = 0}, each (unsigned) character @samp{c} in
41522 the string is incorporated into the hash using the formula depending on the
41527 The formula is @code{r = r * 67 + c - 113}.
41529 @item Versions 5 to 7
41530 The formula is @code{r = r * 67 + tolower (c) - 113}.
41533 The terminating @samp{\0} is not incorporated into the hash.
41535 The step size used in the hash table is computed via
41536 @code{((hash * 17) & (size - 1)) | 1}, where @samp{hash} is the hash
41537 value, and @samp{size} is the size of the hash table. The step size
41538 is used to find the next candidate slot when handling a hash
41541 The names of C@t{++} symbols in the hash table are canonicalized. We
41542 don't currently have a simple description of the canonicalization
41543 algorithm; if you intend to create new index sections, you must read
41547 The constant pool. This is simply a bunch of bytes. It is organized
41548 so that alignment is correct: CU vectors are stored first, followed by
41551 A CU vector in the constant pool is a sequence of @code{offset_type}
41552 values. The first value is the number of CU indices in the vector.
41553 Each subsequent value is the index and symbol attributes of a CU in
41554 the CU list. This element in the hash table is used to indicate which
41555 CUs define the symbol and how the symbol is used.
41556 See below for the format of each CU index+attributes entry.
41558 A string in the constant pool is zero-terminated.
41561 Attributes were added to CU index values in @code{.gdb_index} version 7.
41562 If a symbol has multiple uses within a CU then there is one
41563 CU index+attributes value for each use.
41565 The format of each CU index+attributes entry is as follows
41571 This is the index of the CU in the CU list.
41573 These bits are reserved for future purposes and must be zero.
41575 The kind of the symbol in the CU.
41579 This value is reserved and should not be used.
41580 By reserving zero the full @code{offset_type} value is backwards compatible
41581 with previous versions of the index.
41583 The symbol is a type.
41585 The symbol is a variable or an enum value.
41587 The symbol is a function.
41589 Any other kind of symbol.
41591 These values are reserved.
41595 This bit is zero if the value is global and one if it is static.
41597 The determination of whether a symbol is global or static is complicated.
41598 The authorative reference is the file @file{dwarf2read.c} in
41599 @value{GDBN} sources.
41603 This pseudo-code describes the computation of a symbol's kind and
41604 global/static attributes in the index.
41607 is_external = get_attribute (die, DW_AT_external);
41608 language = get_attribute (cu_die, DW_AT_language);
41611 case DW_TAG_typedef:
41612 case DW_TAG_base_type:
41613 case DW_TAG_subrange_type:
41617 case DW_TAG_enumerator:
41619 is_static = (language != CPLUS && language != JAVA);
41621 case DW_TAG_subprogram:
41623 is_static = ! (is_external || language == ADA);
41625 case DW_TAG_constant:
41627 is_static = ! is_external;
41629 case DW_TAG_variable:
41631 is_static = ! is_external;
41633 case DW_TAG_namespace:
41637 case DW_TAG_class_type:
41638 case DW_TAG_interface_type:
41639 case DW_TAG_structure_type:
41640 case DW_TAG_union_type:
41641 case DW_TAG_enumeration_type:
41643 is_static = (language != CPLUS && language != JAVA);
41652 @node GNU Free Documentation License
41653 @appendix GNU Free Documentation License
41656 @node Concept Index
41657 @unnumbered Concept Index
41661 @node Command and Variable Index
41662 @unnumbered Command, Variable, and Function Index
41667 % I think something like @@colophon should be in texinfo. In the
41669 \long\def\colophon{\hbox to0pt{}\vfill
41670 \centerline{The body of this manual is set in}
41671 \centerline{\fontname\tenrm,}
41672 \centerline{with headings in {\bf\fontname\tenbf}}
41673 \centerline{and examples in {\tt\fontname\tentt}.}
41674 \centerline{{\it\fontname\tenit\/},}
41675 \centerline{{\bf\fontname\tenbf}, and}
41676 \centerline{{\sl\fontname\tensl\/}}
41677 \centerline{are used for emphasis.}\vfill}
41679 % Blame: doc@@cygnus.com, 1991.