1 \input texinfo @c -*-texinfo-*-
2 @c Copyright (C) 1988-2018 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-2018 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-2018 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.
544 Initial support for the FreeBSD/mips target and native configuration
545 was developed by SRI International and the University of Cambridge
546 Computer Laboratory under DARPA/AFRL contract FA8750-10-C-0237
547 ("CTSRD"), as part of the DARPA CRASH research programme.
549 The original port to the OpenRISC 1000 is believed to be due to
550 Alessandro Forin and Per Bothner. More recent ports have been the work
551 of Jeremy Bennett, Franck Jullien, Stefan Wallentowitz and
555 @chapter A Sample @value{GDBN} Session
557 You can use this manual at your leisure to read all about @value{GDBN}.
558 However, a handful of commands are enough to get started using the
559 debugger. This chapter illustrates those commands.
562 In this sample session, we emphasize user input like this: @b{input},
563 to make it easier to pick out from the surrounding output.
566 @c FIXME: this example may not be appropriate for some configs, where
567 @c FIXME...primary interest is in remote use.
569 One of the preliminary versions of @sc{gnu} @code{m4} (a generic macro
570 processor) exhibits the following bug: sometimes, when we change its
571 quote strings from the default, the commands used to capture one macro
572 definition within another stop working. In the following short @code{m4}
573 session, we define a macro @code{foo} which expands to @code{0000}; we
574 then use the @code{m4} built-in @code{defn} to define @code{bar} as the
575 same thing. However, when we change the open quote string to
576 @code{<QUOTE>} and the close quote string to @code{<UNQUOTE>}, the same
577 procedure fails to define a new synonym @code{baz}:
586 @b{define(bar,defn(`foo'))}
590 @b{changequote(<QUOTE>,<UNQUOTE>)}
592 @b{define(baz,defn(<QUOTE>foo<UNQUOTE>))}
595 m4: End of input: 0: fatal error: EOF in string
599 Let us use @value{GDBN} to try to see what is going on.
602 $ @b{@value{GDBP} m4}
603 @c FIXME: this falsifies the exact text played out, to permit smallbook
604 @c FIXME... format to come out better.
605 @value{GDBN} is free software and you are welcome to distribute copies
606 of it under certain conditions; type "show copying" to see
608 There is absolutely no warranty for @value{GDBN}; type "show warranty"
611 @value{GDBN} @value{GDBVN}, Copyright 1999 Free Software Foundation, Inc...
616 @value{GDBN} reads only enough symbol data to know where to find the
617 rest when needed; as a result, the first prompt comes up very quickly.
618 We now tell @value{GDBN} to use a narrower display width than usual, so
619 that examples fit in this manual.
622 (@value{GDBP}) @b{set width 70}
626 We need to see how the @code{m4} built-in @code{changequote} works.
627 Having looked at the source, we know the relevant subroutine is
628 @code{m4_changequote}, so we set a breakpoint there with the @value{GDBN}
629 @code{break} command.
632 (@value{GDBP}) @b{break m4_changequote}
633 Breakpoint 1 at 0x62f4: file builtin.c, line 879.
637 Using the @code{run} command, we start @code{m4} running under @value{GDBN}
638 control; as long as control does not reach the @code{m4_changequote}
639 subroutine, the program runs as usual:
642 (@value{GDBP}) @b{run}
643 Starting program: /work/Editorial/gdb/gnu/m4/m4
651 To trigger the breakpoint, we call @code{changequote}. @value{GDBN}
652 suspends execution of @code{m4}, displaying information about the
653 context where it stops.
656 @b{changequote(<QUOTE>,<UNQUOTE>)}
658 Breakpoint 1, m4_changequote (argc=3, argv=0x33c70)
660 879 if (bad_argc(TOKEN_DATA_TEXT(argv[0]),argc,1,3))
664 Now we use the command @code{n} (@code{next}) to advance execution to
665 the next line of the current function.
669 882 set_quotes((argc >= 2) ? TOKEN_DATA_TEXT(argv[1])\
674 @code{set_quotes} looks like a promising subroutine. We can go into it
675 by using the command @code{s} (@code{step}) instead of @code{next}.
676 @code{step} goes to the next line to be executed in @emph{any}
677 subroutine, so it steps into @code{set_quotes}.
681 set_quotes (lq=0x34c78 "<QUOTE>", rq=0x34c88 "<UNQUOTE>")
683 530 if (lquote != def_lquote)
687 The display that shows the subroutine where @code{m4} is now
688 suspended (and its arguments) is called a stack frame display. It
689 shows a summary of the stack. We can use the @code{backtrace}
690 command (which can also be spelled @code{bt}), to see where we are
691 in the stack as a whole: the @code{backtrace} command displays a
692 stack frame for each active subroutine.
695 (@value{GDBP}) @b{bt}
696 #0 set_quotes (lq=0x34c78 "<QUOTE>", rq=0x34c88 "<UNQUOTE>")
698 #1 0x6344 in m4_changequote (argc=3, argv=0x33c70)
700 #2 0x8174 in expand_macro (sym=0x33320) at macro.c:242
701 #3 0x7a88 in expand_token (obs=0x0, t=209696, td=0xf7fffa30)
703 #4 0x79dc in expand_input () at macro.c:40
704 #5 0x2930 in main (argc=0, argv=0xf7fffb20) at m4.c:195
708 We step through a few more lines to see what happens. The first two
709 times, we can use @samp{s}; the next two times we use @code{n} to avoid
710 falling into the @code{xstrdup} subroutine.
714 0x3b5c 532 if (rquote != def_rquote)
716 0x3b80 535 lquote = (lq == nil || *lq == '\0') ? \
717 def_lquote : xstrdup(lq);
719 536 rquote = (rq == nil || *rq == '\0') ? def_rquote\
722 538 len_lquote = strlen(rquote);
726 The last line displayed looks a little odd; we can examine the variables
727 @code{lquote} and @code{rquote} to see if they are in fact the new left
728 and right quotes we specified. We use the command @code{p}
729 (@code{print}) to see their values.
732 (@value{GDBP}) @b{p lquote}
733 $1 = 0x35d40 "<QUOTE>"
734 (@value{GDBP}) @b{p rquote}
735 $2 = 0x35d50 "<UNQUOTE>"
739 @code{lquote} and @code{rquote} are indeed the new left and right quotes.
740 To look at some context, we can display ten lines of source
741 surrounding the current line with the @code{l} (@code{list}) command.
747 535 lquote = (lq == nil || *lq == '\0') ? def_lquote\
749 536 rquote = (rq == nil || *rq == '\0') ? def_rquote\
752 538 len_lquote = strlen(rquote);
753 539 len_rquote = strlen(lquote);
760 Let us step past the two lines that set @code{len_lquote} and
761 @code{len_rquote}, and then examine the values of those variables.
765 539 len_rquote = strlen(lquote);
768 (@value{GDBP}) @b{p len_lquote}
770 (@value{GDBP}) @b{p len_rquote}
775 That certainly looks wrong, assuming @code{len_lquote} and
776 @code{len_rquote} are meant to be the lengths of @code{lquote} and
777 @code{rquote} respectively. We can set them to better values using
778 the @code{p} command, since it can print the value of
779 any expression---and that expression can include subroutine calls and
783 (@value{GDBP}) @b{p len_lquote=strlen(lquote)}
785 (@value{GDBP}) @b{p len_rquote=strlen(rquote)}
790 Is that enough to fix the problem of using the new quotes with the
791 @code{m4} built-in @code{defn}? We can allow @code{m4} to continue
792 executing with the @code{c} (@code{continue}) command, and then try the
793 example that caused trouble initially:
799 @b{define(baz,defn(<QUOTE>foo<UNQUOTE>))}
806 Success! The new quotes now work just as well as the default ones. The
807 problem seems to have been just the two typos defining the wrong
808 lengths. We allow @code{m4} exit by giving it an EOF as input:
812 Program exited normally.
816 The message @samp{Program exited normally.} is from @value{GDBN}; it
817 indicates @code{m4} has finished executing. We can end our @value{GDBN}
818 session with the @value{GDBN} @code{quit} command.
821 (@value{GDBP}) @b{quit}
825 @chapter Getting In and Out of @value{GDBN}
827 This chapter discusses how to start @value{GDBN}, and how to get out of it.
831 type @samp{@value{GDBP}} to start @value{GDBN}.
833 type @kbd{quit} or @kbd{Ctrl-d} to exit.
837 * Invoking GDB:: How to start @value{GDBN}
838 * Quitting GDB:: How to quit @value{GDBN}
839 * Shell Commands:: How to use shell commands inside @value{GDBN}
840 * Logging Output:: How to log @value{GDBN}'s output to a file
844 @section Invoking @value{GDBN}
846 Invoke @value{GDBN} by running the program @code{@value{GDBP}}. Once started,
847 @value{GDBN} reads commands from the terminal until you tell it to exit.
849 You can also run @code{@value{GDBP}} with a variety of arguments and options,
850 to specify more of your debugging environment at the outset.
852 The command-line options described here are designed
853 to cover a variety of situations; in some environments, some of these
854 options may effectively be unavailable.
856 The most usual way to start @value{GDBN} is with one argument,
857 specifying an executable program:
860 @value{GDBP} @var{program}
864 You can also start with both an executable program and a core file
868 @value{GDBP} @var{program} @var{core}
871 You can, instead, specify a process ID as a second argument, if you want
872 to debug a running process:
875 @value{GDBP} @var{program} 1234
879 would attach @value{GDBN} to process @code{1234} (unless you also have a file
880 named @file{1234}; @value{GDBN} does check for a core file first).
882 Taking advantage of the second command-line argument requires a fairly
883 complete operating system; when you use @value{GDBN} as a remote
884 debugger attached to a bare board, there may not be any notion of
885 ``process'', and there is often no way to get a core dump. @value{GDBN}
886 will warn you if it is unable to attach or to read core dumps.
888 You can optionally have @code{@value{GDBP}} pass any arguments after the
889 executable file to the inferior using @code{--args}. This option stops
892 @value{GDBP} --args gcc -O2 -c foo.c
894 This will cause @code{@value{GDBP}} to debug @code{gcc}, and to set
895 @code{gcc}'s command-line arguments (@pxref{Arguments}) to @samp{-O2 -c foo.c}.
897 You can run @code{@value{GDBP}} without printing the front material, which describes
898 @value{GDBN}'s non-warranty, by specifying @code{--silent}
899 (or @code{-q}/@code{--quiet}):
902 @value{GDBP} --silent
906 You can further control how @value{GDBN} starts up by using command-line
907 options. @value{GDBN} itself can remind you of the options available.
917 to display all available options and briefly describe their use
918 (@samp{@value{GDBP} -h} is a shorter equivalent).
920 All options and command line arguments you give are processed
921 in sequential order. The order makes a difference when the
922 @samp{-x} option is used.
926 * File Options:: Choosing files
927 * Mode Options:: Choosing modes
928 * Startup:: What @value{GDBN} does during startup
932 @subsection Choosing Files
934 When @value{GDBN} starts, it reads any arguments other than options as
935 specifying an executable file and core file (or process ID). This is
936 the same as if the arguments were specified by the @samp{-se} and
937 @samp{-c} (or @samp{-p}) options respectively. (@value{GDBN} reads the
938 first argument that does not have an associated option flag as
939 equivalent to the @samp{-se} option followed by that argument; and the
940 second argument that does not have an associated option flag, if any, as
941 equivalent to the @samp{-c}/@samp{-p} option followed by that argument.)
942 If the second argument begins with a decimal digit, @value{GDBN} will
943 first attempt to attach to it as a process, and if that fails, attempt
944 to open it as a corefile. If you have a corefile whose name begins with
945 a digit, you can prevent @value{GDBN} from treating it as a pid by
946 prefixing it with @file{./}, e.g.@: @file{./12345}.
948 If @value{GDBN} has not been configured to included core file support,
949 such as for most embedded targets, then it will complain about a second
950 argument and ignore it.
952 Many options have both long and short forms; both are shown in the
953 following list. @value{GDBN} also recognizes the long forms if you truncate
954 them, so long as enough of the option is present to be unambiguous.
955 (If you prefer, you can flag option arguments with @samp{--} rather
956 than @samp{-}, though we illustrate the more usual convention.)
958 @c NOTE: the @cindex entries here use double dashes ON PURPOSE. This
959 @c way, both those who look for -foo and --foo in the index, will find
963 @item -symbols @var{file}
965 @cindex @code{--symbols}
967 Read symbol table from file @var{file}.
969 @item -exec @var{file}
971 @cindex @code{--exec}
973 Use file @var{file} as the executable file to execute when appropriate,
974 and for examining pure data in conjunction with a core dump.
978 Read symbol table from file @var{file} and use it as the executable
981 @item -core @var{file}
983 @cindex @code{--core}
985 Use file @var{file} as a core dump to examine.
987 @item -pid @var{number}
988 @itemx -p @var{number}
991 Connect to process ID @var{number}, as with the @code{attach} command.
993 @item -command @var{file}
995 @cindex @code{--command}
997 Execute commands from file @var{file}. The contents of this file is
998 evaluated exactly as the @code{source} command would.
999 @xref{Command Files,, Command files}.
1001 @item -eval-command @var{command}
1002 @itemx -ex @var{command}
1003 @cindex @code{--eval-command}
1005 Execute a single @value{GDBN} command.
1007 This option may be used multiple times to call multiple commands. It may
1008 also be interleaved with @samp{-command} as required.
1011 @value{GDBP} -ex 'target sim' -ex 'load' \
1012 -x setbreakpoints -ex 'run' a.out
1015 @item -init-command @var{file}
1016 @itemx -ix @var{file}
1017 @cindex @code{--init-command}
1019 Execute commands from file @var{file} before loading the inferior (but
1020 after loading gdbinit files).
1023 @item -init-eval-command @var{command}
1024 @itemx -iex @var{command}
1025 @cindex @code{--init-eval-command}
1027 Execute a single @value{GDBN} command before loading the inferior (but
1028 after loading gdbinit files).
1031 @item -directory @var{directory}
1032 @itemx -d @var{directory}
1033 @cindex @code{--directory}
1035 Add @var{directory} to the path to search for source and script files.
1039 @cindex @code{--readnow}
1041 Read each symbol file's entire symbol table immediately, rather than
1042 the default, which is to read it incrementally as it is needed.
1043 This makes startup slower, but makes future operations faster.
1046 @anchor{--readnever}
1047 @cindex @code{--readnever}, command-line option
1048 Do not read each symbol file's symbolic debug information. This makes
1049 startup faster but at the expense of not being able to perform
1050 symbolic debugging. DWARF unwind information is also not read,
1051 meaning backtraces may become incomplete or inaccurate. One use of
1052 this is when a user simply wants to do the following sequence: attach,
1053 dump core, detach. Loading the debugging information in this case is
1054 an unnecessary cause of delay.
1058 @subsection Choosing Modes
1060 You can run @value{GDBN} in various alternative modes---for example, in
1061 batch mode or quiet mode.
1069 Do not execute commands found in any initialization file.
1070 There are three init files, loaded in the following order:
1073 @item @file{system.gdbinit}
1074 This is the system-wide init file.
1075 Its location is specified with the @code{--with-system-gdbinit}
1076 configure option (@pxref{System-wide configuration}).
1077 It is loaded first when @value{GDBN} starts, before command line options
1078 have been processed.
1079 @item @file{~/.gdbinit}
1080 This is the init file in your home directory.
1081 It is loaded next, after @file{system.gdbinit}, and before
1082 command options have been processed.
1083 @item @file{./.gdbinit}
1084 This is the init file in the current directory.
1085 It is loaded last, after command line options other than @code{-x} and
1086 @code{-ex} have been processed. Command line options @code{-x} and
1087 @code{-ex} are processed last, after @file{./.gdbinit} has been loaded.
1090 For further documentation on startup processing, @xref{Startup}.
1091 For documentation on how to write command files,
1092 @xref{Command Files,,Command Files}.
1097 Do not execute commands found in @file{~/.gdbinit}, the init file
1098 in your home directory.
1104 @cindex @code{--quiet}
1105 @cindex @code{--silent}
1107 ``Quiet''. Do not print the introductory and copyright messages. These
1108 messages are also suppressed in batch mode.
1111 @cindex @code{--batch}
1112 Run in batch mode. Exit with status @code{0} after processing all the
1113 command files specified with @samp{-x} (and all commands from
1114 initialization files, if not inhibited with @samp{-n}). Exit with
1115 nonzero status if an error occurs in executing the @value{GDBN} commands
1116 in the command files. Batch mode also disables pagination, sets unlimited
1117 terminal width and height @pxref{Screen Size}, and acts as if @kbd{set confirm
1118 off} were in effect (@pxref{Messages/Warnings}).
1120 Batch mode may be useful for running @value{GDBN} as a filter, for
1121 example to download and run a program on another computer; in order to
1122 make this more useful, the message
1125 Program exited normally.
1129 (which is ordinarily issued whenever a program running under
1130 @value{GDBN} control terminates) is not issued when running in batch
1134 @cindex @code{--batch-silent}
1135 Run in batch mode exactly like @samp{-batch}, but totally silently. All
1136 @value{GDBN} output to @code{stdout} is prevented (@code{stderr} is
1137 unaffected). This is much quieter than @samp{-silent} and would be useless
1138 for an interactive session.
1140 This is particularly useful when using targets that give @samp{Loading section}
1141 messages, for example.
1143 Note that targets that give their output via @value{GDBN}, as opposed to
1144 writing directly to @code{stdout}, will also be made silent.
1146 @item -return-child-result
1147 @cindex @code{--return-child-result}
1148 The return code from @value{GDBN} will be the return code from the child
1149 process (the process being debugged), with the following exceptions:
1153 @value{GDBN} exits abnormally. E.g., due to an incorrect argument or an
1154 internal error. In this case the exit code is the same as it would have been
1155 without @samp{-return-child-result}.
1157 The user quits with an explicit value. E.g., @samp{quit 1}.
1159 The child process never runs, or is not allowed to terminate, in which case
1160 the exit code will be -1.
1163 This option is useful in conjunction with @samp{-batch} or @samp{-batch-silent},
1164 when @value{GDBN} is being used as a remote program loader or simulator
1169 @cindex @code{--nowindows}
1171 ``No windows''. If @value{GDBN} comes with a graphical user interface
1172 (GUI) built in, then this option tells @value{GDBN} to only use the command-line
1173 interface. If no GUI is available, this option has no effect.
1177 @cindex @code{--windows}
1179 If @value{GDBN} includes a GUI, then this option requires it to be
1182 @item -cd @var{directory}
1184 Run @value{GDBN} using @var{directory} as its working directory,
1185 instead of the current directory.
1187 @item -data-directory @var{directory}
1188 @itemx -D @var{directory}
1189 @cindex @code{--data-directory}
1191 Run @value{GDBN} using @var{directory} as its data directory.
1192 The data directory is where @value{GDBN} searches for its
1193 auxiliary files. @xref{Data Files}.
1197 @cindex @code{--fullname}
1199 @sc{gnu} Emacs sets this option when it runs @value{GDBN} as a
1200 subprocess. It tells @value{GDBN} to output the full file name and line
1201 number in a standard, recognizable fashion each time a stack frame is
1202 displayed (which includes each time your program stops). This
1203 recognizable format looks like two @samp{\032} characters, followed by
1204 the file name, line number and character position separated by colons,
1205 and a newline. The Emacs-to-@value{GDBN} interface program uses the two
1206 @samp{\032} characters as a signal to display the source code for the
1209 @item -annotate @var{level}
1210 @cindex @code{--annotate}
1211 This option sets the @dfn{annotation level} inside @value{GDBN}. Its
1212 effect is identical to using @samp{set annotate @var{level}}
1213 (@pxref{Annotations}). The annotation @var{level} controls how much
1214 information @value{GDBN} prints together with its prompt, values of
1215 expressions, source lines, and other types of output. Level 0 is the
1216 normal, level 1 is for use when @value{GDBN} is run as a subprocess of
1217 @sc{gnu} Emacs, level 3 is the maximum annotation suitable for programs
1218 that control @value{GDBN}, and level 2 has been deprecated.
1220 The annotation mechanism has largely been superseded by @sc{gdb/mi}
1224 @cindex @code{--args}
1225 Change interpretation of command line so that arguments following the
1226 executable file are passed as command line arguments to the inferior.
1227 This option stops option processing.
1229 @item -baud @var{bps}
1231 @cindex @code{--baud}
1233 Set the line speed (baud rate or bits per second) of any serial
1234 interface used by @value{GDBN} for remote debugging.
1236 @item -l @var{timeout}
1238 Set the timeout (in seconds) of any communication used by @value{GDBN}
1239 for remote debugging.
1241 @item -tty @var{device}
1242 @itemx -t @var{device}
1243 @cindex @code{--tty}
1245 Run using @var{device} for your program's standard input and output.
1246 @c FIXME: kingdon thinks there is more to -tty. Investigate.
1248 @c resolve the situation of these eventually
1250 @cindex @code{--tui}
1251 Activate the @dfn{Text User Interface} when starting. The Text User
1252 Interface manages several text windows on the terminal, showing
1253 source, assembly, registers and @value{GDBN} command outputs
1254 (@pxref{TUI, ,@value{GDBN} Text User Interface}). Do not use this
1255 option if you run @value{GDBN} from Emacs (@pxref{Emacs, ,
1256 Using @value{GDBN} under @sc{gnu} Emacs}).
1258 @item -interpreter @var{interp}
1259 @cindex @code{--interpreter}
1260 Use the interpreter @var{interp} for interface with the controlling
1261 program or device. This option is meant to be set by programs which
1262 communicate with @value{GDBN} using it as a back end.
1263 @xref{Interpreters, , Command Interpreters}.
1265 @samp{--interpreter=mi} (or @samp{--interpreter=mi2}) causes
1266 @value{GDBN} to use the @dfn{@sc{gdb/mi} interface} (@pxref{GDB/MI, ,
1267 The @sc{gdb/mi} Interface}) included since @value{GDBN} version 6.0. The
1268 previous @sc{gdb/mi} interface, included in @value{GDBN} version 5.3 and
1269 selected with @samp{--interpreter=mi1}, is deprecated. Earlier
1270 @sc{gdb/mi} interfaces are no longer supported.
1273 @cindex @code{--write}
1274 Open the executable and core files for both reading and writing. This
1275 is equivalent to the @samp{set write on} command inside @value{GDBN}
1279 @cindex @code{--statistics}
1280 This option causes @value{GDBN} to print statistics about time and
1281 memory usage after it completes each command and returns to the prompt.
1284 @cindex @code{--version}
1285 This option causes @value{GDBN} to print its version number and
1286 no-warranty blurb, and exit.
1288 @item -configuration
1289 @cindex @code{--configuration}
1290 This option causes @value{GDBN} to print details about its build-time
1291 configuration parameters, and then exit. These details can be
1292 important when reporting @value{GDBN} bugs (@pxref{GDB Bugs}).
1297 @subsection What @value{GDBN} Does During Startup
1298 @cindex @value{GDBN} startup
1300 Here's the description of what @value{GDBN} does during session startup:
1304 Sets up the command interpreter as specified by the command line
1305 (@pxref{Mode Options, interpreter}).
1309 Reads the system-wide @dfn{init file} (if @option{--with-system-gdbinit} was
1310 used when building @value{GDBN}; @pxref{System-wide configuration,
1311 ,System-wide configuration and settings}) and executes all the commands in
1314 @anchor{Home Directory Init File}
1316 Reads the init file (if any) in your home directory@footnote{On
1317 DOS/Windows systems, the home directory is the one pointed to by the
1318 @code{HOME} environment variable.} and executes all the commands in
1321 @anchor{Option -init-eval-command}
1323 Executes commands and command files specified by the @samp{-iex} and
1324 @samp{-ix} options in their specified order. Usually you should use the
1325 @samp{-ex} and @samp{-x} options instead, but this way you can apply
1326 settings before @value{GDBN} init files get executed and before inferior
1330 Processes command line options and operands.
1332 @anchor{Init File in the Current Directory during Startup}
1334 Reads and executes the commands from init file (if any) in the current
1335 working directory as long as @samp{set auto-load local-gdbinit} is set to
1336 @samp{on} (@pxref{Init File in the Current Directory}).
1337 This is only done if the current directory is
1338 different from your home directory. Thus, you can have more than one
1339 init file, one generic in your home directory, and another, specific
1340 to the program you are debugging, in the directory where you invoke
1344 If the command line specified a program to debug, or a process to
1345 attach to, or a core file, @value{GDBN} loads any auto-loaded
1346 scripts provided for the program or for its loaded shared libraries.
1347 @xref{Auto-loading}.
1349 If you wish to disable the auto-loading during startup,
1350 you must do something like the following:
1353 $ gdb -iex "set auto-load python-scripts off" myprogram
1356 Option @samp{-ex} does not work because the auto-loading is then turned
1360 Executes commands and command files specified by the @samp{-ex} and
1361 @samp{-x} options in their specified order. @xref{Command Files}, for
1362 more details about @value{GDBN} command files.
1365 Reads the command history recorded in the @dfn{history file}.
1366 @xref{Command History}, for more details about the command history and the
1367 files where @value{GDBN} records it.
1370 Init files use the same syntax as @dfn{command files} (@pxref{Command
1371 Files}) and are processed by @value{GDBN} in the same way. The init
1372 file in your home directory can set options (such as @samp{set
1373 complaints}) that affect subsequent processing of command line options
1374 and operands. Init files are not executed if you use the @samp{-nx}
1375 option (@pxref{Mode Options, ,Choosing Modes}).
1377 To display the list of init files loaded by gdb at startup, you
1378 can use @kbd{gdb --help}.
1380 @cindex init file name
1381 @cindex @file{.gdbinit}
1382 @cindex @file{gdb.ini}
1383 The @value{GDBN} init files are normally called @file{.gdbinit}.
1384 The DJGPP port of @value{GDBN} uses the name @file{gdb.ini}, due to
1385 the limitations of file names imposed by DOS filesystems. The Windows
1386 port of @value{GDBN} uses the standard name, but if it finds a
1387 @file{gdb.ini} file in your home directory, it warns you about that
1388 and suggests to rename the file to the standard name.
1392 @section Quitting @value{GDBN}
1393 @cindex exiting @value{GDBN}
1394 @cindex leaving @value{GDBN}
1397 @kindex quit @r{[}@var{expression}@r{]}
1398 @kindex q @r{(@code{quit})}
1399 @item quit @r{[}@var{expression}@r{]}
1401 To exit @value{GDBN}, use the @code{quit} command (abbreviated
1402 @code{q}), or type an end-of-file character (usually @kbd{Ctrl-d}). If you
1403 do not supply @var{expression}, @value{GDBN} will terminate normally;
1404 otherwise it will terminate using the result of @var{expression} as the
1409 An interrupt (often @kbd{Ctrl-c}) does not exit from @value{GDBN}, but rather
1410 terminates the action of any @value{GDBN} command that is in progress and
1411 returns to @value{GDBN} command level. It is safe to type the interrupt
1412 character at any time because @value{GDBN} does not allow it to take effect
1413 until a time when it is safe.
1415 If you have been using @value{GDBN} to control an attached process or
1416 device, you can release it with the @code{detach} command
1417 (@pxref{Attach, ,Debugging an Already-running Process}).
1419 @node Shell Commands
1420 @section Shell Commands
1422 If you need to execute occasional shell commands during your
1423 debugging session, there is no need to leave or suspend @value{GDBN}; you can
1424 just use the @code{shell} command.
1429 @cindex shell escape
1430 @item shell @var{command-string}
1431 @itemx !@var{command-string}
1432 Invoke a standard shell to execute @var{command-string}.
1433 Note that no space is needed between @code{!} and @var{command-string}.
1434 If it exists, the environment variable @code{SHELL} determines which
1435 shell to run. Otherwise @value{GDBN} uses the default shell
1436 (@file{/bin/sh} on Unix systems, @file{COMMAND.COM} on MS-DOS, etc.).
1439 The utility @code{make} is often needed in development environments.
1440 You do not have to use the @code{shell} command for this purpose in
1445 @cindex calling make
1446 @item make @var{make-args}
1447 Execute the @code{make} program with the specified
1448 arguments. This is equivalent to @samp{shell make @var{make-args}}.
1451 @node Logging Output
1452 @section Logging Output
1453 @cindex logging @value{GDBN} output
1454 @cindex save @value{GDBN} output to a file
1456 You may want to save the output of @value{GDBN} commands to a file.
1457 There are several commands to control @value{GDBN}'s logging.
1461 @item set logging on
1463 @item set logging off
1465 @cindex logging file name
1466 @item set logging file @var{file}
1467 Change the name of the current logfile. The default logfile is @file{gdb.txt}.
1468 @item set logging overwrite [on|off]
1469 By default, @value{GDBN} will append to the logfile. Set @code{overwrite} if
1470 you want @code{set logging on} to overwrite the logfile instead.
1471 @item set logging redirect [on|off]
1472 By default, @value{GDBN} output will go to both the terminal and the logfile.
1473 Set @code{redirect} if you want output to go only to the log file.
1474 @kindex show logging
1476 Show the current values of the logging settings.
1480 @chapter @value{GDBN} Commands
1482 You can abbreviate a @value{GDBN} command to the first few letters of the command
1483 name, if that abbreviation is unambiguous; and you can repeat certain
1484 @value{GDBN} commands by typing just @key{RET}. You can also use the @key{TAB}
1485 key to get @value{GDBN} to fill out the rest of a word in a command (or to
1486 show you the alternatives available, if there is more than one possibility).
1489 * Command Syntax:: How to give commands to @value{GDBN}
1490 * Completion:: Command completion
1491 * Help:: How to ask @value{GDBN} for help
1494 @node Command Syntax
1495 @section Command Syntax
1497 A @value{GDBN} command is a single line of input. There is no limit on
1498 how long it can be. It starts with a command name, which is followed by
1499 arguments whose meaning depends on the command name. For example, the
1500 command @code{step} accepts an argument which is the number of times to
1501 step, as in @samp{step 5}. You can also use the @code{step} command
1502 with no arguments. Some commands do not allow any arguments.
1504 @cindex abbreviation
1505 @value{GDBN} command names may always be truncated if that abbreviation is
1506 unambiguous. Other possible command abbreviations are listed in the
1507 documentation for individual commands. In some cases, even ambiguous
1508 abbreviations are allowed; for example, @code{s} is specially defined as
1509 equivalent to @code{step} even though there are other commands whose
1510 names start with @code{s}. You can test abbreviations by using them as
1511 arguments to the @code{help} command.
1513 @cindex repeating commands
1514 @kindex RET @r{(repeat last command)}
1515 A blank line as input to @value{GDBN} (typing just @key{RET}) means to
1516 repeat the previous command. Certain commands (for example, @code{run})
1517 will not repeat this way; these are commands whose unintentional
1518 repetition might cause trouble and which you are unlikely to want to
1519 repeat. User-defined commands can disable this feature; see
1520 @ref{Define, dont-repeat}.
1522 The @code{list} and @code{x} commands, when you repeat them with
1523 @key{RET}, construct new arguments rather than repeating
1524 exactly as typed. This permits easy scanning of source or memory.
1526 @value{GDBN} can also use @key{RET} in another way: to partition lengthy
1527 output, in a way similar to the common utility @code{more}
1528 (@pxref{Screen Size,,Screen Size}). Since it is easy to press one
1529 @key{RET} too many in this situation, @value{GDBN} disables command
1530 repetition after any command that generates this sort of display.
1532 @kindex # @r{(a comment)}
1534 Any text from a @kbd{#} to the end of the line is a comment; it does
1535 nothing. This is useful mainly in command files (@pxref{Command
1536 Files,,Command Files}).
1538 @cindex repeating command sequences
1539 @kindex Ctrl-o @r{(operate-and-get-next)}
1540 The @kbd{Ctrl-o} binding is useful for repeating a complex sequence of
1541 commands. This command accepts the current line, like @key{RET}, and
1542 then fetches the next line relative to the current line from the history
1546 @section Command Completion
1549 @cindex word completion
1550 @value{GDBN} can fill in the rest of a word in a command for you, if there is
1551 only one possibility; it can also show you what the valid possibilities
1552 are for the next word in a command, at any time. This works for @value{GDBN}
1553 commands, @value{GDBN} subcommands, and the names of symbols in your program.
1555 Press the @key{TAB} key whenever you want @value{GDBN} to fill out the rest
1556 of a word. If there is only one possibility, @value{GDBN} fills in the
1557 word, and waits for you to finish the command (or press @key{RET} to
1558 enter it). For example, if you type
1560 @c FIXME "@key" does not distinguish its argument sufficiently to permit
1561 @c complete accuracy in these examples; space introduced for clarity.
1562 @c If texinfo enhancements make it unnecessary, it would be nice to
1563 @c replace " @key" by "@key" in the following...
1565 (@value{GDBP}) info bre @key{TAB}
1569 @value{GDBN} fills in the rest of the word @samp{breakpoints}, since that is
1570 the only @code{info} subcommand beginning with @samp{bre}:
1573 (@value{GDBP}) info breakpoints
1577 You can either press @key{RET} at this point, to run the @code{info
1578 breakpoints} command, or backspace and enter something else, if
1579 @samp{breakpoints} does not look like the command you expected. (If you
1580 were sure you wanted @code{info breakpoints} in the first place, you
1581 might as well just type @key{RET} immediately after @samp{info bre},
1582 to exploit command abbreviations rather than command completion).
1584 If there is more than one possibility for the next word when you press
1585 @key{TAB}, @value{GDBN} sounds a bell. You can either supply more
1586 characters and try again, or just press @key{TAB} a second time;
1587 @value{GDBN} displays all the possible completions for that word. For
1588 example, you might want to set a breakpoint on a subroutine whose name
1589 begins with @samp{make_}, but when you type @kbd{b make_@key{TAB}} @value{GDBN}
1590 just sounds the bell. Typing @key{TAB} again displays all the
1591 function names in your program that begin with those characters, for
1595 (@value{GDBP}) b make_ @key{TAB}
1596 @exdent @value{GDBN} sounds bell; press @key{TAB} again, to see:
1597 make_a_section_from_file make_environ
1598 make_abs_section make_function_type
1599 make_blockvector make_pointer_type
1600 make_cleanup make_reference_type
1601 make_command make_symbol_completion_list
1602 (@value{GDBP}) b make_
1606 After displaying the available possibilities, @value{GDBN} copies your
1607 partial input (@samp{b make_} in the example) so you can finish the
1610 If you just want to see the list of alternatives in the first place, you
1611 can press @kbd{M-?} rather than pressing @key{TAB} twice. @kbd{M-?}
1612 means @kbd{@key{META} ?}. You can type this either by holding down a
1613 key designated as the @key{META} shift on your keyboard (if there is
1614 one) while typing @kbd{?}, or as @key{ESC} followed by @kbd{?}.
1616 If the number of possible completions is large, @value{GDBN} will
1617 print as much of the list as it has collected, as well as a message
1618 indicating that the list may be truncated.
1621 (@value{GDBP}) b m@key{TAB}@key{TAB}
1623 <... the rest of the possible completions ...>
1624 *** List may be truncated, max-completions reached. ***
1629 This behavior can be controlled with the following commands:
1632 @kindex set max-completions
1633 @item set max-completions @var{limit}
1634 @itemx set max-completions unlimited
1635 Set the maximum number of completion candidates. @value{GDBN} will
1636 stop looking for more completions once it collects this many candidates.
1637 This is useful when completing on things like function names as collecting
1638 all the possible candidates can be time consuming.
1639 The default value is 200. A value of zero disables tab-completion.
1640 Note that setting either no limit or a very large limit can make
1642 @kindex show max-completions
1643 @item show max-completions
1644 Show the maximum number of candidates that @value{GDBN} will collect and show
1648 @cindex quotes in commands
1649 @cindex completion of quoted strings
1650 Sometimes the string you need, while logically a ``word'', may contain
1651 parentheses or other characters that @value{GDBN} normally excludes from
1652 its notion of a word. To permit word completion to work in this
1653 situation, you may enclose words in @code{'} (single quote marks) in
1654 @value{GDBN} commands.
1656 A likely situation where you might need this is in typing an
1657 expression that involves a C@t{++} symbol name with template
1658 parameters. This is because when completing expressions, GDB treats
1659 the @samp{<} character as word delimiter, assuming that it's the
1660 less-than comparison operator (@pxref{C Operators, , C and C@t{++}
1663 For example, when you want to call a C@t{++} template function
1664 interactively using the @code{print} or @code{call} commands, you may
1665 need to distinguish whether you mean the version of @code{name} that
1666 was specialized for @code{int}, @code{name<int>()}, or the version
1667 that was specialized for @code{float}, @code{name<float>()}. To use
1668 the word-completion facilities in this situation, type a single quote
1669 @code{'} at the beginning of the function name. This alerts
1670 @value{GDBN} that it may need to consider more information than usual
1671 when you press @key{TAB} or @kbd{M-?} to request word completion:
1674 (@value{GDBP}) p 'func< @kbd{M-?}
1675 func<int>() func<float>()
1676 (@value{GDBP}) p 'func<
1679 When setting breakpoints however (@pxref{Specify Location}), you don't
1680 usually need to type a quote before the function name, because
1681 @value{GDBN} understands that you want to set a breakpoint on a
1685 (@value{GDBP}) b func< @kbd{M-?}
1686 func<int>() func<float>()
1687 (@value{GDBP}) b func<
1690 This is true even in the case of typing the name of C@t{++} overloaded
1691 functions (multiple definitions of the same function, distinguished by
1692 argument type). For example, when you want to set a breakpoint you
1693 don't need to distinguish whether you mean the version of @code{name}
1694 that takes an @code{int} parameter, @code{name(int)}, or the version
1695 that takes a @code{float} parameter, @code{name(float)}.
1698 (@value{GDBP}) b bubble( @kbd{M-?}
1699 bubble(int) bubble(double)
1700 (@value{GDBP}) b bubble(dou @kbd{M-?}
1704 See @ref{quoting names} for a description of other scenarios that
1707 For more information about overloaded functions, see @ref{C Plus Plus
1708 Expressions, ,C@t{++} Expressions}. You can use the command @code{set
1709 overload-resolution off} to disable overload resolution;
1710 see @ref{Debugging C Plus Plus, ,@value{GDBN} Features for C@t{++}}.
1712 @cindex completion of structure field names
1713 @cindex structure field name completion
1714 @cindex completion of union field names
1715 @cindex union field name completion
1716 When completing in an expression which looks up a field in a
1717 structure, @value{GDBN} also tries@footnote{The completer can be
1718 confused by certain kinds of invalid expressions. Also, it only
1719 examines the static type of the expression, not the dynamic type.} to
1720 limit completions to the field names available in the type of the
1724 (@value{GDBP}) p gdb_stdout.@kbd{M-?}
1725 magic to_fputs to_rewind
1726 to_data to_isatty to_write
1727 to_delete to_put to_write_async_safe
1732 This is because the @code{gdb_stdout} is a variable of the type
1733 @code{struct ui_file} that is defined in @value{GDBN} sources as
1740 ui_file_flush_ftype *to_flush;
1741 ui_file_write_ftype *to_write;
1742 ui_file_write_async_safe_ftype *to_write_async_safe;
1743 ui_file_fputs_ftype *to_fputs;
1744 ui_file_read_ftype *to_read;
1745 ui_file_delete_ftype *to_delete;
1746 ui_file_isatty_ftype *to_isatty;
1747 ui_file_rewind_ftype *to_rewind;
1748 ui_file_put_ftype *to_put;
1755 @section Getting Help
1756 @cindex online documentation
1759 You can always ask @value{GDBN} itself for information on its commands,
1760 using the command @code{help}.
1763 @kindex h @r{(@code{help})}
1766 You can use @code{help} (abbreviated @code{h}) with no arguments to
1767 display a short list of named classes of commands:
1771 List of classes of commands:
1773 aliases -- Aliases of other commands
1774 breakpoints -- Making program stop at certain points
1775 data -- Examining data
1776 files -- Specifying and examining files
1777 internals -- Maintenance commands
1778 obscure -- Obscure features
1779 running -- Running the program
1780 stack -- Examining the stack
1781 status -- Status inquiries
1782 support -- Support facilities
1783 tracepoints -- Tracing of program execution without
1784 stopping the program
1785 user-defined -- User-defined commands
1787 Type "help" followed by a class name for a list of
1788 commands in that class.
1789 Type "help" followed by command name for full
1791 Command name abbreviations are allowed if unambiguous.
1794 @c the above line break eliminates huge line overfull...
1796 @item help @var{class}
1797 Using one of the general help classes as an argument, you can get a
1798 list of the individual commands in that class. For example, here is the
1799 help display for the class @code{status}:
1802 (@value{GDBP}) help status
1807 @c Line break in "show" line falsifies real output, but needed
1808 @c to fit in smallbook page size.
1809 info -- Generic command for showing things
1810 about the program being debugged
1811 show -- Generic command for showing things
1814 Type "help" followed by command name for full
1816 Command name abbreviations are allowed if unambiguous.
1820 @item help @var{command}
1821 With a command name as @code{help} argument, @value{GDBN} displays a
1822 short paragraph on how to use that command.
1825 @item apropos @var{args}
1826 The @code{apropos} command searches through all of the @value{GDBN}
1827 commands, and their documentation, for the regular expression specified in
1828 @var{args}. It prints out all matches found. For example:
1839 alias -- Define a new command that is an alias of an existing command
1840 aliases -- Aliases of other commands
1841 d -- Delete some breakpoints or auto-display expressions
1842 del -- Delete some breakpoints or auto-display expressions
1843 delete -- Delete some breakpoints or auto-display expressions
1848 @item complete @var{args}
1849 The @code{complete @var{args}} command lists all the possible completions
1850 for the beginning of a command. Use @var{args} to specify the beginning of the
1851 command you want completed. For example:
1857 @noindent results in:
1868 @noindent This is intended for use by @sc{gnu} Emacs.
1871 In addition to @code{help}, you can use the @value{GDBN} commands @code{info}
1872 and @code{show} to inquire about the state of your program, or the state
1873 of @value{GDBN} itself. Each command supports many topics of inquiry; this
1874 manual introduces each of them in the appropriate context. The listings
1875 under @code{info} and under @code{show} in the Command, Variable, and
1876 Function Index point to all the sub-commands. @xref{Command and Variable
1882 @kindex i @r{(@code{info})}
1884 This command (abbreviated @code{i}) is for describing the state of your
1885 program. For example, you can show the arguments passed to a function
1886 with @code{info args}, list the registers currently in use with @code{info
1887 registers}, or list the breakpoints you have set with @code{info breakpoints}.
1888 You can get a complete list of the @code{info} sub-commands with
1889 @w{@code{help info}}.
1893 You can assign the result of an expression to an environment variable with
1894 @code{set}. For example, you can set the @value{GDBN} prompt to a $-sign with
1895 @code{set prompt $}.
1899 In contrast to @code{info}, @code{show} is for describing the state of
1900 @value{GDBN} itself.
1901 You can change most of the things you can @code{show}, by using the
1902 related command @code{set}; for example, you can control what number
1903 system is used for displays with @code{set radix}, or simply inquire
1904 which is currently in use with @code{show radix}.
1907 To display all the settable parameters and their current
1908 values, you can use @code{show} with no arguments; you may also use
1909 @code{info set}. Both commands produce the same display.
1910 @c FIXME: "info set" violates the rule that "info" is for state of
1911 @c FIXME...program. Ck w/ GNU: "info set" to be called something else,
1912 @c FIXME...or change desc of rule---eg "state of prog and debugging session"?
1916 Here are several miscellaneous @code{show} subcommands, all of which are
1917 exceptional in lacking corresponding @code{set} commands:
1920 @kindex show version
1921 @cindex @value{GDBN} version number
1923 Show what version of @value{GDBN} is running. You should include this
1924 information in @value{GDBN} bug-reports. If multiple versions of
1925 @value{GDBN} are in use at your site, you may need to determine which
1926 version of @value{GDBN} you are running; as @value{GDBN} evolves, new
1927 commands are introduced, and old ones may wither away. Also, many
1928 system vendors ship variant versions of @value{GDBN}, and there are
1929 variant versions of @value{GDBN} in @sc{gnu}/Linux distributions as well.
1930 The version number is the same as the one announced when you start
1933 @kindex show copying
1934 @kindex info copying
1935 @cindex display @value{GDBN} copyright
1938 Display information about permission for copying @value{GDBN}.
1940 @kindex show warranty
1941 @kindex info warranty
1943 @itemx info warranty
1944 Display the @sc{gnu} ``NO WARRANTY'' statement, or a warranty,
1945 if your version of @value{GDBN} comes with one.
1947 @kindex show configuration
1948 @item show configuration
1949 Display detailed information about the way @value{GDBN} was configured
1950 when it was built. This displays the optional arguments passed to the
1951 @file{configure} script and also configuration parameters detected
1952 automatically by @command{configure}. When reporting a @value{GDBN}
1953 bug (@pxref{GDB Bugs}), it is important to include this information in
1959 @chapter Running Programs Under @value{GDBN}
1961 When you run a program under @value{GDBN}, you must first generate
1962 debugging information when you compile it.
1964 You may start @value{GDBN} with its arguments, if any, in an environment
1965 of your choice. If you are doing native debugging, you may redirect
1966 your program's input and output, debug an already running process, or
1967 kill a child process.
1970 * Compilation:: Compiling for debugging
1971 * Starting:: Starting your program
1972 * Arguments:: Your program's arguments
1973 * Environment:: Your program's environment
1975 * Working Directory:: Your program's working directory
1976 * Input/Output:: Your program's input and output
1977 * Attach:: Debugging an already-running process
1978 * Kill Process:: Killing the child process
1980 * Inferiors and Programs:: Debugging multiple inferiors and programs
1981 * Threads:: Debugging programs with multiple threads
1982 * Forks:: Debugging forks
1983 * Checkpoint/Restart:: Setting a @emph{bookmark} to return to later
1987 @section Compiling for Debugging
1989 In order to debug a program effectively, you need to generate
1990 debugging information when you compile it. This debugging information
1991 is stored in the object file; it describes the data type of each
1992 variable or function and the correspondence between source line numbers
1993 and addresses in the executable code.
1995 To request debugging information, specify the @samp{-g} option when you run
1998 Programs that are to be shipped to your customers are compiled with
1999 optimizations, using the @samp{-O} compiler option. However, some
2000 compilers are unable to handle the @samp{-g} and @samp{-O} options
2001 together. Using those compilers, you cannot generate optimized
2002 executables containing debugging information.
2004 @value{NGCC}, the @sc{gnu} C/C@t{++} compiler, supports @samp{-g} with or
2005 without @samp{-O}, making it possible to debug optimized code. We
2006 recommend that you @emph{always} use @samp{-g} whenever you compile a
2007 program. You may think your program is correct, but there is no sense
2008 in pushing your luck. For more information, see @ref{Optimized Code}.
2010 Older versions of the @sc{gnu} C compiler permitted a variant option
2011 @w{@samp{-gg}} for debugging information. @value{GDBN} no longer supports this
2012 format; if your @sc{gnu} C compiler has this option, do not use it.
2014 @value{GDBN} knows about preprocessor macros and can show you their
2015 expansion (@pxref{Macros}). Most compilers do not include information
2016 about preprocessor macros in the debugging information if you specify
2017 the @option{-g} flag alone. Version 3.1 and later of @value{NGCC},
2018 the @sc{gnu} C compiler, provides macro information if you are using
2019 the DWARF debugging format, and specify the option @option{-g3}.
2021 @xref{Debugging Options,,Options for Debugging Your Program or GCC,
2022 gcc.info, Using the @sc{gnu} Compiler Collection (GCC)}, for more
2023 information on @value{NGCC} options affecting debug information.
2025 You will have the best debugging experience if you use the latest
2026 version of the DWARF debugging format that your compiler supports.
2027 DWARF is currently the most expressive and best supported debugging
2028 format in @value{GDBN}.
2032 @section Starting your Program
2038 @kindex r @r{(@code{run})}
2041 Use the @code{run} command to start your program under @value{GDBN}.
2042 You must first specify the program name with an argument to
2043 @value{GDBN} (@pxref{Invocation, ,Getting In and Out of
2044 @value{GDBN}}), or by using the @code{file} or @code{exec-file}
2045 command (@pxref{Files, ,Commands to Specify Files}).
2049 If you are running your program in an execution environment that
2050 supports processes, @code{run} creates an inferior process and makes
2051 that process run your program. In some environments without processes,
2052 @code{run} jumps to the start of your program. Other targets,
2053 like @samp{remote}, are always running. If you get an error
2054 message like this one:
2057 The "remote" target does not support "run".
2058 Try "help target" or "continue".
2062 then use @code{continue} to run your program. You may need @code{load}
2063 first (@pxref{load}).
2065 The execution of a program is affected by certain information it
2066 receives from its superior. @value{GDBN} provides ways to specify this
2067 information, which you must do @emph{before} starting your program. (You
2068 can change it after starting your program, but such changes only affect
2069 your program the next time you start it.) This information may be
2070 divided into four categories:
2073 @item The @emph{arguments.}
2074 Specify the arguments to give your program as the arguments of the
2075 @code{run} command. If a shell is available on your target, the shell
2076 is used to pass the arguments, so that you may use normal conventions
2077 (such as wildcard expansion or variable substitution) in describing
2079 In Unix systems, you can control which shell is used with the
2080 @code{SHELL} environment variable. If you do not define @code{SHELL},
2081 @value{GDBN} uses the default shell (@file{/bin/sh}). You can disable
2082 use of any shell with the @code{set startup-with-shell} command (see
2085 @item The @emph{environment.}
2086 Your program normally inherits its environment from @value{GDBN}, but you can
2087 use the @value{GDBN} commands @code{set environment} and @code{unset
2088 environment} to change parts of the environment that affect
2089 your program. @xref{Environment, ,Your Program's Environment}.
2091 @item The @emph{working directory.}
2092 You can set your program's working directory with the command
2093 @kbd{set cwd}. If you do not set any working directory with this
2094 command, your program will inherit @value{GDBN}'s working directory if
2095 native debugging, or the remote server's working directory if remote
2096 debugging. @xref{Working Directory, ,Your Program's Working
2099 @item The @emph{standard input and output.}
2100 Your program normally uses the same device for standard input and
2101 standard output as @value{GDBN} is using. You can redirect input and output
2102 in the @code{run} command line, or you can use the @code{tty} command to
2103 set a different device for your program.
2104 @xref{Input/Output, ,Your Program's Input and Output}.
2107 @emph{Warning:} While input and output redirection work, you cannot use
2108 pipes to pass the output of the program you are debugging to another
2109 program; if you attempt this, @value{GDBN} is likely to wind up debugging the
2113 When you issue the @code{run} command, your program begins to execute
2114 immediately. @xref{Stopping, ,Stopping and Continuing}, for discussion
2115 of how to arrange for your program to stop. Once your program has
2116 stopped, you may call functions in your program, using the @code{print}
2117 or @code{call} commands. @xref{Data, ,Examining Data}.
2119 If the modification time of your symbol file has changed since the last
2120 time @value{GDBN} read its symbols, @value{GDBN} discards its symbol
2121 table, and reads it again. When it does this, @value{GDBN} tries to retain
2122 your current breakpoints.
2127 @cindex run to main procedure
2128 The name of the main procedure can vary from language to language.
2129 With C or C@t{++}, the main procedure name is always @code{main}, but
2130 other languages such as Ada do not require a specific name for their
2131 main procedure. The debugger provides a convenient way to start the
2132 execution of the program and to stop at the beginning of the main
2133 procedure, depending on the language used.
2135 The @samp{start} command does the equivalent of setting a temporary
2136 breakpoint at the beginning of the main procedure and then invoking
2137 the @samp{run} command.
2139 @cindex elaboration phase
2140 Some programs contain an @dfn{elaboration} phase where some startup code is
2141 executed before the main procedure is called. This depends on the
2142 languages used to write your program. In C@t{++}, for instance,
2143 constructors for static and global objects are executed before
2144 @code{main} is called. It is therefore possible that the debugger stops
2145 before reaching the main procedure. However, the temporary breakpoint
2146 will remain to halt execution.
2148 Specify the arguments to give to your program as arguments to the
2149 @samp{start} command. These arguments will be given verbatim to the
2150 underlying @samp{run} command. Note that the same arguments will be
2151 reused if no argument is provided during subsequent calls to
2152 @samp{start} or @samp{run}.
2154 It is sometimes necessary to debug the program during elaboration. In
2155 these cases, using the @code{start} command would stop the execution
2156 of your program too late, as the program would have already completed
2157 the elaboration phase. Under these circumstances, either insert
2158 breakpoints in your elaboration code before running your program or
2159 use the @code{starti} command.
2163 @cindex run to first instruction
2164 The @samp{starti} command does the equivalent of setting a temporary
2165 breakpoint at the first instruction of a program's execution and then
2166 invoking the @samp{run} command. For programs containing an
2167 elaboration phase, the @code{starti} command will stop execution at
2168 the start of the elaboration phase.
2170 @anchor{set exec-wrapper}
2171 @kindex set exec-wrapper
2172 @item set exec-wrapper @var{wrapper}
2173 @itemx show exec-wrapper
2174 @itemx unset exec-wrapper
2175 When @samp{exec-wrapper} is set, the specified wrapper is used to
2176 launch programs for debugging. @value{GDBN} starts your program
2177 with a shell command of the form @kbd{exec @var{wrapper}
2178 @var{program}}. Quoting is added to @var{program} and its
2179 arguments, but not to @var{wrapper}, so you should add quotes if
2180 appropriate for your shell. The wrapper runs until it executes
2181 your program, and then @value{GDBN} takes control.
2183 You can use any program that eventually calls @code{execve} with
2184 its arguments as a wrapper. Several standard Unix utilities do
2185 this, e.g.@: @code{env} and @code{nohup}. Any Unix shell script ending
2186 with @code{exec "$@@"} will also work.
2188 For example, you can use @code{env} to pass an environment variable to
2189 the debugged program, without setting the variable in your shell's
2193 (@value{GDBP}) set exec-wrapper env 'LD_PRELOAD=libtest.so'
2197 This command is available when debugging locally on most targets, excluding
2198 @sc{djgpp}, Cygwin, MS Windows, and QNX Neutrino.
2200 @kindex set startup-with-shell
2201 @anchor{set startup-with-shell}
2202 @item set startup-with-shell
2203 @itemx set startup-with-shell on
2204 @itemx set startup-with-shell off
2205 @itemx show startup-with-shell
2206 On Unix systems, by default, if a shell is available on your target,
2207 @value{GDBN}) uses it to start your program. Arguments of the
2208 @code{run} command are passed to the shell, which does variable
2209 substitution, expands wildcard characters and performs redirection of
2210 I/O. In some circumstances, it may be useful to disable such use of a
2211 shell, for example, when debugging the shell itself or diagnosing
2212 startup failures such as:
2216 Starting program: ./a.out
2217 During startup program terminated with signal SIGSEGV, Segmentation fault.
2221 which indicates the shell or the wrapper specified with
2222 @samp{exec-wrapper} crashed, not your program. Most often, this is
2223 caused by something odd in your shell's non-interactive mode
2224 initialization file---such as @file{.cshrc} for C-shell,
2225 $@file{.zshenv} for the Z shell, or the file specified in the
2226 @samp{BASH_ENV} environment variable for BASH.
2228 @anchor{set auto-connect-native-target}
2229 @kindex set auto-connect-native-target
2230 @item set auto-connect-native-target
2231 @itemx set auto-connect-native-target on
2232 @itemx set auto-connect-native-target off
2233 @itemx show auto-connect-native-target
2235 By default, if not connected to any target yet (e.g., with
2236 @code{target remote}), the @code{run} command starts your program as a
2237 native process under @value{GDBN}, on your local machine. If you're
2238 sure you don't want to debug programs on your local machine, you can
2239 tell @value{GDBN} to not connect to the native target automatically
2240 with the @code{set auto-connect-native-target off} command.
2242 If @code{on}, which is the default, and if @value{GDBN} is not
2243 connected to a target already, the @code{run} command automaticaly
2244 connects to the native target, if one is available.
2246 If @code{off}, and if @value{GDBN} is not connected to a target
2247 already, the @code{run} command fails with an error:
2251 Don't know how to run. Try "help target".
2254 If @value{GDBN} is already connected to a target, @value{GDBN} always
2255 uses it with the @code{run} command.
2257 In any case, you can explicitly connect to the native target with the
2258 @code{target native} command. For example,
2261 (@value{GDBP}) set auto-connect-native-target off
2263 Don't know how to run. Try "help target".
2264 (@value{GDBP}) target native
2266 Starting program: ./a.out
2267 [Inferior 1 (process 10421) exited normally]
2270 In case you connected explicitly to the @code{native} target,
2271 @value{GDBN} remains connected even if all inferiors exit, ready for
2272 the next @code{run} command. Use the @code{disconnect} command to
2275 Examples of other commands that likewise respect the
2276 @code{auto-connect-native-target} setting: @code{attach}, @code{info
2277 proc}, @code{info os}.
2279 @kindex set disable-randomization
2280 @item set disable-randomization
2281 @itemx set disable-randomization on
2282 This option (enabled by default in @value{GDBN}) will turn off the native
2283 randomization of the virtual address space of the started program. This option
2284 is useful for multiple debugging sessions to make the execution better
2285 reproducible and memory addresses reusable across debugging sessions.
2287 This feature is implemented only on certain targets, including @sc{gnu}/Linux.
2288 On @sc{gnu}/Linux you can get the same behavior using
2291 (@value{GDBP}) set exec-wrapper setarch `uname -m` -R
2294 @item set disable-randomization off
2295 Leave the behavior of the started executable unchanged. Some bugs rear their
2296 ugly heads only when the program is loaded at certain addresses. If your bug
2297 disappears when you run the program under @value{GDBN}, that might be because
2298 @value{GDBN} by default disables the address randomization on platforms, such
2299 as @sc{gnu}/Linux, which do that for stand-alone programs. Use @kbd{set
2300 disable-randomization off} to try to reproduce such elusive bugs.
2302 On targets where it is available, virtual address space randomization
2303 protects the programs against certain kinds of security attacks. In these
2304 cases the attacker needs to know the exact location of a concrete executable
2305 code. Randomizing its location makes it impossible to inject jumps misusing
2306 a code at its expected addresses.
2308 Prelinking shared libraries provides a startup performance advantage but it
2309 makes addresses in these libraries predictable for privileged processes by
2310 having just unprivileged access at the target system. Reading the shared
2311 library binary gives enough information for assembling the malicious code
2312 misusing it. Still even a prelinked shared library can get loaded at a new
2313 random address just requiring the regular relocation process during the
2314 startup. Shared libraries not already prelinked are always loaded at
2315 a randomly chosen address.
2317 Position independent executables (PIE) contain position independent code
2318 similar to the shared libraries and therefore such executables get loaded at
2319 a randomly chosen address upon startup. PIE executables always load even
2320 already prelinked shared libraries at a random address. You can build such
2321 executable using @command{gcc -fPIE -pie}.
2323 Heap (malloc storage), stack and custom mmap areas are always placed randomly
2324 (as long as the randomization is enabled).
2326 @item show disable-randomization
2327 Show the current setting of the explicit disable of the native randomization of
2328 the virtual address space of the started program.
2333 @section Your Program's Arguments
2335 @cindex arguments (to your program)
2336 The arguments to your program can be specified by the arguments of the
2338 They are passed to a shell, which expands wildcard characters and
2339 performs redirection of I/O, and thence to your program. Your
2340 @code{SHELL} environment variable (if it exists) specifies what shell
2341 @value{GDBN} uses. If you do not define @code{SHELL}, @value{GDBN} uses
2342 the default shell (@file{/bin/sh} on Unix).
2344 On non-Unix systems, the program is usually invoked directly by
2345 @value{GDBN}, which emulates I/O redirection via the appropriate system
2346 calls, and the wildcard characters are expanded by the startup code of
2347 the program, not by the shell.
2349 @code{run} with no arguments uses the same arguments used by the previous
2350 @code{run}, or those set by the @code{set args} command.
2355 Specify the arguments to be used the next time your program is run. If
2356 @code{set args} has no arguments, @code{run} executes your program
2357 with no arguments. Once you have run your program with arguments,
2358 using @code{set args} before the next @code{run} is the only way to run
2359 it again without arguments.
2363 Show the arguments to give your program when it is started.
2367 @section Your Program's Environment
2369 @cindex environment (of your program)
2370 The @dfn{environment} consists of a set of environment variables and
2371 their values. Environment variables conventionally record such things as
2372 your user name, your home directory, your terminal type, and your search
2373 path for programs to run. Usually you set up environment variables with
2374 the shell and they are inherited by all the other programs you run. When
2375 debugging, it can be useful to try running your program with a modified
2376 environment without having to start @value{GDBN} over again.
2380 @item path @var{directory}
2381 Add @var{directory} to the front of the @code{PATH} environment variable
2382 (the search path for executables) that will be passed to your program.
2383 The value of @code{PATH} used by @value{GDBN} does not change.
2384 You may specify several directory names, separated by whitespace or by a
2385 system-dependent separator character (@samp{:} on Unix, @samp{;} on
2386 MS-DOS and MS-Windows). If @var{directory} is already in the path, it
2387 is moved to the front, so it is searched sooner.
2389 You can use the string @samp{$cwd} to refer to whatever is the current
2390 working directory at the time @value{GDBN} searches the path. If you
2391 use @samp{.} instead, it refers to the directory where you executed the
2392 @code{path} command. @value{GDBN} replaces @samp{.} in the
2393 @var{directory} argument (with the current path) before adding
2394 @var{directory} to the search path.
2395 @c 'path' is explicitly nonrepeatable, but RMS points out it is silly to
2396 @c document that, since repeating it would be a no-op.
2400 Display the list of search paths for executables (the @code{PATH}
2401 environment variable).
2403 @kindex show environment
2404 @item show environment @r{[}@var{varname}@r{]}
2405 Print the value of environment variable @var{varname} to be given to
2406 your program when it starts. If you do not supply @var{varname},
2407 print the names and values of all environment variables to be given to
2408 your program. You can abbreviate @code{environment} as @code{env}.
2410 @kindex set environment
2411 @anchor{set environment}
2412 @item set environment @var{varname} @r{[}=@var{value}@r{]}
2413 Set environment variable @var{varname} to @var{value}. The value
2414 changes for your program (and the shell @value{GDBN} uses to launch
2415 it), not for @value{GDBN} itself. The @var{value} may be any string; the
2416 values of environment variables are just strings, and any
2417 interpretation is supplied by your program itself. The @var{value}
2418 parameter is optional; if it is eliminated, the variable is set to a
2420 @c "any string" here does not include leading, trailing
2421 @c blanks. Gnu asks: does anyone care?
2423 For example, this command:
2430 tells the debugged program, when subsequently run, that its user is named
2431 @samp{foo}. (The spaces around @samp{=} are used for clarity here; they
2432 are not actually required.)
2434 Note that on Unix systems, @value{GDBN} runs your program via a shell,
2435 which also inherits the environment set with @code{set environment}.
2436 If necessary, you can avoid that by using the @samp{env} program as a
2437 wrapper instead of using @code{set environment}. @xref{set
2438 exec-wrapper}, for an example doing just that.
2440 Environment variables that are set by the user are also transmitted to
2441 @command{gdbserver} to be used when starting the remote inferior.
2442 @pxref{QEnvironmentHexEncoded}.
2444 @kindex unset environment
2445 @anchor{unset environment}
2446 @item unset environment @var{varname}
2447 Remove variable @var{varname} from the environment to be passed to your
2448 program. This is different from @samp{set env @var{varname} =};
2449 @code{unset environment} removes the variable from the environment,
2450 rather than assigning it an empty value.
2452 Environment variables that are unset by the user are also unset on
2453 @command{gdbserver} when starting the remote inferior.
2454 @pxref{QEnvironmentUnset}.
2457 @emph{Warning:} On Unix systems, @value{GDBN} runs your program using
2458 the shell indicated by your @code{SHELL} environment variable if it
2459 exists (or @code{/bin/sh} if not). If your @code{SHELL} variable
2460 names a shell that runs an initialization file when started
2461 non-interactively---such as @file{.cshrc} for C-shell, $@file{.zshenv}
2462 for the Z shell, or the file specified in the @samp{BASH_ENV}
2463 environment variable for BASH---any variables you set in that file
2464 affect your program. You may wish to move setting of environment
2465 variables to files that are only run when you sign on, such as
2466 @file{.login} or @file{.profile}.
2468 @node Working Directory
2469 @section Your Program's Working Directory
2471 @cindex working directory (of your program)
2472 Each time you start your program with @code{run}, the inferior will be
2473 initialized with the current working directory specified by the
2474 @kbd{set cwd} command. If no directory has been specified by this
2475 command, then the inferior will inherit @value{GDBN}'s current working
2476 directory as its working directory if native debugging, or it will
2477 inherit the remote server's current working directory if remote
2482 @cindex change inferior's working directory
2483 @anchor{set cwd command}
2484 @item set cwd @r{[}@var{directory}@r{]}
2485 Set the inferior's working directory to @var{directory}, which will be
2486 @code{glob}-expanded in order to resolve tildes (@file{~}). If no
2487 argument has been specified, the command clears the setting and resets
2488 it to an empty state. This setting has no effect on @value{GDBN}'s
2489 working directory, and it only takes effect the next time you start
2490 the inferior. The @file{~} in @var{directory} is a short for the
2491 @dfn{home directory}, usually pointed to by the @env{HOME} environment
2492 variable. On MS-Windows, if @env{HOME} is not defined, @value{GDBN}
2493 uses the concatenation of @env{HOMEDRIVE} and @env{HOMEPATH} as
2496 You can also change @value{GDBN}'s current working directory by using
2497 the @code{cd} command.
2501 @cindex show inferior's working directory
2503 Show the inferior's working directory. If no directory has been
2504 specified by @kbd{set cwd}, then the default inferior's working
2505 directory is the same as @value{GDBN}'s working directory.
2508 @cindex change @value{GDBN}'s working directory
2510 @item cd @r{[}@var{directory}@r{]}
2511 Set the @value{GDBN} working directory to @var{directory}. If not
2512 given, @var{directory} uses @file{'~'}.
2514 The @value{GDBN} working directory serves as a default for the
2515 commands that specify files for @value{GDBN} to operate on.
2516 @xref{Files, ,Commands to Specify Files}.
2517 @xref{set cwd command}.
2521 Print the @value{GDBN} working directory.
2524 It is generally impossible to find the current working directory of
2525 the process being debugged (since a program can change its directory
2526 during its run). If you work on a system where @value{GDBN} supports
2527 the @code{info proc} command (@pxref{Process Information}), you can
2528 use the @code{info proc} command to find out the
2529 current working directory of the debuggee.
2532 @section Your Program's Input and Output
2537 By default, the program you run under @value{GDBN} does input and output to
2538 the same terminal that @value{GDBN} uses. @value{GDBN} switches the terminal
2539 to its own terminal modes to interact with you, but it records the terminal
2540 modes your program was using and switches back to them when you continue
2541 running your program.
2544 @kindex info terminal
2546 Displays information recorded by @value{GDBN} about the terminal modes your
2550 You can redirect your program's input and/or output using shell
2551 redirection with the @code{run} command. For example,
2558 starts your program, diverting its output to the file @file{outfile}.
2561 @cindex controlling terminal
2562 Another way to specify where your program should do input and output is
2563 with the @code{tty} command. This command accepts a file name as
2564 argument, and causes this file to be the default for future @code{run}
2565 commands. It also resets the controlling terminal for the child
2566 process, for future @code{run} commands. For example,
2573 directs that processes started with subsequent @code{run} commands
2574 default to do input and output on the terminal @file{/dev/ttyb} and have
2575 that as their controlling terminal.
2577 An explicit redirection in @code{run} overrides the @code{tty} command's
2578 effect on the input/output device, but not its effect on the controlling
2581 When you use the @code{tty} command or redirect input in the @code{run}
2582 command, only the input @emph{for your program} is affected. The input
2583 for @value{GDBN} still comes from your terminal. @code{tty} is an alias
2584 for @code{set inferior-tty}.
2586 @cindex inferior tty
2587 @cindex set inferior controlling terminal
2588 You can use the @code{show inferior-tty} command to tell @value{GDBN} to
2589 display the name of the terminal that will be used for future runs of your
2593 @item set inferior-tty [ @var{tty} ]
2594 @kindex set inferior-tty
2595 Set the tty for the program being debugged to @var{tty}. Omitting @var{tty}
2596 restores the default behavior, which is to use the same terminal as
2599 @item show inferior-tty
2600 @kindex show inferior-tty
2601 Show the current tty for the program being debugged.
2605 @section Debugging an Already-running Process
2610 @item attach @var{process-id}
2611 This command attaches to a running process---one that was started
2612 outside @value{GDBN}. (@code{info files} shows your active
2613 targets.) The command takes as argument a process ID. The usual way to
2614 find out the @var{process-id} of a Unix process is with the @code{ps} utility,
2615 or with the @samp{jobs -l} shell command.
2617 @code{attach} does not repeat if you press @key{RET} a second time after
2618 executing the command.
2621 To use @code{attach}, your program must be running in an environment
2622 which supports processes; for example, @code{attach} does not work for
2623 programs on bare-board targets that lack an operating system. You must
2624 also have permission to send the process a signal.
2626 When you use @code{attach}, the debugger finds the program running in
2627 the process first by looking in the current working directory, then (if
2628 the program is not found) by using the source file search path
2629 (@pxref{Source Path, ,Specifying Source Directories}). You can also use
2630 the @code{file} command to load the program. @xref{Files, ,Commands to
2633 The first thing @value{GDBN} does after arranging to debug the specified
2634 process is to stop it. You can examine and modify an attached process
2635 with all the @value{GDBN} commands that are ordinarily available when
2636 you start processes with @code{run}. You can insert breakpoints; you
2637 can step and continue; you can modify storage. If you would rather the
2638 process continue running, you may use the @code{continue} command after
2639 attaching @value{GDBN} to the process.
2644 When you have finished debugging the attached process, you can use the
2645 @code{detach} command to release it from @value{GDBN} control. Detaching
2646 the process continues its execution. After the @code{detach} command,
2647 that process and @value{GDBN} become completely independent once more, and you
2648 are ready to @code{attach} another process or start one with @code{run}.
2649 @code{detach} does not repeat if you press @key{RET} again after
2650 executing the command.
2653 If you exit @value{GDBN} while you have an attached process, you detach
2654 that process. If you use the @code{run} command, you kill that process.
2655 By default, @value{GDBN} asks for confirmation if you try to do either of these
2656 things; you can control whether or not you need to confirm by using the
2657 @code{set confirm} command (@pxref{Messages/Warnings, ,Optional Warnings and
2661 @section Killing the Child Process
2666 Kill the child process in which your program is running under @value{GDBN}.
2669 This command is useful if you wish to debug a core dump instead of a
2670 running process. @value{GDBN} ignores any core dump file while your program
2673 On some operating systems, a program cannot be executed outside @value{GDBN}
2674 while you have breakpoints set on it inside @value{GDBN}. You can use the
2675 @code{kill} command in this situation to permit running your program
2676 outside the debugger.
2678 The @code{kill} command is also useful if you wish to recompile and
2679 relink your program, since on many systems it is impossible to modify an
2680 executable file while it is running in a process. In this case, when you
2681 next type @code{run}, @value{GDBN} notices that the file has changed, and
2682 reads the symbol table again (while trying to preserve your current
2683 breakpoint settings).
2685 @node Inferiors and Programs
2686 @section Debugging Multiple Inferiors and Programs
2688 @value{GDBN} lets you run and debug multiple programs in a single
2689 session. In addition, @value{GDBN} on some systems may let you run
2690 several programs simultaneously (otherwise you have to exit from one
2691 before starting another). In the most general case, you can have
2692 multiple threads of execution in each of multiple processes, launched
2693 from multiple executables.
2696 @value{GDBN} represents the state of each program execution with an
2697 object called an @dfn{inferior}. An inferior typically corresponds to
2698 a process, but is more general and applies also to targets that do not
2699 have processes. Inferiors may be created before a process runs, and
2700 may be retained after a process exits. Inferiors have unique
2701 identifiers that are different from process ids. Usually each
2702 inferior will also have its own distinct address space, although some
2703 embedded targets may have several inferiors running in different parts
2704 of a single address space. Each inferior may in turn have multiple
2705 threads running in it.
2707 To find out what inferiors exist at any moment, use @w{@code{info
2711 @kindex info inferiors [ @var{id}@dots{} ]
2712 @item info inferiors
2713 Print a list of all inferiors currently being managed by @value{GDBN}.
2714 By default all inferiors are printed, but the argument @var{id}@dots{}
2715 -- a space separated list of inferior numbers -- can be used to limit
2716 the display to just the requested inferiors.
2718 @value{GDBN} displays for each inferior (in this order):
2722 the inferior number assigned by @value{GDBN}
2725 the target system's inferior identifier
2728 the name of the executable the inferior is running.
2733 An asterisk @samp{*} preceding the @value{GDBN} inferior number
2734 indicates the current inferior.
2738 @c end table here to get a little more width for example
2741 (@value{GDBP}) info inferiors
2742 Num Description Executable
2743 2 process 2307 hello
2744 * 1 process 3401 goodbye
2747 To switch focus between inferiors, use the @code{inferior} command:
2750 @kindex inferior @var{infno}
2751 @item inferior @var{infno}
2752 Make inferior number @var{infno} the current inferior. The argument
2753 @var{infno} is the inferior number assigned by @value{GDBN}, as shown
2754 in the first field of the @samp{info inferiors} display.
2757 @vindex $_inferior@r{, convenience variable}
2758 The debugger convenience variable @samp{$_inferior} contains the
2759 number of the current inferior. You may find this useful in writing
2760 breakpoint conditional expressions, command scripts, and so forth.
2761 @xref{Convenience Vars,, Convenience Variables}, for general
2762 information on convenience variables.
2764 You can get multiple executables into a debugging session via the
2765 @code{add-inferior} and @w{@code{clone-inferior}} commands. On some
2766 systems @value{GDBN} can add inferiors to the debug session
2767 automatically by following calls to @code{fork} and @code{exec}. To
2768 remove inferiors from the debugging session use the
2769 @w{@code{remove-inferiors}} command.
2772 @kindex add-inferior
2773 @item add-inferior [ -copies @var{n} ] [ -exec @var{executable} ]
2774 Adds @var{n} inferiors to be run using @var{executable} as the
2775 executable; @var{n} defaults to 1. If no executable is specified,
2776 the inferiors begins empty, with no program. You can still assign or
2777 change the program assigned to the inferior at any time by using the
2778 @code{file} command with the executable name as its argument.
2780 @kindex clone-inferior
2781 @item clone-inferior [ -copies @var{n} ] [ @var{infno} ]
2782 Adds @var{n} inferiors ready to execute the same program as inferior
2783 @var{infno}; @var{n} defaults to 1, and @var{infno} defaults to the
2784 number of the current inferior. This is a convenient command when you
2785 want to run another instance of the inferior you are debugging.
2788 (@value{GDBP}) info inferiors
2789 Num Description Executable
2790 * 1 process 29964 helloworld
2791 (@value{GDBP}) clone-inferior
2794 (@value{GDBP}) info inferiors
2795 Num Description Executable
2797 * 1 process 29964 helloworld
2800 You can now simply switch focus to inferior 2 and run it.
2802 @kindex remove-inferiors
2803 @item remove-inferiors @var{infno}@dots{}
2804 Removes the inferior or inferiors @var{infno}@dots{}. It is not
2805 possible to remove an inferior that is running with this command. For
2806 those, use the @code{kill} or @code{detach} command first.
2810 To quit debugging one of the running inferiors that is not the current
2811 inferior, you can either detach from it by using the @w{@code{detach
2812 inferior}} command (allowing it to run independently), or kill it
2813 using the @w{@code{kill inferiors}} command:
2816 @kindex detach inferiors @var{infno}@dots{}
2817 @item detach inferior @var{infno}@dots{}
2818 Detach from the inferior or inferiors identified by @value{GDBN}
2819 inferior number(s) @var{infno}@dots{}. Note that the inferior's entry
2820 still stays on the list of inferiors shown by @code{info inferiors},
2821 but its Description will show @samp{<null>}.
2823 @kindex kill inferiors @var{infno}@dots{}
2824 @item kill inferiors @var{infno}@dots{}
2825 Kill the inferior or inferiors identified by @value{GDBN} inferior
2826 number(s) @var{infno}@dots{}. Note that the inferior's entry still
2827 stays on the list of inferiors shown by @code{info inferiors}, but its
2828 Description will show @samp{<null>}.
2831 After the successful completion of a command such as @code{detach},
2832 @code{detach inferiors}, @code{kill} or @code{kill inferiors}, or after
2833 a normal process exit, the inferior is still valid and listed with
2834 @code{info inferiors}, ready to be restarted.
2837 To be notified when inferiors are started or exit under @value{GDBN}'s
2838 control use @w{@code{set print inferior-events}}:
2841 @kindex set print inferior-events
2842 @cindex print messages on inferior start and exit
2843 @item set print inferior-events
2844 @itemx set print inferior-events on
2845 @itemx set print inferior-events off
2846 The @code{set print inferior-events} command allows you to enable or
2847 disable printing of messages when @value{GDBN} notices that new
2848 inferiors have started or that inferiors have exited or have been
2849 detached. By default, these messages will not be printed.
2851 @kindex show print inferior-events
2852 @item show print inferior-events
2853 Show whether messages will be printed when @value{GDBN} detects that
2854 inferiors have started, exited or have been detached.
2857 Many commands will work the same with multiple programs as with a
2858 single program: e.g., @code{print myglobal} will simply display the
2859 value of @code{myglobal} in the current inferior.
2862 Occasionaly, when debugging @value{GDBN} itself, it may be useful to
2863 get more info about the relationship of inferiors, programs, address
2864 spaces in a debug session. You can do that with the @w{@code{maint
2865 info program-spaces}} command.
2868 @kindex maint info program-spaces
2869 @item maint info program-spaces
2870 Print a list of all program spaces currently being managed by
2873 @value{GDBN} displays for each program space (in this order):
2877 the program space number assigned by @value{GDBN}
2880 the name of the executable loaded into the program space, with e.g.,
2881 the @code{file} command.
2886 An asterisk @samp{*} preceding the @value{GDBN} program space number
2887 indicates the current program space.
2889 In addition, below each program space line, @value{GDBN} prints extra
2890 information that isn't suitable to display in tabular form. For
2891 example, the list of inferiors bound to the program space.
2894 (@value{GDBP}) maint info program-spaces
2898 Bound inferiors: ID 1 (process 21561)
2901 Here we can see that no inferior is running the program @code{hello},
2902 while @code{process 21561} is running the program @code{goodbye}. On
2903 some targets, it is possible that multiple inferiors are bound to the
2904 same program space. The most common example is that of debugging both
2905 the parent and child processes of a @code{vfork} call. For example,
2908 (@value{GDBP}) maint info program-spaces
2911 Bound inferiors: ID 2 (process 18050), ID 1 (process 18045)
2914 Here, both inferior 2 and inferior 1 are running in the same program
2915 space as a result of inferior 1 having executed a @code{vfork} call.
2919 @section Debugging Programs with Multiple Threads
2921 @cindex threads of execution
2922 @cindex multiple threads
2923 @cindex switching threads
2924 In some operating systems, such as GNU/Linux and Solaris, a single program
2925 may have more than one @dfn{thread} of execution. The precise semantics
2926 of threads differ from one operating system to another, but in general
2927 the threads of a single program are akin to multiple processes---except
2928 that they share one address space (that is, they can all examine and
2929 modify the same variables). On the other hand, each thread has its own
2930 registers and execution stack, and perhaps private memory.
2932 @value{GDBN} provides these facilities for debugging multi-thread
2936 @item automatic notification of new threads
2937 @item @samp{thread @var{thread-id}}, a command to switch among threads
2938 @item @samp{info threads}, a command to inquire about existing threads
2939 @item @samp{thread apply [@var{thread-id-list}] [@var{all}] @var{args}},
2940 a command to apply a command to a list of threads
2941 @item thread-specific breakpoints
2942 @item @samp{set print thread-events}, which controls printing of
2943 messages on thread start and exit.
2944 @item @samp{set libthread-db-search-path @var{path}}, which lets
2945 the user specify which @code{libthread_db} to use if the default choice
2946 isn't compatible with the program.
2949 @cindex focus of debugging
2950 @cindex current thread
2951 The @value{GDBN} thread debugging facility allows you to observe all
2952 threads while your program runs---but whenever @value{GDBN} takes
2953 control, one thread in particular is always the focus of debugging.
2954 This thread is called the @dfn{current thread}. Debugging commands show
2955 program information from the perspective of the current thread.
2957 @cindex @code{New} @var{systag} message
2958 @cindex thread identifier (system)
2959 @c FIXME-implementors!! It would be more helpful if the [New...] message
2960 @c included GDB's numeric thread handle, so you could just go to that
2961 @c thread without first checking `info threads'.
2962 Whenever @value{GDBN} detects a new thread in your program, it displays
2963 the target system's identification for the thread with a message in the
2964 form @samp{[New @var{systag}]}, where @var{systag} is a thread identifier
2965 whose form varies depending on the particular system. For example, on
2966 @sc{gnu}/Linux, you might see
2969 [New Thread 0x41e02940 (LWP 25582)]
2973 when @value{GDBN} notices a new thread. In contrast, on other systems,
2974 the @var{systag} is simply something like @samp{process 368}, with no
2977 @c FIXME!! (1) Does the [New...] message appear even for the very first
2978 @c thread of a program, or does it only appear for the
2979 @c second---i.e.@: when it becomes obvious we have a multithread
2981 @c (2) *Is* there necessarily a first thread always? Or do some
2982 @c multithread systems permit starting a program with multiple
2983 @c threads ab initio?
2985 @anchor{thread numbers}
2986 @cindex thread number, per inferior
2987 @cindex thread identifier (GDB)
2988 For debugging purposes, @value{GDBN} associates its own thread number
2989 ---always a single integer---with each thread of an inferior. This
2990 number is unique between all threads of an inferior, but not unique
2991 between threads of different inferiors.
2993 @cindex qualified thread ID
2994 You can refer to a given thread in an inferior using the qualified
2995 @var{inferior-num}.@var{thread-num} syntax, also known as
2996 @dfn{qualified thread ID}, with @var{inferior-num} being the inferior
2997 number and @var{thread-num} being the thread number of the given
2998 inferior. For example, thread @code{2.3} refers to thread number 3 of
2999 inferior 2. If you omit @var{inferior-num} (e.g., @code{thread 3}),
3000 then @value{GDBN} infers you're referring to a thread of the current
3003 Until you create a second inferior, @value{GDBN} does not show the
3004 @var{inferior-num} part of thread IDs, even though you can always use
3005 the full @var{inferior-num}.@var{thread-num} form to refer to threads
3006 of inferior 1, the initial inferior.
3008 @anchor{thread ID lists}
3009 @cindex thread ID lists
3010 Some commands accept a space-separated @dfn{thread ID list} as
3011 argument. A list element can be:
3015 A thread ID as shown in the first field of the @samp{info threads}
3016 display, with or without an inferior qualifier. E.g., @samp{2.1} or
3020 A range of thread numbers, again with or without an inferior
3021 qualifier, as in @var{inf}.@var{thr1}-@var{thr2} or
3022 @var{thr1}-@var{thr2}. E.g., @samp{1.2-4} or @samp{2-4}.
3025 All threads of an inferior, specified with a star wildcard, with or
3026 without an inferior qualifier, as in @var{inf}.@code{*} (e.g.,
3027 @samp{1.*}) or @code{*}. The former refers to all threads of the
3028 given inferior, and the latter form without an inferior qualifier
3029 refers to all threads of the current inferior.
3033 For example, if the current inferior is 1, and inferior 7 has one
3034 thread with ID 7.1, the thread list @samp{1 2-3 4.5 6.7-9 7.*}
3035 includes threads 1 to 3 of inferior 1, thread 5 of inferior 4, threads
3036 7 to 9 of inferior 6 and all threads of inferior 7. That is, in
3037 expanded qualified form, the same as @samp{1.1 1.2 1.3 4.5 6.7 6.8 6.9
3041 @anchor{global thread numbers}
3042 @cindex global thread number
3043 @cindex global thread identifier (GDB)
3044 In addition to a @emph{per-inferior} number, each thread is also
3045 assigned a unique @emph{global} number, also known as @dfn{global
3046 thread ID}, a single integer. Unlike the thread number component of
3047 the thread ID, no two threads have the same global ID, even when
3048 you're debugging multiple inferiors.
3050 From @value{GDBN}'s perspective, a process always has at least one
3051 thread. In other words, @value{GDBN} assigns a thread number to the
3052 program's ``main thread'' even if the program is not multi-threaded.
3054 @vindex $_thread@r{, convenience variable}
3055 @vindex $_gthread@r{, convenience variable}
3056 The debugger convenience variables @samp{$_thread} and
3057 @samp{$_gthread} contain, respectively, the per-inferior thread number
3058 and the global thread number of the current thread. You may find this
3059 useful in writing breakpoint conditional expressions, command scripts,
3060 and so forth. @xref{Convenience Vars,, Convenience Variables}, for
3061 general information on convenience variables.
3063 If @value{GDBN} detects the program is multi-threaded, it augments the
3064 usual message about stopping at a breakpoint with the ID and name of
3065 the thread that hit the breakpoint.
3068 Thread 2 "client" hit Breakpoint 1, send_message () at client.c:68
3071 Likewise when the program receives a signal:
3074 Thread 1 "main" received signal SIGINT, Interrupt.
3078 @kindex info threads
3079 @item info threads @r{[}@var{thread-id-list}@r{]}
3081 Display information about one or more threads. With no arguments
3082 displays information about all threads. You can specify the list of
3083 threads that you want to display using the thread ID list syntax
3084 (@pxref{thread ID lists}).
3086 @value{GDBN} displays for each thread (in this order):
3090 the per-inferior thread number assigned by @value{GDBN}
3093 the global thread number assigned by @value{GDBN}, if the @samp{-gid}
3094 option was specified
3097 the target system's thread identifier (@var{systag})
3100 the thread's name, if one is known. A thread can either be named by
3101 the user (see @code{thread name}, below), or, in some cases, by the
3105 the current stack frame summary for that thread
3109 An asterisk @samp{*} to the left of the @value{GDBN} thread number
3110 indicates the current thread.
3114 @c end table here to get a little more width for example
3117 (@value{GDBP}) info threads
3119 * 1 process 35 thread 13 main (argc=1, argv=0x7ffffff8)
3120 2 process 35 thread 23 0x34e5 in sigpause ()
3121 3 process 35 thread 27 0x34e5 in sigpause ()
3125 If you're debugging multiple inferiors, @value{GDBN} displays thread
3126 IDs using the qualified @var{inferior-num}.@var{thread-num} format.
3127 Otherwise, only @var{thread-num} is shown.
3129 If you specify the @samp{-gid} option, @value{GDBN} displays a column
3130 indicating each thread's global thread ID:
3133 (@value{GDBP}) info threads
3134 Id GId Target Id Frame
3135 1.1 1 process 35 thread 13 main (argc=1, argv=0x7ffffff8)
3136 1.2 3 process 35 thread 23 0x34e5 in sigpause ()
3137 1.3 4 process 35 thread 27 0x34e5 in sigpause ()
3138 * 2.1 2 process 65 thread 1 main (argc=1, argv=0x7ffffff8)
3141 On Solaris, you can display more information about user threads with a
3142 Solaris-specific command:
3145 @item maint info sol-threads
3146 @kindex maint info sol-threads
3147 @cindex thread info (Solaris)
3148 Display info on Solaris user threads.
3152 @kindex thread @var{thread-id}
3153 @item thread @var{thread-id}
3154 Make thread ID @var{thread-id} the current thread. The command
3155 argument @var{thread-id} is the @value{GDBN} thread ID, as shown in
3156 the first field of the @samp{info threads} display, with or without an
3157 inferior qualifier (e.g., @samp{2.1} or @samp{1}).
3159 @value{GDBN} responds by displaying the system identifier of the
3160 thread you selected, and its current stack frame summary:
3163 (@value{GDBP}) thread 2
3164 [Switching to thread 2 (Thread 0xb7fdab70 (LWP 12747))]
3165 #0 some_function (ignore=0x0) at example.c:8
3166 8 printf ("hello\n");
3170 As with the @samp{[New @dots{}]} message, the form of the text after
3171 @samp{Switching to} depends on your system's conventions for identifying
3174 @kindex thread apply
3175 @cindex apply command to several threads
3176 @item thread apply [@var{thread-id-list} | all [-ascending]] @var{command}
3177 The @code{thread apply} command allows you to apply the named
3178 @var{command} to one or more threads. Specify the threads that you
3179 want affected using the thread ID list syntax (@pxref{thread ID
3180 lists}), or specify @code{all} to apply to all threads. To apply a
3181 command to all threads in descending order, type @kbd{thread apply all
3182 @var{command}}. To apply a command to all threads in ascending order,
3183 type @kbd{thread apply all -ascending @var{command}}.
3187 @cindex name a thread
3188 @item thread name [@var{name}]
3189 This command assigns a name to the current thread. If no argument is
3190 given, any existing user-specified name is removed. The thread name
3191 appears in the @samp{info threads} display.
3193 On some systems, such as @sc{gnu}/Linux, @value{GDBN} is able to
3194 determine the name of the thread as given by the OS. On these
3195 systems, a name specified with @samp{thread name} will override the
3196 system-give name, and removing the user-specified name will cause
3197 @value{GDBN} to once again display the system-specified name.
3200 @cindex search for a thread
3201 @item thread find [@var{regexp}]
3202 Search for and display thread ids whose name or @var{systag}
3203 matches the supplied regular expression.
3205 As well as being the complement to the @samp{thread name} command,
3206 this command also allows you to identify a thread by its target
3207 @var{systag}. For instance, on @sc{gnu}/Linux, the target @var{systag}
3211 (@value{GDBN}) thread find 26688
3212 Thread 4 has target id 'Thread 0x41e02940 (LWP 26688)'
3213 (@value{GDBN}) info thread 4
3215 4 Thread 0x41e02940 (LWP 26688) 0x00000031ca6cd372 in select ()
3218 @kindex set print thread-events
3219 @cindex print messages on thread start and exit
3220 @item set print thread-events
3221 @itemx set print thread-events on
3222 @itemx set print thread-events off
3223 The @code{set print thread-events} command allows you to enable or
3224 disable printing of messages when @value{GDBN} notices that new threads have
3225 started or that threads have exited. By default, these messages will
3226 be printed if detection of these events is supported by the target.
3227 Note that these messages cannot be disabled on all targets.
3229 @kindex show print thread-events
3230 @item show print thread-events
3231 Show whether messages will be printed when @value{GDBN} detects that threads
3232 have started and exited.
3235 @xref{Thread Stops,,Stopping and Starting Multi-thread Programs}, for
3236 more information about how @value{GDBN} behaves when you stop and start
3237 programs with multiple threads.
3239 @xref{Set Watchpoints,,Setting Watchpoints}, for information about
3240 watchpoints in programs with multiple threads.
3242 @anchor{set libthread-db-search-path}
3244 @kindex set libthread-db-search-path
3245 @cindex search path for @code{libthread_db}
3246 @item set libthread-db-search-path @r{[}@var{path}@r{]}
3247 If this variable is set, @var{path} is a colon-separated list of
3248 directories @value{GDBN} will use to search for @code{libthread_db}.
3249 If you omit @var{path}, @samp{libthread-db-search-path} will be reset to
3250 its default value (@code{$sdir:$pdir} on @sc{gnu}/Linux and Solaris systems).
3251 Internally, the default value comes from the @code{LIBTHREAD_DB_SEARCH_PATH}
3254 On @sc{gnu}/Linux and Solaris systems, @value{GDBN} uses a ``helper''
3255 @code{libthread_db} library to obtain information about threads in the
3256 inferior process. @value{GDBN} will use @samp{libthread-db-search-path}
3257 to find @code{libthread_db}. @value{GDBN} also consults first if inferior
3258 specific thread debugging library loading is enabled
3259 by @samp{set auto-load libthread-db} (@pxref{libthread_db.so.1 file}).
3261 A special entry @samp{$sdir} for @samp{libthread-db-search-path}
3262 refers to the default system directories that are
3263 normally searched for loading shared libraries. The @samp{$sdir} entry
3264 is the only kind not needing to be enabled by @samp{set auto-load libthread-db}
3265 (@pxref{libthread_db.so.1 file}).
3267 A special entry @samp{$pdir} for @samp{libthread-db-search-path}
3268 refers to the directory from which @code{libpthread}
3269 was loaded in the inferior process.
3271 For any @code{libthread_db} library @value{GDBN} finds in above directories,
3272 @value{GDBN} attempts to initialize it with the current inferior process.
3273 If this initialization fails (which could happen because of a version
3274 mismatch between @code{libthread_db} and @code{libpthread}), @value{GDBN}
3275 will unload @code{libthread_db}, and continue with the next directory.
3276 If none of @code{libthread_db} libraries initialize successfully,
3277 @value{GDBN} will issue a warning and thread debugging will be disabled.
3279 Setting @code{libthread-db-search-path} is currently implemented
3280 only on some platforms.
3282 @kindex show libthread-db-search-path
3283 @item show libthread-db-search-path
3284 Display current libthread_db search path.
3286 @kindex set debug libthread-db
3287 @kindex show debug libthread-db
3288 @cindex debugging @code{libthread_db}
3289 @item set debug libthread-db
3290 @itemx show debug libthread-db
3291 Turns on or off display of @code{libthread_db}-related events.
3292 Use @code{1} to enable, @code{0} to disable.
3296 @section Debugging Forks
3298 @cindex fork, debugging programs which call
3299 @cindex multiple processes
3300 @cindex processes, multiple
3301 On most systems, @value{GDBN} has no special support for debugging
3302 programs which create additional processes using the @code{fork}
3303 function. When a program forks, @value{GDBN} will continue to debug the
3304 parent process and the child process will run unimpeded. If you have
3305 set a breakpoint in any code which the child then executes, the child
3306 will get a @code{SIGTRAP} signal which (unless it catches the signal)
3307 will cause it to terminate.
3309 However, if you want to debug the child process there is a workaround
3310 which isn't too painful. Put a call to @code{sleep} in the code which
3311 the child process executes after the fork. It may be useful to sleep
3312 only if a certain environment variable is set, or a certain file exists,
3313 so that the delay need not occur when you don't want to run @value{GDBN}
3314 on the child. While the child is sleeping, use the @code{ps} program to
3315 get its process ID. Then tell @value{GDBN} (a new invocation of
3316 @value{GDBN} if you are also debugging the parent process) to attach to
3317 the child process (@pxref{Attach}). From that point on you can debug
3318 the child process just like any other process which you attached to.
3320 On some systems, @value{GDBN} provides support for debugging programs
3321 that create additional processes using the @code{fork} or @code{vfork}
3322 functions. On @sc{gnu}/Linux platforms, this feature is supported
3323 with kernel version 2.5.46 and later.
3325 The fork debugging commands are supported in native mode and when
3326 connected to @code{gdbserver} in either @code{target remote} mode or
3327 @code{target extended-remote} mode.
3329 By default, when a program forks, @value{GDBN} will continue to debug
3330 the parent process and the child process will run unimpeded.
3332 If you want to follow the child process instead of the parent process,
3333 use the command @w{@code{set follow-fork-mode}}.
3336 @kindex set follow-fork-mode
3337 @item set follow-fork-mode @var{mode}
3338 Set the debugger response to a program call of @code{fork} or
3339 @code{vfork}. A call to @code{fork} or @code{vfork} creates a new
3340 process. The @var{mode} argument can be:
3344 The original process is debugged after a fork. The child process runs
3345 unimpeded. This is the default.
3348 The new process is debugged after a fork. The parent process runs
3353 @kindex show follow-fork-mode
3354 @item show follow-fork-mode
3355 Display the current debugger response to a @code{fork} or @code{vfork} call.
3358 @cindex debugging multiple processes
3359 On Linux, if you want to debug both the parent and child processes, use the
3360 command @w{@code{set detach-on-fork}}.
3363 @kindex set detach-on-fork
3364 @item set detach-on-fork @var{mode}
3365 Tells gdb whether to detach one of the processes after a fork, or
3366 retain debugger control over them both.
3370 The child process (or parent process, depending on the value of
3371 @code{follow-fork-mode}) will be detached and allowed to run
3372 independently. This is the default.
3375 Both processes will be held under the control of @value{GDBN}.
3376 One process (child or parent, depending on the value of
3377 @code{follow-fork-mode}) is debugged as usual, while the other
3382 @kindex show detach-on-fork
3383 @item show detach-on-fork
3384 Show whether detach-on-fork mode is on/off.
3387 If you choose to set @samp{detach-on-fork} mode off, then @value{GDBN}
3388 will retain control of all forked processes (including nested forks).
3389 You can list the forked processes under the control of @value{GDBN} by
3390 using the @w{@code{info inferiors}} command, and switch from one fork
3391 to another by using the @code{inferior} command (@pxref{Inferiors and
3392 Programs, ,Debugging Multiple Inferiors and Programs}).
3394 To quit debugging one of the forked processes, you can either detach
3395 from it by using the @w{@code{detach inferiors}} command (allowing it
3396 to run independently), or kill it using the @w{@code{kill inferiors}}
3397 command. @xref{Inferiors and Programs, ,Debugging Multiple Inferiors
3400 If you ask to debug a child process and a @code{vfork} is followed by an
3401 @code{exec}, @value{GDBN} executes the new target up to the first
3402 breakpoint in the new target. If you have a breakpoint set on
3403 @code{main} in your original program, the breakpoint will also be set on
3404 the child process's @code{main}.
3406 On some systems, when a child process is spawned by @code{vfork}, you
3407 cannot debug the child or parent until an @code{exec} call completes.
3409 If you issue a @code{run} command to @value{GDBN} after an @code{exec}
3410 call executes, the new target restarts. To restart the parent
3411 process, use the @code{file} command with the parent executable name
3412 as its argument. By default, after an @code{exec} call executes,
3413 @value{GDBN} discards the symbols of the previous executable image.
3414 You can change this behaviour with the @w{@code{set follow-exec-mode}}
3418 @kindex set follow-exec-mode
3419 @item set follow-exec-mode @var{mode}
3421 Set debugger response to a program call of @code{exec}. An
3422 @code{exec} call replaces the program image of a process.
3424 @code{follow-exec-mode} can be:
3428 @value{GDBN} creates a new inferior and rebinds the process to this
3429 new inferior. The program the process was running before the
3430 @code{exec} call can be restarted afterwards by restarting the
3436 (@value{GDBP}) info inferiors
3438 Id Description Executable
3441 process 12020 is executing new program: prog2
3442 Program exited normally.
3443 (@value{GDBP}) info inferiors
3444 Id Description Executable
3450 @value{GDBN} keeps the process bound to the same inferior. The new
3451 executable image replaces the previous executable loaded in the
3452 inferior. Restarting the inferior after the @code{exec} call, with
3453 e.g., the @code{run} command, restarts the executable the process was
3454 running after the @code{exec} call. This is the default mode.
3459 (@value{GDBP}) info inferiors
3460 Id Description Executable
3463 process 12020 is executing new program: prog2
3464 Program exited normally.
3465 (@value{GDBP}) info inferiors
3466 Id Description Executable
3473 @code{follow-exec-mode} is supported in native mode and
3474 @code{target extended-remote} mode.
3476 You can use the @code{catch} command to make @value{GDBN} stop whenever
3477 a @code{fork}, @code{vfork}, or @code{exec} call is made. @xref{Set
3478 Catchpoints, ,Setting Catchpoints}.
3480 @node Checkpoint/Restart
3481 @section Setting a @emph{Bookmark} to Return to Later
3486 @cindex snapshot of a process
3487 @cindex rewind program state
3489 On certain operating systems@footnote{Currently, only
3490 @sc{gnu}/Linux.}, @value{GDBN} is able to save a @dfn{snapshot} of a
3491 program's state, called a @dfn{checkpoint}, and come back to it
3494 Returning to a checkpoint effectively undoes everything that has
3495 happened in the program since the @code{checkpoint} was saved. This
3496 includes changes in memory, registers, and even (within some limits)
3497 system state. Effectively, it is like going back in time to the
3498 moment when the checkpoint was saved.
3500 Thus, if you're stepping thru a program and you think you're
3501 getting close to the point where things go wrong, you can save
3502 a checkpoint. Then, if you accidentally go too far and miss
3503 the critical statement, instead of having to restart your program
3504 from the beginning, you can just go back to the checkpoint and
3505 start again from there.
3507 This can be especially useful if it takes a lot of time or
3508 steps to reach the point where you think the bug occurs.
3510 To use the @code{checkpoint}/@code{restart} method of debugging:
3515 Save a snapshot of the debugged program's current execution state.
3516 The @code{checkpoint} command takes no arguments, but each checkpoint
3517 is assigned a small integer id, similar to a breakpoint id.
3519 @kindex info checkpoints
3520 @item info checkpoints
3521 List the checkpoints that have been saved in the current debugging
3522 session. For each checkpoint, the following information will be
3529 @item Source line, or label
3532 @kindex restart @var{checkpoint-id}
3533 @item restart @var{checkpoint-id}
3534 Restore the program state that was saved as checkpoint number
3535 @var{checkpoint-id}. All program variables, registers, stack frames
3536 etc.@: will be returned to the values that they had when the checkpoint
3537 was saved. In essence, gdb will ``wind back the clock'' to the point
3538 in time when the checkpoint was saved.
3540 Note that breakpoints, @value{GDBN} variables, command history etc.
3541 are not affected by restoring a checkpoint. In general, a checkpoint
3542 only restores things that reside in the program being debugged, not in
3545 @kindex delete checkpoint @var{checkpoint-id}
3546 @item delete checkpoint @var{checkpoint-id}
3547 Delete the previously-saved checkpoint identified by @var{checkpoint-id}.
3551 Returning to a previously saved checkpoint will restore the user state
3552 of the program being debugged, plus a significant subset of the system
3553 (OS) state, including file pointers. It won't ``un-write'' data from
3554 a file, but it will rewind the file pointer to the previous location,
3555 so that the previously written data can be overwritten. For files
3556 opened in read mode, the pointer will also be restored so that the
3557 previously read data can be read again.
3559 Of course, characters that have been sent to a printer (or other
3560 external device) cannot be ``snatched back'', and characters received
3561 from eg.@: a serial device can be removed from internal program buffers,
3562 but they cannot be ``pushed back'' into the serial pipeline, ready to
3563 be received again. Similarly, the actual contents of files that have
3564 been changed cannot be restored (at this time).
3566 However, within those constraints, you actually can ``rewind'' your
3567 program to a previously saved point in time, and begin debugging it
3568 again --- and you can change the course of events so as to debug a
3569 different execution path this time.
3571 @cindex checkpoints and process id
3572 Finally, there is one bit of internal program state that will be
3573 different when you return to a checkpoint --- the program's process
3574 id. Each checkpoint will have a unique process id (or @var{pid}),
3575 and each will be different from the program's original @var{pid}.
3576 If your program has saved a local copy of its process id, this could
3577 potentially pose a problem.
3579 @subsection A Non-obvious Benefit of Using Checkpoints
3581 On some systems such as @sc{gnu}/Linux, address space randomization
3582 is performed on new processes for security reasons. This makes it
3583 difficult or impossible to set a breakpoint, or watchpoint, on an
3584 absolute address if you have to restart the program, since the
3585 absolute location of a symbol will change from one execution to the
3588 A checkpoint, however, is an @emph{identical} copy of a process.
3589 Therefore if you create a checkpoint at (eg.@:) the start of main,
3590 and simply return to that checkpoint instead of restarting the
3591 process, you can avoid the effects of address randomization and
3592 your symbols will all stay in the same place.
3595 @chapter Stopping and Continuing
3597 The principal purposes of using a debugger are so that you can stop your
3598 program before it terminates; or so that, if your program runs into
3599 trouble, you can investigate and find out why.
3601 Inside @value{GDBN}, your program may stop for any of several reasons,
3602 such as a signal, a breakpoint, or reaching a new line after a
3603 @value{GDBN} command such as @code{step}. You may then examine and
3604 change variables, set new breakpoints or remove old ones, and then
3605 continue execution. Usually, the messages shown by @value{GDBN} provide
3606 ample explanation of the status of your program---but you can also
3607 explicitly request this information at any time.
3610 @kindex info program
3612 Display information about the status of your program: whether it is
3613 running or not, what process it is, and why it stopped.
3617 * Breakpoints:: Breakpoints, watchpoints, and catchpoints
3618 * Continuing and Stepping:: Resuming execution
3619 * Skipping Over Functions and Files::
3620 Skipping over functions and files
3622 * Thread Stops:: Stopping and starting multi-thread programs
3626 @section Breakpoints, Watchpoints, and Catchpoints
3629 A @dfn{breakpoint} makes your program stop whenever a certain point in
3630 the program is reached. For each breakpoint, you can add conditions to
3631 control in finer detail whether your program stops. You can set
3632 breakpoints with the @code{break} command and its variants (@pxref{Set
3633 Breaks, ,Setting Breakpoints}), to specify the place where your program
3634 should stop by line number, function name or exact address in the
3637 On some systems, you can set breakpoints in shared libraries before
3638 the executable is run.
3641 @cindex data breakpoints
3642 @cindex memory tracing
3643 @cindex breakpoint on memory address
3644 @cindex breakpoint on variable modification
3645 A @dfn{watchpoint} is a special breakpoint that stops your program
3646 when the value of an expression changes. The expression may be a value
3647 of a variable, or it could involve values of one or more variables
3648 combined by operators, such as @samp{a + b}. This is sometimes called
3649 @dfn{data breakpoints}. You must use a different command to set
3650 watchpoints (@pxref{Set Watchpoints, ,Setting Watchpoints}), but aside
3651 from that, you can manage a watchpoint like any other breakpoint: you
3652 enable, disable, and delete both breakpoints and watchpoints using the
3655 You can arrange to have values from your program displayed automatically
3656 whenever @value{GDBN} stops at a breakpoint. @xref{Auto Display,,
3660 @cindex breakpoint on events
3661 A @dfn{catchpoint} is another special breakpoint that stops your program
3662 when a certain kind of event occurs, such as the throwing of a C@t{++}
3663 exception or the loading of a library. As with watchpoints, you use a
3664 different command to set a catchpoint (@pxref{Set Catchpoints, ,Setting
3665 Catchpoints}), but aside from that, you can manage a catchpoint like any
3666 other breakpoint. (To stop when your program receives a signal, use the
3667 @code{handle} command; see @ref{Signals, ,Signals}.)
3669 @cindex breakpoint numbers
3670 @cindex numbers for breakpoints
3671 @value{GDBN} assigns a number to each breakpoint, watchpoint, or
3672 catchpoint when you create it; these numbers are successive integers
3673 starting with one. In many of the commands for controlling various
3674 features of breakpoints you use the breakpoint number to say which
3675 breakpoint you want to change. Each breakpoint may be @dfn{enabled} or
3676 @dfn{disabled}; if disabled, it has no effect on your program until you
3679 @cindex breakpoint ranges
3680 @cindex breakpoint lists
3681 @cindex ranges of breakpoints
3682 @cindex lists of breakpoints
3683 Some @value{GDBN} commands accept a space-separated list of breakpoints
3684 on which to operate. A list element can be either a single breakpoint number,
3685 like @samp{5}, or a range of such numbers, like @samp{5-7}.
3686 When a breakpoint list is given to a command, all breakpoints in that list
3690 * Set Breaks:: Setting breakpoints
3691 * Set Watchpoints:: Setting watchpoints
3692 * Set Catchpoints:: Setting catchpoints
3693 * Delete Breaks:: Deleting breakpoints
3694 * Disabling:: Disabling breakpoints
3695 * Conditions:: Break conditions
3696 * Break Commands:: Breakpoint command lists
3697 * Dynamic Printf:: Dynamic printf
3698 * Save Breakpoints:: How to save breakpoints in a file
3699 * Static Probe Points:: Listing static probe points
3700 * Error in Breakpoints:: ``Cannot insert breakpoints''
3701 * Breakpoint-related Warnings:: ``Breakpoint address adjusted...''
3705 @subsection Setting Breakpoints
3707 @c FIXME LMB what does GDB do if no code on line of breakpt?
3708 @c consider in particular declaration with/without initialization.
3710 @c FIXME 2 is there stuff on this already? break at fun start, already init?
3713 @kindex b @r{(@code{break})}
3714 @vindex $bpnum@r{, convenience variable}
3715 @cindex latest breakpoint
3716 Breakpoints are set with the @code{break} command (abbreviated
3717 @code{b}). The debugger convenience variable @samp{$bpnum} records the
3718 number of the breakpoint you've set most recently; see @ref{Convenience
3719 Vars,, Convenience Variables}, for a discussion of what you can do with
3720 convenience variables.
3723 @item break @var{location}
3724 Set a breakpoint at the given @var{location}, which can specify a
3725 function name, a line number, or an address of an instruction.
3726 (@xref{Specify Location}, for a list of all the possible ways to
3727 specify a @var{location}.) The breakpoint will stop your program just
3728 before it executes any of the code in the specified @var{location}.
3730 When using source languages that permit overloading of symbols, such as
3731 C@t{++}, a function name may refer to more than one possible place to break.
3732 @xref{Ambiguous Expressions,,Ambiguous Expressions}, for a discussion of
3735 It is also possible to insert a breakpoint that will stop the program
3736 only if a specific thread (@pxref{Thread-Specific Breakpoints})
3737 or a specific task (@pxref{Ada Tasks}) hits that breakpoint.
3740 When called without any arguments, @code{break} sets a breakpoint at
3741 the next instruction to be executed in the selected stack frame
3742 (@pxref{Stack, ,Examining the Stack}). In any selected frame but the
3743 innermost, this makes your program stop as soon as control
3744 returns to that frame. This is similar to the effect of a
3745 @code{finish} command in the frame inside the selected frame---except
3746 that @code{finish} does not leave an active breakpoint. If you use
3747 @code{break} without an argument in the innermost frame, @value{GDBN} stops
3748 the next time it reaches the current location; this may be useful
3751 @value{GDBN} normally ignores breakpoints when it resumes execution, until at
3752 least one instruction has been executed. If it did not do this, you
3753 would be unable to proceed past a breakpoint without first disabling the
3754 breakpoint. This rule applies whether or not the breakpoint already
3755 existed when your program stopped.
3757 @item break @dots{} if @var{cond}
3758 Set a breakpoint with condition @var{cond}; evaluate the expression
3759 @var{cond} each time the breakpoint is reached, and stop only if the
3760 value is nonzero---that is, if @var{cond} evaluates as true.
3761 @samp{@dots{}} stands for one of the possible arguments described
3762 above (or no argument) specifying where to break. @xref{Conditions,
3763 ,Break Conditions}, for more information on breakpoint conditions.
3766 @item tbreak @var{args}
3767 Set a breakpoint enabled only for one stop. The @var{args} are the
3768 same as for the @code{break} command, and the breakpoint is set in the same
3769 way, but the breakpoint is automatically deleted after the first time your
3770 program stops there. @xref{Disabling, ,Disabling Breakpoints}.
3773 @cindex hardware breakpoints
3774 @item hbreak @var{args}
3775 Set a hardware-assisted breakpoint. The @var{args} are the same as for the
3776 @code{break} command and the breakpoint is set in the same way, but the
3777 breakpoint requires hardware support and some target hardware may not
3778 have this support. The main purpose of this is EPROM/ROM code
3779 debugging, so you can set a breakpoint at an instruction without
3780 changing the instruction. This can be used with the new trap-generation
3781 provided by SPARClite DSU and most x86-based targets. These targets
3782 will generate traps when a program accesses some data or instruction
3783 address that is assigned to the debug registers. However the hardware
3784 breakpoint registers can take a limited number of breakpoints. For
3785 example, on the DSU, only two data breakpoints can be set at a time, and
3786 @value{GDBN} will reject this command if more than two are used. Delete
3787 or disable unused hardware breakpoints before setting new ones
3788 (@pxref{Disabling, ,Disabling Breakpoints}).
3789 @xref{Conditions, ,Break Conditions}.
3790 For remote targets, you can restrict the number of hardware
3791 breakpoints @value{GDBN} will use, see @ref{set remote
3792 hardware-breakpoint-limit}.
3795 @item thbreak @var{args}
3796 Set a hardware-assisted breakpoint enabled only for one stop. The @var{args}
3797 are the same as for the @code{hbreak} command and the breakpoint is set in
3798 the same way. However, like the @code{tbreak} command,
3799 the breakpoint is automatically deleted after the
3800 first time your program stops there. Also, like the @code{hbreak}
3801 command, the breakpoint requires hardware support and some target hardware
3802 may not have this support. @xref{Disabling, ,Disabling Breakpoints}.
3803 See also @ref{Conditions, ,Break Conditions}.
3806 @cindex regular expression
3807 @cindex breakpoints at functions matching a regexp
3808 @cindex set breakpoints in many functions
3809 @item rbreak @var{regex}
3810 Set breakpoints on all functions matching the regular expression
3811 @var{regex}. This command sets an unconditional breakpoint on all
3812 matches, printing a list of all breakpoints it set. Once these
3813 breakpoints are set, they are treated just like the breakpoints set with
3814 the @code{break} command. You can delete them, disable them, or make
3815 them conditional the same way as any other breakpoint.
3817 The syntax of the regular expression is the standard one used with tools
3818 like @file{grep}. Note that this is different from the syntax used by
3819 shells, so for instance @code{foo*} matches all functions that include
3820 an @code{fo} followed by zero or more @code{o}s. There is an implicit
3821 @code{.*} leading and trailing the regular expression you supply, so to
3822 match only functions that begin with @code{foo}, use @code{^foo}.
3824 @cindex non-member C@t{++} functions, set breakpoint in
3825 When debugging C@t{++} programs, @code{rbreak} is useful for setting
3826 breakpoints on overloaded functions that are not members of any special
3829 @cindex set breakpoints on all functions
3830 The @code{rbreak} command can be used to set breakpoints in
3831 @strong{all} the functions in a program, like this:
3834 (@value{GDBP}) rbreak .
3837 @item rbreak @var{file}:@var{regex}
3838 If @code{rbreak} is called with a filename qualification, it limits
3839 the search for functions matching the given regular expression to the
3840 specified @var{file}. This can be used, for example, to set breakpoints on
3841 every function in a given file:
3844 (@value{GDBP}) rbreak file.c:.
3847 The colon separating the filename qualifier from the regex may
3848 optionally be surrounded by spaces.
3850 @kindex info breakpoints
3851 @cindex @code{$_} and @code{info breakpoints}
3852 @item info breakpoints @r{[}@var{list}@dots{}@r{]}
3853 @itemx info break @r{[}@var{list}@dots{}@r{]}
3854 Print a table of all breakpoints, watchpoints, and catchpoints set and
3855 not deleted. Optional argument @var{n} means print information only
3856 about the specified breakpoint(s) (or watchpoint(s) or catchpoint(s)).
3857 For each breakpoint, following columns are printed:
3860 @item Breakpoint Numbers
3862 Breakpoint, watchpoint, or catchpoint.
3864 Whether the breakpoint is marked to be disabled or deleted when hit.
3865 @item Enabled or Disabled
3866 Enabled breakpoints are marked with @samp{y}. @samp{n} marks breakpoints
3867 that are not enabled.
3869 Where the breakpoint is in your program, as a memory address. For a
3870 pending breakpoint whose address is not yet known, this field will
3871 contain @samp{<PENDING>}. Such breakpoint won't fire until a shared
3872 library that has the symbol or line referred by breakpoint is loaded.
3873 See below for details. A breakpoint with several locations will
3874 have @samp{<MULTIPLE>} in this field---see below for details.
3876 Where the breakpoint is in the source for your program, as a file and
3877 line number. For a pending breakpoint, the original string passed to
3878 the breakpoint command will be listed as it cannot be resolved until
3879 the appropriate shared library is loaded in the future.
3883 If a breakpoint is conditional, there are two evaluation modes: ``host'' and
3884 ``target''. If mode is ``host'', breakpoint condition evaluation is done by
3885 @value{GDBN} on the host's side. If it is ``target'', then the condition
3886 is evaluated by the target. The @code{info break} command shows
3887 the condition on the line following the affected breakpoint, together with
3888 its condition evaluation mode in between parentheses.
3890 Breakpoint commands, if any, are listed after that. A pending breakpoint is
3891 allowed to have a condition specified for it. The condition is not parsed for
3892 validity until a shared library is loaded that allows the pending
3893 breakpoint to resolve to a valid location.
3896 @code{info break} with a breakpoint
3897 number @var{n} as argument lists only that breakpoint. The
3898 convenience variable @code{$_} and the default examining-address for
3899 the @code{x} command are set to the address of the last breakpoint
3900 listed (@pxref{Memory, ,Examining Memory}).
3903 @code{info break} displays a count of the number of times the breakpoint
3904 has been hit. This is especially useful in conjunction with the
3905 @code{ignore} command. You can ignore a large number of breakpoint
3906 hits, look at the breakpoint info to see how many times the breakpoint
3907 was hit, and then run again, ignoring one less than that number. This
3908 will get you quickly to the last hit of that breakpoint.
3911 For a breakpoints with an enable count (xref) greater than 1,
3912 @code{info break} also displays that count.
3916 @value{GDBN} allows you to set any number of breakpoints at the same place in
3917 your program. There is nothing silly or meaningless about this. When
3918 the breakpoints are conditional, this is even useful
3919 (@pxref{Conditions, ,Break Conditions}).
3921 @cindex multiple locations, breakpoints
3922 @cindex breakpoints, multiple locations
3923 It is possible that a breakpoint corresponds to several locations
3924 in your program. Examples of this situation are:
3928 Multiple functions in the program may have the same name.
3931 For a C@t{++} constructor, the @value{NGCC} compiler generates several
3932 instances of the function body, used in different cases.
3935 For a C@t{++} template function, a given line in the function can
3936 correspond to any number of instantiations.
3939 For an inlined function, a given source line can correspond to
3940 several places where that function is inlined.
3943 In all those cases, @value{GDBN} will insert a breakpoint at all
3944 the relevant locations.
3946 A breakpoint with multiple locations is displayed in the breakpoint
3947 table using several rows---one header row, followed by one row for
3948 each breakpoint location. The header row has @samp{<MULTIPLE>} in the
3949 address column. The rows for individual locations contain the actual
3950 addresses for locations, and show the functions to which those
3951 locations belong. The number column for a location is of the form
3952 @var{breakpoint-number}.@var{location-number}.
3957 Num Type Disp Enb Address What
3958 1 breakpoint keep y <MULTIPLE>
3960 breakpoint already hit 1 time
3961 1.1 y 0x080486a2 in void foo<int>() at t.cc:8
3962 1.2 y 0x080486ca in void foo<double>() at t.cc:8
3965 You cannot delete the individual locations from a breakpoint. However,
3966 each location can be individually enabled or disabled by passing
3967 @var{breakpoint-number}.@var{location-number} as argument to the
3968 @code{enable} and @code{disable} commands. It's also possible to
3969 @code{enable} and @code{disable} a range of @var{location-number}
3970 locations using a @var{breakpoint-number} and two @var{location-number}s,
3971 in increasing order, separated by a hyphen, like
3972 @kbd{@var{breakpoint-number}.@var{location-number1}-@var{location-number2}},
3973 in which case @value{GDBN} acts on all the locations in the range (inclusive).
3974 Disabling or enabling the parent breakpoint (@pxref{Disabling}) affects
3975 all of the locations that belong to that breakpoint.
3977 @cindex pending breakpoints
3978 It's quite common to have a breakpoint inside a shared library.
3979 Shared libraries can be loaded and unloaded explicitly,
3980 and possibly repeatedly, as the program is executed. To support
3981 this use case, @value{GDBN} updates breakpoint locations whenever
3982 any shared library is loaded or unloaded. Typically, you would
3983 set a breakpoint in a shared library at the beginning of your
3984 debugging session, when the library is not loaded, and when the
3985 symbols from the library are not available. When you try to set
3986 breakpoint, @value{GDBN} will ask you if you want to set
3987 a so called @dfn{pending breakpoint}---breakpoint whose address
3988 is not yet resolved.
3990 After the program is run, whenever a new shared library is loaded,
3991 @value{GDBN} reevaluates all the breakpoints. When a newly loaded
3992 shared library contains the symbol or line referred to by some
3993 pending breakpoint, that breakpoint is resolved and becomes an
3994 ordinary breakpoint. When a library is unloaded, all breakpoints
3995 that refer to its symbols or source lines become pending again.
3997 This logic works for breakpoints with multiple locations, too. For
3998 example, if you have a breakpoint in a C@t{++} template function, and
3999 a newly loaded shared library has an instantiation of that template,
4000 a new location is added to the list of locations for the breakpoint.
4002 Except for having unresolved address, pending breakpoints do not
4003 differ from regular breakpoints. You can set conditions or commands,
4004 enable and disable them and perform other breakpoint operations.
4006 @value{GDBN} provides some additional commands for controlling what
4007 happens when the @samp{break} command cannot resolve breakpoint
4008 address specification to an address:
4010 @kindex set breakpoint pending
4011 @kindex show breakpoint pending
4013 @item set breakpoint pending auto
4014 This is the default behavior. When @value{GDBN} cannot find the breakpoint
4015 location, it queries you whether a pending breakpoint should be created.
4017 @item set breakpoint pending on
4018 This indicates that an unrecognized breakpoint location should automatically
4019 result in a pending breakpoint being created.
4021 @item set breakpoint pending off
4022 This indicates that pending breakpoints are not to be created. Any
4023 unrecognized breakpoint location results in an error. This setting does
4024 not affect any pending breakpoints previously created.
4026 @item show breakpoint pending
4027 Show the current behavior setting for creating pending breakpoints.
4030 The settings above only affect the @code{break} command and its
4031 variants. Once breakpoint is set, it will be automatically updated
4032 as shared libraries are loaded and unloaded.
4034 @cindex automatic hardware breakpoints
4035 For some targets, @value{GDBN} can automatically decide if hardware or
4036 software breakpoints should be used, depending on whether the
4037 breakpoint address is read-only or read-write. This applies to
4038 breakpoints set with the @code{break} command as well as to internal
4039 breakpoints set by commands like @code{next} and @code{finish}. For
4040 breakpoints set with @code{hbreak}, @value{GDBN} will always use hardware
4043 You can control this automatic behaviour with the following commands:
4045 @kindex set breakpoint auto-hw
4046 @kindex show breakpoint auto-hw
4048 @item set breakpoint auto-hw on
4049 This is the default behavior. When @value{GDBN} sets a breakpoint, it
4050 will try to use the target memory map to decide if software or hardware
4051 breakpoint must be used.
4053 @item set breakpoint auto-hw off
4054 This indicates @value{GDBN} should not automatically select breakpoint
4055 type. If the target provides a memory map, @value{GDBN} will warn when
4056 trying to set software breakpoint at a read-only address.
4059 @value{GDBN} normally implements breakpoints by replacing the program code
4060 at the breakpoint address with a special instruction, which, when
4061 executed, given control to the debugger. By default, the program
4062 code is so modified only when the program is resumed. As soon as
4063 the program stops, @value{GDBN} restores the original instructions. This
4064 behaviour guards against leaving breakpoints inserted in the
4065 target should gdb abrubptly disconnect. However, with slow remote
4066 targets, inserting and removing breakpoint can reduce the performance.
4067 This behavior can be controlled with the following commands::
4069 @kindex set breakpoint always-inserted
4070 @kindex show breakpoint always-inserted
4072 @item set breakpoint always-inserted off
4073 All breakpoints, including newly added by the user, are inserted in
4074 the target only when the target is resumed. All breakpoints are
4075 removed from the target when it stops. This is the default mode.
4077 @item set breakpoint always-inserted on
4078 Causes all breakpoints to be inserted in the target at all times. If
4079 the user adds a new breakpoint, or changes an existing breakpoint, the
4080 breakpoints in the target are updated immediately. A breakpoint is
4081 removed from the target only when breakpoint itself is deleted.
4084 @value{GDBN} handles conditional breakpoints by evaluating these conditions
4085 when a breakpoint breaks. If the condition is true, then the process being
4086 debugged stops, otherwise the process is resumed.
4088 If the target supports evaluating conditions on its end, @value{GDBN} may
4089 download the breakpoint, together with its conditions, to it.
4091 This feature can be controlled via the following commands:
4093 @kindex set breakpoint condition-evaluation
4094 @kindex show breakpoint condition-evaluation
4096 @item set breakpoint condition-evaluation host
4097 This option commands @value{GDBN} to evaluate the breakpoint
4098 conditions on the host's side. Unconditional breakpoints are sent to
4099 the target which in turn receives the triggers and reports them back to GDB
4100 for condition evaluation. This is the standard evaluation mode.
4102 @item set breakpoint condition-evaluation target
4103 This option commands @value{GDBN} to download breakpoint conditions
4104 to the target at the moment of their insertion. The target
4105 is responsible for evaluating the conditional expression and reporting
4106 breakpoint stop events back to @value{GDBN} whenever the condition
4107 is true. Due to limitations of target-side evaluation, some conditions
4108 cannot be evaluated there, e.g., conditions that depend on local data
4109 that is only known to the host. Examples include
4110 conditional expressions involving convenience variables, complex types
4111 that cannot be handled by the agent expression parser and expressions
4112 that are too long to be sent over to the target, specially when the
4113 target is a remote system. In these cases, the conditions will be
4114 evaluated by @value{GDBN}.
4116 @item set breakpoint condition-evaluation auto
4117 This is the default mode. If the target supports evaluating breakpoint
4118 conditions on its end, @value{GDBN} will download breakpoint conditions to
4119 the target (limitations mentioned previously apply). If the target does
4120 not support breakpoint condition evaluation, then @value{GDBN} will fallback
4121 to evaluating all these conditions on the host's side.
4125 @cindex negative breakpoint numbers
4126 @cindex internal @value{GDBN} breakpoints
4127 @value{GDBN} itself sometimes sets breakpoints in your program for
4128 special purposes, such as proper handling of @code{longjmp} (in C
4129 programs). These internal breakpoints are assigned negative numbers,
4130 starting with @code{-1}; @samp{info breakpoints} does not display them.
4131 You can see these breakpoints with the @value{GDBN} maintenance command
4132 @samp{maint info breakpoints} (@pxref{maint info breakpoints}).
4135 @node Set Watchpoints
4136 @subsection Setting Watchpoints
4138 @cindex setting watchpoints
4139 You can use a watchpoint to stop execution whenever the value of an
4140 expression changes, without having to predict a particular place where
4141 this may happen. (This is sometimes called a @dfn{data breakpoint}.)
4142 The expression may be as simple as the value of a single variable, or
4143 as complex as many variables combined by operators. Examples include:
4147 A reference to the value of a single variable.
4150 An address cast to an appropriate data type. For example,
4151 @samp{*(int *)0x12345678} will watch a 4-byte region at the specified
4152 address (assuming an @code{int} occupies 4 bytes).
4155 An arbitrarily complex expression, such as @samp{a*b + c/d}. The
4156 expression can use any operators valid in the program's native
4157 language (@pxref{Languages}).
4160 You can set a watchpoint on an expression even if the expression can
4161 not be evaluated yet. For instance, you can set a watchpoint on
4162 @samp{*global_ptr} before @samp{global_ptr} is initialized.
4163 @value{GDBN} will stop when your program sets @samp{global_ptr} and
4164 the expression produces a valid value. If the expression becomes
4165 valid in some other way than changing a variable (e.g.@: if the memory
4166 pointed to by @samp{*global_ptr} becomes readable as the result of a
4167 @code{malloc} call), @value{GDBN} may not stop until the next time
4168 the expression changes.
4170 @cindex software watchpoints
4171 @cindex hardware watchpoints
4172 Depending on your system, watchpoints may be implemented in software or
4173 hardware. @value{GDBN} does software watchpointing by single-stepping your
4174 program and testing the variable's value each time, which is hundreds of
4175 times slower than normal execution. (But this may still be worth it, to
4176 catch errors where you have no clue what part of your program is the
4179 On some systems, such as most PowerPC or x86-based targets,
4180 @value{GDBN} includes support for hardware watchpoints, which do not
4181 slow down the running of your program.
4185 @item watch @r{[}-l@r{|}-location@r{]} @var{expr} @r{[}thread @var{thread-id}@r{]} @r{[}mask @var{maskvalue}@r{]}
4186 Set a watchpoint for an expression. @value{GDBN} will break when the
4187 expression @var{expr} is written into by the program and its value
4188 changes. The simplest (and the most popular) use of this command is
4189 to watch the value of a single variable:
4192 (@value{GDBP}) watch foo
4195 If the command includes a @code{@r{[}thread @var{thread-id}@r{]}}
4196 argument, @value{GDBN} breaks only when the thread identified by
4197 @var{thread-id} changes the value of @var{expr}. If any other threads
4198 change the value of @var{expr}, @value{GDBN} will not break. Note
4199 that watchpoints restricted to a single thread in this way only work
4200 with Hardware Watchpoints.
4202 Ordinarily a watchpoint respects the scope of variables in @var{expr}
4203 (see below). The @code{-location} argument tells @value{GDBN} to
4204 instead watch the memory referred to by @var{expr}. In this case,
4205 @value{GDBN} will evaluate @var{expr}, take the address of the result,
4206 and watch the memory at that address. The type of the result is used
4207 to determine the size of the watched memory. If the expression's
4208 result does not have an address, then @value{GDBN} will print an
4211 The @code{@r{[}mask @var{maskvalue}@r{]}} argument allows creation
4212 of masked watchpoints, if the current architecture supports this
4213 feature (e.g., PowerPC Embedded architecture, see @ref{PowerPC
4214 Embedded}.) A @dfn{masked watchpoint} specifies a mask in addition
4215 to an address to watch. The mask specifies that some bits of an address
4216 (the bits which are reset in the mask) should be ignored when matching
4217 the address accessed by the inferior against the watchpoint address.
4218 Thus, a masked watchpoint watches many addresses simultaneously---those
4219 addresses whose unmasked bits are identical to the unmasked bits in the
4220 watchpoint address. The @code{mask} argument implies @code{-location}.
4224 (@value{GDBP}) watch foo mask 0xffff00ff
4225 (@value{GDBP}) watch *0xdeadbeef mask 0xffffff00
4229 @item rwatch @r{[}-l@r{|}-location@r{]} @var{expr} @r{[}thread @var{thread-id}@r{]} @r{[}mask @var{maskvalue}@r{]}
4230 Set a watchpoint that will break when the value of @var{expr} is read
4234 @item awatch @r{[}-l@r{|}-location@r{]} @var{expr} @r{[}thread @var{thread-id}@r{]} @r{[}mask @var{maskvalue}@r{]}
4235 Set a watchpoint that will break when @var{expr} is either read from
4236 or written into by the program.
4238 @kindex info watchpoints @r{[}@var{list}@dots{}@r{]}
4239 @item info watchpoints @r{[}@var{list}@dots{}@r{]}
4240 This command prints a list of watchpoints, using the same format as
4241 @code{info break} (@pxref{Set Breaks}).
4244 If you watch for a change in a numerically entered address you need to
4245 dereference it, as the address itself is just a constant number which will
4246 never change. @value{GDBN} refuses to create a watchpoint that watches
4247 a never-changing value:
4250 (@value{GDBP}) watch 0x600850
4251 Cannot watch constant value 0x600850.
4252 (@value{GDBP}) watch *(int *) 0x600850
4253 Watchpoint 1: *(int *) 6293584
4256 @value{GDBN} sets a @dfn{hardware watchpoint} if possible. Hardware
4257 watchpoints execute very quickly, and the debugger reports a change in
4258 value at the exact instruction where the change occurs. If @value{GDBN}
4259 cannot set a hardware watchpoint, it sets a software watchpoint, which
4260 executes more slowly and reports the change in value at the next
4261 @emph{statement}, not the instruction, after the change occurs.
4263 @cindex use only software watchpoints
4264 You can force @value{GDBN} to use only software watchpoints with the
4265 @kbd{set can-use-hw-watchpoints 0} command. With this variable set to
4266 zero, @value{GDBN} will never try to use hardware watchpoints, even if
4267 the underlying system supports them. (Note that hardware-assisted
4268 watchpoints that were set @emph{before} setting
4269 @code{can-use-hw-watchpoints} to zero will still use the hardware
4270 mechanism of watching expression values.)
4273 @item set can-use-hw-watchpoints
4274 @kindex set can-use-hw-watchpoints
4275 Set whether or not to use hardware watchpoints.
4277 @item show can-use-hw-watchpoints
4278 @kindex show can-use-hw-watchpoints
4279 Show the current mode of using hardware watchpoints.
4282 For remote targets, you can restrict the number of hardware
4283 watchpoints @value{GDBN} will use, see @ref{set remote
4284 hardware-breakpoint-limit}.
4286 When you issue the @code{watch} command, @value{GDBN} reports
4289 Hardware watchpoint @var{num}: @var{expr}
4293 if it was able to set a hardware watchpoint.
4295 Currently, the @code{awatch} and @code{rwatch} commands can only set
4296 hardware watchpoints, because accesses to data that don't change the
4297 value of the watched expression cannot be detected without examining
4298 every instruction as it is being executed, and @value{GDBN} does not do
4299 that currently. If @value{GDBN} finds that it is unable to set a
4300 hardware breakpoint with the @code{awatch} or @code{rwatch} command, it
4301 will print a message like this:
4304 Expression cannot be implemented with read/access watchpoint.
4307 Sometimes, @value{GDBN} cannot set a hardware watchpoint because the
4308 data type of the watched expression is wider than what a hardware
4309 watchpoint on the target machine can handle. For example, some systems
4310 can only watch regions that are up to 4 bytes wide; on such systems you
4311 cannot set hardware watchpoints for an expression that yields a
4312 double-precision floating-point number (which is typically 8 bytes
4313 wide). As a work-around, it might be possible to break the large region
4314 into a series of smaller ones and watch them with separate watchpoints.
4316 If you set too many hardware watchpoints, @value{GDBN} might be unable
4317 to insert all of them when you resume the execution of your program.
4318 Since the precise number of active watchpoints is unknown until such
4319 time as the program is about to be resumed, @value{GDBN} might not be
4320 able to warn you about this when you set the watchpoints, and the
4321 warning will be printed only when the program is resumed:
4324 Hardware watchpoint @var{num}: Could not insert watchpoint
4328 If this happens, delete or disable some of the watchpoints.
4330 Watching complex expressions that reference many variables can also
4331 exhaust the resources available for hardware-assisted watchpoints.
4332 That's because @value{GDBN} needs to watch every variable in the
4333 expression with separately allocated resources.
4335 If you call a function interactively using @code{print} or @code{call},
4336 any watchpoints you have set will be inactive until @value{GDBN} reaches another
4337 kind of breakpoint or the call completes.
4339 @value{GDBN} automatically deletes watchpoints that watch local
4340 (automatic) variables, or expressions that involve such variables, when
4341 they go out of scope, that is, when the execution leaves the block in
4342 which these variables were defined. In particular, when the program
4343 being debugged terminates, @emph{all} local variables go out of scope,
4344 and so only watchpoints that watch global variables remain set. If you
4345 rerun the program, you will need to set all such watchpoints again. One
4346 way of doing that would be to set a code breakpoint at the entry to the
4347 @code{main} function and when it breaks, set all the watchpoints.
4349 @cindex watchpoints and threads
4350 @cindex threads and watchpoints
4351 In multi-threaded programs, watchpoints will detect changes to the
4352 watched expression from every thread.
4355 @emph{Warning:} In multi-threaded programs, software watchpoints
4356 have only limited usefulness. If @value{GDBN} creates a software
4357 watchpoint, it can only watch the value of an expression @emph{in a
4358 single thread}. If you are confident that the expression can only
4359 change due to the current thread's activity (and if you are also
4360 confident that no other thread can become current), then you can use
4361 software watchpoints as usual. However, @value{GDBN} may not notice
4362 when a non-current thread's activity changes the expression. (Hardware
4363 watchpoints, in contrast, watch an expression in all threads.)
4366 @xref{set remote hardware-watchpoint-limit}.
4368 @node Set Catchpoints
4369 @subsection Setting Catchpoints
4370 @cindex catchpoints, setting
4371 @cindex exception handlers
4372 @cindex event handling
4374 You can use @dfn{catchpoints} to cause the debugger to stop for certain
4375 kinds of program events, such as C@t{++} exceptions or the loading of a
4376 shared library. Use the @code{catch} command to set a catchpoint.
4380 @item catch @var{event}
4381 Stop when @var{event} occurs. The @var{event} can be any of the following:
4384 @item throw @r{[}@var{regexp}@r{]}
4385 @itemx rethrow @r{[}@var{regexp}@r{]}
4386 @itemx catch @r{[}@var{regexp}@r{]}
4388 @kindex catch rethrow
4390 @cindex stop on C@t{++} exceptions
4391 The throwing, re-throwing, or catching of a C@t{++} exception.
4393 If @var{regexp} is given, then only exceptions whose type matches the
4394 regular expression will be caught.
4396 @vindex $_exception@r{, convenience variable}
4397 The convenience variable @code{$_exception} is available at an
4398 exception-related catchpoint, on some systems. This holds the
4399 exception being thrown.
4401 There are currently some limitations to C@t{++} exception handling in
4406 The support for these commands is system-dependent. Currently, only
4407 systems using the @samp{gnu-v3} C@t{++} ABI (@pxref{ABI}) are
4411 The regular expression feature and the @code{$_exception} convenience
4412 variable rely on the presence of some SDT probes in @code{libstdc++}.
4413 If these probes are not present, then these features cannot be used.
4414 These probes were first available in the GCC 4.8 release, but whether
4415 or not they are available in your GCC also depends on how it was
4419 The @code{$_exception} convenience variable is only valid at the
4420 instruction at which an exception-related catchpoint is set.
4423 When an exception-related catchpoint is hit, @value{GDBN} stops at a
4424 location in the system library which implements runtime exception
4425 support for C@t{++}, usually @code{libstdc++}. You can use @code{up}
4426 (@pxref{Selection}) to get to your code.
4429 If you call a function interactively, @value{GDBN} normally returns
4430 control to you when the function has finished executing. If the call
4431 raises an exception, however, the call may bypass the mechanism that
4432 returns control to you and cause your program either to abort or to
4433 simply continue running until it hits a breakpoint, catches a signal
4434 that @value{GDBN} is listening for, or exits. This is the case even if
4435 you set a catchpoint for the exception; catchpoints on exceptions are
4436 disabled within interactive calls. @xref{Calling}, for information on
4437 controlling this with @code{set unwind-on-terminating-exception}.
4440 You cannot raise an exception interactively.
4443 You cannot install an exception handler interactively.
4447 @kindex catch exception
4448 @cindex Ada exception catching
4449 @cindex catch Ada exceptions
4450 An Ada exception being raised. If an exception name is specified
4451 at the end of the command (eg @code{catch exception Program_Error}),
4452 the debugger will stop only when this specific exception is raised.
4453 Otherwise, the debugger stops execution when any Ada exception is raised.
4455 When inserting an exception catchpoint on a user-defined exception whose
4456 name is identical to one of the exceptions defined by the language, the
4457 fully qualified name must be used as the exception name. Otherwise,
4458 @value{GDBN} will assume that it should stop on the pre-defined exception
4459 rather than the user-defined one. For instance, assuming an exception
4460 called @code{Constraint_Error} is defined in package @code{Pck}, then
4461 the command to use to catch such exceptions is @kbd{catch exception
4462 Pck.Constraint_Error}.
4465 @kindex catch handlers
4466 @cindex Ada exception handlers catching
4467 @cindex catch Ada exceptions when handled
4468 An Ada exception being handled. If an exception name is
4469 specified at the end of the command
4470 (eg @kbd{catch handlers Program_Error}), the debugger will stop
4471 only when this specific exception is handled.
4472 Otherwise, the debugger stops execution when any Ada exception is handled.
4474 When inserting a handlers catchpoint on a user-defined
4475 exception whose name is identical to one of the exceptions
4476 defined by the language, the fully qualified name must be used
4477 as the exception name. Otherwise, @value{GDBN} will assume that it
4478 should stop on the pre-defined exception rather than the
4479 user-defined one. For instance, assuming an exception called
4480 @code{Constraint_Error} is defined in package @code{Pck}, then the
4481 command to use to catch such exceptions handling is
4482 @kbd{catch handlers Pck.Constraint_Error}.
4484 @item exception unhandled
4485 @kindex catch exception unhandled
4486 An exception that was raised but is not handled by the program.
4489 @kindex catch assert
4490 A failed Ada assertion.
4494 @cindex break on fork/exec
4495 A call to @code{exec}.
4498 @itemx syscall @r{[}@var{name} @r{|} @var{number} @r{|} @r{group:}@var{groupname} @r{|} @r{g:}@var{groupname}@r{]} @dots{}
4499 @kindex catch syscall
4500 @cindex break on a system call.
4501 A call to or return from a system call, a.k.a.@: @dfn{syscall}. A
4502 syscall is a mechanism for application programs to request a service
4503 from the operating system (OS) or one of the OS system services.
4504 @value{GDBN} can catch some or all of the syscalls issued by the
4505 debuggee, and show the related information for each syscall. If no
4506 argument is specified, calls to and returns from all system calls
4509 @var{name} can be any system call name that is valid for the
4510 underlying OS. Just what syscalls are valid depends on the OS. On
4511 GNU and Unix systems, you can find the full list of valid syscall
4512 names on @file{/usr/include/asm/unistd.h}.
4514 @c For MS-Windows, the syscall names and the corresponding numbers
4515 @c can be found, e.g., on this URL:
4516 @c http://www.metasploit.com/users/opcode/syscalls.html
4517 @c but we don't support Windows syscalls yet.
4519 Normally, @value{GDBN} knows in advance which syscalls are valid for
4520 each OS, so you can use the @value{GDBN} command-line completion
4521 facilities (@pxref{Completion,, command completion}) to list the
4524 You may also specify the system call numerically. A syscall's
4525 number is the value passed to the OS's syscall dispatcher to
4526 identify the requested service. When you specify the syscall by its
4527 name, @value{GDBN} uses its database of syscalls to convert the name
4528 into the corresponding numeric code, but using the number directly
4529 may be useful if @value{GDBN}'s database does not have the complete
4530 list of syscalls on your system (e.g., because @value{GDBN} lags
4531 behind the OS upgrades).
4533 You may specify a group of related syscalls to be caught at once using
4534 the @code{group:} syntax (@code{g:} is a shorter equivalent). For
4535 instance, on some platforms @value{GDBN} allows you to catch all
4536 network related syscalls, by passing the argument @code{group:network}
4537 to @code{catch syscall}. Note that not all syscall groups are
4538 available in every system. You can use the command completion
4539 facilities (@pxref{Completion,, command completion}) to list the
4540 syscall groups available on your environment.
4542 The example below illustrates how this command works if you don't provide
4546 (@value{GDBP}) catch syscall
4547 Catchpoint 1 (syscall)
4549 Starting program: /tmp/catch-syscall
4551 Catchpoint 1 (call to syscall 'close'), \
4552 0xffffe424 in __kernel_vsyscall ()
4556 Catchpoint 1 (returned from syscall 'close'), \
4557 0xffffe424 in __kernel_vsyscall ()
4561 Here is an example of catching a system call by name:
4564 (@value{GDBP}) catch syscall chroot
4565 Catchpoint 1 (syscall 'chroot' [61])
4567 Starting program: /tmp/catch-syscall
4569 Catchpoint 1 (call to syscall 'chroot'), \
4570 0xffffe424 in __kernel_vsyscall ()
4574 Catchpoint 1 (returned from syscall 'chroot'), \
4575 0xffffe424 in __kernel_vsyscall ()
4579 An example of specifying a system call numerically. In the case
4580 below, the syscall number has a corresponding entry in the XML
4581 file, so @value{GDBN} finds its name and prints it:
4584 (@value{GDBP}) catch syscall 252
4585 Catchpoint 1 (syscall(s) 'exit_group')
4587 Starting program: /tmp/catch-syscall
4589 Catchpoint 1 (call to syscall 'exit_group'), \
4590 0xffffe424 in __kernel_vsyscall ()
4594 Program exited normally.
4598 Here is an example of catching a syscall group:
4601 (@value{GDBP}) catch syscall group:process
4602 Catchpoint 1 (syscalls 'exit' [1] 'fork' [2] 'waitpid' [7]
4603 'execve' [11] 'wait4' [114] 'clone' [120] 'vfork' [190]
4604 'exit_group' [252] 'waitid' [284] 'unshare' [310])
4606 Starting program: /tmp/catch-syscall
4608 Catchpoint 1 (call to syscall fork), 0x00007ffff7df4e27 in open64 ()
4609 from /lib64/ld-linux-x86-64.so.2
4615 However, there can be situations when there is no corresponding name
4616 in XML file for that syscall number. In this case, @value{GDBN} prints
4617 a warning message saying that it was not able to find the syscall name,
4618 but the catchpoint will be set anyway. See the example below:
4621 (@value{GDBP}) catch syscall 764
4622 warning: The number '764' does not represent a known syscall.
4623 Catchpoint 2 (syscall 764)
4627 If you configure @value{GDBN} using the @samp{--without-expat} option,
4628 it will not be able to display syscall names. Also, if your
4629 architecture does not have an XML file describing its system calls,
4630 you will not be able to see the syscall names. It is important to
4631 notice that these two features are used for accessing the syscall
4632 name database. In either case, you will see a warning like this:
4635 (@value{GDBP}) catch syscall
4636 warning: Could not open "syscalls/i386-linux.xml"
4637 warning: Could not load the syscall XML file 'syscalls/i386-linux.xml'.
4638 GDB will not be able to display syscall names.
4639 Catchpoint 1 (syscall)
4643 Of course, the file name will change depending on your architecture and system.
4645 Still using the example above, you can also try to catch a syscall by its
4646 number. In this case, you would see something like:
4649 (@value{GDBP}) catch syscall 252
4650 Catchpoint 1 (syscall(s) 252)
4653 Again, in this case @value{GDBN} would not be able to display syscall's names.
4657 A call to @code{fork}.
4661 A call to @code{vfork}.
4663 @item load @r{[}regexp@r{]}
4664 @itemx unload @r{[}regexp@r{]}
4666 @kindex catch unload
4667 The loading or unloading of a shared library. If @var{regexp} is
4668 given, then the catchpoint will stop only if the regular expression
4669 matches one of the affected libraries.
4671 @item signal @r{[}@var{signal}@dots{} @r{|} @samp{all}@r{]}
4672 @kindex catch signal
4673 The delivery of a signal.
4675 With no arguments, this catchpoint will catch any signal that is not
4676 used internally by @value{GDBN}, specifically, all signals except
4677 @samp{SIGTRAP} and @samp{SIGINT}.
4679 With the argument @samp{all}, all signals, including those used by
4680 @value{GDBN}, will be caught. This argument cannot be used with other
4683 Otherwise, the arguments are a list of signal names as given to
4684 @code{handle} (@pxref{Signals}). Only signals specified in this list
4687 One reason that @code{catch signal} can be more useful than
4688 @code{handle} is that you can attach commands and conditions to the
4691 When a signal is caught by a catchpoint, the signal's @code{stop} and
4692 @code{print} settings, as specified by @code{handle}, are ignored.
4693 However, whether the signal is still delivered to the inferior depends
4694 on the @code{pass} setting; this can be changed in the catchpoint's
4699 @item tcatch @var{event}
4701 Set a catchpoint that is enabled only for one stop. The catchpoint is
4702 automatically deleted after the first time the event is caught.
4706 Use the @code{info break} command to list the current catchpoints.
4710 @subsection Deleting Breakpoints
4712 @cindex clearing breakpoints, watchpoints, catchpoints
4713 @cindex deleting breakpoints, watchpoints, catchpoints
4714 It is often necessary to eliminate a breakpoint, watchpoint, or
4715 catchpoint once it has done its job and you no longer want your program
4716 to stop there. This is called @dfn{deleting} the breakpoint. A
4717 breakpoint that has been deleted no longer exists; it is forgotten.
4719 With the @code{clear} command you can delete breakpoints according to
4720 where they are in your program. With the @code{delete} command you can
4721 delete individual breakpoints, watchpoints, or catchpoints by specifying
4722 their breakpoint numbers.
4724 It is not necessary to delete a breakpoint to proceed past it. @value{GDBN}
4725 automatically ignores breakpoints on the first instruction to be executed
4726 when you continue execution without changing the execution address.
4731 Delete any breakpoints at the next instruction to be executed in the
4732 selected stack frame (@pxref{Selection, ,Selecting a Frame}). When
4733 the innermost frame is selected, this is a good way to delete a
4734 breakpoint where your program just stopped.
4736 @item clear @var{location}
4737 Delete any breakpoints set at the specified @var{location}.
4738 @xref{Specify Location}, for the various forms of @var{location}; the
4739 most useful ones are listed below:
4742 @item clear @var{function}
4743 @itemx clear @var{filename}:@var{function}
4744 Delete any breakpoints set at entry to the named @var{function}.
4746 @item clear @var{linenum}
4747 @itemx clear @var{filename}:@var{linenum}
4748 Delete any breakpoints set at or within the code of the specified
4749 @var{linenum} of the specified @var{filename}.
4752 @cindex delete breakpoints
4754 @kindex d @r{(@code{delete})}
4755 @item delete @r{[}breakpoints@r{]} @r{[}@var{list}@dots{}@r{]}
4756 Delete the breakpoints, watchpoints, or catchpoints of the breakpoint
4757 list specified as argument. If no argument is specified, delete all
4758 breakpoints (@value{GDBN} asks confirmation, unless you have @code{set
4759 confirm off}). You can abbreviate this command as @code{d}.
4763 @subsection Disabling Breakpoints
4765 @cindex enable/disable a breakpoint
4766 Rather than deleting a breakpoint, watchpoint, or catchpoint, you might
4767 prefer to @dfn{disable} it. This makes the breakpoint inoperative as if
4768 it had been deleted, but remembers the information on the breakpoint so
4769 that you can @dfn{enable} it again later.
4771 You disable and enable breakpoints, watchpoints, and catchpoints with
4772 the @code{enable} and @code{disable} commands, optionally specifying
4773 one or more breakpoint numbers as arguments. Use @code{info break} to
4774 print a list of all breakpoints, watchpoints, and catchpoints if you
4775 do not know which numbers to use.
4777 Disabling and enabling a breakpoint that has multiple locations
4778 affects all of its locations.
4780 A breakpoint, watchpoint, or catchpoint can have any of several
4781 different states of enablement:
4785 Enabled. The breakpoint stops your program. A breakpoint set
4786 with the @code{break} command starts out in this state.
4788 Disabled. The breakpoint has no effect on your program.
4790 Enabled once. The breakpoint stops your program, but then becomes
4793 Enabled for a count. The breakpoint stops your program for the next
4794 N times, then becomes disabled.
4796 Enabled for deletion. The breakpoint stops your program, but
4797 immediately after it does so it is deleted permanently. A breakpoint
4798 set with the @code{tbreak} command starts out in this state.
4801 You can use the following commands to enable or disable breakpoints,
4802 watchpoints, and catchpoints:
4806 @kindex dis @r{(@code{disable})}
4807 @item disable @r{[}breakpoints@r{]} @r{[}@var{list}@dots{}@r{]}
4808 Disable the specified breakpoints---or all breakpoints, if none are
4809 listed. A disabled breakpoint has no effect but is not forgotten. All
4810 options such as ignore-counts, conditions and commands are remembered in
4811 case the breakpoint is enabled again later. You may abbreviate
4812 @code{disable} as @code{dis}.
4815 @item enable @r{[}breakpoints@r{]} @r{[}@var{list}@dots{}@r{]}
4816 Enable the specified breakpoints (or all defined breakpoints). They
4817 become effective once again in stopping your program.
4819 @item enable @r{[}breakpoints@r{]} once @var{list}@dots{}
4820 Enable the specified breakpoints temporarily. @value{GDBN} disables any
4821 of these breakpoints immediately after stopping your program.
4823 @item enable @r{[}breakpoints@r{]} count @var{count} @var{list}@dots{}
4824 Enable the specified breakpoints temporarily. @value{GDBN} records
4825 @var{count} with each of the specified breakpoints, and decrements a
4826 breakpoint's count when it is hit. When any count reaches 0,
4827 @value{GDBN} disables that breakpoint. If a breakpoint has an ignore
4828 count (@pxref{Conditions, ,Break Conditions}), that will be
4829 decremented to 0 before @var{count} is affected.
4831 @item enable @r{[}breakpoints@r{]} delete @var{list}@dots{}
4832 Enable the specified breakpoints to work once, then die. @value{GDBN}
4833 deletes any of these breakpoints as soon as your program stops there.
4834 Breakpoints set by the @code{tbreak} command start out in this state.
4837 @c FIXME: I think the following ``Except for [...] @code{tbreak}'' is
4838 @c confusing: tbreak is also initially enabled.
4839 Except for a breakpoint set with @code{tbreak} (@pxref{Set Breaks,
4840 ,Setting Breakpoints}), breakpoints that you set are initially enabled;
4841 subsequently, they become disabled or enabled only when you use one of
4842 the commands above. (The command @code{until} can set and delete a
4843 breakpoint of its own, but it does not change the state of your other
4844 breakpoints; see @ref{Continuing and Stepping, ,Continuing and
4848 @subsection Break Conditions
4849 @cindex conditional breakpoints
4850 @cindex breakpoint conditions
4852 @c FIXME what is scope of break condition expr? Context where wanted?
4853 @c in particular for a watchpoint?
4854 The simplest sort of breakpoint breaks every time your program reaches a
4855 specified place. You can also specify a @dfn{condition} for a
4856 breakpoint. A condition is just a Boolean expression in your
4857 programming language (@pxref{Expressions, ,Expressions}). A breakpoint with
4858 a condition evaluates the expression each time your program reaches it,
4859 and your program stops only if the condition is @emph{true}.
4861 This is the converse of using assertions for program validation; in that
4862 situation, you want to stop when the assertion is violated---that is,
4863 when the condition is false. In C, if you want to test an assertion expressed
4864 by the condition @var{assert}, you should set the condition
4865 @samp{! @var{assert}} on the appropriate breakpoint.
4867 Conditions are also accepted for watchpoints; you may not need them,
4868 since a watchpoint is inspecting the value of an expression anyhow---but
4869 it might be simpler, say, to just set a watchpoint on a variable name,
4870 and specify a condition that tests whether the new value is an interesting
4873 Break conditions can have side effects, and may even call functions in
4874 your program. This can be useful, for example, to activate functions
4875 that log program progress, or to use your own print functions to
4876 format special data structures. The effects are completely predictable
4877 unless there is another enabled breakpoint at the same address. (In
4878 that case, @value{GDBN} might see the other breakpoint first and stop your
4879 program without checking the condition of this one.) Note that
4880 breakpoint commands are usually more convenient and flexible than break
4882 purpose of performing side effects when a breakpoint is reached
4883 (@pxref{Break Commands, ,Breakpoint Command Lists}).
4885 Breakpoint conditions can also be evaluated on the target's side if
4886 the target supports it. Instead of evaluating the conditions locally,
4887 @value{GDBN} encodes the expression into an agent expression
4888 (@pxref{Agent Expressions}) suitable for execution on the target,
4889 independently of @value{GDBN}. Global variables become raw memory
4890 locations, locals become stack accesses, and so forth.
4892 In this case, @value{GDBN} will only be notified of a breakpoint trigger
4893 when its condition evaluates to true. This mechanism may provide faster
4894 response times depending on the performance characteristics of the target
4895 since it does not need to keep @value{GDBN} informed about
4896 every breakpoint trigger, even those with false conditions.
4898 Break conditions can be specified when a breakpoint is set, by using
4899 @samp{if} in the arguments to the @code{break} command. @xref{Set
4900 Breaks, ,Setting Breakpoints}. They can also be changed at any time
4901 with the @code{condition} command.
4903 You can also use the @code{if} keyword with the @code{watch} command.
4904 The @code{catch} command does not recognize the @code{if} keyword;
4905 @code{condition} is the only way to impose a further condition on a
4910 @item condition @var{bnum} @var{expression}
4911 Specify @var{expression} as the break condition for breakpoint,
4912 watchpoint, or catchpoint number @var{bnum}. After you set a condition,
4913 breakpoint @var{bnum} stops your program only if the value of
4914 @var{expression} is true (nonzero, in C). When you use
4915 @code{condition}, @value{GDBN} checks @var{expression} immediately for
4916 syntactic correctness, and to determine whether symbols in it have
4917 referents in the context of your breakpoint. If @var{expression} uses
4918 symbols not referenced in the context of the breakpoint, @value{GDBN}
4919 prints an error message:
4922 No symbol "foo" in current context.
4927 not actually evaluate @var{expression} at the time the @code{condition}
4928 command (or a command that sets a breakpoint with a condition, like
4929 @code{break if @dots{}}) is given, however. @xref{Expressions, ,Expressions}.
4931 @item condition @var{bnum}
4932 Remove the condition from breakpoint number @var{bnum}. It becomes
4933 an ordinary unconditional breakpoint.
4936 @cindex ignore count (of breakpoint)
4937 A special case of a breakpoint condition is to stop only when the
4938 breakpoint has been reached a certain number of times. This is so
4939 useful that there is a special way to do it, using the @dfn{ignore
4940 count} of the breakpoint. Every breakpoint has an ignore count, which
4941 is an integer. Most of the time, the ignore count is zero, and
4942 therefore has no effect. But if your program reaches a breakpoint whose
4943 ignore count is positive, then instead of stopping, it just decrements
4944 the ignore count by one and continues. As a result, if the ignore count
4945 value is @var{n}, the breakpoint does not stop the next @var{n} times
4946 your program reaches it.
4950 @item ignore @var{bnum} @var{count}
4951 Set the ignore count of breakpoint number @var{bnum} to @var{count}.
4952 The next @var{count} times the breakpoint is reached, your program's
4953 execution does not stop; other than to decrement the ignore count, @value{GDBN}
4956 To make the breakpoint stop the next time it is reached, specify
4959 When you use @code{continue} to resume execution of your program from a
4960 breakpoint, you can specify an ignore count directly as an argument to
4961 @code{continue}, rather than using @code{ignore}. @xref{Continuing and
4962 Stepping,,Continuing and Stepping}.
4964 If a breakpoint has a positive ignore count and a condition, the
4965 condition is not checked. Once the ignore count reaches zero,
4966 @value{GDBN} resumes checking the condition.
4968 You could achieve the effect of the ignore count with a condition such
4969 as @w{@samp{$foo-- <= 0}} using a debugger convenience variable that
4970 is decremented each time. @xref{Convenience Vars, ,Convenience
4974 Ignore counts apply to breakpoints, watchpoints, and catchpoints.
4977 @node Break Commands
4978 @subsection Breakpoint Command Lists
4980 @cindex breakpoint commands
4981 You can give any breakpoint (or watchpoint or catchpoint) a series of
4982 commands to execute when your program stops due to that breakpoint. For
4983 example, you might want to print the values of certain expressions, or
4984 enable other breakpoints.
4988 @kindex end@r{ (breakpoint commands)}
4989 @item commands @r{[}@var{list}@dots{}@r{]}
4990 @itemx @dots{} @var{command-list} @dots{}
4992 Specify a list of commands for the given breakpoints. The commands
4993 themselves appear on the following lines. Type a line containing just
4994 @code{end} to terminate the commands.
4996 To remove all commands from a breakpoint, type @code{commands} and
4997 follow it immediately with @code{end}; that is, give no commands.
4999 With no argument, @code{commands} refers to the last breakpoint,
5000 watchpoint, or catchpoint set (not to the breakpoint most recently
5001 encountered). If the most recent breakpoints were set with a single
5002 command, then the @code{commands} will apply to all the breakpoints
5003 set by that command. This applies to breakpoints set by
5004 @code{rbreak}, and also applies when a single @code{break} command
5005 creates multiple breakpoints (@pxref{Ambiguous Expressions,,Ambiguous
5009 Pressing @key{RET} as a means of repeating the last @value{GDBN} command is
5010 disabled within a @var{command-list}.
5012 You can use breakpoint commands to start your program up again. Simply
5013 use the @code{continue} command, or @code{step}, or any other command
5014 that resumes execution.
5016 Any other commands in the command list, after a command that resumes
5017 execution, are ignored. This is because any time you resume execution
5018 (even with a simple @code{next} or @code{step}), you may encounter
5019 another breakpoint---which could have its own command list, leading to
5020 ambiguities about which list to execute.
5023 If the first command you specify in a command list is @code{silent}, the
5024 usual message about stopping at a breakpoint is not printed. This may
5025 be desirable for breakpoints that are to print a specific message and
5026 then continue. If none of the remaining commands print anything, you
5027 see no sign that the breakpoint was reached. @code{silent} is
5028 meaningful only at the beginning of a breakpoint command list.
5030 The commands @code{echo}, @code{output}, and @code{printf} allow you to
5031 print precisely controlled output, and are often useful in silent
5032 breakpoints. @xref{Output, ,Commands for Controlled Output}.
5034 For example, here is how you could use breakpoint commands to print the
5035 value of @code{x} at entry to @code{foo} whenever @code{x} is positive.
5041 printf "x is %d\n",x
5046 One application for breakpoint commands is to compensate for one bug so
5047 you can test for another. Put a breakpoint just after the erroneous line
5048 of code, give it a condition to detect the case in which something
5049 erroneous has been done, and give it commands to assign correct values
5050 to any variables that need them. End with the @code{continue} command
5051 so that your program does not stop, and start with the @code{silent}
5052 command so that no output is produced. Here is an example:
5063 @node Dynamic Printf
5064 @subsection Dynamic Printf
5066 @cindex dynamic printf
5068 The dynamic printf command @code{dprintf} combines a breakpoint with
5069 formatted printing of your program's data to give you the effect of
5070 inserting @code{printf} calls into your program on-the-fly, without
5071 having to recompile it.
5073 In its most basic form, the output goes to the GDB console. However,
5074 you can set the variable @code{dprintf-style} for alternate handling.
5075 For instance, you can ask to format the output by calling your
5076 program's @code{printf} function. This has the advantage that the
5077 characters go to the program's output device, so they can recorded in
5078 redirects to files and so forth.
5080 If you are doing remote debugging with a stub or agent, you can also
5081 ask to have the printf handled by the remote agent. In addition to
5082 ensuring that the output goes to the remote program's device along
5083 with any other output the program might produce, you can also ask that
5084 the dprintf remain active even after disconnecting from the remote
5085 target. Using the stub/agent is also more efficient, as it can do
5086 everything without needing to communicate with @value{GDBN}.
5090 @item dprintf @var{location},@var{template},@var{expression}[,@var{expression}@dots{}]
5091 Whenever execution reaches @var{location}, print the values of one or
5092 more @var{expressions} under the control of the string @var{template}.
5093 To print several values, separate them with commas.
5095 @item set dprintf-style @var{style}
5096 Set the dprintf output to be handled in one of several different
5097 styles enumerated below. A change of style affects all existing
5098 dynamic printfs immediately. (If you need individual control over the
5099 print commands, simply define normal breakpoints with
5100 explicitly-supplied command lists.)
5104 @kindex dprintf-style gdb
5105 Handle the output using the @value{GDBN} @code{printf} command.
5108 @kindex dprintf-style call
5109 Handle the output by calling a function in your program (normally
5113 @kindex dprintf-style agent
5114 Have the remote debugging agent (such as @code{gdbserver}) handle
5115 the output itself. This style is only available for agents that
5116 support running commands on the target.
5119 @item set dprintf-function @var{function}
5120 Set the function to call if the dprintf style is @code{call}. By
5121 default its value is @code{printf}. You may set it to any expression.
5122 that @value{GDBN} can evaluate to a function, as per the @code{call}
5125 @item set dprintf-channel @var{channel}
5126 Set a ``channel'' for dprintf. If set to a non-empty value,
5127 @value{GDBN} will evaluate it as an expression and pass the result as
5128 a first argument to the @code{dprintf-function}, in the manner of
5129 @code{fprintf} and similar functions. Otherwise, the dprintf format
5130 string will be the first argument, in the manner of @code{printf}.
5132 As an example, if you wanted @code{dprintf} output to go to a logfile
5133 that is a standard I/O stream assigned to the variable @code{mylog},
5134 you could do the following:
5137 (gdb) set dprintf-style call
5138 (gdb) set dprintf-function fprintf
5139 (gdb) set dprintf-channel mylog
5140 (gdb) dprintf 25,"at line 25, glob=%d\n",glob
5141 Dprintf 1 at 0x123456: file main.c, line 25.
5143 1 dprintf keep y 0x00123456 in main at main.c:25
5144 call (void) fprintf (mylog,"at line 25, glob=%d\n",glob)
5149 Note that the @code{info break} displays the dynamic printf commands
5150 as normal breakpoint commands; you can thus easily see the effect of
5151 the variable settings.
5153 @item set disconnected-dprintf on
5154 @itemx set disconnected-dprintf off
5155 @kindex set disconnected-dprintf
5156 Choose whether @code{dprintf} commands should continue to run if
5157 @value{GDBN} has disconnected from the target. This only applies
5158 if the @code{dprintf-style} is @code{agent}.
5160 @item show disconnected-dprintf off
5161 @kindex show disconnected-dprintf
5162 Show the current choice for disconnected @code{dprintf}.
5166 @value{GDBN} does not check the validity of function and channel,
5167 relying on you to supply values that are meaningful for the contexts
5168 in which they are being used. For instance, the function and channel
5169 may be the values of local variables, but if that is the case, then
5170 all enabled dynamic prints must be at locations within the scope of
5171 those locals. If evaluation fails, @value{GDBN} will report an error.
5173 @node Save Breakpoints
5174 @subsection How to save breakpoints to a file
5176 To save breakpoint definitions to a file use the @w{@code{save
5177 breakpoints}} command.
5180 @kindex save breakpoints
5181 @cindex save breakpoints to a file for future sessions
5182 @item save breakpoints [@var{filename}]
5183 This command saves all current breakpoint definitions together with
5184 their commands and ignore counts, into a file @file{@var{filename}}
5185 suitable for use in a later debugging session. This includes all
5186 types of breakpoints (breakpoints, watchpoints, catchpoints,
5187 tracepoints). To read the saved breakpoint definitions, use the
5188 @code{source} command (@pxref{Command Files}). Note that watchpoints
5189 with expressions involving local variables may fail to be recreated
5190 because it may not be possible to access the context where the
5191 watchpoint is valid anymore. Because the saved breakpoint definitions
5192 are simply a sequence of @value{GDBN} commands that recreate the
5193 breakpoints, you can edit the file in your favorite editing program,
5194 and remove the breakpoint definitions you're not interested in, or
5195 that can no longer be recreated.
5198 @node Static Probe Points
5199 @subsection Static Probe Points
5201 @cindex static probe point, SystemTap
5202 @cindex static probe point, DTrace
5203 @value{GDBN} supports @dfn{SDT} probes in the code. @acronym{SDT} stands
5204 for Statically Defined Tracing, and the probes are designed to have a tiny
5205 runtime code and data footprint, and no dynamic relocations.
5207 Currently, the following types of probes are supported on
5208 ELF-compatible systems:
5212 @item @code{SystemTap} (@uref{http://sourceware.org/systemtap/})
5213 @acronym{SDT} probes@footnote{See
5214 @uref{http://sourceware.org/systemtap/wiki/AddingUserSpaceProbingToApps}
5215 for more information on how to add @code{SystemTap} @acronym{SDT}
5216 probes in your applications.}. @code{SystemTap} probes are usable
5217 from assembly, C and C@t{++} languages@footnote{See
5218 @uref{http://sourceware.org/systemtap/wiki/UserSpaceProbeImplementation}
5219 for a good reference on how the @acronym{SDT} probes are implemented.}.
5221 @item @code{DTrace} (@uref{http://oss.oracle.com/projects/DTrace})
5222 @acronym{USDT} probes. @code{DTrace} probes are usable from C and
5226 @cindex semaphores on static probe points
5227 Some @code{SystemTap} probes have an associated semaphore variable;
5228 for instance, this happens automatically if you defined your probe
5229 using a DTrace-style @file{.d} file. If your probe has a semaphore,
5230 @value{GDBN} will automatically enable it when you specify a
5231 breakpoint using the @samp{-probe-stap} notation. But, if you put a
5232 breakpoint at a probe's location by some other method (e.g.,
5233 @code{break file:line}), then @value{GDBN} will not automatically set
5234 the semaphore. @code{DTrace} probes do not support semaphores.
5236 You can examine the available static static probes using @code{info
5237 probes}, with optional arguments:
5241 @item info probes @r{[}@var{type}@r{]} @r{[}@var{provider} @r{[}@var{name} @r{[}@var{objfile}@r{]}@r{]}@r{]}
5242 If given, @var{type} is either @code{stap} for listing
5243 @code{SystemTap} probes or @code{dtrace} for listing @code{DTrace}
5244 probes. If omitted all probes are listed regardless of their types.
5246 If given, @var{provider} is a regular expression used to match against provider
5247 names when selecting which probes to list. If omitted, probes by all
5248 probes from all providers are listed.
5250 If given, @var{name} is a regular expression to match against probe names
5251 when selecting which probes to list. If omitted, probe names are not
5252 considered when deciding whether to display them.
5254 If given, @var{objfile} is a regular expression used to select which
5255 object files (executable or shared libraries) to examine. If not
5256 given, all object files are considered.
5258 @item info probes all
5259 List the available static probes, from all types.
5262 @cindex enabling and disabling probes
5263 Some probe points can be enabled and/or disabled. The effect of
5264 enabling or disabling a probe depends on the type of probe being
5265 handled. Some @code{DTrace} probes can be enabled or
5266 disabled, but @code{SystemTap} probes cannot be disabled.
5268 You can enable (or disable) one or more probes using the following
5269 commands, with optional arguments:
5272 @kindex enable probes
5273 @item enable probes @r{[}@var{provider} @r{[}@var{name} @r{[}@var{objfile}@r{]}@r{]}@r{]}
5274 If given, @var{provider} is a regular expression used to match against
5275 provider names when selecting which probes to enable. If omitted,
5276 all probes from all providers are enabled.
5278 If given, @var{name} is a regular expression to match against probe
5279 names when selecting which probes to enable. If omitted, probe names
5280 are not considered when deciding whether to enable them.
5282 If given, @var{objfile} is a regular expression used to select which
5283 object files (executable or shared libraries) to examine. If not
5284 given, all object files are considered.
5286 @kindex disable probes
5287 @item disable probes @r{[}@var{provider} @r{[}@var{name} @r{[}@var{objfile}@r{]}@r{]}@r{]}
5288 See the @code{enable probes} command above for a description of the
5289 optional arguments accepted by this command.
5292 @vindex $_probe_arg@r{, convenience variable}
5293 A probe may specify up to twelve arguments. These are available at the
5294 point at which the probe is defined---that is, when the current PC is
5295 at the probe's location. The arguments are available using the
5296 convenience variables (@pxref{Convenience Vars})
5297 @code{$_probe_arg0}@dots{}@code{$_probe_arg11}. In @code{SystemTap}
5298 probes each probe argument is an integer of the appropriate size;
5299 types are not preserved. In @code{DTrace} probes types are preserved
5300 provided that they are recognized as such by @value{GDBN}; otherwise
5301 the value of the probe argument will be a long integer. The
5302 convenience variable @code{$_probe_argc} holds the number of arguments
5303 at the current probe point.
5305 These variables are always available, but attempts to access them at
5306 any location other than a probe point will cause @value{GDBN} to give
5310 @c @ifclear BARETARGET
5311 @node Error in Breakpoints
5312 @subsection ``Cannot insert breakpoints''
5314 If you request too many active hardware-assisted breakpoints and
5315 watchpoints, you will see this error message:
5317 @c FIXME: the precise wording of this message may change; the relevant
5318 @c source change is not committed yet (Sep 3, 1999).
5320 Stopped; cannot insert breakpoints.
5321 You may have requested too many hardware breakpoints and watchpoints.
5325 This message is printed when you attempt to resume the program, since
5326 only then @value{GDBN} knows exactly how many hardware breakpoints and
5327 watchpoints it needs to insert.
5329 When this message is printed, you need to disable or remove some of the
5330 hardware-assisted breakpoints and watchpoints, and then continue.
5332 @node Breakpoint-related Warnings
5333 @subsection ``Breakpoint address adjusted...''
5334 @cindex breakpoint address adjusted
5336 Some processor architectures place constraints on the addresses at
5337 which breakpoints may be placed. For architectures thus constrained,
5338 @value{GDBN} will attempt to adjust the breakpoint's address to comply
5339 with the constraints dictated by the architecture.
5341 One example of such an architecture is the Fujitsu FR-V. The FR-V is
5342 a VLIW architecture in which a number of RISC-like instructions may be
5343 bundled together for parallel execution. The FR-V architecture
5344 constrains the location of a breakpoint instruction within such a
5345 bundle to the instruction with the lowest address. @value{GDBN}
5346 honors this constraint by adjusting a breakpoint's address to the
5347 first in the bundle.
5349 It is not uncommon for optimized code to have bundles which contain
5350 instructions from different source statements, thus it may happen that
5351 a breakpoint's address will be adjusted from one source statement to
5352 another. Since this adjustment may significantly alter @value{GDBN}'s
5353 breakpoint related behavior from what the user expects, a warning is
5354 printed when the breakpoint is first set and also when the breakpoint
5357 A warning like the one below is printed when setting a breakpoint
5358 that's been subject to address adjustment:
5361 warning: Breakpoint address adjusted from 0x00010414 to 0x00010410.
5364 Such warnings are printed both for user settable and @value{GDBN}'s
5365 internal breakpoints. If you see one of these warnings, you should
5366 verify that a breakpoint set at the adjusted address will have the
5367 desired affect. If not, the breakpoint in question may be removed and
5368 other breakpoints may be set which will have the desired behavior.
5369 E.g., it may be sufficient to place the breakpoint at a later
5370 instruction. A conditional breakpoint may also be useful in some
5371 cases to prevent the breakpoint from triggering too often.
5373 @value{GDBN} will also issue a warning when stopping at one of these
5374 adjusted breakpoints:
5377 warning: Breakpoint 1 address previously adjusted from 0x00010414
5381 When this warning is encountered, it may be too late to take remedial
5382 action except in cases where the breakpoint is hit earlier or more
5383 frequently than expected.
5385 @node Continuing and Stepping
5386 @section Continuing and Stepping
5390 @cindex resuming execution
5391 @dfn{Continuing} means resuming program execution until your program
5392 completes normally. In contrast, @dfn{stepping} means executing just
5393 one more ``step'' of your program, where ``step'' may mean either one
5394 line of source code, or one machine instruction (depending on what
5395 particular command you use). Either when continuing or when stepping,
5396 your program may stop even sooner, due to a breakpoint or a signal. (If
5397 it stops due to a signal, you may want to use @code{handle}, or use
5398 @samp{signal 0} to resume execution (@pxref{Signals, ,Signals}),
5399 or you may step into the signal's handler (@pxref{stepping and signal
5404 @kindex c @r{(@code{continue})}
5405 @kindex fg @r{(resume foreground execution)}
5406 @item continue @r{[}@var{ignore-count}@r{]}
5407 @itemx c @r{[}@var{ignore-count}@r{]}
5408 @itemx fg @r{[}@var{ignore-count}@r{]}
5409 Resume program execution, at the address where your program last stopped;
5410 any breakpoints set at that address are bypassed. The optional argument
5411 @var{ignore-count} allows you to specify a further number of times to
5412 ignore a breakpoint at this location; its effect is like that of
5413 @code{ignore} (@pxref{Conditions, ,Break Conditions}).
5415 The argument @var{ignore-count} is meaningful only when your program
5416 stopped due to a breakpoint. At other times, the argument to
5417 @code{continue} is ignored.
5419 The synonyms @code{c} and @code{fg} (for @dfn{foreground}, as the
5420 debugged program is deemed to be the foreground program) are provided
5421 purely for convenience, and have exactly the same behavior as
5425 To resume execution at a different place, you can use @code{return}
5426 (@pxref{Returning, ,Returning from a Function}) to go back to the
5427 calling function; or @code{jump} (@pxref{Jumping, ,Continuing at a
5428 Different Address}) to go to an arbitrary location in your program.
5430 A typical technique for using stepping is to set a breakpoint
5431 (@pxref{Breakpoints, ,Breakpoints; Watchpoints; and Catchpoints}) at the
5432 beginning of the function or the section of your program where a problem
5433 is believed to lie, run your program until it stops at that breakpoint,
5434 and then step through the suspect area, examining the variables that are
5435 interesting, until you see the problem happen.
5439 @kindex s @r{(@code{step})}
5441 Continue running your program until control reaches a different source
5442 line, then stop it and return control to @value{GDBN}. This command is
5443 abbreviated @code{s}.
5446 @c "without debugging information" is imprecise; actually "without line
5447 @c numbers in the debugging information". (gcc -g1 has debugging info but
5448 @c not line numbers). But it seems complex to try to make that
5449 @c distinction here.
5450 @emph{Warning:} If you use the @code{step} command while control is
5451 within a function that was compiled without debugging information,
5452 execution proceeds until control reaches a function that does have
5453 debugging information. Likewise, it will not step into a function which
5454 is compiled without debugging information. To step through functions
5455 without debugging information, use the @code{stepi} command, described
5459 The @code{step} command only stops at the first instruction of a source
5460 line. This prevents the multiple stops that could otherwise occur in
5461 @code{switch} statements, @code{for} loops, etc. @code{step} continues
5462 to stop if a function that has debugging information is called within
5463 the line. In other words, @code{step} @emph{steps inside} any functions
5464 called within the line.
5466 Also, the @code{step} command only enters a function if there is line
5467 number information for the function. Otherwise it acts like the
5468 @code{next} command. This avoids problems when using @code{cc -gl}
5469 on @acronym{MIPS} machines. Previously, @code{step} entered subroutines if there
5470 was any debugging information about the routine.
5472 @item step @var{count}
5473 Continue running as in @code{step}, but do so @var{count} times. If a
5474 breakpoint is reached, or a signal not related to stepping occurs before
5475 @var{count} steps, stepping stops right away.
5478 @kindex n @r{(@code{next})}
5479 @item next @r{[}@var{count}@r{]}
5480 Continue to the next source line in the current (innermost) stack frame.
5481 This is similar to @code{step}, but function calls that appear within
5482 the line of code are executed without stopping. Execution stops when
5483 control reaches a different line of code at the original stack level
5484 that was executing when you gave the @code{next} command. This command
5485 is abbreviated @code{n}.
5487 An argument @var{count} is a repeat count, as for @code{step}.
5490 @c FIX ME!! Do we delete this, or is there a way it fits in with
5491 @c the following paragraph? --- Vctoria
5493 @c @code{next} within a function that lacks debugging information acts like
5494 @c @code{step}, but any function calls appearing within the code of the
5495 @c function are executed without stopping.
5497 The @code{next} command only stops at the first instruction of a
5498 source line. This prevents multiple stops that could otherwise occur in
5499 @code{switch} statements, @code{for} loops, etc.
5501 @kindex set step-mode
5503 @cindex functions without line info, and stepping
5504 @cindex stepping into functions with no line info
5505 @itemx set step-mode on
5506 The @code{set step-mode on} command causes the @code{step} command to
5507 stop at the first instruction of a function which contains no debug line
5508 information rather than stepping over it.
5510 This is useful in cases where you may be interested in inspecting the
5511 machine instructions of a function which has no symbolic info and do not
5512 want @value{GDBN} to automatically skip over this function.
5514 @item set step-mode off
5515 Causes the @code{step} command to step over any functions which contains no
5516 debug information. This is the default.
5518 @item show step-mode
5519 Show whether @value{GDBN} will stop in or step over functions without
5520 source line debug information.
5523 @kindex fin @r{(@code{finish})}
5525 Continue running until just after function in the selected stack frame
5526 returns. Print the returned value (if any). This command can be
5527 abbreviated as @code{fin}.
5529 Contrast this with the @code{return} command (@pxref{Returning,
5530 ,Returning from a Function}).
5533 @kindex u @r{(@code{until})}
5534 @cindex run until specified location
5537 Continue running until a source line past the current line, in the
5538 current stack frame, is reached. This command is used to avoid single
5539 stepping through a loop more than once. It is like the @code{next}
5540 command, except that when @code{until} encounters a jump, it
5541 automatically continues execution until the program counter is greater
5542 than the address of the jump.
5544 This means that when you reach the end of a loop after single stepping
5545 though it, @code{until} makes your program continue execution until it
5546 exits the loop. In contrast, a @code{next} command at the end of a loop
5547 simply steps back to the beginning of the loop, which forces you to step
5548 through the next iteration.
5550 @code{until} always stops your program if it attempts to exit the current
5553 @code{until} may produce somewhat counterintuitive results if the order
5554 of machine code does not match the order of the source lines. For
5555 example, in the following excerpt from a debugging session, the @code{f}
5556 (@code{frame}) command shows that execution is stopped at line
5557 @code{206}; yet when we use @code{until}, we get to line @code{195}:
5561 #0 main (argc=4, argv=0xf7fffae8) at m4.c:206
5563 (@value{GDBP}) until
5564 195 for ( ; argc > 0; NEXTARG) @{
5567 This happened because, for execution efficiency, the compiler had
5568 generated code for the loop closure test at the end, rather than the
5569 start, of the loop---even though the test in a C @code{for}-loop is
5570 written before the body of the loop. The @code{until} command appeared
5571 to step back to the beginning of the loop when it advanced to this
5572 expression; however, it has not really gone to an earlier
5573 statement---not in terms of the actual machine code.
5575 @code{until} with no argument works by means of single
5576 instruction stepping, and hence is slower than @code{until} with an
5579 @item until @var{location}
5580 @itemx u @var{location}
5581 Continue running your program until either the specified @var{location} is
5582 reached, or the current stack frame returns. The location is any of
5583 the forms described in @ref{Specify Location}.
5584 This form of the command uses temporary breakpoints, and
5585 hence is quicker than @code{until} without an argument. The specified
5586 location is actually reached only if it is in the current frame. This
5587 implies that @code{until} can be used to skip over recursive function
5588 invocations. For instance in the code below, if the current location is
5589 line @code{96}, issuing @code{until 99} will execute the program up to
5590 line @code{99} in the same invocation of factorial, i.e., after the inner
5591 invocations have returned.
5594 94 int factorial (int value)
5596 96 if (value > 1) @{
5597 97 value *= factorial (value - 1);
5604 @kindex advance @var{location}
5605 @item advance @var{location}
5606 Continue running the program up to the given @var{location}. An argument is
5607 required, which should be of one of the forms described in
5608 @ref{Specify Location}.
5609 Execution will also stop upon exit from the current stack
5610 frame. This command is similar to @code{until}, but @code{advance} will
5611 not skip over recursive function calls, and the target location doesn't
5612 have to be in the same frame as the current one.
5616 @kindex si @r{(@code{stepi})}
5618 @itemx stepi @var{arg}
5620 Execute one machine instruction, then stop and return to the debugger.
5622 It is often useful to do @samp{display/i $pc} when stepping by machine
5623 instructions. This makes @value{GDBN} automatically display the next
5624 instruction to be executed, each time your program stops. @xref{Auto
5625 Display,, Automatic Display}.
5627 An argument is a repeat count, as in @code{step}.
5631 @kindex ni @r{(@code{nexti})}
5633 @itemx nexti @var{arg}
5635 Execute one machine instruction, but if it is a function call,
5636 proceed until the function returns.
5638 An argument is a repeat count, as in @code{next}.
5642 @anchor{range stepping}
5643 @cindex range stepping
5644 @cindex target-assisted range stepping
5645 By default, and if available, @value{GDBN} makes use of
5646 target-assisted @dfn{range stepping}. In other words, whenever you
5647 use a stepping command (e.g., @code{step}, @code{next}), @value{GDBN}
5648 tells the target to step the corresponding range of instruction
5649 addresses instead of issuing multiple single-steps. This speeds up
5650 line stepping, particularly for remote targets. Ideally, there should
5651 be no reason you would want to turn range stepping off. However, it's
5652 possible that a bug in the debug info, a bug in the remote stub (for
5653 remote targets), or even a bug in @value{GDBN} could make line
5654 stepping behave incorrectly when target-assisted range stepping is
5655 enabled. You can use the following command to turn off range stepping
5659 @kindex set range-stepping
5660 @kindex show range-stepping
5661 @item set range-stepping
5662 @itemx show range-stepping
5663 Control whether range stepping is enabled.
5665 If @code{on}, and the target supports it, @value{GDBN} tells the
5666 target to step a range of addresses itself, instead of issuing
5667 multiple single-steps. If @code{off}, @value{GDBN} always issues
5668 single-steps, even if range stepping is supported by the target. The
5669 default is @code{on}.
5673 @node Skipping Over Functions and Files
5674 @section Skipping Over Functions and Files
5675 @cindex skipping over functions and files
5677 The program you are debugging may contain some functions which are
5678 uninteresting to debug. The @code{skip} command lets you tell @value{GDBN} to
5679 skip a function, all functions in a file or a particular function in
5680 a particular file when stepping.
5682 For example, consider the following C function:
5693 Suppose you wish to step into the functions @code{foo} and @code{bar}, but you
5694 are not interested in stepping through @code{boring}. If you run @code{step}
5695 at line 103, you'll enter @code{boring()}, but if you run @code{next}, you'll
5696 step over both @code{foo} and @code{boring}!
5698 One solution is to @code{step} into @code{boring} and use the @code{finish}
5699 command to immediately exit it. But this can become tedious if @code{boring}
5700 is called from many places.
5702 A more flexible solution is to execute @kbd{skip boring}. This instructs
5703 @value{GDBN} never to step into @code{boring}. Now when you execute
5704 @code{step} at line 103, you'll step over @code{boring} and directly into
5707 Functions may be skipped by providing either a function name, linespec
5708 (@pxref{Specify Location}), regular expression that matches the function's
5709 name, file name or a @code{glob}-style pattern that matches the file name.
5711 On Posix systems the form of the regular expression is
5712 ``Extended Regular Expressions''. See for example @samp{man 7 regex}
5713 on @sc{gnu}/Linux systems. On non-Posix systems the form of the regular
5714 expression is whatever is provided by the @code{regcomp} function of
5715 the underlying system.
5716 See for example @samp{man 7 glob} on @sc{gnu}/Linux systems for a
5717 description of @code{glob}-style patterns.
5721 @item skip @r{[}@var{options}@r{]}
5722 The basic form of the @code{skip} command takes zero or more options
5723 that specify what to skip.
5724 The @var{options} argument is any useful combination of the following:
5727 @item -file @var{file}
5728 @itemx -fi @var{file}
5729 Functions in @var{file} will be skipped over when stepping.
5731 @item -gfile @var{file-glob-pattern}
5732 @itemx -gfi @var{file-glob-pattern}
5733 @cindex skipping over files via glob-style patterns
5734 Functions in files matching @var{file-glob-pattern} will be skipped
5738 (gdb) skip -gfi utils/*.c
5741 @item -function @var{linespec}
5742 @itemx -fu @var{linespec}
5743 Functions named by @var{linespec} or the function containing the line
5744 named by @var{linespec} will be skipped over when stepping.
5745 @xref{Specify Location}.
5747 @item -rfunction @var{regexp}
5748 @itemx -rfu @var{regexp}
5749 @cindex skipping over functions via regular expressions
5750 Functions whose name matches @var{regexp} will be skipped over when stepping.
5752 This form is useful for complex function names.
5753 For example, there is generally no need to step into C@t{++} @code{std::string}
5754 constructors or destructors. Plus with C@t{++} templates it can be hard to
5755 write out the full name of the function, and often it doesn't matter what
5756 the template arguments are. Specifying the function to be skipped as a
5757 regular expression makes this easier.
5760 (gdb) skip -rfu ^std::(allocator|basic_string)<.*>::~?\1 *\(
5763 If you want to skip every templated C@t{++} constructor and destructor
5764 in the @code{std} namespace you can do:
5767 (gdb) skip -rfu ^std::([a-zA-z0-9_]+)<.*>::~?\1 *\(
5771 If no options are specified, the function you're currently debugging
5774 @kindex skip function
5775 @item skip function @r{[}@var{linespec}@r{]}
5776 After running this command, the function named by @var{linespec} or the
5777 function containing the line named by @var{linespec} will be skipped over when
5778 stepping. @xref{Specify Location}.
5780 If you do not specify @var{linespec}, the function you're currently debugging
5783 (If you have a function called @code{file} that you want to skip, use
5784 @kbd{skip function file}.)
5787 @item skip file @r{[}@var{filename}@r{]}
5788 After running this command, any function whose source lives in @var{filename}
5789 will be skipped over when stepping.
5792 (gdb) skip file boring.c
5793 File boring.c will be skipped when stepping.
5796 If you do not specify @var{filename}, functions whose source lives in the file
5797 you're currently debugging will be skipped.
5800 Skips can be listed, deleted, disabled, and enabled, much like breakpoints.
5801 These are the commands for managing your list of skips:
5805 @item info skip @r{[}@var{range}@r{]}
5806 Print details about the specified skip(s). If @var{range} is not specified,
5807 print a table with details about all functions and files marked for skipping.
5808 @code{info skip} prints the following information about each skip:
5812 A number identifying this skip.
5813 @item Enabled or Disabled
5814 Enabled skips are marked with @samp{y}.
5815 Disabled skips are marked with @samp{n}.
5817 If the file name is a @samp{glob} pattern this is @samp{y}.
5818 Otherwise it is @samp{n}.
5820 The name or @samp{glob} pattern of the file to be skipped.
5821 If no file is specified this is @samp{<none>}.
5823 If the function name is a @samp{regular expression} this is @samp{y}.
5824 Otherwise it is @samp{n}.
5826 The name or regular expression of the function to skip.
5827 If no function is specified this is @samp{<none>}.
5831 @item skip delete @r{[}@var{range}@r{]}
5832 Delete the specified skip(s). If @var{range} is not specified, delete all
5836 @item skip enable @r{[}@var{range}@r{]}
5837 Enable the specified skip(s). If @var{range} is not specified, enable all
5840 @kindex skip disable
5841 @item skip disable @r{[}@var{range}@r{]}
5842 Disable the specified skip(s). If @var{range} is not specified, disable all
5851 A signal is an asynchronous event that can happen in a program. The
5852 operating system defines the possible kinds of signals, and gives each
5853 kind a name and a number. For example, in Unix @code{SIGINT} is the
5854 signal a program gets when you type an interrupt character (often @kbd{Ctrl-c});
5855 @code{SIGSEGV} is the signal a program gets from referencing a place in
5856 memory far away from all the areas in use; @code{SIGALRM} occurs when
5857 the alarm clock timer goes off (which happens only if your program has
5858 requested an alarm).
5860 @cindex fatal signals
5861 Some signals, including @code{SIGALRM}, are a normal part of the
5862 functioning of your program. Others, such as @code{SIGSEGV}, indicate
5863 errors; these signals are @dfn{fatal} (they kill your program immediately) if the
5864 program has not specified in advance some other way to handle the signal.
5865 @code{SIGINT} does not indicate an error in your program, but it is normally
5866 fatal so it can carry out the purpose of the interrupt: to kill the program.
5868 @value{GDBN} has the ability to detect any occurrence of a signal in your
5869 program. You can tell @value{GDBN} in advance what to do for each kind of
5872 @cindex handling signals
5873 Normally, @value{GDBN} is set up to let the non-erroneous signals like
5874 @code{SIGALRM} be silently passed to your program
5875 (so as not to interfere with their role in the program's functioning)
5876 but to stop your program immediately whenever an error signal happens.
5877 You can change these settings with the @code{handle} command.
5880 @kindex info signals
5884 Print a table of all the kinds of signals and how @value{GDBN} has been told to
5885 handle each one. You can use this to see the signal numbers of all
5886 the defined types of signals.
5888 @item info signals @var{sig}
5889 Similar, but print information only about the specified signal number.
5891 @code{info handle} is an alias for @code{info signals}.
5893 @item catch signal @r{[}@var{signal}@dots{} @r{|} @samp{all}@r{]}
5894 Set a catchpoint for the indicated signals. @xref{Set Catchpoints},
5895 for details about this command.
5898 @item handle @var{signal} @r{[}@var{keywords}@dots{}@r{]}
5899 Change the way @value{GDBN} handles signal @var{signal}. The @var{signal}
5900 can be the number of a signal or its name (with or without the
5901 @samp{SIG} at the beginning); a list of signal numbers of the form
5902 @samp{@var{low}-@var{high}}; or the word @samp{all}, meaning all the
5903 known signals. Optional arguments @var{keywords}, described below,
5904 say what change to make.
5908 The keywords allowed by the @code{handle} command can be abbreviated.
5909 Their full names are:
5913 @value{GDBN} should not stop your program when this signal happens. It may
5914 still print a message telling you that the signal has come in.
5917 @value{GDBN} should stop your program when this signal happens. This implies
5918 the @code{print} keyword as well.
5921 @value{GDBN} should print a message when this signal happens.
5924 @value{GDBN} should not mention the occurrence of the signal at all. This
5925 implies the @code{nostop} keyword as well.
5929 @value{GDBN} should allow your program to see this signal; your program
5930 can handle the signal, or else it may terminate if the signal is fatal
5931 and not handled. @code{pass} and @code{noignore} are synonyms.
5935 @value{GDBN} should not allow your program to see this signal.
5936 @code{nopass} and @code{ignore} are synonyms.
5940 When a signal stops your program, the signal is not visible to the
5942 continue. Your program sees the signal then, if @code{pass} is in
5943 effect for the signal in question @emph{at that time}. In other words,
5944 after @value{GDBN} reports a signal, you can use the @code{handle}
5945 command with @code{pass} or @code{nopass} to control whether your
5946 program sees that signal when you continue.
5948 The default is set to @code{nostop}, @code{noprint}, @code{pass} for
5949 non-erroneous signals such as @code{SIGALRM}, @code{SIGWINCH} and
5950 @code{SIGCHLD}, and to @code{stop}, @code{print}, @code{pass} for the
5953 You can also use the @code{signal} command to prevent your program from
5954 seeing a signal, or cause it to see a signal it normally would not see,
5955 or to give it any signal at any time. For example, if your program stopped
5956 due to some sort of memory reference error, you might store correct
5957 values into the erroneous variables and continue, hoping to see more
5958 execution; but your program would probably terminate immediately as
5959 a result of the fatal signal once it saw the signal. To prevent this,
5960 you can continue with @samp{signal 0}. @xref{Signaling, ,Giving your
5963 @cindex stepping and signal handlers
5964 @anchor{stepping and signal handlers}
5966 @value{GDBN} optimizes for stepping the mainline code. If a signal
5967 that has @code{handle nostop} and @code{handle pass} set arrives while
5968 a stepping command (e.g., @code{stepi}, @code{step}, @code{next}) is
5969 in progress, @value{GDBN} lets the signal handler run and then resumes
5970 stepping the mainline code once the signal handler returns. In other
5971 words, @value{GDBN} steps over the signal handler. This prevents
5972 signals that you've specified as not interesting (with @code{handle
5973 nostop}) from changing the focus of debugging unexpectedly. Note that
5974 the signal handler itself may still hit a breakpoint, stop for another
5975 signal that has @code{handle stop} in effect, or for any other event
5976 that normally results in stopping the stepping command sooner. Also
5977 note that @value{GDBN} still informs you that the program received a
5978 signal if @code{handle print} is set.
5980 @anchor{stepping into signal handlers}
5982 If you set @code{handle pass} for a signal, and your program sets up a
5983 handler for it, then issuing a stepping command, such as @code{step}
5984 or @code{stepi}, when your program is stopped due to the signal will
5985 step @emph{into} the signal handler (if the target supports that).
5987 Likewise, if you use the @code{queue-signal} command to queue a signal
5988 to be delivered to the current thread when execution of the thread
5989 resumes (@pxref{Signaling, ,Giving your Program a Signal}), then a
5990 stepping command will step into the signal handler.
5992 Here's an example, using @code{stepi} to step to the first instruction
5993 of @code{SIGUSR1}'s handler:
5996 (@value{GDBP}) handle SIGUSR1
5997 Signal Stop Print Pass to program Description
5998 SIGUSR1 Yes Yes Yes User defined signal 1
6002 Program received signal SIGUSR1, User defined signal 1.
6003 main () sigusr1.c:28
6006 sigusr1_handler () at sigusr1.c:9
6010 The same, but using @code{queue-signal} instead of waiting for the
6011 program to receive the signal first:
6016 (@value{GDBP}) queue-signal SIGUSR1
6018 sigusr1_handler () at sigusr1.c:9
6023 @cindex extra signal information
6024 @anchor{extra signal information}
6026 On some targets, @value{GDBN} can inspect extra signal information
6027 associated with the intercepted signal, before it is actually
6028 delivered to the program being debugged. This information is exported
6029 by the convenience variable @code{$_siginfo}, and consists of data
6030 that is passed by the kernel to the signal handler at the time of the
6031 receipt of a signal. The data type of the information itself is
6032 target dependent. You can see the data type using the @code{ptype
6033 $_siginfo} command. On Unix systems, it typically corresponds to the
6034 standard @code{siginfo_t} type, as defined in the @file{signal.h}
6037 Here's an example, on a @sc{gnu}/Linux system, printing the stray
6038 referenced address that raised a segmentation fault.
6042 (@value{GDBP}) continue
6043 Program received signal SIGSEGV, Segmentation fault.
6044 0x0000000000400766 in main ()
6046 (@value{GDBP}) ptype $_siginfo
6053 struct @{...@} _kill;
6054 struct @{...@} _timer;
6056 struct @{...@} _sigchld;
6057 struct @{...@} _sigfault;
6058 struct @{...@} _sigpoll;
6061 (@value{GDBP}) ptype $_siginfo._sifields._sigfault
6065 (@value{GDBP}) p $_siginfo._sifields._sigfault.si_addr
6066 $1 = (void *) 0x7ffff7ff7000
6070 Depending on target support, @code{$_siginfo} may also be writable.
6072 @cindex Intel MPX boundary violations
6073 @cindex boundary violations, Intel MPX
6074 On some targets, a @code{SIGSEGV} can be caused by a boundary
6075 violation, i.e., accessing an address outside of the allowed range.
6076 In those cases @value{GDBN} may displays additional information,
6077 depending on how @value{GDBN} has been told to handle the signal.
6078 With @code{handle stop SIGSEGV}, @value{GDBN} displays the violation
6079 kind: "Upper" or "Lower", the memory address accessed and the
6080 bounds, while with @code{handle nostop SIGSEGV} no additional
6081 information is displayed.
6083 The usual output of a segfault is:
6085 Program received signal SIGSEGV, Segmentation fault
6086 0x0000000000400d7c in upper () at i386-mpx-sigsegv.c:68
6087 68 value = *(p + len);
6090 While a bound violation is presented as:
6092 Program received signal SIGSEGV, Segmentation fault
6093 Upper bound violation while accessing address 0x7fffffffc3b3
6094 Bounds: [lower = 0x7fffffffc390, upper = 0x7fffffffc3a3]
6095 0x0000000000400d7c in upper () at i386-mpx-sigsegv.c:68
6096 68 value = *(p + len);
6100 @section Stopping and Starting Multi-thread Programs
6102 @cindex stopped threads
6103 @cindex threads, stopped
6105 @cindex continuing threads
6106 @cindex threads, continuing
6108 @value{GDBN} supports debugging programs with multiple threads
6109 (@pxref{Threads,, Debugging Programs with Multiple Threads}). There
6110 are two modes of controlling execution of your program within the
6111 debugger. In the default mode, referred to as @dfn{all-stop mode},
6112 when any thread in your program stops (for example, at a breakpoint
6113 or while being stepped), all other threads in the program are also stopped by
6114 @value{GDBN}. On some targets, @value{GDBN} also supports
6115 @dfn{non-stop mode}, in which other threads can continue to run freely while
6116 you examine the stopped thread in the debugger.
6119 * All-Stop Mode:: All threads stop when GDB takes control
6120 * Non-Stop Mode:: Other threads continue to execute
6121 * Background Execution:: Running your program asynchronously
6122 * Thread-Specific Breakpoints:: Controlling breakpoints
6123 * Interrupted System Calls:: GDB may interfere with system calls
6124 * Observer Mode:: GDB does not alter program behavior
6128 @subsection All-Stop Mode
6130 @cindex all-stop mode
6132 In all-stop mode, whenever your program stops under @value{GDBN} for any reason,
6133 @emph{all} threads of execution stop, not just the current thread. This
6134 allows you to examine the overall state of the program, including
6135 switching between threads, without worrying that things may change
6138 Conversely, whenever you restart the program, @emph{all} threads start
6139 executing. @emph{This is true even when single-stepping} with commands
6140 like @code{step} or @code{next}.
6142 In particular, @value{GDBN} cannot single-step all threads in lockstep.
6143 Since thread scheduling is up to your debugging target's operating
6144 system (not controlled by @value{GDBN}), other threads may
6145 execute more than one statement while the current thread completes a
6146 single step. Moreover, in general other threads stop in the middle of a
6147 statement, rather than at a clean statement boundary, when the program
6150 You might even find your program stopped in another thread after
6151 continuing or even single-stepping. This happens whenever some other
6152 thread runs into a breakpoint, a signal, or an exception before the
6153 first thread completes whatever you requested.
6155 @cindex automatic thread selection
6156 @cindex switching threads automatically
6157 @cindex threads, automatic switching
6158 Whenever @value{GDBN} stops your program, due to a breakpoint or a
6159 signal, it automatically selects the thread where that breakpoint or
6160 signal happened. @value{GDBN} alerts you to the context switch with a
6161 message such as @samp{[Switching to Thread @var{n}]} to identify the
6164 On some OSes, you can modify @value{GDBN}'s default behavior by
6165 locking the OS scheduler to allow only a single thread to run.
6168 @item set scheduler-locking @var{mode}
6169 @cindex scheduler locking mode
6170 @cindex lock scheduler
6171 Set the scheduler locking mode. It applies to normal execution,
6172 record mode, and replay mode. If it is @code{off}, then there is no
6173 locking and any thread may run at any time. If @code{on}, then only
6174 the current thread may run when the inferior is resumed. The
6175 @code{step} mode optimizes for single-stepping; it prevents other
6176 threads from preempting the current thread while you are stepping, so
6177 that the focus of debugging does not change unexpectedly. Other
6178 threads never get a chance to run when you step, and they are
6179 completely free to run when you use commands like @samp{continue},
6180 @samp{until}, or @samp{finish}. However, unless another thread hits a
6181 breakpoint during its timeslice, @value{GDBN} does not change the
6182 current thread away from the thread that you are debugging. The
6183 @code{replay} mode behaves like @code{off} in record mode and like
6184 @code{on} in replay mode.
6186 @item show scheduler-locking
6187 Display the current scheduler locking mode.
6190 @cindex resume threads of multiple processes simultaneously
6191 By default, when you issue one of the execution commands such as
6192 @code{continue}, @code{next} or @code{step}, @value{GDBN} allows only
6193 threads of the current inferior to run. For example, if @value{GDBN}
6194 is attached to two inferiors, each with two threads, the
6195 @code{continue} command resumes only the two threads of the current
6196 inferior. This is useful, for example, when you debug a program that
6197 forks and you want to hold the parent stopped (so that, for instance,
6198 it doesn't run to exit), while you debug the child. In other
6199 situations, you may not be interested in inspecting the current state
6200 of any of the processes @value{GDBN} is attached to, and you may want
6201 to resume them all until some breakpoint is hit. In the latter case,
6202 you can instruct @value{GDBN} to allow all threads of all the
6203 inferiors to run with the @w{@code{set schedule-multiple}} command.
6206 @kindex set schedule-multiple
6207 @item set schedule-multiple
6208 Set the mode for allowing threads of multiple processes to be resumed
6209 when an execution command is issued. When @code{on}, all threads of
6210 all processes are allowed to run. When @code{off}, only the threads
6211 of the current process are resumed. The default is @code{off}. The
6212 @code{scheduler-locking} mode takes precedence when set to @code{on},
6213 or while you are stepping and set to @code{step}.
6215 @item show schedule-multiple
6216 Display the current mode for resuming the execution of threads of
6221 @subsection Non-Stop Mode
6223 @cindex non-stop mode
6225 @c This section is really only a place-holder, and needs to be expanded
6226 @c with more details.
6228 For some multi-threaded targets, @value{GDBN} supports an optional
6229 mode of operation in which you can examine stopped program threads in
6230 the debugger while other threads continue to execute freely. This
6231 minimizes intrusion when debugging live systems, such as programs
6232 where some threads have real-time constraints or must continue to
6233 respond to external events. This is referred to as @dfn{non-stop} mode.
6235 In non-stop mode, when a thread stops to report a debugging event,
6236 @emph{only} that thread is stopped; @value{GDBN} does not stop other
6237 threads as well, in contrast to the all-stop mode behavior. Additionally,
6238 execution commands such as @code{continue} and @code{step} apply by default
6239 only to the current thread in non-stop mode, rather than all threads as
6240 in all-stop mode. This allows you to control threads explicitly in
6241 ways that are not possible in all-stop mode --- for example, stepping
6242 one thread while allowing others to run freely, stepping
6243 one thread while holding all others stopped, or stepping several threads
6244 independently and simultaneously.
6246 To enter non-stop mode, use this sequence of commands before you run
6247 or attach to your program:
6250 # If using the CLI, pagination breaks non-stop.
6253 # Finally, turn it on!
6257 You can use these commands to manipulate the non-stop mode setting:
6260 @kindex set non-stop
6261 @item set non-stop on
6262 Enable selection of non-stop mode.
6263 @item set non-stop off
6264 Disable selection of non-stop mode.
6265 @kindex show non-stop
6267 Show the current non-stop enablement setting.
6270 Note these commands only reflect whether non-stop mode is enabled,
6271 not whether the currently-executing program is being run in non-stop mode.
6272 In particular, the @code{set non-stop} preference is only consulted when
6273 @value{GDBN} starts or connects to the target program, and it is generally
6274 not possible to switch modes once debugging has started. Furthermore,
6275 since not all targets support non-stop mode, even when you have enabled
6276 non-stop mode, @value{GDBN} may still fall back to all-stop operation by
6279 In non-stop mode, all execution commands apply only to the current thread
6280 by default. That is, @code{continue} only continues one thread.
6281 To continue all threads, issue @code{continue -a} or @code{c -a}.
6283 You can use @value{GDBN}'s background execution commands
6284 (@pxref{Background Execution}) to run some threads in the background
6285 while you continue to examine or step others from @value{GDBN}.
6286 The MI execution commands (@pxref{GDB/MI Program Execution}) are
6287 always executed asynchronously in non-stop mode.
6289 Suspending execution is done with the @code{interrupt} command when
6290 running in the background, or @kbd{Ctrl-c} during foreground execution.
6291 In all-stop mode, this stops the whole process;
6292 but in non-stop mode the interrupt applies only to the current thread.
6293 To stop the whole program, use @code{interrupt -a}.
6295 Other execution commands do not currently support the @code{-a} option.
6297 In non-stop mode, when a thread stops, @value{GDBN} doesn't automatically make
6298 that thread current, as it does in all-stop mode. This is because the
6299 thread stop notifications are asynchronous with respect to @value{GDBN}'s
6300 command interpreter, and it would be confusing if @value{GDBN} unexpectedly
6301 changed to a different thread just as you entered a command to operate on the
6302 previously current thread.
6304 @node Background Execution
6305 @subsection Background Execution
6307 @cindex foreground execution
6308 @cindex background execution
6309 @cindex asynchronous execution
6310 @cindex execution, foreground, background and asynchronous
6312 @value{GDBN}'s execution commands have two variants: the normal
6313 foreground (synchronous) behavior, and a background
6314 (asynchronous) behavior. In foreground execution, @value{GDBN} waits for
6315 the program to report that some thread has stopped before prompting for
6316 another command. In background execution, @value{GDBN} immediately gives
6317 a command prompt so that you can issue other commands while your program runs.
6319 If the target doesn't support async mode, @value{GDBN} issues an error
6320 message if you attempt to use the background execution commands.
6322 @cindex @code{&}, background execution of commands
6323 To specify background execution, add a @code{&} to the command. For example,
6324 the background form of the @code{continue} command is @code{continue&}, or
6325 just @code{c&}. The execution commands that accept background execution
6331 @xref{Starting, , Starting your Program}.
6335 @xref{Attach, , Debugging an Already-running Process}.
6339 @xref{Continuing and Stepping, step}.
6343 @xref{Continuing and Stepping, stepi}.
6347 @xref{Continuing and Stepping, next}.
6351 @xref{Continuing and Stepping, nexti}.
6355 @xref{Continuing and Stepping, continue}.
6359 @xref{Continuing and Stepping, finish}.
6363 @xref{Continuing and Stepping, until}.
6367 Background execution is especially useful in conjunction with non-stop
6368 mode for debugging programs with multiple threads; see @ref{Non-Stop Mode}.
6369 However, you can also use these commands in the normal all-stop mode with
6370 the restriction that you cannot issue another execution command until the
6371 previous one finishes. Examples of commands that are valid in all-stop
6372 mode while the program is running include @code{help} and @code{info break}.
6374 You can interrupt your program while it is running in the background by
6375 using the @code{interrupt} command.
6382 Suspend execution of the running program. In all-stop mode,
6383 @code{interrupt} stops the whole process, but in non-stop mode, it stops
6384 only the current thread. To stop the whole program in non-stop mode,
6385 use @code{interrupt -a}.
6388 @node Thread-Specific Breakpoints
6389 @subsection Thread-Specific Breakpoints
6391 When your program has multiple threads (@pxref{Threads,, Debugging
6392 Programs with Multiple Threads}), you can choose whether to set
6393 breakpoints on all threads, or on a particular thread.
6396 @cindex breakpoints and threads
6397 @cindex thread breakpoints
6398 @kindex break @dots{} thread @var{thread-id}
6399 @item break @var{location} thread @var{thread-id}
6400 @itemx break @var{location} thread @var{thread-id} if @dots{}
6401 @var{location} specifies source lines; there are several ways of
6402 writing them (@pxref{Specify Location}), but the effect is always to
6403 specify some source line.
6405 Use the qualifier @samp{thread @var{thread-id}} with a breakpoint command
6406 to specify that you only want @value{GDBN} to stop the program when a
6407 particular thread reaches this breakpoint. The @var{thread-id} specifier
6408 is one of the thread identifiers assigned by @value{GDBN}, shown
6409 in the first column of the @samp{info threads} display.
6411 If you do not specify @samp{thread @var{thread-id}} when you set a
6412 breakpoint, the breakpoint applies to @emph{all} threads of your
6415 You can use the @code{thread} qualifier on conditional breakpoints as
6416 well; in this case, place @samp{thread @var{thread-id}} before or
6417 after the breakpoint condition, like this:
6420 (@value{GDBP}) break frik.c:13 thread 28 if bartab > lim
6425 Thread-specific breakpoints are automatically deleted when
6426 @value{GDBN} detects the corresponding thread is no longer in the
6427 thread list. For example:
6431 Thread-specific breakpoint 3 deleted - thread 28 no longer in the thread list.
6434 There are several ways for a thread to disappear, such as a regular
6435 thread exit, but also when you detach from the process with the
6436 @code{detach} command (@pxref{Attach, ,Debugging an Already-running
6437 Process}), or if @value{GDBN} loses the remote connection
6438 (@pxref{Remote Debugging}), etc. Note that with some targets,
6439 @value{GDBN} is only able to detect a thread has exited when the user
6440 explictly asks for the thread list with the @code{info threads}
6443 @node Interrupted System Calls
6444 @subsection Interrupted System Calls
6446 @cindex thread breakpoints and system calls
6447 @cindex system calls and thread breakpoints
6448 @cindex premature return from system calls
6449 There is an unfortunate side effect when using @value{GDBN} to debug
6450 multi-threaded programs. If one thread stops for a
6451 breakpoint, or for some other reason, and another thread is blocked in a
6452 system call, then the system call may return prematurely. This is a
6453 consequence of the interaction between multiple threads and the signals
6454 that @value{GDBN} uses to implement breakpoints and other events that
6457 To handle this problem, your program should check the return value of
6458 each system call and react appropriately. This is good programming
6461 For example, do not write code like this:
6467 The call to @code{sleep} will return early if a different thread stops
6468 at a breakpoint or for some other reason.
6470 Instead, write this:
6475 unslept = sleep (unslept);
6478 A system call is allowed to return early, so the system is still
6479 conforming to its specification. But @value{GDBN} does cause your
6480 multi-threaded program to behave differently than it would without
6483 Also, @value{GDBN} uses internal breakpoints in the thread library to
6484 monitor certain events such as thread creation and thread destruction.
6485 When such an event happens, a system call in another thread may return
6486 prematurely, even though your program does not appear to stop.
6489 @subsection Observer Mode
6491 If you want to build on non-stop mode and observe program behavior
6492 without any chance of disruption by @value{GDBN}, you can set
6493 variables to disable all of the debugger's attempts to modify state,
6494 whether by writing memory, inserting breakpoints, etc. These operate
6495 at a low level, intercepting operations from all commands.
6497 When all of these are set to @code{off}, then @value{GDBN} is said to
6498 be @dfn{observer mode}. As a convenience, the variable
6499 @code{observer} can be set to disable these, plus enable non-stop
6502 Note that @value{GDBN} will not prevent you from making nonsensical
6503 combinations of these settings. For instance, if you have enabled
6504 @code{may-insert-breakpoints} but disabled @code{may-write-memory},
6505 then breakpoints that work by writing trap instructions into the code
6506 stream will still not be able to be placed.
6511 @item set observer on
6512 @itemx set observer off
6513 When set to @code{on}, this disables all the permission variables
6514 below (except for @code{insert-fast-tracepoints}), plus enables
6515 non-stop debugging. Setting this to @code{off} switches back to
6516 normal debugging, though remaining in non-stop mode.
6519 Show whether observer mode is on or off.
6521 @kindex may-write-registers
6522 @item set may-write-registers on
6523 @itemx set may-write-registers off
6524 This controls whether @value{GDBN} will attempt to alter the values of
6525 registers, such as with assignment expressions in @code{print}, or the
6526 @code{jump} command. It defaults to @code{on}.
6528 @item show may-write-registers
6529 Show the current permission to write registers.
6531 @kindex may-write-memory
6532 @item set may-write-memory on
6533 @itemx set may-write-memory off
6534 This controls whether @value{GDBN} will attempt to alter the contents
6535 of memory, such as with assignment expressions in @code{print}. It
6536 defaults to @code{on}.
6538 @item show may-write-memory
6539 Show the current permission to write memory.
6541 @kindex may-insert-breakpoints
6542 @item set may-insert-breakpoints on
6543 @itemx set may-insert-breakpoints off
6544 This controls whether @value{GDBN} will attempt to insert breakpoints.
6545 This affects all breakpoints, including internal breakpoints defined
6546 by @value{GDBN}. It defaults to @code{on}.
6548 @item show may-insert-breakpoints
6549 Show the current permission to insert breakpoints.
6551 @kindex may-insert-tracepoints
6552 @item set may-insert-tracepoints on
6553 @itemx set may-insert-tracepoints off
6554 This controls whether @value{GDBN} will attempt to insert (regular)
6555 tracepoints at the beginning of a tracing experiment. It affects only
6556 non-fast tracepoints, fast tracepoints being under the control of
6557 @code{may-insert-fast-tracepoints}. It defaults to @code{on}.
6559 @item show may-insert-tracepoints
6560 Show the current permission to insert tracepoints.
6562 @kindex may-insert-fast-tracepoints
6563 @item set may-insert-fast-tracepoints on
6564 @itemx set may-insert-fast-tracepoints off
6565 This controls whether @value{GDBN} will attempt to insert fast
6566 tracepoints at the beginning of a tracing experiment. It affects only
6567 fast tracepoints, regular (non-fast) tracepoints being under the
6568 control of @code{may-insert-tracepoints}. It defaults to @code{on}.
6570 @item show may-insert-fast-tracepoints
6571 Show the current permission to insert fast tracepoints.
6573 @kindex may-interrupt
6574 @item set may-interrupt on
6575 @itemx set may-interrupt off
6576 This controls whether @value{GDBN} will attempt to interrupt or stop
6577 program execution. When this variable is @code{off}, the
6578 @code{interrupt} command will have no effect, nor will
6579 @kbd{Ctrl-c}. It defaults to @code{on}.
6581 @item show may-interrupt
6582 Show the current permission to interrupt or stop the program.
6586 @node Reverse Execution
6587 @chapter Running programs backward
6588 @cindex reverse execution
6589 @cindex running programs backward
6591 When you are debugging a program, it is not unusual to realize that
6592 you have gone too far, and some event of interest has already happened.
6593 If the target environment supports it, @value{GDBN} can allow you to
6594 ``rewind'' the program by running it backward.
6596 A target environment that supports reverse execution should be able
6597 to ``undo'' the changes in machine state that have taken place as the
6598 program was executing normally. Variables, registers etc.@: should
6599 revert to their previous values. Obviously this requires a great
6600 deal of sophistication on the part of the target environment; not
6601 all target environments can support reverse execution.
6603 When a program is executed in reverse, the instructions that
6604 have most recently been executed are ``un-executed'', in reverse
6605 order. The program counter runs backward, following the previous
6606 thread of execution in reverse. As each instruction is ``un-executed'',
6607 the values of memory and/or registers that were changed by that
6608 instruction are reverted to their previous states. After executing
6609 a piece of source code in reverse, all side effects of that code
6610 should be ``undone'', and all variables should be returned to their
6611 prior values@footnote{
6612 Note that some side effects are easier to undo than others. For instance,
6613 memory and registers are relatively easy, but device I/O is hard. Some
6614 targets may be able undo things like device I/O, and some may not.
6616 The contract between @value{GDBN} and the reverse executing target
6617 requires only that the target do something reasonable when
6618 @value{GDBN} tells it to execute backwards, and then report the
6619 results back to @value{GDBN}. Whatever the target reports back to
6620 @value{GDBN}, @value{GDBN} will report back to the user. @value{GDBN}
6621 assumes that the memory and registers that the target reports are in a
6622 consistant state, but @value{GDBN} accepts whatever it is given.
6625 If you are debugging in a target environment that supports
6626 reverse execution, @value{GDBN} provides the following commands.
6629 @kindex reverse-continue
6630 @kindex rc @r{(@code{reverse-continue})}
6631 @item reverse-continue @r{[}@var{ignore-count}@r{]}
6632 @itemx rc @r{[}@var{ignore-count}@r{]}
6633 Beginning at the point where your program last stopped, start executing
6634 in reverse. Reverse execution will stop for breakpoints and synchronous
6635 exceptions (signals), just like normal execution. Behavior of
6636 asynchronous signals depends on the target environment.
6638 @kindex reverse-step
6639 @kindex rs @r{(@code{step})}
6640 @item reverse-step @r{[}@var{count}@r{]}
6641 Run the program backward until control reaches the start of a
6642 different source line; then stop it, and return control to @value{GDBN}.
6644 Like the @code{step} command, @code{reverse-step} will only stop
6645 at the beginning of a source line. It ``un-executes'' the previously
6646 executed source line. If the previous source line included calls to
6647 debuggable functions, @code{reverse-step} will step (backward) into
6648 the called function, stopping at the beginning of the @emph{last}
6649 statement in the called function (typically a return statement).
6651 Also, as with the @code{step} command, if non-debuggable functions are
6652 called, @code{reverse-step} will run thru them backward without stopping.
6654 @kindex reverse-stepi
6655 @kindex rsi @r{(@code{reverse-stepi})}
6656 @item reverse-stepi @r{[}@var{count}@r{]}
6657 Reverse-execute one machine instruction. Note that the instruction
6658 to be reverse-executed is @emph{not} the one pointed to by the program
6659 counter, but the instruction executed prior to that one. For instance,
6660 if the last instruction was a jump, @code{reverse-stepi} will take you
6661 back from the destination of the jump to the jump instruction itself.
6663 @kindex reverse-next
6664 @kindex rn @r{(@code{reverse-next})}
6665 @item reverse-next @r{[}@var{count}@r{]}
6666 Run backward to the beginning of the previous line executed in
6667 the current (innermost) stack frame. If the line contains function
6668 calls, they will be ``un-executed'' without stopping. Starting from
6669 the first line of a function, @code{reverse-next} will take you back
6670 to the caller of that function, @emph{before} the function was called,
6671 just as the normal @code{next} command would take you from the last
6672 line of a function back to its return to its caller
6673 @footnote{Unless the code is too heavily optimized.}.
6675 @kindex reverse-nexti
6676 @kindex rni @r{(@code{reverse-nexti})}
6677 @item reverse-nexti @r{[}@var{count}@r{]}
6678 Like @code{nexti}, @code{reverse-nexti} executes a single instruction
6679 in reverse, except that called functions are ``un-executed'' atomically.
6680 That is, if the previously executed instruction was a return from
6681 another function, @code{reverse-nexti} will continue to execute
6682 in reverse until the call to that function (from the current stack
6685 @kindex reverse-finish
6686 @item reverse-finish
6687 Just as the @code{finish} command takes you to the point where the
6688 current function returns, @code{reverse-finish} takes you to the point
6689 where it was called. Instead of ending up at the end of the current
6690 function invocation, you end up at the beginning.
6692 @kindex set exec-direction
6693 @item set exec-direction
6694 Set the direction of target execution.
6695 @item set exec-direction reverse
6696 @cindex execute forward or backward in time
6697 @value{GDBN} will perform all execution commands in reverse, until the
6698 exec-direction mode is changed to ``forward''. Affected commands include
6699 @code{step, stepi, next, nexti, continue, and finish}. The @code{return}
6700 command cannot be used in reverse mode.
6701 @item set exec-direction forward
6702 @value{GDBN} will perform all execution commands in the normal fashion.
6703 This is the default.
6707 @node Process Record and Replay
6708 @chapter Recording Inferior's Execution and Replaying It
6709 @cindex process record and replay
6710 @cindex recording inferior's execution and replaying it
6712 On some platforms, @value{GDBN} provides a special @dfn{process record
6713 and replay} target that can record a log of the process execution, and
6714 replay it later with both forward and reverse execution commands.
6717 When this target is in use, if the execution log includes the record
6718 for the next instruction, @value{GDBN} will debug in @dfn{replay
6719 mode}. In the replay mode, the inferior does not really execute code
6720 instructions. Instead, all the events that normally happen during
6721 code execution are taken from the execution log. While code is not
6722 really executed in replay mode, the values of registers (including the
6723 program counter register) and the memory of the inferior are still
6724 changed as they normally would. Their contents are taken from the
6728 If the record for the next instruction is not in the execution log,
6729 @value{GDBN} will debug in @dfn{record mode}. In this mode, the
6730 inferior executes normally, and @value{GDBN} records the execution log
6733 The process record and replay target supports reverse execution
6734 (@pxref{Reverse Execution}), even if the platform on which the
6735 inferior runs does not. However, the reverse execution is limited in
6736 this case by the range of the instructions recorded in the execution
6737 log. In other words, reverse execution on platforms that don't
6738 support it directly can only be done in the replay mode.
6740 When debugging in the reverse direction, @value{GDBN} will work in
6741 replay mode as long as the execution log includes the record for the
6742 previous instruction; otherwise, it will work in record mode, if the
6743 platform supports reverse execution, or stop if not.
6745 For architecture environments that support process record and replay,
6746 @value{GDBN} provides the following commands:
6749 @kindex target record
6750 @kindex target record-full
6751 @kindex target record-btrace
6754 @kindex record btrace
6755 @kindex record btrace bts
6756 @kindex record btrace pt
6762 @kindex rec btrace bts
6763 @kindex rec btrace pt
6766 @item record @var{method}
6767 This command starts the process record and replay target. The
6768 recording method can be specified as parameter. Without a parameter
6769 the command uses the @code{full} recording method. The following
6770 recording methods are available:
6774 Full record/replay recording using @value{GDBN}'s software record and
6775 replay implementation. This method allows replaying and reverse
6778 @item btrace @var{format}
6779 Hardware-supported instruction recording. This method does not record
6780 data. Further, the data is collected in a ring buffer so old data will
6781 be overwritten when the buffer is full. It allows limited reverse
6782 execution. Variables and registers are not available during reverse
6783 execution. In remote debugging, recording continues on disconnect.
6784 Recorded data can be inspected after reconnecting. The recording may
6785 be stopped using @code{record stop}.
6787 The recording format can be specified as parameter. Without a parameter
6788 the command chooses the recording format. The following recording
6789 formats are available:
6793 @cindex branch trace store
6794 Use the @dfn{Branch Trace Store} (@acronym{BTS}) recording format. In
6795 this format, the processor stores a from/to record for each executed
6796 branch in the btrace ring buffer.
6799 @cindex Intel Processor Trace
6800 Use the @dfn{Intel Processor Trace} recording format. In this
6801 format, the processor stores the execution trace in a compressed form
6802 that is afterwards decoded by @value{GDBN}.
6804 The trace can be recorded with very low overhead. The compressed
6805 trace format also allows small trace buffers to already contain a big
6806 number of instructions compared to @acronym{BTS}.
6808 Decoding the recorded execution trace, on the other hand, is more
6809 expensive than decoding @acronym{BTS} trace. This is mostly due to the
6810 increased number of instructions to process. You should increase the
6811 buffer-size with care.
6814 Not all recording formats may be available on all processors.
6817 The process record and replay target can only debug a process that is
6818 already running. Therefore, you need first to start the process with
6819 the @kbd{run} or @kbd{start} commands, and then start the recording
6820 with the @kbd{record @var{method}} command.
6822 @cindex displaced stepping, and process record and replay
6823 Displaced stepping (@pxref{Maintenance Commands,, displaced stepping})
6824 will be automatically disabled when process record and replay target
6825 is started. That's because the process record and replay target
6826 doesn't support displaced stepping.
6828 @cindex non-stop mode, and process record and replay
6829 @cindex asynchronous execution, and process record and replay
6830 If the inferior is in the non-stop mode (@pxref{Non-Stop Mode}) or in
6831 the asynchronous execution mode (@pxref{Background Execution}), not
6832 all recording methods are available. The @code{full} recording method
6833 does not support these two modes.
6838 Stop the process record and replay target. When process record and
6839 replay target stops, the entire execution log will be deleted and the
6840 inferior will either be terminated, or will remain in its final state.
6842 When you stop the process record and replay target in record mode (at
6843 the end of the execution log), the inferior will be stopped at the
6844 next instruction that would have been recorded. In other words, if
6845 you record for a while and then stop recording, the inferior process
6846 will be left in the same state as if the recording never happened.
6848 On the other hand, if the process record and replay target is stopped
6849 while in replay mode (that is, not at the end of the execution log,
6850 but at some earlier point), the inferior process will become ``live''
6851 at that earlier state, and it will then be possible to continue the
6852 usual ``live'' debugging of the process from that state.
6854 When the inferior process exits, or @value{GDBN} detaches from it,
6855 process record and replay target will automatically stop itself.
6859 Go to a specific location in the execution log. There are several
6860 ways to specify the location to go to:
6863 @item record goto begin
6864 @itemx record goto start
6865 Go to the beginning of the execution log.
6867 @item record goto end
6868 Go to the end of the execution log.
6870 @item record goto @var{n}
6871 Go to instruction number @var{n} in the execution log.
6875 @item record save @var{filename}
6876 Save the execution log to a file @file{@var{filename}}.
6877 Default filename is @file{gdb_record.@var{process_id}}, where
6878 @var{process_id} is the process ID of the inferior.
6880 This command may not be available for all recording methods.
6882 @kindex record restore
6883 @item record restore @var{filename}
6884 Restore the execution log from a file @file{@var{filename}}.
6885 File must have been created with @code{record save}.
6887 @kindex set record full
6888 @item set record full insn-number-max @var{limit}
6889 @itemx set record full insn-number-max unlimited
6890 Set the limit of instructions to be recorded for the @code{full}
6891 recording method. Default value is 200000.
6893 If @var{limit} is a positive number, then @value{GDBN} will start
6894 deleting instructions from the log once the number of the record
6895 instructions becomes greater than @var{limit}. For every new recorded
6896 instruction, @value{GDBN} will delete the earliest recorded
6897 instruction to keep the number of recorded instructions at the limit.
6898 (Since deleting recorded instructions loses information, @value{GDBN}
6899 lets you control what happens when the limit is reached, by means of
6900 the @code{stop-at-limit} option, described below.)
6902 If @var{limit} is @code{unlimited} or zero, @value{GDBN} will never
6903 delete recorded instructions from the execution log. The number of
6904 recorded instructions is limited only by the available memory.
6906 @kindex show record full
6907 @item show record full insn-number-max
6908 Show the limit of instructions to be recorded with the @code{full}
6911 @item set record full stop-at-limit
6912 Control the behavior of the @code{full} recording method when the
6913 number of recorded instructions reaches the limit. If ON (the
6914 default), @value{GDBN} will stop when the limit is reached for the
6915 first time and ask you whether you want to stop the inferior or
6916 continue running it and recording the execution log. If you decide
6917 to continue recording, each new recorded instruction will cause the
6918 oldest one to be deleted.
6920 If this option is OFF, @value{GDBN} will automatically delete the
6921 oldest record to make room for each new one, without asking.
6923 @item show record full stop-at-limit
6924 Show the current setting of @code{stop-at-limit}.
6926 @item set record full memory-query
6927 Control the behavior when @value{GDBN} is unable to record memory
6928 changes caused by an instruction for the @code{full} recording method.
6929 If ON, @value{GDBN} will query whether to stop the inferior in that
6932 If this option is OFF (the default), @value{GDBN} will automatically
6933 ignore the effect of such instructions on memory. Later, when
6934 @value{GDBN} replays this execution log, it will mark the log of this
6935 instruction as not accessible, and it will not affect the replay
6938 @item show record full memory-query
6939 Show the current setting of @code{memory-query}.
6941 @kindex set record btrace
6942 The @code{btrace} record target does not trace data. As a
6943 convenience, when replaying, @value{GDBN} reads read-only memory off
6944 the live program directly, assuming that the addresses of the
6945 read-only areas don't change. This for example makes it possible to
6946 disassemble code while replaying, but not to print variables.
6947 In some cases, being able to inspect variables might be useful.
6948 You can use the following command for that:
6950 @item set record btrace replay-memory-access
6951 Control the behavior of the @code{btrace} recording method when
6952 accessing memory during replay. If @code{read-only} (the default),
6953 @value{GDBN} will only allow accesses to read-only memory.
6954 If @code{read-write}, @value{GDBN} will allow accesses to read-only
6955 and to read-write memory. Beware that the accessed memory corresponds
6956 to the live target and not necessarily to the current replay
6959 @item set record btrace cpu @var{identifier}
6960 Set the processor to be used for enabling workarounds for processor
6961 errata when decoding the trace.
6963 Processor errata are defects in processor operation, caused by its
6964 design or manufacture. They can cause a trace not to match the
6965 specification. This, in turn, may cause trace decode to fail.
6966 @value{GDBN} can detect erroneous trace packets and correct them, thus
6967 avoiding the decoding failures. These corrections are known as
6968 @dfn{errata workarounds}, and are enabled based on the processor on
6969 which the trace was recorded.
6971 By default, @value{GDBN} attempts to detect the processor
6972 automatically, and apply the necessary workarounds for it. However,
6973 you may need to specify the processor if @value{GDBN} does not yet
6974 support it. This command allows you to do that, and also allows to
6975 disable the workarounds.
6977 The argument @var{identifier} identifies the @sc{cpu} and is of the
6978 form: @code{@var{vendor}:@var{procesor identifier}}. In addition,
6979 there are two special identifiers, @code{none} and @code{auto}
6982 The following vendor identifiers and corresponding processor
6983 identifiers are currently supported:
6985 @multitable @columnfractions .1 .9
6988 @tab @var{family}/@var{model}[/@var{stepping}]
6992 On GNU/Linux systems, the processor @var{family}, @var{model}, and
6993 @var{stepping} can be obtained from @code{/proc/cpuinfo}.
6995 If @var{identifier} is @code{auto}, enable errata workarounds for the
6996 processor on which the trace was recorded. If @var{identifier} is
6997 @code{none}, errata workarounds are disabled.
6999 For example, when using an old @value{GDBN} on a new system, decode
7000 may fail because @value{GDBN} does not support the new processor. It
7001 often suffices to specify an older processor that @value{GDBN}
7006 Active record target: record-btrace
7007 Recording format: Intel Processor Trace.
7009 Failed to configure the Intel Processor Trace decoder: unknown cpu.
7010 (gdb) set record btrace cpu intel:6/158
7012 Active record target: record-btrace
7013 Recording format: Intel Processor Trace.
7015 Recorded 84872 instructions in 3189 functions (0 gaps) for thread 1 (...).
7018 @kindex show record btrace
7019 @item show record btrace replay-memory-access
7020 Show the current setting of @code{replay-memory-access}.
7022 @item show record btrace cpu
7023 Show the processor to be used for enabling trace decode errata
7026 @kindex set record btrace bts
7027 @item set record btrace bts buffer-size @var{size}
7028 @itemx set record btrace bts buffer-size unlimited
7029 Set the requested ring buffer size for branch tracing in @acronym{BTS}
7030 format. Default is 64KB.
7032 If @var{size} is a positive number, then @value{GDBN} will try to
7033 allocate a buffer of at least @var{size} bytes for each new thread
7034 that uses the btrace recording method and the @acronym{BTS} format.
7035 The actually obtained buffer size may differ from the requested
7036 @var{size}. Use the @code{info record} command to see the actual
7037 buffer size for each thread that uses the btrace recording method and
7038 the @acronym{BTS} format.
7040 If @var{limit} is @code{unlimited} or zero, @value{GDBN} will try to
7041 allocate a buffer of 4MB.
7043 Bigger buffers mean longer traces. On the other hand, @value{GDBN} will
7044 also need longer to process the branch trace data before it can be used.
7046 @item show record btrace bts buffer-size @var{size}
7047 Show the current setting of the requested ring buffer size for branch
7048 tracing in @acronym{BTS} format.
7050 @kindex set record btrace pt
7051 @item set record btrace pt buffer-size @var{size}
7052 @itemx set record btrace pt buffer-size unlimited
7053 Set the requested ring buffer size for branch tracing in Intel
7054 Processor Trace format. Default is 16KB.
7056 If @var{size} is a positive number, then @value{GDBN} will try to
7057 allocate a buffer of at least @var{size} bytes for each new thread
7058 that uses the btrace recording method and the Intel Processor Trace
7059 format. The actually obtained buffer size may differ from the
7060 requested @var{size}. Use the @code{info record} command to see the
7061 actual buffer size for each thread.
7063 If @var{limit} is @code{unlimited} or zero, @value{GDBN} will try to
7064 allocate a buffer of 4MB.
7066 Bigger buffers mean longer traces. On the other hand, @value{GDBN} will
7067 also need longer to process the branch trace data before it can be used.
7069 @item show record btrace pt buffer-size @var{size}
7070 Show the current setting of the requested ring buffer size for branch
7071 tracing in Intel Processor Trace format.
7075 Show various statistics about the recording depending on the recording
7080 For the @code{full} recording method, it shows the state of process
7081 record and its in-memory execution log buffer, including:
7085 Whether in record mode or replay mode.
7087 Lowest recorded instruction number (counting from when the current execution log started recording instructions).
7089 Highest recorded instruction number.
7091 Current instruction about to be replayed (if in replay mode).
7093 Number of instructions contained in the execution log.
7095 Maximum number of instructions that may be contained in the execution log.
7099 For the @code{btrace} recording method, it shows:
7105 Number of instructions that have been recorded.
7107 Number of blocks of sequential control-flow formed by the recorded
7110 Whether in record mode or replay mode.
7113 For the @code{bts} recording format, it also shows:
7116 Size of the perf ring buffer.
7119 For the @code{pt} recording format, it also shows:
7122 Size of the perf ring buffer.
7126 @kindex record delete
7129 When record target runs in replay mode (``in the past''), delete the
7130 subsequent execution log and begin to record a new execution log starting
7131 from the current address. This means you will abandon the previously
7132 recorded ``future'' and begin recording a new ``future''.
7134 @kindex record instruction-history
7135 @kindex rec instruction-history
7136 @item record instruction-history
7137 Disassembles instructions from the recorded execution log. By
7138 default, ten instructions are disassembled. This can be changed using
7139 the @code{set record instruction-history-size} command. Instructions
7140 are printed in execution order.
7142 It can also print mixed source+disassembly if you specify the the
7143 @code{/m} or @code{/s} modifier, and print the raw instructions in hex
7144 as well as in symbolic form by specifying the @code{/r} modifier.
7146 The current position marker is printed for the instruction at the
7147 current program counter value. This instruction can appear multiple
7148 times in the trace and the current position marker will be printed
7149 every time. To omit the current position marker, specify the
7152 To better align the printed instructions when the trace contains
7153 instructions from more than one function, the function name may be
7154 omitted by specifying the @code{/f} modifier.
7156 Speculatively executed instructions are prefixed with @samp{?}. This
7157 feature is not available for all recording formats.
7159 There are several ways to specify what part of the execution log to
7163 @item record instruction-history @var{insn}
7164 Disassembles ten instructions starting from instruction number
7167 @item record instruction-history @var{insn}, +/-@var{n}
7168 Disassembles @var{n} instructions around instruction number
7169 @var{insn}. If @var{n} is preceded with @code{+}, disassembles
7170 @var{n} instructions after instruction number @var{insn}. If
7171 @var{n} is preceded with @code{-}, disassembles @var{n}
7172 instructions before instruction number @var{insn}.
7174 @item record instruction-history
7175 Disassembles ten more instructions after the last disassembly.
7177 @item record instruction-history -
7178 Disassembles ten more instructions before the last disassembly.
7180 @item record instruction-history @var{begin}, @var{end}
7181 Disassembles instructions beginning with instruction number
7182 @var{begin} until instruction number @var{end}. The instruction
7183 number @var{end} is included.
7186 This command may not be available for all recording methods.
7189 @item set record instruction-history-size @var{size}
7190 @itemx set record instruction-history-size unlimited
7191 Define how many instructions to disassemble in the @code{record
7192 instruction-history} command. The default value is 10.
7193 A @var{size} of @code{unlimited} means unlimited instructions.
7196 @item show record instruction-history-size
7197 Show how many instructions to disassemble in the @code{record
7198 instruction-history} command.
7200 @kindex record function-call-history
7201 @kindex rec function-call-history
7202 @item record function-call-history
7203 Prints the execution history at function granularity. It prints one
7204 line for each sequence of instructions that belong to the same
7205 function giving the name of that function, the source lines
7206 for this instruction sequence (if the @code{/l} modifier is
7207 specified), and the instructions numbers that form the sequence (if
7208 the @code{/i} modifier is specified). The function names are indented
7209 to reflect the call stack depth if the @code{/c} modifier is
7210 specified. The @code{/l}, @code{/i}, and @code{/c} modifiers can be
7214 (@value{GDBP}) @b{list 1, 10}
7225 (@value{GDBP}) @b{record function-call-history /ilc}
7226 1 bar inst 1,4 at foo.c:6,8
7227 2 foo inst 5,10 at foo.c:2,3
7228 3 bar inst 11,13 at foo.c:9,10
7231 By default, ten lines are printed. This can be changed using the
7232 @code{set record function-call-history-size} command. Functions are
7233 printed in execution order. There are several ways to specify what
7237 @item record function-call-history @var{func}
7238 Prints ten functions starting from function number @var{func}.
7240 @item record function-call-history @var{func}, +/-@var{n}
7241 Prints @var{n} functions around function number @var{func}. If
7242 @var{n} is preceded with @code{+}, prints @var{n} functions after
7243 function number @var{func}. If @var{n} is preceded with @code{-},
7244 prints @var{n} functions before function number @var{func}.
7246 @item record function-call-history
7247 Prints ten more functions after the last ten-line print.
7249 @item record function-call-history -
7250 Prints ten more functions before the last ten-line print.
7252 @item record function-call-history @var{begin}, @var{end}
7253 Prints functions beginning with function number @var{begin} until
7254 function number @var{end}. The function number @var{end} is included.
7257 This command may not be available for all recording methods.
7259 @item set record function-call-history-size @var{size}
7260 @itemx set record function-call-history-size unlimited
7261 Define how many lines to print in the
7262 @code{record function-call-history} command. The default value is 10.
7263 A size of @code{unlimited} means unlimited lines.
7265 @item show record function-call-history-size
7266 Show how many lines to print in the
7267 @code{record function-call-history} command.
7272 @chapter Examining the Stack
7274 When your program has stopped, the first thing you need to know is where it
7275 stopped and how it got there.
7278 Each time your program performs a function call, information about the call
7280 That information includes the location of the call in your program,
7281 the arguments of the call,
7282 and the local variables of the function being called.
7283 The information is saved in a block of data called a @dfn{stack frame}.
7284 The stack frames are allocated in a region of memory called the @dfn{call
7287 When your program stops, the @value{GDBN} commands for examining the
7288 stack allow you to see all of this information.
7290 @cindex selected frame
7291 One of the stack frames is @dfn{selected} by @value{GDBN} and many
7292 @value{GDBN} commands refer implicitly to the selected frame. In
7293 particular, whenever you ask @value{GDBN} for the value of a variable in
7294 your program, the value is found in the selected frame. There are
7295 special @value{GDBN} commands to select whichever frame you are
7296 interested in. @xref{Selection, ,Selecting a Frame}.
7298 When your program stops, @value{GDBN} automatically selects the
7299 currently executing frame and describes it briefly, similar to the
7300 @code{frame} command (@pxref{Frame Info, ,Information about a Frame}).
7303 * Frames:: Stack frames
7304 * Backtrace:: Backtraces
7305 * Selection:: Selecting a frame
7306 * Frame Info:: Information on a frame
7307 * Frame Filter Management:: Managing frame filters
7312 @section Stack Frames
7314 @cindex frame, definition
7316 The call stack is divided up into contiguous pieces called @dfn{stack
7317 frames}, or @dfn{frames} for short; each frame is the data associated
7318 with one call to one function. The frame contains the arguments given
7319 to the function, the function's local variables, and the address at
7320 which the function is executing.
7322 @cindex initial frame
7323 @cindex outermost frame
7324 @cindex innermost frame
7325 When your program is started, the stack has only one frame, that of the
7326 function @code{main}. This is called the @dfn{initial} frame or the
7327 @dfn{outermost} frame. Each time a function is called, a new frame is
7328 made. Each time a function returns, the frame for that function invocation
7329 is eliminated. If a function is recursive, there can be many frames for
7330 the same function. The frame for the function in which execution is
7331 actually occurring is called the @dfn{innermost} frame. This is the most
7332 recently created of all the stack frames that still exist.
7334 @cindex frame pointer
7335 Inside your program, stack frames are identified by their addresses. A
7336 stack frame consists of many bytes, each of which has its own address; each
7337 kind of computer has a convention for choosing one byte whose
7338 address serves as the address of the frame. Usually this address is kept
7339 in a register called the @dfn{frame pointer register}
7340 (@pxref{Registers, $fp}) while execution is going on in that frame.
7342 @cindex frame number
7343 @value{GDBN} assigns numbers to all existing stack frames, starting with
7344 zero for the innermost frame, one for the frame that called it,
7345 and so on upward. These numbers do not really exist in your program;
7346 they are assigned by @value{GDBN} to give you a way of designating stack
7347 frames in @value{GDBN} commands.
7349 @c The -fomit-frame-pointer below perennially causes hbox overflow
7350 @c underflow problems.
7351 @cindex frameless execution
7352 Some compilers provide a way to compile functions so that they operate
7353 without stack frames. (For example, the @value{NGCC} option
7355 @samp{-fomit-frame-pointer}
7357 generates functions without a frame.)
7358 This is occasionally done with heavily used library functions to save
7359 the frame setup time. @value{GDBN} has limited facilities for dealing
7360 with these function invocations. If the innermost function invocation
7361 has no stack frame, @value{GDBN} nevertheless regards it as though
7362 it had a separate frame, which is numbered zero as usual, allowing
7363 correct tracing of the function call chain. However, @value{GDBN} has
7364 no provision for frameless functions elsewhere in the stack.
7370 @cindex call stack traces
7371 A backtrace is a summary of how your program got where it is. It shows one
7372 line per frame, for many frames, starting with the currently executing
7373 frame (frame zero), followed by its caller (frame one), and on up the
7376 @anchor{backtrace-command}
7378 @kindex bt @r{(@code{backtrace})}
7379 To print a backtrace of the entire stack, use the @code{backtrace}
7380 command, or its alias @code{bt}. This command will print one line per
7381 frame for frames in the stack. By default, all stack frames are
7382 printed. You can stop the backtrace at any time by typing the system
7383 interrupt character, normally @kbd{Ctrl-c}.
7386 @item backtrace [@var{args}@dots{}]
7387 @itemx bt [@var{args}@dots{}]
7388 Print the backtrace of the entire stack. The optional @var{args} can
7389 be one of the following:
7394 Print only the innermost @var{n} frames, where @var{n} is a positive
7399 Print only the outermost @var{n} frames, where @var{n} is a positive
7403 Print the values of the local variables also. This can be combined
7404 with a number to limit the number of frames shown.
7407 Do not run Python frame filters on this backtrace. @xref{Frame
7408 Filter API}, for more information. Additionally use @ref{disable
7409 frame-filter all} to turn off all frame filters. This is only
7410 relevant when @value{GDBN} has been configured with @code{Python}
7414 A Python frame filter might decide to ``elide'' some frames. Normally
7415 such elided frames are still printed, but they are indented relative
7416 to the filtered frames that cause them to be elided. The @code{hide}
7417 option causes elided frames to not be printed at all.
7423 The names @code{where} and @code{info stack} (abbreviated @code{info s})
7424 are additional aliases for @code{backtrace}.
7426 @cindex multiple threads, backtrace
7427 In a multi-threaded program, @value{GDBN} by default shows the
7428 backtrace only for the current thread. To display the backtrace for
7429 several or all of the threads, use the command @code{thread apply}
7430 (@pxref{Threads, thread apply}). For example, if you type @kbd{thread
7431 apply all backtrace}, @value{GDBN} will display the backtrace for all
7432 the threads; this is handy when you debug a core dump of a
7433 multi-threaded program.
7435 Each line in the backtrace shows the frame number and the function name.
7436 The program counter value is also shown---unless you use @code{set
7437 print address off}. The backtrace also shows the source file name and
7438 line number, as well as the arguments to the function. The program
7439 counter value is omitted if it is at the beginning of the code for that
7442 Here is an example of a backtrace. It was made with the command
7443 @samp{bt 3}, so it shows the innermost three frames.
7447 #0 m4_traceon (obs=0x24eb0, argc=1, argv=0x2b8c8)
7449 #1 0x6e38 in expand_macro (sym=0x2b600, data=...) at macro.c:242
7450 #2 0x6840 in expand_token (obs=0x0, t=177664, td=0xf7fffb08)
7452 (More stack frames follow...)
7457 The display for frame zero does not begin with a program counter
7458 value, indicating that your program has stopped at the beginning of the
7459 code for line @code{993} of @code{builtin.c}.
7462 The value of parameter @code{data} in frame 1 has been replaced by
7463 @code{@dots{}}. By default, @value{GDBN} prints the value of a parameter
7464 only if it is a scalar (integer, pointer, enumeration, etc). See command
7465 @kbd{set print frame-arguments} in @ref{Print Settings} for more details
7466 on how to configure the way function parameter values are printed.
7468 @cindex optimized out, in backtrace
7469 @cindex function call arguments, optimized out
7470 If your program was compiled with optimizations, some compilers will
7471 optimize away arguments passed to functions if those arguments are
7472 never used after the call. Such optimizations generate code that
7473 passes arguments through registers, but doesn't store those arguments
7474 in the stack frame. @value{GDBN} has no way of displaying such
7475 arguments in stack frames other than the innermost one. Here's what
7476 such a backtrace might look like:
7480 #0 m4_traceon (obs=0x24eb0, argc=1, argv=0x2b8c8)
7482 #1 0x6e38 in expand_macro (sym=<optimized out>) at macro.c:242
7483 #2 0x6840 in expand_token (obs=0x0, t=<optimized out>, td=0xf7fffb08)
7485 (More stack frames follow...)
7490 The values of arguments that were not saved in their stack frames are
7491 shown as @samp{<optimized out>}.
7493 If you need to display the values of such optimized-out arguments,
7494 either deduce that from other variables whose values depend on the one
7495 you are interested in, or recompile without optimizations.
7497 @cindex backtrace beyond @code{main} function
7498 @cindex program entry point
7499 @cindex startup code, and backtrace
7500 Most programs have a standard user entry point---a place where system
7501 libraries and startup code transition into user code. For C this is
7502 @code{main}@footnote{
7503 Note that embedded programs (the so-called ``free-standing''
7504 environment) are not required to have a @code{main} function as the
7505 entry point. They could even have multiple entry points.}.
7506 When @value{GDBN} finds the entry function in a backtrace
7507 it will terminate the backtrace, to avoid tracing into highly
7508 system-specific (and generally uninteresting) code.
7510 If you need to examine the startup code, or limit the number of levels
7511 in a backtrace, you can change this behavior:
7514 @item set backtrace past-main
7515 @itemx set backtrace past-main on
7516 @kindex set backtrace
7517 Backtraces will continue past the user entry point.
7519 @item set backtrace past-main off
7520 Backtraces will stop when they encounter the user entry point. This is the
7523 @item show backtrace past-main
7524 @kindex show backtrace
7525 Display the current user entry point backtrace policy.
7527 @item set backtrace past-entry
7528 @itemx set backtrace past-entry on
7529 Backtraces will continue past the internal entry point of an application.
7530 This entry point is encoded by the linker when the application is built,
7531 and is likely before the user entry point @code{main} (or equivalent) is called.
7533 @item set backtrace past-entry off
7534 Backtraces will stop when they encounter the internal entry point of an
7535 application. This is the default.
7537 @item show backtrace past-entry
7538 Display the current internal entry point backtrace policy.
7540 @item set backtrace limit @var{n}
7541 @itemx set backtrace limit 0
7542 @itemx set backtrace limit unlimited
7543 @cindex backtrace limit
7544 Limit the backtrace to @var{n} levels. A value of @code{unlimited}
7545 or zero means unlimited levels.
7547 @item show backtrace limit
7548 Display the current limit on backtrace levels.
7551 You can control how file names are displayed.
7554 @item set filename-display
7555 @itemx set filename-display relative
7556 @cindex filename-display
7557 Display file names relative to the compilation directory. This is the default.
7559 @item set filename-display basename
7560 Display only basename of a filename.
7562 @item set filename-display absolute
7563 Display an absolute filename.
7565 @item show filename-display
7566 Show the current way to display filenames.
7570 @section Selecting a Frame
7572 Most commands for examining the stack and other data in your program work on
7573 whichever stack frame is selected at the moment. Here are the commands for
7574 selecting a stack frame; all of them finish by printing a brief description
7575 of the stack frame just selected.
7578 @kindex frame@r{, selecting}
7579 @kindex f @r{(@code{frame})}
7582 Select frame number @var{n}. Recall that frame zero is the innermost
7583 (currently executing) frame, frame one is the frame that called the
7584 innermost one, and so on. The highest-numbered frame is the one for
7587 @item frame @var{stack-addr} [ @var{pc-addr} ]
7588 @itemx f @var{stack-addr} [ @var{pc-addr} ]
7589 Select the frame at address @var{stack-addr}. This is useful mainly if the
7590 chaining of stack frames has been damaged by a bug, making it
7591 impossible for @value{GDBN} to assign numbers properly to all frames. In
7592 addition, this can be useful when your program has multiple stacks and
7593 switches between them. The optional @var{pc-addr} can also be given to
7594 specify the value of PC for the stack frame.
7598 Move @var{n} frames up the stack; @var{n} defaults to 1. For positive
7599 numbers @var{n}, this advances toward the outermost frame, to higher
7600 frame numbers, to frames that have existed longer.
7603 @kindex do @r{(@code{down})}
7605 Move @var{n} frames down the stack; @var{n} defaults to 1. For
7606 positive numbers @var{n}, this advances toward the innermost frame, to
7607 lower frame numbers, to frames that were created more recently.
7608 You may abbreviate @code{down} as @code{do}.
7611 All of these commands end by printing two lines of output describing the
7612 frame. The first line shows the frame number, the function name, the
7613 arguments, and the source file and line number of execution in that
7614 frame. The second line shows the text of that source line.
7622 #1 0x22f0 in main (argc=1, argv=0xf7fffbf4, env=0xf7fffbfc)
7624 10 read_input_file (argv[i]);
7628 After such a printout, the @code{list} command with no arguments
7629 prints ten lines centered on the point of execution in the frame.
7630 You can also edit the program at the point of execution with your favorite
7631 editing program by typing @code{edit}.
7632 @xref{List, ,Printing Source Lines},
7636 @kindex select-frame
7638 The @code{select-frame} command is a variant of @code{frame} that does
7639 not display the new frame after selecting it. This command is
7640 intended primarily for use in @value{GDBN} command scripts, where the
7641 output might be unnecessary and distracting.
7643 @kindex down-silently
7645 @item up-silently @var{n}
7646 @itemx down-silently @var{n}
7647 These two commands are variants of @code{up} and @code{down},
7648 respectively; they differ in that they do their work silently, without
7649 causing display of the new frame. They are intended primarily for use
7650 in @value{GDBN} command scripts, where the output might be unnecessary and
7655 @section Information About a Frame
7657 There are several other commands to print information about the selected
7663 When used without any argument, this command does not change which
7664 frame is selected, but prints a brief description of the currently
7665 selected stack frame. It can be abbreviated @code{f}. With an
7666 argument, this command is used to select a stack frame.
7667 @xref{Selection, ,Selecting a Frame}.
7670 @kindex info f @r{(@code{info frame})}
7673 This command prints a verbose description of the selected stack frame,
7678 the address of the frame
7680 the address of the next frame down (called by this frame)
7682 the address of the next frame up (caller of this frame)
7684 the language in which the source code corresponding to this frame is written
7686 the address of the frame's arguments
7688 the address of the frame's local variables
7690 the program counter saved in it (the address of execution in the caller frame)
7692 which registers were saved in the frame
7695 @noindent The verbose description is useful when
7696 something has gone wrong that has made the stack format fail to fit
7697 the usual conventions.
7699 @item info frame @var{addr}
7700 @itemx info f @var{addr}
7701 Print a verbose description of the frame at address @var{addr}, without
7702 selecting that frame. The selected frame remains unchanged by this
7703 command. This requires the same kind of address (more than one for some
7704 architectures) that you specify in the @code{frame} command.
7705 @xref{Selection, ,Selecting a Frame}.
7709 Print the arguments of the selected frame, each on a separate line.
7713 Print the local variables of the selected frame, each on a separate
7714 line. These are all variables (declared either static or automatic)
7715 accessible at the point of execution of the selected frame.
7719 @node Frame Filter Management
7720 @section Management of Frame Filters.
7721 @cindex managing frame filters
7723 Frame filters are Python based utilities to manage and decorate the
7724 output of frames. @xref{Frame Filter API}, for further information.
7726 Managing frame filters is performed by several commands available
7727 within @value{GDBN}, detailed here.
7730 @kindex info frame-filter
7731 @item info frame-filter
7732 Print a list of installed frame filters from all dictionaries, showing
7733 their name, priority and enabled status.
7735 @kindex disable frame-filter
7736 @anchor{disable frame-filter all}
7737 @item disable frame-filter @var{filter-dictionary} @var{filter-name}
7738 Disable a frame filter in the dictionary matching
7739 @var{filter-dictionary} and @var{filter-name}. The
7740 @var{filter-dictionary} may be @code{all}, @code{global},
7741 @code{progspace}, or the name of the object file where the frame filter
7742 dictionary resides. When @code{all} is specified, all frame filters
7743 across all dictionaries are disabled. The @var{filter-name} is the name
7744 of the frame filter and is used when @code{all} is not the option for
7745 @var{filter-dictionary}. A disabled frame-filter is not deleted, it
7746 may be enabled again later.
7748 @kindex enable frame-filter
7749 @item enable frame-filter @var{filter-dictionary} @var{filter-name}
7750 Enable a frame filter in the dictionary matching
7751 @var{filter-dictionary} and @var{filter-name}. The
7752 @var{filter-dictionary} may be @code{all}, @code{global},
7753 @code{progspace} or the name of the object file where the frame filter
7754 dictionary resides. When @code{all} is specified, all frame filters across
7755 all dictionaries are enabled. The @var{filter-name} is the name of the frame
7756 filter and is used when @code{all} is not the option for
7757 @var{filter-dictionary}.
7762 (gdb) info frame-filter
7764 global frame-filters:
7765 Priority Enabled Name
7766 1000 No PrimaryFunctionFilter
7769 progspace /build/test frame-filters:
7770 Priority Enabled Name
7771 100 Yes ProgspaceFilter
7773 objfile /build/test frame-filters:
7774 Priority Enabled Name
7775 999 Yes BuildProgra Filter
7777 (gdb) disable frame-filter /build/test BuildProgramFilter
7778 (gdb) info frame-filter
7780 global frame-filters:
7781 Priority Enabled Name
7782 1000 No PrimaryFunctionFilter
7785 progspace /build/test frame-filters:
7786 Priority Enabled Name
7787 100 Yes ProgspaceFilter
7789 objfile /build/test frame-filters:
7790 Priority Enabled Name
7791 999 No BuildProgramFilter
7793 (gdb) enable frame-filter global PrimaryFunctionFilter
7794 (gdb) info frame-filter
7796 global frame-filters:
7797 Priority Enabled Name
7798 1000 Yes PrimaryFunctionFilter
7801 progspace /build/test frame-filters:
7802 Priority Enabled Name
7803 100 Yes ProgspaceFilter
7805 objfile /build/test frame-filters:
7806 Priority Enabled Name
7807 999 No BuildProgramFilter
7810 @kindex set frame-filter priority
7811 @item set frame-filter priority @var{filter-dictionary} @var{filter-name} @var{priority}
7812 Set the @var{priority} of a frame filter in the dictionary matching
7813 @var{filter-dictionary}, and the frame filter name matching
7814 @var{filter-name}. The @var{filter-dictionary} may be @code{global},
7815 @code{progspace} or the name of the object file where the frame filter
7816 dictionary resides. The @var{priority} is an integer.
7818 @kindex show frame-filter priority
7819 @item show frame-filter priority @var{filter-dictionary} @var{filter-name}
7820 Show the @var{priority} of a frame filter in the dictionary matching
7821 @var{filter-dictionary}, and the frame filter name matching
7822 @var{filter-name}. The @var{filter-dictionary} may be @code{global},
7823 @code{progspace} or the name of the object file where the frame filter
7829 (gdb) info frame-filter
7831 global frame-filters:
7832 Priority Enabled Name
7833 1000 Yes PrimaryFunctionFilter
7836 progspace /build/test frame-filters:
7837 Priority Enabled Name
7838 100 Yes ProgspaceFilter
7840 objfile /build/test frame-filters:
7841 Priority Enabled Name
7842 999 No BuildProgramFilter
7844 (gdb) set frame-filter priority global Reverse 50
7845 (gdb) info frame-filter
7847 global frame-filters:
7848 Priority Enabled Name
7849 1000 Yes PrimaryFunctionFilter
7852 progspace /build/test frame-filters:
7853 Priority Enabled Name
7854 100 Yes ProgspaceFilter
7856 objfile /build/test frame-filters:
7857 Priority Enabled Name
7858 999 No BuildProgramFilter
7863 @chapter Examining Source Files
7865 @value{GDBN} can print parts of your program's source, since the debugging
7866 information recorded in the program tells @value{GDBN} what source files were
7867 used to build it. When your program stops, @value{GDBN} spontaneously prints
7868 the line where it stopped. Likewise, when you select a stack frame
7869 (@pxref{Selection, ,Selecting a Frame}), @value{GDBN} prints the line where
7870 execution in that frame has stopped. You can print other portions of
7871 source files by explicit command.
7873 If you use @value{GDBN} through its @sc{gnu} Emacs interface, you may
7874 prefer to use Emacs facilities to view source; see @ref{Emacs, ,Using
7875 @value{GDBN} under @sc{gnu} Emacs}.
7878 * List:: Printing source lines
7879 * Specify Location:: How to specify code locations
7880 * Edit:: Editing source files
7881 * Search:: Searching source files
7882 * Source Path:: Specifying source directories
7883 * Machine Code:: Source and machine code
7887 @section Printing Source Lines
7890 @kindex l @r{(@code{list})}
7891 To print lines from a source file, use the @code{list} command
7892 (abbreviated @code{l}). By default, ten lines are printed.
7893 There are several ways to specify what part of the file you want to
7894 print; see @ref{Specify Location}, for the full list.
7896 Here are the forms of the @code{list} command most commonly used:
7899 @item list @var{linenum}
7900 Print lines centered around line number @var{linenum} in the
7901 current source file.
7903 @item list @var{function}
7904 Print lines centered around the beginning of function
7908 Print more lines. If the last lines printed were printed with a
7909 @code{list} command, this prints lines following the last lines
7910 printed; however, if the last line printed was a solitary line printed
7911 as part of displaying a stack frame (@pxref{Stack, ,Examining the
7912 Stack}), this prints lines centered around that line.
7915 Print lines just before the lines last printed.
7918 @cindex @code{list}, how many lines to display
7919 By default, @value{GDBN} prints ten source lines with any of these forms of
7920 the @code{list} command. You can change this using @code{set listsize}:
7923 @kindex set listsize
7924 @item set listsize @var{count}
7925 @itemx set listsize unlimited
7926 Make the @code{list} command display @var{count} source lines (unless
7927 the @code{list} argument explicitly specifies some other number).
7928 Setting @var{count} to @code{unlimited} or 0 means there's no limit.
7930 @kindex show listsize
7932 Display the number of lines that @code{list} prints.
7935 Repeating a @code{list} command with @key{RET} discards the argument,
7936 so it is equivalent to typing just @code{list}. This is more useful
7937 than listing the same lines again. An exception is made for an
7938 argument of @samp{-}; that argument is preserved in repetition so that
7939 each repetition moves up in the source file.
7941 In general, the @code{list} command expects you to supply zero, one or two
7942 @dfn{locations}. Locations specify source lines; there are several ways
7943 of writing them (@pxref{Specify Location}), but the effect is always
7944 to specify some source line.
7946 Here is a complete description of the possible arguments for @code{list}:
7949 @item list @var{location}
7950 Print lines centered around the line specified by @var{location}.
7952 @item list @var{first},@var{last}
7953 Print lines from @var{first} to @var{last}. Both arguments are
7954 locations. When a @code{list} command has two locations, and the
7955 source file of the second location is omitted, this refers to
7956 the same source file as the first location.
7958 @item list ,@var{last}
7959 Print lines ending with @var{last}.
7961 @item list @var{first},
7962 Print lines starting with @var{first}.
7965 Print lines just after the lines last printed.
7968 Print lines just before the lines last printed.
7971 As described in the preceding table.
7974 @node Specify Location
7975 @section Specifying a Location
7976 @cindex specifying location
7978 @cindex source location
7981 * Linespec Locations:: Linespec locations
7982 * Explicit Locations:: Explicit locations
7983 * Address Locations:: Address locations
7986 Several @value{GDBN} commands accept arguments that specify a location
7987 of your program's code. Since @value{GDBN} is a source-level
7988 debugger, a location usually specifies some line in the source code.
7989 Locations may be specified using three different formats:
7990 linespec locations, explicit locations, or address locations.
7992 @node Linespec Locations
7993 @subsection Linespec Locations
7994 @cindex linespec locations
7996 A @dfn{linespec} is a colon-separated list of source location parameters such
7997 as file name, function name, etc. Here are all the different ways of
7998 specifying a linespec:
8002 Specifies the line number @var{linenum} of the current source file.
8005 @itemx +@var{offset}
8006 Specifies the line @var{offset} lines before or after the @dfn{current
8007 line}. For the @code{list} command, the current line is the last one
8008 printed; for the breakpoint commands, this is the line at which
8009 execution stopped in the currently selected @dfn{stack frame}
8010 (@pxref{Frames, ,Frames}, for a description of stack frames.) When
8011 used as the second of the two linespecs in a @code{list} command,
8012 this specifies the line @var{offset} lines up or down from the first
8015 @item @var{filename}:@var{linenum}
8016 Specifies the line @var{linenum} in the source file @var{filename}.
8017 If @var{filename} is a relative file name, then it will match any
8018 source file name with the same trailing components. For example, if
8019 @var{filename} is @samp{gcc/expr.c}, then it will match source file
8020 name of @file{/build/trunk/gcc/expr.c}, but not
8021 @file{/build/trunk/libcpp/expr.c} or @file{/build/trunk/gcc/x-expr.c}.
8023 @item @var{function}
8024 Specifies the line that begins the body of the function @var{function}.
8025 For example, in C, this is the line with the open brace.
8027 By default, in C@t{++} and Ada, @var{function} is interpreted as
8028 specifying all functions named @var{function} in all scopes. For
8029 C@t{++}, this means in all namespaces and classes. For Ada, this
8030 means in all packages.
8032 For example, assuming a program with C@t{++} symbols named
8033 @code{A::B::func} and @code{B::func}, both commands @w{@kbd{break
8034 func}} and @w{@kbd{break B::func}} set a breakpoint on both symbols.
8036 Commands that accept a linespec let you override this with the
8037 @code{-qualified} option. For example, @w{@kbd{break -qualified
8038 func}} sets a breakpoint on a free-function named @code{func} ignoring
8039 any C@t{++} class methods and namespace functions called @code{func}.
8041 @xref{Explicit Locations}.
8043 @item @var{function}:@var{label}
8044 Specifies the line where @var{label} appears in @var{function}.
8046 @item @var{filename}:@var{function}
8047 Specifies the line that begins the body of the function @var{function}
8048 in the file @var{filename}. You only need the file name with a
8049 function name to avoid ambiguity when there are identically named
8050 functions in different source files.
8053 Specifies the line at which the label named @var{label} appears
8054 in the function corresponding to the currently selected stack frame.
8055 If there is no current selected stack frame (for instance, if the inferior
8056 is not running), then @value{GDBN} will not search for a label.
8058 @cindex breakpoint at static probe point
8059 @item -pstap|-probe-stap @r{[}@var{objfile}:@r{[}@var{provider}:@r{]}@r{]}@var{name}
8060 The @sc{gnu}/Linux tool @code{SystemTap} provides a way for
8061 applications to embed static probes. @xref{Static Probe Points}, for more
8062 information on finding and using static probes. This form of linespec
8063 specifies the location of such a static probe.
8065 If @var{objfile} is given, only probes coming from that shared library
8066 or executable matching @var{objfile} as a regular expression are considered.
8067 If @var{provider} is given, then only probes from that provider are considered.
8068 If several probes match the spec, @value{GDBN} will insert a breakpoint at
8069 each one of those probes.
8072 @node Explicit Locations
8073 @subsection Explicit Locations
8074 @cindex explicit locations
8076 @dfn{Explicit locations} allow the user to directly specify the source
8077 location's parameters using option-value pairs.
8079 Explicit locations are useful when several functions, labels, or
8080 file names have the same name (base name for files) in the program's
8081 sources. In these cases, explicit locations point to the source
8082 line you meant more accurately and unambiguously. Also, using
8083 explicit locations might be faster in large programs.
8085 For example, the linespec @samp{foo:bar} may refer to a function @code{bar}
8086 defined in the file named @file{foo} or the label @code{bar} in a function
8087 named @code{foo}. @value{GDBN} must search either the file system or
8088 the symbol table to know.
8090 The list of valid explicit location options is summarized in the
8094 @item -source @var{filename}
8095 The value specifies the source file name. To differentiate between
8096 files with the same base name, prepend as many directories as is necessary
8097 to uniquely identify the desired file, e.g., @file{foo/bar/baz.c}. Otherwise
8098 @value{GDBN} will use the first file it finds with the given base
8099 name. This option requires the use of either @code{-function} or @code{-line}.
8101 @item -function @var{function}
8102 The value specifies the name of a function. Operations
8103 on function locations unmodified by other options (such as @code{-label}
8104 or @code{-line}) refer to the line that begins the body of the function.
8105 In C, for example, this is the line with the open brace.
8107 By default, in C@t{++} and Ada, @var{function} is interpreted as
8108 specifying all functions named @var{function} in all scopes. For
8109 C@t{++}, this means in all namespaces and classes. For Ada, this
8110 means in all packages.
8112 For example, assuming a program with C@t{++} symbols named
8113 @code{A::B::func} and @code{B::func}, both commands @w{@kbd{break
8114 -function func}} and @w{@kbd{break -function B::func}} set a
8115 breakpoint on both symbols.
8117 You can use the @kbd{-qualified} flag to override this (see below).
8121 This flag makes @value{GDBN} interpret a function name specified with
8122 @kbd{-function} as a complete fully-qualified name.
8124 For example, assuming a C@t{++} program with symbols named
8125 @code{A::B::func} and @code{B::func}, the @w{@kbd{break -qualified
8126 -function B::func}} command sets a breakpoint on @code{B::func}, only.
8128 (Note: the @kbd{-qualified} option can precede a linespec as well
8129 (@pxref{Linespec Locations}), so the particular example above could be
8130 simplified as @w{@kbd{break -qualified B::func}}.)
8132 @item -label @var{label}
8133 The value specifies the name of a label. When the function
8134 name is not specified, the label is searched in the function of the currently
8135 selected stack frame.
8137 @item -line @var{number}
8138 The value specifies a line offset for the location. The offset may either
8139 be absolute (@code{-line 3}) or relative (@code{-line +3}), depending on
8140 the command. When specified without any other options, the line offset is
8141 relative to the current line.
8144 Explicit location options may be abbreviated by omitting any non-unique
8145 trailing characters from the option name, e.g., @w{@kbd{break -s main.c -li 3}}.
8147 @node Address Locations
8148 @subsection Address Locations
8149 @cindex address locations
8151 @dfn{Address locations} indicate a specific program address. They have
8152 the generalized form *@var{address}.
8154 For line-oriented commands, such as @code{list} and @code{edit}, this
8155 specifies a source line that contains @var{address}. For @code{break} and
8156 other breakpoint-oriented commands, this can be used to set breakpoints in
8157 parts of your program which do not have debugging information or
8160 Here @var{address} may be any expression valid in the current working
8161 language (@pxref{Languages, working language}) that specifies a code
8162 address. In addition, as a convenience, @value{GDBN} extends the
8163 semantics of expressions used in locations to cover several situations
8164 that frequently occur during debugging. Here are the various forms
8168 @item @var{expression}
8169 Any expression valid in the current working language.
8171 @item @var{funcaddr}
8172 An address of a function or procedure derived from its name. In C,
8173 C@t{++}, Objective-C, Fortran, minimal, and assembly, this is
8174 simply the function's name @var{function} (and actually a special case
8175 of a valid expression). In Pascal and Modula-2, this is
8176 @code{&@var{function}}. In Ada, this is @code{@var{function}'Address}
8177 (although the Pascal form also works).
8179 This form specifies the address of the function's first instruction,
8180 before the stack frame and arguments have been set up.
8182 @item '@var{filename}':@var{funcaddr}
8183 Like @var{funcaddr} above, but also specifies the name of the source
8184 file explicitly. This is useful if the name of the function does not
8185 specify the function unambiguously, e.g., if there are several
8186 functions with identical names in different source files.
8190 @section Editing Source Files
8191 @cindex editing source files
8194 @kindex e @r{(@code{edit})}
8195 To edit the lines in a source file, use the @code{edit} command.
8196 The editing program of your choice
8197 is invoked with the current line set to
8198 the active line in the program.
8199 Alternatively, there are several ways to specify what part of the file you
8200 want to print if you want to see other parts of the program:
8203 @item edit @var{location}
8204 Edit the source file specified by @code{location}. Editing starts at
8205 that @var{location}, e.g., at the specified source line of the
8206 specified file. @xref{Specify Location}, for all the possible forms
8207 of the @var{location} argument; here are the forms of the @code{edit}
8208 command most commonly used:
8211 @item edit @var{number}
8212 Edit the current source file with @var{number} as the active line number.
8214 @item edit @var{function}
8215 Edit the file containing @var{function} at the beginning of its definition.
8220 @subsection Choosing your Editor
8221 You can customize @value{GDBN} to use any editor you want
8223 The only restriction is that your editor (say @code{ex}), recognizes the
8224 following command-line syntax:
8226 ex +@var{number} file
8228 The optional numeric value +@var{number} specifies the number of the line in
8229 the file where to start editing.}.
8230 By default, it is @file{@value{EDITOR}}, but you can change this
8231 by setting the environment variable @code{EDITOR} before using
8232 @value{GDBN}. For example, to configure @value{GDBN} to use the
8233 @code{vi} editor, you could use these commands with the @code{sh} shell:
8239 or in the @code{csh} shell,
8241 setenv EDITOR /usr/bin/vi
8246 @section Searching Source Files
8247 @cindex searching source files
8249 There are two commands for searching through the current source file for a
8254 @kindex forward-search
8255 @kindex fo @r{(@code{forward-search})}
8256 @item forward-search @var{regexp}
8257 @itemx search @var{regexp}
8258 The command @samp{forward-search @var{regexp}} checks each line,
8259 starting with the one following the last line listed, for a match for
8260 @var{regexp}. It lists the line that is found. You can use the
8261 synonym @samp{search @var{regexp}} or abbreviate the command name as
8264 @kindex reverse-search
8265 @item reverse-search @var{regexp}
8266 The command @samp{reverse-search @var{regexp}} checks each line, starting
8267 with the one before the last line listed and going backward, for a match
8268 for @var{regexp}. It lists the line that is found. You can abbreviate
8269 this command as @code{rev}.
8273 @section Specifying Source Directories
8276 @cindex directories for source files
8277 Executable programs sometimes do not record the directories of the source
8278 files from which they were compiled, just the names. Even when they do,
8279 the directories could be moved between the compilation and your debugging
8280 session. @value{GDBN} has a list of directories to search for source files;
8281 this is called the @dfn{source path}. Each time @value{GDBN} wants a source file,
8282 it tries all the directories in the list, in the order they are present
8283 in the list, until it finds a file with the desired name.
8285 For example, suppose an executable references the file
8286 @file{/usr/src/foo-1.0/lib/foo.c}, and our source path is
8287 @file{/mnt/cross}. The file is first looked up literally; if this
8288 fails, @file{/mnt/cross/usr/src/foo-1.0/lib/foo.c} is tried; if this
8289 fails, @file{/mnt/cross/foo.c} is opened; if this fails, an error
8290 message is printed. @value{GDBN} does not look up the parts of the
8291 source file name, such as @file{/mnt/cross/src/foo-1.0/lib/foo.c}.
8292 Likewise, the subdirectories of the source path are not searched: if
8293 the source path is @file{/mnt/cross}, and the binary refers to
8294 @file{foo.c}, @value{GDBN} would not find it under
8295 @file{/mnt/cross/usr/src/foo-1.0/lib}.
8297 Plain file names, relative file names with leading directories, file
8298 names containing dots, etc.@: are all treated as described above; for
8299 instance, if the source path is @file{/mnt/cross}, and the source file
8300 is recorded as @file{../lib/foo.c}, @value{GDBN} would first try
8301 @file{../lib/foo.c}, then @file{/mnt/cross/../lib/foo.c}, and after
8302 that---@file{/mnt/cross/foo.c}.
8304 Note that the executable search path is @emph{not} used to locate the
8307 Whenever you reset or rearrange the source path, @value{GDBN} clears out
8308 any information it has cached about where source files are found and where
8309 each line is in the file.
8313 When you start @value{GDBN}, its source path includes only @samp{cdir}
8314 and @samp{cwd}, in that order.
8315 To add other directories, use the @code{directory} command.
8317 The search path is used to find both program source files and @value{GDBN}
8318 script files (read using the @samp{-command} option and @samp{source} command).
8320 In addition to the source path, @value{GDBN} provides a set of commands
8321 that manage a list of source path substitution rules. A @dfn{substitution
8322 rule} specifies how to rewrite source directories stored in the program's
8323 debug information in case the sources were moved to a different
8324 directory between compilation and debugging. A rule is made of
8325 two strings, the first specifying what needs to be rewritten in
8326 the path, and the second specifying how it should be rewritten.
8327 In @ref{set substitute-path}, we name these two parts @var{from} and
8328 @var{to} respectively. @value{GDBN} does a simple string replacement
8329 of @var{from} with @var{to} at the start of the directory part of the
8330 source file name, and uses that result instead of the original file
8331 name to look up the sources.
8333 Using the previous example, suppose the @file{foo-1.0} tree has been
8334 moved from @file{/usr/src} to @file{/mnt/cross}, then you can tell
8335 @value{GDBN} to replace @file{/usr/src} in all source path names with
8336 @file{/mnt/cross}. The first lookup will then be
8337 @file{/mnt/cross/foo-1.0/lib/foo.c} in place of the original location
8338 of @file{/usr/src/foo-1.0/lib/foo.c}. To define a source path
8339 substitution rule, use the @code{set substitute-path} command
8340 (@pxref{set substitute-path}).
8342 To avoid unexpected substitution results, a rule is applied only if the
8343 @var{from} part of the directory name ends at a directory separator.
8344 For instance, a rule substituting @file{/usr/source} into
8345 @file{/mnt/cross} will be applied to @file{/usr/source/foo-1.0} but
8346 not to @file{/usr/sourceware/foo-2.0}. And because the substitution
8347 is applied only at the beginning of the directory name, this rule will
8348 not be applied to @file{/root/usr/source/baz.c} either.
8350 In many cases, you can achieve the same result using the @code{directory}
8351 command. However, @code{set substitute-path} can be more efficient in
8352 the case where the sources are organized in a complex tree with multiple
8353 subdirectories. With the @code{directory} command, you need to add each
8354 subdirectory of your project. If you moved the entire tree while
8355 preserving its internal organization, then @code{set substitute-path}
8356 allows you to direct the debugger to all the sources with one single
8359 @code{set substitute-path} is also more than just a shortcut command.
8360 The source path is only used if the file at the original location no
8361 longer exists. On the other hand, @code{set substitute-path} modifies
8362 the debugger behavior to look at the rewritten location instead. So, if
8363 for any reason a source file that is not relevant to your executable is
8364 located at the original location, a substitution rule is the only
8365 method available to point @value{GDBN} at the new location.
8367 @cindex @samp{--with-relocated-sources}
8368 @cindex default source path substitution
8369 You can configure a default source path substitution rule by
8370 configuring @value{GDBN} with the
8371 @samp{--with-relocated-sources=@var{dir}} option. The @var{dir}
8372 should be the name of a directory under @value{GDBN}'s configured
8373 prefix (set with @samp{--prefix} or @samp{--exec-prefix}), and
8374 directory names in debug information under @var{dir} will be adjusted
8375 automatically if the installed @value{GDBN} is moved to a new
8376 location. This is useful if @value{GDBN}, libraries or executables
8377 with debug information and corresponding source code are being moved
8381 @item directory @var{dirname} @dots{}
8382 @item dir @var{dirname} @dots{}
8383 Add directory @var{dirname} to the front of the source path. Several
8384 directory names may be given to this command, separated by @samp{:}
8385 (@samp{;} on MS-DOS and MS-Windows, where @samp{:} usually appears as
8386 part of absolute file names) or
8387 whitespace. You may specify a directory that is already in the source
8388 path; this moves it forward, so @value{GDBN} searches it sooner.
8392 @vindex $cdir@r{, convenience variable}
8393 @vindex $cwd@r{, convenience variable}
8394 @cindex compilation directory
8395 @cindex current directory
8396 @cindex working directory
8397 @cindex directory, current
8398 @cindex directory, compilation
8399 You can use the string @samp{$cdir} to refer to the compilation
8400 directory (if one is recorded), and @samp{$cwd} to refer to the current
8401 working directory. @samp{$cwd} is not the same as @samp{.}---the former
8402 tracks the current working directory as it changes during your @value{GDBN}
8403 session, while the latter is immediately expanded to the current
8404 directory at the time you add an entry to the source path.
8407 Reset the source path to its default value (@samp{$cdir:$cwd} on Unix systems). This requires confirmation.
8409 @c RET-repeat for @code{directory} is explicitly disabled, but since
8410 @c repeating it would be a no-op we do not say that. (thanks to RMS)
8412 @item set directories @var{path-list}
8413 @kindex set directories
8414 Set the source path to @var{path-list}.
8415 @samp{$cdir:$cwd} are added if missing.
8417 @item show directories
8418 @kindex show directories
8419 Print the source path: show which directories it contains.
8421 @anchor{set substitute-path}
8422 @item set substitute-path @var{from} @var{to}
8423 @kindex set substitute-path
8424 Define a source path substitution rule, and add it at the end of the
8425 current list of existing substitution rules. If a rule with the same
8426 @var{from} was already defined, then the old rule is also deleted.
8428 For example, if the file @file{/foo/bar/baz.c} was moved to
8429 @file{/mnt/cross/baz.c}, then the command
8432 (@value{GDBP}) set substitute-path /foo/bar /mnt/cross
8436 will tell @value{GDBN} to replace @samp{/foo/bar} with
8437 @samp{/mnt/cross}, which will allow @value{GDBN} to find the file
8438 @file{baz.c} even though it was moved.
8440 In the case when more than one substitution rule have been defined,
8441 the rules are evaluated one by one in the order where they have been
8442 defined. The first one matching, if any, is selected to perform
8445 For instance, if we had entered the following commands:
8448 (@value{GDBP}) set substitute-path /usr/src/include /mnt/include
8449 (@value{GDBP}) set substitute-path /usr/src /mnt/src
8453 @value{GDBN} would then rewrite @file{/usr/src/include/defs.h} into
8454 @file{/mnt/include/defs.h} by using the first rule. However, it would
8455 use the second rule to rewrite @file{/usr/src/lib/foo.c} into
8456 @file{/mnt/src/lib/foo.c}.
8459 @item unset substitute-path [path]
8460 @kindex unset substitute-path
8461 If a path is specified, search the current list of substitution rules
8462 for a rule that would rewrite that path. Delete that rule if found.
8463 A warning is emitted by the debugger if no rule could be found.
8465 If no path is specified, then all substitution rules are deleted.
8467 @item show substitute-path [path]
8468 @kindex show substitute-path
8469 If a path is specified, then print the source path substitution rule
8470 which would rewrite that path, if any.
8472 If no path is specified, then print all existing source path substitution
8477 If your source path is cluttered with directories that are no longer of
8478 interest, @value{GDBN} may sometimes cause confusion by finding the wrong
8479 versions of source. You can correct the situation as follows:
8483 Use @code{directory} with no argument to reset the source path to its default value.
8486 Use @code{directory} with suitable arguments to reinstall the
8487 directories you want in the source path. You can add all the
8488 directories in one command.
8492 @section Source and Machine Code
8493 @cindex source line and its code address
8495 You can use the command @code{info line} to map source lines to program
8496 addresses (and vice versa), and the command @code{disassemble} to display
8497 a range of addresses as machine instructions. You can use the command
8498 @code{set disassemble-next-line} to set whether to disassemble next
8499 source line when execution stops. When run under @sc{gnu} Emacs
8500 mode, the @code{info line} command causes the arrow to point to the
8501 line specified. Also, @code{info line} prints addresses in symbolic form as
8507 @itemx info line @var{location}
8508 Print the starting and ending addresses of the compiled code for
8509 source line @var{location}. You can specify source lines in any of
8510 the ways documented in @ref{Specify Location}. With no @var{location}
8511 information about the current source line is printed.
8514 For example, we can use @code{info line} to discover the location of
8515 the object code for the first line of function
8516 @code{m4_changequote}:
8519 (@value{GDBP}) info line m4_changequote
8520 Line 895 of "builtin.c" starts at pc 0x634c <m4_changequote> and \
8521 ends at 0x6350 <m4_changequote+4>.
8525 @cindex code address and its source line
8526 We can also inquire (using @code{*@var{addr}} as the form for
8527 @var{location}) what source line covers a particular address:
8529 (@value{GDBP}) info line *0x63ff
8530 Line 926 of "builtin.c" starts at pc 0x63e4 <m4_changequote+152> and \
8531 ends at 0x6404 <m4_changequote+184>.
8534 @cindex @code{$_} and @code{info line}
8535 @cindex @code{x} command, default address
8536 @kindex x@r{(examine), and} info line
8537 After @code{info line}, the default address for the @code{x} command
8538 is changed to the starting address of the line, so that @samp{x/i} is
8539 sufficient to begin examining the machine code (@pxref{Memory,
8540 ,Examining Memory}). Also, this address is saved as the value of the
8541 convenience variable @code{$_} (@pxref{Convenience Vars, ,Convenience
8544 @cindex info line, repeated calls
8545 After @code{info line}, using @code{info line} again without
8546 specifying a location will display information about the next source
8551 @cindex assembly instructions
8552 @cindex instructions, assembly
8553 @cindex machine instructions
8554 @cindex listing machine instructions
8556 @itemx disassemble /m
8557 @itemx disassemble /s
8558 @itemx disassemble /r
8559 This specialized command dumps a range of memory as machine
8560 instructions. It can also print mixed source+disassembly by specifying
8561 the @code{/m} or @code{/s} modifier and print the raw instructions in hex
8562 as well as in symbolic form by specifying the @code{/r} modifier.
8563 The default memory range is the function surrounding the
8564 program counter of the selected frame. A single argument to this
8565 command is a program counter value; @value{GDBN} dumps the function
8566 surrounding this value. When two arguments are given, they should
8567 be separated by a comma, possibly surrounded by whitespace. The
8568 arguments specify a range of addresses to dump, in one of two forms:
8571 @item @var{start},@var{end}
8572 the addresses from @var{start} (inclusive) to @var{end} (exclusive)
8573 @item @var{start},+@var{length}
8574 the addresses from @var{start} (inclusive) to
8575 @code{@var{start}+@var{length}} (exclusive).
8579 When 2 arguments are specified, the name of the function is also
8580 printed (since there could be several functions in the given range).
8582 The argument(s) can be any expression yielding a numeric value, such as
8583 @samp{0x32c4}, @samp{&main+10} or @samp{$pc - 8}.
8585 If the range of memory being disassembled contains current program counter,
8586 the instruction at that location is shown with a @code{=>} marker.
8589 The following example shows the disassembly of a range of addresses of
8590 HP PA-RISC 2.0 code:
8593 (@value{GDBP}) disas 0x32c4, 0x32e4
8594 Dump of assembler code from 0x32c4 to 0x32e4:
8595 0x32c4 <main+204>: addil 0,dp
8596 0x32c8 <main+208>: ldw 0x22c(sr0,r1),r26
8597 0x32cc <main+212>: ldil 0x3000,r31
8598 0x32d0 <main+216>: ble 0x3f8(sr4,r31)
8599 0x32d4 <main+220>: ldo 0(r31),rp
8600 0x32d8 <main+224>: addil -0x800,dp
8601 0x32dc <main+228>: ldo 0x588(r1),r26
8602 0x32e0 <main+232>: ldil 0x3000,r31
8603 End of assembler dump.
8606 Here is an example showing mixed source+assembly for Intel x86
8607 with @code{/m} or @code{/s}, when the program is stopped just after
8608 function prologue in a non-optimized function with no inline code.
8611 (@value{GDBP}) disas /m main
8612 Dump of assembler code for function main:
8614 0x08048330 <+0>: push %ebp
8615 0x08048331 <+1>: mov %esp,%ebp
8616 0x08048333 <+3>: sub $0x8,%esp
8617 0x08048336 <+6>: and $0xfffffff0,%esp
8618 0x08048339 <+9>: sub $0x10,%esp
8620 6 printf ("Hello.\n");
8621 => 0x0804833c <+12>: movl $0x8048440,(%esp)
8622 0x08048343 <+19>: call 0x8048284 <puts@@plt>
8626 0x08048348 <+24>: mov $0x0,%eax
8627 0x0804834d <+29>: leave
8628 0x0804834e <+30>: ret
8630 End of assembler dump.
8633 The @code{/m} option is deprecated as its output is not useful when
8634 there is either inlined code or re-ordered code.
8635 The @code{/s} option is the preferred choice.
8636 Here is an example for AMD x86-64 showing the difference between
8637 @code{/m} output and @code{/s} output.
8638 This example has one inline function defined in a header file,
8639 and the code is compiled with @samp{-O2} optimization.
8640 Note how the @code{/m} output is missing the disassembly of
8641 several instructions that are present in the @code{/s} output.
8671 (@value{GDBP}) disas /m main
8672 Dump of assembler code for function main:
8676 0x0000000000400400 <+0>: mov 0x200c2e(%rip),%eax # 0x601034 <y>
8677 0x0000000000400417 <+23>: mov %eax,0x200c13(%rip) # 0x601030 <x>
8681 0x000000000040041d <+29>: xor %eax,%eax
8682 0x000000000040041f <+31>: retq
8683 0x0000000000400420 <+32>: add %eax,%eax
8684 0x0000000000400422 <+34>: jmp 0x400417 <main+23>
8686 End of assembler dump.
8687 (@value{GDBP}) disas /s main
8688 Dump of assembler code for function main:
8692 0x0000000000400400 <+0>: mov 0x200c2e(%rip),%eax # 0x601034 <y>
8696 0x0000000000400406 <+6>: test %eax,%eax
8697 0x0000000000400408 <+8>: js 0x400420 <main+32>
8702 0x000000000040040a <+10>: lea 0xa(%rax),%edx
8703 0x000000000040040d <+13>: test %eax,%eax
8704 0x000000000040040f <+15>: mov $0x1,%eax
8705 0x0000000000400414 <+20>: cmovne %edx,%eax
8709 0x0000000000400417 <+23>: mov %eax,0x200c13(%rip) # 0x601030 <x>
8713 0x000000000040041d <+29>: xor %eax,%eax
8714 0x000000000040041f <+31>: retq
8718 0x0000000000400420 <+32>: add %eax,%eax
8719 0x0000000000400422 <+34>: jmp 0x400417 <main+23>
8720 End of assembler dump.
8723 Here is another example showing raw instructions in hex for AMD x86-64,
8726 (gdb) disas /r 0x400281,+10
8727 Dump of assembler code from 0x400281 to 0x40028b:
8728 0x0000000000400281: 38 36 cmp %dh,(%rsi)
8729 0x0000000000400283: 2d 36 34 2e 73 sub $0x732e3436,%eax
8730 0x0000000000400288: 6f outsl %ds:(%rsi),(%dx)
8731 0x0000000000400289: 2e 32 00 xor %cs:(%rax),%al
8732 End of assembler dump.
8735 Addresses cannot be specified as a location (@pxref{Specify Location}).
8736 So, for example, if you want to disassemble function @code{bar}
8737 in file @file{foo.c}, you must type @samp{disassemble 'foo.c'::bar}
8738 and not @samp{disassemble foo.c:bar}.
8740 Some architectures have more than one commonly-used set of instruction
8741 mnemonics or other syntax.
8743 For programs that were dynamically linked and use shared libraries,
8744 instructions that call functions or branch to locations in the shared
8745 libraries might show a seemingly bogus location---it's actually a
8746 location of the relocation table. On some architectures, @value{GDBN}
8747 might be able to resolve these to actual function names.
8750 @kindex set disassembler-options
8751 @cindex disassembler options
8752 @item set disassembler-options @var{option1}[,@var{option2}@dots{}]
8753 This command controls the passing of target specific information to
8754 the disassembler. For a list of valid options, please refer to the
8755 @code{-M}/@code{--disassembler-options} section of the @samp{objdump}
8756 manual and/or the output of @kbd{objdump --help}
8757 (@pxref{objdump,,objdump,binutils.info,The GNU Binary Utilities}).
8758 The default value is the empty string.
8760 If it is necessary to specify more than one disassembler option, then
8761 multiple options can be placed together into a comma separated list.
8762 Currently this command is only supported on targets ARM, PowerPC
8765 @kindex show disassembler-options
8766 @item show disassembler-options
8767 Show the current setting of the disassembler options.
8771 @kindex set disassembly-flavor
8772 @cindex Intel disassembly flavor
8773 @cindex AT&T disassembly flavor
8774 @item set disassembly-flavor @var{instruction-set}
8775 Select the instruction set to use when disassembling the
8776 program via the @code{disassemble} or @code{x/i} commands.
8778 Currently this command is only defined for the Intel x86 family. You
8779 can set @var{instruction-set} to either @code{intel} or @code{att}.
8780 The default is @code{att}, the AT&T flavor used by default by Unix
8781 assemblers for x86-based targets.
8783 @kindex show disassembly-flavor
8784 @item show disassembly-flavor
8785 Show the current setting of the disassembly flavor.
8789 @kindex set disassemble-next-line
8790 @kindex show disassemble-next-line
8791 @item set disassemble-next-line
8792 @itemx show disassemble-next-line
8793 Control whether or not @value{GDBN} will disassemble the next source
8794 line or instruction when execution stops. If ON, @value{GDBN} will
8795 display disassembly of the next source line when execution of the
8796 program being debugged stops. This is @emph{in addition} to
8797 displaying the source line itself, which @value{GDBN} always does if
8798 possible. If the next source line cannot be displayed for some reason
8799 (e.g., if @value{GDBN} cannot find the source file, or there's no line
8800 info in the debug info), @value{GDBN} will display disassembly of the
8801 next @emph{instruction} instead of showing the next source line. If
8802 AUTO, @value{GDBN} will display disassembly of next instruction only
8803 if the source line cannot be displayed. This setting causes
8804 @value{GDBN} to display some feedback when you step through a function
8805 with no line info or whose source file is unavailable. The default is
8806 OFF, which means never display the disassembly of the next line or
8812 @chapter Examining Data
8814 @cindex printing data
8815 @cindex examining data
8818 The usual way to examine data in your program is with the @code{print}
8819 command (abbreviated @code{p}), or its synonym @code{inspect}. It
8820 evaluates and prints the value of an expression of the language your
8821 program is written in (@pxref{Languages, ,Using @value{GDBN} with
8822 Different Languages}). It may also print the expression using a
8823 Python-based pretty-printer (@pxref{Pretty Printing}).
8826 @item print @var{expr}
8827 @itemx print /@var{f} @var{expr}
8828 @var{expr} is an expression (in the source language). By default the
8829 value of @var{expr} is printed in a format appropriate to its data type;
8830 you can choose a different format by specifying @samp{/@var{f}}, where
8831 @var{f} is a letter specifying the format; see @ref{Output Formats,,Output
8835 @itemx print /@var{f}
8836 @cindex reprint the last value
8837 If you omit @var{expr}, @value{GDBN} displays the last value again (from the
8838 @dfn{value history}; @pxref{Value History, ,Value History}). This allows you to
8839 conveniently inspect the same value in an alternative format.
8842 A more low-level way of examining data is with the @code{x} command.
8843 It examines data in memory at a specified address and prints it in a
8844 specified format. @xref{Memory, ,Examining Memory}.
8846 If you are interested in information about types, or about how the
8847 fields of a struct or a class are declared, use the @code{ptype @var{exp}}
8848 command rather than @code{print}. @xref{Symbols, ,Examining the Symbol
8851 @cindex exploring hierarchical data structures
8853 Another way of examining values of expressions and type information is
8854 through the Python extension command @code{explore} (available only if
8855 the @value{GDBN} build is configured with @code{--with-python}). It
8856 offers an interactive way to start at the highest level (or, the most
8857 abstract level) of the data type of an expression (or, the data type
8858 itself) and explore all the way down to leaf scalar values/fields
8859 embedded in the higher level data types.
8862 @item explore @var{arg}
8863 @var{arg} is either an expression (in the source language), or a type
8864 visible in the current context of the program being debugged.
8867 The working of the @code{explore} command can be illustrated with an
8868 example. If a data type @code{struct ComplexStruct} is defined in your
8878 struct ComplexStruct
8880 struct SimpleStruct *ss_p;
8886 followed by variable declarations as
8889 struct SimpleStruct ss = @{ 10, 1.11 @};
8890 struct ComplexStruct cs = @{ &ss, @{ 0, 1, 2, 3, 4, 5, 6, 7, 8, 9 @} @};
8894 then, the value of the variable @code{cs} can be explored using the
8895 @code{explore} command as follows.
8899 The value of `cs' is a struct/class of type `struct ComplexStruct' with
8900 the following fields:
8902 ss_p = <Enter 0 to explore this field of type `struct SimpleStruct *'>
8903 arr = <Enter 1 to explore this field of type `int [10]'>
8905 Enter the field number of choice:
8909 Since the fields of @code{cs} are not scalar values, you are being
8910 prompted to chose the field you want to explore. Let's say you choose
8911 the field @code{ss_p} by entering @code{0}. Then, since this field is a
8912 pointer, you will be asked if it is pointing to a single value. From
8913 the declaration of @code{cs} above, it is indeed pointing to a single
8914 value, hence you enter @code{y}. If you enter @code{n}, then you will
8915 be asked if it were pointing to an array of values, in which case this
8916 field will be explored as if it were an array.
8919 `cs.ss_p' is a pointer to a value of type `struct SimpleStruct'
8920 Continue exploring it as a pointer to a single value [y/n]: y
8921 The value of `*(cs.ss_p)' is a struct/class of type `struct
8922 SimpleStruct' with the following fields:
8924 i = 10 .. (Value of type `int')
8925 d = 1.1100000000000001 .. (Value of type `double')
8927 Press enter to return to parent value:
8931 If the field @code{arr} of @code{cs} was chosen for exploration by
8932 entering @code{1} earlier, then since it is as array, you will be
8933 prompted to enter the index of the element in the array that you want
8937 `cs.arr' is an array of `int'.
8938 Enter the index of the element you want to explore in `cs.arr': 5
8940 `(cs.arr)[5]' is a scalar value of type `int'.
8944 Press enter to return to parent value:
8947 In general, at any stage of exploration, you can go deeper towards the
8948 leaf values by responding to the prompts appropriately, or hit the
8949 return key to return to the enclosing data structure (the @i{higher}
8950 level data structure).
8952 Similar to exploring values, you can use the @code{explore} command to
8953 explore types. Instead of specifying a value (which is typically a
8954 variable name or an expression valid in the current context of the
8955 program being debugged), you specify a type name. If you consider the
8956 same example as above, your can explore the type
8957 @code{struct ComplexStruct} by passing the argument
8958 @code{struct ComplexStruct} to the @code{explore} command.
8961 (gdb) explore struct ComplexStruct
8965 By responding to the prompts appropriately in the subsequent interactive
8966 session, you can explore the type @code{struct ComplexStruct} in a
8967 manner similar to how the value @code{cs} was explored in the above
8970 The @code{explore} command also has two sub-commands,
8971 @code{explore value} and @code{explore type}. The former sub-command is
8972 a way to explicitly specify that value exploration of the argument is
8973 being invoked, while the latter is a way to explicitly specify that type
8974 exploration of the argument is being invoked.
8977 @item explore value @var{expr}
8978 @cindex explore value
8979 This sub-command of @code{explore} explores the value of the
8980 expression @var{expr} (if @var{expr} is an expression valid in the
8981 current context of the program being debugged). The behavior of this
8982 command is identical to that of the behavior of the @code{explore}
8983 command being passed the argument @var{expr}.
8985 @item explore type @var{arg}
8986 @cindex explore type
8987 This sub-command of @code{explore} explores the type of @var{arg} (if
8988 @var{arg} is a type visible in the current context of program being
8989 debugged), or the type of the value/expression @var{arg} (if @var{arg}
8990 is an expression valid in the current context of the program being
8991 debugged). If @var{arg} is a type, then the behavior of this command is
8992 identical to that of the @code{explore} command being passed the
8993 argument @var{arg}. If @var{arg} is an expression, then the behavior of
8994 this command will be identical to that of the @code{explore} command
8995 being passed the type of @var{arg} as the argument.
8999 * Expressions:: Expressions
9000 * Ambiguous Expressions:: Ambiguous Expressions
9001 * Variables:: Program variables
9002 * Arrays:: Artificial arrays
9003 * Output Formats:: Output formats
9004 * Memory:: Examining memory
9005 * Auto Display:: Automatic display
9006 * Print Settings:: Print settings
9007 * Pretty Printing:: Python pretty printing
9008 * Value History:: Value history
9009 * Convenience Vars:: Convenience variables
9010 * Convenience Funs:: Convenience functions
9011 * Registers:: Registers
9012 * Floating Point Hardware:: Floating point hardware
9013 * Vector Unit:: Vector Unit
9014 * OS Information:: Auxiliary data provided by operating system
9015 * Memory Region Attributes:: Memory region attributes
9016 * Dump/Restore Files:: Copy between memory and a file
9017 * Core File Generation:: Cause a program dump its core
9018 * Character Sets:: Debugging programs that use a different
9019 character set than GDB does
9020 * Caching Target Data:: Data caching for targets
9021 * Searching Memory:: Searching memory for a sequence of bytes
9022 * Value Sizes:: Managing memory allocated for values
9026 @section Expressions
9029 @code{print} and many other @value{GDBN} commands accept an expression and
9030 compute its value. Any kind of constant, variable or operator defined
9031 by the programming language you are using is valid in an expression in
9032 @value{GDBN}. This includes conditional expressions, function calls,
9033 casts, and string constants. It also includes preprocessor macros, if
9034 you compiled your program to include this information; see
9037 @cindex arrays in expressions
9038 @value{GDBN} supports array constants in expressions input by
9039 the user. The syntax is @{@var{element}, @var{element}@dots{}@}. For example,
9040 you can use the command @code{print @{1, 2, 3@}} to create an array
9041 of three integers. If you pass an array to a function or assign it
9042 to a program variable, @value{GDBN} copies the array to memory that
9043 is @code{malloc}ed in the target program.
9045 Because C is so widespread, most of the expressions shown in examples in
9046 this manual are in C. @xref{Languages, , Using @value{GDBN} with Different
9047 Languages}, for information on how to use expressions in other
9050 In this section, we discuss operators that you can use in @value{GDBN}
9051 expressions regardless of your programming language.
9053 @cindex casts, in expressions
9054 Casts are supported in all languages, not just in C, because it is so
9055 useful to cast a number into a pointer in order to examine a structure
9056 at that address in memory.
9057 @c FIXME: casts supported---Mod2 true?
9059 @value{GDBN} supports these operators, in addition to those common
9060 to programming languages:
9064 @samp{@@} is a binary operator for treating parts of memory as arrays.
9065 @xref{Arrays, ,Artificial Arrays}, for more information.
9068 @samp{::} allows you to specify a variable in terms of the file or
9069 function where it is defined. @xref{Variables, ,Program Variables}.
9071 @cindex @{@var{type}@}
9072 @cindex type casting memory
9073 @cindex memory, viewing as typed object
9074 @cindex casts, to view memory
9075 @item @{@var{type}@} @var{addr}
9076 Refers to an object of type @var{type} stored at address @var{addr} in
9077 memory. The address @var{addr} may be any expression whose value is
9078 an integer or pointer (but parentheses are required around binary
9079 operators, just as in a cast). This construct is allowed regardless
9080 of what kind of data is normally supposed to reside at @var{addr}.
9083 @node Ambiguous Expressions
9084 @section Ambiguous Expressions
9085 @cindex ambiguous expressions
9087 Expressions can sometimes contain some ambiguous elements. For instance,
9088 some programming languages (notably Ada, C@t{++} and Objective-C) permit
9089 a single function name to be defined several times, for application in
9090 different contexts. This is called @dfn{overloading}. Another example
9091 involving Ada is generics. A @dfn{generic package} is similar to C@t{++}
9092 templates and is typically instantiated several times, resulting in
9093 the same function name being defined in different contexts.
9095 In some cases and depending on the language, it is possible to adjust
9096 the expression to remove the ambiguity. For instance in C@t{++}, you
9097 can specify the signature of the function you want to break on, as in
9098 @kbd{break @var{function}(@var{types})}. In Ada, using the fully
9099 qualified name of your function often makes the expression unambiguous
9102 When an ambiguity that needs to be resolved is detected, the debugger
9103 has the capability to display a menu of numbered choices for each
9104 possibility, and then waits for the selection with the prompt @samp{>}.
9105 The first option is always @samp{[0] cancel}, and typing @kbd{0 @key{RET}}
9106 aborts the current command. If the command in which the expression was
9107 used allows more than one choice to be selected, the next option in the
9108 menu is @samp{[1] all}, and typing @kbd{1 @key{RET}} selects all possible
9111 For example, the following session excerpt shows an attempt to set a
9112 breakpoint at the overloaded symbol @code{String::after}.
9113 We choose three particular definitions of that function name:
9115 @c FIXME! This is likely to change to show arg type lists, at least
9118 (@value{GDBP}) b String::after
9121 [2] file:String.cc; line number:867
9122 [3] file:String.cc; line number:860
9123 [4] file:String.cc; line number:875
9124 [5] file:String.cc; line number:853
9125 [6] file:String.cc; line number:846
9126 [7] file:String.cc; line number:735
9128 Breakpoint 1 at 0xb26c: file String.cc, line 867.
9129 Breakpoint 2 at 0xb344: file String.cc, line 875.
9130 Breakpoint 3 at 0xafcc: file String.cc, line 846.
9131 Multiple breakpoints were set.
9132 Use the "delete" command to delete unwanted
9139 @kindex set multiple-symbols
9140 @item set multiple-symbols @var{mode}
9141 @cindex multiple-symbols menu
9143 This option allows you to adjust the debugger behavior when an expression
9146 By default, @var{mode} is set to @code{all}. If the command with which
9147 the expression is used allows more than one choice, then @value{GDBN}
9148 automatically selects all possible choices. For instance, inserting
9149 a breakpoint on a function using an ambiguous name results in a breakpoint
9150 inserted on each possible match. However, if a unique choice must be made,
9151 then @value{GDBN} uses the menu to help you disambiguate the expression.
9152 For instance, printing the address of an overloaded function will result
9153 in the use of the menu.
9155 When @var{mode} is set to @code{ask}, the debugger always uses the menu
9156 when an ambiguity is detected.
9158 Finally, when @var{mode} is set to @code{cancel}, the debugger reports
9159 an error due to the ambiguity and the command is aborted.
9161 @kindex show multiple-symbols
9162 @item show multiple-symbols
9163 Show the current value of the @code{multiple-symbols} setting.
9167 @section Program Variables
9169 The most common kind of expression to use is the name of a variable
9172 Variables in expressions are understood in the selected stack frame
9173 (@pxref{Selection, ,Selecting a Frame}); they must be either:
9177 global (or file-static)
9184 visible according to the scope rules of the
9185 programming language from the point of execution in that frame
9188 @noindent This means that in the function
9203 you can examine and use the variable @code{a} whenever your program is
9204 executing within the function @code{foo}, but you can only use or
9205 examine the variable @code{b} while your program is executing inside
9206 the block where @code{b} is declared.
9208 @cindex variable name conflict
9209 There is an exception: you can refer to a variable or function whose
9210 scope is a single source file even if the current execution point is not
9211 in this file. But it is possible to have more than one such variable or
9212 function with the same name (in different source files). If that
9213 happens, referring to that name has unpredictable effects. If you wish,
9214 you can specify a static variable in a particular function or file by
9215 using the colon-colon (@code{::}) notation:
9217 @cindex colon-colon, context for variables/functions
9219 @c info cannot cope with a :: index entry, but why deprive hard copy readers?
9220 @cindex @code{::}, context for variables/functions
9223 @var{file}::@var{variable}
9224 @var{function}::@var{variable}
9228 Here @var{file} or @var{function} is the name of the context for the
9229 static @var{variable}. In the case of file names, you can use quotes to
9230 make sure @value{GDBN} parses the file name as a single word---for example,
9231 to print a global value of @code{x} defined in @file{f2.c}:
9234 (@value{GDBP}) p 'f2.c'::x
9237 The @code{::} notation is normally used for referring to
9238 static variables, since you typically disambiguate uses of local variables
9239 in functions by selecting the appropriate frame and using the
9240 simple name of the variable. However, you may also use this notation
9241 to refer to local variables in frames enclosing the selected frame:
9250 process (a); /* Stop here */
9261 For example, if there is a breakpoint at the commented line,
9262 here is what you might see
9263 when the program stops after executing the call @code{bar(0)}:
9268 (@value{GDBP}) p bar::a
9271 #2 0x080483d0 in foo (a=5) at foobar.c:12
9274 (@value{GDBP}) p bar::a
9278 @cindex C@t{++} scope resolution
9279 These uses of @samp{::} are very rarely in conflict with the very
9280 similar use of the same notation in C@t{++}. When they are in
9281 conflict, the C@t{++} meaning takes precedence; however, this can be
9282 overridden by quoting the file or function name with single quotes.
9284 For example, suppose the program is stopped in a method of a class
9285 that has a field named @code{includefile}, and there is also an
9286 include file named @file{includefile} that defines a variable,
9290 (@value{GDBP}) p includefile
9292 (@value{GDBP}) p includefile::some_global
9293 A syntax error in expression, near `'.
9294 (@value{GDBP}) p 'includefile'::some_global
9298 @cindex wrong values
9299 @cindex variable values, wrong
9300 @cindex function entry/exit, wrong values of variables
9301 @cindex optimized code, wrong values of variables
9303 @emph{Warning:} Occasionally, a local variable may appear to have the
9304 wrong value at certain points in a function---just after entry to a new
9305 scope, and just before exit.
9307 You may see this problem when you are stepping by machine instructions.
9308 This is because, on most machines, it takes more than one instruction to
9309 set up a stack frame (including local variable definitions); if you are
9310 stepping by machine instructions, variables may appear to have the wrong
9311 values until the stack frame is completely built. On exit, it usually
9312 also takes more than one machine instruction to destroy a stack frame;
9313 after you begin stepping through that group of instructions, local
9314 variable definitions may be gone.
9316 This may also happen when the compiler does significant optimizations.
9317 To be sure of always seeing accurate values, turn off all optimization
9320 @cindex ``No symbol "foo" in current context''
9321 Another possible effect of compiler optimizations is to optimize
9322 unused variables out of existence, or assign variables to registers (as
9323 opposed to memory addresses). Depending on the support for such cases
9324 offered by the debug info format used by the compiler, @value{GDBN}
9325 might not be able to display values for such local variables. If that
9326 happens, @value{GDBN} will print a message like this:
9329 No symbol "foo" in current context.
9332 To solve such problems, either recompile without optimizations, or use a
9333 different debug info format, if the compiler supports several such
9334 formats. @xref{Compilation}, for more information on choosing compiler
9335 options. @xref{C, ,C and C@t{++}}, for more information about debug
9336 info formats that are best suited to C@t{++} programs.
9338 If you ask to print an object whose contents are unknown to
9339 @value{GDBN}, e.g., because its data type is not completely specified
9340 by the debug information, @value{GDBN} will say @samp{<incomplete
9341 type>}. @xref{Symbols, incomplete type}, for more about this.
9343 @cindex no debug info variables
9344 If you try to examine or use the value of a (global) variable for
9345 which @value{GDBN} has no type information, e.g., because the program
9346 includes no debug information, @value{GDBN} displays an error message.
9347 @xref{Symbols, unknown type}, for more about unknown types. If you
9348 cast the variable to its declared type, @value{GDBN} gets the
9349 variable's value using the cast-to type as the variable's type. For
9350 example, in a C program:
9353 (@value{GDBP}) p var
9354 'var' has unknown type; cast it to its declared type
9355 (@value{GDBP}) p (float) var
9359 If you append @kbd{@@entry} string to a function parameter name you get its
9360 value at the time the function got called. If the value is not available an
9361 error message is printed. Entry values are available only with some compilers.
9362 Entry values are normally also printed at the function parameter list according
9363 to @ref{set print entry-values}.
9366 Breakpoint 1, d (i=30) at gdb.base/entry-value.c:29
9372 (gdb) print i@@entry
9376 Strings are identified as arrays of @code{char} values without specified
9377 signedness. Arrays of either @code{signed char} or @code{unsigned char} get
9378 printed as arrays of 1 byte sized integers. @code{-fsigned-char} or
9379 @code{-funsigned-char} @value{NGCC} options have no effect as @value{GDBN}
9380 defines literal string type @code{"char"} as @code{char} without a sign.
9385 signed char var1[] = "A";
9388 You get during debugging
9393 $2 = @{65 'A', 0 '\0'@}
9397 @section Artificial Arrays
9399 @cindex artificial array
9401 @kindex @@@r{, referencing memory as an array}
9402 It is often useful to print out several successive objects of the
9403 same type in memory; a section of an array, or an array of
9404 dynamically determined size for which only a pointer exists in the
9407 You can do this by referring to a contiguous span of memory as an
9408 @dfn{artificial array}, using the binary operator @samp{@@}. The left
9409 operand of @samp{@@} should be the first element of the desired array
9410 and be an individual object. The right operand should be the desired length
9411 of the array. The result is an array value whose elements are all of
9412 the type of the left argument. The first element is actually the left
9413 argument; the second element comes from bytes of memory immediately
9414 following those that hold the first element, and so on. Here is an
9415 example. If a program says
9418 int *array = (int *) malloc (len * sizeof (int));
9422 you can print the contents of @code{array} with
9428 The left operand of @samp{@@} must reside in memory. Array values made
9429 with @samp{@@} in this way behave just like other arrays in terms of
9430 subscripting, and are coerced to pointers when used in expressions.
9431 Artificial arrays most often appear in expressions via the value history
9432 (@pxref{Value History, ,Value History}), after printing one out.
9434 Another way to create an artificial array is to use a cast.
9435 This re-interprets a value as if it were an array.
9436 The value need not be in memory:
9438 (@value{GDBP}) p/x (short[2])0x12345678
9439 $1 = @{0x1234, 0x5678@}
9442 As a convenience, if you leave the array length out (as in
9443 @samp{(@var{type}[])@var{value}}) @value{GDBN} calculates the size to fill
9444 the value (as @samp{sizeof(@var{value})/sizeof(@var{type})}:
9446 (@value{GDBP}) p/x (short[])0x12345678
9447 $2 = @{0x1234, 0x5678@}
9450 Sometimes the artificial array mechanism is not quite enough; in
9451 moderately complex data structures, the elements of interest may not
9452 actually be adjacent---for example, if you are interested in the values
9453 of pointers in an array. One useful work-around in this situation is
9454 to use a convenience variable (@pxref{Convenience Vars, ,Convenience
9455 Variables}) as a counter in an expression that prints the first
9456 interesting value, and then repeat that expression via @key{RET}. For
9457 instance, suppose you have an array @code{dtab} of pointers to
9458 structures, and you are interested in the values of a field @code{fv}
9459 in each structure. Here is an example of what you might type:
9469 @node Output Formats
9470 @section Output Formats
9472 @cindex formatted output
9473 @cindex output formats
9474 By default, @value{GDBN} prints a value according to its data type. Sometimes
9475 this is not what you want. For example, you might want to print a number
9476 in hex, or a pointer in decimal. Or you might want to view data in memory
9477 at a certain address as a character string or as an instruction. To do
9478 these things, specify an @dfn{output format} when you print a value.
9480 The simplest use of output formats is to say how to print a value
9481 already computed. This is done by starting the arguments of the
9482 @code{print} command with a slash and a format letter. The format
9483 letters supported are:
9487 Regard the bits of the value as an integer, and print the integer in
9491 Print as integer in signed decimal.
9494 Print as integer in unsigned decimal.
9497 Print as integer in octal.
9500 Print as integer in binary. The letter @samp{t} stands for ``two''.
9501 @footnote{@samp{b} cannot be used because these format letters are also
9502 used with the @code{x} command, where @samp{b} stands for ``byte'';
9503 see @ref{Memory,,Examining Memory}.}
9506 @cindex unknown address, locating
9507 @cindex locate address
9508 Print as an address, both absolute in hexadecimal and as an offset from
9509 the nearest preceding symbol. You can use this format used to discover
9510 where (in what function) an unknown address is located:
9513 (@value{GDBP}) p/a 0x54320
9514 $3 = 0x54320 <_initialize_vx+396>
9518 The command @code{info symbol 0x54320} yields similar results.
9519 @xref{Symbols, info symbol}.
9522 Regard as an integer and print it as a character constant. This
9523 prints both the numerical value and its character representation. The
9524 character representation is replaced with the octal escape @samp{\nnn}
9525 for characters outside the 7-bit @sc{ascii} range.
9527 Without this format, @value{GDBN} displays @code{char},
9528 @w{@code{unsigned char}}, and @w{@code{signed char}} data as character
9529 constants. Single-byte members of vectors are displayed as integer
9533 Regard the bits of the value as a floating point number and print
9534 using typical floating point syntax.
9537 @cindex printing strings
9538 @cindex printing byte arrays
9539 Regard as a string, if possible. With this format, pointers to single-byte
9540 data are displayed as null-terminated strings and arrays of single-byte data
9541 are displayed as fixed-length strings. Other values are displayed in their
9544 Without this format, @value{GDBN} displays pointers to and arrays of
9545 @code{char}, @w{@code{unsigned char}}, and @w{@code{signed char}} as
9546 strings. Single-byte members of a vector are displayed as an integer
9550 Like @samp{x} formatting, the value is treated as an integer and
9551 printed as hexadecimal, but leading zeros are printed to pad the value
9552 to the size of the integer type.
9555 @cindex raw printing
9556 Print using the @samp{raw} formatting. By default, @value{GDBN} will
9557 use a Python-based pretty-printer, if one is available (@pxref{Pretty
9558 Printing}). This typically results in a higher-level display of the
9559 value's contents. The @samp{r} format bypasses any Python
9560 pretty-printer which might exist.
9563 For example, to print the program counter in hex (@pxref{Registers}), type
9570 Note that no space is required before the slash; this is because command
9571 names in @value{GDBN} cannot contain a slash.
9573 To reprint the last value in the value history with a different format,
9574 you can use the @code{print} command with just a format and no
9575 expression. For example, @samp{p/x} reprints the last value in hex.
9578 @section Examining Memory
9580 You can use the command @code{x} (for ``examine'') to examine memory in
9581 any of several formats, independently of your program's data types.
9583 @cindex examining memory
9585 @kindex x @r{(examine memory)}
9586 @item x/@var{nfu} @var{addr}
9589 Use the @code{x} command to examine memory.
9592 @var{n}, @var{f}, and @var{u} are all optional parameters that specify how
9593 much memory to display and how to format it; @var{addr} is an
9594 expression giving the address where you want to start displaying memory.
9595 If you use defaults for @var{nfu}, you need not type the slash @samp{/}.
9596 Several commands set convenient defaults for @var{addr}.
9599 @item @var{n}, the repeat count
9600 The repeat count is a decimal integer; the default is 1. It specifies
9601 how much memory (counting by units @var{u}) to display. If a negative
9602 number is specified, memory is examined backward from @var{addr}.
9603 @c This really is **decimal**; unaffected by 'set radix' as of GDB
9606 @item @var{f}, the display format
9607 The display format is one of the formats used by @code{print}
9608 (@samp{x}, @samp{d}, @samp{u}, @samp{o}, @samp{t}, @samp{a}, @samp{c},
9609 @samp{f}, @samp{s}), and in addition @samp{i} (for machine instructions).
9610 The default is @samp{x} (hexadecimal) initially. The default changes
9611 each time you use either @code{x} or @code{print}.
9613 @item @var{u}, the unit size
9614 The unit size is any of
9620 Halfwords (two bytes).
9622 Words (four bytes). This is the initial default.
9624 Giant words (eight bytes).
9627 Each time you specify a unit size with @code{x}, that size becomes the
9628 default unit the next time you use @code{x}. For the @samp{i} format,
9629 the unit size is ignored and is normally not written. For the @samp{s} format,
9630 the unit size defaults to @samp{b}, unless it is explicitly given.
9631 Use @kbd{x /hs} to display 16-bit char strings and @kbd{x /ws} to display
9632 32-bit strings. The next use of @kbd{x /s} will again display 8-bit strings.
9633 Note that the results depend on the programming language of the
9634 current compilation unit. If the language is C, the @samp{s}
9635 modifier will use the UTF-16 encoding while @samp{w} will use
9636 UTF-32. The encoding is set by the programming language and cannot
9639 @item @var{addr}, starting display address
9640 @var{addr} is the address where you want @value{GDBN} to begin displaying
9641 memory. The expression need not have a pointer value (though it may);
9642 it is always interpreted as an integer address of a byte of memory.
9643 @xref{Expressions, ,Expressions}, for more information on expressions. The default for
9644 @var{addr} is usually just after the last address examined---but several
9645 other commands also set the default address: @code{info breakpoints} (to
9646 the address of the last breakpoint listed), @code{info line} (to the
9647 starting address of a line), and @code{print} (if you use it to display
9648 a value from memory).
9651 For example, @samp{x/3uh 0x54320} is a request to display three halfwords
9652 (@code{h}) of memory, formatted as unsigned decimal integers (@samp{u}),
9653 starting at address @code{0x54320}. @samp{x/4xw $sp} prints the four
9654 words (@samp{w}) of memory above the stack pointer (here, @samp{$sp};
9655 @pxref{Registers, ,Registers}) in hexadecimal (@samp{x}).
9657 You can also specify a negative repeat count to examine memory backward
9658 from the given address. For example, @samp{x/-3uh 0x54320} prints three
9659 halfwords (@code{h}) at @code{0x54314}, @code{0x54328}, and @code{0x5431c}.
9661 Since the letters indicating unit sizes are all distinct from the
9662 letters specifying output formats, you do not have to remember whether
9663 unit size or format comes first; either order works. The output
9664 specifications @samp{4xw} and @samp{4wx} mean exactly the same thing.
9665 (However, the count @var{n} must come first; @samp{wx4} does not work.)
9667 Even though the unit size @var{u} is ignored for the formats @samp{s}
9668 and @samp{i}, you might still want to use a count @var{n}; for example,
9669 @samp{3i} specifies that you want to see three machine instructions,
9670 including any operands. For convenience, especially when used with
9671 the @code{display} command, the @samp{i} format also prints branch delay
9672 slot instructions, if any, beyond the count specified, which immediately
9673 follow the last instruction that is within the count. The command
9674 @code{disassemble} gives an alternative way of inspecting machine
9675 instructions; see @ref{Machine Code,,Source and Machine Code}.
9677 If a negative repeat count is specified for the formats @samp{s} or @samp{i},
9678 the command displays null-terminated strings or instructions before the given
9679 address as many as the absolute value of the given number. For the @samp{i}
9680 format, we use line number information in the debug info to accurately locate
9681 instruction boundaries while disassembling backward. If line info is not
9682 available, the command stops examining memory with an error message.
9684 All the defaults for the arguments to @code{x} are designed to make it
9685 easy to continue scanning memory with minimal specifications each time
9686 you use @code{x}. For example, after you have inspected three machine
9687 instructions with @samp{x/3i @var{addr}}, you can inspect the next seven
9688 with just @samp{x/7}. If you use @key{RET} to repeat the @code{x} command,
9689 the repeat count @var{n} is used again; the other arguments default as
9690 for successive uses of @code{x}.
9692 When examining machine instructions, the instruction at current program
9693 counter is shown with a @code{=>} marker. For example:
9696 (@value{GDBP}) x/5i $pc-6
9697 0x804837f <main+11>: mov %esp,%ebp
9698 0x8048381 <main+13>: push %ecx
9699 0x8048382 <main+14>: sub $0x4,%esp
9700 => 0x8048385 <main+17>: movl $0x8048460,(%esp)
9701 0x804838c <main+24>: call 0x80482d4 <puts@@plt>
9704 @cindex @code{$_}, @code{$__}, and value history
9705 The addresses and contents printed by the @code{x} command are not saved
9706 in the value history because there is often too much of them and they
9707 would get in the way. Instead, @value{GDBN} makes these values available for
9708 subsequent use in expressions as values of the convenience variables
9709 @code{$_} and @code{$__}. After an @code{x} command, the last address
9710 examined is available for use in expressions in the convenience variable
9711 @code{$_}. The contents of that address, as examined, are available in
9712 the convenience variable @code{$__}.
9714 If the @code{x} command has a repeat count, the address and contents saved
9715 are from the last memory unit printed; this is not the same as the last
9716 address printed if several units were printed on the last line of output.
9718 @anchor{addressable memory unit}
9719 @cindex addressable memory unit
9720 Most targets have an addressable memory unit size of 8 bits. This means
9721 that to each memory address are associated 8 bits of data. Some
9722 targets, however, have other addressable memory unit sizes.
9723 Within @value{GDBN} and this document, the term
9724 @dfn{addressable memory unit} (or @dfn{memory unit} for short) is used
9725 when explicitly referring to a chunk of data of that size. The word
9726 @dfn{byte} is used to refer to a chunk of data of 8 bits, regardless of
9727 the addressable memory unit size of the target. For most systems,
9728 addressable memory unit is a synonym of byte.
9730 @cindex remote memory comparison
9731 @cindex target memory comparison
9732 @cindex verify remote memory image
9733 @cindex verify target memory image
9734 When you are debugging a program running on a remote target machine
9735 (@pxref{Remote Debugging}), you may wish to verify the program's image
9736 in the remote machine's memory against the executable file you
9737 downloaded to the target. Or, on any target, you may want to check
9738 whether the program has corrupted its own read-only sections. The
9739 @code{compare-sections} command is provided for such situations.
9742 @kindex compare-sections
9743 @item compare-sections @r{[}@var{section-name}@r{|}@code{-r}@r{]}
9744 Compare the data of a loadable section @var{section-name} in the
9745 executable file of the program being debugged with the same section in
9746 the target machine's memory, and report any mismatches. With no
9747 arguments, compares all loadable sections. With an argument of
9748 @code{-r}, compares all loadable read-only sections.
9750 Note: for remote targets, this command can be accelerated if the
9751 target supports computing the CRC checksum of a block of memory
9752 (@pxref{qCRC packet}).
9756 @section Automatic Display
9757 @cindex automatic display
9758 @cindex display of expressions
9760 If you find that you want to print the value of an expression frequently
9761 (to see how it changes), you might want to add it to the @dfn{automatic
9762 display list} so that @value{GDBN} prints its value each time your program stops.
9763 Each expression added to the list is given a number to identify it;
9764 to remove an expression from the list, you specify that number.
9765 The automatic display looks like this:
9769 3: bar[5] = (struct hack *) 0x3804
9773 This display shows item numbers, expressions and their current values. As with
9774 displays you request manually using @code{x} or @code{print}, you can
9775 specify the output format you prefer; in fact, @code{display} decides
9776 whether to use @code{print} or @code{x} depending your format
9777 specification---it uses @code{x} if you specify either the @samp{i}
9778 or @samp{s} format, or a unit size; otherwise it uses @code{print}.
9782 @item display @var{expr}
9783 Add the expression @var{expr} to the list of expressions to display
9784 each time your program stops. @xref{Expressions, ,Expressions}.
9786 @code{display} does not repeat if you press @key{RET} again after using it.
9788 @item display/@var{fmt} @var{expr}
9789 For @var{fmt} specifying only a display format and not a size or
9790 count, add the expression @var{expr} to the auto-display list but
9791 arrange to display it each time in the specified format @var{fmt}.
9792 @xref{Output Formats,,Output Formats}.
9794 @item display/@var{fmt} @var{addr}
9795 For @var{fmt} @samp{i} or @samp{s}, or including a unit-size or a
9796 number of units, add the expression @var{addr} as a memory address to
9797 be examined each time your program stops. Examining means in effect
9798 doing @samp{x/@var{fmt} @var{addr}}. @xref{Memory, ,Examining Memory}.
9801 For example, @samp{display/i $pc} can be helpful, to see the machine
9802 instruction about to be executed each time execution stops (@samp{$pc}
9803 is a common name for the program counter; @pxref{Registers, ,Registers}).
9806 @kindex delete display
9808 @item undisplay @var{dnums}@dots{}
9809 @itemx delete display @var{dnums}@dots{}
9810 Remove items from the list of expressions to display. Specify the
9811 numbers of the displays that you want affected with the command
9812 argument @var{dnums}. It can be a single display number, one of the
9813 numbers shown in the first field of the @samp{info display} display;
9814 or it could be a range of display numbers, as in @code{2-4}.
9816 @code{undisplay} does not repeat if you press @key{RET} after using it.
9817 (Otherwise you would just get the error @samp{No display number @dots{}}.)
9819 @kindex disable display
9820 @item disable display @var{dnums}@dots{}
9821 Disable the display of item numbers @var{dnums}. A disabled display
9822 item is not printed automatically, but is not forgotten. It may be
9823 enabled again later. Specify the numbers of the displays that you
9824 want affected with the command argument @var{dnums}. It can be a
9825 single display number, one of the numbers shown in the first field of
9826 the @samp{info display} display; or it could be a range of display
9827 numbers, as in @code{2-4}.
9829 @kindex enable display
9830 @item enable display @var{dnums}@dots{}
9831 Enable display of item numbers @var{dnums}. It becomes effective once
9832 again in auto display of its expression, until you specify otherwise.
9833 Specify the numbers of the displays that you want affected with the
9834 command argument @var{dnums}. It can be a single display number, one
9835 of the numbers shown in the first field of the @samp{info display}
9836 display; or it could be a range of display numbers, as in @code{2-4}.
9839 Display the current values of the expressions on the list, just as is
9840 done when your program stops.
9842 @kindex info display
9844 Print the list of expressions previously set up to display
9845 automatically, each one with its item number, but without showing the
9846 values. This includes disabled expressions, which are marked as such.
9847 It also includes expressions which would not be displayed right now
9848 because they refer to automatic variables not currently available.
9851 @cindex display disabled out of scope
9852 If a display expression refers to local variables, then it does not make
9853 sense outside the lexical context for which it was set up. Such an
9854 expression is disabled when execution enters a context where one of its
9855 variables is not defined. For example, if you give the command
9856 @code{display last_char} while inside a function with an argument
9857 @code{last_char}, @value{GDBN} displays this argument while your program
9858 continues to stop inside that function. When it stops elsewhere---where
9859 there is no variable @code{last_char}---the display is disabled
9860 automatically. The next time your program stops where @code{last_char}
9861 is meaningful, you can enable the display expression once again.
9863 @node Print Settings
9864 @section Print Settings
9866 @cindex format options
9867 @cindex print settings
9868 @value{GDBN} provides the following ways to control how arrays, structures,
9869 and symbols are printed.
9872 These settings are useful for debugging programs in any language:
9876 @item set print address
9877 @itemx set print address on
9878 @cindex print/don't print memory addresses
9879 @value{GDBN} prints memory addresses showing the location of stack
9880 traces, structure values, pointer values, breakpoints, and so forth,
9881 even when it also displays the contents of those addresses. The default
9882 is @code{on}. For example, this is what a stack frame display looks like with
9883 @code{set print address on}:
9888 #0 set_quotes (lq=0x34c78 "<<", rq=0x34c88 ">>")
9890 530 if (lquote != def_lquote)
9894 @item set print address off
9895 Do not print addresses when displaying their contents. For example,
9896 this is the same stack frame displayed with @code{set print address off}:
9900 (@value{GDBP}) set print addr off
9902 #0 set_quotes (lq="<<", rq=">>") at input.c:530
9903 530 if (lquote != def_lquote)
9907 You can use @samp{set print address off} to eliminate all machine
9908 dependent displays from the @value{GDBN} interface. For example, with
9909 @code{print address off}, you should get the same text for backtraces on
9910 all machines---whether or not they involve pointer arguments.
9913 @item show print address
9914 Show whether or not addresses are to be printed.
9917 When @value{GDBN} prints a symbolic address, it normally prints the
9918 closest earlier symbol plus an offset. If that symbol does not uniquely
9919 identify the address (for example, it is a name whose scope is a single
9920 source file), you may need to clarify. One way to do this is with
9921 @code{info line}, for example @samp{info line *0x4537}. Alternately,
9922 you can set @value{GDBN} to print the source file and line number when
9923 it prints a symbolic address:
9926 @item set print symbol-filename on
9927 @cindex source file and line of a symbol
9928 @cindex symbol, source file and line
9929 Tell @value{GDBN} to print the source file name and line number of a
9930 symbol in the symbolic form of an address.
9932 @item set print symbol-filename off
9933 Do not print source file name and line number of a symbol. This is the
9936 @item show print symbol-filename
9937 Show whether or not @value{GDBN} will print the source file name and
9938 line number of a symbol in the symbolic form of an address.
9941 Another situation where it is helpful to show symbol filenames and line
9942 numbers is when disassembling code; @value{GDBN} shows you the line
9943 number and source file that corresponds to each instruction.
9945 Also, you may wish to see the symbolic form only if the address being
9946 printed is reasonably close to the closest earlier symbol:
9949 @item set print max-symbolic-offset @var{max-offset}
9950 @itemx set print max-symbolic-offset unlimited
9951 @cindex maximum value for offset of closest symbol
9952 Tell @value{GDBN} to only display the symbolic form of an address if the
9953 offset between the closest earlier symbol and the address is less than
9954 @var{max-offset}. The default is @code{unlimited}, which tells @value{GDBN}
9955 to always print the symbolic form of an address if any symbol precedes
9956 it. Zero is equivalent to @code{unlimited}.
9958 @item show print max-symbolic-offset
9959 Ask how large the maximum offset is that @value{GDBN} prints in a
9963 @cindex wild pointer, interpreting
9964 @cindex pointer, finding referent
9965 If you have a pointer and you are not sure where it points, try
9966 @samp{set print symbol-filename on}. Then you can determine the name
9967 and source file location of the variable where it points, using
9968 @samp{p/a @var{pointer}}. This interprets the address in symbolic form.
9969 For example, here @value{GDBN} shows that a variable @code{ptt} points
9970 at another variable @code{t}, defined in @file{hi2.c}:
9973 (@value{GDBP}) set print symbol-filename on
9974 (@value{GDBP}) p/a ptt
9975 $4 = 0xe008 <t in hi2.c>
9979 @emph{Warning:} For pointers that point to a local variable, @samp{p/a}
9980 does not show the symbol name and filename of the referent, even with
9981 the appropriate @code{set print} options turned on.
9984 You can also enable @samp{/a}-like formatting all the time using
9985 @samp{set print symbol on}:
9988 @item set print symbol on
9989 Tell @value{GDBN} to print the symbol corresponding to an address, if
9992 @item set print symbol off
9993 Tell @value{GDBN} not to print the symbol corresponding to an
9994 address. In this mode, @value{GDBN} will still print the symbol
9995 corresponding to pointers to functions. This is the default.
9997 @item show print symbol
9998 Show whether @value{GDBN} will display the symbol corresponding to an
10002 Other settings control how different kinds of objects are printed:
10005 @item set print array
10006 @itemx set print array on
10007 @cindex pretty print arrays
10008 Pretty print arrays. This format is more convenient to read,
10009 but uses more space. The default is off.
10011 @item set print array off
10012 Return to compressed format for arrays.
10014 @item show print array
10015 Show whether compressed or pretty format is selected for displaying
10018 @cindex print array indexes
10019 @item set print array-indexes
10020 @itemx set print array-indexes on
10021 Print the index of each element when displaying arrays. May be more
10022 convenient to locate a given element in the array or quickly find the
10023 index of a given element in that printed array. The default is off.
10025 @item set print array-indexes off
10026 Stop printing element indexes when displaying arrays.
10028 @item show print array-indexes
10029 Show whether the index of each element is printed when displaying
10032 @item set print elements @var{number-of-elements}
10033 @itemx set print elements unlimited
10034 @cindex number of array elements to print
10035 @cindex limit on number of printed array elements
10036 Set a limit on how many elements of an array @value{GDBN} will print.
10037 If @value{GDBN} is printing a large array, it stops printing after it has
10038 printed the number of elements set by the @code{set print elements} command.
10039 This limit also applies to the display of strings.
10040 When @value{GDBN} starts, this limit is set to 200.
10041 Setting @var{number-of-elements} to @code{unlimited} or zero means
10042 that the number of elements to print is unlimited.
10044 @item show print elements
10045 Display the number of elements of a large array that @value{GDBN} will print.
10046 If the number is 0, then the printing is unlimited.
10048 @item set print frame-arguments @var{value}
10049 @kindex set print frame-arguments
10050 @cindex printing frame argument values
10051 @cindex print all frame argument values
10052 @cindex print frame argument values for scalars only
10053 @cindex do not print frame argument values
10054 This command allows to control how the values of arguments are printed
10055 when the debugger prints a frame (@pxref{Frames}). The possible
10060 The values of all arguments are printed.
10063 Print the value of an argument only if it is a scalar. The value of more
10064 complex arguments such as arrays, structures, unions, etc, is replaced
10065 by @code{@dots{}}. This is the default. Here is an example where
10066 only scalar arguments are shown:
10069 #1 0x08048361 in call_me (i=3, s=@dots{}, ss=0xbf8d508c, u=@dots{}, e=green)
10074 None of the argument values are printed. Instead, the value of each argument
10075 is replaced by @code{@dots{}}. In this case, the example above now becomes:
10078 #1 0x08048361 in call_me (i=@dots{}, s=@dots{}, ss=@dots{}, u=@dots{}, e=@dots{})
10083 By default, only scalar arguments are printed. This command can be used
10084 to configure the debugger to print the value of all arguments, regardless
10085 of their type. However, it is often advantageous to not print the value
10086 of more complex parameters. For instance, it reduces the amount of
10087 information printed in each frame, making the backtrace more readable.
10088 Also, it improves performance when displaying Ada frames, because
10089 the computation of large arguments can sometimes be CPU-intensive,
10090 especially in large applications. Setting @code{print frame-arguments}
10091 to @code{scalars} (the default) or @code{none} avoids this computation,
10092 thus speeding up the display of each Ada frame.
10094 @item show print frame-arguments
10095 Show how the value of arguments should be displayed when printing a frame.
10097 @item set print raw frame-arguments on
10098 Print frame arguments in raw, non pretty-printed, form.
10100 @item set print raw frame-arguments off
10101 Print frame arguments in pretty-printed form, if there is a pretty-printer
10102 for the value (@pxref{Pretty Printing}),
10103 otherwise print the value in raw form.
10104 This is the default.
10106 @item show print raw frame-arguments
10107 Show whether to print frame arguments in raw form.
10109 @anchor{set print entry-values}
10110 @item set print entry-values @var{value}
10111 @kindex set print entry-values
10112 Set printing of frame argument values at function entry. In some cases
10113 @value{GDBN} can determine the value of function argument which was passed by
10114 the function caller, even if the value was modified inside the called function
10115 and therefore is different. With optimized code, the current value could be
10116 unavailable, but the entry value may still be known.
10118 The default value is @code{default} (see below for its description). Older
10119 @value{GDBN} behaved as with the setting @code{no}. Compilers not supporting
10120 this feature will behave in the @code{default} setting the same way as with the
10123 This functionality is currently supported only by DWARF 2 debugging format and
10124 the compiler has to produce @samp{DW_TAG_call_site} tags. With
10125 @value{NGCC}, you need to specify @option{-O -g} during compilation, to get
10128 The @var{value} parameter can be one of the following:
10132 Print only actual parameter values, never print values from function entry
10136 #0 different (val=6)
10137 #0 lost (val=<optimized out>)
10139 #0 invalid (val=<optimized out>)
10143 Print only parameter values from function entry point. The actual parameter
10144 values are never printed.
10146 #0 equal (val@@entry=5)
10147 #0 different (val@@entry=5)
10148 #0 lost (val@@entry=5)
10149 #0 born (val@@entry=<optimized out>)
10150 #0 invalid (val@@entry=<optimized out>)
10154 Print only parameter values from function entry point. If value from function
10155 entry point is not known while the actual value is known, print the actual
10156 value for such parameter.
10158 #0 equal (val@@entry=5)
10159 #0 different (val@@entry=5)
10160 #0 lost (val@@entry=5)
10162 #0 invalid (val@@entry=<optimized out>)
10166 Print actual parameter values. If actual parameter value is not known while
10167 value from function entry point is known, print the entry point value for such
10171 #0 different (val=6)
10172 #0 lost (val@@entry=5)
10174 #0 invalid (val=<optimized out>)
10178 Always print both the actual parameter value and its value from function entry
10179 point, even if values of one or both are not available due to compiler
10182 #0 equal (val=5, val@@entry=5)
10183 #0 different (val=6, val@@entry=5)
10184 #0 lost (val=<optimized out>, val@@entry=5)
10185 #0 born (val=10, val@@entry=<optimized out>)
10186 #0 invalid (val=<optimized out>, val@@entry=<optimized out>)
10190 Print the actual parameter value if it is known and also its value from
10191 function entry point if it is known. If neither is known, print for the actual
10192 value @code{<optimized out>}. If not in MI mode (@pxref{GDB/MI}) and if both
10193 values are known and identical, print the shortened
10194 @code{param=param@@entry=VALUE} notation.
10196 #0 equal (val=val@@entry=5)
10197 #0 different (val=6, val@@entry=5)
10198 #0 lost (val@@entry=5)
10200 #0 invalid (val=<optimized out>)
10204 Always print the actual parameter value. Print also its value from function
10205 entry point, but only if it is known. If not in MI mode (@pxref{GDB/MI}) and
10206 if both values are known and identical, print the shortened
10207 @code{param=param@@entry=VALUE} notation.
10209 #0 equal (val=val@@entry=5)
10210 #0 different (val=6, val@@entry=5)
10211 #0 lost (val=<optimized out>, val@@entry=5)
10213 #0 invalid (val=<optimized out>)
10217 For analysis messages on possible failures of frame argument values at function
10218 entry resolution see @ref{set debug entry-values}.
10220 @item show print entry-values
10221 Show the method being used for printing of frame argument values at function
10224 @item set print repeats @var{number-of-repeats}
10225 @itemx set print repeats unlimited
10226 @cindex repeated array elements
10227 Set the threshold for suppressing display of repeated array
10228 elements. When the number of consecutive identical elements of an
10229 array exceeds the threshold, @value{GDBN} prints the string
10230 @code{"<repeats @var{n} times>"}, where @var{n} is the number of
10231 identical repetitions, instead of displaying the identical elements
10232 themselves. Setting the threshold to @code{unlimited} or zero will
10233 cause all elements to be individually printed. The default threshold
10236 @item show print repeats
10237 Display the current threshold for printing repeated identical
10240 @item set print null-stop
10241 @cindex @sc{null} elements in arrays
10242 Cause @value{GDBN} to stop printing the characters of an array when the first
10243 @sc{null} is encountered. This is useful when large arrays actually
10244 contain only short strings.
10245 The default is off.
10247 @item show print null-stop
10248 Show whether @value{GDBN} stops printing an array on the first
10249 @sc{null} character.
10251 @item set print pretty on
10252 @cindex print structures in indented form
10253 @cindex indentation in structure display
10254 Cause @value{GDBN} to print structures in an indented format with one member
10255 per line, like this:
10270 @item set print pretty off
10271 Cause @value{GDBN} to print structures in a compact format, like this:
10275 $1 = @{next = 0x0, flags = @{sweet = 1, sour = 1@}, \
10276 meat = 0x54 "Pork"@}
10281 This is the default format.
10283 @item show print pretty
10284 Show which format @value{GDBN} is using to print structures.
10286 @item set print sevenbit-strings on
10287 @cindex eight-bit characters in strings
10288 @cindex octal escapes in strings
10289 Print using only seven-bit characters; if this option is set,
10290 @value{GDBN} displays any eight-bit characters (in strings or
10291 character values) using the notation @code{\}@var{nnn}. This setting is
10292 best if you are working in English (@sc{ascii}) and you use the
10293 high-order bit of characters as a marker or ``meta'' bit.
10295 @item set print sevenbit-strings off
10296 Print full eight-bit characters. This allows the use of more
10297 international character sets, and is the default.
10299 @item show print sevenbit-strings
10300 Show whether or not @value{GDBN} is printing only seven-bit characters.
10302 @item set print union on
10303 @cindex unions in structures, printing
10304 Tell @value{GDBN} to print unions which are contained in structures
10305 and other unions. This is the default setting.
10307 @item set print union off
10308 Tell @value{GDBN} not to print unions which are contained in
10309 structures and other unions. @value{GDBN} will print @code{"@{...@}"}
10312 @item show print union
10313 Ask @value{GDBN} whether or not it will print unions which are contained in
10314 structures and other unions.
10316 For example, given the declarations
10319 typedef enum @{Tree, Bug@} Species;
10320 typedef enum @{Big_tree, Acorn, Seedling@} Tree_forms;
10321 typedef enum @{Caterpillar, Cocoon, Butterfly@}
10332 struct thing foo = @{Tree, @{Acorn@}@};
10336 with @code{set print union on} in effect @samp{p foo} would print
10339 $1 = @{it = Tree, form = @{tree = Acorn, bug = Cocoon@}@}
10343 and with @code{set print union off} in effect it would print
10346 $1 = @{it = Tree, form = @{...@}@}
10350 @code{set print union} affects programs written in C-like languages
10356 These settings are of interest when debugging C@t{++} programs:
10359 @cindex demangling C@t{++} names
10360 @item set print demangle
10361 @itemx set print demangle on
10362 Print C@t{++} names in their source form rather than in the encoded
10363 (``mangled'') form passed to the assembler and linker for type-safe
10364 linkage. The default is on.
10366 @item show print demangle
10367 Show whether C@t{++} names are printed in mangled or demangled form.
10369 @item set print asm-demangle
10370 @itemx set print asm-demangle on
10371 Print C@t{++} names in their source form rather than their mangled form, even
10372 in assembler code printouts such as instruction disassemblies.
10373 The default is off.
10375 @item show print asm-demangle
10376 Show whether C@t{++} names in assembly listings are printed in mangled
10379 @cindex C@t{++} symbol decoding style
10380 @cindex symbol decoding style, C@t{++}
10381 @kindex set demangle-style
10382 @item set demangle-style @var{style}
10383 Choose among several encoding schemes used by different compilers to
10384 represent C@t{++} names. The choices for @var{style} are currently:
10388 Allow @value{GDBN} to choose a decoding style by inspecting your program.
10389 This is the default.
10392 Decode based on the @sc{gnu} C@t{++} compiler (@code{g++}) encoding algorithm.
10395 Decode based on the HP ANSI C@t{++} (@code{aCC}) encoding algorithm.
10398 Decode based on the Lucid C@t{++} compiler (@code{lcc}) encoding algorithm.
10401 Decode using the algorithm in the @cite{C@t{++} Annotated Reference Manual}.
10402 @strong{Warning:} this setting alone is not sufficient to allow
10403 debugging @code{cfront}-generated executables. @value{GDBN} would
10404 require further enhancement to permit that.
10407 If you omit @var{style}, you will see a list of possible formats.
10409 @item show demangle-style
10410 Display the encoding style currently in use for decoding C@t{++} symbols.
10412 @item set print object
10413 @itemx set print object on
10414 @cindex derived type of an object, printing
10415 @cindex display derived types
10416 When displaying a pointer to an object, identify the @emph{actual}
10417 (derived) type of the object rather than the @emph{declared} type, using
10418 the virtual function table. Note that the virtual function table is
10419 required---this feature can only work for objects that have run-time
10420 type identification; a single virtual method in the object's declared
10421 type is sufficient. Note that this setting is also taken into account when
10422 working with variable objects via MI (@pxref{GDB/MI}).
10424 @item set print object off
10425 Display only the declared type of objects, without reference to the
10426 virtual function table. This is the default setting.
10428 @item show print object
10429 Show whether actual, or declared, object types are displayed.
10431 @item set print static-members
10432 @itemx set print static-members on
10433 @cindex static members of C@t{++} objects
10434 Print static members when displaying a C@t{++} object. The default is on.
10436 @item set print static-members off
10437 Do not print static members when displaying a C@t{++} object.
10439 @item show print static-members
10440 Show whether C@t{++} static members are printed or not.
10442 @item set print pascal_static-members
10443 @itemx set print pascal_static-members on
10444 @cindex static members of Pascal objects
10445 @cindex Pascal objects, static members display
10446 Print static members when displaying a Pascal object. The default is on.
10448 @item set print pascal_static-members off
10449 Do not print static members when displaying a Pascal object.
10451 @item show print pascal_static-members
10452 Show whether Pascal static members are printed or not.
10454 @c These don't work with HP ANSI C++ yet.
10455 @item set print vtbl
10456 @itemx set print vtbl on
10457 @cindex pretty print C@t{++} virtual function tables
10458 @cindex virtual functions (C@t{++}) display
10459 @cindex VTBL display
10460 Pretty print C@t{++} virtual function tables. The default is off.
10461 (The @code{vtbl} commands do not work on programs compiled with the HP
10462 ANSI C@t{++} compiler (@code{aCC}).)
10464 @item set print vtbl off
10465 Do not pretty print C@t{++} virtual function tables.
10467 @item show print vtbl
10468 Show whether C@t{++} virtual function tables are pretty printed, or not.
10471 @node Pretty Printing
10472 @section Pretty Printing
10474 @value{GDBN} provides a mechanism to allow pretty-printing of values using
10475 Python code. It greatly simplifies the display of complex objects. This
10476 mechanism works for both MI and the CLI.
10479 * Pretty-Printer Introduction:: Introduction to pretty-printers
10480 * Pretty-Printer Example:: An example pretty-printer
10481 * Pretty-Printer Commands:: Pretty-printer commands
10484 @node Pretty-Printer Introduction
10485 @subsection Pretty-Printer Introduction
10487 When @value{GDBN} prints a value, it first sees if there is a pretty-printer
10488 registered for the value. If there is then @value{GDBN} invokes the
10489 pretty-printer to print the value. Otherwise the value is printed normally.
10491 Pretty-printers are normally named. This makes them easy to manage.
10492 The @samp{info pretty-printer} command will list all the installed
10493 pretty-printers with their names.
10494 If a pretty-printer can handle multiple data types, then its
10495 @dfn{subprinters} are the printers for the individual data types.
10496 Each such subprinter has its own name.
10497 The format of the name is @var{printer-name};@var{subprinter-name}.
10499 Pretty-printers are installed by @dfn{registering} them with @value{GDBN}.
10500 Typically they are automatically loaded and registered when the corresponding
10501 debug information is loaded, thus making them available without having to
10502 do anything special.
10504 There are three places where a pretty-printer can be registered.
10508 Pretty-printers registered globally are available when debugging
10512 Pretty-printers registered with a program space are available only
10513 when debugging that program.
10514 @xref{Progspaces In Python}, for more details on program spaces in Python.
10517 Pretty-printers registered with an objfile are loaded and unloaded
10518 with the corresponding objfile (e.g., shared library).
10519 @xref{Objfiles In Python}, for more details on objfiles in Python.
10522 @xref{Selecting Pretty-Printers}, for further information on how
10523 pretty-printers are selected,
10525 @xref{Writing a Pretty-Printer}, for implementing pretty printers
10528 @node Pretty-Printer Example
10529 @subsection Pretty-Printer Example
10531 Here is how a C@t{++} @code{std::string} looks without a pretty-printer:
10534 (@value{GDBP}) print s
10536 static npos = 4294967295,
10538 <std::allocator<char>> = @{
10539 <__gnu_cxx::new_allocator<char>> = @{
10540 <No data fields>@}, <No data fields>
10542 members of std::basic_string<char, std::char_traits<char>,
10543 std::allocator<char> >::_Alloc_hider:
10544 _M_p = 0x804a014 "abcd"
10549 With a pretty-printer for @code{std::string} only the contents are printed:
10552 (@value{GDBP}) print s
10556 @node Pretty-Printer Commands
10557 @subsection Pretty-Printer Commands
10558 @cindex pretty-printer commands
10561 @kindex info pretty-printer
10562 @item info pretty-printer [@var{object-regexp} [@var{name-regexp}]]
10563 Print the list of installed pretty-printers.
10564 This includes disabled pretty-printers, which are marked as such.
10566 @var{object-regexp} is a regular expression matching the objects
10567 whose pretty-printers to list.
10568 Objects can be @code{global}, the program space's file
10569 (@pxref{Progspaces In Python}),
10570 and the object files within that program space (@pxref{Objfiles In Python}).
10571 @xref{Selecting Pretty-Printers}, for details on how @value{GDBN}
10572 looks up a printer from these three objects.
10574 @var{name-regexp} is a regular expression matching the name of the printers
10577 @kindex disable pretty-printer
10578 @item disable pretty-printer [@var{object-regexp} [@var{name-regexp}]]
10579 Disable pretty-printers matching @var{object-regexp} and @var{name-regexp}.
10580 A disabled pretty-printer is not forgotten, it may be enabled again later.
10582 @kindex enable pretty-printer
10583 @item enable pretty-printer [@var{object-regexp} [@var{name-regexp}]]
10584 Enable pretty-printers matching @var{object-regexp} and @var{name-regexp}.
10589 Suppose we have three pretty-printers installed: one from library1.so
10590 named @code{foo} that prints objects of type @code{foo}, and
10591 another from library2.so named @code{bar} that prints two types of objects,
10592 @code{bar1} and @code{bar2}.
10595 (gdb) info pretty-printer
10602 (gdb) info pretty-printer library2
10607 (gdb) disable pretty-printer library1
10609 2 of 3 printers enabled
10610 (gdb) info pretty-printer
10617 (gdb) disable pretty-printer library2 bar:bar1
10619 1 of 3 printers enabled
10620 (gdb) info pretty-printer library2
10627 (gdb) disable pretty-printer library2 bar
10629 0 of 3 printers enabled
10630 (gdb) info pretty-printer library2
10639 Note that for @code{bar} the entire printer can be disabled,
10640 as can each individual subprinter.
10642 @node Value History
10643 @section Value History
10645 @cindex value history
10646 @cindex history of values printed by @value{GDBN}
10647 Values printed by the @code{print} command are saved in the @value{GDBN}
10648 @dfn{value history}. This allows you to refer to them in other expressions.
10649 Values are kept until the symbol table is re-read or discarded
10650 (for example with the @code{file} or @code{symbol-file} commands).
10651 When the symbol table changes, the value history is discarded,
10652 since the values may contain pointers back to the types defined in the
10657 @cindex history number
10658 The values printed are given @dfn{history numbers} by which you can
10659 refer to them. These are successive integers starting with one.
10660 @code{print} shows you the history number assigned to a value by
10661 printing @samp{$@var{num} = } before the value; here @var{num} is the
10664 To refer to any previous value, use @samp{$} followed by the value's
10665 history number. The way @code{print} labels its output is designed to
10666 remind you of this. Just @code{$} refers to the most recent value in
10667 the history, and @code{$$} refers to the value before that.
10668 @code{$$@var{n}} refers to the @var{n}th value from the end; @code{$$2}
10669 is the value just prior to @code{$$}, @code{$$1} is equivalent to
10670 @code{$$}, and @code{$$0} is equivalent to @code{$}.
10672 For example, suppose you have just printed a pointer to a structure and
10673 want to see the contents of the structure. It suffices to type
10679 If you have a chain of structures where the component @code{next} points
10680 to the next one, you can print the contents of the next one with this:
10687 You can print successive links in the chain by repeating this
10688 command---which you can do by just typing @key{RET}.
10690 Note that the history records values, not expressions. If the value of
10691 @code{x} is 4 and you type these commands:
10699 then the value recorded in the value history by the @code{print} command
10700 remains 4 even though the value of @code{x} has changed.
10703 @kindex show values
10705 Print the last ten values in the value history, with their item numbers.
10706 This is like @samp{p@ $$9} repeated ten times, except that @code{show
10707 values} does not change the history.
10709 @item show values @var{n}
10710 Print ten history values centered on history item number @var{n}.
10712 @item show values +
10713 Print ten history values just after the values last printed. If no more
10714 values are available, @code{show values +} produces no display.
10717 Pressing @key{RET} to repeat @code{show values @var{n}} has exactly the
10718 same effect as @samp{show values +}.
10720 @node Convenience Vars
10721 @section Convenience Variables
10723 @cindex convenience variables
10724 @cindex user-defined variables
10725 @value{GDBN} provides @dfn{convenience variables} that you can use within
10726 @value{GDBN} to hold on to a value and refer to it later. These variables
10727 exist entirely within @value{GDBN}; they are not part of your program, and
10728 setting a convenience variable has no direct effect on further execution
10729 of your program. That is why you can use them freely.
10731 Convenience variables are prefixed with @samp{$}. Any name preceded by
10732 @samp{$} can be used for a convenience variable, unless it is one of
10733 the predefined machine-specific register names (@pxref{Registers, ,Registers}).
10734 (Value history references, in contrast, are @emph{numbers} preceded
10735 by @samp{$}. @xref{Value History, ,Value History}.)
10737 You can save a value in a convenience variable with an assignment
10738 expression, just as you would set a variable in your program.
10742 set $foo = *object_ptr
10746 would save in @code{$foo} the value contained in the object pointed to by
10749 Using a convenience variable for the first time creates it, but its
10750 value is @code{void} until you assign a new value. You can alter the
10751 value with another assignment at any time.
10753 Convenience variables have no fixed types. You can assign a convenience
10754 variable any type of value, including structures and arrays, even if
10755 that variable already has a value of a different type. The convenience
10756 variable, when used as an expression, has the type of its current value.
10759 @kindex show convenience
10760 @cindex show all user variables and functions
10761 @item show convenience
10762 Print a list of convenience variables used so far, and their values,
10763 as well as a list of the convenience functions.
10764 Abbreviated @code{show conv}.
10766 @kindex init-if-undefined
10767 @cindex convenience variables, initializing
10768 @item init-if-undefined $@var{variable} = @var{expression}
10769 Set a convenience variable if it has not already been set. This is useful
10770 for user-defined commands that keep some state. It is similar, in concept,
10771 to using local static variables with initializers in C (except that
10772 convenience variables are global). It can also be used to allow users to
10773 override default values used in a command script.
10775 If the variable is already defined then the expression is not evaluated so
10776 any side-effects do not occur.
10779 One of the ways to use a convenience variable is as a counter to be
10780 incremented or a pointer to be advanced. For example, to print
10781 a field from successive elements of an array of structures:
10785 print bar[$i++]->contents
10789 Repeat that command by typing @key{RET}.
10791 Some convenience variables are created automatically by @value{GDBN} and given
10792 values likely to be useful.
10795 @vindex $_@r{, convenience variable}
10797 The variable @code{$_} is automatically set by the @code{x} command to
10798 the last address examined (@pxref{Memory, ,Examining Memory}). Other
10799 commands which provide a default address for @code{x} to examine also
10800 set @code{$_} to that address; these commands include @code{info line}
10801 and @code{info breakpoint}. The type of @code{$_} is @code{void *}
10802 except when set by the @code{x} command, in which case it is a pointer
10803 to the type of @code{$__}.
10805 @vindex $__@r{, convenience variable}
10807 The variable @code{$__} is automatically set by the @code{x} command
10808 to the value found in the last address examined. Its type is chosen
10809 to match the format in which the data was printed.
10812 @vindex $_exitcode@r{, convenience variable}
10813 When the program being debugged terminates normally, @value{GDBN}
10814 automatically sets this variable to the exit code of the program, and
10815 resets @code{$_exitsignal} to @code{void}.
10818 @vindex $_exitsignal@r{, convenience variable}
10819 When the program being debugged dies due to an uncaught signal,
10820 @value{GDBN} automatically sets this variable to that signal's number,
10821 and resets @code{$_exitcode} to @code{void}.
10823 To distinguish between whether the program being debugged has exited
10824 (i.e., @code{$_exitcode} is not @code{void}) or signalled (i.e.,
10825 @code{$_exitsignal} is not @code{void}), the convenience function
10826 @code{$_isvoid} can be used (@pxref{Convenience Funs,, Convenience
10827 Functions}). For example, considering the following source code:
10830 #include <signal.h>
10833 main (int argc, char *argv[])
10840 A valid way of telling whether the program being debugged has exited
10841 or signalled would be:
10844 (@value{GDBP}) define has_exited_or_signalled
10845 Type commands for definition of ``has_exited_or_signalled''.
10846 End with a line saying just ``end''.
10847 >if $_isvoid ($_exitsignal)
10848 >echo The program has exited\n
10850 >echo The program has signalled\n
10856 Program terminated with signal SIGALRM, Alarm clock.
10857 The program no longer exists.
10858 (@value{GDBP}) has_exited_or_signalled
10859 The program has signalled
10862 As can be seen, @value{GDBN} correctly informs that the program being
10863 debugged has signalled, since it calls @code{raise} and raises a
10864 @code{SIGALRM} signal. If the program being debugged had not called
10865 @code{raise}, then @value{GDBN} would report a normal exit:
10868 (@value{GDBP}) has_exited_or_signalled
10869 The program has exited
10873 The variable @code{$_exception} is set to the exception object being
10874 thrown at an exception-related catchpoint. @xref{Set Catchpoints}.
10877 @itemx $_probe_arg0@dots{}$_probe_arg11
10878 Arguments to a static probe. @xref{Static Probe Points}.
10881 @vindex $_sdata@r{, inspect, convenience variable}
10882 The variable @code{$_sdata} contains extra collected static tracepoint
10883 data. @xref{Tracepoint Actions,,Tracepoint Action Lists}. Note that
10884 @code{$_sdata} could be empty, if not inspecting a trace buffer, or
10885 if extra static tracepoint data has not been collected.
10888 @vindex $_siginfo@r{, convenience variable}
10889 The variable @code{$_siginfo} contains extra signal information
10890 (@pxref{extra signal information}). Note that @code{$_siginfo}
10891 could be empty, if the application has not yet received any signals.
10892 For example, it will be empty before you execute the @code{run} command.
10895 @vindex $_tlb@r{, convenience variable}
10896 The variable @code{$_tlb} is automatically set when debugging
10897 applications running on MS-Windows in native mode or connected to
10898 gdbserver that supports the @code{qGetTIBAddr} request.
10899 @xref{General Query Packets}.
10900 This variable contains the address of the thread information block.
10903 The number of the current inferior. @xref{Inferiors and
10904 Programs, ,Debugging Multiple Inferiors and Programs}.
10907 The thread number of the current thread. @xref{thread numbers}.
10910 The global number of the current thread. @xref{global thread numbers}.
10914 @node Convenience Funs
10915 @section Convenience Functions
10917 @cindex convenience functions
10918 @value{GDBN} also supplies some @dfn{convenience functions}. These
10919 have a syntax similar to convenience variables. A convenience
10920 function can be used in an expression just like an ordinary function;
10921 however, a convenience function is implemented internally to
10924 These functions do not require @value{GDBN} to be configured with
10925 @code{Python} support, which means that they are always available.
10929 @item $_isvoid (@var{expr})
10930 @findex $_isvoid@r{, convenience function}
10931 Return one if the expression @var{expr} is @code{void}. Otherwise it
10934 A @code{void} expression is an expression where the type of the result
10935 is @code{void}. For example, you can examine a convenience variable
10936 (see @ref{Convenience Vars,, Convenience Variables}) to check whether
10940 (@value{GDBP}) print $_exitcode
10942 (@value{GDBP}) print $_isvoid ($_exitcode)
10945 Starting program: ./a.out
10946 [Inferior 1 (process 29572) exited normally]
10947 (@value{GDBP}) print $_exitcode
10949 (@value{GDBP}) print $_isvoid ($_exitcode)
10953 In the example above, we used @code{$_isvoid} to check whether
10954 @code{$_exitcode} is @code{void} before and after the execution of the
10955 program being debugged. Before the execution there is no exit code to
10956 be examined, therefore @code{$_exitcode} is @code{void}. After the
10957 execution the program being debugged returned zero, therefore
10958 @code{$_exitcode} is zero, which means that it is not @code{void}
10961 The @code{void} expression can also be a call of a function from the
10962 program being debugged. For example, given the following function:
10971 The result of calling it inside @value{GDBN} is @code{void}:
10974 (@value{GDBP}) print foo ()
10976 (@value{GDBP}) print $_isvoid (foo ())
10978 (@value{GDBP}) set $v = foo ()
10979 (@value{GDBP}) print $v
10981 (@value{GDBP}) print $_isvoid ($v)
10987 These functions require @value{GDBN} to be configured with
10988 @code{Python} support.
10992 @item $_memeq(@var{buf1}, @var{buf2}, @var{length})
10993 @findex $_memeq@r{, convenience function}
10994 Returns one if the @var{length} bytes at the addresses given by
10995 @var{buf1} and @var{buf2} are equal.
10996 Otherwise it returns zero.
10998 @item $_regex(@var{str}, @var{regex})
10999 @findex $_regex@r{, convenience function}
11000 Returns one if the string @var{str} matches the regular expression
11001 @var{regex}. Otherwise it returns zero.
11002 The syntax of the regular expression is that specified by @code{Python}'s
11003 regular expression support.
11005 @item $_streq(@var{str1}, @var{str2})
11006 @findex $_streq@r{, convenience function}
11007 Returns one if the strings @var{str1} and @var{str2} are equal.
11008 Otherwise it returns zero.
11010 @item $_strlen(@var{str})
11011 @findex $_strlen@r{, convenience function}
11012 Returns the length of string @var{str}.
11014 @item $_caller_is(@var{name}@r{[}, @var{number_of_frames}@r{]})
11015 @findex $_caller_is@r{, convenience function}
11016 Returns one if the calling function's name is equal to @var{name}.
11017 Otherwise it returns zero.
11019 If the optional argument @var{number_of_frames} is provided,
11020 it is the number of frames up in the stack to look.
11028 at testsuite/gdb.python/py-caller-is.c:21
11029 #1 0x00000000004005a0 in middle_func ()
11030 at testsuite/gdb.python/py-caller-is.c:27
11031 #2 0x00000000004005ab in top_func ()
11032 at testsuite/gdb.python/py-caller-is.c:33
11033 #3 0x00000000004005b6 in main ()
11034 at testsuite/gdb.python/py-caller-is.c:39
11035 (gdb) print $_caller_is ("middle_func")
11037 (gdb) print $_caller_is ("top_func", 2)
11041 @item $_caller_matches(@var{regexp}@r{[}, @var{number_of_frames}@r{]})
11042 @findex $_caller_matches@r{, convenience function}
11043 Returns one if the calling function's name matches the regular expression
11044 @var{regexp}. Otherwise it returns zero.
11046 If the optional argument @var{number_of_frames} is provided,
11047 it is the number of frames up in the stack to look.
11050 @item $_any_caller_is(@var{name}@r{[}, @var{number_of_frames}@r{]})
11051 @findex $_any_caller_is@r{, convenience function}
11052 Returns one if any calling function's name is equal to @var{name}.
11053 Otherwise it returns zero.
11055 If the optional argument @var{number_of_frames} is provided,
11056 it is the number of frames up in the stack to look.
11059 This function differs from @code{$_caller_is} in that this function
11060 checks all stack frames from the immediate caller to the frame specified
11061 by @var{number_of_frames}, whereas @code{$_caller_is} only checks the
11062 frame specified by @var{number_of_frames}.
11064 @item $_any_caller_matches(@var{regexp}@r{[}, @var{number_of_frames}@r{]})
11065 @findex $_any_caller_matches@r{, convenience function}
11066 Returns one if any calling function's name matches the regular expression
11067 @var{regexp}. Otherwise it returns zero.
11069 If the optional argument @var{number_of_frames} is provided,
11070 it is the number of frames up in the stack to look.
11073 This function differs from @code{$_caller_matches} in that this function
11074 checks all stack frames from the immediate caller to the frame specified
11075 by @var{number_of_frames}, whereas @code{$_caller_matches} only checks the
11076 frame specified by @var{number_of_frames}.
11078 @item $_as_string(@var{value})
11079 @findex $_as_string@r{, convenience function}
11080 Return the string representation of @var{value}.
11082 This function is useful to obtain the textual label (enumerator) of an
11083 enumeration value. For example, assuming the variable @var{node} is of
11084 an enumerated type:
11087 (gdb) printf "Visiting node of type %s\n", $_as_string(node)
11088 Visiting node of type NODE_INTEGER
11093 @value{GDBN} provides the ability to list and get help on
11094 convenience functions.
11097 @item help function
11098 @kindex help function
11099 @cindex show all convenience functions
11100 Print a list of all convenience functions.
11107 You can refer to machine register contents, in expressions, as variables
11108 with names starting with @samp{$}. The names of registers are different
11109 for each machine; use @code{info registers} to see the names used on
11113 @kindex info registers
11114 @item info registers
11115 Print the names and values of all registers except floating-point
11116 and vector registers (in the selected stack frame).
11118 @kindex info all-registers
11119 @cindex floating point registers
11120 @item info all-registers
11121 Print the names and values of all registers, including floating-point
11122 and vector registers (in the selected stack frame).
11124 @item info registers @var{reggroup} @dots{}
11125 Print the name and value of the registers in each of the specified
11126 @var{reggroup}s. The @var{reggoup} can be any of those returned by
11127 @code{maint print reggroups} (@pxref{Maintenance Commands}).
11129 @item info registers @var{regname} @dots{}
11130 Print the @dfn{relativized} value of each specified register @var{regname}.
11131 As discussed in detail below, register values are normally relative to
11132 the selected stack frame. The @var{regname} may be any register name valid on
11133 the machine you are using, with or without the initial @samp{$}.
11136 @anchor{standard registers}
11137 @cindex stack pointer register
11138 @cindex program counter register
11139 @cindex process status register
11140 @cindex frame pointer register
11141 @cindex standard registers
11142 @value{GDBN} has four ``standard'' register names that are available (in
11143 expressions) on most machines---whenever they do not conflict with an
11144 architecture's canonical mnemonics for registers. The register names
11145 @code{$pc} and @code{$sp} are used for the program counter register and
11146 the stack pointer. @code{$fp} is used for a register that contains a
11147 pointer to the current stack frame, and @code{$ps} is used for a
11148 register that contains the processor status. For example,
11149 you could print the program counter in hex with
11156 or print the instruction to be executed next with
11163 or add four to the stack pointer@footnote{This is a way of removing
11164 one word from the stack, on machines where stacks grow downward in
11165 memory (most machines, nowadays). This assumes that the innermost
11166 stack frame is selected; setting @code{$sp} is not allowed when other
11167 stack frames are selected. To pop entire frames off the stack,
11168 regardless of machine architecture, use @code{return};
11169 see @ref{Returning, ,Returning from a Function}.} with
11175 Whenever possible, these four standard register names are available on
11176 your machine even though the machine has different canonical mnemonics,
11177 so long as there is no conflict. The @code{info registers} command
11178 shows the canonical names. For example, on the SPARC, @code{info
11179 registers} displays the processor status register as @code{$psr} but you
11180 can also refer to it as @code{$ps}; and on x86-based machines @code{$ps}
11181 is an alias for the @sc{eflags} register.
11183 @value{GDBN} always considers the contents of an ordinary register as an
11184 integer when the register is examined in this way. Some machines have
11185 special registers which can hold nothing but floating point; these
11186 registers are considered to have floating point values. There is no way
11187 to refer to the contents of an ordinary register as floating point value
11188 (although you can @emph{print} it as a floating point value with
11189 @samp{print/f $@var{regname}}).
11191 Some registers have distinct ``raw'' and ``virtual'' data formats. This
11192 means that the data format in which the register contents are saved by
11193 the operating system is not the same one that your program normally
11194 sees. For example, the registers of the 68881 floating point
11195 coprocessor are always saved in ``extended'' (raw) format, but all C
11196 programs expect to work with ``double'' (virtual) format. In such
11197 cases, @value{GDBN} normally works with the virtual format only (the format
11198 that makes sense for your program), but the @code{info registers} command
11199 prints the data in both formats.
11201 @cindex SSE registers (x86)
11202 @cindex MMX registers (x86)
11203 Some machines have special registers whose contents can be interpreted
11204 in several different ways. For example, modern x86-based machines
11205 have SSE and MMX registers that can hold several values packed
11206 together in several different formats. @value{GDBN} refers to such
11207 registers in @code{struct} notation:
11210 (@value{GDBP}) print $xmm1
11212 v4_float = @{0, 3.43859137e-038, 1.54142831e-044, 1.821688e-044@},
11213 v2_double = @{9.92129282474342e-303, 2.7585945287983262e-313@},
11214 v16_int8 = "\000\000\000\000\3706;\001\v\000\000\000\r\000\000",
11215 v8_int16 = @{0, 0, 14072, 315, 11, 0, 13, 0@},
11216 v4_int32 = @{0, 20657912, 11, 13@},
11217 v2_int64 = @{88725056443645952, 55834574859@},
11218 uint128 = 0x0000000d0000000b013b36f800000000
11223 To set values of such registers, you need to tell @value{GDBN} which
11224 view of the register you wish to change, as if you were assigning
11225 value to a @code{struct} member:
11228 (@value{GDBP}) set $xmm1.uint128 = 0x000000000000000000000000FFFFFFFF
11231 Normally, register values are relative to the selected stack frame
11232 (@pxref{Selection, ,Selecting a Frame}). This means that you get the
11233 value that the register would contain if all stack frames farther in
11234 were exited and their saved registers restored. In order to see the
11235 true contents of hardware registers, you must select the innermost
11236 frame (with @samp{frame 0}).
11238 @cindex caller-saved registers
11239 @cindex call-clobbered registers
11240 @cindex volatile registers
11241 @cindex <not saved> values
11242 Usually ABIs reserve some registers as not needed to be saved by the
11243 callee (a.k.a.: ``caller-saved'', ``call-clobbered'' or ``volatile''
11244 registers). It may therefore not be possible for @value{GDBN} to know
11245 the value a register had before the call (in other words, in the outer
11246 frame), if the register value has since been changed by the callee.
11247 @value{GDBN} tries to deduce where the inner frame saved
11248 (``callee-saved'') registers, from the debug info, unwind info, or the
11249 machine code generated by your compiler. If some register is not
11250 saved, and @value{GDBN} knows the register is ``caller-saved'' (via
11251 its own knowledge of the ABI, or because the debug/unwind info
11252 explicitly says the register's value is undefined), @value{GDBN}
11253 displays @w{@samp{<not saved>}} as the register's value. With targets
11254 that @value{GDBN} has no knowledge of the register saving convention,
11255 if a register was not saved by the callee, then its value and location
11256 in the outer frame are assumed to be the same of the inner frame.
11257 This is usually harmless, because if the register is call-clobbered,
11258 the caller either does not care what is in the register after the
11259 call, or has code to restore the value that it does care about. Note,
11260 however, that if you change such a register in the outer frame, you
11261 may also be affecting the inner frame. Also, the more ``outer'' the
11262 frame is you're looking at, the more likely a call-clobbered
11263 register's value is to be wrong, in the sense that it doesn't actually
11264 represent the value the register had just before the call.
11266 @node Floating Point Hardware
11267 @section Floating Point Hardware
11268 @cindex floating point
11270 Depending on the configuration, @value{GDBN} may be able to give
11271 you more information about the status of the floating point hardware.
11276 Display hardware-dependent information about the floating
11277 point unit. The exact contents and layout vary depending on the
11278 floating point chip. Currently, @samp{info float} is supported on
11279 the ARM and x86 machines.
11283 @section Vector Unit
11284 @cindex vector unit
11286 Depending on the configuration, @value{GDBN} may be able to give you
11287 more information about the status of the vector unit.
11290 @kindex info vector
11292 Display information about the vector unit. The exact contents and
11293 layout vary depending on the hardware.
11296 @node OS Information
11297 @section Operating System Auxiliary Information
11298 @cindex OS information
11300 @value{GDBN} provides interfaces to useful OS facilities that can help
11301 you debug your program.
11303 @cindex auxiliary vector
11304 @cindex vector, auxiliary
11305 Some operating systems supply an @dfn{auxiliary vector} to programs at
11306 startup. This is akin to the arguments and environment that you
11307 specify for a program, but contains a system-dependent variety of
11308 binary values that tell system libraries important details about the
11309 hardware, operating system, and process. Each value's purpose is
11310 identified by an integer tag; the meanings are well-known but system-specific.
11311 Depending on the configuration and operating system facilities,
11312 @value{GDBN} may be able to show you this information. For remote
11313 targets, this functionality may further depend on the remote stub's
11314 support of the @samp{qXfer:auxv:read} packet, see
11315 @ref{qXfer auxiliary vector read}.
11320 Display the auxiliary vector of the inferior, which can be either a
11321 live process or a core dump file. @value{GDBN} prints each tag value
11322 numerically, and also shows names and text descriptions for recognized
11323 tags. Some values in the vector are numbers, some bit masks, and some
11324 pointers to strings or other data. @value{GDBN} displays each value in the
11325 most appropriate form for a recognized tag, and in hexadecimal for
11326 an unrecognized tag.
11329 On some targets, @value{GDBN} can access operating system-specific
11330 information and show it to you. The types of information available
11331 will differ depending on the type of operating system running on the
11332 target. The mechanism used to fetch the data is described in
11333 @ref{Operating System Information}. For remote targets, this
11334 functionality depends on the remote stub's support of the
11335 @samp{qXfer:osdata:read} packet, see @ref{qXfer osdata read}.
11339 @item info os @var{infotype}
11341 Display OS information of the requested type.
11343 On @sc{gnu}/Linux, the following values of @var{infotype} are valid:
11345 @anchor{linux info os infotypes}
11347 @kindex info os cpus
11349 Display the list of all CPUs/cores. For each CPU/core, @value{GDBN} prints
11350 the available fields from /proc/cpuinfo. For each supported architecture
11351 different fields are available. Two common entries are processor which gives
11352 CPU number and bogomips; a system constant that is calculated during
11353 kernel initialization.
11355 @kindex info os files
11357 Display the list of open file descriptors on the target. For each
11358 file descriptor, @value{GDBN} prints the identifier of the process
11359 owning the descriptor, the command of the owning process, the value
11360 of the descriptor, and the target of the descriptor.
11362 @kindex info os modules
11364 Display the list of all loaded kernel modules on the target. For each
11365 module, @value{GDBN} prints the module name, the size of the module in
11366 bytes, the number of times the module is used, the dependencies of the
11367 module, the status of the module, and the address of the loaded module
11370 @kindex info os msg
11372 Display the list of all System V message queues on the target. For each
11373 message queue, @value{GDBN} prints the message queue key, the message
11374 queue identifier, the access permissions, the current number of bytes
11375 on the queue, the current number of messages on the queue, the processes
11376 that last sent and received a message on the queue, the user and group
11377 of the owner and creator of the message queue, the times at which a
11378 message was last sent and received on the queue, and the time at which
11379 the message queue was last changed.
11381 @kindex info os processes
11383 Display the list of processes on the target. For each process,
11384 @value{GDBN} prints the process identifier, the name of the user, the
11385 command corresponding to the process, and the list of processor cores
11386 that the process is currently running on. (To understand what these
11387 properties mean, for this and the following info types, please consult
11388 the general @sc{gnu}/Linux documentation.)
11390 @kindex info os procgroups
11392 Display the list of process groups on the target. For each process,
11393 @value{GDBN} prints the identifier of the process group that it belongs
11394 to, the command corresponding to the process group leader, the process
11395 identifier, and the command line of the process. The list is sorted
11396 first by the process group identifier, then by the process identifier,
11397 so that processes belonging to the same process group are grouped together
11398 and the process group leader is listed first.
11400 @kindex info os semaphores
11402 Display the list of all System V semaphore sets on the target. For each
11403 semaphore set, @value{GDBN} prints the semaphore set key, the semaphore
11404 set identifier, the access permissions, the number of semaphores in the
11405 set, the user and group of the owner and creator of the semaphore set,
11406 and the times at which the semaphore set was operated upon and changed.
11408 @kindex info os shm
11410 Display the list of all System V shared-memory regions on the target.
11411 For each shared-memory region, @value{GDBN} prints the region key,
11412 the shared-memory identifier, the access permissions, the size of the
11413 region, the process that created the region, the process that last
11414 attached to or detached from the region, the current number of live
11415 attaches to the region, and the times at which the region was last
11416 attached to, detach from, and changed.
11418 @kindex info os sockets
11420 Display the list of Internet-domain sockets on the target. For each
11421 socket, @value{GDBN} prints the address and port of the local and
11422 remote endpoints, the current state of the connection, the creator of
11423 the socket, the IP address family of the socket, and the type of the
11426 @kindex info os threads
11428 Display the list of threads running on the target. For each thread,
11429 @value{GDBN} prints the identifier of the process that the thread
11430 belongs to, the command of the process, the thread identifier, and the
11431 processor core that it is currently running on. The main thread of a
11432 process is not listed.
11436 If @var{infotype} is omitted, then list the possible values for
11437 @var{infotype} and the kind of OS information available for each
11438 @var{infotype}. If the target does not return a list of possible
11439 types, this command will report an error.
11442 @node Memory Region Attributes
11443 @section Memory Region Attributes
11444 @cindex memory region attributes
11446 @dfn{Memory region attributes} allow you to describe special handling
11447 required by regions of your target's memory. @value{GDBN} uses
11448 attributes to determine whether to allow certain types of memory
11449 accesses; whether to use specific width accesses; and whether to cache
11450 target memory. By default the description of memory regions is
11451 fetched from the target (if the current target supports this), but the
11452 user can override the fetched regions.
11454 Defined memory regions can be individually enabled and disabled. When a
11455 memory region is disabled, @value{GDBN} uses the default attributes when
11456 accessing memory in that region. Similarly, if no memory regions have
11457 been defined, @value{GDBN} uses the default attributes when accessing
11460 When a memory region is defined, it is given a number to identify it;
11461 to enable, disable, or remove a memory region, you specify that number.
11465 @item mem @var{lower} @var{upper} @var{attributes}@dots{}
11466 Define a memory region bounded by @var{lower} and @var{upper} with
11467 attributes @var{attributes}@dots{}, and add it to the list of regions
11468 monitored by @value{GDBN}. Note that @var{upper} == 0 is a special
11469 case: it is treated as the target's maximum memory address.
11470 (0xffff on 16 bit targets, 0xffffffff on 32 bit targets, etc.)
11473 Discard any user changes to the memory regions and use target-supplied
11474 regions, if available, or no regions if the target does not support.
11477 @item delete mem @var{nums}@dots{}
11478 Remove memory regions @var{nums}@dots{} from the list of regions
11479 monitored by @value{GDBN}.
11481 @kindex disable mem
11482 @item disable mem @var{nums}@dots{}
11483 Disable monitoring of memory regions @var{nums}@dots{}.
11484 A disabled memory region is not forgotten.
11485 It may be enabled again later.
11488 @item enable mem @var{nums}@dots{}
11489 Enable monitoring of memory regions @var{nums}@dots{}.
11493 Print a table of all defined memory regions, with the following columns
11497 @item Memory Region Number
11498 @item Enabled or Disabled.
11499 Enabled memory regions are marked with @samp{y}.
11500 Disabled memory regions are marked with @samp{n}.
11503 The address defining the inclusive lower bound of the memory region.
11506 The address defining the exclusive upper bound of the memory region.
11509 The list of attributes set for this memory region.
11514 @subsection Attributes
11516 @subsubsection Memory Access Mode
11517 The access mode attributes set whether @value{GDBN} may make read or
11518 write accesses to a memory region.
11520 While these attributes prevent @value{GDBN} from performing invalid
11521 memory accesses, they do nothing to prevent the target system, I/O DMA,
11522 etc.@: from accessing memory.
11526 Memory is read only.
11528 Memory is write only.
11530 Memory is read/write. This is the default.
11533 @subsubsection Memory Access Size
11534 The access size attribute tells @value{GDBN} to use specific sized
11535 accesses in the memory region. Often memory mapped device registers
11536 require specific sized accesses. If no access size attribute is
11537 specified, @value{GDBN} may use accesses of any size.
11541 Use 8 bit memory accesses.
11543 Use 16 bit memory accesses.
11545 Use 32 bit memory accesses.
11547 Use 64 bit memory accesses.
11550 @c @subsubsection Hardware/Software Breakpoints
11551 @c The hardware/software breakpoint attributes set whether @value{GDBN}
11552 @c will use hardware or software breakpoints for the internal breakpoints
11553 @c used by the step, next, finish, until, etc. commands.
11557 @c Always use hardware breakpoints
11558 @c @item swbreak (default)
11561 @subsubsection Data Cache
11562 The data cache attributes set whether @value{GDBN} will cache target
11563 memory. While this generally improves performance by reducing debug
11564 protocol overhead, it can lead to incorrect results because @value{GDBN}
11565 does not know about volatile variables or memory mapped device
11570 Enable @value{GDBN} to cache target memory.
11572 Disable @value{GDBN} from caching target memory. This is the default.
11575 @subsection Memory Access Checking
11576 @value{GDBN} can be instructed to refuse accesses to memory that is
11577 not explicitly described. This can be useful if accessing such
11578 regions has undesired effects for a specific target, or to provide
11579 better error checking. The following commands control this behaviour.
11582 @kindex set mem inaccessible-by-default
11583 @item set mem inaccessible-by-default [on|off]
11584 If @code{on} is specified, make @value{GDBN} treat memory not
11585 explicitly described by the memory ranges as non-existent and refuse accesses
11586 to such memory. The checks are only performed if there's at least one
11587 memory range defined. If @code{off} is specified, make @value{GDBN}
11588 treat the memory not explicitly described by the memory ranges as RAM.
11589 The default value is @code{on}.
11590 @kindex show mem inaccessible-by-default
11591 @item show mem inaccessible-by-default
11592 Show the current handling of accesses to unknown memory.
11596 @c @subsubsection Memory Write Verification
11597 @c The memory write verification attributes set whether @value{GDBN}
11598 @c will re-reads data after each write to verify the write was successful.
11602 @c @item noverify (default)
11605 @node Dump/Restore Files
11606 @section Copy Between Memory and a File
11607 @cindex dump/restore files
11608 @cindex append data to a file
11609 @cindex dump data to a file
11610 @cindex restore data from a file
11612 You can use the commands @code{dump}, @code{append}, and
11613 @code{restore} to copy data between target memory and a file. The
11614 @code{dump} and @code{append} commands write data to a file, and the
11615 @code{restore} command reads data from a file back into the inferior's
11616 memory. Files may be in binary, Motorola S-record, Intel hex,
11617 Tektronix Hex, or Verilog Hex format; however, @value{GDBN} can only
11618 append to binary files, and cannot read from Verilog Hex files.
11623 @item dump @r{[}@var{format}@r{]} memory @var{filename} @var{start_addr} @var{end_addr}
11624 @itemx dump @r{[}@var{format}@r{]} value @var{filename} @var{expr}
11625 Dump the contents of memory from @var{start_addr} to @var{end_addr},
11626 or the value of @var{expr}, to @var{filename} in the given format.
11628 The @var{format} parameter may be any one of:
11635 Motorola S-record format.
11637 Tektronix Hex format.
11639 Verilog Hex format.
11642 @value{GDBN} uses the same definitions of these formats as the
11643 @sc{gnu} binary utilities, like @samp{objdump} and @samp{objcopy}. If
11644 @var{format} is omitted, @value{GDBN} dumps the data in raw binary
11648 @item append @r{[}binary@r{]} memory @var{filename} @var{start_addr} @var{end_addr}
11649 @itemx append @r{[}binary@r{]} value @var{filename} @var{expr}
11650 Append the contents of memory from @var{start_addr} to @var{end_addr},
11651 or the value of @var{expr}, to the file @var{filename}, in raw binary form.
11652 (@value{GDBN} can only append data to files in raw binary form.)
11655 @item restore @var{filename} @r{[}binary@r{]} @var{bias} @var{start} @var{end}
11656 Restore the contents of file @var{filename} into memory. The
11657 @code{restore} command can automatically recognize any known @sc{bfd}
11658 file format, except for raw binary. To restore a raw binary file you
11659 must specify the optional keyword @code{binary} after the filename.
11661 If @var{bias} is non-zero, its value will be added to the addresses
11662 contained in the file. Binary files always start at address zero, so
11663 they will be restored at address @var{bias}. Other bfd files have
11664 a built-in location; they will be restored at offset @var{bias}
11665 from that location.
11667 If @var{start} and/or @var{end} are non-zero, then only data between
11668 file offset @var{start} and file offset @var{end} will be restored.
11669 These offsets are relative to the addresses in the file, before
11670 the @var{bias} argument is applied.
11674 @node Core File Generation
11675 @section How to Produce a Core File from Your Program
11676 @cindex dump core from inferior
11678 A @dfn{core file} or @dfn{core dump} is a file that records the memory
11679 image of a running process and its process status (register values
11680 etc.). Its primary use is post-mortem debugging of a program that
11681 crashed while it ran outside a debugger. A program that crashes
11682 automatically produces a core file, unless this feature is disabled by
11683 the user. @xref{Files}, for information on invoking @value{GDBN} in
11684 the post-mortem debugging mode.
11686 Occasionally, you may wish to produce a core file of the program you
11687 are debugging in order to preserve a snapshot of its state.
11688 @value{GDBN} has a special command for that.
11692 @kindex generate-core-file
11693 @item generate-core-file [@var{file}]
11694 @itemx gcore [@var{file}]
11695 Produce a core dump of the inferior process. The optional argument
11696 @var{file} specifies the file name where to put the core dump. If not
11697 specified, the file name defaults to @file{core.@var{pid}}, where
11698 @var{pid} is the inferior process ID.
11700 Note that this command is implemented only for some systems (as of
11701 this writing, @sc{gnu}/Linux, FreeBSD, Solaris, and S390).
11703 On @sc{gnu}/Linux, this command can take into account the value of the
11704 file @file{/proc/@var{pid}/coredump_filter} when generating the core
11705 dump (@pxref{set use-coredump-filter}), and by default honors the
11706 @code{VM_DONTDUMP} flag for mappings where it is present in the file
11707 @file{/proc/@var{pid}/smaps} (@pxref{set dump-excluded-mappings}).
11709 @kindex set use-coredump-filter
11710 @anchor{set use-coredump-filter}
11711 @item set use-coredump-filter on
11712 @itemx set use-coredump-filter off
11713 Enable or disable the use of the file
11714 @file{/proc/@var{pid}/coredump_filter} when generating core dump
11715 files. This file is used by the Linux kernel to decide what types of
11716 memory mappings will be dumped or ignored when generating a core dump
11717 file. @var{pid} is the process ID of a currently running process.
11719 To make use of this feature, you have to write in the
11720 @file{/proc/@var{pid}/coredump_filter} file a value, in hexadecimal,
11721 which is a bit mask representing the memory mapping types. If a bit
11722 is set in the bit mask, then the memory mappings of the corresponding
11723 types will be dumped; otherwise, they will be ignored. This
11724 configuration is inherited by child processes. For more information
11725 about the bits that can be set in the
11726 @file{/proc/@var{pid}/coredump_filter} file, please refer to the
11727 manpage of @code{core(5)}.
11729 By default, this option is @code{on}. If this option is turned
11730 @code{off}, @value{GDBN} does not read the @file{coredump_filter} file
11731 and instead uses the same default value as the Linux kernel in order
11732 to decide which pages will be dumped in the core dump file. This
11733 value is currently @code{0x33}, which means that bits @code{0}
11734 (anonymous private mappings), @code{1} (anonymous shared mappings),
11735 @code{4} (ELF headers) and @code{5} (private huge pages) are active.
11736 This will cause these memory mappings to be dumped automatically.
11738 @kindex set dump-excluded-mappings
11739 @anchor{set dump-excluded-mappings}
11740 @item set dump-excluded-mappings on
11741 @itemx set dump-excluded-mappings off
11742 If @code{on} is specified, @value{GDBN} will dump memory mappings
11743 marked with the @code{VM_DONTDUMP} flag. This flag is represented in
11744 the file @file{/proc/@var{pid}/smaps} with the acronym @code{dd}.
11746 The default value is @code{off}.
11749 @node Character Sets
11750 @section Character Sets
11751 @cindex character sets
11753 @cindex translating between character sets
11754 @cindex host character set
11755 @cindex target character set
11757 If the program you are debugging uses a different character set to
11758 represent characters and strings than the one @value{GDBN} uses itself,
11759 @value{GDBN} can automatically translate between the character sets for
11760 you. The character set @value{GDBN} uses we call the @dfn{host
11761 character set}; the one the inferior program uses we call the
11762 @dfn{target character set}.
11764 For example, if you are running @value{GDBN} on a @sc{gnu}/Linux system, which
11765 uses the ISO Latin 1 character set, but you are using @value{GDBN}'s
11766 remote protocol (@pxref{Remote Debugging}) to debug a program
11767 running on an IBM mainframe, which uses the @sc{ebcdic} character set,
11768 then the host character set is Latin-1, and the target character set is
11769 @sc{ebcdic}. If you give @value{GDBN} the command @code{set
11770 target-charset EBCDIC-US}, then @value{GDBN} translates between
11771 @sc{ebcdic} and Latin 1 as you print character or string values, or use
11772 character and string literals in expressions.
11774 @value{GDBN} has no way to automatically recognize which character set
11775 the inferior program uses; you must tell it, using the @code{set
11776 target-charset} command, described below.
11778 Here are the commands for controlling @value{GDBN}'s character set
11782 @item set target-charset @var{charset}
11783 @kindex set target-charset
11784 Set the current target character set to @var{charset}. To display the
11785 list of supported target character sets, type
11786 @kbd{@w{set target-charset @key{TAB}@key{TAB}}}.
11788 @item set host-charset @var{charset}
11789 @kindex set host-charset
11790 Set the current host character set to @var{charset}.
11792 By default, @value{GDBN} uses a host character set appropriate to the
11793 system it is running on; you can override that default using the
11794 @code{set host-charset} command. On some systems, @value{GDBN} cannot
11795 automatically determine the appropriate host character set. In this
11796 case, @value{GDBN} uses @samp{UTF-8}.
11798 @value{GDBN} can only use certain character sets as its host character
11799 set. If you type @kbd{@w{set host-charset @key{TAB}@key{TAB}}},
11800 @value{GDBN} will list the host character sets it supports.
11802 @item set charset @var{charset}
11803 @kindex set charset
11804 Set the current host and target character sets to @var{charset}. As
11805 above, if you type @kbd{@w{set charset @key{TAB}@key{TAB}}},
11806 @value{GDBN} will list the names of the character sets that can be used
11807 for both host and target.
11810 @kindex show charset
11811 Show the names of the current host and target character sets.
11813 @item show host-charset
11814 @kindex show host-charset
11815 Show the name of the current host character set.
11817 @item show target-charset
11818 @kindex show target-charset
11819 Show the name of the current target character set.
11821 @item set target-wide-charset @var{charset}
11822 @kindex set target-wide-charset
11823 Set the current target's wide character set to @var{charset}. This is
11824 the character set used by the target's @code{wchar_t} type. To
11825 display the list of supported wide character sets, type
11826 @kbd{@w{set target-wide-charset @key{TAB}@key{TAB}}}.
11828 @item show target-wide-charset
11829 @kindex show target-wide-charset
11830 Show the name of the current target's wide character set.
11833 Here is an example of @value{GDBN}'s character set support in action.
11834 Assume that the following source code has been placed in the file
11835 @file{charset-test.c}:
11841 = @{72, 101, 108, 108, 111, 44, 32, 119,
11842 111, 114, 108, 100, 33, 10, 0@};
11843 char ibm1047_hello[]
11844 = @{200, 133, 147, 147, 150, 107, 64, 166,
11845 150, 153, 147, 132, 90, 37, 0@};
11849 printf ("Hello, world!\n");
11853 In this program, @code{ascii_hello} and @code{ibm1047_hello} are arrays
11854 containing the string @samp{Hello, world!} followed by a newline,
11855 encoded in the @sc{ascii} and @sc{ibm1047} character sets.
11857 We compile the program, and invoke the debugger on it:
11860 $ gcc -g charset-test.c -o charset-test
11861 $ gdb -nw charset-test
11862 GNU gdb 2001-12-19-cvs
11863 Copyright 2001 Free Software Foundation, Inc.
11868 We can use the @code{show charset} command to see what character sets
11869 @value{GDBN} is currently using to interpret and display characters and
11873 (@value{GDBP}) show charset
11874 The current host and target character set is `ISO-8859-1'.
11878 For the sake of printing this manual, let's use @sc{ascii} as our
11879 initial character set:
11881 (@value{GDBP}) set charset ASCII
11882 (@value{GDBP}) show charset
11883 The current host and target character set is `ASCII'.
11887 Let's assume that @sc{ascii} is indeed the correct character set for our
11888 host system --- in other words, let's assume that if @value{GDBN} prints
11889 characters using the @sc{ascii} character set, our terminal will display
11890 them properly. Since our current target character set is also
11891 @sc{ascii}, the contents of @code{ascii_hello} print legibly:
11894 (@value{GDBP}) print ascii_hello
11895 $1 = 0x401698 "Hello, world!\n"
11896 (@value{GDBP}) print ascii_hello[0]
11901 @value{GDBN} uses the target character set for character and string
11902 literals you use in expressions:
11905 (@value{GDBP}) print '+'
11910 The @sc{ascii} character set uses the number 43 to encode the @samp{+}
11913 @value{GDBN} relies on the user to tell it which character set the
11914 target program uses. If we print @code{ibm1047_hello} while our target
11915 character set is still @sc{ascii}, we get jibberish:
11918 (@value{GDBP}) print ibm1047_hello
11919 $4 = 0x4016a8 "\310\205\223\223\226k@@\246\226\231\223\204Z%"
11920 (@value{GDBP}) print ibm1047_hello[0]
11925 If we invoke the @code{set target-charset} followed by @key{TAB}@key{TAB},
11926 @value{GDBN} tells us the character sets it supports:
11929 (@value{GDBP}) set target-charset
11930 ASCII EBCDIC-US IBM1047 ISO-8859-1
11931 (@value{GDBP}) set target-charset
11934 We can select @sc{ibm1047} as our target character set, and examine the
11935 program's strings again. Now the @sc{ascii} string is wrong, but
11936 @value{GDBN} translates the contents of @code{ibm1047_hello} from the
11937 target character set, @sc{ibm1047}, to the host character set,
11938 @sc{ascii}, and they display correctly:
11941 (@value{GDBP}) set target-charset IBM1047
11942 (@value{GDBP}) show charset
11943 The current host character set is `ASCII'.
11944 The current target character set is `IBM1047'.
11945 (@value{GDBP}) print ascii_hello
11946 $6 = 0x401698 "\110\145%%?\054\040\167?\162%\144\041\012"
11947 (@value{GDBP}) print ascii_hello[0]
11949 (@value{GDBP}) print ibm1047_hello
11950 $8 = 0x4016a8 "Hello, world!\n"
11951 (@value{GDBP}) print ibm1047_hello[0]
11956 As above, @value{GDBN} uses the target character set for character and
11957 string literals you use in expressions:
11960 (@value{GDBP}) print '+'
11965 The @sc{ibm1047} character set uses the number 78 to encode the @samp{+}
11968 @node Caching Target Data
11969 @section Caching Data of Targets
11970 @cindex caching data of targets
11972 @value{GDBN} caches data exchanged between the debugger and a target.
11973 Each cache is associated with the address space of the inferior.
11974 @xref{Inferiors and Programs}, about inferior and address space.
11975 Such caching generally improves performance in remote debugging
11976 (@pxref{Remote Debugging}), because it reduces the overhead of the
11977 remote protocol by bundling memory reads and writes into large chunks.
11978 Unfortunately, simply caching everything would lead to incorrect results,
11979 since @value{GDBN} does not necessarily know anything about volatile
11980 values, memory-mapped I/O addresses, etc. Furthermore, in non-stop mode
11981 (@pxref{Non-Stop Mode}) memory can be changed @emph{while} a gdb command
11983 Therefore, by default, @value{GDBN} only caches data
11984 known to be on the stack@footnote{In non-stop mode, it is moderately
11985 rare for a running thread to modify the stack of a stopped thread
11986 in a way that would interfere with a backtrace, and caching of
11987 stack reads provides a significant speed up of remote backtraces.} or
11988 in the code segment.
11989 Other regions of memory can be explicitly marked as
11990 cacheable; @pxref{Memory Region Attributes}.
11993 @kindex set remotecache
11994 @item set remotecache on
11995 @itemx set remotecache off
11996 This option no longer does anything; it exists for compatibility
11999 @kindex show remotecache
12000 @item show remotecache
12001 Show the current state of the obsolete remotecache flag.
12003 @kindex set stack-cache
12004 @item set stack-cache on
12005 @itemx set stack-cache off
12006 Enable or disable caching of stack accesses. When @code{on}, use
12007 caching. By default, this option is @code{on}.
12009 @kindex show stack-cache
12010 @item show stack-cache
12011 Show the current state of data caching for memory accesses.
12013 @kindex set code-cache
12014 @item set code-cache on
12015 @itemx set code-cache off
12016 Enable or disable caching of code segment accesses. When @code{on},
12017 use caching. By default, this option is @code{on}. This improves
12018 performance of disassembly in remote debugging.
12020 @kindex show code-cache
12021 @item show code-cache
12022 Show the current state of target memory cache for code segment
12025 @kindex info dcache
12026 @item info dcache @r{[}line@r{]}
12027 Print the information about the performance of data cache of the
12028 current inferior's address space. The information displayed
12029 includes the dcache width and depth, and for each cache line, its
12030 number, address, and how many times it was referenced. This
12031 command is useful for debugging the data cache operation.
12033 If a line number is specified, the contents of that line will be
12036 @item set dcache size @var{size}
12037 @cindex dcache size
12038 @kindex set dcache size
12039 Set maximum number of entries in dcache (dcache depth above).
12041 @item set dcache line-size @var{line-size}
12042 @cindex dcache line-size
12043 @kindex set dcache line-size
12044 Set number of bytes each dcache entry caches (dcache width above).
12045 Must be a power of 2.
12047 @item show dcache size
12048 @kindex show dcache size
12049 Show maximum number of dcache entries. @xref{Caching Target Data, info dcache}.
12051 @item show dcache line-size
12052 @kindex show dcache line-size
12053 Show default size of dcache lines.
12057 @node Searching Memory
12058 @section Search Memory
12059 @cindex searching memory
12061 Memory can be searched for a particular sequence of bytes with the
12062 @code{find} command.
12066 @item find @r{[}/@var{sn}@r{]} @var{start_addr}, +@var{len}, @var{val1} @r{[}, @var{val2}, @dots{}@r{]}
12067 @itemx find @r{[}/@var{sn}@r{]} @var{start_addr}, @var{end_addr}, @var{val1} @r{[}, @var{val2}, @dots{}@r{]}
12068 Search memory for the sequence of bytes specified by @var{val1}, @var{val2},
12069 etc. The search begins at address @var{start_addr} and continues for either
12070 @var{len} bytes or through to @var{end_addr} inclusive.
12073 @var{s} and @var{n} are optional parameters.
12074 They may be specified in either order, apart or together.
12077 @item @var{s}, search query size
12078 The size of each search query value.
12084 halfwords (two bytes)
12088 giant words (eight bytes)
12091 All values are interpreted in the current language.
12092 This means, for example, that if the current source language is C/C@t{++}
12093 then searching for the string ``hello'' includes the trailing '\0'.
12094 The null terminator can be removed from searching by using casts,
12095 e.g.: @samp{@{char[5]@}"hello"}.
12097 If the value size is not specified, it is taken from the
12098 value's type in the current language.
12099 This is useful when one wants to specify the search
12100 pattern as a mixture of types.
12101 Note that this means, for example, that in the case of C-like languages
12102 a search for an untyped 0x42 will search for @samp{(int) 0x42}
12103 which is typically four bytes.
12105 @item @var{n}, maximum number of finds
12106 The maximum number of matches to print. The default is to print all finds.
12109 You can use strings as search values. Quote them with double-quotes
12111 The string value is copied into the search pattern byte by byte,
12112 regardless of the endianness of the target and the size specification.
12114 The address of each match found is printed as well as a count of the
12115 number of matches found.
12117 The address of the last value found is stored in convenience variable
12119 A count of the number of matches is stored in @samp{$numfound}.
12121 For example, if stopped at the @code{printf} in this function:
12127 static char hello[] = "hello-hello";
12128 static struct @{ char c; short s; int i; @}
12129 __attribute__ ((packed)) mixed
12130 = @{ 'c', 0x1234, 0x87654321 @};
12131 printf ("%s\n", hello);
12136 you get during debugging:
12139 (gdb) find &hello[0], +sizeof(hello), "hello"
12140 0x804956d <hello.1620+6>
12142 (gdb) find &hello[0], +sizeof(hello), 'h', 'e', 'l', 'l', 'o'
12143 0x8049567 <hello.1620>
12144 0x804956d <hello.1620+6>
12146 (gdb) find &hello[0], +sizeof(hello), @{char[5]@}"hello"
12147 0x8049567 <hello.1620>
12148 0x804956d <hello.1620+6>
12150 (gdb) find /b1 &hello[0], +sizeof(hello), 'h', 0x65, 'l'
12151 0x8049567 <hello.1620>
12153 (gdb) find &mixed, +sizeof(mixed), (char) 'c', (short) 0x1234, (int) 0x87654321
12154 0x8049560 <mixed.1625>
12156 (gdb) print $numfound
12159 $2 = (void *) 0x8049560
12163 @section Value Sizes
12165 Whenever @value{GDBN} prints a value memory will be allocated within
12166 @value{GDBN} to hold the contents of the value. It is possible in
12167 some languages with dynamic typing systems, that an invalid program
12168 may indicate a value that is incorrectly large, this in turn may cause
12169 @value{GDBN} to try and allocate an overly large ammount of memory.
12172 @kindex set max-value-size
12173 @item set max-value-size @var{bytes}
12174 @itemx set max-value-size unlimited
12175 Set the maximum size of memory that @value{GDBN} will allocate for the
12176 contents of a value to @var{bytes}, trying to display a value that
12177 requires more memory than that will result in an error.
12179 Setting this variable does not effect values that have already been
12180 allocated within @value{GDBN}, only future allocations.
12182 There's a minimum size that @code{max-value-size} can be set to in
12183 order that @value{GDBN} can still operate correctly, this minimum is
12184 currently 16 bytes.
12186 The limit applies to the results of some subexpressions as well as to
12187 complete expressions. For example, an expression denoting a simple
12188 integer component, such as @code{x.y.z}, may fail if the size of
12189 @var{x.y} is dynamic and exceeds @var{bytes}. On the other hand,
12190 @value{GDBN} is sometimes clever; the expression @code{A[i]}, where
12191 @var{A} is an array variable with non-constant size, will generally
12192 succeed regardless of the bounds on @var{A}, as long as the component
12193 size is less than @var{bytes}.
12195 The default value of @code{max-value-size} is currently 64k.
12197 @kindex show max-value-size
12198 @item show max-value-size
12199 Show the maximum size of memory, in bytes, that @value{GDBN} will
12200 allocate for the contents of a value.
12203 @node Optimized Code
12204 @chapter Debugging Optimized Code
12205 @cindex optimized code, debugging
12206 @cindex debugging optimized code
12208 Almost all compilers support optimization. With optimization
12209 disabled, the compiler generates assembly code that corresponds
12210 directly to your source code, in a simplistic way. As the compiler
12211 applies more powerful optimizations, the generated assembly code
12212 diverges from your original source code. With help from debugging
12213 information generated by the compiler, @value{GDBN} can map from
12214 the running program back to constructs from your original source.
12216 @value{GDBN} is more accurate with optimization disabled. If you
12217 can recompile without optimization, it is easier to follow the
12218 progress of your program during debugging. But, there are many cases
12219 where you may need to debug an optimized version.
12221 When you debug a program compiled with @samp{-g -O}, remember that the
12222 optimizer has rearranged your code; the debugger shows you what is
12223 really there. Do not be too surprised when the execution path does not
12224 exactly match your source file! An extreme example: if you define a
12225 variable, but never use it, @value{GDBN} never sees that
12226 variable---because the compiler optimizes it out of existence.
12228 Some things do not work as well with @samp{-g -O} as with just
12229 @samp{-g}, particularly on machines with instruction scheduling. If in
12230 doubt, recompile with @samp{-g} alone, and if this fixes the problem,
12231 please report it to us as a bug (including a test case!).
12232 @xref{Variables}, for more information about debugging optimized code.
12235 * Inline Functions:: How @value{GDBN} presents inlining
12236 * Tail Call Frames:: @value{GDBN} analysis of jumps to functions
12239 @node Inline Functions
12240 @section Inline Functions
12241 @cindex inline functions, debugging
12243 @dfn{Inlining} is an optimization that inserts a copy of the function
12244 body directly at each call site, instead of jumping to a shared
12245 routine. @value{GDBN} displays inlined functions just like
12246 non-inlined functions. They appear in backtraces. You can view their
12247 arguments and local variables, step into them with @code{step}, skip
12248 them with @code{next}, and escape from them with @code{finish}.
12249 You can check whether a function was inlined by using the
12250 @code{info frame} command.
12252 For @value{GDBN} to support inlined functions, the compiler must
12253 record information about inlining in the debug information ---
12254 @value{NGCC} using the @sc{dwarf 2} format does this, and several
12255 other compilers do also. @value{GDBN} only supports inlined functions
12256 when using @sc{dwarf 2}. Versions of @value{NGCC} before 4.1
12257 do not emit two required attributes (@samp{DW_AT_call_file} and
12258 @samp{DW_AT_call_line}); @value{GDBN} does not display inlined
12259 function calls with earlier versions of @value{NGCC}. It instead
12260 displays the arguments and local variables of inlined functions as
12261 local variables in the caller.
12263 The body of an inlined function is directly included at its call site;
12264 unlike a non-inlined function, there are no instructions devoted to
12265 the call. @value{GDBN} still pretends that the call site and the
12266 start of the inlined function are different instructions. Stepping to
12267 the call site shows the call site, and then stepping again shows
12268 the first line of the inlined function, even though no additional
12269 instructions are executed.
12271 This makes source-level debugging much clearer; you can see both the
12272 context of the call and then the effect of the call. Only stepping by
12273 a single instruction using @code{stepi} or @code{nexti} does not do
12274 this; single instruction steps always show the inlined body.
12276 There are some ways that @value{GDBN} does not pretend that inlined
12277 function calls are the same as normal calls:
12281 Setting breakpoints at the call site of an inlined function may not
12282 work, because the call site does not contain any code. @value{GDBN}
12283 may incorrectly move the breakpoint to the next line of the enclosing
12284 function, after the call. This limitation will be removed in a future
12285 version of @value{GDBN}; until then, set a breakpoint on an earlier line
12286 or inside the inlined function instead.
12289 @value{GDBN} cannot locate the return value of inlined calls after
12290 using the @code{finish} command. This is a limitation of compiler-generated
12291 debugging information; after @code{finish}, you can step to the next line
12292 and print a variable where your program stored the return value.
12296 @node Tail Call Frames
12297 @section Tail Call Frames
12298 @cindex tail call frames, debugging
12300 Function @code{B} can call function @code{C} in its very last statement. In
12301 unoptimized compilation the call of @code{C} is immediately followed by return
12302 instruction at the end of @code{B} code. Optimizing compiler may replace the
12303 call and return in function @code{B} into one jump to function @code{C}
12304 instead. Such use of a jump instruction is called @dfn{tail call}.
12306 During execution of function @code{C}, there will be no indication in the
12307 function call stack frames that it was tail-called from @code{B}. If function
12308 @code{A} regularly calls function @code{B} which tail-calls function @code{C},
12309 then @value{GDBN} will see @code{A} as the caller of @code{C}. However, in
12310 some cases @value{GDBN} can determine that @code{C} was tail-called from
12311 @code{B}, and it will then create fictitious call frame for that, with the
12312 return address set up as if @code{B} called @code{C} normally.
12314 This functionality is currently supported only by DWARF 2 debugging format and
12315 the compiler has to produce @samp{DW_TAG_call_site} tags. With
12316 @value{NGCC}, you need to specify @option{-O -g} during compilation, to get
12319 @kbd{info frame} command (@pxref{Frame Info}) will indicate the tail call frame
12320 kind by text @code{tail call frame} such as in this sample @value{GDBN} output:
12324 0x40066b <b(int, double)+11>: jmp 0x400640 <c(int, double)>
12326 Stack level 1, frame at 0x7fffffffda30:
12327 rip = 0x40066d in b (amd64-entry-value.cc:59); saved rip 0x4004c5
12328 tail call frame, caller of frame at 0x7fffffffda30
12329 source language c++.
12330 Arglist at unknown address.
12331 Locals at unknown address, Previous frame's sp is 0x7fffffffda30
12334 The detection of all the possible code path executions can find them ambiguous.
12335 There is no execution history stored (possible @ref{Reverse Execution} is never
12336 used for this purpose) and the last known caller could have reached the known
12337 callee by multiple different jump sequences. In such case @value{GDBN} still
12338 tries to show at least all the unambiguous top tail callers and all the
12339 unambiguous bottom tail calees, if any.
12342 @anchor{set debug entry-values}
12343 @item set debug entry-values
12344 @kindex set debug entry-values
12345 When set to on, enables printing of analysis messages for both frame argument
12346 values at function entry and tail calls. It will show all the possible valid
12347 tail calls code paths it has considered. It will also print the intersection
12348 of them with the final unambiguous (possibly partial or even empty) code path
12351 @item show debug entry-values
12352 @kindex show debug entry-values
12353 Show the current state of analysis messages printing for both frame argument
12354 values at function entry and tail calls.
12357 The analysis messages for tail calls can for example show why the virtual tail
12358 call frame for function @code{c} has not been recognized (due to the indirect
12359 reference by variable @code{x}):
12362 static void __attribute__((noinline, noclone)) c (void);
12363 void (*x) (void) = c;
12364 static void __attribute__((noinline, noclone)) a (void) @{ x++; @}
12365 static void __attribute__((noinline, noclone)) c (void) @{ a (); @}
12366 int main (void) @{ x (); return 0; @}
12368 Breakpoint 1, DW_OP_entry_value resolving cannot find
12369 DW_TAG_call_site 0x40039a in main
12371 3 static void __attribute__((noinline, noclone)) a (void) @{ x++; @}
12374 #1 0x000000000040039a in main () at t.c:5
12377 Another possibility is an ambiguous virtual tail call frames resolution:
12381 static void __attribute__((noinline, noclone)) f (void) @{ i++; @}
12382 static void __attribute__((noinline, noclone)) e (void) @{ f (); @}
12383 static void __attribute__((noinline, noclone)) d (void) @{ f (); @}
12384 static void __attribute__((noinline, noclone)) c (void) @{ d (); @}
12385 static void __attribute__((noinline, noclone)) b (void)
12386 @{ if (i) c (); else e (); @}
12387 static void __attribute__((noinline, noclone)) a (void) @{ b (); @}
12388 int main (void) @{ a (); return 0; @}
12390 tailcall: initial: 0x4004d2(a) 0x4004ce(b) 0x4004b2(c) 0x4004a2(d)
12391 tailcall: compare: 0x4004d2(a) 0x4004cc(b) 0x400492(e)
12392 tailcall: reduced: 0x4004d2(a) |
12395 #1 0x00000000004004d2 in a () at t.c:8
12396 #2 0x0000000000400395 in main () at t.c:9
12399 @set CALLSEQ1A @code{main@value{ARROW}a@value{ARROW}b@value{ARROW}c@value{ARROW}d@value{ARROW}f}
12400 @set CALLSEQ2A @code{main@value{ARROW}a@value{ARROW}b@value{ARROW}e@value{ARROW}f}
12402 @c Convert CALLSEQ#A to CALLSEQ#B depending on HAVE_MAKEINFO_CLICK.
12403 @ifset HAVE_MAKEINFO_CLICK
12404 @set ARROW @click{}
12405 @set CALLSEQ1B @clicksequence{@value{CALLSEQ1A}}
12406 @set CALLSEQ2B @clicksequence{@value{CALLSEQ2A}}
12408 @ifclear HAVE_MAKEINFO_CLICK
12410 @set CALLSEQ1B @value{CALLSEQ1A}
12411 @set CALLSEQ2B @value{CALLSEQ2A}
12414 Frames #0 and #2 are real, #1 is a virtual tail call frame.
12415 The code can have possible execution paths @value{CALLSEQ1B} or
12416 @value{CALLSEQ2B}, @value{GDBN} cannot find which one from the inferior state.
12418 @code{initial:} state shows some random possible calling sequence @value{GDBN}
12419 has found. It then finds another possible calling sequcen - that one is
12420 prefixed by @code{compare:}. The non-ambiguous intersection of these two is
12421 printed as the @code{reduced:} calling sequence. That one could have many
12422 futher @code{compare:} and @code{reduced:} statements as long as there remain
12423 any non-ambiguous sequence entries.
12425 For the frame of function @code{b} in both cases there are different possible
12426 @code{$pc} values (@code{0x4004cc} or @code{0x4004ce}), therefore this frame is
12427 also ambigous. The only non-ambiguous frame is the one for function @code{a},
12428 therefore this one is displayed to the user while the ambiguous frames are
12431 There can be also reasons why printing of frame argument values at function
12436 static void __attribute__((noinline, noclone)) c (int i) @{ v++; @}
12437 static void __attribute__((noinline, noclone)) a (int i);
12438 static void __attribute__((noinline, noclone)) b (int i) @{ a (i); @}
12439 static void __attribute__((noinline, noclone)) a (int i)
12440 @{ if (i) b (i - 1); else c (0); @}
12441 int main (void) @{ a (5); return 0; @}
12444 #0 c (i=i@@entry=0) at t.c:2
12445 #1 0x0000000000400428 in a (DW_OP_entry_value resolving has found
12446 function "a" at 0x400420 can call itself via tail calls
12447 i=<optimized out>) at t.c:6
12448 #2 0x000000000040036e in main () at t.c:7
12451 @value{GDBN} cannot find out from the inferior state if and how many times did
12452 function @code{a} call itself (via function @code{b}) as these calls would be
12453 tail calls. Such tail calls would modify thue @code{i} variable, therefore
12454 @value{GDBN} cannot be sure the value it knows would be right - @value{GDBN}
12455 prints @code{<optimized out>} instead.
12458 @chapter C Preprocessor Macros
12460 Some languages, such as C and C@t{++}, provide a way to define and invoke
12461 ``preprocessor macros'' which expand into strings of tokens.
12462 @value{GDBN} can evaluate expressions containing macro invocations, show
12463 the result of macro expansion, and show a macro's definition, including
12464 where it was defined.
12466 You may need to compile your program specially to provide @value{GDBN}
12467 with information about preprocessor macros. Most compilers do not
12468 include macros in their debugging information, even when you compile
12469 with the @option{-g} flag. @xref{Compilation}.
12471 A program may define a macro at one point, remove that definition later,
12472 and then provide a different definition after that. Thus, at different
12473 points in the program, a macro may have different definitions, or have
12474 no definition at all. If there is a current stack frame, @value{GDBN}
12475 uses the macros in scope at that frame's source code line. Otherwise,
12476 @value{GDBN} uses the macros in scope at the current listing location;
12479 Whenever @value{GDBN} evaluates an expression, it always expands any
12480 macro invocations present in the expression. @value{GDBN} also provides
12481 the following commands for working with macros explicitly.
12485 @kindex macro expand
12486 @cindex macro expansion, showing the results of preprocessor
12487 @cindex preprocessor macro expansion, showing the results of
12488 @cindex expanding preprocessor macros
12489 @item macro expand @var{expression}
12490 @itemx macro exp @var{expression}
12491 Show the results of expanding all preprocessor macro invocations in
12492 @var{expression}. Since @value{GDBN} simply expands macros, but does
12493 not parse the result, @var{expression} need not be a valid expression;
12494 it can be any string of tokens.
12497 @item macro expand-once @var{expression}
12498 @itemx macro exp1 @var{expression}
12499 @cindex expand macro once
12500 @i{(This command is not yet implemented.)} Show the results of
12501 expanding those preprocessor macro invocations that appear explicitly in
12502 @var{expression}. Macro invocations appearing in that expansion are
12503 left unchanged. This command allows you to see the effect of a
12504 particular macro more clearly, without being confused by further
12505 expansions. Since @value{GDBN} simply expands macros, but does not
12506 parse the result, @var{expression} need not be a valid expression; it
12507 can be any string of tokens.
12510 @cindex macro definition, showing
12511 @cindex definition of a macro, showing
12512 @cindex macros, from debug info
12513 @item info macro [-a|-all] [--] @var{macro}
12514 Show the current definition or all definitions of the named @var{macro},
12515 and describe the source location or compiler command-line where that
12516 definition was established. The optional double dash is to signify the end of
12517 argument processing and the beginning of @var{macro} for non C-like macros where
12518 the macro may begin with a hyphen.
12520 @kindex info macros
12521 @item info macros @var{location}
12522 Show all macro definitions that are in effect at the location specified
12523 by @var{location}, and describe the source location or compiler
12524 command-line where those definitions were established.
12526 @kindex macro define
12527 @cindex user-defined macros
12528 @cindex defining macros interactively
12529 @cindex macros, user-defined
12530 @item macro define @var{macro} @var{replacement-list}
12531 @itemx macro define @var{macro}(@var{arglist}) @var{replacement-list}
12532 Introduce a definition for a preprocessor macro named @var{macro},
12533 invocations of which are replaced by the tokens given in
12534 @var{replacement-list}. The first form of this command defines an
12535 ``object-like'' macro, which takes no arguments; the second form
12536 defines a ``function-like'' macro, which takes the arguments given in
12539 A definition introduced by this command is in scope in every
12540 expression evaluated in @value{GDBN}, until it is removed with the
12541 @code{macro undef} command, described below. The definition overrides
12542 all definitions for @var{macro} present in the program being debugged,
12543 as well as any previous user-supplied definition.
12545 @kindex macro undef
12546 @item macro undef @var{macro}
12547 Remove any user-supplied definition for the macro named @var{macro}.
12548 This command only affects definitions provided with the @code{macro
12549 define} command, described above; it cannot remove definitions present
12550 in the program being debugged.
12554 List all the macros defined using the @code{macro define} command.
12557 @cindex macros, example of debugging with
12558 Here is a transcript showing the above commands in action. First, we
12559 show our source files:
12564 #include "sample.h"
12567 #define ADD(x) (M + x)
12572 printf ("Hello, world!\n");
12574 printf ("We're so creative.\n");
12576 printf ("Goodbye, world!\n");
12583 Now, we compile the program using the @sc{gnu} C compiler,
12584 @value{NGCC}. We pass the @option{-gdwarf-2}@footnote{This is the
12585 minimum. Recent versions of @value{NGCC} support @option{-gdwarf-3}
12586 and @option{-gdwarf-4}; we recommend always choosing the most recent
12587 version of DWARF.} @emph{and} @option{-g3} flags to ensure the compiler
12588 includes information about preprocessor macros in the debugging
12592 $ gcc -gdwarf-2 -g3 sample.c -o sample
12596 Now, we start @value{GDBN} on our sample program:
12600 GNU gdb 2002-05-06-cvs
12601 Copyright 2002 Free Software Foundation, Inc.
12602 GDB is free software, @dots{}
12606 We can expand macros and examine their definitions, even when the
12607 program is not running. @value{GDBN} uses the current listing position
12608 to decide which macro definitions are in scope:
12611 (@value{GDBP}) list main
12614 5 #define ADD(x) (M + x)
12619 10 printf ("Hello, world!\n");
12621 12 printf ("We're so creative.\n");
12622 (@value{GDBP}) info macro ADD
12623 Defined at /home/jimb/gdb/macros/play/sample.c:5
12624 #define ADD(x) (M + x)
12625 (@value{GDBP}) info macro Q
12626 Defined at /home/jimb/gdb/macros/play/sample.h:1
12627 included at /home/jimb/gdb/macros/play/sample.c:2
12629 (@value{GDBP}) macro expand ADD(1)
12630 expands to: (42 + 1)
12631 (@value{GDBP}) macro expand-once ADD(1)
12632 expands to: once (M + 1)
12636 In the example above, note that @code{macro expand-once} expands only
12637 the macro invocation explicit in the original text --- the invocation of
12638 @code{ADD} --- but does not expand the invocation of the macro @code{M},
12639 which was introduced by @code{ADD}.
12641 Once the program is running, @value{GDBN} uses the macro definitions in
12642 force at the source line of the current stack frame:
12645 (@value{GDBP}) break main
12646 Breakpoint 1 at 0x8048370: file sample.c, line 10.
12648 Starting program: /home/jimb/gdb/macros/play/sample
12650 Breakpoint 1, main () at sample.c:10
12651 10 printf ("Hello, world!\n");
12655 At line 10, the definition of the macro @code{N} at line 9 is in force:
12658 (@value{GDBP}) info macro N
12659 Defined at /home/jimb/gdb/macros/play/sample.c:9
12661 (@value{GDBP}) macro expand N Q M
12662 expands to: 28 < 42
12663 (@value{GDBP}) print N Q M
12668 As we step over directives that remove @code{N}'s definition, and then
12669 give it a new definition, @value{GDBN} finds the definition (or lack
12670 thereof) in force at each point:
12673 (@value{GDBP}) next
12675 12 printf ("We're so creative.\n");
12676 (@value{GDBP}) info macro N
12677 The symbol `N' has no definition as a C/C++ preprocessor macro
12678 at /home/jimb/gdb/macros/play/sample.c:12
12679 (@value{GDBP}) next
12681 14 printf ("Goodbye, world!\n");
12682 (@value{GDBP}) info macro N
12683 Defined at /home/jimb/gdb/macros/play/sample.c:13
12685 (@value{GDBP}) macro expand N Q M
12686 expands to: 1729 < 42
12687 (@value{GDBP}) print N Q M
12692 In addition to source files, macros can be defined on the compilation command
12693 line using the @option{-D@var{name}=@var{value}} syntax. For macros defined in
12694 such a way, @value{GDBN} displays the location of their definition as line zero
12695 of the source file submitted to the compiler.
12698 (@value{GDBP}) info macro __STDC__
12699 Defined at /home/jimb/gdb/macros/play/sample.c:0
12706 @chapter Tracepoints
12707 @c This chapter is based on the documentation written by Michael
12708 @c Snyder, David Taylor, Jim Blandy, and Elena Zannoni.
12710 @cindex tracepoints
12711 In some applications, it is not feasible for the debugger to interrupt
12712 the program's execution long enough for the developer to learn
12713 anything helpful about its behavior. If the program's correctness
12714 depends on its real-time behavior, delays introduced by a debugger
12715 might cause the program to change its behavior drastically, or perhaps
12716 fail, even when the code itself is correct. It is useful to be able
12717 to observe the program's behavior without interrupting it.
12719 Using @value{GDBN}'s @code{trace} and @code{collect} commands, you can
12720 specify locations in the program, called @dfn{tracepoints}, and
12721 arbitrary expressions to evaluate when those tracepoints are reached.
12722 Later, using the @code{tfind} command, you can examine the values
12723 those expressions had when the program hit the tracepoints. The
12724 expressions may also denote objects in memory---structures or arrays,
12725 for example---whose values @value{GDBN} should record; while visiting
12726 a particular tracepoint, you may inspect those objects as if they were
12727 in memory at that moment. However, because @value{GDBN} records these
12728 values without interacting with you, it can do so quickly and
12729 unobtrusively, hopefully not disturbing the program's behavior.
12731 The tracepoint facility is currently available only for remote
12732 targets. @xref{Targets}. In addition, your remote target must know
12733 how to collect trace data. This functionality is implemented in the
12734 remote stub; however, none of the stubs distributed with @value{GDBN}
12735 support tracepoints as of this writing. The format of the remote
12736 packets used to implement tracepoints are described in @ref{Tracepoint
12739 It is also possible to get trace data from a file, in a manner reminiscent
12740 of corefiles; you specify the filename, and use @code{tfind} to search
12741 through the file. @xref{Trace Files}, for more details.
12743 This chapter describes the tracepoint commands and features.
12746 * Set Tracepoints::
12747 * Analyze Collected Data::
12748 * Tracepoint Variables::
12752 @node Set Tracepoints
12753 @section Commands to Set Tracepoints
12755 Before running such a @dfn{trace experiment}, an arbitrary number of
12756 tracepoints can be set. A tracepoint is actually a special type of
12757 breakpoint (@pxref{Set Breaks}), so you can manipulate it using
12758 standard breakpoint commands. For instance, as with breakpoints,
12759 tracepoint numbers are successive integers starting from one, and many
12760 of the commands associated with tracepoints take the tracepoint number
12761 as their argument, to identify which tracepoint to work on.
12763 For each tracepoint, you can specify, in advance, some arbitrary set
12764 of data that you want the target to collect in the trace buffer when
12765 it hits that tracepoint. The collected data can include registers,
12766 local variables, or global data. Later, you can use @value{GDBN}
12767 commands to examine the values these data had at the time the
12768 tracepoint was hit.
12770 Tracepoints do not support every breakpoint feature. Ignore counts on
12771 tracepoints have no effect, and tracepoints cannot run @value{GDBN}
12772 commands when they are hit. Tracepoints may not be thread-specific
12775 @cindex fast tracepoints
12776 Some targets may support @dfn{fast tracepoints}, which are inserted in
12777 a different way (such as with a jump instead of a trap), that is
12778 faster but possibly restricted in where they may be installed.
12780 @cindex static tracepoints
12781 @cindex markers, static tracepoints
12782 @cindex probing markers, static tracepoints
12783 Regular and fast tracepoints are dynamic tracing facilities, meaning
12784 that they can be used to insert tracepoints at (almost) any location
12785 in the target. Some targets may also support controlling @dfn{static
12786 tracepoints} from @value{GDBN}. With static tracing, a set of
12787 instrumentation points, also known as @dfn{markers}, are embedded in
12788 the target program, and can be activated or deactivated by name or
12789 address. These are usually placed at locations which facilitate
12790 investigating what the target is actually doing. @value{GDBN}'s
12791 support for static tracing includes being able to list instrumentation
12792 points, and attach them with @value{GDBN} defined high level
12793 tracepoints that expose the whole range of convenience of
12794 @value{GDBN}'s tracepoints support. Namely, support for collecting
12795 registers values and values of global or local (to the instrumentation
12796 point) variables; tracepoint conditions and trace state variables.
12797 The act of installing a @value{GDBN} static tracepoint on an
12798 instrumentation point, or marker, is referred to as @dfn{probing} a
12799 static tracepoint marker.
12801 @code{gdbserver} supports tracepoints on some target systems.
12802 @xref{Server,,Tracepoints support in @code{gdbserver}}.
12804 This section describes commands to set tracepoints and associated
12805 conditions and actions.
12808 * Create and Delete Tracepoints::
12809 * Enable and Disable Tracepoints::
12810 * Tracepoint Passcounts::
12811 * Tracepoint Conditions::
12812 * Trace State Variables::
12813 * Tracepoint Actions::
12814 * Listing Tracepoints::
12815 * Listing Static Tracepoint Markers::
12816 * Starting and Stopping Trace Experiments::
12817 * Tracepoint Restrictions::
12820 @node Create and Delete Tracepoints
12821 @subsection Create and Delete Tracepoints
12824 @cindex set tracepoint
12826 @item trace @var{location}
12827 The @code{trace} command is very similar to the @code{break} command.
12828 Its argument @var{location} can be any valid location.
12829 @xref{Specify Location}. The @code{trace} command defines a tracepoint,
12830 which is a point in the target program where the debugger will briefly stop,
12831 collect some data, and then allow the program to continue. Setting a tracepoint
12832 or changing its actions takes effect immediately if the remote stub
12833 supports the @samp{InstallInTrace} feature (@pxref{install tracepoint
12835 If remote stub doesn't support the @samp{InstallInTrace} feature, all
12836 these changes don't take effect until the next @code{tstart}
12837 command, and once a trace experiment is running, further changes will
12838 not have any effect until the next trace experiment starts. In addition,
12839 @value{GDBN} supports @dfn{pending tracepoints}---tracepoints whose
12840 address is not yet resolved. (This is similar to pending breakpoints.)
12841 Pending tracepoints are not downloaded to the target and not installed
12842 until they are resolved. The resolution of pending tracepoints requires
12843 @value{GDBN} support---when debugging with the remote target, and
12844 @value{GDBN} disconnects from the remote stub (@pxref{disconnected
12845 tracing}), pending tracepoints can not be resolved (and downloaded to
12846 the remote stub) while @value{GDBN} is disconnected.
12848 Here are some examples of using the @code{trace} command:
12851 (@value{GDBP}) @b{trace foo.c:121} // a source file and line number
12853 (@value{GDBP}) @b{trace +2} // 2 lines forward
12855 (@value{GDBP}) @b{trace my_function} // first source line of function
12857 (@value{GDBP}) @b{trace *my_function} // EXACT start address of function
12859 (@value{GDBP}) @b{trace *0x2117c4} // an address
12863 You can abbreviate @code{trace} as @code{tr}.
12865 @item trace @var{location} if @var{cond}
12866 Set a tracepoint with condition @var{cond}; evaluate the expression
12867 @var{cond} each time the tracepoint is reached, and collect data only
12868 if the value is nonzero---that is, if @var{cond} evaluates as true.
12869 @xref{Tracepoint Conditions, ,Tracepoint Conditions}, for more
12870 information on tracepoint conditions.
12872 @item ftrace @var{location} [ if @var{cond} ]
12873 @cindex set fast tracepoint
12874 @cindex fast tracepoints, setting
12876 The @code{ftrace} command sets a fast tracepoint. For targets that
12877 support them, fast tracepoints will use a more efficient but possibly
12878 less general technique to trigger data collection, such as a jump
12879 instruction instead of a trap, or some sort of hardware support. It
12880 may not be possible to create a fast tracepoint at the desired
12881 location, in which case the command will exit with an explanatory
12884 @value{GDBN} handles arguments to @code{ftrace} exactly as for
12887 On 32-bit x86-architecture systems, fast tracepoints normally need to
12888 be placed at an instruction that is 5 bytes or longer, but can be
12889 placed at 4-byte instructions if the low 64K of memory of the target
12890 program is available to install trampolines. Some Unix-type systems,
12891 such as @sc{gnu}/Linux, exclude low addresses from the program's
12892 address space; but for instance with the Linux kernel it is possible
12893 to let @value{GDBN} use this area by doing a @command{sysctl} command
12894 to set the @code{mmap_min_addr} kernel parameter, as in
12897 sudo sysctl -w vm.mmap_min_addr=32768
12901 which sets the low address to 32K, which leaves plenty of room for
12902 trampolines. The minimum address should be set to a page boundary.
12904 @item strace @var{location} [ if @var{cond} ]
12905 @cindex set static tracepoint
12906 @cindex static tracepoints, setting
12907 @cindex probe static tracepoint marker
12909 The @code{strace} command sets a static tracepoint. For targets that
12910 support it, setting a static tracepoint probes a static
12911 instrumentation point, or marker, found at @var{location}. It may not
12912 be possible to set a static tracepoint at the desired location, in
12913 which case the command will exit with an explanatory message.
12915 @value{GDBN} handles arguments to @code{strace} exactly as for
12916 @code{trace}, with the addition that the user can also specify
12917 @code{-m @var{marker}} as @var{location}. This probes the marker
12918 identified by the @var{marker} string identifier. This identifier
12919 depends on the static tracepoint backend library your program is
12920 using. You can find all the marker identifiers in the @samp{ID} field
12921 of the @code{info static-tracepoint-markers} command output.
12922 @xref{Listing Static Tracepoint Markers,,Listing Static Tracepoint
12923 Markers}. For example, in the following small program using the UST
12929 trace_mark(ust, bar33, "str %s", "FOOBAZ");
12934 the marker id is composed of joining the first two arguments to the
12935 @code{trace_mark} call with a slash, which translates to:
12938 (@value{GDBP}) info static-tracepoint-markers
12939 Cnt Enb ID Address What
12940 1 n ust/bar33 0x0000000000400ddc in main at stexample.c:22
12946 so you may probe the marker above with:
12949 (@value{GDBP}) strace -m ust/bar33
12952 Static tracepoints accept an extra collect action --- @code{collect
12953 $_sdata}. This collects arbitrary user data passed in the probe point
12954 call to the tracing library. In the UST example above, you'll see
12955 that the third argument to @code{trace_mark} is a printf-like format
12956 string. The user data is then the result of running that formating
12957 string against the following arguments. Note that @code{info
12958 static-tracepoint-markers} command output lists that format string in
12959 the @samp{Data:} field.
12961 You can inspect this data when analyzing the trace buffer, by printing
12962 the $_sdata variable like any other variable available to
12963 @value{GDBN}. @xref{Tracepoint Actions,,Tracepoint Action Lists}.
12966 @cindex last tracepoint number
12967 @cindex recent tracepoint number
12968 @cindex tracepoint number
12969 The convenience variable @code{$tpnum} records the tracepoint number
12970 of the most recently set tracepoint.
12972 @kindex delete tracepoint
12973 @cindex tracepoint deletion
12974 @item delete tracepoint @r{[}@var{num}@r{]}
12975 Permanently delete one or more tracepoints. With no argument, the
12976 default is to delete all tracepoints. Note that the regular
12977 @code{delete} command can remove tracepoints also.
12982 (@value{GDBP}) @b{delete trace 1 2 3} // remove three tracepoints
12984 (@value{GDBP}) @b{delete trace} // remove all tracepoints
12988 You can abbreviate this command as @code{del tr}.
12991 @node Enable and Disable Tracepoints
12992 @subsection Enable and Disable Tracepoints
12994 These commands are deprecated; they are equivalent to plain @code{disable} and @code{enable}.
12997 @kindex disable tracepoint
12998 @item disable tracepoint @r{[}@var{num}@r{]}
12999 Disable tracepoint @var{num}, or all tracepoints if no argument
13000 @var{num} is given. A disabled tracepoint will have no effect during
13001 a trace experiment, but it is not forgotten. You can re-enable
13002 a disabled tracepoint using the @code{enable tracepoint} command.
13003 If the command is issued during a trace experiment and the debug target
13004 has support for disabling tracepoints during a trace experiment, then the
13005 change will be effective immediately. Otherwise, it will be applied to the
13006 next trace experiment.
13008 @kindex enable tracepoint
13009 @item enable tracepoint @r{[}@var{num}@r{]}
13010 Enable tracepoint @var{num}, or all tracepoints. If this command is
13011 issued during a trace experiment and the debug target supports enabling
13012 tracepoints during a trace experiment, then the enabled tracepoints will
13013 become effective immediately. Otherwise, they will become effective the
13014 next time a trace experiment is run.
13017 @node Tracepoint Passcounts
13018 @subsection Tracepoint Passcounts
13022 @cindex tracepoint pass count
13023 @item passcount @r{[}@var{n} @r{[}@var{num}@r{]]}
13024 Set the @dfn{passcount} of a tracepoint. The passcount is a way to
13025 automatically stop a trace experiment. If a tracepoint's passcount is
13026 @var{n}, then the trace experiment will be automatically stopped on
13027 the @var{n}'th time that tracepoint is hit. If the tracepoint number
13028 @var{num} is not specified, the @code{passcount} command sets the
13029 passcount of the most recently defined tracepoint. If no passcount is
13030 given, the trace experiment will run until stopped explicitly by the
13036 (@value{GDBP}) @b{passcount 5 2} // Stop on the 5th execution of
13037 @exdent @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @code{// tracepoint 2}
13039 (@value{GDBP}) @b{passcount 12} // Stop on the 12th execution of the
13040 @exdent @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @code{// most recently defined tracepoint.}
13041 (@value{GDBP}) @b{trace foo}
13042 (@value{GDBP}) @b{pass 3}
13043 (@value{GDBP}) @b{trace bar}
13044 (@value{GDBP}) @b{pass 2}
13045 (@value{GDBP}) @b{trace baz}
13046 (@value{GDBP}) @b{pass 1} // Stop tracing when foo has been
13047 @exdent @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @code{// executed 3 times OR when bar has}
13048 @exdent @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @code{// been executed 2 times}
13049 @exdent @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @code{// OR when baz has been executed 1 time.}
13053 @node Tracepoint Conditions
13054 @subsection Tracepoint Conditions
13055 @cindex conditional tracepoints
13056 @cindex tracepoint conditions
13058 The simplest sort of tracepoint collects data every time your program
13059 reaches a specified place. You can also specify a @dfn{condition} for
13060 a tracepoint. A condition is just a Boolean expression in your
13061 programming language (@pxref{Expressions, ,Expressions}). A
13062 tracepoint with a condition evaluates the expression each time your
13063 program reaches it, and data collection happens only if the condition
13066 Tracepoint conditions can be specified when a tracepoint is set, by
13067 using @samp{if} in the arguments to the @code{trace} command.
13068 @xref{Create and Delete Tracepoints, ,Setting Tracepoints}. They can
13069 also be set or changed at any time with the @code{condition} command,
13070 just as with breakpoints.
13072 Unlike breakpoint conditions, @value{GDBN} does not actually evaluate
13073 the conditional expression itself. Instead, @value{GDBN} encodes the
13074 expression into an agent expression (@pxref{Agent Expressions})
13075 suitable for execution on the target, independently of @value{GDBN}.
13076 Global variables become raw memory locations, locals become stack
13077 accesses, and so forth.
13079 For instance, suppose you have a function that is usually called
13080 frequently, but should not be called after an error has occurred. You
13081 could use the following tracepoint command to collect data about calls
13082 of that function that happen while the error code is propagating
13083 through the program; an unconditional tracepoint could end up
13084 collecting thousands of useless trace frames that you would have to
13088 (@value{GDBP}) @kbd{trace normal_operation if errcode > 0}
13091 @node Trace State Variables
13092 @subsection Trace State Variables
13093 @cindex trace state variables
13095 A @dfn{trace state variable} is a special type of variable that is
13096 created and managed by target-side code. The syntax is the same as
13097 that for GDB's convenience variables (a string prefixed with ``$''),
13098 but they are stored on the target. They must be created explicitly,
13099 using a @code{tvariable} command. They are always 64-bit signed
13102 Trace state variables are remembered by @value{GDBN}, and downloaded
13103 to the target along with tracepoint information when the trace
13104 experiment starts. There are no intrinsic limits on the number of
13105 trace state variables, beyond memory limitations of the target.
13107 @cindex convenience variables, and trace state variables
13108 Although trace state variables are managed by the target, you can use
13109 them in print commands and expressions as if they were convenience
13110 variables; @value{GDBN} will get the current value from the target
13111 while the trace experiment is running. Trace state variables share
13112 the same namespace as other ``$'' variables, which means that you
13113 cannot have trace state variables with names like @code{$23} or
13114 @code{$pc}, nor can you have a trace state variable and a convenience
13115 variable with the same name.
13119 @item tvariable $@var{name} [ = @var{expression} ]
13121 The @code{tvariable} command creates a new trace state variable named
13122 @code{$@var{name}}, and optionally gives it an initial value of
13123 @var{expression}. The @var{expression} is evaluated when this command is
13124 entered; the result will be converted to an integer if possible,
13125 otherwise @value{GDBN} will report an error. A subsequent
13126 @code{tvariable} command specifying the same name does not create a
13127 variable, but instead assigns the supplied initial value to the
13128 existing variable of that name, overwriting any previous initial
13129 value. The default initial value is 0.
13131 @item info tvariables
13132 @kindex info tvariables
13133 List all the trace state variables along with their initial values.
13134 Their current values may also be displayed, if the trace experiment is
13137 @item delete tvariable @r{[} $@var{name} @dots{} @r{]}
13138 @kindex delete tvariable
13139 Delete the given trace state variables, or all of them if no arguments
13144 @node Tracepoint Actions
13145 @subsection Tracepoint Action Lists
13149 @cindex tracepoint actions
13150 @item actions @r{[}@var{num}@r{]}
13151 This command will prompt for a list of actions to be taken when the
13152 tracepoint is hit. If the tracepoint number @var{num} is not
13153 specified, this command sets the actions for the one that was most
13154 recently defined (so that you can define a tracepoint and then say
13155 @code{actions} without bothering about its number). You specify the
13156 actions themselves on the following lines, one action at a time, and
13157 terminate the actions list with a line containing just @code{end}. So
13158 far, the only defined actions are @code{collect}, @code{teval}, and
13159 @code{while-stepping}.
13161 @code{actions} is actually equivalent to @code{commands} (@pxref{Break
13162 Commands, ,Breakpoint Command Lists}), except that only the defined
13163 actions are allowed; any other @value{GDBN} command is rejected.
13165 @cindex remove actions from a tracepoint
13166 To remove all actions from a tracepoint, type @samp{actions @var{num}}
13167 and follow it immediately with @samp{end}.
13170 (@value{GDBP}) @b{collect @var{data}} // collect some data
13172 (@value{GDBP}) @b{while-stepping 5} // single-step 5 times, collect data
13174 (@value{GDBP}) @b{end} // signals the end of actions.
13177 In the following example, the action list begins with @code{collect}
13178 commands indicating the things to be collected when the tracepoint is
13179 hit. Then, in order to single-step and collect additional data
13180 following the tracepoint, a @code{while-stepping} command is used,
13181 followed by the list of things to be collected after each step in a
13182 sequence of single steps. The @code{while-stepping} command is
13183 terminated by its own separate @code{end} command. Lastly, the action
13184 list is terminated by an @code{end} command.
13187 (@value{GDBP}) @b{trace foo}
13188 (@value{GDBP}) @b{actions}
13189 Enter actions for tracepoint 1, one per line:
13192 > while-stepping 12
13193 > collect $pc, arr[i]
13198 @kindex collect @r{(tracepoints)}
13199 @item collect@r{[}/@var{mods}@r{]} @var{expr1}, @var{expr2}, @dots{}
13200 Collect values of the given expressions when the tracepoint is hit.
13201 This command accepts a comma-separated list of any valid expressions.
13202 In addition to global, static, or local variables, the following
13203 special arguments are supported:
13207 Collect all registers.
13210 Collect all function arguments.
13213 Collect all local variables.
13216 Collect the return address. This is helpful if you want to see more
13219 @emph{Note:} The return address location can not always be reliably
13220 determined up front, and the wrong address / registers may end up
13221 collected instead. On some architectures the reliability is higher
13222 for tracepoints at function entry, while on others it's the opposite.
13223 When this happens, backtracing will stop because the return address is
13224 found unavailable (unless another collect rule happened to match it).
13227 Collects the number of arguments from the static probe at which the
13228 tracepoint is located.
13229 @xref{Static Probe Points}.
13231 @item $_probe_arg@var{n}
13232 @var{n} is an integer between 0 and 11. Collects the @var{n}th argument
13233 from the static probe at which the tracepoint is located.
13234 @xref{Static Probe Points}.
13237 @vindex $_sdata@r{, collect}
13238 Collect static tracepoint marker specific data. Only available for
13239 static tracepoints. @xref{Tracepoint Actions,,Tracepoint Action
13240 Lists}. On the UST static tracepoints library backend, an
13241 instrumentation point resembles a @code{printf} function call. The
13242 tracing library is able to collect user specified data formatted to a
13243 character string using the format provided by the programmer that
13244 instrumented the program. Other backends have similar mechanisms.
13245 Here's an example of a UST marker call:
13248 const char master_name[] = "$your_name";
13249 trace_mark(channel1, marker1, "hello %s", master_name)
13252 In this case, collecting @code{$_sdata} collects the string
13253 @samp{hello $yourname}. When analyzing the trace buffer, you can
13254 inspect @samp{$_sdata} like any other variable available to
13258 You can give several consecutive @code{collect} commands, each one
13259 with a single argument, or one @code{collect} command with several
13260 arguments separated by commas; the effect is the same.
13262 The optional @var{mods} changes the usual handling of the arguments.
13263 @code{s} requests that pointers to chars be handled as strings, in
13264 particular collecting the contents of the memory being pointed at, up
13265 to the first zero. The upper bound is by default the value of the
13266 @code{print elements} variable; if @code{s} is followed by a decimal
13267 number, that is the upper bound instead. So for instance
13268 @samp{collect/s25 mystr} collects as many as 25 characters at
13271 The command @code{info scope} (@pxref{Symbols, info scope}) is
13272 particularly useful for figuring out what data to collect.
13274 @kindex teval @r{(tracepoints)}
13275 @item teval @var{expr1}, @var{expr2}, @dots{}
13276 Evaluate the given expressions when the tracepoint is hit. This
13277 command accepts a comma-separated list of expressions. The results
13278 are discarded, so this is mainly useful for assigning values to trace
13279 state variables (@pxref{Trace State Variables}) without adding those
13280 values to the trace buffer, as would be the case if the @code{collect}
13283 @kindex while-stepping @r{(tracepoints)}
13284 @item while-stepping @var{n}
13285 Perform @var{n} single-step instruction traces after the tracepoint,
13286 collecting new data after each step. The @code{while-stepping}
13287 command is followed by the list of what to collect while stepping
13288 (followed by its own @code{end} command):
13291 > while-stepping 12
13292 > collect $regs, myglobal
13298 Note that @code{$pc} is not automatically collected by
13299 @code{while-stepping}; you need to explicitly collect that register if
13300 you need it. You may abbreviate @code{while-stepping} as @code{ws} or
13303 @item set default-collect @var{expr1}, @var{expr2}, @dots{}
13304 @kindex set default-collect
13305 @cindex default collection action
13306 This variable is a list of expressions to collect at each tracepoint
13307 hit. It is effectively an additional @code{collect} action prepended
13308 to every tracepoint action list. The expressions are parsed
13309 individually for each tracepoint, so for instance a variable named
13310 @code{xyz} may be interpreted as a global for one tracepoint, and a
13311 local for another, as appropriate to the tracepoint's location.
13313 @item show default-collect
13314 @kindex show default-collect
13315 Show the list of expressions that are collected by default at each
13320 @node Listing Tracepoints
13321 @subsection Listing Tracepoints
13324 @kindex info tracepoints @r{[}@var{n}@dots{}@r{]}
13325 @kindex info tp @r{[}@var{n}@dots{}@r{]}
13326 @cindex information about tracepoints
13327 @item info tracepoints @r{[}@var{num}@dots{}@r{]}
13328 Display information about the tracepoint @var{num}. If you don't
13329 specify a tracepoint number, displays information about all the
13330 tracepoints defined so far. The format is similar to that used for
13331 @code{info breakpoints}; in fact, @code{info tracepoints} is the same
13332 command, simply restricting itself to tracepoints.
13334 A tracepoint's listing may include additional information specific to
13339 its passcount as given by the @code{passcount @var{n}} command
13342 the state about installed on target of each location
13346 (@value{GDBP}) @b{info trace}
13347 Num Type Disp Enb Address What
13348 1 tracepoint keep y 0x0804ab57 in foo() at main.cxx:7
13350 collect globfoo, $regs
13355 2 tracepoint keep y <MULTIPLE>
13357 2.1 y 0x0804859c in func4 at change-loc.h:35
13358 installed on target
13359 2.2 y 0xb7ffc480 in func4 at change-loc.h:35
13360 installed on target
13361 2.3 y <PENDING> set_tracepoint
13362 3 tracepoint keep y 0x080485b1 in foo at change-loc.c:29
13363 not installed on target
13368 This command can be abbreviated @code{info tp}.
13371 @node Listing Static Tracepoint Markers
13372 @subsection Listing Static Tracepoint Markers
13375 @kindex info static-tracepoint-markers
13376 @cindex information about static tracepoint markers
13377 @item info static-tracepoint-markers
13378 Display information about all static tracepoint markers defined in the
13381 For each marker, the following columns are printed:
13385 An incrementing counter, output to help readability. This is not a
13388 The marker ID, as reported by the target.
13389 @item Enabled or Disabled
13390 Probed markers are tagged with @samp{y}. @samp{n} identifies marks
13391 that are not enabled.
13393 Where the marker is in your program, as a memory address.
13395 Where the marker is in the source for your program, as a file and line
13396 number. If the debug information included in the program does not
13397 allow @value{GDBN} to locate the source of the marker, this column
13398 will be left blank.
13402 In addition, the following information may be printed for each marker:
13406 User data passed to the tracing library by the marker call. In the
13407 UST backend, this is the format string passed as argument to the
13409 @item Static tracepoints probing the marker
13410 The list of static tracepoints attached to the marker.
13414 (@value{GDBP}) info static-tracepoint-markers
13415 Cnt ID Enb Address What
13416 1 ust/bar2 y 0x0000000000400e1a in main at stexample.c:25
13417 Data: number1 %d number2 %d
13418 Probed by static tracepoints: #2
13419 2 ust/bar33 n 0x0000000000400c87 in main at stexample.c:24
13425 @node Starting and Stopping Trace Experiments
13426 @subsection Starting and Stopping Trace Experiments
13429 @kindex tstart [ @var{notes} ]
13430 @cindex start a new trace experiment
13431 @cindex collected data discarded
13433 This command starts the trace experiment, and begins collecting data.
13434 It has the side effect of discarding all the data collected in the
13435 trace buffer during the previous trace experiment. If any arguments
13436 are supplied, they are taken as a note and stored with the trace
13437 experiment's state. The notes may be arbitrary text, and are
13438 especially useful with disconnected tracing in a multi-user context;
13439 the notes can explain what the trace is doing, supply user contact
13440 information, and so forth.
13442 @kindex tstop [ @var{notes} ]
13443 @cindex stop a running trace experiment
13445 This command stops the trace experiment. If any arguments are
13446 supplied, they are recorded with the experiment as a note. This is
13447 useful if you are stopping a trace started by someone else, for
13448 instance if the trace is interfering with the system's behavior and
13449 needs to be stopped quickly.
13451 @strong{Note}: a trace experiment and data collection may stop
13452 automatically if any tracepoint's passcount is reached
13453 (@pxref{Tracepoint Passcounts}), or if the trace buffer becomes full.
13456 @cindex status of trace data collection
13457 @cindex trace experiment, status of
13459 This command displays the status of the current trace data
13463 Here is an example of the commands we described so far:
13466 (@value{GDBP}) @b{trace gdb_c_test}
13467 (@value{GDBP}) @b{actions}
13468 Enter actions for tracepoint #1, one per line.
13469 > collect $regs,$locals,$args
13470 > while-stepping 11
13474 (@value{GDBP}) @b{tstart}
13475 [time passes @dots{}]
13476 (@value{GDBP}) @b{tstop}
13479 @anchor{disconnected tracing}
13480 @cindex disconnected tracing
13481 You can choose to continue running the trace experiment even if
13482 @value{GDBN} disconnects from the target, voluntarily or
13483 involuntarily. For commands such as @code{detach}, the debugger will
13484 ask what you want to do with the trace. But for unexpected
13485 terminations (@value{GDBN} crash, network outage), it would be
13486 unfortunate to lose hard-won trace data, so the variable
13487 @code{disconnected-tracing} lets you decide whether the trace should
13488 continue running without @value{GDBN}.
13491 @item set disconnected-tracing on
13492 @itemx set disconnected-tracing off
13493 @kindex set disconnected-tracing
13494 Choose whether a tracing run should continue to run if @value{GDBN}
13495 has disconnected from the target. Note that @code{detach} or
13496 @code{quit} will ask you directly what to do about a running trace no
13497 matter what this variable's setting, so the variable is mainly useful
13498 for handling unexpected situations, such as loss of the network.
13500 @item show disconnected-tracing
13501 @kindex show disconnected-tracing
13502 Show the current choice for disconnected tracing.
13506 When you reconnect to the target, the trace experiment may or may not
13507 still be running; it might have filled the trace buffer in the
13508 meantime, or stopped for one of the other reasons. If it is running,
13509 it will continue after reconnection.
13511 Upon reconnection, the target will upload information about the
13512 tracepoints in effect. @value{GDBN} will then compare that
13513 information to the set of tracepoints currently defined, and attempt
13514 to match them up, allowing for the possibility that the numbers may
13515 have changed due to creation and deletion in the meantime. If one of
13516 the target's tracepoints does not match any in @value{GDBN}, the
13517 debugger will create a new tracepoint, so that you have a number with
13518 which to specify that tracepoint. This matching-up process is
13519 necessarily heuristic, and it may result in useless tracepoints being
13520 created; you may simply delete them if they are of no use.
13522 @cindex circular trace buffer
13523 If your target agent supports a @dfn{circular trace buffer}, then you
13524 can run a trace experiment indefinitely without filling the trace
13525 buffer; when space runs out, the agent deletes already-collected trace
13526 frames, oldest first, until there is enough room to continue
13527 collecting. This is especially useful if your tracepoints are being
13528 hit too often, and your trace gets terminated prematurely because the
13529 buffer is full. To ask for a circular trace buffer, simply set
13530 @samp{circular-trace-buffer} to on. You can set this at any time,
13531 including during tracing; if the agent can do it, it will change
13532 buffer handling on the fly, otherwise it will not take effect until
13536 @item set circular-trace-buffer on
13537 @itemx set circular-trace-buffer off
13538 @kindex set circular-trace-buffer
13539 Choose whether a tracing run should use a linear or circular buffer
13540 for trace data. A linear buffer will not lose any trace data, but may
13541 fill up prematurely, while a circular buffer will discard old trace
13542 data, but it will have always room for the latest tracepoint hits.
13544 @item show circular-trace-buffer
13545 @kindex show circular-trace-buffer
13546 Show the current choice for the trace buffer. Note that this may not
13547 match the agent's current buffer handling, nor is it guaranteed to
13548 match the setting that might have been in effect during a past run,
13549 for instance if you are looking at frames from a trace file.
13554 @item set trace-buffer-size @var{n}
13555 @itemx set trace-buffer-size unlimited
13556 @kindex set trace-buffer-size
13557 Request that the target use a trace buffer of @var{n} bytes. Not all
13558 targets will honor the request; they may have a compiled-in size for
13559 the trace buffer, or some other limitation. Set to a value of
13560 @code{unlimited} or @code{-1} to let the target use whatever size it
13561 likes. This is also the default.
13563 @item show trace-buffer-size
13564 @kindex show trace-buffer-size
13565 Show the current requested size for the trace buffer. Note that this
13566 will only match the actual size if the target supports size-setting,
13567 and was able to handle the requested size. For instance, if the
13568 target can only change buffer size between runs, this variable will
13569 not reflect the change until the next run starts. Use @code{tstatus}
13570 to get a report of the actual buffer size.
13574 @item set trace-user @var{text}
13575 @kindex set trace-user
13577 @item show trace-user
13578 @kindex show trace-user
13580 @item set trace-notes @var{text}
13581 @kindex set trace-notes
13582 Set the trace run's notes.
13584 @item show trace-notes
13585 @kindex show trace-notes
13586 Show the trace run's notes.
13588 @item set trace-stop-notes @var{text}
13589 @kindex set trace-stop-notes
13590 Set the trace run's stop notes. The handling of the note is as for
13591 @code{tstop} arguments; the set command is convenient way to fix a
13592 stop note that is mistaken or incomplete.
13594 @item show trace-stop-notes
13595 @kindex show trace-stop-notes
13596 Show the trace run's stop notes.
13600 @node Tracepoint Restrictions
13601 @subsection Tracepoint Restrictions
13603 @cindex tracepoint restrictions
13604 There are a number of restrictions on the use of tracepoints. As
13605 described above, tracepoint data gathering occurs on the target
13606 without interaction from @value{GDBN}. Thus the full capabilities of
13607 the debugger are not available during data gathering, and then at data
13608 examination time, you will be limited by only having what was
13609 collected. The following items describe some common problems, but it
13610 is not exhaustive, and you may run into additional difficulties not
13616 Tracepoint expressions are intended to gather objects (lvalues). Thus
13617 the full flexibility of GDB's expression evaluator is not available.
13618 You cannot call functions, cast objects to aggregate types, access
13619 convenience variables or modify values (except by assignment to trace
13620 state variables). Some language features may implicitly call
13621 functions (for instance Objective-C fields with accessors), and therefore
13622 cannot be collected either.
13625 Collection of local variables, either individually or in bulk with
13626 @code{$locals} or @code{$args}, during @code{while-stepping} may
13627 behave erratically. The stepping action may enter a new scope (for
13628 instance by stepping into a function), or the location of the variable
13629 may change (for instance it is loaded into a register). The
13630 tracepoint data recorded uses the location information for the
13631 variables that is correct for the tracepoint location. When the
13632 tracepoint is created, it is not possible, in general, to determine
13633 where the steps of a @code{while-stepping} sequence will advance the
13634 program---particularly if a conditional branch is stepped.
13637 Collection of an incompletely-initialized or partially-destroyed object
13638 may result in something that @value{GDBN} cannot display, or displays
13639 in a misleading way.
13642 When @value{GDBN} displays a pointer to character it automatically
13643 dereferences the pointer to also display characters of the string
13644 being pointed to. However, collecting the pointer during tracing does
13645 not automatically collect the string. You need to explicitly
13646 dereference the pointer and provide size information if you want to
13647 collect not only the pointer, but the memory pointed to. For example,
13648 @code{*ptr@@50} can be used to collect the 50 element array pointed to
13652 It is not possible to collect a complete stack backtrace at a
13653 tracepoint. Instead, you may collect the registers and a few hundred
13654 bytes from the stack pointer with something like @code{*(unsigned char *)$esp@@300}
13655 (adjust to use the name of the actual stack pointer register on your
13656 target architecture, and the amount of stack you wish to capture).
13657 Then the @code{backtrace} command will show a partial backtrace when
13658 using a trace frame. The number of stack frames that can be examined
13659 depends on the sizes of the frames in the collected stack. Note that
13660 if you ask for a block so large that it goes past the bottom of the
13661 stack, the target agent may report an error trying to read from an
13665 If you do not collect registers at a tracepoint, @value{GDBN} can
13666 infer that the value of @code{$pc} must be the same as the address of
13667 the tracepoint and use that when you are looking at a trace frame
13668 for that tracepoint. However, this cannot work if the tracepoint has
13669 multiple locations (for instance if it was set in a function that was
13670 inlined), or if it has a @code{while-stepping} loop. In those cases
13671 @value{GDBN} will warn you that it can't infer @code{$pc}, and default
13676 @node Analyze Collected Data
13677 @section Using the Collected Data
13679 After the tracepoint experiment ends, you use @value{GDBN} commands
13680 for examining the trace data. The basic idea is that each tracepoint
13681 collects a trace @dfn{snapshot} every time it is hit and another
13682 snapshot every time it single-steps. All these snapshots are
13683 consecutively numbered from zero and go into a buffer, and you can
13684 examine them later. The way you examine them is to @dfn{focus} on a
13685 specific trace snapshot. When the remote stub is focused on a trace
13686 snapshot, it will respond to all @value{GDBN} requests for memory and
13687 registers by reading from the buffer which belongs to that snapshot,
13688 rather than from @emph{real} memory or registers of the program being
13689 debugged. This means that @strong{all} @value{GDBN} commands
13690 (@code{print}, @code{info registers}, @code{backtrace}, etc.) will
13691 behave as if we were currently debugging the program state as it was
13692 when the tracepoint occurred. Any requests for data that are not in
13693 the buffer will fail.
13696 * tfind:: How to select a trace snapshot
13697 * tdump:: How to display all data for a snapshot
13698 * save tracepoints:: How to save tracepoints for a future run
13702 @subsection @code{tfind @var{n}}
13705 @cindex select trace snapshot
13706 @cindex find trace snapshot
13707 The basic command for selecting a trace snapshot from the buffer is
13708 @code{tfind @var{n}}, which finds trace snapshot number @var{n},
13709 counting from zero. If no argument @var{n} is given, the next
13710 snapshot is selected.
13712 Here are the various forms of using the @code{tfind} command.
13716 Find the first snapshot in the buffer. This is a synonym for
13717 @code{tfind 0} (since 0 is the number of the first snapshot).
13720 Stop debugging trace snapshots, resume @emph{live} debugging.
13723 Same as @samp{tfind none}.
13726 No argument means find the next trace snapshot or find the first
13727 one if no trace snapshot is selected.
13730 Find the previous trace snapshot before the current one. This permits
13731 retracing earlier steps.
13733 @item tfind tracepoint @var{num}
13734 Find the next snapshot associated with tracepoint @var{num}. Search
13735 proceeds forward from the last examined trace snapshot. If no
13736 argument @var{num} is given, it means find the next snapshot collected
13737 for the same tracepoint as the current snapshot.
13739 @item tfind pc @var{addr}
13740 Find the next snapshot associated with the value @var{addr} of the
13741 program counter. Search proceeds forward from the last examined trace
13742 snapshot. If no argument @var{addr} is given, it means find the next
13743 snapshot with the same value of PC as the current snapshot.
13745 @item tfind outside @var{addr1}, @var{addr2}
13746 Find the next snapshot whose PC is outside the given range of
13747 addresses (exclusive).
13749 @item tfind range @var{addr1}, @var{addr2}
13750 Find the next snapshot whose PC is between @var{addr1} and
13751 @var{addr2} (inclusive).
13753 @item tfind line @r{[}@var{file}:@r{]}@var{n}
13754 Find the next snapshot associated with the source line @var{n}. If
13755 the optional argument @var{file} is given, refer to line @var{n} in
13756 that source file. Search proceeds forward from the last examined
13757 trace snapshot. If no argument @var{n} is given, it means find the
13758 next line other than the one currently being examined; thus saying
13759 @code{tfind line} repeatedly can appear to have the same effect as
13760 stepping from line to line in a @emph{live} debugging session.
13763 The default arguments for the @code{tfind} commands are specifically
13764 designed to make it easy to scan through the trace buffer. For
13765 instance, @code{tfind} with no argument selects the next trace
13766 snapshot, and @code{tfind -} with no argument selects the previous
13767 trace snapshot. So, by giving one @code{tfind} command, and then
13768 simply hitting @key{RET} repeatedly you can examine all the trace
13769 snapshots in order. Or, by saying @code{tfind -} and then hitting
13770 @key{RET} repeatedly you can examine the snapshots in reverse order.
13771 The @code{tfind line} command with no argument selects the snapshot
13772 for the next source line executed. The @code{tfind pc} command with
13773 no argument selects the next snapshot with the same program counter
13774 (PC) as the current frame. The @code{tfind tracepoint} command with
13775 no argument selects the next trace snapshot collected by the same
13776 tracepoint as the current one.
13778 In addition to letting you scan through the trace buffer manually,
13779 these commands make it easy to construct @value{GDBN} scripts that
13780 scan through the trace buffer and print out whatever collected data
13781 you are interested in. Thus, if we want to examine the PC, FP, and SP
13782 registers from each trace frame in the buffer, we can say this:
13785 (@value{GDBP}) @b{tfind start}
13786 (@value{GDBP}) @b{while ($trace_frame != -1)}
13787 > printf "Frame %d, PC = %08X, SP = %08X, FP = %08X\n", \
13788 $trace_frame, $pc, $sp, $fp
13792 Frame 0, PC = 0020DC64, SP = 0030BF3C, FP = 0030BF44
13793 Frame 1, PC = 0020DC6C, SP = 0030BF38, FP = 0030BF44
13794 Frame 2, PC = 0020DC70, SP = 0030BF34, FP = 0030BF44
13795 Frame 3, PC = 0020DC74, SP = 0030BF30, FP = 0030BF44
13796 Frame 4, PC = 0020DC78, SP = 0030BF2C, FP = 0030BF44
13797 Frame 5, PC = 0020DC7C, SP = 0030BF28, FP = 0030BF44
13798 Frame 6, PC = 0020DC80, SP = 0030BF24, FP = 0030BF44
13799 Frame 7, PC = 0020DC84, SP = 0030BF20, FP = 0030BF44
13800 Frame 8, PC = 0020DC88, SP = 0030BF1C, FP = 0030BF44
13801 Frame 9, PC = 0020DC8E, SP = 0030BF18, FP = 0030BF44
13802 Frame 10, PC = 00203F6C, SP = 0030BE3C, FP = 0030BF14
13805 Or, if we want to examine the variable @code{X} at each source line in
13809 (@value{GDBP}) @b{tfind start}
13810 (@value{GDBP}) @b{while ($trace_frame != -1)}
13811 > printf "Frame %d, X == %d\n", $trace_frame, X
13821 @subsection @code{tdump}
13823 @cindex dump all data collected at tracepoint
13824 @cindex tracepoint data, display
13826 This command takes no arguments. It prints all the data collected at
13827 the current trace snapshot.
13830 (@value{GDBP}) @b{trace 444}
13831 (@value{GDBP}) @b{actions}
13832 Enter actions for tracepoint #2, one per line:
13833 > collect $regs, $locals, $args, gdb_long_test
13836 (@value{GDBP}) @b{tstart}
13838 (@value{GDBP}) @b{tfind line 444}
13839 #0 gdb_test (p1=0x11, p2=0x22, p3=0x33, p4=0x44, p5=0x55, p6=0x66)
13841 444 printp( "%s: arguments = 0x%X 0x%X 0x%X 0x%X 0x%X 0x%X\n", )
13843 (@value{GDBP}) @b{tdump}
13844 Data collected at tracepoint 2, trace frame 1:
13845 d0 0xc4aa0085 -995491707
13849 d4 0x71aea3d 119204413
13852 d7 0x380035 3670069
13853 a0 0x19e24a 1696330
13854 a1 0x3000668 50333288
13856 a3 0x322000 3284992
13857 a4 0x3000698 50333336
13858 a5 0x1ad3cc 1758156
13859 fp 0x30bf3c 0x30bf3c
13860 sp 0x30bf34 0x30bf34
13862 pc 0x20b2c8 0x20b2c8
13866 p = 0x20e5b4 "gdb-test"
13873 gdb_long_test = 17 '\021'
13878 @code{tdump} works by scanning the tracepoint's current collection
13879 actions and printing the value of each expression listed. So
13880 @code{tdump} can fail, if after a run, you change the tracepoint's
13881 actions to mention variables that were not collected during the run.
13883 Also, for tracepoints with @code{while-stepping} loops, @code{tdump}
13884 uses the collected value of @code{$pc} to distinguish between trace
13885 frames that were collected at the tracepoint hit, and frames that were
13886 collected while stepping. This allows it to correctly choose whether
13887 to display the basic list of collections, or the collections from the
13888 body of the while-stepping loop. However, if @code{$pc} was not collected,
13889 then @code{tdump} will always attempt to dump using the basic collection
13890 list, and may fail if a while-stepping frame does not include all the
13891 same data that is collected at the tracepoint hit.
13892 @c This is getting pretty arcane, example would be good.
13894 @node save tracepoints
13895 @subsection @code{save tracepoints @var{filename}}
13896 @kindex save tracepoints
13897 @kindex save-tracepoints
13898 @cindex save tracepoints for future sessions
13900 This command saves all current tracepoint definitions together with
13901 their actions and passcounts, into a file @file{@var{filename}}
13902 suitable for use in a later debugging session. To read the saved
13903 tracepoint definitions, use the @code{source} command (@pxref{Command
13904 Files}). The @w{@code{save-tracepoints}} command is a deprecated
13905 alias for @w{@code{save tracepoints}}
13907 @node Tracepoint Variables
13908 @section Convenience Variables for Tracepoints
13909 @cindex tracepoint variables
13910 @cindex convenience variables for tracepoints
13913 @vindex $trace_frame
13914 @item (int) $trace_frame
13915 The current trace snapshot (a.k.a.@: @dfn{frame}) number, or -1 if no
13916 snapshot is selected.
13918 @vindex $tracepoint
13919 @item (int) $tracepoint
13920 The tracepoint for the current trace snapshot.
13922 @vindex $trace_line
13923 @item (int) $trace_line
13924 The line number for the current trace snapshot.
13926 @vindex $trace_file
13927 @item (char []) $trace_file
13928 The source file for the current trace snapshot.
13930 @vindex $trace_func
13931 @item (char []) $trace_func
13932 The name of the function containing @code{$tracepoint}.
13935 Note: @code{$trace_file} is not suitable for use in @code{printf},
13936 use @code{output} instead.
13938 Here's a simple example of using these convenience variables for
13939 stepping through all the trace snapshots and printing some of their
13940 data. Note that these are not the same as trace state variables,
13941 which are managed by the target.
13944 (@value{GDBP}) @b{tfind start}
13946 (@value{GDBP}) @b{while $trace_frame != -1}
13947 > output $trace_file
13948 > printf ", line %d (tracepoint #%d)\n", $trace_line, $tracepoint
13954 @section Using Trace Files
13955 @cindex trace files
13957 In some situations, the target running a trace experiment may no
13958 longer be available; perhaps it crashed, or the hardware was needed
13959 for a different activity. To handle these cases, you can arrange to
13960 dump the trace data into a file, and later use that file as a source
13961 of trace data, via the @code{target tfile} command.
13966 @item tsave [ -r ] @var{filename}
13967 @itemx tsave [-ctf] @var{dirname}
13968 Save the trace data to @var{filename}. By default, this command
13969 assumes that @var{filename} refers to the host filesystem, so if
13970 necessary @value{GDBN} will copy raw trace data up from the target and
13971 then save it. If the target supports it, you can also supply the
13972 optional argument @code{-r} (``remote'') to direct the target to save
13973 the data directly into @var{filename} in its own filesystem, which may be
13974 more efficient if the trace buffer is very large. (Note, however, that
13975 @code{target tfile} can only read from files accessible to the host.)
13976 By default, this command will save trace frame in tfile format.
13977 You can supply the optional argument @code{-ctf} to save data in CTF
13978 format. The @dfn{Common Trace Format} (CTF) is proposed as a trace format
13979 that can be shared by multiple debugging and tracing tools. Please go to
13980 @indicateurl{http://www.efficios.com/ctf} to get more information.
13982 @kindex target tfile
13986 @item target tfile @var{filename}
13987 @itemx target ctf @var{dirname}
13988 Use the file named @var{filename} or directory named @var{dirname} as
13989 a source of trace data. Commands that examine data work as they do with
13990 a live target, but it is not possible to run any new trace experiments.
13991 @code{tstatus} will report the state of the trace run at the moment
13992 the data was saved, as well as the current trace frame you are examining.
13993 Both @var{filename} and @var{dirname} must be on a filesystem accessible to
13997 (@value{GDBP}) target ctf ctf.ctf
13998 (@value{GDBP}) tfind
13999 Found trace frame 0, tracepoint 2
14000 39 ++a; /* set tracepoint 1 here */
14001 (@value{GDBP}) tdump
14002 Data collected at tracepoint 2, trace frame 0:
14006 c = @{"123", "456", "789", "123", "456", "789"@}
14007 d = @{@{@{a = 1, b = 2@}, @{a = 3, b = 4@}@}, @{@{a = 5, b = 6@}, @{a = 7, b = 8@}@}@}
14015 @chapter Debugging Programs That Use Overlays
14018 If your program is too large to fit completely in your target system's
14019 memory, you can sometimes use @dfn{overlays} to work around this
14020 problem. @value{GDBN} provides some support for debugging programs that
14024 * How Overlays Work:: A general explanation of overlays.
14025 * Overlay Commands:: Managing overlays in @value{GDBN}.
14026 * Automatic Overlay Debugging:: @value{GDBN} can find out which overlays are
14027 mapped by asking the inferior.
14028 * Overlay Sample Program:: A sample program using overlays.
14031 @node How Overlays Work
14032 @section How Overlays Work
14033 @cindex mapped overlays
14034 @cindex unmapped overlays
14035 @cindex load address, overlay's
14036 @cindex mapped address
14037 @cindex overlay area
14039 Suppose you have a computer whose instruction address space is only 64
14040 kilobytes long, but which has much more memory which can be accessed by
14041 other means: special instructions, segment registers, or memory
14042 management hardware, for example. Suppose further that you want to
14043 adapt a program which is larger than 64 kilobytes to run on this system.
14045 One solution is to identify modules of your program which are relatively
14046 independent, and need not call each other directly; call these modules
14047 @dfn{overlays}. Separate the overlays from the main program, and place
14048 their machine code in the larger memory. Place your main program in
14049 instruction memory, but leave at least enough space there to hold the
14050 largest overlay as well.
14052 Now, to call a function located in an overlay, you must first copy that
14053 overlay's machine code from the large memory into the space set aside
14054 for it in the instruction memory, and then jump to its entry point
14057 @c NB: In the below the mapped area's size is greater or equal to the
14058 @c size of all overlays. This is intentional to remind the developer
14059 @c that overlays don't necessarily need to be the same size.
14063 Data Instruction Larger
14064 Address Space Address Space Address Space
14065 +-----------+ +-----------+ +-----------+
14067 +-----------+ +-----------+ +-----------+<-- overlay 1
14068 | program | | main | .----| overlay 1 | load address
14069 | variables | | program | | +-----------+
14070 | and heap | | | | | |
14071 +-----------+ | | | +-----------+<-- overlay 2
14072 | | +-----------+ | | | load address
14073 +-----------+ | | | .-| overlay 2 |
14075 mapped --->+-----------+ | | +-----------+
14076 address | | | | | |
14077 | overlay | <-' | | |
14078 | area | <---' +-----------+<-- overlay 3
14079 | | <---. | | load address
14080 +-----------+ `--| overlay 3 |
14087 @anchor{A code overlay}A code overlay
14091 The diagram (@pxref{A code overlay}) shows a system with separate data
14092 and instruction address spaces. To map an overlay, the program copies
14093 its code from the larger address space to the instruction address space.
14094 Since the overlays shown here all use the same mapped address, only one
14095 may be mapped at a time. For a system with a single address space for
14096 data and instructions, the diagram would be similar, except that the
14097 program variables and heap would share an address space with the main
14098 program and the overlay area.
14100 An overlay loaded into instruction memory and ready for use is called a
14101 @dfn{mapped} overlay; its @dfn{mapped address} is its address in the
14102 instruction memory. An overlay not present (or only partially present)
14103 in instruction memory is called @dfn{unmapped}; its @dfn{load address}
14104 is its address in the larger memory. The mapped address is also called
14105 the @dfn{virtual memory address}, or @dfn{VMA}; the load address is also
14106 called the @dfn{load memory address}, or @dfn{LMA}.
14108 Unfortunately, overlays are not a completely transparent way to adapt a
14109 program to limited instruction memory. They introduce a new set of
14110 global constraints you must keep in mind as you design your program:
14115 Before calling or returning to a function in an overlay, your program
14116 must make sure that overlay is actually mapped. Otherwise, the call or
14117 return will transfer control to the right address, but in the wrong
14118 overlay, and your program will probably crash.
14121 If the process of mapping an overlay is expensive on your system, you
14122 will need to choose your overlays carefully to minimize their effect on
14123 your program's performance.
14126 The executable file you load onto your system must contain each
14127 overlay's instructions, appearing at the overlay's load address, not its
14128 mapped address. However, each overlay's instructions must be relocated
14129 and its symbols defined as if the overlay were at its mapped address.
14130 You can use GNU linker scripts to specify different load and relocation
14131 addresses for pieces of your program; see @ref{Overlay Description,,,
14132 ld.info, Using ld: the GNU linker}.
14135 The procedure for loading executable files onto your system must be able
14136 to load their contents into the larger address space as well as the
14137 instruction and data spaces.
14141 The overlay system described above is rather simple, and could be
14142 improved in many ways:
14147 If your system has suitable bank switch registers or memory management
14148 hardware, you could use those facilities to make an overlay's load area
14149 contents simply appear at their mapped address in instruction space.
14150 This would probably be faster than copying the overlay to its mapped
14151 area in the usual way.
14154 If your overlays are small enough, you could set aside more than one
14155 overlay area, and have more than one overlay mapped at a time.
14158 You can use overlays to manage data, as well as instructions. In
14159 general, data overlays are even less transparent to your design than
14160 code overlays: whereas code overlays only require care when you call or
14161 return to functions, data overlays require care every time you access
14162 the data. Also, if you change the contents of a data overlay, you
14163 must copy its contents back out to its load address before you can copy a
14164 different data overlay into the same mapped area.
14169 @node Overlay Commands
14170 @section Overlay Commands
14172 To use @value{GDBN}'s overlay support, each overlay in your program must
14173 correspond to a separate section of the executable file. The section's
14174 virtual memory address and load memory address must be the overlay's
14175 mapped and load addresses. Identifying overlays with sections allows
14176 @value{GDBN} to determine the appropriate address of a function or
14177 variable, depending on whether the overlay is mapped or not.
14179 @value{GDBN}'s overlay commands all start with the word @code{overlay};
14180 you can abbreviate this as @code{ov} or @code{ovly}. The commands are:
14185 Disable @value{GDBN}'s overlay support. When overlay support is
14186 disabled, @value{GDBN} assumes that all functions and variables are
14187 always present at their mapped addresses. By default, @value{GDBN}'s
14188 overlay support is disabled.
14190 @item overlay manual
14191 @cindex manual overlay debugging
14192 Enable @dfn{manual} overlay debugging. In this mode, @value{GDBN}
14193 relies on you to tell it which overlays are mapped, and which are not,
14194 using the @code{overlay map-overlay} and @code{overlay unmap-overlay}
14195 commands described below.
14197 @item overlay map-overlay @var{overlay}
14198 @itemx overlay map @var{overlay}
14199 @cindex map an overlay
14200 Tell @value{GDBN} that @var{overlay} is now mapped; @var{overlay} must
14201 be the name of the object file section containing the overlay. When an
14202 overlay is mapped, @value{GDBN} assumes it can find the overlay's
14203 functions and variables at their mapped addresses. @value{GDBN} assumes
14204 that any other overlays whose mapped ranges overlap that of
14205 @var{overlay} are now unmapped.
14207 @item overlay unmap-overlay @var{overlay}
14208 @itemx overlay unmap @var{overlay}
14209 @cindex unmap an overlay
14210 Tell @value{GDBN} that @var{overlay} is no longer mapped; @var{overlay}
14211 must be the name of the object file section containing the overlay.
14212 When an overlay is unmapped, @value{GDBN} assumes it can find the
14213 overlay's functions and variables at their load addresses.
14216 Enable @dfn{automatic} overlay debugging. In this mode, @value{GDBN}
14217 consults a data structure the overlay manager maintains in the inferior
14218 to see which overlays are mapped. For details, see @ref{Automatic
14219 Overlay Debugging}.
14221 @item overlay load-target
14222 @itemx overlay load
14223 @cindex reloading the overlay table
14224 Re-read the overlay table from the inferior. Normally, @value{GDBN}
14225 re-reads the table @value{GDBN} automatically each time the inferior
14226 stops, so this command should only be necessary if you have changed the
14227 overlay mapping yourself using @value{GDBN}. This command is only
14228 useful when using automatic overlay debugging.
14230 @item overlay list-overlays
14231 @itemx overlay list
14232 @cindex listing mapped overlays
14233 Display a list of the overlays currently mapped, along with their mapped
14234 addresses, load addresses, and sizes.
14238 Normally, when @value{GDBN} prints a code address, it includes the name
14239 of the function the address falls in:
14242 (@value{GDBP}) print main
14243 $3 = @{int ()@} 0x11a0 <main>
14246 When overlay debugging is enabled, @value{GDBN} recognizes code in
14247 unmapped overlays, and prints the names of unmapped functions with
14248 asterisks around them. For example, if @code{foo} is a function in an
14249 unmapped overlay, @value{GDBN} prints it this way:
14252 (@value{GDBP}) overlay list
14253 No sections are mapped.
14254 (@value{GDBP}) print foo
14255 $5 = @{int (int)@} 0x100000 <*foo*>
14258 When @code{foo}'s overlay is mapped, @value{GDBN} prints the function's
14262 (@value{GDBP}) overlay list
14263 Section .ov.foo.text, loaded at 0x100000 - 0x100034,
14264 mapped at 0x1016 - 0x104a
14265 (@value{GDBP}) print foo
14266 $6 = @{int (int)@} 0x1016 <foo>
14269 When overlay debugging is enabled, @value{GDBN} can find the correct
14270 address for functions and variables in an overlay, whether or not the
14271 overlay is mapped. This allows most @value{GDBN} commands, like
14272 @code{break} and @code{disassemble}, to work normally, even on unmapped
14273 code. However, @value{GDBN}'s breakpoint support has some limitations:
14277 @cindex breakpoints in overlays
14278 @cindex overlays, setting breakpoints in
14279 You can set breakpoints in functions in unmapped overlays, as long as
14280 @value{GDBN} can write to the overlay at its load address.
14282 @value{GDBN} can not set hardware or simulator-based breakpoints in
14283 unmapped overlays. However, if you set a breakpoint at the end of your
14284 overlay manager (and tell @value{GDBN} which overlays are now mapped, if
14285 you are using manual overlay management), @value{GDBN} will re-set its
14286 breakpoints properly.
14290 @node Automatic Overlay Debugging
14291 @section Automatic Overlay Debugging
14292 @cindex automatic overlay debugging
14294 @value{GDBN} can automatically track which overlays are mapped and which
14295 are not, given some simple co-operation from the overlay manager in the
14296 inferior. If you enable automatic overlay debugging with the
14297 @code{overlay auto} command (@pxref{Overlay Commands}), @value{GDBN}
14298 looks in the inferior's memory for certain variables describing the
14299 current state of the overlays.
14301 Here are the variables your overlay manager must define to support
14302 @value{GDBN}'s automatic overlay debugging:
14306 @item @code{_ovly_table}:
14307 This variable must be an array of the following structures:
14312 /* The overlay's mapped address. */
14315 /* The size of the overlay, in bytes. */
14316 unsigned long size;
14318 /* The overlay's load address. */
14321 /* Non-zero if the overlay is currently mapped;
14323 unsigned long mapped;
14327 @item @code{_novlys}:
14328 This variable must be a four-byte signed integer, holding the total
14329 number of elements in @code{_ovly_table}.
14333 To decide whether a particular overlay is mapped or not, @value{GDBN}
14334 looks for an entry in @w{@code{_ovly_table}} whose @code{vma} and
14335 @code{lma} members equal the VMA and LMA of the overlay's section in the
14336 executable file. When @value{GDBN} finds a matching entry, it consults
14337 the entry's @code{mapped} member to determine whether the overlay is
14340 In addition, your overlay manager may define a function called
14341 @code{_ovly_debug_event}. If this function is defined, @value{GDBN}
14342 will silently set a breakpoint there. If the overlay manager then
14343 calls this function whenever it has changed the overlay table, this
14344 will enable @value{GDBN} to accurately keep track of which overlays
14345 are in program memory, and update any breakpoints that may be set
14346 in overlays. This will allow breakpoints to work even if the
14347 overlays are kept in ROM or other non-writable memory while they
14348 are not being executed.
14350 @node Overlay Sample Program
14351 @section Overlay Sample Program
14352 @cindex overlay example program
14354 When linking a program which uses overlays, you must place the overlays
14355 at their load addresses, while relocating them to run at their mapped
14356 addresses. To do this, you must write a linker script (@pxref{Overlay
14357 Description,,, ld.info, Using ld: the GNU linker}). Unfortunately,
14358 since linker scripts are specific to a particular host system, target
14359 architecture, and target memory layout, this manual cannot provide
14360 portable sample code demonstrating @value{GDBN}'s overlay support.
14362 However, the @value{GDBN} source distribution does contain an overlaid
14363 program, with linker scripts for a few systems, as part of its test
14364 suite. The program consists of the following files from
14365 @file{gdb/testsuite/gdb.base}:
14369 The main program file.
14371 A simple overlay manager, used by @file{overlays.c}.
14376 Overlay modules, loaded and used by @file{overlays.c}.
14379 Linker scripts for linking the test program on the @code{d10v-elf}
14380 and @code{m32r-elf} targets.
14383 You can build the test program using the @code{d10v-elf} GCC
14384 cross-compiler like this:
14387 $ d10v-elf-gcc -g -c overlays.c
14388 $ d10v-elf-gcc -g -c ovlymgr.c
14389 $ d10v-elf-gcc -g -c foo.c
14390 $ d10v-elf-gcc -g -c bar.c
14391 $ d10v-elf-gcc -g -c baz.c
14392 $ d10v-elf-gcc -g -c grbx.c
14393 $ d10v-elf-gcc -g overlays.o ovlymgr.o foo.o bar.o \
14394 baz.o grbx.o -Wl,-Td10v.ld -o overlays
14397 The build process is identical for any other architecture, except that
14398 you must substitute the appropriate compiler and linker script for the
14399 target system for @code{d10v-elf-gcc} and @code{d10v.ld}.
14403 @chapter Using @value{GDBN} with Different Languages
14406 Although programming languages generally have common aspects, they are
14407 rarely expressed in the same manner. For instance, in ANSI C,
14408 dereferencing a pointer @code{p} is accomplished by @code{*p}, but in
14409 Modula-2, it is accomplished by @code{p^}. Values can also be
14410 represented (and displayed) differently. Hex numbers in C appear as
14411 @samp{0x1ae}, while in Modula-2 they appear as @samp{1AEH}.
14413 @cindex working language
14414 Language-specific information is built into @value{GDBN} for some languages,
14415 allowing you to express operations like the above in your program's
14416 native language, and allowing @value{GDBN} to output values in a manner
14417 consistent with the syntax of your program's native language. The
14418 language you use to build expressions is called the @dfn{working
14422 * Setting:: Switching between source languages
14423 * Show:: Displaying the language
14424 * Checks:: Type and range checks
14425 * Supported Languages:: Supported languages
14426 * Unsupported Languages:: Unsupported languages
14430 @section Switching Between Source Languages
14432 There are two ways to control the working language---either have @value{GDBN}
14433 set it automatically, or select it manually yourself. You can use the
14434 @code{set language} command for either purpose. On startup, @value{GDBN}
14435 defaults to setting the language automatically. The working language is
14436 used to determine how expressions you type are interpreted, how values
14439 In addition to the working language, every source file that
14440 @value{GDBN} knows about has its own working language. For some object
14441 file formats, the compiler might indicate which language a particular
14442 source file is in. However, most of the time @value{GDBN} infers the
14443 language from the name of the file. The language of a source file
14444 controls whether C@t{++} names are demangled---this way @code{backtrace} can
14445 show each frame appropriately for its own language. There is no way to
14446 set the language of a source file from within @value{GDBN}, but you can
14447 set the language associated with a filename extension. @xref{Show, ,
14448 Displaying the Language}.
14450 This is most commonly a problem when you use a program, such
14451 as @code{cfront} or @code{f2c}, that generates C but is written in
14452 another language. In that case, make the
14453 program use @code{#line} directives in its C output; that way
14454 @value{GDBN} will know the correct language of the source code of the original
14455 program, and will display that source code, not the generated C code.
14458 * Filenames:: Filename extensions and languages.
14459 * Manually:: Setting the working language manually
14460 * Automatically:: Having @value{GDBN} infer the source language
14464 @subsection List of Filename Extensions and Languages
14466 If a source file name ends in one of the following extensions, then
14467 @value{GDBN} infers that its language is the one indicated.
14485 C@t{++} source file
14491 Objective-C source file
14495 Fortran source file
14498 Modula-2 source file
14502 Assembler source file. This actually behaves almost like C, but
14503 @value{GDBN} does not skip over function prologues when stepping.
14506 In addition, you may set the language associated with a filename
14507 extension. @xref{Show, , Displaying the Language}.
14510 @subsection Setting the Working Language
14512 If you allow @value{GDBN} to set the language automatically,
14513 expressions are interpreted the same way in your debugging session and
14516 @kindex set language
14517 If you wish, you may set the language manually. To do this, issue the
14518 command @samp{set language @var{lang}}, where @var{lang} is the name of
14519 a language, such as
14520 @code{c} or @code{modula-2}.
14521 For a list of the supported languages, type @samp{set language}.
14523 Setting the language manually prevents @value{GDBN} from updating the working
14524 language automatically. This can lead to confusion if you try
14525 to debug a program when the working language is not the same as the
14526 source language, when an expression is acceptable to both
14527 languages---but means different things. For instance, if the current
14528 source file were written in C, and @value{GDBN} was parsing Modula-2, a
14536 might not have the effect you intended. In C, this means to add
14537 @code{b} and @code{c} and place the result in @code{a}. The result
14538 printed would be the value of @code{a}. In Modula-2, this means to compare
14539 @code{a} to the result of @code{b+c}, yielding a @code{BOOLEAN} value.
14541 @node Automatically
14542 @subsection Having @value{GDBN} Infer the Source Language
14544 To have @value{GDBN} set the working language automatically, use
14545 @samp{set language local} or @samp{set language auto}. @value{GDBN}
14546 then infers the working language. That is, when your program stops in a
14547 frame (usually by encountering a breakpoint), @value{GDBN} sets the
14548 working language to the language recorded for the function in that
14549 frame. If the language for a frame is unknown (that is, if the function
14550 or block corresponding to the frame was defined in a source file that
14551 does not have a recognized extension), the current working language is
14552 not changed, and @value{GDBN} issues a warning.
14554 This may not seem necessary for most programs, which are written
14555 entirely in one source language. However, program modules and libraries
14556 written in one source language can be used by a main program written in
14557 a different source language. Using @samp{set language auto} in this
14558 case frees you from having to set the working language manually.
14561 @section Displaying the Language
14563 The following commands help you find out which language is the
14564 working language, and also what language source files were written in.
14567 @item show language
14568 @anchor{show language}
14569 @kindex show language
14570 Display the current working language. This is the
14571 language you can use with commands such as @code{print} to
14572 build and compute expressions that may involve variables in your program.
14575 @kindex info frame@r{, show the source language}
14576 Display the source language for this frame. This language becomes the
14577 working language if you use an identifier from this frame.
14578 @xref{Frame Info, ,Information about a Frame}, to identify the other
14579 information listed here.
14582 @kindex info source@r{, show the source language}
14583 Display the source language of this source file.
14584 @xref{Symbols, ,Examining the Symbol Table}, to identify the other
14585 information listed here.
14588 In unusual circumstances, you may have source files with extensions
14589 not in the standard list. You can then set the extension associated
14590 with a language explicitly:
14593 @item set extension-language @var{ext} @var{language}
14594 @kindex set extension-language
14595 Tell @value{GDBN} that source files with extension @var{ext} are to be
14596 assumed as written in the source language @var{language}.
14598 @item info extensions
14599 @kindex info extensions
14600 List all the filename extensions and the associated languages.
14604 @section Type and Range Checking
14606 Some languages are designed to guard you against making seemingly common
14607 errors through a series of compile- and run-time checks. These include
14608 checking the type of arguments to functions and operators and making
14609 sure mathematical overflows are caught at run time. Checks such as
14610 these help to ensure a program's correctness once it has been compiled
14611 by eliminating type mismatches and providing active checks for range
14612 errors when your program is running.
14614 By default @value{GDBN} checks for these errors according to the
14615 rules of the current source language. Although @value{GDBN} does not check
14616 the statements in your program, it can check expressions entered directly
14617 into @value{GDBN} for evaluation via the @code{print} command, for example.
14620 * Type Checking:: An overview of type checking
14621 * Range Checking:: An overview of range checking
14624 @cindex type checking
14625 @cindex checks, type
14626 @node Type Checking
14627 @subsection An Overview of Type Checking
14629 Some languages, such as C and C@t{++}, are strongly typed, meaning that the
14630 arguments to operators and functions have to be of the correct type,
14631 otherwise an error occurs. These checks prevent type mismatch
14632 errors from ever causing any run-time problems. For example,
14635 int klass::my_method(char *b) @{ return b ? 1 : 2; @}
14637 (@value{GDBP}) print obj.my_method (0)
14640 (@value{GDBP}) print obj.my_method (0x1234)
14641 Cannot resolve method klass::my_method to any overloaded instance
14644 The second example fails because in C@t{++} the integer constant
14645 @samp{0x1234} is not type-compatible with the pointer parameter type.
14647 For the expressions you use in @value{GDBN} commands, you can tell
14648 @value{GDBN} to not enforce strict type checking or
14649 to treat any mismatches as errors and abandon the expression;
14650 When type checking is disabled, @value{GDBN} successfully evaluates
14651 expressions like the second example above.
14653 Even if type checking is off, there may be other reasons
14654 related to type that prevent @value{GDBN} from evaluating an expression.
14655 For instance, @value{GDBN} does not know how to add an @code{int} and
14656 a @code{struct foo}. These particular type errors have nothing to do
14657 with the language in use and usually arise from expressions which make
14658 little sense to evaluate anyway.
14660 @value{GDBN} provides some additional commands for controlling type checking:
14662 @kindex set check type
14663 @kindex show check type
14665 @item set check type on
14666 @itemx set check type off
14667 Set strict type checking on or off. If any type mismatches occur in
14668 evaluating an expression while type checking is on, @value{GDBN} prints a
14669 message and aborts evaluation of the expression.
14671 @item show check type
14672 Show the current setting of type checking and whether @value{GDBN}
14673 is enforcing strict type checking rules.
14676 @cindex range checking
14677 @cindex checks, range
14678 @node Range Checking
14679 @subsection An Overview of Range Checking
14681 In some languages (such as Modula-2), it is an error to exceed the
14682 bounds of a type; this is enforced with run-time checks. Such range
14683 checking is meant to ensure program correctness by making sure
14684 computations do not overflow, or indices on an array element access do
14685 not exceed the bounds of the array.
14687 For expressions you use in @value{GDBN} commands, you can tell
14688 @value{GDBN} to treat range errors in one of three ways: ignore them,
14689 always treat them as errors and abandon the expression, or issue
14690 warnings but evaluate the expression anyway.
14692 A range error can result from numerical overflow, from exceeding an
14693 array index bound, or when you type a constant that is not a member
14694 of any type. Some languages, however, do not treat overflows as an
14695 error. In many implementations of C, mathematical overflow causes the
14696 result to ``wrap around'' to lower values---for example, if @var{m} is
14697 the largest integer value, and @var{s} is the smallest, then
14700 @var{m} + 1 @result{} @var{s}
14703 This, too, is specific to individual languages, and in some cases
14704 specific to individual compilers or machines. @xref{Supported Languages, ,
14705 Supported Languages}, for further details on specific languages.
14707 @value{GDBN} provides some additional commands for controlling the range checker:
14709 @kindex set check range
14710 @kindex show check range
14712 @item set check range auto
14713 Set range checking on or off based on the current working language.
14714 @xref{Supported Languages, ,Supported Languages}, for the default settings for
14717 @item set check range on
14718 @itemx set check range off
14719 Set range checking on or off, overriding the default setting for the
14720 current working language. A warning is issued if the setting does not
14721 match the language default. If a range error occurs and range checking is on,
14722 then a message is printed and evaluation of the expression is aborted.
14724 @item set check range warn
14725 Output messages when the @value{GDBN} range checker detects a range error,
14726 but attempt to evaluate the expression anyway. Evaluating the
14727 expression may still be impossible for other reasons, such as accessing
14728 memory that the process does not own (a typical example from many Unix
14732 Show the current setting of the range checker, and whether or not it is
14733 being set automatically by @value{GDBN}.
14736 @node Supported Languages
14737 @section Supported Languages
14739 @value{GDBN} supports C, C@t{++}, D, Go, Objective-C, Fortran,
14740 OpenCL C, Pascal, Rust, assembly, Modula-2, and Ada.
14741 @c This is false ...
14742 Some @value{GDBN} features may be used in expressions regardless of the
14743 language you use: the @value{GDBN} @code{@@} and @code{::} operators,
14744 and the @samp{@{type@}addr} construct (@pxref{Expressions,
14745 ,Expressions}) can be used with the constructs of any supported
14748 The following sections detail to what degree each source language is
14749 supported by @value{GDBN}. These sections are not meant to be language
14750 tutorials or references, but serve only as a reference guide to what the
14751 @value{GDBN} expression parser accepts, and what input and output
14752 formats should look like for different languages. There are many good
14753 books written on each of these languages; please look to these for a
14754 language reference or tutorial.
14757 * C:: C and C@t{++}
14760 * Objective-C:: Objective-C
14761 * OpenCL C:: OpenCL C
14762 * Fortran:: Fortran
14765 * Modula-2:: Modula-2
14770 @subsection C and C@t{++}
14772 @cindex C and C@t{++}
14773 @cindex expressions in C or C@t{++}
14775 Since C and C@t{++} are so closely related, many features of @value{GDBN} apply
14776 to both languages. Whenever this is the case, we discuss those languages
14780 @cindex @code{g++}, @sc{gnu} C@t{++} compiler
14781 @cindex @sc{gnu} C@t{++}
14782 The C@t{++} debugging facilities are jointly implemented by the C@t{++}
14783 compiler and @value{GDBN}. Therefore, to debug your C@t{++} code
14784 effectively, you must compile your C@t{++} programs with a supported
14785 C@t{++} compiler, such as @sc{gnu} @code{g++}, or the HP ANSI C@t{++}
14786 compiler (@code{aCC}).
14789 * C Operators:: C and C@t{++} operators
14790 * C Constants:: C and C@t{++} constants
14791 * C Plus Plus Expressions:: C@t{++} expressions
14792 * C Defaults:: Default settings for C and C@t{++}
14793 * C Checks:: C and C@t{++} type and range checks
14794 * Debugging C:: @value{GDBN} and C
14795 * Debugging C Plus Plus:: @value{GDBN} features for C@t{++}
14796 * Decimal Floating Point:: Numbers in Decimal Floating Point format
14800 @subsubsection C and C@t{++} Operators
14802 @cindex C and C@t{++} operators
14804 Operators must be defined on values of specific types. For instance,
14805 @code{+} is defined on numbers, but not on structures. Operators are
14806 often defined on groups of types.
14808 For the purposes of C and C@t{++}, the following definitions hold:
14813 @emph{Integral types} include @code{int} with any of its storage-class
14814 specifiers; @code{char}; @code{enum}; and, for C@t{++}, @code{bool}.
14817 @emph{Floating-point types} include @code{float}, @code{double}, and
14818 @code{long double} (if supported by the target platform).
14821 @emph{Pointer types} include all types defined as @code{(@var{type} *)}.
14824 @emph{Scalar types} include all of the above.
14829 The following operators are supported. They are listed here
14830 in order of increasing precedence:
14834 The comma or sequencing operator. Expressions in a comma-separated list
14835 are evaluated from left to right, with the result of the entire
14836 expression being the last expression evaluated.
14839 Assignment. The value of an assignment expression is the value
14840 assigned. Defined on scalar types.
14843 Used in an expression of the form @w{@code{@var{a} @var{op}= @var{b}}},
14844 and translated to @w{@code{@var{a} = @var{a op b}}}.
14845 @w{@code{@var{op}=}} and @code{=} have the same precedence. The operator
14846 @var{op} is any one of the operators @code{|}, @code{^}, @code{&},
14847 @code{<<}, @code{>>}, @code{+}, @code{-}, @code{*}, @code{/}, @code{%}.
14850 The ternary operator. @code{@var{a} ? @var{b} : @var{c}} can be thought
14851 of as: if @var{a} then @var{b} else @var{c}. The argument @var{a}
14852 should be of an integral type.
14855 Logical @sc{or}. Defined on integral types.
14858 Logical @sc{and}. Defined on integral types.
14861 Bitwise @sc{or}. Defined on integral types.
14864 Bitwise exclusive-@sc{or}. Defined on integral types.
14867 Bitwise @sc{and}. Defined on integral types.
14870 Equality and inequality. Defined on scalar types. The value of these
14871 expressions is 0 for false and non-zero for true.
14873 @item <@r{, }>@r{, }<=@r{, }>=
14874 Less than, greater than, less than or equal, greater than or equal.
14875 Defined on scalar types. The value of these expressions is 0 for false
14876 and non-zero for true.
14879 left shift, and right shift. Defined on integral types.
14882 The @value{GDBN} ``artificial array'' operator (@pxref{Expressions, ,Expressions}).
14885 Addition and subtraction. Defined on integral types, floating-point types and
14888 @item *@r{, }/@r{, }%
14889 Multiplication, division, and modulus. Multiplication and division are
14890 defined on integral and floating-point types. Modulus is defined on
14894 Increment and decrement. When appearing before a variable, the
14895 operation is performed before the variable is used in an expression;
14896 when appearing after it, the variable's value is used before the
14897 operation takes place.
14900 Pointer dereferencing. Defined on pointer types. Same precedence as
14904 Address operator. Defined on variables. Same precedence as @code{++}.
14906 For debugging C@t{++}, @value{GDBN} implements a use of @samp{&} beyond what is
14907 allowed in the C@t{++} language itself: you can use @samp{&(&@var{ref})}
14908 to examine the address
14909 where a C@t{++} reference variable (declared with @samp{&@var{ref}}) is
14913 Negative. Defined on integral and floating-point types. Same
14914 precedence as @code{++}.
14917 Logical negation. Defined on integral types. Same precedence as
14921 Bitwise complement operator. Defined on integral types. Same precedence as
14926 Structure member, and pointer-to-structure member. For convenience,
14927 @value{GDBN} regards the two as equivalent, choosing whether to dereference a
14928 pointer based on the stored type information.
14929 Defined on @code{struct} and @code{union} data.
14932 Dereferences of pointers to members.
14935 Array indexing. @code{@var{a}[@var{i}]} is defined as
14936 @code{*(@var{a}+@var{i})}. Same precedence as @code{->}.
14939 Function parameter list. Same precedence as @code{->}.
14942 C@t{++} scope resolution operator. Defined on @code{struct}, @code{union},
14943 and @code{class} types.
14946 Doubled colons also represent the @value{GDBN} scope operator
14947 (@pxref{Expressions, ,Expressions}). Same precedence as @code{::},
14951 If an operator is redefined in the user code, @value{GDBN} usually
14952 attempts to invoke the redefined version instead of using the operator's
14953 predefined meaning.
14956 @subsubsection C and C@t{++} Constants
14958 @cindex C and C@t{++} constants
14960 @value{GDBN} allows you to express the constants of C and C@t{++} in the
14965 Integer constants are a sequence of digits. Octal constants are
14966 specified by a leading @samp{0} (i.e.@: zero), and hexadecimal constants
14967 by a leading @samp{0x} or @samp{0X}. Constants may also end with a letter
14968 @samp{l}, specifying that the constant should be treated as a
14972 Floating point constants are a sequence of digits, followed by a decimal
14973 point, followed by a sequence of digits, and optionally followed by an
14974 exponent. An exponent is of the form:
14975 @samp{@w{e@r{[[}+@r{]|}-@r{]}@var{nnn}}}, where @var{nnn} is another
14976 sequence of digits. The @samp{+} is optional for positive exponents.
14977 A floating-point constant may also end with a letter @samp{f} or
14978 @samp{F}, specifying that the constant should be treated as being of
14979 the @code{float} (as opposed to the default @code{double}) type; or with
14980 a letter @samp{l} or @samp{L}, which specifies a @code{long double}
14984 Enumerated constants consist of enumerated identifiers, or their
14985 integral equivalents.
14988 Character constants are a single character surrounded by single quotes
14989 (@code{'}), or a number---the ordinal value of the corresponding character
14990 (usually its @sc{ascii} value). Within quotes, the single character may
14991 be represented by a letter or by @dfn{escape sequences}, which are of
14992 the form @samp{\@var{nnn}}, where @var{nnn} is the octal representation
14993 of the character's ordinal value; or of the form @samp{\@var{x}}, where
14994 @samp{@var{x}} is a predefined special character---for example,
14995 @samp{\n} for newline.
14997 Wide character constants can be written by prefixing a character
14998 constant with @samp{L}, as in C. For example, @samp{L'x'} is the wide
14999 form of @samp{x}. The target wide character set is used when
15000 computing the value of this constant (@pxref{Character Sets}).
15003 String constants are a sequence of character constants surrounded by
15004 double quotes (@code{"}). Any valid character constant (as described
15005 above) may appear. Double quotes within the string must be preceded by
15006 a backslash, so for instance @samp{"a\"b'c"} is a string of five
15009 Wide string constants can be written by prefixing a string constant
15010 with @samp{L}, as in C. The target wide character set is used when
15011 computing the value of this constant (@pxref{Character Sets}).
15014 Pointer constants are an integral value. You can also write pointers
15015 to constants using the C operator @samp{&}.
15018 Array constants are comma-separated lists surrounded by braces @samp{@{}
15019 and @samp{@}}; for example, @samp{@{1,2,3@}} is a three-element array of
15020 integers, @samp{@{@{1,2@}, @{3,4@}, @{5,6@}@}} is a three-by-two array,
15021 and @samp{@{&"hi", &"there", &"fred"@}} is a three-element array of pointers.
15024 @node C Plus Plus Expressions
15025 @subsubsection C@t{++} Expressions
15027 @cindex expressions in C@t{++}
15028 @value{GDBN} expression handling can interpret most C@t{++} expressions.
15030 @cindex debugging C@t{++} programs
15031 @cindex C@t{++} compilers
15032 @cindex debug formats and C@t{++}
15033 @cindex @value{NGCC} and C@t{++}
15035 @emph{Warning:} @value{GDBN} can only debug C@t{++} code if you use
15036 the proper compiler and the proper debug format. Currently,
15037 @value{GDBN} works best when debugging C@t{++} code that is compiled
15038 with the most recent version of @value{NGCC} possible. The DWARF
15039 debugging format is preferred; @value{NGCC} defaults to this on most
15040 popular platforms. Other compilers and/or debug formats are likely to
15041 work badly or not at all when using @value{GDBN} to debug C@t{++}
15042 code. @xref{Compilation}.
15047 @cindex member functions
15049 Member function calls are allowed; you can use expressions like
15052 count = aml->GetOriginal(x, y)
15055 @vindex this@r{, inside C@t{++} member functions}
15056 @cindex namespace in C@t{++}
15058 While a member function is active (in the selected stack frame), your
15059 expressions have the same namespace available as the member function;
15060 that is, @value{GDBN} allows implicit references to the class instance
15061 pointer @code{this} following the same rules as C@t{++}. @code{using}
15062 declarations in the current scope are also respected by @value{GDBN}.
15064 @cindex call overloaded functions
15065 @cindex overloaded functions, calling
15066 @cindex type conversions in C@t{++}
15068 You can call overloaded functions; @value{GDBN} resolves the function
15069 call to the right definition, with some restrictions. @value{GDBN} does not
15070 perform overload resolution involving user-defined type conversions,
15071 calls to constructors, or instantiations of templates that do not exist
15072 in the program. It also cannot handle ellipsis argument lists or
15075 It does perform integral conversions and promotions, floating-point
15076 promotions, arithmetic conversions, pointer conversions, conversions of
15077 class objects to base classes, and standard conversions such as those of
15078 functions or arrays to pointers; it requires an exact match on the
15079 number of function arguments.
15081 Overload resolution is always performed, unless you have specified
15082 @code{set overload-resolution off}. @xref{Debugging C Plus Plus,
15083 ,@value{GDBN} Features for C@t{++}}.
15085 You must specify @code{set overload-resolution off} in order to use an
15086 explicit function signature to call an overloaded function, as in
15088 p 'foo(char,int)'('x', 13)
15091 The @value{GDBN} command-completion facility can simplify this;
15092 see @ref{Completion, ,Command Completion}.
15094 @cindex reference declarations
15096 @value{GDBN} understands variables declared as C@t{++} lvalue or rvalue
15097 references; you can use them in expressions just as you do in C@t{++}
15098 source---they are automatically dereferenced.
15100 In the parameter list shown when @value{GDBN} displays a frame, the values of
15101 reference variables are not displayed (unlike other variables); this
15102 avoids clutter, since references are often used for large structures.
15103 The @emph{address} of a reference variable is always shown, unless
15104 you have specified @samp{set print address off}.
15107 @value{GDBN} supports the C@t{++} name resolution operator @code{::}---your
15108 expressions can use it just as expressions in your program do. Since
15109 one scope may be defined in another, you can use @code{::} repeatedly if
15110 necessary, for example in an expression like
15111 @samp{@var{scope1}::@var{scope2}::@var{name}}. @value{GDBN} also allows
15112 resolving name scope by reference to source files, in both C and C@t{++}
15113 debugging (@pxref{Variables, ,Program Variables}).
15116 @value{GDBN} performs argument-dependent lookup, following the C@t{++}
15121 @subsubsection C and C@t{++} Defaults
15123 @cindex C and C@t{++} defaults
15125 If you allow @value{GDBN} to set range checking automatically, it
15126 defaults to @code{off} whenever the working language changes to
15127 C or C@t{++}. This happens regardless of whether you or @value{GDBN}
15128 selects the working language.
15130 If you allow @value{GDBN} to set the language automatically, it
15131 recognizes source files whose names end with @file{.c}, @file{.C}, or
15132 @file{.cc}, etc, and when @value{GDBN} enters code compiled from one of
15133 these files, it sets the working language to C or C@t{++}.
15134 @xref{Automatically, ,Having @value{GDBN} Infer the Source Language},
15135 for further details.
15138 @subsubsection C and C@t{++} Type and Range Checks
15140 @cindex C and C@t{++} checks
15142 By default, when @value{GDBN} parses C or C@t{++} expressions, strict type
15143 checking is used. However, if you turn type checking off, @value{GDBN}
15144 will allow certain non-standard conversions, such as promoting integer
15145 constants to pointers.
15147 Range checking, if turned on, is done on mathematical operations. Array
15148 indices are not checked, since they are often used to index a pointer
15149 that is not itself an array.
15152 @subsubsection @value{GDBN} and C
15154 The @code{set print union} and @code{show print union} commands apply to
15155 the @code{union} type. When set to @samp{on}, any @code{union} that is
15156 inside a @code{struct} or @code{class} is also printed. Otherwise, it
15157 appears as @samp{@{...@}}.
15159 The @code{@@} operator aids in the debugging of dynamic arrays, formed
15160 with pointers and a memory allocation function. @xref{Expressions,
15163 @node Debugging C Plus Plus
15164 @subsubsection @value{GDBN} Features for C@t{++}
15166 @cindex commands for C@t{++}
15168 Some @value{GDBN} commands are particularly useful with C@t{++}, and some are
15169 designed specifically for use with C@t{++}. Here is a summary:
15172 @cindex break in overloaded functions
15173 @item @r{breakpoint menus}
15174 When you want a breakpoint in a function whose name is overloaded,
15175 @value{GDBN} has the capability to display a menu of possible breakpoint
15176 locations to help you specify which function definition you want.
15177 @xref{Ambiguous Expressions,,Ambiguous Expressions}.
15179 @cindex overloading in C@t{++}
15180 @item rbreak @var{regex}
15181 Setting breakpoints using regular expressions is helpful for setting
15182 breakpoints on overloaded functions that are not members of any special
15184 @xref{Set Breaks, ,Setting Breakpoints}.
15186 @cindex C@t{++} exception handling
15188 @itemx catch rethrow
15190 Debug C@t{++} exception handling using these commands. @xref{Set
15191 Catchpoints, , Setting Catchpoints}.
15193 @cindex inheritance
15194 @item ptype @var{typename}
15195 Print inheritance relationships as well as other information for type
15197 @xref{Symbols, ,Examining the Symbol Table}.
15199 @item info vtbl @var{expression}.
15200 The @code{info vtbl} command can be used to display the virtual
15201 method tables of the object computed by @var{expression}. This shows
15202 one entry per virtual table; there may be multiple virtual tables when
15203 multiple inheritance is in use.
15205 @cindex C@t{++} demangling
15206 @item demangle @var{name}
15207 Demangle @var{name}.
15208 @xref{Symbols}, for a more complete description of the @code{demangle} command.
15210 @cindex C@t{++} symbol display
15211 @item set print demangle
15212 @itemx show print demangle
15213 @itemx set print asm-demangle
15214 @itemx show print asm-demangle
15215 Control whether C@t{++} symbols display in their source form, both when
15216 displaying code as C@t{++} source and when displaying disassemblies.
15217 @xref{Print Settings, ,Print Settings}.
15219 @item set print object
15220 @itemx show print object
15221 Choose whether to print derived (actual) or declared types of objects.
15222 @xref{Print Settings, ,Print Settings}.
15224 @item set print vtbl
15225 @itemx show print vtbl
15226 Control the format for printing virtual function tables.
15227 @xref{Print Settings, ,Print Settings}.
15228 (The @code{vtbl} commands do not work on programs compiled with the HP
15229 ANSI C@t{++} compiler (@code{aCC}).)
15231 @kindex set overload-resolution
15232 @cindex overloaded functions, overload resolution
15233 @item set overload-resolution on
15234 Enable overload resolution for C@t{++} expression evaluation. The default
15235 is on. For overloaded functions, @value{GDBN} evaluates the arguments
15236 and searches for a function whose signature matches the argument types,
15237 using the standard C@t{++} conversion rules (see @ref{C Plus Plus
15238 Expressions, ,C@t{++} Expressions}, for details).
15239 If it cannot find a match, it emits a message.
15241 @item set overload-resolution off
15242 Disable overload resolution for C@t{++} expression evaluation. For
15243 overloaded functions that are not class member functions, @value{GDBN}
15244 chooses the first function of the specified name that it finds in the
15245 symbol table, whether or not its arguments are of the correct type. For
15246 overloaded functions that are class member functions, @value{GDBN}
15247 searches for a function whose signature @emph{exactly} matches the
15250 @kindex show overload-resolution
15251 @item show overload-resolution
15252 Show the current setting of overload resolution.
15254 @item @r{Overloaded symbol names}
15255 You can specify a particular definition of an overloaded symbol, using
15256 the same notation that is used to declare such symbols in C@t{++}: type
15257 @code{@var{symbol}(@var{types})} rather than just @var{symbol}. You can
15258 also use the @value{GDBN} command-line word completion facilities to list the
15259 available choices, or to finish the type list for you.
15260 @xref{Completion,, Command Completion}, for details on how to do this.
15262 @item @r{Breakpoints in functions with ABI tags}
15264 The GNU C@t{++} compiler introduced the notion of ABI ``tags'', which
15265 correspond to changes in the ABI of a type, function, or variable that
15266 would not otherwise be reflected in a mangled name. See
15267 @url{https://developers.redhat.com/blog/2015/02/05/gcc5-and-the-c11-abi/}
15270 The ABI tags are visible in C@t{++} demangled names. For example, a
15271 function that returns a std::string:
15274 std::string function(int);
15278 when compiled for the C++11 ABI is marked with the @code{cxx11} ABI
15279 tag, and @value{GDBN} displays the symbol like this:
15282 function[abi:cxx11](int)
15285 You can set a breakpoint on such functions simply as if they had no
15289 (gdb) b function(int)
15290 Breakpoint 2 at 0x40060d: file main.cc, line 10.
15291 (gdb) info breakpoints
15292 Num Type Disp Enb Address What
15293 1 breakpoint keep y 0x0040060d in function[abi:cxx11](int)
15297 On the rare occasion you need to disambiguate between different ABI
15298 tags, you can do so by simply including the ABI tag in the function
15302 (@value{GDBP}) b ambiguous[abi:other_tag](int)
15306 @node Decimal Floating Point
15307 @subsubsection Decimal Floating Point format
15308 @cindex decimal floating point format
15310 @value{GDBN} can examine, set and perform computations with numbers in
15311 decimal floating point format, which in the C language correspond to the
15312 @code{_Decimal32}, @code{_Decimal64} and @code{_Decimal128} types as
15313 specified by the extension to support decimal floating-point arithmetic.
15315 There are two encodings in use, depending on the architecture: BID (Binary
15316 Integer Decimal) for x86 and x86-64, and DPD (Densely Packed Decimal) for
15317 PowerPC and S/390. @value{GDBN} will use the appropriate encoding for the
15320 Because of a limitation in @file{libdecnumber}, the library used by @value{GDBN}
15321 to manipulate decimal floating point numbers, it is not possible to convert
15322 (using a cast, for example) integers wider than 32-bit to decimal float.
15324 In addition, in order to imitate @value{GDBN}'s behaviour with binary floating
15325 point computations, error checking in decimal float operations ignores
15326 underflow, overflow and divide by zero exceptions.
15328 In the PowerPC architecture, @value{GDBN} provides a set of pseudo-registers
15329 to inspect @code{_Decimal128} values stored in floating point registers.
15330 See @ref{PowerPC,,PowerPC} for more details.
15336 @value{GDBN} can be used to debug programs written in D and compiled with
15337 GDC, LDC or DMD compilers. Currently @value{GDBN} supports only one D
15338 specific feature --- dynamic arrays.
15343 @cindex Go (programming language)
15344 @value{GDBN} can be used to debug programs written in Go and compiled with
15345 @file{gccgo} or @file{6g} compilers.
15347 Here is a summary of the Go-specific features and restrictions:
15350 @cindex current Go package
15351 @item The current Go package
15352 The name of the current package does not need to be specified when
15353 specifying global variables and functions.
15355 For example, given the program:
15359 var myglob = "Shall we?"
15365 When stopped inside @code{main} either of these work:
15369 (gdb) p main.myglob
15372 @cindex builtin Go types
15373 @item Builtin Go types
15374 The @code{string} type is recognized by @value{GDBN} and is printed
15377 @cindex builtin Go functions
15378 @item Builtin Go functions
15379 The @value{GDBN} expression parser recognizes the @code{unsafe.Sizeof}
15380 function and handles it internally.
15382 @cindex restrictions on Go expressions
15383 @item Restrictions on Go expressions
15384 All Go operators are supported except @code{&^}.
15385 The Go @code{_} ``blank identifier'' is not supported.
15386 Automatic dereferencing of pointers is not supported.
15390 @subsection Objective-C
15392 @cindex Objective-C
15393 This section provides information about some commands and command
15394 options that are useful for debugging Objective-C code. See also
15395 @ref{Symbols, info classes}, and @ref{Symbols, info selectors}, for a
15396 few more commands specific to Objective-C support.
15399 * Method Names in Commands::
15400 * The Print Command with Objective-C::
15403 @node Method Names in Commands
15404 @subsubsection Method Names in Commands
15406 The following commands have been extended to accept Objective-C method
15407 names as line specifications:
15409 @kindex clear@r{, and Objective-C}
15410 @kindex break@r{, and Objective-C}
15411 @kindex info line@r{, and Objective-C}
15412 @kindex jump@r{, and Objective-C}
15413 @kindex list@r{, and Objective-C}
15417 @item @code{info line}
15422 A fully qualified Objective-C method name is specified as
15425 -[@var{Class} @var{methodName}]
15428 where the minus sign is used to indicate an instance method and a
15429 plus sign (not shown) is used to indicate a class method. The class
15430 name @var{Class} and method name @var{methodName} are enclosed in
15431 brackets, similar to the way messages are specified in Objective-C
15432 source code. For example, to set a breakpoint at the @code{create}
15433 instance method of class @code{Fruit} in the program currently being
15437 break -[Fruit create]
15440 To list ten program lines around the @code{initialize} class method,
15444 list +[NSText initialize]
15447 In the current version of @value{GDBN}, the plus or minus sign is
15448 required. In future versions of @value{GDBN}, the plus or minus
15449 sign will be optional, but you can use it to narrow the search. It
15450 is also possible to specify just a method name:
15456 You must specify the complete method name, including any colons. If
15457 your program's source files contain more than one @code{create} method,
15458 you'll be presented with a numbered list of classes that implement that
15459 method. Indicate your choice by number, or type @samp{0} to exit if
15462 As another example, to clear a breakpoint established at the
15463 @code{makeKeyAndOrderFront:} method of the @code{NSWindow} class, enter:
15466 clear -[NSWindow makeKeyAndOrderFront:]
15469 @node The Print Command with Objective-C
15470 @subsubsection The Print Command With Objective-C
15471 @cindex Objective-C, print objects
15472 @kindex print-object
15473 @kindex po @r{(@code{print-object})}
15475 The print command has also been extended to accept methods. For example:
15478 print -[@var{object} hash]
15481 @cindex print an Objective-C object description
15482 @cindex @code{_NSPrintForDebugger}, and printing Objective-C objects
15484 will tell @value{GDBN} to send the @code{hash} message to @var{object}
15485 and print the result. Also, an additional command has been added,
15486 @code{print-object} or @code{po} for short, which is meant to print
15487 the description of an object. However, this command may only work
15488 with certain Objective-C libraries that have a particular hook
15489 function, @code{_NSPrintForDebugger}, defined.
15492 @subsection OpenCL C
15495 This section provides information about @value{GDBN}s OpenCL C support.
15498 * OpenCL C Datatypes::
15499 * OpenCL C Expressions::
15500 * OpenCL C Operators::
15503 @node OpenCL C Datatypes
15504 @subsubsection OpenCL C Datatypes
15506 @cindex OpenCL C Datatypes
15507 @value{GDBN} supports the builtin scalar and vector datatypes specified
15508 by OpenCL 1.1. In addition the half- and double-precision floating point
15509 data types of the @code{cl_khr_fp16} and @code{cl_khr_fp64} OpenCL
15510 extensions are also known to @value{GDBN}.
15512 @node OpenCL C Expressions
15513 @subsubsection OpenCL C Expressions
15515 @cindex OpenCL C Expressions
15516 @value{GDBN} supports accesses to vector components including the access as
15517 lvalue where possible. Since OpenCL C is based on C99 most C expressions
15518 supported by @value{GDBN} can be used as well.
15520 @node OpenCL C Operators
15521 @subsubsection OpenCL C Operators
15523 @cindex OpenCL C Operators
15524 @value{GDBN} supports the operators specified by OpenCL 1.1 for scalar and
15528 @subsection Fortran
15529 @cindex Fortran-specific support in @value{GDBN}
15531 @value{GDBN} can be used to debug programs written in Fortran, but it
15532 currently supports only the features of Fortran 77 language.
15534 @cindex trailing underscore, in Fortran symbols
15535 Some Fortran compilers (@sc{gnu} Fortran 77 and Fortran 95 compilers
15536 among them) append an underscore to the names of variables and
15537 functions. When you debug programs compiled by those compilers, you
15538 will need to refer to variables and functions with a trailing
15542 * Fortran Operators:: Fortran operators and expressions
15543 * Fortran Defaults:: Default settings for Fortran
15544 * Special Fortran Commands:: Special @value{GDBN} commands for Fortran
15547 @node Fortran Operators
15548 @subsubsection Fortran Operators and Expressions
15550 @cindex Fortran operators and expressions
15552 Operators must be defined on values of specific types. For instance,
15553 @code{+} is defined on numbers, but not on characters or other non-
15554 arithmetic types. Operators are often defined on groups of types.
15558 The exponentiation operator. It raises the first operand to the power
15562 The range operator. Normally used in the form of array(low:high) to
15563 represent a section of array.
15566 The access component operator. Normally used to access elements in derived
15567 types. Also suitable for unions. As unions aren't part of regular Fortran,
15568 this can only happen when accessing a register that uses a gdbarch-defined
15572 @node Fortran Defaults
15573 @subsubsection Fortran Defaults
15575 @cindex Fortran Defaults
15577 Fortran symbols are usually case-insensitive, so @value{GDBN} by
15578 default uses case-insensitive matches for Fortran symbols. You can
15579 change that with the @samp{set case-insensitive} command, see
15580 @ref{Symbols}, for the details.
15582 @node Special Fortran Commands
15583 @subsubsection Special Fortran Commands
15585 @cindex Special Fortran commands
15587 @value{GDBN} has some commands to support Fortran-specific features,
15588 such as displaying common blocks.
15591 @cindex @code{COMMON} blocks, Fortran
15592 @kindex info common
15593 @item info common @r{[}@var{common-name}@r{]}
15594 This command prints the values contained in the Fortran @code{COMMON}
15595 block whose name is @var{common-name}. With no argument, the names of
15596 all @code{COMMON} blocks visible at the current program location are
15603 @cindex Pascal support in @value{GDBN}, limitations
15604 Debugging Pascal programs which use sets, subranges, file variables, or
15605 nested functions does not currently work. @value{GDBN} does not support
15606 entering expressions, printing values, or similar features using Pascal
15609 The Pascal-specific command @code{set print pascal_static-members}
15610 controls whether static members of Pascal objects are displayed.
15611 @xref{Print Settings, pascal_static-members}.
15616 @value{GDBN} supports the @url{https://www.rust-lang.org/, Rust
15617 Programming Language}. Type- and value-printing, and expression
15618 parsing, are reasonably complete. However, there are a few
15619 peculiarities and holes to be aware of.
15623 Linespecs (@pxref{Specify Location}) are never relative to the current
15624 crate. Instead, they act as if there were a global namespace of
15625 crates, somewhat similar to the way @code{extern crate} behaves.
15627 That is, if @value{GDBN} is stopped at a breakpoint in a function in
15628 crate @samp{A}, module @samp{B}, then @code{break B::f} will attempt
15629 to set a breakpoint in a function named @samp{f} in a crate named
15632 As a consequence of this approach, linespecs also cannot refer to
15633 items using @samp{self::} or @samp{super::}.
15636 Because @value{GDBN} implements Rust name-lookup semantics in
15637 expressions, it will sometimes prepend the current crate to a name.
15638 For example, if @value{GDBN} is stopped at a breakpoint in the crate
15639 @samp{K}, then @code{print ::x::y} will try to find the symbol
15642 However, since it is useful to be able to refer to other crates when
15643 debugging, @value{GDBN} provides the @code{extern} extension to
15644 circumvent this. To use the extension, just put @code{extern} before
15645 a path expression to refer to the otherwise unavailable ``global''
15648 In the above example, if you wanted to refer to the symbol @samp{y} in
15649 the crate @samp{x}, you would use @code{print extern x::y}.
15652 The Rust expression evaluator does not support ``statement-like''
15653 expressions such as @code{if} or @code{match}, or lambda expressions.
15656 Tuple expressions are not implemented.
15659 The Rust expression evaluator does not currently implement the
15660 @code{Drop} trait. Objects that may be created by the evaluator will
15661 never be destroyed.
15664 @value{GDBN} does not implement type inference for generics. In order
15665 to call generic functions or otherwise refer to generic items, you
15666 will have to specify the type parameters manually.
15669 @value{GDBN} currently uses the C@t{++} demangler for Rust. In most
15670 cases this does not cause any problems. However, in an expression
15671 context, completing a generic function name will give syntactically
15672 invalid results. This happens because Rust requires the @samp{::}
15673 operator between the function name and its generic arguments. For
15674 example, @value{GDBN} might provide a completion like
15675 @code{crate::f<u32>}, where the parser would require
15676 @code{crate::f::<u32>}.
15679 As of this writing, the Rust compiler (version 1.8) has a few holes in
15680 the debugging information it generates. These holes prevent certain
15681 features from being implemented by @value{GDBN}:
15685 Method calls cannot be made via traits.
15688 Operator overloading is not implemented.
15691 When debugging in a monomorphized function, you cannot use the generic
15695 The type @code{Self} is not available.
15698 @code{use} statements are not available, so some names may not be
15699 available in the crate.
15704 @subsection Modula-2
15706 @cindex Modula-2, @value{GDBN} support
15708 The extensions made to @value{GDBN} to support Modula-2 only support
15709 output from the @sc{gnu} Modula-2 compiler (which is currently being
15710 developed). Other Modula-2 compilers are not currently supported, and
15711 attempting to debug executables produced by them is most likely
15712 to give an error as @value{GDBN} reads in the executable's symbol
15715 @cindex expressions in Modula-2
15717 * M2 Operators:: Built-in operators
15718 * Built-In Func/Proc:: Built-in functions and procedures
15719 * M2 Constants:: Modula-2 constants
15720 * M2 Types:: Modula-2 types
15721 * M2 Defaults:: Default settings for Modula-2
15722 * Deviations:: Deviations from standard Modula-2
15723 * M2 Checks:: Modula-2 type and range checks
15724 * M2 Scope:: The scope operators @code{::} and @code{.}
15725 * GDB/M2:: @value{GDBN} and Modula-2
15729 @subsubsection Operators
15730 @cindex Modula-2 operators
15732 Operators must be defined on values of specific types. For instance,
15733 @code{+} is defined on numbers, but not on structures. Operators are
15734 often defined on groups of types. For the purposes of Modula-2, the
15735 following definitions hold:
15740 @emph{Integral types} consist of @code{INTEGER}, @code{CARDINAL}, and
15744 @emph{Character types} consist of @code{CHAR} and its subranges.
15747 @emph{Floating-point types} consist of @code{REAL}.
15750 @emph{Pointer types} consist of anything declared as @code{POINTER TO
15754 @emph{Scalar types} consist of all of the above.
15757 @emph{Set types} consist of @code{SET} and @code{BITSET} types.
15760 @emph{Boolean types} consist of @code{BOOLEAN}.
15764 The following operators are supported, and appear in order of
15765 increasing precedence:
15769 Function argument or array index separator.
15772 Assignment. The value of @var{var} @code{:=} @var{value} is
15776 Less than, greater than on integral, floating-point, or enumerated
15780 Less than or equal to, greater than or equal to
15781 on integral, floating-point and enumerated types, or set inclusion on
15782 set types. Same precedence as @code{<}.
15784 @item =@r{, }<>@r{, }#
15785 Equality and two ways of expressing inequality, valid on scalar types.
15786 Same precedence as @code{<}. In @value{GDBN} scripts, only @code{<>} is
15787 available for inequality, since @code{#} conflicts with the script
15791 Set membership. Defined on set types and the types of their members.
15792 Same precedence as @code{<}.
15795 Boolean disjunction. Defined on boolean types.
15798 Boolean conjunction. Defined on boolean types.
15801 The @value{GDBN} ``artificial array'' operator (@pxref{Expressions, ,Expressions}).
15804 Addition and subtraction on integral and floating-point types, or union
15805 and difference on set types.
15808 Multiplication on integral and floating-point types, or set intersection
15812 Division on floating-point types, or symmetric set difference on set
15813 types. Same precedence as @code{*}.
15816 Integer division and remainder. Defined on integral types. Same
15817 precedence as @code{*}.
15820 Negative. Defined on @code{INTEGER} and @code{REAL} data.
15823 Pointer dereferencing. Defined on pointer types.
15826 Boolean negation. Defined on boolean types. Same precedence as
15830 @code{RECORD} field selector. Defined on @code{RECORD} data. Same
15831 precedence as @code{^}.
15834 Array indexing. Defined on @code{ARRAY} data. Same precedence as @code{^}.
15837 Procedure argument list. Defined on @code{PROCEDURE} objects. Same precedence
15841 @value{GDBN} and Modula-2 scope operators.
15845 @emph{Warning:} Set expressions and their operations are not yet supported, so @value{GDBN}
15846 treats the use of the operator @code{IN}, or the use of operators
15847 @code{+}, @code{-}, @code{*}, @code{/}, @code{=}, , @code{<>}, @code{#},
15848 @code{<=}, and @code{>=} on sets as an error.
15852 @node Built-In Func/Proc
15853 @subsubsection Built-in Functions and Procedures
15854 @cindex Modula-2 built-ins
15856 Modula-2 also makes available several built-in procedures and functions.
15857 In describing these, the following metavariables are used:
15862 represents an @code{ARRAY} variable.
15865 represents a @code{CHAR} constant or variable.
15868 represents a variable or constant of integral type.
15871 represents an identifier that belongs to a set. Generally used in the
15872 same function with the metavariable @var{s}. The type of @var{s} should
15873 be @code{SET OF @var{mtype}} (where @var{mtype} is the type of @var{m}).
15876 represents a variable or constant of integral or floating-point type.
15879 represents a variable or constant of floating-point type.
15885 represents a variable.
15888 represents a variable or constant of one of many types. See the
15889 explanation of the function for details.
15892 All Modula-2 built-in procedures also return a result, described below.
15896 Returns the absolute value of @var{n}.
15899 If @var{c} is a lower case letter, it returns its upper case
15900 equivalent, otherwise it returns its argument.
15903 Returns the character whose ordinal value is @var{i}.
15906 Decrements the value in the variable @var{v} by one. Returns the new value.
15908 @item DEC(@var{v},@var{i})
15909 Decrements the value in the variable @var{v} by @var{i}. Returns the
15912 @item EXCL(@var{m},@var{s})
15913 Removes the element @var{m} from the set @var{s}. Returns the new
15916 @item FLOAT(@var{i})
15917 Returns the floating point equivalent of the integer @var{i}.
15919 @item HIGH(@var{a})
15920 Returns the index of the last member of @var{a}.
15923 Increments the value in the variable @var{v} by one. Returns the new value.
15925 @item INC(@var{v},@var{i})
15926 Increments the value in the variable @var{v} by @var{i}. Returns the
15929 @item INCL(@var{m},@var{s})
15930 Adds the element @var{m} to the set @var{s} if it is not already
15931 there. Returns the new set.
15934 Returns the maximum value of the type @var{t}.
15937 Returns the minimum value of the type @var{t}.
15940 Returns boolean TRUE if @var{i} is an odd number.
15943 Returns the ordinal value of its argument. For example, the ordinal
15944 value of a character is its @sc{ascii} value (on machines supporting
15945 the @sc{ascii} character set). The argument @var{x} must be of an
15946 ordered type, which include integral, character and enumerated types.
15948 @item SIZE(@var{x})
15949 Returns the size of its argument. The argument @var{x} can be a
15950 variable or a type.
15952 @item TRUNC(@var{r})
15953 Returns the integral part of @var{r}.
15955 @item TSIZE(@var{x})
15956 Returns the size of its argument. The argument @var{x} can be a
15957 variable or a type.
15959 @item VAL(@var{t},@var{i})
15960 Returns the member of the type @var{t} whose ordinal value is @var{i}.
15964 @emph{Warning:} Sets and their operations are not yet supported, so
15965 @value{GDBN} treats the use of procedures @code{INCL} and @code{EXCL} as
15969 @cindex Modula-2 constants
15971 @subsubsection Constants
15973 @value{GDBN} allows you to express the constants of Modula-2 in the following
15979 Integer constants are simply a sequence of digits. When used in an
15980 expression, a constant is interpreted to be type-compatible with the
15981 rest of the expression. Hexadecimal integers are specified by a
15982 trailing @samp{H}, and octal integers by a trailing @samp{B}.
15985 Floating point constants appear as a sequence of digits, followed by a
15986 decimal point and another sequence of digits. An optional exponent can
15987 then be specified, in the form @samp{E@r{[}+@r{|}-@r{]}@var{nnn}}, where
15988 @samp{@r{[}+@r{|}-@r{]}@var{nnn}} is the desired exponent. All of the
15989 digits of the floating point constant must be valid decimal (base 10)
15993 Character constants consist of a single character enclosed by a pair of
15994 like quotes, either single (@code{'}) or double (@code{"}). They may
15995 also be expressed by their ordinal value (their @sc{ascii} value, usually)
15996 followed by a @samp{C}.
15999 String constants consist of a sequence of characters enclosed by a
16000 pair of like quotes, either single (@code{'}) or double (@code{"}).
16001 Escape sequences in the style of C are also allowed. @xref{C
16002 Constants, ,C and C@t{++} Constants}, for a brief explanation of escape
16006 Enumerated constants consist of an enumerated identifier.
16009 Boolean constants consist of the identifiers @code{TRUE} and
16013 Pointer constants consist of integral values only.
16016 Set constants are not yet supported.
16020 @subsubsection Modula-2 Types
16021 @cindex Modula-2 types
16023 Currently @value{GDBN} can print the following data types in Modula-2
16024 syntax: array types, record types, set types, pointer types, procedure
16025 types, enumerated types, subrange types and base types. You can also
16026 print the contents of variables declared using these type.
16027 This section gives a number of simple source code examples together with
16028 sample @value{GDBN} sessions.
16030 The first example contains the following section of code:
16039 and you can request @value{GDBN} to interrogate the type and value of
16040 @code{r} and @code{s}.
16043 (@value{GDBP}) print s
16045 (@value{GDBP}) ptype s
16047 (@value{GDBP}) print r
16049 (@value{GDBP}) ptype r
16054 Likewise if your source code declares @code{s} as:
16058 s: SET ['A'..'Z'] ;
16062 then you may query the type of @code{s} by:
16065 (@value{GDBP}) ptype s
16066 type = SET ['A'..'Z']
16070 Note that at present you cannot interactively manipulate set
16071 expressions using the debugger.
16073 The following example shows how you might declare an array in Modula-2
16074 and how you can interact with @value{GDBN} to print its type and contents:
16078 s: ARRAY [-10..10] OF CHAR ;
16082 (@value{GDBP}) ptype s
16083 ARRAY [-10..10] OF CHAR
16086 Note that the array handling is not yet complete and although the type
16087 is printed correctly, expression handling still assumes that all
16088 arrays have a lower bound of zero and not @code{-10} as in the example
16091 Here are some more type related Modula-2 examples:
16095 colour = (blue, red, yellow, green) ;
16096 t = [blue..yellow] ;
16104 The @value{GDBN} interaction shows how you can query the data type
16105 and value of a variable.
16108 (@value{GDBP}) print s
16110 (@value{GDBP}) ptype t
16111 type = [blue..yellow]
16115 In this example a Modula-2 array is declared and its contents
16116 displayed. Observe that the contents are written in the same way as
16117 their @code{C} counterparts.
16121 s: ARRAY [1..5] OF CARDINAL ;
16127 (@value{GDBP}) print s
16128 $1 = @{1, 0, 0, 0, 0@}
16129 (@value{GDBP}) ptype s
16130 type = ARRAY [1..5] OF CARDINAL
16133 The Modula-2 language interface to @value{GDBN} also understands
16134 pointer types as shown in this example:
16138 s: POINTER TO ARRAY [1..5] OF CARDINAL ;
16145 and you can request that @value{GDBN} describes the type of @code{s}.
16148 (@value{GDBP}) ptype s
16149 type = POINTER TO ARRAY [1..5] OF CARDINAL
16152 @value{GDBN} handles compound types as we can see in this example.
16153 Here we combine array types, record types, pointer types and subrange
16164 myarray = ARRAY myrange OF CARDINAL ;
16165 myrange = [-2..2] ;
16167 s: POINTER TO ARRAY myrange OF foo ;
16171 and you can ask @value{GDBN} to describe the type of @code{s} as shown
16175 (@value{GDBP}) ptype s
16176 type = POINTER TO ARRAY [-2..2] OF foo = RECORD
16179 f3 : ARRAY [-2..2] OF CARDINAL;
16184 @subsubsection Modula-2 Defaults
16185 @cindex Modula-2 defaults
16187 If type and range checking are set automatically by @value{GDBN}, they
16188 both default to @code{on} whenever the working language changes to
16189 Modula-2. This happens regardless of whether you or @value{GDBN}
16190 selected the working language.
16192 If you allow @value{GDBN} to set the language automatically, then entering
16193 code compiled from a file whose name ends with @file{.mod} sets the
16194 working language to Modula-2. @xref{Automatically, ,Having @value{GDBN}
16195 Infer the Source Language}, for further details.
16198 @subsubsection Deviations from Standard Modula-2
16199 @cindex Modula-2, deviations from
16201 A few changes have been made to make Modula-2 programs easier to debug.
16202 This is done primarily via loosening its type strictness:
16206 Unlike in standard Modula-2, pointer constants can be formed by
16207 integers. This allows you to modify pointer variables during
16208 debugging. (In standard Modula-2, the actual address contained in a
16209 pointer variable is hidden from you; it can only be modified
16210 through direct assignment to another pointer variable or expression that
16211 returned a pointer.)
16214 C escape sequences can be used in strings and characters to represent
16215 non-printable characters. @value{GDBN} prints out strings with these
16216 escape sequences embedded. Single non-printable characters are
16217 printed using the @samp{CHR(@var{nnn})} format.
16220 The assignment operator (@code{:=}) returns the value of its right-hand
16224 All built-in procedures both modify @emph{and} return their argument.
16228 @subsubsection Modula-2 Type and Range Checks
16229 @cindex Modula-2 checks
16232 @emph{Warning:} in this release, @value{GDBN} does not yet perform type or
16235 @c FIXME remove warning when type/range checks added
16237 @value{GDBN} considers two Modula-2 variables type equivalent if:
16241 They are of types that have been declared equivalent via a @code{TYPE
16242 @var{t1} = @var{t2}} statement
16245 They have been declared on the same line. (Note: This is true of the
16246 @sc{gnu} Modula-2 compiler, but it may not be true of other compilers.)
16249 As long as type checking is enabled, any attempt to combine variables
16250 whose types are not equivalent is an error.
16252 Range checking is done on all mathematical operations, assignment, array
16253 index bounds, and all built-in functions and procedures.
16256 @subsubsection The Scope Operators @code{::} and @code{.}
16258 @cindex @code{.}, Modula-2 scope operator
16259 @cindex colon, doubled as scope operator
16261 @vindex colon-colon@r{, in Modula-2}
16262 @c Info cannot handle :: but TeX can.
16265 @vindex ::@r{, in Modula-2}
16268 There are a few subtle differences between the Modula-2 scope operator
16269 (@code{.}) and the @value{GDBN} scope operator (@code{::}). The two have
16274 @var{module} . @var{id}
16275 @var{scope} :: @var{id}
16279 where @var{scope} is the name of a module or a procedure,
16280 @var{module} the name of a module, and @var{id} is any declared
16281 identifier within your program, except another module.
16283 Using the @code{::} operator makes @value{GDBN} search the scope
16284 specified by @var{scope} for the identifier @var{id}. If it is not
16285 found in the specified scope, then @value{GDBN} searches all scopes
16286 enclosing the one specified by @var{scope}.
16288 Using the @code{.} operator makes @value{GDBN} search the current scope for
16289 the identifier specified by @var{id} that was imported from the
16290 definition module specified by @var{module}. With this operator, it is
16291 an error if the identifier @var{id} was not imported from definition
16292 module @var{module}, or if @var{id} is not an identifier in
16296 @subsubsection @value{GDBN} and Modula-2
16298 Some @value{GDBN} commands have little use when debugging Modula-2 programs.
16299 Five subcommands of @code{set print} and @code{show print} apply
16300 specifically to C and C@t{++}: @samp{vtbl}, @samp{demangle},
16301 @samp{asm-demangle}, @samp{object}, and @samp{union}. The first four
16302 apply to C@t{++}, and the last to the C @code{union} type, which has no direct
16303 analogue in Modula-2.
16305 The @code{@@} operator (@pxref{Expressions, ,Expressions}), while available
16306 with any language, is not useful with Modula-2. Its
16307 intent is to aid the debugging of @dfn{dynamic arrays}, which cannot be
16308 created in Modula-2 as they can in C or C@t{++}. However, because an
16309 address can be specified by an integral constant, the construct
16310 @samp{@{@var{type}@}@var{adrexp}} is still useful.
16312 @cindex @code{#} in Modula-2
16313 In @value{GDBN} scripts, the Modula-2 inequality operator @code{#} is
16314 interpreted as the beginning of a comment. Use @code{<>} instead.
16320 The extensions made to @value{GDBN} for Ada only support
16321 output from the @sc{gnu} Ada (GNAT) compiler.
16322 Other Ada compilers are not currently supported, and
16323 attempting to debug executables produced by them is most likely
16327 @cindex expressions in Ada
16329 * Ada Mode Intro:: General remarks on the Ada syntax
16330 and semantics supported by Ada mode
16332 * Omissions from Ada:: Restrictions on the Ada expression syntax.
16333 * Additions to Ada:: Extensions of the Ada expression syntax.
16334 * Overloading support for Ada:: Support for expressions involving overloaded
16336 * Stopping Before Main Program:: Debugging the program during elaboration.
16337 * Ada Exceptions:: Ada Exceptions
16338 * Ada Tasks:: Listing and setting breakpoints in tasks.
16339 * Ada Tasks and Core Files:: Tasking Support when Debugging Core Files
16340 * Ravenscar Profile:: Tasking Support when using the Ravenscar
16342 * Ada Settings:: New settable GDB parameters for Ada.
16343 * Ada Glitches:: Known peculiarities of Ada mode.
16346 @node Ada Mode Intro
16347 @subsubsection Introduction
16348 @cindex Ada mode, general
16350 The Ada mode of @value{GDBN} supports a fairly large subset of Ada expression
16351 syntax, with some extensions.
16352 The philosophy behind the design of this subset is
16356 That @value{GDBN} should provide basic literals and access to operations for
16357 arithmetic, dereferencing, field selection, indexing, and subprogram calls,
16358 leaving more sophisticated computations to subprograms written into the
16359 program (which therefore may be called from @value{GDBN}).
16362 That type safety and strict adherence to Ada language restrictions
16363 are not particularly important to the @value{GDBN} user.
16366 That brevity is important to the @value{GDBN} user.
16369 Thus, for brevity, the debugger acts as if all names declared in
16370 user-written packages are directly visible, even if they are not visible
16371 according to Ada rules, thus making it unnecessary to fully qualify most
16372 names with their packages, regardless of context. Where this causes
16373 ambiguity, @value{GDBN} asks the user's intent.
16375 The debugger will start in Ada mode if it detects an Ada main program.
16376 As for other languages, it will enter Ada mode when stopped in a program that
16377 was translated from an Ada source file.
16379 While in Ada mode, you may use `@t{--}' for comments. This is useful
16380 mostly for documenting command files. The standard @value{GDBN} comment
16381 (@samp{#}) still works at the beginning of a line in Ada mode, but not in the
16382 middle (to allow based literals).
16384 @node Omissions from Ada
16385 @subsubsection Omissions from Ada
16386 @cindex Ada, omissions from
16388 Here are the notable omissions from the subset:
16392 Only a subset of the attributes are supported:
16396 @t{'First}, @t{'Last}, and @t{'Length}
16397 on array objects (not on types and subtypes).
16400 @t{'Min} and @t{'Max}.
16403 @t{'Pos} and @t{'Val}.
16409 @t{'Range} on array objects (not subtypes), but only as the right
16410 operand of the membership (@code{in}) operator.
16413 @t{'Access}, @t{'Unchecked_Access}, and
16414 @t{'Unrestricted_Access} (a GNAT extension).
16422 @code{Characters.Latin_1} are not available and
16423 concatenation is not implemented. Thus, escape characters in strings are
16424 not currently available.
16427 Equality tests (@samp{=} and @samp{/=}) on arrays test for bitwise
16428 equality of representations. They will generally work correctly
16429 for strings and arrays whose elements have integer or enumeration types.
16430 They may not work correctly for arrays whose element
16431 types have user-defined equality, for arrays of real values
16432 (in particular, IEEE-conformant floating point, because of negative
16433 zeroes and NaNs), and for arrays whose elements contain unused bits with
16434 indeterminate values.
16437 The other component-by-component array operations (@code{and}, @code{or},
16438 @code{xor}, @code{not}, and relational tests other than equality)
16439 are not implemented.
16442 @cindex array aggregates (Ada)
16443 @cindex record aggregates (Ada)
16444 @cindex aggregates (Ada)
16445 There is limited support for array and record aggregates. They are
16446 permitted only on the right sides of assignments, as in these examples:
16449 (@value{GDBP}) set An_Array := (1, 2, 3, 4, 5, 6)
16450 (@value{GDBP}) set An_Array := (1, others => 0)
16451 (@value{GDBP}) set An_Array := (0|4 => 1, 1..3 => 2, 5 => 6)
16452 (@value{GDBP}) set A_2D_Array := ((1, 2, 3), (4, 5, 6), (7, 8, 9))
16453 (@value{GDBP}) set A_Record := (1, "Peter", True);
16454 (@value{GDBP}) set A_Record := (Name => "Peter", Id => 1, Alive => True)
16458 discriminant's value by assigning an aggregate has an
16459 undefined effect if that discriminant is used within the record.
16460 However, you can first modify discriminants by directly assigning to
16461 them (which normally would not be allowed in Ada), and then performing an
16462 aggregate assignment. For example, given a variable @code{A_Rec}
16463 declared to have a type such as:
16466 type Rec (Len : Small_Integer := 0) is record
16468 Vals : IntArray (1 .. Len);
16472 you can assign a value with a different size of @code{Vals} with two
16476 (@value{GDBP}) set A_Rec.Len := 4
16477 (@value{GDBP}) set A_Rec := (Id => 42, Vals => (1, 2, 3, 4))
16480 As this example also illustrates, @value{GDBN} is very loose about the usual
16481 rules concerning aggregates. You may leave out some of the
16482 components of an array or record aggregate (such as the @code{Len}
16483 component in the assignment to @code{A_Rec} above); they will retain their
16484 original values upon assignment. You may freely use dynamic values as
16485 indices in component associations. You may even use overlapping or
16486 redundant component associations, although which component values are
16487 assigned in such cases is not defined.
16490 Calls to dispatching subprograms are not implemented.
16493 The overloading algorithm is much more limited (i.e., less selective)
16494 than that of real Ada. It makes only limited use of the context in
16495 which a subexpression appears to resolve its meaning, and it is much
16496 looser in its rules for allowing type matches. As a result, some
16497 function calls will be ambiguous, and the user will be asked to choose
16498 the proper resolution.
16501 The @code{new} operator is not implemented.
16504 Entry calls are not implemented.
16507 Aside from printing, arithmetic operations on the native VAX floating-point
16508 formats are not supported.
16511 It is not possible to slice a packed array.
16514 The names @code{True} and @code{False}, when not part of a qualified name,
16515 are interpreted as if implicitly prefixed by @code{Standard}, regardless of
16517 Should your program
16518 redefine these names in a package or procedure (at best a dubious practice),
16519 you will have to use fully qualified names to access their new definitions.
16522 @node Additions to Ada
16523 @subsubsection Additions to Ada
16524 @cindex Ada, deviations from
16526 As it does for other languages, @value{GDBN} makes certain generic
16527 extensions to Ada (@pxref{Expressions}):
16531 If the expression @var{E} is a variable residing in memory (typically
16532 a local variable or array element) and @var{N} is a positive integer,
16533 then @code{@var{E}@@@var{N}} displays the values of @var{E} and the
16534 @var{N}-1 adjacent variables following it in memory as an array. In
16535 Ada, this operator is generally not necessary, since its prime use is
16536 in displaying parts of an array, and slicing will usually do this in
16537 Ada. However, there are occasional uses when debugging programs in
16538 which certain debugging information has been optimized away.
16541 @code{@var{B}::@var{var}} means ``the variable named @var{var} that
16542 appears in function or file @var{B}.'' When @var{B} is a file name,
16543 you must typically surround it in single quotes.
16546 The expression @code{@{@var{type}@} @var{addr}} means ``the variable of type
16547 @var{type} that appears at address @var{addr}.''
16550 A name starting with @samp{$} is a convenience variable
16551 (@pxref{Convenience Vars}) or a machine register (@pxref{Registers}).
16554 In addition, @value{GDBN} provides a few other shortcuts and outright
16555 additions specific to Ada:
16559 The assignment statement is allowed as an expression, returning
16560 its right-hand operand as its value. Thus, you may enter
16563 (@value{GDBP}) set x := y + 3
16564 (@value{GDBP}) print A(tmp := y + 1)
16568 The semicolon is allowed as an ``operator,'' returning as its value
16569 the value of its right-hand operand.
16570 This allows, for example,
16571 complex conditional breaks:
16574 (@value{GDBP}) break f
16575 (@value{GDBP}) condition 1 (report(i); k += 1; A(k) > 100)
16579 Rather than use catenation and symbolic character names to introduce special
16580 characters into strings, one may instead use a special bracket notation,
16581 which is also used to print strings. A sequence of characters of the form
16582 @samp{["@var{XX}"]} within a string or character literal denotes the
16583 (single) character whose numeric encoding is @var{XX} in hexadecimal. The
16584 sequence of characters @samp{["""]} also denotes a single quotation mark
16585 in strings. For example,
16587 "One line.["0a"]Next line.["0a"]"
16590 contains an ASCII newline character (@code{Ada.Characters.Latin_1.LF})
16594 The subtype used as a prefix for the attributes @t{'Pos}, @t{'Min}, and
16595 @t{'Max} is optional (and is ignored in any case). For example, it is valid
16599 (@value{GDBP}) print 'max(x, y)
16603 When printing arrays, @value{GDBN} uses positional notation when the
16604 array has a lower bound of 1, and uses a modified named notation otherwise.
16605 For example, a one-dimensional array of three integers with a lower bound
16606 of 3 might print as
16613 That is, in contrast to valid Ada, only the first component has a @code{=>}
16617 You may abbreviate attributes in expressions with any unique,
16618 multi-character subsequence of
16619 their names (an exact match gets preference).
16620 For example, you may use @t{a'len}, @t{a'gth}, or @t{a'lh}
16621 in place of @t{a'length}.
16624 @cindex quoting Ada internal identifiers
16625 Since Ada is case-insensitive, the debugger normally maps identifiers you type
16626 to lower case. The GNAT compiler uses upper-case characters for
16627 some of its internal identifiers, which are normally of no interest to users.
16628 For the rare occasions when you actually have to look at them,
16629 enclose them in angle brackets to avoid the lower-case mapping.
16632 (@value{GDBP}) print <JMPBUF_SAVE>[0]
16636 Printing an object of class-wide type or dereferencing an
16637 access-to-class-wide value will display all the components of the object's
16638 specific type (as indicated by its run-time tag). Likewise, component
16639 selection on such a value will operate on the specific type of the
16644 @node Overloading support for Ada
16645 @subsubsection Overloading support for Ada
16646 @cindex overloading, Ada
16648 The debugger supports limited overloading. Given a subprogram call in which
16649 the function symbol has multiple definitions, it will use the number of
16650 actual parameters and some information about their types to attempt to narrow
16651 the set of definitions. It also makes very limited use of context, preferring
16652 procedures to functions in the context of the @code{call} command, and
16653 functions to procedures elsewhere.
16655 If, after narrowing, the set of matching definitions still contains more than
16656 one definition, @value{GDBN} will display a menu to query which one it should
16660 (@value{GDBP}) print f(1)
16661 Multiple matches for f
16663 [1] foo.f (integer) return boolean at foo.adb:23
16664 [2] foo.f (foo.new_integer) return boolean at foo.adb:28
16668 In this case, just select one menu entry either to cancel expression evaluation
16669 (type @kbd{0} and press @key{RET}) or to continue evaluation with a specific
16670 instance (type the corresponding number and press @key{RET}).
16672 Here are a couple of commands to customize @value{GDBN}'s behavior in this
16677 @kindex set ada print-signatures
16678 @item set ada print-signatures
16679 Control whether parameter types and return types are displayed in overloads
16680 selection menus. It is @code{on} by default.
16681 @xref{Overloading support for Ada}.
16683 @kindex show ada print-signatures
16684 @item show ada print-signatures
16685 Show the current setting for displaying parameter types and return types in
16686 overloads selection menu.
16687 @xref{Overloading support for Ada}.
16691 @node Stopping Before Main Program
16692 @subsubsection Stopping at the Very Beginning
16694 @cindex breakpointing Ada elaboration code
16695 It is sometimes necessary to debug the program during elaboration, and
16696 before reaching the main procedure.
16697 As defined in the Ada Reference
16698 Manual, the elaboration code is invoked from a procedure called
16699 @code{adainit}. To run your program up to the beginning of
16700 elaboration, simply use the following two commands:
16701 @code{tbreak adainit} and @code{run}.
16703 @node Ada Exceptions
16704 @subsubsection Ada Exceptions
16706 A command is provided to list all Ada exceptions:
16709 @kindex info exceptions
16710 @item info exceptions
16711 @itemx info exceptions @var{regexp}
16712 The @code{info exceptions} command allows you to list all Ada exceptions
16713 defined within the program being debugged, as well as their addresses.
16714 With a regular expression, @var{regexp}, as argument, only those exceptions
16715 whose names match @var{regexp} are listed.
16718 Below is a small example, showing how the command can be used, first
16719 without argument, and next with a regular expression passed as an
16723 (@value{GDBP}) info exceptions
16724 All defined Ada exceptions:
16725 constraint_error: 0x613da0
16726 program_error: 0x613d20
16727 storage_error: 0x613ce0
16728 tasking_error: 0x613ca0
16729 const.aint_global_e: 0x613b00
16730 (@value{GDBP}) info exceptions const.aint
16731 All Ada exceptions matching regular expression "const.aint":
16732 constraint_error: 0x613da0
16733 const.aint_global_e: 0x613b00
16736 It is also possible to ask @value{GDBN} to stop your program's execution
16737 when an exception is raised. For more details, see @ref{Set Catchpoints}.
16740 @subsubsection Extensions for Ada Tasks
16741 @cindex Ada, tasking
16743 Support for Ada tasks is analogous to that for threads (@pxref{Threads}).
16744 @value{GDBN} provides the following task-related commands:
16749 This command shows a list of current Ada tasks, as in the following example:
16756 (@value{GDBP}) info tasks
16757 ID TID P-ID Pri State Name
16758 1 8088000 0 15 Child Activation Wait main_task
16759 2 80a4000 1 15 Accept Statement b
16760 3 809a800 1 15 Child Activation Wait a
16761 * 4 80ae800 3 15 Runnable c
16766 In this listing, the asterisk before the last task indicates it to be the
16767 task currently being inspected.
16771 Represents @value{GDBN}'s internal task number.
16777 The parent's task ID (@value{GDBN}'s internal task number).
16780 The base priority of the task.
16783 Current state of the task.
16787 The task has been created but has not been activated. It cannot be
16791 The task is not blocked for any reason known to Ada. (It may be waiting
16792 for a mutex, though.) It is conceptually "executing" in normal mode.
16795 The task is terminated, in the sense of ARM 9.3 (5). Any dependents
16796 that were waiting on terminate alternatives have been awakened and have
16797 terminated themselves.
16799 @item Child Activation Wait
16800 The task is waiting for created tasks to complete activation.
16802 @item Accept Statement
16803 The task is waiting on an accept or selective wait statement.
16805 @item Waiting on entry call
16806 The task is waiting on an entry call.
16808 @item Async Select Wait
16809 The task is waiting to start the abortable part of an asynchronous
16813 The task is waiting on a select statement with only a delay
16816 @item Child Termination Wait
16817 The task is sleeping having completed a master within itself, and is
16818 waiting for the tasks dependent on that master to become terminated or
16819 waiting on a terminate Phase.
16821 @item Wait Child in Term Alt
16822 The task is sleeping waiting for tasks on terminate alternatives to
16823 finish terminating.
16825 @item Accepting RV with @var{taskno}
16826 The task is accepting a rendez-vous with the task @var{taskno}.
16830 Name of the task in the program.
16834 @kindex info task @var{taskno}
16835 @item info task @var{taskno}
16836 This command shows detailled informations on the specified task, as in
16837 the following example:
16842 (@value{GDBP}) info tasks
16843 ID TID P-ID Pri State Name
16844 1 8077880 0 15 Child Activation Wait main_task
16845 * 2 807c468 1 15 Runnable task_1
16846 (@value{GDBP}) info task 2
16847 Ada Task: 0x807c468
16850 Parent: 1 (main_task)
16856 @kindex task@r{ (Ada)}
16857 @cindex current Ada task ID
16858 This command prints the ID of the current task.
16864 (@value{GDBP}) info tasks
16865 ID TID P-ID Pri State Name
16866 1 8077870 0 15 Child Activation Wait main_task
16867 * 2 807c458 1 15 Runnable t
16868 (@value{GDBP}) task
16869 [Current task is 2]
16872 @item task @var{taskno}
16873 @cindex Ada task switching
16874 This command is like the @code{thread @var{thread-id}}
16875 command (@pxref{Threads}). It switches the context of debugging
16876 from the current task to the given task.
16882 (@value{GDBP}) info tasks
16883 ID TID P-ID Pri State Name
16884 1 8077870 0 15 Child Activation Wait main_task
16885 * 2 807c458 1 15 Runnable t
16886 (@value{GDBP}) task 1
16887 [Switching to task 1]
16888 #0 0x8067726 in pthread_cond_wait ()
16890 #0 0x8067726 in pthread_cond_wait ()
16891 #1 0x8056714 in system.os_interface.pthread_cond_wait ()
16892 #2 0x805cb63 in system.task_primitives.operations.sleep ()
16893 #3 0x806153e in system.tasking.stages.activate_tasks ()
16894 #4 0x804aacc in un () at un.adb:5
16897 @item break @var{location} task @var{taskno}
16898 @itemx break @var{location} task @var{taskno} if @dots{}
16899 @cindex breakpoints and tasks, in Ada
16900 @cindex task breakpoints, in Ada
16901 @kindex break @dots{} task @var{taskno}@r{ (Ada)}
16902 These commands are like the @code{break @dots{} thread @dots{}}
16903 command (@pxref{Thread Stops}). The
16904 @var{location} argument specifies source lines, as described
16905 in @ref{Specify Location}.
16907 Use the qualifier @samp{task @var{taskno}} with a breakpoint command
16908 to specify that you only want @value{GDBN} to stop the program when a
16909 particular Ada task reaches this breakpoint. The @var{taskno} is one of the
16910 numeric task identifiers assigned by @value{GDBN}, shown in the first
16911 column of the @samp{info tasks} display.
16913 If you do not specify @samp{task @var{taskno}} when you set a
16914 breakpoint, the breakpoint applies to @emph{all} tasks of your
16917 You can use the @code{task} qualifier on conditional breakpoints as
16918 well; in this case, place @samp{task @var{taskno}} before the
16919 breakpoint condition (before the @code{if}).
16927 (@value{GDBP}) info tasks
16928 ID TID P-ID Pri State Name
16929 1 140022020 0 15 Child Activation Wait main_task
16930 2 140045060 1 15 Accept/Select Wait t2
16931 3 140044840 1 15 Runnable t1
16932 * 4 140056040 1 15 Runnable t3
16933 (@value{GDBP}) b 15 task 2
16934 Breakpoint 5 at 0x120044cb0: file test_task_debug.adb, line 15.
16935 (@value{GDBP}) cont
16940 Breakpoint 5, test_task_debug () at test_task_debug.adb:15
16942 (@value{GDBP}) info tasks
16943 ID TID P-ID Pri State Name
16944 1 140022020 0 15 Child Activation Wait main_task
16945 * 2 140045060 1 15 Runnable t2
16946 3 140044840 1 15 Runnable t1
16947 4 140056040 1 15 Delay Sleep t3
16951 @node Ada Tasks and Core Files
16952 @subsubsection Tasking Support when Debugging Core Files
16953 @cindex Ada tasking and core file debugging
16955 When inspecting a core file, as opposed to debugging a live program,
16956 tasking support may be limited or even unavailable, depending on
16957 the platform being used.
16958 For instance, on x86-linux, the list of tasks is available, but task
16959 switching is not supported.
16961 On certain platforms, the debugger needs to perform some
16962 memory writes in order to provide Ada tasking support. When inspecting
16963 a core file, this means that the core file must be opened with read-write
16964 privileges, using the command @samp{"set write on"} (@pxref{Patching}).
16965 Under these circumstances, you should make a backup copy of the core
16966 file before inspecting it with @value{GDBN}.
16968 @node Ravenscar Profile
16969 @subsubsection Tasking Support when using the Ravenscar Profile
16970 @cindex Ravenscar Profile
16972 The @dfn{Ravenscar Profile} is a subset of the Ada tasking features,
16973 specifically designed for systems with safety-critical real-time
16977 @kindex set ravenscar task-switching on
16978 @cindex task switching with program using Ravenscar Profile
16979 @item set ravenscar task-switching on
16980 Allows task switching when debugging a program that uses the Ravenscar
16981 Profile. This is the default.
16983 @kindex set ravenscar task-switching off
16984 @item set ravenscar task-switching off
16985 Turn off task switching when debugging a program that uses the Ravenscar
16986 Profile. This is mostly intended to disable the code that adds support
16987 for the Ravenscar Profile, in case a bug in either @value{GDBN} or in
16988 the Ravenscar runtime is preventing @value{GDBN} from working properly.
16989 To be effective, this command should be run before the program is started.
16991 @kindex show ravenscar task-switching
16992 @item show ravenscar task-switching
16993 Show whether it is possible to switch from task to task in a program
16994 using the Ravenscar Profile.
16999 @subsubsection Ada Settings
17000 @cindex Ada settings
17003 @kindex set varsize-limit
17004 @item set varsize-limit @var{size}
17005 Prevent @value{GDBN} from attempting to evaluate objects whose size
17006 is above the given limit (@var{size}) when those sizes are computed
17007 from run-time quantities. This is typically the case when the object
17008 has a variable size, such as an array whose bounds are not known at
17009 compile time for example. Setting @var{size} to @code{unlimited}
17010 removes the size limitation. By default, the limit is about 65KB.
17012 The purpose of having such a limit is to prevent @value{GDBN} from
17013 trying to grab enormous chunks of virtual memory when asked to evaluate
17014 a quantity whose bounds have been corrupted or have not yet been fully
17015 initialized. The limit applies to the results of some subexpressions
17016 as well as to complete expressions. For example, an expression denoting
17017 a simple integer component, such as @code{x.y.z}, may fail if the size of
17018 @code{x.y} is variable and exceeds @code{size}. On the other hand,
17019 @value{GDBN} is sometimes clever; the expression @code{A(i)}, where
17020 @code{A} is an array variable with non-constant size, will generally
17021 succeed regardless of the bounds on @code{A}, as long as the component
17022 size is less than @var{size}.
17024 @kindex show varsize-limit
17025 @item show varsize-limit
17026 Show the limit on types whose size is determined by run-time quantities.
17030 @subsubsection Known Peculiarities of Ada Mode
17031 @cindex Ada, problems
17033 Besides the omissions listed previously (@pxref{Omissions from Ada}),
17034 we know of several problems with and limitations of Ada mode in
17036 some of which will be fixed with planned future releases of the debugger
17037 and the GNU Ada compiler.
17041 Static constants that the compiler chooses not to materialize as objects in
17042 storage are invisible to the debugger.
17045 Named parameter associations in function argument lists are ignored (the
17046 argument lists are treated as positional).
17049 Many useful library packages are currently invisible to the debugger.
17052 Fixed-point arithmetic, conversions, input, and output is carried out using
17053 floating-point arithmetic, and may give results that only approximate those on
17057 The GNAT compiler never generates the prefix @code{Standard} for any of
17058 the standard symbols defined by the Ada language. @value{GDBN} knows about
17059 this: it will strip the prefix from names when you use it, and will never
17060 look for a name you have so qualified among local symbols, nor match against
17061 symbols in other packages or subprograms. If you have
17062 defined entities anywhere in your program other than parameters and
17063 local variables whose simple names match names in @code{Standard},
17064 GNAT's lack of qualification here can cause confusion. When this happens,
17065 you can usually resolve the confusion
17066 by qualifying the problematic names with package
17067 @code{Standard} explicitly.
17070 Older versions of the compiler sometimes generate erroneous debugging
17071 information, resulting in the debugger incorrectly printing the value
17072 of affected entities. In some cases, the debugger is able to work
17073 around an issue automatically. In other cases, the debugger is able
17074 to work around the issue, but the work-around has to be specifically
17077 @kindex set ada trust-PAD-over-XVS
17078 @kindex show ada trust-PAD-over-XVS
17081 @item set ada trust-PAD-over-XVS on
17082 Configure GDB to strictly follow the GNAT encoding when computing the
17083 value of Ada entities, particularly when @code{PAD} and @code{PAD___XVS}
17084 types are involved (see @code{ada/exp_dbug.ads} in the GCC sources for
17085 a complete description of the encoding used by the GNAT compiler).
17086 This is the default.
17088 @item set ada trust-PAD-over-XVS off
17089 This is related to the encoding using by the GNAT compiler. If @value{GDBN}
17090 sometimes prints the wrong value for certain entities, changing @code{ada
17091 trust-PAD-over-XVS} to @code{off} activates a work-around which may fix
17092 the issue. It is always safe to set @code{ada trust-PAD-over-XVS} to
17093 @code{off}, but this incurs a slight performance penalty, so it is
17094 recommended to leave this setting to @code{on} unless necessary.
17098 @cindex GNAT descriptive types
17099 @cindex GNAT encoding
17100 Internally, the debugger also relies on the compiler following a number
17101 of conventions known as the @samp{GNAT Encoding}, all documented in
17102 @file{gcc/ada/exp_dbug.ads} in the GCC sources. This encoding describes
17103 how the debugging information should be generated for certain types.
17104 In particular, this convention makes use of @dfn{descriptive types},
17105 which are artificial types generated purely to help the debugger.
17107 These encodings were defined at a time when the debugging information
17108 format used was not powerful enough to describe some of the more complex
17109 types available in Ada. Since DWARF allows us to express nearly all
17110 Ada features, the long-term goal is to slowly replace these descriptive
17111 types by their pure DWARF equivalent. To facilitate that transition,
17112 a new maintenance option is available to force the debugger to ignore
17113 those descriptive types. It allows the user to quickly evaluate how
17114 well @value{GDBN} works without them.
17118 @kindex maint ada set ignore-descriptive-types
17119 @item maintenance ada set ignore-descriptive-types [on|off]
17120 Control whether the debugger should ignore descriptive types.
17121 The default is not to ignore descriptives types (@code{off}).
17123 @kindex maint ada show ignore-descriptive-types
17124 @item maintenance ada show ignore-descriptive-types
17125 Show if descriptive types are ignored by @value{GDBN}.
17129 @node Unsupported Languages
17130 @section Unsupported Languages
17132 @cindex unsupported languages
17133 @cindex minimal language
17134 In addition to the other fully-supported programming languages,
17135 @value{GDBN} also provides a pseudo-language, called @code{minimal}.
17136 It does not represent a real programming language, but provides a set
17137 of capabilities close to what the C or assembly languages provide.
17138 This should allow most simple operations to be performed while debugging
17139 an application that uses a language currently not supported by @value{GDBN}.
17141 If the language is set to @code{auto}, @value{GDBN} will automatically
17142 select this language if the current frame corresponds to an unsupported
17146 @chapter Examining the Symbol Table
17148 The commands described in this chapter allow you to inquire about the
17149 symbols (names of variables, functions and types) defined in your
17150 program. This information is inherent in the text of your program and
17151 does not change as your program executes. @value{GDBN} finds it in your
17152 program's symbol table, in the file indicated when you started @value{GDBN}
17153 (@pxref{File Options, ,Choosing Files}), or by one of the
17154 file-management commands (@pxref{Files, ,Commands to Specify Files}).
17156 @cindex symbol names
17157 @cindex names of symbols
17158 @cindex quoting names
17159 @anchor{quoting names}
17160 Occasionally, you may need to refer to symbols that contain unusual
17161 characters, which @value{GDBN} ordinarily treats as word delimiters. The
17162 most frequent case is in referring to static variables in other
17163 source files (@pxref{Variables,,Program Variables}). File names
17164 are recorded in object files as debugging symbols, but @value{GDBN} would
17165 ordinarily parse a typical file name, like @file{foo.c}, as the three words
17166 @samp{foo} @samp{.} @samp{c}. To allow @value{GDBN} to recognize
17167 @samp{foo.c} as a single symbol, enclose it in single quotes; for example,
17174 looks up the value of @code{x} in the scope of the file @file{foo.c}.
17177 @cindex case-insensitive symbol names
17178 @cindex case sensitivity in symbol names
17179 @kindex set case-sensitive
17180 @item set case-sensitive on
17181 @itemx set case-sensitive off
17182 @itemx set case-sensitive auto
17183 Normally, when @value{GDBN} looks up symbols, it matches their names
17184 with case sensitivity determined by the current source language.
17185 Occasionally, you may wish to control that. The command @code{set
17186 case-sensitive} lets you do that by specifying @code{on} for
17187 case-sensitive matches or @code{off} for case-insensitive ones. If
17188 you specify @code{auto}, case sensitivity is reset to the default
17189 suitable for the source language. The default is case-sensitive
17190 matches for all languages except for Fortran, for which the default is
17191 case-insensitive matches.
17193 @kindex show case-sensitive
17194 @item show case-sensitive
17195 This command shows the current setting of case sensitivity for symbols
17198 @kindex set print type methods
17199 @item set print type methods
17200 @itemx set print type methods on
17201 @itemx set print type methods off
17202 Normally, when @value{GDBN} prints a class, it displays any methods
17203 declared in that class. You can control this behavior either by
17204 passing the appropriate flag to @code{ptype}, or using @command{set
17205 print type methods}. Specifying @code{on} will cause @value{GDBN} to
17206 display the methods; this is the default. Specifying @code{off} will
17207 cause @value{GDBN} to omit the methods.
17209 @kindex show print type methods
17210 @item show print type methods
17211 This command shows the current setting of method display when printing
17214 @kindex set print type nested-type-limit
17215 @item set print type nested-type-limit @var{limit}
17216 @itemx set print type nested-type-limit unlimited
17217 Set the limit of displayed nested types that the type printer will
17218 show. A @var{limit} of @code{unlimited} or @code{-1} will show all
17219 nested definitions. By default, the type printer will not show any nested
17220 types defined in classes.
17222 @kindex show print type nested-type-limit
17223 @item show print type nested-type-limit
17224 This command shows the current display limit of nested types when
17227 @kindex set print type typedefs
17228 @item set print type typedefs
17229 @itemx set print type typedefs on
17230 @itemx set print type typedefs off
17232 Normally, when @value{GDBN} prints a class, it displays any typedefs
17233 defined in that class. You can control this behavior either by
17234 passing the appropriate flag to @code{ptype}, or using @command{set
17235 print type typedefs}. Specifying @code{on} will cause @value{GDBN} to
17236 display the typedef definitions; this is the default. Specifying
17237 @code{off} will cause @value{GDBN} to omit the typedef definitions.
17238 Note that this controls whether the typedef definition itself is
17239 printed, not whether typedef names are substituted when printing other
17242 @kindex show print type typedefs
17243 @item show print type typedefs
17244 This command shows the current setting of typedef display when
17247 @kindex info address
17248 @cindex address of a symbol
17249 @item info address @var{symbol}
17250 Describe where the data for @var{symbol} is stored. For a register
17251 variable, this says which register it is kept in. For a non-register
17252 local variable, this prints the stack-frame offset at which the variable
17255 Note the contrast with @samp{print &@var{symbol}}, which does not work
17256 at all for a register variable, and for a stack local variable prints
17257 the exact address of the current instantiation of the variable.
17259 @kindex info symbol
17260 @cindex symbol from address
17261 @cindex closest symbol and offset for an address
17262 @item info symbol @var{addr}
17263 Print the name of a symbol which is stored at the address @var{addr}.
17264 If no symbol is stored exactly at @var{addr}, @value{GDBN} prints the
17265 nearest symbol and an offset from it:
17268 (@value{GDBP}) info symbol 0x54320
17269 _initialize_vx + 396 in section .text
17273 This is the opposite of the @code{info address} command. You can use
17274 it to find out the name of a variable or a function given its address.
17276 For dynamically linked executables, the name of executable or shared
17277 library containing the symbol is also printed:
17280 (@value{GDBP}) info symbol 0x400225
17281 _start + 5 in section .text of /tmp/a.out
17282 (@value{GDBP}) info symbol 0x2aaaac2811cf
17283 __read_nocancel + 6 in section .text of /usr/lib64/libc.so.6
17288 @item demangle @r{[}-l @var{language}@r{]} @r{[}@var{--}@r{]} @var{name}
17289 Demangle @var{name}.
17290 If @var{language} is provided it is the name of the language to demangle
17291 @var{name} in. Otherwise @var{name} is demangled in the current language.
17293 The @samp{--} option specifies the end of options,
17294 and is useful when @var{name} begins with a dash.
17296 The parameter @code{demangle-style} specifies how to interpret the kind
17297 of mangling used. @xref{Print Settings}.
17300 @item whatis[/@var{flags}] [@var{arg}]
17301 Print the data type of @var{arg}, which can be either an expression
17302 or a name of a data type. With no argument, print the data type of
17303 @code{$}, the last value in the value history.
17305 If @var{arg} is an expression (@pxref{Expressions, ,Expressions}), it
17306 is not actually evaluated, and any side-effecting operations (such as
17307 assignments or function calls) inside it do not take place.
17309 If @var{arg} is a variable or an expression, @code{whatis} prints its
17310 literal type as it is used in the source code. If the type was
17311 defined using a @code{typedef}, @code{whatis} will @emph{not} print
17312 the data type underlying the @code{typedef}. If the type of the
17313 variable or the expression is a compound data type, such as
17314 @code{struct} or @code{class}, @code{whatis} never prints their
17315 fields or methods. It just prints the @code{struct}/@code{class}
17316 name (a.k.a.@: its @dfn{tag}). If you want to see the members of
17317 such a compound data type, use @code{ptype}.
17319 If @var{arg} is a type name that was defined using @code{typedef},
17320 @code{whatis} @dfn{unrolls} only one level of that @code{typedef}.
17321 Unrolling means that @code{whatis} will show the underlying type used
17322 in the @code{typedef} declaration of @var{arg}. However, if that
17323 underlying type is also a @code{typedef}, @code{whatis} will not
17326 For C code, the type names may also have the form @samp{class
17327 @var{class-name}}, @samp{struct @var{struct-tag}}, @samp{union
17328 @var{union-tag}} or @samp{enum @var{enum-tag}}.
17330 @var{flags} can be used to modify how the type is displayed.
17331 Available flags are:
17335 Display in ``raw'' form. Normally, @value{GDBN} substitutes template
17336 parameters and typedefs defined in a class when printing the class'
17337 members. The @code{/r} flag disables this.
17340 Do not print methods defined in the class.
17343 Print methods defined in the class. This is the default, but the flag
17344 exists in case you change the default with @command{set print type methods}.
17347 Do not print typedefs defined in the class. Note that this controls
17348 whether the typedef definition itself is printed, not whether typedef
17349 names are substituted when printing other types.
17352 Print typedefs defined in the class. This is the default, but the flag
17353 exists in case you change the default with @command{set print type typedefs}.
17356 Print the offsets and sizes of fields in a struct, similar to what the
17357 @command{pahole} tool does. This option implies the @code{/tm} flags.
17359 For example, given the following declarations:
17395 Issuing a @kbd{ptype /o struct tuv} command would print:
17398 (@value{GDBP}) ptype /o struct tuv
17399 /* offset | size */ type = struct tuv @{
17400 /* 0 | 4 */ int a1;
17401 /* XXX 4-byte hole */
17402 /* 8 | 8 */ char *a2;
17403 /* 16 | 4 */ int a3;
17405 /* total size (bytes): 24 */
17409 Notice the format of the first column of comments. There, you can
17410 find two parts separated by the @samp{|} character: the @emph{offset},
17411 which indicates where the field is located inside the struct, in
17412 bytes, and the @emph{size} of the field. Another interesting line is
17413 the marker of a @emph{hole} in the struct, indicating that it may be
17414 possible to pack the struct and make it use less space by reorganizing
17417 It is also possible to print offsets inside an union:
17420 (@value{GDBP}) ptype /o union qwe
17421 /* offset | size */ type = union qwe @{
17422 /* 24 */ struct tuv @{
17423 /* 0 | 4 */ int a1;
17424 /* XXX 4-byte hole */
17425 /* 8 | 8 */ char *a2;
17426 /* 16 | 4 */ int a3;
17428 /* total size (bytes): 24 */
17430 /* 40 */ struct xyz @{
17431 /* 0 | 4 */ int f1;
17432 /* 4 | 1 */ char f2;
17433 /* XXX 3-byte hole */
17434 /* 8 | 8 */ void *f3;
17435 /* 16 | 24 */ struct tuv @{
17436 /* 16 | 4 */ int a1;
17437 /* XXX 4-byte hole */
17438 /* 24 | 8 */ char *a2;
17439 /* 32 | 4 */ int a3;
17441 /* total size (bytes): 24 */
17444 /* total size (bytes): 40 */
17447 /* total size (bytes): 40 */
17451 In this case, since @code{struct tuv} and @code{struct xyz} occupy the
17452 same space (because we are dealing with an union), the offset is not
17453 printed for them. However, you can still examine the offset of each
17454 of these structures' fields.
17456 Another useful scenario is printing the offsets of a struct containing
17460 (@value{GDBP}) ptype /o struct tyu
17461 /* offset | size */ type = struct tyu @{
17462 /* 0:31 | 4 */ int a1 : 1;
17463 /* 0:28 | 4 */ int a2 : 3;
17464 /* 0: 5 | 4 */ int a3 : 23;
17465 /* 3: 3 | 1 */ signed char a4 : 2;
17466 /* XXX 3-bit hole */
17467 /* XXX 4-byte hole */
17468 /* 8 | 8 */ int64_t a5;
17469 /* 16:27 | 4 */ int a6 : 5;
17470 /* 16:56 | 8 */ int64_t a7 : 3;
17472 /* total size (bytes): 24 */
17476 Note how the offset information is now extended to also include how
17477 many bits are left to be used in each bitfield.
17481 @item ptype[/@var{flags}] [@var{arg}]
17482 @code{ptype} accepts the same arguments as @code{whatis}, but prints a
17483 detailed description of the type, instead of just the name of the type.
17484 @xref{Expressions, ,Expressions}.
17486 Contrary to @code{whatis}, @code{ptype} always unrolls any
17487 @code{typedef}s in its argument declaration, whether the argument is
17488 a variable, expression, or a data type. This means that @code{ptype}
17489 of a variable or an expression will not print literally its type as
17490 present in the source code---use @code{whatis} for that. @code{typedef}s at
17491 the pointer or reference targets are also unrolled. Only @code{typedef}s of
17492 fields, methods and inner @code{class typedef}s of @code{struct}s,
17493 @code{class}es and @code{union}s are not unrolled even with @code{ptype}.
17495 For example, for this variable declaration:
17498 typedef double real_t;
17499 struct complex @{ real_t real; double imag; @};
17500 typedef struct complex complex_t;
17502 real_t *real_pointer_var;
17506 the two commands give this output:
17510 (@value{GDBP}) whatis var
17512 (@value{GDBP}) ptype var
17513 type = struct complex @{
17517 (@value{GDBP}) whatis complex_t
17518 type = struct complex
17519 (@value{GDBP}) whatis struct complex
17520 type = struct complex
17521 (@value{GDBP}) ptype struct complex
17522 type = struct complex @{
17526 (@value{GDBP}) whatis real_pointer_var
17528 (@value{GDBP}) ptype real_pointer_var
17534 As with @code{whatis}, using @code{ptype} without an argument refers to
17535 the type of @code{$}, the last value in the value history.
17537 @cindex incomplete type
17538 Sometimes, programs use opaque data types or incomplete specifications
17539 of complex data structure. If the debug information included in the
17540 program does not allow @value{GDBN} to display a full declaration of
17541 the data type, it will say @samp{<incomplete type>}. For example,
17542 given these declarations:
17546 struct foo *fooptr;
17550 but no definition for @code{struct foo} itself, @value{GDBN} will say:
17553 (@value{GDBP}) ptype foo
17554 $1 = <incomplete type>
17558 ``Incomplete type'' is C terminology for data types that are not
17559 completely specified.
17561 @cindex unknown type
17562 Othertimes, information about a variable's type is completely absent
17563 from the debug information included in the program. This most often
17564 happens when the program or library where the variable is defined
17565 includes no debug information at all. @value{GDBN} knows the variable
17566 exists from inspecting the linker/loader symbol table (e.g., the ELF
17567 dynamic symbol table), but such symbols do not contain type
17568 information. Inspecting the type of a (global) variable for which
17569 @value{GDBN} has no type information shows:
17572 (@value{GDBP}) ptype var
17573 type = <data variable, no debug info>
17576 @xref{Variables, no debug info variables}, for how to print the values
17580 @item info types @var{regexp}
17582 Print a brief description of all types whose names match the regular
17583 expression @var{regexp} (or all types in your program, if you supply
17584 no argument). Each complete typename is matched as though it were a
17585 complete line; thus, @samp{i type value} gives information on all
17586 types in your program whose names include the string @code{value}, but
17587 @samp{i type ^value$} gives information only on types whose complete
17588 name is @code{value}.
17590 This command differs from @code{ptype} in two ways: first, like
17591 @code{whatis}, it does not print a detailed description; second, it
17592 lists all source files and line numbers where a type is defined.
17594 @kindex info type-printers
17595 @item info type-printers
17596 Versions of @value{GDBN} that ship with Python scripting enabled may
17597 have ``type printers'' available. When using @command{ptype} or
17598 @command{whatis}, these printers are consulted when the name of a type
17599 is needed. @xref{Type Printing API}, for more information on writing
17602 @code{info type-printers} displays all the available type printers.
17604 @kindex enable type-printer
17605 @kindex disable type-printer
17606 @item enable type-printer @var{name}@dots{}
17607 @item disable type-printer @var{name}@dots{}
17608 These commands can be used to enable or disable type printers.
17611 @cindex local variables
17612 @item info scope @var{location}
17613 List all the variables local to a particular scope. This command
17614 accepts a @var{location} argument---a function name, a source line, or
17615 an address preceded by a @samp{*}, and prints all the variables local
17616 to the scope defined by that location. (@xref{Specify Location}, for
17617 details about supported forms of @var{location}.) For example:
17620 (@value{GDBP}) @b{info scope command_line_handler}
17621 Scope for command_line_handler:
17622 Symbol rl is an argument at stack/frame offset 8, length 4.
17623 Symbol linebuffer is in static storage at address 0x150a18, length 4.
17624 Symbol linelength is in static storage at address 0x150a1c, length 4.
17625 Symbol p is a local variable in register $esi, length 4.
17626 Symbol p1 is a local variable in register $ebx, length 4.
17627 Symbol nline is a local variable in register $edx, length 4.
17628 Symbol repeat is a local variable at frame offset -8, length 4.
17632 This command is especially useful for determining what data to collect
17633 during a @dfn{trace experiment}, see @ref{Tracepoint Actions,
17636 @kindex info source
17638 Show information about the current source file---that is, the source file for
17639 the function containing the current point of execution:
17642 the name of the source file, and the directory containing it,
17644 the directory it was compiled in,
17646 its length, in lines,
17648 which programming language it is written in,
17650 if the debug information provides it, the program that compiled the file
17651 (which may include, e.g., the compiler version and command line arguments),
17653 whether the executable includes debugging information for that file, and
17654 if so, what format the information is in (e.g., STABS, Dwarf 2, etc.), and
17656 whether the debugging information includes information about
17657 preprocessor macros.
17661 @kindex info sources
17663 Print the names of all source files in your program for which there is
17664 debugging information, organized into two lists: files whose symbols
17665 have already been read, and files whose symbols will be read when needed.
17667 @kindex info functions
17668 @item info functions
17669 Print the names and data types of all defined functions.
17670 Similarly to @samp{info types}, this command groups its output by source
17671 files and annotates each function definition with its source line
17674 @item info functions @var{regexp}
17675 Like @samp{info functions}, but only print the names and data types of
17676 functions whose names contain a match for regular expression
17677 @var{regexp}. Thus, @samp{info fun step} finds all functions whose
17678 names include @code{step}; @samp{info fun ^step} finds those whose names
17679 start with @code{step}. If a function name contains characters that
17680 conflict with the regular expression language (e.g.@:
17681 @samp{operator*()}), they may be quoted with a backslash.
17683 @kindex info variables
17684 @item info variables
17685 Print the names and data types of all variables that are defined
17686 outside of functions (i.e.@: excluding local variables).
17687 The printed variables are grouped by source files and annotated with
17688 their respective source line numbers.
17690 @item info variables @var{regexp}
17691 Like @kbd{info variables}, but only print the names and data types of
17692 non-local variables whose names contain a match for regular expression
17695 @kindex info classes
17696 @cindex Objective-C, classes and selectors
17698 @itemx info classes @var{regexp}
17699 Display all Objective-C classes in your program, or
17700 (with the @var{regexp} argument) all those matching a particular regular
17703 @kindex info selectors
17704 @item info selectors
17705 @itemx info selectors @var{regexp}
17706 Display all Objective-C selectors in your program, or
17707 (with the @var{regexp} argument) all those matching a particular regular
17711 This was never implemented.
17712 @kindex info methods
17714 @itemx info methods @var{regexp}
17715 The @code{info methods} command permits the user to examine all defined
17716 methods within C@t{++} program, or (with the @var{regexp} argument) a
17717 specific set of methods found in the various C@t{++} classes. Many
17718 C@t{++} classes provide a large number of methods. Thus, the output
17719 from the @code{ptype} command can be overwhelming and hard to use. The
17720 @code{info-methods} command filters the methods, printing only those
17721 which match the regular-expression @var{regexp}.
17724 @cindex opaque data types
17725 @kindex set opaque-type-resolution
17726 @item set opaque-type-resolution on
17727 Tell @value{GDBN} to resolve opaque types. An opaque type is a type
17728 declared as a pointer to a @code{struct}, @code{class}, or
17729 @code{union}---for example, @code{struct MyType *}---that is used in one
17730 source file although the full declaration of @code{struct MyType} is in
17731 another source file. The default is on.
17733 A change in the setting of this subcommand will not take effect until
17734 the next time symbols for a file are loaded.
17736 @item set opaque-type-resolution off
17737 Tell @value{GDBN} not to resolve opaque types. In this case, the type
17738 is printed as follows:
17740 @{<no data fields>@}
17743 @kindex show opaque-type-resolution
17744 @item show opaque-type-resolution
17745 Show whether opaque types are resolved or not.
17747 @kindex set print symbol-loading
17748 @cindex print messages when symbols are loaded
17749 @item set print symbol-loading
17750 @itemx set print symbol-loading full
17751 @itemx set print symbol-loading brief
17752 @itemx set print symbol-loading off
17753 The @code{set print symbol-loading} command allows you to control the
17754 printing of messages when @value{GDBN} loads symbol information.
17755 By default a message is printed for the executable and one for each
17756 shared library, and normally this is what you want. However, when
17757 debugging apps with large numbers of shared libraries these messages
17759 When set to @code{brief} a message is printed for each executable,
17760 and when @value{GDBN} loads a collection of shared libraries at once
17761 it will only print one message regardless of the number of shared
17762 libraries. When set to @code{off} no messages are printed.
17764 @kindex show print symbol-loading
17765 @item show print symbol-loading
17766 Show whether messages will be printed when a @value{GDBN} command
17767 entered from the keyboard causes symbol information to be loaded.
17769 @kindex maint print symbols
17770 @cindex symbol dump
17771 @kindex maint print psymbols
17772 @cindex partial symbol dump
17773 @kindex maint print msymbols
17774 @cindex minimal symbol dump
17775 @item maint print symbols @r{[}-pc @var{address}@r{]} @r{[}@var{filename}@r{]}
17776 @itemx maint print symbols @r{[}-objfile @var{objfile}@r{]} @r{[}-source @var{source}@r{]} @r{[}--@r{]} @r{[}@var{filename}@r{]}
17777 @itemx maint print psymbols @r{[}-objfile @var{objfile}@r{]} @r{[}-pc @var{address}@r{]} @r{[}--@r{]} @r{[}@var{filename}@r{]}
17778 @itemx maint print psymbols @r{[}-objfile @var{objfile}@r{]} @r{[}-source @var{source}@r{]} @r{[}--@r{]} @r{[}@var{filename}@r{]}
17779 @itemx maint print msymbols @r{[}-objfile @var{objfile}@r{]} @r{[}--@r{]} @r{[}@var{filename}@r{]}
17780 Write a dump of debugging symbol data into the file @var{filename} or
17781 the terminal if @var{filename} is unspecified.
17782 If @code{-objfile @var{objfile}} is specified, only dump symbols for
17784 If @code{-pc @var{address}} is specified, only dump symbols for the file
17785 with code at that address. Note that @var{address} may be a symbol like
17787 If @code{-source @var{source}} is specified, only dump symbols for that
17790 These commands are used to debug the @value{GDBN} symbol-reading code.
17791 These commands do not modify internal @value{GDBN} state, therefore
17792 @samp{maint print symbols} will only print symbols for already expanded symbol
17794 You can use the command @code{info sources} to find out which files these are.
17795 If you use @samp{maint print psymbols} instead, the dump shows information
17796 about symbols that @value{GDBN} only knows partially---that is, symbols
17797 defined in files that @value{GDBN} has skimmed, but not yet read completely.
17798 Finally, @samp{maint print msymbols} just dumps ``minimal symbols'', e.g.,
17801 @xref{Files, ,Commands to Specify Files}, for a discussion of how
17802 @value{GDBN} reads symbols (in the description of @code{symbol-file}).
17804 @kindex maint info symtabs
17805 @kindex maint info psymtabs
17806 @cindex listing @value{GDBN}'s internal symbol tables
17807 @cindex symbol tables, listing @value{GDBN}'s internal
17808 @cindex full symbol tables, listing @value{GDBN}'s internal
17809 @cindex partial symbol tables, listing @value{GDBN}'s internal
17810 @item maint info symtabs @r{[} @var{regexp} @r{]}
17811 @itemx maint info psymtabs @r{[} @var{regexp} @r{]}
17813 List the @code{struct symtab} or @code{struct partial_symtab}
17814 structures whose names match @var{regexp}. If @var{regexp} is not
17815 given, list them all. The output includes expressions which you can
17816 copy into a @value{GDBN} debugging this one to examine a particular
17817 structure in more detail. For example:
17820 (@value{GDBP}) maint info psymtabs dwarf2read
17821 @{ objfile /home/gnu/build/gdb/gdb
17822 ((struct objfile *) 0x82e69d0)
17823 @{ psymtab /home/gnu/src/gdb/dwarf2read.c
17824 ((struct partial_symtab *) 0x8474b10)
17827 text addresses 0x814d3c8 -- 0x8158074
17828 globals (* (struct partial_symbol **) 0x8507a08 @@ 9)
17829 statics (* (struct partial_symbol **) 0x40e95b78 @@ 2882)
17830 dependencies (none)
17833 (@value{GDBP}) maint info symtabs
17837 We see that there is one partial symbol table whose filename contains
17838 the string @samp{dwarf2read}, belonging to the @samp{gdb} executable;
17839 and we see that @value{GDBN} has not read in any symtabs yet at all.
17840 If we set a breakpoint on a function, that will cause @value{GDBN} to
17841 read the symtab for the compilation unit containing that function:
17844 (@value{GDBP}) break dwarf2_psymtab_to_symtab
17845 Breakpoint 1 at 0x814e5da: file /home/gnu/src/gdb/dwarf2read.c,
17847 (@value{GDBP}) maint info symtabs
17848 @{ objfile /home/gnu/build/gdb/gdb
17849 ((struct objfile *) 0x82e69d0)
17850 @{ symtab /home/gnu/src/gdb/dwarf2read.c
17851 ((struct symtab *) 0x86c1f38)
17854 blockvector ((struct blockvector *) 0x86c1bd0) (primary)
17855 linetable ((struct linetable *) 0x8370fa0)
17856 debugformat DWARF 2
17862 @kindex maint info line-table
17863 @cindex listing @value{GDBN}'s internal line tables
17864 @cindex line tables, listing @value{GDBN}'s internal
17865 @item maint info line-table @r{[} @var{regexp} @r{]}
17867 List the @code{struct linetable} from all @code{struct symtab}
17868 instances whose name matches @var{regexp}. If @var{regexp} is not
17869 given, list the @code{struct linetable} from all @code{struct symtab}.
17871 @kindex maint set symbol-cache-size
17872 @cindex symbol cache size
17873 @item maint set symbol-cache-size @var{size}
17874 Set the size of the symbol cache to @var{size}.
17875 The default size is intended to be good enough for debugging
17876 most applications. This option exists to allow for experimenting
17877 with different sizes.
17879 @kindex maint show symbol-cache-size
17880 @item maint show symbol-cache-size
17881 Show the size of the symbol cache.
17883 @kindex maint print symbol-cache
17884 @cindex symbol cache, printing its contents
17885 @item maint print symbol-cache
17886 Print the contents of the symbol cache.
17887 This is useful when debugging symbol cache issues.
17889 @kindex maint print symbol-cache-statistics
17890 @cindex symbol cache, printing usage statistics
17891 @item maint print symbol-cache-statistics
17892 Print symbol cache usage statistics.
17893 This helps determine how well the cache is being utilized.
17895 @kindex maint flush-symbol-cache
17896 @cindex symbol cache, flushing
17897 @item maint flush-symbol-cache
17898 Flush the contents of the symbol cache, all entries are removed.
17899 This command is useful when debugging the symbol cache.
17900 It is also useful when collecting performance data.
17905 @chapter Altering Execution
17907 Once you think you have found an error in your program, you might want to
17908 find out for certain whether correcting the apparent error would lead to
17909 correct results in the rest of the run. You can find the answer by
17910 experiment, using the @value{GDBN} features for altering execution of the
17913 For example, you can store new values into variables or memory
17914 locations, give your program a signal, restart it at a different
17915 address, or even return prematurely from a function.
17918 * Assignment:: Assignment to variables
17919 * Jumping:: Continuing at a different address
17920 * Signaling:: Giving your program a signal
17921 * Returning:: Returning from a function
17922 * Calling:: Calling your program's functions
17923 * Patching:: Patching your program
17924 * Compiling and Injecting Code:: Compiling and injecting code in @value{GDBN}
17928 @section Assignment to Variables
17931 @cindex setting variables
17932 To alter the value of a variable, evaluate an assignment expression.
17933 @xref{Expressions, ,Expressions}. For example,
17940 stores the value 4 into the variable @code{x}, and then prints the
17941 value of the assignment expression (which is 4).
17942 @xref{Languages, ,Using @value{GDBN} with Different Languages}, for more
17943 information on operators in supported languages.
17945 @kindex set variable
17946 @cindex variables, setting
17947 If you are not interested in seeing the value of the assignment, use the
17948 @code{set} command instead of the @code{print} command. @code{set} is
17949 really the same as @code{print} except that the expression's value is
17950 not printed and is not put in the value history (@pxref{Value History,
17951 ,Value History}). The expression is evaluated only for its effects.
17953 If the beginning of the argument string of the @code{set} command
17954 appears identical to a @code{set} subcommand, use the @code{set
17955 variable} command instead of just @code{set}. This command is identical
17956 to @code{set} except for its lack of subcommands. For example, if your
17957 program has a variable @code{width}, you get an error if you try to set
17958 a new value with just @samp{set width=13}, because @value{GDBN} has the
17959 command @code{set width}:
17962 (@value{GDBP}) whatis width
17964 (@value{GDBP}) p width
17966 (@value{GDBP}) set width=47
17967 Invalid syntax in expression.
17971 The invalid expression, of course, is @samp{=47}. In
17972 order to actually set the program's variable @code{width}, use
17975 (@value{GDBP}) set var width=47
17978 Because the @code{set} command has many subcommands that can conflict
17979 with the names of program variables, it is a good idea to use the
17980 @code{set variable} command instead of just @code{set}. For example, if
17981 your program has a variable @code{g}, you run into problems if you try
17982 to set a new value with just @samp{set g=4}, because @value{GDBN} has
17983 the command @code{set gnutarget}, abbreviated @code{set g}:
17987 (@value{GDBP}) whatis g
17991 (@value{GDBP}) set g=4
17995 The program being debugged has been started already.
17996 Start it from the beginning? (y or n) y
17997 Starting program: /home/smith/cc_progs/a.out
17998 "/home/smith/cc_progs/a.out": can't open to read symbols:
17999 Invalid bfd target.
18000 (@value{GDBP}) show g
18001 The current BFD target is "=4".
18006 The program variable @code{g} did not change, and you silently set the
18007 @code{gnutarget} to an invalid value. In order to set the variable
18011 (@value{GDBP}) set var g=4
18014 @value{GDBN} allows more implicit conversions in assignments than C; you can
18015 freely store an integer value into a pointer variable or vice versa,
18016 and you can convert any structure to any other structure that is the
18017 same length or shorter.
18018 @comment FIXME: how do structs align/pad in these conversions?
18019 @comment /doc@cygnus.com 18dec1990
18021 To store values into arbitrary places in memory, use the @samp{@{@dots{}@}}
18022 construct to generate a value of specified type at a specified address
18023 (@pxref{Expressions, ,Expressions}). For example, @code{@{int@}0x83040} refers
18024 to memory location @code{0x83040} as an integer (which implies a certain size
18025 and representation in memory), and
18028 set @{int@}0x83040 = 4
18032 stores the value 4 into that memory location.
18035 @section Continuing at a Different Address
18037 Ordinarily, when you continue your program, you do so at the place where
18038 it stopped, with the @code{continue} command. You can instead continue at
18039 an address of your own choosing, with the following commands:
18043 @kindex j @r{(@code{jump})}
18044 @item jump @var{location}
18045 @itemx j @var{location}
18046 Resume execution at @var{location}. Execution stops again immediately
18047 if there is a breakpoint there. @xref{Specify Location}, for a description
18048 of the different forms of @var{location}. It is common
18049 practice to use the @code{tbreak} command in conjunction with
18050 @code{jump}. @xref{Set Breaks, ,Setting Breakpoints}.
18052 The @code{jump} command does not change the current stack frame, or
18053 the stack pointer, or the contents of any memory location or any
18054 register other than the program counter. If @var{location} is in
18055 a different function from the one currently executing, the results may
18056 be bizarre if the two functions expect different patterns of arguments or
18057 of local variables. For this reason, the @code{jump} command requests
18058 confirmation if the specified line is not in the function currently
18059 executing. However, even bizarre results are predictable if you are
18060 well acquainted with the machine-language code of your program.
18063 On many systems, you can get much the same effect as the @code{jump}
18064 command by storing a new value into the register @code{$pc}. The
18065 difference is that this does not start your program running; it only
18066 changes the address of where it @emph{will} run when you continue. For
18074 makes the next @code{continue} command or stepping command execute at
18075 address @code{0x485}, rather than at the address where your program stopped.
18076 @xref{Continuing and Stepping, ,Continuing and Stepping}.
18078 The most common occasion to use the @code{jump} command is to back
18079 up---perhaps with more breakpoints set---over a portion of a program
18080 that has already executed, in order to examine its execution in more
18085 @section Giving your Program a Signal
18086 @cindex deliver a signal to a program
18090 @item signal @var{signal}
18091 Resume execution where your program is stopped, but immediately give it the
18092 signal @var{signal}. The @var{signal} can be the name or the number of a
18093 signal. For example, on many systems @code{signal 2} and @code{signal
18094 SIGINT} are both ways of sending an interrupt signal.
18096 Alternatively, if @var{signal} is zero, continue execution without
18097 giving a signal. This is useful when your program stopped on account of
18098 a signal and would ordinarily see the signal when resumed with the
18099 @code{continue} command; @samp{signal 0} causes it to resume without a
18102 @emph{Note:} When resuming a multi-threaded program, @var{signal} is
18103 delivered to the currently selected thread, not the thread that last
18104 reported a stop. This includes the situation where a thread was
18105 stopped due to a signal. So if you want to continue execution
18106 suppressing the signal that stopped a thread, you should select that
18107 same thread before issuing the @samp{signal 0} command. If you issue
18108 the @samp{signal 0} command with another thread as the selected one,
18109 @value{GDBN} detects that and asks for confirmation.
18111 Invoking the @code{signal} command is not the same as invoking the
18112 @code{kill} utility from the shell. Sending a signal with @code{kill}
18113 causes @value{GDBN} to decide what to do with the signal depending on
18114 the signal handling tables (@pxref{Signals}). The @code{signal} command
18115 passes the signal directly to your program.
18117 @code{signal} does not repeat when you press @key{RET} a second time
18118 after executing the command.
18120 @kindex queue-signal
18121 @item queue-signal @var{signal}
18122 Queue @var{signal} to be delivered immediately to the current thread
18123 when execution of the thread resumes. The @var{signal} can be the name or
18124 the number of a signal. For example, on many systems @code{signal 2} and
18125 @code{signal SIGINT} are both ways of sending an interrupt signal.
18126 The handling of the signal must be set to pass the signal to the program,
18127 otherwise @value{GDBN} will report an error.
18128 You can control the handling of signals from @value{GDBN} with the
18129 @code{handle} command (@pxref{Signals}).
18131 Alternatively, if @var{signal} is zero, any currently queued signal
18132 for the current thread is discarded and when execution resumes no signal
18133 will be delivered. This is useful when your program stopped on account
18134 of a signal and would ordinarily see the signal when resumed with the
18135 @code{continue} command.
18137 This command differs from the @code{signal} command in that the signal
18138 is just queued, execution is not resumed. And @code{queue-signal} cannot
18139 be used to pass a signal whose handling state has been set to @code{nopass}
18144 @xref{stepping into signal handlers}, for information on how stepping
18145 commands behave when the thread has a signal queued.
18148 @section Returning from a Function
18151 @cindex returning from a function
18154 @itemx return @var{expression}
18155 You can cancel execution of a function call with the @code{return}
18156 command. If you give an
18157 @var{expression} argument, its value is used as the function's return
18161 When you use @code{return}, @value{GDBN} discards the selected stack frame
18162 (and all frames within it). You can think of this as making the
18163 discarded frame return prematurely. If you wish to specify a value to
18164 be returned, give that value as the argument to @code{return}.
18166 This pops the selected stack frame (@pxref{Selection, ,Selecting a
18167 Frame}), and any other frames inside of it, leaving its caller as the
18168 innermost remaining frame. That frame becomes selected. The
18169 specified value is stored in the registers used for returning values
18172 The @code{return} command does not resume execution; it leaves the
18173 program stopped in the state that would exist if the function had just
18174 returned. In contrast, the @code{finish} command (@pxref{Continuing
18175 and Stepping, ,Continuing and Stepping}) resumes execution until the
18176 selected stack frame returns naturally.
18178 @value{GDBN} needs to know how the @var{expression} argument should be set for
18179 the inferior. The concrete registers assignment depends on the OS ABI and the
18180 type being returned by the selected stack frame. For example it is common for
18181 OS ABI to return floating point values in FPU registers while integer values in
18182 CPU registers. Still some ABIs return even floating point values in CPU
18183 registers. Larger integer widths (such as @code{long long int}) also have
18184 specific placement rules. @value{GDBN} already knows the OS ABI from its
18185 current target so it needs to find out also the type being returned to make the
18186 assignment into the right register(s).
18188 Normally, the selected stack frame has debug info. @value{GDBN} will always
18189 use the debug info instead of the implicit type of @var{expression} when the
18190 debug info is available. For example, if you type @kbd{return -1}, and the
18191 function in the current stack frame is declared to return a @code{long long
18192 int}, @value{GDBN} transparently converts the implicit @code{int} value of -1
18193 into a @code{long long int}:
18196 Breakpoint 1, func () at gdb.base/return-nodebug.c:29
18198 (@value{GDBP}) return -1
18199 Make func return now? (y or n) y
18200 #0 0x004004f6 in main () at gdb.base/return-nodebug.c:43
18201 43 printf ("result=%lld\n", func ());
18205 However, if the selected stack frame does not have a debug info, e.g., if the
18206 function was compiled without debug info, @value{GDBN} has to find out the type
18207 to return from user. Specifying a different type by mistake may set the value
18208 in different inferior registers than the caller code expects. For example,
18209 typing @kbd{return -1} with its implicit type @code{int} would set only a part
18210 of a @code{long long int} result for a debug info less function (on 32-bit
18211 architectures). Therefore the user is required to specify the return type by
18212 an appropriate cast explicitly:
18215 Breakpoint 2, 0x0040050b in func ()
18216 (@value{GDBP}) return -1
18217 Return value type not available for selected stack frame.
18218 Please use an explicit cast of the value to return.
18219 (@value{GDBP}) return (long long int) -1
18220 Make selected stack frame return now? (y or n) y
18221 #0 0x00400526 in main ()
18226 @section Calling Program Functions
18229 @cindex calling functions
18230 @cindex inferior functions, calling
18231 @item print @var{expr}
18232 Evaluate the expression @var{expr} and display the resulting value.
18233 The expression may include calls to functions in the program being
18237 @item call @var{expr}
18238 Evaluate the expression @var{expr} without displaying @code{void}
18241 You can use this variant of the @code{print} command if you want to
18242 execute a function from your program that does not return anything
18243 (a.k.a.@: @dfn{a void function}), but without cluttering the output
18244 with @code{void} returned values that @value{GDBN} will otherwise
18245 print. If the result is not void, it is printed and saved in the
18249 It is possible for the function you call via the @code{print} or
18250 @code{call} command to generate a signal (e.g., if there's a bug in
18251 the function, or if you passed it incorrect arguments). What happens
18252 in that case is controlled by the @code{set unwindonsignal} command.
18254 Similarly, with a C@t{++} program it is possible for the function you
18255 call via the @code{print} or @code{call} command to generate an
18256 exception that is not handled due to the constraints of the dummy
18257 frame. In this case, any exception that is raised in the frame, but has
18258 an out-of-frame exception handler will not be found. GDB builds a
18259 dummy-frame for the inferior function call, and the unwinder cannot
18260 seek for exception handlers outside of this dummy-frame. What happens
18261 in that case is controlled by the
18262 @code{set unwind-on-terminating-exception} command.
18265 @item set unwindonsignal
18266 @kindex set unwindonsignal
18267 @cindex unwind stack in called functions
18268 @cindex call dummy stack unwinding
18269 Set unwinding of the stack if a signal is received while in a function
18270 that @value{GDBN} called in the program being debugged. If set to on,
18271 @value{GDBN} unwinds the stack it created for the call and restores
18272 the context to what it was before the call. If set to off (the
18273 default), @value{GDBN} stops in the frame where the signal was
18276 @item show unwindonsignal
18277 @kindex show unwindonsignal
18278 Show the current setting of stack unwinding in the functions called by
18281 @item set unwind-on-terminating-exception
18282 @kindex set unwind-on-terminating-exception
18283 @cindex unwind stack in called functions with unhandled exceptions
18284 @cindex call dummy stack unwinding on unhandled exception.
18285 Set unwinding of the stack if a C@t{++} exception is raised, but left
18286 unhandled while in a function that @value{GDBN} called in the program being
18287 debugged. If set to on (the default), @value{GDBN} unwinds the stack
18288 it created for the call and restores the context to what it was before
18289 the call. If set to off, @value{GDBN} the exception is delivered to
18290 the default C@t{++} exception handler and the inferior terminated.
18292 @item show unwind-on-terminating-exception
18293 @kindex show unwind-on-terminating-exception
18294 Show the current setting of stack unwinding in the functions called by
18299 @subsection Calling functions with no debug info
18301 @cindex no debug info functions
18302 Sometimes, a function you wish to call is missing debug information.
18303 In such case, @value{GDBN} does not know the type of the function,
18304 including the types of the function's parameters. To avoid calling
18305 the inferior function incorrectly, which could result in the called
18306 function functioning erroneously and even crash, @value{GDBN} refuses
18307 to call the function unless you tell it the type of the function.
18309 For prototyped (i.e.@: ANSI/ISO style) functions, there are two ways
18310 to do that. The simplest is to cast the call to the function's
18311 declared return type. For example:
18314 (@value{GDBP}) p getenv ("PATH")
18315 'getenv' has unknown return type; cast the call to its declared return type
18316 (@value{GDBP}) p (char *) getenv ("PATH")
18317 $1 = 0x7fffffffe7ba "/usr/local/bin:/"...
18320 Casting the return type of a no-debug function is equivalent to
18321 casting the function to a pointer to a prototyped function that has a
18322 prototype that matches the types of the passed-in arguments, and
18323 calling that. I.e., the call above is equivalent to:
18326 (@value{GDBP}) p ((char * (*) (const char *)) getenv) ("PATH")
18330 and given this prototyped C or C++ function with float parameters:
18333 float multiply (float v1, float v2) @{ return v1 * v2; @}
18337 these calls are equivalent:
18340 (@value{GDBP}) p (float) multiply (2.0f, 3.0f)
18341 (@value{GDBP}) p ((float (*) (float, float)) multiply) (2.0f, 3.0f)
18344 If the function you wish to call is declared as unprototyped (i.e.@:
18345 old K&R style), you must use the cast-to-function-pointer syntax, so
18346 that @value{GDBN} knows that it needs to apply default argument
18347 promotions (promote float arguments to double). @xref{ABI, float
18348 promotion}. For example, given this unprototyped C function with
18349 float parameters, and no debug info:
18353 multiply_noproto (v1, v2)
18361 you call it like this:
18364 (@value{GDBP}) p ((float (*) ()) multiply_noproto) (2.0f, 3.0f)
18368 @section Patching Programs
18370 @cindex patching binaries
18371 @cindex writing into executables
18372 @cindex writing into corefiles
18374 By default, @value{GDBN} opens the file containing your program's
18375 executable code (or the corefile) read-only. This prevents accidental
18376 alterations to machine code; but it also prevents you from intentionally
18377 patching your program's binary.
18379 If you'd like to be able to patch the binary, you can specify that
18380 explicitly with the @code{set write} command. For example, you might
18381 want to turn on internal debugging flags, or even to make emergency
18387 @itemx set write off
18388 If you specify @samp{set write on}, @value{GDBN} opens executable and
18389 core files for both reading and writing; if you specify @kbd{set write
18390 off} (the default), @value{GDBN} opens them read-only.
18392 If you have already loaded a file, you must load it again (using the
18393 @code{exec-file} or @code{core-file} command) after changing @code{set
18394 write}, for your new setting to take effect.
18398 Display whether executable files and core files are opened for writing
18399 as well as reading.
18402 @node Compiling and Injecting Code
18403 @section Compiling and injecting code in @value{GDBN}
18404 @cindex injecting code
18405 @cindex writing into executables
18406 @cindex compiling code
18408 @value{GDBN} supports on-demand compilation and code injection into
18409 programs running under @value{GDBN}. GCC 5.0 or higher built with
18410 @file{libcc1.so} must be installed for this functionality to be enabled.
18411 This functionality is implemented with the following commands.
18414 @kindex compile code
18415 @item compile code @var{source-code}
18416 @itemx compile code -raw @var{--} @var{source-code}
18417 Compile @var{source-code} with the compiler language found as the current
18418 language in @value{GDBN} (@pxref{Languages}). If compilation and
18419 injection is not supported with the current language specified in
18420 @value{GDBN}, or the compiler does not support this feature, an error
18421 message will be printed. If @var{source-code} compiles and links
18422 successfully, @value{GDBN} will load the object-code emitted,
18423 and execute it within the context of the currently selected inferior.
18424 It is important to note that the compiled code is executed immediately.
18425 After execution, the compiled code is removed from @value{GDBN} and any
18426 new types or variables you have defined will be deleted.
18428 The command allows you to specify @var{source-code} in two ways.
18429 The simplest method is to provide a single line of code to the command.
18433 compile code printf ("hello world\n");
18436 If you specify options on the command line as well as source code, they
18437 may conflict. The @samp{--} delimiter can be used to separate options
18438 from actual source code. E.g.:
18441 compile code -r -- printf ("hello world\n");
18444 Alternatively you can enter source code as multiple lines of text. To
18445 enter this mode, invoke the @samp{compile code} command without any text
18446 following the command. This will start the multiple-line editor and
18447 allow you to type as many lines of source code as required. When you
18448 have completed typing, enter @samp{end} on its own line to exit the
18453 >printf ("hello\n");
18454 >printf ("world\n");
18458 Specifying @samp{-raw}, prohibits @value{GDBN} from wrapping the
18459 provided @var{source-code} in a callable scope. In this case, you must
18460 specify the entry point of the code by defining a function named
18461 @code{_gdb_expr_}. The @samp{-raw} code cannot access variables of the
18462 inferior. Using @samp{-raw} option may be needed for example when
18463 @var{source-code} requires @samp{#include} lines which may conflict with
18464 inferior symbols otherwise.
18466 @kindex compile file
18467 @item compile file @var{filename}
18468 @itemx compile file -raw @var{filename}
18469 Like @code{compile code}, but take the source code from @var{filename}.
18472 compile file /home/user/example.c
18477 @item compile print @var{expr}
18478 @itemx compile print /@var{f} @var{expr}
18479 Compile and execute @var{expr} with the compiler language found as the
18480 current language in @value{GDBN} (@pxref{Languages}). By default the
18481 value of @var{expr} is printed in a format appropriate to its data type;
18482 you can choose a different format by specifying @samp{/@var{f}}, where
18483 @var{f} is a letter specifying the format; see @ref{Output Formats,,Output
18486 @item compile print
18487 @itemx compile print /@var{f}
18488 @cindex reprint the last value
18489 Alternatively you can enter the expression (source code producing it) as
18490 multiple lines of text. To enter this mode, invoke the @samp{compile print}
18491 command without any text following the command. This will start the
18492 multiple-line editor.
18496 The process of compiling and injecting the code can be inspected using:
18499 @anchor{set debug compile}
18500 @item set debug compile
18501 @cindex compile command debugging info
18502 Turns on or off display of @value{GDBN} process of compiling and
18503 injecting the code. The default is off.
18505 @item show debug compile
18506 Displays the current state of displaying @value{GDBN} process of
18507 compiling and injecting the code.
18510 @subsection Compilation options for the @code{compile} command
18512 @value{GDBN} needs to specify the right compilation options for the code
18513 to be injected, in part to make its ABI compatible with the inferior
18514 and in part to make the injected code compatible with @value{GDBN}'s
18518 The options used, in increasing precedence:
18521 @item target architecture and OS options (@code{gdbarch})
18522 These options depend on target processor type and target operating
18523 system, usually they specify at least 32-bit (@code{-m32}) or 64-bit
18524 (@code{-m64}) compilation option.
18526 @item compilation options recorded in the target
18527 @value{NGCC} (since version 4.7) stores the options used for compilation
18528 into @code{DW_AT_producer} part of DWARF debugging information according
18529 to the @value{NGCC} option @code{-grecord-gcc-switches}. One has to
18530 explicitly specify @code{-g} during inferior compilation otherwise
18531 @value{NGCC} produces no DWARF. This feature is only relevant for
18532 platforms where @code{-g} produces DWARF by default, otherwise one may
18533 try to enforce DWARF by using @code{-gdwarf-4}.
18535 @item compilation options set by @code{set compile-args}
18539 You can override compilation options using the following command:
18542 @item set compile-args
18543 @cindex compile command options override
18544 Set compilation options used for compiling and injecting code with the
18545 @code{compile} commands. These options override any conflicting ones
18546 from the target architecture and/or options stored during inferior
18549 @item show compile-args
18550 Displays the current state of compilation options override.
18551 This does not show all the options actually used during compilation,
18552 use @ref{set debug compile} for that.
18555 @subsection Caveats when using the @code{compile} command
18557 There are a few caveats to keep in mind when using the @code{compile}
18558 command. As the caveats are different per language, the table below
18559 highlights specific issues on a per language basis.
18562 @item C code examples and caveats
18563 When the language in @value{GDBN} is set to @samp{C}, the compiler will
18564 attempt to compile the source code with a @samp{C} compiler. The source
18565 code provided to the @code{compile} command will have much the same
18566 access to variables and types as it normally would if it were part of
18567 the program currently being debugged in @value{GDBN}.
18569 Below is a sample program that forms the basis of the examples that
18570 follow. This program has been compiled and loaded into @value{GDBN},
18571 much like any other normal debugging session.
18574 void function1 (void)
18577 printf ("function 1\n");
18580 void function2 (void)
18595 For the purposes of the examples in this section, the program above has
18596 been compiled, loaded into @value{GDBN}, stopped at the function
18597 @code{main}, and @value{GDBN} is awaiting input from the user.
18599 To access variables and types for any program in @value{GDBN}, the
18600 program must be compiled and packaged with debug information. The
18601 @code{compile} command is not an exception to this rule. Without debug
18602 information, you can still use the @code{compile} command, but you will
18603 be very limited in what variables and types you can access.
18605 So with that in mind, the example above has been compiled with debug
18606 information enabled. The @code{compile} command will have access to
18607 all variables and types (except those that may have been optimized
18608 out). Currently, as @value{GDBN} has stopped the program in the
18609 @code{main} function, the @code{compile} command would have access to
18610 the variable @code{k}. You could invoke the @code{compile} command
18611 and type some source code to set the value of @code{k}. You can also
18612 read it, or do anything with that variable you would normally do in
18613 @code{C}. Be aware that changes to inferior variables in the
18614 @code{compile} command are persistent. In the following example:
18617 compile code k = 3;
18621 the variable @code{k} is now 3. It will retain that value until
18622 something else in the example program changes it, or another
18623 @code{compile} command changes it.
18625 Normal scope and access rules apply to source code compiled and
18626 injected by the @code{compile} command. In the example, the variables
18627 @code{j} and @code{k} are not accessible yet, because the program is
18628 currently stopped in the @code{main} function, where these variables
18629 are not in scope. Therefore, the following command
18632 compile code j = 3;
18636 will result in a compilation error message.
18638 Once the program is continued, execution will bring these variables in
18639 scope, and they will become accessible; then the code you specify via
18640 the @code{compile} command will be able to access them.
18642 You can create variables and types with the @code{compile} command as
18643 part of your source code. Variables and types that are created as part
18644 of the @code{compile} command are not visible to the rest of the program for
18645 the duration of its run. This example is valid:
18648 compile code int ff = 5; printf ("ff is %d\n", ff);
18651 However, if you were to type the following into @value{GDBN} after that
18652 command has completed:
18655 compile code printf ("ff is %d\n'', ff);
18659 a compiler error would be raised as the variable @code{ff} no longer
18660 exists. Object code generated and injected by the @code{compile}
18661 command is removed when its execution ends. Caution is advised
18662 when assigning to program variables values of variables created by the
18663 code submitted to the @code{compile} command. This example is valid:
18666 compile code int ff = 5; k = ff;
18669 The value of the variable @code{ff} is assigned to @code{k}. The variable
18670 @code{k} does not require the existence of @code{ff} to maintain the value
18671 it has been assigned. However, pointers require particular care in
18672 assignment. If the source code compiled with the @code{compile} command
18673 changed the address of a pointer in the example program, perhaps to a
18674 variable created in the @code{compile} command, that pointer would point
18675 to an invalid location when the command exits. The following example
18676 would likely cause issues with your debugged program:
18679 compile code int ff = 5; p = &ff;
18682 In this example, @code{p} would point to @code{ff} when the
18683 @code{compile} command is executing the source code provided to it.
18684 However, as variables in the (example) program persist with their
18685 assigned values, the variable @code{p} would point to an invalid
18686 location when the command exists. A general rule should be followed
18687 in that you should either assign @code{NULL} to any assigned pointers,
18688 or restore a valid location to the pointer before the command exits.
18690 Similar caution must be exercised with any structs, unions, and typedefs
18691 defined in @code{compile} command. Types defined in the @code{compile}
18692 command will no longer be available in the next @code{compile} command.
18693 Therefore, if you cast a variable to a type defined in the
18694 @code{compile} command, care must be taken to ensure that any future
18695 need to resolve the type can be achieved.
18698 (gdb) compile code static struct a @{ int a; @} v = @{ 42 @}; argv = &v;
18699 (gdb) compile code printf ("%d\n", ((struct a *) argv)->a);
18700 gdb command line:1:36: error: dereferencing pointer to incomplete type ‘struct a’
18701 Compilation failed.
18702 (gdb) compile code struct a @{ int a; @}; printf ("%d\n", ((struct a *) argv)->a);
18706 Variables that have been optimized away by the compiler are not
18707 accessible to the code submitted to the @code{compile} command.
18708 Access to those variables will generate a compiler error which @value{GDBN}
18709 will print to the console.
18712 @subsection Compiler search for the @code{compile} command
18714 @value{GDBN} needs to find @value{NGCC} for the inferior being debugged
18715 which may not be obvious for remote targets of different architecture
18716 than where @value{GDBN} is running. Environment variable @code{PATH} on
18717 @value{GDBN} host is searched for @value{NGCC} binary matching the
18718 target architecture and operating system. This search can be overriden
18719 by @code{set compile-gcc} @value{GDBN} command below. @code{PATH} is
18720 taken from shell that executed @value{GDBN}, it is not the value set by
18721 @value{GDBN} command @code{set environment}). @xref{Environment}.
18724 Specifically @code{PATH} is searched for binaries matching regular expression
18725 @code{@var{arch}(-[^-]*)?-@var{os}-gcc} according to the inferior target being
18726 debugged. @var{arch} is processor name --- multiarch is supported, so for
18727 example both @code{i386} and @code{x86_64} targets look for pattern
18728 @code{(x86_64|i.86)} and both @code{s390} and @code{s390x} targets look
18729 for pattern @code{s390x?}. @var{os} is currently supported only for
18730 pattern @code{linux(-gnu)?}.
18732 On Posix hosts the compiler driver @value{GDBN} needs to find also
18733 shared library @file{libcc1.so} from the compiler. It is searched in
18734 default shared library search path (overridable with usual environment
18735 variable @code{LD_LIBRARY_PATH}), unrelated to @code{PATH} or @code{set
18736 compile-gcc} settings. Contrary to it @file{libcc1plugin.so} is found
18737 according to the installation of the found compiler --- as possibly
18738 specified by the @code{set compile-gcc} command.
18741 @item set compile-gcc
18742 @cindex compile command driver filename override
18743 Set compilation command used for compiling and injecting code with the
18744 @code{compile} commands. If this option is not set (it is set to
18745 an empty string), the search described above will occur --- that is the
18748 @item show compile-gcc
18749 Displays the current compile command @value{NGCC} driver filename.
18750 If set, it is the main command @command{gcc}, found usually for example
18751 under name @file{x86_64-linux-gnu-gcc}.
18755 @chapter @value{GDBN} Files
18757 @value{GDBN} needs to know the file name of the program to be debugged,
18758 both in order to read its symbol table and in order to start your
18759 program. To debug a core dump of a previous run, you must also tell
18760 @value{GDBN} the name of the core dump file.
18763 * Files:: Commands to specify files
18764 * File Caching:: Information about @value{GDBN}'s file caching
18765 * Separate Debug Files:: Debugging information in separate files
18766 * MiniDebugInfo:: Debugging information in a special section
18767 * Index Files:: Index files speed up GDB
18768 * Symbol Errors:: Errors reading symbol files
18769 * Data Files:: GDB data files
18773 @section Commands to Specify Files
18775 @cindex symbol table
18776 @cindex core dump file
18778 You may want to specify executable and core dump file names. The usual
18779 way to do this is at start-up time, using the arguments to
18780 @value{GDBN}'s start-up commands (@pxref{Invocation, , Getting In and
18781 Out of @value{GDBN}}).
18783 Occasionally it is necessary to change to a different file during a
18784 @value{GDBN} session. Or you may run @value{GDBN} and forget to
18785 specify a file you want to use. Or you are debugging a remote target
18786 via @code{gdbserver} (@pxref{Server, file, Using the @code{gdbserver}
18787 Program}). In these situations the @value{GDBN} commands to specify
18788 new files are useful.
18791 @cindex executable file
18793 @item file @var{filename}
18794 Use @var{filename} as the program to be debugged. It is read for its
18795 symbols and for the contents of pure memory. It is also the program
18796 executed when you use the @code{run} command. If you do not specify a
18797 directory and the file is not found in the @value{GDBN} working directory,
18798 @value{GDBN} uses the environment variable @code{PATH} as a list of
18799 directories to search, just as the shell does when looking for a program
18800 to run. You can change the value of this variable, for both @value{GDBN}
18801 and your program, using the @code{path} command.
18803 @cindex unlinked object files
18804 @cindex patching object files
18805 You can load unlinked object @file{.o} files into @value{GDBN} using
18806 the @code{file} command. You will not be able to ``run'' an object
18807 file, but you can disassemble functions and inspect variables. Also,
18808 if the underlying BFD functionality supports it, you could use
18809 @kbd{gdb -write} to patch object files using this technique. Note
18810 that @value{GDBN} can neither interpret nor modify relocations in this
18811 case, so branches and some initialized variables will appear to go to
18812 the wrong place. But this feature is still handy from time to time.
18815 @code{file} with no argument makes @value{GDBN} discard any information it
18816 has on both executable file and the symbol table.
18819 @item exec-file @r{[} @var{filename} @r{]}
18820 Specify that the program to be run (but not the symbol table) is found
18821 in @var{filename}. @value{GDBN} searches the environment variable @code{PATH}
18822 if necessary to locate your program. Omitting @var{filename} means to
18823 discard information on the executable file.
18825 @kindex symbol-file
18826 @item symbol-file @r{[} @var{filename} @r{[} -o @var{offset} @r{]]}
18827 Read symbol table information from file @var{filename}. @code{PATH} is
18828 searched when necessary. Use the @code{file} command to get both symbol
18829 table and program to run from the same file.
18831 If an optional @var{offset} is specified, it is added to the start
18832 address of each section in the symbol file. This is useful if the
18833 program is relocated at runtime, such as the Linux kernel with kASLR
18836 @code{symbol-file} with no argument clears out @value{GDBN} information on your
18837 program's symbol table.
18839 The @code{symbol-file} command causes @value{GDBN} to forget the contents of
18840 some breakpoints and auto-display expressions. This is because they may
18841 contain pointers to the internal data recording symbols and data types,
18842 which are part of the old symbol table data being discarded inside
18845 @code{symbol-file} does not repeat if you press @key{RET} again after
18848 When @value{GDBN} is configured for a particular environment, it
18849 understands debugging information in whatever format is the standard
18850 generated for that environment; you may use either a @sc{gnu} compiler, or
18851 other compilers that adhere to the local conventions.
18852 Best results are usually obtained from @sc{gnu} compilers; for example,
18853 using @code{@value{NGCC}} you can generate debugging information for
18856 For most kinds of object files, with the exception of old SVR3 systems
18857 using COFF, the @code{symbol-file} command does not normally read the
18858 symbol table in full right away. Instead, it scans the symbol table
18859 quickly to find which source files and which symbols are present. The
18860 details are read later, one source file at a time, as they are needed.
18862 The purpose of this two-stage reading strategy is to make @value{GDBN}
18863 start up faster. For the most part, it is invisible except for
18864 occasional pauses while the symbol table details for a particular source
18865 file are being read. (The @code{set verbose} command can turn these
18866 pauses into messages if desired. @xref{Messages/Warnings, ,Optional
18867 Warnings and Messages}.)
18869 We have not implemented the two-stage strategy for COFF yet. When the
18870 symbol table is stored in COFF format, @code{symbol-file} reads the
18871 symbol table data in full right away. Note that ``stabs-in-COFF''
18872 still does the two-stage strategy, since the debug info is actually
18876 @cindex reading symbols immediately
18877 @cindex symbols, reading immediately
18878 @item symbol-file @r{[} -readnow @r{]} @var{filename}
18879 @itemx file @r{[} -readnow @r{]} @var{filename}
18880 You can override the @value{GDBN} two-stage strategy for reading symbol
18881 tables by using the @samp{-readnow} option with any of the commands that
18882 load symbol table information, if you want to be sure @value{GDBN} has the
18883 entire symbol table available.
18885 @cindex @code{-readnever}, option for symbol-file command
18886 @cindex never read symbols
18887 @cindex symbols, never read
18888 @item symbol-file @r{[} -readnever @r{]} @var{filename}
18889 @itemx file @r{[} -readnever @r{]} @var{filename}
18890 You can instruct @value{GDBN} to never read the symbolic information
18891 contained in @var{filename} by using the @samp{-readnever} option.
18892 @xref{--readnever}.
18894 @c FIXME: for now no mention of directories, since this seems to be in
18895 @c flux. 13mar1992 status is that in theory GDB would look either in
18896 @c current dir or in same dir as myprog; but issues like competing
18897 @c GDB's, or clutter in system dirs, mean that in practice right now
18898 @c only current dir is used. FFish says maybe a special GDB hierarchy
18899 @c (eg rooted in val of env var GDBSYMS) could exist for mappable symbol
18903 @item core-file @r{[}@var{filename}@r{]}
18905 Specify the whereabouts of a core dump file to be used as the ``contents
18906 of memory''. Traditionally, core files contain only some parts of the
18907 address space of the process that generated them; @value{GDBN} can access the
18908 executable file itself for other parts.
18910 @code{core-file} with no argument specifies that no core file is
18913 Note that the core file is ignored when your program is actually running
18914 under @value{GDBN}. So, if you have been running your program and you
18915 wish to debug a core file instead, you must kill the subprocess in which
18916 the program is running. To do this, use the @code{kill} command
18917 (@pxref{Kill Process, ,Killing the Child Process}).
18919 @kindex add-symbol-file
18920 @cindex dynamic linking
18921 @item add-symbol-file @var{filename} @r{[} -readnow @r{|} -readnever @r{]} @r{[} @var{textaddress} @r{]} @r{[} -s @var{section} @var{address} @dots{} @r{]}
18922 The @code{add-symbol-file} command reads additional symbol table
18923 information from the file @var{filename}. You would use this command
18924 when @var{filename} has been dynamically loaded (by some other means)
18925 into the program that is running. The @var{textaddress} parameter gives
18926 the memory address at which the file's text section has been loaded.
18927 You can additionally specify the base address of other sections using
18928 an arbitrary number of @samp{-s @var{section} @var{address}} pairs.
18929 If a section is omitted, @value{GDBN} will use its default addresses
18930 as found in @var{filename}. Any @var{address} or @var{textaddress}
18931 can be given as an expression.
18933 The symbol table of the file @var{filename} is added to the symbol table
18934 originally read with the @code{symbol-file} command. You can use the
18935 @code{add-symbol-file} command any number of times; the new symbol data
18936 thus read is kept in addition to the old.
18938 Changes can be reverted using the command @code{remove-symbol-file}.
18940 @cindex relocatable object files, reading symbols from
18941 @cindex object files, relocatable, reading symbols from
18942 @cindex reading symbols from relocatable object files
18943 @cindex symbols, reading from relocatable object files
18944 @cindex @file{.o} files, reading symbols from
18945 Although @var{filename} is typically a shared library file, an
18946 executable file, or some other object file which has been fully
18947 relocated for loading into a process, you can also load symbolic
18948 information from relocatable @file{.o} files, as long as:
18952 the file's symbolic information refers only to linker symbols defined in
18953 that file, not to symbols defined by other object files,
18955 every section the file's symbolic information refers to has actually
18956 been loaded into the inferior, as it appears in the file, and
18958 you can determine the address at which every section was loaded, and
18959 provide these to the @code{add-symbol-file} command.
18963 Some embedded operating systems, like Sun Chorus and VxWorks, can load
18964 relocatable files into an already running program; such systems
18965 typically make the requirements above easy to meet. However, it's
18966 important to recognize that many native systems use complex link
18967 procedures (@code{.linkonce} section factoring and C@t{++} constructor table
18968 assembly, for example) that make the requirements difficult to meet. In
18969 general, one cannot assume that using @code{add-symbol-file} to read a
18970 relocatable object file's symbolic information will have the same effect
18971 as linking the relocatable object file into the program in the normal
18974 @code{add-symbol-file} does not repeat if you press @key{RET} after using it.
18976 @kindex remove-symbol-file
18977 @item remove-symbol-file @var{filename}
18978 @item remove-symbol-file -a @var{address}
18979 Remove a symbol file added via the @code{add-symbol-file} command. The
18980 file to remove can be identified by its @var{filename} or by an @var{address}
18981 that lies within the boundaries of this symbol file in memory. Example:
18984 (gdb) add-symbol-file /home/user/gdb/mylib.so 0x7ffff7ff9480
18985 add symbol table from file "/home/user/gdb/mylib.so" at
18986 .text_addr = 0x7ffff7ff9480
18988 Reading symbols from /home/user/gdb/mylib.so...done.
18989 (gdb) remove-symbol-file -a 0x7ffff7ff9480
18990 Remove symbol table from file "/home/user/gdb/mylib.so"? (y or n) y
18995 @code{remove-symbol-file} does not repeat if you press @key{RET} after using it.
18997 @kindex add-symbol-file-from-memory
18998 @cindex @code{syscall DSO}
18999 @cindex load symbols from memory
19000 @item add-symbol-file-from-memory @var{address}
19001 Load symbols from the given @var{address} in a dynamically loaded
19002 object file whose image is mapped directly into the inferior's memory.
19003 For example, the Linux kernel maps a @code{syscall DSO} into each
19004 process's address space; this DSO provides kernel-specific code for
19005 some system calls. The argument can be any expression whose
19006 evaluation yields the address of the file's shared object file header.
19007 For this command to work, you must have used @code{symbol-file} or
19008 @code{exec-file} commands in advance.
19011 @item section @var{section} @var{addr}
19012 The @code{section} command changes the base address of the named
19013 @var{section} of the exec file to @var{addr}. This can be used if the
19014 exec file does not contain section addresses, (such as in the
19015 @code{a.out} format), or when the addresses specified in the file
19016 itself are wrong. Each section must be changed separately. The
19017 @code{info files} command, described below, lists all the sections and
19021 @kindex info target
19024 @code{info files} and @code{info target} are synonymous; both print the
19025 current target (@pxref{Targets, ,Specifying a Debugging Target}),
19026 including the names of the executable and core dump files currently in
19027 use by @value{GDBN}, and the files from which symbols were loaded. The
19028 command @code{help target} lists all possible targets rather than
19031 @kindex maint info sections
19032 @item maint info sections
19033 Another command that can give you extra information about program sections
19034 is @code{maint info sections}. In addition to the section information
19035 displayed by @code{info files}, this command displays the flags and file
19036 offset of each section in the executable and core dump files. In addition,
19037 @code{maint info sections} provides the following command options (which
19038 may be arbitrarily combined):
19042 Display sections for all loaded object files, including shared libraries.
19043 @item @var{sections}
19044 Display info only for named @var{sections}.
19045 @item @var{section-flags}
19046 Display info only for sections for which @var{section-flags} are true.
19047 The section flags that @value{GDBN} currently knows about are:
19050 Section will have space allocated in the process when loaded.
19051 Set for all sections except those containing debug information.
19053 Section will be loaded from the file into the child process memory.
19054 Set for pre-initialized code and data, clear for @code{.bss} sections.
19056 Section needs to be relocated before loading.
19058 Section cannot be modified by the child process.
19060 Section contains executable code only.
19062 Section contains data only (no executable code).
19064 Section will reside in ROM.
19066 Section contains data for constructor/destructor lists.
19068 Section is not empty.
19070 An instruction to the linker to not output the section.
19071 @item COFF_SHARED_LIBRARY
19072 A notification to the linker that the section contains
19073 COFF shared library information.
19075 Section contains common symbols.
19078 @kindex set trust-readonly-sections
19079 @cindex read-only sections
19080 @item set trust-readonly-sections on
19081 Tell @value{GDBN} that readonly sections in your object file
19082 really are read-only (i.e.@: that their contents will not change).
19083 In that case, @value{GDBN} can fetch values from these sections
19084 out of the object file, rather than from the target program.
19085 For some targets (notably embedded ones), this can be a significant
19086 enhancement to debugging performance.
19088 The default is off.
19090 @item set trust-readonly-sections off
19091 Tell @value{GDBN} not to trust readonly sections. This means that
19092 the contents of the section might change while the program is running,
19093 and must therefore be fetched from the target when needed.
19095 @item show trust-readonly-sections
19096 Show the current setting of trusting readonly sections.
19099 All file-specifying commands allow both absolute and relative file names
19100 as arguments. @value{GDBN} always converts the file name to an absolute file
19101 name and remembers it that way.
19103 @cindex shared libraries
19104 @anchor{Shared Libraries}
19105 @value{GDBN} supports @sc{gnu}/Linux, MS-Windows, SunOS,
19106 Darwin/Mach-O, SVr4, IBM RS/6000 AIX, QNX Neutrino, FDPIC (FR-V), and
19107 DSBT (TIC6X) shared libraries.
19109 On MS-Windows @value{GDBN} must be linked with the Expat library to support
19110 shared libraries. @xref{Expat}.
19112 @value{GDBN} automatically loads symbol definitions from shared libraries
19113 when you use the @code{run} command, or when you examine a core file.
19114 (Before you issue the @code{run} command, @value{GDBN} does not understand
19115 references to a function in a shared library, however---unless you are
19116 debugging a core file).
19118 @c FIXME: some @value{GDBN} release may permit some refs to undef
19119 @c FIXME...symbols---eg in a break cmd---assuming they are from a shared
19120 @c FIXME...lib; check this from time to time when updating manual
19122 There are times, however, when you may wish to not automatically load
19123 symbol definitions from shared libraries, such as when they are
19124 particularly large or there are many of them.
19126 To control the automatic loading of shared library symbols, use the
19130 @kindex set auto-solib-add
19131 @item set auto-solib-add @var{mode}
19132 If @var{mode} is @code{on}, symbols from all shared object libraries
19133 will be loaded automatically when the inferior begins execution, you
19134 attach to an independently started inferior, or when the dynamic linker
19135 informs @value{GDBN} that a new library has been loaded. If @var{mode}
19136 is @code{off}, symbols must be loaded manually, using the
19137 @code{sharedlibrary} command. The default value is @code{on}.
19139 @cindex memory used for symbol tables
19140 If your program uses lots of shared libraries with debug info that
19141 takes large amounts of memory, you can decrease the @value{GDBN}
19142 memory footprint by preventing it from automatically loading the
19143 symbols from shared libraries. To that end, type @kbd{set
19144 auto-solib-add off} before running the inferior, then load each
19145 library whose debug symbols you do need with @kbd{sharedlibrary
19146 @var{regexp}}, where @var{regexp} is a regular expression that matches
19147 the libraries whose symbols you want to be loaded.
19149 @kindex show auto-solib-add
19150 @item show auto-solib-add
19151 Display the current autoloading mode.
19154 @cindex load shared library
19155 To explicitly load shared library symbols, use the @code{sharedlibrary}
19159 @kindex info sharedlibrary
19161 @item info share @var{regex}
19162 @itemx info sharedlibrary @var{regex}
19163 Print the names of the shared libraries which are currently loaded
19164 that match @var{regex}. If @var{regex} is omitted then print
19165 all shared libraries that are loaded.
19168 @item info dll @var{regex}
19169 This is an alias of @code{info sharedlibrary}.
19171 @kindex sharedlibrary
19173 @item sharedlibrary @var{regex}
19174 @itemx share @var{regex}
19175 Load shared object library symbols for files matching a
19176 Unix regular expression.
19177 As with files loaded automatically, it only loads shared libraries
19178 required by your program for a core file or after typing @code{run}. If
19179 @var{regex} is omitted all shared libraries required by your program are
19182 @item nosharedlibrary
19183 @kindex nosharedlibrary
19184 @cindex unload symbols from shared libraries
19185 Unload all shared object library symbols. This discards all symbols
19186 that have been loaded from all shared libraries. Symbols from shared
19187 libraries that were loaded by explicit user requests are not
19191 Sometimes you may wish that @value{GDBN} stops and gives you control
19192 when any of shared library events happen. The best way to do this is
19193 to use @code{catch load} and @code{catch unload} (@pxref{Set
19196 @value{GDBN} also supports the the @code{set stop-on-solib-events}
19197 command for this. This command exists for historical reasons. It is
19198 less useful than setting a catchpoint, because it does not allow for
19199 conditions or commands as a catchpoint does.
19202 @item set stop-on-solib-events
19203 @kindex set stop-on-solib-events
19204 This command controls whether @value{GDBN} should give you control
19205 when the dynamic linker notifies it about some shared library event.
19206 The most common event of interest is loading or unloading of a new
19209 @item show stop-on-solib-events
19210 @kindex show stop-on-solib-events
19211 Show whether @value{GDBN} stops and gives you control when shared
19212 library events happen.
19215 Shared libraries are also supported in many cross or remote debugging
19216 configurations. @value{GDBN} needs to have access to the target's libraries;
19217 this can be accomplished either by providing copies of the libraries
19218 on the host system, or by asking @value{GDBN} to automatically retrieve the
19219 libraries from the target. If copies of the target libraries are
19220 provided, they need to be the same as the target libraries, although the
19221 copies on the target can be stripped as long as the copies on the host are
19224 @cindex where to look for shared libraries
19225 For remote debugging, you need to tell @value{GDBN} where the target
19226 libraries are, so that it can load the correct copies---otherwise, it
19227 may try to load the host's libraries. @value{GDBN} has two variables
19228 to specify the search directories for target libraries.
19231 @cindex prefix for executable and shared library file names
19232 @cindex system root, alternate
19233 @kindex set solib-absolute-prefix
19234 @kindex set sysroot
19235 @item set sysroot @var{path}
19236 Use @var{path} as the system root for the program being debugged. Any
19237 absolute shared library paths will be prefixed with @var{path}; many
19238 runtime loaders store the absolute paths to the shared library in the
19239 target program's memory. When starting processes remotely, and when
19240 attaching to already-running processes (local or remote), their
19241 executable filenames will be prefixed with @var{path} if reported to
19242 @value{GDBN} as absolute by the operating system. If you use
19243 @code{set sysroot} to find executables and shared libraries, they need
19244 to be laid out in the same way that they are on the target, with
19245 e.g.@: a @file{/bin}, @file{/lib} and @file{/usr/lib} hierarchy under
19248 If @var{path} starts with the sequence @file{target:} and the target
19249 system is remote then @value{GDBN} will retrieve the target binaries
19250 from the remote system. This is only supported when using a remote
19251 target that supports the @code{remote get} command (@pxref{File
19252 Transfer,,Sending files to a remote system}). The part of @var{path}
19253 following the initial @file{target:} (if present) is used as system
19254 root prefix on the remote file system. If @var{path} starts with the
19255 sequence @file{remote:} this is converted to the sequence
19256 @file{target:} by @code{set sysroot}@footnote{Historically the
19257 functionality to retrieve binaries from the remote system was
19258 provided by prefixing @var{path} with @file{remote:}}. If you want
19259 to specify a local system root using a directory that happens to be
19260 named @file{target:} or @file{remote:}, you need to use some
19261 equivalent variant of the name like @file{./target:}.
19263 For targets with an MS-DOS based filesystem, such as MS-Windows and
19264 SymbianOS, @value{GDBN} tries prefixing a few variants of the target
19265 absolute file name with @var{path}. But first, on Unix hosts,
19266 @value{GDBN} converts all backslash directory separators into forward
19267 slashes, because the backslash is not a directory separator on Unix:
19270 c:\foo\bar.dll @result{} c:/foo/bar.dll
19273 Then, @value{GDBN} attempts prefixing the target file name with
19274 @var{path}, and looks for the resulting file name in the host file
19278 c:/foo/bar.dll @result{} /path/to/sysroot/c:/foo/bar.dll
19281 If that does not find the binary, @value{GDBN} tries removing
19282 the @samp{:} character from the drive spec, both for convenience, and,
19283 for the case of the host file system not supporting file names with
19287 c:/foo/bar.dll @result{} /path/to/sysroot/c/foo/bar.dll
19290 This makes it possible to have a system root that mirrors a target
19291 with more than one drive. E.g., you may want to setup your local
19292 copies of the target system shared libraries like so (note @samp{c} vs
19296 @file{/path/to/sysroot/c/sys/bin/foo.dll}
19297 @file{/path/to/sysroot/c/sys/bin/bar.dll}
19298 @file{/path/to/sysroot/z/sys/bin/bar.dll}
19302 and point the system root at @file{/path/to/sysroot}, so that
19303 @value{GDBN} can find the correct copies of both
19304 @file{c:\sys\bin\foo.dll}, and @file{z:\sys\bin\bar.dll}.
19306 If that still does not find the binary, @value{GDBN} tries
19307 removing the whole drive spec from the target file name:
19310 c:/foo/bar.dll @result{} /path/to/sysroot/foo/bar.dll
19313 This last lookup makes it possible to not care about the drive name,
19314 if you don't want or need to.
19316 The @code{set solib-absolute-prefix} command is an alias for @code{set
19319 @cindex default system root
19320 @cindex @samp{--with-sysroot}
19321 You can set the default system root by using the configure-time
19322 @samp{--with-sysroot} option. If the system root is inside
19323 @value{GDBN}'s configured binary prefix (set with @samp{--prefix} or
19324 @samp{--exec-prefix}), then the default system root will be updated
19325 automatically if the installed @value{GDBN} is moved to a new
19328 @kindex show sysroot
19330 Display the current executable and shared library prefix.
19332 @kindex set solib-search-path
19333 @item set solib-search-path @var{path}
19334 If this variable is set, @var{path} is a colon-separated list of
19335 directories to search for shared libraries. @samp{solib-search-path}
19336 is used after @samp{sysroot} fails to locate the library, or if the
19337 path to the library is relative instead of absolute. If you want to
19338 use @samp{solib-search-path} instead of @samp{sysroot}, be sure to set
19339 @samp{sysroot} to a nonexistent directory to prevent @value{GDBN} from
19340 finding your host's libraries. @samp{sysroot} is preferred; setting
19341 it to a nonexistent directory may interfere with automatic loading
19342 of shared library symbols.
19344 @kindex show solib-search-path
19345 @item show solib-search-path
19346 Display the current shared library search path.
19348 @cindex DOS file-name semantics of file names.
19349 @kindex set target-file-system-kind (unix|dos-based|auto)
19350 @kindex show target-file-system-kind
19351 @item set target-file-system-kind @var{kind}
19352 Set assumed file system kind for target reported file names.
19354 Shared library file names as reported by the target system may not
19355 make sense as is on the system @value{GDBN} is running on. For
19356 example, when remote debugging a target that has MS-DOS based file
19357 system semantics, from a Unix host, the target may be reporting to
19358 @value{GDBN} a list of loaded shared libraries with file names such as
19359 @file{c:\Windows\kernel32.dll}. On Unix hosts, there's no concept of
19360 drive letters, so the @samp{c:\} prefix is not normally understood as
19361 indicating an absolute file name, and neither is the backslash
19362 normally considered a directory separator character. In that case,
19363 the native file system would interpret this whole absolute file name
19364 as a relative file name with no directory components. This would make
19365 it impossible to point @value{GDBN} at a copy of the remote target's
19366 shared libraries on the host using @code{set sysroot}, and impractical
19367 with @code{set solib-search-path}. Setting
19368 @code{target-file-system-kind} to @code{dos-based} tells @value{GDBN}
19369 to interpret such file names similarly to how the target would, and to
19370 map them to file names valid on @value{GDBN}'s native file system
19371 semantics. The value of @var{kind} can be @code{"auto"}, in addition
19372 to one of the supported file system kinds. In that case, @value{GDBN}
19373 tries to determine the appropriate file system variant based on the
19374 current target's operating system (@pxref{ABI, ,Configuring the
19375 Current ABI}). The supported file system settings are:
19379 Instruct @value{GDBN} to assume the target file system is of Unix
19380 kind. Only file names starting the forward slash (@samp{/}) character
19381 are considered absolute, and the directory separator character is also
19385 Instruct @value{GDBN} to assume the target file system is DOS based.
19386 File names starting with either a forward slash, or a drive letter
19387 followed by a colon (e.g., @samp{c:}), are considered absolute, and
19388 both the slash (@samp{/}) and the backslash (@samp{\\}) characters are
19389 considered directory separators.
19392 Instruct @value{GDBN} to use the file system kind associated with the
19393 target operating system (@pxref{ABI, ,Configuring the Current ABI}).
19394 This is the default.
19398 @cindex file name canonicalization
19399 @cindex base name differences
19400 When processing file names provided by the user, @value{GDBN}
19401 frequently needs to compare them to the file names recorded in the
19402 program's debug info. Normally, @value{GDBN} compares just the
19403 @dfn{base names} of the files as strings, which is reasonably fast
19404 even for very large programs. (The base name of a file is the last
19405 portion of its name, after stripping all the leading directories.)
19406 This shortcut in comparison is based upon the assumption that files
19407 cannot have more than one base name. This is usually true, but
19408 references to files that use symlinks or similar filesystem
19409 facilities violate that assumption. If your program records files
19410 using such facilities, or if you provide file names to @value{GDBN}
19411 using symlinks etc., you can set @code{basenames-may-differ} to
19412 @code{true} to instruct @value{GDBN} to completely canonicalize each
19413 pair of file names it needs to compare. This will make file-name
19414 comparisons accurate, but at a price of a significant slowdown.
19417 @item set basenames-may-differ
19418 @kindex set basenames-may-differ
19419 Set whether a source file may have multiple base names.
19421 @item show basenames-may-differ
19422 @kindex show basenames-may-differ
19423 Show whether a source file may have multiple base names.
19427 @section File Caching
19428 @cindex caching of opened files
19429 @cindex caching of bfd objects
19431 To speed up file loading, and reduce memory usage, @value{GDBN} will
19432 reuse the @code{bfd} objects used to track open files. @xref{Top, ,
19433 BFD, bfd, The Binary File Descriptor Library}. The following commands
19434 allow visibility and control of the caching behavior.
19437 @kindex maint info bfds
19438 @item maint info bfds
19439 This prints information about each @code{bfd} object that is known to
19442 @kindex maint set bfd-sharing
19443 @kindex maint show bfd-sharing
19444 @kindex bfd caching
19445 @item maint set bfd-sharing
19446 @item maint show bfd-sharing
19447 Control whether @code{bfd} objects can be shared. When sharing is
19448 enabled @value{GDBN} reuses already open @code{bfd} objects rather
19449 than reopening the same file. Turning sharing off does not cause
19450 already shared @code{bfd} objects to be unshared, but all future files
19451 that are opened will create a new @code{bfd} object. Similarly,
19452 re-enabling sharing does not cause multiple existing @code{bfd}
19453 objects to be collapsed into a single shared @code{bfd} object.
19455 @kindex set debug bfd-cache @var{level}
19456 @kindex bfd caching
19457 @item set debug bfd-cache @var{level}
19458 Turns on debugging of the bfd cache, setting the level to @var{level}.
19460 @kindex show debug bfd-cache
19461 @kindex bfd caching
19462 @item show debug bfd-cache
19463 Show the current debugging level of the bfd cache.
19466 @node Separate Debug Files
19467 @section Debugging Information in Separate Files
19468 @cindex separate debugging information files
19469 @cindex debugging information in separate files
19470 @cindex @file{.debug} subdirectories
19471 @cindex debugging information directory, global
19472 @cindex global debugging information directories
19473 @cindex build ID, and separate debugging files
19474 @cindex @file{.build-id} directory
19476 @value{GDBN} allows you to put a program's debugging information in a
19477 file separate from the executable itself, in a way that allows
19478 @value{GDBN} to find and load the debugging information automatically.
19479 Since debugging information can be very large---sometimes larger
19480 than the executable code itself---some systems distribute debugging
19481 information for their executables in separate files, which users can
19482 install only when they need to debug a problem.
19484 @value{GDBN} supports two ways of specifying the separate debug info
19489 The executable contains a @dfn{debug link} that specifies the name of
19490 the separate debug info file. The separate debug file's name is
19491 usually @file{@var{executable}.debug}, where @var{executable} is the
19492 name of the corresponding executable file without leading directories
19493 (e.g., @file{ls.debug} for @file{/usr/bin/ls}). In addition, the
19494 debug link specifies a 32-bit @dfn{Cyclic Redundancy Check} (CRC)
19495 checksum for the debug file, which @value{GDBN} uses to validate that
19496 the executable and the debug file came from the same build.
19499 The executable contains a @dfn{build ID}, a unique bit string that is
19500 also present in the corresponding debug info file. (This is supported
19501 only on some operating systems, when using the ELF or PE file formats
19502 for binary files and the @sc{gnu} Binutils.) For more details about
19503 this feature, see the description of the @option{--build-id}
19504 command-line option in @ref{Options, , Command Line Options, ld.info,
19505 The GNU Linker}. The debug info file's name is not specified
19506 explicitly by the build ID, but can be computed from the build ID, see
19510 Depending on the way the debug info file is specified, @value{GDBN}
19511 uses two different methods of looking for the debug file:
19515 For the ``debug link'' method, @value{GDBN} looks up the named file in
19516 the directory of the executable file, then in a subdirectory of that
19517 directory named @file{.debug}, and finally under each one of the global debug
19518 directories, in a subdirectory whose name is identical to the leading
19519 directories of the executable's absolute file name.
19522 For the ``build ID'' method, @value{GDBN} looks in the
19523 @file{.build-id} subdirectory of each one of the global debug directories for
19524 a file named @file{@var{nn}/@var{nnnnnnnn}.debug}, where @var{nn} are the
19525 first 2 hex characters of the build ID bit string, and @var{nnnnnnnn}
19526 are the rest of the bit string. (Real build ID strings are 32 or more
19527 hex characters, not 10.)
19530 So, for example, suppose you ask @value{GDBN} to debug
19531 @file{/usr/bin/ls}, which has a debug link that specifies the
19532 file @file{ls.debug}, and a build ID whose value in hex is
19533 @code{abcdef1234}. If the list of the global debug directories includes
19534 @file{/usr/lib/debug}, then @value{GDBN} will look for the following
19535 debug information files, in the indicated order:
19539 @file{/usr/lib/debug/.build-id/ab/cdef1234.debug}
19541 @file{/usr/bin/ls.debug}
19543 @file{/usr/bin/.debug/ls.debug}
19545 @file{/usr/lib/debug/usr/bin/ls.debug}.
19548 @anchor{debug-file-directory}
19549 Global debugging info directories default to what is set by @value{GDBN}
19550 configure option @option{--with-separate-debug-dir}. During @value{GDBN} run
19551 you can also set the global debugging info directories, and view the list
19552 @value{GDBN} is currently using.
19556 @kindex set debug-file-directory
19557 @item set debug-file-directory @var{directories}
19558 Set the directories which @value{GDBN} searches for separate debugging
19559 information files to @var{directory}. Multiple path components can be set
19560 concatenating them by a path separator.
19562 @kindex show debug-file-directory
19563 @item show debug-file-directory
19564 Show the directories @value{GDBN} searches for separate debugging
19569 @cindex @code{.gnu_debuglink} sections
19570 @cindex debug link sections
19571 A debug link is a special section of the executable file named
19572 @code{.gnu_debuglink}. The section must contain:
19576 A filename, with any leading directory components removed, followed by
19579 zero to three bytes of padding, as needed to reach the next four-byte
19580 boundary within the section, and
19582 a four-byte CRC checksum, stored in the same endianness used for the
19583 executable file itself. The checksum is computed on the debugging
19584 information file's full contents by the function given below, passing
19585 zero as the @var{crc} argument.
19588 Any executable file format can carry a debug link, as long as it can
19589 contain a section named @code{.gnu_debuglink} with the contents
19592 @cindex @code{.note.gnu.build-id} sections
19593 @cindex build ID sections
19594 The build ID is a special section in the executable file (and in other
19595 ELF binary files that @value{GDBN} may consider). This section is
19596 often named @code{.note.gnu.build-id}, but that name is not mandatory.
19597 It contains unique identification for the built files---the ID remains
19598 the same across multiple builds of the same build tree. The default
19599 algorithm SHA1 produces 160 bits (40 hexadecimal characters) of the
19600 content for the build ID string. The same section with an identical
19601 value is present in the original built binary with symbols, in its
19602 stripped variant, and in the separate debugging information file.
19604 The debugging information file itself should be an ordinary
19605 executable, containing a full set of linker symbols, sections, and
19606 debugging information. The sections of the debugging information file
19607 should have the same names, addresses, and sizes as the original file,
19608 but they need not contain any data---much like a @code{.bss} section
19609 in an ordinary executable.
19611 The @sc{gnu} binary utilities (Binutils) package includes the
19612 @samp{objcopy} utility that can produce
19613 the separated executable / debugging information file pairs using the
19614 following commands:
19617 @kbd{objcopy --only-keep-debug foo foo.debug}
19622 These commands remove the debugging
19623 information from the executable file @file{foo} and place it in the file
19624 @file{foo.debug}. You can use the first, second or both methods to link the
19629 The debug link method needs the following additional command to also leave
19630 behind a debug link in @file{foo}:
19633 @kbd{objcopy --add-gnu-debuglink=foo.debug foo}
19636 Ulrich Drepper's @file{elfutils} package, starting with version 0.53, contains
19637 a version of the @code{strip} command such that the command @kbd{strip foo -f
19638 foo.debug} has the same functionality as the two @code{objcopy} commands and
19639 the @code{ln -s} command above, together.
19642 Build ID gets embedded into the main executable using @code{ld --build-id} or
19643 the @value{NGCC} counterpart @code{gcc -Wl,--build-id}. Build ID support plus
19644 compatibility fixes for debug files separation are present in @sc{gnu} binary
19645 utilities (Binutils) package since version 2.18.
19650 @cindex CRC algorithm definition
19651 The CRC used in @code{.gnu_debuglink} is the CRC-32 defined in
19652 IEEE 802.3 using the polynomial:
19654 @c TexInfo requires naked braces for multi-digit exponents for Tex
19655 @c output, but this causes HTML output to barf. HTML has to be set using
19656 @c raw commands. So we end up having to specify this equation in 2
19661 <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>
19662 + <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
19668 @math{x^{32} + x^{26} + x^{23} + x^{22} + x^{16} + x^{12} + x^{11}}
19669 @math{+ x^{10} + x^8 + x^7 + x^5 + x^4 + x^2 + x + 1}
19673 The function is computed byte at a time, taking the least
19674 significant bit of each byte first. The initial pattern
19675 @code{0xffffffff} is used, to ensure leading zeros affect the CRC and
19676 the final result is inverted to ensure trailing zeros also affect the
19679 @emph{Note:} This is the same CRC polynomial as used in handling the
19680 @dfn{Remote Serial Protocol} @code{qCRC} packet (@pxref{qCRC packet}).
19681 However in the case of the Remote Serial Protocol, the CRC is computed
19682 @emph{most} significant bit first, and the result is not inverted, so
19683 trailing zeros have no effect on the CRC value.
19685 To complete the description, we show below the code of the function
19686 which produces the CRC used in @code{.gnu_debuglink}. Inverting the
19687 initially supplied @code{crc} argument means that an initial call to
19688 this function passing in zero will start computing the CRC using
19691 @kindex gnu_debuglink_crc32
19694 gnu_debuglink_crc32 (unsigned long crc,
19695 unsigned char *buf, size_t len)
19697 static const unsigned long crc32_table[256] =
19699 0x00000000, 0x77073096, 0xee0e612c, 0x990951ba, 0x076dc419,
19700 0x706af48f, 0xe963a535, 0x9e6495a3, 0x0edb8832, 0x79dcb8a4,
19701 0xe0d5e91e, 0x97d2d988, 0x09b64c2b, 0x7eb17cbd, 0xe7b82d07,
19702 0x90bf1d91, 0x1db71064, 0x6ab020f2, 0xf3b97148, 0x84be41de,
19703 0x1adad47d, 0x6ddde4eb, 0xf4d4b551, 0x83d385c7, 0x136c9856,
19704 0x646ba8c0, 0xfd62f97a, 0x8a65c9ec, 0x14015c4f, 0x63066cd9,
19705 0xfa0f3d63, 0x8d080df5, 0x3b6e20c8, 0x4c69105e, 0xd56041e4,
19706 0xa2677172, 0x3c03e4d1, 0x4b04d447, 0xd20d85fd, 0xa50ab56b,
19707 0x35b5a8fa, 0x42b2986c, 0xdbbbc9d6, 0xacbcf940, 0x32d86ce3,
19708 0x45df5c75, 0xdcd60dcf, 0xabd13d59, 0x26d930ac, 0x51de003a,
19709 0xc8d75180, 0xbfd06116, 0x21b4f4b5, 0x56b3c423, 0xcfba9599,
19710 0xb8bda50f, 0x2802b89e, 0x5f058808, 0xc60cd9b2, 0xb10be924,
19711 0x2f6f7c87, 0x58684c11, 0xc1611dab, 0xb6662d3d, 0x76dc4190,
19712 0x01db7106, 0x98d220bc, 0xefd5102a, 0x71b18589, 0x06b6b51f,
19713 0x9fbfe4a5, 0xe8b8d433, 0x7807c9a2, 0x0f00f934, 0x9609a88e,
19714 0xe10e9818, 0x7f6a0dbb, 0x086d3d2d, 0x91646c97, 0xe6635c01,
19715 0x6b6b51f4, 0x1c6c6162, 0x856530d8, 0xf262004e, 0x6c0695ed,
19716 0x1b01a57b, 0x8208f4c1, 0xf50fc457, 0x65b0d9c6, 0x12b7e950,
19717 0x8bbeb8ea, 0xfcb9887c, 0x62dd1ddf, 0x15da2d49, 0x8cd37cf3,
19718 0xfbd44c65, 0x4db26158, 0x3ab551ce, 0xa3bc0074, 0xd4bb30e2,
19719 0x4adfa541, 0x3dd895d7, 0xa4d1c46d, 0xd3d6f4fb, 0x4369e96a,
19720 0x346ed9fc, 0xad678846, 0xda60b8d0, 0x44042d73, 0x33031de5,
19721 0xaa0a4c5f, 0xdd0d7cc9, 0x5005713c, 0x270241aa, 0xbe0b1010,
19722 0xc90c2086, 0x5768b525, 0x206f85b3, 0xb966d409, 0xce61e49f,
19723 0x5edef90e, 0x29d9c998, 0xb0d09822, 0xc7d7a8b4, 0x59b33d17,
19724 0x2eb40d81, 0xb7bd5c3b, 0xc0ba6cad, 0xedb88320, 0x9abfb3b6,
19725 0x03b6e20c, 0x74b1d29a, 0xead54739, 0x9dd277af, 0x04db2615,
19726 0x73dc1683, 0xe3630b12, 0x94643b84, 0x0d6d6a3e, 0x7a6a5aa8,
19727 0xe40ecf0b, 0x9309ff9d, 0x0a00ae27, 0x7d079eb1, 0xf00f9344,
19728 0x8708a3d2, 0x1e01f268, 0x6906c2fe, 0xf762575d, 0x806567cb,
19729 0x196c3671, 0x6e6b06e7, 0xfed41b76, 0x89d32be0, 0x10da7a5a,
19730 0x67dd4acc, 0xf9b9df6f, 0x8ebeeff9, 0x17b7be43, 0x60b08ed5,
19731 0xd6d6a3e8, 0xa1d1937e, 0x38d8c2c4, 0x4fdff252, 0xd1bb67f1,
19732 0xa6bc5767, 0x3fb506dd, 0x48b2364b, 0xd80d2bda, 0xaf0a1b4c,
19733 0x36034af6, 0x41047a60, 0xdf60efc3, 0xa867df55, 0x316e8eef,
19734 0x4669be79, 0xcb61b38c, 0xbc66831a, 0x256fd2a0, 0x5268e236,
19735 0xcc0c7795, 0xbb0b4703, 0x220216b9, 0x5505262f, 0xc5ba3bbe,
19736 0xb2bd0b28, 0x2bb45a92, 0x5cb36a04, 0xc2d7ffa7, 0xb5d0cf31,
19737 0x2cd99e8b, 0x5bdeae1d, 0x9b64c2b0, 0xec63f226, 0x756aa39c,
19738 0x026d930a, 0x9c0906a9, 0xeb0e363f, 0x72076785, 0x05005713,
19739 0x95bf4a82, 0xe2b87a14, 0x7bb12bae, 0x0cb61b38, 0x92d28e9b,
19740 0xe5d5be0d, 0x7cdcefb7, 0x0bdbdf21, 0x86d3d2d4, 0xf1d4e242,
19741 0x68ddb3f8, 0x1fda836e, 0x81be16cd, 0xf6b9265b, 0x6fb077e1,
19742 0x18b74777, 0x88085ae6, 0xff0f6a70, 0x66063bca, 0x11010b5c,
19743 0x8f659eff, 0xf862ae69, 0x616bffd3, 0x166ccf45, 0xa00ae278,
19744 0xd70dd2ee, 0x4e048354, 0x3903b3c2, 0xa7672661, 0xd06016f7,
19745 0x4969474d, 0x3e6e77db, 0xaed16a4a, 0xd9d65adc, 0x40df0b66,
19746 0x37d83bf0, 0xa9bcae53, 0xdebb9ec5, 0x47b2cf7f, 0x30b5ffe9,
19747 0xbdbdf21c, 0xcabac28a, 0x53b39330, 0x24b4a3a6, 0xbad03605,
19748 0xcdd70693, 0x54de5729, 0x23d967bf, 0xb3667a2e, 0xc4614ab8,
19749 0x5d681b02, 0x2a6f2b94, 0xb40bbe37, 0xc30c8ea1, 0x5a05df1b,
19752 unsigned char *end;
19754 crc = ~crc & 0xffffffff;
19755 for (end = buf + len; buf < end; ++buf)
19756 crc = crc32_table[(crc ^ *buf) & 0xff] ^ (crc >> 8);
19757 return ~crc & 0xffffffff;
19762 This computation does not apply to the ``build ID'' method.
19764 @node MiniDebugInfo
19765 @section Debugging information in a special section
19766 @cindex separate debug sections
19767 @cindex @samp{.gnu_debugdata} section
19769 Some systems ship pre-built executables and libraries that have a
19770 special @samp{.gnu_debugdata} section. This feature is called
19771 @dfn{MiniDebugInfo}. This section holds an LZMA-compressed object and
19772 is used to supply extra symbols for backtraces.
19774 The intent of this section is to provide extra minimal debugging
19775 information for use in simple backtraces. It is not intended to be a
19776 replacement for full separate debugging information (@pxref{Separate
19777 Debug Files}). The example below shows the intended use; however,
19778 @value{GDBN} does not currently put restrictions on what sort of
19779 debugging information might be included in the section.
19781 @value{GDBN} has support for this extension. If the section exists,
19782 then it is used provided that no other source of debugging information
19783 can be found, and that @value{GDBN} was configured with LZMA support.
19785 This section can be easily created using @command{objcopy} and other
19786 standard utilities:
19789 # Extract the dynamic symbols from the main binary, there is no need
19790 # to also have these in the normal symbol table.
19791 nm -D @var{binary} --format=posix --defined-only \
19792 | awk '@{ print $1 @}' | sort > dynsyms
19794 # Extract all the text (i.e. function) symbols from the debuginfo.
19795 # (Note that we actually also accept "D" symbols, for the benefit
19796 # of platforms like PowerPC64 that use function descriptors.)
19797 nm @var{binary} --format=posix --defined-only \
19798 | awk '@{ if ($2 == "T" || $2 == "t" || $2 == "D") print $1 @}' \
19801 # Keep all the function symbols not already in the dynamic symbol
19803 comm -13 dynsyms funcsyms > keep_symbols
19805 # Separate full debug info into debug binary.
19806 objcopy --only-keep-debug @var{binary} debug
19808 # Copy the full debuginfo, keeping only a minimal set of symbols and
19809 # removing some unnecessary sections.
19810 objcopy -S --remove-section .gdb_index --remove-section .comment \
19811 --keep-symbols=keep_symbols debug mini_debuginfo
19813 # Drop the full debug info from the original binary.
19814 strip --strip-all -R .comment @var{binary}
19816 # Inject the compressed data into the .gnu_debugdata section of the
19819 objcopy --add-section .gnu_debugdata=mini_debuginfo.xz @var{binary}
19823 @section Index Files Speed Up @value{GDBN}
19824 @cindex index files
19825 @cindex @samp{.gdb_index} section
19827 When @value{GDBN} finds a symbol file, it scans the symbols in the
19828 file in order to construct an internal symbol table. This lets most
19829 @value{GDBN} operations work quickly---at the cost of a delay early
19830 on. For large programs, this delay can be quite lengthy, so
19831 @value{GDBN} provides a way to build an index, which speeds up
19834 For convenience, @value{GDBN} comes with a program,
19835 @command{gdb-add-index}, which can be used to add the index to a
19836 symbol file. It takes the symbol file as its only argument:
19839 $ gdb-add-index symfile
19842 @xref{gdb-add-index}.
19844 It is also possible to do the work manually. Here is what
19845 @command{gdb-add-index} does behind the curtains.
19847 The index is stored as a section in the symbol file. @value{GDBN} can
19848 write the index to a file, then you can put it into the symbol file
19849 using @command{objcopy}.
19851 To create an index file, use the @code{save gdb-index} command:
19854 @item save gdb-index [-dwarf-5] @var{directory}
19855 @kindex save gdb-index
19856 Create index files for all symbol files currently known by
19857 @value{GDBN}. For each known @var{symbol-file}, this command by
19858 default creates it produces a single file
19859 @file{@var{symbol-file}.gdb-index}. If you invoke this command with
19860 the @option{-dwarf-5} option, it produces 2 files:
19861 @file{@var{symbol-file}.debug_names} and
19862 @file{@var{symbol-file}.debug_str}. The files are created in the
19863 given @var{directory}.
19866 Once you have created an index file you can merge it into your symbol
19867 file, here named @file{symfile}, using @command{objcopy}:
19870 $ objcopy --add-section .gdb_index=symfile.gdb-index \
19871 --set-section-flags .gdb_index=readonly symfile symfile
19874 Or for @code{-dwarf-5}:
19877 $ objcopy --dump-section .debug_str=symfile.debug_str.new symfile
19878 $ cat symfile.debug_str >>symfile.debug_str.new
19879 $ objcopy --add-section .debug_names=symfile.gdb-index \
19880 --set-section-flags .debug_names=readonly \
19881 --update-section .debug_str=symfile.debug_str.new symfile symfile
19884 @value{GDBN} will normally ignore older versions of @file{.gdb_index}
19885 sections that have been deprecated. Usually they are deprecated because
19886 they are missing a new feature or have performance issues.
19887 To tell @value{GDBN} to use a deprecated index section anyway
19888 specify @code{set use-deprecated-index-sections on}.
19889 The default is @code{off}.
19890 This can speed up startup, but may result in some functionality being lost.
19891 @xref{Index Section Format}.
19893 @emph{Warning:} Setting @code{use-deprecated-index-sections} to @code{on}
19894 must be done before gdb reads the file. The following will not work:
19897 $ gdb -ex "set use-deprecated-index-sections on" <program>
19900 Instead you must do, for example,
19903 $ gdb -iex "set use-deprecated-index-sections on" <program>
19906 There are currently some limitation on indices. They only work when
19907 for DWARF debugging information, not stabs. And, they do not
19908 currently work for programs using Ada.
19910 @node Symbol Errors
19911 @section Errors Reading Symbol Files
19913 While reading a symbol file, @value{GDBN} occasionally encounters problems,
19914 such as symbol types it does not recognize, or known bugs in compiler
19915 output. By default, @value{GDBN} does not notify you of such problems, since
19916 they are relatively common and primarily of interest to people
19917 debugging compilers. If you are interested in seeing information
19918 about ill-constructed symbol tables, you can either ask @value{GDBN} to print
19919 only one message about each such type of problem, no matter how many
19920 times the problem occurs; or you can ask @value{GDBN} to print more messages,
19921 to see how many times the problems occur, with the @code{set
19922 complaints} command (@pxref{Messages/Warnings, ,Optional Warnings and
19925 The messages currently printed, and their meanings, include:
19928 @item inner block not inside outer block in @var{symbol}
19930 The symbol information shows where symbol scopes begin and end
19931 (such as at the start of a function or a block of statements). This
19932 error indicates that an inner scope block is not fully contained
19933 in its outer scope blocks.
19935 @value{GDBN} circumvents the problem by treating the inner block as if it had
19936 the same scope as the outer block. In the error message, @var{symbol}
19937 may be shown as ``@code{(don't know)}'' if the outer block is not a
19940 @item block at @var{address} out of order
19942 The symbol information for symbol scope blocks should occur in
19943 order of increasing addresses. This error indicates that it does not
19946 @value{GDBN} does not circumvent this problem, and has trouble
19947 locating symbols in the source file whose symbols it is reading. (You
19948 can often determine what source file is affected by specifying
19949 @code{set verbose on}. @xref{Messages/Warnings, ,Optional Warnings and
19952 @item bad block start address patched
19954 The symbol information for a symbol scope block has a start address
19955 smaller than the address of the preceding source line. This is known
19956 to occur in the SunOS 4.1.1 (and earlier) C compiler.
19958 @value{GDBN} circumvents the problem by treating the symbol scope block as
19959 starting on the previous source line.
19961 @item bad string table offset in symbol @var{n}
19964 Symbol number @var{n} contains a pointer into the string table which is
19965 larger than the size of the string table.
19967 @value{GDBN} circumvents the problem by considering the symbol to have the
19968 name @code{foo}, which may cause other problems if many symbols end up
19971 @item unknown symbol type @code{0x@var{nn}}
19973 The symbol information contains new data types that @value{GDBN} does
19974 not yet know how to read. @code{0x@var{nn}} is the symbol type of the
19975 uncomprehended information, in hexadecimal.
19977 @value{GDBN} circumvents the error by ignoring this symbol information.
19978 This usually allows you to debug your program, though certain symbols
19979 are not accessible. If you encounter such a problem and feel like
19980 debugging it, you can debug @code{@value{GDBP}} with itself, breakpoint
19981 on @code{complain}, then go up to the function @code{read_dbx_symtab}
19982 and examine @code{*bufp} to see the symbol.
19984 @item stub type has NULL name
19986 @value{GDBN} could not find the full definition for a struct or class.
19988 @item const/volatile indicator missing (ok if using g++ v1.x), got@dots{}
19989 The symbol information for a C@t{++} member function is missing some
19990 information that recent versions of the compiler should have output for
19993 @item info mismatch between compiler and debugger
19995 @value{GDBN} could not parse a type specification output by the compiler.
20000 @section GDB Data Files
20002 @cindex prefix for data files
20003 @value{GDBN} will sometimes read an auxiliary data file. These files
20004 are kept in a directory known as the @dfn{data directory}.
20006 You can set the data directory's name, and view the name @value{GDBN}
20007 is currently using.
20010 @kindex set data-directory
20011 @item set data-directory @var{directory}
20012 Set the directory which @value{GDBN} searches for auxiliary data files
20013 to @var{directory}.
20015 @kindex show data-directory
20016 @item show data-directory
20017 Show the directory @value{GDBN} searches for auxiliary data files.
20020 @cindex default data directory
20021 @cindex @samp{--with-gdb-datadir}
20022 You can set the default data directory by using the configure-time
20023 @samp{--with-gdb-datadir} option. If the data directory is inside
20024 @value{GDBN}'s configured binary prefix (set with @samp{--prefix} or
20025 @samp{--exec-prefix}), then the default data directory will be updated
20026 automatically if the installed @value{GDBN} is moved to a new
20029 The data directory may also be specified with the
20030 @code{--data-directory} command line option.
20031 @xref{Mode Options}.
20034 @chapter Specifying a Debugging Target
20036 @cindex debugging target
20037 A @dfn{target} is the execution environment occupied by your program.
20039 Often, @value{GDBN} runs in the same host environment as your program;
20040 in that case, the debugging target is specified as a side effect when
20041 you use the @code{file} or @code{core} commands. When you need more
20042 flexibility---for example, running @value{GDBN} on a physically separate
20043 host, or controlling a standalone system over a serial port or a
20044 realtime system over a TCP/IP connection---you can use the @code{target}
20045 command to specify one of the target types configured for @value{GDBN}
20046 (@pxref{Target Commands, ,Commands for Managing Targets}).
20048 @cindex target architecture
20049 It is possible to build @value{GDBN} for several different @dfn{target
20050 architectures}. When @value{GDBN} is built like that, you can choose
20051 one of the available architectures with the @kbd{set architecture}
20055 @kindex set architecture
20056 @kindex show architecture
20057 @item set architecture @var{arch}
20058 This command sets the current target architecture to @var{arch}. The
20059 value of @var{arch} can be @code{"auto"}, in addition to one of the
20060 supported architectures.
20062 @item show architecture
20063 Show the current target architecture.
20065 @item set processor
20067 @kindex set processor
20068 @kindex show processor
20069 These are alias commands for, respectively, @code{set architecture}
20070 and @code{show architecture}.
20074 * Active Targets:: Active targets
20075 * Target Commands:: Commands for managing targets
20076 * Byte Order:: Choosing target byte order
20079 @node Active Targets
20080 @section Active Targets
20082 @cindex stacking targets
20083 @cindex active targets
20084 @cindex multiple targets
20086 There are multiple classes of targets such as: processes, executable files or
20087 recording sessions. Core files belong to the process class, making core file
20088 and process mutually exclusive. Otherwise, @value{GDBN} can work concurrently
20089 on multiple active targets, one in each class. This allows you to (for
20090 example) start a process and inspect its activity, while still having access to
20091 the executable file after the process finishes. Or if you start process
20092 recording (@pxref{Reverse Execution}) and @code{reverse-step} there, you are
20093 presented a virtual layer of the recording target, while the process target
20094 remains stopped at the chronologically last point of the process execution.
20096 Use the @code{core-file} and @code{exec-file} commands to select a new core
20097 file or executable target (@pxref{Files, ,Commands to Specify Files}). To
20098 specify as a target a process that is already running, use the @code{attach}
20099 command (@pxref{Attach, ,Debugging an Already-running Process}).
20101 @node Target Commands
20102 @section Commands for Managing Targets
20105 @item target @var{type} @var{parameters}
20106 Connects the @value{GDBN} host environment to a target machine or
20107 process. A target is typically a protocol for talking to debugging
20108 facilities. You use the argument @var{type} to specify the type or
20109 protocol of the target machine.
20111 Further @var{parameters} are interpreted by the target protocol, but
20112 typically include things like device names or host names to connect
20113 with, process numbers, and baud rates.
20115 The @code{target} command does not repeat if you press @key{RET} again
20116 after executing the command.
20118 @kindex help target
20120 Displays the names of all targets available. To display targets
20121 currently selected, use either @code{info target} or @code{info files}
20122 (@pxref{Files, ,Commands to Specify Files}).
20124 @item help target @var{name}
20125 Describe a particular target, including any parameters necessary to
20128 @kindex set gnutarget
20129 @item set gnutarget @var{args}
20130 @value{GDBN} uses its own library BFD to read your files. @value{GDBN}
20131 knows whether it is reading an @dfn{executable},
20132 a @dfn{core}, or a @dfn{.o} file; however, you can specify the file format
20133 with the @code{set gnutarget} command. Unlike most @code{target} commands,
20134 with @code{gnutarget} the @code{target} refers to a program, not a machine.
20137 @emph{Warning:} To specify a file format with @code{set gnutarget},
20138 you must know the actual BFD name.
20142 @xref{Files, , Commands to Specify Files}.
20144 @kindex show gnutarget
20145 @item show gnutarget
20146 Use the @code{show gnutarget} command to display what file format
20147 @code{gnutarget} is set to read. If you have not set @code{gnutarget},
20148 @value{GDBN} will determine the file format for each file automatically,
20149 and @code{show gnutarget} displays @samp{The current BFD target is "auto"}.
20152 @cindex common targets
20153 Here are some common targets (available, or not, depending on the GDB
20158 @item target exec @var{program}
20159 @cindex executable file target
20160 An executable file. @samp{target exec @var{program}} is the same as
20161 @samp{exec-file @var{program}}.
20163 @item target core @var{filename}
20164 @cindex core dump file target
20165 A core dump file. @samp{target core @var{filename}} is the same as
20166 @samp{core-file @var{filename}}.
20168 @item target remote @var{medium}
20169 @cindex remote target
20170 A remote system connected to @value{GDBN} via a serial line or network
20171 connection. This command tells @value{GDBN} to use its own remote
20172 protocol over @var{medium} for debugging. @xref{Remote Debugging}.
20174 For example, if you have a board connected to @file{/dev/ttya} on the
20175 machine running @value{GDBN}, you could say:
20178 target remote /dev/ttya
20181 @code{target remote} supports the @code{load} command. This is only
20182 useful if you have some other way of getting the stub to the target
20183 system, and you can put it somewhere in memory where it won't get
20184 clobbered by the download.
20186 @item target sim @r{[}@var{simargs}@r{]} @dots{}
20187 @cindex built-in simulator target
20188 Builtin CPU simulator. @value{GDBN} includes simulators for most architectures.
20196 works; however, you cannot assume that a specific memory map, device
20197 drivers, or even basic I/O is available, although some simulators do
20198 provide these. For info about any processor-specific simulator details,
20199 see the appropriate section in @ref{Embedded Processors, ,Embedded
20202 @item target native
20203 @cindex native target
20204 Setup for local/native process debugging. Useful to make the
20205 @code{run} command spawn native processes (likewise @code{attach},
20206 etc.@:) even when @code{set auto-connect-native-target} is @code{off}
20207 (@pxref{set auto-connect-native-target}).
20211 Different targets are available on different configurations of @value{GDBN};
20212 your configuration may have more or fewer targets.
20214 Many remote targets require you to download the executable's code once
20215 you've successfully established a connection. You may wish to control
20216 various aspects of this process.
20221 @kindex set hash@r{, for remote monitors}
20222 @cindex hash mark while downloading
20223 This command controls whether a hash mark @samp{#} is displayed while
20224 downloading a file to the remote monitor. If on, a hash mark is
20225 displayed after each S-record is successfully downloaded to the
20229 @kindex show hash@r{, for remote monitors}
20230 Show the current status of displaying the hash mark.
20232 @item set debug monitor
20233 @kindex set debug monitor
20234 @cindex display remote monitor communications
20235 Enable or disable display of communications messages between
20236 @value{GDBN} and the remote monitor.
20238 @item show debug monitor
20239 @kindex show debug monitor
20240 Show the current status of displaying communications between
20241 @value{GDBN} and the remote monitor.
20246 @kindex load @var{filename} @var{offset}
20247 @item load @var{filename} @var{offset}
20249 Depending on what remote debugging facilities are configured into
20250 @value{GDBN}, the @code{load} command may be available. Where it exists, it
20251 is meant to make @var{filename} (an executable) available for debugging
20252 on the remote system---by downloading, or dynamic linking, for example.
20253 @code{load} also records the @var{filename} symbol table in @value{GDBN}, like
20254 the @code{add-symbol-file} command.
20256 If your @value{GDBN} does not have a @code{load} command, attempting to
20257 execute it gets the error message ``@code{You can't do that when your
20258 target is @dots{}}''
20260 The file is loaded at whatever address is specified in the executable.
20261 For some object file formats, you can specify the load address when you
20262 link the program; for other formats, like a.out, the object file format
20263 specifies a fixed address.
20264 @c FIXME! This would be a good place for an xref to the GNU linker doc.
20266 It is also possible to tell @value{GDBN} to load the executable file at a
20267 specific offset described by the optional argument @var{offset}. When
20268 @var{offset} is provided, @var{filename} must also be provided.
20270 Depending on the remote side capabilities, @value{GDBN} may be able to
20271 load programs into flash memory.
20273 @code{load} does not repeat if you press @key{RET} again after using it.
20278 @kindex flash-erase
20280 @anchor{flash-erase}
20282 Erases all known flash memory regions on the target.
20287 @section Choosing Target Byte Order
20289 @cindex choosing target byte order
20290 @cindex target byte order
20292 Some types of processors, such as the @acronym{MIPS}, PowerPC, and Renesas SH,
20293 offer the ability to run either big-endian or little-endian byte
20294 orders. Usually the executable or symbol will include a bit to
20295 designate the endian-ness, and you will not need to worry about
20296 which to use. However, you may still find it useful to adjust
20297 @value{GDBN}'s idea of processor endian-ness manually.
20301 @item set endian big
20302 Instruct @value{GDBN} to assume the target is big-endian.
20304 @item set endian little
20305 Instruct @value{GDBN} to assume the target is little-endian.
20307 @item set endian auto
20308 Instruct @value{GDBN} to use the byte order associated with the
20312 Display @value{GDBN}'s current idea of the target byte order.
20316 If the @code{set endian auto} mode is in effect and no executable has
20317 been selected, then the endianness used is the last one chosen either
20318 by one of the @code{set endian big} and @code{set endian little}
20319 commands or by inferring from the last executable used. If no
20320 endianness has been previously chosen, then the default for this mode
20321 is inferred from the target @value{GDBN} has been built for, and is
20322 @code{little} if the name of the target CPU has an @code{el} suffix
20323 and @code{big} otherwise.
20325 Note that these commands merely adjust interpretation of symbolic
20326 data on the host, and that they have absolutely no effect on the
20330 @node Remote Debugging
20331 @chapter Debugging Remote Programs
20332 @cindex remote debugging
20334 If you are trying to debug a program running on a machine that cannot run
20335 @value{GDBN} in the usual way, it is often useful to use remote debugging.
20336 For example, you might use remote debugging on an operating system kernel,
20337 or on a small system which does not have a general purpose operating system
20338 powerful enough to run a full-featured debugger.
20340 Some configurations of @value{GDBN} have special serial or TCP/IP interfaces
20341 to make this work with particular debugging targets. In addition,
20342 @value{GDBN} comes with a generic serial protocol (specific to @value{GDBN},
20343 but not specific to any particular target system) which you can use if you
20344 write the remote stubs---the code that runs on the remote system to
20345 communicate with @value{GDBN}.
20347 Other remote targets may be available in your
20348 configuration of @value{GDBN}; use @code{help target} to list them.
20351 * Connecting:: Connecting to a remote target
20352 * File Transfer:: Sending files to a remote system
20353 * Server:: Using the gdbserver program
20354 * Remote Configuration:: Remote configuration
20355 * Remote Stub:: Implementing a remote stub
20359 @section Connecting to a Remote Target
20360 @cindex remote debugging, connecting
20361 @cindex @code{gdbserver}, connecting
20362 @cindex remote debugging, types of connections
20363 @cindex @code{gdbserver}, types of connections
20364 @cindex @code{gdbserver}, @code{target remote} mode
20365 @cindex @code{gdbserver}, @code{target extended-remote} mode
20367 This section describes how to connect to a remote target, including the
20368 types of connections and their differences, how to set up executable and
20369 symbol files on the host and target, and the commands used for
20370 connecting to and disconnecting from the remote target.
20372 @subsection Types of Remote Connections
20374 @value{GDBN} supports two types of remote connections, @code{target remote}
20375 mode and @code{target extended-remote} mode. Note that many remote targets
20376 support only @code{target remote} mode. There are several major
20377 differences between the two types of connections, enumerated here:
20381 @cindex remote debugging, detach and program exit
20382 @item Result of detach or program exit
20383 @strong{With target remote mode:} When the debugged program exits or you
20384 detach from it, @value{GDBN} disconnects from the target. When using
20385 @code{gdbserver}, @code{gdbserver} will exit.
20387 @strong{With target extended-remote mode:} When the debugged program exits or
20388 you detach from it, @value{GDBN} remains connected to the target, even
20389 though no program is running. You can rerun the program, attach to a
20390 running program, or use @code{monitor} commands specific to the target.
20392 When using @code{gdbserver} in this case, it does not exit unless it was
20393 invoked using the @option{--once} option. If the @option{--once} option
20394 was not used, you can ask @code{gdbserver} to exit using the
20395 @code{monitor exit} command (@pxref{Monitor Commands for gdbserver}).
20397 @item Specifying the program to debug
20398 For both connection types you use the @code{file} command to specify the
20399 program on the host system. If you are using @code{gdbserver} there are
20400 some differences in how to specify the location of the program on the
20403 @strong{With target remote mode:} You must either specify the program to debug
20404 on the @code{gdbserver} command line or use the @option{--attach} option
20405 (@pxref{Attaching to a program,,Attaching to a Running Program}).
20407 @cindex @option{--multi}, @code{gdbserver} option
20408 @strong{With target extended-remote mode:} You may specify the program to debug
20409 on the @code{gdbserver} command line, or you can load the program or attach
20410 to it using @value{GDBN} commands after connecting to @code{gdbserver}.
20412 @anchor{--multi Option in Types of Remote Connnections}
20413 You can start @code{gdbserver} without supplying an initial command to run
20414 or process ID to attach. To do this, use the @option{--multi} command line
20415 option. Then you can connect using @code{target extended-remote} and start
20416 the program you want to debug (see below for details on using the
20417 @code{run} command in this scenario). Note that the conditions under which
20418 @code{gdbserver} terminates depend on how @value{GDBN} connects to it
20419 (@code{target remote} or @code{target extended-remote}). The
20420 @option{--multi} option to @code{gdbserver} has no influence on that.
20422 @item The @code{run} command
20423 @strong{With target remote mode:} The @code{run} command is not
20424 supported. Once a connection has been established, you can use all
20425 the usual @value{GDBN} commands to examine and change data. The
20426 remote program is already running, so you can use commands like
20427 @kbd{step} and @kbd{continue}.
20429 @strong{With target extended-remote mode:} The @code{run} command is
20430 supported. The @code{run} command uses the value set by
20431 @code{set remote exec-file} (@pxref{set remote exec-file}) to select
20432 the program to run. Command line arguments are supported, except for
20433 wildcard expansion and I/O redirection (@pxref{Arguments}).
20435 If you specify the program to debug on the command line, then the
20436 @code{run} command is not required to start execution, and you can
20437 resume using commands like @kbd{step} and @kbd{continue} as with
20438 @code{target remote} mode.
20440 @anchor{Attaching in Types of Remote Connections}
20442 @strong{With target remote mode:} The @value{GDBN} command @code{attach} is
20443 not supported. To attach to a running program using @code{gdbserver}, you
20444 must use the @option{--attach} option (@pxref{Running gdbserver}).
20446 @strong{With target extended-remote mode:} To attach to a running program,
20447 you may use the @code{attach} command after the connection has been
20448 established. If you are using @code{gdbserver}, you may also invoke
20449 @code{gdbserver} using the @option{--attach} option
20450 (@pxref{Running gdbserver}).
20454 @anchor{Host and target files}
20455 @subsection Host and Target Files
20456 @cindex remote debugging, symbol files
20457 @cindex symbol files, remote debugging
20459 @value{GDBN}, running on the host, needs access to symbol and debugging
20460 information for your program running on the target. This requires
20461 access to an unstripped copy of your program, and possibly any associated
20462 symbol files. Note that this section applies equally to both @code{target
20463 remote} mode and @code{target extended-remote} mode.
20465 Some remote targets (@pxref{qXfer executable filename read}, and
20466 @pxref{Host I/O Packets}) allow @value{GDBN} to access program files over
20467 the same connection used to communicate with @value{GDBN}. With such a
20468 target, if the remote program is unstripped, the only command you need is
20469 @code{target remote} (or @code{target extended-remote}).
20471 If the remote program is stripped, or the target does not support remote
20472 program file access, start up @value{GDBN} using the name of the local
20473 unstripped copy of your program as the first argument, or use the
20474 @code{file} command. Use @code{set sysroot} to specify the location (on
20475 the host) of target libraries (unless your @value{GDBN} was compiled with
20476 the correct sysroot using @code{--with-sysroot}). Alternatively, you
20477 may use @code{set solib-search-path} to specify how @value{GDBN} locates
20480 The symbol file and target libraries must exactly match the executable
20481 and libraries on the target, with one exception: the files on the host
20482 system should not be stripped, even if the files on the target system
20483 are. Mismatched or missing files will lead to confusing results
20484 during debugging. On @sc{gnu}/Linux targets, mismatched or missing
20485 files may also prevent @code{gdbserver} from debugging multi-threaded
20488 @subsection Remote Connection Commands
20489 @cindex remote connection commands
20490 @value{GDBN} can communicate with the target over a serial line, or
20491 over an @acronym{IP} network using @acronym{TCP} or @acronym{UDP}. In
20492 each case, @value{GDBN} uses the same protocol for debugging your
20493 program; only the medium carrying the debugging packets varies. The
20494 @code{target remote} and @code{target extended-remote} commands
20495 establish a connection to the target. Both commands accept the same
20496 arguments, which indicate the medium to use:
20500 @item target remote @var{serial-device}
20501 @itemx target extended-remote @var{serial-device}
20502 @cindex serial line, @code{target remote}
20503 Use @var{serial-device} to communicate with the target. For example,
20504 to use a serial line connected to the device named @file{/dev/ttyb}:
20507 target remote /dev/ttyb
20510 If you're using a serial line, you may want to give @value{GDBN} the
20511 @samp{--baud} option, or use the @code{set serial baud} command
20512 (@pxref{Remote Configuration, set serial baud}) before the
20513 @code{target} command.
20515 @item target remote @code{@var{host}:@var{port}}
20516 @itemx target remote @code{tcp:@var{host}:@var{port}}
20517 @itemx target extended-remote @code{@var{host}:@var{port}}
20518 @itemx target extended-remote @code{tcp:@var{host}:@var{port}}
20519 @cindex @acronym{TCP} port, @code{target remote}
20520 Debug using a @acronym{TCP} connection to @var{port} on @var{host}.
20521 The @var{host} may be either a host name or a numeric @acronym{IP}
20522 address; @var{port} must be a decimal number. The @var{host} could be
20523 the target machine itself, if it is directly connected to the net, or
20524 it might be a terminal server which in turn has a serial line to the
20527 For example, to connect to port 2828 on a terminal server named
20531 target remote manyfarms:2828
20534 If your remote target is actually running on the same machine as your
20535 debugger session (e.g.@: a simulator for your target running on the
20536 same host), you can omit the hostname. For example, to connect to
20537 port 1234 on your local machine:
20540 target remote :1234
20544 Note that the colon is still required here.
20546 @item target remote @code{udp:@var{host}:@var{port}}
20547 @itemx target extended-remote @code{udp:@var{host}:@var{port}}
20548 @cindex @acronym{UDP} port, @code{target remote}
20549 Debug using @acronym{UDP} packets to @var{port} on @var{host}. For example, to
20550 connect to @acronym{UDP} port 2828 on a terminal server named @code{manyfarms}:
20553 target remote udp:manyfarms:2828
20556 When using a @acronym{UDP} connection for remote debugging, you should
20557 keep in mind that the `U' stands for ``Unreliable''. @acronym{UDP}
20558 can silently drop packets on busy or unreliable networks, which will
20559 cause havoc with your debugging session.
20561 @item target remote | @var{command}
20562 @itemx target extended-remote | @var{command}
20563 @cindex pipe, @code{target remote} to
20564 Run @var{command} in the background and communicate with it using a
20565 pipe. The @var{command} is a shell command, to be parsed and expanded
20566 by the system's command shell, @code{/bin/sh}; it should expect remote
20567 protocol packets on its standard input, and send replies on its
20568 standard output. You could use this to run a stand-alone simulator
20569 that speaks the remote debugging protocol, to make net connections
20570 using programs like @code{ssh}, or for other similar tricks.
20572 If @var{command} closes its standard output (perhaps by exiting),
20573 @value{GDBN} will try to send it a @code{SIGTERM} signal. (If the
20574 program has already exited, this will have no effect.)
20578 @cindex interrupting remote programs
20579 @cindex remote programs, interrupting
20580 Whenever @value{GDBN} is waiting for the remote program, if you type the
20581 interrupt character (often @kbd{Ctrl-c}), @value{GDBN} attempts to stop the
20582 program. This may or may not succeed, depending in part on the hardware
20583 and the serial drivers the remote system uses. If you type the
20584 interrupt character once again, @value{GDBN} displays this prompt:
20587 Interrupted while waiting for the program.
20588 Give up (and stop debugging it)? (y or n)
20591 In @code{target remote} mode, if you type @kbd{y}, @value{GDBN} abandons
20592 the remote debugging session. (If you decide you want to try again later,
20593 you can use @kbd{target remote} again to connect once more.) If you type
20594 @kbd{n}, @value{GDBN} goes back to waiting.
20596 In @code{target extended-remote} mode, typing @kbd{n} will leave
20597 @value{GDBN} connected to the target.
20600 @kindex detach (remote)
20602 When you have finished debugging the remote program, you can use the
20603 @code{detach} command to release it from @value{GDBN} control.
20604 Detaching from the target normally resumes its execution, but the results
20605 will depend on your particular remote stub. After the @code{detach}
20606 command in @code{target remote} mode, @value{GDBN} is free to connect to
20607 another target. In @code{target extended-remote} mode, @value{GDBN} is
20608 still connected to the target.
20612 The @code{disconnect} command closes the connection to the target, and
20613 the target is generally not resumed. It will wait for @value{GDBN}
20614 (this instance or another one) to connect and continue debugging. After
20615 the @code{disconnect} command, @value{GDBN} is again free to connect to
20618 @cindex send command to remote monitor
20619 @cindex extend @value{GDBN} for remote targets
20620 @cindex add new commands for external monitor
20622 @item monitor @var{cmd}
20623 This command allows you to send arbitrary commands directly to the
20624 remote monitor. Since @value{GDBN} doesn't care about the commands it
20625 sends like this, this command is the way to extend @value{GDBN}---you
20626 can add new commands that only the external monitor will understand
20630 @node File Transfer
20631 @section Sending files to a remote system
20632 @cindex remote target, file transfer
20633 @cindex file transfer
20634 @cindex sending files to remote systems
20636 Some remote targets offer the ability to transfer files over the same
20637 connection used to communicate with @value{GDBN}. This is convenient
20638 for targets accessible through other means, e.g.@: @sc{gnu}/Linux systems
20639 running @code{gdbserver} over a network interface. For other targets,
20640 e.g.@: embedded devices with only a single serial port, this may be
20641 the only way to upload or download files.
20643 Not all remote targets support these commands.
20647 @item remote put @var{hostfile} @var{targetfile}
20648 Copy file @var{hostfile} from the host system (the machine running
20649 @value{GDBN}) to @var{targetfile} on the target system.
20652 @item remote get @var{targetfile} @var{hostfile}
20653 Copy file @var{targetfile} from the target system to @var{hostfile}
20654 on the host system.
20656 @kindex remote delete
20657 @item remote delete @var{targetfile}
20658 Delete @var{targetfile} from the target system.
20663 @section Using the @code{gdbserver} Program
20666 @cindex remote connection without stubs
20667 @code{gdbserver} is a control program for Unix-like systems, which
20668 allows you to connect your program with a remote @value{GDBN} via
20669 @code{target remote} or @code{target extended-remote}---but without
20670 linking in the usual debugging stub.
20672 @code{gdbserver} is not a complete replacement for the debugging stubs,
20673 because it requires essentially the same operating-system facilities
20674 that @value{GDBN} itself does. In fact, a system that can run
20675 @code{gdbserver} to connect to a remote @value{GDBN} could also run
20676 @value{GDBN} locally! @code{gdbserver} is sometimes useful nevertheless,
20677 because it is a much smaller program than @value{GDBN} itself. It is
20678 also easier to port than all of @value{GDBN}, so you may be able to get
20679 started more quickly on a new system by using @code{gdbserver}.
20680 Finally, if you develop code for real-time systems, you may find that
20681 the tradeoffs involved in real-time operation make it more convenient to
20682 do as much development work as possible on another system, for example
20683 by cross-compiling. You can use @code{gdbserver} to make a similar
20684 choice for debugging.
20686 @value{GDBN} and @code{gdbserver} communicate via either a serial line
20687 or a TCP connection, using the standard @value{GDBN} remote serial
20691 @emph{Warning:} @code{gdbserver} does not have any built-in security.
20692 Do not run @code{gdbserver} connected to any public network; a
20693 @value{GDBN} connection to @code{gdbserver} provides access to the
20694 target system with the same privileges as the user running
20698 @anchor{Running gdbserver}
20699 @subsection Running @code{gdbserver}
20700 @cindex arguments, to @code{gdbserver}
20701 @cindex @code{gdbserver}, command-line arguments
20703 Run @code{gdbserver} on the target system. You need a copy of the
20704 program you want to debug, including any libraries it requires.
20705 @code{gdbserver} does not need your program's symbol table, so you can
20706 strip the program if necessary to save space. @value{GDBN} on the host
20707 system does all the symbol handling.
20709 To use the server, you must tell it how to communicate with @value{GDBN};
20710 the name of your program; and the arguments for your program. The usual
20714 target> gdbserver @var{comm} @var{program} [ @var{args} @dots{} ]
20717 @var{comm} is either a device name (to use a serial line), or a TCP
20718 hostname and portnumber, or @code{-} or @code{stdio} to use
20719 stdin/stdout of @code{gdbserver}.
20720 For example, to debug Emacs with the argument
20721 @samp{foo.txt} and communicate with @value{GDBN} over the serial port
20725 target> gdbserver /dev/com1 emacs foo.txt
20728 @code{gdbserver} waits passively for the host @value{GDBN} to communicate
20731 To use a TCP connection instead of a serial line:
20734 target> gdbserver host:2345 emacs foo.txt
20737 The only difference from the previous example is the first argument,
20738 specifying that you are communicating with the host @value{GDBN} via
20739 TCP. The @samp{host:2345} argument means that @code{gdbserver} is to
20740 expect a TCP connection from machine @samp{host} to local TCP port 2345.
20741 (Currently, the @samp{host} part is ignored.) You can choose any number
20742 you want for the port number as long as it does not conflict with any
20743 TCP ports already in use on the target system (for example, @code{23} is
20744 reserved for @code{telnet}).@footnote{If you choose a port number that
20745 conflicts with another service, @code{gdbserver} prints an error message
20746 and exits.} You must use the same port number with the host @value{GDBN}
20747 @code{target remote} command.
20749 The @code{stdio} connection is useful when starting @code{gdbserver}
20753 (gdb) target remote | ssh -T hostname gdbserver - hello
20756 The @samp{-T} option to ssh is provided because we don't need a remote pty,
20757 and we don't want escape-character handling. Ssh does this by default when
20758 a command is provided, the flag is provided to make it explicit.
20759 You could elide it if you want to.
20761 Programs started with stdio-connected gdbserver have @file{/dev/null} for
20762 @code{stdin}, and @code{stdout},@code{stderr} are sent back to gdb for
20763 display through a pipe connected to gdbserver.
20764 Both @code{stdout} and @code{stderr} use the same pipe.
20766 @anchor{Attaching to a program}
20767 @subsubsection Attaching to a Running Program
20768 @cindex attach to a program, @code{gdbserver}
20769 @cindex @option{--attach}, @code{gdbserver} option
20771 On some targets, @code{gdbserver} can also attach to running programs.
20772 This is accomplished via the @code{--attach} argument. The syntax is:
20775 target> gdbserver --attach @var{comm} @var{pid}
20778 @var{pid} is the process ID of a currently running process. It isn't
20779 necessary to point @code{gdbserver} at a binary for the running process.
20781 In @code{target extended-remote} mode, you can also attach using the
20782 @value{GDBN} attach command
20783 (@pxref{Attaching in Types of Remote Connections}).
20786 You can debug processes by name instead of process ID if your target has the
20787 @code{pidof} utility:
20790 target> gdbserver --attach @var{comm} `pidof @var{program}`
20793 In case more than one copy of @var{program} is running, or @var{program}
20794 has multiple threads, most versions of @code{pidof} support the
20795 @code{-s} option to only return the first process ID.
20797 @subsubsection TCP port allocation lifecycle of @code{gdbserver}
20799 This section applies only when @code{gdbserver} is run to listen on a TCP
20802 @code{gdbserver} normally terminates after all of its debugged processes have
20803 terminated in @kbd{target remote} mode. On the other hand, for @kbd{target
20804 extended-remote}, @code{gdbserver} stays running even with no processes left.
20805 @value{GDBN} normally terminates the spawned debugged process on its exit,
20806 which normally also terminates @code{gdbserver} in the @kbd{target remote}
20807 mode. Therefore, when the connection drops unexpectedly, and @value{GDBN}
20808 cannot ask @code{gdbserver} to kill its debugged processes, @code{gdbserver}
20809 stays running even in the @kbd{target remote} mode.
20811 When @code{gdbserver} stays running, @value{GDBN} can connect to it again later.
20812 Such reconnecting is useful for features like @ref{disconnected tracing}. For
20813 completeness, at most one @value{GDBN} can be connected at a time.
20815 @cindex @option{--once}, @code{gdbserver} option
20816 By default, @code{gdbserver} keeps the listening TCP port open, so that
20817 subsequent connections are possible. However, if you start @code{gdbserver}
20818 with the @option{--once} option, it will stop listening for any further
20819 connection attempts after connecting to the first @value{GDBN} session. This
20820 means no further connections to @code{gdbserver} will be possible after the
20821 first one. It also means @code{gdbserver} will terminate after the first
20822 connection with remote @value{GDBN} has closed, even for unexpectedly closed
20823 connections and even in the @kbd{target extended-remote} mode. The
20824 @option{--once} option allows reusing the same port number for connecting to
20825 multiple instances of @code{gdbserver} running on the same host, since each
20826 instance closes its port after the first connection.
20828 @anchor{Other Command-Line Arguments for gdbserver}
20829 @subsubsection Other Command-Line Arguments for @code{gdbserver}
20831 You can use the @option{--multi} option to start @code{gdbserver} without
20832 specifying a program to debug or a process to attach to. Then you can
20833 attach in @code{target extended-remote} mode and run or attach to a
20834 program. For more information,
20835 @pxref{--multi Option in Types of Remote Connnections}.
20837 @cindex @option{--debug}, @code{gdbserver} option
20838 The @option{--debug} option tells @code{gdbserver} to display extra
20839 status information about the debugging process.
20840 @cindex @option{--remote-debug}, @code{gdbserver} option
20841 The @option{--remote-debug} option tells @code{gdbserver} to display
20842 remote protocol debug output. These options are intended for
20843 @code{gdbserver} development and for bug reports to the developers.
20845 @cindex @option{--debug-format}, @code{gdbserver} option
20846 The @option{--debug-format=option1[,option2,...]} option tells
20847 @code{gdbserver} to include additional information in each output.
20848 Possible options are:
20852 Turn off all extra information in debugging output.
20854 Turn on all extra information in debugging output.
20856 Include a timestamp in each line of debugging output.
20859 Options are processed in order. Thus, for example, if @option{none}
20860 appears last then no additional information is added to debugging output.
20862 @cindex @option{--wrapper}, @code{gdbserver} option
20863 The @option{--wrapper} option specifies a wrapper to launch programs
20864 for debugging. The option should be followed by the name of the
20865 wrapper, then any command-line arguments to pass to the wrapper, then
20866 @kbd{--} indicating the end of the wrapper arguments.
20868 @code{gdbserver} runs the specified wrapper program with a combined
20869 command line including the wrapper arguments, then the name of the
20870 program to debug, then any arguments to the program. The wrapper
20871 runs until it executes your program, and then @value{GDBN} gains control.
20873 You can use any program that eventually calls @code{execve} with
20874 its arguments as a wrapper. Several standard Unix utilities do
20875 this, e.g.@: @code{env} and @code{nohup}. Any Unix shell script ending
20876 with @code{exec "$@@"} will also work.
20878 For example, you can use @code{env} to pass an environment variable to
20879 the debugged program, without setting the variable in @code{gdbserver}'s
20883 $ gdbserver --wrapper env LD_PRELOAD=libtest.so -- :2222 ./testprog
20886 @cindex @option{--selftest}
20887 The @option{--selftest} option runs the self tests in @code{gdbserver}:
20890 $ gdbserver --selftest
20891 Ran 2 unit tests, 0 failed
20894 These tests are disabled in release.
20895 @subsection Connecting to @code{gdbserver}
20897 The basic procedure for connecting to the remote target is:
20901 Run @value{GDBN} on the host system.
20904 Make sure you have the necessary symbol files
20905 (@pxref{Host and target files}).
20906 Load symbols for your application using the @code{file} command before you
20907 connect. Use @code{set sysroot} to locate target libraries (unless your
20908 @value{GDBN} was compiled with the correct sysroot using
20909 @code{--with-sysroot}).
20912 Connect to your target (@pxref{Connecting,,Connecting to a Remote Target}).
20913 For TCP connections, you must start up @code{gdbserver} prior to using
20914 the @code{target} command. Otherwise you may get an error whose
20915 text depends on the host system, but which usually looks something like
20916 @samp{Connection refused}. Don't use the @code{load}
20917 command in @value{GDBN} when using @code{target remote} mode, since the
20918 program is already on the target.
20922 @anchor{Monitor Commands for gdbserver}
20923 @subsection Monitor Commands for @code{gdbserver}
20924 @cindex monitor commands, for @code{gdbserver}
20926 During a @value{GDBN} session using @code{gdbserver}, you can use the
20927 @code{monitor} command to send special requests to @code{gdbserver}.
20928 Here are the available commands.
20932 List the available monitor commands.
20934 @item monitor set debug 0
20935 @itemx monitor set debug 1
20936 Disable or enable general debugging messages.
20938 @item monitor set remote-debug 0
20939 @itemx monitor set remote-debug 1
20940 Disable or enable specific debugging messages associated with the remote
20941 protocol (@pxref{Remote Protocol}).
20943 @item monitor set debug-format option1@r{[},option2,...@r{]}
20944 Specify additional text to add to debugging messages.
20945 Possible options are:
20949 Turn off all extra information in debugging output.
20951 Turn on all extra information in debugging output.
20953 Include a timestamp in each line of debugging output.
20956 Options are processed in order. Thus, for example, if @option{none}
20957 appears last then no additional information is added to debugging output.
20959 @item monitor set libthread-db-search-path [PATH]
20960 @cindex gdbserver, search path for @code{libthread_db}
20961 When this command is issued, @var{path} is a colon-separated list of
20962 directories to search for @code{libthread_db} (@pxref{Threads,,set
20963 libthread-db-search-path}). If you omit @var{path},
20964 @samp{libthread-db-search-path} will be reset to its default value.
20966 The special entry @samp{$pdir} for @samp{libthread-db-search-path} is
20967 not supported in @code{gdbserver}.
20970 Tell gdbserver to exit immediately. This command should be followed by
20971 @code{disconnect} to close the debugging session. @code{gdbserver} will
20972 detach from any attached processes and kill any processes it created.
20973 Use @code{monitor exit} to terminate @code{gdbserver} at the end
20974 of a multi-process mode debug session.
20978 @subsection Tracepoints support in @code{gdbserver}
20979 @cindex tracepoints support in @code{gdbserver}
20981 On some targets, @code{gdbserver} supports tracepoints, fast
20982 tracepoints and static tracepoints.
20984 For fast or static tracepoints to work, a special library called the
20985 @dfn{in-process agent} (IPA), must be loaded in the inferior process.
20986 This library is built and distributed as an integral part of
20987 @code{gdbserver}. In addition, support for static tracepoints
20988 requires building the in-process agent library with static tracepoints
20989 support. At present, the UST (LTTng Userspace Tracer,
20990 @url{http://lttng.org/ust}) tracing engine is supported. This support
20991 is automatically available if UST development headers are found in the
20992 standard include path when @code{gdbserver} is built, or if
20993 @code{gdbserver} was explicitly configured using @option{--with-ust}
20994 to point at such headers. You can explicitly disable the support
20995 using @option{--with-ust=no}.
20997 There are several ways to load the in-process agent in your program:
21000 @item Specifying it as dependency at link time
21002 You can link your program dynamically with the in-process agent
21003 library. On most systems, this is accomplished by adding
21004 @code{-linproctrace} to the link command.
21006 @item Using the system's preloading mechanisms
21008 You can force loading the in-process agent at startup time by using
21009 your system's support for preloading shared libraries. Many Unixes
21010 support the concept of preloading user defined libraries. In most
21011 cases, you do that by specifying @code{LD_PRELOAD=libinproctrace.so}
21012 in the environment. See also the description of @code{gdbserver}'s
21013 @option{--wrapper} command line option.
21015 @item Using @value{GDBN} to force loading the agent at run time
21017 On some systems, you can force the inferior to load a shared library,
21018 by calling a dynamic loader function in the inferior that takes care
21019 of dynamically looking up and loading a shared library. On most Unix
21020 systems, the function is @code{dlopen}. You'll use the @code{call}
21021 command for that. For example:
21024 (@value{GDBP}) call dlopen ("libinproctrace.so", ...)
21027 Note that on most Unix systems, for the @code{dlopen} function to be
21028 available, the program needs to be linked with @code{-ldl}.
21031 On systems that have a userspace dynamic loader, like most Unix
21032 systems, when you connect to @code{gdbserver} using @code{target
21033 remote}, you'll find that the program is stopped at the dynamic
21034 loader's entry point, and no shared library has been loaded in the
21035 program's address space yet, including the in-process agent. In that
21036 case, before being able to use any of the fast or static tracepoints
21037 features, you need to let the loader run and load the shared
21038 libraries. The simplest way to do that is to run the program to the
21039 main procedure. E.g., if debugging a C or C@t{++} program, start
21040 @code{gdbserver} like so:
21043 $ gdbserver :9999 myprogram
21046 Start GDB and connect to @code{gdbserver} like so, and run to main:
21050 (@value{GDBP}) target remote myhost:9999
21051 0x00007f215893ba60 in ?? () from /lib64/ld-linux-x86-64.so.2
21052 (@value{GDBP}) b main
21053 (@value{GDBP}) continue
21056 The in-process tracing agent library should now be loaded into the
21057 process; you can confirm it with the @code{info sharedlibrary}
21058 command, which will list @file{libinproctrace.so} as loaded in the
21059 process. You are now ready to install fast tracepoints, list static
21060 tracepoint markers, probe static tracepoints markers, and start
21063 @node Remote Configuration
21064 @section Remote Configuration
21067 @kindex show remote
21068 This section documents the configuration options available when
21069 debugging remote programs. For the options related to the File I/O
21070 extensions of the remote protocol, see @ref{system,
21071 system-call-allowed}.
21074 @item set remoteaddresssize @var{bits}
21075 @cindex address size for remote targets
21076 @cindex bits in remote address
21077 Set the maximum size of address in a memory packet to the specified
21078 number of bits. @value{GDBN} will mask off the address bits above
21079 that number, when it passes addresses to the remote target. The
21080 default value is the number of bits in the target's address.
21082 @item show remoteaddresssize
21083 Show the current value of remote address size in bits.
21085 @item set serial baud @var{n}
21086 @cindex baud rate for remote targets
21087 Set the baud rate for the remote serial I/O to @var{n} baud. The
21088 value is used to set the speed of the serial port used for debugging
21091 @item show serial baud
21092 Show the current speed of the remote connection.
21094 @item set serial parity @var{parity}
21095 Set the parity for the remote serial I/O. Supported values of @var{parity} are:
21096 @code{even}, @code{none}, and @code{odd}. The default is @code{none}.
21098 @item show serial parity
21099 Show the current parity of the serial port.
21101 @item set remotebreak
21102 @cindex interrupt remote programs
21103 @cindex BREAK signal instead of Ctrl-C
21104 @anchor{set remotebreak}
21105 If set to on, @value{GDBN} sends a @code{BREAK} signal to the remote
21106 when you type @kbd{Ctrl-c} to interrupt the program running
21107 on the remote. If set to off, @value{GDBN} sends the @samp{Ctrl-C}
21108 character instead. The default is off, since most remote systems
21109 expect to see @samp{Ctrl-C} as the interrupt signal.
21111 @item show remotebreak
21112 Show whether @value{GDBN} sends @code{BREAK} or @samp{Ctrl-C} to
21113 interrupt the remote program.
21115 @item set remoteflow on
21116 @itemx set remoteflow off
21117 @kindex set remoteflow
21118 Enable or disable hardware flow control (@code{RTS}/@code{CTS})
21119 on the serial port used to communicate to the remote target.
21121 @item show remoteflow
21122 @kindex show remoteflow
21123 Show the current setting of hardware flow control.
21125 @item set remotelogbase @var{base}
21126 Set the base (a.k.a.@: radix) of logging serial protocol
21127 communications to @var{base}. Supported values of @var{base} are:
21128 @code{ascii}, @code{octal}, and @code{hex}. The default is
21131 @item show remotelogbase
21132 Show the current setting of the radix for logging remote serial
21135 @item set remotelogfile @var{file}
21136 @cindex record serial communications on file
21137 Record remote serial communications on the named @var{file}. The
21138 default is not to record at all.
21140 @item show remotelogfile.
21141 Show the current setting of the file name on which to record the
21142 serial communications.
21144 @item set remotetimeout @var{num}
21145 @cindex timeout for serial communications
21146 @cindex remote timeout
21147 Set the timeout limit to wait for the remote target to respond to
21148 @var{num} seconds. The default is 2 seconds.
21150 @item show remotetimeout
21151 Show the current number of seconds to wait for the remote target
21154 @cindex limit hardware breakpoints and watchpoints
21155 @cindex remote target, limit break- and watchpoints
21156 @anchor{set remote hardware-watchpoint-limit}
21157 @anchor{set remote hardware-breakpoint-limit}
21158 @item set remote hardware-watchpoint-limit @var{limit}
21159 @itemx set remote hardware-breakpoint-limit @var{limit}
21160 Restrict @value{GDBN} to using @var{limit} remote hardware breakpoint or
21161 watchpoints. A limit of -1, the default, is treated as unlimited.
21163 @cindex limit hardware watchpoints length
21164 @cindex remote target, limit watchpoints length
21165 @anchor{set remote hardware-watchpoint-length-limit}
21166 @item set remote hardware-watchpoint-length-limit @var{limit}
21167 Restrict @value{GDBN} to using @var{limit} bytes for the maximum length of
21168 a remote hardware watchpoint. A limit of -1, the default, is treated
21171 @item show remote hardware-watchpoint-length-limit
21172 Show the current limit (in bytes) of the maximum length of
21173 a remote hardware watchpoint.
21175 @item set remote exec-file @var{filename}
21176 @itemx show remote exec-file
21177 @anchor{set remote exec-file}
21178 @cindex executable file, for remote target
21179 Select the file used for @code{run} with @code{target
21180 extended-remote}. This should be set to a filename valid on the
21181 target system. If it is not set, the target will use a default
21182 filename (e.g.@: the last program run).
21184 @item set remote interrupt-sequence
21185 @cindex interrupt remote programs
21186 @cindex select Ctrl-C, BREAK or BREAK-g
21187 Allow the user to select one of @samp{Ctrl-C}, a @code{BREAK} or
21188 @samp{BREAK-g} as the
21189 sequence to the remote target in order to interrupt the execution.
21190 @samp{Ctrl-C} is a default. Some system prefers @code{BREAK} which
21191 is high level of serial line for some certain time.
21192 Linux kernel prefers @samp{BREAK-g}, a.k.a Magic SysRq g.
21193 It is @code{BREAK} signal followed by character @code{g}.
21195 @item show interrupt-sequence
21196 Show which of @samp{Ctrl-C}, @code{BREAK} or @code{BREAK-g}
21197 is sent by @value{GDBN} to interrupt the remote program.
21198 @code{BREAK-g} is BREAK signal followed by @code{g} and
21199 also known as Magic SysRq g.
21201 @item set remote interrupt-on-connect
21202 @cindex send interrupt-sequence on start
21203 Specify whether interrupt-sequence is sent to remote target when
21204 @value{GDBN} connects to it. This is mostly needed when you debug
21205 Linux kernel. Linux kernel expects @code{BREAK} followed by @code{g}
21206 which is known as Magic SysRq g in order to connect @value{GDBN}.
21208 @item show interrupt-on-connect
21209 Show whether interrupt-sequence is sent
21210 to remote target when @value{GDBN} connects to it.
21214 @item set tcp auto-retry on
21215 @cindex auto-retry, for remote TCP target
21216 Enable auto-retry for remote TCP connections. This is useful if the remote
21217 debugging agent is launched in parallel with @value{GDBN}; there is a race
21218 condition because the agent may not become ready to accept the connection
21219 before @value{GDBN} attempts to connect. When auto-retry is
21220 enabled, if the initial attempt to connect fails, @value{GDBN} reattempts
21221 to establish the connection using the timeout specified by
21222 @code{set tcp connect-timeout}.
21224 @item set tcp auto-retry off
21225 Do not auto-retry failed TCP connections.
21227 @item show tcp auto-retry
21228 Show the current auto-retry setting.
21230 @item set tcp connect-timeout @var{seconds}
21231 @itemx set tcp connect-timeout unlimited
21232 @cindex connection timeout, for remote TCP target
21233 @cindex timeout, for remote target connection
21234 Set the timeout for establishing a TCP connection to the remote target to
21235 @var{seconds}. The timeout affects both polling to retry failed connections
21236 (enabled by @code{set tcp auto-retry on}) and waiting for connections
21237 that are merely slow to complete, and represents an approximate cumulative
21238 value. If @var{seconds} is @code{unlimited}, there is no timeout and
21239 @value{GDBN} will keep attempting to establish a connection forever,
21240 unless interrupted with @kbd{Ctrl-c}. The default is 15 seconds.
21242 @item show tcp connect-timeout
21243 Show the current connection timeout setting.
21246 @cindex remote packets, enabling and disabling
21247 The @value{GDBN} remote protocol autodetects the packets supported by
21248 your debugging stub. If you need to override the autodetection, you
21249 can use these commands to enable or disable individual packets. Each
21250 packet can be set to @samp{on} (the remote target supports this
21251 packet), @samp{off} (the remote target does not support this packet),
21252 or @samp{auto} (detect remote target support for this packet). They
21253 all default to @samp{auto}. For more information about each packet,
21254 see @ref{Remote Protocol}.
21256 During normal use, you should not have to use any of these commands.
21257 If you do, that may be a bug in your remote debugging stub, or a bug
21258 in @value{GDBN}. You may want to report the problem to the
21259 @value{GDBN} developers.
21261 For each packet @var{name}, the command to enable or disable the
21262 packet is @code{set remote @var{name}-packet}. The available settings
21265 @multitable @columnfractions 0.28 0.32 0.25
21268 @tab Related Features
21270 @item @code{fetch-register}
21272 @tab @code{info registers}
21274 @item @code{set-register}
21278 @item @code{binary-download}
21280 @tab @code{load}, @code{set}
21282 @item @code{read-aux-vector}
21283 @tab @code{qXfer:auxv:read}
21284 @tab @code{info auxv}
21286 @item @code{symbol-lookup}
21287 @tab @code{qSymbol}
21288 @tab Detecting multiple threads
21290 @item @code{attach}
21291 @tab @code{vAttach}
21294 @item @code{verbose-resume}
21296 @tab Stepping or resuming multiple threads
21302 @item @code{software-breakpoint}
21306 @item @code{hardware-breakpoint}
21310 @item @code{write-watchpoint}
21314 @item @code{read-watchpoint}
21318 @item @code{access-watchpoint}
21322 @item @code{pid-to-exec-file}
21323 @tab @code{qXfer:exec-file:read}
21324 @tab @code{attach}, @code{run}
21326 @item @code{target-features}
21327 @tab @code{qXfer:features:read}
21328 @tab @code{set architecture}
21330 @item @code{library-info}
21331 @tab @code{qXfer:libraries:read}
21332 @tab @code{info sharedlibrary}
21334 @item @code{memory-map}
21335 @tab @code{qXfer:memory-map:read}
21336 @tab @code{info mem}
21338 @item @code{read-sdata-object}
21339 @tab @code{qXfer:sdata:read}
21340 @tab @code{print $_sdata}
21342 @item @code{read-spu-object}
21343 @tab @code{qXfer:spu:read}
21344 @tab @code{info spu}
21346 @item @code{write-spu-object}
21347 @tab @code{qXfer:spu:write}
21348 @tab @code{info spu}
21350 @item @code{read-siginfo-object}
21351 @tab @code{qXfer:siginfo:read}
21352 @tab @code{print $_siginfo}
21354 @item @code{write-siginfo-object}
21355 @tab @code{qXfer:siginfo:write}
21356 @tab @code{set $_siginfo}
21358 @item @code{threads}
21359 @tab @code{qXfer:threads:read}
21360 @tab @code{info threads}
21362 @item @code{get-thread-local-@*storage-address}
21363 @tab @code{qGetTLSAddr}
21364 @tab Displaying @code{__thread} variables
21366 @item @code{get-thread-information-block-address}
21367 @tab @code{qGetTIBAddr}
21368 @tab Display MS-Windows Thread Information Block.
21370 @item @code{search-memory}
21371 @tab @code{qSearch:memory}
21374 @item @code{supported-packets}
21375 @tab @code{qSupported}
21376 @tab Remote communications parameters
21378 @item @code{catch-syscalls}
21379 @tab @code{QCatchSyscalls}
21380 @tab @code{catch syscall}
21382 @item @code{pass-signals}
21383 @tab @code{QPassSignals}
21384 @tab @code{handle @var{signal}}
21386 @item @code{program-signals}
21387 @tab @code{QProgramSignals}
21388 @tab @code{handle @var{signal}}
21390 @item @code{hostio-close-packet}
21391 @tab @code{vFile:close}
21392 @tab @code{remote get}, @code{remote put}
21394 @item @code{hostio-open-packet}
21395 @tab @code{vFile:open}
21396 @tab @code{remote get}, @code{remote put}
21398 @item @code{hostio-pread-packet}
21399 @tab @code{vFile:pread}
21400 @tab @code{remote get}, @code{remote put}
21402 @item @code{hostio-pwrite-packet}
21403 @tab @code{vFile:pwrite}
21404 @tab @code{remote get}, @code{remote put}
21406 @item @code{hostio-unlink-packet}
21407 @tab @code{vFile:unlink}
21408 @tab @code{remote delete}
21410 @item @code{hostio-readlink-packet}
21411 @tab @code{vFile:readlink}
21414 @item @code{hostio-fstat-packet}
21415 @tab @code{vFile:fstat}
21418 @item @code{hostio-setfs-packet}
21419 @tab @code{vFile:setfs}
21422 @item @code{noack-packet}
21423 @tab @code{QStartNoAckMode}
21424 @tab Packet acknowledgment
21426 @item @code{osdata}
21427 @tab @code{qXfer:osdata:read}
21428 @tab @code{info os}
21430 @item @code{query-attached}
21431 @tab @code{qAttached}
21432 @tab Querying remote process attach state.
21434 @item @code{trace-buffer-size}
21435 @tab @code{QTBuffer:size}
21436 @tab @code{set trace-buffer-size}
21438 @item @code{trace-status}
21439 @tab @code{qTStatus}
21440 @tab @code{tstatus}
21442 @item @code{traceframe-info}
21443 @tab @code{qXfer:traceframe-info:read}
21444 @tab Traceframe info
21446 @item @code{install-in-trace}
21447 @tab @code{InstallInTrace}
21448 @tab Install tracepoint in tracing
21450 @item @code{disable-randomization}
21451 @tab @code{QDisableRandomization}
21452 @tab @code{set disable-randomization}
21454 @item @code{startup-with-shell}
21455 @tab @code{QStartupWithShell}
21456 @tab @code{set startup-with-shell}
21458 @item @code{environment-hex-encoded}
21459 @tab @code{QEnvironmentHexEncoded}
21460 @tab @code{set environment}
21462 @item @code{environment-unset}
21463 @tab @code{QEnvironmentUnset}
21464 @tab @code{unset environment}
21466 @item @code{environment-reset}
21467 @tab @code{QEnvironmentReset}
21468 @tab @code{Reset the inferior environment (i.e., unset user-set variables)}
21470 @item @code{set-working-dir}
21471 @tab @code{QSetWorkingDir}
21472 @tab @code{set cwd}
21474 @item @code{conditional-breakpoints-packet}
21475 @tab @code{Z0 and Z1}
21476 @tab @code{Support for target-side breakpoint condition evaluation}
21478 @item @code{multiprocess-extensions}
21479 @tab @code{multiprocess extensions}
21480 @tab Debug multiple processes and remote process PID awareness
21482 @item @code{swbreak-feature}
21483 @tab @code{swbreak stop reason}
21486 @item @code{hwbreak-feature}
21487 @tab @code{hwbreak stop reason}
21490 @item @code{fork-event-feature}
21491 @tab @code{fork stop reason}
21494 @item @code{vfork-event-feature}
21495 @tab @code{vfork stop reason}
21498 @item @code{exec-event-feature}
21499 @tab @code{exec stop reason}
21502 @item @code{thread-events}
21503 @tab @code{QThreadEvents}
21504 @tab Tracking thread lifetime.
21506 @item @code{no-resumed-stop-reply}
21507 @tab @code{no resumed thread left stop reply}
21508 @tab Tracking thread lifetime.
21513 @section Implementing a Remote Stub
21515 @cindex debugging stub, example
21516 @cindex remote stub, example
21517 @cindex stub example, remote debugging
21518 The stub files provided with @value{GDBN} implement the target side of the
21519 communication protocol, and the @value{GDBN} side is implemented in the
21520 @value{GDBN} source file @file{remote.c}. Normally, you can simply allow
21521 these subroutines to communicate, and ignore the details. (If you're
21522 implementing your own stub file, you can still ignore the details: start
21523 with one of the existing stub files. @file{sparc-stub.c} is the best
21524 organized, and therefore the easiest to read.)
21526 @cindex remote serial debugging, overview
21527 To debug a program running on another machine (the debugging
21528 @dfn{target} machine), you must first arrange for all the usual
21529 prerequisites for the program to run by itself. For example, for a C
21534 A startup routine to set up the C runtime environment; these usually
21535 have a name like @file{crt0}. The startup routine may be supplied by
21536 your hardware supplier, or you may have to write your own.
21539 A C subroutine library to support your program's
21540 subroutine calls, notably managing input and output.
21543 A way of getting your program to the other machine---for example, a
21544 download program. These are often supplied by the hardware
21545 manufacturer, but you may have to write your own from hardware
21549 The next step is to arrange for your program to use a serial port to
21550 communicate with the machine where @value{GDBN} is running (the @dfn{host}
21551 machine). In general terms, the scheme looks like this:
21555 @value{GDBN} already understands how to use this protocol; when everything
21556 else is set up, you can simply use the @samp{target remote} command
21557 (@pxref{Targets,,Specifying a Debugging Target}).
21559 @item On the target,
21560 you must link with your program a few special-purpose subroutines that
21561 implement the @value{GDBN} remote serial protocol. The file containing these
21562 subroutines is called a @dfn{debugging stub}.
21564 On certain remote targets, you can use an auxiliary program
21565 @code{gdbserver} instead of linking a stub into your program.
21566 @xref{Server,,Using the @code{gdbserver} Program}, for details.
21569 The debugging stub is specific to the architecture of the remote
21570 machine; for example, use @file{sparc-stub.c} to debug programs on
21573 @cindex remote serial stub list
21574 These working remote stubs are distributed with @value{GDBN}:
21579 @cindex @file{i386-stub.c}
21582 For Intel 386 and compatible architectures.
21585 @cindex @file{m68k-stub.c}
21586 @cindex Motorola 680x0
21588 For Motorola 680x0 architectures.
21591 @cindex @file{sh-stub.c}
21594 For Renesas SH architectures.
21597 @cindex @file{sparc-stub.c}
21599 For @sc{sparc} architectures.
21601 @item sparcl-stub.c
21602 @cindex @file{sparcl-stub.c}
21605 For Fujitsu @sc{sparclite} architectures.
21609 The @file{README} file in the @value{GDBN} distribution may list other
21610 recently added stubs.
21613 * Stub Contents:: What the stub can do for you
21614 * Bootstrapping:: What you must do for the stub
21615 * Debug Session:: Putting it all together
21618 @node Stub Contents
21619 @subsection What the Stub Can Do for You
21621 @cindex remote serial stub
21622 The debugging stub for your architecture supplies these three
21626 @item set_debug_traps
21627 @findex set_debug_traps
21628 @cindex remote serial stub, initialization
21629 This routine arranges for @code{handle_exception} to run when your
21630 program stops. You must call this subroutine explicitly in your
21631 program's startup code.
21633 @item handle_exception
21634 @findex handle_exception
21635 @cindex remote serial stub, main routine
21636 This is the central workhorse, but your program never calls it
21637 explicitly---the setup code arranges for @code{handle_exception} to
21638 run when a trap is triggered.
21640 @code{handle_exception} takes control when your program stops during
21641 execution (for example, on a breakpoint), and mediates communications
21642 with @value{GDBN} on the host machine. This is where the communications
21643 protocol is implemented; @code{handle_exception} acts as the @value{GDBN}
21644 representative on the target machine. It begins by sending summary
21645 information on the state of your program, then continues to execute,
21646 retrieving and transmitting any information @value{GDBN} needs, until you
21647 execute a @value{GDBN} command that makes your program resume; at that point,
21648 @code{handle_exception} returns control to your own code on the target
21652 @cindex @code{breakpoint} subroutine, remote
21653 Use this auxiliary subroutine to make your program contain a
21654 breakpoint. Depending on the particular situation, this may be the only
21655 way for @value{GDBN} to get control. For instance, if your target
21656 machine has some sort of interrupt button, you won't need to call this;
21657 pressing the interrupt button transfers control to
21658 @code{handle_exception}---in effect, to @value{GDBN}. On some machines,
21659 simply receiving characters on the serial port may also trigger a trap;
21660 again, in that situation, you don't need to call @code{breakpoint} from
21661 your own program---simply running @samp{target remote} from the host
21662 @value{GDBN} session gets control.
21664 Call @code{breakpoint} if none of these is true, or if you simply want
21665 to make certain your program stops at a predetermined point for the
21666 start of your debugging session.
21669 @node Bootstrapping
21670 @subsection What You Must Do for the Stub
21672 @cindex remote stub, support routines
21673 The debugging stubs that come with @value{GDBN} are set up for a particular
21674 chip architecture, but they have no information about the rest of your
21675 debugging target machine.
21677 First of all you need to tell the stub how to communicate with the
21681 @item int getDebugChar()
21682 @findex getDebugChar
21683 Write this subroutine to read a single character from the serial port.
21684 It may be identical to @code{getchar} for your target system; a
21685 different name is used to allow you to distinguish the two if you wish.
21687 @item void putDebugChar(int)
21688 @findex putDebugChar
21689 Write this subroutine to write a single character to the serial port.
21690 It may be identical to @code{putchar} for your target system; a
21691 different name is used to allow you to distinguish the two if you wish.
21694 @cindex control C, and remote debugging
21695 @cindex interrupting remote targets
21696 If you want @value{GDBN} to be able to stop your program while it is
21697 running, you need to use an interrupt-driven serial driver, and arrange
21698 for it to stop when it receives a @code{^C} (@samp{\003}, the control-C
21699 character). That is the character which @value{GDBN} uses to tell the
21700 remote system to stop.
21702 Getting the debugging target to return the proper status to @value{GDBN}
21703 probably requires changes to the standard stub; one quick and dirty way
21704 is to just execute a breakpoint instruction (the ``dirty'' part is that
21705 @value{GDBN} reports a @code{SIGTRAP} instead of a @code{SIGINT}).
21707 Other routines you need to supply are:
21710 @item void exceptionHandler (int @var{exception_number}, void *@var{exception_address})
21711 @findex exceptionHandler
21712 Write this function to install @var{exception_address} in the exception
21713 handling tables. You need to do this because the stub does not have any
21714 way of knowing what the exception handling tables on your target system
21715 are like (for example, the processor's table might be in @sc{rom},
21716 containing entries which point to a table in @sc{ram}).
21717 The @var{exception_number} specifies the exception which should be changed;
21718 its meaning is architecture-dependent (for example, different numbers
21719 might represent divide by zero, misaligned access, etc). When this
21720 exception occurs, control should be transferred directly to
21721 @var{exception_address}, and the processor state (stack, registers,
21722 and so on) should be just as it is when a processor exception occurs. So if
21723 you want to use a jump instruction to reach @var{exception_address}, it
21724 should be a simple jump, not a jump to subroutine.
21726 For the 386, @var{exception_address} should be installed as an interrupt
21727 gate so that interrupts are masked while the handler runs. The gate
21728 should be at privilege level 0 (the most privileged level). The
21729 @sc{sparc} and 68k stubs are able to mask interrupts themselves without
21730 help from @code{exceptionHandler}.
21732 @item void flush_i_cache()
21733 @findex flush_i_cache
21734 On @sc{sparc} and @sc{sparclite} only, write this subroutine to flush the
21735 instruction cache, if any, on your target machine. If there is no
21736 instruction cache, this subroutine may be a no-op.
21738 On target machines that have instruction caches, @value{GDBN} requires this
21739 function to make certain that the state of your program is stable.
21743 You must also make sure this library routine is available:
21746 @item void *memset(void *, int, int)
21748 This is the standard library function @code{memset} that sets an area of
21749 memory to a known value. If you have one of the free versions of
21750 @code{libc.a}, @code{memset} can be found there; otherwise, you must
21751 either obtain it from your hardware manufacturer, or write your own.
21754 If you do not use the GNU C compiler, you may need other standard
21755 library subroutines as well; this varies from one stub to another,
21756 but in general the stubs are likely to use any of the common library
21757 subroutines which @code{@value{NGCC}} generates as inline code.
21760 @node Debug Session
21761 @subsection Putting it All Together
21763 @cindex remote serial debugging summary
21764 In summary, when your program is ready to debug, you must follow these
21769 Make sure you have defined the supporting low-level routines
21770 (@pxref{Bootstrapping,,What You Must Do for the Stub}):
21772 @code{getDebugChar}, @code{putDebugChar},
21773 @code{flush_i_cache}, @code{memset}, @code{exceptionHandler}.
21777 Insert these lines in your program's startup code, before the main
21778 procedure is called:
21785 On some machines, when a breakpoint trap is raised, the hardware
21786 automatically makes the PC point to the instruction after the
21787 breakpoint. If your machine doesn't do that, you may need to adjust
21788 @code{handle_exception} to arrange for it to return to the instruction
21789 after the breakpoint on this first invocation, so that your program
21790 doesn't keep hitting the initial breakpoint instead of making
21794 For the 680x0 stub only, you need to provide a variable called
21795 @code{exceptionHook}. Normally you just use:
21798 void (*exceptionHook)() = 0;
21802 but if before calling @code{set_debug_traps}, you set it to point to a
21803 function in your program, that function is called when
21804 @code{@value{GDBN}} continues after stopping on a trap (for example, bus
21805 error). The function indicated by @code{exceptionHook} is called with
21806 one parameter: an @code{int} which is the exception number.
21809 Compile and link together: your program, the @value{GDBN} debugging stub for
21810 your target architecture, and the supporting subroutines.
21813 Make sure you have a serial connection between your target machine and
21814 the @value{GDBN} host, and identify the serial port on the host.
21817 @c The "remote" target now provides a `load' command, so we should
21818 @c document that. FIXME.
21819 Download your program to your target machine (or get it there by
21820 whatever means the manufacturer provides), and start it.
21823 Start @value{GDBN} on the host, and connect to the target
21824 (@pxref{Connecting,,Connecting to a Remote Target}).
21828 @node Configurations
21829 @chapter Configuration-Specific Information
21831 While nearly all @value{GDBN} commands are available for all native and
21832 cross versions of the debugger, there are some exceptions. This chapter
21833 describes things that are only available in certain configurations.
21835 There are three major categories of configurations: native
21836 configurations, where the host and target are the same, embedded
21837 operating system configurations, which are usually the same for several
21838 different processor architectures, and bare embedded processors, which
21839 are quite different from each other.
21844 * Embedded Processors::
21851 This section describes details specific to particular native
21855 * BSD libkvm Interface:: Debugging BSD kernel memory images
21856 * Process Information:: Process information
21857 * DJGPP Native:: Features specific to the DJGPP port
21858 * Cygwin Native:: Features specific to the Cygwin port
21859 * Hurd Native:: Features specific to @sc{gnu} Hurd
21860 * Darwin:: Features specific to Darwin
21863 @node BSD libkvm Interface
21864 @subsection BSD libkvm Interface
21867 @cindex kernel memory image
21868 @cindex kernel crash dump
21870 BSD-derived systems (FreeBSD/NetBSD/OpenBSD) have a kernel memory
21871 interface that provides a uniform interface for accessing kernel virtual
21872 memory images, including live systems and crash dumps. @value{GDBN}
21873 uses this interface to allow you to debug live kernels and kernel crash
21874 dumps on many native BSD configurations. This is implemented as a
21875 special @code{kvm} debugging target. For debugging a live system, load
21876 the currently running kernel into @value{GDBN} and connect to the
21880 (@value{GDBP}) @b{target kvm}
21883 For debugging crash dumps, provide the file name of the crash dump as an
21887 (@value{GDBP}) @b{target kvm /var/crash/bsd.0}
21890 Once connected to the @code{kvm} target, the following commands are
21896 Set current context from the @dfn{Process Control Block} (PCB) address.
21899 Set current context from proc address. This command isn't available on
21900 modern FreeBSD systems.
21903 @node Process Information
21904 @subsection Process Information
21906 @cindex examine process image
21907 @cindex process info via @file{/proc}
21909 Some operating systems provide interfaces to fetch additional
21910 information about running processes beyond memory and per-thread
21911 register state. If @value{GDBN} is configured for an operating system
21912 with a supported interface, the command @code{info proc} is available
21913 to report information about the process running your program, or about
21914 any process running on your system.
21916 One supported interface is a facility called @samp{/proc} that can be
21917 used to examine the image of a running process using file-system
21918 subroutines. This facility is supported on @sc{gnu}/Linux and Solaris
21921 On FreeBSD systems, system control nodes are used to query process
21924 In addition, some systems may provide additional process information
21925 in core files. Note that a core file may include a subset of the
21926 information available from a live process. Process information is
21927 currently avaiable from cores created on @sc{gnu}/Linux and FreeBSD
21934 @itemx info proc @var{process-id}
21935 Summarize available information about any running process. If a
21936 process ID is specified by @var{process-id}, display information about
21937 that process; otherwise display information about the program being
21938 debugged. The summary includes the debugged process ID, the command
21939 line used to invoke it, its current working directory, and its
21940 executable file's absolute file name.
21942 On some systems, @var{process-id} can be of the form
21943 @samp{[@var{pid}]/@var{tid}} which specifies a certain thread ID
21944 within a process. If the optional @var{pid} part is missing, it means
21945 a thread from the process being debugged (the leading @samp{/} still
21946 needs to be present, or else @value{GDBN} will interpret the number as
21947 a process ID rather than a thread ID).
21949 @item info proc cmdline
21950 @cindex info proc cmdline
21951 Show the original command line of the process. This command is
21952 supported on @sc{gnu}/Linux and FreeBSD.
21954 @item info proc cwd
21955 @cindex info proc cwd
21956 Show the current working directory of the process. This command is
21957 supported on @sc{gnu}/Linux and FreeBSD.
21959 @item info proc exe
21960 @cindex info proc exe
21961 Show the name of executable of the process. This command is supported
21962 on @sc{gnu}/Linux and FreeBSD.
21964 @item info proc mappings
21965 @cindex memory address space mappings
21966 Report the memory address space ranges accessible in the program. On
21967 Solaris and FreeBSD systems, each memory range includes information on
21968 whether the process has read, write, or execute access rights to each
21969 range. On @sc{gnu}/Linux and FreeBSD systems, each memory range
21970 includes the object file which is mapped to that range.
21972 @item info proc stat
21973 @itemx info proc status
21974 @cindex process detailed status information
21975 Show additional process-related information, including the user ID and
21976 group ID; virtual memory usage; the signals that are pending, blocked,
21977 and ignored; its TTY; its consumption of system and user time; its
21978 stack size; its @samp{nice} value; etc. These commands are supported
21979 on @sc{gnu}/Linux and FreeBSD.
21981 For @sc{gnu}/Linux systems, see the @samp{proc} man page for more
21982 information (type @kbd{man 5 proc} from your shell prompt).
21984 For FreeBSD systems, @code{info proc stat} is an alias for @code{info
21987 @item info proc all
21988 Show all the information about the process described under all of the
21989 above @code{info proc} subcommands.
21992 @comment These sub-options of 'info proc' were not included when
21993 @comment procfs.c was re-written. Keep their descriptions around
21994 @comment against the day when someone finds the time to put them back in.
21995 @kindex info proc times
21996 @item info proc times
21997 Starting time, user CPU time, and system CPU time for your program and
22000 @kindex info proc id
22002 Report on the process IDs related to your program: its own process ID,
22003 the ID of its parent, the process group ID, and the session ID.
22006 @item set procfs-trace
22007 @kindex set procfs-trace
22008 @cindex @code{procfs} API calls
22009 This command enables and disables tracing of @code{procfs} API calls.
22011 @item show procfs-trace
22012 @kindex show procfs-trace
22013 Show the current state of @code{procfs} API call tracing.
22015 @item set procfs-file @var{file}
22016 @kindex set procfs-file
22017 Tell @value{GDBN} to write @code{procfs} API trace to the named
22018 @var{file}. @value{GDBN} appends the trace info to the previous
22019 contents of the file. The default is to display the trace on the
22022 @item show procfs-file
22023 @kindex show procfs-file
22024 Show the file to which @code{procfs} API trace is written.
22026 @item proc-trace-entry
22027 @itemx proc-trace-exit
22028 @itemx proc-untrace-entry
22029 @itemx proc-untrace-exit
22030 @kindex proc-trace-entry
22031 @kindex proc-trace-exit
22032 @kindex proc-untrace-entry
22033 @kindex proc-untrace-exit
22034 These commands enable and disable tracing of entries into and exits
22035 from the @code{syscall} interface.
22038 @kindex info pidlist
22039 @cindex process list, QNX Neutrino
22040 For QNX Neutrino only, this command displays the list of all the
22041 processes and all the threads within each process.
22044 @kindex info meminfo
22045 @cindex mapinfo list, QNX Neutrino
22046 For QNX Neutrino only, this command displays the list of all mapinfos.
22050 @subsection Features for Debugging @sc{djgpp} Programs
22051 @cindex @sc{djgpp} debugging
22052 @cindex native @sc{djgpp} debugging
22053 @cindex MS-DOS-specific commands
22056 @sc{djgpp} is a port of the @sc{gnu} development tools to MS-DOS and
22057 MS-Windows. @sc{djgpp} programs are 32-bit protected-mode programs
22058 that use the @dfn{DPMI} (DOS Protected-Mode Interface) API to run on
22059 top of real-mode DOS systems and their emulations.
22061 @value{GDBN} supports native debugging of @sc{djgpp} programs, and
22062 defines a few commands specific to the @sc{djgpp} port. This
22063 subsection describes those commands.
22068 This is a prefix of @sc{djgpp}-specific commands which print
22069 information about the target system and important OS structures.
22072 @cindex MS-DOS system info
22073 @cindex free memory information (MS-DOS)
22074 @item info dos sysinfo
22075 This command displays assorted information about the underlying
22076 platform: the CPU type and features, the OS version and flavor, the
22077 DPMI version, and the available conventional and DPMI memory.
22082 @cindex segment descriptor tables
22083 @cindex descriptor tables display
22085 @itemx info dos ldt
22086 @itemx info dos idt
22087 These 3 commands display entries from, respectively, Global, Local,
22088 and Interrupt Descriptor Tables (GDT, LDT, and IDT). The descriptor
22089 tables are data structures which store a descriptor for each segment
22090 that is currently in use. The segment's selector is an index into a
22091 descriptor table; the table entry for that index holds the
22092 descriptor's base address and limit, and its attributes and access
22095 A typical @sc{djgpp} program uses 3 segments: a code segment, a data
22096 segment (used for both data and the stack), and a DOS segment (which
22097 allows access to DOS/BIOS data structures and absolute addresses in
22098 conventional memory). However, the DPMI host will usually define
22099 additional segments in order to support the DPMI environment.
22101 @cindex garbled pointers
22102 These commands allow to display entries from the descriptor tables.
22103 Without an argument, all entries from the specified table are
22104 displayed. An argument, which should be an integer expression, means
22105 display a single entry whose index is given by the argument. For
22106 example, here's a convenient way to display information about the
22107 debugged program's data segment:
22110 @exdent @code{(@value{GDBP}) info dos ldt $ds}
22111 @exdent @code{0x13f: base=0x11970000 limit=0x0009ffff 32-Bit Data (Read/Write, Exp-up)}
22115 This comes in handy when you want to see whether a pointer is outside
22116 the data segment's limit (i.e.@: @dfn{garbled}).
22118 @cindex page tables display (MS-DOS)
22120 @itemx info dos pte
22121 These two commands display entries from, respectively, the Page
22122 Directory and the Page Tables. Page Directories and Page Tables are
22123 data structures which control how virtual memory addresses are mapped
22124 into physical addresses. A Page Table includes an entry for every
22125 page of memory that is mapped into the program's address space; there
22126 may be several Page Tables, each one holding up to 4096 entries. A
22127 Page Directory has up to 4096 entries, one each for every Page Table
22128 that is currently in use.
22130 Without an argument, @kbd{info dos pde} displays the entire Page
22131 Directory, and @kbd{info dos pte} displays all the entries in all of
22132 the Page Tables. An argument, an integer expression, given to the
22133 @kbd{info dos pde} command means display only that entry from the Page
22134 Directory table. An argument given to the @kbd{info dos pte} command
22135 means display entries from a single Page Table, the one pointed to by
22136 the specified entry in the Page Directory.
22138 @cindex direct memory access (DMA) on MS-DOS
22139 These commands are useful when your program uses @dfn{DMA} (Direct
22140 Memory Access), which needs physical addresses to program the DMA
22143 These commands are supported only with some DPMI servers.
22145 @cindex physical address from linear address
22146 @item info dos address-pte @var{addr}
22147 This command displays the Page Table entry for a specified linear
22148 address. The argument @var{addr} is a linear address which should
22149 already have the appropriate segment's base address added to it,
22150 because this command accepts addresses which may belong to @emph{any}
22151 segment. For example, here's how to display the Page Table entry for
22152 the page where a variable @code{i} is stored:
22155 @exdent @code{(@value{GDBP}) info dos address-pte __djgpp_base_address + (char *)&i}
22156 @exdent @code{Page Table entry for address 0x11a00d30:}
22157 @exdent @code{Base=0x02698000 Dirty Acc. Not-Cached Write-Back Usr Read-Write +0xd30}
22161 This says that @code{i} is stored at offset @code{0xd30} from the page
22162 whose physical base address is @code{0x02698000}, and shows all the
22163 attributes of that page.
22165 Note that you must cast the addresses of variables to a @code{char *},
22166 since otherwise the value of @code{__djgpp_base_address}, the base
22167 address of all variables and functions in a @sc{djgpp} program, will
22168 be added using the rules of C pointer arithmetics: if @code{i} is
22169 declared an @code{int}, @value{GDBN} will add 4 times the value of
22170 @code{__djgpp_base_address} to the address of @code{i}.
22172 Here's another example, it displays the Page Table entry for the
22176 @exdent @code{(@value{GDBP}) info dos address-pte *((unsigned *)&_go32_info_block + 3)}
22177 @exdent @code{Page Table entry for address 0x29110:}
22178 @exdent @code{Base=0x00029000 Dirty Acc. Not-Cached Write-Back Usr Read-Write +0x110}
22182 (The @code{+ 3} offset is because the transfer buffer's address is the
22183 3rd member of the @code{_go32_info_block} structure.) The output
22184 clearly shows that this DPMI server maps the addresses in conventional
22185 memory 1:1, i.e.@: the physical (@code{0x00029000} + @code{0x110}) and
22186 linear (@code{0x29110}) addresses are identical.
22188 This command is supported only with some DPMI servers.
22191 @cindex DOS serial data link, remote debugging
22192 In addition to native debugging, the DJGPP port supports remote
22193 debugging via a serial data link. The following commands are specific
22194 to remote serial debugging in the DJGPP port of @value{GDBN}.
22197 @kindex set com1base
22198 @kindex set com1irq
22199 @kindex set com2base
22200 @kindex set com2irq
22201 @kindex set com3base
22202 @kindex set com3irq
22203 @kindex set com4base
22204 @kindex set com4irq
22205 @item set com1base @var{addr}
22206 This command sets the base I/O port address of the @file{COM1} serial
22209 @item set com1irq @var{irq}
22210 This command sets the @dfn{Interrupt Request} (@code{IRQ}) line to use
22211 for the @file{COM1} serial port.
22213 There are similar commands @samp{set com2base}, @samp{set com3irq},
22214 etc.@: for setting the port address and the @code{IRQ} lines for the
22217 @kindex show com1base
22218 @kindex show com1irq
22219 @kindex show com2base
22220 @kindex show com2irq
22221 @kindex show com3base
22222 @kindex show com3irq
22223 @kindex show com4base
22224 @kindex show com4irq
22225 The related commands @samp{show com1base}, @samp{show com1irq} etc.@:
22226 display the current settings of the base address and the @code{IRQ}
22227 lines used by the COM ports.
22230 @kindex info serial
22231 @cindex DOS serial port status
22232 This command prints the status of the 4 DOS serial ports. For each
22233 port, it prints whether it's active or not, its I/O base address and
22234 IRQ number, whether it uses a 16550-style FIFO, its baudrate, and the
22235 counts of various errors encountered so far.
22239 @node Cygwin Native
22240 @subsection Features for Debugging MS Windows PE Executables
22241 @cindex MS Windows debugging
22242 @cindex native Cygwin debugging
22243 @cindex Cygwin-specific commands
22245 @value{GDBN} supports native debugging of MS Windows programs, including
22246 DLLs with and without symbolic debugging information.
22248 @cindex Ctrl-BREAK, MS-Windows
22249 @cindex interrupt debuggee on MS-Windows
22250 MS-Windows programs that call @code{SetConsoleMode} to switch off the
22251 special meaning of the @samp{Ctrl-C} keystroke cannot be interrupted
22252 by typing @kbd{C-c}. For this reason, @value{GDBN} on MS-Windows
22253 supports @kbd{C-@key{BREAK}} as an alternative interrupt key
22254 sequence, which can be used to interrupt the debuggee even if it
22257 There are various additional Cygwin-specific commands, described in
22258 this section. Working with DLLs that have no debugging symbols is
22259 described in @ref{Non-debug DLL Symbols}.
22264 This is a prefix of MS Windows-specific commands which print
22265 information about the target system and important OS structures.
22267 @item info w32 selector
22268 This command displays information returned by
22269 the Win32 API @code{GetThreadSelectorEntry} function.
22270 It takes an optional argument that is evaluated to
22271 a long value to give the information about this given selector.
22272 Without argument, this command displays information
22273 about the six segment registers.
22275 @item info w32 thread-information-block
22276 This command displays thread specific information stored in the
22277 Thread Information Block (readable on the X86 CPU family using @code{$fs}
22278 selector for 32-bit programs and @code{$gs} for 64-bit programs).
22280 @kindex signal-event
22281 @item signal-event @var{id}
22282 This command signals an event with user-provided @var{id}. Used to resume
22283 crashing process when attached to it using MS-Windows JIT debugging (AeDebug).
22285 To use it, create or edit the following keys in
22286 @code{HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AeDebug} and/or
22287 @code{HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion\AeDebug}
22288 (for x86_64 versions):
22292 @code{Debugger} (REG_SZ) --- a command to launch the debugger.
22293 Suggested command is: @code{@var{fully-qualified-path-to-gdb.exe} -ex
22294 "attach %ld" -ex "signal-event %ld" -ex "continue"}.
22296 The first @code{%ld} will be replaced by the process ID of the
22297 crashing process, the second @code{%ld} will be replaced by the ID of
22298 the event that blocks the crashing process, waiting for @value{GDBN}
22302 @code{Auto} (REG_SZ) --- either @code{1} or @code{0}. @code{1} will
22303 make the system run debugger specified by the Debugger key
22304 automatically, @code{0} will cause a dialog box with ``OK'' and
22305 ``Cancel'' buttons to appear, which allows the user to either
22306 terminate the crashing process (OK) or debug it (Cancel).
22309 @kindex set cygwin-exceptions
22310 @cindex debugging the Cygwin DLL
22311 @cindex Cygwin DLL, debugging
22312 @item set cygwin-exceptions @var{mode}
22313 If @var{mode} is @code{on}, @value{GDBN} will break on exceptions that
22314 happen inside the Cygwin DLL. If @var{mode} is @code{off},
22315 @value{GDBN} will delay recognition of exceptions, and may ignore some
22316 exceptions which seem to be caused by internal Cygwin DLL
22317 ``bookkeeping''. This option is meant primarily for debugging the
22318 Cygwin DLL itself; the default value is @code{off} to avoid annoying
22319 @value{GDBN} users with false @code{SIGSEGV} signals.
22321 @kindex show cygwin-exceptions
22322 @item show cygwin-exceptions
22323 Displays whether @value{GDBN} will break on exceptions that happen
22324 inside the Cygwin DLL itself.
22326 @kindex set new-console
22327 @item set new-console @var{mode}
22328 If @var{mode} is @code{on} the debuggee will
22329 be started in a new console on next start.
22330 If @var{mode} is @code{off}, the debuggee will
22331 be started in the same console as the debugger.
22333 @kindex show new-console
22334 @item show new-console
22335 Displays whether a new console is used
22336 when the debuggee is started.
22338 @kindex set new-group
22339 @item set new-group @var{mode}
22340 This boolean value controls whether the debuggee should
22341 start a new group or stay in the same group as the debugger.
22342 This affects the way the Windows OS handles
22345 @kindex show new-group
22346 @item show new-group
22347 Displays current value of new-group boolean.
22349 @kindex set debugevents
22350 @item set debugevents
22351 This boolean value adds debug output concerning kernel events related
22352 to the debuggee seen by the debugger. This includes events that
22353 signal thread and process creation and exit, DLL loading and
22354 unloading, console interrupts, and debugging messages produced by the
22355 Windows @code{OutputDebugString} API call.
22357 @kindex set debugexec
22358 @item set debugexec
22359 This boolean value adds debug output concerning execute events
22360 (such as resume thread) seen by the debugger.
22362 @kindex set debugexceptions
22363 @item set debugexceptions
22364 This boolean value adds debug output concerning exceptions in the
22365 debuggee seen by the debugger.
22367 @kindex set debugmemory
22368 @item set debugmemory
22369 This boolean value adds debug output concerning debuggee memory reads
22370 and writes by the debugger.
22374 This boolean values specifies whether the debuggee is called
22375 via a shell or directly (default value is on).
22379 Displays if the debuggee will be started with a shell.
22384 * Non-debug DLL Symbols:: Support for DLLs without debugging symbols
22387 @node Non-debug DLL Symbols
22388 @subsubsection Support for DLLs without Debugging Symbols
22389 @cindex DLLs with no debugging symbols
22390 @cindex Minimal symbols and DLLs
22392 Very often on windows, some of the DLLs that your program relies on do
22393 not include symbolic debugging information (for example,
22394 @file{kernel32.dll}). When @value{GDBN} doesn't recognize any debugging
22395 symbols in a DLL, it relies on the minimal amount of symbolic
22396 information contained in the DLL's export table. This section
22397 describes working with such symbols, known internally to @value{GDBN} as
22398 ``minimal symbols''.
22400 Note that before the debugged program has started execution, no DLLs
22401 will have been loaded. The easiest way around this problem is simply to
22402 start the program --- either by setting a breakpoint or letting the
22403 program run once to completion.
22405 @subsubsection DLL Name Prefixes
22407 In keeping with the naming conventions used by the Microsoft debugging
22408 tools, DLL export symbols are made available with a prefix based on the
22409 DLL name, for instance @code{KERNEL32!CreateFileA}. The plain name is
22410 also entered into the symbol table, so @code{CreateFileA} is often
22411 sufficient. In some cases there will be name clashes within a program
22412 (particularly if the executable itself includes full debugging symbols)
22413 necessitating the use of the fully qualified name when referring to the
22414 contents of the DLL. Use single-quotes around the name to avoid the
22415 exclamation mark (``!'') being interpreted as a language operator.
22417 Note that the internal name of the DLL may be all upper-case, even
22418 though the file name of the DLL is lower-case, or vice-versa. Since
22419 symbols within @value{GDBN} are @emph{case-sensitive} this may cause
22420 some confusion. If in doubt, try the @code{info functions} and
22421 @code{info variables} commands or even @code{maint print msymbols}
22422 (@pxref{Symbols}). Here's an example:
22425 (@value{GDBP}) info function CreateFileA
22426 All functions matching regular expression "CreateFileA":
22428 Non-debugging symbols:
22429 0x77e885f4 CreateFileA
22430 0x77e885f4 KERNEL32!CreateFileA
22434 (@value{GDBP}) info function !
22435 All functions matching regular expression "!":
22437 Non-debugging symbols:
22438 0x6100114c cygwin1!__assert
22439 0x61004034 cygwin1!_dll_crt0@@0
22440 0x61004240 cygwin1!dll_crt0(per_process *)
22444 @subsubsection Working with Minimal Symbols
22446 Symbols extracted from a DLL's export table do not contain very much
22447 type information. All that @value{GDBN} can do is guess whether a symbol
22448 refers to a function or variable depending on the linker section that
22449 contains the symbol. Also note that the actual contents of the memory
22450 contained in a DLL are not available unless the program is running. This
22451 means that you cannot examine the contents of a variable or disassemble
22452 a function within a DLL without a running program.
22454 Variables are generally treated as pointers and dereferenced
22455 automatically. For this reason, it is often necessary to prefix a
22456 variable name with the address-of operator (``&'') and provide explicit
22457 type information in the command. Here's an example of the type of
22461 (@value{GDBP}) print 'cygwin1!__argv'
22462 'cygwin1!__argv' has unknown type; cast it to its declared type
22466 (@value{GDBP}) x 'cygwin1!__argv'
22467 'cygwin1!__argv' has unknown type; cast it to its declared type
22470 And two possible solutions:
22473 (@value{GDBP}) print ((char **)'cygwin1!__argv')[0]
22474 $2 = 0x22fd98 "/cygdrive/c/mydirectory/myprogram"
22478 (@value{GDBP}) x/2x &'cygwin1!__argv'
22479 0x610c0aa8 <cygwin1!__argv>: 0x10021608 0x00000000
22480 (@value{GDBP}) x/x 0x10021608
22481 0x10021608: 0x0022fd98
22482 (@value{GDBP}) x/s 0x0022fd98
22483 0x22fd98: "/cygdrive/c/mydirectory/myprogram"
22486 Setting a break point within a DLL is possible even before the program
22487 starts execution. However, under these circumstances, @value{GDBN} can't
22488 examine the initial instructions of the function in order to skip the
22489 function's frame set-up code. You can work around this by using ``*&''
22490 to set the breakpoint at a raw memory address:
22493 (@value{GDBP}) break *&'python22!PyOS_Readline'
22494 Breakpoint 1 at 0x1e04eff0
22497 The author of these extensions is not entirely convinced that setting a
22498 break point within a shared DLL like @file{kernel32.dll} is completely
22502 @subsection Commands Specific to @sc{gnu} Hurd Systems
22503 @cindex @sc{gnu} Hurd debugging
22505 This subsection describes @value{GDBN} commands specific to the
22506 @sc{gnu} Hurd native debugging.
22511 @kindex set signals@r{, Hurd command}
22512 @kindex set sigs@r{, Hurd command}
22513 This command toggles the state of inferior signal interception by
22514 @value{GDBN}. Mach exceptions, such as breakpoint traps, are not
22515 affected by this command. @code{sigs} is a shorthand alias for
22520 @kindex show signals@r{, Hurd command}
22521 @kindex show sigs@r{, Hurd command}
22522 Show the current state of intercepting inferior's signals.
22524 @item set signal-thread
22525 @itemx set sigthread
22526 @kindex set signal-thread
22527 @kindex set sigthread
22528 This command tells @value{GDBN} which thread is the @code{libc} signal
22529 thread. That thread is run when a signal is delivered to a running
22530 process. @code{set sigthread} is the shorthand alias of @code{set
22533 @item show signal-thread
22534 @itemx show sigthread
22535 @kindex show signal-thread
22536 @kindex show sigthread
22537 These two commands show which thread will run when the inferior is
22538 delivered a signal.
22541 @kindex set stopped@r{, Hurd command}
22542 This commands tells @value{GDBN} that the inferior process is stopped,
22543 as with the @code{SIGSTOP} signal. The stopped process can be
22544 continued by delivering a signal to it.
22547 @kindex show stopped@r{, Hurd command}
22548 This command shows whether @value{GDBN} thinks the debuggee is
22551 @item set exceptions
22552 @kindex set exceptions@r{, Hurd command}
22553 Use this command to turn off trapping of exceptions in the inferior.
22554 When exception trapping is off, neither breakpoints nor
22555 single-stepping will work. To restore the default, set exception
22558 @item show exceptions
22559 @kindex show exceptions@r{, Hurd command}
22560 Show the current state of trapping exceptions in the inferior.
22562 @item set task pause
22563 @kindex set task@r{, Hurd commands}
22564 @cindex task attributes (@sc{gnu} Hurd)
22565 @cindex pause current task (@sc{gnu} Hurd)
22566 This command toggles task suspension when @value{GDBN} has control.
22567 Setting it to on takes effect immediately, and the task is suspended
22568 whenever @value{GDBN} gets control. Setting it to off will take
22569 effect the next time the inferior is continued. If this option is set
22570 to off, you can use @code{set thread default pause on} or @code{set
22571 thread pause on} (see below) to pause individual threads.
22573 @item show task pause
22574 @kindex show task@r{, Hurd commands}
22575 Show the current state of task suspension.
22577 @item set task detach-suspend-count
22578 @cindex task suspend count
22579 @cindex detach from task, @sc{gnu} Hurd
22580 This command sets the suspend count the task will be left with when
22581 @value{GDBN} detaches from it.
22583 @item show task detach-suspend-count
22584 Show the suspend count the task will be left with when detaching.
22586 @item set task exception-port
22587 @itemx set task excp
22588 @cindex task exception port, @sc{gnu} Hurd
22589 This command sets the task exception port to which @value{GDBN} will
22590 forward exceptions. The argument should be the value of the @dfn{send
22591 rights} of the task. @code{set task excp} is a shorthand alias.
22593 @item set noninvasive
22594 @cindex noninvasive task options
22595 This command switches @value{GDBN} to a mode that is the least
22596 invasive as far as interfering with the inferior is concerned. This
22597 is the same as using @code{set task pause}, @code{set exceptions}, and
22598 @code{set signals} to values opposite to the defaults.
22600 @item info send-rights
22601 @itemx info receive-rights
22602 @itemx info port-rights
22603 @itemx info port-sets
22604 @itemx info dead-names
22607 @cindex send rights, @sc{gnu} Hurd
22608 @cindex receive rights, @sc{gnu} Hurd
22609 @cindex port rights, @sc{gnu} Hurd
22610 @cindex port sets, @sc{gnu} Hurd
22611 @cindex dead names, @sc{gnu} Hurd
22612 These commands display information about, respectively, send rights,
22613 receive rights, port rights, port sets, and dead names of a task.
22614 There are also shorthand aliases: @code{info ports} for @code{info
22615 port-rights} and @code{info psets} for @code{info port-sets}.
22617 @item set thread pause
22618 @kindex set thread@r{, Hurd command}
22619 @cindex thread properties, @sc{gnu} Hurd
22620 @cindex pause current thread (@sc{gnu} Hurd)
22621 This command toggles current thread suspension when @value{GDBN} has
22622 control. Setting it to on takes effect immediately, and the current
22623 thread is suspended whenever @value{GDBN} gets control. Setting it to
22624 off will take effect the next time the inferior is continued.
22625 Normally, this command has no effect, since when @value{GDBN} has
22626 control, the whole task is suspended. However, if you used @code{set
22627 task pause off} (see above), this command comes in handy to suspend
22628 only the current thread.
22630 @item show thread pause
22631 @kindex show thread@r{, Hurd command}
22632 This command shows the state of current thread suspension.
22634 @item set thread run
22635 This command sets whether the current thread is allowed to run.
22637 @item show thread run
22638 Show whether the current thread is allowed to run.
22640 @item set thread detach-suspend-count
22641 @cindex thread suspend count, @sc{gnu} Hurd
22642 @cindex detach from thread, @sc{gnu} Hurd
22643 This command sets the suspend count @value{GDBN} will leave on a
22644 thread when detaching. This number is relative to the suspend count
22645 found by @value{GDBN} when it notices the thread; use @code{set thread
22646 takeover-suspend-count} to force it to an absolute value.
22648 @item show thread detach-suspend-count
22649 Show the suspend count @value{GDBN} will leave on the thread when
22652 @item set thread exception-port
22653 @itemx set thread excp
22654 Set the thread exception port to which to forward exceptions. This
22655 overrides the port set by @code{set task exception-port} (see above).
22656 @code{set thread excp} is the shorthand alias.
22658 @item set thread takeover-suspend-count
22659 Normally, @value{GDBN}'s thread suspend counts are relative to the
22660 value @value{GDBN} finds when it notices each thread. This command
22661 changes the suspend counts to be absolute instead.
22663 @item set thread default
22664 @itemx show thread default
22665 @cindex thread default settings, @sc{gnu} Hurd
22666 Each of the above @code{set thread} commands has a @code{set thread
22667 default} counterpart (e.g., @code{set thread default pause}, @code{set
22668 thread default exception-port}, etc.). The @code{thread default}
22669 variety of commands sets the default thread properties for all
22670 threads; you can then change the properties of individual threads with
22671 the non-default commands.
22678 @value{GDBN} provides the following commands specific to the Darwin target:
22681 @item set debug darwin @var{num}
22682 @kindex set debug darwin
22683 When set to a non zero value, enables debugging messages specific to
22684 the Darwin support. Higher values produce more verbose output.
22686 @item show debug darwin
22687 @kindex show debug darwin
22688 Show the current state of Darwin messages.
22690 @item set debug mach-o @var{num}
22691 @kindex set debug mach-o
22692 When set to a non zero value, enables debugging messages while
22693 @value{GDBN} is reading Darwin object files. (@dfn{Mach-O} is the
22694 file format used on Darwin for object and executable files.) Higher
22695 values produce more verbose output. This is a command to diagnose
22696 problems internal to @value{GDBN} and should not be needed in normal
22699 @item show debug mach-o
22700 @kindex show debug mach-o
22701 Show the current state of Mach-O file messages.
22703 @item set mach-exceptions on
22704 @itemx set mach-exceptions off
22705 @kindex set mach-exceptions
22706 On Darwin, faults are first reported as a Mach exception and are then
22707 mapped to a Posix signal. Use this command to turn on trapping of
22708 Mach exceptions in the inferior. This might be sometimes useful to
22709 better understand the cause of a fault. The default is off.
22711 @item show mach-exceptions
22712 @kindex show mach-exceptions
22713 Show the current state of exceptions trapping.
22718 @section Embedded Operating Systems
22720 This section describes configurations involving the debugging of
22721 embedded operating systems that are available for several different
22724 @value{GDBN} includes the ability to debug programs running on
22725 various real-time operating systems.
22727 @node Embedded Processors
22728 @section Embedded Processors
22730 This section goes into details specific to particular embedded
22733 @cindex send command to simulator
22734 Whenever a specific embedded processor has a simulator, @value{GDBN}
22735 allows to send an arbitrary command to the simulator.
22738 @item sim @var{command}
22739 @kindex sim@r{, a command}
22740 Send an arbitrary @var{command} string to the simulator. Consult the
22741 documentation for the specific simulator in use for information about
22742 acceptable commands.
22747 * ARC:: Synopsys ARC
22749 * M68K:: Motorola M68K
22750 * MicroBlaze:: Xilinx MicroBlaze
22751 * MIPS Embedded:: MIPS Embedded
22752 * OpenRISC 1000:: OpenRISC 1000 (or1k)
22753 * PowerPC Embedded:: PowerPC Embedded
22756 * Super-H:: Renesas Super-H
22760 @subsection Synopsys ARC
22761 @cindex Synopsys ARC
22762 @cindex ARC specific commands
22768 @value{GDBN} provides the following ARC-specific commands:
22771 @item set debug arc
22772 @kindex set debug arc
22773 Control the level of ARC specific debug messages. Use 0 for no messages (the
22774 default), 1 for debug messages, and 2 for even more debug messages.
22776 @item show debug arc
22777 @kindex show debug arc
22778 Show the level of ARC specific debugging in operation.
22780 @item maint print arc arc-instruction @var{address}
22781 @kindex maint print arc arc-instruction
22782 Print internal disassembler information about instruction at a given address.
22789 @value{GDBN} provides the following ARM-specific commands:
22792 @item set arm disassembler
22794 This commands selects from a list of disassembly styles. The
22795 @code{"std"} style is the standard style.
22797 @item show arm disassembler
22799 Show the current disassembly style.
22801 @item set arm apcs32
22802 @cindex ARM 32-bit mode
22803 This command toggles ARM operation mode between 32-bit and 26-bit.
22805 @item show arm apcs32
22806 Display the current usage of the ARM 32-bit mode.
22808 @item set arm fpu @var{fputype}
22809 This command sets the ARM floating-point unit (FPU) type. The
22810 argument @var{fputype} can be one of these:
22814 Determine the FPU type by querying the OS ABI.
22816 Software FPU, with mixed-endian doubles on little-endian ARM
22819 GCC-compiled FPA co-processor.
22821 Software FPU with pure-endian doubles.
22827 Show the current type of the FPU.
22830 This command forces @value{GDBN} to use the specified ABI.
22833 Show the currently used ABI.
22835 @item set arm fallback-mode (arm|thumb|auto)
22836 @value{GDBN} uses the symbol table, when available, to determine
22837 whether instructions are ARM or Thumb. This command controls
22838 @value{GDBN}'s default behavior when the symbol table is not
22839 available. The default is @samp{auto}, which causes @value{GDBN} to
22840 use the current execution mode (from the @code{T} bit in the @code{CPSR}
22843 @item show arm fallback-mode
22844 Show the current fallback instruction mode.
22846 @item set arm force-mode (arm|thumb|auto)
22847 This command overrides use of the symbol table to determine whether
22848 instructions are ARM or Thumb. The default is @samp{auto}, which
22849 causes @value{GDBN} to use the symbol table and then the setting
22850 of @samp{set arm fallback-mode}.
22852 @item show arm force-mode
22853 Show the current forced instruction mode.
22855 @item set debug arm
22856 Toggle whether to display ARM-specific debugging messages from the ARM
22857 target support subsystem.
22859 @item show debug arm
22860 Show whether ARM-specific debugging messages are enabled.
22864 @item target sim @r{[}@var{simargs}@r{]} @dots{}
22865 The @value{GDBN} ARM simulator accepts the following optional arguments.
22868 @item --swi-support=@var{type}
22869 Tell the simulator which SWI interfaces to support. The argument
22870 @var{type} may be a comma separated list of the following values.
22871 The default value is @code{all}.
22886 The Motorola m68k configuration includes ColdFire support.
22889 @subsection MicroBlaze
22890 @cindex Xilinx MicroBlaze
22891 @cindex XMD, Xilinx Microprocessor Debugger
22893 The MicroBlaze is a soft-core processor supported on various Xilinx
22894 FPGAs, such as Spartan or Virtex series. Boards with these processors
22895 usually have JTAG ports which connect to a host system running the Xilinx
22896 Embedded Development Kit (EDK) or Software Development Kit (SDK).
22897 This host system is used to download the configuration bitstream to
22898 the target FPGA. The Xilinx Microprocessor Debugger (XMD) program
22899 communicates with the target board using the JTAG interface and
22900 presents a @code{gdbserver} interface to the board. By default
22901 @code{xmd} uses port @code{1234}. (While it is possible to change
22902 this default port, it requires the use of undocumented @code{xmd}
22903 commands. Contact Xilinx support if you need to do this.)
22905 Use these GDB commands to connect to the MicroBlaze target processor.
22908 @item target remote :1234
22909 Use this command to connect to the target if you are running @value{GDBN}
22910 on the same system as @code{xmd}.
22912 @item target remote @var{xmd-host}:1234
22913 Use this command to connect to the target if it is connected to @code{xmd}
22914 running on a different system named @var{xmd-host}.
22917 Use this command to download a program to the MicroBlaze target.
22919 @item set debug microblaze @var{n}
22920 Enable MicroBlaze-specific debugging messages if non-zero.
22922 @item show debug microblaze @var{n}
22923 Show MicroBlaze-specific debugging level.
22926 @node MIPS Embedded
22927 @subsection @acronym{MIPS} Embedded
22930 @value{GDBN} supports these special commands for @acronym{MIPS} targets:
22933 @item set mipsfpu double
22934 @itemx set mipsfpu single
22935 @itemx set mipsfpu none
22936 @itemx set mipsfpu auto
22937 @itemx show mipsfpu
22938 @kindex set mipsfpu
22939 @kindex show mipsfpu
22940 @cindex @acronym{MIPS} remote floating point
22941 @cindex floating point, @acronym{MIPS} remote
22942 If your target board does not support the @acronym{MIPS} floating point
22943 coprocessor, you should use the command @samp{set mipsfpu none} (if you
22944 need this, you may wish to put the command in your @value{GDBN} init
22945 file). This tells @value{GDBN} how to find the return value of
22946 functions which return floating point values. It also allows
22947 @value{GDBN} to avoid saving the floating point registers when calling
22948 functions on the board. If you are using a floating point coprocessor
22949 with only single precision floating point support, as on the @sc{r4650}
22950 processor, use the command @samp{set mipsfpu single}. The default
22951 double precision floating point coprocessor may be selected using
22952 @samp{set mipsfpu double}.
22954 In previous versions the only choices were double precision or no
22955 floating point, so @samp{set mipsfpu on} will select double precision
22956 and @samp{set mipsfpu off} will select no floating point.
22958 As usual, you can inquire about the @code{mipsfpu} variable with
22959 @samp{show mipsfpu}.
22962 @node OpenRISC 1000
22963 @subsection OpenRISC 1000
22964 @cindex OpenRISC 1000
22967 The OpenRISC 1000 provides a free RISC instruction set architecture. It is
22968 mainly provided as a soft-core which can run on Xilinx, Altera and other
22971 @value{GDBN} for OpenRISC supports the below commands when connecting to
22979 Runs the builtin CPU simulator which can run very basic
22980 programs but does not support most hardware functions like MMU.
22981 For more complex use cases the user is advised to run an external
22982 target, and connect using @samp{target remote}.
22984 Example: @code{target sim}
22986 @item set debug or1k
22987 Toggle whether to display OpenRISC-specific debugging messages from the
22988 OpenRISC target support subsystem.
22990 @item show debug or1k
22991 Show whether OpenRISC-specific debugging messages are enabled.
22994 @node PowerPC Embedded
22995 @subsection PowerPC Embedded
22997 @cindex DVC register
22998 @value{GDBN} supports using the DVC (Data Value Compare) register to
22999 implement in hardware simple hardware watchpoint conditions of the form:
23002 (@value{GDBP}) watch @var{ADDRESS|VARIABLE} \
23003 if @var{ADDRESS|VARIABLE} == @var{CONSTANT EXPRESSION}
23006 The DVC register will be automatically used when @value{GDBN} detects
23007 such pattern in a condition expression, and the created watchpoint uses one
23008 debug register (either the @code{exact-watchpoints} option is on and the
23009 variable is scalar, or the variable has a length of one byte). This feature
23010 is available in native @value{GDBN} running on a Linux kernel version 2.6.34
23013 When running on PowerPC embedded processors, @value{GDBN} automatically uses
23014 ranged hardware watchpoints, unless the @code{exact-watchpoints} option is on,
23015 in which case watchpoints using only one debug register are created when
23016 watching variables of scalar types.
23018 You can create an artificial array to watch an arbitrary memory
23019 region using one of the following commands (@pxref{Expressions}):
23022 (@value{GDBP}) watch *((char *) @var{address})@@@var{length}
23023 (@value{GDBP}) watch @{char[@var{length}]@} @var{address}
23026 PowerPC embedded processors support masked watchpoints. See the discussion
23027 about the @code{mask} argument in @ref{Set Watchpoints}.
23029 @cindex ranged breakpoint
23030 PowerPC embedded processors support hardware accelerated
23031 @dfn{ranged breakpoints}. A ranged breakpoint stops execution of
23032 the inferior whenever it executes an instruction at any address within
23033 the range it specifies. To set a ranged breakpoint in @value{GDBN},
23034 use the @code{break-range} command.
23036 @value{GDBN} provides the following PowerPC-specific commands:
23039 @kindex break-range
23040 @item break-range @var{start-location}, @var{end-location}
23041 Set a breakpoint for an address range given by
23042 @var{start-location} and @var{end-location}, which can specify a function name,
23043 a line number, an offset of lines from the current line or from the start
23044 location, or an address of an instruction (see @ref{Specify Location},
23045 for a list of all the possible ways to specify a @var{location}.)
23046 The breakpoint will stop execution of the inferior whenever it
23047 executes an instruction at any address within the specified range,
23048 (including @var{start-location} and @var{end-location}.)
23050 @kindex set powerpc
23051 @item set powerpc soft-float
23052 @itemx show powerpc soft-float
23053 Force @value{GDBN} to use (or not use) a software floating point calling
23054 convention. By default, @value{GDBN} selects the calling convention based
23055 on the selected architecture and the provided executable file.
23057 @item set powerpc vector-abi
23058 @itemx show powerpc vector-abi
23059 Force @value{GDBN} to use the specified calling convention for vector
23060 arguments and return values. The valid options are @samp{auto};
23061 @samp{generic}, to avoid vector registers even if they are present;
23062 @samp{altivec}, to use AltiVec registers; and @samp{spe} to use SPE
23063 registers. By default, @value{GDBN} selects the calling convention
23064 based on the selected architecture and the provided executable file.
23066 @item set powerpc exact-watchpoints
23067 @itemx show powerpc exact-watchpoints
23068 Allow @value{GDBN} to use only one debug register when watching a variable
23069 of scalar type, thus assuming that the variable is accessed through the
23070 address of its first byte.
23075 @subsection Atmel AVR
23078 When configured for debugging the Atmel AVR, @value{GDBN} supports the
23079 following AVR-specific commands:
23082 @item info io_registers
23083 @kindex info io_registers@r{, AVR}
23084 @cindex I/O registers (Atmel AVR)
23085 This command displays information about the AVR I/O registers. For
23086 each register, @value{GDBN} prints its number and value.
23093 When configured for debugging CRIS, @value{GDBN} provides the
23094 following CRIS-specific commands:
23097 @item set cris-version @var{ver}
23098 @cindex CRIS version
23099 Set the current CRIS version to @var{ver}, either @samp{10} or @samp{32}.
23100 The CRIS version affects register names and sizes. This command is useful in
23101 case autodetection of the CRIS version fails.
23103 @item show cris-version
23104 Show the current CRIS version.
23106 @item set cris-dwarf2-cfi
23107 @cindex DWARF-2 CFI and CRIS
23108 Set the usage of DWARF-2 CFI for CRIS debugging. The default is @samp{on}.
23109 Change to @samp{off} when using @code{gcc-cris} whose version is below
23112 @item show cris-dwarf2-cfi
23113 Show the current state of using DWARF-2 CFI.
23115 @item set cris-mode @var{mode}
23117 Set the current CRIS mode to @var{mode}. It should only be changed when
23118 debugging in guru mode, in which case it should be set to
23119 @samp{guru} (the default is @samp{normal}).
23121 @item show cris-mode
23122 Show the current CRIS mode.
23126 @subsection Renesas Super-H
23129 For the Renesas Super-H processor, @value{GDBN} provides these
23133 @item set sh calling-convention @var{convention}
23134 @kindex set sh calling-convention
23135 Set the calling-convention used when calling functions from @value{GDBN}.
23136 Allowed values are @samp{gcc}, which is the default setting, and @samp{renesas}.
23137 With the @samp{gcc} setting, functions are called using the @value{NGCC} calling
23138 convention. If the DWARF-2 information of the called function specifies
23139 that the function follows the Renesas calling convention, the function
23140 is called using the Renesas calling convention. If the calling convention
23141 is set to @samp{renesas}, the Renesas calling convention is always used,
23142 regardless of the DWARF-2 information. This can be used to override the
23143 default of @samp{gcc} if debug information is missing, or the compiler
23144 does not emit the DWARF-2 calling convention entry for a function.
23146 @item show sh calling-convention
23147 @kindex show sh calling-convention
23148 Show the current calling convention setting.
23153 @node Architectures
23154 @section Architectures
23156 This section describes characteristics of architectures that affect
23157 all uses of @value{GDBN} with the architecture, both native and cross.
23164 * HPPA:: HP PA architecture
23165 * SPU:: Cell Broadband Engine SPU architecture
23172 @subsection AArch64
23173 @cindex AArch64 support
23175 When @value{GDBN} is debugging the AArch64 architecture, it provides the
23176 following special commands:
23179 @item set debug aarch64
23180 @kindex set debug aarch64
23181 This command determines whether AArch64 architecture-specific debugging
23182 messages are to be displayed.
23184 @item show debug aarch64
23185 Show whether AArch64 debugging messages are displayed.
23190 @subsection x86 Architecture-specific Issues
23193 @item set struct-convention @var{mode}
23194 @kindex set struct-convention
23195 @cindex struct return convention
23196 @cindex struct/union returned in registers
23197 Set the convention used by the inferior to return @code{struct}s and
23198 @code{union}s from functions to @var{mode}. Possible values of
23199 @var{mode} are @code{"pcc"}, @code{"reg"}, and @code{"default"} (the
23200 default). @code{"default"} or @code{"pcc"} means that @code{struct}s
23201 are returned on the stack, while @code{"reg"} means that a
23202 @code{struct} or a @code{union} whose size is 1, 2, 4, or 8 bytes will
23203 be returned in a register.
23205 @item show struct-convention
23206 @kindex show struct-convention
23207 Show the current setting of the convention to return @code{struct}s
23212 @subsubsection Intel @dfn{Memory Protection Extensions} (MPX).
23213 @cindex Intel Memory Protection Extensions (MPX).
23215 Memory Protection Extension (MPX) adds the bound registers @samp{BND0}
23216 @footnote{The register named with capital letters represent the architecture
23217 registers.} through @samp{BND3}. Bound registers store a pair of 64-bit values
23218 which are the lower bound and upper bound. Bounds are effective addresses or
23219 memory locations. The upper bounds are architecturally represented in 1's
23220 complement form. A bound having lower bound = 0, and upper bound = 0
23221 (1's complement of all bits set) will allow access to the entire address space.
23223 @samp{BND0} through @samp{BND3} are represented in @value{GDBN} as @samp{bnd0raw}
23224 through @samp{bnd3raw}. Pseudo registers @samp{bnd0} through @samp{bnd3}
23225 display the upper bound performing the complement of one operation on the
23226 upper bound value, i.e.@ when upper bound in @samp{bnd0raw} is 0 in the
23227 @value{GDBN} @samp{bnd0} it will be @code{0xfff@dots{}}. In this sense it
23228 can also be noted that the upper bounds are inclusive.
23230 As an example, assume that the register BND0 holds bounds for a pointer having
23231 access allowed for the range between 0x32 and 0x71. The values present on
23232 bnd0raw and bnd registers are presented as follows:
23235 bnd0raw = @{0x32, 0xffffffff8e@}
23236 bnd0 = @{lbound = 0x32, ubound = 0x71@} : size 64
23239 This way the raw value can be accessed via bnd0raw@dots{}bnd3raw. Any
23240 change on bnd0@dots{}bnd3 or bnd0raw@dots{}bnd3raw is reflect on its
23241 counterpart. When the bnd0@dots{}bnd3 registers are displayed via
23242 Python, the display includes the memory size, in bits, accessible to
23245 Bounds can also be stored in bounds tables, which are stored in
23246 application memory. These tables store bounds for pointers by specifying
23247 the bounds pointer's value along with its bounds. Evaluating and changing
23248 bounds located in bound tables is therefore interesting while investigating
23249 bugs on MPX context. @value{GDBN} provides commands for this purpose:
23252 @item show mpx bound @var{pointer}
23253 @kindex show mpx bound
23254 Display bounds of the given @var{pointer}.
23256 @item set mpx bound @var{pointer}, @var{lbound}, @var{ubound}
23257 @kindex set mpx bound
23258 Set the bounds of a pointer in the bound table.
23259 This command takes three parameters: @var{pointer} is the pointers
23260 whose bounds are to be changed, @var{lbound} and @var{ubound} are new values
23261 for lower and upper bounds respectively.
23264 When you call an inferior function on an Intel MPX enabled program,
23265 GDB sets the inferior's bound registers to the init (disabled) state
23266 before calling the function. As a consequence, bounds checks for the
23267 pointer arguments passed to the function will always pass.
23269 This is necessary because when you call an inferior function, the
23270 program is usually in the middle of the execution of other function.
23271 Since at that point bound registers are in an arbitrary state, not
23272 clearing them would lead to random bound violations in the called
23275 You can still examine the influence of the bound registers on the
23276 execution of the called function by stopping the execution of the
23277 called function at its prologue, setting bound registers, and
23278 continuing the execution. For example:
23282 Breakpoint 2 at 0x4009de: file i386-mpx-call.c, line 47.
23283 $ print upper (a, b, c, d, 1)
23284 Breakpoint 2, upper (a=0x0, b=0x6e0000005b, c=0x0, d=0x0, len=48)....
23286 @{lbound = 0x0, ubound = ffffffff@} : size -1
23289 At this last step the value of bnd0 can be changed for investigation of bound
23290 violations caused along the execution of the call. In order to know how to
23291 set the bound registers or bound table for the call consult the ABI.
23296 See the following section.
23299 @subsection @acronym{MIPS}
23301 @cindex stack on Alpha
23302 @cindex stack on @acronym{MIPS}
23303 @cindex Alpha stack
23304 @cindex @acronym{MIPS} stack
23305 Alpha- and @acronym{MIPS}-based computers use an unusual stack frame, which
23306 sometimes requires @value{GDBN} to search backward in the object code to
23307 find the beginning of a function.
23309 @cindex response time, @acronym{MIPS} debugging
23310 To improve response time (especially for embedded applications, where
23311 @value{GDBN} may be restricted to a slow serial line for this search)
23312 you may want to limit the size of this search, using one of these
23316 @cindex @code{heuristic-fence-post} (Alpha, @acronym{MIPS})
23317 @item set heuristic-fence-post @var{limit}
23318 Restrict @value{GDBN} to examining at most @var{limit} bytes in its
23319 search for the beginning of a function. A value of @var{0} (the
23320 default) means there is no limit. However, except for @var{0}, the
23321 larger the limit the more bytes @code{heuristic-fence-post} must search
23322 and therefore the longer it takes to run. You should only need to use
23323 this command when debugging a stripped executable.
23325 @item show heuristic-fence-post
23326 Display the current limit.
23330 These commands are available @emph{only} when @value{GDBN} is configured
23331 for debugging programs on Alpha or @acronym{MIPS} processors.
23333 Several @acronym{MIPS}-specific commands are available when debugging @acronym{MIPS}
23337 @item set mips abi @var{arg}
23338 @kindex set mips abi
23339 @cindex set ABI for @acronym{MIPS}
23340 Tell @value{GDBN} which @acronym{MIPS} ABI is used by the inferior. Possible
23341 values of @var{arg} are:
23345 The default ABI associated with the current binary (this is the
23355 @item show mips abi
23356 @kindex show mips abi
23357 Show the @acronym{MIPS} ABI used by @value{GDBN} to debug the inferior.
23359 @item set mips compression @var{arg}
23360 @kindex set mips compression
23361 @cindex code compression, @acronym{MIPS}
23362 Tell @value{GDBN} which @acronym{MIPS} compressed
23363 @acronym{ISA, Instruction Set Architecture} encoding is used by the
23364 inferior. @value{GDBN} uses this for code disassembly and other
23365 internal interpretation purposes. This setting is only referred to
23366 when no executable has been associated with the debugging session or
23367 the executable does not provide information about the encoding it uses.
23368 Otherwise this setting is automatically updated from information
23369 provided by the executable.
23371 Possible values of @var{arg} are @samp{mips16} and @samp{micromips}.
23372 The default compressed @acronym{ISA} encoding is @samp{mips16}, as
23373 executables containing @acronym{MIPS16} code frequently are not
23374 identified as such.
23376 This setting is ``sticky''; that is, it retains its value across
23377 debugging sessions until reset either explicitly with this command or
23378 implicitly from an executable.
23380 The compiler and/or assembler typically add symbol table annotations to
23381 identify functions compiled for the @acronym{MIPS16} or
23382 @acronym{microMIPS} @acronym{ISA}s. If these function-scope annotations
23383 are present, @value{GDBN} uses them in preference to the global
23384 compressed @acronym{ISA} encoding setting.
23386 @item show mips compression
23387 @kindex show mips compression
23388 Show the @acronym{MIPS} compressed @acronym{ISA} encoding used by
23389 @value{GDBN} to debug the inferior.
23392 @itemx show mipsfpu
23393 @xref{MIPS Embedded, set mipsfpu}.
23395 @item set mips mask-address @var{arg}
23396 @kindex set mips mask-address
23397 @cindex @acronym{MIPS} addresses, masking
23398 This command determines whether the most-significant 32 bits of 64-bit
23399 @acronym{MIPS} addresses are masked off. The argument @var{arg} can be
23400 @samp{on}, @samp{off}, or @samp{auto}. The latter is the default
23401 setting, which lets @value{GDBN} determine the correct value.
23403 @item show mips mask-address
23404 @kindex show mips mask-address
23405 Show whether the upper 32 bits of @acronym{MIPS} addresses are masked off or
23408 @item set remote-mips64-transfers-32bit-regs
23409 @kindex set remote-mips64-transfers-32bit-regs
23410 This command controls compatibility with 64-bit @acronym{MIPS} targets that
23411 transfer data in 32-bit quantities. If you have an old @acronym{MIPS} 64 target
23412 that transfers 32 bits for some registers, like @sc{sr} and @sc{fsr},
23413 and 64 bits for other registers, set this option to @samp{on}.
23415 @item show remote-mips64-transfers-32bit-regs
23416 @kindex show remote-mips64-transfers-32bit-regs
23417 Show the current setting of compatibility with older @acronym{MIPS} 64 targets.
23419 @item set debug mips
23420 @kindex set debug mips
23421 This command turns on and off debugging messages for the @acronym{MIPS}-specific
23422 target code in @value{GDBN}.
23424 @item show debug mips
23425 @kindex show debug mips
23426 Show the current setting of @acronym{MIPS} debugging messages.
23432 @cindex HPPA support
23434 When @value{GDBN} is debugging the HP PA architecture, it provides the
23435 following special commands:
23438 @item set debug hppa
23439 @kindex set debug hppa
23440 This command determines whether HPPA architecture-specific debugging
23441 messages are to be displayed.
23443 @item show debug hppa
23444 Show whether HPPA debugging messages are displayed.
23446 @item maint print unwind @var{address}
23447 @kindex maint print unwind@r{, HPPA}
23448 This command displays the contents of the unwind table entry at the
23449 given @var{address}.
23455 @subsection Cell Broadband Engine SPU architecture
23456 @cindex Cell Broadband Engine
23459 When @value{GDBN} is debugging the Cell Broadband Engine SPU architecture,
23460 it provides the following special commands:
23463 @item info spu event
23465 Display SPU event facility status. Shows current event mask
23466 and pending event status.
23468 @item info spu signal
23469 Display SPU signal notification facility status. Shows pending
23470 signal-control word and signal notification mode of both signal
23471 notification channels.
23473 @item info spu mailbox
23474 Display SPU mailbox facility status. Shows all pending entries,
23475 in order of processing, in each of the SPU Write Outbound,
23476 SPU Write Outbound Interrupt, and SPU Read Inbound mailboxes.
23479 Display MFC DMA status. Shows all pending commands in the MFC
23480 DMA queue. For each entry, opcode, tag, class IDs, effective
23481 and local store addresses and transfer size are shown.
23483 @item info spu proxydma
23484 Display MFC Proxy-DMA status. Shows all pending commands in the MFC
23485 Proxy-DMA queue. For each entry, opcode, tag, class IDs, effective
23486 and local store addresses and transfer size are shown.
23490 When @value{GDBN} is debugging a combined PowerPC/SPU application
23491 on the Cell Broadband Engine, it provides in addition the following
23495 @item set spu stop-on-load @var{arg}
23497 Set whether to stop for new SPE threads. When set to @code{on}, @value{GDBN}
23498 will give control to the user when a new SPE thread enters its @code{main}
23499 function. The default is @code{off}.
23501 @item show spu stop-on-load
23503 Show whether to stop for new SPE threads.
23505 @item set spu auto-flush-cache @var{arg}
23506 Set whether to automatically flush the software-managed cache. When set to
23507 @code{on}, @value{GDBN} will automatically cause the SPE software-managed
23508 cache to be flushed whenever SPE execution stops. This provides a consistent
23509 view of PowerPC memory that is accessed via the cache. If an application
23510 does not use the software-managed cache, this option has no effect.
23512 @item show spu auto-flush-cache
23513 Show whether to automatically flush the software-managed cache.
23518 @subsection PowerPC
23519 @cindex PowerPC architecture
23521 When @value{GDBN} is debugging the PowerPC architecture, it provides a set of
23522 pseudo-registers to enable inspection of 128-bit wide Decimal Floating Point
23523 numbers stored in the floating point registers. These values must be stored
23524 in two consecutive registers, always starting at an even register like
23525 @code{f0} or @code{f2}.
23527 The pseudo-registers go from @code{$dl0} through @code{$dl15}, and are formed
23528 by joining the even/odd register pairs @code{f0} and @code{f1} for @code{$dl0},
23529 @code{f2} and @code{f3} for @code{$dl1} and so on.
23531 For POWER7 processors, @value{GDBN} provides a set of pseudo-registers, the 64-bit
23532 wide Extended Floating Point Registers (@samp{f32} through @samp{f63}).
23535 @subsection Nios II
23536 @cindex Nios II architecture
23538 When @value{GDBN} is debugging the Nios II architecture,
23539 it provides the following special commands:
23543 @item set debug nios2
23544 @kindex set debug nios2
23545 This command turns on and off debugging messages for the Nios II
23546 target code in @value{GDBN}.
23548 @item show debug nios2
23549 @kindex show debug nios2
23550 Show the current setting of Nios II debugging messages.
23554 @subsection Sparc64
23555 @cindex Sparc64 support
23556 @cindex Application Data Integrity
23557 @subsubsection ADI Support
23559 The M7 processor supports an Application Data Integrity (ADI) feature that
23560 detects invalid data accesses. When software allocates memory and enables
23561 ADI on the allocated memory, it chooses a 4-bit version number, sets the
23562 version in the upper 4 bits of the 64-bit pointer to that data, and stores
23563 the 4-bit version in every cacheline of that data. Hardware saves the latter
23564 in spare bits in the cache and memory hierarchy. On each load and store,
23565 the processor compares the upper 4 VA (virtual address) bits to the
23566 cacheline's version. If there is a mismatch, the processor generates a
23567 version mismatch trap which can be either precise or disrupting. The trap
23568 is an error condition which the kernel delivers to the process as a SIGSEGV
23571 Note that only 64-bit applications can use ADI and need to be built with
23574 Values of the ADI version tags, which are in granularity of a
23575 cacheline (64 bytes), can be viewed or modified.
23579 @kindex adi examine
23580 @item adi (examine | x) [ / @var{n} ] @var{addr}
23582 The @code{adi examine} command displays the value of one ADI version tag per
23585 @var{n} is a decimal integer specifying the number in bytes; the default
23586 is 1. It specifies how much ADI version information, at the ratio of 1:ADI
23587 block size, to display.
23589 @var{addr} is the address in user address space where you want @value{GDBN}
23590 to begin displaying the ADI version tags.
23592 Below is an example of displaying ADI versions of variable "shmaddr".
23595 (@value{GDBP}) adi x/100 shmaddr
23596 0xfff800010002c000: 0 0
23600 @item adi (assign | a) [ / @var{n} ] @var{addr} = @var{tag}
23602 The @code{adi assign} command is used to assign new ADI version tag
23605 @var{n} is a decimal integer specifying the number in bytes;
23606 the default is 1. It specifies how much ADI version information, at the
23607 ratio of 1:ADI block size, to modify.
23609 @var{addr} is the address in user address space where you want @value{GDBN}
23610 to begin modifying the ADI version tags.
23612 @var{tag} is the new ADI version tag.
23614 For example, do the following to modify then verify ADI versions of
23615 variable "shmaddr":
23618 (@value{GDBP}) adi a/100 shmaddr = 7
23619 (@value{GDBP}) adi x/100 shmaddr
23620 0xfff800010002c000: 7 7
23625 @node Controlling GDB
23626 @chapter Controlling @value{GDBN}
23628 You can alter the way @value{GDBN} interacts with you by using the
23629 @code{set} command. For commands controlling how @value{GDBN} displays
23630 data, see @ref{Print Settings, ,Print Settings}. Other settings are
23635 * Editing:: Command editing
23636 * Command History:: Command history
23637 * Screen Size:: Screen size
23638 * Numbers:: Numbers
23639 * ABI:: Configuring the current ABI
23640 * Auto-loading:: Automatically loading associated files
23641 * Messages/Warnings:: Optional warnings and messages
23642 * Debugging Output:: Optional messages about internal happenings
23643 * Other Misc Settings:: Other Miscellaneous Settings
23651 @value{GDBN} indicates its readiness to read a command by printing a string
23652 called the @dfn{prompt}. This string is normally @samp{(@value{GDBP})}. You
23653 can change the prompt string with the @code{set prompt} command. For
23654 instance, when debugging @value{GDBN} with @value{GDBN}, it is useful to change
23655 the prompt in one of the @value{GDBN} sessions so that you can always tell
23656 which one you are talking to.
23658 @emph{Note:} @code{set prompt} does not add a space for you after the
23659 prompt you set. This allows you to set a prompt which ends in a space
23660 or a prompt that does not.
23664 @item set prompt @var{newprompt}
23665 Directs @value{GDBN} to use @var{newprompt} as its prompt string henceforth.
23667 @kindex show prompt
23669 Prints a line of the form: @samp{Gdb's prompt is: @var{your-prompt}}
23672 Versions of @value{GDBN} that ship with Python scripting enabled have
23673 prompt extensions. The commands for interacting with these extensions
23677 @kindex set extended-prompt
23678 @item set extended-prompt @var{prompt}
23679 Set an extended prompt that allows for substitutions.
23680 @xref{gdb.prompt}, for a list of escape sequences that can be used for
23681 substitution. Any escape sequences specified as part of the prompt
23682 string are replaced with the corresponding strings each time the prompt
23688 set extended-prompt Current working directory: \w (gdb)
23691 Note that when an extended-prompt is set, it takes control of the
23692 @var{prompt_hook} hook. @xref{prompt_hook}, for further information.
23694 @kindex show extended-prompt
23695 @item show extended-prompt
23696 Prints the extended prompt. Any escape sequences specified as part of
23697 the prompt string with @code{set extended-prompt}, are replaced with the
23698 corresponding strings each time the prompt is displayed.
23702 @section Command Editing
23704 @cindex command line editing
23706 @value{GDBN} reads its input commands via the @dfn{Readline} interface. This
23707 @sc{gnu} library provides consistent behavior for programs which provide a
23708 command line interface to the user. Advantages are @sc{gnu} Emacs-style
23709 or @dfn{vi}-style inline editing of commands, @code{csh}-like history
23710 substitution, and a storage and recall of command history across
23711 debugging sessions.
23713 You may control the behavior of command line editing in @value{GDBN} with the
23714 command @code{set}.
23717 @kindex set editing
23720 @itemx set editing on
23721 Enable command line editing (enabled by default).
23723 @item set editing off
23724 Disable command line editing.
23726 @kindex show editing
23728 Show whether command line editing is enabled.
23731 @ifset SYSTEM_READLINE
23732 @xref{Command Line Editing, , , rluserman, GNU Readline Library},
23734 @ifclear SYSTEM_READLINE
23735 @xref{Command Line Editing},
23737 for more details about the Readline
23738 interface. Users unfamiliar with @sc{gnu} Emacs or @code{vi} are
23739 encouraged to read that chapter.
23741 @node Command History
23742 @section Command History
23743 @cindex command history
23745 @value{GDBN} can keep track of the commands you type during your
23746 debugging sessions, so that you can be certain of precisely what
23747 happened. Use these commands to manage the @value{GDBN} command
23750 @value{GDBN} uses the @sc{gnu} History library, a part of the Readline
23751 package, to provide the history facility.
23752 @ifset SYSTEM_READLINE
23753 @xref{Using History Interactively, , , history, GNU History Library},
23755 @ifclear SYSTEM_READLINE
23756 @xref{Using History Interactively},
23758 for the detailed description of the History library.
23760 To issue a command to @value{GDBN} without affecting certain aspects of
23761 the state which is seen by users, prefix it with @samp{server }
23762 (@pxref{Server Prefix}). This
23763 means that this command will not affect the command history, nor will it
23764 affect @value{GDBN}'s notion of which command to repeat if @key{RET} is
23765 pressed on a line by itself.
23767 @cindex @code{server}, command prefix
23768 The server prefix does not affect the recording of values into the value
23769 history; to print a value without recording it into the value history,
23770 use the @code{output} command instead of the @code{print} command.
23772 Here is the description of @value{GDBN} commands related to command
23776 @cindex history substitution
23777 @cindex history file
23778 @kindex set history filename
23779 @cindex @env{GDBHISTFILE}, environment variable
23780 @item set history filename @var{fname}
23781 Set the name of the @value{GDBN} command history file to @var{fname}.
23782 This is the file where @value{GDBN} reads an initial command history
23783 list, and where it writes the command history from this session when it
23784 exits. You can access this list through history expansion or through
23785 the history command editing characters listed below. This file defaults
23786 to the value of the environment variable @code{GDBHISTFILE}, or to
23787 @file{./.gdb_history} (@file{./_gdb_history} on MS-DOS) if this variable
23790 @cindex save command history
23791 @kindex set history save
23792 @item set history save
23793 @itemx set history save on
23794 Record command history in a file, whose name may be specified with the
23795 @code{set history filename} command. By default, this option is disabled.
23797 @item set history save off
23798 Stop recording command history in a file.
23800 @cindex history size
23801 @kindex set history size
23802 @cindex @env{GDBHISTSIZE}, environment variable
23803 @item set history size @var{size}
23804 @itemx set history size unlimited
23805 Set the number of commands which @value{GDBN} keeps in its history list.
23806 This defaults to the value of the environment variable @env{GDBHISTSIZE}, or
23807 to 256 if this variable is not set. Non-numeric values of @env{GDBHISTSIZE}
23808 are ignored. If @var{size} is @code{unlimited} or if @env{GDBHISTSIZE} is
23809 either a negative number or the empty string, then the number of commands
23810 @value{GDBN} keeps in the history list is unlimited.
23812 @cindex remove duplicate history
23813 @kindex set history remove-duplicates
23814 @item set history remove-duplicates @var{count}
23815 @itemx set history remove-duplicates unlimited
23816 Control the removal of duplicate history entries in the command history list.
23817 If @var{count} is non-zero, @value{GDBN} will look back at the last @var{count}
23818 history entries and remove the first entry that is a duplicate of the current
23819 entry being added to the command history list. If @var{count} is
23820 @code{unlimited} then this lookbehind is unbounded. If @var{count} is 0, then
23821 removal of duplicate history entries is disabled.
23823 Only history entries added during the current session are considered for
23824 removal. This option is set to 0 by default.
23828 History expansion assigns special meaning to the character @kbd{!}.
23829 @ifset SYSTEM_READLINE
23830 @xref{Event Designators, , , history, GNU History Library},
23832 @ifclear SYSTEM_READLINE
23833 @xref{Event Designators},
23837 @cindex history expansion, turn on/off
23838 Since @kbd{!} is also the logical not operator in C, history expansion
23839 is off by default. If you decide to enable history expansion with the
23840 @code{set history expansion on} command, you may sometimes need to
23841 follow @kbd{!} (when it is used as logical not, in an expression) with
23842 a space or a tab to prevent it from being expanded. The readline
23843 history facilities do not attempt substitution on the strings
23844 @kbd{!=} and @kbd{!(}, even when history expansion is enabled.
23846 The commands to control history expansion are:
23849 @item set history expansion on
23850 @itemx set history expansion
23851 @kindex set history expansion
23852 Enable history expansion. History expansion is off by default.
23854 @item set history expansion off
23855 Disable history expansion.
23858 @kindex show history
23860 @itemx show history filename
23861 @itemx show history save
23862 @itemx show history size
23863 @itemx show history expansion
23864 These commands display the state of the @value{GDBN} history parameters.
23865 @code{show history} by itself displays all four states.
23870 @kindex show commands
23871 @cindex show last commands
23872 @cindex display command history
23873 @item show commands
23874 Display the last ten commands in the command history.
23876 @item show commands @var{n}
23877 Print ten commands centered on command number @var{n}.
23879 @item show commands +
23880 Print ten commands just after the commands last printed.
23884 @section Screen Size
23885 @cindex size of screen
23886 @cindex screen size
23889 @cindex pauses in output
23891 Certain commands to @value{GDBN} may produce large amounts of
23892 information output to the screen. To help you read all of it,
23893 @value{GDBN} pauses and asks you for input at the end of each page of
23894 output. Type @key{RET} when you want to see one more page of output,
23895 @kbd{q} to discard the remaining output, or @kbd{c} to continue
23896 without paging for the rest of the current command. Also, the screen
23897 width setting determines when to wrap lines of output. Depending on
23898 what is being printed, @value{GDBN} tries to break the line at a
23899 readable place, rather than simply letting it overflow onto the
23902 Normally @value{GDBN} knows the size of the screen from the terminal
23903 driver software. For example, on Unix @value{GDBN} uses the termcap data base
23904 together with the value of the @code{TERM} environment variable and the
23905 @code{stty rows} and @code{stty cols} settings. If this is not correct,
23906 you can override it with the @code{set height} and @code{set
23913 @kindex show height
23914 @item set height @var{lpp}
23915 @itemx set height unlimited
23917 @itemx set width @var{cpl}
23918 @itemx set width unlimited
23920 These @code{set} commands specify a screen height of @var{lpp} lines and
23921 a screen width of @var{cpl} characters. The associated @code{show}
23922 commands display the current settings.
23924 If you specify a height of either @code{unlimited} or zero lines,
23925 @value{GDBN} does not pause during output no matter how long the
23926 output is. This is useful if output is to a file or to an editor
23929 Likewise, you can specify @samp{set width unlimited} or @samp{set
23930 width 0} to prevent @value{GDBN} from wrapping its output.
23932 @item set pagination on
23933 @itemx set pagination off
23934 @kindex set pagination
23935 Turn the output pagination on or off; the default is on. Turning
23936 pagination off is the alternative to @code{set height unlimited}. Note that
23937 running @value{GDBN} with the @option{--batch} option (@pxref{Mode
23938 Options, -batch}) also automatically disables pagination.
23940 @item show pagination
23941 @kindex show pagination
23942 Show the current pagination mode.
23947 @cindex number representation
23948 @cindex entering numbers
23950 You can always enter numbers in octal, decimal, or hexadecimal in
23951 @value{GDBN} by the usual conventions: octal numbers begin with
23952 @samp{0}, decimal numbers end with @samp{.}, and hexadecimal numbers
23953 begin with @samp{0x}. Numbers that neither begin with @samp{0} or
23954 @samp{0x}, nor end with a @samp{.} are, by default, entered in base
23955 10; likewise, the default display for numbers---when no particular
23956 format is specified---is base 10. You can change the default base for
23957 both input and output with the commands described below.
23960 @kindex set input-radix
23961 @item set input-radix @var{base}
23962 Set the default base for numeric input. Supported choices
23963 for @var{base} are decimal 8, 10, or 16. The base must itself be
23964 specified either unambiguously or using the current input radix; for
23968 set input-radix 012
23969 set input-radix 10.
23970 set input-radix 0xa
23974 sets the input base to decimal. On the other hand, @samp{set input-radix 10}
23975 leaves the input radix unchanged, no matter what it was, since
23976 @samp{10}, being without any leading or trailing signs of its base, is
23977 interpreted in the current radix. Thus, if the current radix is 16,
23978 @samp{10} is interpreted in hex, i.e.@: as 16 decimal, which doesn't
23981 @kindex set output-radix
23982 @item set output-radix @var{base}
23983 Set the default base for numeric display. Supported choices
23984 for @var{base} are decimal 8, 10, or 16. The base must itself be
23985 specified either unambiguously or using the current input radix.
23987 @kindex show input-radix
23988 @item show input-radix
23989 Display the current default base for numeric input.
23991 @kindex show output-radix
23992 @item show output-radix
23993 Display the current default base for numeric display.
23995 @item set radix @r{[}@var{base}@r{]}
23999 These commands set and show the default base for both input and output
24000 of numbers. @code{set radix} sets the radix of input and output to
24001 the same base; without an argument, it resets the radix back to its
24002 default value of 10.
24007 @section Configuring the Current ABI
24009 @value{GDBN} can determine the @dfn{ABI} (Application Binary Interface) of your
24010 application automatically. However, sometimes you need to override its
24011 conclusions. Use these commands to manage @value{GDBN}'s view of the
24017 @cindex Newlib OS ABI and its influence on the longjmp handling
24019 One @value{GDBN} configuration can debug binaries for multiple operating
24020 system targets, either via remote debugging or native emulation.
24021 @value{GDBN} will autodetect the @dfn{OS ABI} (Operating System ABI) in use,
24022 but you can override its conclusion using the @code{set osabi} command.
24023 One example where this is useful is in debugging of binaries which use
24024 an alternate C library (e.g.@: @sc{uClibc} for @sc{gnu}/Linux) which does
24025 not have the same identifying marks that the standard C library for your
24028 When @value{GDBN} is debugging the AArch64 architecture, it provides a
24029 ``Newlib'' OS ABI. This is useful for handling @code{setjmp} and
24030 @code{longjmp} when debugging binaries that use the @sc{newlib} C library.
24031 The ``Newlib'' OS ABI can be selected by @code{set osabi Newlib}.
24035 Show the OS ABI currently in use.
24038 With no argument, show the list of registered available OS ABI's.
24040 @item set osabi @var{abi}
24041 Set the current OS ABI to @var{abi}.
24044 @cindex float promotion
24046 Generally, the way that an argument of type @code{float} is passed to a
24047 function depends on whether the function is prototyped. For a prototyped
24048 (i.e.@: ANSI/ISO style) function, @code{float} arguments are passed unchanged,
24049 according to the architecture's convention for @code{float}. For unprototyped
24050 (i.e.@: K&R style) functions, @code{float} arguments are first promoted to type
24051 @code{double} and then passed.
24053 Unfortunately, some forms of debug information do not reliably indicate whether
24054 a function is prototyped. If @value{GDBN} calls a function that is not marked
24055 as prototyped, it consults @kbd{set coerce-float-to-double}.
24058 @kindex set coerce-float-to-double
24059 @item set coerce-float-to-double
24060 @itemx set coerce-float-to-double on
24061 Arguments of type @code{float} will be promoted to @code{double} when passed
24062 to an unprototyped function. This is the default setting.
24064 @item set coerce-float-to-double off
24065 Arguments of type @code{float} will be passed directly to unprototyped
24068 @kindex show coerce-float-to-double
24069 @item show coerce-float-to-double
24070 Show the current setting of promoting @code{float} to @code{double}.
24074 @kindex show cp-abi
24075 @value{GDBN} needs to know the ABI used for your program's C@t{++}
24076 objects. The correct C@t{++} ABI depends on which C@t{++} compiler was
24077 used to build your application. @value{GDBN} only fully supports
24078 programs with a single C@t{++} ABI; if your program contains code using
24079 multiple C@t{++} ABI's or if @value{GDBN} can not identify your
24080 program's ABI correctly, you can tell @value{GDBN} which ABI to use.
24081 Currently supported ABI's include ``gnu-v2'', for @code{g++} versions
24082 before 3.0, ``gnu-v3'', for @code{g++} versions 3.0 and later, and
24083 ``hpaCC'' for the HP ANSI C@t{++} compiler. Other C@t{++} compilers may
24084 use the ``gnu-v2'' or ``gnu-v3'' ABI's as well. The default setting is
24089 Show the C@t{++} ABI currently in use.
24092 With no argument, show the list of supported C@t{++} ABI's.
24094 @item set cp-abi @var{abi}
24095 @itemx set cp-abi auto
24096 Set the current C@t{++} ABI to @var{abi}, or return to automatic detection.
24100 @section Automatically loading associated files
24101 @cindex auto-loading
24103 @value{GDBN} sometimes reads files with commands and settings automatically,
24104 without being explicitly told so by the user. We call this feature
24105 @dfn{auto-loading}. While auto-loading is useful for automatically adapting
24106 @value{GDBN} to the needs of your project, it can sometimes produce unexpected
24107 results or introduce security risks (e.g., if the file comes from untrusted
24111 * Init File in the Current Directory:: @samp{set/show/info auto-load local-gdbinit}
24112 * libthread_db.so.1 file:: @samp{set/show/info auto-load libthread-db}
24114 * Auto-loading safe path:: @samp{set/show/info auto-load safe-path}
24115 * Auto-loading verbose mode:: @samp{set/show debug auto-load}
24118 There are various kinds of files @value{GDBN} can automatically load.
24119 In addition to these files, @value{GDBN} supports auto-loading code written
24120 in various extension languages. @xref{Auto-loading extensions}.
24122 Note that loading of these associated files (including the local @file{.gdbinit}
24123 file) requires accordingly configured @code{auto-load safe-path}
24124 (@pxref{Auto-loading safe path}).
24126 For these reasons, @value{GDBN} includes commands and options to let you
24127 control when to auto-load files and which files should be auto-loaded.
24130 @anchor{set auto-load off}
24131 @kindex set auto-load off
24132 @item set auto-load off
24133 Globally disable loading of all auto-loaded files.
24134 You may want to use this command with the @samp{-iex} option
24135 (@pxref{Option -init-eval-command}) such as:
24137 $ @kbd{gdb -iex "set auto-load off" untrusted-executable corefile}
24140 Be aware that system init file (@pxref{System-wide configuration})
24141 and init files from your home directory (@pxref{Home Directory Init File})
24142 still get read (as they come from generally trusted directories).
24143 To prevent @value{GDBN} from auto-loading even those init files, use the
24144 @option{-nx} option (@pxref{Mode Options}), in addition to
24145 @code{set auto-load no}.
24147 @anchor{show auto-load}
24148 @kindex show auto-load
24149 @item show auto-load
24150 Show whether auto-loading of each specific @samp{auto-load} file(s) is enabled
24154 (gdb) show auto-load
24155 gdb-scripts: Auto-loading of canned sequences of commands scripts is on.
24156 libthread-db: Auto-loading of inferior specific libthread_db is on.
24157 local-gdbinit: Auto-loading of .gdbinit script from current directory
24159 python-scripts: Auto-loading of Python scripts is on.
24160 safe-path: List of directories from which it is safe to auto-load files
24161 is $debugdir:$datadir/auto-load.
24162 scripts-directory: List of directories from which to load auto-loaded scripts
24163 is $debugdir:$datadir/auto-load.
24166 @anchor{info auto-load}
24167 @kindex info auto-load
24168 @item info auto-load
24169 Print whether each specific @samp{auto-load} file(s) have been auto-loaded or
24173 (gdb) info auto-load
24176 Yes /home/user/gdb/gdb-gdb.gdb
24177 libthread-db: No auto-loaded libthread-db.
24178 local-gdbinit: Local .gdbinit file "/home/user/gdb/.gdbinit" has been
24182 Yes /home/user/gdb/gdb-gdb.py
24186 These are @value{GDBN} control commands for the auto-loading:
24188 @multitable @columnfractions .5 .5
24189 @item @xref{set auto-load off}.
24190 @tab Disable auto-loading globally.
24191 @item @xref{show auto-load}.
24192 @tab Show setting of all kinds of files.
24193 @item @xref{info auto-load}.
24194 @tab Show state of all kinds of files.
24195 @item @xref{set auto-load gdb-scripts}.
24196 @tab Control for @value{GDBN} command scripts.
24197 @item @xref{show auto-load gdb-scripts}.
24198 @tab Show setting of @value{GDBN} command scripts.
24199 @item @xref{info auto-load gdb-scripts}.
24200 @tab Show state of @value{GDBN} command scripts.
24201 @item @xref{set auto-load python-scripts}.
24202 @tab Control for @value{GDBN} Python scripts.
24203 @item @xref{show auto-load python-scripts}.
24204 @tab Show setting of @value{GDBN} Python scripts.
24205 @item @xref{info auto-load python-scripts}.
24206 @tab Show state of @value{GDBN} Python scripts.
24207 @item @xref{set auto-load guile-scripts}.
24208 @tab Control for @value{GDBN} Guile scripts.
24209 @item @xref{show auto-load guile-scripts}.
24210 @tab Show setting of @value{GDBN} Guile scripts.
24211 @item @xref{info auto-load guile-scripts}.
24212 @tab Show state of @value{GDBN} Guile scripts.
24213 @item @xref{set auto-load scripts-directory}.
24214 @tab Control for @value{GDBN} auto-loaded scripts location.
24215 @item @xref{show auto-load scripts-directory}.
24216 @tab Show @value{GDBN} auto-loaded scripts location.
24217 @item @xref{add-auto-load-scripts-directory}.
24218 @tab Add directory for auto-loaded scripts location list.
24219 @item @xref{set auto-load local-gdbinit}.
24220 @tab Control for init file in the current directory.
24221 @item @xref{show auto-load local-gdbinit}.
24222 @tab Show setting of init file in the current directory.
24223 @item @xref{info auto-load local-gdbinit}.
24224 @tab Show state of init file in the current directory.
24225 @item @xref{set auto-load libthread-db}.
24226 @tab Control for thread debugging library.
24227 @item @xref{show auto-load libthread-db}.
24228 @tab Show setting of thread debugging library.
24229 @item @xref{info auto-load libthread-db}.
24230 @tab Show state of thread debugging library.
24231 @item @xref{set auto-load safe-path}.
24232 @tab Control directories trusted for automatic loading.
24233 @item @xref{show auto-load safe-path}.
24234 @tab Show directories trusted for automatic loading.
24235 @item @xref{add-auto-load-safe-path}.
24236 @tab Add directory trusted for automatic loading.
24239 @node Init File in the Current Directory
24240 @subsection Automatically loading init file in the current directory
24241 @cindex auto-loading init file in the current directory
24243 By default, @value{GDBN} reads and executes the canned sequences of commands
24244 from init file (if any) in the current working directory,
24245 see @ref{Init File in the Current Directory during Startup}.
24247 Note that loading of this local @file{.gdbinit} file also requires accordingly
24248 configured @code{auto-load safe-path} (@pxref{Auto-loading safe path}).
24251 @anchor{set auto-load local-gdbinit}
24252 @kindex set auto-load local-gdbinit
24253 @item set auto-load local-gdbinit [on|off]
24254 Enable or disable the auto-loading of canned sequences of commands
24255 (@pxref{Sequences}) found in init file in the current directory.
24257 @anchor{show auto-load local-gdbinit}
24258 @kindex show auto-load local-gdbinit
24259 @item show auto-load local-gdbinit
24260 Show whether auto-loading of canned sequences of commands from init file in the
24261 current directory is enabled or disabled.
24263 @anchor{info auto-load local-gdbinit}
24264 @kindex info auto-load local-gdbinit
24265 @item info auto-load local-gdbinit
24266 Print whether canned sequences of commands from init file in the
24267 current directory have been auto-loaded.
24270 @node libthread_db.so.1 file
24271 @subsection Automatically loading thread debugging library
24272 @cindex auto-loading libthread_db.so.1
24274 This feature is currently present only on @sc{gnu}/Linux native hosts.
24276 @value{GDBN} reads in some cases thread debugging library from places specific
24277 to the inferior (@pxref{set libthread-db-search-path}).
24279 The special @samp{libthread-db-search-path} entry @samp{$sdir} is processed
24280 without checking this @samp{set auto-load libthread-db} switch as system
24281 libraries have to be trusted in general. In all other cases of
24282 @samp{libthread-db-search-path} entries @value{GDBN} checks first if @samp{set
24283 auto-load libthread-db} is enabled before trying to open such thread debugging
24286 Note that loading of this debugging library also requires accordingly configured
24287 @code{auto-load safe-path} (@pxref{Auto-loading safe path}).
24290 @anchor{set auto-load libthread-db}
24291 @kindex set auto-load libthread-db
24292 @item set auto-load libthread-db [on|off]
24293 Enable or disable the auto-loading of inferior specific thread debugging library.
24295 @anchor{show auto-load libthread-db}
24296 @kindex show auto-load libthread-db
24297 @item show auto-load libthread-db
24298 Show whether auto-loading of inferior specific thread debugging library is
24299 enabled or disabled.
24301 @anchor{info auto-load libthread-db}
24302 @kindex info auto-load libthread-db
24303 @item info auto-load libthread-db
24304 Print the list of all loaded inferior specific thread debugging libraries and
24305 for each such library print list of inferior @var{pid}s using it.
24308 @node Auto-loading safe path
24309 @subsection Security restriction for auto-loading
24310 @cindex auto-loading safe-path
24312 As the files of inferior can come from untrusted source (such as submitted by
24313 an application user) @value{GDBN} does not always load any files automatically.
24314 @value{GDBN} provides the @samp{set auto-load safe-path} setting to list
24315 directories trusted for loading files not explicitly requested by user.
24316 Each directory can also be a shell wildcard pattern.
24318 If the path is not set properly you will see a warning and the file will not
24323 Reading symbols from /home/user/gdb/gdb...done.
24324 warning: File "/home/user/gdb/gdb-gdb.gdb" auto-loading has been
24325 declined by your `auto-load safe-path' set
24326 to "$debugdir:$datadir/auto-load".
24327 warning: File "/home/user/gdb/gdb-gdb.py" auto-loading has been
24328 declined by your `auto-load safe-path' set
24329 to "$debugdir:$datadir/auto-load".
24333 To instruct @value{GDBN} to go ahead and use the init files anyway,
24334 invoke @value{GDBN} like this:
24337 $ gdb -q -iex "set auto-load safe-path /home/user/gdb" ./gdb
24340 The list of trusted directories is controlled by the following commands:
24343 @anchor{set auto-load safe-path}
24344 @kindex set auto-load safe-path
24345 @item set auto-load safe-path @r{[}@var{directories}@r{]}
24346 Set the list of directories (and their subdirectories) trusted for automatic
24347 loading and execution of scripts. You can also enter a specific trusted file.
24348 Each directory can also be a shell wildcard pattern; wildcards do not match
24349 directory separator - see @code{FNM_PATHNAME} for system function @code{fnmatch}
24350 (@pxref{Wildcard Matching, fnmatch, , libc, GNU C Library Reference Manual}).
24351 If you omit @var{directories}, @samp{auto-load safe-path} will be reset to
24352 its default value as specified during @value{GDBN} compilation.
24354 The list of directories uses path separator (@samp{:} on GNU and Unix
24355 systems, @samp{;} on MS-Windows and MS-DOS) to separate directories, similarly
24356 to the @env{PATH} environment variable.
24358 @anchor{show auto-load safe-path}
24359 @kindex show auto-load safe-path
24360 @item show auto-load safe-path
24361 Show the list of directories trusted for automatic loading and execution of
24364 @anchor{add-auto-load-safe-path}
24365 @kindex add-auto-load-safe-path
24366 @item add-auto-load-safe-path
24367 Add an entry (or list of entries) to the list of directories trusted for
24368 automatic loading and execution of scripts. Multiple entries may be delimited
24369 by the host platform path separator in use.
24372 This variable defaults to what @code{--with-auto-load-dir} has been configured
24373 to (@pxref{with-auto-load-dir}). @file{$debugdir} and @file{$datadir}
24374 substitution applies the same as for @ref{set auto-load scripts-directory}.
24375 The default @code{set auto-load safe-path} value can be also overriden by
24376 @value{GDBN} configuration option @option{--with-auto-load-safe-path}.
24378 Setting this variable to @file{/} disables this security protection,
24379 corresponding @value{GDBN} configuration option is
24380 @option{--without-auto-load-safe-path}.
24381 This variable is supposed to be set to the system directories writable by the
24382 system superuser only. Users can add their source directories in init files in
24383 their home directories (@pxref{Home Directory Init File}). See also deprecated
24384 init file in the current directory
24385 (@pxref{Init File in the Current Directory during Startup}).
24387 To force @value{GDBN} to load the files it declined to load in the previous
24388 example, you could use one of the following ways:
24391 @item @file{~/.gdbinit}: @samp{add-auto-load-safe-path ~/src/gdb}
24392 Specify this trusted directory (or a file) as additional component of the list.
24393 You have to specify also any existing directories displayed by
24394 by @samp{show auto-load safe-path} (such as @samp{/usr:/bin} in this example).
24396 @item @kbd{gdb -iex "set auto-load safe-path /usr:/bin:~/src/gdb" @dots{}}
24397 Specify this directory as in the previous case but just for a single
24398 @value{GDBN} session.
24400 @item @kbd{gdb -iex "set auto-load safe-path /" @dots{}}
24401 Disable auto-loading safety for a single @value{GDBN} session.
24402 This assumes all the files you debug during this @value{GDBN} session will come
24403 from trusted sources.
24405 @item @kbd{./configure --without-auto-load-safe-path}
24406 During compilation of @value{GDBN} you may disable any auto-loading safety.
24407 This assumes all the files you will ever debug with this @value{GDBN} come from
24411 On the other hand you can also explicitly forbid automatic files loading which
24412 also suppresses any such warning messages:
24415 @item @kbd{gdb -iex "set auto-load no" @dots{}}
24416 You can use @value{GDBN} command-line option for a single @value{GDBN} session.
24418 @item @file{~/.gdbinit}: @samp{set auto-load no}
24419 Disable auto-loading globally for the user
24420 (@pxref{Home Directory Init File}). While it is improbable, you could also
24421 use system init file instead (@pxref{System-wide configuration}).
24424 This setting applies to the file names as entered by user. If no entry matches
24425 @value{GDBN} tries as a last resort to also resolve all the file names into
24426 their canonical form (typically resolving symbolic links) and compare the
24427 entries again. @value{GDBN} already canonicalizes most of the filenames on its
24428 own before starting the comparison so a canonical form of directories is
24429 recommended to be entered.
24431 @node Auto-loading verbose mode
24432 @subsection Displaying files tried for auto-load
24433 @cindex auto-loading verbose mode
24435 For better visibility of all the file locations where you can place scripts to
24436 be auto-loaded with inferior --- or to protect yourself against accidental
24437 execution of untrusted scripts --- @value{GDBN} provides a feature for printing
24438 all the files attempted to be loaded. Both existing and non-existing files may
24441 For example the list of directories from which it is safe to auto-load files
24442 (@pxref{Auto-loading safe path}) applies also to canonicalized filenames which
24443 may not be too obvious while setting it up.
24446 (gdb) set debug auto-load on
24447 (gdb) file ~/src/t/true
24448 auto-load: Loading canned sequences of commands script "/tmp/true-gdb.gdb"
24449 for objfile "/tmp/true".
24450 auto-load: Updating directories of "/usr:/opt".
24451 auto-load: Using directory "/usr".
24452 auto-load: Using directory "/opt".
24453 warning: File "/tmp/true-gdb.gdb" auto-loading has been declined
24454 by your `auto-load safe-path' set to "/usr:/opt".
24458 @anchor{set debug auto-load}
24459 @kindex set debug auto-load
24460 @item set debug auto-load [on|off]
24461 Set whether to print the filenames attempted to be auto-loaded.
24463 @anchor{show debug auto-load}
24464 @kindex show debug auto-load
24465 @item show debug auto-load
24466 Show whether printing of the filenames attempted to be auto-loaded is turned
24470 @node Messages/Warnings
24471 @section Optional Warnings and Messages
24473 @cindex verbose operation
24474 @cindex optional warnings
24475 By default, @value{GDBN} is silent about its inner workings. If you are
24476 running on a slow machine, you may want to use the @code{set verbose}
24477 command. This makes @value{GDBN} tell you when it does a lengthy
24478 internal operation, so you will not think it has crashed.
24480 Currently, the messages controlled by @code{set verbose} are those
24481 which announce that the symbol table for a source file is being read;
24482 see @code{symbol-file} in @ref{Files, ,Commands to Specify Files}.
24485 @kindex set verbose
24486 @item set verbose on
24487 Enables @value{GDBN} output of certain informational messages.
24489 @item set verbose off
24490 Disables @value{GDBN} output of certain informational messages.
24492 @kindex show verbose
24494 Displays whether @code{set verbose} is on or off.
24497 By default, if @value{GDBN} encounters bugs in the symbol table of an
24498 object file, it is silent; but if you are debugging a compiler, you may
24499 find this information useful (@pxref{Symbol Errors, ,Errors Reading
24504 @kindex set complaints
24505 @item set complaints @var{limit}
24506 Permits @value{GDBN} to output @var{limit} complaints about each type of
24507 unusual symbols before becoming silent about the problem. Set
24508 @var{limit} to zero to suppress all complaints; set it to a large number
24509 to prevent complaints from being suppressed.
24511 @kindex show complaints
24512 @item show complaints
24513 Displays how many symbol complaints @value{GDBN} is permitted to produce.
24517 @anchor{confirmation requests}
24518 By default, @value{GDBN} is cautious, and asks what sometimes seems to be a
24519 lot of stupid questions to confirm certain commands. For example, if
24520 you try to run a program which is already running:
24524 The program being debugged has been started already.
24525 Start it from the beginning? (y or n)
24528 If you are willing to unflinchingly face the consequences of your own
24529 commands, you can disable this ``feature'':
24533 @kindex set confirm
24535 @cindex confirmation
24536 @cindex stupid questions
24537 @item set confirm off
24538 Disables confirmation requests. Note that running @value{GDBN} with
24539 the @option{--batch} option (@pxref{Mode Options, -batch}) also
24540 automatically disables confirmation requests.
24542 @item set confirm on
24543 Enables confirmation requests (the default).
24545 @kindex show confirm
24547 Displays state of confirmation requests.
24551 @cindex command tracing
24552 If you need to debug user-defined commands or sourced files you may find it
24553 useful to enable @dfn{command tracing}. In this mode each command will be
24554 printed as it is executed, prefixed with one or more @samp{+} symbols, the
24555 quantity denoting the call depth of each command.
24558 @kindex set trace-commands
24559 @cindex command scripts, debugging
24560 @item set trace-commands on
24561 Enable command tracing.
24562 @item set trace-commands off
24563 Disable command tracing.
24564 @item show trace-commands
24565 Display the current state of command tracing.
24568 @node Debugging Output
24569 @section Optional Messages about Internal Happenings
24570 @cindex optional debugging messages
24572 @value{GDBN} has commands that enable optional debugging messages from
24573 various @value{GDBN} subsystems; normally these commands are of
24574 interest to @value{GDBN} maintainers, or when reporting a bug. This
24575 section documents those commands.
24578 @kindex set exec-done-display
24579 @item set exec-done-display
24580 Turns on or off the notification of asynchronous commands'
24581 completion. When on, @value{GDBN} will print a message when an
24582 asynchronous command finishes its execution. The default is off.
24583 @kindex show exec-done-display
24584 @item show exec-done-display
24585 Displays the current setting of asynchronous command completion
24588 @cindex ARM AArch64
24589 @item set debug aarch64
24590 Turns on or off display of debugging messages related to ARM AArch64.
24591 The default is off.
24593 @item show debug aarch64
24594 Displays the current state of displaying debugging messages related to
24596 @cindex gdbarch debugging info
24597 @cindex architecture debugging info
24598 @item set debug arch
24599 Turns on or off display of gdbarch debugging info. The default is off
24600 @item show debug arch
24601 Displays the current state of displaying gdbarch debugging info.
24602 @item set debug aix-solib
24603 @cindex AIX shared library debugging
24604 Control display of debugging messages from the AIX shared library
24605 support module. The default is off.
24606 @item show debug aix-thread
24607 Show the current state of displaying AIX shared library debugging messages.
24608 @item set debug aix-thread
24609 @cindex AIX threads
24610 Display debugging messages about inner workings of the AIX thread
24612 @item show debug aix-thread
24613 Show the current state of AIX thread debugging info display.
24614 @item set debug check-physname
24616 Check the results of the ``physname'' computation. When reading DWARF
24617 debugging information for C@t{++}, @value{GDBN} attempts to compute
24618 each entity's name. @value{GDBN} can do this computation in two
24619 different ways, depending on exactly what information is present.
24620 When enabled, this setting causes @value{GDBN} to compute the names
24621 both ways and display any discrepancies.
24622 @item show debug check-physname
24623 Show the current state of ``physname'' checking.
24624 @item set debug coff-pe-read
24625 @cindex COFF/PE exported symbols
24626 Control display of debugging messages related to reading of COFF/PE
24627 exported symbols. The default is off.
24628 @item show debug coff-pe-read
24629 Displays the current state of displaying debugging messages related to
24630 reading of COFF/PE exported symbols.
24631 @item set debug dwarf-die
24633 Dump DWARF DIEs after they are read in.
24634 The value is the number of nesting levels to print.
24635 A value of zero turns off the display.
24636 @item show debug dwarf-die
24637 Show the current state of DWARF DIE debugging.
24638 @item set debug dwarf-line
24639 @cindex DWARF Line Tables
24640 Turns on or off display of debugging messages related to reading
24641 DWARF line tables. The default is 0 (off).
24642 A value of 1 provides basic information.
24643 A value greater than 1 provides more verbose information.
24644 @item show debug dwarf-line
24645 Show the current state of DWARF line table debugging.
24646 @item set debug dwarf-read
24647 @cindex DWARF Reading
24648 Turns on or off display of debugging messages related to reading
24649 DWARF debug info. The default is 0 (off).
24650 A value of 1 provides basic information.
24651 A value greater than 1 provides more verbose information.
24652 @item show debug dwarf-read
24653 Show the current state of DWARF reader debugging.
24654 @item set debug displaced
24655 @cindex displaced stepping debugging info
24656 Turns on or off display of @value{GDBN} debugging info for the
24657 displaced stepping support. The default is off.
24658 @item show debug displaced
24659 Displays the current state of displaying @value{GDBN} debugging info
24660 related to displaced stepping.
24661 @item set debug event
24662 @cindex event debugging info
24663 Turns on or off display of @value{GDBN} event debugging info. The
24665 @item show debug event
24666 Displays the current state of displaying @value{GDBN} event debugging
24668 @item set debug expression
24669 @cindex expression debugging info
24670 Turns on or off display of debugging info about @value{GDBN}
24671 expression parsing. The default is off.
24672 @item show debug expression
24673 Displays the current state of displaying debugging info about
24674 @value{GDBN} expression parsing.
24675 @item set debug fbsd-lwp
24676 @cindex FreeBSD LWP debug messages
24677 Turns on or off debugging messages from the FreeBSD LWP debug support.
24678 @item show debug fbsd-lwp
24679 Show the current state of FreeBSD LWP debugging messages.
24680 @item set debug fbsd-nat
24681 @cindex FreeBSD native target debug messages
24682 Turns on or off debugging messages from the FreeBSD native target.
24683 @item show debug fbsd-nat
24684 Show the current state of FreeBSD native target debugging messages.
24685 @item set debug frame
24686 @cindex frame debugging info
24687 Turns on or off display of @value{GDBN} frame debugging info. The
24689 @item show debug frame
24690 Displays the current state of displaying @value{GDBN} frame debugging
24692 @item set debug gnu-nat
24693 @cindex @sc{gnu}/Hurd debug messages
24694 Turn on or off debugging messages from the @sc{gnu}/Hurd debug support.
24695 @item show debug gnu-nat
24696 Show the current state of @sc{gnu}/Hurd debugging messages.
24697 @item set debug infrun
24698 @cindex inferior debugging info
24699 Turns on or off display of @value{GDBN} debugging info for running the inferior.
24700 The default is off. @file{infrun.c} contains GDB's runtime state machine used
24701 for implementing operations such as single-stepping the inferior.
24702 @item show debug infrun
24703 Displays the current state of @value{GDBN} inferior debugging.
24704 @item set debug jit
24705 @cindex just-in-time compilation, debugging messages
24706 Turn on or off debugging messages from JIT debug support.
24707 @item show debug jit
24708 Displays the current state of @value{GDBN} JIT debugging.
24709 @item set debug lin-lwp
24710 @cindex @sc{gnu}/Linux LWP debug messages
24711 @cindex Linux lightweight processes
24712 Turn on or off debugging messages from the Linux LWP debug support.
24713 @item show debug lin-lwp
24714 Show the current state of Linux LWP debugging messages.
24715 @item set debug linux-namespaces
24716 @cindex @sc{gnu}/Linux namespaces debug messages
24717 Turn on or off debugging messages from the Linux namespaces debug support.
24718 @item show debug linux-namespaces
24719 Show the current state of Linux namespaces debugging messages.
24720 @item set debug mach-o
24721 @cindex Mach-O symbols processing
24722 Control display of debugging messages related to Mach-O symbols
24723 processing. The default is off.
24724 @item show debug mach-o
24725 Displays the current state of displaying debugging messages related to
24726 reading of COFF/PE exported symbols.
24727 @item set debug notification
24728 @cindex remote async notification debugging info
24729 Turn on or off debugging messages about remote async notification.
24730 The default is off.
24731 @item show debug notification
24732 Displays the current state of remote async notification debugging messages.
24733 @item set debug observer
24734 @cindex observer debugging info
24735 Turns on or off display of @value{GDBN} observer debugging. This
24736 includes info such as the notification of observable events.
24737 @item show debug observer
24738 Displays the current state of observer debugging.
24739 @item set debug overload
24740 @cindex C@t{++} overload debugging info
24741 Turns on or off display of @value{GDBN} C@t{++} overload debugging
24742 info. This includes info such as ranking of functions, etc. The default
24744 @item show debug overload
24745 Displays the current state of displaying @value{GDBN} C@t{++} overload
24747 @cindex expression parser, debugging info
24748 @cindex debug expression parser
24749 @item set debug parser
24750 Turns on or off the display of expression parser debugging output.
24751 Internally, this sets the @code{yydebug} variable in the expression
24752 parser. @xref{Tracing, , Tracing Your Parser, bison, Bison}, for
24753 details. The default is off.
24754 @item show debug parser
24755 Show the current state of expression parser debugging.
24756 @cindex packets, reporting on stdout
24757 @cindex serial connections, debugging
24758 @cindex debug remote protocol
24759 @cindex remote protocol debugging
24760 @cindex display remote packets
24761 @item set debug remote
24762 Turns on or off display of reports on all packets sent back and forth across
24763 the serial line to the remote machine. The info is printed on the
24764 @value{GDBN} standard output stream. The default is off.
24765 @item show debug remote
24766 Displays the state of display of remote packets.
24768 @item set debug separate-debug-file
24769 Turns on or off display of debug output about separate debug file search.
24770 @item show debug separate-debug-file
24771 Displays the state of separate debug file search debug output.
24773 @item set debug serial
24774 Turns on or off display of @value{GDBN} serial debugging info. The
24776 @item show debug serial
24777 Displays the current state of displaying @value{GDBN} serial debugging
24779 @item set debug solib-frv
24780 @cindex FR-V shared-library debugging
24781 Turn on or off debugging messages for FR-V shared-library code.
24782 @item show debug solib-frv
24783 Display the current state of FR-V shared-library code debugging
24785 @item set debug symbol-lookup
24786 @cindex symbol lookup
24787 Turns on or off display of debugging messages related to symbol lookup.
24788 The default is 0 (off).
24789 A value of 1 provides basic information.
24790 A value greater than 1 provides more verbose information.
24791 @item show debug symbol-lookup
24792 Show the current state of symbol lookup debugging messages.
24793 @item set debug symfile
24794 @cindex symbol file functions
24795 Turns on or off display of debugging messages related to symbol file functions.
24796 The default is off. @xref{Files}.
24797 @item show debug symfile
24798 Show the current state of symbol file debugging messages.
24799 @item set debug symtab-create
24800 @cindex symbol table creation
24801 Turns on or off display of debugging messages related to symbol table creation.
24802 The default is 0 (off).
24803 A value of 1 provides basic information.
24804 A value greater than 1 provides more verbose information.
24805 @item show debug symtab-create
24806 Show the current state of symbol table creation debugging.
24807 @item set debug target
24808 @cindex target debugging info
24809 Turns on or off display of @value{GDBN} target debugging info. This info
24810 includes what is going on at the target level of GDB, as it happens. The
24811 default is 0. Set it to 1 to track events, and to 2 to also track the
24812 value of large memory transfers.
24813 @item show debug target
24814 Displays the current state of displaying @value{GDBN} target debugging
24816 @item set debug timestamp
24817 @cindex timestampping debugging info
24818 Turns on or off display of timestamps with @value{GDBN} debugging info.
24819 When enabled, seconds and microseconds are displayed before each debugging
24821 @item show debug timestamp
24822 Displays the current state of displaying timestamps with @value{GDBN}
24824 @item set debug varobj
24825 @cindex variable object debugging info
24826 Turns on or off display of @value{GDBN} variable object debugging
24827 info. The default is off.
24828 @item show debug varobj
24829 Displays the current state of displaying @value{GDBN} variable object
24831 @item set debug xml
24832 @cindex XML parser debugging
24833 Turn on or off debugging messages for built-in XML parsers.
24834 @item show debug xml
24835 Displays the current state of XML debugging messages.
24838 @node Other Misc Settings
24839 @section Other Miscellaneous Settings
24840 @cindex miscellaneous settings
24843 @kindex set interactive-mode
24844 @item set interactive-mode
24845 If @code{on}, forces @value{GDBN} to assume that GDB was started
24846 in a terminal. In practice, this means that @value{GDBN} should wait
24847 for the user to answer queries generated by commands entered at
24848 the command prompt. If @code{off}, forces @value{GDBN} to operate
24849 in the opposite mode, and it uses the default answers to all queries.
24850 If @code{auto} (the default), @value{GDBN} tries to determine whether
24851 its standard input is a terminal, and works in interactive-mode if it
24852 is, non-interactively otherwise.
24854 In the vast majority of cases, the debugger should be able to guess
24855 correctly which mode should be used. But this setting can be useful
24856 in certain specific cases, such as running a MinGW @value{GDBN}
24857 inside a cygwin window.
24859 @kindex show interactive-mode
24860 @item show interactive-mode
24861 Displays whether the debugger is operating in interactive mode or not.
24864 @node Extending GDB
24865 @chapter Extending @value{GDBN}
24866 @cindex extending GDB
24868 @value{GDBN} provides several mechanisms for extension.
24869 @value{GDBN} also provides the ability to automatically load
24870 extensions when it reads a file for debugging. This allows the
24871 user to automatically customize @value{GDBN} for the program
24875 * Sequences:: Canned Sequences of @value{GDBN} Commands
24876 * Python:: Extending @value{GDBN} using Python
24877 * Guile:: Extending @value{GDBN} using Guile
24878 * Auto-loading extensions:: Automatically loading extensions
24879 * Multiple Extension Languages:: Working with multiple extension languages
24880 * Aliases:: Creating new spellings of existing commands
24883 To facilitate the use of extension languages, @value{GDBN} is capable
24884 of evaluating the contents of a file. When doing so, @value{GDBN}
24885 can recognize which extension language is being used by looking at
24886 the filename extension. Files with an unrecognized filename extension
24887 are always treated as a @value{GDBN} Command Files.
24888 @xref{Command Files,, Command files}.
24890 You can control how @value{GDBN} evaluates these files with the following
24894 @kindex set script-extension
24895 @kindex show script-extension
24896 @item set script-extension off
24897 All scripts are always evaluated as @value{GDBN} Command Files.
24899 @item set script-extension soft
24900 The debugger determines the scripting language based on filename
24901 extension. If this scripting language is supported, @value{GDBN}
24902 evaluates the script using that language. Otherwise, it evaluates
24903 the file as a @value{GDBN} Command File.
24905 @item set script-extension strict
24906 The debugger determines the scripting language based on filename
24907 extension, and evaluates the script using that language. If the
24908 language is not supported, then the evaluation fails.
24910 @item show script-extension
24911 Display the current value of the @code{script-extension} option.
24916 @section Canned Sequences of Commands
24918 Aside from breakpoint commands (@pxref{Break Commands, ,Breakpoint
24919 Command Lists}), @value{GDBN} provides two ways to store sequences of
24920 commands for execution as a unit: user-defined commands and command
24924 * Define:: How to define your own commands
24925 * Hooks:: Hooks for user-defined commands
24926 * Command Files:: How to write scripts of commands to be stored in a file
24927 * Output:: Commands for controlled output
24928 * Auto-loading sequences:: Controlling auto-loaded command files
24932 @subsection User-defined Commands
24934 @cindex user-defined command
24935 @cindex arguments, to user-defined commands
24936 A @dfn{user-defined command} is a sequence of @value{GDBN} commands to
24937 which you assign a new name as a command. This is done with the
24938 @code{define} command. User commands may accept an unlimited number of arguments
24939 separated by whitespace. Arguments are accessed within the user command
24940 via @code{$arg0@dots{}$argN}. A trivial example:
24944 print $arg0 + $arg1 + $arg2
24949 To execute the command use:
24956 This defines the command @code{adder}, which prints the sum of
24957 its three arguments. Note the arguments are text substitutions, so they may
24958 reference variables, use complex expressions, or even perform inferior
24961 @cindex argument count in user-defined commands
24962 @cindex how many arguments (user-defined commands)
24963 In addition, @code{$argc} may be used to find out how many arguments have
24969 print $arg0 + $arg1
24972 print $arg0 + $arg1 + $arg2
24977 Combining with the @code{eval} command (@pxref{eval}) makes it easier
24978 to process a variable number of arguments:
24985 eval "set $sum = $sum + $arg%d", $i
24995 @item define @var{commandname}
24996 Define a command named @var{commandname}. If there is already a command
24997 by that name, you are asked to confirm that you want to redefine it.
24998 The argument @var{commandname} may be a bare command name consisting of letters,
24999 numbers, dashes, and underscores. It may also start with any predefined
25000 prefix command. For example, @samp{define target my-target} creates
25001 a user-defined @samp{target my-target} command.
25003 The definition of the command is made up of other @value{GDBN} command lines,
25004 which are given following the @code{define} command. The end of these
25005 commands is marked by a line containing @code{end}.
25008 @kindex end@r{ (user-defined commands)}
25009 @item document @var{commandname}
25010 Document the user-defined command @var{commandname}, so that it can be
25011 accessed by @code{help}. The command @var{commandname} must already be
25012 defined. This command reads lines of documentation just as @code{define}
25013 reads the lines of the command definition, ending with @code{end}.
25014 After the @code{document} command is finished, @code{help} on command
25015 @var{commandname} displays the documentation you have written.
25017 You may use the @code{document} command again to change the
25018 documentation of a command. Redefining the command with @code{define}
25019 does not change the documentation.
25021 @kindex dont-repeat
25022 @cindex don't repeat command
25024 Used inside a user-defined command, this tells @value{GDBN} that this
25025 command should not be repeated when the user hits @key{RET}
25026 (@pxref{Command Syntax, repeat last command}).
25028 @kindex help user-defined
25029 @item help user-defined
25030 List all user-defined commands and all python commands defined in class
25031 COMAND_USER. The first line of the documentation or docstring is
25036 @itemx show user @var{commandname}
25037 Display the @value{GDBN} commands used to define @var{commandname} (but
25038 not its documentation). If no @var{commandname} is given, display the
25039 definitions for all user-defined commands.
25040 This does not work for user-defined python commands.
25042 @cindex infinite recursion in user-defined commands
25043 @kindex show max-user-call-depth
25044 @kindex set max-user-call-depth
25045 @item show max-user-call-depth
25046 @itemx set max-user-call-depth
25047 The value of @code{max-user-call-depth} controls how many recursion
25048 levels are allowed in user-defined commands before @value{GDBN} suspects an
25049 infinite recursion and aborts the command.
25050 This does not apply to user-defined python commands.
25053 In addition to the above commands, user-defined commands frequently
25054 use control flow commands, described in @ref{Command Files}.
25056 When user-defined commands are executed, the
25057 commands of the definition are not printed. An error in any command
25058 stops execution of the user-defined command.
25060 If used interactively, commands that would ask for confirmation proceed
25061 without asking when used inside a user-defined command. Many @value{GDBN}
25062 commands that normally print messages to say what they are doing omit the
25063 messages when used in a user-defined command.
25066 @subsection User-defined Command Hooks
25067 @cindex command hooks
25068 @cindex hooks, for commands
25069 @cindex hooks, pre-command
25072 You may define @dfn{hooks}, which are a special kind of user-defined
25073 command. Whenever you run the command @samp{foo}, if the user-defined
25074 command @samp{hook-foo} exists, it is executed (with no arguments)
25075 before that command.
25077 @cindex hooks, post-command
25079 A hook may also be defined which is run after the command you executed.
25080 Whenever you run the command @samp{foo}, if the user-defined command
25081 @samp{hookpost-foo} exists, it is executed (with no arguments) after
25082 that command. Post-execution hooks may exist simultaneously with
25083 pre-execution hooks, for the same command.
25085 It is valid for a hook to call the command which it hooks. If this
25086 occurs, the hook is not re-executed, thereby avoiding infinite recursion.
25088 @c It would be nice if hookpost could be passed a parameter indicating
25089 @c if the command it hooks executed properly or not. FIXME!
25091 @kindex stop@r{, a pseudo-command}
25092 In addition, a pseudo-command, @samp{stop} exists. Defining
25093 (@samp{hook-stop}) makes the associated commands execute every time
25094 execution stops in your program: before breakpoint commands are run,
25095 displays are printed, or the stack frame is printed.
25097 For example, to ignore @code{SIGALRM} signals while
25098 single-stepping, but treat them normally during normal execution,
25103 handle SIGALRM nopass
25107 handle SIGALRM pass
25110 define hook-continue
25111 handle SIGALRM pass
25115 As a further example, to hook at the beginning and end of the @code{echo}
25116 command, and to add extra text to the beginning and end of the message,
25124 define hookpost-echo
25128 (@value{GDBP}) echo Hello World
25129 <<<---Hello World--->>>
25134 You can define a hook for any single-word command in @value{GDBN}, but
25135 not for command aliases; you should define a hook for the basic command
25136 name, e.g.@: @code{backtrace} rather than @code{bt}.
25137 @c FIXME! So how does Joe User discover whether a command is an alias
25139 You can hook a multi-word command by adding @code{hook-} or
25140 @code{hookpost-} to the last word of the command, e.g.@:
25141 @samp{define target hook-remote} to add a hook to @samp{target remote}.
25143 If an error occurs during the execution of your hook, execution of
25144 @value{GDBN} commands stops and @value{GDBN} issues a prompt
25145 (before the command that you actually typed had a chance to run).
25147 If you try to define a hook which does not match any known command, you
25148 get a warning from the @code{define} command.
25150 @node Command Files
25151 @subsection Command Files
25153 @cindex command files
25154 @cindex scripting commands
25155 A command file for @value{GDBN} is a text file made of lines that are
25156 @value{GDBN} commands. Comments (lines starting with @kbd{#}) may
25157 also be included. An empty line in a command file does nothing; it
25158 does not mean to repeat the last command, as it would from the
25161 You can request the execution of a command file with the @code{source}
25162 command. Note that the @code{source} command is also used to evaluate
25163 scripts that are not Command Files. The exact behavior can be configured
25164 using the @code{script-extension} setting.
25165 @xref{Extending GDB,, Extending GDB}.
25169 @cindex execute commands from a file
25170 @item source [-s] [-v] @var{filename}
25171 Execute the command file @var{filename}.
25174 The lines in a command file are generally executed sequentially,
25175 unless the order of execution is changed by one of the
25176 @emph{flow-control commands} described below. The commands are not
25177 printed as they are executed. An error in any command terminates
25178 execution of the command file and control is returned to the console.
25180 @value{GDBN} first searches for @var{filename} in the current directory.
25181 If the file is not found there, and @var{filename} does not specify a
25182 directory, then @value{GDBN} also looks for the file on the source search path
25183 (specified with the @samp{directory} command);
25184 except that @file{$cdir} is not searched because the compilation directory
25185 is not relevant to scripts.
25187 If @code{-s} is specified, then @value{GDBN} searches for @var{filename}
25188 on the search path even if @var{filename} specifies a directory.
25189 The search is done by appending @var{filename} to each element of the
25190 search path. So, for example, if @var{filename} is @file{mylib/myscript}
25191 and the search path contains @file{/home/user} then @value{GDBN} will
25192 look for the script @file{/home/user/mylib/myscript}.
25193 The search is also done if @var{filename} is an absolute path.
25194 For example, if @var{filename} is @file{/tmp/myscript} and
25195 the search path contains @file{/home/user} then @value{GDBN} will
25196 look for the script @file{/home/user/tmp/myscript}.
25197 For DOS-like systems, if @var{filename} contains a drive specification,
25198 it is stripped before concatenation. For example, if @var{filename} is
25199 @file{d:myscript} and the search path contains @file{c:/tmp} then @value{GDBN}
25200 will look for the script @file{c:/tmp/myscript}.
25202 If @code{-v}, for verbose mode, is given then @value{GDBN} displays
25203 each command as it is executed. The option must be given before
25204 @var{filename}, and is interpreted as part of the filename anywhere else.
25206 Commands that would ask for confirmation if used interactively proceed
25207 without asking when used in a command file. Many @value{GDBN} commands that
25208 normally print messages to say what they are doing omit the messages
25209 when called from command files.
25211 @value{GDBN} also accepts command input from standard input. In this
25212 mode, normal output goes to standard output and error output goes to
25213 standard error. Errors in a command file supplied on standard input do
25214 not terminate execution of the command file---execution continues with
25218 gdb < cmds > log 2>&1
25221 (The syntax above will vary depending on the shell used.) This example
25222 will execute commands from the file @file{cmds}. All output and errors
25223 would be directed to @file{log}.
25225 Since commands stored on command files tend to be more general than
25226 commands typed interactively, they frequently need to deal with
25227 complicated situations, such as different or unexpected values of
25228 variables and symbols, changes in how the program being debugged is
25229 built, etc. @value{GDBN} provides a set of flow-control commands to
25230 deal with these complexities. Using these commands, you can write
25231 complex scripts that loop over data structures, execute commands
25232 conditionally, etc.
25239 This command allows to include in your script conditionally executed
25240 commands. The @code{if} command takes a single argument, which is an
25241 expression to evaluate. It is followed by a series of commands that
25242 are executed only if the expression is true (its value is nonzero).
25243 There can then optionally be an @code{else} line, followed by a series
25244 of commands that are only executed if the expression was false. The
25245 end of the list is marked by a line containing @code{end}.
25249 This command allows to write loops. Its syntax is similar to
25250 @code{if}: the command takes a single argument, which is an expression
25251 to evaluate, and must be followed by the commands to execute, one per
25252 line, terminated by an @code{end}. These commands are called the
25253 @dfn{body} of the loop. The commands in the body of @code{while} are
25254 executed repeatedly as long as the expression evaluates to true.
25258 This command exits the @code{while} loop in whose body it is included.
25259 Execution of the script continues after that @code{while}s @code{end}
25262 @kindex loop_continue
25263 @item loop_continue
25264 This command skips the execution of the rest of the body of commands
25265 in the @code{while} loop in whose body it is included. Execution
25266 branches to the beginning of the @code{while} loop, where it evaluates
25267 the controlling expression.
25269 @kindex end@r{ (if/else/while commands)}
25271 Terminate the block of commands that are the body of @code{if},
25272 @code{else}, or @code{while} flow-control commands.
25277 @subsection Commands for Controlled Output
25279 During the execution of a command file or a user-defined command, normal
25280 @value{GDBN} output is suppressed; the only output that appears is what is
25281 explicitly printed by the commands in the definition. This section
25282 describes three commands useful for generating exactly the output you
25287 @item echo @var{text}
25288 @c I do not consider backslash-space a standard C escape sequence
25289 @c because it is not in ANSI.
25290 Print @var{text}. Nonprinting characters can be included in
25291 @var{text} using C escape sequences, such as @samp{\n} to print a
25292 newline. @strong{No newline is printed unless you specify one.}
25293 In addition to the standard C escape sequences, a backslash followed
25294 by a space stands for a space. This is useful for displaying a
25295 string with spaces at the beginning or the end, since leading and
25296 trailing spaces are otherwise trimmed from all arguments.
25297 To print @samp{@w{ }and foo =@w{ }}, use the command
25298 @samp{echo \@w{ }and foo = \@w{ }}.
25300 A backslash at the end of @var{text} can be used, as in C, to continue
25301 the command onto subsequent lines. For example,
25304 echo This is some text\n\
25305 which is continued\n\
25306 onto several lines.\n
25309 produces the same output as
25312 echo This is some text\n
25313 echo which is continued\n
25314 echo onto several lines.\n
25318 @item output @var{expression}
25319 Print the value of @var{expression} and nothing but that value: no
25320 newlines, no @samp{$@var{nn} = }. The value is not entered in the
25321 value history either. @xref{Expressions, ,Expressions}, for more information
25324 @item output/@var{fmt} @var{expression}
25325 Print the value of @var{expression} in format @var{fmt}. You can use
25326 the same formats as for @code{print}. @xref{Output Formats,,Output
25327 Formats}, for more information.
25330 @item printf @var{template}, @var{expressions}@dots{}
25331 Print the values of one or more @var{expressions} under the control of
25332 the string @var{template}. To print several values, make
25333 @var{expressions} be a comma-separated list of individual expressions,
25334 which may be either numbers or pointers. Their values are printed as
25335 specified by @var{template}, exactly as a C program would do by
25336 executing the code below:
25339 printf (@var{template}, @var{expressions}@dots{});
25342 As in @code{C} @code{printf}, ordinary characters in @var{template}
25343 are printed verbatim, while @dfn{conversion specification} introduced
25344 by the @samp{%} character cause subsequent @var{expressions} to be
25345 evaluated, their values converted and formatted according to type and
25346 style information encoded in the conversion specifications, and then
25349 For example, you can print two values in hex like this:
25352 printf "foo, bar-foo = 0x%x, 0x%x\n", foo, bar-foo
25355 @code{printf} supports all the standard @code{C} conversion
25356 specifications, including the flags and modifiers between the @samp{%}
25357 character and the conversion letter, with the following exceptions:
25361 The argument-ordering modifiers, such as @samp{2$}, are not supported.
25364 The modifier @samp{*} is not supported for specifying precision or
25368 The @samp{'} flag (for separation of digits into groups according to
25369 @code{LC_NUMERIC'}) is not supported.
25372 The type modifiers @samp{hh}, @samp{j}, @samp{t}, and @samp{z} are not
25376 The conversion letter @samp{n} (as in @samp{%n}) is not supported.
25379 The conversion letters @samp{a} and @samp{A} are not supported.
25383 Note that the @samp{ll} type modifier is supported only if the
25384 underlying @code{C} implementation used to build @value{GDBN} supports
25385 the @code{long long int} type, and the @samp{L} type modifier is
25386 supported only if @code{long double} type is available.
25388 As in @code{C}, @code{printf} supports simple backslash-escape
25389 sequences, such as @code{\n}, @samp{\t}, @samp{\\}, @samp{\"},
25390 @samp{\a}, and @samp{\f}, that consist of backslash followed by a
25391 single character. Octal and hexadecimal escape sequences are not
25394 Additionally, @code{printf} supports conversion specifications for DFP
25395 (@dfn{Decimal Floating Point}) types using the following length modifiers
25396 together with a floating point specifier.
25401 @samp{H} for printing @code{Decimal32} types.
25404 @samp{D} for printing @code{Decimal64} types.
25407 @samp{DD} for printing @code{Decimal128} types.
25410 If the underlying @code{C} implementation used to build @value{GDBN} has
25411 support for the three length modifiers for DFP types, other modifiers
25412 such as width and precision will also be available for @value{GDBN} to use.
25414 In case there is no such @code{C} support, no additional modifiers will be
25415 available and the value will be printed in the standard way.
25417 Here's an example of printing DFP types using the above conversion letters:
25419 printf "D32: %Hf - D64: %Df - D128: %DDf\n",1.2345df,1.2E10dd,1.2E1dl
25424 @item eval @var{template}, @var{expressions}@dots{}
25425 Convert the values of one or more @var{expressions} under the control of
25426 the string @var{template} to a command line, and call it.
25430 @node Auto-loading sequences
25431 @subsection Controlling auto-loading native @value{GDBN} scripts
25432 @cindex native script auto-loading
25434 When a new object file is read (for example, due to the @code{file}
25435 command, or because the inferior has loaded a shared library),
25436 @value{GDBN} will look for the command file @file{@var{objfile}-gdb.gdb}.
25437 @xref{Auto-loading extensions}.
25439 Auto-loading can be enabled or disabled,
25440 and the list of auto-loaded scripts can be printed.
25443 @anchor{set auto-load gdb-scripts}
25444 @kindex set auto-load gdb-scripts
25445 @item set auto-load gdb-scripts [on|off]
25446 Enable or disable the auto-loading of canned sequences of commands scripts.
25448 @anchor{show auto-load gdb-scripts}
25449 @kindex show auto-load gdb-scripts
25450 @item show auto-load gdb-scripts
25451 Show whether auto-loading of canned sequences of commands scripts is enabled or
25454 @anchor{info auto-load gdb-scripts}
25455 @kindex info auto-load gdb-scripts
25456 @cindex print list of auto-loaded canned sequences of commands scripts
25457 @item info auto-load gdb-scripts [@var{regexp}]
25458 Print the list of all canned sequences of commands scripts that @value{GDBN}
25462 If @var{regexp} is supplied only canned sequences of commands scripts with
25463 matching names are printed.
25465 @c Python docs live in a separate file.
25466 @include python.texi
25468 @c Guile docs live in a separate file.
25469 @include guile.texi
25471 @node Auto-loading extensions
25472 @section Auto-loading extensions
25473 @cindex auto-loading extensions
25475 @value{GDBN} provides two mechanisms for automatically loading extensions
25476 when a new object file is read (for example, due to the @code{file}
25477 command, or because the inferior has loaded a shared library):
25478 @file{@var{objfile}-gdb.@var{ext}} and the @code{.debug_gdb_scripts}
25479 section of modern file formats like ELF.
25482 * objfile-gdb.ext file: objfile-gdbdotext file. The @file{@var{objfile}-gdb.@var{ext}} file
25483 * .debug_gdb_scripts section: dotdebug_gdb_scripts section. The @code{.debug_gdb_scripts} section
25484 * Which flavor to choose?::
25487 The auto-loading feature is useful for supplying application-specific
25488 debugging commands and features.
25490 Auto-loading can be enabled or disabled,
25491 and the list of auto-loaded scripts can be printed.
25492 See the @samp{auto-loading} section of each extension language
25493 for more information.
25494 For @value{GDBN} command files see @ref{Auto-loading sequences}.
25495 For Python files see @ref{Python Auto-loading}.
25497 Note that loading of this script file also requires accordingly configured
25498 @code{auto-load safe-path} (@pxref{Auto-loading safe path}).
25500 @node objfile-gdbdotext file
25501 @subsection The @file{@var{objfile}-gdb.@var{ext}} file
25502 @cindex @file{@var{objfile}-gdb.gdb}
25503 @cindex @file{@var{objfile}-gdb.py}
25504 @cindex @file{@var{objfile}-gdb.scm}
25506 When a new object file is read, @value{GDBN} looks for a file named
25507 @file{@var{objfile}-gdb.@var{ext}} (we call it @var{script-name} below),
25508 where @var{objfile} is the object file's name and
25509 where @var{ext} is the file extension for the extension language:
25512 @item @file{@var{objfile}-gdb.gdb}
25513 GDB's own command language
25514 @item @file{@var{objfile}-gdb.py}
25516 @item @file{@var{objfile}-gdb.scm}
25520 @var{script-name} is formed by ensuring that the file name of @var{objfile}
25521 is absolute, following all symlinks, and resolving @code{.} and @code{..}
25522 components, and appending the @file{-gdb.@var{ext}} suffix.
25523 If this file exists and is readable, @value{GDBN} will evaluate it as a
25524 script in the specified extension language.
25526 If this file does not exist, then @value{GDBN} will look for
25527 @var{script-name} file in all of the directories as specified below.
25529 Note that loading of these files requires an accordingly configured
25530 @code{auto-load safe-path} (@pxref{Auto-loading safe path}).
25532 For object files using @file{.exe} suffix @value{GDBN} tries to load first the
25533 scripts normally according to its @file{.exe} filename. But if no scripts are
25534 found @value{GDBN} also tries script filenames matching the object file without
25535 its @file{.exe} suffix. This @file{.exe} stripping is case insensitive and it
25536 is attempted on any platform. This makes the script filenames compatible
25537 between Unix and MS-Windows hosts.
25540 @anchor{set auto-load scripts-directory}
25541 @kindex set auto-load scripts-directory
25542 @item set auto-load scripts-directory @r{[}@var{directories}@r{]}
25543 Control @value{GDBN} auto-loaded scripts location. Multiple directory entries
25544 may be delimited by the host platform path separator in use
25545 (@samp{:} on Unix, @samp{;} on MS-Windows and MS-DOS).
25547 Each entry here needs to be covered also by the security setting
25548 @code{set auto-load safe-path} (@pxref{set auto-load safe-path}).
25550 @anchor{with-auto-load-dir}
25551 This variable defaults to @file{$debugdir:$datadir/auto-load}. The default
25552 @code{set auto-load safe-path} value can be also overriden by @value{GDBN}
25553 configuration option @option{--with-auto-load-dir}.
25555 Any reference to @file{$debugdir} will get replaced by
25556 @var{debug-file-directory} value (@pxref{Separate Debug Files}) and any
25557 reference to @file{$datadir} will get replaced by @var{data-directory} which is
25558 determined at @value{GDBN} startup (@pxref{Data Files}). @file{$debugdir} and
25559 @file{$datadir} must be placed as a directory component --- either alone or
25560 delimited by @file{/} or @file{\} directory separators, depending on the host
25563 The list of directories uses path separator (@samp{:} on GNU and Unix
25564 systems, @samp{;} on MS-Windows and MS-DOS) to separate directories, similarly
25565 to the @env{PATH} environment variable.
25567 @anchor{show auto-load scripts-directory}
25568 @kindex show auto-load scripts-directory
25569 @item show auto-load scripts-directory
25570 Show @value{GDBN} auto-loaded scripts location.
25572 @anchor{add-auto-load-scripts-directory}
25573 @kindex add-auto-load-scripts-directory
25574 @item add-auto-load-scripts-directory @r{[}@var{directories}@dots{}@r{]}
25575 Add an entry (or list of entries) to the list of auto-loaded scripts locations.
25576 Multiple entries may be delimited by the host platform path separator in use.
25579 @value{GDBN} does not track which files it has already auto-loaded this way.
25580 @value{GDBN} will load the associated script every time the corresponding
25581 @var{objfile} is opened.
25582 So your @file{-gdb.@var{ext}} file should be careful to avoid errors if it
25583 is evaluated more than once.
25585 @node dotdebug_gdb_scripts section
25586 @subsection The @code{.debug_gdb_scripts} section
25587 @cindex @code{.debug_gdb_scripts} section
25589 For systems using file formats like ELF and COFF,
25590 when @value{GDBN} loads a new object file
25591 it will look for a special section named @code{.debug_gdb_scripts}.
25592 If this section exists, its contents is a list of null-terminated entries
25593 specifying scripts to load. Each entry begins with a non-null prefix byte that
25594 specifies the kind of entry, typically the extension language and whether the
25595 script is in a file or inlined in @code{.debug_gdb_scripts}.
25597 The following entries are supported:
25600 @item SECTION_SCRIPT_ID_PYTHON_FILE = 1
25601 @item SECTION_SCRIPT_ID_SCHEME_FILE = 3
25602 @item SECTION_SCRIPT_ID_PYTHON_TEXT = 4
25603 @item SECTION_SCRIPT_ID_SCHEME_TEXT = 6
25606 @subsubsection Script File Entries
25608 If the entry specifies a file, @value{GDBN} will look for the file first
25609 in the current directory and then along the source search path
25610 (@pxref{Source Path, ,Specifying Source Directories}),
25611 except that @file{$cdir} is not searched, since the compilation
25612 directory is not relevant to scripts.
25614 File entries can be placed in section @code{.debug_gdb_scripts} with,
25615 for example, this GCC macro for Python scripts.
25618 /* Note: The "MS" section flags are to remove duplicates. */
25619 #define DEFINE_GDB_PY_SCRIPT(script_name) \
25621 .pushsection \".debug_gdb_scripts\", \"MS\",@@progbits,1\n\
25622 .byte 1 /* Python */\n\
25623 .asciz \"" script_name "\"\n\
25629 For Guile scripts, replace @code{.byte 1} with @code{.byte 3}.
25630 Then one can reference the macro in a header or source file like this:
25633 DEFINE_GDB_PY_SCRIPT ("my-app-scripts.py")
25636 The script name may include directories if desired.
25638 Note that loading of this script file also requires accordingly configured
25639 @code{auto-load safe-path} (@pxref{Auto-loading safe path}).
25641 If the macro invocation is put in a header, any application or library
25642 using this header will get a reference to the specified script,
25643 and with the use of @code{"MS"} attributes on the section, the linker
25644 will remove duplicates.
25646 @subsubsection Script Text Entries
25648 Script text entries allow to put the executable script in the entry
25649 itself instead of loading it from a file.
25650 The first line of the entry, everything after the prefix byte and up to
25651 the first newline (@code{0xa}) character, is the script name, and must not
25652 contain any kind of space character, e.g., spaces or tabs.
25653 The rest of the entry, up to the trailing null byte, is the script to
25654 execute in the specified language. The name needs to be unique among
25655 all script names, as @value{GDBN} executes each script only once based
25658 Here is an example from file @file{py-section-script.c} in the @value{GDBN}
25662 #include "symcat.h"
25663 #include "gdb/section-scripts.h"
25665 ".pushsection \".debug_gdb_scripts\", \"MS\",@@progbits,1\n"
25666 ".byte " XSTRING (SECTION_SCRIPT_ID_PYTHON_TEXT) "\n"
25667 ".ascii \"gdb.inlined-script\\n\"\n"
25668 ".ascii \"class test_cmd (gdb.Command):\\n\"\n"
25669 ".ascii \" def __init__ (self):\\n\"\n"
25670 ".ascii \" super (test_cmd, self).__init__ ("
25671 "\\\"test-cmd\\\", gdb.COMMAND_OBSCURE)\\n\"\n"
25672 ".ascii \" def invoke (self, arg, from_tty):\\n\"\n"
25673 ".ascii \" print (\\\"test-cmd output, arg = %s\\\" % arg)\\n\"\n"
25674 ".ascii \"test_cmd ()\\n\"\n"
25680 Loading of inlined scripts requires a properly configured
25681 @code{auto-load safe-path} (@pxref{Auto-loading safe path}).
25682 The path to specify in @code{auto-load safe-path} is the path of the file
25683 containing the @code{.debug_gdb_scripts} section.
25685 @node Which flavor to choose?
25686 @subsection Which flavor to choose?
25688 Given the multiple ways of auto-loading extensions, it might not always
25689 be clear which one to choose. This section provides some guidance.
25692 Benefits of the @file{-gdb.@var{ext}} way:
25696 Can be used with file formats that don't support multiple sections.
25699 Ease of finding scripts for public libraries.
25701 Scripts specified in the @code{.debug_gdb_scripts} section are searched for
25702 in the source search path.
25703 For publicly installed libraries, e.g., @file{libstdc++}, there typically
25704 isn't a source directory in which to find the script.
25707 Doesn't require source code additions.
25711 Benefits of the @code{.debug_gdb_scripts} way:
25715 Works with static linking.
25717 Scripts for libraries done the @file{-gdb.@var{ext}} way require an objfile to
25718 trigger their loading. When an application is statically linked the only
25719 objfile available is the executable, and it is cumbersome to attach all the
25720 scripts from all the input libraries to the executable's
25721 @file{-gdb.@var{ext}} script.
25724 Works with classes that are entirely inlined.
25726 Some classes can be entirely inlined, and thus there may not be an associated
25727 shared library to attach a @file{-gdb.@var{ext}} script to.
25730 Scripts needn't be copied out of the source tree.
25732 In some circumstances, apps can be built out of large collections of internal
25733 libraries, and the build infrastructure necessary to install the
25734 @file{-gdb.@var{ext}} scripts in a place where @value{GDBN} can find them is
25735 cumbersome. It may be easier to specify the scripts in the
25736 @code{.debug_gdb_scripts} section as relative paths, and add a path to the
25737 top of the source tree to the source search path.
25740 @node Multiple Extension Languages
25741 @section Multiple Extension Languages
25743 The Guile and Python extension languages do not share any state,
25744 and generally do not interfere with each other.
25745 There are some things to be aware of, however.
25747 @subsection Python comes first
25749 Python was @value{GDBN}'s first extension language, and to avoid breaking
25750 existing behaviour Python comes first. This is generally solved by the
25751 ``first one wins'' principle. @value{GDBN} maintains a list of enabled
25752 extension languages, and when it makes a call to an extension language,
25753 (say to pretty-print a value), it tries each in turn until an extension
25754 language indicates it has performed the request (e.g., has returned the
25755 pretty-printed form of a value).
25756 This extends to errors while performing such requests: If an error happens
25757 while, for example, trying to pretty-print an object then the error is
25758 reported and any following extension languages are not tried.
25761 @section Creating new spellings of existing commands
25762 @cindex aliases for commands
25764 It is often useful to define alternate spellings of existing commands.
25765 For example, if a new @value{GDBN} command defined in Python has
25766 a long name to type, it is handy to have an abbreviated version of it
25767 that involves less typing.
25769 @value{GDBN} itself uses aliases. For example @samp{s} is an alias
25770 of the @samp{step} command even though it is otherwise an ambiguous
25771 abbreviation of other commands like @samp{set} and @samp{show}.
25773 Aliases are also used to provide shortened or more common versions
25774 of multi-word commands. For example, @value{GDBN} provides the
25775 @samp{tty} alias of the @samp{set inferior-tty} command.
25777 You can define a new alias with the @samp{alias} command.
25782 @item alias [-a] [--] @var{ALIAS} = @var{COMMAND}
25786 @var{ALIAS} specifies the name of the new alias.
25787 Each word of @var{ALIAS} must consist of letters, numbers, dashes and
25790 @var{COMMAND} specifies the name of an existing command
25791 that is being aliased.
25793 The @samp{-a} option specifies that the new alias is an abbreviation
25794 of the command. Abbreviations are not shown in command
25795 lists displayed by the @samp{help} command.
25797 The @samp{--} option specifies the end of options,
25798 and is useful when @var{ALIAS} begins with a dash.
25800 Here is a simple example showing how to make an abbreviation
25801 of a command so that there is less to type.
25802 Suppose you were tired of typing @samp{disas}, the current
25803 shortest unambiguous abbreviation of the @samp{disassemble} command
25804 and you wanted an even shorter version named @samp{di}.
25805 The following will accomplish this.
25808 (gdb) alias -a di = disas
25811 Note that aliases are different from user-defined commands.
25812 With a user-defined command, you also need to write documentation
25813 for it with the @samp{document} command.
25814 An alias automatically picks up the documentation of the existing command.
25816 Here is an example where we make @samp{elms} an abbreviation of
25817 @samp{elements} in the @samp{set print elements} command.
25818 This is to show that you can make an abbreviation of any part
25822 (gdb) alias -a set print elms = set print elements
25823 (gdb) alias -a show print elms = show print elements
25824 (gdb) set p elms 20
25826 Limit on string chars or array elements to print is 200.
25829 Note that if you are defining an alias of a @samp{set} command,
25830 and you want to have an alias for the corresponding @samp{show}
25831 command, then you need to define the latter separately.
25833 Unambiguously abbreviated commands are allowed in @var{COMMAND} and
25834 @var{ALIAS}, just as they are normally.
25837 (gdb) alias -a set pr elms = set p ele
25840 Finally, here is an example showing the creation of a one word
25841 alias for a more complex command.
25842 This creates alias @samp{spe} of the command @samp{set print elements}.
25845 (gdb) alias spe = set print elements
25850 @chapter Command Interpreters
25851 @cindex command interpreters
25853 @value{GDBN} supports multiple command interpreters, and some command
25854 infrastructure to allow users or user interface writers to switch
25855 between interpreters or run commands in other interpreters.
25857 @value{GDBN} currently supports two command interpreters, the console
25858 interpreter (sometimes called the command-line interpreter or @sc{cli})
25859 and the machine interface interpreter (or @sc{gdb/mi}). This manual
25860 describes both of these interfaces in great detail.
25862 By default, @value{GDBN} will start with the console interpreter.
25863 However, the user may choose to start @value{GDBN} with another
25864 interpreter by specifying the @option{-i} or @option{--interpreter}
25865 startup options. Defined interpreters include:
25869 @cindex console interpreter
25870 The traditional console or command-line interpreter. This is the most often
25871 used interpreter with @value{GDBN}. With no interpreter specified at runtime,
25872 @value{GDBN} will use this interpreter.
25875 @cindex mi interpreter
25876 The newest @sc{gdb/mi} interface (currently @code{mi2}). Used primarily
25877 by programs wishing to use @value{GDBN} as a backend for a debugger GUI
25878 or an IDE. For more information, see @ref{GDB/MI, ,The @sc{gdb/mi}
25882 @cindex mi2 interpreter
25883 The current @sc{gdb/mi} interface.
25886 @cindex mi1 interpreter
25887 The @sc{gdb/mi} interface included in @value{GDBN} 5.1, 5.2, and 5.3.
25891 @cindex invoke another interpreter
25893 @kindex interpreter-exec
25894 You may execute commands in any interpreter from the current
25895 interpreter using the appropriate command. If you are running the
25896 console interpreter, simply use the @code{interpreter-exec} command:
25899 interpreter-exec mi "-data-list-register-names"
25902 @sc{gdb/mi} has a similar command, although it is only available in versions of
25903 @value{GDBN} which support @sc{gdb/mi} version 2 (or greater).
25905 Note that @code{interpreter-exec} only changes the interpreter for the
25906 duration of the specified command. It does not change the interpreter
25909 @cindex start a new independent interpreter
25911 Although you may only choose a single interpreter at startup, it is
25912 possible to run an independent interpreter on a specified input/output
25913 device (usually a tty).
25915 For example, consider a debugger GUI or IDE that wants to provide a
25916 @value{GDBN} console view. It may do so by embedding a terminal
25917 emulator widget in its GUI, starting @value{GDBN} in the traditional
25918 command-line mode with stdin/stdout/stderr redirected to that
25919 terminal, and then creating an MI interpreter running on a specified
25920 input/output device. The console interpreter created by @value{GDBN}
25921 at startup handles commands the user types in the terminal widget,
25922 while the GUI controls and synchronizes state with @value{GDBN} using
25923 the separate MI interpreter.
25925 To start a new secondary @dfn{user interface} running MI, use the
25926 @code{new-ui} command:
25929 @cindex new user interface
25931 new-ui @var{interpreter} @var{tty}
25934 The @var{interpreter} parameter specifies the interpreter to run.
25935 This accepts the same values as the @code{interpreter-exec} command.
25936 For example, @samp{console}, @samp{mi}, @samp{mi2}, etc. The
25937 @var{tty} parameter specifies the name of the bidirectional file the
25938 interpreter uses for input/output, usually the name of a
25939 pseudoterminal slave on Unix systems. For example:
25942 (@value{GDBP}) new-ui mi /dev/pts/9
25946 runs an MI interpreter on @file{/dev/pts/9}.
25949 @chapter @value{GDBN} Text User Interface
25951 @cindex Text User Interface
25954 * TUI Overview:: TUI overview
25955 * TUI Keys:: TUI key bindings
25956 * TUI Single Key Mode:: TUI single key mode
25957 * TUI Commands:: TUI-specific commands
25958 * TUI Configuration:: TUI configuration variables
25961 The @value{GDBN} Text User Interface (TUI) is a terminal
25962 interface which uses the @code{curses} library to show the source
25963 file, the assembly output, the program registers and @value{GDBN}
25964 commands in separate text windows. The TUI mode is supported only
25965 on platforms where a suitable version of the @code{curses} library
25968 The TUI mode is enabled by default when you invoke @value{GDBN} as
25969 @samp{@value{GDBP} -tui}.
25970 You can also switch in and out of TUI mode while @value{GDBN} runs by
25971 using various TUI commands and key bindings, such as @command{tui
25972 enable} or @kbd{C-x C-a}. @xref{TUI Commands, ,TUI Commands}, and
25973 @ref{TUI Keys, ,TUI Key Bindings}.
25976 @section TUI Overview
25978 In TUI mode, @value{GDBN} can display several text windows:
25982 This window is the @value{GDBN} command window with the @value{GDBN}
25983 prompt and the @value{GDBN} output. The @value{GDBN} input is still
25984 managed using readline.
25987 The source window shows the source file of the program. The current
25988 line and active breakpoints are displayed in this window.
25991 The assembly window shows the disassembly output of the program.
25994 This window shows the processor registers. Registers are highlighted
25995 when their values change.
25998 The source and assembly windows show the current program position
25999 by highlighting the current line and marking it with a @samp{>} marker.
26000 Breakpoints are indicated with two markers. The first marker
26001 indicates the breakpoint type:
26005 Breakpoint which was hit at least once.
26008 Breakpoint which was never hit.
26011 Hardware breakpoint which was hit at least once.
26014 Hardware breakpoint which was never hit.
26017 The second marker indicates whether the breakpoint is enabled or not:
26021 Breakpoint is enabled.
26024 Breakpoint is disabled.
26027 The source, assembly and register windows are updated when the current
26028 thread changes, when the frame changes, or when the program counter
26031 These windows are not all visible at the same time. The command
26032 window is always visible. The others can be arranged in several
26043 source and assembly,
26046 source and registers, or
26049 assembly and registers.
26052 A status line above the command window shows the following information:
26056 Indicates the current @value{GDBN} target.
26057 (@pxref{Targets, ,Specifying a Debugging Target}).
26060 Gives the current process or thread number.
26061 When no process is being debugged, this field is set to @code{No process}.
26064 Gives the current function name for the selected frame.
26065 The name is demangled if demangling is turned on (@pxref{Print Settings}).
26066 When there is no symbol corresponding to the current program counter,
26067 the string @code{??} is displayed.
26070 Indicates the current line number for the selected frame.
26071 When the current line number is not known, the string @code{??} is displayed.
26074 Indicates the current program counter address.
26078 @section TUI Key Bindings
26079 @cindex TUI key bindings
26081 The TUI installs several key bindings in the readline keymaps
26082 @ifset SYSTEM_READLINE
26083 (@pxref{Command Line Editing, , , rluserman, GNU Readline Library}).
26085 @ifclear SYSTEM_READLINE
26086 (@pxref{Command Line Editing}).
26088 The following key bindings are installed for both TUI mode and the
26089 @value{GDBN} standard mode.
26098 Enter or leave the TUI mode. When leaving the TUI mode,
26099 the curses window management stops and @value{GDBN} operates using
26100 its standard mode, writing on the terminal directly. When reentering
26101 the TUI mode, control is given back to the curses windows.
26102 The screen is then refreshed.
26106 Use a TUI layout with only one window. The layout will
26107 either be @samp{source} or @samp{assembly}. When the TUI mode
26108 is not active, it will switch to the TUI mode.
26110 Think of this key binding as the Emacs @kbd{C-x 1} binding.
26114 Use a TUI layout with at least two windows. When the current
26115 layout already has two windows, the next layout with two windows is used.
26116 When a new layout is chosen, one window will always be common to the
26117 previous layout and the new one.
26119 Think of it as the Emacs @kbd{C-x 2} binding.
26123 Change the active window. The TUI associates several key bindings
26124 (like scrolling and arrow keys) with the active window. This command
26125 gives the focus to the next TUI window.
26127 Think of it as the Emacs @kbd{C-x o} binding.
26131 Switch in and out of the TUI SingleKey mode that binds single
26132 keys to @value{GDBN} commands (@pxref{TUI Single Key Mode}).
26135 The following key bindings only work in the TUI mode:
26140 Scroll the active window one page up.
26144 Scroll the active window one page down.
26148 Scroll the active window one line up.
26152 Scroll the active window one line down.
26156 Scroll the active window one column left.
26160 Scroll the active window one column right.
26164 Refresh the screen.
26167 Because the arrow keys scroll the active window in the TUI mode, they
26168 are not available for their normal use by readline unless the command
26169 window has the focus. When another window is active, you must use
26170 other readline key bindings such as @kbd{C-p}, @kbd{C-n}, @kbd{C-b}
26171 and @kbd{C-f} to control the command window.
26173 @node TUI Single Key Mode
26174 @section TUI Single Key Mode
26175 @cindex TUI single key mode
26177 The TUI also provides a @dfn{SingleKey} mode, which binds several
26178 frequently used @value{GDBN} commands to single keys. Type @kbd{C-x s} to
26179 switch into this mode, where the following key bindings are used:
26182 @kindex c @r{(SingleKey TUI key)}
26186 @kindex d @r{(SingleKey TUI key)}
26190 @kindex f @r{(SingleKey TUI key)}
26194 @kindex n @r{(SingleKey TUI key)}
26198 @kindex o @r{(SingleKey TUI key)}
26200 nexti. The shortcut letter @samp{o} stands for ``step Over''.
26202 @kindex q @r{(SingleKey TUI key)}
26204 exit the SingleKey mode.
26206 @kindex r @r{(SingleKey TUI key)}
26210 @kindex s @r{(SingleKey TUI key)}
26214 @kindex i @r{(SingleKey TUI key)}
26216 stepi. The shortcut letter @samp{i} stands for ``step Into''.
26218 @kindex u @r{(SingleKey TUI key)}
26222 @kindex v @r{(SingleKey TUI key)}
26226 @kindex w @r{(SingleKey TUI key)}
26231 Other keys temporarily switch to the @value{GDBN} command prompt.
26232 The key that was pressed is inserted in the editing buffer so that
26233 it is possible to type most @value{GDBN} commands without interaction
26234 with the TUI SingleKey mode. Once the command is entered the TUI
26235 SingleKey mode is restored. The only way to permanently leave
26236 this mode is by typing @kbd{q} or @kbd{C-x s}.
26240 @section TUI-specific Commands
26241 @cindex TUI commands
26243 The TUI has specific commands to control the text windows.
26244 These commands are always available, even when @value{GDBN} is not in
26245 the TUI mode. When @value{GDBN} is in the standard mode, most
26246 of these commands will automatically switch to the TUI mode.
26248 Note that if @value{GDBN}'s @code{stdout} is not connected to a
26249 terminal, or @value{GDBN} has been started with the machine interface
26250 interpreter (@pxref{GDB/MI, ,The @sc{gdb/mi} Interface}), most of
26251 these commands will fail with an error, because it would not be
26252 possible or desirable to enable curses window management.
26257 Activate TUI mode. The last active TUI window layout will be used if
26258 TUI mode has prevsiouly been used in the current debugging session,
26259 otherwise a default layout is used.
26262 @kindex tui disable
26263 Disable TUI mode, returning to the console interpreter.
26267 List and give the size of all displayed windows.
26269 @item layout @var{name}
26271 Changes which TUI windows are displayed. In each layout the command
26272 window is always displayed, the @var{name} parameter controls which
26273 additional windows are displayed, and can be any of the following:
26277 Display the next layout.
26280 Display the previous layout.
26283 Display the source and command windows.
26286 Display the assembly and command windows.
26289 Display the source, assembly, and command windows.
26292 When in @code{src} layout display the register, source, and command
26293 windows. When in @code{asm} or @code{split} layout display the
26294 register, assembler, and command windows.
26297 @item focus @var{name}
26299 Changes which TUI window is currently active for scrolling. The
26300 @var{name} parameter can be any of the following:
26304 Make the next window active for scrolling.
26307 Make the previous window active for scrolling.
26310 Make the source window active for scrolling.
26313 Make the assembly window active for scrolling.
26316 Make the register window active for scrolling.
26319 Make the command window active for scrolling.
26324 Refresh the screen. This is similar to typing @kbd{C-L}.
26326 @item tui reg @var{group}
26328 Changes the register group displayed in the tui register window to
26329 @var{group}. If the register window is not currently displayed this
26330 command will cause the register window to be displayed. The list of
26331 register groups, as well as their order is target specific. The
26332 following groups are available on most targets:
26335 Repeatedly selecting this group will cause the display to cycle
26336 through all of the available register groups.
26339 Repeatedly selecting this group will cause the display to cycle
26340 through all of the available register groups in the reverse order to
26344 Display the general registers.
26346 Display the floating point registers.
26348 Display the system registers.
26350 Display the vector registers.
26352 Display all registers.
26357 Update the source window and the current execution point.
26359 @item winheight @var{name} +@var{count}
26360 @itemx winheight @var{name} -@var{count}
26362 Change the height of the window @var{name} by @var{count}
26363 lines. Positive counts increase the height, while negative counts
26364 decrease it. The @var{name} parameter can be one of @code{src} (the
26365 source window), @code{cmd} (the command window), @code{asm} (the
26366 disassembly window), or @code{regs} (the register display window).
26368 @item tabset @var{nchars}
26370 Set the width of tab stops to be @var{nchars} characters. This
26371 setting affects the display of TAB characters in the source and
26375 @node TUI Configuration
26376 @section TUI Configuration Variables
26377 @cindex TUI configuration variables
26379 Several configuration variables control the appearance of TUI windows.
26382 @item set tui border-kind @var{kind}
26383 @kindex set tui border-kind
26384 Select the border appearance for the source, assembly and register windows.
26385 The possible values are the following:
26388 Use a space character to draw the border.
26391 Use @sc{ascii} characters @samp{+}, @samp{-} and @samp{|} to draw the border.
26394 Use the Alternate Character Set to draw the border. The border is
26395 drawn using character line graphics if the terminal supports them.
26398 @item set tui border-mode @var{mode}
26399 @kindex set tui border-mode
26400 @itemx set tui active-border-mode @var{mode}
26401 @kindex set tui active-border-mode
26402 Select the display attributes for the borders of the inactive windows
26403 or the active window. The @var{mode} can be one of the following:
26406 Use normal attributes to display the border.
26412 Use reverse video mode.
26415 Use half bright mode.
26417 @item half-standout
26418 Use half bright and standout mode.
26421 Use extra bright or bold mode.
26423 @item bold-standout
26424 Use extra bright or bold and standout mode.
26429 @chapter Using @value{GDBN} under @sc{gnu} Emacs
26432 @cindex @sc{gnu} Emacs
26433 A special interface allows you to use @sc{gnu} Emacs to view (and
26434 edit) the source files for the program you are debugging with
26437 To use this interface, use the command @kbd{M-x gdb} in Emacs. Give the
26438 executable file you want to debug as an argument. This command starts
26439 @value{GDBN} as a subprocess of Emacs, with input and output through a newly
26440 created Emacs buffer.
26441 @c (Do not use the @code{-tui} option to run @value{GDBN} from Emacs.)
26443 Running @value{GDBN} under Emacs can be just like running @value{GDBN} normally except for two
26448 All ``terminal'' input and output goes through an Emacs buffer, called
26451 This applies both to @value{GDBN} commands and their output, and to the input
26452 and output done by the program you are debugging.
26454 This is useful because it means that you can copy the text of previous
26455 commands and input them again; you can even use parts of the output
26458 All the facilities of Emacs' Shell mode are available for interacting
26459 with your program. In particular, you can send signals the usual
26460 way---for example, @kbd{C-c C-c} for an interrupt, @kbd{C-c C-z} for a
26464 @value{GDBN} displays source code through Emacs.
26466 Each time @value{GDBN} displays a stack frame, Emacs automatically finds the
26467 source file for that frame and puts an arrow (@samp{=>}) at the
26468 left margin of the current line. Emacs uses a separate buffer for
26469 source display, and splits the screen to show both your @value{GDBN} session
26472 Explicit @value{GDBN} @code{list} or search commands still produce output as
26473 usual, but you probably have no reason to use them from Emacs.
26476 We call this @dfn{text command mode}. Emacs 22.1, and later, also uses
26477 a graphical mode, enabled by default, which provides further buffers
26478 that can control the execution and describe the state of your program.
26479 @xref{GDB Graphical Interface,,, Emacs, The @sc{gnu} Emacs Manual}.
26481 If you specify an absolute file name when prompted for the @kbd{M-x
26482 gdb} argument, then Emacs sets your current working directory to where
26483 your program resides. If you only specify the file name, then Emacs
26484 sets your current working directory to the directory associated
26485 with the previous buffer. In this case, @value{GDBN} may find your
26486 program by searching your environment's @code{PATH} variable, but on
26487 some operating systems it might not find the source. So, although the
26488 @value{GDBN} input and output session proceeds normally, the auxiliary
26489 buffer does not display the current source and line of execution.
26491 The initial working directory of @value{GDBN} is printed on the top
26492 line of the GUD buffer and this serves as a default for the commands
26493 that specify files for @value{GDBN} to operate on. @xref{Files,
26494 ,Commands to Specify Files}.
26496 By default, @kbd{M-x gdb} calls the program called @file{gdb}. If you
26497 need to call @value{GDBN} by a different name (for example, if you
26498 keep several configurations around, with different names) you can
26499 customize the Emacs variable @code{gud-gdb-command-name} to run the
26502 In the GUD buffer, you can use these special Emacs commands in
26503 addition to the standard Shell mode commands:
26507 Describe the features of Emacs' GUD Mode.
26510 Execute to another source line, like the @value{GDBN} @code{step} command; also
26511 update the display window to show the current file and location.
26514 Execute to next source line in this function, skipping all function
26515 calls, like the @value{GDBN} @code{next} command. Then update the display window
26516 to show the current file and location.
26519 Execute one instruction, like the @value{GDBN} @code{stepi} command; update
26520 display window accordingly.
26523 Execute until exit from the selected stack frame, like the @value{GDBN}
26524 @code{finish} command.
26527 Continue execution of your program, like the @value{GDBN} @code{continue}
26531 Go up the number of frames indicated by the numeric argument
26532 (@pxref{Arguments, , Numeric Arguments, Emacs, The @sc{gnu} Emacs Manual}),
26533 like the @value{GDBN} @code{up} command.
26536 Go down the number of frames indicated by the numeric argument, like the
26537 @value{GDBN} @code{down} command.
26540 In any source file, the Emacs command @kbd{C-x @key{SPC}} (@code{gud-break})
26541 tells @value{GDBN} to set a breakpoint on the source line point is on.
26543 In text command mode, if you type @kbd{M-x speedbar}, Emacs displays a
26544 separate frame which shows a backtrace when the GUD buffer is current.
26545 Move point to any frame in the stack and type @key{RET} to make it
26546 become the current frame and display the associated source in the
26547 source buffer. Alternatively, click @kbd{Mouse-2} to make the
26548 selected frame become the current one. In graphical mode, the
26549 speedbar displays watch expressions.
26551 If you accidentally delete the source-display buffer, an easy way to get
26552 it back is to type the command @code{f} in the @value{GDBN} buffer, to
26553 request a frame display; when you run under Emacs, this recreates
26554 the source buffer if necessary to show you the context of the current
26557 The source files displayed in Emacs are in ordinary Emacs buffers
26558 which are visiting the source files in the usual way. You can edit
26559 the files with these buffers if you wish; but keep in mind that @value{GDBN}
26560 communicates with Emacs in terms of line numbers. If you add or
26561 delete lines from the text, the line numbers that @value{GDBN} knows cease
26562 to correspond properly with the code.
26564 A more detailed description of Emacs' interaction with @value{GDBN} is
26565 given in the Emacs manual (@pxref{Debuggers,,, Emacs, The @sc{gnu}
26569 @chapter The @sc{gdb/mi} Interface
26571 @unnumberedsec Function and Purpose
26573 @cindex @sc{gdb/mi}, its purpose
26574 @sc{gdb/mi} is a line based machine oriented text interface to
26575 @value{GDBN} and is activated by specifying using the
26576 @option{--interpreter} command line option (@pxref{Mode Options}). It
26577 is specifically intended to support the development of systems which
26578 use the debugger as just one small component of a larger system.
26580 This chapter is a specification of the @sc{gdb/mi} interface. It is written
26581 in the form of a reference manual.
26583 Note that @sc{gdb/mi} is still under construction, so some of the
26584 features described below are incomplete and subject to change
26585 (@pxref{GDB/MI Development and Front Ends, , @sc{gdb/mi} Development and Front Ends}).
26587 @unnumberedsec Notation and Terminology
26589 @cindex notational conventions, for @sc{gdb/mi}
26590 This chapter uses the following notation:
26594 @code{|} separates two alternatives.
26597 @code{[ @var{something} ]} indicates that @var{something} is optional:
26598 it may or may not be given.
26601 @code{( @var{group} )*} means that @var{group} inside the parentheses
26602 may repeat zero or more times.
26605 @code{( @var{group} )+} means that @var{group} inside the parentheses
26606 may repeat one or more times.
26609 @code{"@var{string}"} means a literal @var{string}.
26613 @heading Dependencies
26617 * GDB/MI General Design::
26618 * GDB/MI Command Syntax::
26619 * GDB/MI Compatibility with CLI::
26620 * GDB/MI Development and Front Ends::
26621 * GDB/MI Output Records::
26622 * GDB/MI Simple Examples::
26623 * GDB/MI Command Description Format::
26624 * GDB/MI Breakpoint Commands::
26625 * GDB/MI Catchpoint Commands::
26626 * GDB/MI Program Context::
26627 * GDB/MI Thread Commands::
26628 * GDB/MI Ada Tasking Commands::
26629 * GDB/MI Program Execution::
26630 * GDB/MI Stack Manipulation::
26631 * GDB/MI Variable Objects::
26632 * GDB/MI Data Manipulation::
26633 * GDB/MI Tracepoint Commands::
26634 * GDB/MI Symbol Query::
26635 * GDB/MI File Commands::
26637 * GDB/MI Kod Commands::
26638 * GDB/MI Memory Overlay Commands::
26639 * GDB/MI Signal Handling Commands::
26641 * GDB/MI Target Manipulation::
26642 * GDB/MI File Transfer Commands::
26643 * GDB/MI Ada Exceptions Commands::
26644 * GDB/MI Support Commands::
26645 * GDB/MI Miscellaneous Commands::
26648 @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
26649 @node GDB/MI General Design
26650 @section @sc{gdb/mi} General Design
26651 @cindex GDB/MI General Design
26653 Interaction of a @sc{GDB/MI} frontend with @value{GDBN} involves three
26654 parts---commands sent to @value{GDBN}, responses to those commands
26655 and notifications. Each command results in exactly one response,
26656 indicating either successful completion of the command, or an error.
26657 For the commands that do not resume the target, the response contains the
26658 requested information. For the commands that resume the target, the
26659 response only indicates whether the target was successfully resumed.
26660 Notifications is the mechanism for reporting changes in the state of the
26661 target, or in @value{GDBN} state, that cannot conveniently be associated with
26662 a command and reported as part of that command response.
26664 The important examples of notifications are:
26668 Exec notifications. These are used to report changes in
26669 target state---when a target is resumed, or stopped. It would not
26670 be feasible to include this information in response of resuming
26671 commands, because one resume commands can result in multiple events in
26672 different threads. Also, quite some time may pass before any event
26673 happens in the target, while a frontend needs to know whether the resuming
26674 command itself was successfully executed.
26677 Console output, and status notifications. Console output
26678 notifications are used to report output of CLI commands, as well as
26679 diagnostics for other commands. Status notifications are used to
26680 report the progress of a long-running operation. Naturally, including
26681 this information in command response would mean no output is produced
26682 until the command is finished, which is undesirable.
26685 General notifications. Commands may have various side effects on
26686 the @value{GDBN} or target state beyond their official purpose. For example,
26687 a command may change the selected thread. Although such changes can
26688 be included in command response, using notification allows for more
26689 orthogonal frontend design.
26693 There's no guarantee that whenever an MI command reports an error,
26694 @value{GDBN} or the target are in any specific state, and especially,
26695 the state is not reverted to the state before the MI command was
26696 processed. Therefore, whenever an MI command results in an error,
26697 we recommend that the frontend refreshes all the information shown in
26698 the user interface.
26702 * Context management::
26703 * Asynchronous and non-stop modes::
26707 @node Context management
26708 @subsection Context management
26710 @subsubsection Threads and Frames
26712 In most cases when @value{GDBN} accesses the target, this access is
26713 done in context of a specific thread and frame (@pxref{Frames}).
26714 Often, even when accessing global data, the target requires that a thread
26715 be specified. The CLI interface maintains the selected thread and frame,
26716 and supplies them to target on each command. This is convenient,
26717 because a command line user would not want to specify that information
26718 explicitly on each command, and because user interacts with
26719 @value{GDBN} via a single terminal, so no confusion is possible as
26720 to what thread and frame are the current ones.
26722 In the case of MI, the concept of selected thread and frame is less
26723 useful. First, a frontend can easily remember this information
26724 itself. Second, a graphical frontend can have more than one window,
26725 each one used for debugging a different thread, and the frontend might
26726 want to access additional threads for internal purposes. This
26727 increases the risk that by relying on implicitly selected thread, the
26728 frontend may be operating on a wrong one. Therefore, each MI command
26729 should explicitly specify which thread and frame to operate on. To
26730 make it possible, each MI command accepts the @samp{--thread} and
26731 @samp{--frame} options, the value to each is @value{GDBN} global
26732 identifier for thread and frame to operate on.
26734 Usually, each top-level window in a frontend allows the user to select
26735 a thread and a frame, and remembers the user selection for further
26736 operations. However, in some cases @value{GDBN} may suggest that the
26737 current thread or frame be changed. For example, when stopping on a
26738 breakpoint it is reasonable to switch to the thread where breakpoint is
26739 hit. For another example, if the user issues the CLI @samp{thread} or
26740 @samp{frame} commands via the frontend, it is desirable to change the
26741 frontend's selection to the one specified by user. @value{GDBN}
26742 communicates the suggestion to change current thread and frame using the
26743 @samp{=thread-selected} notification.
26745 Note that historically, MI shares the selected thread with CLI, so
26746 frontends used the @code{-thread-select} to execute commands in the
26747 right context. However, getting this to work right is cumbersome. The
26748 simplest way is for frontend to emit @code{-thread-select} command
26749 before every command. This doubles the number of commands that need
26750 to be sent. The alternative approach is to suppress @code{-thread-select}
26751 if the selected thread in @value{GDBN} is supposed to be identical to the
26752 thread the frontend wants to operate on. However, getting this
26753 optimization right can be tricky. In particular, if the frontend
26754 sends several commands to @value{GDBN}, and one of the commands changes the
26755 selected thread, then the behaviour of subsequent commands will
26756 change. So, a frontend should either wait for response from such
26757 problematic commands, or explicitly add @code{-thread-select} for
26758 all subsequent commands. No frontend is known to do this exactly
26759 right, so it is suggested to just always pass the @samp{--thread} and
26760 @samp{--frame} options.
26762 @subsubsection Language
26764 The execution of several commands depends on which language is selected.
26765 By default, the current language (@pxref{show language}) is used.
26766 But for commands known to be language-sensitive, it is recommended
26767 to use the @samp{--language} option. This option takes one argument,
26768 which is the name of the language to use while executing the command.
26772 -data-evaluate-expression --language c "sizeof (void*)"
26777 The valid language names are the same names accepted by the
26778 @samp{set language} command (@pxref{Manually}), excluding @samp{auto},
26779 @samp{local} or @samp{unknown}.
26781 @node Asynchronous and non-stop modes
26782 @subsection Asynchronous command execution and non-stop mode
26784 On some targets, @value{GDBN} is capable of processing MI commands
26785 even while the target is running. This is called @dfn{asynchronous
26786 command execution} (@pxref{Background Execution}). The frontend may
26787 specify a preferrence for asynchronous execution using the
26788 @code{-gdb-set mi-async 1} command, which should be emitted before
26789 either running the executable or attaching to the target. After the
26790 frontend has started the executable or attached to the target, it can
26791 find if asynchronous execution is enabled using the
26792 @code{-list-target-features} command.
26795 @item -gdb-set mi-async on
26796 @item -gdb-set mi-async off
26797 Set whether MI is in asynchronous mode.
26799 When @code{off}, which is the default, MI execution commands (e.g.,
26800 @code{-exec-continue}) are foreground commands, and @value{GDBN} waits
26801 for the program to stop before processing further commands.
26803 When @code{on}, MI execution commands are background execution
26804 commands (e.g., @code{-exec-continue} becomes the equivalent of the
26805 @code{c&} CLI command), and so @value{GDBN} is capable of processing
26806 MI commands even while the target is running.
26808 @item -gdb-show mi-async
26809 Show whether MI asynchronous mode is enabled.
26812 Note: In @value{GDBN} version 7.7 and earlier, this option was called
26813 @code{target-async} instead of @code{mi-async}, and it had the effect
26814 of both putting MI in asynchronous mode and making CLI background
26815 commands possible. CLI background commands are now always possible
26816 ``out of the box'' if the target supports them. The old spelling is
26817 kept as a deprecated alias for backwards compatibility.
26819 Even if @value{GDBN} can accept a command while target is running,
26820 many commands that access the target do not work when the target is
26821 running. Therefore, asynchronous command execution is most useful
26822 when combined with non-stop mode (@pxref{Non-Stop Mode}). Then,
26823 it is possible to examine the state of one thread, while other threads
26826 When a given thread is running, MI commands that try to access the
26827 target in the context of that thread may not work, or may work only on
26828 some targets. In particular, commands that try to operate on thread's
26829 stack will not work, on any target. Commands that read memory, or
26830 modify breakpoints, may work or not work, depending on the target. Note
26831 that even commands that operate on global state, such as @code{print},
26832 @code{set}, and breakpoint commands, still access the target in the
26833 context of a specific thread, so frontend should try to find a
26834 stopped thread and perform the operation on that thread (using the
26835 @samp{--thread} option).
26837 Which commands will work in the context of a running thread is
26838 highly target dependent. However, the two commands
26839 @code{-exec-interrupt}, to stop a thread, and @code{-thread-info},
26840 to find the state of a thread, will always work.
26842 @node Thread groups
26843 @subsection Thread groups
26844 @value{GDBN} may be used to debug several processes at the same time.
26845 On some platfroms, @value{GDBN} may support debugging of several
26846 hardware systems, each one having several cores with several different
26847 processes running on each core. This section describes the MI
26848 mechanism to support such debugging scenarios.
26850 The key observation is that regardless of the structure of the
26851 target, MI can have a global list of threads, because most commands that
26852 accept the @samp{--thread} option do not need to know what process that
26853 thread belongs to. Therefore, it is not necessary to introduce
26854 neither additional @samp{--process} option, nor an notion of the
26855 current process in the MI interface. The only strictly new feature
26856 that is required is the ability to find how the threads are grouped
26859 To allow the user to discover such grouping, and to support arbitrary
26860 hierarchy of machines/cores/processes, MI introduces the concept of a
26861 @dfn{thread group}. Thread group is a collection of threads and other
26862 thread groups. A thread group always has a string identifier, a type,
26863 and may have additional attributes specific to the type. A new
26864 command, @code{-list-thread-groups}, returns the list of top-level
26865 thread groups, which correspond to processes that @value{GDBN} is
26866 debugging at the moment. By passing an identifier of a thread group
26867 to the @code{-list-thread-groups} command, it is possible to obtain
26868 the members of specific thread group.
26870 To allow the user to easily discover processes, and other objects, he
26871 wishes to debug, a concept of @dfn{available thread group} is
26872 introduced. Available thread group is an thread group that
26873 @value{GDBN} is not debugging, but that can be attached to, using the
26874 @code{-target-attach} command. The list of available top-level thread
26875 groups can be obtained using @samp{-list-thread-groups --available}.
26876 In general, the content of a thread group may be only retrieved only
26877 after attaching to that thread group.
26879 Thread groups are related to inferiors (@pxref{Inferiors and
26880 Programs}). Each inferior corresponds to a thread group of a special
26881 type @samp{process}, and some additional operations are permitted on
26882 such thread groups.
26884 @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
26885 @node GDB/MI Command Syntax
26886 @section @sc{gdb/mi} Command Syntax
26889 * GDB/MI Input Syntax::
26890 * GDB/MI Output Syntax::
26893 @node GDB/MI Input Syntax
26894 @subsection @sc{gdb/mi} Input Syntax
26896 @cindex input syntax for @sc{gdb/mi}
26897 @cindex @sc{gdb/mi}, input syntax
26899 @item @var{command} @expansion{}
26900 @code{@var{cli-command} | @var{mi-command}}
26902 @item @var{cli-command} @expansion{}
26903 @code{[ @var{token} ] @var{cli-command} @var{nl}}, where
26904 @var{cli-command} is any existing @value{GDBN} CLI command.
26906 @item @var{mi-command} @expansion{}
26907 @code{[ @var{token} ] "-" @var{operation} ( " " @var{option} )*
26908 @code{[} " --" @code{]} ( " " @var{parameter} )* @var{nl}}
26910 @item @var{token} @expansion{}
26911 "any sequence of digits"
26913 @item @var{option} @expansion{}
26914 @code{"-" @var{parameter} [ " " @var{parameter} ]}
26916 @item @var{parameter} @expansion{}
26917 @code{@var{non-blank-sequence} | @var{c-string}}
26919 @item @var{operation} @expansion{}
26920 @emph{any of the operations described in this chapter}
26922 @item @var{non-blank-sequence} @expansion{}
26923 @emph{anything, provided it doesn't contain special characters such as
26924 "-", @var{nl}, """ and of course " "}
26926 @item @var{c-string} @expansion{}
26927 @code{""" @var{seven-bit-iso-c-string-content} """}
26929 @item @var{nl} @expansion{}
26938 The CLI commands are still handled by the @sc{mi} interpreter; their
26939 output is described below.
26942 The @code{@var{token}}, when present, is passed back when the command
26946 Some @sc{mi} commands accept optional arguments as part of the parameter
26947 list. Each option is identified by a leading @samp{-} (dash) and may be
26948 followed by an optional argument parameter. Options occur first in the
26949 parameter list and can be delimited from normal parameters using
26950 @samp{--} (this is useful when some parameters begin with a dash).
26957 We want easy access to the existing CLI syntax (for debugging).
26960 We want it to be easy to spot a @sc{mi} operation.
26963 @node GDB/MI Output Syntax
26964 @subsection @sc{gdb/mi} Output Syntax
26966 @cindex output syntax of @sc{gdb/mi}
26967 @cindex @sc{gdb/mi}, output syntax
26968 The output from @sc{gdb/mi} consists of zero or more out-of-band records
26969 followed, optionally, by a single result record. This result record
26970 is for the most recent command. The sequence of output records is
26971 terminated by @samp{(gdb)}.
26973 If an input command was prefixed with a @code{@var{token}} then the
26974 corresponding output for that command will also be prefixed by that same
26978 @item @var{output} @expansion{}
26979 @code{( @var{out-of-band-record} )* [ @var{result-record} ] "(gdb)" @var{nl}}
26981 @item @var{result-record} @expansion{}
26982 @code{ [ @var{token} ] "^" @var{result-class} ( "," @var{result} )* @var{nl}}
26984 @item @var{out-of-band-record} @expansion{}
26985 @code{@var{async-record} | @var{stream-record}}
26987 @item @var{async-record} @expansion{}
26988 @code{@var{exec-async-output} | @var{status-async-output} | @var{notify-async-output}}
26990 @item @var{exec-async-output} @expansion{}
26991 @code{[ @var{token} ] "*" @var{async-output nl}}
26993 @item @var{status-async-output} @expansion{}
26994 @code{[ @var{token} ] "+" @var{async-output nl}}
26996 @item @var{notify-async-output} @expansion{}
26997 @code{[ @var{token} ] "=" @var{async-output nl}}
26999 @item @var{async-output} @expansion{}
27000 @code{@var{async-class} ( "," @var{result} )*}
27002 @item @var{result-class} @expansion{}
27003 @code{"done" | "running" | "connected" | "error" | "exit"}
27005 @item @var{async-class} @expansion{}
27006 @code{"stopped" | @var{others}} (where @var{others} will be added
27007 depending on the needs---this is still in development).
27009 @item @var{result} @expansion{}
27010 @code{ @var{variable} "=" @var{value}}
27012 @item @var{variable} @expansion{}
27013 @code{ @var{string} }
27015 @item @var{value} @expansion{}
27016 @code{ @var{const} | @var{tuple} | @var{list} }
27018 @item @var{const} @expansion{}
27019 @code{@var{c-string}}
27021 @item @var{tuple} @expansion{}
27022 @code{ "@{@}" | "@{" @var{result} ( "," @var{result} )* "@}" }
27024 @item @var{list} @expansion{}
27025 @code{ "[]" | "[" @var{value} ( "," @var{value} )* "]" | "["
27026 @var{result} ( "," @var{result} )* "]" }
27028 @item @var{stream-record} @expansion{}
27029 @code{@var{console-stream-output} | @var{target-stream-output} | @var{log-stream-output}}
27031 @item @var{console-stream-output} @expansion{}
27032 @code{"~" @var{c-string nl}}
27034 @item @var{target-stream-output} @expansion{}
27035 @code{"@@" @var{c-string nl}}
27037 @item @var{log-stream-output} @expansion{}
27038 @code{"&" @var{c-string nl}}
27040 @item @var{nl} @expansion{}
27043 @item @var{token} @expansion{}
27044 @emph{any sequence of digits}.
27052 All output sequences end in a single line containing a period.
27055 The @code{@var{token}} is from the corresponding request. Note that
27056 for all async output, while the token is allowed by the grammar and
27057 may be output by future versions of @value{GDBN} for select async
27058 output messages, it is generally omitted. Frontends should treat
27059 all async output as reporting general changes in the state of the
27060 target and there should be no need to associate async output to any
27064 @cindex status output in @sc{gdb/mi}
27065 @var{status-async-output} contains on-going status information about the
27066 progress of a slow operation. It can be discarded. All status output is
27067 prefixed by @samp{+}.
27070 @cindex async output in @sc{gdb/mi}
27071 @var{exec-async-output} contains asynchronous state change on the target
27072 (stopped, started, disappeared). All async output is prefixed by
27076 @cindex notify output in @sc{gdb/mi}
27077 @var{notify-async-output} contains supplementary information that the
27078 client should handle (e.g., a new breakpoint information). All notify
27079 output is prefixed by @samp{=}.
27082 @cindex console output in @sc{gdb/mi}
27083 @var{console-stream-output} is output that should be displayed as is in the
27084 console. It is the textual response to a CLI command. All the console
27085 output is prefixed by @samp{~}.
27088 @cindex target output in @sc{gdb/mi}
27089 @var{target-stream-output} is the output produced by the target program.
27090 All the target output is prefixed by @samp{@@}.
27093 @cindex log output in @sc{gdb/mi}
27094 @var{log-stream-output} is output text coming from @value{GDBN}'s internals, for
27095 instance messages that should be displayed as part of an error log. All
27096 the log output is prefixed by @samp{&}.
27099 @cindex list output in @sc{gdb/mi}
27100 New @sc{gdb/mi} commands should only output @var{lists} containing
27106 @xref{GDB/MI Stream Records, , @sc{gdb/mi} Stream Records}, for more
27107 details about the various output records.
27109 @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
27110 @node GDB/MI Compatibility with CLI
27111 @section @sc{gdb/mi} Compatibility with CLI
27113 @cindex compatibility, @sc{gdb/mi} and CLI
27114 @cindex @sc{gdb/mi}, compatibility with CLI
27116 For the developers convenience CLI commands can be entered directly,
27117 but there may be some unexpected behaviour. For example, commands
27118 that query the user will behave as if the user replied yes, breakpoint
27119 command lists are not executed and some CLI commands, such as
27120 @code{if}, @code{when} and @code{define}, prompt for further input with
27121 @samp{>}, which is not valid MI output.
27123 This feature may be removed at some stage in the future and it is
27124 recommended that front ends use the @code{-interpreter-exec} command
27125 (@pxref{-interpreter-exec}).
27127 @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
27128 @node GDB/MI Development and Front Ends
27129 @section @sc{gdb/mi} Development and Front Ends
27130 @cindex @sc{gdb/mi} development
27132 The application which takes the MI output and presents the state of the
27133 program being debugged to the user is called a @dfn{front end}.
27135 Although @sc{gdb/mi} is still incomplete, it is currently being used
27136 by a variety of front ends to @value{GDBN}. This makes it difficult
27137 to introduce new functionality without breaking existing usage. This
27138 section tries to minimize the problems by describing how the protocol
27141 Some changes in MI need not break a carefully designed front end, and
27142 for these the MI version will remain unchanged. The following is a
27143 list of changes that may occur within one level, so front ends should
27144 parse MI output in a way that can handle them:
27148 New MI commands may be added.
27151 New fields may be added to the output of any MI command.
27154 The range of values for fields with specified values, e.g.,
27155 @code{in_scope} (@pxref{-var-update}) may be extended.
27157 @c The format of field's content e.g type prefix, may change so parse it
27158 @c at your own risk. Yes, in general?
27160 @c The order of fields may change? Shouldn't really matter but it might
27161 @c resolve inconsistencies.
27164 If the changes are likely to break front ends, the MI version level
27165 will be increased by one. This will allow the front end to parse the
27166 output according to the MI version. Apart from mi0, new versions of
27167 @value{GDBN} will not support old versions of MI and it will be the
27168 responsibility of the front end to work with the new one.
27170 @c Starting with mi3, add a new command -mi-version that prints the MI
27173 The best way to avoid unexpected changes in MI that might break your front
27174 end is to make your project known to @value{GDBN} developers and
27175 follow development on @email{gdb@@sourceware.org} and
27176 @email{gdb-patches@@sourceware.org}.
27177 @cindex mailing lists
27179 @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
27180 @node GDB/MI Output Records
27181 @section @sc{gdb/mi} Output Records
27184 * GDB/MI Result Records::
27185 * GDB/MI Stream Records::
27186 * GDB/MI Async Records::
27187 * GDB/MI Breakpoint Information::
27188 * GDB/MI Frame Information::
27189 * GDB/MI Thread Information::
27190 * GDB/MI Ada Exception Information::
27193 @node GDB/MI Result Records
27194 @subsection @sc{gdb/mi} Result Records
27196 @cindex result records in @sc{gdb/mi}
27197 @cindex @sc{gdb/mi}, result records
27198 In addition to a number of out-of-band notifications, the response to a
27199 @sc{gdb/mi} command includes one of the following result indications:
27203 @item "^done" [ "," @var{results} ]
27204 The synchronous operation was successful, @code{@var{results}} are the return
27209 This result record is equivalent to @samp{^done}. Historically, it
27210 was output instead of @samp{^done} if the command has resumed the
27211 target. This behaviour is maintained for backward compatibility, but
27212 all frontends should treat @samp{^done} and @samp{^running}
27213 identically and rely on the @samp{*running} output record to determine
27214 which threads are resumed.
27218 @value{GDBN} has connected to a remote target.
27220 @item "^error" "," "msg=" @var{c-string} [ "," "code=" @var{c-string} ]
27222 The operation failed. The @code{msg=@var{c-string}} variable contains
27223 the corresponding error message.
27225 If present, the @code{code=@var{c-string}} variable provides an error
27226 code on which consumers can rely on to detect the corresponding
27227 error condition. At present, only one error code is defined:
27230 @item "undefined-command"
27231 Indicates that the command causing the error does not exist.
27236 @value{GDBN} has terminated.
27240 @node GDB/MI Stream Records
27241 @subsection @sc{gdb/mi} Stream Records
27243 @cindex @sc{gdb/mi}, stream records
27244 @cindex stream records in @sc{gdb/mi}
27245 @value{GDBN} internally maintains a number of output streams: the console, the
27246 target, and the log. The output intended for each of these streams is
27247 funneled through the @sc{gdb/mi} interface using @dfn{stream records}.
27249 Each stream record begins with a unique @dfn{prefix character} which
27250 identifies its stream (@pxref{GDB/MI Output Syntax, , @sc{gdb/mi} Output
27251 Syntax}). In addition to the prefix, each stream record contains a
27252 @code{@var{string-output}}. This is either raw text (with an implicit new
27253 line) or a quoted C string (which does not contain an implicit newline).
27256 @item "~" @var{string-output}
27257 The console output stream contains text that should be displayed in the
27258 CLI console window. It contains the textual responses to CLI commands.
27260 @item "@@" @var{string-output}
27261 The target output stream contains any textual output from the running
27262 target. This is only present when GDB's event loop is truly
27263 asynchronous, which is currently only the case for remote targets.
27265 @item "&" @var{string-output}
27266 The log stream contains debugging messages being produced by @value{GDBN}'s
27270 @node GDB/MI Async Records
27271 @subsection @sc{gdb/mi} Async Records
27273 @cindex async records in @sc{gdb/mi}
27274 @cindex @sc{gdb/mi}, async records
27275 @dfn{Async} records are used to notify the @sc{gdb/mi} client of
27276 additional changes that have occurred. Those changes can either be a
27277 consequence of @sc{gdb/mi} commands (e.g., a breakpoint modified) or a result of
27278 target activity (e.g., target stopped).
27280 The following is the list of possible async records:
27284 @item *running,thread-id="@var{thread}"
27285 The target is now running. The @var{thread} field can be the global
27286 thread ID of the the thread that is now running, and it can be
27287 @samp{all} if all threads are running. The frontend should assume
27288 that no interaction with a running thread is possible after this
27289 notification is produced. The frontend should not assume that this
27290 notification is output only once for any command. @value{GDBN} may
27291 emit this notification several times, either for different threads,
27292 because it cannot resume all threads together, or even for a single
27293 thread, if the thread must be stepped though some code before letting
27296 @item *stopped,reason="@var{reason}",thread-id="@var{id}",stopped-threads="@var{stopped}",core="@var{core}"
27297 The target has stopped. The @var{reason} field can have one of the
27301 @item breakpoint-hit
27302 A breakpoint was reached.
27303 @item watchpoint-trigger
27304 A watchpoint was triggered.
27305 @item read-watchpoint-trigger
27306 A read watchpoint was triggered.
27307 @item access-watchpoint-trigger
27308 An access watchpoint was triggered.
27309 @item function-finished
27310 An -exec-finish or similar CLI command was accomplished.
27311 @item location-reached
27312 An -exec-until or similar CLI command was accomplished.
27313 @item watchpoint-scope
27314 A watchpoint has gone out of scope.
27315 @item end-stepping-range
27316 An -exec-next, -exec-next-instruction, -exec-step, -exec-step-instruction or
27317 similar CLI command was accomplished.
27318 @item exited-signalled
27319 The inferior exited because of a signal.
27321 The inferior exited.
27322 @item exited-normally
27323 The inferior exited normally.
27324 @item signal-received
27325 A signal was received by the inferior.
27327 The inferior has stopped due to a library being loaded or unloaded.
27328 This can happen when @code{stop-on-solib-events} (@pxref{Files}) is
27329 set or when a @code{catch load} or @code{catch unload} catchpoint is
27330 in use (@pxref{Set Catchpoints}).
27332 The inferior has forked. This is reported when @code{catch fork}
27333 (@pxref{Set Catchpoints}) has been used.
27335 The inferior has vforked. This is reported in when @code{catch vfork}
27336 (@pxref{Set Catchpoints}) has been used.
27337 @item syscall-entry
27338 The inferior entered a system call. This is reported when @code{catch
27339 syscall} (@pxref{Set Catchpoints}) has been used.
27340 @item syscall-return
27341 The inferior returned from a system call. This is reported when
27342 @code{catch syscall} (@pxref{Set Catchpoints}) has been used.
27344 The inferior called @code{exec}. This is reported when @code{catch exec}
27345 (@pxref{Set Catchpoints}) has been used.
27348 The @var{id} field identifies the global thread ID of the thread
27349 that directly caused the stop -- for example by hitting a breakpoint.
27350 Depending on whether all-stop
27351 mode is in effect (@pxref{All-Stop Mode}), @value{GDBN} may either
27352 stop all threads, or only the thread that directly triggered the stop.
27353 If all threads are stopped, the @var{stopped} field will have the
27354 value of @code{"all"}. Otherwise, the value of the @var{stopped}
27355 field will be a list of thread identifiers. Presently, this list will
27356 always include a single thread, but frontend should be prepared to see
27357 several threads in the list. The @var{core} field reports the
27358 processor core on which the stop event has happened. This field may be absent
27359 if such information is not available.
27361 @item =thread-group-added,id="@var{id}"
27362 @itemx =thread-group-removed,id="@var{id}"
27363 A thread group was either added or removed. The @var{id} field
27364 contains the @value{GDBN} identifier of the thread group. When a thread
27365 group is added, it generally might not be associated with a running
27366 process. When a thread group is removed, its id becomes invalid and
27367 cannot be used in any way.
27369 @item =thread-group-started,id="@var{id}",pid="@var{pid}"
27370 A thread group became associated with a running program,
27371 either because the program was just started or the thread group
27372 was attached to a program. The @var{id} field contains the
27373 @value{GDBN} identifier of the thread group. The @var{pid} field
27374 contains process identifier, specific to the operating system.
27376 @item =thread-group-exited,id="@var{id}"[,exit-code="@var{code}"]
27377 A thread group is no longer associated with a running program,
27378 either because the program has exited, or because it was detached
27379 from. The @var{id} field contains the @value{GDBN} identifier of the
27380 thread group. The @var{code} field is the exit code of the inferior; it exists
27381 only when the inferior exited with some code.
27383 @item =thread-created,id="@var{id}",group-id="@var{gid}"
27384 @itemx =thread-exited,id="@var{id}",group-id="@var{gid}"
27385 A thread either was created, or has exited. The @var{id} field
27386 contains the global @value{GDBN} identifier of the thread. The @var{gid}
27387 field identifies the thread group this thread belongs to.
27389 @item =thread-selected,id="@var{id}"[,frame="@var{frame}"]
27390 Informs that the selected thread or frame were changed. This notification
27391 is not emitted as result of the @code{-thread-select} or
27392 @code{-stack-select-frame} commands, but is emitted whenever an MI command
27393 that is not documented to change the selected thread and frame actually
27394 changes them. In particular, invoking, directly or indirectly
27395 (via user-defined command), the CLI @code{thread} or @code{frame} commands,
27396 will generate this notification. Changing the thread or frame from another
27397 user interface (see @ref{Interpreters}) will also generate this notification.
27399 The @var{frame} field is only present if the newly selected thread is
27400 stopped. See @ref{GDB/MI Frame Information} for the format of its value.
27402 We suggest that in response to this notification, front ends
27403 highlight the selected thread and cause subsequent commands to apply to
27406 @item =library-loaded,...
27407 Reports that a new library file was loaded by the program. This
27408 notification has 5 fields---@var{id}, @var{target-name},
27409 @var{host-name}, @var{symbols-loaded} and @var{ranges}. The @var{id} field is an
27410 opaque identifier of the library. For remote debugging case,
27411 @var{target-name} and @var{host-name} fields give the name of the
27412 library file on the target, and on the host respectively. For native
27413 debugging, both those fields have the same value. The
27414 @var{symbols-loaded} field is emitted only for backward compatibility
27415 and should not be relied on to convey any useful information. The
27416 @var{thread-group} field, if present, specifies the id of the thread
27417 group in whose context the library was loaded. If the field is
27418 absent, it means the library was loaded in the context of all present
27419 thread groups. The @var{ranges} field specifies the ranges of addresses belonging
27422 @item =library-unloaded,...
27423 Reports that a library was unloaded by the program. This notification
27424 has 3 fields---@var{id}, @var{target-name} and @var{host-name} with
27425 the same meaning as for the @code{=library-loaded} notification.
27426 The @var{thread-group} field, if present, specifies the id of the
27427 thread group in whose context the library was unloaded. If the field is
27428 absent, it means the library was unloaded in the context of all present
27431 @item =traceframe-changed,num=@var{tfnum},tracepoint=@var{tpnum}
27432 @itemx =traceframe-changed,end
27433 Reports that the trace frame was changed and its new number is
27434 @var{tfnum}. The number of the tracepoint associated with this trace
27435 frame is @var{tpnum}.
27437 @item =tsv-created,name=@var{name},initial=@var{initial}
27438 Reports that the new trace state variable @var{name} is created with
27439 initial value @var{initial}.
27441 @item =tsv-deleted,name=@var{name}
27442 @itemx =tsv-deleted
27443 Reports that the trace state variable @var{name} is deleted or all
27444 trace state variables are deleted.
27446 @item =tsv-modified,name=@var{name},initial=@var{initial}[,current=@var{current}]
27447 Reports that the trace state variable @var{name} is modified with
27448 the initial value @var{initial}. The current value @var{current} of
27449 trace state variable is optional and is reported if the current
27450 value of trace state variable is known.
27452 @item =breakpoint-created,bkpt=@{...@}
27453 @itemx =breakpoint-modified,bkpt=@{...@}
27454 @itemx =breakpoint-deleted,id=@var{number}
27455 Reports that a breakpoint was created, modified, or deleted,
27456 respectively. Only user-visible breakpoints are reported to the MI
27459 The @var{bkpt} argument is of the same form as returned by the various
27460 breakpoint commands; @xref{GDB/MI Breakpoint Commands}. The
27461 @var{number} is the ordinal number of the breakpoint.
27463 Note that if a breakpoint is emitted in the result record of a
27464 command, then it will not also be emitted in an async record.
27466 @item =record-started,thread-group="@var{id}",method="@var{method}"[,format="@var{format}"]
27467 @itemx =record-stopped,thread-group="@var{id}"
27468 Execution log recording was either started or stopped on an
27469 inferior. The @var{id} is the @value{GDBN} identifier of the thread
27470 group corresponding to the affected inferior.
27472 The @var{method} field indicates the method used to record execution. If the
27473 method in use supports multiple recording formats, @var{format} will be present
27474 and contain the currently used format. @xref{Process Record and Replay},
27475 for existing method and format values.
27477 @item =cmd-param-changed,param=@var{param},value=@var{value}
27478 Reports that a parameter of the command @code{set @var{param}} is
27479 changed to @var{value}. In the multi-word @code{set} command,
27480 the @var{param} is the whole parameter list to @code{set} command.
27481 For example, In command @code{set check type on}, @var{param}
27482 is @code{check type} and @var{value} is @code{on}.
27484 @item =memory-changed,thread-group=@var{id},addr=@var{addr},len=@var{len}[,type="code"]
27485 Reports that bytes from @var{addr} to @var{data} + @var{len} were
27486 written in an inferior. The @var{id} is the identifier of the
27487 thread group corresponding to the affected inferior. The optional
27488 @code{type="code"} part is reported if the memory written to holds
27492 @node GDB/MI Breakpoint Information
27493 @subsection @sc{gdb/mi} Breakpoint Information
27495 When @value{GDBN} reports information about a breakpoint, a
27496 tracepoint, a watchpoint, or a catchpoint, it uses a tuple with the
27501 The breakpoint number. For a breakpoint that represents one location
27502 of a multi-location breakpoint, this will be a dotted pair, like
27506 The type of the breakpoint. For ordinary breakpoints this will be
27507 @samp{breakpoint}, but many values are possible.
27510 If the type of the breakpoint is @samp{catchpoint}, then this
27511 indicates the exact type of catchpoint.
27514 This is the breakpoint disposition---either @samp{del}, meaning that
27515 the breakpoint will be deleted at the next stop, or @samp{keep},
27516 meaning that the breakpoint will not be deleted.
27519 This indicates whether the breakpoint is enabled, in which case the
27520 value is @samp{y}, or disabled, in which case the value is @samp{n}.
27521 Note that this is not the same as the field @code{enable}.
27524 The address of the breakpoint. This may be a hexidecimal number,
27525 giving the address; or the string @samp{<PENDING>}, for a pending
27526 breakpoint; or the string @samp{<MULTIPLE>}, for a breakpoint with
27527 multiple locations. This field will not be present if no address can
27528 be determined. For example, a watchpoint does not have an address.
27531 If known, the function in which the breakpoint appears.
27532 If not known, this field is not present.
27535 The name of the source file which contains this function, if known.
27536 If not known, this field is not present.
27539 The full file name of the source file which contains this function, if
27540 known. If not known, this field is not present.
27543 The line number at which this breakpoint appears, if known.
27544 If not known, this field is not present.
27547 If the source file is not known, this field may be provided. If
27548 provided, this holds the address of the breakpoint, possibly followed
27552 If this breakpoint is pending, this field is present and holds the
27553 text used to set the breakpoint, as entered by the user.
27556 Where this breakpoint's condition is evaluated, either @samp{host} or
27560 If this is a thread-specific breakpoint, then this identifies the
27561 thread in which the breakpoint can trigger.
27564 If this breakpoint is restricted to a particular Ada task, then this
27565 field will hold the task identifier.
27568 If the breakpoint is conditional, this is the condition expression.
27571 The ignore count of the breakpoint.
27574 The enable count of the breakpoint.
27576 @item traceframe-usage
27579 @item static-tracepoint-marker-string-id
27580 For a static tracepoint, the name of the static tracepoint marker.
27583 For a masked watchpoint, this is the mask.
27586 A tracepoint's pass count.
27588 @item original-location
27589 The location of the breakpoint as originally specified by the user.
27590 This field is optional.
27593 The number of times the breakpoint has been hit.
27596 This field is only given for tracepoints. This is either @samp{y},
27597 meaning that the tracepoint is installed, or @samp{n}, meaning that it
27601 Some extra data, the exact contents of which are type-dependent.
27605 For example, here is what the output of @code{-break-insert}
27606 (@pxref{GDB/MI Breakpoint Commands}) might be:
27609 -> -break-insert main
27610 <- ^done,bkpt=@{number="1",type="breakpoint",disp="keep",
27611 enabled="y",addr="0x08048564",func="main",file="myprog.c",
27612 fullname="/home/nickrob/myprog.c",line="68",thread-groups=["i1"],
27617 @node GDB/MI Frame Information
27618 @subsection @sc{gdb/mi} Frame Information
27620 Response from many MI commands includes an information about stack
27621 frame. This information is a tuple that may have the following
27626 The level of the stack frame. The innermost frame has the level of
27627 zero. This field is always present.
27630 The name of the function corresponding to the frame. This field may
27631 be absent if @value{GDBN} is unable to determine the function name.
27634 The code address for the frame. This field is always present.
27637 The name of the source files that correspond to the frame's code
27638 address. This field may be absent.
27641 The source line corresponding to the frames' code address. This field
27645 The name of the binary file (either executable or shared library) the
27646 corresponds to the frame's code address. This field may be absent.
27650 @node GDB/MI Thread Information
27651 @subsection @sc{gdb/mi} Thread Information
27653 Whenever @value{GDBN} has to report an information about a thread, it
27654 uses a tuple with the following fields. The fields are always present unless
27659 The global numeric id assigned to the thread by @value{GDBN}.
27662 The target-specific string identifying the thread.
27665 Additional information about the thread provided by the target.
27666 It is supposed to be human-readable and not interpreted by the
27667 frontend. This field is optional.
27670 The name of the thread. If the user specified a name using the
27671 @code{thread name} command, then this name is given. Otherwise, if
27672 @value{GDBN} can extract the thread name from the target, then that
27673 name is given. If @value{GDBN} cannot find the thread name, then this
27677 The execution state of the thread, either @samp{stopped} or @samp{running},
27678 depending on whether the thread is presently running.
27681 The stack frame currently executing in the thread. This field is only present
27682 if the thread is stopped. Its format is documented in
27683 @ref{GDB/MI Frame Information}.
27686 The value of this field is an integer number of the processor core the
27687 thread was last seen on. This field is optional.
27690 @node GDB/MI Ada Exception Information
27691 @subsection @sc{gdb/mi} Ada Exception Information
27693 Whenever a @code{*stopped} record is emitted because the program
27694 stopped after hitting an exception catchpoint (@pxref{Set Catchpoints}),
27695 @value{GDBN} provides the name of the exception that was raised via
27696 the @code{exception-name} field. Also, for exceptions that were raised
27697 with an exception message, @value{GDBN} provides that message via
27698 the @code{exception-message} field.
27700 @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
27701 @node GDB/MI Simple Examples
27702 @section Simple Examples of @sc{gdb/mi} Interaction
27703 @cindex @sc{gdb/mi}, simple examples
27705 This subsection presents several simple examples of interaction using
27706 the @sc{gdb/mi} interface. In these examples, @samp{->} means that the
27707 following line is passed to @sc{gdb/mi} as input, while @samp{<-} means
27708 the output received from @sc{gdb/mi}.
27710 Note the line breaks shown in the examples are here only for
27711 readability, they don't appear in the real output.
27713 @subheading Setting a Breakpoint
27715 Setting a breakpoint generates synchronous output which contains detailed
27716 information of the breakpoint.
27719 -> -break-insert main
27720 <- ^done,bkpt=@{number="1",type="breakpoint",disp="keep",
27721 enabled="y",addr="0x08048564",func="main",file="myprog.c",
27722 fullname="/home/nickrob/myprog.c",line="68",thread-groups=["i1"],
27727 @subheading Program Execution
27729 Program execution generates asynchronous records and MI gives the
27730 reason that execution stopped.
27736 <- *stopped,reason="breakpoint-hit",disp="keep",bkptno="1",thread-id="0",
27737 frame=@{addr="0x08048564",func="main",
27738 args=[@{name="argc",value="1"@},@{name="argv",value="0xbfc4d4d4"@}],
27739 file="myprog.c",fullname="/home/nickrob/myprog.c",line="68"@}
27744 <- *stopped,reason="exited-normally"
27748 @subheading Quitting @value{GDBN}
27750 Quitting @value{GDBN} just prints the result class @samp{^exit}.
27758 Please note that @samp{^exit} is printed immediately, but it might
27759 take some time for @value{GDBN} to actually exit. During that time, @value{GDBN}
27760 performs necessary cleanups, including killing programs being debugged
27761 or disconnecting from debug hardware, so the frontend should wait till
27762 @value{GDBN} exits and should only forcibly kill @value{GDBN} if it
27763 fails to exit in reasonable time.
27765 @subheading A Bad Command
27767 Here's what happens if you pass a non-existent command:
27771 <- ^error,msg="Undefined MI command: rubbish"
27776 @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
27777 @node GDB/MI Command Description Format
27778 @section @sc{gdb/mi} Command Description Format
27780 The remaining sections describe blocks of commands. Each block of
27781 commands is laid out in a fashion similar to this section.
27783 @subheading Motivation
27785 The motivation for this collection of commands.
27787 @subheading Introduction
27789 A brief introduction to this collection of commands as a whole.
27791 @subheading Commands
27793 For each command in the block, the following is described:
27795 @subsubheading Synopsis
27798 -command @var{args}@dots{}
27801 @subsubheading Result
27803 @subsubheading @value{GDBN} Command
27805 The corresponding @value{GDBN} CLI command(s), if any.
27807 @subsubheading Example
27809 Example(s) formatted for readability. Some of the described commands have
27810 not been implemented yet and these are labeled N.A.@: (not available).
27813 @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
27814 @node GDB/MI Breakpoint Commands
27815 @section @sc{gdb/mi} Breakpoint Commands
27817 @cindex breakpoint commands for @sc{gdb/mi}
27818 @cindex @sc{gdb/mi}, breakpoint commands
27819 This section documents @sc{gdb/mi} commands for manipulating
27822 @subheading The @code{-break-after} Command
27823 @findex -break-after
27825 @subsubheading Synopsis
27828 -break-after @var{number} @var{count}
27831 The breakpoint number @var{number} is not in effect until it has been
27832 hit @var{count} times. To see how this is reflected in the output of
27833 the @samp{-break-list} command, see the description of the
27834 @samp{-break-list} command below.
27836 @subsubheading @value{GDBN} Command
27838 The corresponding @value{GDBN} command is @samp{ignore}.
27840 @subsubheading Example
27845 ^done,bkpt=@{number="1",type="breakpoint",disp="keep",
27846 enabled="y",addr="0x000100d0",func="main",file="hello.c",
27847 fullname="/home/foo/hello.c",line="5",thread-groups=["i1"],
27855 ^done,BreakpointTable=@{nr_rows="1",nr_cols="6",
27856 hdr=[@{width="3",alignment="-1",col_name="number",colhdr="Num"@},
27857 @{width="14",alignment="-1",col_name="type",colhdr="Type"@},
27858 @{width="4",alignment="-1",col_name="disp",colhdr="Disp"@},
27859 @{width="3",alignment="-1",col_name="enabled",colhdr="Enb"@},
27860 @{width="10",alignment="-1",col_name="addr",colhdr="Address"@},
27861 @{width="40",alignment="2",col_name="what",colhdr="What"@}],
27862 body=[bkpt=@{number="1",type="breakpoint",disp="keep",enabled="y",
27863 addr="0x000100d0",func="main",file="hello.c",fullname="/home/foo/hello.c",
27864 line="5",thread-groups=["i1"],times="0",ignore="3"@}]@}
27869 @subheading The @code{-break-catch} Command
27870 @findex -break-catch
27873 @subheading The @code{-break-commands} Command
27874 @findex -break-commands
27876 @subsubheading Synopsis
27879 -break-commands @var{number} [ @var{command1} ... @var{commandN} ]
27882 Specifies the CLI commands that should be executed when breakpoint
27883 @var{number} is hit. The parameters @var{command1} to @var{commandN}
27884 are the commands. If no command is specified, any previously-set
27885 commands are cleared. @xref{Break Commands}. Typical use of this
27886 functionality is tracing a program, that is, printing of values of
27887 some variables whenever breakpoint is hit and then continuing.
27889 @subsubheading @value{GDBN} Command
27891 The corresponding @value{GDBN} command is @samp{commands}.
27893 @subsubheading Example
27898 ^done,bkpt=@{number="1",type="breakpoint",disp="keep",
27899 enabled="y",addr="0x000100d0",func="main",file="hello.c",
27900 fullname="/home/foo/hello.c",line="5",thread-groups=["i1"],
27903 -break-commands 1 "print v" "continue"
27908 @subheading The @code{-break-condition} Command
27909 @findex -break-condition
27911 @subsubheading Synopsis
27914 -break-condition @var{number} @var{expr}
27917 Breakpoint @var{number} will stop the program only if the condition in
27918 @var{expr} is true. The condition becomes part of the
27919 @samp{-break-list} output (see the description of the @samp{-break-list}
27922 @subsubheading @value{GDBN} Command
27924 The corresponding @value{GDBN} command is @samp{condition}.
27926 @subsubheading Example
27930 -break-condition 1 1
27934 ^done,BreakpointTable=@{nr_rows="1",nr_cols="6",
27935 hdr=[@{width="3",alignment="-1",col_name="number",colhdr="Num"@},
27936 @{width="14",alignment="-1",col_name="type",colhdr="Type"@},
27937 @{width="4",alignment="-1",col_name="disp",colhdr="Disp"@},
27938 @{width="3",alignment="-1",col_name="enabled",colhdr="Enb"@},
27939 @{width="10",alignment="-1",col_name="addr",colhdr="Address"@},
27940 @{width="40",alignment="2",col_name="what",colhdr="What"@}],
27941 body=[bkpt=@{number="1",type="breakpoint",disp="keep",enabled="y",
27942 addr="0x000100d0",func="main",file="hello.c",fullname="/home/foo/hello.c",
27943 line="5",cond="1",thread-groups=["i1"],times="0",ignore="3"@}]@}
27947 @subheading The @code{-break-delete} Command
27948 @findex -break-delete
27950 @subsubheading Synopsis
27953 -break-delete ( @var{breakpoint} )+
27956 Delete the breakpoint(s) whose number(s) are specified in the argument
27957 list. This is obviously reflected in the breakpoint list.
27959 @subsubheading @value{GDBN} Command
27961 The corresponding @value{GDBN} command is @samp{delete}.
27963 @subsubheading Example
27971 ^done,BreakpointTable=@{nr_rows="0",nr_cols="6",
27972 hdr=[@{width="3",alignment="-1",col_name="number",colhdr="Num"@},
27973 @{width="14",alignment="-1",col_name="type",colhdr="Type"@},
27974 @{width="4",alignment="-1",col_name="disp",colhdr="Disp"@},
27975 @{width="3",alignment="-1",col_name="enabled",colhdr="Enb"@},
27976 @{width="10",alignment="-1",col_name="addr",colhdr="Address"@},
27977 @{width="40",alignment="2",col_name="what",colhdr="What"@}],
27982 @subheading The @code{-break-disable} Command
27983 @findex -break-disable
27985 @subsubheading Synopsis
27988 -break-disable ( @var{breakpoint} )+
27991 Disable the named @var{breakpoint}(s). The field @samp{enabled} in the
27992 break list is now set to @samp{n} for the named @var{breakpoint}(s).
27994 @subsubheading @value{GDBN} Command
27996 The corresponding @value{GDBN} command is @samp{disable}.
27998 @subsubheading Example
28006 ^done,BreakpointTable=@{nr_rows="1",nr_cols="6",
28007 hdr=[@{width="3",alignment="-1",col_name="number",colhdr="Num"@},
28008 @{width="14",alignment="-1",col_name="type",colhdr="Type"@},
28009 @{width="4",alignment="-1",col_name="disp",colhdr="Disp"@},
28010 @{width="3",alignment="-1",col_name="enabled",colhdr="Enb"@},
28011 @{width="10",alignment="-1",col_name="addr",colhdr="Address"@},
28012 @{width="40",alignment="2",col_name="what",colhdr="What"@}],
28013 body=[bkpt=@{number="2",type="breakpoint",disp="keep",enabled="n",
28014 addr="0x000100d0",func="main",file="hello.c",fullname="/home/foo/hello.c",
28015 line="5",thread-groups=["i1"],times="0"@}]@}
28019 @subheading The @code{-break-enable} Command
28020 @findex -break-enable
28022 @subsubheading Synopsis
28025 -break-enable ( @var{breakpoint} )+
28028 Enable (previously disabled) @var{breakpoint}(s).
28030 @subsubheading @value{GDBN} Command
28032 The corresponding @value{GDBN} command is @samp{enable}.
28034 @subsubheading Example
28042 ^done,BreakpointTable=@{nr_rows="1",nr_cols="6",
28043 hdr=[@{width="3",alignment="-1",col_name="number",colhdr="Num"@},
28044 @{width="14",alignment="-1",col_name="type",colhdr="Type"@},
28045 @{width="4",alignment="-1",col_name="disp",colhdr="Disp"@},
28046 @{width="3",alignment="-1",col_name="enabled",colhdr="Enb"@},
28047 @{width="10",alignment="-1",col_name="addr",colhdr="Address"@},
28048 @{width="40",alignment="2",col_name="what",colhdr="What"@}],
28049 body=[bkpt=@{number="2",type="breakpoint",disp="keep",enabled="y",
28050 addr="0x000100d0",func="main",file="hello.c",fullname="/home/foo/hello.c",
28051 line="5",thread-groups=["i1"],times="0"@}]@}
28055 @subheading The @code{-break-info} Command
28056 @findex -break-info
28058 @subsubheading Synopsis
28061 -break-info @var{breakpoint}
28065 Get information about a single breakpoint.
28067 The result is a table of breakpoints. @xref{GDB/MI Breakpoint
28068 Information}, for details on the format of each breakpoint in the
28071 @subsubheading @value{GDBN} Command
28073 The corresponding @value{GDBN} command is @samp{info break @var{breakpoint}}.
28075 @subsubheading Example
28078 @subheading The @code{-break-insert} Command
28079 @findex -break-insert
28080 @anchor{-break-insert}
28082 @subsubheading Synopsis
28085 -break-insert [ -t ] [ -h ] [ -f ] [ -d ] [ -a ]
28086 [ -c @var{condition} ] [ -i @var{ignore-count} ]
28087 [ -p @var{thread-id} ] [ @var{location} ]
28091 If specified, @var{location}, can be one of:
28094 @item linespec location
28095 A linespec location. @xref{Linespec Locations}.
28097 @item explicit location
28098 An explicit location. @sc{gdb/mi} explicit locations are
28099 analogous to the CLI's explicit locations using the option names
28100 listed below. @xref{Explicit Locations}.
28103 @item --source @var{filename}
28104 The source file name of the location. This option requires the use
28105 of either @samp{--function} or @samp{--line}.
28107 @item --function @var{function}
28108 The name of a function or method.
28110 @item --label @var{label}
28111 The name of a label.
28113 @item --line @var{lineoffset}
28114 An absolute or relative line offset from the start of the location.
28117 @item address location
28118 An address location, *@var{address}. @xref{Address Locations}.
28122 The possible optional parameters of this command are:
28126 Insert a temporary breakpoint.
28128 Insert a hardware breakpoint.
28130 If @var{location} cannot be parsed (for example if it
28131 refers to unknown files or functions), create a pending
28132 breakpoint. Without this flag, @value{GDBN} will report
28133 an error, and won't create a breakpoint, if @var{location}
28136 Create a disabled breakpoint.
28138 Create a tracepoint. @xref{Tracepoints}. When this parameter
28139 is used together with @samp{-h}, a fast tracepoint is created.
28140 @item -c @var{condition}
28141 Make the breakpoint conditional on @var{condition}.
28142 @item -i @var{ignore-count}
28143 Initialize the @var{ignore-count}.
28144 @item -p @var{thread-id}
28145 Restrict the breakpoint to the thread with the specified global
28149 @subsubheading Result
28151 @xref{GDB/MI Breakpoint Information}, for details on the format of the
28152 resulting breakpoint.
28154 Note: this format is open to change.
28155 @c An out-of-band breakpoint instead of part of the result?
28157 @subsubheading @value{GDBN} Command
28159 The corresponding @value{GDBN} commands are @samp{break}, @samp{tbreak},
28160 @samp{hbreak}, and @samp{thbreak}. @c and @samp{rbreak}.
28162 @subsubheading Example
28167 ^done,bkpt=@{number="1",addr="0x0001072c",file="recursive2.c",
28168 fullname="/home/foo/recursive2.c,line="4",thread-groups=["i1"],
28171 -break-insert -t foo
28172 ^done,bkpt=@{number="2",addr="0x00010774",file="recursive2.c",
28173 fullname="/home/foo/recursive2.c,line="11",thread-groups=["i1"],
28177 ^done,BreakpointTable=@{nr_rows="2",nr_cols="6",
28178 hdr=[@{width="3",alignment="-1",col_name="number",colhdr="Num"@},
28179 @{width="14",alignment="-1",col_name="type",colhdr="Type"@},
28180 @{width="4",alignment="-1",col_name="disp",colhdr="Disp"@},
28181 @{width="3",alignment="-1",col_name="enabled",colhdr="Enb"@},
28182 @{width="10",alignment="-1",col_name="addr",colhdr="Address"@},
28183 @{width="40",alignment="2",col_name="what",colhdr="What"@}],
28184 body=[bkpt=@{number="1",type="breakpoint",disp="keep",enabled="y",
28185 addr="0x0001072c", func="main",file="recursive2.c",
28186 fullname="/home/foo/recursive2.c,"line="4",thread-groups=["i1"],
28188 bkpt=@{number="2",type="breakpoint",disp="del",enabled="y",
28189 addr="0x00010774",func="foo",file="recursive2.c",
28190 fullname="/home/foo/recursive2.c",line="11",thread-groups=["i1"],
28193 @c -break-insert -r foo.*
28194 @c ~int foo(int, int);
28195 @c ^done,bkpt=@{number="3",addr="0x00010774",file="recursive2.c,
28196 @c "fullname="/home/foo/recursive2.c",line="11",thread-groups=["i1"],
28201 @subheading The @code{-dprintf-insert} Command
28202 @findex -dprintf-insert
28204 @subsubheading Synopsis
28207 -dprintf-insert [ -t ] [ -f ] [ -d ]
28208 [ -c @var{condition} ] [ -i @var{ignore-count} ]
28209 [ -p @var{thread-id} ] [ @var{location} ] [ @var{format} ]
28214 If supplied, @var{location} may be specified the same way as for
28215 the @code{-break-insert} command. @xref{-break-insert}.
28217 The possible optional parameters of this command are:
28221 Insert a temporary breakpoint.
28223 If @var{location} cannot be parsed (for example, if it
28224 refers to unknown files or functions), create a pending
28225 breakpoint. Without this flag, @value{GDBN} will report
28226 an error, and won't create a breakpoint, if @var{location}
28229 Create a disabled breakpoint.
28230 @item -c @var{condition}
28231 Make the breakpoint conditional on @var{condition}.
28232 @item -i @var{ignore-count}
28233 Set the ignore count of the breakpoint (@pxref{Conditions, ignore count})
28234 to @var{ignore-count}.
28235 @item -p @var{thread-id}
28236 Restrict the breakpoint to the thread with the specified global
28240 @subsubheading Result
28242 @xref{GDB/MI Breakpoint Information}, for details on the format of the
28243 resulting breakpoint.
28245 @c An out-of-band breakpoint instead of part of the result?
28247 @subsubheading @value{GDBN} Command
28249 The corresponding @value{GDBN} command is @samp{dprintf}.
28251 @subsubheading Example
28255 4-dprintf-insert foo "At foo entry\n"
28256 4^done,bkpt=@{number="1",type="dprintf",disp="keep",enabled="y",
28257 addr="0x000000000040061b",func="foo",file="mi-dprintf.c",
28258 fullname="mi-dprintf.c",line="25",thread-groups=["i1"],
28259 times="0",script=@{"printf \"At foo entry\\n\"","continue"@},
28260 original-location="foo"@}
28262 5-dprintf-insert 26 "arg=%d, g=%d\n" arg g
28263 5^done,bkpt=@{number="2",type="dprintf",disp="keep",enabled="y",
28264 addr="0x000000000040062a",func="foo",file="mi-dprintf.c",
28265 fullname="mi-dprintf.c",line="26",thread-groups=["i1"],
28266 times="0",script=@{"printf \"arg=%d, g=%d\\n\", arg, g","continue"@},
28267 original-location="mi-dprintf.c:26"@}
28271 @subheading The @code{-break-list} Command
28272 @findex -break-list
28274 @subsubheading Synopsis
28280 Displays the list of inserted breakpoints, showing the following fields:
28284 number of the breakpoint
28286 type of the breakpoint: @samp{breakpoint} or @samp{watchpoint}
28288 should the breakpoint be deleted or disabled when it is hit: @samp{keep}
28291 is the breakpoint enabled or no: @samp{y} or @samp{n}
28293 memory location at which the breakpoint is set
28295 logical location of the breakpoint, expressed by function name, file
28297 @item Thread-groups
28298 list of thread groups to which this breakpoint applies
28300 number of times the breakpoint has been hit
28303 If there are no breakpoints or watchpoints, the @code{BreakpointTable}
28304 @code{body} field is an empty list.
28306 @subsubheading @value{GDBN} Command
28308 The corresponding @value{GDBN} command is @samp{info break}.
28310 @subsubheading Example
28315 ^done,BreakpointTable=@{nr_rows="2",nr_cols="6",
28316 hdr=[@{width="3",alignment="-1",col_name="number",colhdr="Num"@},
28317 @{width="14",alignment="-1",col_name="type",colhdr="Type"@},
28318 @{width="4",alignment="-1",col_name="disp",colhdr="Disp"@},
28319 @{width="3",alignment="-1",col_name="enabled",colhdr="Enb"@},
28320 @{width="10",alignment="-1",col_name="addr",colhdr="Address"@},
28321 @{width="40",alignment="2",col_name="what",colhdr="What"@}],
28322 body=[bkpt=@{number="1",type="breakpoint",disp="keep",enabled="y",
28323 addr="0x000100d0",func="main",file="hello.c",line="5",thread-groups=["i1"],
28325 bkpt=@{number="2",type="breakpoint",disp="keep",enabled="y",
28326 addr="0x00010114",func="foo",file="hello.c",fullname="/home/foo/hello.c",
28327 line="13",thread-groups=["i1"],times="0"@}]@}
28331 Here's an example of the result when there are no breakpoints:
28336 ^done,BreakpointTable=@{nr_rows="0",nr_cols="6",
28337 hdr=[@{width="3",alignment="-1",col_name="number",colhdr="Num"@},
28338 @{width="14",alignment="-1",col_name="type",colhdr="Type"@},
28339 @{width="4",alignment="-1",col_name="disp",colhdr="Disp"@},
28340 @{width="3",alignment="-1",col_name="enabled",colhdr="Enb"@},
28341 @{width="10",alignment="-1",col_name="addr",colhdr="Address"@},
28342 @{width="40",alignment="2",col_name="what",colhdr="What"@}],
28347 @subheading The @code{-break-passcount} Command
28348 @findex -break-passcount
28350 @subsubheading Synopsis
28353 -break-passcount @var{tracepoint-number} @var{passcount}
28356 Set the passcount for tracepoint @var{tracepoint-number} to
28357 @var{passcount}. If the breakpoint referred to by @var{tracepoint-number}
28358 is not a tracepoint, error is emitted. This corresponds to CLI
28359 command @samp{passcount}.
28361 @subheading The @code{-break-watch} Command
28362 @findex -break-watch
28364 @subsubheading Synopsis
28367 -break-watch [ -a | -r ]
28370 Create a watchpoint. With the @samp{-a} option it will create an
28371 @dfn{access} watchpoint, i.e., a watchpoint that triggers either on a
28372 read from or on a write to the memory location. With the @samp{-r}
28373 option, the watchpoint created is a @dfn{read} watchpoint, i.e., it will
28374 trigger only when the memory location is accessed for reading. Without
28375 either of the options, the watchpoint created is a regular watchpoint,
28376 i.e., it will trigger when the memory location is accessed for writing.
28377 @xref{Set Watchpoints, , Setting Watchpoints}.
28379 Note that @samp{-break-list} will report a single list of watchpoints and
28380 breakpoints inserted.
28382 @subsubheading @value{GDBN} Command
28384 The corresponding @value{GDBN} commands are @samp{watch}, @samp{awatch}, and
28387 @subsubheading Example
28389 Setting a watchpoint on a variable in the @code{main} function:
28394 ^done,wpt=@{number="2",exp="x"@}
28399 *stopped,reason="watchpoint-trigger",wpt=@{number="2",exp="x"@},
28400 value=@{old="-268439212",new="55"@},
28401 frame=@{func="main",args=[],file="recursive2.c",
28402 fullname="/home/foo/bar/recursive2.c",line="5"@}
28406 Setting a watchpoint on a variable local to a function. @value{GDBN} will stop
28407 the program execution twice: first for the variable changing value, then
28408 for the watchpoint going out of scope.
28413 ^done,wpt=@{number="5",exp="C"@}
28418 *stopped,reason="watchpoint-trigger",
28419 wpt=@{number="5",exp="C"@},value=@{old="-276895068",new="3"@},
28420 frame=@{func="callee4",args=[],
28421 file="../../../devo/gdb/testsuite/gdb.mi/basics.c",
28422 fullname="/home/foo/bar/devo/gdb/testsuite/gdb.mi/basics.c",line="13"@}
28427 *stopped,reason="watchpoint-scope",wpnum="5",
28428 frame=@{func="callee3",args=[@{name="strarg",
28429 value="0x11940 \"A string argument.\""@}],
28430 file="../../../devo/gdb/testsuite/gdb.mi/basics.c",
28431 fullname="/home/foo/bar/devo/gdb/testsuite/gdb.mi/basics.c",line="18"@}
28435 Listing breakpoints and watchpoints, at different points in the program
28436 execution. Note that once the watchpoint goes out of scope, it is
28442 ^done,wpt=@{number="2",exp="C"@}
28445 ^done,BreakpointTable=@{nr_rows="2",nr_cols="6",
28446 hdr=[@{width="3",alignment="-1",col_name="number",colhdr="Num"@},
28447 @{width="14",alignment="-1",col_name="type",colhdr="Type"@},
28448 @{width="4",alignment="-1",col_name="disp",colhdr="Disp"@},
28449 @{width="3",alignment="-1",col_name="enabled",colhdr="Enb"@},
28450 @{width="10",alignment="-1",col_name="addr",colhdr="Address"@},
28451 @{width="40",alignment="2",col_name="what",colhdr="What"@}],
28452 body=[bkpt=@{number="1",type="breakpoint",disp="keep",enabled="y",
28453 addr="0x00010734",func="callee4",
28454 file="../../../devo/gdb/testsuite/gdb.mi/basics.c",
28455 fullname="/home/foo/devo/gdb/testsuite/gdb.mi/basics.c"line="8",thread-groups=["i1"],
28457 bkpt=@{number="2",type="watchpoint",disp="keep",
28458 enabled="y",addr="",what="C",thread-groups=["i1"],times="0"@}]@}
28463 *stopped,reason="watchpoint-trigger",wpt=@{number="2",exp="C"@},
28464 value=@{old="-276895068",new="3"@},
28465 frame=@{func="callee4",args=[],
28466 file="../../../devo/gdb/testsuite/gdb.mi/basics.c",
28467 fullname="/home/foo/bar/devo/gdb/testsuite/gdb.mi/basics.c",line="13"@}
28470 ^done,BreakpointTable=@{nr_rows="2",nr_cols="6",
28471 hdr=[@{width="3",alignment="-1",col_name="number",colhdr="Num"@},
28472 @{width="14",alignment="-1",col_name="type",colhdr="Type"@},
28473 @{width="4",alignment="-1",col_name="disp",colhdr="Disp"@},
28474 @{width="3",alignment="-1",col_name="enabled",colhdr="Enb"@},
28475 @{width="10",alignment="-1",col_name="addr",colhdr="Address"@},
28476 @{width="40",alignment="2",col_name="what",colhdr="What"@}],
28477 body=[bkpt=@{number="1",type="breakpoint",disp="keep",enabled="y",
28478 addr="0x00010734",func="callee4",
28479 file="../../../devo/gdb/testsuite/gdb.mi/basics.c",
28480 fullname="/home/foo/devo/gdb/testsuite/gdb.mi/basics.c",line="8",thread-groups=["i1"],
28482 bkpt=@{number="2",type="watchpoint",disp="keep",
28483 enabled="y",addr="",what="C",thread-groups=["i1"],times="-5"@}]@}
28487 ^done,reason="watchpoint-scope",wpnum="2",
28488 frame=@{func="callee3",args=[@{name="strarg",
28489 value="0x11940 \"A string argument.\""@}],
28490 file="../../../devo/gdb/testsuite/gdb.mi/basics.c",
28491 fullname="/home/foo/bar/devo/gdb/testsuite/gdb.mi/basics.c",line="18"@}
28494 ^done,BreakpointTable=@{nr_rows="1",nr_cols="6",
28495 hdr=[@{width="3",alignment="-1",col_name="number",colhdr="Num"@},
28496 @{width="14",alignment="-1",col_name="type",colhdr="Type"@},
28497 @{width="4",alignment="-1",col_name="disp",colhdr="Disp"@},
28498 @{width="3",alignment="-1",col_name="enabled",colhdr="Enb"@},
28499 @{width="10",alignment="-1",col_name="addr",colhdr="Address"@},
28500 @{width="40",alignment="2",col_name="what",colhdr="What"@}],
28501 body=[bkpt=@{number="1",type="breakpoint",disp="keep",enabled="y",
28502 addr="0x00010734",func="callee4",
28503 file="../../../devo/gdb/testsuite/gdb.mi/basics.c",
28504 fullname="/home/foo/devo/gdb/testsuite/gdb.mi/basics.c",line="8",
28505 thread-groups=["i1"],times="1"@}]@}
28510 @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
28511 @node GDB/MI Catchpoint Commands
28512 @section @sc{gdb/mi} Catchpoint Commands
28514 This section documents @sc{gdb/mi} commands for manipulating
28518 * Shared Library GDB/MI Catchpoint Commands::
28519 * Ada Exception GDB/MI Catchpoint Commands::
28522 @node Shared Library GDB/MI Catchpoint Commands
28523 @subsection Shared Library @sc{gdb/mi} Catchpoints
28525 @subheading The @code{-catch-load} Command
28526 @findex -catch-load
28528 @subsubheading Synopsis
28531 -catch-load [ -t ] [ -d ] @var{regexp}
28534 Add a catchpoint for library load events. If the @samp{-t} option is used,
28535 the catchpoint is a temporary one (@pxref{Set Breaks, ,Setting
28536 Breakpoints}). If the @samp{-d} option is used, the catchpoint is created
28537 in a disabled state. The @samp{regexp} argument is a regular
28538 expression used to match the name of the loaded library.
28541 @subsubheading @value{GDBN} Command
28543 The corresponding @value{GDBN} command is @samp{catch load}.
28545 @subsubheading Example
28548 -catch-load -t foo.so
28549 ^done,bkpt=@{number="1",type="catchpoint",disp="del",enabled="y",
28550 what="load of library matching foo.so",catch-type="load",times="0"@}
28555 @subheading The @code{-catch-unload} Command
28556 @findex -catch-unload
28558 @subsubheading Synopsis
28561 -catch-unload [ -t ] [ -d ] @var{regexp}
28564 Add a catchpoint for library unload events. If the @samp{-t} option is
28565 used, the catchpoint is a temporary one (@pxref{Set Breaks, ,Setting
28566 Breakpoints}). If the @samp{-d} option is used, the catchpoint is
28567 created in a disabled state. The @samp{regexp} argument is a regular
28568 expression used to match the name of the unloaded library.
28570 @subsubheading @value{GDBN} Command
28572 The corresponding @value{GDBN} command is @samp{catch unload}.
28574 @subsubheading Example
28577 -catch-unload -d bar.so
28578 ^done,bkpt=@{number="2",type="catchpoint",disp="keep",enabled="n",
28579 what="load of library matching bar.so",catch-type="unload",times="0"@}
28583 @node Ada Exception GDB/MI Catchpoint Commands
28584 @subsection Ada Exception @sc{gdb/mi} Catchpoints
28586 The following @sc{gdb/mi} commands can be used to create catchpoints
28587 that stop the execution when Ada exceptions are being raised.
28589 @subheading The @code{-catch-assert} Command
28590 @findex -catch-assert
28592 @subsubheading Synopsis
28595 -catch-assert [ -c @var{condition}] [ -d ] [ -t ]
28598 Add a catchpoint for failed Ada assertions.
28600 The possible optional parameters for this command are:
28603 @item -c @var{condition}
28604 Make the catchpoint conditional on @var{condition}.
28606 Create a disabled catchpoint.
28608 Create a temporary catchpoint.
28611 @subsubheading @value{GDBN} Command
28613 The corresponding @value{GDBN} command is @samp{catch assert}.
28615 @subsubheading Example
28619 ^done,bkptno="5",bkpt=@{number="5",type="breakpoint",disp="keep",
28620 enabled="y",addr="0x0000000000404888",what="failed Ada assertions",
28621 thread-groups=["i1"],times="0",
28622 original-location="__gnat_debug_raise_assert_failure"@}
28626 @subheading The @code{-catch-exception} Command
28627 @findex -catch-exception
28629 @subsubheading Synopsis
28632 -catch-exception [ -c @var{condition}] [ -d ] [ -e @var{exception-name} ]
28636 Add a catchpoint stopping when Ada exceptions are raised.
28637 By default, the command stops the program when any Ada exception
28638 gets raised. But it is also possible, by using some of the
28639 optional parameters described below, to create more selective
28642 The possible optional parameters for this command are:
28645 @item -c @var{condition}
28646 Make the catchpoint conditional on @var{condition}.
28648 Create a disabled catchpoint.
28649 @item -e @var{exception-name}
28650 Only stop when @var{exception-name} is raised. This option cannot
28651 be used combined with @samp{-u}.
28653 Create a temporary catchpoint.
28655 Stop only when an unhandled exception gets raised. This option
28656 cannot be used combined with @samp{-e}.
28659 @subsubheading @value{GDBN} Command
28661 The corresponding @value{GDBN} commands are @samp{catch exception}
28662 and @samp{catch exception unhandled}.
28664 @subsubheading Example
28667 -catch-exception -e Program_Error
28668 ^done,bkptno="4",bkpt=@{number="4",type="breakpoint",disp="keep",
28669 enabled="y",addr="0x0000000000404874",
28670 what="`Program_Error' Ada exception", thread-groups=["i1"],
28671 times="0",original-location="__gnat_debug_raise_exception"@}
28675 @subheading The @code{-catch-handlers} Command
28676 @findex -catch-handlers
28678 @subsubheading Synopsis
28681 -catch-handlers [ -c @var{condition}] [ -d ] [ -e @var{exception-name} ]
28685 Add a catchpoint stopping when Ada exceptions are handled.
28686 By default, the command stops the program when any Ada exception
28687 gets handled. But it is also possible, by using some of the
28688 optional parameters described below, to create more selective
28691 The possible optional parameters for this command are:
28694 @item -c @var{condition}
28695 Make the catchpoint conditional on @var{condition}.
28697 Create a disabled catchpoint.
28698 @item -e @var{exception-name}
28699 Only stop when @var{exception-name} is handled.
28701 Create a temporary catchpoint.
28704 @subsubheading @value{GDBN} Command
28706 The corresponding @value{GDBN} command is @samp{catch handlers}.
28708 @subsubheading Example
28711 -catch-handlers -e Constraint_Error
28712 ^done,bkptno="4",bkpt=@{number="4",type="breakpoint",disp="keep",
28713 enabled="y",addr="0x0000000000402f68",
28714 what="`Constraint_Error' Ada exception handlers",thread-groups=["i1"],
28715 times="0",original-location="__gnat_begin_handler"@}
28719 @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
28720 @node GDB/MI Program Context
28721 @section @sc{gdb/mi} Program Context
28723 @subheading The @code{-exec-arguments} Command
28724 @findex -exec-arguments
28727 @subsubheading Synopsis
28730 -exec-arguments @var{args}
28733 Set the inferior program arguments, to be used in the next
28736 @subsubheading @value{GDBN} Command
28738 The corresponding @value{GDBN} command is @samp{set args}.
28740 @subsubheading Example
28744 -exec-arguments -v word
28751 @subheading The @code{-exec-show-arguments} Command
28752 @findex -exec-show-arguments
28754 @subsubheading Synopsis
28757 -exec-show-arguments
28760 Print the arguments of the program.
28762 @subsubheading @value{GDBN} Command
28764 The corresponding @value{GDBN} command is @samp{show args}.
28766 @subsubheading Example
28771 @subheading The @code{-environment-cd} Command
28772 @findex -environment-cd
28774 @subsubheading Synopsis
28777 -environment-cd @var{pathdir}
28780 Set @value{GDBN}'s working directory.
28782 @subsubheading @value{GDBN} Command
28784 The corresponding @value{GDBN} command is @samp{cd}.
28786 @subsubheading Example
28790 -environment-cd /kwikemart/marge/ezannoni/flathead-dev/devo/gdb
28796 @subheading The @code{-environment-directory} Command
28797 @findex -environment-directory
28799 @subsubheading Synopsis
28802 -environment-directory [ -r ] [ @var{pathdir} ]+
28805 Add directories @var{pathdir} to beginning of search path for source files.
28806 If the @samp{-r} option is used, the search path is reset to the default
28807 search path. If directories @var{pathdir} are supplied in addition to the
28808 @samp{-r} option, the search path is first reset and then addition
28810 Multiple directories may be specified, separated by blanks. Specifying
28811 multiple directories in a single command
28812 results in the directories added to the beginning of the
28813 search path in the same order they were presented in the command.
28814 If blanks are needed as
28815 part of a directory name, double-quotes should be used around
28816 the name. In the command output, the path will show up separated
28817 by the system directory-separator character. The directory-separator
28818 character must not be used
28819 in any directory name.
28820 If no directories are specified, the current search path is displayed.
28822 @subsubheading @value{GDBN} Command
28824 The corresponding @value{GDBN} command is @samp{dir}.
28826 @subsubheading Example
28830 -environment-directory /kwikemart/marge/ezannoni/flathead-dev/devo/gdb
28831 ^done,source-path="/kwikemart/marge/ezannoni/flathead-dev/devo/gdb:$cdir:$cwd"
28833 -environment-directory ""
28834 ^done,source-path="/kwikemart/marge/ezannoni/flathead-dev/devo/gdb:$cdir:$cwd"
28836 -environment-directory -r /home/jjohnstn/src/gdb /usr/src
28837 ^done,source-path="/home/jjohnstn/src/gdb:/usr/src:$cdir:$cwd"
28839 -environment-directory -r
28840 ^done,source-path="$cdir:$cwd"
28845 @subheading The @code{-environment-path} Command
28846 @findex -environment-path
28848 @subsubheading Synopsis
28851 -environment-path [ -r ] [ @var{pathdir} ]+
28854 Add directories @var{pathdir} to beginning of search path for object files.
28855 If the @samp{-r} option is used, the search path is reset to the original
28856 search path that existed at gdb start-up. If directories @var{pathdir} are
28857 supplied in addition to the
28858 @samp{-r} option, the search path is first reset and then addition
28860 Multiple directories may be specified, separated by blanks. Specifying
28861 multiple directories in a single command
28862 results in the directories added to the beginning of the
28863 search path in the same order they were presented in the command.
28864 If blanks are needed as
28865 part of a directory name, double-quotes should be used around
28866 the name. In the command output, the path will show up separated
28867 by the system directory-separator character. The directory-separator
28868 character must not be used
28869 in any directory name.
28870 If no directories are specified, the current path is displayed.
28873 @subsubheading @value{GDBN} Command
28875 The corresponding @value{GDBN} command is @samp{path}.
28877 @subsubheading Example
28882 ^done,path="/usr/bin"
28884 -environment-path /kwikemart/marge/ezannoni/flathead-dev/ppc-eabi/gdb /bin
28885 ^done,path="/kwikemart/marge/ezannoni/flathead-dev/ppc-eabi/gdb:/bin:/usr/bin"
28887 -environment-path -r /usr/local/bin
28888 ^done,path="/usr/local/bin:/usr/bin"
28893 @subheading The @code{-environment-pwd} Command
28894 @findex -environment-pwd
28896 @subsubheading Synopsis
28902 Show the current working directory.
28904 @subsubheading @value{GDBN} Command
28906 The corresponding @value{GDBN} command is @samp{pwd}.
28908 @subsubheading Example
28913 ^done,cwd="/kwikemart/marge/ezannoni/flathead-dev/devo/gdb"
28917 @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
28918 @node GDB/MI Thread Commands
28919 @section @sc{gdb/mi} Thread Commands
28922 @subheading The @code{-thread-info} Command
28923 @findex -thread-info
28925 @subsubheading Synopsis
28928 -thread-info [ @var{thread-id} ]
28931 Reports information about either a specific thread, if the
28932 @var{thread-id} parameter is present, or about all threads.
28933 @var{thread-id} is the thread's global thread ID. When printing
28934 information about all threads, also reports the global ID of the
28937 @subsubheading @value{GDBN} Command
28939 The @samp{info thread} command prints the same information
28942 @subsubheading Result
28944 The result contains the following attributes:
28948 A list of threads. The format of the elements of the list is described in
28949 @ref{GDB/MI Thread Information}.
28951 @item current-thread-id
28952 The global id of the currently selected thread. This field is omitted if there
28953 is no selected thread (for example, when the selected inferior is not running,
28954 and therefore has no threads) or if a @var{thread-id} argument was passed to
28959 @subsubheading Example
28964 @{id="2",target-id="Thread 0xb7e14b90 (LWP 21257)",
28965 frame=@{level="0",addr="0xffffe410",func="__kernel_vsyscall",
28966 args=[]@},state="running"@},
28967 @{id="1",target-id="Thread 0xb7e156b0 (LWP 21254)",
28968 frame=@{level="0",addr="0x0804891f",func="foo",
28969 args=[@{name="i",value="10"@}],
28970 file="/tmp/a.c",fullname="/tmp/a.c",line="158"@},
28971 state="running"@}],
28972 current-thread-id="1"
28976 @subheading The @code{-thread-list-ids} Command
28977 @findex -thread-list-ids
28979 @subsubheading Synopsis
28985 Produces a list of the currently known global @value{GDBN} thread ids.
28986 At the end of the list it also prints the total number of such
28989 This command is retained for historical reasons, the
28990 @code{-thread-info} command should be used instead.
28992 @subsubheading @value{GDBN} Command
28994 Part of @samp{info threads} supplies the same information.
28996 @subsubheading Example
29001 ^done,thread-ids=@{thread-id="3",thread-id="2",thread-id="1"@},
29002 current-thread-id="1",number-of-threads="3"
29007 @subheading The @code{-thread-select} Command
29008 @findex -thread-select
29010 @subsubheading Synopsis
29013 -thread-select @var{thread-id}
29016 Make thread with global thread number @var{thread-id} the current
29017 thread. It prints the number of the new current thread, and the
29018 topmost frame for that thread.
29020 This command is deprecated in favor of explicitly using the
29021 @samp{--thread} option to each command.
29023 @subsubheading @value{GDBN} Command
29025 The corresponding @value{GDBN} command is @samp{thread}.
29027 @subsubheading Example
29034 *stopped,reason="end-stepping-range",thread-id="2",line="187",
29035 file="../../../devo/gdb/testsuite/gdb.threads/linux-dp.c"
29039 thread-ids=@{thread-id="3",thread-id="2",thread-id="1"@},
29040 number-of-threads="3"
29043 ^done,new-thread-id="3",
29044 frame=@{level="0",func="vprintf",
29045 args=[@{name="format",value="0x8048e9c \"%*s%c %d %c\\n\""@},
29046 @{name="arg",value="0x2"@}],file="vprintf.c",line="31"@}
29050 @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
29051 @node GDB/MI Ada Tasking Commands
29052 @section @sc{gdb/mi} Ada Tasking Commands
29054 @subheading The @code{-ada-task-info} Command
29055 @findex -ada-task-info
29057 @subsubheading Synopsis
29060 -ada-task-info [ @var{task-id} ]
29063 Reports information about either a specific Ada task, if the
29064 @var{task-id} parameter is present, or about all Ada tasks.
29066 @subsubheading @value{GDBN} Command
29068 The @samp{info tasks} command prints the same information
29069 about all Ada tasks (@pxref{Ada Tasks}).
29071 @subsubheading Result
29073 The result is a table of Ada tasks. The following columns are
29074 defined for each Ada task:
29078 This field exists only for the current thread. It has the value @samp{*}.
29081 The identifier that @value{GDBN} uses to refer to the Ada task.
29084 The identifier that the target uses to refer to the Ada task.
29087 The global thread identifier of the thread corresponding to the Ada
29090 This field should always exist, as Ada tasks are always implemented
29091 on top of a thread. But if @value{GDBN} cannot find this corresponding
29092 thread for any reason, the field is omitted.
29095 This field exists only when the task was created by another task.
29096 In this case, it provides the ID of the parent task.
29099 The base priority of the task.
29102 The current state of the task. For a detailed description of the
29103 possible states, see @ref{Ada Tasks}.
29106 The name of the task.
29110 @subsubheading Example
29114 ^done,tasks=@{nr_rows="3",nr_cols="8",
29115 hdr=[@{width="1",alignment="-1",col_name="current",colhdr=""@},
29116 @{width="3",alignment="1",col_name="id",colhdr="ID"@},
29117 @{width="9",alignment="1",col_name="task-id",colhdr="TID"@},
29118 @{width="4",alignment="1",col_name="thread-id",colhdr=""@},
29119 @{width="4",alignment="1",col_name="parent-id",colhdr="P-ID"@},
29120 @{width="3",alignment="1",col_name="priority",colhdr="Pri"@},
29121 @{width="22",alignment="-1",col_name="state",colhdr="State"@},
29122 @{width="1",alignment="2",col_name="name",colhdr="Name"@}],
29123 body=[@{current="*",id="1",task-id=" 644010",thread-id="1",priority="48",
29124 state="Child Termination Wait",name="main_task"@}]@}
29128 @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
29129 @node GDB/MI Program Execution
29130 @section @sc{gdb/mi} Program Execution
29132 These are the asynchronous commands which generate the out-of-band
29133 record @samp{*stopped}. Currently @value{GDBN} only really executes
29134 asynchronously with remote targets and this interaction is mimicked in
29137 @subheading The @code{-exec-continue} Command
29138 @findex -exec-continue
29140 @subsubheading Synopsis
29143 -exec-continue [--reverse] [--all|--thread-group N]
29146 Resumes the execution of the inferior program, which will continue
29147 to execute until it reaches a debugger stop event. If the
29148 @samp{--reverse} option is specified, execution resumes in reverse until
29149 it reaches a stop event. Stop events may include
29152 breakpoints or watchpoints
29154 signals or exceptions
29156 the end of the process (or its beginning under @samp{--reverse})
29158 the end or beginning of a replay log if one is being used.
29160 In all-stop mode (@pxref{All-Stop
29161 Mode}), may resume only one thread, or all threads, depending on the
29162 value of the @samp{scheduler-locking} variable. If @samp{--all} is
29163 specified, all threads (in all inferiors) will be resumed. The @samp{--all} option is
29164 ignored in all-stop mode. If the @samp{--thread-group} options is
29165 specified, then all threads in that thread group are resumed.
29167 @subsubheading @value{GDBN} Command
29169 The corresponding @value{GDBN} corresponding is @samp{continue}.
29171 @subsubheading Example
29178 *stopped,reason="breakpoint-hit",disp="keep",bkptno="2",frame=@{
29179 func="foo",args=[],file="hello.c",fullname="/home/foo/bar/hello.c",
29185 @subheading The @code{-exec-finish} Command
29186 @findex -exec-finish
29188 @subsubheading Synopsis
29191 -exec-finish [--reverse]
29194 Resumes the execution of the inferior program until the current
29195 function is exited. Displays the results returned by the function.
29196 If the @samp{--reverse} option is specified, resumes the reverse
29197 execution of the inferior program until the point where current
29198 function was called.
29200 @subsubheading @value{GDBN} Command
29202 The corresponding @value{GDBN} command is @samp{finish}.
29204 @subsubheading Example
29206 Function returning @code{void}.
29213 *stopped,reason="function-finished",frame=@{func="main",args=[],
29214 file="hello.c",fullname="/home/foo/bar/hello.c",line="7"@}
29218 Function returning other than @code{void}. The name of the internal
29219 @value{GDBN} variable storing the result is printed, together with the
29226 *stopped,reason="function-finished",frame=@{addr="0x000107b0",func="foo",
29227 args=[@{name="a",value="1"],@{name="b",value="9"@}@},
29228 file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@},
29229 gdb-result-var="$1",return-value="0"
29234 @subheading The @code{-exec-interrupt} Command
29235 @findex -exec-interrupt
29237 @subsubheading Synopsis
29240 -exec-interrupt [--all|--thread-group N]
29243 Interrupts the background execution of the target. Note how the token
29244 associated with the stop message is the one for the execution command
29245 that has been interrupted. The token for the interrupt itself only
29246 appears in the @samp{^done} output. If the user is trying to
29247 interrupt a non-running program, an error message will be printed.
29249 Note that when asynchronous execution is enabled, this command is
29250 asynchronous just like other execution commands. That is, first the
29251 @samp{^done} response will be printed, and the target stop will be
29252 reported after that using the @samp{*stopped} notification.
29254 In non-stop mode, only the context thread is interrupted by default.
29255 All threads (in all inferiors) will be interrupted if the
29256 @samp{--all} option is specified. If the @samp{--thread-group}
29257 option is specified, all threads in that group will be interrupted.
29259 @subsubheading @value{GDBN} Command
29261 The corresponding @value{GDBN} command is @samp{interrupt}.
29263 @subsubheading Example
29274 111*stopped,signal-name="SIGINT",signal-meaning="Interrupt",
29275 frame=@{addr="0x00010140",func="foo",args=[],file="try.c",
29276 fullname="/home/foo/bar/try.c",line="13"@}
29281 ^error,msg="mi_cmd_exec_interrupt: Inferior not executing."
29285 @subheading The @code{-exec-jump} Command
29288 @subsubheading Synopsis
29291 -exec-jump @var{location}
29294 Resumes execution of the inferior program at the location specified by
29295 parameter. @xref{Specify Location}, for a description of the
29296 different forms of @var{location}.
29298 @subsubheading @value{GDBN} Command
29300 The corresponding @value{GDBN} command is @samp{jump}.
29302 @subsubheading Example
29305 -exec-jump foo.c:10
29306 *running,thread-id="all"
29311 @subheading The @code{-exec-next} Command
29314 @subsubheading Synopsis
29317 -exec-next [--reverse]
29320 Resumes execution of the inferior program, stopping when the beginning
29321 of the next source line is reached.
29323 If the @samp{--reverse} option is specified, resumes reverse execution
29324 of the inferior program, stopping at the beginning of the previous
29325 source line. If you issue this command on the first line of a
29326 function, it will take you back to the caller of that function, to the
29327 source line where the function was called.
29330 @subsubheading @value{GDBN} Command
29332 The corresponding @value{GDBN} command is @samp{next}.
29334 @subsubheading Example
29340 *stopped,reason="end-stepping-range",line="8",file="hello.c"
29345 @subheading The @code{-exec-next-instruction} Command
29346 @findex -exec-next-instruction
29348 @subsubheading Synopsis
29351 -exec-next-instruction [--reverse]
29354 Executes one machine instruction. If the instruction is a function
29355 call, continues until the function returns. If the program stops at an
29356 instruction in the middle of a source line, the address will be
29359 If the @samp{--reverse} option is specified, resumes reverse execution
29360 of the inferior program, stopping at the previous instruction. If the
29361 previously executed instruction was a return from another function,
29362 it will continue to execute in reverse until the call to that function
29363 (from the current stack frame) is reached.
29365 @subsubheading @value{GDBN} Command
29367 The corresponding @value{GDBN} command is @samp{nexti}.
29369 @subsubheading Example
29373 -exec-next-instruction
29377 *stopped,reason="end-stepping-range",
29378 addr="0x000100d4",line="5",file="hello.c"
29383 @subheading The @code{-exec-return} Command
29384 @findex -exec-return
29386 @subsubheading Synopsis
29392 Makes current function return immediately. Doesn't execute the inferior.
29393 Displays the new current frame.
29395 @subsubheading @value{GDBN} Command
29397 The corresponding @value{GDBN} command is @samp{return}.
29399 @subsubheading Example
29403 200-break-insert callee4
29404 200^done,bkpt=@{number="1",addr="0x00010734",
29405 file="../../../devo/gdb/testsuite/gdb.mi/basics.c",line="8"@}
29410 000*stopped,reason="breakpoint-hit",disp="keep",bkptno="1",
29411 frame=@{func="callee4",args=[],
29412 file="../../../devo/gdb/testsuite/gdb.mi/basics.c",
29413 fullname="/home/foo/bar/devo/gdb/testsuite/gdb.mi/basics.c",line="8"@}
29419 111^done,frame=@{level="0",func="callee3",
29420 args=[@{name="strarg",
29421 value="0x11940 \"A string argument.\""@}],
29422 file="../../../devo/gdb/testsuite/gdb.mi/basics.c",
29423 fullname="/home/foo/bar/devo/gdb/testsuite/gdb.mi/basics.c",line="18"@}
29428 @subheading The @code{-exec-run} Command
29431 @subsubheading Synopsis
29434 -exec-run [ --all | --thread-group N ] [ --start ]
29437 Starts execution of the inferior from the beginning. The inferior
29438 executes until either a breakpoint is encountered or the program
29439 exits. In the latter case the output will include an exit code, if
29440 the program has exited exceptionally.
29442 When neither the @samp{--all} nor the @samp{--thread-group} option
29443 is specified, the current inferior is started. If the
29444 @samp{--thread-group} option is specified, it should refer to a thread
29445 group of type @samp{process}, and that thread group will be started.
29446 If the @samp{--all} option is specified, then all inferiors will be started.
29448 Using the @samp{--start} option instructs the debugger to stop
29449 the execution at the start of the inferior's main subprogram,
29450 following the same behavior as the @code{start} command
29451 (@pxref{Starting}).
29453 @subsubheading @value{GDBN} Command
29455 The corresponding @value{GDBN} command is @samp{run}.
29457 @subsubheading Examples
29462 ^done,bkpt=@{number="1",addr="0x0001072c",file="recursive2.c",line="4"@}
29467 *stopped,reason="breakpoint-hit",disp="keep",bkptno="1",
29468 frame=@{func="main",args=[],file="recursive2.c",
29469 fullname="/home/foo/bar/recursive2.c",line="4"@}
29474 Program exited normally:
29482 *stopped,reason="exited-normally"
29487 Program exited exceptionally:
29495 *stopped,reason="exited",exit-code="01"
29499 Another way the program can terminate is if it receives a signal such as
29500 @code{SIGINT}. In this case, @sc{gdb/mi} displays this:
29504 *stopped,reason="exited-signalled",signal-name="SIGINT",
29505 signal-meaning="Interrupt"
29509 @c @subheading -exec-signal
29512 @subheading The @code{-exec-step} Command
29515 @subsubheading Synopsis
29518 -exec-step [--reverse]
29521 Resumes execution of the inferior program, stopping when the beginning
29522 of the next source line is reached, if the next source line is not a
29523 function call. If it is, stop at the first instruction of the called
29524 function. If the @samp{--reverse} option is specified, resumes reverse
29525 execution of the inferior program, stopping at the beginning of the
29526 previously executed source line.
29528 @subsubheading @value{GDBN} Command
29530 The corresponding @value{GDBN} command is @samp{step}.
29532 @subsubheading Example
29534 Stepping into a function:
29540 *stopped,reason="end-stepping-range",
29541 frame=@{func="foo",args=[@{name="a",value="10"@},
29542 @{name="b",value="0"@}],file="recursive2.c",
29543 fullname="/home/foo/bar/recursive2.c",line="11"@}
29553 *stopped,reason="end-stepping-range",line="14",file="recursive2.c"
29558 @subheading The @code{-exec-step-instruction} Command
29559 @findex -exec-step-instruction
29561 @subsubheading Synopsis
29564 -exec-step-instruction [--reverse]
29567 Resumes the inferior which executes one machine instruction. If the
29568 @samp{--reverse} option is specified, resumes reverse execution of the
29569 inferior program, stopping at the previously executed instruction.
29570 The output, once @value{GDBN} has stopped, will vary depending on
29571 whether we have stopped in the middle of a source line or not. In the
29572 former case, the address at which the program stopped will be printed
29575 @subsubheading @value{GDBN} Command
29577 The corresponding @value{GDBN} command is @samp{stepi}.
29579 @subsubheading Example
29583 -exec-step-instruction
29587 *stopped,reason="end-stepping-range",
29588 frame=@{func="foo",args=[],file="try.c",
29589 fullname="/home/foo/bar/try.c",line="10"@}
29591 -exec-step-instruction
29595 *stopped,reason="end-stepping-range",
29596 frame=@{addr="0x000100f4",func="foo",args=[],file="try.c",
29597 fullname="/home/foo/bar/try.c",line="10"@}
29602 @subheading The @code{-exec-until} Command
29603 @findex -exec-until
29605 @subsubheading Synopsis
29608 -exec-until [ @var{location} ]
29611 Executes the inferior until the @var{location} specified in the
29612 argument is reached. If there is no argument, the inferior executes
29613 until a source line greater than the current one is reached. The
29614 reason for stopping in this case will be @samp{location-reached}.
29616 @subsubheading @value{GDBN} Command
29618 The corresponding @value{GDBN} command is @samp{until}.
29620 @subsubheading Example
29624 -exec-until recursive2.c:6
29628 *stopped,reason="location-reached",frame=@{func="main",args=[],
29629 file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="6"@}
29634 @subheading -file-clear
29635 Is this going away????
29638 @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
29639 @node GDB/MI Stack Manipulation
29640 @section @sc{gdb/mi} Stack Manipulation Commands
29642 @subheading The @code{-enable-frame-filters} Command
29643 @findex -enable-frame-filters
29646 -enable-frame-filters
29649 @value{GDBN} allows Python-based frame filters to affect the output of
29650 the MI commands relating to stack traces. As there is no way to
29651 implement this in a fully backward-compatible way, a front end must
29652 request that this functionality be enabled.
29654 Once enabled, this feature cannot be disabled.
29656 Note that if Python support has not been compiled into @value{GDBN},
29657 this command will still succeed (and do nothing).
29659 @subheading The @code{-stack-info-frame} Command
29660 @findex -stack-info-frame
29662 @subsubheading Synopsis
29668 Get info on the selected frame.
29670 @subsubheading @value{GDBN} Command
29672 The corresponding @value{GDBN} command is @samp{info frame} or @samp{frame}
29673 (without arguments).
29675 @subsubheading Example
29680 ^done,frame=@{level="1",addr="0x0001076c",func="callee3",
29681 file="../../../devo/gdb/testsuite/gdb.mi/basics.c",
29682 fullname="/home/foo/bar/devo/gdb/testsuite/gdb.mi/basics.c",line="17"@}
29686 @subheading The @code{-stack-info-depth} Command
29687 @findex -stack-info-depth
29689 @subsubheading Synopsis
29692 -stack-info-depth [ @var{max-depth} ]
29695 Return the depth of the stack. If the integer argument @var{max-depth}
29696 is specified, do not count beyond @var{max-depth} frames.
29698 @subsubheading @value{GDBN} Command
29700 There's no equivalent @value{GDBN} command.
29702 @subsubheading Example
29704 For a stack with frame levels 0 through 11:
29711 -stack-info-depth 4
29714 -stack-info-depth 12
29717 -stack-info-depth 11
29720 -stack-info-depth 13
29725 @anchor{-stack-list-arguments}
29726 @subheading The @code{-stack-list-arguments} Command
29727 @findex -stack-list-arguments
29729 @subsubheading Synopsis
29732 -stack-list-arguments [ --no-frame-filters ] [ --skip-unavailable ] @var{print-values}
29733 [ @var{low-frame} @var{high-frame} ]
29736 Display a list of the arguments for the frames between @var{low-frame}
29737 and @var{high-frame} (inclusive). If @var{low-frame} and
29738 @var{high-frame} are not provided, list the arguments for the whole
29739 call stack. If the two arguments are equal, show the single frame
29740 at the corresponding level. It is an error if @var{low-frame} is
29741 larger than the actual number of frames. On the other hand,
29742 @var{high-frame} may be larger than the actual number of frames, in
29743 which case only existing frames will be returned.
29745 If @var{print-values} is 0 or @code{--no-values}, print only the names of
29746 the variables; if it is 1 or @code{--all-values}, print also their
29747 values; and if it is 2 or @code{--simple-values}, print the name,
29748 type and value for simple data types, and the name and type for arrays,
29749 structures and unions. If the option @code{--no-frame-filters} is
29750 supplied, then Python frame filters will not be executed.
29752 If the @code{--skip-unavailable} option is specified, arguments that
29753 are not available are not listed. Partially available arguments
29754 are still displayed, however.
29756 Use of this command to obtain arguments in a single frame is
29757 deprecated in favor of the @samp{-stack-list-variables} command.
29759 @subsubheading @value{GDBN} Command
29761 @value{GDBN} does not have an equivalent command. @code{gdbtk} has a
29762 @samp{gdb_get_args} command which partially overlaps with the
29763 functionality of @samp{-stack-list-arguments}.
29765 @subsubheading Example
29772 frame=@{level="0",addr="0x00010734",func="callee4",
29773 file="../../../devo/gdb/testsuite/gdb.mi/basics.c",
29774 fullname="/home/foo/bar/devo/gdb/testsuite/gdb.mi/basics.c",line="8"@},
29775 frame=@{level="1",addr="0x0001076c",func="callee3",
29776 file="../../../devo/gdb/testsuite/gdb.mi/basics.c",
29777 fullname="/home/foo/bar/devo/gdb/testsuite/gdb.mi/basics.c",line="17"@},
29778 frame=@{level="2",addr="0x0001078c",func="callee2",
29779 file="../../../devo/gdb/testsuite/gdb.mi/basics.c",
29780 fullname="/home/foo/bar/devo/gdb/testsuite/gdb.mi/basics.c",line="22"@},
29781 frame=@{level="3",addr="0x000107b4",func="callee1",
29782 file="../../../devo/gdb/testsuite/gdb.mi/basics.c",
29783 fullname="/home/foo/bar/devo/gdb/testsuite/gdb.mi/basics.c",line="27"@},
29784 frame=@{level="4",addr="0x000107e0",func="main",
29785 file="../../../devo/gdb/testsuite/gdb.mi/basics.c",
29786 fullname="/home/foo/bar/devo/gdb/testsuite/gdb.mi/basics.c",line="32"@}]
29788 -stack-list-arguments 0
29791 frame=@{level="0",args=[]@},
29792 frame=@{level="1",args=[name="strarg"]@},
29793 frame=@{level="2",args=[name="intarg",name="strarg"]@},
29794 frame=@{level="3",args=[name="intarg",name="strarg",name="fltarg"]@},
29795 frame=@{level="4",args=[]@}]
29797 -stack-list-arguments 1
29800 frame=@{level="0",args=[]@},
29802 args=[@{name="strarg",value="0x11940 \"A string argument.\""@}]@},
29803 frame=@{level="2",args=[
29804 @{name="intarg",value="2"@},
29805 @{name="strarg",value="0x11940 \"A string argument.\""@}]@},
29806 @{frame=@{level="3",args=[
29807 @{name="intarg",value="2"@},
29808 @{name="strarg",value="0x11940 \"A string argument.\""@},
29809 @{name="fltarg",value="3.5"@}]@},
29810 frame=@{level="4",args=[]@}]
29812 -stack-list-arguments 0 2 2
29813 ^done,stack-args=[frame=@{level="2",args=[name="intarg",name="strarg"]@}]
29815 -stack-list-arguments 1 2 2
29816 ^done,stack-args=[frame=@{level="2",
29817 args=[@{name="intarg",value="2"@},
29818 @{name="strarg",value="0x11940 \"A string argument.\""@}]@}]
29822 @c @subheading -stack-list-exception-handlers
29825 @anchor{-stack-list-frames}
29826 @subheading The @code{-stack-list-frames} Command
29827 @findex -stack-list-frames
29829 @subsubheading Synopsis
29832 -stack-list-frames [ --no-frame-filters @var{low-frame} @var{high-frame} ]
29835 List the frames currently on the stack. For each frame it displays the
29840 The frame number, 0 being the topmost frame, i.e., the innermost function.
29842 The @code{$pc} value for that frame.
29846 File name of the source file where the function lives.
29847 @item @var{fullname}
29848 The full file name of the source file where the function lives.
29850 Line number corresponding to the @code{$pc}.
29852 The shared library where this function is defined. This is only given
29853 if the frame's function is not known.
29856 If invoked without arguments, this command prints a backtrace for the
29857 whole stack. If given two integer arguments, it shows the frames whose
29858 levels are between the two arguments (inclusive). If the two arguments
29859 are equal, it shows the single frame at the corresponding level. It is
29860 an error if @var{low-frame} is larger than the actual number of
29861 frames. On the other hand, @var{high-frame} may be larger than the
29862 actual number of frames, in which case only existing frames will be
29863 returned. If the option @code{--no-frame-filters} is supplied, then
29864 Python frame filters will not be executed.
29866 @subsubheading @value{GDBN} Command
29868 The corresponding @value{GDBN} commands are @samp{backtrace} and @samp{where}.
29870 @subsubheading Example
29872 Full stack backtrace:
29878 [frame=@{level="0",addr="0x0001076c",func="foo",
29879 file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="11"@},
29880 frame=@{level="1",addr="0x000107a4",func="foo",
29881 file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@},
29882 frame=@{level="2",addr="0x000107a4",func="foo",
29883 file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@},
29884 frame=@{level="3",addr="0x000107a4",func="foo",
29885 file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@},
29886 frame=@{level="4",addr="0x000107a4",func="foo",
29887 file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@},
29888 frame=@{level="5",addr="0x000107a4",func="foo",
29889 file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@},
29890 frame=@{level="6",addr="0x000107a4",func="foo",
29891 file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@},
29892 frame=@{level="7",addr="0x000107a4",func="foo",
29893 file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@},
29894 frame=@{level="8",addr="0x000107a4",func="foo",
29895 file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@},
29896 frame=@{level="9",addr="0x000107a4",func="foo",
29897 file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@},
29898 frame=@{level="10",addr="0x000107a4",func="foo",
29899 file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@},
29900 frame=@{level="11",addr="0x00010738",func="main",
29901 file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="4"@}]
29905 Show frames between @var{low_frame} and @var{high_frame}:
29909 -stack-list-frames 3 5
29911 [frame=@{level="3",addr="0x000107a4",func="foo",
29912 file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@},
29913 frame=@{level="4",addr="0x000107a4",func="foo",
29914 file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@},
29915 frame=@{level="5",addr="0x000107a4",func="foo",
29916 file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@}]
29920 Show a single frame:
29924 -stack-list-frames 3 3
29926 [frame=@{level="3",addr="0x000107a4",func="foo",
29927 file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@}]
29932 @subheading The @code{-stack-list-locals} Command
29933 @findex -stack-list-locals
29934 @anchor{-stack-list-locals}
29936 @subsubheading Synopsis
29939 -stack-list-locals [ --no-frame-filters ] [ --skip-unavailable ] @var{print-values}
29942 Display the local variable names for the selected frame. If
29943 @var{print-values} is 0 or @code{--no-values}, print only the names of
29944 the variables; if it is 1 or @code{--all-values}, print also their
29945 values; and if it is 2 or @code{--simple-values}, print the name,
29946 type and value for simple data types, and the name and type for arrays,
29947 structures and unions. In this last case, a frontend can immediately
29948 display the value of simple data types and create variable objects for
29949 other data types when the user wishes to explore their values in
29950 more detail. If the option @code{--no-frame-filters} is supplied, then
29951 Python frame filters will not be executed.
29953 If the @code{--skip-unavailable} option is specified, local variables
29954 that are not available are not listed. Partially available local
29955 variables are still displayed, however.
29957 This command is deprecated in favor of the
29958 @samp{-stack-list-variables} command.
29960 @subsubheading @value{GDBN} Command
29962 @samp{info locals} in @value{GDBN}, @samp{gdb_get_locals} in @code{gdbtk}.
29964 @subsubheading Example
29968 -stack-list-locals 0
29969 ^done,locals=[name="A",name="B",name="C"]
29971 -stack-list-locals --all-values
29972 ^done,locals=[@{name="A",value="1"@},@{name="B",value="2"@},
29973 @{name="C",value="@{1, 2, 3@}"@}]
29974 -stack-list-locals --simple-values
29975 ^done,locals=[@{name="A",type="int",value="1"@},
29976 @{name="B",type="int",value="2"@},@{name="C",type="int [3]"@}]
29980 @anchor{-stack-list-variables}
29981 @subheading The @code{-stack-list-variables} Command
29982 @findex -stack-list-variables
29984 @subsubheading Synopsis
29987 -stack-list-variables [ --no-frame-filters ] [ --skip-unavailable ] @var{print-values}
29990 Display the names of local variables and function arguments for the selected frame. If
29991 @var{print-values} is 0 or @code{--no-values}, print only the names of
29992 the variables; if it is 1 or @code{--all-values}, print also their
29993 values; and if it is 2 or @code{--simple-values}, print the name,
29994 type and value for simple data types, and the name and type for arrays,
29995 structures and unions. If the option @code{--no-frame-filters} is
29996 supplied, then Python frame filters will not be executed.
29998 If the @code{--skip-unavailable} option is specified, local variables
29999 and arguments that are not available are not listed. Partially
30000 available arguments and local variables are still displayed, however.
30002 @subsubheading Example
30006 -stack-list-variables --thread 1 --frame 0 --all-values
30007 ^done,variables=[@{name="x",value="11"@},@{name="s",value="@{a = 1, b = 2@}"@}]
30012 @subheading The @code{-stack-select-frame} Command
30013 @findex -stack-select-frame
30015 @subsubheading Synopsis
30018 -stack-select-frame @var{framenum}
30021 Change the selected frame. Select a different frame @var{framenum} on
30024 This command in deprecated in favor of passing the @samp{--frame}
30025 option to every command.
30027 @subsubheading @value{GDBN} Command
30029 The corresponding @value{GDBN} commands are @samp{frame}, @samp{up},
30030 @samp{down}, @samp{select-frame}, @samp{up-silent}, and @samp{down-silent}.
30032 @subsubheading Example
30036 -stack-select-frame 2
30041 @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
30042 @node GDB/MI Variable Objects
30043 @section @sc{gdb/mi} Variable Objects
30047 @subheading Motivation for Variable Objects in @sc{gdb/mi}
30049 For the implementation of a variable debugger window (locals, watched
30050 expressions, etc.), we are proposing the adaptation of the existing code
30051 used by @code{Insight}.
30053 The two main reasons for that are:
30057 It has been proven in practice (it is already on its second generation).
30060 It will shorten development time (needless to say how important it is
30064 The original interface was designed to be used by Tcl code, so it was
30065 slightly changed so it could be used through @sc{gdb/mi}. This section
30066 describes the @sc{gdb/mi} operations that will be available and gives some
30067 hints about their use.
30069 @emph{Note}: In addition to the set of operations described here, we
30070 expect the @sc{gui} implementation of a variable window to require, at
30071 least, the following operations:
30074 @item @code{-gdb-show} @code{output-radix}
30075 @item @code{-stack-list-arguments}
30076 @item @code{-stack-list-locals}
30077 @item @code{-stack-select-frame}
30082 @subheading Introduction to Variable Objects
30084 @cindex variable objects in @sc{gdb/mi}
30086 Variable objects are "object-oriented" MI interface for examining and
30087 changing values of expressions. Unlike some other MI interfaces that
30088 work with expressions, variable objects are specifically designed for
30089 simple and efficient presentation in the frontend. A variable object
30090 is identified by string name. When a variable object is created, the
30091 frontend specifies the expression for that variable object. The
30092 expression can be a simple variable, or it can be an arbitrary complex
30093 expression, and can even involve CPU registers. After creating a
30094 variable object, the frontend can invoke other variable object
30095 operations---for example to obtain or change the value of a variable
30096 object, or to change display format.
30098 Variable objects have hierarchical tree structure. Any variable object
30099 that corresponds to a composite type, such as structure in C, has
30100 a number of child variable objects, for example corresponding to each
30101 element of a structure. A child variable object can itself have
30102 children, recursively. Recursion ends when we reach
30103 leaf variable objects, which always have built-in types. Child variable
30104 objects are created only by explicit request, so if a frontend
30105 is not interested in the children of a particular variable object, no
30106 child will be created.
30108 For a leaf variable object it is possible to obtain its value as a
30109 string, or set the value from a string. String value can be also
30110 obtained for a non-leaf variable object, but it's generally a string
30111 that only indicates the type of the object, and does not list its
30112 contents. Assignment to a non-leaf variable object is not allowed.
30114 A frontend does not need to read the values of all variable objects each time
30115 the program stops. Instead, MI provides an update command that lists all
30116 variable objects whose values has changed since the last update
30117 operation. This considerably reduces the amount of data that must
30118 be transferred to the frontend. As noted above, children variable
30119 objects are created on demand, and only leaf variable objects have a
30120 real value. As result, gdb will read target memory only for leaf
30121 variables that frontend has created.
30123 The automatic update is not always desirable. For example, a frontend
30124 might want to keep a value of some expression for future reference,
30125 and never update it. For another example, fetching memory is
30126 relatively slow for embedded targets, so a frontend might want
30127 to disable automatic update for the variables that are either not
30128 visible on the screen, or ``closed''. This is possible using so
30129 called ``frozen variable objects''. Such variable objects are never
30130 implicitly updated.
30132 Variable objects can be either @dfn{fixed} or @dfn{floating}. For the
30133 fixed variable object, the expression is parsed when the variable
30134 object is created, including associating identifiers to specific
30135 variables. The meaning of expression never changes. For a floating
30136 variable object the values of variables whose names appear in the
30137 expressions are re-evaluated every time in the context of the current
30138 frame. Consider this example:
30143 struct work_state state;
30150 If a fixed variable object for the @code{state} variable is created in
30151 this function, and we enter the recursive call, the variable
30152 object will report the value of @code{state} in the top-level
30153 @code{do_work} invocation. On the other hand, a floating variable
30154 object will report the value of @code{state} in the current frame.
30156 If an expression specified when creating a fixed variable object
30157 refers to a local variable, the variable object becomes bound to the
30158 thread and frame in which the variable object is created. When such
30159 variable object is updated, @value{GDBN} makes sure that the
30160 thread/frame combination the variable object is bound to still exists,
30161 and re-evaluates the variable object in context of that thread/frame.
30163 The following is the complete set of @sc{gdb/mi} operations defined to
30164 access this functionality:
30166 @multitable @columnfractions .4 .6
30167 @item @strong{Operation}
30168 @tab @strong{Description}
30170 @item @code{-enable-pretty-printing}
30171 @tab enable Python-based pretty-printing
30172 @item @code{-var-create}
30173 @tab create a variable object
30174 @item @code{-var-delete}
30175 @tab delete the variable object and/or its children
30176 @item @code{-var-set-format}
30177 @tab set the display format of this variable
30178 @item @code{-var-show-format}
30179 @tab show the display format of this variable
30180 @item @code{-var-info-num-children}
30181 @tab tells how many children this object has
30182 @item @code{-var-list-children}
30183 @tab return a list of the object's children
30184 @item @code{-var-info-type}
30185 @tab show the type of this variable object
30186 @item @code{-var-info-expression}
30187 @tab print parent-relative expression that this variable object represents
30188 @item @code{-var-info-path-expression}
30189 @tab print full expression that this variable object represents
30190 @item @code{-var-show-attributes}
30191 @tab is this variable editable? does it exist here?
30192 @item @code{-var-evaluate-expression}
30193 @tab get the value of this variable
30194 @item @code{-var-assign}
30195 @tab set the value of this variable
30196 @item @code{-var-update}
30197 @tab update the variable and its children
30198 @item @code{-var-set-frozen}
30199 @tab set frozeness attribute
30200 @item @code{-var-set-update-range}
30201 @tab set range of children to display on update
30204 In the next subsection we describe each operation in detail and suggest
30205 how it can be used.
30207 @subheading Description And Use of Operations on Variable Objects
30209 @subheading The @code{-enable-pretty-printing} Command
30210 @findex -enable-pretty-printing
30213 -enable-pretty-printing
30216 @value{GDBN} allows Python-based visualizers to affect the output of the
30217 MI variable object commands. However, because there was no way to
30218 implement this in a fully backward-compatible way, a front end must
30219 request that this functionality be enabled.
30221 Once enabled, this feature cannot be disabled.
30223 Note that if Python support has not been compiled into @value{GDBN},
30224 this command will still succeed (and do nothing).
30226 This feature is currently (as of @value{GDBN} 7.0) experimental, and
30227 may work differently in future versions of @value{GDBN}.
30229 @subheading The @code{-var-create} Command
30230 @findex -var-create
30232 @subsubheading Synopsis
30235 -var-create @{@var{name} | "-"@}
30236 @{@var{frame-addr} | "*" | "@@"@} @var{expression}
30239 This operation creates a variable object, which allows the monitoring of
30240 a variable, the result of an expression, a memory cell or a CPU
30243 The @var{name} parameter is the string by which the object can be
30244 referenced. It must be unique. If @samp{-} is specified, the varobj
30245 system will generate a string ``varNNNNNN'' automatically. It will be
30246 unique provided that one does not specify @var{name} of that format.
30247 The command fails if a duplicate name is found.
30249 The frame under which the expression should be evaluated can be
30250 specified by @var{frame-addr}. A @samp{*} indicates that the current
30251 frame should be used. A @samp{@@} indicates that a floating variable
30252 object must be created.
30254 @var{expression} is any expression valid on the current language set (must not
30255 begin with a @samp{*}), or one of the following:
30259 @samp{*@var{addr}}, where @var{addr} is the address of a memory cell
30262 @samp{*@var{addr}-@var{addr}} --- a memory address range (TBD)
30265 @samp{$@var{regname}} --- a CPU register name
30268 @cindex dynamic varobj
30269 A varobj's contents may be provided by a Python-based pretty-printer. In this
30270 case the varobj is known as a @dfn{dynamic varobj}. Dynamic varobjs
30271 have slightly different semantics in some cases. If the
30272 @code{-enable-pretty-printing} command is not sent, then @value{GDBN}
30273 will never create a dynamic varobj. This ensures backward
30274 compatibility for existing clients.
30276 @subsubheading Result
30278 This operation returns attributes of the newly-created varobj. These
30283 The name of the varobj.
30286 The number of children of the varobj. This number is not necessarily
30287 reliable for a dynamic varobj. Instead, you must examine the
30288 @samp{has_more} attribute.
30291 The varobj's scalar value. For a varobj whose type is some sort of
30292 aggregate (e.g., a @code{struct}), or for a dynamic varobj, this value
30293 will not be interesting.
30296 The varobj's type. This is a string representation of the type, as
30297 would be printed by the @value{GDBN} CLI. If @samp{print object}
30298 (@pxref{Print Settings, set print object}) is set to @code{on}, the
30299 @emph{actual} (derived) type of the object is shown rather than the
30300 @emph{declared} one.
30303 If a variable object is bound to a specific thread, then this is the
30304 thread's global identifier.
30307 For a dynamic varobj, this indicates whether there appear to be any
30308 children available. For a non-dynamic varobj, this will be 0.
30311 This attribute will be present and have the value @samp{1} if the
30312 varobj is a dynamic varobj. If the varobj is not a dynamic varobj,
30313 then this attribute will not be present.
30316 A dynamic varobj can supply a display hint to the front end. The
30317 value comes directly from the Python pretty-printer object's
30318 @code{display_hint} method. @xref{Pretty Printing API}.
30321 Typical output will look like this:
30324 name="@var{name}",numchild="@var{N}",type="@var{type}",thread-id="@var{M}",
30325 has_more="@var{has_more}"
30329 @subheading The @code{-var-delete} Command
30330 @findex -var-delete
30332 @subsubheading Synopsis
30335 -var-delete [ -c ] @var{name}
30338 Deletes a previously created variable object and all of its children.
30339 With the @samp{-c} option, just deletes the children.
30341 Returns an error if the object @var{name} is not found.
30344 @subheading The @code{-var-set-format} Command
30345 @findex -var-set-format
30347 @subsubheading Synopsis
30350 -var-set-format @var{name} @var{format-spec}
30353 Sets the output format for the value of the object @var{name} to be
30356 @anchor{-var-set-format}
30357 The syntax for the @var{format-spec} is as follows:
30360 @var{format-spec} @expansion{}
30361 @{binary | decimal | hexadecimal | octal | natural | zero-hexadecimal@}
30364 The natural format is the default format choosen automatically
30365 based on the variable type (like decimal for an @code{int}, hex
30366 for pointers, etc.).
30368 The zero-hexadecimal format has a representation similar to hexadecimal
30369 but with padding zeroes to the left of the value. For example, a 32-bit
30370 hexadecimal value of 0x1234 would be represented as 0x00001234 in the
30371 zero-hexadecimal format.
30373 For a variable with children, the format is set only on the
30374 variable itself, and the children are not affected.
30376 @subheading The @code{-var-show-format} Command
30377 @findex -var-show-format
30379 @subsubheading Synopsis
30382 -var-show-format @var{name}
30385 Returns the format used to display the value of the object @var{name}.
30388 @var{format} @expansion{}
30393 @subheading The @code{-var-info-num-children} Command
30394 @findex -var-info-num-children
30396 @subsubheading Synopsis
30399 -var-info-num-children @var{name}
30402 Returns the number of children of a variable object @var{name}:
30408 Note that this number is not completely reliable for a dynamic varobj.
30409 It will return the current number of children, but more children may
30413 @subheading The @code{-var-list-children} Command
30414 @findex -var-list-children
30416 @subsubheading Synopsis
30419 -var-list-children [@var{print-values}] @var{name} [@var{from} @var{to}]
30421 @anchor{-var-list-children}
30423 Return a list of the children of the specified variable object and
30424 create variable objects for them, if they do not already exist. With
30425 a single argument or if @var{print-values} has a value of 0 or
30426 @code{--no-values}, print only the names of the variables; if
30427 @var{print-values} is 1 or @code{--all-values}, also print their
30428 values; and if it is 2 or @code{--simple-values} print the name and
30429 value for simple data types and just the name for arrays, structures
30432 @var{from} and @var{to}, if specified, indicate the range of children
30433 to report. If @var{from} or @var{to} is less than zero, the range is
30434 reset and all children will be reported. Otherwise, children starting
30435 at @var{from} (zero-based) and up to and excluding @var{to} will be
30438 If a child range is requested, it will only affect the current call to
30439 @code{-var-list-children}, but not future calls to @code{-var-update}.
30440 For this, you must instead use @code{-var-set-update-range}. The
30441 intent of this approach is to enable a front end to implement any
30442 update approach it likes; for example, scrolling a view may cause the
30443 front end to request more children with @code{-var-list-children}, and
30444 then the front end could call @code{-var-set-update-range} with a
30445 different range to ensure that future updates are restricted to just
30448 For each child the following results are returned:
30453 Name of the variable object created for this child.
30456 The expression to be shown to the user by the front end to designate this child.
30457 For example this may be the name of a structure member.
30459 For a dynamic varobj, this value cannot be used to form an
30460 expression. There is no way to do this at all with a dynamic varobj.
30462 For C/C@t{++} structures there are several pseudo children returned to
30463 designate access qualifiers. For these pseudo children @var{exp} is
30464 @samp{public}, @samp{private}, or @samp{protected}. In this case the
30465 type and value are not present.
30467 A dynamic varobj will not report the access qualifying
30468 pseudo-children, regardless of the language. This information is not
30469 available at all with a dynamic varobj.
30472 Number of children this child has. For a dynamic varobj, this will be
30476 The type of the child. If @samp{print object}
30477 (@pxref{Print Settings, set print object}) is set to @code{on}, the
30478 @emph{actual} (derived) type of the object is shown rather than the
30479 @emph{declared} one.
30482 If values were requested, this is the value.
30485 If this variable object is associated with a thread, this is the
30486 thread's global thread id. Otherwise this result is not present.
30489 If the variable object is frozen, this variable will be present with a value of 1.
30492 A dynamic varobj can supply a display hint to the front end. The
30493 value comes directly from the Python pretty-printer object's
30494 @code{display_hint} method. @xref{Pretty Printing API}.
30497 This attribute will be present and have the value @samp{1} if the
30498 varobj is a dynamic varobj. If the varobj is not a dynamic varobj,
30499 then this attribute will not be present.
30503 The result may have its own attributes:
30507 A dynamic varobj can supply a display hint to the front end. The
30508 value comes directly from the Python pretty-printer object's
30509 @code{display_hint} method. @xref{Pretty Printing API}.
30512 This is an integer attribute which is nonzero if there are children
30513 remaining after the end of the selected range.
30516 @subsubheading Example
30520 -var-list-children n
30521 ^done,numchild=@var{n},children=[child=@{name=@var{name},exp=@var{exp},
30522 numchild=@var{n},type=@var{type}@},@r{(repeats N times)}]
30524 -var-list-children --all-values n
30525 ^done,numchild=@var{n},children=[child=@{name=@var{name},exp=@var{exp},
30526 numchild=@var{n},value=@var{value},type=@var{type}@},@r{(repeats N times)}]
30530 @subheading The @code{-var-info-type} Command
30531 @findex -var-info-type
30533 @subsubheading Synopsis
30536 -var-info-type @var{name}
30539 Returns the type of the specified variable @var{name}. The type is
30540 returned as a string in the same format as it is output by the
30544 type=@var{typename}
30548 @subheading The @code{-var-info-expression} Command
30549 @findex -var-info-expression
30551 @subsubheading Synopsis
30554 -var-info-expression @var{name}
30557 Returns a string that is suitable for presenting this
30558 variable object in user interface. The string is generally
30559 not valid expression in the current language, and cannot be evaluated.
30561 For example, if @code{a} is an array, and variable object
30562 @code{A} was created for @code{a}, then we'll get this output:
30565 (gdb) -var-info-expression A.1
30566 ^done,lang="C",exp="1"
30570 Here, the value of @code{lang} is the language name, which can be
30571 found in @ref{Supported Languages}.
30573 Note that the output of the @code{-var-list-children} command also
30574 includes those expressions, so the @code{-var-info-expression} command
30577 @subheading The @code{-var-info-path-expression} Command
30578 @findex -var-info-path-expression
30580 @subsubheading Synopsis
30583 -var-info-path-expression @var{name}
30586 Returns an expression that can be evaluated in the current
30587 context and will yield the same value that a variable object has.
30588 Compare this with the @code{-var-info-expression} command, which
30589 result can be used only for UI presentation. Typical use of
30590 the @code{-var-info-path-expression} command is creating a
30591 watchpoint from a variable object.
30593 This command is currently not valid for children of a dynamic varobj,
30594 and will give an error when invoked on one.
30596 For example, suppose @code{C} is a C@t{++} class, derived from class
30597 @code{Base}, and that the @code{Base} class has a member called
30598 @code{m_size}. Assume a variable @code{c} is has the type of
30599 @code{C} and a variable object @code{C} was created for variable
30600 @code{c}. Then, we'll get this output:
30602 (gdb) -var-info-path-expression C.Base.public.m_size
30603 ^done,path_expr=((Base)c).m_size)
30606 @subheading The @code{-var-show-attributes} Command
30607 @findex -var-show-attributes
30609 @subsubheading Synopsis
30612 -var-show-attributes @var{name}
30615 List attributes of the specified variable object @var{name}:
30618 status=@var{attr} [ ( ,@var{attr} )* ]
30622 where @var{attr} is @code{@{ @{ editable | noneditable @} | TBD @}}.
30624 @subheading The @code{-var-evaluate-expression} Command
30625 @findex -var-evaluate-expression
30627 @subsubheading Synopsis
30630 -var-evaluate-expression [-f @var{format-spec}] @var{name}
30633 Evaluates the expression that is represented by the specified variable
30634 object and returns its value as a string. The format of the string
30635 can be specified with the @samp{-f} option. The possible values of
30636 this option are the same as for @code{-var-set-format}
30637 (@pxref{-var-set-format}). If the @samp{-f} option is not specified,
30638 the current display format will be used. The current display format
30639 can be changed using the @code{-var-set-format} command.
30645 Note that one must invoke @code{-var-list-children} for a variable
30646 before the value of a child variable can be evaluated.
30648 @subheading The @code{-var-assign} Command
30649 @findex -var-assign
30651 @subsubheading Synopsis
30654 -var-assign @var{name} @var{expression}
30657 Assigns the value of @var{expression} to the variable object specified
30658 by @var{name}. The object must be @samp{editable}. If the variable's
30659 value is altered by the assign, the variable will show up in any
30660 subsequent @code{-var-update} list.
30662 @subsubheading Example
30670 ^done,changelist=[@{name="var1",in_scope="true",type_changed="false"@}]
30674 @subheading The @code{-var-update} Command
30675 @findex -var-update
30677 @subsubheading Synopsis
30680 -var-update [@var{print-values}] @{@var{name} | "*"@}
30683 Reevaluate the expressions corresponding to the variable object
30684 @var{name} and all its direct and indirect children, and return the
30685 list of variable objects whose values have changed; @var{name} must
30686 be a root variable object. Here, ``changed'' means that the result of
30687 @code{-var-evaluate-expression} before and after the
30688 @code{-var-update} is different. If @samp{*} is used as the variable
30689 object names, all existing variable objects are updated, except
30690 for frozen ones (@pxref{-var-set-frozen}). The option
30691 @var{print-values} determines whether both names and values, or just
30692 names are printed. The possible values of this option are the same
30693 as for @code{-var-list-children} (@pxref{-var-list-children}). It is
30694 recommended to use the @samp{--all-values} option, to reduce the
30695 number of MI commands needed on each program stop.
30697 With the @samp{*} parameter, if a variable object is bound to a
30698 currently running thread, it will not be updated, without any
30701 If @code{-var-set-update-range} was previously used on a varobj, then
30702 only the selected range of children will be reported.
30704 @code{-var-update} reports all the changed varobjs in a tuple named
30707 Each item in the change list is itself a tuple holding:
30711 The name of the varobj.
30714 If values were requested for this update, then this field will be
30715 present and will hold the value of the varobj.
30718 @anchor{-var-update}
30719 This field is a string which may take one of three values:
30723 The variable object's current value is valid.
30726 The variable object does not currently hold a valid value but it may
30727 hold one in the future if its associated expression comes back into
30731 The variable object no longer holds a valid value.
30732 This can occur when the executable file being debugged has changed,
30733 either through recompilation or by using the @value{GDBN} @code{file}
30734 command. The front end should normally choose to delete these variable
30738 In the future new values may be added to this list so the front should
30739 be prepared for this possibility. @xref{GDB/MI Development and Front Ends, ,@sc{GDB/MI} Development and Front Ends}.
30742 This is only present if the varobj is still valid. If the type
30743 changed, then this will be the string @samp{true}; otherwise it will
30746 When a varobj's type changes, its children are also likely to have
30747 become incorrect. Therefore, the varobj's children are automatically
30748 deleted when this attribute is @samp{true}. Also, the varobj's update
30749 range, when set using the @code{-var-set-update-range} command, is
30753 If the varobj's type changed, then this field will be present and will
30756 @item new_num_children
30757 For a dynamic varobj, if the number of children changed, or if the
30758 type changed, this will be the new number of children.
30760 The @samp{numchild} field in other varobj responses is generally not
30761 valid for a dynamic varobj -- it will show the number of children that
30762 @value{GDBN} knows about, but because dynamic varobjs lazily
30763 instantiate their children, this will not reflect the number of
30764 children which may be available.
30766 The @samp{new_num_children} attribute only reports changes to the
30767 number of children known by @value{GDBN}. This is the only way to
30768 detect whether an update has removed children (which necessarily can
30769 only happen at the end of the update range).
30772 The display hint, if any.
30775 This is an integer value, which will be 1 if there are more children
30776 available outside the varobj's update range.
30779 This attribute will be present and have the value @samp{1} if the
30780 varobj is a dynamic varobj. If the varobj is not a dynamic varobj,
30781 then this attribute will not be present.
30784 If new children were added to a dynamic varobj within the selected
30785 update range (as set by @code{-var-set-update-range}), then they will
30786 be listed in this attribute.
30789 @subsubheading Example
30796 -var-update --all-values var1
30797 ^done,changelist=[@{name="var1",value="3",in_scope="true",
30798 type_changed="false"@}]
30802 @subheading The @code{-var-set-frozen} Command
30803 @findex -var-set-frozen
30804 @anchor{-var-set-frozen}
30806 @subsubheading Synopsis
30809 -var-set-frozen @var{name} @var{flag}
30812 Set the frozenness flag on the variable object @var{name}. The
30813 @var{flag} parameter should be either @samp{1} to make the variable
30814 frozen or @samp{0} to make it unfrozen. If a variable object is
30815 frozen, then neither itself, nor any of its children, are
30816 implicitly updated by @code{-var-update} of
30817 a parent variable or by @code{-var-update *}. Only
30818 @code{-var-update} of the variable itself will update its value and
30819 values of its children. After a variable object is unfrozen, it is
30820 implicitly updated by all subsequent @code{-var-update} operations.
30821 Unfreezing a variable does not update it, only subsequent
30822 @code{-var-update} does.
30824 @subsubheading Example
30828 -var-set-frozen V 1
30833 @subheading The @code{-var-set-update-range} command
30834 @findex -var-set-update-range
30835 @anchor{-var-set-update-range}
30837 @subsubheading Synopsis
30840 -var-set-update-range @var{name} @var{from} @var{to}
30843 Set the range of children to be returned by future invocations of
30844 @code{-var-update}.
30846 @var{from} and @var{to} indicate the range of children to report. If
30847 @var{from} or @var{to} is less than zero, the range is reset and all
30848 children will be reported. Otherwise, children starting at @var{from}
30849 (zero-based) and up to and excluding @var{to} will be reported.
30851 @subsubheading Example
30855 -var-set-update-range V 1 2
30859 @subheading The @code{-var-set-visualizer} command
30860 @findex -var-set-visualizer
30861 @anchor{-var-set-visualizer}
30863 @subsubheading Synopsis
30866 -var-set-visualizer @var{name} @var{visualizer}
30869 Set a visualizer for the variable object @var{name}.
30871 @var{visualizer} is the visualizer to use. The special value
30872 @samp{None} means to disable any visualizer in use.
30874 If not @samp{None}, @var{visualizer} must be a Python expression.
30875 This expression must evaluate to a callable object which accepts a
30876 single argument. @value{GDBN} will call this object with the value of
30877 the varobj @var{name} as an argument (this is done so that the same
30878 Python pretty-printing code can be used for both the CLI and MI).
30879 When called, this object must return an object which conforms to the
30880 pretty-printing interface (@pxref{Pretty Printing API}).
30882 The pre-defined function @code{gdb.default_visualizer} may be used to
30883 select a visualizer by following the built-in process
30884 (@pxref{Selecting Pretty-Printers}). This is done automatically when
30885 a varobj is created, and so ordinarily is not needed.
30887 This feature is only available if Python support is enabled. The MI
30888 command @code{-list-features} (@pxref{GDB/MI Support Commands})
30889 can be used to check this.
30891 @subsubheading Example
30893 Resetting the visualizer:
30897 -var-set-visualizer V None
30901 Reselecting the default (type-based) visualizer:
30905 -var-set-visualizer V gdb.default_visualizer
30909 Suppose @code{SomeClass} is a visualizer class. A lambda expression
30910 can be used to instantiate this class for a varobj:
30914 -var-set-visualizer V "lambda val: SomeClass()"
30918 @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
30919 @node GDB/MI Data Manipulation
30920 @section @sc{gdb/mi} Data Manipulation
30922 @cindex data manipulation, in @sc{gdb/mi}
30923 @cindex @sc{gdb/mi}, data manipulation
30924 This section describes the @sc{gdb/mi} commands that manipulate data:
30925 examine memory and registers, evaluate expressions, etc.
30927 For details about what an addressable memory unit is,
30928 @pxref{addressable memory unit}.
30930 @c REMOVED FROM THE INTERFACE.
30931 @c @subheading -data-assign
30932 @c Change the value of a program variable. Plenty of side effects.
30933 @c @subsubheading GDB Command
30935 @c @subsubheading Example
30938 @subheading The @code{-data-disassemble} Command
30939 @findex -data-disassemble
30941 @subsubheading Synopsis
30945 [ -s @var{start-addr} -e @var{end-addr} ]
30946 | [ -f @var{filename} -l @var{linenum} [ -n @var{lines} ] ]
30954 @item @var{start-addr}
30955 is the beginning address (or @code{$pc})
30956 @item @var{end-addr}
30958 @item @var{filename}
30959 is the name of the file to disassemble
30960 @item @var{linenum}
30961 is the line number to disassemble around
30963 is the number of disassembly lines to be produced. If it is -1,
30964 the whole function will be disassembled, in case no @var{end-addr} is
30965 specified. If @var{end-addr} is specified as a non-zero value, and
30966 @var{lines} is lower than the number of disassembly lines between
30967 @var{start-addr} and @var{end-addr}, only @var{lines} lines are
30968 displayed; if @var{lines} is higher than the number of lines between
30969 @var{start-addr} and @var{end-addr}, only the lines up to @var{end-addr}
30974 @item 0 disassembly only
30975 @item 1 mixed source and disassembly (deprecated)
30976 @item 2 disassembly with raw opcodes
30977 @item 3 mixed source and disassembly with raw opcodes (deprecated)
30978 @item 4 mixed source and disassembly
30979 @item 5 mixed source and disassembly with raw opcodes
30982 Modes 1 and 3 are deprecated. The output is ``source centric''
30983 which hasn't proved useful in practice.
30984 @xref{Machine Code}, for a discussion of the difference between
30985 @code{/m} and @code{/s} output of the @code{disassemble} command.
30988 @subsubheading Result
30990 The result of the @code{-data-disassemble} command will be a list named
30991 @samp{asm_insns}, the contents of this list depend on the @var{mode}
30992 used with the @code{-data-disassemble} command.
30994 For modes 0 and 2 the @samp{asm_insns} list contains tuples with the
30999 The address at which this instruction was disassembled.
31002 The name of the function this instruction is within.
31005 The decimal offset in bytes from the start of @samp{func-name}.
31008 The text disassembly for this @samp{address}.
31011 This field is only present for modes 2, 3 and 5. This contains the raw opcode
31012 bytes for the @samp{inst} field.
31016 For modes 1, 3, 4 and 5 the @samp{asm_insns} list contains tuples named
31017 @samp{src_and_asm_line}, each of which has the following fields:
31021 The line number within @samp{file}.
31024 The file name from the compilation unit. This might be an absolute
31025 file name or a relative file name depending on the compile command
31029 Absolute file name of @samp{file}. It is converted to a canonical form
31030 using the source file search path
31031 (@pxref{Source Path, ,Specifying Source Directories})
31032 and after resolving all the symbolic links.
31034 If the source file is not found this field will contain the path as
31035 present in the debug information.
31037 @item line_asm_insn
31038 This is a list of tuples containing the disassembly for @samp{line} in
31039 @samp{file}. The fields of each tuple are the same as for
31040 @code{-data-disassemble} in @var{mode} 0 and 2, so @samp{address},
31041 @samp{func-name}, @samp{offset}, @samp{inst}, and optionally
31046 Note that whatever included in the @samp{inst} field, is not
31047 manipulated directly by @sc{gdb/mi}, i.e., it is not possible to
31050 @subsubheading @value{GDBN} Command
31052 The corresponding @value{GDBN} command is @samp{disassemble}.
31054 @subsubheading Example
31056 Disassemble from the current value of @code{$pc} to @code{$pc + 20}:
31060 -data-disassemble -s $pc -e "$pc + 20" -- 0
31063 @{address="0x000107c0",func-name="main",offset="4",
31064 inst="mov 2, %o0"@},
31065 @{address="0x000107c4",func-name="main",offset="8",
31066 inst="sethi %hi(0x11800), %o2"@},
31067 @{address="0x000107c8",func-name="main",offset="12",
31068 inst="or %o2, 0x140, %o1\t! 0x11940 <_lib_version+8>"@},
31069 @{address="0x000107cc",func-name="main",offset="16",
31070 inst="sethi %hi(0x11800), %o2"@},
31071 @{address="0x000107d0",func-name="main",offset="20",
31072 inst="or %o2, 0x168, %o4\t! 0x11968 <_lib_version+48>"@}]
31076 Disassemble the whole @code{main} function. Line 32 is part of
31080 -data-disassemble -f basics.c -l 32 -- 0
31082 @{address="0x000107bc",func-name="main",offset="0",
31083 inst="save %sp, -112, %sp"@},
31084 @{address="0x000107c0",func-name="main",offset="4",
31085 inst="mov 2, %o0"@},
31086 @{address="0x000107c4",func-name="main",offset="8",
31087 inst="sethi %hi(0x11800), %o2"@},
31089 @{address="0x0001081c",func-name="main",offset="96",inst="ret "@},
31090 @{address="0x00010820",func-name="main",offset="100",inst="restore "@}]
31094 Disassemble 3 instructions from the start of @code{main}:
31098 -data-disassemble -f basics.c -l 32 -n 3 -- 0
31100 @{address="0x000107bc",func-name="main",offset="0",
31101 inst="save %sp, -112, %sp"@},
31102 @{address="0x000107c0",func-name="main",offset="4",
31103 inst="mov 2, %o0"@},
31104 @{address="0x000107c4",func-name="main",offset="8",
31105 inst="sethi %hi(0x11800), %o2"@}]
31109 Disassemble 3 instructions from the start of @code{main} in mixed mode:
31113 -data-disassemble -f basics.c -l 32 -n 3 -- 1
31115 src_and_asm_line=@{line="31",
31116 file="../../../src/gdb/testsuite/gdb.mi/basics.c",
31117 fullname="/absolute/path/to/src/gdb/testsuite/gdb.mi/basics.c",
31118 line_asm_insn=[@{address="0x000107bc",
31119 func-name="main",offset="0",inst="save %sp, -112, %sp"@}]@},
31120 src_and_asm_line=@{line="32",
31121 file="../../../src/gdb/testsuite/gdb.mi/basics.c",
31122 fullname="/absolute/path/to/src/gdb/testsuite/gdb.mi/basics.c",
31123 line_asm_insn=[@{address="0x000107c0",
31124 func-name="main",offset="4",inst="mov 2, %o0"@},
31125 @{address="0x000107c4",func-name="main",offset="8",
31126 inst="sethi %hi(0x11800), %o2"@}]@}]
31131 @subheading The @code{-data-evaluate-expression} Command
31132 @findex -data-evaluate-expression
31134 @subsubheading Synopsis
31137 -data-evaluate-expression @var{expr}
31140 Evaluate @var{expr} as an expression. The expression could contain an
31141 inferior function call. The function call will execute synchronously.
31142 If the expression contains spaces, it must be enclosed in double quotes.
31144 @subsubheading @value{GDBN} Command
31146 The corresponding @value{GDBN} commands are @samp{print}, @samp{output}, and
31147 @samp{call}. In @code{gdbtk} only, there's a corresponding
31148 @samp{gdb_eval} command.
31150 @subsubheading Example
31152 In the following example, the numbers that precede the commands are the
31153 @dfn{tokens} described in @ref{GDB/MI Command Syntax, ,@sc{gdb/mi}
31154 Command Syntax}. Notice how @sc{gdb/mi} returns the same tokens in its
31158 211-data-evaluate-expression A
31161 311-data-evaluate-expression &A
31162 311^done,value="0xefffeb7c"
31164 411-data-evaluate-expression A+3
31167 511-data-evaluate-expression "A + 3"
31173 @subheading The @code{-data-list-changed-registers} Command
31174 @findex -data-list-changed-registers
31176 @subsubheading Synopsis
31179 -data-list-changed-registers
31182 Display a list of the registers that have changed.
31184 @subsubheading @value{GDBN} Command
31186 @value{GDBN} doesn't have a direct analog for this command; @code{gdbtk}
31187 has the corresponding command @samp{gdb_changed_register_list}.
31189 @subsubheading Example
31191 On a PPC MBX board:
31199 *stopped,reason="breakpoint-hit",disp="keep",bkptno="1",frame=@{
31200 func="main",args=[],file="try.c",fullname="/home/foo/bar/try.c",
31203 -data-list-changed-registers
31204 ^done,changed-registers=["0","1","2","4","5","6","7","8","9",
31205 "10","11","13","14","15","16","17","18","19","20","21","22","23",
31206 "24","25","26","27","28","30","31","64","65","66","67","69"]
31211 @subheading The @code{-data-list-register-names} Command
31212 @findex -data-list-register-names
31214 @subsubheading Synopsis
31217 -data-list-register-names [ ( @var{regno} )+ ]
31220 Show a list of register names for the current target. If no arguments
31221 are given, it shows a list of the names of all the registers. If
31222 integer numbers are given as arguments, it will print a list of the
31223 names of the registers corresponding to the arguments. To ensure
31224 consistency between a register name and its number, the output list may
31225 include empty register names.
31227 @subsubheading @value{GDBN} Command
31229 @value{GDBN} does not have a command which corresponds to
31230 @samp{-data-list-register-names}. In @code{gdbtk} there is a
31231 corresponding command @samp{gdb_regnames}.
31233 @subsubheading Example
31235 For the PPC MBX board:
31238 -data-list-register-names
31239 ^done,register-names=["r0","r1","r2","r3","r4","r5","r6","r7",
31240 "r8","r9","r10","r11","r12","r13","r14","r15","r16","r17","r18",
31241 "r19","r20","r21","r22","r23","r24","r25","r26","r27","r28","r29",
31242 "r30","r31","f0","f1","f2","f3","f4","f5","f6","f7","f8","f9",
31243 "f10","f11","f12","f13","f14","f15","f16","f17","f18","f19","f20",
31244 "f21","f22","f23","f24","f25","f26","f27","f28","f29","f30","f31",
31245 "", "pc","ps","cr","lr","ctr","xer"]
31247 -data-list-register-names 1 2 3
31248 ^done,register-names=["r1","r2","r3"]
31252 @subheading The @code{-data-list-register-values} Command
31253 @findex -data-list-register-values
31255 @subsubheading Synopsis
31258 -data-list-register-values
31259 [ @code{--skip-unavailable} ] @var{fmt} [ ( @var{regno} )*]
31262 Display the registers' contents. The format according to which the
31263 registers' contents are to be returned is given by @var{fmt}, followed
31264 by an optional list of numbers specifying the registers to display. A
31265 missing list of numbers indicates that the contents of all the
31266 registers must be returned. The @code{--skip-unavailable} option
31267 indicates that only the available registers are to be returned.
31269 Allowed formats for @var{fmt} are:
31286 @subsubheading @value{GDBN} Command
31288 The corresponding @value{GDBN} commands are @samp{info reg}, @samp{info
31289 all-reg}, and (in @code{gdbtk}) @samp{gdb_fetch_registers}.
31291 @subsubheading Example
31293 For a PPC MBX board (note: line breaks are for readability only, they
31294 don't appear in the actual output):
31298 -data-list-register-values r 64 65
31299 ^done,register-values=[@{number="64",value="0xfe00a300"@},
31300 @{number="65",value="0x00029002"@}]
31302 -data-list-register-values x
31303 ^done,register-values=[@{number="0",value="0xfe0043c8"@},
31304 @{number="1",value="0x3fff88"@},@{number="2",value="0xfffffffe"@},
31305 @{number="3",value="0x0"@},@{number="4",value="0xa"@},
31306 @{number="5",value="0x3fff68"@},@{number="6",value="0x3fff58"@},
31307 @{number="7",value="0xfe011e98"@},@{number="8",value="0x2"@},
31308 @{number="9",value="0xfa202820"@},@{number="10",value="0xfa202808"@},
31309 @{number="11",value="0x1"@},@{number="12",value="0x0"@},
31310 @{number="13",value="0x4544"@},@{number="14",value="0xffdfffff"@},
31311 @{number="15",value="0xffffffff"@},@{number="16",value="0xfffffeff"@},
31312 @{number="17",value="0xefffffed"@},@{number="18",value="0xfffffffe"@},
31313 @{number="19",value="0xffffffff"@},@{number="20",value="0xffffffff"@},
31314 @{number="21",value="0xffffffff"@},@{number="22",value="0xfffffff7"@},
31315 @{number="23",value="0xffffffff"@},@{number="24",value="0xffffffff"@},
31316 @{number="25",value="0xffffffff"@},@{number="26",value="0xfffffffb"@},
31317 @{number="27",value="0xffffffff"@},@{number="28",value="0xf7bfffff"@},
31318 @{number="29",value="0x0"@},@{number="30",value="0xfe010000"@},
31319 @{number="31",value="0x0"@},@{number="32",value="0x0"@},
31320 @{number="33",value="0x0"@},@{number="34",value="0x0"@},
31321 @{number="35",value="0x0"@},@{number="36",value="0x0"@},
31322 @{number="37",value="0x0"@},@{number="38",value="0x0"@},
31323 @{number="39",value="0x0"@},@{number="40",value="0x0"@},
31324 @{number="41",value="0x0"@},@{number="42",value="0x0"@},
31325 @{number="43",value="0x0"@},@{number="44",value="0x0"@},
31326 @{number="45",value="0x0"@},@{number="46",value="0x0"@},
31327 @{number="47",value="0x0"@},@{number="48",value="0x0"@},
31328 @{number="49",value="0x0"@},@{number="50",value="0x0"@},
31329 @{number="51",value="0x0"@},@{number="52",value="0x0"@},
31330 @{number="53",value="0x0"@},@{number="54",value="0x0"@},
31331 @{number="55",value="0x0"@},@{number="56",value="0x0"@},
31332 @{number="57",value="0x0"@},@{number="58",value="0x0"@},
31333 @{number="59",value="0x0"@},@{number="60",value="0x0"@},
31334 @{number="61",value="0x0"@},@{number="62",value="0x0"@},
31335 @{number="63",value="0x0"@},@{number="64",value="0xfe00a300"@},
31336 @{number="65",value="0x29002"@},@{number="66",value="0x202f04b5"@},
31337 @{number="67",value="0xfe0043b0"@},@{number="68",value="0xfe00b3e4"@},
31338 @{number="69",value="0x20002b03"@}]
31343 @subheading The @code{-data-read-memory} Command
31344 @findex -data-read-memory
31346 This command is deprecated, use @code{-data-read-memory-bytes} instead.
31348 @subsubheading Synopsis
31351 -data-read-memory [ -o @var{byte-offset} ]
31352 @var{address} @var{word-format} @var{word-size}
31353 @var{nr-rows} @var{nr-cols} [ @var{aschar} ]
31360 @item @var{address}
31361 An expression specifying the address of the first memory word to be
31362 read. Complex expressions containing embedded white space should be
31363 quoted using the C convention.
31365 @item @var{word-format}
31366 The format to be used to print the memory words. The notation is the
31367 same as for @value{GDBN}'s @code{print} command (@pxref{Output Formats,
31370 @item @var{word-size}
31371 The size of each memory word in bytes.
31373 @item @var{nr-rows}
31374 The number of rows in the output table.
31376 @item @var{nr-cols}
31377 The number of columns in the output table.
31380 If present, indicates that each row should include an @sc{ascii} dump. The
31381 value of @var{aschar} is used as a padding character when a byte is not a
31382 member of the printable @sc{ascii} character set (printable @sc{ascii}
31383 characters are those whose code is between 32 and 126, inclusively).
31385 @item @var{byte-offset}
31386 An offset to add to the @var{address} before fetching memory.
31389 This command displays memory contents as a table of @var{nr-rows} by
31390 @var{nr-cols} words, each word being @var{word-size} bytes. In total,
31391 @code{@var{nr-rows} * @var{nr-cols} * @var{word-size}} bytes are read
31392 (returned as @samp{total-bytes}). Should less than the requested number
31393 of bytes be returned by the target, the missing words are identified
31394 using @samp{N/A}. The number of bytes read from the target is returned
31395 in @samp{nr-bytes} and the starting address used to read memory in
31398 The address of the next/previous row or page is available in
31399 @samp{next-row} and @samp{prev-row}, @samp{next-page} and
31402 @subsubheading @value{GDBN} Command
31404 The corresponding @value{GDBN} command is @samp{x}. @code{gdbtk} has
31405 @samp{gdb_get_mem} memory read command.
31407 @subsubheading Example
31409 Read six bytes of memory starting at @code{bytes+6} but then offset by
31410 @code{-6} bytes. Format as three rows of two columns. One byte per
31411 word. Display each word in hex.
31415 9-data-read-memory -o -6 -- bytes+6 x 1 3 2
31416 9^done,addr="0x00001390",nr-bytes="6",total-bytes="6",
31417 next-row="0x00001396",prev-row="0x0000138e",next-page="0x00001396",
31418 prev-page="0x0000138a",memory=[
31419 @{addr="0x00001390",data=["0x00","0x01"]@},
31420 @{addr="0x00001392",data=["0x02","0x03"]@},
31421 @{addr="0x00001394",data=["0x04","0x05"]@}]
31425 Read two bytes of memory starting at address @code{shorts + 64} and
31426 display as a single word formatted in decimal.
31430 5-data-read-memory shorts+64 d 2 1 1
31431 5^done,addr="0x00001510",nr-bytes="2",total-bytes="2",
31432 next-row="0x00001512",prev-row="0x0000150e",
31433 next-page="0x00001512",prev-page="0x0000150e",memory=[
31434 @{addr="0x00001510",data=["128"]@}]
31438 Read thirty two bytes of memory starting at @code{bytes+16} and format
31439 as eight rows of four columns. Include a string encoding with @samp{x}
31440 used as the non-printable character.
31444 4-data-read-memory bytes+16 x 1 8 4 x
31445 4^done,addr="0x000013a0",nr-bytes="32",total-bytes="32",
31446 next-row="0x000013c0",prev-row="0x0000139c",
31447 next-page="0x000013c0",prev-page="0x00001380",memory=[
31448 @{addr="0x000013a0",data=["0x10","0x11","0x12","0x13"],ascii="xxxx"@},
31449 @{addr="0x000013a4",data=["0x14","0x15","0x16","0x17"],ascii="xxxx"@},
31450 @{addr="0x000013a8",data=["0x18","0x19","0x1a","0x1b"],ascii="xxxx"@},
31451 @{addr="0x000013ac",data=["0x1c","0x1d","0x1e","0x1f"],ascii="xxxx"@},
31452 @{addr="0x000013b0",data=["0x20","0x21","0x22","0x23"],ascii=" !\"#"@},
31453 @{addr="0x000013b4",data=["0x24","0x25","0x26","0x27"],ascii="$%&'"@},
31454 @{addr="0x000013b8",data=["0x28","0x29","0x2a","0x2b"],ascii="()*+"@},
31455 @{addr="0x000013bc",data=["0x2c","0x2d","0x2e","0x2f"],ascii=",-./"@}]
31459 @subheading The @code{-data-read-memory-bytes} Command
31460 @findex -data-read-memory-bytes
31462 @subsubheading Synopsis
31465 -data-read-memory-bytes [ -o @var{offset} ]
31466 @var{address} @var{count}
31473 @item @var{address}
31474 An expression specifying the address of the first addressable memory unit
31475 to be read. Complex expressions containing embedded white space should be
31476 quoted using the C convention.
31479 The number of addressable memory units to read. This should be an integer
31483 The offset relative to @var{address} at which to start reading. This
31484 should be an integer literal. This option is provided so that a frontend
31485 is not required to first evaluate address and then perform address
31486 arithmetics itself.
31490 This command attempts to read all accessible memory regions in the
31491 specified range. First, all regions marked as unreadable in the memory
31492 map (if one is defined) will be skipped. @xref{Memory Region
31493 Attributes}. Second, @value{GDBN} will attempt to read the remaining
31494 regions. For each one, if reading full region results in an errors,
31495 @value{GDBN} will try to read a subset of the region.
31497 In general, every single memory unit in the region may be readable or not,
31498 and the only way to read every readable unit is to try a read at
31499 every address, which is not practical. Therefore, @value{GDBN} will
31500 attempt to read all accessible memory units at either beginning or the end
31501 of the region, using a binary division scheme. This heuristic works
31502 well for reading accross a memory map boundary. Note that if a region
31503 has a readable range that is neither at the beginning or the end,
31504 @value{GDBN} will not read it.
31506 The result record (@pxref{GDB/MI Result Records}) that is output of
31507 the command includes a field named @samp{memory} whose content is a
31508 list of tuples. Each tuple represent a successfully read memory block
31509 and has the following fields:
31513 The start address of the memory block, as hexadecimal literal.
31516 The end address of the memory block, as hexadecimal literal.
31519 The offset of the memory block, as hexadecimal literal, relative to
31520 the start address passed to @code{-data-read-memory-bytes}.
31523 The contents of the memory block, in hex.
31529 @subsubheading @value{GDBN} Command
31531 The corresponding @value{GDBN} command is @samp{x}.
31533 @subsubheading Example
31537 -data-read-memory-bytes &a 10
31538 ^done,memory=[@{begin="0xbffff154",offset="0x00000000",
31540 contents="01000000020000000300"@}]
31545 @subheading The @code{-data-write-memory-bytes} Command
31546 @findex -data-write-memory-bytes
31548 @subsubheading Synopsis
31551 -data-write-memory-bytes @var{address} @var{contents}
31552 -data-write-memory-bytes @var{address} @var{contents} @r{[}@var{count}@r{]}
31559 @item @var{address}
31560 An expression specifying the address of the first addressable memory unit
31561 to be written. Complex expressions containing embedded white space should
31562 be quoted using the C convention.
31564 @item @var{contents}
31565 The hex-encoded data to write. It is an error if @var{contents} does
31566 not represent an integral number of addressable memory units.
31569 Optional argument indicating the number of addressable memory units to be
31570 written. If @var{count} is greater than @var{contents}' length,
31571 @value{GDBN} will repeatedly write @var{contents} until it fills
31572 @var{count} memory units.
31576 @subsubheading @value{GDBN} Command
31578 There's no corresponding @value{GDBN} command.
31580 @subsubheading Example
31584 -data-write-memory-bytes &a "aabbccdd"
31591 -data-write-memory-bytes &a "aabbccdd" 16e
31596 @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
31597 @node GDB/MI Tracepoint Commands
31598 @section @sc{gdb/mi} Tracepoint Commands
31600 The commands defined in this section implement MI support for
31601 tracepoints. For detailed introduction, see @ref{Tracepoints}.
31603 @subheading The @code{-trace-find} Command
31604 @findex -trace-find
31606 @subsubheading Synopsis
31609 -trace-find @var{mode} [@var{parameters}@dots{}]
31612 Find a trace frame using criteria defined by @var{mode} and
31613 @var{parameters}. The following table lists permissible
31614 modes and their parameters. For details of operation, see @ref{tfind}.
31619 No parameters are required. Stops examining trace frames.
31622 An integer is required as parameter. Selects tracepoint frame with
31625 @item tracepoint-number
31626 An integer is required as parameter. Finds next
31627 trace frame that corresponds to tracepoint with the specified number.
31630 An address is required as parameter. Finds
31631 next trace frame that corresponds to any tracepoint at the specified
31634 @item pc-inside-range
31635 Two addresses are required as parameters. Finds next trace
31636 frame that corresponds to a tracepoint at an address inside the
31637 specified range. Both bounds are considered to be inside the range.
31639 @item pc-outside-range
31640 Two addresses are required as parameters. Finds
31641 next trace frame that corresponds to a tracepoint at an address outside
31642 the specified range. Both bounds are considered to be inside the range.
31645 Line specification is required as parameter. @xref{Specify Location}.
31646 Finds next trace frame that corresponds to a tracepoint at
31647 the specified location.
31651 If @samp{none} was passed as @var{mode}, the response does not
31652 have fields. Otherwise, the response may have the following fields:
31656 This field has either @samp{0} or @samp{1} as the value, depending
31657 on whether a matching tracepoint was found.
31660 The index of the found traceframe. This field is present iff
31661 the @samp{found} field has value of @samp{1}.
31664 The index of the found tracepoint. This field is present iff
31665 the @samp{found} field has value of @samp{1}.
31668 The information about the frame corresponding to the found trace
31669 frame. This field is present only if a trace frame was found.
31670 @xref{GDB/MI Frame Information}, for description of this field.
31674 @subsubheading @value{GDBN} Command
31676 The corresponding @value{GDBN} command is @samp{tfind}.
31678 @subheading -trace-define-variable
31679 @findex -trace-define-variable
31681 @subsubheading Synopsis
31684 -trace-define-variable @var{name} [ @var{value} ]
31687 Create trace variable @var{name} if it does not exist. If
31688 @var{value} is specified, sets the initial value of the specified
31689 trace variable to that value. Note that the @var{name} should start
31690 with the @samp{$} character.
31692 @subsubheading @value{GDBN} Command
31694 The corresponding @value{GDBN} command is @samp{tvariable}.
31696 @subheading The @code{-trace-frame-collected} Command
31697 @findex -trace-frame-collected
31699 @subsubheading Synopsis
31702 -trace-frame-collected
31703 [--var-print-values @var{var_pval}]
31704 [--comp-print-values @var{comp_pval}]
31705 [--registers-format @var{regformat}]
31706 [--memory-contents]
31709 This command returns the set of collected objects, register names,
31710 trace state variable names, memory ranges and computed expressions
31711 that have been collected at a particular trace frame. The optional
31712 parameters to the command affect the output format in different ways.
31713 See the output description table below for more details.
31715 The reported names can be used in the normal manner to create
31716 varobjs and inspect the objects themselves. The items returned by
31717 this command are categorized so that it is clear which is a variable,
31718 which is a register, which is a trace state variable, which is a
31719 memory range and which is a computed expression.
31721 For instance, if the actions were
31723 collect myVar, myArray[myIndex], myObj.field, myPtr->field, myCount + 2
31724 collect *(int*)0xaf02bef0@@40
31728 the object collected in its entirety would be @code{myVar}. The
31729 object @code{myArray} would be partially collected, because only the
31730 element at index @code{myIndex} would be collected. The remaining
31731 objects would be computed expressions.
31733 An example output would be:
31737 -trace-frame-collected
31739 explicit-variables=[@{name="myVar",value="1"@}],
31740 computed-expressions=[@{name="myArray[myIndex]",value="0"@},
31741 @{name="myObj.field",value="0"@},
31742 @{name="myPtr->field",value="1"@},
31743 @{name="myCount + 2",value="3"@},
31744 @{name="$tvar1 + 1",value="43970027"@}],
31745 registers=[@{number="0",value="0x7fe2c6e79ec8"@},
31746 @{number="1",value="0x0"@},
31747 @{number="2",value="0x4"@},
31749 @{number="125",value="0x0"@}],
31750 tvars=[@{name="$tvar1",current="43970026"@}],
31751 memory=[@{address="0x0000000000602264",length="4"@},
31752 @{address="0x0000000000615bc0",length="4"@}]
31759 @item explicit-variables
31760 The set of objects that have been collected in their entirety (as
31761 opposed to collecting just a few elements of an array or a few struct
31762 members). For each object, its name and value are printed.
31763 The @code{--var-print-values} option affects how or whether the value
31764 field is output. If @var{var_pval} is 0, then print only the names;
31765 if it is 1, print also their values; and if it is 2, print the name,
31766 type and value for simple data types, and the name and type for
31767 arrays, structures and unions.
31769 @item computed-expressions
31770 The set of computed expressions that have been collected at the
31771 current trace frame. The @code{--comp-print-values} option affects
31772 this set like the @code{--var-print-values} option affects the
31773 @code{explicit-variables} set. See above.
31776 The registers that have been collected at the current trace frame.
31777 For each register collected, the name and current value are returned.
31778 The value is formatted according to the @code{--registers-format}
31779 option. See the @command{-data-list-register-values} command for a
31780 list of the allowed formats. The default is @samp{x}.
31783 The trace state variables that have been collected at the current
31784 trace frame. For each trace state variable collected, the name and
31785 current value are returned.
31788 The set of memory ranges that have been collected at the current trace
31789 frame. Its content is a list of tuples. Each tuple represents a
31790 collected memory range and has the following fields:
31794 The start address of the memory range, as hexadecimal literal.
31797 The length of the memory range, as decimal literal.
31800 The contents of the memory block, in hex. This field is only present
31801 if the @code{--memory-contents} option is specified.
31807 @subsubheading @value{GDBN} Command
31809 There is no corresponding @value{GDBN} command.
31811 @subsubheading Example
31813 @subheading -trace-list-variables
31814 @findex -trace-list-variables
31816 @subsubheading Synopsis
31819 -trace-list-variables
31822 Return a table of all defined trace variables. Each element of the
31823 table has the following fields:
31827 The name of the trace variable. This field is always present.
31830 The initial value. This is a 64-bit signed integer. This
31831 field is always present.
31834 The value the trace variable has at the moment. This is a 64-bit
31835 signed integer. This field is absent iff current value is
31836 not defined, for example if the trace was never run, or is
31841 @subsubheading @value{GDBN} Command
31843 The corresponding @value{GDBN} command is @samp{tvariables}.
31845 @subsubheading Example
31849 -trace-list-variables
31850 ^done,trace-variables=@{nr_rows="1",nr_cols="3",
31851 hdr=[@{width="15",alignment="-1",col_name="name",colhdr="Name"@},
31852 @{width="11",alignment="-1",col_name="initial",colhdr="Initial"@},
31853 @{width="11",alignment="-1",col_name="current",colhdr="Current"@}],
31854 body=[variable=@{name="$trace_timestamp",initial="0"@}
31855 variable=@{name="$foo",initial="10",current="15"@}]@}
31859 @subheading -trace-save
31860 @findex -trace-save
31862 @subsubheading Synopsis
31865 -trace-save [ -r ] [ -ctf ] @var{filename}
31868 Saves the collected trace data to @var{filename}. Without the
31869 @samp{-r} option, the data is downloaded from the target and saved
31870 in a local file. With the @samp{-r} option the target is asked
31871 to perform the save.
31873 By default, this command will save the trace in the tfile format. You can
31874 supply the optional @samp{-ctf} argument to save it the CTF format. See
31875 @ref{Trace Files} for more information about CTF.
31877 @subsubheading @value{GDBN} Command
31879 The corresponding @value{GDBN} command is @samp{tsave}.
31882 @subheading -trace-start
31883 @findex -trace-start
31885 @subsubheading Synopsis
31891 Starts a tracing experiment. The result of this command does not
31894 @subsubheading @value{GDBN} Command
31896 The corresponding @value{GDBN} command is @samp{tstart}.
31898 @subheading -trace-status
31899 @findex -trace-status
31901 @subsubheading Synopsis
31907 Obtains the status of a tracing experiment. The result may include
31908 the following fields:
31913 May have a value of either @samp{0}, when no tracing operations are
31914 supported, @samp{1}, when all tracing operations are supported, or
31915 @samp{file} when examining trace file. In the latter case, examining
31916 of trace frame is possible but new tracing experiement cannot be
31917 started. This field is always present.
31920 May have a value of either @samp{0} or @samp{1} depending on whether
31921 tracing experiement is in progress on target. This field is present
31922 if @samp{supported} field is not @samp{0}.
31925 Report the reason why the tracing was stopped last time. This field
31926 may be absent iff tracing was never stopped on target yet. The
31927 value of @samp{request} means the tracing was stopped as result of
31928 the @code{-trace-stop} command. The value of @samp{overflow} means
31929 the tracing buffer is full. The value of @samp{disconnection} means
31930 tracing was automatically stopped when @value{GDBN} has disconnected.
31931 The value of @samp{passcount} means tracing was stopped when a
31932 tracepoint was passed a maximal number of times for that tracepoint.
31933 This field is present if @samp{supported} field is not @samp{0}.
31935 @item stopping-tracepoint
31936 The number of tracepoint whose passcount as exceeded. This field is
31937 present iff the @samp{stop-reason} field has the value of
31941 @itemx frames-created
31942 The @samp{frames} field is a count of the total number of trace frames
31943 in the trace buffer, while @samp{frames-created} is the total created
31944 during the run, including ones that were discarded, such as when a
31945 circular trace buffer filled up. Both fields are optional.
31949 These fields tell the current size of the tracing buffer and the
31950 remaining space. These fields are optional.
31953 The value of the circular trace buffer flag. @code{1} means that the
31954 trace buffer is circular and old trace frames will be discarded if
31955 necessary to make room, @code{0} means that the trace buffer is linear
31959 The value of the disconnected tracing flag. @code{1} means that
31960 tracing will continue after @value{GDBN} disconnects, @code{0} means
31961 that the trace run will stop.
31964 The filename of the trace file being examined. This field is
31965 optional, and only present when examining a trace file.
31969 @subsubheading @value{GDBN} Command
31971 The corresponding @value{GDBN} command is @samp{tstatus}.
31973 @subheading -trace-stop
31974 @findex -trace-stop
31976 @subsubheading Synopsis
31982 Stops a tracing experiment. The result of this command has the same
31983 fields as @code{-trace-status}, except that the @samp{supported} and
31984 @samp{running} fields are not output.
31986 @subsubheading @value{GDBN} Command
31988 The corresponding @value{GDBN} command is @samp{tstop}.
31991 @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
31992 @node GDB/MI Symbol Query
31993 @section @sc{gdb/mi} Symbol Query Commands
31997 @subheading The @code{-symbol-info-address} Command
31998 @findex -symbol-info-address
32000 @subsubheading Synopsis
32003 -symbol-info-address @var{symbol}
32006 Describe where @var{symbol} is stored.
32008 @subsubheading @value{GDBN} Command
32010 The corresponding @value{GDBN} command is @samp{info address}.
32012 @subsubheading Example
32016 @subheading The @code{-symbol-info-file} Command
32017 @findex -symbol-info-file
32019 @subsubheading Synopsis
32025 Show the file for the symbol.
32027 @subsubheading @value{GDBN} Command
32029 There's no equivalent @value{GDBN} command. @code{gdbtk} has
32030 @samp{gdb_find_file}.
32032 @subsubheading Example
32036 @subheading The @code{-symbol-info-function} Command
32037 @findex -symbol-info-function
32039 @subsubheading Synopsis
32042 -symbol-info-function
32045 Show which function the symbol lives in.
32047 @subsubheading @value{GDBN} Command
32049 @samp{gdb_get_function} in @code{gdbtk}.
32051 @subsubheading Example
32055 @subheading The @code{-symbol-info-line} Command
32056 @findex -symbol-info-line
32058 @subsubheading Synopsis
32064 Show the core addresses of the code for a source line.
32066 @subsubheading @value{GDBN} Command
32068 The corresponding @value{GDBN} command is @samp{info line}.
32069 @code{gdbtk} has the @samp{gdb_get_line} and @samp{gdb_get_file} commands.
32071 @subsubheading Example
32075 @subheading The @code{-symbol-info-symbol} Command
32076 @findex -symbol-info-symbol
32078 @subsubheading Synopsis
32081 -symbol-info-symbol @var{addr}
32084 Describe what symbol is at location @var{addr}.
32086 @subsubheading @value{GDBN} Command
32088 The corresponding @value{GDBN} command is @samp{info symbol}.
32090 @subsubheading Example
32094 @subheading The @code{-symbol-list-functions} Command
32095 @findex -symbol-list-functions
32097 @subsubheading Synopsis
32100 -symbol-list-functions
32103 List the functions in the executable.
32105 @subsubheading @value{GDBN} Command
32107 @samp{info functions} in @value{GDBN}, @samp{gdb_listfunc} and
32108 @samp{gdb_search} in @code{gdbtk}.
32110 @subsubheading Example
32115 @subheading The @code{-symbol-list-lines} Command
32116 @findex -symbol-list-lines
32118 @subsubheading Synopsis
32121 -symbol-list-lines @var{filename}
32124 Print the list of lines that contain code and their associated program
32125 addresses for the given source filename. The entries are sorted in
32126 ascending PC order.
32128 @subsubheading @value{GDBN} Command
32130 There is no corresponding @value{GDBN} command.
32132 @subsubheading Example
32135 -symbol-list-lines basics.c
32136 ^done,lines=[@{pc="0x08048554",line="7"@},@{pc="0x0804855a",line="8"@}]
32142 @subheading The @code{-symbol-list-types} Command
32143 @findex -symbol-list-types
32145 @subsubheading Synopsis
32151 List all the type names.
32153 @subsubheading @value{GDBN} Command
32155 The corresponding commands are @samp{info types} in @value{GDBN},
32156 @samp{gdb_search} in @code{gdbtk}.
32158 @subsubheading Example
32162 @subheading The @code{-symbol-list-variables} Command
32163 @findex -symbol-list-variables
32165 @subsubheading Synopsis
32168 -symbol-list-variables
32171 List all the global and static variable names.
32173 @subsubheading @value{GDBN} Command
32175 @samp{info variables} in @value{GDBN}, @samp{gdb_search} in @code{gdbtk}.
32177 @subsubheading Example
32181 @subheading The @code{-symbol-locate} Command
32182 @findex -symbol-locate
32184 @subsubheading Synopsis
32190 @subsubheading @value{GDBN} Command
32192 @samp{gdb_loc} in @code{gdbtk}.
32194 @subsubheading Example
32198 @subheading The @code{-symbol-type} Command
32199 @findex -symbol-type
32201 @subsubheading Synopsis
32204 -symbol-type @var{variable}
32207 Show type of @var{variable}.
32209 @subsubheading @value{GDBN} Command
32211 The corresponding @value{GDBN} command is @samp{ptype}, @code{gdbtk} has
32212 @samp{gdb_obj_variable}.
32214 @subsubheading Example
32219 @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
32220 @node GDB/MI File Commands
32221 @section @sc{gdb/mi} File Commands
32223 This section describes the GDB/MI commands to specify executable file names
32224 and to read in and obtain symbol table information.
32226 @subheading The @code{-file-exec-and-symbols} Command
32227 @findex -file-exec-and-symbols
32229 @subsubheading Synopsis
32232 -file-exec-and-symbols @var{file}
32235 Specify the executable file to be debugged. This file is the one from
32236 which the symbol table is also read. If no file is specified, the
32237 command clears the executable and symbol information. If breakpoints
32238 are set when using this command with no arguments, @value{GDBN} will produce
32239 error messages. Otherwise, no output is produced, except a completion
32242 @subsubheading @value{GDBN} Command
32244 The corresponding @value{GDBN} command is @samp{file}.
32246 @subsubheading Example
32250 -file-exec-and-symbols /kwikemart/marge/ezannoni/TRUNK/mbx/hello.mbx
32256 @subheading The @code{-file-exec-file} Command
32257 @findex -file-exec-file
32259 @subsubheading Synopsis
32262 -file-exec-file @var{file}
32265 Specify the executable file to be debugged. Unlike
32266 @samp{-file-exec-and-symbols}, the symbol table is @emph{not} read
32267 from this file. If used without argument, @value{GDBN} clears the information
32268 about the executable file. No output is produced, except a completion
32271 @subsubheading @value{GDBN} Command
32273 The corresponding @value{GDBN} command is @samp{exec-file}.
32275 @subsubheading Example
32279 -file-exec-file /kwikemart/marge/ezannoni/TRUNK/mbx/hello.mbx
32286 @subheading The @code{-file-list-exec-sections} Command
32287 @findex -file-list-exec-sections
32289 @subsubheading Synopsis
32292 -file-list-exec-sections
32295 List the sections of the current executable file.
32297 @subsubheading @value{GDBN} Command
32299 The @value{GDBN} command @samp{info file} shows, among the rest, the same
32300 information as this command. @code{gdbtk} has a corresponding command
32301 @samp{gdb_load_info}.
32303 @subsubheading Example
32308 @subheading The @code{-file-list-exec-source-file} Command
32309 @findex -file-list-exec-source-file
32311 @subsubheading Synopsis
32314 -file-list-exec-source-file
32317 List the line number, the current source file, and the absolute path
32318 to the current source file for the current executable. The macro
32319 information field has a value of @samp{1} or @samp{0} depending on
32320 whether or not the file includes preprocessor macro information.
32322 @subsubheading @value{GDBN} Command
32324 The @value{GDBN} equivalent is @samp{info source}
32326 @subsubheading Example
32330 123-file-list-exec-source-file
32331 123^done,line="1",file="foo.c",fullname="/home/bar/foo.c,macro-info="1"
32336 @subheading The @code{-file-list-exec-source-files} Command
32337 @findex -file-list-exec-source-files
32339 @subsubheading Synopsis
32342 -file-list-exec-source-files
32345 List the source files for the current executable.
32347 It will always output both the filename and fullname (absolute file
32348 name) of a source file.
32350 @subsubheading @value{GDBN} Command
32352 The @value{GDBN} equivalent is @samp{info sources}.
32353 @code{gdbtk} has an analogous command @samp{gdb_listfiles}.
32355 @subsubheading Example
32358 -file-list-exec-source-files
32360 @{file=foo.c,fullname=/home/foo.c@},
32361 @{file=/home/bar.c,fullname=/home/bar.c@},
32362 @{file=gdb_could_not_find_fullpath.c@}]
32366 @subheading The @code{-file-list-shared-libraries} Command
32367 @findex -file-list-shared-libraries
32369 @subsubheading Synopsis
32372 -file-list-shared-libraries [ @var{regexp} ]
32375 List the shared libraries in the program.
32376 With a regular expression @var{regexp}, only those libraries whose
32377 names match @var{regexp} are listed.
32379 @subsubheading @value{GDBN} Command
32381 The corresponding @value{GDBN} command is @samp{info shared}. The fields
32382 have a similar meaning to the @code{=library-loaded} notification.
32383 The @code{ranges} field specifies the multiple segments belonging to this
32384 library. Each range has the following fields:
32388 The address defining the inclusive lower bound of the segment.
32390 The address defining the exclusive upper bound of the segment.
32393 @subsubheading Example
32396 -file-list-exec-source-files
32397 ^done,shared-libraries=[
32398 @{id="/lib/libfoo.so",target-name="/lib/libfoo.so",host-name="/lib/libfoo.so",symbols-loaded="1",thread-group="i1",ranges=[@{from="0x72815989",to="0x728162c0"@}]@},
32399 @{id="/lib/libbar.so",target-name="/lib/libbar.so",host-name="/lib/libbar.so",symbols-loaded="1",thread-group="i1",ranges=[@{from="0x76ee48c0",to="0x76ee9160"@}]@}]
32405 @subheading The @code{-file-list-symbol-files} Command
32406 @findex -file-list-symbol-files
32408 @subsubheading Synopsis
32411 -file-list-symbol-files
32416 @subsubheading @value{GDBN} Command
32418 The corresponding @value{GDBN} command is @samp{info file} (part of it).
32420 @subsubheading Example
32425 @subheading The @code{-file-symbol-file} Command
32426 @findex -file-symbol-file
32428 @subsubheading Synopsis
32431 -file-symbol-file @var{file}
32434 Read symbol table info from the specified @var{file} argument. When
32435 used without arguments, clears @value{GDBN}'s symbol table info. No output is
32436 produced, except for a completion notification.
32438 @subsubheading @value{GDBN} Command
32440 The corresponding @value{GDBN} command is @samp{symbol-file}.
32442 @subsubheading Example
32446 -file-symbol-file /kwikemart/marge/ezannoni/TRUNK/mbx/hello.mbx
32452 @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
32453 @node GDB/MI Memory Overlay Commands
32454 @section @sc{gdb/mi} Memory Overlay Commands
32456 The memory overlay commands are not implemented.
32458 @c @subheading -overlay-auto
32460 @c @subheading -overlay-list-mapping-state
32462 @c @subheading -overlay-list-overlays
32464 @c @subheading -overlay-map
32466 @c @subheading -overlay-off
32468 @c @subheading -overlay-on
32470 @c @subheading -overlay-unmap
32472 @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
32473 @node GDB/MI Signal Handling Commands
32474 @section @sc{gdb/mi} Signal Handling Commands
32476 Signal handling commands are not implemented.
32478 @c @subheading -signal-handle
32480 @c @subheading -signal-list-handle-actions
32482 @c @subheading -signal-list-signal-types
32486 @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
32487 @node GDB/MI Target Manipulation
32488 @section @sc{gdb/mi} Target Manipulation Commands
32491 @subheading The @code{-target-attach} Command
32492 @findex -target-attach
32494 @subsubheading Synopsis
32497 -target-attach @var{pid} | @var{gid} | @var{file}
32500 Attach to a process @var{pid} or a file @var{file} outside of
32501 @value{GDBN}, or a thread group @var{gid}. If attaching to a thread
32502 group, the id previously returned by
32503 @samp{-list-thread-groups --available} must be used.
32505 @subsubheading @value{GDBN} Command
32507 The corresponding @value{GDBN} command is @samp{attach}.
32509 @subsubheading Example
32513 =thread-created,id="1"
32514 *stopped,thread-id="1",frame=@{addr="0xb7f7e410",func="bar",args=[]@}
32520 @subheading The @code{-target-compare-sections} Command
32521 @findex -target-compare-sections
32523 @subsubheading Synopsis
32526 -target-compare-sections [ @var{section} ]
32529 Compare data of section @var{section} on target to the exec file.
32530 Without the argument, all sections are compared.
32532 @subsubheading @value{GDBN} Command
32534 The @value{GDBN} equivalent is @samp{compare-sections}.
32536 @subsubheading Example
32541 @subheading The @code{-target-detach} Command
32542 @findex -target-detach
32544 @subsubheading Synopsis
32547 -target-detach [ @var{pid} | @var{gid} ]
32550 Detach from the remote target which normally resumes its execution.
32551 If either @var{pid} or @var{gid} is specified, detaches from either
32552 the specified process, or specified thread group. There's no output.
32554 @subsubheading @value{GDBN} Command
32556 The corresponding @value{GDBN} command is @samp{detach}.
32558 @subsubheading Example
32568 @subheading The @code{-target-disconnect} Command
32569 @findex -target-disconnect
32571 @subsubheading Synopsis
32577 Disconnect from the remote target. There's no output and the target is
32578 generally not resumed.
32580 @subsubheading @value{GDBN} Command
32582 The corresponding @value{GDBN} command is @samp{disconnect}.
32584 @subsubheading Example
32594 @subheading The @code{-target-download} Command
32595 @findex -target-download
32597 @subsubheading Synopsis
32603 Loads the executable onto the remote target.
32604 It prints out an update message every half second, which includes the fields:
32608 The name of the section.
32610 The size of what has been sent so far for that section.
32612 The size of the section.
32614 The total size of what was sent so far (the current and the previous sections).
32616 The size of the overall executable to download.
32620 Each message is sent as status record (@pxref{GDB/MI Output Syntax, ,
32621 @sc{gdb/mi} Output Syntax}).
32623 In addition, it prints the name and size of the sections, as they are
32624 downloaded. These messages include the following fields:
32628 The name of the section.
32630 The size of the section.
32632 The size of the overall executable to download.
32636 At the end, a summary is printed.
32638 @subsubheading @value{GDBN} Command
32640 The corresponding @value{GDBN} command is @samp{load}.
32642 @subsubheading Example
32644 Note: each status message appears on a single line. Here the messages
32645 have been broken down so that they can fit onto a page.
32650 +download,@{section=".text",section-size="6668",total-size="9880"@}
32651 +download,@{section=".text",section-sent="512",section-size="6668",
32652 total-sent="512",total-size="9880"@}
32653 +download,@{section=".text",section-sent="1024",section-size="6668",
32654 total-sent="1024",total-size="9880"@}
32655 +download,@{section=".text",section-sent="1536",section-size="6668",
32656 total-sent="1536",total-size="9880"@}
32657 +download,@{section=".text",section-sent="2048",section-size="6668",
32658 total-sent="2048",total-size="9880"@}
32659 +download,@{section=".text",section-sent="2560",section-size="6668",
32660 total-sent="2560",total-size="9880"@}
32661 +download,@{section=".text",section-sent="3072",section-size="6668",
32662 total-sent="3072",total-size="9880"@}
32663 +download,@{section=".text",section-sent="3584",section-size="6668",
32664 total-sent="3584",total-size="9880"@}
32665 +download,@{section=".text",section-sent="4096",section-size="6668",
32666 total-sent="4096",total-size="9880"@}
32667 +download,@{section=".text",section-sent="4608",section-size="6668",
32668 total-sent="4608",total-size="9880"@}
32669 +download,@{section=".text",section-sent="5120",section-size="6668",
32670 total-sent="5120",total-size="9880"@}
32671 +download,@{section=".text",section-sent="5632",section-size="6668",
32672 total-sent="5632",total-size="9880"@}
32673 +download,@{section=".text",section-sent="6144",section-size="6668",
32674 total-sent="6144",total-size="9880"@}
32675 +download,@{section=".text",section-sent="6656",section-size="6668",
32676 total-sent="6656",total-size="9880"@}
32677 +download,@{section=".init",section-size="28",total-size="9880"@}
32678 +download,@{section=".fini",section-size="28",total-size="9880"@}
32679 +download,@{section=".data",section-size="3156",total-size="9880"@}
32680 +download,@{section=".data",section-sent="512",section-size="3156",
32681 total-sent="7236",total-size="9880"@}
32682 +download,@{section=".data",section-sent="1024",section-size="3156",
32683 total-sent="7748",total-size="9880"@}
32684 +download,@{section=".data",section-sent="1536",section-size="3156",
32685 total-sent="8260",total-size="9880"@}
32686 +download,@{section=".data",section-sent="2048",section-size="3156",
32687 total-sent="8772",total-size="9880"@}
32688 +download,@{section=".data",section-sent="2560",section-size="3156",
32689 total-sent="9284",total-size="9880"@}
32690 +download,@{section=".data",section-sent="3072",section-size="3156",
32691 total-sent="9796",total-size="9880"@}
32692 ^done,address="0x10004",load-size="9880",transfer-rate="6586",
32699 @subheading The @code{-target-exec-status} Command
32700 @findex -target-exec-status
32702 @subsubheading Synopsis
32705 -target-exec-status
32708 Provide information on the state of the target (whether it is running or
32709 not, for instance).
32711 @subsubheading @value{GDBN} Command
32713 There's no equivalent @value{GDBN} command.
32715 @subsubheading Example
32719 @subheading The @code{-target-list-available-targets} Command
32720 @findex -target-list-available-targets
32722 @subsubheading Synopsis
32725 -target-list-available-targets
32728 List the possible targets to connect to.
32730 @subsubheading @value{GDBN} Command
32732 The corresponding @value{GDBN} command is @samp{help target}.
32734 @subsubheading Example
32738 @subheading The @code{-target-list-current-targets} Command
32739 @findex -target-list-current-targets
32741 @subsubheading Synopsis
32744 -target-list-current-targets
32747 Describe the current target.
32749 @subsubheading @value{GDBN} Command
32751 The corresponding information is printed by @samp{info file} (among
32754 @subsubheading Example
32758 @subheading The @code{-target-list-parameters} Command
32759 @findex -target-list-parameters
32761 @subsubheading Synopsis
32764 -target-list-parameters
32770 @subsubheading @value{GDBN} Command
32774 @subsubheading Example
32777 @subheading The @code{-target-flash-erase} Command
32778 @findex -target-flash-erase
32780 @subsubheading Synopsis
32783 -target-flash-erase
32786 Erases all known flash memory regions on the target.
32788 The corresponding @value{GDBN} command is @samp{flash-erase}.
32790 The output is a list of flash regions that have been erased, with starting
32791 addresses and memory region sizes.
32795 -target-flash-erase
32796 ^done,erased-regions=@{address="0x0",size="0x40000"@}
32800 @subheading The @code{-target-select} Command
32801 @findex -target-select
32803 @subsubheading Synopsis
32806 -target-select @var{type} @var{parameters @dots{}}
32809 Connect @value{GDBN} to the remote target. This command takes two args:
32813 The type of target, for instance @samp{remote}, etc.
32814 @item @var{parameters}
32815 Device names, host names and the like. @xref{Target Commands, ,
32816 Commands for Managing Targets}, for more details.
32819 The output is a connection notification, followed by the address at
32820 which the target program is, in the following form:
32823 ^connected,addr="@var{address}",func="@var{function name}",
32824 args=[@var{arg list}]
32827 @subsubheading @value{GDBN} Command
32829 The corresponding @value{GDBN} command is @samp{target}.
32831 @subsubheading Example
32835 -target-select remote /dev/ttya
32836 ^connected,addr="0xfe00a300",func="??",args=[]
32840 @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
32841 @node GDB/MI File Transfer Commands
32842 @section @sc{gdb/mi} File Transfer Commands
32845 @subheading The @code{-target-file-put} Command
32846 @findex -target-file-put
32848 @subsubheading Synopsis
32851 -target-file-put @var{hostfile} @var{targetfile}
32854 Copy file @var{hostfile} from the host system (the machine running
32855 @value{GDBN}) to @var{targetfile} on the target system.
32857 @subsubheading @value{GDBN} Command
32859 The corresponding @value{GDBN} command is @samp{remote put}.
32861 @subsubheading Example
32865 -target-file-put localfile remotefile
32871 @subheading The @code{-target-file-get} Command
32872 @findex -target-file-get
32874 @subsubheading Synopsis
32877 -target-file-get @var{targetfile} @var{hostfile}
32880 Copy file @var{targetfile} from the target system to @var{hostfile}
32881 on the host system.
32883 @subsubheading @value{GDBN} Command
32885 The corresponding @value{GDBN} command is @samp{remote get}.
32887 @subsubheading Example
32891 -target-file-get remotefile localfile
32897 @subheading The @code{-target-file-delete} Command
32898 @findex -target-file-delete
32900 @subsubheading Synopsis
32903 -target-file-delete @var{targetfile}
32906 Delete @var{targetfile} from the target system.
32908 @subsubheading @value{GDBN} Command
32910 The corresponding @value{GDBN} command is @samp{remote delete}.
32912 @subsubheading Example
32916 -target-file-delete remotefile
32922 @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
32923 @node GDB/MI Ada Exceptions Commands
32924 @section Ada Exceptions @sc{gdb/mi} Commands
32926 @subheading The @code{-info-ada-exceptions} Command
32927 @findex -info-ada-exceptions
32929 @subsubheading Synopsis
32932 -info-ada-exceptions [ @var{regexp}]
32935 List all Ada exceptions defined within the program being debugged.
32936 With a regular expression @var{regexp}, only those exceptions whose
32937 names match @var{regexp} are listed.
32939 @subsubheading @value{GDBN} Command
32941 The corresponding @value{GDBN} command is @samp{info exceptions}.
32943 @subsubheading Result
32945 The result is a table of Ada exceptions. The following columns are
32946 defined for each exception:
32950 The name of the exception.
32953 The address of the exception.
32957 @subsubheading Example
32960 -info-ada-exceptions aint
32961 ^done,ada-exceptions=@{nr_rows="2",nr_cols="2",
32962 hdr=[@{width="1",alignment="-1",col_name="name",colhdr="Name"@},
32963 @{width="1",alignment="-1",col_name="address",colhdr="Address"@}],
32964 body=[@{name="constraint_error",address="0x0000000000613da0"@},
32965 @{name="const.aint_global_e",address="0x0000000000613b00"@}]@}
32968 @subheading Catching Ada Exceptions
32970 The commands describing how to ask @value{GDBN} to stop when a program
32971 raises an exception are described at @ref{Ada Exception GDB/MI
32972 Catchpoint Commands}.
32975 @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
32976 @node GDB/MI Support Commands
32977 @section @sc{gdb/mi} Support Commands
32979 Since new commands and features get regularly added to @sc{gdb/mi},
32980 some commands are available to help front-ends query the debugger
32981 about support for these capabilities. Similarly, it is also possible
32982 to query @value{GDBN} about target support of certain features.
32984 @subheading The @code{-info-gdb-mi-command} Command
32985 @cindex @code{-info-gdb-mi-command}
32986 @findex -info-gdb-mi-command
32988 @subsubheading Synopsis
32991 -info-gdb-mi-command @var{cmd_name}
32994 Query support for the @sc{gdb/mi} command named @var{cmd_name}.
32996 Note that the dash (@code{-}) starting all @sc{gdb/mi} commands
32997 is technically not part of the command name (@pxref{GDB/MI Input
32998 Syntax}), and thus should be omitted in @var{cmd_name}. However,
32999 for ease of use, this command also accepts the form with the leading
33002 @subsubheading @value{GDBN} Command
33004 There is no corresponding @value{GDBN} command.
33006 @subsubheading Result
33008 The result is a tuple. There is currently only one field:
33012 This field is equal to @code{"true"} if the @sc{gdb/mi} command exists,
33013 @code{"false"} otherwise.
33017 @subsubheading Example
33019 Here is an example where the @sc{gdb/mi} command does not exist:
33022 -info-gdb-mi-command unsupported-command
33023 ^done,command=@{exists="false"@}
33027 And here is an example where the @sc{gdb/mi} command is known
33031 -info-gdb-mi-command symbol-list-lines
33032 ^done,command=@{exists="true"@}
33035 @subheading The @code{-list-features} Command
33036 @findex -list-features
33037 @cindex supported @sc{gdb/mi} features, list
33039 Returns a list of particular features of the MI protocol that
33040 this version of gdb implements. A feature can be a command,
33041 or a new field in an output of some command, or even an
33042 important bugfix. While a frontend can sometimes detect presence
33043 of a feature at runtime, it is easier to perform detection at debugger
33046 The command returns a list of strings, with each string naming an
33047 available feature. Each returned string is just a name, it does not
33048 have any internal structure. The list of possible feature names
33054 (gdb) -list-features
33055 ^done,result=["feature1","feature2"]
33058 The current list of features is:
33061 @item frozen-varobjs
33062 Indicates support for the @code{-var-set-frozen} command, as well
33063 as possible presense of the @code{frozen} field in the output
33064 of @code{-varobj-create}.
33065 @item pending-breakpoints
33066 Indicates support for the @option{-f} option to the @code{-break-insert}
33069 Indicates Python scripting support, Python-based
33070 pretty-printing commands, and possible presence of the
33071 @samp{display_hint} field in the output of @code{-var-list-children}
33073 Indicates support for the @code{-thread-info} command.
33074 @item data-read-memory-bytes
33075 Indicates support for the @code{-data-read-memory-bytes} and the
33076 @code{-data-write-memory-bytes} commands.
33077 @item breakpoint-notifications
33078 Indicates that changes to breakpoints and breakpoints created via the
33079 CLI will be announced via async records.
33080 @item ada-task-info
33081 Indicates support for the @code{-ada-task-info} command.
33082 @item language-option
33083 Indicates that all @sc{gdb/mi} commands accept the @option{--language}
33084 option (@pxref{Context management}).
33085 @item info-gdb-mi-command
33086 Indicates support for the @code{-info-gdb-mi-command} command.
33087 @item undefined-command-error-code
33088 Indicates support for the "undefined-command" error code in error result
33089 records, produced when trying to execute an undefined @sc{gdb/mi} command
33090 (@pxref{GDB/MI Result Records}).
33091 @item exec-run-start-option
33092 Indicates that the @code{-exec-run} command supports the @option{--start}
33093 option (@pxref{GDB/MI Program Execution}).
33096 @subheading The @code{-list-target-features} Command
33097 @findex -list-target-features
33099 Returns a list of particular features that are supported by the
33100 target. Those features affect the permitted MI commands, but
33101 unlike the features reported by the @code{-list-features} command, the
33102 features depend on which target GDB is using at the moment. Whenever
33103 a target can change, due to commands such as @code{-target-select},
33104 @code{-target-attach} or @code{-exec-run}, the list of target features
33105 may change, and the frontend should obtain it again.
33109 (gdb) -list-target-features
33110 ^done,result=["async"]
33113 The current list of features is:
33117 Indicates that the target is capable of asynchronous command
33118 execution, which means that @value{GDBN} will accept further commands
33119 while the target is running.
33122 Indicates that the target is capable of reverse execution.
33123 @xref{Reverse Execution}, for more information.
33127 @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
33128 @node GDB/MI Miscellaneous Commands
33129 @section Miscellaneous @sc{gdb/mi} Commands
33131 @c @subheading -gdb-complete
33133 @subheading The @code{-gdb-exit} Command
33136 @subsubheading Synopsis
33142 Exit @value{GDBN} immediately.
33144 @subsubheading @value{GDBN} Command
33146 Approximately corresponds to @samp{quit}.
33148 @subsubheading Example
33158 @subheading The @code{-exec-abort} Command
33159 @findex -exec-abort
33161 @subsubheading Synopsis
33167 Kill the inferior running program.
33169 @subsubheading @value{GDBN} Command
33171 The corresponding @value{GDBN} command is @samp{kill}.
33173 @subsubheading Example
33178 @subheading The @code{-gdb-set} Command
33181 @subsubheading Synopsis
33187 Set an internal @value{GDBN} variable.
33188 @c IS THIS A DOLLAR VARIABLE? OR SOMETHING LIKE ANNOTATE ?????
33190 @subsubheading @value{GDBN} Command
33192 The corresponding @value{GDBN} command is @samp{set}.
33194 @subsubheading Example
33204 @subheading The @code{-gdb-show} Command
33207 @subsubheading Synopsis
33213 Show the current value of a @value{GDBN} variable.
33215 @subsubheading @value{GDBN} Command
33217 The corresponding @value{GDBN} command is @samp{show}.
33219 @subsubheading Example
33228 @c @subheading -gdb-source
33231 @subheading The @code{-gdb-version} Command
33232 @findex -gdb-version
33234 @subsubheading Synopsis
33240 Show version information for @value{GDBN}. Used mostly in testing.
33242 @subsubheading @value{GDBN} Command
33244 The @value{GDBN} equivalent is @samp{show version}. @value{GDBN} by
33245 default shows this information when you start an interactive session.
33247 @subsubheading Example
33249 @c This example modifies the actual output from GDB to avoid overfull
33255 ~Copyright 2000 Free Software Foundation, Inc.
33256 ~GDB is free software, covered by the GNU General Public License, and
33257 ~you are welcome to change it and/or distribute copies of it under
33258 ~ certain conditions.
33259 ~Type "show copying" to see the conditions.
33260 ~There is absolutely no warranty for GDB. Type "show warranty" for
33262 ~This GDB was configured as
33263 "--host=sparc-sun-solaris2.5.1 --target=ppc-eabi".
33268 @subheading The @code{-list-thread-groups} Command
33269 @findex -list-thread-groups
33271 @subheading Synopsis
33274 -list-thread-groups [ --available ] [ --recurse 1 ] [ @var{group} ... ]
33277 Lists thread groups (@pxref{Thread groups}). When a single thread
33278 group is passed as the argument, lists the children of that group.
33279 When several thread group are passed, lists information about those
33280 thread groups. Without any parameters, lists information about all
33281 top-level thread groups.
33283 Normally, thread groups that are being debugged are reported.
33284 With the @samp{--available} option, @value{GDBN} reports thread groups
33285 available on the target.
33287 The output of this command may have either a @samp{threads} result or
33288 a @samp{groups} result. The @samp{thread} result has a list of tuples
33289 as value, with each tuple describing a thread (@pxref{GDB/MI Thread
33290 Information}). The @samp{groups} result has a list of tuples as value,
33291 each tuple describing a thread group. If top-level groups are
33292 requested (that is, no parameter is passed), or when several groups
33293 are passed, the output always has a @samp{groups} result. The format
33294 of the @samp{group} result is described below.
33296 To reduce the number of roundtrips it's possible to list thread groups
33297 together with their children, by passing the @samp{--recurse} option
33298 and the recursion depth. Presently, only recursion depth of 1 is
33299 permitted. If this option is present, then every reported thread group
33300 will also include its children, either as @samp{group} or
33301 @samp{threads} field.
33303 In general, any combination of option and parameters is permitted, with
33304 the following caveats:
33308 When a single thread group is passed, the output will typically
33309 be the @samp{threads} result. Because threads may not contain
33310 anything, the @samp{recurse} option will be ignored.
33313 When the @samp{--available} option is passed, limited information may
33314 be available. In particular, the list of threads of a process might
33315 be inaccessible. Further, specifying specific thread groups might
33316 not give any performance advantage over listing all thread groups.
33317 The frontend should assume that @samp{-list-thread-groups --available}
33318 is always an expensive operation and cache the results.
33322 The @samp{groups} result is a list of tuples, where each tuple may
33323 have the following fields:
33327 Identifier of the thread group. This field is always present.
33328 The identifier is an opaque string; frontends should not try to
33329 convert it to an integer, even though it might look like one.
33332 The type of the thread group. At present, only @samp{process} is a
33336 The target-specific process identifier. This field is only present
33337 for thread groups of type @samp{process} and only if the process exists.
33340 The exit code of this group's last exited thread, formatted in octal.
33341 This field is only present for thread groups of type @samp{process} and
33342 only if the process is not running.
33345 The number of children this thread group has. This field may be
33346 absent for an available thread group.
33349 This field has a list of tuples as value, each tuple describing a
33350 thread. It may be present if the @samp{--recurse} option is
33351 specified, and it's actually possible to obtain the threads.
33354 This field is a list of integers, each identifying a core that one
33355 thread of the group is running on. This field may be absent if
33356 such information is not available.
33359 The name of the executable file that corresponds to this thread group.
33360 The field is only present for thread groups of type @samp{process},
33361 and only if there is a corresponding executable file.
33365 @subheading Example
33369 -list-thread-groups
33370 ^done,groups=[@{id="17",type="process",pid="yyy",num_children="2"@}]
33371 -list-thread-groups 17
33372 ^done,threads=[@{id="2",target-id="Thread 0xb7e14b90 (LWP 21257)",
33373 frame=@{level="0",addr="0xffffe410",func="__kernel_vsyscall",args=[]@},state="running"@},
33374 @{id="1",target-id="Thread 0xb7e156b0 (LWP 21254)",
33375 frame=@{level="0",addr="0x0804891f",func="foo",args=[@{name="i",value="10"@}],
33376 file="/tmp/a.c",fullname="/tmp/a.c",line="158"@},state="running"@}]]
33377 -list-thread-groups --available
33378 ^done,groups=[@{id="17",type="process",pid="yyy",num_children="2",cores=[1,2]@}]
33379 -list-thread-groups --available --recurse 1
33380 ^done,groups=[@{id="17", types="process",pid="yyy",num_children="2",cores=[1,2],
33381 threads=[@{id="1",target-id="Thread 0xb7e14b90",cores=[1]@},
33382 @{id="2",target-id="Thread 0xb7e14b90",cores=[2]@}]@},..]
33383 -list-thread-groups --available --recurse 1 17 18
33384 ^done,groups=[@{id="17", types="process",pid="yyy",num_children="2",cores=[1,2],
33385 threads=[@{id="1",target-id="Thread 0xb7e14b90",cores=[1]@},
33386 @{id="2",target-id="Thread 0xb7e14b90",cores=[2]@}]@},...]
33389 @subheading The @code{-info-os} Command
33392 @subsubheading Synopsis
33395 -info-os [ @var{type} ]
33398 If no argument is supplied, the command returns a table of available
33399 operating-system-specific information types. If one of these types is
33400 supplied as an argument @var{type}, then the command returns a table
33401 of data of that type.
33403 The types of information available depend on the target operating
33406 @subsubheading @value{GDBN} Command
33408 The corresponding @value{GDBN} command is @samp{info os}.
33410 @subsubheading Example
33412 When run on a @sc{gnu}/Linux system, the output will look something
33418 ^done,OSDataTable=@{nr_rows="10",nr_cols="3",
33419 hdr=[@{width="10",alignment="-1",col_name="col0",colhdr="Type"@},
33420 @{width="10",alignment="-1",col_name="col1",colhdr="Description"@},
33421 @{width="10",alignment="-1",col_name="col2",colhdr="Title"@}],
33422 body=[item=@{col0="cpus",col1="Listing of all cpus/cores on the system",
33424 item=@{col0="files",col1="Listing of all file descriptors",
33425 col2="File descriptors"@},
33426 item=@{col0="modules",col1="Listing of all loaded kernel modules",
33427 col2="Kernel modules"@},
33428 item=@{col0="msg",col1="Listing of all message queues",
33429 col2="Message queues"@},
33430 item=@{col0="processes",col1="Listing of all processes",
33431 col2="Processes"@},
33432 item=@{col0="procgroups",col1="Listing of all process groups",
33433 col2="Process groups"@},
33434 item=@{col0="semaphores",col1="Listing of all semaphores",
33435 col2="Semaphores"@},
33436 item=@{col0="shm",col1="Listing of all shared-memory regions",
33437 col2="Shared-memory regions"@},
33438 item=@{col0="sockets",col1="Listing of all internet-domain sockets",
33440 item=@{col0="threads",col1="Listing of all threads",
33444 ^done,OSDataTable=@{nr_rows="190",nr_cols="4",
33445 hdr=[@{width="10",alignment="-1",col_name="col0",colhdr="pid"@},
33446 @{width="10",alignment="-1",col_name="col1",colhdr="user"@},
33447 @{width="10",alignment="-1",col_name="col2",colhdr="command"@},
33448 @{width="10",alignment="-1",col_name="col3",colhdr="cores"@}],
33449 body=[item=@{col0="1",col1="root",col2="/sbin/init",col3="0"@},
33450 item=@{col0="2",col1="root",col2="[kthreadd]",col3="1"@},
33451 item=@{col0="3",col1="root",col2="[ksoftirqd/0]",col3="0"@},
33453 item=@{col0="26446",col1="stan",col2="bash",col3="0"@},
33454 item=@{col0="28152",col1="stan",col2="bash",col3="1"@}]@}
33458 (Note that the MI output here includes a @code{"Title"} column that
33459 does not appear in command-line @code{info os}; this column is useful
33460 for MI clients that want to enumerate the types of data, such as in a
33461 popup menu, but is needless clutter on the command line, and
33462 @code{info os} omits it.)
33464 @subheading The @code{-add-inferior} Command
33465 @findex -add-inferior
33467 @subheading Synopsis
33473 Creates a new inferior (@pxref{Inferiors and Programs}). The created
33474 inferior is not associated with any executable. Such association may
33475 be established with the @samp{-file-exec-and-symbols} command
33476 (@pxref{GDB/MI File Commands}). The command response has a single
33477 field, @samp{inferior}, whose value is the identifier of the
33478 thread group corresponding to the new inferior.
33480 @subheading Example
33485 ^done,inferior="i3"
33488 @subheading The @code{-interpreter-exec} Command
33489 @findex -interpreter-exec
33491 @subheading Synopsis
33494 -interpreter-exec @var{interpreter} @var{command}
33496 @anchor{-interpreter-exec}
33498 Execute the specified @var{command} in the given @var{interpreter}.
33500 @subheading @value{GDBN} Command
33502 The corresponding @value{GDBN} command is @samp{interpreter-exec}.
33504 @subheading Example
33508 -interpreter-exec console "break main"
33509 &"During symbol reading, couldn't parse type; debugger out of date?.\n"
33510 &"During symbol reading, bad structure-type format.\n"
33511 ~"Breakpoint 1 at 0x8074fc6: file ../../src/gdb/main.c, line 743.\n"
33516 @subheading The @code{-inferior-tty-set} Command
33517 @findex -inferior-tty-set
33519 @subheading Synopsis
33522 -inferior-tty-set /dev/pts/1
33525 Set terminal for future runs of the program being debugged.
33527 @subheading @value{GDBN} Command
33529 The corresponding @value{GDBN} command is @samp{set inferior-tty} /dev/pts/1.
33531 @subheading Example
33535 -inferior-tty-set /dev/pts/1
33540 @subheading The @code{-inferior-tty-show} Command
33541 @findex -inferior-tty-show
33543 @subheading Synopsis
33549 Show terminal for future runs of program being debugged.
33551 @subheading @value{GDBN} Command
33553 The corresponding @value{GDBN} command is @samp{show inferior-tty}.
33555 @subheading Example
33559 -inferior-tty-set /dev/pts/1
33563 ^done,inferior_tty_terminal="/dev/pts/1"
33567 @subheading The @code{-enable-timings} Command
33568 @findex -enable-timings
33570 @subheading Synopsis
33573 -enable-timings [yes | no]
33576 Toggle the printing of the wallclock, user and system times for an MI
33577 command as a field in its output. This command is to help frontend
33578 developers optimize the performance of their code. No argument is
33579 equivalent to @samp{yes}.
33581 @subheading @value{GDBN} Command
33585 @subheading Example
33593 ^done,bkpt=@{number="1",type="breakpoint",disp="keep",enabled="y",
33594 addr="0x080484ed",func="main",file="myprog.c",
33595 fullname="/home/nickrob/myprog.c",line="73",thread-groups=["i1"],
33597 time=@{wallclock="0.05185",user="0.00800",system="0.00000"@}
33605 *stopped,reason="breakpoint-hit",disp="keep",bkptno="1",thread-id="0",
33606 frame=@{addr="0x080484ed",func="main",args=[@{name="argc",value="1"@},
33607 @{name="argv",value="0xbfb60364"@}],file="myprog.c",
33608 fullname="/home/nickrob/myprog.c",line="73"@}
33613 @chapter @value{GDBN} Annotations
33615 This chapter describes annotations in @value{GDBN}. Annotations were
33616 designed to interface @value{GDBN} to graphical user interfaces or other
33617 similar programs which want to interact with @value{GDBN} at a
33618 relatively high level.
33620 The annotation mechanism has largely been superseded by @sc{gdb/mi}
33624 This is Edition @value{EDITION}, @value{DATE}.
33628 * Annotations Overview:: What annotations are; the general syntax.
33629 * Server Prefix:: Issuing a command without affecting user state.
33630 * Prompting:: Annotations marking @value{GDBN}'s need for input.
33631 * Errors:: Annotations for error messages.
33632 * Invalidation:: Some annotations describe things now invalid.
33633 * Annotations for Running::
33634 Whether the program is running, how it stopped, etc.
33635 * Source Annotations:: Annotations describing source code.
33638 @node Annotations Overview
33639 @section What is an Annotation?
33640 @cindex annotations
33642 Annotations start with a newline character, two @samp{control-z}
33643 characters, and the name of the annotation. If there is no additional
33644 information associated with this annotation, the name of the annotation
33645 is followed immediately by a newline. If there is additional
33646 information, the name of the annotation is followed by a space, the
33647 additional information, and a newline. The additional information
33648 cannot contain newline characters.
33650 Any output not beginning with a newline and two @samp{control-z}
33651 characters denotes literal output from @value{GDBN}. Currently there is
33652 no need for @value{GDBN} to output a newline followed by two
33653 @samp{control-z} characters, but if there was such a need, the
33654 annotations could be extended with an @samp{escape} annotation which
33655 means those three characters as output.
33657 The annotation @var{level}, which is specified using the
33658 @option{--annotate} command line option (@pxref{Mode Options}), controls
33659 how much information @value{GDBN} prints together with its prompt,
33660 values of expressions, source lines, and other types of output. Level 0
33661 is for no annotations, level 1 is for use when @value{GDBN} is run as a
33662 subprocess of @sc{gnu} Emacs, level 3 is the maximum annotation suitable
33663 for programs that control @value{GDBN}, and level 2 annotations have
33664 been made obsolete (@pxref{Limitations, , Limitations of the Annotation
33665 Interface, annotate, GDB's Obsolete Annotations}).
33668 @kindex set annotate
33669 @item set annotate @var{level}
33670 The @value{GDBN} command @code{set annotate} sets the level of
33671 annotations to the specified @var{level}.
33673 @item show annotate
33674 @kindex show annotate
33675 Show the current annotation level.
33678 This chapter describes level 3 annotations.
33680 A simple example of starting up @value{GDBN} with annotations is:
33683 $ @kbd{gdb --annotate=3}
33685 Copyright 2003 Free Software Foundation, Inc.
33686 GDB is free software, covered by the GNU General Public License,
33687 and you are welcome to change it and/or distribute copies of it
33688 under certain conditions.
33689 Type "show copying" to see the conditions.
33690 There is absolutely no warranty for GDB. Type "show warranty"
33692 This GDB was configured as "i386-pc-linux-gnu"
33703 Here @samp{quit} is input to @value{GDBN}; the rest is output from
33704 @value{GDBN}. The three lines beginning @samp{^Z^Z} (where @samp{^Z}
33705 denotes a @samp{control-z} character) are annotations; the rest is
33706 output from @value{GDBN}.
33708 @node Server Prefix
33709 @section The Server Prefix
33710 @cindex server prefix
33712 If you prefix a command with @samp{server } then it will not affect
33713 the command history, nor will it affect @value{GDBN}'s notion of which
33714 command to repeat if @key{RET} is pressed on a line by itself. This
33715 means that commands can be run behind a user's back by a front-end in
33716 a transparent manner.
33718 The @code{server } prefix does not affect the recording of values into
33719 the value history; to print a value without recording it into the
33720 value history, use the @code{output} command instead of the
33721 @code{print} command.
33723 Using this prefix also disables confirmation requests
33724 (@pxref{confirmation requests}).
33727 @section Annotation for @value{GDBN} Input
33729 @cindex annotations for prompts
33730 When @value{GDBN} prompts for input, it annotates this fact so it is possible
33731 to know when to send output, when the output from a given command is
33734 Different kinds of input each have a different @dfn{input type}. Each
33735 input type has three annotations: a @code{pre-} annotation, which
33736 denotes the beginning of any prompt which is being output, a plain
33737 annotation, which denotes the end of the prompt, and then a @code{post-}
33738 annotation which denotes the end of any echo which may (or may not) be
33739 associated with the input. For example, the @code{prompt} input type
33740 features the following annotations:
33748 The input types are
33751 @findex pre-prompt annotation
33752 @findex prompt annotation
33753 @findex post-prompt annotation
33755 When @value{GDBN} is prompting for a command (the main @value{GDBN} prompt).
33757 @findex pre-commands annotation
33758 @findex commands annotation
33759 @findex post-commands annotation
33761 When @value{GDBN} prompts for a set of commands, like in the @code{commands}
33762 command. The annotations are repeated for each command which is input.
33764 @findex pre-overload-choice annotation
33765 @findex overload-choice annotation
33766 @findex post-overload-choice annotation
33767 @item overload-choice
33768 When @value{GDBN} wants the user to select between various overloaded functions.
33770 @findex pre-query annotation
33771 @findex query annotation
33772 @findex post-query annotation
33774 When @value{GDBN} wants the user to confirm a potentially dangerous operation.
33776 @findex pre-prompt-for-continue annotation
33777 @findex prompt-for-continue annotation
33778 @findex post-prompt-for-continue annotation
33779 @item prompt-for-continue
33780 When @value{GDBN} is asking the user to press return to continue. Note: Don't
33781 expect this to work well; instead use @code{set height 0} to disable
33782 prompting. This is because the counting of lines is buggy in the
33783 presence of annotations.
33788 @cindex annotations for errors, warnings and interrupts
33790 @findex quit annotation
33795 This annotation occurs right before @value{GDBN} responds to an interrupt.
33797 @findex error annotation
33802 This annotation occurs right before @value{GDBN} responds to an error.
33804 Quit and error annotations indicate that any annotations which @value{GDBN} was
33805 in the middle of may end abruptly. For example, if a
33806 @code{value-history-begin} annotation is followed by a @code{error}, one
33807 cannot expect to receive the matching @code{value-history-end}. One
33808 cannot expect not to receive it either, however; an error annotation
33809 does not necessarily mean that @value{GDBN} is immediately returning all the way
33812 @findex error-begin annotation
33813 A quit or error annotation may be preceded by
33819 Any output between that and the quit or error annotation is the error
33822 Warning messages are not yet annotated.
33823 @c If we want to change that, need to fix warning(), type_error(),
33824 @c range_error(), and possibly other places.
33827 @section Invalidation Notices
33829 @cindex annotations for invalidation messages
33830 The following annotations say that certain pieces of state may have
33834 @findex frames-invalid annotation
33835 @item ^Z^Zframes-invalid
33837 The frames (for example, output from the @code{backtrace} command) may
33840 @findex breakpoints-invalid annotation
33841 @item ^Z^Zbreakpoints-invalid
33843 The breakpoints may have changed. For example, the user just added or
33844 deleted a breakpoint.
33847 @node Annotations for Running
33848 @section Running the Program
33849 @cindex annotations for running programs
33851 @findex starting annotation
33852 @findex stopping annotation
33853 When the program starts executing due to a @value{GDBN} command such as
33854 @code{step} or @code{continue},
33860 is output. When the program stops,
33866 is output. Before the @code{stopped} annotation, a variety of
33867 annotations describe how the program stopped.
33870 @findex exited annotation
33871 @item ^Z^Zexited @var{exit-status}
33872 The program exited, and @var{exit-status} is the exit status (zero for
33873 successful exit, otherwise nonzero).
33875 @findex signalled annotation
33876 @findex signal-name annotation
33877 @findex signal-name-end annotation
33878 @findex signal-string annotation
33879 @findex signal-string-end annotation
33880 @item ^Z^Zsignalled
33881 The program exited with a signal. After the @code{^Z^Zsignalled}, the
33882 annotation continues:
33888 ^Z^Zsignal-name-end
33892 ^Z^Zsignal-string-end
33897 where @var{name} is the name of the signal, such as @code{SIGILL} or
33898 @code{SIGSEGV}, and @var{string} is the explanation of the signal, such
33899 as @code{Illegal Instruction} or @code{Segmentation fault}. The arguments
33900 @var{intro-text}, @var{middle-text}, and @var{end-text} are for the
33901 user's benefit and have no particular format.
33903 @findex signal annotation
33905 The syntax of this annotation is just like @code{signalled}, but @value{GDBN} is
33906 just saying that the program received the signal, not that it was
33907 terminated with it.
33909 @findex breakpoint annotation
33910 @item ^Z^Zbreakpoint @var{number}
33911 The program hit breakpoint number @var{number}.
33913 @findex watchpoint annotation
33914 @item ^Z^Zwatchpoint @var{number}
33915 The program hit watchpoint number @var{number}.
33918 @node Source Annotations
33919 @section Displaying Source
33920 @cindex annotations for source display
33922 @findex source annotation
33923 The following annotation is used instead of displaying source code:
33926 ^Z^Zsource @var{filename}:@var{line}:@var{character}:@var{middle}:@var{addr}
33929 where @var{filename} is an absolute file name indicating which source
33930 file, @var{line} is the line number within that file (where 1 is the
33931 first line in the file), @var{character} is the character position
33932 within the file (where 0 is the first character in the file) (for most
33933 debug formats this will necessarily point to the beginning of a line),
33934 @var{middle} is @samp{middle} if @var{addr} is in the middle of the
33935 line, or @samp{beg} if @var{addr} is at the beginning of the line, and
33936 @var{addr} is the address in the target program associated with the
33937 source which is being displayed. The @var{addr} is in the form @samp{0x}
33938 followed by one or more lowercase hex digits (note that this does not
33939 depend on the language).
33941 @node JIT Interface
33942 @chapter JIT Compilation Interface
33943 @cindex just-in-time compilation
33944 @cindex JIT compilation interface
33946 This chapter documents @value{GDBN}'s @dfn{just-in-time} (JIT) compilation
33947 interface. A JIT compiler is a program or library that generates native
33948 executable code at runtime and executes it, usually in order to achieve good
33949 performance while maintaining platform independence.
33951 Programs that use JIT compilation are normally difficult to debug because
33952 portions of their code are generated at runtime, instead of being loaded from
33953 object files, which is where @value{GDBN} normally finds the program's symbols
33954 and debug information. In order to debug programs that use JIT compilation,
33955 @value{GDBN} has an interface that allows the program to register in-memory
33956 symbol files with @value{GDBN} at runtime.
33958 If you are using @value{GDBN} to debug a program that uses this interface, then
33959 it should work transparently so long as you have not stripped the binary. If
33960 you are developing a JIT compiler, then the interface is documented in the rest
33961 of this chapter. At this time, the only known client of this interface is the
33964 Broadly speaking, the JIT interface mirrors the dynamic loader interface. The
33965 JIT compiler communicates with @value{GDBN} by writing data into a global
33966 variable and calling a fuction at a well-known symbol. When @value{GDBN}
33967 attaches, it reads a linked list of symbol files from the global variable to
33968 find existing code, and puts a breakpoint in the function so that it can find
33969 out about additional code.
33972 * Declarations:: Relevant C struct declarations
33973 * Registering Code:: Steps to register code
33974 * Unregistering Code:: Steps to unregister code
33975 * Custom Debug Info:: Emit debug information in a custom format
33979 @section JIT Declarations
33981 These are the relevant struct declarations that a C program should include to
33982 implement the interface:
33992 struct jit_code_entry
33994 struct jit_code_entry *next_entry;
33995 struct jit_code_entry *prev_entry;
33996 const char *symfile_addr;
33997 uint64_t symfile_size;
34000 struct jit_descriptor
34003 /* This type should be jit_actions_t, but we use uint32_t
34004 to be explicit about the bitwidth. */
34005 uint32_t action_flag;
34006 struct jit_code_entry *relevant_entry;
34007 struct jit_code_entry *first_entry;
34010 /* GDB puts a breakpoint in this function. */
34011 void __attribute__((noinline)) __jit_debug_register_code() @{ @};
34013 /* Make sure to specify the version statically, because the
34014 debugger may check the version before we can set it. */
34015 struct jit_descriptor __jit_debug_descriptor = @{ 1, 0, 0, 0 @};
34018 If the JIT is multi-threaded, then it is important that the JIT synchronize any
34019 modifications to this global data properly, which can easily be done by putting
34020 a global mutex around modifications to these structures.
34022 @node Registering Code
34023 @section Registering Code
34025 To register code with @value{GDBN}, the JIT should follow this protocol:
34029 Generate an object file in memory with symbols and other desired debug
34030 information. The file must include the virtual addresses of the sections.
34033 Create a code entry for the file, which gives the start and size of the symbol
34037 Add it to the linked list in the JIT descriptor.
34040 Point the relevant_entry field of the descriptor at the entry.
34043 Set @code{action_flag} to @code{JIT_REGISTER} and call
34044 @code{__jit_debug_register_code}.
34047 When @value{GDBN} is attached and the breakpoint fires, @value{GDBN} uses the
34048 @code{relevant_entry} pointer so it doesn't have to walk the list looking for
34049 new code. However, the linked list must still be maintained in order to allow
34050 @value{GDBN} to attach to a running process and still find the symbol files.
34052 @node Unregistering Code
34053 @section Unregistering Code
34055 If code is freed, then the JIT should use the following protocol:
34059 Remove the code entry corresponding to the code from the linked list.
34062 Point the @code{relevant_entry} field of the descriptor at the code entry.
34065 Set @code{action_flag} to @code{JIT_UNREGISTER} and call
34066 @code{__jit_debug_register_code}.
34069 If the JIT frees or recompiles code without unregistering it, then @value{GDBN}
34070 and the JIT will leak the memory used for the associated symbol files.
34072 @node Custom Debug Info
34073 @section Custom Debug Info
34074 @cindex custom JIT debug info
34075 @cindex JIT debug info reader
34077 Generating debug information in platform-native file formats (like ELF
34078 or COFF) may be an overkill for JIT compilers; especially if all the
34079 debug info is used for is displaying a meaningful backtrace. The
34080 issue can be resolved by having the JIT writers decide on a debug info
34081 format and also provide a reader that parses the debug info generated
34082 by the JIT compiler. This section gives a brief overview on writing
34083 such a parser. More specific details can be found in the source file
34084 @file{gdb/jit-reader.in}, which is also installed as a header at
34085 @file{@var{includedir}/gdb/jit-reader.h} for easy inclusion.
34087 The reader is implemented as a shared object (so this functionality is
34088 not available on platforms which don't allow loading shared objects at
34089 runtime). Two @value{GDBN} commands, @code{jit-reader-load} and
34090 @code{jit-reader-unload} are provided, to be used to load and unload
34091 the readers from a preconfigured directory. Once loaded, the shared
34092 object is used the parse the debug information emitted by the JIT
34096 * Using JIT Debug Info Readers:: How to use supplied readers correctly
34097 * Writing JIT Debug Info Readers:: Creating a debug-info reader
34100 @node Using JIT Debug Info Readers
34101 @subsection Using JIT Debug Info Readers
34102 @kindex jit-reader-load
34103 @kindex jit-reader-unload
34105 Readers can be loaded and unloaded using the @code{jit-reader-load}
34106 and @code{jit-reader-unload} commands.
34109 @item jit-reader-load @var{reader}
34110 Load the JIT reader named @var{reader}, which is a shared
34111 object specified as either an absolute or a relative file name. In
34112 the latter case, @value{GDBN} will try to load the reader from a
34113 pre-configured directory, usually @file{@var{libdir}/gdb/} on a UNIX
34114 system (here @var{libdir} is the system library directory, often
34115 @file{/usr/local/lib}).
34117 Only one reader can be active at a time; trying to load a second
34118 reader when one is already loaded will result in @value{GDBN}
34119 reporting an error. A new JIT reader can be loaded by first unloading
34120 the current one using @code{jit-reader-unload} and then invoking
34121 @code{jit-reader-load}.
34123 @item jit-reader-unload
34124 Unload the currently loaded JIT reader.
34128 @node Writing JIT Debug Info Readers
34129 @subsection Writing JIT Debug Info Readers
34130 @cindex writing JIT debug info readers
34132 As mentioned, a reader is essentially a shared object conforming to a
34133 certain ABI. This ABI is described in @file{jit-reader.h}.
34135 @file{jit-reader.h} defines the structures, macros and functions
34136 required to write a reader. It is installed (along with
34137 @value{GDBN}), in @file{@var{includedir}/gdb} where @var{includedir} is
34138 the system include directory.
34140 Readers need to be released under a GPL compatible license. A reader
34141 can be declared as released under such a license by placing the macro
34142 @code{GDB_DECLARE_GPL_COMPATIBLE_READER} in a source file.
34144 The entry point for readers is the symbol @code{gdb_init_reader},
34145 which is expected to be a function with the prototype
34147 @findex gdb_init_reader
34149 extern struct gdb_reader_funcs *gdb_init_reader (void);
34152 @cindex @code{struct gdb_reader_funcs}
34154 @code{struct gdb_reader_funcs} contains a set of pointers to callback
34155 functions. These functions are executed to read the debug info
34156 generated by the JIT compiler (@code{read}), to unwind stack frames
34157 (@code{unwind}) and to create canonical frame IDs
34158 (@code{get_Frame_id}). It also has a callback that is called when the
34159 reader is being unloaded (@code{destroy}). The struct looks like this
34162 struct gdb_reader_funcs
34164 /* Must be set to GDB_READER_INTERFACE_VERSION. */
34165 int reader_version;
34167 /* For use by the reader. */
34170 gdb_read_debug_info *read;
34171 gdb_unwind_frame *unwind;
34172 gdb_get_frame_id *get_frame_id;
34173 gdb_destroy_reader *destroy;
34177 @cindex @code{struct gdb_symbol_callbacks}
34178 @cindex @code{struct gdb_unwind_callbacks}
34180 The callbacks are provided with another set of callbacks by
34181 @value{GDBN} to do their job. For @code{read}, these callbacks are
34182 passed in a @code{struct gdb_symbol_callbacks} and for @code{unwind}
34183 and @code{get_frame_id}, in a @code{struct gdb_unwind_callbacks}.
34184 @code{struct gdb_symbol_callbacks} has callbacks to create new object
34185 files and new symbol tables inside those object files. @code{struct
34186 gdb_unwind_callbacks} has callbacks to read registers off the current
34187 frame and to write out the values of the registers in the previous
34188 frame. Both have a callback (@code{target_read}) to read bytes off the
34189 target's address space.
34191 @node In-Process Agent
34192 @chapter In-Process Agent
34193 @cindex debugging agent
34194 The traditional debugging model is conceptually low-speed, but works fine,
34195 because most bugs can be reproduced in debugging-mode execution. However,
34196 as multi-core or many-core processors are becoming mainstream, and
34197 multi-threaded programs become more and more popular, there should be more
34198 and more bugs that only manifest themselves at normal-mode execution, for
34199 example, thread races, because debugger's interference with the program's
34200 timing may conceal the bugs. On the other hand, in some applications,
34201 it is not feasible for the debugger to interrupt the program's execution
34202 long enough for the developer to learn anything helpful about its behavior.
34203 If the program's correctness depends on its real-time behavior, delays
34204 introduced by a debugger might cause the program to fail, even when the
34205 code itself is correct. It is useful to be able to observe the program's
34206 behavior without interrupting it.
34208 Therefore, traditional debugging model is too intrusive to reproduce
34209 some bugs. In order to reduce the interference with the program, we can
34210 reduce the number of operations performed by debugger. The
34211 @dfn{In-Process Agent}, a shared library, is running within the same
34212 process with inferior, and is able to perform some debugging operations
34213 itself. As a result, debugger is only involved when necessary, and
34214 performance of debugging can be improved accordingly. Note that
34215 interference with program can be reduced but can't be removed completely,
34216 because the in-process agent will still stop or slow down the program.
34218 The in-process agent can interpret and execute Agent Expressions
34219 (@pxref{Agent Expressions}) during performing debugging operations. The
34220 agent expressions can be used for different purposes, such as collecting
34221 data in tracepoints, and condition evaluation in breakpoints.
34223 @anchor{Control Agent}
34224 You can control whether the in-process agent is used as an aid for
34225 debugging with the following commands:
34228 @kindex set agent on
34230 Causes the in-process agent to perform some operations on behalf of the
34231 debugger. Just which operations requested by the user will be done
34232 by the in-process agent depends on the its capabilities. For example,
34233 if you request to evaluate breakpoint conditions in the in-process agent,
34234 and the in-process agent has such capability as well, then breakpoint
34235 conditions will be evaluated in the in-process agent.
34237 @kindex set agent off
34238 @item set agent off
34239 Disables execution of debugging operations by the in-process agent. All
34240 of the operations will be performed by @value{GDBN}.
34244 Display the current setting of execution of debugging operations by
34245 the in-process agent.
34249 * In-Process Agent Protocol::
34252 @node In-Process Agent Protocol
34253 @section In-Process Agent Protocol
34254 @cindex in-process agent protocol
34256 The in-process agent is able to communicate with both @value{GDBN} and
34257 GDBserver (@pxref{In-Process Agent}). This section documents the protocol
34258 used for communications between @value{GDBN} or GDBserver and the IPA.
34259 In general, @value{GDBN} or GDBserver sends commands
34260 (@pxref{IPA Protocol Commands}) and data to in-process agent, and then
34261 in-process agent replies back with the return result of the command, or
34262 some other information. The data sent to in-process agent is composed
34263 of primitive data types, such as 4-byte or 8-byte type, and composite
34264 types, which are called objects (@pxref{IPA Protocol Objects}).
34267 * IPA Protocol Objects::
34268 * IPA Protocol Commands::
34271 @node IPA Protocol Objects
34272 @subsection IPA Protocol Objects
34273 @cindex ipa protocol objects
34275 The commands sent to and results received from agent may contain some
34276 complex data types called @dfn{objects}.
34278 The in-process agent is running on the same machine with @value{GDBN}
34279 or GDBserver, so it doesn't have to handle as much differences between
34280 two ends as remote protocol (@pxref{Remote Protocol}) tries to handle.
34281 However, there are still some differences of two ends in two processes:
34285 word size. On some 64-bit machines, @value{GDBN} or GDBserver can be
34286 compiled as a 64-bit executable, while in-process agent is a 32-bit one.
34288 ABI. Some machines may have multiple types of ABI, @value{GDBN} or
34289 GDBserver is compiled with one, and in-process agent is compiled with
34293 Here are the IPA Protocol Objects:
34297 agent expression object. It represents an agent expression
34298 (@pxref{Agent Expressions}).
34299 @anchor{agent expression object}
34301 tracepoint action object. It represents a tracepoint action
34302 (@pxref{Tracepoint Actions,,Tracepoint Action Lists}) to collect registers,
34303 memory, static trace data and to evaluate expression.
34304 @anchor{tracepoint action object}
34306 tracepoint object. It represents a tracepoint (@pxref{Tracepoints}).
34307 @anchor{tracepoint object}
34311 The following table describes important attributes of each IPA protocol
34314 @multitable @columnfractions .30 .20 .50
34315 @headitem Name @tab Size @tab Description
34316 @item @emph{agent expression object} @tab @tab
34317 @item length @tab 4 @tab length of bytes code
34318 @item byte code @tab @var{length} @tab contents of byte code
34319 @item @emph{tracepoint action for collecting memory} @tab @tab
34320 @item 'M' @tab 1 @tab type of tracepoint action
34321 @item addr @tab 8 @tab if @var{basereg} is @samp{-1}, @var{addr} is the
34322 address of the lowest byte to collect, otherwise @var{addr} is the offset
34323 of @var{basereg} for memory collecting.
34324 @item len @tab 8 @tab length of memory for collecting
34325 @item basereg @tab 4 @tab the register number containing the starting
34326 memory address for collecting.
34327 @item @emph{tracepoint action for collecting registers} @tab @tab
34328 @item 'R' @tab 1 @tab type of tracepoint action
34329 @item @emph{tracepoint action for collecting static trace data} @tab @tab
34330 @item 'L' @tab 1 @tab type of tracepoint action
34331 @item @emph{tracepoint action for expression evaluation} @tab @tab
34332 @item 'X' @tab 1 @tab type of tracepoint action
34333 @item agent expression @tab length of @tab @ref{agent expression object}
34334 @item @emph{tracepoint object} @tab @tab
34335 @item number @tab 4 @tab number of tracepoint
34336 @item address @tab 8 @tab address of tracepoint inserted on
34337 @item type @tab 4 @tab type of tracepoint
34338 @item enabled @tab 1 @tab enable or disable of tracepoint
34339 @item step_count @tab 8 @tab step
34340 @item pass_count @tab 8 @tab pass
34341 @item numactions @tab 4 @tab number of tracepoint actions
34342 @item hit count @tab 8 @tab hit count
34343 @item trace frame usage @tab 8 @tab trace frame usage
34344 @item compiled_cond @tab 8 @tab compiled condition
34345 @item orig_size @tab 8 @tab orig size
34346 @item condition @tab 4 if condition is NULL otherwise length of
34347 @ref{agent expression object}
34348 @tab zero if condition is NULL, otherwise is
34349 @ref{agent expression object}
34350 @item actions @tab variable
34351 @tab numactions number of @ref{tracepoint action object}
34354 @node IPA Protocol Commands
34355 @subsection IPA Protocol Commands
34356 @cindex ipa protocol commands
34358 The spaces in each command are delimiters to ease reading this commands
34359 specification. They don't exist in real commands.
34363 @item FastTrace:@var{tracepoint_object} @var{gdb_jump_pad_head}
34364 Installs a new fast tracepoint described by @var{tracepoint_object}
34365 (@pxref{tracepoint object}). The @var{gdb_jump_pad_head}, 8-byte long, is the
34366 head of @dfn{jumppad}, which is used to jump to data collection routine
34371 @item OK @var{target_address} @var{gdb_jump_pad_head} @var{fjump_size} @var{fjump}
34372 @var{target_address} is address of tracepoint in the inferior.
34373 The @var{gdb_jump_pad_head} is updated head of jumppad. Both of
34374 @var{target_address} and @var{gdb_jump_pad_head} are 8-byte long.
34375 The @var{fjump} contains a sequence of instructions jump to jumppad entry.
34376 The @var{fjump_size}, 4-byte long, is the size of @var{fjump}.
34383 Closes the in-process agent. This command is sent when @value{GDBN} or GDBserver
34384 is about to kill inferiors.
34392 @item probe_marker_at:@var{address}
34393 Asks in-process agent to probe the marker at @var{address}.
34400 @item unprobe_marker_at:@var{address}
34401 Asks in-process agent to unprobe the marker at @var{address}.
34405 @chapter Reporting Bugs in @value{GDBN}
34406 @cindex bugs in @value{GDBN}
34407 @cindex reporting bugs in @value{GDBN}
34409 Your bug reports play an essential role in making @value{GDBN} reliable.
34411 Reporting a bug may help you by bringing a solution to your problem, or it
34412 may not. But in any case the principal function of a bug report is to help
34413 the entire community by making the next version of @value{GDBN} work better. Bug
34414 reports are your contribution to the maintenance of @value{GDBN}.
34416 In order for a bug report to serve its purpose, you must include the
34417 information that enables us to fix the bug.
34420 * Bug Criteria:: Have you found a bug?
34421 * Bug Reporting:: How to report bugs
34425 @section Have You Found a Bug?
34426 @cindex bug criteria
34428 If you are not sure whether you have found a bug, here are some guidelines:
34431 @cindex fatal signal
34432 @cindex debugger crash
34433 @cindex crash of debugger
34435 If the debugger gets a fatal signal, for any input whatever, that is a
34436 @value{GDBN} bug. Reliable debuggers never crash.
34438 @cindex error on valid input
34440 If @value{GDBN} produces an error message for valid input, that is a
34441 bug. (Note that if you're cross debugging, the problem may also be
34442 somewhere in the connection to the target.)
34444 @cindex invalid input
34446 If @value{GDBN} does not produce an error message for invalid input,
34447 that is a bug. However, you should note that your idea of
34448 ``invalid input'' might be our idea of ``an extension'' or ``support
34449 for traditional practice''.
34452 If you are an experienced user of debugging tools, your suggestions
34453 for improvement of @value{GDBN} are welcome in any case.
34456 @node Bug Reporting
34457 @section How to Report Bugs
34458 @cindex bug reports
34459 @cindex @value{GDBN} bugs, reporting
34461 A number of companies and individuals offer support for @sc{gnu} products.
34462 If you obtained @value{GDBN} from a support organization, we recommend you
34463 contact that organization first.
34465 You can find contact information for many support companies and
34466 individuals in the file @file{etc/SERVICE} in the @sc{gnu} Emacs
34468 @c should add a web page ref...
34471 @ifset BUGURL_DEFAULT
34472 In any event, we also recommend that you submit bug reports for
34473 @value{GDBN}. The preferred method is to submit them directly using
34474 @uref{http://www.gnu.org/software/gdb/bugs/, @value{GDBN}'s Bugs web
34475 page}. Alternatively, the @email{bug-gdb@@gnu.org, e-mail gateway} can
34478 @strong{Do not send bug reports to @samp{info-gdb}, or to
34479 @samp{help-gdb}, or to any newsgroups.} Most users of @value{GDBN} do
34480 not want to receive bug reports. Those that do have arranged to receive
34483 The mailing list @samp{bug-gdb} has a newsgroup @samp{gnu.gdb.bug} which
34484 serves as a repeater. The mailing list and the newsgroup carry exactly
34485 the same messages. Often people think of posting bug reports to the
34486 newsgroup instead of mailing them. This appears to work, but it has one
34487 problem which can be crucial: a newsgroup posting often lacks a mail
34488 path back to the sender. Thus, if we need to ask for more information,
34489 we may be unable to reach you. For this reason, it is better to send
34490 bug reports to the mailing list.
34492 @ifclear BUGURL_DEFAULT
34493 In any event, we also recommend that you submit bug reports for
34494 @value{GDBN} to @value{BUGURL}.
34498 The fundamental principle of reporting bugs usefully is this:
34499 @strong{report all the facts}. If you are not sure whether to state a
34500 fact or leave it out, state it!
34502 Often people omit facts because they think they know what causes the
34503 problem and assume that some details do not matter. Thus, you might
34504 assume that the name of the variable you use in an example does not matter.
34505 Well, probably it does not, but one cannot be sure. Perhaps the bug is a
34506 stray memory reference which happens to fetch from the location where that
34507 name is stored in memory; perhaps, if the name were different, the contents
34508 of that location would fool the debugger into doing the right thing despite
34509 the bug. Play it safe and give a specific, complete example. That is the
34510 easiest thing for you to do, and the most helpful.
34512 Keep in mind that the purpose of a bug report is to enable us to fix the
34513 bug. It may be that the bug has been reported previously, but neither
34514 you nor we can know that unless your bug report is complete and
34517 Sometimes people give a few sketchy facts and ask, ``Does this ring a
34518 bell?'' Those bug reports are useless, and we urge everyone to
34519 @emph{refuse to respond to them} except to chide the sender to report
34522 To enable us to fix the bug, you should include all these things:
34526 The version of @value{GDBN}. @value{GDBN} announces it if you start
34527 with no arguments; you can also print it at any time using @code{show
34530 Without this, we will not know whether there is any point in looking for
34531 the bug in the current version of @value{GDBN}.
34534 The type of machine you are using, and the operating system name and
34538 The details of the @value{GDBN} build-time configuration.
34539 @value{GDBN} shows these details if you invoke it with the
34540 @option{--configuration} command-line option, or if you type
34541 @code{show configuration} at @value{GDBN}'s prompt.
34544 What compiler (and its version) was used to compile @value{GDBN}---e.g.@:
34545 ``@value{GCC}--2.8.1''.
34548 What compiler (and its version) was used to compile the program you are
34549 debugging---e.g.@: ``@value{GCC}--2.8.1'', or ``HP92453-01 A.10.32.03 HP
34550 C Compiler''. For @value{NGCC}, you can say @kbd{@value{GCC} --version}
34551 to get this information; for other compilers, see the documentation for
34555 The command arguments you gave the compiler to compile your example and
34556 observe the bug. For example, did you use @samp{-O}? To guarantee
34557 you will not omit something important, list them all. A copy of the
34558 Makefile (or the output from make) is sufficient.
34560 If we were to try to guess the arguments, we would probably guess wrong
34561 and then we might not encounter the bug.
34564 A complete input script, and all necessary source files, that will
34568 A description of what behavior you observe that you believe is
34569 incorrect. For example, ``It gets a fatal signal.''
34571 Of course, if the bug is that @value{GDBN} gets a fatal signal, then we
34572 will certainly notice it. But if the bug is incorrect output, we might
34573 not notice unless it is glaringly wrong. You might as well not give us
34574 a chance to make a mistake.
34576 Even if the problem you experience is a fatal signal, you should still
34577 say so explicitly. Suppose something strange is going on, such as, your
34578 copy of @value{GDBN} is out of synch, or you have encountered a bug in
34579 the C library on your system. (This has happened!) Your copy might
34580 crash and ours would not. If you told us to expect a crash, then when
34581 ours fails to crash, we would know that the bug was not happening for
34582 us. If you had not told us to expect a crash, then we would not be able
34583 to draw any conclusion from our observations.
34586 @cindex recording a session script
34587 To collect all this information, you can use a session recording program
34588 such as @command{script}, which is available on many Unix systems.
34589 Just run your @value{GDBN} session inside @command{script} and then
34590 include the @file{typescript} file with your bug report.
34592 Another way to record a @value{GDBN} session is to run @value{GDBN}
34593 inside Emacs and then save the entire buffer to a file.
34596 If you wish to suggest changes to the @value{GDBN} source, send us context
34597 diffs. If you even discuss something in the @value{GDBN} source, refer to
34598 it by context, not by line number.
34600 The line numbers in our development sources will not match those in your
34601 sources. Your line numbers would convey no useful information to us.
34605 Here are some things that are not necessary:
34609 A description of the envelope of the bug.
34611 Often people who encounter a bug spend a lot of time investigating
34612 which changes to the input file will make the bug go away and which
34613 changes will not affect it.
34615 This is often time consuming and not very useful, because the way we
34616 will find the bug is by running a single example under the debugger
34617 with breakpoints, not by pure deduction from a series of examples.
34618 We recommend that you save your time for something else.
34620 Of course, if you can find a simpler example to report @emph{instead}
34621 of the original one, that is a convenience for us. Errors in the
34622 output will be easier to spot, running under the debugger will take
34623 less time, and so on.
34625 However, simplification is not vital; if you do not want to do this,
34626 report the bug anyway and send us the entire test case you used.
34629 A patch for the bug.
34631 A patch for the bug does help us if it is a good one. But do not omit
34632 the necessary information, such as the test case, on the assumption that
34633 a patch is all we need. We might see problems with your patch and decide
34634 to fix the problem another way, or we might not understand it at all.
34636 Sometimes with a program as complicated as @value{GDBN} it is very hard to
34637 construct an example that will make the program follow a certain path
34638 through the code. If you do not send us the example, we will not be able
34639 to construct one, so we will not be able to verify that the bug is fixed.
34641 And if we cannot understand what bug you are trying to fix, or why your
34642 patch should be an improvement, we will not install it. A test case will
34643 help us to understand.
34646 A guess about what the bug is or what it depends on.
34648 Such guesses are usually wrong. Even we cannot guess right about such
34649 things without first using the debugger to find the facts.
34652 @c The readline documentation is distributed with the readline code
34653 @c and consists of the two following files:
34656 @c Use -I with makeinfo to point to the appropriate directory,
34657 @c environment var TEXINPUTS with TeX.
34658 @ifclear SYSTEM_READLINE
34659 @include rluser.texi
34660 @include hsuser.texi
34664 @appendix In Memoriam
34666 The @value{GDBN} project mourns the loss of the following long-time
34671 Fred was a long-standing contributor to @value{GDBN} (1991-2006), and
34672 to Free Software in general. Outside of @value{GDBN}, he was known in
34673 the Amiga world for his series of Fish Disks, and the GeekGadget project.
34675 @item Michael Snyder
34676 Michael was one of the Global Maintainers of the @value{GDBN} project,
34677 with contributions recorded as early as 1996, until 2011. In addition
34678 to his day to day participation, he was a large driving force behind
34679 adding Reverse Debugging to @value{GDBN}.
34682 Beyond their technical contributions to the project, they were also
34683 enjoyable members of the Free Software Community. We will miss them.
34685 @node Formatting Documentation
34686 @appendix Formatting Documentation
34688 @cindex @value{GDBN} reference card
34689 @cindex reference card
34690 The @value{GDBN} 4 release includes an already-formatted reference card, ready
34691 for printing with PostScript or Ghostscript, in the @file{gdb}
34692 subdirectory of the main source directory@footnote{In
34693 @file{gdb-@value{GDBVN}/gdb/refcard.ps} of the version @value{GDBVN}
34694 release.}. If you can use PostScript or Ghostscript with your printer,
34695 you can print the reference card immediately with @file{refcard.ps}.
34697 The release also includes the source for the reference card. You
34698 can format it, using @TeX{}, by typing:
34704 The @value{GDBN} reference card is designed to print in @dfn{landscape}
34705 mode on US ``letter'' size paper;
34706 that is, on a sheet 11 inches wide by 8.5 inches
34707 high. You will need to specify this form of printing as an option to
34708 your @sc{dvi} output program.
34710 @cindex documentation
34712 All the documentation for @value{GDBN} comes as part of the machine-readable
34713 distribution. The documentation is written in Texinfo format, which is
34714 a documentation system that uses a single source file to produce both
34715 on-line information and a printed manual. You can use one of the Info
34716 formatting commands to create the on-line version of the documentation
34717 and @TeX{} (or @code{texi2roff}) to typeset the printed version.
34719 @value{GDBN} includes an already formatted copy of the on-line Info
34720 version of this manual in the @file{gdb} subdirectory. The main Info
34721 file is @file{gdb-@value{GDBVN}/gdb/gdb.info}, and it refers to
34722 subordinate files matching @samp{gdb.info*} in the same directory. If
34723 necessary, you can print out these files, or read them with any editor;
34724 but they are easier to read using the @code{info} subsystem in @sc{gnu}
34725 Emacs or the standalone @code{info} program, available as part of the
34726 @sc{gnu} Texinfo distribution.
34728 If you want to format these Info files yourself, you need one of the
34729 Info formatting programs, such as @code{texinfo-format-buffer} or
34732 If you have @code{makeinfo} installed, and are in the top level
34733 @value{GDBN} source directory (@file{gdb-@value{GDBVN}}, in the case of
34734 version @value{GDBVN}), you can make the Info file by typing:
34741 If you want to typeset and print copies of this manual, you need @TeX{},
34742 a program to print its @sc{dvi} output files, and @file{texinfo.tex}, the
34743 Texinfo definitions file.
34745 @TeX{} is a typesetting program; it does not print files directly, but
34746 produces output files called @sc{dvi} files. To print a typeset
34747 document, you need a program to print @sc{dvi} files. If your system
34748 has @TeX{} installed, chances are it has such a program. The precise
34749 command to use depends on your system; @kbd{lpr -d} is common; another
34750 (for PostScript devices) is @kbd{dvips}. The @sc{dvi} print command may
34751 require a file name without any extension or a @samp{.dvi} extension.
34753 @TeX{} also requires a macro definitions file called
34754 @file{texinfo.tex}. This file tells @TeX{} how to typeset a document
34755 written in Texinfo format. On its own, @TeX{} cannot either read or
34756 typeset a Texinfo file. @file{texinfo.tex} is distributed with GDB
34757 and is located in the @file{gdb-@var{version-number}/texinfo}
34760 If you have @TeX{} and a @sc{dvi} printer program installed, you can
34761 typeset and print this manual. First switch to the @file{gdb}
34762 subdirectory of the main source directory (for example, to
34763 @file{gdb-@value{GDBVN}/gdb}) and type:
34769 Then give @file{gdb.dvi} to your @sc{dvi} printing program.
34771 @node Installing GDB
34772 @appendix Installing @value{GDBN}
34773 @cindex installation
34776 * Requirements:: Requirements for building @value{GDBN}
34777 * Running Configure:: Invoking the @value{GDBN} @file{configure} script
34778 * Separate Objdir:: Compiling @value{GDBN} in another directory
34779 * Config Names:: Specifying names for hosts and targets
34780 * Configure Options:: Summary of options for configure
34781 * System-wide configuration:: Having a system-wide init file
34785 @section Requirements for Building @value{GDBN}
34786 @cindex building @value{GDBN}, requirements for
34788 Building @value{GDBN} requires various tools and packages to be available.
34789 Other packages will be used only if they are found.
34791 @heading Tools/Packages Necessary for Building @value{GDBN}
34793 @item ISO C90 compiler
34794 @value{GDBN} is written in ISO C90. It should be buildable with any
34795 working C90 compiler, e.g.@: GCC.
34799 @heading Tools/Packages Optional for Building @value{GDBN}
34803 @value{GDBN} can use the Expat XML parsing library. This library may be
34804 included with your operating system distribution; if it is not, you
34805 can get the latest version from @url{http://expat.sourceforge.net}.
34806 The @file{configure} script will search for this library in several
34807 standard locations; if it is installed in an unusual path, you can
34808 use the @option{--with-libexpat-prefix} option to specify its location.
34814 Remote protocol memory maps (@pxref{Memory Map Format})
34816 Target descriptions (@pxref{Target Descriptions})
34818 Remote shared library lists (@xref{Library List Format},
34819 or alternatively @pxref{Library List Format for SVR4 Targets})
34821 MS-Windows shared libraries (@pxref{Shared Libraries})
34823 Traceframe info (@pxref{Traceframe Info Format})
34825 Branch trace (@pxref{Branch Trace Format},
34826 @pxref{Branch Trace Configuration Format})
34831 @value{GDBN} can use the GNU MPFR multiple-precision floating-point
34832 library. This library may be included with your operating system
34833 distribution; if it is not, you can get the latest version from
34834 @url{http://www.mpfr.org}. The @file{configure} script will search
34835 for this library in several standard locations; if it is installed
34836 in an unusual path, you can use the @option{--with-libmpfr-prefix}
34837 option to specify its location.
34839 GNU MPFR is used to emulate target floating-point arithmetic during
34840 expression evaluation when the target uses different floating-point
34841 formats than the host. If GNU MPFR it is not available, @value{GDBN}
34842 will fall back to using host floating-point arithmetic.
34845 @cindex compressed debug sections
34846 @value{GDBN} will use the @samp{zlib} library, if available, to read
34847 compressed debug sections. Some linkers, such as GNU gold, are capable
34848 of producing binaries with compressed debug sections. If @value{GDBN}
34849 is compiled with @samp{zlib}, it will be able to read the debug
34850 information in such binaries.
34852 The @samp{zlib} library is likely included with your operating system
34853 distribution; if it is not, you can get the latest version from
34854 @url{http://zlib.net}.
34857 @value{GDBN}'s features related to character sets (@pxref{Character
34858 Sets}) require a functioning @code{iconv} implementation. If you are
34859 on a GNU system, then this is provided by the GNU C Library. Some
34860 other systems also provide a working @code{iconv}.
34862 If @value{GDBN} is using the @code{iconv} program which is installed
34863 in a non-standard place, you will need to tell @value{GDBN} where to find it.
34864 This is done with @option{--with-iconv-bin} which specifies the
34865 directory that contains the @code{iconv} program.
34867 On systems without @code{iconv}, you can install GNU Libiconv. If you
34868 have previously installed Libiconv, you can use the
34869 @option{--with-libiconv-prefix} option to configure.
34871 @value{GDBN}'s top-level @file{configure} and @file{Makefile} will
34872 arrange to build Libiconv if a directory named @file{libiconv} appears
34873 in the top-most source directory. If Libiconv is built this way, and
34874 if the operating system does not provide a suitable @code{iconv}
34875 implementation, then the just-built library will automatically be used
34876 by @value{GDBN}. One easy way to set this up is to download GNU
34877 Libiconv, unpack it, and then rename the directory holding the
34878 Libiconv source code to @samp{libiconv}.
34881 @node Running Configure
34882 @section Invoking the @value{GDBN} @file{configure} Script
34883 @cindex configuring @value{GDBN}
34884 @value{GDBN} comes with a @file{configure} script that automates the process
34885 of preparing @value{GDBN} for installation; you can then use @code{make} to
34886 build the @code{gdb} program.
34888 @c irrelevant in info file; it's as current as the code it lives with.
34889 @footnote{If you have a more recent version of @value{GDBN} than @value{GDBVN},
34890 look at the @file{README} file in the sources; we may have improved the
34891 installation procedures since publishing this manual.}
34894 The @value{GDBN} distribution includes all the source code you need for
34895 @value{GDBN} in a single directory, whose name is usually composed by
34896 appending the version number to @samp{gdb}.
34898 For example, the @value{GDBN} version @value{GDBVN} distribution is in the
34899 @file{gdb-@value{GDBVN}} directory. That directory contains:
34902 @item gdb-@value{GDBVN}/configure @r{(and supporting files)}
34903 script for configuring @value{GDBN} and all its supporting libraries
34905 @item gdb-@value{GDBVN}/gdb
34906 the source specific to @value{GDBN} itself
34908 @item gdb-@value{GDBVN}/bfd
34909 source for the Binary File Descriptor library
34911 @item gdb-@value{GDBVN}/include
34912 @sc{gnu} include files
34914 @item gdb-@value{GDBVN}/libiberty
34915 source for the @samp{-liberty} free software library
34917 @item gdb-@value{GDBVN}/opcodes
34918 source for the library of opcode tables and disassemblers
34920 @item gdb-@value{GDBVN}/readline
34921 source for the @sc{gnu} command-line interface
34923 @item gdb-@value{GDBVN}/glob
34924 source for the @sc{gnu} filename pattern-matching subroutine
34926 @item gdb-@value{GDBVN}/mmalloc
34927 source for the @sc{gnu} memory-mapped malloc package
34930 The simplest way to configure and build @value{GDBN} is to run @file{configure}
34931 from the @file{gdb-@var{version-number}} source directory, which in
34932 this example is the @file{gdb-@value{GDBVN}} directory.
34934 First switch to the @file{gdb-@var{version-number}} source directory
34935 if you are not already in it; then run @file{configure}. Pass the
34936 identifier for the platform on which @value{GDBN} will run as an
34942 cd gdb-@value{GDBVN}
34943 ./configure @var{host}
34948 where @var{host} is an identifier such as @samp{sun4} or
34949 @samp{decstation}, that identifies the platform where @value{GDBN} will run.
34950 (You can often leave off @var{host}; @file{configure} tries to guess the
34951 correct value by examining your system.)
34953 Running @samp{configure @var{host}} and then running @code{make} builds the
34954 @file{bfd}, @file{readline}, @file{mmalloc}, and @file{libiberty}
34955 libraries, then @code{gdb} itself. The configured source files, and the
34956 binaries, are left in the corresponding source directories.
34959 @file{configure} is a Bourne-shell (@code{/bin/sh}) script; if your
34960 system does not recognize this automatically when you run a different
34961 shell, you may need to run @code{sh} on it explicitly:
34964 sh configure @var{host}
34967 If you run @file{configure} from a directory that contains source
34968 directories for multiple libraries or programs, such as the
34969 @file{gdb-@value{GDBVN}} source directory for version @value{GDBVN},
34971 creates configuration files for every directory level underneath (unless
34972 you tell it not to, with the @samp{--norecursion} option).
34974 You should run the @file{configure} script from the top directory in the
34975 source tree, the @file{gdb-@var{version-number}} directory. If you run
34976 @file{configure} from one of the subdirectories, you will configure only
34977 that subdirectory. That is usually not what you want. In particular,
34978 if you run the first @file{configure} from the @file{gdb} subdirectory
34979 of the @file{gdb-@var{version-number}} directory, you will omit the
34980 configuration of @file{bfd}, @file{readline}, and other sibling
34981 directories of the @file{gdb} subdirectory. This leads to build errors
34982 about missing include files such as @file{bfd/bfd.h}.
34984 You can install @code{@value{GDBP}} anywhere; it has no hardwired paths.
34985 However, you should make sure that the shell on your path (named by
34986 the @samp{SHELL} environment variable) is publicly readable. Remember
34987 that @value{GDBN} uses the shell to start your program---some systems refuse to
34988 let @value{GDBN} debug child processes whose programs are not readable.
34990 @node Separate Objdir
34991 @section Compiling @value{GDBN} in Another Directory
34993 If you want to run @value{GDBN} versions for several host or target machines,
34994 you need a different @code{gdb} compiled for each combination of
34995 host and target. @file{configure} is designed to make this easy by
34996 allowing you to generate each configuration in a separate subdirectory,
34997 rather than in the source directory. If your @code{make} program
34998 handles the @samp{VPATH} feature (@sc{gnu} @code{make} does), running
34999 @code{make} in each of these directories builds the @code{gdb}
35000 program specified there.
35002 To build @code{gdb} in a separate directory, run @file{configure}
35003 with the @samp{--srcdir} option to specify where to find the source.
35004 (You also need to specify a path to find @file{configure}
35005 itself from your working directory. If the path to @file{configure}
35006 would be the same as the argument to @samp{--srcdir}, you can leave out
35007 the @samp{--srcdir} option; it is assumed.)
35009 For example, with version @value{GDBVN}, you can build @value{GDBN} in a
35010 separate directory for a Sun 4 like this:
35014 cd gdb-@value{GDBVN}
35017 ../gdb-@value{GDBVN}/configure sun4
35022 When @file{configure} builds a configuration using a remote source
35023 directory, it creates a tree for the binaries with the same structure
35024 (and using the same names) as the tree under the source directory. In
35025 the example, you'd find the Sun 4 library @file{libiberty.a} in the
35026 directory @file{gdb-sun4/libiberty}, and @value{GDBN} itself in
35027 @file{gdb-sun4/gdb}.
35029 Make sure that your path to the @file{configure} script has just one
35030 instance of @file{gdb} in it. If your path to @file{configure} looks
35031 like @file{../gdb-@value{GDBVN}/gdb/configure}, you are configuring only
35032 one subdirectory of @value{GDBN}, not the whole package. This leads to
35033 build errors about missing include files such as @file{bfd/bfd.h}.
35035 One popular reason to build several @value{GDBN} configurations in separate
35036 directories is to configure @value{GDBN} for cross-compiling (where
35037 @value{GDBN} runs on one machine---the @dfn{host}---while debugging
35038 programs that run on another machine---the @dfn{target}).
35039 You specify a cross-debugging target by
35040 giving the @samp{--target=@var{target}} option to @file{configure}.
35042 When you run @code{make} to build a program or library, you must run
35043 it in a configured directory---whatever directory you were in when you
35044 called @file{configure} (or one of its subdirectories).
35046 The @code{Makefile} that @file{configure} generates in each source
35047 directory also runs recursively. If you type @code{make} in a source
35048 directory such as @file{gdb-@value{GDBVN}} (or in a separate configured
35049 directory configured with @samp{--srcdir=@var{dirname}/gdb-@value{GDBVN}}), you
35050 will build all the required libraries, and then build GDB.
35052 When you have multiple hosts or targets configured in separate
35053 directories, you can run @code{make} on them in parallel (for example,
35054 if they are NFS-mounted on each of the hosts); they will not interfere
35058 @section Specifying Names for Hosts and Targets
35060 The specifications used for hosts and targets in the @file{configure}
35061 script are based on a three-part naming scheme, but some short predefined
35062 aliases are also supported. The full naming scheme encodes three pieces
35063 of information in the following pattern:
35066 @var{architecture}-@var{vendor}-@var{os}
35069 For example, you can use the alias @code{sun4} as a @var{host} argument,
35070 or as the value for @var{target} in a @code{--target=@var{target}}
35071 option. The equivalent full name is @samp{sparc-sun-sunos4}.
35073 The @file{configure} script accompanying @value{GDBN} does not provide
35074 any query facility to list all supported host and target names or
35075 aliases. @file{configure} calls the Bourne shell script
35076 @code{config.sub} to map abbreviations to full names; you can read the
35077 script, if you wish, or you can use it to test your guesses on
35078 abbreviations---for example:
35081 % sh config.sub i386-linux
35083 % sh config.sub alpha-linux
35084 alpha-unknown-linux-gnu
35085 % sh config.sub hp9k700
35087 % sh config.sub sun4
35088 sparc-sun-sunos4.1.1
35089 % sh config.sub sun3
35090 m68k-sun-sunos4.1.1
35091 % sh config.sub i986v
35092 Invalid configuration `i986v': machine `i986v' not recognized
35096 @code{config.sub} is also distributed in the @value{GDBN} source
35097 directory (@file{gdb-@value{GDBVN}}, for version @value{GDBVN}).
35099 @node Configure Options
35100 @section @file{configure} Options
35102 Here is a summary of the @file{configure} options and arguments that
35103 are most often useful for building @value{GDBN}. @file{configure} also has
35104 several other options not listed here. @inforef{What Configure
35105 Does,,configure.info}, for a full explanation of @file{configure}.
35108 configure @r{[}--help@r{]}
35109 @r{[}--prefix=@var{dir}@r{]}
35110 @r{[}--exec-prefix=@var{dir}@r{]}
35111 @r{[}--srcdir=@var{dirname}@r{]}
35112 @r{[}--norecursion@r{]} @r{[}--rm@r{]}
35113 @r{[}--target=@var{target}@r{]}
35118 You may introduce options with a single @samp{-} rather than
35119 @samp{--} if you prefer; but you may abbreviate option names if you use
35124 Display a quick summary of how to invoke @file{configure}.
35126 @item --prefix=@var{dir}
35127 Configure the source to install programs and files under directory
35130 @item --exec-prefix=@var{dir}
35131 Configure the source to install programs under directory
35134 @c avoid splitting the warning from the explanation:
35136 @item --srcdir=@var{dirname}
35137 @strong{Warning: using this option requires @sc{gnu} @code{make}, or another
35138 @code{make} that implements the @code{VPATH} feature.}@*
35139 Use this option to make configurations in directories separate from the
35140 @value{GDBN} source directories. Among other things, you can use this to
35141 build (or maintain) several configurations simultaneously, in separate
35142 directories. @file{configure} writes configuration-specific files in
35143 the current directory, but arranges for them to use the source in the
35144 directory @var{dirname}. @file{configure} creates directories under
35145 the working directory in parallel to the source directories below
35148 @item --norecursion
35149 Configure only the directory level where @file{configure} is executed; do not
35150 propagate configuration to subdirectories.
35152 @item --target=@var{target}
35153 Configure @value{GDBN} for cross-debugging programs running on the specified
35154 @var{target}. Without this option, @value{GDBN} is configured to debug
35155 programs that run on the same machine (@var{host}) as @value{GDBN} itself.
35157 There is no convenient way to generate a list of all available targets.
35159 @item @var{host} @dots{}
35160 Configure @value{GDBN} to run on the specified @var{host}.
35162 There is no convenient way to generate a list of all available hosts.
35165 There are many other options available as well, but they are generally
35166 needed for special purposes only.
35168 @node System-wide configuration
35169 @section System-wide configuration and settings
35170 @cindex system-wide init file
35172 @value{GDBN} can be configured to have a system-wide init file;
35173 this file will be read and executed at startup (@pxref{Startup, , What
35174 @value{GDBN} does during startup}).
35176 Here is the corresponding configure option:
35179 @item --with-system-gdbinit=@var{file}
35180 Specify that the default location of the system-wide init file is
35184 If @value{GDBN} has been configured with the option @option{--prefix=$prefix},
35185 it may be subject to relocation. Two possible cases:
35189 If the default location of this init file contains @file{$prefix},
35190 it will be subject to relocation. Suppose that the configure options
35191 are @option{--prefix=$prefix --with-system-gdbinit=$prefix/etc/gdbinit};
35192 if @value{GDBN} is moved from @file{$prefix} to @file{$install}, the system
35193 init file is looked for as @file{$install/etc/gdbinit} instead of
35194 @file{$prefix/etc/gdbinit}.
35197 By contrast, if the default location does not contain the prefix,
35198 it will not be relocated. E.g.@: if @value{GDBN} has been configured with
35199 @option{--prefix=/usr/local --with-system-gdbinit=/usr/share/gdb/gdbinit},
35200 then @value{GDBN} will always look for @file{/usr/share/gdb/gdbinit},
35201 wherever @value{GDBN} is installed.
35204 If the configured location of the system-wide init file (as given by the
35205 @option{--with-system-gdbinit} option at configure time) is in the
35206 data-directory (as specified by @option{--with-gdb-datadir} at configure
35207 time) or in one of its subdirectories, then @value{GDBN} will look for the
35208 system-wide init file in the directory specified by the
35209 @option{--data-directory} command-line option.
35210 Note that the system-wide init file is only read once, during @value{GDBN}
35211 initialization. If the data-directory is changed after @value{GDBN} has
35212 started with the @code{set data-directory} command, the file will not be
35216 * System-wide Configuration Scripts:: Installed System-wide Configuration Scripts
35219 @node System-wide Configuration Scripts
35220 @subsection Installed System-wide Configuration Scripts
35221 @cindex system-wide configuration scripts
35223 The @file{system-gdbinit} directory, located inside the data-directory
35224 (as specified by @option{--with-gdb-datadir} at configure time) contains
35225 a number of scripts which can be used as system-wide init files. To
35226 automatically source those scripts at startup, @value{GDBN} should be
35227 configured with @option{--with-system-gdbinit}. Otherwise, any user
35228 should be able to source them by hand as needed.
35230 The following scripts are currently available:
35233 @item @file{elinos.py}
35235 @cindex ELinOS system-wide configuration script
35236 This script is useful when debugging a program on an ELinOS target.
35237 It takes advantage of the environment variables defined in a standard
35238 ELinOS environment in order to determine the location of the system
35239 shared libraries, and then sets the @samp{solib-absolute-prefix}
35240 and @samp{solib-search-path} variables appropriately.
35242 @item @file{wrs-linux.py}
35243 @pindex wrs-linux.py
35244 @cindex Wind River Linux system-wide configuration script
35245 This script is useful when debugging a program on a target running
35246 Wind River Linux. It expects the @env{ENV_PREFIX} to be set to
35247 the host-side sysroot used by the target system.
35251 @node Maintenance Commands
35252 @appendix Maintenance Commands
35253 @cindex maintenance commands
35254 @cindex internal commands
35256 In addition to commands intended for @value{GDBN} users, @value{GDBN}
35257 includes a number of commands intended for @value{GDBN} developers,
35258 that are not documented elsewhere in this manual. These commands are
35259 provided here for reference. (For commands that turn on debugging
35260 messages, see @ref{Debugging Output}.)
35263 @kindex maint agent
35264 @kindex maint agent-eval
35265 @item maint agent @r{[}-at @var{location}@r{,}@r{]} @var{expression}
35266 @itemx maint agent-eval @r{[}-at @var{location}@r{,}@r{]} @var{expression}
35267 Translate the given @var{expression} into remote agent bytecodes.
35268 This command is useful for debugging the Agent Expression mechanism
35269 (@pxref{Agent Expressions}). The @samp{agent} version produces an
35270 expression useful for data collection, such as by tracepoints, while
35271 @samp{maint agent-eval} produces an expression that evaluates directly
35272 to a result. For instance, a collection expression for @code{globa +
35273 globb} will include bytecodes to record four bytes of memory at each
35274 of the addresses of @code{globa} and @code{globb}, while discarding
35275 the result of the addition, while an evaluation expression will do the
35276 addition and return the sum.
35277 If @code{-at} is given, generate remote agent bytecode for @var{location}.
35278 If not, generate remote agent bytecode for current frame PC address.
35280 @kindex maint agent-printf
35281 @item maint agent-printf @var{format},@var{expr},...
35282 Translate the given format string and list of argument expressions
35283 into remote agent bytecodes and display them as a disassembled list.
35284 This command is useful for debugging the agent version of dynamic
35285 printf (@pxref{Dynamic Printf}).
35287 @kindex maint info breakpoints
35288 @item @anchor{maint info breakpoints}maint info breakpoints
35289 Using the same format as @samp{info breakpoints}, display both the
35290 breakpoints you've set explicitly, and those @value{GDBN} is using for
35291 internal purposes. Internal breakpoints are shown with negative
35292 breakpoint numbers. The type column identifies what kind of breakpoint
35297 Normal, explicitly set breakpoint.
35300 Normal, explicitly set watchpoint.
35303 Internal breakpoint, used to handle correctly stepping through
35304 @code{longjmp} calls.
35306 @item longjmp resume
35307 Internal breakpoint at the target of a @code{longjmp}.
35310 Temporary internal breakpoint used by the @value{GDBN} @code{until} command.
35313 Temporary internal breakpoint used by the @value{GDBN} @code{finish} command.
35316 Shared library events.
35320 @kindex maint info btrace
35321 @item maint info btrace
35322 Pint information about raw branch tracing data.
35324 @kindex maint btrace packet-history
35325 @item maint btrace packet-history
35326 Print the raw branch trace packets that are used to compute the
35327 execution history for the @samp{record btrace} command. Both the
35328 information and the format in which it is printed depend on the btrace
35333 For the BTS recording format, print a list of blocks of sequential
35334 code. For each block, the following information is printed:
35338 Newer blocks have higher numbers. The oldest block has number zero.
35339 @item Lowest @samp{PC}
35340 @item Highest @samp{PC}
35344 For the Intel Processor Trace recording format, print a list of
35345 Intel Processor Trace packets. For each packet, the following
35346 information is printed:
35349 @item Packet number
35350 Newer packets have higher numbers. The oldest packet has number zero.
35352 The packet's offset in the trace stream.
35353 @item Packet opcode and payload
35357 @kindex maint btrace clear-packet-history
35358 @item maint btrace clear-packet-history
35359 Discards the cached packet history printed by the @samp{maint btrace
35360 packet-history} command. The history will be computed again when
35363 @kindex maint btrace clear
35364 @item maint btrace clear
35365 Discard the branch trace data. The data will be fetched anew and the
35366 branch trace will be recomputed when needed.
35368 This implicitly truncates the branch trace to a single branch trace
35369 buffer. When updating branch trace incrementally, the branch trace
35370 available to @value{GDBN} may be bigger than a single branch trace
35373 @kindex maint set btrace pt skip-pad
35374 @item maint set btrace pt skip-pad
35375 @kindex maint show btrace pt skip-pad
35376 @item maint show btrace pt skip-pad
35377 Control whether @value{GDBN} will skip PAD packets when computing the
35380 @kindex set displaced-stepping
35381 @kindex show displaced-stepping
35382 @cindex displaced stepping support
35383 @cindex out-of-line single-stepping
35384 @item set displaced-stepping
35385 @itemx show displaced-stepping
35386 Control whether or not @value{GDBN} will do @dfn{displaced stepping}
35387 if the target supports it. Displaced stepping is a way to single-step
35388 over breakpoints without removing them from the inferior, by executing
35389 an out-of-line copy of the instruction that was originally at the
35390 breakpoint location. It is also known as out-of-line single-stepping.
35393 @item set displaced-stepping on
35394 If the target architecture supports it, @value{GDBN} will use
35395 displaced stepping to step over breakpoints.
35397 @item set displaced-stepping off
35398 @value{GDBN} will not use displaced stepping to step over breakpoints,
35399 even if such is supported by the target architecture.
35401 @cindex non-stop mode, and @samp{set displaced-stepping}
35402 @item set displaced-stepping auto
35403 This is the default mode. @value{GDBN} will use displaced stepping
35404 only if non-stop mode is active (@pxref{Non-Stop Mode}) and the target
35405 architecture supports displaced stepping.
35408 @kindex maint check-psymtabs
35409 @item maint check-psymtabs
35410 Check the consistency of currently expanded psymtabs versus symtabs.
35411 Use this to check, for example, whether a symbol is in one but not the other.
35413 @kindex maint check-symtabs
35414 @item maint check-symtabs
35415 Check the consistency of currently expanded symtabs.
35417 @kindex maint expand-symtabs
35418 @item maint expand-symtabs [@var{regexp}]
35419 Expand symbol tables.
35420 If @var{regexp} is specified, only expand symbol tables for file
35421 names matching @var{regexp}.
35423 @kindex maint set catch-demangler-crashes
35424 @kindex maint show catch-demangler-crashes
35425 @cindex demangler crashes
35426 @item maint set catch-demangler-crashes [on|off]
35427 @itemx maint show catch-demangler-crashes
35428 Control whether @value{GDBN} should attempt to catch crashes in the
35429 symbol name demangler. The default is to attempt to catch crashes.
35430 If enabled, the first time a crash is caught, a core file is created,
35431 the offending symbol is displayed and the user is presented with the
35432 option to terminate the current session.
35434 @kindex maint cplus first_component
35435 @item maint cplus first_component @var{name}
35436 Print the first C@t{++} class/namespace component of @var{name}.
35438 @kindex maint cplus namespace
35439 @item maint cplus namespace
35440 Print the list of possible C@t{++} namespaces.
35442 @kindex maint deprecate
35443 @kindex maint undeprecate
35444 @cindex deprecated commands
35445 @item maint deprecate @var{command} @r{[}@var{replacement}@r{]}
35446 @itemx maint undeprecate @var{command}
35447 Deprecate or undeprecate the named @var{command}. Deprecated commands
35448 cause @value{GDBN} to issue a warning when you use them. The optional
35449 argument @var{replacement} says which newer command should be used in
35450 favor of the deprecated one; if it is given, @value{GDBN} will mention
35451 the replacement as part of the warning.
35453 @kindex maint dump-me
35454 @item maint dump-me
35455 @cindex @code{SIGQUIT} signal, dump core of @value{GDBN}
35456 Cause a fatal signal in the debugger and force it to dump its core.
35457 This is supported only on systems which support aborting a program
35458 with the @code{SIGQUIT} signal.
35460 @kindex maint internal-error
35461 @kindex maint internal-warning
35462 @kindex maint demangler-warning
35463 @cindex demangler crashes
35464 @item maint internal-error @r{[}@var{message-text}@r{]}
35465 @itemx maint internal-warning @r{[}@var{message-text}@r{]}
35466 @itemx maint demangler-warning @r{[}@var{message-text}@r{]}
35468 Cause @value{GDBN} to call the internal function @code{internal_error},
35469 @code{internal_warning} or @code{demangler_warning} and hence behave
35470 as though an internal problem has been detected. In addition to
35471 reporting the internal problem, these functions give the user the
35472 opportunity to either quit @value{GDBN} or (for @code{internal_error}
35473 and @code{internal_warning}) create a core file of the current
35474 @value{GDBN} session.
35476 These commands take an optional parameter @var{message-text} that is
35477 used as the text of the error or warning message.
35479 Here's an example of using @code{internal-error}:
35482 (@value{GDBP}) @kbd{maint internal-error testing, 1, 2}
35483 @dots{}/maint.c:121: internal-error: testing, 1, 2
35484 A problem internal to GDB has been detected. Further
35485 debugging may prove unreliable.
35486 Quit this debugging session? (y or n) @kbd{n}
35487 Create a core file? (y or n) @kbd{n}
35491 @cindex @value{GDBN} internal error
35492 @cindex internal errors, control of @value{GDBN} behavior
35493 @cindex demangler crashes
35495 @kindex maint set internal-error
35496 @kindex maint show internal-error
35497 @kindex maint set internal-warning
35498 @kindex maint show internal-warning
35499 @kindex maint set demangler-warning
35500 @kindex maint show demangler-warning
35501 @item maint set internal-error @var{action} [ask|yes|no]
35502 @itemx maint show internal-error @var{action}
35503 @itemx maint set internal-warning @var{action} [ask|yes|no]
35504 @itemx maint show internal-warning @var{action}
35505 @itemx maint set demangler-warning @var{action} [ask|yes|no]
35506 @itemx maint show demangler-warning @var{action}
35507 When @value{GDBN} reports an internal problem (error or warning) it
35508 gives the user the opportunity to both quit @value{GDBN} and create a
35509 core file of the current @value{GDBN} session. These commands let you
35510 override the default behaviour for each particular @var{action},
35511 described in the table below.
35515 You can specify that @value{GDBN} should always (yes) or never (no)
35516 quit. The default is to ask the user what to do.
35519 You can specify that @value{GDBN} should always (yes) or never (no)
35520 create a core file. The default is to ask the user what to do. Note
35521 that there is no @code{corefile} option for @code{demangler-warning}:
35522 demangler warnings always create a core file and this cannot be
35526 @kindex maint packet
35527 @item maint packet @var{text}
35528 If @value{GDBN} is talking to an inferior via the serial protocol,
35529 then this command sends the string @var{text} to the inferior, and
35530 displays the response packet. @value{GDBN} supplies the initial
35531 @samp{$} character, the terminating @samp{#} character, and the
35534 @kindex maint print architecture
35535 @item maint print architecture @r{[}@var{file}@r{]}
35536 Print the entire architecture configuration. The optional argument
35537 @var{file} names the file where the output goes.
35539 @kindex maint print c-tdesc @r{[}@var{file}@r{]}
35540 @item maint print c-tdesc
35541 Print the target description (@pxref{Target Descriptions}) as
35542 a C source file. By default, the target description is for the current
35543 target, but if the optional argument @var{file} is provided, that file
35544 is used to produce the description. The @var{file} should be an XML
35545 document, of the form described in @ref{Target Description Format}.
35546 The created source file is built into @value{GDBN} when @value{GDBN} is
35547 built again. This command is used by developers after they add or
35548 modify XML target descriptions.
35550 @kindex maint check xml-descriptions
35551 @item maint check xml-descriptions @var{dir}
35552 Check that the target descriptions dynamically created by @value{GDBN}
35553 equal the descriptions created from XML files found in @var{dir}.
35555 @anchor{maint check libthread-db}
35556 @kindex maint check libthread-db
35557 @item maint check libthread-db
35558 Run integrity checks on the current inferior's thread debugging
35559 library. This exercises all @code{libthread_db} functionality used by
35560 @value{GDBN} on GNU/Linux systems, and by extension also exercises the
35561 @code{proc_service} functions provided by @value{GDBN} that
35562 @code{libthread_db} uses. Note that parts of the test may be skipped
35563 on some platforms when debugging core files.
35565 @kindex maint print dummy-frames
35566 @item maint print dummy-frames
35567 Prints the contents of @value{GDBN}'s internal dummy-frame stack.
35570 (@value{GDBP}) @kbd{b add}
35572 (@value{GDBP}) @kbd{print add(2,3)}
35573 Breakpoint 2, add (a=2, b=3) at @dots{}
35575 The program being debugged stopped while in a function called from GDB.
35577 (@value{GDBP}) @kbd{maint print dummy-frames}
35578 0xa8206d8: id=@{stack=0xbfffe734,code=0xbfffe73f,!special@}, ptid=process 9353
35582 Takes an optional file parameter.
35584 @kindex maint print registers
35585 @kindex maint print raw-registers
35586 @kindex maint print cooked-registers
35587 @kindex maint print register-groups
35588 @kindex maint print remote-registers
35589 @item maint print registers @r{[}@var{file}@r{]}
35590 @itemx maint print raw-registers @r{[}@var{file}@r{]}
35591 @itemx maint print cooked-registers @r{[}@var{file}@r{]}
35592 @itemx maint print register-groups @r{[}@var{file}@r{]}
35593 @itemx maint print remote-registers @r{[}@var{file}@r{]}
35594 Print @value{GDBN}'s internal register data structures.
35596 The command @code{maint print raw-registers} includes the contents of
35597 the raw register cache; the command @code{maint print
35598 cooked-registers} includes the (cooked) value of all registers,
35599 including registers which aren't available on the target nor visible
35600 to user; the command @code{maint print register-groups} includes the
35601 groups that each register is a member of; and the command @code{maint
35602 print remote-registers} includes the remote target's register numbers
35603 and offsets in the `G' packets.
35605 These commands take an optional parameter, a file name to which to
35606 write the information.
35608 @kindex maint print reggroups
35609 @item maint print reggroups @r{[}@var{file}@r{]}
35610 Print @value{GDBN}'s internal register group data structures. The
35611 optional argument @var{file} tells to what file to write the
35614 The register groups info looks like this:
35617 (@value{GDBP}) @kbd{maint print reggroups}
35630 This command forces @value{GDBN} to flush its internal register cache.
35632 @kindex maint print objfiles
35633 @cindex info for known object files
35634 @item maint print objfiles @r{[}@var{regexp}@r{]}
35635 Print a dump of all known object files.
35636 If @var{regexp} is specified, only print object files whose names
35637 match @var{regexp}. For each object file, this command prints its name,
35638 address in memory, and all of its psymtabs and symtabs.
35640 @kindex maint print user-registers
35641 @cindex user registers
35642 @item maint print user-registers
35643 List all currently available @dfn{user registers}. User registers
35644 typically provide alternate names for actual hardware registers. They
35645 include the four ``standard'' registers @code{$fp}, @code{$pc},
35646 @code{$sp}, and @code{$ps}. @xref{standard registers}. User
35647 registers can be used in expressions in the same way as the canonical
35648 register names, but only the latter are listed by the @code{info
35649 registers} and @code{maint print registers} commands.
35651 @kindex maint print section-scripts
35652 @cindex info for known .debug_gdb_scripts-loaded scripts
35653 @item maint print section-scripts [@var{regexp}]
35654 Print a dump of scripts specified in the @code{.debug_gdb_section} section.
35655 If @var{regexp} is specified, only print scripts loaded by object files
35656 matching @var{regexp}.
35657 For each script, this command prints its name as specified in the objfile,
35658 and the full path if known.
35659 @xref{dotdebug_gdb_scripts section}.
35661 @kindex maint print statistics
35662 @cindex bcache statistics
35663 @item maint print statistics
35664 This command prints, for each object file in the program, various data
35665 about that object file followed by the byte cache (@dfn{bcache})
35666 statistics for the object file. The objfile data includes the number
35667 of minimal, partial, full, and stabs symbols, the number of types
35668 defined by the objfile, the number of as yet unexpanded psym tables,
35669 the number of line tables and string tables, and the amount of memory
35670 used by the various tables. The bcache statistics include the counts,
35671 sizes, and counts of duplicates of all and unique objects, max,
35672 average, and median entry size, total memory used and its overhead and
35673 savings, and various measures of the hash table size and chain
35676 @kindex maint print target-stack
35677 @cindex target stack description
35678 @item maint print target-stack
35679 A @dfn{target} is an interface between the debugger and a particular
35680 kind of file or process. Targets can be stacked in @dfn{strata},
35681 so that more than one target can potentially respond to a request.
35682 In particular, memory accesses will walk down the stack of targets
35683 until they find a target that is interested in handling that particular
35686 This command prints a short description of each layer that was pushed on
35687 the @dfn{target stack}, starting from the top layer down to the bottom one.
35689 @kindex maint print type
35690 @cindex type chain of a data type
35691 @item maint print type @var{expr}
35692 Print the type chain for a type specified by @var{expr}. The argument
35693 can be either a type name or a symbol. If it is a symbol, the type of
35694 that symbol is described. The type chain produced by this command is
35695 a recursive definition of the data type as stored in @value{GDBN}'s
35696 data structures, including its flags and contained types.
35698 @kindex maint selftest
35700 @item maint selftest @r{[}@var{filter}@r{]}
35701 Run any self tests that were compiled in to @value{GDBN}. This will
35702 print a message showing how many tests were run, and how many failed.
35703 If a @var{filter} is passed, only the tests with @var{filter} in their
35706 @kindex "maint info selftests"
35708 @item maint info selftests
35709 List the selftests compiled in to @value{GDBN}.
35711 @kindex maint set dwarf always-disassemble
35712 @kindex maint show dwarf always-disassemble
35713 @item maint set dwarf always-disassemble
35714 @item maint show dwarf always-disassemble
35715 Control the behavior of @code{info address} when using DWARF debugging
35718 The default is @code{off}, which means that @value{GDBN} should try to
35719 describe a variable's location in an easily readable format. When
35720 @code{on}, @value{GDBN} will instead display the DWARF location
35721 expression in an assembly-like format. Note that some locations are
35722 too complex for @value{GDBN} to describe simply; in this case you will
35723 always see the disassembly form.
35725 Here is an example of the resulting disassembly:
35728 (gdb) info addr argc
35729 Symbol "argc" is a complex DWARF expression:
35733 For more information on these expressions, see
35734 @uref{http://www.dwarfstd.org/, the DWARF standard}.
35736 @kindex maint set dwarf max-cache-age
35737 @kindex maint show dwarf max-cache-age
35738 @item maint set dwarf max-cache-age
35739 @itemx maint show dwarf max-cache-age
35740 Control the DWARF compilation unit cache.
35742 @cindex DWARF compilation units cache
35743 In object files with inter-compilation-unit references, such as those
35744 produced by the GCC option @samp{-feliminate-dwarf2-dups}, the DWARF
35745 reader needs to frequently refer to previously read compilation units.
35746 This setting controls how long a compilation unit will remain in the
35747 cache if it is not referenced. A higher limit means that cached
35748 compilation units will be stored in memory longer, and more total
35749 memory will be used. Setting it to zero disables caching, which will
35750 slow down @value{GDBN} startup, but reduce memory consumption.
35752 @kindex maint set profile
35753 @kindex maint show profile
35754 @cindex profiling GDB
35755 @item maint set profile
35756 @itemx maint show profile
35757 Control profiling of @value{GDBN}.
35759 Profiling will be disabled until you use the @samp{maint set profile}
35760 command to enable it. When you enable profiling, the system will begin
35761 collecting timing and execution count data; when you disable profiling or
35762 exit @value{GDBN}, the results will be written to a log file. Remember that
35763 if you use profiling, @value{GDBN} will overwrite the profiling log file
35764 (often called @file{gmon.out}). If you have a record of important profiling
35765 data in a @file{gmon.out} file, be sure to move it to a safe location.
35767 Configuring with @samp{--enable-profiling} arranges for @value{GDBN} to be
35768 compiled with the @samp{-pg} compiler option.
35770 @kindex maint set show-debug-regs
35771 @kindex maint show show-debug-regs
35772 @cindex hardware debug registers
35773 @item maint set show-debug-regs
35774 @itemx maint show show-debug-regs
35775 Control whether to show variables that mirror the hardware debug
35776 registers. Use @code{on} to enable, @code{off} to disable. If
35777 enabled, the debug registers values are shown when @value{GDBN} inserts or
35778 removes a hardware breakpoint or watchpoint, and when the inferior
35779 triggers a hardware-assisted breakpoint or watchpoint.
35781 @kindex maint set show-all-tib
35782 @kindex maint show show-all-tib
35783 @item maint set show-all-tib
35784 @itemx maint show show-all-tib
35785 Control whether to show all non zero areas within a 1k block starting
35786 at thread local base, when using the @samp{info w32 thread-information-block}
35789 @kindex maint set target-async
35790 @kindex maint show target-async
35791 @item maint set target-async
35792 @itemx maint show target-async
35793 This controls whether @value{GDBN} targets operate in synchronous or
35794 asynchronous mode (@pxref{Background Execution}). Normally the
35795 default is asynchronous, if it is available; but this can be changed
35796 to more easily debug problems occurring only in synchronous mode.
35798 @kindex maint set target-non-stop @var{mode} [on|off|auto]
35799 @kindex maint show target-non-stop
35800 @item maint set target-non-stop
35801 @itemx maint show target-non-stop
35803 This controls whether @value{GDBN} targets always operate in non-stop
35804 mode even if @code{set non-stop} is @code{off} (@pxref{Non-Stop
35805 Mode}). The default is @code{auto}, meaning non-stop mode is enabled
35806 if supported by the target.
35809 @item maint set target-non-stop auto
35810 This is the default mode. @value{GDBN} controls the target in
35811 non-stop mode if the target supports it.
35813 @item maint set target-non-stop on
35814 @value{GDBN} controls the target in non-stop mode even if the target
35815 does not indicate support.
35817 @item maint set target-non-stop off
35818 @value{GDBN} does not control the target in non-stop mode even if the
35819 target supports it.
35822 @kindex maint set per-command
35823 @kindex maint show per-command
35824 @item maint set per-command
35825 @itemx maint show per-command
35826 @cindex resources used by commands
35828 @value{GDBN} can display the resources used by each command.
35829 This is useful in debugging performance problems.
35832 @item maint set per-command space [on|off]
35833 @itemx maint show per-command space
35834 Enable or disable the printing of the memory used by GDB for each command.
35835 If enabled, @value{GDBN} will display how much memory each command
35836 took, following the command's own output.
35837 This can also be requested by invoking @value{GDBN} with the
35838 @option{--statistics} command-line switch (@pxref{Mode Options}).
35840 @item maint set per-command time [on|off]
35841 @itemx maint show per-command time
35842 Enable or disable the printing of the execution time of @value{GDBN}
35844 If enabled, @value{GDBN} will display how much time it
35845 took to execute each command, following the command's own output.
35846 Both CPU time and wallclock time are printed.
35847 Printing both is useful when trying to determine whether the cost is
35848 CPU or, e.g., disk/network latency.
35849 Note that the CPU time printed is for @value{GDBN} only, it does not include
35850 the execution time of the inferior because there's no mechanism currently
35851 to compute how much time was spent by @value{GDBN} and how much time was
35852 spent by the program been debugged.
35853 This can also be requested by invoking @value{GDBN} with the
35854 @option{--statistics} command-line switch (@pxref{Mode Options}).
35856 @item maint set per-command symtab [on|off]
35857 @itemx maint show per-command symtab
35858 Enable or disable the printing of basic symbol table statistics
35860 If enabled, @value{GDBN} will display the following information:
35864 number of symbol tables
35866 number of primary symbol tables
35868 number of blocks in the blockvector
35872 @kindex maint set check-libthread-db
35873 @kindex maint show check-libthread-db
35874 @item maint set check-libthread-db [on|off]
35875 @itemx maint show check-libthread-db
35876 Control whether @value{GDBN} should run integrity checks on inferior
35877 specific thread debugging libraries as they are loaded. The default
35878 is not to perform such checks. If any check fails @value{GDBN} will
35879 unload the library and continue searching for a suitable candidate as
35880 described in @ref{set libthread-db-search-path}. For more information
35881 about the tests, see @ref{maint check libthread-db}.
35883 @kindex maint space
35884 @cindex memory used by commands
35885 @item maint space @var{value}
35886 An alias for @code{maint set per-command space}.
35887 A non-zero value enables it, zero disables it.
35890 @cindex time of command execution
35891 @item maint time @var{value}
35892 An alias for @code{maint set per-command time}.
35893 A non-zero value enables it, zero disables it.
35895 @kindex maint translate-address
35896 @item maint translate-address @r{[}@var{section}@r{]} @var{addr}
35897 Find the symbol stored at the location specified by the address
35898 @var{addr} and an optional section name @var{section}. If found,
35899 @value{GDBN} prints the name of the closest symbol and an offset from
35900 the symbol's location to the specified address. This is similar to
35901 the @code{info address} command (@pxref{Symbols}), except that this
35902 command also allows to find symbols in other sections.
35904 If section was not specified, the section in which the symbol was found
35905 is also printed. For dynamically linked executables, the name of
35906 executable or shared library containing the symbol is printed as well.
35910 The following command is useful for non-interactive invocations of
35911 @value{GDBN}, such as in the test suite.
35914 @item set watchdog @var{nsec}
35915 @kindex set watchdog
35916 @cindex watchdog timer
35917 @cindex timeout for commands
35918 Set the maximum number of seconds @value{GDBN} will wait for the
35919 target operation to finish. If this time expires, @value{GDBN}
35920 reports and error and the command is aborted.
35922 @item show watchdog
35923 Show the current setting of the target wait timeout.
35926 @node Remote Protocol
35927 @appendix @value{GDBN} Remote Serial Protocol
35932 * Stop Reply Packets::
35933 * General Query Packets::
35934 * Architecture-Specific Protocol Details::
35935 * Tracepoint Packets::
35936 * Host I/O Packets::
35938 * Notification Packets::
35939 * Remote Non-Stop::
35940 * Packet Acknowledgment::
35942 * File-I/O Remote Protocol Extension::
35943 * Library List Format::
35944 * Library List Format for SVR4 Targets::
35945 * Memory Map Format::
35946 * Thread List Format::
35947 * Traceframe Info Format::
35948 * Branch Trace Format::
35949 * Branch Trace Configuration Format::
35955 There may be occasions when you need to know something about the
35956 protocol---for example, if there is only one serial port to your target
35957 machine, you might want your program to do something special if it
35958 recognizes a packet meant for @value{GDBN}.
35960 In the examples below, @samp{->} and @samp{<-} are used to indicate
35961 transmitted and received data, respectively.
35963 @cindex protocol, @value{GDBN} remote serial
35964 @cindex serial protocol, @value{GDBN} remote
35965 @cindex remote serial protocol
35966 All @value{GDBN} commands and responses (other than acknowledgments
35967 and notifications, see @ref{Notification Packets}) are sent as a
35968 @var{packet}. A @var{packet} is introduced with the character
35969 @samp{$}, the actual @var{packet-data}, and the terminating character
35970 @samp{#} followed by a two-digit @var{checksum}:
35973 @code{$}@var{packet-data}@code{#}@var{checksum}
35977 @cindex checksum, for @value{GDBN} remote
35979 The two-digit @var{checksum} is computed as the modulo 256 sum of all
35980 characters between the leading @samp{$} and the trailing @samp{#} (an
35981 eight bit unsigned checksum).
35983 Implementors should note that prior to @value{GDBN} 5.0 the protocol
35984 specification also included an optional two-digit @var{sequence-id}:
35987 @code{$}@var{sequence-id}@code{:}@var{packet-data}@code{#}@var{checksum}
35990 @cindex sequence-id, for @value{GDBN} remote
35992 That @var{sequence-id} was appended to the acknowledgment. @value{GDBN}
35993 has never output @var{sequence-id}s. Stubs that handle packets added
35994 since @value{GDBN} 5.0 must not accept @var{sequence-id}.
35996 When either the host or the target machine receives a packet, the first
35997 response expected is an acknowledgment: either @samp{+} (to indicate
35998 the package was received correctly) or @samp{-} (to request
36002 -> @code{$}@var{packet-data}@code{#}@var{checksum}
36007 The @samp{+}/@samp{-} acknowledgments can be disabled
36008 once a connection is established.
36009 @xref{Packet Acknowledgment}, for details.
36011 The host (@value{GDBN}) sends @var{command}s, and the target (the
36012 debugging stub incorporated in your program) sends a @var{response}. In
36013 the case of step and continue @var{command}s, the response is only sent
36014 when the operation has completed, and the target has again stopped all
36015 threads in all attached processes. This is the default all-stop mode
36016 behavior, but the remote protocol also supports @value{GDBN}'s non-stop
36017 execution mode; see @ref{Remote Non-Stop}, for details.
36019 @var{packet-data} consists of a sequence of characters with the
36020 exception of @samp{#} and @samp{$} (see @samp{X} packet for additional
36023 @cindex remote protocol, field separator
36024 Fields within the packet should be separated using @samp{,} @samp{;} or
36025 @samp{:}. Except where otherwise noted all numbers are represented in
36026 @sc{hex} with leading zeros suppressed.
36028 Implementors should note that prior to @value{GDBN} 5.0, the character
36029 @samp{:} could not appear as the third character in a packet (as it
36030 would potentially conflict with the @var{sequence-id}).
36032 @cindex remote protocol, binary data
36033 @anchor{Binary Data}
36034 Binary data in most packets is encoded either as two hexadecimal
36035 digits per byte of binary data. This allowed the traditional remote
36036 protocol to work over connections which were only seven-bit clean.
36037 Some packets designed more recently assume an eight-bit clean
36038 connection, and use a more efficient encoding to send and receive
36041 The binary data representation uses @code{7d} (@sc{ascii} @samp{@}})
36042 as an escape character. Any escaped byte is transmitted as the escape
36043 character followed by the original character XORed with @code{0x20}.
36044 For example, the byte @code{0x7d} would be transmitted as the two
36045 bytes @code{0x7d 0x5d}. The bytes @code{0x23} (@sc{ascii} @samp{#}),
36046 @code{0x24} (@sc{ascii} @samp{$}), and @code{0x7d} (@sc{ascii}
36047 @samp{@}}) must always be escaped. Responses sent by the stub
36048 must also escape @code{0x2a} (@sc{ascii} @samp{*}), so that it
36049 is not interpreted as the start of a run-length encoded sequence
36052 Response @var{data} can be run-length encoded to save space.
36053 Run-length encoding replaces runs of identical characters with one
36054 instance of the repeated character, followed by a @samp{*} and a
36055 repeat count. The repeat count is itself sent encoded, to avoid
36056 binary characters in @var{data}: a value of @var{n} is sent as
36057 @code{@var{n}+29}. For a repeat count greater or equal to 3, this
36058 produces a printable @sc{ascii} character, e.g.@: a space (@sc{ascii}
36059 code 32) for a repeat count of 3. (This is because run-length
36060 encoding starts to win for counts 3 or more.) Thus, for example,
36061 @samp{0* } is a run-length encoding of ``0000'': the space character
36062 after @samp{*} means repeat the leading @code{0} @w{@code{32 - 29 =
36065 The printable characters @samp{#} and @samp{$} or with a numeric value
36066 greater than 126 must not be used. Runs of six repeats (@samp{#}) or
36067 seven repeats (@samp{$}) can be expanded using a repeat count of only
36068 five (@samp{"}). For example, @samp{00000000} can be encoded as
36071 The error response returned for some packets includes a two character
36072 error number. That number is not well defined.
36074 @cindex empty response, for unsupported packets
36075 For any @var{command} not supported by the stub, an empty response
36076 (@samp{$#00}) should be returned. That way it is possible to extend the
36077 protocol. A newer @value{GDBN} can tell if a packet is supported based
36080 At a minimum, a stub is required to support the @samp{g} and @samp{G}
36081 commands for register access, and the @samp{m} and @samp{M} commands
36082 for memory access. Stubs that only control single-threaded targets
36083 can implement run control with the @samp{c} (continue), and @samp{s}
36084 (step) commands. Stubs that support multi-threading targets should
36085 support the @samp{vCont} command. All other commands are optional.
36090 The following table provides a complete list of all currently defined
36091 @var{command}s and their corresponding response @var{data}.
36092 @xref{File-I/O Remote Protocol Extension}, for details about the File
36093 I/O extension of the remote protocol.
36095 Each packet's description has a template showing the packet's overall
36096 syntax, followed by an explanation of the packet's meaning. We
36097 include spaces in some of the templates for clarity; these are not
36098 part of the packet's syntax. No @value{GDBN} packet uses spaces to
36099 separate its components. For example, a template like @samp{foo
36100 @var{bar} @var{baz}} describes a packet beginning with the three ASCII
36101 bytes @samp{foo}, followed by a @var{bar}, followed directly by a
36102 @var{baz}. @value{GDBN} does not transmit a space character between the
36103 @samp{foo} and the @var{bar}, or between the @var{bar} and the
36106 @cindex @var{thread-id}, in remote protocol
36107 @anchor{thread-id syntax}
36108 Several packets and replies include a @var{thread-id} field to identify
36109 a thread. Normally these are positive numbers with a target-specific
36110 interpretation, formatted as big-endian hex strings. A @var{thread-id}
36111 can also be a literal @samp{-1} to indicate all threads, or @samp{0} to
36114 In addition, the remote protocol supports a multiprocess feature in
36115 which the @var{thread-id} syntax is extended to optionally include both
36116 process and thread ID fields, as @samp{p@var{pid}.@var{tid}}.
36117 The @var{pid} (process) and @var{tid} (thread) components each have the
36118 format described above: a positive number with target-specific
36119 interpretation formatted as a big-endian hex string, literal @samp{-1}
36120 to indicate all processes or threads (respectively), or @samp{0} to
36121 indicate an arbitrary process or thread. Specifying just a process, as
36122 @samp{p@var{pid}}, is equivalent to @samp{p@var{pid}.-1}. It is an
36123 error to specify all processes but a specific thread, such as
36124 @samp{p-1.@var{tid}}. Note that the @samp{p} prefix is @emph{not} used
36125 for those packets and replies explicitly documented to include a process
36126 ID, rather than a @var{thread-id}.
36128 The multiprocess @var{thread-id} syntax extensions are only used if both
36129 @value{GDBN} and the stub report support for the @samp{multiprocess}
36130 feature using @samp{qSupported}. @xref{multiprocess extensions}, for
36133 Note that all packet forms beginning with an upper- or lower-case
36134 letter, other than those described here, are reserved for future use.
36136 Here are the packet descriptions.
36141 @cindex @samp{!} packet
36142 @anchor{extended mode}
36143 Enable extended mode. In extended mode, the remote server is made
36144 persistent. The @samp{R} packet is used to restart the program being
36150 The remote target both supports and has enabled extended mode.
36154 @cindex @samp{?} packet
36156 Indicate the reason the target halted. The reply is the same as for
36157 step and continue. This packet has a special interpretation when the
36158 target is in non-stop mode; see @ref{Remote Non-Stop}.
36161 @xref{Stop Reply Packets}, for the reply specifications.
36163 @item A @var{arglen},@var{argnum},@var{arg},@dots{}
36164 @cindex @samp{A} packet
36165 Initialized @code{argv[]} array passed into program. @var{arglen}
36166 specifies the number of bytes in the hex encoded byte stream
36167 @var{arg}. See @code{gdbserver} for more details.
36172 The arguments were set.
36178 @cindex @samp{b} packet
36179 (Don't use this packet; its behavior is not well-defined.)
36180 Change the serial line speed to @var{baud}.
36182 JTC: @emph{When does the transport layer state change? When it's
36183 received, or after the ACK is transmitted. In either case, there are
36184 problems if the command or the acknowledgment packet is dropped.}
36186 Stan: @emph{If people really wanted to add something like this, and get
36187 it working for the first time, they ought to modify ser-unix.c to send
36188 some kind of out-of-band message to a specially-setup stub and have the
36189 switch happen "in between" packets, so that from remote protocol's point
36190 of view, nothing actually happened.}
36192 @item B @var{addr},@var{mode}
36193 @cindex @samp{B} packet
36194 Set (@var{mode} is @samp{S}) or clear (@var{mode} is @samp{C}) a
36195 breakpoint at @var{addr}.
36197 Don't use this packet. Use the @samp{Z} and @samp{z} packets instead
36198 (@pxref{insert breakpoint or watchpoint packet}).
36200 @cindex @samp{bc} packet
36203 Backward continue. Execute the target system in reverse. No parameter.
36204 @xref{Reverse Execution}, for more information.
36207 @xref{Stop Reply Packets}, for the reply specifications.
36209 @cindex @samp{bs} packet
36212 Backward single step. Execute one instruction in reverse. No parameter.
36213 @xref{Reverse Execution}, for more information.
36216 @xref{Stop Reply Packets}, for the reply specifications.
36218 @item c @r{[}@var{addr}@r{]}
36219 @cindex @samp{c} packet
36220 Continue at @var{addr}, which is the address to resume. If @var{addr}
36221 is omitted, resume at current address.
36223 This packet is deprecated for multi-threading support. @xref{vCont
36227 @xref{Stop Reply Packets}, for the reply specifications.
36229 @item C @var{sig}@r{[};@var{addr}@r{]}
36230 @cindex @samp{C} packet
36231 Continue with signal @var{sig} (hex signal number). If
36232 @samp{;@var{addr}} is omitted, resume at same address.
36234 This packet is deprecated for multi-threading support. @xref{vCont
36238 @xref{Stop Reply Packets}, for the reply specifications.
36241 @cindex @samp{d} packet
36244 Don't use this packet; instead, define a general set packet
36245 (@pxref{General Query Packets}).
36249 @cindex @samp{D} packet
36250 The first form of the packet is used to detach @value{GDBN} from the
36251 remote system. It is sent to the remote target
36252 before @value{GDBN} disconnects via the @code{detach} command.
36254 The second form, including a process ID, is used when multiprocess
36255 protocol extensions are enabled (@pxref{multiprocess extensions}), to
36256 detach only a specific process. The @var{pid} is specified as a
36257 big-endian hex string.
36267 @item F @var{RC},@var{EE},@var{CF};@var{XX}
36268 @cindex @samp{F} packet
36269 A reply from @value{GDBN} to an @samp{F} packet sent by the target.
36270 This is part of the File-I/O protocol extension. @xref{File-I/O
36271 Remote Protocol Extension}, for the specification.
36274 @anchor{read registers packet}
36275 @cindex @samp{g} packet
36276 Read general registers.
36280 @item @var{XX@dots{}}
36281 Each byte of register data is described by two hex digits. The bytes
36282 with the register are transmitted in target byte order. The size of
36283 each register and their position within the @samp{g} packet are
36284 determined by the @value{GDBN} internal gdbarch functions
36285 @code{DEPRECATED_REGISTER_RAW_SIZE} and @code{gdbarch_register_name}.
36287 When reading registers from a trace frame (@pxref{Analyze Collected
36288 Data,,Using the Collected Data}), the stub may also return a string of
36289 literal @samp{x}'s in place of the register data digits, to indicate
36290 that the corresponding register has not been collected, thus its value
36291 is unavailable. For example, for an architecture with 4 registers of
36292 4 bytes each, the following reply indicates to @value{GDBN} that
36293 registers 0 and 2 have not been collected, while registers 1 and 3
36294 have been collected, and both have zero value:
36298 <- @code{xxxxxxxx00000000xxxxxxxx00000000}
36305 @item G @var{XX@dots{}}
36306 @cindex @samp{G} packet
36307 Write general registers. @xref{read registers packet}, for a
36308 description of the @var{XX@dots{}} data.
36318 @item H @var{op} @var{thread-id}
36319 @cindex @samp{H} packet
36320 Set thread for subsequent operations (@samp{m}, @samp{M}, @samp{g},
36321 @samp{G}, et.al.). Depending on the operation to be performed, @var{op}
36322 should be @samp{c} for step and continue operations (note that this
36323 is deprecated, supporting the @samp{vCont} command is a better
36324 option), and @samp{g} for other operations. The thread designator
36325 @var{thread-id} has the format and interpretation described in
36326 @ref{thread-id syntax}.
36337 @c 'H': How restrictive (or permissive) is the thread model. If a
36338 @c thread is selected and stopped, are other threads allowed
36339 @c to continue to execute? As I mentioned above, I think the
36340 @c semantics of each command when a thread is selected must be
36341 @c described. For example:
36343 @c 'g': If the stub supports threads and a specific thread is
36344 @c selected, returns the register block from that thread;
36345 @c otherwise returns current registers.
36347 @c 'G' If the stub supports threads and a specific thread is
36348 @c selected, sets the registers of the register block of
36349 @c that thread; otherwise sets current registers.
36351 @item i @r{[}@var{addr}@r{[},@var{nnn}@r{]]}
36352 @anchor{cycle step packet}
36353 @cindex @samp{i} packet
36354 Step the remote target by a single clock cycle. If @samp{,@var{nnn}} is
36355 present, cycle step @var{nnn} cycles. If @var{addr} is present, cycle
36356 step starting at that address.
36359 @cindex @samp{I} packet
36360 Signal, then cycle step. @xref{step with signal packet}. @xref{cycle
36364 @cindex @samp{k} packet
36367 The exact effect of this packet is not specified.
36369 For a bare-metal target, it may power cycle or reset the target
36370 system. For that reason, the @samp{k} packet has no reply.
36372 For a single-process target, it may kill that process if possible.
36374 A multiple-process target may choose to kill just one process, or all
36375 that are under @value{GDBN}'s control. For more precise control, use
36376 the vKill packet (@pxref{vKill packet}).
36378 If the target system immediately closes the connection in response to
36379 @samp{k}, @value{GDBN} does not consider the lack of packet
36380 acknowledgment to be an error, and assumes the kill was successful.
36382 If connected using @kbd{target extended-remote}, and the target does
36383 not close the connection in response to a kill request, @value{GDBN}
36384 probes the target state as if a new connection was opened
36385 (@pxref{? packet}).
36387 @item m @var{addr},@var{length}
36388 @cindex @samp{m} packet
36389 Read @var{length} addressable memory units starting at address @var{addr}
36390 (@pxref{addressable memory unit}). Note that @var{addr} may not be aligned to
36391 any particular boundary.
36393 The stub need not use any particular size or alignment when gathering
36394 data from memory for the response; even if @var{addr} is word-aligned
36395 and @var{length} is a multiple of the word size, the stub is free to
36396 use byte accesses, or not. For this reason, this packet may not be
36397 suitable for accessing memory-mapped I/O devices.
36398 @cindex alignment of remote memory accesses
36399 @cindex size of remote memory accesses
36400 @cindex memory, alignment and size of remote accesses
36404 @item @var{XX@dots{}}
36405 Memory contents; each byte is transmitted as a two-digit hexadecimal number.
36406 The reply may contain fewer addressable memory units than requested if the
36407 server was able to read only part of the region of memory.
36412 @item M @var{addr},@var{length}:@var{XX@dots{}}
36413 @cindex @samp{M} packet
36414 Write @var{length} addressable memory units starting at address @var{addr}
36415 (@pxref{addressable memory unit}). The data is given by @var{XX@dots{}}; each
36416 byte is transmitted as a two-digit hexadecimal number.
36423 for an error (this includes the case where only part of the data was
36428 @cindex @samp{p} packet
36429 Read the value of register @var{n}; @var{n} is in hex.
36430 @xref{read registers packet}, for a description of how the returned
36431 register value is encoded.
36435 @item @var{XX@dots{}}
36436 the register's value
36440 Indicating an unrecognized @var{query}.
36443 @item P @var{n@dots{}}=@var{r@dots{}}
36444 @anchor{write register packet}
36445 @cindex @samp{P} packet
36446 Write register @var{n@dots{}} with value @var{r@dots{}}. The register
36447 number @var{n} is in hexadecimal, and @var{r@dots{}} contains two hex
36448 digits for each byte in the register (target byte order).
36458 @item q @var{name} @var{params}@dots{}
36459 @itemx Q @var{name} @var{params}@dots{}
36460 @cindex @samp{q} packet
36461 @cindex @samp{Q} packet
36462 General query (@samp{q}) and set (@samp{Q}). These packets are
36463 described fully in @ref{General Query Packets}.
36466 @cindex @samp{r} packet
36467 Reset the entire system.
36469 Don't use this packet; use the @samp{R} packet instead.
36472 @cindex @samp{R} packet
36473 Restart the program being debugged. The @var{XX}, while needed, is ignored.
36474 This packet is only available in extended mode (@pxref{extended mode}).
36476 The @samp{R} packet has no reply.
36478 @item s @r{[}@var{addr}@r{]}
36479 @cindex @samp{s} packet
36480 Single step, resuming at @var{addr}. If
36481 @var{addr} is omitted, resume at same address.
36483 This packet is deprecated for multi-threading support. @xref{vCont
36487 @xref{Stop Reply Packets}, for the reply specifications.
36489 @item S @var{sig}@r{[};@var{addr}@r{]}
36490 @anchor{step with signal packet}
36491 @cindex @samp{S} packet
36492 Step with signal. This is analogous to the @samp{C} packet, but
36493 requests a single-step, rather than a normal resumption of execution.
36495 This packet is deprecated for multi-threading support. @xref{vCont
36499 @xref{Stop Reply Packets}, for the reply specifications.
36501 @item t @var{addr}:@var{PP},@var{MM}
36502 @cindex @samp{t} packet
36503 Search backwards starting at address @var{addr} for a match with pattern
36504 @var{PP} and mask @var{MM}, both of which are are 4 byte long.
36505 There must be at least 3 digits in @var{addr}.
36507 @item T @var{thread-id}
36508 @cindex @samp{T} packet
36509 Find out if the thread @var{thread-id} is alive. @xref{thread-id syntax}.
36514 thread is still alive
36520 Packets starting with @samp{v} are identified by a multi-letter name,
36521 up to the first @samp{;} or @samp{?} (or the end of the packet).
36523 @item vAttach;@var{pid}
36524 @cindex @samp{vAttach} packet
36525 Attach to a new process with the specified process ID @var{pid}.
36526 The process ID is a
36527 hexadecimal integer identifying the process. In all-stop mode, all
36528 threads in the attached process are stopped; in non-stop mode, it may be
36529 attached without being stopped if that is supported by the target.
36531 @c In non-stop mode, on a successful vAttach, the stub should set the
36532 @c current thread to a thread of the newly-attached process. After
36533 @c attaching, GDB queries for the attached process's thread ID with qC.
36534 @c Also note that, from a user perspective, whether or not the
36535 @c target is stopped on attach in non-stop mode depends on whether you
36536 @c use the foreground or background version of the attach command, not
36537 @c on what vAttach does; GDB does the right thing with respect to either
36538 @c stopping or restarting threads.
36540 This packet is only available in extended mode (@pxref{extended mode}).
36546 @item @r{Any stop packet}
36547 for success in all-stop mode (@pxref{Stop Reply Packets})
36549 for success in non-stop mode (@pxref{Remote Non-Stop})
36552 @item vCont@r{[};@var{action}@r{[}:@var{thread-id}@r{]]}@dots{}
36553 @cindex @samp{vCont} packet
36554 @anchor{vCont packet}
36555 Resume the inferior, specifying different actions for each thread.
36557 For each inferior thread, the leftmost action with a matching
36558 @var{thread-id} is applied. Threads that don't match any action
36559 remain in their current state. Thread IDs are specified using the
36560 syntax described in @ref{thread-id syntax}. If multiprocess
36561 extensions (@pxref{multiprocess extensions}) are supported, actions
36562 can be specified to match all threads in a process by using the
36563 @samp{p@var{pid}.-1} form of the @var{thread-id}. An action with no
36564 @var{thread-id} matches all threads. Specifying no actions is an
36567 Currently supported actions are:
36573 Continue with signal @var{sig}. The signal @var{sig} should be two hex digits.
36577 Step with signal @var{sig}. The signal @var{sig} should be two hex digits.
36580 @item r @var{start},@var{end}
36581 Step once, and then keep stepping as long as the thread stops at
36582 addresses between @var{start} (inclusive) and @var{end} (exclusive).
36583 The remote stub reports a stop reply when either the thread goes out
36584 of the range or is stopped due to an unrelated reason, such as hitting
36585 a breakpoint. @xref{range stepping}.
36587 If the range is empty (@var{start} == @var{end}), then the action
36588 becomes equivalent to the @samp{s} action. In other words,
36589 single-step once, and report the stop (even if the stepped instruction
36590 jumps to @var{start}).
36592 (A stop reply may be sent at any point even if the PC is still within
36593 the stepping range; for example, it is valid to implement this packet
36594 in a degenerate way as a single instruction step operation.)
36598 The optional argument @var{addr} normally associated with the
36599 @samp{c}, @samp{C}, @samp{s}, and @samp{S} packets is
36600 not supported in @samp{vCont}.
36602 The @samp{t} action is only relevant in non-stop mode
36603 (@pxref{Remote Non-Stop}) and may be ignored by the stub otherwise.
36604 A stop reply should be generated for any affected thread not already stopped.
36605 When a thread is stopped by means of a @samp{t} action,
36606 the corresponding stop reply should indicate that the thread has stopped with
36607 signal @samp{0}, regardless of whether the target uses some other signal
36608 as an implementation detail.
36610 The server must ignore @samp{c}, @samp{C}, @samp{s}, @samp{S}, and
36611 @samp{r} actions for threads that are already running. Conversely,
36612 the server must ignore @samp{t} actions for threads that are already
36615 @emph{Note:} In non-stop mode, a thread is considered running until
36616 @value{GDBN} acknowleges an asynchronous stop notification for it with
36617 the @samp{vStopped} packet (@pxref{Remote Non-Stop}).
36619 The stub must support @samp{vCont} if it reports support for
36620 multiprocess extensions (@pxref{multiprocess extensions}).
36623 @xref{Stop Reply Packets}, for the reply specifications.
36626 @cindex @samp{vCont?} packet
36627 Request a list of actions supported by the @samp{vCont} packet.
36631 @item vCont@r{[};@var{action}@dots{}@r{]}
36632 The @samp{vCont} packet is supported. Each @var{action} is a supported
36633 command in the @samp{vCont} packet.
36635 The @samp{vCont} packet is not supported.
36638 @anchor{vCtrlC packet}
36640 @cindex @samp{vCtrlC} packet
36641 Interrupt remote target as if a control-C was pressed on the remote
36642 terminal. This is the equivalent to reacting to the @code{^C}
36643 (@samp{\003}, the control-C character) character in all-stop mode
36644 while the target is running, except this works in non-stop mode.
36645 @xref{interrupting remote targets}, for more info on the all-stop
36656 @item vFile:@var{operation}:@var{parameter}@dots{}
36657 @cindex @samp{vFile} packet
36658 Perform a file operation on the target system. For details,
36659 see @ref{Host I/O Packets}.
36661 @item vFlashErase:@var{addr},@var{length}
36662 @cindex @samp{vFlashErase} packet
36663 Direct the stub to erase @var{length} bytes of flash starting at
36664 @var{addr}. The region may enclose any number of flash blocks, but
36665 its start and end must fall on block boundaries, as indicated by the
36666 flash block size appearing in the memory map (@pxref{Memory Map
36667 Format}). @value{GDBN} groups flash memory programming operations
36668 together, and sends a @samp{vFlashDone} request after each group; the
36669 stub is allowed to delay erase operation until the @samp{vFlashDone}
36670 packet is received.
36680 @item vFlashWrite:@var{addr}:@var{XX@dots{}}
36681 @cindex @samp{vFlashWrite} packet
36682 Direct the stub to write data to flash address @var{addr}. The data
36683 is passed in binary form using the same encoding as for the @samp{X}
36684 packet (@pxref{Binary Data}). The memory ranges specified by
36685 @samp{vFlashWrite} packets preceding a @samp{vFlashDone} packet must
36686 not overlap, and must appear in order of increasing addresses
36687 (although @samp{vFlashErase} packets for higher addresses may already
36688 have been received; the ordering is guaranteed only between
36689 @samp{vFlashWrite} packets). If a packet writes to an address that was
36690 neither erased by a preceding @samp{vFlashErase} packet nor by some other
36691 target-specific method, the results are unpredictable.
36699 for vFlashWrite addressing non-flash memory
36705 @cindex @samp{vFlashDone} packet
36706 Indicate to the stub that flash programming operation is finished.
36707 The stub is permitted to delay or batch the effects of a group of
36708 @samp{vFlashErase} and @samp{vFlashWrite} packets until a
36709 @samp{vFlashDone} packet is received. The contents of the affected
36710 regions of flash memory are unpredictable until the @samp{vFlashDone}
36711 request is completed.
36713 @item vKill;@var{pid}
36714 @cindex @samp{vKill} packet
36715 @anchor{vKill packet}
36716 Kill the process with the specified process ID @var{pid}, which is a
36717 hexadecimal integer identifying the process. This packet is used in
36718 preference to @samp{k} when multiprocess protocol extensions are
36719 supported; see @ref{multiprocess extensions}.
36729 @item vMustReplyEmpty
36730 @cindex @samp{vMustReplyEmpty} packet
36731 The correct reply to an unknown @samp{v} packet is to return the empty
36732 string, however, some older versions of @command{gdbserver} would
36733 incorrectly return @samp{OK} for unknown @samp{v} packets.
36735 The @samp{vMustReplyEmpty} is used as a feature test to check how
36736 @command{gdbserver} handles unknown packets, it is important that this
36737 packet be handled in the same way as other unknown @samp{v} packets.
36738 If this packet is handled differently to other unknown @samp{v}
36739 packets then it is possile that @value{GDBN} may run into problems in
36740 other areas, specifically around use of @samp{vFile:setfs:}.
36742 @item vRun;@var{filename}@r{[};@var{argument}@r{]}@dots{}
36743 @cindex @samp{vRun} packet
36744 Run the program @var{filename}, passing it each @var{argument} on its
36745 command line. The file and arguments are hex-encoded strings. If
36746 @var{filename} is an empty string, the stub may use a default program
36747 (e.g.@: the last program run). The program is created in the stopped
36750 @c FIXME: What about non-stop mode?
36752 This packet is only available in extended mode (@pxref{extended mode}).
36758 @item @r{Any stop packet}
36759 for success (@pxref{Stop Reply Packets})
36763 @cindex @samp{vStopped} packet
36764 @xref{Notification Packets}.
36766 @item X @var{addr},@var{length}:@var{XX@dots{}}
36768 @cindex @samp{X} packet
36769 Write data to memory, where the data is transmitted in binary.
36770 Memory is specified by its address @var{addr} and number of addressable memory
36771 units @var{length} (@pxref{addressable memory unit});
36772 @samp{@var{XX}@dots{}} is binary data (@pxref{Binary Data}).
36782 @item z @var{type},@var{addr},@var{kind}
36783 @itemx Z @var{type},@var{addr},@var{kind}
36784 @anchor{insert breakpoint or watchpoint packet}
36785 @cindex @samp{z} packet
36786 @cindex @samp{Z} packets
36787 Insert (@samp{Z}) or remove (@samp{z}) a @var{type} breakpoint or
36788 watchpoint starting at address @var{address} of kind @var{kind}.
36790 Each breakpoint and watchpoint packet @var{type} is documented
36793 @emph{Implementation notes: A remote target shall return an empty string
36794 for an unrecognized breakpoint or watchpoint packet @var{type}. A
36795 remote target shall support either both or neither of a given
36796 @samp{Z@var{type}@dots{}} and @samp{z@var{type}@dots{}} packet pair. To
36797 avoid potential problems with duplicate packets, the operations should
36798 be implemented in an idempotent way.}
36800 @item z0,@var{addr},@var{kind}
36801 @itemx Z0,@var{addr},@var{kind}@r{[};@var{cond_list}@dots{}@r{]}@r{[};cmds:@var{persist},@var{cmd_list}@dots{}@r{]}
36802 @cindex @samp{z0} packet
36803 @cindex @samp{Z0} packet
36804 Insert (@samp{Z0}) or remove (@samp{z0}) a software breakpoint at address
36805 @var{addr} of type @var{kind}.
36807 A software breakpoint is implemented by replacing the instruction at
36808 @var{addr} with a software breakpoint or trap instruction. The
36809 @var{kind} is target-specific and typically indicates the size of the
36810 breakpoint in bytes that should be inserted. E.g., the @sc{arm} and
36811 @sc{mips} can insert either a 2 or 4 byte breakpoint. Some
36812 architectures have additional meanings for @var{kind}
36813 (@pxref{Architecture-Specific Protocol Details}); if no
36814 architecture-specific value is being used, it should be @samp{0}.
36815 @var{kind} is hex-encoded. @var{cond_list} is an optional list of
36816 conditional expressions in bytecode form that should be evaluated on
36817 the target's side. These are the conditions that should be taken into
36818 consideration when deciding if the breakpoint trigger should be
36819 reported back to @value{GDBN}.
36821 See also the @samp{swbreak} stop reason (@pxref{swbreak stop reason})
36822 for how to best report a software breakpoint event to @value{GDBN}.
36824 The @var{cond_list} parameter is comprised of a series of expressions,
36825 concatenated without separators. Each expression has the following form:
36829 @item X @var{len},@var{expr}
36830 @var{len} is the length of the bytecode expression and @var{expr} is the
36831 actual conditional expression in bytecode form.
36835 The optional @var{cmd_list} parameter introduces commands that may be
36836 run on the target, rather than being reported back to @value{GDBN}.
36837 The parameter starts with a numeric flag @var{persist}; if the flag is
36838 nonzero, then the breakpoint may remain active and the commands
36839 continue to be run even when @value{GDBN} disconnects from the target.
36840 Following this flag is a series of expressions concatenated with no
36841 separators. Each expression has the following form:
36845 @item X @var{len},@var{expr}
36846 @var{len} is the length of the bytecode expression and @var{expr} is the
36847 actual commands expression in bytecode form.
36851 @emph{Implementation note: It is possible for a target to copy or move
36852 code that contains software breakpoints (e.g., when implementing
36853 overlays). The behavior of this packet, in the presence of such a
36854 target, is not defined.}
36866 @item z1,@var{addr},@var{kind}
36867 @itemx Z1,@var{addr},@var{kind}@r{[};@var{cond_list}@dots{}@r{]}@r{[};cmds:@var{persist},@var{cmd_list}@dots{}@r{]}
36868 @cindex @samp{z1} packet
36869 @cindex @samp{Z1} packet
36870 Insert (@samp{Z1}) or remove (@samp{z1}) a hardware breakpoint at
36871 address @var{addr}.
36873 A hardware breakpoint is implemented using a mechanism that is not
36874 dependent on being able to modify the target's memory. The
36875 @var{kind}, @var{cond_list}, and @var{cmd_list} arguments have the
36876 same meaning as in @samp{Z0} packets.
36878 @emph{Implementation note: A hardware breakpoint is not affected by code
36891 @item z2,@var{addr},@var{kind}
36892 @itemx Z2,@var{addr},@var{kind}
36893 @cindex @samp{z2} packet
36894 @cindex @samp{Z2} packet
36895 Insert (@samp{Z2}) or remove (@samp{z2}) a write watchpoint at @var{addr}.
36896 The number of bytes to watch is specified by @var{kind}.
36908 @item z3,@var{addr},@var{kind}
36909 @itemx Z3,@var{addr},@var{kind}
36910 @cindex @samp{z3} packet
36911 @cindex @samp{Z3} packet
36912 Insert (@samp{Z3}) or remove (@samp{z3}) a read watchpoint at @var{addr}.
36913 The number of bytes to watch is specified by @var{kind}.
36925 @item z4,@var{addr},@var{kind}
36926 @itemx Z4,@var{addr},@var{kind}
36927 @cindex @samp{z4} packet
36928 @cindex @samp{Z4} packet
36929 Insert (@samp{Z4}) or remove (@samp{z4}) an access watchpoint at @var{addr}.
36930 The number of bytes to watch is specified by @var{kind}.
36944 @node Stop Reply Packets
36945 @section Stop Reply Packets
36946 @cindex stop reply packets
36948 The @samp{C}, @samp{c}, @samp{S}, @samp{s}, @samp{vCont},
36949 @samp{vAttach}, @samp{vRun}, @samp{vStopped}, and @samp{?} packets can
36950 receive any of the below as a reply. Except for @samp{?}
36951 and @samp{vStopped}, that reply is only returned
36952 when the target halts. In the below the exact meaning of @dfn{signal
36953 number} is defined by the header @file{include/gdb/signals.h} in the
36954 @value{GDBN} source code.
36956 In non-stop mode, the server will simply reply @samp{OK} to commands
36957 such as @samp{vCont}; any stop will be the subject of a future
36958 notification. @xref{Remote Non-Stop}.
36960 As in the description of request packets, we include spaces in the
36961 reply templates for clarity; these are not part of the reply packet's
36962 syntax. No @value{GDBN} stop reply packet uses spaces to separate its
36968 The program received signal number @var{AA} (a two-digit hexadecimal
36969 number). This is equivalent to a @samp{T} response with no
36970 @var{n}:@var{r} pairs.
36972 @item T @var{AA} @var{n1}:@var{r1};@var{n2}:@var{r2};@dots{}
36973 @cindex @samp{T} packet reply
36974 The program received signal number @var{AA} (a two-digit hexadecimal
36975 number). This is equivalent to an @samp{S} response, except that the
36976 @samp{@var{n}:@var{r}} pairs can carry values of important registers
36977 and other information directly in the stop reply packet, reducing
36978 round-trip latency. Single-step and breakpoint traps are reported
36979 this way. Each @samp{@var{n}:@var{r}} pair is interpreted as follows:
36983 If @var{n} is a hexadecimal number, it is a register number, and the
36984 corresponding @var{r} gives that register's value. The data @var{r} is a
36985 series of bytes in target byte order, with each byte given by a
36986 two-digit hex number.
36989 If @var{n} is @samp{thread}, then @var{r} is the @var{thread-id} of
36990 the stopped thread, as specified in @ref{thread-id syntax}.
36993 If @var{n} is @samp{core}, then @var{r} is the hexadecimal number of
36994 the core on which the stop event was detected.
36997 If @var{n} is a recognized @dfn{stop reason}, it describes a more
36998 specific event that stopped the target. The currently defined stop
36999 reasons are listed below. The @var{aa} should be @samp{05}, the trap
37000 signal. At most one stop reason should be present.
37003 Otherwise, @value{GDBN} should ignore this @samp{@var{n}:@var{r}} pair
37004 and go on to the next; this allows us to extend the protocol in the
37008 The currently defined stop reasons are:
37014 The packet indicates a watchpoint hit, and @var{r} is the data address, in
37017 @item syscall_entry
37018 @itemx syscall_return
37019 The packet indicates a syscall entry or return, and @var{r} is the
37020 syscall number, in hex.
37022 @cindex shared library events, remote reply
37024 The packet indicates that the loaded libraries have changed.
37025 @value{GDBN} should use @samp{qXfer:libraries:read} to fetch a new
37026 list of loaded libraries. The @var{r} part is ignored.
37028 @cindex replay log events, remote reply
37030 The packet indicates that the target cannot continue replaying
37031 logged execution events, because it has reached the end (or the
37032 beginning when executing backward) of the log. The value of @var{r}
37033 will be either @samp{begin} or @samp{end}. @xref{Reverse Execution},
37034 for more information.
37037 @anchor{swbreak stop reason}
37038 The packet indicates a software breakpoint instruction was executed,
37039 irrespective of whether it was @value{GDBN} that planted the
37040 breakpoint or the breakpoint is hardcoded in the program. The @var{r}
37041 part must be left empty.
37043 On some architectures, such as x86, at the architecture level, when a
37044 breakpoint instruction executes the program counter points at the
37045 breakpoint address plus an offset. On such targets, the stub is
37046 responsible for adjusting the PC to point back at the breakpoint
37049 This packet should not be sent by default; older @value{GDBN} versions
37050 did not support it. @value{GDBN} requests it, by supplying an
37051 appropriate @samp{qSupported} feature (@pxref{qSupported}). The
37052 remote stub must also supply the appropriate @samp{qSupported} feature
37053 indicating support.
37055 This packet is required for correct non-stop mode operation.
37058 The packet indicates the target stopped for a hardware breakpoint.
37059 The @var{r} part must be left empty.
37061 The same remarks about @samp{qSupported} and non-stop mode above
37064 @cindex fork events, remote reply
37066 The packet indicates that @code{fork} was called, and @var{r}
37067 is the thread ID of the new child process. Refer to
37068 @ref{thread-id syntax} for the format of the @var{thread-id}
37069 field. This packet is only applicable to targets that support
37072 This packet should not be sent by default; older @value{GDBN} versions
37073 did not support it. @value{GDBN} requests it, by supplying an
37074 appropriate @samp{qSupported} feature (@pxref{qSupported}). The
37075 remote stub must also supply the appropriate @samp{qSupported} feature
37076 indicating support.
37078 @cindex vfork events, remote reply
37080 The packet indicates that @code{vfork} was called, and @var{r}
37081 is the thread ID of the new child process. Refer to
37082 @ref{thread-id syntax} for the format of the @var{thread-id}
37083 field. This packet is only applicable to targets that support
37086 This packet should not be sent by default; older @value{GDBN} versions
37087 did not support it. @value{GDBN} requests it, by supplying an
37088 appropriate @samp{qSupported} feature (@pxref{qSupported}). The
37089 remote stub must also supply the appropriate @samp{qSupported} feature
37090 indicating support.
37092 @cindex vforkdone events, remote reply
37094 The packet indicates that a child process created by a vfork
37095 has either called @code{exec} or terminated, so that the
37096 address spaces of the parent and child process are no longer
37097 shared. The @var{r} part is ignored. This packet is only
37098 applicable to targets that support vforkdone events.
37100 This packet should not be sent by default; older @value{GDBN} versions
37101 did not support it. @value{GDBN} requests it, by supplying an
37102 appropriate @samp{qSupported} feature (@pxref{qSupported}). The
37103 remote stub must also supply the appropriate @samp{qSupported} feature
37104 indicating support.
37106 @cindex exec events, remote reply
37108 The packet indicates that @code{execve} was called, and @var{r}
37109 is the absolute pathname of the file that was executed, in hex.
37110 This packet is only applicable to targets that support exec events.
37112 This packet should not be sent by default; older @value{GDBN} versions
37113 did not support it. @value{GDBN} requests it, by supplying an
37114 appropriate @samp{qSupported} feature (@pxref{qSupported}). The
37115 remote stub must also supply the appropriate @samp{qSupported} feature
37116 indicating support.
37118 @cindex thread create event, remote reply
37119 @anchor{thread create event}
37121 The packet indicates that the thread was just created. The new thread
37122 is stopped until @value{GDBN} sets it running with a resumption packet
37123 (@pxref{vCont packet}). This packet should not be sent by default;
37124 @value{GDBN} requests it with the @ref{QThreadEvents} packet. See
37125 also the @samp{w} (@pxref{thread exit event}) remote reply below. The
37126 @var{r} part is ignored.
37131 @itemx W @var{AA} ; process:@var{pid}
37132 The process exited, and @var{AA} is the exit status. This is only
37133 applicable to certain targets.
37135 The second form of the response, including the process ID of the
37136 exited process, can be used only when @value{GDBN} has reported
37137 support for multiprocess protocol extensions; see @ref{multiprocess
37138 extensions}. Both @var{AA} and @var{pid} are formatted as big-endian
37142 @itemx X @var{AA} ; process:@var{pid}
37143 The process terminated with signal @var{AA}.
37145 The second form of the response, including the process ID of the
37146 terminated process, can be used only when @value{GDBN} has reported
37147 support for multiprocess protocol extensions; see @ref{multiprocess
37148 extensions}. Both @var{AA} and @var{pid} are formatted as big-endian
37151 @anchor{thread exit event}
37152 @cindex thread exit event, remote reply
37153 @item w @var{AA} ; @var{tid}
37155 The thread exited, and @var{AA} is the exit status. This response
37156 should not be sent by default; @value{GDBN} requests it with the
37157 @ref{QThreadEvents} packet. See also @ref{thread create event} above.
37158 @var{AA} is formatted as a big-endian hex string.
37161 There are no resumed threads left in the target. In other words, even
37162 though the process is alive, the last resumed thread has exited. For
37163 example, say the target process has two threads: thread 1 and thread
37164 2. The client leaves thread 1 stopped, and resumes thread 2, which
37165 subsequently exits. At this point, even though the process is still
37166 alive, and thus no @samp{W} stop reply is sent, no thread is actually
37167 executing either. The @samp{N} stop reply thus informs the client
37168 that it can stop waiting for stop replies. This packet should not be
37169 sent by default; older @value{GDBN} versions did not support it.
37170 @value{GDBN} requests it, by supplying an appropriate
37171 @samp{qSupported} feature (@pxref{qSupported}). The remote stub must
37172 also supply the appropriate @samp{qSupported} feature indicating
37175 @item O @var{XX}@dots{}
37176 @samp{@var{XX}@dots{}} is hex encoding of @sc{ascii} data, to be
37177 written as the program's console output. This can happen at any time
37178 while the program is running and the debugger should continue to wait
37179 for @samp{W}, @samp{T}, etc. This reply is not permitted in non-stop mode.
37181 @item F @var{call-id},@var{parameter}@dots{}
37182 @var{call-id} is the identifier which says which host system call should
37183 be called. This is just the name of the function. Translation into the
37184 correct system call is only applicable as it's defined in @value{GDBN}.
37185 @xref{File-I/O Remote Protocol Extension}, for a list of implemented
37188 @samp{@var{parameter}@dots{}} is a list of parameters as defined for
37189 this very system call.
37191 The target replies with this packet when it expects @value{GDBN} to
37192 call a host system call on behalf of the target. @value{GDBN} replies
37193 with an appropriate @samp{F} packet and keeps up waiting for the next
37194 reply packet from the target. The latest @samp{C}, @samp{c}, @samp{S}
37195 or @samp{s} action is expected to be continued. @xref{File-I/O Remote
37196 Protocol Extension}, for more details.
37200 @node General Query Packets
37201 @section General Query Packets
37202 @cindex remote query requests
37204 Packets starting with @samp{q} are @dfn{general query packets};
37205 packets starting with @samp{Q} are @dfn{general set packets}. General
37206 query and set packets are a semi-unified form for retrieving and
37207 sending information to and from the stub.
37209 The initial letter of a query or set packet is followed by a name
37210 indicating what sort of thing the packet applies to. For example,
37211 @value{GDBN} may use a @samp{qSymbol} packet to exchange symbol
37212 definitions with the stub. These packet names follow some
37217 The name must not contain commas, colons or semicolons.
37219 Most @value{GDBN} query and set packets have a leading upper case
37222 The names of custom vendor packets should use a company prefix, in
37223 lower case, followed by a period. For example, packets designed at
37224 the Acme Corporation might begin with @samp{qacme.foo} (for querying
37225 foos) or @samp{Qacme.bar} (for setting bars).
37228 The name of a query or set packet should be separated from any
37229 parameters by a @samp{:}; the parameters themselves should be
37230 separated by @samp{,} or @samp{;}. Stubs must be careful to match the
37231 full packet name, and check for a separator or the end of the packet,
37232 in case two packet names share a common prefix. New packets should not begin
37233 with @samp{qC}, @samp{qP}, or @samp{qL}@footnote{The @samp{qP} and @samp{qL}
37234 packets predate these conventions, and have arguments without any terminator
37235 for the packet name; we suspect they are in widespread use in places that
37236 are difficult to upgrade. The @samp{qC} packet has no arguments, but some
37237 existing stubs (e.g.@: RedBoot) are known to not check for the end of the
37240 Like the descriptions of the other packets, each description here
37241 has a template showing the packet's overall syntax, followed by an
37242 explanation of the packet's meaning. We include spaces in some of the
37243 templates for clarity; these are not part of the packet's syntax. No
37244 @value{GDBN} packet uses spaces to separate its components.
37246 Here are the currently defined query and set packets:
37252 Turn on or off the agent as a helper to perform some debugging operations
37253 delegated from @value{GDBN} (@pxref{Control Agent}).
37255 @item QAllow:@var{op}:@var{val}@dots{}
37256 @cindex @samp{QAllow} packet
37257 Specify which operations @value{GDBN} expects to request of the
37258 target, as a semicolon-separated list of operation name and value
37259 pairs. Possible values for @var{op} include @samp{WriteReg},
37260 @samp{WriteMem}, @samp{InsertBreak}, @samp{InsertTrace},
37261 @samp{InsertFastTrace}, and @samp{Stop}. @var{val} is either 0,
37262 indicating that @value{GDBN} will not request the operation, or 1,
37263 indicating that it may. (The target can then use this to set up its
37264 own internals optimally, for instance if the debugger never expects to
37265 insert breakpoints, it may not need to install its own trap handler.)
37268 @cindex current thread, remote request
37269 @cindex @samp{qC} packet
37270 Return the current thread ID.
37274 @item QC @var{thread-id}
37275 Where @var{thread-id} is a thread ID as documented in
37276 @ref{thread-id syntax}.
37277 @item @r{(anything else)}
37278 Any other reply implies the old thread ID.
37281 @item qCRC:@var{addr},@var{length}
37282 @cindex CRC of memory block, remote request
37283 @cindex @samp{qCRC} packet
37284 @anchor{qCRC packet}
37285 Compute the CRC checksum of a block of memory using CRC-32 defined in
37286 IEEE 802.3. The CRC is computed byte at a time, taking the most
37287 significant bit of each byte first. The initial pattern code
37288 @code{0xffffffff} is used to ensure leading zeros affect the CRC.
37290 @emph{Note:} This is the same CRC used in validating separate debug
37291 files (@pxref{Separate Debug Files, , Debugging Information in Separate
37292 Files}). However the algorithm is slightly different. When validating
37293 separate debug files, the CRC is computed taking the @emph{least}
37294 significant bit of each byte first, and the final result is inverted to
37295 detect trailing zeros.
37300 An error (such as memory fault)
37301 @item C @var{crc32}
37302 The specified memory region's checksum is @var{crc32}.
37305 @item QDisableRandomization:@var{value}
37306 @cindex disable address space randomization, remote request
37307 @cindex @samp{QDisableRandomization} packet
37308 Some target operating systems will randomize the virtual address space
37309 of the inferior process as a security feature, but provide a feature
37310 to disable such randomization, e.g.@: to allow for a more deterministic
37311 debugging experience. On such systems, this packet with a @var{value}
37312 of 1 directs the target to disable address space randomization for
37313 processes subsequently started via @samp{vRun} packets, while a packet
37314 with a @var{value} of 0 tells the target to enable address space
37317 This packet is only available in extended mode (@pxref{extended mode}).
37322 The request succeeded.
37325 An error occurred. The error number @var{nn} is given as hex digits.
37328 An empty reply indicates that @samp{QDisableRandomization} is not supported
37332 This packet is not probed by default; the remote stub must request it,
37333 by supplying an appropriate @samp{qSupported} response (@pxref{qSupported}).
37334 This should only be done on targets that actually support disabling
37335 address space randomization.
37337 @item QStartupWithShell:@var{value}
37338 @cindex startup with shell, remote request
37339 @cindex @samp{QStartupWithShell} packet
37340 On UNIX-like targets, it is possible to start the inferior using a
37341 shell program. This is the default behavior on both @value{GDBN} and
37342 @command{gdbserver} (@pxref{set startup-with-shell}). This packet is
37343 used to inform @command{gdbserver} whether it should start the
37344 inferior using a shell or not.
37346 If @var{value} is @samp{0}, @command{gdbserver} will not use a shell
37347 to start the inferior. If @var{value} is @samp{1},
37348 @command{gdbserver} will use a shell to start the inferior. All other
37349 values are considered an error.
37351 This packet is only available in extended mode (@pxref{extended
37357 The request succeeded.
37360 An error occurred. The error number @var{nn} is given as hex digits.
37363 This packet is not probed by default; the remote stub must request it,
37364 by supplying an appropriate @samp{qSupported} response
37365 (@pxref{qSupported}). This should only be done on targets that
37366 actually support starting the inferior using a shell.
37368 Use of this packet is controlled by the @code{set startup-with-shell}
37369 command; @pxref{set startup-with-shell}.
37371 @item QEnvironmentHexEncoded:@var{hex-value}
37372 @anchor{QEnvironmentHexEncoded}
37373 @cindex set environment variable, remote request
37374 @cindex @samp{QEnvironmentHexEncoded} packet
37375 On UNIX-like targets, it is possible to set environment variables that
37376 will be passed to the inferior during the startup process. This
37377 packet is used to inform @command{gdbserver} of an environment
37378 variable that has been defined by the user on @value{GDBN} (@pxref{set
37381 The packet is composed by @var{hex-value}, an hex encoded
37382 representation of the @var{name=value} format representing an
37383 environment variable. The name of the environment variable is
37384 represented by @var{name}, and the value to be assigned to the
37385 environment variable is represented by @var{value}. If the variable
37386 has no value (i.e., the value is @code{null}), then @var{value} will
37389 This packet is only available in extended mode (@pxref{extended
37395 The request succeeded.
37398 This packet is not probed by default; the remote stub must request it,
37399 by supplying an appropriate @samp{qSupported} response
37400 (@pxref{qSupported}). This should only be done on targets that
37401 actually support passing environment variables to the starting
37404 This packet is related to the @code{set environment} command;
37405 @pxref{set environment}.
37407 @item QEnvironmentUnset:@var{hex-value}
37408 @anchor{QEnvironmentUnset}
37409 @cindex unset environment variable, remote request
37410 @cindex @samp{QEnvironmentUnset} packet
37411 On UNIX-like targets, it is possible to unset environment variables
37412 before starting the inferior in the remote target. This packet is
37413 used to inform @command{gdbserver} of an environment variable that has
37414 been unset by the user on @value{GDBN} (@pxref{unset environment}).
37416 The packet is composed by @var{hex-value}, an hex encoded
37417 representation of the name of the environment variable to be unset.
37419 This packet is only available in extended mode (@pxref{extended
37425 The request succeeded.
37428 This packet is not probed by default; the remote stub must request it,
37429 by supplying an appropriate @samp{qSupported} response
37430 (@pxref{qSupported}). This should only be done on targets that
37431 actually support passing environment variables to the starting
37434 This packet is related to the @code{unset environment} command;
37435 @pxref{unset environment}.
37437 @item QEnvironmentReset
37438 @anchor{QEnvironmentReset}
37439 @cindex reset environment, remote request
37440 @cindex @samp{QEnvironmentReset} packet
37441 On UNIX-like targets, this packet is used to reset the state of
37442 environment variables in the remote target before starting the
37443 inferior. In this context, reset means unsetting all environment
37444 variables that were previously set by the user (i.e., were not
37445 initially present in the environment). It is sent to
37446 @command{gdbserver} before the @samp{QEnvironmentHexEncoded}
37447 (@pxref{QEnvironmentHexEncoded}) and the @samp{QEnvironmentUnset}
37448 (@pxref{QEnvironmentUnset}) packets.
37450 This packet is only available in extended mode (@pxref{extended
37456 The request succeeded.
37459 This packet is not probed by default; the remote stub must request it,
37460 by supplying an appropriate @samp{qSupported} response
37461 (@pxref{qSupported}). This should only be done on targets that
37462 actually support passing environment variables to the starting
37465 @item QSetWorkingDir:@r{[}@var{directory}@r{]}
37466 @anchor{QSetWorkingDir packet}
37467 @cindex set working directory, remote request
37468 @cindex @samp{QSetWorkingDir} packet
37469 This packet is used to inform the remote server of the intended
37470 current working directory for programs that are going to be executed.
37472 The packet is composed by @var{directory}, an hex encoded
37473 representation of the directory that the remote inferior will use as
37474 its current working directory. If @var{directory} is an empty string,
37475 the remote server should reset the inferior's current working
37476 directory to its original, empty value.
37478 This packet is only available in extended mode (@pxref{extended
37484 The request succeeded.
37488 @itemx qsThreadInfo
37489 @cindex list active threads, remote request
37490 @cindex @samp{qfThreadInfo} packet
37491 @cindex @samp{qsThreadInfo} packet
37492 Obtain a list of all active thread IDs from the target (OS). Since there
37493 may be too many active threads to fit into one reply packet, this query
37494 works iteratively: it may require more than one query/reply sequence to
37495 obtain the entire list of threads. The first query of the sequence will
37496 be the @samp{qfThreadInfo} query; subsequent queries in the
37497 sequence will be the @samp{qsThreadInfo} query.
37499 NOTE: This packet replaces the @samp{qL} query (see below).
37503 @item m @var{thread-id}
37505 @item m @var{thread-id},@var{thread-id}@dots{}
37506 a comma-separated list of thread IDs
37508 (lower case letter @samp{L}) denotes end of list.
37511 In response to each query, the target will reply with a list of one or
37512 more thread IDs, separated by commas.
37513 @value{GDBN} will respond to each reply with a request for more thread
37514 ids (using the @samp{qs} form of the query), until the target responds
37515 with @samp{l} (lower-case ell, for @dfn{last}).
37516 Refer to @ref{thread-id syntax}, for the format of the @var{thread-id}
37519 @emph{Note: @value{GDBN} will send the @code{qfThreadInfo} query during the
37520 initial connection with the remote target, and the very first thread ID
37521 mentioned in the reply will be stopped by @value{GDBN} in a subsequent
37522 message. Therefore, the stub should ensure that the first thread ID in
37523 the @code{qfThreadInfo} reply is suitable for being stopped by @value{GDBN}.}
37525 @item qGetTLSAddr:@var{thread-id},@var{offset},@var{lm}
37526 @cindex get thread-local storage address, remote request
37527 @cindex @samp{qGetTLSAddr} packet
37528 Fetch the address associated with thread local storage specified
37529 by @var{thread-id}, @var{offset}, and @var{lm}.
37531 @var{thread-id} is the thread ID associated with the
37532 thread for which to fetch the TLS address. @xref{thread-id syntax}.
37534 @var{offset} is the (big endian, hex encoded) offset associated with the
37535 thread local variable. (This offset is obtained from the debug
37536 information associated with the variable.)
37538 @var{lm} is the (big endian, hex encoded) OS/ABI-specific encoding of the
37539 load module associated with the thread local storage. For example,
37540 a @sc{gnu}/Linux system will pass the link map address of the shared
37541 object associated with the thread local storage under consideration.
37542 Other operating environments may choose to represent the load module
37543 differently, so the precise meaning of this parameter will vary.
37547 @item @var{XX}@dots{}
37548 Hex encoded (big endian) bytes representing the address of the thread
37549 local storage requested.
37552 An error occurred. The error number @var{nn} is given as hex digits.
37555 An empty reply indicates that @samp{qGetTLSAddr} is not supported by the stub.
37558 @item qGetTIBAddr:@var{thread-id}
37559 @cindex get thread information block address
37560 @cindex @samp{qGetTIBAddr} packet
37561 Fetch address of the Windows OS specific Thread Information Block.
37563 @var{thread-id} is the thread ID associated with the thread.
37567 @item @var{XX}@dots{}
37568 Hex encoded (big endian) bytes representing the linear address of the
37569 thread information block.
37572 An error occured. This means that either the thread was not found, or the
37573 address could not be retrieved.
37576 An empty reply indicates that @samp{qGetTIBAddr} is not supported by the stub.
37579 @item qL @var{startflag} @var{threadcount} @var{nextthread}
37580 Obtain thread information from RTOS. Where: @var{startflag} (one hex
37581 digit) is one to indicate the first query and zero to indicate a
37582 subsequent query; @var{threadcount} (two hex digits) is the maximum
37583 number of threads the response packet can contain; and @var{nextthread}
37584 (eight hex digits), for subsequent queries (@var{startflag} is zero), is
37585 returned in the response as @var{argthread}.
37587 Don't use this packet; use the @samp{qfThreadInfo} query instead (see above).
37591 @item qM @var{count} @var{done} @var{argthread} @var{thread}@dots{}
37592 Where: @var{count} (two hex digits) is the number of threads being
37593 returned; @var{done} (one hex digit) is zero to indicate more threads
37594 and one indicates no further threads; @var{argthreadid} (eight hex
37595 digits) is @var{nextthread} from the request packet; @var{thread}@dots{}
37596 is a sequence of thread IDs, @var{threadid} (eight hex
37597 digits), from the target. See @code{remote.c:parse_threadlist_response()}.
37601 @cindex section offsets, remote request
37602 @cindex @samp{qOffsets} packet
37603 Get section offsets that the target used when relocating the downloaded
37608 @item Text=@var{xxx};Data=@var{yyy}@r{[};Bss=@var{zzz}@r{]}
37609 Relocate the @code{Text} section by @var{xxx} from its original address.
37610 Relocate the @code{Data} section by @var{yyy} from its original address.
37611 If the object file format provides segment information (e.g.@: @sc{elf}
37612 @samp{PT_LOAD} program headers), @value{GDBN} will relocate entire
37613 segments by the supplied offsets.
37615 @emph{Note: while a @code{Bss} offset may be included in the response,
37616 @value{GDBN} ignores this and instead applies the @code{Data} offset
37617 to the @code{Bss} section.}
37619 @item TextSeg=@var{xxx}@r{[};DataSeg=@var{yyy}@r{]}
37620 Relocate the first segment of the object file, which conventionally
37621 contains program code, to a starting address of @var{xxx}. If
37622 @samp{DataSeg} is specified, relocate the second segment, which
37623 conventionally contains modifiable data, to a starting address of
37624 @var{yyy}. @value{GDBN} will report an error if the object file
37625 does not contain segment information, or does not contain at least
37626 as many segments as mentioned in the reply. Extra segments are
37627 kept at fixed offsets relative to the last relocated segment.
37630 @item qP @var{mode} @var{thread-id}
37631 @cindex thread information, remote request
37632 @cindex @samp{qP} packet
37633 Returns information on @var{thread-id}. Where: @var{mode} is a hex
37634 encoded 32 bit mode; @var{thread-id} is a thread ID
37635 (@pxref{thread-id syntax}).
37637 Don't use this packet; use the @samp{qThreadExtraInfo} query instead
37640 Reply: see @code{remote.c:remote_unpack_thread_info_response()}.
37644 @cindex non-stop mode, remote request
37645 @cindex @samp{QNonStop} packet
37647 Enter non-stop (@samp{QNonStop:1}) or all-stop (@samp{QNonStop:0}) mode.
37648 @xref{Remote Non-Stop}, for more information.
37653 The request succeeded.
37656 An error occurred. The error number @var{nn} is given as hex digits.
37659 An empty reply indicates that @samp{QNonStop} is not supported by
37663 This packet is not probed by default; the remote stub must request it,
37664 by supplying an appropriate @samp{qSupported} response (@pxref{qSupported}).
37665 Use of this packet is controlled by the @code{set non-stop} command;
37666 @pxref{Non-Stop Mode}.
37668 @item QCatchSyscalls:1 @r{[};@var{sysno}@r{]}@dots{}
37669 @itemx QCatchSyscalls:0
37670 @cindex catch syscalls from inferior, remote request
37671 @cindex @samp{QCatchSyscalls} packet
37672 @anchor{QCatchSyscalls}
37673 Enable (@samp{QCatchSyscalls:1}) or disable (@samp{QCatchSyscalls:0})
37674 catching syscalls from the inferior process.
37676 For @samp{QCatchSyscalls:1}, each listed syscall @var{sysno} (encoded
37677 in hex) should be reported to @value{GDBN}. If no syscall @var{sysno}
37678 is listed, every system call should be reported.
37680 Note that if a syscall not in the list is reported, @value{GDBN} will
37681 still filter the event according to its own list from all corresponding
37682 @code{catch syscall} commands. However, it is more efficient to only
37683 report the requested syscalls.
37685 Multiple @samp{QCatchSyscalls:1} packets do not combine; any earlier
37686 @samp{QCatchSyscalls:1} list is completely replaced by the new list.
37688 If the inferior process execs, the state of @samp{QCatchSyscalls} is
37689 kept for the new process too. On targets where exec may affect syscall
37690 numbers, for example with exec between 32 and 64-bit processes, the
37691 client should send a new packet with the new syscall list.
37696 The request succeeded.
37699 An error occurred. @var{nn} are hex digits.
37702 An empty reply indicates that @samp{QCatchSyscalls} is not supported by
37706 Use of this packet is controlled by the @code{set remote catch-syscalls}
37707 command (@pxref{Remote Configuration, set remote catch-syscalls}).
37708 This packet is not probed by default; the remote stub must request it,
37709 by supplying an appropriate @samp{qSupported} response (@pxref{qSupported}).
37711 @item QPassSignals: @var{signal} @r{[};@var{signal}@r{]}@dots{}
37712 @cindex pass signals to inferior, remote request
37713 @cindex @samp{QPassSignals} packet
37714 @anchor{QPassSignals}
37715 Each listed @var{signal} should be passed directly to the inferior process.
37716 Signals are numbered identically to continue packets and stop replies
37717 (@pxref{Stop Reply Packets}). Each @var{signal} list item should be
37718 strictly greater than the previous item. These signals do not need to stop
37719 the inferior, or be reported to @value{GDBN}. All other signals should be
37720 reported to @value{GDBN}. Multiple @samp{QPassSignals} packets do not
37721 combine; any earlier @samp{QPassSignals} list is completely replaced by the
37722 new list. This packet improves performance when using @samp{handle
37723 @var{signal} nostop noprint pass}.
37728 The request succeeded.
37731 An error occurred. The error number @var{nn} is given as hex digits.
37734 An empty reply indicates that @samp{QPassSignals} is not supported by
37738 Use of this packet is controlled by the @code{set remote pass-signals}
37739 command (@pxref{Remote Configuration, set remote pass-signals}).
37740 This packet is not probed by default; the remote stub must request it,
37741 by supplying an appropriate @samp{qSupported} response (@pxref{qSupported}).
37743 @item QProgramSignals: @var{signal} @r{[};@var{signal}@r{]}@dots{}
37744 @cindex signals the inferior may see, remote request
37745 @cindex @samp{QProgramSignals} packet
37746 @anchor{QProgramSignals}
37747 Each listed @var{signal} may be delivered to the inferior process.
37748 Others should be silently discarded.
37750 In some cases, the remote stub may need to decide whether to deliver a
37751 signal to the program or not without @value{GDBN} involvement. One
37752 example of that is while detaching --- the program's threads may have
37753 stopped for signals that haven't yet had a chance of being reported to
37754 @value{GDBN}, and so the remote stub can use the signal list specified
37755 by this packet to know whether to deliver or ignore those pending
37758 This does not influence whether to deliver a signal as requested by a
37759 resumption packet (@pxref{vCont packet}).
37761 Signals are numbered identically to continue packets and stop replies
37762 (@pxref{Stop Reply Packets}). Each @var{signal} list item should be
37763 strictly greater than the previous item. Multiple
37764 @samp{QProgramSignals} packets do not combine; any earlier
37765 @samp{QProgramSignals} list is completely replaced by the new list.
37770 The request succeeded.
37773 An error occurred. The error number @var{nn} is given as hex digits.
37776 An empty reply indicates that @samp{QProgramSignals} is not supported
37780 Use of this packet is controlled by the @code{set remote program-signals}
37781 command (@pxref{Remote Configuration, set remote program-signals}).
37782 This packet is not probed by default; the remote stub must request it,
37783 by supplying an appropriate @samp{qSupported} response (@pxref{qSupported}).
37785 @anchor{QThreadEvents}
37786 @item QThreadEvents:1
37787 @itemx QThreadEvents:0
37788 @cindex thread create/exit events, remote request
37789 @cindex @samp{QThreadEvents} packet
37791 Enable (@samp{QThreadEvents:1}) or disable (@samp{QThreadEvents:0})
37792 reporting of thread create and exit events. @xref{thread create
37793 event}, for the reply specifications. For example, this is used in
37794 non-stop mode when @value{GDBN} stops a set of threads and
37795 synchronously waits for the their corresponding stop replies. Without
37796 exit events, if one of the threads exits, @value{GDBN} would hang
37797 forever not knowing that it should no longer expect a stop for that
37798 same thread. @value{GDBN} does not enable this feature unless the
37799 stub reports that it supports it by including @samp{QThreadEvents+} in
37800 its @samp{qSupported} reply.
37805 The request succeeded.
37808 An error occurred. The error number @var{nn} is given as hex digits.
37811 An empty reply indicates that @samp{QThreadEvents} is not supported by
37815 Use of this packet is controlled by the @code{set remote thread-events}
37816 command (@pxref{Remote Configuration, set remote thread-events}).
37818 @item qRcmd,@var{command}
37819 @cindex execute remote command, remote request
37820 @cindex @samp{qRcmd} packet
37821 @var{command} (hex encoded) is passed to the local interpreter for
37822 execution. Invalid commands should be reported using the output
37823 string. Before the final result packet, the target may also respond
37824 with a number of intermediate @samp{O@var{output}} console output
37825 packets. @emph{Implementors should note that providing access to a
37826 stubs's interpreter may have security implications}.
37831 A command response with no output.
37833 A command response with the hex encoded output string @var{OUTPUT}.
37835 Indicate a badly formed request.
37837 An empty reply indicates that @samp{qRcmd} is not recognized.
37840 (Note that the @code{qRcmd} packet's name is separated from the
37841 command by a @samp{,}, not a @samp{:}, contrary to the naming
37842 conventions above. Please don't use this packet as a model for new
37845 @item qSearch:memory:@var{address};@var{length};@var{search-pattern}
37846 @cindex searching memory, in remote debugging
37848 @cindex @samp{qSearch:memory} packet
37850 @cindex @samp{qSearch memory} packet
37851 @anchor{qSearch memory}
37852 Search @var{length} bytes at @var{address} for @var{search-pattern}.
37853 Both @var{address} and @var{length} are encoded in hex;
37854 @var{search-pattern} is a sequence of bytes, also hex encoded.
37859 The pattern was not found.
37861 The pattern was found at @var{address}.
37863 A badly formed request or an error was encountered while searching memory.
37865 An empty reply indicates that @samp{qSearch:memory} is not recognized.
37868 @item QStartNoAckMode
37869 @cindex @samp{QStartNoAckMode} packet
37870 @anchor{QStartNoAckMode}
37871 Request that the remote stub disable the normal @samp{+}/@samp{-}
37872 protocol acknowledgments (@pxref{Packet Acknowledgment}).
37877 The stub has switched to no-acknowledgment mode.
37878 @value{GDBN} acknowledges this reponse,
37879 but neither the stub nor @value{GDBN} shall send or expect further
37880 @samp{+}/@samp{-} acknowledgments in the current connection.
37882 An empty reply indicates that the stub does not support no-acknowledgment mode.
37885 @item qSupported @r{[}:@var{gdbfeature} @r{[};@var{gdbfeature}@r{]}@dots{} @r{]}
37886 @cindex supported packets, remote query
37887 @cindex features of the remote protocol
37888 @cindex @samp{qSupported} packet
37889 @anchor{qSupported}
37890 Tell the remote stub about features supported by @value{GDBN}, and
37891 query the stub for features it supports. This packet allows
37892 @value{GDBN} and the remote stub to take advantage of each others'
37893 features. @samp{qSupported} also consolidates multiple feature probes
37894 at startup, to improve @value{GDBN} performance---a single larger
37895 packet performs better than multiple smaller probe packets on
37896 high-latency links. Some features may enable behavior which must not
37897 be on by default, e.g.@: because it would confuse older clients or
37898 stubs. Other features may describe packets which could be
37899 automatically probed for, but are not. These features must be
37900 reported before @value{GDBN} will use them. This ``default
37901 unsupported'' behavior is not appropriate for all packets, but it
37902 helps to keep the initial connection time under control with new
37903 versions of @value{GDBN} which support increasing numbers of packets.
37907 @item @var{stubfeature} @r{[};@var{stubfeature}@r{]}@dots{}
37908 The stub supports or does not support each returned @var{stubfeature},
37909 depending on the form of each @var{stubfeature} (see below for the
37912 An empty reply indicates that @samp{qSupported} is not recognized,
37913 or that no features needed to be reported to @value{GDBN}.
37916 The allowed forms for each feature (either a @var{gdbfeature} in the
37917 @samp{qSupported} packet, or a @var{stubfeature} in the response)
37921 @item @var{name}=@var{value}
37922 The remote protocol feature @var{name} is supported, and associated
37923 with the specified @var{value}. The format of @var{value} depends
37924 on the feature, but it must not include a semicolon.
37926 The remote protocol feature @var{name} is supported, and does not
37927 need an associated value.
37929 The remote protocol feature @var{name} is not supported.
37931 The remote protocol feature @var{name} may be supported, and
37932 @value{GDBN} should auto-detect support in some other way when it is
37933 needed. This form will not be used for @var{gdbfeature} notifications,
37934 but may be used for @var{stubfeature} responses.
37937 Whenever the stub receives a @samp{qSupported} request, the
37938 supplied set of @value{GDBN} features should override any previous
37939 request. This allows @value{GDBN} to put the stub in a known
37940 state, even if the stub had previously been communicating with
37941 a different version of @value{GDBN}.
37943 The following values of @var{gdbfeature} (for the packet sent by @value{GDBN})
37948 This feature indicates whether @value{GDBN} supports multiprocess
37949 extensions to the remote protocol. @value{GDBN} does not use such
37950 extensions unless the stub also reports that it supports them by
37951 including @samp{multiprocess+} in its @samp{qSupported} reply.
37952 @xref{multiprocess extensions}, for details.
37955 This feature indicates that @value{GDBN} supports the XML target
37956 description. If the stub sees @samp{xmlRegisters=} with target
37957 specific strings separated by a comma, it will report register
37961 This feature indicates whether @value{GDBN} supports the
37962 @samp{qRelocInsn} packet (@pxref{Tracepoint Packets,,Relocate
37963 instruction reply packet}).
37966 This feature indicates whether @value{GDBN} supports the swbreak stop
37967 reason in stop replies. @xref{swbreak stop reason}, for details.
37970 This feature indicates whether @value{GDBN} supports the hwbreak stop
37971 reason in stop replies. @xref{swbreak stop reason}, for details.
37974 This feature indicates whether @value{GDBN} supports fork event
37975 extensions to the remote protocol. @value{GDBN} does not use such
37976 extensions unless the stub also reports that it supports them by
37977 including @samp{fork-events+} in its @samp{qSupported} reply.
37980 This feature indicates whether @value{GDBN} supports vfork event
37981 extensions to the remote protocol. @value{GDBN} does not use such
37982 extensions unless the stub also reports that it supports them by
37983 including @samp{vfork-events+} in its @samp{qSupported} reply.
37986 This feature indicates whether @value{GDBN} supports exec event
37987 extensions to the remote protocol. @value{GDBN} does not use such
37988 extensions unless the stub also reports that it supports them by
37989 including @samp{exec-events+} in its @samp{qSupported} reply.
37991 @item vContSupported
37992 This feature indicates whether @value{GDBN} wants to know the
37993 supported actions in the reply to @samp{vCont?} packet.
37996 Stubs should ignore any unknown values for
37997 @var{gdbfeature}. Any @value{GDBN} which sends a @samp{qSupported}
37998 packet supports receiving packets of unlimited length (earlier
37999 versions of @value{GDBN} may reject overly long responses). Additional values
38000 for @var{gdbfeature} may be defined in the future to let the stub take
38001 advantage of new features in @value{GDBN}, e.g.@: incompatible
38002 improvements in the remote protocol---the @samp{multiprocess} feature is
38003 an example of such a feature. The stub's reply should be independent
38004 of the @var{gdbfeature} entries sent by @value{GDBN}; first @value{GDBN}
38005 describes all the features it supports, and then the stub replies with
38006 all the features it supports.
38008 Similarly, @value{GDBN} will silently ignore unrecognized stub feature
38009 responses, as long as each response uses one of the standard forms.
38011 Some features are flags. A stub which supports a flag feature
38012 should respond with a @samp{+} form response. Other features
38013 require values, and the stub should respond with an @samp{=}
38016 Each feature has a default value, which @value{GDBN} will use if
38017 @samp{qSupported} is not available or if the feature is not mentioned
38018 in the @samp{qSupported} response. The default values are fixed; a
38019 stub is free to omit any feature responses that match the defaults.
38021 Not all features can be probed, but for those which can, the probing
38022 mechanism is useful: in some cases, a stub's internal
38023 architecture may not allow the protocol layer to know some information
38024 about the underlying target in advance. This is especially common in
38025 stubs which may be configured for multiple targets.
38027 These are the currently defined stub features and their properties:
38029 @multitable @columnfractions 0.35 0.2 0.12 0.2
38030 @c NOTE: The first row should be @headitem, but we do not yet require
38031 @c a new enough version of Texinfo (4.7) to use @headitem.
38033 @tab Value Required
38037 @item @samp{PacketSize}
38042 @item @samp{qXfer:auxv:read}
38047 @item @samp{qXfer:btrace:read}
38052 @item @samp{qXfer:btrace-conf:read}
38057 @item @samp{qXfer:exec-file:read}
38062 @item @samp{qXfer:features:read}
38067 @item @samp{qXfer:libraries:read}
38072 @item @samp{qXfer:libraries-svr4:read}
38077 @item @samp{augmented-libraries-svr4-read}
38082 @item @samp{qXfer:memory-map:read}
38087 @item @samp{qXfer:sdata:read}
38092 @item @samp{qXfer:spu:read}
38097 @item @samp{qXfer:spu:write}
38102 @item @samp{qXfer:siginfo:read}
38107 @item @samp{qXfer:siginfo:write}
38112 @item @samp{qXfer:threads:read}
38117 @item @samp{qXfer:traceframe-info:read}
38122 @item @samp{qXfer:uib:read}
38127 @item @samp{qXfer:fdpic:read}
38132 @item @samp{Qbtrace:off}
38137 @item @samp{Qbtrace:bts}
38142 @item @samp{Qbtrace:pt}
38147 @item @samp{Qbtrace-conf:bts:size}
38152 @item @samp{Qbtrace-conf:pt:size}
38157 @item @samp{QNonStop}
38162 @item @samp{QCatchSyscalls}
38167 @item @samp{QPassSignals}
38172 @item @samp{QStartNoAckMode}
38177 @item @samp{multiprocess}
38182 @item @samp{ConditionalBreakpoints}
38187 @item @samp{ConditionalTracepoints}
38192 @item @samp{ReverseContinue}
38197 @item @samp{ReverseStep}
38202 @item @samp{TracepointSource}
38207 @item @samp{QAgent}
38212 @item @samp{QAllow}
38217 @item @samp{QDisableRandomization}
38222 @item @samp{EnableDisableTracepoints}
38227 @item @samp{QTBuffer:size}
38232 @item @samp{tracenz}
38237 @item @samp{BreakpointCommands}
38242 @item @samp{swbreak}
38247 @item @samp{hwbreak}
38252 @item @samp{fork-events}
38257 @item @samp{vfork-events}
38262 @item @samp{exec-events}
38267 @item @samp{QThreadEvents}
38272 @item @samp{no-resumed}
38279 These are the currently defined stub features, in more detail:
38282 @cindex packet size, remote protocol
38283 @item PacketSize=@var{bytes}
38284 The remote stub can accept packets up to at least @var{bytes} in
38285 length. @value{GDBN} will send packets up to this size for bulk
38286 transfers, and will never send larger packets. This is a limit on the
38287 data characters in the packet, including the frame and checksum.
38288 There is no trailing NUL byte in a remote protocol packet; if the stub
38289 stores packets in a NUL-terminated format, it should allow an extra
38290 byte in its buffer for the NUL. If this stub feature is not supported,
38291 @value{GDBN} guesses based on the size of the @samp{g} packet response.
38293 @item qXfer:auxv:read
38294 The remote stub understands the @samp{qXfer:auxv:read} packet
38295 (@pxref{qXfer auxiliary vector read}).
38297 @item qXfer:btrace:read
38298 The remote stub understands the @samp{qXfer:btrace:read}
38299 packet (@pxref{qXfer btrace read}).
38301 @item qXfer:btrace-conf:read
38302 The remote stub understands the @samp{qXfer:btrace-conf:read}
38303 packet (@pxref{qXfer btrace-conf read}).
38305 @item qXfer:exec-file:read
38306 The remote stub understands the @samp{qXfer:exec-file:read} packet
38307 (@pxref{qXfer executable filename read}).
38309 @item qXfer:features:read
38310 The remote stub understands the @samp{qXfer:features:read} packet
38311 (@pxref{qXfer target description read}).
38313 @item qXfer:libraries:read
38314 The remote stub understands the @samp{qXfer:libraries:read} packet
38315 (@pxref{qXfer library list read}).
38317 @item qXfer:libraries-svr4:read
38318 The remote stub understands the @samp{qXfer:libraries-svr4:read} packet
38319 (@pxref{qXfer svr4 library list read}).
38321 @item augmented-libraries-svr4-read
38322 The remote stub understands the augmented form of the
38323 @samp{qXfer:libraries-svr4:read} packet
38324 (@pxref{qXfer svr4 library list read}).
38326 @item qXfer:memory-map:read
38327 The remote stub understands the @samp{qXfer:memory-map:read} packet
38328 (@pxref{qXfer memory map read}).
38330 @item qXfer:sdata:read
38331 The remote stub understands the @samp{qXfer:sdata:read} packet
38332 (@pxref{qXfer sdata read}).
38334 @item qXfer:spu:read
38335 The remote stub understands the @samp{qXfer:spu:read} packet
38336 (@pxref{qXfer spu read}).
38338 @item qXfer:spu:write
38339 The remote stub understands the @samp{qXfer:spu:write} packet
38340 (@pxref{qXfer spu write}).
38342 @item qXfer:siginfo:read
38343 The remote stub understands the @samp{qXfer:siginfo:read} packet
38344 (@pxref{qXfer siginfo read}).
38346 @item qXfer:siginfo:write
38347 The remote stub understands the @samp{qXfer:siginfo:write} packet
38348 (@pxref{qXfer siginfo write}).
38350 @item qXfer:threads:read
38351 The remote stub understands the @samp{qXfer:threads:read} packet
38352 (@pxref{qXfer threads read}).
38354 @item qXfer:traceframe-info:read
38355 The remote stub understands the @samp{qXfer:traceframe-info:read}
38356 packet (@pxref{qXfer traceframe info read}).
38358 @item qXfer:uib:read
38359 The remote stub understands the @samp{qXfer:uib:read}
38360 packet (@pxref{qXfer unwind info block}).
38362 @item qXfer:fdpic:read
38363 The remote stub understands the @samp{qXfer:fdpic:read}
38364 packet (@pxref{qXfer fdpic loadmap read}).
38367 The remote stub understands the @samp{QNonStop} packet
38368 (@pxref{QNonStop}).
38370 @item QCatchSyscalls
38371 The remote stub understands the @samp{QCatchSyscalls} packet
38372 (@pxref{QCatchSyscalls}).
38375 The remote stub understands the @samp{QPassSignals} packet
38376 (@pxref{QPassSignals}).
38378 @item QStartNoAckMode
38379 The remote stub understands the @samp{QStartNoAckMode} packet and
38380 prefers to operate in no-acknowledgment mode. @xref{Packet Acknowledgment}.
38383 @anchor{multiprocess extensions}
38384 @cindex multiprocess extensions, in remote protocol
38385 The remote stub understands the multiprocess extensions to the remote
38386 protocol syntax. The multiprocess extensions affect the syntax of
38387 thread IDs in both packets and replies (@pxref{thread-id syntax}), and
38388 add process IDs to the @samp{D} packet and @samp{W} and @samp{X}
38389 replies. Note that reporting this feature indicates support for the
38390 syntactic extensions only, not that the stub necessarily supports
38391 debugging of more than one process at a time. The stub must not use
38392 multiprocess extensions in packet replies unless @value{GDBN} has also
38393 indicated it supports them in its @samp{qSupported} request.
38395 @item qXfer:osdata:read
38396 The remote stub understands the @samp{qXfer:osdata:read} packet
38397 ((@pxref{qXfer osdata read}).
38399 @item ConditionalBreakpoints
38400 The target accepts and implements evaluation of conditional expressions
38401 defined for breakpoints. The target will only report breakpoint triggers
38402 when such conditions are true (@pxref{Conditions, ,Break Conditions}).
38404 @item ConditionalTracepoints
38405 The remote stub accepts and implements conditional expressions defined
38406 for tracepoints (@pxref{Tracepoint Conditions}).
38408 @item ReverseContinue
38409 The remote stub accepts and implements the reverse continue packet
38413 The remote stub accepts and implements the reverse step packet
38416 @item TracepointSource
38417 The remote stub understands the @samp{QTDPsrc} packet that supplies
38418 the source form of tracepoint definitions.
38421 The remote stub understands the @samp{QAgent} packet.
38424 The remote stub understands the @samp{QAllow} packet.
38426 @item QDisableRandomization
38427 The remote stub understands the @samp{QDisableRandomization} packet.
38429 @item StaticTracepoint
38430 @cindex static tracepoints, in remote protocol
38431 The remote stub supports static tracepoints.
38433 @item InstallInTrace
38434 @anchor{install tracepoint in tracing}
38435 The remote stub supports installing tracepoint in tracing.
38437 @item EnableDisableTracepoints
38438 The remote stub supports the @samp{QTEnable} (@pxref{QTEnable}) and
38439 @samp{QTDisable} (@pxref{QTDisable}) packets that allow tracepoints
38440 to be enabled and disabled while a trace experiment is running.
38442 @item QTBuffer:size
38443 The remote stub supports the @samp{QTBuffer:size} (@pxref{QTBuffer-size})
38444 packet that allows to change the size of the trace buffer.
38447 @cindex string tracing, in remote protocol
38448 The remote stub supports the @samp{tracenz} bytecode for collecting strings.
38449 See @ref{Bytecode Descriptions} for details about the bytecode.
38451 @item BreakpointCommands
38452 @cindex breakpoint commands, in remote protocol
38453 The remote stub supports running a breakpoint's command list itself,
38454 rather than reporting the hit to @value{GDBN}.
38457 The remote stub understands the @samp{Qbtrace:off} packet.
38460 The remote stub understands the @samp{Qbtrace:bts} packet.
38463 The remote stub understands the @samp{Qbtrace:pt} packet.
38465 @item Qbtrace-conf:bts:size
38466 The remote stub understands the @samp{Qbtrace-conf:bts:size} packet.
38468 @item Qbtrace-conf:pt:size
38469 The remote stub understands the @samp{Qbtrace-conf:pt:size} packet.
38472 The remote stub reports the @samp{swbreak} stop reason for memory
38476 The remote stub reports the @samp{hwbreak} stop reason for hardware
38480 The remote stub reports the @samp{fork} stop reason for fork events.
38483 The remote stub reports the @samp{vfork} stop reason for vfork events
38484 and vforkdone events.
38487 The remote stub reports the @samp{exec} stop reason for exec events.
38489 @item vContSupported
38490 The remote stub reports the supported actions in the reply to
38491 @samp{vCont?} packet.
38493 @item QThreadEvents
38494 The remote stub understands the @samp{QThreadEvents} packet.
38497 The remote stub reports the @samp{N} stop reply.
38502 @cindex symbol lookup, remote request
38503 @cindex @samp{qSymbol} packet
38504 Notify the target that @value{GDBN} is prepared to serve symbol lookup
38505 requests. Accept requests from the target for the values of symbols.
38510 The target does not need to look up any (more) symbols.
38511 @item qSymbol:@var{sym_name}
38512 The target requests the value of symbol @var{sym_name} (hex encoded).
38513 @value{GDBN} may provide the value by using the
38514 @samp{qSymbol:@var{sym_value}:@var{sym_name}} message, described
38518 @item qSymbol:@var{sym_value}:@var{sym_name}
38519 Set the value of @var{sym_name} to @var{sym_value}.
38521 @var{sym_name} (hex encoded) is the name of a symbol whose value the
38522 target has previously requested.
38524 @var{sym_value} (hex) is the value for symbol @var{sym_name}. If
38525 @value{GDBN} cannot supply a value for @var{sym_name}, then this field
38531 The target does not need to look up any (more) symbols.
38532 @item qSymbol:@var{sym_name}
38533 The target requests the value of a new symbol @var{sym_name} (hex
38534 encoded). @value{GDBN} will continue to supply the values of symbols
38535 (if available), until the target ceases to request them.
38540 @itemx QTDisconnected
38547 @itemx qTMinFTPILen
38549 @xref{Tracepoint Packets}.
38551 @item qThreadExtraInfo,@var{thread-id}
38552 @cindex thread attributes info, remote request
38553 @cindex @samp{qThreadExtraInfo} packet
38554 Obtain from the target OS a printable string description of thread
38555 attributes for the thread @var{thread-id}; see @ref{thread-id syntax},
38556 for the forms of @var{thread-id}. This
38557 string may contain anything that the target OS thinks is interesting
38558 for @value{GDBN} to tell the user about the thread. The string is
38559 displayed in @value{GDBN}'s @code{info threads} display. Some
38560 examples of possible thread extra info strings are @samp{Runnable}, or
38561 @samp{Blocked on Mutex}.
38565 @item @var{XX}@dots{}
38566 Where @samp{@var{XX}@dots{}} is a hex encoding of @sc{ascii} data,
38567 comprising the printable string containing the extra information about
38568 the thread's attributes.
38571 (Note that the @code{qThreadExtraInfo} packet's name is separated from
38572 the command by a @samp{,}, not a @samp{:}, contrary to the naming
38573 conventions above. Please don't use this packet as a model for new
38592 @xref{Tracepoint Packets}.
38594 @item qXfer:@var{object}:read:@var{annex}:@var{offset},@var{length}
38595 @cindex read special object, remote request
38596 @cindex @samp{qXfer} packet
38597 @anchor{qXfer read}
38598 Read uninterpreted bytes from the target's special data area
38599 identified by the keyword @var{object}. Request @var{length} bytes
38600 starting at @var{offset} bytes into the data. The content and
38601 encoding of @var{annex} is specific to @var{object}; it can supply
38602 additional details about what data to access.
38607 Data @var{data} (@pxref{Binary Data}) has been read from the
38608 target. There may be more data at a higher address (although
38609 it is permitted to return @samp{m} even for the last valid
38610 block of data, as long as at least one byte of data was read).
38611 It is possible for @var{data} to have fewer bytes than the @var{length} in the
38615 Data @var{data} (@pxref{Binary Data}) has been read from the target.
38616 There is no more data to be read. It is possible for @var{data} to
38617 have fewer bytes than the @var{length} in the request.
38620 The @var{offset} in the request is at the end of the data.
38621 There is no more data to be read.
38624 The request was malformed, or @var{annex} was invalid.
38627 The offset was invalid, or there was an error encountered reading the data.
38628 The @var{nn} part is a hex-encoded @code{errno} value.
38631 An empty reply indicates the @var{object} string was not recognized by
38632 the stub, or that the object does not support reading.
38635 Here are the specific requests of this form defined so far. All the
38636 @samp{qXfer:@var{object}:read:@dots{}} requests use the same reply
38637 formats, listed above.
38640 @item qXfer:auxv:read::@var{offset},@var{length}
38641 @anchor{qXfer auxiliary vector read}
38642 Access the target's @dfn{auxiliary vector}. @xref{OS Information,
38643 auxiliary vector}. Note @var{annex} must be empty.
38645 This packet is not probed by default; the remote stub must request it,
38646 by supplying an appropriate @samp{qSupported} response (@pxref{qSupported}).
38648 @item qXfer:btrace:read:@var{annex}:@var{offset},@var{length}
38649 @anchor{qXfer btrace read}
38651 Return a description of the current branch trace.
38652 @xref{Branch Trace Format}. The annex part of the generic @samp{qXfer}
38653 packet may have one of the following values:
38657 Returns all available branch trace.
38660 Returns all available branch trace if the branch trace changed since
38661 the last read request.
38664 Returns the new branch trace since the last read request. Adds a new
38665 block to the end of the trace that begins at zero and ends at the source
38666 location of the first branch in the trace buffer. This extra block is
38667 used to stitch traces together.
38669 If the trace buffer overflowed, returns an error indicating the overflow.
38672 This packet is not probed by default; the remote stub must request it
38673 by supplying an appropriate @samp{qSupported} response (@pxref{qSupported}).
38675 @item qXfer:btrace-conf:read::@var{offset},@var{length}
38676 @anchor{qXfer btrace-conf read}
38678 Return a description of the current branch trace configuration.
38679 @xref{Branch Trace Configuration Format}.
38681 This packet is not probed by default; the remote stub must request it
38682 by supplying an appropriate @samp{qSupported} response (@pxref{qSupported}).
38684 @item qXfer:exec-file:read:@var{annex}:@var{offset},@var{length}
38685 @anchor{qXfer executable filename read}
38686 Return the full absolute name of the file that was executed to create
38687 a process running on the remote system. The annex specifies the
38688 numeric process ID of the process to query, encoded as a hexadecimal
38689 number. If the annex part is empty the remote stub should return the
38690 filename corresponding to the currently executing process.
38692 This packet is not probed by default; the remote stub must request it,
38693 by supplying an appropriate @samp{qSupported} response (@pxref{qSupported}).
38695 @item qXfer:features:read:@var{annex}:@var{offset},@var{length}
38696 @anchor{qXfer target description read}
38697 Access the @dfn{target description}. @xref{Target Descriptions}. The
38698 annex specifies which XML document to access. The main description is
38699 always loaded from the @samp{target.xml} annex.
38701 This packet is not probed by default; the remote stub must request it,
38702 by supplying an appropriate @samp{qSupported} response (@pxref{qSupported}).
38704 @item qXfer:libraries:read:@var{annex}:@var{offset},@var{length}
38705 @anchor{qXfer library list read}
38706 Access the target's list of loaded libraries. @xref{Library List Format}.
38707 The annex part of the generic @samp{qXfer} packet must be empty
38708 (@pxref{qXfer read}).
38710 Targets which maintain a list of libraries in the program's memory do
38711 not need to implement this packet; it is designed for platforms where
38712 the operating system manages the list of loaded libraries.
38714 This packet is not probed by default; the remote stub must request it,
38715 by supplying an appropriate @samp{qSupported} response (@pxref{qSupported}).
38717 @item qXfer:libraries-svr4:read:@var{annex}:@var{offset},@var{length}
38718 @anchor{qXfer svr4 library list read}
38719 Access the target's list of loaded libraries when the target is an SVR4
38720 platform. @xref{Library List Format for SVR4 Targets}. The annex part
38721 of the generic @samp{qXfer} packet must be empty unless the remote
38722 stub indicated it supports the augmented form of this packet
38723 by supplying an appropriate @samp{qSupported} response
38724 (@pxref{qXfer read}, @ref{qSupported}).
38726 This packet is optional for better performance on SVR4 targets.
38727 @value{GDBN} uses memory read packets to read the SVR4 library list otherwise.
38729 This packet is not probed by default; the remote stub must request it,
38730 by supplying an appropriate @samp{qSupported} response (@pxref{qSupported}).
38732 If the remote stub indicates it supports the augmented form of this
38733 packet then the annex part of the generic @samp{qXfer} packet may
38734 contain a semicolon-separated list of @samp{@var{name}=@var{value}}
38735 arguments. The currently supported arguments are:
38738 @item start=@var{address}
38739 A hexadecimal number specifying the address of the @samp{struct
38740 link_map} to start reading the library list from. If unset or zero
38741 then the first @samp{struct link_map} in the library list will be
38742 chosen as the starting point.
38744 @item prev=@var{address}
38745 A hexadecimal number specifying the address of the @samp{struct
38746 link_map} immediately preceding the @samp{struct link_map}
38747 specified by the @samp{start} argument. If unset or zero then
38748 the remote stub will expect that no @samp{struct link_map}
38749 exists prior to the starting point.
38753 Arguments that are not understood by the remote stub will be silently
38756 @item qXfer:memory-map:read::@var{offset},@var{length}
38757 @anchor{qXfer memory map read}
38758 Access the target's @dfn{memory-map}. @xref{Memory Map Format}. The
38759 annex part of the generic @samp{qXfer} packet must be empty
38760 (@pxref{qXfer read}).
38762 This packet is not probed by default; the remote stub must request it,
38763 by supplying an appropriate @samp{qSupported} response (@pxref{qSupported}).
38765 @item qXfer:sdata:read::@var{offset},@var{length}
38766 @anchor{qXfer sdata read}
38768 Read contents of the extra collected static tracepoint marker
38769 information. The annex part of the generic @samp{qXfer} packet must
38770 be empty (@pxref{qXfer read}). @xref{Tracepoint Actions,,Tracepoint
38773 This packet is not probed by default; the remote stub must request it,
38774 by supplying an appropriate @samp{qSupported} response
38775 (@pxref{qSupported}).
38777 @item qXfer:siginfo:read::@var{offset},@var{length}
38778 @anchor{qXfer siginfo read}
38779 Read contents of the extra signal information on the target
38780 system. The annex part of the generic @samp{qXfer} packet must be
38781 empty (@pxref{qXfer read}).
38783 This packet is not probed by default; the remote stub must request it,
38784 by supplying an appropriate @samp{qSupported} response
38785 (@pxref{qSupported}).
38787 @item qXfer:spu:read:@var{annex}:@var{offset},@var{length}
38788 @anchor{qXfer spu read}
38789 Read contents of an @code{spufs} file on the target system. The
38790 annex specifies which file to read; it must be of the form
38791 @file{@var{id}/@var{name}}, where @var{id} specifies an SPU context ID
38792 in the target process, and @var{name} identifes the @code{spufs} file
38793 in that context to be accessed.
38795 This packet is not probed by default; the remote stub must request it,
38796 by supplying an appropriate @samp{qSupported} response
38797 (@pxref{qSupported}).
38799 @item qXfer:threads:read::@var{offset},@var{length}
38800 @anchor{qXfer threads read}
38801 Access the list of threads on target. @xref{Thread List Format}. The
38802 annex part of the generic @samp{qXfer} packet must be empty
38803 (@pxref{qXfer read}).
38805 This packet is not probed by default; the remote stub must request it,
38806 by supplying an appropriate @samp{qSupported} response (@pxref{qSupported}).
38808 @item qXfer:traceframe-info:read::@var{offset},@var{length}
38809 @anchor{qXfer traceframe info read}
38811 Return a description of the current traceframe's contents.
38812 @xref{Traceframe Info Format}. The annex part of the generic
38813 @samp{qXfer} packet must be empty (@pxref{qXfer read}).
38815 This packet is not probed by default; the remote stub must request it,
38816 by supplying an appropriate @samp{qSupported} response (@pxref{qSupported}).
38818 @item qXfer:uib:read:@var{pc}:@var{offset},@var{length}
38819 @anchor{qXfer unwind info block}
38821 Return the unwind information block for @var{pc}. This packet is used
38822 on OpenVMS/ia64 to ask the kernel unwind information.
38824 This packet is not probed by default.
38826 @item qXfer:fdpic:read:@var{annex}:@var{offset},@var{length}
38827 @anchor{qXfer fdpic loadmap read}
38828 Read contents of @code{loadmap}s on the target system. The
38829 annex, either @samp{exec} or @samp{interp}, specifies which @code{loadmap},
38830 executable @code{loadmap} or interpreter @code{loadmap} to read.
38832 This packet is not probed by default; the remote stub must request it,
38833 by supplying an appropriate @samp{qSupported} response (@pxref{qSupported}).
38835 @item qXfer:osdata:read::@var{offset},@var{length}
38836 @anchor{qXfer osdata read}
38837 Access the target's @dfn{operating system information}.
38838 @xref{Operating System Information}.
38842 @item qXfer:@var{object}:write:@var{annex}:@var{offset}:@var{data}@dots{}
38843 @cindex write data into object, remote request
38844 @anchor{qXfer write}
38845 Write uninterpreted bytes into the target's special data area
38846 identified by the keyword @var{object}, starting at @var{offset} bytes
38847 into the data. The binary-encoded data (@pxref{Binary Data}) to be
38848 written is given by @var{data}@dots{}. The content and encoding of @var{annex}
38849 is specific to @var{object}; it can supply additional details about what data
38855 @var{nn} (hex encoded) is the number of bytes written.
38856 This may be fewer bytes than supplied in the request.
38859 The request was malformed, or @var{annex} was invalid.
38862 The offset was invalid, or there was an error encountered writing the data.
38863 The @var{nn} part is a hex-encoded @code{errno} value.
38866 An empty reply indicates the @var{object} string was not
38867 recognized by the stub, or that the object does not support writing.
38870 Here are the specific requests of this form defined so far. All the
38871 @samp{qXfer:@var{object}:write:@dots{}} requests use the same reply
38872 formats, listed above.
38875 @item qXfer:siginfo:write::@var{offset}:@var{data}@dots{}
38876 @anchor{qXfer siginfo write}
38877 Write @var{data} to the extra signal information on the target system.
38878 The annex part of the generic @samp{qXfer} packet must be
38879 empty (@pxref{qXfer write}).
38881 This packet is not probed by default; the remote stub must request it,
38882 by supplying an appropriate @samp{qSupported} response
38883 (@pxref{qSupported}).
38885 @item qXfer:spu:write:@var{annex}:@var{offset}:@var{data}@dots{}
38886 @anchor{qXfer spu write}
38887 Write @var{data} to an @code{spufs} file on the target system. The
38888 annex specifies which file to write; it must be of the form
38889 @file{@var{id}/@var{name}}, where @var{id} specifies an SPU context ID
38890 in the target process, and @var{name} identifes the @code{spufs} file
38891 in that context to be accessed.
38893 This packet is not probed by default; the remote stub must request it,
38894 by supplying an appropriate @samp{qSupported} response (@pxref{qSupported}).
38897 @item qXfer:@var{object}:@var{operation}:@dots{}
38898 Requests of this form may be added in the future. When a stub does
38899 not recognize the @var{object} keyword, or its support for
38900 @var{object} does not recognize the @var{operation} keyword, the stub
38901 must respond with an empty packet.
38903 @item qAttached:@var{pid}
38904 @cindex query attached, remote request
38905 @cindex @samp{qAttached} packet
38906 Return an indication of whether the remote server attached to an
38907 existing process or created a new process. When the multiprocess
38908 protocol extensions are supported (@pxref{multiprocess extensions}),
38909 @var{pid} is an integer in hexadecimal format identifying the target
38910 process. Otherwise, @value{GDBN} will omit the @var{pid} field and
38911 the query packet will be simplified as @samp{qAttached}.
38913 This query is used, for example, to know whether the remote process
38914 should be detached or killed when a @value{GDBN} session is ended with
38915 the @code{quit} command.
38920 The remote server attached to an existing process.
38922 The remote server created a new process.
38924 A badly formed request or an error was encountered.
38928 Enable branch tracing for the current thread using Branch Trace Store.
38933 Branch tracing has been enabled.
38935 A badly formed request or an error was encountered.
38939 Enable branch tracing for the current thread using Intel Processor Trace.
38944 Branch tracing has been enabled.
38946 A badly formed request or an error was encountered.
38950 Disable branch tracing for the current thread.
38955 Branch tracing has been disabled.
38957 A badly formed request or an error was encountered.
38960 @item Qbtrace-conf:bts:size=@var{value}
38961 Set the requested ring buffer size for new threads that use the
38962 btrace recording method in bts format.
38967 The ring buffer size has been set.
38969 A badly formed request or an error was encountered.
38972 @item Qbtrace-conf:pt:size=@var{value}
38973 Set the requested ring buffer size for new threads that use the
38974 btrace recording method in pt format.
38979 The ring buffer size has been set.
38981 A badly formed request or an error was encountered.
38986 @node Architecture-Specific Protocol Details
38987 @section Architecture-Specific Protocol Details
38989 This section describes how the remote protocol is applied to specific
38990 target architectures. Also see @ref{Standard Target Features}, for
38991 details of XML target descriptions for each architecture.
38994 * ARM-Specific Protocol Details::
38995 * MIPS-Specific Protocol Details::
38998 @node ARM-Specific Protocol Details
38999 @subsection @acronym{ARM}-specific Protocol Details
39002 * ARM Breakpoint Kinds::
39005 @node ARM Breakpoint Kinds
39006 @subsubsection @acronym{ARM} Breakpoint Kinds
39007 @cindex breakpoint kinds, @acronym{ARM}
39009 These breakpoint kinds are defined for the @samp{Z0} and @samp{Z1} packets.
39014 16-bit Thumb mode breakpoint.
39017 32-bit Thumb mode (Thumb-2) breakpoint.
39020 32-bit @acronym{ARM} mode breakpoint.
39024 @node MIPS-Specific Protocol Details
39025 @subsection @acronym{MIPS}-specific Protocol Details
39028 * MIPS Register packet Format::
39029 * MIPS Breakpoint Kinds::
39032 @node MIPS Register packet Format
39033 @subsubsection @acronym{MIPS} Register Packet Format
39034 @cindex register packet format, @acronym{MIPS}
39036 The following @code{g}/@code{G} packets have previously been defined.
39037 In the below, some thirty-two bit registers are transferred as
39038 sixty-four bits. Those registers should be zero/sign extended (which?)
39039 to fill the space allocated. Register bytes are transferred in target
39040 byte order. The two nibbles within a register byte are transferred
39041 most-significant -- least-significant.
39046 All registers are transferred as thirty-two bit quantities in the order:
39047 32 general-purpose; sr; lo; hi; bad; cause; pc; 32 floating-point
39048 registers; fsr; fir; fp.
39051 All registers are transferred as sixty-four bit quantities (including
39052 thirty-two bit registers such as @code{sr}). The ordering is the same
39057 @node MIPS Breakpoint Kinds
39058 @subsubsection @acronym{MIPS} Breakpoint Kinds
39059 @cindex breakpoint kinds, @acronym{MIPS}
39061 These breakpoint kinds are defined for the @samp{Z0} and @samp{Z1} packets.
39066 16-bit @acronym{MIPS16} mode breakpoint.
39069 16-bit @acronym{microMIPS} mode breakpoint.
39072 32-bit standard @acronym{MIPS} mode breakpoint.
39075 32-bit @acronym{microMIPS} mode breakpoint.
39079 @node Tracepoint Packets
39080 @section Tracepoint Packets
39081 @cindex tracepoint packets
39082 @cindex packets, tracepoint
39084 Here we describe the packets @value{GDBN} uses to implement
39085 tracepoints (@pxref{Tracepoints}).
39089 @item QTDP:@var{n}:@var{addr}:@var{ena}:@var{step}:@var{pass}[:F@var{flen}][:X@var{len},@var{bytes}]@r{[}-@r{]}
39090 @cindex @samp{QTDP} packet
39091 Create a new tracepoint, number @var{n}, at @var{addr}. If @var{ena}
39092 is @samp{E}, then the tracepoint is enabled; if it is @samp{D}, then
39093 the tracepoint is disabled. The @var{step} gives the tracepoint's step
39094 count, and @var{pass} gives its pass count. If an @samp{F} is present,
39095 then the tracepoint is to be a fast tracepoint, and the @var{flen} is
39096 the number of bytes that the target should copy elsewhere to make room
39097 for the tracepoint. If an @samp{X} is present, it introduces a
39098 tracepoint condition, which consists of a hexadecimal length, followed
39099 by a comma and hex-encoded bytes, in a manner similar to action
39100 encodings as described below. If the trailing @samp{-} is present,
39101 further @samp{QTDP} packets will follow to specify this tracepoint's
39107 The packet was understood and carried out.
39109 @xref{Tracepoint Packets,,Relocate instruction reply packet}.
39111 The packet was not recognized.
39114 @item QTDP:-@var{n}:@var{addr}:@r{[}S@r{]}@var{action}@dots{}@r{[}-@r{]}
39115 Define actions to be taken when a tracepoint is hit. The @var{n} and
39116 @var{addr} must be the same as in the initial @samp{QTDP} packet for
39117 this tracepoint. This packet may only be sent immediately after
39118 another @samp{QTDP} packet that ended with a @samp{-}. If the
39119 trailing @samp{-} is present, further @samp{QTDP} packets will follow,
39120 specifying more actions for this tracepoint.
39122 In the series of action packets for a given tracepoint, at most one
39123 can have an @samp{S} before its first @var{action}. If such a packet
39124 is sent, it and the following packets define ``while-stepping''
39125 actions. Any prior packets define ordinary actions --- that is, those
39126 taken when the tracepoint is first hit. If no action packet has an
39127 @samp{S}, then all the packets in the series specify ordinary
39128 tracepoint actions.
39130 The @samp{@var{action}@dots{}} portion of the packet is a series of
39131 actions, concatenated without separators. Each action has one of the
39137 Collect the registers whose bits are set in @var{mask},
39138 a hexadecimal number whose @var{i}'th bit is set if register number
39139 @var{i} should be collected. (The least significant bit is numbered
39140 zero.) Note that @var{mask} may be any number of digits long; it may
39141 not fit in a 32-bit word.
39143 @item M @var{basereg},@var{offset},@var{len}
39144 Collect @var{len} bytes of memory starting at the address in register
39145 number @var{basereg}, plus @var{offset}. If @var{basereg} is
39146 @samp{-1}, then the range has a fixed address: @var{offset} is the
39147 address of the lowest byte to collect. The @var{basereg},
39148 @var{offset}, and @var{len} parameters are all unsigned hexadecimal
39149 values (the @samp{-1} value for @var{basereg} is a special case).
39151 @item X @var{len},@var{expr}
39152 Evaluate @var{expr}, whose length is @var{len}, and collect memory as
39153 it directs. The agent expression @var{expr} is as described in
39154 @ref{Agent Expressions}. Each byte of the expression is encoded as a
39155 two-digit hex number in the packet; @var{len} is the number of bytes
39156 in the expression (and thus one-half the number of hex digits in the
39161 Any number of actions may be packed together in a single @samp{QTDP}
39162 packet, as long as the packet does not exceed the maximum packet
39163 length (400 bytes, for many stubs). There may be only one @samp{R}
39164 action per tracepoint, and it must precede any @samp{M} or @samp{X}
39165 actions. Any registers referred to by @samp{M} and @samp{X} actions
39166 must be collected by a preceding @samp{R} action. (The
39167 ``while-stepping'' actions are treated as if they were attached to a
39168 separate tracepoint, as far as these restrictions are concerned.)
39173 The packet was understood and carried out.
39175 @xref{Tracepoint Packets,,Relocate instruction reply packet}.
39177 The packet was not recognized.
39180 @item QTDPsrc:@var{n}:@var{addr}:@var{type}:@var{start}:@var{slen}:@var{bytes}
39181 @cindex @samp{QTDPsrc} packet
39182 Specify a source string of tracepoint @var{n} at address @var{addr}.
39183 This is useful to get accurate reproduction of the tracepoints
39184 originally downloaded at the beginning of the trace run. The @var{type}
39185 is the name of the tracepoint part, such as @samp{cond} for the
39186 tracepoint's conditional expression (see below for a list of types), while
39187 @var{bytes} is the string, encoded in hexadecimal.
39189 @var{start} is the offset of the @var{bytes} within the overall source
39190 string, while @var{slen} is the total length of the source string.
39191 This is intended for handling source strings that are longer than will
39192 fit in a single packet.
39193 @c Add detailed example when this info is moved into a dedicated
39194 @c tracepoint descriptions section.
39196 The available string types are @samp{at} for the location,
39197 @samp{cond} for the conditional, and @samp{cmd} for an action command.
39198 @value{GDBN} sends a separate packet for each command in the action
39199 list, in the same order in which the commands are stored in the list.
39201 The target does not need to do anything with source strings except
39202 report them back as part of the replies to the @samp{qTfP}/@samp{qTsP}
39205 Although this packet is optional, and @value{GDBN} will only send it
39206 if the target replies with @samp{TracepointSource} @xref{General
39207 Query Packets}, it makes both disconnected tracing and trace files
39208 much easier to use. Otherwise the user must be careful that the
39209 tracepoints in effect while looking at trace frames are identical to
39210 the ones in effect during the trace run; even a small discrepancy
39211 could cause @samp{tdump} not to work, or a particular trace frame not
39214 @item QTDV:@var{n}:@var{value}:@var{builtin}:@var{name}
39215 @cindex define trace state variable, remote request
39216 @cindex @samp{QTDV} packet
39217 Create a new trace state variable, number @var{n}, with an initial
39218 value of @var{value}, which is a 64-bit signed integer. Both @var{n}
39219 and @var{value} are encoded as hexadecimal values. @value{GDBN} has
39220 the option of not using this packet for initial values of zero; the
39221 target should simply create the trace state variables as they are
39222 mentioned in expressions. The value @var{builtin} should be 1 (one)
39223 if the trace state variable is builtin and 0 (zero) if it is not builtin.
39224 @value{GDBN} only sets @var{builtin} to 1 if a previous @samp{qTfV} or
39225 @samp{qTsV} packet had it set. The contents of @var{name} is the
39226 hex-encoded name (without the leading @samp{$}) of the trace state
39229 @item QTFrame:@var{n}
39230 @cindex @samp{QTFrame} packet
39231 Select the @var{n}'th tracepoint frame from the buffer, and use the
39232 register and memory contents recorded there to answer subsequent
39233 request packets from @value{GDBN}.
39235 A successful reply from the stub indicates that the stub has found the
39236 requested frame. The response is a series of parts, concatenated
39237 without separators, describing the frame we selected. Each part has
39238 one of the following forms:
39242 The selected frame is number @var{n} in the trace frame buffer;
39243 @var{f} is a hexadecimal number. If @var{f} is @samp{-1}, then there
39244 was no frame matching the criteria in the request packet.
39247 The selected trace frame records a hit of tracepoint number @var{t};
39248 @var{t} is a hexadecimal number.
39252 @item QTFrame:pc:@var{addr}
39253 Like @samp{QTFrame:@var{n}}, but select the first tracepoint frame after the
39254 currently selected frame whose PC is @var{addr};
39255 @var{addr} is a hexadecimal number.
39257 @item QTFrame:tdp:@var{t}
39258 Like @samp{QTFrame:@var{n}}, but select the first tracepoint frame after the
39259 currently selected frame that is a hit of tracepoint @var{t}; @var{t}
39260 is a hexadecimal number.
39262 @item QTFrame:range:@var{start}:@var{end}
39263 Like @samp{QTFrame:@var{n}}, but select the first tracepoint frame after the
39264 currently selected frame whose PC is between @var{start} (inclusive)
39265 and @var{end} (inclusive); @var{start} and @var{end} are hexadecimal
39268 @item QTFrame:outside:@var{start}:@var{end}
39269 Like @samp{QTFrame:range:@var{start}:@var{end}}, but select the first
39270 frame @emph{outside} the given range of addresses (exclusive).
39273 @cindex @samp{qTMinFTPILen} packet
39274 This packet requests the minimum length of instruction at which a fast
39275 tracepoint (@pxref{Set Tracepoints}) may be placed. For instance, on
39276 the 32-bit x86 architecture, it is possible to use a 4-byte jump, but
39277 it depends on the target system being able to create trampolines in
39278 the first 64K of memory, which might or might not be possible for that
39279 system. So the reply to this packet will be 4 if it is able to
39286 The minimum instruction length is currently unknown.
39288 The minimum instruction length is @var{length}, where @var{length}
39289 is a hexadecimal number greater or equal to 1. A reply
39290 of 1 means that a fast tracepoint may be placed on any instruction
39291 regardless of size.
39293 An error has occurred.
39295 An empty reply indicates that the request is not supported by the stub.
39299 @cindex @samp{QTStart} packet
39300 Begin the tracepoint experiment. Begin collecting data from
39301 tracepoint hits in the trace frame buffer. This packet supports the
39302 @samp{qRelocInsn} reply (@pxref{Tracepoint Packets,,Relocate
39303 instruction reply packet}).
39306 @cindex @samp{QTStop} packet
39307 End the tracepoint experiment. Stop collecting trace frames.
39309 @item QTEnable:@var{n}:@var{addr}
39311 @cindex @samp{QTEnable} packet
39312 Enable tracepoint @var{n} at address @var{addr} in a started tracepoint
39313 experiment. If the tracepoint was previously disabled, then collection
39314 of data from it will resume.
39316 @item QTDisable:@var{n}:@var{addr}
39318 @cindex @samp{QTDisable} packet
39319 Disable tracepoint @var{n} at address @var{addr} in a started tracepoint
39320 experiment. No more data will be collected from the tracepoint unless
39321 @samp{QTEnable:@var{n}:@var{addr}} is subsequently issued.
39324 @cindex @samp{QTinit} packet
39325 Clear the table of tracepoints, and empty the trace frame buffer.
39327 @item QTro:@var{start1},@var{end1}:@var{start2},@var{end2}:@dots{}
39328 @cindex @samp{QTro} packet
39329 Establish the given ranges of memory as ``transparent''. The stub
39330 will answer requests for these ranges from memory's current contents,
39331 if they were not collected as part of the tracepoint hit.
39333 @value{GDBN} uses this to mark read-only regions of memory, like those
39334 containing program code. Since these areas never change, they should
39335 still have the same contents they did when the tracepoint was hit, so
39336 there's no reason for the stub to refuse to provide their contents.
39338 @item QTDisconnected:@var{value}
39339 @cindex @samp{QTDisconnected} packet
39340 Set the choice to what to do with the tracing run when @value{GDBN}
39341 disconnects from the target. A @var{value} of 1 directs the target to
39342 continue the tracing run, while 0 tells the target to stop tracing if
39343 @value{GDBN} is no longer in the picture.
39346 @cindex @samp{qTStatus} packet
39347 Ask the stub if there is a trace experiment running right now.
39349 The reply has the form:
39353 @item T@var{running}@r{[};@var{field}@r{]}@dots{}
39354 @var{running} is a single digit @code{1} if the trace is presently
39355 running, or @code{0} if not. It is followed by semicolon-separated
39356 optional fields that an agent may use to report additional status.
39360 If the trace is not running, the agent may report any of several
39361 explanations as one of the optional fields:
39366 No trace has been run yet.
39368 @item tstop[:@var{text}]:0
39369 The trace was stopped by a user-originated stop command. The optional
39370 @var{text} field is a user-supplied string supplied as part of the
39371 stop command (for instance, an explanation of why the trace was
39372 stopped manually). It is hex-encoded.
39375 The trace stopped because the trace buffer filled up.
39377 @item tdisconnected:0
39378 The trace stopped because @value{GDBN} disconnected from the target.
39380 @item tpasscount:@var{tpnum}
39381 The trace stopped because tracepoint @var{tpnum} exceeded its pass count.
39383 @item terror:@var{text}:@var{tpnum}
39384 The trace stopped because tracepoint @var{tpnum} had an error. The
39385 string @var{text} is available to describe the nature of the error
39386 (for instance, a divide by zero in the condition expression); it
39390 The trace stopped for some other reason.
39394 Additional optional fields supply statistical and other information.
39395 Although not required, they are extremely useful for users monitoring
39396 the progress of a trace run. If a trace has stopped, and these
39397 numbers are reported, they must reflect the state of the just-stopped
39402 @item tframes:@var{n}
39403 The number of trace frames in the buffer.
39405 @item tcreated:@var{n}
39406 The total number of trace frames created during the run. This may
39407 be larger than the trace frame count, if the buffer is circular.
39409 @item tsize:@var{n}
39410 The total size of the trace buffer, in bytes.
39412 @item tfree:@var{n}
39413 The number of bytes still unused in the buffer.
39415 @item circular:@var{n}
39416 The value of the circular trace buffer flag. @code{1} means that the
39417 trace buffer is circular and old trace frames will be discarded if
39418 necessary to make room, @code{0} means that the trace buffer is linear
39421 @item disconn:@var{n}
39422 The value of the disconnected tracing flag. @code{1} means that
39423 tracing will continue after @value{GDBN} disconnects, @code{0} means
39424 that the trace run will stop.
39428 @item qTP:@var{tp}:@var{addr}
39429 @cindex tracepoint status, remote request
39430 @cindex @samp{qTP} packet
39431 Ask the stub for the current state of tracepoint number @var{tp} at
39432 address @var{addr}.
39436 @item V@var{hits}:@var{usage}
39437 The tracepoint has been hit @var{hits} times so far during the trace
39438 run, and accounts for @var{usage} in the trace buffer. Note that
39439 @code{while-stepping} steps are not counted as separate hits, but the
39440 steps' space consumption is added into the usage number.
39444 @item qTV:@var{var}
39445 @cindex trace state variable value, remote request
39446 @cindex @samp{qTV} packet
39447 Ask the stub for the value of the trace state variable number @var{var}.
39452 The value of the variable is @var{value}. This will be the current
39453 value of the variable if the user is examining a running target, or a
39454 saved value if the variable was collected in the trace frame that the
39455 user is looking at. Note that multiple requests may result in
39456 different reply values, such as when requesting values while the
39457 program is running.
39460 The value of the variable is unknown. This would occur, for example,
39461 if the user is examining a trace frame in which the requested variable
39466 @cindex @samp{qTfP} packet
39468 @cindex @samp{qTsP} packet
39469 These packets request data about tracepoints that are being used by
39470 the target. @value{GDBN} sends @code{qTfP} to get the first piece
39471 of data, and multiple @code{qTsP} to get additional pieces. Replies
39472 to these packets generally take the form of the @code{QTDP} packets
39473 that define tracepoints. (FIXME add detailed syntax)
39476 @cindex @samp{qTfV} packet
39478 @cindex @samp{qTsV} packet
39479 These packets request data about trace state variables that are on the
39480 target. @value{GDBN} sends @code{qTfV} to get the first vari of data,
39481 and multiple @code{qTsV} to get additional variables. Replies to
39482 these packets follow the syntax of the @code{QTDV} packets that define
39483 trace state variables.
39489 @cindex @samp{qTfSTM} packet
39490 @cindex @samp{qTsSTM} packet
39491 These packets request data about static tracepoint markers that exist
39492 in the target program. @value{GDBN} sends @code{qTfSTM} to get the
39493 first piece of data, and multiple @code{qTsSTM} to get additional
39494 pieces. Replies to these packets take the following form:
39498 @item m @var{address}:@var{id}:@var{extra}
39500 @item m @var{address}:@var{id}:@var{extra},@var{address}:@var{id}:@var{extra}@dots{}
39501 a comma-separated list of markers
39503 (lower case letter @samp{L}) denotes end of list.
39505 An error occurred. The error number @var{nn} is given as hex digits.
39507 An empty reply indicates that the request is not supported by the
39511 The @var{address} is encoded in hex;
39512 @var{id} and @var{extra} are strings encoded in hex.
39514 In response to each query, the target will reply with a list of one or
39515 more markers, separated by commas. @value{GDBN} will respond to each
39516 reply with a request for more markers (using the @samp{qs} form of the
39517 query), until the target responds with @samp{l} (lower-case ell, for
39520 @item qTSTMat:@var{address}
39522 @cindex @samp{qTSTMat} packet
39523 This packets requests data about static tracepoint markers in the
39524 target program at @var{address}. Replies to this packet follow the
39525 syntax of the @samp{qTfSTM} and @code{qTsSTM} packets that list static
39526 tracepoint markers.
39528 @item QTSave:@var{filename}
39529 @cindex @samp{QTSave} packet
39530 This packet directs the target to save trace data to the file name
39531 @var{filename} in the target's filesystem. The @var{filename} is encoded
39532 as a hex string; the interpretation of the file name (relative vs
39533 absolute, wild cards, etc) is up to the target.
39535 @item qTBuffer:@var{offset},@var{len}
39536 @cindex @samp{qTBuffer} packet
39537 Return up to @var{len} bytes of the current contents of trace buffer,
39538 starting at @var{offset}. The trace buffer is treated as if it were
39539 a contiguous collection of traceframes, as per the trace file format.
39540 The reply consists as many hex-encoded bytes as the target can deliver
39541 in a packet; it is not an error to return fewer than were asked for.
39542 A reply consisting of just @code{l} indicates that no bytes are
39545 @item QTBuffer:circular:@var{value}
39546 This packet directs the target to use a circular trace buffer if
39547 @var{value} is 1, or a linear buffer if the value is 0.
39549 @item QTBuffer:size:@var{size}
39550 @anchor{QTBuffer-size}
39551 @cindex @samp{QTBuffer size} packet
39552 This packet directs the target to make the trace buffer be of size
39553 @var{size} if possible. A value of @code{-1} tells the target to
39554 use whatever size it prefers.
39556 @item QTNotes:@r{[}@var{type}:@var{text}@r{]}@r{[};@var{type}:@var{text}@r{]}@dots{}
39557 @cindex @samp{QTNotes} packet
39558 This packet adds optional textual notes to the trace run. Allowable
39559 types include @code{user}, @code{notes}, and @code{tstop}, the
39560 @var{text} fields are arbitrary strings, hex-encoded.
39564 @subsection Relocate instruction reply packet
39565 When installing fast tracepoints in memory, the target may need to
39566 relocate the instruction currently at the tracepoint address to a
39567 different address in memory. For most instructions, a simple copy is
39568 enough, but, for example, call instructions that implicitly push the
39569 return address on the stack, and relative branches or other
39570 PC-relative instructions require offset adjustment, so that the effect
39571 of executing the instruction at a different address is the same as if
39572 it had executed in the original location.
39574 In response to several of the tracepoint packets, the target may also
39575 respond with a number of intermediate @samp{qRelocInsn} request
39576 packets before the final result packet, to have @value{GDBN} handle
39577 this relocation operation. If a packet supports this mechanism, its
39578 documentation will explicitly say so. See for example the above
39579 descriptions for the @samp{QTStart} and @samp{QTDP} packets. The
39580 format of the request is:
39583 @item qRelocInsn:@var{from};@var{to}
39585 This requests @value{GDBN} to copy instruction at address @var{from}
39586 to address @var{to}, possibly adjusted so that executing the
39587 instruction at @var{to} has the same effect as executing it at
39588 @var{from}. @value{GDBN} writes the adjusted instruction to target
39589 memory starting at @var{to}.
39594 @item qRelocInsn:@var{adjusted_size}
39595 Informs the stub the relocation is complete. The @var{adjusted_size} is
39596 the length in bytes of resulting relocated instruction sequence.
39598 A badly formed request was detected, or an error was encountered while
39599 relocating the instruction.
39602 @node Host I/O Packets
39603 @section Host I/O Packets
39604 @cindex Host I/O, remote protocol
39605 @cindex file transfer, remote protocol
39607 The @dfn{Host I/O} packets allow @value{GDBN} to perform I/O
39608 operations on the far side of a remote link. For example, Host I/O is
39609 used to upload and download files to a remote target with its own
39610 filesystem. Host I/O uses the same constant values and data structure
39611 layout as the target-initiated File-I/O protocol. However, the
39612 Host I/O packets are structured differently. The target-initiated
39613 protocol relies on target memory to store parameters and buffers.
39614 Host I/O requests are initiated by @value{GDBN}, and the
39615 target's memory is not involved. @xref{File-I/O Remote Protocol
39616 Extension}, for more details on the target-initiated protocol.
39618 The Host I/O request packets all encode a single operation along with
39619 its arguments. They have this format:
39623 @item vFile:@var{operation}: @var{parameter}@dots{}
39624 @var{operation} is the name of the particular request; the target
39625 should compare the entire packet name up to the second colon when checking
39626 for a supported operation. The format of @var{parameter} depends on
39627 the operation. Numbers are always passed in hexadecimal. Negative
39628 numbers have an explicit minus sign (i.e.@: two's complement is not
39629 used). Strings (e.g.@: filenames) are encoded as a series of
39630 hexadecimal bytes. The last argument to a system call may be a
39631 buffer of escaped binary data (@pxref{Binary Data}).
39635 The valid responses to Host I/O packets are:
39639 @item F @var{result} [, @var{errno}] [; @var{attachment}]
39640 @var{result} is the integer value returned by this operation, usually
39641 non-negative for success and -1 for errors. If an error has occured,
39642 @var{errno} will be included in the result specifying a
39643 value defined by the File-I/O protocol (@pxref{Errno Values}). For
39644 operations which return data, @var{attachment} supplies the data as a
39645 binary buffer. Binary buffers in response packets are escaped in the
39646 normal way (@pxref{Binary Data}). See the individual packet
39647 documentation for the interpretation of @var{result} and
39651 An empty response indicates that this operation is not recognized.
39655 These are the supported Host I/O operations:
39658 @item vFile:open: @var{filename}, @var{flags}, @var{mode}
39659 Open a file at @var{filename} and return a file descriptor for it, or
39660 return -1 if an error occurs. The @var{filename} is a string,
39661 @var{flags} is an integer indicating a mask of open flags
39662 (@pxref{Open Flags}), and @var{mode} is an integer indicating a mask
39663 of mode bits to use if the file is created (@pxref{mode_t Values}).
39664 @xref{open}, for details of the open flags and mode values.
39666 @item vFile:close: @var{fd}
39667 Close the open file corresponding to @var{fd} and return 0, or
39668 -1 if an error occurs.
39670 @item vFile:pread: @var{fd}, @var{count}, @var{offset}
39671 Read data from the open file corresponding to @var{fd}. Up to
39672 @var{count} bytes will be read from the file, starting at @var{offset}
39673 relative to the start of the file. The target may read fewer bytes;
39674 common reasons include packet size limits and an end-of-file
39675 condition. The number of bytes read is returned. Zero should only be
39676 returned for a successful read at the end of the file, or if
39677 @var{count} was zero.
39679 The data read should be returned as a binary attachment on success.
39680 If zero bytes were read, the response should include an empty binary
39681 attachment (i.e.@: a trailing semicolon). The return value is the
39682 number of target bytes read; the binary attachment may be longer if
39683 some characters were escaped.
39685 @item vFile:pwrite: @var{fd}, @var{offset}, @var{data}
39686 Write @var{data} (a binary buffer) to the open file corresponding
39687 to @var{fd}. Start the write at @var{offset} from the start of the
39688 file. Unlike many @code{write} system calls, there is no
39689 separate @var{count} argument; the length of @var{data} in the
39690 packet is used. @samp{vFile:write} returns the number of bytes written,
39691 which may be shorter than the length of @var{data}, or -1 if an
39694 @item vFile:fstat: @var{fd}
39695 Get information about the open file corresponding to @var{fd}.
39696 On success the information is returned as a binary attachment
39697 and the return value is the size of this attachment in bytes.
39698 If an error occurs the return value is -1. The format of the
39699 returned binary attachment is as described in @ref{struct stat}.
39701 @item vFile:unlink: @var{filename}
39702 Delete the file at @var{filename} on the target. Return 0,
39703 or -1 if an error occurs. The @var{filename} is a string.
39705 @item vFile:readlink: @var{filename}
39706 Read value of symbolic link @var{filename} on the target. Return
39707 the number of bytes read, or -1 if an error occurs.
39709 The data read should be returned as a binary attachment on success.
39710 If zero bytes were read, the response should include an empty binary
39711 attachment (i.e.@: a trailing semicolon). The return value is the
39712 number of target bytes read; the binary attachment may be longer if
39713 some characters were escaped.
39715 @item vFile:setfs: @var{pid}
39716 Select the filesystem on which @code{vFile} operations with
39717 @var{filename} arguments will operate. This is required for
39718 @value{GDBN} to be able to access files on remote targets where
39719 the remote stub does not share a common filesystem with the
39722 If @var{pid} is nonzero, select the filesystem as seen by process
39723 @var{pid}. If @var{pid} is zero, select the filesystem as seen by
39724 the remote stub. Return 0 on success, or -1 if an error occurs.
39725 If @code{vFile:setfs:} indicates success, the selected filesystem
39726 remains selected until the next successful @code{vFile:setfs:}
39732 @section Interrupts
39733 @cindex interrupts (remote protocol)
39734 @anchor{interrupting remote targets}
39736 In all-stop mode, when a program on the remote target is running,
39737 @value{GDBN} may attempt to interrupt it by sending a @samp{Ctrl-C},
39738 @code{BREAK} or a @code{BREAK} followed by @code{g}, control of which
39739 is specified via @value{GDBN}'s @samp{interrupt-sequence}.
39741 The precise meaning of @code{BREAK} is defined by the transport
39742 mechanism and may, in fact, be undefined. @value{GDBN} does not
39743 currently define a @code{BREAK} mechanism for any of the network
39744 interfaces except for TCP, in which case @value{GDBN} sends the
39745 @code{telnet} BREAK sequence.
39747 @samp{Ctrl-C}, on the other hand, is defined and implemented for all
39748 transport mechanisms. It is represented by sending the single byte
39749 @code{0x03} without any of the usual packet overhead described in
39750 the Overview section (@pxref{Overview}). When a @code{0x03} byte is
39751 transmitted as part of a packet, it is considered to be packet data
39752 and does @emph{not} represent an interrupt. E.g., an @samp{X} packet
39753 (@pxref{X packet}), used for binary downloads, may include an unescaped
39754 @code{0x03} as part of its packet.
39756 @code{BREAK} followed by @code{g} is also known as Magic SysRq g.
39757 When Linux kernel receives this sequence from serial port,
39758 it stops execution and connects to gdb.
39760 In non-stop mode, because packet resumptions are asynchronous
39761 (@pxref{vCont packet}), @value{GDBN} is always free to send a remote
39762 command to the remote stub, even when the target is running. For that
39763 reason, @value{GDBN} instead sends a regular packet (@pxref{vCtrlC
39764 packet}) with the usual packet framing instead of the single byte
39767 Stubs are not required to recognize these interrupt mechanisms and the
39768 precise meaning associated with receipt of the interrupt is
39769 implementation defined. If the target supports debugging of multiple
39770 threads and/or processes, it should attempt to interrupt all
39771 currently-executing threads and processes.
39772 If the stub is successful at interrupting the
39773 running program, it should send one of the stop
39774 reply packets (@pxref{Stop Reply Packets}) to @value{GDBN} as a result
39775 of successfully stopping the program in all-stop mode, and a stop reply
39776 for each stopped thread in non-stop mode.
39777 Interrupts received while the
39778 program is stopped are queued and the program will be interrupted when
39779 it is resumed next time.
39781 @node Notification Packets
39782 @section Notification Packets
39783 @cindex notification packets
39784 @cindex packets, notification
39786 The @value{GDBN} remote serial protocol includes @dfn{notifications},
39787 packets that require no acknowledgment. Both the GDB and the stub
39788 may send notifications (although the only notifications defined at
39789 present are sent by the stub). Notifications carry information
39790 without incurring the round-trip latency of an acknowledgment, and so
39791 are useful for low-impact communications where occasional packet loss
39794 A notification packet has the form @samp{% @var{data} #
39795 @var{checksum}}, where @var{data} is the content of the notification,
39796 and @var{checksum} is a checksum of @var{data}, computed and formatted
39797 as for ordinary @value{GDBN} packets. A notification's @var{data}
39798 never contains @samp{$}, @samp{%} or @samp{#} characters. Upon
39799 receiving a notification, the recipient sends no @samp{+} or @samp{-}
39800 to acknowledge the notification's receipt or to report its corruption.
39802 Every notification's @var{data} begins with a name, which contains no
39803 colon characters, followed by a colon character.
39805 Recipients should silently ignore corrupted notifications and
39806 notifications they do not understand. Recipients should restart
39807 timeout periods on receipt of a well-formed notification, whether or
39808 not they understand it.
39810 Senders should only send the notifications described here when this
39811 protocol description specifies that they are permitted. In the
39812 future, we may extend the protocol to permit existing notifications in
39813 new contexts; this rule helps older senders avoid confusing newer
39816 (Older versions of @value{GDBN} ignore bytes received until they see
39817 the @samp{$} byte that begins an ordinary packet, so new stubs may
39818 transmit notifications without fear of confusing older clients. There
39819 are no notifications defined for @value{GDBN} to send at the moment, but we
39820 assume that most older stubs would ignore them, as well.)
39822 Each notification is comprised of three parts:
39824 @item @var{name}:@var{event}
39825 The notification packet is sent by the side that initiates the
39826 exchange (currently, only the stub does that), with @var{event}
39827 carrying the specific information about the notification, and
39828 @var{name} specifying the name of the notification.
39830 The acknowledge sent by the other side, usually @value{GDBN}, to
39831 acknowledge the exchange and request the event.
39834 The purpose of an asynchronous notification mechanism is to report to
39835 @value{GDBN} that something interesting happened in the remote stub.
39837 The remote stub may send notification @var{name}:@var{event}
39838 at any time, but @value{GDBN} acknowledges the notification when
39839 appropriate. The notification event is pending before @value{GDBN}
39840 acknowledges. Only one notification at a time may be pending; if
39841 additional events occur before @value{GDBN} has acknowledged the
39842 previous notification, they must be queued by the stub for later
39843 synchronous transmission in response to @var{ack} packets from
39844 @value{GDBN}. Because the notification mechanism is unreliable,
39845 the stub is permitted to resend a notification if it believes
39846 @value{GDBN} may not have received it.
39848 Specifically, notifications may appear when @value{GDBN} is not
39849 otherwise reading input from the stub, or when @value{GDBN} is
39850 expecting to read a normal synchronous response or a
39851 @samp{+}/@samp{-} acknowledgment to a packet it has sent.
39852 Notification packets are distinct from any other communication from
39853 the stub so there is no ambiguity.
39855 After receiving a notification, @value{GDBN} shall acknowledge it by
39856 sending a @var{ack} packet as a regular, synchronous request to the
39857 stub. Such acknowledgment is not required to happen immediately, as
39858 @value{GDBN} is permitted to send other, unrelated packets to the
39859 stub first, which the stub should process normally.
39861 Upon receiving a @var{ack} packet, if the stub has other queued
39862 events to report to @value{GDBN}, it shall respond by sending a
39863 normal @var{event}. @value{GDBN} shall then send another @var{ack}
39864 packet to solicit further responses; again, it is permitted to send
39865 other, unrelated packets as well which the stub should process
39868 If the stub receives a @var{ack} packet and there are no additional
39869 @var{event} to report, the stub shall return an @samp{OK} response.
39870 At this point, @value{GDBN} has finished processing a notification
39871 and the stub has completed sending any queued events. @value{GDBN}
39872 won't accept any new notifications until the final @samp{OK} is
39873 received . If further notification events occur, the stub shall send
39874 a new notification, @value{GDBN} shall accept the notification, and
39875 the process shall be repeated.
39877 The process of asynchronous notification can be illustrated by the
39880 <- @code{%Stop:T0505:98e7ffbf;04:4ce6ffbf;08:b1b6e54c;thread:p7526.7526;core:0;}
39883 <- @code{T0505:68f37db7;04:40f37db7;08:63850408;thread:p7526.7528;core:0;}
39885 <- @code{T0505:68e3fdb6;04:40e3fdb6;08:63850408;thread:p7526.7529;core:0;}
39890 The following notifications are defined:
39891 @multitable @columnfractions 0.12 0.12 0.38 0.38
39900 @tab @var{reply}. The @var{reply} has the form of a stop reply, as
39901 described in @ref{Stop Reply Packets}. Refer to @ref{Remote Non-Stop},
39902 for information on how these notifications are acknowledged by
39904 @tab Report an asynchronous stop event in non-stop mode.
39908 @node Remote Non-Stop
39909 @section Remote Protocol Support for Non-Stop Mode
39911 @value{GDBN}'s remote protocol supports non-stop debugging of
39912 multi-threaded programs, as described in @ref{Non-Stop Mode}. If the stub
39913 supports non-stop mode, it should report that to @value{GDBN} by including
39914 @samp{QNonStop+} in its @samp{qSupported} response (@pxref{qSupported}).
39916 @value{GDBN} typically sends a @samp{QNonStop} packet only when
39917 establishing a new connection with the stub. Entering non-stop mode
39918 does not alter the state of any currently-running threads, but targets
39919 must stop all threads in any already-attached processes when entering
39920 all-stop mode. @value{GDBN} uses the @samp{?} packet as necessary to
39921 probe the target state after a mode change.
39923 In non-stop mode, when an attached process encounters an event that
39924 would otherwise be reported with a stop reply, it uses the
39925 asynchronous notification mechanism (@pxref{Notification Packets}) to
39926 inform @value{GDBN}. In contrast to all-stop mode, where all threads
39927 in all processes are stopped when a stop reply is sent, in non-stop
39928 mode only the thread reporting the stop event is stopped. That is,
39929 when reporting a @samp{S} or @samp{T} response to indicate completion
39930 of a step operation, hitting a breakpoint, or a fault, only the
39931 affected thread is stopped; any other still-running threads continue
39932 to run. When reporting a @samp{W} or @samp{X} response, all running
39933 threads belonging to other attached processes continue to run.
39935 In non-stop mode, the target shall respond to the @samp{?} packet as
39936 follows. First, any incomplete stop reply notification/@samp{vStopped}
39937 sequence in progress is abandoned. The target must begin a new
39938 sequence reporting stop events for all stopped threads, whether or not
39939 it has previously reported those events to @value{GDBN}. The first
39940 stop reply is sent as a synchronous reply to the @samp{?} packet, and
39941 subsequent stop replies are sent as responses to @samp{vStopped} packets
39942 using the mechanism described above. The target must not send
39943 asynchronous stop reply notifications until the sequence is complete.
39944 If all threads are running when the target receives the @samp{?} packet,
39945 or if the target is not attached to any process, it shall respond
39948 If the stub supports non-stop mode, it should also support the
39949 @samp{swbreak} stop reason if software breakpoints are supported, and
39950 the @samp{hwbreak} stop reason if hardware breakpoints are supported
39951 (@pxref{swbreak stop reason}). This is because given the asynchronous
39952 nature of non-stop mode, between the time a thread hits a breakpoint
39953 and the time the event is finally processed by @value{GDBN}, the
39954 breakpoint may have already been removed from the target. Due to
39955 this, @value{GDBN} needs to be able to tell whether a trap stop was
39956 caused by a delayed breakpoint event, which should be ignored, as
39957 opposed to a random trap signal, which should be reported to the user.
39958 Note the @samp{swbreak} feature implies that the target is responsible
39959 for adjusting the PC when a software breakpoint triggers, if
39960 necessary, such as on the x86 architecture.
39962 @node Packet Acknowledgment
39963 @section Packet Acknowledgment
39965 @cindex acknowledgment, for @value{GDBN} remote
39966 @cindex packet acknowledgment, for @value{GDBN} remote
39967 By default, when either the host or the target machine receives a packet,
39968 the first response expected is an acknowledgment: either @samp{+} (to indicate
39969 the package was received correctly) or @samp{-} (to request retransmission).
39970 This mechanism allows the @value{GDBN} remote protocol to operate over
39971 unreliable transport mechanisms, such as a serial line.
39973 In cases where the transport mechanism is itself reliable (such as a pipe or
39974 TCP connection), the @samp{+}/@samp{-} acknowledgments are redundant.
39975 It may be desirable to disable them in that case to reduce communication
39976 overhead, or for other reasons. This can be accomplished by means of the
39977 @samp{QStartNoAckMode} packet; @pxref{QStartNoAckMode}.
39979 When in no-acknowledgment mode, neither the stub nor @value{GDBN} shall send or
39980 expect @samp{+}/@samp{-} protocol acknowledgments. The packet
39981 and response format still includes the normal checksum, as described in
39982 @ref{Overview}, but the checksum may be ignored by the receiver.
39984 If the stub supports @samp{QStartNoAckMode} and prefers to operate in
39985 no-acknowledgment mode, it should report that to @value{GDBN}
39986 by including @samp{QStartNoAckMode+} in its response to @samp{qSupported};
39987 @pxref{qSupported}.
39988 If @value{GDBN} also supports @samp{QStartNoAckMode} and it has not been
39989 disabled via the @code{set remote noack-packet off} command
39990 (@pxref{Remote Configuration}),
39991 @value{GDBN} may then send a @samp{QStartNoAckMode} packet to the stub.
39992 Only then may the stub actually turn off packet acknowledgments.
39993 @value{GDBN} sends a final @samp{+} acknowledgment of the stub's @samp{OK}
39994 response, which can be safely ignored by the stub.
39996 Note that @code{set remote noack-packet} command only affects negotiation
39997 between @value{GDBN} and the stub when subsequent connections are made;
39998 it does not affect the protocol acknowledgment state for any current
40000 Since @samp{+}/@samp{-} acknowledgments are enabled by default when a
40001 new connection is established,
40002 there is also no protocol request to re-enable the acknowledgments
40003 for the current connection, once disabled.
40008 Example sequence of a target being re-started. Notice how the restart
40009 does not get any direct output:
40014 @emph{target restarts}
40017 <- @code{T001:1234123412341234}
40021 Example sequence of a target being stepped by a single instruction:
40024 -> @code{G1445@dots{}}
40029 <- @code{T001:1234123412341234}
40033 <- @code{1455@dots{}}
40037 @node File-I/O Remote Protocol Extension
40038 @section File-I/O Remote Protocol Extension
40039 @cindex File-I/O remote protocol extension
40042 * File-I/O Overview::
40043 * Protocol Basics::
40044 * The F Request Packet::
40045 * The F Reply Packet::
40046 * The Ctrl-C Message::
40048 * List of Supported Calls::
40049 * Protocol-specific Representation of Datatypes::
40051 * File-I/O Examples::
40054 @node File-I/O Overview
40055 @subsection File-I/O Overview
40056 @cindex file-i/o overview
40058 The @dfn{File I/O remote protocol extension} (short: File-I/O) allows the
40059 target to use the host's file system and console I/O to perform various
40060 system calls. System calls on the target system are translated into a
40061 remote protocol packet to the host system, which then performs the needed
40062 actions and returns a response packet to the target system.
40063 This simulates file system operations even on targets that lack file systems.
40065 The protocol is defined to be independent of both the host and target systems.
40066 It uses its own internal representation of datatypes and values. Both
40067 @value{GDBN} and the target's @value{GDBN} stub are responsible for
40068 translating the system-dependent value representations into the internal
40069 protocol representations when data is transmitted.
40071 The communication is synchronous. A system call is possible only when
40072 @value{GDBN} is waiting for a response from the @samp{C}, @samp{c}, @samp{S}
40073 or @samp{s} packets. While @value{GDBN} handles the request for a system call,
40074 the target is stopped to allow deterministic access to the target's
40075 memory. Therefore File-I/O is not interruptible by target signals. On
40076 the other hand, it is possible to interrupt File-I/O by a user interrupt
40077 (@samp{Ctrl-C}) within @value{GDBN}.
40079 The target's request to perform a host system call does not finish
40080 the latest @samp{C}, @samp{c}, @samp{S} or @samp{s} action. That means,
40081 after finishing the system call, the target returns to continuing the
40082 previous activity (continue, step). No additional continue or step
40083 request from @value{GDBN} is required.
40086 (@value{GDBP}) continue
40087 <- target requests 'system call X'
40088 target is stopped, @value{GDBN} executes system call
40089 -> @value{GDBN} returns result
40090 ... target continues, @value{GDBN} returns to wait for the target
40091 <- target hits breakpoint and sends a Txx packet
40094 The protocol only supports I/O on the console and to regular files on
40095 the host file system. Character or block special devices, pipes,
40096 named pipes, sockets or any other communication method on the host
40097 system are not supported by this protocol.
40099 File I/O is not supported in non-stop mode.
40101 @node Protocol Basics
40102 @subsection Protocol Basics
40103 @cindex protocol basics, file-i/o
40105 The File-I/O protocol uses the @code{F} packet as the request as well
40106 as reply packet. Since a File-I/O system call can only occur when
40107 @value{GDBN} is waiting for a response from the continuing or stepping target,
40108 the File-I/O request is a reply that @value{GDBN} has to expect as a result
40109 of a previous @samp{C}, @samp{c}, @samp{S} or @samp{s} packet.
40110 This @code{F} packet contains all information needed to allow @value{GDBN}
40111 to call the appropriate host system call:
40115 A unique identifier for the requested system call.
40118 All parameters to the system call. Pointers are given as addresses
40119 in the target memory address space. Pointers to strings are given as
40120 pointer/length pair. Numerical values are given as they are.
40121 Numerical control flags are given in a protocol-specific representation.
40125 At this point, @value{GDBN} has to perform the following actions.
40129 If the parameters include pointer values to data needed as input to a
40130 system call, @value{GDBN} requests this data from the target with a
40131 standard @code{m} packet request. This additional communication has to be
40132 expected by the target implementation and is handled as any other @code{m}
40136 @value{GDBN} translates all value from protocol representation to host
40137 representation as needed. Datatypes are coerced into the host types.
40140 @value{GDBN} calls the system call.
40143 It then coerces datatypes back to protocol representation.
40146 If the system call is expected to return data in buffer space specified
40147 by pointer parameters to the call, the data is transmitted to the
40148 target using a @code{M} or @code{X} packet. This packet has to be expected
40149 by the target implementation and is handled as any other @code{M} or @code{X}
40154 Eventually @value{GDBN} replies with another @code{F} packet which contains all
40155 necessary information for the target to continue. This at least contains
40162 @code{errno}, if has been changed by the system call.
40169 After having done the needed type and value coercion, the target continues
40170 the latest continue or step action.
40172 @node The F Request Packet
40173 @subsection The @code{F} Request Packet
40174 @cindex file-i/o request packet
40175 @cindex @code{F} request packet
40177 The @code{F} request packet has the following format:
40180 @item F@var{call-id},@var{parameter@dots{}}
40182 @var{call-id} is the identifier to indicate the host system call to be called.
40183 This is just the name of the function.
40185 @var{parameter@dots{}} are the parameters to the system call.
40186 Parameters are hexadecimal integer values, either the actual values in case
40187 of scalar datatypes, pointers to target buffer space in case of compound
40188 datatypes and unspecified memory areas, or pointer/length pairs in case
40189 of string parameters. These are appended to the @var{call-id} as a
40190 comma-delimited list. All values are transmitted in ASCII
40191 string representation, pointer/length pairs separated by a slash.
40197 @node The F Reply Packet
40198 @subsection The @code{F} Reply Packet
40199 @cindex file-i/o reply packet
40200 @cindex @code{F} reply packet
40202 The @code{F} reply packet has the following format:
40206 @item F@var{retcode},@var{errno},@var{Ctrl-C flag};@var{call-specific attachment}
40208 @var{retcode} is the return code of the system call as hexadecimal value.
40210 @var{errno} is the @code{errno} set by the call, in protocol-specific
40212 This parameter can be omitted if the call was successful.
40214 @var{Ctrl-C flag} is only sent if the user requested a break. In this
40215 case, @var{errno} must be sent as well, even if the call was successful.
40216 The @var{Ctrl-C flag} itself consists of the character @samp{C}:
40223 or, if the call was interrupted before the host call has been performed:
40230 assuming 4 is the protocol-specific representation of @code{EINTR}.
40235 @node The Ctrl-C Message
40236 @subsection The @samp{Ctrl-C} Message
40237 @cindex ctrl-c message, in file-i/o protocol
40239 If the @samp{Ctrl-C} flag is set in the @value{GDBN}
40240 reply packet (@pxref{The F Reply Packet}),
40241 the target should behave as if it had
40242 gotten a break message. The meaning for the target is ``system call
40243 interrupted by @code{SIGINT}''. Consequentially, the target should actually stop
40244 (as with a break message) and return to @value{GDBN} with a @code{T02}
40247 It's important for the target to know in which
40248 state the system call was interrupted. There are two possible cases:
40252 The system call hasn't been performed on the host yet.
40255 The system call on the host has been finished.
40259 These two states can be distinguished by the target by the value of the
40260 returned @code{errno}. If it's the protocol representation of @code{EINTR}, the system
40261 call hasn't been performed. This is equivalent to the @code{EINTR} handling
40262 on POSIX systems. In any other case, the target may presume that the
40263 system call has been finished --- successfully or not --- and should behave
40264 as if the break message arrived right after the system call.
40266 @value{GDBN} must behave reliably. If the system call has not been called
40267 yet, @value{GDBN} may send the @code{F} reply immediately, setting @code{EINTR} as
40268 @code{errno} in the packet. If the system call on the host has been finished
40269 before the user requests a break, the full action must be finished by
40270 @value{GDBN}. This requires sending @code{M} or @code{X} packets as necessary.
40271 The @code{F} packet may only be sent when either nothing has happened
40272 or the full action has been completed.
40275 @subsection Console I/O
40276 @cindex console i/o as part of file-i/o
40278 By default and if not explicitly closed by the target system, the file
40279 descriptors 0, 1 and 2 are connected to the @value{GDBN} console. Output
40280 on the @value{GDBN} console is handled as any other file output operation
40281 (@code{write(1, @dots{})} or @code{write(2, @dots{})}). Console input is handled
40282 by @value{GDBN} so that after the target read request from file descriptor
40283 0 all following typing is buffered until either one of the following
40288 The user types @kbd{Ctrl-c}. The behaviour is as explained above, and the
40290 system call is treated as finished.
40293 The user presses @key{RET}. This is treated as end of input with a trailing
40297 The user types @kbd{Ctrl-d}. This is treated as end of input. No trailing
40298 character (neither newline nor @samp{Ctrl-D}) is appended to the input.
40302 If the user has typed more characters than fit in the buffer given to
40303 the @code{read} call, the trailing characters are buffered in @value{GDBN} until
40304 either another @code{read(0, @dots{})} is requested by the target, or debugging
40305 is stopped at the user's request.
40308 @node List of Supported Calls
40309 @subsection List of Supported Calls
40310 @cindex list of supported file-i/o calls
40327 @unnumberedsubsubsec open
40328 @cindex open, file-i/o system call
40333 int open(const char *pathname, int flags);
40334 int open(const char *pathname, int flags, mode_t mode);
40338 @samp{Fopen,@var{pathptr}/@var{len},@var{flags},@var{mode}}
40341 @var{flags} is the bitwise @code{OR} of the following values:
40345 If the file does not exist it will be created. The host
40346 rules apply as far as file ownership and time stamps
40350 When used with @code{O_CREAT}, if the file already exists it is
40351 an error and open() fails.
40354 If the file already exists and the open mode allows
40355 writing (@code{O_RDWR} or @code{O_WRONLY} is given) it will be
40356 truncated to zero length.
40359 The file is opened in append mode.
40362 The file is opened for reading only.
40365 The file is opened for writing only.
40368 The file is opened for reading and writing.
40372 Other bits are silently ignored.
40376 @var{mode} is the bitwise @code{OR} of the following values:
40380 User has read permission.
40383 User has write permission.
40386 Group has read permission.
40389 Group has write permission.
40392 Others have read permission.
40395 Others have write permission.
40399 Other bits are silently ignored.
40402 @item Return value:
40403 @code{open} returns the new file descriptor or -1 if an error
40410 @var{pathname} already exists and @code{O_CREAT} and @code{O_EXCL} were used.
40413 @var{pathname} refers to a directory.
40416 The requested access is not allowed.
40419 @var{pathname} was too long.
40422 A directory component in @var{pathname} does not exist.
40425 @var{pathname} refers to a device, pipe, named pipe or socket.
40428 @var{pathname} refers to a file on a read-only filesystem and
40429 write access was requested.
40432 @var{pathname} is an invalid pointer value.
40435 No space on device to create the file.
40438 The process already has the maximum number of files open.
40441 The limit on the total number of files open on the system
40445 The call was interrupted by the user.
40451 @unnumberedsubsubsec close
40452 @cindex close, file-i/o system call
40461 @samp{Fclose,@var{fd}}
40463 @item Return value:
40464 @code{close} returns zero on success, or -1 if an error occurred.
40470 @var{fd} isn't a valid open file descriptor.
40473 The call was interrupted by the user.
40479 @unnumberedsubsubsec read
40480 @cindex read, file-i/o system call
40485 int read(int fd, void *buf, unsigned int count);
40489 @samp{Fread,@var{fd},@var{bufptr},@var{count}}
40491 @item Return value:
40492 On success, the number of bytes read is returned.
40493 Zero indicates end of file. If count is zero, read
40494 returns zero as well. On error, -1 is returned.
40500 @var{fd} is not a valid file descriptor or is not open for
40504 @var{bufptr} is an invalid pointer value.
40507 The call was interrupted by the user.
40513 @unnumberedsubsubsec write
40514 @cindex write, file-i/o system call
40519 int write(int fd, const void *buf, unsigned int count);
40523 @samp{Fwrite,@var{fd},@var{bufptr},@var{count}}
40525 @item Return value:
40526 On success, the number of bytes written are returned.
40527 Zero indicates nothing was written. On error, -1
40534 @var{fd} is not a valid file descriptor or is not open for
40538 @var{bufptr} is an invalid pointer value.
40541 An attempt was made to write a file that exceeds the
40542 host-specific maximum file size allowed.
40545 No space on device to write the data.
40548 The call was interrupted by the user.
40554 @unnumberedsubsubsec lseek
40555 @cindex lseek, file-i/o system call
40560 long lseek (int fd, long offset, int flag);
40564 @samp{Flseek,@var{fd},@var{offset},@var{flag}}
40566 @var{flag} is one of:
40570 The offset is set to @var{offset} bytes.
40573 The offset is set to its current location plus @var{offset}
40577 The offset is set to the size of the file plus @var{offset}
40581 @item Return value:
40582 On success, the resulting unsigned offset in bytes from
40583 the beginning of the file is returned. Otherwise, a
40584 value of -1 is returned.
40590 @var{fd} is not a valid open file descriptor.
40593 @var{fd} is associated with the @value{GDBN} console.
40596 @var{flag} is not a proper value.
40599 The call was interrupted by the user.
40605 @unnumberedsubsubsec rename
40606 @cindex rename, file-i/o system call
40611 int rename(const char *oldpath, const char *newpath);
40615 @samp{Frename,@var{oldpathptr}/@var{len},@var{newpathptr}/@var{len}}
40617 @item Return value:
40618 On success, zero is returned. On error, -1 is returned.
40624 @var{newpath} is an existing directory, but @var{oldpath} is not a
40628 @var{newpath} is a non-empty directory.
40631 @var{oldpath} or @var{newpath} is a directory that is in use by some
40635 An attempt was made to make a directory a subdirectory
40639 A component used as a directory in @var{oldpath} or new
40640 path is not a directory. Or @var{oldpath} is a directory
40641 and @var{newpath} exists but is not a directory.
40644 @var{oldpathptr} or @var{newpathptr} are invalid pointer values.
40647 No access to the file or the path of the file.
40651 @var{oldpath} or @var{newpath} was too long.
40654 A directory component in @var{oldpath} or @var{newpath} does not exist.
40657 The file is on a read-only filesystem.
40660 The device containing the file has no room for the new
40664 The call was interrupted by the user.
40670 @unnumberedsubsubsec unlink
40671 @cindex unlink, file-i/o system call
40676 int unlink(const char *pathname);
40680 @samp{Funlink,@var{pathnameptr}/@var{len}}
40682 @item Return value:
40683 On success, zero is returned. On error, -1 is returned.
40689 No access to the file or the path of the file.
40692 The system does not allow unlinking of directories.
40695 The file @var{pathname} cannot be unlinked because it's
40696 being used by another process.
40699 @var{pathnameptr} is an invalid pointer value.
40702 @var{pathname} was too long.
40705 A directory component in @var{pathname} does not exist.
40708 A component of the path is not a directory.
40711 The file is on a read-only filesystem.
40714 The call was interrupted by the user.
40720 @unnumberedsubsubsec stat/fstat
40721 @cindex fstat, file-i/o system call
40722 @cindex stat, file-i/o system call
40727 int stat(const char *pathname, struct stat *buf);
40728 int fstat(int fd, struct stat *buf);
40732 @samp{Fstat,@var{pathnameptr}/@var{len},@var{bufptr}}@*
40733 @samp{Ffstat,@var{fd},@var{bufptr}}
40735 @item Return value:
40736 On success, zero is returned. On error, -1 is returned.
40742 @var{fd} is not a valid open file.
40745 A directory component in @var{pathname} does not exist or the
40746 path is an empty string.
40749 A component of the path is not a directory.
40752 @var{pathnameptr} is an invalid pointer value.
40755 No access to the file or the path of the file.
40758 @var{pathname} was too long.
40761 The call was interrupted by the user.
40767 @unnumberedsubsubsec gettimeofday
40768 @cindex gettimeofday, file-i/o system call
40773 int gettimeofday(struct timeval *tv, void *tz);
40777 @samp{Fgettimeofday,@var{tvptr},@var{tzptr}}
40779 @item Return value:
40780 On success, 0 is returned, -1 otherwise.
40786 @var{tz} is a non-NULL pointer.
40789 @var{tvptr} and/or @var{tzptr} is an invalid pointer value.
40795 @unnumberedsubsubsec isatty
40796 @cindex isatty, file-i/o system call
40801 int isatty(int fd);
40805 @samp{Fisatty,@var{fd}}
40807 @item Return value:
40808 Returns 1 if @var{fd} refers to the @value{GDBN} console, 0 otherwise.
40814 The call was interrupted by the user.
40819 Note that the @code{isatty} call is treated as a special case: it returns
40820 1 to the target if the file descriptor is attached
40821 to the @value{GDBN} console, 0 otherwise. Implementing through system calls
40822 would require implementing @code{ioctl} and would be more complex than
40827 @unnumberedsubsubsec system
40828 @cindex system, file-i/o system call
40833 int system(const char *command);
40837 @samp{Fsystem,@var{commandptr}/@var{len}}
40839 @item Return value:
40840 If @var{len} is zero, the return value indicates whether a shell is
40841 available. A zero return value indicates a shell is not available.
40842 For non-zero @var{len}, the value returned is -1 on error and the
40843 return status of the command otherwise. Only the exit status of the
40844 command is returned, which is extracted from the host's @code{system}
40845 return value by calling @code{WEXITSTATUS(retval)}. In case
40846 @file{/bin/sh} could not be executed, 127 is returned.
40852 The call was interrupted by the user.
40857 @value{GDBN} takes over the full task of calling the necessary host calls
40858 to perform the @code{system} call. The return value of @code{system} on
40859 the host is simplified before it's returned
40860 to the target. Any termination signal information from the child process
40861 is discarded, and the return value consists
40862 entirely of the exit status of the called command.
40864 Due to security concerns, the @code{system} call is by default refused
40865 by @value{GDBN}. The user has to allow this call explicitly with the
40866 @code{set remote system-call-allowed 1} command.
40869 @item set remote system-call-allowed
40870 @kindex set remote system-call-allowed
40871 Control whether to allow the @code{system} calls in the File I/O
40872 protocol for the remote target. The default is zero (disabled).
40874 @item show remote system-call-allowed
40875 @kindex show remote system-call-allowed
40876 Show whether the @code{system} calls are allowed in the File I/O
40880 @node Protocol-specific Representation of Datatypes
40881 @subsection Protocol-specific Representation of Datatypes
40882 @cindex protocol-specific representation of datatypes, in file-i/o protocol
40885 * Integral Datatypes::
40887 * Memory Transfer::
40892 @node Integral Datatypes
40893 @unnumberedsubsubsec Integral Datatypes
40894 @cindex integral datatypes, in file-i/o protocol
40896 The integral datatypes used in the system calls are @code{int},
40897 @code{unsigned int}, @code{long}, @code{unsigned long},
40898 @code{mode_t}, and @code{time_t}.
40900 @code{int}, @code{unsigned int}, @code{mode_t} and @code{time_t} are
40901 implemented as 32 bit values in this protocol.
40903 @code{long} and @code{unsigned long} are implemented as 64 bit types.
40905 @xref{Limits}, for corresponding MIN and MAX values (similar to those
40906 in @file{limits.h}) to allow range checking on host and target.
40908 @code{time_t} datatypes are defined as seconds since the Epoch.
40910 All integral datatypes transferred as part of a memory read or write of a
40911 structured datatype e.g.@: a @code{struct stat} have to be given in big endian
40914 @node Pointer Values
40915 @unnumberedsubsubsec Pointer Values
40916 @cindex pointer values, in file-i/o protocol
40918 Pointers to target data are transmitted as they are. An exception
40919 is made for pointers to buffers for which the length isn't
40920 transmitted as part of the function call, namely strings. Strings
40921 are transmitted as a pointer/length pair, both as hex values, e.g.@:
40928 which is a pointer to data of length 18 bytes at position 0x1aaf.
40929 The length is defined as the full string length in bytes, including
40930 the trailing null byte. For example, the string @code{"hello world"}
40931 at address 0x123456 is transmitted as
40937 @node Memory Transfer
40938 @unnumberedsubsubsec Memory Transfer
40939 @cindex memory transfer, in file-i/o protocol
40941 Structured data which is transferred using a memory read or write (for
40942 example, a @code{struct stat}) is expected to be in a protocol-specific format
40943 with all scalar multibyte datatypes being big endian. Translation to
40944 this representation needs to be done both by the target before the @code{F}
40945 packet is sent, and by @value{GDBN} before
40946 it transfers memory to the target. Transferred pointers to structured
40947 data should point to the already-coerced data at any time.
40951 @unnumberedsubsubsec struct stat
40952 @cindex struct stat, in file-i/o protocol
40954 The buffer of type @code{struct stat} used by the target and @value{GDBN}
40955 is defined as follows:
40959 unsigned int st_dev; /* device */
40960 unsigned int st_ino; /* inode */
40961 mode_t st_mode; /* protection */
40962 unsigned int st_nlink; /* number of hard links */
40963 unsigned int st_uid; /* user ID of owner */
40964 unsigned int st_gid; /* group ID of owner */
40965 unsigned int st_rdev; /* device type (if inode device) */
40966 unsigned long st_size; /* total size, in bytes */
40967 unsigned long st_blksize; /* blocksize for filesystem I/O */
40968 unsigned long st_blocks; /* number of blocks allocated */
40969 time_t st_atime; /* time of last access */
40970 time_t st_mtime; /* time of last modification */
40971 time_t st_ctime; /* time of last change */
40975 The integral datatypes conform to the definitions given in the
40976 appropriate section (see @ref{Integral Datatypes}, for details) so this
40977 structure is of size 64 bytes.
40979 The values of several fields have a restricted meaning and/or
40985 A value of 0 represents a file, 1 the console.
40988 No valid meaning for the target. Transmitted unchanged.
40991 Valid mode bits are described in @ref{Constants}. Any other
40992 bits have currently no meaning for the target.
40997 No valid meaning for the target. Transmitted unchanged.
41002 These values have a host and file system dependent
41003 accuracy. Especially on Windows hosts, the file system may not
41004 support exact timing values.
41007 The target gets a @code{struct stat} of the above representation and is
41008 responsible for coercing it to the target representation before
41011 Note that due to size differences between the host, target, and protocol
41012 representations of @code{struct stat} members, these members could eventually
41013 get truncated on the target.
41015 @node struct timeval
41016 @unnumberedsubsubsec struct timeval
41017 @cindex struct timeval, in file-i/o protocol
41019 The buffer of type @code{struct timeval} used by the File-I/O protocol
41020 is defined as follows:
41024 time_t tv_sec; /* second */
41025 long tv_usec; /* microsecond */
41029 The integral datatypes conform to the definitions given in the
41030 appropriate section (see @ref{Integral Datatypes}, for details) so this
41031 structure is of size 8 bytes.
41034 @subsection Constants
41035 @cindex constants, in file-i/o protocol
41037 The following values are used for the constants inside of the
41038 protocol. @value{GDBN} and target are responsible for translating these
41039 values before and after the call as needed.
41050 @unnumberedsubsubsec Open Flags
41051 @cindex open flags, in file-i/o protocol
41053 All values are given in hexadecimal representation.
41065 @node mode_t Values
41066 @unnumberedsubsubsec mode_t Values
41067 @cindex mode_t values, in file-i/o protocol
41069 All values are given in octal representation.
41086 @unnumberedsubsubsec Errno Values
41087 @cindex errno values, in file-i/o protocol
41089 All values are given in decimal representation.
41114 @code{EUNKNOWN} is used as a fallback error value if a host system returns
41115 any error value not in the list of supported error numbers.
41118 @unnumberedsubsubsec Lseek Flags
41119 @cindex lseek flags, in file-i/o protocol
41128 @unnumberedsubsubsec Limits
41129 @cindex limits, in file-i/o protocol
41131 All values are given in decimal representation.
41134 INT_MIN -2147483648
41136 UINT_MAX 4294967295
41137 LONG_MIN -9223372036854775808
41138 LONG_MAX 9223372036854775807
41139 ULONG_MAX 18446744073709551615
41142 @node File-I/O Examples
41143 @subsection File-I/O Examples
41144 @cindex file-i/o examples
41146 Example sequence of a write call, file descriptor 3, buffer is at target
41147 address 0x1234, 6 bytes should be written:
41150 <- @code{Fwrite,3,1234,6}
41151 @emph{request memory read from target}
41154 @emph{return "6 bytes written"}
41158 Example sequence of a read call, file descriptor 3, buffer is at target
41159 address 0x1234, 6 bytes should be read:
41162 <- @code{Fread,3,1234,6}
41163 @emph{request memory write to target}
41164 -> @code{X1234,6:XXXXXX}
41165 @emph{return "6 bytes read"}
41169 Example sequence of a read call, call fails on the host due to invalid
41170 file descriptor (@code{EBADF}):
41173 <- @code{Fread,3,1234,6}
41177 Example sequence of a read call, user presses @kbd{Ctrl-c} before syscall on
41181 <- @code{Fread,3,1234,6}
41186 Example sequence of a read call, user presses @kbd{Ctrl-c} after syscall on
41190 <- @code{Fread,3,1234,6}
41191 -> @code{X1234,6:XXXXXX}
41195 @node Library List Format
41196 @section Library List Format
41197 @cindex library list format, remote protocol
41199 On some platforms, a dynamic loader (e.g.@: @file{ld.so}) runs in the
41200 same process as your application to manage libraries. In this case,
41201 @value{GDBN} can use the loader's symbol table and normal memory
41202 operations to maintain a list of shared libraries. On other
41203 platforms, the operating system manages loaded libraries.
41204 @value{GDBN} can not retrieve the list of currently loaded libraries
41205 through memory operations, so it uses the @samp{qXfer:libraries:read}
41206 packet (@pxref{qXfer library list read}) instead. The remote stub
41207 queries the target's operating system and reports which libraries
41210 The @samp{qXfer:libraries:read} packet returns an XML document which
41211 lists loaded libraries and their offsets. Each library has an
41212 associated name and one or more segment or section base addresses,
41213 which report where the library was loaded in memory.
41215 For the common case of libraries that are fully linked binaries, the
41216 library should have a list of segments. If the target supports
41217 dynamic linking of a relocatable object file, its library XML element
41218 should instead include a list of allocated sections. The segment or
41219 section bases are start addresses, not relocation offsets; they do not
41220 depend on the library's link-time base addresses.
41222 @value{GDBN} must be linked with the Expat library to support XML
41223 library lists. @xref{Expat}.
41225 A simple memory map, with one loaded library relocated by a single
41226 offset, looks like this:
41230 <library name="/lib/libc.so.6">
41231 <segment address="0x10000000"/>
41236 Another simple memory map, with one loaded library with three
41237 allocated sections (.text, .data, .bss), looks like this:
41241 <library name="sharedlib.o">
41242 <section address="0x10000000"/>
41243 <section address="0x20000000"/>
41244 <section address="0x30000000"/>
41249 The format of a library list is described by this DTD:
41252 <!-- library-list: Root element with versioning -->
41253 <!ELEMENT library-list (library)*>
41254 <!ATTLIST library-list version CDATA #FIXED "1.0">
41255 <!ELEMENT library (segment*, section*)>
41256 <!ATTLIST library name CDATA #REQUIRED>
41257 <!ELEMENT segment EMPTY>
41258 <!ATTLIST segment address CDATA #REQUIRED>
41259 <!ELEMENT section EMPTY>
41260 <!ATTLIST section address CDATA #REQUIRED>
41263 In addition, segments and section descriptors cannot be mixed within a
41264 single library element, and you must supply at least one segment or
41265 section for each library.
41267 @node Library List Format for SVR4 Targets
41268 @section Library List Format for SVR4 Targets
41269 @cindex library list format, remote protocol
41271 On SVR4 platforms @value{GDBN} can use the symbol table of a dynamic loader
41272 (e.g.@: @file{ld.so}) and normal memory operations to maintain a list of
41273 shared libraries. Still a special library list provided by this packet is
41274 more efficient for the @value{GDBN} remote protocol.
41276 The @samp{qXfer:libraries-svr4:read} packet returns an XML document which lists
41277 loaded libraries and their SVR4 linker parameters. For each library on SVR4
41278 target, the following parameters are reported:
41282 @code{name}, the absolute file name from the @code{l_name} field of
41283 @code{struct link_map}.
41285 @code{lm} with address of @code{struct link_map} used for TLS
41286 (Thread Local Storage) access.
41288 @code{l_addr}, the displacement as read from the field @code{l_addr} of
41289 @code{struct link_map}. For prelinked libraries this is not an absolute
41290 memory address. It is a displacement of absolute memory address against
41291 address the file was prelinked to during the library load.
41293 @code{l_ld}, which is memory address of the @code{PT_DYNAMIC} segment
41296 Additionally the single @code{main-lm} attribute specifies address of
41297 @code{struct link_map} used for the main executable. This parameter is used
41298 for TLS access and its presence is optional.
41300 @value{GDBN} must be linked with the Expat library to support XML
41301 SVR4 library lists. @xref{Expat}.
41303 A simple memory map, with two loaded libraries (which do not use prelink),
41307 <library-list-svr4 version="1.0" main-lm="0xe4f8f8">
41308 <library name="/lib/ld-linux.so.2" lm="0xe4f51c" l_addr="0xe2d000"
41310 <library name="/lib/libc.so.6" lm="0xe4fbe8" l_addr="0x154000"
41312 </library-list-svr>
41315 The format of an SVR4 library list is described by this DTD:
41318 <!-- library-list-svr4: Root element with versioning -->
41319 <!ELEMENT library-list-svr4 (library)*>
41320 <!ATTLIST library-list-svr4 version CDATA #FIXED "1.0">
41321 <!ATTLIST library-list-svr4 main-lm CDATA #IMPLIED>
41322 <!ELEMENT library EMPTY>
41323 <!ATTLIST library name CDATA #REQUIRED>
41324 <!ATTLIST library lm CDATA #REQUIRED>
41325 <!ATTLIST library l_addr CDATA #REQUIRED>
41326 <!ATTLIST library l_ld CDATA #REQUIRED>
41329 @node Memory Map Format
41330 @section Memory Map Format
41331 @cindex memory map format
41333 To be able to write into flash memory, @value{GDBN} needs to obtain a
41334 memory map from the target. This section describes the format of the
41337 The memory map is obtained using the @samp{qXfer:memory-map:read}
41338 (@pxref{qXfer memory map read}) packet and is an XML document that
41339 lists memory regions.
41341 @value{GDBN} must be linked with the Expat library to support XML
41342 memory maps. @xref{Expat}.
41344 The top-level structure of the document is shown below:
41347 <?xml version="1.0"?>
41348 <!DOCTYPE memory-map
41349 PUBLIC "+//IDN gnu.org//DTD GDB Memory Map V1.0//EN"
41350 "http://sourceware.org/gdb/gdb-memory-map.dtd">
41356 Each region can be either:
41361 A region of RAM starting at @var{addr} and extending for @var{length}
41365 <memory type="ram" start="@var{addr}" length="@var{length}"/>
41370 A region of read-only memory:
41373 <memory type="rom" start="@var{addr}" length="@var{length}"/>
41378 A region of flash memory, with erasure blocks @var{blocksize}
41382 <memory type="flash" start="@var{addr}" length="@var{length}">
41383 <property name="blocksize">@var{blocksize}</property>
41389 Regions must not overlap. @value{GDBN} assumes that areas of memory not covered
41390 by the memory map are RAM, and uses the ordinary @samp{M} and @samp{X}
41391 packets to write to addresses in such ranges.
41393 The formal DTD for memory map format is given below:
41396 <!-- ................................................... -->
41397 <!-- Memory Map XML DTD ................................ -->
41398 <!-- File: memory-map.dtd .............................. -->
41399 <!-- .................................... .............. -->
41400 <!-- memory-map.dtd -->
41401 <!-- memory-map: Root element with versioning -->
41402 <!ELEMENT memory-map (memory)*>
41403 <!ATTLIST memory-map version CDATA #FIXED "1.0.0">
41404 <!ELEMENT memory (property)*>
41405 <!-- memory: Specifies a memory region,
41406 and its type, or device. -->
41407 <!ATTLIST memory type (ram|rom|flash) #REQUIRED
41408 start CDATA #REQUIRED
41409 length CDATA #REQUIRED>
41410 <!-- property: Generic attribute tag -->
41411 <!ELEMENT property (#PCDATA | property)*>
41412 <!ATTLIST property name (blocksize) #REQUIRED>
41415 @node Thread List Format
41416 @section Thread List Format
41417 @cindex thread list format
41419 To efficiently update the list of threads and their attributes,
41420 @value{GDBN} issues the @samp{qXfer:threads:read} packet
41421 (@pxref{qXfer threads read}) and obtains the XML document with
41422 the following structure:
41425 <?xml version="1.0"?>
41427 <thread id="id" core="0" name="name">
41428 ... description ...
41433 Each @samp{thread} element must have the @samp{id} attribute that
41434 identifies the thread (@pxref{thread-id syntax}). The
41435 @samp{core} attribute, if present, specifies which processor core
41436 the thread was last executing on. The @samp{name} attribute, if
41437 present, specifies the human-readable name of the thread. The content
41438 of the of @samp{thread} element is interpreted as human-readable
41439 auxiliary information. The @samp{handle} attribute, if present,
41440 is a hex encoded representation of the thread handle.
41443 @node Traceframe Info Format
41444 @section Traceframe Info Format
41445 @cindex traceframe info format
41447 To be able to know which objects in the inferior can be examined when
41448 inspecting a tracepoint hit, @value{GDBN} needs to obtain the list of
41449 memory ranges, registers and trace state variables that have been
41450 collected in a traceframe.
41452 This list is obtained using the @samp{qXfer:traceframe-info:read}
41453 (@pxref{qXfer traceframe info read}) packet and is an XML document.
41455 @value{GDBN} must be linked with the Expat library to support XML
41456 traceframe info discovery. @xref{Expat}.
41458 The top-level structure of the document is shown below:
41461 <?xml version="1.0"?>
41462 <!DOCTYPE traceframe-info
41463 PUBLIC "+//IDN gnu.org//DTD GDB Memory Map V1.0//EN"
41464 "http://sourceware.org/gdb/gdb-traceframe-info.dtd">
41470 Each traceframe block can be either:
41475 A region of collected memory starting at @var{addr} and extending for
41476 @var{length} bytes from there:
41479 <memory start="@var{addr}" length="@var{length}"/>
41483 A block indicating trace state variable numbered @var{number} has been
41487 <tvar id="@var{number}"/>
41492 The formal DTD for the traceframe info format is given below:
41495 <!ELEMENT traceframe-info (memory | tvar)* >
41496 <!ATTLIST traceframe-info version CDATA #FIXED "1.0">
41498 <!ELEMENT memory EMPTY>
41499 <!ATTLIST memory start CDATA #REQUIRED
41500 length CDATA #REQUIRED>
41502 <!ATTLIST tvar id CDATA #REQUIRED>
41505 @node Branch Trace Format
41506 @section Branch Trace Format
41507 @cindex branch trace format
41509 In order to display the branch trace of an inferior thread,
41510 @value{GDBN} needs to obtain the list of branches. This list is
41511 represented as list of sequential code blocks that are connected via
41512 branches. The code in each block has been executed sequentially.
41514 This list is obtained using the @samp{qXfer:btrace:read}
41515 (@pxref{qXfer btrace read}) packet and is an XML document.
41517 @value{GDBN} must be linked with the Expat library to support XML
41518 traceframe info discovery. @xref{Expat}.
41520 The top-level structure of the document is shown below:
41523 <?xml version="1.0"?>
41525 PUBLIC "+//IDN gnu.org//DTD GDB Branch Trace V1.0//EN"
41526 "http://sourceware.org/gdb/gdb-btrace.dtd">
41535 A block of sequentially executed instructions starting at @var{begin}
41536 and ending at @var{end}:
41539 <block begin="@var{begin}" end="@var{end}"/>
41544 The formal DTD for the branch trace format is given below:
41547 <!ELEMENT btrace (block* | pt) >
41548 <!ATTLIST btrace version CDATA #FIXED "1.0">
41550 <!ELEMENT block EMPTY>
41551 <!ATTLIST block begin CDATA #REQUIRED
41552 end CDATA #REQUIRED>
41554 <!ELEMENT pt (pt-config?, raw?)>
41556 <!ELEMENT pt-config (cpu?)>
41558 <!ELEMENT cpu EMPTY>
41559 <!ATTLIST cpu vendor CDATA #REQUIRED
41560 family CDATA #REQUIRED
41561 model CDATA #REQUIRED
41562 stepping CDATA #REQUIRED>
41564 <!ELEMENT raw (#PCDATA)>
41567 @node Branch Trace Configuration Format
41568 @section Branch Trace Configuration Format
41569 @cindex branch trace configuration format
41571 For each inferior thread, @value{GDBN} can obtain the branch trace
41572 configuration using the @samp{qXfer:btrace-conf:read}
41573 (@pxref{qXfer btrace-conf read}) packet.
41575 The configuration describes the branch trace format and configuration
41576 settings for that format. The following information is described:
41580 This thread uses the @dfn{Branch Trace Store} (@acronym{BTS}) format.
41583 The size of the @acronym{BTS} ring buffer in bytes.
41586 This thread uses the @dfn{Intel Processor Trace} (@acronym{Intel
41590 The size of the @acronym{Intel PT} ring buffer in bytes.
41594 @value{GDBN} must be linked with the Expat library to support XML
41595 branch trace configuration discovery. @xref{Expat}.
41597 The formal DTD for the branch trace configuration format is given below:
41600 <!ELEMENT btrace-conf (bts?, pt?)>
41601 <!ATTLIST btrace-conf version CDATA #FIXED "1.0">
41603 <!ELEMENT bts EMPTY>
41604 <!ATTLIST bts size CDATA #IMPLIED>
41606 <!ELEMENT pt EMPTY>
41607 <!ATTLIST pt size CDATA #IMPLIED>
41610 @include agentexpr.texi
41612 @node Target Descriptions
41613 @appendix Target Descriptions
41614 @cindex target descriptions
41616 One of the challenges of using @value{GDBN} to debug embedded systems
41617 is that there are so many minor variants of each processor
41618 architecture in use. It is common practice for vendors to start with
41619 a standard processor core --- ARM, PowerPC, or @acronym{MIPS}, for example ---
41620 and then make changes to adapt it to a particular market niche. Some
41621 architectures have hundreds of variants, available from dozens of
41622 vendors. This leads to a number of problems:
41626 With so many different customized processors, it is difficult for
41627 the @value{GDBN} maintainers to keep up with the changes.
41629 Since individual variants may have short lifetimes or limited
41630 audiences, it may not be worthwhile to carry information about every
41631 variant in the @value{GDBN} source tree.
41633 When @value{GDBN} does support the architecture of the embedded system
41634 at hand, the task of finding the correct architecture name to give the
41635 @command{set architecture} command can be error-prone.
41638 To address these problems, the @value{GDBN} remote protocol allows a
41639 target system to not only identify itself to @value{GDBN}, but to
41640 actually describe its own features. This lets @value{GDBN} support
41641 processor variants it has never seen before --- to the extent that the
41642 descriptions are accurate, and that @value{GDBN} understands them.
41644 @value{GDBN} must be linked with the Expat library to support XML
41645 target descriptions. @xref{Expat}.
41648 * Retrieving Descriptions:: How descriptions are fetched from a target.
41649 * Target Description Format:: The contents of a target description.
41650 * Predefined Target Types:: Standard types available for target
41652 * Enum Target Types:: How to define enum target types.
41653 * Standard Target Features:: Features @value{GDBN} knows about.
41656 @node Retrieving Descriptions
41657 @section Retrieving Descriptions
41659 Target descriptions can be read from the target automatically, or
41660 specified by the user manually. The default behavior is to read the
41661 description from the target. @value{GDBN} retrieves it via the remote
41662 protocol using @samp{qXfer} requests (@pxref{General Query Packets,
41663 qXfer}). The @var{annex} in the @samp{qXfer} packet will be
41664 @samp{target.xml}. The contents of the @samp{target.xml} annex are an
41665 XML document, of the form described in @ref{Target Description
41668 Alternatively, you can specify a file to read for the target description.
41669 If a file is set, the target will not be queried. The commands to
41670 specify a file are:
41673 @cindex set tdesc filename
41674 @item set tdesc filename @var{path}
41675 Read the target description from @var{path}.
41677 @cindex unset tdesc filename
41678 @item unset tdesc filename
41679 Do not read the XML target description from a file. @value{GDBN}
41680 will use the description supplied by the current target.
41682 @cindex show tdesc filename
41683 @item show tdesc filename
41684 Show the filename to read for a target description, if any.
41688 @node Target Description Format
41689 @section Target Description Format
41690 @cindex target descriptions, XML format
41692 A target description annex is an @uref{http://www.w3.org/XML/, XML}
41693 document which complies with the Document Type Definition provided in
41694 the @value{GDBN} sources in @file{gdb/features/gdb-target.dtd}. This
41695 means you can use generally available tools like @command{xmllint} to
41696 check that your feature descriptions are well-formed and valid.
41697 However, to help people unfamiliar with XML write descriptions for
41698 their targets, we also describe the grammar here.
41700 Target descriptions can identify the architecture of the remote target
41701 and (for some architectures) provide information about custom register
41702 sets. They can also identify the OS ABI of the remote target.
41703 @value{GDBN} can use this information to autoconfigure for your
41704 target, or to warn you if you connect to an unsupported target.
41706 Here is a simple target description:
41709 <target version="1.0">
41710 <architecture>i386:x86-64</architecture>
41715 This minimal description only says that the target uses
41716 the x86-64 architecture.
41718 A target description has the following overall form, with [ ] marking
41719 optional elements and @dots{} marking repeatable elements. The elements
41720 are explained further below.
41723 <?xml version="1.0"?>
41724 <!DOCTYPE target SYSTEM "gdb-target.dtd">
41725 <target version="1.0">
41726 @r{[}@var{architecture}@r{]}
41727 @r{[}@var{osabi}@r{]}
41728 @r{[}@var{compatible}@r{]}
41729 @r{[}@var{feature}@dots{}@r{]}
41734 The description is generally insensitive to whitespace and line
41735 breaks, under the usual common-sense rules. The XML version
41736 declaration and document type declaration can generally be omitted
41737 (@value{GDBN} does not require them), but specifying them may be
41738 useful for XML validation tools. The @samp{version} attribute for
41739 @samp{<target>} may also be omitted, but we recommend
41740 including it; if future versions of @value{GDBN} use an incompatible
41741 revision of @file{gdb-target.dtd}, they will detect and report
41742 the version mismatch.
41744 @subsection Inclusion
41745 @cindex target descriptions, inclusion
41748 @cindex <xi:include>
41751 It can sometimes be valuable to split a target description up into
41752 several different annexes, either for organizational purposes, or to
41753 share files between different possible target descriptions. You can
41754 divide a description into multiple files by replacing any element of
41755 the target description with an inclusion directive of the form:
41758 <xi:include href="@var{document}"/>
41762 When @value{GDBN} encounters an element of this form, it will retrieve
41763 the named XML @var{document}, and replace the inclusion directive with
41764 the contents of that document. If the current description was read
41765 using @samp{qXfer}, then so will be the included document;
41766 @var{document} will be interpreted as the name of an annex. If the
41767 current description was read from a file, @value{GDBN} will look for
41768 @var{document} as a file in the same directory where it found the
41769 original description.
41771 @subsection Architecture
41772 @cindex <architecture>
41774 An @samp{<architecture>} element has this form:
41777 <architecture>@var{arch}</architecture>
41780 @var{arch} is one of the architectures from the set accepted by
41781 @code{set architecture} (@pxref{Targets, ,Specifying a Debugging Target}).
41784 @cindex @code{<osabi>}
41786 This optional field was introduced in @value{GDBN} version 7.0.
41787 Previous versions of @value{GDBN} ignore it.
41789 An @samp{<osabi>} element has this form:
41792 <osabi>@var{abi-name}</osabi>
41795 @var{abi-name} is an OS ABI name from the same selection accepted by
41796 @w{@code{set osabi}} (@pxref{ABI, ,Configuring the Current ABI}).
41798 @subsection Compatible Architecture
41799 @cindex @code{<compatible>}
41801 This optional field was introduced in @value{GDBN} version 7.0.
41802 Previous versions of @value{GDBN} ignore it.
41804 A @samp{<compatible>} element has this form:
41807 <compatible>@var{arch}</compatible>
41810 @var{arch} is one of the architectures from the set accepted by
41811 @code{set architecture} (@pxref{Targets, ,Specifying a Debugging Target}).
41813 A @samp{<compatible>} element is used to specify that the target
41814 is able to run binaries in some other than the main target architecture
41815 given by the @samp{<architecture>} element. For example, on the
41816 Cell Broadband Engine, the main architecture is @code{powerpc:common}
41817 or @code{powerpc:common64}, but the system is able to run binaries
41818 in the @code{spu} architecture as well. The way to describe this
41819 capability with @samp{<compatible>} is as follows:
41822 <architecture>powerpc:common</architecture>
41823 <compatible>spu</compatible>
41826 @subsection Features
41829 Each @samp{<feature>} describes some logical portion of the target
41830 system. Features are currently used to describe available CPU
41831 registers and the types of their contents. A @samp{<feature>} element
41835 <feature name="@var{name}">
41836 @r{[}@var{type}@dots{}@r{]}
41842 Each feature's name should be unique within the description. The name
41843 of a feature does not matter unless @value{GDBN} has some special
41844 knowledge of the contents of that feature; if it does, the feature
41845 should have its standard name. @xref{Standard Target Features}.
41849 Any register's value is a collection of bits which @value{GDBN} must
41850 interpret. The default interpretation is a two's complement integer,
41851 but other types can be requested by name in the register description.
41852 Some predefined types are provided by @value{GDBN} (@pxref{Predefined
41853 Target Types}), and the description can define additional composite
41856 Each type element must have an @samp{id} attribute, which gives
41857 a unique (within the containing @samp{<feature>}) name to the type.
41858 Types must be defined before they are used.
41861 Some targets offer vector registers, which can be treated as arrays
41862 of scalar elements. These types are written as @samp{<vector>} elements,
41863 specifying the array element type, @var{type}, and the number of elements,
41867 <vector id="@var{id}" type="@var{type}" count="@var{count}"/>
41871 If a register's value is usefully viewed in multiple ways, define it
41872 with a union type containing the useful representations. The
41873 @samp{<union>} element contains one or more @samp{<field>} elements,
41874 each of which has a @var{name} and a @var{type}:
41877 <union id="@var{id}">
41878 <field name="@var{name}" type="@var{type}"/>
41885 If a register's value is composed from several separate values, define
41886 it with either a structure type or a flags type.
41887 A flags type may only contain bitfields.
41888 A structure type may either contain only bitfields or contain no bitfields.
41889 If the value contains only bitfields, its total size in bytes must be
41892 Non-bitfield values have a @var{name} and @var{type}.
41895 <struct id="@var{id}">
41896 <field name="@var{name}" type="@var{type}"/>
41901 Both @var{name} and @var{type} values are required.
41902 No implicit padding is added.
41904 Bitfield values have a @var{name}, @var{start}, @var{end} and @var{type}.
41907 <struct id="@var{id}" size="@var{size}">
41908 <field name="@var{name}" start="@var{start}" end="@var{end}" type="@var{type}"/>
41914 <flags id="@var{id}" size="@var{size}">
41915 <field name="@var{name}" start="@var{start}" end="@var{end}" type="@var{type}"/>
41920 The @var{name} value is required.
41921 Bitfield values may be named with the empty string, @samp{""},
41922 in which case the field is ``filler'' and its value is not printed.
41923 Not all bits need to be specified, so ``filler'' fields are optional.
41925 The @var{start} and @var{end} values are required, and @var{type}
41927 The field's @var{start} must be less than or equal to its @var{end},
41928 and zero represents the least significant bit.
41930 The default value of @var{type} is @code{bool} for single bit fields,
41931 and an unsigned integer otherwise.
41933 Which to choose? Structures or flags?
41935 Registers defined with @samp{flags} have these advantages over
41936 defining them with @samp{struct}:
41940 Arithmetic may be performed on them as if they were integers.
41942 They are printed in a more readable fashion.
41945 Registers defined with @samp{struct} have one advantage over
41946 defining them with @samp{flags}:
41950 One can fetch individual fields like in @samp{C}.
41953 (gdb) print $my_struct_reg.field3
41959 @subsection Registers
41962 Each register is represented as an element with this form:
41965 <reg name="@var{name}"
41966 bitsize="@var{size}"
41967 @r{[}regnum="@var{num}"@r{]}
41968 @r{[}save-restore="@var{save-restore}"@r{]}
41969 @r{[}type="@var{type}"@r{]}
41970 @r{[}group="@var{group}"@r{]}/>
41974 The components are as follows:
41979 The register's name; it must be unique within the target description.
41982 The register's size, in bits.
41985 The register's number. If omitted, a register's number is one greater
41986 than that of the previous register (either in the current feature or in
41987 a preceding feature); the first register in the target description
41988 defaults to zero. This register number is used to read or write
41989 the register; e.g.@: it is used in the remote @code{p} and @code{P}
41990 packets, and registers appear in the @code{g} and @code{G} packets
41991 in order of increasing register number.
41994 Whether the register should be preserved across inferior function
41995 calls; this must be either @code{yes} or @code{no}. The default is
41996 @code{yes}, which is appropriate for most registers except for
41997 some system control registers; this is not related to the target's
42001 The type of the register. It may be a predefined type, a type
42002 defined in the current feature, or one of the special types @code{int}
42003 and @code{float}. @code{int} is an integer type of the correct size
42004 for @var{bitsize}, and @code{float} is a floating point type (in the
42005 architecture's normal floating point format) of the correct size for
42006 @var{bitsize}. The default is @code{int}.
42009 The register group to which this register belongs. It can be one of the
42010 standard register groups @code{general}, @code{float}, @code{vector} or an
42011 arbitrary string. Group names should be limited to alphanumeric characters.
42012 If a group name is made up of multiple words the words may be separated by
42013 hyphens; e.g.@: @code{special-group} or @code{ultra-special-group}. If no
42014 @var{group} is specified, @value{GDBN} will not display the register in
42015 @code{info registers}.
42019 @node Predefined Target Types
42020 @section Predefined Target Types
42021 @cindex target descriptions, predefined types
42023 Type definitions in the self-description can build up composite types
42024 from basic building blocks, but can not define fundamental types. Instead,
42025 standard identifiers are provided by @value{GDBN} for the fundamental
42026 types. The currently supported types are:
42031 Boolean type, occupying a single bit.
42038 Signed integer types holding the specified number of bits.
42045 Unsigned integer types holding the specified number of bits.
42049 Pointers to unspecified code and data. The program counter and
42050 any dedicated return address register may be marked as code
42051 pointers; printing a code pointer converts it into a symbolic
42052 address. The stack pointer and any dedicated address registers
42053 may be marked as data pointers.
42056 Single precision IEEE floating point.
42059 Double precision IEEE floating point.
42062 The 12-byte extended precision format used by ARM FPA registers.
42065 The 10-byte extended precision format used by x87 registers.
42068 32bit @sc{eflags} register used by x86.
42071 32bit @sc{mxcsr} register used by x86.
42075 @node Enum Target Types
42076 @section Enum Target Types
42077 @cindex target descriptions, enum types
42079 Enum target types are useful in @samp{struct} and @samp{flags}
42080 register descriptions. @xref{Target Description Format}.
42082 Enum types have a name, size and a list of name/value pairs.
42085 <enum id="@var{id}" size="@var{size}">
42086 <evalue name="@var{name}" value="@var{value}"/>
42091 Enums must be defined before they are used.
42094 <enum id="levels_type" size="4">
42095 <evalue name="low" value="0"/>
42096 <evalue name="high" value="1"/>
42098 <flags id="flags_type" size="4">
42099 <field name="X" start="0"/>
42100 <field name="LEVEL" start="1" end="1" type="levels_type"/>
42102 <reg name="flags" bitsize="32" type="flags_type"/>
42105 Given that description, a value of 3 for the @samp{flags} register
42106 would be printed as:
42109 (gdb) info register flags
42110 flags 0x3 [ X LEVEL=high ]
42113 @node Standard Target Features
42114 @section Standard Target Features
42115 @cindex target descriptions, standard features
42117 A target description must contain either no registers or all the
42118 target's registers. If the description contains no registers, then
42119 @value{GDBN} will assume a default register layout, selected based on
42120 the architecture. If the description contains any registers, the
42121 default layout will not be used; the standard registers must be
42122 described in the target description, in such a way that @value{GDBN}
42123 can recognize them.
42125 This is accomplished by giving specific names to feature elements
42126 which contain standard registers. @value{GDBN} will look for features
42127 with those names and verify that they contain the expected registers;
42128 if any known feature is missing required registers, or if any required
42129 feature is missing, @value{GDBN} will reject the target
42130 description. You can add additional registers to any of the
42131 standard features --- @value{GDBN} will display them just as if
42132 they were added to an unrecognized feature.
42134 This section lists the known features and their expected contents.
42135 Sample XML documents for these features are included in the
42136 @value{GDBN} source tree, in the directory @file{gdb/features}.
42138 Names recognized by @value{GDBN} should include the name of the
42139 company or organization which selected the name, and the overall
42140 architecture to which the feature applies; so e.g.@: the feature
42141 containing ARM core registers is named @samp{org.gnu.gdb.arm.core}.
42143 The names of registers are not case sensitive for the purpose
42144 of recognizing standard features, but @value{GDBN} will only display
42145 registers using the capitalization used in the description.
42148 * AArch64 Features::
42152 * MicroBlaze Features::
42156 * Nios II Features::
42157 * OpenRISC 1000 Features::
42158 * PowerPC Features::
42159 * S/390 and System z Features::
42165 @node AArch64 Features
42166 @subsection AArch64 Features
42167 @cindex target descriptions, AArch64 features
42169 The @samp{org.gnu.gdb.aarch64.core} feature is required for AArch64
42170 targets. It should contain registers @samp{x0} through @samp{x30},
42171 @samp{sp}, @samp{pc}, and @samp{cpsr}.
42173 The @samp{org.gnu.gdb.aarch64.fpu} feature is optional. If present,
42174 it should contain registers @samp{v0} through @samp{v31}, @samp{fpsr},
42177 The @samp{org.gnu.gdb.aarch64.sve} feature is optional. If present,
42178 it should contain registers @samp{z0} through @samp{z31}, @samp{p0}
42179 through @samp{p15}, @samp{ffr} and @samp{vg}.
42182 @subsection ARC Features
42183 @cindex target descriptions, ARC Features
42185 ARC processors are highly configurable, so even core registers and their number
42186 are not completely predetermined. In addition flags and PC registers which are
42187 important to @value{GDBN} are not ``core'' registers in ARC. It is required
42188 that one of the core registers features is present.
42189 @samp{org.gnu.gdb.arc.aux-minimal} feature is mandatory.
42191 The @samp{org.gnu.gdb.arc.core.v2} feature is required for ARC EM and ARC HS
42192 targets with a normal register file. It should contain registers @samp{r0}
42193 through @samp{r25}, @samp{gp}, @samp{fp}, @samp{sp}, @samp{r30}, @samp{blink},
42194 @samp{lp_count} and @samp{pcl}. This feature may contain register @samp{ilink}
42195 and any of extension core registers @samp{r32} through @samp{r59/acch}.
42196 @samp{ilink} and extension core registers are not available to read/write, when
42197 debugging GNU/Linux applications, thus @samp{ilink} is made optional.
42199 The @samp{org.gnu.gdb.arc.core-reduced.v2} feature is required for ARC EM and
42200 ARC HS targets with a reduced register file. It should contain registers
42201 @samp{r0} through @samp{r3}, @samp{r10} through @samp{r15}, @samp{gp},
42202 @samp{fp}, @samp{sp}, @samp{r30}, @samp{blink}, @samp{lp_count} and @samp{pcl}.
42203 This feature may contain register @samp{ilink} and any of extension core
42204 registers @samp{r32} through @samp{r59/acch}.
42206 The @samp{org.gnu.gdb.arc.core.arcompact} feature is required for ARCompact
42207 targets with a normal register file. It should contain registers @samp{r0}
42208 through @samp{r25}, @samp{gp}, @samp{fp}, @samp{sp}, @samp{r30}, @samp{blink},
42209 @samp{lp_count} and @samp{pcl}. This feature may contain registers
42210 @samp{ilink1}, @samp{ilink2} and any of extension core registers @samp{r32}
42211 through @samp{r59/acch}. @samp{ilink1} and @samp{ilink2} and extension core
42212 registers are not available when debugging GNU/Linux applications. The only
42213 difference with @samp{org.gnu.gdb.arc.core.v2} feature is in the names of
42214 @samp{ilink1} and @samp{ilink2} registers and that @samp{r30} is mandatory in
42215 ARC v2, but @samp{ilink2} is optional on ARCompact.
42217 The @samp{org.gnu.gdb.arc.aux-minimal} feature is required for all ARC
42218 targets. It should contain registers @samp{pc} and @samp{status32}.
42221 @subsection ARM Features
42222 @cindex target descriptions, ARM features
42224 The @samp{org.gnu.gdb.arm.core} feature is required for non-M-profile
42226 It should contain registers @samp{r0} through @samp{r13}, @samp{sp},
42227 @samp{lr}, @samp{pc}, and @samp{cpsr}.
42229 For M-profile targets (e.g. Cortex-M3), the @samp{org.gnu.gdb.arm.core}
42230 feature is replaced by @samp{org.gnu.gdb.arm.m-profile}. It should contain
42231 registers @samp{r0} through @samp{r13}, @samp{sp}, @samp{lr}, @samp{pc},
42234 The @samp{org.gnu.gdb.arm.fpa} feature is optional. If present, it
42235 should contain registers @samp{f0} through @samp{f7} and @samp{fps}.
42237 The @samp{org.gnu.gdb.xscale.iwmmxt} feature is optional. If present,
42238 it should contain at least registers @samp{wR0} through @samp{wR15} and
42239 @samp{wCGR0} through @samp{wCGR3}. The @samp{wCID}, @samp{wCon},
42240 @samp{wCSSF}, and @samp{wCASF} registers are optional.
42242 The @samp{org.gnu.gdb.arm.vfp} feature is optional. If present, it
42243 should contain at least registers @samp{d0} through @samp{d15}. If
42244 they are present, @samp{d16} through @samp{d31} should also be included.
42245 @value{GDBN} will synthesize the single-precision registers from
42246 halves of the double-precision registers.
42248 The @samp{org.gnu.gdb.arm.neon} feature is optional. It does not
42249 need to contain registers; it instructs @value{GDBN} to display the
42250 VFP double-precision registers as vectors and to synthesize the
42251 quad-precision registers from pairs of double-precision registers.
42252 If this feature is present, @samp{org.gnu.gdb.arm.vfp} must also
42253 be present and include 32 double-precision registers.
42255 @node i386 Features
42256 @subsection i386 Features
42257 @cindex target descriptions, i386 features
42259 The @samp{org.gnu.gdb.i386.core} feature is required for i386/amd64
42260 targets. It should describe the following registers:
42264 @samp{eax} through @samp{edi} plus @samp{eip} for i386
42266 @samp{rax} through @samp{r15} plus @samp{rip} for amd64
42268 @samp{eflags}, @samp{cs}, @samp{ss}, @samp{ds}, @samp{es},
42269 @samp{fs}, @samp{gs}
42271 @samp{st0} through @samp{st7}
42273 @samp{fctrl}, @samp{fstat}, @samp{ftag}, @samp{fiseg}, @samp{fioff},
42274 @samp{foseg}, @samp{fooff} and @samp{fop}
42277 The register sets may be different, depending on the target.
42279 The @samp{org.gnu.gdb.i386.sse} feature is optional. It should
42280 describe registers:
42284 @samp{xmm0} through @samp{xmm7} for i386
42286 @samp{xmm0} through @samp{xmm15} for amd64
42291 The @samp{org.gnu.gdb.i386.avx} feature is optional and requires the
42292 @samp{org.gnu.gdb.i386.sse} feature. It should
42293 describe the upper 128 bits of @sc{ymm} registers:
42297 @samp{ymm0h} through @samp{ymm7h} for i386
42299 @samp{ymm0h} through @samp{ymm15h} for amd64
42302 The @samp{org.gnu.gdb.i386.mpx} is an optional feature representing Intel
42303 Memory Protection Extension (MPX). It should describe the following registers:
42307 @samp{bnd0raw} through @samp{bnd3raw} for i386 and amd64.
42309 @samp{bndcfgu} and @samp{bndstatus} for i386 and amd64.
42312 The @samp{org.gnu.gdb.i386.linux} feature is optional. It should
42313 describe a single register, @samp{orig_eax}.
42315 The @samp{org.gnu.gdb.i386.segments} feature is optional. It should
42316 describe two system registers: @samp{fs_base} and @samp{gs_base}.
42318 The @samp{org.gnu.gdb.i386.avx512} feature is optional and requires the
42319 @samp{org.gnu.gdb.i386.avx} feature. It should
42320 describe additional @sc{xmm} registers:
42324 @samp{xmm16h} through @samp{xmm31h}, only valid for amd64.
42327 It should describe the upper 128 bits of additional @sc{ymm} registers:
42331 @samp{ymm16h} through @samp{ymm31h}, only valid for amd64.
42335 describe the upper 256 bits of @sc{zmm} registers:
42339 @samp{zmm0h} through @samp{zmm7h} for i386.
42341 @samp{zmm0h} through @samp{zmm15h} for amd64.
42345 describe the additional @sc{zmm} registers:
42349 @samp{zmm16h} through @samp{zmm31h}, only valid for amd64.
42352 The @samp{org.gnu.gdb.i386.pkeys} feature is optional. It should
42353 describe a single register, @samp{pkru}. It is a 32-bit register
42354 valid for i386 and amd64.
42356 @node MicroBlaze Features
42357 @subsection MicroBlaze Features
42358 @cindex target descriptions, MicroBlaze features
42360 The @samp{org.gnu.gdb.microblaze.core} feature is required for MicroBlaze
42361 targets. It should contain registers @samp{r0} through @samp{r31},
42362 @samp{rpc}, @samp{rmsr}, @samp{rear}, @samp{resr}, @samp{rfsr}, @samp{rbtr},
42363 @samp{rpvr}, @samp{rpvr1} through @samp{rpvr11}, @samp{redr}, @samp{rpid},
42364 @samp{rzpr}, @samp{rtlbx}, @samp{rtlbsx}, @samp{rtlblo}, and @samp{rtlbhi}.
42366 The @samp{org.gnu.gdb.microblaze.stack-protect} feature is optional.
42367 If present, it should contain registers @samp{rshr} and @samp{rslr}
42369 @node MIPS Features
42370 @subsection @acronym{MIPS} Features
42371 @cindex target descriptions, @acronym{MIPS} features
42373 The @samp{org.gnu.gdb.mips.cpu} feature is required for @acronym{MIPS} targets.
42374 It should contain registers @samp{r0} through @samp{r31}, @samp{lo},
42375 @samp{hi}, and @samp{pc}. They may be 32-bit or 64-bit depending
42378 The @samp{org.gnu.gdb.mips.cp0} feature is also required. It should
42379 contain at least the @samp{status}, @samp{badvaddr}, and @samp{cause}
42380 registers. They may be 32-bit or 64-bit depending on the target.
42382 The @samp{org.gnu.gdb.mips.fpu} feature is currently required, though
42383 it may be optional in a future version of @value{GDBN}. It should
42384 contain registers @samp{f0} through @samp{f31}, @samp{fcsr}, and
42385 @samp{fir}. They may be 32-bit or 64-bit depending on the target.
42387 The @samp{org.gnu.gdb.mips.dsp} feature is optional. It should
42388 contain registers @samp{hi1} through @samp{hi3}, @samp{lo1} through
42389 @samp{lo3}, and @samp{dspctl}. The @samp{dspctl} register should
42390 be 32-bit and the rest may be 32-bit or 64-bit depending on the target.
42392 The @samp{org.gnu.gdb.mips.linux} feature is optional. It should
42393 contain a single register, @samp{restart}, which is used by the
42394 Linux kernel to control restartable syscalls.
42396 @node M68K Features
42397 @subsection M68K Features
42398 @cindex target descriptions, M68K features
42401 @item @samp{org.gnu.gdb.m68k.core}
42402 @itemx @samp{org.gnu.gdb.coldfire.core}
42403 @itemx @samp{org.gnu.gdb.fido.core}
42404 One of those features must be always present.
42405 The feature that is present determines which flavor of m68k is
42406 used. The feature that is present should contain registers
42407 @samp{d0} through @samp{d7}, @samp{a0} through @samp{a5}, @samp{fp},
42408 @samp{sp}, @samp{ps} and @samp{pc}.
42410 @item @samp{org.gnu.gdb.coldfire.fp}
42411 This feature is optional. If present, it should contain registers
42412 @samp{fp0} through @samp{fp7}, @samp{fpcontrol}, @samp{fpstatus} and
42416 @node NDS32 Features
42417 @subsection NDS32 Features
42418 @cindex target descriptions, NDS32 features
42420 The @samp{org.gnu.gdb.nds32.core} feature is required for NDS32
42421 targets. It should contain at least registers @samp{r0} through
42422 @samp{r10}, @samp{r15}, @samp{fp}, @samp{gp}, @samp{lp}, @samp{sp},
42425 The @samp{org.gnu.gdb.nds32.fpu} feature is optional. If present,
42426 it should contain 64-bit double-precision floating-point registers
42427 @samp{fd0} through @emph{fdN}, which should be @samp{fd3}, @samp{fd7},
42428 @samp{fd15}, or @samp{fd31} based on the FPU configuration implemented.
42430 @emph{Note:} The first sixteen 64-bit double-precision floating-point
42431 registers are overlapped with the thirty-two 32-bit single-precision
42432 floating-point registers. The 32-bit single-precision registers, if
42433 not being listed explicitly, will be synthesized from halves of the
42434 overlapping 64-bit double-precision registers. Listing 32-bit
42435 single-precision registers explicitly is deprecated, and the
42436 support to it could be totally removed some day.
42438 @node Nios II Features
42439 @subsection Nios II Features
42440 @cindex target descriptions, Nios II features
42442 The @samp{org.gnu.gdb.nios2.cpu} feature is required for Nios II
42443 targets. It should contain the 32 core registers (@samp{zero},
42444 @samp{at}, @samp{r2} through @samp{r23}, @samp{et} through @samp{ra}),
42445 @samp{pc}, and the 16 control registers (@samp{status} through
42448 @node OpenRISC 1000 Features
42449 @subsection Openrisc 1000 Features
42450 @cindex target descriptions, OpenRISC 1000 features
42452 The @samp{org.gnu.gdb.or1k.group0} feature is required for OpenRISC 1000
42453 targets. It should contain the 32 general purpose registers (@samp{r0}
42454 through @samp{r31}), @samp{ppc}, @samp{npc} and @samp{sr}.
42456 @node PowerPC Features
42457 @subsection PowerPC Features
42458 @cindex target descriptions, PowerPC features
42460 The @samp{org.gnu.gdb.power.core} feature is required for PowerPC
42461 targets. It should contain registers @samp{r0} through @samp{r31},
42462 @samp{pc}, @samp{msr}, @samp{cr}, @samp{lr}, @samp{ctr}, and
42463 @samp{xer}. They may be 32-bit or 64-bit depending on the target.
42465 The @samp{org.gnu.gdb.power.fpu} feature is optional. It should
42466 contain registers @samp{f0} through @samp{f31} and @samp{fpscr}.
42468 The @samp{org.gnu.gdb.power.altivec} feature is optional. It should
42469 contain registers @samp{vr0} through @samp{vr31}, @samp{vscr},
42472 The @samp{org.gnu.gdb.power.vsx} feature is optional. It should
42473 contain registers @samp{vs0h} through @samp{vs31h}. @value{GDBN}
42474 will combine these registers with the floating point registers
42475 (@samp{f0} through @samp{f31}) and the altivec registers (@samp{vr0}
42476 through @samp{vr31}) to present the 128-bit wide registers @samp{vs0}
42477 through @samp{vs63}, the set of vector registers for POWER7.
42479 The @samp{org.gnu.gdb.power.spe} feature is optional. It should
42480 contain registers @samp{ev0h} through @samp{ev31h}, @samp{acc}, and
42481 @samp{spefscr}. SPE targets should provide 32-bit registers in
42482 @samp{org.gnu.gdb.power.core} and provide the upper halves in
42483 @samp{ev0h} through @samp{ev31h}. @value{GDBN} will combine
42484 these to present registers @samp{ev0} through @samp{ev31} to the
42487 @node S/390 and System z Features
42488 @subsection S/390 and System z Features
42489 @cindex target descriptions, S/390 features
42490 @cindex target descriptions, System z features
42492 The @samp{org.gnu.gdb.s390.core} feature is required for S/390 and
42493 System z targets. It should contain the PSW and the 16 general
42494 registers. In particular, System z targets should provide the 64-bit
42495 registers @samp{pswm}, @samp{pswa}, and @samp{r0} through @samp{r15}.
42496 S/390 targets should provide the 32-bit versions of these registers.
42497 A System z target that runs in 31-bit addressing mode should provide
42498 32-bit versions of @samp{pswm} and @samp{pswa}, as well as the general
42499 register's upper halves @samp{r0h} through @samp{r15h}, and their
42500 lower halves @samp{r0l} through @samp{r15l}.
42502 The @samp{org.gnu.gdb.s390.fpr} feature is required. It should
42503 contain the 64-bit registers @samp{f0} through @samp{f15}, and
42506 The @samp{org.gnu.gdb.s390.acr} feature is required. It should
42507 contain the 32-bit registers @samp{acr0} through @samp{acr15}.
42509 The @samp{org.gnu.gdb.s390.linux} feature is optional. It should
42510 contain the register @samp{orig_r2}, which is 64-bit wide on System z
42511 targets and 32-bit otherwise. In addition, the feature may contain
42512 the @samp{last_break} register, whose width depends on the addressing
42513 mode, as well as the @samp{system_call} register, which is always
42516 The @samp{org.gnu.gdb.s390.tdb} feature is optional. It should
42517 contain the 64-bit registers @samp{tdb0}, @samp{tac}, @samp{tct},
42518 @samp{atia}, and @samp{tr0} through @samp{tr15}.
42520 The @samp{org.gnu.gdb.s390.vx} feature is optional. It should contain
42521 64-bit wide registers @samp{v0l} through @samp{v15l}, which will be
42522 combined by @value{GDBN} with the floating point registers @samp{f0}
42523 through @samp{f15} to present the 128-bit wide vector registers
42524 @samp{v0} through @samp{v15}. In addition, this feature should
42525 contain the 128-bit wide vector registers @samp{v16} through
42528 The @samp{org.gnu.gdb.s390.gs} feature is optional. It should contain
42529 the 64-bit wide guarded-storage-control registers @samp{gsd},
42530 @samp{gssm}, and @samp{gsepla}.
42532 The @samp{org.gnu.gdb.s390.gsbc} feature is optional. It should contain
42533 the 64-bit wide guarded-storage broadcast control registers
42534 @samp{bc_gsd}, @samp{bc_gssm}, and @samp{bc_gsepla}.
42536 @node Sparc Features
42537 @subsection Sparc Features
42538 @cindex target descriptions, sparc32 features
42539 @cindex target descriptions, sparc64 features
42540 The @samp{org.gnu.gdb.sparc.cpu} feature is required for sparc32/sparc64
42541 targets. It should describe the following registers:
42545 @samp{g0} through @samp{g7}
42547 @samp{o0} through @samp{o7}
42549 @samp{l0} through @samp{l7}
42551 @samp{i0} through @samp{i7}
42554 They may be 32-bit or 64-bit depending on the target.
42556 Also the @samp{org.gnu.gdb.sparc.fpu} feature is required for sparc32/sparc64
42557 targets. It should describe the following registers:
42561 @samp{f0} through @samp{f31}
42563 @samp{f32} through @samp{f62} for sparc64
42566 The @samp{org.gnu.gdb.sparc.cp0} feature is required for sparc32/sparc64
42567 targets. It should describe the following registers:
42571 @samp{y}, @samp{psr}, @samp{wim}, @samp{tbr}, @samp{pc}, @samp{npc},
42572 @samp{fsr}, and @samp{csr} for sparc32
42574 @samp{pc}, @samp{npc}, @samp{state}, @samp{fsr}, @samp{fprs}, and @samp{y}
42578 @node TIC6x Features
42579 @subsection TMS320C6x Features
42580 @cindex target descriptions, TIC6x features
42581 @cindex target descriptions, TMS320C6x features
42582 The @samp{org.gnu.gdb.tic6x.core} feature is required for TMS320C6x
42583 targets. It should contain registers @samp{A0} through @samp{A15},
42584 registers @samp{B0} through @samp{B15}, @samp{CSR} and @samp{PC}.
42586 The @samp{org.gnu.gdb.tic6x.gp} feature is optional. It should
42587 contain registers @samp{A16} through @samp{A31} and @samp{B16}
42588 through @samp{B31}.
42590 The @samp{org.gnu.gdb.tic6x.c6xp} feature is optional. It should
42591 contain registers @samp{TSR}, @samp{ILC} and @samp{RILC}.
42593 @node Operating System Information
42594 @appendix Operating System Information
42595 @cindex operating system information
42601 Users of @value{GDBN} often wish to obtain information about the state of
42602 the operating system running on the target---for example the list of
42603 processes, or the list of open files. This section describes the
42604 mechanism that makes it possible. This mechanism is similar to the
42605 target features mechanism (@pxref{Target Descriptions}), but focuses
42606 on a different aspect of target.
42608 Operating system information is retrived from the target via the
42609 remote protocol, using @samp{qXfer} requests (@pxref{qXfer osdata
42610 read}). The object name in the request should be @samp{osdata}, and
42611 the @var{annex} identifies the data to be fetched.
42614 @appendixsection Process list
42615 @cindex operating system information, process list
42617 When requesting the process list, the @var{annex} field in the
42618 @samp{qXfer} request should be @samp{processes}. The returned data is
42619 an XML document. The formal syntax of this document is defined in
42620 @file{gdb/features/osdata.dtd}.
42622 An example document is:
42625 <?xml version="1.0"?>
42626 <!DOCTYPE target SYSTEM "osdata.dtd">
42627 <osdata type="processes">
42629 <column name="pid">1</column>
42630 <column name="user">root</column>
42631 <column name="command">/sbin/init</column>
42632 <column name="cores">1,2,3</column>
42637 Each item should include a column whose name is @samp{pid}. The value
42638 of that column should identify the process on the target. The
42639 @samp{user} and @samp{command} columns are optional, and will be
42640 displayed by @value{GDBN}. The @samp{cores} column, if present,
42641 should contain a comma-separated list of cores that this process
42642 is running on. Target may provide additional columns,
42643 which @value{GDBN} currently ignores.
42645 @node Trace File Format
42646 @appendix Trace File Format
42647 @cindex trace file format
42649 The trace file comes in three parts: a header, a textual description
42650 section, and a trace frame section with binary data.
42652 The header has the form @code{\x7fTRACE0\n}. The first byte is
42653 @code{0x7f} so as to indicate that the file contains binary data,
42654 while the @code{0} is a version number that may have different values
42657 The description section consists of multiple lines of @sc{ascii} text
42658 separated by newline characters (@code{0xa}). The lines may include a
42659 variety of optional descriptive or context-setting information, such
42660 as tracepoint definitions or register set size. @value{GDBN} will
42661 ignore any line that it does not recognize. An empty line marks the end
42666 Specifies the size of a register block in bytes. This is equal to the
42667 size of a @code{g} packet payload in the remote protocol. @var{size}
42668 is an ascii decimal number. There should be only one such line in
42669 a single trace file.
42671 @item status @var{status}
42672 Trace status. @var{status} has the same format as a @code{qTStatus}
42673 remote packet reply. There should be only one such line in a single trace
42676 @item tp @var{payload}
42677 Tracepoint definition. The @var{payload} has the same format as
42678 @code{qTfP}/@code{qTsP} remote packet reply payload. A single tracepoint
42679 may take multiple lines of definition, corresponding to the multiple
42682 @item tsv @var{payload}
42683 Trace state variable definition. The @var{payload} has the same format as
42684 @code{qTfV}/@code{qTsV} remote packet reply payload. A single variable
42685 may take multiple lines of definition, corresponding to the multiple
42688 @item tdesc @var{payload}
42689 Target description in XML format. The @var{payload} is a single line of
42690 the XML file. All such lines should be concatenated together to get
42691 the original XML file. This file is in the same format as @code{qXfer}
42692 @code{features} payload, and corresponds to the main @code{target.xml}
42693 file. Includes are not allowed.
42697 The trace frame section consists of a number of consecutive frames.
42698 Each frame begins with a two-byte tracepoint number, followed by a
42699 four-byte size giving the amount of data in the frame. The data in
42700 the frame consists of a number of blocks, each introduced by a
42701 character indicating its type (at least register, memory, and trace
42702 state variable). The data in this section is raw binary, not a
42703 hexadecimal or other encoding; its endianness matches the target's
42706 @c FIXME bi-arch may require endianness/arch info in description section
42709 @item R @var{bytes}
42710 Register block. The number and ordering of bytes matches that of a
42711 @code{g} packet in the remote protocol. Note that these are the
42712 actual bytes, in target order, not a hexadecimal encoding.
42714 @item M @var{address} @var{length} @var{bytes}...
42715 Memory block. This is a contiguous block of memory, at the 8-byte
42716 address @var{address}, with a 2-byte length @var{length}, followed by
42717 @var{length} bytes.
42719 @item V @var{number} @var{value}
42720 Trace state variable block. This records the 8-byte signed value
42721 @var{value} of trace state variable numbered @var{number}.
42725 Future enhancements of the trace file format may include additional types
42728 @node Index Section Format
42729 @appendix @code{.gdb_index} section format
42730 @cindex .gdb_index section format
42731 @cindex index section format
42733 This section documents the index section that is created by @code{save
42734 gdb-index} (@pxref{Index Files}). The index section is
42735 DWARF-specific; some knowledge of DWARF is assumed in this
42738 The mapped index file format is designed to be directly
42739 @code{mmap}able on any architecture. In most cases, a datum is
42740 represented using a little-endian 32-bit integer value, called an
42741 @code{offset_type}. Big endian machines must byte-swap the values
42742 before using them. Exceptions to this rule are noted. The data is
42743 laid out such that alignment is always respected.
42745 A mapped index consists of several areas, laid out in order.
42749 The file header. This is a sequence of values, of @code{offset_type}
42750 unless otherwise noted:
42754 The version number, currently 8. Versions 1, 2 and 3 are obsolete.
42755 Version 4 uses a different hashing function from versions 5 and 6.
42756 Version 6 includes symbols for inlined functions, whereas versions 4
42757 and 5 do not. Version 7 adds attributes to the CU indices in the
42758 symbol table. Version 8 specifies that symbols from DWARF type units
42759 (@samp{DW_TAG_type_unit}) refer to the type unit's symbol table and not the
42760 compilation unit (@samp{DW_TAG_comp_unit}) using the type.
42762 @value{GDBN} will only read version 4, 5, or 6 indices
42763 by specifying @code{set use-deprecated-index-sections on}.
42764 GDB has a workaround for potentially broken version 7 indices so it is
42765 currently not flagged as deprecated.
42768 The offset, from the start of the file, of the CU list.
42771 The offset, from the start of the file, of the types CU list. Note
42772 that this area can be empty, in which case this offset will be equal
42773 to the next offset.
42776 The offset, from the start of the file, of the address area.
42779 The offset, from the start of the file, of the symbol table.
42782 The offset, from the start of the file, of the constant pool.
42786 The CU list. This is a sequence of pairs of 64-bit little-endian
42787 values, sorted by the CU offset. The first element in each pair is
42788 the offset of a CU in the @code{.debug_info} section. The second
42789 element in each pair is the length of that CU. References to a CU
42790 elsewhere in the map are done using a CU index, which is just the
42791 0-based index into this table. Note that if there are type CUs, then
42792 conceptually CUs and type CUs form a single list for the purposes of
42796 The types CU list. This is a sequence of triplets of 64-bit
42797 little-endian values. In a triplet, the first value is the CU offset,
42798 the second value is the type offset in the CU, and the third value is
42799 the type signature. The types CU list is not sorted.
42802 The address area. The address area consists of a sequence of address
42803 entries. Each address entry has three elements:
42807 The low address. This is a 64-bit little-endian value.
42810 The high address. This is a 64-bit little-endian value. Like
42811 @code{DW_AT_high_pc}, the value is one byte beyond the end.
42814 The CU index. This is an @code{offset_type} value.
42818 The symbol table. This is an open-addressed hash table. The size of
42819 the hash table is always a power of 2.
42821 Each slot in the hash table consists of a pair of @code{offset_type}
42822 values. The first value is the offset of the symbol's name in the
42823 constant pool. The second value is the offset of the CU vector in the
42826 If both values are 0, then this slot in the hash table is empty. This
42827 is ok because while 0 is a valid constant pool index, it cannot be a
42828 valid index for both a string and a CU vector.
42830 The hash value for a table entry is computed by applying an
42831 iterative hash function to the symbol's name. Starting with an
42832 initial value of @code{r = 0}, each (unsigned) character @samp{c} in
42833 the string is incorporated into the hash using the formula depending on the
42838 The formula is @code{r = r * 67 + c - 113}.
42840 @item Versions 5 to 7
42841 The formula is @code{r = r * 67 + tolower (c) - 113}.
42844 The terminating @samp{\0} is not incorporated into the hash.
42846 The step size used in the hash table is computed via
42847 @code{((hash * 17) & (size - 1)) | 1}, where @samp{hash} is the hash
42848 value, and @samp{size} is the size of the hash table. The step size
42849 is used to find the next candidate slot when handling a hash
42852 The names of C@t{++} symbols in the hash table are canonicalized. We
42853 don't currently have a simple description of the canonicalization
42854 algorithm; if you intend to create new index sections, you must read
42858 The constant pool. This is simply a bunch of bytes. It is organized
42859 so that alignment is correct: CU vectors are stored first, followed by
42862 A CU vector in the constant pool is a sequence of @code{offset_type}
42863 values. The first value is the number of CU indices in the vector.
42864 Each subsequent value is the index and symbol attributes of a CU in
42865 the CU list. This element in the hash table is used to indicate which
42866 CUs define the symbol and how the symbol is used.
42867 See below for the format of each CU index+attributes entry.
42869 A string in the constant pool is zero-terminated.
42872 Attributes were added to CU index values in @code{.gdb_index} version 7.
42873 If a symbol has multiple uses within a CU then there is one
42874 CU index+attributes value for each use.
42876 The format of each CU index+attributes entry is as follows
42882 This is the index of the CU in the CU list.
42884 These bits are reserved for future purposes and must be zero.
42886 The kind of the symbol in the CU.
42890 This value is reserved and should not be used.
42891 By reserving zero the full @code{offset_type} value is backwards compatible
42892 with previous versions of the index.
42894 The symbol is a type.
42896 The symbol is a variable or an enum value.
42898 The symbol is a function.
42900 Any other kind of symbol.
42902 These values are reserved.
42906 This bit is zero if the value is global and one if it is static.
42908 The determination of whether a symbol is global or static is complicated.
42909 The authorative reference is the file @file{dwarf2read.c} in
42910 @value{GDBN} sources.
42914 This pseudo-code describes the computation of a symbol's kind and
42915 global/static attributes in the index.
42918 is_external = get_attribute (die, DW_AT_external);
42919 language = get_attribute (cu_die, DW_AT_language);
42922 case DW_TAG_typedef:
42923 case DW_TAG_base_type:
42924 case DW_TAG_subrange_type:
42928 case DW_TAG_enumerator:
42930 is_static = language != CPLUS;
42932 case DW_TAG_subprogram:
42934 is_static = ! (is_external || language == ADA);
42936 case DW_TAG_constant:
42938 is_static = ! is_external;
42940 case DW_TAG_variable:
42942 is_static = ! is_external;
42944 case DW_TAG_namespace:
42948 case DW_TAG_class_type:
42949 case DW_TAG_interface_type:
42950 case DW_TAG_structure_type:
42951 case DW_TAG_union_type:
42952 case DW_TAG_enumeration_type:
42954 is_static = language != CPLUS;
42962 @appendix Manual pages
42966 * gdb man:: The GNU Debugger man page
42967 * gdbserver man:: Remote Server for the GNU Debugger man page
42968 * gcore man:: Generate a core file of a running program
42969 * gdbinit man:: gdbinit scripts
42970 * gdb-add-index man:: Add index files to speed up GDB
42976 @c man title gdb The GNU Debugger
42978 @c man begin SYNOPSIS gdb
42979 gdb [@option{-help}] [@option{-nh}] [@option{-nx}] [@option{-q}]
42980 [@option{-batch}] [@option{-cd=}@var{dir}] [@option{-f}]
42981 [@option{-b}@w{ }@var{bps}]
42982 [@option{-tty=}@var{dev}] [@option{-s} @var{symfile}]
42983 [@option{-e}@w{ }@var{prog}] [@option{-se}@w{ }@var{prog}]
42984 [@option{-c}@w{ }@var{core}] [@option{-p}@w{ }@var{procID}]
42985 [@option{-x}@w{ }@var{cmds}] [@option{-d}@w{ }@var{dir}]
42986 [@var{prog}|@var{prog} @var{procID}|@var{prog} @var{core}]
42989 @c man begin DESCRIPTION gdb
42990 The purpose of a debugger such as @value{GDBN} is to allow you to see what is
42991 going on ``inside'' another program while it executes -- or what another
42992 program was doing at the moment it crashed.
42994 @value{GDBN} can do four main kinds of things (plus other things in support of
42995 these) to help you catch bugs in the act:
42999 Start your program, specifying anything that might affect its behavior.
43002 Make your program stop on specified conditions.
43005 Examine what has happened, when your program has stopped.
43008 Change things in your program, so you can experiment with correcting the
43009 effects of one bug and go on to learn about another.
43012 You can use @value{GDBN} to debug programs written in C, C@t{++}, Fortran and
43015 @value{GDBN} is invoked with the shell command @code{gdb}. Once started, it reads
43016 commands from the terminal until you tell it to exit with the @value{GDBN}
43017 command @code{quit}. You can get online help from @value{GDBN} itself
43018 by using the command @code{help}.
43020 You can run @code{gdb} with no arguments or options; but the most
43021 usual way to start @value{GDBN} is with one argument or two, specifying an
43022 executable program as the argument:
43028 You can also start with both an executable program and a core file specified:
43034 You can, instead, specify a process ID as a second argument, if you want
43035 to debug a running process:
43043 would attach @value{GDBN} to process @code{1234} (unless you also have a file
43044 named @file{1234}; @value{GDBN} does check for a core file first).
43045 With option @option{-p} you can omit the @var{program} filename.
43047 Here are some of the most frequently needed @value{GDBN} commands:
43049 @c pod2man highlights the right hand side of the @item lines.
43051 @item break [@var{file}:]@var{function}
43052 Set a breakpoint at @var{function} (in @var{file}).
43054 @item run [@var{arglist}]
43055 Start your program (with @var{arglist}, if specified).
43058 Backtrace: display the program stack.
43060 @item print @var{expr}
43061 Display the value of an expression.
43064 Continue running your program (after stopping, e.g. at a breakpoint).
43067 Execute next program line (after stopping); step @emph{over} any
43068 function calls in the line.
43070 @item edit [@var{file}:]@var{function}
43071 look at the program line where it is presently stopped.
43073 @item list [@var{file}:]@var{function}
43074 type the text of the program in the vicinity of where it is presently stopped.
43077 Execute next program line (after stopping); step @emph{into} any
43078 function calls in the line.
43080 @item help [@var{name}]
43081 Show information about @value{GDBN} command @var{name}, or general information
43082 about using @value{GDBN}.
43085 Exit from @value{GDBN}.
43089 For full details on @value{GDBN},
43090 see @cite{Using GDB: A Guide to the GNU Source-Level Debugger},
43091 by Richard M. Stallman and Roland H. Pesch. The same text is available online
43092 as the @code{gdb} entry in the @code{info} program.
43096 @c man begin OPTIONS gdb
43097 Any arguments other than options specify an executable
43098 file and core file (or process ID); that is, the first argument
43099 encountered with no
43100 associated option flag is equivalent to a @option{-se} option, and the second,
43101 if any, is equivalent to a @option{-c} option if it's the name of a file.
43103 both long and short forms; both are shown here. The long forms are also
43104 recognized if you truncate them, so long as enough of the option is
43105 present to be unambiguous. (If you prefer, you can flag option
43106 arguments with @option{+} rather than @option{-}, though we illustrate the
43107 more usual convention.)
43109 All the options and command line arguments you give are processed
43110 in sequential order. The order makes a difference when the @option{-x}
43116 List all options, with brief explanations.
43118 @item -symbols=@var{file}
43119 @itemx -s @var{file}
43120 Read symbol table from file @var{file}.
43123 Enable writing into executable and core files.
43125 @item -exec=@var{file}
43126 @itemx -e @var{file}
43127 Use file @var{file} as the executable file to execute when
43128 appropriate, and for examining pure data in conjunction with a core
43131 @item -se=@var{file}
43132 Read symbol table from file @var{file} and use it as the executable
43135 @item -core=@var{file}
43136 @itemx -c @var{file}
43137 Use file @var{file} as a core dump to examine.
43139 @item -command=@var{file}
43140 @itemx -x @var{file}
43141 Execute @value{GDBN} commands from file @var{file}.
43143 @item -ex @var{command}
43144 Execute given @value{GDBN} @var{command}.
43146 @item -directory=@var{directory}
43147 @itemx -d @var{directory}
43148 Add @var{directory} to the path to search for source files.
43151 Do not execute commands from @file{~/.gdbinit}.
43155 Do not execute commands from any @file{.gdbinit} initialization files.
43159 ``Quiet''. Do not print the introductory and copyright messages. These
43160 messages are also suppressed in batch mode.
43163 Run in batch mode. Exit with status @code{0} after processing all the command
43164 files specified with @option{-x} (and @file{.gdbinit}, if not inhibited).
43165 Exit with nonzero status if an error occurs in executing the @value{GDBN}
43166 commands in the command files.
43168 Batch mode may be useful for running @value{GDBN} as a filter, for example to
43169 download and run a program on another computer; in order to make this
43170 more useful, the message
43173 Program exited normally.
43177 (which is ordinarily issued whenever a program running under @value{GDBN} control
43178 terminates) is not issued when running in batch mode.
43180 @item -cd=@var{directory}
43181 Run @value{GDBN} using @var{directory} as its working directory,
43182 instead of the current directory.
43186 Emacs sets this option when it runs @value{GDBN} as a subprocess. It tells
43187 @value{GDBN} to output the full file name and line number in a standard,
43188 recognizable fashion each time a stack frame is displayed (which
43189 includes each time the program stops). This recognizable format looks
43190 like two @samp{\032} characters, followed by the file name, line number
43191 and character position separated by colons, and a newline. The
43192 Emacs-to-@value{GDBN} interface program uses the two @samp{\032}
43193 characters as a signal to display the source code for the frame.
43196 Set the line speed (baud rate or bits per second) of any serial
43197 interface used by @value{GDBN} for remote debugging.
43199 @item -tty=@var{device}
43200 Run using @var{device} for your program's standard input and output.
43204 @c man begin SEEALSO gdb
43206 The full documentation for @value{GDBN} is maintained as a Texinfo manual.
43207 If the @code{info} and @code{gdb} programs and @value{GDBN}'s Texinfo
43208 documentation are properly installed at your site, the command
43215 should give you access to the complete manual.
43217 @cite{Using GDB: A Guide to the GNU Source-Level Debugger},
43218 Richard M. Stallman and Roland H. Pesch, July 1991.
43222 @node gdbserver man
43223 @heading gdbserver man
43225 @c man title gdbserver Remote Server for the GNU Debugger
43227 @c man begin SYNOPSIS gdbserver
43228 gdbserver @var{comm} @var{prog} [@var{args}@dots{}]
43230 gdbserver --attach @var{comm} @var{pid}
43232 gdbserver --multi @var{comm}
43236 @c man begin DESCRIPTION gdbserver
43237 @command{gdbserver} is a program that allows you to run @value{GDBN} on a different machine
43238 than the one which is running the program being debugged.
43241 @subheading Usage (server (target) side)
43244 Usage (server (target) side):
43247 First, you need to have a copy of the program you want to debug put onto
43248 the target system. The program can be stripped to save space if needed, as
43249 @command{gdbserver} doesn't care about symbols. All symbol handling is taken care of by
43250 the @value{GDBN} running on the host system.
43252 To use the server, you log on to the target system, and run the @command{gdbserver}
43253 program. You must tell it (a) how to communicate with @value{GDBN}, (b) the name of
43254 your program, and (c) its arguments. The general syntax is:
43257 target> gdbserver @var{comm} @var{program} [@var{args} ...]
43260 For example, using a serial port, you might say:
43264 @c @file would wrap it as F</dev/com1>.
43265 target> gdbserver /dev/com1 emacs foo.txt
43268 target> gdbserver @file{/dev/com1} emacs foo.txt
43272 This tells @command{gdbserver} to debug emacs with an argument of foo.txt, and
43273 to communicate with @value{GDBN} via @file{/dev/com1}. @command{gdbserver} now
43274 waits patiently for the host @value{GDBN} to communicate with it.
43276 To use a TCP connection, you could say:
43279 target> gdbserver host:2345 emacs foo.txt
43282 This says pretty much the same thing as the last example, except that we are
43283 going to communicate with the @code{host} @value{GDBN} via TCP. The @code{host:2345} argument means
43284 that we are expecting to see a TCP connection from @code{host} to local TCP port
43285 2345. (Currently, the @code{host} part is ignored.) You can choose any number you
43286 want for the port number as long as it does not conflict with any existing TCP
43287 ports on the target system. This same port number must be used in the host
43288 @value{GDBN}s @code{target remote} command, which will be described shortly. Note that if
43289 you chose a port number that conflicts with another service, @command{gdbserver} will
43290 print an error message and exit.
43292 @command{gdbserver} can also attach to running programs.
43293 This is accomplished via the @option{--attach} argument. The syntax is:
43296 target> gdbserver --attach @var{comm} @var{pid}
43299 @var{pid} is the process ID of a currently running process. It isn't
43300 necessary to point @command{gdbserver} at a binary for the running process.
43302 To start @code{gdbserver} without supplying an initial command to run
43303 or process ID to attach, use the @option{--multi} command line option.
43304 In such case you should connect using @kbd{target extended-remote} to start
43305 the program you want to debug.
43308 target> gdbserver --multi @var{comm}
43312 @subheading Usage (host side)
43318 You need an unstripped copy of the target program on your host system, since
43319 @value{GDBN} needs to examine it's symbol tables and such. Start up @value{GDBN} as you normally
43320 would, with the target program as the first argument. (You may need to use the
43321 @option{--baud} option if the serial line is running at anything except 9600 baud.)
43322 That is @code{gdb TARGET-PROG}, or @code{gdb --baud BAUD TARGET-PROG}. After that, the only
43323 new command you need to know about is @code{target remote}
43324 (or @code{target extended-remote}). Its argument is either
43325 a device name (usually a serial device, like @file{/dev/ttyb}), or a @code{HOST:PORT}
43326 descriptor. For example:
43330 @c @file would wrap it as F</dev/ttyb>.
43331 (gdb) target remote /dev/ttyb
43334 (gdb) target remote @file{/dev/ttyb}
43339 communicates with the server via serial line @file{/dev/ttyb}, and:
43342 (gdb) target remote the-target:2345
43346 communicates via a TCP connection to port 2345 on host `the-target', where
43347 you previously started up @command{gdbserver} with the same port number. Note that for
43348 TCP connections, you must start up @command{gdbserver} prior to using the `target remote'
43349 command, otherwise you may get an error that looks something like
43350 `Connection refused'.
43352 @command{gdbserver} can also debug multiple inferiors at once,
43355 the @value{GDBN} manual in node @code{Inferiors and Programs}
43356 -- shell command @code{info -f gdb -n 'Inferiors and Programs'}.
43359 @ref{Inferiors and Programs}.
43361 In such case use the @code{extended-remote} @value{GDBN} command variant:
43364 (gdb) target extended-remote the-target:2345
43367 The @command{gdbserver} option @option{--multi} may or may not be used in such
43371 @c man begin OPTIONS gdbserver
43372 There are three different modes for invoking @command{gdbserver}:
43377 Debug a specific program specified by its program name:
43380 gdbserver @var{comm} @var{prog} [@var{args}@dots{}]
43383 The @var{comm} parameter specifies how should the server communicate
43384 with @value{GDBN}; it is either a device name (to use a serial line),
43385 a TCP port number (@code{:1234}), or @code{-} or @code{stdio} to use
43386 stdin/stdout of @code{gdbserver}. Specify the name of the program to
43387 debug in @var{prog}. Any remaining arguments will be passed to the
43388 program verbatim. When the program exits, @value{GDBN} will close the
43389 connection, and @code{gdbserver} will exit.
43392 Debug a specific program by specifying the process ID of a running
43396 gdbserver --attach @var{comm} @var{pid}
43399 The @var{comm} parameter is as described above. Supply the process ID
43400 of a running program in @var{pid}; @value{GDBN} will do everything
43401 else. Like with the previous mode, when the process @var{pid} exits,
43402 @value{GDBN} will close the connection, and @code{gdbserver} will exit.
43405 Multi-process mode -- debug more than one program/process:
43408 gdbserver --multi @var{comm}
43411 In this mode, @value{GDBN} can instruct @command{gdbserver} which
43412 command(s) to run. Unlike the other 2 modes, @value{GDBN} will not
43413 close the connection when a process being debugged exits, so you can
43414 debug several processes in the same session.
43417 In each of the modes you may specify these options:
43422 List all options, with brief explanations.
43425 This option causes @command{gdbserver} to print its version number and exit.
43428 @command{gdbserver} will attach to a running program. The syntax is:
43431 target> gdbserver --attach @var{comm} @var{pid}
43434 @var{pid} is the process ID of a currently running process. It isn't
43435 necessary to point @command{gdbserver} at a binary for the running process.
43438 To start @code{gdbserver} without supplying an initial command to run
43439 or process ID to attach, use this command line option.
43440 Then you can connect using @kbd{target extended-remote} and start
43441 the program you want to debug. The syntax is:
43444 target> gdbserver --multi @var{comm}
43448 Instruct @code{gdbserver} to display extra status information about the debugging
43450 This option is intended for @code{gdbserver} development and for bug reports to
43453 @item --remote-debug
43454 Instruct @code{gdbserver} to display remote protocol debug output.
43455 This option is intended for @code{gdbserver} development and for bug reports to
43458 @item --debug-format=option1@r{[},option2,...@r{]}
43459 Instruct @code{gdbserver} to include extra information in each line
43460 of debugging output.
43461 @xref{Other Command-Line Arguments for gdbserver}.
43464 Specify a wrapper to launch programs
43465 for debugging. The option should be followed by the name of the
43466 wrapper, then any command-line arguments to pass to the wrapper, then
43467 @kbd{--} indicating the end of the wrapper arguments.
43470 By default, @command{gdbserver} keeps the listening TCP port open, so that
43471 additional connections are possible. However, if you start @code{gdbserver}
43472 with the @option{--once} option, it will stop listening for any further
43473 connection attempts after connecting to the first @value{GDBN} session.
43475 @c --disable-packet is not documented for users.
43477 @c --disable-randomization and --no-disable-randomization are superseded by
43478 @c QDisableRandomization.
43483 @c man begin SEEALSO gdbserver
43485 The full documentation for @value{GDBN} is maintained as a Texinfo manual.
43486 If the @code{info} and @code{gdb} programs and @value{GDBN}'s Texinfo
43487 documentation are properly installed at your site, the command
43493 should give you access to the complete manual.
43495 @cite{Using GDB: A Guide to the GNU Source-Level Debugger},
43496 Richard M. Stallman and Roland H. Pesch, July 1991.
43503 @c man title gcore Generate a core file of a running program
43506 @c man begin SYNOPSIS gcore
43507 gcore [-a] [-o @var{filename}] @var{pid}
43511 @c man begin DESCRIPTION gcore
43512 Generate a core dump of a running program with process ID @var{pid}.
43513 Produced file is equivalent to a kernel produced core file as if the process
43514 crashed (and if @kbd{ulimit -c} were used to set up an appropriate core dump
43515 limit). Unlike after a crash, after @command{gcore} the program remains
43516 running without any change.
43519 @c man begin OPTIONS gcore
43522 Dump all memory mappings. The actual effect of this option depends on
43523 the Operating System. On @sc{gnu}/Linux, it will disable
43524 @code{use-coredump-filter} (@pxref{set use-coredump-filter}) and
43525 enable @code{dump-excluded-mappings} (@pxref{set
43526 dump-excluded-mappings}).
43528 @item -o @var{filename}
43529 The optional argument
43530 @var{filename} specifies the file name where to put the core dump.
43531 If not specified, the file name defaults to @file{core.@var{pid}},
43532 where @var{pid} is the running program process ID.
43536 @c man begin SEEALSO gcore
43538 The full documentation for @value{GDBN} is maintained as a Texinfo manual.
43539 If the @code{info} and @code{gdb} programs and @value{GDBN}'s Texinfo
43540 documentation are properly installed at your site, the command
43547 should give you access to the complete manual.
43549 @cite{Using GDB: A Guide to the GNU Source-Level Debugger},
43550 Richard M. Stallman and Roland H. Pesch, July 1991.
43557 @c man title gdbinit GDB initialization scripts
43560 @c man begin SYNOPSIS gdbinit
43561 @ifset SYSTEM_GDBINIT
43562 @value{SYSTEM_GDBINIT}
43571 @c man begin DESCRIPTION gdbinit
43572 These files contain @value{GDBN} commands to automatically execute during
43573 @value{GDBN} startup. The lines of contents are canned sequences of commands,
43576 the @value{GDBN} manual in node @code{Sequences}
43577 -- shell command @code{info -f gdb -n Sequences}.
43583 Please read more in
43585 the @value{GDBN} manual in node @code{Startup}
43586 -- shell command @code{info -f gdb -n Startup}.
43593 @ifset SYSTEM_GDBINIT
43594 @item @value{SYSTEM_GDBINIT}
43596 @ifclear SYSTEM_GDBINIT
43597 @item (not enabled with @code{--with-system-gdbinit} during compilation)
43599 System-wide initialization file. It is executed unless user specified
43600 @value{GDBN} option @code{-nx} or @code{-n}.
43603 the @value{GDBN} manual in node @code{System-wide configuration}
43604 -- shell command @code{info -f gdb -n 'System-wide configuration'}.
43607 @ref{System-wide configuration}.
43611 User initialization file. It is executed unless user specified
43612 @value{GDBN} options @code{-nx}, @code{-n} or @code{-nh}.
43615 Initialization file for current directory. It may need to be enabled with
43616 @value{GDBN} security command @code{set auto-load local-gdbinit}.
43619 the @value{GDBN} manual in node @code{Init File in the Current Directory}
43620 -- shell command @code{info -f gdb -n 'Init File in the Current Directory'}.
43623 @ref{Init File in the Current Directory}.
43628 @c man begin SEEALSO gdbinit
43630 gdb(1), @code{info -f gdb -n Startup}
43632 The full documentation for @value{GDBN} is maintained as a Texinfo manual.
43633 If the @code{info} and @code{gdb} programs and @value{GDBN}'s Texinfo
43634 documentation are properly installed at your site, the command
43640 should give you access to the complete manual.
43642 @cite{Using GDB: A Guide to the GNU Source-Level Debugger},
43643 Richard M. Stallman and Roland H. Pesch, July 1991.
43647 @node gdb-add-index man
43648 @heading gdb-add-index
43649 @pindex gdb-add-index
43650 @anchor{gdb-add-index}
43652 @c man title gdb-add-index Add index files to speed up GDB
43654 @c man begin SYNOPSIS gdb-add-index
43655 gdb-add-index @var{filename}
43658 @c man begin DESCRIPTION gdb-add-index
43659 When @value{GDBN} finds a symbol file, it scans the symbols in the
43660 file in order to construct an internal symbol table. This lets most
43661 @value{GDBN} operations work quickly--at the cost of a delay early on.
43662 For large programs, this delay can be quite lengthy, so @value{GDBN}
43663 provides a way to build an index, which speeds up startup.
43665 To determine whether a file contains such an index, use the command
43666 @kbd{readelf -S filename}: the index is stored in a section named
43667 @code{.gdb_index}. The index file can only be produced on systems
43668 which use ELF binaries and DWARF debug information (i.e., sections
43669 named @code{.debug_*}).
43671 @command{gdb-add-index} uses @value{GDBN} and @command{objdump} found
43672 in the @env{PATH} environment variable. If you want to use different
43673 versions of these programs, you can specify them through the
43674 @env{GDB} and @env{OBJDUMP} environment variables.
43678 the @value{GDBN} manual in node @code{Index Files}
43679 -- shell command @kbd{info -f gdb -n "Index Files"}.
43686 @c man begin SEEALSO gdb-add-index
43688 The full documentation for @value{GDBN} is maintained as a Texinfo manual.
43689 If the @code{info} and @code{gdb} programs and @value{GDBN}'s Texinfo
43690 documentation are properly installed at your site, the command
43696 should give you access to the complete manual.
43698 @cite{Using GDB: A Guide to the GNU Source-Level Debugger},
43699 Richard M. Stallman and Roland H. Pesch, July 1991.
43705 @node GNU Free Documentation License
43706 @appendix GNU Free Documentation License
43709 @node Concept Index
43710 @unnumbered Concept Index
43714 @node Command and Variable Index
43715 @unnumbered Command, Variable, and Function Index
43720 % I think something like @@colophon should be in texinfo. In the
43722 \long\def\colophon{\hbox to0pt{}\vfill
43723 \centerline{The body of this manual is set in}
43724 \centerline{\fontname\tenrm,}
43725 \centerline{with headings in {\bf\fontname\tenbf}}
43726 \centerline{and examples in {\tt\fontname\tentt}.}
43727 \centerline{{\it\fontname\tenit\/},}
43728 \centerline{{\bf\fontname\tenbf}, and}
43729 \centerline{{\sl\fontname\tensl\/}}
43730 \centerline{are used for emphasis.}\vfill}
43732 % Blame: doc@@cygnus.com, 1991.