1 \input texinfo @c -*-texinfo-*-
2 @c Copyright (C) 1988-2014 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.
13 @settitle Debugging with @value{GDBN}
14 @setchapternewpage odd
23 @c To avoid file-name clashes between index.html and Index.html, when
24 @c the manual is produced on a Posix host and then moved to a
25 @c case-insensitive filesystem (e.g., MS-Windows), we separate the
26 @c indices into two: Concept Index and all the rest.
30 @c readline appendices use @vindex, @findex and @ftable,
31 @c annotate.texi and gdbmi use @findex.
34 @c !!set GDB manual's edition---not the same as GDB version!
35 @c This is updated by GNU Press.
38 @c !!set GDB edit command default editor
41 @c THIS MANUAL REQUIRES TEXINFO 4.0 OR LATER.
43 @c This is a dir.info fragment to support semi-automated addition of
44 @c manuals to an info tree.
45 @dircategory Software development
47 * Gdb: (gdb). The GNU debugger.
48 * gdbserver: (gdb) Server. The GNU debugging server.
52 @c man begin COPYRIGHT
53 Copyright @copyright{} 1988-2014 Free Software Foundation, Inc.
55 Permission is granted to copy, distribute and/or modify this document
56 under the terms of the GNU Free Documentation License, Version 1.3 or
57 any later version published by the Free Software Foundation; with the
58 Invariant Sections being ``Free Software'' and ``Free Software Needs
59 Free Documentation'', with the Front-Cover Texts being ``A GNU Manual,''
60 and with the Back-Cover Texts as in (a) below.
62 (a) The FSF's Back-Cover Text is: ``You are free to copy and modify
63 this GNU Manual. Buying copies from GNU Press supports the FSF in
64 developing GNU and promoting software freedom.''
69 This file documents the @sc{gnu} debugger @value{GDBN}.
71 This is the @value{EDITION} Edition, of @cite{Debugging with
72 @value{GDBN}: the @sc{gnu} Source-Level Debugger} for @value{GDBN}
73 @ifset VERSION_PACKAGE
74 @value{VERSION_PACKAGE}
76 Version @value{GDBVN}.
82 @title Debugging with @value{GDBN}
83 @subtitle The @sc{gnu} Source-Level Debugger
85 @subtitle @value{EDITION} Edition, for @value{GDBN} version @value{GDBVN}
86 @ifset VERSION_PACKAGE
88 @subtitle @value{VERSION_PACKAGE}
90 @author Richard Stallman, Roland Pesch, Stan Shebs, et al.
94 \hfill (Send bugs and comments on @value{GDBN} to @value{BUGURL}.)\par
95 \hfill {\it Debugging with @value{GDBN}}\par
96 \hfill \TeX{}info \texinfoversion\par
100 @vskip 0pt plus 1filll
101 Published by the Free Software Foundation @*
102 51 Franklin Street, Fifth Floor,
103 Boston, MA 02110-1301, USA@*
104 ISBN 978-0-9831592-3-0 @*
111 @node Top, Summary, (dir), (dir)
113 @top Debugging with @value{GDBN}
115 This file describes @value{GDBN}, the @sc{gnu} symbolic debugger.
117 This is the @value{EDITION} Edition, for @value{GDBN}
118 @ifset VERSION_PACKAGE
119 @value{VERSION_PACKAGE}
121 Version @value{GDBVN}.
123 Copyright (C) 1988-2014 Free Software Foundation, Inc.
125 This edition of the GDB manual is dedicated to the memory of Fred
126 Fish. Fred was a long-standing contributor to GDB and to Free
127 software in general. We will miss him.
130 * Summary:: Summary of @value{GDBN}
131 * Sample Session:: A sample @value{GDBN} session
133 * Invocation:: Getting in and out of @value{GDBN}
134 * Commands:: @value{GDBN} commands
135 * Running:: Running programs under @value{GDBN}
136 * Stopping:: Stopping and continuing
137 * Reverse Execution:: Running programs backward
138 * Process Record and Replay:: Recording inferior's execution and replaying it
139 * Stack:: Examining the stack
140 * Source:: Examining source files
141 * Data:: Examining data
142 * Optimized Code:: Debugging optimized code
143 * Macros:: Preprocessor Macros
144 * Tracepoints:: Debugging remote targets non-intrusively
145 * Overlays:: Debugging programs that use overlays
147 * Languages:: Using @value{GDBN} with different languages
149 * Symbols:: Examining the symbol table
150 * Altering:: Altering execution
151 * GDB Files:: @value{GDBN} files
152 * Targets:: Specifying a debugging target
153 * Remote Debugging:: Debugging remote programs
154 * Configurations:: Configuration-specific information
155 * Controlling GDB:: Controlling @value{GDBN}
156 * Extending GDB:: Extending @value{GDBN}
157 * Interpreters:: Command Interpreters
158 * TUI:: @value{GDBN} Text User Interface
159 * Emacs:: Using @value{GDBN} under @sc{gnu} Emacs
160 * GDB/MI:: @value{GDBN}'s Machine Interface.
161 * Annotations:: @value{GDBN}'s annotation interface.
162 * JIT Interface:: Using the JIT debugging interface.
163 * In-Process Agent:: In-Process Agent
165 * GDB Bugs:: Reporting bugs in @value{GDBN}
167 @ifset SYSTEM_READLINE
168 * Command Line Editing: (rluserman). Command Line Editing
169 * Using History Interactively: (history). Using History Interactively
171 @ifclear SYSTEM_READLINE
172 * Command Line Editing:: Command Line Editing
173 * Using History Interactively:: Using History Interactively
175 * In Memoriam:: In Memoriam
176 * Formatting Documentation:: How to format and print @value{GDBN} documentation
177 * Installing GDB:: Installing GDB
178 * Maintenance Commands:: Maintenance Commands
179 * Remote Protocol:: GDB Remote Serial Protocol
180 * Agent Expressions:: The GDB Agent Expression Mechanism
181 * Target Descriptions:: How targets can describe themselves to
183 * Operating System Information:: Getting additional information from
185 * Trace File Format:: GDB trace file format
186 * Index Section Format:: .gdb_index section format
187 * Man Pages:: Manual pages
188 * Copying:: GNU General Public License says
189 how you can copy and share GDB
190 * GNU Free Documentation License:: The license for this documentation
191 * Concept Index:: Index of @value{GDBN} concepts
192 * Command and Variable Index:: Index of @value{GDBN} commands, variables,
193 functions, and Python data types
201 @unnumbered Summary of @value{GDBN}
203 The purpose of a debugger such as @value{GDBN} is to allow you to see what is
204 going on ``inside'' another program while it executes---or what another
205 program was doing at the moment it crashed.
207 @value{GDBN} can do four main kinds of things (plus other things in support of
208 these) to help you catch bugs in the act:
212 Start your program, specifying anything that might affect its behavior.
215 Make your program stop on specified conditions.
218 Examine what has happened, when your program has stopped.
221 Change things in your program, so you can experiment with correcting the
222 effects of one bug and go on to learn about another.
225 You can use @value{GDBN} to debug programs written in C and C@t{++}.
226 For more information, see @ref{Supported Languages,,Supported Languages}.
227 For more information, see @ref{C,,C and C++}.
229 Support for D is partial. For information on D, see
233 Support for Modula-2 is partial. For information on Modula-2, see
234 @ref{Modula-2,,Modula-2}.
236 Support for OpenCL C is partial. For information on OpenCL C, see
237 @ref{OpenCL C,,OpenCL C}.
240 Debugging Pascal programs which use sets, subranges, file variables, or
241 nested functions does not currently work. @value{GDBN} does not support
242 entering expressions, printing values, or similar features using Pascal
246 @value{GDBN} can be used to debug programs written in Fortran, although
247 it may be necessary to refer to some variables with a trailing
250 @value{GDBN} can be used to debug programs written in Objective-C,
251 using either the Apple/NeXT or the GNU Objective-C runtime.
254 * Free Software:: Freely redistributable software
255 * Free Documentation:: Free Software Needs Free Documentation
256 * Contributors:: Contributors to GDB
260 @unnumberedsec Free Software
262 @value{GDBN} is @dfn{free software}, protected by the @sc{gnu}
263 General Public License
264 (GPL). The GPL gives you the freedom to copy or adapt a licensed
265 program---but every person getting a copy also gets with it the
266 freedom to modify that copy (which means that they must get access to
267 the source code), and the freedom to distribute further copies.
268 Typical software companies use copyrights to limit your freedoms; the
269 Free Software Foundation uses the GPL to preserve these freedoms.
271 Fundamentally, the General Public License is a license which says that
272 you have these freedoms and that you cannot take these freedoms away
275 @node Free Documentation
276 @unnumberedsec Free Software Needs Free Documentation
278 The biggest deficiency in the free software community today is not in
279 the software---it is the lack of good free documentation that we can
280 include with the free software. Many of our most important
281 programs do not come with free reference manuals and free introductory
282 texts. Documentation is an essential part of any software package;
283 when an important free software package does not come with a free
284 manual and a free tutorial, that is a major gap. We have many such
287 Consider Perl, for instance. The tutorial manuals that people
288 normally use are non-free. How did this come about? Because the
289 authors of those manuals published them with restrictive terms---no
290 copying, no modification, source files not available---which exclude
291 them from the free software world.
293 That wasn't the first time this sort of thing happened, and it was far
294 from the last. Many times we have heard a GNU user eagerly describe a
295 manual that he is writing, his intended contribution to the community,
296 only to learn that he had ruined everything by signing a publication
297 contract to make it non-free.
299 Free documentation, like free software, is a matter of freedom, not
300 price. The problem with the non-free manual is not that publishers
301 charge a price for printed copies---that in itself is fine. (The Free
302 Software Foundation sells printed copies of manuals, too.) The
303 problem is the restrictions on the use of the manual. Free manuals
304 are available in source code form, and give you permission to copy and
305 modify. Non-free manuals do not allow this.
307 The criteria of freedom for a free manual are roughly the same as for
308 free software. Redistribution (including the normal kinds of
309 commercial redistribution) must be permitted, so that the manual can
310 accompany every copy of the program, both on-line and on paper.
312 Permission for modification of the technical content is crucial too.
313 When people modify the software, adding or changing features, if they
314 are conscientious they will change the manual too---so they can
315 provide accurate and clear documentation for the modified program. A
316 manual that leaves you no choice but to write a new manual to document
317 a changed version of the program is not really available to our
320 Some kinds of limits on the way modification is handled are
321 acceptable. For example, requirements to preserve the original
322 author's copyright notice, the distribution terms, or the list of
323 authors, are ok. It is also no problem to require modified versions
324 to include notice that they were modified. Even entire sections that
325 may not be deleted or changed are acceptable, as long as they deal
326 with nontechnical topics (like this one). These kinds of restrictions
327 are acceptable because they don't obstruct the community's normal use
330 However, it must be possible to modify all the @emph{technical}
331 content of the manual, and then distribute the result in all the usual
332 media, through all the usual channels. Otherwise, the restrictions
333 obstruct the use of the manual, it is not free, and we need another
334 manual to replace it.
336 Please spread the word about this issue. Our community continues to
337 lose manuals to proprietary publishing. If we spread the word that
338 free software needs free reference manuals and free tutorials, perhaps
339 the next person who wants to contribute by writing documentation will
340 realize, before it is too late, that only free manuals contribute to
341 the free software community.
343 If you are writing documentation, please insist on publishing it under
344 the GNU Free Documentation License or another free documentation
345 license. Remember that this decision requires your approval---you
346 don't have to let the publisher decide. Some commercial publishers
347 will use a free license if you insist, but they will not propose the
348 option; it is up to you to raise the issue and say firmly that this is
349 what you want. If the publisher you are dealing with refuses, please
350 try other publishers. If you're not sure whether a proposed license
351 is free, write to @email{licensing@@gnu.org}.
353 You can encourage commercial publishers to sell more free, copylefted
354 manuals and tutorials by buying them, and particularly by buying
355 copies from the publishers that paid for their writing or for major
356 improvements. Meanwhile, try to avoid buying non-free documentation
357 at all. Check the distribution terms of a manual before you buy it,
358 and insist that whoever seeks your business must respect your freedom.
359 Check the history of the book, and try to reward the publishers that
360 have paid or pay the authors to work on it.
362 The Free Software Foundation maintains a list of free documentation
363 published by other publishers, at
364 @url{http://www.fsf.org/doc/other-free-books.html}.
367 @unnumberedsec Contributors to @value{GDBN}
369 Richard Stallman was the original author of @value{GDBN}, and of many
370 other @sc{gnu} programs. Many others have contributed to its
371 development. This section attempts to credit major contributors. One
372 of the virtues of free software is that everyone is free to contribute
373 to it; with regret, we cannot actually acknowledge everyone here. The
374 file @file{ChangeLog} in the @value{GDBN} distribution approximates a
375 blow-by-blow account.
377 Changes much prior to version 2.0 are lost in the mists of time.
380 @emph{Plea:} Additions to this section are particularly welcome. If you
381 or your friends (or enemies, to be evenhanded) have been unfairly
382 omitted from this list, we would like to add your names!
385 So that they may not regard their many labors as thankless, we
386 particularly thank those who shepherded @value{GDBN} through major
388 Andrew Cagney (releases 6.3, 6.2, 6.1, 6.0, 5.3, 5.2, 5.1 and 5.0);
389 Jim Blandy (release 4.18);
390 Jason Molenda (release 4.17);
391 Stan Shebs (release 4.14);
392 Fred Fish (releases 4.16, 4.15, 4.13, 4.12, 4.11, 4.10, and 4.9);
393 Stu Grossman and John Gilmore (releases 4.8, 4.7, 4.6, 4.5, and 4.4);
394 John Gilmore (releases 4.3, 4.2, 4.1, 4.0, and 3.9);
395 Jim Kingdon (releases 3.5, 3.4, and 3.3);
396 and Randy Smith (releases 3.2, 3.1, and 3.0).
398 Richard Stallman, assisted at various times by Peter TerMaat, Chris
399 Hanson, and Richard Mlynarik, handled releases through 2.8.
401 Michael Tiemann is the author of most of the @sc{gnu} C@t{++} support
402 in @value{GDBN}, with significant additional contributions from Per
403 Bothner and Daniel Berlin. James Clark wrote the @sc{gnu} C@t{++}
404 demangler. Early work on C@t{++} was by Peter TerMaat (who also did
405 much general update work leading to release 3.0).
407 @value{GDBN} uses the BFD subroutine library to examine multiple
408 object-file formats; BFD was a joint project of David V.
409 Henkel-Wallace, Rich Pixley, Steve Chamberlain, and John Gilmore.
411 David Johnson wrote the original COFF support; Pace Willison did
412 the original support for encapsulated COFF.
414 Brent Benson of Harris Computer Systems contributed DWARF 2 support.
416 Adam de Boor and Bradley Davis contributed the ISI Optimum V support.
417 Per Bothner, Noboyuki Hikichi, and Alessandro Forin contributed MIPS
419 Jean-Daniel Fekete contributed Sun 386i support.
420 Chris Hanson improved the HP9000 support.
421 Noboyuki Hikichi and Tomoyuki Hasei contributed Sony/News OS 3 support.
422 David Johnson contributed Encore Umax support.
423 Jyrki Kuoppala contributed Altos 3068 support.
424 Jeff Law contributed HP PA and SOM support.
425 Keith Packard contributed NS32K support.
426 Doug Rabson contributed Acorn Risc Machine support.
427 Bob Rusk contributed Harris Nighthawk CX-UX support.
428 Chris Smith contributed Convex support (and Fortran debugging).
429 Jonathan Stone contributed Pyramid support.
430 Michael Tiemann contributed SPARC support.
431 Tim Tucker contributed support for the Gould NP1 and Gould Powernode.
432 Pace Willison contributed Intel 386 support.
433 Jay Vosburgh contributed Symmetry support.
434 Marko Mlinar contributed OpenRISC 1000 support.
436 Andreas Schwab contributed M68K @sc{gnu}/Linux support.
438 Rich Schaefer and Peter Schauer helped with support of SunOS shared
441 Jay Fenlason and Roland McGrath ensured that @value{GDBN} and GAS agree
442 about several machine instruction sets.
444 Patrick Duval, Ted Goldstein, Vikram Koka and Glenn Engel helped develop
445 remote debugging. Intel Corporation, Wind River Systems, AMD, and ARM
446 contributed remote debugging modules for the i960, VxWorks, A29K UDI,
447 and RDI targets, respectively.
449 Brian Fox is the author of the readline libraries providing
450 command-line editing and command history.
452 Andrew Beers of SUNY Buffalo wrote the language-switching code, the
453 Modula-2 support, and contributed the Languages chapter of this manual.
455 Fred Fish wrote most of the support for Unix System Vr4.
456 He also enhanced the command-completion support to cover C@t{++} overloaded
459 Hitachi America (now Renesas America), Ltd. sponsored the support for
460 H8/300, H8/500, and Super-H processors.
462 NEC sponsored the support for the v850, Vr4xxx, and Vr5xxx processors.
464 Mitsubishi (now Renesas) sponsored the support for D10V, D30V, and M32R/D
467 Toshiba sponsored the support for the TX39 Mips processor.
469 Matsushita sponsored the support for the MN10200 and MN10300 processors.
471 Fujitsu sponsored the support for SPARClite and FR30 processors.
473 Kung Hsu, Jeff Law, and Rick Sladkey added support for hardware
476 Michael Snyder added support for tracepoints.
478 Stu Grossman wrote gdbserver.
480 Jim Kingdon, Peter Schauer, Ian Taylor, and Stu Grossman made
481 nearly innumerable bug fixes and cleanups throughout @value{GDBN}.
483 The following people at the Hewlett-Packard Company contributed
484 support for the PA-RISC 2.0 architecture, HP-UX 10.20, 10.30, and 11.0
485 (narrow mode), HP's implementation of kernel threads, HP's aC@t{++}
486 compiler, and the Text User Interface (nee Terminal User Interface):
487 Ben Krepp, Richard Title, John Bishop, Susan Macchia, Kathy Mann,
488 Satish Pai, India Paul, Steve Rehrauer, and Elena Zannoni. Kim Haase
489 provided HP-specific information in this manual.
491 DJ Delorie ported @value{GDBN} to MS-DOS, for the DJGPP project.
492 Robert Hoehne made significant contributions to the DJGPP port.
494 Cygnus Solutions has sponsored @value{GDBN} maintenance and much of its
495 development since 1991. Cygnus engineers who have worked on @value{GDBN}
496 fulltime include Mark Alexander, Jim Blandy, Per Bothner, Kevin
497 Buettner, Edith Epstein, Chris Faylor, Fred Fish, Martin Hunt, Jim
498 Ingham, John Gilmore, Stu Grossman, Kung Hsu, Jim Kingdon, John Metzler,
499 Fernando Nasser, Geoffrey Noer, Dawn Perchik, Rich Pixley, Zdenek
500 Radouch, Keith Seitz, Stan Shebs, David Taylor, and Elena Zannoni. In
501 addition, Dave Brolley, Ian Carmichael, Steve Chamberlain, Nick Clifton,
502 JT Conklin, Stan Cox, DJ Delorie, Ulrich Drepper, Frank Eigler, Doug
503 Evans, Sean Fagan, David Henkel-Wallace, Richard Henderson, Jeff
504 Holcomb, Jeff Law, Jim Lemke, Tom Lord, Bob Manson, Michael Meissner,
505 Jason Merrill, Catherine Moore, Drew Moseley, Ken Raeburn, Gavin
506 Romig-Koch, Rob Savoye, Jamie Smith, Mike Stump, Ian Taylor, Angela
507 Thomas, Michael Tiemann, Tom Tromey, Ron Unrau, Jim Wilson, and David
508 Zuhn have made contributions both large and small.
510 Andrew Cagney, Fernando Nasser, and Elena Zannoni, while working for
511 Cygnus Solutions, implemented the original @sc{gdb/mi} interface.
513 Jim Blandy added support for preprocessor macros, while working for Red
516 Andrew Cagney designed @value{GDBN}'s architecture vector. Many
517 people including Andrew Cagney, Stephane Carrez, Randolph Chung, Nick
518 Duffek, Richard Henderson, Mark Kettenis, Grace Sainsbury, Kei
519 Sakamoto, Yoshinori Sato, Michael Snyder, Andreas Schwab, Jason
520 Thorpe, Corinna Vinschen, Ulrich Weigand, and Elena Zannoni, helped
521 with the migration of old architectures to this new framework.
523 Andrew Cagney completely re-designed and re-implemented @value{GDBN}'s
524 unwinder framework, this consisting of a fresh new design featuring
525 frame IDs, independent frame sniffers, and the sentinel frame. Mark
526 Kettenis implemented the @sc{dwarf 2} unwinder, Jeff Johnston the
527 libunwind unwinder, and Andrew Cagney the dummy, sentinel, tramp, and
528 trad unwinders. The architecture-specific changes, each involving a
529 complete rewrite of the architecture's frame code, were carried out by
530 Jim Blandy, Joel Brobecker, Kevin Buettner, Andrew Cagney, Stephane
531 Carrez, Randolph Chung, Orjan Friberg, Richard Henderson, Daniel
532 Jacobowitz, Jeff Johnston, Mark Kettenis, Theodore A. Roth, Kei
533 Sakamoto, Yoshinori Sato, Michael Snyder, Corinna Vinschen, and Ulrich
536 Christian Zankel, Ross Morley, Bob Wilson, and Maxim Grigoriev from
537 Tensilica, Inc.@: contributed support for Xtensa processors. Others
538 who have worked on the Xtensa port of @value{GDBN} in the past include
539 Steve Tjiang, John Newlin, and Scott Foehner.
541 Michael Eager and staff of Xilinx, Inc., contributed support for the
542 Xilinx MicroBlaze architecture.
545 @chapter A Sample @value{GDBN} Session
547 You can use this manual at your leisure to read all about @value{GDBN}.
548 However, a handful of commands are enough to get started using the
549 debugger. This chapter illustrates those commands.
552 In this sample session, we emphasize user input like this: @b{input},
553 to make it easier to pick out from the surrounding output.
556 @c FIXME: this example may not be appropriate for some configs, where
557 @c FIXME...primary interest is in remote use.
559 One of the preliminary versions of @sc{gnu} @code{m4} (a generic macro
560 processor) exhibits the following bug: sometimes, when we change its
561 quote strings from the default, the commands used to capture one macro
562 definition within another stop working. In the following short @code{m4}
563 session, we define a macro @code{foo} which expands to @code{0000}; we
564 then use the @code{m4} built-in @code{defn} to define @code{bar} as the
565 same thing. However, when we change the open quote string to
566 @code{<QUOTE>} and the close quote string to @code{<UNQUOTE>}, the same
567 procedure fails to define a new synonym @code{baz}:
576 @b{define(bar,defn(`foo'))}
580 @b{changequote(<QUOTE>,<UNQUOTE>)}
582 @b{define(baz,defn(<QUOTE>foo<UNQUOTE>))}
585 m4: End of input: 0: fatal error: EOF in string
589 Let us use @value{GDBN} to try to see what is going on.
592 $ @b{@value{GDBP} m4}
593 @c FIXME: this falsifies the exact text played out, to permit smallbook
594 @c FIXME... format to come out better.
595 @value{GDBN} is free software and you are welcome to distribute copies
596 of it under certain conditions; type "show copying" to see
598 There is absolutely no warranty for @value{GDBN}; type "show warranty"
601 @value{GDBN} @value{GDBVN}, Copyright 1999 Free Software Foundation, Inc...
606 @value{GDBN} reads only enough symbol data to know where to find the
607 rest when needed; as a result, the first prompt comes up very quickly.
608 We now tell @value{GDBN} to use a narrower display width than usual, so
609 that examples fit in this manual.
612 (@value{GDBP}) @b{set width 70}
616 We need to see how the @code{m4} built-in @code{changequote} works.
617 Having looked at the source, we know the relevant subroutine is
618 @code{m4_changequote}, so we set a breakpoint there with the @value{GDBN}
619 @code{break} command.
622 (@value{GDBP}) @b{break m4_changequote}
623 Breakpoint 1 at 0x62f4: file builtin.c, line 879.
627 Using the @code{run} command, we start @code{m4} running under @value{GDBN}
628 control; as long as control does not reach the @code{m4_changequote}
629 subroutine, the program runs as usual:
632 (@value{GDBP}) @b{run}
633 Starting program: /work/Editorial/gdb/gnu/m4/m4
641 To trigger the breakpoint, we call @code{changequote}. @value{GDBN}
642 suspends execution of @code{m4}, displaying information about the
643 context where it stops.
646 @b{changequote(<QUOTE>,<UNQUOTE>)}
648 Breakpoint 1, m4_changequote (argc=3, argv=0x33c70)
650 879 if (bad_argc(TOKEN_DATA_TEXT(argv[0]),argc,1,3))
654 Now we use the command @code{n} (@code{next}) to advance execution to
655 the next line of the current function.
659 882 set_quotes((argc >= 2) ? TOKEN_DATA_TEXT(argv[1])\
664 @code{set_quotes} looks like a promising subroutine. We can go into it
665 by using the command @code{s} (@code{step}) instead of @code{next}.
666 @code{step} goes to the next line to be executed in @emph{any}
667 subroutine, so it steps into @code{set_quotes}.
671 set_quotes (lq=0x34c78 "<QUOTE>", rq=0x34c88 "<UNQUOTE>")
673 530 if (lquote != def_lquote)
677 The display that shows the subroutine where @code{m4} is now
678 suspended (and its arguments) is called a stack frame display. It
679 shows a summary of the stack. We can use the @code{backtrace}
680 command (which can also be spelled @code{bt}), to see where we are
681 in the stack as a whole: the @code{backtrace} command displays a
682 stack frame for each active subroutine.
685 (@value{GDBP}) @b{bt}
686 #0 set_quotes (lq=0x34c78 "<QUOTE>", rq=0x34c88 "<UNQUOTE>")
688 #1 0x6344 in m4_changequote (argc=3, argv=0x33c70)
690 #2 0x8174 in expand_macro (sym=0x33320) at macro.c:242
691 #3 0x7a88 in expand_token (obs=0x0, t=209696, td=0xf7fffa30)
693 #4 0x79dc in expand_input () at macro.c:40
694 #5 0x2930 in main (argc=0, argv=0xf7fffb20) at m4.c:195
698 We step through a few more lines to see what happens. The first two
699 times, we can use @samp{s}; the next two times we use @code{n} to avoid
700 falling into the @code{xstrdup} subroutine.
704 0x3b5c 532 if (rquote != def_rquote)
706 0x3b80 535 lquote = (lq == nil || *lq == '\0') ? \
707 def_lquote : xstrdup(lq);
709 536 rquote = (rq == nil || *rq == '\0') ? def_rquote\
712 538 len_lquote = strlen(rquote);
716 The last line displayed looks a little odd; we can examine the variables
717 @code{lquote} and @code{rquote} to see if they are in fact the new left
718 and right quotes we specified. We use the command @code{p}
719 (@code{print}) to see their values.
722 (@value{GDBP}) @b{p lquote}
723 $1 = 0x35d40 "<QUOTE>"
724 (@value{GDBP}) @b{p rquote}
725 $2 = 0x35d50 "<UNQUOTE>"
729 @code{lquote} and @code{rquote} are indeed the new left and right quotes.
730 To look at some context, we can display ten lines of source
731 surrounding the current line with the @code{l} (@code{list}) command.
737 535 lquote = (lq == nil || *lq == '\0') ? def_lquote\
739 536 rquote = (rq == nil || *rq == '\0') ? def_rquote\
742 538 len_lquote = strlen(rquote);
743 539 len_rquote = strlen(lquote);
750 Let us step past the two lines that set @code{len_lquote} and
751 @code{len_rquote}, and then examine the values of those variables.
755 539 len_rquote = strlen(lquote);
758 (@value{GDBP}) @b{p len_lquote}
760 (@value{GDBP}) @b{p len_rquote}
765 That certainly looks wrong, assuming @code{len_lquote} and
766 @code{len_rquote} are meant to be the lengths of @code{lquote} and
767 @code{rquote} respectively. We can set them to better values using
768 the @code{p} command, since it can print the value of
769 any expression---and that expression can include subroutine calls and
773 (@value{GDBP}) @b{p len_lquote=strlen(lquote)}
775 (@value{GDBP}) @b{p len_rquote=strlen(rquote)}
780 Is that enough to fix the problem of using the new quotes with the
781 @code{m4} built-in @code{defn}? We can allow @code{m4} to continue
782 executing with the @code{c} (@code{continue}) command, and then try the
783 example that caused trouble initially:
789 @b{define(baz,defn(<QUOTE>foo<UNQUOTE>))}
796 Success! The new quotes now work just as well as the default ones. The
797 problem seems to have been just the two typos defining the wrong
798 lengths. We allow @code{m4} exit by giving it an EOF as input:
802 Program exited normally.
806 The message @samp{Program exited normally.} is from @value{GDBN}; it
807 indicates @code{m4} has finished executing. We can end our @value{GDBN}
808 session with the @value{GDBN} @code{quit} command.
811 (@value{GDBP}) @b{quit}
815 @chapter Getting In and Out of @value{GDBN}
817 This chapter discusses how to start @value{GDBN}, and how to get out of it.
821 type @samp{@value{GDBP}} to start @value{GDBN}.
823 type @kbd{quit} or @kbd{Ctrl-d} to exit.
827 * Invoking GDB:: How to start @value{GDBN}
828 * Quitting GDB:: How to quit @value{GDBN}
829 * Shell Commands:: How to use shell commands inside @value{GDBN}
830 * Logging Output:: How to log @value{GDBN}'s output to a file
834 @section Invoking @value{GDBN}
836 Invoke @value{GDBN} by running the program @code{@value{GDBP}}. Once started,
837 @value{GDBN} reads commands from the terminal until you tell it to exit.
839 You can also run @code{@value{GDBP}} with a variety of arguments and options,
840 to specify more of your debugging environment at the outset.
842 The command-line options described here are designed
843 to cover a variety of situations; in some environments, some of these
844 options may effectively be unavailable.
846 The most usual way to start @value{GDBN} is with one argument,
847 specifying an executable program:
850 @value{GDBP} @var{program}
854 You can also start with both an executable program and a core file
858 @value{GDBP} @var{program} @var{core}
861 You can, instead, specify a process ID as a second argument, if you want
862 to debug a running process:
865 @value{GDBP} @var{program} 1234
869 would attach @value{GDBN} to process @code{1234} (unless you also have a file
870 named @file{1234}; @value{GDBN} does check for a core file first).
872 Taking advantage of the second command-line argument requires a fairly
873 complete operating system; when you use @value{GDBN} as a remote
874 debugger attached to a bare board, there may not be any notion of
875 ``process'', and there is often no way to get a core dump. @value{GDBN}
876 will warn you if it is unable to attach or to read core dumps.
878 You can optionally have @code{@value{GDBP}} pass any arguments after the
879 executable file to the inferior using @code{--args}. This option stops
882 @value{GDBP} --args gcc -O2 -c foo.c
884 This will cause @code{@value{GDBP}} to debug @code{gcc}, and to set
885 @code{gcc}'s command-line arguments (@pxref{Arguments}) to @samp{-O2 -c foo.c}.
887 You can run @code{@value{GDBP}} without printing the front material, which describes
888 @value{GDBN}'s non-warranty, by specifying @code{-silent}:
895 You can further control how @value{GDBN} starts up by using command-line
896 options. @value{GDBN} itself can remind you of the options available.
906 to display all available options and briefly describe their use
907 (@samp{@value{GDBP} -h} is a shorter equivalent).
909 All options and command line arguments you give are processed
910 in sequential order. The order makes a difference when the
911 @samp{-x} option is used.
915 * File Options:: Choosing files
916 * Mode Options:: Choosing modes
917 * Startup:: What @value{GDBN} does during startup
921 @subsection Choosing Files
923 When @value{GDBN} starts, it reads any arguments other than options as
924 specifying an executable file and core file (or process ID). This is
925 the same as if the arguments were specified by the @samp{-se} and
926 @samp{-c} (or @samp{-p}) options respectively. (@value{GDBN} reads the
927 first argument that does not have an associated option flag as
928 equivalent to the @samp{-se} option followed by that argument; and the
929 second argument that does not have an associated option flag, if any, as
930 equivalent to the @samp{-c}/@samp{-p} option followed by that argument.)
931 If the second argument begins with a decimal digit, @value{GDBN} will
932 first attempt to attach to it as a process, and if that fails, attempt
933 to open it as a corefile. If you have a corefile whose name begins with
934 a digit, you can prevent @value{GDBN} from treating it as a pid by
935 prefixing it with @file{./}, e.g.@: @file{./12345}.
937 If @value{GDBN} has not been configured to included core file support,
938 such as for most embedded targets, then it will complain about a second
939 argument and ignore it.
941 Many options have both long and short forms; both are shown in the
942 following list. @value{GDBN} also recognizes the long forms if you truncate
943 them, so long as enough of the option is present to be unambiguous.
944 (If you prefer, you can flag option arguments with @samp{--} rather
945 than @samp{-}, though we illustrate the more usual convention.)
947 @c NOTE: the @cindex entries here use double dashes ON PURPOSE. This
948 @c way, both those who look for -foo and --foo in the index, will find
952 @item -symbols @var{file}
954 @cindex @code{--symbols}
956 Read symbol table from file @var{file}.
958 @item -exec @var{file}
960 @cindex @code{--exec}
962 Use file @var{file} as the executable file to execute when appropriate,
963 and for examining pure data in conjunction with a core dump.
967 Read symbol table from file @var{file} and use it as the executable
970 @item -core @var{file}
972 @cindex @code{--core}
974 Use file @var{file} as a core dump to examine.
976 @item -pid @var{number}
977 @itemx -p @var{number}
980 Connect to process ID @var{number}, as with the @code{attach} command.
982 @item -command @var{file}
984 @cindex @code{--command}
986 Execute commands from file @var{file}. The contents of this file is
987 evaluated exactly as the @code{source} command would.
988 @xref{Command Files,, Command files}.
990 @item -eval-command @var{command}
991 @itemx -ex @var{command}
992 @cindex @code{--eval-command}
994 Execute a single @value{GDBN} command.
996 This option may be used multiple times to call multiple commands. It may
997 also be interleaved with @samp{-command} as required.
1000 @value{GDBP} -ex 'target sim' -ex 'load' \
1001 -x setbreakpoints -ex 'run' a.out
1004 @item -init-command @var{file}
1005 @itemx -ix @var{file}
1006 @cindex @code{--init-command}
1008 Execute commands from file @var{file} before loading the inferior (but
1009 after loading gdbinit files).
1012 @item -init-eval-command @var{command}
1013 @itemx -iex @var{command}
1014 @cindex @code{--init-eval-command}
1016 Execute a single @value{GDBN} command before loading the inferior (but
1017 after loading gdbinit files).
1020 @item -directory @var{directory}
1021 @itemx -d @var{directory}
1022 @cindex @code{--directory}
1024 Add @var{directory} to the path to search for source and script files.
1028 @cindex @code{--readnow}
1030 Read each symbol file's entire symbol table immediately, rather than
1031 the default, which is to read it incrementally as it is needed.
1032 This makes startup slower, but makes future operations faster.
1037 @subsection Choosing Modes
1039 You can run @value{GDBN} in various alternative modes---for example, in
1040 batch mode or quiet mode.
1048 Do not execute commands found in any initialization file.
1049 There are three init files, loaded in the following order:
1052 @item @file{system.gdbinit}
1053 This is the system-wide init file.
1054 Its location is specified with the @code{--with-system-gdbinit}
1055 configure option (@pxref{System-wide configuration}).
1056 It is loaded first when @value{GDBN} starts, before command line options
1057 have been processed.
1058 @item @file{~/.gdbinit}
1059 This is the init file in your home directory.
1060 It is loaded next, after @file{system.gdbinit}, and before
1061 command options have been processed.
1062 @item @file{./.gdbinit}
1063 This is the init file in the current directory.
1064 It is loaded last, after command line options other than @code{-x} and
1065 @code{-ex} have been processed. Command line options @code{-x} and
1066 @code{-ex} are processed last, after @file{./.gdbinit} has been loaded.
1069 For further documentation on startup processing, @xref{Startup}.
1070 For documentation on how to write command files,
1071 @xref{Command Files,,Command Files}.
1076 Do not execute commands found in @file{~/.gdbinit}, the init file
1077 in your home directory.
1083 @cindex @code{--quiet}
1084 @cindex @code{--silent}
1086 ``Quiet''. Do not print the introductory and copyright messages. These
1087 messages are also suppressed in batch mode.
1090 @cindex @code{--batch}
1091 Run in batch mode. Exit with status @code{0} after processing all the
1092 command files specified with @samp{-x} (and all commands from
1093 initialization files, if not inhibited with @samp{-n}). Exit with
1094 nonzero status if an error occurs in executing the @value{GDBN} commands
1095 in the command files. Batch mode also disables pagination, sets unlimited
1096 terminal width and height @pxref{Screen Size}, and acts as if @kbd{set confirm
1097 off} were in effect (@pxref{Messages/Warnings}).
1099 Batch mode may be useful for running @value{GDBN} as a filter, for
1100 example to download and run a program on another computer; in order to
1101 make this more useful, the message
1104 Program exited normally.
1108 (which is ordinarily issued whenever a program running under
1109 @value{GDBN} control terminates) is not issued when running in batch
1113 @cindex @code{--batch-silent}
1114 Run in batch mode exactly like @samp{-batch}, but totally silently. All
1115 @value{GDBN} output to @code{stdout} is prevented (@code{stderr} is
1116 unaffected). This is much quieter than @samp{-silent} and would be useless
1117 for an interactive session.
1119 This is particularly useful when using targets that give @samp{Loading section}
1120 messages, for example.
1122 Note that targets that give their output via @value{GDBN}, as opposed to
1123 writing directly to @code{stdout}, will also be made silent.
1125 @item -return-child-result
1126 @cindex @code{--return-child-result}
1127 The return code from @value{GDBN} will be the return code from the child
1128 process (the process being debugged), with the following exceptions:
1132 @value{GDBN} exits abnormally. E.g., due to an incorrect argument or an
1133 internal error. In this case the exit code is the same as it would have been
1134 without @samp{-return-child-result}.
1136 The user quits with an explicit value. E.g., @samp{quit 1}.
1138 The child process never runs, or is not allowed to terminate, in which case
1139 the exit code will be -1.
1142 This option is useful in conjunction with @samp{-batch} or @samp{-batch-silent},
1143 when @value{GDBN} is being used as a remote program loader or simulator
1148 @cindex @code{--nowindows}
1150 ``No windows''. If @value{GDBN} comes with a graphical user interface
1151 (GUI) built in, then this option tells @value{GDBN} to only use the command-line
1152 interface. If no GUI is available, this option has no effect.
1156 @cindex @code{--windows}
1158 If @value{GDBN} includes a GUI, then this option requires it to be
1161 @item -cd @var{directory}
1163 Run @value{GDBN} using @var{directory} as its working directory,
1164 instead of the current directory.
1166 @item -data-directory @var{directory}
1167 @cindex @code{--data-directory}
1168 Run @value{GDBN} using @var{directory} as its data directory.
1169 The data directory is where @value{GDBN} searches for its
1170 auxiliary files. @xref{Data Files}.
1174 @cindex @code{--fullname}
1176 @sc{gnu} Emacs sets this option when it runs @value{GDBN} as a
1177 subprocess. It tells @value{GDBN} to output the full file name and line
1178 number in a standard, recognizable fashion each time a stack frame is
1179 displayed (which includes each time your program stops). This
1180 recognizable format looks like two @samp{\032} characters, followed by
1181 the file name, line number and character position separated by colons,
1182 and a newline. The Emacs-to-@value{GDBN} interface program uses the two
1183 @samp{\032} characters as a signal to display the source code for the
1186 @item -annotate @var{level}
1187 @cindex @code{--annotate}
1188 This option sets the @dfn{annotation level} inside @value{GDBN}. Its
1189 effect is identical to using @samp{set annotate @var{level}}
1190 (@pxref{Annotations}). The annotation @var{level} controls how much
1191 information @value{GDBN} prints together with its prompt, values of
1192 expressions, source lines, and other types of output. Level 0 is the
1193 normal, level 1 is for use when @value{GDBN} is run as a subprocess of
1194 @sc{gnu} Emacs, level 3 is the maximum annotation suitable for programs
1195 that control @value{GDBN}, and level 2 has been deprecated.
1197 The annotation mechanism has largely been superseded by @sc{gdb/mi}
1201 @cindex @code{--args}
1202 Change interpretation of command line so that arguments following the
1203 executable file are passed as command line arguments to the inferior.
1204 This option stops option processing.
1206 @item -baud @var{bps}
1208 @cindex @code{--baud}
1210 Set the line speed (baud rate or bits per second) of any serial
1211 interface used by @value{GDBN} for remote debugging.
1213 @item -l @var{timeout}
1215 Set the timeout (in seconds) of any communication used by @value{GDBN}
1216 for remote debugging.
1218 @item -tty @var{device}
1219 @itemx -t @var{device}
1220 @cindex @code{--tty}
1222 Run using @var{device} for your program's standard input and output.
1223 @c FIXME: kingdon thinks there is more to -tty. Investigate.
1225 @c resolve the situation of these eventually
1227 @cindex @code{--tui}
1228 Activate the @dfn{Text User Interface} when starting. The Text User
1229 Interface manages several text windows on the terminal, showing
1230 source, assembly, registers and @value{GDBN} command outputs
1231 (@pxref{TUI, ,@value{GDBN} Text User Interface}). Do not use this
1232 option if you run @value{GDBN} from Emacs (@pxref{Emacs, ,
1233 Using @value{GDBN} under @sc{gnu} Emacs}).
1236 @c @cindex @code{--xdb}
1237 @c Run in XDB compatibility mode, allowing the use of certain XDB commands.
1238 @c For information, see the file @file{xdb_trans.html}, which is usually
1239 @c installed in the directory @code{/opt/langtools/wdb/doc} on HP-UX
1242 @item -interpreter @var{interp}
1243 @cindex @code{--interpreter}
1244 Use the interpreter @var{interp} for interface with the controlling
1245 program or device. This option is meant to be set by programs which
1246 communicate with @value{GDBN} using it as a back end.
1247 @xref{Interpreters, , Command Interpreters}.
1249 @samp{--interpreter=mi} (or @samp{--interpreter=mi2}) causes
1250 @value{GDBN} to use the @dfn{@sc{gdb/mi} interface} (@pxref{GDB/MI, ,
1251 The @sc{gdb/mi} Interface}) included since @value{GDBN} version 6.0. The
1252 previous @sc{gdb/mi} interface, included in @value{GDBN} version 5.3 and
1253 selected with @samp{--interpreter=mi1}, is deprecated. Earlier
1254 @sc{gdb/mi} interfaces are no longer supported.
1257 @cindex @code{--write}
1258 Open the executable and core files for both reading and writing. This
1259 is equivalent to the @samp{set write on} command inside @value{GDBN}
1263 @cindex @code{--statistics}
1264 This option causes @value{GDBN} to print statistics about time and
1265 memory usage after it completes each command and returns to the prompt.
1268 @cindex @code{--version}
1269 This option causes @value{GDBN} to print its version number and
1270 no-warranty blurb, and exit.
1272 @item -configuration
1273 @cindex @code{--configuration}
1274 This option causes @value{GDBN} to print details about its build-time
1275 configuration parameters, and then exit. These details can be
1276 important when reporting @value{GDBN} bugs (@pxref{GDB Bugs}).
1281 @subsection What @value{GDBN} Does During Startup
1282 @cindex @value{GDBN} startup
1284 Here's the description of what @value{GDBN} does during session startup:
1288 Sets up the command interpreter as specified by the command line
1289 (@pxref{Mode Options, interpreter}).
1293 Reads the system-wide @dfn{init file} (if @option{--with-system-gdbinit} was
1294 used when building @value{GDBN}; @pxref{System-wide configuration,
1295 ,System-wide configuration and settings}) and executes all the commands in
1298 @anchor{Home Directory Init File}
1300 Reads the init file (if any) in your home directory@footnote{On
1301 DOS/Windows systems, the home directory is the one pointed to by the
1302 @code{HOME} environment variable.} and executes all the commands in
1305 @anchor{Option -init-eval-command}
1307 Executes commands and command files specified by the @samp{-iex} and
1308 @samp{-ix} options in their specified order. Usually you should use the
1309 @samp{-ex} and @samp{-x} options instead, but this way you can apply
1310 settings before @value{GDBN} init files get executed and before inferior
1314 Processes command line options and operands.
1316 @anchor{Init File in the Current Directory during Startup}
1318 Reads and executes the commands from init file (if any) in the current
1319 working directory as long as @samp{set auto-load local-gdbinit} is set to
1320 @samp{on} (@pxref{Init File in the Current Directory}).
1321 This is only done if the current directory is
1322 different from your home directory. Thus, you can have more than one
1323 init file, one generic in your home directory, and another, specific
1324 to the program you are debugging, in the directory where you invoke
1328 If the command line specified a program to debug, or a process to
1329 attach to, or a core file, @value{GDBN} loads any auto-loaded
1330 scripts provided for the program or for its loaded shared libraries.
1331 @xref{Auto-loading}.
1333 If you wish to disable the auto-loading during startup,
1334 you must do something like the following:
1337 $ gdb -iex "set auto-load python-scripts off" myprogram
1340 Option @samp{-ex} does not work because the auto-loading is then turned
1344 Executes commands and command files specified by the @samp{-ex} and
1345 @samp{-x} options in their specified order. @xref{Command Files}, for
1346 more details about @value{GDBN} command files.
1349 Reads the command history recorded in the @dfn{history file}.
1350 @xref{Command History}, for more details about the command history and the
1351 files where @value{GDBN} records it.
1354 Init files use the same syntax as @dfn{command files} (@pxref{Command
1355 Files}) and are processed by @value{GDBN} in the same way. The init
1356 file in your home directory can set options (such as @samp{set
1357 complaints}) that affect subsequent processing of command line options
1358 and operands. Init files are not executed if you use the @samp{-nx}
1359 option (@pxref{Mode Options, ,Choosing Modes}).
1361 To display the list of init files loaded by gdb at startup, you
1362 can use @kbd{gdb --help}.
1364 @cindex init file name
1365 @cindex @file{.gdbinit}
1366 @cindex @file{gdb.ini}
1367 The @value{GDBN} init files are normally called @file{.gdbinit}.
1368 The DJGPP port of @value{GDBN} uses the name @file{gdb.ini}, due to
1369 the limitations of file names imposed by DOS filesystems. The Windows
1370 port of @value{GDBN} uses the standard name, but if it finds a
1371 @file{gdb.ini} file in your home directory, it warns you about that
1372 and suggests to rename the file to the standard name.
1376 @section Quitting @value{GDBN}
1377 @cindex exiting @value{GDBN}
1378 @cindex leaving @value{GDBN}
1381 @kindex quit @r{[}@var{expression}@r{]}
1382 @kindex q @r{(@code{quit})}
1383 @item quit @r{[}@var{expression}@r{]}
1385 To exit @value{GDBN}, use the @code{quit} command (abbreviated
1386 @code{q}), or type an end-of-file character (usually @kbd{Ctrl-d}). If you
1387 do not supply @var{expression}, @value{GDBN} will terminate normally;
1388 otherwise it will terminate using the result of @var{expression} as the
1393 An interrupt (often @kbd{Ctrl-c}) does not exit from @value{GDBN}, but rather
1394 terminates the action of any @value{GDBN} command that is in progress and
1395 returns to @value{GDBN} command level. It is safe to type the interrupt
1396 character at any time because @value{GDBN} does not allow it to take effect
1397 until a time when it is safe.
1399 If you have been using @value{GDBN} to control an attached process or
1400 device, you can release it with the @code{detach} command
1401 (@pxref{Attach, ,Debugging an Already-running Process}).
1403 @node Shell Commands
1404 @section Shell Commands
1406 If you need to execute occasional shell commands during your
1407 debugging session, there is no need to leave or suspend @value{GDBN}; you can
1408 just use the @code{shell} command.
1413 @cindex shell escape
1414 @item shell @var{command-string}
1415 @itemx !@var{command-string}
1416 Invoke a standard shell to execute @var{command-string}.
1417 Note that no space is needed between @code{!} and @var{command-string}.
1418 If it exists, the environment variable @code{SHELL} determines which
1419 shell to run. Otherwise @value{GDBN} uses the default shell
1420 (@file{/bin/sh} on Unix systems, @file{COMMAND.COM} on MS-DOS, etc.).
1423 The utility @code{make} is often needed in development environments.
1424 You do not have to use the @code{shell} command for this purpose in
1429 @cindex calling make
1430 @item make @var{make-args}
1431 Execute the @code{make} program with the specified
1432 arguments. This is equivalent to @samp{shell make @var{make-args}}.
1435 @node Logging Output
1436 @section Logging Output
1437 @cindex logging @value{GDBN} output
1438 @cindex save @value{GDBN} output to a file
1440 You may want to save the output of @value{GDBN} commands to a file.
1441 There are several commands to control @value{GDBN}'s logging.
1445 @item set logging on
1447 @item set logging off
1449 @cindex logging file name
1450 @item set logging file @var{file}
1451 Change the name of the current logfile. The default logfile is @file{gdb.txt}.
1452 @item set logging overwrite [on|off]
1453 By default, @value{GDBN} will append to the logfile. Set @code{overwrite} if
1454 you want @code{set logging on} to overwrite the logfile instead.
1455 @item set logging redirect [on|off]
1456 By default, @value{GDBN} output will go to both the terminal and the logfile.
1457 Set @code{redirect} if you want output to go only to the log file.
1458 @kindex show logging
1460 Show the current values of the logging settings.
1464 @chapter @value{GDBN} Commands
1466 You can abbreviate a @value{GDBN} command to the first few letters of the command
1467 name, if that abbreviation is unambiguous; and you can repeat certain
1468 @value{GDBN} commands by typing just @key{RET}. You can also use the @key{TAB}
1469 key to get @value{GDBN} to fill out the rest of a word in a command (or to
1470 show you the alternatives available, if there is more than one possibility).
1473 * Command Syntax:: How to give commands to @value{GDBN}
1474 * Completion:: Command completion
1475 * Help:: How to ask @value{GDBN} for help
1478 @node Command Syntax
1479 @section Command Syntax
1481 A @value{GDBN} command is a single line of input. There is no limit on
1482 how long it can be. It starts with a command name, which is followed by
1483 arguments whose meaning depends on the command name. For example, the
1484 command @code{step} accepts an argument which is the number of times to
1485 step, as in @samp{step 5}. You can also use the @code{step} command
1486 with no arguments. Some commands do not allow any arguments.
1488 @cindex abbreviation
1489 @value{GDBN} command names may always be truncated if that abbreviation is
1490 unambiguous. Other possible command abbreviations are listed in the
1491 documentation for individual commands. In some cases, even ambiguous
1492 abbreviations are allowed; for example, @code{s} is specially defined as
1493 equivalent to @code{step} even though there are other commands whose
1494 names start with @code{s}. You can test abbreviations by using them as
1495 arguments to the @code{help} command.
1497 @cindex repeating commands
1498 @kindex RET @r{(repeat last command)}
1499 A blank line as input to @value{GDBN} (typing just @key{RET}) means to
1500 repeat the previous command. Certain commands (for example, @code{run})
1501 will not repeat this way; these are commands whose unintentional
1502 repetition might cause trouble and which you are unlikely to want to
1503 repeat. User-defined commands can disable this feature; see
1504 @ref{Define, dont-repeat}.
1506 The @code{list} and @code{x} commands, when you repeat them with
1507 @key{RET}, construct new arguments rather than repeating
1508 exactly as typed. This permits easy scanning of source or memory.
1510 @value{GDBN} can also use @key{RET} in another way: to partition lengthy
1511 output, in a way similar to the common utility @code{more}
1512 (@pxref{Screen Size,,Screen Size}). Since it is easy to press one
1513 @key{RET} too many in this situation, @value{GDBN} disables command
1514 repetition after any command that generates this sort of display.
1516 @kindex # @r{(a comment)}
1518 Any text from a @kbd{#} to the end of the line is a comment; it does
1519 nothing. This is useful mainly in command files (@pxref{Command
1520 Files,,Command Files}).
1522 @cindex repeating command sequences
1523 @kindex Ctrl-o @r{(operate-and-get-next)}
1524 The @kbd{Ctrl-o} binding is useful for repeating a complex sequence of
1525 commands. This command accepts the current line, like @key{RET}, and
1526 then fetches the next line relative to the current line from the history
1530 @section Command Completion
1533 @cindex word completion
1534 @value{GDBN} can fill in the rest of a word in a command for you, if there is
1535 only one possibility; it can also show you what the valid possibilities
1536 are for the next word in a command, at any time. This works for @value{GDBN}
1537 commands, @value{GDBN} subcommands, and the names of symbols in your program.
1539 Press the @key{TAB} key whenever you want @value{GDBN} to fill out the rest
1540 of a word. If there is only one possibility, @value{GDBN} fills in the
1541 word, and waits for you to finish the command (or press @key{RET} to
1542 enter it). For example, if you type
1544 @c FIXME "@key" does not distinguish its argument sufficiently to permit
1545 @c complete accuracy in these examples; space introduced for clarity.
1546 @c If texinfo enhancements make it unnecessary, it would be nice to
1547 @c replace " @key" by "@key" in the following...
1549 (@value{GDBP}) info bre @key{TAB}
1553 @value{GDBN} fills in the rest of the word @samp{breakpoints}, since that is
1554 the only @code{info} subcommand beginning with @samp{bre}:
1557 (@value{GDBP}) info breakpoints
1561 You can either press @key{RET} at this point, to run the @code{info
1562 breakpoints} command, or backspace and enter something else, if
1563 @samp{breakpoints} does not look like the command you expected. (If you
1564 were sure you wanted @code{info breakpoints} in the first place, you
1565 might as well just type @key{RET} immediately after @samp{info bre},
1566 to exploit command abbreviations rather than command completion).
1568 If there is more than one possibility for the next word when you press
1569 @key{TAB}, @value{GDBN} sounds a bell. You can either supply more
1570 characters and try again, or just press @key{TAB} a second time;
1571 @value{GDBN} displays all the possible completions for that word. For
1572 example, you might want to set a breakpoint on a subroutine whose name
1573 begins with @samp{make_}, but when you type @kbd{b make_@key{TAB}} @value{GDBN}
1574 just sounds the bell. Typing @key{TAB} again displays all the
1575 function names in your program that begin with those characters, for
1579 (@value{GDBP}) b make_ @key{TAB}
1580 @exdent @value{GDBN} sounds bell; press @key{TAB} again, to see:
1581 make_a_section_from_file make_environ
1582 make_abs_section make_function_type
1583 make_blockvector make_pointer_type
1584 make_cleanup make_reference_type
1585 make_command make_symbol_completion_list
1586 (@value{GDBP}) b make_
1590 After displaying the available possibilities, @value{GDBN} copies your
1591 partial input (@samp{b make_} in the example) so you can finish the
1594 If you just want to see the list of alternatives in the first place, you
1595 can press @kbd{M-?} rather than pressing @key{TAB} twice. @kbd{M-?}
1596 means @kbd{@key{META} ?}. You can type this either by holding down a
1597 key designated as the @key{META} shift on your keyboard (if there is
1598 one) while typing @kbd{?}, or as @key{ESC} followed by @kbd{?}.
1600 @cindex quotes in commands
1601 @cindex completion of quoted strings
1602 Sometimes the string you need, while logically a ``word'', may contain
1603 parentheses or other characters that @value{GDBN} normally excludes from
1604 its notion of a word. To permit word completion to work in this
1605 situation, you may enclose words in @code{'} (single quote marks) in
1606 @value{GDBN} commands.
1608 The most likely situation where you might need this is in typing the
1609 name of a C@t{++} function. This is because C@t{++} allows function
1610 overloading (multiple definitions of the same function, distinguished
1611 by argument type). For example, when you want to set a breakpoint you
1612 may need to distinguish whether you mean the version of @code{name}
1613 that takes an @code{int} parameter, @code{name(int)}, or the version
1614 that takes a @code{float} parameter, @code{name(float)}. To use the
1615 word-completion facilities in this situation, type a single quote
1616 @code{'} at the beginning of the function name. This alerts
1617 @value{GDBN} that it may need to consider more information than usual
1618 when you press @key{TAB} or @kbd{M-?} to request word completion:
1621 (@value{GDBP}) b 'bubble( @kbd{M-?}
1622 bubble(double,double) bubble(int,int)
1623 (@value{GDBP}) b 'bubble(
1626 In some cases, @value{GDBN} can tell that completing a name requires using
1627 quotes. When this happens, @value{GDBN} inserts the quote for you (while
1628 completing as much as it can) if you do not type the quote in the first
1632 (@value{GDBP}) b bub @key{TAB}
1633 @exdent @value{GDBN} alters your input line to the following, and rings a bell:
1634 (@value{GDBP}) b 'bubble(
1638 In general, @value{GDBN} can tell that a quote is needed (and inserts it) if
1639 you have not yet started typing the argument list when you ask for
1640 completion on an overloaded symbol.
1642 For more information about overloaded functions, see @ref{C Plus Plus
1643 Expressions, ,C@t{++} Expressions}. You can use the command @code{set
1644 overload-resolution off} to disable overload resolution;
1645 see @ref{Debugging C Plus Plus, ,@value{GDBN} Features for C@t{++}}.
1647 @cindex completion of structure field names
1648 @cindex structure field name completion
1649 @cindex completion of union field names
1650 @cindex union field name completion
1651 When completing in an expression which looks up a field in a
1652 structure, @value{GDBN} also tries@footnote{The completer can be
1653 confused by certain kinds of invalid expressions. Also, it only
1654 examines the static type of the expression, not the dynamic type.} to
1655 limit completions to the field names available in the type of the
1659 (@value{GDBP}) p gdb_stdout.@kbd{M-?}
1660 magic to_fputs to_rewind
1661 to_data to_isatty to_write
1662 to_delete to_put to_write_async_safe
1667 This is because the @code{gdb_stdout} is a variable of the type
1668 @code{struct ui_file} that is defined in @value{GDBN} sources as
1675 ui_file_flush_ftype *to_flush;
1676 ui_file_write_ftype *to_write;
1677 ui_file_write_async_safe_ftype *to_write_async_safe;
1678 ui_file_fputs_ftype *to_fputs;
1679 ui_file_read_ftype *to_read;
1680 ui_file_delete_ftype *to_delete;
1681 ui_file_isatty_ftype *to_isatty;
1682 ui_file_rewind_ftype *to_rewind;
1683 ui_file_put_ftype *to_put;
1690 @section Getting Help
1691 @cindex online documentation
1694 You can always ask @value{GDBN} itself for information on its commands,
1695 using the command @code{help}.
1698 @kindex h @r{(@code{help})}
1701 You can use @code{help} (abbreviated @code{h}) with no arguments to
1702 display a short list of named classes of commands:
1706 List of classes of commands:
1708 aliases -- Aliases of other commands
1709 breakpoints -- Making program stop at certain points
1710 data -- Examining data
1711 files -- Specifying and examining files
1712 internals -- Maintenance commands
1713 obscure -- Obscure features
1714 running -- Running the program
1715 stack -- Examining the stack
1716 status -- Status inquiries
1717 support -- Support facilities
1718 tracepoints -- Tracing of program execution without
1719 stopping the program
1720 user-defined -- User-defined commands
1722 Type "help" followed by a class name for a list of
1723 commands in that class.
1724 Type "help" followed by command name for full
1726 Command name abbreviations are allowed if unambiguous.
1729 @c the above line break eliminates huge line overfull...
1731 @item help @var{class}
1732 Using one of the general help classes as an argument, you can get a
1733 list of the individual commands in that class. For example, here is the
1734 help display for the class @code{status}:
1737 (@value{GDBP}) help status
1742 @c Line break in "show" line falsifies real output, but needed
1743 @c to fit in smallbook page size.
1744 info -- Generic command for showing things
1745 about the program being debugged
1746 show -- Generic command for showing things
1749 Type "help" followed by command name for full
1751 Command name abbreviations are allowed if unambiguous.
1755 @item help @var{command}
1756 With a command name as @code{help} argument, @value{GDBN} displays a
1757 short paragraph on how to use that command.
1760 @item apropos @var{args}
1761 The @code{apropos} command searches through all of the @value{GDBN}
1762 commands, and their documentation, for the regular expression specified in
1763 @var{args}. It prints out all matches found. For example:
1774 alias -- Define a new command that is an alias of an existing command
1775 aliases -- Aliases of other commands
1776 d -- Delete some breakpoints or auto-display expressions
1777 del -- Delete some breakpoints or auto-display expressions
1778 delete -- Delete some breakpoints or auto-display expressions
1783 @item complete @var{args}
1784 The @code{complete @var{args}} command lists all the possible completions
1785 for the beginning of a command. Use @var{args} to specify the beginning of the
1786 command you want completed. For example:
1792 @noindent results in:
1803 @noindent This is intended for use by @sc{gnu} Emacs.
1806 In addition to @code{help}, you can use the @value{GDBN} commands @code{info}
1807 and @code{show} to inquire about the state of your program, or the state
1808 of @value{GDBN} itself. Each command supports many topics of inquiry; this
1809 manual introduces each of them in the appropriate context. The listings
1810 under @code{info} and under @code{show} in the Command, Variable, and
1811 Function Index point to all the sub-commands. @xref{Command and Variable
1817 @kindex i @r{(@code{info})}
1819 This command (abbreviated @code{i}) is for describing the state of your
1820 program. For example, you can show the arguments passed to a function
1821 with @code{info args}, list the registers currently in use with @code{info
1822 registers}, or list the breakpoints you have set with @code{info breakpoints}.
1823 You can get a complete list of the @code{info} sub-commands with
1824 @w{@code{help info}}.
1828 You can assign the result of an expression to an environment variable with
1829 @code{set}. For example, you can set the @value{GDBN} prompt to a $-sign with
1830 @code{set prompt $}.
1834 In contrast to @code{info}, @code{show} is for describing the state of
1835 @value{GDBN} itself.
1836 You can change most of the things you can @code{show}, by using the
1837 related command @code{set}; for example, you can control what number
1838 system is used for displays with @code{set radix}, or simply inquire
1839 which is currently in use with @code{show radix}.
1842 To display all the settable parameters and their current
1843 values, you can use @code{show} with no arguments; you may also use
1844 @code{info set}. Both commands produce the same display.
1845 @c FIXME: "info set" violates the rule that "info" is for state of
1846 @c FIXME...program. Ck w/ GNU: "info set" to be called something else,
1847 @c FIXME...or change desc of rule---eg "state of prog and debugging session"?
1851 Here are several miscellaneous @code{show} subcommands, all of which are
1852 exceptional in lacking corresponding @code{set} commands:
1855 @kindex show version
1856 @cindex @value{GDBN} version number
1858 Show what version of @value{GDBN} is running. You should include this
1859 information in @value{GDBN} bug-reports. If multiple versions of
1860 @value{GDBN} are in use at your site, you may need to determine which
1861 version of @value{GDBN} you are running; as @value{GDBN} evolves, new
1862 commands are introduced, and old ones may wither away. Also, many
1863 system vendors ship variant versions of @value{GDBN}, and there are
1864 variant versions of @value{GDBN} in @sc{gnu}/Linux distributions as well.
1865 The version number is the same as the one announced when you start
1868 @kindex show copying
1869 @kindex info copying
1870 @cindex display @value{GDBN} copyright
1873 Display information about permission for copying @value{GDBN}.
1875 @kindex show warranty
1876 @kindex info warranty
1878 @itemx info warranty
1879 Display the @sc{gnu} ``NO WARRANTY'' statement, or a warranty,
1880 if your version of @value{GDBN} comes with one.
1882 @kindex show configuration
1883 @item show configuration
1884 Display detailed information about the way @value{GDBN} was configured
1885 when it was built. This displays the optional arguments passed to the
1886 @file{configure} script and also configuration parameters detected
1887 automatically by @command{configure}. When reporting a @value{GDBN}
1888 bug (@pxref{GDB Bugs}), it is important to include this information in
1894 @chapter Running Programs Under @value{GDBN}
1896 When you run a program under @value{GDBN}, you must first generate
1897 debugging information when you compile it.
1899 You may start @value{GDBN} with its arguments, if any, in an environment
1900 of your choice. If you are doing native debugging, you may redirect
1901 your program's input and output, debug an already running process, or
1902 kill a child process.
1905 * Compilation:: Compiling for debugging
1906 * Starting:: Starting your program
1907 * Arguments:: Your program's arguments
1908 * Environment:: Your program's environment
1910 * Working Directory:: Your program's working directory
1911 * Input/Output:: Your program's input and output
1912 * Attach:: Debugging an already-running process
1913 * Kill Process:: Killing the child process
1915 * Inferiors and Programs:: Debugging multiple inferiors and programs
1916 * Threads:: Debugging programs with multiple threads
1917 * Forks:: Debugging forks
1918 * Checkpoint/Restart:: Setting a @emph{bookmark} to return to later
1922 @section Compiling for Debugging
1924 In order to debug a program effectively, you need to generate
1925 debugging information when you compile it. This debugging information
1926 is stored in the object file; it describes the data type of each
1927 variable or function and the correspondence between source line numbers
1928 and addresses in the executable code.
1930 To request debugging information, specify the @samp{-g} option when you run
1933 Programs that are to be shipped to your customers are compiled with
1934 optimizations, using the @samp{-O} compiler option. However, some
1935 compilers are unable to handle the @samp{-g} and @samp{-O} options
1936 together. Using those compilers, you cannot generate optimized
1937 executables containing debugging information.
1939 @value{NGCC}, the @sc{gnu} C/C@t{++} compiler, supports @samp{-g} with or
1940 without @samp{-O}, making it possible to debug optimized code. We
1941 recommend that you @emph{always} use @samp{-g} whenever you compile a
1942 program. You may think your program is correct, but there is no sense
1943 in pushing your luck. For more information, see @ref{Optimized Code}.
1945 Older versions of the @sc{gnu} C compiler permitted a variant option
1946 @w{@samp{-gg}} for debugging information. @value{GDBN} no longer supports this
1947 format; if your @sc{gnu} C compiler has this option, do not use it.
1949 @value{GDBN} knows about preprocessor macros and can show you their
1950 expansion (@pxref{Macros}). Most compilers do not include information
1951 about preprocessor macros in the debugging information if you specify
1952 the @option{-g} flag alone. Version 3.1 and later of @value{NGCC},
1953 the @sc{gnu} C compiler, provides macro information if you are using
1954 the DWARF debugging format, and specify the option @option{-g3}.
1956 @xref{Debugging Options,,Options for Debugging Your Program or GCC,
1957 gcc.info, Using the @sc{gnu} Compiler Collection (GCC)}, for more
1958 information on @value{NGCC} options affecting debug information.
1960 You will have the best debugging experience if you use the latest
1961 version of the DWARF debugging format that your compiler supports.
1962 DWARF is currently the most expressive and best supported debugging
1963 format in @value{GDBN}.
1967 @section Starting your Program
1973 @kindex r @r{(@code{run})}
1976 Use the @code{run} command to start your program under @value{GDBN}.
1977 You must first specify the program name (except on VxWorks) with an
1978 argument to @value{GDBN} (@pxref{Invocation, ,Getting In and Out of
1979 @value{GDBN}}), or by using the @code{file} or @code{exec-file} command
1980 (@pxref{Files, ,Commands to Specify Files}).
1984 If you are running your program in an execution environment that
1985 supports processes, @code{run} creates an inferior process and makes
1986 that process run your program. In some environments without processes,
1987 @code{run} jumps to the start of your program. Other targets,
1988 like @samp{remote}, are always running. If you get an error
1989 message like this one:
1992 The "remote" target does not support "run".
1993 Try "help target" or "continue".
1997 then use @code{continue} to run your program. You may need @code{load}
1998 first (@pxref{load}).
2000 The execution of a program is affected by certain information it
2001 receives from its superior. @value{GDBN} provides ways to specify this
2002 information, which you must do @emph{before} starting your program. (You
2003 can change it after starting your program, but such changes only affect
2004 your program the next time you start it.) This information may be
2005 divided into four categories:
2008 @item The @emph{arguments.}
2009 Specify the arguments to give your program as the arguments of the
2010 @code{run} command. If a shell is available on your target, the shell
2011 is used to pass the arguments, so that you may use normal conventions
2012 (such as wildcard expansion or variable substitution) in describing
2014 In Unix systems, you can control which shell is used with the
2015 @code{SHELL} environment variable. If you do not define @code{SHELL},
2016 @value{GDBN} uses the default shell (@file{/bin/sh}). You can disable
2017 use of any shell with the @code{set startup-with-shell} command (see
2020 @item The @emph{environment.}
2021 Your program normally inherits its environment from @value{GDBN}, but you can
2022 use the @value{GDBN} commands @code{set environment} and @code{unset
2023 environment} to change parts of the environment that affect
2024 your program. @xref{Environment, ,Your Program's Environment}.
2026 @item The @emph{working directory.}
2027 Your program inherits its working directory from @value{GDBN}. You can set
2028 the @value{GDBN} working directory with the @code{cd} command in @value{GDBN}.
2029 @xref{Working Directory, ,Your Program's Working Directory}.
2031 @item The @emph{standard input and output.}
2032 Your program normally uses the same device for standard input and
2033 standard output as @value{GDBN} is using. You can redirect input and output
2034 in the @code{run} command line, or you can use the @code{tty} command to
2035 set a different device for your program.
2036 @xref{Input/Output, ,Your Program's Input and Output}.
2039 @emph{Warning:} While input and output redirection work, you cannot use
2040 pipes to pass the output of the program you are debugging to another
2041 program; if you attempt this, @value{GDBN} is likely to wind up debugging the
2045 When you issue the @code{run} command, your program begins to execute
2046 immediately. @xref{Stopping, ,Stopping and Continuing}, for discussion
2047 of how to arrange for your program to stop. Once your program has
2048 stopped, you may call functions in your program, using the @code{print}
2049 or @code{call} commands. @xref{Data, ,Examining Data}.
2051 If the modification time of your symbol file has changed since the last
2052 time @value{GDBN} read its symbols, @value{GDBN} discards its symbol
2053 table, and reads it again. When it does this, @value{GDBN} tries to retain
2054 your current breakpoints.
2059 @cindex run to main procedure
2060 The name of the main procedure can vary from language to language.
2061 With C or C@t{++}, the main procedure name is always @code{main}, but
2062 other languages such as Ada do not require a specific name for their
2063 main procedure. The debugger provides a convenient way to start the
2064 execution of the program and to stop at the beginning of the main
2065 procedure, depending on the language used.
2067 The @samp{start} command does the equivalent of setting a temporary
2068 breakpoint at the beginning of the main procedure and then invoking
2069 the @samp{run} command.
2071 @cindex elaboration phase
2072 Some programs contain an @dfn{elaboration} phase where some startup code is
2073 executed before the main procedure is called. This depends on the
2074 languages used to write your program. In C@t{++}, for instance,
2075 constructors for static and global objects are executed before
2076 @code{main} is called. It is therefore possible that the debugger stops
2077 before reaching the main procedure. However, the temporary breakpoint
2078 will remain to halt execution.
2080 Specify the arguments to give to your program as arguments to the
2081 @samp{start} command. These arguments will be given verbatim to the
2082 underlying @samp{run} command. Note that the same arguments will be
2083 reused if no argument is provided during subsequent calls to
2084 @samp{start} or @samp{run}.
2086 It is sometimes necessary to debug the program during elaboration. In
2087 these cases, using the @code{start} command would stop the execution of
2088 your program too late, as the program would have already completed the
2089 elaboration phase. Under these circumstances, insert breakpoints in your
2090 elaboration code before running your program.
2092 @anchor{set exec-wrapper}
2093 @kindex set exec-wrapper
2094 @item set exec-wrapper @var{wrapper}
2095 @itemx show exec-wrapper
2096 @itemx unset exec-wrapper
2097 When @samp{exec-wrapper} is set, the specified wrapper is used to
2098 launch programs for debugging. @value{GDBN} starts your program
2099 with a shell command of the form @kbd{exec @var{wrapper}
2100 @var{program}}. Quoting is added to @var{program} and its
2101 arguments, but not to @var{wrapper}, so you should add quotes if
2102 appropriate for your shell. The wrapper runs until it executes
2103 your program, and then @value{GDBN} takes control.
2105 You can use any program that eventually calls @code{execve} with
2106 its arguments as a wrapper. Several standard Unix utilities do
2107 this, e.g.@: @code{env} and @code{nohup}. Any Unix shell script ending
2108 with @code{exec "$@@"} will also work.
2110 For example, you can use @code{env} to pass an environment variable to
2111 the debugged program, without setting the variable in your shell's
2115 (@value{GDBP}) set exec-wrapper env 'LD_PRELOAD=libtest.so'
2119 This command is available when debugging locally on most targets, excluding
2120 @sc{djgpp}, Cygwin, MS Windows, and QNX Neutrino.
2122 @kindex set startup-with-shell
2123 @item set startup-with-shell
2124 @itemx set startup-with-shell on
2125 @itemx set startup-with-shell off
2126 @itemx show set startup-with-shell
2127 On Unix systems, by default, if a shell is available on your target,
2128 @value{GDBN}) uses it to start your program. Arguments of the
2129 @code{run} command are passed to the shell, which does variable
2130 substitution, expands wildcard characters and performs redirection of
2131 I/O. In some circumstances, it may be useful to disable such use of a
2132 shell, for example, when debugging the shell itself or diagnosing
2133 startup failures such as:
2137 Starting program: ./a.out
2138 During startup program terminated with signal SIGSEGV, Segmentation fault.
2142 which indicates the shell or the wrapper specified with
2143 @samp{exec-wrapper} crashed, not your program. Most often, this is
2144 caused by something odd in your shell's non-interactive mode
2145 initialization file---such as @file{.cshrc} for C-shell,
2146 $@file{.zshenv} for the Z shell, or the file specified in the
2147 @samp{BASH_ENV} environment variable for BASH.
2149 @kindex set disable-randomization
2150 @item set disable-randomization
2151 @itemx set disable-randomization on
2152 This option (enabled by default in @value{GDBN}) will turn off the native
2153 randomization of the virtual address space of the started program. This option
2154 is useful for multiple debugging sessions to make the execution better
2155 reproducible and memory addresses reusable across debugging sessions.
2157 This feature is implemented only on certain targets, including @sc{gnu}/Linux.
2158 On @sc{gnu}/Linux you can get the same behavior using
2161 (@value{GDBP}) set exec-wrapper setarch `uname -m` -R
2164 @item set disable-randomization off
2165 Leave the behavior of the started executable unchanged. Some bugs rear their
2166 ugly heads only when the program is loaded at certain addresses. If your bug
2167 disappears when you run the program under @value{GDBN}, that might be because
2168 @value{GDBN} by default disables the address randomization on platforms, such
2169 as @sc{gnu}/Linux, which do that for stand-alone programs. Use @kbd{set
2170 disable-randomization off} to try to reproduce such elusive bugs.
2172 On targets where it is available, virtual address space randomization
2173 protects the programs against certain kinds of security attacks. In these
2174 cases the attacker needs to know the exact location of a concrete executable
2175 code. Randomizing its location makes it impossible to inject jumps misusing
2176 a code at its expected addresses.
2178 Prelinking shared libraries provides a startup performance advantage but it
2179 makes addresses in these libraries predictable for privileged processes by
2180 having just unprivileged access at the target system. Reading the shared
2181 library binary gives enough information for assembling the malicious code
2182 misusing it. Still even a prelinked shared library can get loaded at a new
2183 random address just requiring the regular relocation process during the
2184 startup. Shared libraries not already prelinked are always loaded at
2185 a randomly chosen address.
2187 Position independent executables (PIE) contain position independent code
2188 similar to the shared libraries and therefore such executables get loaded at
2189 a randomly chosen address upon startup. PIE executables always load even
2190 already prelinked shared libraries at a random address. You can build such
2191 executable using @command{gcc -fPIE -pie}.
2193 Heap (malloc storage), stack and custom mmap areas are always placed randomly
2194 (as long as the randomization is enabled).
2196 @item show disable-randomization
2197 Show the current setting of the explicit disable of the native randomization of
2198 the virtual address space of the started program.
2203 @section Your Program's Arguments
2205 @cindex arguments (to your program)
2206 The arguments to your program can be specified by the arguments of the
2208 They are passed to a shell, which expands wildcard characters and
2209 performs redirection of I/O, and thence to your program. Your
2210 @code{SHELL} environment variable (if it exists) specifies what shell
2211 @value{GDBN} uses. If you do not define @code{SHELL}, @value{GDBN} uses
2212 the default shell (@file{/bin/sh} on Unix).
2214 On non-Unix systems, the program is usually invoked directly by
2215 @value{GDBN}, which emulates I/O redirection via the appropriate system
2216 calls, and the wildcard characters are expanded by the startup code of
2217 the program, not by the shell.
2219 @code{run} with no arguments uses the same arguments used by the previous
2220 @code{run}, or those set by the @code{set args} command.
2225 Specify the arguments to be used the next time your program is run. If
2226 @code{set args} has no arguments, @code{run} executes your program
2227 with no arguments. Once you have run your program with arguments,
2228 using @code{set args} before the next @code{run} is the only way to run
2229 it again without arguments.
2233 Show the arguments to give your program when it is started.
2237 @section Your Program's Environment
2239 @cindex environment (of your program)
2240 The @dfn{environment} consists of a set of environment variables and
2241 their values. Environment variables conventionally record such things as
2242 your user name, your home directory, your terminal type, and your search
2243 path for programs to run. Usually you set up environment variables with
2244 the shell and they are inherited by all the other programs you run. When
2245 debugging, it can be useful to try running your program with a modified
2246 environment without having to start @value{GDBN} over again.
2250 @item path @var{directory}
2251 Add @var{directory} to the front of the @code{PATH} environment variable
2252 (the search path for executables) that will be passed to your program.
2253 The value of @code{PATH} used by @value{GDBN} does not change.
2254 You may specify several directory names, separated by whitespace or by a
2255 system-dependent separator character (@samp{:} on Unix, @samp{;} on
2256 MS-DOS and MS-Windows). If @var{directory} is already in the path, it
2257 is moved to the front, so it is searched sooner.
2259 You can use the string @samp{$cwd} to refer to whatever is the current
2260 working directory at the time @value{GDBN} searches the path. If you
2261 use @samp{.} instead, it refers to the directory where you executed the
2262 @code{path} command. @value{GDBN} replaces @samp{.} in the
2263 @var{directory} argument (with the current path) before adding
2264 @var{directory} to the search path.
2265 @c 'path' is explicitly nonrepeatable, but RMS points out it is silly to
2266 @c document that, since repeating it would be a no-op.
2270 Display the list of search paths for executables (the @code{PATH}
2271 environment variable).
2273 @kindex show environment
2274 @item show environment @r{[}@var{varname}@r{]}
2275 Print the value of environment variable @var{varname} to be given to
2276 your program when it starts. If you do not supply @var{varname},
2277 print the names and values of all environment variables to be given to
2278 your program. You can abbreviate @code{environment} as @code{env}.
2280 @kindex set environment
2281 @item set environment @var{varname} @r{[}=@var{value}@r{]}
2282 Set environment variable @var{varname} to @var{value}. The value
2283 changes for your program (and the shell @value{GDBN} uses to launch
2284 it), not for @value{GDBN} itself. @var{value} may be any string; the
2285 values of environment variables are just strings, and any
2286 interpretation is supplied by your program itself. The @var{value}
2287 parameter is optional; if it is eliminated, the variable is set to a
2289 @c "any string" here does not include leading, trailing
2290 @c blanks. Gnu asks: does anyone care?
2292 For example, this command:
2299 tells the debugged program, when subsequently run, that its user is named
2300 @samp{foo}. (The spaces around @samp{=} are used for clarity here; they
2301 are not actually required.)
2303 Note that on Unix systems, @value{GDBN} runs your program via a shell,
2304 which also inherits the environment set with @code{set environment}.
2305 If necessary, you can avoid that by using the @samp{env} program as a
2306 wrapper instead of using @code{set environment}. @xref{set
2307 exec-wrapper}, for an example doing just that.
2309 @kindex unset environment
2310 @item unset environment @var{varname}
2311 Remove variable @var{varname} from the environment to be passed to your
2312 program. This is different from @samp{set env @var{varname} =};
2313 @code{unset environment} removes the variable from the environment,
2314 rather than assigning it an empty value.
2317 @emph{Warning:} On Unix systems, @value{GDBN} runs your program using
2318 the shell indicated by your @code{SHELL} environment variable if it
2319 exists (or @code{/bin/sh} if not). If your @code{SHELL} variable
2320 names a shell that runs an initialization file when started
2321 non-interactively---such as @file{.cshrc} for C-shell, $@file{.zshenv}
2322 for the Z shell, or the file specified in the @samp{BASH_ENV}
2323 environment variable for BASH---any variables you set in that file
2324 affect your program. You may wish to move setting of environment
2325 variables to files that are only run when you sign on, such as
2326 @file{.login} or @file{.profile}.
2328 @node Working Directory
2329 @section Your Program's Working Directory
2331 @cindex working directory (of your program)
2332 Each time you start your program with @code{run}, it inherits its
2333 working directory from the current working directory of @value{GDBN}.
2334 The @value{GDBN} working directory is initially whatever it inherited
2335 from its parent process (typically the shell), but you can specify a new
2336 working directory in @value{GDBN} with the @code{cd} command.
2338 The @value{GDBN} working directory also serves as a default for the commands
2339 that specify files for @value{GDBN} to operate on. @xref{Files, ,Commands to
2344 @cindex change working directory
2345 @item cd @r{[}@var{directory}@r{]}
2346 Set the @value{GDBN} working directory to @var{directory}. If not
2347 given, @var{directory} uses @file{'~'}.
2351 Print the @value{GDBN} working directory.
2354 It is generally impossible to find the current working directory of
2355 the process being debugged (since a program can change its directory
2356 during its run). If you work on a system where @value{GDBN} is
2357 configured with the @file{/proc} support, you can use the @code{info
2358 proc} command (@pxref{SVR4 Process Information}) to find out the
2359 current working directory of the debuggee.
2362 @section Your Program's Input and Output
2367 By default, the program you run under @value{GDBN} does input and output to
2368 the same terminal that @value{GDBN} uses. @value{GDBN} switches the terminal
2369 to its own terminal modes to interact with you, but it records the terminal
2370 modes your program was using and switches back to them when you continue
2371 running your program.
2374 @kindex info terminal
2376 Displays information recorded by @value{GDBN} about the terminal modes your
2380 You can redirect your program's input and/or output using shell
2381 redirection with the @code{run} command. For example,
2388 starts your program, diverting its output to the file @file{outfile}.
2391 @cindex controlling terminal
2392 Another way to specify where your program should do input and output is
2393 with the @code{tty} command. This command accepts a file name as
2394 argument, and causes this file to be the default for future @code{run}
2395 commands. It also resets the controlling terminal for the child
2396 process, for future @code{run} commands. For example,
2403 directs that processes started with subsequent @code{run} commands
2404 default to do input and output on the terminal @file{/dev/ttyb} and have
2405 that as their controlling terminal.
2407 An explicit redirection in @code{run} overrides the @code{tty} command's
2408 effect on the input/output device, but not its effect on the controlling
2411 When you use the @code{tty} command or redirect input in the @code{run}
2412 command, only the input @emph{for your program} is affected. The input
2413 for @value{GDBN} still comes from your terminal. @code{tty} is an alias
2414 for @code{set inferior-tty}.
2416 @cindex inferior tty
2417 @cindex set inferior controlling terminal
2418 You can use the @code{show inferior-tty} command to tell @value{GDBN} to
2419 display the name of the terminal that will be used for future runs of your
2423 @item set inferior-tty /dev/ttyb
2424 @kindex set inferior-tty
2425 Set the tty for the program being debugged to /dev/ttyb.
2427 @item show inferior-tty
2428 @kindex show inferior-tty
2429 Show the current tty for the program being debugged.
2433 @section Debugging an Already-running Process
2438 @item attach @var{process-id}
2439 This command attaches to a running process---one that was started
2440 outside @value{GDBN}. (@code{info files} shows your active
2441 targets.) The command takes as argument a process ID. The usual way to
2442 find out the @var{process-id} of a Unix process is with the @code{ps} utility,
2443 or with the @samp{jobs -l} shell command.
2445 @code{attach} does not repeat if you press @key{RET} a second time after
2446 executing the command.
2449 To use @code{attach}, your program must be running in an environment
2450 which supports processes; for example, @code{attach} does not work for
2451 programs on bare-board targets that lack an operating system. You must
2452 also have permission to send the process a signal.
2454 When you use @code{attach}, the debugger finds the program running in
2455 the process first by looking in the current working directory, then (if
2456 the program is not found) by using the source file search path
2457 (@pxref{Source Path, ,Specifying Source Directories}). You can also use
2458 the @code{file} command to load the program. @xref{Files, ,Commands to
2461 The first thing @value{GDBN} does after arranging to debug the specified
2462 process is to stop it. You can examine and modify an attached process
2463 with all the @value{GDBN} commands that are ordinarily available when
2464 you start processes with @code{run}. You can insert breakpoints; you
2465 can step and continue; you can modify storage. If you would rather the
2466 process continue running, you may use the @code{continue} command after
2467 attaching @value{GDBN} to the process.
2472 When you have finished debugging the attached process, you can use the
2473 @code{detach} command to release it from @value{GDBN} control. Detaching
2474 the process continues its execution. After the @code{detach} command,
2475 that process and @value{GDBN} become completely independent once more, and you
2476 are ready to @code{attach} another process or start one with @code{run}.
2477 @code{detach} does not repeat if you press @key{RET} again after
2478 executing the command.
2481 If you exit @value{GDBN} while you have an attached process, you detach
2482 that process. If you use the @code{run} command, you kill that process.
2483 By default, @value{GDBN} asks for confirmation if you try to do either of these
2484 things; you can control whether or not you need to confirm by using the
2485 @code{set confirm} command (@pxref{Messages/Warnings, ,Optional Warnings and
2489 @section Killing the Child Process
2494 Kill the child process in which your program is running under @value{GDBN}.
2497 This command is useful if you wish to debug a core dump instead of a
2498 running process. @value{GDBN} ignores any core dump file while your program
2501 On some operating systems, a program cannot be executed outside @value{GDBN}
2502 while you have breakpoints set on it inside @value{GDBN}. You can use the
2503 @code{kill} command in this situation to permit running your program
2504 outside the debugger.
2506 The @code{kill} command is also useful if you wish to recompile and
2507 relink your program, since on many systems it is impossible to modify an
2508 executable file while it is running in a process. In this case, when you
2509 next type @code{run}, @value{GDBN} notices that the file has changed, and
2510 reads the symbol table again (while trying to preserve your current
2511 breakpoint settings).
2513 @node Inferiors and Programs
2514 @section Debugging Multiple Inferiors and Programs
2516 @value{GDBN} lets you run and debug multiple programs in a single
2517 session. In addition, @value{GDBN} on some systems may let you run
2518 several programs simultaneously (otherwise you have to exit from one
2519 before starting another). In the most general case, you can have
2520 multiple threads of execution in each of multiple processes, launched
2521 from multiple executables.
2524 @value{GDBN} represents the state of each program execution with an
2525 object called an @dfn{inferior}. An inferior typically corresponds to
2526 a process, but is more general and applies also to targets that do not
2527 have processes. Inferiors may be created before a process runs, and
2528 may be retained after a process exits. Inferiors have unique
2529 identifiers that are different from process ids. Usually each
2530 inferior will also have its own distinct address space, although some
2531 embedded targets may have several inferiors running in different parts
2532 of a single address space. Each inferior may in turn have multiple
2533 threads running in it.
2535 To find out what inferiors exist at any moment, use @w{@code{info
2539 @kindex info inferiors
2540 @item info inferiors
2541 Print a list of all inferiors currently being managed by @value{GDBN}.
2543 @value{GDBN} displays for each inferior (in this order):
2547 the inferior number assigned by @value{GDBN}
2550 the target system's inferior identifier
2553 the name of the executable the inferior is running.
2558 An asterisk @samp{*} preceding the @value{GDBN} inferior number
2559 indicates the current inferior.
2563 @c end table here to get a little more width for example
2566 (@value{GDBP}) info inferiors
2567 Num Description Executable
2568 2 process 2307 hello
2569 * 1 process 3401 goodbye
2572 To switch focus between inferiors, use the @code{inferior} command:
2575 @kindex inferior @var{infno}
2576 @item inferior @var{infno}
2577 Make inferior number @var{infno} the current inferior. The argument
2578 @var{infno} is the inferior number assigned by @value{GDBN}, as shown
2579 in the first field of the @samp{info inferiors} display.
2583 You can get multiple executables into a debugging session via the
2584 @code{add-inferior} and @w{@code{clone-inferior}} commands. On some
2585 systems @value{GDBN} can add inferiors to the debug session
2586 automatically by following calls to @code{fork} and @code{exec}. To
2587 remove inferiors from the debugging session use the
2588 @w{@code{remove-inferiors}} command.
2591 @kindex add-inferior
2592 @item add-inferior [ -copies @var{n} ] [ -exec @var{executable} ]
2593 Adds @var{n} inferiors to be run using @var{executable} as the
2594 executable. @var{n} defaults to 1. If no executable is specified,
2595 the inferiors begins empty, with no program. You can still assign or
2596 change the program assigned to the inferior at any time by using the
2597 @code{file} command with the executable name as its argument.
2599 @kindex clone-inferior
2600 @item clone-inferior [ -copies @var{n} ] [ @var{infno} ]
2601 Adds @var{n} inferiors ready to execute the same program as inferior
2602 @var{infno}. @var{n} defaults to 1. @var{infno} defaults to the
2603 number of the current inferior. This is a convenient command when you
2604 want to run another instance of the inferior you are debugging.
2607 (@value{GDBP}) info inferiors
2608 Num Description Executable
2609 * 1 process 29964 helloworld
2610 (@value{GDBP}) clone-inferior
2613 (@value{GDBP}) info inferiors
2614 Num Description Executable
2616 * 1 process 29964 helloworld
2619 You can now simply switch focus to inferior 2 and run it.
2621 @kindex remove-inferiors
2622 @item remove-inferiors @var{infno}@dots{}
2623 Removes the inferior or inferiors @var{infno}@dots{}. It is not
2624 possible to remove an inferior that is running with this command. For
2625 those, use the @code{kill} or @code{detach} command first.
2629 To quit debugging one of the running inferiors that is not the current
2630 inferior, you can either detach from it by using the @w{@code{detach
2631 inferior}} command (allowing it to run independently), or kill it
2632 using the @w{@code{kill inferiors}} command:
2635 @kindex detach inferiors @var{infno}@dots{}
2636 @item detach inferior @var{infno}@dots{}
2637 Detach from the inferior or inferiors identified by @value{GDBN}
2638 inferior number(s) @var{infno}@dots{}. Note that the inferior's entry
2639 still stays on the list of inferiors shown by @code{info inferiors},
2640 but its Description will show @samp{<null>}.
2642 @kindex kill inferiors @var{infno}@dots{}
2643 @item kill inferiors @var{infno}@dots{}
2644 Kill the inferior or inferiors identified by @value{GDBN} inferior
2645 number(s) @var{infno}@dots{}. Note that the inferior's entry still
2646 stays on the list of inferiors shown by @code{info inferiors}, but its
2647 Description will show @samp{<null>}.
2650 After the successful completion of a command such as @code{detach},
2651 @code{detach inferiors}, @code{kill} or @code{kill inferiors}, or after
2652 a normal process exit, the inferior is still valid and listed with
2653 @code{info inferiors}, ready to be restarted.
2656 To be notified when inferiors are started or exit under @value{GDBN}'s
2657 control use @w{@code{set print inferior-events}}:
2660 @kindex set print inferior-events
2661 @cindex print messages on inferior start and exit
2662 @item set print inferior-events
2663 @itemx set print inferior-events on
2664 @itemx set print inferior-events off
2665 The @code{set print inferior-events} command allows you to enable or
2666 disable printing of messages when @value{GDBN} notices that new
2667 inferiors have started or that inferiors have exited or have been
2668 detached. By default, these messages will not be printed.
2670 @kindex show print inferior-events
2671 @item show print inferior-events
2672 Show whether messages will be printed when @value{GDBN} detects that
2673 inferiors have started, exited or have been detached.
2676 Many commands will work the same with multiple programs as with a
2677 single program: e.g., @code{print myglobal} will simply display the
2678 value of @code{myglobal} in the current inferior.
2681 Occasionaly, when debugging @value{GDBN} itself, it may be useful to
2682 get more info about the relationship of inferiors, programs, address
2683 spaces in a debug session. You can do that with the @w{@code{maint
2684 info program-spaces}} command.
2687 @kindex maint info program-spaces
2688 @item maint info program-spaces
2689 Print a list of all program spaces currently being managed by
2692 @value{GDBN} displays for each program space (in this order):
2696 the program space number assigned by @value{GDBN}
2699 the name of the executable loaded into the program space, with e.g.,
2700 the @code{file} command.
2705 An asterisk @samp{*} preceding the @value{GDBN} program space number
2706 indicates the current program space.
2708 In addition, below each program space line, @value{GDBN} prints extra
2709 information that isn't suitable to display in tabular form. For
2710 example, the list of inferiors bound to the program space.
2713 (@value{GDBP}) maint info program-spaces
2716 Bound inferiors: ID 1 (process 21561)
2720 Here we can see that no inferior is running the program @code{hello},
2721 while @code{process 21561} is running the program @code{goodbye}. On
2722 some targets, it is possible that multiple inferiors are bound to the
2723 same program space. The most common example is that of debugging both
2724 the parent and child processes of a @code{vfork} call. For example,
2727 (@value{GDBP}) maint info program-spaces
2730 Bound inferiors: ID 2 (process 18050), ID 1 (process 18045)
2733 Here, both inferior 2 and inferior 1 are running in the same program
2734 space as a result of inferior 1 having executed a @code{vfork} call.
2738 @section Debugging Programs with Multiple Threads
2740 @cindex threads of execution
2741 @cindex multiple threads
2742 @cindex switching threads
2743 In some operating systems, such as HP-UX and Solaris, a single program
2744 may have more than one @dfn{thread} of execution. The precise semantics
2745 of threads differ from one operating system to another, but in general
2746 the threads of a single program are akin to multiple processes---except
2747 that they share one address space (that is, they can all examine and
2748 modify the same variables). On the other hand, each thread has its own
2749 registers and execution stack, and perhaps private memory.
2751 @value{GDBN} provides these facilities for debugging multi-thread
2755 @item automatic notification of new threads
2756 @item @samp{thread @var{threadno}}, a command to switch among threads
2757 @item @samp{info threads}, a command to inquire about existing threads
2758 @item @samp{thread apply [@var{threadno}] [@var{all}] @var{args}},
2759 a command to apply a command to a list of threads
2760 @item thread-specific breakpoints
2761 @item @samp{set print thread-events}, which controls printing of
2762 messages on thread start and exit.
2763 @item @samp{set libthread-db-search-path @var{path}}, which lets
2764 the user specify which @code{libthread_db} to use if the default choice
2765 isn't compatible with the program.
2769 @emph{Warning:} These facilities are not yet available on every
2770 @value{GDBN} configuration where the operating system supports threads.
2771 If your @value{GDBN} does not support threads, these commands have no
2772 effect. For example, a system without thread support shows no output
2773 from @samp{info threads}, and always rejects the @code{thread} command,
2777 (@value{GDBP}) info threads
2778 (@value{GDBP}) thread 1
2779 Thread ID 1 not known. Use the "info threads" command to
2780 see the IDs of currently known threads.
2782 @c FIXME to implementors: how hard would it be to say "sorry, this GDB
2783 @c doesn't support threads"?
2786 @cindex focus of debugging
2787 @cindex current thread
2788 The @value{GDBN} thread debugging facility allows you to observe all
2789 threads while your program runs---but whenever @value{GDBN} takes
2790 control, one thread in particular is always the focus of debugging.
2791 This thread is called the @dfn{current thread}. Debugging commands show
2792 program information from the perspective of the current thread.
2794 @cindex @code{New} @var{systag} message
2795 @cindex thread identifier (system)
2796 @c FIXME-implementors!! It would be more helpful if the [New...] message
2797 @c included GDB's numeric thread handle, so you could just go to that
2798 @c thread without first checking `info threads'.
2799 Whenever @value{GDBN} detects a new thread in your program, it displays
2800 the target system's identification for the thread with a message in the
2801 form @samp{[New @var{systag}]}. @var{systag} is a thread identifier
2802 whose form varies depending on the particular system. For example, on
2803 @sc{gnu}/Linux, you might see
2806 [New Thread 0x41e02940 (LWP 25582)]
2810 when @value{GDBN} notices a new thread. In contrast, on an SGI system,
2811 the @var{systag} is simply something like @samp{process 368}, with no
2814 @c FIXME!! (1) Does the [New...] message appear even for the very first
2815 @c thread of a program, or does it only appear for the
2816 @c second---i.e.@: when it becomes obvious we have a multithread
2818 @c (2) *Is* there necessarily a first thread always? Or do some
2819 @c multithread systems permit starting a program with multiple
2820 @c threads ab initio?
2822 @cindex thread number
2823 @cindex thread identifier (GDB)
2824 For debugging purposes, @value{GDBN} associates its own thread
2825 number---always a single integer---with each thread in your program.
2828 @kindex info threads
2829 @item info threads @r{[}@var{id}@dots{}@r{]}
2830 Display a summary of all threads currently in your program. Optional
2831 argument @var{id}@dots{} is one or more thread ids separated by spaces, and
2832 means to print information only about the specified thread or threads.
2833 @value{GDBN} displays for each thread (in this order):
2837 the thread number assigned by @value{GDBN}
2840 the target system's thread identifier (@var{systag})
2843 the thread's name, if one is known. A thread can either be named by
2844 the user (see @code{thread name}, below), or, in some cases, by the
2848 the current stack frame summary for that thread
2852 An asterisk @samp{*} to the left of the @value{GDBN} thread number
2853 indicates the current thread.
2857 @c end table here to get a little more width for example
2860 (@value{GDBP}) info threads
2862 3 process 35 thread 27 0x34e5 in sigpause ()
2863 2 process 35 thread 23 0x34e5 in sigpause ()
2864 * 1 process 35 thread 13 main (argc=1, argv=0x7ffffff8)
2868 On Solaris, you can display more information about user threads with a
2869 Solaris-specific command:
2872 @item maint info sol-threads
2873 @kindex maint info sol-threads
2874 @cindex thread info (Solaris)
2875 Display info on Solaris user threads.
2879 @kindex thread @var{threadno}
2880 @item thread @var{threadno}
2881 Make thread number @var{threadno} the current thread. The command
2882 argument @var{threadno} is the internal @value{GDBN} thread number, as
2883 shown in the first field of the @samp{info threads} display.
2884 @value{GDBN} responds by displaying the system identifier of the thread
2885 you selected, and its current stack frame summary:
2888 (@value{GDBP}) thread 2
2889 [Switching to thread 2 (Thread 0xb7fdab70 (LWP 12747))]
2890 #0 some_function (ignore=0x0) at example.c:8
2891 8 printf ("hello\n");
2895 As with the @samp{[New @dots{}]} message, the form of the text after
2896 @samp{Switching to} depends on your system's conventions for identifying
2899 @vindex $_thread@r{, convenience variable}
2900 The debugger convenience variable @samp{$_thread} contains the number
2901 of the current thread. You may find this useful in writing breakpoint
2902 conditional expressions, command scripts, and so forth. See
2903 @xref{Convenience Vars,, Convenience Variables}, for general
2904 information on convenience variables.
2906 @kindex thread apply
2907 @cindex apply command to several threads
2908 @item thread apply [@var{threadno} | all] @var{command}
2909 The @code{thread apply} command allows you to apply the named
2910 @var{command} to one or more threads. Specify the numbers of the
2911 threads that you want affected with the command argument
2912 @var{threadno}. It can be a single thread number, one of the numbers
2913 shown in the first field of the @samp{info threads} display; or it
2914 could be a range of thread numbers, as in @code{2-4}. To apply a
2915 command to all threads, type @kbd{thread apply all @var{command}}.
2918 @cindex name a thread
2919 @item thread name [@var{name}]
2920 This command assigns a name to the current thread. If no argument is
2921 given, any existing user-specified name is removed. The thread name
2922 appears in the @samp{info threads} display.
2924 On some systems, such as @sc{gnu}/Linux, @value{GDBN} is able to
2925 determine the name of the thread as given by the OS. On these
2926 systems, a name specified with @samp{thread name} will override the
2927 system-give name, and removing the user-specified name will cause
2928 @value{GDBN} to once again display the system-specified name.
2931 @cindex search for a thread
2932 @item thread find [@var{regexp}]
2933 Search for and display thread ids whose name or @var{systag}
2934 matches the supplied regular expression.
2936 As well as being the complement to the @samp{thread name} command,
2937 this command also allows you to identify a thread by its target
2938 @var{systag}. For instance, on @sc{gnu}/Linux, the target @var{systag}
2942 (@value{GDBN}) thread find 26688
2943 Thread 4 has target id 'Thread 0x41e02940 (LWP 26688)'
2944 (@value{GDBN}) info thread 4
2946 4 Thread 0x41e02940 (LWP 26688) 0x00000031ca6cd372 in select ()
2949 @kindex set print thread-events
2950 @cindex print messages on thread start and exit
2951 @item set print thread-events
2952 @itemx set print thread-events on
2953 @itemx set print thread-events off
2954 The @code{set print thread-events} command allows you to enable or
2955 disable printing of messages when @value{GDBN} notices that new threads have
2956 started or that threads have exited. By default, these messages will
2957 be printed if detection of these events is supported by the target.
2958 Note that these messages cannot be disabled on all targets.
2960 @kindex show print thread-events
2961 @item show print thread-events
2962 Show whether messages will be printed when @value{GDBN} detects that threads
2963 have started and exited.
2966 @xref{Thread Stops,,Stopping and Starting Multi-thread Programs}, for
2967 more information about how @value{GDBN} behaves when you stop and start
2968 programs with multiple threads.
2970 @xref{Set Watchpoints,,Setting Watchpoints}, for information about
2971 watchpoints in programs with multiple threads.
2973 @anchor{set libthread-db-search-path}
2975 @kindex set libthread-db-search-path
2976 @cindex search path for @code{libthread_db}
2977 @item set libthread-db-search-path @r{[}@var{path}@r{]}
2978 If this variable is set, @var{path} is a colon-separated list of
2979 directories @value{GDBN} will use to search for @code{libthread_db}.
2980 If you omit @var{path}, @samp{libthread-db-search-path} will be reset to
2981 its default value (@code{$sdir:$pdir} on @sc{gnu}/Linux and Solaris systems).
2982 Internally, the default value comes from the @code{LIBTHREAD_DB_SEARCH_PATH}
2985 On @sc{gnu}/Linux and Solaris systems, @value{GDBN} uses a ``helper''
2986 @code{libthread_db} library to obtain information about threads in the
2987 inferior process. @value{GDBN} will use @samp{libthread-db-search-path}
2988 to find @code{libthread_db}. @value{GDBN} also consults first if inferior
2989 specific thread debugging library loading is enabled
2990 by @samp{set auto-load libthread-db} (@pxref{libthread_db.so.1 file}).
2992 A special entry @samp{$sdir} for @samp{libthread-db-search-path}
2993 refers to the default system directories that are
2994 normally searched for loading shared libraries. The @samp{$sdir} entry
2995 is the only kind not needing to be enabled by @samp{set auto-load libthread-db}
2996 (@pxref{libthread_db.so.1 file}).
2998 A special entry @samp{$pdir} for @samp{libthread-db-search-path}
2999 refers to the directory from which @code{libpthread}
3000 was loaded in the inferior process.
3002 For any @code{libthread_db} library @value{GDBN} finds in above directories,
3003 @value{GDBN} attempts to initialize it with the current inferior process.
3004 If this initialization fails (which could happen because of a version
3005 mismatch between @code{libthread_db} and @code{libpthread}), @value{GDBN}
3006 will unload @code{libthread_db}, and continue with the next directory.
3007 If none of @code{libthread_db} libraries initialize successfully,
3008 @value{GDBN} will issue a warning and thread debugging will be disabled.
3010 Setting @code{libthread-db-search-path} is currently implemented
3011 only on some platforms.
3013 @kindex show libthread-db-search-path
3014 @item show libthread-db-search-path
3015 Display current libthread_db search path.
3017 @kindex set debug libthread-db
3018 @kindex show debug libthread-db
3019 @cindex debugging @code{libthread_db}
3020 @item set debug libthread-db
3021 @itemx show debug libthread-db
3022 Turns on or off display of @code{libthread_db}-related events.
3023 Use @code{1} to enable, @code{0} to disable.
3027 @section Debugging Forks
3029 @cindex fork, debugging programs which call
3030 @cindex multiple processes
3031 @cindex processes, multiple
3032 On most systems, @value{GDBN} has no special support for debugging
3033 programs which create additional processes using the @code{fork}
3034 function. When a program forks, @value{GDBN} will continue to debug the
3035 parent process and the child process will run unimpeded. If you have
3036 set a breakpoint in any code which the child then executes, the child
3037 will get a @code{SIGTRAP} signal which (unless it catches the signal)
3038 will cause it to terminate.
3040 However, if you want to debug the child process there is a workaround
3041 which isn't too painful. Put a call to @code{sleep} in the code which
3042 the child process executes after the fork. It may be useful to sleep
3043 only if a certain environment variable is set, or a certain file exists,
3044 so that the delay need not occur when you don't want to run @value{GDBN}
3045 on the child. While the child is sleeping, use the @code{ps} program to
3046 get its process ID. Then tell @value{GDBN} (a new invocation of
3047 @value{GDBN} if you are also debugging the parent process) to attach to
3048 the child process (@pxref{Attach}). From that point on you can debug
3049 the child process just like any other process which you attached to.
3051 On some systems, @value{GDBN} provides support for debugging programs that
3052 create additional processes using the @code{fork} or @code{vfork} functions.
3053 Currently, the only platforms with this feature are HP-UX (11.x and later
3054 only?) and @sc{gnu}/Linux (kernel version 2.5.60 and later).
3056 By default, when a program forks, @value{GDBN} will continue to debug
3057 the parent process and the child process will run unimpeded.
3059 If you want to follow the child process instead of the parent process,
3060 use the command @w{@code{set follow-fork-mode}}.
3063 @kindex set follow-fork-mode
3064 @item set follow-fork-mode @var{mode}
3065 Set the debugger response to a program call of @code{fork} or
3066 @code{vfork}. A call to @code{fork} or @code{vfork} creates a new
3067 process. The @var{mode} argument can be:
3071 The original process is debugged after a fork. The child process runs
3072 unimpeded. This is the default.
3075 The new process is debugged after a fork. The parent process runs
3080 @kindex show follow-fork-mode
3081 @item show follow-fork-mode
3082 Display the current debugger response to a @code{fork} or @code{vfork} call.
3085 @cindex debugging multiple processes
3086 On Linux, if you want to debug both the parent and child processes, use the
3087 command @w{@code{set detach-on-fork}}.
3090 @kindex set detach-on-fork
3091 @item set detach-on-fork @var{mode}
3092 Tells gdb whether to detach one of the processes after a fork, or
3093 retain debugger control over them both.
3097 The child process (or parent process, depending on the value of
3098 @code{follow-fork-mode}) will be detached and allowed to run
3099 independently. This is the default.
3102 Both processes will be held under the control of @value{GDBN}.
3103 One process (child or parent, depending on the value of
3104 @code{follow-fork-mode}) is debugged as usual, while the other
3109 @kindex show detach-on-fork
3110 @item show detach-on-fork
3111 Show whether detach-on-fork mode is on/off.
3114 If you choose to set @samp{detach-on-fork} mode off, then @value{GDBN}
3115 will retain control of all forked processes (including nested forks).
3116 You can list the forked processes under the control of @value{GDBN} by
3117 using the @w{@code{info inferiors}} command, and switch from one fork
3118 to another by using the @code{inferior} command (@pxref{Inferiors and
3119 Programs, ,Debugging Multiple Inferiors and Programs}).
3121 To quit debugging one of the forked processes, you can either detach
3122 from it by using the @w{@code{detach inferiors}} command (allowing it
3123 to run independently), or kill it using the @w{@code{kill inferiors}}
3124 command. @xref{Inferiors and Programs, ,Debugging Multiple Inferiors
3127 If you ask to debug a child process and a @code{vfork} is followed by an
3128 @code{exec}, @value{GDBN} executes the new target up to the first
3129 breakpoint in the new target. If you have a breakpoint set on
3130 @code{main} in your original program, the breakpoint will also be set on
3131 the child process's @code{main}.
3133 On some systems, when a child process is spawned by @code{vfork}, you
3134 cannot debug the child or parent until an @code{exec} call completes.
3136 If you issue a @code{run} command to @value{GDBN} after an @code{exec}
3137 call executes, the new target restarts. To restart the parent
3138 process, use the @code{file} command with the parent executable name
3139 as its argument. By default, after an @code{exec} call executes,
3140 @value{GDBN} discards the symbols of the previous executable image.
3141 You can change this behaviour with the @w{@code{set follow-exec-mode}}
3145 @kindex set follow-exec-mode
3146 @item set follow-exec-mode @var{mode}
3148 Set debugger response to a program call of @code{exec}. An
3149 @code{exec} call replaces the program image of a process.
3151 @code{follow-exec-mode} can be:
3155 @value{GDBN} creates a new inferior and rebinds the process to this
3156 new inferior. The program the process was running before the
3157 @code{exec} call can be restarted afterwards by restarting the
3163 (@value{GDBP}) info inferiors
3165 Id Description Executable
3168 process 12020 is executing new program: prog2
3169 Program exited normally.
3170 (@value{GDBP}) info inferiors
3171 Id Description Executable
3177 @value{GDBN} keeps the process bound to the same inferior. The new
3178 executable image replaces the previous executable loaded in the
3179 inferior. Restarting the inferior after the @code{exec} call, with
3180 e.g., the @code{run} command, restarts the executable the process was
3181 running after the @code{exec} call. This is the default mode.
3186 (@value{GDBP}) info inferiors
3187 Id Description Executable
3190 process 12020 is executing new program: prog2
3191 Program exited normally.
3192 (@value{GDBP}) info inferiors
3193 Id Description Executable
3200 You can use the @code{catch} command to make @value{GDBN} stop whenever
3201 a @code{fork}, @code{vfork}, or @code{exec} call is made. @xref{Set
3202 Catchpoints, ,Setting Catchpoints}.
3204 @node Checkpoint/Restart
3205 @section Setting a @emph{Bookmark} to Return to Later
3210 @cindex snapshot of a process
3211 @cindex rewind program state
3213 On certain operating systems@footnote{Currently, only
3214 @sc{gnu}/Linux.}, @value{GDBN} is able to save a @dfn{snapshot} of a
3215 program's state, called a @dfn{checkpoint}, and come back to it
3218 Returning to a checkpoint effectively undoes everything that has
3219 happened in the program since the @code{checkpoint} was saved. This
3220 includes changes in memory, registers, and even (within some limits)
3221 system state. Effectively, it is like going back in time to the
3222 moment when the checkpoint was saved.
3224 Thus, if you're stepping thru a program and you think you're
3225 getting close to the point where things go wrong, you can save
3226 a checkpoint. Then, if you accidentally go too far and miss
3227 the critical statement, instead of having to restart your program
3228 from the beginning, you can just go back to the checkpoint and
3229 start again from there.
3231 This can be especially useful if it takes a lot of time or
3232 steps to reach the point where you think the bug occurs.
3234 To use the @code{checkpoint}/@code{restart} method of debugging:
3239 Save a snapshot of the debugged program's current execution state.
3240 The @code{checkpoint} command takes no arguments, but each checkpoint
3241 is assigned a small integer id, similar to a breakpoint id.
3243 @kindex info checkpoints
3244 @item info checkpoints
3245 List the checkpoints that have been saved in the current debugging
3246 session. For each checkpoint, the following information will be
3253 @item Source line, or label
3256 @kindex restart @var{checkpoint-id}
3257 @item restart @var{checkpoint-id}
3258 Restore the program state that was saved as checkpoint number
3259 @var{checkpoint-id}. All program variables, registers, stack frames
3260 etc.@: will be returned to the values that they had when the checkpoint
3261 was saved. In essence, gdb will ``wind back the clock'' to the point
3262 in time when the checkpoint was saved.
3264 Note that breakpoints, @value{GDBN} variables, command history etc.
3265 are not affected by restoring a checkpoint. In general, a checkpoint
3266 only restores things that reside in the program being debugged, not in
3269 @kindex delete checkpoint @var{checkpoint-id}
3270 @item delete checkpoint @var{checkpoint-id}
3271 Delete the previously-saved checkpoint identified by @var{checkpoint-id}.
3275 Returning to a previously saved checkpoint will restore the user state
3276 of the program being debugged, plus a significant subset of the system
3277 (OS) state, including file pointers. It won't ``un-write'' data from
3278 a file, but it will rewind the file pointer to the previous location,
3279 so that the previously written data can be overwritten. For files
3280 opened in read mode, the pointer will also be restored so that the
3281 previously read data can be read again.
3283 Of course, characters that have been sent to a printer (or other
3284 external device) cannot be ``snatched back'', and characters received
3285 from eg.@: a serial device can be removed from internal program buffers,
3286 but they cannot be ``pushed back'' into the serial pipeline, ready to
3287 be received again. Similarly, the actual contents of files that have
3288 been changed cannot be restored (at this time).
3290 However, within those constraints, you actually can ``rewind'' your
3291 program to a previously saved point in time, and begin debugging it
3292 again --- and you can change the course of events so as to debug a
3293 different execution path this time.
3295 @cindex checkpoints and process id
3296 Finally, there is one bit of internal program state that will be
3297 different when you return to a checkpoint --- the program's process
3298 id. Each checkpoint will have a unique process id (or @var{pid}),
3299 and each will be different from the program's original @var{pid}.
3300 If your program has saved a local copy of its process id, this could
3301 potentially pose a problem.
3303 @subsection A Non-obvious Benefit of Using Checkpoints
3305 On some systems such as @sc{gnu}/Linux, address space randomization
3306 is performed on new processes for security reasons. This makes it
3307 difficult or impossible to set a breakpoint, or watchpoint, on an
3308 absolute address if you have to restart the program, since the
3309 absolute location of a symbol will change from one execution to the
3312 A checkpoint, however, is an @emph{identical} copy of a process.
3313 Therefore if you create a checkpoint at (eg.@:) the start of main,
3314 and simply return to that checkpoint instead of restarting the
3315 process, you can avoid the effects of address randomization and
3316 your symbols will all stay in the same place.
3319 @chapter Stopping and Continuing
3321 The principal purposes of using a debugger are so that you can stop your
3322 program before it terminates; or so that, if your program runs into
3323 trouble, you can investigate and find out why.
3325 Inside @value{GDBN}, your program may stop for any of several reasons,
3326 such as a signal, a breakpoint, or reaching a new line after a
3327 @value{GDBN} command such as @code{step}. You may then examine and
3328 change variables, set new breakpoints or remove old ones, and then
3329 continue execution. Usually, the messages shown by @value{GDBN} provide
3330 ample explanation of the status of your program---but you can also
3331 explicitly request this information at any time.
3334 @kindex info program
3336 Display information about the status of your program: whether it is
3337 running or not, what process it is, and why it stopped.
3341 * Breakpoints:: Breakpoints, watchpoints, and catchpoints
3342 * Continuing and Stepping:: Resuming execution
3343 * Skipping Over Functions and Files::
3344 Skipping over functions and files
3346 * Thread Stops:: Stopping and starting multi-thread programs
3350 @section Breakpoints, Watchpoints, and Catchpoints
3353 A @dfn{breakpoint} makes your program stop whenever a certain point in
3354 the program is reached. For each breakpoint, you can add conditions to
3355 control in finer detail whether your program stops. You can set
3356 breakpoints with the @code{break} command and its variants (@pxref{Set
3357 Breaks, ,Setting Breakpoints}), to specify the place where your program
3358 should stop by line number, function name or exact address in the
3361 On some systems, you can set breakpoints in shared libraries before
3362 the executable is run. There is a minor limitation on HP-UX systems:
3363 you must wait until the executable is run in order to set breakpoints
3364 in shared library routines that are not called directly by the program
3365 (for example, routines that are arguments in a @code{pthread_create}
3369 @cindex data breakpoints
3370 @cindex memory tracing
3371 @cindex breakpoint on memory address
3372 @cindex breakpoint on variable modification
3373 A @dfn{watchpoint} is a special breakpoint that stops your program
3374 when the value of an expression changes. The expression may be a value
3375 of a variable, or it could involve values of one or more variables
3376 combined by operators, such as @samp{a + b}. This is sometimes called
3377 @dfn{data breakpoints}. You must use a different command to set
3378 watchpoints (@pxref{Set Watchpoints, ,Setting Watchpoints}), but aside
3379 from that, you can manage a watchpoint like any other breakpoint: you
3380 enable, disable, and delete both breakpoints and watchpoints using the
3383 You can arrange to have values from your program displayed automatically
3384 whenever @value{GDBN} stops at a breakpoint. @xref{Auto Display,,
3388 @cindex breakpoint on events
3389 A @dfn{catchpoint} is another special breakpoint that stops your program
3390 when a certain kind of event occurs, such as the throwing of a C@t{++}
3391 exception or the loading of a library. As with watchpoints, you use a
3392 different command to set a catchpoint (@pxref{Set Catchpoints, ,Setting
3393 Catchpoints}), but aside from that, you can manage a catchpoint like any
3394 other breakpoint. (To stop when your program receives a signal, use the
3395 @code{handle} command; see @ref{Signals, ,Signals}.)
3397 @cindex breakpoint numbers
3398 @cindex numbers for breakpoints
3399 @value{GDBN} assigns a number to each breakpoint, watchpoint, or
3400 catchpoint when you create it; these numbers are successive integers
3401 starting with one. In many of the commands for controlling various
3402 features of breakpoints you use the breakpoint number to say which
3403 breakpoint you want to change. Each breakpoint may be @dfn{enabled} or
3404 @dfn{disabled}; if disabled, it has no effect on your program until you
3407 @cindex breakpoint ranges
3408 @cindex ranges of breakpoints
3409 Some @value{GDBN} commands accept a range of breakpoints on which to
3410 operate. A breakpoint range is either a single breakpoint number, like
3411 @samp{5}, or two such numbers, in increasing order, separated by a
3412 hyphen, like @samp{5-7}. When a breakpoint range is given to a command,
3413 all breakpoints in that range are operated on.
3416 * Set Breaks:: Setting breakpoints
3417 * Set Watchpoints:: Setting watchpoints
3418 * Set Catchpoints:: Setting catchpoints
3419 * Delete Breaks:: Deleting breakpoints
3420 * Disabling:: Disabling breakpoints
3421 * Conditions:: Break conditions
3422 * Break Commands:: Breakpoint command lists
3423 * Dynamic Printf:: Dynamic printf
3424 * Save Breakpoints:: How to save breakpoints in a file
3425 * Static Probe Points:: Listing static probe points
3426 * Error in Breakpoints:: ``Cannot insert breakpoints''
3427 * Breakpoint-related Warnings:: ``Breakpoint address adjusted...''
3431 @subsection Setting Breakpoints
3433 @c FIXME LMB what does GDB do if no code on line of breakpt?
3434 @c consider in particular declaration with/without initialization.
3436 @c FIXME 2 is there stuff on this already? break at fun start, already init?
3439 @kindex b @r{(@code{break})}
3440 @vindex $bpnum@r{, convenience variable}
3441 @cindex latest breakpoint
3442 Breakpoints are set with the @code{break} command (abbreviated
3443 @code{b}). The debugger convenience variable @samp{$bpnum} records the
3444 number of the breakpoint you've set most recently; see @ref{Convenience
3445 Vars,, Convenience Variables}, for a discussion of what you can do with
3446 convenience variables.
3449 @item break @var{location}
3450 Set a breakpoint at the given @var{location}, which can specify a
3451 function name, a line number, or an address of an instruction.
3452 (@xref{Specify Location}, for a list of all the possible ways to
3453 specify a @var{location}.) The breakpoint will stop your program just
3454 before it executes any of the code in the specified @var{location}.
3456 When using source languages that permit overloading of symbols, such as
3457 C@t{++}, a function name may refer to more than one possible place to break.
3458 @xref{Ambiguous Expressions,,Ambiguous Expressions}, for a discussion of
3461 It is also possible to insert a breakpoint that will stop the program
3462 only if a specific thread (@pxref{Thread-Specific Breakpoints})
3463 or a specific task (@pxref{Ada Tasks}) hits that breakpoint.
3466 When called without any arguments, @code{break} sets a breakpoint at
3467 the next instruction to be executed in the selected stack frame
3468 (@pxref{Stack, ,Examining the Stack}). In any selected frame but the
3469 innermost, this makes your program stop as soon as control
3470 returns to that frame. This is similar to the effect of a
3471 @code{finish} command in the frame inside the selected frame---except
3472 that @code{finish} does not leave an active breakpoint. If you use
3473 @code{break} without an argument in the innermost frame, @value{GDBN} stops
3474 the next time it reaches the current location; this may be useful
3477 @value{GDBN} normally ignores breakpoints when it resumes execution, until at
3478 least one instruction has been executed. If it did not do this, you
3479 would be unable to proceed past a breakpoint without first disabling the
3480 breakpoint. This rule applies whether or not the breakpoint already
3481 existed when your program stopped.
3483 @item break @dots{} if @var{cond}
3484 Set a breakpoint with condition @var{cond}; evaluate the expression
3485 @var{cond} each time the breakpoint is reached, and stop only if the
3486 value is nonzero---that is, if @var{cond} evaluates as true.
3487 @samp{@dots{}} stands for one of the possible arguments described
3488 above (or no argument) specifying where to break. @xref{Conditions,
3489 ,Break Conditions}, for more information on breakpoint conditions.
3492 @item tbreak @var{args}
3493 Set a breakpoint enabled only for one stop. @var{args} are the
3494 same as for the @code{break} command, and the breakpoint is set in the same
3495 way, but the breakpoint is automatically deleted after the first time your
3496 program stops there. @xref{Disabling, ,Disabling Breakpoints}.
3499 @cindex hardware breakpoints
3500 @item hbreak @var{args}
3501 Set a hardware-assisted breakpoint. @var{args} are the same as for the
3502 @code{break} command and the breakpoint is set in the same way, but the
3503 breakpoint requires hardware support and some target hardware may not
3504 have this support. The main purpose of this is EPROM/ROM code
3505 debugging, so you can set a breakpoint at an instruction without
3506 changing the instruction. This can be used with the new trap-generation
3507 provided by SPARClite DSU and most x86-based targets. These targets
3508 will generate traps when a program accesses some data or instruction
3509 address that is assigned to the debug registers. However the hardware
3510 breakpoint registers can take a limited number of breakpoints. For
3511 example, on the DSU, only two data breakpoints can be set at a time, and
3512 @value{GDBN} will reject this command if more than two are used. Delete
3513 or disable unused hardware breakpoints before setting new ones
3514 (@pxref{Disabling, ,Disabling Breakpoints}).
3515 @xref{Conditions, ,Break Conditions}.
3516 For remote targets, you can restrict the number of hardware
3517 breakpoints @value{GDBN} will use, see @ref{set remote
3518 hardware-breakpoint-limit}.
3521 @item thbreak @var{args}
3522 Set a hardware-assisted breakpoint enabled only for one stop. @var{args}
3523 are the same as for the @code{hbreak} command and the breakpoint is set in
3524 the same way. However, like the @code{tbreak} command,
3525 the breakpoint is automatically deleted after the
3526 first time your program stops there. Also, like the @code{hbreak}
3527 command, the breakpoint requires hardware support and some target hardware
3528 may not have this support. @xref{Disabling, ,Disabling Breakpoints}.
3529 See also @ref{Conditions, ,Break Conditions}.
3532 @cindex regular expression
3533 @cindex breakpoints at functions matching a regexp
3534 @cindex set breakpoints in many functions
3535 @item rbreak @var{regex}
3536 Set breakpoints on all functions matching the regular expression
3537 @var{regex}. This command sets an unconditional breakpoint on all
3538 matches, printing a list of all breakpoints it set. Once these
3539 breakpoints are set, they are treated just like the breakpoints set with
3540 the @code{break} command. You can delete them, disable them, or make
3541 them conditional the same way as any other breakpoint.
3543 The syntax of the regular expression is the standard one used with tools
3544 like @file{grep}. Note that this is different from the syntax used by
3545 shells, so for instance @code{foo*} matches all functions that include
3546 an @code{fo} followed by zero or more @code{o}s. There is an implicit
3547 @code{.*} leading and trailing the regular expression you supply, so to
3548 match only functions that begin with @code{foo}, use @code{^foo}.
3550 @cindex non-member C@t{++} functions, set breakpoint in
3551 When debugging C@t{++} programs, @code{rbreak} is useful for setting
3552 breakpoints on overloaded functions that are not members of any special
3555 @cindex set breakpoints on all functions
3556 The @code{rbreak} command can be used to set breakpoints in
3557 @strong{all} the functions in a program, like this:
3560 (@value{GDBP}) rbreak .
3563 @item rbreak @var{file}:@var{regex}
3564 If @code{rbreak} is called with a filename qualification, it limits
3565 the search for functions matching the given regular expression to the
3566 specified @var{file}. This can be used, for example, to set breakpoints on
3567 every function in a given file:
3570 (@value{GDBP}) rbreak file.c:.
3573 The colon separating the filename qualifier from the regex may
3574 optionally be surrounded by spaces.
3576 @kindex info breakpoints
3577 @cindex @code{$_} and @code{info breakpoints}
3578 @item info breakpoints @r{[}@var{n}@dots{}@r{]}
3579 @itemx info break @r{[}@var{n}@dots{}@r{]}
3580 Print a table of all breakpoints, watchpoints, and catchpoints set and
3581 not deleted. Optional argument @var{n} means print information only
3582 about the specified breakpoint(s) (or watchpoint(s) or catchpoint(s)).
3583 For each breakpoint, following columns are printed:
3586 @item Breakpoint Numbers
3588 Breakpoint, watchpoint, or catchpoint.
3590 Whether the breakpoint is marked to be disabled or deleted when hit.
3591 @item Enabled or Disabled
3592 Enabled breakpoints are marked with @samp{y}. @samp{n} marks breakpoints
3593 that are not enabled.
3595 Where the breakpoint is in your program, as a memory address. For a
3596 pending breakpoint whose address is not yet known, this field will
3597 contain @samp{<PENDING>}. Such breakpoint won't fire until a shared
3598 library that has the symbol or line referred by breakpoint is loaded.
3599 See below for details. A breakpoint with several locations will
3600 have @samp{<MULTIPLE>} in this field---see below for details.
3602 Where the breakpoint is in the source for your program, as a file and
3603 line number. For a pending breakpoint, the original string passed to
3604 the breakpoint command will be listed as it cannot be resolved until
3605 the appropriate shared library is loaded in the future.
3609 If a breakpoint is conditional, there are two evaluation modes: ``host'' and
3610 ``target''. If mode is ``host'', breakpoint condition evaluation is done by
3611 @value{GDBN} on the host's side. If it is ``target'', then the condition
3612 is evaluated by the target. The @code{info break} command shows
3613 the condition on the line following the affected breakpoint, together with
3614 its condition evaluation mode in between parentheses.
3616 Breakpoint commands, if any, are listed after that. A pending breakpoint is
3617 allowed to have a condition specified for it. The condition is not parsed for
3618 validity until a shared library is loaded that allows the pending
3619 breakpoint to resolve to a valid location.
3622 @code{info break} with a breakpoint
3623 number @var{n} as argument lists only that breakpoint. The
3624 convenience variable @code{$_} and the default examining-address for
3625 the @code{x} command are set to the address of the last breakpoint
3626 listed (@pxref{Memory, ,Examining Memory}).
3629 @code{info break} displays a count of the number of times the breakpoint
3630 has been hit. This is especially useful in conjunction with the
3631 @code{ignore} command. You can ignore a large number of breakpoint
3632 hits, look at the breakpoint info to see how many times the breakpoint
3633 was hit, and then run again, ignoring one less than that number. This
3634 will get you quickly to the last hit of that breakpoint.
3637 For a breakpoints with an enable count (xref) greater than 1,
3638 @code{info break} also displays that count.
3642 @value{GDBN} allows you to set any number of breakpoints at the same place in
3643 your program. There is nothing silly or meaningless about this. When
3644 the breakpoints are conditional, this is even useful
3645 (@pxref{Conditions, ,Break Conditions}).
3647 @cindex multiple locations, breakpoints
3648 @cindex breakpoints, multiple locations
3649 It is possible that a breakpoint corresponds to several locations
3650 in your program. Examples of this situation are:
3654 Multiple functions in the program may have the same name.
3657 For a C@t{++} constructor, the @value{NGCC} compiler generates several
3658 instances of the function body, used in different cases.
3661 For a C@t{++} template function, a given line in the function can
3662 correspond to any number of instantiations.
3665 For an inlined function, a given source line can correspond to
3666 several places where that function is inlined.
3669 In all those cases, @value{GDBN} will insert a breakpoint at all
3670 the relevant locations.
3672 A breakpoint with multiple locations is displayed in the breakpoint
3673 table using several rows---one header row, followed by one row for
3674 each breakpoint location. The header row has @samp{<MULTIPLE>} in the
3675 address column. The rows for individual locations contain the actual
3676 addresses for locations, and show the functions to which those
3677 locations belong. The number column for a location is of the form
3678 @var{breakpoint-number}.@var{location-number}.
3683 Num Type Disp Enb Address What
3684 1 breakpoint keep y <MULTIPLE>
3686 breakpoint already hit 1 time
3687 1.1 y 0x080486a2 in void foo<int>() at t.cc:8
3688 1.2 y 0x080486ca in void foo<double>() at t.cc:8
3691 Each location can be individually enabled or disabled by passing
3692 @var{breakpoint-number}.@var{location-number} as argument to the
3693 @code{enable} and @code{disable} commands. Note that you cannot
3694 delete the individual locations from the list, you can only delete the
3695 entire list of locations that belong to their parent breakpoint (with
3696 the @kbd{delete @var{num}} command, where @var{num} is the number of
3697 the parent breakpoint, 1 in the above example). Disabling or enabling
3698 the parent breakpoint (@pxref{Disabling}) affects all of the locations
3699 that belong to that breakpoint.
3701 @cindex pending breakpoints
3702 It's quite common to have a breakpoint inside a shared library.
3703 Shared libraries can be loaded and unloaded explicitly,
3704 and possibly repeatedly, as the program is executed. To support
3705 this use case, @value{GDBN} updates breakpoint locations whenever
3706 any shared library is loaded or unloaded. Typically, you would
3707 set a breakpoint in a shared library at the beginning of your
3708 debugging session, when the library is not loaded, and when the
3709 symbols from the library are not available. When you try to set
3710 breakpoint, @value{GDBN} will ask you if you want to set
3711 a so called @dfn{pending breakpoint}---breakpoint whose address
3712 is not yet resolved.
3714 After the program is run, whenever a new shared library is loaded,
3715 @value{GDBN} reevaluates all the breakpoints. When a newly loaded
3716 shared library contains the symbol or line referred to by some
3717 pending breakpoint, that breakpoint is resolved and becomes an
3718 ordinary breakpoint. When a library is unloaded, all breakpoints
3719 that refer to its symbols or source lines become pending again.
3721 This logic works for breakpoints with multiple locations, too. For
3722 example, if you have a breakpoint in a C@t{++} template function, and
3723 a newly loaded shared library has an instantiation of that template,
3724 a new location is added to the list of locations for the breakpoint.
3726 Except for having unresolved address, pending breakpoints do not
3727 differ from regular breakpoints. You can set conditions or commands,
3728 enable and disable them and perform other breakpoint operations.
3730 @value{GDBN} provides some additional commands for controlling what
3731 happens when the @samp{break} command cannot resolve breakpoint
3732 address specification to an address:
3734 @kindex set breakpoint pending
3735 @kindex show breakpoint pending
3737 @item set breakpoint pending auto
3738 This is the default behavior. When @value{GDBN} cannot find the breakpoint
3739 location, it queries you whether a pending breakpoint should be created.
3741 @item set breakpoint pending on
3742 This indicates that an unrecognized breakpoint location should automatically
3743 result in a pending breakpoint being created.
3745 @item set breakpoint pending off
3746 This indicates that pending breakpoints are not to be created. Any
3747 unrecognized breakpoint location results in an error. This setting does
3748 not affect any pending breakpoints previously created.
3750 @item show breakpoint pending
3751 Show the current behavior setting for creating pending breakpoints.
3754 The settings above only affect the @code{break} command and its
3755 variants. Once breakpoint is set, it will be automatically updated
3756 as shared libraries are loaded and unloaded.
3758 @cindex automatic hardware breakpoints
3759 For some targets, @value{GDBN} can automatically decide if hardware or
3760 software breakpoints should be used, depending on whether the
3761 breakpoint address is read-only or read-write. This applies to
3762 breakpoints set with the @code{break} command as well as to internal
3763 breakpoints set by commands like @code{next} and @code{finish}. For
3764 breakpoints set with @code{hbreak}, @value{GDBN} will always use hardware
3767 You can control this automatic behaviour with the following commands::
3769 @kindex set breakpoint auto-hw
3770 @kindex show breakpoint auto-hw
3772 @item set breakpoint auto-hw on
3773 This is the default behavior. When @value{GDBN} sets a breakpoint, it
3774 will try to use the target memory map to decide if software or hardware
3775 breakpoint must be used.
3777 @item set breakpoint auto-hw off
3778 This indicates @value{GDBN} should not automatically select breakpoint
3779 type. If the target provides a memory map, @value{GDBN} will warn when
3780 trying to set software breakpoint at a read-only address.
3783 @value{GDBN} normally implements breakpoints by replacing the program code
3784 at the breakpoint address with a special instruction, which, when
3785 executed, given control to the debugger. By default, the program
3786 code is so modified only when the program is resumed. As soon as
3787 the program stops, @value{GDBN} restores the original instructions. This
3788 behaviour guards against leaving breakpoints inserted in the
3789 target should gdb abrubptly disconnect. However, with slow remote
3790 targets, inserting and removing breakpoint can reduce the performance.
3791 This behavior can be controlled with the following commands::
3793 @kindex set breakpoint always-inserted
3794 @kindex show breakpoint always-inserted
3796 @item set breakpoint always-inserted off
3797 All breakpoints, including newly added by the user, are inserted in
3798 the target only when the target is resumed. All breakpoints are
3799 removed from the target when it stops.
3801 @item set breakpoint always-inserted on
3802 Causes all breakpoints to be inserted in the target at all times. If
3803 the user adds a new breakpoint, or changes an existing breakpoint, the
3804 breakpoints in the target are updated immediately. A breakpoint is
3805 removed from the target only when breakpoint itself is removed.
3807 @cindex non-stop mode, and @code{breakpoint always-inserted}
3808 @item set breakpoint always-inserted auto
3809 This is the default mode. If @value{GDBN} is controlling the inferior
3810 in non-stop mode (@pxref{Non-Stop Mode}), gdb behaves as if
3811 @code{breakpoint always-inserted} mode is on. If @value{GDBN} is
3812 controlling the inferior in all-stop mode, @value{GDBN} behaves as if
3813 @code{breakpoint always-inserted} mode is off.
3816 @value{GDBN} handles conditional breakpoints by evaluating these conditions
3817 when a breakpoint breaks. If the condition is true, then the process being
3818 debugged stops, otherwise the process is resumed.
3820 If the target supports evaluating conditions on its end, @value{GDBN} may
3821 download the breakpoint, together with its conditions, to it.
3823 This feature can be controlled via the following commands:
3825 @kindex set breakpoint condition-evaluation
3826 @kindex show breakpoint condition-evaluation
3828 @item set breakpoint condition-evaluation host
3829 This option commands @value{GDBN} to evaluate the breakpoint
3830 conditions on the host's side. Unconditional breakpoints are sent to
3831 the target which in turn receives the triggers and reports them back to GDB
3832 for condition evaluation. This is the standard evaluation mode.
3834 @item set breakpoint condition-evaluation target
3835 This option commands @value{GDBN} to download breakpoint conditions
3836 to the target at the moment of their insertion. The target
3837 is responsible for evaluating the conditional expression and reporting
3838 breakpoint stop events back to @value{GDBN} whenever the condition
3839 is true. Due to limitations of target-side evaluation, some conditions
3840 cannot be evaluated there, e.g., conditions that depend on local data
3841 that is only known to the host. Examples include
3842 conditional expressions involving convenience variables, complex types
3843 that cannot be handled by the agent expression parser and expressions
3844 that are too long to be sent over to the target, specially when the
3845 target is a remote system. In these cases, the conditions will be
3846 evaluated by @value{GDBN}.
3848 @item set breakpoint condition-evaluation auto
3849 This is the default mode. If the target supports evaluating breakpoint
3850 conditions on its end, @value{GDBN} will download breakpoint conditions to
3851 the target (limitations mentioned previously apply). If the target does
3852 not support breakpoint condition evaluation, then @value{GDBN} will fallback
3853 to evaluating all these conditions on the host's side.
3857 @cindex negative breakpoint numbers
3858 @cindex internal @value{GDBN} breakpoints
3859 @value{GDBN} itself sometimes sets breakpoints in your program for
3860 special purposes, such as proper handling of @code{longjmp} (in C
3861 programs). These internal breakpoints are assigned negative numbers,
3862 starting with @code{-1}; @samp{info breakpoints} does not display them.
3863 You can see these breakpoints with the @value{GDBN} maintenance command
3864 @samp{maint info breakpoints} (@pxref{maint info breakpoints}).
3867 @node Set Watchpoints
3868 @subsection Setting Watchpoints
3870 @cindex setting watchpoints
3871 You can use a watchpoint to stop execution whenever the value of an
3872 expression changes, without having to predict a particular place where
3873 this may happen. (This is sometimes called a @dfn{data breakpoint}.)
3874 The expression may be as simple as the value of a single variable, or
3875 as complex as many variables combined by operators. Examples include:
3879 A reference to the value of a single variable.
3882 An address cast to an appropriate data type. For example,
3883 @samp{*(int *)0x12345678} will watch a 4-byte region at the specified
3884 address (assuming an @code{int} occupies 4 bytes).
3887 An arbitrarily complex expression, such as @samp{a*b + c/d}. The
3888 expression can use any operators valid in the program's native
3889 language (@pxref{Languages}).
3892 You can set a watchpoint on an expression even if the expression can
3893 not be evaluated yet. For instance, you can set a watchpoint on
3894 @samp{*global_ptr} before @samp{global_ptr} is initialized.
3895 @value{GDBN} will stop when your program sets @samp{global_ptr} and
3896 the expression produces a valid value. If the expression becomes
3897 valid in some other way than changing a variable (e.g.@: if the memory
3898 pointed to by @samp{*global_ptr} becomes readable as the result of a
3899 @code{malloc} call), @value{GDBN} may not stop until the next time
3900 the expression changes.
3902 @cindex software watchpoints
3903 @cindex hardware watchpoints
3904 Depending on your system, watchpoints may be implemented in software or
3905 hardware. @value{GDBN} does software watchpointing by single-stepping your
3906 program and testing the variable's value each time, which is hundreds of
3907 times slower than normal execution. (But this may still be worth it, to
3908 catch errors where you have no clue what part of your program is the
3911 On some systems, such as HP-UX, PowerPC, @sc{gnu}/Linux and most other
3912 x86-based targets, @value{GDBN} includes support for hardware
3913 watchpoints, which do not slow down the running of your program.
3917 @item watch @r{[}-l@r{|}-location@r{]} @var{expr} @r{[}thread @var{threadnum}@r{]} @r{[}mask @var{maskvalue}@r{]}
3918 Set a watchpoint for an expression. @value{GDBN} will break when the
3919 expression @var{expr} is written into by the program and its value
3920 changes. The simplest (and the most popular) use of this command is
3921 to watch the value of a single variable:
3924 (@value{GDBP}) watch foo
3927 If the command includes a @code{@r{[}thread @var{threadnum}@r{]}}
3928 argument, @value{GDBN} breaks only when the thread identified by
3929 @var{threadnum} changes the value of @var{expr}. If any other threads
3930 change the value of @var{expr}, @value{GDBN} will not break. Note
3931 that watchpoints restricted to a single thread in this way only work
3932 with Hardware Watchpoints.
3934 Ordinarily a watchpoint respects the scope of variables in @var{expr}
3935 (see below). The @code{-location} argument tells @value{GDBN} to
3936 instead watch the memory referred to by @var{expr}. In this case,
3937 @value{GDBN} will evaluate @var{expr}, take the address of the result,
3938 and watch the memory at that address. The type of the result is used
3939 to determine the size of the watched memory. If the expression's
3940 result does not have an address, then @value{GDBN} will print an
3943 The @code{@r{[}mask @var{maskvalue}@r{]}} argument allows creation
3944 of masked watchpoints, if the current architecture supports this
3945 feature (e.g., PowerPC Embedded architecture, see @ref{PowerPC
3946 Embedded}.) A @dfn{masked watchpoint} specifies a mask in addition
3947 to an address to watch. The mask specifies that some bits of an address
3948 (the bits which are reset in the mask) should be ignored when matching
3949 the address accessed by the inferior against the watchpoint address.
3950 Thus, a masked watchpoint watches many addresses simultaneously---those
3951 addresses whose unmasked bits are identical to the unmasked bits in the
3952 watchpoint address. The @code{mask} argument implies @code{-location}.
3956 (@value{GDBP}) watch foo mask 0xffff00ff
3957 (@value{GDBP}) watch *0xdeadbeef mask 0xffffff00
3961 @item rwatch @r{[}-l@r{|}-location@r{]} @var{expr} @r{[}thread @var{threadnum}@r{]} @r{[}mask @var{maskvalue}@r{]}
3962 Set a watchpoint that will break when the value of @var{expr} is read
3966 @item awatch @r{[}-l@r{|}-location@r{]} @var{expr} @r{[}thread @var{threadnum}@r{]} @r{[}mask @var{maskvalue}@r{]}
3967 Set a watchpoint that will break when @var{expr} is either read from
3968 or written into by the program.
3970 @kindex info watchpoints @r{[}@var{n}@dots{}@r{]}
3971 @item info watchpoints @r{[}@var{n}@dots{}@r{]}
3972 This command prints a list of watchpoints, using the same format as
3973 @code{info break} (@pxref{Set Breaks}).
3976 If you watch for a change in a numerically entered address you need to
3977 dereference it, as the address itself is just a constant number which will
3978 never change. @value{GDBN} refuses to create a watchpoint that watches
3979 a never-changing value:
3982 (@value{GDBP}) watch 0x600850
3983 Cannot watch constant value 0x600850.
3984 (@value{GDBP}) watch *(int *) 0x600850
3985 Watchpoint 1: *(int *) 6293584
3988 @value{GDBN} sets a @dfn{hardware watchpoint} if possible. Hardware
3989 watchpoints execute very quickly, and the debugger reports a change in
3990 value at the exact instruction where the change occurs. If @value{GDBN}
3991 cannot set a hardware watchpoint, it sets a software watchpoint, which
3992 executes more slowly and reports the change in value at the next
3993 @emph{statement}, not the instruction, after the change occurs.
3995 @cindex use only software watchpoints
3996 You can force @value{GDBN} to use only software watchpoints with the
3997 @kbd{set can-use-hw-watchpoints 0} command. With this variable set to
3998 zero, @value{GDBN} will never try to use hardware watchpoints, even if
3999 the underlying system supports them. (Note that hardware-assisted
4000 watchpoints that were set @emph{before} setting
4001 @code{can-use-hw-watchpoints} to zero will still use the hardware
4002 mechanism of watching expression values.)
4005 @item set can-use-hw-watchpoints
4006 @kindex set can-use-hw-watchpoints
4007 Set whether or not to use hardware watchpoints.
4009 @item show can-use-hw-watchpoints
4010 @kindex show can-use-hw-watchpoints
4011 Show the current mode of using hardware watchpoints.
4014 For remote targets, you can restrict the number of hardware
4015 watchpoints @value{GDBN} will use, see @ref{set remote
4016 hardware-breakpoint-limit}.
4018 When you issue the @code{watch} command, @value{GDBN} reports
4021 Hardware watchpoint @var{num}: @var{expr}
4025 if it was able to set a hardware watchpoint.
4027 Currently, the @code{awatch} and @code{rwatch} commands can only set
4028 hardware watchpoints, because accesses to data that don't change the
4029 value of the watched expression cannot be detected without examining
4030 every instruction as it is being executed, and @value{GDBN} does not do
4031 that currently. If @value{GDBN} finds that it is unable to set a
4032 hardware breakpoint with the @code{awatch} or @code{rwatch} command, it
4033 will print a message like this:
4036 Expression cannot be implemented with read/access watchpoint.
4039 Sometimes, @value{GDBN} cannot set a hardware watchpoint because the
4040 data type of the watched expression is wider than what a hardware
4041 watchpoint on the target machine can handle. For example, some systems
4042 can only watch regions that are up to 4 bytes wide; on such systems you
4043 cannot set hardware watchpoints for an expression that yields a
4044 double-precision floating-point number (which is typically 8 bytes
4045 wide). As a work-around, it might be possible to break the large region
4046 into a series of smaller ones and watch them with separate watchpoints.
4048 If you set too many hardware watchpoints, @value{GDBN} might be unable
4049 to insert all of them when you resume the execution of your program.
4050 Since the precise number of active watchpoints is unknown until such
4051 time as the program is about to be resumed, @value{GDBN} might not be
4052 able to warn you about this when you set the watchpoints, and the
4053 warning will be printed only when the program is resumed:
4056 Hardware watchpoint @var{num}: Could not insert watchpoint
4060 If this happens, delete or disable some of the watchpoints.
4062 Watching complex expressions that reference many variables can also
4063 exhaust the resources available for hardware-assisted watchpoints.
4064 That's because @value{GDBN} needs to watch every variable in the
4065 expression with separately allocated resources.
4067 If you call a function interactively using @code{print} or @code{call},
4068 any watchpoints you have set will be inactive until @value{GDBN} reaches another
4069 kind of breakpoint or the call completes.
4071 @value{GDBN} automatically deletes watchpoints that watch local
4072 (automatic) variables, or expressions that involve such variables, when
4073 they go out of scope, that is, when the execution leaves the block in
4074 which these variables were defined. In particular, when the program
4075 being debugged terminates, @emph{all} local variables go out of scope,
4076 and so only watchpoints that watch global variables remain set. If you
4077 rerun the program, you will need to set all such watchpoints again. One
4078 way of doing that would be to set a code breakpoint at the entry to the
4079 @code{main} function and when it breaks, set all the watchpoints.
4081 @cindex watchpoints and threads
4082 @cindex threads and watchpoints
4083 In multi-threaded programs, watchpoints will detect changes to the
4084 watched expression from every thread.
4087 @emph{Warning:} In multi-threaded programs, software watchpoints
4088 have only limited usefulness. If @value{GDBN} creates a software
4089 watchpoint, it can only watch the value of an expression @emph{in a
4090 single thread}. If you are confident that the expression can only
4091 change due to the current thread's activity (and if you are also
4092 confident that no other thread can become current), then you can use
4093 software watchpoints as usual. However, @value{GDBN} may not notice
4094 when a non-current thread's activity changes the expression. (Hardware
4095 watchpoints, in contrast, watch an expression in all threads.)
4098 @xref{set remote hardware-watchpoint-limit}.
4100 @node Set Catchpoints
4101 @subsection Setting Catchpoints
4102 @cindex catchpoints, setting
4103 @cindex exception handlers
4104 @cindex event handling
4106 You can use @dfn{catchpoints} to cause the debugger to stop for certain
4107 kinds of program events, such as C@t{++} exceptions or the loading of a
4108 shared library. Use the @code{catch} command to set a catchpoint.
4112 @item catch @var{event}
4113 Stop when @var{event} occurs. @var{event} can be any of the following:
4116 @item throw @r{[}@var{regexp}@r{]}
4117 @itemx rethrow @r{[}@var{regexp}@r{]}
4118 @itemx catch @r{[}@var{regexp}@r{]}
4120 @kindex catch rethrow
4122 @cindex stop on C@t{++} exceptions
4123 The throwing, re-throwing, or catching of a C@t{++} exception.
4125 If @var{regexp} is given, then only exceptions whose type matches the
4126 regular expression will be caught.
4128 @vindex $_exception@r{, convenience variable}
4129 The convenience variable @code{$_exception} is available at an
4130 exception-related catchpoint, on some systems. This holds the
4131 exception being thrown.
4133 There are currently some limitations to C@t{++} exception handling in
4138 The support for these commands is system-dependent. Currently, only
4139 systems using the @samp{gnu-v3} C@t{++} ABI (@pxref{ABI}) are
4143 The regular expression feature and the @code{$_exception} convenience
4144 variable rely on the presence of some SDT probes in @code{libstdc++}.
4145 If these probes are not present, then these features cannot be used.
4146 These probes were first available in the GCC 4.8 release, but whether
4147 or not they are available in your GCC also depends on how it was
4151 The @code{$_exception} convenience variable is only valid at the
4152 instruction at which an exception-related catchpoint is set.
4155 When an exception-related catchpoint is hit, @value{GDBN} stops at a
4156 location in the system library which implements runtime exception
4157 support for C@t{++}, usually @code{libstdc++}. You can use @code{up}
4158 (@pxref{Selection}) to get to your code.
4161 If you call a function interactively, @value{GDBN} normally returns
4162 control to you when the function has finished executing. If the call
4163 raises an exception, however, the call may bypass the mechanism that
4164 returns control to you and cause your program either to abort or to
4165 simply continue running until it hits a breakpoint, catches a signal
4166 that @value{GDBN} is listening for, or exits. This is the case even if
4167 you set a catchpoint for the exception; catchpoints on exceptions are
4168 disabled within interactive calls. @xref{Calling}, for information on
4169 controlling this with @code{set unwind-on-terminating-exception}.
4172 You cannot raise an exception interactively.
4175 You cannot install an exception handler interactively.
4179 @kindex catch exception
4180 @cindex Ada exception catching
4181 @cindex catch Ada exceptions
4182 An Ada exception being raised. If an exception name is specified
4183 at the end of the command (eg @code{catch exception Program_Error}),
4184 the debugger will stop only when this specific exception is raised.
4185 Otherwise, the debugger stops execution when any Ada exception is raised.
4187 When inserting an exception catchpoint on a user-defined exception whose
4188 name is identical to one of the exceptions defined by the language, the
4189 fully qualified name must be used as the exception name. Otherwise,
4190 @value{GDBN} will assume that it should stop on the pre-defined exception
4191 rather than the user-defined one. For instance, assuming an exception
4192 called @code{Constraint_Error} is defined in package @code{Pck}, then
4193 the command to use to catch such exceptions is @kbd{catch exception
4194 Pck.Constraint_Error}.
4196 @item exception unhandled
4197 @kindex catch exception unhandled
4198 An exception that was raised but is not handled by the program.
4201 @kindex catch assert
4202 A failed Ada assertion.
4206 @cindex break on fork/exec
4207 A call to @code{exec}. This is currently only available for HP-UX
4211 @itemx syscall @r{[}@var{name} @r{|} @var{number}@r{]} @dots{}
4212 @kindex catch syscall
4213 @cindex break on a system call.
4214 A call to or return from a system call, a.k.a.@: @dfn{syscall}. A
4215 syscall is a mechanism for application programs to request a service
4216 from the operating system (OS) or one of the OS system services.
4217 @value{GDBN} can catch some or all of the syscalls issued by the
4218 debuggee, and show the related information for each syscall. If no
4219 argument is specified, calls to and returns from all system calls
4222 @var{name} can be any system call name that is valid for the
4223 underlying OS. Just what syscalls are valid depends on the OS. On
4224 GNU and Unix systems, you can find the full list of valid syscall
4225 names on @file{/usr/include/asm/unistd.h}.
4227 @c For MS-Windows, the syscall names and the corresponding numbers
4228 @c can be found, e.g., on this URL:
4229 @c http://www.metasploit.com/users/opcode/syscalls.html
4230 @c but we don't support Windows syscalls yet.
4232 Normally, @value{GDBN} knows in advance which syscalls are valid for
4233 each OS, so you can use the @value{GDBN} command-line completion
4234 facilities (@pxref{Completion,, command completion}) to list the
4237 You may also specify the system call numerically. A syscall's
4238 number is the value passed to the OS's syscall dispatcher to
4239 identify the requested service. When you specify the syscall by its
4240 name, @value{GDBN} uses its database of syscalls to convert the name
4241 into the corresponding numeric code, but using the number directly
4242 may be useful if @value{GDBN}'s database does not have the complete
4243 list of syscalls on your system (e.g., because @value{GDBN} lags
4244 behind the OS upgrades).
4246 The example below illustrates how this command works if you don't provide
4250 (@value{GDBP}) catch syscall
4251 Catchpoint 1 (syscall)
4253 Starting program: /tmp/catch-syscall
4255 Catchpoint 1 (call to syscall 'close'), \
4256 0xffffe424 in __kernel_vsyscall ()
4260 Catchpoint 1 (returned from syscall 'close'), \
4261 0xffffe424 in __kernel_vsyscall ()
4265 Here is an example of catching a system call by name:
4268 (@value{GDBP}) catch syscall chroot
4269 Catchpoint 1 (syscall 'chroot' [61])
4271 Starting program: /tmp/catch-syscall
4273 Catchpoint 1 (call to syscall 'chroot'), \
4274 0xffffe424 in __kernel_vsyscall ()
4278 Catchpoint 1 (returned from syscall 'chroot'), \
4279 0xffffe424 in __kernel_vsyscall ()
4283 An example of specifying a system call numerically. In the case
4284 below, the syscall number has a corresponding entry in the XML
4285 file, so @value{GDBN} finds its name and prints it:
4288 (@value{GDBP}) catch syscall 252
4289 Catchpoint 1 (syscall(s) 'exit_group')
4291 Starting program: /tmp/catch-syscall
4293 Catchpoint 1 (call to syscall 'exit_group'), \
4294 0xffffe424 in __kernel_vsyscall ()
4298 Program exited normally.
4302 However, there can be situations when there is no corresponding name
4303 in XML file for that syscall number. In this case, @value{GDBN} prints
4304 a warning message saying that it was not able to find the syscall name,
4305 but the catchpoint will be set anyway. See the example below:
4308 (@value{GDBP}) catch syscall 764
4309 warning: The number '764' does not represent a known syscall.
4310 Catchpoint 2 (syscall 764)
4314 If you configure @value{GDBN} using the @samp{--without-expat} option,
4315 it will not be able to display syscall names. Also, if your
4316 architecture does not have an XML file describing its system calls,
4317 you will not be able to see the syscall names. It is important to
4318 notice that these two features are used for accessing the syscall
4319 name database. In either case, you will see a warning like this:
4322 (@value{GDBP}) catch syscall
4323 warning: Could not open "syscalls/i386-linux.xml"
4324 warning: Could not load the syscall XML file 'syscalls/i386-linux.xml'.
4325 GDB will not be able to display syscall names.
4326 Catchpoint 1 (syscall)
4330 Of course, the file name will change depending on your architecture and system.
4332 Still using the example above, you can also try to catch a syscall by its
4333 number. In this case, you would see something like:
4336 (@value{GDBP}) catch syscall 252
4337 Catchpoint 1 (syscall(s) 252)
4340 Again, in this case @value{GDBN} would not be able to display syscall's names.
4344 A call to @code{fork}. This is currently only available for HP-UX
4349 A call to @code{vfork}. This is currently only available for HP-UX
4352 @item load @r{[}regexp@r{]}
4353 @itemx unload @r{[}regexp@r{]}
4355 @kindex catch unload
4356 The loading or unloading of a shared library. If @var{regexp} is
4357 given, then the catchpoint will stop only if the regular expression
4358 matches one of the affected libraries.
4360 @item signal @r{[}@var{signal}@dots{} @r{|} @samp{all}@r{]}
4361 @kindex catch signal
4362 The delivery of a signal.
4364 With no arguments, this catchpoint will catch any signal that is not
4365 used internally by @value{GDBN}, specifically, all signals except
4366 @samp{SIGTRAP} and @samp{SIGINT}.
4368 With the argument @samp{all}, all signals, including those used by
4369 @value{GDBN}, will be caught. This argument cannot be used with other
4372 Otherwise, the arguments are a list of signal names as given to
4373 @code{handle} (@pxref{Signals}). Only signals specified in this list
4376 One reason that @code{catch signal} can be more useful than
4377 @code{handle} is that you can attach commands and conditions to the
4380 When a signal is caught by a catchpoint, the signal's @code{stop} and
4381 @code{print} settings, as specified by @code{handle}, are ignored.
4382 However, whether the signal is still delivered to the inferior depends
4383 on the @code{pass} setting; this can be changed in the catchpoint's
4388 @item tcatch @var{event}
4390 Set a catchpoint that is enabled only for one stop. The catchpoint is
4391 automatically deleted after the first time the event is caught.
4395 Use the @code{info break} command to list the current catchpoints.
4399 @subsection Deleting Breakpoints
4401 @cindex clearing breakpoints, watchpoints, catchpoints
4402 @cindex deleting breakpoints, watchpoints, catchpoints
4403 It is often necessary to eliminate a breakpoint, watchpoint, or
4404 catchpoint once it has done its job and you no longer want your program
4405 to stop there. This is called @dfn{deleting} the breakpoint. A
4406 breakpoint that has been deleted no longer exists; it is forgotten.
4408 With the @code{clear} command you can delete breakpoints according to
4409 where they are in your program. With the @code{delete} command you can
4410 delete individual breakpoints, watchpoints, or catchpoints by specifying
4411 their breakpoint numbers.
4413 It is not necessary to delete a breakpoint to proceed past it. @value{GDBN}
4414 automatically ignores breakpoints on the first instruction to be executed
4415 when you continue execution without changing the execution address.
4420 Delete any breakpoints at the next instruction to be executed in the
4421 selected stack frame (@pxref{Selection, ,Selecting a Frame}). When
4422 the innermost frame is selected, this is a good way to delete a
4423 breakpoint where your program just stopped.
4425 @item clear @var{location}
4426 Delete any breakpoints set at the specified @var{location}.
4427 @xref{Specify Location}, for the various forms of @var{location}; the
4428 most useful ones are listed below:
4431 @item clear @var{function}
4432 @itemx clear @var{filename}:@var{function}
4433 Delete any breakpoints set at entry to the named @var{function}.
4435 @item clear @var{linenum}
4436 @itemx clear @var{filename}:@var{linenum}
4437 Delete any breakpoints set at or within the code of the specified
4438 @var{linenum} of the specified @var{filename}.
4441 @cindex delete breakpoints
4443 @kindex d @r{(@code{delete})}
4444 @item delete @r{[}breakpoints@r{]} @r{[}@var{range}@dots{}@r{]}
4445 Delete the breakpoints, watchpoints, or catchpoints of the breakpoint
4446 ranges specified as arguments. If no argument is specified, delete all
4447 breakpoints (@value{GDBN} asks confirmation, unless you have @code{set
4448 confirm off}). You can abbreviate this command as @code{d}.
4452 @subsection Disabling Breakpoints
4454 @cindex enable/disable a breakpoint
4455 Rather than deleting a breakpoint, watchpoint, or catchpoint, you might
4456 prefer to @dfn{disable} it. This makes the breakpoint inoperative as if
4457 it had been deleted, but remembers the information on the breakpoint so
4458 that you can @dfn{enable} it again later.
4460 You disable and enable breakpoints, watchpoints, and catchpoints with
4461 the @code{enable} and @code{disable} commands, optionally specifying
4462 one or more breakpoint numbers as arguments. Use @code{info break} to
4463 print a list of all breakpoints, watchpoints, and catchpoints if you
4464 do not know which numbers to use.
4466 Disabling and enabling a breakpoint that has multiple locations
4467 affects all of its locations.
4469 A breakpoint, watchpoint, or catchpoint can have any of several
4470 different states of enablement:
4474 Enabled. The breakpoint stops your program. A breakpoint set
4475 with the @code{break} command starts out in this state.
4477 Disabled. The breakpoint has no effect on your program.
4479 Enabled once. The breakpoint stops your program, but then becomes
4482 Enabled for a count. The breakpoint stops your program for the next
4483 N times, then becomes disabled.
4485 Enabled for deletion. The breakpoint stops your program, but
4486 immediately after it does so it is deleted permanently. A breakpoint
4487 set with the @code{tbreak} command starts out in this state.
4490 You can use the following commands to enable or disable breakpoints,
4491 watchpoints, and catchpoints:
4495 @kindex dis @r{(@code{disable})}
4496 @item disable @r{[}breakpoints@r{]} @r{[}@var{range}@dots{}@r{]}
4497 Disable the specified breakpoints---or all breakpoints, if none are
4498 listed. A disabled breakpoint has no effect but is not forgotten. All
4499 options such as ignore-counts, conditions and commands are remembered in
4500 case the breakpoint is enabled again later. You may abbreviate
4501 @code{disable} as @code{dis}.
4504 @item enable @r{[}breakpoints@r{]} @r{[}@var{range}@dots{}@r{]}
4505 Enable the specified breakpoints (or all defined breakpoints). They
4506 become effective once again in stopping your program.
4508 @item enable @r{[}breakpoints@r{]} once @var{range}@dots{}
4509 Enable the specified breakpoints temporarily. @value{GDBN} disables any
4510 of these breakpoints immediately after stopping your program.
4512 @item enable @r{[}breakpoints@r{]} count @var{count} @var{range}@dots{}
4513 Enable the specified breakpoints temporarily. @value{GDBN} records
4514 @var{count} with each of the specified breakpoints, and decrements a
4515 breakpoint's count when it is hit. When any count reaches 0,
4516 @value{GDBN} disables that breakpoint. If a breakpoint has an ignore
4517 count (@pxref{Conditions, ,Break Conditions}), that will be
4518 decremented to 0 before @var{count} is affected.
4520 @item enable @r{[}breakpoints@r{]} delete @var{range}@dots{}
4521 Enable the specified breakpoints to work once, then die. @value{GDBN}
4522 deletes any of these breakpoints as soon as your program stops there.
4523 Breakpoints set by the @code{tbreak} command start out in this state.
4526 @c FIXME: I think the following ``Except for [...] @code{tbreak}'' is
4527 @c confusing: tbreak is also initially enabled.
4528 Except for a breakpoint set with @code{tbreak} (@pxref{Set Breaks,
4529 ,Setting Breakpoints}), breakpoints that you set are initially enabled;
4530 subsequently, they become disabled or enabled only when you use one of
4531 the commands above. (The command @code{until} can set and delete a
4532 breakpoint of its own, but it does not change the state of your other
4533 breakpoints; see @ref{Continuing and Stepping, ,Continuing and
4537 @subsection Break Conditions
4538 @cindex conditional breakpoints
4539 @cindex breakpoint conditions
4541 @c FIXME what is scope of break condition expr? Context where wanted?
4542 @c in particular for a watchpoint?
4543 The simplest sort of breakpoint breaks every time your program reaches a
4544 specified place. You can also specify a @dfn{condition} for a
4545 breakpoint. A condition is just a Boolean expression in your
4546 programming language (@pxref{Expressions, ,Expressions}). A breakpoint with
4547 a condition evaluates the expression each time your program reaches it,
4548 and your program stops only if the condition is @emph{true}.
4550 This is the converse of using assertions for program validation; in that
4551 situation, you want to stop when the assertion is violated---that is,
4552 when the condition is false. In C, if you want to test an assertion expressed
4553 by the condition @var{assert}, you should set the condition
4554 @samp{! @var{assert}} on the appropriate breakpoint.
4556 Conditions are also accepted for watchpoints; you may not need them,
4557 since a watchpoint is inspecting the value of an expression anyhow---but
4558 it might be simpler, say, to just set a watchpoint on a variable name,
4559 and specify a condition that tests whether the new value is an interesting
4562 Break conditions can have side effects, and may even call functions in
4563 your program. This can be useful, for example, to activate functions
4564 that log program progress, or to use your own print functions to
4565 format special data structures. The effects are completely predictable
4566 unless there is another enabled breakpoint at the same address. (In
4567 that case, @value{GDBN} might see the other breakpoint first and stop your
4568 program without checking the condition of this one.) Note that
4569 breakpoint commands are usually more convenient and flexible than break
4571 purpose of performing side effects when a breakpoint is reached
4572 (@pxref{Break Commands, ,Breakpoint Command Lists}).
4574 Breakpoint conditions can also be evaluated on the target's side if
4575 the target supports it. Instead of evaluating the conditions locally,
4576 @value{GDBN} encodes the expression into an agent expression
4577 (@pxref{Agent Expressions}) suitable for execution on the target,
4578 independently of @value{GDBN}. Global variables become raw memory
4579 locations, locals become stack accesses, and so forth.
4581 In this case, @value{GDBN} will only be notified of a breakpoint trigger
4582 when its condition evaluates to true. This mechanism may provide faster
4583 response times depending on the performance characteristics of the target
4584 since it does not need to keep @value{GDBN} informed about
4585 every breakpoint trigger, even those with false conditions.
4587 Break conditions can be specified when a breakpoint is set, by using
4588 @samp{if} in the arguments to the @code{break} command. @xref{Set
4589 Breaks, ,Setting Breakpoints}. They can also be changed at any time
4590 with the @code{condition} command.
4592 You can also use the @code{if} keyword with the @code{watch} command.
4593 The @code{catch} command does not recognize the @code{if} keyword;
4594 @code{condition} is the only way to impose a further condition on a
4599 @item condition @var{bnum} @var{expression}
4600 Specify @var{expression} as the break condition for breakpoint,
4601 watchpoint, or catchpoint number @var{bnum}. After you set a condition,
4602 breakpoint @var{bnum} stops your program only if the value of
4603 @var{expression} is true (nonzero, in C). When you use
4604 @code{condition}, @value{GDBN} checks @var{expression} immediately for
4605 syntactic correctness, and to determine whether symbols in it have
4606 referents in the context of your breakpoint. If @var{expression} uses
4607 symbols not referenced in the context of the breakpoint, @value{GDBN}
4608 prints an error message:
4611 No symbol "foo" in current context.
4616 not actually evaluate @var{expression} at the time the @code{condition}
4617 command (or a command that sets a breakpoint with a condition, like
4618 @code{break if @dots{}}) is given, however. @xref{Expressions, ,Expressions}.
4620 @item condition @var{bnum}
4621 Remove the condition from breakpoint number @var{bnum}. It becomes
4622 an ordinary unconditional breakpoint.
4625 @cindex ignore count (of breakpoint)
4626 A special case of a breakpoint condition is to stop only when the
4627 breakpoint has been reached a certain number of times. This is so
4628 useful that there is a special way to do it, using the @dfn{ignore
4629 count} of the breakpoint. Every breakpoint has an ignore count, which
4630 is an integer. Most of the time, the ignore count is zero, and
4631 therefore has no effect. But if your program reaches a breakpoint whose
4632 ignore count is positive, then instead of stopping, it just decrements
4633 the ignore count by one and continues. As a result, if the ignore count
4634 value is @var{n}, the breakpoint does not stop the next @var{n} times
4635 your program reaches it.
4639 @item ignore @var{bnum} @var{count}
4640 Set the ignore count of breakpoint number @var{bnum} to @var{count}.
4641 The next @var{count} times the breakpoint is reached, your program's
4642 execution does not stop; other than to decrement the ignore count, @value{GDBN}
4645 To make the breakpoint stop the next time it is reached, specify
4648 When you use @code{continue} to resume execution of your program from a
4649 breakpoint, you can specify an ignore count directly as an argument to
4650 @code{continue}, rather than using @code{ignore}. @xref{Continuing and
4651 Stepping,,Continuing and Stepping}.
4653 If a breakpoint has a positive ignore count and a condition, the
4654 condition is not checked. Once the ignore count reaches zero,
4655 @value{GDBN} resumes checking the condition.
4657 You could achieve the effect of the ignore count with a condition such
4658 as @w{@samp{$foo-- <= 0}} using a debugger convenience variable that
4659 is decremented each time. @xref{Convenience Vars, ,Convenience
4663 Ignore counts apply to breakpoints, watchpoints, and catchpoints.
4666 @node Break Commands
4667 @subsection Breakpoint Command Lists
4669 @cindex breakpoint commands
4670 You can give any breakpoint (or watchpoint or catchpoint) a series of
4671 commands to execute when your program stops due to that breakpoint. For
4672 example, you might want to print the values of certain expressions, or
4673 enable other breakpoints.
4677 @kindex end@r{ (breakpoint commands)}
4678 @item commands @r{[}@var{range}@dots{}@r{]}
4679 @itemx @dots{} @var{command-list} @dots{}
4681 Specify a list of commands for the given breakpoints. The commands
4682 themselves appear on the following lines. Type a line containing just
4683 @code{end} to terminate the commands.
4685 To remove all commands from a breakpoint, type @code{commands} and
4686 follow it immediately with @code{end}; that is, give no commands.
4688 With no argument, @code{commands} refers to the last breakpoint,
4689 watchpoint, or catchpoint set (not to the breakpoint most recently
4690 encountered). If the most recent breakpoints were set with a single
4691 command, then the @code{commands} will apply to all the breakpoints
4692 set by that command. This applies to breakpoints set by
4693 @code{rbreak}, and also applies when a single @code{break} command
4694 creates multiple breakpoints (@pxref{Ambiguous Expressions,,Ambiguous
4698 Pressing @key{RET} as a means of repeating the last @value{GDBN} command is
4699 disabled within a @var{command-list}.
4701 You can use breakpoint commands to start your program up again. Simply
4702 use the @code{continue} command, or @code{step}, or any other command
4703 that resumes execution.
4705 Any other commands in the command list, after a command that resumes
4706 execution, are ignored. This is because any time you resume execution
4707 (even with a simple @code{next} or @code{step}), you may encounter
4708 another breakpoint---which could have its own command list, leading to
4709 ambiguities about which list to execute.
4712 If the first command you specify in a command list is @code{silent}, the
4713 usual message about stopping at a breakpoint is not printed. This may
4714 be desirable for breakpoints that are to print a specific message and
4715 then continue. If none of the remaining commands print anything, you
4716 see no sign that the breakpoint was reached. @code{silent} is
4717 meaningful only at the beginning of a breakpoint command list.
4719 The commands @code{echo}, @code{output}, and @code{printf} allow you to
4720 print precisely controlled output, and are often useful in silent
4721 breakpoints. @xref{Output, ,Commands for Controlled Output}.
4723 For example, here is how you could use breakpoint commands to print the
4724 value of @code{x} at entry to @code{foo} whenever @code{x} is positive.
4730 printf "x is %d\n",x
4735 One application for breakpoint commands is to compensate for one bug so
4736 you can test for another. Put a breakpoint just after the erroneous line
4737 of code, give it a condition to detect the case in which something
4738 erroneous has been done, and give it commands to assign correct values
4739 to any variables that need them. End with the @code{continue} command
4740 so that your program does not stop, and start with the @code{silent}
4741 command so that no output is produced. Here is an example:
4752 @node Dynamic Printf
4753 @subsection Dynamic Printf
4755 @cindex dynamic printf
4757 The dynamic printf command @code{dprintf} combines a breakpoint with
4758 formatted printing of your program's data to give you the effect of
4759 inserting @code{printf} calls into your program on-the-fly, without
4760 having to recompile it.
4762 In its most basic form, the output goes to the GDB console. However,
4763 you can set the variable @code{dprintf-style} for alternate handling.
4764 For instance, you can ask to format the output by calling your
4765 program's @code{printf} function. This has the advantage that the
4766 characters go to the program's output device, so they can recorded in
4767 redirects to files and so forth.
4769 If you are doing remote debugging with a stub or agent, you can also
4770 ask to have the printf handled by the remote agent. In addition to
4771 ensuring that the output goes to the remote program's device along
4772 with any other output the program might produce, you can also ask that
4773 the dprintf remain active even after disconnecting from the remote
4774 target. Using the stub/agent is also more efficient, as it can do
4775 everything without needing to communicate with @value{GDBN}.
4779 @item dprintf @var{location},@var{template},@var{expression}[,@var{expression}@dots{}]
4780 Whenever execution reaches @var{location}, print the values of one or
4781 more @var{expressions} under the control of the string @var{template}.
4782 To print several values, separate them with commas.
4784 @item set dprintf-style @var{style}
4785 Set the dprintf output to be handled in one of several different
4786 styles enumerated below. A change of style affects all existing
4787 dynamic printfs immediately. (If you need individual control over the
4788 print commands, simply define normal breakpoints with
4789 explicitly-supplied command lists.)
4792 @kindex dprintf-style gdb
4793 Handle the output using the @value{GDBN} @code{printf} command.
4796 @kindex dprintf-style call
4797 Handle the output by calling a function in your program (normally
4801 @kindex dprintf-style agent
4802 Have the remote debugging agent (such as @code{gdbserver}) handle
4803 the output itself. This style is only available for agents that
4804 support running commands on the target.
4806 @item set dprintf-function @var{function}
4807 Set the function to call if the dprintf style is @code{call}. By
4808 default its value is @code{printf}. You may set it to any expression.
4809 that @value{GDBN} can evaluate to a function, as per the @code{call}
4812 @item set dprintf-channel @var{channel}
4813 Set a ``channel'' for dprintf. If set to a non-empty value,
4814 @value{GDBN} will evaluate it as an expression and pass the result as
4815 a first argument to the @code{dprintf-function}, in the manner of
4816 @code{fprintf} and similar functions. Otherwise, the dprintf format
4817 string will be the first argument, in the manner of @code{printf}.
4819 As an example, if you wanted @code{dprintf} output to go to a logfile
4820 that is a standard I/O stream assigned to the variable @code{mylog},
4821 you could do the following:
4824 (gdb) set dprintf-style call
4825 (gdb) set dprintf-function fprintf
4826 (gdb) set dprintf-channel mylog
4827 (gdb) dprintf 25,"at line 25, glob=%d\n",glob
4828 Dprintf 1 at 0x123456: file main.c, line 25.
4830 1 dprintf keep y 0x00123456 in main at main.c:25
4831 call (void) fprintf (mylog,"at line 25, glob=%d\n",glob)
4836 Note that the @code{info break} displays the dynamic printf commands
4837 as normal breakpoint commands; you can thus easily see the effect of
4838 the variable settings.
4840 @item set disconnected-dprintf on
4841 @itemx set disconnected-dprintf off
4842 @kindex set disconnected-dprintf
4843 Choose whether @code{dprintf} commands should continue to run if
4844 @value{GDBN} has disconnected from the target. This only applies
4845 if the @code{dprintf-style} is @code{agent}.
4847 @item show disconnected-dprintf off
4848 @kindex show disconnected-dprintf
4849 Show the current choice for disconnected @code{dprintf}.
4853 @value{GDBN} does not check the validity of function and channel,
4854 relying on you to supply values that are meaningful for the contexts
4855 in which they are being used. For instance, the function and channel
4856 may be the values of local variables, but if that is the case, then
4857 all enabled dynamic prints must be at locations within the scope of
4858 those locals. If evaluation fails, @value{GDBN} will report an error.
4860 @node Save Breakpoints
4861 @subsection How to save breakpoints to a file
4863 To save breakpoint definitions to a file use the @w{@code{save
4864 breakpoints}} command.
4867 @kindex save breakpoints
4868 @cindex save breakpoints to a file for future sessions
4869 @item save breakpoints [@var{filename}]
4870 This command saves all current breakpoint definitions together with
4871 their commands and ignore counts, into a file @file{@var{filename}}
4872 suitable for use in a later debugging session. This includes all
4873 types of breakpoints (breakpoints, watchpoints, catchpoints,
4874 tracepoints). To read the saved breakpoint definitions, use the
4875 @code{source} command (@pxref{Command Files}). Note that watchpoints
4876 with expressions involving local variables may fail to be recreated
4877 because it may not be possible to access the context where the
4878 watchpoint is valid anymore. Because the saved breakpoint definitions
4879 are simply a sequence of @value{GDBN} commands that recreate the
4880 breakpoints, you can edit the file in your favorite editing program,
4881 and remove the breakpoint definitions you're not interested in, or
4882 that can no longer be recreated.
4885 @node Static Probe Points
4886 @subsection Static Probe Points
4888 @cindex static probe point, SystemTap
4889 @value{GDBN} supports @dfn{SDT} probes in the code. @acronym{SDT} stands
4890 for Statically Defined Tracing, and the probes are designed to have a tiny
4891 runtime code and data footprint, and no dynamic relocations. They are
4892 usable from assembly, C and C@t{++} languages. See
4893 @uref{http://sourceware.org/systemtap/wiki/UserSpaceProbeImplementation}
4894 for a good reference on how the @acronym{SDT} probes are implemented.
4896 Currently, @code{SystemTap} (@uref{http://sourceware.org/systemtap/})
4897 @acronym{SDT} probes are supported on ELF-compatible systems. See
4898 @uref{http://sourceware.org/systemtap/wiki/AddingUserSpaceProbingToApps}
4899 for more information on how to add @code{SystemTap} @acronym{SDT} probes
4900 in your applications.
4902 @cindex semaphores on static probe points
4903 Some probes have an associated semaphore variable; for instance, this
4904 happens automatically if you defined your probe using a DTrace-style
4905 @file{.d} file. If your probe has a semaphore, @value{GDBN} will
4906 automatically enable it when you specify a breakpoint using the
4907 @samp{-probe-stap} notation. But, if you put a breakpoint at a probe's
4908 location by some other method (e.g., @code{break file:line}), then
4909 @value{GDBN} will not automatically set the semaphore.
4911 You can examine the available static static probes using @code{info
4912 probes}, with optional arguments:
4916 @item info probes stap @r{[}@var{provider} @r{[}@var{name} @r{[}@var{objfile}@r{]}@r{]}@r{]}
4917 If given, @var{provider} is a regular expression used to match against provider
4918 names when selecting which probes to list. If omitted, probes by all
4919 probes from all providers are listed.
4921 If given, @var{name} is a regular expression to match against probe names
4922 when selecting which probes to list. If omitted, probe names are not
4923 considered when deciding whether to display them.
4925 If given, @var{objfile} is a regular expression used to select which
4926 object files (executable or shared libraries) to examine. If not
4927 given, all object files are considered.
4929 @item info probes all
4930 List the available static probes, from all types.
4933 @vindex $_probe_arg@r{, convenience variable}
4934 A probe may specify up to twelve arguments. These are available at the
4935 point at which the probe is defined---that is, when the current PC is
4936 at the probe's location. The arguments are available using the
4937 convenience variables (@pxref{Convenience Vars})
4938 @code{$_probe_arg0}@dots{}@code{$_probe_arg11}. Each probe argument is
4939 an integer of the appropriate size; types are not preserved. The
4940 convenience variable @code{$_probe_argc} holds the number of arguments
4941 at the current probe point.
4943 These variables are always available, but attempts to access them at
4944 any location other than a probe point will cause @value{GDBN} to give
4948 @c @ifclear BARETARGET
4949 @node Error in Breakpoints
4950 @subsection ``Cannot insert breakpoints''
4952 If you request too many active hardware-assisted breakpoints and
4953 watchpoints, you will see this error message:
4955 @c FIXME: the precise wording of this message may change; the relevant
4956 @c source change is not committed yet (Sep 3, 1999).
4958 Stopped; cannot insert breakpoints.
4959 You may have requested too many hardware breakpoints and watchpoints.
4963 This message is printed when you attempt to resume the program, since
4964 only then @value{GDBN} knows exactly how many hardware breakpoints and
4965 watchpoints it needs to insert.
4967 When this message is printed, you need to disable or remove some of the
4968 hardware-assisted breakpoints and watchpoints, and then continue.
4970 @node Breakpoint-related Warnings
4971 @subsection ``Breakpoint address adjusted...''
4972 @cindex breakpoint address adjusted
4974 Some processor architectures place constraints on the addresses at
4975 which breakpoints may be placed. For architectures thus constrained,
4976 @value{GDBN} will attempt to adjust the breakpoint's address to comply
4977 with the constraints dictated by the architecture.
4979 One example of such an architecture is the Fujitsu FR-V. The FR-V is
4980 a VLIW architecture in which a number of RISC-like instructions may be
4981 bundled together for parallel execution. The FR-V architecture
4982 constrains the location of a breakpoint instruction within such a
4983 bundle to the instruction with the lowest address. @value{GDBN}
4984 honors this constraint by adjusting a breakpoint's address to the
4985 first in the bundle.
4987 It is not uncommon for optimized code to have bundles which contain
4988 instructions from different source statements, thus it may happen that
4989 a breakpoint's address will be adjusted from one source statement to
4990 another. Since this adjustment may significantly alter @value{GDBN}'s
4991 breakpoint related behavior from what the user expects, a warning is
4992 printed when the breakpoint is first set and also when the breakpoint
4995 A warning like the one below is printed when setting a breakpoint
4996 that's been subject to address adjustment:
4999 warning: Breakpoint address adjusted from 0x00010414 to 0x00010410.
5002 Such warnings are printed both for user settable and @value{GDBN}'s
5003 internal breakpoints. If you see one of these warnings, you should
5004 verify that a breakpoint set at the adjusted address will have the
5005 desired affect. If not, the breakpoint in question may be removed and
5006 other breakpoints may be set which will have the desired behavior.
5007 E.g., it may be sufficient to place the breakpoint at a later
5008 instruction. A conditional breakpoint may also be useful in some
5009 cases to prevent the breakpoint from triggering too often.
5011 @value{GDBN} will also issue a warning when stopping at one of these
5012 adjusted breakpoints:
5015 warning: Breakpoint 1 address previously adjusted from 0x00010414
5019 When this warning is encountered, it may be too late to take remedial
5020 action except in cases where the breakpoint is hit earlier or more
5021 frequently than expected.
5023 @node Continuing and Stepping
5024 @section Continuing and Stepping
5028 @cindex resuming execution
5029 @dfn{Continuing} means resuming program execution until your program
5030 completes normally. In contrast, @dfn{stepping} means executing just
5031 one more ``step'' of your program, where ``step'' may mean either one
5032 line of source code, or one machine instruction (depending on what
5033 particular command you use). Either when continuing or when stepping,
5034 your program may stop even sooner, due to a breakpoint or a signal. (If
5035 it stops due to a signal, you may want to use @code{handle}, or use
5036 @samp{signal 0} to resume execution. @xref{Signals, ,Signals}.)
5040 @kindex c @r{(@code{continue})}
5041 @kindex fg @r{(resume foreground execution)}
5042 @item continue @r{[}@var{ignore-count}@r{]}
5043 @itemx c @r{[}@var{ignore-count}@r{]}
5044 @itemx fg @r{[}@var{ignore-count}@r{]}
5045 Resume program execution, at the address where your program last stopped;
5046 any breakpoints set at that address are bypassed. The optional argument
5047 @var{ignore-count} allows you to specify a further number of times to
5048 ignore a breakpoint at this location; its effect is like that of
5049 @code{ignore} (@pxref{Conditions, ,Break Conditions}).
5051 The argument @var{ignore-count} is meaningful only when your program
5052 stopped due to a breakpoint. At other times, the argument to
5053 @code{continue} is ignored.
5055 The synonyms @code{c} and @code{fg} (for @dfn{foreground}, as the
5056 debugged program is deemed to be the foreground program) are provided
5057 purely for convenience, and have exactly the same behavior as
5061 To resume execution at a different place, you can use @code{return}
5062 (@pxref{Returning, ,Returning from a Function}) to go back to the
5063 calling function; or @code{jump} (@pxref{Jumping, ,Continuing at a
5064 Different Address}) to go to an arbitrary location in your program.
5066 A typical technique for using stepping is to set a breakpoint
5067 (@pxref{Breakpoints, ,Breakpoints; Watchpoints; and Catchpoints}) at the
5068 beginning of the function or the section of your program where a problem
5069 is believed to lie, run your program until it stops at that breakpoint,
5070 and then step through the suspect area, examining the variables that are
5071 interesting, until you see the problem happen.
5075 @kindex s @r{(@code{step})}
5077 Continue running your program until control reaches a different source
5078 line, then stop it and return control to @value{GDBN}. This command is
5079 abbreviated @code{s}.
5082 @c "without debugging information" is imprecise; actually "without line
5083 @c numbers in the debugging information". (gcc -g1 has debugging info but
5084 @c not line numbers). But it seems complex to try to make that
5085 @c distinction here.
5086 @emph{Warning:} If you use the @code{step} command while control is
5087 within a function that was compiled without debugging information,
5088 execution proceeds until control reaches a function that does have
5089 debugging information. Likewise, it will not step into a function which
5090 is compiled without debugging information. To step through functions
5091 without debugging information, use the @code{stepi} command, described
5095 The @code{step} command only stops at the first instruction of a source
5096 line. This prevents the multiple stops that could otherwise occur in
5097 @code{switch} statements, @code{for} loops, etc. @code{step} continues
5098 to stop if a function that has debugging information is called within
5099 the line. In other words, @code{step} @emph{steps inside} any functions
5100 called within the line.
5102 Also, the @code{step} command only enters a function if there is line
5103 number information for the function. Otherwise it acts like the
5104 @code{next} command. This avoids problems when using @code{cc -gl}
5105 on @acronym{MIPS} machines. Previously, @code{step} entered subroutines if there
5106 was any debugging information about the routine.
5108 @item step @var{count}
5109 Continue running as in @code{step}, but do so @var{count} times. If a
5110 breakpoint is reached, or a signal not related to stepping occurs before
5111 @var{count} steps, stepping stops right away.
5114 @kindex n @r{(@code{next})}
5115 @item next @r{[}@var{count}@r{]}
5116 Continue to the next source line in the current (innermost) stack frame.
5117 This is similar to @code{step}, but function calls that appear within
5118 the line of code are executed without stopping. Execution stops when
5119 control reaches a different line of code at the original stack level
5120 that was executing when you gave the @code{next} command. This command
5121 is abbreviated @code{n}.
5123 An argument @var{count} is a repeat count, as for @code{step}.
5126 @c FIX ME!! Do we delete this, or is there a way it fits in with
5127 @c the following paragraph? --- Vctoria
5129 @c @code{next} within a function that lacks debugging information acts like
5130 @c @code{step}, but any function calls appearing within the code of the
5131 @c function are executed without stopping.
5133 The @code{next} command only stops at the first instruction of a
5134 source line. This prevents multiple stops that could otherwise occur in
5135 @code{switch} statements, @code{for} loops, etc.
5137 @kindex set step-mode
5139 @cindex functions without line info, and stepping
5140 @cindex stepping into functions with no line info
5141 @itemx set step-mode on
5142 The @code{set step-mode on} command causes the @code{step} command to
5143 stop at the first instruction of a function which contains no debug line
5144 information rather than stepping over it.
5146 This is useful in cases where you may be interested in inspecting the
5147 machine instructions of a function which has no symbolic info and do not
5148 want @value{GDBN} to automatically skip over this function.
5150 @item set step-mode off
5151 Causes the @code{step} command to step over any functions which contains no
5152 debug information. This is the default.
5154 @item show step-mode
5155 Show whether @value{GDBN} will stop in or step over functions without
5156 source line debug information.
5159 @kindex fin @r{(@code{finish})}
5161 Continue running until just after function in the selected stack frame
5162 returns. Print the returned value (if any). This command can be
5163 abbreviated as @code{fin}.
5165 Contrast this with the @code{return} command (@pxref{Returning,
5166 ,Returning from a Function}).
5169 @kindex u @r{(@code{until})}
5170 @cindex run until specified location
5173 Continue running until a source line past the current line, in the
5174 current stack frame, is reached. This command is used to avoid single
5175 stepping through a loop more than once. It is like the @code{next}
5176 command, except that when @code{until} encounters a jump, it
5177 automatically continues execution until the program counter is greater
5178 than the address of the jump.
5180 This means that when you reach the end of a loop after single stepping
5181 though it, @code{until} makes your program continue execution until it
5182 exits the loop. In contrast, a @code{next} command at the end of a loop
5183 simply steps back to the beginning of the loop, which forces you to step
5184 through the next iteration.
5186 @code{until} always stops your program if it attempts to exit the current
5189 @code{until} may produce somewhat counterintuitive results if the order
5190 of machine code does not match the order of the source lines. For
5191 example, in the following excerpt from a debugging session, the @code{f}
5192 (@code{frame}) command shows that execution is stopped at line
5193 @code{206}; yet when we use @code{until}, we get to line @code{195}:
5197 #0 main (argc=4, argv=0xf7fffae8) at m4.c:206
5199 (@value{GDBP}) until
5200 195 for ( ; argc > 0; NEXTARG) @{
5203 This happened because, for execution efficiency, the compiler had
5204 generated code for the loop closure test at the end, rather than the
5205 start, of the loop---even though the test in a C @code{for}-loop is
5206 written before the body of the loop. The @code{until} command appeared
5207 to step back to the beginning of the loop when it advanced to this
5208 expression; however, it has not really gone to an earlier
5209 statement---not in terms of the actual machine code.
5211 @code{until} with no argument works by means of single
5212 instruction stepping, and hence is slower than @code{until} with an
5215 @item until @var{location}
5216 @itemx u @var{location}
5217 Continue running your program until either the specified location is
5218 reached, or the current stack frame returns. @var{location} is any of
5219 the forms described in @ref{Specify Location}.
5220 This form of the command uses temporary breakpoints, and
5221 hence is quicker than @code{until} without an argument. The specified
5222 location is actually reached only if it is in the current frame. This
5223 implies that @code{until} can be used to skip over recursive function
5224 invocations. For instance in the code below, if the current location is
5225 line @code{96}, issuing @code{until 99} will execute the program up to
5226 line @code{99} in the same invocation of factorial, i.e., after the inner
5227 invocations have returned.
5230 94 int factorial (int value)
5232 96 if (value > 1) @{
5233 97 value *= factorial (value - 1);
5240 @kindex advance @var{location}
5241 @item advance @var{location}
5242 Continue running the program up to the given @var{location}. An argument is
5243 required, which should be of one of the forms described in
5244 @ref{Specify Location}.
5245 Execution will also stop upon exit from the current stack
5246 frame. This command is similar to @code{until}, but @code{advance} will
5247 not skip over recursive function calls, and the target location doesn't
5248 have to be in the same frame as the current one.
5252 @kindex si @r{(@code{stepi})}
5254 @itemx stepi @var{arg}
5256 Execute one machine instruction, then stop and return to the debugger.
5258 It is often useful to do @samp{display/i $pc} when stepping by machine
5259 instructions. This makes @value{GDBN} automatically display the next
5260 instruction to be executed, each time your program stops. @xref{Auto
5261 Display,, Automatic Display}.
5263 An argument is a repeat count, as in @code{step}.
5267 @kindex ni @r{(@code{nexti})}
5269 @itemx nexti @var{arg}
5271 Execute one machine instruction, but if it is a function call,
5272 proceed until the function returns.
5274 An argument is a repeat count, as in @code{next}.
5278 @anchor{range stepping}
5279 @cindex range stepping
5280 @cindex target-assisted range stepping
5281 By default, and if available, @value{GDBN} makes use of
5282 target-assisted @dfn{range stepping}. In other words, whenever you
5283 use a stepping command (e.g., @code{step}, @code{next}), @value{GDBN}
5284 tells the target to step the corresponding range of instruction
5285 addresses instead of issuing multiple single-steps. This speeds up
5286 line stepping, particularly for remote targets. Ideally, there should
5287 be no reason you would want to turn range stepping off. However, it's
5288 possible that a bug in the debug info, a bug in the remote stub (for
5289 remote targets), or even a bug in @value{GDBN} could make line
5290 stepping behave incorrectly when target-assisted range stepping is
5291 enabled. You can use the following command to turn off range stepping
5295 @kindex set range-stepping
5296 @kindex show range-stepping
5297 @item set range-stepping
5298 @itemx show range-stepping
5299 Control whether range stepping is enabled.
5301 If @code{on}, and the target supports it, @value{GDBN} tells the
5302 target to step a range of addresses itself, instead of issuing
5303 multiple single-steps. If @code{off}, @value{GDBN} always issues
5304 single-steps, even if range stepping is supported by the target. The
5305 default is @code{on}.
5309 @node Skipping Over Functions and Files
5310 @section Skipping Over Functions and Files
5311 @cindex skipping over functions and files
5313 The program you are debugging may contain some functions which are
5314 uninteresting to debug. The @code{skip} comand lets you tell @value{GDBN} to
5315 skip a function or all functions in a file when stepping.
5317 For example, consider the following C function:
5328 Suppose you wish to step into the functions @code{foo} and @code{bar}, but you
5329 are not interested in stepping through @code{boring}. If you run @code{step}
5330 at line 103, you'll enter @code{boring()}, but if you run @code{next}, you'll
5331 step over both @code{foo} and @code{boring}!
5333 One solution is to @code{step} into @code{boring} and use the @code{finish}
5334 command to immediately exit it. But this can become tedious if @code{boring}
5335 is called from many places.
5337 A more flexible solution is to execute @kbd{skip boring}. This instructs
5338 @value{GDBN} never to step into @code{boring}. Now when you execute
5339 @code{step} at line 103, you'll step over @code{boring} and directly into
5342 You can also instruct @value{GDBN} to skip all functions in a file, with, for
5343 example, @code{skip file boring.c}.
5346 @kindex skip function
5347 @item skip @r{[}@var{linespec}@r{]}
5348 @itemx skip function @r{[}@var{linespec}@r{]}
5349 After running this command, the function named by @var{linespec} or the
5350 function containing the line named by @var{linespec} will be skipped over when
5351 stepping. @xref{Specify Location}.
5353 If you do not specify @var{linespec}, the function you're currently debugging
5356 (If you have a function called @code{file} that you want to skip, use
5357 @kbd{skip function file}.)
5360 @item skip file @r{[}@var{filename}@r{]}
5361 After running this command, any function whose source lives in @var{filename}
5362 will be skipped over when stepping.
5364 If you do not specify @var{filename}, functions whose source lives in the file
5365 you're currently debugging will be skipped.
5368 Skips can be listed, deleted, disabled, and enabled, much like breakpoints.
5369 These are the commands for managing your list of skips:
5373 @item info skip @r{[}@var{range}@r{]}
5374 Print details about the specified skip(s). If @var{range} is not specified,
5375 print a table with details about all functions and files marked for skipping.
5376 @code{info skip} prints the following information about each skip:
5380 A number identifying this skip.
5382 The type of this skip, either @samp{function} or @samp{file}.
5383 @item Enabled or Disabled
5384 Enabled skips are marked with @samp{y}. Disabled skips are marked with @samp{n}.
5386 For function skips, this column indicates the address in memory of the function
5387 being skipped. If you've set a function skip on a function which has not yet
5388 been loaded, this field will contain @samp{<PENDING>}. Once a shared library
5389 which has the function is loaded, @code{info skip} will show the function's
5392 For file skips, this field contains the filename being skipped. For functions
5393 skips, this field contains the function name and its line number in the file
5394 where it is defined.
5398 @item skip delete @r{[}@var{range}@r{]}
5399 Delete the specified skip(s). If @var{range} is not specified, delete all
5403 @item skip enable @r{[}@var{range}@r{]}
5404 Enable the specified skip(s). If @var{range} is not specified, enable all
5407 @kindex skip disable
5408 @item skip disable @r{[}@var{range}@r{]}
5409 Disable the specified skip(s). If @var{range} is not specified, disable all
5418 A signal is an asynchronous event that can happen in a program. The
5419 operating system defines the possible kinds of signals, and gives each
5420 kind a name and a number. For example, in Unix @code{SIGINT} is the
5421 signal a program gets when you type an interrupt character (often @kbd{Ctrl-c});
5422 @code{SIGSEGV} is the signal a program gets from referencing a place in
5423 memory far away from all the areas in use; @code{SIGALRM} occurs when
5424 the alarm clock timer goes off (which happens only if your program has
5425 requested an alarm).
5427 @cindex fatal signals
5428 Some signals, including @code{SIGALRM}, are a normal part of the
5429 functioning of your program. Others, such as @code{SIGSEGV}, indicate
5430 errors; these signals are @dfn{fatal} (they kill your program immediately) if the
5431 program has not specified in advance some other way to handle the signal.
5432 @code{SIGINT} does not indicate an error in your program, but it is normally
5433 fatal so it can carry out the purpose of the interrupt: to kill the program.
5435 @value{GDBN} has the ability to detect any occurrence of a signal in your
5436 program. You can tell @value{GDBN} in advance what to do for each kind of
5439 @cindex handling signals
5440 Normally, @value{GDBN} is set up to let the non-erroneous signals like
5441 @code{SIGALRM} be silently passed to your program
5442 (so as not to interfere with their role in the program's functioning)
5443 but to stop your program immediately whenever an error signal happens.
5444 You can change these settings with the @code{handle} command.
5447 @kindex info signals
5451 Print a table of all the kinds of signals and how @value{GDBN} has been told to
5452 handle each one. You can use this to see the signal numbers of all
5453 the defined types of signals.
5455 @item info signals @var{sig}
5456 Similar, but print information only about the specified signal number.
5458 @code{info handle} is an alias for @code{info signals}.
5460 @item catch signal @r{[}@var{signal}@dots{} @r{|} @samp{all}@r{]}
5461 Set a catchpoint for the indicated signals. @xref{Set Catchpoints},
5462 for details about this command.
5465 @item handle @var{signal} @r{[}@var{keywords}@dots{}@r{]}
5466 Change the way @value{GDBN} handles signal @var{signal}. @var{signal}
5467 can be the number of a signal or its name (with or without the
5468 @samp{SIG} at the beginning); a list of signal numbers of the form
5469 @samp{@var{low}-@var{high}}; or the word @samp{all}, meaning all the
5470 known signals. Optional arguments @var{keywords}, described below,
5471 say what change to make.
5475 The keywords allowed by the @code{handle} command can be abbreviated.
5476 Their full names are:
5480 @value{GDBN} should not stop your program when this signal happens. It may
5481 still print a message telling you that the signal has come in.
5484 @value{GDBN} should stop your program when this signal happens. This implies
5485 the @code{print} keyword as well.
5488 @value{GDBN} should print a message when this signal happens.
5491 @value{GDBN} should not mention the occurrence of the signal at all. This
5492 implies the @code{nostop} keyword as well.
5496 @value{GDBN} should allow your program to see this signal; your program
5497 can handle the signal, or else it may terminate if the signal is fatal
5498 and not handled. @code{pass} and @code{noignore} are synonyms.
5502 @value{GDBN} should not allow your program to see this signal.
5503 @code{nopass} and @code{ignore} are synonyms.
5507 When a signal stops your program, the signal is not visible to the
5509 continue. Your program sees the signal then, if @code{pass} is in
5510 effect for the signal in question @emph{at that time}. In other words,
5511 after @value{GDBN} reports a signal, you can use the @code{handle}
5512 command with @code{pass} or @code{nopass} to control whether your
5513 program sees that signal when you continue.
5515 The default is set to @code{nostop}, @code{noprint}, @code{pass} for
5516 non-erroneous signals such as @code{SIGALRM}, @code{SIGWINCH} and
5517 @code{SIGCHLD}, and to @code{stop}, @code{print}, @code{pass} for the
5520 You can also use the @code{signal} command to prevent your program from
5521 seeing a signal, or cause it to see a signal it normally would not see,
5522 or to give it any signal at any time. For example, if your program stopped
5523 due to some sort of memory reference error, you might store correct
5524 values into the erroneous variables and continue, hoping to see more
5525 execution; but your program would probably terminate immediately as
5526 a result of the fatal signal once it saw the signal. To prevent this,
5527 you can continue with @samp{signal 0}. @xref{Signaling, ,Giving your
5530 @cindex extra signal information
5531 @anchor{extra signal information}
5533 On some targets, @value{GDBN} can inspect extra signal information
5534 associated with the intercepted signal, before it is actually
5535 delivered to the program being debugged. This information is exported
5536 by the convenience variable @code{$_siginfo}, and consists of data
5537 that is passed by the kernel to the signal handler at the time of the
5538 receipt of a signal. The data type of the information itself is
5539 target dependent. You can see the data type using the @code{ptype
5540 $_siginfo} command. On Unix systems, it typically corresponds to the
5541 standard @code{siginfo_t} type, as defined in the @file{signal.h}
5544 Here's an example, on a @sc{gnu}/Linux system, printing the stray
5545 referenced address that raised a segmentation fault.
5549 (@value{GDBP}) continue
5550 Program received signal SIGSEGV, Segmentation fault.
5551 0x0000000000400766 in main ()
5553 (@value{GDBP}) ptype $_siginfo
5560 struct @{...@} _kill;
5561 struct @{...@} _timer;
5563 struct @{...@} _sigchld;
5564 struct @{...@} _sigfault;
5565 struct @{...@} _sigpoll;
5568 (@value{GDBP}) ptype $_siginfo._sifields._sigfault
5572 (@value{GDBP}) p $_siginfo._sifields._sigfault.si_addr
5573 $1 = (void *) 0x7ffff7ff7000
5577 Depending on target support, @code{$_siginfo} may also be writable.
5580 @section Stopping and Starting Multi-thread Programs
5582 @cindex stopped threads
5583 @cindex threads, stopped
5585 @cindex continuing threads
5586 @cindex threads, continuing
5588 @value{GDBN} supports debugging programs with multiple threads
5589 (@pxref{Threads,, Debugging Programs with Multiple Threads}). There
5590 are two modes of controlling execution of your program within the
5591 debugger. In the default mode, referred to as @dfn{all-stop mode},
5592 when any thread in your program stops (for example, at a breakpoint
5593 or while being stepped), all other threads in the program are also stopped by
5594 @value{GDBN}. On some targets, @value{GDBN} also supports
5595 @dfn{non-stop mode}, in which other threads can continue to run freely while
5596 you examine the stopped thread in the debugger.
5599 * All-Stop Mode:: All threads stop when GDB takes control
5600 * Non-Stop Mode:: Other threads continue to execute
5601 * Background Execution:: Running your program asynchronously
5602 * Thread-Specific Breakpoints:: Controlling breakpoints
5603 * Interrupted System Calls:: GDB may interfere with system calls
5604 * Observer Mode:: GDB does not alter program behavior
5608 @subsection All-Stop Mode
5610 @cindex all-stop mode
5612 In all-stop mode, whenever your program stops under @value{GDBN} for any reason,
5613 @emph{all} threads of execution stop, not just the current thread. This
5614 allows you to examine the overall state of the program, including
5615 switching between threads, without worrying that things may change
5618 Conversely, whenever you restart the program, @emph{all} threads start
5619 executing. @emph{This is true even when single-stepping} with commands
5620 like @code{step} or @code{next}.
5622 In particular, @value{GDBN} cannot single-step all threads in lockstep.
5623 Since thread scheduling is up to your debugging target's operating
5624 system (not controlled by @value{GDBN}), other threads may
5625 execute more than one statement while the current thread completes a
5626 single step. Moreover, in general other threads stop in the middle of a
5627 statement, rather than at a clean statement boundary, when the program
5630 You might even find your program stopped in another thread after
5631 continuing or even single-stepping. This happens whenever some other
5632 thread runs into a breakpoint, a signal, or an exception before the
5633 first thread completes whatever you requested.
5635 @cindex automatic thread selection
5636 @cindex switching threads automatically
5637 @cindex threads, automatic switching
5638 Whenever @value{GDBN} stops your program, due to a breakpoint or a
5639 signal, it automatically selects the thread where that breakpoint or
5640 signal happened. @value{GDBN} alerts you to the context switch with a
5641 message such as @samp{[Switching to Thread @var{n}]} to identify the
5644 On some OSes, you can modify @value{GDBN}'s default behavior by
5645 locking the OS scheduler to allow only a single thread to run.
5648 @item set scheduler-locking @var{mode}
5649 @cindex scheduler locking mode
5650 @cindex lock scheduler
5651 Set the scheduler locking mode. If it is @code{off}, then there is no
5652 locking and any thread may run at any time. If @code{on}, then only the
5653 current thread may run when the inferior is resumed. The @code{step}
5654 mode optimizes for single-stepping; it prevents other threads
5655 from preempting the current thread while you are stepping, so that
5656 the focus of debugging does not change unexpectedly.
5657 Other threads only rarely (or never) get a chance to run
5658 when you step. They are more likely to run when you @samp{next} over a
5659 function call, and they are completely free to run when you use commands
5660 like @samp{continue}, @samp{until}, or @samp{finish}. However, unless another
5661 thread hits a breakpoint during its timeslice, @value{GDBN} does not change
5662 the current thread away from the thread that you are debugging.
5664 @item show scheduler-locking
5665 Display the current scheduler locking mode.
5668 @cindex resume threads of multiple processes simultaneously
5669 By default, when you issue one of the execution commands such as
5670 @code{continue}, @code{next} or @code{step}, @value{GDBN} allows only
5671 threads of the current inferior to run. For example, if @value{GDBN}
5672 is attached to two inferiors, each with two threads, the
5673 @code{continue} command resumes only the two threads of the current
5674 inferior. This is useful, for example, when you debug a program that
5675 forks and you want to hold the parent stopped (so that, for instance,
5676 it doesn't run to exit), while you debug the child. In other
5677 situations, you may not be interested in inspecting the current state
5678 of any of the processes @value{GDBN} is attached to, and you may want
5679 to resume them all until some breakpoint is hit. In the latter case,
5680 you can instruct @value{GDBN} to allow all threads of all the
5681 inferiors to run with the @w{@code{set schedule-multiple}} command.
5684 @kindex set schedule-multiple
5685 @item set schedule-multiple
5686 Set the mode for allowing threads of multiple processes to be resumed
5687 when an execution command is issued. When @code{on}, all threads of
5688 all processes are allowed to run. When @code{off}, only the threads
5689 of the current process are resumed. The default is @code{off}. The
5690 @code{scheduler-locking} mode takes precedence when set to @code{on},
5691 or while you are stepping and set to @code{step}.
5693 @item show schedule-multiple
5694 Display the current mode for resuming the execution of threads of
5699 @subsection Non-Stop Mode
5701 @cindex non-stop mode
5703 @c This section is really only a place-holder, and needs to be expanded
5704 @c with more details.
5706 For some multi-threaded targets, @value{GDBN} supports an optional
5707 mode of operation in which you can examine stopped program threads in
5708 the debugger while other threads continue to execute freely. This
5709 minimizes intrusion when debugging live systems, such as programs
5710 where some threads have real-time constraints or must continue to
5711 respond to external events. This is referred to as @dfn{non-stop} mode.
5713 In non-stop mode, when a thread stops to report a debugging event,
5714 @emph{only} that thread is stopped; @value{GDBN} does not stop other
5715 threads as well, in contrast to the all-stop mode behavior. Additionally,
5716 execution commands such as @code{continue} and @code{step} apply by default
5717 only to the current thread in non-stop mode, rather than all threads as
5718 in all-stop mode. This allows you to control threads explicitly in
5719 ways that are not possible in all-stop mode --- for example, stepping
5720 one thread while allowing others to run freely, stepping
5721 one thread while holding all others stopped, or stepping several threads
5722 independently and simultaneously.
5724 To enter non-stop mode, use this sequence of commands before you run
5725 or attach to your program:
5728 # Enable the async interface.
5731 # If using the CLI, pagination breaks non-stop.
5734 # Finally, turn it on!
5738 You can use these commands to manipulate the non-stop mode setting:
5741 @kindex set non-stop
5742 @item set non-stop on
5743 Enable selection of non-stop mode.
5744 @item set non-stop off
5745 Disable selection of non-stop mode.
5746 @kindex show non-stop
5748 Show the current non-stop enablement setting.
5751 Note these commands only reflect whether non-stop mode is enabled,
5752 not whether the currently-executing program is being run in non-stop mode.
5753 In particular, the @code{set non-stop} preference is only consulted when
5754 @value{GDBN} starts or connects to the target program, and it is generally
5755 not possible to switch modes once debugging has started. Furthermore,
5756 since not all targets support non-stop mode, even when you have enabled
5757 non-stop mode, @value{GDBN} may still fall back to all-stop operation by
5760 In non-stop mode, all execution commands apply only to the current thread
5761 by default. That is, @code{continue} only continues one thread.
5762 To continue all threads, issue @code{continue -a} or @code{c -a}.
5764 You can use @value{GDBN}'s background execution commands
5765 (@pxref{Background Execution}) to run some threads in the background
5766 while you continue to examine or step others from @value{GDBN}.
5767 The MI execution commands (@pxref{GDB/MI Program Execution}) are
5768 always executed asynchronously in non-stop mode.
5770 Suspending execution is done with the @code{interrupt} command when
5771 running in the background, or @kbd{Ctrl-c} during foreground execution.
5772 In all-stop mode, this stops the whole process;
5773 but in non-stop mode the interrupt applies only to the current thread.
5774 To stop the whole program, use @code{interrupt -a}.
5776 Other execution commands do not currently support the @code{-a} option.
5778 In non-stop mode, when a thread stops, @value{GDBN} doesn't automatically make
5779 that thread current, as it does in all-stop mode. This is because the
5780 thread stop notifications are asynchronous with respect to @value{GDBN}'s
5781 command interpreter, and it would be confusing if @value{GDBN} unexpectedly
5782 changed to a different thread just as you entered a command to operate on the
5783 previously current thread.
5785 @node Background Execution
5786 @subsection Background Execution
5788 @cindex foreground execution
5789 @cindex background execution
5790 @cindex asynchronous execution
5791 @cindex execution, foreground, background and asynchronous
5793 @value{GDBN}'s execution commands have two variants: the normal
5794 foreground (synchronous) behavior, and a background
5795 (asynchronous) behavior. In foreground execution, @value{GDBN} waits for
5796 the program to report that some thread has stopped before prompting for
5797 another command. In background execution, @value{GDBN} immediately gives
5798 a command prompt so that you can issue other commands while your program runs.
5800 You need to explicitly enable asynchronous mode before you can use
5801 background execution commands. You can use these commands to
5802 manipulate the asynchronous mode setting:
5805 @kindex set target-async
5806 @item set target-async on
5807 Enable asynchronous mode.
5808 @item set target-async off
5809 Disable asynchronous mode.
5810 @kindex show target-async
5811 @item show target-async
5812 Show the current target-async setting.
5815 If the target doesn't support async mode, @value{GDBN} issues an error
5816 message if you attempt to use the background execution commands.
5818 To specify background execution, add a @code{&} to the command. For example,
5819 the background form of the @code{continue} command is @code{continue&}, or
5820 just @code{c&}. The execution commands that accept background execution
5826 @xref{Starting, , Starting your Program}.
5830 @xref{Attach, , Debugging an Already-running Process}.
5834 @xref{Continuing and Stepping, step}.
5838 @xref{Continuing and Stepping, stepi}.
5842 @xref{Continuing and Stepping, next}.
5846 @xref{Continuing and Stepping, nexti}.
5850 @xref{Continuing and Stepping, continue}.
5854 @xref{Continuing and Stepping, finish}.
5858 @xref{Continuing and Stepping, until}.
5862 Background execution is especially useful in conjunction with non-stop
5863 mode for debugging programs with multiple threads; see @ref{Non-Stop Mode}.
5864 However, you can also use these commands in the normal all-stop mode with
5865 the restriction that you cannot issue another execution command until the
5866 previous one finishes. Examples of commands that are valid in all-stop
5867 mode while the program is running include @code{help} and @code{info break}.
5869 You can interrupt your program while it is running in the background by
5870 using the @code{interrupt} command.
5877 Suspend execution of the running program. In all-stop mode,
5878 @code{interrupt} stops the whole process, but in non-stop mode, it stops
5879 only the current thread. To stop the whole program in non-stop mode,
5880 use @code{interrupt -a}.
5883 @node Thread-Specific Breakpoints
5884 @subsection Thread-Specific Breakpoints
5886 When your program has multiple threads (@pxref{Threads,, Debugging
5887 Programs with Multiple Threads}), you can choose whether to set
5888 breakpoints on all threads, or on a particular thread.
5891 @cindex breakpoints and threads
5892 @cindex thread breakpoints
5893 @kindex break @dots{} thread @var{threadno}
5894 @item break @var{linespec} thread @var{threadno}
5895 @itemx break @var{linespec} thread @var{threadno} if @dots{}
5896 @var{linespec} specifies source lines; there are several ways of
5897 writing them (@pxref{Specify Location}), but the effect is always to
5898 specify some source line.
5900 Use the qualifier @samp{thread @var{threadno}} with a breakpoint command
5901 to specify that you only want @value{GDBN} to stop the program when a
5902 particular thread reaches this breakpoint. @var{threadno} is one of the
5903 numeric thread identifiers assigned by @value{GDBN}, shown in the first
5904 column of the @samp{info threads} display.
5906 If you do not specify @samp{thread @var{threadno}} when you set a
5907 breakpoint, the breakpoint applies to @emph{all} threads of your
5910 You can use the @code{thread} qualifier on conditional breakpoints as
5911 well; in this case, place @samp{thread @var{threadno}} before or
5912 after the breakpoint condition, like this:
5915 (@value{GDBP}) break frik.c:13 thread 28 if bartab > lim
5920 Thread-specific breakpoints are automatically deleted when
5921 @value{GDBN} detects the corresponding thread is no longer in the
5922 thread list. For example:
5926 Thread-specific breakpoint 3 deleted - thread 28 no longer in the thread list.
5929 There are several ways for a thread to disappear, such as a regular
5930 thread exit, but also when you detach from the process with the
5931 @code{detach} command (@pxref{Attach, ,Debugging an Already-running
5932 Process}), or if @value{GDBN} loses the remote connection
5933 (@pxref{Remote Debugging}), etc. Note that with some targets,
5934 @value{GDBN} is only able to detect a thread has exited when the user
5935 explictly asks for the thread list with the @code{info threads}
5938 @node Interrupted System Calls
5939 @subsection Interrupted System Calls
5941 @cindex thread breakpoints and system calls
5942 @cindex system calls and thread breakpoints
5943 @cindex premature return from system calls
5944 There is an unfortunate side effect when using @value{GDBN} to debug
5945 multi-threaded programs. If one thread stops for a
5946 breakpoint, or for some other reason, and another thread is blocked in a
5947 system call, then the system call may return prematurely. This is a
5948 consequence of the interaction between multiple threads and the signals
5949 that @value{GDBN} uses to implement breakpoints and other events that
5952 To handle this problem, your program should check the return value of
5953 each system call and react appropriately. This is good programming
5956 For example, do not write code like this:
5962 The call to @code{sleep} will return early if a different thread stops
5963 at a breakpoint or for some other reason.
5965 Instead, write this:
5970 unslept = sleep (unslept);
5973 A system call is allowed to return early, so the system is still
5974 conforming to its specification. But @value{GDBN} does cause your
5975 multi-threaded program to behave differently than it would without
5978 Also, @value{GDBN} uses internal breakpoints in the thread library to
5979 monitor certain events such as thread creation and thread destruction.
5980 When such an event happens, a system call in another thread may return
5981 prematurely, even though your program does not appear to stop.
5984 @subsection Observer Mode
5986 If you want to build on non-stop mode and observe program behavior
5987 without any chance of disruption by @value{GDBN}, you can set
5988 variables to disable all of the debugger's attempts to modify state,
5989 whether by writing memory, inserting breakpoints, etc. These operate
5990 at a low level, intercepting operations from all commands.
5992 When all of these are set to @code{off}, then @value{GDBN} is said to
5993 be @dfn{observer mode}. As a convenience, the variable
5994 @code{observer} can be set to disable these, plus enable non-stop
5997 Note that @value{GDBN} will not prevent you from making nonsensical
5998 combinations of these settings. For instance, if you have enabled
5999 @code{may-insert-breakpoints} but disabled @code{may-write-memory},
6000 then breakpoints that work by writing trap instructions into the code
6001 stream will still not be able to be placed.
6006 @item set observer on
6007 @itemx set observer off
6008 When set to @code{on}, this disables all the permission variables
6009 below (except for @code{insert-fast-tracepoints}), plus enables
6010 non-stop debugging. Setting this to @code{off} switches back to
6011 normal debugging, though remaining in non-stop mode.
6014 Show whether observer mode is on or off.
6016 @kindex may-write-registers
6017 @item set may-write-registers on
6018 @itemx set may-write-registers off
6019 This controls whether @value{GDBN} will attempt to alter the values of
6020 registers, such as with assignment expressions in @code{print}, or the
6021 @code{jump} command. It defaults to @code{on}.
6023 @item show may-write-registers
6024 Show the current permission to write registers.
6026 @kindex may-write-memory
6027 @item set may-write-memory on
6028 @itemx set may-write-memory off
6029 This controls whether @value{GDBN} will attempt to alter the contents
6030 of memory, such as with assignment expressions in @code{print}. It
6031 defaults to @code{on}.
6033 @item show may-write-memory
6034 Show the current permission to write memory.
6036 @kindex may-insert-breakpoints
6037 @item set may-insert-breakpoints on
6038 @itemx set may-insert-breakpoints off
6039 This controls whether @value{GDBN} will attempt to insert breakpoints.
6040 This affects all breakpoints, including internal breakpoints defined
6041 by @value{GDBN}. It defaults to @code{on}.
6043 @item show may-insert-breakpoints
6044 Show the current permission to insert breakpoints.
6046 @kindex may-insert-tracepoints
6047 @item set may-insert-tracepoints on
6048 @itemx set may-insert-tracepoints off
6049 This controls whether @value{GDBN} will attempt to insert (regular)
6050 tracepoints at the beginning of a tracing experiment. It affects only
6051 non-fast tracepoints, fast tracepoints being under the control of
6052 @code{may-insert-fast-tracepoints}. It defaults to @code{on}.
6054 @item show may-insert-tracepoints
6055 Show the current permission to insert tracepoints.
6057 @kindex may-insert-fast-tracepoints
6058 @item set may-insert-fast-tracepoints on
6059 @itemx set may-insert-fast-tracepoints off
6060 This controls whether @value{GDBN} will attempt to insert fast
6061 tracepoints at the beginning of a tracing experiment. It affects only
6062 fast tracepoints, regular (non-fast) tracepoints being under the
6063 control of @code{may-insert-tracepoints}. It defaults to @code{on}.
6065 @item show may-insert-fast-tracepoints
6066 Show the current permission to insert fast tracepoints.
6068 @kindex may-interrupt
6069 @item set may-interrupt on
6070 @itemx set may-interrupt off
6071 This controls whether @value{GDBN} will attempt to interrupt or stop
6072 program execution. When this variable is @code{off}, the
6073 @code{interrupt} command will have no effect, nor will
6074 @kbd{Ctrl-c}. It defaults to @code{on}.
6076 @item show may-interrupt
6077 Show the current permission to interrupt or stop the program.
6081 @node Reverse Execution
6082 @chapter Running programs backward
6083 @cindex reverse execution
6084 @cindex running programs backward
6086 When you are debugging a program, it is not unusual to realize that
6087 you have gone too far, and some event of interest has already happened.
6088 If the target environment supports it, @value{GDBN} can allow you to
6089 ``rewind'' the program by running it backward.
6091 A target environment that supports reverse execution should be able
6092 to ``undo'' the changes in machine state that have taken place as the
6093 program was executing normally. Variables, registers etc.@: should
6094 revert to their previous values. Obviously this requires a great
6095 deal of sophistication on the part of the target environment; not
6096 all target environments can support reverse execution.
6098 When a program is executed in reverse, the instructions that
6099 have most recently been executed are ``un-executed'', in reverse
6100 order. The program counter runs backward, following the previous
6101 thread of execution in reverse. As each instruction is ``un-executed'',
6102 the values of memory and/or registers that were changed by that
6103 instruction are reverted to their previous states. After executing
6104 a piece of source code in reverse, all side effects of that code
6105 should be ``undone'', and all variables should be returned to their
6106 prior values@footnote{
6107 Note that some side effects are easier to undo than others. For instance,
6108 memory and registers are relatively easy, but device I/O is hard. Some
6109 targets may be able undo things like device I/O, and some may not.
6111 The contract between @value{GDBN} and the reverse executing target
6112 requires only that the target do something reasonable when
6113 @value{GDBN} tells it to execute backwards, and then report the
6114 results back to @value{GDBN}. Whatever the target reports back to
6115 @value{GDBN}, @value{GDBN} will report back to the user. @value{GDBN}
6116 assumes that the memory and registers that the target reports are in a
6117 consistant state, but @value{GDBN} accepts whatever it is given.
6120 If you are debugging in a target environment that supports
6121 reverse execution, @value{GDBN} provides the following commands.
6124 @kindex reverse-continue
6125 @kindex rc @r{(@code{reverse-continue})}
6126 @item reverse-continue @r{[}@var{ignore-count}@r{]}
6127 @itemx rc @r{[}@var{ignore-count}@r{]}
6128 Beginning at the point where your program last stopped, start executing
6129 in reverse. Reverse execution will stop for breakpoints and synchronous
6130 exceptions (signals), just like normal execution. Behavior of
6131 asynchronous signals depends on the target environment.
6133 @kindex reverse-step
6134 @kindex rs @r{(@code{step})}
6135 @item reverse-step @r{[}@var{count}@r{]}
6136 Run the program backward until control reaches the start of a
6137 different source line; then stop it, and return control to @value{GDBN}.
6139 Like the @code{step} command, @code{reverse-step} will only stop
6140 at the beginning of a source line. It ``un-executes'' the previously
6141 executed source line. If the previous source line included calls to
6142 debuggable functions, @code{reverse-step} will step (backward) into
6143 the called function, stopping at the beginning of the @emph{last}
6144 statement in the called function (typically a return statement).
6146 Also, as with the @code{step} command, if non-debuggable functions are
6147 called, @code{reverse-step} will run thru them backward without stopping.
6149 @kindex reverse-stepi
6150 @kindex rsi @r{(@code{reverse-stepi})}
6151 @item reverse-stepi @r{[}@var{count}@r{]}
6152 Reverse-execute one machine instruction. Note that the instruction
6153 to be reverse-executed is @emph{not} the one pointed to by the program
6154 counter, but the instruction executed prior to that one. For instance,
6155 if the last instruction was a jump, @code{reverse-stepi} will take you
6156 back from the destination of the jump to the jump instruction itself.
6158 @kindex reverse-next
6159 @kindex rn @r{(@code{reverse-next})}
6160 @item reverse-next @r{[}@var{count}@r{]}
6161 Run backward to the beginning of the previous line executed in
6162 the current (innermost) stack frame. If the line contains function
6163 calls, they will be ``un-executed'' without stopping. Starting from
6164 the first line of a function, @code{reverse-next} will take you back
6165 to the caller of that function, @emph{before} the function was called,
6166 just as the normal @code{next} command would take you from the last
6167 line of a function back to its return to its caller
6168 @footnote{Unless the code is too heavily optimized.}.
6170 @kindex reverse-nexti
6171 @kindex rni @r{(@code{reverse-nexti})}
6172 @item reverse-nexti @r{[}@var{count}@r{]}
6173 Like @code{nexti}, @code{reverse-nexti} executes a single instruction
6174 in reverse, except that called functions are ``un-executed'' atomically.
6175 That is, if the previously executed instruction was a return from
6176 another function, @code{reverse-nexti} will continue to execute
6177 in reverse until the call to that function (from the current stack
6180 @kindex reverse-finish
6181 @item reverse-finish
6182 Just as the @code{finish} command takes you to the point where the
6183 current function returns, @code{reverse-finish} takes you to the point
6184 where it was called. Instead of ending up at the end of the current
6185 function invocation, you end up at the beginning.
6187 @kindex set exec-direction
6188 @item set exec-direction
6189 Set the direction of target execution.
6190 @item set exec-direction reverse
6191 @cindex execute forward or backward in time
6192 @value{GDBN} will perform all execution commands in reverse, until the
6193 exec-direction mode is changed to ``forward''. Affected commands include
6194 @code{step, stepi, next, nexti, continue, and finish}. The @code{return}
6195 command cannot be used in reverse mode.
6196 @item set exec-direction forward
6197 @value{GDBN} will perform all execution commands in the normal fashion.
6198 This is the default.
6202 @node Process Record and Replay
6203 @chapter Recording Inferior's Execution and Replaying It
6204 @cindex process record and replay
6205 @cindex recording inferior's execution and replaying it
6207 On some platforms, @value{GDBN} provides a special @dfn{process record
6208 and replay} target that can record a log of the process execution, and
6209 replay it later with both forward and reverse execution commands.
6212 When this target is in use, if the execution log includes the record
6213 for the next instruction, @value{GDBN} will debug in @dfn{replay
6214 mode}. In the replay mode, the inferior does not really execute code
6215 instructions. Instead, all the events that normally happen during
6216 code execution are taken from the execution log. While code is not
6217 really executed in replay mode, the values of registers (including the
6218 program counter register) and the memory of the inferior are still
6219 changed as they normally would. Their contents are taken from the
6223 If the record for the next instruction is not in the execution log,
6224 @value{GDBN} will debug in @dfn{record mode}. In this mode, the
6225 inferior executes normally, and @value{GDBN} records the execution log
6228 The process record and replay target supports reverse execution
6229 (@pxref{Reverse Execution}), even if the platform on which the
6230 inferior runs does not. However, the reverse execution is limited in
6231 this case by the range of the instructions recorded in the execution
6232 log. In other words, reverse execution on platforms that don't
6233 support it directly can only be done in the replay mode.
6235 When debugging in the reverse direction, @value{GDBN} will work in
6236 replay mode as long as the execution log includes the record for the
6237 previous instruction; otherwise, it will work in record mode, if the
6238 platform supports reverse execution, or stop if not.
6240 For architecture environments that support process record and replay,
6241 @value{GDBN} provides the following commands:
6244 @kindex target record
6245 @kindex target record-full
6246 @kindex target record-btrace
6249 @kindex record btrace
6253 @item record @var{method}
6254 This command starts the process record and replay target. The
6255 recording method can be specified as parameter. Without a parameter
6256 the command uses the @code{full} recording method. The following
6257 recording methods are available:
6261 Full record/replay recording using @value{GDBN}'s software record and
6262 replay implementation. This method allows replaying and reverse
6266 Hardware-supported instruction recording. This method does not record
6267 data. Further, the data is collected in a ring buffer so old data will
6268 be overwritten when the buffer is full. It allows limited replay and
6271 This recording method may not be available on all processors.
6274 The process record and replay target can only debug a process that is
6275 already running. Therefore, you need first to start the process with
6276 the @kbd{run} or @kbd{start} commands, and then start the recording
6277 with the @kbd{record @var{method}} command.
6279 Both @code{record @var{method}} and @code{rec @var{method}} are
6280 aliases of @code{target record-@var{method}}.
6282 @cindex displaced stepping, and process record and replay
6283 Displaced stepping (@pxref{Maintenance Commands,, displaced stepping})
6284 will be automatically disabled when process record and replay target
6285 is started. That's because the process record and replay target
6286 doesn't support displaced stepping.
6288 @cindex non-stop mode, and process record and replay
6289 @cindex asynchronous execution, and process record and replay
6290 If the inferior is in the non-stop mode (@pxref{Non-Stop Mode}) or in
6291 the asynchronous execution mode (@pxref{Background Execution}), not
6292 all recording methods are available. The @code{full} recording method
6293 does not support these two modes.
6298 Stop the process record and replay target. When process record and
6299 replay target stops, the entire execution log will be deleted and the
6300 inferior will either be terminated, or will remain in its final state.
6302 When you stop the process record and replay target in record mode (at
6303 the end of the execution log), the inferior will be stopped at the
6304 next instruction that would have been recorded. In other words, if
6305 you record for a while and then stop recording, the inferior process
6306 will be left in the same state as if the recording never happened.
6308 On the other hand, if the process record and replay target is stopped
6309 while in replay mode (that is, not at the end of the execution log,
6310 but at some earlier point), the inferior process will become ``live''
6311 at that earlier state, and it will then be possible to continue the
6312 usual ``live'' debugging of the process from that state.
6314 When the inferior process exits, or @value{GDBN} detaches from it,
6315 process record and replay target will automatically stop itself.
6319 Go to a specific location in the execution log. There are several
6320 ways to specify the location to go to:
6323 @item record goto begin
6324 @itemx record goto start
6325 Go to the beginning of the execution log.
6327 @item record goto end
6328 Go to the end of the execution log.
6330 @item record goto @var{n}
6331 Go to instruction number @var{n} in the execution log.
6335 @item record save @var{filename}
6336 Save the execution log to a file @file{@var{filename}}.
6337 Default filename is @file{gdb_record.@var{process_id}}, where
6338 @var{process_id} is the process ID of the inferior.
6340 This command may not be available for all recording methods.
6342 @kindex record restore
6343 @item record restore @var{filename}
6344 Restore the execution log from a file @file{@var{filename}}.
6345 File must have been created with @code{record save}.
6347 @kindex set record full
6348 @item set record full insn-number-max @var{limit}
6349 @itemx set record full insn-number-max unlimited
6350 Set the limit of instructions to be recorded for the @code{full}
6351 recording method. Default value is 200000.
6353 If @var{limit} is a positive number, then @value{GDBN} will start
6354 deleting instructions from the log once the number of the record
6355 instructions becomes greater than @var{limit}. For every new recorded
6356 instruction, @value{GDBN} will delete the earliest recorded
6357 instruction to keep the number of recorded instructions at the limit.
6358 (Since deleting recorded instructions loses information, @value{GDBN}
6359 lets you control what happens when the limit is reached, by means of
6360 the @code{stop-at-limit} option, described below.)
6362 If @var{limit} is @code{unlimited} or zero, @value{GDBN} will never
6363 delete recorded instructions from the execution log. The number of
6364 recorded instructions is limited only by the available memory.
6366 @kindex show record full
6367 @item show record full insn-number-max
6368 Show the limit of instructions to be recorded with the @code{full}
6371 @item set record full stop-at-limit
6372 Control the behavior of the @code{full} recording method when the
6373 number of recorded instructions reaches the limit. If ON (the
6374 default), @value{GDBN} will stop when the limit is reached for the
6375 first time and ask you whether you want to stop the inferior or
6376 continue running it and recording the execution log. If you decide
6377 to continue recording, each new recorded instruction will cause the
6378 oldest one to be deleted.
6380 If this option is OFF, @value{GDBN} will automatically delete the
6381 oldest record to make room for each new one, without asking.
6383 @item show record full stop-at-limit
6384 Show the current setting of @code{stop-at-limit}.
6386 @item set record full memory-query
6387 Control the behavior when @value{GDBN} is unable to record memory
6388 changes caused by an instruction for the @code{full} recording method.
6389 If ON, @value{GDBN} will query whether to stop the inferior in that
6392 If this option is OFF (the default), @value{GDBN} will automatically
6393 ignore the effect of such instructions on memory. Later, when
6394 @value{GDBN} replays this execution log, it will mark the log of this
6395 instruction as not accessible, and it will not affect the replay
6398 @item show record full memory-query
6399 Show the current setting of @code{memory-query}.
6403 Show various statistics about the recording depending on the recording
6408 For the @code{full} recording method, it shows the state of process
6409 record and its in-memory execution log buffer, including:
6413 Whether in record mode or replay mode.
6415 Lowest recorded instruction number (counting from when the current execution log started recording instructions).
6417 Highest recorded instruction number.
6419 Current instruction about to be replayed (if in replay mode).
6421 Number of instructions contained in the execution log.
6423 Maximum number of instructions that may be contained in the execution log.
6427 For the @code{btrace} recording method, it shows the number of
6428 instructions that have been recorded and the number of blocks of
6429 sequential control-flow that is formed by the recorded instructions.
6432 @kindex record delete
6435 When record target runs in replay mode (``in the past''), delete the
6436 subsequent execution log and begin to record a new execution log starting
6437 from the current address. This means you will abandon the previously
6438 recorded ``future'' and begin recording a new ``future''.
6440 @kindex record instruction-history
6441 @kindex rec instruction-history
6442 @item record instruction-history
6443 Disassembles instructions from the recorded execution log. By
6444 default, ten instructions are disassembled. This can be changed using
6445 the @code{set record instruction-history-size} command. Instructions
6446 are printed in execution order. There are several ways to specify
6447 what part of the execution log to disassemble:
6450 @item record instruction-history @var{insn}
6451 Disassembles ten instructions starting from instruction number
6454 @item record instruction-history @var{insn}, +/-@var{n}
6455 Disassembles @var{n} instructions around instruction number
6456 @var{insn}. If @var{n} is preceded with @code{+}, disassembles
6457 @var{n} instructions after instruction number @var{insn}. If
6458 @var{n} is preceded with @code{-}, disassembles @var{n}
6459 instructions before instruction number @var{insn}.
6461 @item record instruction-history
6462 Disassembles ten more instructions after the last disassembly.
6464 @item record instruction-history -
6465 Disassembles ten more instructions before the last disassembly.
6467 @item record instruction-history @var{begin} @var{end}
6468 Disassembles instructions beginning with instruction number
6469 @var{begin} until instruction number @var{end}. The instruction
6470 number @var{end} is included.
6473 This command may not be available for all recording methods.
6476 @item set record instruction-history-size @var{size}
6477 @itemx set record instruction-history-size unlimited
6478 Define how many instructions to disassemble in the @code{record
6479 instruction-history} command. The default value is 10.
6480 A @var{size} of @code{unlimited} means unlimited instructions.
6483 @item show record instruction-history-size
6484 Show how many instructions to disassemble in the @code{record
6485 instruction-history} command.
6487 @kindex record function-call-history
6488 @kindex rec function-call-history
6489 @item record function-call-history
6490 Prints the execution history at function granularity. It prints one
6491 line for each sequence of instructions that belong to the same
6492 function giving the name of that function, the source lines
6493 for this instruction sequence (if the @code{/l} modifier is
6494 specified), and the instructions numbers that form the sequence (if
6495 the @code{/i} modifier is specified). The function names are indented
6496 to reflect the call stack depth if the @code{/c} modifier is
6497 specified. The @code{/l}, @code{/i}, and @code{/c} modifiers can be
6501 (@value{GDBP}) @b{list 1, 10}
6512 (@value{GDBP}) @b{record function-call-history /ilc}
6513 1 bar inst 1,4 at foo.c:6,8
6514 2 foo inst 5,10 at foo.c:2,3
6515 3 bar inst 11,13 at foo.c:9,10
6518 By default, ten lines are printed. This can be changed using the
6519 @code{set record function-call-history-size} command. Functions are
6520 printed in execution order. There are several ways to specify what
6524 @item record function-call-history @var{func}
6525 Prints ten functions starting from function number @var{func}.
6527 @item record function-call-history @var{func}, +/-@var{n}
6528 Prints @var{n} functions around function number @var{func}. If
6529 @var{n} is preceded with @code{+}, prints @var{n} functions after
6530 function number @var{func}. If @var{n} is preceded with @code{-},
6531 prints @var{n} functions before function number @var{func}.
6533 @item record function-call-history
6534 Prints ten more functions after the last ten-line print.
6536 @item record function-call-history -
6537 Prints ten more functions before the last ten-line print.
6539 @item record function-call-history @var{begin} @var{end}
6540 Prints functions beginning with function number @var{begin} until
6541 function number @var{end}. The function number @var{end} is included.
6544 This command may not be available for all recording methods.
6546 @item set record function-call-history-size @var{size}
6547 @itemx set record function-call-history-size unlimited
6548 Define how many lines to print in the
6549 @code{record function-call-history} command. The default value is 10.
6550 A size of @code{unlimited} means unlimited lines.
6552 @item show record function-call-history-size
6553 Show how many lines to print in the
6554 @code{record function-call-history} command.
6559 @chapter Examining the Stack
6561 When your program has stopped, the first thing you need to know is where it
6562 stopped and how it got there.
6565 Each time your program performs a function call, information about the call
6567 That information includes the location of the call in your program,
6568 the arguments of the call,
6569 and the local variables of the function being called.
6570 The information is saved in a block of data called a @dfn{stack frame}.
6571 The stack frames are allocated in a region of memory called the @dfn{call
6574 When your program stops, the @value{GDBN} commands for examining the
6575 stack allow you to see all of this information.
6577 @cindex selected frame
6578 One of the stack frames is @dfn{selected} by @value{GDBN} and many
6579 @value{GDBN} commands refer implicitly to the selected frame. In
6580 particular, whenever you ask @value{GDBN} for the value of a variable in
6581 your program, the value is found in the selected frame. There are
6582 special @value{GDBN} commands to select whichever frame you are
6583 interested in. @xref{Selection, ,Selecting a Frame}.
6585 When your program stops, @value{GDBN} automatically selects the
6586 currently executing frame and describes it briefly, similar to the
6587 @code{frame} command (@pxref{Frame Info, ,Information about a Frame}).
6590 * Frames:: Stack frames
6591 * Backtrace:: Backtraces
6592 * Frame Filter Management:: Managing frame filters
6593 * Selection:: Selecting a frame
6594 * Frame Info:: Information on a frame
6599 @section Stack Frames
6601 @cindex frame, definition
6603 The call stack is divided up into contiguous pieces called @dfn{stack
6604 frames}, or @dfn{frames} for short; each frame is the data associated
6605 with one call to one function. The frame contains the arguments given
6606 to the function, the function's local variables, and the address at
6607 which the function is executing.
6609 @cindex initial frame
6610 @cindex outermost frame
6611 @cindex innermost frame
6612 When your program is started, the stack has only one frame, that of the
6613 function @code{main}. This is called the @dfn{initial} frame or the
6614 @dfn{outermost} frame. Each time a function is called, a new frame is
6615 made. Each time a function returns, the frame for that function invocation
6616 is eliminated. If a function is recursive, there can be many frames for
6617 the same function. The frame for the function in which execution is
6618 actually occurring is called the @dfn{innermost} frame. This is the most
6619 recently created of all the stack frames that still exist.
6621 @cindex frame pointer
6622 Inside your program, stack frames are identified by their addresses. A
6623 stack frame consists of many bytes, each of which has its own address; each
6624 kind of computer has a convention for choosing one byte whose
6625 address serves as the address of the frame. Usually this address is kept
6626 in a register called the @dfn{frame pointer register}
6627 (@pxref{Registers, $fp}) while execution is going on in that frame.
6629 @cindex frame number
6630 @value{GDBN} assigns numbers to all existing stack frames, starting with
6631 zero for the innermost frame, one for the frame that called it,
6632 and so on upward. These numbers do not really exist in your program;
6633 they are assigned by @value{GDBN} to give you a way of designating stack
6634 frames in @value{GDBN} commands.
6636 @c The -fomit-frame-pointer below perennially causes hbox overflow
6637 @c underflow problems.
6638 @cindex frameless execution
6639 Some compilers provide a way to compile functions so that they operate
6640 without stack frames. (For example, the @value{NGCC} option
6642 @samp{-fomit-frame-pointer}
6644 generates functions without a frame.)
6645 This is occasionally done with heavily used library functions to save
6646 the frame setup time. @value{GDBN} has limited facilities for dealing
6647 with these function invocations. If the innermost function invocation
6648 has no stack frame, @value{GDBN} nevertheless regards it as though
6649 it had a separate frame, which is numbered zero as usual, allowing
6650 correct tracing of the function call chain. However, @value{GDBN} has
6651 no provision for frameless functions elsewhere in the stack.
6654 @kindex frame@r{, command}
6655 @cindex current stack frame
6656 @item frame @var{args}
6657 The @code{frame} command allows you to move from one stack frame to another,
6658 and to print the stack frame you select. @var{args} may be either the
6659 address of the frame or the stack frame number. Without an argument,
6660 @code{frame} prints the current stack frame.
6662 @kindex select-frame
6663 @cindex selecting frame silently
6665 The @code{select-frame} command allows you to move from one stack frame
6666 to another without printing the frame. This is the silent version of
6674 @cindex call stack traces
6675 A backtrace is a summary of how your program got where it is. It shows one
6676 line per frame, for many frames, starting with the currently executing
6677 frame (frame zero), followed by its caller (frame one), and on up the
6680 @anchor{backtrace-command}
6683 @kindex bt @r{(@code{backtrace})}
6686 Print a backtrace of the entire stack: one line per frame for all
6687 frames in the stack.
6689 You can stop the backtrace at any time by typing the system interrupt
6690 character, normally @kbd{Ctrl-c}.
6692 @item backtrace @var{n}
6694 Similar, but print only the innermost @var{n} frames.
6696 @item backtrace -@var{n}
6698 Similar, but print only the outermost @var{n} frames.
6700 @item backtrace full
6702 @itemx bt full @var{n}
6703 @itemx bt full -@var{n}
6704 Print the values of the local variables also. @var{n} specifies the
6705 number of frames to print, as described above.
6707 @item backtrace no-filters
6708 @itemx bt no-filters
6709 @itemx bt no-filters @var{n}
6710 @itemx bt no-filters -@var{n}
6711 @itemx bt no-filters full
6712 @itemx bt no-filters full @var{n}
6713 @itemx bt no-filters full -@var{n}
6714 Do not run Python frame filters on this backtrace. @xref{Frame
6715 Filter API}, for more information. Additionally use @ref{disable
6716 frame-filter all} to turn off all frame filters. This is only
6717 relevant when @value{GDBN} has been configured with @code{Python}
6723 The names @code{where} and @code{info stack} (abbreviated @code{info s})
6724 are additional aliases for @code{backtrace}.
6726 @cindex multiple threads, backtrace
6727 In a multi-threaded program, @value{GDBN} by default shows the
6728 backtrace only for the current thread. To display the backtrace for
6729 several or all of the threads, use the command @code{thread apply}
6730 (@pxref{Threads, thread apply}). For example, if you type @kbd{thread
6731 apply all backtrace}, @value{GDBN} will display the backtrace for all
6732 the threads; this is handy when you debug a core dump of a
6733 multi-threaded program.
6735 Each line in the backtrace shows the frame number and the function name.
6736 The program counter value is also shown---unless you use @code{set
6737 print address off}. The backtrace also shows the source file name and
6738 line number, as well as the arguments to the function. The program
6739 counter value is omitted if it is at the beginning of the code for that
6742 Here is an example of a backtrace. It was made with the command
6743 @samp{bt 3}, so it shows the innermost three frames.
6747 #0 m4_traceon (obs=0x24eb0, argc=1, argv=0x2b8c8)
6749 #1 0x6e38 in expand_macro (sym=0x2b600, data=...) at macro.c:242
6750 #2 0x6840 in expand_token (obs=0x0, t=177664, td=0xf7fffb08)
6752 (More stack frames follow...)
6757 The display for frame zero does not begin with a program counter
6758 value, indicating that your program has stopped at the beginning of the
6759 code for line @code{993} of @code{builtin.c}.
6762 The value of parameter @code{data} in frame 1 has been replaced by
6763 @code{@dots{}}. By default, @value{GDBN} prints the value of a parameter
6764 only if it is a scalar (integer, pointer, enumeration, etc). See command
6765 @kbd{set print frame-arguments} in @ref{Print Settings} for more details
6766 on how to configure the way function parameter values are printed.
6768 @cindex optimized out, in backtrace
6769 @cindex function call arguments, optimized out
6770 If your program was compiled with optimizations, some compilers will
6771 optimize away arguments passed to functions if those arguments are
6772 never used after the call. Such optimizations generate code that
6773 passes arguments through registers, but doesn't store those arguments
6774 in the stack frame. @value{GDBN} has no way of displaying such
6775 arguments in stack frames other than the innermost one. Here's what
6776 such a backtrace might look like:
6780 #0 m4_traceon (obs=0x24eb0, argc=1, argv=0x2b8c8)
6782 #1 0x6e38 in expand_macro (sym=<optimized out>) at macro.c:242
6783 #2 0x6840 in expand_token (obs=0x0, t=<optimized out>, td=0xf7fffb08)
6785 (More stack frames follow...)
6790 The values of arguments that were not saved in their stack frames are
6791 shown as @samp{<optimized out>}.
6793 If you need to display the values of such optimized-out arguments,
6794 either deduce that from other variables whose values depend on the one
6795 you are interested in, or recompile without optimizations.
6797 @cindex backtrace beyond @code{main} function
6798 @cindex program entry point
6799 @cindex startup code, and backtrace
6800 Most programs have a standard user entry point---a place where system
6801 libraries and startup code transition into user code. For C this is
6802 @code{main}@footnote{
6803 Note that embedded programs (the so-called ``free-standing''
6804 environment) are not required to have a @code{main} function as the
6805 entry point. They could even have multiple entry points.}.
6806 When @value{GDBN} finds the entry function in a backtrace
6807 it will terminate the backtrace, to avoid tracing into highly
6808 system-specific (and generally uninteresting) code.
6810 If you need to examine the startup code, or limit the number of levels
6811 in a backtrace, you can change this behavior:
6814 @item set backtrace past-main
6815 @itemx set backtrace past-main on
6816 @kindex set backtrace
6817 Backtraces will continue past the user entry point.
6819 @item set backtrace past-main off
6820 Backtraces will stop when they encounter the user entry point. This is the
6823 @item show backtrace past-main
6824 @kindex show backtrace
6825 Display the current user entry point backtrace policy.
6827 @item set backtrace past-entry
6828 @itemx set backtrace past-entry on
6829 Backtraces will continue past the internal entry point of an application.
6830 This entry point is encoded by the linker when the application is built,
6831 and is likely before the user entry point @code{main} (or equivalent) is called.
6833 @item set backtrace past-entry off
6834 Backtraces will stop when they encounter the internal entry point of an
6835 application. This is the default.
6837 @item show backtrace past-entry
6838 Display the current internal entry point backtrace policy.
6840 @item set backtrace limit @var{n}
6841 @itemx set backtrace limit 0
6842 @itemx set backtrace limit unlimited
6843 @cindex backtrace limit
6844 Limit the backtrace to @var{n} levels. A value of @code{unlimited}
6845 or zero means unlimited levels.
6847 @item show backtrace limit
6848 Display the current limit on backtrace levels.
6851 You can control how file names are displayed.
6854 @item set filename-display
6855 @itemx set filename-display relative
6856 @cindex filename-display
6857 Display file names relative to the compilation directory. This is the default.
6859 @item set filename-display basename
6860 Display only basename of a filename.
6862 @item set filename-display absolute
6863 Display an absolute filename.
6865 @item show filename-display
6866 Show the current way to display filenames.
6869 @node Frame Filter Management
6870 @section Management of Frame Filters.
6871 @cindex managing frame filters
6873 Frame filters are Python based utilities to manage and decorate the
6874 output of frames. @xref{Frame Filter API}, for further information.
6876 Managing frame filters is performed by several commands available
6877 within @value{GDBN}, detailed here.
6880 @kindex info frame-filter
6881 @item info frame-filter
6882 Print a list of installed frame filters from all dictionaries, showing
6883 their name, priority and enabled status.
6885 @kindex disable frame-filter
6886 @anchor{disable frame-filter all}
6887 @item disable frame-filter @var{filter-dictionary} @var{filter-name}
6888 Disable a frame filter in the dictionary matching
6889 @var{filter-dictionary}, or @code{all}, and @var{filter-name}.
6890 @var{filter-dictionary} may be @code{all}, @code{global},
6891 @code{progspace} or the name of the object file where the frame filter
6892 dictionary resides. When @code{all} is specified, all frame filters
6893 across all dictionaries are disabled. @var{filter-name} is the name
6894 of the frame filter and is used when @code{all} is not the option for
6895 @var{filter-dictionary}. A disabled frame-filter is not deleted, it
6896 may be enabled again later.
6898 @kindex enable frame-filter
6899 @item enable frame-filter @var{filter-dictionary} @var{filter-name}
6900 Enable a frame filter in the dictionary matching
6901 @var{filter-dictionary}, or @code{all}, and @var{filter-name}.
6902 @var{filter-dictionary} may be @code{all}, @code{global},
6903 @code{progspace} or the name of the object file where the frame filter
6904 dictionary resides. When @code{all} is specified, all frame filters across
6905 all dictionaries are enabled. @var{filter-name} is the name of the frame
6906 filter and is used when @code{all} is not the option for
6907 @var{filter-dictionary}.
6912 (gdb) info frame-filter
6914 global frame-filters:
6915 Priority Enabled Name
6916 1000 No PrimaryFunctionFilter
6919 progspace /build/test frame-filters:
6920 Priority Enabled Name
6921 100 Yes ProgspaceFilter
6923 objfile /build/test frame-filters:
6924 Priority Enabled Name
6925 999 Yes BuildProgra Filter
6927 (gdb) disable frame-filter /build/test BuildProgramFilter
6928 (gdb) info frame-filter
6930 global frame-filters:
6931 Priority Enabled Name
6932 1000 No PrimaryFunctionFilter
6935 progspace /build/test frame-filters:
6936 Priority Enabled Name
6937 100 Yes ProgspaceFilter
6939 objfile /build/test frame-filters:
6940 Priority Enabled Name
6941 999 No BuildProgramFilter
6943 (gdb) enable frame-filter global PrimaryFunctionFilter
6944 (gdb) info frame-filter
6946 global frame-filters:
6947 Priority Enabled Name
6948 1000 Yes PrimaryFunctionFilter
6951 progspace /build/test frame-filters:
6952 Priority Enabled Name
6953 100 Yes ProgspaceFilter
6955 objfile /build/test frame-filters:
6956 Priority Enabled Name
6957 999 No BuildProgramFilter
6960 @kindex set frame-filter priority
6961 @item set frame-filter priority @var{filter-dictionary} @var{filter-name} @var{priority}
6962 Set the @var{priority} of a frame filter in the dictionary matching
6963 @var{filter-dictionary}, and the frame filter name matching
6964 @var{filter-name}. @var{filter-dictionary} may be @code{global},
6965 @code{progspace} or the name of the object file where the frame filter
6966 dictionary resides. @var{priority} is an integer.
6968 @kindex show frame-filter priority
6969 @item show frame-filter priority @var{filter-dictionary} @var{filter-name}
6970 Show the @var{priority} of a frame filter in the dictionary matching
6971 @var{filter-dictionary}, and the frame filter name matching
6972 @var{filter-name}. @var{filter-dictionary} may be @code{global},
6973 @code{progspace} or the name of the object file where the frame filter
6979 (gdb) info frame-filter
6981 global frame-filters:
6982 Priority Enabled Name
6983 1000 Yes PrimaryFunctionFilter
6986 progspace /build/test frame-filters:
6987 Priority Enabled Name
6988 100 Yes ProgspaceFilter
6990 objfile /build/test frame-filters:
6991 Priority Enabled Name
6992 999 No BuildProgramFilter
6994 (gdb) set frame-filter priority global Reverse 50
6995 (gdb) info frame-filter
6997 global frame-filters:
6998 Priority Enabled Name
6999 1000 Yes PrimaryFunctionFilter
7002 progspace /build/test frame-filters:
7003 Priority Enabled Name
7004 100 Yes ProgspaceFilter
7006 objfile /build/test frame-filters:
7007 Priority Enabled Name
7008 999 No BuildProgramFilter
7013 @section Selecting a Frame
7015 Most commands for examining the stack and other data in your program work on
7016 whichever stack frame is selected at the moment. Here are the commands for
7017 selecting a stack frame; all of them finish by printing a brief description
7018 of the stack frame just selected.
7021 @kindex frame@r{, selecting}
7022 @kindex f @r{(@code{frame})}
7025 Select frame number @var{n}. Recall that frame zero is the innermost
7026 (currently executing) frame, frame one is the frame that called the
7027 innermost one, and so on. The highest-numbered frame is the one for
7030 @item frame @var{addr}
7032 Select the frame at address @var{addr}. This is useful mainly if the
7033 chaining of stack frames has been damaged by a bug, making it
7034 impossible for @value{GDBN} to assign numbers properly to all frames. In
7035 addition, this can be useful when your program has multiple stacks and
7036 switches between them.
7038 On the SPARC architecture, @code{frame} needs two addresses to
7039 select an arbitrary frame: a frame pointer and a stack pointer.
7041 On the @acronym{MIPS} and Alpha architecture, it needs two addresses: a stack
7042 pointer and a program counter.
7044 On the 29k architecture, it needs three addresses: a register stack
7045 pointer, a program counter, and a memory stack pointer.
7049 Move @var{n} frames up the stack. For positive numbers @var{n}, this
7050 advances toward the outermost frame, to higher frame numbers, to frames
7051 that have existed longer. @var{n} defaults to one.
7054 @kindex do @r{(@code{down})}
7056 Move @var{n} frames down the stack. For positive numbers @var{n}, this
7057 advances toward the innermost frame, to lower frame numbers, to frames
7058 that were created more recently. @var{n} defaults to one. You may
7059 abbreviate @code{down} as @code{do}.
7062 All of these commands end by printing two lines of output describing the
7063 frame. The first line shows the frame number, the function name, the
7064 arguments, and the source file and line number of execution in that
7065 frame. The second line shows the text of that source line.
7073 #1 0x22f0 in main (argc=1, argv=0xf7fffbf4, env=0xf7fffbfc)
7075 10 read_input_file (argv[i]);
7079 After such a printout, the @code{list} command with no arguments
7080 prints ten lines centered on the point of execution in the frame.
7081 You can also edit the program at the point of execution with your favorite
7082 editing program by typing @code{edit}.
7083 @xref{List, ,Printing Source Lines},
7087 @kindex down-silently
7089 @item up-silently @var{n}
7090 @itemx down-silently @var{n}
7091 These two commands are variants of @code{up} and @code{down},
7092 respectively; they differ in that they do their work silently, without
7093 causing display of the new frame. They are intended primarily for use
7094 in @value{GDBN} command scripts, where the output might be unnecessary and
7099 @section Information About a Frame
7101 There are several other commands to print information about the selected
7107 When used without any argument, this command does not change which
7108 frame is selected, but prints a brief description of the currently
7109 selected stack frame. It can be abbreviated @code{f}. With an
7110 argument, this command is used to select a stack frame.
7111 @xref{Selection, ,Selecting a Frame}.
7114 @kindex info f @r{(@code{info frame})}
7117 This command prints a verbose description of the selected stack frame,
7122 the address of the frame
7124 the address of the next frame down (called by this frame)
7126 the address of the next frame up (caller of this frame)
7128 the language in which the source code corresponding to this frame is written
7130 the address of the frame's arguments
7132 the address of the frame's local variables
7134 the program counter saved in it (the address of execution in the caller frame)
7136 which registers were saved in the frame
7139 @noindent The verbose description is useful when
7140 something has gone wrong that has made the stack format fail to fit
7141 the usual conventions.
7143 @item info frame @var{addr}
7144 @itemx info f @var{addr}
7145 Print a verbose description of the frame at address @var{addr}, without
7146 selecting that frame. The selected frame remains unchanged by this
7147 command. This requires the same kind of address (more than one for some
7148 architectures) that you specify in the @code{frame} command.
7149 @xref{Selection, ,Selecting a Frame}.
7153 Print the arguments of the selected frame, each on a separate line.
7157 Print the local variables of the selected frame, each on a separate
7158 line. These are all variables (declared either static or automatic)
7159 accessible at the point of execution of the selected frame.
7165 @chapter Examining Source Files
7167 @value{GDBN} can print parts of your program's source, since the debugging
7168 information recorded in the program tells @value{GDBN} what source files were
7169 used to build it. When your program stops, @value{GDBN} spontaneously prints
7170 the line where it stopped. Likewise, when you select a stack frame
7171 (@pxref{Selection, ,Selecting a Frame}), @value{GDBN} prints the line where
7172 execution in that frame has stopped. You can print other portions of
7173 source files by explicit command.
7175 If you use @value{GDBN} through its @sc{gnu} Emacs interface, you may
7176 prefer to use Emacs facilities to view source; see @ref{Emacs, ,Using
7177 @value{GDBN} under @sc{gnu} Emacs}.
7180 * List:: Printing source lines
7181 * Specify Location:: How to specify code locations
7182 * Edit:: Editing source files
7183 * Search:: Searching source files
7184 * Source Path:: Specifying source directories
7185 * Machine Code:: Source and machine code
7189 @section Printing Source Lines
7192 @kindex l @r{(@code{list})}
7193 To print lines from a source file, use the @code{list} command
7194 (abbreviated @code{l}). By default, ten lines are printed.
7195 There are several ways to specify what part of the file you want to
7196 print; see @ref{Specify Location}, for the full list.
7198 Here are the forms of the @code{list} command most commonly used:
7201 @item list @var{linenum}
7202 Print lines centered around line number @var{linenum} in the
7203 current source file.
7205 @item list @var{function}
7206 Print lines centered around the beginning of function
7210 Print more lines. If the last lines printed were printed with a
7211 @code{list} command, this prints lines following the last lines
7212 printed; however, if the last line printed was a solitary line printed
7213 as part of displaying a stack frame (@pxref{Stack, ,Examining the
7214 Stack}), this prints lines centered around that line.
7217 Print lines just before the lines last printed.
7220 @cindex @code{list}, how many lines to display
7221 By default, @value{GDBN} prints ten source lines with any of these forms of
7222 the @code{list} command. You can change this using @code{set listsize}:
7225 @kindex set listsize
7226 @item set listsize @var{count}
7227 @itemx set listsize unlimited
7228 Make the @code{list} command display @var{count} source lines (unless
7229 the @code{list} argument explicitly specifies some other number).
7230 Setting @var{count} to @code{unlimited} or 0 means there's no limit.
7232 @kindex show listsize
7234 Display the number of lines that @code{list} prints.
7237 Repeating a @code{list} command with @key{RET} discards the argument,
7238 so it is equivalent to typing just @code{list}. This is more useful
7239 than listing the same lines again. An exception is made for an
7240 argument of @samp{-}; that argument is preserved in repetition so that
7241 each repetition moves up in the source file.
7243 In general, the @code{list} command expects you to supply zero, one or two
7244 @dfn{linespecs}. Linespecs specify source lines; there are several ways
7245 of writing them (@pxref{Specify Location}), but the effect is always
7246 to specify some source line.
7248 Here is a complete description of the possible arguments for @code{list}:
7251 @item list @var{linespec}
7252 Print lines centered around the line specified by @var{linespec}.
7254 @item list @var{first},@var{last}
7255 Print lines from @var{first} to @var{last}. Both arguments are
7256 linespecs. When a @code{list} command has two linespecs, and the
7257 source file of the second linespec is omitted, this refers to
7258 the same source file as the first linespec.
7260 @item list ,@var{last}
7261 Print lines ending with @var{last}.
7263 @item list @var{first},
7264 Print lines starting with @var{first}.
7267 Print lines just after the lines last printed.
7270 Print lines just before the lines last printed.
7273 As described in the preceding table.
7276 @node Specify Location
7277 @section Specifying a Location
7278 @cindex specifying location
7281 Several @value{GDBN} commands accept arguments that specify a location
7282 of your program's code. Since @value{GDBN} is a source-level
7283 debugger, a location usually specifies some line in the source code;
7284 for that reason, locations are also known as @dfn{linespecs}.
7286 Here are all the different ways of specifying a code location that
7287 @value{GDBN} understands:
7291 Specifies the line number @var{linenum} of the current source file.
7294 @itemx +@var{offset}
7295 Specifies the line @var{offset} lines before or after the @dfn{current
7296 line}. For the @code{list} command, the current line is the last one
7297 printed; for the breakpoint commands, this is the line at which
7298 execution stopped in the currently selected @dfn{stack frame}
7299 (@pxref{Frames, ,Frames}, for a description of stack frames.) When
7300 used as the second of the two linespecs in a @code{list} command,
7301 this specifies the line @var{offset} lines up or down from the first
7304 @item @var{filename}:@var{linenum}
7305 Specifies the line @var{linenum} in the source file @var{filename}.
7306 If @var{filename} is a relative file name, then it will match any
7307 source file name with the same trailing components. For example, if
7308 @var{filename} is @samp{gcc/expr.c}, then it will match source file
7309 name of @file{/build/trunk/gcc/expr.c}, but not
7310 @file{/build/trunk/libcpp/expr.c} or @file{/build/trunk/gcc/x-expr.c}.
7312 @item @var{function}
7313 Specifies the line that begins the body of the function @var{function}.
7314 For example, in C, this is the line with the open brace.
7316 @item @var{function}:@var{label}
7317 Specifies the line where @var{label} appears in @var{function}.
7319 @item @var{filename}:@var{function}
7320 Specifies the line that begins the body of the function @var{function}
7321 in the file @var{filename}. You only need the file name with a
7322 function name to avoid ambiguity when there are identically named
7323 functions in different source files.
7326 Specifies the line at which the label named @var{label} appears.
7327 @value{GDBN} searches for the label in the function corresponding to
7328 the currently selected stack frame. If there is no current selected
7329 stack frame (for instance, if the inferior is not running), then
7330 @value{GDBN} will not search for a label.
7332 @item *@var{address}
7333 Specifies the program address @var{address}. For line-oriented
7334 commands, such as @code{list} and @code{edit}, this specifies a source
7335 line that contains @var{address}. For @code{break} and other
7336 breakpoint oriented commands, this can be used to set breakpoints in
7337 parts of your program which do not have debugging information or
7340 Here @var{address} may be any expression valid in the current working
7341 language (@pxref{Languages, working language}) that specifies a code
7342 address. In addition, as a convenience, @value{GDBN} extends the
7343 semantics of expressions used in locations to cover the situations
7344 that frequently happen during debugging. Here are the various forms
7348 @item @var{expression}
7349 Any expression valid in the current working language.
7351 @item @var{funcaddr}
7352 An address of a function or procedure derived from its name. In C,
7353 C@t{++}, Java, Objective-C, Fortran, minimal, and assembly, this is
7354 simply the function's name @var{function} (and actually a special case
7355 of a valid expression). In Pascal and Modula-2, this is
7356 @code{&@var{function}}. In Ada, this is @code{@var{function}'Address}
7357 (although the Pascal form also works).
7359 This form specifies the address of the function's first instruction,
7360 before the stack frame and arguments have been set up.
7362 @item '@var{filename}'::@var{funcaddr}
7363 Like @var{funcaddr} above, but also specifies the name of the source
7364 file explicitly. This is useful if the name of the function does not
7365 specify the function unambiguously, e.g., if there are several
7366 functions with identical names in different source files.
7369 @cindex breakpoint at static probe point
7370 @item -pstap|-probe-stap @r{[}@var{objfile}:@r{[}@var{provider}:@r{]}@r{]}@var{name}
7371 The @sc{gnu}/Linux tool @code{SystemTap} provides a way for
7372 applications to embed static probes. @xref{Static Probe Points}, for more
7373 information on finding and using static probes. This form of linespec
7374 specifies the location of such a static probe.
7376 If @var{objfile} is given, only probes coming from that shared library
7377 or executable matching @var{objfile} as a regular expression are considered.
7378 If @var{provider} is given, then only probes from that provider are considered.
7379 If several probes match the spec, @value{GDBN} will insert a breakpoint at
7380 each one of those probes.
7386 @section Editing Source Files
7387 @cindex editing source files
7390 @kindex e @r{(@code{edit})}
7391 To edit the lines in a source file, use the @code{edit} command.
7392 The editing program of your choice
7393 is invoked with the current line set to
7394 the active line in the program.
7395 Alternatively, there are several ways to specify what part of the file you
7396 want to print if you want to see other parts of the program:
7399 @item edit @var{location}
7400 Edit the source file specified by @code{location}. Editing starts at
7401 that @var{location}, e.g., at the specified source line of the
7402 specified file. @xref{Specify Location}, for all the possible forms
7403 of the @var{location} argument; here are the forms of the @code{edit}
7404 command most commonly used:
7407 @item edit @var{number}
7408 Edit the current source file with @var{number} as the active line number.
7410 @item edit @var{function}
7411 Edit the file containing @var{function} at the beginning of its definition.
7416 @subsection Choosing your Editor
7417 You can customize @value{GDBN} to use any editor you want
7419 The only restriction is that your editor (say @code{ex}), recognizes the
7420 following command-line syntax:
7422 ex +@var{number} file
7424 The optional numeric value +@var{number} specifies the number of the line in
7425 the file where to start editing.}.
7426 By default, it is @file{@value{EDITOR}}, but you can change this
7427 by setting the environment variable @code{EDITOR} before using
7428 @value{GDBN}. For example, to configure @value{GDBN} to use the
7429 @code{vi} editor, you could use these commands with the @code{sh} shell:
7435 or in the @code{csh} shell,
7437 setenv EDITOR /usr/bin/vi
7442 @section Searching Source Files
7443 @cindex searching source files
7445 There are two commands for searching through the current source file for a
7450 @kindex forward-search
7451 @kindex fo @r{(@code{forward-search})}
7452 @item forward-search @var{regexp}
7453 @itemx search @var{regexp}
7454 The command @samp{forward-search @var{regexp}} checks each line,
7455 starting with the one following the last line listed, for a match for
7456 @var{regexp}. It lists the line that is found. You can use the
7457 synonym @samp{search @var{regexp}} or abbreviate the command name as
7460 @kindex reverse-search
7461 @item reverse-search @var{regexp}
7462 The command @samp{reverse-search @var{regexp}} checks each line, starting
7463 with the one before the last line listed and going backward, for a match
7464 for @var{regexp}. It lists the line that is found. You can abbreviate
7465 this command as @code{rev}.
7469 @section Specifying Source Directories
7472 @cindex directories for source files
7473 Executable programs sometimes do not record the directories of the source
7474 files from which they were compiled, just the names. Even when they do,
7475 the directories could be moved between the compilation and your debugging
7476 session. @value{GDBN} has a list of directories to search for source files;
7477 this is called the @dfn{source path}. Each time @value{GDBN} wants a source file,
7478 it tries all the directories in the list, in the order they are present
7479 in the list, until it finds a file with the desired name.
7481 For example, suppose an executable references the file
7482 @file{/usr/src/foo-1.0/lib/foo.c}, and our source path is
7483 @file{/mnt/cross}. The file is first looked up literally; if this
7484 fails, @file{/mnt/cross/usr/src/foo-1.0/lib/foo.c} is tried; if this
7485 fails, @file{/mnt/cross/foo.c} is opened; if this fails, an error
7486 message is printed. @value{GDBN} does not look up the parts of the
7487 source file name, such as @file{/mnt/cross/src/foo-1.0/lib/foo.c}.
7488 Likewise, the subdirectories of the source path are not searched: if
7489 the source path is @file{/mnt/cross}, and the binary refers to
7490 @file{foo.c}, @value{GDBN} would not find it under
7491 @file{/mnt/cross/usr/src/foo-1.0/lib}.
7493 Plain file names, relative file names with leading directories, file
7494 names containing dots, etc.@: are all treated as described above; for
7495 instance, if the source path is @file{/mnt/cross}, and the source file
7496 is recorded as @file{../lib/foo.c}, @value{GDBN} would first try
7497 @file{../lib/foo.c}, then @file{/mnt/cross/../lib/foo.c}, and after
7498 that---@file{/mnt/cross/foo.c}.
7500 Note that the executable search path is @emph{not} used to locate the
7503 Whenever you reset or rearrange the source path, @value{GDBN} clears out
7504 any information it has cached about where source files are found and where
7505 each line is in the file.
7509 When you start @value{GDBN}, its source path includes only @samp{cdir}
7510 and @samp{cwd}, in that order.
7511 To add other directories, use the @code{directory} command.
7513 The search path is used to find both program source files and @value{GDBN}
7514 script files (read using the @samp{-command} option and @samp{source} command).
7516 In addition to the source path, @value{GDBN} provides a set of commands
7517 that manage a list of source path substitution rules. A @dfn{substitution
7518 rule} specifies how to rewrite source directories stored in the program's
7519 debug information in case the sources were moved to a different
7520 directory between compilation and debugging. A rule is made of
7521 two strings, the first specifying what needs to be rewritten in
7522 the path, and the second specifying how it should be rewritten.
7523 In @ref{set substitute-path}, we name these two parts @var{from} and
7524 @var{to} respectively. @value{GDBN} does a simple string replacement
7525 of @var{from} with @var{to} at the start of the directory part of the
7526 source file name, and uses that result instead of the original file
7527 name to look up the sources.
7529 Using the previous example, suppose the @file{foo-1.0} tree has been
7530 moved from @file{/usr/src} to @file{/mnt/cross}, then you can tell
7531 @value{GDBN} to replace @file{/usr/src} in all source path names with
7532 @file{/mnt/cross}. The first lookup will then be
7533 @file{/mnt/cross/foo-1.0/lib/foo.c} in place of the original location
7534 of @file{/usr/src/foo-1.0/lib/foo.c}. To define a source path
7535 substitution rule, use the @code{set substitute-path} command
7536 (@pxref{set substitute-path}).
7538 To avoid unexpected substitution results, a rule is applied only if the
7539 @var{from} part of the directory name ends at a directory separator.
7540 For instance, a rule substituting @file{/usr/source} into
7541 @file{/mnt/cross} will be applied to @file{/usr/source/foo-1.0} but
7542 not to @file{/usr/sourceware/foo-2.0}. And because the substitution
7543 is applied only at the beginning of the directory name, this rule will
7544 not be applied to @file{/root/usr/source/baz.c} either.
7546 In many cases, you can achieve the same result using the @code{directory}
7547 command. However, @code{set substitute-path} can be more efficient in
7548 the case where the sources are organized in a complex tree with multiple
7549 subdirectories. With the @code{directory} command, you need to add each
7550 subdirectory of your project. If you moved the entire tree while
7551 preserving its internal organization, then @code{set substitute-path}
7552 allows you to direct the debugger to all the sources with one single
7555 @code{set substitute-path} is also more than just a shortcut command.
7556 The source path is only used if the file at the original location no
7557 longer exists. On the other hand, @code{set substitute-path} modifies
7558 the debugger behavior to look at the rewritten location instead. So, if
7559 for any reason a source file that is not relevant to your executable is
7560 located at the original location, a substitution rule is the only
7561 method available to point @value{GDBN} at the new location.
7563 @cindex @samp{--with-relocated-sources}
7564 @cindex default source path substitution
7565 You can configure a default source path substitution rule by
7566 configuring @value{GDBN} with the
7567 @samp{--with-relocated-sources=@var{dir}} option. The @var{dir}
7568 should be the name of a directory under @value{GDBN}'s configured
7569 prefix (set with @samp{--prefix} or @samp{--exec-prefix}), and
7570 directory names in debug information under @var{dir} will be adjusted
7571 automatically if the installed @value{GDBN} is moved to a new
7572 location. This is useful if @value{GDBN}, libraries or executables
7573 with debug information and corresponding source code are being moved
7577 @item directory @var{dirname} @dots{}
7578 @item dir @var{dirname} @dots{}
7579 Add directory @var{dirname} to the front of the source path. Several
7580 directory names may be given to this command, separated by @samp{:}
7581 (@samp{;} on MS-DOS and MS-Windows, where @samp{:} usually appears as
7582 part of absolute file names) or
7583 whitespace. You may specify a directory that is already in the source
7584 path; this moves it forward, so @value{GDBN} searches it sooner.
7588 @vindex $cdir@r{, convenience variable}
7589 @vindex $cwd@r{, convenience variable}
7590 @cindex compilation directory
7591 @cindex current directory
7592 @cindex working directory
7593 @cindex directory, current
7594 @cindex directory, compilation
7595 You can use the string @samp{$cdir} to refer to the compilation
7596 directory (if one is recorded), and @samp{$cwd} to refer to the current
7597 working directory. @samp{$cwd} is not the same as @samp{.}---the former
7598 tracks the current working directory as it changes during your @value{GDBN}
7599 session, while the latter is immediately expanded to the current
7600 directory at the time you add an entry to the source path.
7603 Reset the source path to its default value (@samp{$cdir:$cwd} on Unix systems). This requires confirmation.
7605 @c RET-repeat for @code{directory} is explicitly disabled, but since
7606 @c repeating it would be a no-op we do not say that. (thanks to RMS)
7608 @item set directories @var{path-list}
7609 @kindex set directories
7610 Set the source path to @var{path-list}.
7611 @samp{$cdir:$cwd} are added if missing.
7613 @item show directories
7614 @kindex show directories
7615 Print the source path: show which directories it contains.
7617 @anchor{set substitute-path}
7618 @item set substitute-path @var{from} @var{to}
7619 @kindex set substitute-path
7620 Define a source path substitution rule, and add it at the end of the
7621 current list of existing substitution rules. If a rule with the same
7622 @var{from} was already defined, then the old rule is also deleted.
7624 For example, if the file @file{/foo/bar/baz.c} was moved to
7625 @file{/mnt/cross/baz.c}, then the command
7628 (@value{GDBP}) set substitute-path /usr/src /mnt/cross
7632 will tell @value{GDBN} to replace @samp{/usr/src} with
7633 @samp{/mnt/cross}, which will allow @value{GDBN} to find the file
7634 @file{baz.c} even though it was moved.
7636 In the case when more than one substitution rule have been defined,
7637 the rules are evaluated one by one in the order where they have been
7638 defined. The first one matching, if any, is selected to perform
7641 For instance, if we had entered the following commands:
7644 (@value{GDBP}) set substitute-path /usr/src/include /mnt/include
7645 (@value{GDBP}) set substitute-path /usr/src /mnt/src
7649 @value{GDBN} would then rewrite @file{/usr/src/include/defs.h} into
7650 @file{/mnt/include/defs.h} by using the first rule. However, it would
7651 use the second rule to rewrite @file{/usr/src/lib/foo.c} into
7652 @file{/mnt/src/lib/foo.c}.
7655 @item unset substitute-path [path]
7656 @kindex unset substitute-path
7657 If a path is specified, search the current list of substitution rules
7658 for a rule that would rewrite that path. Delete that rule if found.
7659 A warning is emitted by the debugger if no rule could be found.
7661 If no path is specified, then all substitution rules are deleted.
7663 @item show substitute-path [path]
7664 @kindex show substitute-path
7665 If a path is specified, then print the source path substitution rule
7666 which would rewrite that path, if any.
7668 If no path is specified, then print all existing source path substitution
7673 If your source path is cluttered with directories that are no longer of
7674 interest, @value{GDBN} may sometimes cause confusion by finding the wrong
7675 versions of source. You can correct the situation as follows:
7679 Use @code{directory} with no argument to reset the source path to its default value.
7682 Use @code{directory} with suitable arguments to reinstall the
7683 directories you want in the source path. You can add all the
7684 directories in one command.
7688 @section Source and Machine Code
7689 @cindex source line and its code address
7691 You can use the command @code{info line} to map source lines to program
7692 addresses (and vice versa), and the command @code{disassemble} to display
7693 a range of addresses as machine instructions. You can use the command
7694 @code{set disassemble-next-line} to set whether to disassemble next
7695 source line when execution stops. When run under @sc{gnu} Emacs
7696 mode, the @code{info line} command causes the arrow to point to the
7697 line specified. Also, @code{info line} prints addresses in symbolic form as
7702 @item info line @var{linespec}
7703 Print the starting and ending addresses of the compiled code for
7704 source line @var{linespec}. You can specify source lines in any of
7705 the ways documented in @ref{Specify Location}.
7708 For example, we can use @code{info line} to discover the location of
7709 the object code for the first line of function
7710 @code{m4_changequote}:
7712 @c FIXME: I think this example should also show the addresses in
7713 @c symbolic form, as they usually would be displayed.
7715 (@value{GDBP}) info line m4_changequote
7716 Line 895 of "builtin.c" starts at pc 0x634c and ends at 0x6350.
7720 @cindex code address and its source line
7721 We can also inquire (using @code{*@var{addr}} as the form for
7722 @var{linespec}) what source line covers a particular address:
7724 (@value{GDBP}) info line *0x63ff
7725 Line 926 of "builtin.c" starts at pc 0x63e4 and ends at 0x6404.
7728 @cindex @code{$_} and @code{info line}
7729 @cindex @code{x} command, default address
7730 @kindex x@r{(examine), and} info line
7731 After @code{info line}, the default address for the @code{x} command
7732 is changed to the starting address of the line, so that @samp{x/i} is
7733 sufficient to begin examining the machine code (@pxref{Memory,
7734 ,Examining Memory}). Also, this address is saved as the value of the
7735 convenience variable @code{$_} (@pxref{Convenience Vars, ,Convenience
7740 @cindex assembly instructions
7741 @cindex instructions, assembly
7742 @cindex machine instructions
7743 @cindex listing machine instructions
7745 @itemx disassemble /m
7746 @itemx disassemble /r
7747 This specialized command dumps a range of memory as machine
7748 instructions. It can also print mixed source+disassembly by specifying
7749 the @code{/m} modifier and print the raw instructions in hex as well as
7750 in symbolic form by specifying the @code{/r}.
7751 The default memory range is the function surrounding the
7752 program counter of the selected frame. A single argument to this
7753 command is a program counter value; @value{GDBN} dumps the function
7754 surrounding this value. When two arguments are given, they should
7755 be separated by a comma, possibly surrounded by whitespace. The
7756 arguments specify a range of addresses to dump, in one of two forms:
7759 @item @var{start},@var{end}
7760 the addresses from @var{start} (inclusive) to @var{end} (exclusive)
7761 @item @var{start},+@var{length}
7762 the addresses from @var{start} (inclusive) to
7763 @code{@var{start}+@var{length}} (exclusive).
7767 When 2 arguments are specified, the name of the function is also
7768 printed (since there could be several functions in the given range).
7770 The argument(s) can be any expression yielding a numeric value, such as
7771 @samp{0x32c4}, @samp{&main+10} or @samp{$pc - 8}.
7773 If the range of memory being disassembled contains current program counter,
7774 the instruction at that location is shown with a @code{=>} marker.
7777 The following example shows the disassembly of a range of addresses of
7778 HP PA-RISC 2.0 code:
7781 (@value{GDBP}) disas 0x32c4, 0x32e4
7782 Dump of assembler code from 0x32c4 to 0x32e4:
7783 0x32c4 <main+204>: addil 0,dp
7784 0x32c8 <main+208>: ldw 0x22c(sr0,r1),r26
7785 0x32cc <main+212>: ldil 0x3000,r31
7786 0x32d0 <main+216>: ble 0x3f8(sr4,r31)
7787 0x32d4 <main+220>: ldo 0(r31),rp
7788 0x32d8 <main+224>: addil -0x800,dp
7789 0x32dc <main+228>: ldo 0x588(r1),r26
7790 0x32e0 <main+232>: ldil 0x3000,r31
7791 End of assembler dump.
7794 Here is an example showing mixed source+assembly for Intel x86, when the
7795 program is stopped just after function prologue:
7798 (@value{GDBP}) disas /m main
7799 Dump of assembler code for function main:
7801 0x08048330 <+0>: push %ebp
7802 0x08048331 <+1>: mov %esp,%ebp
7803 0x08048333 <+3>: sub $0x8,%esp
7804 0x08048336 <+6>: and $0xfffffff0,%esp
7805 0x08048339 <+9>: sub $0x10,%esp
7807 6 printf ("Hello.\n");
7808 => 0x0804833c <+12>: movl $0x8048440,(%esp)
7809 0x08048343 <+19>: call 0x8048284 <puts@@plt>
7813 0x08048348 <+24>: mov $0x0,%eax
7814 0x0804834d <+29>: leave
7815 0x0804834e <+30>: ret
7817 End of assembler dump.
7820 Here is another example showing raw instructions in hex for AMD x86-64,
7823 (gdb) disas /r 0x400281,+10
7824 Dump of assembler code from 0x400281 to 0x40028b:
7825 0x0000000000400281: 38 36 cmp %dh,(%rsi)
7826 0x0000000000400283: 2d 36 34 2e 73 sub $0x732e3436,%eax
7827 0x0000000000400288: 6f outsl %ds:(%rsi),(%dx)
7828 0x0000000000400289: 2e 32 00 xor %cs:(%rax),%al
7829 End of assembler dump.
7832 Addresses cannot be specified as a linespec (@pxref{Specify Location}).
7833 So, for example, if you want to disassemble function @code{bar}
7834 in file @file{foo.c}, you must type @samp{disassemble 'foo.c'::bar}
7835 and not @samp{disassemble foo.c:bar}.
7837 Some architectures have more than one commonly-used set of instruction
7838 mnemonics or other syntax.
7840 For programs that were dynamically linked and use shared libraries,
7841 instructions that call functions or branch to locations in the shared
7842 libraries might show a seemingly bogus location---it's actually a
7843 location of the relocation table. On some architectures, @value{GDBN}
7844 might be able to resolve these to actual function names.
7847 @kindex set disassembly-flavor
7848 @cindex Intel disassembly flavor
7849 @cindex AT&T disassembly flavor
7850 @item set disassembly-flavor @var{instruction-set}
7851 Select the instruction set to use when disassembling the
7852 program via the @code{disassemble} or @code{x/i} commands.
7854 Currently this command is only defined for the Intel x86 family. You
7855 can set @var{instruction-set} to either @code{intel} or @code{att}.
7856 The default is @code{att}, the AT&T flavor used by default by Unix
7857 assemblers for x86-based targets.
7859 @kindex show disassembly-flavor
7860 @item show disassembly-flavor
7861 Show the current setting of the disassembly flavor.
7865 @kindex set disassemble-next-line
7866 @kindex show disassemble-next-line
7867 @item set disassemble-next-line
7868 @itemx show disassemble-next-line
7869 Control whether or not @value{GDBN} will disassemble the next source
7870 line or instruction when execution stops. If ON, @value{GDBN} will
7871 display disassembly of the next source line when execution of the
7872 program being debugged stops. This is @emph{in addition} to
7873 displaying the source line itself, which @value{GDBN} always does if
7874 possible. If the next source line cannot be displayed for some reason
7875 (e.g., if @value{GDBN} cannot find the source file, or there's no line
7876 info in the debug info), @value{GDBN} will display disassembly of the
7877 next @emph{instruction} instead of showing the next source line. If
7878 AUTO, @value{GDBN} will display disassembly of next instruction only
7879 if the source line cannot be displayed. This setting causes
7880 @value{GDBN} to display some feedback when you step through a function
7881 with no line info or whose source file is unavailable. The default is
7882 OFF, which means never display the disassembly of the next line or
7888 @chapter Examining Data
7890 @cindex printing data
7891 @cindex examining data
7894 The usual way to examine data in your program is with the @code{print}
7895 command (abbreviated @code{p}), or its synonym @code{inspect}. It
7896 evaluates and prints the value of an expression of the language your
7897 program is written in (@pxref{Languages, ,Using @value{GDBN} with
7898 Different Languages}). It may also print the expression using a
7899 Python-based pretty-printer (@pxref{Pretty Printing}).
7902 @item print @var{expr}
7903 @itemx print /@var{f} @var{expr}
7904 @var{expr} is an expression (in the source language). By default the
7905 value of @var{expr} is printed in a format appropriate to its data type;
7906 you can choose a different format by specifying @samp{/@var{f}}, where
7907 @var{f} is a letter specifying the format; see @ref{Output Formats,,Output
7911 @itemx print /@var{f}
7912 @cindex reprint the last value
7913 If you omit @var{expr}, @value{GDBN} displays the last value again (from the
7914 @dfn{value history}; @pxref{Value History, ,Value History}). This allows you to
7915 conveniently inspect the same value in an alternative format.
7918 A more low-level way of examining data is with the @code{x} command.
7919 It examines data in memory at a specified address and prints it in a
7920 specified format. @xref{Memory, ,Examining Memory}.
7922 If you are interested in information about types, or about how the
7923 fields of a struct or a class are declared, use the @code{ptype @var{exp}}
7924 command rather than @code{print}. @xref{Symbols, ,Examining the Symbol
7927 @cindex exploring hierarchical data structures
7929 Another way of examining values of expressions and type information is
7930 through the Python extension command @code{explore} (available only if
7931 the @value{GDBN} build is configured with @code{--with-python}). It
7932 offers an interactive way to start at the highest level (or, the most
7933 abstract level) of the data type of an expression (or, the data type
7934 itself) and explore all the way down to leaf scalar values/fields
7935 embedded in the higher level data types.
7938 @item explore @var{arg}
7939 @var{arg} is either an expression (in the source language), or a type
7940 visible in the current context of the program being debugged.
7943 The working of the @code{explore} command can be illustrated with an
7944 example. If a data type @code{struct ComplexStruct} is defined in your
7954 struct ComplexStruct
7956 struct SimpleStruct *ss_p;
7962 followed by variable declarations as
7965 struct SimpleStruct ss = @{ 10, 1.11 @};
7966 struct ComplexStruct cs = @{ &ss, @{ 0, 1, 2, 3, 4, 5, 6, 7, 8, 9 @} @};
7970 then, the value of the variable @code{cs} can be explored using the
7971 @code{explore} command as follows.
7975 The value of `cs' is a struct/class of type `struct ComplexStruct' with
7976 the following fields:
7978 ss_p = <Enter 0 to explore this field of type `struct SimpleStruct *'>
7979 arr = <Enter 1 to explore this field of type `int [10]'>
7981 Enter the field number of choice:
7985 Since the fields of @code{cs} are not scalar values, you are being
7986 prompted to chose the field you want to explore. Let's say you choose
7987 the field @code{ss_p} by entering @code{0}. Then, since this field is a
7988 pointer, you will be asked if it is pointing to a single value. From
7989 the declaration of @code{cs} above, it is indeed pointing to a single
7990 value, hence you enter @code{y}. If you enter @code{n}, then you will
7991 be asked if it were pointing to an array of values, in which case this
7992 field will be explored as if it were an array.
7995 `cs.ss_p' is a pointer to a value of type `struct SimpleStruct'
7996 Continue exploring it as a pointer to a single value [y/n]: y
7997 The value of `*(cs.ss_p)' is a struct/class of type `struct
7998 SimpleStruct' with the following fields:
8000 i = 10 .. (Value of type `int')
8001 d = 1.1100000000000001 .. (Value of type `double')
8003 Press enter to return to parent value:
8007 If the field @code{arr} of @code{cs} was chosen for exploration by
8008 entering @code{1} earlier, then since it is as array, you will be
8009 prompted to enter the index of the element in the array that you want
8013 `cs.arr' is an array of `int'.
8014 Enter the index of the element you want to explore in `cs.arr': 5
8016 `(cs.arr)[5]' is a scalar value of type `int'.
8020 Press enter to return to parent value:
8023 In general, at any stage of exploration, you can go deeper towards the
8024 leaf values by responding to the prompts appropriately, or hit the
8025 return key to return to the enclosing data structure (the @i{higher}
8026 level data structure).
8028 Similar to exploring values, you can use the @code{explore} command to
8029 explore types. Instead of specifying a value (which is typically a
8030 variable name or an expression valid in the current context of the
8031 program being debugged), you specify a type name. If you consider the
8032 same example as above, your can explore the type
8033 @code{struct ComplexStruct} by passing the argument
8034 @code{struct ComplexStruct} to the @code{explore} command.
8037 (gdb) explore struct ComplexStruct
8041 By responding to the prompts appropriately in the subsequent interactive
8042 session, you can explore the type @code{struct ComplexStruct} in a
8043 manner similar to how the value @code{cs} was explored in the above
8046 The @code{explore} command also has two sub-commands,
8047 @code{explore value} and @code{explore type}. The former sub-command is
8048 a way to explicitly specify that value exploration of the argument is
8049 being invoked, while the latter is a way to explicitly specify that type
8050 exploration of the argument is being invoked.
8053 @item explore value @var{expr}
8054 @cindex explore value
8055 This sub-command of @code{explore} explores the value of the
8056 expression @var{expr} (if @var{expr} is an expression valid in the
8057 current context of the program being debugged). The behavior of this
8058 command is identical to that of the behavior of the @code{explore}
8059 command being passed the argument @var{expr}.
8061 @item explore type @var{arg}
8062 @cindex explore type
8063 This sub-command of @code{explore} explores the type of @var{arg} (if
8064 @var{arg} is a type visible in the current context of program being
8065 debugged), or the type of the value/expression @var{arg} (if @var{arg}
8066 is an expression valid in the current context of the program being
8067 debugged). If @var{arg} is a type, then the behavior of this command is
8068 identical to that of the @code{explore} command being passed the
8069 argument @var{arg}. If @var{arg} is an expression, then the behavior of
8070 this command will be identical to that of the @code{explore} command
8071 being passed the type of @var{arg} as the argument.
8075 * Expressions:: Expressions
8076 * Ambiguous Expressions:: Ambiguous Expressions
8077 * Variables:: Program variables
8078 * Arrays:: Artificial arrays
8079 * Output Formats:: Output formats
8080 * Memory:: Examining memory
8081 * Auto Display:: Automatic display
8082 * Print Settings:: Print settings
8083 * Pretty Printing:: Python pretty printing
8084 * Value History:: Value history
8085 * Convenience Vars:: Convenience variables
8086 * Convenience Funs:: Convenience functions
8087 * Registers:: Registers
8088 * Floating Point Hardware:: Floating point hardware
8089 * Vector Unit:: Vector Unit
8090 * OS Information:: Auxiliary data provided by operating system
8091 * Memory Region Attributes:: Memory region attributes
8092 * Dump/Restore Files:: Copy between memory and a file
8093 * Core File Generation:: Cause a program dump its core
8094 * Character Sets:: Debugging programs that use a different
8095 character set than GDB does
8096 * Caching Target Data:: Data caching for targets
8097 * Searching Memory:: Searching memory for a sequence of bytes
8101 @section Expressions
8104 @code{print} and many other @value{GDBN} commands accept an expression and
8105 compute its value. Any kind of constant, variable or operator defined
8106 by the programming language you are using is valid in an expression in
8107 @value{GDBN}. This includes conditional expressions, function calls,
8108 casts, and string constants. It also includes preprocessor macros, if
8109 you compiled your program to include this information; see
8112 @cindex arrays in expressions
8113 @value{GDBN} supports array constants in expressions input by
8114 the user. The syntax is @{@var{element}, @var{element}@dots{}@}. For example,
8115 you can use the command @code{print @{1, 2, 3@}} to create an array
8116 of three integers. If you pass an array to a function or assign it
8117 to a program variable, @value{GDBN} copies the array to memory that
8118 is @code{malloc}ed in the target program.
8120 Because C is so widespread, most of the expressions shown in examples in
8121 this manual are in C. @xref{Languages, , Using @value{GDBN} with Different
8122 Languages}, for information on how to use expressions in other
8125 In this section, we discuss operators that you can use in @value{GDBN}
8126 expressions regardless of your programming language.
8128 @cindex casts, in expressions
8129 Casts are supported in all languages, not just in C, because it is so
8130 useful to cast a number into a pointer in order to examine a structure
8131 at that address in memory.
8132 @c FIXME: casts supported---Mod2 true?
8134 @value{GDBN} supports these operators, in addition to those common
8135 to programming languages:
8139 @samp{@@} is a binary operator for treating parts of memory as arrays.
8140 @xref{Arrays, ,Artificial Arrays}, for more information.
8143 @samp{::} allows you to specify a variable in terms of the file or
8144 function where it is defined. @xref{Variables, ,Program Variables}.
8146 @cindex @{@var{type}@}
8147 @cindex type casting memory
8148 @cindex memory, viewing as typed object
8149 @cindex casts, to view memory
8150 @item @{@var{type}@} @var{addr}
8151 Refers to an object of type @var{type} stored at address @var{addr} in
8152 memory. @var{addr} may be any expression whose value is an integer or
8153 pointer (but parentheses are required around binary operators, just as in
8154 a cast). This construct is allowed regardless of what kind of data is
8155 normally supposed to reside at @var{addr}.
8158 @node Ambiguous Expressions
8159 @section Ambiguous Expressions
8160 @cindex ambiguous expressions
8162 Expressions can sometimes contain some ambiguous elements. For instance,
8163 some programming languages (notably Ada, C@t{++} and Objective-C) permit
8164 a single function name to be defined several times, for application in
8165 different contexts. This is called @dfn{overloading}. Another example
8166 involving Ada is generics. A @dfn{generic package} is similar to C@t{++}
8167 templates and is typically instantiated several times, resulting in
8168 the same function name being defined in different contexts.
8170 In some cases and depending on the language, it is possible to adjust
8171 the expression to remove the ambiguity. For instance in C@t{++}, you
8172 can specify the signature of the function you want to break on, as in
8173 @kbd{break @var{function}(@var{types})}. In Ada, using the fully
8174 qualified name of your function often makes the expression unambiguous
8177 When an ambiguity that needs to be resolved is detected, the debugger
8178 has the capability to display a menu of numbered choices for each
8179 possibility, and then waits for the selection with the prompt @samp{>}.
8180 The first option is always @samp{[0] cancel}, and typing @kbd{0 @key{RET}}
8181 aborts the current command. If the command in which the expression was
8182 used allows more than one choice to be selected, the next option in the
8183 menu is @samp{[1] all}, and typing @kbd{1 @key{RET}} selects all possible
8186 For example, the following session excerpt shows an attempt to set a
8187 breakpoint at the overloaded symbol @code{String::after}.
8188 We choose three particular definitions of that function name:
8190 @c FIXME! This is likely to change to show arg type lists, at least
8193 (@value{GDBP}) b String::after
8196 [2] file:String.cc; line number:867
8197 [3] file:String.cc; line number:860
8198 [4] file:String.cc; line number:875
8199 [5] file:String.cc; line number:853
8200 [6] file:String.cc; line number:846
8201 [7] file:String.cc; line number:735
8203 Breakpoint 1 at 0xb26c: file String.cc, line 867.
8204 Breakpoint 2 at 0xb344: file String.cc, line 875.
8205 Breakpoint 3 at 0xafcc: file String.cc, line 846.
8206 Multiple breakpoints were set.
8207 Use the "delete" command to delete unwanted
8214 @kindex set multiple-symbols
8215 @item set multiple-symbols @var{mode}
8216 @cindex multiple-symbols menu
8218 This option allows you to adjust the debugger behavior when an expression
8221 By default, @var{mode} is set to @code{all}. If the command with which
8222 the expression is used allows more than one choice, then @value{GDBN}
8223 automatically selects all possible choices. For instance, inserting
8224 a breakpoint on a function using an ambiguous name results in a breakpoint
8225 inserted on each possible match. However, if a unique choice must be made,
8226 then @value{GDBN} uses the menu to help you disambiguate the expression.
8227 For instance, printing the address of an overloaded function will result
8228 in the use of the menu.
8230 When @var{mode} is set to @code{ask}, the debugger always uses the menu
8231 when an ambiguity is detected.
8233 Finally, when @var{mode} is set to @code{cancel}, the debugger reports
8234 an error due to the ambiguity and the command is aborted.
8236 @kindex show multiple-symbols
8237 @item show multiple-symbols
8238 Show the current value of the @code{multiple-symbols} setting.
8242 @section Program Variables
8244 The most common kind of expression to use is the name of a variable
8247 Variables in expressions are understood in the selected stack frame
8248 (@pxref{Selection, ,Selecting a Frame}); they must be either:
8252 global (or file-static)
8259 visible according to the scope rules of the
8260 programming language from the point of execution in that frame
8263 @noindent This means that in the function
8278 you can examine and use the variable @code{a} whenever your program is
8279 executing within the function @code{foo}, but you can only use or
8280 examine the variable @code{b} while your program is executing inside
8281 the block where @code{b} is declared.
8283 @cindex variable name conflict
8284 There is an exception: you can refer to a variable or function whose
8285 scope is a single source file even if the current execution point is not
8286 in this file. But it is possible to have more than one such variable or
8287 function with the same name (in different source files). If that
8288 happens, referring to that name has unpredictable effects. If you wish,
8289 you can specify a static variable in a particular function or file by
8290 using the colon-colon (@code{::}) notation:
8292 @cindex colon-colon, context for variables/functions
8294 @c info cannot cope with a :: index entry, but why deprive hard copy readers?
8295 @cindex @code{::}, context for variables/functions
8298 @var{file}::@var{variable}
8299 @var{function}::@var{variable}
8303 Here @var{file} or @var{function} is the name of the context for the
8304 static @var{variable}. In the case of file names, you can use quotes to
8305 make sure @value{GDBN} parses the file name as a single word---for example,
8306 to print a global value of @code{x} defined in @file{f2.c}:
8309 (@value{GDBP}) p 'f2.c'::x
8312 The @code{::} notation is normally used for referring to
8313 static variables, since you typically disambiguate uses of local variables
8314 in functions by selecting the appropriate frame and using the
8315 simple name of the variable. However, you may also use this notation
8316 to refer to local variables in frames enclosing the selected frame:
8325 process (a); /* Stop here */
8336 For example, if there is a breakpoint at the commented line,
8337 here is what you might see
8338 when the program stops after executing the call @code{bar(0)}:
8343 (@value{GDBP}) p bar::a
8346 #2 0x080483d0 in foo (a=5) at foobar.c:12
8349 (@value{GDBP}) p bar::a
8353 @cindex C@t{++} scope resolution
8354 These uses of @samp{::} are very rarely in conflict with the very
8355 similar use of the same notation in C@t{++}. When they are in
8356 conflict, the C@t{++} meaning takes precedence; however, this can be
8357 overridden by quoting the file or function name with single quotes.
8359 For example, suppose the program is stopped in a method of a class
8360 that has a field named @code{includefile}, and there is also an
8361 include file named @file{includefile} that defines a variable,
8365 (@value{GDBP}) p includefile
8367 (@value{GDBP}) p includefile::some_global
8368 A syntax error in expression, near `'.
8369 (@value{GDBP}) p 'includefile'::some_global
8373 @cindex wrong values
8374 @cindex variable values, wrong
8375 @cindex function entry/exit, wrong values of variables
8376 @cindex optimized code, wrong values of variables
8378 @emph{Warning:} Occasionally, a local variable may appear to have the
8379 wrong value at certain points in a function---just after entry to a new
8380 scope, and just before exit.
8382 You may see this problem when you are stepping by machine instructions.
8383 This is because, on most machines, it takes more than one instruction to
8384 set up a stack frame (including local variable definitions); if you are
8385 stepping by machine instructions, variables may appear to have the wrong
8386 values until the stack frame is completely built. On exit, it usually
8387 also takes more than one machine instruction to destroy a stack frame;
8388 after you begin stepping through that group of instructions, local
8389 variable definitions may be gone.
8391 This may also happen when the compiler does significant optimizations.
8392 To be sure of always seeing accurate values, turn off all optimization
8395 @cindex ``No symbol "foo" in current context''
8396 Another possible effect of compiler optimizations is to optimize
8397 unused variables out of existence, or assign variables to registers (as
8398 opposed to memory addresses). Depending on the support for such cases
8399 offered by the debug info format used by the compiler, @value{GDBN}
8400 might not be able to display values for such local variables. If that
8401 happens, @value{GDBN} will print a message like this:
8404 No symbol "foo" in current context.
8407 To solve such problems, either recompile without optimizations, or use a
8408 different debug info format, if the compiler supports several such
8409 formats. @xref{Compilation}, for more information on choosing compiler
8410 options. @xref{C, ,C and C@t{++}}, for more information about debug
8411 info formats that are best suited to C@t{++} programs.
8413 If you ask to print an object whose contents are unknown to
8414 @value{GDBN}, e.g., because its data type is not completely specified
8415 by the debug information, @value{GDBN} will say @samp{<incomplete
8416 type>}. @xref{Symbols, incomplete type}, for more about this.
8418 If you append @kbd{@@entry} string to a function parameter name you get its
8419 value at the time the function got called. If the value is not available an
8420 error message is printed. Entry values are available only with some compilers.
8421 Entry values are normally also printed at the function parameter list according
8422 to @ref{set print entry-values}.
8425 Breakpoint 1, d (i=30) at gdb.base/entry-value.c:29
8431 (gdb) print i@@entry
8435 Strings are identified as arrays of @code{char} values without specified
8436 signedness. Arrays of either @code{signed char} or @code{unsigned char} get
8437 printed as arrays of 1 byte sized integers. @code{-fsigned-char} or
8438 @code{-funsigned-char} @value{NGCC} options have no effect as @value{GDBN}
8439 defines literal string type @code{"char"} as @code{char} without a sign.
8444 signed char var1[] = "A";
8447 You get during debugging
8452 $2 = @{65 'A', 0 '\0'@}
8456 @section Artificial Arrays
8458 @cindex artificial array
8460 @kindex @@@r{, referencing memory as an array}
8461 It is often useful to print out several successive objects of the
8462 same type in memory; a section of an array, or an array of
8463 dynamically determined size for which only a pointer exists in the
8466 You can do this by referring to a contiguous span of memory as an
8467 @dfn{artificial array}, using the binary operator @samp{@@}. The left
8468 operand of @samp{@@} should be the first element of the desired array
8469 and be an individual object. The right operand should be the desired length
8470 of the array. The result is an array value whose elements are all of
8471 the type of the left argument. The first element is actually the left
8472 argument; the second element comes from bytes of memory immediately
8473 following those that hold the first element, and so on. Here is an
8474 example. If a program says
8477 int *array = (int *) malloc (len * sizeof (int));
8481 you can print the contents of @code{array} with
8487 The left operand of @samp{@@} must reside in memory. Array values made
8488 with @samp{@@} in this way behave just like other arrays in terms of
8489 subscripting, and are coerced to pointers when used in expressions.
8490 Artificial arrays most often appear in expressions via the value history
8491 (@pxref{Value History, ,Value History}), after printing one out.
8493 Another way to create an artificial array is to use a cast.
8494 This re-interprets a value as if it were an array.
8495 The value need not be in memory:
8497 (@value{GDBP}) p/x (short[2])0x12345678
8498 $1 = @{0x1234, 0x5678@}
8501 As a convenience, if you leave the array length out (as in
8502 @samp{(@var{type}[])@var{value}}) @value{GDBN} calculates the size to fill
8503 the value (as @samp{sizeof(@var{value})/sizeof(@var{type})}:
8505 (@value{GDBP}) p/x (short[])0x12345678
8506 $2 = @{0x1234, 0x5678@}
8509 Sometimes the artificial array mechanism is not quite enough; in
8510 moderately complex data structures, the elements of interest may not
8511 actually be adjacent---for example, if you are interested in the values
8512 of pointers in an array. One useful work-around in this situation is
8513 to use a convenience variable (@pxref{Convenience Vars, ,Convenience
8514 Variables}) as a counter in an expression that prints the first
8515 interesting value, and then repeat that expression via @key{RET}. For
8516 instance, suppose you have an array @code{dtab} of pointers to
8517 structures, and you are interested in the values of a field @code{fv}
8518 in each structure. Here is an example of what you might type:
8528 @node Output Formats
8529 @section Output Formats
8531 @cindex formatted output
8532 @cindex output formats
8533 By default, @value{GDBN} prints a value according to its data type. Sometimes
8534 this is not what you want. For example, you might want to print a number
8535 in hex, or a pointer in decimal. Or you might want to view data in memory
8536 at a certain address as a character string or as an instruction. To do
8537 these things, specify an @dfn{output format} when you print a value.
8539 The simplest use of output formats is to say how to print a value
8540 already computed. This is done by starting the arguments of the
8541 @code{print} command with a slash and a format letter. The format
8542 letters supported are:
8546 Regard the bits of the value as an integer, and print the integer in
8550 Print as integer in signed decimal.
8553 Print as integer in unsigned decimal.
8556 Print as integer in octal.
8559 Print as integer in binary. The letter @samp{t} stands for ``two''.
8560 @footnote{@samp{b} cannot be used because these format letters are also
8561 used with the @code{x} command, where @samp{b} stands for ``byte'';
8562 see @ref{Memory,,Examining Memory}.}
8565 @cindex unknown address, locating
8566 @cindex locate address
8567 Print as an address, both absolute in hexadecimal and as an offset from
8568 the nearest preceding symbol. You can use this format used to discover
8569 where (in what function) an unknown address is located:
8572 (@value{GDBP}) p/a 0x54320
8573 $3 = 0x54320 <_initialize_vx+396>
8577 The command @code{info symbol 0x54320} yields similar results.
8578 @xref{Symbols, info symbol}.
8581 Regard as an integer and print it as a character constant. This
8582 prints both the numerical value and its character representation. The
8583 character representation is replaced with the octal escape @samp{\nnn}
8584 for characters outside the 7-bit @sc{ascii} range.
8586 Without this format, @value{GDBN} displays @code{char},
8587 @w{@code{unsigned char}}, and @w{@code{signed char}} data as character
8588 constants. Single-byte members of vectors are displayed as integer
8592 Regard the bits of the value as a floating point number and print
8593 using typical floating point syntax.
8596 @cindex printing strings
8597 @cindex printing byte arrays
8598 Regard as a string, if possible. With this format, pointers to single-byte
8599 data are displayed as null-terminated strings and arrays of single-byte data
8600 are displayed as fixed-length strings. Other values are displayed in their
8603 Without this format, @value{GDBN} displays pointers to and arrays of
8604 @code{char}, @w{@code{unsigned char}}, and @w{@code{signed char}} as
8605 strings. Single-byte members of a vector are displayed as an integer
8609 Like @samp{x} formatting, the value is treated as an integer and
8610 printed as hexadecimal, but leading zeros are printed to pad the value
8611 to the size of the integer type.
8614 @cindex raw printing
8615 Print using the @samp{raw} formatting. By default, @value{GDBN} will
8616 use a Python-based pretty-printer, if one is available (@pxref{Pretty
8617 Printing}). This typically results in a higher-level display of the
8618 value's contents. The @samp{r} format bypasses any Python
8619 pretty-printer which might exist.
8622 For example, to print the program counter in hex (@pxref{Registers}), type
8629 Note that no space is required before the slash; this is because command
8630 names in @value{GDBN} cannot contain a slash.
8632 To reprint the last value in the value history with a different format,
8633 you can use the @code{print} command with just a format and no
8634 expression. For example, @samp{p/x} reprints the last value in hex.
8637 @section Examining Memory
8639 You can use the command @code{x} (for ``examine'') to examine memory in
8640 any of several formats, independently of your program's data types.
8642 @cindex examining memory
8644 @kindex x @r{(examine memory)}
8645 @item x/@var{nfu} @var{addr}
8648 Use the @code{x} command to examine memory.
8651 @var{n}, @var{f}, and @var{u} are all optional parameters that specify how
8652 much memory to display and how to format it; @var{addr} is an
8653 expression giving the address where you want to start displaying memory.
8654 If you use defaults for @var{nfu}, you need not type the slash @samp{/}.
8655 Several commands set convenient defaults for @var{addr}.
8658 @item @var{n}, the repeat count
8659 The repeat count is a decimal integer; the default is 1. It specifies
8660 how much memory (counting by units @var{u}) to display.
8661 @c This really is **decimal**; unaffected by 'set radix' as of GDB
8664 @item @var{f}, the display format
8665 The display format is one of the formats used by @code{print}
8666 (@samp{x}, @samp{d}, @samp{u}, @samp{o}, @samp{t}, @samp{a}, @samp{c},
8667 @samp{f}, @samp{s}), and in addition @samp{i} (for machine instructions).
8668 The default is @samp{x} (hexadecimal) initially. The default changes
8669 each time you use either @code{x} or @code{print}.
8671 @item @var{u}, the unit size
8672 The unit size is any of
8678 Halfwords (two bytes).
8680 Words (four bytes). This is the initial default.
8682 Giant words (eight bytes).
8685 Each time you specify a unit size with @code{x}, that size becomes the
8686 default unit the next time you use @code{x}. For the @samp{i} format,
8687 the unit size is ignored and is normally not written. For the @samp{s} format,
8688 the unit size defaults to @samp{b}, unless it is explicitly given.
8689 Use @kbd{x /hs} to display 16-bit char strings and @kbd{x /ws} to display
8690 32-bit strings. The next use of @kbd{x /s} will again display 8-bit strings.
8691 Note that the results depend on the programming language of the
8692 current compilation unit. If the language is C, the @samp{s}
8693 modifier will use the UTF-16 encoding while @samp{w} will use
8694 UTF-32. The encoding is set by the programming language and cannot
8697 @item @var{addr}, starting display address
8698 @var{addr} is the address where you want @value{GDBN} to begin displaying
8699 memory. The expression need not have a pointer value (though it may);
8700 it is always interpreted as an integer address of a byte of memory.
8701 @xref{Expressions, ,Expressions}, for more information on expressions. The default for
8702 @var{addr} is usually just after the last address examined---but several
8703 other commands also set the default address: @code{info breakpoints} (to
8704 the address of the last breakpoint listed), @code{info line} (to the
8705 starting address of a line), and @code{print} (if you use it to display
8706 a value from memory).
8709 For example, @samp{x/3uh 0x54320} is a request to display three halfwords
8710 (@code{h}) of memory, formatted as unsigned decimal integers (@samp{u}),
8711 starting at address @code{0x54320}. @samp{x/4xw $sp} prints the four
8712 words (@samp{w}) of memory above the stack pointer (here, @samp{$sp};
8713 @pxref{Registers, ,Registers}) in hexadecimal (@samp{x}).
8715 Since the letters indicating unit sizes are all distinct from the
8716 letters specifying output formats, you do not have to remember whether
8717 unit size or format comes first; either order works. The output
8718 specifications @samp{4xw} and @samp{4wx} mean exactly the same thing.
8719 (However, the count @var{n} must come first; @samp{wx4} does not work.)
8721 Even though the unit size @var{u} is ignored for the formats @samp{s}
8722 and @samp{i}, you might still want to use a count @var{n}; for example,
8723 @samp{3i} specifies that you want to see three machine instructions,
8724 including any operands. For convenience, especially when used with
8725 the @code{display} command, the @samp{i} format also prints branch delay
8726 slot instructions, if any, beyond the count specified, which immediately
8727 follow the last instruction that is within the count. The command
8728 @code{disassemble} gives an alternative way of inspecting machine
8729 instructions; see @ref{Machine Code,,Source and Machine Code}.
8731 All the defaults for the arguments to @code{x} are designed to make it
8732 easy to continue scanning memory with minimal specifications each time
8733 you use @code{x}. For example, after you have inspected three machine
8734 instructions with @samp{x/3i @var{addr}}, you can inspect the next seven
8735 with just @samp{x/7}. If you use @key{RET} to repeat the @code{x} command,
8736 the repeat count @var{n} is used again; the other arguments default as
8737 for successive uses of @code{x}.
8739 When examining machine instructions, the instruction at current program
8740 counter is shown with a @code{=>} marker. For example:
8743 (@value{GDBP}) x/5i $pc-6
8744 0x804837f <main+11>: mov %esp,%ebp
8745 0x8048381 <main+13>: push %ecx
8746 0x8048382 <main+14>: sub $0x4,%esp
8747 => 0x8048385 <main+17>: movl $0x8048460,(%esp)
8748 0x804838c <main+24>: call 0x80482d4 <puts@@plt>
8751 @cindex @code{$_}, @code{$__}, and value history
8752 The addresses and contents printed by the @code{x} command are not saved
8753 in the value history because there is often too much of them and they
8754 would get in the way. Instead, @value{GDBN} makes these values available for
8755 subsequent use in expressions as values of the convenience variables
8756 @code{$_} and @code{$__}. After an @code{x} command, the last address
8757 examined is available for use in expressions in the convenience variable
8758 @code{$_}. The contents of that address, as examined, are available in
8759 the convenience variable @code{$__}.
8761 If the @code{x} command has a repeat count, the address and contents saved
8762 are from the last memory unit printed; this is not the same as the last
8763 address printed if several units were printed on the last line of output.
8765 @cindex remote memory comparison
8766 @cindex verify remote memory image
8767 When you are debugging a program running on a remote target machine
8768 (@pxref{Remote Debugging}), you may wish to verify the program's image in the
8769 remote machine's memory against the executable file you downloaded to
8770 the target. The @code{compare-sections} command is provided for such
8774 @kindex compare-sections
8775 @item compare-sections @r{[}@var{section-name}@r{]}
8776 Compare the data of a loadable section @var{section-name} in the
8777 executable file of the program being debugged with the same section in
8778 the remote machine's memory, and report any mismatches. With no
8779 arguments, compares all loadable sections. This command's
8780 availability depends on the target's support for the @code{"qCRC"}
8785 @section Automatic Display
8786 @cindex automatic display
8787 @cindex display of expressions
8789 If you find that you want to print the value of an expression frequently
8790 (to see how it changes), you might want to add it to the @dfn{automatic
8791 display list} so that @value{GDBN} prints its value each time your program stops.
8792 Each expression added to the list is given a number to identify it;
8793 to remove an expression from the list, you specify that number.
8794 The automatic display looks like this:
8798 3: bar[5] = (struct hack *) 0x3804
8802 This display shows item numbers, expressions and their current values. As with
8803 displays you request manually using @code{x} or @code{print}, you can
8804 specify the output format you prefer; in fact, @code{display} decides
8805 whether to use @code{print} or @code{x} depending your format
8806 specification---it uses @code{x} if you specify either the @samp{i}
8807 or @samp{s} format, or a unit size; otherwise it uses @code{print}.
8811 @item display @var{expr}
8812 Add the expression @var{expr} to the list of expressions to display
8813 each time your program stops. @xref{Expressions, ,Expressions}.
8815 @code{display} does not repeat if you press @key{RET} again after using it.
8817 @item display/@var{fmt} @var{expr}
8818 For @var{fmt} specifying only a display format and not a size or
8819 count, add the expression @var{expr} to the auto-display list but
8820 arrange to display it each time in the specified format @var{fmt}.
8821 @xref{Output Formats,,Output Formats}.
8823 @item display/@var{fmt} @var{addr}
8824 For @var{fmt} @samp{i} or @samp{s}, or including a unit-size or a
8825 number of units, add the expression @var{addr} as a memory address to
8826 be examined each time your program stops. Examining means in effect
8827 doing @samp{x/@var{fmt} @var{addr}}. @xref{Memory, ,Examining Memory}.
8830 For example, @samp{display/i $pc} can be helpful, to see the machine
8831 instruction about to be executed each time execution stops (@samp{$pc}
8832 is a common name for the program counter; @pxref{Registers, ,Registers}).
8835 @kindex delete display
8837 @item undisplay @var{dnums}@dots{}
8838 @itemx delete display @var{dnums}@dots{}
8839 Remove items from the list of expressions to display. Specify the
8840 numbers of the displays that you want affected with the command
8841 argument @var{dnums}. It can be a single display number, one of the
8842 numbers shown in the first field of the @samp{info display} display;
8843 or it could be a range of display numbers, as in @code{2-4}.
8845 @code{undisplay} does not repeat if you press @key{RET} after using it.
8846 (Otherwise you would just get the error @samp{No display number @dots{}}.)
8848 @kindex disable display
8849 @item disable display @var{dnums}@dots{}
8850 Disable the display of item numbers @var{dnums}. A disabled display
8851 item is not printed automatically, but is not forgotten. It may be
8852 enabled again later. Specify the numbers of the displays that you
8853 want affected with the command argument @var{dnums}. It can be a
8854 single display number, one of the numbers shown in the first field of
8855 the @samp{info display} display; or it could be a range of display
8856 numbers, as in @code{2-4}.
8858 @kindex enable display
8859 @item enable display @var{dnums}@dots{}
8860 Enable display of item numbers @var{dnums}. It becomes effective once
8861 again in auto display of its expression, until you specify otherwise.
8862 Specify the numbers of the displays that you want affected with the
8863 command argument @var{dnums}. It can be a single display number, one
8864 of the numbers shown in the first field of the @samp{info display}
8865 display; or it could be a range of display numbers, as in @code{2-4}.
8868 Display the current values of the expressions on the list, just as is
8869 done when your program stops.
8871 @kindex info display
8873 Print the list of expressions previously set up to display
8874 automatically, each one with its item number, but without showing the
8875 values. This includes disabled expressions, which are marked as such.
8876 It also includes expressions which would not be displayed right now
8877 because they refer to automatic variables not currently available.
8880 @cindex display disabled out of scope
8881 If a display expression refers to local variables, then it does not make
8882 sense outside the lexical context for which it was set up. Such an
8883 expression is disabled when execution enters a context where one of its
8884 variables is not defined. For example, if you give the command
8885 @code{display last_char} while inside a function with an argument
8886 @code{last_char}, @value{GDBN} displays this argument while your program
8887 continues to stop inside that function. When it stops elsewhere---where
8888 there is no variable @code{last_char}---the display is disabled
8889 automatically. The next time your program stops where @code{last_char}
8890 is meaningful, you can enable the display expression once again.
8892 @node Print Settings
8893 @section Print Settings
8895 @cindex format options
8896 @cindex print settings
8897 @value{GDBN} provides the following ways to control how arrays, structures,
8898 and symbols are printed.
8901 These settings are useful for debugging programs in any language:
8905 @item set print address
8906 @itemx set print address on
8907 @cindex print/don't print memory addresses
8908 @value{GDBN} prints memory addresses showing the location of stack
8909 traces, structure values, pointer values, breakpoints, and so forth,
8910 even when it also displays the contents of those addresses. The default
8911 is @code{on}. For example, this is what a stack frame display looks like with
8912 @code{set print address on}:
8917 #0 set_quotes (lq=0x34c78 "<<", rq=0x34c88 ">>")
8919 530 if (lquote != def_lquote)
8923 @item set print address off
8924 Do not print addresses when displaying their contents. For example,
8925 this is the same stack frame displayed with @code{set print address off}:
8929 (@value{GDBP}) set print addr off
8931 #0 set_quotes (lq="<<", rq=">>") at input.c:530
8932 530 if (lquote != def_lquote)
8936 You can use @samp{set print address off} to eliminate all machine
8937 dependent displays from the @value{GDBN} interface. For example, with
8938 @code{print address off}, you should get the same text for backtraces on
8939 all machines---whether or not they involve pointer arguments.
8942 @item show print address
8943 Show whether or not addresses are to be printed.
8946 When @value{GDBN} prints a symbolic address, it normally prints the
8947 closest earlier symbol plus an offset. If that symbol does not uniquely
8948 identify the address (for example, it is a name whose scope is a single
8949 source file), you may need to clarify. One way to do this is with
8950 @code{info line}, for example @samp{info line *0x4537}. Alternately,
8951 you can set @value{GDBN} to print the source file and line number when
8952 it prints a symbolic address:
8955 @item set print symbol-filename on
8956 @cindex source file and line of a symbol
8957 @cindex symbol, source file and line
8958 Tell @value{GDBN} to print the source file name and line number of a
8959 symbol in the symbolic form of an address.
8961 @item set print symbol-filename off
8962 Do not print source file name and line number of a symbol. This is the
8965 @item show print symbol-filename
8966 Show whether or not @value{GDBN} will print the source file name and
8967 line number of a symbol in the symbolic form of an address.
8970 Another situation where it is helpful to show symbol filenames and line
8971 numbers is when disassembling code; @value{GDBN} shows you the line
8972 number and source file that corresponds to each instruction.
8974 Also, you may wish to see the symbolic form only if the address being
8975 printed is reasonably close to the closest earlier symbol:
8978 @item set print max-symbolic-offset @var{max-offset}
8979 @itemx set print max-symbolic-offset unlimited
8980 @cindex maximum value for offset of closest symbol
8981 Tell @value{GDBN} to only display the symbolic form of an address if the
8982 offset between the closest earlier symbol and the address is less than
8983 @var{max-offset}. The default is @code{unlimited}, which tells @value{GDBN}
8984 to always print the symbolic form of an address if any symbol precedes
8985 it. Zero is equivalent to @code{unlimited}.
8987 @item show print max-symbolic-offset
8988 Ask how large the maximum offset is that @value{GDBN} prints in a
8992 @cindex wild pointer, interpreting
8993 @cindex pointer, finding referent
8994 If you have a pointer and you are not sure where it points, try
8995 @samp{set print symbol-filename on}. Then you can determine the name
8996 and source file location of the variable where it points, using
8997 @samp{p/a @var{pointer}}. This interprets the address in symbolic form.
8998 For example, here @value{GDBN} shows that a variable @code{ptt} points
8999 at another variable @code{t}, defined in @file{hi2.c}:
9002 (@value{GDBP}) set print symbol-filename on
9003 (@value{GDBP}) p/a ptt
9004 $4 = 0xe008 <t in hi2.c>
9008 @emph{Warning:} For pointers that point to a local variable, @samp{p/a}
9009 does not show the symbol name and filename of the referent, even with
9010 the appropriate @code{set print} options turned on.
9013 You can also enable @samp{/a}-like formatting all the time using
9014 @samp{set print symbol on}:
9017 @item set print symbol on
9018 Tell @value{GDBN} to print the symbol corresponding to an address, if
9021 @item set print symbol off
9022 Tell @value{GDBN} not to print the symbol corresponding to an
9023 address. In this mode, @value{GDBN} will still print the symbol
9024 corresponding to pointers to functions. This is the default.
9026 @item show print symbol
9027 Show whether @value{GDBN} will display the symbol corresponding to an
9031 Other settings control how different kinds of objects are printed:
9034 @item set print array
9035 @itemx set print array on
9036 @cindex pretty print arrays
9037 Pretty print arrays. This format is more convenient to read,
9038 but uses more space. The default is off.
9040 @item set print array off
9041 Return to compressed format for arrays.
9043 @item show print array
9044 Show whether compressed or pretty format is selected for displaying
9047 @cindex print array indexes
9048 @item set print array-indexes
9049 @itemx set print array-indexes on
9050 Print the index of each element when displaying arrays. May be more
9051 convenient to locate a given element in the array or quickly find the
9052 index of a given element in that printed array. The default is off.
9054 @item set print array-indexes off
9055 Stop printing element indexes when displaying arrays.
9057 @item show print array-indexes
9058 Show whether the index of each element is printed when displaying
9061 @item set print elements @var{number-of-elements}
9062 @itemx set print elements unlimited
9063 @cindex number of array elements to print
9064 @cindex limit on number of printed array elements
9065 Set a limit on how many elements of an array @value{GDBN} will print.
9066 If @value{GDBN} is printing a large array, it stops printing after it has
9067 printed the number of elements set by the @code{set print elements} command.
9068 This limit also applies to the display of strings.
9069 When @value{GDBN} starts, this limit is set to 200.
9070 Setting @var{number-of-elements} to @code{unlimited} or zero means
9071 that the number of elements to print is unlimited.
9073 @item show print elements
9074 Display the number of elements of a large array that @value{GDBN} will print.
9075 If the number is 0, then the printing is unlimited.
9077 @item set print frame-arguments @var{value}
9078 @kindex set print frame-arguments
9079 @cindex printing frame argument values
9080 @cindex print all frame argument values
9081 @cindex print frame argument values for scalars only
9082 @cindex do not print frame argument values
9083 This command allows to control how the values of arguments are printed
9084 when the debugger prints a frame (@pxref{Frames}). The possible
9089 The values of all arguments are printed.
9092 Print the value of an argument only if it is a scalar. The value of more
9093 complex arguments such as arrays, structures, unions, etc, is replaced
9094 by @code{@dots{}}. This is the default. Here is an example where
9095 only scalar arguments are shown:
9098 #1 0x08048361 in call_me (i=3, s=@dots{}, ss=0xbf8d508c, u=@dots{}, e=green)
9103 None of the argument values are printed. Instead, the value of each argument
9104 is replaced by @code{@dots{}}. In this case, the example above now becomes:
9107 #1 0x08048361 in call_me (i=@dots{}, s=@dots{}, ss=@dots{}, u=@dots{}, e=@dots{})
9112 By default, only scalar arguments are printed. This command can be used
9113 to configure the debugger to print the value of all arguments, regardless
9114 of their type. However, it is often advantageous to not print the value
9115 of more complex parameters. For instance, it reduces the amount of
9116 information printed in each frame, making the backtrace more readable.
9117 Also, it improves performance when displaying Ada frames, because
9118 the computation of large arguments can sometimes be CPU-intensive,
9119 especially in large applications. Setting @code{print frame-arguments}
9120 to @code{scalars} (the default) or @code{none} avoids this computation,
9121 thus speeding up the display of each Ada frame.
9123 @item show print frame-arguments
9124 Show how the value of arguments should be displayed when printing a frame.
9126 @item set print raw frame-arguments on
9127 Print frame arguments in raw, non pretty-printed, form.
9129 @item set print raw frame-arguments off
9130 Print frame arguments in pretty-printed form, if there is a pretty-printer
9131 for the value (@pxref{Pretty Printing}),
9132 otherwise print the value in raw form.
9133 This is the default.
9135 @item show print raw frame-arguments
9136 Show whether to print frame arguments in raw form.
9138 @anchor{set print entry-values}
9139 @item set print entry-values @var{value}
9140 @kindex set print entry-values
9141 Set printing of frame argument values at function entry. In some cases
9142 @value{GDBN} can determine the value of function argument which was passed by
9143 the function caller, even if the value was modified inside the called function
9144 and therefore is different. With optimized code, the current value could be
9145 unavailable, but the entry value may still be known.
9147 The default value is @code{default} (see below for its description). Older
9148 @value{GDBN} behaved as with the setting @code{no}. Compilers not supporting
9149 this feature will behave in the @code{default} setting the same way as with the
9152 This functionality is currently supported only by DWARF 2 debugging format and
9153 the compiler has to produce @samp{DW_TAG_GNU_call_site} tags. With
9154 @value{NGCC}, you need to specify @option{-O -g} during compilation, to get
9157 The @var{value} parameter can be one of the following:
9161 Print only actual parameter values, never print values from function entry
9165 #0 different (val=6)
9166 #0 lost (val=<optimized out>)
9168 #0 invalid (val=<optimized out>)
9172 Print only parameter values from function entry point. The actual parameter
9173 values are never printed.
9175 #0 equal (val@@entry=5)
9176 #0 different (val@@entry=5)
9177 #0 lost (val@@entry=5)
9178 #0 born (val@@entry=<optimized out>)
9179 #0 invalid (val@@entry=<optimized out>)
9183 Print only parameter values from function entry point. If value from function
9184 entry point is not known while the actual value is known, print the actual
9185 value for such parameter.
9187 #0 equal (val@@entry=5)
9188 #0 different (val@@entry=5)
9189 #0 lost (val@@entry=5)
9191 #0 invalid (val@@entry=<optimized out>)
9195 Print actual parameter values. If actual parameter value is not known while
9196 value from function entry point is known, print the entry point value for such
9200 #0 different (val=6)
9201 #0 lost (val@@entry=5)
9203 #0 invalid (val=<optimized out>)
9207 Always print both the actual parameter value and its value from function entry
9208 point, even if values of one or both are not available due to compiler
9211 #0 equal (val=5, val@@entry=5)
9212 #0 different (val=6, val@@entry=5)
9213 #0 lost (val=<optimized out>, val@@entry=5)
9214 #0 born (val=10, val@@entry=<optimized out>)
9215 #0 invalid (val=<optimized out>, val@@entry=<optimized out>)
9219 Print the actual parameter value if it is known and also its value from
9220 function entry point if it is known. If neither is known, print for the actual
9221 value @code{<optimized out>}. If not in MI mode (@pxref{GDB/MI}) and if both
9222 values are known and identical, print the shortened
9223 @code{param=param@@entry=VALUE} notation.
9225 #0 equal (val=val@@entry=5)
9226 #0 different (val=6, val@@entry=5)
9227 #0 lost (val@@entry=5)
9229 #0 invalid (val=<optimized out>)
9233 Always print the actual parameter value. Print also its value from function
9234 entry point, but only if it is known. If not in MI mode (@pxref{GDB/MI}) and
9235 if both values are known and identical, print the shortened
9236 @code{param=param@@entry=VALUE} notation.
9238 #0 equal (val=val@@entry=5)
9239 #0 different (val=6, val@@entry=5)
9240 #0 lost (val=<optimized out>, val@@entry=5)
9242 #0 invalid (val=<optimized out>)
9246 For analysis messages on possible failures of frame argument values at function
9247 entry resolution see @ref{set debug entry-values}.
9249 @item show print entry-values
9250 Show the method being used for printing of frame argument values at function
9253 @item set print repeats @var{number-of-repeats}
9254 @itemx set print repeats unlimited
9255 @cindex repeated array elements
9256 Set the threshold for suppressing display of repeated array
9257 elements. When the number of consecutive identical elements of an
9258 array exceeds the threshold, @value{GDBN} prints the string
9259 @code{"<repeats @var{n} times>"}, where @var{n} is the number of
9260 identical repetitions, instead of displaying the identical elements
9261 themselves. Setting the threshold to @code{unlimited} or zero will
9262 cause all elements to be individually printed. The default threshold
9265 @item show print repeats
9266 Display the current threshold for printing repeated identical
9269 @item set print null-stop
9270 @cindex @sc{null} elements in arrays
9271 Cause @value{GDBN} to stop printing the characters of an array when the first
9272 @sc{null} is encountered. This is useful when large arrays actually
9273 contain only short strings.
9276 @item show print null-stop
9277 Show whether @value{GDBN} stops printing an array on the first
9278 @sc{null} character.
9280 @item set print pretty on
9281 @cindex print structures in indented form
9282 @cindex indentation in structure display
9283 Cause @value{GDBN} to print structures in an indented format with one member
9284 per line, like this:
9299 @item set print pretty off
9300 Cause @value{GDBN} to print structures in a compact format, like this:
9304 $1 = @{next = 0x0, flags = @{sweet = 1, sour = 1@}, \
9305 meat = 0x54 "Pork"@}
9310 This is the default format.
9312 @item show print pretty
9313 Show which format @value{GDBN} is using to print structures.
9315 @item set print sevenbit-strings on
9316 @cindex eight-bit characters in strings
9317 @cindex octal escapes in strings
9318 Print using only seven-bit characters; if this option is set,
9319 @value{GDBN} displays any eight-bit characters (in strings or
9320 character values) using the notation @code{\}@var{nnn}. This setting is
9321 best if you are working in English (@sc{ascii}) and you use the
9322 high-order bit of characters as a marker or ``meta'' bit.
9324 @item set print sevenbit-strings off
9325 Print full eight-bit characters. This allows the use of more
9326 international character sets, and is the default.
9328 @item show print sevenbit-strings
9329 Show whether or not @value{GDBN} is printing only seven-bit characters.
9331 @item set print union on
9332 @cindex unions in structures, printing
9333 Tell @value{GDBN} to print unions which are contained in structures
9334 and other unions. This is the default setting.
9336 @item set print union off
9337 Tell @value{GDBN} not to print unions which are contained in
9338 structures and other unions. @value{GDBN} will print @code{"@{...@}"}
9341 @item show print union
9342 Ask @value{GDBN} whether or not it will print unions which are contained in
9343 structures and other unions.
9345 For example, given the declarations
9348 typedef enum @{Tree, Bug@} Species;
9349 typedef enum @{Big_tree, Acorn, Seedling@} Tree_forms;
9350 typedef enum @{Caterpillar, Cocoon, Butterfly@}
9361 struct thing foo = @{Tree, @{Acorn@}@};
9365 with @code{set print union on} in effect @samp{p foo} would print
9368 $1 = @{it = Tree, form = @{tree = Acorn, bug = Cocoon@}@}
9372 and with @code{set print union off} in effect it would print
9375 $1 = @{it = Tree, form = @{...@}@}
9379 @code{set print union} affects programs written in C-like languages
9385 These settings are of interest when debugging C@t{++} programs:
9388 @cindex demangling C@t{++} names
9389 @item set print demangle
9390 @itemx set print demangle on
9391 Print C@t{++} names in their source form rather than in the encoded
9392 (``mangled'') form passed to the assembler and linker for type-safe
9393 linkage. The default is on.
9395 @item show print demangle
9396 Show whether C@t{++} names are printed in mangled or demangled form.
9398 @item set print asm-demangle
9399 @itemx set print asm-demangle on
9400 Print C@t{++} names in their source form rather than their mangled form, even
9401 in assembler code printouts such as instruction disassemblies.
9404 @item show print asm-demangle
9405 Show whether C@t{++} names in assembly listings are printed in mangled
9408 @cindex C@t{++} symbol decoding style
9409 @cindex symbol decoding style, C@t{++}
9410 @kindex set demangle-style
9411 @item set demangle-style @var{style}
9412 Choose among several encoding schemes used by different compilers to
9413 represent C@t{++} names. The choices for @var{style} are currently:
9417 Allow @value{GDBN} to choose a decoding style by inspecting your program.
9418 This is the default.
9421 Decode based on the @sc{gnu} C@t{++} compiler (@code{g++}) encoding algorithm.
9424 Decode based on the HP ANSI C@t{++} (@code{aCC}) encoding algorithm.
9427 Decode based on the Lucid C@t{++} compiler (@code{lcc}) encoding algorithm.
9430 Decode using the algorithm in the @cite{C@t{++} Annotated Reference Manual}.
9431 @strong{Warning:} this setting alone is not sufficient to allow
9432 debugging @code{cfront}-generated executables. @value{GDBN} would
9433 require further enhancement to permit that.
9436 If you omit @var{style}, you will see a list of possible formats.
9438 @item show demangle-style
9439 Display the encoding style currently in use for decoding C@t{++} symbols.
9441 @item set print object
9442 @itemx set print object on
9443 @cindex derived type of an object, printing
9444 @cindex display derived types
9445 When displaying a pointer to an object, identify the @emph{actual}
9446 (derived) type of the object rather than the @emph{declared} type, using
9447 the virtual function table. Note that the virtual function table is
9448 required---this feature can only work for objects that have run-time
9449 type identification; a single virtual method in the object's declared
9450 type is sufficient. Note that this setting is also taken into account when
9451 working with variable objects via MI (@pxref{GDB/MI}).
9453 @item set print object off
9454 Display only the declared type of objects, without reference to the
9455 virtual function table. This is the default setting.
9457 @item show print object
9458 Show whether actual, or declared, object types are displayed.
9460 @item set print static-members
9461 @itemx set print static-members on
9462 @cindex static members of C@t{++} objects
9463 Print static members when displaying a C@t{++} object. The default is on.
9465 @item set print static-members off
9466 Do not print static members when displaying a C@t{++} object.
9468 @item show print static-members
9469 Show whether C@t{++} static members are printed or not.
9471 @item set print pascal_static-members
9472 @itemx set print pascal_static-members on
9473 @cindex static members of Pascal objects
9474 @cindex Pascal objects, static members display
9475 Print static members when displaying a Pascal object. The default is on.
9477 @item set print pascal_static-members off
9478 Do not print static members when displaying a Pascal object.
9480 @item show print pascal_static-members
9481 Show whether Pascal static members are printed or not.
9483 @c These don't work with HP ANSI C++ yet.
9484 @item set print vtbl
9485 @itemx set print vtbl on
9486 @cindex pretty print C@t{++} virtual function tables
9487 @cindex virtual functions (C@t{++}) display
9488 @cindex VTBL display
9489 Pretty print C@t{++} virtual function tables. The default is off.
9490 (The @code{vtbl} commands do not work on programs compiled with the HP
9491 ANSI C@t{++} compiler (@code{aCC}).)
9493 @item set print vtbl off
9494 Do not pretty print C@t{++} virtual function tables.
9496 @item show print vtbl
9497 Show whether C@t{++} virtual function tables are pretty printed, or not.
9500 @node Pretty Printing
9501 @section Pretty Printing
9503 @value{GDBN} provides a mechanism to allow pretty-printing of values using
9504 Python code. It greatly simplifies the display of complex objects. This
9505 mechanism works for both MI and the CLI.
9508 * Pretty-Printer Introduction:: Introduction to pretty-printers
9509 * Pretty-Printer Example:: An example pretty-printer
9510 * Pretty-Printer Commands:: Pretty-printer commands
9513 @node Pretty-Printer Introduction
9514 @subsection Pretty-Printer Introduction
9516 When @value{GDBN} prints a value, it first sees if there is a pretty-printer
9517 registered for the value. If there is then @value{GDBN} invokes the
9518 pretty-printer to print the value. Otherwise the value is printed normally.
9520 Pretty-printers are normally named. This makes them easy to manage.
9521 The @samp{info pretty-printer} command will list all the installed
9522 pretty-printers with their names.
9523 If a pretty-printer can handle multiple data types, then its
9524 @dfn{subprinters} are the printers for the individual data types.
9525 Each such subprinter has its own name.
9526 The format of the name is @var{printer-name};@var{subprinter-name}.
9528 Pretty-printers are installed by @dfn{registering} them with @value{GDBN}.
9529 Typically they are automatically loaded and registered when the corresponding
9530 debug information is loaded, thus making them available without having to
9531 do anything special.
9533 There are three places where a pretty-printer can be registered.
9537 Pretty-printers registered globally are available when debugging
9541 Pretty-printers registered with a program space are available only
9542 when debugging that program.
9543 @xref{Progspaces In Python}, for more details on program spaces in Python.
9546 Pretty-printers registered with an objfile are loaded and unloaded
9547 with the corresponding objfile (e.g., shared library).
9548 @xref{Objfiles In Python}, for more details on objfiles in Python.
9551 @xref{Selecting Pretty-Printers}, for further information on how
9552 pretty-printers are selected,
9554 @xref{Writing a Pretty-Printer}, for implementing pretty printers
9557 @node Pretty-Printer Example
9558 @subsection Pretty-Printer Example
9560 Here is how a C@t{++} @code{std::string} looks without a pretty-printer:
9563 (@value{GDBP}) print s
9565 static npos = 4294967295,
9567 <std::allocator<char>> = @{
9568 <__gnu_cxx::new_allocator<char>> = @{
9569 <No data fields>@}, <No data fields>
9571 members of std::basic_string<char, std::char_traits<char>,
9572 std::allocator<char> >::_Alloc_hider:
9573 _M_p = 0x804a014 "abcd"
9578 With a pretty-printer for @code{std::string} only the contents are printed:
9581 (@value{GDBP}) print s
9585 @node Pretty-Printer Commands
9586 @subsection Pretty-Printer Commands
9587 @cindex pretty-printer commands
9590 @kindex info pretty-printer
9591 @item info pretty-printer [@var{object-regexp} [@var{name-regexp}]]
9592 Print the list of installed pretty-printers.
9593 This includes disabled pretty-printers, which are marked as such.
9595 @var{object-regexp} is a regular expression matching the objects
9596 whose pretty-printers to list.
9597 Objects can be @code{global}, the program space's file
9598 (@pxref{Progspaces In Python}),
9599 and the object files within that program space (@pxref{Objfiles In Python}).
9600 @xref{Selecting Pretty-Printers}, for details on how @value{GDBN}
9601 looks up a printer from these three objects.
9603 @var{name-regexp} is a regular expression matching the name of the printers
9606 @kindex disable pretty-printer
9607 @item disable pretty-printer [@var{object-regexp} [@var{name-regexp}]]
9608 Disable pretty-printers matching @var{object-regexp} and @var{name-regexp}.
9609 A disabled pretty-printer is not forgotten, it may be enabled again later.
9611 @kindex enable pretty-printer
9612 @item enable pretty-printer [@var{object-regexp} [@var{name-regexp}]]
9613 Enable pretty-printers matching @var{object-regexp} and @var{name-regexp}.
9618 Suppose we have three pretty-printers installed: one from library1.so
9619 named @code{foo} that prints objects of type @code{foo}, and
9620 another from library2.so named @code{bar} that prints two types of objects,
9621 @code{bar1} and @code{bar2}.
9624 (gdb) info pretty-printer
9631 (gdb) info pretty-printer library2
9636 (gdb) disable pretty-printer library1
9638 2 of 3 printers enabled
9639 (gdb) info pretty-printer
9646 (gdb) disable pretty-printer library2 bar:bar1
9648 1 of 3 printers enabled
9649 (gdb) info pretty-printer library2
9656 (gdb) disable pretty-printer library2 bar
9658 0 of 3 printers enabled
9659 (gdb) info pretty-printer library2
9668 Note that for @code{bar} the entire printer can be disabled,
9669 as can each individual subprinter.
9672 @section Value History
9674 @cindex value history
9675 @cindex history of values printed by @value{GDBN}
9676 Values printed by the @code{print} command are saved in the @value{GDBN}
9677 @dfn{value history}. This allows you to refer to them in other expressions.
9678 Values are kept until the symbol table is re-read or discarded
9679 (for example with the @code{file} or @code{symbol-file} commands).
9680 When the symbol table changes, the value history is discarded,
9681 since the values may contain pointers back to the types defined in the
9686 @cindex history number
9687 The values printed are given @dfn{history numbers} by which you can
9688 refer to them. These are successive integers starting with one.
9689 @code{print} shows you the history number assigned to a value by
9690 printing @samp{$@var{num} = } before the value; here @var{num} is the
9693 To refer to any previous value, use @samp{$} followed by the value's
9694 history number. The way @code{print} labels its output is designed to
9695 remind you of this. Just @code{$} refers to the most recent value in
9696 the history, and @code{$$} refers to the value before that.
9697 @code{$$@var{n}} refers to the @var{n}th value from the end; @code{$$2}
9698 is the value just prior to @code{$$}, @code{$$1} is equivalent to
9699 @code{$$}, and @code{$$0} is equivalent to @code{$}.
9701 For example, suppose you have just printed a pointer to a structure and
9702 want to see the contents of the structure. It suffices to type
9708 If you have a chain of structures where the component @code{next} points
9709 to the next one, you can print the contents of the next one with this:
9716 You can print successive links in the chain by repeating this
9717 command---which you can do by just typing @key{RET}.
9719 Note that the history records values, not expressions. If the value of
9720 @code{x} is 4 and you type these commands:
9728 then the value recorded in the value history by the @code{print} command
9729 remains 4 even though the value of @code{x} has changed.
9734 Print the last ten values in the value history, with their item numbers.
9735 This is like @samp{p@ $$9} repeated ten times, except that @code{show
9736 values} does not change the history.
9738 @item show values @var{n}
9739 Print ten history values centered on history item number @var{n}.
9742 Print ten history values just after the values last printed. If no more
9743 values are available, @code{show values +} produces no display.
9746 Pressing @key{RET} to repeat @code{show values @var{n}} has exactly the
9747 same effect as @samp{show values +}.
9749 @node Convenience Vars
9750 @section Convenience Variables
9752 @cindex convenience variables
9753 @cindex user-defined variables
9754 @value{GDBN} provides @dfn{convenience variables} that you can use within
9755 @value{GDBN} to hold on to a value and refer to it later. These variables
9756 exist entirely within @value{GDBN}; they are not part of your program, and
9757 setting a convenience variable has no direct effect on further execution
9758 of your program. That is why you can use them freely.
9760 Convenience variables are prefixed with @samp{$}. Any name preceded by
9761 @samp{$} can be used for a convenience variable, unless it is one of
9762 the predefined machine-specific register names (@pxref{Registers, ,Registers}).
9763 (Value history references, in contrast, are @emph{numbers} preceded
9764 by @samp{$}. @xref{Value History, ,Value History}.)
9766 You can save a value in a convenience variable with an assignment
9767 expression, just as you would set a variable in your program.
9771 set $foo = *object_ptr
9775 would save in @code{$foo} the value contained in the object pointed to by
9778 Using a convenience variable for the first time creates it, but its
9779 value is @code{void} until you assign a new value. You can alter the
9780 value with another assignment at any time.
9782 Convenience variables have no fixed types. You can assign a convenience
9783 variable any type of value, including structures and arrays, even if
9784 that variable already has a value of a different type. The convenience
9785 variable, when used as an expression, has the type of its current value.
9788 @kindex show convenience
9789 @cindex show all user variables and functions
9790 @item show convenience
9791 Print a list of convenience variables used so far, and their values,
9792 as well as a list of the convenience functions.
9793 Abbreviated @code{show conv}.
9795 @kindex init-if-undefined
9796 @cindex convenience variables, initializing
9797 @item init-if-undefined $@var{variable} = @var{expression}
9798 Set a convenience variable if it has not already been set. This is useful
9799 for user-defined commands that keep some state. It is similar, in concept,
9800 to using local static variables with initializers in C (except that
9801 convenience variables are global). It can also be used to allow users to
9802 override default values used in a command script.
9804 If the variable is already defined then the expression is not evaluated so
9805 any side-effects do not occur.
9808 One of the ways to use a convenience variable is as a counter to be
9809 incremented or a pointer to be advanced. For example, to print
9810 a field from successive elements of an array of structures:
9814 print bar[$i++]->contents
9818 Repeat that command by typing @key{RET}.
9820 Some convenience variables are created automatically by @value{GDBN} and given
9821 values likely to be useful.
9824 @vindex $_@r{, convenience variable}
9826 The variable @code{$_} is automatically set by the @code{x} command to
9827 the last address examined (@pxref{Memory, ,Examining Memory}). Other
9828 commands which provide a default address for @code{x} to examine also
9829 set @code{$_} to that address; these commands include @code{info line}
9830 and @code{info breakpoint}. The type of @code{$_} is @code{void *}
9831 except when set by the @code{x} command, in which case it is a pointer
9832 to the type of @code{$__}.
9834 @vindex $__@r{, convenience variable}
9836 The variable @code{$__} is automatically set by the @code{x} command
9837 to the value found in the last address examined. Its type is chosen
9838 to match the format in which the data was printed.
9841 @vindex $_exitcode@r{, convenience variable}
9842 When the program being debugged terminates normally, @value{GDBN}
9843 automatically sets this variable to the exit code of the program, and
9844 resets @code{$_exitsignal} to @code{void}.
9847 @vindex $_exitsignal@r{, convenience variable}
9848 When the program being debugged dies due to an uncaught signal,
9849 @value{GDBN} automatically sets this variable to that signal's number,
9850 and resets @code{$_exitcode} to @code{void}.
9852 To distinguish between whether the program being debugged has exited
9853 (i.e., @code{$_exitcode} is not @code{void}) or signalled (i.e.,
9854 @code{$_exitsignal} is not @code{void}), the convenience function
9855 @code{$_isvoid} can be used (@pxref{Convenience Funs,, Convenience
9856 Functions}). For example, considering the following source code:
9862 main (int argc, char *argv[])
9869 A valid way of telling whether the program being debugged has exited
9870 or signalled would be:
9873 (@value{GDBP}) define has_exited_or_signalled
9874 Type commands for definition of ``has_exited_or_signalled''.
9875 End with a line saying just ``end''.
9876 >if $_isvoid ($_exitsignal)
9877 >echo The program has exited\n
9879 >echo The program has signalled\n
9885 Program terminated with signal SIGALRM, Alarm clock.
9886 The program no longer exists.
9887 (@value{GDBP}) has_exited_or_signalled
9888 The program has signalled
9891 As can be seen, @value{GDBN} correctly informs that the program being
9892 debugged has signalled, since it calls @code{raise} and raises a
9893 @code{SIGALRM} signal. If the program being debugged had not called
9894 @code{raise}, then @value{GDBN} would report a normal exit:
9897 (@value{GDBP}) has_exited_or_signalled
9898 The program has exited
9902 The variable @code{$_exception} is set to the exception object being
9903 thrown at an exception-related catchpoint. @xref{Set Catchpoints}.
9906 @itemx $_probe_arg0@dots{}$_probe_arg11
9907 Arguments to a static probe. @xref{Static Probe Points}.
9910 @vindex $_sdata@r{, inspect, convenience variable}
9911 The variable @code{$_sdata} contains extra collected static tracepoint
9912 data. @xref{Tracepoint Actions,,Tracepoint Action Lists}. Note that
9913 @code{$_sdata} could be empty, if not inspecting a trace buffer, or
9914 if extra static tracepoint data has not been collected.
9917 @vindex $_siginfo@r{, convenience variable}
9918 The variable @code{$_siginfo} contains extra signal information
9919 (@pxref{extra signal information}). Note that @code{$_siginfo}
9920 could be empty, if the application has not yet received any signals.
9921 For example, it will be empty before you execute the @code{run} command.
9924 @vindex $_tlb@r{, convenience variable}
9925 The variable @code{$_tlb} is automatically set when debugging
9926 applications running on MS-Windows in native mode or connected to
9927 gdbserver that supports the @code{qGetTIBAddr} request.
9928 @xref{General Query Packets}.
9929 This variable contains the address of the thread information block.
9933 On HP-UX systems, if you refer to a function or variable name that
9934 begins with a dollar sign, @value{GDBN} searches for a user or system
9935 name first, before it searches for a convenience variable.
9937 @node Convenience Funs
9938 @section Convenience Functions
9940 @cindex convenience functions
9941 @value{GDBN} also supplies some @dfn{convenience functions}. These
9942 have a syntax similar to convenience variables. A convenience
9943 function can be used in an expression just like an ordinary function;
9944 however, a convenience function is implemented internally to
9947 These functions do not require @value{GDBN} to be configured with
9948 @code{Python} support, which means that they are always available.
9952 @item $_isvoid (@var{expr})
9953 @findex $_isvoid@r{, convenience function}
9954 Return one if the expression @var{expr} is @code{void}. Otherwise it
9957 A @code{void} expression is an expression where the type of the result
9958 is @code{void}. For example, you can examine a convenience variable
9959 (see @ref{Convenience Vars,, Convenience Variables}) to check whether
9963 (@value{GDBP}) print $_exitcode
9965 (@value{GDBP}) print $_isvoid ($_exitcode)
9968 Starting program: ./a.out
9969 [Inferior 1 (process 29572) exited normally]
9970 (@value{GDBP}) print $_exitcode
9972 (@value{GDBP}) print $_isvoid ($_exitcode)
9976 In the example above, we used @code{$_isvoid} to check whether
9977 @code{$_exitcode} is @code{void} before and after the execution of the
9978 program being debugged. Before the execution there is no exit code to
9979 be examined, therefore @code{$_exitcode} is @code{void}. After the
9980 execution the program being debugged returned zero, therefore
9981 @code{$_exitcode} is zero, which means that it is not @code{void}
9984 The @code{void} expression can also be a call of a function from the
9985 program being debugged. For example, given the following function:
9994 The result of calling it inside @value{GDBN} is @code{void}:
9997 (@value{GDBP}) print foo ()
9999 (@value{GDBP}) print $_isvoid (foo ())
10001 (@value{GDBP}) set $v = foo ()
10002 (@value{GDBP}) print $v
10004 (@value{GDBP}) print $_isvoid ($v)
10010 These functions require @value{GDBN} to be configured with
10011 @code{Python} support.
10015 @item $_memeq(@var{buf1}, @var{buf2}, @var{length})
10016 @findex $_memeq@r{, convenience function}
10017 Returns one if the @var{length} bytes at the addresses given by
10018 @var{buf1} and @var{buf2} are equal.
10019 Otherwise it returns zero.
10021 @item $_regex(@var{str}, @var{regex})
10022 @findex $_regex@r{, convenience function}
10023 Returns one if the string @var{str} matches the regular expression
10024 @var{regex}. Otherwise it returns zero.
10025 The syntax of the regular expression is that specified by @code{Python}'s
10026 regular expression support.
10028 @item $_streq(@var{str1}, @var{str2})
10029 @findex $_streq@r{, convenience function}
10030 Returns one if the strings @var{str1} and @var{str2} are equal.
10031 Otherwise it returns zero.
10033 @item $_strlen(@var{str})
10034 @findex $_strlen@r{, convenience function}
10035 Returns the length of string @var{str}.
10039 @value{GDBN} provides the ability to list and get help on
10040 convenience functions.
10043 @item help function
10044 @kindex help function
10045 @cindex show all convenience functions
10046 Print a list of all convenience functions.
10053 You can refer to machine register contents, in expressions, as variables
10054 with names starting with @samp{$}. The names of registers are different
10055 for each machine; use @code{info registers} to see the names used on
10059 @kindex info registers
10060 @item info registers
10061 Print the names and values of all registers except floating-point
10062 and vector registers (in the selected stack frame).
10064 @kindex info all-registers
10065 @cindex floating point registers
10066 @item info all-registers
10067 Print the names and values of all registers, including floating-point
10068 and vector registers (in the selected stack frame).
10070 @item info registers @var{regname} @dots{}
10071 Print the @dfn{relativized} value of each specified register @var{regname}.
10072 As discussed in detail below, register values are normally relative to
10073 the selected stack frame. @var{regname} may be any register name valid on
10074 the machine you are using, with or without the initial @samp{$}.
10077 @cindex stack pointer register
10078 @cindex program counter register
10079 @cindex process status register
10080 @cindex frame pointer register
10081 @cindex standard registers
10082 @value{GDBN} has four ``standard'' register names that are available (in
10083 expressions) on most machines---whenever they do not conflict with an
10084 architecture's canonical mnemonics for registers. The register names
10085 @code{$pc} and @code{$sp} are used for the program counter register and
10086 the stack pointer. @code{$fp} is used for a register that contains a
10087 pointer to the current stack frame, and @code{$ps} is used for a
10088 register that contains the processor status. For example,
10089 you could print the program counter in hex with
10096 or print the instruction to be executed next with
10103 or add four to the stack pointer@footnote{This is a way of removing
10104 one word from the stack, on machines where stacks grow downward in
10105 memory (most machines, nowadays). This assumes that the innermost
10106 stack frame is selected; setting @code{$sp} is not allowed when other
10107 stack frames are selected. To pop entire frames off the stack,
10108 regardless of machine architecture, use @code{return};
10109 see @ref{Returning, ,Returning from a Function}.} with
10115 Whenever possible, these four standard register names are available on
10116 your machine even though the machine has different canonical mnemonics,
10117 so long as there is no conflict. The @code{info registers} command
10118 shows the canonical names. For example, on the SPARC, @code{info
10119 registers} displays the processor status register as @code{$psr} but you
10120 can also refer to it as @code{$ps}; and on x86-based machines @code{$ps}
10121 is an alias for the @sc{eflags} register.
10123 @value{GDBN} always considers the contents of an ordinary register as an
10124 integer when the register is examined in this way. Some machines have
10125 special registers which can hold nothing but floating point; these
10126 registers are considered to have floating point values. There is no way
10127 to refer to the contents of an ordinary register as floating point value
10128 (although you can @emph{print} it as a floating point value with
10129 @samp{print/f $@var{regname}}).
10131 Some registers have distinct ``raw'' and ``virtual'' data formats. This
10132 means that the data format in which the register contents are saved by
10133 the operating system is not the same one that your program normally
10134 sees. For example, the registers of the 68881 floating point
10135 coprocessor are always saved in ``extended'' (raw) format, but all C
10136 programs expect to work with ``double'' (virtual) format. In such
10137 cases, @value{GDBN} normally works with the virtual format only (the format
10138 that makes sense for your program), but the @code{info registers} command
10139 prints the data in both formats.
10141 @cindex SSE registers (x86)
10142 @cindex MMX registers (x86)
10143 Some machines have special registers whose contents can be interpreted
10144 in several different ways. For example, modern x86-based machines
10145 have SSE and MMX registers that can hold several values packed
10146 together in several different formats. @value{GDBN} refers to such
10147 registers in @code{struct} notation:
10150 (@value{GDBP}) print $xmm1
10152 v4_float = @{0, 3.43859137e-038, 1.54142831e-044, 1.821688e-044@},
10153 v2_double = @{9.92129282474342e-303, 2.7585945287983262e-313@},
10154 v16_int8 = "\000\000\000\000\3706;\001\v\000\000\000\r\000\000",
10155 v8_int16 = @{0, 0, 14072, 315, 11, 0, 13, 0@},
10156 v4_int32 = @{0, 20657912, 11, 13@},
10157 v2_int64 = @{88725056443645952, 55834574859@},
10158 uint128 = 0x0000000d0000000b013b36f800000000
10163 To set values of such registers, you need to tell @value{GDBN} which
10164 view of the register you wish to change, as if you were assigning
10165 value to a @code{struct} member:
10168 (@value{GDBP}) set $xmm1.uint128 = 0x000000000000000000000000FFFFFFFF
10171 Normally, register values are relative to the selected stack frame
10172 (@pxref{Selection, ,Selecting a Frame}). This means that you get the
10173 value that the register would contain if all stack frames farther in
10174 were exited and their saved registers restored. In order to see the
10175 true contents of hardware registers, you must select the innermost
10176 frame (with @samp{frame 0}).
10178 @cindex caller-saved registers
10179 @cindex call-clobbered registers
10180 @cindex volatile registers
10181 @cindex <not saved> values
10182 Usually ABIs reserve some registers as not needed to be saved by the
10183 callee (a.k.a.: ``caller-saved'', ``call-clobbered'' or ``volatile''
10184 registers). It may therefore not be possible for @value{GDBN} to know
10185 the value a register had before the call (in other words, in the outer
10186 frame), if the register value has since been changed by the callee.
10187 @value{GDBN} tries to deduce where the inner frame saved
10188 (``callee-saved'') registers, from the debug info, unwind info, or the
10189 machine code generated by your compiler. If some register is not
10190 saved, and @value{GDBN} knows the register is ``caller-saved'' (via
10191 its own knowledge of the ABI, or because the debug/unwind info
10192 explicitly says the register's value is undefined), @value{GDBN}
10193 displays @w{@samp{<not saved>}} as the register's value. With targets
10194 that @value{GDBN} has no knowledge of the register saving convention,
10195 if a register was not saved by the callee, then its value and location
10196 in the outer frame are assumed to be the same of the inner frame.
10197 This is usually harmless, because if the register is call-clobbered,
10198 the caller either does not care what is in the register after the
10199 call, or has code to restore the value that it does care about. Note,
10200 however, that if you change such a register in the outer frame, you
10201 may also be affecting the inner frame. Also, the more ``outer'' the
10202 frame is you're looking at, the more likely a call-clobbered
10203 register's value is to be wrong, in the sense that it doesn't actually
10204 represent the value the register had just before the call.
10206 @node Floating Point Hardware
10207 @section Floating Point Hardware
10208 @cindex floating point
10210 Depending on the configuration, @value{GDBN} may be able to give
10211 you more information about the status of the floating point hardware.
10216 Display hardware-dependent information about the floating
10217 point unit. The exact contents and layout vary depending on the
10218 floating point chip. Currently, @samp{info float} is supported on
10219 the ARM and x86 machines.
10223 @section Vector Unit
10224 @cindex vector unit
10226 Depending on the configuration, @value{GDBN} may be able to give you
10227 more information about the status of the vector unit.
10230 @kindex info vector
10232 Display information about the vector unit. The exact contents and
10233 layout vary depending on the hardware.
10236 @node OS Information
10237 @section Operating System Auxiliary Information
10238 @cindex OS information
10240 @value{GDBN} provides interfaces to useful OS facilities that can help
10241 you debug your program.
10243 @cindex auxiliary vector
10244 @cindex vector, auxiliary
10245 Some operating systems supply an @dfn{auxiliary vector} to programs at
10246 startup. This is akin to the arguments and environment that you
10247 specify for a program, but contains a system-dependent variety of
10248 binary values that tell system libraries important details about the
10249 hardware, operating system, and process. Each value's purpose is
10250 identified by an integer tag; the meanings are well-known but system-specific.
10251 Depending on the configuration and operating system facilities,
10252 @value{GDBN} may be able to show you this information. For remote
10253 targets, this functionality may further depend on the remote stub's
10254 support of the @samp{qXfer:auxv:read} packet, see
10255 @ref{qXfer auxiliary vector read}.
10260 Display the auxiliary vector of the inferior, which can be either a
10261 live process or a core dump file. @value{GDBN} prints each tag value
10262 numerically, and also shows names and text descriptions for recognized
10263 tags. Some values in the vector are numbers, some bit masks, and some
10264 pointers to strings or other data. @value{GDBN} displays each value in the
10265 most appropriate form for a recognized tag, and in hexadecimal for
10266 an unrecognized tag.
10269 On some targets, @value{GDBN} can access operating system-specific
10270 information and show it to you. The types of information available
10271 will differ depending on the type of operating system running on the
10272 target. The mechanism used to fetch the data is described in
10273 @ref{Operating System Information}. For remote targets, this
10274 functionality depends on the remote stub's support of the
10275 @samp{qXfer:osdata:read} packet, see @ref{qXfer osdata read}.
10279 @item info os @var{infotype}
10281 Display OS information of the requested type.
10283 On @sc{gnu}/Linux, the following values of @var{infotype} are valid:
10285 @anchor{linux info os infotypes}
10287 @kindex info os processes
10289 Display the list of processes on the target. For each process,
10290 @value{GDBN} prints the process identifier, the name of the user, the
10291 command corresponding to the process, and the list of processor cores
10292 that the process is currently running on. (To understand what these
10293 properties mean, for this and the following info types, please consult
10294 the general @sc{gnu}/Linux documentation.)
10296 @kindex info os procgroups
10298 Display the list of process groups on the target. For each process,
10299 @value{GDBN} prints the identifier of the process group that it belongs
10300 to, the command corresponding to the process group leader, the process
10301 identifier, and the command line of the process. The list is sorted
10302 first by the process group identifier, then by the process identifier,
10303 so that processes belonging to the same process group are grouped together
10304 and the process group leader is listed first.
10306 @kindex info os threads
10308 Display the list of threads running on the target. For each thread,
10309 @value{GDBN} prints the identifier of the process that the thread
10310 belongs to, the command of the process, the thread identifier, and the
10311 processor core that it is currently running on. The main thread of a
10312 process is not listed.
10314 @kindex info os files
10316 Display the list of open file descriptors on the target. For each
10317 file descriptor, @value{GDBN} prints the identifier of the process
10318 owning the descriptor, the command of the owning process, the value
10319 of the descriptor, and the target of the descriptor.
10321 @kindex info os sockets
10323 Display the list of Internet-domain sockets on the target. For each
10324 socket, @value{GDBN} prints the address and port of the local and
10325 remote endpoints, the current state of the connection, the creator of
10326 the socket, the IP address family of the socket, and the type of the
10329 @kindex info os shm
10331 Display the list of all System V shared-memory regions on the target.
10332 For each shared-memory region, @value{GDBN} prints the region key,
10333 the shared-memory identifier, the access permissions, the size of the
10334 region, the process that created the region, the process that last
10335 attached to or detached from the region, the current number of live
10336 attaches to the region, and the times at which the region was last
10337 attached to, detach from, and changed.
10339 @kindex info os semaphores
10341 Display the list of all System V semaphore sets on the target. For each
10342 semaphore set, @value{GDBN} prints the semaphore set key, the semaphore
10343 set identifier, the access permissions, the number of semaphores in the
10344 set, the user and group of the owner and creator of the semaphore set,
10345 and the times at which the semaphore set was operated upon and changed.
10347 @kindex info os msg
10349 Display the list of all System V message queues on the target. For each
10350 message queue, @value{GDBN} prints the message queue key, the message
10351 queue identifier, the access permissions, the current number of bytes
10352 on the queue, the current number of messages on the queue, the processes
10353 that last sent and received a message on the queue, the user and group
10354 of the owner and creator of the message queue, the times at which a
10355 message was last sent and received on the queue, and the time at which
10356 the message queue was last changed.
10358 @kindex info os modules
10360 Display the list of all loaded kernel modules on the target. For each
10361 module, @value{GDBN} prints the module name, the size of the module in
10362 bytes, the number of times the module is used, the dependencies of the
10363 module, the status of the module, and the address of the loaded module
10368 If @var{infotype} is omitted, then list the possible values for
10369 @var{infotype} and the kind of OS information available for each
10370 @var{infotype}. If the target does not return a list of possible
10371 types, this command will report an error.
10374 @node Memory Region Attributes
10375 @section Memory Region Attributes
10376 @cindex memory region attributes
10378 @dfn{Memory region attributes} allow you to describe special handling
10379 required by regions of your target's memory. @value{GDBN} uses
10380 attributes to determine whether to allow certain types of memory
10381 accesses; whether to use specific width accesses; and whether to cache
10382 target memory. By default the description of memory regions is
10383 fetched from the target (if the current target supports this), but the
10384 user can override the fetched regions.
10386 Defined memory regions can be individually enabled and disabled. When a
10387 memory region is disabled, @value{GDBN} uses the default attributes when
10388 accessing memory in that region. Similarly, if no memory regions have
10389 been defined, @value{GDBN} uses the default attributes when accessing
10392 When a memory region is defined, it is given a number to identify it;
10393 to enable, disable, or remove a memory region, you specify that number.
10397 @item mem @var{lower} @var{upper} @var{attributes}@dots{}
10398 Define a memory region bounded by @var{lower} and @var{upper} with
10399 attributes @var{attributes}@dots{}, and add it to the list of regions
10400 monitored by @value{GDBN}. Note that @var{upper} == 0 is a special
10401 case: it is treated as the target's maximum memory address.
10402 (0xffff on 16 bit targets, 0xffffffff on 32 bit targets, etc.)
10405 Discard any user changes to the memory regions and use target-supplied
10406 regions, if available, or no regions if the target does not support.
10409 @item delete mem @var{nums}@dots{}
10410 Remove memory regions @var{nums}@dots{} from the list of regions
10411 monitored by @value{GDBN}.
10413 @kindex disable mem
10414 @item disable mem @var{nums}@dots{}
10415 Disable monitoring of memory regions @var{nums}@dots{}.
10416 A disabled memory region is not forgotten.
10417 It may be enabled again later.
10420 @item enable mem @var{nums}@dots{}
10421 Enable monitoring of memory regions @var{nums}@dots{}.
10425 Print a table of all defined memory regions, with the following columns
10429 @item Memory Region Number
10430 @item Enabled or Disabled.
10431 Enabled memory regions are marked with @samp{y}.
10432 Disabled memory regions are marked with @samp{n}.
10435 The address defining the inclusive lower bound of the memory region.
10438 The address defining the exclusive upper bound of the memory region.
10441 The list of attributes set for this memory region.
10446 @subsection Attributes
10448 @subsubsection Memory Access Mode
10449 The access mode attributes set whether @value{GDBN} may make read or
10450 write accesses to a memory region.
10452 While these attributes prevent @value{GDBN} from performing invalid
10453 memory accesses, they do nothing to prevent the target system, I/O DMA,
10454 etc.@: from accessing memory.
10458 Memory is read only.
10460 Memory is write only.
10462 Memory is read/write. This is the default.
10465 @subsubsection Memory Access Size
10466 The access size attribute tells @value{GDBN} to use specific sized
10467 accesses in the memory region. Often memory mapped device registers
10468 require specific sized accesses. If no access size attribute is
10469 specified, @value{GDBN} may use accesses of any size.
10473 Use 8 bit memory accesses.
10475 Use 16 bit memory accesses.
10477 Use 32 bit memory accesses.
10479 Use 64 bit memory accesses.
10482 @c @subsubsection Hardware/Software Breakpoints
10483 @c The hardware/software breakpoint attributes set whether @value{GDBN}
10484 @c will use hardware or software breakpoints for the internal breakpoints
10485 @c used by the step, next, finish, until, etc. commands.
10489 @c Always use hardware breakpoints
10490 @c @item swbreak (default)
10493 @subsubsection Data Cache
10494 The data cache attributes set whether @value{GDBN} will cache target
10495 memory. While this generally improves performance by reducing debug
10496 protocol overhead, it can lead to incorrect results because @value{GDBN}
10497 does not know about volatile variables or memory mapped device
10502 Enable @value{GDBN} to cache target memory.
10504 Disable @value{GDBN} from caching target memory. This is the default.
10507 @subsection Memory Access Checking
10508 @value{GDBN} can be instructed to refuse accesses to memory that is
10509 not explicitly described. This can be useful if accessing such
10510 regions has undesired effects for a specific target, or to provide
10511 better error checking. The following commands control this behaviour.
10514 @kindex set mem inaccessible-by-default
10515 @item set mem inaccessible-by-default [on|off]
10516 If @code{on} is specified, make @value{GDBN} treat memory not
10517 explicitly described by the memory ranges as non-existent and refuse accesses
10518 to such memory. The checks are only performed if there's at least one
10519 memory range defined. If @code{off} is specified, make @value{GDBN}
10520 treat the memory not explicitly described by the memory ranges as RAM.
10521 The default value is @code{on}.
10522 @kindex show mem inaccessible-by-default
10523 @item show mem inaccessible-by-default
10524 Show the current handling of accesses to unknown memory.
10528 @c @subsubsection Memory Write Verification
10529 @c The memory write verification attributes set whether @value{GDBN}
10530 @c will re-reads data after each write to verify the write was successful.
10534 @c @item noverify (default)
10537 @node Dump/Restore Files
10538 @section Copy Between Memory and a File
10539 @cindex dump/restore files
10540 @cindex append data to a file
10541 @cindex dump data to a file
10542 @cindex restore data from a file
10544 You can use the commands @code{dump}, @code{append}, and
10545 @code{restore} to copy data between target memory and a file. The
10546 @code{dump} and @code{append} commands write data to a file, and the
10547 @code{restore} command reads data from a file back into the inferior's
10548 memory. Files may be in binary, Motorola S-record, Intel hex, or
10549 Tektronix Hex format; however, @value{GDBN} can only append to binary
10555 @item dump @r{[}@var{format}@r{]} memory @var{filename} @var{start_addr} @var{end_addr}
10556 @itemx dump @r{[}@var{format}@r{]} value @var{filename} @var{expr}
10557 Dump the contents of memory from @var{start_addr} to @var{end_addr},
10558 or the value of @var{expr}, to @var{filename} in the given format.
10560 The @var{format} parameter may be any one of:
10567 Motorola S-record format.
10569 Tektronix Hex format.
10572 @value{GDBN} uses the same definitions of these formats as the
10573 @sc{gnu} binary utilities, like @samp{objdump} and @samp{objcopy}. If
10574 @var{format} is omitted, @value{GDBN} dumps the data in raw binary
10578 @item append @r{[}binary@r{]} memory @var{filename} @var{start_addr} @var{end_addr}
10579 @itemx append @r{[}binary@r{]} value @var{filename} @var{expr}
10580 Append the contents of memory from @var{start_addr} to @var{end_addr},
10581 or the value of @var{expr}, to the file @var{filename}, in raw binary form.
10582 (@value{GDBN} can only append data to files in raw binary form.)
10585 @item restore @var{filename} @r{[}binary@r{]} @var{bias} @var{start} @var{end}
10586 Restore the contents of file @var{filename} into memory. The
10587 @code{restore} command can automatically recognize any known @sc{bfd}
10588 file format, except for raw binary. To restore a raw binary file you
10589 must specify the optional keyword @code{binary} after the filename.
10591 If @var{bias} is non-zero, its value will be added to the addresses
10592 contained in the file. Binary files always start at address zero, so
10593 they will be restored at address @var{bias}. Other bfd files have
10594 a built-in location; they will be restored at offset @var{bias}
10595 from that location.
10597 If @var{start} and/or @var{end} are non-zero, then only data between
10598 file offset @var{start} and file offset @var{end} will be restored.
10599 These offsets are relative to the addresses in the file, before
10600 the @var{bias} argument is applied.
10604 @node Core File Generation
10605 @section How to Produce a Core File from Your Program
10606 @cindex dump core from inferior
10608 A @dfn{core file} or @dfn{core dump} is a file that records the memory
10609 image of a running process and its process status (register values
10610 etc.). Its primary use is post-mortem debugging of a program that
10611 crashed while it ran outside a debugger. A program that crashes
10612 automatically produces a core file, unless this feature is disabled by
10613 the user. @xref{Files}, for information on invoking @value{GDBN} in
10614 the post-mortem debugging mode.
10616 Occasionally, you may wish to produce a core file of the program you
10617 are debugging in order to preserve a snapshot of its state.
10618 @value{GDBN} has a special command for that.
10622 @kindex generate-core-file
10623 @item generate-core-file [@var{file}]
10624 @itemx gcore [@var{file}]
10625 Produce a core dump of the inferior process. The optional argument
10626 @var{file} specifies the file name where to put the core dump. If not
10627 specified, the file name defaults to @file{core.@var{pid}}, where
10628 @var{pid} is the inferior process ID.
10630 Note that this command is implemented only for some systems (as of
10631 this writing, @sc{gnu}/Linux, FreeBSD, Solaris, and S390).
10634 @node Character Sets
10635 @section Character Sets
10636 @cindex character sets
10638 @cindex translating between character sets
10639 @cindex host character set
10640 @cindex target character set
10642 If the program you are debugging uses a different character set to
10643 represent characters and strings than the one @value{GDBN} uses itself,
10644 @value{GDBN} can automatically translate between the character sets for
10645 you. The character set @value{GDBN} uses we call the @dfn{host
10646 character set}; the one the inferior program uses we call the
10647 @dfn{target character set}.
10649 For example, if you are running @value{GDBN} on a @sc{gnu}/Linux system, which
10650 uses the ISO Latin 1 character set, but you are using @value{GDBN}'s
10651 remote protocol (@pxref{Remote Debugging}) to debug a program
10652 running on an IBM mainframe, which uses the @sc{ebcdic} character set,
10653 then the host character set is Latin-1, and the target character set is
10654 @sc{ebcdic}. If you give @value{GDBN} the command @code{set
10655 target-charset EBCDIC-US}, then @value{GDBN} translates between
10656 @sc{ebcdic} and Latin 1 as you print character or string values, or use
10657 character and string literals in expressions.
10659 @value{GDBN} has no way to automatically recognize which character set
10660 the inferior program uses; you must tell it, using the @code{set
10661 target-charset} command, described below.
10663 Here are the commands for controlling @value{GDBN}'s character set
10667 @item set target-charset @var{charset}
10668 @kindex set target-charset
10669 Set the current target character set to @var{charset}. To display the
10670 list of supported target character sets, type
10671 @kbd{@w{set target-charset @key{TAB}@key{TAB}}}.
10673 @item set host-charset @var{charset}
10674 @kindex set host-charset
10675 Set the current host character set to @var{charset}.
10677 By default, @value{GDBN} uses a host character set appropriate to the
10678 system it is running on; you can override that default using the
10679 @code{set host-charset} command. On some systems, @value{GDBN} cannot
10680 automatically determine the appropriate host character set. In this
10681 case, @value{GDBN} uses @samp{UTF-8}.
10683 @value{GDBN} can only use certain character sets as its host character
10684 set. If you type @kbd{@w{set host-charset @key{TAB}@key{TAB}}},
10685 @value{GDBN} will list the host character sets it supports.
10687 @item set charset @var{charset}
10688 @kindex set charset
10689 Set the current host and target character sets to @var{charset}. As
10690 above, if you type @kbd{@w{set charset @key{TAB}@key{TAB}}},
10691 @value{GDBN} will list the names of the character sets that can be used
10692 for both host and target.
10695 @kindex show charset
10696 Show the names of the current host and target character sets.
10698 @item show host-charset
10699 @kindex show host-charset
10700 Show the name of the current host character set.
10702 @item show target-charset
10703 @kindex show target-charset
10704 Show the name of the current target character set.
10706 @item set target-wide-charset @var{charset}
10707 @kindex set target-wide-charset
10708 Set the current target's wide character set to @var{charset}. This is
10709 the character set used by the target's @code{wchar_t} type. To
10710 display the list of supported wide character sets, type
10711 @kbd{@w{set target-wide-charset @key{TAB}@key{TAB}}}.
10713 @item show target-wide-charset
10714 @kindex show target-wide-charset
10715 Show the name of the current target's wide character set.
10718 Here is an example of @value{GDBN}'s character set support in action.
10719 Assume that the following source code has been placed in the file
10720 @file{charset-test.c}:
10726 = @{72, 101, 108, 108, 111, 44, 32, 119,
10727 111, 114, 108, 100, 33, 10, 0@};
10728 char ibm1047_hello[]
10729 = @{200, 133, 147, 147, 150, 107, 64, 166,
10730 150, 153, 147, 132, 90, 37, 0@};
10734 printf ("Hello, world!\n");
10738 In this program, @code{ascii_hello} and @code{ibm1047_hello} are arrays
10739 containing the string @samp{Hello, world!} followed by a newline,
10740 encoded in the @sc{ascii} and @sc{ibm1047} character sets.
10742 We compile the program, and invoke the debugger on it:
10745 $ gcc -g charset-test.c -o charset-test
10746 $ gdb -nw charset-test
10747 GNU gdb 2001-12-19-cvs
10748 Copyright 2001 Free Software Foundation, Inc.
10753 We can use the @code{show charset} command to see what character sets
10754 @value{GDBN} is currently using to interpret and display characters and
10758 (@value{GDBP}) show charset
10759 The current host and target character set is `ISO-8859-1'.
10763 For the sake of printing this manual, let's use @sc{ascii} as our
10764 initial character set:
10766 (@value{GDBP}) set charset ASCII
10767 (@value{GDBP}) show charset
10768 The current host and target character set is `ASCII'.
10772 Let's assume that @sc{ascii} is indeed the correct character set for our
10773 host system --- in other words, let's assume that if @value{GDBN} prints
10774 characters using the @sc{ascii} character set, our terminal will display
10775 them properly. Since our current target character set is also
10776 @sc{ascii}, the contents of @code{ascii_hello} print legibly:
10779 (@value{GDBP}) print ascii_hello
10780 $1 = 0x401698 "Hello, world!\n"
10781 (@value{GDBP}) print ascii_hello[0]
10786 @value{GDBN} uses the target character set for character and string
10787 literals you use in expressions:
10790 (@value{GDBP}) print '+'
10795 The @sc{ascii} character set uses the number 43 to encode the @samp{+}
10798 @value{GDBN} relies on the user to tell it which character set the
10799 target program uses. If we print @code{ibm1047_hello} while our target
10800 character set is still @sc{ascii}, we get jibberish:
10803 (@value{GDBP}) print ibm1047_hello
10804 $4 = 0x4016a8 "\310\205\223\223\226k@@\246\226\231\223\204Z%"
10805 (@value{GDBP}) print ibm1047_hello[0]
10810 If we invoke the @code{set target-charset} followed by @key{TAB}@key{TAB},
10811 @value{GDBN} tells us the character sets it supports:
10814 (@value{GDBP}) set target-charset
10815 ASCII EBCDIC-US IBM1047 ISO-8859-1
10816 (@value{GDBP}) set target-charset
10819 We can select @sc{ibm1047} as our target character set, and examine the
10820 program's strings again. Now the @sc{ascii} string is wrong, but
10821 @value{GDBN} translates the contents of @code{ibm1047_hello} from the
10822 target character set, @sc{ibm1047}, to the host character set,
10823 @sc{ascii}, and they display correctly:
10826 (@value{GDBP}) set target-charset IBM1047
10827 (@value{GDBP}) show charset
10828 The current host character set is `ASCII'.
10829 The current target character set is `IBM1047'.
10830 (@value{GDBP}) print ascii_hello
10831 $6 = 0x401698 "\110\145%%?\054\040\167?\162%\144\041\012"
10832 (@value{GDBP}) print ascii_hello[0]
10834 (@value{GDBP}) print ibm1047_hello
10835 $8 = 0x4016a8 "Hello, world!\n"
10836 (@value{GDBP}) print ibm1047_hello[0]
10841 As above, @value{GDBN} uses the target character set for character and
10842 string literals you use in expressions:
10845 (@value{GDBP}) print '+'
10850 The @sc{ibm1047} character set uses the number 78 to encode the @samp{+}
10853 @node Caching Target Data
10854 @section Caching Data of Targets
10855 @cindex caching data of targets
10857 @value{GDBN} caches data exchanged between the debugger and a target.
10858 Each cache is associated with the address space of the inferior.
10859 @xref{Inferiors and Programs}, about inferior and address space.
10860 Such caching generally improves performance in remote debugging
10861 (@pxref{Remote Debugging}), because it reduces the overhead of the
10862 remote protocol by bundling memory reads and writes into large chunks.
10863 Unfortunately, simply caching everything would lead to incorrect results,
10864 since @value{GDBN} does not necessarily know anything about volatile
10865 values, memory-mapped I/O addresses, etc. Furthermore, in non-stop mode
10866 (@pxref{Non-Stop Mode}) memory can be changed @emph{while} a gdb command
10868 Therefore, by default, @value{GDBN} only caches data
10869 known to be on the stack@footnote{In non-stop mode, it is moderately
10870 rare for a running thread to modify the stack of a stopped thread
10871 in a way that would interfere with a backtrace, and caching of
10872 stack reads provides a significant speed up of remote backtraces.} or
10873 in the code segment.
10874 Other regions of memory can be explicitly marked as
10875 cacheable; @pxref{Memory Region Attributes}.
10878 @kindex set remotecache
10879 @item set remotecache on
10880 @itemx set remotecache off
10881 This option no longer does anything; it exists for compatibility
10884 @kindex show remotecache
10885 @item show remotecache
10886 Show the current state of the obsolete remotecache flag.
10888 @kindex set stack-cache
10889 @item set stack-cache on
10890 @itemx set stack-cache off
10891 Enable or disable caching of stack accesses. When @code{on}, use
10892 caching. By default, this option is @code{on}.
10894 @kindex show stack-cache
10895 @item show stack-cache
10896 Show the current state of data caching for memory accesses.
10898 @kindex set code-cache
10899 @item set code-cache on
10900 @itemx set code-cache off
10901 Enable or disable caching of code segment accesses. When @code{on},
10902 use caching. By default, this option is @code{on}. This improves
10903 performance of disassembly in remote debugging.
10905 @kindex show code-cache
10906 @item show code-cache
10907 Show the current state of target memory cache for code segment
10910 @kindex info dcache
10911 @item info dcache @r{[}line@r{]}
10912 Print the information about the performance of data cache of the
10913 current inferior's address space. The information displayed
10914 includes the dcache width and depth, and for each cache line, its
10915 number, address, and how many times it was referenced. This
10916 command is useful for debugging the data cache operation.
10918 If a line number is specified, the contents of that line will be
10921 @item set dcache size @var{size}
10922 @cindex dcache size
10923 @kindex set dcache size
10924 Set maximum number of entries in dcache (dcache depth above).
10926 @item set dcache line-size @var{line-size}
10927 @cindex dcache line-size
10928 @kindex set dcache line-size
10929 Set number of bytes each dcache entry caches (dcache width above).
10930 Must be a power of 2.
10932 @item show dcache size
10933 @kindex show dcache size
10934 Show maximum number of dcache entries. @xref{Caching Target Data, info dcache}.
10936 @item show dcache line-size
10937 @kindex show dcache line-size
10938 Show default size of dcache lines.
10942 @node Searching Memory
10943 @section Search Memory
10944 @cindex searching memory
10946 Memory can be searched for a particular sequence of bytes with the
10947 @code{find} command.
10951 @item find @r{[}/@var{sn}@r{]} @var{start_addr}, +@var{len}, @var{val1} @r{[}, @var{val2}, @dots{}@r{]}
10952 @itemx find @r{[}/@var{sn}@r{]} @var{start_addr}, @var{end_addr}, @var{val1} @r{[}, @var{val2}, @dots{}@r{]}
10953 Search memory for the sequence of bytes specified by @var{val1}, @var{val2},
10954 etc. The search begins at address @var{start_addr} and continues for either
10955 @var{len} bytes or through to @var{end_addr} inclusive.
10958 @var{s} and @var{n} are optional parameters.
10959 They may be specified in either order, apart or together.
10962 @item @var{s}, search query size
10963 The size of each search query value.
10969 halfwords (two bytes)
10973 giant words (eight bytes)
10976 All values are interpreted in the current language.
10977 This means, for example, that if the current source language is C/C@t{++}
10978 then searching for the string ``hello'' includes the trailing '\0'.
10980 If the value size is not specified, it is taken from the
10981 value's type in the current language.
10982 This is useful when one wants to specify the search
10983 pattern as a mixture of types.
10984 Note that this means, for example, that in the case of C-like languages
10985 a search for an untyped 0x42 will search for @samp{(int) 0x42}
10986 which is typically four bytes.
10988 @item @var{n}, maximum number of finds
10989 The maximum number of matches to print. The default is to print all finds.
10992 You can use strings as search values. Quote them with double-quotes
10994 The string value is copied into the search pattern byte by byte,
10995 regardless of the endianness of the target and the size specification.
10997 The address of each match found is printed as well as a count of the
10998 number of matches found.
11000 The address of the last value found is stored in convenience variable
11002 A count of the number of matches is stored in @samp{$numfound}.
11004 For example, if stopped at the @code{printf} in this function:
11010 static char hello[] = "hello-hello";
11011 static struct @{ char c; short s; int i; @}
11012 __attribute__ ((packed)) mixed
11013 = @{ 'c', 0x1234, 0x87654321 @};
11014 printf ("%s\n", hello);
11019 you get during debugging:
11022 (gdb) find &hello[0], +sizeof(hello), "hello"
11023 0x804956d <hello.1620+6>
11025 (gdb) find &hello[0], +sizeof(hello), 'h', 'e', 'l', 'l', 'o'
11026 0x8049567 <hello.1620>
11027 0x804956d <hello.1620+6>
11029 (gdb) find /b1 &hello[0], +sizeof(hello), 'h', 0x65, 'l'
11030 0x8049567 <hello.1620>
11032 (gdb) find &mixed, +sizeof(mixed), (char) 'c', (short) 0x1234, (int) 0x87654321
11033 0x8049560 <mixed.1625>
11035 (gdb) print $numfound
11038 $2 = (void *) 0x8049560
11041 @node Optimized Code
11042 @chapter Debugging Optimized Code
11043 @cindex optimized code, debugging
11044 @cindex debugging optimized code
11046 Almost all compilers support optimization. With optimization
11047 disabled, the compiler generates assembly code that corresponds
11048 directly to your source code, in a simplistic way. As the compiler
11049 applies more powerful optimizations, the generated assembly code
11050 diverges from your original source code. With help from debugging
11051 information generated by the compiler, @value{GDBN} can map from
11052 the running program back to constructs from your original source.
11054 @value{GDBN} is more accurate with optimization disabled. If you
11055 can recompile without optimization, it is easier to follow the
11056 progress of your program during debugging. But, there are many cases
11057 where you may need to debug an optimized version.
11059 When you debug a program compiled with @samp{-g -O}, remember that the
11060 optimizer has rearranged your code; the debugger shows you what is
11061 really there. Do not be too surprised when the execution path does not
11062 exactly match your source file! An extreme example: if you define a
11063 variable, but never use it, @value{GDBN} never sees that
11064 variable---because the compiler optimizes it out of existence.
11066 Some things do not work as well with @samp{-g -O} as with just
11067 @samp{-g}, particularly on machines with instruction scheduling. If in
11068 doubt, recompile with @samp{-g} alone, and if this fixes the problem,
11069 please report it to us as a bug (including a test case!).
11070 @xref{Variables}, for more information about debugging optimized code.
11073 * Inline Functions:: How @value{GDBN} presents inlining
11074 * Tail Call Frames:: @value{GDBN} analysis of jumps to functions
11077 @node Inline Functions
11078 @section Inline Functions
11079 @cindex inline functions, debugging
11081 @dfn{Inlining} is an optimization that inserts a copy of the function
11082 body directly at each call site, instead of jumping to a shared
11083 routine. @value{GDBN} displays inlined functions just like
11084 non-inlined functions. They appear in backtraces. You can view their
11085 arguments and local variables, step into them with @code{step}, skip
11086 them with @code{next}, and escape from them with @code{finish}.
11087 You can check whether a function was inlined by using the
11088 @code{info frame} command.
11090 For @value{GDBN} to support inlined functions, the compiler must
11091 record information about inlining in the debug information ---
11092 @value{NGCC} using the @sc{dwarf 2} format does this, and several
11093 other compilers do also. @value{GDBN} only supports inlined functions
11094 when using @sc{dwarf 2}. Versions of @value{NGCC} before 4.1
11095 do not emit two required attributes (@samp{DW_AT_call_file} and
11096 @samp{DW_AT_call_line}); @value{GDBN} does not display inlined
11097 function calls with earlier versions of @value{NGCC}. It instead
11098 displays the arguments and local variables of inlined functions as
11099 local variables in the caller.
11101 The body of an inlined function is directly included at its call site;
11102 unlike a non-inlined function, there are no instructions devoted to
11103 the call. @value{GDBN} still pretends that the call site and the
11104 start of the inlined function are different instructions. Stepping to
11105 the call site shows the call site, and then stepping again shows
11106 the first line of the inlined function, even though no additional
11107 instructions are executed.
11109 This makes source-level debugging much clearer; you can see both the
11110 context of the call and then the effect of the call. Only stepping by
11111 a single instruction using @code{stepi} or @code{nexti} does not do
11112 this; single instruction steps always show the inlined body.
11114 There are some ways that @value{GDBN} does not pretend that inlined
11115 function calls are the same as normal calls:
11119 Setting breakpoints at the call site of an inlined function may not
11120 work, because the call site does not contain any code. @value{GDBN}
11121 may incorrectly move the breakpoint to the next line of the enclosing
11122 function, after the call. This limitation will be removed in a future
11123 version of @value{GDBN}; until then, set a breakpoint on an earlier line
11124 or inside the inlined function instead.
11127 @value{GDBN} cannot locate the return value of inlined calls after
11128 using the @code{finish} command. This is a limitation of compiler-generated
11129 debugging information; after @code{finish}, you can step to the next line
11130 and print a variable where your program stored the return value.
11134 @node Tail Call Frames
11135 @section Tail Call Frames
11136 @cindex tail call frames, debugging
11138 Function @code{B} can call function @code{C} in its very last statement. In
11139 unoptimized compilation the call of @code{C} is immediately followed by return
11140 instruction at the end of @code{B} code. Optimizing compiler may replace the
11141 call and return in function @code{B} into one jump to function @code{C}
11142 instead. Such use of a jump instruction is called @dfn{tail call}.
11144 During execution of function @code{C}, there will be no indication in the
11145 function call stack frames that it was tail-called from @code{B}. If function
11146 @code{A} regularly calls function @code{B} which tail-calls function @code{C},
11147 then @value{GDBN} will see @code{A} as the caller of @code{C}. However, in
11148 some cases @value{GDBN} can determine that @code{C} was tail-called from
11149 @code{B}, and it will then create fictitious call frame for that, with the
11150 return address set up as if @code{B} called @code{C} normally.
11152 This functionality is currently supported only by DWARF 2 debugging format and
11153 the compiler has to produce @samp{DW_TAG_GNU_call_site} tags. With
11154 @value{NGCC}, you need to specify @option{-O -g} during compilation, to get
11157 @kbd{info frame} command (@pxref{Frame Info}) will indicate the tail call frame
11158 kind by text @code{tail call frame} such as in this sample @value{GDBN} output:
11162 0x40066b <b(int, double)+11>: jmp 0x400640 <c(int, double)>
11164 Stack level 1, frame at 0x7fffffffda30:
11165 rip = 0x40066d in b (amd64-entry-value.cc:59); saved rip 0x4004c5
11166 tail call frame, caller of frame at 0x7fffffffda30
11167 source language c++.
11168 Arglist at unknown address.
11169 Locals at unknown address, Previous frame's sp is 0x7fffffffda30
11172 The detection of all the possible code path executions can find them ambiguous.
11173 There is no execution history stored (possible @ref{Reverse Execution} is never
11174 used for this purpose) and the last known caller could have reached the known
11175 callee by multiple different jump sequences. In such case @value{GDBN} still
11176 tries to show at least all the unambiguous top tail callers and all the
11177 unambiguous bottom tail calees, if any.
11180 @anchor{set debug entry-values}
11181 @item set debug entry-values
11182 @kindex set debug entry-values
11183 When set to on, enables printing of analysis messages for both frame argument
11184 values at function entry and tail calls. It will show all the possible valid
11185 tail calls code paths it has considered. It will also print the intersection
11186 of them with the final unambiguous (possibly partial or even empty) code path
11189 @item show debug entry-values
11190 @kindex show debug entry-values
11191 Show the current state of analysis messages printing for both frame argument
11192 values at function entry and tail calls.
11195 The analysis messages for tail calls can for example show why the virtual tail
11196 call frame for function @code{c} has not been recognized (due to the indirect
11197 reference by variable @code{x}):
11200 static void __attribute__((noinline, noclone)) c (void);
11201 void (*x) (void) = c;
11202 static void __attribute__((noinline, noclone)) a (void) @{ x++; @}
11203 static void __attribute__((noinline, noclone)) c (void) @{ a (); @}
11204 int main (void) @{ x (); return 0; @}
11206 Breakpoint 1, DW_OP_GNU_entry_value resolving cannot find
11207 DW_TAG_GNU_call_site 0x40039a in main
11209 3 static void __attribute__((noinline, noclone)) a (void) @{ x++; @}
11212 #1 0x000000000040039a in main () at t.c:5
11215 Another possibility is an ambiguous virtual tail call frames resolution:
11219 static void __attribute__((noinline, noclone)) f (void) @{ i++; @}
11220 static void __attribute__((noinline, noclone)) e (void) @{ f (); @}
11221 static void __attribute__((noinline, noclone)) d (void) @{ f (); @}
11222 static void __attribute__((noinline, noclone)) c (void) @{ d (); @}
11223 static void __attribute__((noinline, noclone)) b (void)
11224 @{ if (i) c (); else e (); @}
11225 static void __attribute__((noinline, noclone)) a (void) @{ b (); @}
11226 int main (void) @{ a (); return 0; @}
11228 tailcall: initial: 0x4004d2(a) 0x4004ce(b) 0x4004b2(c) 0x4004a2(d)
11229 tailcall: compare: 0x4004d2(a) 0x4004cc(b) 0x400492(e)
11230 tailcall: reduced: 0x4004d2(a) |
11233 #1 0x00000000004004d2 in a () at t.c:8
11234 #2 0x0000000000400395 in main () at t.c:9
11237 @set CALLSEQ1A @code{main@value{ARROW}a@value{ARROW}b@value{ARROW}c@value{ARROW}d@value{ARROW}f}
11238 @set CALLSEQ2A @code{main@value{ARROW}a@value{ARROW}b@value{ARROW}e@value{ARROW}f}
11240 @c Convert CALLSEQ#A to CALLSEQ#B depending on HAVE_MAKEINFO_CLICK.
11241 @ifset HAVE_MAKEINFO_CLICK
11242 @set ARROW @click{}
11243 @set CALLSEQ1B @clicksequence{@value{CALLSEQ1A}}
11244 @set CALLSEQ2B @clicksequence{@value{CALLSEQ2A}}
11246 @ifclear HAVE_MAKEINFO_CLICK
11248 @set CALLSEQ1B @value{CALLSEQ1A}
11249 @set CALLSEQ2B @value{CALLSEQ2A}
11252 Frames #0 and #2 are real, #1 is a virtual tail call frame.
11253 The code can have possible execution paths @value{CALLSEQ1B} or
11254 @value{CALLSEQ2B}, @value{GDBN} cannot find which one from the inferior state.
11256 @code{initial:} state shows some random possible calling sequence @value{GDBN}
11257 has found. It then finds another possible calling sequcen - that one is
11258 prefixed by @code{compare:}. The non-ambiguous intersection of these two is
11259 printed as the @code{reduced:} calling sequence. That one could have many
11260 futher @code{compare:} and @code{reduced:} statements as long as there remain
11261 any non-ambiguous sequence entries.
11263 For the frame of function @code{b} in both cases there are different possible
11264 @code{$pc} values (@code{0x4004cc} or @code{0x4004ce}), therefore this frame is
11265 also ambigous. The only non-ambiguous frame is the one for function @code{a},
11266 therefore this one is displayed to the user while the ambiguous frames are
11269 There can be also reasons why printing of frame argument values at function
11274 static void __attribute__((noinline, noclone)) c (int i) @{ v++; @}
11275 static void __attribute__((noinline, noclone)) a (int i);
11276 static void __attribute__((noinline, noclone)) b (int i) @{ a (i); @}
11277 static void __attribute__((noinline, noclone)) a (int i)
11278 @{ if (i) b (i - 1); else c (0); @}
11279 int main (void) @{ a (5); return 0; @}
11282 #0 c (i=i@@entry=0) at t.c:2
11283 #1 0x0000000000400428 in a (DW_OP_GNU_entry_value resolving has found
11284 function "a" at 0x400420 can call itself via tail calls
11285 i=<optimized out>) at t.c:6
11286 #2 0x000000000040036e in main () at t.c:7
11289 @value{GDBN} cannot find out from the inferior state if and how many times did
11290 function @code{a} call itself (via function @code{b}) as these calls would be
11291 tail calls. Such tail calls would modify thue @code{i} variable, therefore
11292 @value{GDBN} cannot be sure the value it knows would be right - @value{GDBN}
11293 prints @code{<optimized out>} instead.
11296 @chapter C Preprocessor Macros
11298 Some languages, such as C and C@t{++}, provide a way to define and invoke
11299 ``preprocessor macros'' which expand into strings of tokens.
11300 @value{GDBN} can evaluate expressions containing macro invocations, show
11301 the result of macro expansion, and show a macro's definition, including
11302 where it was defined.
11304 You may need to compile your program specially to provide @value{GDBN}
11305 with information about preprocessor macros. Most compilers do not
11306 include macros in their debugging information, even when you compile
11307 with the @option{-g} flag. @xref{Compilation}.
11309 A program may define a macro at one point, remove that definition later,
11310 and then provide a different definition after that. Thus, at different
11311 points in the program, a macro may have different definitions, or have
11312 no definition at all. If there is a current stack frame, @value{GDBN}
11313 uses the macros in scope at that frame's source code line. Otherwise,
11314 @value{GDBN} uses the macros in scope at the current listing location;
11317 Whenever @value{GDBN} evaluates an expression, it always expands any
11318 macro invocations present in the expression. @value{GDBN} also provides
11319 the following commands for working with macros explicitly.
11323 @kindex macro expand
11324 @cindex macro expansion, showing the results of preprocessor
11325 @cindex preprocessor macro expansion, showing the results of
11326 @cindex expanding preprocessor macros
11327 @item macro expand @var{expression}
11328 @itemx macro exp @var{expression}
11329 Show the results of expanding all preprocessor macro invocations in
11330 @var{expression}. Since @value{GDBN} simply expands macros, but does
11331 not parse the result, @var{expression} need not be a valid expression;
11332 it can be any string of tokens.
11335 @item macro expand-once @var{expression}
11336 @itemx macro exp1 @var{expression}
11337 @cindex expand macro once
11338 @i{(This command is not yet implemented.)} Show the results of
11339 expanding those preprocessor macro invocations that appear explicitly in
11340 @var{expression}. Macro invocations appearing in that expansion are
11341 left unchanged. This command allows you to see the effect of a
11342 particular macro more clearly, without being confused by further
11343 expansions. Since @value{GDBN} simply expands macros, but does not
11344 parse the result, @var{expression} need not be a valid expression; it
11345 can be any string of tokens.
11348 @cindex macro definition, showing
11349 @cindex definition of a macro, showing
11350 @cindex macros, from debug info
11351 @item info macro [-a|-all] [--] @var{macro}
11352 Show the current definition or all definitions of the named @var{macro},
11353 and describe the source location or compiler command-line where that
11354 definition was established. The optional double dash is to signify the end of
11355 argument processing and the beginning of @var{macro} for non C-like macros where
11356 the macro may begin with a hyphen.
11358 @kindex info macros
11359 @item info macros @var{linespec}
11360 Show all macro definitions that are in effect at the location specified
11361 by @var{linespec}, and describe the source location or compiler
11362 command-line where those definitions were established.
11364 @kindex macro define
11365 @cindex user-defined macros
11366 @cindex defining macros interactively
11367 @cindex macros, user-defined
11368 @item macro define @var{macro} @var{replacement-list}
11369 @itemx macro define @var{macro}(@var{arglist}) @var{replacement-list}
11370 Introduce a definition for a preprocessor macro named @var{macro},
11371 invocations of which are replaced by the tokens given in
11372 @var{replacement-list}. The first form of this command defines an
11373 ``object-like'' macro, which takes no arguments; the second form
11374 defines a ``function-like'' macro, which takes the arguments given in
11377 A definition introduced by this command is in scope in every
11378 expression evaluated in @value{GDBN}, until it is removed with the
11379 @code{macro undef} command, described below. The definition overrides
11380 all definitions for @var{macro} present in the program being debugged,
11381 as well as any previous user-supplied definition.
11383 @kindex macro undef
11384 @item macro undef @var{macro}
11385 Remove any user-supplied definition for the macro named @var{macro}.
11386 This command only affects definitions provided with the @code{macro
11387 define} command, described above; it cannot remove definitions present
11388 in the program being debugged.
11392 List all the macros defined using the @code{macro define} command.
11395 @cindex macros, example of debugging with
11396 Here is a transcript showing the above commands in action. First, we
11397 show our source files:
11402 #include "sample.h"
11405 #define ADD(x) (M + x)
11410 printf ("Hello, world!\n");
11412 printf ("We're so creative.\n");
11414 printf ("Goodbye, world!\n");
11421 Now, we compile the program using the @sc{gnu} C compiler,
11422 @value{NGCC}. We pass the @option{-gdwarf-2}@footnote{This is the
11423 minimum. Recent versions of @value{NGCC} support @option{-gdwarf-3}
11424 and @option{-gdwarf-4}; we recommend always choosing the most recent
11425 version of DWARF.} @emph{and} @option{-g3} flags to ensure the compiler
11426 includes information about preprocessor macros in the debugging
11430 $ gcc -gdwarf-2 -g3 sample.c -o sample
11434 Now, we start @value{GDBN} on our sample program:
11438 GNU gdb 2002-05-06-cvs
11439 Copyright 2002 Free Software Foundation, Inc.
11440 GDB is free software, @dots{}
11444 We can expand macros and examine their definitions, even when the
11445 program is not running. @value{GDBN} uses the current listing position
11446 to decide which macro definitions are in scope:
11449 (@value{GDBP}) list main
11452 5 #define ADD(x) (M + x)
11457 10 printf ("Hello, world!\n");
11459 12 printf ("We're so creative.\n");
11460 (@value{GDBP}) info macro ADD
11461 Defined at /home/jimb/gdb/macros/play/sample.c:5
11462 #define ADD(x) (M + x)
11463 (@value{GDBP}) info macro Q
11464 Defined at /home/jimb/gdb/macros/play/sample.h:1
11465 included at /home/jimb/gdb/macros/play/sample.c:2
11467 (@value{GDBP}) macro expand ADD(1)
11468 expands to: (42 + 1)
11469 (@value{GDBP}) macro expand-once ADD(1)
11470 expands to: once (M + 1)
11474 In the example above, note that @code{macro expand-once} expands only
11475 the macro invocation explicit in the original text --- the invocation of
11476 @code{ADD} --- but does not expand the invocation of the macro @code{M},
11477 which was introduced by @code{ADD}.
11479 Once the program is running, @value{GDBN} uses the macro definitions in
11480 force at the source line of the current stack frame:
11483 (@value{GDBP}) break main
11484 Breakpoint 1 at 0x8048370: file sample.c, line 10.
11486 Starting program: /home/jimb/gdb/macros/play/sample
11488 Breakpoint 1, main () at sample.c:10
11489 10 printf ("Hello, world!\n");
11493 At line 10, the definition of the macro @code{N} at line 9 is in force:
11496 (@value{GDBP}) info macro N
11497 Defined at /home/jimb/gdb/macros/play/sample.c:9
11499 (@value{GDBP}) macro expand N Q M
11500 expands to: 28 < 42
11501 (@value{GDBP}) print N Q M
11506 As we step over directives that remove @code{N}'s definition, and then
11507 give it a new definition, @value{GDBN} finds the definition (or lack
11508 thereof) in force at each point:
11511 (@value{GDBP}) next
11513 12 printf ("We're so creative.\n");
11514 (@value{GDBP}) info macro N
11515 The symbol `N' has no definition as a C/C++ preprocessor macro
11516 at /home/jimb/gdb/macros/play/sample.c:12
11517 (@value{GDBP}) next
11519 14 printf ("Goodbye, world!\n");
11520 (@value{GDBP}) info macro N
11521 Defined at /home/jimb/gdb/macros/play/sample.c:13
11523 (@value{GDBP}) macro expand N Q M
11524 expands to: 1729 < 42
11525 (@value{GDBP}) print N Q M
11530 In addition to source files, macros can be defined on the compilation command
11531 line using the @option{-D@var{name}=@var{value}} syntax. For macros defined in
11532 such a way, @value{GDBN} displays the location of their definition as line zero
11533 of the source file submitted to the compiler.
11536 (@value{GDBP}) info macro __STDC__
11537 Defined at /home/jimb/gdb/macros/play/sample.c:0
11544 @chapter Tracepoints
11545 @c This chapter is based on the documentation written by Michael
11546 @c Snyder, David Taylor, Jim Blandy, and Elena Zannoni.
11548 @cindex tracepoints
11549 In some applications, it is not feasible for the debugger to interrupt
11550 the program's execution long enough for the developer to learn
11551 anything helpful about its behavior. If the program's correctness
11552 depends on its real-time behavior, delays introduced by a debugger
11553 might cause the program to change its behavior drastically, or perhaps
11554 fail, even when the code itself is correct. It is useful to be able
11555 to observe the program's behavior without interrupting it.
11557 Using @value{GDBN}'s @code{trace} and @code{collect} commands, you can
11558 specify locations in the program, called @dfn{tracepoints}, and
11559 arbitrary expressions to evaluate when those tracepoints are reached.
11560 Later, using the @code{tfind} command, you can examine the values
11561 those expressions had when the program hit the tracepoints. The
11562 expressions may also denote objects in memory---structures or arrays,
11563 for example---whose values @value{GDBN} should record; while visiting
11564 a particular tracepoint, you may inspect those objects as if they were
11565 in memory at that moment. However, because @value{GDBN} records these
11566 values without interacting with you, it can do so quickly and
11567 unobtrusively, hopefully not disturbing the program's behavior.
11569 The tracepoint facility is currently available only for remote
11570 targets. @xref{Targets}. In addition, your remote target must know
11571 how to collect trace data. This functionality is implemented in the
11572 remote stub; however, none of the stubs distributed with @value{GDBN}
11573 support tracepoints as of this writing. The format of the remote
11574 packets used to implement tracepoints are described in @ref{Tracepoint
11577 It is also possible to get trace data from a file, in a manner reminiscent
11578 of corefiles; you specify the filename, and use @code{tfind} to search
11579 through the file. @xref{Trace Files}, for more details.
11581 This chapter describes the tracepoint commands and features.
11584 * Set Tracepoints::
11585 * Analyze Collected Data::
11586 * Tracepoint Variables::
11590 @node Set Tracepoints
11591 @section Commands to Set Tracepoints
11593 Before running such a @dfn{trace experiment}, an arbitrary number of
11594 tracepoints can be set. A tracepoint is actually a special type of
11595 breakpoint (@pxref{Set Breaks}), so you can manipulate it using
11596 standard breakpoint commands. For instance, as with breakpoints,
11597 tracepoint numbers are successive integers starting from one, and many
11598 of the commands associated with tracepoints take the tracepoint number
11599 as their argument, to identify which tracepoint to work on.
11601 For each tracepoint, you can specify, in advance, some arbitrary set
11602 of data that you want the target to collect in the trace buffer when
11603 it hits that tracepoint. The collected data can include registers,
11604 local variables, or global data. Later, you can use @value{GDBN}
11605 commands to examine the values these data had at the time the
11606 tracepoint was hit.
11608 Tracepoints do not support every breakpoint feature. Ignore counts on
11609 tracepoints have no effect, and tracepoints cannot run @value{GDBN}
11610 commands when they are hit. Tracepoints may not be thread-specific
11613 @cindex fast tracepoints
11614 Some targets may support @dfn{fast tracepoints}, which are inserted in
11615 a different way (such as with a jump instead of a trap), that is
11616 faster but possibly restricted in where they may be installed.
11618 @cindex static tracepoints
11619 @cindex markers, static tracepoints
11620 @cindex probing markers, static tracepoints
11621 Regular and fast tracepoints are dynamic tracing facilities, meaning
11622 that they can be used to insert tracepoints at (almost) any location
11623 in the target. Some targets may also support controlling @dfn{static
11624 tracepoints} from @value{GDBN}. With static tracing, a set of
11625 instrumentation points, also known as @dfn{markers}, are embedded in
11626 the target program, and can be activated or deactivated by name or
11627 address. These are usually placed at locations which facilitate
11628 investigating what the target is actually doing. @value{GDBN}'s
11629 support for static tracing includes being able to list instrumentation
11630 points, and attach them with @value{GDBN} defined high level
11631 tracepoints that expose the whole range of convenience of
11632 @value{GDBN}'s tracepoints support. Namely, support for collecting
11633 registers values and values of global or local (to the instrumentation
11634 point) variables; tracepoint conditions and trace state variables.
11635 The act of installing a @value{GDBN} static tracepoint on an
11636 instrumentation point, or marker, is referred to as @dfn{probing} a
11637 static tracepoint marker.
11639 @code{gdbserver} supports tracepoints on some target systems.
11640 @xref{Server,,Tracepoints support in @code{gdbserver}}.
11642 This section describes commands to set tracepoints and associated
11643 conditions and actions.
11646 * Create and Delete Tracepoints::
11647 * Enable and Disable Tracepoints::
11648 * Tracepoint Passcounts::
11649 * Tracepoint Conditions::
11650 * Trace State Variables::
11651 * Tracepoint Actions::
11652 * Listing Tracepoints::
11653 * Listing Static Tracepoint Markers::
11654 * Starting and Stopping Trace Experiments::
11655 * Tracepoint Restrictions::
11658 @node Create and Delete Tracepoints
11659 @subsection Create and Delete Tracepoints
11662 @cindex set tracepoint
11664 @item trace @var{location}
11665 The @code{trace} command is very similar to the @code{break} command.
11666 Its argument @var{location} can be a source line, a function name, or
11667 an address in the target program. @xref{Specify Location}. The
11668 @code{trace} command defines a tracepoint, which is a point in the
11669 target program where the debugger will briefly stop, collect some
11670 data, and then allow the program to continue. Setting a tracepoint or
11671 changing its actions takes effect immediately if the remote stub
11672 supports the @samp{InstallInTrace} feature (@pxref{install tracepoint
11674 If remote stub doesn't support the @samp{InstallInTrace} feature, all
11675 these changes don't take effect until the next @code{tstart}
11676 command, and once a trace experiment is running, further changes will
11677 not have any effect until the next trace experiment starts. In addition,
11678 @value{GDBN} supports @dfn{pending tracepoints}---tracepoints whose
11679 address is not yet resolved. (This is similar to pending breakpoints.)
11680 Pending tracepoints are not downloaded to the target and not installed
11681 until they are resolved. The resolution of pending tracepoints requires
11682 @value{GDBN} support---when debugging with the remote target, and
11683 @value{GDBN} disconnects from the remote stub (@pxref{disconnected
11684 tracing}), pending tracepoints can not be resolved (and downloaded to
11685 the remote stub) while @value{GDBN} is disconnected.
11687 Here are some examples of using the @code{trace} command:
11690 (@value{GDBP}) @b{trace foo.c:121} // a source file and line number
11692 (@value{GDBP}) @b{trace +2} // 2 lines forward
11694 (@value{GDBP}) @b{trace my_function} // first source line of function
11696 (@value{GDBP}) @b{trace *my_function} // EXACT start address of function
11698 (@value{GDBP}) @b{trace *0x2117c4} // an address
11702 You can abbreviate @code{trace} as @code{tr}.
11704 @item trace @var{location} if @var{cond}
11705 Set a tracepoint with condition @var{cond}; evaluate the expression
11706 @var{cond} each time the tracepoint is reached, and collect data only
11707 if the value is nonzero---that is, if @var{cond} evaluates as true.
11708 @xref{Tracepoint Conditions, ,Tracepoint Conditions}, for more
11709 information on tracepoint conditions.
11711 @item ftrace @var{location} [ if @var{cond} ]
11712 @cindex set fast tracepoint
11713 @cindex fast tracepoints, setting
11715 The @code{ftrace} command sets a fast tracepoint. For targets that
11716 support them, fast tracepoints will use a more efficient but possibly
11717 less general technique to trigger data collection, such as a jump
11718 instruction instead of a trap, or some sort of hardware support. It
11719 may not be possible to create a fast tracepoint at the desired
11720 location, in which case the command will exit with an explanatory
11723 @value{GDBN} handles arguments to @code{ftrace} exactly as for
11726 On 32-bit x86-architecture systems, fast tracepoints normally need to
11727 be placed at an instruction that is 5 bytes or longer, but can be
11728 placed at 4-byte instructions if the low 64K of memory of the target
11729 program is available to install trampolines. Some Unix-type systems,
11730 such as @sc{gnu}/Linux, exclude low addresses from the program's
11731 address space; but for instance with the Linux kernel it is possible
11732 to let @value{GDBN} use this area by doing a @command{sysctl} command
11733 to set the @code{mmap_min_addr} kernel parameter, as in
11736 sudo sysctl -w vm.mmap_min_addr=32768
11740 which sets the low address to 32K, which leaves plenty of room for
11741 trampolines. The minimum address should be set to a page boundary.
11743 @item strace @var{location} [ if @var{cond} ]
11744 @cindex set static tracepoint
11745 @cindex static tracepoints, setting
11746 @cindex probe static tracepoint marker
11748 The @code{strace} command sets a static tracepoint. For targets that
11749 support it, setting a static tracepoint probes a static
11750 instrumentation point, or marker, found at @var{location}. It may not
11751 be possible to set a static tracepoint at the desired location, in
11752 which case the command will exit with an explanatory message.
11754 @value{GDBN} handles arguments to @code{strace} exactly as for
11755 @code{trace}, with the addition that the user can also specify
11756 @code{-m @var{marker}} as @var{location}. This probes the marker
11757 identified by the @var{marker} string identifier. This identifier
11758 depends on the static tracepoint backend library your program is
11759 using. You can find all the marker identifiers in the @samp{ID} field
11760 of the @code{info static-tracepoint-markers} command output.
11761 @xref{Listing Static Tracepoint Markers,,Listing Static Tracepoint
11762 Markers}. For example, in the following small program using the UST
11768 trace_mark(ust, bar33, "str %s", "FOOBAZ");
11773 the marker id is composed of joining the first two arguments to the
11774 @code{trace_mark} call with a slash, which translates to:
11777 (@value{GDBP}) info static-tracepoint-markers
11778 Cnt Enb ID Address What
11779 1 n ust/bar33 0x0000000000400ddc in main at stexample.c:22
11785 so you may probe the marker above with:
11788 (@value{GDBP}) strace -m ust/bar33
11791 Static tracepoints accept an extra collect action --- @code{collect
11792 $_sdata}. This collects arbitrary user data passed in the probe point
11793 call to the tracing library. In the UST example above, you'll see
11794 that the third argument to @code{trace_mark} is a printf-like format
11795 string. The user data is then the result of running that formating
11796 string against the following arguments. Note that @code{info
11797 static-tracepoint-markers} command output lists that format string in
11798 the @samp{Data:} field.
11800 You can inspect this data when analyzing the trace buffer, by printing
11801 the $_sdata variable like any other variable available to
11802 @value{GDBN}. @xref{Tracepoint Actions,,Tracepoint Action Lists}.
11805 @cindex last tracepoint number
11806 @cindex recent tracepoint number
11807 @cindex tracepoint number
11808 The convenience variable @code{$tpnum} records the tracepoint number
11809 of the most recently set tracepoint.
11811 @kindex delete tracepoint
11812 @cindex tracepoint deletion
11813 @item delete tracepoint @r{[}@var{num}@r{]}
11814 Permanently delete one or more tracepoints. With no argument, the
11815 default is to delete all tracepoints. Note that the regular
11816 @code{delete} command can remove tracepoints also.
11821 (@value{GDBP}) @b{delete trace 1 2 3} // remove three tracepoints
11823 (@value{GDBP}) @b{delete trace} // remove all tracepoints
11827 You can abbreviate this command as @code{del tr}.
11830 @node Enable and Disable Tracepoints
11831 @subsection Enable and Disable Tracepoints
11833 These commands are deprecated; they are equivalent to plain @code{disable} and @code{enable}.
11836 @kindex disable tracepoint
11837 @item disable tracepoint @r{[}@var{num}@r{]}
11838 Disable tracepoint @var{num}, or all tracepoints if no argument
11839 @var{num} is given. A disabled tracepoint will have no effect during
11840 a trace experiment, but it is not forgotten. You can re-enable
11841 a disabled tracepoint using the @code{enable tracepoint} command.
11842 If the command is issued during a trace experiment and the debug target
11843 has support for disabling tracepoints during a trace experiment, then the
11844 change will be effective immediately. Otherwise, it will be applied to the
11845 next trace experiment.
11847 @kindex enable tracepoint
11848 @item enable tracepoint @r{[}@var{num}@r{]}
11849 Enable tracepoint @var{num}, or all tracepoints. If this command is
11850 issued during a trace experiment and the debug target supports enabling
11851 tracepoints during a trace experiment, then the enabled tracepoints will
11852 become effective immediately. Otherwise, they will become effective the
11853 next time a trace experiment is run.
11856 @node Tracepoint Passcounts
11857 @subsection Tracepoint Passcounts
11861 @cindex tracepoint pass count
11862 @item passcount @r{[}@var{n} @r{[}@var{num}@r{]]}
11863 Set the @dfn{passcount} of a tracepoint. The passcount is a way to
11864 automatically stop a trace experiment. If a tracepoint's passcount is
11865 @var{n}, then the trace experiment will be automatically stopped on
11866 the @var{n}'th time that tracepoint is hit. If the tracepoint number
11867 @var{num} is not specified, the @code{passcount} command sets the
11868 passcount of the most recently defined tracepoint. If no passcount is
11869 given, the trace experiment will run until stopped explicitly by the
11875 (@value{GDBP}) @b{passcount 5 2} // Stop on the 5th execution of
11876 @exdent @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @code{// tracepoint 2}
11878 (@value{GDBP}) @b{passcount 12} // Stop on the 12th execution of the
11879 @exdent @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @code{// most recently defined tracepoint.}
11880 (@value{GDBP}) @b{trace foo}
11881 (@value{GDBP}) @b{pass 3}
11882 (@value{GDBP}) @b{trace bar}
11883 (@value{GDBP}) @b{pass 2}
11884 (@value{GDBP}) @b{trace baz}
11885 (@value{GDBP}) @b{pass 1} // Stop tracing when foo has been
11886 @exdent @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @code{// executed 3 times OR when bar has}
11887 @exdent @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @code{// been executed 2 times}
11888 @exdent @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @code{// OR when baz has been executed 1 time.}
11892 @node Tracepoint Conditions
11893 @subsection Tracepoint Conditions
11894 @cindex conditional tracepoints
11895 @cindex tracepoint conditions
11897 The simplest sort of tracepoint collects data every time your program
11898 reaches a specified place. You can also specify a @dfn{condition} for
11899 a tracepoint. A condition is just a Boolean expression in your
11900 programming language (@pxref{Expressions, ,Expressions}). A
11901 tracepoint with a condition evaluates the expression each time your
11902 program reaches it, and data collection happens only if the condition
11905 Tracepoint conditions can be specified when a tracepoint is set, by
11906 using @samp{if} in the arguments to the @code{trace} command.
11907 @xref{Create and Delete Tracepoints, ,Setting Tracepoints}. They can
11908 also be set or changed at any time with the @code{condition} command,
11909 just as with breakpoints.
11911 Unlike breakpoint conditions, @value{GDBN} does not actually evaluate
11912 the conditional expression itself. Instead, @value{GDBN} encodes the
11913 expression into an agent expression (@pxref{Agent Expressions})
11914 suitable for execution on the target, independently of @value{GDBN}.
11915 Global variables become raw memory locations, locals become stack
11916 accesses, and so forth.
11918 For instance, suppose you have a function that is usually called
11919 frequently, but should not be called after an error has occurred. You
11920 could use the following tracepoint command to collect data about calls
11921 of that function that happen while the error code is propagating
11922 through the program; an unconditional tracepoint could end up
11923 collecting thousands of useless trace frames that you would have to
11927 (@value{GDBP}) @kbd{trace normal_operation if errcode > 0}
11930 @node Trace State Variables
11931 @subsection Trace State Variables
11932 @cindex trace state variables
11934 A @dfn{trace state variable} is a special type of variable that is
11935 created and managed by target-side code. The syntax is the same as
11936 that for GDB's convenience variables (a string prefixed with ``$''),
11937 but they are stored on the target. They must be created explicitly,
11938 using a @code{tvariable} command. They are always 64-bit signed
11941 Trace state variables are remembered by @value{GDBN}, and downloaded
11942 to the target along with tracepoint information when the trace
11943 experiment starts. There are no intrinsic limits on the number of
11944 trace state variables, beyond memory limitations of the target.
11946 @cindex convenience variables, and trace state variables
11947 Although trace state variables are managed by the target, you can use
11948 them in print commands and expressions as if they were convenience
11949 variables; @value{GDBN} will get the current value from the target
11950 while the trace experiment is running. Trace state variables share
11951 the same namespace as other ``$'' variables, which means that you
11952 cannot have trace state variables with names like @code{$23} or
11953 @code{$pc}, nor can you have a trace state variable and a convenience
11954 variable with the same name.
11958 @item tvariable $@var{name} [ = @var{expression} ]
11960 The @code{tvariable} command creates a new trace state variable named
11961 @code{$@var{name}}, and optionally gives it an initial value of
11962 @var{expression}. @var{expression} is evaluated when this command is
11963 entered; the result will be converted to an integer if possible,
11964 otherwise @value{GDBN} will report an error. A subsequent
11965 @code{tvariable} command specifying the same name does not create a
11966 variable, but instead assigns the supplied initial value to the
11967 existing variable of that name, overwriting any previous initial
11968 value. The default initial value is 0.
11970 @item info tvariables
11971 @kindex info tvariables
11972 List all the trace state variables along with their initial values.
11973 Their current values may also be displayed, if the trace experiment is
11976 @item delete tvariable @r{[} $@var{name} @dots{} @r{]}
11977 @kindex delete tvariable
11978 Delete the given trace state variables, or all of them if no arguments
11983 @node Tracepoint Actions
11984 @subsection Tracepoint Action Lists
11988 @cindex tracepoint actions
11989 @item actions @r{[}@var{num}@r{]}
11990 This command will prompt for a list of actions to be taken when the
11991 tracepoint is hit. If the tracepoint number @var{num} is not
11992 specified, this command sets the actions for the one that was most
11993 recently defined (so that you can define a tracepoint and then say
11994 @code{actions} without bothering about its number). You specify the
11995 actions themselves on the following lines, one action at a time, and
11996 terminate the actions list with a line containing just @code{end}. So
11997 far, the only defined actions are @code{collect}, @code{teval}, and
11998 @code{while-stepping}.
12000 @code{actions} is actually equivalent to @code{commands} (@pxref{Break
12001 Commands, ,Breakpoint Command Lists}), except that only the defined
12002 actions are allowed; any other @value{GDBN} command is rejected.
12004 @cindex remove actions from a tracepoint
12005 To remove all actions from a tracepoint, type @samp{actions @var{num}}
12006 and follow it immediately with @samp{end}.
12009 (@value{GDBP}) @b{collect @var{data}} // collect some data
12011 (@value{GDBP}) @b{while-stepping 5} // single-step 5 times, collect data
12013 (@value{GDBP}) @b{end} // signals the end of actions.
12016 In the following example, the action list begins with @code{collect}
12017 commands indicating the things to be collected when the tracepoint is
12018 hit. Then, in order to single-step and collect additional data
12019 following the tracepoint, a @code{while-stepping} command is used,
12020 followed by the list of things to be collected after each step in a
12021 sequence of single steps. The @code{while-stepping} command is
12022 terminated by its own separate @code{end} command. Lastly, the action
12023 list is terminated by an @code{end} command.
12026 (@value{GDBP}) @b{trace foo}
12027 (@value{GDBP}) @b{actions}
12028 Enter actions for tracepoint 1, one per line:
12031 > while-stepping 12
12032 > collect $pc, arr[i]
12037 @kindex collect @r{(tracepoints)}
12038 @item collect@r{[}/@var{mods}@r{]} @var{expr1}, @var{expr2}, @dots{}
12039 Collect values of the given expressions when the tracepoint is hit.
12040 This command accepts a comma-separated list of any valid expressions.
12041 In addition to global, static, or local variables, the following
12042 special arguments are supported:
12046 Collect all registers.
12049 Collect all function arguments.
12052 Collect all local variables.
12055 Collect the return address. This is helpful if you want to see more
12059 Collects the number of arguments from the static probe at which the
12060 tracepoint is located.
12061 @xref{Static Probe Points}.
12063 @item $_probe_arg@var{n}
12064 @var{n} is an integer between 0 and 11. Collects the @var{n}th argument
12065 from the static probe at which the tracepoint is located.
12066 @xref{Static Probe Points}.
12069 @vindex $_sdata@r{, collect}
12070 Collect static tracepoint marker specific data. Only available for
12071 static tracepoints. @xref{Tracepoint Actions,,Tracepoint Action
12072 Lists}. On the UST static tracepoints library backend, an
12073 instrumentation point resembles a @code{printf} function call. The
12074 tracing library is able to collect user specified data formatted to a
12075 character string using the format provided by the programmer that
12076 instrumented the program. Other backends have similar mechanisms.
12077 Here's an example of a UST marker call:
12080 const char master_name[] = "$your_name";
12081 trace_mark(channel1, marker1, "hello %s", master_name)
12084 In this case, collecting @code{$_sdata} collects the string
12085 @samp{hello $yourname}. When analyzing the trace buffer, you can
12086 inspect @samp{$_sdata} like any other variable available to
12090 You can give several consecutive @code{collect} commands, each one
12091 with a single argument, or one @code{collect} command with several
12092 arguments separated by commas; the effect is the same.
12094 The optional @var{mods} changes the usual handling of the arguments.
12095 @code{s} requests that pointers to chars be handled as strings, in
12096 particular collecting the contents of the memory being pointed at, up
12097 to the first zero. The upper bound is by default the value of the
12098 @code{print elements} variable; if @code{s} is followed by a decimal
12099 number, that is the upper bound instead. So for instance
12100 @samp{collect/s25 mystr} collects as many as 25 characters at
12103 The command @code{info scope} (@pxref{Symbols, info scope}) is
12104 particularly useful for figuring out what data to collect.
12106 @kindex teval @r{(tracepoints)}
12107 @item teval @var{expr1}, @var{expr2}, @dots{}
12108 Evaluate the given expressions when the tracepoint is hit. This
12109 command accepts a comma-separated list of expressions. The results
12110 are discarded, so this is mainly useful for assigning values to trace
12111 state variables (@pxref{Trace State Variables}) without adding those
12112 values to the trace buffer, as would be the case if the @code{collect}
12115 @kindex while-stepping @r{(tracepoints)}
12116 @item while-stepping @var{n}
12117 Perform @var{n} single-step instruction traces after the tracepoint,
12118 collecting new data after each step. The @code{while-stepping}
12119 command is followed by the list of what to collect while stepping
12120 (followed by its own @code{end} command):
12123 > while-stepping 12
12124 > collect $regs, myglobal
12130 Note that @code{$pc} is not automatically collected by
12131 @code{while-stepping}; you need to explicitly collect that register if
12132 you need it. You may abbreviate @code{while-stepping} as @code{ws} or
12135 @item set default-collect @var{expr1}, @var{expr2}, @dots{}
12136 @kindex set default-collect
12137 @cindex default collection action
12138 This variable is a list of expressions to collect at each tracepoint
12139 hit. It is effectively an additional @code{collect} action prepended
12140 to every tracepoint action list. The expressions are parsed
12141 individually for each tracepoint, so for instance a variable named
12142 @code{xyz} may be interpreted as a global for one tracepoint, and a
12143 local for another, as appropriate to the tracepoint's location.
12145 @item show default-collect
12146 @kindex show default-collect
12147 Show the list of expressions that are collected by default at each
12152 @node Listing Tracepoints
12153 @subsection Listing Tracepoints
12156 @kindex info tracepoints @r{[}@var{n}@dots{}@r{]}
12157 @kindex info tp @r{[}@var{n}@dots{}@r{]}
12158 @cindex information about tracepoints
12159 @item info tracepoints @r{[}@var{num}@dots{}@r{]}
12160 Display information about the tracepoint @var{num}. If you don't
12161 specify a tracepoint number, displays information about all the
12162 tracepoints defined so far. The format is similar to that used for
12163 @code{info breakpoints}; in fact, @code{info tracepoints} is the same
12164 command, simply restricting itself to tracepoints.
12166 A tracepoint's listing may include additional information specific to
12171 its passcount as given by the @code{passcount @var{n}} command
12174 the state about installed on target of each location
12178 (@value{GDBP}) @b{info trace}
12179 Num Type Disp Enb Address What
12180 1 tracepoint keep y 0x0804ab57 in foo() at main.cxx:7
12182 collect globfoo, $regs
12187 2 tracepoint keep y <MULTIPLE>
12189 2.1 y 0x0804859c in func4 at change-loc.h:35
12190 installed on target
12191 2.2 y 0xb7ffc480 in func4 at change-loc.h:35
12192 installed on target
12193 2.3 y <PENDING> set_tracepoint
12194 3 tracepoint keep y 0x080485b1 in foo at change-loc.c:29
12195 not installed on target
12200 This command can be abbreviated @code{info tp}.
12203 @node Listing Static Tracepoint Markers
12204 @subsection Listing Static Tracepoint Markers
12207 @kindex info static-tracepoint-markers
12208 @cindex information about static tracepoint markers
12209 @item info static-tracepoint-markers
12210 Display information about all static tracepoint markers defined in the
12213 For each marker, the following columns are printed:
12217 An incrementing counter, output to help readability. This is not a
12220 The marker ID, as reported by the target.
12221 @item Enabled or Disabled
12222 Probed markers are tagged with @samp{y}. @samp{n} identifies marks
12223 that are not enabled.
12225 Where the marker is in your program, as a memory address.
12227 Where the marker is in the source for your program, as a file and line
12228 number. If the debug information included in the program does not
12229 allow @value{GDBN} to locate the source of the marker, this column
12230 will be left blank.
12234 In addition, the following information may be printed for each marker:
12238 User data passed to the tracing library by the marker call. In the
12239 UST backend, this is the format string passed as argument to the
12241 @item Static tracepoints probing the marker
12242 The list of static tracepoints attached to the marker.
12246 (@value{GDBP}) info static-tracepoint-markers
12247 Cnt ID Enb Address What
12248 1 ust/bar2 y 0x0000000000400e1a in main at stexample.c:25
12249 Data: number1 %d number2 %d
12250 Probed by static tracepoints: #2
12251 2 ust/bar33 n 0x0000000000400c87 in main at stexample.c:24
12257 @node Starting and Stopping Trace Experiments
12258 @subsection Starting and Stopping Trace Experiments
12261 @kindex tstart [ @var{notes} ]
12262 @cindex start a new trace experiment
12263 @cindex collected data discarded
12265 This command starts the trace experiment, and begins collecting data.
12266 It has the side effect of discarding all the data collected in the
12267 trace buffer during the previous trace experiment. If any arguments
12268 are supplied, they are taken as a note and stored with the trace
12269 experiment's state. The notes may be arbitrary text, and are
12270 especially useful with disconnected tracing in a multi-user context;
12271 the notes can explain what the trace is doing, supply user contact
12272 information, and so forth.
12274 @kindex tstop [ @var{notes} ]
12275 @cindex stop a running trace experiment
12277 This command stops the trace experiment. If any arguments are
12278 supplied, they are recorded with the experiment as a note. This is
12279 useful if you are stopping a trace started by someone else, for
12280 instance if the trace is interfering with the system's behavior and
12281 needs to be stopped quickly.
12283 @strong{Note}: a trace experiment and data collection may stop
12284 automatically if any tracepoint's passcount is reached
12285 (@pxref{Tracepoint Passcounts}), or if the trace buffer becomes full.
12288 @cindex status of trace data collection
12289 @cindex trace experiment, status of
12291 This command displays the status of the current trace data
12295 Here is an example of the commands we described so far:
12298 (@value{GDBP}) @b{trace gdb_c_test}
12299 (@value{GDBP}) @b{actions}
12300 Enter actions for tracepoint #1, one per line.
12301 > collect $regs,$locals,$args
12302 > while-stepping 11
12306 (@value{GDBP}) @b{tstart}
12307 [time passes @dots{}]
12308 (@value{GDBP}) @b{tstop}
12311 @anchor{disconnected tracing}
12312 @cindex disconnected tracing
12313 You can choose to continue running the trace experiment even if
12314 @value{GDBN} disconnects from the target, voluntarily or
12315 involuntarily. For commands such as @code{detach}, the debugger will
12316 ask what you want to do with the trace. But for unexpected
12317 terminations (@value{GDBN} crash, network outage), it would be
12318 unfortunate to lose hard-won trace data, so the variable
12319 @code{disconnected-tracing} lets you decide whether the trace should
12320 continue running without @value{GDBN}.
12323 @item set disconnected-tracing on
12324 @itemx set disconnected-tracing off
12325 @kindex set disconnected-tracing
12326 Choose whether a tracing run should continue to run if @value{GDBN}
12327 has disconnected from the target. Note that @code{detach} or
12328 @code{quit} will ask you directly what to do about a running trace no
12329 matter what this variable's setting, so the variable is mainly useful
12330 for handling unexpected situations, such as loss of the network.
12332 @item show disconnected-tracing
12333 @kindex show disconnected-tracing
12334 Show the current choice for disconnected tracing.
12338 When you reconnect to the target, the trace experiment may or may not
12339 still be running; it might have filled the trace buffer in the
12340 meantime, or stopped for one of the other reasons. If it is running,
12341 it will continue after reconnection.
12343 Upon reconnection, the target will upload information about the
12344 tracepoints in effect. @value{GDBN} will then compare that
12345 information to the set of tracepoints currently defined, and attempt
12346 to match them up, allowing for the possibility that the numbers may
12347 have changed due to creation and deletion in the meantime. If one of
12348 the target's tracepoints does not match any in @value{GDBN}, the
12349 debugger will create a new tracepoint, so that you have a number with
12350 which to specify that tracepoint. This matching-up process is
12351 necessarily heuristic, and it may result in useless tracepoints being
12352 created; you may simply delete them if they are of no use.
12354 @cindex circular trace buffer
12355 If your target agent supports a @dfn{circular trace buffer}, then you
12356 can run a trace experiment indefinitely without filling the trace
12357 buffer; when space runs out, the agent deletes already-collected trace
12358 frames, oldest first, until there is enough room to continue
12359 collecting. This is especially useful if your tracepoints are being
12360 hit too often, and your trace gets terminated prematurely because the
12361 buffer is full. To ask for a circular trace buffer, simply set
12362 @samp{circular-trace-buffer} to on. You can set this at any time,
12363 including during tracing; if the agent can do it, it will change
12364 buffer handling on the fly, otherwise it will not take effect until
12368 @item set circular-trace-buffer on
12369 @itemx set circular-trace-buffer off
12370 @kindex set circular-trace-buffer
12371 Choose whether a tracing run should use a linear or circular buffer
12372 for trace data. A linear buffer will not lose any trace data, but may
12373 fill up prematurely, while a circular buffer will discard old trace
12374 data, but it will have always room for the latest tracepoint hits.
12376 @item show circular-trace-buffer
12377 @kindex show circular-trace-buffer
12378 Show the current choice for the trace buffer. Note that this may not
12379 match the agent's current buffer handling, nor is it guaranteed to
12380 match the setting that might have been in effect during a past run,
12381 for instance if you are looking at frames from a trace file.
12386 @item set trace-buffer-size @var{n}
12387 @itemx set trace-buffer-size unlimited
12388 @kindex set trace-buffer-size
12389 Request that the target use a trace buffer of @var{n} bytes. Not all
12390 targets will honor the request; they may have a compiled-in size for
12391 the trace buffer, or some other limitation. Set to a value of
12392 @code{unlimited} or @code{-1} to let the target use whatever size it
12393 likes. This is also the default.
12395 @item show trace-buffer-size
12396 @kindex show trace-buffer-size
12397 Show the current requested size for the trace buffer. Note that this
12398 will only match the actual size if the target supports size-setting,
12399 and was able to handle the requested size. For instance, if the
12400 target can only change buffer size between runs, this variable will
12401 not reflect the change until the next run starts. Use @code{tstatus}
12402 to get a report of the actual buffer size.
12406 @item set trace-user @var{text}
12407 @kindex set trace-user
12409 @item show trace-user
12410 @kindex show trace-user
12412 @item set trace-notes @var{text}
12413 @kindex set trace-notes
12414 Set the trace run's notes.
12416 @item show trace-notes
12417 @kindex show trace-notes
12418 Show the trace run's notes.
12420 @item set trace-stop-notes @var{text}
12421 @kindex set trace-stop-notes
12422 Set the trace run's stop notes. The handling of the note is as for
12423 @code{tstop} arguments; the set command is convenient way to fix a
12424 stop note that is mistaken or incomplete.
12426 @item show trace-stop-notes
12427 @kindex show trace-stop-notes
12428 Show the trace run's stop notes.
12432 @node Tracepoint Restrictions
12433 @subsection Tracepoint Restrictions
12435 @cindex tracepoint restrictions
12436 There are a number of restrictions on the use of tracepoints. As
12437 described above, tracepoint data gathering occurs on the target
12438 without interaction from @value{GDBN}. Thus the full capabilities of
12439 the debugger are not available during data gathering, and then at data
12440 examination time, you will be limited by only having what was
12441 collected. The following items describe some common problems, but it
12442 is not exhaustive, and you may run into additional difficulties not
12448 Tracepoint expressions are intended to gather objects (lvalues). Thus
12449 the full flexibility of GDB's expression evaluator is not available.
12450 You cannot call functions, cast objects to aggregate types, access
12451 convenience variables or modify values (except by assignment to trace
12452 state variables). Some language features may implicitly call
12453 functions (for instance Objective-C fields with accessors), and therefore
12454 cannot be collected either.
12457 Collection of local variables, either individually or in bulk with
12458 @code{$locals} or @code{$args}, during @code{while-stepping} may
12459 behave erratically. The stepping action may enter a new scope (for
12460 instance by stepping into a function), or the location of the variable
12461 may change (for instance it is loaded into a register). The
12462 tracepoint data recorded uses the location information for the
12463 variables that is correct for the tracepoint location. When the
12464 tracepoint is created, it is not possible, in general, to determine
12465 where the steps of a @code{while-stepping} sequence will advance the
12466 program---particularly if a conditional branch is stepped.
12469 Collection of an incompletely-initialized or partially-destroyed object
12470 may result in something that @value{GDBN} cannot display, or displays
12471 in a misleading way.
12474 When @value{GDBN} displays a pointer to character it automatically
12475 dereferences the pointer to also display characters of the string
12476 being pointed to. However, collecting the pointer during tracing does
12477 not automatically collect the string. You need to explicitly
12478 dereference the pointer and provide size information if you want to
12479 collect not only the pointer, but the memory pointed to. For example,
12480 @code{*ptr@@50} can be used to collect the 50 element array pointed to
12484 It is not possible to collect a complete stack backtrace at a
12485 tracepoint. Instead, you may collect the registers and a few hundred
12486 bytes from the stack pointer with something like @code{*(unsigned char *)$esp@@300}
12487 (adjust to use the name of the actual stack pointer register on your
12488 target architecture, and the amount of stack you wish to capture).
12489 Then the @code{backtrace} command will show a partial backtrace when
12490 using a trace frame. The number of stack frames that can be examined
12491 depends on the sizes of the frames in the collected stack. Note that
12492 if you ask for a block so large that it goes past the bottom of the
12493 stack, the target agent may report an error trying to read from an
12497 If you do not collect registers at a tracepoint, @value{GDBN} can
12498 infer that the value of @code{$pc} must be the same as the address of
12499 the tracepoint and use that when you are looking at a trace frame
12500 for that tracepoint. However, this cannot work if the tracepoint has
12501 multiple locations (for instance if it was set in a function that was
12502 inlined), or if it has a @code{while-stepping} loop. In those cases
12503 @value{GDBN} will warn you that it can't infer @code{$pc}, and default
12508 @node Analyze Collected Data
12509 @section Using the Collected Data
12511 After the tracepoint experiment ends, you use @value{GDBN} commands
12512 for examining the trace data. The basic idea is that each tracepoint
12513 collects a trace @dfn{snapshot} every time it is hit and another
12514 snapshot every time it single-steps. All these snapshots are
12515 consecutively numbered from zero and go into a buffer, and you can
12516 examine them later. The way you examine them is to @dfn{focus} on a
12517 specific trace snapshot. When the remote stub is focused on a trace
12518 snapshot, it will respond to all @value{GDBN} requests for memory and
12519 registers by reading from the buffer which belongs to that snapshot,
12520 rather than from @emph{real} memory or registers of the program being
12521 debugged. This means that @strong{all} @value{GDBN} commands
12522 (@code{print}, @code{info registers}, @code{backtrace}, etc.) will
12523 behave as if we were currently debugging the program state as it was
12524 when the tracepoint occurred. Any requests for data that are not in
12525 the buffer will fail.
12528 * tfind:: How to select a trace snapshot
12529 * tdump:: How to display all data for a snapshot
12530 * save tracepoints:: How to save tracepoints for a future run
12534 @subsection @code{tfind @var{n}}
12537 @cindex select trace snapshot
12538 @cindex find trace snapshot
12539 The basic command for selecting a trace snapshot from the buffer is
12540 @code{tfind @var{n}}, which finds trace snapshot number @var{n},
12541 counting from zero. If no argument @var{n} is given, the next
12542 snapshot is selected.
12544 Here are the various forms of using the @code{tfind} command.
12548 Find the first snapshot in the buffer. This is a synonym for
12549 @code{tfind 0} (since 0 is the number of the first snapshot).
12552 Stop debugging trace snapshots, resume @emph{live} debugging.
12555 Same as @samp{tfind none}.
12558 No argument means find the next trace snapshot.
12561 Find the previous trace snapshot before the current one. This permits
12562 retracing earlier steps.
12564 @item tfind tracepoint @var{num}
12565 Find the next snapshot associated with tracepoint @var{num}. Search
12566 proceeds forward from the last examined trace snapshot. If no
12567 argument @var{num} is given, it means find the next snapshot collected
12568 for the same tracepoint as the current snapshot.
12570 @item tfind pc @var{addr}
12571 Find the next snapshot associated with the value @var{addr} of the
12572 program counter. Search proceeds forward from the last examined trace
12573 snapshot. If no argument @var{addr} is given, it means find the next
12574 snapshot with the same value of PC as the current snapshot.
12576 @item tfind outside @var{addr1}, @var{addr2}
12577 Find the next snapshot whose PC is outside the given range of
12578 addresses (exclusive).
12580 @item tfind range @var{addr1}, @var{addr2}
12581 Find the next snapshot whose PC is between @var{addr1} and
12582 @var{addr2} (inclusive).
12584 @item tfind line @r{[}@var{file}:@r{]}@var{n}
12585 Find the next snapshot associated with the source line @var{n}. If
12586 the optional argument @var{file} is given, refer to line @var{n} in
12587 that source file. Search proceeds forward from the last examined
12588 trace snapshot. If no argument @var{n} is given, it means find the
12589 next line other than the one currently being examined; thus saying
12590 @code{tfind line} repeatedly can appear to have the same effect as
12591 stepping from line to line in a @emph{live} debugging session.
12594 The default arguments for the @code{tfind} commands are specifically
12595 designed to make it easy to scan through the trace buffer. For
12596 instance, @code{tfind} with no argument selects the next trace
12597 snapshot, and @code{tfind -} with no argument selects the previous
12598 trace snapshot. So, by giving one @code{tfind} command, and then
12599 simply hitting @key{RET} repeatedly you can examine all the trace
12600 snapshots in order. Or, by saying @code{tfind -} and then hitting
12601 @key{RET} repeatedly you can examine the snapshots in reverse order.
12602 The @code{tfind line} command with no argument selects the snapshot
12603 for the next source line executed. The @code{tfind pc} command with
12604 no argument selects the next snapshot with the same program counter
12605 (PC) as the current frame. The @code{tfind tracepoint} command with
12606 no argument selects the next trace snapshot collected by the same
12607 tracepoint as the current one.
12609 In addition to letting you scan through the trace buffer manually,
12610 these commands make it easy to construct @value{GDBN} scripts that
12611 scan through the trace buffer and print out whatever collected data
12612 you are interested in. Thus, if we want to examine the PC, FP, and SP
12613 registers from each trace frame in the buffer, we can say this:
12616 (@value{GDBP}) @b{tfind start}
12617 (@value{GDBP}) @b{while ($trace_frame != -1)}
12618 > printf "Frame %d, PC = %08X, SP = %08X, FP = %08X\n", \
12619 $trace_frame, $pc, $sp, $fp
12623 Frame 0, PC = 0020DC64, SP = 0030BF3C, FP = 0030BF44
12624 Frame 1, PC = 0020DC6C, SP = 0030BF38, FP = 0030BF44
12625 Frame 2, PC = 0020DC70, SP = 0030BF34, FP = 0030BF44
12626 Frame 3, PC = 0020DC74, SP = 0030BF30, FP = 0030BF44
12627 Frame 4, PC = 0020DC78, SP = 0030BF2C, FP = 0030BF44
12628 Frame 5, PC = 0020DC7C, SP = 0030BF28, FP = 0030BF44
12629 Frame 6, PC = 0020DC80, SP = 0030BF24, FP = 0030BF44
12630 Frame 7, PC = 0020DC84, SP = 0030BF20, FP = 0030BF44
12631 Frame 8, PC = 0020DC88, SP = 0030BF1C, FP = 0030BF44
12632 Frame 9, PC = 0020DC8E, SP = 0030BF18, FP = 0030BF44
12633 Frame 10, PC = 00203F6C, SP = 0030BE3C, FP = 0030BF14
12636 Or, if we want to examine the variable @code{X} at each source line in
12640 (@value{GDBP}) @b{tfind start}
12641 (@value{GDBP}) @b{while ($trace_frame != -1)}
12642 > printf "Frame %d, X == %d\n", $trace_frame, X
12652 @subsection @code{tdump}
12654 @cindex dump all data collected at tracepoint
12655 @cindex tracepoint data, display
12657 This command takes no arguments. It prints all the data collected at
12658 the current trace snapshot.
12661 (@value{GDBP}) @b{trace 444}
12662 (@value{GDBP}) @b{actions}
12663 Enter actions for tracepoint #2, one per line:
12664 > collect $regs, $locals, $args, gdb_long_test
12667 (@value{GDBP}) @b{tstart}
12669 (@value{GDBP}) @b{tfind line 444}
12670 #0 gdb_test (p1=0x11, p2=0x22, p3=0x33, p4=0x44, p5=0x55, p6=0x66)
12672 444 printp( "%s: arguments = 0x%X 0x%X 0x%X 0x%X 0x%X 0x%X\n", )
12674 (@value{GDBP}) @b{tdump}
12675 Data collected at tracepoint 2, trace frame 1:
12676 d0 0xc4aa0085 -995491707
12680 d4 0x71aea3d 119204413
12683 d7 0x380035 3670069
12684 a0 0x19e24a 1696330
12685 a1 0x3000668 50333288
12687 a3 0x322000 3284992
12688 a4 0x3000698 50333336
12689 a5 0x1ad3cc 1758156
12690 fp 0x30bf3c 0x30bf3c
12691 sp 0x30bf34 0x30bf34
12693 pc 0x20b2c8 0x20b2c8
12697 p = 0x20e5b4 "gdb-test"
12704 gdb_long_test = 17 '\021'
12709 @code{tdump} works by scanning the tracepoint's current collection
12710 actions and printing the value of each expression listed. So
12711 @code{tdump} can fail, if after a run, you change the tracepoint's
12712 actions to mention variables that were not collected during the run.
12714 Also, for tracepoints with @code{while-stepping} loops, @code{tdump}
12715 uses the collected value of @code{$pc} to distinguish between trace
12716 frames that were collected at the tracepoint hit, and frames that were
12717 collected while stepping. This allows it to correctly choose whether
12718 to display the basic list of collections, or the collections from the
12719 body of the while-stepping loop. However, if @code{$pc} was not collected,
12720 then @code{tdump} will always attempt to dump using the basic collection
12721 list, and may fail if a while-stepping frame does not include all the
12722 same data that is collected at the tracepoint hit.
12723 @c This is getting pretty arcane, example would be good.
12725 @node save tracepoints
12726 @subsection @code{save tracepoints @var{filename}}
12727 @kindex save tracepoints
12728 @kindex save-tracepoints
12729 @cindex save tracepoints for future sessions
12731 This command saves all current tracepoint definitions together with
12732 their actions and passcounts, into a file @file{@var{filename}}
12733 suitable for use in a later debugging session. To read the saved
12734 tracepoint definitions, use the @code{source} command (@pxref{Command
12735 Files}). The @w{@code{save-tracepoints}} command is a deprecated
12736 alias for @w{@code{save tracepoints}}
12738 @node Tracepoint Variables
12739 @section Convenience Variables for Tracepoints
12740 @cindex tracepoint variables
12741 @cindex convenience variables for tracepoints
12744 @vindex $trace_frame
12745 @item (int) $trace_frame
12746 The current trace snapshot (a.k.a.@: @dfn{frame}) number, or -1 if no
12747 snapshot is selected.
12749 @vindex $tracepoint
12750 @item (int) $tracepoint
12751 The tracepoint for the current trace snapshot.
12753 @vindex $trace_line
12754 @item (int) $trace_line
12755 The line number for the current trace snapshot.
12757 @vindex $trace_file
12758 @item (char []) $trace_file
12759 The source file for the current trace snapshot.
12761 @vindex $trace_func
12762 @item (char []) $trace_func
12763 The name of the function containing @code{$tracepoint}.
12766 Note: @code{$trace_file} is not suitable for use in @code{printf},
12767 use @code{output} instead.
12769 Here's a simple example of using these convenience variables for
12770 stepping through all the trace snapshots and printing some of their
12771 data. Note that these are not the same as trace state variables,
12772 which are managed by the target.
12775 (@value{GDBP}) @b{tfind start}
12777 (@value{GDBP}) @b{while $trace_frame != -1}
12778 > output $trace_file
12779 > printf ", line %d (tracepoint #%d)\n", $trace_line, $tracepoint
12785 @section Using Trace Files
12786 @cindex trace files
12788 In some situations, the target running a trace experiment may no
12789 longer be available; perhaps it crashed, or the hardware was needed
12790 for a different activity. To handle these cases, you can arrange to
12791 dump the trace data into a file, and later use that file as a source
12792 of trace data, via the @code{target tfile} command.
12797 @item tsave [ -r ] @var{filename}
12798 @itemx tsave [-ctf] @var{dirname}
12799 Save the trace data to @var{filename}. By default, this command
12800 assumes that @var{filename} refers to the host filesystem, so if
12801 necessary @value{GDBN} will copy raw trace data up from the target and
12802 then save it. If the target supports it, you can also supply the
12803 optional argument @code{-r} (``remote'') to direct the target to save
12804 the data directly into @var{filename} in its own filesystem, which may be
12805 more efficient if the trace buffer is very large. (Note, however, that
12806 @code{target tfile} can only read from files accessible to the host.)
12807 By default, this command will save trace frame in tfile format.
12808 You can supply the optional argument @code{-ctf} to save date in CTF
12809 format. The @dfn{Common Trace Format} (CTF) is proposed as a trace format
12810 that can be shared by multiple debugging and tracing tools. Please go to
12811 @indicateurl{http://www.efficios.com/ctf} to get more information.
12813 @kindex target tfile
12817 @item target tfile @var{filename}
12818 @itemx target ctf @var{dirname}
12819 Use the file named @var{filename} or directory named @var{dirname} as
12820 a source of trace data. Commands that examine data work as they do with
12821 a live target, but it is not possible to run any new trace experiments.
12822 @code{tstatus} will report the state of the trace run at the moment
12823 the data was saved, as well as the current trace frame you are examining.
12824 @var{filename} or @var{dirname} must be on a filesystem accessible to
12828 (@value{GDBP}) target ctf ctf.ctf
12829 (@value{GDBP}) tfind
12830 Found trace frame 0, tracepoint 2
12831 39 ++a; /* set tracepoint 1 here */
12832 (@value{GDBP}) tdump
12833 Data collected at tracepoint 2, trace frame 0:
12837 c = @{"123", "456", "789", "123", "456", "789"@}
12838 d = @{@{@{a = 1, b = 2@}, @{a = 3, b = 4@}@}, @{@{a = 5, b = 6@}, @{a = 7, b = 8@}@}@}
12846 @chapter Debugging Programs That Use Overlays
12849 If your program is too large to fit completely in your target system's
12850 memory, you can sometimes use @dfn{overlays} to work around this
12851 problem. @value{GDBN} provides some support for debugging programs that
12855 * How Overlays Work:: A general explanation of overlays.
12856 * Overlay Commands:: Managing overlays in @value{GDBN}.
12857 * Automatic Overlay Debugging:: @value{GDBN} can find out which overlays are
12858 mapped by asking the inferior.
12859 * Overlay Sample Program:: A sample program using overlays.
12862 @node How Overlays Work
12863 @section How Overlays Work
12864 @cindex mapped overlays
12865 @cindex unmapped overlays
12866 @cindex load address, overlay's
12867 @cindex mapped address
12868 @cindex overlay area
12870 Suppose you have a computer whose instruction address space is only 64
12871 kilobytes long, but which has much more memory which can be accessed by
12872 other means: special instructions, segment registers, or memory
12873 management hardware, for example. Suppose further that you want to
12874 adapt a program which is larger than 64 kilobytes to run on this system.
12876 One solution is to identify modules of your program which are relatively
12877 independent, and need not call each other directly; call these modules
12878 @dfn{overlays}. Separate the overlays from the main program, and place
12879 their machine code in the larger memory. Place your main program in
12880 instruction memory, but leave at least enough space there to hold the
12881 largest overlay as well.
12883 Now, to call a function located in an overlay, you must first copy that
12884 overlay's machine code from the large memory into the space set aside
12885 for it in the instruction memory, and then jump to its entry point
12888 @c NB: In the below the mapped area's size is greater or equal to the
12889 @c size of all overlays. This is intentional to remind the developer
12890 @c that overlays don't necessarily need to be the same size.
12894 Data Instruction Larger
12895 Address Space Address Space Address Space
12896 +-----------+ +-----------+ +-----------+
12898 +-----------+ +-----------+ +-----------+<-- overlay 1
12899 | program | | main | .----| overlay 1 | load address
12900 | variables | | program | | +-----------+
12901 | and heap | | | | | |
12902 +-----------+ | | | +-----------+<-- overlay 2
12903 | | +-----------+ | | | load address
12904 +-----------+ | | | .-| overlay 2 |
12906 mapped --->+-----------+ | | +-----------+
12907 address | | | | | |
12908 | overlay | <-' | | |
12909 | area | <---' +-----------+<-- overlay 3
12910 | | <---. | | load address
12911 +-----------+ `--| overlay 3 |
12918 @anchor{A code overlay}A code overlay
12922 The diagram (@pxref{A code overlay}) shows a system with separate data
12923 and instruction address spaces. To map an overlay, the program copies
12924 its code from the larger address space to the instruction address space.
12925 Since the overlays shown here all use the same mapped address, only one
12926 may be mapped at a time. For a system with a single address space for
12927 data and instructions, the diagram would be similar, except that the
12928 program variables and heap would share an address space with the main
12929 program and the overlay area.
12931 An overlay loaded into instruction memory and ready for use is called a
12932 @dfn{mapped} overlay; its @dfn{mapped address} is its address in the
12933 instruction memory. An overlay not present (or only partially present)
12934 in instruction memory is called @dfn{unmapped}; its @dfn{load address}
12935 is its address in the larger memory. The mapped address is also called
12936 the @dfn{virtual memory address}, or @dfn{VMA}; the load address is also
12937 called the @dfn{load memory address}, or @dfn{LMA}.
12939 Unfortunately, overlays are not a completely transparent way to adapt a
12940 program to limited instruction memory. They introduce a new set of
12941 global constraints you must keep in mind as you design your program:
12946 Before calling or returning to a function in an overlay, your program
12947 must make sure that overlay is actually mapped. Otherwise, the call or
12948 return will transfer control to the right address, but in the wrong
12949 overlay, and your program will probably crash.
12952 If the process of mapping an overlay is expensive on your system, you
12953 will need to choose your overlays carefully to minimize their effect on
12954 your program's performance.
12957 The executable file you load onto your system must contain each
12958 overlay's instructions, appearing at the overlay's load address, not its
12959 mapped address. However, each overlay's instructions must be relocated
12960 and its symbols defined as if the overlay were at its mapped address.
12961 You can use GNU linker scripts to specify different load and relocation
12962 addresses for pieces of your program; see @ref{Overlay Description,,,
12963 ld.info, Using ld: the GNU linker}.
12966 The procedure for loading executable files onto your system must be able
12967 to load their contents into the larger address space as well as the
12968 instruction and data spaces.
12972 The overlay system described above is rather simple, and could be
12973 improved in many ways:
12978 If your system has suitable bank switch registers or memory management
12979 hardware, you could use those facilities to make an overlay's load area
12980 contents simply appear at their mapped address in instruction space.
12981 This would probably be faster than copying the overlay to its mapped
12982 area in the usual way.
12985 If your overlays are small enough, you could set aside more than one
12986 overlay area, and have more than one overlay mapped at a time.
12989 You can use overlays to manage data, as well as instructions. In
12990 general, data overlays are even less transparent to your design than
12991 code overlays: whereas code overlays only require care when you call or
12992 return to functions, data overlays require care every time you access
12993 the data. Also, if you change the contents of a data overlay, you
12994 must copy its contents back out to its load address before you can copy a
12995 different data overlay into the same mapped area.
13000 @node Overlay Commands
13001 @section Overlay Commands
13003 To use @value{GDBN}'s overlay support, each overlay in your program must
13004 correspond to a separate section of the executable file. The section's
13005 virtual memory address and load memory address must be the overlay's
13006 mapped and load addresses. Identifying overlays with sections allows
13007 @value{GDBN} to determine the appropriate address of a function or
13008 variable, depending on whether the overlay is mapped or not.
13010 @value{GDBN}'s overlay commands all start with the word @code{overlay};
13011 you can abbreviate this as @code{ov} or @code{ovly}. The commands are:
13016 Disable @value{GDBN}'s overlay support. When overlay support is
13017 disabled, @value{GDBN} assumes that all functions and variables are
13018 always present at their mapped addresses. By default, @value{GDBN}'s
13019 overlay support is disabled.
13021 @item overlay manual
13022 @cindex manual overlay debugging
13023 Enable @dfn{manual} overlay debugging. In this mode, @value{GDBN}
13024 relies on you to tell it which overlays are mapped, and which are not,
13025 using the @code{overlay map-overlay} and @code{overlay unmap-overlay}
13026 commands described below.
13028 @item overlay map-overlay @var{overlay}
13029 @itemx overlay map @var{overlay}
13030 @cindex map an overlay
13031 Tell @value{GDBN} that @var{overlay} is now mapped; @var{overlay} must
13032 be the name of the object file section containing the overlay. When an
13033 overlay is mapped, @value{GDBN} assumes it can find the overlay's
13034 functions and variables at their mapped addresses. @value{GDBN} assumes
13035 that any other overlays whose mapped ranges overlap that of
13036 @var{overlay} are now unmapped.
13038 @item overlay unmap-overlay @var{overlay}
13039 @itemx overlay unmap @var{overlay}
13040 @cindex unmap an overlay
13041 Tell @value{GDBN} that @var{overlay} is no longer mapped; @var{overlay}
13042 must be the name of the object file section containing the overlay.
13043 When an overlay is unmapped, @value{GDBN} assumes it can find the
13044 overlay's functions and variables at their load addresses.
13047 Enable @dfn{automatic} overlay debugging. In this mode, @value{GDBN}
13048 consults a data structure the overlay manager maintains in the inferior
13049 to see which overlays are mapped. For details, see @ref{Automatic
13050 Overlay Debugging}.
13052 @item overlay load-target
13053 @itemx overlay load
13054 @cindex reloading the overlay table
13055 Re-read the overlay table from the inferior. Normally, @value{GDBN}
13056 re-reads the table @value{GDBN} automatically each time the inferior
13057 stops, so this command should only be necessary if you have changed the
13058 overlay mapping yourself using @value{GDBN}. This command is only
13059 useful when using automatic overlay debugging.
13061 @item overlay list-overlays
13062 @itemx overlay list
13063 @cindex listing mapped overlays
13064 Display a list of the overlays currently mapped, along with their mapped
13065 addresses, load addresses, and sizes.
13069 Normally, when @value{GDBN} prints a code address, it includes the name
13070 of the function the address falls in:
13073 (@value{GDBP}) print main
13074 $3 = @{int ()@} 0x11a0 <main>
13077 When overlay debugging is enabled, @value{GDBN} recognizes code in
13078 unmapped overlays, and prints the names of unmapped functions with
13079 asterisks around them. For example, if @code{foo} is a function in an
13080 unmapped overlay, @value{GDBN} prints it this way:
13083 (@value{GDBP}) overlay list
13084 No sections are mapped.
13085 (@value{GDBP}) print foo
13086 $5 = @{int (int)@} 0x100000 <*foo*>
13089 When @code{foo}'s overlay is mapped, @value{GDBN} prints the function's
13093 (@value{GDBP}) overlay list
13094 Section .ov.foo.text, loaded at 0x100000 - 0x100034,
13095 mapped at 0x1016 - 0x104a
13096 (@value{GDBP}) print foo
13097 $6 = @{int (int)@} 0x1016 <foo>
13100 When overlay debugging is enabled, @value{GDBN} can find the correct
13101 address for functions and variables in an overlay, whether or not the
13102 overlay is mapped. This allows most @value{GDBN} commands, like
13103 @code{break} and @code{disassemble}, to work normally, even on unmapped
13104 code. However, @value{GDBN}'s breakpoint support has some limitations:
13108 @cindex breakpoints in overlays
13109 @cindex overlays, setting breakpoints in
13110 You can set breakpoints in functions in unmapped overlays, as long as
13111 @value{GDBN} can write to the overlay at its load address.
13113 @value{GDBN} can not set hardware or simulator-based breakpoints in
13114 unmapped overlays. However, if you set a breakpoint at the end of your
13115 overlay manager (and tell @value{GDBN} which overlays are now mapped, if
13116 you are using manual overlay management), @value{GDBN} will re-set its
13117 breakpoints properly.
13121 @node Automatic Overlay Debugging
13122 @section Automatic Overlay Debugging
13123 @cindex automatic overlay debugging
13125 @value{GDBN} can automatically track which overlays are mapped and which
13126 are not, given some simple co-operation from the overlay manager in the
13127 inferior. If you enable automatic overlay debugging with the
13128 @code{overlay auto} command (@pxref{Overlay Commands}), @value{GDBN}
13129 looks in the inferior's memory for certain variables describing the
13130 current state of the overlays.
13132 Here are the variables your overlay manager must define to support
13133 @value{GDBN}'s automatic overlay debugging:
13137 @item @code{_ovly_table}:
13138 This variable must be an array of the following structures:
13143 /* The overlay's mapped address. */
13146 /* The size of the overlay, in bytes. */
13147 unsigned long size;
13149 /* The overlay's load address. */
13152 /* Non-zero if the overlay is currently mapped;
13154 unsigned long mapped;
13158 @item @code{_novlys}:
13159 This variable must be a four-byte signed integer, holding the total
13160 number of elements in @code{_ovly_table}.
13164 To decide whether a particular overlay is mapped or not, @value{GDBN}
13165 looks for an entry in @w{@code{_ovly_table}} whose @code{vma} and
13166 @code{lma} members equal the VMA and LMA of the overlay's section in the
13167 executable file. When @value{GDBN} finds a matching entry, it consults
13168 the entry's @code{mapped} member to determine whether the overlay is
13171 In addition, your overlay manager may define a function called
13172 @code{_ovly_debug_event}. If this function is defined, @value{GDBN}
13173 will silently set a breakpoint there. If the overlay manager then
13174 calls this function whenever it has changed the overlay table, this
13175 will enable @value{GDBN} to accurately keep track of which overlays
13176 are in program memory, and update any breakpoints that may be set
13177 in overlays. This will allow breakpoints to work even if the
13178 overlays are kept in ROM or other non-writable memory while they
13179 are not being executed.
13181 @node Overlay Sample Program
13182 @section Overlay Sample Program
13183 @cindex overlay example program
13185 When linking a program which uses overlays, you must place the overlays
13186 at their load addresses, while relocating them to run at their mapped
13187 addresses. To do this, you must write a linker script (@pxref{Overlay
13188 Description,,, ld.info, Using ld: the GNU linker}). Unfortunately,
13189 since linker scripts are specific to a particular host system, target
13190 architecture, and target memory layout, this manual cannot provide
13191 portable sample code demonstrating @value{GDBN}'s overlay support.
13193 However, the @value{GDBN} source distribution does contain an overlaid
13194 program, with linker scripts for a few systems, as part of its test
13195 suite. The program consists of the following files from
13196 @file{gdb/testsuite/gdb.base}:
13200 The main program file.
13202 A simple overlay manager, used by @file{overlays.c}.
13207 Overlay modules, loaded and used by @file{overlays.c}.
13210 Linker scripts for linking the test program on the @code{d10v-elf}
13211 and @code{m32r-elf} targets.
13214 You can build the test program using the @code{d10v-elf} GCC
13215 cross-compiler like this:
13218 $ d10v-elf-gcc -g -c overlays.c
13219 $ d10v-elf-gcc -g -c ovlymgr.c
13220 $ d10v-elf-gcc -g -c foo.c
13221 $ d10v-elf-gcc -g -c bar.c
13222 $ d10v-elf-gcc -g -c baz.c
13223 $ d10v-elf-gcc -g -c grbx.c
13224 $ d10v-elf-gcc -g overlays.o ovlymgr.o foo.o bar.o \
13225 baz.o grbx.o -Wl,-Td10v.ld -o overlays
13228 The build process is identical for any other architecture, except that
13229 you must substitute the appropriate compiler and linker script for the
13230 target system for @code{d10v-elf-gcc} and @code{d10v.ld}.
13234 @chapter Using @value{GDBN} with Different Languages
13237 Although programming languages generally have common aspects, they are
13238 rarely expressed in the same manner. For instance, in ANSI C,
13239 dereferencing a pointer @code{p} is accomplished by @code{*p}, but in
13240 Modula-2, it is accomplished by @code{p^}. Values can also be
13241 represented (and displayed) differently. Hex numbers in C appear as
13242 @samp{0x1ae}, while in Modula-2 they appear as @samp{1AEH}.
13244 @cindex working language
13245 Language-specific information is built into @value{GDBN} for some languages,
13246 allowing you to express operations like the above in your program's
13247 native language, and allowing @value{GDBN} to output values in a manner
13248 consistent with the syntax of your program's native language. The
13249 language you use to build expressions is called the @dfn{working
13253 * Setting:: Switching between source languages
13254 * Show:: Displaying the language
13255 * Checks:: Type and range checks
13256 * Supported Languages:: Supported languages
13257 * Unsupported Languages:: Unsupported languages
13261 @section Switching Between Source Languages
13263 There are two ways to control the working language---either have @value{GDBN}
13264 set it automatically, or select it manually yourself. You can use the
13265 @code{set language} command for either purpose. On startup, @value{GDBN}
13266 defaults to setting the language automatically. The working language is
13267 used to determine how expressions you type are interpreted, how values
13270 In addition to the working language, every source file that
13271 @value{GDBN} knows about has its own working language. For some object
13272 file formats, the compiler might indicate which language a particular
13273 source file is in. However, most of the time @value{GDBN} infers the
13274 language from the name of the file. The language of a source file
13275 controls whether C@t{++} names are demangled---this way @code{backtrace} can
13276 show each frame appropriately for its own language. There is no way to
13277 set the language of a source file from within @value{GDBN}, but you can
13278 set the language associated with a filename extension. @xref{Show, ,
13279 Displaying the Language}.
13281 This is most commonly a problem when you use a program, such
13282 as @code{cfront} or @code{f2c}, that generates C but is written in
13283 another language. In that case, make the
13284 program use @code{#line} directives in its C output; that way
13285 @value{GDBN} will know the correct language of the source code of the original
13286 program, and will display that source code, not the generated C code.
13289 * Filenames:: Filename extensions and languages.
13290 * Manually:: Setting the working language manually
13291 * Automatically:: Having @value{GDBN} infer the source language
13295 @subsection List of Filename Extensions and Languages
13297 If a source file name ends in one of the following extensions, then
13298 @value{GDBN} infers that its language is the one indicated.
13316 C@t{++} source file
13322 Objective-C source file
13326 Fortran source file
13329 Modula-2 source file
13333 Assembler source file. This actually behaves almost like C, but
13334 @value{GDBN} does not skip over function prologues when stepping.
13337 In addition, you may set the language associated with a filename
13338 extension. @xref{Show, , Displaying the Language}.
13341 @subsection Setting the Working Language
13343 If you allow @value{GDBN} to set the language automatically,
13344 expressions are interpreted the same way in your debugging session and
13347 @kindex set language
13348 If you wish, you may set the language manually. To do this, issue the
13349 command @samp{set language @var{lang}}, where @var{lang} is the name of
13350 a language, such as
13351 @code{c} or @code{modula-2}.
13352 For a list of the supported languages, type @samp{set language}.
13354 Setting the language manually prevents @value{GDBN} from updating the working
13355 language automatically. This can lead to confusion if you try
13356 to debug a program when the working language is not the same as the
13357 source language, when an expression is acceptable to both
13358 languages---but means different things. For instance, if the current
13359 source file were written in C, and @value{GDBN} was parsing Modula-2, a
13367 might not have the effect you intended. In C, this means to add
13368 @code{b} and @code{c} and place the result in @code{a}. The result
13369 printed would be the value of @code{a}. In Modula-2, this means to compare
13370 @code{a} to the result of @code{b+c}, yielding a @code{BOOLEAN} value.
13372 @node Automatically
13373 @subsection Having @value{GDBN} Infer the Source Language
13375 To have @value{GDBN} set the working language automatically, use
13376 @samp{set language local} or @samp{set language auto}. @value{GDBN}
13377 then infers the working language. That is, when your program stops in a
13378 frame (usually by encountering a breakpoint), @value{GDBN} sets the
13379 working language to the language recorded for the function in that
13380 frame. If the language for a frame is unknown (that is, if the function
13381 or block corresponding to the frame was defined in a source file that
13382 does not have a recognized extension), the current working language is
13383 not changed, and @value{GDBN} issues a warning.
13385 This may not seem necessary for most programs, which are written
13386 entirely in one source language. However, program modules and libraries
13387 written in one source language can be used by a main program written in
13388 a different source language. Using @samp{set language auto} in this
13389 case frees you from having to set the working language manually.
13392 @section Displaying the Language
13394 The following commands help you find out which language is the
13395 working language, and also what language source files were written in.
13398 @item show language
13399 @anchor{show language}
13400 @kindex show language
13401 Display the current working language. This is the
13402 language you can use with commands such as @code{print} to
13403 build and compute expressions that may involve variables in your program.
13406 @kindex info frame@r{, show the source language}
13407 Display the source language for this frame. This language becomes the
13408 working language if you use an identifier from this frame.
13409 @xref{Frame Info, ,Information about a Frame}, to identify the other
13410 information listed here.
13413 @kindex info source@r{, show the source language}
13414 Display the source language of this source file.
13415 @xref{Symbols, ,Examining the Symbol Table}, to identify the other
13416 information listed here.
13419 In unusual circumstances, you may have source files with extensions
13420 not in the standard list. You can then set the extension associated
13421 with a language explicitly:
13424 @item set extension-language @var{ext} @var{language}
13425 @kindex set extension-language
13426 Tell @value{GDBN} that source files with extension @var{ext} are to be
13427 assumed as written in the source language @var{language}.
13429 @item info extensions
13430 @kindex info extensions
13431 List all the filename extensions and the associated languages.
13435 @section Type and Range Checking
13437 Some languages are designed to guard you against making seemingly common
13438 errors through a series of compile- and run-time checks. These include
13439 checking the type of arguments to functions and operators and making
13440 sure mathematical overflows are caught at run time. Checks such as
13441 these help to ensure a program's correctness once it has been compiled
13442 by eliminating type mismatches and providing active checks for range
13443 errors when your program is running.
13445 By default @value{GDBN} checks for these errors according to the
13446 rules of the current source language. Although @value{GDBN} does not check
13447 the statements in your program, it can check expressions entered directly
13448 into @value{GDBN} for evaluation via the @code{print} command, for example.
13451 * Type Checking:: An overview of type checking
13452 * Range Checking:: An overview of range checking
13455 @cindex type checking
13456 @cindex checks, type
13457 @node Type Checking
13458 @subsection An Overview of Type Checking
13460 Some languages, such as C and C@t{++}, are strongly typed, meaning that the
13461 arguments to operators and functions have to be of the correct type,
13462 otherwise an error occurs. These checks prevent type mismatch
13463 errors from ever causing any run-time problems. For example,
13466 int klass::my_method(char *b) @{ return b ? 1 : 2; @}
13468 (@value{GDBP}) print obj.my_method (0)
13471 (@value{GDBP}) print obj.my_method (0x1234)
13472 Cannot resolve method klass::my_method to any overloaded instance
13475 The second example fails because in C@t{++} the integer constant
13476 @samp{0x1234} is not type-compatible with the pointer parameter type.
13478 For the expressions you use in @value{GDBN} commands, you can tell
13479 @value{GDBN} to not enforce strict type checking or
13480 to treat any mismatches as errors and abandon the expression;
13481 When type checking is disabled, @value{GDBN} successfully evaluates
13482 expressions like the second example above.
13484 Even if type checking is off, there may be other reasons
13485 related to type that prevent @value{GDBN} from evaluating an expression.
13486 For instance, @value{GDBN} does not know how to add an @code{int} and
13487 a @code{struct foo}. These particular type errors have nothing to do
13488 with the language in use and usually arise from expressions which make
13489 little sense to evaluate anyway.
13491 @value{GDBN} provides some additional commands for controlling type checking:
13493 @kindex set check type
13494 @kindex show check type
13496 @item set check type on
13497 @itemx set check type off
13498 Set strict type checking on or off. If any type mismatches occur in
13499 evaluating an expression while type checking is on, @value{GDBN} prints a
13500 message and aborts evaluation of the expression.
13502 @item show check type
13503 Show the current setting of type checking and whether @value{GDBN}
13504 is enforcing strict type checking rules.
13507 @cindex range checking
13508 @cindex checks, range
13509 @node Range Checking
13510 @subsection An Overview of Range Checking
13512 In some languages (such as Modula-2), it is an error to exceed the
13513 bounds of a type; this is enforced with run-time checks. Such range
13514 checking is meant to ensure program correctness by making sure
13515 computations do not overflow, or indices on an array element access do
13516 not exceed the bounds of the array.
13518 For expressions you use in @value{GDBN} commands, you can tell
13519 @value{GDBN} to treat range errors in one of three ways: ignore them,
13520 always treat them as errors and abandon the expression, or issue
13521 warnings but evaluate the expression anyway.
13523 A range error can result from numerical overflow, from exceeding an
13524 array index bound, or when you type a constant that is not a member
13525 of any type. Some languages, however, do not treat overflows as an
13526 error. In many implementations of C, mathematical overflow causes the
13527 result to ``wrap around'' to lower values---for example, if @var{m} is
13528 the largest integer value, and @var{s} is the smallest, then
13531 @var{m} + 1 @result{} @var{s}
13534 This, too, is specific to individual languages, and in some cases
13535 specific to individual compilers or machines. @xref{Supported Languages, ,
13536 Supported Languages}, for further details on specific languages.
13538 @value{GDBN} provides some additional commands for controlling the range checker:
13540 @kindex set check range
13541 @kindex show check range
13543 @item set check range auto
13544 Set range checking on or off based on the current working language.
13545 @xref{Supported Languages, ,Supported Languages}, for the default settings for
13548 @item set check range on
13549 @itemx set check range off
13550 Set range checking on or off, overriding the default setting for the
13551 current working language. A warning is issued if the setting does not
13552 match the language default. If a range error occurs and range checking is on,
13553 then a message is printed and evaluation of the expression is aborted.
13555 @item set check range warn
13556 Output messages when the @value{GDBN} range checker detects a range error,
13557 but attempt to evaluate the expression anyway. Evaluating the
13558 expression may still be impossible for other reasons, such as accessing
13559 memory that the process does not own (a typical example from many Unix
13563 Show the current setting of the range checker, and whether or not it is
13564 being set automatically by @value{GDBN}.
13567 @node Supported Languages
13568 @section Supported Languages
13570 @value{GDBN} supports C, C@t{++}, D, Go, Objective-C, Fortran, Java,
13571 OpenCL C, Pascal, assembly, Modula-2, and Ada.
13572 @c This is false ...
13573 Some @value{GDBN} features may be used in expressions regardless of the
13574 language you use: the @value{GDBN} @code{@@} and @code{::} operators,
13575 and the @samp{@{type@}addr} construct (@pxref{Expressions,
13576 ,Expressions}) can be used with the constructs of any supported
13579 The following sections detail to what degree each source language is
13580 supported by @value{GDBN}. These sections are not meant to be language
13581 tutorials or references, but serve only as a reference guide to what the
13582 @value{GDBN} expression parser accepts, and what input and output
13583 formats should look like for different languages. There are many good
13584 books written on each of these languages; please look to these for a
13585 language reference or tutorial.
13588 * C:: C and C@t{++}
13591 * Objective-C:: Objective-C
13592 * OpenCL C:: OpenCL C
13593 * Fortran:: Fortran
13595 * Modula-2:: Modula-2
13600 @subsection C and C@t{++}
13602 @cindex C and C@t{++}
13603 @cindex expressions in C or C@t{++}
13605 Since C and C@t{++} are so closely related, many features of @value{GDBN} apply
13606 to both languages. Whenever this is the case, we discuss those languages
13610 @cindex @code{g++}, @sc{gnu} C@t{++} compiler
13611 @cindex @sc{gnu} C@t{++}
13612 The C@t{++} debugging facilities are jointly implemented by the C@t{++}
13613 compiler and @value{GDBN}. Therefore, to debug your C@t{++} code
13614 effectively, you must compile your C@t{++} programs with a supported
13615 C@t{++} compiler, such as @sc{gnu} @code{g++}, or the HP ANSI C@t{++}
13616 compiler (@code{aCC}).
13619 * C Operators:: C and C@t{++} operators
13620 * C Constants:: C and C@t{++} constants
13621 * C Plus Plus Expressions:: C@t{++} expressions
13622 * C Defaults:: Default settings for C and C@t{++}
13623 * C Checks:: C and C@t{++} type and range checks
13624 * Debugging C:: @value{GDBN} and C
13625 * Debugging C Plus Plus:: @value{GDBN} features for C@t{++}
13626 * Decimal Floating Point:: Numbers in Decimal Floating Point format
13630 @subsubsection C and C@t{++} Operators
13632 @cindex C and C@t{++} operators
13634 Operators must be defined on values of specific types. For instance,
13635 @code{+} is defined on numbers, but not on structures. Operators are
13636 often defined on groups of types.
13638 For the purposes of C and C@t{++}, the following definitions hold:
13643 @emph{Integral types} include @code{int} with any of its storage-class
13644 specifiers; @code{char}; @code{enum}; and, for C@t{++}, @code{bool}.
13647 @emph{Floating-point types} include @code{float}, @code{double}, and
13648 @code{long double} (if supported by the target platform).
13651 @emph{Pointer types} include all types defined as @code{(@var{type} *)}.
13654 @emph{Scalar types} include all of the above.
13659 The following operators are supported. They are listed here
13660 in order of increasing precedence:
13664 The comma or sequencing operator. Expressions in a comma-separated list
13665 are evaluated from left to right, with the result of the entire
13666 expression being the last expression evaluated.
13669 Assignment. The value of an assignment expression is the value
13670 assigned. Defined on scalar types.
13673 Used in an expression of the form @w{@code{@var{a} @var{op}= @var{b}}},
13674 and translated to @w{@code{@var{a} = @var{a op b}}}.
13675 @w{@code{@var{op}=}} and @code{=} have the same precedence.
13676 @var{op} is any one of the operators @code{|}, @code{^}, @code{&},
13677 @code{<<}, @code{>>}, @code{+}, @code{-}, @code{*}, @code{/}, @code{%}.
13680 The ternary operator. @code{@var{a} ? @var{b} : @var{c}} can be thought
13681 of as: if @var{a} then @var{b} else @var{c}. @var{a} should be of an
13685 Logical @sc{or}. Defined on integral types.
13688 Logical @sc{and}. Defined on integral types.
13691 Bitwise @sc{or}. Defined on integral types.
13694 Bitwise exclusive-@sc{or}. Defined on integral types.
13697 Bitwise @sc{and}. Defined on integral types.
13700 Equality and inequality. Defined on scalar types. The value of these
13701 expressions is 0 for false and non-zero for true.
13703 @item <@r{, }>@r{, }<=@r{, }>=
13704 Less than, greater than, less than or equal, greater than or equal.
13705 Defined on scalar types. The value of these expressions is 0 for false
13706 and non-zero for true.
13709 left shift, and right shift. Defined on integral types.
13712 The @value{GDBN} ``artificial array'' operator (@pxref{Expressions, ,Expressions}).
13715 Addition and subtraction. Defined on integral types, floating-point types and
13718 @item *@r{, }/@r{, }%
13719 Multiplication, division, and modulus. Multiplication and division are
13720 defined on integral and floating-point types. Modulus is defined on
13724 Increment and decrement. When appearing before a variable, the
13725 operation is performed before the variable is used in an expression;
13726 when appearing after it, the variable's value is used before the
13727 operation takes place.
13730 Pointer dereferencing. Defined on pointer types. Same precedence as
13734 Address operator. Defined on variables. Same precedence as @code{++}.
13736 For debugging C@t{++}, @value{GDBN} implements a use of @samp{&} beyond what is
13737 allowed in the C@t{++} language itself: you can use @samp{&(&@var{ref})}
13738 to examine the address
13739 where a C@t{++} reference variable (declared with @samp{&@var{ref}}) is
13743 Negative. Defined on integral and floating-point types. Same
13744 precedence as @code{++}.
13747 Logical negation. Defined on integral types. Same precedence as
13751 Bitwise complement operator. Defined on integral types. Same precedence as
13756 Structure member, and pointer-to-structure member. For convenience,
13757 @value{GDBN} regards the two as equivalent, choosing whether to dereference a
13758 pointer based on the stored type information.
13759 Defined on @code{struct} and @code{union} data.
13762 Dereferences of pointers to members.
13765 Array indexing. @code{@var{a}[@var{i}]} is defined as
13766 @code{*(@var{a}+@var{i})}. Same precedence as @code{->}.
13769 Function parameter list. Same precedence as @code{->}.
13772 C@t{++} scope resolution operator. Defined on @code{struct}, @code{union},
13773 and @code{class} types.
13776 Doubled colons also represent the @value{GDBN} scope operator
13777 (@pxref{Expressions, ,Expressions}). Same precedence as @code{::},
13781 If an operator is redefined in the user code, @value{GDBN} usually
13782 attempts to invoke the redefined version instead of using the operator's
13783 predefined meaning.
13786 @subsubsection C and C@t{++} Constants
13788 @cindex C and C@t{++} constants
13790 @value{GDBN} allows you to express the constants of C and C@t{++} in the
13795 Integer constants are a sequence of digits. Octal constants are
13796 specified by a leading @samp{0} (i.e.@: zero), and hexadecimal constants
13797 by a leading @samp{0x} or @samp{0X}. Constants may also end with a letter
13798 @samp{l}, specifying that the constant should be treated as a
13802 Floating point constants are a sequence of digits, followed by a decimal
13803 point, followed by a sequence of digits, and optionally followed by an
13804 exponent. An exponent is of the form:
13805 @samp{@w{e@r{[[}+@r{]|}-@r{]}@var{nnn}}}, where @var{nnn} is another
13806 sequence of digits. The @samp{+} is optional for positive exponents.
13807 A floating-point constant may also end with a letter @samp{f} or
13808 @samp{F}, specifying that the constant should be treated as being of
13809 the @code{float} (as opposed to the default @code{double}) type; or with
13810 a letter @samp{l} or @samp{L}, which specifies a @code{long double}
13814 Enumerated constants consist of enumerated identifiers, or their
13815 integral equivalents.
13818 Character constants are a single character surrounded by single quotes
13819 (@code{'}), or a number---the ordinal value of the corresponding character
13820 (usually its @sc{ascii} value). Within quotes, the single character may
13821 be represented by a letter or by @dfn{escape sequences}, which are of
13822 the form @samp{\@var{nnn}}, where @var{nnn} is the octal representation
13823 of the character's ordinal value; or of the form @samp{\@var{x}}, where
13824 @samp{@var{x}} is a predefined special character---for example,
13825 @samp{\n} for newline.
13827 Wide character constants can be written by prefixing a character
13828 constant with @samp{L}, as in C. For example, @samp{L'x'} is the wide
13829 form of @samp{x}. The target wide character set is used when
13830 computing the value of this constant (@pxref{Character Sets}).
13833 String constants are a sequence of character constants surrounded by
13834 double quotes (@code{"}). Any valid character constant (as described
13835 above) may appear. Double quotes within the string must be preceded by
13836 a backslash, so for instance @samp{"a\"b'c"} is a string of five
13839 Wide string constants can be written by prefixing a string constant
13840 with @samp{L}, as in C. The target wide character set is used when
13841 computing the value of this constant (@pxref{Character Sets}).
13844 Pointer constants are an integral value. You can also write pointers
13845 to constants using the C operator @samp{&}.
13848 Array constants are comma-separated lists surrounded by braces @samp{@{}
13849 and @samp{@}}; for example, @samp{@{1,2,3@}} is a three-element array of
13850 integers, @samp{@{@{1,2@}, @{3,4@}, @{5,6@}@}} is a three-by-two array,
13851 and @samp{@{&"hi", &"there", &"fred"@}} is a three-element array of pointers.
13854 @node C Plus Plus Expressions
13855 @subsubsection C@t{++} Expressions
13857 @cindex expressions in C@t{++}
13858 @value{GDBN} expression handling can interpret most C@t{++} expressions.
13860 @cindex debugging C@t{++} programs
13861 @cindex C@t{++} compilers
13862 @cindex debug formats and C@t{++}
13863 @cindex @value{NGCC} and C@t{++}
13865 @emph{Warning:} @value{GDBN} can only debug C@t{++} code if you use
13866 the proper compiler and the proper debug format. Currently,
13867 @value{GDBN} works best when debugging C@t{++} code that is compiled
13868 with the most recent version of @value{NGCC} possible. The DWARF
13869 debugging format is preferred; @value{NGCC} defaults to this on most
13870 popular platforms. Other compilers and/or debug formats are likely to
13871 work badly or not at all when using @value{GDBN} to debug C@t{++}
13872 code. @xref{Compilation}.
13877 @cindex member functions
13879 Member function calls are allowed; you can use expressions like
13882 count = aml->GetOriginal(x, y)
13885 @vindex this@r{, inside C@t{++} member functions}
13886 @cindex namespace in C@t{++}
13888 While a member function is active (in the selected stack frame), your
13889 expressions have the same namespace available as the member function;
13890 that is, @value{GDBN} allows implicit references to the class instance
13891 pointer @code{this} following the same rules as C@t{++}. @code{using}
13892 declarations in the current scope are also respected by @value{GDBN}.
13894 @cindex call overloaded functions
13895 @cindex overloaded functions, calling
13896 @cindex type conversions in C@t{++}
13898 You can call overloaded functions; @value{GDBN} resolves the function
13899 call to the right definition, with some restrictions. @value{GDBN} does not
13900 perform overload resolution involving user-defined type conversions,
13901 calls to constructors, or instantiations of templates that do not exist
13902 in the program. It also cannot handle ellipsis argument lists or
13905 It does perform integral conversions and promotions, floating-point
13906 promotions, arithmetic conversions, pointer conversions, conversions of
13907 class objects to base classes, and standard conversions such as those of
13908 functions or arrays to pointers; it requires an exact match on the
13909 number of function arguments.
13911 Overload resolution is always performed, unless you have specified
13912 @code{set overload-resolution off}. @xref{Debugging C Plus Plus,
13913 ,@value{GDBN} Features for C@t{++}}.
13915 You must specify @code{set overload-resolution off} in order to use an
13916 explicit function signature to call an overloaded function, as in
13918 p 'foo(char,int)'('x', 13)
13921 The @value{GDBN} command-completion facility can simplify this;
13922 see @ref{Completion, ,Command Completion}.
13924 @cindex reference declarations
13926 @value{GDBN} understands variables declared as C@t{++} references; you can use
13927 them in expressions just as you do in C@t{++} source---they are automatically
13930 In the parameter list shown when @value{GDBN} displays a frame, the values of
13931 reference variables are not displayed (unlike other variables); this
13932 avoids clutter, since references are often used for large structures.
13933 The @emph{address} of a reference variable is always shown, unless
13934 you have specified @samp{set print address off}.
13937 @value{GDBN} supports the C@t{++} name resolution operator @code{::}---your
13938 expressions can use it just as expressions in your program do. Since
13939 one scope may be defined in another, you can use @code{::} repeatedly if
13940 necessary, for example in an expression like
13941 @samp{@var{scope1}::@var{scope2}::@var{name}}. @value{GDBN} also allows
13942 resolving name scope by reference to source files, in both C and C@t{++}
13943 debugging (@pxref{Variables, ,Program Variables}).
13946 @value{GDBN} performs argument-dependent lookup, following the C@t{++}
13951 @subsubsection C and C@t{++} Defaults
13953 @cindex C and C@t{++} defaults
13955 If you allow @value{GDBN} to set range checking automatically, it
13956 defaults to @code{off} whenever the working language changes to
13957 C or C@t{++}. This happens regardless of whether you or @value{GDBN}
13958 selects the working language.
13960 If you allow @value{GDBN} to set the language automatically, it
13961 recognizes source files whose names end with @file{.c}, @file{.C}, or
13962 @file{.cc}, etc, and when @value{GDBN} enters code compiled from one of
13963 these files, it sets the working language to C or C@t{++}.
13964 @xref{Automatically, ,Having @value{GDBN} Infer the Source Language},
13965 for further details.
13968 @subsubsection C and C@t{++} Type and Range Checks
13970 @cindex C and C@t{++} checks
13972 By default, when @value{GDBN} parses C or C@t{++} expressions, strict type
13973 checking is used. However, if you turn type checking off, @value{GDBN}
13974 will allow certain non-standard conversions, such as promoting integer
13975 constants to pointers.
13977 Range checking, if turned on, is done on mathematical operations. Array
13978 indices are not checked, since they are often used to index a pointer
13979 that is not itself an array.
13982 @subsubsection @value{GDBN} and C
13984 The @code{set print union} and @code{show print union} commands apply to
13985 the @code{union} type. When set to @samp{on}, any @code{union} that is
13986 inside a @code{struct} or @code{class} is also printed. Otherwise, it
13987 appears as @samp{@{...@}}.
13989 The @code{@@} operator aids in the debugging of dynamic arrays, formed
13990 with pointers and a memory allocation function. @xref{Expressions,
13993 @node Debugging C Plus Plus
13994 @subsubsection @value{GDBN} Features for C@t{++}
13996 @cindex commands for C@t{++}
13998 Some @value{GDBN} commands are particularly useful with C@t{++}, and some are
13999 designed specifically for use with C@t{++}. Here is a summary:
14002 @cindex break in overloaded functions
14003 @item @r{breakpoint menus}
14004 When you want a breakpoint in a function whose name is overloaded,
14005 @value{GDBN} has the capability to display a menu of possible breakpoint
14006 locations to help you specify which function definition you want.
14007 @xref{Ambiguous Expressions,,Ambiguous Expressions}.
14009 @cindex overloading in C@t{++}
14010 @item rbreak @var{regex}
14011 Setting breakpoints using regular expressions is helpful for setting
14012 breakpoints on overloaded functions that are not members of any special
14014 @xref{Set Breaks, ,Setting Breakpoints}.
14016 @cindex C@t{++} exception handling
14018 @itemx catch rethrow
14020 Debug C@t{++} exception handling using these commands. @xref{Set
14021 Catchpoints, , Setting Catchpoints}.
14023 @cindex inheritance
14024 @item ptype @var{typename}
14025 Print inheritance relationships as well as other information for type
14027 @xref{Symbols, ,Examining the Symbol Table}.
14029 @item info vtbl @var{expression}.
14030 The @code{info vtbl} command can be used to display the virtual
14031 method tables of the object computed by @var{expression}. This shows
14032 one entry per virtual table; there may be multiple virtual tables when
14033 multiple inheritance is in use.
14035 @cindex C@t{++} symbol display
14036 @item set print demangle
14037 @itemx show print demangle
14038 @itemx set print asm-demangle
14039 @itemx show print asm-demangle
14040 Control whether C@t{++} symbols display in their source form, both when
14041 displaying code as C@t{++} source and when displaying disassemblies.
14042 @xref{Print Settings, ,Print Settings}.
14044 @item set print object
14045 @itemx show print object
14046 Choose whether to print derived (actual) or declared types of objects.
14047 @xref{Print Settings, ,Print Settings}.
14049 @item set print vtbl
14050 @itemx show print vtbl
14051 Control the format for printing virtual function tables.
14052 @xref{Print Settings, ,Print Settings}.
14053 (The @code{vtbl} commands do not work on programs compiled with the HP
14054 ANSI C@t{++} compiler (@code{aCC}).)
14056 @kindex set overload-resolution
14057 @cindex overloaded functions, overload resolution
14058 @item set overload-resolution on
14059 Enable overload resolution for C@t{++} expression evaluation. The default
14060 is on. For overloaded functions, @value{GDBN} evaluates the arguments
14061 and searches for a function whose signature matches the argument types,
14062 using the standard C@t{++} conversion rules (see @ref{C Plus Plus
14063 Expressions, ,C@t{++} Expressions}, for details).
14064 If it cannot find a match, it emits a message.
14066 @item set overload-resolution off
14067 Disable overload resolution for C@t{++} expression evaluation. For
14068 overloaded functions that are not class member functions, @value{GDBN}
14069 chooses the first function of the specified name that it finds in the
14070 symbol table, whether or not its arguments are of the correct type. For
14071 overloaded functions that are class member functions, @value{GDBN}
14072 searches for a function whose signature @emph{exactly} matches the
14075 @kindex show overload-resolution
14076 @item show overload-resolution
14077 Show the current setting of overload resolution.
14079 @item @r{Overloaded symbol names}
14080 You can specify a particular definition of an overloaded symbol, using
14081 the same notation that is used to declare such symbols in C@t{++}: type
14082 @code{@var{symbol}(@var{types})} rather than just @var{symbol}. You can
14083 also use the @value{GDBN} command-line word completion facilities to list the
14084 available choices, or to finish the type list for you.
14085 @xref{Completion,, Command Completion}, for details on how to do this.
14088 @node Decimal Floating Point
14089 @subsubsection Decimal Floating Point format
14090 @cindex decimal floating point format
14092 @value{GDBN} can examine, set and perform computations with numbers in
14093 decimal floating point format, which in the C language correspond to the
14094 @code{_Decimal32}, @code{_Decimal64} and @code{_Decimal128} types as
14095 specified by the extension to support decimal floating-point arithmetic.
14097 There are two encodings in use, depending on the architecture: BID (Binary
14098 Integer Decimal) for x86 and x86-64, and DPD (Densely Packed Decimal) for
14099 PowerPC and S/390. @value{GDBN} will use the appropriate encoding for the
14102 Because of a limitation in @file{libdecnumber}, the library used by @value{GDBN}
14103 to manipulate decimal floating point numbers, it is not possible to convert
14104 (using a cast, for example) integers wider than 32-bit to decimal float.
14106 In addition, in order to imitate @value{GDBN}'s behaviour with binary floating
14107 point computations, error checking in decimal float operations ignores
14108 underflow, overflow and divide by zero exceptions.
14110 In the PowerPC architecture, @value{GDBN} provides a set of pseudo-registers
14111 to inspect @code{_Decimal128} values stored in floating point registers.
14112 See @ref{PowerPC,,PowerPC} for more details.
14118 @value{GDBN} can be used to debug programs written in D and compiled with
14119 GDC, LDC or DMD compilers. Currently @value{GDBN} supports only one D
14120 specific feature --- dynamic arrays.
14125 @cindex Go (programming language)
14126 @value{GDBN} can be used to debug programs written in Go and compiled with
14127 @file{gccgo} or @file{6g} compilers.
14129 Here is a summary of the Go-specific features and restrictions:
14132 @cindex current Go package
14133 @item The current Go package
14134 The name of the current package does not need to be specified when
14135 specifying global variables and functions.
14137 For example, given the program:
14141 var myglob = "Shall we?"
14147 When stopped inside @code{main} either of these work:
14151 (gdb) p main.myglob
14154 @cindex builtin Go types
14155 @item Builtin Go types
14156 The @code{string} type is recognized by @value{GDBN} and is printed
14159 @cindex builtin Go functions
14160 @item Builtin Go functions
14161 The @value{GDBN} expression parser recognizes the @code{unsafe.Sizeof}
14162 function and handles it internally.
14164 @cindex restrictions on Go expressions
14165 @item Restrictions on Go expressions
14166 All Go operators are supported except @code{&^}.
14167 The Go @code{_} ``blank identifier'' is not supported.
14168 Automatic dereferencing of pointers is not supported.
14172 @subsection Objective-C
14174 @cindex Objective-C
14175 This section provides information about some commands and command
14176 options that are useful for debugging Objective-C code. See also
14177 @ref{Symbols, info classes}, and @ref{Symbols, info selectors}, for a
14178 few more commands specific to Objective-C support.
14181 * Method Names in Commands::
14182 * The Print Command with Objective-C::
14185 @node Method Names in Commands
14186 @subsubsection Method Names in Commands
14188 The following commands have been extended to accept Objective-C method
14189 names as line specifications:
14191 @kindex clear@r{, and Objective-C}
14192 @kindex break@r{, and Objective-C}
14193 @kindex info line@r{, and Objective-C}
14194 @kindex jump@r{, and Objective-C}
14195 @kindex list@r{, and Objective-C}
14199 @item @code{info line}
14204 A fully qualified Objective-C method name is specified as
14207 -[@var{Class} @var{methodName}]
14210 where the minus sign is used to indicate an instance method and a
14211 plus sign (not shown) is used to indicate a class method. The class
14212 name @var{Class} and method name @var{methodName} are enclosed in
14213 brackets, similar to the way messages are specified in Objective-C
14214 source code. For example, to set a breakpoint at the @code{create}
14215 instance method of class @code{Fruit} in the program currently being
14219 break -[Fruit create]
14222 To list ten program lines around the @code{initialize} class method,
14226 list +[NSText initialize]
14229 In the current version of @value{GDBN}, the plus or minus sign is
14230 required. In future versions of @value{GDBN}, the plus or minus
14231 sign will be optional, but you can use it to narrow the search. It
14232 is also possible to specify just a method name:
14238 You must specify the complete method name, including any colons. If
14239 your program's source files contain more than one @code{create} method,
14240 you'll be presented with a numbered list of classes that implement that
14241 method. Indicate your choice by number, or type @samp{0} to exit if
14244 As another example, to clear a breakpoint established at the
14245 @code{makeKeyAndOrderFront:} method of the @code{NSWindow} class, enter:
14248 clear -[NSWindow makeKeyAndOrderFront:]
14251 @node The Print Command with Objective-C
14252 @subsubsection The Print Command With Objective-C
14253 @cindex Objective-C, print objects
14254 @kindex print-object
14255 @kindex po @r{(@code{print-object})}
14257 The print command has also been extended to accept methods. For example:
14260 print -[@var{object} hash]
14263 @cindex print an Objective-C object description
14264 @cindex @code{_NSPrintForDebugger}, and printing Objective-C objects
14266 will tell @value{GDBN} to send the @code{hash} message to @var{object}
14267 and print the result. Also, an additional command has been added,
14268 @code{print-object} or @code{po} for short, which is meant to print
14269 the description of an object. However, this command may only work
14270 with certain Objective-C libraries that have a particular hook
14271 function, @code{_NSPrintForDebugger}, defined.
14274 @subsection OpenCL C
14277 This section provides information about @value{GDBN}s OpenCL C support.
14280 * OpenCL C Datatypes::
14281 * OpenCL C Expressions::
14282 * OpenCL C Operators::
14285 @node OpenCL C Datatypes
14286 @subsubsection OpenCL C Datatypes
14288 @cindex OpenCL C Datatypes
14289 @value{GDBN} supports the builtin scalar and vector datatypes specified
14290 by OpenCL 1.1. In addition the half- and double-precision floating point
14291 data types of the @code{cl_khr_fp16} and @code{cl_khr_fp64} OpenCL
14292 extensions are also known to @value{GDBN}.
14294 @node OpenCL C Expressions
14295 @subsubsection OpenCL C Expressions
14297 @cindex OpenCL C Expressions
14298 @value{GDBN} supports accesses to vector components including the access as
14299 lvalue where possible. Since OpenCL C is based on C99 most C expressions
14300 supported by @value{GDBN} can be used as well.
14302 @node OpenCL C Operators
14303 @subsubsection OpenCL C Operators
14305 @cindex OpenCL C Operators
14306 @value{GDBN} supports the operators specified by OpenCL 1.1 for scalar and
14310 @subsection Fortran
14311 @cindex Fortran-specific support in @value{GDBN}
14313 @value{GDBN} can be used to debug programs written in Fortran, but it
14314 currently supports only the features of Fortran 77 language.
14316 @cindex trailing underscore, in Fortran symbols
14317 Some Fortran compilers (@sc{gnu} Fortran 77 and Fortran 95 compilers
14318 among them) append an underscore to the names of variables and
14319 functions. When you debug programs compiled by those compilers, you
14320 will need to refer to variables and functions with a trailing
14324 * Fortran Operators:: Fortran operators and expressions
14325 * Fortran Defaults:: Default settings for Fortran
14326 * Special Fortran Commands:: Special @value{GDBN} commands for Fortran
14329 @node Fortran Operators
14330 @subsubsection Fortran Operators and Expressions
14332 @cindex Fortran operators and expressions
14334 Operators must be defined on values of specific types. For instance,
14335 @code{+} is defined on numbers, but not on characters or other non-
14336 arithmetic types. Operators are often defined on groups of types.
14340 The exponentiation operator. It raises the first operand to the power
14344 The range operator. Normally used in the form of array(low:high) to
14345 represent a section of array.
14348 The access component operator. Normally used to access elements in derived
14349 types. Also suitable for unions. As unions aren't part of regular Fortran,
14350 this can only happen when accessing a register that uses a gdbarch-defined
14354 @node Fortran Defaults
14355 @subsubsection Fortran Defaults
14357 @cindex Fortran Defaults
14359 Fortran symbols are usually case-insensitive, so @value{GDBN} by
14360 default uses case-insensitive matches for Fortran symbols. You can
14361 change that with the @samp{set case-insensitive} command, see
14362 @ref{Symbols}, for the details.
14364 @node Special Fortran Commands
14365 @subsubsection Special Fortran Commands
14367 @cindex Special Fortran commands
14369 @value{GDBN} has some commands to support Fortran-specific features,
14370 such as displaying common blocks.
14373 @cindex @code{COMMON} blocks, Fortran
14374 @kindex info common
14375 @item info common @r{[}@var{common-name}@r{]}
14376 This command prints the values contained in the Fortran @code{COMMON}
14377 block whose name is @var{common-name}. With no argument, the names of
14378 all @code{COMMON} blocks visible at the current program location are
14385 @cindex Pascal support in @value{GDBN}, limitations
14386 Debugging Pascal programs which use sets, subranges, file variables, or
14387 nested functions does not currently work. @value{GDBN} does not support
14388 entering expressions, printing values, or similar features using Pascal
14391 The Pascal-specific command @code{set print pascal_static-members}
14392 controls whether static members of Pascal objects are displayed.
14393 @xref{Print Settings, pascal_static-members}.
14396 @subsection Modula-2
14398 @cindex Modula-2, @value{GDBN} support
14400 The extensions made to @value{GDBN} to support Modula-2 only support
14401 output from the @sc{gnu} Modula-2 compiler (which is currently being
14402 developed). Other Modula-2 compilers are not currently supported, and
14403 attempting to debug executables produced by them is most likely
14404 to give an error as @value{GDBN} reads in the executable's symbol
14407 @cindex expressions in Modula-2
14409 * M2 Operators:: Built-in operators
14410 * Built-In Func/Proc:: Built-in functions and procedures
14411 * M2 Constants:: Modula-2 constants
14412 * M2 Types:: Modula-2 types
14413 * M2 Defaults:: Default settings for Modula-2
14414 * Deviations:: Deviations from standard Modula-2
14415 * M2 Checks:: Modula-2 type and range checks
14416 * M2 Scope:: The scope operators @code{::} and @code{.}
14417 * GDB/M2:: @value{GDBN} and Modula-2
14421 @subsubsection Operators
14422 @cindex Modula-2 operators
14424 Operators must be defined on values of specific types. For instance,
14425 @code{+} is defined on numbers, but not on structures. Operators are
14426 often defined on groups of types. For the purposes of Modula-2, the
14427 following definitions hold:
14432 @emph{Integral types} consist of @code{INTEGER}, @code{CARDINAL}, and
14436 @emph{Character types} consist of @code{CHAR} and its subranges.
14439 @emph{Floating-point types} consist of @code{REAL}.
14442 @emph{Pointer types} consist of anything declared as @code{POINTER TO
14446 @emph{Scalar types} consist of all of the above.
14449 @emph{Set types} consist of @code{SET} and @code{BITSET} types.
14452 @emph{Boolean types} consist of @code{BOOLEAN}.
14456 The following operators are supported, and appear in order of
14457 increasing precedence:
14461 Function argument or array index separator.
14464 Assignment. The value of @var{var} @code{:=} @var{value} is
14468 Less than, greater than on integral, floating-point, or enumerated
14472 Less than or equal to, greater than or equal to
14473 on integral, floating-point and enumerated types, or set inclusion on
14474 set types. Same precedence as @code{<}.
14476 @item =@r{, }<>@r{, }#
14477 Equality and two ways of expressing inequality, valid on scalar types.
14478 Same precedence as @code{<}. In @value{GDBN} scripts, only @code{<>} is
14479 available for inequality, since @code{#} conflicts with the script
14483 Set membership. Defined on set types and the types of their members.
14484 Same precedence as @code{<}.
14487 Boolean disjunction. Defined on boolean types.
14490 Boolean conjunction. Defined on boolean types.
14493 The @value{GDBN} ``artificial array'' operator (@pxref{Expressions, ,Expressions}).
14496 Addition and subtraction on integral and floating-point types, or union
14497 and difference on set types.
14500 Multiplication on integral and floating-point types, or set intersection
14504 Division on floating-point types, or symmetric set difference on set
14505 types. Same precedence as @code{*}.
14508 Integer division and remainder. Defined on integral types. Same
14509 precedence as @code{*}.
14512 Negative. Defined on @code{INTEGER} and @code{REAL} data.
14515 Pointer dereferencing. Defined on pointer types.
14518 Boolean negation. Defined on boolean types. Same precedence as
14522 @code{RECORD} field selector. Defined on @code{RECORD} data. Same
14523 precedence as @code{^}.
14526 Array indexing. Defined on @code{ARRAY} data. Same precedence as @code{^}.
14529 Procedure argument list. Defined on @code{PROCEDURE} objects. Same precedence
14533 @value{GDBN} and Modula-2 scope operators.
14537 @emph{Warning:} Set expressions and their operations are not yet supported, so @value{GDBN}
14538 treats the use of the operator @code{IN}, or the use of operators
14539 @code{+}, @code{-}, @code{*}, @code{/}, @code{=}, , @code{<>}, @code{#},
14540 @code{<=}, and @code{>=} on sets as an error.
14544 @node Built-In Func/Proc
14545 @subsubsection Built-in Functions and Procedures
14546 @cindex Modula-2 built-ins
14548 Modula-2 also makes available several built-in procedures and functions.
14549 In describing these, the following metavariables are used:
14554 represents an @code{ARRAY} variable.
14557 represents a @code{CHAR} constant or variable.
14560 represents a variable or constant of integral type.
14563 represents an identifier that belongs to a set. Generally used in the
14564 same function with the metavariable @var{s}. The type of @var{s} should
14565 be @code{SET OF @var{mtype}} (where @var{mtype} is the type of @var{m}).
14568 represents a variable or constant of integral or floating-point type.
14571 represents a variable or constant of floating-point type.
14577 represents a variable.
14580 represents a variable or constant of one of many types. See the
14581 explanation of the function for details.
14584 All Modula-2 built-in procedures also return a result, described below.
14588 Returns the absolute value of @var{n}.
14591 If @var{c} is a lower case letter, it returns its upper case
14592 equivalent, otherwise it returns its argument.
14595 Returns the character whose ordinal value is @var{i}.
14598 Decrements the value in the variable @var{v} by one. Returns the new value.
14600 @item DEC(@var{v},@var{i})
14601 Decrements the value in the variable @var{v} by @var{i}. Returns the
14604 @item EXCL(@var{m},@var{s})
14605 Removes the element @var{m} from the set @var{s}. Returns the new
14608 @item FLOAT(@var{i})
14609 Returns the floating point equivalent of the integer @var{i}.
14611 @item HIGH(@var{a})
14612 Returns the index of the last member of @var{a}.
14615 Increments the value in the variable @var{v} by one. Returns the new value.
14617 @item INC(@var{v},@var{i})
14618 Increments the value in the variable @var{v} by @var{i}. Returns the
14621 @item INCL(@var{m},@var{s})
14622 Adds the element @var{m} to the set @var{s} if it is not already
14623 there. Returns the new set.
14626 Returns the maximum value of the type @var{t}.
14629 Returns the minimum value of the type @var{t}.
14632 Returns boolean TRUE if @var{i} is an odd number.
14635 Returns the ordinal value of its argument. For example, the ordinal
14636 value of a character is its @sc{ascii} value (on machines supporting the
14637 @sc{ascii} character set). @var{x} must be of an ordered type, which include
14638 integral, character and enumerated types.
14640 @item SIZE(@var{x})
14641 Returns the size of its argument. @var{x} can be a variable or a type.
14643 @item TRUNC(@var{r})
14644 Returns the integral part of @var{r}.
14646 @item TSIZE(@var{x})
14647 Returns the size of its argument. @var{x} can be a variable or a type.
14649 @item VAL(@var{t},@var{i})
14650 Returns the member of the type @var{t} whose ordinal value is @var{i}.
14654 @emph{Warning:} Sets and their operations are not yet supported, so
14655 @value{GDBN} treats the use of procedures @code{INCL} and @code{EXCL} as
14659 @cindex Modula-2 constants
14661 @subsubsection Constants
14663 @value{GDBN} allows you to express the constants of Modula-2 in the following
14669 Integer constants are simply a sequence of digits. When used in an
14670 expression, a constant is interpreted to be type-compatible with the
14671 rest of the expression. Hexadecimal integers are specified by a
14672 trailing @samp{H}, and octal integers by a trailing @samp{B}.
14675 Floating point constants appear as a sequence of digits, followed by a
14676 decimal point and another sequence of digits. An optional exponent can
14677 then be specified, in the form @samp{E@r{[}+@r{|}-@r{]}@var{nnn}}, where
14678 @samp{@r{[}+@r{|}-@r{]}@var{nnn}} is the desired exponent. All of the
14679 digits of the floating point constant must be valid decimal (base 10)
14683 Character constants consist of a single character enclosed by a pair of
14684 like quotes, either single (@code{'}) or double (@code{"}). They may
14685 also be expressed by their ordinal value (their @sc{ascii} value, usually)
14686 followed by a @samp{C}.
14689 String constants consist of a sequence of characters enclosed by a
14690 pair of like quotes, either single (@code{'}) or double (@code{"}).
14691 Escape sequences in the style of C are also allowed. @xref{C
14692 Constants, ,C and C@t{++} Constants}, for a brief explanation of escape
14696 Enumerated constants consist of an enumerated identifier.
14699 Boolean constants consist of the identifiers @code{TRUE} and
14703 Pointer constants consist of integral values only.
14706 Set constants are not yet supported.
14710 @subsubsection Modula-2 Types
14711 @cindex Modula-2 types
14713 Currently @value{GDBN} can print the following data types in Modula-2
14714 syntax: array types, record types, set types, pointer types, procedure
14715 types, enumerated types, subrange types and base types. You can also
14716 print the contents of variables declared using these type.
14717 This section gives a number of simple source code examples together with
14718 sample @value{GDBN} sessions.
14720 The first example contains the following section of code:
14729 and you can request @value{GDBN} to interrogate the type and value of
14730 @code{r} and @code{s}.
14733 (@value{GDBP}) print s
14735 (@value{GDBP}) ptype s
14737 (@value{GDBP}) print r
14739 (@value{GDBP}) ptype r
14744 Likewise if your source code declares @code{s} as:
14748 s: SET ['A'..'Z'] ;
14752 then you may query the type of @code{s} by:
14755 (@value{GDBP}) ptype s
14756 type = SET ['A'..'Z']
14760 Note that at present you cannot interactively manipulate set
14761 expressions using the debugger.
14763 The following example shows how you might declare an array in Modula-2
14764 and how you can interact with @value{GDBN} to print its type and contents:
14768 s: ARRAY [-10..10] OF CHAR ;
14772 (@value{GDBP}) ptype s
14773 ARRAY [-10..10] OF CHAR
14776 Note that the array handling is not yet complete and although the type
14777 is printed correctly, expression handling still assumes that all
14778 arrays have a lower bound of zero and not @code{-10} as in the example
14781 Here are some more type related Modula-2 examples:
14785 colour = (blue, red, yellow, green) ;
14786 t = [blue..yellow] ;
14794 The @value{GDBN} interaction shows how you can query the data type
14795 and value of a variable.
14798 (@value{GDBP}) print s
14800 (@value{GDBP}) ptype t
14801 type = [blue..yellow]
14805 In this example a Modula-2 array is declared and its contents
14806 displayed. Observe that the contents are written in the same way as
14807 their @code{C} counterparts.
14811 s: ARRAY [1..5] OF CARDINAL ;
14817 (@value{GDBP}) print s
14818 $1 = @{1, 0, 0, 0, 0@}
14819 (@value{GDBP}) ptype s
14820 type = ARRAY [1..5] OF CARDINAL
14823 The Modula-2 language interface to @value{GDBN} also understands
14824 pointer types as shown in this example:
14828 s: POINTER TO ARRAY [1..5] OF CARDINAL ;
14835 and you can request that @value{GDBN} describes the type of @code{s}.
14838 (@value{GDBP}) ptype s
14839 type = POINTER TO ARRAY [1..5] OF CARDINAL
14842 @value{GDBN} handles compound types as we can see in this example.
14843 Here we combine array types, record types, pointer types and subrange
14854 myarray = ARRAY myrange OF CARDINAL ;
14855 myrange = [-2..2] ;
14857 s: POINTER TO ARRAY myrange OF foo ;
14861 and you can ask @value{GDBN} to describe the type of @code{s} as shown
14865 (@value{GDBP}) ptype s
14866 type = POINTER TO ARRAY [-2..2] OF foo = RECORD
14869 f3 : ARRAY [-2..2] OF CARDINAL;
14874 @subsubsection Modula-2 Defaults
14875 @cindex Modula-2 defaults
14877 If type and range checking are set automatically by @value{GDBN}, they
14878 both default to @code{on} whenever the working language changes to
14879 Modula-2. This happens regardless of whether you or @value{GDBN}
14880 selected the working language.
14882 If you allow @value{GDBN} to set the language automatically, then entering
14883 code compiled from a file whose name ends with @file{.mod} sets the
14884 working language to Modula-2. @xref{Automatically, ,Having @value{GDBN}
14885 Infer the Source Language}, for further details.
14888 @subsubsection Deviations from Standard Modula-2
14889 @cindex Modula-2, deviations from
14891 A few changes have been made to make Modula-2 programs easier to debug.
14892 This is done primarily via loosening its type strictness:
14896 Unlike in standard Modula-2, pointer constants can be formed by
14897 integers. This allows you to modify pointer variables during
14898 debugging. (In standard Modula-2, the actual address contained in a
14899 pointer variable is hidden from you; it can only be modified
14900 through direct assignment to another pointer variable or expression that
14901 returned a pointer.)
14904 C escape sequences can be used in strings and characters to represent
14905 non-printable characters. @value{GDBN} prints out strings with these
14906 escape sequences embedded. Single non-printable characters are
14907 printed using the @samp{CHR(@var{nnn})} format.
14910 The assignment operator (@code{:=}) returns the value of its right-hand
14914 All built-in procedures both modify @emph{and} return their argument.
14918 @subsubsection Modula-2 Type and Range Checks
14919 @cindex Modula-2 checks
14922 @emph{Warning:} in this release, @value{GDBN} does not yet perform type or
14925 @c FIXME remove warning when type/range checks added
14927 @value{GDBN} considers two Modula-2 variables type equivalent if:
14931 They are of types that have been declared equivalent via a @code{TYPE
14932 @var{t1} = @var{t2}} statement
14935 They have been declared on the same line. (Note: This is true of the
14936 @sc{gnu} Modula-2 compiler, but it may not be true of other compilers.)
14939 As long as type checking is enabled, any attempt to combine variables
14940 whose types are not equivalent is an error.
14942 Range checking is done on all mathematical operations, assignment, array
14943 index bounds, and all built-in functions and procedures.
14946 @subsubsection The Scope Operators @code{::} and @code{.}
14948 @cindex @code{.}, Modula-2 scope operator
14949 @cindex colon, doubled as scope operator
14951 @vindex colon-colon@r{, in Modula-2}
14952 @c Info cannot handle :: but TeX can.
14955 @vindex ::@r{, in Modula-2}
14958 There are a few subtle differences between the Modula-2 scope operator
14959 (@code{.}) and the @value{GDBN} scope operator (@code{::}). The two have
14964 @var{module} . @var{id}
14965 @var{scope} :: @var{id}
14969 where @var{scope} is the name of a module or a procedure,
14970 @var{module} the name of a module, and @var{id} is any declared
14971 identifier within your program, except another module.
14973 Using the @code{::} operator makes @value{GDBN} search the scope
14974 specified by @var{scope} for the identifier @var{id}. If it is not
14975 found in the specified scope, then @value{GDBN} searches all scopes
14976 enclosing the one specified by @var{scope}.
14978 Using the @code{.} operator makes @value{GDBN} search the current scope for
14979 the identifier specified by @var{id} that was imported from the
14980 definition module specified by @var{module}. With this operator, it is
14981 an error if the identifier @var{id} was not imported from definition
14982 module @var{module}, or if @var{id} is not an identifier in
14986 @subsubsection @value{GDBN} and Modula-2
14988 Some @value{GDBN} commands have little use when debugging Modula-2 programs.
14989 Five subcommands of @code{set print} and @code{show print} apply
14990 specifically to C and C@t{++}: @samp{vtbl}, @samp{demangle},
14991 @samp{asm-demangle}, @samp{object}, and @samp{union}. The first four
14992 apply to C@t{++}, and the last to the C @code{union} type, which has no direct
14993 analogue in Modula-2.
14995 The @code{@@} operator (@pxref{Expressions, ,Expressions}), while available
14996 with any language, is not useful with Modula-2. Its
14997 intent is to aid the debugging of @dfn{dynamic arrays}, which cannot be
14998 created in Modula-2 as they can in C or C@t{++}. However, because an
14999 address can be specified by an integral constant, the construct
15000 @samp{@{@var{type}@}@var{adrexp}} is still useful.
15002 @cindex @code{#} in Modula-2
15003 In @value{GDBN} scripts, the Modula-2 inequality operator @code{#} is
15004 interpreted as the beginning of a comment. Use @code{<>} instead.
15010 The extensions made to @value{GDBN} for Ada only support
15011 output from the @sc{gnu} Ada (GNAT) compiler.
15012 Other Ada compilers are not currently supported, and
15013 attempting to debug executables produced by them is most likely
15017 @cindex expressions in Ada
15019 * Ada Mode Intro:: General remarks on the Ada syntax
15020 and semantics supported by Ada mode
15022 * Omissions from Ada:: Restrictions on the Ada expression syntax.
15023 * Additions to Ada:: Extensions of the Ada expression syntax.
15024 * Stopping Before Main Program:: Debugging the program during elaboration.
15025 * Ada Exceptions:: Ada Exceptions
15026 * Ada Tasks:: Listing and setting breakpoints in tasks.
15027 * Ada Tasks and Core Files:: Tasking Support when Debugging Core Files
15028 * Ravenscar Profile:: Tasking Support when using the Ravenscar
15030 * Ada Glitches:: Known peculiarities of Ada mode.
15033 @node Ada Mode Intro
15034 @subsubsection Introduction
15035 @cindex Ada mode, general
15037 The Ada mode of @value{GDBN} supports a fairly large subset of Ada expression
15038 syntax, with some extensions.
15039 The philosophy behind the design of this subset is
15043 That @value{GDBN} should provide basic literals and access to operations for
15044 arithmetic, dereferencing, field selection, indexing, and subprogram calls,
15045 leaving more sophisticated computations to subprograms written into the
15046 program (which therefore may be called from @value{GDBN}).
15049 That type safety and strict adherence to Ada language restrictions
15050 are not particularly important to the @value{GDBN} user.
15053 That brevity is important to the @value{GDBN} user.
15056 Thus, for brevity, the debugger acts as if all names declared in
15057 user-written packages are directly visible, even if they are not visible
15058 according to Ada rules, thus making it unnecessary to fully qualify most
15059 names with their packages, regardless of context. Where this causes
15060 ambiguity, @value{GDBN} asks the user's intent.
15062 The debugger will start in Ada mode if it detects an Ada main program.
15063 As for other languages, it will enter Ada mode when stopped in a program that
15064 was translated from an Ada source file.
15066 While in Ada mode, you may use `@t{--}' for comments. This is useful
15067 mostly for documenting command files. The standard @value{GDBN} comment
15068 (@samp{#}) still works at the beginning of a line in Ada mode, but not in the
15069 middle (to allow based literals).
15071 The debugger supports limited overloading. Given a subprogram call in which
15072 the function symbol has multiple definitions, it will use the number of
15073 actual parameters and some information about their types to attempt to narrow
15074 the set of definitions. It also makes very limited use of context, preferring
15075 procedures to functions in the context of the @code{call} command, and
15076 functions to procedures elsewhere.
15078 @node Omissions from Ada
15079 @subsubsection Omissions from Ada
15080 @cindex Ada, omissions from
15082 Here are the notable omissions from the subset:
15086 Only a subset of the attributes are supported:
15090 @t{'First}, @t{'Last}, and @t{'Length}
15091 on array objects (not on types and subtypes).
15094 @t{'Min} and @t{'Max}.
15097 @t{'Pos} and @t{'Val}.
15103 @t{'Range} on array objects (not subtypes), but only as the right
15104 operand of the membership (@code{in}) operator.
15107 @t{'Access}, @t{'Unchecked_Access}, and
15108 @t{'Unrestricted_Access} (a GNAT extension).
15116 @code{Characters.Latin_1} are not available and
15117 concatenation is not implemented. Thus, escape characters in strings are
15118 not currently available.
15121 Equality tests (@samp{=} and @samp{/=}) on arrays test for bitwise
15122 equality of representations. They will generally work correctly
15123 for strings and arrays whose elements have integer or enumeration types.
15124 They may not work correctly for arrays whose element
15125 types have user-defined equality, for arrays of real values
15126 (in particular, IEEE-conformant floating point, because of negative
15127 zeroes and NaNs), and for arrays whose elements contain unused bits with
15128 indeterminate values.
15131 The other component-by-component array operations (@code{and}, @code{or},
15132 @code{xor}, @code{not}, and relational tests other than equality)
15133 are not implemented.
15136 @cindex array aggregates (Ada)
15137 @cindex record aggregates (Ada)
15138 @cindex aggregates (Ada)
15139 There is limited support for array and record aggregates. They are
15140 permitted only on the right sides of assignments, as in these examples:
15143 (@value{GDBP}) set An_Array := (1, 2, 3, 4, 5, 6)
15144 (@value{GDBP}) set An_Array := (1, others => 0)
15145 (@value{GDBP}) set An_Array := (0|4 => 1, 1..3 => 2, 5 => 6)
15146 (@value{GDBP}) set A_2D_Array := ((1, 2, 3), (4, 5, 6), (7, 8, 9))
15147 (@value{GDBP}) set A_Record := (1, "Peter", True);
15148 (@value{GDBP}) set A_Record := (Name => "Peter", Id => 1, Alive => True)
15152 discriminant's value by assigning an aggregate has an
15153 undefined effect if that discriminant is used within the record.
15154 However, you can first modify discriminants by directly assigning to
15155 them (which normally would not be allowed in Ada), and then performing an
15156 aggregate assignment. For example, given a variable @code{A_Rec}
15157 declared to have a type such as:
15160 type Rec (Len : Small_Integer := 0) is record
15162 Vals : IntArray (1 .. Len);
15166 you can assign a value with a different size of @code{Vals} with two
15170 (@value{GDBP}) set A_Rec.Len := 4
15171 (@value{GDBP}) set A_Rec := (Id => 42, Vals => (1, 2, 3, 4))
15174 As this example also illustrates, @value{GDBN} is very loose about the usual
15175 rules concerning aggregates. You may leave out some of the
15176 components of an array or record aggregate (such as the @code{Len}
15177 component in the assignment to @code{A_Rec} above); they will retain their
15178 original values upon assignment. You may freely use dynamic values as
15179 indices in component associations. You may even use overlapping or
15180 redundant component associations, although which component values are
15181 assigned in such cases is not defined.
15184 Calls to dispatching subprograms are not implemented.
15187 The overloading algorithm is much more limited (i.e., less selective)
15188 than that of real Ada. It makes only limited use of the context in
15189 which a subexpression appears to resolve its meaning, and it is much
15190 looser in its rules for allowing type matches. As a result, some
15191 function calls will be ambiguous, and the user will be asked to choose
15192 the proper resolution.
15195 The @code{new} operator is not implemented.
15198 Entry calls are not implemented.
15201 Aside from printing, arithmetic operations on the native VAX floating-point
15202 formats are not supported.
15205 It is not possible to slice a packed array.
15208 The names @code{True} and @code{False}, when not part of a qualified name,
15209 are interpreted as if implicitly prefixed by @code{Standard}, regardless of
15211 Should your program
15212 redefine these names in a package or procedure (at best a dubious practice),
15213 you will have to use fully qualified names to access their new definitions.
15216 @node Additions to Ada
15217 @subsubsection Additions to Ada
15218 @cindex Ada, deviations from
15220 As it does for other languages, @value{GDBN} makes certain generic
15221 extensions to Ada (@pxref{Expressions}):
15225 If the expression @var{E} is a variable residing in memory (typically
15226 a local variable or array element) and @var{N} is a positive integer,
15227 then @code{@var{E}@@@var{N}} displays the values of @var{E} and the
15228 @var{N}-1 adjacent variables following it in memory as an array. In
15229 Ada, this operator is generally not necessary, since its prime use is
15230 in displaying parts of an array, and slicing will usually do this in
15231 Ada. However, there are occasional uses when debugging programs in
15232 which certain debugging information has been optimized away.
15235 @code{@var{B}::@var{var}} means ``the variable named @var{var} that
15236 appears in function or file @var{B}.'' When @var{B} is a file name,
15237 you must typically surround it in single quotes.
15240 The expression @code{@{@var{type}@} @var{addr}} means ``the variable of type
15241 @var{type} that appears at address @var{addr}.''
15244 A name starting with @samp{$} is a convenience variable
15245 (@pxref{Convenience Vars}) or a machine register (@pxref{Registers}).
15248 In addition, @value{GDBN} provides a few other shortcuts and outright
15249 additions specific to Ada:
15253 The assignment statement is allowed as an expression, returning
15254 its right-hand operand as its value. Thus, you may enter
15257 (@value{GDBP}) set x := y + 3
15258 (@value{GDBP}) print A(tmp := y + 1)
15262 The semicolon is allowed as an ``operator,'' returning as its value
15263 the value of its right-hand operand.
15264 This allows, for example,
15265 complex conditional breaks:
15268 (@value{GDBP}) break f
15269 (@value{GDBP}) condition 1 (report(i); k += 1; A(k) > 100)
15273 Rather than use catenation and symbolic character names to introduce special
15274 characters into strings, one may instead use a special bracket notation,
15275 which is also used to print strings. A sequence of characters of the form
15276 @samp{["@var{XX}"]} within a string or character literal denotes the
15277 (single) character whose numeric encoding is @var{XX} in hexadecimal. The
15278 sequence of characters @samp{["""]} also denotes a single quotation mark
15279 in strings. For example,
15281 "One line.["0a"]Next line.["0a"]"
15284 contains an ASCII newline character (@code{Ada.Characters.Latin_1.LF})
15288 The subtype used as a prefix for the attributes @t{'Pos}, @t{'Min}, and
15289 @t{'Max} is optional (and is ignored in any case). For example, it is valid
15293 (@value{GDBP}) print 'max(x, y)
15297 When printing arrays, @value{GDBN} uses positional notation when the
15298 array has a lower bound of 1, and uses a modified named notation otherwise.
15299 For example, a one-dimensional array of three integers with a lower bound
15300 of 3 might print as
15307 That is, in contrast to valid Ada, only the first component has a @code{=>}
15311 You may abbreviate attributes in expressions with any unique,
15312 multi-character subsequence of
15313 their names (an exact match gets preference).
15314 For example, you may use @t{a'len}, @t{a'gth}, or @t{a'lh}
15315 in place of @t{a'length}.
15318 @cindex quoting Ada internal identifiers
15319 Since Ada is case-insensitive, the debugger normally maps identifiers you type
15320 to lower case. The GNAT compiler uses upper-case characters for
15321 some of its internal identifiers, which are normally of no interest to users.
15322 For the rare occasions when you actually have to look at them,
15323 enclose them in angle brackets to avoid the lower-case mapping.
15326 (@value{GDBP}) print <JMPBUF_SAVE>[0]
15330 Printing an object of class-wide type or dereferencing an
15331 access-to-class-wide value will display all the components of the object's
15332 specific type (as indicated by its run-time tag). Likewise, component
15333 selection on such a value will operate on the specific type of the
15338 @node Stopping Before Main Program
15339 @subsubsection Stopping at the Very Beginning
15341 @cindex breakpointing Ada elaboration code
15342 It is sometimes necessary to debug the program during elaboration, and
15343 before reaching the main procedure.
15344 As defined in the Ada Reference
15345 Manual, the elaboration code is invoked from a procedure called
15346 @code{adainit}. To run your program up to the beginning of
15347 elaboration, simply use the following two commands:
15348 @code{tbreak adainit} and @code{run}.
15350 @node Ada Exceptions
15351 @subsubsection Ada Exceptions
15353 A command is provided to list all Ada exceptions:
15356 @kindex info exceptions
15357 @item info exceptions
15358 @itemx info exceptions @var{regexp}
15359 The @code{info exceptions} command allows you to list all Ada exceptions
15360 defined within the program being debugged, as well as their addresses.
15361 With a regular expression, @var{regexp}, as argument, only those exceptions
15362 whose names match @var{regexp} are listed.
15365 Below is a small example, showing how the command can be used, first
15366 without argument, and next with a regular expression passed as an
15370 (@value{GDBP}) info exceptions
15371 All defined Ada exceptions:
15372 constraint_error: 0x613da0
15373 program_error: 0x613d20
15374 storage_error: 0x613ce0
15375 tasking_error: 0x613ca0
15376 const.aint_global_e: 0x613b00
15377 (@value{GDBP}) info exceptions const.aint
15378 All Ada exceptions matching regular expression "const.aint":
15379 constraint_error: 0x613da0
15380 const.aint_global_e: 0x613b00
15383 It is also possible to ask @value{GDBN} to stop your program's execution
15384 when an exception is raised. For more details, see @ref{Set Catchpoints}.
15387 @subsubsection Extensions for Ada Tasks
15388 @cindex Ada, tasking
15390 Support for Ada tasks is analogous to that for threads (@pxref{Threads}).
15391 @value{GDBN} provides the following task-related commands:
15396 This command shows a list of current Ada tasks, as in the following example:
15403 (@value{GDBP}) info tasks
15404 ID TID P-ID Pri State Name
15405 1 8088000 0 15 Child Activation Wait main_task
15406 2 80a4000 1 15 Accept Statement b
15407 3 809a800 1 15 Child Activation Wait a
15408 * 4 80ae800 3 15 Runnable c
15413 In this listing, the asterisk before the last task indicates it to be the
15414 task currently being inspected.
15418 Represents @value{GDBN}'s internal task number.
15424 The parent's task ID (@value{GDBN}'s internal task number).
15427 The base priority of the task.
15430 Current state of the task.
15434 The task has been created but has not been activated. It cannot be
15438 The task is not blocked for any reason known to Ada. (It may be waiting
15439 for a mutex, though.) It is conceptually "executing" in normal mode.
15442 The task is terminated, in the sense of ARM 9.3 (5). Any dependents
15443 that were waiting on terminate alternatives have been awakened and have
15444 terminated themselves.
15446 @item Child Activation Wait
15447 The task is waiting for created tasks to complete activation.
15449 @item Accept Statement
15450 The task is waiting on an accept or selective wait statement.
15452 @item Waiting on entry call
15453 The task is waiting on an entry call.
15455 @item Async Select Wait
15456 The task is waiting to start the abortable part of an asynchronous
15460 The task is waiting on a select statement with only a delay
15463 @item Child Termination Wait
15464 The task is sleeping having completed a master within itself, and is
15465 waiting for the tasks dependent on that master to become terminated or
15466 waiting on a terminate Phase.
15468 @item Wait Child in Term Alt
15469 The task is sleeping waiting for tasks on terminate alternatives to
15470 finish terminating.
15472 @item Accepting RV with @var{taskno}
15473 The task is accepting a rendez-vous with the task @var{taskno}.
15477 Name of the task in the program.
15481 @kindex info task @var{taskno}
15482 @item info task @var{taskno}
15483 This command shows detailled informations on the specified task, as in
15484 the following example:
15489 (@value{GDBP}) info tasks
15490 ID TID P-ID Pri State Name
15491 1 8077880 0 15 Child Activation Wait main_task
15492 * 2 807c468 1 15 Runnable task_1
15493 (@value{GDBP}) info task 2
15494 Ada Task: 0x807c468
15497 Parent: 1 (main_task)
15503 @kindex task@r{ (Ada)}
15504 @cindex current Ada task ID
15505 This command prints the ID of the current task.
15511 (@value{GDBP}) info tasks
15512 ID TID P-ID Pri State Name
15513 1 8077870 0 15 Child Activation Wait main_task
15514 * 2 807c458 1 15 Runnable t
15515 (@value{GDBP}) task
15516 [Current task is 2]
15519 @item task @var{taskno}
15520 @cindex Ada task switching
15521 This command is like the @code{thread @var{threadno}}
15522 command (@pxref{Threads}). It switches the context of debugging
15523 from the current task to the given task.
15529 (@value{GDBP}) info tasks
15530 ID TID P-ID Pri State Name
15531 1 8077870 0 15 Child Activation Wait main_task
15532 * 2 807c458 1 15 Runnable t
15533 (@value{GDBP}) task 1
15534 [Switching to task 1]
15535 #0 0x8067726 in pthread_cond_wait ()
15537 #0 0x8067726 in pthread_cond_wait ()
15538 #1 0x8056714 in system.os_interface.pthread_cond_wait ()
15539 #2 0x805cb63 in system.task_primitives.operations.sleep ()
15540 #3 0x806153e in system.tasking.stages.activate_tasks ()
15541 #4 0x804aacc in un () at un.adb:5
15544 @item break @var{linespec} task @var{taskno}
15545 @itemx break @var{linespec} task @var{taskno} if @dots{}
15546 @cindex breakpoints and tasks, in Ada
15547 @cindex task breakpoints, in Ada
15548 @kindex break @dots{} task @var{taskno}@r{ (Ada)}
15549 These commands are like the @code{break @dots{} thread @dots{}}
15550 command (@pxref{Thread Stops}).
15551 @var{linespec} specifies source lines, as described
15552 in @ref{Specify Location}.
15554 Use the qualifier @samp{task @var{taskno}} with a breakpoint command
15555 to specify that you only want @value{GDBN} to stop the program when a
15556 particular Ada task reaches this breakpoint. @var{taskno} is one of the
15557 numeric task identifiers assigned by @value{GDBN}, shown in the first
15558 column of the @samp{info tasks} display.
15560 If you do not specify @samp{task @var{taskno}} when you set a
15561 breakpoint, the breakpoint applies to @emph{all} tasks of your
15564 You can use the @code{task} qualifier on conditional breakpoints as
15565 well; in this case, place @samp{task @var{taskno}} before the
15566 breakpoint condition (before the @code{if}).
15574 (@value{GDBP}) info tasks
15575 ID TID P-ID Pri State Name
15576 1 140022020 0 15 Child Activation Wait main_task
15577 2 140045060 1 15 Accept/Select Wait t2
15578 3 140044840 1 15 Runnable t1
15579 * 4 140056040 1 15 Runnable t3
15580 (@value{GDBP}) b 15 task 2
15581 Breakpoint 5 at 0x120044cb0: file test_task_debug.adb, line 15.
15582 (@value{GDBP}) cont
15587 Breakpoint 5, test_task_debug () at test_task_debug.adb:15
15589 (@value{GDBP}) info tasks
15590 ID TID P-ID Pri State Name
15591 1 140022020 0 15 Child Activation Wait main_task
15592 * 2 140045060 1 15 Runnable t2
15593 3 140044840 1 15 Runnable t1
15594 4 140056040 1 15 Delay Sleep t3
15598 @node Ada Tasks and Core Files
15599 @subsubsection Tasking Support when Debugging Core Files
15600 @cindex Ada tasking and core file debugging
15602 When inspecting a core file, as opposed to debugging a live program,
15603 tasking support may be limited or even unavailable, depending on
15604 the platform being used.
15605 For instance, on x86-linux, the list of tasks is available, but task
15606 switching is not supported. On Tru64, however, task switching will work
15609 On certain platforms, including Tru64, the debugger needs to perform some
15610 memory writes in order to provide Ada tasking support. When inspecting
15611 a core file, this means that the core file must be opened with read-write
15612 privileges, using the command @samp{"set write on"} (@pxref{Patching}).
15613 Under these circumstances, you should make a backup copy of the core
15614 file before inspecting it with @value{GDBN}.
15616 @node Ravenscar Profile
15617 @subsubsection Tasking Support when using the Ravenscar Profile
15618 @cindex Ravenscar Profile
15620 The @dfn{Ravenscar Profile} is a subset of the Ada tasking features,
15621 specifically designed for systems with safety-critical real-time
15625 @kindex set ravenscar task-switching on
15626 @cindex task switching with program using Ravenscar Profile
15627 @item set ravenscar task-switching on
15628 Allows task switching when debugging a program that uses the Ravenscar
15629 Profile. This is the default.
15631 @kindex set ravenscar task-switching off
15632 @item set ravenscar task-switching off
15633 Turn off task switching when debugging a program that uses the Ravenscar
15634 Profile. This is mostly intended to disable the code that adds support
15635 for the Ravenscar Profile, in case a bug in either @value{GDBN} or in
15636 the Ravenscar runtime is preventing @value{GDBN} from working properly.
15637 To be effective, this command should be run before the program is started.
15639 @kindex show ravenscar task-switching
15640 @item show ravenscar task-switching
15641 Show whether it is possible to switch from task to task in a program
15642 using the Ravenscar Profile.
15647 @subsubsection Known Peculiarities of Ada Mode
15648 @cindex Ada, problems
15650 Besides the omissions listed previously (@pxref{Omissions from Ada}),
15651 we know of several problems with and limitations of Ada mode in
15653 some of which will be fixed with planned future releases of the debugger
15654 and the GNU Ada compiler.
15658 Static constants that the compiler chooses not to materialize as objects in
15659 storage are invisible to the debugger.
15662 Named parameter associations in function argument lists are ignored (the
15663 argument lists are treated as positional).
15666 Many useful library packages are currently invisible to the debugger.
15669 Fixed-point arithmetic, conversions, input, and output is carried out using
15670 floating-point arithmetic, and may give results that only approximate those on
15674 The GNAT compiler never generates the prefix @code{Standard} for any of
15675 the standard symbols defined by the Ada language. @value{GDBN} knows about
15676 this: it will strip the prefix from names when you use it, and will never
15677 look for a name you have so qualified among local symbols, nor match against
15678 symbols in other packages or subprograms. If you have
15679 defined entities anywhere in your program other than parameters and
15680 local variables whose simple names match names in @code{Standard},
15681 GNAT's lack of qualification here can cause confusion. When this happens,
15682 you can usually resolve the confusion
15683 by qualifying the problematic names with package
15684 @code{Standard} explicitly.
15687 Older versions of the compiler sometimes generate erroneous debugging
15688 information, resulting in the debugger incorrectly printing the value
15689 of affected entities. In some cases, the debugger is able to work
15690 around an issue automatically. In other cases, the debugger is able
15691 to work around the issue, but the work-around has to be specifically
15694 @kindex set ada trust-PAD-over-XVS
15695 @kindex show ada trust-PAD-over-XVS
15698 @item set ada trust-PAD-over-XVS on
15699 Configure GDB to strictly follow the GNAT encoding when computing the
15700 value of Ada entities, particularly when @code{PAD} and @code{PAD___XVS}
15701 types are involved (see @code{ada/exp_dbug.ads} in the GCC sources for
15702 a complete description of the encoding used by the GNAT compiler).
15703 This is the default.
15705 @item set ada trust-PAD-over-XVS off
15706 This is related to the encoding using by the GNAT compiler. If @value{GDBN}
15707 sometimes prints the wrong value for certain entities, changing @code{ada
15708 trust-PAD-over-XVS} to @code{off} activates a work-around which may fix
15709 the issue. It is always safe to set @code{ada trust-PAD-over-XVS} to
15710 @code{off}, but this incurs a slight performance penalty, so it is
15711 recommended to leave this setting to @code{on} unless necessary.
15715 @cindex GNAT descriptive types
15716 @cindex GNAT encoding
15717 Internally, the debugger also relies on the compiler following a number
15718 of conventions known as the @samp{GNAT Encoding}, all documented in
15719 @file{gcc/ada/exp_dbug.ads} in the GCC sources. This encoding describes
15720 how the debugging information should be generated for certain types.
15721 In particular, this convention makes use of @dfn{descriptive types},
15722 which are artificial types generated purely to help the debugger.
15724 These encodings were defined at a time when the debugging information
15725 format used was not powerful enough to describe some of the more complex
15726 types available in Ada. Since DWARF allows us to express nearly all
15727 Ada features, the long-term goal is to slowly replace these descriptive
15728 types by their pure DWARF equivalent. To facilitate that transition,
15729 a new maintenance option is available to force the debugger to ignore
15730 those descriptive types. It allows the user to quickly evaluate how
15731 well @value{GDBN} works without them.
15735 @kindex maint ada set ignore-descriptive-types
15736 @item maintenance ada set ignore-descriptive-types [on|off]
15737 Control whether the debugger should ignore descriptive types.
15738 The default is not to ignore descriptives types (@code{off}).
15740 @kindex maint ada show ignore-descriptive-types
15741 @item maintenance ada show ignore-descriptive-types
15742 Show if descriptive types are ignored by @value{GDBN}.
15746 @node Unsupported Languages
15747 @section Unsupported Languages
15749 @cindex unsupported languages
15750 @cindex minimal language
15751 In addition to the other fully-supported programming languages,
15752 @value{GDBN} also provides a pseudo-language, called @code{minimal}.
15753 It does not represent a real programming language, but provides a set
15754 of capabilities close to what the C or assembly languages provide.
15755 This should allow most simple operations to be performed while debugging
15756 an application that uses a language currently not supported by @value{GDBN}.
15758 If the language is set to @code{auto}, @value{GDBN} will automatically
15759 select this language if the current frame corresponds to an unsupported
15763 @chapter Examining the Symbol Table
15765 The commands described in this chapter allow you to inquire about the
15766 symbols (names of variables, functions and types) defined in your
15767 program. This information is inherent in the text of your program and
15768 does not change as your program executes. @value{GDBN} finds it in your
15769 program's symbol table, in the file indicated when you started @value{GDBN}
15770 (@pxref{File Options, ,Choosing Files}), or by one of the
15771 file-management commands (@pxref{Files, ,Commands to Specify Files}).
15773 @cindex symbol names
15774 @cindex names of symbols
15775 @cindex quoting names
15776 Occasionally, you may need to refer to symbols that contain unusual
15777 characters, which @value{GDBN} ordinarily treats as word delimiters. The
15778 most frequent case is in referring to static variables in other
15779 source files (@pxref{Variables,,Program Variables}). File names
15780 are recorded in object files as debugging symbols, but @value{GDBN} would
15781 ordinarily parse a typical file name, like @file{foo.c}, as the three words
15782 @samp{foo} @samp{.} @samp{c}. To allow @value{GDBN} to recognize
15783 @samp{foo.c} as a single symbol, enclose it in single quotes; for example,
15790 looks up the value of @code{x} in the scope of the file @file{foo.c}.
15793 @cindex case-insensitive symbol names
15794 @cindex case sensitivity in symbol names
15795 @kindex set case-sensitive
15796 @item set case-sensitive on
15797 @itemx set case-sensitive off
15798 @itemx set case-sensitive auto
15799 Normally, when @value{GDBN} looks up symbols, it matches their names
15800 with case sensitivity determined by the current source language.
15801 Occasionally, you may wish to control that. The command @code{set
15802 case-sensitive} lets you do that by specifying @code{on} for
15803 case-sensitive matches or @code{off} for case-insensitive ones. If
15804 you specify @code{auto}, case sensitivity is reset to the default
15805 suitable for the source language. The default is case-sensitive
15806 matches for all languages except for Fortran, for which the default is
15807 case-insensitive matches.
15809 @kindex show case-sensitive
15810 @item show case-sensitive
15811 This command shows the current setting of case sensitivity for symbols
15814 @kindex set print type methods
15815 @item set print type methods
15816 @itemx set print type methods on
15817 @itemx set print type methods off
15818 Normally, when @value{GDBN} prints a class, it displays any methods
15819 declared in that class. You can control this behavior either by
15820 passing the appropriate flag to @code{ptype}, or using @command{set
15821 print type methods}. Specifying @code{on} will cause @value{GDBN} to
15822 display the methods; this is the default. Specifying @code{off} will
15823 cause @value{GDBN} to omit the methods.
15825 @kindex show print type methods
15826 @item show print type methods
15827 This command shows the current setting of method display when printing
15830 @kindex set print type typedefs
15831 @item set print type typedefs
15832 @itemx set print type typedefs on
15833 @itemx set print type typedefs off
15835 Normally, when @value{GDBN} prints a class, it displays any typedefs
15836 defined in that class. You can control this behavior either by
15837 passing the appropriate flag to @code{ptype}, or using @command{set
15838 print type typedefs}. Specifying @code{on} will cause @value{GDBN} to
15839 display the typedef definitions; this is the default. Specifying
15840 @code{off} will cause @value{GDBN} to omit the typedef definitions.
15841 Note that this controls whether the typedef definition itself is
15842 printed, not whether typedef names are substituted when printing other
15845 @kindex show print type typedefs
15846 @item show print type typedefs
15847 This command shows the current setting of typedef display when
15850 @kindex info address
15851 @cindex address of a symbol
15852 @item info address @var{symbol}
15853 Describe where the data for @var{symbol} is stored. For a register
15854 variable, this says which register it is kept in. For a non-register
15855 local variable, this prints the stack-frame offset at which the variable
15858 Note the contrast with @samp{print &@var{symbol}}, which does not work
15859 at all for a register variable, and for a stack local variable prints
15860 the exact address of the current instantiation of the variable.
15862 @kindex info symbol
15863 @cindex symbol from address
15864 @cindex closest symbol and offset for an address
15865 @item info symbol @var{addr}
15866 Print the name of a symbol which is stored at the address @var{addr}.
15867 If no symbol is stored exactly at @var{addr}, @value{GDBN} prints the
15868 nearest symbol and an offset from it:
15871 (@value{GDBP}) info symbol 0x54320
15872 _initialize_vx + 396 in section .text
15876 This is the opposite of the @code{info address} command. You can use
15877 it to find out the name of a variable or a function given its address.
15879 For dynamically linked executables, the name of executable or shared
15880 library containing the symbol is also printed:
15883 (@value{GDBP}) info symbol 0x400225
15884 _start + 5 in section .text of /tmp/a.out
15885 (@value{GDBP}) info symbol 0x2aaaac2811cf
15886 __read_nocancel + 6 in section .text of /usr/lib64/libc.so.6
15890 @item whatis[/@var{flags}] [@var{arg}]
15891 Print the data type of @var{arg}, which can be either an expression
15892 or a name of a data type. With no argument, print the data type of
15893 @code{$}, the last value in the value history.
15895 If @var{arg} is an expression (@pxref{Expressions, ,Expressions}), it
15896 is not actually evaluated, and any side-effecting operations (such as
15897 assignments or function calls) inside it do not take place.
15899 If @var{arg} is a variable or an expression, @code{whatis} prints its
15900 literal type as it is used in the source code. If the type was
15901 defined using a @code{typedef}, @code{whatis} will @emph{not} print
15902 the data type underlying the @code{typedef}. If the type of the
15903 variable or the expression is a compound data type, such as
15904 @code{struct} or @code{class}, @code{whatis} never prints their
15905 fields or methods. It just prints the @code{struct}/@code{class}
15906 name (a.k.a.@: its @dfn{tag}). If you want to see the members of
15907 such a compound data type, use @code{ptype}.
15909 If @var{arg} is a type name that was defined using @code{typedef},
15910 @code{whatis} @dfn{unrolls} only one level of that @code{typedef}.
15911 Unrolling means that @code{whatis} will show the underlying type used
15912 in the @code{typedef} declaration of @var{arg}. However, if that
15913 underlying type is also a @code{typedef}, @code{whatis} will not
15916 For C code, the type names may also have the form @samp{class
15917 @var{class-name}}, @samp{struct @var{struct-tag}}, @samp{union
15918 @var{union-tag}} or @samp{enum @var{enum-tag}}.
15920 @var{flags} can be used to modify how the type is displayed.
15921 Available flags are:
15925 Display in ``raw'' form. Normally, @value{GDBN} substitutes template
15926 parameters and typedefs defined in a class when printing the class'
15927 members. The @code{/r} flag disables this.
15930 Do not print methods defined in the class.
15933 Print methods defined in the class. This is the default, but the flag
15934 exists in case you change the default with @command{set print type methods}.
15937 Do not print typedefs defined in the class. Note that this controls
15938 whether the typedef definition itself is printed, not whether typedef
15939 names are substituted when printing other types.
15942 Print typedefs defined in the class. This is the default, but the flag
15943 exists in case you change the default with @command{set print type typedefs}.
15947 @item ptype[/@var{flags}] [@var{arg}]
15948 @code{ptype} accepts the same arguments as @code{whatis}, but prints a
15949 detailed description of the type, instead of just the name of the type.
15950 @xref{Expressions, ,Expressions}.
15952 Contrary to @code{whatis}, @code{ptype} always unrolls any
15953 @code{typedef}s in its argument declaration, whether the argument is
15954 a variable, expression, or a data type. This means that @code{ptype}
15955 of a variable or an expression will not print literally its type as
15956 present in the source code---use @code{whatis} for that. @code{typedef}s at
15957 the pointer or reference targets are also unrolled. Only @code{typedef}s of
15958 fields, methods and inner @code{class typedef}s of @code{struct}s,
15959 @code{class}es and @code{union}s are not unrolled even with @code{ptype}.
15961 For example, for this variable declaration:
15964 typedef double real_t;
15965 struct complex @{ real_t real; double imag; @};
15966 typedef struct complex complex_t;
15968 real_t *real_pointer_var;
15972 the two commands give this output:
15976 (@value{GDBP}) whatis var
15978 (@value{GDBP}) ptype var
15979 type = struct complex @{
15983 (@value{GDBP}) whatis complex_t
15984 type = struct complex
15985 (@value{GDBP}) whatis struct complex
15986 type = struct complex
15987 (@value{GDBP}) ptype struct complex
15988 type = struct complex @{
15992 (@value{GDBP}) whatis real_pointer_var
15994 (@value{GDBP}) ptype real_pointer_var
16000 As with @code{whatis}, using @code{ptype} without an argument refers to
16001 the type of @code{$}, the last value in the value history.
16003 @cindex incomplete type
16004 Sometimes, programs use opaque data types or incomplete specifications
16005 of complex data structure. If the debug information included in the
16006 program does not allow @value{GDBN} to display a full declaration of
16007 the data type, it will say @samp{<incomplete type>}. For example,
16008 given these declarations:
16012 struct foo *fooptr;
16016 but no definition for @code{struct foo} itself, @value{GDBN} will say:
16019 (@value{GDBP}) ptype foo
16020 $1 = <incomplete type>
16024 ``Incomplete type'' is C terminology for data types that are not
16025 completely specified.
16028 @item info types @var{regexp}
16030 Print a brief description of all types whose names match the regular
16031 expression @var{regexp} (or all types in your program, if you supply
16032 no argument). Each complete typename is matched as though it were a
16033 complete line; thus, @samp{i type value} gives information on all
16034 types in your program whose names include the string @code{value}, but
16035 @samp{i type ^value$} gives information only on types whose complete
16036 name is @code{value}.
16038 This command differs from @code{ptype} in two ways: first, like
16039 @code{whatis}, it does not print a detailed description; second, it
16040 lists all source files where a type is defined.
16042 @kindex info type-printers
16043 @item info type-printers
16044 Versions of @value{GDBN} that ship with Python scripting enabled may
16045 have ``type printers'' available. When using @command{ptype} or
16046 @command{whatis}, these printers are consulted when the name of a type
16047 is needed. @xref{Type Printing API}, for more information on writing
16050 @code{info type-printers} displays all the available type printers.
16052 @kindex enable type-printer
16053 @kindex disable type-printer
16054 @item enable type-printer @var{name}@dots{}
16055 @item disable type-printer @var{name}@dots{}
16056 These commands can be used to enable or disable type printers.
16059 @cindex local variables
16060 @item info scope @var{location}
16061 List all the variables local to a particular scope. This command
16062 accepts a @var{location} argument---a function name, a source line, or
16063 an address preceded by a @samp{*}, and prints all the variables local
16064 to the scope defined by that location. (@xref{Specify Location}, for
16065 details about supported forms of @var{location}.) For example:
16068 (@value{GDBP}) @b{info scope command_line_handler}
16069 Scope for command_line_handler:
16070 Symbol rl is an argument at stack/frame offset 8, length 4.
16071 Symbol linebuffer is in static storage at address 0x150a18, length 4.
16072 Symbol linelength is in static storage at address 0x150a1c, length 4.
16073 Symbol p is a local variable in register $esi, length 4.
16074 Symbol p1 is a local variable in register $ebx, length 4.
16075 Symbol nline is a local variable in register $edx, length 4.
16076 Symbol repeat is a local variable at frame offset -8, length 4.
16080 This command is especially useful for determining what data to collect
16081 during a @dfn{trace experiment}, see @ref{Tracepoint Actions,
16084 @kindex info source
16086 Show information about the current source file---that is, the source file for
16087 the function containing the current point of execution:
16090 the name of the source file, and the directory containing it,
16092 the directory it was compiled in,
16094 its length, in lines,
16096 which programming language it is written in,
16098 whether the executable includes debugging information for that file, and
16099 if so, what format the information is in (e.g., STABS, Dwarf 2, etc.), and
16101 whether the debugging information includes information about
16102 preprocessor macros.
16106 @kindex info sources
16108 Print the names of all source files in your program for which there is
16109 debugging information, organized into two lists: files whose symbols
16110 have already been read, and files whose symbols will be read when needed.
16112 @kindex info functions
16113 @item info functions
16114 Print the names and data types of all defined functions.
16116 @item info functions @var{regexp}
16117 Print the names and data types of all defined functions
16118 whose names contain a match for regular expression @var{regexp}.
16119 Thus, @samp{info fun step} finds all functions whose names
16120 include @code{step}; @samp{info fun ^step} finds those whose names
16121 start with @code{step}. If a function name contains characters
16122 that conflict with the regular expression language (e.g.@:
16123 @samp{operator*()}), they may be quoted with a backslash.
16125 @kindex info variables
16126 @item info variables
16127 Print the names and data types of all variables that are defined
16128 outside of functions (i.e.@: excluding local variables).
16130 @item info variables @var{regexp}
16131 Print the names and data types of all variables (except for local
16132 variables) whose names contain a match for regular expression
16135 @kindex info classes
16136 @cindex Objective-C, classes and selectors
16138 @itemx info classes @var{regexp}
16139 Display all Objective-C classes in your program, or
16140 (with the @var{regexp} argument) all those matching a particular regular
16143 @kindex info selectors
16144 @item info selectors
16145 @itemx info selectors @var{regexp}
16146 Display all Objective-C selectors in your program, or
16147 (with the @var{regexp} argument) all those matching a particular regular
16151 This was never implemented.
16152 @kindex info methods
16154 @itemx info methods @var{regexp}
16155 The @code{info methods} command permits the user to examine all defined
16156 methods within C@t{++} program, or (with the @var{regexp} argument) a
16157 specific set of methods found in the various C@t{++} classes. Many
16158 C@t{++} classes provide a large number of methods. Thus, the output
16159 from the @code{ptype} command can be overwhelming and hard to use. The
16160 @code{info-methods} command filters the methods, printing only those
16161 which match the regular-expression @var{regexp}.
16164 @cindex opaque data types
16165 @kindex set opaque-type-resolution
16166 @item set opaque-type-resolution on
16167 Tell @value{GDBN} to resolve opaque types. An opaque type is a type
16168 declared as a pointer to a @code{struct}, @code{class}, or
16169 @code{union}---for example, @code{struct MyType *}---that is used in one
16170 source file although the full declaration of @code{struct MyType} is in
16171 another source file. The default is on.
16173 A change in the setting of this subcommand will not take effect until
16174 the next time symbols for a file are loaded.
16176 @item set opaque-type-resolution off
16177 Tell @value{GDBN} not to resolve opaque types. In this case, the type
16178 is printed as follows:
16180 @{<no data fields>@}
16183 @kindex show opaque-type-resolution
16184 @item show opaque-type-resolution
16185 Show whether opaque types are resolved or not.
16187 @kindex maint print symbols
16188 @cindex symbol dump
16189 @kindex maint print psymbols
16190 @cindex partial symbol dump
16191 @kindex maint print msymbols
16192 @cindex minimal symbol dump
16193 @item maint print symbols @var{filename}
16194 @itemx maint print psymbols @var{filename}
16195 @itemx maint print msymbols @var{filename}
16196 Write a dump of debugging symbol data into the file @var{filename}.
16197 These commands are used to debug the @value{GDBN} symbol-reading code. Only
16198 symbols with debugging data are included. If you use @samp{maint print
16199 symbols}, @value{GDBN} includes all the symbols for which it has already
16200 collected full details: that is, @var{filename} reflects symbols for
16201 only those files whose symbols @value{GDBN} has read. You can use the
16202 command @code{info sources} to find out which files these are. If you
16203 use @samp{maint print psymbols} instead, the dump shows information about
16204 symbols that @value{GDBN} only knows partially---that is, symbols defined in
16205 files that @value{GDBN} has skimmed, but not yet read completely. Finally,
16206 @samp{maint print msymbols} dumps just the minimal symbol information
16207 required for each object file from which @value{GDBN} has read some symbols.
16208 @xref{Files, ,Commands to Specify Files}, for a discussion of how
16209 @value{GDBN} reads symbols (in the description of @code{symbol-file}).
16211 @kindex maint info symtabs
16212 @kindex maint info psymtabs
16213 @cindex listing @value{GDBN}'s internal symbol tables
16214 @cindex symbol tables, listing @value{GDBN}'s internal
16215 @cindex full symbol tables, listing @value{GDBN}'s internal
16216 @cindex partial symbol tables, listing @value{GDBN}'s internal
16217 @item maint info symtabs @r{[} @var{regexp} @r{]}
16218 @itemx maint info psymtabs @r{[} @var{regexp} @r{]}
16220 List the @code{struct symtab} or @code{struct partial_symtab}
16221 structures whose names match @var{regexp}. If @var{regexp} is not
16222 given, list them all. The output includes expressions which you can
16223 copy into a @value{GDBN} debugging this one to examine a particular
16224 structure in more detail. For example:
16227 (@value{GDBP}) maint info psymtabs dwarf2read
16228 @{ objfile /home/gnu/build/gdb/gdb
16229 ((struct objfile *) 0x82e69d0)
16230 @{ psymtab /home/gnu/src/gdb/dwarf2read.c
16231 ((struct partial_symtab *) 0x8474b10)
16234 text addresses 0x814d3c8 -- 0x8158074
16235 globals (* (struct partial_symbol **) 0x8507a08 @@ 9)
16236 statics (* (struct partial_symbol **) 0x40e95b78 @@ 2882)
16237 dependencies (none)
16240 (@value{GDBP}) maint info symtabs
16244 We see that there is one partial symbol table whose filename contains
16245 the string @samp{dwarf2read}, belonging to the @samp{gdb} executable;
16246 and we see that @value{GDBN} has not read in any symtabs yet at all.
16247 If we set a breakpoint on a function, that will cause @value{GDBN} to
16248 read the symtab for the compilation unit containing that function:
16251 (@value{GDBP}) break dwarf2_psymtab_to_symtab
16252 Breakpoint 1 at 0x814e5da: file /home/gnu/src/gdb/dwarf2read.c,
16254 (@value{GDBP}) maint info symtabs
16255 @{ objfile /home/gnu/build/gdb/gdb
16256 ((struct objfile *) 0x82e69d0)
16257 @{ symtab /home/gnu/src/gdb/dwarf2read.c
16258 ((struct symtab *) 0x86c1f38)
16261 blockvector ((struct blockvector *) 0x86c1bd0) (primary)
16262 linetable ((struct linetable *) 0x8370fa0)
16263 debugformat DWARF 2
16272 @chapter Altering Execution
16274 Once you think you have found an error in your program, you might want to
16275 find out for certain whether correcting the apparent error would lead to
16276 correct results in the rest of the run. You can find the answer by
16277 experiment, using the @value{GDBN} features for altering execution of the
16280 For example, you can store new values into variables or memory
16281 locations, give your program a signal, restart it at a different
16282 address, or even return prematurely from a function.
16285 * Assignment:: Assignment to variables
16286 * Jumping:: Continuing at a different address
16287 * Signaling:: Giving your program a signal
16288 * Returning:: Returning from a function
16289 * Calling:: Calling your program's functions
16290 * Patching:: Patching your program
16294 @section Assignment to Variables
16297 @cindex setting variables
16298 To alter the value of a variable, evaluate an assignment expression.
16299 @xref{Expressions, ,Expressions}. For example,
16306 stores the value 4 into the variable @code{x}, and then prints the
16307 value of the assignment expression (which is 4).
16308 @xref{Languages, ,Using @value{GDBN} with Different Languages}, for more
16309 information on operators in supported languages.
16311 @kindex set variable
16312 @cindex variables, setting
16313 If you are not interested in seeing the value of the assignment, use the
16314 @code{set} command instead of the @code{print} command. @code{set} is
16315 really the same as @code{print} except that the expression's value is
16316 not printed and is not put in the value history (@pxref{Value History,
16317 ,Value History}). The expression is evaluated only for its effects.
16319 If the beginning of the argument string of the @code{set} command
16320 appears identical to a @code{set} subcommand, use the @code{set
16321 variable} command instead of just @code{set}. This command is identical
16322 to @code{set} except for its lack of subcommands. For example, if your
16323 program has a variable @code{width}, you get an error if you try to set
16324 a new value with just @samp{set width=13}, because @value{GDBN} has the
16325 command @code{set width}:
16328 (@value{GDBP}) whatis width
16330 (@value{GDBP}) p width
16332 (@value{GDBP}) set width=47
16333 Invalid syntax in expression.
16337 The invalid expression, of course, is @samp{=47}. In
16338 order to actually set the program's variable @code{width}, use
16341 (@value{GDBP}) set var width=47
16344 Because the @code{set} command has many subcommands that can conflict
16345 with the names of program variables, it is a good idea to use the
16346 @code{set variable} command instead of just @code{set}. For example, if
16347 your program has a variable @code{g}, you run into problems if you try
16348 to set a new value with just @samp{set g=4}, because @value{GDBN} has
16349 the command @code{set gnutarget}, abbreviated @code{set g}:
16353 (@value{GDBP}) whatis g
16357 (@value{GDBP}) set g=4
16361 The program being debugged has been started already.
16362 Start it from the beginning? (y or n) y
16363 Starting program: /home/smith/cc_progs/a.out
16364 "/home/smith/cc_progs/a.out": can't open to read symbols:
16365 Invalid bfd target.
16366 (@value{GDBP}) show g
16367 The current BFD target is "=4".
16372 The program variable @code{g} did not change, and you silently set the
16373 @code{gnutarget} to an invalid value. In order to set the variable
16377 (@value{GDBP}) set var g=4
16380 @value{GDBN} allows more implicit conversions in assignments than C; you can
16381 freely store an integer value into a pointer variable or vice versa,
16382 and you can convert any structure to any other structure that is the
16383 same length or shorter.
16384 @comment FIXME: how do structs align/pad in these conversions?
16385 @comment /doc@cygnus.com 18dec1990
16387 To store values into arbitrary places in memory, use the @samp{@{@dots{}@}}
16388 construct to generate a value of specified type at a specified address
16389 (@pxref{Expressions, ,Expressions}). For example, @code{@{int@}0x83040} refers
16390 to memory location @code{0x83040} as an integer (which implies a certain size
16391 and representation in memory), and
16394 set @{int@}0x83040 = 4
16398 stores the value 4 into that memory location.
16401 @section Continuing at a Different Address
16403 Ordinarily, when you continue your program, you do so at the place where
16404 it stopped, with the @code{continue} command. You can instead continue at
16405 an address of your own choosing, with the following commands:
16409 @kindex j @r{(@code{jump})}
16410 @item jump @var{linespec}
16411 @itemx j @var{linespec}
16412 @itemx jump @var{location}
16413 @itemx j @var{location}
16414 Resume execution at line @var{linespec} or at address given by
16415 @var{location}. Execution stops again immediately if there is a
16416 breakpoint there. @xref{Specify Location}, for a description of the
16417 different forms of @var{linespec} and @var{location}. It is common
16418 practice to use the @code{tbreak} command in conjunction with
16419 @code{jump}. @xref{Set Breaks, ,Setting Breakpoints}.
16421 The @code{jump} command does not change the current stack frame, or
16422 the stack pointer, or the contents of any memory location or any
16423 register other than the program counter. If line @var{linespec} is in
16424 a different function from the one currently executing, the results may
16425 be bizarre if the two functions expect different patterns of arguments or
16426 of local variables. For this reason, the @code{jump} command requests
16427 confirmation if the specified line is not in the function currently
16428 executing. However, even bizarre results are predictable if you are
16429 well acquainted with the machine-language code of your program.
16432 @c Doesn't work on HP-UX; have to set $pcoqh and $pcoqt.
16433 On many systems, you can get much the same effect as the @code{jump}
16434 command by storing a new value into the register @code{$pc}. The
16435 difference is that this does not start your program running; it only
16436 changes the address of where it @emph{will} run when you continue. For
16444 makes the next @code{continue} command or stepping command execute at
16445 address @code{0x485}, rather than at the address where your program stopped.
16446 @xref{Continuing and Stepping, ,Continuing and Stepping}.
16448 The most common occasion to use the @code{jump} command is to back
16449 up---perhaps with more breakpoints set---over a portion of a program
16450 that has already executed, in order to examine its execution in more
16455 @section Giving your Program a Signal
16456 @cindex deliver a signal to a program
16460 @item signal @var{signal}
16461 Resume execution where your program stopped, but immediately give it the
16462 signal @var{signal}. @var{signal} can be the name or the number of a
16463 signal. For example, on many systems @code{signal 2} and @code{signal
16464 SIGINT} are both ways of sending an interrupt signal.
16466 Alternatively, if @var{signal} is zero, continue execution without
16467 giving a signal. This is useful when your program stopped on account of
16468 a signal and would ordinarily see the signal when resumed with the
16469 @code{continue} command; @samp{signal 0} causes it to resume without a
16472 @code{signal} does not repeat when you press @key{RET} a second time
16473 after executing the command.
16477 Invoking the @code{signal} command is not the same as invoking the
16478 @code{kill} utility from the shell. Sending a signal with @code{kill}
16479 causes @value{GDBN} to decide what to do with the signal depending on
16480 the signal handling tables (@pxref{Signals}). The @code{signal} command
16481 passes the signal directly to your program.
16485 @section Returning from a Function
16488 @cindex returning from a function
16491 @itemx return @var{expression}
16492 You can cancel execution of a function call with the @code{return}
16493 command. If you give an
16494 @var{expression} argument, its value is used as the function's return
16498 When you use @code{return}, @value{GDBN} discards the selected stack frame
16499 (and all frames within it). You can think of this as making the
16500 discarded frame return prematurely. If you wish to specify a value to
16501 be returned, give that value as the argument to @code{return}.
16503 This pops the selected stack frame (@pxref{Selection, ,Selecting a
16504 Frame}), and any other frames inside of it, leaving its caller as the
16505 innermost remaining frame. That frame becomes selected. The
16506 specified value is stored in the registers used for returning values
16509 The @code{return} command does not resume execution; it leaves the
16510 program stopped in the state that would exist if the function had just
16511 returned. In contrast, the @code{finish} command (@pxref{Continuing
16512 and Stepping, ,Continuing and Stepping}) resumes execution until the
16513 selected stack frame returns naturally.
16515 @value{GDBN} needs to know how the @var{expression} argument should be set for
16516 the inferior. The concrete registers assignment depends on the OS ABI and the
16517 type being returned by the selected stack frame. For example it is common for
16518 OS ABI to return floating point values in FPU registers while integer values in
16519 CPU registers. Still some ABIs return even floating point values in CPU
16520 registers. Larger integer widths (such as @code{long long int}) also have
16521 specific placement rules. @value{GDBN} already knows the OS ABI from its
16522 current target so it needs to find out also the type being returned to make the
16523 assignment into the right register(s).
16525 Normally, the selected stack frame has debug info. @value{GDBN} will always
16526 use the debug info instead of the implicit type of @var{expression} when the
16527 debug info is available. For example, if you type @kbd{return -1}, and the
16528 function in the current stack frame is declared to return a @code{long long
16529 int}, @value{GDBN} transparently converts the implicit @code{int} value of -1
16530 into a @code{long long int}:
16533 Breakpoint 1, func () at gdb.base/return-nodebug.c:29
16535 (@value{GDBP}) return -1
16536 Make func return now? (y or n) y
16537 #0 0x004004f6 in main () at gdb.base/return-nodebug.c:43
16538 43 printf ("result=%lld\n", func ());
16542 However, if the selected stack frame does not have a debug info, e.g., if the
16543 function was compiled without debug info, @value{GDBN} has to find out the type
16544 to return from user. Specifying a different type by mistake may set the value
16545 in different inferior registers than the caller code expects. For example,
16546 typing @kbd{return -1} with its implicit type @code{int} would set only a part
16547 of a @code{long long int} result for a debug info less function (on 32-bit
16548 architectures). Therefore the user is required to specify the return type by
16549 an appropriate cast explicitly:
16552 Breakpoint 2, 0x0040050b in func ()
16553 (@value{GDBP}) return -1
16554 Return value type not available for selected stack frame.
16555 Please use an explicit cast of the value to return.
16556 (@value{GDBP}) return (long long int) -1
16557 Make selected stack frame return now? (y or n) y
16558 #0 0x00400526 in main ()
16563 @section Calling Program Functions
16566 @cindex calling functions
16567 @cindex inferior functions, calling
16568 @item print @var{expr}
16569 Evaluate the expression @var{expr} and display the resulting value.
16570 @var{expr} may include calls to functions in the program being
16574 @item call @var{expr}
16575 Evaluate the expression @var{expr} without displaying @code{void}
16578 You can use this variant of the @code{print} command if you want to
16579 execute a function from your program that does not return anything
16580 (a.k.a.@: @dfn{a void function}), but without cluttering the output
16581 with @code{void} returned values that @value{GDBN} will otherwise
16582 print. If the result is not void, it is printed and saved in the
16586 It is possible for the function you call via the @code{print} or
16587 @code{call} command to generate a signal (e.g., if there's a bug in
16588 the function, or if you passed it incorrect arguments). What happens
16589 in that case is controlled by the @code{set unwindonsignal} command.
16591 Similarly, with a C@t{++} program it is possible for the function you
16592 call via the @code{print} or @code{call} command to generate an
16593 exception that is not handled due to the constraints of the dummy
16594 frame. In this case, any exception that is raised in the frame, but has
16595 an out-of-frame exception handler will not be found. GDB builds a
16596 dummy-frame for the inferior function call, and the unwinder cannot
16597 seek for exception handlers outside of this dummy-frame. What happens
16598 in that case is controlled by the
16599 @code{set unwind-on-terminating-exception} command.
16602 @item set unwindonsignal
16603 @kindex set unwindonsignal
16604 @cindex unwind stack in called functions
16605 @cindex call dummy stack unwinding
16606 Set unwinding of the stack if a signal is received while in a function
16607 that @value{GDBN} called in the program being debugged. If set to on,
16608 @value{GDBN} unwinds the stack it created for the call and restores
16609 the context to what it was before the call. If set to off (the
16610 default), @value{GDBN} stops in the frame where the signal was
16613 @item show unwindonsignal
16614 @kindex show unwindonsignal
16615 Show the current setting of stack unwinding in the functions called by
16618 @item set unwind-on-terminating-exception
16619 @kindex set unwind-on-terminating-exception
16620 @cindex unwind stack in called functions with unhandled exceptions
16621 @cindex call dummy stack unwinding on unhandled exception.
16622 Set unwinding of the stack if a C@t{++} exception is raised, but left
16623 unhandled while in a function that @value{GDBN} called in the program being
16624 debugged. If set to on (the default), @value{GDBN} unwinds the stack
16625 it created for the call and restores the context to what it was before
16626 the call. If set to off, @value{GDBN} the exception is delivered to
16627 the default C@t{++} exception handler and the inferior terminated.
16629 @item show unwind-on-terminating-exception
16630 @kindex show unwind-on-terminating-exception
16631 Show the current setting of stack unwinding in the functions called by
16636 @cindex weak alias functions
16637 Sometimes, a function you wish to call is actually a @dfn{weak alias}
16638 for another function. In such case, @value{GDBN} might not pick up
16639 the type information, including the types of the function arguments,
16640 which causes @value{GDBN} to call the inferior function incorrectly.
16641 As a result, the called function will function erroneously and may
16642 even crash. A solution to that is to use the name of the aliased
16646 @section Patching Programs
16648 @cindex patching binaries
16649 @cindex writing into executables
16650 @cindex writing into corefiles
16652 By default, @value{GDBN} opens the file containing your program's
16653 executable code (or the corefile) read-only. This prevents accidental
16654 alterations to machine code; but it also prevents you from intentionally
16655 patching your program's binary.
16657 If you'd like to be able to patch the binary, you can specify that
16658 explicitly with the @code{set write} command. For example, you might
16659 want to turn on internal debugging flags, or even to make emergency
16665 @itemx set write off
16666 If you specify @samp{set write on}, @value{GDBN} opens executable and
16667 core files for both reading and writing; if you specify @kbd{set write
16668 off} (the default), @value{GDBN} opens them read-only.
16670 If you have already loaded a file, you must load it again (using the
16671 @code{exec-file} or @code{core-file} command) after changing @code{set
16672 write}, for your new setting to take effect.
16676 Display whether executable files and core files are opened for writing
16677 as well as reading.
16681 @chapter @value{GDBN} Files
16683 @value{GDBN} needs to know the file name of the program to be debugged,
16684 both in order to read its symbol table and in order to start your
16685 program. To debug a core dump of a previous run, you must also tell
16686 @value{GDBN} the name of the core dump file.
16689 * Files:: Commands to specify files
16690 * Separate Debug Files:: Debugging information in separate files
16691 * MiniDebugInfo:: Debugging information in a special section
16692 * Index Files:: Index files speed up GDB
16693 * Symbol Errors:: Errors reading symbol files
16694 * Data Files:: GDB data files
16698 @section Commands to Specify Files
16700 @cindex symbol table
16701 @cindex core dump file
16703 You may want to specify executable and core dump file names. The usual
16704 way to do this is at start-up time, using the arguments to
16705 @value{GDBN}'s start-up commands (@pxref{Invocation, , Getting In and
16706 Out of @value{GDBN}}).
16708 Occasionally it is necessary to change to a different file during a
16709 @value{GDBN} session. Or you may run @value{GDBN} and forget to
16710 specify a file you want to use. Or you are debugging a remote target
16711 via @code{gdbserver} (@pxref{Server, file, Using the @code{gdbserver}
16712 Program}). In these situations the @value{GDBN} commands to specify
16713 new files are useful.
16716 @cindex executable file
16718 @item file @var{filename}
16719 Use @var{filename} as the program to be debugged. It is read for its
16720 symbols and for the contents of pure memory. It is also the program
16721 executed when you use the @code{run} command. If you do not specify a
16722 directory and the file is not found in the @value{GDBN} working directory,
16723 @value{GDBN} uses the environment variable @code{PATH} as a list of
16724 directories to search, just as the shell does when looking for a program
16725 to run. You can change the value of this variable, for both @value{GDBN}
16726 and your program, using the @code{path} command.
16728 @cindex unlinked object files
16729 @cindex patching object files
16730 You can load unlinked object @file{.o} files into @value{GDBN} using
16731 the @code{file} command. You will not be able to ``run'' an object
16732 file, but you can disassemble functions and inspect variables. Also,
16733 if the underlying BFD functionality supports it, you could use
16734 @kbd{gdb -write} to patch object files using this technique. Note
16735 that @value{GDBN} can neither interpret nor modify relocations in this
16736 case, so branches and some initialized variables will appear to go to
16737 the wrong place. But this feature is still handy from time to time.
16740 @code{file} with no argument makes @value{GDBN} discard any information it
16741 has on both executable file and the symbol table.
16744 @item exec-file @r{[} @var{filename} @r{]}
16745 Specify that the program to be run (but not the symbol table) is found
16746 in @var{filename}. @value{GDBN} searches the environment variable @code{PATH}
16747 if necessary to locate your program. Omitting @var{filename} means to
16748 discard information on the executable file.
16750 @kindex symbol-file
16751 @item symbol-file @r{[} @var{filename} @r{]}
16752 Read symbol table information from file @var{filename}. @code{PATH} is
16753 searched when necessary. Use the @code{file} command to get both symbol
16754 table and program to run from the same file.
16756 @code{symbol-file} with no argument clears out @value{GDBN} information on your
16757 program's symbol table.
16759 The @code{symbol-file} command causes @value{GDBN} to forget the contents of
16760 some breakpoints and auto-display expressions. This is because they may
16761 contain pointers to the internal data recording symbols and data types,
16762 which are part of the old symbol table data being discarded inside
16765 @code{symbol-file} does not repeat if you press @key{RET} again after
16768 When @value{GDBN} is configured for a particular environment, it
16769 understands debugging information in whatever format is the standard
16770 generated for that environment; you may use either a @sc{gnu} compiler, or
16771 other compilers that adhere to the local conventions.
16772 Best results are usually obtained from @sc{gnu} compilers; for example,
16773 using @code{@value{NGCC}} you can generate debugging information for
16776 For most kinds of object files, with the exception of old SVR3 systems
16777 using COFF, the @code{symbol-file} command does not normally read the
16778 symbol table in full right away. Instead, it scans the symbol table
16779 quickly to find which source files and which symbols are present. The
16780 details are read later, one source file at a time, as they are needed.
16782 The purpose of this two-stage reading strategy is to make @value{GDBN}
16783 start up faster. For the most part, it is invisible except for
16784 occasional pauses while the symbol table details for a particular source
16785 file are being read. (The @code{set verbose} command can turn these
16786 pauses into messages if desired. @xref{Messages/Warnings, ,Optional
16787 Warnings and Messages}.)
16789 We have not implemented the two-stage strategy for COFF yet. When the
16790 symbol table is stored in COFF format, @code{symbol-file} reads the
16791 symbol table data in full right away. Note that ``stabs-in-COFF''
16792 still does the two-stage strategy, since the debug info is actually
16796 @cindex reading symbols immediately
16797 @cindex symbols, reading immediately
16798 @item symbol-file @r{[} -readnow @r{]} @var{filename}
16799 @itemx file @r{[} -readnow @r{]} @var{filename}
16800 You can override the @value{GDBN} two-stage strategy for reading symbol
16801 tables by using the @samp{-readnow} option with any of the commands that
16802 load symbol table information, if you want to be sure @value{GDBN} has the
16803 entire symbol table available.
16805 @c FIXME: for now no mention of directories, since this seems to be in
16806 @c flux. 13mar1992 status is that in theory GDB would look either in
16807 @c current dir or in same dir as myprog; but issues like competing
16808 @c GDB's, or clutter in system dirs, mean that in practice right now
16809 @c only current dir is used. FFish says maybe a special GDB hierarchy
16810 @c (eg rooted in val of env var GDBSYMS) could exist for mappable symbol
16814 @item core-file @r{[}@var{filename}@r{]}
16816 Specify the whereabouts of a core dump file to be used as the ``contents
16817 of memory''. Traditionally, core files contain only some parts of the
16818 address space of the process that generated them; @value{GDBN} can access the
16819 executable file itself for other parts.
16821 @code{core-file} with no argument specifies that no core file is
16824 Note that the core file is ignored when your program is actually running
16825 under @value{GDBN}. So, if you have been running your program and you
16826 wish to debug a core file instead, you must kill the subprocess in which
16827 the program is running. To do this, use the @code{kill} command
16828 (@pxref{Kill Process, ,Killing the Child Process}).
16830 @kindex add-symbol-file
16831 @cindex dynamic linking
16832 @item add-symbol-file @var{filename} @var{address}
16833 @itemx add-symbol-file @var{filename} @var{address} @r{[} -readnow @r{]}
16834 @itemx add-symbol-file @var{filename} @var{address} -s @var{section} @var{address} @dots{}
16835 The @code{add-symbol-file} command reads additional symbol table
16836 information from the file @var{filename}. You would use this command
16837 when @var{filename} has been dynamically loaded (by some other means)
16838 into the program that is running. @var{address} should be the memory
16839 address at which the file has been loaded; @value{GDBN} cannot figure
16840 this out for itself. You can additionally specify an arbitrary number
16841 of @samp{-s @var{section} @var{address}} pairs, to give an explicit
16842 section name and base address for that section. You can specify any
16843 @var{address} as an expression.
16845 The symbol table of the file @var{filename} is added to the symbol table
16846 originally read with the @code{symbol-file} command. You can use the
16847 @code{add-symbol-file} command any number of times; the new symbol data
16848 thus read is kept in addition to the old.
16850 Changes can be reverted using the command @code{remove-symbol-file}.
16852 @cindex relocatable object files, reading symbols from
16853 @cindex object files, relocatable, reading symbols from
16854 @cindex reading symbols from relocatable object files
16855 @cindex symbols, reading from relocatable object files
16856 @cindex @file{.o} files, reading symbols from
16857 Although @var{filename} is typically a shared library file, an
16858 executable file, or some other object file which has been fully
16859 relocated for loading into a process, you can also load symbolic
16860 information from relocatable @file{.o} files, as long as:
16864 the file's symbolic information refers only to linker symbols defined in
16865 that file, not to symbols defined by other object files,
16867 every section the file's symbolic information refers to has actually
16868 been loaded into the inferior, as it appears in the file, and
16870 you can determine the address at which every section was loaded, and
16871 provide these to the @code{add-symbol-file} command.
16875 Some embedded operating systems, like Sun Chorus and VxWorks, can load
16876 relocatable files into an already running program; such systems
16877 typically make the requirements above easy to meet. However, it's
16878 important to recognize that many native systems use complex link
16879 procedures (@code{.linkonce} section factoring and C@t{++} constructor table
16880 assembly, for example) that make the requirements difficult to meet. In
16881 general, one cannot assume that using @code{add-symbol-file} to read a
16882 relocatable object file's symbolic information will have the same effect
16883 as linking the relocatable object file into the program in the normal
16886 @code{add-symbol-file} does not repeat if you press @key{RET} after using it.
16888 @kindex remove-symbol-file
16889 @item remove-symbol-file @var{filename}
16890 @item remove-symbol-file -a @var{address}
16891 Remove a symbol file added via the @code{add-symbol-file} command. The
16892 file to remove can be identified by its @var{filename} or by an @var{address}
16893 that lies within the boundaries of this symbol file in memory. Example:
16896 (gdb) add-symbol-file /home/user/gdb/mylib.so 0x7ffff7ff9480
16897 add symbol table from file "/home/user/gdb/mylib.so" at
16898 .text_addr = 0x7ffff7ff9480
16900 Reading symbols from /home/user/gdb/mylib.so...done.
16901 (gdb) remove-symbol-file -a 0x7ffff7ff9480
16902 Remove symbol table from file "/home/user/gdb/mylib.so"? (y or n) y
16907 @code{remove-symbol-file} does not repeat if you press @key{RET} after using it.
16909 @kindex add-symbol-file-from-memory
16910 @cindex @code{syscall DSO}
16911 @cindex load symbols from memory
16912 @item add-symbol-file-from-memory @var{address}
16913 Load symbols from the given @var{address} in a dynamically loaded
16914 object file whose image is mapped directly into the inferior's memory.
16915 For example, the Linux kernel maps a @code{syscall DSO} into each
16916 process's address space; this DSO provides kernel-specific code for
16917 some system calls. The argument can be any expression whose
16918 evaluation yields the address of the file's shared object file header.
16919 For this command to work, you must have used @code{symbol-file} or
16920 @code{exec-file} commands in advance.
16922 @kindex add-shared-symbol-files
16924 @item add-shared-symbol-files @var{library-file}
16925 @itemx assf @var{library-file}
16926 This command is deprecated and will be removed in future versions
16927 of @value{GDBN}. Use the @code{sharedlibrary} command instead.
16929 The @code{add-shared-symbol-files} command can currently be used only
16930 in the Cygwin build of @value{GDBN} on MS-Windows OS, where it is an
16931 alias for the @code{dll-symbols} command (@pxref{Cygwin Native}).
16932 @value{GDBN} automatically looks for shared libraries, however if
16933 @value{GDBN} does not find yours, you can invoke
16934 @code{add-shared-symbol-files}. It takes one argument: the shared
16935 library's file name. @code{assf} is a shorthand alias for
16936 @code{add-shared-symbol-files}.
16939 @item section @var{section} @var{addr}
16940 The @code{section} command changes the base address of the named
16941 @var{section} of the exec file to @var{addr}. This can be used if the
16942 exec file does not contain section addresses, (such as in the
16943 @code{a.out} format), or when the addresses specified in the file
16944 itself are wrong. Each section must be changed separately. The
16945 @code{info files} command, described below, lists all the sections and
16949 @kindex info target
16952 @code{info files} and @code{info target} are synonymous; both print the
16953 current target (@pxref{Targets, ,Specifying a Debugging Target}),
16954 including the names of the executable and core dump files currently in
16955 use by @value{GDBN}, and the files from which symbols were loaded. The
16956 command @code{help target} lists all possible targets rather than
16959 @kindex maint info sections
16960 @item maint info sections
16961 Another command that can give you extra information about program sections
16962 is @code{maint info sections}. In addition to the section information
16963 displayed by @code{info files}, this command displays the flags and file
16964 offset of each section in the executable and core dump files. In addition,
16965 @code{maint info sections} provides the following command options (which
16966 may be arbitrarily combined):
16970 Display sections for all loaded object files, including shared libraries.
16971 @item @var{sections}
16972 Display info only for named @var{sections}.
16973 @item @var{section-flags}
16974 Display info only for sections for which @var{section-flags} are true.
16975 The section flags that @value{GDBN} currently knows about are:
16978 Section will have space allocated in the process when loaded.
16979 Set for all sections except those containing debug information.
16981 Section will be loaded from the file into the child process memory.
16982 Set for pre-initialized code and data, clear for @code{.bss} sections.
16984 Section needs to be relocated before loading.
16986 Section cannot be modified by the child process.
16988 Section contains executable code only.
16990 Section contains data only (no executable code).
16992 Section will reside in ROM.
16994 Section contains data for constructor/destructor lists.
16996 Section is not empty.
16998 An instruction to the linker to not output the section.
16999 @item COFF_SHARED_LIBRARY
17000 A notification to the linker that the section contains
17001 COFF shared library information.
17003 Section contains common symbols.
17006 @kindex set trust-readonly-sections
17007 @cindex read-only sections
17008 @item set trust-readonly-sections on
17009 Tell @value{GDBN} that readonly sections in your object file
17010 really are read-only (i.e.@: that their contents will not change).
17011 In that case, @value{GDBN} can fetch values from these sections
17012 out of the object file, rather than from the target program.
17013 For some targets (notably embedded ones), this can be a significant
17014 enhancement to debugging performance.
17016 The default is off.
17018 @item set trust-readonly-sections off
17019 Tell @value{GDBN} not to trust readonly sections. This means that
17020 the contents of the section might change while the program is running,
17021 and must therefore be fetched from the target when needed.
17023 @item show trust-readonly-sections
17024 Show the current setting of trusting readonly sections.
17027 All file-specifying commands allow both absolute and relative file names
17028 as arguments. @value{GDBN} always converts the file name to an absolute file
17029 name and remembers it that way.
17031 @cindex shared libraries
17032 @anchor{Shared Libraries}
17033 @value{GDBN} supports @sc{gnu}/Linux, MS-Windows, HP-UX, SunOS, SVr4, Irix,
17034 and IBM RS/6000 AIX shared libraries.
17036 On MS-Windows @value{GDBN} must be linked with the Expat library to support
17037 shared libraries. @xref{Expat}.
17039 @value{GDBN} automatically loads symbol definitions from shared libraries
17040 when you use the @code{run} command, or when you examine a core file.
17041 (Before you issue the @code{run} command, @value{GDBN} does not understand
17042 references to a function in a shared library, however---unless you are
17043 debugging a core file).
17045 On HP-UX, if the program loads a library explicitly, @value{GDBN}
17046 automatically loads the symbols at the time of the @code{shl_load} call.
17048 @c FIXME: some @value{GDBN} release may permit some refs to undef
17049 @c FIXME...symbols---eg in a break cmd---assuming they are from a shared
17050 @c FIXME...lib; check this from time to time when updating manual
17052 There are times, however, when you may wish to not automatically load
17053 symbol definitions from shared libraries, such as when they are
17054 particularly large or there are many of them.
17056 To control the automatic loading of shared library symbols, use the
17060 @kindex set auto-solib-add
17061 @item set auto-solib-add @var{mode}
17062 If @var{mode} is @code{on}, symbols from all shared object libraries
17063 will be loaded automatically when the inferior begins execution, you
17064 attach to an independently started inferior, or when the dynamic linker
17065 informs @value{GDBN} that a new library has been loaded. If @var{mode}
17066 is @code{off}, symbols must be loaded manually, using the
17067 @code{sharedlibrary} command. The default value is @code{on}.
17069 @cindex memory used for symbol tables
17070 If your program uses lots of shared libraries with debug info that
17071 takes large amounts of memory, you can decrease the @value{GDBN}
17072 memory footprint by preventing it from automatically loading the
17073 symbols from shared libraries. To that end, type @kbd{set
17074 auto-solib-add off} before running the inferior, then load each
17075 library whose debug symbols you do need with @kbd{sharedlibrary
17076 @var{regexp}}, where @var{regexp} is a regular expression that matches
17077 the libraries whose symbols you want to be loaded.
17079 @kindex show auto-solib-add
17080 @item show auto-solib-add
17081 Display the current autoloading mode.
17084 @cindex load shared library
17085 To explicitly load shared library symbols, use the @code{sharedlibrary}
17089 @kindex info sharedlibrary
17091 @item info share @var{regex}
17092 @itemx info sharedlibrary @var{regex}
17093 Print the names of the shared libraries which are currently loaded
17094 that match @var{regex}. If @var{regex} is omitted then print
17095 all shared libraries that are loaded.
17097 @kindex sharedlibrary
17099 @item sharedlibrary @var{regex}
17100 @itemx share @var{regex}
17101 Load shared object library symbols for files matching a
17102 Unix regular expression.
17103 As with files loaded automatically, it only loads shared libraries
17104 required by your program for a core file or after typing @code{run}. If
17105 @var{regex} is omitted all shared libraries required by your program are
17108 @item nosharedlibrary
17109 @kindex nosharedlibrary
17110 @cindex unload symbols from shared libraries
17111 Unload all shared object library symbols. This discards all symbols
17112 that have been loaded from all shared libraries. Symbols from shared
17113 libraries that were loaded by explicit user requests are not
17117 Sometimes you may wish that @value{GDBN} stops and gives you control
17118 when any of shared library events happen. The best way to do this is
17119 to use @code{catch load} and @code{catch unload} (@pxref{Set
17122 @value{GDBN} also supports the the @code{set stop-on-solib-events}
17123 command for this. This command exists for historical reasons. It is
17124 less useful than setting a catchpoint, because it does not allow for
17125 conditions or commands as a catchpoint does.
17128 @item set stop-on-solib-events
17129 @kindex set stop-on-solib-events
17130 This command controls whether @value{GDBN} should give you control
17131 when the dynamic linker notifies it about some shared library event.
17132 The most common event of interest is loading or unloading of a new
17135 @item show stop-on-solib-events
17136 @kindex show stop-on-solib-events
17137 Show whether @value{GDBN} stops and gives you control when shared
17138 library events happen.
17141 Shared libraries are also supported in many cross or remote debugging
17142 configurations. @value{GDBN} needs to have access to the target's libraries;
17143 this can be accomplished either by providing copies of the libraries
17144 on the host system, or by asking @value{GDBN} to automatically retrieve the
17145 libraries from the target. If copies of the target libraries are
17146 provided, they need to be the same as the target libraries, although the
17147 copies on the target can be stripped as long as the copies on the host are
17150 @cindex where to look for shared libraries
17151 For remote debugging, you need to tell @value{GDBN} where the target
17152 libraries are, so that it can load the correct copies---otherwise, it
17153 may try to load the host's libraries. @value{GDBN} has two variables
17154 to specify the search directories for target libraries.
17157 @cindex prefix for shared library file names
17158 @cindex system root, alternate
17159 @kindex set solib-absolute-prefix
17160 @kindex set sysroot
17161 @item set sysroot @var{path}
17162 Use @var{path} as the system root for the program being debugged. Any
17163 absolute shared library paths will be prefixed with @var{path}; many
17164 runtime loaders store the absolute paths to the shared library in the
17165 target program's memory. If you use @code{set sysroot} to find shared
17166 libraries, they need to be laid out in the same way that they are on
17167 the target, with e.g.@: a @file{/lib} and @file{/usr/lib} hierarchy
17170 If @var{path} starts with the sequence @file{remote:}, @value{GDBN} will
17171 retrieve the target libraries from the remote system. This is only
17172 supported when using a remote target that supports the @code{remote get}
17173 command (@pxref{File Transfer,,Sending files to a remote system}).
17174 The part of @var{path} following the initial @file{remote:}
17175 (if present) is used as system root prefix on the remote file system.
17176 @footnote{If you want to specify a local system root using a directory
17177 that happens to be named @file{remote:}, you need to use some equivalent
17178 variant of the name like @file{./remote:}.}
17180 For targets with an MS-DOS based filesystem, such as MS-Windows and
17181 SymbianOS, @value{GDBN} tries prefixing a few variants of the target
17182 absolute file name with @var{path}. But first, on Unix hosts,
17183 @value{GDBN} converts all backslash directory separators into forward
17184 slashes, because the backslash is not a directory separator on Unix:
17187 c:\foo\bar.dll @result{} c:/foo/bar.dll
17190 Then, @value{GDBN} attempts prefixing the target file name with
17191 @var{path}, and looks for the resulting file name in the host file
17195 c:/foo/bar.dll @result{} /path/to/sysroot/c:/foo/bar.dll
17198 If that does not find the shared library, @value{GDBN} tries removing
17199 the @samp{:} character from the drive spec, both for convenience, and,
17200 for the case of the host file system not supporting file names with
17204 c:/foo/bar.dll @result{} /path/to/sysroot/c/foo/bar.dll
17207 This makes it possible to have a system root that mirrors a target
17208 with more than one drive. E.g., you may want to setup your local
17209 copies of the target system shared libraries like so (note @samp{c} vs
17213 @file{/path/to/sysroot/c/sys/bin/foo.dll}
17214 @file{/path/to/sysroot/c/sys/bin/bar.dll}
17215 @file{/path/to/sysroot/z/sys/bin/bar.dll}
17219 and point the system root at @file{/path/to/sysroot}, so that
17220 @value{GDBN} can find the correct copies of both
17221 @file{c:\sys\bin\foo.dll}, and @file{z:\sys\bin\bar.dll}.
17223 If that still does not find the shared library, @value{GDBN} tries
17224 removing the whole drive spec from the target file name:
17227 c:/foo/bar.dll @result{} /path/to/sysroot/foo/bar.dll
17230 This last lookup makes it possible to not care about the drive name,
17231 if you don't want or need to.
17233 The @code{set solib-absolute-prefix} command is an alias for @code{set
17236 @cindex default system root
17237 @cindex @samp{--with-sysroot}
17238 You can set the default system root by using the configure-time
17239 @samp{--with-sysroot} option. If the system root is inside
17240 @value{GDBN}'s configured binary prefix (set with @samp{--prefix} or
17241 @samp{--exec-prefix}), then the default system root will be updated
17242 automatically if the installed @value{GDBN} is moved to a new
17245 @kindex show sysroot
17247 Display the current shared library prefix.
17249 @kindex set solib-search-path
17250 @item set solib-search-path @var{path}
17251 If this variable is set, @var{path} is a colon-separated list of
17252 directories to search for shared libraries. @samp{solib-search-path}
17253 is used after @samp{sysroot} fails to locate the library, or if the
17254 path to the library is relative instead of absolute. If you want to
17255 use @samp{solib-search-path} instead of @samp{sysroot}, be sure to set
17256 @samp{sysroot} to a nonexistent directory to prevent @value{GDBN} from
17257 finding your host's libraries. @samp{sysroot} is preferred; setting
17258 it to a nonexistent directory may interfere with automatic loading
17259 of shared library symbols.
17261 @kindex show solib-search-path
17262 @item show solib-search-path
17263 Display the current shared library search path.
17265 @cindex DOS file-name semantics of file names.
17266 @kindex set target-file-system-kind (unix|dos-based|auto)
17267 @kindex show target-file-system-kind
17268 @item set target-file-system-kind @var{kind}
17269 Set assumed file system kind for target reported file names.
17271 Shared library file names as reported by the target system may not
17272 make sense as is on the system @value{GDBN} is running on. For
17273 example, when remote debugging a target that has MS-DOS based file
17274 system semantics, from a Unix host, the target may be reporting to
17275 @value{GDBN} a list of loaded shared libraries with file names such as
17276 @file{c:\Windows\kernel32.dll}. On Unix hosts, there's no concept of
17277 drive letters, so the @samp{c:\} prefix is not normally understood as
17278 indicating an absolute file name, and neither is the backslash
17279 normally considered a directory separator character. In that case,
17280 the native file system would interpret this whole absolute file name
17281 as a relative file name with no directory components. This would make
17282 it impossible to point @value{GDBN} at a copy of the remote target's
17283 shared libraries on the host using @code{set sysroot}, and impractical
17284 with @code{set solib-search-path}. Setting
17285 @code{target-file-system-kind} to @code{dos-based} tells @value{GDBN}
17286 to interpret such file names similarly to how the target would, and to
17287 map them to file names valid on @value{GDBN}'s native file system
17288 semantics. The value of @var{kind} can be @code{"auto"}, in addition
17289 to one of the supported file system kinds. In that case, @value{GDBN}
17290 tries to determine the appropriate file system variant based on the
17291 current target's operating system (@pxref{ABI, ,Configuring the
17292 Current ABI}). The supported file system settings are:
17296 Instruct @value{GDBN} to assume the target file system is of Unix
17297 kind. Only file names starting the forward slash (@samp{/}) character
17298 are considered absolute, and the directory separator character is also
17302 Instruct @value{GDBN} to assume the target file system is DOS based.
17303 File names starting with either a forward slash, or a drive letter
17304 followed by a colon (e.g., @samp{c:}), are considered absolute, and
17305 both the slash (@samp{/}) and the backslash (@samp{\\}) characters are
17306 considered directory separators.
17309 Instruct @value{GDBN} to use the file system kind associated with the
17310 target operating system (@pxref{ABI, ,Configuring the Current ABI}).
17311 This is the default.
17315 @cindex file name canonicalization
17316 @cindex base name differences
17317 When processing file names provided by the user, @value{GDBN}
17318 frequently needs to compare them to the file names recorded in the
17319 program's debug info. Normally, @value{GDBN} compares just the
17320 @dfn{base names} of the files as strings, which is reasonably fast
17321 even for very large programs. (The base name of a file is the last
17322 portion of its name, after stripping all the leading directories.)
17323 This shortcut in comparison is based upon the assumption that files
17324 cannot have more than one base name. This is usually true, but
17325 references to files that use symlinks or similar filesystem
17326 facilities violate that assumption. If your program records files
17327 using such facilities, or if you provide file names to @value{GDBN}
17328 using symlinks etc., you can set @code{basenames-may-differ} to
17329 @code{true} to instruct @value{GDBN} to completely canonicalize each
17330 pair of file names it needs to compare. This will make file-name
17331 comparisons accurate, but at a price of a significant slowdown.
17334 @item set basenames-may-differ
17335 @kindex set basenames-may-differ
17336 Set whether a source file may have multiple base names.
17338 @item show basenames-may-differ
17339 @kindex show basenames-may-differ
17340 Show whether a source file may have multiple base names.
17343 @node Separate Debug Files
17344 @section Debugging Information in Separate Files
17345 @cindex separate debugging information files
17346 @cindex debugging information in separate files
17347 @cindex @file{.debug} subdirectories
17348 @cindex debugging information directory, global
17349 @cindex global debugging information directories
17350 @cindex build ID, and separate debugging files
17351 @cindex @file{.build-id} directory
17353 @value{GDBN} allows you to put a program's debugging information in a
17354 file separate from the executable itself, in a way that allows
17355 @value{GDBN} to find and load the debugging information automatically.
17356 Since debugging information can be very large---sometimes larger
17357 than the executable code itself---some systems distribute debugging
17358 information for their executables in separate files, which users can
17359 install only when they need to debug a problem.
17361 @value{GDBN} supports two ways of specifying the separate debug info
17366 The executable contains a @dfn{debug link} that specifies the name of
17367 the separate debug info file. The separate debug file's name is
17368 usually @file{@var{executable}.debug}, where @var{executable} is the
17369 name of the corresponding executable file without leading directories
17370 (e.g., @file{ls.debug} for @file{/usr/bin/ls}). In addition, the
17371 debug link specifies a 32-bit @dfn{Cyclic Redundancy Check} (CRC)
17372 checksum for the debug file, which @value{GDBN} uses to validate that
17373 the executable and the debug file came from the same build.
17376 The executable contains a @dfn{build ID}, a unique bit string that is
17377 also present in the corresponding debug info file. (This is supported
17378 only on some operating systems, notably those which use the ELF format
17379 for binary files and the @sc{gnu} Binutils.) For more details about
17380 this feature, see the description of the @option{--build-id}
17381 command-line option in @ref{Options, , Command Line Options, ld.info,
17382 The GNU Linker}. The debug info file's name is not specified
17383 explicitly by the build ID, but can be computed from the build ID, see
17387 Depending on the way the debug info file is specified, @value{GDBN}
17388 uses two different methods of looking for the debug file:
17392 For the ``debug link'' method, @value{GDBN} looks up the named file in
17393 the directory of the executable file, then in a subdirectory of that
17394 directory named @file{.debug}, and finally under each one of the global debug
17395 directories, in a subdirectory whose name is identical to the leading
17396 directories of the executable's absolute file name.
17399 For the ``build ID'' method, @value{GDBN} looks in the
17400 @file{.build-id} subdirectory of each one of the global debug directories for
17401 a file named @file{@var{nn}/@var{nnnnnnnn}.debug}, where @var{nn} are the
17402 first 2 hex characters of the build ID bit string, and @var{nnnnnnnn}
17403 are the rest of the bit string. (Real build ID strings are 32 or more
17404 hex characters, not 10.)
17407 So, for example, suppose you ask @value{GDBN} to debug
17408 @file{/usr/bin/ls}, which has a debug link that specifies the
17409 file @file{ls.debug}, and a build ID whose value in hex is
17410 @code{abcdef1234}. If the list of the global debug directories includes
17411 @file{/usr/lib/debug}, then @value{GDBN} will look for the following
17412 debug information files, in the indicated order:
17416 @file{/usr/lib/debug/.build-id/ab/cdef1234.debug}
17418 @file{/usr/bin/ls.debug}
17420 @file{/usr/bin/.debug/ls.debug}
17422 @file{/usr/lib/debug/usr/bin/ls.debug}.
17425 @anchor{debug-file-directory}
17426 Global debugging info directories default to what is set by @value{GDBN}
17427 configure option @option{--with-separate-debug-dir}. During @value{GDBN} run
17428 you can also set the global debugging info directories, and view the list
17429 @value{GDBN} is currently using.
17433 @kindex set debug-file-directory
17434 @item set debug-file-directory @var{directories}
17435 Set the directories which @value{GDBN} searches for separate debugging
17436 information files to @var{directory}. Multiple path components can be set
17437 concatenating them by a path separator.
17439 @kindex show debug-file-directory
17440 @item show debug-file-directory
17441 Show the directories @value{GDBN} searches for separate debugging
17446 @cindex @code{.gnu_debuglink} sections
17447 @cindex debug link sections
17448 A debug link is a special section of the executable file named
17449 @code{.gnu_debuglink}. The section must contain:
17453 A filename, with any leading directory components removed, followed by
17456 zero to three bytes of padding, as needed to reach the next four-byte
17457 boundary within the section, and
17459 a four-byte CRC checksum, stored in the same endianness used for the
17460 executable file itself. The checksum is computed on the debugging
17461 information file's full contents by the function given below, passing
17462 zero as the @var{crc} argument.
17465 Any executable file format can carry a debug link, as long as it can
17466 contain a section named @code{.gnu_debuglink} with the contents
17469 @cindex @code{.note.gnu.build-id} sections
17470 @cindex build ID sections
17471 The build ID is a special section in the executable file (and in other
17472 ELF binary files that @value{GDBN} may consider). This section is
17473 often named @code{.note.gnu.build-id}, but that name is not mandatory.
17474 It contains unique identification for the built files---the ID remains
17475 the same across multiple builds of the same build tree. The default
17476 algorithm SHA1 produces 160 bits (40 hexadecimal characters) of the
17477 content for the build ID string. The same section with an identical
17478 value is present in the original built binary with symbols, in its
17479 stripped variant, and in the separate debugging information file.
17481 The debugging information file itself should be an ordinary
17482 executable, containing a full set of linker symbols, sections, and
17483 debugging information. The sections of the debugging information file
17484 should have the same names, addresses, and sizes as the original file,
17485 but they need not contain any data---much like a @code{.bss} section
17486 in an ordinary executable.
17488 The @sc{gnu} binary utilities (Binutils) package includes the
17489 @samp{objcopy} utility that can produce
17490 the separated executable / debugging information file pairs using the
17491 following commands:
17494 @kbd{objcopy --only-keep-debug foo foo.debug}
17499 These commands remove the debugging
17500 information from the executable file @file{foo} and place it in the file
17501 @file{foo.debug}. You can use the first, second or both methods to link the
17506 The debug link method needs the following additional command to also leave
17507 behind a debug link in @file{foo}:
17510 @kbd{objcopy --add-gnu-debuglink=foo.debug foo}
17513 Ulrich Drepper's @file{elfutils} package, starting with version 0.53, contains
17514 a version of the @code{strip} command such that the command @kbd{strip foo -f
17515 foo.debug} has the same functionality as the two @code{objcopy} commands and
17516 the @code{ln -s} command above, together.
17519 Build ID gets embedded into the main executable using @code{ld --build-id} or
17520 the @value{NGCC} counterpart @code{gcc -Wl,--build-id}. Build ID support plus
17521 compatibility fixes for debug files separation are present in @sc{gnu} binary
17522 utilities (Binutils) package since version 2.18.
17527 @cindex CRC algorithm definition
17528 The CRC used in @code{.gnu_debuglink} is the CRC-32 defined in
17529 IEEE 802.3 using the polynomial:
17531 @c TexInfo requires naked braces for multi-digit exponents for Tex
17532 @c output, but this causes HTML output to barf. HTML has to be set using
17533 @c raw commands. So we end up having to specify this equation in 2
17538 <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>
17539 + <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
17545 @math{x^{32} + x^{26} + x^{23} + x^{22} + x^{16} + x^{12} + x^{11}}
17546 @math{+ x^{10} + x^8 + x^7 + x^5 + x^4 + x^2 + x + 1}
17550 The function is computed byte at a time, taking the least
17551 significant bit of each byte first. The initial pattern
17552 @code{0xffffffff} is used, to ensure leading zeros affect the CRC and
17553 the final result is inverted to ensure trailing zeros also affect the
17556 @emph{Note:} This is the same CRC polynomial as used in handling the
17557 @dfn{Remote Serial Protocol} @code{qCRC} packet (@pxref{Remote Protocol,
17558 , @value{GDBN} Remote Serial Protocol}). However in the
17559 case of the Remote Serial Protocol, the CRC is computed @emph{most}
17560 significant bit first, and the result is not inverted, so trailing
17561 zeros have no effect on the CRC value.
17563 To complete the description, we show below the code of the function
17564 which produces the CRC used in @code{.gnu_debuglink}. Inverting the
17565 initially supplied @code{crc} argument means that an initial call to
17566 this function passing in zero will start computing the CRC using
17569 @kindex gnu_debuglink_crc32
17572 gnu_debuglink_crc32 (unsigned long crc,
17573 unsigned char *buf, size_t len)
17575 static const unsigned long crc32_table[256] =
17577 0x00000000, 0x77073096, 0xee0e612c, 0x990951ba, 0x076dc419,
17578 0x706af48f, 0xe963a535, 0x9e6495a3, 0x0edb8832, 0x79dcb8a4,
17579 0xe0d5e91e, 0x97d2d988, 0x09b64c2b, 0x7eb17cbd, 0xe7b82d07,
17580 0x90bf1d91, 0x1db71064, 0x6ab020f2, 0xf3b97148, 0x84be41de,
17581 0x1adad47d, 0x6ddde4eb, 0xf4d4b551, 0x83d385c7, 0x136c9856,
17582 0x646ba8c0, 0xfd62f97a, 0x8a65c9ec, 0x14015c4f, 0x63066cd9,
17583 0xfa0f3d63, 0x8d080df5, 0x3b6e20c8, 0x4c69105e, 0xd56041e4,
17584 0xa2677172, 0x3c03e4d1, 0x4b04d447, 0xd20d85fd, 0xa50ab56b,
17585 0x35b5a8fa, 0x42b2986c, 0xdbbbc9d6, 0xacbcf940, 0x32d86ce3,
17586 0x45df5c75, 0xdcd60dcf, 0xabd13d59, 0x26d930ac, 0x51de003a,
17587 0xc8d75180, 0xbfd06116, 0x21b4f4b5, 0x56b3c423, 0xcfba9599,
17588 0xb8bda50f, 0x2802b89e, 0x5f058808, 0xc60cd9b2, 0xb10be924,
17589 0x2f6f7c87, 0x58684c11, 0xc1611dab, 0xb6662d3d, 0x76dc4190,
17590 0x01db7106, 0x98d220bc, 0xefd5102a, 0x71b18589, 0x06b6b51f,
17591 0x9fbfe4a5, 0xe8b8d433, 0x7807c9a2, 0x0f00f934, 0x9609a88e,
17592 0xe10e9818, 0x7f6a0dbb, 0x086d3d2d, 0x91646c97, 0xe6635c01,
17593 0x6b6b51f4, 0x1c6c6162, 0x856530d8, 0xf262004e, 0x6c0695ed,
17594 0x1b01a57b, 0x8208f4c1, 0xf50fc457, 0x65b0d9c6, 0x12b7e950,
17595 0x8bbeb8ea, 0xfcb9887c, 0x62dd1ddf, 0x15da2d49, 0x8cd37cf3,
17596 0xfbd44c65, 0x4db26158, 0x3ab551ce, 0xa3bc0074, 0xd4bb30e2,
17597 0x4adfa541, 0x3dd895d7, 0xa4d1c46d, 0xd3d6f4fb, 0x4369e96a,
17598 0x346ed9fc, 0xad678846, 0xda60b8d0, 0x44042d73, 0x33031de5,
17599 0xaa0a4c5f, 0xdd0d7cc9, 0x5005713c, 0x270241aa, 0xbe0b1010,
17600 0xc90c2086, 0x5768b525, 0x206f85b3, 0xb966d409, 0xce61e49f,
17601 0x5edef90e, 0x29d9c998, 0xb0d09822, 0xc7d7a8b4, 0x59b33d17,
17602 0x2eb40d81, 0xb7bd5c3b, 0xc0ba6cad, 0xedb88320, 0x9abfb3b6,
17603 0x03b6e20c, 0x74b1d29a, 0xead54739, 0x9dd277af, 0x04db2615,
17604 0x73dc1683, 0xe3630b12, 0x94643b84, 0x0d6d6a3e, 0x7a6a5aa8,
17605 0xe40ecf0b, 0x9309ff9d, 0x0a00ae27, 0x7d079eb1, 0xf00f9344,
17606 0x8708a3d2, 0x1e01f268, 0x6906c2fe, 0xf762575d, 0x806567cb,
17607 0x196c3671, 0x6e6b06e7, 0xfed41b76, 0x89d32be0, 0x10da7a5a,
17608 0x67dd4acc, 0xf9b9df6f, 0x8ebeeff9, 0x17b7be43, 0x60b08ed5,
17609 0xd6d6a3e8, 0xa1d1937e, 0x38d8c2c4, 0x4fdff252, 0xd1bb67f1,
17610 0xa6bc5767, 0x3fb506dd, 0x48b2364b, 0xd80d2bda, 0xaf0a1b4c,
17611 0x36034af6, 0x41047a60, 0xdf60efc3, 0xa867df55, 0x316e8eef,
17612 0x4669be79, 0xcb61b38c, 0xbc66831a, 0x256fd2a0, 0x5268e236,
17613 0xcc0c7795, 0xbb0b4703, 0x220216b9, 0x5505262f, 0xc5ba3bbe,
17614 0xb2bd0b28, 0x2bb45a92, 0x5cb36a04, 0xc2d7ffa7, 0xb5d0cf31,
17615 0x2cd99e8b, 0x5bdeae1d, 0x9b64c2b0, 0xec63f226, 0x756aa39c,
17616 0x026d930a, 0x9c0906a9, 0xeb0e363f, 0x72076785, 0x05005713,
17617 0x95bf4a82, 0xe2b87a14, 0x7bb12bae, 0x0cb61b38, 0x92d28e9b,
17618 0xe5d5be0d, 0x7cdcefb7, 0x0bdbdf21, 0x86d3d2d4, 0xf1d4e242,
17619 0x68ddb3f8, 0x1fda836e, 0x81be16cd, 0xf6b9265b, 0x6fb077e1,
17620 0x18b74777, 0x88085ae6, 0xff0f6a70, 0x66063bca, 0x11010b5c,
17621 0x8f659eff, 0xf862ae69, 0x616bffd3, 0x166ccf45, 0xa00ae278,
17622 0xd70dd2ee, 0x4e048354, 0x3903b3c2, 0xa7672661, 0xd06016f7,
17623 0x4969474d, 0x3e6e77db, 0xaed16a4a, 0xd9d65adc, 0x40df0b66,
17624 0x37d83bf0, 0xa9bcae53, 0xdebb9ec5, 0x47b2cf7f, 0x30b5ffe9,
17625 0xbdbdf21c, 0xcabac28a, 0x53b39330, 0x24b4a3a6, 0xbad03605,
17626 0xcdd70693, 0x54de5729, 0x23d967bf, 0xb3667a2e, 0xc4614ab8,
17627 0x5d681b02, 0x2a6f2b94, 0xb40bbe37, 0xc30c8ea1, 0x5a05df1b,
17630 unsigned char *end;
17632 crc = ~crc & 0xffffffff;
17633 for (end = buf + len; buf < end; ++buf)
17634 crc = crc32_table[(crc ^ *buf) & 0xff] ^ (crc >> 8);
17635 return ~crc & 0xffffffff;
17640 This computation does not apply to the ``build ID'' method.
17642 @node MiniDebugInfo
17643 @section Debugging information in a special section
17644 @cindex separate debug sections
17645 @cindex @samp{.gnu_debugdata} section
17647 Some systems ship pre-built executables and libraries that have a
17648 special @samp{.gnu_debugdata} section. This feature is called
17649 @dfn{MiniDebugInfo}. This section holds an LZMA-compressed object and
17650 is used to supply extra symbols for backtraces.
17652 The intent of this section is to provide extra minimal debugging
17653 information for use in simple backtraces. It is not intended to be a
17654 replacement for full separate debugging information (@pxref{Separate
17655 Debug Files}). The example below shows the intended use; however,
17656 @value{GDBN} does not currently put restrictions on what sort of
17657 debugging information might be included in the section.
17659 @value{GDBN} has support for this extension. If the section exists,
17660 then it is used provided that no other source of debugging information
17661 can be found, and that @value{GDBN} was configured with LZMA support.
17663 This section can be easily created using @command{objcopy} and other
17664 standard utilities:
17667 # Extract the dynamic symbols from the main binary, there is no need
17668 # to also have these in the normal symbol table.
17669 nm -D @var{binary} --format=posix --defined-only \
17670 | awk '@{ print $1 @}' | sort > dynsyms
17672 # Extract all the text (i.e. function) symbols from the debuginfo.
17673 # (Note that we actually also accept "D" symbols, for the benefit
17674 # of platforms like PowerPC64 that use function descriptors.)
17675 nm @var{binary} --format=posix --defined-only \
17676 | awk '@{ if ($2 == "T" || $2 == "t" || $2 == "D") print $1 @}' \
17679 # Keep all the function symbols not already in the dynamic symbol
17681 comm -13 dynsyms funcsyms > keep_symbols
17683 # Separate full debug info into debug binary.
17684 objcopy --only-keep-debug @var{binary} debug
17686 # Copy the full debuginfo, keeping only a minimal set of symbols and
17687 # removing some unnecessary sections.
17688 objcopy -S --remove-section .gdb_index --remove-section .comment \
17689 --keep-symbols=keep_symbols debug mini_debuginfo
17691 # Drop the full debug info from the original binary.
17692 strip --strip-all -R .comment @var{binary}
17694 # Inject the compressed data into the .gnu_debugdata section of the
17697 objcopy --add-section .gnu_debugdata=mini_debuginfo.xz @var{binary}
17701 @section Index Files Speed Up @value{GDBN}
17702 @cindex index files
17703 @cindex @samp{.gdb_index} section
17705 When @value{GDBN} finds a symbol file, it scans the symbols in the
17706 file in order to construct an internal symbol table. This lets most
17707 @value{GDBN} operations work quickly---at the cost of a delay early
17708 on. For large programs, this delay can be quite lengthy, so
17709 @value{GDBN} provides a way to build an index, which speeds up
17712 The index is stored as a section in the symbol file. @value{GDBN} can
17713 write the index to a file, then you can put it into the symbol file
17714 using @command{objcopy}.
17716 To create an index file, use the @code{save gdb-index} command:
17719 @item save gdb-index @var{directory}
17720 @kindex save gdb-index
17721 Create an index file for each symbol file currently known by
17722 @value{GDBN}. Each file is named after its corresponding symbol file,
17723 with @samp{.gdb-index} appended, and is written into the given
17727 Once you have created an index file you can merge it into your symbol
17728 file, here named @file{symfile}, using @command{objcopy}:
17731 $ objcopy --add-section .gdb_index=symfile.gdb-index \
17732 --set-section-flags .gdb_index=readonly symfile symfile
17735 @value{GDBN} will normally ignore older versions of @file{.gdb_index}
17736 sections that have been deprecated. Usually they are deprecated because
17737 they are missing a new feature or have performance issues.
17738 To tell @value{GDBN} to use a deprecated index section anyway
17739 specify @code{set use-deprecated-index-sections on}.
17740 The default is @code{off}.
17741 This can speed up startup, but may result in some functionality being lost.
17742 @xref{Index Section Format}.
17744 @emph{Warning:} Setting @code{use-deprecated-index-sections} to @code{on}
17745 must be done before gdb reads the file. The following will not work:
17748 $ gdb -ex "set use-deprecated-index-sections on" <program>
17751 Instead you must do, for example,
17754 $ gdb -iex "set use-deprecated-index-sections on" <program>
17757 There are currently some limitation on indices. They only work when
17758 for DWARF debugging information, not stabs. And, they do not
17759 currently work for programs using Ada.
17761 @node Symbol Errors
17762 @section Errors Reading Symbol Files
17764 While reading a symbol file, @value{GDBN} occasionally encounters problems,
17765 such as symbol types it does not recognize, or known bugs in compiler
17766 output. By default, @value{GDBN} does not notify you of such problems, since
17767 they are relatively common and primarily of interest to people
17768 debugging compilers. If you are interested in seeing information
17769 about ill-constructed symbol tables, you can either ask @value{GDBN} to print
17770 only one message about each such type of problem, no matter how many
17771 times the problem occurs; or you can ask @value{GDBN} to print more messages,
17772 to see how many times the problems occur, with the @code{set
17773 complaints} command (@pxref{Messages/Warnings, ,Optional Warnings and
17776 The messages currently printed, and their meanings, include:
17779 @item inner block not inside outer block in @var{symbol}
17781 The symbol information shows where symbol scopes begin and end
17782 (such as at the start of a function or a block of statements). This
17783 error indicates that an inner scope block is not fully contained
17784 in its outer scope blocks.
17786 @value{GDBN} circumvents the problem by treating the inner block as if it had
17787 the same scope as the outer block. In the error message, @var{symbol}
17788 may be shown as ``@code{(don't know)}'' if the outer block is not a
17791 @item block at @var{address} out of order
17793 The symbol information for symbol scope blocks should occur in
17794 order of increasing addresses. This error indicates that it does not
17797 @value{GDBN} does not circumvent this problem, and has trouble
17798 locating symbols in the source file whose symbols it is reading. (You
17799 can often determine what source file is affected by specifying
17800 @code{set verbose on}. @xref{Messages/Warnings, ,Optional Warnings and
17803 @item bad block start address patched
17805 The symbol information for a symbol scope block has a start address
17806 smaller than the address of the preceding source line. This is known
17807 to occur in the SunOS 4.1.1 (and earlier) C compiler.
17809 @value{GDBN} circumvents the problem by treating the symbol scope block as
17810 starting on the previous source line.
17812 @item bad string table offset in symbol @var{n}
17815 Symbol number @var{n} contains a pointer into the string table which is
17816 larger than the size of the string table.
17818 @value{GDBN} circumvents the problem by considering the symbol to have the
17819 name @code{foo}, which may cause other problems if many symbols end up
17822 @item unknown symbol type @code{0x@var{nn}}
17824 The symbol information contains new data types that @value{GDBN} does
17825 not yet know how to read. @code{0x@var{nn}} is the symbol type of the
17826 uncomprehended information, in hexadecimal.
17828 @value{GDBN} circumvents the error by ignoring this symbol information.
17829 This usually allows you to debug your program, though certain symbols
17830 are not accessible. If you encounter such a problem and feel like
17831 debugging it, you can debug @code{@value{GDBP}} with itself, breakpoint
17832 on @code{complain}, then go up to the function @code{read_dbx_symtab}
17833 and examine @code{*bufp} to see the symbol.
17835 @item stub type has NULL name
17837 @value{GDBN} could not find the full definition for a struct or class.
17839 @item const/volatile indicator missing (ok if using g++ v1.x), got@dots{}
17840 The symbol information for a C@t{++} member function is missing some
17841 information that recent versions of the compiler should have output for
17844 @item info mismatch between compiler and debugger
17846 @value{GDBN} could not parse a type specification output by the compiler.
17851 @section GDB Data Files
17853 @cindex prefix for data files
17854 @value{GDBN} will sometimes read an auxiliary data file. These files
17855 are kept in a directory known as the @dfn{data directory}.
17857 You can set the data directory's name, and view the name @value{GDBN}
17858 is currently using.
17861 @kindex set data-directory
17862 @item set data-directory @var{directory}
17863 Set the directory which @value{GDBN} searches for auxiliary data files
17864 to @var{directory}.
17866 @kindex show data-directory
17867 @item show data-directory
17868 Show the directory @value{GDBN} searches for auxiliary data files.
17871 @cindex default data directory
17872 @cindex @samp{--with-gdb-datadir}
17873 You can set the default data directory by using the configure-time
17874 @samp{--with-gdb-datadir} option. If the data directory is inside
17875 @value{GDBN}'s configured binary prefix (set with @samp{--prefix} or
17876 @samp{--exec-prefix}), then the default data directory will be updated
17877 automatically if the installed @value{GDBN} is moved to a new
17880 The data directory may also be specified with the
17881 @code{--data-directory} command line option.
17882 @xref{Mode Options}.
17885 @chapter Specifying a Debugging Target
17887 @cindex debugging target
17888 A @dfn{target} is the execution environment occupied by your program.
17890 Often, @value{GDBN} runs in the same host environment as your program;
17891 in that case, the debugging target is specified as a side effect when
17892 you use the @code{file} or @code{core} commands. When you need more
17893 flexibility---for example, running @value{GDBN} on a physically separate
17894 host, or controlling a standalone system over a serial port or a
17895 realtime system over a TCP/IP connection---you can use the @code{target}
17896 command to specify one of the target types configured for @value{GDBN}
17897 (@pxref{Target Commands, ,Commands for Managing Targets}).
17899 @cindex target architecture
17900 It is possible to build @value{GDBN} for several different @dfn{target
17901 architectures}. When @value{GDBN} is built like that, you can choose
17902 one of the available architectures with the @kbd{set architecture}
17906 @kindex set architecture
17907 @kindex show architecture
17908 @item set architecture @var{arch}
17909 This command sets the current target architecture to @var{arch}. The
17910 value of @var{arch} can be @code{"auto"}, in addition to one of the
17911 supported architectures.
17913 @item show architecture
17914 Show the current target architecture.
17916 @item set processor
17918 @kindex set processor
17919 @kindex show processor
17920 These are alias commands for, respectively, @code{set architecture}
17921 and @code{show architecture}.
17925 * Active Targets:: Active targets
17926 * Target Commands:: Commands for managing targets
17927 * Byte Order:: Choosing target byte order
17930 @node Active Targets
17931 @section Active Targets
17933 @cindex stacking targets
17934 @cindex active targets
17935 @cindex multiple targets
17937 There are multiple classes of targets such as: processes, executable files or
17938 recording sessions. Core files belong to the process class, making core file
17939 and process mutually exclusive. Otherwise, @value{GDBN} can work concurrently
17940 on multiple active targets, one in each class. This allows you to (for
17941 example) start a process and inspect its activity, while still having access to
17942 the executable file after the process finishes. Or if you start process
17943 recording (@pxref{Reverse Execution}) and @code{reverse-step} there, you are
17944 presented a virtual layer of the recording target, while the process target
17945 remains stopped at the chronologically last point of the process execution.
17947 Use the @code{core-file} and @code{exec-file} commands to select a new core
17948 file or executable target (@pxref{Files, ,Commands to Specify Files}). To
17949 specify as a target a process that is already running, use the @code{attach}
17950 command (@pxref{Attach, ,Debugging an Already-running Process}).
17952 @node Target Commands
17953 @section Commands for Managing Targets
17956 @item target @var{type} @var{parameters}
17957 Connects the @value{GDBN} host environment to a target machine or
17958 process. A target is typically a protocol for talking to debugging
17959 facilities. You use the argument @var{type} to specify the type or
17960 protocol of the target machine.
17962 Further @var{parameters} are interpreted by the target protocol, but
17963 typically include things like device names or host names to connect
17964 with, process numbers, and baud rates.
17966 The @code{target} command does not repeat if you press @key{RET} again
17967 after executing the command.
17969 @kindex help target
17971 Displays the names of all targets available. To display targets
17972 currently selected, use either @code{info target} or @code{info files}
17973 (@pxref{Files, ,Commands to Specify Files}).
17975 @item help target @var{name}
17976 Describe a particular target, including any parameters necessary to
17979 @kindex set gnutarget
17980 @item set gnutarget @var{args}
17981 @value{GDBN} uses its own library BFD to read your files. @value{GDBN}
17982 knows whether it is reading an @dfn{executable},
17983 a @dfn{core}, or a @dfn{.o} file; however, you can specify the file format
17984 with the @code{set gnutarget} command. Unlike most @code{target} commands,
17985 with @code{gnutarget} the @code{target} refers to a program, not a machine.
17988 @emph{Warning:} To specify a file format with @code{set gnutarget},
17989 you must know the actual BFD name.
17993 @xref{Files, , Commands to Specify Files}.
17995 @kindex show gnutarget
17996 @item show gnutarget
17997 Use the @code{show gnutarget} command to display what file format
17998 @code{gnutarget} is set to read. If you have not set @code{gnutarget},
17999 @value{GDBN} will determine the file format for each file automatically,
18000 and @code{show gnutarget} displays @samp{The current BFD target is "auto"}.
18003 @cindex common targets
18004 Here are some common targets (available, or not, depending on the GDB
18009 @item target exec @var{program}
18010 @cindex executable file target
18011 An executable file. @samp{target exec @var{program}} is the same as
18012 @samp{exec-file @var{program}}.
18014 @item target core @var{filename}
18015 @cindex core dump file target
18016 A core dump file. @samp{target core @var{filename}} is the same as
18017 @samp{core-file @var{filename}}.
18019 @item target remote @var{medium}
18020 @cindex remote target
18021 A remote system connected to @value{GDBN} via a serial line or network
18022 connection. This command tells @value{GDBN} to use its own remote
18023 protocol over @var{medium} for debugging. @xref{Remote Debugging}.
18025 For example, if you have a board connected to @file{/dev/ttya} on the
18026 machine running @value{GDBN}, you could say:
18029 target remote /dev/ttya
18032 @code{target remote} supports the @code{load} command. This is only
18033 useful if you have some other way of getting the stub to the target
18034 system, and you can put it somewhere in memory where it won't get
18035 clobbered by the download.
18037 @item target sim @r{[}@var{simargs}@r{]} @dots{}
18038 @cindex built-in simulator target
18039 Builtin CPU simulator. @value{GDBN} includes simulators for most architectures.
18047 works; however, you cannot assume that a specific memory map, device
18048 drivers, or even basic I/O is available, although some simulators do
18049 provide these. For info about any processor-specific simulator details,
18050 see the appropriate section in @ref{Embedded Processors, ,Embedded
18055 Different targets are available on different configurations of @value{GDBN};
18056 your configuration may have more or fewer targets.
18058 Many remote targets require you to download the executable's code once
18059 you've successfully established a connection. You may wish to control
18060 various aspects of this process.
18065 @kindex set hash@r{, for remote monitors}
18066 @cindex hash mark while downloading
18067 This command controls whether a hash mark @samp{#} is displayed while
18068 downloading a file to the remote monitor. If on, a hash mark is
18069 displayed after each S-record is successfully downloaded to the
18073 @kindex show hash@r{, for remote monitors}
18074 Show the current status of displaying the hash mark.
18076 @item set debug monitor
18077 @kindex set debug monitor
18078 @cindex display remote monitor communications
18079 Enable or disable display of communications messages between
18080 @value{GDBN} and the remote monitor.
18082 @item show debug monitor
18083 @kindex show debug monitor
18084 Show the current status of displaying communications between
18085 @value{GDBN} and the remote monitor.
18090 @kindex load @var{filename}
18091 @item load @var{filename}
18093 Depending on what remote debugging facilities are configured into
18094 @value{GDBN}, the @code{load} command may be available. Where it exists, it
18095 is meant to make @var{filename} (an executable) available for debugging
18096 on the remote system---by downloading, or dynamic linking, for example.
18097 @code{load} also records the @var{filename} symbol table in @value{GDBN}, like
18098 the @code{add-symbol-file} command.
18100 If your @value{GDBN} does not have a @code{load} command, attempting to
18101 execute it gets the error message ``@code{You can't do that when your
18102 target is @dots{}}''
18104 The file is loaded at whatever address is specified in the executable.
18105 For some object file formats, you can specify the load address when you
18106 link the program; for other formats, like a.out, the object file format
18107 specifies a fixed address.
18108 @c FIXME! This would be a good place for an xref to the GNU linker doc.
18110 Depending on the remote side capabilities, @value{GDBN} may be able to
18111 load programs into flash memory.
18113 @code{load} does not repeat if you press @key{RET} again after using it.
18117 @section Choosing Target Byte Order
18119 @cindex choosing target byte order
18120 @cindex target byte order
18122 Some types of processors, such as the @acronym{MIPS}, PowerPC, and Renesas SH,
18123 offer the ability to run either big-endian or little-endian byte
18124 orders. Usually the executable or symbol will include a bit to
18125 designate the endian-ness, and you will not need to worry about
18126 which to use. However, you may still find it useful to adjust
18127 @value{GDBN}'s idea of processor endian-ness manually.
18131 @item set endian big
18132 Instruct @value{GDBN} to assume the target is big-endian.
18134 @item set endian little
18135 Instruct @value{GDBN} to assume the target is little-endian.
18137 @item set endian auto
18138 Instruct @value{GDBN} to use the byte order associated with the
18142 Display @value{GDBN}'s current idea of the target byte order.
18146 Note that these commands merely adjust interpretation of symbolic
18147 data on the host, and that they have absolutely no effect on the
18151 @node Remote Debugging
18152 @chapter Debugging Remote Programs
18153 @cindex remote debugging
18155 If you are trying to debug a program running on a machine that cannot run
18156 @value{GDBN} in the usual way, it is often useful to use remote debugging.
18157 For example, you might use remote debugging on an operating system kernel,
18158 or on a small system which does not have a general purpose operating system
18159 powerful enough to run a full-featured debugger.
18161 Some configurations of @value{GDBN} have special serial or TCP/IP interfaces
18162 to make this work with particular debugging targets. In addition,
18163 @value{GDBN} comes with a generic serial protocol (specific to @value{GDBN},
18164 but not specific to any particular target system) which you can use if you
18165 write the remote stubs---the code that runs on the remote system to
18166 communicate with @value{GDBN}.
18168 Other remote targets may be available in your
18169 configuration of @value{GDBN}; use @code{help target} to list them.
18172 * Connecting:: Connecting to a remote target
18173 * File Transfer:: Sending files to a remote system
18174 * Server:: Using the gdbserver program
18175 * Remote Configuration:: Remote configuration
18176 * Remote Stub:: Implementing a remote stub
18180 @section Connecting to a Remote Target
18182 On the @value{GDBN} host machine, you will need an unstripped copy of
18183 your program, since @value{GDBN} needs symbol and debugging information.
18184 Start up @value{GDBN} as usual, using the name of the local copy of your
18185 program as the first argument.
18187 @cindex @code{target remote}
18188 @value{GDBN} can communicate with the target over a serial line, or
18189 over an @acronym{IP} network using @acronym{TCP} or @acronym{UDP}. In
18190 each case, @value{GDBN} uses the same protocol for debugging your
18191 program; only the medium carrying the debugging packets varies. The
18192 @code{target remote} command establishes a connection to the target.
18193 Its arguments indicate which medium to use:
18197 @item target remote @var{serial-device}
18198 @cindex serial line, @code{target remote}
18199 Use @var{serial-device} to communicate with the target. For example,
18200 to use a serial line connected to the device named @file{/dev/ttyb}:
18203 target remote /dev/ttyb
18206 If you're using a serial line, you may want to give @value{GDBN} the
18207 @samp{--baud} option, or use the @code{set serial baud} command
18208 (@pxref{Remote Configuration, set serial baud}) before the
18209 @code{target} command.
18211 @item target remote @code{@var{host}:@var{port}}
18212 @itemx target remote @code{tcp:@var{host}:@var{port}}
18213 @cindex @acronym{TCP} port, @code{target remote}
18214 Debug using a @acronym{TCP} connection to @var{port} on @var{host}.
18215 The @var{host} may be either a host name or a numeric @acronym{IP}
18216 address; @var{port} must be a decimal number. The @var{host} could be
18217 the target machine itself, if it is directly connected to the net, or
18218 it might be a terminal server which in turn has a serial line to the
18221 For example, to connect to port 2828 on a terminal server named
18225 target remote manyfarms:2828
18228 If your remote target is actually running on the same machine as your
18229 debugger session (e.g.@: a simulator for your target running on the
18230 same host), you can omit the hostname. For example, to connect to
18231 port 1234 on your local machine:
18234 target remote :1234
18238 Note that the colon is still required here.
18240 @item target remote @code{udp:@var{host}:@var{port}}
18241 @cindex @acronym{UDP} port, @code{target remote}
18242 Debug using @acronym{UDP} packets to @var{port} on @var{host}. For example, to
18243 connect to @acronym{UDP} port 2828 on a terminal server named @code{manyfarms}:
18246 target remote udp:manyfarms:2828
18249 When using a @acronym{UDP} connection for remote debugging, you should
18250 keep in mind that the `U' stands for ``Unreliable''. @acronym{UDP}
18251 can silently drop packets on busy or unreliable networks, which will
18252 cause havoc with your debugging session.
18254 @item target remote | @var{command}
18255 @cindex pipe, @code{target remote} to
18256 Run @var{command} in the background and communicate with it using a
18257 pipe. The @var{command} is a shell command, to be parsed and expanded
18258 by the system's command shell, @code{/bin/sh}; it should expect remote
18259 protocol packets on its standard input, and send replies on its
18260 standard output. You could use this to run a stand-alone simulator
18261 that speaks the remote debugging protocol, to make net connections
18262 using programs like @code{ssh}, or for other similar tricks.
18264 If @var{command} closes its standard output (perhaps by exiting),
18265 @value{GDBN} will try to send it a @code{SIGTERM} signal. (If the
18266 program has already exited, this will have no effect.)
18270 Once the connection has been established, you can use all the usual
18271 commands to examine and change data. The remote program is already
18272 running; you can use @kbd{step} and @kbd{continue}, and you do not
18273 need to use @kbd{run}.
18275 @cindex interrupting remote programs
18276 @cindex remote programs, interrupting
18277 Whenever @value{GDBN} is waiting for the remote program, if you type the
18278 interrupt character (often @kbd{Ctrl-c}), @value{GDBN} attempts to stop the
18279 program. This may or may not succeed, depending in part on the hardware
18280 and the serial drivers the remote system uses. If you type the
18281 interrupt character once again, @value{GDBN} displays this prompt:
18284 Interrupted while waiting for the program.
18285 Give up (and stop debugging it)? (y or n)
18288 If you type @kbd{y}, @value{GDBN} abandons the remote debugging session.
18289 (If you decide you want to try again later, you can use @samp{target
18290 remote} again to connect once more.) If you type @kbd{n}, @value{GDBN}
18291 goes back to waiting.
18294 @kindex detach (remote)
18296 When you have finished debugging the remote program, you can use the
18297 @code{detach} command to release it from @value{GDBN} control.
18298 Detaching from the target normally resumes its execution, but the results
18299 will depend on your particular remote stub. After the @code{detach}
18300 command, @value{GDBN} is free to connect to another target.
18304 The @code{disconnect} command behaves like @code{detach}, except that
18305 the target is generally not resumed. It will wait for @value{GDBN}
18306 (this instance or another one) to connect and continue debugging. After
18307 the @code{disconnect} command, @value{GDBN} is again free to connect to
18310 @cindex send command to remote monitor
18311 @cindex extend @value{GDBN} for remote targets
18312 @cindex add new commands for external monitor
18314 @item monitor @var{cmd}
18315 This command allows you to send arbitrary commands directly to the
18316 remote monitor. Since @value{GDBN} doesn't care about the commands it
18317 sends like this, this command is the way to extend @value{GDBN}---you
18318 can add new commands that only the external monitor will understand
18322 @node File Transfer
18323 @section Sending files to a remote system
18324 @cindex remote target, file transfer
18325 @cindex file transfer
18326 @cindex sending files to remote systems
18328 Some remote targets offer the ability to transfer files over the same
18329 connection used to communicate with @value{GDBN}. This is convenient
18330 for targets accessible through other means, e.g.@: @sc{gnu}/Linux systems
18331 running @code{gdbserver} over a network interface. For other targets,
18332 e.g.@: embedded devices with only a single serial port, this may be
18333 the only way to upload or download files.
18335 Not all remote targets support these commands.
18339 @item remote put @var{hostfile} @var{targetfile}
18340 Copy file @var{hostfile} from the host system (the machine running
18341 @value{GDBN}) to @var{targetfile} on the target system.
18344 @item remote get @var{targetfile} @var{hostfile}
18345 Copy file @var{targetfile} from the target system to @var{hostfile}
18346 on the host system.
18348 @kindex remote delete
18349 @item remote delete @var{targetfile}
18350 Delete @var{targetfile} from the target system.
18355 @section Using the @code{gdbserver} Program
18358 @cindex remote connection without stubs
18359 @code{gdbserver} is a control program for Unix-like systems, which
18360 allows you to connect your program with a remote @value{GDBN} via
18361 @code{target remote}---but without linking in the usual debugging stub.
18363 @code{gdbserver} is not a complete replacement for the debugging stubs,
18364 because it requires essentially the same operating-system facilities
18365 that @value{GDBN} itself does. In fact, a system that can run
18366 @code{gdbserver} to connect to a remote @value{GDBN} could also run
18367 @value{GDBN} locally! @code{gdbserver} is sometimes useful nevertheless,
18368 because it is a much smaller program than @value{GDBN} itself. It is
18369 also easier to port than all of @value{GDBN}, so you may be able to get
18370 started more quickly on a new system by using @code{gdbserver}.
18371 Finally, if you develop code for real-time systems, you may find that
18372 the tradeoffs involved in real-time operation make it more convenient to
18373 do as much development work as possible on another system, for example
18374 by cross-compiling. You can use @code{gdbserver} to make a similar
18375 choice for debugging.
18377 @value{GDBN} and @code{gdbserver} communicate via either a serial line
18378 or a TCP connection, using the standard @value{GDBN} remote serial
18382 @emph{Warning:} @code{gdbserver} does not have any built-in security.
18383 Do not run @code{gdbserver} connected to any public network; a
18384 @value{GDBN} connection to @code{gdbserver} provides access to the
18385 target system with the same privileges as the user running
18389 @subsection Running @code{gdbserver}
18390 @cindex arguments, to @code{gdbserver}
18391 @cindex @code{gdbserver}, command-line arguments
18393 Run @code{gdbserver} on the target system. You need a copy of the
18394 program you want to debug, including any libraries it requires.
18395 @code{gdbserver} does not need your program's symbol table, so you can
18396 strip the program if necessary to save space. @value{GDBN} on the host
18397 system does all the symbol handling.
18399 To use the server, you must tell it how to communicate with @value{GDBN};
18400 the name of your program; and the arguments for your program. The usual
18404 target> gdbserver @var{comm} @var{program} [ @var{args} @dots{} ]
18407 @var{comm} is either a device name (to use a serial line), or a TCP
18408 hostname and portnumber, or @code{-} or @code{stdio} to use
18409 stdin/stdout of @code{gdbserver}.
18410 For example, to debug Emacs with the argument
18411 @samp{foo.txt} and communicate with @value{GDBN} over the serial port
18415 target> gdbserver /dev/com1 emacs foo.txt
18418 @code{gdbserver} waits passively for the host @value{GDBN} to communicate
18421 To use a TCP connection instead of a serial line:
18424 target> gdbserver host:2345 emacs foo.txt
18427 The only difference from the previous example is the first argument,
18428 specifying that you are communicating with the host @value{GDBN} via
18429 TCP. The @samp{host:2345} argument means that @code{gdbserver} is to
18430 expect a TCP connection from machine @samp{host} to local TCP port 2345.
18431 (Currently, the @samp{host} part is ignored.) You can choose any number
18432 you want for the port number as long as it does not conflict with any
18433 TCP ports already in use on the target system (for example, @code{23} is
18434 reserved for @code{telnet}).@footnote{If you choose a port number that
18435 conflicts with another service, @code{gdbserver} prints an error message
18436 and exits.} You must use the same port number with the host @value{GDBN}
18437 @code{target remote} command.
18439 The @code{stdio} connection is useful when starting @code{gdbserver}
18443 (gdb) target remote | ssh -T hostname gdbserver - hello
18446 The @samp{-T} option to ssh is provided because we don't need a remote pty,
18447 and we don't want escape-character handling. Ssh does this by default when
18448 a command is provided, the flag is provided to make it explicit.
18449 You could elide it if you want to.
18451 Programs started with stdio-connected gdbserver have @file{/dev/null} for
18452 @code{stdin}, and @code{stdout},@code{stderr} are sent back to gdb for
18453 display through a pipe connected to gdbserver.
18454 Both @code{stdout} and @code{stderr} use the same pipe.
18456 @subsubsection Attaching to a Running Program
18457 @cindex attach to a program, @code{gdbserver}
18458 @cindex @option{--attach}, @code{gdbserver} option
18460 On some targets, @code{gdbserver} can also attach to running programs.
18461 This is accomplished via the @code{--attach} argument. The syntax is:
18464 target> gdbserver --attach @var{comm} @var{pid}
18467 @var{pid} is the process ID of a currently running process. It isn't necessary
18468 to point @code{gdbserver} at a binary for the running process.
18471 You can debug processes by name instead of process ID if your target has the
18472 @code{pidof} utility:
18475 target> gdbserver --attach @var{comm} `pidof @var{program}`
18478 In case more than one copy of @var{program} is running, or @var{program}
18479 has multiple threads, most versions of @code{pidof} support the
18480 @code{-s} option to only return the first process ID.
18482 @subsubsection Multi-Process Mode for @code{gdbserver}
18483 @cindex @code{gdbserver}, multiple processes
18484 @cindex multiple processes with @code{gdbserver}
18486 When you connect to @code{gdbserver} using @code{target remote},
18487 @code{gdbserver} debugs the specified program only once. When the
18488 program exits, or you detach from it, @value{GDBN} closes the connection
18489 and @code{gdbserver} exits.
18491 If you connect using @kbd{target extended-remote}, @code{gdbserver}
18492 enters multi-process mode. When the debugged program exits, or you
18493 detach from it, @value{GDBN} stays connected to @code{gdbserver} even
18494 though no program is running. The @code{run} and @code{attach}
18495 commands instruct @code{gdbserver} to run or attach to a new program.
18496 The @code{run} command uses @code{set remote exec-file} (@pxref{set
18497 remote exec-file}) to select the program to run. Command line
18498 arguments are supported, except for wildcard expansion and I/O
18499 redirection (@pxref{Arguments}).
18501 @cindex @option{--multi}, @code{gdbserver} option
18502 To start @code{gdbserver} without supplying an initial command to run
18503 or process ID to attach, use the @option{--multi} command line option.
18504 Then you can connect using @kbd{target extended-remote} and start
18505 the program you want to debug.
18507 In multi-process mode @code{gdbserver} does not automatically exit unless you
18508 use the option @option{--once}. You can terminate it by using
18509 @code{monitor exit} (@pxref{Monitor Commands for gdbserver}). Note that the
18510 conditions under which @code{gdbserver} terminates depend on how @value{GDBN}
18511 connects to it (@kbd{target remote} or @kbd{target extended-remote}). The
18512 @option{--multi} option to @code{gdbserver} has no influence on that.
18514 @subsubsection TCP port allocation lifecycle of @code{gdbserver}
18516 This section applies only when @code{gdbserver} is run to listen on a TCP port.
18518 @code{gdbserver} normally terminates after all of its debugged processes have
18519 terminated in @kbd{target remote} mode. On the other hand, for @kbd{target
18520 extended-remote}, @code{gdbserver} stays running even with no processes left.
18521 @value{GDBN} normally terminates the spawned debugged process on its exit,
18522 which normally also terminates @code{gdbserver} in the @kbd{target remote}
18523 mode. Therefore, when the connection drops unexpectedly, and @value{GDBN}
18524 cannot ask @code{gdbserver} to kill its debugged processes, @code{gdbserver}
18525 stays running even in the @kbd{target remote} mode.
18527 When @code{gdbserver} stays running, @value{GDBN} can connect to it again later.
18528 Such reconnecting is useful for features like @ref{disconnected tracing}. For
18529 completeness, at most one @value{GDBN} can be connected at a time.
18531 @cindex @option{--once}, @code{gdbserver} option
18532 By default, @code{gdbserver} keeps the listening TCP port open, so that
18533 subsequent connections are possible. However, if you start @code{gdbserver}
18534 with the @option{--once} option, it will stop listening for any further
18535 connection attempts after connecting to the first @value{GDBN} session. This
18536 means no further connections to @code{gdbserver} will be possible after the
18537 first one. It also means @code{gdbserver} will terminate after the first
18538 connection with remote @value{GDBN} has closed, even for unexpectedly closed
18539 connections and even in the @kbd{target extended-remote} mode. The
18540 @option{--once} option allows reusing the same port number for connecting to
18541 multiple instances of @code{gdbserver} running on the same host, since each
18542 instance closes its port after the first connection.
18544 @anchor{Other Command-Line Arguments for gdbserver}
18545 @subsubsection Other Command-Line Arguments for @code{gdbserver}
18547 @cindex @option{--debug}, @code{gdbserver} option
18548 The @option{--debug} option tells @code{gdbserver} to display extra
18549 status information about the debugging process.
18550 @cindex @option{--remote-debug}, @code{gdbserver} option
18551 The @option{--remote-debug} option tells @code{gdbserver} to display
18552 remote protocol debug output. These options are intended for
18553 @code{gdbserver} development and for bug reports to the developers.
18555 @cindex @option{--debug-format}, @code{gdbserver} option
18556 The @option{--debug-format=option1[,option2,...]} option tells
18557 @code{gdbserver} to include additional information in each output.
18558 Possible options are:
18562 Turn off all extra information in debugging output.
18564 Turn on all extra information in debugging output.
18566 Include a timestamp in each line of debugging output.
18569 Options are processed in order. Thus, for example, if @option{none}
18570 appears last then no additional information is added to debugging output.
18572 @cindex @option{--wrapper}, @code{gdbserver} option
18573 The @option{--wrapper} option specifies a wrapper to launch programs
18574 for debugging. The option should be followed by the name of the
18575 wrapper, then any command-line arguments to pass to the wrapper, then
18576 @kbd{--} indicating the end of the wrapper arguments.
18578 @code{gdbserver} runs the specified wrapper program with a combined
18579 command line including the wrapper arguments, then the name of the
18580 program to debug, then any arguments to the program. The wrapper
18581 runs until it executes your program, and then @value{GDBN} gains control.
18583 You can use any program that eventually calls @code{execve} with
18584 its arguments as a wrapper. Several standard Unix utilities do
18585 this, e.g.@: @code{env} and @code{nohup}. Any Unix shell script ending
18586 with @code{exec "$@@"} will also work.
18588 For example, you can use @code{env} to pass an environment variable to
18589 the debugged program, without setting the variable in @code{gdbserver}'s
18593 $ gdbserver --wrapper env LD_PRELOAD=libtest.so -- :2222 ./testprog
18596 @subsection Connecting to @code{gdbserver}
18598 Run @value{GDBN} on the host system.
18600 First make sure you have the necessary symbol files. Load symbols for
18601 your application using the @code{file} command before you connect. Use
18602 @code{set sysroot} to locate target libraries (unless your @value{GDBN}
18603 was compiled with the correct sysroot using @code{--with-sysroot}).
18605 The symbol file and target libraries must exactly match the executable
18606 and libraries on the target, with one exception: the files on the host
18607 system should not be stripped, even if the files on the target system
18608 are. Mismatched or missing files will lead to confusing results
18609 during debugging. On @sc{gnu}/Linux targets, mismatched or missing
18610 files may also prevent @code{gdbserver} from debugging multi-threaded
18613 Connect to your target (@pxref{Connecting,,Connecting to a Remote Target}).
18614 For TCP connections, you must start up @code{gdbserver} prior to using
18615 the @code{target remote} command. Otherwise you may get an error whose
18616 text depends on the host system, but which usually looks something like
18617 @samp{Connection refused}. Don't use the @code{load}
18618 command in @value{GDBN} when using @code{gdbserver}, since the program is
18619 already on the target.
18621 @subsection Monitor Commands for @code{gdbserver}
18622 @cindex monitor commands, for @code{gdbserver}
18623 @anchor{Monitor Commands for gdbserver}
18625 During a @value{GDBN} session using @code{gdbserver}, you can use the
18626 @code{monitor} command to send special requests to @code{gdbserver}.
18627 Here are the available commands.
18631 List the available monitor commands.
18633 @item monitor set debug 0
18634 @itemx monitor set debug 1
18635 Disable or enable general debugging messages.
18637 @item monitor set remote-debug 0
18638 @itemx monitor set remote-debug 1
18639 Disable or enable specific debugging messages associated with the remote
18640 protocol (@pxref{Remote Protocol}).
18642 @item monitor set debug-format option1@r{[},option2,...@r{]}
18643 Specify additional text to add to debugging messages.
18644 Possible options are:
18648 Turn off all extra information in debugging output.
18650 Turn on all extra information in debugging output.
18652 Include a timestamp in each line of debugging output.
18655 Options are processed in order. Thus, for example, if @option{none}
18656 appears last then no additional information is added to debugging output.
18658 @item monitor set libthread-db-search-path [PATH]
18659 @cindex gdbserver, search path for @code{libthread_db}
18660 When this command is issued, @var{path} is a colon-separated list of
18661 directories to search for @code{libthread_db} (@pxref{Threads,,set
18662 libthread-db-search-path}). If you omit @var{path},
18663 @samp{libthread-db-search-path} will be reset to its default value.
18665 The special entry @samp{$pdir} for @samp{libthread-db-search-path} is
18666 not supported in @code{gdbserver}.
18669 Tell gdbserver to exit immediately. This command should be followed by
18670 @code{disconnect} to close the debugging session. @code{gdbserver} will
18671 detach from any attached processes and kill any processes it created.
18672 Use @code{monitor exit} to terminate @code{gdbserver} at the end
18673 of a multi-process mode debug session.
18677 @subsection Tracepoints support in @code{gdbserver}
18678 @cindex tracepoints support in @code{gdbserver}
18680 On some targets, @code{gdbserver} supports tracepoints, fast
18681 tracepoints and static tracepoints.
18683 For fast or static tracepoints to work, a special library called the
18684 @dfn{in-process agent} (IPA), must be loaded in the inferior process.
18685 This library is built and distributed as an integral part of
18686 @code{gdbserver}. In addition, support for static tracepoints
18687 requires building the in-process agent library with static tracepoints
18688 support. At present, the UST (LTTng Userspace Tracer,
18689 @url{http://lttng.org/ust}) tracing engine is supported. This support
18690 is automatically available if UST development headers are found in the
18691 standard include path when @code{gdbserver} is built, or if
18692 @code{gdbserver} was explicitly configured using @option{--with-ust}
18693 to point at such headers. You can explicitly disable the support
18694 using @option{--with-ust=no}.
18696 There are several ways to load the in-process agent in your program:
18699 @item Specifying it as dependency at link time
18701 You can link your program dynamically with the in-process agent
18702 library. On most systems, this is accomplished by adding
18703 @code{-linproctrace} to the link command.
18705 @item Using the system's preloading mechanisms
18707 You can force loading the in-process agent at startup time by using
18708 your system's support for preloading shared libraries. Many Unixes
18709 support the concept of preloading user defined libraries. In most
18710 cases, you do that by specifying @code{LD_PRELOAD=libinproctrace.so}
18711 in the environment. See also the description of @code{gdbserver}'s
18712 @option{--wrapper} command line option.
18714 @item Using @value{GDBN} to force loading the agent at run time
18716 On some systems, you can force the inferior to load a shared library,
18717 by calling a dynamic loader function in the inferior that takes care
18718 of dynamically looking up and loading a shared library. On most Unix
18719 systems, the function is @code{dlopen}. You'll use the @code{call}
18720 command for that. For example:
18723 (@value{GDBP}) call dlopen ("libinproctrace.so", ...)
18726 Note that on most Unix systems, for the @code{dlopen} function to be
18727 available, the program needs to be linked with @code{-ldl}.
18730 On systems that have a userspace dynamic loader, like most Unix
18731 systems, when you connect to @code{gdbserver} using @code{target
18732 remote}, you'll find that the program is stopped at the dynamic
18733 loader's entry point, and no shared library has been loaded in the
18734 program's address space yet, including the in-process agent. In that
18735 case, before being able to use any of the fast or static tracepoints
18736 features, you need to let the loader run and load the shared
18737 libraries. The simplest way to do that is to run the program to the
18738 main procedure. E.g., if debugging a C or C@t{++} program, start
18739 @code{gdbserver} like so:
18742 $ gdbserver :9999 myprogram
18745 Start GDB and connect to @code{gdbserver} like so, and run to main:
18749 (@value{GDBP}) target remote myhost:9999
18750 0x00007f215893ba60 in ?? () from /lib64/ld-linux-x86-64.so.2
18751 (@value{GDBP}) b main
18752 (@value{GDBP}) continue
18755 The in-process tracing agent library should now be loaded into the
18756 process; you can confirm it with the @code{info sharedlibrary}
18757 command, which will list @file{libinproctrace.so} as loaded in the
18758 process. You are now ready to install fast tracepoints, list static
18759 tracepoint markers, probe static tracepoints markers, and start
18762 @node Remote Configuration
18763 @section Remote Configuration
18766 @kindex show remote
18767 This section documents the configuration options available when
18768 debugging remote programs. For the options related to the File I/O
18769 extensions of the remote protocol, see @ref{system,
18770 system-call-allowed}.
18773 @item set remoteaddresssize @var{bits}
18774 @cindex address size for remote targets
18775 @cindex bits in remote address
18776 Set the maximum size of address in a memory packet to the specified
18777 number of bits. @value{GDBN} will mask off the address bits above
18778 that number, when it passes addresses to the remote target. The
18779 default value is the number of bits in the target's address.
18781 @item show remoteaddresssize
18782 Show the current value of remote address size in bits.
18784 @item set serial baud @var{n}
18785 @cindex baud rate for remote targets
18786 Set the baud rate for the remote serial I/O to @var{n} baud. The
18787 value is used to set the speed of the serial port used for debugging
18790 @item show serial baud
18791 Show the current speed of the remote connection.
18793 @item set remotebreak
18794 @cindex interrupt remote programs
18795 @cindex BREAK signal instead of Ctrl-C
18796 @anchor{set remotebreak}
18797 If set to on, @value{GDBN} sends a @code{BREAK} signal to the remote
18798 when you type @kbd{Ctrl-c} to interrupt the program running
18799 on the remote. If set to off, @value{GDBN} sends the @samp{Ctrl-C}
18800 character instead. The default is off, since most remote systems
18801 expect to see @samp{Ctrl-C} as the interrupt signal.
18803 @item show remotebreak
18804 Show whether @value{GDBN} sends @code{BREAK} or @samp{Ctrl-C} to
18805 interrupt the remote program.
18807 @item set remoteflow on
18808 @itemx set remoteflow off
18809 @kindex set remoteflow
18810 Enable or disable hardware flow control (@code{RTS}/@code{CTS})
18811 on the serial port used to communicate to the remote target.
18813 @item show remoteflow
18814 @kindex show remoteflow
18815 Show the current setting of hardware flow control.
18817 @item set remotelogbase @var{base}
18818 Set the base (a.k.a.@: radix) of logging serial protocol
18819 communications to @var{base}. Supported values of @var{base} are:
18820 @code{ascii}, @code{octal}, and @code{hex}. The default is
18823 @item show remotelogbase
18824 Show the current setting of the radix for logging remote serial
18827 @item set remotelogfile @var{file}
18828 @cindex record serial communications on file
18829 Record remote serial communications on the named @var{file}. The
18830 default is not to record at all.
18832 @item show remotelogfile.
18833 Show the current setting of the file name on which to record the
18834 serial communications.
18836 @item set remotetimeout @var{num}
18837 @cindex timeout for serial communications
18838 @cindex remote timeout
18839 Set the timeout limit to wait for the remote target to respond to
18840 @var{num} seconds. The default is 2 seconds.
18842 @item show remotetimeout
18843 Show the current number of seconds to wait for the remote target
18846 @cindex limit hardware breakpoints and watchpoints
18847 @cindex remote target, limit break- and watchpoints
18848 @anchor{set remote hardware-watchpoint-limit}
18849 @anchor{set remote hardware-breakpoint-limit}
18850 @item set remote hardware-watchpoint-limit @var{limit}
18851 @itemx set remote hardware-breakpoint-limit @var{limit}
18852 Restrict @value{GDBN} to using @var{limit} remote hardware breakpoint or
18853 watchpoints. A limit of -1, the default, is treated as unlimited.
18855 @cindex limit hardware watchpoints length
18856 @cindex remote target, limit watchpoints length
18857 @anchor{set remote hardware-watchpoint-length-limit}
18858 @item set remote hardware-watchpoint-length-limit @var{limit}
18859 Restrict @value{GDBN} to using @var{limit} bytes for the maximum length of
18860 a remote hardware watchpoint. A limit of -1, the default, is treated
18863 @item show remote hardware-watchpoint-length-limit
18864 Show the current limit (in bytes) of the maximum length of
18865 a remote hardware watchpoint.
18867 @item set remote exec-file @var{filename}
18868 @itemx show remote exec-file
18869 @anchor{set remote exec-file}
18870 @cindex executable file, for remote target
18871 Select the file used for @code{run} with @code{target
18872 extended-remote}. This should be set to a filename valid on the
18873 target system. If it is not set, the target will use a default
18874 filename (e.g.@: the last program run).
18876 @item set remote interrupt-sequence
18877 @cindex interrupt remote programs
18878 @cindex select Ctrl-C, BREAK or BREAK-g
18879 Allow the user to select one of @samp{Ctrl-C}, a @code{BREAK} or
18880 @samp{BREAK-g} as the
18881 sequence to the remote target in order to interrupt the execution.
18882 @samp{Ctrl-C} is a default. Some system prefers @code{BREAK} which
18883 is high level of serial line for some certain time.
18884 Linux kernel prefers @samp{BREAK-g}, a.k.a Magic SysRq g.
18885 It is @code{BREAK} signal followed by character @code{g}.
18887 @item show interrupt-sequence
18888 Show which of @samp{Ctrl-C}, @code{BREAK} or @code{BREAK-g}
18889 is sent by @value{GDBN} to interrupt the remote program.
18890 @code{BREAK-g} is BREAK signal followed by @code{g} and
18891 also known as Magic SysRq g.
18893 @item set remote interrupt-on-connect
18894 @cindex send interrupt-sequence on start
18895 Specify whether interrupt-sequence is sent to remote target when
18896 @value{GDBN} connects to it. This is mostly needed when you debug
18897 Linux kernel. Linux kernel expects @code{BREAK} followed by @code{g}
18898 which is known as Magic SysRq g in order to connect @value{GDBN}.
18900 @item show interrupt-on-connect
18901 Show whether interrupt-sequence is sent
18902 to remote target when @value{GDBN} connects to it.
18906 @item set tcp auto-retry on
18907 @cindex auto-retry, for remote TCP target
18908 Enable auto-retry for remote TCP connections. This is useful if the remote
18909 debugging agent is launched in parallel with @value{GDBN}; there is a race
18910 condition because the agent may not become ready to accept the connection
18911 before @value{GDBN} attempts to connect. When auto-retry is
18912 enabled, if the initial attempt to connect fails, @value{GDBN} reattempts
18913 to establish the connection using the timeout specified by
18914 @code{set tcp connect-timeout}.
18916 @item set tcp auto-retry off
18917 Do not auto-retry failed TCP connections.
18919 @item show tcp auto-retry
18920 Show the current auto-retry setting.
18922 @item set tcp connect-timeout @var{seconds}
18923 @itemx set tcp connect-timeout unlimited
18924 @cindex connection timeout, for remote TCP target
18925 @cindex timeout, for remote target connection
18926 Set the timeout for establishing a TCP connection to the remote target to
18927 @var{seconds}. The timeout affects both polling to retry failed connections
18928 (enabled by @code{set tcp auto-retry on}) and waiting for connections
18929 that are merely slow to complete, and represents an approximate cumulative
18930 value. If @var{seconds} is @code{unlimited}, there is no timeout and
18931 @value{GDBN} will keep attempting to establish a connection forever,
18932 unless interrupted with @kbd{Ctrl-c}. The default is 15 seconds.
18934 @item show tcp connect-timeout
18935 Show the current connection timeout setting.
18938 @cindex remote packets, enabling and disabling
18939 The @value{GDBN} remote protocol autodetects the packets supported by
18940 your debugging stub. If you need to override the autodetection, you
18941 can use these commands to enable or disable individual packets. Each
18942 packet can be set to @samp{on} (the remote target supports this
18943 packet), @samp{off} (the remote target does not support this packet),
18944 or @samp{auto} (detect remote target support for this packet). They
18945 all default to @samp{auto}. For more information about each packet,
18946 see @ref{Remote Protocol}.
18948 During normal use, you should not have to use any of these commands.
18949 If you do, that may be a bug in your remote debugging stub, or a bug
18950 in @value{GDBN}. You may want to report the problem to the
18951 @value{GDBN} developers.
18953 For each packet @var{name}, the command to enable or disable the
18954 packet is @code{set remote @var{name}-packet}. The available settings
18957 @multitable @columnfractions 0.28 0.32 0.25
18960 @tab Related Features
18962 @item @code{fetch-register}
18964 @tab @code{info registers}
18966 @item @code{set-register}
18970 @item @code{binary-download}
18972 @tab @code{load}, @code{set}
18974 @item @code{read-aux-vector}
18975 @tab @code{qXfer:auxv:read}
18976 @tab @code{info auxv}
18978 @item @code{symbol-lookup}
18979 @tab @code{qSymbol}
18980 @tab Detecting multiple threads
18982 @item @code{attach}
18983 @tab @code{vAttach}
18986 @item @code{verbose-resume}
18988 @tab Stepping or resuming multiple threads
18994 @item @code{software-breakpoint}
18998 @item @code{hardware-breakpoint}
19002 @item @code{write-watchpoint}
19006 @item @code{read-watchpoint}
19010 @item @code{access-watchpoint}
19014 @item @code{target-features}
19015 @tab @code{qXfer:features:read}
19016 @tab @code{set architecture}
19018 @item @code{library-info}
19019 @tab @code{qXfer:libraries:read}
19020 @tab @code{info sharedlibrary}
19022 @item @code{memory-map}
19023 @tab @code{qXfer:memory-map:read}
19024 @tab @code{info mem}
19026 @item @code{read-sdata-object}
19027 @tab @code{qXfer:sdata:read}
19028 @tab @code{print $_sdata}
19030 @item @code{read-spu-object}
19031 @tab @code{qXfer:spu:read}
19032 @tab @code{info spu}
19034 @item @code{write-spu-object}
19035 @tab @code{qXfer:spu:write}
19036 @tab @code{info spu}
19038 @item @code{read-siginfo-object}
19039 @tab @code{qXfer:siginfo:read}
19040 @tab @code{print $_siginfo}
19042 @item @code{write-siginfo-object}
19043 @tab @code{qXfer:siginfo:write}
19044 @tab @code{set $_siginfo}
19046 @item @code{threads}
19047 @tab @code{qXfer:threads:read}
19048 @tab @code{info threads}
19050 @item @code{get-thread-local-@*storage-address}
19051 @tab @code{qGetTLSAddr}
19052 @tab Displaying @code{__thread} variables
19054 @item @code{get-thread-information-block-address}
19055 @tab @code{qGetTIBAddr}
19056 @tab Display MS-Windows Thread Information Block.
19058 @item @code{search-memory}
19059 @tab @code{qSearch:memory}
19062 @item @code{supported-packets}
19063 @tab @code{qSupported}
19064 @tab Remote communications parameters
19066 @item @code{pass-signals}
19067 @tab @code{QPassSignals}
19068 @tab @code{handle @var{signal}}
19070 @item @code{program-signals}
19071 @tab @code{QProgramSignals}
19072 @tab @code{handle @var{signal}}
19074 @item @code{hostio-close-packet}
19075 @tab @code{vFile:close}
19076 @tab @code{remote get}, @code{remote put}
19078 @item @code{hostio-open-packet}
19079 @tab @code{vFile:open}
19080 @tab @code{remote get}, @code{remote put}
19082 @item @code{hostio-pread-packet}
19083 @tab @code{vFile:pread}
19084 @tab @code{remote get}, @code{remote put}
19086 @item @code{hostio-pwrite-packet}
19087 @tab @code{vFile:pwrite}
19088 @tab @code{remote get}, @code{remote put}
19090 @item @code{hostio-unlink-packet}
19091 @tab @code{vFile:unlink}
19092 @tab @code{remote delete}
19094 @item @code{hostio-readlink-packet}
19095 @tab @code{vFile:readlink}
19098 @item @code{noack-packet}
19099 @tab @code{QStartNoAckMode}
19100 @tab Packet acknowledgment
19102 @item @code{osdata}
19103 @tab @code{qXfer:osdata:read}
19104 @tab @code{info os}
19106 @item @code{query-attached}
19107 @tab @code{qAttached}
19108 @tab Querying remote process attach state.
19110 @item @code{trace-buffer-size}
19111 @tab @code{QTBuffer:size}
19112 @tab @code{set trace-buffer-size}
19114 @item @code{trace-status}
19115 @tab @code{qTStatus}
19116 @tab @code{tstatus}
19118 @item @code{traceframe-info}
19119 @tab @code{qXfer:traceframe-info:read}
19120 @tab Traceframe info
19122 @item @code{install-in-trace}
19123 @tab @code{InstallInTrace}
19124 @tab Install tracepoint in tracing
19126 @item @code{disable-randomization}
19127 @tab @code{QDisableRandomization}
19128 @tab @code{set disable-randomization}
19130 @item @code{conditional-breakpoints-packet}
19131 @tab @code{Z0 and Z1}
19132 @tab @code{Support for target-side breakpoint condition evaluation}
19136 @section Implementing a Remote Stub
19138 @cindex debugging stub, example
19139 @cindex remote stub, example
19140 @cindex stub example, remote debugging
19141 The stub files provided with @value{GDBN} implement the target side of the
19142 communication protocol, and the @value{GDBN} side is implemented in the
19143 @value{GDBN} source file @file{remote.c}. Normally, you can simply allow
19144 these subroutines to communicate, and ignore the details. (If you're
19145 implementing your own stub file, you can still ignore the details: start
19146 with one of the existing stub files. @file{sparc-stub.c} is the best
19147 organized, and therefore the easiest to read.)
19149 @cindex remote serial debugging, overview
19150 To debug a program running on another machine (the debugging
19151 @dfn{target} machine), you must first arrange for all the usual
19152 prerequisites for the program to run by itself. For example, for a C
19157 A startup routine to set up the C runtime environment; these usually
19158 have a name like @file{crt0}. The startup routine may be supplied by
19159 your hardware supplier, or you may have to write your own.
19162 A C subroutine library to support your program's
19163 subroutine calls, notably managing input and output.
19166 A way of getting your program to the other machine---for example, a
19167 download program. These are often supplied by the hardware
19168 manufacturer, but you may have to write your own from hardware
19172 The next step is to arrange for your program to use a serial port to
19173 communicate with the machine where @value{GDBN} is running (the @dfn{host}
19174 machine). In general terms, the scheme looks like this:
19178 @value{GDBN} already understands how to use this protocol; when everything
19179 else is set up, you can simply use the @samp{target remote} command
19180 (@pxref{Targets,,Specifying a Debugging Target}).
19182 @item On the target,
19183 you must link with your program a few special-purpose subroutines that
19184 implement the @value{GDBN} remote serial protocol. The file containing these
19185 subroutines is called a @dfn{debugging stub}.
19187 On certain remote targets, you can use an auxiliary program
19188 @code{gdbserver} instead of linking a stub into your program.
19189 @xref{Server,,Using the @code{gdbserver} Program}, for details.
19192 The debugging stub is specific to the architecture of the remote
19193 machine; for example, use @file{sparc-stub.c} to debug programs on
19196 @cindex remote serial stub list
19197 These working remote stubs are distributed with @value{GDBN}:
19202 @cindex @file{i386-stub.c}
19205 For Intel 386 and compatible architectures.
19208 @cindex @file{m68k-stub.c}
19209 @cindex Motorola 680x0
19211 For Motorola 680x0 architectures.
19214 @cindex @file{sh-stub.c}
19217 For Renesas SH architectures.
19220 @cindex @file{sparc-stub.c}
19222 For @sc{sparc} architectures.
19224 @item sparcl-stub.c
19225 @cindex @file{sparcl-stub.c}
19228 For Fujitsu @sc{sparclite} architectures.
19232 The @file{README} file in the @value{GDBN} distribution may list other
19233 recently added stubs.
19236 * Stub Contents:: What the stub can do for you
19237 * Bootstrapping:: What you must do for the stub
19238 * Debug Session:: Putting it all together
19241 @node Stub Contents
19242 @subsection What the Stub Can Do for You
19244 @cindex remote serial stub
19245 The debugging stub for your architecture supplies these three
19249 @item set_debug_traps
19250 @findex set_debug_traps
19251 @cindex remote serial stub, initialization
19252 This routine arranges for @code{handle_exception} to run when your
19253 program stops. You must call this subroutine explicitly in your
19254 program's startup code.
19256 @item handle_exception
19257 @findex handle_exception
19258 @cindex remote serial stub, main routine
19259 This is the central workhorse, but your program never calls it
19260 explicitly---the setup code arranges for @code{handle_exception} to
19261 run when a trap is triggered.
19263 @code{handle_exception} takes control when your program stops during
19264 execution (for example, on a breakpoint), and mediates communications
19265 with @value{GDBN} on the host machine. This is where the communications
19266 protocol is implemented; @code{handle_exception} acts as the @value{GDBN}
19267 representative on the target machine. It begins by sending summary
19268 information on the state of your program, then continues to execute,
19269 retrieving and transmitting any information @value{GDBN} needs, until you
19270 execute a @value{GDBN} command that makes your program resume; at that point,
19271 @code{handle_exception} returns control to your own code on the target
19275 @cindex @code{breakpoint} subroutine, remote
19276 Use this auxiliary subroutine to make your program contain a
19277 breakpoint. Depending on the particular situation, this may be the only
19278 way for @value{GDBN} to get control. For instance, if your target
19279 machine has some sort of interrupt button, you won't need to call this;
19280 pressing the interrupt button transfers control to
19281 @code{handle_exception}---in effect, to @value{GDBN}. On some machines,
19282 simply receiving characters on the serial port may also trigger a trap;
19283 again, in that situation, you don't need to call @code{breakpoint} from
19284 your own program---simply running @samp{target remote} from the host
19285 @value{GDBN} session gets control.
19287 Call @code{breakpoint} if none of these is true, or if you simply want
19288 to make certain your program stops at a predetermined point for the
19289 start of your debugging session.
19292 @node Bootstrapping
19293 @subsection What You Must Do for the Stub
19295 @cindex remote stub, support routines
19296 The debugging stubs that come with @value{GDBN} are set up for a particular
19297 chip architecture, but they have no information about the rest of your
19298 debugging target machine.
19300 First of all you need to tell the stub how to communicate with the
19304 @item int getDebugChar()
19305 @findex getDebugChar
19306 Write this subroutine to read a single character from the serial port.
19307 It may be identical to @code{getchar} for your target system; a
19308 different name is used to allow you to distinguish the two if you wish.
19310 @item void putDebugChar(int)
19311 @findex putDebugChar
19312 Write this subroutine to write a single character to the serial port.
19313 It may be identical to @code{putchar} for your target system; a
19314 different name is used to allow you to distinguish the two if you wish.
19317 @cindex control C, and remote debugging
19318 @cindex interrupting remote targets
19319 If you want @value{GDBN} to be able to stop your program while it is
19320 running, you need to use an interrupt-driven serial driver, and arrange
19321 for it to stop when it receives a @code{^C} (@samp{\003}, the control-C
19322 character). That is the character which @value{GDBN} uses to tell the
19323 remote system to stop.
19325 Getting the debugging target to return the proper status to @value{GDBN}
19326 probably requires changes to the standard stub; one quick and dirty way
19327 is to just execute a breakpoint instruction (the ``dirty'' part is that
19328 @value{GDBN} reports a @code{SIGTRAP} instead of a @code{SIGINT}).
19330 Other routines you need to supply are:
19333 @item void exceptionHandler (int @var{exception_number}, void *@var{exception_address})
19334 @findex exceptionHandler
19335 Write this function to install @var{exception_address} in the exception
19336 handling tables. You need to do this because the stub does not have any
19337 way of knowing what the exception handling tables on your target system
19338 are like (for example, the processor's table might be in @sc{rom},
19339 containing entries which point to a table in @sc{ram}).
19340 @var{exception_number} is the exception number which should be changed;
19341 its meaning is architecture-dependent (for example, different numbers
19342 might represent divide by zero, misaligned access, etc). When this
19343 exception occurs, control should be transferred directly to
19344 @var{exception_address}, and the processor state (stack, registers,
19345 and so on) should be just as it is when a processor exception occurs. So if
19346 you want to use a jump instruction to reach @var{exception_address}, it
19347 should be a simple jump, not a jump to subroutine.
19349 For the 386, @var{exception_address} should be installed as an interrupt
19350 gate so that interrupts are masked while the handler runs. The gate
19351 should be at privilege level 0 (the most privileged level). The
19352 @sc{sparc} and 68k stubs are able to mask interrupts themselves without
19353 help from @code{exceptionHandler}.
19355 @item void flush_i_cache()
19356 @findex flush_i_cache
19357 On @sc{sparc} and @sc{sparclite} only, write this subroutine to flush the
19358 instruction cache, if any, on your target machine. If there is no
19359 instruction cache, this subroutine may be a no-op.
19361 On target machines that have instruction caches, @value{GDBN} requires this
19362 function to make certain that the state of your program is stable.
19366 You must also make sure this library routine is available:
19369 @item void *memset(void *, int, int)
19371 This is the standard library function @code{memset} that sets an area of
19372 memory to a known value. If you have one of the free versions of
19373 @code{libc.a}, @code{memset} can be found there; otherwise, you must
19374 either obtain it from your hardware manufacturer, or write your own.
19377 If you do not use the GNU C compiler, you may need other standard
19378 library subroutines as well; this varies from one stub to another,
19379 but in general the stubs are likely to use any of the common library
19380 subroutines which @code{@value{NGCC}} generates as inline code.
19383 @node Debug Session
19384 @subsection Putting it All Together
19386 @cindex remote serial debugging summary
19387 In summary, when your program is ready to debug, you must follow these
19392 Make sure you have defined the supporting low-level routines
19393 (@pxref{Bootstrapping,,What You Must Do for the Stub}):
19395 @code{getDebugChar}, @code{putDebugChar},
19396 @code{flush_i_cache}, @code{memset}, @code{exceptionHandler}.
19400 Insert these lines in your program's startup code, before the main
19401 procedure is called:
19408 On some machines, when a breakpoint trap is raised, the hardware
19409 automatically makes the PC point to the instruction after the
19410 breakpoint. If your machine doesn't do that, you may need to adjust
19411 @code{handle_exception} to arrange for it to return to the instruction
19412 after the breakpoint on this first invocation, so that your program
19413 doesn't keep hitting the initial breakpoint instead of making
19417 For the 680x0 stub only, you need to provide a variable called
19418 @code{exceptionHook}. Normally you just use:
19421 void (*exceptionHook)() = 0;
19425 but if before calling @code{set_debug_traps}, you set it to point to a
19426 function in your program, that function is called when
19427 @code{@value{GDBN}} continues after stopping on a trap (for example, bus
19428 error). The function indicated by @code{exceptionHook} is called with
19429 one parameter: an @code{int} which is the exception number.
19432 Compile and link together: your program, the @value{GDBN} debugging stub for
19433 your target architecture, and the supporting subroutines.
19436 Make sure you have a serial connection between your target machine and
19437 the @value{GDBN} host, and identify the serial port on the host.
19440 @c The "remote" target now provides a `load' command, so we should
19441 @c document that. FIXME.
19442 Download your program to your target machine (or get it there by
19443 whatever means the manufacturer provides), and start it.
19446 Start @value{GDBN} on the host, and connect to the target
19447 (@pxref{Connecting,,Connecting to a Remote Target}).
19451 @node Configurations
19452 @chapter Configuration-Specific Information
19454 While nearly all @value{GDBN} commands are available for all native and
19455 cross versions of the debugger, there are some exceptions. This chapter
19456 describes things that are only available in certain configurations.
19458 There are three major categories of configurations: native
19459 configurations, where the host and target are the same, embedded
19460 operating system configurations, which are usually the same for several
19461 different processor architectures, and bare embedded processors, which
19462 are quite different from each other.
19467 * Embedded Processors::
19474 This section describes details specific to particular native
19479 * BSD libkvm Interface:: Debugging BSD kernel memory images
19480 * SVR4 Process Information:: SVR4 process information
19481 * DJGPP Native:: Features specific to the DJGPP port
19482 * Cygwin Native:: Features specific to the Cygwin port
19483 * Hurd Native:: Features specific to @sc{gnu} Hurd
19484 * Darwin:: Features specific to Darwin
19490 On HP-UX systems, if you refer to a function or variable name that
19491 begins with a dollar sign, @value{GDBN} searches for a user or system
19492 name first, before it searches for a convenience variable.
19495 @node BSD libkvm Interface
19496 @subsection BSD libkvm Interface
19499 @cindex kernel memory image
19500 @cindex kernel crash dump
19502 BSD-derived systems (FreeBSD/NetBSD/OpenBSD) have a kernel memory
19503 interface that provides a uniform interface for accessing kernel virtual
19504 memory images, including live systems and crash dumps. @value{GDBN}
19505 uses this interface to allow you to debug live kernels and kernel crash
19506 dumps on many native BSD configurations. This is implemented as a
19507 special @code{kvm} debugging target. For debugging a live system, load
19508 the currently running kernel into @value{GDBN} and connect to the
19512 (@value{GDBP}) @b{target kvm}
19515 For debugging crash dumps, provide the file name of the crash dump as an
19519 (@value{GDBP}) @b{target kvm /var/crash/bsd.0}
19522 Once connected to the @code{kvm} target, the following commands are
19528 Set current context from the @dfn{Process Control Block} (PCB) address.
19531 Set current context from proc address. This command isn't available on
19532 modern FreeBSD systems.
19535 @node SVR4 Process Information
19536 @subsection SVR4 Process Information
19538 @cindex examine process image
19539 @cindex process info via @file{/proc}
19541 Many versions of SVR4 and compatible systems provide a facility called
19542 @samp{/proc} that can be used to examine the image of a running
19543 process using file-system subroutines.
19545 If @value{GDBN} is configured for an operating system with this
19546 facility, the command @code{info proc} is available to report
19547 information about the process running your program, or about any
19548 process running on your system. This includes, as of this writing,
19549 @sc{gnu}/Linux, OSF/1 (Digital Unix), Solaris, and Irix, but
19550 not HP-UX, for example.
19552 This command may also work on core files that were created on a system
19553 that has the @samp{/proc} facility.
19559 @itemx info proc @var{process-id}
19560 Summarize available information about any running process. If a
19561 process ID is specified by @var{process-id}, display information about
19562 that process; otherwise display information about the program being
19563 debugged. The summary includes the debugged process ID, the command
19564 line used to invoke it, its current working directory, and its
19565 executable file's absolute file name.
19567 On some systems, @var{process-id} can be of the form
19568 @samp{[@var{pid}]/@var{tid}} which specifies a certain thread ID
19569 within a process. If the optional @var{pid} part is missing, it means
19570 a thread from the process being debugged (the leading @samp{/} still
19571 needs to be present, or else @value{GDBN} will interpret the number as
19572 a process ID rather than a thread ID).
19574 @item info proc cmdline
19575 @cindex info proc cmdline
19576 Show the original command line of the process. This command is
19577 specific to @sc{gnu}/Linux.
19579 @item info proc cwd
19580 @cindex info proc cwd
19581 Show the current working directory of the process. This command is
19582 specific to @sc{gnu}/Linux.
19584 @item info proc exe
19585 @cindex info proc exe
19586 Show the name of executable of the process. This command is specific
19589 @item info proc mappings
19590 @cindex memory address space mappings
19591 Report the memory address space ranges accessible in the program, with
19592 information on whether the process has read, write, or execute access
19593 rights to each range. On @sc{gnu}/Linux systems, each memory range
19594 includes the object file which is mapped to that range, instead of the
19595 memory access rights to that range.
19597 @item info proc stat
19598 @itemx info proc status
19599 @cindex process detailed status information
19600 These subcommands are specific to @sc{gnu}/Linux systems. They show
19601 the process-related information, including the user ID and group ID;
19602 how many threads are there in the process; its virtual memory usage;
19603 the signals that are pending, blocked, and ignored; its TTY; its
19604 consumption of system and user time; its stack size; its @samp{nice}
19605 value; etc. For more information, see the @samp{proc} man page
19606 (type @kbd{man 5 proc} from your shell prompt).
19608 @item info proc all
19609 Show all the information about the process described under all of the
19610 above @code{info proc} subcommands.
19613 @comment These sub-options of 'info proc' were not included when
19614 @comment procfs.c was re-written. Keep their descriptions around
19615 @comment against the day when someone finds the time to put them back in.
19616 @kindex info proc times
19617 @item info proc times
19618 Starting time, user CPU time, and system CPU time for your program and
19621 @kindex info proc id
19623 Report on the process IDs related to your program: its own process ID,
19624 the ID of its parent, the process group ID, and the session ID.
19627 @item set procfs-trace
19628 @kindex set procfs-trace
19629 @cindex @code{procfs} API calls
19630 This command enables and disables tracing of @code{procfs} API calls.
19632 @item show procfs-trace
19633 @kindex show procfs-trace
19634 Show the current state of @code{procfs} API call tracing.
19636 @item set procfs-file @var{file}
19637 @kindex set procfs-file
19638 Tell @value{GDBN} to write @code{procfs} API trace to the named
19639 @var{file}. @value{GDBN} appends the trace info to the previous
19640 contents of the file. The default is to display the trace on the
19643 @item show procfs-file
19644 @kindex show procfs-file
19645 Show the file to which @code{procfs} API trace is written.
19647 @item proc-trace-entry
19648 @itemx proc-trace-exit
19649 @itemx proc-untrace-entry
19650 @itemx proc-untrace-exit
19651 @kindex proc-trace-entry
19652 @kindex proc-trace-exit
19653 @kindex proc-untrace-entry
19654 @kindex proc-untrace-exit
19655 These commands enable and disable tracing of entries into and exits
19656 from the @code{syscall} interface.
19659 @kindex info pidlist
19660 @cindex process list, QNX Neutrino
19661 For QNX Neutrino only, this command displays the list of all the
19662 processes and all the threads within each process.
19665 @kindex info meminfo
19666 @cindex mapinfo list, QNX Neutrino
19667 For QNX Neutrino only, this command displays the list of all mapinfos.
19671 @subsection Features for Debugging @sc{djgpp} Programs
19672 @cindex @sc{djgpp} debugging
19673 @cindex native @sc{djgpp} debugging
19674 @cindex MS-DOS-specific commands
19677 @sc{djgpp} is a port of the @sc{gnu} development tools to MS-DOS and
19678 MS-Windows. @sc{djgpp} programs are 32-bit protected-mode programs
19679 that use the @dfn{DPMI} (DOS Protected-Mode Interface) API to run on
19680 top of real-mode DOS systems and their emulations.
19682 @value{GDBN} supports native debugging of @sc{djgpp} programs, and
19683 defines a few commands specific to the @sc{djgpp} port. This
19684 subsection describes those commands.
19689 This is a prefix of @sc{djgpp}-specific commands which print
19690 information about the target system and important OS structures.
19693 @cindex MS-DOS system info
19694 @cindex free memory information (MS-DOS)
19695 @item info dos sysinfo
19696 This command displays assorted information about the underlying
19697 platform: the CPU type and features, the OS version and flavor, the
19698 DPMI version, and the available conventional and DPMI memory.
19703 @cindex segment descriptor tables
19704 @cindex descriptor tables display
19706 @itemx info dos ldt
19707 @itemx info dos idt
19708 These 3 commands display entries from, respectively, Global, Local,
19709 and Interrupt Descriptor Tables (GDT, LDT, and IDT). The descriptor
19710 tables are data structures which store a descriptor for each segment
19711 that is currently in use. The segment's selector is an index into a
19712 descriptor table; the table entry for that index holds the
19713 descriptor's base address and limit, and its attributes and access
19716 A typical @sc{djgpp} program uses 3 segments: a code segment, a data
19717 segment (used for both data and the stack), and a DOS segment (which
19718 allows access to DOS/BIOS data structures and absolute addresses in
19719 conventional memory). However, the DPMI host will usually define
19720 additional segments in order to support the DPMI environment.
19722 @cindex garbled pointers
19723 These commands allow to display entries from the descriptor tables.
19724 Without an argument, all entries from the specified table are
19725 displayed. An argument, which should be an integer expression, means
19726 display a single entry whose index is given by the argument. For
19727 example, here's a convenient way to display information about the
19728 debugged program's data segment:
19731 @exdent @code{(@value{GDBP}) info dos ldt $ds}
19732 @exdent @code{0x13f: base=0x11970000 limit=0x0009ffff 32-Bit Data (Read/Write, Exp-up)}
19736 This comes in handy when you want to see whether a pointer is outside
19737 the data segment's limit (i.e.@: @dfn{garbled}).
19739 @cindex page tables display (MS-DOS)
19741 @itemx info dos pte
19742 These two commands display entries from, respectively, the Page
19743 Directory and the Page Tables. Page Directories and Page Tables are
19744 data structures which control how virtual memory addresses are mapped
19745 into physical addresses. A Page Table includes an entry for every
19746 page of memory that is mapped into the program's address space; there
19747 may be several Page Tables, each one holding up to 4096 entries. A
19748 Page Directory has up to 4096 entries, one each for every Page Table
19749 that is currently in use.
19751 Without an argument, @kbd{info dos pde} displays the entire Page
19752 Directory, and @kbd{info dos pte} displays all the entries in all of
19753 the Page Tables. An argument, an integer expression, given to the
19754 @kbd{info dos pde} command means display only that entry from the Page
19755 Directory table. An argument given to the @kbd{info dos pte} command
19756 means display entries from a single Page Table, the one pointed to by
19757 the specified entry in the Page Directory.
19759 @cindex direct memory access (DMA) on MS-DOS
19760 These commands are useful when your program uses @dfn{DMA} (Direct
19761 Memory Access), which needs physical addresses to program the DMA
19764 These commands are supported only with some DPMI servers.
19766 @cindex physical address from linear address
19767 @item info dos address-pte @var{addr}
19768 This command displays the Page Table entry for a specified linear
19769 address. The argument @var{addr} is a linear address which should
19770 already have the appropriate segment's base address added to it,
19771 because this command accepts addresses which may belong to @emph{any}
19772 segment. For example, here's how to display the Page Table entry for
19773 the page where a variable @code{i} is stored:
19776 @exdent @code{(@value{GDBP}) info dos address-pte __djgpp_base_address + (char *)&i}
19777 @exdent @code{Page Table entry for address 0x11a00d30:}
19778 @exdent @code{Base=0x02698000 Dirty Acc. Not-Cached Write-Back Usr Read-Write +0xd30}
19782 This says that @code{i} is stored at offset @code{0xd30} from the page
19783 whose physical base address is @code{0x02698000}, and shows all the
19784 attributes of that page.
19786 Note that you must cast the addresses of variables to a @code{char *},
19787 since otherwise the value of @code{__djgpp_base_address}, the base
19788 address of all variables and functions in a @sc{djgpp} program, will
19789 be added using the rules of C pointer arithmetics: if @code{i} is
19790 declared an @code{int}, @value{GDBN} will add 4 times the value of
19791 @code{__djgpp_base_address} to the address of @code{i}.
19793 Here's another example, it displays the Page Table entry for the
19797 @exdent @code{(@value{GDBP}) info dos address-pte *((unsigned *)&_go32_info_block + 3)}
19798 @exdent @code{Page Table entry for address 0x29110:}
19799 @exdent @code{Base=0x00029000 Dirty Acc. Not-Cached Write-Back Usr Read-Write +0x110}
19803 (The @code{+ 3} offset is because the transfer buffer's address is the
19804 3rd member of the @code{_go32_info_block} structure.) The output
19805 clearly shows that this DPMI server maps the addresses in conventional
19806 memory 1:1, i.e.@: the physical (@code{0x00029000} + @code{0x110}) and
19807 linear (@code{0x29110}) addresses are identical.
19809 This command is supported only with some DPMI servers.
19812 @cindex DOS serial data link, remote debugging
19813 In addition to native debugging, the DJGPP port supports remote
19814 debugging via a serial data link. The following commands are specific
19815 to remote serial debugging in the DJGPP port of @value{GDBN}.
19818 @kindex set com1base
19819 @kindex set com1irq
19820 @kindex set com2base
19821 @kindex set com2irq
19822 @kindex set com3base
19823 @kindex set com3irq
19824 @kindex set com4base
19825 @kindex set com4irq
19826 @item set com1base @var{addr}
19827 This command sets the base I/O port address of the @file{COM1} serial
19830 @item set com1irq @var{irq}
19831 This command sets the @dfn{Interrupt Request} (@code{IRQ}) line to use
19832 for the @file{COM1} serial port.
19834 There are similar commands @samp{set com2base}, @samp{set com3irq},
19835 etc.@: for setting the port address and the @code{IRQ} lines for the
19838 @kindex show com1base
19839 @kindex show com1irq
19840 @kindex show com2base
19841 @kindex show com2irq
19842 @kindex show com3base
19843 @kindex show com3irq
19844 @kindex show com4base
19845 @kindex show com4irq
19846 The related commands @samp{show com1base}, @samp{show com1irq} etc.@:
19847 display the current settings of the base address and the @code{IRQ}
19848 lines used by the COM ports.
19851 @kindex info serial
19852 @cindex DOS serial port status
19853 This command prints the status of the 4 DOS serial ports. For each
19854 port, it prints whether it's active or not, its I/O base address and
19855 IRQ number, whether it uses a 16550-style FIFO, its baudrate, and the
19856 counts of various errors encountered so far.
19860 @node Cygwin Native
19861 @subsection Features for Debugging MS Windows PE Executables
19862 @cindex MS Windows debugging
19863 @cindex native Cygwin debugging
19864 @cindex Cygwin-specific commands
19866 @value{GDBN} supports native debugging of MS Windows programs, including
19867 DLLs with and without symbolic debugging information.
19869 @cindex Ctrl-BREAK, MS-Windows
19870 @cindex interrupt debuggee on MS-Windows
19871 MS-Windows programs that call @code{SetConsoleMode} to switch off the
19872 special meaning of the @samp{Ctrl-C} keystroke cannot be interrupted
19873 by typing @kbd{C-c}. For this reason, @value{GDBN} on MS-Windows
19874 supports @kbd{C-@key{BREAK}} as an alternative interrupt key
19875 sequence, which can be used to interrupt the debuggee even if it
19878 There are various additional Cygwin-specific commands, described in
19879 this section. Working with DLLs that have no debugging symbols is
19880 described in @ref{Non-debug DLL Symbols}.
19885 This is a prefix of MS Windows-specific commands which print
19886 information about the target system and important OS structures.
19888 @item info w32 selector
19889 This command displays information returned by
19890 the Win32 API @code{GetThreadSelectorEntry} function.
19891 It takes an optional argument that is evaluated to
19892 a long value to give the information about this given selector.
19893 Without argument, this command displays information
19894 about the six segment registers.
19896 @item info w32 thread-information-block
19897 This command displays thread specific information stored in the
19898 Thread Information Block (readable on the X86 CPU family using @code{$fs}
19899 selector for 32-bit programs and @code{$gs} for 64-bit programs).
19903 This is a Cygwin-specific alias of @code{info shared}.
19905 @kindex dll-symbols
19907 This command is deprecated and will be removed in future versions
19908 of @value{GDBN}. Use the @code{sharedlibrary} command instead.
19910 This command loads symbols from a dll similarly to
19911 add-sym command but without the need to specify a base address.
19913 @kindex set cygwin-exceptions
19914 @cindex debugging the Cygwin DLL
19915 @cindex Cygwin DLL, debugging
19916 @item set cygwin-exceptions @var{mode}
19917 If @var{mode} is @code{on}, @value{GDBN} will break on exceptions that
19918 happen inside the Cygwin DLL. If @var{mode} is @code{off},
19919 @value{GDBN} will delay recognition of exceptions, and may ignore some
19920 exceptions which seem to be caused by internal Cygwin DLL
19921 ``bookkeeping''. This option is meant primarily for debugging the
19922 Cygwin DLL itself; the default value is @code{off} to avoid annoying
19923 @value{GDBN} users with false @code{SIGSEGV} signals.
19925 @kindex show cygwin-exceptions
19926 @item show cygwin-exceptions
19927 Displays whether @value{GDBN} will break on exceptions that happen
19928 inside the Cygwin DLL itself.
19930 @kindex set new-console
19931 @item set new-console @var{mode}
19932 If @var{mode} is @code{on} the debuggee will
19933 be started in a new console on next start.
19934 If @var{mode} is @code{off}, the debuggee will
19935 be started in the same console as the debugger.
19937 @kindex show new-console
19938 @item show new-console
19939 Displays whether a new console is used
19940 when the debuggee is started.
19942 @kindex set new-group
19943 @item set new-group @var{mode}
19944 This boolean value controls whether the debuggee should
19945 start a new group or stay in the same group as the debugger.
19946 This affects the way the Windows OS handles
19949 @kindex show new-group
19950 @item show new-group
19951 Displays current value of new-group boolean.
19953 @kindex set debugevents
19954 @item set debugevents
19955 This boolean value adds debug output concerning kernel events related
19956 to the debuggee seen by the debugger. This includes events that
19957 signal thread and process creation and exit, DLL loading and
19958 unloading, console interrupts, and debugging messages produced by the
19959 Windows @code{OutputDebugString} API call.
19961 @kindex set debugexec
19962 @item set debugexec
19963 This boolean value adds debug output concerning execute events
19964 (such as resume thread) seen by the debugger.
19966 @kindex set debugexceptions
19967 @item set debugexceptions
19968 This boolean value adds debug output concerning exceptions in the
19969 debuggee seen by the debugger.
19971 @kindex set debugmemory
19972 @item set debugmemory
19973 This boolean value adds debug output concerning debuggee memory reads
19974 and writes by the debugger.
19978 This boolean values specifies whether the debuggee is called
19979 via a shell or directly (default value is on).
19983 Displays if the debuggee will be started with a shell.
19988 * Non-debug DLL Symbols:: Support for DLLs without debugging symbols
19991 @node Non-debug DLL Symbols
19992 @subsubsection Support for DLLs without Debugging Symbols
19993 @cindex DLLs with no debugging symbols
19994 @cindex Minimal symbols and DLLs
19996 Very often on windows, some of the DLLs that your program relies on do
19997 not include symbolic debugging information (for example,
19998 @file{kernel32.dll}). When @value{GDBN} doesn't recognize any debugging
19999 symbols in a DLL, it relies on the minimal amount of symbolic
20000 information contained in the DLL's export table. This section
20001 describes working with such symbols, known internally to @value{GDBN} as
20002 ``minimal symbols''.
20004 Note that before the debugged program has started execution, no DLLs
20005 will have been loaded. The easiest way around this problem is simply to
20006 start the program --- either by setting a breakpoint or letting the
20007 program run once to completion.
20009 @subsubsection DLL Name Prefixes
20011 In keeping with the naming conventions used by the Microsoft debugging
20012 tools, DLL export symbols are made available with a prefix based on the
20013 DLL name, for instance @code{KERNEL32!CreateFileA}. The plain name is
20014 also entered into the symbol table, so @code{CreateFileA} is often
20015 sufficient. In some cases there will be name clashes within a program
20016 (particularly if the executable itself includes full debugging symbols)
20017 necessitating the use of the fully qualified name when referring to the
20018 contents of the DLL. Use single-quotes around the name to avoid the
20019 exclamation mark (``!'') being interpreted as a language operator.
20021 Note that the internal name of the DLL may be all upper-case, even
20022 though the file name of the DLL is lower-case, or vice-versa. Since
20023 symbols within @value{GDBN} are @emph{case-sensitive} this may cause
20024 some confusion. If in doubt, try the @code{info functions} and
20025 @code{info variables} commands or even @code{maint print msymbols}
20026 (@pxref{Symbols}). Here's an example:
20029 (@value{GDBP}) info function CreateFileA
20030 All functions matching regular expression "CreateFileA":
20032 Non-debugging symbols:
20033 0x77e885f4 CreateFileA
20034 0x77e885f4 KERNEL32!CreateFileA
20038 (@value{GDBP}) info function !
20039 All functions matching regular expression "!":
20041 Non-debugging symbols:
20042 0x6100114c cygwin1!__assert
20043 0x61004034 cygwin1!_dll_crt0@@0
20044 0x61004240 cygwin1!dll_crt0(per_process *)
20048 @subsubsection Working with Minimal Symbols
20050 Symbols extracted from a DLL's export table do not contain very much
20051 type information. All that @value{GDBN} can do is guess whether a symbol
20052 refers to a function or variable depending on the linker section that
20053 contains the symbol. Also note that the actual contents of the memory
20054 contained in a DLL are not available unless the program is running. This
20055 means that you cannot examine the contents of a variable or disassemble
20056 a function within a DLL without a running program.
20058 Variables are generally treated as pointers and dereferenced
20059 automatically. For this reason, it is often necessary to prefix a
20060 variable name with the address-of operator (``&'') and provide explicit
20061 type information in the command. Here's an example of the type of
20065 (@value{GDBP}) print 'cygwin1!__argv'
20070 (@value{GDBP}) x 'cygwin1!__argv'
20071 0x10021610: "\230y\""
20074 And two possible solutions:
20077 (@value{GDBP}) print ((char **)'cygwin1!__argv')[0]
20078 $2 = 0x22fd98 "/cygdrive/c/mydirectory/myprogram"
20082 (@value{GDBP}) x/2x &'cygwin1!__argv'
20083 0x610c0aa8 <cygwin1!__argv>: 0x10021608 0x00000000
20084 (@value{GDBP}) x/x 0x10021608
20085 0x10021608: 0x0022fd98
20086 (@value{GDBP}) x/s 0x0022fd98
20087 0x22fd98: "/cygdrive/c/mydirectory/myprogram"
20090 Setting a break point within a DLL is possible even before the program
20091 starts execution. However, under these circumstances, @value{GDBN} can't
20092 examine the initial instructions of the function in order to skip the
20093 function's frame set-up code. You can work around this by using ``*&''
20094 to set the breakpoint at a raw memory address:
20097 (@value{GDBP}) break *&'python22!PyOS_Readline'
20098 Breakpoint 1 at 0x1e04eff0
20101 The author of these extensions is not entirely convinced that setting a
20102 break point within a shared DLL like @file{kernel32.dll} is completely
20106 @subsection Commands Specific to @sc{gnu} Hurd Systems
20107 @cindex @sc{gnu} Hurd debugging
20109 This subsection describes @value{GDBN} commands specific to the
20110 @sc{gnu} Hurd native debugging.
20115 @kindex set signals@r{, Hurd command}
20116 @kindex set sigs@r{, Hurd command}
20117 This command toggles the state of inferior signal interception by
20118 @value{GDBN}. Mach exceptions, such as breakpoint traps, are not
20119 affected by this command. @code{sigs} is a shorthand alias for
20124 @kindex show signals@r{, Hurd command}
20125 @kindex show sigs@r{, Hurd command}
20126 Show the current state of intercepting inferior's signals.
20128 @item set signal-thread
20129 @itemx set sigthread
20130 @kindex set signal-thread
20131 @kindex set sigthread
20132 This command tells @value{GDBN} which thread is the @code{libc} signal
20133 thread. That thread is run when a signal is delivered to a running
20134 process. @code{set sigthread} is the shorthand alias of @code{set
20137 @item show signal-thread
20138 @itemx show sigthread
20139 @kindex show signal-thread
20140 @kindex show sigthread
20141 These two commands show which thread will run when the inferior is
20142 delivered a signal.
20145 @kindex set stopped@r{, Hurd command}
20146 This commands tells @value{GDBN} that the inferior process is stopped,
20147 as with the @code{SIGSTOP} signal. The stopped process can be
20148 continued by delivering a signal to it.
20151 @kindex show stopped@r{, Hurd command}
20152 This command shows whether @value{GDBN} thinks the debuggee is
20155 @item set exceptions
20156 @kindex set exceptions@r{, Hurd command}
20157 Use this command to turn off trapping of exceptions in the inferior.
20158 When exception trapping is off, neither breakpoints nor
20159 single-stepping will work. To restore the default, set exception
20162 @item show exceptions
20163 @kindex show exceptions@r{, Hurd command}
20164 Show the current state of trapping exceptions in the inferior.
20166 @item set task pause
20167 @kindex set task@r{, Hurd commands}
20168 @cindex task attributes (@sc{gnu} Hurd)
20169 @cindex pause current task (@sc{gnu} Hurd)
20170 This command toggles task suspension when @value{GDBN} has control.
20171 Setting it to on takes effect immediately, and the task is suspended
20172 whenever @value{GDBN} gets control. Setting it to off will take
20173 effect the next time the inferior is continued. If this option is set
20174 to off, you can use @code{set thread default pause on} or @code{set
20175 thread pause on} (see below) to pause individual threads.
20177 @item show task pause
20178 @kindex show task@r{, Hurd commands}
20179 Show the current state of task suspension.
20181 @item set task detach-suspend-count
20182 @cindex task suspend count
20183 @cindex detach from task, @sc{gnu} Hurd
20184 This command sets the suspend count the task will be left with when
20185 @value{GDBN} detaches from it.
20187 @item show task detach-suspend-count
20188 Show the suspend count the task will be left with when detaching.
20190 @item set task exception-port
20191 @itemx set task excp
20192 @cindex task exception port, @sc{gnu} Hurd
20193 This command sets the task exception port to which @value{GDBN} will
20194 forward exceptions. The argument should be the value of the @dfn{send
20195 rights} of the task. @code{set task excp} is a shorthand alias.
20197 @item set noninvasive
20198 @cindex noninvasive task options
20199 This command switches @value{GDBN} to a mode that is the least
20200 invasive as far as interfering with the inferior is concerned. This
20201 is the same as using @code{set task pause}, @code{set exceptions}, and
20202 @code{set signals} to values opposite to the defaults.
20204 @item info send-rights
20205 @itemx info receive-rights
20206 @itemx info port-rights
20207 @itemx info port-sets
20208 @itemx info dead-names
20211 @cindex send rights, @sc{gnu} Hurd
20212 @cindex receive rights, @sc{gnu} Hurd
20213 @cindex port rights, @sc{gnu} Hurd
20214 @cindex port sets, @sc{gnu} Hurd
20215 @cindex dead names, @sc{gnu} Hurd
20216 These commands display information about, respectively, send rights,
20217 receive rights, port rights, port sets, and dead names of a task.
20218 There are also shorthand aliases: @code{info ports} for @code{info
20219 port-rights} and @code{info psets} for @code{info port-sets}.
20221 @item set thread pause
20222 @kindex set thread@r{, Hurd command}
20223 @cindex thread properties, @sc{gnu} Hurd
20224 @cindex pause current thread (@sc{gnu} Hurd)
20225 This command toggles current thread suspension when @value{GDBN} has
20226 control. Setting it to on takes effect immediately, and the current
20227 thread is suspended whenever @value{GDBN} gets control. Setting it to
20228 off will take effect the next time the inferior is continued.
20229 Normally, this command has no effect, since when @value{GDBN} has
20230 control, the whole task is suspended. However, if you used @code{set
20231 task pause off} (see above), this command comes in handy to suspend
20232 only the current thread.
20234 @item show thread pause
20235 @kindex show thread@r{, Hurd command}
20236 This command shows the state of current thread suspension.
20238 @item set thread run
20239 This command sets whether the current thread is allowed to run.
20241 @item show thread run
20242 Show whether the current thread is allowed to run.
20244 @item set thread detach-suspend-count
20245 @cindex thread suspend count, @sc{gnu} Hurd
20246 @cindex detach from thread, @sc{gnu} Hurd
20247 This command sets the suspend count @value{GDBN} will leave on a
20248 thread when detaching. This number is relative to the suspend count
20249 found by @value{GDBN} when it notices the thread; use @code{set thread
20250 takeover-suspend-count} to force it to an absolute value.
20252 @item show thread detach-suspend-count
20253 Show the suspend count @value{GDBN} will leave on the thread when
20256 @item set thread exception-port
20257 @itemx set thread excp
20258 Set the thread exception port to which to forward exceptions. This
20259 overrides the port set by @code{set task exception-port} (see above).
20260 @code{set thread excp} is the shorthand alias.
20262 @item set thread takeover-suspend-count
20263 Normally, @value{GDBN}'s thread suspend counts are relative to the
20264 value @value{GDBN} finds when it notices each thread. This command
20265 changes the suspend counts to be absolute instead.
20267 @item set thread default
20268 @itemx show thread default
20269 @cindex thread default settings, @sc{gnu} Hurd
20270 Each of the above @code{set thread} commands has a @code{set thread
20271 default} counterpart (e.g., @code{set thread default pause}, @code{set
20272 thread default exception-port}, etc.). The @code{thread default}
20273 variety of commands sets the default thread properties for all
20274 threads; you can then change the properties of individual threads with
20275 the non-default commands.
20282 @value{GDBN} provides the following commands specific to the Darwin target:
20285 @item set debug darwin @var{num}
20286 @kindex set debug darwin
20287 When set to a non zero value, enables debugging messages specific to
20288 the Darwin support. Higher values produce more verbose output.
20290 @item show debug darwin
20291 @kindex show debug darwin
20292 Show the current state of Darwin messages.
20294 @item set debug mach-o @var{num}
20295 @kindex set debug mach-o
20296 When set to a non zero value, enables debugging messages while
20297 @value{GDBN} is reading Darwin object files. (@dfn{Mach-O} is the
20298 file format used on Darwin for object and executable files.) Higher
20299 values produce more verbose output. This is a command to diagnose
20300 problems internal to @value{GDBN} and should not be needed in normal
20303 @item show debug mach-o
20304 @kindex show debug mach-o
20305 Show the current state of Mach-O file messages.
20307 @item set mach-exceptions on
20308 @itemx set mach-exceptions off
20309 @kindex set mach-exceptions
20310 On Darwin, faults are first reported as a Mach exception and are then
20311 mapped to a Posix signal. Use this command to turn on trapping of
20312 Mach exceptions in the inferior. This might be sometimes useful to
20313 better understand the cause of a fault. The default is off.
20315 @item show mach-exceptions
20316 @kindex show mach-exceptions
20317 Show the current state of exceptions trapping.
20322 @section Embedded Operating Systems
20324 This section describes configurations involving the debugging of
20325 embedded operating systems that are available for several different
20329 * VxWorks:: Using @value{GDBN} with VxWorks
20332 @value{GDBN} includes the ability to debug programs running on
20333 various real-time operating systems.
20336 @subsection Using @value{GDBN} with VxWorks
20342 @kindex target vxworks
20343 @item target vxworks @var{machinename}
20344 A VxWorks system, attached via TCP/IP. The argument @var{machinename}
20345 is the target system's machine name or IP address.
20349 On VxWorks, @code{load} links @var{filename} dynamically on the
20350 current target system as well as adding its symbols in @value{GDBN}.
20352 @value{GDBN} enables developers to spawn and debug tasks running on networked
20353 VxWorks targets from a Unix host. Already-running tasks spawned from
20354 the VxWorks shell can also be debugged. @value{GDBN} uses code that runs on
20355 both the Unix host and on the VxWorks target. The program
20356 @code{@value{GDBP}} is installed and executed on the Unix host. (It may be
20357 installed with the name @code{vxgdb}, to distinguish it from a
20358 @value{GDBN} for debugging programs on the host itself.)
20361 @item VxWorks-timeout @var{args}
20362 @kindex vxworks-timeout
20363 All VxWorks-based targets now support the option @code{vxworks-timeout}.
20364 This option is set by the user, and @var{args} represents the number of
20365 seconds @value{GDBN} waits for responses to rpc's. You might use this if
20366 your VxWorks target is a slow software simulator or is on the far side
20367 of a thin network line.
20370 The following information on connecting to VxWorks was current when
20371 this manual was produced; newer releases of VxWorks may use revised
20374 @findex INCLUDE_RDB
20375 To use @value{GDBN} with VxWorks, you must rebuild your VxWorks kernel
20376 to include the remote debugging interface routines in the VxWorks
20377 library @file{rdb.a}. To do this, define @code{INCLUDE_RDB} in the
20378 VxWorks configuration file @file{configAll.h} and rebuild your VxWorks
20379 kernel. The resulting kernel contains @file{rdb.a}, and spawns the
20380 source debugging task @code{tRdbTask} when VxWorks is booted. For more
20381 information on configuring and remaking VxWorks, see the manufacturer's
20383 @c VxWorks, see the @cite{VxWorks Programmer's Guide}.
20385 Once you have included @file{rdb.a} in your VxWorks system image and set
20386 your Unix execution search path to find @value{GDBN}, you are ready to
20387 run @value{GDBN}. From your Unix host, run @code{@value{GDBP}} (or
20388 @code{vxgdb}, depending on your installation).
20390 @value{GDBN} comes up showing the prompt:
20397 * VxWorks Connection:: Connecting to VxWorks
20398 * VxWorks Download:: VxWorks download
20399 * VxWorks Attach:: Running tasks
20402 @node VxWorks Connection
20403 @subsubsection Connecting to VxWorks
20405 The @value{GDBN} command @code{target} lets you connect to a VxWorks target on the
20406 network. To connect to a target whose host name is ``@code{tt}'', type:
20409 (vxgdb) target vxworks tt
20413 @value{GDBN} displays messages like these:
20416 Attaching remote machine across net...
20421 @value{GDBN} then attempts to read the symbol tables of any object modules
20422 loaded into the VxWorks target since it was last booted. @value{GDBN} locates
20423 these files by searching the directories listed in the command search
20424 path (@pxref{Environment, ,Your Program's Environment}); if it fails
20425 to find an object file, it displays a message such as:
20428 prog.o: No such file or directory.
20431 When this happens, add the appropriate directory to the search path with
20432 the @value{GDBN} command @code{path}, and execute the @code{target}
20435 @node VxWorks Download
20436 @subsubsection VxWorks Download
20438 @cindex download to VxWorks
20439 If you have connected to the VxWorks target and you want to debug an
20440 object that has not yet been loaded, you can use the @value{GDBN}
20441 @code{load} command to download a file from Unix to VxWorks
20442 incrementally. The object file given as an argument to the @code{load}
20443 command is actually opened twice: first by the VxWorks target in order
20444 to download the code, then by @value{GDBN} in order to read the symbol
20445 table. This can lead to problems if the current working directories on
20446 the two systems differ. If both systems have NFS mounted the same
20447 filesystems, you can avoid these problems by using absolute paths.
20448 Otherwise, it is simplest to set the working directory on both systems
20449 to the directory in which the object file resides, and then to reference
20450 the file by its name, without any path. For instance, a program
20451 @file{prog.o} may reside in @file{@var{vxpath}/vw/demo/rdb} in VxWorks
20452 and in @file{@var{hostpath}/vw/demo/rdb} on the host. To load this
20453 program, type this on VxWorks:
20456 -> cd "@var{vxpath}/vw/demo/rdb"
20460 Then, in @value{GDBN}, type:
20463 (vxgdb) cd @var{hostpath}/vw/demo/rdb
20464 (vxgdb) load prog.o
20467 @value{GDBN} displays a response similar to this:
20470 Reading symbol data from wherever/vw/demo/rdb/prog.o... done.
20473 You can also use the @code{load} command to reload an object module
20474 after editing and recompiling the corresponding source file. Note that
20475 this makes @value{GDBN} delete all currently-defined breakpoints,
20476 auto-displays, and convenience variables, and to clear the value
20477 history. (This is necessary in order to preserve the integrity of
20478 debugger's data structures that reference the target system's symbol
20481 @node VxWorks Attach
20482 @subsubsection Running Tasks
20484 @cindex running VxWorks tasks
20485 You can also attach to an existing task using the @code{attach} command as
20489 (vxgdb) attach @var{task}
20493 where @var{task} is the VxWorks hexadecimal task ID. The task can be running
20494 or suspended when you attach to it. Running tasks are suspended at
20495 the time of attachment.
20497 @node Embedded Processors
20498 @section Embedded Processors
20500 This section goes into details specific to particular embedded
20503 @cindex send command to simulator
20504 Whenever a specific embedded processor has a simulator, @value{GDBN}
20505 allows to send an arbitrary command to the simulator.
20508 @item sim @var{command}
20509 @kindex sim@r{, a command}
20510 Send an arbitrary @var{command} string to the simulator. Consult the
20511 documentation for the specific simulator in use for information about
20512 acceptable commands.
20518 * M32R/D:: Renesas M32R/D
20519 * M68K:: Motorola M68K
20520 * MicroBlaze:: Xilinx MicroBlaze
20521 * MIPS Embedded:: MIPS Embedded
20522 * PowerPC Embedded:: PowerPC Embedded
20523 * PA:: HP PA Embedded
20524 * Sparclet:: Tsqware Sparclet
20525 * Sparclite:: Fujitsu Sparclite
20526 * Z8000:: Zilog Z8000
20529 * Super-H:: Renesas Super-H
20538 @item target rdi @var{dev}
20539 ARM Angel monitor, via RDI library interface to ADP protocol. You may
20540 use this target to communicate with both boards running the Angel
20541 monitor, or with the EmbeddedICE JTAG debug device.
20544 @item target rdp @var{dev}
20549 @value{GDBN} provides the following ARM-specific commands:
20552 @item set arm disassembler
20554 This commands selects from a list of disassembly styles. The
20555 @code{"std"} style is the standard style.
20557 @item show arm disassembler
20559 Show the current disassembly style.
20561 @item set arm apcs32
20562 @cindex ARM 32-bit mode
20563 This command toggles ARM operation mode between 32-bit and 26-bit.
20565 @item show arm apcs32
20566 Display the current usage of the ARM 32-bit mode.
20568 @item set arm fpu @var{fputype}
20569 This command sets the ARM floating-point unit (FPU) type. The
20570 argument @var{fputype} can be one of these:
20574 Determine the FPU type by querying the OS ABI.
20576 Software FPU, with mixed-endian doubles on little-endian ARM
20579 GCC-compiled FPA co-processor.
20581 Software FPU with pure-endian doubles.
20587 Show the current type of the FPU.
20590 This command forces @value{GDBN} to use the specified ABI.
20593 Show the currently used ABI.
20595 @item set arm fallback-mode (arm|thumb|auto)
20596 @value{GDBN} uses the symbol table, when available, to determine
20597 whether instructions are ARM or Thumb. This command controls
20598 @value{GDBN}'s default behavior when the symbol table is not
20599 available. The default is @samp{auto}, which causes @value{GDBN} to
20600 use the current execution mode (from the @code{T} bit in the @code{CPSR}
20603 @item show arm fallback-mode
20604 Show the current fallback instruction mode.
20606 @item set arm force-mode (arm|thumb|auto)
20607 This command overrides use of the symbol table to determine whether
20608 instructions are ARM or Thumb. The default is @samp{auto}, which
20609 causes @value{GDBN} to use the symbol table and then the setting
20610 of @samp{set arm fallback-mode}.
20612 @item show arm force-mode
20613 Show the current forced instruction mode.
20615 @item set debug arm
20616 Toggle whether to display ARM-specific debugging messages from the ARM
20617 target support subsystem.
20619 @item show debug arm
20620 Show whether ARM-specific debugging messages are enabled.
20623 The following commands are available when an ARM target is debugged
20624 using the RDI interface:
20627 @item rdilogfile @r{[}@var{file}@r{]}
20629 @cindex ADP (Angel Debugger Protocol) logging
20630 Set the filename for the ADP (Angel Debugger Protocol) packet log.
20631 With an argument, sets the log file to the specified @var{file}. With
20632 no argument, show the current log file name. The default log file is
20635 @item rdilogenable @r{[}@var{arg}@r{]}
20636 @kindex rdilogenable
20637 Control logging of ADP packets. With an argument of 1 or @code{"yes"}
20638 enables logging, with an argument 0 or @code{"no"} disables it. With
20639 no arguments displays the current setting. When logging is enabled,
20640 ADP packets exchanged between @value{GDBN} and the RDI target device
20641 are logged to a file.
20643 @item set rdiromatzero
20644 @kindex set rdiromatzero
20645 @cindex ROM at zero address, RDI
20646 Tell @value{GDBN} whether the target has ROM at address 0. If on,
20647 vector catching is disabled, so that zero address can be used. If off
20648 (the default), vector catching is enabled. For this command to take
20649 effect, it needs to be invoked prior to the @code{target rdi} command.
20651 @item show rdiromatzero
20652 @kindex show rdiromatzero
20653 Show the current setting of ROM at zero address.
20655 @item set rdiheartbeat
20656 @kindex set rdiheartbeat
20657 @cindex RDI heartbeat
20658 Enable or disable RDI heartbeat packets. It is not recommended to
20659 turn on this option, since it confuses ARM and EPI JTAG interface, as
20660 well as the Angel monitor.
20662 @item show rdiheartbeat
20663 @kindex show rdiheartbeat
20664 Show the setting of RDI heartbeat packets.
20668 @item target sim @r{[}@var{simargs}@r{]} @dots{}
20669 The @value{GDBN} ARM simulator accepts the following optional arguments.
20672 @item --swi-support=@var{type}
20673 Tell the simulator which SWI interfaces to support.
20674 @var{type} may be a comma separated list of the following values.
20675 The default value is @code{all}.
20688 @subsection Renesas M32R/D and M32R/SDI
20691 @kindex target m32r
20692 @item target m32r @var{dev}
20693 Renesas M32R/D ROM monitor.
20695 @kindex target m32rsdi
20696 @item target m32rsdi @var{dev}
20697 Renesas M32R SDI server, connected via parallel port to the board.
20700 The following @value{GDBN} commands are specific to the M32R monitor:
20703 @item set download-path @var{path}
20704 @kindex set download-path
20705 @cindex find downloadable @sc{srec} files (M32R)
20706 Set the default path for finding downloadable @sc{srec} files.
20708 @item show download-path
20709 @kindex show download-path
20710 Show the default path for downloadable @sc{srec} files.
20712 @item set board-address @var{addr}
20713 @kindex set board-address
20714 @cindex M32-EVA target board address
20715 Set the IP address for the M32R-EVA target board.
20717 @item show board-address
20718 @kindex show board-address
20719 Show the current IP address of the target board.
20721 @item set server-address @var{addr}
20722 @kindex set server-address
20723 @cindex download server address (M32R)
20724 Set the IP address for the download server, which is the @value{GDBN}'s
20727 @item show server-address
20728 @kindex show server-address
20729 Display the IP address of the download server.
20731 @item upload @r{[}@var{file}@r{]}
20732 @kindex upload@r{, M32R}
20733 Upload the specified @sc{srec} @var{file} via the monitor's Ethernet
20734 upload capability. If no @var{file} argument is given, the current
20735 executable file is uploaded.
20737 @item tload @r{[}@var{file}@r{]}
20738 @kindex tload@r{, M32R}
20739 Test the @code{upload} command.
20742 The following commands are available for M32R/SDI:
20747 @cindex reset SDI connection, M32R
20748 This command resets the SDI connection.
20752 This command shows the SDI connection status.
20755 @kindex debug_chaos
20756 @cindex M32R/Chaos debugging
20757 Instructs the remote that M32R/Chaos debugging is to be used.
20759 @item use_debug_dma
20760 @kindex use_debug_dma
20761 Instructs the remote to use the DEBUG_DMA method of accessing memory.
20764 @kindex use_mon_code
20765 Instructs the remote to use the MON_CODE method of accessing memory.
20768 @kindex use_ib_break
20769 Instructs the remote to set breakpoints by IB break.
20771 @item use_dbt_break
20772 @kindex use_dbt_break
20773 Instructs the remote to set breakpoints by DBT.
20779 The Motorola m68k configuration includes ColdFire support, and a
20780 target command for the following ROM monitor.
20784 @kindex target dbug
20785 @item target dbug @var{dev}
20786 dBUG ROM monitor for Motorola ColdFire.
20791 @subsection MicroBlaze
20792 @cindex Xilinx MicroBlaze
20793 @cindex XMD, Xilinx Microprocessor Debugger
20795 The MicroBlaze is a soft-core processor supported on various Xilinx
20796 FPGAs, such as Spartan or Virtex series. Boards with these processors
20797 usually have JTAG ports which connect to a host system running the Xilinx
20798 Embedded Development Kit (EDK) or Software Development Kit (SDK).
20799 This host system is used to download the configuration bitstream to
20800 the target FPGA. The Xilinx Microprocessor Debugger (XMD) program
20801 communicates with the target board using the JTAG interface and
20802 presents a @code{gdbserver} interface to the board. By default
20803 @code{xmd} uses port @code{1234}. (While it is possible to change
20804 this default port, it requires the use of undocumented @code{xmd}
20805 commands. Contact Xilinx support if you need to do this.)
20807 Use these GDB commands to connect to the MicroBlaze target processor.
20810 @item target remote :1234
20811 Use this command to connect to the target if you are running @value{GDBN}
20812 on the same system as @code{xmd}.
20814 @item target remote @var{xmd-host}:1234
20815 Use this command to connect to the target if it is connected to @code{xmd}
20816 running on a different system named @var{xmd-host}.
20819 Use this command to download a program to the MicroBlaze target.
20821 @item set debug microblaze @var{n}
20822 Enable MicroBlaze-specific debugging messages if non-zero.
20824 @item show debug microblaze @var{n}
20825 Show MicroBlaze-specific debugging level.
20828 @node MIPS Embedded
20829 @subsection @acronym{MIPS} Embedded
20831 @cindex @acronym{MIPS} boards
20832 @value{GDBN} can use the @acronym{MIPS} remote debugging protocol to talk to a
20833 @acronym{MIPS} board attached to a serial line. This is available when
20834 you configure @value{GDBN} with @samp{--target=mips-elf}.
20837 Use these @value{GDBN} commands to specify the connection to your target board:
20840 @item target mips @var{port}
20841 @kindex target mips @var{port}
20842 To run a program on the board, start up @code{@value{GDBP}} with the
20843 name of your program as the argument. To connect to the board, use the
20844 command @samp{target mips @var{port}}, where @var{port} is the name of
20845 the serial port connected to the board. If the program has not already
20846 been downloaded to the board, you may use the @code{load} command to
20847 download it. You can then use all the usual @value{GDBN} commands.
20849 For example, this sequence connects to the target board through a serial
20850 port, and loads and runs a program called @var{prog} through the
20854 host$ @value{GDBP} @var{prog}
20855 @value{GDBN} is free software and @dots{}
20856 (@value{GDBP}) target mips /dev/ttyb
20857 (@value{GDBP}) load @var{prog}
20861 @item target mips @var{hostname}:@var{portnumber}
20862 On some @value{GDBN} host configurations, you can specify a TCP
20863 connection (for instance, to a serial line managed by a terminal
20864 concentrator) instead of a serial port, using the syntax
20865 @samp{@var{hostname}:@var{portnumber}}.
20867 @item target pmon @var{port}
20868 @kindex target pmon @var{port}
20871 @item target ddb @var{port}
20872 @kindex target ddb @var{port}
20873 NEC's DDB variant of PMON for Vr4300.
20875 @item target lsi @var{port}
20876 @kindex target lsi @var{port}
20877 LSI variant of PMON.
20879 @kindex target r3900
20880 @item target r3900 @var{dev}
20881 Densan DVE-R3900 ROM monitor for Toshiba R3900 Mips.
20883 @kindex target array
20884 @item target array @var{dev}
20885 Array Tech LSI33K RAID controller board.
20891 @value{GDBN} also supports these special commands for @acronym{MIPS} targets:
20894 @item set mipsfpu double
20895 @itemx set mipsfpu single
20896 @itemx set mipsfpu none
20897 @itemx set mipsfpu auto
20898 @itemx show mipsfpu
20899 @kindex set mipsfpu
20900 @kindex show mipsfpu
20901 @cindex @acronym{MIPS} remote floating point
20902 @cindex floating point, @acronym{MIPS} remote
20903 If your target board does not support the @acronym{MIPS} floating point
20904 coprocessor, you should use the command @samp{set mipsfpu none} (if you
20905 need this, you may wish to put the command in your @value{GDBN} init
20906 file). This tells @value{GDBN} how to find the return value of
20907 functions which return floating point values. It also allows
20908 @value{GDBN} to avoid saving the floating point registers when calling
20909 functions on the board. If you are using a floating point coprocessor
20910 with only single precision floating point support, as on the @sc{r4650}
20911 processor, use the command @samp{set mipsfpu single}. The default
20912 double precision floating point coprocessor may be selected using
20913 @samp{set mipsfpu double}.
20915 In previous versions the only choices were double precision or no
20916 floating point, so @samp{set mipsfpu on} will select double precision
20917 and @samp{set mipsfpu off} will select no floating point.
20919 As usual, you can inquire about the @code{mipsfpu} variable with
20920 @samp{show mipsfpu}.
20922 @item set timeout @var{seconds}
20923 @itemx set retransmit-timeout @var{seconds}
20924 @itemx show timeout
20925 @itemx show retransmit-timeout
20926 @cindex @code{timeout}, @acronym{MIPS} protocol
20927 @cindex @code{retransmit-timeout}, @acronym{MIPS} protocol
20928 @kindex set timeout
20929 @kindex show timeout
20930 @kindex set retransmit-timeout
20931 @kindex show retransmit-timeout
20932 You can control the timeout used while waiting for a packet, in the @acronym{MIPS}
20933 remote protocol, with the @code{set timeout @var{seconds}} command. The
20934 default is 5 seconds. Similarly, you can control the timeout used while
20935 waiting for an acknowledgment of a packet with the @code{set
20936 retransmit-timeout @var{seconds}} command. The default is 3 seconds.
20937 You can inspect both values with @code{show timeout} and @code{show
20938 retransmit-timeout}. (These commands are @emph{only} available when
20939 @value{GDBN} is configured for @samp{--target=mips-elf}.)
20941 The timeout set by @code{set timeout} does not apply when @value{GDBN}
20942 is waiting for your program to stop. In that case, @value{GDBN} waits
20943 forever because it has no way of knowing how long the program is going
20944 to run before stopping.
20946 @item set syn-garbage-limit @var{num}
20947 @kindex set syn-garbage-limit@r{, @acronym{MIPS} remote}
20948 @cindex synchronize with remote @acronym{MIPS} target
20949 Limit the maximum number of characters @value{GDBN} should ignore when
20950 it tries to synchronize with the remote target. The default is 10
20951 characters. Setting the limit to -1 means there's no limit.
20953 @item show syn-garbage-limit
20954 @kindex show syn-garbage-limit@r{, @acronym{MIPS} remote}
20955 Show the current limit on the number of characters to ignore when
20956 trying to synchronize with the remote system.
20958 @item set monitor-prompt @var{prompt}
20959 @kindex set monitor-prompt@r{, @acronym{MIPS} remote}
20960 @cindex remote monitor prompt
20961 Tell @value{GDBN} to expect the specified @var{prompt} string from the
20962 remote monitor. The default depends on the target:
20972 @item show monitor-prompt
20973 @kindex show monitor-prompt@r{, @acronym{MIPS} remote}
20974 Show the current strings @value{GDBN} expects as the prompt from the
20977 @item set monitor-warnings
20978 @kindex set monitor-warnings@r{, @acronym{MIPS} remote}
20979 Enable or disable monitor warnings about hardware breakpoints. This
20980 has effect only for the @code{lsi} target. When on, @value{GDBN} will
20981 display warning messages whose codes are returned by the @code{lsi}
20982 PMON monitor for breakpoint commands.
20984 @item show monitor-warnings
20985 @kindex show monitor-warnings@r{, @acronym{MIPS} remote}
20986 Show the current setting of printing monitor warnings.
20988 @item pmon @var{command}
20989 @kindex pmon@r{, @acronym{MIPS} remote}
20990 @cindex send PMON command
20991 This command allows sending an arbitrary @var{command} string to the
20992 monitor. The monitor must be in debug mode for this to work.
20995 @node PowerPC Embedded
20996 @subsection PowerPC Embedded
20998 @cindex DVC register
20999 @value{GDBN} supports using the DVC (Data Value Compare) register to
21000 implement in hardware simple hardware watchpoint conditions of the form:
21003 (@value{GDBP}) watch @var{ADDRESS|VARIABLE} \
21004 if @var{ADDRESS|VARIABLE} == @var{CONSTANT EXPRESSION}
21007 The DVC register will be automatically used when @value{GDBN} detects
21008 such pattern in a condition expression, and the created watchpoint uses one
21009 debug register (either the @code{exact-watchpoints} option is on and the
21010 variable is scalar, or the variable has a length of one byte). This feature
21011 is available in native @value{GDBN} running on a Linux kernel version 2.6.34
21014 When running on PowerPC embedded processors, @value{GDBN} automatically uses
21015 ranged hardware watchpoints, unless the @code{exact-watchpoints} option is on,
21016 in which case watchpoints using only one debug register are created when
21017 watching variables of scalar types.
21019 You can create an artificial array to watch an arbitrary memory
21020 region using one of the following commands (@pxref{Expressions}):
21023 (@value{GDBP}) watch *((char *) @var{address})@@@var{length}
21024 (@value{GDBP}) watch @{char[@var{length}]@} @var{address}
21027 PowerPC embedded processors support masked watchpoints. See the discussion
21028 about the @code{mask} argument in @ref{Set Watchpoints}.
21030 @cindex ranged breakpoint
21031 PowerPC embedded processors support hardware accelerated
21032 @dfn{ranged breakpoints}. A ranged breakpoint stops execution of
21033 the inferior whenever it executes an instruction at any address within
21034 the range it specifies. To set a ranged breakpoint in @value{GDBN},
21035 use the @code{break-range} command.
21037 @value{GDBN} provides the following PowerPC-specific commands:
21040 @kindex break-range
21041 @item break-range @var{start-location}, @var{end-location}
21042 Set a breakpoint for an address range.
21043 @var{start-location} and @var{end-location} can specify a function name,
21044 a line number, an offset of lines from the current line or from the start
21045 location, or an address of an instruction (see @ref{Specify Location},
21046 for a list of all the possible ways to specify a @var{location}.)
21047 The breakpoint will stop execution of the inferior whenever it
21048 executes an instruction at any address within the specified range,
21049 (including @var{start-location} and @var{end-location}.)
21051 @kindex set powerpc
21052 @item set powerpc soft-float
21053 @itemx show powerpc soft-float
21054 Force @value{GDBN} to use (or not use) a software floating point calling
21055 convention. By default, @value{GDBN} selects the calling convention based
21056 on the selected architecture and the provided executable file.
21058 @item set powerpc vector-abi
21059 @itemx show powerpc vector-abi
21060 Force @value{GDBN} to use the specified calling convention for vector
21061 arguments and return values. The valid options are @samp{auto};
21062 @samp{generic}, to avoid vector registers even if they are present;
21063 @samp{altivec}, to use AltiVec registers; and @samp{spe} to use SPE
21064 registers. By default, @value{GDBN} selects the calling convention
21065 based on the selected architecture and the provided executable file.
21067 @item set powerpc exact-watchpoints
21068 @itemx show powerpc exact-watchpoints
21069 Allow @value{GDBN} to use only one debug register when watching a variable
21070 of scalar type, thus assuming that the variable is accessed through the
21071 address of its first byte.
21073 @kindex target dink32
21074 @item target dink32 @var{dev}
21075 DINK32 ROM monitor.
21077 @kindex target ppcbug
21078 @item target ppcbug @var{dev}
21079 @kindex target ppcbug1
21080 @item target ppcbug1 @var{dev}
21081 PPCBUG ROM monitor for PowerPC.
21084 @item target sds @var{dev}
21085 SDS monitor, running on a PowerPC board (such as Motorola's ADS).
21088 @cindex SDS protocol
21089 The following commands specific to the SDS protocol are supported
21093 @item set sdstimeout @var{nsec}
21094 @kindex set sdstimeout
21095 Set the timeout for SDS protocol reads to be @var{nsec} seconds. The
21096 default is 2 seconds.
21098 @item show sdstimeout
21099 @kindex show sdstimeout
21100 Show the current value of the SDS timeout.
21102 @item sds @var{command}
21103 @kindex sds@r{, a command}
21104 Send the specified @var{command} string to the SDS monitor.
21109 @subsection HP PA Embedded
21113 @kindex target op50n
21114 @item target op50n @var{dev}
21115 OP50N monitor, running on an OKI HPPA board.
21117 @kindex target w89k
21118 @item target w89k @var{dev}
21119 W89K monitor, running on a Winbond HPPA board.
21124 @subsection Tsqware Sparclet
21128 @value{GDBN} enables developers to debug tasks running on
21129 Sparclet targets from a Unix host.
21130 @value{GDBN} uses code that runs on
21131 both the Unix host and on the Sparclet target. The program
21132 @code{@value{GDBP}} is installed and executed on the Unix host.
21135 @item remotetimeout @var{args}
21136 @kindex remotetimeout
21137 @value{GDBN} supports the option @code{remotetimeout}.
21138 This option is set by the user, and @var{args} represents the number of
21139 seconds @value{GDBN} waits for responses.
21142 @cindex compiling, on Sparclet
21143 When compiling for debugging, include the options @samp{-g} to get debug
21144 information and @samp{-Ttext} to relocate the program to where you wish to
21145 load it on the target. You may also want to add the options @samp{-n} or
21146 @samp{-N} in order to reduce the size of the sections. Example:
21149 sparclet-aout-gcc prog.c -Ttext 0x12010000 -g -o prog -N
21152 You can use @code{objdump} to verify that the addresses are what you intended:
21155 sparclet-aout-objdump --headers --syms prog
21158 @cindex running, on Sparclet
21160 your Unix execution search path to find @value{GDBN}, you are ready to
21161 run @value{GDBN}. From your Unix host, run @code{@value{GDBP}}
21162 (or @code{sparclet-aout-gdb}, depending on your installation).
21164 @value{GDBN} comes up showing the prompt:
21171 * Sparclet File:: Setting the file to debug
21172 * Sparclet Connection:: Connecting to Sparclet
21173 * Sparclet Download:: Sparclet download
21174 * Sparclet Execution:: Running and debugging
21177 @node Sparclet File
21178 @subsubsection Setting File to Debug
21180 The @value{GDBN} command @code{file} lets you choose with program to debug.
21183 (gdbslet) file prog
21187 @value{GDBN} then attempts to read the symbol table of @file{prog}.
21188 @value{GDBN} locates
21189 the file by searching the directories listed in the command search
21191 If the file was compiled with debug information (option @samp{-g}), source
21192 files will be searched as well.
21193 @value{GDBN} locates
21194 the source files by searching the directories listed in the directory search
21195 path (@pxref{Environment, ,Your Program's Environment}).
21197 to find a file, it displays a message such as:
21200 prog: No such file or directory.
21203 When this happens, add the appropriate directories to the search paths with
21204 the @value{GDBN} commands @code{path} and @code{dir}, and execute the
21205 @code{target} command again.
21207 @node Sparclet Connection
21208 @subsubsection Connecting to Sparclet
21210 The @value{GDBN} command @code{target} lets you connect to a Sparclet target.
21211 To connect to a target on serial port ``@code{ttya}'', type:
21214 (gdbslet) target sparclet /dev/ttya
21215 Remote target sparclet connected to /dev/ttya
21216 main () at ../prog.c:3
21220 @value{GDBN} displays messages like these:
21226 @node Sparclet Download
21227 @subsubsection Sparclet Download
21229 @cindex download to Sparclet
21230 Once connected to the Sparclet target,
21231 you can use the @value{GDBN}
21232 @code{load} command to download the file from the host to the target.
21233 The file name and load offset should be given as arguments to the @code{load}
21235 Since the file format is aout, the program must be loaded to the starting
21236 address. You can use @code{objdump} to find out what this value is. The load
21237 offset is an offset which is added to the VMA (virtual memory address)
21238 of each of the file's sections.
21239 For instance, if the program
21240 @file{prog} was linked to text address 0x1201000, with data at 0x12010160
21241 and bss at 0x12010170, in @value{GDBN}, type:
21244 (gdbslet) load prog 0x12010000
21245 Loading section .text, size 0xdb0 vma 0x12010000
21248 If the code is loaded at a different address then what the program was linked
21249 to, you may need to use the @code{section} and @code{add-symbol-file} commands
21250 to tell @value{GDBN} where to map the symbol table.
21252 @node Sparclet Execution
21253 @subsubsection Running and Debugging
21255 @cindex running and debugging Sparclet programs
21256 You can now begin debugging the task using @value{GDBN}'s execution control
21257 commands, @code{b}, @code{step}, @code{run}, etc. See the @value{GDBN}
21258 manual for the list of commands.
21262 Breakpoint 1 at 0x12010000: file prog.c, line 3.
21264 Starting program: prog
21265 Breakpoint 1, main (argc=1, argv=0xeffff21c) at prog.c:3
21266 3 char *symarg = 0;
21268 4 char *execarg = "hello!";
21273 @subsection Fujitsu Sparclite
21277 @kindex target sparclite
21278 @item target sparclite @var{dev}
21279 Fujitsu sparclite boards, used only for the purpose of loading.
21280 You must use an additional command to debug the program.
21281 For example: target remote @var{dev} using @value{GDBN} standard
21287 @subsection Zilog Z8000
21290 @cindex simulator, Z8000
21291 @cindex Zilog Z8000 simulator
21293 When configured for debugging Zilog Z8000 targets, @value{GDBN} includes
21296 For the Z8000 family, @samp{target sim} simulates either the Z8002 (the
21297 unsegmented variant of the Z8000 architecture) or the Z8001 (the
21298 segmented variant). The simulator recognizes which architecture is
21299 appropriate by inspecting the object code.
21302 @item target sim @var{args}
21304 @kindex target sim@r{, with Z8000}
21305 Debug programs on a simulated CPU. If the simulator supports setup
21306 options, specify them via @var{args}.
21310 After specifying this target, you can debug programs for the simulated
21311 CPU in the same style as programs for your host computer; use the
21312 @code{file} command to load a new program image, the @code{run} command
21313 to run your program, and so on.
21315 As well as making available all the usual machine registers
21316 (@pxref{Registers, ,Registers}), the Z8000 simulator provides three
21317 additional items of information as specially named registers:
21322 Counts clock-ticks in the simulator.
21325 Counts instructions run in the simulator.
21328 Execution time in 60ths of a second.
21332 You can refer to these values in @value{GDBN} expressions with the usual
21333 conventions; for example, @w{@samp{b fputc if $cycles>5000}} sets a
21334 conditional breakpoint that suspends only after at least 5000
21335 simulated clock ticks.
21338 @subsection Atmel AVR
21341 When configured for debugging the Atmel AVR, @value{GDBN} supports the
21342 following AVR-specific commands:
21345 @item info io_registers
21346 @kindex info io_registers@r{, AVR}
21347 @cindex I/O registers (Atmel AVR)
21348 This command displays information about the AVR I/O registers. For
21349 each register, @value{GDBN} prints its number and value.
21356 When configured for debugging CRIS, @value{GDBN} provides the
21357 following CRIS-specific commands:
21360 @item set cris-version @var{ver}
21361 @cindex CRIS version
21362 Set the current CRIS version to @var{ver}, either @samp{10} or @samp{32}.
21363 The CRIS version affects register names and sizes. This command is useful in
21364 case autodetection of the CRIS version fails.
21366 @item show cris-version
21367 Show the current CRIS version.
21369 @item set cris-dwarf2-cfi
21370 @cindex DWARF-2 CFI and CRIS
21371 Set the usage of DWARF-2 CFI for CRIS debugging. The default is @samp{on}.
21372 Change to @samp{off} when using @code{gcc-cris} whose version is below
21375 @item show cris-dwarf2-cfi
21376 Show the current state of using DWARF-2 CFI.
21378 @item set cris-mode @var{mode}
21380 Set the current CRIS mode to @var{mode}. It should only be changed when
21381 debugging in guru mode, in which case it should be set to
21382 @samp{guru} (the default is @samp{normal}).
21384 @item show cris-mode
21385 Show the current CRIS mode.
21389 @subsection Renesas Super-H
21392 For the Renesas Super-H processor, @value{GDBN} provides these
21396 @item set sh calling-convention @var{convention}
21397 @kindex set sh calling-convention
21398 Set the calling-convention used when calling functions from @value{GDBN}.
21399 Allowed values are @samp{gcc}, which is the default setting, and @samp{renesas}.
21400 With the @samp{gcc} setting, functions are called using the @value{NGCC} calling
21401 convention. If the DWARF-2 information of the called function specifies
21402 that the function follows the Renesas calling convention, the function
21403 is called using the Renesas calling convention. If the calling convention
21404 is set to @samp{renesas}, the Renesas calling convention is always used,
21405 regardless of the DWARF-2 information. This can be used to override the
21406 default of @samp{gcc} if debug information is missing, or the compiler
21407 does not emit the DWARF-2 calling convention entry for a function.
21409 @item show sh calling-convention
21410 @kindex show sh calling-convention
21411 Show the current calling convention setting.
21416 @node Architectures
21417 @section Architectures
21419 This section describes characteristics of architectures that affect
21420 all uses of @value{GDBN} with the architecture, both native and cross.
21427 * HPPA:: HP PA architecture
21428 * SPU:: Cell Broadband Engine SPU architecture
21434 @subsection AArch64
21435 @cindex AArch64 support
21437 When @value{GDBN} is debugging the AArch64 architecture, it provides the
21438 following special commands:
21441 @item set debug aarch64
21442 @kindex set debug aarch64
21443 This command determines whether AArch64 architecture-specific debugging
21444 messages are to be displayed.
21446 @item show debug aarch64
21447 Show whether AArch64 debugging messages are displayed.
21452 @subsection x86 Architecture-specific Issues
21455 @item set struct-convention @var{mode}
21456 @kindex set struct-convention
21457 @cindex struct return convention
21458 @cindex struct/union returned in registers
21459 Set the convention used by the inferior to return @code{struct}s and
21460 @code{union}s from functions to @var{mode}. Possible values of
21461 @var{mode} are @code{"pcc"}, @code{"reg"}, and @code{"default"} (the
21462 default). @code{"default"} or @code{"pcc"} means that @code{struct}s
21463 are returned on the stack, while @code{"reg"} means that a
21464 @code{struct} or a @code{union} whose size is 1, 2, 4, or 8 bytes will
21465 be returned in a register.
21467 @item show struct-convention
21468 @kindex show struct-convention
21469 Show the current setting of the convention to return @code{struct}s
21473 @subsubsection Intel(R) @dfn{Memory Protection Extensions} (MPX).
21474 @cindex Intel(R) Memory Protection Extensions (MPX).
21476 Memory Protection Extension (MPX) adds the bound registers @samp{BND0}
21477 @footnote{The register named with capital letters represent the architecture
21478 registers.} through @samp{BND3}. Bound registers store a pair of 64-bit values
21479 which are the lower bound and upper bound. Bounds are effective addresses or
21480 memory locations. The upper bounds are architecturally represented in 1's
21481 complement form. A bound having lower bound = 0, and upper bound = 0
21482 (1's complement of all bits set) will allow access to the entire address space.
21484 @samp{BND0} through @samp{BND3} are represented in @value{GDBN} as @samp{bnd0raw}
21485 through @samp{bnd3raw}. Pseudo registers @samp{bnd0} through @samp{bnd3}
21486 display the upper bound performing the complement of one operation on the
21487 upper bound value, i.e.@ when upper bound in @samp{bnd0raw} is 0 in the
21488 @value{GDBN} @samp{bnd0} it will be @code{0xfff@dots{}}. In this sense it
21489 can also be noted that the upper bounds are inclusive.
21491 As an example, assume that the register BND0 holds bounds for a pointer having
21492 access allowed for the range between 0x32 and 0x71. The values present on
21493 bnd0raw and bnd registers are presented as follows:
21496 bnd0raw = @{0x32, 0xffffffff8e@}
21497 bnd0 = @{lbound = 0x32, ubound = 0x71@} : size 64
21500 This way the raw value can be accessed via bnd0raw@dots{}bnd3raw. Any
21501 change on bnd0@dots{}bnd3 or bnd0raw@dots{}bnd3raw is reflect on its
21502 counterpart. When the bnd0@dots{}bnd3 registers are displayed via
21503 Python, the display includes the memory size, in bits, accessible to
21509 See the following section.
21512 @subsection @acronym{MIPS}
21514 @cindex stack on Alpha
21515 @cindex stack on @acronym{MIPS}
21516 @cindex Alpha stack
21517 @cindex @acronym{MIPS} stack
21518 Alpha- and @acronym{MIPS}-based computers use an unusual stack frame, which
21519 sometimes requires @value{GDBN} to search backward in the object code to
21520 find the beginning of a function.
21522 @cindex response time, @acronym{MIPS} debugging
21523 To improve response time (especially for embedded applications, where
21524 @value{GDBN} may be restricted to a slow serial line for this search)
21525 you may want to limit the size of this search, using one of these
21529 @cindex @code{heuristic-fence-post} (Alpha, @acronym{MIPS})
21530 @item set heuristic-fence-post @var{limit}
21531 Restrict @value{GDBN} to examining at most @var{limit} bytes in its
21532 search for the beginning of a function. A value of @var{0} (the
21533 default) means there is no limit. However, except for @var{0}, the
21534 larger the limit the more bytes @code{heuristic-fence-post} must search
21535 and therefore the longer it takes to run. You should only need to use
21536 this command when debugging a stripped executable.
21538 @item show heuristic-fence-post
21539 Display the current limit.
21543 These commands are available @emph{only} when @value{GDBN} is configured
21544 for debugging programs on Alpha or @acronym{MIPS} processors.
21546 Several @acronym{MIPS}-specific commands are available when debugging @acronym{MIPS}
21550 @item set mips abi @var{arg}
21551 @kindex set mips abi
21552 @cindex set ABI for @acronym{MIPS}
21553 Tell @value{GDBN} which @acronym{MIPS} ABI is used by the inferior. Possible
21554 values of @var{arg} are:
21558 The default ABI associated with the current binary (this is the
21568 @item show mips abi
21569 @kindex show mips abi
21570 Show the @acronym{MIPS} ABI used by @value{GDBN} to debug the inferior.
21572 @item set mips compression @var{arg}
21573 @kindex set mips compression
21574 @cindex code compression, @acronym{MIPS}
21575 Tell @value{GDBN} which @acronym{MIPS} compressed
21576 @acronym{ISA, Instruction Set Architecture} encoding is used by the
21577 inferior. @value{GDBN} uses this for code disassembly and other
21578 internal interpretation purposes. This setting is only referred to
21579 when no executable has been associated with the debugging session or
21580 the executable does not provide information about the encoding it uses.
21581 Otherwise this setting is automatically updated from information
21582 provided by the executable.
21584 Possible values of @var{arg} are @samp{mips16} and @samp{micromips}.
21585 The default compressed @acronym{ISA} encoding is @samp{mips16}, as
21586 executables containing @acronym{MIPS16} code frequently are not
21587 identified as such.
21589 This setting is ``sticky''; that is, it retains its value across
21590 debugging sessions until reset either explicitly with this command or
21591 implicitly from an executable.
21593 The compiler and/or assembler typically add symbol table annotations to
21594 identify functions compiled for the @acronym{MIPS16} or
21595 @acronym{microMIPS} @acronym{ISA}s. If these function-scope annotations
21596 are present, @value{GDBN} uses them in preference to the global
21597 compressed @acronym{ISA} encoding setting.
21599 @item show mips compression
21600 @kindex show mips compression
21601 Show the @acronym{MIPS} compressed @acronym{ISA} encoding used by
21602 @value{GDBN} to debug the inferior.
21605 @itemx show mipsfpu
21606 @xref{MIPS Embedded, set mipsfpu}.
21608 @item set mips mask-address @var{arg}
21609 @kindex set mips mask-address
21610 @cindex @acronym{MIPS} addresses, masking
21611 This command determines whether the most-significant 32 bits of 64-bit
21612 @acronym{MIPS} addresses are masked off. The argument @var{arg} can be
21613 @samp{on}, @samp{off}, or @samp{auto}. The latter is the default
21614 setting, which lets @value{GDBN} determine the correct value.
21616 @item show mips mask-address
21617 @kindex show mips mask-address
21618 Show whether the upper 32 bits of @acronym{MIPS} addresses are masked off or
21621 @item set remote-mips64-transfers-32bit-regs
21622 @kindex set remote-mips64-transfers-32bit-regs
21623 This command controls compatibility with 64-bit @acronym{MIPS} targets that
21624 transfer data in 32-bit quantities. If you have an old @acronym{MIPS} 64 target
21625 that transfers 32 bits for some registers, like @sc{sr} and @sc{fsr},
21626 and 64 bits for other registers, set this option to @samp{on}.
21628 @item show remote-mips64-transfers-32bit-regs
21629 @kindex show remote-mips64-transfers-32bit-regs
21630 Show the current setting of compatibility with older @acronym{MIPS} 64 targets.
21632 @item set debug mips
21633 @kindex set debug mips
21634 This command turns on and off debugging messages for the @acronym{MIPS}-specific
21635 target code in @value{GDBN}.
21637 @item show debug mips
21638 @kindex show debug mips
21639 Show the current setting of @acronym{MIPS} debugging messages.
21645 @cindex HPPA support
21647 When @value{GDBN} is debugging the HP PA architecture, it provides the
21648 following special commands:
21651 @item set debug hppa
21652 @kindex set debug hppa
21653 This command determines whether HPPA architecture-specific debugging
21654 messages are to be displayed.
21656 @item show debug hppa
21657 Show whether HPPA debugging messages are displayed.
21659 @item maint print unwind @var{address}
21660 @kindex maint print unwind@r{, HPPA}
21661 This command displays the contents of the unwind table entry at the
21662 given @var{address}.
21668 @subsection Cell Broadband Engine SPU architecture
21669 @cindex Cell Broadband Engine
21672 When @value{GDBN} is debugging the Cell Broadband Engine SPU architecture,
21673 it provides the following special commands:
21676 @item info spu event
21678 Display SPU event facility status. Shows current event mask
21679 and pending event status.
21681 @item info spu signal
21682 Display SPU signal notification facility status. Shows pending
21683 signal-control word and signal notification mode of both signal
21684 notification channels.
21686 @item info spu mailbox
21687 Display SPU mailbox facility status. Shows all pending entries,
21688 in order of processing, in each of the SPU Write Outbound,
21689 SPU Write Outbound Interrupt, and SPU Read Inbound mailboxes.
21692 Display MFC DMA status. Shows all pending commands in the MFC
21693 DMA queue. For each entry, opcode, tag, class IDs, effective
21694 and local store addresses and transfer size are shown.
21696 @item info spu proxydma
21697 Display MFC Proxy-DMA status. Shows all pending commands in the MFC
21698 Proxy-DMA queue. For each entry, opcode, tag, class IDs, effective
21699 and local store addresses and transfer size are shown.
21703 When @value{GDBN} is debugging a combined PowerPC/SPU application
21704 on the Cell Broadband Engine, it provides in addition the following
21708 @item set spu stop-on-load @var{arg}
21710 Set whether to stop for new SPE threads. When set to @code{on}, @value{GDBN}
21711 will give control to the user when a new SPE thread enters its @code{main}
21712 function. The default is @code{off}.
21714 @item show spu stop-on-load
21716 Show whether to stop for new SPE threads.
21718 @item set spu auto-flush-cache @var{arg}
21719 Set whether to automatically flush the software-managed cache. When set to
21720 @code{on}, @value{GDBN} will automatically cause the SPE software-managed
21721 cache to be flushed whenever SPE execution stops. This provides a consistent
21722 view of PowerPC memory that is accessed via the cache. If an application
21723 does not use the software-managed cache, this option has no effect.
21725 @item show spu auto-flush-cache
21726 Show whether to automatically flush the software-managed cache.
21731 @subsection PowerPC
21732 @cindex PowerPC architecture
21734 When @value{GDBN} is debugging the PowerPC architecture, it provides a set of
21735 pseudo-registers to enable inspection of 128-bit wide Decimal Floating Point
21736 numbers stored in the floating point registers. These values must be stored
21737 in two consecutive registers, always starting at an even register like
21738 @code{f0} or @code{f2}.
21740 The pseudo-registers go from @code{$dl0} through @code{$dl15}, and are formed
21741 by joining the even/odd register pairs @code{f0} and @code{f1} for @code{$dl0},
21742 @code{f2} and @code{f3} for @code{$dl1} and so on.
21744 For POWER7 processors, @value{GDBN} provides a set of pseudo-registers, the 64-bit
21745 wide Extended Floating Point Registers (@samp{f32} through @samp{f63}).
21748 @subsection Nios II
21749 @cindex Nios II architecture
21751 When @value{GDBN} is debugging the Nios II architecture,
21752 it provides the following special commands:
21756 @item set debug nios2
21757 @kindex set debug nios2
21758 This command turns on and off debugging messages for the Nios II
21759 target code in @value{GDBN}.
21761 @item show debug nios2
21762 @kindex show debug nios2
21763 Show the current setting of Nios II debugging messages.
21766 @node Controlling GDB
21767 @chapter Controlling @value{GDBN}
21769 You can alter the way @value{GDBN} interacts with you by using the
21770 @code{set} command. For commands controlling how @value{GDBN} displays
21771 data, see @ref{Print Settings, ,Print Settings}. Other settings are
21776 * Editing:: Command editing
21777 * Command History:: Command history
21778 * Screen Size:: Screen size
21779 * Numbers:: Numbers
21780 * ABI:: Configuring the current ABI
21781 * Auto-loading:: Automatically loading associated files
21782 * Messages/Warnings:: Optional warnings and messages
21783 * Debugging Output:: Optional messages about internal happenings
21784 * Other Misc Settings:: Other Miscellaneous Settings
21792 @value{GDBN} indicates its readiness to read a command by printing a string
21793 called the @dfn{prompt}. This string is normally @samp{(@value{GDBP})}. You
21794 can change the prompt string with the @code{set prompt} command. For
21795 instance, when debugging @value{GDBN} with @value{GDBN}, it is useful to change
21796 the prompt in one of the @value{GDBN} sessions so that you can always tell
21797 which one you are talking to.
21799 @emph{Note:} @code{set prompt} does not add a space for you after the
21800 prompt you set. This allows you to set a prompt which ends in a space
21801 or a prompt that does not.
21805 @item set prompt @var{newprompt}
21806 Directs @value{GDBN} to use @var{newprompt} as its prompt string henceforth.
21808 @kindex show prompt
21810 Prints a line of the form: @samp{Gdb's prompt is: @var{your-prompt}}
21813 Versions of @value{GDBN} that ship with Python scripting enabled have
21814 prompt extensions. The commands for interacting with these extensions
21818 @kindex set extended-prompt
21819 @item set extended-prompt @var{prompt}
21820 Set an extended prompt that allows for substitutions.
21821 @xref{gdb.prompt}, for a list of escape sequences that can be used for
21822 substitution. Any escape sequences specified as part of the prompt
21823 string are replaced with the corresponding strings each time the prompt
21829 set extended-prompt Current working directory: \w (gdb)
21832 Note that when an extended-prompt is set, it takes control of the
21833 @var{prompt_hook} hook. @xref{prompt_hook}, for further information.
21835 @kindex show extended-prompt
21836 @item show extended-prompt
21837 Prints the extended prompt. Any escape sequences specified as part of
21838 the prompt string with @code{set extended-prompt}, are replaced with the
21839 corresponding strings each time the prompt is displayed.
21843 @section Command Editing
21845 @cindex command line editing
21847 @value{GDBN} reads its input commands via the @dfn{Readline} interface. This
21848 @sc{gnu} library provides consistent behavior for programs which provide a
21849 command line interface to the user. Advantages are @sc{gnu} Emacs-style
21850 or @dfn{vi}-style inline editing of commands, @code{csh}-like history
21851 substitution, and a storage and recall of command history across
21852 debugging sessions.
21854 You may control the behavior of command line editing in @value{GDBN} with the
21855 command @code{set}.
21858 @kindex set editing
21861 @itemx set editing on
21862 Enable command line editing (enabled by default).
21864 @item set editing off
21865 Disable command line editing.
21867 @kindex show editing
21869 Show whether command line editing is enabled.
21872 @ifset SYSTEM_READLINE
21873 @xref{Command Line Editing, , , rluserman, GNU Readline Library},
21875 @ifclear SYSTEM_READLINE
21876 @xref{Command Line Editing},
21878 for more details about the Readline
21879 interface. Users unfamiliar with @sc{gnu} Emacs or @code{vi} are
21880 encouraged to read that chapter.
21882 @node Command History
21883 @section Command History
21884 @cindex command history
21886 @value{GDBN} can keep track of the commands you type during your
21887 debugging sessions, so that you can be certain of precisely what
21888 happened. Use these commands to manage the @value{GDBN} command
21891 @value{GDBN} uses the @sc{gnu} History library, a part of the Readline
21892 package, to provide the history facility.
21893 @ifset SYSTEM_READLINE
21894 @xref{Using History Interactively, , , history, GNU History Library},
21896 @ifclear SYSTEM_READLINE
21897 @xref{Using History Interactively},
21899 for the detailed description of the History library.
21901 To issue a command to @value{GDBN} without affecting certain aspects of
21902 the state which is seen by users, prefix it with @samp{server }
21903 (@pxref{Server Prefix}). This
21904 means that this command will not affect the command history, nor will it
21905 affect @value{GDBN}'s notion of which command to repeat if @key{RET} is
21906 pressed on a line by itself.
21908 @cindex @code{server}, command prefix
21909 The server prefix does not affect the recording of values into the value
21910 history; to print a value without recording it into the value history,
21911 use the @code{output} command instead of the @code{print} command.
21913 Here is the description of @value{GDBN} commands related to command
21917 @cindex history substitution
21918 @cindex history file
21919 @kindex set history filename
21920 @cindex @env{GDBHISTFILE}, environment variable
21921 @item set history filename @var{fname}
21922 Set the name of the @value{GDBN} command history file to @var{fname}.
21923 This is the file where @value{GDBN} reads an initial command history
21924 list, and where it writes the command history from this session when it
21925 exits. You can access this list through history expansion or through
21926 the history command editing characters listed below. This file defaults
21927 to the value of the environment variable @code{GDBHISTFILE}, or to
21928 @file{./.gdb_history} (@file{./_gdb_history} on MS-DOS) if this variable
21931 @cindex save command history
21932 @kindex set history save
21933 @item set history save
21934 @itemx set history save on
21935 Record command history in a file, whose name may be specified with the
21936 @code{set history filename} command. By default, this option is disabled.
21938 @item set history save off
21939 Stop recording command history in a file.
21941 @cindex history size
21942 @kindex set history size
21943 @cindex @env{HISTSIZE}, environment variable
21944 @item set history size @var{size}
21945 @itemx set history size unlimited
21946 Set the number of commands which @value{GDBN} keeps in its history list.
21947 This defaults to the value of the environment variable
21948 @code{HISTSIZE}, or to 256 if this variable is not set. If @var{size}
21949 is @code{unlimited}, the number of commands @value{GDBN} keeps in the
21950 history list is unlimited.
21953 History expansion assigns special meaning to the character @kbd{!}.
21954 @ifset SYSTEM_READLINE
21955 @xref{Event Designators, , , history, GNU History Library},
21957 @ifclear SYSTEM_READLINE
21958 @xref{Event Designators},
21962 @cindex history expansion, turn on/off
21963 Since @kbd{!} is also the logical not operator in C, history expansion
21964 is off by default. If you decide to enable history expansion with the
21965 @code{set history expansion on} command, you may sometimes need to
21966 follow @kbd{!} (when it is used as logical not, in an expression) with
21967 a space or a tab to prevent it from being expanded. The readline
21968 history facilities do not attempt substitution on the strings
21969 @kbd{!=} and @kbd{!(}, even when history expansion is enabled.
21971 The commands to control history expansion are:
21974 @item set history expansion on
21975 @itemx set history expansion
21976 @kindex set history expansion
21977 Enable history expansion. History expansion is off by default.
21979 @item set history expansion off
21980 Disable history expansion.
21983 @kindex show history
21985 @itemx show history filename
21986 @itemx show history save
21987 @itemx show history size
21988 @itemx show history expansion
21989 These commands display the state of the @value{GDBN} history parameters.
21990 @code{show history} by itself displays all four states.
21995 @kindex show commands
21996 @cindex show last commands
21997 @cindex display command history
21998 @item show commands
21999 Display the last ten commands in the command history.
22001 @item show commands @var{n}
22002 Print ten commands centered on command number @var{n}.
22004 @item show commands +
22005 Print ten commands just after the commands last printed.
22009 @section Screen Size
22010 @cindex size of screen
22011 @cindex pauses in output
22013 Certain commands to @value{GDBN} may produce large amounts of
22014 information output to the screen. To help you read all of it,
22015 @value{GDBN} pauses and asks you for input at the end of each page of
22016 output. Type @key{RET} when you want to continue the output, or @kbd{q}
22017 to discard the remaining output. Also, the screen width setting
22018 determines when to wrap lines of output. Depending on what is being
22019 printed, @value{GDBN} tries to break the line at a readable place,
22020 rather than simply letting it overflow onto the following line.
22022 Normally @value{GDBN} knows the size of the screen from the terminal
22023 driver software. For example, on Unix @value{GDBN} uses the termcap data base
22024 together with the value of the @code{TERM} environment variable and the
22025 @code{stty rows} and @code{stty cols} settings. If this is not correct,
22026 you can override it with the @code{set height} and @code{set
22033 @kindex show height
22034 @item set height @var{lpp}
22035 @itemx set height unlimited
22037 @itemx set width @var{cpl}
22038 @itemx set width unlimited
22040 These @code{set} commands specify a screen height of @var{lpp} lines and
22041 a screen width of @var{cpl} characters. The associated @code{show}
22042 commands display the current settings.
22044 If you specify a height of either @code{unlimited} or zero lines,
22045 @value{GDBN} does not pause during output no matter how long the
22046 output is. This is useful if output is to a file or to an editor
22049 Likewise, you can specify @samp{set width unlimited} or @samp{set
22050 width 0} to prevent @value{GDBN} from wrapping its output.
22052 @item set pagination on
22053 @itemx set pagination off
22054 @kindex set pagination
22055 Turn the output pagination on or off; the default is on. Turning
22056 pagination off is the alternative to @code{set height unlimited}. Note that
22057 running @value{GDBN} with the @option{--batch} option (@pxref{Mode
22058 Options, -batch}) also automatically disables pagination.
22060 @item show pagination
22061 @kindex show pagination
22062 Show the current pagination mode.
22067 @cindex number representation
22068 @cindex entering numbers
22070 You can always enter numbers in octal, decimal, or hexadecimal in
22071 @value{GDBN} by the usual conventions: octal numbers begin with
22072 @samp{0}, decimal numbers end with @samp{.}, and hexadecimal numbers
22073 begin with @samp{0x}. Numbers that neither begin with @samp{0} or
22074 @samp{0x}, nor end with a @samp{.} are, by default, entered in base
22075 10; likewise, the default display for numbers---when no particular
22076 format is specified---is base 10. You can change the default base for
22077 both input and output with the commands described below.
22080 @kindex set input-radix
22081 @item set input-radix @var{base}
22082 Set the default base for numeric input. Supported choices
22083 for @var{base} are decimal 8, 10, or 16. @var{base} must itself be
22084 specified either unambiguously or using the current input radix; for
22088 set input-radix 012
22089 set input-radix 10.
22090 set input-radix 0xa
22094 sets the input base to decimal. On the other hand, @samp{set input-radix 10}
22095 leaves the input radix unchanged, no matter what it was, since
22096 @samp{10}, being without any leading or trailing signs of its base, is
22097 interpreted in the current radix. Thus, if the current radix is 16,
22098 @samp{10} is interpreted in hex, i.e.@: as 16 decimal, which doesn't
22101 @kindex set output-radix
22102 @item set output-radix @var{base}
22103 Set the default base for numeric display. Supported choices
22104 for @var{base} are decimal 8, 10, or 16. @var{base} must itself be
22105 specified either unambiguously or using the current input radix.
22107 @kindex show input-radix
22108 @item show input-radix
22109 Display the current default base for numeric input.
22111 @kindex show output-radix
22112 @item show output-radix
22113 Display the current default base for numeric display.
22115 @item set radix @r{[}@var{base}@r{]}
22119 These commands set and show the default base for both input and output
22120 of numbers. @code{set radix} sets the radix of input and output to
22121 the same base; without an argument, it resets the radix back to its
22122 default value of 10.
22127 @section Configuring the Current ABI
22129 @value{GDBN} can determine the @dfn{ABI} (Application Binary Interface) of your
22130 application automatically. However, sometimes you need to override its
22131 conclusions. Use these commands to manage @value{GDBN}'s view of the
22137 @cindex Newlib OS ABI and its influence on the longjmp handling
22139 One @value{GDBN} configuration can debug binaries for multiple operating
22140 system targets, either via remote debugging or native emulation.
22141 @value{GDBN} will autodetect the @dfn{OS ABI} (Operating System ABI) in use,
22142 but you can override its conclusion using the @code{set osabi} command.
22143 One example where this is useful is in debugging of binaries which use
22144 an alternate C library (e.g.@: @sc{uClibc} for @sc{gnu}/Linux) which does
22145 not have the same identifying marks that the standard C library for your
22148 When @value{GDBN} is debugging the AArch64 architecture, it provides a
22149 ``Newlib'' OS ABI. This is useful for handling @code{setjmp} and
22150 @code{longjmp} when debugging binaries that use the @sc{newlib} C library.
22151 The ``Newlib'' OS ABI can be selected by @code{set osabi Newlib}.
22155 Show the OS ABI currently in use.
22158 With no argument, show the list of registered available OS ABI's.
22160 @item set osabi @var{abi}
22161 Set the current OS ABI to @var{abi}.
22164 @cindex float promotion
22166 Generally, the way that an argument of type @code{float} is passed to a
22167 function depends on whether the function is prototyped. For a prototyped
22168 (i.e.@: ANSI/ISO style) function, @code{float} arguments are passed unchanged,
22169 according to the architecture's convention for @code{float}. For unprototyped
22170 (i.e.@: K&R style) functions, @code{float} arguments are first promoted to type
22171 @code{double} and then passed.
22173 Unfortunately, some forms of debug information do not reliably indicate whether
22174 a function is prototyped. If @value{GDBN} calls a function that is not marked
22175 as prototyped, it consults @kbd{set coerce-float-to-double}.
22178 @kindex set coerce-float-to-double
22179 @item set coerce-float-to-double
22180 @itemx set coerce-float-to-double on
22181 Arguments of type @code{float} will be promoted to @code{double} when passed
22182 to an unprototyped function. This is the default setting.
22184 @item set coerce-float-to-double off
22185 Arguments of type @code{float} will be passed directly to unprototyped
22188 @kindex show coerce-float-to-double
22189 @item show coerce-float-to-double
22190 Show the current setting of promoting @code{float} to @code{double}.
22194 @kindex show cp-abi
22195 @value{GDBN} needs to know the ABI used for your program's C@t{++}
22196 objects. The correct C@t{++} ABI depends on which C@t{++} compiler was
22197 used to build your application. @value{GDBN} only fully supports
22198 programs with a single C@t{++} ABI; if your program contains code using
22199 multiple C@t{++} ABI's or if @value{GDBN} can not identify your
22200 program's ABI correctly, you can tell @value{GDBN} which ABI to use.
22201 Currently supported ABI's include ``gnu-v2'', for @code{g++} versions
22202 before 3.0, ``gnu-v3'', for @code{g++} versions 3.0 and later, and
22203 ``hpaCC'' for the HP ANSI C@t{++} compiler. Other C@t{++} compilers may
22204 use the ``gnu-v2'' or ``gnu-v3'' ABI's as well. The default setting is
22209 Show the C@t{++} ABI currently in use.
22212 With no argument, show the list of supported C@t{++} ABI's.
22214 @item set cp-abi @var{abi}
22215 @itemx set cp-abi auto
22216 Set the current C@t{++} ABI to @var{abi}, or return to automatic detection.
22220 @section Automatically loading associated files
22221 @cindex auto-loading
22223 @value{GDBN} sometimes reads files with commands and settings automatically,
22224 without being explicitly told so by the user. We call this feature
22225 @dfn{auto-loading}. While auto-loading is useful for automatically adapting
22226 @value{GDBN} to the needs of your project, it can sometimes produce unexpected
22227 results or introduce security risks (e.g., if the file comes from untrusted
22231 * Init File in the Current Directory:: @samp{set/show/info auto-load local-gdbinit}
22232 * libthread_db.so.1 file:: @samp{set/show/info auto-load libthread-db}
22234 * Auto-loading safe path:: @samp{set/show/info auto-load safe-path}
22235 * Auto-loading verbose mode:: @samp{set/show debug auto-load}
22238 There are various kinds of files @value{GDBN} can automatically load.
22239 In addition to these files, @value{GDBN} supports auto-loading code written
22240 in various extension languages. @xref{Auto-loading extensions}.
22242 Note that loading of these associated files (including the local @file{.gdbinit}
22243 file) requires accordingly configured @code{auto-load safe-path}
22244 (@pxref{Auto-loading safe path}).
22246 For these reasons, @value{GDBN} includes commands and options to let you
22247 control when to auto-load files and which files should be auto-loaded.
22250 @anchor{set auto-load off}
22251 @kindex set auto-load off
22252 @item set auto-load off
22253 Globally disable loading of all auto-loaded files.
22254 You may want to use this command with the @samp{-iex} option
22255 (@pxref{Option -init-eval-command}) such as:
22257 $ @kbd{gdb -iex "set auto-load off" untrusted-executable corefile}
22260 Be aware that system init file (@pxref{System-wide configuration})
22261 and init files from your home directory (@pxref{Home Directory Init File})
22262 still get read (as they come from generally trusted directories).
22263 To prevent @value{GDBN} from auto-loading even those init files, use the
22264 @option{-nx} option (@pxref{Mode Options}), in addition to
22265 @code{set auto-load no}.
22267 @anchor{show auto-load}
22268 @kindex show auto-load
22269 @item show auto-load
22270 Show whether auto-loading of each specific @samp{auto-load} file(s) is enabled
22274 (gdb) show auto-load
22275 gdb-scripts: Auto-loading of canned sequences of commands scripts is on.
22276 libthread-db: Auto-loading of inferior specific libthread_db is on.
22277 local-gdbinit: Auto-loading of .gdbinit script from current directory
22279 python-scripts: Auto-loading of Python scripts is on.
22280 safe-path: List of directories from which it is safe to auto-load files
22281 is $debugdir:$datadir/auto-load.
22282 scripts-directory: List of directories from which to load auto-loaded scripts
22283 is $debugdir:$datadir/auto-load.
22286 @anchor{info auto-load}
22287 @kindex info auto-load
22288 @item info auto-load
22289 Print whether each specific @samp{auto-load} file(s) have been auto-loaded or
22293 (gdb) info auto-load
22296 Yes /home/user/gdb/gdb-gdb.gdb
22297 libthread-db: No auto-loaded libthread-db.
22298 local-gdbinit: Local .gdbinit file "/home/user/gdb/.gdbinit" has been
22302 Yes /home/user/gdb/gdb-gdb.py
22306 These are @value{GDBN} control commands for the auto-loading:
22308 @multitable @columnfractions .5 .5
22309 @item @xref{set auto-load off}.
22310 @tab Disable auto-loading globally.
22311 @item @xref{show auto-load}.
22312 @tab Show setting of all kinds of files.
22313 @item @xref{info auto-load}.
22314 @tab Show state of all kinds of files.
22315 @item @xref{set auto-load gdb-scripts}.
22316 @tab Control for @value{GDBN} command scripts.
22317 @item @xref{show auto-load gdb-scripts}.
22318 @tab Show setting of @value{GDBN} command scripts.
22319 @item @xref{info auto-load gdb-scripts}.
22320 @tab Show state of @value{GDBN} command scripts.
22321 @item @xref{set auto-load python-scripts}.
22322 @tab Control for @value{GDBN} Python scripts.
22323 @item @xref{show auto-load python-scripts}.
22324 @tab Show setting of @value{GDBN} Python scripts.
22325 @item @xref{info auto-load python-scripts}.
22326 @tab Show state of @value{GDBN} Python scripts.
22327 @item @xref{set auto-load guile-scripts}.
22328 @tab Control for @value{GDBN} Guile scripts.
22329 @item @xref{show auto-load guile-scripts}.
22330 @tab Show setting of @value{GDBN} Guile scripts.
22331 @item @xref{info auto-load guile-scripts}.
22332 @tab Show state of @value{GDBN} Guile scripts.
22333 @item @xref{set auto-load scripts-directory}.
22334 @tab Control for @value{GDBN} auto-loaded scripts location.
22335 @item @xref{show auto-load scripts-directory}.
22336 @tab Show @value{GDBN} auto-loaded scripts location.
22337 @item @xref{set auto-load local-gdbinit}.
22338 @tab Control for init file in the current directory.
22339 @item @xref{show auto-load local-gdbinit}.
22340 @tab Show setting of init file in the current directory.
22341 @item @xref{info auto-load local-gdbinit}.
22342 @tab Show state of init file in the current directory.
22343 @item @xref{set auto-load libthread-db}.
22344 @tab Control for thread debugging library.
22345 @item @xref{show auto-load libthread-db}.
22346 @tab Show setting of thread debugging library.
22347 @item @xref{info auto-load libthread-db}.
22348 @tab Show state of thread debugging library.
22349 @item @xref{set auto-load safe-path}.
22350 @tab Control directories trusted for automatic loading.
22351 @item @xref{show auto-load safe-path}.
22352 @tab Show directories trusted for automatic loading.
22353 @item @xref{add-auto-load-safe-path}.
22354 @tab Add directory trusted for automatic loading.
22357 @node Init File in the Current Directory
22358 @subsection Automatically loading init file in the current directory
22359 @cindex auto-loading init file in the current directory
22361 By default, @value{GDBN} reads and executes the canned sequences of commands
22362 from init file (if any) in the current working directory,
22363 see @ref{Init File in the Current Directory during Startup}.
22365 Note that loading of this local @file{.gdbinit} file also requires accordingly
22366 configured @code{auto-load safe-path} (@pxref{Auto-loading safe path}).
22369 @anchor{set auto-load local-gdbinit}
22370 @kindex set auto-load local-gdbinit
22371 @item set auto-load local-gdbinit [on|off]
22372 Enable or disable the auto-loading of canned sequences of commands
22373 (@pxref{Sequences}) found in init file in the current directory.
22375 @anchor{show auto-load local-gdbinit}
22376 @kindex show auto-load local-gdbinit
22377 @item show auto-load local-gdbinit
22378 Show whether auto-loading of canned sequences of commands from init file in the
22379 current directory is enabled or disabled.
22381 @anchor{info auto-load local-gdbinit}
22382 @kindex info auto-load local-gdbinit
22383 @item info auto-load local-gdbinit
22384 Print whether canned sequences of commands from init file in the
22385 current directory have been auto-loaded.
22388 @node libthread_db.so.1 file
22389 @subsection Automatically loading thread debugging library
22390 @cindex auto-loading libthread_db.so.1
22392 This feature is currently present only on @sc{gnu}/Linux native hosts.
22394 @value{GDBN} reads in some cases thread debugging library from places specific
22395 to the inferior (@pxref{set libthread-db-search-path}).
22397 The special @samp{libthread-db-search-path} entry @samp{$sdir} is processed
22398 without checking this @samp{set auto-load libthread-db} switch as system
22399 libraries have to be trusted in general. In all other cases of
22400 @samp{libthread-db-search-path} entries @value{GDBN} checks first if @samp{set
22401 auto-load libthread-db} is enabled before trying to open such thread debugging
22404 Note that loading of this debugging library also requires accordingly configured
22405 @code{auto-load safe-path} (@pxref{Auto-loading safe path}).
22408 @anchor{set auto-load libthread-db}
22409 @kindex set auto-load libthread-db
22410 @item set auto-load libthread-db [on|off]
22411 Enable or disable the auto-loading of inferior specific thread debugging library.
22413 @anchor{show auto-load libthread-db}
22414 @kindex show auto-load libthread-db
22415 @item show auto-load libthread-db
22416 Show whether auto-loading of inferior specific thread debugging library is
22417 enabled or disabled.
22419 @anchor{info auto-load libthread-db}
22420 @kindex info auto-load libthread-db
22421 @item info auto-load libthread-db
22422 Print the list of all loaded inferior specific thread debugging libraries and
22423 for each such library print list of inferior @var{pid}s using it.
22426 @node Auto-loading safe path
22427 @subsection Security restriction for auto-loading
22428 @cindex auto-loading safe-path
22430 As the files of inferior can come from untrusted source (such as submitted by
22431 an application user) @value{GDBN} does not always load any files automatically.
22432 @value{GDBN} provides the @samp{set auto-load safe-path} setting to list
22433 directories trusted for loading files not explicitly requested by user.
22434 Each directory can also be a shell wildcard pattern.
22436 If the path is not set properly you will see a warning and the file will not
22441 Reading symbols from /home/user/gdb/gdb...done.
22442 warning: File "/home/user/gdb/gdb-gdb.gdb" auto-loading has been
22443 declined by your `auto-load safe-path' set
22444 to "$debugdir:$datadir/auto-load".
22445 warning: File "/home/user/gdb/gdb-gdb.py" auto-loading has been
22446 declined by your `auto-load safe-path' set
22447 to "$debugdir:$datadir/auto-load".
22451 To instruct @value{GDBN} to go ahead and use the init files anyway,
22452 invoke @value{GDBN} like this:
22455 $ gdb -q -iex "set auto-load safe-path /home/user/gdb" ./gdb
22458 The list of trusted directories is controlled by the following commands:
22461 @anchor{set auto-load safe-path}
22462 @kindex set auto-load safe-path
22463 @item set auto-load safe-path @r{[}@var{directories}@r{]}
22464 Set the list of directories (and their subdirectories) trusted for automatic
22465 loading and execution of scripts. You can also enter a specific trusted file.
22466 Each directory can also be a shell wildcard pattern; wildcards do not match
22467 directory separator - see @code{FNM_PATHNAME} for system function @code{fnmatch}
22468 (@pxref{Wildcard Matching, fnmatch, , libc, GNU C Library Reference Manual}).
22469 If you omit @var{directories}, @samp{auto-load safe-path} will be reset to
22470 its default value as specified during @value{GDBN} compilation.
22472 The list of directories uses path separator (@samp{:} on GNU and Unix
22473 systems, @samp{;} on MS-Windows and MS-DOS) to separate directories, similarly
22474 to the @env{PATH} environment variable.
22476 @anchor{show auto-load safe-path}
22477 @kindex show auto-load safe-path
22478 @item show auto-load safe-path
22479 Show the list of directories trusted for automatic loading and execution of
22482 @anchor{add-auto-load-safe-path}
22483 @kindex add-auto-load-safe-path
22484 @item add-auto-load-safe-path
22485 Add an entry (or list of entries) the list of directories trusted for automatic
22486 loading and execution of scripts. Multiple entries may be delimited by the
22487 host platform path separator in use.
22490 This variable defaults to what @code{--with-auto-load-dir} has been configured
22491 to (@pxref{with-auto-load-dir}). @file{$debugdir} and @file{$datadir}
22492 substitution applies the same as for @ref{set auto-load scripts-directory}.
22493 The default @code{set auto-load safe-path} value can be also overriden by
22494 @value{GDBN} configuration option @option{--with-auto-load-safe-path}.
22496 Setting this variable to @file{/} disables this security protection,
22497 corresponding @value{GDBN} configuration option is
22498 @option{--without-auto-load-safe-path}.
22499 This variable is supposed to be set to the system directories writable by the
22500 system superuser only. Users can add their source directories in init files in
22501 their home directories (@pxref{Home Directory Init File}). See also deprecated
22502 init file in the current directory
22503 (@pxref{Init File in the Current Directory during Startup}).
22505 To force @value{GDBN} to load the files it declined to load in the previous
22506 example, you could use one of the following ways:
22509 @item @file{~/.gdbinit}: @samp{add-auto-load-safe-path ~/src/gdb}
22510 Specify this trusted directory (or a file) as additional component of the list.
22511 You have to specify also any existing directories displayed by
22512 by @samp{show auto-load safe-path} (such as @samp{/usr:/bin} in this example).
22514 @item @kbd{gdb -iex "set auto-load safe-path /usr:/bin:~/src/gdb" @dots{}}
22515 Specify this directory as in the previous case but just for a single
22516 @value{GDBN} session.
22518 @item @kbd{gdb -iex "set auto-load safe-path /" @dots{}}
22519 Disable auto-loading safety for a single @value{GDBN} session.
22520 This assumes all the files you debug during this @value{GDBN} session will come
22521 from trusted sources.
22523 @item @kbd{./configure --without-auto-load-safe-path}
22524 During compilation of @value{GDBN} you may disable any auto-loading safety.
22525 This assumes all the files you will ever debug with this @value{GDBN} come from
22529 On the other hand you can also explicitly forbid automatic files loading which
22530 also suppresses any such warning messages:
22533 @item @kbd{gdb -iex "set auto-load no" @dots{}}
22534 You can use @value{GDBN} command-line option for a single @value{GDBN} session.
22536 @item @file{~/.gdbinit}: @samp{set auto-load no}
22537 Disable auto-loading globally for the user
22538 (@pxref{Home Directory Init File}). While it is improbable, you could also
22539 use system init file instead (@pxref{System-wide configuration}).
22542 This setting applies to the file names as entered by user. If no entry matches
22543 @value{GDBN} tries as a last resort to also resolve all the file names into
22544 their canonical form (typically resolving symbolic links) and compare the
22545 entries again. @value{GDBN} already canonicalizes most of the filenames on its
22546 own before starting the comparison so a canonical form of directories is
22547 recommended to be entered.
22549 @node Auto-loading verbose mode
22550 @subsection Displaying files tried for auto-load
22551 @cindex auto-loading verbose mode
22553 For better visibility of all the file locations where you can place scripts to
22554 be auto-loaded with inferior --- or to protect yourself against accidental
22555 execution of untrusted scripts --- @value{GDBN} provides a feature for printing
22556 all the files attempted to be loaded. Both existing and non-existing files may
22559 For example the list of directories from which it is safe to auto-load files
22560 (@pxref{Auto-loading safe path}) applies also to canonicalized filenames which
22561 may not be too obvious while setting it up.
22564 (gdb) set debug auto-load on
22565 (gdb) file ~/src/t/true
22566 auto-load: Loading canned sequences of commands script "/tmp/true-gdb.gdb"
22567 for objfile "/tmp/true".
22568 auto-load: Updating directories of "/usr:/opt".
22569 auto-load: Using directory "/usr".
22570 auto-load: Using directory "/opt".
22571 warning: File "/tmp/true-gdb.gdb" auto-loading has been declined
22572 by your `auto-load safe-path' set to "/usr:/opt".
22576 @anchor{set debug auto-load}
22577 @kindex set debug auto-load
22578 @item set debug auto-load [on|off]
22579 Set whether to print the filenames attempted to be auto-loaded.
22581 @anchor{show debug auto-load}
22582 @kindex show debug auto-load
22583 @item show debug auto-load
22584 Show whether printing of the filenames attempted to be auto-loaded is turned
22588 @node Messages/Warnings
22589 @section Optional Warnings and Messages
22591 @cindex verbose operation
22592 @cindex optional warnings
22593 By default, @value{GDBN} is silent about its inner workings. If you are
22594 running on a slow machine, you may want to use the @code{set verbose}
22595 command. This makes @value{GDBN} tell you when it does a lengthy
22596 internal operation, so you will not think it has crashed.
22598 Currently, the messages controlled by @code{set verbose} are those
22599 which announce that the symbol table for a source file is being read;
22600 see @code{symbol-file} in @ref{Files, ,Commands to Specify Files}.
22603 @kindex set verbose
22604 @item set verbose on
22605 Enables @value{GDBN} output of certain informational messages.
22607 @item set verbose off
22608 Disables @value{GDBN} output of certain informational messages.
22610 @kindex show verbose
22612 Displays whether @code{set verbose} is on or off.
22615 By default, if @value{GDBN} encounters bugs in the symbol table of an
22616 object file, it is silent; but if you are debugging a compiler, you may
22617 find this information useful (@pxref{Symbol Errors, ,Errors Reading
22622 @kindex set complaints
22623 @item set complaints @var{limit}
22624 Permits @value{GDBN} to output @var{limit} complaints about each type of
22625 unusual symbols before becoming silent about the problem. Set
22626 @var{limit} to zero to suppress all complaints; set it to a large number
22627 to prevent complaints from being suppressed.
22629 @kindex show complaints
22630 @item show complaints
22631 Displays how many symbol complaints @value{GDBN} is permitted to produce.
22635 @anchor{confirmation requests}
22636 By default, @value{GDBN} is cautious, and asks what sometimes seems to be a
22637 lot of stupid questions to confirm certain commands. For example, if
22638 you try to run a program which is already running:
22642 The program being debugged has been started already.
22643 Start it from the beginning? (y or n)
22646 If you are willing to unflinchingly face the consequences of your own
22647 commands, you can disable this ``feature'':
22651 @kindex set confirm
22653 @cindex confirmation
22654 @cindex stupid questions
22655 @item set confirm off
22656 Disables confirmation requests. Note that running @value{GDBN} with
22657 the @option{--batch} option (@pxref{Mode Options, -batch}) also
22658 automatically disables confirmation requests.
22660 @item set confirm on
22661 Enables confirmation requests (the default).
22663 @kindex show confirm
22665 Displays state of confirmation requests.
22669 @cindex command tracing
22670 If you need to debug user-defined commands or sourced files you may find it
22671 useful to enable @dfn{command tracing}. In this mode each command will be
22672 printed as it is executed, prefixed with one or more @samp{+} symbols, the
22673 quantity denoting the call depth of each command.
22676 @kindex set trace-commands
22677 @cindex command scripts, debugging
22678 @item set trace-commands on
22679 Enable command tracing.
22680 @item set trace-commands off
22681 Disable command tracing.
22682 @item show trace-commands
22683 Display the current state of command tracing.
22686 @node Debugging Output
22687 @section Optional Messages about Internal Happenings
22688 @cindex optional debugging messages
22690 @value{GDBN} has commands that enable optional debugging messages from
22691 various @value{GDBN} subsystems; normally these commands are of
22692 interest to @value{GDBN} maintainers, or when reporting a bug. This
22693 section documents those commands.
22696 @kindex set exec-done-display
22697 @item set exec-done-display
22698 Turns on or off the notification of asynchronous commands'
22699 completion. When on, @value{GDBN} will print a message when an
22700 asynchronous command finishes its execution. The default is off.
22701 @kindex show exec-done-display
22702 @item show exec-done-display
22703 Displays the current setting of asynchronous command completion
22706 @cindex ARM AArch64
22707 @item set debug aarch64
22708 Turns on or off display of debugging messages related to ARM AArch64.
22709 The default is off.
22711 @item show debug aarch64
22712 Displays the current state of displaying debugging messages related to
22714 @cindex gdbarch debugging info
22715 @cindex architecture debugging info
22716 @item set debug arch
22717 Turns on or off display of gdbarch debugging info. The default is off
22718 @item show debug arch
22719 Displays the current state of displaying gdbarch debugging info.
22720 @item set debug aix-solib
22721 @cindex AIX shared library debugging
22722 Control display of debugging messages from the AIX shared library
22723 support module. The default is off.
22724 @item show debug aix-thread
22725 Show the current state of displaying AIX shared library debugging messages.
22726 @item set debug aix-thread
22727 @cindex AIX threads
22728 Display debugging messages about inner workings of the AIX thread
22730 @item show debug aix-thread
22731 Show the current state of AIX thread debugging info display.
22732 @item set debug check-physname
22734 Check the results of the ``physname'' computation. When reading DWARF
22735 debugging information for C@t{++}, @value{GDBN} attempts to compute
22736 each entity's name. @value{GDBN} can do this computation in two
22737 different ways, depending on exactly what information is present.
22738 When enabled, this setting causes @value{GDBN} to compute the names
22739 both ways and display any discrepancies.
22740 @item show debug check-physname
22741 Show the current state of ``physname'' checking.
22742 @item set debug coff-pe-read
22743 @cindex COFF/PE exported symbols
22744 Control display of debugging messages related to reading of COFF/PE
22745 exported symbols. The default is off.
22746 @item show debug coff-pe-read
22747 Displays the current state of displaying debugging messages related to
22748 reading of COFF/PE exported symbols.
22749 @item set debug dwarf2-die
22750 @cindex DWARF2 DIEs
22751 Dump DWARF2 DIEs after they are read in.
22752 The value is the number of nesting levels to print.
22753 A value of zero turns off the display.
22754 @item show debug dwarf2-die
22755 Show the current state of DWARF2 DIE debugging.
22756 @item set debug dwarf2-read
22757 @cindex DWARF2 Reading
22758 Turns on or off display of debugging messages related to reading
22759 DWARF debug info. The default is 0 (off).
22760 A value of 1 provides basic information.
22761 A value greater than 1 provides more verbose information.
22762 @item show debug dwarf2-read
22763 Show the current state of DWARF2 reader debugging.
22764 @item set debug displaced
22765 @cindex displaced stepping debugging info
22766 Turns on or off display of @value{GDBN} debugging info for the
22767 displaced stepping support. The default is off.
22768 @item show debug displaced
22769 Displays the current state of displaying @value{GDBN} debugging info
22770 related to displaced stepping.
22771 @item set debug event
22772 @cindex event debugging info
22773 Turns on or off display of @value{GDBN} event debugging info. The
22775 @item show debug event
22776 Displays the current state of displaying @value{GDBN} event debugging
22778 @item set debug expression
22779 @cindex expression debugging info
22780 Turns on or off display of debugging info about @value{GDBN}
22781 expression parsing. The default is off.
22782 @item show debug expression
22783 Displays the current state of displaying debugging info about
22784 @value{GDBN} expression parsing.
22785 @item set debug frame
22786 @cindex frame debugging info
22787 Turns on or off display of @value{GDBN} frame debugging info. The
22789 @item show debug frame
22790 Displays the current state of displaying @value{GDBN} frame debugging
22792 @item set debug gnu-nat
22793 @cindex @sc{gnu}/Hurd debug messages
22794 Turns on or off debugging messages from the @sc{gnu}/Hurd debug support.
22795 @item show debug gnu-nat
22796 Show the current state of @sc{gnu}/Hurd debugging messages.
22797 @item set debug infrun
22798 @cindex inferior debugging info
22799 Turns on or off display of @value{GDBN} debugging info for running the inferior.
22800 The default is off. @file{infrun.c} contains GDB's runtime state machine used
22801 for implementing operations such as single-stepping the inferior.
22802 @item show debug infrun
22803 Displays the current state of @value{GDBN} inferior debugging.
22804 @item set debug jit
22805 @cindex just-in-time compilation, debugging messages
22806 Turns on or off debugging messages from JIT debug support.
22807 @item show debug jit
22808 Displays the current state of @value{GDBN} JIT debugging.
22809 @item set debug lin-lwp
22810 @cindex @sc{gnu}/Linux LWP debug messages
22811 @cindex Linux lightweight processes
22812 Turns on or off debugging messages from the Linux LWP debug support.
22813 @item show debug lin-lwp
22814 Show the current state of Linux LWP debugging messages.
22815 @item set debug mach-o
22816 @cindex Mach-O symbols processing
22817 Control display of debugging messages related to Mach-O symbols
22818 processing. The default is off.
22819 @item show debug mach-o
22820 Displays the current state of displaying debugging messages related to
22821 reading of COFF/PE exported symbols.
22822 @item set debug notification
22823 @cindex remote async notification debugging info
22824 Turns on or off debugging messages about remote async notification.
22825 The default is off.
22826 @item show debug notification
22827 Displays the current state of remote async notification debugging messages.
22828 @item set debug observer
22829 @cindex observer debugging info
22830 Turns on or off display of @value{GDBN} observer debugging. This
22831 includes info such as the notification of observable events.
22832 @item show debug observer
22833 Displays the current state of observer debugging.
22834 @item set debug overload
22835 @cindex C@t{++} overload debugging info
22836 Turns on or off display of @value{GDBN} C@t{++} overload debugging
22837 info. This includes info such as ranking of functions, etc. The default
22839 @item show debug overload
22840 Displays the current state of displaying @value{GDBN} C@t{++} overload
22842 @cindex expression parser, debugging info
22843 @cindex debug expression parser
22844 @item set debug parser
22845 Turns on or off the display of expression parser debugging output.
22846 Internally, this sets the @code{yydebug} variable in the expression
22847 parser. @xref{Tracing, , Tracing Your Parser, bison, Bison}, for
22848 details. The default is off.
22849 @item show debug parser
22850 Show the current state of expression parser debugging.
22851 @cindex packets, reporting on stdout
22852 @cindex serial connections, debugging
22853 @cindex debug remote protocol
22854 @cindex remote protocol debugging
22855 @cindex display remote packets
22856 @item set debug remote
22857 Turns on or off display of reports on all packets sent back and forth across
22858 the serial line to the remote machine. The info is printed on the
22859 @value{GDBN} standard output stream. The default is off.
22860 @item show debug remote
22861 Displays the state of display of remote packets.
22862 @item set debug serial
22863 Turns on or off display of @value{GDBN} serial debugging info. The
22865 @item show debug serial
22866 Displays the current state of displaying @value{GDBN} serial debugging
22868 @item set debug solib-frv
22869 @cindex FR-V shared-library debugging
22870 Turns on or off debugging messages for FR-V shared-library code.
22871 @item show debug solib-frv
22872 Display the current state of FR-V shared-library code debugging
22874 @item set debug symfile
22875 @cindex symbol file functions
22876 Turns on or off display of debugging messages related to symbol file functions.
22877 The default is off. @xref{Files}.
22878 @item show debug symfile
22879 Show the current state of symbol file debugging messages.
22880 @item set debug symtab-create
22881 @cindex symbol table creation
22882 Turns on or off display of debugging messages related to symbol table creation.
22883 The default is 0 (off).
22884 A value of 1 provides basic information.
22885 A value greater than 1 provides more verbose information.
22886 @item show debug symtab-create
22887 Show the current state of symbol table creation debugging.
22888 @item set debug target
22889 @cindex target debugging info
22890 Turns on or off display of @value{GDBN} target debugging info. This info
22891 includes what is going on at the target level of GDB, as it happens. The
22892 default is 0. Set it to 1 to track events, and to 2 to also track the
22893 value of large memory transfers. Changes to this flag do not take effect
22894 until the next time you connect to a target or use the @code{run} command.
22895 @item show debug target
22896 Displays the current state of displaying @value{GDBN} target debugging
22898 @item set debug timestamp
22899 @cindex timestampping debugging info
22900 Turns on or off display of timestamps with @value{GDBN} debugging info.
22901 When enabled, seconds and microseconds are displayed before each debugging
22903 @item show debug timestamp
22904 Displays the current state of displaying timestamps with @value{GDBN}
22906 @item set debugvarobj
22907 @cindex variable object debugging info
22908 Turns on or off display of @value{GDBN} variable object debugging
22909 info. The default is off.
22910 @item show debugvarobj
22911 Displays the current state of displaying @value{GDBN} variable object
22913 @item set debug xml
22914 @cindex XML parser debugging
22915 Turns on or off debugging messages for built-in XML parsers.
22916 @item show debug xml
22917 Displays the current state of XML debugging messages.
22920 @node Other Misc Settings
22921 @section Other Miscellaneous Settings
22922 @cindex miscellaneous settings
22925 @kindex set interactive-mode
22926 @item set interactive-mode
22927 If @code{on}, forces @value{GDBN} to assume that GDB was started
22928 in a terminal. In practice, this means that @value{GDBN} should wait
22929 for the user to answer queries generated by commands entered at
22930 the command prompt. If @code{off}, forces @value{GDBN} to operate
22931 in the opposite mode, and it uses the default answers to all queries.
22932 If @code{auto} (the default), @value{GDBN} tries to determine whether
22933 its standard input is a terminal, and works in interactive-mode if it
22934 is, non-interactively otherwise.
22936 In the vast majority of cases, the debugger should be able to guess
22937 correctly which mode should be used. But this setting can be useful
22938 in certain specific cases, such as running a MinGW @value{GDBN}
22939 inside a cygwin window.
22941 @kindex show interactive-mode
22942 @item show interactive-mode
22943 Displays whether the debugger is operating in interactive mode or not.
22946 @node Extending GDB
22947 @chapter Extending @value{GDBN}
22948 @cindex extending GDB
22950 @value{GDBN} provides several mechanisms for extension.
22951 @value{GDBN} also provides the ability to automatically load
22952 extensions when it reads a file for debugging. This allows the
22953 user to automatically customize @value{GDBN} for the program
22957 * Sequences:: Canned Sequences of @value{GDBN} Commands
22958 * Python:: Extending @value{GDBN} using Python
22959 * Guile:: Extending @value{GDBN} using Guile
22960 * Auto-loading extensions:: Automatically loading extensions
22961 * Multiple Extension Languages:: Working with multiple extension languages
22962 * Aliases:: Creating new spellings of existing commands
22965 To facilitate the use of extension languages, @value{GDBN} is capable
22966 of evaluating the contents of a file. When doing so, @value{GDBN}
22967 can recognize which extension language is being used by looking at
22968 the filename extension. Files with an unrecognized filename extension
22969 are always treated as a @value{GDBN} Command Files.
22970 @xref{Command Files,, Command files}.
22972 You can control how @value{GDBN} evaluates these files with the following
22976 @kindex set script-extension
22977 @kindex show script-extension
22978 @item set script-extension off
22979 All scripts are always evaluated as @value{GDBN} Command Files.
22981 @item set script-extension soft
22982 The debugger determines the scripting language based on filename
22983 extension. If this scripting language is supported, @value{GDBN}
22984 evaluates the script using that language. Otherwise, it evaluates
22985 the file as a @value{GDBN} Command File.
22987 @item set script-extension strict
22988 The debugger determines the scripting language based on filename
22989 extension, and evaluates the script using that language. If the
22990 language is not supported, then the evaluation fails.
22992 @item show script-extension
22993 Display the current value of the @code{script-extension} option.
22998 @section Canned Sequences of Commands
23000 Aside from breakpoint commands (@pxref{Break Commands, ,Breakpoint
23001 Command Lists}), @value{GDBN} provides two ways to store sequences of
23002 commands for execution as a unit: user-defined commands and command
23006 * Define:: How to define your own commands
23007 * Hooks:: Hooks for user-defined commands
23008 * Command Files:: How to write scripts of commands to be stored in a file
23009 * Output:: Commands for controlled output
23010 * Auto-loading sequences:: Controlling auto-loaded command files
23014 @subsection User-defined Commands
23016 @cindex user-defined command
23017 @cindex arguments, to user-defined commands
23018 A @dfn{user-defined command} is a sequence of @value{GDBN} commands to
23019 which you assign a new name as a command. This is done with the
23020 @code{define} command. User commands may accept up to 10 arguments
23021 separated by whitespace. Arguments are accessed within the user command
23022 via @code{$arg0@dots{}$arg9}. A trivial example:
23026 print $arg0 + $arg1 + $arg2
23031 To execute the command use:
23038 This defines the command @code{adder}, which prints the sum of
23039 its three arguments. Note the arguments are text substitutions, so they may
23040 reference variables, use complex expressions, or even perform inferior
23043 @cindex argument count in user-defined commands
23044 @cindex how many arguments (user-defined commands)
23045 In addition, @code{$argc} may be used to find out how many arguments have
23046 been passed. This expands to a number in the range 0@dots{}10.
23051 print $arg0 + $arg1
23054 print $arg0 + $arg1 + $arg2
23062 @item define @var{commandname}
23063 Define a command named @var{commandname}. If there is already a command
23064 by that name, you are asked to confirm that you want to redefine it.
23065 @var{commandname} may be a bare command name consisting of letters,
23066 numbers, dashes, and underscores. It may also start with any predefined
23067 prefix command. For example, @samp{define target my-target} creates
23068 a user-defined @samp{target my-target} command.
23070 The definition of the command is made up of other @value{GDBN} command lines,
23071 which are given following the @code{define} command. The end of these
23072 commands is marked by a line containing @code{end}.
23075 @kindex end@r{ (user-defined commands)}
23076 @item document @var{commandname}
23077 Document the user-defined command @var{commandname}, so that it can be
23078 accessed by @code{help}. The command @var{commandname} must already be
23079 defined. This command reads lines of documentation just as @code{define}
23080 reads the lines of the command definition, ending with @code{end}.
23081 After the @code{document} command is finished, @code{help} on command
23082 @var{commandname} displays the documentation you have written.
23084 You may use the @code{document} command again to change the
23085 documentation of a command. Redefining the command with @code{define}
23086 does not change the documentation.
23088 @kindex dont-repeat
23089 @cindex don't repeat command
23091 Used inside a user-defined command, this tells @value{GDBN} that this
23092 command should not be repeated when the user hits @key{RET}
23093 (@pxref{Command Syntax, repeat last command}).
23095 @kindex help user-defined
23096 @item help user-defined
23097 List all user-defined commands and all python commands defined in class
23098 COMAND_USER. The first line of the documentation or docstring is
23103 @itemx show user @var{commandname}
23104 Display the @value{GDBN} commands used to define @var{commandname} (but
23105 not its documentation). If no @var{commandname} is given, display the
23106 definitions for all user-defined commands.
23107 This does not work for user-defined python commands.
23109 @cindex infinite recursion in user-defined commands
23110 @kindex show max-user-call-depth
23111 @kindex set max-user-call-depth
23112 @item show max-user-call-depth
23113 @itemx set max-user-call-depth
23114 The value of @code{max-user-call-depth} controls how many recursion
23115 levels are allowed in user-defined commands before @value{GDBN} suspects an
23116 infinite recursion and aborts the command.
23117 This does not apply to user-defined python commands.
23120 In addition to the above commands, user-defined commands frequently
23121 use control flow commands, described in @ref{Command Files}.
23123 When user-defined commands are executed, the
23124 commands of the definition are not printed. An error in any command
23125 stops execution of the user-defined command.
23127 If used interactively, commands that would ask for confirmation proceed
23128 without asking when used inside a user-defined command. Many @value{GDBN}
23129 commands that normally print messages to say what they are doing omit the
23130 messages when used in a user-defined command.
23133 @subsection User-defined Command Hooks
23134 @cindex command hooks
23135 @cindex hooks, for commands
23136 @cindex hooks, pre-command
23139 You may define @dfn{hooks}, which are a special kind of user-defined
23140 command. Whenever you run the command @samp{foo}, if the user-defined
23141 command @samp{hook-foo} exists, it is executed (with no arguments)
23142 before that command.
23144 @cindex hooks, post-command
23146 A hook may also be defined which is run after the command you executed.
23147 Whenever you run the command @samp{foo}, if the user-defined command
23148 @samp{hookpost-foo} exists, it is executed (with no arguments) after
23149 that command. Post-execution hooks may exist simultaneously with
23150 pre-execution hooks, for the same command.
23152 It is valid for a hook to call the command which it hooks. If this
23153 occurs, the hook is not re-executed, thereby avoiding infinite recursion.
23155 @c It would be nice if hookpost could be passed a parameter indicating
23156 @c if the command it hooks executed properly or not. FIXME!
23158 @kindex stop@r{, a pseudo-command}
23159 In addition, a pseudo-command, @samp{stop} exists. Defining
23160 (@samp{hook-stop}) makes the associated commands execute every time
23161 execution stops in your program: before breakpoint commands are run,
23162 displays are printed, or the stack frame is printed.
23164 For example, to ignore @code{SIGALRM} signals while
23165 single-stepping, but treat them normally during normal execution,
23170 handle SIGALRM nopass
23174 handle SIGALRM pass
23177 define hook-continue
23178 handle SIGALRM pass
23182 As a further example, to hook at the beginning and end of the @code{echo}
23183 command, and to add extra text to the beginning and end of the message,
23191 define hookpost-echo
23195 (@value{GDBP}) echo Hello World
23196 <<<---Hello World--->>>
23201 You can define a hook for any single-word command in @value{GDBN}, but
23202 not for command aliases; you should define a hook for the basic command
23203 name, e.g.@: @code{backtrace} rather than @code{bt}.
23204 @c FIXME! So how does Joe User discover whether a command is an alias
23206 You can hook a multi-word command by adding @code{hook-} or
23207 @code{hookpost-} to the last word of the command, e.g.@:
23208 @samp{define target hook-remote} to add a hook to @samp{target remote}.
23210 If an error occurs during the execution of your hook, execution of
23211 @value{GDBN} commands stops and @value{GDBN} issues a prompt
23212 (before the command that you actually typed had a chance to run).
23214 If you try to define a hook which does not match any known command, you
23215 get a warning from the @code{define} command.
23217 @node Command Files
23218 @subsection Command Files
23220 @cindex command files
23221 @cindex scripting commands
23222 A command file for @value{GDBN} is a text file made of lines that are
23223 @value{GDBN} commands. Comments (lines starting with @kbd{#}) may
23224 also be included. An empty line in a command file does nothing; it
23225 does not mean to repeat the last command, as it would from the
23228 You can request the execution of a command file with the @code{source}
23229 command. Note that the @code{source} command is also used to evaluate
23230 scripts that are not Command Files. The exact behavior can be configured
23231 using the @code{script-extension} setting.
23232 @xref{Extending GDB,, Extending GDB}.
23236 @cindex execute commands from a file
23237 @item source [-s] [-v] @var{filename}
23238 Execute the command file @var{filename}.
23241 The lines in a command file are generally executed sequentially,
23242 unless the order of execution is changed by one of the
23243 @emph{flow-control commands} described below. The commands are not
23244 printed as they are executed. An error in any command terminates
23245 execution of the command file and control is returned to the console.
23247 @value{GDBN} first searches for @var{filename} in the current directory.
23248 If the file is not found there, and @var{filename} does not specify a
23249 directory, then @value{GDBN} also looks for the file on the source search path
23250 (specified with the @samp{directory} command);
23251 except that @file{$cdir} is not searched because the compilation directory
23252 is not relevant to scripts.
23254 If @code{-s} is specified, then @value{GDBN} searches for @var{filename}
23255 on the search path even if @var{filename} specifies a directory.
23256 The search is done by appending @var{filename} to each element of the
23257 search path. So, for example, if @var{filename} is @file{mylib/myscript}
23258 and the search path contains @file{/home/user} then @value{GDBN} will
23259 look for the script @file{/home/user/mylib/myscript}.
23260 The search is also done if @var{filename} is an absolute path.
23261 For example, if @var{filename} is @file{/tmp/myscript} and
23262 the search path contains @file{/home/user} then @value{GDBN} will
23263 look for the script @file{/home/user/tmp/myscript}.
23264 For DOS-like systems, if @var{filename} contains a drive specification,
23265 it is stripped before concatenation. For example, if @var{filename} is
23266 @file{d:myscript} and the search path contains @file{c:/tmp} then @value{GDBN}
23267 will look for the script @file{c:/tmp/myscript}.
23269 If @code{-v}, for verbose mode, is given then @value{GDBN} displays
23270 each command as it is executed. The option must be given before
23271 @var{filename}, and is interpreted as part of the filename anywhere else.
23273 Commands that would ask for confirmation if used interactively proceed
23274 without asking when used in a command file. Many @value{GDBN} commands that
23275 normally print messages to say what they are doing omit the messages
23276 when called from command files.
23278 @value{GDBN} also accepts command input from standard input. In this
23279 mode, normal output goes to standard output and error output goes to
23280 standard error. Errors in a command file supplied on standard input do
23281 not terminate execution of the command file---execution continues with
23285 gdb < cmds > log 2>&1
23288 (The syntax above will vary depending on the shell used.) This example
23289 will execute commands from the file @file{cmds}. All output and errors
23290 would be directed to @file{log}.
23292 Since commands stored on command files tend to be more general than
23293 commands typed interactively, they frequently need to deal with
23294 complicated situations, such as different or unexpected values of
23295 variables and symbols, changes in how the program being debugged is
23296 built, etc. @value{GDBN} provides a set of flow-control commands to
23297 deal with these complexities. Using these commands, you can write
23298 complex scripts that loop over data structures, execute commands
23299 conditionally, etc.
23306 This command allows to include in your script conditionally executed
23307 commands. The @code{if} command takes a single argument, which is an
23308 expression to evaluate. It is followed by a series of commands that
23309 are executed only if the expression is true (its value is nonzero).
23310 There can then optionally be an @code{else} line, followed by a series
23311 of commands that are only executed if the expression was false. The
23312 end of the list is marked by a line containing @code{end}.
23316 This command allows to write loops. Its syntax is similar to
23317 @code{if}: the command takes a single argument, which is an expression
23318 to evaluate, and must be followed by the commands to execute, one per
23319 line, terminated by an @code{end}. These commands are called the
23320 @dfn{body} of the loop. The commands in the body of @code{while} are
23321 executed repeatedly as long as the expression evaluates to true.
23325 This command exits the @code{while} loop in whose body it is included.
23326 Execution of the script continues after that @code{while}s @code{end}
23329 @kindex loop_continue
23330 @item loop_continue
23331 This command skips the execution of the rest of the body of commands
23332 in the @code{while} loop in whose body it is included. Execution
23333 branches to the beginning of the @code{while} loop, where it evaluates
23334 the controlling expression.
23336 @kindex end@r{ (if/else/while commands)}
23338 Terminate the block of commands that are the body of @code{if},
23339 @code{else}, or @code{while} flow-control commands.
23344 @subsection Commands for Controlled Output
23346 During the execution of a command file or a user-defined command, normal
23347 @value{GDBN} output is suppressed; the only output that appears is what is
23348 explicitly printed by the commands in the definition. This section
23349 describes three commands useful for generating exactly the output you
23354 @item echo @var{text}
23355 @c I do not consider backslash-space a standard C escape sequence
23356 @c because it is not in ANSI.
23357 Print @var{text}. Nonprinting characters can be included in
23358 @var{text} using C escape sequences, such as @samp{\n} to print a
23359 newline. @strong{No newline is printed unless you specify one.}
23360 In addition to the standard C escape sequences, a backslash followed
23361 by a space stands for a space. This is useful for displaying a
23362 string with spaces at the beginning or the end, since leading and
23363 trailing spaces are otherwise trimmed from all arguments.
23364 To print @samp{@w{ }and foo =@w{ }}, use the command
23365 @samp{echo \@w{ }and foo = \@w{ }}.
23367 A backslash at the end of @var{text} can be used, as in C, to continue
23368 the command onto subsequent lines. For example,
23371 echo This is some text\n\
23372 which is continued\n\
23373 onto several lines.\n
23376 produces the same output as
23379 echo This is some text\n
23380 echo which is continued\n
23381 echo onto several lines.\n
23385 @item output @var{expression}
23386 Print the value of @var{expression} and nothing but that value: no
23387 newlines, no @samp{$@var{nn} = }. The value is not entered in the
23388 value history either. @xref{Expressions, ,Expressions}, for more information
23391 @item output/@var{fmt} @var{expression}
23392 Print the value of @var{expression} in format @var{fmt}. You can use
23393 the same formats as for @code{print}. @xref{Output Formats,,Output
23394 Formats}, for more information.
23397 @item printf @var{template}, @var{expressions}@dots{}
23398 Print the values of one or more @var{expressions} under the control of
23399 the string @var{template}. To print several values, make
23400 @var{expressions} be a comma-separated list of individual expressions,
23401 which may be either numbers or pointers. Their values are printed as
23402 specified by @var{template}, exactly as a C program would do by
23403 executing the code below:
23406 printf (@var{template}, @var{expressions}@dots{});
23409 As in @code{C} @code{printf}, ordinary characters in @var{template}
23410 are printed verbatim, while @dfn{conversion specification} introduced
23411 by the @samp{%} character cause subsequent @var{expressions} to be
23412 evaluated, their values converted and formatted according to type and
23413 style information encoded in the conversion specifications, and then
23416 For example, you can print two values in hex like this:
23419 printf "foo, bar-foo = 0x%x, 0x%x\n", foo, bar-foo
23422 @code{printf} supports all the standard @code{C} conversion
23423 specifications, including the flags and modifiers between the @samp{%}
23424 character and the conversion letter, with the following exceptions:
23428 The argument-ordering modifiers, such as @samp{2$}, are not supported.
23431 The modifier @samp{*} is not supported for specifying precision or
23435 The @samp{'} flag (for separation of digits into groups according to
23436 @code{LC_NUMERIC'}) is not supported.
23439 The type modifiers @samp{hh}, @samp{j}, @samp{t}, and @samp{z} are not
23443 The conversion letter @samp{n} (as in @samp{%n}) is not supported.
23446 The conversion letters @samp{a} and @samp{A} are not supported.
23450 Note that the @samp{ll} type modifier is supported only if the
23451 underlying @code{C} implementation used to build @value{GDBN} supports
23452 the @code{long long int} type, and the @samp{L} type modifier is
23453 supported only if @code{long double} type is available.
23455 As in @code{C}, @code{printf} supports simple backslash-escape
23456 sequences, such as @code{\n}, @samp{\t}, @samp{\\}, @samp{\"},
23457 @samp{\a}, and @samp{\f}, that consist of backslash followed by a
23458 single character. Octal and hexadecimal escape sequences are not
23461 Additionally, @code{printf} supports conversion specifications for DFP
23462 (@dfn{Decimal Floating Point}) types using the following length modifiers
23463 together with a floating point specifier.
23468 @samp{H} for printing @code{Decimal32} types.
23471 @samp{D} for printing @code{Decimal64} types.
23474 @samp{DD} for printing @code{Decimal128} types.
23477 If the underlying @code{C} implementation used to build @value{GDBN} has
23478 support for the three length modifiers for DFP types, other modifiers
23479 such as width and precision will also be available for @value{GDBN} to use.
23481 In case there is no such @code{C} support, no additional modifiers will be
23482 available and the value will be printed in the standard way.
23484 Here's an example of printing DFP types using the above conversion letters:
23486 printf "D32: %Hf - D64: %Df - D128: %DDf\n",1.2345df,1.2E10dd,1.2E1dl
23490 @item eval @var{template}, @var{expressions}@dots{}
23491 Convert the values of one or more @var{expressions} under the control of
23492 the string @var{template} to a command line, and call it.
23496 @node Auto-loading sequences
23497 @subsection Controlling auto-loading native @value{GDBN} scripts
23498 @cindex native script auto-loading
23500 When a new object file is read (for example, due to the @code{file}
23501 command, or because the inferior has loaded a shared library),
23502 @value{GDBN} will look for the command file @file{@var{objfile}-gdb.gdb}.
23503 @xref{Auto-loading extensions}.
23505 Auto-loading can be enabled or disabled,
23506 and the list of auto-loaded scripts can be printed.
23509 @anchor{set auto-load gdb-scripts}
23510 @kindex set auto-load gdb-scripts
23511 @item set auto-load gdb-scripts [on|off]
23512 Enable or disable the auto-loading of canned sequences of commands scripts.
23514 @anchor{show auto-load gdb-scripts}
23515 @kindex show auto-load gdb-scripts
23516 @item show auto-load gdb-scripts
23517 Show whether auto-loading of canned sequences of commands scripts is enabled or
23520 @anchor{info auto-load gdb-scripts}
23521 @kindex info auto-load gdb-scripts
23522 @cindex print list of auto-loaded canned sequences of commands scripts
23523 @item info auto-load gdb-scripts [@var{regexp}]
23524 Print the list of all canned sequences of commands scripts that @value{GDBN}
23528 If @var{regexp} is supplied only canned sequences of commands scripts with
23529 matching names are printed.
23531 @c Python docs live in a separate file.
23532 @include python.texi
23534 @c Guile docs live in a separate file.
23535 @include guile.texi
23537 @node Auto-loading extensions
23538 @section Auto-loading extensions
23539 @cindex auto-loading extensions
23541 @value{GDBN} provides two mechanisms for automatically loading extensions
23542 when a new object file is read (for example, due to the @code{file}
23543 command, or because the inferior has loaded a shared library):
23544 @file{@var{objfile}-gdb.@var{ext}} and the @code{.debug_gdb_scripts}
23545 section of modern file formats like ELF.
23548 * objfile-gdb.ext file: objfile-gdbdotext file. The @file{@var{objfile}-gdb.@var{ext}} file
23549 * .debug_gdb_scripts section: dotdebug_gdb_scripts section. The @code{.debug_gdb_scripts} section
23550 * Which flavor to choose?::
23553 The auto-loading feature is useful for supplying application-specific
23554 debugging commands and features.
23556 Auto-loading can be enabled or disabled,
23557 and the list of auto-loaded scripts can be printed.
23558 See the @samp{auto-loading} section of each extension language
23559 for more information.
23560 For @value{GDBN} command files see @ref{Auto-loading sequences}.
23561 For Python files see @ref{Python Auto-loading}.
23563 Note that loading of this script file also requires accordingly configured
23564 @code{auto-load safe-path} (@pxref{Auto-loading safe path}).
23566 @node objfile-gdbdotext file
23567 @subsection The @file{@var{objfile}-gdb.@var{ext}} file
23568 @cindex @file{@var{objfile}-gdb.gdb}
23569 @cindex @file{@var{objfile}-gdb.py}
23570 @cindex @file{@var{objfile}-gdb.scm}
23572 When a new object file is read, @value{GDBN} looks for a file named
23573 @file{@var{objfile}-gdb.@var{ext}} (we call it @var{script-name} below),
23574 where @var{objfile} is the object file's name and
23575 where @var{ext} is the file extension for the extension language:
23578 @item @file{@var{objfile}-gdb.gdb}
23579 GDB's own command language
23580 @item @file{@var{objfile}-gdb.py}
23582 @item @file{@var{objfile}-gdb.scm}
23586 @var{script-name} is formed by ensuring that the file name of @var{objfile}
23587 is absolute, following all symlinks, and resolving @code{.} and @code{..}
23588 components, and appending the @file{-gdb.@var{ext}} suffix.
23589 If this file exists and is readable, @value{GDBN} will evaluate it as a
23590 script in the specified extension language.
23592 If this file does not exist, then @value{GDBN} will look for
23593 @var{script-name} file in all of the directories as specified below.
23595 Note that loading of these files requires an accordingly configured
23596 @code{auto-load safe-path} (@pxref{Auto-loading safe path}).
23598 For object files using @file{.exe} suffix @value{GDBN} tries to load first the
23599 scripts normally according to its @file{.exe} filename. But if no scripts are
23600 found @value{GDBN} also tries script filenames matching the object file without
23601 its @file{.exe} suffix. This @file{.exe} stripping is case insensitive and it
23602 is attempted on any platform. This makes the script filenames compatible
23603 between Unix and MS-Windows hosts.
23606 @anchor{set auto-load scripts-directory}
23607 @kindex set auto-load scripts-directory
23608 @item set auto-load scripts-directory @r{[}@var{directories}@r{]}
23609 Control @value{GDBN} auto-loaded scripts location. Multiple directory entries
23610 may be delimited by the host platform path separator in use
23611 (@samp{:} on Unix, @samp{;} on MS-Windows and MS-DOS).
23613 Each entry here needs to be covered also by the security setting
23614 @code{set auto-load safe-path} (@pxref{set auto-load safe-path}).
23616 @anchor{with-auto-load-dir}
23617 This variable defaults to @file{$debugdir:$datadir/auto-load}. The default
23618 @code{set auto-load safe-path} value can be also overriden by @value{GDBN}
23619 configuration option @option{--with-auto-load-dir}.
23621 Any reference to @file{$debugdir} will get replaced by
23622 @var{debug-file-directory} value (@pxref{Separate Debug Files}) and any
23623 reference to @file{$datadir} will get replaced by @var{data-directory} which is
23624 determined at @value{GDBN} startup (@pxref{Data Files}). @file{$debugdir} and
23625 @file{$datadir} must be placed as a directory component --- either alone or
23626 delimited by @file{/} or @file{\} directory separators, depending on the host
23629 The list of directories uses path separator (@samp{:} on GNU and Unix
23630 systems, @samp{;} on MS-Windows and MS-DOS) to separate directories, similarly
23631 to the @env{PATH} environment variable.
23633 @anchor{show auto-load scripts-directory}
23634 @kindex show auto-load scripts-directory
23635 @item show auto-load scripts-directory
23636 Show @value{GDBN} auto-loaded scripts location.
23639 @value{GDBN} does not track which files it has already auto-loaded this way.
23640 @value{GDBN} will load the associated script every time the corresponding
23641 @var{objfile} is opened.
23642 So your @file{-gdb.@var{ext}} file should be careful to avoid errors if it
23643 is evaluated more than once.
23645 @node dotdebug_gdb_scripts section
23646 @subsection The @code{.debug_gdb_scripts} section
23647 @cindex @code{.debug_gdb_scripts} section
23649 For systems using file formats like ELF and COFF,
23650 when @value{GDBN} loads a new object file
23651 it will look for a special section named @code{.debug_gdb_scripts}.
23652 If this section exists, its contents is a list of NUL-terminated names
23653 of scripts to load. Each entry begins with a non-NULL prefix byte that
23654 specifies the kind of entry, typically the extension language.
23656 @value{GDBN} will look for each specified script file first in the
23657 current directory and then along the source search path
23658 (@pxref{Source Path, ,Specifying Source Directories}),
23659 except that @file{$cdir} is not searched, since the compilation
23660 directory is not relevant to scripts.
23662 Entries can be placed in section @code{.debug_gdb_scripts} with,
23663 for example, this GCC macro for Python scripts.
23666 /* Note: The "MS" section flags are to remove duplicates. */
23667 #define DEFINE_GDB_PY_SCRIPT(script_name) \
23669 .pushsection \".debug_gdb_scripts\", \"MS\",@@progbits,1\n\
23670 .byte 1 /* Python */\n\
23671 .asciz \"" script_name "\"\n\
23677 For Guile scripts, replace @code{.byte 1} with @code{.byte 3}.
23678 Then one can reference the macro in a header or source file like this:
23681 DEFINE_GDB_PY_SCRIPT ("my-app-scripts.py")
23684 The script name may include directories if desired.
23686 Note that loading of this script file also requires accordingly configured
23687 @code{auto-load safe-path} (@pxref{Auto-loading safe path}).
23689 If the macro invocation is put in a header, any application or library
23690 using this header will get a reference to the specified script,
23691 and with the use of @code{"MS"} attributes on the section, the linker
23692 will remove duplicates.
23694 @node Which flavor to choose?
23695 @subsection Which flavor to choose?
23697 Given the multiple ways of auto-loading extensions, it might not always
23698 be clear which one to choose. This section provides some guidance.
23701 Benefits of the @file{-gdb.@var{ext}} way:
23705 Can be used with file formats that don't support multiple sections.
23708 Ease of finding scripts for public libraries.
23710 Scripts specified in the @code{.debug_gdb_scripts} section are searched for
23711 in the source search path.
23712 For publicly installed libraries, e.g., @file{libstdc++}, there typically
23713 isn't a source directory in which to find the script.
23716 Doesn't require source code additions.
23720 Benefits of the @code{.debug_gdb_scripts} way:
23724 Works with static linking.
23726 Scripts for libraries done the @file{-gdb.@var{ext}} way require an objfile to
23727 trigger their loading. When an application is statically linked the only
23728 objfile available is the executable, and it is cumbersome to attach all the
23729 scripts from all the input libraries to the executable's
23730 @file{-gdb.@var{ext}} script.
23733 Works with classes that are entirely inlined.
23735 Some classes can be entirely inlined, and thus there may not be an associated
23736 shared library to attach a @file{-gdb.@var{ext}} script to.
23739 Scripts needn't be copied out of the source tree.
23741 In some circumstances, apps can be built out of large collections of internal
23742 libraries, and the build infrastructure necessary to install the
23743 @file{-gdb.@var{ext}} scripts in a place where @value{GDBN} can find them is
23744 cumbersome. It may be easier to specify the scripts in the
23745 @code{.debug_gdb_scripts} section as relative paths, and add a path to the
23746 top of the source tree to the source search path.
23749 @node Multiple Extension Languages
23750 @section Multiple Extension Languages
23752 The Guile and Python extension languages do not share any state,
23753 and generally do not interfere with each other.
23754 There are some things to be aware of, however.
23756 @subsection Python comes first
23758 Python was @value{GDBN}'s first extension language, and to avoid breaking
23759 existing behaviour Python comes first. This is generally solved by the
23760 ``first one wins'' principle. @value{GDBN} maintains a list of enabled
23761 extension languages, and when it makes a call to an extension language,
23762 (say to pretty-print a value), it tries each in turn until an extension
23763 language indicates it has performed the request (e.g., has returned the
23764 pretty-printed form of a value).
23765 This extends to errors while performing such requests: If an error happens
23766 while, for example, trying to pretty-print an object then the error is
23767 reported and any following extension languages are not tried.
23770 @section Creating new spellings of existing commands
23771 @cindex aliases for commands
23773 It is often useful to define alternate spellings of existing commands.
23774 For example, if a new @value{GDBN} command defined in Python has
23775 a long name to type, it is handy to have an abbreviated version of it
23776 that involves less typing.
23778 @value{GDBN} itself uses aliases. For example @samp{s} is an alias
23779 of the @samp{step} command even though it is otherwise an ambiguous
23780 abbreviation of other commands like @samp{set} and @samp{show}.
23782 Aliases are also used to provide shortened or more common versions
23783 of multi-word commands. For example, @value{GDBN} provides the
23784 @samp{tty} alias of the @samp{set inferior-tty} command.
23786 You can define a new alias with the @samp{alias} command.
23791 @item alias [-a] [--] @var{ALIAS} = @var{COMMAND}
23795 @var{ALIAS} specifies the name of the new alias.
23796 Each word of @var{ALIAS} must consist of letters, numbers, dashes and
23799 @var{COMMAND} specifies the name of an existing command
23800 that is being aliased.
23802 The @samp{-a} option specifies that the new alias is an abbreviation
23803 of the command. Abbreviations are not shown in command
23804 lists displayed by the @samp{help} command.
23806 The @samp{--} option specifies the end of options,
23807 and is useful when @var{ALIAS} begins with a dash.
23809 Here is a simple example showing how to make an abbreviation
23810 of a command so that there is less to type.
23811 Suppose you were tired of typing @samp{disas}, the current
23812 shortest unambiguous abbreviation of the @samp{disassemble} command
23813 and you wanted an even shorter version named @samp{di}.
23814 The following will accomplish this.
23817 (gdb) alias -a di = disas
23820 Note that aliases are different from user-defined commands.
23821 With a user-defined command, you also need to write documentation
23822 for it with the @samp{document} command.
23823 An alias automatically picks up the documentation of the existing command.
23825 Here is an example where we make @samp{elms} an abbreviation of
23826 @samp{elements} in the @samp{set print elements} command.
23827 This is to show that you can make an abbreviation of any part
23831 (gdb) alias -a set print elms = set print elements
23832 (gdb) alias -a show print elms = show print elements
23833 (gdb) set p elms 20
23835 Limit on string chars or array elements to print is 200.
23838 Note that if you are defining an alias of a @samp{set} command,
23839 and you want to have an alias for the corresponding @samp{show}
23840 command, then you need to define the latter separately.
23842 Unambiguously abbreviated commands are allowed in @var{COMMAND} and
23843 @var{ALIAS}, just as they are normally.
23846 (gdb) alias -a set pr elms = set p ele
23849 Finally, here is an example showing the creation of a one word
23850 alias for a more complex command.
23851 This creates alias @samp{spe} of the command @samp{set print elements}.
23854 (gdb) alias spe = set print elements
23859 @chapter Command Interpreters
23860 @cindex command interpreters
23862 @value{GDBN} supports multiple command interpreters, and some command
23863 infrastructure to allow users or user interface writers to switch
23864 between interpreters or run commands in other interpreters.
23866 @value{GDBN} currently supports two command interpreters, the console
23867 interpreter (sometimes called the command-line interpreter or @sc{cli})
23868 and the machine interface interpreter (or @sc{gdb/mi}). This manual
23869 describes both of these interfaces in great detail.
23871 By default, @value{GDBN} will start with the console interpreter.
23872 However, the user may choose to start @value{GDBN} with another
23873 interpreter by specifying the @option{-i} or @option{--interpreter}
23874 startup options. Defined interpreters include:
23878 @cindex console interpreter
23879 The traditional console or command-line interpreter. This is the most often
23880 used interpreter with @value{GDBN}. With no interpreter specified at runtime,
23881 @value{GDBN} will use this interpreter.
23884 @cindex mi interpreter
23885 The newest @sc{gdb/mi} interface (currently @code{mi2}). Used primarily
23886 by programs wishing to use @value{GDBN} as a backend for a debugger GUI
23887 or an IDE. For more information, see @ref{GDB/MI, ,The @sc{gdb/mi}
23891 @cindex mi2 interpreter
23892 The current @sc{gdb/mi} interface.
23895 @cindex mi1 interpreter
23896 The @sc{gdb/mi} interface included in @value{GDBN} 5.1, 5.2, and 5.3.
23900 @cindex invoke another interpreter
23901 The interpreter being used by @value{GDBN} may not be dynamically
23902 switched at runtime. Although possible, this could lead to a very
23903 precarious situation. Consider an IDE using @sc{gdb/mi}. If a user
23904 enters the command "interpreter-set console" in a console view,
23905 @value{GDBN} would switch to using the console interpreter, rendering
23906 the IDE inoperable!
23908 @kindex interpreter-exec
23909 Although you may only choose a single interpreter at startup, you may execute
23910 commands in any interpreter from the current interpreter using the appropriate
23911 command. If you are running the console interpreter, simply use the
23912 @code{interpreter-exec} command:
23915 interpreter-exec mi "-data-list-register-names"
23918 @sc{gdb/mi} has a similar command, although it is only available in versions of
23919 @value{GDBN} which support @sc{gdb/mi} version 2 (or greater).
23922 @chapter @value{GDBN} Text User Interface
23924 @cindex Text User Interface
23927 * TUI Overview:: TUI overview
23928 * TUI Keys:: TUI key bindings
23929 * TUI Single Key Mode:: TUI single key mode
23930 * TUI Commands:: TUI-specific commands
23931 * TUI Configuration:: TUI configuration variables
23934 The @value{GDBN} Text User Interface (TUI) is a terminal
23935 interface which uses the @code{curses} library to show the source
23936 file, the assembly output, the program registers and @value{GDBN}
23937 commands in separate text windows. The TUI mode is supported only
23938 on platforms where a suitable version of the @code{curses} library
23941 The TUI mode is enabled by default when you invoke @value{GDBN} as
23942 @samp{@value{GDBP} -tui}.
23943 You can also switch in and out of TUI mode while @value{GDBN} runs by
23944 using various TUI commands and key bindings, such as @kbd{C-x C-a}.
23945 @xref{TUI Keys, ,TUI Key Bindings}.
23948 @section TUI Overview
23950 In TUI mode, @value{GDBN} can display several text windows:
23954 This window is the @value{GDBN} command window with the @value{GDBN}
23955 prompt and the @value{GDBN} output. The @value{GDBN} input is still
23956 managed using readline.
23959 The source window shows the source file of the program. The current
23960 line and active breakpoints are displayed in this window.
23963 The assembly window shows the disassembly output of the program.
23966 This window shows the processor registers. Registers are highlighted
23967 when their values change.
23970 The source and assembly windows show the current program position
23971 by highlighting the current line and marking it with a @samp{>} marker.
23972 Breakpoints are indicated with two markers. The first marker
23973 indicates the breakpoint type:
23977 Breakpoint which was hit at least once.
23980 Breakpoint which was never hit.
23983 Hardware breakpoint which was hit at least once.
23986 Hardware breakpoint which was never hit.
23989 The second marker indicates whether the breakpoint is enabled or not:
23993 Breakpoint is enabled.
23996 Breakpoint is disabled.
23999 The source, assembly and register windows are updated when the current
24000 thread changes, when the frame changes, or when the program counter
24003 These windows are not all visible at the same time. The command
24004 window is always visible. The others can be arranged in several
24015 source and assembly,
24018 source and registers, or
24021 assembly and registers.
24024 A status line above the command window shows the following information:
24028 Indicates the current @value{GDBN} target.
24029 (@pxref{Targets, ,Specifying a Debugging Target}).
24032 Gives the current process or thread number.
24033 When no process is being debugged, this field is set to @code{No process}.
24036 Gives the current function name for the selected frame.
24037 The name is demangled if demangling is turned on (@pxref{Print Settings}).
24038 When there is no symbol corresponding to the current program counter,
24039 the string @code{??} is displayed.
24042 Indicates the current line number for the selected frame.
24043 When the current line number is not known, the string @code{??} is displayed.
24046 Indicates the current program counter address.
24050 @section TUI Key Bindings
24051 @cindex TUI key bindings
24053 The TUI installs several key bindings in the readline keymaps
24054 @ifset SYSTEM_READLINE
24055 (@pxref{Command Line Editing, , , rluserman, GNU Readline Library}).
24057 @ifclear SYSTEM_READLINE
24058 (@pxref{Command Line Editing}).
24060 The following key bindings are installed for both TUI mode and the
24061 @value{GDBN} standard mode.
24070 Enter or leave the TUI mode. When leaving the TUI mode,
24071 the curses window management stops and @value{GDBN} operates using
24072 its standard mode, writing on the terminal directly. When reentering
24073 the TUI mode, control is given back to the curses windows.
24074 The screen is then refreshed.
24078 Use a TUI layout with only one window. The layout will
24079 either be @samp{source} or @samp{assembly}. When the TUI mode
24080 is not active, it will switch to the TUI mode.
24082 Think of this key binding as the Emacs @kbd{C-x 1} binding.
24086 Use a TUI layout with at least two windows. When the current
24087 layout already has two windows, the next layout with two windows is used.
24088 When a new layout is chosen, one window will always be common to the
24089 previous layout and the new one.
24091 Think of it as the Emacs @kbd{C-x 2} binding.
24095 Change the active window. The TUI associates several key bindings
24096 (like scrolling and arrow keys) with the active window. This command
24097 gives the focus to the next TUI window.
24099 Think of it as the Emacs @kbd{C-x o} binding.
24103 Switch in and out of the TUI SingleKey mode that binds single
24104 keys to @value{GDBN} commands (@pxref{TUI Single Key Mode}).
24107 The following key bindings only work in the TUI mode:
24112 Scroll the active window one page up.
24116 Scroll the active window one page down.
24120 Scroll the active window one line up.
24124 Scroll the active window one line down.
24128 Scroll the active window one column left.
24132 Scroll the active window one column right.
24136 Refresh the screen.
24139 Because the arrow keys scroll the active window in the TUI mode, they
24140 are not available for their normal use by readline unless the command
24141 window has the focus. When another window is active, you must use
24142 other readline key bindings such as @kbd{C-p}, @kbd{C-n}, @kbd{C-b}
24143 and @kbd{C-f} to control the command window.
24145 @node TUI Single Key Mode
24146 @section TUI Single Key Mode
24147 @cindex TUI single key mode
24149 The TUI also provides a @dfn{SingleKey} mode, which binds several
24150 frequently used @value{GDBN} commands to single keys. Type @kbd{C-x s} to
24151 switch into this mode, where the following key bindings are used:
24154 @kindex c @r{(SingleKey TUI key)}
24158 @kindex d @r{(SingleKey TUI key)}
24162 @kindex f @r{(SingleKey TUI key)}
24166 @kindex n @r{(SingleKey TUI key)}
24170 @kindex q @r{(SingleKey TUI key)}
24172 exit the SingleKey mode.
24174 @kindex r @r{(SingleKey TUI key)}
24178 @kindex s @r{(SingleKey TUI key)}
24182 @kindex u @r{(SingleKey TUI key)}
24186 @kindex v @r{(SingleKey TUI key)}
24190 @kindex w @r{(SingleKey TUI key)}
24195 Other keys temporarily switch to the @value{GDBN} command prompt.
24196 The key that was pressed is inserted in the editing buffer so that
24197 it is possible to type most @value{GDBN} commands without interaction
24198 with the TUI SingleKey mode. Once the command is entered the TUI
24199 SingleKey mode is restored. The only way to permanently leave
24200 this mode is by typing @kbd{q} or @kbd{C-x s}.
24204 @section TUI-specific Commands
24205 @cindex TUI commands
24207 The TUI has specific commands to control the text windows.
24208 These commands are always available, even when @value{GDBN} is not in
24209 the TUI mode. When @value{GDBN} is in the standard mode, most
24210 of these commands will automatically switch to the TUI mode.
24212 Note that if @value{GDBN}'s @code{stdout} is not connected to a
24213 terminal, or @value{GDBN} has been started with the machine interface
24214 interpreter (@pxref{GDB/MI, ,The @sc{gdb/mi} Interface}), most of
24215 these commands will fail with an error, because it would not be
24216 possible or desirable to enable curses window management.
24221 List and give the size of all displayed windows.
24225 Display the next layout.
24228 Display the previous layout.
24231 Display the source window only.
24234 Display the assembly window only.
24237 Display the source and assembly window.
24240 Display the register window together with the source or assembly window.
24244 Make the next window active for scrolling.
24247 Make the previous window active for scrolling.
24250 Make the source window active for scrolling.
24253 Make the assembly window active for scrolling.
24256 Make the register window active for scrolling.
24259 Make the command window active for scrolling.
24263 Refresh the screen. This is similar to typing @kbd{C-L}.
24265 @item tui reg float
24267 Show the floating point registers in the register window.
24269 @item tui reg general
24270 Show the general registers in the register window.
24273 Show the next register group. The list of register groups as well as
24274 their order is target specific. The predefined register groups are the
24275 following: @code{general}, @code{float}, @code{system}, @code{vector},
24276 @code{all}, @code{save}, @code{restore}.
24278 @item tui reg system
24279 Show the system registers in the register window.
24283 Update the source window and the current execution point.
24285 @item winheight @var{name} +@var{count}
24286 @itemx winheight @var{name} -@var{count}
24288 Change the height of the window @var{name} by @var{count}
24289 lines. Positive counts increase the height, while negative counts
24292 @item tabset @var{nchars}
24294 Set the width of tab stops to be @var{nchars} characters.
24297 @node TUI Configuration
24298 @section TUI Configuration Variables
24299 @cindex TUI configuration variables
24301 Several configuration variables control the appearance of TUI windows.
24304 @item set tui border-kind @var{kind}
24305 @kindex set tui border-kind
24306 Select the border appearance for the source, assembly and register windows.
24307 The possible values are the following:
24310 Use a space character to draw the border.
24313 Use @sc{ascii} characters @samp{+}, @samp{-} and @samp{|} to draw the border.
24316 Use the Alternate Character Set to draw the border. The border is
24317 drawn using character line graphics if the terminal supports them.
24320 @item set tui border-mode @var{mode}
24321 @kindex set tui border-mode
24322 @itemx set tui active-border-mode @var{mode}
24323 @kindex set tui active-border-mode
24324 Select the display attributes for the borders of the inactive windows
24325 or the active window. The @var{mode} can be one of the following:
24328 Use normal attributes to display the border.
24334 Use reverse video mode.
24337 Use half bright mode.
24339 @item half-standout
24340 Use half bright and standout mode.
24343 Use extra bright or bold mode.
24345 @item bold-standout
24346 Use extra bright or bold and standout mode.
24351 @chapter Using @value{GDBN} under @sc{gnu} Emacs
24354 @cindex @sc{gnu} Emacs
24355 A special interface allows you to use @sc{gnu} Emacs to view (and
24356 edit) the source files for the program you are debugging with
24359 To use this interface, use the command @kbd{M-x gdb} in Emacs. Give the
24360 executable file you want to debug as an argument. This command starts
24361 @value{GDBN} as a subprocess of Emacs, with input and output through a newly
24362 created Emacs buffer.
24363 @c (Do not use the @code{-tui} option to run @value{GDBN} from Emacs.)
24365 Running @value{GDBN} under Emacs can be just like running @value{GDBN} normally except for two
24370 All ``terminal'' input and output goes through an Emacs buffer, called
24373 This applies both to @value{GDBN} commands and their output, and to the input
24374 and output done by the program you are debugging.
24376 This is useful because it means that you can copy the text of previous
24377 commands and input them again; you can even use parts of the output
24380 All the facilities of Emacs' Shell mode are available for interacting
24381 with your program. In particular, you can send signals the usual
24382 way---for example, @kbd{C-c C-c} for an interrupt, @kbd{C-c C-z} for a
24386 @value{GDBN} displays source code through Emacs.
24388 Each time @value{GDBN} displays a stack frame, Emacs automatically finds the
24389 source file for that frame and puts an arrow (@samp{=>}) at the
24390 left margin of the current line. Emacs uses a separate buffer for
24391 source display, and splits the screen to show both your @value{GDBN} session
24394 Explicit @value{GDBN} @code{list} or search commands still produce output as
24395 usual, but you probably have no reason to use them from Emacs.
24398 We call this @dfn{text command mode}. Emacs 22.1, and later, also uses
24399 a graphical mode, enabled by default, which provides further buffers
24400 that can control the execution and describe the state of your program.
24401 @xref{GDB Graphical Interface,,, Emacs, The @sc{gnu} Emacs Manual}.
24403 If you specify an absolute file name when prompted for the @kbd{M-x
24404 gdb} argument, then Emacs sets your current working directory to where
24405 your program resides. If you only specify the file name, then Emacs
24406 sets your current working directory to the directory associated
24407 with the previous buffer. In this case, @value{GDBN} may find your
24408 program by searching your environment's @code{PATH} variable, but on
24409 some operating systems it might not find the source. So, although the
24410 @value{GDBN} input and output session proceeds normally, the auxiliary
24411 buffer does not display the current source and line of execution.
24413 The initial working directory of @value{GDBN} is printed on the top
24414 line of the GUD buffer and this serves as a default for the commands
24415 that specify files for @value{GDBN} to operate on. @xref{Files,
24416 ,Commands to Specify Files}.
24418 By default, @kbd{M-x gdb} calls the program called @file{gdb}. If you
24419 need to call @value{GDBN} by a different name (for example, if you
24420 keep several configurations around, with different names) you can
24421 customize the Emacs variable @code{gud-gdb-command-name} to run the
24424 In the GUD buffer, you can use these special Emacs commands in
24425 addition to the standard Shell mode commands:
24429 Describe the features of Emacs' GUD Mode.
24432 Execute to another source line, like the @value{GDBN} @code{step} command; also
24433 update the display window to show the current file and location.
24436 Execute to next source line in this function, skipping all function
24437 calls, like the @value{GDBN} @code{next} command. Then update the display window
24438 to show the current file and location.
24441 Execute one instruction, like the @value{GDBN} @code{stepi} command; update
24442 display window accordingly.
24445 Execute until exit from the selected stack frame, like the @value{GDBN}
24446 @code{finish} command.
24449 Continue execution of your program, like the @value{GDBN} @code{continue}
24453 Go up the number of frames indicated by the numeric argument
24454 (@pxref{Arguments, , Numeric Arguments, Emacs, The @sc{gnu} Emacs Manual}),
24455 like the @value{GDBN} @code{up} command.
24458 Go down the number of frames indicated by the numeric argument, like the
24459 @value{GDBN} @code{down} command.
24462 In any source file, the Emacs command @kbd{C-x @key{SPC}} (@code{gud-break})
24463 tells @value{GDBN} to set a breakpoint on the source line point is on.
24465 In text command mode, if you type @kbd{M-x speedbar}, Emacs displays a
24466 separate frame which shows a backtrace when the GUD buffer is current.
24467 Move point to any frame in the stack and type @key{RET} to make it
24468 become the current frame and display the associated source in the
24469 source buffer. Alternatively, click @kbd{Mouse-2} to make the
24470 selected frame become the current one. In graphical mode, the
24471 speedbar displays watch expressions.
24473 If you accidentally delete the source-display buffer, an easy way to get
24474 it back is to type the command @code{f} in the @value{GDBN} buffer, to
24475 request a frame display; when you run under Emacs, this recreates
24476 the source buffer if necessary to show you the context of the current
24479 The source files displayed in Emacs are in ordinary Emacs buffers
24480 which are visiting the source files in the usual way. You can edit
24481 the files with these buffers if you wish; but keep in mind that @value{GDBN}
24482 communicates with Emacs in terms of line numbers. If you add or
24483 delete lines from the text, the line numbers that @value{GDBN} knows cease
24484 to correspond properly with the code.
24486 A more detailed description of Emacs' interaction with @value{GDBN} is
24487 given in the Emacs manual (@pxref{Debuggers,,, Emacs, The @sc{gnu}
24491 @chapter The @sc{gdb/mi} Interface
24493 @unnumberedsec Function and Purpose
24495 @cindex @sc{gdb/mi}, its purpose
24496 @sc{gdb/mi} is a line based machine oriented text interface to
24497 @value{GDBN} and is activated by specifying using the
24498 @option{--interpreter} command line option (@pxref{Mode Options}). It
24499 is specifically intended to support the development of systems which
24500 use the debugger as just one small component of a larger system.
24502 This chapter is a specification of the @sc{gdb/mi} interface. It is written
24503 in the form of a reference manual.
24505 Note that @sc{gdb/mi} is still under construction, so some of the
24506 features described below are incomplete and subject to change
24507 (@pxref{GDB/MI Development and Front Ends, , @sc{gdb/mi} Development and Front Ends}).
24509 @unnumberedsec Notation and Terminology
24511 @cindex notational conventions, for @sc{gdb/mi}
24512 This chapter uses the following notation:
24516 @code{|} separates two alternatives.
24519 @code{[ @var{something} ]} indicates that @var{something} is optional:
24520 it may or may not be given.
24523 @code{( @var{group} )*} means that @var{group} inside the parentheses
24524 may repeat zero or more times.
24527 @code{( @var{group} )+} means that @var{group} inside the parentheses
24528 may repeat one or more times.
24531 @code{"@var{string}"} means a literal @var{string}.
24535 @heading Dependencies
24539 * GDB/MI General Design::
24540 * GDB/MI Command Syntax::
24541 * GDB/MI Compatibility with CLI::
24542 * GDB/MI Development and Front Ends::
24543 * GDB/MI Output Records::
24544 * GDB/MI Simple Examples::
24545 * GDB/MI Command Description Format::
24546 * GDB/MI Breakpoint Commands::
24547 * GDB/MI Catchpoint Commands::
24548 * GDB/MI Program Context::
24549 * GDB/MI Thread Commands::
24550 * GDB/MI Ada Tasking Commands::
24551 * GDB/MI Program Execution::
24552 * GDB/MI Stack Manipulation::
24553 * GDB/MI Variable Objects::
24554 * GDB/MI Data Manipulation::
24555 * GDB/MI Tracepoint Commands::
24556 * GDB/MI Symbol Query::
24557 * GDB/MI File Commands::
24559 * GDB/MI Kod Commands::
24560 * GDB/MI Memory Overlay Commands::
24561 * GDB/MI Signal Handling Commands::
24563 * GDB/MI Target Manipulation::
24564 * GDB/MI File Transfer Commands::
24565 * GDB/MI Ada Exceptions Commands::
24566 * GDB/MI Support Commands::
24567 * GDB/MI Miscellaneous Commands::
24570 @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
24571 @node GDB/MI General Design
24572 @section @sc{gdb/mi} General Design
24573 @cindex GDB/MI General Design
24575 Interaction of a @sc{GDB/MI} frontend with @value{GDBN} involves three
24576 parts---commands sent to @value{GDBN}, responses to those commands
24577 and notifications. Each command results in exactly one response,
24578 indicating either successful completion of the command, or an error.
24579 For the commands that do not resume the target, the response contains the
24580 requested information. For the commands that resume the target, the
24581 response only indicates whether the target was successfully resumed.
24582 Notifications is the mechanism for reporting changes in the state of the
24583 target, or in @value{GDBN} state, that cannot conveniently be associated with
24584 a command and reported as part of that command response.
24586 The important examples of notifications are:
24590 Exec notifications. These are used to report changes in
24591 target state---when a target is resumed, or stopped. It would not
24592 be feasible to include this information in response of resuming
24593 commands, because one resume commands can result in multiple events in
24594 different threads. Also, quite some time may pass before any event
24595 happens in the target, while a frontend needs to know whether the resuming
24596 command itself was successfully executed.
24599 Console output, and status notifications. Console output
24600 notifications are used to report output of CLI commands, as well as
24601 diagnostics for other commands. Status notifications are used to
24602 report the progress of a long-running operation. Naturally, including
24603 this information in command response would mean no output is produced
24604 until the command is finished, which is undesirable.
24607 General notifications. Commands may have various side effects on
24608 the @value{GDBN} or target state beyond their official purpose. For example,
24609 a command may change the selected thread. Although such changes can
24610 be included in command response, using notification allows for more
24611 orthogonal frontend design.
24615 There's no guarantee that whenever an MI command reports an error,
24616 @value{GDBN} or the target are in any specific state, and especially,
24617 the state is not reverted to the state before the MI command was
24618 processed. Therefore, whenever an MI command results in an error,
24619 we recommend that the frontend refreshes all the information shown in
24620 the user interface.
24624 * Context management::
24625 * Asynchronous and non-stop modes::
24629 @node Context management
24630 @subsection Context management
24632 @subsubsection Threads and Frames
24634 In most cases when @value{GDBN} accesses the target, this access is
24635 done in context of a specific thread and frame (@pxref{Frames}).
24636 Often, even when accessing global data, the target requires that a thread
24637 be specified. The CLI interface maintains the selected thread and frame,
24638 and supplies them to target on each command. This is convenient,
24639 because a command line user would not want to specify that information
24640 explicitly on each command, and because user interacts with
24641 @value{GDBN} via a single terminal, so no confusion is possible as
24642 to what thread and frame are the current ones.
24644 In the case of MI, the concept of selected thread and frame is less
24645 useful. First, a frontend can easily remember this information
24646 itself. Second, a graphical frontend can have more than one window,
24647 each one used for debugging a different thread, and the frontend might
24648 want to access additional threads for internal purposes. This
24649 increases the risk that by relying on implicitly selected thread, the
24650 frontend may be operating on a wrong one. Therefore, each MI command
24651 should explicitly specify which thread and frame to operate on. To
24652 make it possible, each MI command accepts the @samp{--thread} and
24653 @samp{--frame} options, the value to each is @value{GDBN} identifier
24654 for thread and frame to operate on.
24656 Usually, each top-level window in a frontend allows the user to select
24657 a thread and a frame, and remembers the user selection for further
24658 operations. However, in some cases @value{GDBN} may suggest that the
24659 current thread be changed. For example, when stopping on a breakpoint
24660 it is reasonable to switch to the thread where breakpoint is hit. For
24661 another example, if the user issues the CLI @samp{thread} command via
24662 the frontend, it is desirable to change the frontend's selected thread to the
24663 one specified by user. @value{GDBN} communicates the suggestion to
24664 change current thread using the @samp{=thread-selected} notification.
24665 No such notification is available for the selected frame at the moment.
24667 Note that historically, MI shares the selected thread with CLI, so
24668 frontends used the @code{-thread-select} to execute commands in the
24669 right context. However, getting this to work right is cumbersome. The
24670 simplest way is for frontend to emit @code{-thread-select} command
24671 before every command. This doubles the number of commands that need
24672 to be sent. The alternative approach is to suppress @code{-thread-select}
24673 if the selected thread in @value{GDBN} is supposed to be identical to the
24674 thread the frontend wants to operate on. However, getting this
24675 optimization right can be tricky. In particular, if the frontend
24676 sends several commands to @value{GDBN}, and one of the commands changes the
24677 selected thread, then the behaviour of subsequent commands will
24678 change. So, a frontend should either wait for response from such
24679 problematic commands, or explicitly add @code{-thread-select} for
24680 all subsequent commands. No frontend is known to do this exactly
24681 right, so it is suggested to just always pass the @samp{--thread} and
24682 @samp{--frame} options.
24684 @subsubsection Language
24686 The execution of several commands depends on which language is selected.
24687 By default, the current language (@pxref{show language}) is used.
24688 But for commands known to be language-sensitive, it is recommended
24689 to use the @samp{--language} option. This option takes one argument,
24690 which is the name of the language to use while executing the command.
24694 -data-evaluate-expression --language c "sizeof (void*)"
24699 The valid language names are the same names accepted by the
24700 @samp{set language} command (@pxref{Manually}), excluding @samp{auto},
24701 @samp{local} or @samp{unknown}.
24703 @node Asynchronous and non-stop modes
24704 @subsection Asynchronous command execution and non-stop mode
24706 On some targets, @value{GDBN} is capable of processing MI commands
24707 even while the target is running. This is called @dfn{asynchronous
24708 command execution} (@pxref{Background Execution}). The frontend may
24709 specify a preferrence for asynchronous execution using the
24710 @code{-gdb-set target-async 1} command, which should be emitted before
24711 either running the executable or attaching to the target. After the
24712 frontend has started the executable or attached to the target, it can
24713 find if asynchronous execution is enabled using the
24714 @code{-list-target-features} command.
24716 Even if @value{GDBN} can accept a command while target is running,
24717 many commands that access the target do not work when the target is
24718 running. Therefore, asynchronous command execution is most useful
24719 when combined with non-stop mode (@pxref{Non-Stop Mode}). Then,
24720 it is possible to examine the state of one thread, while other threads
24723 When a given thread is running, MI commands that try to access the
24724 target in the context of that thread may not work, or may work only on
24725 some targets. In particular, commands that try to operate on thread's
24726 stack will not work, on any target. Commands that read memory, or
24727 modify breakpoints, may work or not work, depending on the target. Note
24728 that even commands that operate on global state, such as @code{print},
24729 @code{set}, and breakpoint commands, still access the target in the
24730 context of a specific thread, so frontend should try to find a
24731 stopped thread and perform the operation on that thread (using the
24732 @samp{--thread} option).
24734 Which commands will work in the context of a running thread is
24735 highly target dependent. However, the two commands
24736 @code{-exec-interrupt}, to stop a thread, and @code{-thread-info},
24737 to find the state of a thread, will always work.
24739 @node Thread groups
24740 @subsection Thread groups
24741 @value{GDBN} may be used to debug several processes at the same time.
24742 On some platfroms, @value{GDBN} may support debugging of several
24743 hardware systems, each one having several cores with several different
24744 processes running on each core. This section describes the MI
24745 mechanism to support such debugging scenarios.
24747 The key observation is that regardless of the structure of the
24748 target, MI can have a global list of threads, because most commands that
24749 accept the @samp{--thread} option do not need to know what process that
24750 thread belongs to. Therefore, it is not necessary to introduce
24751 neither additional @samp{--process} option, nor an notion of the
24752 current process in the MI interface. The only strictly new feature
24753 that is required is the ability to find how the threads are grouped
24756 To allow the user to discover such grouping, and to support arbitrary
24757 hierarchy of machines/cores/processes, MI introduces the concept of a
24758 @dfn{thread group}. Thread group is a collection of threads and other
24759 thread groups. A thread group always has a string identifier, a type,
24760 and may have additional attributes specific to the type. A new
24761 command, @code{-list-thread-groups}, returns the list of top-level
24762 thread groups, which correspond to processes that @value{GDBN} is
24763 debugging at the moment. By passing an identifier of a thread group
24764 to the @code{-list-thread-groups} command, it is possible to obtain
24765 the members of specific thread group.
24767 To allow the user to easily discover processes, and other objects, he
24768 wishes to debug, a concept of @dfn{available thread group} is
24769 introduced. Available thread group is an thread group that
24770 @value{GDBN} is not debugging, but that can be attached to, using the
24771 @code{-target-attach} command. The list of available top-level thread
24772 groups can be obtained using @samp{-list-thread-groups --available}.
24773 In general, the content of a thread group may be only retrieved only
24774 after attaching to that thread group.
24776 Thread groups are related to inferiors (@pxref{Inferiors and
24777 Programs}). Each inferior corresponds to a thread group of a special
24778 type @samp{process}, and some additional operations are permitted on
24779 such thread groups.
24781 @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
24782 @node GDB/MI Command Syntax
24783 @section @sc{gdb/mi} Command Syntax
24786 * GDB/MI Input Syntax::
24787 * GDB/MI Output Syntax::
24790 @node GDB/MI Input Syntax
24791 @subsection @sc{gdb/mi} Input Syntax
24793 @cindex input syntax for @sc{gdb/mi}
24794 @cindex @sc{gdb/mi}, input syntax
24796 @item @var{command} @expansion{}
24797 @code{@var{cli-command} | @var{mi-command}}
24799 @item @var{cli-command} @expansion{}
24800 @code{[ @var{token} ] @var{cli-command} @var{nl}}, where
24801 @var{cli-command} is any existing @value{GDBN} CLI command.
24803 @item @var{mi-command} @expansion{}
24804 @code{[ @var{token} ] "-" @var{operation} ( " " @var{option} )*
24805 @code{[} " --" @code{]} ( " " @var{parameter} )* @var{nl}}
24807 @item @var{token} @expansion{}
24808 "any sequence of digits"
24810 @item @var{option} @expansion{}
24811 @code{"-" @var{parameter} [ " " @var{parameter} ]}
24813 @item @var{parameter} @expansion{}
24814 @code{@var{non-blank-sequence} | @var{c-string}}
24816 @item @var{operation} @expansion{}
24817 @emph{any of the operations described in this chapter}
24819 @item @var{non-blank-sequence} @expansion{}
24820 @emph{anything, provided it doesn't contain special characters such as
24821 "-", @var{nl}, """ and of course " "}
24823 @item @var{c-string} @expansion{}
24824 @code{""" @var{seven-bit-iso-c-string-content} """}
24826 @item @var{nl} @expansion{}
24835 The CLI commands are still handled by the @sc{mi} interpreter; their
24836 output is described below.
24839 The @code{@var{token}}, when present, is passed back when the command
24843 Some @sc{mi} commands accept optional arguments as part of the parameter
24844 list. Each option is identified by a leading @samp{-} (dash) and may be
24845 followed by an optional argument parameter. Options occur first in the
24846 parameter list and can be delimited from normal parameters using
24847 @samp{--} (this is useful when some parameters begin with a dash).
24854 We want easy access to the existing CLI syntax (for debugging).
24857 We want it to be easy to spot a @sc{mi} operation.
24860 @node GDB/MI Output Syntax
24861 @subsection @sc{gdb/mi} Output Syntax
24863 @cindex output syntax of @sc{gdb/mi}
24864 @cindex @sc{gdb/mi}, output syntax
24865 The output from @sc{gdb/mi} consists of zero or more out-of-band records
24866 followed, optionally, by a single result record. This result record
24867 is for the most recent command. The sequence of output records is
24868 terminated by @samp{(gdb)}.
24870 If an input command was prefixed with a @code{@var{token}} then the
24871 corresponding output for that command will also be prefixed by that same
24875 @item @var{output} @expansion{}
24876 @code{( @var{out-of-band-record} )* [ @var{result-record} ] "(gdb)" @var{nl}}
24878 @item @var{result-record} @expansion{}
24879 @code{ [ @var{token} ] "^" @var{result-class} ( "," @var{result} )* @var{nl}}
24881 @item @var{out-of-band-record} @expansion{}
24882 @code{@var{async-record} | @var{stream-record}}
24884 @item @var{async-record} @expansion{}
24885 @code{@var{exec-async-output} | @var{status-async-output} | @var{notify-async-output}}
24887 @item @var{exec-async-output} @expansion{}
24888 @code{[ @var{token} ] "*" @var{async-output nl}}
24890 @item @var{status-async-output} @expansion{}
24891 @code{[ @var{token} ] "+" @var{async-output nl}}
24893 @item @var{notify-async-output} @expansion{}
24894 @code{[ @var{token} ] "=" @var{async-output nl}}
24896 @item @var{async-output} @expansion{}
24897 @code{@var{async-class} ( "," @var{result} )*}
24899 @item @var{result-class} @expansion{}
24900 @code{"done" | "running" | "connected" | "error" | "exit"}
24902 @item @var{async-class} @expansion{}
24903 @code{"stopped" | @var{others}} (where @var{others} will be added
24904 depending on the needs---this is still in development).
24906 @item @var{result} @expansion{}
24907 @code{ @var{variable} "=" @var{value}}
24909 @item @var{variable} @expansion{}
24910 @code{ @var{string} }
24912 @item @var{value} @expansion{}
24913 @code{ @var{const} | @var{tuple} | @var{list} }
24915 @item @var{const} @expansion{}
24916 @code{@var{c-string}}
24918 @item @var{tuple} @expansion{}
24919 @code{ "@{@}" | "@{" @var{result} ( "," @var{result} )* "@}" }
24921 @item @var{list} @expansion{}
24922 @code{ "[]" | "[" @var{value} ( "," @var{value} )* "]" | "["
24923 @var{result} ( "," @var{result} )* "]" }
24925 @item @var{stream-record} @expansion{}
24926 @code{@var{console-stream-output} | @var{target-stream-output} | @var{log-stream-output}}
24928 @item @var{console-stream-output} @expansion{}
24929 @code{"~" @var{c-string nl}}
24931 @item @var{target-stream-output} @expansion{}
24932 @code{"@@" @var{c-string nl}}
24934 @item @var{log-stream-output} @expansion{}
24935 @code{"&" @var{c-string nl}}
24937 @item @var{nl} @expansion{}
24940 @item @var{token} @expansion{}
24941 @emph{any sequence of digits}.
24949 All output sequences end in a single line containing a period.
24952 The @code{@var{token}} is from the corresponding request. Note that
24953 for all async output, while the token is allowed by the grammar and
24954 may be output by future versions of @value{GDBN} for select async
24955 output messages, it is generally omitted. Frontends should treat
24956 all async output as reporting general changes in the state of the
24957 target and there should be no need to associate async output to any
24961 @cindex status output in @sc{gdb/mi}
24962 @var{status-async-output} contains on-going status information about the
24963 progress of a slow operation. It can be discarded. All status output is
24964 prefixed by @samp{+}.
24967 @cindex async output in @sc{gdb/mi}
24968 @var{exec-async-output} contains asynchronous state change on the target
24969 (stopped, started, disappeared). All async output is prefixed by
24973 @cindex notify output in @sc{gdb/mi}
24974 @var{notify-async-output} contains supplementary information that the
24975 client should handle (e.g., a new breakpoint information). All notify
24976 output is prefixed by @samp{=}.
24979 @cindex console output in @sc{gdb/mi}
24980 @var{console-stream-output} is output that should be displayed as is in the
24981 console. It is the textual response to a CLI command. All the console
24982 output is prefixed by @samp{~}.
24985 @cindex target output in @sc{gdb/mi}
24986 @var{target-stream-output} is the output produced by the target program.
24987 All the target output is prefixed by @samp{@@}.
24990 @cindex log output in @sc{gdb/mi}
24991 @var{log-stream-output} is output text coming from @value{GDBN}'s internals, for
24992 instance messages that should be displayed as part of an error log. All
24993 the log output is prefixed by @samp{&}.
24996 @cindex list output in @sc{gdb/mi}
24997 New @sc{gdb/mi} commands should only output @var{lists} containing
25003 @xref{GDB/MI Stream Records, , @sc{gdb/mi} Stream Records}, for more
25004 details about the various output records.
25006 @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
25007 @node GDB/MI Compatibility with CLI
25008 @section @sc{gdb/mi} Compatibility with CLI
25010 @cindex compatibility, @sc{gdb/mi} and CLI
25011 @cindex @sc{gdb/mi}, compatibility with CLI
25013 For the developers convenience CLI commands can be entered directly,
25014 but there may be some unexpected behaviour. For example, commands
25015 that query the user will behave as if the user replied yes, breakpoint
25016 command lists are not executed and some CLI commands, such as
25017 @code{if}, @code{when} and @code{define}, prompt for further input with
25018 @samp{>}, which is not valid MI output.
25020 This feature may be removed at some stage in the future and it is
25021 recommended that front ends use the @code{-interpreter-exec} command
25022 (@pxref{-interpreter-exec}).
25024 @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
25025 @node GDB/MI Development and Front Ends
25026 @section @sc{gdb/mi} Development and Front Ends
25027 @cindex @sc{gdb/mi} development
25029 The application which takes the MI output and presents the state of the
25030 program being debugged to the user is called a @dfn{front end}.
25032 Although @sc{gdb/mi} is still incomplete, it is currently being used
25033 by a variety of front ends to @value{GDBN}. This makes it difficult
25034 to introduce new functionality without breaking existing usage. This
25035 section tries to minimize the problems by describing how the protocol
25038 Some changes in MI need not break a carefully designed front end, and
25039 for these the MI version will remain unchanged. The following is a
25040 list of changes that may occur within one level, so front ends should
25041 parse MI output in a way that can handle them:
25045 New MI commands may be added.
25048 New fields may be added to the output of any MI command.
25051 The range of values for fields with specified values, e.g.,
25052 @code{in_scope} (@pxref{-var-update}) may be extended.
25054 @c The format of field's content e.g type prefix, may change so parse it
25055 @c at your own risk. Yes, in general?
25057 @c The order of fields may change? Shouldn't really matter but it might
25058 @c resolve inconsistencies.
25061 If the changes are likely to break front ends, the MI version level
25062 will be increased by one. This will allow the front end to parse the
25063 output according to the MI version. Apart from mi0, new versions of
25064 @value{GDBN} will not support old versions of MI and it will be the
25065 responsibility of the front end to work with the new one.
25067 @c Starting with mi3, add a new command -mi-version that prints the MI
25070 The best way to avoid unexpected changes in MI that might break your front
25071 end is to make your project known to @value{GDBN} developers and
25072 follow development on @email{gdb@@sourceware.org} and
25073 @email{gdb-patches@@sourceware.org}.
25074 @cindex mailing lists
25076 @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
25077 @node GDB/MI Output Records
25078 @section @sc{gdb/mi} Output Records
25081 * GDB/MI Result Records::
25082 * GDB/MI Stream Records::
25083 * GDB/MI Async Records::
25084 * GDB/MI Breakpoint Information::
25085 * GDB/MI Frame Information::
25086 * GDB/MI Thread Information::
25087 * GDB/MI Ada Exception Information::
25090 @node GDB/MI Result Records
25091 @subsection @sc{gdb/mi} Result Records
25093 @cindex result records in @sc{gdb/mi}
25094 @cindex @sc{gdb/mi}, result records
25095 In addition to a number of out-of-band notifications, the response to a
25096 @sc{gdb/mi} command includes one of the following result indications:
25100 @item "^done" [ "," @var{results} ]
25101 The synchronous operation was successful, @code{@var{results}} are the return
25106 This result record is equivalent to @samp{^done}. Historically, it
25107 was output instead of @samp{^done} if the command has resumed the
25108 target. This behaviour is maintained for backward compatibility, but
25109 all frontends should treat @samp{^done} and @samp{^running}
25110 identically and rely on the @samp{*running} output record to determine
25111 which threads are resumed.
25115 @value{GDBN} has connected to a remote target.
25117 @item "^error" "," "msg=" @var{c-string} [ "," "code=" @var{c-string} ]
25119 The operation failed. The @code{msg=@var{c-string}} variable contains
25120 the corresponding error message.
25122 If present, the @code{code=@var{c-string}} variable provides an error
25123 code on which consumers can rely on to detect the corresponding
25124 error condition. At present, only one error code is defined:
25127 @item "undefined-command"
25128 Indicates that the command causing the error does not exist.
25133 @value{GDBN} has terminated.
25137 @node GDB/MI Stream Records
25138 @subsection @sc{gdb/mi} Stream Records
25140 @cindex @sc{gdb/mi}, stream records
25141 @cindex stream records in @sc{gdb/mi}
25142 @value{GDBN} internally maintains a number of output streams: the console, the
25143 target, and the log. The output intended for each of these streams is
25144 funneled through the @sc{gdb/mi} interface using @dfn{stream records}.
25146 Each stream record begins with a unique @dfn{prefix character} which
25147 identifies its stream (@pxref{GDB/MI Output Syntax, , @sc{gdb/mi} Output
25148 Syntax}). In addition to the prefix, each stream record contains a
25149 @code{@var{string-output}}. This is either raw text (with an implicit new
25150 line) or a quoted C string (which does not contain an implicit newline).
25153 @item "~" @var{string-output}
25154 The console output stream contains text that should be displayed in the
25155 CLI console window. It contains the textual responses to CLI commands.
25157 @item "@@" @var{string-output}
25158 The target output stream contains any textual output from the running
25159 target. This is only present when GDB's event loop is truly
25160 asynchronous, which is currently only the case for remote targets.
25162 @item "&" @var{string-output}
25163 The log stream contains debugging messages being produced by @value{GDBN}'s
25167 @node GDB/MI Async Records
25168 @subsection @sc{gdb/mi} Async Records
25170 @cindex async records in @sc{gdb/mi}
25171 @cindex @sc{gdb/mi}, async records
25172 @dfn{Async} records are used to notify the @sc{gdb/mi} client of
25173 additional changes that have occurred. Those changes can either be a
25174 consequence of @sc{gdb/mi} commands (e.g., a breakpoint modified) or a result of
25175 target activity (e.g., target stopped).
25177 The following is the list of possible async records:
25181 @item *running,thread-id="@var{thread}"
25182 The target is now running. The @var{thread} field tells which
25183 specific thread is now running, and can be @samp{all} if all threads
25184 are running. The frontend should assume that no interaction with a
25185 running thread is possible after this notification is produced.
25186 The frontend should not assume that this notification is output
25187 only once for any command. @value{GDBN} may emit this notification
25188 several times, either for different threads, because it cannot resume
25189 all threads together, or even for a single thread, if the thread must
25190 be stepped though some code before letting it run freely.
25192 @item *stopped,reason="@var{reason}",thread-id="@var{id}",stopped-threads="@var{stopped}",core="@var{core}"
25193 The target has stopped. The @var{reason} field can have one of the
25197 @item breakpoint-hit
25198 A breakpoint was reached.
25199 @item watchpoint-trigger
25200 A watchpoint was triggered.
25201 @item read-watchpoint-trigger
25202 A read watchpoint was triggered.
25203 @item access-watchpoint-trigger
25204 An access watchpoint was triggered.
25205 @item function-finished
25206 An -exec-finish or similar CLI command was accomplished.
25207 @item location-reached
25208 An -exec-until or similar CLI command was accomplished.
25209 @item watchpoint-scope
25210 A watchpoint has gone out of scope.
25211 @item end-stepping-range
25212 An -exec-next, -exec-next-instruction, -exec-step, -exec-step-instruction or
25213 similar CLI command was accomplished.
25214 @item exited-signalled
25215 The inferior exited because of a signal.
25217 The inferior exited.
25218 @item exited-normally
25219 The inferior exited normally.
25220 @item signal-received
25221 A signal was received by the inferior.
25223 The inferior has stopped due to a library being loaded or unloaded.
25224 This can happen when @code{stop-on-solib-events} (@pxref{Files}) is
25225 set or when a @code{catch load} or @code{catch unload} catchpoint is
25226 in use (@pxref{Set Catchpoints}).
25228 The inferior has forked. This is reported when @code{catch fork}
25229 (@pxref{Set Catchpoints}) has been used.
25231 The inferior has vforked. This is reported in when @code{catch vfork}
25232 (@pxref{Set Catchpoints}) has been used.
25233 @item syscall-entry
25234 The inferior entered a system call. This is reported when @code{catch
25235 syscall} (@pxref{Set Catchpoints}) has been used.
25236 @item syscall-entry
25237 The inferior returned from a system call. This is reported when
25238 @code{catch syscall} (@pxref{Set Catchpoints}) has been used.
25240 The inferior called @code{exec}. This is reported when @code{catch exec}
25241 (@pxref{Set Catchpoints}) has been used.
25244 The @var{id} field identifies the thread that directly caused the stop
25245 -- for example by hitting a breakpoint. Depending on whether all-stop
25246 mode is in effect (@pxref{All-Stop Mode}), @value{GDBN} may either
25247 stop all threads, or only the thread that directly triggered the stop.
25248 If all threads are stopped, the @var{stopped} field will have the
25249 value of @code{"all"}. Otherwise, the value of the @var{stopped}
25250 field will be a list of thread identifiers. Presently, this list will
25251 always include a single thread, but frontend should be prepared to see
25252 several threads in the list. The @var{core} field reports the
25253 processor core on which the stop event has happened. This field may be absent
25254 if such information is not available.
25256 @item =thread-group-added,id="@var{id}"
25257 @itemx =thread-group-removed,id="@var{id}"
25258 A thread group was either added or removed. The @var{id} field
25259 contains the @value{GDBN} identifier of the thread group. When a thread
25260 group is added, it generally might not be associated with a running
25261 process. When a thread group is removed, its id becomes invalid and
25262 cannot be used in any way.
25264 @item =thread-group-started,id="@var{id}",pid="@var{pid}"
25265 A thread group became associated with a running program,
25266 either because the program was just started or the thread group
25267 was attached to a program. The @var{id} field contains the
25268 @value{GDBN} identifier of the thread group. The @var{pid} field
25269 contains process identifier, specific to the operating system.
25271 @item =thread-group-exited,id="@var{id}"[,exit-code="@var{code}"]
25272 A thread group is no longer associated with a running program,
25273 either because the program has exited, or because it was detached
25274 from. The @var{id} field contains the @value{GDBN} identifier of the
25275 thread group. @var{code} is the exit code of the inferior; it exists
25276 only when the inferior exited with some code.
25278 @item =thread-created,id="@var{id}",group-id="@var{gid}"
25279 @itemx =thread-exited,id="@var{id}",group-id="@var{gid}"
25280 A thread either was created, or has exited. The @var{id} field
25281 contains the @value{GDBN} identifier of the thread. The @var{gid}
25282 field identifies the thread group this thread belongs to.
25284 @item =thread-selected,id="@var{id}"
25285 Informs that the selected thread was changed as result of the last
25286 command. This notification is not emitted as result of @code{-thread-select}
25287 command but is emitted whenever an MI command that is not documented
25288 to change the selected thread actually changes it. In particular,
25289 invoking, directly or indirectly (via user-defined command), the CLI
25290 @code{thread} command, will generate this notification.
25292 We suggest that in response to this notification, front ends
25293 highlight the selected thread and cause subsequent commands to apply to
25296 @item =library-loaded,...
25297 Reports that a new library file was loaded by the program. This
25298 notification has 4 fields---@var{id}, @var{target-name},
25299 @var{host-name}, and @var{symbols-loaded}. The @var{id} field is an
25300 opaque identifier of the library. For remote debugging case,
25301 @var{target-name} and @var{host-name} fields give the name of the
25302 library file on the target, and on the host respectively. For native
25303 debugging, both those fields have the same value. The
25304 @var{symbols-loaded} field is emitted only for backward compatibility
25305 and should not be relied on to convey any useful information. The
25306 @var{thread-group} field, if present, specifies the id of the thread
25307 group in whose context the library was loaded. If the field is
25308 absent, it means the library was loaded in the context of all present
25311 @item =library-unloaded,...
25312 Reports that a library was unloaded by the program. This notification
25313 has 3 fields---@var{id}, @var{target-name} and @var{host-name} with
25314 the same meaning as for the @code{=library-loaded} notification.
25315 The @var{thread-group} field, if present, specifies the id of the
25316 thread group in whose context the library was unloaded. If the field is
25317 absent, it means the library was unloaded in the context of all present
25320 @item =traceframe-changed,num=@var{tfnum},tracepoint=@var{tpnum}
25321 @itemx =traceframe-changed,end
25322 Reports that the trace frame was changed and its new number is
25323 @var{tfnum}. The number of the tracepoint associated with this trace
25324 frame is @var{tpnum}.
25326 @item =tsv-created,name=@var{name},initial=@var{initial}
25327 Reports that the new trace state variable @var{name} is created with
25328 initial value @var{initial}.
25330 @item =tsv-deleted,name=@var{name}
25331 @itemx =tsv-deleted
25332 Reports that the trace state variable @var{name} is deleted or all
25333 trace state variables are deleted.
25335 @item =tsv-modified,name=@var{name},initial=@var{initial}[,current=@var{current}]
25336 Reports that the trace state variable @var{name} is modified with
25337 the initial value @var{initial}. The current value @var{current} of
25338 trace state variable is optional and is reported if the current
25339 value of trace state variable is known.
25341 @item =breakpoint-created,bkpt=@{...@}
25342 @itemx =breakpoint-modified,bkpt=@{...@}
25343 @itemx =breakpoint-deleted,id=@var{number}
25344 Reports that a breakpoint was created, modified, or deleted,
25345 respectively. Only user-visible breakpoints are reported to the MI
25348 The @var{bkpt} argument is of the same form as returned by the various
25349 breakpoint commands; @xref{GDB/MI Breakpoint Commands}. The
25350 @var{number} is the ordinal number of the breakpoint.
25352 Note that if a breakpoint is emitted in the result record of a
25353 command, then it will not also be emitted in an async record.
25355 @item =record-started,thread-group="@var{id}"
25356 @itemx =record-stopped,thread-group="@var{id}"
25357 Execution log recording was either started or stopped on an
25358 inferior. The @var{id} is the @value{GDBN} identifier of the thread
25359 group corresponding to the affected inferior.
25361 @item =cmd-param-changed,param=@var{param},value=@var{value}
25362 Reports that a parameter of the command @code{set @var{param}} is
25363 changed to @var{value}. In the multi-word @code{set} command,
25364 the @var{param} is the whole parameter list to @code{set} command.
25365 For example, In command @code{set check type on}, @var{param}
25366 is @code{check type} and @var{value} is @code{on}.
25368 @item =memory-changed,thread-group=@var{id},addr=@var{addr},len=@var{len}[,type="code"]
25369 Reports that bytes from @var{addr} to @var{data} + @var{len} were
25370 written in an inferior. The @var{id} is the identifier of the
25371 thread group corresponding to the affected inferior. The optional
25372 @code{type="code"} part is reported if the memory written to holds
25376 @node GDB/MI Breakpoint Information
25377 @subsection @sc{gdb/mi} Breakpoint Information
25379 When @value{GDBN} reports information about a breakpoint, a
25380 tracepoint, a watchpoint, or a catchpoint, it uses a tuple with the
25385 The breakpoint number. For a breakpoint that represents one location
25386 of a multi-location breakpoint, this will be a dotted pair, like
25390 The type of the breakpoint. For ordinary breakpoints this will be
25391 @samp{breakpoint}, but many values are possible.
25394 If the type of the breakpoint is @samp{catchpoint}, then this
25395 indicates the exact type of catchpoint.
25398 This is the breakpoint disposition---either @samp{del}, meaning that
25399 the breakpoint will be deleted at the next stop, or @samp{keep},
25400 meaning that the breakpoint will not be deleted.
25403 This indicates whether the breakpoint is enabled, in which case the
25404 value is @samp{y}, or disabled, in which case the value is @samp{n}.
25405 Note that this is not the same as the field @code{enable}.
25408 The address of the breakpoint. This may be a hexidecimal number,
25409 giving the address; or the string @samp{<PENDING>}, for a pending
25410 breakpoint; or the string @samp{<MULTIPLE>}, for a breakpoint with
25411 multiple locations. This field will not be present if no address can
25412 be determined. For example, a watchpoint does not have an address.
25415 If known, the function in which the breakpoint appears.
25416 If not known, this field is not present.
25419 The name of the source file which contains this function, if known.
25420 If not known, this field is not present.
25423 The full file name of the source file which contains this function, if
25424 known. If not known, this field is not present.
25427 The line number at which this breakpoint appears, if known.
25428 If not known, this field is not present.
25431 If the source file is not known, this field may be provided. If
25432 provided, this holds the address of the breakpoint, possibly followed
25436 If this breakpoint is pending, this field is present and holds the
25437 text used to set the breakpoint, as entered by the user.
25440 Where this breakpoint's condition is evaluated, either @samp{host} or
25444 If this is a thread-specific breakpoint, then this identifies the
25445 thread in which the breakpoint can trigger.
25448 If this breakpoint is restricted to a particular Ada task, then this
25449 field will hold the task identifier.
25452 If the breakpoint is conditional, this is the condition expression.
25455 The ignore count of the breakpoint.
25458 The enable count of the breakpoint.
25460 @item traceframe-usage
25463 @item static-tracepoint-marker-string-id
25464 For a static tracepoint, the name of the static tracepoint marker.
25467 For a masked watchpoint, this is the mask.
25470 A tracepoint's pass count.
25472 @item original-location
25473 The location of the breakpoint as originally specified by the user.
25474 This field is optional.
25477 The number of times the breakpoint has been hit.
25480 This field is only given for tracepoints. This is either @samp{y},
25481 meaning that the tracepoint is installed, or @samp{n}, meaning that it
25485 Some extra data, the exact contents of which are type-dependent.
25489 For example, here is what the output of @code{-break-insert}
25490 (@pxref{GDB/MI Breakpoint Commands}) might be:
25493 -> -break-insert main
25494 <- ^done,bkpt=@{number="1",type="breakpoint",disp="keep",
25495 enabled="y",addr="0x08048564",func="main",file="myprog.c",
25496 fullname="/home/nickrob/myprog.c",line="68",thread-groups=["i1"],
25501 @node GDB/MI Frame Information
25502 @subsection @sc{gdb/mi} Frame Information
25504 Response from many MI commands includes an information about stack
25505 frame. This information is a tuple that may have the following
25510 The level of the stack frame. The innermost frame has the level of
25511 zero. This field is always present.
25514 The name of the function corresponding to the frame. This field may
25515 be absent if @value{GDBN} is unable to determine the function name.
25518 The code address for the frame. This field is always present.
25521 The name of the source files that correspond to the frame's code
25522 address. This field may be absent.
25525 The source line corresponding to the frames' code address. This field
25529 The name of the binary file (either executable or shared library) the
25530 corresponds to the frame's code address. This field may be absent.
25534 @node GDB/MI Thread Information
25535 @subsection @sc{gdb/mi} Thread Information
25537 Whenever @value{GDBN} has to report an information about a thread, it
25538 uses a tuple with the following fields:
25542 The numeric id assigned to the thread by @value{GDBN}. This field is
25546 Target-specific string identifying the thread. This field is always present.
25549 Additional information about the thread provided by the target.
25550 It is supposed to be human-readable and not interpreted by the
25551 frontend. This field is optional.
25554 Either @samp{stopped} or @samp{running}, depending on whether the
25555 thread is presently running. This field is always present.
25558 The value of this field is an integer number of the processor core the
25559 thread was last seen on. This field is optional.
25562 @node GDB/MI Ada Exception Information
25563 @subsection @sc{gdb/mi} Ada Exception Information
25565 Whenever a @code{*stopped} record is emitted because the program
25566 stopped after hitting an exception catchpoint (@pxref{Set Catchpoints}),
25567 @value{GDBN} provides the name of the exception that was raised via
25568 the @code{exception-name} field.
25570 @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
25571 @node GDB/MI Simple Examples
25572 @section Simple Examples of @sc{gdb/mi} Interaction
25573 @cindex @sc{gdb/mi}, simple examples
25575 This subsection presents several simple examples of interaction using
25576 the @sc{gdb/mi} interface. In these examples, @samp{->} means that the
25577 following line is passed to @sc{gdb/mi} as input, while @samp{<-} means
25578 the output received from @sc{gdb/mi}.
25580 Note the line breaks shown in the examples are here only for
25581 readability, they don't appear in the real output.
25583 @subheading Setting a Breakpoint
25585 Setting a breakpoint generates synchronous output which contains detailed
25586 information of the breakpoint.
25589 -> -break-insert main
25590 <- ^done,bkpt=@{number="1",type="breakpoint",disp="keep",
25591 enabled="y",addr="0x08048564",func="main",file="myprog.c",
25592 fullname="/home/nickrob/myprog.c",line="68",thread-groups=["i1"],
25597 @subheading Program Execution
25599 Program execution generates asynchronous records and MI gives the
25600 reason that execution stopped.
25606 <- *stopped,reason="breakpoint-hit",disp="keep",bkptno="1",thread-id="0",
25607 frame=@{addr="0x08048564",func="main",
25608 args=[@{name="argc",value="1"@},@{name="argv",value="0xbfc4d4d4"@}],
25609 file="myprog.c",fullname="/home/nickrob/myprog.c",line="68"@}
25614 <- *stopped,reason="exited-normally"
25618 @subheading Quitting @value{GDBN}
25620 Quitting @value{GDBN} just prints the result class @samp{^exit}.
25628 Please note that @samp{^exit} is printed immediately, but it might
25629 take some time for @value{GDBN} to actually exit. During that time, @value{GDBN}
25630 performs necessary cleanups, including killing programs being debugged
25631 or disconnecting from debug hardware, so the frontend should wait till
25632 @value{GDBN} exits and should only forcibly kill @value{GDBN} if it
25633 fails to exit in reasonable time.
25635 @subheading A Bad Command
25637 Here's what happens if you pass a non-existent command:
25641 <- ^error,msg="Undefined MI command: rubbish"
25646 @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
25647 @node GDB/MI Command Description Format
25648 @section @sc{gdb/mi} Command Description Format
25650 The remaining sections describe blocks of commands. Each block of
25651 commands is laid out in a fashion similar to this section.
25653 @subheading Motivation
25655 The motivation for this collection of commands.
25657 @subheading Introduction
25659 A brief introduction to this collection of commands as a whole.
25661 @subheading Commands
25663 For each command in the block, the following is described:
25665 @subsubheading Synopsis
25668 -command @var{args}@dots{}
25671 @subsubheading Result
25673 @subsubheading @value{GDBN} Command
25675 The corresponding @value{GDBN} CLI command(s), if any.
25677 @subsubheading Example
25679 Example(s) formatted for readability. Some of the described commands have
25680 not been implemented yet and these are labeled N.A.@: (not available).
25683 @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
25684 @node GDB/MI Breakpoint Commands
25685 @section @sc{gdb/mi} Breakpoint Commands
25687 @cindex breakpoint commands for @sc{gdb/mi}
25688 @cindex @sc{gdb/mi}, breakpoint commands
25689 This section documents @sc{gdb/mi} commands for manipulating
25692 @subheading The @code{-break-after} Command
25693 @findex -break-after
25695 @subsubheading Synopsis
25698 -break-after @var{number} @var{count}
25701 The breakpoint number @var{number} is not in effect until it has been
25702 hit @var{count} times. To see how this is reflected in the output of
25703 the @samp{-break-list} command, see the description of the
25704 @samp{-break-list} command below.
25706 @subsubheading @value{GDBN} Command
25708 The corresponding @value{GDBN} command is @samp{ignore}.
25710 @subsubheading Example
25715 ^done,bkpt=@{number="1",type="breakpoint",disp="keep",
25716 enabled="y",addr="0x000100d0",func="main",file="hello.c",
25717 fullname="/home/foo/hello.c",line="5",thread-groups=["i1"],
25725 ^done,BreakpointTable=@{nr_rows="1",nr_cols="6",
25726 hdr=[@{width="3",alignment="-1",col_name="number",colhdr="Num"@},
25727 @{width="14",alignment="-1",col_name="type",colhdr="Type"@},
25728 @{width="4",alignment="-1",col_name="disp",colhdr="Disp"@},
25729 @{width="3",alignment="-1",col_name="enabled",colhdr="Enb"@},
25730 @{width="10",alignment="-1",col_name="addr",colhdr="Address"@},
25731 @{width="40",alignment="2",col_name="what",colhdr="What"@}],
25732 body=[bkpt=@{number="1",type="breakpoint",disp="keep",enabled="y",
25733 addr="0x000100d0",func="main",file="hello.c",fullname="/home/foo/hello.c",
25734 line="5",thread-groups=["i1"],times="0",ignore="3"@}]@}
25739 @subheading The @code{-break-catch} Command
25740 @findex -break-catch
25743 @subheading The @code{-break-commands} Command
25744 @findex -break-commands
25746 @subsubheading Synopsis
25749 -break-commands @var{number} [ @var{command1} ... @var{commandN} ]
25752 Specifies the CLI commands that should be executed when breakpoint
25753 @var{number} is hit. The parameters @var{command1} to @var{commandN}
25754 are the commands. If no command is specified, any previously-set
25755 commands are cleared. @xref{Break Commands}. Typical use of this
25756 functionality is tracing a program, that is, printing of values of
25757 some variables whenever breakpoint is hit and then continuing.
25759 @subsubheading @value{GDBN} Command
25761 The corresponding @value{GDBN} command is @samp{commands}.
25763 @subsubheading Example
25768 ^done,bkpt=@{number="1",type="breakpoint",disp="keep",
25769 enabled="y",addr="0x000100d0",func="main",file="hello.c",
25770 fullname="/home/foo/hello.c",line="5",thread-groups=["i1"],
25773 -break-commands 1 "print v" "continue"
25778 @subheading The @code{-break-condition} Command
25779 @findex -break-condition
25781 @subsubheading Synopsis
25784 -break-condition @var{number} @var{expr}
25787 Breakpoint @var{number} will stop the program only if the condition in
25788 @var{expr} is true. The condition becomes part of the
25789 @samp{-break-list} output (see the description of the @samp{-break-list}
25792 @subsubheading @value{GDBN} Command
25794 The corresponding @value{GDBN} command is @samp{condition}.
25796 @subsubheading Example
25800 -break-condition 1 1
25804 ^done,BreakpointTable=@{nr_rows="1",nr_cols="6",
25805 hdr=[@{width="3",alignment="-1",col_name="number",colhdr="Num"@},
25806 @{width="14",alignment="-1",col_name="type",colhdr="Type"@},
25807 @{width="4",alignment="-1",col_name="disp",colhdr="Disp"@},
25808 @{width="3",alignment="-1",col_name="enabled",colhdr="Enb"@},
25809 @{width="10",alignment="-1",col_name="addr",colhdr="Address"@},
25810 @{width="40",alignment="2",col_name="what",colhdr="What"@}],
25811 body=[bkpt=@{number="1",type="breakpoint",disp="keep",enabled="y",
25812 addr="0x000100d0",func="main",file="hello.c",fullname="/home/foo/hello.c",
25813 line="5",cond="1",thread-groups=["i1"],times="0",ignore="3"@}]@}
25817 @subheading The @code{-break-delete} Command
25818 @findex -break-delete
25820 @subsubheading Synopsis
25823 -break-delete ( @var{breakpoint} )+
25826 Delete the breakpoint(s) whose number(s) are specified in the argument
25827 list. This is obviously reflected in the breakpoint list.
25829 @subsubheading @value{GDBN} Command
25831 The corresponding @value{GDBN} command is @samp{delete}.
25833 @subsubheading Example
25841 ^done,BreakpointTable=@{nr_rows="0",nr_cols="6",
25842 hdr=[@{width="3",alignment="-1",col_name="number",colhdr="Num"@},
25843 @{width="14",alignment="-1",col_name="type",colhdr="Type"@},
25844 @{width="4",alignment="-1",col_name="disp",colhdr="Disp"@},
25845 @{width="3",alignment="-1",col_name="enabled",colhdr="Enb"@},
25846 @{width="10",alignment="-1",col_name="addr",colhdr="Address"@},
25847 @{width="40",alignment="2",col_name="what",colhdr="What"@}],
25852 @subheading The @code{-break-disable} Command
25853 @findex -break-disable
25855 @subsubheading Synopsis
25858 -break-disable ( @var{breakpoint} )+
25861 Disable the named @var{breakpoint}(s). The field @samp{enabled} in the
25862 break list is now set to @samp{n} for the named @var{breakpoint}(s).
25864 @subsubheading @value{GDBN} Command
25866 The corresponding @value{GDBN} command is @samp{disable}.
25868 @subsubheading Example
25876 ^done,BreakpointTable=@{nr_rows="1",nr_cols="6",
25877 hdr=[@{width="3",alignment="-1",col_name="number",colhdr="Num"@},
25878 @{width="14",alignment="-1",col_name="type",colhdr="Type"@},
25879 @{width="4",alignment="-1",col_name="disp",colhdr="Disp"@},
25880 @{width="3",alignment="-1",col_name="enabled",colhdr="Enb"@},
25881 @{width="10",alignment="-1",col_name="addr",colhdr="Address"@},
25882 @{width="40",alignment="2",col_name="what",colhdr="What"@}],
25883 body=[bkpt=@{number="2",type="breakpoint",disp="keep",enabled="n",
25884 addr="0x000100d0",func="main",file="hello.c",fullname="/home/foo/hello.c",
25885 line="5",thread-groups=["i1"],times="0"@}]@}
25889 @subheading The @code{-break-enable} Command
25890 @findex -break-enable
25892 @subsubheading Synopsis
25895 -break-enable ( @var{breakpoint} )+
25898 Enable (previously disabled) @var{breakpoint}(s).
25900 @subsubheading @value{GDBN} Command
25902 The corresponding @value{GDBN} command is @samp{enable}.
25904 @subsubheading Example
25912 ^done,BreakpointTable=@{nr_rows="1",nr_cols="6",
25913 hdr=[@{width="3",alignment="-1",col_name="number",colhdr="Num"@},
25914 @{width="14",alignment="-1",col_name="type",colhdr="Type"@},
25915 @{width="4",alignment="-1",col_name="disp",colhdr="Disp"@},
25916 @{width="3",alignment="-1",col_name="enabled",colhdr="Enb"@},
25917 @{width="10",alignment="-1",col_name="addr",colhdr="Address"@},
25918 @{width="40",alignment="2",col_name="what",colhdr="What"@}],
25919 body=[bkpt=@{number="2",type="breakpoint",disp="keep",enabled="y",
25920 addr="0x000100d0",func="main",file="hello.c",fullname="/home/foo/hello.c",
25921 line="5",thread-groups=["i1"],times="0"@}]@}
25925 @subheading The @code{-break-info} Command
25926 @findex -break-info
25928 @subsubheading Synopsis
25931 -break-info @var{breakpoint}
25935 Get information about a single breakpoint.
25937 The result is a table of breakpoints. @xref{GDB/MI Breakpoint
25938 Information}, for details on the format of each breakpoint in the
25941 @subsubheading @value{GDBN} Command
25943 The corresponding @value{GDBN} command is @samp{info break @var{breakpoint}}.
25945 @subsubheading Example
25948 @subheading The @code{-break-insert} Command
25949 @findex -break-insert
25951 @subsubheading Synopsis
25954 -break-insert [ -t ] [ -h ] [ -f ] [ -d ] [ -a ]
25955 [ -c @var{condition} ] [ -i @var{ignore-count} ]
25956 [ -p @var{thread-id} ] [ @var{location} ]
25960 If specified, @var{location}, can be one of:
25967 @item filename:linenum
25968 @item filename:function
25972 The possible optional parameters of this command are:
25976 Insert a temporary breakpoint.
25978 Insert a hardware breakpoint.
25980 If @var{location} cannot be parsed (for example if it
25981 refers to unknown files or functions), create a pending
25982 breakpoint. Without this flag, @value{GDBN} will report
25983 an error, and won't create a breakpoint, if @var{location}
25986 Create a disabled breakpoint.
25988 Create a tracepoint. @xref{Tracepoints}. When this parameter
25989 is used together with @samp{-h}, a fast tracepoint is created.
25990 @item -c @var{condition}
25991 Make the breakpoint conditional on @var{condition}.
25992 @item -i @var{ignore-count}
25993 Initialize the @var{ignore-count}.
25994 @item -p @var{thread-id}
25995 Restrict the breakpoint to the specified @var{thread-id}.
25998 @subsubheading Result
26000 @xref{GDB/MI Breakpoint Information}, for details on the format of the
26001 resulting breakpoint.
26003 Note: this format is open to change.
26004 @c An out-of-band breakpoint instead of part of the result?
26006 @subsubheading @value{GDBN} Command
26008 The corresponding @value{GDBN} commands are @samp{break}, @samp{tbreak},
26009 @samp{hbreak}, and @samp{thbreak}. @c and @samp{rbreak}.
26011 @subsubheading Example
26016 ^done,bkpt=@{number="1",addr="0x0001072c",file="recursive2.c",
26017 fullname="/home/foo/recursive2.c,line="4",thread-groups=["i1"],
26020 -break-insert -t foo
26021 ^done,bkpt=@{number="2",addr="0x00010774",file="recursive2.c",
26022 fullname="/home/foo/recursive2.c,line="11",thread-groups=["i1"],
26026 ^done,BreakpointTable=@{nr_rows="2",nr_cols="6",
26027 hdr=[@{width="3",alignment="-1",col_name="number",colhdr="Num"@},
26028 @{width="14",alignment="-1",col_name="type",colhdr="Type"@},
26029 @{width="4",alignment="-1",col_name="disp",colhdr="Disp"@},
26030 @{width="3",alignment="-1",col_name="enabled",colhdr="Enb"@},
26031 @{width="10",alignment="-1",col_name="addr",colhdr="Address"@},
26032 @{width="40",alignment="2",col_name="what",colhdr="What"@}],
26033 body=[bkpt=@{number="1",type="breakpoint",disp="keep",enabled="y",
26034 addr="0x0001072c", func="main",file="recursive2.c",
26035 fullname="/home/foo/recursive2.c,"line="4",thread-groups=["i1"],
26037 bkpt=@{number="2",type="breakpoint",disp="del",enabled="y",
26038 addr="0x00010774",func="foo",file="recursive2.c",
26039 fullname="/home/foo/recursive2.c",line="11",thread-groups=["i1"],
26042 @c -break-insert -r foo.*
26043 @c ~int foo(int, int);
26044 @c ^done,bkpt=@{number="3",addr="0x00010774",file="recursive2.c,
26045 @c "fullname="/home/foo/recursive2.c",line="11",thread-groups=["i1"],
26050 @subheading The @code{-dprintf-insert} Command
26051 @findex -dprintf-insert
26053 @subsubheading Synopsis
26056 -dprintf-insert [ -t ] [ -f ] [ -d ]
26057 [ -c @var{condition} ] [ -i @var{ignore-count} ]
26058 [ -p @var{thread-id} ] [ @var{location} ] [ @var{format} ]
26063 If specified, @var{location}, can be one of:
26066 @item @var{function}
26069 @c @item @var{linenum}
26070 @item @var{filename}:@var{linenum}
26071 @item @var{filename}:function
26072 @item *@var{address}
26075 The possible optional parameters of this command are:
26079 Insert a temporary breakpoint.
26081 If @var{location} cannot be parsed (for example, if it
26082 refers to unknown files or functions), create a pending
26083 breakpoint. Without this flag, @value{GDBN} will report
26084 an error, and won't create a breakpoint, if @var{location}
26087 Create a disabled breakpoint.
26088 @item -c @var{condition}
26089 Make the breakpoint conditional on @var{condition}.
26090 @item -i @var{ignore-count}
26091 Set the ignore count of the breakpoint (@pxref{Conditions, ignore count})
26092 to @var{ignore-count}.
26093 @item -p @var{thread-id}
26094 Restrict the breakpoint to the specified @var{thread-id}.
26097 @subsubheading Result
26099 @xref{GDB/MI Breakpoint Information}, for details on the format of the
26100 resulting breakpoint.
26102 @c An out-of-band breakpoint instead of part of the result?
26104 @subsubheading @value{GDBN} Command
26106 The corresponding @value{GDBN} command is @samp{dprintf}.
26108 @subsubheading Example
26112 4-dprintf-insert foo "At foo entry\n"
26113 4^done,bkpt=@{number="1",type="dprintf",disp="keep",enabled="y",
26114 addr="0x000000000040061b",func="foo",file="mi-dprintf.c",
26115 fullname="mi-dprintf.c",line="25",thread-groups=["i1"],
26116 times="0",script=@{"printf \"At foo entry\\n\"","continue"@},
26117 original-location="foo"@}
26119 5-dprintf-insert 26 "arg=%d, g=%d\n" arg g
26120 5^done,bkpt=@{number="2",type="dprintf",disp="keep",enabled="y",
26121 addr="0x000000000040062a",func="foo",file="mi-dprintf.c",
26122 fullname="mi-dprintf.c",line="26",thread-groups=["i1"],
26123 times="0",script=@{"printf \"arg=%d, g=%d\\n\", arg, g","continue"@},
26124 original-location="mi-dprintf.c:26"@}
26128 @subheading The @code{-break-list} Command
26129 @findex -break-list
26131 @subsubheading Synopsis
26137 Displays the list of inserted breakpoints, showing the following fields:
26141 number of the breakpoint
26143 type of the breakpoint: @samp{breakpoint} or @samp{watchpoint}
26145 should the breakpoint be deleted or disabled when it is hit: @samp{keep}
26148 is the breakpoint enabled or no: @samp{y} or @samp{n}
26150 memory location at which the breakpoint is set
26152 logical location of the breakpoint, expressed by function name, file
26154 @item Thread-groups
26155 list of thread groups to which this breakpoint applies
26157 number of times the breakpoint has been hit
26160 If there are no breakpoints or watchpoints, the @code{BreakpointTable}
26161 @code{body} field is an empty list.
26163 @subsubheading @value{GDBN} Command
26165 The corresponding @value{GDBN} command is @samp{info break}.
26167 @subsubheading Example
26172 ^done,BreakpointTable=@{nr_rows="2",nr_cols="6",
26173 hdr=[@{width="3",alignment="-1",col_name="number",colhdr="Num"@},
26174 @{width="14",alignment="-1",col_name="type",colhdr="Type"@},
26175 @{width="4",alignment="-1",col_name="disp",colhdr="Disp"@},
26176 @{width="3",alignment="-1",col_name="enabled",colhdr="Enb"@},
26177 @{width="10",alignment="-1",col_name="addr",colhdr="Address"@},
26178 @{width="40",alignment="2",col_name="what",colhdr="What"@}],
26179 body=[bkpt=@{number="1",type="breakpoint",disp="keep",enabled="y",
26180 addr="0x000100d0",func="main",file="hello.c",line="5",thread-groups=["i1"],
26182 bkpt=@{number="2",type="breakpoint",disp="keep",enabled="y",
26183 addr="0x00010114",func="foo",file="hello.c",fullname="/home/foo/hello.c",
26184 line="13",thread-groups=["i1"],times="0"@}]@}
26188 Here's an example of the result when there are no breakpoints:
26193 ^done,BreakpointTable=@{nr_rows="0",nr_cols="6",
26194 hdr=[@{width="3",alignment="-1",col_name="number",colhdr="Num"@},
26195 @{width="14",alignment="-1",col_name="type",colhdr="Type"@},
26196 @{width="4",alignment="-1",col_name="disp",colhdr="Disp"@},
26197 @{width="3",alignment="-1",col_name="enabled",colhdr="Enb"@},
26198 @{width="10",alignment="-1",col_name="addr",colhdr="Address"@},
26199 @{width="40",alignment="2",col_name="what",colhdr="What"@}],
26204 @subheading The @code{-break-passcount} Command
26205 @findex -break-passcount
26207 @subsubheading Synopsis
26210 -break-passcount @var{tracepoint-number} @var{passcount}
26213 Set the passcount for tracepoint @var{tracepoint-number} to
26214 @var{passcount}. If the breakpoint referred to by @var{tracepoint-number}
26215 is not a tracepoint, error is emitted. This corresponds to CLI
26216 command @samp{passcount}.
26218 @subheading The @code{-break-watch} Command
26219 @findex -break-watch
26221 @subsubheading Synopsis
26224 -break-watch [ -a | -r ]
26227 Create a watchpoint. With the @samp{-a} option it will create an
26228 @dfn{access} watchpoint, i.e., a watchpoint that triggers either on a
26229 read from or on a write to the memory location. With the @samp{-r}
26230 option, the watchpoint created is a @dfn{read} watchpoint, i.e., it will
26231 trigger only when the memory location is accessed for reading. Without
26232 either of the options, the watchpoint created is a regular watchpoint,
26233 i.e., it will trigger when the memory location is accessed for writing.
26234 @xref{Set Watchpoints, , Setting Watchpoints}.
26236 Note that @samp{-break-list} will report a single list of watchpoints and
26237 breakpoints inserted.
26239 @subsubheading @value{GDBN} Command
26241 The corresponding @value{GDBN} commands are @samp{watch}, @samp{awatch}, and
26244 @subsubheading Example
26246 Setting a watchpoint on a variable in the @code{main} function:
26251 ^done,wpt=@{number="2",exp="x"@}
26256 *stopped,reason="watchpoint-trigger",wpt=@{number="2",exp="x"@},
26257 value=@{old="-268439212",new="55"@},
26258 frame=@{func="main",args=[],file="recursive2.c",
26259 fullname="/home/foo/bar/recursive2.c",line="5"@}
26263 Setting a watchpoint on a variable local to a function. @value{GDBN} will stop
26264 the program execution twice: first for the variable changing value, then
26265 for the watchpoint going out of scope.
26270 ^done,wpt=@{number="5",exp="C"@}
26275 *stopped,reason="watchpoint-trigger",
26276 wpt=@{number="5",exp="C"@},value=@{old="-276895068",new="3"@},
26277 frame=@{func="callee4",args=[],
26278 file="../../../devo/gdb/testsuite/gdb.mi/basics.c",
26279 fullname="/home/foo/bar/devo/gdb/testsuite/gdb.mi/basics.c",line="13"@}
26284 *stopped,reason="watchpoint-scope",wpnum="5",
26285 frame=@{func="callee3",args=[@{name="strarg",
26286 value="0x11940 \"A string argument.\""@}],
26287 file="../../../devo/gdb/testsuite/gdb.mi/basics.c",
26288 fullname="/home/foo/bar/devo/gdb/testsuite/gdb.mi/basics.c",line="18"@}
26292 Listing breakpoints and watchpoints, at different points in the program
26293 execution. Note that once the watchpoint goes out of scope, it is
26299 ^done,wpt=@{number="2",exp="C"@}
26302 ^done,BreakpointTable=@{nr_rows="2",nr_cols="6",
26303 hdr=[@{width="3",alignment="-1",col_name="number",colhdr="Num"@},
26304 @{width="14",alignment="-1",col_name="type",colhdr="Type"@},
26305 @{width="4",alignment="-1",col_name="disp",colhdr="Disp"@},
26306 @{width="3",alignment="-1",col_name="enabled",colhdr="Enb"@},
26307 @{width="10",alignment="-1",col_name="addr",colhdr="Address"@},
26308 @{width="40",alignment="2",col_name="what",colhdr="What"@}],
26309 body=[bkpt=@{number="1",type="breakpoint",disp="keep",enabled="y",
26310 addr="0x00010734",func="callee4",
26311 file="../../../devo/gdb/testsuite/gdb.mi/basics.c",
26312 fullname="/home/foo/devo/gdb/testsuite/gdb.mi/basics.c"line="8",thread-groups=["i1"],
26314 bkpt=@{number="2",type="watchpoint",disp="keep",
26315 enabled="y",addr="",what="C",thread-groups=["i1"],times="0"@}]@}
26320 *stopped,reason="watchpoint-trigger",wpt=@{number="2",exp="C"@},
26321 value=@{old="-276895068",new="3"@},
26322 frame=@{func="callee4",args=[],
26323 file="../../../devo/gdb/testsuite/gdb.mi/basics.c",
26324 fullname="/home/foo/bar/devo/gdb/testsuite/gdb.mi/basics.c",line="13"@}
26327 ^done,BreakpointTable=@{nr_rows="2",nr_cols="6",
26328 hdr=[@{width="3",alignment="-1",col_name="number",colhdr="Num"@},
26329 @{width="14",alignment="-1",col_name="type",colhdr="Type"@},
26330 @{width="4",alignment="-1",col_name="disp",colhdr="Disp"@},
26331 @{width="3",alignment="-1",col_name="enabled",colhdr="Enb"@},
26332 @{width="10",alignment="-1",col_name="addr",colhdr="Address"@},
26333 @{width="40",alignment="2",col_name="what",colhdr="What"@}],
26334 body=[bkpt=@{number="1",type="breakpoint",disp="keep",enabled="y",
26335 addr="0x00010734",func="callee4",
26336 file="../../../devo/gdb/testsuite/gdb.mi/basics.c",
26337 fullname="/home/foo/devo/gdb/testsuite/gdb.mi/basics.c",line="8",thread-groups=["i1"],
26339 bkpt=@{number="2",type="watchpoint",disp="keep",
26340 enabled="y",addr="",what="C",thread-groups=["i1"],times="-5"@}]@}
26344 ^done,reason="watchpoint-scope",wpnum="2",
26345 frame=@{func="callee3",args=[@{name="strarg",
26346 value="0x11940 \"A string argument.\""@}],
26347 file="../../../devo/gdb/testsuite/gdb.mi/basics.c",
26348 fullname="/home/foo/bar/devo/gdb/testsuite/gdb.mi/basics.c",line="18"@}
26351 ^done,BreakpointTable=@{nr_rows="1",nr_cols="6",
26352 hdr=[@{width="3",alignment="-1",col_name="number",colhdr="Num"@},
26353 @{width="14",alignment="-1",col_name="type",colhdr="Type"@},
26354 @{width="4",alignment="-1",col_name="disp",colhdr="Disp"@},
26355 @{width="3",alignment="-1",col_name="enabled",colhdr="Enb"@},
26356 @{width="10",alignment="-1",col_name="addr",colhdr="Address"@},
26357 @{width="40",alignment="2",col_name="what",colhdr="What"@}],
26358 body=[bkpt=@{number="1",type="breakpoint",disp="keep",enabled="y",
26359 addr="0x00010734",func="callee4",
26360 file="../../../devo/gdb/testsuite/gdb.mi/basics.c",
26361 fullname="/home/foo/devo/gdb/testsuite/gdb.mi/basics.c",line="8",
26362 thread-groups=["i1"],times="1"@}]@}
26367 @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
26368 @node GDB/MI Catchpoint Commands
26369 @section @sc{gdb/mi} Catchpoint Commands
26371 This section documents @sc{gdb/mi} commands for manipulating
26375 * Shared Library GDB/MI Catchpoint Commands::
26376 * Ada Exception GDB/MI Catchpoint Commands::
26379 @node Shared Library GDB/MI Catchpoint Commands
26380 @subsection Shared Library @sc{gdb/mi} Catchpoints
26382 @subheading The @code{-catch-load} Command
26383 @findex -catch-load
26385 @subsubheading Synopsis
26388 -catch-load [ -t ] [ -d ] @var{regexp}
26391 Add a catchpoint for library load events. If the @samp{-t} option is used,
26392 the catchpoint is a temporary one (@pxref{Set Breaks, ,Setting
26393 Breakpoints}). If the @samp{-d} option is used, the catchpoint is created
26394 in a disabled state. The @samp{regexp} argument is a regular
26395 expression used to match the name of the loaded library.
26398 @subsubheading @value{GDBN} Command
26400 The corresponding @value{GDBN} command is @samp{catch load}.
26402 @subsubheading Example
26405 -catch-load -t foo.so
26406 ^done,bkpt=@{number="1",type="catchpoint",disp="del",enabled="y",
26407 what="load of library matching foo.so",catch-type="load",times="0"@}
26412 @subheading The @code{-catch-unload} Command
26413 @findex -catch-unload
26415 @subsubheading Synopsis
26418 -catch-unload [ -t ] [ -d ] @var{regexp}
26421 Add a catchpoint for library unload events. If the @samp{-t} option is
26422 used, the catchpoint is a temporary one (@pxref{Set Breaks, ,Setting
26423 Breakpoints}). If the @samp{-d} option is used, the catchpoint is
26424 created in a disabled state. The @samp{regexp} argument is a regular
26425 expression used to match the name of the unloaded library.
26427 @subsubheading @value{GDBN} Command
26429 The corresponding @value{GDBN} command is @samp{catch unload}.
26431 @subsubheading Example
26434 -catch-unload -d bar.so
26435 ^done,bkpt=@{number="2",type="catchpoint",disp="keep",enabled="n",
26436 what="load of library matching bar.so",catch-type="unload",times="0"@}
26440 @node Ada Exception GDB/MI Catchpoint Commands
26441 @subsection Ada Exception @sc{gdb/mi} Catchpoints
26443 The following @sc{gdb/mi} commands can be used to create catchpoints
26444 that stop the execution when Ada exceptions are being raised.
26446 @subheading The @code{-catch-assert} Command
26447 @findex -catch-assert
26449 @subsubheading Synopsis
26452 -catch-assert [ -c @var{condition}] [ -d ] [ -t ]
26455 Add a catchpoint for failed Ada assertions.
26457 The possible optional parameters for this command are:
26460 @item -c @var{condition}
26461 Make the catchpoint conditional on @var{condition}.
26463 Create a disabled catchpoint.
26465 Create a temporary catchpoint.
26468 @subsubheading @value{GDBN} Command
26470 The corresponding @value{GDBN} command is @samp{catch assert}.
26472 @subsubheading Example
26476 ^done,bkptno="5",bkpt=@{number="5",type="breakpoint",disp="keep",
26477 enabled="y",addr="0x0000000000404888",what="failed Ada assertions",
26478 thread-groups=["i1"],times="0",
26479 original-location="__gnat_debug_raise_assert_failure"@}
26483 @subheading The @code{-catch-exception} Command
26484 @findex -catch-exception
26486 @subsubheading Synopsis
26489 -catch-exception [ -c @var{condition}] [ -d ] [ -e @var{exception-name} ]
26493 Add a catchpoint stopping when Ada exceptions are raised.
26494 By default, the command stops the program when any Ada exception
26495 gets raised. But it is also possible, by using some of the
26496 optional parameters described below, to create more selective
26499 The possible optional parameters for this command are:
26502 @item -c @var{condition}
26503 Make the catchpoint conditional on @var{condition}.
26505 Create a disabled catchpoint.
26506 @item -e @var{exception-name}
26507 Only stop when @var{exception-name} is raised. This option cannot
26508 be used combined with @samp{-u}.
26510 Create a temporary catchpoint.
26512 Stop only when an unhandled exception gets raised. This option
26513 cannot be used combined with @samp{-e}.
26516 @subsubheading @value{GDBN} Command
26518 The corresponding @value{GDBN} commands are @samp{catch exception}
26519 and @samp{catch exception unhandled}.
26521 @subsubheading Example
26524 -catch-exception -e Program_Error
26525 ^done,bkptno="4",bkpt=@{number="4",type="breakpoint",disp="keep",
26526 enabled="y",addr="0x0000000000404874",
26527 what="`Program_Error' Ada exception", thread-groups=["i1"],
26528 times="0",original-location="__gnat_debug_raise_exception"@}
26532 @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
26533 @node GDB/MI Program Context
26534 @section @sc{gdb/mi} Program Context
26536 @subheading The @code{-exec-arguments} Command
26537 @findex -exec-arguments
26540 @subsubheading Synopsis
26543 -exec-arguments @var{args}
26546 Set the inferior program arguments, to be used in the next
26549 @subsubheading @value{GDBN} Command
26551 The corresponding @value{GDBN} command is @samp{set args}.
26553 @subsubheading Example
26557 -exec-arguments -v word
26564 @subheading The @code{-exec-show-arguments} Command
26565 @findex -exec-show-arguments
26567 @subsubheading Synopsis
26570 -exec-show-arguments
26573 Print the arguments of the program.
26575 @subsubheading @value{GDBN} Command
26577 The corresponding @value{GDBN} command is @samp{show args}.
26579 @subsubheading Example
26584 @subheading The @code{-environment-cd} Command
26585 @findex -environment-cd
26587 @subsubheading Synopsis
26590 -environment-cd @var{pathdir}
26593 Set @value{GDBN}'s working directory.
26595 @subsubheading @value{GDBN} Command
26597 The corresponding @value{GDBN} command is @samp{cd}.
26599 @subsubheading Example
26603 -environment-cd /kwikemart/marge/ezannoni/flathead-dev/devo/gdb
26609 @subheading The @code{-environment-directory} Command
26610 @findex -environment-directory
26612 @subsubheading Synopsis
26615 -environment-directory [ -r ] [ @var{pathdir} ]+
26618 Add directories @var{pathdir} to beginning of search path for source files.
26619 If the @samp{-r} option is used, the search path is reset to the default
26620 search path. If directories @var{pathdir} are supplied in addition to the
26621 @samp{-r} option, the search path is first reset and then addition
26623 Multiple directories may be specified, separated by blanks. Specifying
26624 multiple directories in a single command
26625 results in the directories added to the beginning of the
26626 search path in the same order they were presented in the command.
26627 If blanks are needed as
26628 part of a directory name, double-quotes should be used around
26629 the name. In the command output, the path will show up separated
26630 by the system directory-separator character. The directory-separator
26631 character must not be used
26632 in any directory name.
26633 If no directories are specified, the current search path is displayed.
26635 @subsubheading @value{GDBN} Command
26637 The corresponding @value{GDBN} command is @samp{dir}.
26639 @subsubheading Example
26643 -environment-directory /kwikemart/marge/ezannoni/flathead-dev/devo/gdb
26644 ^done,source-path="/kwikemart/marge/ezannoni/flathead-dev/devo/gdb:$cdir:$cwd"
26646 -environment-directory ""
26647 ^done,source-path="/kwikemart/marge/ezannoni/flathead-dev/devo/gdb:$cdir:$cwd"
26649 -environment-directory -r /home/jjohnstn/src/gdb /usr/src
26650 ^done,source-path="/home/jjohnstn/src/gdb:/usr/src:$cdir:$cwd"
26652 -environment-directory -r
26653 ^done,source-path="$cdir:$cwd"
26658 @subheading The @code{-environment-path} Command
26659 @findex -environment-path
26661 @subsubheading Synopsis
26664 -environment-path [ -r ] [ @var{pathdir} ]+
26667 Add directories @var{pathdir} to beginning of search path for object files.
26668 If the @samp{-r} option is used, the search path is reset to the original
26669 search path that existed at gdb start-up. If directories @var{pathdir} are
26670 supplied in addition to the
26671 @samp{-r} option, the search path is first reset and then addition
26673 Multiple directories may be specified, separated by blanks. Specifying
26674 multiple directories in a single command
26675 results in the directories added to the beginning of the
26676 search path in the same order they were presented in the command.
26677 If blanks are needed as
26678 part of a directory name, double-quotes should be used around
26679 the name. In the command output, the path will show up separated
26680 by the system directory-separator character. The directory-separator
26681 character must not be used
26682 in any directory name.
26683 If no directories are specified, the current path is displayed.
26686 @subsubheading @value{GDBN} Command
26688 The corresponding @value{GDBN} command is @samp{path}.
26690 @subsubheading Example
26695 ^done,path="/usr/bin"
26697 -environment-path /kwikemart/marge/ezannoni/flathead-dev/ppc-eabi/gdb /bin
26698 ^done,path="/kwikemart/marge/ezannoni/flathead-dev/ppc-eabi/gdb:/bin:/usr/bin"
26700 -environment-path -r /usr/local/bin
26701 ^done,path="/usr/local/bin:/usr/bin"
26706 @subheading The @code{-environment-pwd} Command
26707 @findex -environment-pwd
26709 @subsubheading Synopsis
26715 Show the current working directory.
26717 @subsubheading @value{GDBN} Command
26719 The corresponding @value{GDBN} command is @samp{pwd}.
26721 @subsubheading Example
26726 ^done,cwd="/kwikemart/marge/ezannoni/flathead-dev/devo/gdb"
26730 @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
26731 @node GDB/MI Thread Commands
26732 @section @sc{gdb/mi} Thread Commands
26735 @subheading The @code{-thread-info} Command
26736 @findex -thread-info
26738 @subsubheading Synopsis
26741 -thread-info [ @var{thread-id} ]
26744 Reports information about either a specific thread, if
26745 the @var{thread-id} parameter is present, or about all
26746 threads. When printing information about all threads,
26747 also reports the current thread.
26749 @subsubheading @value{GDBN} Command
26751 The @samp{info thread} command prints the same information
26754 @subsubheading Result
26756 The result is a list of threads. The following attributes are
26757 defined for a given thread:
26761 This field exists only for the current thread. It has the value @samp{*}.
26764 The identifier that @value{GDBN} uses to refer to the thread.
26767 The identifier that the target uses to refer to the thread.
26770 Extra information about the thread, in a target-specific format. This
26774 The name of the thread. If the user specified a name using the
26775 @code{thread name} command, then this name is given. Otherwise, if
26776 @value{GDBN} can extract the thread name from the target, then that
26777 name is given. If @value{GDBN} cannot find the thread name, then this
26781 The stack frame currently executing in the thread.
26784 The thread's state. The @samp{state} field may have the following
26789 The thread is stopped. Frame information is available for stopped
26793 The thread is running. There's no frame information for running
26799 If @value{GDBN} can find the CPU core on which this thread is running,
26800 then this field is the core identifier. This field is optional.
26804 @subsubheading Example
26809 @{id="2",target-id="Thread 0xb7e14b90 (LWP 21257)",
26810 frame=@{level="0",addr="0xffffe410",func="__kernel_vsyscall",
26811 args=[]@},state="running"@},
26812 @{id="1",target-id="Thread 0xb7e156b0 (LWP 21254)",
26813 frame=@{level="0",addr="0x0804891f",func="foo",
26814 args=[@{name="i",value="10"@}],
26815 file="/tmp/a.c",fullname="/tmp/a.c",line="158"@},
26816 state="running"@}],
26817 current-thread-id="1"
26821 @subheading The @code{-thread-list-ids} Command
26822 @findex -thread-list-ids
26824 @subsubheading Synopsis
26830 Produces a list of the currently known @value{GDBN} thread ids. At the
26831 end of the list it also prints the total number of such threads.
26833 This command is retained for historical reasons, the
26834 @code{-thread-info} command should be used instead.
26836 @subsubheading @value{GDBN} Command
26838 Part of @samp{info threads} supplies the same information.
26840 @subsubheading Example
26845 ^done,thread-ids=@{thread-id="3",thread-id="2",thread-id="1"@},
26846 current-thread-id="1",number-of-threads="3"
26851 @subheading The @code{-thread-select} Command
26852 @findex -thread-select
26854 @subsubheading Synopsis
26857 -thread-select @var{threadnum}
26860 Make @var{threadnum} the current thread. It prints the number of the new
26861 current thread, and the topmost frame for that thread.
26863 This command is deprecated in favor of explicitly using the
26864 @samp{--thread} option to each command.
26866 @subsubheading @value{GDBN} Command
26868 The corresponding @value{GDBN} command is @samp{thread}.
26870 @subsubheading Example
26877 *stopped,reason="end-stepping-range",thread-id="2",line="187",
26878 file="../../../devo/gdb/testsuite/gdb.threads/linux-dp.c"
26882 thread-ids=@{thread-id="3",thread-id="2",thread-id="1"@},
26883 number-of-threads="3"
26886 ^done,new-thread-id="3",
26887 frame=@{level="0",func="vprintf",
26888 args=[@{name="format",value="0x8048e9c \"%*s%c %d %c\\n\""@},
26889 @{name="arg",value="0x2"@}],file="vprintf.c",line="31"@}
26893 @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
26894 @node GDB/MI Ada Tasking Commands
26895 @section @sc{gdb/mi} Ada Tasking Commands
26897 @subheading The @code{-ada-task-info} Command
26898 @findex -ada-task-info
26900 @subsubheading Synopsis
26903 -ada-task-info [ @var{task-id} ]
26906 Reports information about either a specific Ada task, if the
26907 @var{task-id} parameter is present, or about all Ada tasks.
26909 @subsubheading @value{GDBN} Command
26911 The @samp{info tasks} command prints the same information
26912 about all Ada tasks (@pxref{Ada Tasks}).
26914 @subsubheading Result
26916 The result is a table of Ada tasks. The following columns are
26917 defined for each Ada task:
26921 This field exists only for the current thread. It has the value @samp{*}.
26924 The identifier that @value{GDBN} uses to refer to the Ada task.
26927 The identifier that the target uses to refer to the Ada task.
26930 The identifier of the thread corresponding to the Ada task.
26932 This field should always exist, as Ada tasks are always implemented
26933 on top of a thread. But if @value{GDBN} cannot find this corresponding
26934 thread for any reason, the field is omitted.
26937 This field exists only when the task was created by another task.
26938 In this case, it provides the ID of the parent task.
26941 The base priority of the task.
26944 The current state of the task. For a detailed description of the
26945 possible states, see @ref{Ada Tasks}.
26948 The name of the task.
26952 @subsubheading Example
26956 ^done,tasks=@{nr_rows="3",nr_cols="8",
26957 hdr=[@{width="1",alignment="-1",col_name="current",colhdr=""@},
26958 @{width="3",alignment="1",col_name="id",colhdr="ID"@},
26959 @{width="9",alignment="1",col_name="task-id",colhdr="TID"@},
26960 @{width="4",alignment="1",col_name="thread-id",colhdr=""@},
26961 @{width="4",alignment="1",col_name="parent-id",colhdr="P-ID"@},
26962 @{width="3",alignment="1",col_name="priority",colhdr="Pri"@},
26963 @{width="22",alignment="-1",col_name="state",colhdr="State"@},
26964 @{width="1",alignment="2",col_name="name",colhdr="Name"@}],
26965 body=[@{current="*",id="1",task-id=" 644010",thread-id="1",priority="48",
26966 state="Child Termination Wait",name="main_task"@}]@}
26970 @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
26971 @node GDB/MI Program Execution
26972 @section @sc{gdb/mi} Program Execution
26974 These are the asynchronous commands which generate the out-of-band
26975 record @samp{*stopped}. Currently @value{GDBN} only really executes
26976 asynchronously with remote targets and this interaction is mimicked in
26979 @subheading The @code{-exec-continue} Command
26980 @findex -exec-continue
26982 @subsubheading Synopsis
26985 -exec-continue [--reverse] [--all|--thread-group N]
26988 Resumes the execution of the inferior program, which will continue
26989 to execute until it reaches a debugger stop event. If the
26990 @samp{--reverse} option is specified, execution resumes in reverse until
26991 it reaches a stop event. Stop events may include
26994 breakpoints or watchpoints
26996 signals or exceptions
26998 the end of the process (or its beginning under @samp{--reverse})
27000 the end or beginning of a replay log if one is being used.
27002 In all-stop mode (@pxref{All-Stop
27003 Mode}), may resume only one thread, or all threads, depending on the
27004 value of the @samp{scheduler-locking} variable. If @samp{--all} is
27005 specified, all threads (in all inferiors) will be resumed. The @samp{--all} option is
27006 ignored in all-stop mode. If the @samp{--thread-group} options is
27007 specified, then all threads in that thread group are resumed.
27009 @subsubheading @value{GDBN} Command
27011 The corresponding @value{GDBN} corresponding is @samp{continue}.
27013 @subsubheading Example
27020 *stopped,reason="breakpoint-hit",disp="keep",bkptno="2",frame=@{
27021 func="foo",args=[],file="hello.c",fullname="/home/foo/bar/hello.c",
27027 @subheading The @code{-exec-finish} Command
27028 @findex -exec-finish
27030 @subsubheading Synopsis
27033 -exec-finish [--reverse]
27036 Resumes the execution of the inferior program until the current
27037 function is exited. Displays the results returned by the function.
27038 If the @samp{--reverse} option is specified, resumes the reverse
27039 execution of the inferior program until the point where current
27040 function was called.
27042 @subsubheading @value{GDBN} Command
27044 The corresponding @value{GDBN} command is @samp{finish}.
27046 @subsubheading Example
27048 Function returning @code{void}.
27055 *stopped,reason="function-finished",frame=@{func="main",args=[],
27056 file="hello.c",fullname="/home/foo/bar/hello.c",line="7"@}
27060 Function returning other than @code{void}. The name of the internal
27061 @value{GDBN} variable storing the result is printed, together with the
27068 *stopped,reason="function-finished",frame=@{addr="0x000107b0",func="foo",
27069 args=[@{name="a",value="1"],@{name="b",value="9"@}@},
27070 file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@},
27071 gdb-result-var="$1",return-value="0"
27076 @subheading The @code{-exec-interrupt} Command
27077 @findex -exec-interrupt
27079 @subsubheading Synopsis
27082 -exec-interrupt [--all|--thread-group N]
27085 Interrupts the background execution of the target. Note how the token
27086 associated with the stop message is the one for the execution command
27087 that has been interrupted. The token for the interrupt itself only
27088 appears in the @samp{^done} output. If the user is trying to
27089 interrupt a non-running program, an error message will be printed.
27091 Note that when asynchronous execution is enabled, this command is
27092 asynchronous just like other execution commands. That is, first the
27093 @samp{^done} response will be printed, and the target stop will be
27094 reported after that using the @samp{*stopped} notification.
27096 In non-stop mode, only the context thread is interrupted by default.
27097 All threads (in all inferiors) will be interrupted if the
27098 @samp{--all} option is specified. If the @samp{--thread-group}
27099 option is specified, all threads in that group will be interrupted.
27101 @subsubheading @value{GDBN} Command
27103 The corresponding @value{GDBN} command is @samp{interrupt}.
27105 @subsubheading Example
27116 111*stopped,signal-name="SIGINT",signal-meaning="Interrupt",
27117 frame=@{addr="0x00010140",func="foo",args=[],file="try.c",
27118 fullname="/home/foo/bar/try.c",line="13"@}
27123 ^error,msg="mi_cmd_exec_interrupt: Inferior not executing."
27127 @subheading The @code{-exec-jump} Command
27130 @subsubheading Synopsis
27133 -exec-jump @var{location}
27136 Resumes execution of the inferior program at the location specified by
27137 parameter. @xref{Specify Location}, for a description of the
27138 different forms of @var{location}.
27140 @subsubheading @value{GDBN} Command
27142 The corresponding @value{GDBN} command is @samp{jump}.
27144 @subsubheading Example
27147 -exec-jump foo.c:10
27148 *running,thread-id="all"
27153 @subheading The @code{-exec-next} Command
27156 @subsubheading Synopsis
27159 -exec-next [--reverse]
27162 Resumes execution of the inferior program, stopping when the beginning
27163 of the next source line is reached.
27165 If the @samp{--reverse} option is specified, resumes reverse execution
27166 of the inferior program, stopping at the beginning of the previous
27167 source line. If you issue this command on the first line of a
27168 function, it will take you back to the caller of that function, to the
27169 source line where the function was called.
27172 @subsubheading @value{GDBN} Command
27174 The corresponding @value{GDBN} command is @samp{next}.
27176 @subsubheading Example
27182 *stopped,reason="end-stepping-range",line="8",file="hello.c"
27187 @subheading The @code{-exec-next-instruction} Command
27188 @findex -exec-next-instruction
27190 @subsubheading Synopsis
27193 -exec-next-instruction [--reverse]
27196 Executes one machine instruction. If the instruction is a function
27197 call, continues until the function returns. If the program stops at an
27198 instruction in the middle of a source line, the address will be
27201 If the @samp{--reverse} option is specified, resumes reverse execution
27202 of the inferior program, stopping at the previous instruction. If the
27203 previously executed instruction was a return from another function,
27204 it will continue to execute in reverse until the call to that function
27205 (from the current stack frame) is reached.
27207 @subsubheading @value{GDBN} Command
27209 The corresponding @value{GDBN} command is @samp{nexti}.
27211 @subsubheading Example
27215 -exec-next-instruction
27219 *stopped,reason="end-stepping-range",
27220 addr="0x000100d4",line="5",file="hello.c"
27225 @subheading The @code{-exec-return} Command
27226 @findex -exec-return
27228 @subsubheading Synopsis
27234 Makes current function return immediately. Doesn't execute the inferior.
27235 Displays the new current frame.
27237 @subsubheading @value{GDBN} Command
27239 The corresponding @value{GDBN} command is @samp{return}.
27241 @subsubheading Example
27245 200-break-insert callee4
27246 200^done,bkpt=@{number="1",addr="0x00010734",
27247 file="../../../devo/gdb/testsuite/gdb.mi/basics.c",line="8"@}
27252 000*stopped,reason="breakpoint-hit",disp="keep",bkptno="1",
27253 frame=@{func="callee4",args=[],
27254 file="../../../devo/gdb/testsuite/gdb.mi/basics.c",
27255 fullname="/home/foo/bar/devo/gdb/testsuite/gdb.mi/basics.c",line="8"@}
27261 111^done,frame=@{level="0",func="callee3",
27262 args=[@{name="strarg",
27263 value="0x11940 \"A string argument.\""@}],
27264 file="../../../devo/gdb/testsuite/gdb.mi/basics.c",
27265 fullname="/home/foo/bar/devo/gdb/testsuite/gdb.mi/basics.c",line="18"@}
27270 @subheading The @code{-exec-run} Command
27273 @subsubheading Synopsis
27276 -exec-run [ --all | --thread-group N ] [ --start ]
27279 Starts execution of the inferior from the beginning. The inferior
27280 executes until either a breakpoint is encountered or the program
27281 exits. In the latter case the output will include an exit code, if
27282 the program has exited exceptionally.
27284 When neither the @samp{--all} nor the @samp{--thread-group} option
27285 is specified, the current inferior is started. If the
27286 @samp{--thread-group} option is specified, it should refer to a thread
27287 group of type @samp{process}, and that thread group will be started.
27288 If the @samp{--all} option is specified, then all inferiors will be started.
27290 Using the @samp{--start} option instructs the debugger to stop
27291 the execution at the start of the inferior's main subprogram,
27292 following the same behavior as the @code{start} command
27293 (@pxref{Starting}).
27295 @subsubheading @value{GDBN} Command
27297 The corresponding @value{GDBN} command is @samp{run}.
27299 @subsubheading Examples
27304 ^done,bkpt=@{number="1",addr="0x0001072c",file="recursive2.c",line="4"@}
27309 *stopped,reason="breakpoint-hit",disp="keep",bkptno="1",
27310 frame=@{func="main",args=[],file="recursive2.c",
27311 fullname="/home/foo/bar/recursive2.c",line="4"@}
27316 Program exited normally:
27324 *stopped,reason="exited-normally"
27329 Program exited exceptionally:
27337 *stopped,reason="exited",exit-code="01"
27341 Another way the program can terminate is if it receives a signal such as
27342 @code{SIGINT}. In this case, @sc{gdb/mi} displays this:
27346 *stopped,reason="exited-signalled",signal-name="SIGINT",
27347 signal-meaning="Interrupt"
27351 @c @subheading -exec-signal
27354 @subheading The @code{-exec-step} Command
27357 @subsubheading Synopsis
27360 -exec-step [--reverse]
27363 Resumes execution of the inferior program, stopping when the beginning
27364 of the next source line is reached, if the next source line is not a
27365 function call. If it is, stop at the first instruction of the called
27366 function. If the @samp{--reverse} option is specified, resumes reverse
27367 execution of the inferior program, stopping at the beginning of the
27368 previously executed source line.
27370 @subsubheading @value{GDBN} Command
27372 The corresponding @value{GDBN} command is @samp{step}.
27374 @subsubheading Example
27376 Stepping into a function:
27382 *stopped,reason="end-stepping-range",
27383 frame=@{func="foo",args=[@{name="a",value="10"@},
27384 @{name="b",value="0"@}],file="recursive2.c",
27385 fullname="/home/foo/bar/recursive2.c",line="11"@}
27395 *stopped,reason="end-stepping-range",line="14",file="recursive2.c"
27400 @subheading The @code{-exec-step-instruction} Command
27401 @findex -exec-step-instruction
27403 @subsubheading Synopsis
27406 -exec-step-instruction [--reverse]
27409 Resumes the inferior which executes one machine instruction. If the
27410 @samp{--reverse} option is specified, resumes reverse execution of the
27411 inferior program, stopping at the previously executed instruction.
27412 The output, once @value{GDBN} has stopped, will vary depending on
27413 whether we have stopped in the middle of a source line or not. In the
27414 former case, the address at which the program stopped will be printed
27417 @subsubheading @value{GDBN} Command
27419 The corresponding @value{GDBN} command is @samp{stepi}.
27421 @subsubheading Example
27425 -exec-step-instruction
27429 *stopped,reason="end-stepping-range",
27430 frame=@{func="foo",args=[],file="try.c",
27431 fullname="/home/foo/bar/try.c",line="10"@}
27433 -exec-step-instruction
27437 *stopped,reason="end-stepping-range",
27438 frame=@{addr="0x000100f4",func="foo",args=[],file="try.c",
27439 fullname="/home/foo/bar/try.c",line="10"@}
27444 @subheading The @code{-exec-until} Command
27445 @findex -exec-until
27447 @subsubheading Synopsis
27450 -exec-until [ @var{location} ]
27453 Executes the inferior until the @var{location} specified in the
27454 argument is reached. If there is no argument, the inferior executes
27455 until a source line greater than the current one is reached. The
27456 reason for stopping in this case will be @samp{location-reached}.
27458 @subsubheading @value{GDBN} Command
27460 The corresponding @value{GDBN} command is @samp{until}.
27462 @subsubheading Example
27466 -exec-until recursive2.c:6
27470 *stopped,reason="location-reached",frame=@{func="main",args=[],
27471 file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="6"@}
27476 @subheading -file-clear
27477 Is this going away????
27480 @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
27481 @node GDB/MI Stack Manipulation
27482 @section @sc{gdb/mi} Stack Manipulation Commands
27484 @subheading The @code{-enable-frame-filters} Command
27485 @findex -enable-frame-filters
27488 -enable-frame-filters
27491 @value{GDBN} allows Python-based frame filters to affect the output of
27492 the MI commands relating to stack traces. As there is no way to
27493 implement this in a fully backward-compatible way, a front end must
27494 request that this functionality be enabled.
27496 Once enabled, this feature cannot be disabled.
27498 Note that if Python support has not been compiled into @value{GDBN},
27499 this command will still succeed (and do nothing).
27501 @subheading The @code{-stack-info-frame} Command
27502 @findex -stack-info-frame
27504 @subsubheading Synopsis
27510 Get info on the selected frame.
27512 @subsubheading @value{GDBN} Command
27514 The corresponding @value{GDBN} command is @samp{info frame} or @samp{frame}
27515 (without arguments).
27517 @subsubheading Example
27522 ^done,frame=@{level="1",addr="0x0001076c",func="callee3",
27523 file="../../../devo/gdb/testsuite/gdb.mi/basics.c",
27524 fullname="/home/foo/bar/devo/gdb/testsuite/gdb.mi/basics.c",line="17"@}
27528 @subheading The @code{-stack-info-depth} Command
27529 @findex -stack-info-depth
27531 @subsubheading Synopsis
27534 -stack-info-depth [ @var{max-depth} ]
27537 Return the depth of the stack. If the integer argument @var{max-depth}
27538 is specified, do not count beyond @var{max-depth} frames.
27540 @subsubheading @value{GDBN} Command
27542 There's no equivalent @value{GDBN} command.
27544 @subsubheading Example
27546 For a stack with frame levels 0 through 11:
27553 -stack-info-depth 4
27556 -stack-info-depth 12
27559 -stack-info-depth 11
27562 -stack-info-depth 13
27567 @anchor{-stack-list-arguments}
27568 @subheading The @code{-stack-list-arguments} Command
27569 @findex -stack-list-arguments
27571 @subsubheading Synopsis
27574 -stack-list-arguments [ --no-frame-filters ] [ --skip-unavailable ] @var{print-values}
27575 [ @var{low-frame} @var{high-frame} ]
27578 Display a list of the arguments for the frames between @var{low-frame}
27579 and @var{high-frame} (inclusive). If @var{low-frame} and
27580 @var{high-frame} are not provided, list the arguments for the whole
27581 call stack. If the two arguments are equal, show the single frame
27582 at the corresponding level. It is an error if @var{low-frame} is
27583 larger than the actual number of frames. On the other hand,
27584 @var{high-frame} may be larger than the actual number of frames, in
27585 which case only existing frames will be returned.
27587 If @var{print-values} is 0 or @code{--no-values}, print only the names of
27588 the variables; if it is 1 or @code{--all-values}, print also their
27589 values; and if it is 2 or @code{--simple-values}, print the name,
27590 type and value for simple data types, and the name and type for arrays,
27591 structures and unions. If the option @code{--no-frame-filters} is
27592 supplied, then Python frame filters will not be executed.
27594 If the @code{--skip-unavailable} option is specified, arguments that
27595 are not available are not listed. Partially available arguments
27596 are still displayed, however.
27598 Use of this command to obtain arguments in a single frame is
27599 deprecated in favor of the @samp{-stack-list-variables} command.
27601 @subsubheading @value{GDBN} Command
27603 @value{GDBN} does not have an equivalent command. @code{gdbtk} has a
27604 @samp{gdb_get_args} command which partially overlaps with the
27605 functionality of @samp{-stack-list-arguments}.
27607 @subsubheading Example
27614 frame=@{level="0",addr="0x00010734",func="callee4",
27615 file="../../../devo/gdb/testsuite/gdb.mi/basics.c",
27616 fullname="/home/foo/bar/devo/gdb/testsuite/gdb.mi/basics.c",line="8"@},
27617 frame=@{level="1",addr="0x0001076c",func="callee3",
27618 file="../../../devo/gdb/testsuite/gdb.mi/basics.c",
27619 fullname="/home/foo/bar/devo/gdb/testsuite/gdb.mi/basics.c",line="17"@},
27620 frame=@{level="2",addr="0x0001078c",func="callee2",
27621 file="../../../devo/gdb/testsuite/gdb.mi/basics.c",
27622 fullname="/home/foo/bar/devo/gdb/testsuite/gdb.mi/basics.c",line="22"@},
27623 frame=@{level="3",addr="0x000107b4",func="callee1",
27624 file="../../../devo/gdb/testsuite/gdb.mi/basics.c",
27625 fullname="/home/foo/bar/devo/gdb/testsuite/gdb.mi/basics.c",line="27"@},
27626 frame=@{level="4",addr="0x000107e0",func="main",
27627 file="../../../devo/gdb/testsuite/gdb.mi/basics.c",
27628 fullname="/home/foo/bar/devo/gdb/testsuite/gdb.mi/basics.c",line="32"@}]
27630 -stack-list-arguments 0
27633 frame=@{level="0",args=[]@},
27634 frame=@{level="1",args=[name="strarg"]@},
27635 frame=@{level="2",args=[name="intarg",name="strarg"]@},
27636 frame=@{level="3",args=[name="intarg",name="strarg",name="fltarg"]@},
27637 frame=@{level="4",args=[]@}]
27639 -stack-list-arguments 1
27642 frame=@{level="0",args=[]@},
27644 args=[@{name="strarg",value="0x11940 \"A string argument.\""@}]@},
27645 frame=@{level="2",args=[
27646 @{name="intarg",value="2"@},
27647 @{name="strarg",value="0x11940 \"A string argument.\""@}]@},
27648 @{frame=@{level="3",args=[
27649 @{name="intarg",value="2"@},
27650 @{name="strarg",value="0x11940 \"A string argument.\""@},
27651 @{name="fltarg",value="3.5"@}]@},
27652 frame=@{level="4",args=[]@}]
27654 -stack-list-arguments 0 2 2
27655 ^done,stack-args=[frame=@{level="2",args=[name="intarg",name="strarg"]@}]
27657 -stack-list-arguments 1 2 2
27658 ^done,stack-args=[frame=@{level="2",
27659 args=[@{name="intarg",value="2"@},
27660 @{name="strarg",value="0x11940 \"A string argument.\""@}]@}]
27664 @c @subheading -stack-list-exception-handlers
27667 @anchor{-stack-list-frames}
27668 @subheading The @code{-stack-list-frames} Command
27669 @findex -stack-list-frames
27671 @subsubheading Synopsis
27674 -stack-list-frames [ --no-frame-filters @var{low-frame} @var{high-frame} ]
27677 List the frames currently on the stack. For each frame it displays the
27682 The frame number, 0 being the topmost frame, i.e., the innermost function.
27684 The @code{$pc} value for that frame.
27688 File name of the source file where the function lives.
27689 @item @var{fullname}
27690 The full file name of the source file where the function lives.
27692 Line number corresponding to the @code{$pc}.
27694 The shared library where this function is defined. This is only given
27695 if the frame's function is not known.
27698 If invoked without arguments, this command prints a backtrace for the
27699 whole stack. If given two integer arguments, it shows the frames whose
27700 levels are between the two arguments (inclusive). If the two arguments
27701 are equal, it shows the single frame at the corresponding level. It is
27702 an error if @var{low-frame} is larger than the actual number of
27703 frames. On the other hand, @var{high-frame} may be larger than the
27704 actual number of frames, in which case only existing frames will be
27705 returned. If the option @code{--no-frame-filters} is supplied, then
27706 Python frame filters will not be executed.
27708 @subsubheading @value{GDBN} Command
27710 The corresponding @value{GDBN} commands are @samp{backtrace} and @samp{where}.
27712 @subsubheading Example
27714 Full stack backtrace:
27720 [frame=@{level="0",addr="0x0001076c",func="foo",
27721 file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="11"@},
27722 frame=@{level="1",addr="0x000107a4",func="foo",
27723 file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@},
27724 frame=@{level="2",addr="0x000107a4",func="foo",
27725 file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@},
27726 frame=@{level="3",addr="0x000107a4",func="foo",
27727 file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@},
27728 frame=@{level="4",addr="0x000107a4",func="foo",
27729 file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@},
27730 frame=@{level="5",addr="0x000107a4",func="foo",
27731 file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@},
27732 frame=@{level="6",addr="0x000107a4",func="foo",
27733 file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@},
27734 frame=@{level="7",addr="0x000107a4",func="foo",
27735 file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@},
27736 frame=@{level="8",addr="0x000107a4",func="foo",
27737 file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@},
27738 frame=@{level="9",addr="0x000107a4",func="foo",
27739 file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@},
27740 frame=@{level="10",addr="0x000107a4",func="foo",
27741 file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@},
27742 frame=@{level="11",addr="0x00010738",func="main",
27743 file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="4"@}]
27747 Show frames between @var{low_frame} and @var{high_frame}:
27751 -stack-list-frames 3 5
27753 [frame=@{level="3",addr="0x000107a4",func="foo",
27754 file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@},
27755 frame=@{level="4",addr="0x000107a4",func="foo",
27756 file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@},
27757 frame=@{level="5",addr="0x000107a4",func="foo",
27758 file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@}]
27762 Show a single frame:
27766 -stack-list-frames 3 3
27768 [frame=@{level="3",addr="0x000107a4",func="foo",
27769 file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@}]
27774 @subheading The @code{-stack-list-locals} Command
27775 @findex -stack-list-locals
27776 @anchor{-stack-list-locals}
27778 @subsubheading Synopsis
27781 -stack-list-locals [ --no-frame-filters ] [ --skip-unavailable ] @var{print-values}
27784 Display the local variable names for the selected frame. If
27785 @var{print-values} is 0 or @code{--no-values}, print only the names of
27786 the variables; if it is 1 or @code{--all-values}, print also their
27787 values; and if it is 2 or @code{--simple-values}, print the name,
27788 type and value for simple data types, and the name and type for arrays,
27789 structures and unions. In this last case, a frontend can immediately
27790 display the value of simple data types and create variable objects for
27791 other data types when the user wishes to explore their values in
27792 more detail. If the option @code{--no-frame-filters} is supplied, then
27793 Python frame filters will not be executed.
27795 If the @code{--skip-unavailable} option is specified, local variables
27796 that are not available are not listed. Partially available local
27797 variables are still displayed, however.
27799 This command is deprecated in favor of the
27800 @samp{-stack-list-variables} command.
27802 @subsubheading @value{GDBN} Command
27804 @samp{info locals} in @value{GDBN}, @samp{gdb_get_locals} in @code{gdbtk}.
27806 @subsubheading Example
27810 -stack-list-locals 0
27811 ^done,locals=[name="A",name="B",name="C"]
27813 -stack-list-locals --all-values
27814 ^done,locals=[@{name="A",value="1"@},@{name="B",value="2"@},
27815 @{name="C",value="@{1, 2, 3@}"@}]
27816 -stack-list-locals --simple-values
27817 ^done,locals=[@{name="A",type="int",value="1"@},
27818 @{name="B",type="int",value="2"@},@{name="C",type="int [3]"@}]
27822 @anchor{-stack-list-variables}
27823 @subheading The @code{-stack-list-variables} Command
27824 @findex -stack-list-variables
27826 @subsubheading Synopsis
27829 -stack-list-variables [ --no-frame-filters ] [ --skip-unavailable ] @var{print-values}
27832 Display the names of local variables and function arguments for the selected frame. If
27833 @var{print-values} is 0 or @code{--no-values}, print only the names of
27834 the variables; if it is 1 or @code{--all-values}, print also their
27835 values; and if it is 2 or @code{--simple-values}, print the name,
27836 type and value for simple data types, and the name and type for arrays,
27837 structures and unions. If the option @code{--no-frame-filters} is
27838 supplied, then Python frame filters will not be executed.
27840 If the @code{--skip-unavailable} option is specified, local variables
27841 and arguments that are not available are not listed. Partially
27842 available arguments and local variables are still displayed, however.
27844 @subsubheading Example
27848 -stack-list-variables --thread 1 --frame 0 --all-values
27849 ^done,variables=[@{name="x",value="11"@},@{name="s",value="@{a = 1, b = 2@}"@}]
27854 @subheading The @code{-stack-select-frame} Command
27855 @findex -stack-select-frame
27857 @subsubheading Synopsis
27860 -stack-select-frame @var{framenum}
27863 Change the selected frame. Select a different frame @var{framenum} on
27866 This command in deprecated in favor of passing the @samp{--frame}
27867 option to every command.
27869 @subsubheading @value{GDBN} Command
27871 The corresponding @value{GDBN} commands are @samp{frame}, @samp{up},
27872 @samp{down}, @samp{select-frame}, @samp{up-silent}, and @samp{down-silent}.
27874 @subsubheading Example
27878 -stack-select-frame 2
27883 @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
27884 @node GDB/MI Variable Objects
27885 @section @sc{gdb/mi} Variable Objects
27889 @subheading Motivation for Variable Objects in @sc{gdb/mi}
27891 For the implementation of a variable debugger window (locals, watched
27892 expressions, etc.), we are proposing the adaptation of the existing code
27893 used by @code{Insight}.
27895 The two main reasons for that are:
27899 It has been proven in practice (it is already on its second generation).
27902 It will shorten development time (needless to say how important it is
27906 The original interface was designed to be used by Tcl code, so it was
27907 slightly changed so it could be used through @sc{gdb/mi}. This section
27908 describes the @sc{gdb/mi} operations that will be available and gives some
27909 hints about their use.
27911 @emph{Note}: In addition to the set of operations described here, we
27912 expect the @sc{gui} implementation of a variable window to require, at
27913 least, the following operations:
27916 @item @code{-gdb-show} @code{output-radix}
27917 @item @code{-stack-list-arguments}
27918 @item @code{-stack-list-locals}
27919 @item @code{-stack-select-frame}
27924 @subheading Introduction to Variable Objects
27926 @cindex variable objects in @sc{gdb/mi}
27928 Variable objects are "object-oriented" MI interface for examining and
27929 changing values of expressions. Unlike some other MI interfaces that
27930 work with expressions, variable objects are specifically designed for
27931 simple and efficient presentation in the frontend. A variable object
27932 is identified by string name. When a variable object is created, the
27933 frontend specifies the expression for that variable object. The
27934 expression can be a simple variable, or it can be an arbitrary complex
27935 expression, and can even involve CPU registers. After creating a
27936 variable object, the frontend can invoke other variable object
27937 operations---for example to obtain or change the value of a variable
27938 object, or to change display format.
27940 Variable objects have hierarchical tree structure. Any variable object
27941 that corresponds to a composite type, such as structure in C, has
27942 a number of child variable objects, for example corresponding to each
27943 element of a structure. A child variable object can itself have
27944 children, recursively. Recursion ends when we reach
27945 leaf variable objects, which always have built-in types. Child variable
27946 objects are created only by explicit request, so if a frontend
27947 is not interested in the children of a particular variable object, no
27948 child will be created.
27950 For a leaf variable object it is possible to obtain its value as a
27951 string, or set the value from a string. String value can be also
27952 obtained for a non-leaf variable object, but it's generally a string
27953 that only indicates the type of the object, and does not list its
27954 contents. Assignment to a non-leaf variable object is not allowed.
27956 A frontend does not need to read the values of all variable objects each time
27957 the program stops. Instead, MI provides an update command that lists all
27958 variable objects whose values has changed since the last update
27959 operation. This considerably reduces the amount of data that must
27960 be transferred to the frontend. As noted above, children variable
27961 objects are created on demand, and only leaf variable objects have a
27962 real value. As result, gdb will read target memory only for leaf
27963 variables that frontend has created.
27965 The automatic update is not always desirable. For example, a frontend
27966 might want to keep a value of some expression for future reference,
27967 and never update it. For another example, fetching memory is
27968 relatively slow for embedded targets, so a frontend might want
27969 to disable automatic update for the variables that are either not
27970 visible on the screen, or ``closed''. This is possible using so
27971 called ``frozen variable objects''. Such variable objects are never
27972 implicitly updated.
27974 Variable objects can be either @dfn{fixed} or @dfn{floating}. For the
27975 fixed variable object, the expression is parsed when the variable
27976 object is created, including associating identifiers to specific
27977 variables. The meaning of expression never changes. For a floating
27978 variable object the values of variables whose names appear in the
27979 expressions are re-evaluated every time in the context of the current
27980 frame. Consider this example:
27985 struct work_state state;
27992 If a fixed variable object for the @code{state} variable is created in
27993 this function, and we enter the recursive call, the variable
27994 object will report the value of @code{state} in the top-level
27995 @code{do_work} invocation. On the other hand, a floating variable
27996 object will report the value of @code{state} in the current frame.
27998 If an expression specified when creating a fixed variable object
27999 refers to a local variable, the variable object becomes bound to the
28000 thread and frame in which the variable object is created. When such
28001 variable object is updated, @value{GDBN} makes sure that the
28002 thread/frame combination the variable object is bound to still exists,
28003 and re-evaluates the variable object in context of that thread/frame.
28005 The following is the complete set of @sc{gdb/mi} operations defined to
28006 access this functionality:
28008 @multitable @columnfractions .4 .6
28009 @item @strong{Operation}
28010 @tab @strong{Description}
28012 @item @code{-enable-pretty-printing}
28013 @tab enable Python-based pretty-printing
28014 @item @code{-var-create}
28015 @tab create a variable object
28016 @item @code{-var-delete}
28017 @tab delete the variable object and/or its children
28018 @item @code{-var-set-format}
28019 @tab set the display format of this variable
28020 @item @code{-var-show-format}
28021 @tab show the display format of this variable
28022 @item @code{-var-info-num-children}
28023 @tab tells how many children this object has
28024 @item @code{-var-list-children}
28025 @tab return a list of the object's children
28026 @item @code{-var-info-type}
28027 @tab show the type of this variable object
28028 @item @code{-var-info-expression}
28029 @tab print parent-relative expression that this variable object represents
28030 @item @code{-var-info-path-expression}
28031 @tab print full expression that this variable object represents
28032 @item @code{-var-show-attributes}
28033 @tab is this variable editable? does it exist here?
28034 @item @code{-var-evaluate-expression}
28035 @tab get the value of this variable
28036 @item @code{-var-assign}
28037 @tab set the value of this variable
28038 @item @code{-var-update}
28039 @tab update the variable and its children
28040 @item @code{-var-set-frozen}
28041 @tab set frozeness attribute
28042 @item @code{-var-set-update-range}
28043 @tab set range of children to display on update
28046 In the next subsection we describe each operation in detail and suggest
28047 how it can be used.
28049 @subheading Description And Use of Operations on Variable Objects
28051 @subheading The @code{-enable-pretty-printing} Command
28052 @findex -enable-pretty-printing
28055 -enable-pretty-printing
28058 @value{GDBN} allows Python-based visualizers to affect the output of the
28059 MI variable object commands. However, because there was no way to
28060 implement this in a fully backward-compatible way, a front end must
28061 request that this functionality be enabled.
28063 Once enabled, this feature cannot be disabled.
28065 Note that if Python support has not been compiled into @value{GDBN},
28066 this command will still succeed (and do nothing).
28068 This feature is currently (as of @value{GDBN} 7.0) experimental, and
28069 may work differently in future versions of @value{GDBN}.
28071 @subheading The @code{-var-create} Command
28072 @findex -var-create
28074 @subsubheading Synopsis
28077 -var-create @{@var{name} | "-"@}
28078 @{@var{frame-addr} | "*" | "@@"@} @var{expression}
28081 This operation creates a variable object, which allows the monitoring of
28082 a variable, the result of an expression, a memory cell or a CPU
28085 The @var{name} parameter is the string by which the object can be
28086 referenced. It must be unique. If @samp{-} is specified, the varobj
28087 system will generate a string ``varNNNNNN'' automatically. It will be
28088 unique provided that one does not specify @var{name} of that format.
28089 The command fails if a duplicate name is found.
28091 The frame under which the expression should be evaluated can be
28092 specified by @var{frame-addr}. A @samp{*} indicates that the current
28093 frame should be used. A @samp{@@} indicates that a floating variable
28094 object must be created.
28096 @var{expression} is any expression valid on the current language set (must not
28097 begin with a @samp{*}), or one of the following:
28101 @samp{*@var{addr}}, where @var{addr} is the address of a memory cell
28104 @samp{*@var{addr}-@var{addr}} --- a memory address range (TBD)
28107 @samp{$@var{regname}} --- a CPU register name
28110 @cindex dynamic varobj
28111 A varobj's contents may be provided by a Python-based pretty-printer. In this
28112 case the varobj is known as a @dfn{dynamic varobj}. Dynamic varobjs
28113 have slightly different semantics in some cases. If the
28114 @code{-enable-pretty-printing} command is not sent, then @value{GDBN}
28115 will never create a dynamic varobj. This ensures backward
28116 compatibility for existing clients.
28118 @subsubheading Result
28120 This operation returns attributes of the newly-created varobj. These
28125 The name of the varobj.
28128 The number of children of the varobj. This number is not necessarily
28129 reliable for a dynamic varobj. Instead, you must examine the
28130 @samp{has_more} attribute.
28133 The varobj's scalar value. For a varobj whose type is some sort of
28134 aggregate (e.g., a @code{struct}), or for a dynamic varobj, this value
28135 will not be interesting.
28138 The varobj's type. This is a string representation of the type, as
28139 would be printed by the @value{GDBN} CLI. If @samp{print object}
28140 (@pxref{Print Settings, set print object}) is set to @code{on}, the
28141 @emph{actual} (derived) type of the object is shown rather than the
28142 @emph{declared} one.
28145 If a variable object is bound to a specific thread, then this is the
28146 thread's identifier.
28149 For a dynamic varobj, this indicates whether there appear to be any
28150 children available. For a non-dynamic varobj, this will be 0.
28153 This attribute will be present and have the value @samp{1} if the
28154 varobj is a dynamic varobj. If the varobj is not a dynamic varobj,
28155 then this attribute will not be present.
28158 A dynamic varobj can supply a display hint to the front end. The
28159 value comes directly from the Python pretty-printer object's
28160 @code{display_hint} method. @xref{Pretty Printing API}.
28163 Typical output will look like this:
28166 name="@var{name}",numchild="@var{N}",type="@var{type}",thread-id="@var{M}",
28167 has_more="@var{has_more}"
28171 @subheading The @code{-var-delete} Command
28172 @findex -var-delete
28174 @subsubheading Synopsis
28177 -var-delete [ -c ] @var{name}
28180 Deletes a previously created variable object and all of its children.
28181 With the @samp{-c} option, just deletes the children.
28183 Returns an error if the object @var{name} is not found.
28186 @subheading The @code{-var-set-format} Command
28187 @findex -var-set-format
28189 @subsubheading Synopsis
28192 -var-set-format @var{name} @var{format-spec}
28195 Sets the output format for the value of the object @var{name} to be
28198 @anchor{-var-set-format}
28199 The syntax for the @var{format-spec} is as follows:
28202 @var{format-spec} @expansion{}
28203 @{binary | decimal | hexadecimal | octal | natural@}
28206 The natural format is the default format choosen automatically
28207 based on the variable type (like decimal for an @code{int}, hex
28208 for pointers, etc.).
28210 For a variable with children, the format is set only on the
28211 variable itself, and the children are not affected.
28213 @subheading The @code{-var-show-format} Command
28214 @findex -var-show-format
28216 @subsubheading Synopsis
28219 -var-show-format @var{name}
28222 Returns the format used to display the value of the object @var{name}.
28225 @var{format} @expansion{}
28230 @subheading The @code{-var-info-num-children} Command
28231 @findex -var-info-num-children
28233 @subsubheading Synopsis
28236 -var-info-num-children @var{name}
28239 Returns the number of children of a variable object @var{name}:
28245 Note that this number is not completely reliable for a dynamic varobj.
28246 It will return the current number of children, but more children may
28250 @subheading The @code{-var-list-children} Command
28251 @findex -var-list-children
28253 @subsubheading Synopsis
28256 -var-list-children [@var{print-values}] @var{name} [@var{from} @var{to}]
28258 @anchor{-var-list-children}
28260 Return a list of the children of the specified variable object and
28261 create variable objects for them, if they do not already exist. With
28262 a single argument or if @var{print-values} has a value of 0 or
28263 @code{--no-values}, print only the names of the variables; if
28264 @var{print-values} is 1 or @code{--all-values}, also print their
28265 values; and if it is 2 or @code{--simple-values} print the name and
28266 value for simple data types and just the name for arrays, structures
28269 @var{from} and @var{to}, if specified, indicate the range of children
28270 to report. If @var{from} or @var{to} is less than zero, the range is
28271 reset and all children will be reported. Otherwise, children starting
28272 at @var{from} (zero-based) and up to and excluding @var{to} will be
28275 If a child range is requested, it will only affect the current call to
28276 @code{-var-list-children}, but not future calls to @code{-var-update}.
28277 For this, you must instead use @code{-var-set-update-range}. The
28278 intent of this approach is to enable a front end to implement any
28279 update approach it likes; for example, scrolling a view may cause the
28280 front end to request more children with @code{-var-list-children}, and
28281 then the front end could call @code{-var-set-update-range} with a
28282 different range to ensure that future updates are restricted to just
28285 For each child the following results are returned:
28290 Name of the variable object created for this child.
28293 The expression to be shown to the user by the front end to designate this child.
28294 For example this may be the name of a structure member.
28296 For a dynamic varobj, this value cannot be used to form an
28297 expression. There is no way to do this at all with a dynamic varobj.
28299 For C/C@t{++} structures there are several pseudo children returned to
28300 designate access qualifiers. For these pseudo children @var{exp} is
28301 @samp{public}, @samp{private}, or @samp{protected}. In this case the
28302 type and value are not present.
28304 A dynamic varobj will not report the access qualifying
28305 pseudo-children, regardless of the language. This information is not
28306 available at all with a dynamic varobj.
28309 Number of children this child has. For a dynamic varobj, this will be
28313 The type of the child. If @samp{print object}
28314 (@pxref{Print Settings, set print object}) is set to @code{on}, the
28315 @emph{actual} (derived) type of the object is shown rather than the
28316 @emph{declared} one.
28319 If values were requested, this is the value.
28322 If this variable object is associated with a thread, this is the thread id.
28323 Otherwise this result is not present.
28326 If the variable object is frozen, this variable will be present with a value of 1.
28329 A dynamic varobj can supply a display hint to the front end. The
28330 value comes directly from the Python pretty-printer object's
28331 @code{display_hint} method. @xref{Pretty Printing API}.
28334 This attribute will be present and have the value @samp{1} if the
28335 varobj is a dynamic varobj. If the varobj is not a dynamic varobj,
28336 then this attribute will not be present.
28340 The result may have its own attributes:
28344 A dynamic varobj can supply a display hint to the front end. The
28345 value comes directly from the Python pretty-printer object's
28346 @code{display_hint} method. @xref{Pretty Printing API}.
28349 This is an integer attribute which is nonzero if there are children
28350 remaining after the end of the selected range.
28353 @subsubheading Example
28357 -var-list-children n
28358 ^done,numchild=@var{n},children=[child=@{name=@var{name},exp=@var{exp},
28359 numchild=@var{n},type=@var{type}@},@r{(repeats N times)}]
28361 -var-list-children --all-values n
28362 ^done,numchild=@var{n},children=[child=@{name=@var{name},exp=@var{exp},
28363 numchild=@var{n},value=@var{value},type=@var{type}@},@r{(repeats N times)}]
28367 @subheading The @code{-var-info-type} Command
28368 @findex -var-info-type
28370 @subsubheading Synopsis
28373 -var-info-type @var{name}
28376 Returns the type of the specified variable @var{name}. The type is
28377 returned as a string in the same format as it is output by the
28381 type=@var{typename}
28385 @subheading The @code{-var-info-expression} Command
28386 @findex -var-info-expression
28388 @subsubheading Synopsis
28391 -var-info-expression @var{name}
28394 Returns a string that is suitable for presenting this
28395 variable object in user interface. The string is generally
28396 not valid expression in the current language, and cannot be evaluated.
28398 For example, if @code{a} is an array, and variable object
28399 @code{A} was created for @code{a}, then we'll get this output:
28402 (gdb) -var-info-expression A.1
28403 ^done,lang="C",exp="1"
28407 Here, the value of @code{lang} is the language name, which can be
28408 found in @ref{Supported Languages}.
28410 Note that the output of the @code{-var-list-children} command also
28411 includes those expressions, so the @code{-var-info-expression} command
28414 @subheading The @code{-var-info-path-expression} Command
28415 @findex -var-info-path-expression
28417 @subsubheading Synopsis
28420 -var-info-path-expression @var{name}
28423 Returns an expression that can be evaluated in the current
28424 context and will yield the same value that a variable object has.
28425 Compare this with the @code{-var-info-expression} command, which
28426 result can be used only for UI presentation. Typical use of
28427 the @code{-var-info-path-expression} command is creating a
28428 watchpoint from a variable object.
28430 This command is currently not valid for children of a dynamic varobj,
28431 and will give an error when invoked on one.
28433 For example, suppose @code{C} is a C@t{++} class, derived from class
28434 @code{Base}, and that the @code{Base} class has a member called
28435 @code{m_size}. Assume a variable @code{c} is has the type of
28436 @code{C} and a variable object @code{C} was created for variable
28437 @code{c}. Then, we'll get this output:
28439 (gdb) -var-info-path-expression C.Base.public.m_size
28440 ^done,path_expr=((Base)c).m_size)
28443 @subheading The @code{-var-show-attributes} Command
28444 @findex -var-show-attributes
28446 @subsubheading Synopsis
28449 -var-show-attributes @var{name}
28452 List attributes of the specified variable object @var{name}:
28455 status=@var{attr} [ ( ,@var{attr} )* ]
28459 where @var{attr} is @code{@{ @{ editable | noneditable @} | TBD @}}.
28461 @subheading The @code{-var-evaluate-expression} Command
28462 @findex -var-evaluate-expression
28464 @subsubheading Synopsis
28467 -var-evaluate-expression [-f @var{format-spec}] @var{name}
28470 Evaluates the expression that is represented by the specified variable
28471 object and returns its value as a string. The format of the string
28472 can be specified with the @samp{-f} option. The possible values of
28473 this option are the same as for @code{-var-set-format}
28474 (@pxref{-var-set-format}). If the @samp{-f} option is not specified,
28475 the current display format will be used. The current display format
28476 can be changed using the @code{-var-set-format} command.
28482 Note that one must invoke @code{-var-list-children} for a variable
28483 before the value of a child variable can be evaluated.
28485 @subheading The @code{-var-assign} Command
28486 @findex -var-assign
28488 @subsubheading Synopsis
28491 -var-assign @var{name} @var{expression}
28494 Assigns the value of @var{expression} to the variable object specified
28495 by @var{name}. The object must be @samp{editable}. If the variable's
28496 value is altered by the assign, the variable will show up in any
28497 subsequent @code{-var-update} list.
28499 @subsubheading Example
28507 ^done,changelist=[@{name="var1",in_scope="true",type_changed="false"@}]
28511 @subheading The @code{-var-update} Command
28512 @findex -var-update
28514 @subsubheading Synopsis
28517 -var-update [@var{print-values}] @{@var{name} | "*"@}
28520 Reevaluate the expressions corresponding to the variable object
28521 @var{name} and all its direct and indirect children, and return the
28522 list of variable objects whose values have changed; @var{name} must
28523 be a root variable object. Here, ``changed'' means that the result of
28524 @code{-var-evaluate-expression} before and after the
28525 @code{-var-update} is different. If @samp{*} is used as the variable
28526 object names, all existing variable objects are updated, except
28527 for frozen ones (@pxref{-var-set-frozen}). The option
28528 @var{print-values} determines whether both names and values, or just
28529 names are printed. The possible values of this option are the same
28530 as for @code{-var-list-children} (@pxref{-var-list-children}). It is
28531 recommended to use the @samp{--all-values} option, to reduce the
28532 number of MI commands needed on each program stop.
28534 With the @samp{*} parameter, if a variable object is bound to a
28535 currently running thread, it will not be updated, without any
28538 If @code{-var-set-update-range} was previously used on a varobj, then
28539 only the selected range of children will be reported.
28541 @code{-var-update} reports all the changed varobjs in a tuple named
28544 Each item in the change list is itself a tuple holding:
28548 The name of the varobj.
28551 If values were requested for this update, then this field will be
28552 present and will hold the value of the varobj.
28555 @anchor{-var-update}
28556 This field is a string which may take one of three values:
28560 The variable object's current value is valid.
28563 The variable object does not currently hold a valid value but it may
28564 hold one in the future if its associated expression comes back into
28568 The variable object no longer holds a valid value.
28569 This can occur when the executable file being debugged has changed,
28570 either through recompilation or by using the @value{GDBN} @code{file}
28571 command. The front end should normally choose to delete these variable
28575 In the future new values may be added to this list so the front should
28576 be prepared for this possibility. @xref{GDB/MI Development and Front Ends, ,@sc{GDB/MI} Development and Front Ends}.
28579 This is only present if the varobj is still valid. If the type
28580 changed, then this will be the string @samp{true}; otherwise it will
28583 When a varobj's type changes, its children are also likely to have
28584 become incorrect. Therefore, the varobj's children are automatically
28585 deleted when this attribute is @samp{true}. Also, the varobj's update
28586 range, when set using the @code{-var-set-update-range} command, is
28590 If the varobj's type changed, then this field will be present and will
28593 @item new_num_children
28594 For a dynamic varobj, if the number of children changed, or if the
28595 type changed, this will be the new number of children.
28597 The @samp{numchild} field in other varobj responses is generally not
28598 valid for a dynamic varobj -- it will show the number of children that
28599 @value{GDBN} knows about, but because dynamic varobjs lazily
28600 instantiate their children, this will not reflect the number of
28601 children which may be available.
28603 The @samp{new_num_children} attribute only reports changes to the
28604 number of children known by @value{GDBN}. This is the only way to
28605 detect whether an update has removed children (which necessarily can
28606 only happen at the end of the update range).
28609 The display hint, if any.
28612 This is an integer value, which will be 1 if there are more children
28613 available outside the varobj's update range.
28616 This attribute will be present and have the value @samp{1} if the
28617 varobj is a dynamic varobj. If the varobj is not a dynamic varobj,
28618 then this attribute will not be present.
28621 If new children were added to a dynamic varobj within the selected
28622 update range (as set by @code{-var-set-update-range}), then they will
28623 be listed in this attribute.
28626 @subsubheading Example
28633 -var-update --all-values var1
28634 ^done,changelist=[@{name="var1",value="3",in_scope="true",
28635 type_changed="false"@}]
28639 @subheading The @code{-var-set-frozen} Command
28640 @findex -var-set-frozen
28641 @anchor{-var-set-frozen}
28643 @subsubheading Synopsis
28646 -var-set-frozen @var{name} @var{flag}
28649 Set the frozenness flag on the variable object @var{name}. The
28650 @var{flag} parameter should be either @samp{1} to make the variable
28651 frozen or @samp{0} to make it unfrozen. If a variable object is
28652 frozen, then neither itself, nor any of its children, are
28653 implicitly updated by @code{-var-update} of
28654 a parent variable or by @code{-var-update *}. Only
28655 @code{-var-update} of the variable itself will update its value and
28656 values of its children. After a variable object is unfrozen, it is
28657 implicitly updated by all subsequent @code{-var-update} operations.
28658 Unfreezing a variable does not update it, only subsequent
28659 @code{-var-update} does.
28661 @subsubheading Example
28665 -var-set-frozen V 1
28670 @subheading The @code{-var-set-update-range} command
28671 @findex -var-set-update-range
28672 @anchor{-var-set-update-range}
28674 @subsubheading Synopsis
28677 -var-set-update-range @var{name} @var{from} @var{to}
28680 Set the range of children to be returned by future invocations of
28681 @code{-var-update}.
28683 @var{from} and @var{to} indicate the range of children to report. If
28684 @var{from} or @var{to} is less than zero, the range is reset and all
28685 children will be reported. Otherwise, children starting at @var{from}
28686 (zero-based) and up to and excluding @var{to} will be reported.
28688 @subsubheading Example
28692 -var-set-update-range V 1 2
28696 @subheading The @code{-var-set-visualizer} command
28697 @findex -var-set-visualizer
28698 @anchor{-var-set-visualizer}
28700 @subsubheading Synopsis
28703 -var-set-visualizer @var{name} @var{visualizer}
28706 Set a visualizer for the variable object @var{name}.
28708 @var{visualizer} is the visualizer to use. The special value
28709 @samp{None} means to disable any visualizer in use.
28711 If not @samp{None}, @var{visualizer} must be a Python expression.
28712 This expression must evaluate to a callable object which accepts a
28713 single argument. @value{GDBN} will call this object with the value of
28714 the varobj @var{name} as an argument (this is done so that the same
28715 Python pretty-printing code can be used for both the CLI and MI).
28716 When called, this object must return an object which conforms to the
28717 pretty-printing interface (@pxref{Pretty Printing API}).
28719 The pre-defined function @code{gdb.default_visualizer} may be used to
28720 select a visualizer by following the built-in process
28721 (@pxref{Selecting Pretty-Printers}). This is done automatically when
28722 a varobj is created, and so ordinarily is not needed.
28724 This feature is only available if Python support is enabled. The MI
28725 command @code{-list-features} (@pxref{GDB/MI Support Commands})
28726 can be used to check this.
28728 @subsubheading Example
28730 Resetting the visualizer:
28734 -var-set-visualizer V None
28738 Reselecting the default (type-based) visualizer:
28742 -var-set-visualizer V gdb.default_visualizer
28746 Suppose @code{SomeClass} is a visualizer class. A lambda expression
28747 can be used to instantiate this class for a varobj:
28751 -var-set-visualizer V "lambda val: SomeClass()"
28755 @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
28756 @node GDB/MI Data Manipulation
28757 @section @sc{gdb/mi} Data Manipulation
28759 @cindex data manipulation, in @sc{gdb/mi}
28760 @cindex @sc{gdb/mi}, data manipulation
28761 This section describes the @sc{gdb/mi} commands that manipulate data:
28762 examine memory and registers, evaluate expressions, etc.
28764 @c REMOVED FROM THE INTERFACE.
28765 @c @subheading -data-assign
28766 @c Change the value of a program variable. Plenty of side effects.
28767 @c @subsubheading GDB Command
28769 @c @subsubheading Example
28772 @subheading The @code{-data-disassemble} Command
28773 @findex -data-disassemble
28775 @subsubheading Synopsis
28779 [ -s @var{start-addr} -e @var{end-addr} ]
28780 | [ -f @var{filename} -l @var{linenum} [ -n @var{lines} ] ]
28788 @item @var{start-addr}
28789 is the beginning address (or @code{$pc})
28790 @item @var{end-addr}
28792 @item @var{filename}
28793 is the name of the file to disassemble
28794 @item @var{linenum}
28795 is the line number to disassemble around
28797 is the number of disassembly lines to be produced. If it is -1,
28798 the whole function will be disassembled, in case no @var{end-addr} is
28799 specified. If @var{end-addr} is specified as a non-zero value, and
28800 @var{lines} is lower than the number of disassembly lines between
28801 @var{start-addr} and @var{end-addr}, only @var{lines} lines are
28802 displayed; if @var{lines} is higher than the number of lines between
28803 @var{start-addr} and @var{end-addr}, only the lines up to @var{end-addr}
28806 is either 0 (meaning only disassembly), 1 (meaning mixed source and
28807 disassembly), 2 (meaning disassembly with raw opcodes), or 3 (meaning
28808 mixed source and disassembly with raw opcodes).
28811 @subsubheading Result
28813 The result of the @code{-data-disassemble} command will be a list named
28814 @samp{asm_insns}, the contents of this list depend on the @var{mode}
28815 used with the @code{-data-disassemble} command.
28817 For modes 0 and 2 the @samp{asm_insns} list contains tuples with the
28822 The address at which this instruction was disassembled.
28825 The name of the function this instruction is within.
28828 The decimal offset in bytes from the start of @samp{func-name}.
28831 The text disassembly for this @samp{address}.
28834 This field is only present for mode 2. This contains the raw opcode
28835 bytes for the @samp{inst} field.
28839 For modes 1 and 3 the @samp{asm_insns} list contains tuples named
28840 @samp{src_and_asm_line}, each of which has the following fields:
28844 The line number within @samp{file}.
28847 The file name from the compilation unit. This might be an absolute
28848 file name or a relative file name depending on the compile command
28852 Absolute file name of @samp{file}. It is converted to a canonical form
28853 using the source file search path
28854 (@pxref{Source Path, ,Specifying Source Directories})
28855 and after resolving all the symbolic links.
28857 If the source file is not found this field will contain the path as
28858 present in the debug information.
28860 @item line_asm_insn
28861 This is a list of tuples containing the disassembly for @samp{line} in
28862 @samp{file}. The fields of each tuple are the same as for
28863 @code{-data-disassemble} in @var{mode} 0 and 2, so @samp{address},
28864 @samp{func-name}, @samp{offset}, @samp{inst}, and optionally
28869 Note that whatever included in the @samp{inst} field, is not
28870 manipulated directly by @sc{gdb/mi}, i.e., it is not possible to
28873 @subsubheading @value{GDBN} Command
28875 The corresponding @value{GDBN} command is @samp{disassemble}.
28877 @subsubheading Example
28879 Disassemble from the current value of @code{$pc} to @code{$pc + 20}:
28883 -data-disassemble -s $pc -e "$pc + 20" -- 0
28886 @{address="0x000107c0",func-name="main",offset="4",
28887 inst="mov 2, %o0"@},
28888 @{address="0x000107c4",func-name="main",offset="8",
28889 inst="sethi %hi(0x11800), %o2"@},
28890 @{address="0x000107c8",func-name="main",offset="12",
28891 inst="or %o2, 0x140, %o1\t! 0x11940 <_lib_version+8>"@},
28892 @{address="0x000107cc",func-name="main",offset="16",
28893 inst="sethi %hi(0x11800), %o2"@},
28894 @{address="0x000107d0",func-name="main",offset="20",
28895 inst="or %o2, 0x168, %o4\t! 0x11968 <_lib_version+48>"@}]
28899 Disassemble the whole @code{main} function. Line 32 is part of
28903 -data-disassemble -f basics.c -l 32 -- 0
28905 @{address="0x000107bc",func-name="main",offset="0",
28906 inst="save %sp, -112, %sp"@},
28907 @{address="0x000107c0",func-name="main",offset="4",
28908 inst="mov 2, %o0"@},
28909 @{address="0x000107c4",func-name="main",offset="8",
28910 inst="sethi %hi(0x11800), %o2"@},
28912 @{address="0x0001081c",func-name="main",offset="96",inst="ret "@},
28913 @{address="0x00010820",func-name="main",offset="100",inst="restore "@}]
28917 Disassemble 3 instructions from the start of @code{main}:
28921 -data-disassemble -f basics.c -l 32 -n 3 -- 0
28923 @{address="0x000107bc",func-name="main",offset="0",
28924 inst="save %sp, -112, %sp"@},
28925 @{address="0x000107c0",func-name="main",offset="4",
28926 inst="mov 2, %o0"@},
28927 @{address="0x000107c4",func-name="main",offset="8",
28928 inst="sethi %hi(0x11800), %o2"@}]
28932 Disassemble 3 instructions from the start of @code{main} in mixed mode:
28936 -data-disassemble -f basics.c -l 32 -n 3 -- 1
28938 src_and_asm_line=@{line="31",
28939 file="../../../src/gdb/testsuite/gdb.mi/basics.c",
28940 fullname="/absolute/path/to/src/gdb/testsuite/gdb.mi/basics.c",
28941 line_asm_insn=[@{address="0x000107bc",
28942 func-name="main",offset="0",inst="save %sp, -112, %sp"@}]@},
28943 src_and_asm_line=@{line="32",
28944 file="../../../src/gdb/testsuite/gdb.mi/basics.c",
28945 fullname="/absolute/path/to/src/gdb/testsuite/gdb.mi/basics.c",
28946 line_asm_insn=[@{address="0x000107c0",
28947 func-name="main",offset="4",inst="mov 2, %o0"@},
28948 @{address="0x000107c4",func-name="main",offset="8",
28949 inst="sethi %hi(0x11800), %o2"@}]@}]
28954 @subheading The @code{-data-evaluate-expression} Command
28955 @findex -data-evaluate-expression
28957 @subsubheading Synopsis
28960 -data-evaluate-expression @var{expr}
28963 Evaluate @var{expr} as an expression. The expression could contain an
28964 inferior function call. The function call will execute synchronously.
28965 If the expression contains spaces, it must be enclosed in double quotes.
28967 @subsubheading @value{GDBN} Command
28969 The corresponding @value{GDBN} commands are @samp{print}, @samp{output}, and
28970 @samp{call}. In @code{gdbtk} only, there's a corresponding
28971 @samp{gdb_eval} command.
28973 @subsubheading Example
28975 In the following example, the numbers that precede the commands are the
28976 @dfn{tokens} described in @ref{GDB/MI Command Syntax, ,@sc{gdb/mi}
28977 Command Syntax}. Notice how @sc{gdb/mi} returns the same tokens in its
28981 211-data-evaluate-expression A
28984 311-data-evaluate-expression &A
28985 311^done,value="0xefffeb7c"
28987 411-data-evaluate-expression A+3
28990 511-data-evaluate-expression "A + 3"
28996 @subheading The @code{-data-list-changed-registers} Command
28997 @findex -data-list-changed-registers
28999 @subsubheading Synopsis
29002 -data-list-changed-registers
29005 Display a list of the registers that have changed.
29007 @subsubheading @value{GDBN} Command
29009 @value{GDBN} doesn't have a direct analog for this command; @code{gdbtk}
29010 has the corresponding command @samp{gdb_changed_register_list}.
29012 @subsubheading Example
29014 On a PPC MBX board:
29022 *stopped,reason="breakpoint-hit",disp="keep",bkptno="1",frame=@{
29023 func="main",args=[],file="try.c",fullname="/home/foo/bar/try.c",
29026 -data-list-changed-registers
29027 ^done,changed-registers=["0","1","2","4","5","6","7","8","9",
29028 "10","11","13","14","15","16","17","18","19","20","21","22","23",
29029 "24","25","26","27","28","30","31","64","65","66","67","69"]
29034 @subheading The @code{-data-list-register-names} Command
29035 @findex -data-list-register-names
29037 @subsubheading Synopsis
29040 -data-list-register-names [ ( @var{regno} )+ ]
29043 Show a list of register names for the current target. If no arguments
29044 are given, it shows a list of the names of all the registers. If
29045 integer numbers are given as arguments, it will print a list of the
29046 names of the registers corresponding to the arguments. To ensure
29047 consistency between a register name and its number, the output list may
29048 include empty register names.
29050 @subsubheading @value{GDBN} Command
29052 @value{GDBN} does not have a command which corresponds to
29053 @samp{-data-list-register-names}. In @code{gdbtk} there is a
29054 corresponding command @samp{gdb_regnames}.
29056 @subsubheading Example
29058 For the PPC MBX board:
29061 -data-list-register-names
29062 ^done,register-names=["r0","r1","r2","r3","r4","r5","r6","r7",
29063 "r8","r9","r10","r11","r12","r13","r14","r15","r16","r17","r18",
29064 "r19","r20","r21","r22","r23","r24","r25","r26","r27","r28","r29",
29065 "r30","r31","f0","f1","f2","f3","f4","f5","f6","f7","f8","f9",
29066 "f10","f11","f12","f13","f14","f15","f16","f17","f18","f19","f20",
29067 "f21","f22","f23","f24","f25","f26","f27","f28","f29","f30","f31",
29068 "", "pc","ps","cr","lr","ctr","xer"]
29070 -data-list-register-names 1 2 3
29071 ^done,register-names=["r1","r2","r3"]
29075 @subheading The @code{-data-list-register-values} Command
29076 @findex -data-list-register-values
29078 @subsubheading Synopsis
29081 -data-list-register-values
29082 [ @code{--skip-unavailable} ] @var{fmt} [ ( @var{regno} )*]
29085 Display the registers' contents. @var{fmt} is the format according to
29086 which the registers' contents are to be returned, followed by an optional
29087 list of numbers specifying the registers to display. A missing list of
29088 numbers indicates that the contents of all the registers must be
29089 returned. The @code{--skip-unavailable} option indicates that only
29090 the available registers are to be returned.
29092 Allowed formats for @var{fmt} are:
29109 @subsubheading @value{GDBN} Command
29111 The corresponding @value{GDBN} commands are @samp{info reg}, @samp{info
29112 all-reg}, and (in @code{gdbtk}) @samp{gdb_fetch_registers}.
29114 @subsubheading Example
29116 For a PPC MBX board (note: line breaks are for readability only, they
29117 don't appear in the actual output):
29121 -data-list-register-values r 64 65
29122 ^done,register-values=[@{number="64",value="0xfe00a300"@},
29123 @{number="65",value="0x00029002"@}]
29125 -data-list-register-values x
29126 ^done,register-values=[@{number="0",value="0xfe0043c8"@},
29127 @{number="1",value="0x3fff88"@},@{number="2",value="0xfffffffe"@},
29128 @{number="3",value="0x0"@},@{number="4",value="0xa"@},
29129 @{number="5",value="0x3fff68"@},@{number="6",value="0x3fff58"@},
29130 @{number="7",value="0xfe011e98"@},@{number="8",value="0x2"@},
29131 @{number="9",value="0xfa202820"@},@{number="10",value="0xfa202808"@},
29132 @{number="11",value="0x1"@},@{number="12",value="0x0"@},
29133 @{number="13",value="0x4544"@},@{number="14",value="0xffdfffff"@},
29134 @{number="15",value="0xffffffff"@},@{number="16",value="0xfffffeff"@},
29135 @{number="17",value="0xefffffed"@},@{number="18",value="0xfffffffe"@},
29136 @{number="19",value="0xffffffff"@},@{number="20",value="0xffffffff"@},
29137 @{number="21",value="0xffffffff"@},@{number="22",value="0xfffffff7"@},
29138 @{number="23",value="0xffffffff"@},@{number="24",value="0xffffffff"@},
29139 @{number="25",value="0xffffffff"@},@{number="26",value="0xfffffffb"@},
29140 @{number="27",value="0xffffffff"@},@{number="28",value="0xf7bfffff"@},
29141 @{number="29",value="0x0"@},@{number="30",value="0xfe010000"@},
29142 @{number="31",value="0x0"@},@{number="32",value="0x0"@},
29143 @{number="33",value="0x0"@},@{number="34",value="0x0"@},
29144 @{number="35",value="0x0"@},@{number="36",value="0x0"@},
29145 @{number="37",value="0x0"@},@{number="38",value="0x0"@},
29146 @{number="39",value="0x0"@},@{number="40",value="0x0"@},
29147 @{number="41",value="0x0"@},@{number="42",value="0x0"@},
29148 @{number="43",value="0x0"@},@{number="44",value="0x0"@},
29149 @{number="45",value="0x0"@},@{number="46",value="0x0"@},
29150 @{number="47",value="0x0"@},@{number="48",value="0x0"@},
29151 @{number="49",value="0x0"@},@{number="50",value="0x0"@},
29152 @{number="51",value="0x0"@},@{number="52",value="0x0"@},
29153 @{number="53",value="0x0"@},@{number="54",value="0x0"@},
29154 @{number="55",value="0x0"@},@{number="56",value="0x0"@},
29155 @{number="57",value="0x0"@},@{number="58",value="0x0"@},
29156 @{number="59",value="0x0"@},@{number="60",value="0x0"@},
29157 @{number="61",value="0x0"@},@{number="62",value="0x0"@},
29158 @{number="63",value="0x0"@},@{number="64",value="0xfe00a300"@},
29159 @{number="65",value="0x29002"@},@{number="66",value="0x202f04b5"@},
29160 @{number="67",value="0xfe0043b0"@},@{number="68",value="0xfe00b3e4"@},
29161 @{number="69",value="0x20002b03"@}]
29166 @subheading The @code{-data-read-memory} Command
29167 @findex -data-read-memory
29169 This command is deprecated, use @code{-data-read-memory-bytes} instead.
29171 @subsubheading Synopsis
29174 -data-read-memory [ -o @var{byte-offset} ]
29175 @var{address} @var{word-format} @var{word-size}
29176 @var{nr-rows} @var{nr-cols} [ @var{aschar} ]
29183 @item @var{address}
29184 An expression specifying the address of the first memory word to be
29185 read. Complex expressions containing embedded white space should be
29186 quoted using the C convention.
29188 @item @var{word-format}
29189 The format to be used to print the memory words. The notation is the
29190 same as for @value{GDBN}'s @code{print} command (@pxref{Output Formats,
29193 @item @var{word-size}
29194 The size of each memory word in bytes.
29196 @item @var{nr-rows}
29197 The number of rows in the output table.
29199 @item @var{nr-cols}
29200 The number of columns in the output table.
29203 If present, indicates that each row should include an @sc{ascii} dump. The
29204 value of @var{aschar} is used as a padding character when a byte is not a
29205 member of the printable @sc{ascii} character set (printable @sc{ascii}
29206 characters are those whose code is between 32 and 126, inclusively).
29208 @item @var{byte-offset}
29209 An offset to add to the @var{address} before fetching memory.
29212 This command displays memory contents as a table of @var{nr-rows} by
29213 @var{nr-cols} words, each word being @var{word-size} bytes. In total,
29214 @code{@var{nr-rows} * @var{nr-cols} * @var{word-size}} bytes are read
29215 (returned as @samp{total-bytes}). Should less than the requested number
29216 of bytes be returned by the target, the missing words are identified
29217 using @samp{N/A}. The number of bytes read from the target is returned
29218 in @samp{nr-bytes} and the starting address used to read memory in
29221 The address of the next/previous row or page is available in
29222 @samp{next-row} and @samp{prev-row}, @samp{next-page} and
29225 @subsubheading @value{GDBN} Command
29227 The corresponding @value{GDBN} command is @samp{x}. @code{gdbtk} has
29228 @samp{gdb_get_mem} memory read command.
29230 @subsubheading Example
29232 Read six bytes of memory starting at @code{bytes+6} but then offset by
29233 @code{-6} bytes. Format as three rows of two columns. One byte per
29234 word. Display each word in hex.
29238 9-data-read-memory -o -6 -- bytes+6 x 1 3 2
29239 9^done,addr="0x00001390",nr-bytes="6",total-bytes="6",
29240 next-row="0x00001396",prev-row="0x0000138e",next-page="0x00001396",
29241 prev-page="0x0000138a",memory=[
29242 @{addr="0x00001390",data=["0x00","0x01"]@},
29243 @{addr="0x00001392",data=["0x02","0x03"]@},
29244 @{addr="0x00001394",data=["0x04","0x05"]@}]
29248 Read two bytes of memory starting at address @code{shorts + 64} and
29249 display as a single word formatted in decimal.
29253 5-data-read-memory shorts+64 d 2 1 1
29254 5^done,addr="0x00001510",nr-bytes="2",total-bytes="2",
29255 next-row="0x00001512",prev-row="0x0000150e",
29256 next-page="0x00001512",prev-page="0x0000150e",memory=[
29257 @{addr="0x00001510",data=["128"]@}]
29261 Read thirty two bytes of memory starting at @code{bytes+16} and format
29262 as eight rows of four columns. Include a string encoding with @samp{x}
29263 used as the non-printable character.
29267 4-data-read-memory bytes+16 x 1 8 4 x
29268 4^done,addr="0x000013a0",nr-bytes="32",total-bytes="32",
29269 next-row="0x000013c0",prev-row="0x0000139c",
29270 next-page="0x000013c0",prev-page="0x00001380",memory=[
29271 @{addr="0x000013a0",data=["0x10","0x11","0x12","0x13"],ascii="xxxx"@},
29272 @{addr="0x000013a4",data=["0x14","0x15","0x16","0x17"],ascii="xxxx"@},
29273 @{addr="0x000013a8",data=["0x18","0x19","0x1a","0x1b"],ascii="xxxx"@},
29274 @{addr="0x000013ac",data=["0x1c","0x1d","0x1e","0x1f"],ascii="xxxx"@},
29275 @{addr="0x000013b0",data=["0x20","0x21","0x22","0x23"],ascii=" !\"#"@},
29276 @{addr="0x000013b4",data=["0x24","0x25","0x26","0x27"],ascii="$%&'"@},
29277 @{addr="0x000013b8",data=["0x28","0x29","0x2a","0x2b"],ascii="()*+"@},
29278 @{addr="0x000013bc",data=["0x2c","0x2d","0x2e","0x2f"],ascii=",-./"@}]
29282 @subheading The @code{-data-read-memory-bytes} Command
29283 @findex -data-read-memory-bytes
29285 @subsubheading Synopsis
29288 -data-read-memory-bytes [ -o @var{byte-offset} ]
29289 @var{address} @var{count}
29296 @item @var{address}
29297 An expression specifying the address of the first memory word to be
29298 read. Complex expressions containing embedded white space should be
29299 quoted using the C convention.
29302 The number of bytes to read. This should be an integer literal.
29304 @item @var{byte-offset}
29305 The offsets in bytes relative to @var{address} at which to start
29306 reading. This should be an integer literal. This option is provided
29307 so that a frontend is not required to first evaluate address and then
29308 perform address arithmetics itself.
29312 This command attempts to read all accessible memory regions in the
29313 specified range. First, all regions marked as unreadable in the memory
29314 map (if one is defined) will be skipped. @xref{Memory Region
29315 Attributes}. Second, @value{GDBN} will attempt to read the remaining
29316 regions. For each one, if reading full region results in an errors,
29317 @value{GDBN} will try to read a subset of the region.
29319 In general, every single byte in the region may be readable or not,
29320 and the only way to read every readable byte is to try a read at
29321 every address, which is not practical. Therefore, @value{GDBN} will
29322 attempt to read all accessible bytes at either beginning or the end
29323 of the region, using a binary division scheme. This heuristic works
29324 well for reading accross a memory map boundary. Note that if a region
29325 has a readable range that is neither at the beginning or the end,
29326 @value{GDBN} will not read it.
29328 The result record (@pxref{GDB/MI Result Records}) that is output of
29329 the command includes a field named @samp{memory} whose content is a
29330 list of tuples. Each tuple represent a successfully read memory block
29331 and has the following fields:
29335 The start address of the memory block, as hexadecimal literal.
29338 The end address of the memory block, as hexadecimal literal.
29341 The offset of the memory block, as hexadecimal literal, relative to
29342 the start address passed to @code{-data-read-memory-bytes}.
29345 The contents of the memory block, in hex.
29351 @subsubheading @value{GDBN} Command
29353 The corresponding @value{GDBN} command is @samp{x}.
29355 @subsubheading Example
29359 -data-read-memory-bytes &a 10
29360 ^done,memory=[@{begin="0xbffff154",offset="0x00000000",
29362 contents="01000000020000000300"@}]
29367 @subheading The @code{-data-write-memory-bytes} Command
29368 @findex -data-write-memory-bytes
29370 @subsubheading Synopsis
29373 -data-write-memory-bytes @var{address} @var{contents}
29374 -data-write-memory-bytes @var{address} @var{contents} @r{[}@var{count}@r{]}
29381 @item @var{address}
29382 An expression specifying the address of the first memory word to be
29383 read. Complex expressions containing embedded white space should be
29384 quoted using the C convention.
29386 @item @var{contents}
29387 The hex-encoded bytes to write.
29390 Optional argument indicating the number of bytes to be written. If @var{count}
29391 is greater than @var{contents}' length, @value{GDBN} will repeatedly
29392 write @var{contents} until it fills @var{count} bytes.
29396 @subsubheading @value{GDBN} Command
29398 There's no corresponding @value{GDBN} command.
29400 @subsubheading Example
29404 -data-write-memory-bytes &a "aabbccdd"
29411 -data-write-memory-bytes &a "aabbccdd" 16e
29416 @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
29417 @node GDB/MI Tracepoint Commands
29418 @section @sc{gdb/mi} Tracepoint Commands
29420 The commands defined in this section implement MI support for
29421 tracepoints. For detailed introduction, see @ref{Tracepoints}.
29423 @subheading The @code{-trace-find} Command
29424 @findex -trace-find
29426 @subsubheading Synopsis
29429 -trace-find @var{mode} [@var{parameters}@dots{}]
29432 Find a trace frame using criteria defined by @var{mode} and
29433 @var{parameters}. The following table lists permissible
29434 modes and their parameters. For details of operation, see @ref{tfind}.
29439 No parameters are required. Stops examining trace frames.
29442 An integer is required as parameter. Selects tracepoint frame with
29445 @item tracepoint-number
29446 An integer is required as parameter. Finds next
29447 trace frame that corresponds to tracepoint with the specified number.
29450 An address is required as parameter. Finds
29451 next trace frame that corresponds to any tracepoint at the specified
29454 @item pc-inside-range
29455 Two addresses are required as parameters. Finds next trace
29456 frame that corresponds to a tracepoint at an address inside the
29457 specified range. Both bounds are considered to be inside the range.
29459 @item pc-outside-range
29460 Two addresses are required as parameters. Finds
29461 next trace frame that corresponds to a tracepoint at an address outside
29462 the specified range. Both bounds are considered to be inside the range.
29465 Line specification is required as parameter. @xref{Specify Location}.
29466 Finds next trace frame that corresponds to a tracepoint at
29467 the specified location.
29471 If @samp{none} was passed as @var{mode}, the response does not
29472 have fields. Otherwise, the response may have the following fields:
29476 This field has either @samp{0} or @samp{1} as the value, depending
29477 on whether a matching tracepoint was found.
29480 The index of the found traceframe. This field is present iff
29481 the @samp{found} field has value of @samp{1}.
29484 The index of the found tracepoint. This field is present iff
29485 the @samp{found} field has value of @samp{1}.
29488 The information about the frame corresponding to the found trace
29489 frame. This field is present only if a trace frame was found.
29490 @xref{GDB/MI Frame Information}, for description of this field.
29494 @subsubheading @value{GDBN} Command
29496 The corresponding @value{GDBN} command is @samp{tfind}.
29498 @subheading -trace-define-variable
29499 @findex -trace-define-variable
29501 @subsubheading Synopsis
29504 -trace-define-variable @var{name} [ @var{value} ]
29507 Create trace variable @var{name} if it does not exist. If
29508 @var{value} is specified, sets the initial value of the specified
29509 trace variable to that value. Note that the @var{name} should start
29510 with the @samp{$} character.
29512 @subsubheading @value{GDBN} Command
29514 The corresponding @value{GDBN} command is @samp{tvariable}.
29516 @subheading The @code{-trace-frame-collected} Command
29517 @findex -trace-frame-collected
29519 @subsubheading Synopsis
29522 -trace-frame-collected
29523 [--var-print-values @var{var_pval}]
29524 [--comp-print-values @var{comp_pval}]
29525 [--registers-format @var{regformat}]
29526 [--memory-contents]
29529 This command returns the set of collected objects, register names,
29530 trace state variable names, memory ranges and computed expressions
29531 that have been collected at a particular trace frame. The optional
29532 parameters to the command affect the output format in different ways.
29533 See the output description table below for more details.
29535 The reported names can be used in the normal manner to create
29536 varobjs and inspect the objects themselves. The items returned by
29537 this command are categorized so that it is clear which is a variable,
29538 which is a register, which is a trace state variable, which is a
29539 memory range and which is a computed expression.
29541 For instance, if the actions were
29543 collect myVar, myArray[myIndex], myObj.field, myPtr->field, myCount + 2
29544 collect *(int*)0xaf02bef0@@40
29548 the object collected in its entirety would be @code{myVar}. The
29549 object @code{myArray} would be partially collected, because only the
29550 element at index @code{myIndex} would be collected. The remaining
29551 objects would be computed expressions.
29553 An example output would be:
29557 -trace-frame-collected
29559 explicit-variables=[@{name="myVar",value="1"@}],
29560 computed-expressions=[@{name="myArray[myIndex]",value="0"@},
29561 @{name="myObj.field",value="0"@},
29562 @{name="myPtr->field",value="1"@},
29563 @{name="myCount + 2",value="3"@},
29564 @{name="$tvar1 + 1",value="43970027"@}],
29565 registers=[@{number="0",value="0x7fe2c6e79ec8"@},
29566 @{number="1",value="0x0"@},
29567 @{number="2",value="0x4"@},
29569 @{number="125",value="0x0"@}],
29570 tvars=[@{name="$tvar1",current="43970026"@}],
29571 memory=[@{address="0x0000000000602264",length="4"@},
29572 @{address="0x0000000000615bc0",length="4"@}]
29579 @item explicit-variables
29580 The set of objects that have been collected in their entirety (as
29581 opposed to collecting just a few elements of an array or a few struct
29582 members). For each object, its name and value are printed.
29583 The @code{--var-print-values} option affects how or whether the value
29584 field is output. If @var{var_pval} is 0, then print only the names;
29585 if it is 1, print also their values; and if it is 2, print the name,
29586 type and value for simple data types, and the name and type for
29587 arrays, structures and unions.
29589 @item computed-expressions
29590 The set of computed expressions that have been collected at the
29591 current trace frame. The @code{--comp-print-values} option affects
29592 this set like the @code{--var-print-values} option affects the
29593 @code{explicit-variables} set. See above.
29596 The registers that have been collected at the current trace frame.
29597 For each register collected, the name and current value are returned.
29598 The value is formatted according to the @code{--registers-format}
29599 option. See the @command{-data-list-register-values} command for a
29600 list of the allowed formats. The default is @samp{x}.
29603 The trace state variables that have been collected at the current
29604 trace frame. For each trace state variable collected, the name and
29605 current value are returned.
29608 The set of memory ranges that have been collected at the current trace
29609 frame. Its content is a list of tuples. Each tuple represents a
29610 collected memory range and has the following fields:
29614 The start address of the memory range, as hexadecimal literal.
29617 The length of the memory range, as decimal literal.
29620 The contents of the memory block, in hex. This field is only present
29621 if the @code{--memory-contents} option is specified.
29627 @subsubheading @value{GDBN} Command
29629 There is no corresponding @value{GDBN} command.
29631 @subsubheading Example
29633 @subheading -trace-list-variables
29634 @findex -trace-list-variables
29636 @subsubheading Synopsis
29639 -trace-list-variables
29642 Return a table of all defined trace variables. Each element of the
29643 table has the following fields:
29647 The name of the trace variable. This field is always present.
29650 The initial value. This is a 64-bit signed integer. This
29651 field is always present.
29654 The value the trace variable has at the moment. This is a 64-bit
29655 signed integer. This field is absent iff current value is
29656 not defined, for example if the trace was never run, or is
29661 @subsubheading @value{GDBN} Command
29663 The corresponding @value{GDBN} command is @samp{tvariables}.
29665 @subsubheading Example
29669 -trace-list-variables
29670 ^done,trace-variables=@{nr_rows="1",nr_cols="3",
29671 hdr=[@{width="15",alignment="-1",col_name="name",colhdr="Name"@},
29672 @{width="11",alignment="-1",col_name="initial",colhdr="Initial"@},
29673 @{width="11",alignment="-1",col_name="current",colhdr="Current"@}],
29674 body=[variable=@{name="$trace_timestamp",initial="0"@}
29675 variable=@{name="$foo",initial="10",current="15"@}]@}
29679 @subheading -trace-save
29680 @findex -trace-save
29682 @subsubheading Synopsis
29685 -trace-save [-r ] @var{filename}
29688 Saves the collected trace data to @var{filename}. Without the
29689 @samp{-r} option, the data is downloaded from the target and saved
29690 in a local file. With the @samp{-r} option the target is asked
29691 to perform the save.
29693 @subsubheading @value{GDBN} Command
29695 The corresponding @value{GDBN} command is @samp{tsave}.
29698 @subheading -trace-start
29699 @findex -trace-start
29701 @subsubheading Synopsis
29707 Starts a tracing experiments. The result of this command does not
29710 @subsubheading @value{GDBN} Command
29712 The corresponding @value{GDBN} command is @samp{tstart}.
29714 @subheading -trace-status
29715 @findex -trace-status
29717 @subsubheading Synopsis
29723 Obtains the status of a tracing experiment. The result may include
29724 the following fields:
29729 May have a value of either @samp{0}, when no tracing operations are
29730 supported, @samp{1}, when all tracing operations are supported, or
29731 @samp{file} when examining trace file. In the latter case, examining
29732 of trace frame is possible but new tracing experiement cannot be
29733 started. This field is always present.
29736 May have a value of either @samp{0} or @samp{1} depending on whether
29737 tracing experiement is in progress on target. This field is present
29738 if @samp{supported} field is not @samp{0}.
29741 Report the reason why the tracing was stopped last time. This field
29742 may be absent iff tracing was never stopped on target yet. The
29743 value of @samp{request} means the tracing was stopped as result of
29744 the @code{-trace-stop} command. The value of @samp{overflow} means
29745 the tracing buffer is full. The value of @samp{disconnection} means
29746 tracing was automatically stopped when @value{GDBN} has disconnected.
29747 The value of @samp{passcount} means tracing was stopped when a
29748 tracepoint was passed a maximal number of times for that tracepoint.
29749 This field is present if @samp{supported} field is not @samp{0}.
29751 @item stopping-tracepoint
29752 The number of tracepoint whose passcount as exceeded. This field is
29753 present iff the @samp{stop-reason} field has the value of
29757 @itemx frames-created
29758 The @samp{frames} field is a count of the total number of trace frames
29759 in the trace buffer, while @samp{frames-created} is the total created
29760 during the run, including ones that were discarded, such as when a
29761 circular trace buffer filled up. Both fields are optional.
29765 These fields tell the current size of the tracing buffer and the
29766 remaining space. These fields are optional.
29769 The value of the circular trace buffer flag. @code{1} means that the
29770 trace buffer is circular and old trace frames will be discarded if
29771 necessary to make room, @code{0} means that the trace buffer is linear
29775 The value of the disconnected tracing flag. @code{1} means that
29776 tracing will continue after @value{GDBN} disconnects, @code{0} means
29777 that the trace run will stop.
29780 The filename of the trace file being examined. This field is
29781 optional, and only present when examining a trace file.
29785 @subsubheading @value{GDBN} Command
29787 The corresponding @value{GDBN} command is @samp{tstatus}.
29789 @subheading -trace-stop
29790 @findex -trace-stop
29792 @subsubheading Synopsis
29798 Stops a tracing experiment. The result of this command has the same
29799 fields as @code{-trace-status}, except that the @samp{supported} and
29800 @samp{running} fields are not output.
29802 @subsubheading @value{GDBN} Command
29804 The corresponding @value{GDBN} command is @samp{tstop}.
29807 @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
29808 @node GDB/MI Symbol Query
29809 @section @sc{gdb/mi} Symbol Query Commands
29813 @subheading The @code{-symbol-info-address} Command
29814 @findex -symbol-info-address
29816 @subsubheading Synopsis
29819 -symbol-info-address @var{symbol}
29822 Describe where @var{symbol} is stored.
29824 @subsubheading @value{GDBN} Command
29826 The corresponding @value{GDBN} command is @samp{info address}.
29828 @subsubheading Example
29832 @subheading The @code{-symbol-info-file} Command
29833 @findex -symbol-info-file
29835 @subsubheading Synopsis
29841 Show the file for the symbol.
29843 @subsubheading @value{GDBN} Command
29845 There's no equivalent @value{GDBN} command. @code{gdbtk} has
29846 @samp{gdb_find_file}.
29848 @subsubheading Example
29852 @subheading The @code{-symbol-info-function} Command
29853 @findex -symbol-info-function
29855 @subsubheading Synopsis
29858 -symbol-info-function
29861 Show which function the symbol lives in.
29863 @subsubheading @value{GDBN} Command
29865 @samp{gdb_get_function} in @code{gdbtk}.
29867 @subsubheading Example
29871 @subheading The @code{-symbol-info-line} Command
29872 @findex -symbol-info-line
29874 @subsubheading Synopsis
29880 Show the core addresses of the code for a source line.
29882 @subsubheading @value{GDBN} Command
29884 The corresponding @value{GDBN} command is @samp{info line}.
29885 @code{gdbtk} has the @samp{gdb_get_line} and @samp{gdb_get_file} commands.
29887 @subsubheading Example
29891 @subheading The @code{-symbol-info-symbol} Command
29892 @findex -symbol-info-symbol
29894 @subsubheading Synopsis
29897 -symbol-info-symbol @var{addr}
29900 Describe what symbol is at location @var{addr}.
29902 @subsubheading @value{GDBN} Command
29904 The corresponding @value{GDBN} command is @samp{info symbol}.
29906 @subsubheading Example
29910 @subheading The @code{-symbol-list-functions} Command
29911 @findex -symbol-list-functions
29913 @subsubheading Synopsis
29916 -symbol-list-functions
29919 List the functions in the executable.
29921 @subsubheading @value{GDBN} Command
29923 @samp{info functions} in @value{GDBN}, @samp{gdb_listfunc} and
29924 @samp{gdb_search} in @code{gdbtk}.
29926 @subsubheading Example
29931 @subheading The @code{-symbol-list-lines} Command
29932 @findex -symbol-list-lines
29934 @subsubheading Synopsis
29937 -symbol-list-lines @var{filename}
29940 Print the list of lines that contain code and their associated program
29941 addresses for the given source filename. The entries are sorted in
29942 ascending PC order.
29944 @subsubheading @value{GDBN} Command
29946 There is no corresponding @value{GDBN} command.
29948 @subsubheading Example
29951 -symbol-list-lines basics.c
29952 ^done,lines=[@{pc="0x08048554",line="7"@},@{pc="0x0804855a",line="8"@}]
29958 @subheading The @code{-symbol-list-types} Command
29959 @findex -symbol-list-types
29961 @subsubheading Synopsis
29967 List all the type names.
29969 @subsubheading @value{GDBN} Command
29971 The corresponding commands are @samp{info types} in @value{GDBN},
29972 @samp{gdb_search} in @code{gdbtk}.
29974 @subsubheading Example
29978 @subheading The @code{-symbol-list-variables} Command
29979 @findex -symbol-list-variables
29981 @subsubheading Synopsis
29984 -symbol-list-variables
29987 List all the global and static variable names.
29989 @subsubheading @value{GDBN} Command
29991 @samp{info variables} in @value{GDBN}, @samp{gdb_search} in @code{gdbtk}.
29993 @subsubheading Example
29997 @subheading The @code{-symbol-locate} Command
29998 @findex -symbol-locate
30000 @subsubheading Synopsis
30006 @subsubheading @value{GDBN} Command
30008 @samp{gdb_loc} in @code{gdbtk}.
30010 @subsubheading Example
30014 @subheading The @code{-symbol-type} Command
30015 @findex -symbol-type
30017 @subsubheading Synopsis
30020 -symbol-type @var{variable}
30023 Show type of @var{variable}.
30025 @subsubheading @value{GDBN} Command
30027 The corresponding @value{GDBN} command is @samp{ptype}, @code{gdbtk} has
30028 @samp{gdb_obj_variable}.
30030 @subsubheading Example
30035 @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
30036 @node GDB/MI File Commands
30037 @section @sc{gdb/mi} File Commands
30039 This section describes the GDB/MI commands to specify executable file names
30040 and to read in and obtain symbol table information.
30042 @subheading The @code{-file-exec-and-symbols} Command
30043 @findex -file-exec-and-symbols
30045 @subsubheading Synopsis
30048 -file-exec-and-symbols @var{file}
30051 Specify the executable file to be debugged. This file is the one from
30052 which the symbol table is also read. If no file is specified, the
30053 command clears the executable and symbol information. If breakpoints
30054 are set when using this command with no arguments, @value{GDBN} will produce
30055 error messages. Otherwise, no output is produced, except a completion
30058 @subsubheading @value{GDBN} Command
30060 The corresponding @value{GDBN} command is @samp{file}.
30062 @subsubheading Example
30066 -file-exec-and-symbols /kwikemart/marge/ezannoni/TRUNK/mbx/hello.mbx
30072 @subheading The @code{-file-exec-file} Command
30073 @findex -file-exec-file
30075 @subsubheading Synopsis
30078 -file-exec-file @var{file}
30081 Specify the executable file to be debugged. Unlike
30082 @samp{-file-exec-and-symbols}, the symbol table is @emph{not} read
30083 from this file. If used without argument, @value{GDBN} clears the information
30084 about the executable file. No output is produced, except a completion
30087 @subsubheading @value{GDBN} Command
30089 The corresponding @value{GDBN} command is @samp{exec-file}.
30091 @subsubheading Example
30095 -file-exec-file /kwikemart/marge/ezannoni/TRUNK/mbx/hello.mbx
30102 @subheading The @code{-file-list-exec-sections} Command
30103 @findex -file-list-exec-sections
30105 @subsubheading Synopsis
30108 -file-list-exec-sections
30111 List the sections of the current executable file.
30113 @subsubheading @value{GDBN} Command
30115 The @value{GDBN} command @samp{info file} shows, among the rest, the same
30116 information as this command. @code{gdbtk} has a corresponding command
30117 @samp{gdb_load_info}.
30119 @subsubheading Example
30124 @subheading The @code{-file-list-exec-source-file} Command
30125 @findex -file-list-exec-source-file
30127 @subsubheading Synopsis
30130 -file-list-exec-source-file
30133 List the line number, the current source file, and the absolute path
30134 to the current source file for the current executable. The macro
30135 information field has a value of @samp{1} or @samp{0} depending on
30136 whether or not the file includes preprocessor macro information.
30138 @subsubheading @value{GDBN} Command
30140 The @value{GDBN} equivalent is @samp{info source}
30142 @subsubheading Example
30146 123-file-list-exec-source-file
30147 123^done,line="1",file="foo.c",fullname="/home/bar/foo.c,macro-info="1"
30152 @subheading The @code{-file-list-exec-source-files} Command
30153 @findex -file-list-exec-source-files
30155 @subsubheading Synopsis
30158 -file-list-exec-source-files
30161 List the source files for the current executable.
30163 It will always output both the filename and fullname (absolute file
30164 name) of a source file.
30166 @subsubheading @value{GDBN} Command
30168 The @value{GDBN} equivalent is @samp{info sources}.
30169 @code{gdbtk} has an analogous command @samp{gdb_listfiles}.
30171 @subsubheading Example
30174 -file-list-exec-source-files
30176 @{file=foo.c,fullname=/home/foo.c@},
30177 @{file=/home/bar.c,fullname=/home/bar.c@},
30178 @{file=gdb_could_not_find_fullpath.c@}]
30183 @subheading The @code{-file-list-shared-libraries} Command
30184 @findex -file-list-shared-libraries
30186 @subsubheading Synopsis
30189 -file-list-shared-libraries
30192 List the shared libraries in the program.
30194 @subsubheading @value{GDBN} Command
30196 The corresponding @value{GDBN} command is @samp{info shared}.
30198 @subsubheading Example
30202 @subheading The @code{-file-list-symbol-files} Command
30203 @findex -file-list-symbol-files
30205 @subsubheading Synopsis
30208 -file-list-symbol-files
30213 @subsubheading @value{GDBN} Command
30215 The corresponding @value{GDBN} command is @samp{info file} (part of it).
30217 @subsubheading Example
30222 @subheading The @code{-file-symbol-file} Command
30223 @findex -file-symbol-file
30225 @subsubheading Synopsis
30228 -file-symbol-file @var{file}
30231 Read symbol table info from the specified @var{file} argument. When
30232 used without arguments, clears @value{GDBN}'s symbol table info. No output is
30233 produced, except for a completion notification.
30235 @subsubheading @value{GDBN} Command
30237 The corresponding @value{GDBN} command is @samp{symbol-file}.
30239 @subsubheading Example
30243 -file-symbol-file /kwikemart/marge/ezannoni/TRUNK/mbx/hello.mbx
30249 @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
30250 @node GDB/MI Memory Overlay Commands
30251 @section @sc{gdb/mi} Memory Overlay Commands
30253 The memory overlay commands are not implemented.
30255 @c @subheading -overlay-auto
30257 @c @subheading -overlay-list-mapping-state
30259 @c @subheading -overlay-list-overlays
30261 @c @subheading -overlay-map
30263 @c @subheading -overlay-off
30265 @c @subheading -overlay-on
30267 @c @subheading -overlay-unmap
30269 @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
30270 @node GDB/MI Signal Handling Commands
30271 @section @sc{gdb/mi} Signal Handling Commands
30273 Signal handling commands are not implemented.
30275 @c @subheading -signal-handle
30277 @c @subheading -signal-list-handle-actions
30279 @c @subheading -signal-list-signal-types
30283 @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
30284 @node GDB/MI Target Manipulation
30285 @section @sc{gdb/mi} Target Manipulation Commands
30288 @subheading The @code{-target-attach} Command
30289 @findex -target-attach
30291 @subsubheading Synopsis
30294 -target-attach @var{pid} | @var{gid} | @var{file}
30297 Attach to a process @var{pid} or a file @var{file} outside of
30298 @value{GDBN}, or a thread group @var{gid}. If attaching to a thread
30299 group, the id previously returned by
30300 @samp{-list-thread-groups --available} must be used.
30302 @subsubheading @value{GDBN} Command
30304 The corresponding @value{GDBN} command is @samp{attach}.
30306 @subsubheading Example
30310 =thread-created,id="1"
30311 *stopped,thread-id="1",frame=@{addr="0xb7f7e410",func="bar",args=[]@}
30317 @subheading The @code{-target-compare-sections} Command
30318 @findex -target-compare-sections
30320 @subsubheading Synopsis
30323 -target-compare-sections [ @var{section} ]
30326 Compare data of section @var{section} on target to the exec file.
30327 Without the argument, all sections are compared.
30329 @subsubheading @value{GDBN} Command
30331 The @value{GDBN} equivalent is @samp{compare-sections}.
30333 @subsubheading Example
30338 @subheading The @code{-target-detach} Command
30339 @findex -target-detach
30341 @subsubheading Synopsis
30344 -target-detach [ @var{pid} | @var{gid} ]
30347 Detach from the remote target which normally resumes its execution.
30348 If either @var{pid} or @var{gid} is specified, detaches from either
30349 the specified process, or specified thread group. There's no output.
30351 @subsubheading @value{GDBN} Command
30353 The corresponding @value{GDBN} command is @samp{detach}.
30355 @subsubheading Example
30365 @subheading The @code{-target-disconnect} Command
30366 @findex -target-disconnect
30368 @subsubheading Synopsis
30374 Disconnect from the remote target. There's no output and the target is
30375 generally not resumed.
30377 @subsubheading @value{GDBN} Command
30379 The corresponding @value{GDBN} command is @samp{disconnect}.
30381 @subsubheading Example
30391 @subheading The @code{-target-download} Command
30392 @findex -target-download
30394 @subsubheading Synopsis
30400 Loads the executable onto the remote target.
30401 It prints out an update message every half second, which includes the fields:
30405 The name of the section.
30407 The size of what has been sent so far for that section.
30409 The size of the section.
30411 The total size of what was sent so far (the current and the previous sections).
30413 The size of the overall executable to download.
30417 Each message is sent as status record (@pxref{GDB/MI Output Syntax, ,
30418 @sc{gdb/mi} Output Syntax}).
30420 In addition, it prints the name and size of the sections, as they are
30421 downloaded. These messages include the following fields:
30425 The name of the section.
30427 The size of the section.
30429 The size of the overall executable to download.
30433 At the end, a summary is printed.
30435 @subsubheading @value{GDBN} Command
30437 The corresponding @value{GDBN} command is @samp{load}.
30439 @subsubheading Example
30441 Note: each status message appears on a single line. Here the messages
30442 have been broken down so that they can fit onto a page.
30447 +download,@{section=".text",section-size="6668",total-size="9880"@}
30448 +download,@{section=".text",section-sent="512",section-size="6668",
30449 total-sent="512",total-size="9880"@}
30450 +download,@{section=".text",section-sent="1024",section-size="6668",
30451 total-sent="1024",total-size="9880"@}
30452 +download,@{section=".text",section-sent="1536",section-size="6668",
30453 total-sent="1536",total-size="9880"@}
30454 +download,@{section=".text",section-sent="2048",section-size="6668",
30455 total-sent="2048",total-size="9880"@}
30456 +download,@{section=".text",section-sent="2560",section-size="6668",
30457 total-sent="2560",total-size="9880"@}
30458 +download,@{section=".text",section-sent="3072",section-size="6668",
30459 total-sent="3072",total-size="9880"@}
30460 +download,@{section=".text",section-sent="3584",section-size="6668",
30461 total-sent="3584",total-size="9880"@}
30462 +download,@{section=".text",section-sent="4096",section-size="6668",
30463 total-sent="4096",total-size="9880"@}
30464 +download,@{section=".text",section-sent="4608",section-size="6668",
30465 total-sent="4608",total-size="9880"@}
30466 +download,@{section=".text",section-sent="5120",section-size="6668",
30467 total-sent="5120",total-size="9880"@}
30468 +download,@{section=".text",section-sent="5632",section-size="6668",
30469 total-sent="5632",total-size="9880"@}
30470 +download,@{section=".text",section-sent="6144",section-size="6668",
30471 total-sent="6144",total-size="9880"@}
30472 +download,@{section=".text",section-sent="6656",section-size="6668",
30473 total-sent="6656",total-size="9880"@}
30474 +download,@{section=".init",section-size="28",total-size="9880"@}
30475 +download,@{section=".fini",section-size="28",total-size="9880"@}
30476 +download,@{section=".data",section-size="3156",total-size="9880"@}
30477 +download,@{section=".data",section-sent="512",section-size="3156",
30478 total-sent="7236",total-size="9880"@}
30479 +download,@{section=".data",section-sent="1024",section-size="3156",
30480 total-sent="7748",total-size="9880"@}
30481 +download,@{section=".data",section-sent="1536",section-size="3156",
30482 total-sent="8260",total-size="9880"@}
30483 +download,@{section=".data",section-sent="2048",section-size="3156",
30484 total-sent="8772",total-size="9880"@}
30485 +download,@{section=".data",section-sent="2560",section-size="3156",
30486 total-sent="9284",total-size="9880"@}
30487 +download,@{section=".data",section-sent="3072",section-size="3156",
30488 total-sent="9796",total-size="9880"@}
30489 ^done,address="0x10004",load-size="9880",transfer-rate="6586",
30496 @subheading The @code{-target-exec-status} Command
30497 @findex -target-exec-status
30499 @subsubheading Synopsis
30502 -target-exec-status
30505 Provide information on the state of the target (whether it is running or
30506 not, for instance).
30508 @subsubheading @value{GDBN} Command
30510 There's no equivalent @value{GDBN} command.
30512 @subsubheading Example
30516 @subheading The @code{-target-list-available-targets} Command
30517 @findex -target-list-available-targets
30519 @subsubheading Synopsis
30522 -target-list-available-targets
30525 List the possible targets to connect to.
30527 @subsubheading @value{GDBN} Command
30529 The corresponding @value{GDBN} command is @samp{help target}.
30531 @subsubheading Example
30535 @subheading The @code{-target-list-current-targets} Command
30536 @findex -target-list-current-targets
30538 @subsubheading Synopsis
30541 -target-list-current-targets
30544 Describe the current target.
30546 @subsubheading @value{GDBN} Command
30548 The corresponding information is printed by @samp{info file} (among
30551 @subsubheading Example
30555 @subheading The @code{-target-list-parameters} Command
30556 @findex -target-list-parameters
30558 @subsubheading Synopsis
30561 -target-list-parameters
30567 @subsubheading @value{GDBN} Command
30571 @subsubheading Example
30575 @subheading The @code{-target-select} Command
30576 @findex -target-select
30578 @subsubheading Synopsis
30581 -target-select @var{type} @var{parameters @dots{}}
30584 Connect @value{GDBN} to the remote target. This command takes two args:
30588 The type of target, for instance @samp{remote}, etc.
30589 @item @var{parameters}
30590 Device names, host names and the like. @xref{Target Commands, ,
30591 Commands for Managing Targets}, for more details.
30594 The output is a connection notification, followed by the address at
30595 which the target program is, in the following form:
30598 ^connected,addr="@var{address}",func="@var{function name}",
30599 args=[@var{arg list}]
30602 @subsubheading @value{GDBN} Command
30604 The corresponding @value{GDBN} command is @samp{target}.
30606 @subsubheading Example
30610 -target-select remote /dev/ttya
30611 ^connected,addr="0xfe00a300",func="??",args=[]
30615 @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
30616 @node GDB/MI File Transfer Commands
30617 @section @sc{gdb/mi} File Transfer Commands
30620 @subheading The @code{-target-file-put} Command
30621 @findex -target-file-put
30623 @subsubheading Synopsis
30626 -target-file-put @var{hostfile} @var{targetfile}
30629 Copy file @var{hostfile} from the host system (the machine running
30630 @value{GDBN}) to @var{targetfile} on the target system.
30632 @subsubheading @value{GDBN} Command
30634 The corresponding @value{GDBN} command is @samp{remote put}.
30636 @subsubheading Example
30640 -target-file-put localfile remotefile
30646 @subheading The @code{-target-file-get} Command
30647 @findex -target-file-get
30649 @subsubheading Synopsis
30652 -target-file-get @var{targetfile} @var{hostfile}
30655 Copy file @var{targetfile} from the target system to @var{hostfile}
30656 on the host system.
30658 @subsubheading @value{GDBN} Command
30660 The corresponding @value{GDBN} command is @samp{remote get}.
30662 @subsubheading Example
30666 -target-file-get remotefile localfile
30672 @subheading The @code{-target-file-delete} Command
30673 @findex -target-file-delete
30675 @subsubheading Synopsis
30678 -target-file-delete @var{targetfile}
30681 Delete @var{targetfile} from the target system.
30683 @subsubheading @value{GDBN} Command
30685 The corresponding @value{GDBN} command is @samp{remote delete}.
30687 @subsubheading Example
30691 -target-file-delete remotefile
30697 @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
30698 @node GDB/MI Ada Exceptions Commands
30699 @section Ada Exceptions @sc{gdb/mi} Commands
30701 @subheading The @code{-info-ada-exceptions} Command
30702 @findex -info-ada-exceptions
30704 @subsubheading Synopsis
30707 -info-ada-exceptions [ @var{regexp}]
30710 List all Ada exceptions defined within the program being debugged.
30711 With a regular expression @var{regexp}, only those exceptions whose
30712 names match @var{regexp} are listed.
30714 @subsubheading @value{GDBN} Command
30716 The corresponding @value{GDBN} command is @samp{info exceptions}.
30718 @subsubheading Result
30720 The result is a table of Ada exceptions. The following columns are
30721 defined for each exception:
30725 The name of the exception.
30728 The address of the exception.
30732 @subsubheading Example
30735 -info-ada-exceptions aint
30736 ^done,ada-exceptions=@{nr_rows="2",nr_cols="2",
30737 hdr=[@{width="1",alignment="-1",col_name="name",colhdr="Name"@},
30738 @{width="1",alignment="-1",col_name="address",colhdr="Address"@}],
30739 body=[@{name="constraint_error",address="0x0000000000613da0"@},
30740 @{name="const.aint_global_e",address="0x0000000000613b00"@}]@}
30743 @subheading Catching Ada Exceptions
30745 The commands describing how to ask @value{GDBN} to stop when a program
30746 raises an exception are described at @ref{Ada Exception GDB/MI
30747 Catchpoint Commands}.
30750 @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
30751 @node GDB/MI Support Commands
30752 @section @sc{gdb/mi} Support Commands
30754 Since new commands and features get regularly added to @sc{gdb/mi},
30755 some commands are available to help front-ends query the debugger
30756 about support for these capabilities. Similarly, it is also possible
30757 to query @value{GDBN} about target support of certain features.
30759 @subheading The @code{-info-gdb-mi-command} Command
30760 @cindex @code{-info-gdb-mi-command}
30761 @findex -info-gdb-mi-command
30763 @subsubheading Synopsis
30766 -info-gdb-mi-command @var{cmd_name}
30769 Query support for the @sc{gdb/mi} command named @var{cmd_name}.
30771 Note that the dash (@code{-}) starting all @sc{gdb/mi} commands
30772 is technically not part of the command name (@pxref{GDB/MI Input
30773 Syntax}), and thus should be omitted in @var{cmd_name}. However,
30774 for ease of use, this command also accepts the form with the leading
30777 @subsubheading @value{GDBN} Command
30779 There is no corresponding @value{GDBN} command.
30781 @subsubheading Result
30783 The result is a tuple. There is currently only one field:
30787 This field is equal to @code{"true"} if the @sc{gdb/mi} command exists,
30788 @code{"false"} otherwise.
30792 @subsubheading Example
30794 Here is an example where the @sc{gdb/mi} command does not exist:
30797 -info-gdb-mi-command unsupported-command
30798 ^done,command=@{exists="false"@}
30802 And here is an example where the @sc{gdb/mi} command is known
30806 -info-gdb-mi-command symbol-list-lines
30807 ^done,command=@{exists="true"@}
30810 @subheading The @code{-list-features} Command
30811 @findex -list-features
30812 @cindex supported @sc{gdb/mi} features, list
30814 Returns a list of particular features of the MI protocol that
30815 this version of gdb implements. A feature can be a command,
30816 or a new field in an output of some command, or even an
30817 important bugfix. While a frontend can sometimes detect presence
30818 of a feature at runtime, it is easier to perform detection at debugger
30821 The command returns a list of strings, with each string naming an
30822 available feature. Each returned string is just a name, it does not
30823 have any internal structure. The list of possible feature names
30829 (gdb) -list-features
30830 ^done,result=["feature1","feature2"]
30833 The current list of features is:
30836 @item frozen-varobjs
30837 Indicates support for the @code{-var-set-frozen} command, as well
30838 as possible presense of the @code{frozen} field in the output
30839 of @code{-varobj-create}.
30840 @item pending-breakpoints
30841 Indicates support for the @option{-f} option to the @code{-break-insert}
30844 Indicates Python scripting support, Python-based
30845 pretty-printing commands, and possible presence of the
30846 @samp{display_hint} field in the output of @code{-var-list-children}
30848 Indicates support for the @code{-thread-info} command.
30849 @item data-read-memory-bytes
30850 Indicates support for the @code{-data-read-memory-bytes} and the
30851 @code{-data-write-memory-bytes} commands.
30852 @item breakpoint-notifications
30853 Indicates that changes to breakpoints and breakpoints created via the
30854 CLI will be announced via async records.
30855 @item ada-task-info
30856 Indicates support for the @code{-ada-task-info} command.
30857 @item language-option
30858 Indicates that all @sc{gdb/mi} commands accept the @option{--language}
30859 option (@pxref{Context management}).
30860 @item info-gdb-mi-command
30861 Indicates support for the @code{-info-gdb-mi-command} command.
30862 @item undefined-command-error-code
30863 Indicates support for the "undefined-command" error code in error result
30864 records, produced when trying to execute an undefined @sc{gdb/mi} command
30865 (@pxref{GDB/MI Result Records}).
30866 @item exec-run-start-option
30867 Indicates that the @code{-exec-run} command supports the @option{--start}
30868 option (@pxref{GDB/MI Program Execution}).
30871 @subheading The @code{-list-target-features} Command
30872 @findex -list-target-features
30874 Returns a list of particular features that are supported by the
30875 target. Those features affect the permitted MI commands, but
30876 unlike the features reported by the @code{-list-features} command, the
30877 features depend on which target GDB is using at the moment. Whenever
30878 a target can change, due to commands such as @code{-target-select},
30879 @code{-target-attach} or @code{-exec-run}, the list of target features
30880 may change, and the frontend should obtain it again.
30884 (gdb) -list-target-features
30885 ^done,result=["async"]
30888 The current list of features is:
30892 Indicates that the target is capable of asynchronous command
30893 execution, which means that @value{GDBN} will accept further commands
30894 while the target is running.
30897 Indicates that the target is capable of reverse execution.
30898 @xref{Reverse Execution}, for more information.
30902 @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
30903 @node GDB/MI Miscellaneous Commands
30904 @section Miscellaneous @sc{gdb/mi} Commands
30906 @c @subheading -gdb-complete
30908 @subheading The @code{-gdb-exit} Command
30911 @subsubheading Synopsis
30917 Exit @value{GDBN} immediately.
30919 @subsubheading @value{GDBN} Command
30921 Approximately corresponds to @samp{quit}.
30923 @subsubheading Example
30933 @subheading The @code{-exec-abort} Command
30934 @findex -exec-abort
30936 @subsubheading Synopsis
30942 Kill the inferior running program.
30944 @subsubheading @value{GDBN} Command
30946 The corresponding @value{GDBN} command is @samp{kill}.
30948 @subsubheading Example
30953 @subheading The @code{-gdb-set} Command
30956 @subsubheading Synopsis
30962 Set an internal @value{GDBN} variable.
30963 @c IS THIS A DOLLAR VARIABLE? OR SOMETHING LIKE ANNOTATE ?????
30965 @subsubheading @value{GDBN} Command
30967 The corresponding @value{GDBN} command is @samp{set}.
30969 @subsubheading Example
30979 @subheading The @code{-gdb-show} Command
30982 @subsubheading Synopsis
30988 Show the current value of a @value{GDBN} variable.
30990 @subsubheading @value{GDBN} Command
30992 The corresponding @value{GDBN} command is @samp{show}.
30994 @subsubheading Example
31003 @c @subheading -gdb-source
31006 @subheading The @code{-gdb-version} Command
31007 @findex -gdb-version
31009 @subsubheading Synopsis
31015 Show version information for @value{GDBN}. Used mostly in testing.
31017 @subsubheading @value{GDBN} Command
31019 The @value{GDBN} equivalent is @samp{show version}. @value{GDBN} by
31020 default shows this information when you start an interactive session.
31022 @subsubheading Example
31024 @c This example modifies the actual output from GDB to avoid overfull
31030 ~Copyright 2000 Free Software Foundation, Inc.
31031 ~GDB is free software, covered by the GNU General Public License, and
31032 ~you are welcome to change it and/or distribute copies of it under
31033 ~ certain conditions.
31034 ~Type "show copying" to see the conditions.
31035 ~There is absolutely no warranty for GDB. Type "show warranty" for
31037 ~This GDB was configured as
31038 "--host=sparc-sun-solaris2.5.1 --target=ppc-eabi".
31043 @subheading The @code{-list-thread-groups} Command
31044 @findex -list-thread-groups
31046 @subheading Synopsis
31049 -list-thread-groups [ --available ] [ --recurse 1 ] [ @var{group} ... ]
31052 Lists thread groups (@pxref{Thread groups}). When a single thread
31053 group is passed as the argument, lists the children of that group.
31054 When several thread group are passed, lists information about those
31055 thread groups. Without any parameters, lists information about all
31056 top-level thread groups.
31058 Normally, thread groups that are being debugged are reported.
31059 With the @samp{--available} option, @value{GDBN} reports thread groups
31060 available on the target.
31062 The output of this command may have either a @samp{threads} result or
31063 a @samp{groups} result. The @samp{thread} result has a list of tuples
31064 as value, with each tuple describing a thread (@pxref{GDB/MI Thread
31065 Information}). The @samp{groups} result has a list of tuples as value,
31066 each tuple describing a thread group. If top-level groups are
31067 requested (that is, no parameter is passed), or when several groups
31068 are passed, the output always has a @samp{groups} result. The format
31069 of the @samp{group} result is described below.
31071 To reduce the number of roundtrips it's possible to list thread groups
31072 together with their children, by passing the @samp{--recurse} option
31073 and the recursion depth. Presently, only recursion depth of 1 is
31074 permitted. If this option is present, then every reported thread group
31075 will also include its children, either as @samp{group} or
31076 @samp{threads} field.
31078 In general, any combination of option and parameters is permitted, with
31079 the following caveats:
31083 When a single thread group is passed, the output will typically
31084 be the @samp{threads} result. Because threads may not contain
31085 anything, the @samp{recurse} option will be ignored.
31088 When the @samp{--available} option is passed, limited information may
31089 be available. In particular, the list of threads of a process might
31090 be inaccessible. Further, specifying specific thread groups might
31091 not give any performance advantage over listing all thread groups.
31092 The frontend should assume that @samp{-list-thread-groups --available}
31093 is always an expensive operation and cache the results.
31097 The @samp{groups} result is a list of tuples, where each tuple may
31098 have the following fields:
31102 Identifier of the thread group. This field is always present.
31103 The identifier is an opaque string; frontends should not try to
31104 convert it to an integer, even though it might look like one.
31107 The type of the thread group. At present, only @samp{process} is a
31111 The target-specific process identifier. This field is only present
31112 for thread groups of type @samp{process} and only if the process exists.
31115 The number of children this thread group has. This field may be
31116 absent for an available thread group.
31119 This field has a list of tuples as value, each tuple describing a
31120 thread. It may be present if the @samp{--recurse} option is
31121 specified, and it's actually possible to obtain the threads.
31124 This field is a list of integers, each identifying a core that one
31125 thread of the group is running on. This field may be absent if
31126 such information is not available.
31129 The name of the executable file that corresponds to this thread group.
31130 The field is only present for thread groups of type @samp{process},
31131 and only if there is a corresponding executable file.
31135 @subheading Example
31139 -list-thread-groups
31140 ^done,groups=[@{id="17",type="process",pid="yyy",num_children="2"@}]
31141 -list-thread-groups 17
31142 ^done,threads=[@{id="2",target-id="Thread 0xb7e14b90 (LWP 21257)",
31143 frame=@{level="0",addr="0xffffe410",func="__kernel_vsyscall",args=[]@},state="running"@},
31144 @{id="1",target-id="Thread 0xb7e156b0 (LWP 21254)",
31145 frame=@{level="0",addr="0x0804891f",func="foo",args=[@{name="i",value="10"@}],
31146 file="/tmp/a.c",fullname="/tmp/a.c",line="158"@},state="running"@}]]
31147 -list-thread-groups --available
31148 ^done,groups=[@{id="17",type="process",pid="yyy",num_children="2",cores=[1,2]@}]
31149 -list-thread-groups --available --recurse 1
31150 ^done,groups=[@{id="17", types="process",pid="yyy",num_children="2",cores=[1,2],
31151 threads=[@{id="1",target-id="Thread 0xb7e14b90",cores=[1]@},
31152 @{id="2",target-id="Thread 0xb7e14b90",cores=[2]@}]@},..]
31153 -list-thread-groups --available --recurse 1 17 18
31154 ^done,groups=[@{id="17", types="process",pid="yyy",num_children="2",cores=[1,2],
31155 threads=[@{id="1",target-id="Thread 0xb7e14b90",cores=[1]@},
31156 @{id="2",target-id="Thread 0xb7e14b90",cores=[2]@}]@},...]
31159 @subheading The @code{-info-os} Command
31162 @subsubheading Synopsis
31165 -info-os [ @var{type} ]
31168 If no argument is supplied, the command returns a table of available
31169 operating-system-specific information types. If one of these types is
31170 supplied as an argument @var{type}, then the command returns a table
31171 of data of that type.
31173 The types of information available depend on the target operating
31176 @subsubheading @value{GDBN} Command
31178 The corresponding @value{GDBN} command is @samp{info os}.
31180 @subsubheading Example
31182 When run on a @sc{gnu}/Linux system, the output will look something
31188 ^done,OSDataTable=@{nr_rows="9",nr_cols="3",
31189 hdr=[@{width="10",alignment="-1",col_name="col0",colhdr="Type"@},
31190 @{width="10",alignment="-1",col_name="col1",colhdr="Description"@},
31191 @{width="10",alignment="-1",col_name="col2",colhdr="Title"@}],
31192 body=[item=@{col0="processes",col1="Listing of all processes",
31193 col2="Processes"@},
31194 item=@{col0="procgroups",col1="Listing of all process groups",
31195 col2="Process groups"@},
31196 item=@{col0="threads",col1="Listing of all threads",
31198 item=@{col0="files",col1="Listing of all file descriptors",
31199 col2="File descriptors"@},
31200 item=@{col0="sockets",col1="Listing of all internet-domain sockets",
31202 item=@{col0="shm",col1="Listing of all shared-memory regions",
31203 col2="Shared-memory regions"@},
31204 item=@{col0="semaphores",col1="Listing of all semaphores",
31205 col2="Semaphores"@},
31206 item=@{col0="msg",col1="Listing of all message queues",
31207 col2="Message queues"@},
31208 item=@{col0="modules",col1="Listing of all loaded kernel modules",
31209 col2="Kernel modules"@}]@}
31212 ^done,OSDataTable=@{nr_rows="190",nr_cols="4",
31213 hdr=[@{width="10",alignment="-1",col_name="col0",colhdr="pid"@},
31214 @{width="10",alignment="-1",col_name="col1",colhdr="user"@},
31215 @{width="10",alignment="-1",col_name="col2",colhdr="command"@},
31216 @{width="10",alignment="-1",col_name="col3",colhdr="cores"@}],
31217 body=[item=@{col0="1",col1="root",col2="/sbin/init",col3="0"@},
31218 item=@{col0="2",col1="root",col2="[kthreadd]",col3="1"@},
31219 item=@{col0="3",col1="root",col2="[ksoftirqd/0]",col3="0"@},
31221 item=@{col0="26446",col1="stan",col2="bash",col3="0"@},
31222 item=@{col0="28152",col1="stan",col2="bash",col3="1"@}]@}
31226 (Note that the MI output here includes a @code{"Title"} column that
31227 does not appear in command-line @code{info os}; this column is useful
31228 for MI clients that want to enumerate the types of data, such as in a
31229 popup menu, but is needless clutter on the command line, and
31230 @code{info os} omits it.)
31232 @subheading The @code{-add-inferior} Command
31233 @findex -add-inferior
31235 @subheading Synopsis
31241 Creates a new inferior (@pxref{Inferiors and Programs}). The created
31242 inferior is not associated with any executable. Such association may
31243 be established with the @samp{-file-exec-and-symbols} command
31244 (@pxref{GDB/MI File Commands}). The command response has a single
31245 field, @samp{inferior}, whose value is the identifier of the
31246 thread group corresponding to the new inferior.
31248 @subheading Example
31253 ^done,inferior="i3"
31256 @subheading The @code{-interpreter-exec} Command
31257 @findex -interpreter-exec
31259 @subheading Synopsis
31262 -interpreter-exec @var{interpreter} @var{command}
31264 @anchor{-interpreter-exec}
31266 Execute the specified @var{command} in the given @var{interpreter}.
31268 @subheading @value{GDBN} Command
31270 The corresponding @value{GDBN} command is @samp{interpreter-exec}.
31272 @subheading Example
31276 -interpreter-exec console "break main"
31277 &"During symbol reading, couldn't parse type; debugger out of date?.\n"
31278 &"During symbol reading, bad structure-type format.\n"
31279 ~"Breakpoint 1 at 0x8074fc6: file ../../src/gdb/main.c, line 743.\n"
31284 @subheading The @code{-inferior-tty-set} Command
31285 @findex -inferior-tty-set
31287 @subheading Synopsis
31290 -inferior-tty-set /dev/pts/1
31293 Set terminal for future runs of the program being debugged.
31295 @subheading @value{GDBN} Command
31297 The corresponding @value{GDBN} command is @samp{set inferior-tty} /dev/pts/1.
31299 @subheading Example
31303 -inferior-tty-set /dev/pts/1
31308 @subheading The @code{-inferior-tty-show} Command
31309 @findex -inferior-tty-show
31311 @subheading Synopsis
31317 Show terminal for future runs of program being debugged.
31319 @subheading @value{GDBN} Command
31321 The corresponding @value{GDBN} command is @samp{show inferior-tty}.
31323 @subheading Example
31327 -inferior-tty-set /dev/pts/1
31331 ^done,inferior_tty_terminal="/dev/pts/1"
31335 @subheading The @code{-enable-timings} Command
31336 @findex -enable-timings
31338 @subheading Synopsis
31341 -enable-timings [yes | no]
31344 Toggle the printing of the wallclock, user and system times for an MI
31345 command as a field in its output. This command is to help frontend
31346 developers optimize the performance of their code. No argument is
31347 equivalent to @samp{yes}.
31349 @subheading @value{GDBN} Command
31353 @subheading Example
31361 ^done,bkpt=@{number="1",type="breakpoint",disp="keep",enabled="y",
31362 addr="0x080484ed",func="main",file="myprog.c",
31363 fullname="/home/nickrob/myprog.c",line="73",thread-groups=["i1"],
31365 time=@{wallclock="0.05185",user="0.00800",system="0.00000"@}
31373 *stopped,reason="breakpoint-hit",disp="keep",bkptno="1",thread-id="0",
31374 frame=@{addr="0x080484ed",func="main",args=[@{name="argc",value="1"@},
31375 @{name="argv",value="0xbfb60364"@}],file="myprog.c",
31376 fullname="/home/nickrob/myprog.c",line="73"@}
31381 @chapter @value{GDBN} Annotations
31383 This chapter describes annotations in @value{GDBN}. Annotations were
31384 designed to interface @value{GDBN} to graphical user interfaces or other
31385 similar programs which want to interact with @value{GDBN} at a
31386 relatively high level.
31388 The annotation mechanism has largely been superseded by @sc{gdb/mi}
31392 This is Edition @value{EDITION}, @value{DATE}.
31396 * Annotations Overview:: What annotations are; the general syntax.
31397 * Server Prefix:: Issuing a command without affecting user state.
31398 * Prompting:: Annotations marking @value{GDBN}'s need for input.
31399 * Errors:: Annotations for error messages.
31400 * Invalidation:: Some annotations describe things now invalid.
31401 * Annotations for Running::
31402 Whether the program is running, how it stopped, etc.
31403 * Source Annotations:: Annotations describing source code.
31406 @node Annotations Overview
31407 @section What is an Annotation?
31408 @cindex annotations
31410 Annotations start with a newline character, two @samp{control-z}
31411 characters, and the name of the annotation. If there is no additional
31412 information associated with this annotation, the name of the annotation
31413 is followed immediately by a newline. If there is additional
31414 information, the name of the annotation is followed by a space, the
31415 additional information, and a newline. The additional information
31416 cannot contain newline characters.
31418 Any output not beginning with a newline and two @samp{control-z}
31419 characters denotes literal output from @value{GDBN}. Currently there is
31420 no need for @value{GDBN} to output a newline followed by two
31421 @samp{control-z} characters, but if there was such a need, the
31422 annotations could be extended with an @samp{escape} annotation which
31423 means those three characters as output.
31425 The annotation @var{level}, which is specified using the
31426 @option{--annotate} command line option (@pxref{Mode Options}), controls
31427 how much information @value{GDBN} prints together with its prompt,
31428 values of expressions, source lines, and other types of output. Level 0
31429 is for no annotations, level 1 is for use when @value{GDBN} is run as a
31430 subprocess of @sc{gnu} Emacs, level 3 is the maximum annotation suitable
31431 for programs that control @value{GDBN}, and level 2 annotations have
31432 been made obsolete (@pxref{Limitations, , Limitations of the Annotation
31433 Interface, annotate, GDB's Obsolete Annotations}).
31436 @kindex set annotate
31437 @item set annotate @var{level}
31438 The @value{GDBN} command @code{set annotate} sets the level of
31439 annotations to the specified @var{level}.
31441 @item show annotate
31442 @kindex show annotate
31443 Show the current annotation level.
31446 This chapter describes level 3 annotations.
31448 A simple example of starting up @value{GDBN} with annotations is:
31451 $ @kbd{gdb --annotate=3}
31453 Copyright 2003 Free Software Foundation, Inc.
31454 GDB is free software, covered by the GNU General Public License,
31455 and you are welcome to change it and/or distribute copies of it
31456 under certain conditions.
31457 Type "show copying" to see the conditions.
31458 There is absolutely no warranty for GDB. Type "show warranty"
31460 This GDB was configured as "i386-pc-linux-gnu"
31471 Here @samp{quit} is input to @value{GDBN}; the rest is output from
31472 @value{GDBN}. The three lines beginning @samp{^Z^Z} (where @samp{^Z}
31473 denotes a @samp{control-z} character) are annotations; the rest is
31474 output from @value{GDBN}.
31476 @node Server Prefix
31477 @section The Server Prefix
31478 @cindex server prefix
31480 If you prefix a command with @samp{server } then it will not affect
31481 the command history, nor will it affect @value{GDBN}'s notion of which
31482 command to repeat if @key{RET} is pressed on a line by itself. This
31483 means that commands can be run behind a user's back by a front-end in
31484 a transparent manner.
31486 The @code{server } prefix does not affect the recording of values into
31487 the value history; to print a value without recording it into the
31488 value history, use the @code{output} command instead of the
31489 @code{print} command.
31491 Using this prefix also disables confirmation requests
31492 (@pxref{confirmation requests}).
31495 @section Annotation for @value{GDBN} Input
31497 @cindex annotations for prompts
31498 When @value{GDBN} prompts for input, it annotates this fact so it is possible
31499 to know when to send output, when the output from a given command is
31502 Different kinds of input each have a different @dfn{input type}. Each
31503 input type has three annotations: a @code{pre-} annotation, which
31504 denotes the beginning of any prompt which is being output, a plain
31505 annotation, which denotes the end of the prompt, and then a @code{post-}
31506 annotation which denotes the end of any echo which may (or may not) be
31507 associated with the input. For example, the @code{prompt} input type
31508 features the following annotations:
31516 The input types are
31519 @findex pre-prompt annotation
31520 @findex prompt annotation
31521 @findex post-prompt annotation
31523 When @value{GDBN} is prompting for a command (the main @value{GDBN} prompt).
31525 @findex pre-commands annotation
31526 @findex commands annotation
31527 @findex post-commands annotation
31529 When @value{GDBN} prompts for a set of commands, like in the @code{commands}
31530 command. The annotations are repeated for each command which is input.
31532 @findex pre-overload-choice annotation
31533 @findex overload-choice annotation
31534 @findex post-overload-choice annotation
31535 @item overload-choice
31536 When @value{GDBN} wants the user to select between various overloaded functions.
31538 @findex pre-query annotation
31539 @findex query annotation
31540 @findex post-query annotation
31542 When @value{GDBN} wants the user to confirm a potentially dangerous operation.
31544 @findex pre-prompt-for-continue annotation
31545 @findex prompt-for-continue annotation
31546 @findex post-prompt-for-continue annotation
31547 @item prompt-for-continue
31548 When @value{GDBN} is asking the user to press return to continue. Note: Don't
31549 expect this to work well; instead use @code{set height 0} to disable
31550 prompting. This is because the counting of lines is buggy in the
31551 presence of annotations.
31556 @cindex annotations for errors, warnings and interrupts
31558 @findex quit annotation
31563 This annotation occurs right before @value{GDBN} responds to an interrupt.
31565 @findex error annotation
31570 This annotation occurs right before @value{GDBN} responds to an error.
31572 Quit and error annotations indicate that any annotations which @value{GDBN} was
31573 in the middle of may end abruptly. For example, if a
31574 @code{value-history-begin} annotation is followed by a @code{error}, one
31575 cannot expect to receive the matching @code{value-history-end}. One
31576 cannot expect not to receive it either, however; an error annotation
31577 does not necessarily mean that @value{GDBN} is immediately returning all the way
31580 @findex error-begin annotation
31581 A quit or error annotation may be preceded by
31587 Any output between that and the quit or error annotation is the error
31590 Warning messages are not yet annotated.
31591 @c If we want to change that, need to fix warning(), type_error(),
31592 @c range_error(), and possibly other places.
31595 @section Invalidation Notices
31597 @cindex annotations for invalidation messages
31598 The following annotations say that certain pieces of state may have
31602 @findex frames-invalid annotation
31603 @item ^Z^Zframes-invalid
31605 The frames (for example, output from the @code{backtrace} command) may
31608 @findex breakpoints-invalid annotation
31609 @item ^Z^Zbreakpoints-invalid
31611 The breakpoints may have changed. For example, the user just added or
31612 deleted a breakpoint.
31615 @node Annotations for Running
31616 @section Running the Program
31617 @cindex annotations for running programs
31619 @findex starting annotation
31620 @findex stopping annotation
31621 When the program starts executing due to a @value{GDBN} command such as
31622 @code{step} or @code{continue},
31628 is output. When the program stops,
31634 is output. Before the @code{stopped} annotation, a variety of
31635 annotations describe how the program stopped.
31638 @findex exited annotation
31639 @item ^Z^Zexited @var{exit-status}
31640 The program exited, and @var{exit-status} is the exit status (zero for
31641 successful exit, otherwise nonzero).
31643 @findex signalled annotation
31644 @findex signal-name annotation
31645 @findex signal-name-end annotation
31646 @findex signal-string annotation
31647 @findex signal-string-end annotation
31648 @item ^Z^Zsignalled
31649 The program exited with a signal. After the @code{^Z^Zsignalled}, the
31650 annotation continues:
31656 ^Z^Zsignal-name-end
31660 ^Z^Zsignal-string-end
31665 where @var{name} is the name of the signal, such as @code{SIGILL} or
31666 @code{SIGSEGV}, and @var{string} is the explanation of the signal, such
31667 as @code{Illegal Instruction} or @code{Segmentation fault}.
31668 @var{intro-text}, @var{middle-text}, and @var{end-text} are for the
31669 user's benefit and have no particular format.
31671 @findex signal annotation
31673 The syntax of this annotation is just like @code{signalled}, but @value{GDBN} is
31674 just saying that the program received the signal, not that it was
31675 terminated with it.
31677 @findex breakpoint annotation
31678 @item ^Z^Zbreakpoint @var{number}
31679 The program hit breakpoint number @var{number}.
31681 @findex watchpoint annotation
31682 @item ^Z^Zwatchpoint @var{number}
31683 The program hit watchpoint number @var{number}.
31686 @node Source Annotations
31687 @section Displaying Source
31688 @cindex annotations for source display
31690 @findex source annotation
31691 The following annotation is used instead of displaying source code:
31694 ^Z^Zsource @var{filename}:@var{line}:@var{character}:@var{middle}:@var{addr}
31697 where @var{filename} is an absolute file name indicating which source
31698 file, @var{line} is the line number within that file (where 1 is the
31699 first line in the file), @var{character} is the character position
31700 within the file (where 0 is the first character in the file) (for most
31701 debug formats this will necessarily point to the beginning of a line),
31702 @var{middle} is @samp{middle} if @var{addr} is in the middle of the
31703 line, or @samp{beg} if @var{addr} is at the beginning of the line, and
31704 @var{addr} is the address in the target program associated with the
31705 source which is being displayed. @var{addr} is in the form @samp{0x}
31706 followed by one or more lowercase hex digits (note that this does not
31707 depend on the language).
31709 @node JIT Interface
31710 @chapter JIT Compilation Interface
31711 @cindex just-in-time compilation
31712 @cindex JIT compilation interface
31714 This chapter documents @value{GDBN}'s @dfn{just-in-time} (JIT) compilation
31715 interface. A JIT compiler is a program or library that generates native
31716 executable code at runtime and executes it, usually in order to achieve good
31717 performance while maintaining platform independence.
31719 Programs that use JIT compilation are normally difficult to debug because
31720 portions of their code are generated at runtime, instead of being loaded from
31721 object files, which is where @value{GDBN} normally finds the program's symbols
31722 and debug information. In order to debug programs that use JIT compilation,
31723 @value{GDBN} has an interface that allows the program to register in-memory
31724 symbol files with @value{GDBN} at runtime.
31726 If you are using @value{GDBN} to debug a program that uses this interface, then
31727 it should work transparently so long as you have not stripped the binary. If
31728 you are developing a JIT compiler, then the interface is documented in the rest
31729 of this chapter. At this time, the only known client of this interface is the
31732 Broadly speaking, the JIT interface mirrors the dynamic loader interface. The
31733 JIT compiler communicates with @value{GDBN} by writing data into a global
31734 variable and calling a fuction at a well-known symbol. When @value{GDBN}
31735 attaches, it reads a linked list of symbol files from the global variable to
31736 find existing code, and puts a breakpoint in the function so that it can find
31737 out about additional code.
31740 * Declarations:: Relevant C struct declarations
31741 * Registering Code:: Steps to register code
31742 * Unregistering Code:: Steps to unregister code
31743 * Custom Debug Info:: Emit debug information in a custom format
31747 @section JIT Declarations
31749 These are the relevant struct declarations that a C program should include to
31750 implement the interface:
31760 struct jit_code_entry
31762 struct jit_code_entry *next_entry;
31763 struct jit_code_entry *prev_entry;
31764 const char *symfile_addr;
31765 uint64_t symfile_size;
31768 struct jit_descriptor
31771 /* This type should be jit_actions_t, but we use uint32_t
31772 to be explicit about the bitwidth. */
31773 uint32_t action_flag;
31774 struct jit_code_entry *relevant_entry;
31775 struct jit_code_entry *first_entry;
31778 /* GDB puts a breakpoint in this function. */
31779 void __attribute__((noinline)) __jit_debug_register_code() @{ @};
31781 /* Make sure to specify the version statically, because the
31782 debugger may check the version before we can set it. */
31783 struct jit_descriptor __jit_debug_descriptor = @{ 1, 0, 0, 0 @};
31786 If the JIT is multi-threaded, then it is important that the JIT synchronize any
31787 modifications to this global data properly, which can easily be done by putting
31788 a global mutex around modifications to these structures.
31790 @node Registering Code
31791 @section Registering Code
31793 To register code with @value{GDBN}, the JIT should follow this protocol:
31797 Generate an object file in memory with symbols and other desired debug
31798 information. The file must include the virtual addresses of the sections.
31801 Create a code entry for the file, which gives the start and size of the symbol
31805 Add it to the linked list in the JIT descriptor.
31808 Point the relevant_entry field of the descriptor at the entry.
31811 Set @code{action_flag} to @code{JIT_REGISTER} and call
31812 @code{__jit_debug_register_code}.
31815 When @value{GDBN} is attached and the breakpoint fires, @value{GDBN} uses the
31816 @code{relevant_entry} pointer so it doesn't have to walk the list looking for
31817 new code. However, the linked list must still be maintained in order to allow
31818 @value{GDBN} to attach to a running process and still find the symbol files.
31820 @node Unregistering Code
31821 @section Unregistering Code
31823 If code is freed, then the JIT should use the following protocol:
31827 Remove the code entry corresponding to the code from the linked list.
31830 Point the @code{relevant_entry} field of the descriptor at the code entry.
31833 Set @code{action_flag} to @code{JIT_UNREGISTER} and call
31834 @code{__jit_debug_register_code}.
31837 If the JIT frees or recompiles code without unregistering it, then @value{GDBN}
31838 and the JIT will leak the memory used for the associated symbol files.
31840 @node Custom Debug Info
31841 @section Custom Debug Info
31842 @cindex custom JIT debug info
31843 @cindex JIT debug info reader
31845 Generating debug information in platform-native file formats (like ELF
31846 or COFF) may be an overkill for JIT compilers; especially if all the
31847 debug info is used for is displaying a meaningful backtrace. The
31848 issue can be resolved by having the JIT writers decide on a debug info
31849 format and also provide a reader that parses the debug info generated
31850 by the JIT compiler. This section gives a brief overview on writing
31851 such a parser. More specific details can be found in the source file
31852 @file{gdb/jit-reader.in}, which is also installed as a header at
31853 @file{@var{includedir}/gdb/jit-reader.h} for easy inclusion.
31855 The reader is implemented as a shared object (so this functionality is
31856 not available on platforms which don't allow loading shared objects at
31857 runtime). Two @value{GDBN} commands, @code{jit-reader-load} and
31858 @code{jit-reader-unload} are provided, to be used to load and unload
31859 the readers from a preconfigured directory. Once loaded, the shared
31860 object is used the parse the debug information emitted by the JIT
31864 * Using JIT Debug Info Readers:: How to use supplied readers correctly
31865 * Writing JIT Debug Info Readers:: Creating a debug-info reader
31868 @node Using JIT Debug Info Readers
31869 @subsection Using JIT Debug Info Readers
31870 @kindex jit-reader-load
31871 @kindex jit-reader-unload
31873 Readers can be loaded and unloaded using the @code{jit-reader-load}
31874 and @code{jit-reader-unload} commands.
31877 @item jit-reader-load @var{reader}
31878 Load the JIT reader named @var{reader}. @var{reader} is a shared
31879 object specified as either an absolute or a relative file name. In
31880 the latter case, @value{GDBN} will try to load the reader from a
31881 pre-configured directory, usually @file{@var{libdir}/gdb/} on a UNIX
31882 system (here @var{libdir} is the system library directory, often
31883 @file{/usr/local/lib}).
31885 Only one reader can be active at a time; trying to load a second
31886 reader when one is already loaded will result in @value{GDBN}
31887 reporting an error. A new JIT reader can be loaded by first unloading
31888 the current one using @code{jit-reader-unload} and then invoking
31889 @code{jit-reader-load}.
31891 @item jit-reader-unload
31892 Unload the currently loaded JIT reader.
31896 @node Writing JIT Debug Info Readers
31897 @subsection Writing JIT Debug Info Readers
31898 @cindex writing JIT debug info readers
31900 As mentioned, a reader is essentially a shared object conforming to a
31901 certain ABI. This ABI is described in @file{jit-reader.h}.
31903 @file{jit-reader.h} defines the structures, macros and functions
31904 required to write a reader. It is installed (along with
31905 @value{GDBN}), in @file{@var{includedir}/gdb} where @var{includedir} is
31906 the system include directory.
31908 Readers need to be released under a GPL compatible license. A reader
31909 can be declared as released under such a license by placing the macro
31910 @code{GDB_DECLARE_GPL_COMPATIBLE_READER} in a source file.
31912 The entry point for readers is the symbol @code{gdb_init_reader},
31913 which is expected to be a function with the prototype
31915 @findex gdb_init_reader
31917 extern struct gdb_reader_funcs *gdb_init_reader (void);
31920 @cindex @code{struct gdb_reader_funcs}
31922 @code{struct gdb_reader_funcs} contains a set of pointers to callback
31923 functions. These functions are executed to read the debug info
31924 generated by the JIT compiler (@code{read}), to unwind stack frames
31925 (@code{unwind}) and to create canonical frame IDs
31926 (@code{get_Frame_id}). It also has a callback that is called when the
31927 reader is being unloaded (@code{destroy}). The struct looks like this
31930 struct gdb_reader_funcs
31932 /* Must be set to GDB_READER_INTERFACE_VERSION. */
31933 int reader_version;
31935 /* For use by the reader. */
31938 gdb_read_debug_info *read;
31939 gdb_unwind_frame *unwind;
31940 gdb_get_frame_id *get_frame_id;
31941 gdb_destroy_reader *destroy;
31945 @cindex @code{struct gdb_symbol_callbacks}
31946 @cindex @code{struct gdb_unwind_callbacks}
31948 The callbacks are provided with another set of callbacks by
31949 @value{GDBN} to do their job. For @code{read}, these callbacks are
31950 passed in a @code{struct gdb_symbol_callbacks} and for @code{unwind}
31951 and @code{get_frame_id}, in a @code{struct gdb_unwind_callbacks}.
31952 @code{struct gdb_symbol_callbacks} has callbacks to create new object
31953 files and new symbol tables inside those object files. @code{struct
31954 gdb_unwind_callbacks} has callbacks to read registers off the current
31955 frame and to write out the values of the registers in the previous
31956 frame. Both have a callback (@code{target_read}) to read bytes off the
31957 target's address space.
31959 @node In-Process Agent
31960 @chapter In-Process Agent
31961 @cindex debugging agent
31962 The traditional debugging model is conceptually low-speed, but works fine,
31963 because most bugs can be reproduced in debugging-mode execution. However,
31964 as multi-core or many-core processors are becoming mainstream, and
31965 multi-threaded programs become more and more popular, there should be more
31966 and more bugs that only manifest themselves at normal-mode execution, for
31967 example, thread races, because debugger's interference with the program's
31968 timing may conceal the bugs. On the other hand, in some applications,
31969 it is not feasible for the debugger to interrupt the program's execution
31970 long enough for the developer to learn anything helpful about its behavior.
31971 If the program's correctness depends on its real-time behavior, delays
31972 introduced by a debugger might cause the program to fail, even when the
31973 code itself is correct. It is useful to be able to observe the program's
31974 behavior without interrupting it.
31976 Therefore, traditional debugging model is too intrusive to reproduce
31977 some bugs. In order to reduce the interference with the program, we can
31978 reduce the number of operations performed by debugger. The
31979 @dfn{In-Process Agent}, a shared library, is running within the same
31980 process with inferior, and is able to perform some debugging operations
31981 itself. As a result, debugger is only involved when necessary, and
31982 performance of debugging can be improved accordingly. Note that
31983 interference with program can be reduced but can't be removed completely,
31984 because the in-process agent will still stop or slow down the program.
31986 The in-process agent can interpret and execute Agent Expressions
31987 (@pxref{Agent Expressions}) during performing debugging operations. The
31988 agent expressions can be used for different purposes, such as collecting
31989 data in tracepoints, and condition evaluation in breakpoints.
31991 @anchor{Control Agent}
31992 You can control whether the in-process agent is used as an aid for
31993 debugging with the following commands:
31996 @kindex set agent on
31998 Causes the in-process agent to perform some operations on behalf of the
31999 debugger. Just which operations requested by the user will be done
32000 by the in-process agent depends on the its capabilities. For example,
32001 if you request to evaluate breakpoint conditions in the in-process agent,
32002 and the in-process agent has such capability as well, then breakpoint
32003 conditions will be evaluated in the in-process agent.
32005 @kindex set agent off
32006 @item set agent off
32007 Disables execution of debugging operations by the in-process agent. All
32008 of the operations will be performed by @value{GDBN}.
32012 Display the current setting of execution of debugging operations by
32013 the in-process agent.
32017 * In-Process Agent Protocol::
32020 @node In-Process Agent Protocol
32021 @section In-Process Agent Protocol
32022 @cindex in-process agent protocol
32024 The in-process agent is able to communicate with both @value{GDBN} and
32025 GDBserver (@pxref{In-Process Agent}). This section documents the protocol
32026 used for communications between @value{GDBN} or GDBserver and the IPA.
32027 In general, @value{GDBN} or GDBserver sends commands
32028 (@pxref{IPA Protocol Commands}) and data to in-process agent, and then
32029 in-process agent replies back with the return result of the command, or
32030 some other information. The data sent to in-process agent is composed
32031 of primitive data types, such as 4-byte or 8-byte type, and composite
32032 types, which are called objects (@pxref{IPA Protocol Objects}).
32035 * IPA Protocol Objects::
32036 * IPA Protocol Commands::
32039 @node IPA Protocol Objects
32040 @subsection IPA Protocol Objects
32041 @cindex ipa protocol objects
32043 The commands sent to and results received from agent may contain some
32044 complex data types called @dfn{objects}.
32046 The in-process agent is running on the same machine with @value{GDBN}
32047 or GDBserver, so it doesn't have to handle as much differences between
32048 two ends as remote protocol (@pxref{Remote Protocol}) tries to handle.
32049 However, there are still some differences of two ends in two processes:
32053 word size. On some 64-bit machines, @value{GDBN} or GDBserver can be
32054 compiled as a 64-bit executable, while in-process agent is a 32-bit one.
32056 ABI. Some machines may have multiple types of ABI, @value{GDBN} or
32057 GDBserver is compiled with one, and in-process agent is compiled with
32061 Here are the IPA Protocol Objects:
32065 agent expression object. It represents an agent expression
32066 (@pxref{Agent Expressions}).
32067 @anchor{agent expression object}
32069 tracepoint action object. It represents a tracepoint action
32070 (@pxref{Tracepoint Actions,,Tracepoint Action Lists}) to collect registers,
32071 memory, static trace data and to evaluate expression.
32072 @anchor{tracepoint action object}
32074 tracepoint object. It represents a tracepoint (@pxref{Tracepoints}).
32075 @anchor{tracepoint object}
32079 The following table describes important attributes of each IPA protocol
32082 @multitable @columnfractions .30 .20 .50
32083 @headitem Name @tab Size @tab Description
32084 @item @emph{agent expression object} @tab @tab
32085 @item length @tab 4 @tab length of bytes code
32086 @item byte code @tab @var{length} @tab contents of byte code
32087 @item @emph{tracepoint action for collecting memory} @tab @tab
32088 @item 'M' @tab 1 @tab type of tracepoint action
32089 @item addr @tab 8 @tab if @var{basereg} is @samp{-1}, @var{addr} is the
32090 address of the lowest byte to collect, otherwise @var{addr} is the offset
32091 of @var{basereg} for memory collecting.
32092 @item len @tab 8 @tab length of memory for collecting
32093 @item basereg @tab 4 @tab the register number containing the starting
32094 memory address for collecting.
32095 @item @emph{tracepoint action for collecting registers} @tab @tab
32096 @item 'R' @tab 1 @tab type of tracepoint action
32097 @item @emph{tracepoint action for collecting static trace data} @tab @tab
32098 @item 'L' @tab 1 @tab type of tracepoint action
32099 @item @emph{tracepoint action for expression evaluation} @tab @tab
32100 @item 'X' @tab 1 @tab type of tracepoint action
32101 @item agent expression @tab length of @tab @ref{agent expression object}
32102 @item @emph{tracepoint object} @tab @tab
32103 @item number @tab 4 @tab number of tracepoint
32104 @item address @tab 8 @tab address of tracepoint inserted on
32105 @item type @tab 4 @tab type of tracepoint
32106 @item enabled @tab 1 @tab enable or disable of tracepoint
32107 @item step_count @tab 8 @tab step
32108 @item pass_count @tab 8 @tab pass
32109 @item numactions @tab 4 @tab number of tracepoint actions
32110 @item hit count @tab 8 @tab hit count
32111 @item trace frame usage @tab 8 @tab trace frame usage
32112 @item compiled_cond @tab 8 @tab compiled condition
32113 @item orig_size @tab 8 @tab orig size
32114 @item condition @tab 4 if condition is NULL otherwise length of
32115 @ref{agent expression object}
32116 @tab zero if condition is NULL, otherwise is
32117 @ref{agent expression object}
32118 @item actions @tab variable
32119 @tab numactions number of @ref{tracepoint action object}
32122 @node IPA Protocol Commands
32123 @subsection IPA Protocol Commands
32124 @cindex ipa protocol commands
32126 The spaces in each command are delimiters to ease reading this commands
32127 specification. They don't exist in real commands.
32131 @item FastTrace:@var{tracepoint_object} @var{gdb_jump_pad_head}
32132 Installs a new fast tracepoint described by @var{tracepoint_object}
32133 (@pxref{tracepoint object}). @var{gdb_jump_pad_head}, 8-byte long, is the
32134 head of @dfn{jumppad}, which is used to jump to data collection routine
32139 @item OK @var{target_address} @var{gdb_jump_pad_head} @var{fjump_size} @var{fjump}
32140 @var{target_address} is address of tracepoint in the inferior.
32141 @var{gdb_jump_pad_head} is updated head of jumppad. Both of
32142 @var{target_address} and @var{gdb_jump_pad_head} are 8-byte long.
32143 @var{fjump} contains a sequence of instructions jump to jumppad entry.
32144 @var{fjump_size}, 4-byte long, is the size of @var{fjump}.
32151 Closes the in-process agent. This command is sent when @value{GDBN} or GDBserver
32152 is about to kill inferiors.
32160 @item probe_marker_at:@var{address}
32161 Asks in-process agent to probe the marker at @var{address}.
32168 @item unprobe_marker_at:@var{address}
32169 Asks in-process agent to unprobe the marker at @var{address}.
32173 @chapter Reporting Bugs in @value{GDBN}
32174 @cindex bugs in @value{GDBN}
32175 @cindex reporting bugs in @value{GDBN}
32177 Your bug reports play an essential role in making @value{GDBN} reliable.
32179 Reporting a bug may help you by bringing a solution to your problem, or it
32180 may not. But in any case the principal function of a bug report is to help
32181 the entire community by making the next version of @value{GDBN} work better. Bug
32182 reports are your contribution to the maintenance of @value{GDBN}.
32184 In order for a bug report to serve its purpose, you must include the
32185 information that enables us to fix the bug.
32188 * Bug Criteria:: Have you found a bug?
32189 * Bug Reporting:: How to report bugs
32193 @section Have You Found a Bug?
32194 @cindex bug criteria
32196 If you are not sure whether you have found a bug, here are some guidelines:
32199 @cindex fatal signal
32200 @cindex debugger crash
32201 @cindex crash of debugger
32203 If the debugger gets a fatal signal, for any input whatever, that is a
32204 @value{GDBN} bug. Reliable debuggers never crash.
32206 @cindex error on valid input
32208 If @value{GDBN} produces an error message for valid input, that is a
32209 bug. (Note that if you're cross debugging, the problem may also be
32210 somewhere in the connection to the target.)
32212 @cindex invalid input
32214 If @value{GDBN} does not produce an error message for invalid input,
32215 that is a bug. However, you should note that your idea of
32216 ``invalid input'' might be our idea of ``an extension'' or ``support
32217 for traditional practice''.
32220 If you are an experienced user of debugging tools, your suggestions
32221 for improvement of @value{GDBN} are welcome in any case.
32224 @node Bug Reporting
32225 @section How to Report Bugs
32226 @cindex bug reports
32227 @cindex @value{GDBN} bugs, reporting
32229 A number of companies and individuals offer support for @sc{gnu} products.
32230 If you obtained @value{GDBN} from a support organization, we recommend you
32231 contact that organization first.
32233 You can find contact information for many support companies and
32234 individuals in the file @file{etc/SERVICE} in the @sc{gnu} Emacs
32236 @c should add a web page ref...
32239 @ifset BUGURL_DEFAULT
32240 In any event, we also recommend that you submit bug reports for
32241 @value{GDBN}. The preferred method is to submit them directly using
32242 @uref{http://www.gnu.org/software/gdb/bugs/, @value{GDBN}'s Bugs web
32243 page}. Alternatively, the @email{bug-gdb@@gnu.org, e-mail gateway} can
32246 @strong{Do not send bug reports to @samp{info-gdb}, or to
32247 @samp{help-gdb}, or to any newsgroups.} Most users of @value{GDBN} do
32248 not want to receive bug reports. Those that do have arranged to receive
32251 The mailing list @samp{bug-gdb} has a newsgroup @samp{gnu.gdb.bug} which
32252 serves as a repeater. The mailing list and the newsgroup carry exactly
32253 the same messages. Often people think of posting bug reports to the
32254 newsgroup instead of mailing them. This appears to work, but it has one
32255 problem which can be crucial: a newsgroup posting often lacks a mail
32256 path back to the sender. Thus, if we need to ask for more information,
32257 we may be unable to reach you. For this reason, it is better to send
32258 bug reports to the mailing list.
32260 @ifclear BUGURL_DEFAULT
32261 In any event, we also recommend that you submit bug reports for
32262 @value{GDBN} to @value{BUGURL}.
32266 The fundamental principle of reporting bugs usefully is this:
32267 @strong{report all the facts}. If you are not sure whether to state a
32268 fact or leave it out, state it!
32270 Often people omit facts because they think they know what causes the
32271 problem and assume that some details do not matter. Thus, you might
32272 assume that the name of the variable you use in an example does not matter.
32273 Well, probably it does not, but one cannot be sure. Perhaps the bug is a
32274 stray memory reference which happens to fetch from the location where that
32275 name is stored in memory; perhaps, if the name were different, the contents
32276 of that location would fool the debugger into doing the right thing despite
32277 the bug. Play it safe and give a specific, complete example. That is the
32278 easiest thing for you to do, and the most helpful.
32280 Keep in mind that the purpose of a bug report is to enable us to fix the
32281 bug. It may be that the bug has been reported previously, but neither
32282 you nor we can know that unless your bug report is complete and
32285 Sometimes people give a few sketchy facts and ask, ``Does this ring a
32286 bell?'' Those bug reports are useless, and we urge everyone to
32287 @emph{refuse to respond to them} except to chide the sender to report
32290 To enable us to fix the bug, you should include all these things:
32294 The version of @value{GDBN}. @value{GDBN} announces it if you start
32295 with no arguments; you can also print it at any time using @code{show
32298 Without this, we will not know whether there is any point in looking for
32299 the bug in the current version of @value{GDBN}.
32302 The type of machine you are using, and the operating system name and
32306 The details of the @value{GDBN} build-time configuration.
32307 @value{GDBN} shows these details if you invoke it with the
32308 @option{--configuration} command-line option, or if you type
32309 @code{show configuration} at @value{GDBN}'s prompt.
32312 What compiler (and its version) was used to compile @value{GDBN}---e.g.@:
32313 ``@value{GCC}--2.8.1''.
32316 What compiler (and its version) was used to compile the program you are
32317 debugging---e.g.@: ``@value{GCC}--2.8.1'', or ``HP92453-01 A.10.32.03 HP
32318 C Compiler''. For @value{NGCC}, you can say @kbd{@value{GCC} --version}
32319 to get this information; for other compilers, see the documentation for
32323 The command arguments you gave the compiler to compile your example and
32324 observe the bug. For example, did you use @samp{-O}? To guarantee
32325 you will not omit something important, list them all. A copy of the
32326 Makefile (or the output from make) is sufficient.
32328 If we were to try to guess the arguments, we would probably guess wrong
32329 and then we might not encounter the bug.
32332 A complete input script, and all necessary source files, that will
32336 A description of what behavior you observe that you believe is
32337 incorrect. For example, ``It gets a fatal signal.''
32339 Of course, if the bug is that @value{GDBN} gets a fatal signal, then we
32340 will certainly notice it. But if the bug is incorrect output, we might
32341 not notice unless it is glaringly wrong. You might as well not give us
32342 a chance to make a mistake.
32344 Even if the problem you experience is a fatal signal, you should still
32345 say so explicitly. Suppose something strange is going on, such as, your
32346 copy of @value{GDBN} is out of synch, or you have encountered a bug in
32347 the C library on your system. (This has happened!) Your copy might
32348 crash and ours would not. If you told us to expect a crash, then when
32349 ours fails to crash, we would know that the bug was not happening for
32350 us. If you had not told us to expect a crash, then we would not be able
32351 to draw any conclusion from our observations.
32354 @cindex recording a session script
32355 To collect all this information, you can use a session recording program
32356 such as @command{script}, which is available on many Unix systems.
32357 Just run your @value{GDBN} session inside @command{script} and then
32358 include the @file{typescript} file with your bug report.
32360 Another way to record a @value{GDBN} session is to run @value{GDBN}
32361 inside Emacs and then save the entire buffer to a file.
32364 If you wish to suggest changes to the @value{GDBN} source, send us context
32365 diffs. If you even discuss something in the @value{GDBN} source, refer to
32366 it by context, not by line number.
32368 The line numbers in our development sources will not match those in your
32369 sources. Your line numbers would convey no useful information to us.
32373 Here are some things that are not necessary:
32377 A description of the envelope of the bug.
32379 Often people who encounter a bug spend a lot of time investigating
32380 which changes to the input file will make the bug go away and which
32381 changes will not affect it.
32383 This is often time consuming and not very useful, because the way we
32384 will find the bug is by running a single example under the debugger
32385 with breakpoints, not by pure deduction from a series of examples.
32386 We recommend that you save your time for something else.
32388 Of course, if you can find a simpler example to report @emph{instead}
32389 of the original one, that is a convenience for us. Errors in the
32390 output will be easier to spot, running under the debugger will take
32391 less time, and so on.
32393 However, simplification is not vital; if you do not want to do this,
32394 report the bug anyway and send us the entire test case you used.
32397 A patch for the bug.
32399 A patch for the bug does help us if it is a good one. But do not omit
32400 the necessary information, such as the test case, on the assumption that
32401 a patch is all we need. We might see problems with your patch and decide
32402 to fix the problem another way, or we might not understand it at all.
32404 Sometimes with a program as complicated as @value{GDBN} it is very hard to
32405 construct an example that will make the program follow a certain path
32406 through the code. If you do not send us the example, we will not be able
32407 to construct one, so we will not be able to verify that the bug is fixed.
32409 And if we cannot understand what bug you are trying to fix, or why your
32410 patch should be an improvement, we will not install it. A test case will
32411 help us to understand.
32414 A guess about what the bug is or what it depends on.
32416 Such guesses are usually wrong. Even we cannot guess right about such
32417 things without first using the debugger to find the facts.
32420 @c The readline documentation is distributed with the readline code
32421 @c and consists of the two following files:
32424 @c Use -I with makeinfo to point to the appropriate directory,
32425 @c environment var TEXINPUTS with TeX.
32426 @ifclear SYSTEM_READLINE
32427 @include rluser.texi
32428 @include hsuser.texi
32432 @appendix In Memoriam
32434 The @value{GDBN} project mourns the loss of the following long-time
32439 Fred was a long-standing contributor to @value{GDBN} (1991-2006), and
32440 to Free Software in general. Outside of @value{GDBN}, he was known in
32441 the Amiga world for his series of Fish Disks, and the GeekGadget project.
32443 @item Michael Snyder
32444 Michael was one of the Global Maintainers of the @value{GDBN} project,
32445 with contributions recorded as early as 1996, until 2011. In addition
32446 to his day to day participation, he was a large driving force behind
32447 adding Reverse Debugging to @value{GDBN}.
32450 Beyond their technical contributions to the project, they were also
32451 enjoyable members of the Free Software Community. We will miss them.
32453 @node Formatting Documentation
32454 @appendix Formatting Documentation
32456 @cindex @value{GDBN} reference card
32457 @cindex reference card
32458 The @value{GDBN} 4 release includes an already-formatted reference card, ready
32459 for printing with PostScript or Ghostscript, in the @file{gdb}
32460 subdirectory of the main source directory@footnote{In
32461 @file{gdb-@value{GDBVN}/gdb/refcard.ps} of the version @value{GDBVN}
32462 release.}. If you can use PostScript or Ghostscript with your printer,
32463 you can print the reference card immediately with @file{refcard.ps}.
32465 The release also includes the source for the reference card. You
32466 can format it, using @TeX{}, by typing:
32472 The @value{GDBN} reference card is designed to print in @dfn{landscape}
32473 mode on US ``letter'' size paper;
32474 that is, on a sheet 11 inches wide by 8.5 inches
32475 high. You will need to specify this form of printing as an option to
32476 your @sc{dvi} output program.
32478 @cindex documentation
32480 All the documentation for @value{GDBN} comes as part of the machine-readable
32481 distribution. The documentation is written in Texinfo format, which is
32482 a documentation system that uses a single source file to produce both
32483 on-line information and a printed manual. You can use one of the Info
32484 formatting commands to create the on-line version of the documentation
32485 and @TeX{} (or @code{texi2roff}) to typeset the printed version.
32487 @value{GDBN} includes an already formatted copy of the on-line Info
32488 version of this manual in the @file{gdb} subdirectory. The main Info
32489 file is @file{gdb-@value{GDBVN}/gdb/gdb.info}, and it refers to
32490 subordinate files matching @samp{gdb.info*} in the same directory. If
32491 necessary, you can print out these files, or read them with any editor;
32492 but they are easier to read using the @code{info} subsystem in @sc{gnu}
32493 Emacs or the standalone @code{info} program, available as part of the
32494 @sc{gnu} Texinfo distribution.
32496 If you want to format these Info files yourself, you need one of the
32497 Info formatting programs, such as @code{texinfo-format-buffer} or
32500 If you have @code{makeinfo} installed, and are in the top level
32501 @value{GDBN} source directory (@file{gdb-@value{GDBVN}}, in the case of
32502 version @value{GDBVN}), you can make the Info file by typing:
32509 If you want to typeset and print copies of this manual, you need @TeX{},
32510 a program to print its @sc{dvi} output files, and @file{texinfo.tex}, the
32511 Texinfo definitions file.
32513 @TeX{} is a typesetting program; it does not print files directly, but
32514 produces output files called @sc{dvi} files. To print a typeset
32515 document, you need a program to print @sc{dvi} files. If your system
32516 has @TeX{} installed, chances are it has such a program. The precise
32517 command to use depends on your system; @kbd{lpr -d} is common; another
32518 (for PostScript devices) is @kbd{dvips}. The @sc{dvi} print command may
32519 require a file name without any extension or a @samp{.dvi} extension.
32521 @TeX{} also requires a macro definitions file called
32522 @file{texinfo.tex}. This file tells @TeX{} how to typeset a document
32523 written in Texinfo format. On its own, @TeX{} cannot either read or
32524 typeset a Texinfo file. @file{texinfo.tex} is distributed with GDB
32525 and is located in the @file{gdb-@var{version-number}/texinfo}
32528 If you have @TeX{} and a @sc{dvi} printer program installed, you can
32529 typeset and print this manual. First switch to the @file{gdb}
32530 subdirectory of the main source directory (for example, to
32531 @file{gdb-@value{GDBVN}/gdb}) and type:
32537 Then give @file{gdb.dvi} to your @sc{dvi} printing program.
32539 @node Installing GDB
32540 @appendix Installing @value{GDBN}
32541 @cindex installation
32544 * Requirements:: Requirements for building @value{GDBN}
32545 * Running Configure:: Invoking the @value{GDBN} @file{configure} script
32546 * Separate Objdir:: Compiling @value{GDBN} in another directory
32547 * Config Names:: Specifying names for hosts and targets
32548 * Configure Options:: Summary of options for configure
32549 * System-wide configuration:: Having a system-wide init file
32553 @section Requirements for Building @value{GDBN}
32554 @cindex building @value{GDBN}, requirements for
32556 Building @value{GDBN} requires various tools and packages to be available.
32557 Other packages will be used only if they are found.
32559 @heading Tools/Packages Necessary for Building @value{GDBN}
32561 @item ISO C90 compiler
32562 @value{GDBN} is written in ISO C90. It should be buildable with any
32563 working C90 compiler, e.g.@: GCC.
32567 @heading Tools/Packages Optional for Building @value{GDBN}
32571 @value{GDBN} can use the Expat XML parsing library. This library may be
32572 included with your operating system distribution; if it is not, you
32573 can get the latest version from @url{http://expat.sourceforge.net}.
32574 The @file{configure} script will search for this library in several
32575 standard locations; if it is installed in an unusual path, you can
32576 use the @option{--with-libexpat-prefix} option to specify its location.
32582 Remote protocol memory maps (@pxref{Memory Map Format})
32584 Target descriptions (@pxref{Target Descriptions})
32586 Remote shared library lists (@xref{Library List Format},
32587 or alternatively @pxref{Library List Format for SVR4 Targets})
32589 MS-Windows shared libraries (@pxref{Shared Libraries})
32591 Traceframe info (@pxref{Traceframe Info Format})
32593 Branch trace (@pxref{Branch Trace Format})
32597 @cindex compressed debug sections
32598 @value{GDBN} will use the @samp{zlib} library, if available, to read
32599 compressed debug sections. Some linkers, such as GNU gold, are capable
32600 of producing binaries with compressed debug sections. If @value{GDBN}
32601 is compiled with @samp{zlib}, it will be able to read the debug
32602 information in such binaries.
32604 The @samp{zlib} library is likely included with your operating system
32605 distribution; if it is not, you can get the latest version from
32606 @url{http://zlib.net}.
32609 @value{GDBN}'s features related to character sets (@pxref{Character
32610 Sets}) require a functioning @code{iconv} implementation. If you are
32611 on a GNU system, then this is provided by the GNU C Library. Some
32612 other systems also provide a working @code{iconv}.
32614 If @value{GDBN} is using the @code{iconv} program which is installed
32615 in a non-standard place, you will need to tell @value{GDBN} where to find it.
32616 This is done with @option{--with-iconv-bin} which specifies the
32617 directory that contains the @code{iconv} program.
32619 On systems without @code{iconv}, you can install GNU Libiconv. If you
32620 have previously installed Libiconv, you can use the
32621 @option{--with-libiconv-prefix} option to configure.
32623 @value{GDBN}'s top-level @file{configure} and @file{Makefile} will
32624 arrange to build Libiconv if a directory named @file{libiconv} appears
32625 in the top-most source directory. If Libiconv is built this way, and
32626 if the operating system does not provide a suitable @code{iconv}
32627 implementation, then the just-built library will automatically be used
32628 by @value{GDBN}. One easy way to set this up is to download GNU
32629 Libiconv, unpack it, and then rename the directory holding the
32630 Libiconv source code to @samp{libiconv}.
32633 @node Running Configure
32634 @section Invoking the @value{GDBN} @file{configure} Script
32635 @cindex configuring @value{GDBN}
32636 @value{GDBN} comes with a @file{configure} script that automates the process
32637 of preparing @value{GDBN} for installation; you can then use @code{make} to
32638 build the @code{gdb} program.
32640 @c irrelevant in info file; it's as current as the code it lives with.
32641 @footnote{If you have a more recent version of @value{GDBN} than @value{GDBVN},
32642 look at the @file{README} file in the sources; we may have improved the
32643 installation procedures since publishing this manual.}
32646 The @value{GDBN} distribution includes all the source code you need for
32647 @value{GDBN} in a single directory, whose name is usually composed by
32648 appending the version number to @samp{gdb}.
32650 For example, the @value{GDBN} version @value{GDBVN} distribution is in the
32651 @file{gdb-@value{GDBVN}} directory. That directory contains:
32654 @item gdb-@value{GDBVN}/configure @r{(and supporting files)}
32655 script for configuring @value{GDBN} and all its supporting libraries
32657 @item gdb-@value{GDBVN}/gdb
32658 the source specific to @value{GDBN} itself
32660 @item gdb-@value{GDBVN}/bfd
32661 source for the Binary File Descriptor library
32663 @item gdb-@value{GDBVN}/include
32664 @sc{gnu} include files
32666 @item gdb-@value{GDBVN}/libiberty
32667 source for the @samp{-liberty} free software library
32669 @item gdb-@value{GDBVN}/opcodes
32670 source for the library of opcode tables and disassemblers
32672 @item gdb-@value{GDBVN}/readline
32673 source for the @sc{gnu} command-line interface
32675 @item gdb-@value{GDBVN}/glob
32676 source for the @sc{gnu} filename pattern-matching subroutine
32678 @item gdb-@value{GDBVN}/mmalloc
32679 source for the @sc{gnu} memory-mapped malloc package
32682 The simplest way to configure and build @value{GDBN} is to run @file{configure}
32683 from the @file{gdb-@var{version-number}} source directory, which in
32684 this example is the @file{gdb-@value{GDBVN}} directory.
32686 First switch to the @file{gdb-@var{version-number}} source directory
32687 if you are not already in it; then run @file{configure}. Pass the
32688 identifier for the platform on which @value{GDBN} will run as an
32694 cd gdb-@value{GDBVN}
32695 ./configure @var{host}
32700 where @var{host} is an identifier such as @samp{sun4} or
32701 @samp{decstation}, that identifies the platform where @value{GDBN} will run.
32702 (You can often leave off @var{host}; @file{configure} tries to guess the
32703 correct value by examining your system.)
32705 Running @samp{configure @var{host}} and then running @code{make} builds the
32706 @file{bfd}, @file{readline}, @file{mmalloc}, and @file{libiberty}
32707 libraries, then @code{gdb} itself. The configured source files, and the
32708 binaries, are left in the corresponding source directories.
32711 @file{configure} is a Bourne-shell (@code{/bin/sh}) script; if your
32712 system does not recognize this automatically when you run a different
32713 shell, you may need to run @code{sh} on it explicitly:
32716 sh configure @var{host}
32719 If you run @file{configure} from a directory that contains source
32720 directories for multiple libraries or programs, such as the
32721 @file{gdb-@value{GDBVN}} source directory for version @value{GDBVN},
32723 creates configuration files for every directory level underneath (unless
32724 you tell it not to, with the @samp{--norecursion} option).
32726 You should run the @file{configure} script from the top directory in the
32727 source tree, the @file{gdb-@var{version-number}} directory. If you run
32728 @file{configure} from one of the subdirectories, you will configure only
32729 that subdirectory. That is usually not what you want. In particular,
32730 if you run the first @file{configure} from the @file{gdb} subdirectory
32731 of the @file{gdb-@var{version-number}} directory, you will omit the
32732 configuration of @file{bfd}, @file{readline}, and other sibling
32733 directories of the @file{gdb} subdirectory. This leads to build errors
32734 about missing include files such as @file{bfd/bfd.h}.
32736 You can install @code{@value{GDBP}} anywhere; it has no hardwired paths.
32737 However, you should make sure that the shell on your path (named by
32738 the @samp{SHELL} environment variable) is publicly readable. Remember
32739 that @value{GDBN} uses the shell to start your program---some systems refuse to
32740 let @value{GDBN} debug child processes whose programs are not readable.
32742 @node Separate Objdir
32743 @section Compiling @value{GDBN} in Another Directory
32745 If you want to run @value{GDBN} versions for several host or target machines,
32746 you need a different @code{gdb} compiled for each combination of
32747 host and target. @file{configure} is designed to make this easy by
32748 allowing you to generate each configuration in a separate subdirectory,
32749 rather than in the source directory. If your @code{make} program
32750 handles the @samp{VPATH} feature (@sc{gnu} @code{make} does), running
32751 @code{make} in each of these directories builds the @code{gdb}
32752 program specified there.
32754 To build @code{gdb} in a separate directory, run @file{configure}
32755 with the @samp{--srcdir} option to specify where to find the source.
32756 (You also need to specify a path to find @file{configure}
32757 itself from your working directory. If the path to @file{configure}
32758 would be the same as the argument to @samp{--srcdir}, you can leave out
32759 the @samp{--srcdir} option; it is assumed.)
32761 For example, with version @value{GDBVN}, you can build @value{GDBN} in a
32762 separate directory for a Sun 4 like this:
32766 cd gdb-@value{GDBVN}
32769 ../gdb-@value{GDBVN}/configure sun4
32774 When @file{configure} builds a configuration using a remote source
32775 directory, it creates a tree for the binaries with the same structure
32776 (and using the same names) as the tree under the source directory. In
32777 the example, you'd find the Sun 4 library @file{libiberty.a} in the
32778 directory @file{gdb-sun4/libiberty}, and @value{GDBN} itself in
32779 @file{gdb-sun4/gdb}.
32781 Make sure that your path to the @file{configure} script has just one
32782 instance of @file{gdb} in it. If your path to @file{configure} looks
32783 like @file{../gdb-@value{GDBVN}/gdb/configure}, you are configuring only
32784 one subdirectory of @value{GDBN}, not the whole package. This leads to
32785 build errors about missing include files such as @file{bfd/bfd.h}.
32787 One popular reason to build several @value{GDBN} configurations in separate
32788 directories is to configure @value{GDBN} for cross-compiling (where
32789 @value{GDBN} runs on one machine---the @dfn{host}---while debugging
32790 programs that run on another machine---the @dfn{target}).
32791 You specify a cross-debugging target by
32792 giving the @samp{--target=@var{target}} option to @file{configure}.
32794 When you run @code{make} to build a program or library, you must run
32795 it in a configured directory---whatever directory you were in when you
32796 called @file{configure} (or one of its subdirectories).
32798 The @code{Makefile} that @file{configure} generates in each source
32799 directory also runs recursively. If you type @code{make} in a source
32800 directory such as @file{gdb-@value{GDBVN}} (or in a separate configured
32801 directory configured with @samp{--srcdir=@var{dirname}/gdb-@value{GDBVN}}), you
32802 will build all the required libraries, and then build GDB.
32804 When you have multiple hosts or targets configured in separate
32805 directories, you can run @code{make} on them in parallel (for example,
32806 if they are NFS-mounted on each of the hosts); they will not interfere
32810 @section Specifying Names for Hosts and Targets
32812 The specifications used for hosts and targets in the @file{configure}
32813 script are based on a three-part naming scheme, but some short predefined
32814 aliases are also supported. The full naming scheme encodes three pieces
32815 of information in the following pattern:
32818 @var{architecture}-@var{vendor}-@var{os}
32821 For example, you can use the alias @code{sun4} as a @var{host} argument,
32822 or as the value for @var{target} in a @code{--target=@var{target}}
32823 option. The equivalent full name is @samp{sparc-sun-sunos4}.
32825 The @file{configure} script accompanying @value{GDBN} does not provide
32826 any query facility to list all supported host and target names or
32827 aliases. @file{configure} calls the Bourne shell script
32828 @code{config.sub} to map abbreviations to full names; you can read the
32829 script, if you wish, or you can use it to test your guesses on
32830 abbreviations---for example:
32833 % sh config.sub i386-linux
32835 % sh config.sub alpha-linux
32836 alpha-unknown-linux-gnu
32837 % sh config.sub hp9k700
32839 % sh config.sub sun4
32840 sparc-sun-sunos4.1.1
32841 % sh config.sub sun3
32842 m68k-sun-sunos4.1.1
32843 % sh config.sub i986v
32844 Invalid configuration `i986v': machine `i986v' not recognized
32848 @code{config.sub} is also distributed in the @value{GDBN} source
32849 directory (@file{gdb-@value{GDBVN}}, for version @value{GDBVN}).
32851 @node Configure Options
32852 @section @file{configure} Options
32854 Here is a summary of the @file{configure} options and arguments that
32855 are most often useful for building @value{GDBN}. @file{configure} also has
32856 several other options not listed here. @inforef{What Configure
32857 Does,,configure.info}, for a full explanation of @file{configure}.
32860 configure @r{[}--help@r{]}
32861 @r{[}--prefix=@var{dir}@r{]}
32862 @r{[}--exec-prefix=@var{dir}@r{]}
32863 @r{[}--srcdir=@var{dirname}@r{]}
32864 @r{[}--norecursion@r{]} @r{[}--rm@r{]}
32865 @r{[}--target=@var{target}@r{]}
32870 You may introduce options with a single @samp{-} rather than
32871 @samp{--} if you prefer; but you may abbreviate option names if you use
32876 Display a quick summary of how to invoke @file{configure}.
32878 @item --prefix=@var{dir}
32879 Configure the source to install programs and files under directory
32882 @item --exec-prefix=@var{dir}
32883 Configure the source to install programs under directory
32886 @c avoid splitting the warning from the explanation:
32888 @item --srcdir=@var{dirname}
32889 @strong{Warning: using this option requires @sc{gnu} @code{make}, or another
32890 @code{make} that implements the @code{VPATH} feature.}@*
32891 Use this option to make configurations in directories separate from the
32892 @value{GDBN} source directories. Among other things, you can use this to
32893 build (or maintain) several configurations simultaneously, in separate
32894 directories. @file{configure} writes configuration-specific files in
32895 the current directory, but arranges for them to use the source in the
32896 directory @var{dirname}. @file{configure} creates directories under
32897 the working directory in parallel to the source directories below
32900 @item --norecursion
32901 Configure only the directory level where @file{configure} is executed; do not
32902 propagate configuration to subdirectories.
32904 @item --target=@var{target}
32905 Configure @value{GDBN} for cross-debugging programs running on the specified
32906 @var{target}. Without this option, @value{GDBN} is configured to debug
32907 programs that run on the same machine (@var{host}) as @value{GDBN} itself.
32909 There is no convenient way to generate a list of all available targets.
32911 @item @var{host} @dots{}
32912 Configure @value{GDBN} to run on the specified @var{host}.
32914 There is no convenient way to generate a list of all available hosts.
32917 There are many other options available as well, but they are generally
32918 needed for special purposes only.
32920 @node System-wide configuration
32921 @section System-wide configuration and settings
32922 @cindex system-wide init file
32924 @value{GDBN} can be configured to have a system-wide init file;
32925 this file will be read and executed at startup (@pxref{Startup, , What
32926 @value{GDBN} does during startup}).
32928 Here is the corresponding configure option:
32931 @item --with-system-gdbinit=@var{file}
32932 Specify that the default location of the system-wide init file is
32936 If @value{GDBN} has been configured with the option @option{--prefix=$prefix},
32937 it may be subject to relocation. Two possible cases:
32941 If the default location of this init file contains @file{$prefix},
32942 it will be subject to relocation. Suppose that the configure options
32943 are @option{--prefix=$prefix --with-system-gdbinit=$prefix/etc/gdbinit};
32944 if @value{GDBN} is moved from @file{$prefix} to @file{$install}, the system
32945 init file is looked for as @file{$install/etc/gdbinit} instead of
32946 @file{$prefix/etc/gdbinit}.
32949 By contrast, if the default location does not contain the prefix,
32950 it will not be relocated. E.g.@: if @value{GDBN} has been configured with
32951 @option{--prefix=/usr/local --with-system-gdbinit=/usr/share/gdb/gdbinit},
32952 then @value{GDBN} will always look for @file{/usr/share/gdb/gdbinit},
32953 wherever @value{GDBN} is installed.
32956 If the configured location of the system-wide init file (as given by the
32957 @option{--with-system-gdbinit} option at configure time) is in the
32958 data-directory (as specified by @option{--with-gdb-datadir} at configure
32959 time) or in one of its subdirectories, then @value{GDBN} will look for the
32960 system-wide init file in the directory specified by the
32961 @option{--data-directory} command-line option.
32962 Note that the system-wide init file is only read once, during @value{GDBN}
32963 initialization. If the data-directory is changed after @value{GDBN} has
32964 started with the @code{set data-directory} command, the file will not be
32968 * System-wide Configuration Scripts:: Installed System-wide Configuration Scripts
32971 @node System-wide Configuration Scripts
32972 @subsection Installed System-wide Configuration Scripts
32973 @cindex system-wide configuration scripts
32975 The @file{system-gdbinit} directory, located inside the data-directory
32976 (as specified by @option{--with-gdb-datadir} at configure time) contains
32977 a number of scripts which can be used as system-wide init files. To
32978 automatically source those scripts at startup, @value{GDBN} should be
32979 configured with @option{--with-system-gdbinit}. Otherwise, any user
32980 should be able to source them by hand as needed.
32982 The following scripts are currently available:
32985 @item @file{elinos.py}
32987 @cindex ELinOS system-wide configuration script
32988 This script is useful when debugging a program on an ELinOS target.
32989 It takes advantage of the environment variables defined in a standard
32990 ELinOS environment in order to determine the location of the system
32991 shared libraries, and then sets the @samp{solib-absolute-prefix}
32992 and @samp{solib-search-path} variables appropriately.
32994 @item @file{wrs-linux.py}
32995 @pindex wrs-linux.py
32996 @cindex Wind River Linux system-wide configuration script
32997 This script is useful when debugging a program on a target running
32998 Wind River Linux. It expects the @env{ENV_PREFIX} to be set to
32999 the host-side sysroot used by the target system.
33003 @node Maintenance Commands
33004 @appendix Maintenance Commands
33005 @cindex maintenance commands
33006 @cindex internal commands
33008 In addition to commands intended for @value{GDBN} users, @value{GDBN}
33009 includes a number of commands intended for @value{GDBN} developers,
33010 that are not documented elsewhere in this manual. These commands are
33011 provided here for reference. (For commands that turn on debugging
33012 messages, see @ref{Debugging Output}.)
33015 @kindex maint agent
33016 @kindex maint agent-eval
33017 @item maint agent @r{[}-at @var{location}@r{,}@r{]} @var{expression}
33018 @itemx maint agent-eval @r{[}-at @var{location}@r{,}@r{]} @var{expression}
33019 Translate the given @var{expression} into remote agent bytecodes.
33020 This command is useful for debugging the Agent Expression mechanism
33021 (@pxref{Agent Expressions}). The @samp{agent} version produces an
33022 expression useful for data collection, such as by tracepoints, while
33023 @samp{maint agent-eval} produces an expression that evaluates directly
33024 to a result. For instance, a collection expression for @code{globa +
33025 globb} will include bytecodes to record four bytes of memory at each
33026 of the addresses of @code{globa} and @code{globb}, while discarding
33027 the result of the addition, while an evaluation expression will do the
33028 addition and return the sum.
33029 If @code{-at} is given, generate remote agent bytecode for @var{location}.
33030 If not, generate remote agent bytecode for current frame PC address.
33032 @kindex maint agent-printf
33033 @item maint agent-printf @var{format},@var{expr},...
33034 Translate the given format string and list of argument expressions
33035 into remote agent bytecodes and display them as a disassembled list.
33036 This command is useful for debugging the agent version of dynamic
33037 printf (@pxref{Dynamic Printf}).
33039 @kindex maint info breakpoints
33040 @item @anchor{maint info breakpoints}maint info breakpoints
33041 Using the same format as @samp{info breakpoints}, display both the
33042 breakpoints you've set explicitly, and those @value{GDBN} is using for
33043 internal purposes. Internal breakpoints are shown with negative
33044 breakpoint numbers. The type column identifies what kind of breakpoint
33049 Normal, explicitly set breakpoint.
33052 Normal, explicitly set watchpoint.
33055 Internal breakpoint, used to handle correctly stepping through
33056 @code{longjmp} calls.
33058 @item longjmp resume
33059 Internal breakpoint at the target of a @code{longjmp}.
33062 Temporary internal breakpoint used by the @value{GDBN} @code{until} command.
33065 Temporary internal breakpoint used by the @value{GDBN} @code{finish} command.
33068 Shared library events.
33072 @kindex maint info bfds
33073 @item maint info bfds
33074 This prints information about each @code{bfd} object that is known to
33075 @value{GDBN}. @xref{Top, , BFD, bfd, The Binary File Descriptor Library}.
33077 @kindex set displaced-stepping
33078 @kindex show displaced-stepping
33079 @cindex displaced stepping support
33080 @cindex out-of-line single-stepping
33081 @item set displaced-stepping
33082 @itemx show displaced-stepping
33083 Control whether or not @value{GDBN} will do @dfn{displaced stepping}
33084 if the target supports it. Displaced stepping is a way to single-step
33085 over breakpoints without removing them from the inferior, by executing
33086 an out-of-line copy of the instruction that was originally at the
33087 breakpoint location. It is also known as out-of-line single-stepping.
33090 @item set displaced-stepping on
33091 If the target architecture supports it, @value{GDBN} will use
33092 displaced stepping to step over breakpoints.
33094 @item set displaced-stepping off
33095 @value{GDBN} will not use displaced stepping to step over breakpoints,
33096 even if such is supported by the target architecture.
33098 @cindex non-stop mode, and @samp{set displaced-stepping}
33099 @item set displaced-stepping auto
33100 This is the default mode. @value{GDBN} will use displaced stepping
33101 only if non-stop mode is active (@pxref{Non-Stop Mode}) and the target
33102 architecture supports displaced stepping.
33105 @kindex maint check-psymtabs
33106 @item maint check-psymtabs
33107 Check the consistency of currently expanded psymtabs versus symtabs.
33108 Use this to check, for example, whether a symbol is in one but not the other.
33110 @kindex maint check-symtabs
33111 @item maint check-symtabs
33112 Check the consistency of currently expanded symtabs.
33114 @kindex maint expand-symtabs
33115 @item maint expand-symtabs [@var{regexp}]
33116 Expand symbol tables.
33117 If @var{regexp} is specified, only expand symbol tables for file
33118 names matching @var{regexp}.
33120 @kindex maint cplus first_component
33121 @item maint cplus first_component @var{name}
33122 Print the first C@t{++} class/namespace component of @var{name}.
33124 @kindex maint cplus namespace
33125 @item maint cplus namespace
33126 Print the list of possible C@t{++} namespaces.
33128 @kindex maint demangle
33129 @item maint demangle @var{name}
33130 Demangle a C@t{++} or Objective-C mangled @var{name}.
33132 @kindex maint deprecate
33133 @kindex maint undeprecate
33134 @cindex deprecated commands
33135 @item maint deprecate @var{command} @r{[}@var{replacement}@r{]}
33136 @itemx maint undeprecate @var{command}
33137 Deprecate or undeprecate the named @var{command}. Deprecated commands
33138 cause @value{GDBN} to issue a warning when you use them. The optional
33139 argument @var{replacement} says which newer command should be used in
33140 favor of the deprecated one; if it is given, @value{GDBN} will mention
33141 the replacement as part of the warning.
33143 @kindex maint dump-me
33144 @item maint dump-me
33145 @cindex @code{SIGQUIT} signal, dump core of @value{GDBN}
33146 Cause a fatal signal in the debugger and force it to dump its core.
33147 This is supported only on systems which support aborting a program
33148 with the @code{SIGQUIT} signal.
33150 @kindex maint internal-error
33151 @kindex maint internal-warning
33152 @item maint internal-error @r{[}@var{message-text}@r{]}
33153 @itemx maint internal-warning @r{[}@var{message-text}@r{]}
33154 Cause @value{GDBN} to call the internal function @code{internal_error}
33155 or @code{internal_warning} and hence behave as though an internal error
33156 or internal warning has been detected. In addition to reporting the
33157 internal problem, these functions give the user the opportunity to
33158 either quit @value{GDBN} or create a core file of the current
33159 @value{GDBN} session.
33161 These commands take an optional parameter @var{message-text} that is
33162 used as the text of the error or warning message.
33164 Here's an example of using @code{internal-error}:
33167 (@value{GDBP}) @kbd{maint internal-error testing, 1, 2}
33168 @dots{}/maint.c:121: internal-error: testing, 1, 2
33169 A problem internal to GDB has been detected. Further
33170 debugging may prove unreliable.
33171 Quit this debugging session? (y or n) @kbd{n}
33172 Create a core file? (y or n) @kbd{n}
33176 @cindex @value{GDBN} internal error
33177 @cindex internal errors, control of @value{GDBN} behavior
33179 @kindex maint set internal-error
33180 @kindex maint show internal-error
33181 @kindex maint set internal-warning
33182 @kindex maint show internal-warning
33183 @item maint set internal-error @var{action} [ask|yes|no]
33184 @itemx maint show internal-error @var{action}
33185 @itemx maint set internal-warning @var{action} [ask|yes|no]
33186 @itemx maint show internal-warning @var{action}
33187 When @value{GDBN} reports an internal problem (error or warning) it
33188 gives the user the opportunity to both quit @value{GDBN} and create a
33189 core file of the current @value{GDBN} session. These commands let you
33190 override the default behaviour for each particular @var{action},
33191 described in the table below.
33195 You can specify that @value{GDBN} should always (yes) or never (no)
33196 quit. The default is to ask the user what to do.
33199 You can specify that @value{GDBN} should always (yes) or never (no)
33200 create a core file. The default is to ask the user what to do.
33203 @kindex maint packet
33204 @item maint packet @var{text}
33205 If @value{GDBN} is talking to an inferior via the serial protocol,
33206 then this command sends the string @var{text} to the inferior, and
33207 displays the response packet. @value{GDBN} supplies the initial
33208 @samp{$} character, the terminating @samp{#} character, and the
33211 @kindex maint print architecture
33212 @item maint print architecture @r{[}@var{file}@r{]}
33213 Print the entire architecture configuration. The optional argument
33214 @var{file} names the file where the output goes.
33216 @kindex maint print c-tdesc
33217 @item maint print c-tdesc
33218 Print the current target description (@pxref{Target Descriptions}) as
33219 a C source file. The created source file can be used in @value{GDBN}
33220 when an XML parser is not available to parse the description.
33222 @kindex maint print dummy-frames
33223 @item maint print dummy-frames
33224 Prints the contents of @value{GDBN}'s internal dummy-frame stack.
33227 (@value{GDBP}) @kbd{b add}
33229 (@value{GDBP}) @kbd{print add(2,3)}
33230 Breakpoint 2, add (a=2, b=3) at @dots{}
33232 The program being debugged stopped while in a function called from GDB.
33234 (@value{GDBP}) @kbd{maint print dummy-frames}
33235 0x1a57c80: pc=0x01014068 fp=0x0200bddc sp=0x0200bdd6
33236 top=0x0200bdd4 id=@{stack=0x200bddc,code=0x101405c@}
33237 call_lo=0x01014000 call_hi=0x01014001
33241 Takes an optional file parameter.
33243 @kindex maint print registers
33244 @kindex maint print raw-registers
33245 @kindex maint print cooked-registers
33246 @kindex maint print register-groups
33247 @kindex maint print remote-registers
33248 @item maint print registers @r{[}@var{file}@r{]}
33249 @itemx maint print raw-registers @r{[}@var{file}@r{]}
33250 @itemx maint print cooked-registers @r{[}@var{file}@r{]}
33251 @itemx maint print register-groups @r{[}@var{file}@r{]}
33252 @itemx maint print remote-registers @r{[}@var{file}@r{]}
33253 Print @value{GDBN}'s internal register data structures.
33255 The command @code{maint print raw-registers} includes the contents of
33256 the raw register cache; the command @code{maint print
33257 cooked-registers} includes the (cooked) value of all registers,
33258 including registers which aren't available on the target nor visible
33259 to user; the command @code{maint print register-groups} includes the
33260 groups that each register is a member of; and the command @code{maint
33261 print remote-registers} includes the remote target's register numbers
33262 and offsets in the `G' packets.
33264 These commands take an optional parameter, a file name to which to
33265 write the information.
33267 @kindex maint print reggroups
33268 @item maint print reggroups @r{[}@var{file}@r{]}
33269 Print @value{GDBN}'s internal register group data structures. The
33270 optional argument @var{file} tells to what file to write the
33273 The register groups info looks like this:
33276 (@value{GDBP}) @kbd{maint print reggroups}
33289 This command forces @value{GDBN} to flush its internal register cache.
33291 @kindex maint print objfiles
33292 @cindex info for known object files
33293 @item maint print objfiles @r{[}@var{regexp}@r{]}
33294 Print a dump of all known object files.
33295 If @var{regexp} is specified, only print object files whose names
33296 match @var{regexp}. For each object file, this command prints its name,
33297 address in memory, and all of its psymtabs and symtabs.
33299 @kindex maint print section-scripts
33300 @cindex info for known .debug_gdb_scripts-loaded scripts
33301 @item maint print section-scripts [@var{regexp}]
33302 Print a dump of scripts specified in the @code{.debug_gdb_section} section.
33303 If @var{regexp} is specified, only print scripts loaded by object files
33304 matching @var{regexp}.
33305 For each script, this command prints its name as specified in the objfile,
33306 and the full path if known.
33307 @xref{dotdebug_gdb_scripts section}.
33309 @kindex maint print statistics
33310 @cindex bcache statistics
33311 @item maint print statistics
33312 This command prints, for each object file in the program, various data
33313 about that object file followed by the byte cache (@dfn{bcache})
33314 statistics for the object file. The objfile data includes the number
33315 of minimal, partial, full, and stabs symbols, the number of types
33316 defined by the objfile, the number of as yet unexpanded psym tables,
33317 the number of line tables and string tables, and the amount of memory
33318 used by the various tables. The bcache statistics include the counts,
33319 sizes, and counts of duplicates of all and unique objects, max,
33320 average, and median entry size, total memory used and its overhead and
33321 savings, and various measures of the hash table size and chain
33324 @kindex maint print target-stack
33325 @cindex target stack description
33326 @item maint print target-stack
33327 A @dfn{target} is an interface between the debugger and a particular
33328 kind of file or process. Targets can be stacked in @dfn{strata},
33329 so that more than one target can potentially respond to a request.
33330 In particular, memory accesses will walk down the stack of targets
33331 until they find a target that is interested in handling that particular
33334 This command prints a short description of each layer that was pushed on
33335 the @dfn{target stack}, starting from the top layer down to the bottom one.
33337 @kindex maint print type
33338 @cindex type chain of a data type
33339 @item maint print type @var{expr}
33340 Print the type chain for a type specified by @var{expr}. The argument
33341 can be either a type name or a symbol. If it is a symbol, the type of
33342 that symbol is described. The type chain produced by this command is
33343 a recursive definition of the data type as stored in @value{GDBN}'s
33344 data structures, including its flags and contained types.
33346 @kindex maint set dwarf2 always-disassemble
33347 @kindex maint show dwarf2 always-disassemble
33348 @item maint set dwarf2 always-disassemble
33349 @item maint show dwarf2 always-disassemble
33350 Control the behavior of @code{info address} when using DWARF debugging
33353 The default is @code{off}, which means that @value{GDBN} should try to
33354 describe a variable's location in an easily readable format. When
33355 @code{on}, @value{GDBN} will instead display the DWARF location
33356 expression in an assembly-like format. Note that some locations are
33357 too complex for @value{GDBN} to describe simply; in this case you will
33358 always see the disassembly form.
33360 Here is an example of the resulting disassembly:
33363 (gdb) info addr argc
33364 Symbol "argc" is a complex DWARF expression:
33368 For more information on these expressions, see
33369 @uref{http://www.dwarfstd.org/, the DWARF standard}.
33371 @kindex maint set dwarf2 max-cache-age
33372 @kindex maint show dwarf2 max-cache-age
33373 @item maint set dwarf2 max-cache-age
33374 @itemx maint show dwarf2 max-cache-age
33375 Control the DWARF 2 compilation unit cache.
33377 @cindex DWARF 2 compilation units cache
33378 In object files with inter-compilation-unit references, such as those
33379 produced by the GCC option @samp{-feliminate-dwarf2-dups}, the DWARF 2
33380 reader needs to frequently refer to previously read compilation units.
33381 This setting controls how long a compilation unit will remain in the
33382 cache if it is not referenced. A higher limit means that cached
33383 compilation units will be stored in memory longer, and more total
33384 memory will be used. Setting it to zero disables caching, which will
33385 slow down @value{GDBN} startup, but reduce memory consumption.
33387 @kindex maint set profile
33388 @kindex maint show profile
33389 @cindex profiling GDB
33390 @item maint set profile
33391 @itemx maint show profile
33392 Control profiling of @value{GDBN}.
33394 Profiling will be disabled until you use the @samp{maint set profile}
33395 command to enable it. When you enable profiling, the system will begin
33396 collecting timing and execution count data; when you disable profiling or
33397 exit @value{GDBN}, the results will be written to a log file. Remember that
33398 if you use profiling, @value{GDBN} will overwrite the profiling log file
33399 (often called @file{gmon.out}). If you have a record of important profiling
33400 data in a @file{gmon.out} file, be sure to move it to a safe location.
33402 Configuring with @samp{--enable-profiling} arranges for @value{GDBN} to be
33403 compiled with the @samp{-pg} compiler option.
33405 @kindex maint set show-debug-regs
33406 @kindex maint show show-debug-regs
33407 @cindex hardware debug registers
33408 @item maint set show-debug-regs
33409 @itemx maint show show-debug-regs
33410 Control whether to show variables that mirror the hardware debug
33411 registers. Use @code{on} to enable, @code{off} to disable. If
33412 enabled, the debug registers values are shown when @value{GDBN} inserts or
33413 removes a hardware breakpoint or watchpoint, and when the inferior
33414 triggers a hardware-assisted breakpoint or watchpoint.
33416 @kindex maint set show-all-tib
33417 @kindex maint show show-all-tib
33418 @item maint set show-all-tib
33419 @itemx maint show show-all-tib
33420 Control whether to show all non zero areas within a 1k block starting
33421 at thread local base, when using the @samp{info w32 thread-information-block}
33424 @kindex maint set per-command
33425 @kindex maint show per-command
33426 @item maint set per-command
33427 @itemx maint show per-command
33428 @cindex resources used by commands
33430 @value{GDBN} can display the resources used by each command.
33431 This is useful in debugging performance problems.
33434 @item maint set per-command space [on|off]
33435 @itemx maint show per-command space
33436 Enable or disable the printing of the memory used by GDB for each command.
33437 If enabled, @value{GDBN} will display how much memory each command
33438 took, following the command's own output.
33439 This can also be requested by invoking @value{GDBN} with the
33440 @option{--statistics} command-line switch (@pxref{Mode Options}).
33442 @item maint set per-command time [on|off]
33443 @itemx maint show per-command time
33444 Enable or disable the printing of the execution time of @value{GDBN}
33446 If enabled, @value{GDBN} will display how much time it
33447 took to execute each command, following the command's own output.
33448 Both CPU time and wallclock time are printed.
33449 Printing both is useful when trying to determine whether the cost is
33450 CPU or, e.g., disk/network latency.
33451 Note that the CPU time printed is for @value{GDBN} only, it does not include
33452 the execution time of the inferior because there's no mechanism currently
33453 to compute how much time was spent by @value{GDBN} and how much time was
33454 spent by the program been debugged.
33455 This can also be requested by invoking @value{GDBN} with the
33456 @option{--statistics} command-line switch (@pxref{Mode Options}).
33458 @item maint set per-command symtab [on|off]
33459 @itemx maint show per-command symtab
33460 Enable or disable the printing of basic symbol table statistics
33462 If enabled, @value{GDBN} will display the following information:
33466 number of symbol tables
33468 number of primary symbol tables
33470 number of blocks in the blockvector
33474 @kindex maint space
33475 @cindex memory used by commands
33476 @item maint space @var{value}
33477 An alias for @code{maint set per-command space}.
33478 A non-zero value enables it, zero disables it.
33481 @cindex time of command execution
33482 @item maint time @var{value}
33483 An alias for @code{maint set per-command time}.
33484 A non-zero value enables it, zero disables it.
33486 @kindex maint translate-address
33487 @item maint translate-address @r{[}@var{section}@r{]} @var{addr}
33488 Find the symbol stored at the location specified by the address
33489 @var{addr} and an optional section name @var{section}. If found,
33490 @value{GDBN} prints the name of the closest symbol and an offset from
33491 the symbol's location to the specified address. This is similar to
33492 the @code{info address} command (@pxref{Symbols}), except that this
33493 command also allows to find symbols in other sections.
33495 If section was not specified, the section in which the symbol was found
33496 is also printed. For dynamically linked executables, the name of
33497 executable or shared library containing the symbol is printed as well.
33501 The following command is useful for non-interactive invocations of
33502 @value{GDBN}, such as in the test suite.
33505 @item set watchdog @var{nsec}
33506 @kindex set watchdog
33507 @cindex watchdog timer
33508 @cindex timeout for commands
33509 Set the maximum number of seconds @value{GDBN} will wait for the
33510 target operation to finish. If this time expires, @value{GDBN}
33511 reports and error and the command is aborted.
33513 @item show watchdog
33514 Show the current setting of the target wait timeout.
33517 @node Remote Protocol
33518 @appendix @value{GDBN} Remote Serial Protocol
33523 * Stop Reply Packets::
33524 * General Query Packets::
33525 * Architecture-Specific Protocol Details::
33526 * Tracepoint Packets::
33527 * Host I/O Packets::
33529 * Notification Packets::
33530 * Remote Non-Stop::
33531 * Packet Acknowledgment::
33533 * File-I/O Remote Protocol Extension::
33534 * Library List Format::
33535 * Library List Format for SVR4 Targets::
33536 * Memory Map Format::
33537 * Thread List Format::
33538 * Traceframe Info Format::
33539 * Branch Trace Format::
33545 There may be occasions when you need to know something about the
33546 protocol---for example, if there is only one serial port to your target
33547 machine, you might want your program to do something special if it
33548 recognizes a packet meant for @value{GDBN}.
33550 In the examples below, @samp{->} and @samp{<-} are used to indicate
33551 transmitted and received data, respectively.
33553 @cindex protocol, @value{GDBN} remote serial
33554 @cindex serial protocol, @value{GDBN} remote
33555 @cindex remote serial protocol
33556 All @value{GDBN} commands and responses (other than acknowledgments
33557 and notifications, see @ref{Notification Packets}) are sent as a
33558 @var{packet}. A @var{packet} is introduced with the character
33559 @samp{$}, the actual @var{packet-data}, and the terminating character
33560 @samp{#} followed by a two-digit @var{checksum}:
33563 @code{$}@var{packet-data}@code{#}@var{checksum}
33567 @cindex checksum, for @value{GDBN} remote
33569 The two-digit @var{checksum} is computed as the modulo 256 sum of all
33570 characters between the leading @samp{$} and the trailing @samp{#} (an
33571 eight bit unsigned checksum).
33573 Implementors should note that prior to @value{GDBN} 5.0 the protocol
33574 specification also included an optional two-digit @var{sequence-id}:
33577 @code{$}@var{sequence-id}@code{:}@var{packet-data}@code{#}@var{checksum}
33580 @cindex sequence-id, for @value{GDBN} remote
33582 That @var{sequence-id} was appended to the acknowledgment. @value{GDBN}
33583 has never output @var{sequence-id}s. Stubs that handle packets added
33584 since @value{GDBN} 5.0 must not accept @var{sequence-id}.
33586 When either the host or the target machine receives a packet, the first
33587 response expected is an acknowledgment: either @samp{+} (to indicate
33588 the package was received correctly) or @samp{-} (to request
33592 -> @code{$}@var{packet-data}@code{#}@var{checksum}
33597 The @samp{+}/@samp{-} acknowledgments can be disabled
33598 once a connection is established.
33599 @xref{Packet Acknowledgment}, for details.
33601 The host (@value{GDBN}) sends @var{command}s, and the target (the
33602 debugging stub incorporated in your program) sends a @var{response}. In
33603 the case of step and continue @var{command}s, the response is only sent
33604 when the operation has completed, and the target has again stopped all
33605 threads in all attached processes. This is the default all-stop mode
33606 behavior, but the remote protocol also supports @value{GDBN}'s non-stop
33607 execution mode; see @ref{Remote Non-Stop}, for details.
33609 @var{packet-data} consists of a sequence of characters with the
33610 exception of @samp{#} and @samp{$} (see @samp{X} packet for additional
33613 @cindex remote protocol, field separator
33614 Fields within the packet should be separated using @samp{,} @samp{;} or
33615 @samp{:}. Except where otherwise noted all numbers are represented in
33616 @sc{hex} with leading zeros suppressed.
33618 Implementors should note that prior to @value{GDBN} 5.0, the character
33619 @samp{:} could not appear as the third character in a packet (as it
33620 would potentially conflict with the @var{sequence-id}).
33622 @cindex remote protocol, binary data
33623 @anchor{Binary Data}
33624 Binary data in most packets is encoded either as two hexadecimal
33625 digits per byte of binary data. This allowed the traditional remote
33626 protocol to work over connections which were only seven-bit clean.
33627 Some packets designed more recently assume an eight-bit clean
33628 connection, and use a more efficient encoding to send and receive
33631 The binary data representation uses @code{7d} (@sc{ascii} @samp{@}})
33632 as an escape character. Any escaped byte is transmitted as the escape
33633 character followed by the original character XORed with @code{0x20}.
33634 For example, the byte @code{0x7d} would be transmitted as the two
33635 bytes @code{0x7d 0x5d}. The bytes @code{0x23} (@sc{ascii} @samp{#}),
33636 @code{0x24} (@sc{ascii} @samp{$}), and @code{0x7d} (@sc{ascii}
33637 @samp{@}}) must always be escaped. Responses sent by the stub
33638 must also escape @code{0x2a} (@sc{ascii} @samp{*}), so that it
33639 is not interpreted as the start of a run-length encoded sequence
33642 Response @var{data} can be run-length encoded to save space.
33643 Run-length encoding replaces runs of identical characters with one
33644 instance of the repeated character, followed by a @samp{*} and a
33645 repeat count. The repeat count is itself sent encoded, to avoid
33646 binary characters in @var{data}: a value of @var{n} is sent as
33647 @code{@var{n}+29}. For a repeat count greater or equal to 3, this
33648 produces a printable @sc{ascii} character, e.g.@: a space (@sc{ascii}
33649 code 32) for a repeat count of 3. (This is because run-length
33650 encoding starts to win for counts 3 or more.) Thus, for example,
33651 @samp{0* } is a run-length encoding of ``0000'': the space character
33652 after @samp{*} means repeat the leading @code{0} @w{@code{32 - 29 =
33655 The printable characters @samp{#} and @samp{$} or with a numeric value
33656 greater than 126 must not be used. Runs of six repeats (@samp{#}) or
33657 seven repeats (@samp{$}) can be expanded using a repeat count of only
33658 five (@samp{"}). For example, @samp{00000000} can be encoded as
33661 The error response returned for some packets includes a two character
33662 error number. That number is not well defined.
33664 @cindex empty response, for unsupported packets
33665 For any @var{command} not supported by the stub, an empty response
33666 (@samp{$#00}) should be returned. That way it is possible to extend the
33667 protocol. A newer @value{GDBN} can tell if a packet is supported based
33670 At a minimum, a stub is required to support the @samp{g} and @samp{G}
33671 commands for register access, and the @samp{m} and @samp{M} commands
33672 for memory access. Stubs that only control single-threaded targets
33673 can implement run control with the @samp{c} (continue), and @samp{s}
33674 (step) commands. Stubs that support multi-threading targets should
33675 support the @samp{vCont} command. All other commands are optional.
33680 The following table provides a complete list of all currently defined
33681 @var{command}s and their corresponding response @var{data}.
33682 @xref{File-I/O Remote Protocol Extension}, for details about the File
33683 I/O extension of the remote protocol.
33685 Each packet's description has a template showing the packet's overall
33686 syntax, followed by an explanation of the packet's meaning. We
33687 include spaces in some of the templates for clarity; these are not
33688 part of the packet's syntax. No @value{GDBN} packet uses spaces to
33689 separate its components. For example, a template like @samp{foo
33690 @var{bar} @var{baz}} describes a packet beginning with the three ASCII
33691 bytes @samp{foo}, followed by a @var{bar}, followed directly by a
33692 @var{baz}. @value{GDBN} does not transmit a space character between the
33693 @samp{foo} and the @var{bar}, or between the @var{bar} and the
33696 @cindex @var{thread-id}, in remote protocol
33697 @anchor{thread-id syntax}
33698 Several packets and replies include a @var{thread-id} field to identify
33699 a thread. Normally these are positive numbers with a target-specific
33700 interpretation, formatted as big-endian hex strings. A @var{thread-id}
33701 can also be a literal @samp{-1} to indicate all threads, or @samp{0} to
33704 In addition, the remote protocol supports a multiprocess feature in
33705 which the @var{thread-id} syntax is extended to optionally include both
33706 process and thread ID fields, as @samp{p@var{pid}.@var{tid}}.
33707 The @var{pid} (process) and @var{tid} (thread) components each have the
33708 format described above: a positive number with target-specific
33709 interpretation formatted as a big-endian hex string, literal @samp{-1}
33710 to indicate all processes or threads (respectively), or @samp{0} to
33711 indicate an arbitrary process or thread. Specifying just a process, as
33712 @samp{p@var{pid}}, is equivalent to @samp{p@var{pid}.-1}. It is an
33713 error to specify all processes but a specific thread, such as
33714 @samp{p-1.@var{tid}}. Note that the @samp{p} prefix is @emph{not} used
33715 for those packets and replies explicitly documented to include a process
33716 ID, rather than a @var{thread-id}.
33718 The multiprocess @var{thread-id} syntax extensions are only used if both
33719 @value{GDBN} and the stub report support for the @samp{multiprocess}
33720 feature using @samp{qSupported}. @xref{multiprocess extensions}, for
33723 Note that all packet forms beginning with an upper- or lower-case
33724 letter, other than those described here, are reserved for future use.
33726 Here are the packet descriptions.
33731 @cindex @samp{!} packet
33732 @anchor{extended mode}
33733 Enable extended mode. In extended mode, the remote server is made
33734 persistent. The @samp{R} packet is used to restart the program being
33740 The remote target both supports and has enabled extended mode.
33744 @cindex @samp{?} packet
33746 Indicate the reason the target halted. The reply is the same as for
33747 step and continue. This packet has a special interpretation when the
33748 target is in non-stop mode; see @ref{Remote Non-Stop}.
33751 @xref{Stop Reply Packets}, for the reply specifications.
33753 @item A @var{arglen},@var{argnum},@var{arg},@dots{}
33754 @cindex @samp{A} packet
33755 Initialized @code{argv[]} array passed into program. @var{arglen}
33756 specifies the number of bytes in the hex encoded byte stream
33757 @var{arg}. See @code{gdbserver} for more details.
33762 The arguments were set.
33768 @cindex @samp{b} packet
33769 (Don't use this packet; its behavior is not well-defined.)
33770 Change the serial line speed to @var{baud}.
33772 JTC: @emph{When does the transport layer state change? When it's
33773 received, or after the ACK is transmitted. In either case, there are
33774 problems if the command or the acknowledgment packet is dropped.}
33776 Stan: @emph{If people really wanted to add something like this, and get
33777 it working for the first time, they ought to modify ser-unix.c to send
33778 some kind of out-of-band message to a specially-setup stub and have the
33779 switch happen "in between" packets, so that from remote protocol's point
33780 of view, nothing actually happened.}
33782 @item B @var{addr},@var{mode}
33783 @cindex @samp{B} packet
33784 Set (@var{mode} is @samp{S}) or clear (@var{mode} is @samp{C}) a
33785 breakpoint at @var{addr}.
33787 Don't use this packet. Use the @samp{Z} and @samp{z} packets instead
33788 (@pxref{insert breakpoint or watchpoint packet}).
33790 @cindex @samp{bc} packet
33793 Backward continue. Execute the target system in reverse. No parameter.
33794 @xref{Reverse Execution}, for more information.
33797 @xref{Stop Reply Packets}, for the reply specifications.
33799 @cindex @samp{bs} packet
33802 Backward single step. Execute one instruction in reverse. No parameter.
33803 @xref{Reverse Execution}, for more information.
33806 @xref{Stop Reply Packets}, for the reply specifications.
33808 @item c @r{[}@var{addr}@r{]}
33809 @cindex @samp{c} packet
33810 Continue. @var{addr} is address to resume. If @var{addr} is omitted,
33811 resume at current address.
33813 This packet is deprecated for multi-threading support. @xref{vCont
33817 @xref{Stop Reply Packets}, for the reply specifications.
33819 @item C @var{sig}@r{[};@var{addr}@r{]}
33820 @cindex @samp{C} packet
33821 Continue with signal @var{sig} (hex signal number). If
33822 @samp{;@var{addr}} is omitted, resume at same address.
33824 This packet is deprecated for multi-threading support. @xref{vCont
33828 @xref{Stop Reply Packets}, for the reply specifications.
33831 @cindex @samp{d} packet
33834 Don't use this packet; instead, define a general set packet
33835 (@pxref{General Query Packets}).
33839 @cindex @samp{D} packet
33840 The first form of the packet is used to detach @value{GDBN} from the
33841 remote system. It is sent to the remote target
33842 before @value{GDBN} disconnects via the @code{detach} command.
33844 The second form, including a process ID, is used when multiprocess
33845 protocol extensions are enabled (@pxref{multiprocess extensions}), to
33846 detach only a specific process. The @var{pid} is specified as a
33847 big-endian hex string.
33857 @item F @var{RC},@var{EE},@var{CF};@var{XX}
33858 @cindex @samp{F} packet
33859 A reply from @value{GDBN} to an @samp{F} packet sent by the target.
33860 This is part of the File-I/O protocol extension. @xref{File-I/O
33861 Remote Protocol Extension}, for the specification.
33864 @anchor{read registers packet}
33865 @cindex @samp{g} packet
33866 Read general registers.
33870 @item @var{XX@dots{}}
33871 Each byte of register data is described by two hex digits. The bytes
33872 with the register are transmitted in target byte order. The size of
33873 each register and their position within the @samp{g} packet are
33874 determined by the @value{GDBN} internal gdbarch functions
33875 @code{DEPRECATED_REGISTER_RAW_SIZE} and @code{gdbarch_register_name}. The
33876 specification of several standard @samp{g} packets is specified below.
33878 When reading registers from a trace frame (@pxref{Analyze Collected
33879 Data,,Using the Collected Data}), the stub may also return a string of
33880 literal @samp{x}'s in place of the register data digits, to indicate
33881 that the corresponding register has not been collected, thus its value
33882 is unavailable. For example, for an architecture with 4 registers of
33883 4 bytes each, the following reply indicates to @value{GDBN} that
33884 registers 0 and 2 have not been collected, while registers 1 and 3
33885 have been collected, and both have zero value:
33889 <- @code{xxxxxxxx00000000xxxxxxxx00000000}
33896 @item G @var{XX@dots{}}
33897 @cindex @samp{G} packet
33898 Write general registers. @xref{read registers packet}, for a
33899 description of the @var{XX@dots{}} data.
33909 @item H @var{op} @var{thread-id}
33910 @cindex @samp{H} packet
33911 Set thread for subsequent operations (@samp{m}, @samp{M}, @samp{g},
33912 @samp{G}, et.al.). @var{op} depends on the operation to be performed:
33913 it should be @samp{c} for step and continue operations (note that this
33914 is deprecated, supporting the @samp{vCont} command is a better
33915 option), @samp{g} for other operations. The thread designator
33916 @var{thread-id} has the format and interpretation described in
33917 @ref{thread-id syntax}.
33928 @c 'H': How restrictive (or permissive) is the thread model. If a
33929 @c thread is selected and stopped, are other threads allowed
33930 @c to continue to execute? As I mentioned above, I think the
33931 @c semantics of each command when a thread is selected must be
33932 @c described. For example:
33934 @c 'g': If the stub supports threads and a specific thread is
33935 @c selected, returns the register block from that thread;
33936 @c otherwise returns current registers.
33938 @c 'G' If the stub supports threads and a specific thread is
33939 @c selected, sets the registers of the register block of
33940 @c that thread; otherwise sets current registers.
33942 @item i @r{[}@var{addr}@r{[},@var{nnn}@r{]]}
33943 @anchor{cycle step packet}
33944 @cindex @samp{i} packet
33945 Step the remote target by a single clock cycle. If @samp{,@var{nnn}} is
33946 present, cycle step @var{nnn} cycles. If @var{addr} is present, cycle
33947 step starting at that address.
33950 @cindex @samp{I} packet
33951 Signal, then cycle step. @xref{step with signal packet}. @xref{cycle
33955 @cindex @samp{k} packet
33958 The exact effect of this packet is not specified.
33960 For a bare-metal target, it may power cycle or reset the target
33961 system. For that reason, the @samp{k} packet has no reply.
33963 For a single-process target, it may kill that process if possible.
33965 A multiple-process target may choose to kill just one process, or all
33966 that are under @value{GDBN}'s control. For more precise control, use
33967 the vKill packet (@pxref{vKill packet}).
33969 If the target system immediately closes the connection in response to
33970 @samp{k}, @value{GDBN} does not consider the lack of packet
33971 acknowledgment to be an error, and assumes the kill was successful.
33973 If connected using @kbd{target extended-remote}, and the target does
33974 not close the connection in response to a kill request, @value{GDBN}
33975 probes the target state as if a new connection was opened
33976 (@pxref{? packet}).
33978 @item m @var{addr},@var{length}
33979 @cindex @samp{m} packet
33980 Read @var{length} bytes of memory starting at address @var{addr}.
33981 Note that @var{addr} may not be aligned to any particular boundary.
33983 The stub need not use any particular size or alignment when gathering
33984 data from memory for the response; even if @var{addr} is word-aligned
33985 and @var{length} is a multiple of the word size, the stub is free to
33986 use byte accesses, or not. For this reason, this packet may not be
33987 suitable for accessing memory-mapped I/O devices.
33988 @cindex alignment of remote memory accesses
33989 @cindex size of remote memory accesses
33990 @cindex memory, alignment and size of remote accesses
33994 @item @var{XX@dots{}}
33995 Memory contents; each byte is transmitted as a two-digit hexadecimal
33996 number. The reply may contain fewer bytes than requested if the
33997 server was able to read only part of the region of memory.
34002 @item M @var{addr},@var{length}:@var{XX@dots{}}
34003 @cindex @samp{M} packet
34004 Write @var{length} bytes of memory starting at address @var{addr}.
34005 @var{XX@dots{}} is the data; each byte is transmitted as a two-digit
34006 hexadecimal number.
34013 for an error (this includes the case where only part of the data was
34018 @cindex @samp{p} packet
34019 Read the value of register @var{n}; @var{n} is in hex.
34020 @xref{read registers packet}, for a description of how the returned
34021 register value is encoded.
34025 @item @var{XX@dots{}}
34026 the register's value
34030 Indicating an unrecognized @var{query}.
34033 @item P @var{n@dots{}}=@var{r@dots{}}
34034 @anchor{write register packet}
34035 @cindex @samp{P} packet
34036 Write register @var{n@dots{}} with value @var{r@dots{}}. The register
34037 number @var{n} is in hexadecimal, and @var{r@dots{}} contains two hex
34038 digits for each byte in the register (target byte order).
34048 @item q @var{name} @var{params}@dots{}
34049 @itemx Q @var{name} @var{params}@dots{}
34050 @cindex @samp{q} packet
34051 @cindex @samp{Q} packet
34052 General query (@samp{q}) and set (@samp{Q}). These packets are
34053 described fully in @ref{General Query Packets}.
34056 @cindex @samp{r} packet
34057 Reset the entire system.
34059 Don't use this packet; use the @samp{R} packet instead.
34062 @cindex @samp{R} packet
34063 Restart the program being debugged. @var{XX}, while needed, is ignored.
34064 This packet is only available in extended mode (@pxref{extended mode}).
34066 The @samp{R} packet has no reply.
34068 @item s @r{[}@var{addr}@r{]}
34069 @cindex @samp{s} packet
34070 Single step. @var{addr} is the address at which to resume. If
34071 @var{addr} is omitted, resume at same address.
34073 This packet is deprecated for multi-threading support. @xref{vCont
34077 @xref{Stop Reply Packets}, for the reply specifications.
34079 @item S @var{sig}@r{[};@var{addr}@r{]}
34080 @anchor{step with signal packet}
34081 @cindex @samp{S} packet
34082 Step with signal. This is analogous to the @samp{C} packet, but
34083 requests a single-step, rather than a normal resumption of execution.
34085 This packet is deprecated for multi-threading support. @xref{vCont
34089 @xref{Stop Reply Packets}, for the reply specifications.
34091 @item t @var{addr}:@var{PP},@var{MM}
34092 @cindex @samp{t} packet
34093 Search backwards starting at address @var{addr} for a match with pattern
34094 @var{PP} and mask @var{MM}. @var{PP} and @var{MM} are 4 bytes.
34095 @var{addr} must be at least 3 digits.
34097 @item T @var{thread-id}
34098 @cindex @samp{T} packet
34099 Find out if the thread @var{thread-id} is alive. @xref{thread-id syntax}.
34104 thread is still alive
34110 Packets starting with @samp{v} are identified by a multi-letter name,
34111 up to the first @samp{;} or @samp{?} (or the end of the packet).
34113 @item vAttach;@var{pid}
34114 @cindex @samp{vAttach} packet
34115 Attach to a new process with the specified process ID @var{pid}.
34116 The process ID is a
34117 hexadecimal integer identifying the process. In all-stop mode, all
34118 threads in the attached process are stopped; in non-stop mode, it may be
34119 attached without being stopped if that is supported by the target.
34121 @c In non-stop mode, on a successful vAttach, the stub should set the
34122 @c current thread to a thread of the newly-attached process. After
34123 @c attaching, GDB queries for the attached process's thread ID with qC.
34124 @c Also note that, from a user perspective, whether or not the
34125 @c target is stopped on attach in non-stop mode depends on whether you
34126 @c use the foreground or background version of the attach command, not
34127 @c on what vAttach does; GDB does the right thing with respect to either
34128 @c stopping or restarting threads.
34130 This packet is only available in extended mode (@pxref{extended mode}).
34136 @item @r{Any stop packet}
34137 for success in all-stop mode (@pxref{Stop Reply Packets})
34139 for success in non-stop mode (@pxref{Remote Non-Stop})
34142 @item vCont@r{[};@var{action}@r{[}:@var{thread-id}@r{]]}@dots{}
34143 @cindex @samp{vCont} packet
34144 @anchor{vCont packet}
34145 Resume the inferior, specifying different actions for each thread.
34146 If an action is specified with no @var{thread-id}, then it is applied to any
34147 threads that don't have a specific action specified; if no default action is
34148 specified then other threads should remain stopped in all-stop mode and
34149 in their current state in non-stop mode.
34150 Specifying multiple
34151 default actions is an error; specifying no actions is also an error.
34152 Thread IDs are specified using the syntax described in @ref{thread-id syntax}.
34154 Currently supported actions are:
34160 Continue with signal @var{sig}. The signal @var{sig} should be two hex digits.
34164 Step with signal @var{sig}. The signal @var{sig} should be two hex digits.
34167 @item r @var{start},@var{end}
34168 Step once, and then keep stepping as long as the thread stops at
34169 addresses between @var{start} (inclusive) and @var{end} (exclusive).
34170 The remote stub reports a stop reply when either the thread goes out
34171 of the range or is stopped due to an unrelated reason, such as hitting
34172 a breakpoint. @xref{range stepping}.
34174 If the range is empty (@var{start} == @var{end}), then the action
34175 becomes equivalent to the @samp{s} action. In other words,
34176 single-step once, and report the stop (even if the stepped instruction
34177 jumps to @var{start}).
34179 (A stop reply may be sent at any point even if the PC is still within
34180 the stepping range; for example, it is valid to implement this packet
34181 in a degenerate way as a single instruction step operation.)
34185 The optional argument @var{addr} normally associated with the
34186 @samp{c}, @samp{C}, @samp{s}, and @samp{S} packets is
34187 not supported in @samp{vCont}.
34189 The @samp{t} action is only relevant in non-stop mode
34190 (@pxref{Remote Non-Stop}) and may be ignored by the stub otherwise.
34191 A stop reply should be generated for any affected thread not already stopped.
34192 When a thread is stopped by means of a @samp{t} action,
34193 the corresponding stop reply should indicate that the thread has stopped with
34194 signal @samp{0}, regardless of whether the target uses some other signal
34195 as an implementation detail.
34197 The stub must support @samp{vCont} if it reports support for
34198 multiprocess extensions (@pxref{multiprocess extensions}). Note that in
34199 this case @samp{vCont} actions can be specified to apply to all threads
34200 in a process by using the @samp{p@var{pid}.-1} form of the
34204 @xref{Stop Reply Packets}, for the reply specifications.
34207 @cindex @samp{vCont?} packet
34208 Request a list of actions supported by the @samp{vCont} packet.
34212 @item vCont@r{[};@var{action}@dots{}@r{]}
34213 The @samp{vCont} packet is supported. Each @var{action} is a supported
34214 command in the @samp{vCont} packet.
34216 The @samp{vCont} packet is not supported.
34219 @item vFile:@var{operation}:@var{parameter}@dots{}
34220 @cindex @samp{vFile} packet
34221 Perform a file operation on the target system. For details,
34222 see @ref{Host I/O Packets}.
34224 @item vFlashErase:@var{addr},@var{length}
34225 @cindex @samp{vFlashErase} packet
34226 Direct the stub to erase @var{length} bytes of flash starting at
34227 @var{addr}. The region may enclose any number of flash blocks, but
34228 its start and end must fall on block boundaries, as indicated by the
34229 flash block size appearing in the memory map (@pxref{Memory Map
34230 Format}). @value{GDBN} groups flash memory programming operations
34231 together, and sends a @samp{vFlashDone} request after each group; the
34232 stub is allowed to delay erase operation until the @samp{vFlashDone}
34233 packet is received.
34243 @item vFlashWrite:@var{addr}:@var{XX@dots{}}
34244 @cindex @samp{vFlashWrite} packet
34245 Direct the stub to write data to flash address @var{addr}. The data
34246 is passed in binary form using the same encoding as for the @samp{X}
34247 packet (@pxref{Binary Data}). The memory ranges specified by
34248 @samp{vFlashWrite} packets preceding a @samp{vFlashDone} packet must
34249 not overlap, and must appear in order of increasing addresses
34250 (although @samp{vFlashErase} packets for higher addresses may already
34251 have been received; the ordering is guaranteed only between
34252 @samp{vFlashWrite} packets). If a packet writes to an address that was
34253 neither erased by a preceding @samp{vFlashErase} packet nor by some other
34254 target-specific method, the results are unpredictable.
34262 for vFlashWrite addressing non-flash memory
34268 @cindex @samp{vFlashDone} packet
34269 Indicate to the stub that flash programming operation is finished.
34270 The stub is permitted to delay or batch the effects of a group of
34271 @samp{vFlashErase} and @samp{vFlashWrite} packets until a
34272 @samp{vFlashDone} packet is received. The contents of the affected
34273 regions of flash memory are unpredictable until the @samp{vFlashDone}
34274 request is completed.
34276 @item vKill;@var{pid}
34277 @cindex @samp{vKill} packet
34278 @anchor{vKill packet}
34279 Kill the process with the specified process ID. @var{pid} is a
34280 hexadecimal integer identifying the process. This packet is used in
34281 preference to @samp{k} when multiprocess protocol extensions are
34282 supported; see @ref{multiprocess extensions}.
34292 @item vRun;@var{filename}@r{[};@var{argument}@r{]}@dots{}
34293 @cindex @samp{vRun} packet
34294 Run the program @var{filename}, passing it each @var{argument} on its
34295 command line. The file and arguments are hex-encoded strings. If
34296 @var{filename} is an empty string, the stub may use a default program
34297 (e.g.@: the last program run). The program is created in the stopped
34300 @c FIXME: What about non-stop mode?
34302 This packet is only available in extended mode (@pxref{extended mode}).
34308 @item @r{Any stop packet}
34309 for success (@pxref{Stop Reply Packets})
34313 @cindex @samp{vStopped} packet
34314 @xref{Notification Packets}.
34316 @item X @var{addr},@var{length}:@var{XX@dots{}}
34318 @cindex @samp{X} packet
34319 Write data to memory, where the data is transmitted in binary.
34320 @var{addr} is address, @var{length} is number of bytes,
34321 @samp{@var{XX}@dots{}} is binary data (@pxref{Binary Data}).
34331 @item z @var{type},@var{addr},@var{kind}
34332 @itemx Z @var{type},@var{addr},@var{kind}
34333 @anchor{insert breakpoint or watchpoint packet}
34334 @cindex @samp{z} packet
34335 @cindex @samp{Z} packets
34336 Insert (@samp{Z}) or remove (@samp{z}) a @var{type} breakpoint or
34337 watchpoint starting at address @var{address} of kind @var{kind}.
34339 Each breakpoint and watchpoint packet @var{type} is documented
34342 @emph{Implementation notes: A remote target shall return an empty string
34343 for an unrecognized breakpoint or watchpoint packet @var{type}. A
34344 remote target shall support either both or neither of a given
34345 @samp{Z@var{type}@dots{}} and @samp{z@var{type}@dots{}} packet pair. To
34346 avoid potential problems with duplicate packets, the operations should
34347 be implemented in an idempotent way.}
34349 @item z0,@var{addr},@var{kind}
34350 @itemx Z0,@var{addr},@var{kind}@r{[};@var{cond_list}@dots{}@r{]}@r{[};cmds:@var{persist},@var{cmd_list}@dots{}@r{]}
34351 @cindex @samp{z0} packet
34352 @cindex @samp{Z0} packet
34353 Insert (@samp{Z0}) or remove (@samp{z0}) a memory breakpoint at address
34354 @var{addr} of type @var{kind}.
34356 A memory breakpoint is implemented by replacing the instruction at
34357 @var{addr} with a software breakpoint or trap instruction. The
34358 @var{kind} is target-specific and typically indicates the size of
34359 the breakpoint in bytes that should be inserted. E.g., the @sc{arm}
34360 and @sc{mips} can insert either a 2 or 4 byte breakpoint. Some
34361 architectures have additional meanings for @var{kind};
34362 @var{cond_list} is an optional list of conditional expressions in bytecode
34363 form that should be evaluated on the target's side. These are the
34364 conditions that should be taken into consideration when deciding if
34365 the breakpoint trigger should be reported back to @var{GDBN}.
34367 The @var{cond_list} parameter is comprised of a series of expressions,
34368 concatenated without separators. Each expression has the following form:
34372 @item X @var{len},@var{expr}
34373 @var{len} is the length of the bytecode expression and @var{expr} is the
34374 actual conditional expression in bytecode form.
34378 The optional @var{cmd_list} parameter introduces commands that may be
34379 run on the target, rather than being reported back to @value{GDBN}.
34380 The parameter starts with a numeric flag @var{persist}; if the flag is
34381 nonzero, then the breakpoint may remain active and the commands
34382 continue to be run even when @value{GDBN} disconnects from the target.
34383 Following this flag is a series of expressions concatenated with no
34384 separators. Each expression has the following form:
34388 @item X @var{len},@var{expr}
34389 @var{len} is the length of the bytecode expression and @var{expr} is the
34390 actual conditional expression in bytecode form.
34394 see @ref{Architecture-Specific Protocol Details}.
34396 @emph{Implementation note: It is possible for a target to copy or move
34397 code that contains memory breakpoints (e.g., when implementing
34398 overlays). The behavior of this packet, in the presence of such a
34399 target, is not defined.}
34411 @item z1,@var{addr},@var{kind}
34412 @itemx Z1,@var{addr},@var{kind}@r{[};@var{cond_list}@dots{}@r{]}
34413 @cindex @samp{z1} packet
34414 @cindex @samp{Z1} packet
34415 Insert (@samp{Z1}) or remove (@samp{z1}) a hardware breakpoint at
34416 address @var{addr}.
34418 A hardware breakpoint is implemented using a mechanism that is not
34419 dependant on being able to modify the target's memory. @var{kind}
34420 and @var{cond_list} have the same meaning as in @samp{Z0} packets.
34422 @emph{Implementation note: A hardware breakpoint is not affected by code
34435 @item z2,@var{addr},@var{kind}
34436 @itemx Z2,@var{addr},@var{kind}
34437 @cindex @samp{z2} packet
34438 @cindex @samp{Z2} packet
34439 Insert (@samp{Z2}) or remove (@samp{z2}) a write watchpoint at @var{addr}.
34440 @var{kind} is interpreted as the number of bytes to watch.
34452 @item z3,@var{addr},@var{kind}
34453 @itemx Z3,@var{addr},@var{kind}
34454 @cindex @samp{z3} packet
34455 @cindex @samp{Z3} packet
34456 Insert (@samp{Z3}) or remove (@samp{z3}) a read watchpoint at @var{addr}.
34457 @var{kind} is interpreted as the number of bytes to watch.
34469 @item z4,@var{addr},@var{kind}
34470 @itemx Z4,@var{addr},@var{kind}
34471 @cindex @samp{z4} packet
34472 @cindex @samp{Z4} packet
34473 Insert (@samp{Z4}) or remove (@samp{z4}) an access watchpoint at @var{addr}.
34474 @var{kind} is interpreted as the number of bytes to watch.
34488 @node Stop Reply Packets
34489 @section Stop Reply Packets
34490 @cindex stop reply packets
34492 The @samp{C}, @samp{c}, @samp{S}, @samp{s}, @samp{vCont},
34493 @samp{vAttach}, @samp{vRun}, @samp{vStopped}, and @samp{?} packets can
34494 receive any of the below as a reply. Except for @samp{?}
34495 and @samp{vStopped}, that reply is only returned
34496 when the target halts. In the below the exact meaning of @dfn{signal
34497 number} is defined by the header @file{include/gdb/signals.h} in the
34498 @value{GDBN} source code.
34500 As in the description of request packets, we include spaces in the
34501 reply templates for clarity; these are not part of the reply packet's
34502 syntax. No @value{GDBN} stop reply packet uses spaces to separate its
34508 The program received signal number @var{AA} (a two-digit hexadecimal
34509 number). This is equivalent to a @samp{T} response with no
34510 @var{n}:@var{r} pairs.
34512 @item T @var{AA} @var{n1}:@var{r1};@var{n2}:@var{r2};@dots{}
34513 @cindex @samp{T} packet reply
34514 The program received signal number @var{AA} (a two-digit hexadecimal
34515 number). This is equivalent to an @samp{S} response, except that the
34516 @samp{@var{n}:@var{r}} pairs can carry values of important registers
34517 and other information directly in the stop reply packet, reducing
34518 round-trip latency. Single-step and breakpoint traps are reported
34519 this way. Each @samp{@var{n}:@var{r}} pair is interpreted as follows:
34523 If @var{n} is a hexadecimal number, it is a register number, and the
34524 corresponding @var{r} gives that register's value. @var{r} is a
34525 series of bytes in target byte order, with each byte given by a
34526 two-digit hex number.
34529 If @var{n} is @samp{thread}, then @var{r} is the @var{thread-id} of
34530 the stopped thread, as specified in @ref{thread-id syntax}.
34533 If @var{n} is @samp{core}, then @var{r} is the hexadecimal number of
34534 the core on which the stop event was detected.
34537 If @var{n} is a recognized @dfn{stop reason}, it describes a more
34538 specific event that stopped the target. The currently defined stop
34539 reasons are listed below. @var{aa} should be @samp{05}, the trap
34540 signal. At most one stop reason should be present.
34543 Otherwise, @value{GDBN} should ignore this @samp{@var{n}:@var{r}} pair
34544 and go on to the next; this allows us to extend the protocol in the
34548 The currently defined stop reasons are:
34554 The packet indicates a watchpoint hit, and @var{r} is the data address, in
34557 @cindex shared library events, remote reply
34559 The packet indicates that the loaded libraries have changed.
34560 @value{GDBN} should use @samp{qXfer:libraries:read} to fetch a new
34561 list of loaded libraries. @var{r} is ignored.
34563 @cindex replay log events, remote reply
34565 The packet indicates that the target cannot continue replaying
34566 logged execution events, because it has reached the end (or the
34567 beginning when executing backward) of the log. The value of @var{r}
34568 will be either @samp{begin} or @samp{end}. @xref{Reverse Execution},
34569 for more information.
34573 @itemx W @var{AA} ; process:@var{pid}
34574 The process exited, and @var{AA} is the exit status. This is only
34575 applicable to certain targets.
34577 The second form of the response, including the process ID of the exited
34578 process, can be used only when @value{GDBN} has reported support for
34579 multiprocess protocol extensions; see @ref{multiprocess extensions}.
34580 The @var{pid} is formatted as a big-endian hex string.
34583 @itemx X @var{AA} ; process:@var{pid}
34584 The process terminated with signal @var{AA}.
34586 The second form of the response, including the process ID of the
34587 terminated process, can be used only when @value{GDBN} has reported
34588 support for multiprocess protocol extensions; see @ref{multiprocess
34589 extensions}. The @var{pid} is formatted as a big-endian hex string.
34591 @item O @var{XX}@dots{}
34592 @samp{@var{XX}@dots{}} is hex encoding of @sc{ascii} data, to be
34593 written as the program's console output. This can happen at any time
34594 while the program is running and the debugger should continue to wait
34595 for @samp{W}, @samp{T}, etc. This reply is not permitted in non-stop mode.
34597 @item F @var{call-id},@var{parameter}@dots{}
34598 @var{call-id} is the identifier which says which host system call should
34599 be called. This is just the name of the function. Translation into the
34600 correct system call is only applicable as it's defined in @value{GDBN}.
34601 @xref{File-I/O Remote Protocol Extension}, for a list of implemented
34604 @samp{@var{parameter}@dots{}} is a list of parameters as defined for
34605 this very system call.
34607 The target replies with this packet when it expects @value{GDBN} to
34608 call a host system call on behalf of the target. @value{GDBN} replies
34609 with an appropriate @samp{F} packet and keeps up waiting for the next
34610 reply packet from the target. The latest @samp{C}, @samp{c}, @samp{S}
34611 or @samp{s} action is expected to be continued. @xref{File-I/O Remote
34612 Protocol Extension}, for more details.
34616 @node General Query Packets
34617 @section General Query Packets
34618 @cindex remote query requests
34620 Packets starting with @samp{q} are @dfn{general query packets};
34621 packets starting with @samp{Q} are @dfn{general set packets}. General
34622 query and set packets are a semi-unified form for retrieving and
34623 sending information to and from the stub.
34625 The initial letter of a query or set packet is followed by a name
34626 indicating what sort of thing the packet applies to. For example,
34627 @value{GDBN} may use a @samp{qSymbol} packet to exchange symbol
34628 definitions with the stub. These packet names follow some
34633 The name must not contain commas, colons or semicolons.
34635 Most @value{GDBN} query and set packets have a leading upper case
34638 The names of custom vendor packets should use a company prefix, in
34639 lower case, followed by a period. For example, packets designed at
34640 the Acme Corporation might begin with @samp{qacme.foo} (for querying
34641 foos) or @samp{Qacme.bar} (for setting bars).
34644 The name of a query or set packet should be separated from any
34645 parameters by a @samp{:}; the parameters themselves should be
34646 separated by @samp{,} or @samp{;}. Stubs must be careful to match the
34647 full packet name, and check for a separator or the end of the packet,
34648 in case two packet names share a common prefix. New packets should not begin
34649 with @samp{qC}, @samp{qP}, or @samp{qL}@footnote{The @samp{qP} and @samp{qL}
34650 packets predate these conventions, and have arguments without any terminator
34651 for the packet name; we suspect they are in widespread use in places that
34652 are difficult to upgrade. The @samp{qC} packet has no arguments, but some
34653 existing stubs (e.g.@: RedBoot) are known to not check for the end of the
34656 Like the descriptions of the other packets, each description here
34657 has a template showing the packet's overall syntax, followed by an
34658 explanation of the packet's meaning. We include spaces in some of the
34659 templates for clarity; these are not part of the packet's syntax. No
34660 @value{GDBN} packet uses spaces to separate its components.
34662 Here are the currently defined query and set packets:
34668 Turn on or off the agent as a helper to perform some debugging operations
34669 delegated from @value{GDBN} (@pxref{Control Agent}).
34671 @item QAllow:@var{op}:@var{val}@dots{}
34672 @cindex @samp{QAllow} packet
34673 Specify which operations @value{GDBN} expects to request of the
34674 target, as a semicolon-separated list of operation name and value
34675 pairs. Possible values for @var{op} include @samp{WriteReg},
34676 @samp{WriteMem}, @samp{InsertBreak}, @samp{InsertTrace},
34677 @samp{InsertFastTrace}, and @samp{Stop}. @var{val} is either 0,
34678 indicating that @value{GDBN} will not request the operation, or 1,
34679 indicating that it may. (The target can then use this to set up its
34680 own internals optimally, for instance if the debugger never expects to
34681 insert breakpoints, it may not need to install its own trap handler.)
34684 @cindex current thread, remote request
34685 @cindex @samp{qC} packet
34686 Return the current thread ID.
34690 @item QC @var{thread-id}
34691 Where @var{thread-id} is a thread ID as documented in
34692 @ref{thread-id syntax}.
34693 @item @r{(anything else)}
34694 Any other reply implies the old thread ID.
34697 @item qCRC:@var{addr},@var{length}
34698 @cindex CRC of memory block, remote request
34699 @cindex @samp{qCRC} packet
34700 Compute the CRC checksum of a block of memory using CRC-32 defined in
34701 IEEE 802.3. The CRC is computed byte at a time, taking the most
34702 significant bit of each byte first. The initial pattern code
34703 @code{0xffffffff} is used to ensure leading zeros affect the CRC.
34705 @emph{Note:} This is the same CRC used in validating separate debug
34706 files (@pxref{Separate Debug Files, , Debugging Information in Separate
34707 Files}). However the algorithm is slightly different. When validating
34708 separate debug files, the CRC is computed taking the @emph{least}
34709 significant bit of each byte first, and the final result is inverted to
34710 detect trailing zeros.
34715 An error (such as memory fault)
34716 @item C @var{crc32}
34717 The specified memory region's checksum is @var{crc32}.
34720 @item QDisableRandomization:@var{value}
34721 @cindex disable address space randomization, remote request
34722 @cindex @samp{QDisableRandomization} packet
34723 Some target operating systems will randomize the virtual address space
34724 of the inferior process as a security feature, but provide a feature
34725 to disable such randomization, e.g.@: to allow for a more deterministic
34726 debugging experience. On such systems, this packet with a @var{value}
34727 of 1 directs the target to disable address space randomization for
34728 processes subsequently started via @samp{vRun} packets, while a packet
34729 with a @var{value} of 0 tells the target to enable address space
34732 This packet is only available in extended mode (@pxref{extended mode}).
34737 The request succeeded.
34740 An error occurred. @var{nn} are hex digits.
34743 An empty reply indicates that @samp{QDisableRandomization} is not supported
34747 This packet is not probed by default; the remote stub must request it,
34748 by supplying an appropriate @samp{qSupported} response (@pxref{qSupported}).
34749 This should only be done on targets that actually support disabling
34750 address space randomization.
34753 @itemx qsThreadInfo
34754 @cindex list active threads, remote request
34755 @cindex @samp{qfThreadInfo} packet
34756 @cindex @samp{qsThreadInfo} packet
34757 Obtain a list of all active thread IDs from the target (OS). Since there
34758 may be too many active threads to fit into one reply packet, this query
34759 works iteratively: it may require more than one query/reply sequence to
34760 obtain the entire list of threads. The first query of the sequence will
34761 be the @samp{qfThreadInfo} query; subsequent queries in the
34762 sequence will be the @samp{qsThreadInfo} query.
34764 NOTE: This packet replaces the @samp{qL} query (see below).
34768 @item m @var{thread-id}
34770 @item m @var{thread-id},@var{thread-id}@dots{}
34771 a comma-separated list of thread IDs
34773 (lower case letter @samp{L}) denotes end of list.
34776 In response to each query, the target will reply with a list of one or
34777 more thread IDs, separated by commas.
34778 @value{GDBN} will respond to each reply with a request for more thread
34779 ids (using the @samp{qs} form of the query), until the target responds
34780 with @samp{l} (lower-case ell, for @dfn{last}).
34781 Refer to @ref{thread-id syntax}, for the format of the @var{thread-id}
34784 @item qGetTLSAddr:@var{thread-id},@var{offset},@var{lm}
34785 @cindex get thread-local storage address, remote request
34786 @cindex @samp{qGetTLSAddr} packet
34787 Fetch the address associated with thread local storage specified
34788 by @var{thread-id}, @var{offset}, and @var{lm}.
34790 @var{thread-id} is the thread ID associated with the
34791 thread for which to fetch the TLS address. @xref{thread-id syntax}.
34793 @var{offset} is the (big endian, hex encoded) offset associated with the
34794 thread local variable. (This offset is obtained from the debug
34795 information associated with the variable.)
34797 @var{lm} is the (big endian, hex encoded) OS/ABI-specific encoding of the
34798 load module associated with the thread local storage. For example,
34799 a @sc{gnu}/Linux system will pass the link map address of the shared
34800 object associated with the thread local storage under consideration.
34801 Other operating environments may choose to represent the load module
34802 differently, so the precise meaning of this parameter will vary.
34806 @item @var{XX}@dots{}
34807 Hex encoded (big endian) bytes representing the address of the thread
34808 local storage requested.
34811 An error occurred. @var{nn} are hex digits.
34814 An empty reply indicates that @samp{qGetTLSAddr} is not supported by the stub.
34817 @item qGetTIBAddr:@var{thread-id}
34818 @cindex get thread information block address
34819 @cindex @samp{qGetTIBAddr} packet
34820 Fetch address of the Windows OS specific Thread Information Block.
34822 @var{thread-id} is the thread ID associated with the thread.
34826 @item @var{XX}@dots{}
34827 Hex encoded (big endian) bytes representing the linear address of the
34828 thread information block.
34831 An error occured. This means that either the thread was not found, or the
34832 address could not be retrieved.
34835 An empty reply indicates that @samp{qGetTIBAddr} is not supported by the stub.
34838 @item qL @var{startflag} @var{threadcount} @var{nextthread}
34839 Obtain thread information from RTOS. Where: @var{startflag} (one hex
34840 digit) is one to indicate the first query and zero to indicate a
34841 subsequent query; @var{threadcount} (two hex digits) is the maximum
34842 number of threads the response packet can contain; and @var{nextthread}
34843 (eight hex digits), for subsequent queries (@var{startflag} is zero), is
34844 returned in the response as @var{argthread}.
34846 Don't use this packet; use the @samp{qfThreadInfo} query instead (see above).
34850 @item qM @var{count} @var{done} @var{argthread} @var{thread}@dots{}
34851 Where: @var{count} (two hex digits) is the number of threads being
34852 returned; @var{done} (one hex digit) is zero to indicate more threads
34853 and one indicates no further threads; @var{argthreadid} (eight hex
34854 digits) is @var{nextthread} from the request packet; @var{thread}@dots{}
34855 is a sequence of thread IDs from the target. @var{threadid} (eight hex
34856 digits). See @code{remote.c:parse_threadlist_response()}.
34860 @cindex section offsets, remote request
34861 @cindex @samp{qOffsets} packet
34862 Get section offsets that the target used when relocating the downloaded
34867 @item Text=@var{xxx};Data=@var{yyy}@r{[};Bss=@var{zzz}@r{]}
34868 Relocate the @code{Text} section by @var{xxx} from its original address.
34869 Relocate the @code{Data} section by @var{yyy} from its original address.
34870 If the object file format provides segment information (e.g.@: @sc{elf}
34871 @samp{PT_LOAD} program headers), @value{GDBN} will relocate entire
34872 segments by the supplied offsets.
34874 @emph{Note: while a @code{Bss} offset may be included in the response,
34875 @value{GDBN} ignores this and instead applies the @code{Data} offset
34876 to the @code{Bss} section.}
34878 @item TextSeg=@var{xxx}@r{[};DataSeg=@var{yyy}@r{]}
34879 Relocate the first segment of the object file, which conventionally
34880 contains program code, to a starting address of @var{xxx}. If
34881 @samp{DataSeg} is specified, relocate the second segment, which
34882 conventionally contains modifiable data, to a starting address of
34883 @var{yyy}. @value{GDBN} will report an error if the object file
34884 does not contain segment information, or does not contain at least
34885 as many segments as mentioned in the reply. Extra segments are
34886 kept at fixed offsets relative to the last relocated segment.
34889 @item qP @var{mode} @var{thread-id}
34890 @cindex thread information, remote request
34891 @cindex @samp{qP} packet
34892 Returns information on @var{thread-id}. Where: @var{mode} is a hex
34893 encoded 32 bit mode; @var{thread-id} is a thread ID
34894 (@pxref{thread-id syntax}).
34896 Don't use this packet; use the @samp{qThreadExtraInfo} query instead
34899 Reply: see @code{remote.c:remote_unpack_thread_info_response()}.
34903 @cindex non-stop mode, remote request
34904 @cindex @samp{QNonStop} packet
34906 Enter non-stop (@samp{QNonStop:1}) or all-stop (@samp{QNonStop:0}) mode.
34907 @xref{Remote Non-Stop}, for more information.
34912 The request succeeded.
34915 An error occurred. @var{nn} are hex digits.
34918 An empty reply indicates that @samp{QNonStop} is not supported by
34922 This packet is not probed by default; the remote stub must request it,
34923 by supplying an appropriate @samp{qSupported} response (@pxref{qSupported}).
34924 Use of this packet is controlled by the @code{set non-stop} command;
34925 @pxref{Non-Stop Mode}.
34927 @item QPassSignals: @var{signal} @r{[};@var{signal}@r{]}@dots{}
34928 @cindex pass signals to inferior, remote request
34929 @cindex @samp{QPassSignals} packet
34930 @anchor{QPassSignals}
34931 Each listed @var{signal} should be passed directly to the inferior process.
34932 Signals are numbered identically to continue packets and stop replies
34933 (@pxref{Stop Reply Packets}). Each @var{signal} list item should be
34934 strictly greater than the previous item. These signals do not need to stop
34935 the inferior, or be reported to @value{GDBN}. All other signals should be
34936 reported to @value{GDBN}. Multiple @samp{QPassSignals} packets do not
34937 combine; any earlier @samp{QPassSignals} list is completely replaced by the
34938 new list. This packet improves performance when using @samp{handle
34939 @var{signal} nostop noprint pass}.
34944 The request succeeded.
34947 An error occurred. @var{nn} are hex digits.
34950 An empty reply indicates that @samp{QPassSignals} is not supported by
34954 Use of this packet is controlled by the @code{set remote pass-signals}
34955 command (@pxref{Remote Configuration, set remote pass-signals}).
34956 This packet is not probed by default; the remote stub must request it,
34957 by supplying an appropriate @samp{qSupported} response (@pxref{qSupported}).
34959 @item QProgramSignals: @var{signal} @r{[};@var{signal}@r{]}@dots{}
34960 @cindex signals the inferior may see, remote request
34961 @cindex @samp{QProgramSignals} packet
34962 @anchor{QProgramSignals}
34963 Each listed @var{signal} may be delivered to the inferior process.
34964 Others should be silently discarded.
34966 In some cases, the remote stub may need to decide whether to deliver a
34967 signal to the program or not without @value{GDBN} involvement. One
34968 example of that is while detaching --- the program's threads may have
34969 stopped for signals that haven't yet had a chance of being reported to
34970 @value{GDBN}, and so the remote stub can use the signal list specified
34971 by this packet to know whether to deliver or ignore those pending
34974 This does not influence whether to deliver a signal as requested by a
34975 resumption packet (@pxref{vCont packet}).
34977 Signals are numbered identically to continue packets and stop replies
34978 (@pxref{Stop Reply Packets}). Each @var{signal} list item should be
34979 strictly greater than the previous item. Multiple
34980 @samp{QProgramSignals} packets do not combine; any earlier
34981 @samp{QProgramSignals} list is completely replaced by the new list.
34986 The request succeeded.
34989 An error occurred. @var{nn} are hex digits.
34992 An empty reply indicates that @samp{QProgramSignals} is not supported
34996 Use of this packet is controlled by the @code{set remote program-signals}
34997 command (@pxref{Remote Configuration, set remote program-signals}).
34998 This packet is not probed by default; the remote stub must request it,
34999 by supplying an appropriate @samp{qSupported} response (@pxref{qSupported}).
35001 @item qRcmd,@var{command}
35002 @cindex execute remote command, remote request
35003 @cindex @samp{qRcmd} packet
35004 @var{command} (hex encoded) is passed to the local interpreter for
35005 execution. Invalid commands should be reported using the output
35006 string. Before the final result packet, the target may also respond
35007 with a number of intermediate @samp{O@var{output}} console output
35008 packets. @emph{Implementors should note that providing access to a
35009 stubs's interpreter may have security implications}.
35014 A command response with no output.
35016 A command response with the hex encoded output string @var{OUTPUT}.
35018 Indicate a badly formed request.
35020 An empty reply indicates that @samp{qRcmd} is not recognized.
35023 (Note that the @code{qRcmd} packet's name is separated from the
35024 command by a @samp{,}, not a @samp{:}, contrary to the naming
35025 conventions above. Please don't use this packet as a model for new
35028 @item qSearch:memory:@var{address};@var{length};@var{search-pattern}
35029 @cindex searching memory, in remote debugging
35031 @cindex @samp{qSearch:memory} packet
35033 @cindex @samp{qSearch memory} packet
35034 @anchor{qSearch memory}
35035 Search @var{length} bytes at @var{address} for @var{search-pattern}.
35036 @var{address} and @var{length} are encoded in hex.
35037 @var{search-pattern} is a sequence of bytes, hex encoded.
35042 The pattern was not found.
35044 The pattern was found at @var{address}.
35046 A badly formed request or an error was encountered while searching memory.
35048 An empty reply indicates that @samp{qSearch:memory} is not recognized.
35051 @item QStartNoAckMode
35052 @cindex @samp{QStartNoAckMode} packet
35053 @anchor{QStartNoAckMode}
35054 Request that the remote stub disable the normal @samp{+}/@samp{-}
35055 protocol acknowledgments (@pxref{Packet Acknowledgment}).
35060 The stub has switched to no-acknowledgment mode.
35061 @value{GDBN} acknowledges this reponse,
35062 but neither the stub nor @value{GDBN} shall send or expect further
35063 @samp{+}/@samp{-} acknowledgments in the current connection.
35065 An empty reply indicates that the stub does not support no-acknowledgment mode.
35068 @item qSupported @r{[}:@var{gdbfeature} @r{[};@var{gdbfeature}@r{]}@dots{} @r{]}
35069 @cindex supported packets, remote query
35070 @cindex features of the remote protocol
35071 @cindex @samp{qSupported} packet
35072 @anchor{qSupported}
35073 Tell the remote stub about features supported by @value{GDBN}, and
35074 query the stub for features it supports. This packet allows
35075 @value{GDBN} and the remote stub to take advantage of each others'
35076 features. @samp{qSupported} also consolidates multiple feature probes
35077 at startup, to improve @value{GDBN} performance---a single larger
35078 packet performs better than multiple smaller probe packets on
35079 high-latency links. Some features may enable behavior which must not
35080 be on by default, e.g.@: because it would confuse older clients or
35081 stubs. Other features may describe packets which could be
35082 automatically probed for, but are not. These features must be
35083 reported before @value{GDBN} will use them. This ``default
35084 unsupported'' behavior is not appropriate for all packets, but it
35085 helps to keep the initial connection time under control with new
35086 versions of @value{GDBN} which support increasing numbers of packets.
35090 @item @var{stubfeature} @r{[};@var{stubfeature}@r{]}@dots{}
35091 The stub supports or does not support each returned @var{stubfeature},
35092 depending on the form of each @var{stubfeature} (see below for the
35095 An empty reply indicates that @samp{qSupported} is not recognized,
35096 or that no features needed to be reported to @value{GDBN}.
35099 The allowed forms for each feature (either a @var{gdbfeature} in the
35100 @samp{qSupported} packet, or a @var{stubfeature} in the response)
35104 @item @var{name}=@var{value}
35105 The remote protocol feature @var{name} is supported, and associated
35106 with the specified @var{value}. The format of @var{value} depends
35107 on the feature, but it must not include a semicolon.
35109 The remote protocol feature @var{name} is supported, and does not
35110 need an associated value.
35112 The remote protocol feature @var{name} is not supported.
35114 The remote protocol feature @var{name} may be supported, and
35115 @value{GDBN} should auto-detect support in some other way when it is
35116 needed. This form will not be used for @var{gdbfeature} notifications,
35117 but may be used for @var{stubfeature} responses.
35120 Whenever the stub receives a @samp{qSupported} request, the
35121 supplied set of @value{GDBN} features should override any previous
35122 request. This allows @value{GDBN} to put the stub in a known
35123 state, even if the stub had previously been communicating with
35124 a different version of @value{GDBN}.
35126 The following values of @var{gdbfeature} (for the packet sent by @value{GDBN})
35131 This feature indicates whether @value{GDBN} supports multiprocess
35132 extensions to the remote protocol. @value{GDBN} does not use such
35133 extensions unless the stub also reports that it supports them by
35134 including @samp{multiprocess+} in its @samp{qSupported} reply.
35135 @xref{multiprocess extensions}, for details.
35138 This feature indicates that @value{GDBN} supports the XML target
35139 description. If the stub sees @samp{xmlRegisters=} with target
35140 specific strings separated by a comma, it will report register
35144 This feature indicates whether @value{GDBN} supports the
35145 @samp{qRelocInsn} packet (@pxref{Tracepoint Packets,,Relocate
35146 instruction reply packet}).
35149 Stubs should ignore any unknown values for
35150 @var{gdbfeature}. Any @value{GDBN} which sends a @samp{qSupported}
35151 packet supports receiving packets of unlimited length (earlier
35152 versions of @value{GDBN} may reject overly long responses). Additional values
35153 for @var{gdbfeature} may be defined in the future to let the stub take
35154 advantage of new features in @value{GDBN}, e.g.@: incompatible
35155 improvements in the remote protocol---the @samp{multiprocess} feature is
35156 an example of such a feature. The stub's reply should be independent
35157 of the @var{gdbfeature} entries sent by @value{GDBN}; first @value{GDBN}
35158 describes all the features it supports, and then the stub replies with
35159 all the features it supports.
35161 Similarly, @value{GDBN} will silently ignore unrecognized stub feature
35162 responses, as long as each response uses one of the standard forms.
35164 Some features are flags. A stub which supports a flag feature
35165 should respond with a @samp{+} form response. Other features
35166 require values, and the stub should respond with an @samp{=}
35169 Each feature has a default value, which @value{GDBN} will use if
35170 @samp{qSupported} is not available or if the feature is not mentioned
35171 in the @samp{qSupported} response. The default values are fixed; a
35172 stub is free to omit any feature responses that match the defaults.
35174 Not all features can be probed, but for those which can, the probing
35175 mechanism is useful: in some cases, a stub's internal
35176 architecture may not allow the protocol layer to know some information
35177 about the underlying target in advance. This is especially common in
35178 stubs which may be configured for multiple targets.
35180 These are the currently defined stub features and their properties:
35182 @multitable @columnfractions 0.35 0.2 0.12 0.2
35183 @c NOTE: The first row should be @headitem, but we do not yet require
35184 @c a new enough version of Texinfo (4.7) to use @headitem.
35186 @tab Value Required
35190 @item @samp{PacketSize}
35195 @item @samp{qXfer:auxv:read}
35200 @item @samp{qXfer:btrace:read}
35205 @item @samp{qXfer:features:read}
35210 @item @samp{qXfer:libraries:read}
35215 @item @samp{qXfer:libraries-svr4:read}
35220 @item @samp{augmented-libraries-svr4-read}
35225 @item @samp{qXfer:memory-map:read}
35230 @item @samp{qXfer:sdata:read}
35235 @item @samp{qXfer:spu:read}
35240 @item @samp{qXfer:spu:write}
35245 @item @samp{qXfer:siginfo:read}
35250 @item @samp{qXfer:siginfo:write}
35255 @item @samp{qXfer:threads:read}
35260 @item @samp{qXfer:traceframe-info:read}
35265 @item @samp{qXfer:uib:read}
35270 @item @samp{qXfer:fdpic:read}
35275 @item @samp{Qbtrace:off}
35280 @item @samp{Qbtrace:bts}
35285 @item @samp{QNonStop}
35290 @item @samp{QPassSignals}
35295 @item @samp{QStartNoAckMode}
35300 @item @samp{multiprocess}
35305 @item @samp{ConditionalBreakpoints}
35310 @item @samp{ConditionalTracepoints}
35315 @item @samp{ReverseContinue}
35320 @item @samp{ReverseStep}
35325 @item @samp{TracepointSource}
35330 @item @samp{QAgent}
35335 @item @samp{QAllow}
35340 @item @samp{QDisableRandomization}
35345 @item @samp{EnableDisableTracepoints}
35350 @item @samp{QTBuffer:size}
35355 @item @samp{tracenz}
35360 @item @samp{BreakpointCommands}
35367 These are the currently defined stub features, in more detail:
35370 @cindex packet size, remote protocol
35371 @item PacketSize=@var{bytes}
35372 The remote stub can accept packets up to at least @var{bytes} in
35373 length. @value{GDBN} will send packets up to this size for bulk
35374 transfers, and will never send larger packets. This is a limit on the
35375 data characters in the packet, including the frame and checksum.
35376 There is no trailing NUL byte in a remote protocol packet; if the stub
35377 stores packets in a NUL-terminated format, it should allow an extra
35378 byte in its buffer for the NUL. If this stub feature is not supported,
35379 @value{GDBN} guesses based on the size of the @samp{g} packet response.
35381 @item qXfer:auxv:read
35382 The remote stub understands the @samp{qXfer:auxv:read} packet
35383 (@pxref{qXfer auxiliary vector read}).
35385 @item qXfer:btrace:read
35386 The remote stub understands the @samp{qXfer:btrace:read}
35387 packet (@pxref{qXfer btrace read}).
35389 @item qXfer:features:read
35390 The remote stub understands the @samp{qXfer:features:read} packet
35391 (@pxref{qXfer target description read}).
35393 @item qXfer:libraries:read
35394 The remote stub understands the @samp{qXfer:libraries:read} packet
35395 (@pxref{qXfer library list read}).
35397 @item qXfer:libraries-svr4:read
35398 The remote stub understands the @samp{qXfer:libraries-svr4:read} packet
35399 (@pxref{qXfer svr4 library list read}).
35401 @item augmented-libraries-svr4-read
35402 The remote stub understands the augmented form of the
35403 @samp{qXfer:libraries-svr4:read} packet
35404 (@pxref{qXfer svr4 library list read}).
35406 @item qXfer:memory-map:read
35407 The remote stub understands the @samp{qXfer:memory-map:read} packet
35408 (@pxref{qXfer memory map read}).
35410 @item qXfer:sdata:read
35411 The remote stub understands the @samp{qXfer:sdata:read} packet
35412 (@pxref{qXfer sdata read}).
35414 @item qXfer:spu:read
35415 The remote stub understands the @samp{qXfer:spu:read} packet
35416 (@pxref{qXfer spu read}).
35418 @item qXfer:spu:write
35419 The remote stub understands the @samp{qXfer:spu:write} packet
35420 (@pxref{qXfer spu write}).
35422 @item qXfer:siginfo:read
35423 The remote stub understands the @samp{qXfer:siginfo:read} packet
35424 (@pxref{qXfer siginfo read}).
35426 @item qXfer:siginfo:write
35427 The remote stub understands the @samp{qXfer:siginfo:write} packet
35428 (@pxref{qXfer siginfo write}).
35430 @item qXfer:threads:read
35431 The remote stub understands the @samp{qXfer:threads:read} packet
35432 (@pxref{qXfer threads read}).
35434 @item qXfer:traceframe-info:read
35435 The remote stub understands the @samp{qXfer:traceframe-info:read}
35436 packet (@pxref{qXfer traceframe info read}).
35438 @item qXfer:uib:read
35439 The remote stub understands the @samp{qXfer:uib:read}
35440 packet (@pxref{qXfer unwind info block}).
35442 @item qXfer:fdpic:read
35443 The remote stub understands the @samp{qXfer:fdpic:read}
35444 packet (@pxref{qXfer fdpic loadmap read}).
35447 The remote stub understands the @samp{QNonStop} packet
35448 (@pxref{QNonStop}).
35451 The remote stub understands the @samp{QPassSignals} packet
35452 (@pxref{QPassSignals}).
35454 @item QStartNoAckMode
35455 The remote stub understands the @samp{QStartNoAckMode} packet and
35456 prefers to operate in no-acknowledgment mode. @xref{Packet Acknowledgment}.
35459 @anchor{multiprocess extensions}
35460 @cindex multiprocess extensions, in remote protocol
35461 The remote stub understands the multiprocess extensions to the remote
35462 protocol syntax. The multiprocess extensions affect the syntax of
35463 thread IDs in both packets and replies (@pxref{thread-id syntax}), and
35464 add process IDs to the @samp{D} packet and @samp{W} and @samp{X}
35465 replies. Note that reporting this feature indicates support for the
35466 syntactic extensions only, not that the stub necessarily supports
35467 debugging of more than one process at a time. The stub must not use
35468 multiprocess extensions in packet replies unless @value{GDBN} has also
35469 indicated it supports them in its @samp{qSupported} request.
35471 @item qXfer:osdata:read
35472 The remote stub understands the @samp{qXfer:osdata:read} packet
35473 ((@pxref{qXfer osdata read}).
35475 @item ConditionalBreakpoints
35476 The target accepts and implements evaluation of conditional expressions
35477 defined for breakpoints. The target will only report breakpoint triggers
35478 when such conditions are true (@pxref{Conditions, ,Break Conditions}).
35480 @item ConditionalTracepoints
35481 The remote stub accepts and implements conditional expressions defined
35482 for tracepoints (@pxref{Tracepoint Conditions}).
35484 @item ReverseContinue
35485 The remote stub accepts and implements the reverse continue packet
35489 The remote stub accepts and implements the reverse step packet
35492 @item TracepointSource
35493 The remote stub understands the @samp{QTDPsrc} packet that supplies
35494 the source form of tracepoint definitions.
35497 The remote stub understands the @samp{QAgent} packet.
35500 The remote stub understands the @samp{QAllow} packet.
35502 @item QDisableRandomization
35503 The remote stub understands the @samp{QDisableRandomization} packet.
35505 @item StaticTracepoint
35506 @cindex static tracepoints, in remote protocol
35507 The remote stub supports static tracepoints.
35509 @item InstallInTrace
35510 @anchor{install tracepoint in tracing}
35511 The remote stub supports installing tracepoint in tracing.
35513 @item EnableDisableTracepoints
35514 The remote stub supports the @samp{QTEnable} (@pxref{QTEnable}) and
35515 @samp{QTDisable} (@pxref{QTDisable}) packets that allow tracepoints
35516 to be enabled and disabled while a trace experiment is running.
35518 @item QTBuffer:size
35519 The remote stub supports the @samp{QTBuffer:size} (@pxref{QTBuffer-size})
35520 packet that allows to change the size of the trace buffer.
35523 @cindex string tracing, in remote protocol
35524 The remote stub supports the @samp{tracenz} bytecode for collecting strings.
35525 See @ref{Bytecode Descriptions} for details about the bytecode.
35527 @item BreakpointCommands
35528 @cindex breakpoint commands, in remote protocol
35529 The remote stub supports running a breakpoint's command list itself,
35530 rather than reporting the hit to @value{GDBN}.
35533 The remote stub understands the @samp{Qbtrace:off} packet.
35536 The remote stub understands the @samp{Qbtrace:bts} packet.
35541 @cindex symbol lookup, remote request
35542 @cindex @samp{qSymbol} packet
35543 Notify the target that @value{GDBN} is prepared to serve symbol lookup
35544 requests. Accept requests from the target for the values of symbols.
35549 The target does not need to look up any (more) symbols.
35550 @item qSymbol:@var{sym_name}
35551 The target requests the value of symbol @var{sym_name} (hex encoded).
35552 @value{GDBN} may provide the value by using the
35553 @samp{qSymbol:@var{sym_value}:@var{sym_name}} message, described
35557 @item qSymbol:@var{sym_value}:@var{sym_name}
35558 Set the value of @var{sym_name} to @var{sym_value}.
35560 @var{sym_name} (hex encoded) is the name of a symbol whose value the
35561 target has previously requested.
35563 @var{sym_value} (hex) is the value for symbol @var{sym_name}. If
35564 @value{GDBN} cannot supply a value for @var{sym_name}, then this field
35570 The target does not need to look up any (more) symbols.
35571 @item qSymbol:@var{sym_name}
35572 The target requests the value of a new symbol @var{sym_name} (hex
35573 encoded). @value{GDBN} will continue to supply the values of symbols
35574 (if available), until the target ceases to request them.
35579 @itemx QTDisconnected
35586 @itemx qTMinFTPILen
35588 @xref{Tracepoint Packets}.
35590 @item qThreadExtraInfo,@var{thread-id}
35591 @cindex thread attributes info, remote request
35592 @cindex @samp{qThreadExtraInfo} packet
35593 Obtain a printable string description of a thread's attributes from
35594 the target OS. @var{thread-id} is a thread ID;
35595 see @ref{thread-id syntax}. This
35596 string may contain anything that the target OS thinks is interesting
35597 for @value{GDBN} to tell the user about the thread. The string is
35598 displayed in @value{GDBN}'s @code{info threads} display. Some
35599 examples of possible thread extra info strings are @samp{Runnable}, or
35600 @samp{Blocked on Mutex}.
35604 @item @var{XX}@dots{}
35605 Where @samp{@var{XX}@dots{}} is a hex encoding of @sc{ascii} data,
35606 comprising the printable string containing the extra information about
35607 the thread's attributes.
35610 (Note that the @code{qThreadExtraInfo} packet's name is separated from
35611 the command by a @samp{,}, not a @samp{:}, contrary to the naming
35612 conventions above. Please don't use this packet as a model for new
35631 @xref{Tracepoint Packets}.
35633 @item qXfer:@var{object}:read:@var{annex}:@var{offset},@var{length}
35634 @cindex read special object, remote request
35635 @cindex @samp{qXfer} packet
35636 @anchor{qXfer read}
35637 Read uninterpreted bytes from the target's special data area
35638 identified by the keyword @var{object}. Request @var{length} bytes
35639 starting at @var{offset} bytes into the data. The content and
35640 encoding of @var{annex} is specific to @var{object}; it can supply
35641 additional details about what data to access.
35643 Here are the specific requests of this form defined so far. All
35644 @samp{qXfer:@var{object}:read:@dots{}} requests use the same reply
35645 formats, listed below.
35648 @item qXfer:auxv:read::@var{offset},@var{length}
35649 @anchor{qXfer auxiliary vector read}
35650 Access the target's @dfn{auxiliary vector}. @xref{OS Information,
35651 auxiliary vector}. Note @var{annex} must be empty.
35653 This packet is not probed by default; the remote stub must request it,
35654 by supplying an appropriate @samp{qSupported} response (@pxref{qSupported}).
35656 @item qXfer:btrace:read:@var{annex}:@var{offset},@var{length}
35657 @anchor{qXfer btrace read}
35659 Return a description of the current branch trace.
35660 @xref{Branch Trace Format}. The annex part of the generic @samp{qXfer}
35661 packet may have one of the following values:
35665 Returns all available branch trace.
35668 Returns all available branch trace if the branch trace changed since
35669 the last read request.
35672 Returns the new branch trace since the last read request. Adds a new
35673 block to the end of the trace that begins at zero and ends at the source
35674 location of the first branch in the trace buffer. This extra block is
35675 used to stitch traces together.
35677 If the trace buffer overflowed, returns an error indicating the overflow.
35680 This packet is not probed by default; the remote stub must request it
35681 by supplying an appropriate @samp{qSupported} response (@pxref{qSupported}).
35683 @item qXfer:features:read:@var{annex}:@var{offset},@var{length}
35684 @anchor{qXfer target description read}
35685 Access the @dfn{target description}. @xref{Target Descriptions}. The
35686 annex specifies which XML document to access. The main description is
35687 always loaded from the @samp{target.xml} annex.
35689 This packet is not probed by default; the remote stub must request it,
35690 by supplying an appropriate @samp{qSupported} response (@pxref{qSupported}).
35692 @item qXfer:libraries:read:@var{annex}:@var{offset},@var{length}
35693 @anchor{qXfer library list read}
35694 Access the target's list of loaded libraries. @xref{Library List Format}.
35695 The annex part of the generic @samp{qXfer} packet must be empty
35696 (@pxref{qXfer read}).
35698 Targets which maintain a list of libraries in the program's memory do
35699 not need to implement this packet; it is designed for platforms where
35700 the operating system manages the list of loaded libraries.
35702 This packet is not probed by default; the remote stub must request it,
35703 by supplying an appropriate @samp{qSupported} response (@pxref{qSupported}).
35705 @item qXfer:libraries-svr4:read:@var{annex}:@var{offset},@var{length}
35706 @anchor{qXfer svr4 library list read}
35707 Access the target's list of loaded libraries when the target is an SVR4
35708 platform. @xref{Library List Format for SVR4 Targets}. The annex part
35709 of the generic @samp{qXfer} packet must be empty unless the remote
35710 stub indicated it supports the augmented form of this packet
35711 by supplying an appropriate @samp{qSupported} response
35712 (@pxref{qXfer read}, @ref{qSupported}).
35714 This packet is optional for better performance on SVR4 targets.
35715 @value{GDBN} uses memory read packets to read the SVR4 library list otherwise.
35717 This packet is not probed by default; the remote stub must request it,
35718 by supplying an appropriate @samp{qSupported} response (@pxref{qSupported}).
35720 If the remote stub indicates it supports the augmented form of this
35721 packet then the annex part of the generic @samp{qXfer} packet may
35722 contain a semicolon-separated list of @samp{@var{name}=@var{value}}
35723 arguments. The currently supported arguments are:
35726 @item start=@var{address}
35727 A hexadecimal number specifying the address of the @samp{struct
35728 link_map} to start reading the library list from. If unset or zero
35729 then the first @samp{struct link_map} in the library list will be
35730 chosen as the starting point.
35732 @item prev=@var{address}
35733 A hexadecimal number specifying the address of the @samp{struct
35734 link_map} immediately preceding the @samp{struct link_map}
35735 specified by the @samp{start} argument. If unset or zero then
35736 the remote stub will expect that no @samp{struct link_map}
35737 exists prior to the starting point.
35741 Arguments that are not understood by the remote stub will be silently
35744 @item qXfer:memory-map:read::@var{offset},@var{length}
35745 @anchor{qXfer memory map read}
35746 Access the target's @dfn{memory-map}. @xref{Memory Map Format}. The
35747 annex part of the generic @samp{qXfer} packet must be empty
35748 (@pxref{qXfer read}).
35750 This packet is not probed by default; the remote stub must request it,
35751 by supplying an appropriate @samp{qSupported} response (@pxref{qSupported}).
35753 @item qXfer:sdata:read::@var{offset},@var{length}
35754 @anchor{qXfer sdata read}
35756 Read contents of the extra collected static tracepoint marker
35757 information. The annex part of the generic @samp{qXfer} packet must
35758 be empty (@pxref{qXfer read}). @xref{Tracepoint Actions,,Tracepoint
35761 This packet is not probed by default; the remote stub must request it,
35762 by supplying an appropriate @samp{qSupported} response
35763 (@pxref{qSupported}).
35765 @item qXfer:siginfo:read::@var{offset},@var{length}
35766 @anchor{qXfer siginfo read}
35767 Read contents of the extra signal information on the target
35768 system. The annex part of the generic @samp{qXfer} packet must be
35769 empty (@pxref{qXfer read}).
35771 This packet is not probed by default; the remote stub must request it,
35772 by supplying an appropriate @samp{qSupported} response
35773 (@pxref{qSupported}).
35775 @item qXfer:spu:read:@var{annex}:@var{offset},@var{length}
35776 @anchor{qXfer spu read}
35777 Read contents of an @code{spufs} file on the target system. The
35778 annex specifies which file to read; it must be of the form
35779 @file{@var{id}/@var{name}}, where @var{id} specifies an SPU context ID
35780 in the target process, and @var{name} identifes the @code{spufs} file
35781 in that context to be accessed.
35783 This packet is not probed by default; the remote stub must request it,
35784 by supplying an appropriate @samp{qSupported} response
35785 (@pxref{qSupported}).
35787 @item qXfer:threads:read::@var{offset},@var{length}
35788 @anchor{qXfer threads read}
35789 Access the list of threads on target. @xref{Thread List Format}. The
35790 annex part of the generic @samp{qXfer} packet must be empty
35791 (@pxref{qXfer read}).
35793 This packet is not probed by default; the remote stub must request it,
35794 by supplying an appropriate @samp{qSupported} response (@pxref{qSupported}).
35796 @item qXfer:traceframe-info:read::@var{offset},@var{length}
35797 @anchor{qXfer traceframe info read}
35799 Return a description of the current traceframe's contents.
35800 @xref{Traceframe Info Format}. The annex part of the generic
35801 @samp{qXfer} packet must be empty (@pxref{qXfer read}).
35803 This packet is not probed by default; the remote stub must request it,
35804 by supplying an appropriate @samp{qSupported} response (@pxref{qSupported}).
35806 @item qXfer:uib:read:@var{pc}:@var{offset},@var{length}
35807 @anchor{qXfer unwind info block}
35809 Return the unwind information block for @var{pc}. This packet is used
35810 on OpenVMS/ia64 to ask the kernel unwind information.
35812 This packet is not probed by default.
35814 @item qXfer:fdpic:read:@var{annex}:@var{offset},@var{length}
35815 @anchor{qXfer fdpic loadmap read}
35816 Read contents of @code{loadmap}s on the target system. The
35817 annex, either @samp{exec} or @samp{interp}, specifies which @code{loadmap},
35818 executable @code{loadmap} or interpreter @code{loadmap} to read.
35820 This packet is not probed by default; the remote stub must request it,
35821 by supplying an appropriate @samp{qSupported} response (@pxref{qSupported}).
35823 @item qXfer:osdata:read::@var{offset},@var{length}
35824 @anchor{qXfer osdata read}
35825 Access the target's @dfn{operating system information}.
35826 @xref{Operating System Information}.
35833 Data @var{data} (@pxref{Binary Data}) has been read from the
35834 target. There may be more data at a higher address (although
35835 it is permitted to return @samp{m} even for the last valid
35836 block of data, as long as at least one byte of data was read).
35837 @var{data} may have fewer bytes than the @var{length} in the
35841 Data @var{data} (@pxref{Binary Data}) has been read from the target.
35842 There is no more data to be read. @var{data} may have fewer bytes
35843 than the @var{length} in the request.
35846 The @var{offset} in the request is at the end of the data.
35847 There is no more data to be read.
35850 The request was malformed, or @var{annex} was invalid.
35853 The offset was invalid, or there was an error encountered reading the data.
35854 @var{nn} is a hex-encoded @code{errno} value.
35857 An empty reply indicates the @var{object} string was not recognized by
35858 the stub, or that the object does not support reading.
35861 @item qXfer:@var{object}:write:@var{annex}:@var{offset}:@var{data}@dots{}
35862 @cindex write data into object, remote request
35863 @anchor{qXfer write}
35864 Write uninterpreted bytes into the target's special data area
35865 identified by the keyword @var{object}, starting at @var{offset} bytes
35866 into the data. @var{data}@dots{} is the binary-encoded data
35867 (@pxref{Binary Data}) to be written. The content and encoding of @var{annex}
35868 is specific to @var{object}; it can supply additional details about what data
35871 Here are the specific requests of this form defined so far. All
35872 @samp{qXfer:@var{object}:write:@dots{}} requests use the same reply
35873 formats, listed below.
35876 @item qXfer:siginfo:write::@var{offset}:@var{data}@dots{}
35877 @anchor{qXfer siginfo write}
35878 Write @var{data} to the extra signal information on the target system.
35879 The annex part of the generic @samp{qXfer} packet must be
35880 empty (@pxref{qXfer write}).
35882 This packet is not probed by default; the remote stub must request it,
35883 by supplying an appropriate @samp{qSupported} response
35884 (@pxref{qSupported}).
35886 @item qXfer:spu:write:@var{annex}:@var{offset}:@var{data}@dots{}
35887 @anchor{qXfer spu write}
35888 Write @var{data} to an @code{spufs} file on the target system. The
35889 annex specifies which file to write; it must be of the form
35890 @file{@var{id}/@var{name}}, where @var{id} specifies an SPU context ID
35891 in the target process, and @var{name} identifes the @code{spufs} file
35892 in that context to be accessed.
35894 This packet is not probed by default; the remote stub must request it,
35895 by supplying an appropriate @samp{qSupported} response (@pxref{qSupported}).
35901 @var{nn} (hex encoded) is the number of bytes written.
35902 This may be fewer bytes than supplied in the request.
35905 The request was malformed, or @var{annex} was invalid.
35908 The offset was invalid, or there was an error encountered writing the data.
35909 @var{nn} is a hex-encoded @code{errno} value.
35912 An empty reply indicates the @var{object} string was not
35913 recognized by the stub, or that the object does not support writing.
35916 @item qXfer:@var{object}:@var{operation}:@dots{}
35917 Requests of this form may be added in the future. When a stub does
35918 not recognize the @var{object} keyword, or its support for
35919 @var{object} does not recognize the @var{operation} keyword, the stub
35920 must respond with an empty packet.
35922 @item qAttached:@var{pid}
35923 @cindex query attached, remote request
35924 @cindex @samp{qAttached} packet
35925 Return an indication of whether the remote server attached to an
35926 existing process or created a new process. When the multiprocess
35927 protocol extensions are supported (@pxref{multiprocess extensions}),
35928 @var{pid} is an integer in hexadecimal format identifying the target
35929 process. Otherwise, @value{GDBN} will omit the @var{pid} field and
35930 the query packet will be simplified as @samp{qAttached}.
35932 This query is used, for example, to know whether the remote process
35933 should be detached or killed when a @value{GDBN} session is ended with
35934 the @code{quit} command.
35939 The remote server attached to an existing process.
35941 The remote server created a new process.
35943 A badly formed request or an error was encountered.
35947 Enable branch tracing for the current thread using bts tracing.
35952 Branch tracing has been enabled.
35954 A badly formed request or an error was encountered.
35958 Disable branch tracing for the current thread.
35963 Branch tracing has been disabled.
35965 A badly formed request or an error was encountered.
35970 @node Architecture-Specific Protocol Details
35971 @section Architecture-Specific Protocol Details
35973 This section describes how the remote protocol is applied to specific
35974 target architectures. Also see @ref{Standard Target Features}, for
35975 details of XML target descriptions for each architecture.
35978 * ARM-Specific Protocol Details::
35979 * MIPS-Specific Protocol Details::
35982 @node ARM-Specific Protocol Details
35983 @subsection @acronym{ARM}-specific Protocol Details
35986 * ARM Breakpoint Kinds::
35989 @node ARM Breakpoint Kinds
35990 @subsubsection @acronym{ARM} Breakpoint Kinds
35991 @cindex breakpoint kinds, @acronym{ARM}
35993 These breakpoint kinds are defined for the @samp{Z0} and @samp{Z1} packets.
35998 16-bit Thumb mode breakpoint.
36001 32-bit Thumb mode (Thumb-2) breakpoint.
36004 32-bit @acronym{ARM} mode breakpoint.
36008 @node MIPS-Specific Protocol Details
36009 @subsection @acronym{MIPS}-specific Protocol Details
36012 * MIPS Register packet Format::
36013 * MIPS Breakpoint Kinds::
36016 @node MIPS Register packet Format
36017 @subsubsection @acronym{MIPS} Register Packet Format
36018 @cindex register packet format, @acronym{MIPS}
36020 The following @code{g}/@code{G} packets have previously been defined.
36021 In the below, some thirty-two bit registers are transferred as
36022 sixty-four bits. Those registers should be zero/sign extended (which?)
36023 to fill the space allocated. Register bytes are transferred in target
36024 byte order. The two nibbles within a register byte are transferred
36025 most-significant -- least-significant.
36030 All registers are transferred as thirty-two bit quantities in the order:
36031 32 general-purpose; sr; lo; hi; bad; cause; pc; 32 floating-point
36032 registers; fsr; fir; fp.
36035 All registers are transferred as sixty-four bit quantities (including
36036 thirty-two bit registers such as @code{sr}). The ordering is the same
36041 @node MIPS Breakpoint Kinds
36042 @subsubsection @acronym{MIPS} Breakpoint Kinds
36043 @cindex breakpoint kinds, @acronym{MIPS}
36045 These breakpoint kinds are defined for the @samp{Z0} and @samp{Z1} packets.
36050 16-bit @acronym{MIPS16} mode breakpoint.
36053 16-bit @acronym{microMIPS} mode breakpoint.
36056 32-bit standard @acronym{MIPS} mode breakpoint.
36059 32-bit @acronym{microMIPS} mode breakpoint.
36063 @node Tracepoint Packets
36064 @section Tracepoint Packets
36065 @cindex tracepoint packets
36066 @cindex packets, tracepoint
36068 Here we describe the packets @value{GDBN} uses to implement
36069 tracepoints (@pxref{Tracepoints}).
36073 @item QTDP:@var{n}:@var{addr}:@var{ena}:@var{step}:@var{pass}[:F@var{flen}][:X@var{len},@var{bytes}]@r{[}-@r{]}
36074 @cindex @samp{QTDP} packet
36075 Create a new tracepoint, number @var{n}, at @var{addr}. If @var{ena}
36076 is @samp{E}, then the tracepoint is enabled; if it is @samp{D}, then
36077 the tracepoint is disabled. @var{step} is the tracepoint's step
36078 count, and @var{pass} is its pass count. If an @samp{F} is present,
36079 then the tracepoint is to be a fast tracepoint, and the @var{flen} is
36080 the number of bytes that the target should copy elsewhere to make room
36081 for the tracepoint. If an @samp{X} is present, it introduces a
36082 tracepoint condition, which consists of a hexadecimal length, followed
36083 by a comma and hex-encoded bytes, in a manner similar to action
36084 encodings as described below. If the trailing @samp{-} is present,
36085 further @samp{QTDP} packets will follow to specify this tracepoint's
36091 The packet was understood and carried out.
36093 @xref{Tracepoint Packets,,Relocate instruction reply packet}.
36095 The packet was not recognized.
36098 @item QTDP:-@var{n}:@var{addr}:@r{[}S@r{]}@var{action}@dots{}@r{[}-@r{]}
36099 Define actions to be taken when a tracepoint is hit. @var{n} and
36100 @var{addr} must be the same as in the initial @samp{QTDP} packet for
36101 this tracepoint. This packet may only be sent immediately after
36102 another @samp{QTDP} packet that ended with a @samp{-}. If the
36103 trailing @samp{-} is present, further @samp{QTDP} packets will follow,
36104 specifying more actions for this tracepoint.
36106 In the series of action packets for a given tracepoint, at most one
36107 can have an @samp{S} before its first @var{action}. If such a packet
36108 is sent, it and the following packets define ``while-stepping''
36109 actions. Any prior packets define ordinary actions --- that is, those
36110 taken when the tracepoint is first hit. If no action packet has an
36111 @samp{S}, then all the packets in the series specify ordinary
36112 tracepoint actions.
36114 The @samp{@var{action}@dots{}} portion of the packet is a series of
36115 actions, concatenated without separators. Each action has one of the
36121 Collect the registers whose bits are set in @var{mask}. @var{mask} is
36122 a hexadecimal number whose @var{i}'th bit is set if register number
36123 @var{i} should be collected. (The least significant bit is numbered
36124 zero.) Note that @var{mask} may be any number of digits long; it may
36125 not fit in a 32-bit word.
36127 @item M @var{basereg},@var{offset},@var{len}
36128 Collect @var{len} bytes of memory starting at the address in register
36129 number @var{basereg}, plus @var{offset}. If @var{basereg} is
36130 @samp{-1}, then the range has a fixed address: @var{offset} is the
36131 address of the lowest byte to collect. The @var{basereg},
36132 @var{offset}, and @var{len} parameters are all unsigned hexadecimal
36133 values (the @samp{-1} value for @var{basereg} is a special case).
36135 @item X @var{len},@var{expr}
36136 Evaluate @var{expr}, whose length is @var{len}, and collect memory as
36137 it directs. @var{expr} is an agent expression, as described in
36138 @ref{Agent Expressions}. Each byte of the expression is encoded as a
36139 two-digit hex number in the packet; @var{len} is the number of bytes
36140 in the expression (and thus one-half the number of hex digits in the
36145 Any number of actions may be packed together in a single @samp{QTDP}
36146 packet, as long as the packet does not exceed the maximum packet
36147 length (400 bytes, for many stubs). There may be only one @samp{R}
36148 action per tracepoint, and it must precede any @samp{M} or @samp{X}
36149 actions. Any registers referred to by @samp{M} and @samp{X} actions
36150 must be collected by a preceding @samp{R} action. (The
36151 ``while-stepping'' actions are treated as if they were attached to a
36152 separate tracepoint, as far as these restrictions are concerned.)
36157 The packet was understood and carried out.
36159 @xref{Tracepoint Packets,,Relocate instruction reply packet}.
36161 The packet was not recognized.
36164 @item QTDPsrc:@var{n}:@var{addr}:@var{type}:@var{start}:@var{slen}:@var{bytes}
36165 @cindex @samp{QTDPsrc} packet
36166 Specify a source string of tracepoint @var{n} at address @var{addr}.
36167 This is useful to get accurate reproduction of the tracepoints
36168 originally downloaded at the beginning of the trace run. @var{type}
36169 is the name of the tracepoint part, such as @samp{cond} for the
36170 tracepoint's conditional expression (see below for a list of types), while
36171 @var{bytes} is the string, encoded in hexadecimal.
36173 @var{start} is the offset of the @var{bytes} within the overall source
36174 string, while @var{slen} is the total length of the source string.
36175 This is intended for handling source strings that are longer than will
36176 fit in a single packet.
36177 @c Add detailed example when this info is moved into a dedicated
36178 @c tracepoint descriptions section.
36180 The available string types are @samp{at} for the location,
36181 @samp{cond} for the conditional, and @samp{cmd} for an action command.
36182 @value{GDBN} sends a separate packet for each command in the action
36183 list, in the same order in which the commands are stored in the list.
36185 The target does not need to do anything with source strings except
36186 report them back as part of the replies to the @samp{qTfP}/@samp{qTsP}
36189 Although this packet is optional, and @value{GDBN} will only send it
36190 if the target replies with @samp{TracepointSource} @xref{General
36191 Query Packets}, it makes both disconnected tracing and trace files
36192 much easier to use. Otherwise the user must be careful that the
36193 tracepoints in effect while looking at trace frames are identical to
36194 the ones in effect during the trace run; even a small discrepancy
36195 could cause @samp{tdump} not to work, or a particular trace frame not
36198 @item QTDV:@var{n}:@var{value}
36199 @cindex define trace state variable, remote request
36200 @cindex @samp{QTDV} packet
36201 Create a new trace state variable, number @var{n}, with an initial
36202 value of @var{value}, which is a 64-bit signed integer. Both @var{n}
36203 and @var{value} are encoded as hexadecimal values. @value{GDBN} has
36204 the option of not using this packet for initial values of zero; the
36205 target should simply create the trace state variables as they are
36206 mentioned in expressions.
36208 @item QTFrame:@var{n}
36209 @cindex @samp{QTFrame} packet
36210 Select the @var{n}'th tracepoint frame from the buffer, and use the
36211 register and memory contents recorded there to answer subsequent
36212 request packets from @value{GDBN}.
36214 A successful reply from the stub indicates that the stub has found the
36215 requested frame. The response is a series of parts, concatenated
36216 without separators, describing the frame we selected. Each part has
36217 one of the following forms:
36221 The selected frame is number @var{n} in the trace frame buffer;
36222 @var{f} is a hexadecimal number. If @var{f} is @samp{-1}, then there
36223 was no frame matching the criteria in the request packet.
36226 The selected trace frame records a hit of tracepoint number @var{t};
36227 @var{t} is a hexadecimal number.
36231 @item QTFrame:pc:@var{addr}
36232 Like @samp{QTFrame:@var{n}}, but select the first tracepoint frame after the
36233 currently selected frame whose PC is @var{addr};
36234 @var{addr} is a hexadecimal number.
36236 @item QTFrame:tdp:@var{t}
36237 Like @samp{QTFrame:@var{n}}, but select the first tracepoint frame after the
36238 currently selected frame that is a hit of tracepoint @var{t}; @var{t}
36239 is a hexadecimal number.
36241 @item QTFrame:range:@var{start}:@var{end}
36242 Like @samp{QTFrame:@var{n}}, but select the first tracepoint frame after the
36243 currently selected frame whose PC is between @var{start} (inclusive)
36244 and @var{end} (inclusive); @var{start} and @var{end} are hexadecimal
36247 @item QTFrame:outside:@var{start}:@var{end}
36248 Like @samp{QTFrame:range:@var{start}:@var{end}}, but select the first
36249 frame @emph{outside} the given range of addresses (exclusive).
36252 @cindex @samp{qTMinFTPILen} packet
36253 This packet requests the minimum length of instruction at which a fast
36254 tracepoint (@pxref{Set Tracepoints}) may be placed. For instance, on
36255 the 32-bit x86 architecture, it is possible to use a 4-byte jump, but
36256 it depends on the target system being able to create trampolines in
36257 the first 64K of memory, which might or might not be possible for that
36258 system. So the reply to this packet will be 4 if it is able to
36265 The minimum instruction length is currently unknown.
36267 The minimum instruction length is @var{length}, where @var{length} is greater
36268 or equal to 1. @var{length} is a hexadecimal number. A reply of 1 means
36269 that a fast tracepoint may be placed on any instruction regardless of size.
36271 An error has occurred.
36273 An empty reply indicates that the request is not supported by the stub.
36277 @cindex @samp{QTStart} packet
36278 Begin the tracepoint experiment. Begin collecting data from
36279 tracepoint hits in the trace frame buffer. This packet supports the
36280 @samp{qRelocInsn} reply (@pxref{Tracepoint Packets,,Relocate
36281 instruction reply packet}).
36284 @cindex @samp{QTStop} packet
36285 End the tracepoint experiment. Stop collecting trace frames.
36287 @item QTEnable:@var{n}:@var{addr}
36289 @cindex @samp{QTEnable} packet
36290 Enable tracepoint @var{n} at address @var{addr} in a started tracepoint
36291 experiment. If the tracepoint was previously disabled, then collection
36292 of data from it will resume.
36294 @item QTDisable:@var{n}:@var{addr}
36296 @cindex @samp{QTDisable} packet
36297 Disable tracepoint @var{n} at address @var{addr} in a started tracepoint
36298 experiment. No more data will be collected from the tracepoint unless
36299 @samp{QTEnable:@var{n}:@var{addr}} is subsequently issued.
36302 @cindex @samp{QTinit} packet
36303 Clear the table of tracepoints, and empty the trace frame buffer.
36305 @item QTro:@var{start1},@var{end1}:@var{start2},@var{end2}:@dots{}
36306 @cindex @samp{QTro} packet
36307 Establish the given ranges of memory as ``transparent''. The stub
36308 will answer requests for these ranges from memory's current contents,
36309 if they were not collected as part of the tracepoint hit.
36311 @value{GDBN} uses this to mark read-only regions of memory, like those
36312 containing program code. Since these areas never change, they should
36313 still have the same contents they did when the tracepoint was hit, so
36314 there's no reason for the stub to refuse to provide their contents.
36316 @item QTDisconnected:@var{value}
36317 @cindex @samp{QTDisconnected} packet
36318 Set the choice to what to do with the tracing run when @value{GDBN}
36319 disconnects from the target. A @var{value} of 1 directs the target to
36320 continue the tracing run, while 0 tells the target to stop tracing if
36321 @value{GDBN} is no longer in the picture.
36324 @cindex @samp{qTStatus} packet
36325 Ask the stub if there is a trace experiment running right now.
36327 The reply has the form:
36331 @item T@var{running}@r{[};@var{field}@r{]}@dots{}
36332 @var{running} is a single digit @code{1} if the trace is presently
36333 running, or @code{0} if not. It is followed by semicolon-separated
36334 optional fields that an agent may use to report additional status.
36338 If the trace is not running, the agent may report any of several
36339 explanations as one of the optional fields:
36344 No trace has been run yet.
36346 @item tstop[:@var{text}]:0
36347 The trace was stopped by a user-originated stop command. The optional
36348 @var{text} field is a user-supplied string supplied as part of the
36349 stop command (for instance, an explanation of why the trace was
36350 stopped manually). It is hex-encoded.
36353 The trace stopped because the trace buffer filled up.
36355 @item tdisconnected:0
36356 The trace stopped because @value{GDBN} disconnected from the target.
36358 @item tpasscount:@var{tpnum}
36359 The trace stopped because tracepoint @var{tpnum} exceeded its pass count.
36361 @item terror:@var{text}:@var{tpnum}
36362 The trace stopped because tracepoint @var{tpnum} had an error. The
36363 string @var{text} is available to describe the nature of the error
36364 (for instance, a divide by zero in the condition expression).
36365 @var{text} is hex encoded.
36368 The trace stopped for some other reason.
36372 Additional optional fields supply statistical and other information.
36373 Although not required, they are extremely useful for users monitoring
36374 the progress of a trace run. If a trace has stopped, and these
36375 numbers are reported, they must reflect the state of the just-stopped
36380 @item tframes:@var{n}
36381 The number of trace frames in the buffer.
36383 @item tcreated:@var{n}
36384 The total number of trace frames created during the run. This may
36385 be larger than the trace frame count, if the buffer is circular.
36387 @item tsize:@var{n}
36388 The total size of the trace buffer, in bytes.
36390 @item tfree:@var{n}
36391 The number of bytes still unused in the buffer.
36393 @item circular:@var{n}
36394 The value of the circular trace buffer flag. @code{1} means that the
36395 trace buffer is circular and old trace frames will be discarded if
36396 necessary to make room, @code{0} means that the trace buffer is linear
36399 @item disconn:@var{n}
36400 The value of the disconnected tracing flag. @code{1} means that
36401 tracing will continue after @value{GDBN} disconnects, @code{0} means
36402 that the trace run will stop.
36406 @item qTP:@var{tp}:@var{addr}
36407 @cindex tracepoint status, remote request
36408 @cindex @samp{qTP} packet
36409 Ask the stub for the current state of tracepoint number @var{tp} at
36410 address @var{addr}.
36414 @item V@var{hits}:@var{usage}
36415 The tracepoint has been hit @var{hits} times so far during the trace
36416 run, and accounts for @var{usage} in the trace buffer. Note that
36417 @code{while-stepping} steps are not counted as separate hits, but the
36418 steps' space consumption is added into the usage number.
36422 @item qTV:@var{var}
36423 @cindex trace state variable value, remote request
36424 @cindex @samp{qTV} packet
36425 Ask the stub for the value of the trace state variable number @var{var}.
36430 The value of the variable is @var{value}. This will be the current
36431 value of the variable if the user is examining a running target, or a
36432 saved value if the variable was collected in the trace frame that the
36433 user is looking at. Note that multiple requests may result in
36434 different reply values, such as when requesting values while the
36435 program is running.
36438 The value of the variable is unknown. This would occur, for example,
36439 if the user is examining a trace frame in which the requested variable
36444 @cindex @samp{qTfP} packet
36446 @cindex @samp{qTsP} packet
36447 These packets request data about tracepoints that are being used by
36448 the target. @value{GDBN} sends @code{qTfP} to get the first piece
36449 of data, and multiple @code{qTsP} to get additional pieces. Replies
36450 to these packets generally take the form of the @code{QTDP} packets
36451 that define tracepoints. (FIXME add detailed syntax)
36454 @cindex @samp{qTfV} packet
36456 @cindex @samp{qTsV} packet
36457 These packets request data about trace state variables that are on the
36458 target. @value{GDBN} sends @code{qTfV} to get the first vari of data,
36459 and multiple @code{qTsV} to get additional variables. Replies to
36460 these packets follow the syntax of the @code{QTDV} packets that define
36461 trace state variables.
36467 @cindex @samp{qTfSTM} packet
36468 @cindex @samp{qTsSTM} packet
36469 These packets request data about static tracepoint markers that exist
36470 in the target program. @value{GDBN} sends @code{qTfSTM} to get the
36471 first piece of data, and multiple @code{qTsSTM} to get additional
36472 pieces. Replies to these packets take the following form:
36476 @item m @var{address}:@var{id}:@var{extra}
36478 @item m @var{address}:@var{id}:@var{extra},@var{address}:@var{id}:@var{extra}@dots{}
36479 a comma-separated list of markers
36481 (lower case letter @samp{L}) denotes end of list.
36483 An error occurred. @var{nn} are hex digits.
36485 An empty reply indicates that the request is not supported by the
36489 @var{address} is encoded in hex.
36490 @var{id} and @var{extra} are strings encoded in hex.
36492 In response to each query, the target will reply with a list of one or
36493 more markers, separated by commas. @value{GDBN} will respond to each
36494 reply with a request for more markers (using the @samp{qs} form of the
36495 query), until the target responds with @samp{l} (lower-case ell, for
36498 @item qTSTMat:@var{address}
36500 @cindex @samp{qTSTMat} packet
36501 This packets requests data about static tracepoint markers in the
36502 target program at @var{address}. Replies to this packet follow the
36503 syntax of the @samp{qTfSTM} and @code{qTsSTM} packets that list static
36504 tracepoint markers.
36506 @item QTSave:@var{filename}
36507 @cindex @samp{QTSave} packet
36508 This packet directs the target to save trace data to the file name
36509 @var{filename} in the target's filesystem. @var{filename} is encoded
36510 as a hex string; the interpretation of the file name (relative vs
36511 absolute, wild cards, etc) is up to the target.
36513 @item qTBuffer:@var{offset},@var{len}
36514 @cindex @samp{qTBuffer} packet
36515 Return up to @var{len} bytes of the current contents of trace buffer,
36516 starting at @var{offset}. The trace buffer is treated as if it were
36517 a contiguous collection of traceframes, as per the trace file format.
36518 The reply consists as many hex-encoded bytes as the target can deliver
36519 in a packet; it is not an error to return fewer than were asked for.
36520 A reply consisting of just @code{l} indicates that no bytes are
36523 @item QTBuffer:circular:@var{value}
36524 This packet directs the target to use a circular trace buffer if
36525 @var{value} is 1, or a linear buffer if the value is 0.
36527 @item QTBuffer:size:@var{size}
36528 @anchor{QTBuffer-size}
36529 @cindex @samp{QTBuffer size} packet
36530 This packet directs the target to make the trace buffer be of size
36531 @var{size} if possible. A value of @code{-1} tells the target to
36532 use whatever size it prefers.
36534 @item QTNotes:@r{[}@var{type}:@var{text}@r{]}@r{[};@var{type}:@var{text}@r{]}@dots{}
36535 @cindex @samp{QTNotes} packet
36536 This packet adds optional textual notes to the trace run. Allowable
36537 types include @code{user}, @code{notes}, and @code{tstop}, the
36538 @var{text} fields are arbitrary strings, hex-encoded.
36542 @subsection Relocate instruction reply packet
36543 When installing fast tracepoints in memory, the target may need to
36544 relocate the instruction currently at the tracepoint address to a
36545 different address in memory. For most instructions, a simple copy is
36546 enough, but, for example, call instructions that implicitly push the
36547 return address on the stack, and relative branches or other
36548 PC-relative instructions require offset adjustment, so that the effect
36549 of executing the instruction at a different address is the same as if
36550 it had executed in the original location.
36552 In response to several of the tracepoint packets, the target may also
36553 respond with a number of intermediate @samp{qRelocInsn} request
36554 packets before the final result packet, to have @value{GDBN} handle
36555 this relocation operation. If a packet supports this mechanism, its
36556 documentation will explicitly say so. See for example the above
36557 descriptions for the @samp{QTStart} and @samp{QTDP} packets. The
36558 format of the request is:
36561 @item qRelocInsn:@var{from};@var{to}
36563 This requests @value{GDBN} to copy instruction at address @var{from}
36564 to address @var{to}, possibly adjusted so that executing the
36565 instruction at @var{to} has the same effect as executing it at
36566 @var{from}. @value{GDBN} writes the adjusted instruction to target
36567 memory starting at @var{to}.
36572 @item qRelocInsn:@var{adjusted_size}
36573 Informs the stub the relocation is complete. @var{adjusted_size} is
36574 the length in bytes of resulting relocated instruction sequence.
36576 A badly formed request was detected, or an error was encountered while
36577 relocating the instruction.
36580 @node Host I/O Packets
36581 @section Host I/O Packets
36582 @cindex Host I/O, remote protocol
36583 @cindex file transfer, remote protocol
36585 The @dfn{Host I/O} packets allow @value{GDBN} to perform I/O
36586 operations on the far side of a remote link. For example, Host I/O is
36587 used to upload and download files to a remote target with its own
36588 filesystem. Host I/O uses the same constant values and data structure
36589 layout as the target-initiated File-I/O protocol. However, the
36590 Host I/O packets are structured differently. The target-initiated
36591 protocol relies on target memory to store parameters and buffers.
36592 Host I/O requests are initiated by @value{GDBN}, and the
36593 target's memory is not involved. @xref{File-I/O Remote Protocol
36594 Extension}, for more details on the target-initiated protocol.
36596 The Host I/O request packets all encode a single operation along with
36597 its arguments. They have this format:
36601 @item vFile:@var{operation}: @var{parameter}@dots{}
36602 @var{operation} is the name of the particular request; the target
36603 should compare the entire packet name up to the second colon when checking
36604 for a supported operation. The format of @var{parameter} depends on
36605 the operation. Numbers are always passed in hexadecimal. Negative
36606 numbers have an explicit minus sign (i.e.@: two's complement is not
36607 used). Strings (e.g.@: filenames) are encoded as a series of
36608 hexadecimal bytes. The last argument to a system call may be a
36609 buffer of escaped binary data (@pxref{Binary Data}).
36613 The valid responses to Host I/O packets are:
36617 @item F @var{result} [, @var{errno}] [; @var{attachment}]
36618 @var{result} is the integer value returned by this operation, usually
36619 non-negative for success and -1 for errors. If an error has occured,
36620 @var{errno} will be included in the result. @var{errno} will have a
36621 value defined by the File-I/O protocol (@pxref{Errno Values}). For
36622 operations which return data, @var{attachment} supplies the data as a
36623 binary buffer. Binary buffers in response packets are escaped in the
36624 normal way (@pxref{Binary Data}). See the individual packet
36625 documentation for the interpretation of @var{result} and
36629 An empty response indicates that this operation is not recognized.
36633 These are the supported Host I/O operations:
36636 @item vFile:open: @var{pathname}, @var{flags}, @var{mode}
36637 Open a file at @var{pathname} and return a file descriptor for it, or
36638 return -1 if an error occurs. @var{pathname} is a string,
36639 @var{flags} is an integer indicating a mask of open flags
36640 (@pxref{Open Flags}), and @var{mode} is an integer indicating a mask
36641 of mode bits to use if the file is created (@pxref{mode_t Values}).
36642 @xref{open}, for details of the open flags and mode values.
36644 @item vFile:close: @var{fd}
36645 Close the open file corresponding to @var{fd} and return 0, or
36646 -1 if an error occurs.
36648 @item vFile:pread: @var{fd}, @var{count}, @var{offset}
36649 Read data from the open file corresponding to @var{fd}. Up to
36650 @var{count} bytes will be read from the file, starting at @var{offset}
36651 relative to the start of the file. The target may read fewer bytes;
36652 common reasons include packet size limits and an end-of-file
36653 condition. The number of bytes read is returned. Zero should only be
36654 returned for a successful read at the end of the file, or if
36655 @var{count} was zero.
36657 The data read should be returned as a binary attachment on success.
36658 If zero bytes were read, the response should include an empty binary
36659 attachment (i.e.@: a trailing semicolon). The return value is the
36660 number of target bytes read; the binary attachment may be longer if
36661 some characters were escaped.
36663 @item vFile:pwrite: @var{fd}, @var{offset}, @var{data}
36664 Write @var{data} (a binary buffer) to the open file corresponding
36665 to @var{fd}. Start the write at @var{offset} from the start of the
36666 file. Unlike many @code{write} system calls, there is no
36667 separate @var{count} argument; the length of @var{data} in the
36668 packet is used. @samp{vFile:write} returns the number of bytes written,
36669 which may be shorter than the length of @var{data}, or -1 if an
36672 @item vFile:unlink: @var{pathname}
36673 Delete the file at @var{pathname} on the target. Return 0,
36674 or -1 if an error occurs. @var{pathname} is a string.
36676 @item vFile:readlink: @var{filename}
36677 Read value of symbolic link @var{filename} on the target. Return
36678 the number of bytes read, or -1 if an error occurs.
36680 The data read should be returned as a binary attachment on success.
36681 If zero bytes were read, the response should include an empty binary
36682 attachment (i.e.@: a trailing semicolon). The return value is the
36683 number of target bytes read; the binary attachment may be longer if
36684 some characters were escaped.
36689 @section Interrupts
36690 @cindex interrupts (remote protocol)
36692 When a program on the remote target is running, @value{GDBN} may
36693 attempt to interrupt it by sending a @samp{Ctrl-C}, @code{BREAK} or
36694 a @code{BREAK} followed by @code{g},
36695 control of which is specified via @value{GDBN}'s @samp{interrupt-sequence}.
36697 The precise meaning of @code{BREAK} is defined by the transport
36698 mechanism and may, in fact, be undefined. @value{GDBN} does not
36699 currently define a @code{BREAK} mechanism for any of the network
36700 interfaces except for TCP, in which case @value{GDBN} sends the
36701 @code{telnet} BREAK sequence.
36703 @samp{Ctrl-C}, on the other hand, is defined and implemented for all
36704 transport mechanisms. It is represented by sending the single byte
36705 @code{0x03} without any of the usual packet overhead described in
36706 the Overview section (@pxref{Overview}). When a @code{0x03} byte is
36707 transmitted as part of a packet, it is considered to be packet data
36708 and does @emph{not} represent an interrupt. E.g., an @samp{X} packet
36709 (@pxref{X packet}), used for binary downloads, may include an unescaped
36710 @code{0x03} as part of its packet.
36712 @code{BREAK} followed by @code{g} is also known as Magic SysRq g.
36713 When Linux kernel receives this sequence from serial port,
36714 it stops execution and connects to gdb.
36716 Stubs are not required to recognize these interrupt mechanisms and the
36717 precise meaning associated with receipt of the interrupt is
36718 implementation defined. If the target supports debugging of multiple
36719 threads and/or processes, it should attempt to interrupt all
36720 currently-executing threads and processes.
36721 If the stub is successful at interrupting the
36722 running program, it should send one of the stop
36723 reply packets (@pxref{Stop Reply Packets}) to @value{GDBN} as a result
36724 of successfully stopping the program in all-stop mode, and a stop reply
36725 for each stopped thread in non-stop mode.
36726 Interrupts received while the
36727 program is stopped are discarded.
36729 @node Notification Packets
36730 @section Notification Packets
36731 @cindex notification packets
36732 @cindex packets, notification
36734 The @value{GDBN} remote serial protocol includes @dfn{notifications},
36735 packets that require no acknowledgment. Both the GDB and the stub
36736 may send notifications (although the only notifications defined at
36737 present are sent by the stub). Notifications carry information
36738 without incurring the round-trip latency of an acknowledgment, and so
36739 are useful for low-impact communications where occasional packet loss
36742 A notification packet has the form @samp{% @var{data} #
36743 @var{checksum}}, where @var{data} is the content of the notification,
36744 and @var{checksum} is a checksum of @var{data}, computed and formatted
36745 as for ordinary @value{GDBN} packets. A notification's @var{data}
36746 never contains @samp{$}, @samp{%} or @samp{#} characters. Upon
36747 receiving a notification, the recipient sends no @samp{+} or @samp{-}
36748 to acknowledge the notification's receipt or to report its corruption.
36750 Every notification's @var{data} begins with a name, which contains no
36751 colon characters, followed by a colon character.
36753 Recipients should silently ignore corrupted notifications and
36754 notifications they do not understand. Recipients should restart
36755 timeout periods on receipt of a well-formed notification, whether or
36756 not they understand it.
36758 Senders should only send the notifications described here when this
36759 protocol description specifies that they are permitted. In the
36760 future, we may extend the protocol to permit existing notifications in
36761 new contexts; this rule helps older senders avoid confusing newer
36764 (Older versions of @value{GDBN} ignore bytes received until they see
36765 the @samp{$} byte that begins an ordinary packet, so new stubs may
36766 transmit notifications without fear of confusing older clients. There
36767 are no notifications defined for @value{GDBN} to send at the moment, but we
36768 assume that most older stubs would ignore them, as well.)
36770 Each notification is comprised of three parts:
36772 @item @var{name}:@var{event}
36773 The notification packet is sent by the side that initiates the
36774 exchange (currently, only the stub does that), with @var{event}
36775 carrying the specific information about the notification.
36776 @var{name} is the name of the notification.
36778 The acknowledge sent by the other side, usually @value{GDBN}, to
36779 acknowledge the exchange and request the event.
36782 The purpose of an asynchronous notification mechanism is to report to
36783 @value{GDBN} that something interesting happened in the remote stub.
36785 The remote stub may send notification @var{name}:@var{event}
36786 at any time, but @value{GDBN} acknowledges the notification when
36787 appropriate. The notification event is pending before @value{GDBN}
36788 acknowledges. Only one notification at a time may be pending; if
36789 additional events occur before @value{GDBN} has acknowledged the
36790 previous notification, they must be queued by the stub for later
36791 synchronous transmission in response to @var{ack} packets from
36792 @value{GDBN}. Because the notification mechanism is unreliable,
36793 the stub is permitted to resend a notification if it believes
36794 @value{GDBN} may not have received it.
36796 Specifically, notifications may appear when @value{GDBN} is not
36797 otherwise reading input from the stub, or when @value{GDBN} is
36798 expecting to read a normal synchronous response or a
36799 @samp{+}/@samp{-} acknowledgment to a packet it has sent.
36800 Notification packets are distinct from any other communication from
36801 the stub so there is no ambiguity.
36803 After receiving a notification, @value{GDBN} shall acknowledge it by
36804 sending a @var{ack} packet as a regular, synchronous request to the
36805 stub. Such acknowledgment is not required to happen immediately, as
36806 @value{GDBN} is permitted to send other, unrelated packets to the
36807 stub first, which the stub should process normally.
36809 Upon receiving a @var{ack} packet, if the stub has other queued
36810 events to report to @value{GDBN}, it shall respond by sending a
36811 normal @var{event}. @value{GDBN} shall then send another @var{ack}
36812 packet to solicit further responses; again, it is permitted to send
36813 other, unrelated packets as well which the stub should process
36816 If the stub receives a @var{ack} packet and there are no additional
36817 @var{event} to report, the stub shall return an @samp{OK} response.
36818 At this point, @value{GDBN} has finished processing a notification
36819 and the stub has completed sending any queued events. @value{GDBN}
36820 won't accept any new notifications until the final @samp{OK} is
36821 received . If further notification events occur, the stub shall send
36822 a new notification, @value{GDBN} shall accept the notification, and
36823 the process shall be repeated.
36825 The process of asynchronous notification can be illustrated by the
36828 <- @code{%%Stop:T0505:98e7ffbf;04:4ce6ffbf;08:b1b6e54c;thread:p7526.7526;core:0;}
36831 <- @code{T0505:68f37db7;04:40f37db7;08:63850408;thread:p7526.7528;core:0;}
36833 <- @code{T0505:68e3fdb6;04:40e3fdb6;08:63850408;thread:p7526.7529;core:0;}
36838 The following notifications are defined:
36839 @multitable @columnfractions 0.12 0.12 0.38 0.38
36848 @tab @var{reply}. The @var{reply} has the form of a stop reply, as
36849 described in @ref{Stop Reply Packets}. Refer to @ref{Remote Non-Stop},
36850 for information on how these notifications are acknowledged by
36852 @tab Report an asynchronous stop event in non-stop mode.
36856 @node Remote Non-Stop
36857 @section Remote Protocol Support for Non-Stop Mode
36859 @value{GDBN}'s remote protocol supports non-stop debugging of
36860 multi-threaded programs, as described in @ref{Non-Stop Mode}. If the stub
36861 supports non-stop mode, it should report that to @value{GDBN} by including
36862 @samp{QNonStop+} in its @samp{qSupported} response (@pxref{qSupported}).
36864 @value{GDBN} typically sends a @samp{QNonStop} packet only when
36865 establishing a new connection with the stub. Entering non-stop mode
36866 does not alter the state of any currently-running threads, but targets
36867 must stop all threads in any already-attached processes when entering
36868 all-stop mode. @value{GDBN} uses the @samp{?} packet as necessary to
36869 probe the target state after a mode change.
36871 In non-stop mode, when an attached process encounters an event that
36872 would otherwise be reported with a stop reply, it uses the
36873 asynchronous notification mechanism (@pxref{Notification Packets}) to
36874 inform @value{GDBN}. In contrast to all-stop mode, where all threads
36875 in all processes are stopped when a stop reply is sent, in non-stop
36876 mode only the thread reporting the stop event is stopped. That is,
36877 when reporting a @samp{S} or @samp{T} response to indicate completion
36878 of a step operation, hitting a breakpoint, or a fault, only the
36879 affected thread is stopped; any other still-running threads continue
36880 to run. When reporting a @samp{W} or @samp{X} response, all running
36881 threads belonging to other attached processes continue to run.
36883 In non-stop mode, the target shall respond to the @samp{?} packet as
36884 follows. First, any incomplete stop reply notification/@samp{vStopped}
36885 sequence in progress is abandoned. The target must begin a new
36886 sequence reporting stop events for all stopped threads, whether or not
36887 it has previously reported those events to @value{GDBN}. The first
36888 stop reply is sent as a synchronous reply to the @samp{?} packet, and
36889 subsequent stop replies are sent as responses to @samp{vStopped} packets
36890 using the mechanism described above. The target must not send
36891 asynchronous stop reply notifications until the sequence is complete.
36892 If all threads are running when the target receives the @samp{?} packet,
36893 or if the target is not attached to any process, it shall respond
36896 @node Packet Acknowledgment
36897 @section Packet Acknowledgment
36899 @cindex acknowledgment, for @value{GDBN} remote
36900 @cindex packet acknowledgment, for @value{GDBN} remote
36901 By default, when either the host or the target machine receives a packet,
36902 the first response expected is an acknowledgment: either @samp{+} (to indicate
36903 the package was received correctly) or @samp{-} (to request retransmission).
36904 This mechanism allows the @value{GDBN} remote protocol to operate over
36905 unreliable transport mechanisms, such as a serial line.
36907 In cases where the transport mechanism is itself reliable (such as a pipe or
36908 TCP connection), the @samp{+}/@samp{-} acknowledgments are redundant.
36909 It may be desirable to disable them in that case to reduce communication
36910 overhead, or for other reasons. This can be accomplished by means of the
36911 @samp{QStartNoAckMode} packet; @pxref{QStartNoAckMode}.
36913 When in no-acknowledgment mode, neither the stub nor @value{GDBN} shall send or
36914 expect @samp{+}/@samp{-} protocol acknowledgments. The packet
36915 and response format still includes the normal checksum, as described in
36916 @ref{Overview}, but the checksum may be ignored by the receiver.
36918 If the stub supports @samp{QStartNoAckMode} and prefers to operate in
36919 no-acknowledgment mode, it should report that to @value{GDBN}
36920 by including @samp{QStartNoAckMode+} in its response to @samp{qSupported};
36921 @pxref{qSupported}.
36922 If @value{GDBN} also supports @samp{QStartNoAckMode} and it has not been
36923 disabled via the @code{set remote noack-packet off} command
36924 (@pxref{Remote Configuration}),
36925 @value{GDBN} may then send a @samp{QStartNoAckMode} packet to the stub.
36926 Only then may the stub actually turn off packet acknowledgments.
36927 @value{GDBN} sends a final @samp{+} acknowledgment of the stub's @samp{OK}
36928 response, which can be safely ignored by the stub.
36930 Note that @code{set remote noack-packet} command only affects negotiation
36931 between @value{GDBN} and the stub when subsequent connections are made;
36932 it does not affect the protocol acknowledgment state for any current
36934 Since @samp{+}/@samp{-} acknowledgments are enabled by default when a
36935 new connection is established,
36936 there is also no protocol request to re-enable the acknowledgments
36937 for the current connection, once disabled.
36942 Example sequence of a target being re-started. Notice how the restart
36943 does not get any direct output:
36948 @emph{target restarts}
36951 <- @code{T001:1234123412341234}
36955 Example sequence of a target being stepped by a single instruction:
36958 -> @code{G1445@dots{}}
36963 <- @code{T001:1234123412341234}
36967 <- @code{1455@dots{}}
36971 @node File-I/O Remote Protocol Extension
36972 @section File-I/O Remote Protocol Extension
36973 @cindex File-I/O remote protocol extension
36976 * File-I/O Overview::
36977 * Protocol Basics::
36978 * The F Request Packet::
36979 * The F Reply Packet::
36980 * The Ctrl-C Message::
36982 * List of Supported Calls::
36983 * Protocol-specific Representation of Datatypes::
36985 * File-I/O Examples::
36988 @node File-I/O Overview
36989 @subsection File-I/O Overview
36990 @cindex file-i/o overview
36992 The @dfn{File I/O remote protocol extension} (short: File-I/O) allows the
36993 target to use the host's file system and console I/O to perform various
36994 system calls. System calls on the target system are translated into a
36995 remote protocol packet to the host system, which then performs the needed
36996 actions and returns a response packet to the target system.
36997 This simulates file system operations even on targets that lack file systems.
36999 The protocol is defined to be independent of both the host and target systems.
37000 It uses its own internal representation of datatypes and values. Both
37001 @value{GDBN} and the target's @value{GDBN} stub are responsible for
37002 translating the system-dependent value representations into the internal
37003 protocol representations when data is transmitted.
37005 The communication is synchronous. A system call is possible only when
37006 @value{GDBN} is waiting for a response from the @samp{C}, @samp{c}, @samp{S}
37007 or @samp{s} packets. While @value{GDBN} handles the request for a system call,
37008 the target is stopped to allow deterministic access to the target's
37009 memory. Therefore File-I/O is not interruptible by target signals. On
37010 the other hand, it is possible to interrupt File-I/O by a user interrupt
37011 (@samp{Ctrl-C}) within @value{GDBN}.
37013 The target's request to perform a host system call does not finish
37014 the latest @samp{C}, @samp{c}, @samp{S} or @samp{s} action. That means,
37015 after finishing the system call, the target returns to continuing the
37016 previous activity (continue, step). No additional continue or step
37017 request from @value{GDBN} is required.
37020 (@value{GDBP}) continue
37021 <- target requests 'system call X'
37022 target is stopped, @value{GDBN} executes system call
37023 -> @value{GDBN} returns result
37024 ... target continues, @value{GDBN} returns to wait for the target
37025 <- target hits breakpoint and sends a Txx packet
37028 The protocol only supports I/O on the console and to regular files on
37029 the host file system. Character or block special devices, pipes,
37030 named pipes, sockets or any other communication method on the host
37031 system are not supported by this protocol.
37033 File I/O is not supported in non-stop mode.
37035 @node Protocol Basics
37036 @subsection Protocol Basics
37037 @cindex protocol basics, file-i/o
37039 The File-I/O protocol uses the @code{F} packet as the request as well
37040 as reply packet. Since a File-I/O system call can only occur when
37041 @value{GDBN} is waiting for a response from the continuing or stepping target,
37042 the File-I/O request is a reply that @value{GDBN} has to expect as a result
37043 of a previous @samp{C}, @samp{c}, @samp{S} or @samp{s} packet.
37044 This @code{F} packet contains all information needed to allow @value{GDBN}
37045 to call the appropriate host system call:
37049 A unique identifier for the requested system call.
37052 All parameters to the system call. Pointers are given as addresses
37053 in the target memory address space. Pointers to strings are given as
37054 pointer/length pair. Numerical values are given as they are.
37055 Numerical control flags are given in a protocol-specific representation.
37059 At this point, @value{GDBN} has to perform the following actions.
37063 If the parameters include pointer values to data needed as input to a
37064 system call, @value{GDBN} requests this data from the target with a
37065 standard @code{m} packet request. This additional communication has to be
37066 expected by the target implementation and is handled as any other @code{m}
37070 @value{GDBN} translates all value from protocol representation to host
37071 representation as needed. Datatypes are coerced into the host types.
37074 @value{GDBN} calls the system call.
37077 It then coerces datatypes back to protocol representation.
37080 If the system call is expected to return data in buffer space specified
37081 by pointer parameters to the call, the data is transmitted to the
37082 target using a @code{M} or @code{X} packet. This packet has to be expected
37083 by the target implementation and is handled as any other @code{M} or @code{X}
37088 Eventually @value{GDBN} replies with another @code{F} packet which contains all
37089 necessary information for the target to continue. This at least contains
37096 @code{errno}, if has been changed by the system call.
37103 After having done the needed type and value coercion, the target continues
37104 the latest continue or step action.
37106 @node The F Request Packet
37107 @subsection The @code{F} Request Packet
37108 @cindex file-i/o request packet
37109 @cindex @code{F} request packet
37111 The @code{F} request packet has the following format:
37114 @item F@var{call-id},@var{parameter@dots{}}
37116 @var{call-id} is the identifier to indicate the host system call to be called.
37117 This is just the name of the function.
37119 @var{parameter@dots{}} are the parameters to the system call.
37120 Parameters are hexadecimal integer values, either the actual values in case
37121 of scalar datatypes, pointers to target buffer space in case of compound
37122 datatypes and unspecified memory areas, or pointer/length pairs in case
37123 of string parameters. These are appended to the @var{call-id} as a
37124 comma-delimited list. All values are transmitted in ASCII
37125 string representation, pointer/length pairs separated by a slash.
37131 @node The F Reply Packet
37132 @subsection The @code{F} Reply Packet
37133 @cindex file-i/o reply packet
37134 @cindex @code{F} reply packet
37136 The @code{F} reply packet has the following format:
37140 @item F@var{retcode},@var{errno},@var{Ctrl-C flag};@var{call-specific attachment}
37142 @var{retcode} is the return code of the system call as hexadecimal value.
37144 @var{errno} is the @code{errno} set by the call, in protocol-specific
37146 This parameter can be omitted if the call was successful.
37148 @var{Ctrl-C flag} is only sent if the user requested a break. In this
37149 case, @var{errno} must be sent as well, even if the call was successful.
37150 The @var{Ctrl-C flag} itself consists of the character @samp{C}:
37157 or, if the call was interrupted before the host call has been performed:
37164 assuming 4 is the protocol-specific representation of @code{EINTR}.
37169 @node The Ctrl-C Message
37170 @subsection The @samp{Ctrl-C} Message
37171 @cindex ctrl-c message, in file-i/o protocol
37173 If the @samp{Ctrl-C} flag is set in the @value{GDBN}
37174 reply packet (@pxref{The F Reply Packet}),
37175 the target should behave as if it had
37176 gotten a break message. The meaning for the target is ``system call
37177 interrupted by @code{SIGINT}''. Consequentially, the target should actually stop
37178 (as with a break message) and return to @value{GDBN} with a @code{T02}
37181 It's important for the target to know in which
37182 state the system call was interrupted. There are two possible cases:
37186 The system call hasn't been performed on the host yet.
37189 The system call on the host has been finished.
37193 These two states can be distinguished by the target by the value of the
37194 returned @code{errno}. If it's the protocol representation of @code{EINTR}, the system
37195 call hasn't been performed. This is equivalent to the @code{EINTR} handling
37196 on POSIX systems. In any other case, the target may presume that the
37197 system call has been finished --- successfully or not --- and should behave
37198 as if the break message arrived right after the system call.
37200 @value{GDBN} must behave reliably. If the system call has not been called
37201 yet, @value{GDBN} may send the @code{F} reply immediately, setting @code{EINTR} as
37202 @code{errno} in the packet. If the system call on the host has been finished
37203 before the user requests a break, the full action must be finished by
37204 @value{GDBN}. This requires sending @code{M} or @code{X} packets as necessary.
37205 The @code{F} packet may only be sent when either nothing has happened
37206 or the full action has been completed.
37209 @subsection Console I/O
37210 @cindex console i/o as part of file-i/o
37212 By default and if not explicitly closed by the target system, the file
37213 descriptors 0, 1 and 2 are connected to the @value{GDBN} console. Output
37214 on the @value{GDBN} console is handled as any other file output operation
37215 (@code{write(1, @dots{})} or @code{write(2, @dots{})}). Console input is handled
37216 by @value{GDBN} so that after the target read request from file descriptor
37217 0 all following typing is buffered until either one of the following
37222 The user types @kbd{Ctrl-c}. The behaviour is as explained above, and the
37224 system call is treated as finished.
37227 The user presses @key{RET}. This is treated as end of input with a trailing
37231 The user types @kbd{Ctrl-d}. This is treated as end of input. No trailing
37232 character (neither newline nor @samp{Ctrl-D}) is appended to the input.
37236 If the user has typed more characters than fit in the buffer given to
37237 the @code{read} call, the trailing characters are buffered in @value{GDBN} until
37238 either another @code{read(0, @dots{})} is requested by the target, or debugging
37239 is stopped at the user's request.
37242 @node List of Supported Calls
37243 @subsection List of Supported Calls
37244 @cindex list of supported file-i/o calls
37261 @unnumberedsubsubsec open
37262 @cindex open, file-i/o system call
37267 int open(const char *pathname, int flags);
37268 int open(const char *pathname, int flags, mode_t mode);
37272 @samp{Fopen,@var{pathptr}/@var{len},@var{flags},@var{mode}}
37275 @var{flags} is the bitwise @code{OR} of the following values:
37279 If the file does not exist it will be created. The host
37280 rules apply as far as file ownership and time stamps
37284 When used with @code{O_CREAT}, if the file already exists it is
37285 an error and open() fails.
37288 If the file already exists and the open mode allows
37289 writing (@code{O_RDWR} or @code{O_WRONLY} is given) it will be
37290 truncated to zero length.
37293 The file is opened in append mode.
37296 The file is opened for reading only.
37299 The file is opened for writing only.
37302 The file is opened for reading and writing.
37306 Other bits are silently ignored.
37310 @var{mode} is the bitwise @code{OR} of the following values:
37314 User has read permission.
37317 User has write permission.
37320 Group has read permission.
37323 Group has write permission.
37326 Others have read permission.
37329 Others have write permission.
37333 Other bits are silently ignored.
37336 @item Return value:
37337 @code{open} returns the new file descriptor or -1 if an error
37344 @var{pathname} already exists and @code{O_CREAT} and @code{O_EXCL} were used.
37347 @var{pathname} refers to a directory.
37350 The requested access is not allowed.
37353 @var{pathname} was too long.
37356 A directory component in @var{pathname} does not exist.
37359 @var{pathname} refers to a device, pipe, named pipe or socket.
37362 @var{pathname} refers to a file on a read-only filesystem and
37363 write access was requested.
37366 @var{pathname} is an invalid pointer value.
37369 No space on device to create the file.
37372 The process already has the maximum number of files open.
37375 The limit on the total number of files open on the system
37379 The call was interrupted by the user.
37385 @unnumberedsubsubsec close
37386 @cindex close, file-i/o system call
37395 @samp{Fclose,@var{fd}}
37397 @item Return value:
37398 @code{close} returns zero on success, or -1 if an error occurred.
37404 @var{fd} isn't a valid open file descriptor.
37407 The call was interrupted by the user.
37413 @unnumberedsubsubsec read
37414 @cindex read, file-i/o system call
37419 int read(int fd, void *buf, unsigned int count);
37423 @samp{Fread,@var{fd},@var{bufptr},@var{count}}
37425 @item Return value:
37426 On success, the number of bytes read is returned.
37427 Zero indicates end of file. If count is zero, read
37428 returns zero as well. On error, -1 is returned.
37434 @var{fd} is not a valid file descriptor or is not open for
37438 @var{bufptr} is an invalid pointer value.
37441 The call was interrupted by the user.
37447 @unnumberedsubsubsec write
37448 @cindex write, file-i/o system call
37453 int write(int fd, const void *buf, unsigned int count);
37457 @samp{Fwrite,@var{fd},@var{bufptr},@var{count}}
37459 @item Return value:
37460 On success, the number of bytes written are returned.
37461 Zero indicates nothing was written. On error, -1
37468 @var{fd} is not a valid file descriptor or is not open for
37472 @var{bufptr} is an invalid pointer value.
37475 An attempt was made to write a file that exceeds the
37476 host-specific maximum file size allowed.
37479 No space on device to write the data.
37482 The call was interrupted by the user.
37488 @unnumberedsubsubsec lseek
37489 @cindex lseek, file-i/o system call
37494 long lseek (int fd, long offset, int flag);
37498 @samp{Flseek,@var{fd},@var{offset},@var{flag}}
37500 @var{flag} is one of:
37504 The offset is set to @var{offset} bytes.
37507 The offset is set to its current location plus @var{offset}
37511 The offset is set to the size of the file plus @var{offset}
37515 @item Return value:
37516 On success, the resulting unsigned offset in bytes from
37517 the beginning of the file is returned. Otherwise, a
37518 value of -1 is returned.
37524 @var{fd} is not a valid open file descriptor.
37527 @var{fd} is associated with the @value{GDBN} console.
37530 @var{flag} is not a proper value.
37533 The call was interrupted by the user.
37539 @unnumberedsubsubsec rename
37540 @cindex rename, file-i/o system call
37545 int rename(const char *oldpath, const char *newpath);
37549 @samp{Frename,@var{oldpathptr}/@var{len},@var{newpathptr}/@var{len}}
37551 @item Return value:
37552 On success, zero is returned. On error, -1 is returned.
37558 @var{newpath} is an existing directory, but @var{oldpath} is not a
37562 @var{newpath} is a non-empty directory.
37565 @var{oldpath} or @var{newpath} is a directory that is in use by some
37569 An attempt was made to make a directory a subdirectory
37573 A component used as a directory in @var{oldpath} or new
37574 path is not a directory. Or @var{oldpath} is a directory
37575 and @var{newpath} exists but is not a directory.
37578 @var{oldpathptr} or @var{newpathptr} are invalid pointer values.
37581 No access to the file or the path of the file.
37585 @var{oldpath} or @var{newpath} was too long.
37588 A directory component in @var{oldpath} or @var{newpath} does not exist.
37591 The file is on a read-only filesystem.
37594 The device containing the file has no room for the new
37598 The call was interrupted by the user.
37604 @unnumberedsubsubsec unlink
37605 @cindex unlink, file-i/o system call
37610 int unlink(const char *pathname);
37614 @samp{Funlink,@var{pathnameptr}/@var{len}}
37616 @item Return value:
37617 On success, zero is returned. On error, -1 is returned.
37623 No access to the file or the path of the file.
37626 The system does not allow unlinking of directories.
37629 The file @var{pathname} cannot be unlinked because it's
37630 being used by another process.
37633 @var{pathnameptr} is an invalid pointer value.
37636 @var{pathname} was too long.
37639 A directory component in @var{pathname} does not exist.
37642 A component of the path is not a directory.
37645 The file is on a read-only filesystem.
37648 The call was interrupted by the user.
37654 @unnumberedsubsubsec stat/fstat
37655 @cindex fstat, file-i/o system call
37656 @cindex stat, file-i/o system call
37661 int stat(const char *pathname, struct stat *buf);
37662 int fstat(int fd, struct stat *buf);
37666 @samp{Fstat,@var{pathnameptr}/@var{len},@var{bufptr}}@*
37667 @samp{Ffstat,@var{fd},@var{bufptr}}
37669 @item Return value:
37670 On success, zero is returned. On error, -1 is returned.
37676 @var{fd} is not a valid open file.
37679 A directory component in @var{pathname} does not exist or the
37680 path is an empty string.
37683 A component of the path is not a directory.
37686 @var{pathnameptr} is an invalid pointer value.
37689 No access to the file or the path of the file.
37692 @var{pathname} was too long.
37695 The call was interrupted by the user.
37701 @unnumberedsubsubsec gettimeofday
37702 @cindex gettimeofday, file-i/o system call
37707 int gettimeofday(struct timeval *tv, void *tz);
37711 @samp{Fgettimeofday,@var{tvptr},@var{tzptr}}
37713 @item Return value:
37714 On success, 0 is returned, -1 otherwise.
37720 @var{tz} is a non-NULL pointer.
37723 @var{tvptr} and/or @var{tzptr} is an invalid pointer value.
37729 @unnumberedsubsubsec isatty
37730 @cindex isatty, file-i/o system call
37735 int isatty(int fd);
37739 @samp{Fisatty,@var{fd}}
37741 @item Return value:
37742 Returns 1 if @var{fd} refers to the @value{GDBN} console, 0 otherwise.
37748 The call was interrupted by the user.
37753 Note that the @code{isatty} call is treated as a special case: it returns
37754 1 to the target if the file descriptor is attached
37755 to the @value{GDBN} console, 0 otherwise. Implementing through system calls
37756 would require implementing @code{ioctl} and would be more complex than
37761 @unnumberedsubsubsec system
37762 @cindex system, file-i/o system call
37767 int system(const char *command);
37771 @samp{Fsystem,@var{commandptr}/@var{len}}
37773 @item Return value:
37774 If @var{len} is zero, the return value indicates whether a shell is
37775 available. A zero return value indicates a shell is not available.
37776 For non-zero @var{len}, the value returned is -1 on error and the
37777 return status of the command otherwise. Only the exit status of the
37778 command is returned, which is extracted from the host's @code{system}
37779 return value by calling @code{WEXITSTATUS(retval)}. In case
37780 @file{/bin/sh} could not be executed, 127 is returned.
37786 The call was interrupted by the user.
37791 @value{GDBN} takes over the full task of calling the necessary host calls
37792 to perform the @code{system} call. The return value of @code{system} on
37793 the host is simplified before it's returned
37794 to the target. Any termination signal information from the child process
37795 is discarded, and the return value consists
37796 entirely of the exit status of the called command.
37798 Due to security concerns, the @code{system} call is by default refused
37799 by @value{GDBN}. The user has to allow this call explicitly with the
37800 @code{set remote system-call-allowed 1} command.
37803 @item set remote system-call-allowed
37804 @kindex set remote system-call-allowed
37805 Control whether to allow the @code{system} calls in the File I/O
37806 protocol for the remote target. The default is zero (disabled).
37808 @item show remote system-call-allowed
37809 @kindex show remote system-call-allowed
37810 Show whether the @code{system} calls are allowed in the File I/O
37814 @node Protocol-specific Representation of Datatypes
37815 @subsection Protocol-specific Representation of Datatypes
37816 @cindex protocol-specific representation of datatypes, in file-i/o protocol
37819 * Integral Datatypes::
37821 * Memory Transfer::
37826 @node Integral Datatypes
37827 @unnumberedsubsubsec Integral Datatypes
37828 @cindex integral datatypes, in file-i/o protocol
37830 The integral datatypes used in the system calls are @code{int},
37831 @code{unsigned int}, @code{long}, @code{unsigned long},
37832 @code{mode_t}, and @code{time_t}.
37834 @code{int}, @code{unsigned int}, @code{mode_t} and @code{time_t} are
37835 implemented as 32 bit values in this protocol.
37837 @code{long} and @code{unsigned long} are implemented as 64 bit types.
37839 @xref{Limits}, for corresponding MIN and MAX values (similar to those
37840 in @file{limits.h}) to allow range checking on host and target.
37842 @code{time_t} datatypes are defined as seconds since the Epoch.
37844 All integral datatypes transferred as part of a memory read or write of a
37845 structured datatype e.g.@: a @code{struct stat} have to be given in big endian
37848 @node Pointer Values
37849 @unnumberedsubsubsec Pointer Values
37850 @cindex pointer values, in file-i/o protocol
37852 Pointers to target data are transmitted as they are. An exception
37853 is made for pointers to buffers for which the length isn't
37854 transmitted as part of the function call, namely strings. Strings
37855 are transmitted as a pointer/length pair, both as hex values, e.g.@:
37862 which is a pointer to data of length 18 bytes at position 0x1aaf.
37863 The length is defined as the full string length in bytes, including
37864 the trailing null byte. For example, the string @code{"hello world"}
37865 at address 0x123456 is transmitted as
37871 @node Memory Transfer
37872 @unnumberedsubsubsec Memory Transfer
37873 @cindex memory transfer, in file-i/o protocol
37875 Structured data which is transferred using a memory read or write (for
37876 example, a @code{struct stat}) is expected to be in a protocol-specific format
37877 with all scalar multibyte datatypes being big endian. Translation to
37878 this representation needs to be done both by the target before the @code{F}
37879 packet is sent, and by @value{GDBN} before
37880 it transfers memory to the target. Transferred pointers to structured
37881 data should point to the already-coerced data at any time.
37885 @unnumberedsubsubsec struct stat
37886 @cindex struct stat, in file-i/o protocol
37888 The buffer of type @code{struct stat} used by the target and @value{GDBN}
37889 is defined as follows:
37893 unsigned int st_dev; /* device */
37894 unsigned int st_ino; /* inode */
37895 mode_t st_mode; /* protection */
37896 unsigned int st_nlink; /* number of hard links */
37897 unsigned int st_uid; /* user ID of owner */
37898 unsigned int st_gid; /* group ID of owner */
37899 unsigned int st_rdev; /* device type (if inode device) */
37900 unsigned long st_size; /* total size, in bytes */
37901 unsigned long st_blksize; /* blocksize for filesystem I/O */
37902 unsigned long st_blocks; /* number of blocks allocated */
37903 time_t st_atime; /* time of last access */
37904 time_t st_mtime; /* time of last modification */
37905 time_t st_ctime; /* time of last change */
37909 The integral datatypes conform to the definitions given in the
37910 appropriate section (see @ref{Integral Datatypes}, for details) so this
37911 structure is of size 64 bytes.
37913 The values of several fields have a restricted meaning and/or
37919 A value of 0 represents a file, 1 the console.
37922 No valid meaning for the target. Transmitted unchanged.
37925 Valid mode bits are described in @ref{Constants}. Any other
37926 bits have currently no meaning for the target.
37931 No valid meaning for the target. Transmitted unchanged.
37936 These values have a host and file system dependent
37937 accuracy. Especially on Windows hosts, the file system may not
37938 support exact timing values.
37941 The target gets a @code{struct stat} of the above representation and is
37942 responsible for coercing it to the target representation before
37945 Note that due to size differences between the host, target, and protocol
37946 representations of @code{struct stat} members, these members could eventually
37947 get truncated on the target.
37949 @node struct timeval
37950 @unnumberedsubsubsec struct timeval
37951 @cindex struct timeval, in file-i/o protocol
37953 The buffer of type @code{struct timeval} used by the File-I/O protocol
37954 is defined as follows:
37958 time_t tv_sec; /* second */
37959 long tv_usec; /* microsecond */
37963 The integral datatypes conform to the definitions given in the
37964 appropriate section (see @ref{Integral Datatypes}, for details) so this
37965 structure is of size 8 bytes.
37968 @subsection Constants
37969 @cindex constants, in file-i/o protocol
37971 The following values are used for the constants inside of the
37972 protocol. @value{GDBN} and target are responsible for translating these
37973 values before and after the call as needed.
37984 @unnumberedsubsubsec Open Flags
37985 @cindex open flags, in file-i/o protocol
37987 All values are given in hexadecimal representation.
37999 @node mode_t Values
38000 @unnumberedsubsubsec mode_t Values
38001 @cindex mode_t values, in file-i/o protocol
38003 All values are given in octal representation.
38020 @unnumberedsubsubsec Errno Values
38021 @cindex errno values, in file-i/o protocol
38023 All values are given in decimal representation.
38048 @code{EUNKNOWN} is used as a fallback error value if a host system returns
38049 any error value not in the list of supported error numbers.
38052 @unnumberedsubsubsec Lseek Flags
38053 @cindex lseek flags, in file-i/o protocol
38062 @unnumberedsubsubsec Limits
38063 @cindex limits, in file-i/o protocol
38065 All values are given in decimal representation.
38068 INT_MIN -2147483648
38070 UINT_MAX 4294967295
38071 LONG_MIN -9223372036854775808
38072 LONG_MAX 9223372036854775807
38073 ULONG_MAX 18446744073709551615
38076 @node File-I/O Examples
38077 @subsection File-I/O Examples
38078 @cindex file-i/o examples
38080 Example sequence of a write call, file descriptor 3, buffer is at target
38081 address 0x1234, 6 bytes should be written:
38084 <- @code{Fwrite,3,1234,6}
38085 @emph{request memory read from target}
38088 @emph{return "6 bytes written"}
38092 Example sequence of a read call, file descriptor 3, buffer is at target
38093 address 0x1234, 6 bytes should be read:
38096 <- @code{Fread,3,1234,6}
38097 @emph{request memory write to target}
38098 -> @code{X1234,6:XXXXXX}
38099 @emph{return "6 bytes read"}
38103 Example sequence of a read call, call fails on the host due to invalid
38104 file descriptor (@code{EBADF}):
38107 <- @code{Fread,3,1234,6}
38111 Example sequence of a read call, user presses @kbd{Ctrl-c} before syscall on
38115 <- @code{Fread,3,1234,6}
38120 Example sequence of a read call, user presses @kbd{Ctrl-c} after syscall on
38124 <- @code{Fread,3,1234,6}
38125 -> @code{X1234,6:XXXXXX}
38129 @node Library List Format
38130 @section Library List Format
38131 @cindex library list format, remote protocol
38133 On some platforms, a dynamic loader (e.g.@: @file{ld.so}) runs in the
38134 same process as your application to manage libraries. In this case,
38135 @value{GDBN} can use the loader's symbol table and normal memory
38136 operations to maintain a list of shared libraries. On other
38137 platforms, the operating system manages loaded libraries.
38138 @value{GDBN} can not retrieve the list of currently loaded libraries
38139 through memory operations, so it uses the @samp{qXfer:libraries:read}
38140 packet (@pxref{qXfer library list read}) instead. The remote stub
38141 queries the target's operating system and reports which libraries
38144 The @samp{qXfer:libraries:read} packet returns an XML document which
38145 lists loaded libraries and their offsets. Each library has an
38146 associated name and one or more segment or section base addresses,
38147 which report where the library was loaded in memory.
38149 For the common case of libraries that are fully linked binaries, the
38150 library should have a list of segments. If the target supports
38151 dynamic linking of a relocatable object file, its library XML element
38152 should instead include a list of allocated sections. The segment or
38153 section bases are start addresses, not relocation offsets; they do not
38154 depend on the library's link-time base addresses.
38156 @value{GDBN} must be linked with the Expat library to support XML
38157 library lists. @xref{Expat}.
38159 A simple memory map, with one loaded library relocated by a single
38160 offset, looks like this:
38164 <library name="/lib/libc.so.6">
38165 <segment address="0x10000000"/>
38170 Another simple memory map, with one loaded library with three
38171 allocated sections (.text, .data, .bss), looks like this:
38175 <library name="sharedlib.o">
38176 <section address="0x10000000"/>
38177 <section address="0x20000000"/>
38178 <section address="0x30000000"/>
38183 The format of a library list is described by this DTD:
38186 <!-- library-list: Root element with versioning -->
38187 <!ELEMENT library-list (library)*>
38188 <!ATTLIST library-list version CDATA #FIXED "1.0">
38189 <!ELEMENT library (segment*, section*)>
38190 <!ATTLIST library name CDATA #REQUIRED>
38191 <!ELEMENT segment EMPTY>
38192 <!ATTLIST segment address CDATA #REQUIRED>
38193 <!ELEMENT section EMPTY>
38194 <!ATTLIST section address CDATA #REQUIRED>
38197 In addition, segments and section descriptors cannot be mixed within a
38198 single library element, and you must supply at least one segment or
38199 section for each library.
38201 @node Library List Format for SVR4 Targets
38202 @section Library List Format for SVR4 Targets
38203 @cindex library list format, remote protocol
38205 On SVR4 platforms @value{GDBN} can use the symbol table of a dynamic loader
38206 (e.g.@: @file{ld.so}) and normal memory operations to maintain a list of
38207 shared libraries. Still a special library list provided by this packet is
38208 more efficient for the @value{GDBN} remote protocol.
38210 The @samp{qXfer:libraries-svr4:read} packet returns an XML document which lists
38211 loaded libraries and their SVR4 linker parameters. For each library on SVR4
38212 target, the following parameters are reported:
38216 @code{name}, the absolute file name from the @code{l_name} field of
38217 @code{struct link_map}.
38219 @code{lm} with address of @code{struct link_map} used for TLS
38220 (Thread Local Storage) access.
38222 @code{l_addr}, the displacement as read from the field @code{l_addr} of
38223 @code{struct link_map}. For prelinked libraries this is not an absolute
38224 memory address. It is a displacement of absolute memory address against
38225 address the file was prelinked to during the library load.
38227 @code{l_ld}, which is memory address of the @code{PT_DYNAMIC} segment
38230 Additionally the single @code{main-lm} attribute specifies address of
38231 @code{struct link_map} used for the main executable. This parameter is used
38232 for TLS access and its presence is optional.
38234 @value{GDBN} must be linked with the Expat library to support XML
38235 SVR4 library lists. @xref{Expat}.
38237 A simple memory map, with two loaded libraries (which do not use prelink),
38241 <library-list-svr4 version="1.0" main-lm="0xe4f8f8">
38242 <library name="/lib/ld-linux.so.2" lm="0xe4f51c" l_addr="0xe2d000"
38244 <library name="/lib/libc.so.6" lm="0xe4fbe8" l_addr="0x154000"
38246 </library-list-svr>
38249 The format of an SVR4 library list is described by this DTD:
38252 <!-- library-list-svr4: Root element with versioning -->
38253 <!ELEMENT library-list-svr4 (library)*>
38254 <!ATTLIST library-list-svr4 version CDATA #FIXED "1.0">
38255 <!ATTLIST library-list-svr4 main-lm CDATA #IMPLIED>
38256 <!ELEMENT library EMPTY>
38257 <!ATTLIST library name CDATA #REQUIRED>
38258 <!ATTLIST library lm CDATA #REQUIRED>
38259 <!ATTLIST library l_addr CDATA #REQUIRED>
38260 <!ATTLIST library l_ld CDATA #REQUIRED>
38263 @node Memory Map Format
38264 @section Memory Map Format
38265 @cindex memory map format
38267 To be able to write into flash memory, @value{GDBN} needs to obtain a
38268 memory map from the target. This section describes the format of the
38271 The memory map is obtained using the @samp{qXfer:memory-map:read}
38272 (@pxref{qXfer memory map read}) packet and is an XML document that
38273 lists memory regions.
38275 @value{GDBN} must be linked with the Expat library to support XML
38276 memory maps. @xref{Expat}.
38278 The top-level structure of the document is shown below:
38281 <?xml version="1.0"?>
38282 <!DOCTYPE memory-map
38283 PUBLIC "+//IDN gnu.org//DTD GDB Memory Map V1.0//EN"
38284 "http://sourceware.org/gdb/gdb-memory-map.dtd">
38290 Each region can be either:
38295 A region of RAM starting at @var{addr} and extending for @var{length}
38299 <memory type="ram" start="@var{addr}" length="@var{length}"/>
38304 A region of read-only memory:
38307 <memory type="rom" start="@var{addr}" length="@var{length}"/>
38312 A region of flash memory, with erasure blocks @var{blocksize}
38316 <memory type="flash" start="@var{addr}" length="@var{length}">
38317 <property name="blocksize">@var{blocksize}</property>
38323 Regions must not overlap. @value{GDBN} assumes that areas of memory not covered
38324 by the memory map are RAM, and uses the ordinary @samp{M} and @samp{X}
38325 packets to write to addresses in such ranges.
38327 The formal DTD for memory map format is given below:
38330 <!-- ................................................... -->
38331 <!-- Memory Map XML DTD ................................ -->
38332 <!-- File: memory-map.dtd .............................. -->
38333 <!-- .................................... .............. -->
38334 <!-- memory-map.dtd -->
38335 <!-- memory-map: Root element with versioning -->
38336 <!ELEMENT memory-map (memory | property)>
38337 <!ATTLIST memory-map version CDATA #FIXED "1.0.0">
38338 <!ELEMENT memory (property)>
38339 <!-- memory: Specifies a memory region,
38340 and its type, or device. -->
38341 <!ATTLIST memory type CDATA #REQUIRED
38342 start CDATA #REQUIRED
38343 length CDATA #REQUIRED
38344 device CDATA #IMPLIED>
38345 <!-- property: Generic attribute tag -->
38346 <!ELEMENT property (#PCDATA | property)*>
38347 <!ATTLIST property name CDATA #REQUIRED>
38350 @node Thread List Format
38351 @section Thread List Format
38352 @cindex thread list format
38354 To efficiently update the list of threads and their attributes,
38355 @value{GDBN} issues the @samp{qXfer:threads:read} packet
38356 (@pxref{qXfer threads read}) and obtains the XML document with
38357 the following structure:
38360 <?xml version="1.0"?>
38362 <thread id="id" core="0">
38363 ... description ...
38368 Each @samp{thread} element must have the @samp{id} attribute that
38369 identifies the thread (@pxref{thread-id syntax}). The
38370 @samp{core} attribute, if present, specifies which processor core
38371 the thread was last executing on. The content of the of @samp{thread}
38372 element is interpreted as human-readable auxilliary information.
38374 @node Traceframe Info Format
38375 @section Traceframe Info Format
38376 @cindex traceframe info format
38378 To be able to know which objects in the inferior can be examined when
38379 inspecting a tracepoint hit, @value{GDBN} needs to obtain the list of
38380 memory ranges, registers and trace state variables that have been
38381 collected in a traceframe.
38383 This list is obtained using the @samp{qXfer:traceframe-info:read}
38384 (@pxref{qXfer traceframe info read}) packet and is an XML document.
38386 @value{GDBN} must be linked with the Expat library to support XML
38387 traceframe info discovery. @xref{Expat}.
38389 The top-level structure of the document is shown below:
38392 <?xml version="1.0"?>
38393 <!DOCTYPE traceframe-info
38394 PUBLIC "+//IDN gnu.org//DTD GDB Memory Map V1.0//EN"
38395 "http://sourceware.org/gdb/gdb-traceframe-info.dtd">
38401 Each traceframe block can be either:
38406 A region of collected memory starting at @var{addr} and extending for
38407 @var{length} bytes from there:
38410 <memory start="@var{addr}" length="@var{length}"/>
38414 A block indicating trace state variable numbered @var{number} has been
38418 <tvar id="@var{number}"/>
38423 The formal DTD for the traceframe info format is given below:
38426 <!ELEMENT traceframe-info (memory | tvar)* >
38427 <!ATTLIST traceframe-info version CDATA #FIXED "1.0">
38429 <!ELEMENT memory EMPTY>
38430 <!ATTLIST memory start CDATA #REQUIRED
38431 length CDATA #REQUIRED>
38433 <!ATTLIST tvar id CDATA #REQUIRED>
38436 @node Branch Trace Format
38437 @section Branch Trace Format
38438 @cindex branch trace format
38440 In order to display the branch trace of an inferior thread,
38441 @value{GDBN} needs to obtain the list of branches. This list is
38442 represented as list of sequential code blocks that are connected via
38443 branches. The code in each block has been executed sequentially.
38445 This list is obtained using the @samp{qXfer:btrace:read}
38446 (@pxref{qXfer btrace read}) packet and is an XML document.
38448 @value{GDBN} must be linked with the Expat library to support XML
38449 traceframe info discovery. @xref{Expat}.
38451 The top-level structure of the document is shown below:
38454 <?xml version="1.0"?>
38456 PUBLIC "+//IDN gnu.org//DTD GDB Branch Trace V1.0//EN"
38457 "http://sourceware.org/gdb/gdb-btrace.dtd">
38466 A block of sequentially executed instructions starting at @var{begin}
38467 and ending at @var{end}:
38470 <block begin="@var{begin}" end="@var{end}"/>
38475 The formal DTD for the branch trace format is given below:
38478 <!ELEMENT btrace (block)* >
38479 <!ATTLIST btrace version CDATA #FIXED "1.0">
38481 <!ELEMENT block EMPTY>
38482 <!ATTLIST block begin CDATA #REQUIRED
38483 end CDATA #REQUIRED>
38486 @include agentexpr.texi
38488 @node Target Descriptions
38489 @appendix Target Descriptions
38490 @cindex target descriptions
38492 One of the challenges of using @value{GDBN} to debug embedded systems
38493 is that there are so many minor variants of each processor
38494 architecture in use. It is common practice for vendors to start with
38495 a standard processor core --- ARM, PowerPC, or @acronym{MIPS}, for example ---
38496 and then make changes to adapt it to a particular market niche. Some
38497 architectures have hundreds of variants, available from dozens of
38498 vendors. This leads to a number of problems:
38502 With so many different customized processors, it is difficult for
38503 the @value{GDBN} maintainers to keep up with the changes.
38505 Since individual variants may have short lifetimes or limited
38506 audiences, it may not be worthwhile to carry information about every
38507 variant in the @value{GDBN} source tree.
38509 When @value{GDBN} does support the architecture of the embedded system
38510 at hand, the task of finding the correct architecture name to give the
38511 @command{set architecture} command can be error-prone.
38514 To address these problems, the @value{GDBN} remote protocol allows a
38515 target system to not only identify itself to @value{GDBN}, but to
38516 actually describe its own features. This lets @value{GDBN} support
38517 processor variants it has never seen before --- to the extent that the
38518 descriptions are accurate, and that @value{GDBN} understands them.
38520 @value{GDBN} must be linked with the Expat library to support XML
38521 target descriptions. @xref{Expat}.
38524 * Retrieving Descriptions:: How descriptions are fetched from a target.
38525 * Target Description Format:: The contents of a target description.
38526 * Predefined Target Types:: Standard types available for target
38528 * Standard Target Features:: Features @value{GDBN} knows about.
38531 @node Retrieving Descriptions
38532 @section Retrieving Descriptions
38534 Target descriptions can be read from the target automatically, or
38535 specified by the user manually. The default behavior is to read the
38536 description from the target. @value{GDBN} retrieves it via the remote
38537 protocol using @samp{qXfer} requests (@pxref{General Query Packets,
38538 qXfer}). The @var{annex} in the @samp{qXfer} packet will be
38539 @samp{target.xml}. The contents of the @samp{target.xml} annex are an
38540 XML document, of the form described in @ref{Target Description
38543 Alternatively, you can specify a file to read for the target description.
38544 If a file is set, the target will not be queried. The commands to
38545 specify a file are:
38548 @cindex set tdesc filename
38549 @item set tdesc filename @var{path}
38550 Read the target description from @var{path}.
38552 @cindex unset tdesc filename
38553 @item unset tdesc filename
38554 Do not read the XML target description from a file. @value{GDBN}
38555 will use the description supplied by the current target.
38557 @cindex show tdesc filename
38558 @item show tdesc filename
38559 Show the filename to read for a target description, if any.
38563 @node Target Description Format
38564 @section Target Description Format
38565 @cindex target descriptions, XML format
38567 A target description annex is an @uref{http://www.w3.org/XML/, XML}
38568 document which complies with the Document Type Definition provided in
38569 the @value{GDBN} sources in @file{gdb/features/gdb-target.dtd}. This
38570 means you can use generally available tools like @command{xmllint} to
38571 check that your feature descriptions are well-formed and valid.
38572 However, to help people unfamiliar with XML write descriptions for
38573 their targets, we also describe the grammar here.
38575 Target descriptions can identify the architecture of the remote target
38576 and (for some architectures) provide information about custom register
38577 sets. They can also identify the OS ABI of the remote target.
38578 @value{GDBN} can use this information to autoconfigure for your
38579 target, or to warn you if you connect to an unsupported target.
38581 Here is a simple target description:
38584 <target version="1.0">
38585 <architecture>i386:x86-64</architecture>
38590 This minimal description only says that the target uses
38591 the x86-64 architecture.
38593 A target description has the following overall form, with [ ] marking
38594 optional elements and @dots{} marking repeatable elements. The elements
38595 are explained further below.
38598 <?xml version="1.0"?>
38599 <!DOCTYPE target SYSTEM "gdb-target.dtd">
38600 <target version="1.0">
38601 @r{[}@var{architecture}@r{]}
38602 @r{[}@var{osabi}@r{]}
38603 @r{[}@var{compatible}@r{]}
38604 @r{[}@var{feature}@dots{}@r{]}
38609 The description is generally insensitive to whitespace and line
38610 breaks, under the usual common-sense rules. The XML version
38611 declaration and document type declaration can generally be omitted
38612 (@value{GDBN} does not require them), but specifying them may be
38613 useful for XML validation tools. The @samp{version} attribute for
38614 @samp{<target>} may also be omitted, but we recommend
38615 including it; if future versions of @value{GDBN} use an incompatible
38616 revision of @file{gdb-target.dtd}, they will detect and report
38617 the version mismatch.
38619 @subsection Inclusion
38620 @cindex target descriptions, inclusion
38623 @cindex <xi:include>
38626 It can sometimes be valuable to split a target description up into
38627 several different annexes, either for organizational purposes, or to
38628 share files between different possible target descriptions. You can
38629 divide a description into multiple files by replacing any element of
38630 the target description with an inclusion directive of the form:
38633 <xi:include href="@var{document}"/>
38637 When @value{GDBN} encounters an element of this form, it will retrieve
38638 the named XML @var{document}, and replace the inclusion directive with
38639 the contents of that document. If the current description was read
38640 using @samp{qXfer}, then so will be the included document;
38641 @var{document} will be interpreted as the name of an annex. If the
38642 current description was read from a file, @value{GDBN} will look for
38643 @var{document} as a file in the same directory where it found the
38644 original description.
38646 @subsection Architecture
38647 @cindex <architecture>
38649 An @samp{<architecture>} element has this form:
38652 <architecture>@var{arch}</architecture>
38655 @var{arch} is one of the architectures from the set accepted by
38656 @code{set architecture} (@pxref{Targets, ,Specifying a Debugging Target}).
38659 @cindex @code{<osabi>}
38661 This optional field was introduced in @value{GDBN} version 7.0.
38662 Previous versions of @value{GDBN} ignore it.
38664 An @samp{<osabi>} element has this form:
38667 <osabi>@var{abi-name}</osabi>
38670 @var{abi-name} is an OS ABI name from the same selection accepted by
38671 @w{@code{set osabi}} (@pxref{ABI, ,Configuring the Current ABI}).
38673 @subsection Compatible Architecture
38674 @cindex @code{<compatible>}
38676 This optional field was introduced in @value{GDBN} version 7.0.
38677 Previous versions of @value{GDBN} ignore it.
38679 A @samp{<compatible>} element has this form:
38682 <compatible>@var{arch}</compatible>
38685 @var{arch} is one of the architectures from the set accepted by
38686 @code{set architecture} (@pxref{Targets, ,Specifying a Debugging Target}).
38688 A @samp{<compatible>} element is used to specify that the target
38689 is able to run binaries in some other than the main target architecture
38690 given by the @samp{<architecture>} element. For example, on the
38691 Cell Broadband Engine, the main architecture is @code{powerpc:common}
38692 or @code{powerpc:common64}, but the system is able to run binaries
38693 in the @code{spu} architecture as well. The way to describe this
38694 capability with @samp{<compatible>} is as follows:
38697 <architecture>powerpc:common</architecture>
38698 <compatible>spu</compatible>
38701 @subsection Features
38704 Each @samp{<feature>} describes some logical portion of the target
38705 system. Features are currently used to describe available CPU
38706 registers and the types of their contents. A @samp{<feature>} element
38710 <feature name="@var{name}">
38711 @r{[}@var{type}@dots{}@r{]}
38717 Each feature's name should be unique within the description. The name
38718 of a feature does not matter unless @value{GDBN} has some special
38719 knowledge of the contents of that feature; if it does, the feature
38720 should have its standard name. @xref{Standard Target Features}.
38724 Any register's value is a collection of bits which @value{GDBN} must
38725 interpret. The default interpretation is a two's complement integer,
38726 but other types can be requested by name in the register description.
38727 Some predefined types are provided by @value{GDBN} (@pxref{Predefined
38728 Target Types}), and the description can define additional composite types.
38730 Each type element must have an @samp{id} attribute, which gives
38731 a unique (within the containing @samp{<feature>}) name to the type.
38732 Types must be defined before they are used.
38735 Some targets offer vector registers, which can be treated as arrays
38736 of scalar elements. These types are written as @samp{<vector>} elements,
38737 specifying the array element type, @var{type}, and the number of elements,
38741 <vector id="@var{id}" type="@var{type}" count="@var{count}"/>
38745 If a register's value is usefully viewed in multiple ways, define it
38746 with a union type containing the useful representations. The
38747 @samp{<union>} element contains one or more @samp{<field>} elements,
38748 each of which has a @var{name} and a @var{type}:
38751 <union id="@var{id}">
38752 <field name="@var{name}" type="@var{type}"/>
38758 If a register's value is composed from several separate values, define
38759 it with a structure type. There are two forms of the @samp{<struct>}
38760 element; a @samp{<struct>} element must either contain only bitfields
38761 or contain no bitfields. If the structure contains only bitfields,
38762 its total size in bytes must be specified, each bitfield must have an
38763 explicit start and end, and bitfields are automatically assigned an
38764 integer type. The field's @var{start} should be less than or
38765 equal to its @var{end}, and zero represents the least significant bit.
38768 <struct id="@var{id}" size="@var{size}">
38769 <field name="@var{name}" start="@var{start}" end="@var{end}"/>
38774 If the structure contains no bitfields, then each field has an
38775 explicit type, and no implicit padding is added.
38778 <struct id="@var{id}">
38779 <field name="@var{name}" type="@var{type}"/>
38785 If a register's value is a series of single-bit flags, define it with
38786 a flags type. The @samp{<flags>} element has an explicit @var{size}
38787 and contains one or more @samp{<field>} elements. Each field has a
38788 @var{name}, a @var{start}, and an @var{end}. Only single-bit flags
38792 <flags id="@var{id}" size="@var{size}">
38793 <field name="@var{name}" start="@var{start}" end="@var{end}"/>
38798 @subsection Registers
38801 Each register is represented as an element with this form:
38804 <reg name="@var{name}"
38805 bitsize="@var{size}"
38806 @r{[}regnum="@var{num}"@r{]}
38807 @r{[}save-restore="@var{save-restore}"@r{]}
38808 @r{[}type="@var{type}"@r{]}
38809 @r{[}group="@var{group}"@r{]}/>
38813 The components are as follows:
38818 The register's name; it must be unique within the target description.
38821 The register's size, in bits.
38824 The register's number. If omitted, a register's number is one greater
38825 than that of the previous register (either in the current feature or in
38826 a preceding feature); the first register in the target description
38827 defaults to zero. This register number is used to read or write
38828 the register; e.g.@: it is used in the remote @code{p} and @code{P}
38829 packets, and registers appear in the @code{g} and @code{G} packets
38830 in order of increasing register number.
38833 Whether the register should be preserved across inferior function
38834 calls; this must be either @code{yes} or @code{no}. The default is
38835 @code{yes}, which is appropriate for most registers except for
38836 some system control registers; this is not related to the target's
38840 The type of the register. @var{type} may be a predefined type, a type
38841 defined in the current feature, or one of the special types @code{int}
38842 and @code{float}. @code{int} is an integer type of the correct size
38843 for @var{bitsize}, and @code{float} is a floating point type (in the
38844 architecture's normal floating point format) of the correct size for
38845 @var{bitsize}. The default is @code{int}.
38848 The register group to which this register belongs. @var{group} must
38849 be either @code{general}, @code{float}, or @code{vector}. If no
38850 @var{group} is specified, @value{GDBN} will not display the register
38851 in @code{info registers}.
38855 @node Predefined Target Types
38856 @section Predefined Target Types
38857 @cindex target descriptions, predefined types
38859 Type definitions in the self-description can build up composite types
38860 from basic building blocks, but can not define fundamental types. Instead,
38861 standard identifiers are provided by @value{GDBN} for the fundamental
38862 types. The currently supported types are:
38871 Signed integer types holding the specified number of bits.
38878 Unsigned integer types holding the specified number of bits.
38882 Pointers to unspecified code and data. The program counter and
38883 any dedicated return address register may be marked as code
38884 pointers; printing a code pointer converts it into a symbolic
38885 address. The stack pointer and any dedicated address registers
38886 may be marked as data pointers.
38889 Single precision IEEE floating point.
38892 Double precision IEEE floating point.
38895 The 12-byte extended precision format used by ARM FPA registers.
38898 The 10-byte extended precision format used by x87 registers.
38901 32bit @sc{eflags} register used by x86.
38904 32bit @sc{mxcsr} register used by x86.
38908 @node Standard Target Features
38909 @section Standard Target Features
38910 @cindex target descriptions, standard features
38912 A target description must contain either no registers or all the
38913 target's registers. If the description contains no registers, then
38914 @value{GDBN} will assume a default register layout, selected based on
38915 the architecture. If the description contains any registers, the
38916 default layout will not be used; the standard registers must be
38917 described in the target description, in such a way that @value{GDBN}
38918 can recognize them.
38920 This is accomplished by giving specific names to feature elements
38921 which contain standard registers. @value{GDBN} will look for features
38922 with those names and verify that they contain the expected registers;
38923 if any known feature is missing required registers, or if any required
38924 feature is missing, @value{GDBN} will reject the target
38925 description. You can add additional registers to any of the
38926 standard features --- @value{GDBN} will display them just as if
38927 they were added to an unrecognized feature.
38929 This section lists the known features and their expected contents.
38930 Sample XML documents for these features are included in the
38931 @value{GDBN} source tree, in the directory @file{gdb/features}.
38933 Names recognized by @value{GDBN} should include the name of the
38934 company or organization which selected the name, and the overall
38935 architecture to which the feature applies; so e.g.@: the feature
38936 containing ARM core registers is named @samp{org.gnu.gdb.arm.core}.
38938 The names of registers are not case sensitive for the purpose
38939 of recognizing standard features, but @value{GDBN} will only display
38940 registers using the capitalization used in the description.
38943 * AArch64 Features::
38948 * Nios II Features::
38949 * PowerPC Features::
38950 * S/390 and System z Features::
38955 @node AArch64 Features
38956 @subsection AArch64 Features
38957 @cindex target descriptions, AArch64 features
38959 The @samp{org.gnu.gdb.aarch64.core} feature is required for AArch64
38960 targets. It should contain registers @samp{x0} through @samp{x30},
38961 @samp{sp}, @samp{pc}, and @samp{cpsr}.
38963 The @samp{org.gnu.gdb.aarch64.fpu} feature is optional. If present,
38964 it should contain registers @samp{v0} through @samp{v31}, @samp{fpsr},
38968 @subsection ARM Features
38969 @cindex target descriptions, ARM features
38971 The @samp{org.gnu.gdb.arm.core} feature is required for non-M-profile
38973 It should contain registers @samp{r0} through @samp{r13}, @samp{sp},
38974 @samp{lr}, @samp{pc}, and @samp{cpsr}.
38976 For M-profile targets (e.g. Cortex-M3), the @samp{org.gnu.gdb.arm.core}
38977 feature is replaced by @samp{org.gnu.gdb.arm.m-profile}. It should contain
38978 registers @samp{r0} through @samp{r13}, @samp{sp}, @samp{lr}, @samp{pc},
38981 The @samp{org.gnu.gdb.arm.fpa} feature is optional. If present, it
38982 should contain registers @samp{f0} through @samp{f7} and @samp{fps}.
38984 The @samp{org.gnu.gdb.xscale.iwmmxt} feature is optional. If present,
38985 it should contain at least registers @samp{wR0} through @samp{wR15} and
38986 @samp{wCGR0} through @samp{wCGR3}. The @samp{wCID}, @samp{wCon},
38987 @samp{wCSSF}, and @samp{wCASF} registers are optional.
38989 The @samp{org.gnu.gdb.arm.vfp} feature is optional. If present, it
38990 should contain at least registers @samp{d0} through @samp{d15}. If
38991 they are present, @samp{d16} through @samp{d31} should also be included.
38992 @value{GDBN} will synthesize the single-precision registers from
38993 halves of the double-precision registers.
38995 The @samp{org.gnu.gdb.arm.neon} feature is optional. It does not
38996 need to contain registers; it instructs @value{GDBN} to display the
38997 VFP double-precision registers as vectors and to synthesize the
38998 quad-precision registers from pairs of double-precision registers.
38999 If this feature is present, @samp{org.gnu.gdb.arm.vfp} must also
39000 be present and include 32 double-precision registers.
39002 @node i386 Features
39003 @subsection i386 Features
39004 @cindex target descriptions, i386 features
39006 The @samp{org.gnu.gdb.i386.core} feature is required for i386/amd64
39007 targets. It should describe the following registers:
39011 @samp{eax} through @samp{edi} plus @samp{eip} for i386
39013 @samp{rax} through @samp{r15} plus @samp{rip} for amd64
39015 @samp{eflags}, @samp{cs}, @samp{ss}, @samp{ds}, @samp{es},
39016 @samp{fs}, @samp{gs}
39018 @samp{st0} through @samp{st7}
39020 @samp{fctrl}, @samp{fstat}, @samp{ftag}, @samp{fiseg}, @samp{fioff},
39021 @samp{foseg}, @samp{fooff} and @samp{fop}
39024 The register sets may be different, depending on the target.
39026 The @samp{org.gnu.gdb.i386.sse} feature is optional. It should
39027 describe registers:
39031 @samp{xmm0} through @samp{xmm7} for i386
39033 @samp{xmm0} through @samp{xmm15} for amd64
39038 The @samp{org.gnu.gdb.i386.avx} feature is optional and requires the
39039 @samp{org.gnu.gdb.i386.sse} feature. It should
39040 describe the upper 128 bits of @sc{ymm} registers:
39044 @samp{ymm0h} through @samp{ymm7h} for i386
39046 @samp{ymm0h} through @samp{ymm15h} for amd64
39049 The @samp{org.gnu.gdb.i386.mpx} is an optional feature representing Intel(R)
39050 Memory Protection Extension (MPX). It should describe the following registers:
39054 @samp{bnd0raw} through @samp{bnd3raw} for i386 and amd64.
39056 @samp{bndcfgu} and @samp{bndstatus} for i386 and amd64.
39059 The @samp{org.gnu.gdb.i386.linux} feature is optional. It should
39060 describe a single register, @samp{orig_eax}.
39062 @node MIPS Features
39063 @subsection @acronym{MIPS} Features
39064 @cindex target descriptions, @acronym{MIPS} features
39066 The @samp{org.gnu.gdb.mips.cpu} feature is required for @acronym{MIPS} targets.
39067 It should contain registers @samp{r0} through @samp{r31}, @samp{lo},
39068 @samp{hi}, and @samp{pc}. They may be 32-bit or 64-bit depending
39071 The @samp{org.gnu.gdb.mips.cp0} feature is also required. It should
39072 contain at least the @samp{status}, @samp{badvaddr}, and @samp{cause}
39073 registers. They may be 32-bit or 64-bit depending on the target.
39075 The @samp{org.gnu.gdb.mips.fpu} feature is currently required, though
39076 it may be optional in a future version of @value{GDBN}. It should
39077 contain registers @samp{f0} through @samp{f31}, @samp{fcsr}, and
39078 @samp{fir}. They may be 32-bit or 64-bit depending on the target.
39080 The @samp{org.gnu.gdb.mips.dsp} feature is optional. It should
39081 contain registers @samp{hi1} through @samp{hi3}, @samp{lo1} through
39082 @samp{lo3}, and @samp{dspctl}. The @samp{dspctl} register should
39083 be 32-bit and the rest may be 32-bit or 64-bit depending on the target.
39085 The @samp{org.gnu.gdb.mips.linux} feature is optional. It should
39086 contain a single register, @samp{restart}, which is used by the
39087 Linux kernel to control restartable syscalls.
39089 @node M68K Features
39090 @subsection M68K Features
39091 @cindex target descriptions, M68K features
39094 @item @samp{org.gnu.gdb.m68k.core}
39095 @itemx @samp{org.gnu.gdb.coldfire.core}
39096 @itemx @samp{org.gnu.gdb.fido.core}
39097 One of those features must be always present.
39098 The feature that is present determines which flavor of m68k is
39099 used. The feature that is present should contain registers
39100 @samp{d0} through @samp{d7}, @samp{a0} through @samp{a5}, @samp{fp},
39101 @samp{sp}, @samp{ps} and @samp{pc}.
39103 @item @samp{org.gnu.gdb.coldfire.fp}
39104 This feature is optional. If present, it should contain registers
39105 @samp{fp0} through @samp{fp7}, @samp{fpcontrol}, @samp{fpstatus} and
39109 @node Nios II Features
39110 @subsection Nios II Features
39111 @cindex target descriptions, Nios II features
39113 The @samp{org.gnu.gdb.nios2.cpu} feature is required for Nios II
39114 targets. It should contain the 32 core registers (@samp{zero},
39115 @samp{at}, @samp{r2} through @samp{r23}, @samp{et} through @samp{ra}),
39116 @samp{pc}, and the 16 control registers (@samp{status} through
39119 @node PowerPC Features
39120 @subsection PowerPC Features
39121 @cindex target descriptions, PowerPC features
39123 The @samp{org.gnu.gdb.power.core} feature is required for PowerPC
39124 targets. It should contain registers @samp{r0} through @samp{r31},
39125 @samp{pc}, @samp{msr}, @samp{cr}, @samp{lr}, @samp{ctr}, and
39126 @samp{xer}. They may be 32-bit or 64-bit depending on the target.
39128 The @samp{org.gnu.gdb.power.fpu} feature is optional. It should
39129 contain registers @samp{f0} through @samp{f31} and @samp{fpscr}.
39131 The @samp{org.gnu.gdb.power.altivec} feature is optional. It should
39132 contain registers @samp{vr0} through @samp{vr31}, @samp{vscr},
39135 The @samp{org.gnu.gdb.power.vsx} feature is optional. It should
39136 contain registers @samp{vs0h} through @samp{vs31h}. @value{GDBN}
39137 will combine these registers with the floating point registers
39138 (@samp{f0} through @samp{f31}) and the altivec registers (@samp{vr0}
39139 through @samp{vr31}) to present the 128-bit wide registers @samp{vs0}
39140 through @samp{vs63}, the set of vector registers for POWER7.
39142 The @samp{org.gnu.gdb.power.spe} feature is optional. It should
39143 contain registers @samp{ev0h} through @samp{ev31h}, @samp{acc}, and
39144 @samp{spefscr}. SPE targets should provide 32-bit registers in
39145 @samp{org.gnu.gdb.power.core} and provide the upper halves in
39146 @samp{ev0h} through @samp{ev31h}. @value{GDBN} will combine
39147 these to present registers @samp{ev0} through @samp{ev31} to the
39150 @node S/390 and System z Features
39151 @subsection S/390 and System z Features
39152 @cindex target descriptions, S/390 features
39153 @cindex target descriptions, System z features
39155 The @samp{org.gnu.gdb.s390.core} feature is required for S/390 and
39156 System z targets. It should contain the PSW and the 16 general
39157 registers. In particular, System z targets should provide the 64-bit
39158 registers @samp{pswm}, @samp{pswa}, and @samp{r0} through @samp{r15}.
39159 S/390 targets should provide the 32-bit versions of these registers.
39160 A System z target that runs in 31-bit addressing mode should provide
39161 32-bit versions of @samp{pswm} and @samp{pswa}, as well as the general
39162 register's upper halves @samp{r0h} through @samp{r15h}, and their
39163 lower halves @samp{r0l} through @samp{r15l}.
39165 The @samp{org.gnu.gdb.s390.fpr} feature is required. It should
39166 contain the 64-bit registers @samp{f0} through @samp{f15}, and
39169 The @samp{org.gnu.gdb.s390.acr} feature is required. It should
39170 contain the 32-bit registers @samp{acr0} through @samp{acr15}.
39172 The @samp{org.gnu.gdb.s390.linux} feature is optional. It should
39173 contain the register @samp{orig_r2}, which is 64-bit wide on System z
39174 targets and 32-bit otherwise. In addition, the feature may contain
39175 the @samp{last_break} register, whose width depends on the addressing
39176 mode, as well as the @samp{system_call} register, which is always
39179 The @samp{org.gnu.gdb.s390.tdb} feature is optional. It should
39180 contain the 64-bit registers @samp{tdb0}, @samp{tac}, @samp{tct},
39181 @samp{atia}, and @samp{tr0} through @samp{tr15}.
39183 @node TIC6x Features
39184 @subsection TMS320C6x Features
39185 @cindex target descriptions, TIC6x features
39186 @cindex target descriptions, TMS320C6x features
39187 The @samp{org.gnu.gdb.tic6x.core} feature is required for TMS320C6x
39188 targets. It should contain registers @samp{A0} through @samp{A15},
39189 registers @samp{B0} through @samp{B15}, @samp{CSR} and @samp{PC}.
39191 The @samp{org.gnu.gdb.tic6x.gp} feature is optional. It should
39192 contain registers @samp{A16} through @samp{A31} and @samp{B16}
39193 through @samp{B31}.
39195 The @samp{org.gnu.gdb.tic6x.c6xp} feature is optional. It should
39196 contain registers @samp{TSR}, @samp{ILC} and @samp{RILC}.
39198 @node Operating System Information
39199 @appendix Operating System Information
39200 @cindex operating system information
39206 Users of @value{GDBN} often wish to obtain information about the state of
39207 the operating system running on the target---for example the list of
39208 processes, or the list of open files. This section describes the
39209 mechanism that makes it possible. This mechanism is similar to the
39210 target features mechanism (@pxref{Target Descriptions}), but focuses
39211 on a different aspect of target.
39213 Operating system information is retrived from the target via the
39214 remote protocol, using @samp{qXfer} requests (@pxref{qXfer osdata
39215 read}). The object name in the request should be @samp{osdata}, and
39216 the @var{annex} identifies the data to be fetched.
39219 @appendixsection Process list
39220 @cindex operating system information, process list
39222 When requesting the process list, the @var{annex} field in the
39223 @samp{qXfer} request should be @samp{processes}. The returned data is
39224 an XML document. The formal syntax of this document is defined in
39225 @file{gdb/features/osdata.dtd}.
39227 An example document is:
39230 <?xml version="1.0"?>
39231 <!DOCTYPE target SYSTEM "osdata.dtd">
39232 <osdata type="processes">
39234 <column name="pid">1</column>
39235 <column name="user">root</column>
39236 <column name="command">/sbin/init</column>
39237 <column name="cores">1,2,3</column>
39242 Each item should include a column whose name is @samp{pid}. The value
39243 of that column should identify the process on the target. The
39244 @samp{user} and @samp{command} columns are optional, and will be
39245 displayed by @value{GDBN}. The @samp{cores} column, if present,
39246 should contain a comma-separated list of cores that this process
39247 is running on. Target may provide additional columns,
39248 which @value{GDBN} currently ignores.
39250 @node Trace File Format
39251 @appendix Trace File Format
39252 @cindex trace file format
39254 The trace file comes in three parts: a header, a textual description
39255 section, and a trace frame section with binary data.
39257 The header has the form @code{\x7fTRACE0\n}. The first byte is
39258 @code{0x7f} so as to indicate that the file contains binary data,
39259 while the @code{0} is a version number that may have different values
39262 The description section consists of multiple lines of @sc{ascii} text
39263 separated by newline characters (@code{0xa}). The lines may include a
39264 variety of optional descriptive or context-setting information, such
39265 as tracepoint definitions or register set size. @value{GDBN} will
39266 ignore any line that it does not recognize. An empty line marks the end
39269 @c FIXME add some specific types of data
39271 The trace frame section consists of a number of consecutive frames.
39272 Each frame begins with a two-byte tracepoint number, followed by a
39273 four-byte size giving the amount of data in the frame. The data in
39274 the frame consists of a number of blocks, each introduced by a
39275 character indicating its type (at least register, memory, and trace
39276 state variable). The data in this section is raw binary, not a
39277 hexadecimal or other encoding; its endianness matches the target's
39280 @c FIXME bi-arch may require endianness/arch info in description section
39283 @item R @var{bytes}
39284 Register block. The number and ordering of bytes matches that of a
39285 @code{g} packet in the remote protocol. Note that these are the
39286 actual bytes, in target order and @value{GDBN} register order, not a
39287 hexadecimal encoding.
39289 @item M @var{address} @var{length} @var{bytes}...
39290 Memory block. This is a contiguous block of memory, at the 8-byte
39291 address @var{address}, with a 2-byte length @var{length}, followed by
39292 @var{length} bytes.
39294 @item V @var{number} @var{value}
39295 Trace state variable block. This records the 8-byte signed value
39296 @var{value} of trace state variable numbered @var{number}.
39300 Future enhancements of the trace file format may include additional types
39303 @node Index Section Format
39304 @appendix @code{.gdb_index} section format
39305 @cindex .gdb_index section format
39306 @cindex index section format
39308 This section documents the index section that is created by @code{save
39309 gdb-index} (@pxref{Index Files}). The index section is
39310 DWARF-specific; some knowledge of DWARF is assumed in this
39313 The mapped index file format is designed to be directly
39314 @code{mmap}able on any architecture. In most cases, a datum is
39315 represented using a little-endian 32-bit integer value, called an
39316 @code{offset_type}. Big endian machines must byte-swap the values
39317 before using them. Exceptions to this rule are noted. The data is
39318 laid out such that alignment is always respected.
39320 A mapped index consists of several areas, laid out in order.
39324 The file header. This is a sequence of values, of @code{offset_type}
39325 unless otherwise noted:
39329 The version number, currently 8. Versions 1, 2 and 3 are obsolete.
39330 Version 4 uses a different hashing function from versions 5 and 6.
39331 Version 6 includes symbols for inlined functions, whereas versions 4
39332 and 5 do not. Version 7 adds attributes to the CU indices in the
39333 symbol table. Version 8 specifies that symbols from DWARF type units
39334 (@samp{DW_TAG_type_unit}) refer to the type unit's symbol table and not the
39335 compilation unit (@samp{DW_TAG_comp_unit}) using the type.
39337 @value{GDBN} will only read version 4, 5, or 6 indices
39338 by specifying @code{set use-deprecated-index-sections on}.
39339 GDB has a workaround for potentially broken version 7 indices so it is
39340 currently not flagged as deprecated.
39343 The offset, from the start of the file, of the CU list.
39346 The offset, from the start of the file, of the types CU list. Note
39347 that this area can be empty, in which case this offset will be equal
39348 to the next offset.
39351 The offset, from the start of the file, of the address area.
39354 The offset, from the start of the file, of the symbol table.
39357 The offset, from the start of the file, of the constant pool.
39361 The CU list. This is a sequence of pairs of 64-bit little-endian
39362 values, sorted by the CU offset. The first element in each pair is
39363 the offset of a CU in the @code{.debug_info} section. The second
39364 element in each pair is the length of that CU. References to a CU
39365 elsewhere in the map are done using a CU index, which is just the
39366 0-based index into this table. Note that if there are type CUs, then
39367 conceptually CUs and type CUs form a single list for the purposes of
39371 The types CU list. This is a sequence of triplets of 64-bit
39372 little-endian values. In a triplet, the first value is the CU offset,
39373 the second value is the type offset in the CU, and the third value is
39374 the type signature. The types CU list is not sorted.
39377 The address area. The address area consists of a sequence of address
39378 entries. Each address entry has three elements:
39382 The low address. This is a 64-bit little-endian value.
39385 The high address. This is a 64-bit little-endian value. Like
39386 @code{DW_AT_high_pc}, the value is one byte beyond the end.
39389 The CU index. This is an @code{offset_type} value.
39393 The symbol table. This is an open-addressed hash table. The size of
39394 the hash table is always a power of 2.
39396 Each slot in the hash table consists of a pair of @code{offset_type}
39397 values. The first value is the offset of the symbol's name in the
39398 constant pool. The second value is the offset of the CU vector in the
39401 If both values are 0, then this slot in the hash table is empty. This
39402 is ok because while 0 is a valid constant pool index, it cannot be a
39403 valid index for both a string and a CU vector.
39405 The hash value for a table entry is computed by applying an
39406 iterative hash function to the symbol's name. Starting with an
39407 initial value of @code{r = 0}, each (unsigned) character @samp{c} in
39408 the string is incorporated into the hash using the formula depending on the
39413 The formula is @code{r = r * 67 + c - 113}.
39415 @item Versions 5 to 7
39416 The formula is @code{r = r * 67 + tolower (c) - 113}.
39419 The terminating @samp{\0} is not incorporated into the hash.
39421 The step size used in the hash table is computed via
39422 @code{((hash * 17) & (size - 1)) | 1}, where @samp{hash} is the hash
39423 value, and @samp{size} is the size of the hash table. The step size
39424 is used to find the next candidate slot when handling a hash
39427 The names of C@t{++} symbols in the hash table are canonicalized. We
39428 don't currently have a simple description of the canonicalization
39429 algorithm; if you intend to create new index sections, you must read
39433 The constant pool. This is simply a bunch of bytes. It is organized
39434 so that alignment is correct: CU vectors are stored first, followed by
39437 A CU vector in the constant pool is a sequence of @code{offset_type}
39438 values. The first value is the number of CU indices in the vector.
39439 Each subsequent value is the index and symbol attributes of a CU in
39440 the CU list. This element in the hash table is used to indicate which
39441 CUs define the symbol and how the symbol is used.
39442 See below for the format of each CU index+attributes entry.
39444 A string in the constant pool is zero-terminated.
39447 Attributes were added to CU index values in @code{.gdb_index} version 7.
39448 If a symbol has multiple uses within a CU then there is one
39449 CU index+attributes value for each use.
39451 The format of each CU index+attributes entry is as follows
39457 This is the index of the CU in the CU list.
39459 These bits are reserved for future purposes and must be zero.
39461 The kind of the symbol in the CU.
39465 This value is reserved and should not be used.
39466 By reserving zero the full @code{offset_type} value is backwards compatible
39467 with previous versions of the index.
39469 The symbol is a type.
39471 The symbol is a variable or an enum value.
39473 The symbol is a function.
39475 Any other kind of symbol.
39477 These values are reserved.
39481 This bit is zero if the value is global and one if it is static.
39483 The determination of whether a symbol is global or static is complicated.
39484 The authorative reference is the file @file{dwarf2read.c} in
39485 @value{GDBN} sources.
39489 This pseudo-code describes the computation of a symbol's kind and
39490 global/static attributes in the index.
39493 is_external = get_attribute (die, DW_AT_external);
39494 language = get_attribute (cu_die, DW_AT_language);
39497 case DW_TAG_typedef:
39498 case DW_TAG_base_type:
39499 case DW_TAG_subrange_type:
39503 case DW_TAG_enumerator:
39505 is_static = (language != CPLUS && language != JAVA);
39507 case DW_TAG_subprogram:
39509 is_static = ! (is_external || language == ADA);
39511 case DW_TAG_constant:
39513 is_static = ! is_external;
39515 case DW_TAG_variable:
39517 is_static = ! is_external;
39519 case DW_TAG_namespace:
39523 case DW_TAG_class_type:
39524 case DW_TAG_interface_type:
39525 case DW_TAG_structure_type:
39526 case DW_TAG_union_type:
39527 case DW_TAG_enumeration_type:
39529 is_static = (language != CPLUS && language != JAVA);
39537 @appendix Manual pages
39541 * gdb man:: The GNU Debugger man page
39542 * gdbserver man:: Remote Server for the GNU Debugger man page
39543 * gcore man:: Generate a core file of a running program
39544 * gdbinit man:: gdbinit scripts
39550 @c man title gdb The GNU Debugger
39552 @c man begin SYNOPSIS gdb
39553 gdb [@option{-help}] [@option{-nh}] [@option{-nx}] [@option{-q}]
39554 [@option{-batch}] [@option{-cd=}@var{dir}] [@option{-f}]
39555 [@option{-b}@w{ }@var{bps}]
39556 [@option{-tty=}@var{dev}] [@option{-s} @var{symfile}]
39557 [@option{-e}@w{ }@var{prog}] [@option{-se}@w{ }@var{prog}]
39558 [@option{-c}@w{ }@var{core}] [@option{-p}@w{ }@var{procID}]
39559 [@option{-x}@w{ }@var{cmds}] [@option{-d}@w{ }@var{dir}]
39560 [@var{prog}|@var{prog} @var{procID}|@var{prog} @var{core}]
39563 @c man begin DESCRIPTION gdb
39564 The purpose of a debugger such as @value{GDBN} is to allow you to see what is
39565 going on ``inside'' another program while it executes -- or what another
39566 program was doing at the moment it crashed.
39568 @value{GDBN} can do four main kinds of things (plus other things in support of
39569 these) to help you catch bugs in the act:
39573 Start your program, specifying anything that might affect its behavior.
39576 Make your program stop on specified conditions.
39579 Examine what has happened, when your program has stopped.
39582 Change things in your program, so you can experiment with correcting the
39583 effects of one bug and go on to learn about another.
39586 You can use @value{GDBN} to debug programs written in C, C@t{++}, Fortran and
39589 @value{GDBN} is invoked with the shell command @code{gdb}. Once started, it reads
39590 commands from the terminal until you tell it to exit with the @value{GDBN}
39591 command @code{quit}. You can get online help from @value{GDBN} itself
39592 by using the command @code{help}.
39594 You can run @code{gdb} with no arguments or options; but the most
39595 usual way to start @value{GDBN} is with one argument or two, specifying an
39596 executable program as the argument:
39602 You can also start with both an executable program and a core file specified:
39608 You can, instead, specify a process ID as a second argument, if you want
39609 to debug a running process:
39617 would attach @value{GDBN} to process @code{1234} (unless you also have a file
39618 named @file{1234}; @value{GDBN} does check for a core file first).
39619 With option @option{-p} you can omit the @var{program} filename.
39621 Here are some of the most frequently needed @value{GDBN} commands:
39623 @c pod2man highlights the right hand side of the @item lines.
39625 @item break [@var{file}:]@var{functiop}
39626 Set a breakpoint at @var{function} (in @var{file}).
39628 @item run [@var{arglist}]
39629 Start your program (with @var{arglist}, if specified).
39632 Backtrace: display the program stack.
39634 @item print @var{expr}
39635 Display the value of an expression.
39638 Continue running your program (after stopping, e.g. at a breakpoint).
39641 Execute next program line (after stopping); step @emph{over} any
39642 function calls in the line.
39644 @item edit [@var{file}:]@var{function}
39645 look at the program line where it is presently stopped.
39647 @item list [@var{file}:]@var{function}
39648 type the text of the program in the vicinity of where it is presently stopped.
39651 Execute next program line (after stopping); step @emph{into} any
39652 function calls in the line.
39654 @item help [@var{name}]
39655 Show information about @value{GDBN} command @var{name}, or general information
39656 about using @value{GDBN}.
39659 Exit from @value{GDBN}.
39663 For full details on @value{GDBN},
39664 see @cite{Using GDB: A Guide to the GNU Source-Level Debugger},
39665 by Richard M. Stallman and Roland H. Pesch. The same text is available online
39666 as the @code{gdb} entry in the @code{info} program.
39670 @c man begin OPTIONS gdb
39671 Any arguments other than options specify an executable
39672 file and core file (or process ID); that is, the first argument
39673 encountered with no
39674 associated option flag is equivalent to a @option{-se} option, and the second,
39675 if any, is equivalent to a @option{-c} option if it's the name of a file.
39677 both long and short forms; both are shown here. The long forms are also
39678 recognized if you truncate them, so long as enough of the option is
39679 present to be unambiguous. (If you prefer, you can flag option
39680 arguments with @option{+} rather than @option{-}, though we illustrate the
39681 more usual convention.)
39683 All the options and command line arguments you give are processed
39684 in sequential order. The order makes a difference when the @option{-x}
39690 List all options, with brief explanations.
39692 @item -symbols=@var{file}
39693 @itemx -s @var{file}
39694 Read symbol table from file @var{file}.
39697 Enable writing into executable and core files.
39699 @item -exec=@var{file}
39700 @itemx -e @var{file}
39701 Use file @var{file} as the executable file to execute when
39702 appropriate, and for examining pure data in conjunction with a core
39705 @item -se=@var{file}
39706 Read symbol table from file @var{file} and use it as the executable
39709 @item -core=@var{file}
39710 @itemx -c @var{file}
39711 Use file @var{file} as a core dump to examine.
39713 @item -command=@var{file}
39714 @itemx -x @var{file}
39715 Execute @value{GDBN} commands from file @var{file}.
39717 @item -ex @var{command}
39718 Execute given @value{GDBN} @var{command}.
39720 @item -directory=@var{directory}
39721 @itemx -d @var{directory}
39722 Add @var{directory} to the path to search for source files.
39725 Do not execute commands from @file{~/.gdbinit}.
39729 Do not execute commands from any @file{.gdbinit} initialization files.
39733 ``Quiet''. Do not print the introductory and copyright messages. These
39734 messages are also suppressed in batch mode.
39737 Run in batch mode. Exit with status @code{0} after processing all the command
39738 files specified with @option{-x} (and @file{.gdbinit}, if not inhibited).
39739 Exit with nonzero status if an error occurs in executing the @value{GDBN}
39740 commands in the command files.
39742 Batch mode may be useful for running @value{GDBN} as a filter, for example to
39743 download and run a program on another computer; in order to make this
39744 more useful, the message
39747 Program exited normally.
39751 (which is ordinarily issued whenever a program running under @value{GDBN} control
39752 terminates) is not issued when running in batch mode.
39754 @item -cd=@var{directory}
39755 Run @value{GDBN} using @var{directory} as its working directory,
39756 instead of the current directory.
39760 Emacs sets this option when it runs @value{GDBN} as a subprocess. It tells
39761 @value{GDBN} to output the full file name and line number in a standard,
39762 recognizable fashion each time a stack frame is displayed (which
39763 includes each time the program stops). This recognizable format looks
39764 like two @samp{\032} characters, followed by the file name, line number
39765 and character position separated by colons, and a newline. The
39766 Emacs-to-@value{GDBN} interface program uses the two @samp{\032}
39767 characters as a signal to display the source code for the frame.
39770 Set the line speed (baud rate or bits per second) of any serial
39771 interface used by @value{GDBN} for remote debugging.
39773 @item -tty=@var{device}
39774 Run using @var{device} for your program's standard input and output.
39778 @c man begin SEEALSO gdb
39780 The full documentation for @value{GDBN} is maintained as a Texinfo manual.
39781 If the @code{info} and @code{gdb} programs and @value{GDBN}'s Texinfo
39782 documentation are properly installed at your site, the command
39789 should give you access to the complete manual.
39791 @cite{Using GDB: A Guide to the GNU Source-Level Debugger},
39792 Richard M. Stallman and Roland H. Pesch, July 1991.
39796 @node gdbserver man
39797 @heading gdbserver man
39799 @c man title gdbserver Remote Server for the GNU Debugger
39801 @c man begin SYNOPSIS gdbserver
39802 gdbserver @var{comm} @var{prog} [@var{args}@dots{}]
39804 gdbserver --attach @var{comm} @var{pid}
39806 gdbserver --multi @var{comm}
39810 @c man begin DESCRIPTION gdbserver
39811 @command{gdbserver} is a program that allows you to run @value{GDBN} on a different machine
39812 than the one which is running the program being debugged.
39815 @subheading Usage (server (target) side)
39818 Usage (server (target) side):
39821 First, you need to have a copy of the program you want to debug put onto
39822 the target system. The program can be stripped to save space if needed, as
39823 @command{gdbserver} doesn't care about symbols. All symbol handling is taken care of by
39824 the @value{GDBN} running on the host system.
39826 To use the server, you log on to the target system, and run the @command{gdbserver}
39827 program. You must tell it (a) how to communicate with @value{GDBN}, (b) the name of
39828 your program, and (c) its arguments. The general syntax is:
39831 target> gdbserver @var{comm} @var{program} [@var{args} ...]
39834 For example, using a serial port, you might say:
39838 @c @file would wrap it as F</dev/com1>.
39839 target> gdbserver /dev/com1 emacs foo.txt
39842 target> gdbserver @file{/dev/com1} emacs foo.txt
39846 This tells @command{gdbserver} to debug emacs with an argument of foo.txt, and
39847 to communicate with @value{GDBN} via @file{/dev/com1}. @command{gdbserver} now
39848 waits patiently for the host @value{GDBN} to communicate with it.
39850 To use a TCP connection, you could say:
39853 target> gdbserver host:2345 emacs foo.txt
39856 This says pretty much the same thing as the last example, except that we are
39857 going to communicate with the @code{host} @value{GDBN} via TCP. The @code{host:2345} argument means
39858 that we are expecting to see a TCP connection from @code{host} to local TCP port
39859 2345. (Currently, the @code{host} part is ignored.) You can choose any number you
39860 want for the port number as long as it does not conflict with any existing TCP
39861 ports on the target system. This same port number must be used in the host
39862 @value{GDBN}s @code{target remote} command, which will be described shortly. Note that if
39863 you chose a port number that conflicts with another service, @command{gdbserver} will
39864 print an error message and exit.
39866 @command{gdbserver} can also attach to running programs.
39867 This is accomplished via the @option{--attach} argument. The syntax is:
39870 target> gdbserver --attach @var{comm} @var{pid}
39873 @var{pid} is the process ID of a currently running process. It isn't
39874 necessary to point @command{gdbserver} at a binary for the running process.
39876 To start @code{gdbserver} without supplying an initial command to run
39877 or process ID to attach, use the @option{--multi} command line option.
39878 In such case you should connect using @kbd{target extended-remote} to start
39879 the program you want to debug.
39882 target> gdbserver --multi @var{comm}
39886 @subheading Usage (host side)
39892 You need an unstripped copy of the target program on your host system, since
39893 @value{GDBN} needs to examine it's symbol tables and such. Start up @value{GDBN} as you normally
39894 would, with the target program as the first argument. (You may need to use the
39895 @option{--baud} option if the serial line is running at anything except 9600 baud.)
39896 That is @code{gdb TARGET-PROG}, or @code{gdb --baud BAUD TARGET-PROG}. After that, the only
39897 new command you need to know about is @code{target remote}
39898 (or @code{target extended-remote}). Its argument is either
39899 a device name (usually a serial device, like @file{/dev/ttyb}), or a @code{HOST:PORT}
39900 descriptor. For example:
39904 @c @file would wrap it as F</dev/ttyb>.
39905 (gdb) target remote /dev/ttyb
39908 (gdb) target remote @file{/dev/ttyb}
39913 communicates with the server via serial line @file{/dev/ttyb}, and:
39916 (gdb) target remote the-target:2345
39920 communicates via a TCP connection to port 2345 on host `the-target', where
39921 you previously started up @command{gdbserver} with the same port number. Note that for
39922 TCP connections, you must start up @command{gdbserver} prior to using the `target remote'
39923 command, otherwise you may get an error that looks something like
39924 `Connection refused'.
39926 @command{gdbserver} can also debug multiple inferiors at once,
39929 the @value{GDBN} manual in node @code{Inferiors and Programs}
39930 -- shell command @code{info -f gdb -n 'Inferiors and Programs'}.
39933 @ref{Inferiors and Programs}.
39935 In such case use the @code{extended-remote} @value{GDBN} command variant:
39938 (gdb) target extended-remote the-target:2345
39941 The @command{gdbserver} option @option{--multi} may or may not be used in such
39945 @c man begin OPTIONS gdbserver
39946 There are three different modes for invoking @command{gdbserver}:
39951 Debug a specific program specified by its program name:
39954 gdbserver @var{comm} @var{prog} [@var{args}@dots{}]
39957 The @var{comm} parameter specifies how should the server communicate
39958 with @value{GDBN}; it is either a device name (to use a serial line),
39959 a TCP port number (@code{:1234}), or @code{-} or @code{stdio} to use
39960 stdin/stdout of @code{gdbserver}. Specify the name of the program to
39961 debug in @var{prog}. Any remaining arguments will be passed to the
39962 program verbatim. When the program exits, @value{GDBN} will close the
39963 connection, and @code{gdbserver} will exit.
39966 Debug a specific program by specifying the process ID of a running
39970 gdbserver --attach @var{comm} @var{pid}
39973 The @var{comm} parameter is as described above. Supply the process ID
39974 of a running program in @var{pid}; @value{GDBN} will do everything
39975 else. Like with the previous mode, when the process @var{pid} exits,
39976 @value{GDBN} will close the connection, and @code{gdbserver} will exit.
39979 Multi-process mode -- debug more than one program/process:
39982 gdbserver --multi @var{comm}
39985 In this mode, @value{GDBN} can instruct @command{gdbserver} which
39986 command(s) to run. Unlike the other 2 modes, @value{GDBN} will not
39987 close the connection when a process being debugged exits, so you can
39988 debug several processes in the same session.
39991 In each of the modes you may specify these options:
39996 List all options, with brief explanations.
39999 This option causes @command{gdbserver} to print its version number and exit.
40002 @command{gdbserver} will attach to a running program. The syntax is:
40005 target> gdbserver --attach @var{comm} @var{pid}
40008 @var{pid} is the process ID of a currently running process. It isn't
40009 necessary to point @command{gdbserver} at a binary for the running process.
40012 To start @code{gdbserver} without supplying an initial command to run
40013 or process ID to attach, use this command line option.
40014 Then you can connect using @kbd{target extended-remote} and start
40015 the program you want to debug. The syntax is:
40018 target> gdbserver --multi @var{comm}
40022 Instruct @code{gdbserver} to display extra status information about the debugging
40024 This option is intended for @code{gdbserver} development and for bug reports to
40027 @item --remote-debug
40028 Instruct @code{gdbserver} to display remote protocol debug output.
40029 This option is intended for @code{gdbserver} development and for bug reports to
40032 @item --debug-format=option1@r{[},option2,...@r{]}
40033 Instruct @code{gdbserver} to include extra information in each line
40034 of debugging output.
40035 @xref{Other Command-Line Arguments for gdbserver}.
40038 Specify a wrapper to launch programs
40039 for debugging. The option should be followed by the name of the
40040 wrapper, then any command-line arguments to pass to the wrapper, then
40041 @kbd{--} indicating the end of the wrapper arguments.
40044 By default, @command{gdbserver} keeps the listening TCP port open, so that
40045 additional connections are possible. However, if you start @code{gdbserver}
40046 with the @option{--once} option, it will stop listening for any further
40047 connection attempts after connecting to the first @value{GDBN} session.
40049 @c --disable-packet is not documented for users.
40051 @c --disable-randomization and --no-disable-randomization are superseded by
40052 @c QDisableRandomization.
40057 @c man begin SEEALSO gdbserver
40059 The full documentation for @value{GDBN} is maintained as a Texinfo manual.
40060 If the @code{info} and @code{gdb} programs and @value{GDBN}'s Texinfo
40061 documentation are properly installed at your site, the command
40067 should give you access to the complete manual.
40069 @cite{Using GDB: A Guide to the GNU Source-Level Debugger},
40070 Richard M. Stallman and Roland H. Pesch, July 1991.
40077 @c man title gcore Generate a core file of a running program
40080 @c man begin SYNOPSIS gcore
40081 gcore [-o @var{filename}] @var{pid}
40085 @c man begin DESCRIPTION gcore
40086 Generate a core dump of a running program with process ID @var{pid}.
40087 Produced file is equivalent to a kernel produced core file as if the process
40088 crashed (and if @kbd{ulimit -c} were used to set up an appropriate core dump
40089 limit). Unlike after a crash, after @command{gcore} the program remains
40090 running without any change.
40093 @c man begin OPTIONS gcore
40095 @item -o @var{filename}
40096 The optional argument
40097 @var{filename} specifies the file name where to put the core dump.
40098 If not specified, the file name defaults to @file{core.@var{pid}},
40099 where @var{pid} is the running program process ID.
40103 @c man begin SEEALSO gcore
40105 The full documentation for @value{GDBN} is maintained as a Texinfo manual.
40106 If the @code{info} and @code{gdb} programs and @value{GDBN}'s Texinfo
40107 documentation are properly installed at your site, the command
40114 should give you access to the complete manual.
40116 @cite{Using GDB: A Guide to the GNU Source-Level Debugger},
40117 Richard M. Stallman and Roland H. Pesch, July 1991.
40124 @c man title gdbinit GDB initialization scripts
40127 @c man begin SYNOPSIS gdbinit
40128 @ifset SYSTEM_GDBINIT
40129 @value{SYSTEM_GDBINIT}
40138 @c man begin DESCRIPTION gdbinit
40139 These files contain @value{GDBN} commands to automatically execute during
40140 @value{GDBN} startup. The lines of contents are canned sequences of commands,
40143 the @value{GDBN} manual in node @code{Sequences}
40144 -- shell command @code{info -f gdb -n Sequences}.
40150 Please read more in
40152 the @value{GDBN} manual in node @code{Startup}
40153 -- shell command @code{info -f gdb -n Startup}.
40160 @ifset SYSTEM_GDBINIT
40161 @item @value{SYSTEM_GDBINIT}
40163 @ifclear SYSTEM_GDBINIT
40164 @item (not enabled with @code{--with-system-gdbinit} during compilation)
40166 System-wide initialization file. It is executed unless user specified
40167 @value{GDBN} option @code{-nx} or @code{-n}.
40170 the @value{GDBN} manual in node @code{System-wide configuration}
40171 -- shell command @code{info -f gdb -n 'System-wide configuration'}.
40174 @ref{System-wide configuration}.
40178 User initialization file. It is executed unless user specified
40179 @value{GDBN} options @code{-nx}, @code{-n} or @code{-nh}.
40182 Initialization file for current directory. It may need to be enabled with
40183 @value{GDBN} security command @code{set auto-load local-gdbinit}.
40186 the @value{GDBN} manual in node @code{Init File in the Current Directory}
40187 -- shell command @code{info -f gdb -n 'Init File in the Current Directory'}.
40190 @ref{Init File in the Current Directory}.
40195 @c man begin SEEALSO gdbinit
40197 gdb(1), @code{info -f gdb -n Startup}
40199 The full documentation for @value{GDBN} is maintained as a Texinfo manual.
40200 If the @code{info} and @code{gdb} programs and @value{GDBN}'s Texinfo
40201 documentation are properly installed at your site, the command
40207 should give you access to the complete manual.
40209 @cite{Using GDB: A Guide to the GNU Source-Level Debugger},
40210 Richard M. Stallman and Roland H. Pesch, July 1991.
40216 @node GNU Free Documentation License
40217 @appendix GNU Free Documentation License
40220 @node Concept Index
40221 @unnumbered Concept Index
40225 @node Command and Variable Index
40226 @unnumbered Command, Variable, and Function Index
40231 % I think something like @@colophon should be in texinfo. In the
40233 \long\def\colophon{\hbox to0pt{}\vfill
40234 \centerline{The body of this manual is set in}
40235 \centerline{\fontname\tenrm,}
40236 \centerline{with headings in {\bf\fontname\tenbf}}
40237 \centerline{and examples in {\tt\fontname\tentt}.}
40238 \centerline{{\it\fontname\tenit\/},}
40239 \centerline{{\bf\fontname\tenbf}, and}
40240 \centerline{{\sl\fontname\tensl\/}}
40241 \centerline{are used for emphasis.}\vfill}
40243 % Blame: doc@@cygnus.com, 1991.