Commit | Line | Data |
---|---|---|
c906108c | 1 | \input texinfo @c -*-texinfo-*- |
c02a867d | 2 | @c Copyright (C) 1988, 1989, 1990, 1991, 1992, 1993, 1994, 1995, 1996, 1998, |
a67ec3f4 | 3 | @c 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009 |
c906108c SS |
4 | @c Free Software Foundation, Inc. |
5 | @c | |
5d161b24 | 6 | @c %**start of header |
c906108c SS |
7 | @c makeinfo ignores cmds prev to setfilename, so its arg cannot make use |
8 | @c of @set vars. However, you can override filename with makeinfo -o. | |
9 | @setfilename gdb.info | |
10 | @c | |
11 | @include gdb-cfg.texi | |
12 | @c | |
c906108c | 13 | @settitle Debugging with @value{GDBN} |
c906108c SS |
14 | @setchapternewpage odd |
15 | @c %**end of header | |
16 | ||
17 | @iftex | |
18 | @c @smallbook | |
19 | @c @cropmarks | |
20 | @end iftex | |
21 | ||
22 | @finalout | |
23 | @syncodeindex ky cp | |
89c73ade | 24 | @syncodeindex tp cp |
c906108c | 25 | |
41afff9a | 26 | @c readline appendices use @vindex, @findex and @ftable, |
48e934c6 | 27 | @c annotate.texi and gdbmi use @findex. |
c906108c | 28 | @syncodeindex vr cp |
41afff9a | 29 | @syncodeindex fn cp |
c906108c SS |
30 | |
31 | @c !!set GDB manual's edition---not the same as GDB version! | |
9fe8321b | 32 | @c This is updated by GNU Press. |
e9c75b65 | 33 | @set EDITION Ninth |
c906108c | 34 | |
87885426 FN |
35 | @c !!set GDB edit command default editor |
36 | @set EDITOR /bin/ex | |
c906108c | 37 | |
6c0e9fb3 | 38 | @c THIS MANUAL REQUIRES TEXINFO 4.0 OR LATER. |
c906108c | 39 | |
c906108c | 40 | @c This is a dir.info fragment to support semi-automated addition of |
6d2ebf8b | 41 | @c manuals to an info tree. |
03727ca6 | 42 | @dircategory Software development |
96a2c332 | 43 | @direntry |
03727ca6 | 44 | * Gdb: (gdb). The GNU debugger. |
96a2c332 SS |
45 | @end direntry |
46 | ||
a67ec3f4 JM |
47 | @copying |
48 | Copyright @copyright{} 1988, 1989, 1990, 1991, 1992, 1993, 1994, 1995, 1996, | |
49 | 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009 | |
50 | Free Software Foundation, Inc. | |
c906108c | 51 | |
e9c75b65 EZ |
52 | Permission is granted to copy, distribute and/or modify this document |
53 | under the terms of the GNU Free Documentation License, Version 1.1 or | |
54 | any later version published by the Free Software Foundation; with the | |
959acfd1 EZ |
55 | Invariant Sections being ``Free Software'' and ``Free Software Needs |
56 | Free Documentation'', with the Front-Cover Texts being ``A GNU Manual,'' | |
57 | and with the Back-Cover Texts as in (a) below. | |
c906108c | 58 | |
b8533aec DJ |
59 | (a) The FSF's Back-Cover Text is: ``You are free to copy and modify |
60 | this GNU Manual. Buying copies from GNU Press supports the FSF in | |
61 | developing GNU and promoting software freedom.'' | |
a67ec3f4 JM |
62 | @end copying |
63 | ||
64 | @ifnottex | |
65 | This file documents the @sc{gnu} debugger @value{GDBN}. | |
66 | ||
67 | This is the @value{EDITION} Edition, of @cite{Debugging with | |
68 | @value{GDBN}: the @sc{gnu} Source-Level Debugger} for @value{GDBN} | |
69 | @ifset VERSION_PACKAGE | |
70 | @value{VERSION_PACKAGE} | |
71 | @end ifset | |
72 | Version @value{GDBVN}. | |
73 | ||
74 | @insertcopying | |
75 | @end ifnottex | |
c906108c SS |
76 | |
77 | @titlepage | |
78 | @title Debugging with @value{GDBN} | |
79 | @subtitle The @sc{gnu} Source-Level Debugger | |
c906108c | 80 | @sp 1 |
c906108c | 81 | @subtitle @value{EDITION} Edition, for @value{GDBN} version @value{GDBVN} |
c16158bc JM |
82 | @ifset VERSION_PACKAGE |
83 | @sp 1 | |
84 | @subtitle @value{VERSION_PACKAGE} | |
85 | @end ifset | |
9e9c5ae7 | 86 | @author Richard Stallman, Roland Pesch, Stan Shebs, et al. |
c906108c | 87 | @page |
c906108c SS |
88 | @tex |
89 | {\parskip=0pt | |
c16158bc | 90 | \hfill (Send bugs and comments on @value{GDBN} to @value{BUGURL}.)\par |
c906108c SS |
91 | \hfill {\it Debugging with @value{GDBN}}\par |
92 | \hfill \TeX{}info \texinfoversion\par | |
93 | } | |
94 | @end tex | |
53a5351d | 95 | |
c906108c | 96 | @vskip 0pt plus 1filll |
c906108c | 97 | Published by the Free Software Foundation @* |
c02a867d EZ |
98 | 51 Franklin Street, Fifth Floor, |
99 | Boston, MA 02110-1301, USA@* | |
6d2ebf8b | 100 | ISBN 1-882114-77-9 @* |
e9c75b65 | 101 | |
a67ec3f4 | 102 | @insertcopying |
3fb6a982 JB |
103 | @page |
104 | This edition of the GDB manual is dedicated to the memory of Fred | |
105 | Fish. Fred was a long-standing contributor to GDB and to Free | |
106 | software in general. We will miss him. | |
c906108c SS |
107 | @end titlepage |
108 | @page | |
109 | ||
6c0e9fb3 | 110 | @ifnottex |
6d2ebf8b SS |
111 | @node Top, Summary, (dir), (dir) |
112 | ||
c906108c SS |
113 | @top Debugging with @value{GDBN} |
114 | ||
115 | This file describes @value{GDBN}, the @sc{gnu} symbolic debugger. | |
116 | ||
c16158bc JM |
117 | This is the @value{EDITION} Edition, for @value{GDBN} |
118 | @ifset VERSION_PACKAGE | |
119 | @value{VERSION_PACKAGE} | |
120 | @end ifset | |
121 | Version @value{GDBVN}. | |
c906108c | 122 | |
a67ec3f4 | 123 | Copyright (C) 1988-2009 Free Software Foundation, Inc. |
6d2ebf8b | 124 | |
3fb6a982 JB |
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. | |
128 | ||
6d2ebf8b SS |
129 | @menu |
130 | * Summary:: Summary of @value{GDBN} | |
131 | * Sample Session:: A sample @value{GDBN} session | |
132 | ||
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 | |
bacec72f | 137 | * Reverse Execution:: Running programs backward |
a2311334 | 138 | * Process Record and Replay:: Recording inferior's execution and replaying it |
6d2ebf8b SS |
139 | * Stack:: Examining the stack |
140 | * Source:: Examining source files | |
141 | * Data:: Examining data | |
edb3359d | 142 | * Optimized Code:: Debugging optimized code |
e2e0bcd1 | 143 | * Macros:: Preprocessor Macros |
b37052ae | 144 | * Tracepoints:: Debugging remote targets non-intrusively |
df0cd8c5 | 145 | * Overlays:: Debugging programs that use overlays |
6d2ebf8b SS |
146 | |
147 | * Languages:: Using @value{GDBN} with different languages | |
148 | ||
149 | * Symbols:: Examining the symbol table | |
150 | * Altering:: Altering execution | |
151 | * GDB Files:: @value{GDBN} files | |
152 | * Targets:: Specifying a debugging target | |
6b2f586d | 153 | * Remote Debugging:: Debugging remote programs |
6d2ebf8b SS |
154 | * Configurations:: Configuration-specific information |
155 | * Controlling GDB:: Controlling @value{GDBN} | |
d57a3c85 | 156 | * Extending GDB:: Extending @value{GDBN} |
21c294e6 | 157 | * Interpreters:: Command Interpreters |
c8f4133a | 158 | * TUI:: @value{GDBN} Text User Interface |
6d2ebf8b | 159 | * Emacs:: Using @value{GDBN} under @sc{gnu} Emacs |
7162c0ca | 160 | * GDB/MI:: @value{GDBN}'s Machine Interface. |
c8f4133a | 161 | * Annotations:: @value{GDBN}'s annotation interface. |
4efc6507 | 162 | * JIT Interface:: Using the JIT debugging interface. |
6d2ebf8b SS |
163 | |
164 | * GDB Bugs:: Reporting bugs in @value{GDBN} | |
6d2ebf8b SS |
165 | |
166 | * Command Line Editing:: Command Line Editing | |
167 | * Using History Interactively:: Using History Interactively | |
0869d01b | 168 | * Formatting Documentation:: How to format and print @value{GDBN} documentation |
6d2ebf8b | 169 | * Installing GDB:: Installing GDB |
eb12ee30 | 170 | * Maintenance Commands:: Maintenance Commands |
e0ce93ac | 171 | * Remote Protocol:: GDB Remote Serial Protocol |
f418dd93 | 172 | * Agent Expressions:: The GDB Agent Expression Mechanism |
23181151 DJ |
173 | * Target Descriptions:: How targets can describe themselves to |
174 | @value{GDBN} | |
07e059b5 VP |
175 | * Operating System Information:: Getting additional information from |
176 | the operating system | |
aab4e0ec AC |
177 | * Copying:: GNU General Public License says |
178 | how you can copy and share GDB | |
6826cf00 | 179 | * GNU Free Documentation License:: The license for this documentation |
6d2ebf8b SS |
180 | * Index:: Index |
181 | @end menu | |
182 | ||
6c0e9fb3 | 183 | @end ifnottex |
c906108c | 184 | |
449f3b6c | 185 | @contents |
449f3b6c | 186 | |
6d2ebf8b | 187 | @node Summary |
c906108c SS |
188 | @unnumbered Summary of @value{GDBN} |
189 | ||
190 | The purpose of a debugger such as @value{GDBN} is to allow you to see what is | |
191 | going on ``inside'' another program while it executes---or what another | |
192 | program was doing at the moment it crashed. | |
193 | ||
194 | @value{GDBN} can do four main kinds of things (plus other things in support of | |
195 | these) to help you catch bugs in the act: | |
196 | ||
197 | @itemize @bullet | |
198 | @item | |
199 | Start your program, specifying anything that might affect its behavior. | |
200 | ||
201 | @item | |
202 | Make your program stop on specified conditions. | |
203 | ||
204 | @item | |
205 | Examine what has happened, when your program has stopped. | |
206 | ||
207 | @item | |
208 | Change things in your program, so you can experiment with correcting the | |
209 | effects of one bug and go on to learn about another. | |
210 | @end itemize | |
211 | ||
49efadf5 | 212 | You can use @value{GDBN} to debug programs written in C and C@t{++}. |
79a6e687 | 213 | For more information, see @ref{Supported Languages,,Supported Languages}. |
c906108c SS |
214 | For more information, see @ref{C,,C and C++}. |
215 | ||
cce74817 | 216 | @cindex Modula-2 |
e632838e AC |
217 | Support for Modula-2 is partial. For information on Modula-2, see |
218 | @ref{Modula-2,,Modula-2}. | |
c906108c | 219 | |
cce74817 JM |
220 | @cindex Pascal |
221 | Debugging Pascal programs which use sets, subranges, file variables, or | |
222 | nested functions does not currently work. @value{GDBN} does not support | |
223 | entering expressions, printing values, or similar features using Pascal | |
224 | syntax. | |
c906108c | 225 | |
c906108c SS |
226 | @cindex Fortran |
227 | @value{GDBN} can be used to debug programs written in Fortran, although | |
53a5351d | 228 | it may be necessary to refer to some variables with a trailing |
cce74817 | 229 | underscore. |
c906108c | 230 | |
b37303ee AF |
231 | @value{GDBN} can be used to debug programs written in Objective-C, |
232 | using either the Apple/NeXT or the GNU Objective-C runtime. | |
233 | ||
c906108c SS |
234 | @menu |
235 | * Free Software:: Freely redistributable software | |
236 | * Contributors:: Contributors to GDB | |
237 | @end menu | |
238 | ||
6d2ebf8b | 239 | @node Free Software |
79a6e687 | 240 | @unnumberedsec Free Software |
c906108c | 241 | |
5d161b24 | 242 | @value{GDBN} is @dfn{free software}, protected by the @sc{gnu} |
c906108c SS |
243 | General Public License |
244 | (GPL). The GPL gives you the freedom to copy or adapt a licensed | |
245 | program---but every person getting a copy also gets with it the | |
246 | freedom to modify that copy (which means that they must get access to | |
247 | the source code), and the freedom to distribute further copies. | |
248 | Typical software companies use copyrights to limit your freedoms; the | |
249 | Free Software Foundation uses the GPL to preserve these freedoms. | |
250 | ||
251 | Fundamentally, the General Public License is a license which says that | |
252 | you have these freedoms and that you cannot take these freedoms away | |
253 | from anyone else. | |
254 | ||
2666264b | 255 | @unnumberedsec Free Software Needs Free Documentation |
959acfd1 EZ |
256 | |
257 | The biggest deficiency in the free software community today is not in | |
258 | the software---it is the lack of good free documentation that we can | |
259 | include with the free software. Many of our most important | |
260 | programs do not come with free reference manuals and free introductory | |
261 | texts. Documentation is an essential part of any software package; | |
262 | when an important free software package does not come with a free | |
263 | manual and a free tutorial, that is a major gap. We have many such | |
264 | gaps today. | |
265 | ||
266 | Consider Perl, for instance. The tutorial manuals that people | |
267 | normally use are non-free. How did this come about? Because the | |
268 | authors of those manuals published them with restrictive terms---no | |
269 | copying, no modification, source files not available---which exclude | |
270 | them from the free software world. | |
271 | ||
272 | That wasn't the first time this sort of thing happened, and it was far | |
273 | from the last. Many times we have heard a GNU user eagerly describe a | |
274 | manual that he is writing, his intended contribution to the community, | |
275 | only to learn that he had ruined everything by signing a publication | |
276 | contract to make it non-free. | |
277 | ||
278 | Free documentation, like free software, is a matter of freedom, not | |
279 | price. The problem with the non-free manual is not that publishers | |
280 | charge a price for printed copies---that in itself is fine. (The Free | |
281 | Software Foundation sells printed copies of manuals, too.) The | |
282 | problem is the restrictions on the use of the manual. Free manuals | |
283 | are available in source code form, and give you permission to copy and | |
284 | modify. Non-free manuals do not allow this. | |
285 | ||
286 | The criteria of freedom for a free manual are roughly the same as for | |
287 | free software. Redistribution (including the normal kinds of | |
288 | commercial redistribution) must be permitted, so that the manual can | |
289 | accompany every copy of the program, both on-line and on paper. | |
290 | ||
291 | Permission for modification of the technical content is crucial too. | |
292 | When people modify the software, adding or changing features, if they | |
293 | are conscientious they will change the manual too---so they can | |
294 | provide accurate and clear documentation for the modified program. A | |
295 | manual that leaves you no choice but to write a new manual to document | |
296 | a changed version of the program is not really available to our | |
297 | community. | |
298 | ||
299 | Some kinds of limits on the way modification is handled are | |
300 | acceptable. For example, requirements to preserve the original | |
301 | author's copyright notice, the distribution terms, or the list of | |
302 | authors, are ok. It is also no problem to require modified versions | |
303 | to include notice that they were modified. Even entire sections that | |
304 | may not be deleted or changed are acceptable, as long as they deal | |
305 | with nontechnical topics (like this one). These kinds of restrictions | |
306 | are acceptable because they don't obstruct the community's normal use | |
307 | of the manual. | |
308 | ||
309 | However, it must be possible to modify all the @emph{technical} | |
310 | content of the manual, and then distribute the result in all the usual | |
311 | media, through all the usual channels. Otherwise, the restrictions | |
312 | obstruct the use of the manual, it is not free, and we need another | |
313 | manual to replace it. | |
314 | ||
315 | Please spread the word about this issue. Our community continues to | |
316 | lose manuals to proprietary publishing. If we spread the word that | |
317 | free software needs free reference manuals and free tutorials, perhaps | |
318 | the next person who wants to contribute by writing documentation will | |
319 | realize, before it is too late, that only free manuals contribute to | |
320 | the free software community. | |
321 | ||
322 | If you are writing documentation, please insist on publishing it under | |
323 | the GNU Free Documentation License or another free documentation | |
324 | license. Remember that this decision requires your approval---you | |
325 | don't have to let the publisher decide. Some commercial publishers | |
326 | will use a free license if you insist, but they will not propose the | |
327 | option; it is up to you to raise the issue and say firmly that this is | |
328 | what you want. If the publisher you are dealing with refuses, please | |
329 | try other publishers. If you're not sure whether a proposed license | |
42584a72 | 330 | is free, write to @email{licensing@@gnu.org}. |
959acfd1 EZ |
331 | |
332 | You can encourage commercial publishers to sell more free, copylefted | |
333 | manuals and tutorials by buying them, and particularly by buying | |
334 | copies from the publishers that paid for their writing or for major | |
335 | improvements. Meanwhile, try to avoid buying non-free documentation | |
336 | at all. Check the distribution terms of a manual before you buy it, | |
337 | and insist that whoever seeks your business must respect your freedom. | |
72c9928d EZ |
338 | Check the history of the book, and try to reward the publishers that |
339 | have paid or pay the authors to work on it. | |
959acfd1 EZ |
340 | |
341 | The Free Software Foundation maintains a list of free documentation | |
342 | published by other publishers, at | |
343 | @url{http://www.fsf.org/doc/other-free-books.html}. | |
344 | ||
6d2ebf8b | 345 | @node Contributors |
96a2c332 SS |
346 | @unnumberedsec Contributors to @value{GDBN} |
347 | ||
348 | Richard Stallman was the original author of @value{GDBN}, and of many | |
349 | other @sc{gnu} programs. Many others have contributed to its | |
350 | development. This section attempts to credit major contributors. One | |
351 | of the virtues of free software is that everyone is free to contribute | |
352 | to it; with regret, we cannot actually acknowledge everyone here. The | |
353 | file @file{ChangeLog} in the @value{GDBN} distribution approximates a | |
c906108c SS |
354 | blow-by-blow account. |
355 | ||
356 | Changes much prior to version 2.0 are lost in the mists of time. | |
357 | ||
358 | @quotation | |
359 | @emph{Plea:} Additions to this section are particularly welcome. If you | |
360 | or your friends (or enemies, to be evenhanded) have been unfairly | |
361 | omitted from this list, we would like to add your names! | |
362 | @end quotation | |
363 | ||
364 | So that they may not regard their many labors as thankless, we | |
365 | particularly thank those who shepherded @value{GDBN} through major | |
366 | releases: | |
7ba3cf9c | 367 | Andrew Cagney (releases 6.3, 6.2, 6.1, 6.0, 5.3, 5.2, 5.1 and 5.0); |
c906108c SS |
368 | Jim Blandy (release 4.18); |
369 | Jason Molenda (release 4.17); | |
370 | Stan Shebs (release 4.14); | |
371 | Fred Fish (releases 4.16, 4.15, 4.13, 4.12, 4.11, 4.10, and 4.9); | |
372 | Stu Grossman and John Gilmore (releases 4.8, 4.7, 4.6, 4.5, and 4.4); | |
373 | John Gilmore (releases 4.3, 4.2, 4.1, 4.0, and 3.9); | |
374 | Jim Kingdon (releases 3.5, 3.4, and 3.3); | |
375 | and Randy Smith (releases 3.2, 3.1, and 3.0). | |
376 | ||
377 | Richard Stallman, assisted at various times by Peter TerMaat, Chris | |
378 | Hanson, and Richard Mlynarik, handled releases through 2.8. | |
379 | ||
b37052ae EZ |
380 | Michael Tiemann is the author of most of the @sc{gnu} C@t{++} support |
381 | in @value{GDBN}, with significant additional contributions from Per | |
382 | Bothner and Daniel Berlin. James Clark wrote the @sc{gnu} C@t{++} | |
383 | demangler. Early work on C@t{++} was by Peter TerMaat (who also did | |
384 | much general update work leading to release 3.0). | |
c906108c | 385 | |
b37052ae | 386 | @value{GDBN} uses the BFD subroutine library to examine multiple |
c906108c SS |
387 | object-file formats; BFD was a joint project of David V. |
388 | Henkel-Wallace, Rich Pixley, Steve Chamberlain, and John Gilmore. | |
389 | ||
390 | David Johnson wrote the original COFF support; Pace Willison did | |
391 | the original support for encapsulated COFF. | |
392 | ||
0179ffac | 393 | Brent Benson of Harris Computer Systems contributed DWARF 2 support. |
c906108c SS |
394 | |
395 | Adam de Boor and Bradley Davis contributed the ISI Optimum V support. | |
396 | Per Bothner, Noboyuki Hikichi, and Alessandro Forin contributed MIPS | |
397 | support. | |
398 | Jean-Daniel Fekete contributed Sun 386i support. | |
399 | Chris Hanson improved the HP9000 support. | |
400 | Noboyuki Hikichi and Tomoyuki Hasei contributed Sony/News OS 3 support. | |
401 | David Johnson contributed Encore Umax support. | |
402 | Jyrki Kuoppala contributed Altos 3068 support. | |
403 | Jeff Law contributed HP PA and SOM support. | |
404 | Keith Packard contributed NS32K support. | |
405 | Doug Rabson contributed Acorn Risc Machine support. | |
406 | Bob Rusk contributed Harris Nighthawk CX-UX support. | |
407 | Chris Smith contributed Convex support (and Fortran debugging). | |
408 | Jonathan Stone contributed Pyramid support. | |
409 | Michael Tiemann contributed SPARC support. | |
410 | Tim Tucker contributed support for the Gould NP1 and Gould Powernode. | |
411 | Pace Willison contributed Intel 386 support. | |
412 | Jay Vosburgh contributed Symmetry support. | |
a37295f9 | 413 | Marko Mlinar contributed OpenRISC 1000 support. |
c906108c | 414 | |
1104b9e7 | 415 | Andreas Schwab contributed M68K @sc{gnu}/Linux support. |
c906108c SS |
416 | |
417 | Rich Schaefer and Peter Schauer helped with support of SunOS shared | |
418 | libraries. | |
419 | ||
420 | Jay Fenlason and Roland McGrath ensured that @value{GDBN} and GAS agree | |
421 | about several machine instruction sets. | |
422 | ||
423 | Patrick Duval, Ted Goldstein, Vikram Koka and Glenn Engel helped develop | |
424 | remote debugging. Intel Corporation, Wind River Systems, AMD, and ARM | |
425 | contributed remote debugging modules for the i960, VxWorks, A29K UDI, | |
426 | and RDI targets, respectively. | |
427 | ||
428 | Brian Fox is the author of the readline libraries providing | |
429 | command-line editing and command history. | |
430 | ||
7a292a7a SS |
431 | Andrew Beers of SUNY Buffalo wrote the language-switching code, the |
432 | Modula-2 support, and contributed the Languages chapter of this manual. | |
c906108c | 433 | |
5d161b24 | 434 | Fred Fish wrote most of the support for Unix System Vr4. |
b37052ae | 435 | He also enhanced the command-completion support to cover C@t{++} overloaded |
c906108c | 436 | symbols. |
c906108c | 437 | |
f24c5e49 KI |
438 | Hitachi America (now Renesas America), Ltd. sponsored the support for |
439 | H8/300, H8/500, and Super-H processors. | |
c906108c SS |
440 | |
441 | NEC sponsored the support for the v850, Vr4xxx, and Vr5xxx processors. | |
442 | ||
f24c5e49 KI |
443 | Mitsubishi (now Renesas) sponsored the support for D10V, D30V, and M32R/D |
444 | processors. | |
c906108c SS |
445 | |
446 | Toshiba sponsored the support for the TX39 Mips processor. | |
447 | ||
448 | Matsushita sponsored the support for the MN10200 and MN10300 processors. | |
449 | ||
96a2c332 | 450 | Fujitsu sponsored the support for SPARClite and FR30 processors. |
c906108c SS |
451 | |
452 | Kung Hsu, Jeff Law, and Rick Sladkey added support for hardware | |
453 | watchpoints. | |
454 | ||
455 | Michael Snyder added support for tracepoints. | |
456 | ||
457 | Stu Grossman wrote gdbserver. | |
458 | ||
459 | Jim Kingdon, Peter Schauer, Ian Taylor, and Stu Grossman made | |
96a2c332 | 460 | nearly innumerable bug fixes and cleanups throughout @value{GDBN}. |
c906108c SS |
461 | |
462 | The following people at the Hewlett-Packard Company contributed | |
463 | support for the PA-RISC 2.0 architecture, HP-UX 10.20, 10.30, and 11.0 | |
b37052ae | 464 | (narrow mode), HP's implementation of kernel threads, HP's aC@t{++} |
d0d5df6f AC |
465 | compiler, and the Text User Interface (nee Terminal User Interface): |
466 | Ben Krepp, Richard Title, John Bishop, Susan Macchia, Kathy Mann, | |
467 | Satish Pai, India Paul, Steve Rehrauer, and Elena Zannoni. Kim Haase | |
468 | provided HP-specific information in this manual. | |
c906108c | 469 | |
b37052ae EZ |
470 | DJ Delorie ported @value{GDBN} to MS-DOS, for the DJGPP project. |
471 | Robert Hoehne made significant contributions to the DJGPP port. | |
472 | ||
96a2c332 SS |
473 | Cygnus Solutions has sponsored @value{GDBN} maintenance and much of its |
474 | development since 1991. Cygnus engineers who have worked on @value{GDBN} | |
2df3850c JM |
475 | fulltime include Mark Alexander, Jim Blandy, Per Bothner, Kevin |
476 | Buettner, Edith Epstein, Chris Faylor, Fred Fish, Martin Hunt, Jim | |
477 | Ingham, John Gilmore, Stu Grossman, Kung Hsu, Jim Kingdon, John Metzler, | |
478 | Fernando Nasser, Geoffrey Noer, Dawn Perchik, Rich Pixley, Zdenek | |
479 | Radouch, Keith Seitz, Stan Shebs, David Taylor, and Elena Zannoni. In | |
480 | addition, Dave Brolley, Ian Carmichael, Steve Chamberlain, Nick Clifton, | |
481 | JT Conklin, Stan Cox, DJ Delorie, Ulrich Drepper, Frank Eigler, Doug | |
482 | Evans, Sean Fagan, David Henkel-Wallace, Richard Henderson, Jeff | |
483 | Holcomb, Jeff Law, Jim Lemke, Tom Lord, Bob Manson, Michael Meissner, | |
484 | Jason Merrill, Catherine Moore, Drew Moseley, Ken Raeburn, Gavin | |
485 | Romig-Koch, Rob Savoye, Jamie Smith, Mike Stump, Ian Taylor, Angela | |
486 | Thomas, Michael Tiemann, Tom Tromey, Ron Unrau, Jim Wilson, and David | |
487 | Zuhn have made contributions both large and small. | |
c906108c | 488 | |
ffed4509 AC |
489 | Andrew Cagney, Fernando Nasser, and Elena Zannoni, while working for |
490 | Cygnus Solutions, implemented the original @sc{gdb/mi} interface. | |
491 | ||
e2e0bcd1 JB |
492 | Jim Blandy added support for preprocessor macros, while working for Red |
493 | Hat. | |
c906108c | 494 | |
a9967aef AC |
495 | Andrew Cagney designed @value{GDBN}'s architecture vector. Many |
496 | people including Andrew Cagney, Stephane Carrez, Randolph Chung, Nick | |
497 | Duffek, Richard Henderson, Mark Kettenis, Grace Sainsbury, Kei | |
498 | Sakamoto, Yoshinori Sato, Michael Snyder, Andreas Schwab, Jason | |
499 | Thorpe, Corinna Vinschen, Ulrich Weigand, and Elena Zannoni, helped | |
500 | with the migration of old architectures to this new framework. | |
501 | ||
c5e30d01 AC |
502 | Andrew Cagney completely re-designed and re-implemented @value{GDBN}'s |
503 | unwinder framework, this consisting of a fresh new design featuring | |
504 | frame IDs, independent frame sniffers, and the sentinel frame. Mark | |
505 | Kettenis implemented the @sc{dwarf 2} unwinder, Jeff Johnston the | |
506 | libunwind unwinder, and Andrew Cagney the dummy, sentinel, tramp, and | |
db2e3e2e | 507 | trad unwinders. The architecture-specific changes, each involving a |
c5e30d01 AC |
508 | complete rewrite of the architecture's frame code, were carried out by |
509 | Jim Blandy, Joel Brobecker, Kevin Buettner, Andrew Cagney, Stephane | |
510 | Carrez, Randolph Chung, Orjan Friberg, Richard Henderson, Daniel | |
511 | Jacobowitz, Jeff Johnston, Mark Kettenis, Theodore A. Roth, Kei | |
512 | Sakamoto, Yoshinori Sato, Michael Snyder, Corinna Vinschen, and Ulrich | |
513 | Weigand. | |
514 | ||
ca3bf3bd DJ |
515 | Christian Zankel, Ross Morley, Bob Wilson, and Maxim Grigoriev from |
516 | Tensilica, Inc.@: contributed support for Xtensa processors. Others | |
517 | who have worked on the Xtensa port of @value{GDBN} in the past include | |
518 | Steve Tjiang, John Newlin, and Scott Foehner. | |
519 | ||
08be9d71 ME |
520 | Michael Eager and staff of Xilinx, Inc., contributed support for the |
521 | Xilinx MicroBlaze architecture. | |
522 | ||
6d2ebf8b | 523 | @node Sample Session |
c906108c SS |
524 | @chapter A Sample @value{GDBN} Session |
525 | ||
526 | You can use this manual at your leisure to read all about @value{GDBN}. | |
527 | However, a handful of commands are enough to get started using the | |
528 | debugger. This chapter illustrates those commands. | |
529 | ||
530 | @iftex | |
531 | In this sample session, we emphasize user input like this: @b{input}, | |
532 | to make it easier to pick out from the surrounding output. | |
533 | @end iftex | |
534 | ||
535 | @c FIXME: this example may not be appropriate for some configs, where | |
536 | @c FIXME...primary interest is in remote use. | |
537 | ||
538 | One of the preliminary versions of @sc{gnu} @code{m4} (a generic macro | |
539 | processor) exhibits the following bug: sometimes, when we change its | |
540 | quote strings from the default, the commands used to capture one macro | |
541 | definition within another stop working. In the following short @code{m4} | |
542 | session, we define a macro @code{foo} which expands to @code{0000}; we | |
543 | then use the @code{m4} built-in @code{defn} to define @code{bar} as the | |
544 | same thing. However, when we change the open quote string to | |
545 | @code{<QUOTE>} and the close quote string to @code{<UNQUOTE>}, the same | |
546 | procedure fails to define a new synonym @code{baz}: | |
547 | ||
548 | @smallexample | |
549 | $ @b{cd gnu/m4} | |
550 | $ @b{./m4} | |
551 | @b{define(foo,0000)} | |
552 | ||
553 | @b{foo} | |
554 | 0000 | |
555 | @b{define(bar,defn(`foo'))} | |
556 | ||
557 | @b{bar} | |
558 | 0000 | |
559 | @b{changequote(<QUOTE>,<UNQUOTE>)} | |
560 | ||
561 | @b{define(baz,defn(<QUOTE>foo<UNQUOTE>))} | |
562 | @b{baz} | |
c8aa23ab | 563 | @b{Ctrl-d} |
c906108c SS |
564 | m4: End of input: 0: fatal error: EOF in string |
565 | @end smallexample | |
566 | ||
567 | @noindent | |
568 | Let us use @value{GDBN} to try to see what is going on. | |
569 | ||
c906108c SS |
570 | @smallexample |
571 | $ @b{@value{GDBP} m4} | |
572 | @c FIXME: this falsifies the exact text played out, to permit smallbook | |
573 | @c FIXME... format to come out better. | |
574 | @value{GDBN} is free software and you are welcome to distribute copies | |
5d161b24 | 575 | of it under certain conditions; type "show copying" to see |
c906108c | 576 | the conditions. |
5d161b24 | 577 | There is absolutely no warranty for @value{GDBN}; type "show warranty" |
c906108c SS |
578 | for details. |
579 | ||
580 | @value{GDBN} @value{GDBVN}, Copyright 1999 Free Software Foundation, Inc... | |
581 | (@value{GDBP}) | |
582 | @end smallexample | |
c906108c SS |
583 | |
584 | @noindent | |
585 | @value{GDBN} reads only enough symbol data to know where to find the | |
586 | rest when needed; as a result, the first prompt comes up very quickly. | |
587 | We now tell @value{GDBN} to use a narrower display width than usual, so | |
588 | that examples fit in this manual. | |
589 | ||
590 | @smallexample | |
591 | (@value{GDBP}) @b{set width 70} | |
592 | @end smallexample | |
593 | ||
594 | @noindent | |
595 | We need to see how the @code{m4} built-in @code{changequote} works. | |
596 | Having looked at the source, we know the relevant subroutine is | |
597 | @code{m4_changequote}, so we set a breakpoint there with the @value{GDBN} | |
598 | @code{break} command. | |
599 | ||
600 | @smallexample | |
601 | (@value{GDBP}) @b{break m4_changequote} | |
602 | Breakpoint 1 at 0x62f4: file builtin.c, line 879. | |
603 | @end smallexample | |
604 | ||
605 | @noindent | |
606 | Using the @code{run} command, we start @code{m4} running under @value{GDBN} | |
607 | control; as long as control does not reach the @code{m4_changequote} | |
608 | subroutine, the program runs as usual: | |
609 | ||
610 | @smallexample | |
611 | (@value{GDBP}) @b{run} | |
612 | Starting program: /work/Editorial/gdb/gnu/m4/m4 | |
613 | @b{define(foo,0000)} | |
614 | ||
615 | @b{foo} | |
616 | 0000 | |
617 | @end smallexample | |
618 | ||
619 | @noindent | |
620 | To trigger the breakpoint, we call @code{changequote}. @value{GDBN} | |
621 | suspends execution of @code{m4}, displaying information about the | |
622 | context where it stops. | |
623 | ||
624 | @smallexample | |
625 | @b{changequote(<QUOTE>,<UNQUOTE>)} | |
626 | ||
5d161b24 | 627 | Breakpoint 1, m4_changequote (argc=3, argv=0x33c70) |
c906108c SS |
628 | at builtin.c:879 |
629 | 879 if (bad_argc(TOKEN_DATA_TEXT(argv[0]),argc,1,3)) | |
630 | @end smallexample | |
631 | ||
632 | @noindent | |
633 | Now we use the command @code{n} (@code{next}) to advance execution to | |
634 | the next line of the current function. | |
635 | ||
636 | @smallexample | |
637 | (@value{GDBP}) @b{n} | |
638 | 882 set_quotes((argc >= 2) ? TOKEN_DATA_TEXT(argv[1])\ | |
639 | : nil, | |
640 | @end smallexample | |
641 | ||
642 | @noindent | |
643 | @code{set_quotes} looks like a promising subroutine. We can go into it | |
644 | by using the command @code{s} (@code{step}) instead of @code{next}. | |
645 | @code{step} goes to the next line to be executed in @emph{any} | |
646 | subroutine, so it steps into @code{set_quotes}. | |
647 | ||
648 | @smallexample | |
649 | (@value{GDBP}) @b{s} | |
650 | set_quotes (lq=0x34c78 "<QUOTE>", rq=0x34c88 "<UNQUOTE>") | |
651 | at input.c:530 | |
652 | 530 if (lquote != def_lquote) | |
653 | @end smallexample | |
654 | ||
655 | @noindent | |
656 | The display that shows the subroutine where @code{m4} is now | |
657 | suspended (and its arguments) is called a stack frame display. It | |
658 | shows a summary of the stack. We can use the @code{backtrace} | |
659 | command (which can also be spelled @code{bt}), to see where we are | |
660 | in the stack as a whole: the @code{backtrace} command displays a | |
661 | stack frame for each active subroutine. | |
662 | ||
663 | @smallexample | |
664 | (@value{GDBP}) @b{bt} | |
665 | #0 set_quotes (lq=0x34c78 "<QUOTE>", rq=0x34c88 "<UNQUOTE>") | |
666 | at input.c:530 | |
5d161b24 | 667 | #1 0x6344 in m4_changequote (argc=3, argv=0x33c70) |
c906108c SS |
668 | at builtin.c:882 |
669 | #2 0x8174 in expand_macro (sym=0x33320) at macro.c:242 | |
670 | #3 0x7a88 in expand_token (obs=0x0, t=209696, td=0xf7fffa30) | |
671 | at macro.c:71 | |
672 | #4 0x79dc in expand_input () at macro.c:40 | |
673 | #5 0x2930 in main (argc=0, argv=0xf7fffb20) at m4.c:195 | |
674 | @end smallexample | |
675 | ||
676 | @noindent | |
677 | We step through a few more lines to see what happens. The first two | |
678 | times, we can use @samp{s}; the next two times we use @code{n} to avoid | |
679 | falling into the @code{xstrdup} subroutine. | |
680 | ||
681 | @smallexample | |
682 | (@value{GDBP}) @b{s} | |
683 | 0x3b5c 532 if (rquote != def_rquote) | |
684 | (@value{GDBP}) @b{s} | |
685 | 0x3b80 535 lquote = (lq == nil || *lq == '\0') ? \ | |
686 | def_lquote : xstrdup(lq); | |
687 | (@value{GDBP}) @b{n} | |
688 | 536 rquote = (rq == nil || *rq == '\0') ? def_rquote\ | |
689 | : xstrdup(rq); | |
690 | (@value{GDBP}) @b{n} | |
691 | 538 len_lquote = strlen(rquote); | |
692 | @end smallexample | |
693 | ||
694 | @noindent | |
695 | The last line displayed looks a little odd; we can examine the variables | |
696 | @code{lquote} and @code{rquote} to see if they are in fact the new left | |
697 | and right quotes we specified. We use the command @code{p} | |
698 | (@code{print}) to see their values. | |
699 | ||
700 | @smallexample | |
701 | (@value{GDBP}) @b{p lquote} | |
702 | $1 = 0x35d40 "<QUOTE>" | |
703 | (@value{GDBP}) @b{p rquote} | |
704 | $2 = 0x35d50 "<UNQUOTE>" | |
705 | @end smallexample | |
706 | ||
707 | @noindent | |
708 | @code{lquote} and @code{rquote} are indeed the new left and right quotes. | |
709 | To look at some context, we can display ten lines of source | |
710 | surrounding the current line with the @code{l} (@code{list}) command. | |
711 | ||
712 | @smallexample | |
713 | (@value{GDBP}) @b{l} | |
714 | 533 xfree(rquote); | |
715 | 534 | |
716 | 535 lquote = (lq == nil || *lq == '\0') ? def_lquote\ | |
717 | : xstrdup (lq); | |
718 | 536 rquote = (rq == nil || *rq == '\0') ? def_rquote\ | |
719 | : xstrdup (rq); | |
720 | 537 | |
721 | 538 len_lquote = strlen(rquote); | |
722 | 539 len_rquote = strlen(lquote); | |
723 | 540 @} | |
724 | 541 | |
725 | 542 void | |
726 | @end smallexample | |
727 | ||
728 | @noindent | |
729 | Let us step past the two lines that set @code{len_lquote} and | |
730 | @code{len_rquote}, and then examine the values of those variables. | |
731 | ||
732 | @smallexample | |
733 | (@value{GDBP}) @b{n} | |
734 | 539 len_rquote = strlen(lquote); | |
735 | (@value{GDBP}) @b{n} | |
736 | 540 @} | |
737 | (@value{GDBP}) @b{p len_lquote} | |
738 | $3 = 9 | |
739 | (@value{GDBP}) @b{p len_rquote} | |
740 | $4 = 7 | |
741 | @end smallexample | |
742 | ||
743 | @noindent | |
744 | That certainly looks wrong, assuming @code{len_lquote} and | |
745 | @code{len_rquote} are meant to be the lengths of @code{lquote} and | |
746 | @code{rquote} respectively. We can set them to better values using | |
747 | the @code{p} command, since it can print the value of | |
748 | any expression---and that expression can include subroutine calls and | |
749 | assignments. | |
750 | ||
751 | @smallexample | |
752 | (@value{GDBP}) @b{p len_lquote=strlen(lquote)} | |
753 | $5 = 7 | |
754 | (@value{GDBP}) @b{p len_rquote=strlen(rquote)} | |
755 | $6 = 9 | |
756 | @end smallexample | |
757 | ||
758 | @noindent | |
759 | Is that enough to fix the problem of using the new quotes with the | |
760 | @code{m4} built-in @code{defn}? We can allow @code{m4} to continue | |
761 | executing with the @code{c} (@code{continue}) command, and then try the | |
762 | example that caused trouble initially: | |
763 | ||
764 | @smallexample | |
765 | (@value{GDBP}) @b{c} | |
766 | Continuing. | |
767 | ||
768 | @b{define(baz,defn(<QUOTE>foo<UNQUOTE>))} | |
769 | ||
770 | baz | |
771 | 0000 | |
772 | @end smallexample | |
773 | ||
774 | @noindent | |
775 | Success! The new quotes now work just as well as the default ones. The | |
776 | problem seems to have been just the two typos defining the wrong | |
777 | lengths. We allow @code{m4} exit by giving it an EOF as input: | |
778 | ||
779 | @smallexample | |
c8aa23ab | 780 | @b{Ctrl-d} |
c906108c SS |
781 | Program exited normally. |
782 | @end smallexample | |
783 | ||
784 | @noindent | |
785 | The message @samp{Program exited normally.} is from @value{GDBN}; it | |
786 | indicates @code{m4} has finished executing. We can end our @value{GDBN} | |
787 | session with the @value{GDBN} @code{quit} command. | |
788 | ||
789 | @smallexample | |
790 | (@value{GDBP}) @b{quit} | |
791 | @end smallexample | |
c906108c | 792 | |
6d2ebf8b | 793 | @node Invocation |
c906108c SS |
794 | @chapter Getting In and Out of @value{GDBN} |
795 | ||
796 | This chapter discusses how to start @value{GDBN}, and how to get out of it. | |
5d161b24 | 797 | The essentials are: |
c906108c | 798 | @itemize @bullet |
5d161b24 | 799 | @item |
53a5351d | 800 | type @samp{@value{GDBP}} to start @value{GDBN}. |
5d161b24 | 801 | @item |
c8aa23ab | 802 | type @kbd{quit} or @kbd{Ctrl-d} to exit. |
c906108c SS |
803 | @end itemize |
804 | ||
805 | @menu | |
806 | * Invoking GDB:: How to start @value{GDBN} | |
807 | * Quitting GDB:: How to quit @value{GDBN} | |
808 | * Shell Commands:: How to use shell commands inside @value{GDBN} | |
79a6e687 | 809 | * Logging Output:: How to log @value{GDBN}'s output to a file |
c906108c SS |
810 | @end menu |
811 | ||
6d2ebf8b | 812 | @node Invoking GDB |
c906108c SS |
813 | @section Invoking @value{GDBN} |
814 | ||
c906108c SS |
815 | Invoke @value{GDBN} by running the program @code{@value{GDBP}}. Once started, |
816 | @value{GDBN} reads commands from the terminal until you tell it to exit. | |
817 | ||
818 | You can also run @code{@value{GDBP}} with a variety of arguments and options, | |
819 | to specify more of your debugging environment at the outset. | |
820 | ||
c906108c SS |
821 | The command-line options described here are designed |
822 | to cover a variety of situations; in some environments, some of these | |
5d161b24 | 823 | options may effectively be unavailable. |
c906108c SS |
824 | |
825 | The most usual way to start @value{GDBN} is with one argument, | |
826 | specifying an executable program: | |
827 | ||
474c8240 | 828 | @smallexample |
c906108c | 829 | @value{GDBP} @var{program} |
474c8240 | 830 | @end smallexample |
c906108c | 831 | |
c906108c SS |
832 | @noindent |
833 | You can also start with both an executable program and a core file | |
834 | specified: | |
835 | ||
474c8240 | 836 | @smallexample |
c906108c | 837 | @value{GDBP} @var{program} @var{core} |
474c8240 | 838 | @end smallexample |
c906108c SS |
839 | |
840 | You can, instead, specify a process ID as a second argument, if you want | |
841 | to debug a running process: | |
842 | ||
474c8240 | 843 | @smallexample |
c906108c | 844 | @value{GDBP} @var{program} 1234 |
474c8240 | 845 | @end smallexample |
c906108c SS |
846 | |
847 | @noindent | |
848 | would attach @value{GDBN} to process @code{1234} (unless you also have a file | |
849 | named @file{1234}; @value{GDBN} does check for a core file first). | |
850 | ||
c906108c | 851 | Taking advantage of the second command-line argument requires a fairly |
2df3850c JM |
852 | complete operating system; when you use @value{GDBN} as a remote |
853 | debugger attached to a bare board, there may not be any notion of | |
854 | ``process'', and there is often no way to get a core dump. @value{GDBN} | |
855 | will warn you if it is unable to attach or to read core dumps. | |
c906108c | 856 | |
aa26fa3a TT |
857 | You can optionally have @code{@value{GDBP}} pass any arguments after the |
858 | executable file to the inferior using @code{--args}. This option stops | |
859 | option processing. | |
474c8240 | 860 | @smallexample |
3f94c067 | 861 | @value{GDBP} --args gcc -O2 -c foo.c |
474c8240 | 862 | @end smallexample |
aa26fa3a TT |
863 | This will cause @code{@value{GDBP}} to debug @code{gcc}, and to set |
864 | @code{gcc}'s command-line arguments (@pxref{Arguments}) to @samp{-O2 -c foo.c}. | |
865 | ||
96a2c332 | 866 | You can run @code{@value{GDBP}} without printing the front material, which describes |
c906108c SS |
867 | @value{GDBN}'s non-warranty, by specifying @code{-silent}: |
868 | ||
869 | @smallexample | |
870 | @value{GDBP} -silent | |
871 | @end smallexample | |
872 | ||
873 | @noindent | |
874 | You can further control how @value{GDBN} starts up by using command-line | |
875 | options. @value{GDBN} itself can remind you of the options available. | |
876 | ||
877 | @noindent | |
878 | Type | |
879 | ||
474c8240 | 880 | @smallexample |
c906108c | 881 | @value{GDBP} -help |
474c8240 | 882 | @end smallexample |
c906108c SS |
883 | |
884 | @noindent | |
885 | to display all available options and briefly describe their use | |
886 | (@samp{@value{GDBP} -h} is a shorter equivalent). | |
887 | ||
888 | All options and command line arguments you give are processed | |
889 | in sequential order. The order makes a difference when the | |
890 | @samp{-x} option is used. | |
891 | ||
892 | ||
893 | @menu | |
c906108c SS |
894 | * File Options:: Choosing files |
895 | * Mode Options:: Choosing modes | |
6fc08d32 | 896 | * Startup:: What @value{GDBN} does during startup |
c906108c SS |
897 | @end menu |
898 | ||
6d2ebf8b | 899 | @node File Options |
79a6e687 | 900 | @subsection Choosing Files |
c906108c | 901 | |
2df3850c | 902 | When @value{GDBN} starts, it reads any arguments other than options as |
c906108c SS |
903 | specifying an executable file and core file (or process ID). This is |
904 | the same as if the arguments were specified by the @samp{-se} and | |
d52fb0e9 | 905 | @samp{-c} (or @samp{-p}) options respectively. (@value{GDBN} reads the |
19837790 MS |
906 | first argument that does not have an associated option flag as |
907 | equivalent to the @samp{-se} option followed by that argument; and the | |
908 | second argument that does not have an associated option flag, if any, as | |
909 | equivalent to the @samp{-c}/@samp{-p} option followed by that argument.) | |
910 | If the second argument begins with a decimal digit, @value{GDBN} will | |
911 | first attempt to attach to it as a process, and if that fails, attempt | |
912 | to open it as a corefile. If you have a corefile whose name begins with | |
b383017d | 913 | a digit, you can prevent @value{GDBN} from treating it as a pid by |
c1468174 | 914 | prefixing it with @file{./}, e.g.@: @file{./12345}. |
7a292a7a SS |
915 | |
916 | If @value{GDBN} has not been configured to included core file support, | |
917 | such as for most embedded targets, then it will complain about a second | |
918 | argument and ignore it. | |
c906108c SS |
919 | |
920 | Many options have both long and short forms; both are shown in the | |
921 | following list. @value{GDBN} also recognizes the long forms if you truncate | |
922 | them, so long as enough of the option is present to be unambiguous. | |
923 | (If you prefer, you can flag option arguments with @samp{--} rather | |
924 | than @samp{-}, though we illustrate the more usual convention.) | |
925 | ||
d700128c EZ |
926 | @c NOTE: the @cindex entries here use double dashes ON PURPOSE. This |
927 | @c way, both those who look for -foo and --foo in the index, will find | |
928 | @c it. | |
929 | ||
c906108c SS |
930 | @table @code |
931 | @item -symbols @var{file} | |
932 | @itemx -s @var{file} | |
d700128c EZ |
933 | @cindex @code{--symbols} |
934 | @cindex @code{-s} | |
c906108c SS |
935 | Read symbol table from file @var{file}. |
936 | ||
937 | @item -exec @var{file} | |
938 | @itemx -e @var{file} | |
d700128c EZ |
939 | @cindex @code{--exec} |
940 | @cindex @code{-e} | |
7a292a7a SS |
941 | Use file @var{file} as the executable file to execute when appropriate, |
942 | and for examining pure data in conjunction with a core dump. | |
c906108c SS |
943 | |
944 | @item -se @var{file} | |
d700128c | 945 | @cindex @code{--se} |
c906108c SS |
946 | Read symbol table from file @var{file} and use it as the executable |
947 | file. | |
948 | ||
c906108c SS |
949 | @item -core @var{file} |
950 | @itemx -c @var{file} | |
d700128c EZ |
951 | @cindex @code{--core} |
952 | @cindex @code{-c} | |
b383017d | 953 | Use file @var{file} as a core dump to examine. |
c906108c | 954 | |
19837790 MS |
955 | @item -pid @var{number} |
956 | @itemx -p @var{number} | |
957 | @cindex @code{--pid} | |
958 | @cindex @code{-p} | |
959 | Connect to process ID @var{number}, as with the @code{attach} command. | |
c906108c SS |
960 | |
961 | @item -command @var{file} | |
962 | @itemx -x @var{file} | |
d700128c EZ |
963 | @cindex @code{--command} |
964 | @cindex @code{-x} | |
c906108c SS |
965 | Execute @value{GDBN} commands from file @var{file}. @xref{Command |
966 | Files,, Command files}. | |
967 | ||
8a5a3c82 AS |
968 | @item -eval-command @var{command} |
969 | @itemx -ex @var{command} | |
970 | @cindex @code{--eval-command} | |
971 | @cindex @code{-ex} | |
972 | Execute a single @value{GDBN} command. | |
973 | ||
974 | This option may be used multiple times to call multiple commands. It may | |
975 | also be interleaved with @samp{-command} as required. | |
976 | ||
977 | @smallexample | |
978 | @value{GDBP} -ex 'target sim' -ex 'load' \ | |
979 | -x setbreakpoints -ex 'run' a.out | |
980 | @end smallexample | |
981 | ||
c906108c SS |
982 | @item -directory @var{directory} |
983 | @itemx -d @var{directory} | |
d700128c EZ |
984 | @cindex @code{--directory} |
985 | @cindex @code{-d} | |
4b505b12 | 986 | Add @var{directory} to the path to search for source and script files. |
c906108c | 987 | |
c906108c SS |
988 | @item -r |
989 | @itemx -readnow | |
d700128c EZ |
990 | @cindex @code{--readnow} |
991 | @cindex @code{-r} | |
c906108c SS |
992 | Read each symbol file's entire symbol table immediately, rather than |
993 | the default, which is to read it incrementally as it is needed. | |
994 | This makes startup slower, but makes future operations faster. | |
53a5351d | 995 | |
c906108c SS |
996 | @end table |
997 | ||
6d2ebf8b | 998 | @node Mode Options |
79a6e687 | 999 | @subsection Choosing Modes |
c906108c SS |
1000 | |
1001 | You can run @value{GDBN} in various alternative modes---for example, in | |
1002 | batch mode or quiet mode. | |
1003 | ||
1004 | @table @code | |
1005 | @item -nx | |
1006 | @itemx -n | |
d700128c EZ |
1007 | @cindex @code{--nx} |
1008 | @cindex @code{-n} | |
96565e91 | 1009 | Do not execute commands found in any initialization files. Normally, |
2df3850c JM |
1010 | @value{GDBN} executes the commands in these files after all the command |
1011 | options and arguments have been processed. @xref{Command Files,,Command | |
79a6e687 | 1012 | Files}. |
c906108c SS |
1013 | |
1014 | @item -quiet | |
d700128c | 1015 | @itemx -silent |
c906108c | 1016 | @itemx -q |
d700128c EZ |
1017 | @cindex @code{--quiet} |
1018 | @cindex @code{--silent} | |
1019 | @cindex @code{-q} | |
c906108c SS |
1020 | ``Quiet''. Do not print the introductory and copyright messages. These |
1021 | messages are also suppressed in batch mode. | |
1022 | ||
1023 | @item -batch | |
d700128c | 1024 | @cindex @code{--batch} |
c906108c SS |
1025 | Run in batch mode. Exit with status @code{0} after processing all the |
1026 | command files specified with @samp{-x} (and all commands from | |
1027 | initialization files, if not inhibited with @samp{-n}). Exit with | |
1028 | nonzero status if an error occurs in executing the @value{GDBN} commands | |
1029 | in the command files. | |
1030 | ||
2df3850c JM |
1031 | Batch mode may be useful for running @value{GDBN} as a filter, for |
1032 | example to download and run a program on another computer; in order to | |
1033 | make this more useful, the message | |
c906108c | 1034 | |
474c8240 | 1035 | @smallexample |
c906108c | 1036 | Program exited normally. |
474c8240 | 1037 | @end smallexample |
c906108c SS |
1038 | |
1039 | @noindent | |
2df3850c JM |
1040 | (which is ordinarily issued whenever a program running under |
1041 | @value{GDBN} control terminates) is not issued when running in batch | |
1042 | mode. | |
1043 | ||
1a088d06 AS |
1044 | @item -batch-silent |
1045 | @cindex @code{--batch-silent} | |
1046 | Run in batch mode exactly like @samp{-batch}, but totally silently. All | |
1047 | @value{GDBN} output to @code{stdout} is prevented (@code{stderr} is | |
1048 | unaffected). This is much quieter than @samp{-silent} and would be useless | |
1049 | for an interactive session. | |
1050 | ||
1051 | This is particularly useful when using targets that give @samp{Loading section} | |
1052 | messages, for example. | |
1053 | ||
1054 | Note that targets that give their output via @value{GDBN}, as opposed to | |
1055 | writing directly to @code{stdout}, will also be made silent. | |
1056 | ||
4b0ad762 AS |
1057 | @item -return-child-result |
1058 | @cindex @code{--return-child-result} | |
1059 | The return code from @value{GDBN} will be the return code from the child | |
1060 | process (the process being debugged), with the following exceptions: | |
1061 | ||
1062 | @itemize @bullet | |
1063 | @item | |
1064 | @value{GDBN} exits abnormally. E.g., due to an incorrect argument or an | |
1065 | internal error. In this case the exit code is the same as it would have been | |
1066 | without @samp{-return-child-result}. | |
1067 | @item | |
1068 | The user quits with an explicit value. E.g., @samp{quit 1}. | |
1069 | @item | |
1070 | The child process never runs, or is not allowed to terminate, in which case | |
1071 | the exit code will be -1. | |
1072 | @end itemize | |
1073 | ||
1074 | This option is useful in conjunction with @samp{-batch} or @samp{-batch-silent}, | |
1075 | when @value{GDBN} is being used as a remote program loader or simulator | |
1076 | interface. | |
1077 | ||
2df3850c JM |
1078 | @item -nowindows |
1079 | @itemx -nw | |
d700128c EZ |
1080 | @cindex @code{--nowindows} |
1081 | @cindex @code{-nw} | |
2df3850c | 1082 | ``No windows''. If @value{GDBN} comes with a graphical user interface |
96a2c332 | 1083 | (GUI) built in, then this option tells @value{GDBN} to only use the command-line |
2df3850c JM |
1084 | interface. If no GUI is available, this option has no effect. |
1085 | ||
1086 | @item -windows | |
1087 | @itemx -w | |
d700128c EZ |
1088 | @cindex @code{--windows} |
1089 | @cindex @code{-w} | |
2df3850c JM |
1090 | If @value{GDBN} includes a GUI, then this option requires it to be |
1091 | used if possible. | |
c906108c SS |
1092 | |
1093 | @item -cd @var{directory} | |
d700128c | 1094 | @cindex @code{--cd} |
c906108c SS |
1095 | Run @value{GDBN} using @var{directory} as its working directory, |
1096 | instead of the current directory. | |
1097 | ||
c906108c SS |
1098 | @item -fullname |
1099 | @itemx -f | |
d700128c EZ |
1100 | @cindex @code{--fullname} |
1101 | @cindex @code{-f} | |
7a292a7a SS |
1102 | @sc{gnu} Emacs sets this option when it runs @value{GDBN} as a |
1103 | subprocess. It tells @value{GDBN} to output the full file name and line | |
1104 | number in a standard, recognizable fashion each time a stack frame is | |
1105 | displayed (which includes each time your program stops). This | |
1106 | recognizable format looks like two @samp{\032} characters, followed by | |
1107 | the file name, line number and character position separated by colons, | |
1108 | and a newline. The Emacs-to-@value{GDBN} interface program uses the two | |
1109 | @samp{\032} characters as a signal to display the source code for the | |
1110 | frame. | |
c906108c | 1111 | |
d700128c EZ |
1112 | @item -epoch |
1113 | @cindex @code{--epoch} | |
1114 | The Epoch Emacs-@value{GDBN} interface sets this option when it runs | |
1115 | @value{GDBN} as a subprocess. It tells @value{GDBN} to modify its print | |
1116 | routines so as to allow Epoch to display values of expressions in a | |
1117 | separate window. | |
1118 | ||
1119 | @item -annotate @var{level} | |
1120 | @cindex @code{--annotate} | |
1121 | This option sets the @dfn{annotation level} inside @value{GDBN}. Its | |
1122 | effect is identical to using @samp{set annotate @var{level}} | |
086432e2 AC |
1123 | (@pxref{Annotations}). The annotation @var{level} controls how much |
1124 | information @value{GDBN} prints together with its prompt, values of | |
1125 | expressions, source lines, and other types of output. Level 0 is the | |
1126 | normal, level 1 is for use when @value{GDBN} is run as a subprocess of | |
1127 | @sc{gnu} Emacs, level 3 is the maximum annotation suitable for programs | |
1128 | that control @value{GDBN}, and level 2 has been deprecated. | |
1129 | ||
265eeb58 | 1130 | The annotation mechanism has largely been superseded by @sc{gdb/mi} |
086432e2 | 1131 | (@pxref{GDB/MI}). |
d700128c | 1132 | |
aa26fa3a TT |
1133 | @item --args |
1134 | @cindex @code{--args} | |
1135 | Change interpretation of command line so that arguments following the | |
1136 | executable file are passed as command line arguments to the inferior. | |
1137 | This option stops option processing. | |
1138 | ||
2df3850c JM |
1139 | @item -baud @var{bps} |
1140 | @itemx -b @var{bps} | |
d700128c EZ |
1141 | @cindex @code{--baud} |
1142 | @cindex @code{-b} | |
c906108c SS |
1143 | Set the line speed (baud rate or bits per second) of any serial |
1144 | interface used by @value{GDBN} for remote debugging. | |
c906108c | 1145 | |
f47b1503 AS |
1146 | @item -l @var{timeout} |
1147 | @cindex @code{-l} | |
1148 | Set the timeout (in seconds) of any communication used by @value{GDBN} | |
1149 | for remote debugging. | |
1150 | ||
c906108c | 1151 | @item -tty @var{device} |
d700128c EZ |
1152 | @itemx -t @var{device} |
1153 | @cindex @code{--tty} | |
1154 | @cindex @code{-t} | |
c906108c SS |
1155 | Run using @var{device} for your program's standard input and output. |
1156 | @c FIXME: kingdon thinks there is more to -tty. Investigate. | |
c906108c | 1157 | |
53a5351d | 1158 | @c resolve the situation of these eventually |
c4555f82 SC |
1159 | @item -tui |
1160 | @cindex @code{--tui} | |
d0d5df6f AC |
1161 | Activate the @dfn{Text User Interface} when starting. The Text User |
1162 | Interface manages several text windows on the terminal, showing | |
1163 | source, assembly, registers and @value{GDBN} command outputs | |
1164 | (@pxref{TUI, ,@value{GDBN} Text User Interface}). Alternatively, the | |
1165 | Text User Interface can be enabled by invoking the program | |
46ba6afa | 1166 | @samp{@value{GDBTUI}}. Do not use this option if you run @value{GDBN} from |
d0d5df6f | 1167 | Emacs (@pxref{Emacs, ,Using @value{GDBN} under @sc{gnu} Emacs}). |
53a5351d JM |
1168 | |
1169 | @c @item -xdb | |
d700128c | 1170 | @c @cindex @code{--xdb} |
53a5351d JM |
1171 | @c Run in XDB compatibility mode, allowing the use of certain XDB commands. |
1172 | @c For information, see the file @file{xdb_trans.html}, which is usually | |
1173 | @c installed in the directory @code{/opt/langtools/wdb/doc} on HP-UX | |
1174 | @c systems. | |
1175 | ||
d700128c EZ |
1176 | @item -interpreter @var{interp} |
1177 | @cindex @code{--interpreter} | |
1178 | Use the interpreter @var{interp} for interface with the controlling | |
1179 | program or device. This option is meant to be set by programs which | |
94bbb2c0 | 1180 | communicate with @value{GDBN} using it as a back end. |
21c294e6 | 1181 | @xref{Interpreters, , Command Interpreters}. |
94bbb2c0 | 1182 | |
da0f9dcd | 1183 | @samp{--interpreter=mi} (or @samp{--interpreter=mi2}) causes |
2fcf52f0 | 1184 | @value{GDBN} to use the @dfn{@sc{gdb/mi} interface} (@pxref{GDB/MI, , |
6b5e8c01 | 1185 | The @sc{gdb/mi} Interface}) included since @value{GDBN} version 6.0. The |
6c74ac8b AC |
1186 | previous @sc{gdb/mi} interface, included in @value{GDBN} version 5.3 and |
1187 | selected with @samp{--interpreter=mi1}, is deprecated. Earlier | |
1188 | @sc{gdb/mi} interfaces are no longer supported. | |
d700128c EZ |
1189 | |
1190 | @item -write | |
1191 | @cindex @code{--write} | |
1192 | Open the executable and core files for both reading and writing. This | |
1193 | is equivalent to the @samp{set write on} command inside @value{GDBN} | |
1194 | (@pxref{Patching}). | |
1195 | ||
1196 | @item -statistics | |
1197 | @cindex @code{--statistics} | |
1198 | This option causes @value{GDBN} to print statistics about time and | |
1199 | memory usage after it completes each command and returns to the prompt. | |
1200 | ||
1201 | @item -version | |
1202 | @cindex @code{--version} | |
1203 | This option causes @value{GDBN} to print its version number and | |
1204 | no-warranty blurb, and exit. | |
1205 | ||
c906108c SS |
1206 | @end table |
1207 | ||
6fc08d32 | 1208 | @node Startup |
79a6e687 | 1209 | @subsection What @value{GDBN} Does During Startup |
6fc08d32 EZ |
1210 | @cindex @value{GDBN} startup |
1211 | ||
1212 | Here's the description of what @value{GDBN} does during session startup: | |
1213 | ||
1214 | @enumerate | |
1215 | @item | |
1216 | Sets up the command interpreter as specified by the command line | |
1217 | (@pxref{Mode Options, interpreter}). | |
1218 | ||
1219 | @item | |
1220 | @cindex init file | |
098b41a6 JG |
1221 | Reads the system-wide @dfn{init file} (if @option{--with-system-gdbinit} was |
1222 | used when building @value{GDBN}; @pxref{System-wide configuration, | |
1223 | ,System-wide configuration and settings}) and executes all the commands in | |
1224 | that file. | |
1225 | ||
1226 | @item | |
1227 | Reads the init file (if any) in your home directory@footnote{On | |
6fc08d32 EZ |
1228 | DOS/Windows systems, the home directory is the one pointed to by the |
1229 | @code{HOME} environment variable.} and executes all the commands in | |
1230 | that file. | |
1231 | ||
1232 | @item | |
1233 | Processes command line options and operands. | |
1234 | ||
1235 | @item | |
1236 | Reads and executes the commands from init file (if any) in the current | |
119b882a EZ |
1237 | working directory. This is only done if the current directory is |
1238 | different from your home directory. Thus, you can have more than one | |
1239 | init file, one generic in your home directory, and another, specific | |
1240 | to the program you are debugging, in the directory where you invoke | |
6fc08d32 EZ |
1241 | @value{GDBN}. |
1242 | ||
1243 | @item | |
1244 | Reads command files specified by the @samp{-x} option. @xref{Command | |
1245 | Files}, for more details about @value{GDBN} command files. | |
1246 | ||
1247 | @item | |
1248 | Reads the command history recorded in the @dfn{history file}. | |
d620b259 | 1249 | @xref{Command History}, for more details about the command history and the |
6fc08d32 EZ |
1250 | files where @value{GDBN} records it. |
1251 | @end enumerate | |
1252 | ||
1253 | Init files use the same syntax as @dfn{command files} (@pxref{Command | |
1254 | Files}) and are processed by @value{GDBN} in the same way. The init | |
1255 | file in your home directory can set options (such as @samp{set | |
1256 | complaints}) that affect subsequent processing of command line options | |
1257 | and operands. Init files are not executed if you use the @samp{-nx} | |
79a6e687 | 1258 | option (@pxref{Mode Options, ,Choosing Modes}). |
6fc08d32 | 1259 | |
098b41a6 JG |
1260 | To display the list of init files loaded by gdb at startup, you |
1261 | can use @kbd{gdb --help}. | |
1262 | ||
6fc08d32 EZ |
1263 | @cindex init file name |
1264 | @cindex @file{.gdbinit} | |
119b882a | 1265 | @cindex @file{gdb.ini} |
8807d78b | 1266 | The @value{GDBN} init files are normally called @file{.gdbinit}. |
119b882a EZ |
1267 | The DJGPP port of @value{GDBN} uses the name @file{gdb.ini}, due to |
1268 | the limitations of file names imposed by DOS filesystems. The Windows | |
1269 | ports of @value{GDBN} use the standard name, but if they find a | |
1270 | @file{gdb.ini} file, they warn you about that and suggest to rename | |
1271 | the file to the standard name. | |
1272 | ||
6fc08d32 | 1273 | |
6d2ebf8b | 1274 | @node Quitting GDB |
c906108c SS |
1275 | @section Quitting @value{GDBN} |
1276 | @cindex exiting @value{GDBN} | |
1277 | @cindex leaving @value{GDBN} | |
1278 | ||
1279 | @table @code | |
1280 | @kindex quit @r{[}@var{expression}@r{]} | |
41afff9a | 1281 | @kindex q @r{(@code{quit})} |
96a2c332 SS |
1282 | @item quit @r{[}@var{expression}@r{]} |
1283 | @itemx q | |
1284 | To exit @value{GDBN}, use the @code{quit} command (abbreviated | |
c8aa23ab | 1285 | @code{q}), or type an end-of-file character (usually @kbd{Ctrl-d}). If you |
96a2c332 SS |
1286 | do not supply @var{expression}, @value{GDBN} will terminate normally; |
1287 | otherwise it will terminate using the result of @var{expression} as the | |
1288 | error code. | |
c906108c SS |
1289 | @end table |
1290 | ||
1291 | @cindex interrupt | |
c8aa23ab | 1292 | An interrupt (often @kbd{Ctrl-c}) does not exit from @value{GDBN}, but rather |
c906108c SS |
1293 | terminates the action of any @value{GDBN} command that is in progress and |
1294 | returns to @value{GDBN} command level. It is safe to type the interrupt | |
1295 | character at any time because @value{GDBN} does not allow it to take effect | |
1296 | until a time when it is safe. | |
1297 | ||
c906108c SS |
1298 | If you have been using @value{GDBN} to control an attached process or |
1299 | device, you can release it with the @code{detach} command | |
79a6e687 | 1300 | (@pxref{Attach, ,Debugging an Already-running Process}). |
c906108c | 1301 | |
6d2ebf8b | 1302 | @node Shell Commands |
79a6e687 | 1303 | @section Shell Commands |
c906108c SS |
1304 | |
1305 | If you need to execute occasional shell commands during your | |
1306 | debugging session, there is no need to leave or suspend @value{GDBN}; you can | |
1307 | just use the @code{shell} command. | |
1308 | ||
1309 | @table @code | |
1310 | @kindex shell | |
1311 | @cindex shell escape | |
1312 | @item shell @var{command string} | |
1313 | Invoke a standard shell to execute @var{command string}. | |
c906108c | 1314 | If it exists, the environment variable @code{SHELL} determines which |
d4f3574e SS |
1315 | shell to run. Otherwise @value{GDBN} uses the default shell |
1316 | (@file{/bin/sh} on Unix systems, @file{COMMAND.COM} on MS-DOS, etc.). | |
c906108c SS |
1317 | @end table |
1318 | ||
1319 | The utility @code{make} is often needed in development environments. | |
1320 | You do not have to use the @code{shell} command for this purpose in | |
1321 | @value{GDBN}: | |
1322 | ||
1323 | @table @code | |
1324 | @kindex make | |
1325 | @cindex calling make | |
1326 | @item make @var{make-args} | |
1327 | Execute the @code{make} program with the specified | |
1328 | arguments. This is equivalent to @samp{shell make @var{make-args}}. | |
1329 | @end table | |
1330 | ||
79a6e687 BW |
1331 | @node Logging Output |
1332 | @section Logging Output | |
0fac0b41 | 1333 | @cindex logging @value{GDBN} output |
9c16f35a | 1334 | @cindex save @value{GDBN} output to a file |
0fac0b41 DJ |
1335 | |
1336 | You may want to save the output of @value{GDBN} commands to a file. | |
1337 | There are several commands to control @value{GDBN}'s logging. | |
1338 | ||
1339 | @table @code | |
1340 | @kindex set logging | |
1341 | @item set logging on | |
1342 | Enable logging. | |
1343 | @item set logging off | |
1344 | Disable logging. | |
9c16f35a | 1345 | @cindex logging file name |
0fac0b41 DJ |
1346 | @item set logging file @var{file} |
1347 | Change the name of the current logfile. The default logfile is @file{gdb.txt}. | |
1348 | @item set logging overwrite [on|off] | |
1349 | By default, @value{GDBN} will append to the logfile. Set @code{overwrite} if | |
1350 | you want @code{set logging on} to overwrite the logfile instead. | |
1351 | @item set logging redirect [on|off] | |
1352 | By default, @value{GDBN} output will go to both the terminal and the logfile. | |
1353 | Set @code{redirect} if you want output to go only to the log file. | |
1354 | @kindex show logging | |
1355 | @item show logging | |
1356 | Show the current values of the logging settings. | |
1357 | @end table | |
1358 | ||
6d2ebf8b | 1359 | @node Commands |
c906108c SS |
1360 | @chapter @value{GDBN} Commands |
1361 | ||
1362 | You can abbreviate a @value{GDBN} command to the first few letters of the command | |
1363 | name, if that abbreviation is unambiguous; and you can repeat certain | |
1364 | @value{GDBN} commands by typing just @key{RET}. You can also use the @key{TAB} | |
1365 | key to get @value{GDBN} to fill out the rest of a word in a command (or to | |
1366 | show you the alternatives available, if there is more than one possibility). | |
1367 | ||
1368 | @menu | |
1369 | * Command Syntax:: How to give commands to @value{GDBN} | |
1370 | * Completion:: Command completion | |
1371 | * Help:: How to ask @value{GDBN} for help | |
1372 | @end menu | |
1373 | ||
6d2ebf8b | 1374 | @node Command Syntax |
79a6e687 | 1375 | @section Command Syntax |
c906108c SS |
1376 | |
1377 | A @value{GDBN} command is a single line of input. There is no limit on | |
1378 | how long it can be. It starts with a command name, which is followed by | |
1379 | arguments whose meaning depends on the command name. For example, the | |
1380 | command @code{step} accepts an argument which is the number of times to | |
1381 | step, as in @samp{step 5}. You can also use the @code{step} command | |
96a2c332 | 1382 | with no arguments. Some commands do not allow any arguments. |
c906108c SS |
1383 | |
1384 | @cindex abbreviation | |
1385 | @value{GDBN} command names may always be truncated if that abbreviation is | |
1386 | unambiguous. Other possible command abbreviations are listed in the | |
1387 | documentation for individual commands. In some cases, even ambiguous | |
1388 | abbreviations are allowed; for example, @code{s} is specially defined as | |
1389 | equivalent to @code{step} even though there are other commands whose | |
1390 | names start with @code{s}. You can test abbreviations by using them as | |
1391 | arguments to the @code{help} command. | |
1392 | ||
1393 | @cindex repeating commands | |
41afff9a | 1394 | @kindex RET @r{(repeat last command)} |
c906108c | 1395 | A blank line as input to @value{GDBN} (typing just @key{RET}) means to |
96a2c332 | 1396 | repeat the previous command. Certain commands (for example, @code{run}) |
c906108c SS |
1397 | will not repeat this way; these are commands whose unintentional |
1398 | repetition might cause trouble and which you are unlikely to want to | |
c45da7e6 EZ |
1399 | repeat. User-defined commands can disable this feature; see |
1400 | @ref{Define, dont-repeat}. | |
c906108c SS |
1401 | |
1402 | The @code{list} and @code{x} commands, when you repeat them with | |
1403 | @key{RET}, construct new arguments rather than repeating | |
1404 | exactly as typed. This permits easy scanning of source or memory. | |
1405 | ||
1406 | @value{GDBN} can also use @key{RET} in another way: to partition lengthy | |
1407 | output, in a way similar to the common utility @code{more} | |
79a6e687 | 1408 | (@pxref{Screen Size,,Screen Size}). Since it is easy to press one |
c906108c SS |
1409 | @key{RET} too many in this situation, @value{GDBN} disables command |
1410 | repetition after any command that generates this sort of display. | |
1411 | ||
41afff9a | 1412 | @kindex # @r{(a comment)} |
c906108c SS |
1413 | @cindex comment |
1414 | Any text from a @kbd{#} to the end of the line is a comment; it does | |
1415 | nothing. This is useful mainly in command files (@pxref{Command | |
79a6e687 | 1416 | Files,,Command Files}). |
c906108c | 1417 | |
88118b3a | 1418 | @cindex repeating command sequences |
c8aa23ab EZ |
1419 | @kindex Ctrl-o @r{(operate-and-get-next)} |
1420 | The @kbd{Ctrl-o} binding is useful for repeating a complex sequence of | |
7f9087cb | 1421 | commands. This command accepts the current line, like @key{RET}, and |
88118b3a TT |
1422 | then fetches the next line relative to the current line from the history |
1423 | for editing. | |
1424 | ||
6d2ebf8b | 1425 | @node Completion |
79a6e687 | 1426 | @section Command Completion |
c906108c SS |
1427 | |
1428 | @cindex completion | |
1429 | @cindex word completion | |
1430 | @value{GDBN} can fill in the rest of a word in a command for you, if there is | |
1431 | only one possibility; it can also show you what the valid possibilities | |
1432 | are for the next word in a command, at any time. This works for @value{GDBN} | |
1433 | commands, @value{GDBN} subcommands, and the names of symbols in your program. | |
1434 | ||
1435 | Press the @key{TAB} key whenever you want @value{GDBN} to fill out the rest | |
1436 | of a word. If there is only one possibility, @value{GDBN} fills in the | |
1437 | word, and waits for you to finish the command (or press @key{RET} to | |
1438 | enter it). For example, if you type | |
1439 | ||
1440 | @c FIXME "@key" does not distinguish its argument sufficiently to permit | |
1441 | @c complete accuracy in these examples; space introduced for clarity. | |
1442 | @c If texinfo enhancements make it unnecessary, it would be nice to | |
1443 | @c replace " @key" by "@key" in the following... | |
474c8240 | 1444 | @smallexample |
c906108c | 1445 | (@value{GDBP}) info bre @key{TAB} |
474c8240 | 1446 | @end smallexample |
c906108c SS |
1447 | |
1448 | @noindent | |
1449 | @value{GDBN} fills in the rest of the word @samp{breakpoints}, since that is | |
1450 | the only @code{info} subcommand beginning with @samp{bre}: | |
1451 | ||
474c8240 | 1452 | @smallexample |
c906108c | 1453 | (@value{GDBP}) info breakpoints |
474c8240 | 1454 | @end smallexample |
c906108c SS |
1455 | |
1456 | @noindent | |
1457 | You can either press @key{RET} at this point, to run the @code{info | |
1458 | breakpoints} command, or backspace and enter something else, if | |
1459 | @samp{breakpoints} does not look like the command you expected. (If you | |
1460 | were sure you wanted @code{info breakpoints} in the first place, you | |
1461 | might as well just type @key{RET} immediately after @samp{info bre}, | |
1462 | to exploit command abbreviations rather than command completion). | |
1463 | ||
1464 | If there is more than one possibility for the next word when you press | |
1465 | @key{TAB}, @value{GDBN} sounds a bell. You can either supply more | |
1466 | characters and try again, or just press @key{TAB} a second time; | |
1467 | @value{GDBN} displays all the possible completions for that word. For | |
1468 | example, you might want to set a breakpoint on a subroutine whose name | |
1469 | begins with @samp{make_}, but when you type @kbd{b make_@key{TAB}} @value{GDBN} | |
1470 | just sounds the bell. Typing @key{TAB} again displays all the | |
1471 | function names in your program that begin with those characters, for | |
1472 | example: | |
1473 | ||
474c8240 | 1474 | @smallexample |
c906108c SS |
1475 | (@value{GDBP}) b make_ @key{TAB} |
1476 | @exdent @value{GDBN} sounds bell; press @key{TAB} again, to see: | |
5d161b24 DB |
1477 | make_a_section_from_file make_environ |
1478 | make_abs_section make_function_type | |
1479 | make_blockvector make_pointer_type | |
1480 | make_cleanup make_reference_type | |
c906108c SS |
1481 | make_command make_symbol_completion_list |
1482 | (@value{GDBP}) b make_ | |
474c8240 | 1483 | @end smallexample |
c906108c SS |
1484 | |
1485 | @noindent | |
1486 | After displaying the available possibilities, @value{GDBN} copies your | |
1487 | partial input (@samp{b make_} in the example) so you can finish the | |
1488 | command. | |
1489 | ||
1490 | If you just want to see the list of alternatives in the first place, you | |
b37052ae | 1491 | can press @kbd{M-?} rather than pressing @key{TAB} twice. @kbd{M-?} |
7a292a7a | 1492 | means @kbd{@key{META} ?}. You can type this either by holding down a |
c906108c | 1493 | key designated as the @key{META} shift on your keyboard (if there is |
7a292a7a | 1494 | one) while typing @kbd{?}, or as @key{ESC} followed by @kbd{?}. |
c906108c SS |
1495 | |
1496 | @cindex quotes in commands | |
1497 | @cindex completion of quoted strings | |
1498 | Sometimes the string you need, while logically a ``word'', may contain | |
7a292a7a SS |
1499 | parentheses or other characters that @value{GDBN} normally excludes from |
1500 | its notion of a word. To permit word completion to work in this | |
1501 | situation, you may enclose words in @code{'} (single quote marks) in | |
1502 | @value{GDBN} commands. | |
c906108c | 1503 | |
c906108c | 1504 | The most likely situation where you might need this is in typing the |
b37052ae EZ |
1505 | name of a C@t{++} function. This is because C@t{++} allows function |
1506 | overloading (multiple definitions of the same function, distinguished | |
1507 | by argument type). For example, when you want to set a breakpoint you | |
1508 | may need to distinguish whether you mean the version of @code{name} | |
1509 | that takes an @code{int} parameter, @code{name(int)}, or the version | |
1510 | that takes a @code{float} parameter, @code{name(float)}. To use the | |
1511 | word-completion facilities in this situation, type a single quote | |
1512 | @code{'} at the beginning of the function name. This alerts | |
1513 | @value{GDBN} that it may need to consider more information than usual | |
1514 | when you press @key{TAB} or @kbd{M-?} to request word completion: | |
c906108c | 1515 | |
474c8240 | 1516 | @smallexample |
96a2c332 | 1517 | (@value{GDBP}) b 'bubble( @kbd{M-?} |
c906108c SS |
1518 | bubble(double,double) bubble(int,int) |
1519 | (@value{GDBP}) b 'bubble( | |
474c8240 | 1520 | @end smallexample |
c906108c SS |
1521 | |
1522 | In some cases, @value{GDBN} can tell that completing a name requires using | |
1523 | quotes. When this happens, @value{GDBN} inserts the quote for you (while | |
1524 | completing as much as it can) if you do not type the quote in the first | |
1525 | place: | |
1526 | ||
474c8240 | 1527 | @smallexample |
c906108c SS |
1528 | (@value{GDBP}) b bub @key{TAB} |
1529 | @exdent @value{GDBN} alters your input line to the following, and rings a bell: | |
1530 | (@value{GDBP}) b 'bubble( | |
474c8240 | 1531 | @end smallexample |
c906108c SS |
1532 | |
1533 | @noindent | |
1534 | In general, @value{GDBN} can tell that a quote is needed (and inserts it) if | |
1535 | you have not yet started typing the argument list when you ask for | |
1536 | completion on an overloaded symbol. | |
1537 | ||
79a6e687 BW |
1538 | For more information about overloaded functions, see @ref{C Plus Plus |
1539 | Expressions, ,C@t{++} Expressions}. You can use the command @code{set | |
c906108c | 1540 | overload-resolution off} to disable overload resolution; |
79a6e687 | 1541 | see @ref{Debugging C Plus Plus, ,@value{GDBN} Features for C@t{++}}. |
c906108c | 1542 | |
65d12d83 TT |
1543 | @cindex completion of structure field names |
1544 | @cindex structure field name completion | |
1545 | @cindex completion of union field names | |
1546 | @cindex union field name completion | |
1547 | When completing in an expression which looks up a field in a | |
1548 | structure, @value{GDBN} also tries@footnote{The completer can be | |
1549 | confused by certain kinds of invalid expressions. Also, it only | |
1550 | examines the static type of the expression, not the dynamic type.} to | |
1551 | limit completions to the field names available in the type of the | |
1552 | left-hand-side: | |
1553 | ||
1554 | @smallexample | |
1555 | (@value{GDBP}) p gdb_stdout.@kbd{M-?} | |
1556 | magic to_delete to_fputs to_put to_rewind | |
1557 | to_data to_flush to_isatty to_read to_write | |
1558 | @end smallexample | |
1559 | ||
1560 | @noindent | |
1561 | This is because the @code{gdb_stdout} is a variable of the type | |
1562 | @code{struct ui_file} that is defined in @value{GDBN} sources as | |
1563 | follows: | |
1564 | ||
1565 | @smallexample | |
1566 | struct ui_file | |
1567 | @{ | |
1568 | int *magic; | |
1569 | ui_file_flush_ftype *to_flush; | |
1570 | ui_file_write_ftype *to_write; | |
1571 | ui_file_fputs_ftype *to_fputs; | |
1572 | ui_file_read_ftype *to_read; | |
1573 | ui_file_delete_ftype *to_delete; | |
1574 | ui_file_isatty_ftype *to_isatty; | |
1575 | ui_file_rewind_ftype *to_rewind; | |
1576 | ui_file_put_ftype *to_put; | |
1577 | void *to_data; | |
1578 | @} | |
1579 | @end smallexample | |
1580 | ||
c906108c | 1581 | |
6d2ebf8b | 1582 | @node Help |
79a6e687 | 1583 | @section Getting Help |
c906108c SS |
1584 | @cindex online documentation |
1585 | @kindex help | |
1586 | ||
5d161b24 | 1587 | You can always ask @value{GDBN} itself for information on its commands, |
c906108c SS |
1588 | using the command @code{help}. |
1589 | ||
1590 | @table @code | |
41afff9a | 1591 | @kindex h @r{(@code{help})} |
c906108c SS |
1592 | @item help |
1593 | @itemx h | |
1594 | You can use @code{help} (abbreviated @code{h}) with no arguments to | |
1595 | display a short list of named classes of commands: | |
1596 | ||
1597 | @smallexample | |
1598 | (@value{GDBP}) help | |
1599 | List of classes of commands: | |
1600 | ||
2df3850c | 1601 | aliases -- Aliases of other commands |
c906108c | 1602 | breakpoints -- Making program stop at certain points |
2df3850c | 1603 | data -- Examining data |
c906108c | 1604 | files -- Specifying and examining files |
2df3850c JM |
1605 | internals -- Maintenance commands |
1606 | obscure -- Obscure features | |
1607 | running -- Running the program | |
1608 | stack -- Examining the stack | |
c906108c SS |
1609 | status -- Status inquiries |
1610 | support -- Support facilities | |
12c27660 | 1611 | tracepoints -- Tracing of program execution without |
96a2c332 | 1612 | stopping the program |
c906108c | 1613 | user-defined -- User-defined commands |
c906108c | 1614 | |
5d161b24 | 1615 | Type "help" followed by a class name for a list of |
c906108c | 1616 | commands in that class. |
5d161b24 | 1617 | Type "help" followed by command name for full |
c906108c SS |
1618 | documentation. |
1619 | Command name abbreviations are allowed if unambiguous. | |
1620 | (@value{GDBP}) | |
1621 | @end smallexample | |
96a2c332 | 1622 | @c the above line break eliminates huge line overfull... |
c906108c SS |
1623 | |
1624 | @item help @var{class} | |
1625 | Using one of the general help classes as an argument, you can get a | |
1626 | list of the individual commands in that class. For example, here is the | |
1627 | help display for the class @code{status}: | |
1628 | ||
1629 | @smallexample | |
1630 | (@value{GDBP}) help status | |
1631 | Status inquiries. | |
1632 | ||
1633 | List of commands: | |
1634 | ||
1635 | @c Line break in "show" line falsifies real output, but needed | |
1636 | @c to fit in smallbook page size. | |
2df3850c | 1637 | info -- Generic command for showing things |
12c27660 | 1638 | about the program being debugged |
2df3850c | 1639 | show -- Generic command for showing things |
12c27660 | 1640 | about the debugger |
c906108c | 1641 | |
5d161b24 | 1642 | Type "help" followed by command name for full |
c906108c SS |
1643 | documentation. |
1644 | Command name abbreviations are allowed if unambiguous. | |
1645 | (@value{GDBP}) | |
1646 | @end smallexample | |
1647 | ||
1648 | @item help @var{command} | |
1649 | With a command name as @code{help} argument, @value{GDBN} displays a | |
1650 | short paragraph on how to use that command. | |
1651 | ||
6837a0a2 DB |
1652 | @kindex apropos |
1653 | @item apropos @var{args} | |
09d4efe1 | 1654 | The @code{apropos} command searches through all of the @value{GDBN} |
6837a0a2 | 1655 | commands, and their documentation, for the regular expression specified in |
99e008fe | 1656 | @var{args}. It prints out all matches found. For example: |
6837a0a2 DB |
1657 | |
1658 | @smallexample | |
1659 | apropos reload | |
1660 | @end smallexample | |
1661 | ||
b37052ae EZ |
1662 | @noindent |
1663 | results in: | |
6837a0a2 DB |
1664 | |
1665 | @smallexample | |
6d2ebf8b SS |
1666 | @c @group |
1667 | set symbol-reloading -- Set dynamic symbol table reloading | |
12c27660 | 1668 | multiple times in one run |
6d2ebf8b | 1669 | show symbol-reloading -- Show dynamic symbol table reloading |
12c27660 | 1670 | multiple times in one run |
6d2ebf8b | 1671 | @c @end group |
6837a0a2 DB |
1672 | @end smallexample |
1673 | ||
c906108c SS |
1674 | @kindex complete |
1675 | @item complete @var{args} | |
1676 | The @code{complete @var{args}} command lists all the possible completions | |
1677 | for the beginning of a command. Use @var{args} to specify the beginning of the | |
1678 | command you want completed. For example: | |
1679 | ||
1680 | @smallexample | |
1681 | complete i | |
1682 | @end smallexample | |
1683 | ||
1684 | @noindent results in: | |
1685 | ||
1686 | @smallexample | |
1687 | @group | |
2df3850c JM |
1688 | if |
1689 | ignore | |
c906108c SS |
1690 | info |
1691 | inspect | |
c906108c SS |
1692 | @end group |
1693 | @end smallexample | |
1694 | ||
1695 | @noindent This is intended for use by @sc{gnu} Emacs. | |
1696 | @end table | |
1697 | ||
1698 | In addition to @code{help}, you can use the @value{GDBN} commands @code{info} | |
1699 | and @code{show} to inquire about the state of your program, or the state | |
1700 | of @value{GDBN} itself. Each command supports many topics of inquiry; this | |
1701 | manual introduces each of them in the appropriate context. The listings | |
1702 | under @code{info} and under @code{show} in the Index point to | |
1703 | all the sub-commands. @xref{Index}. | |
1704 | ||
1705 | @c @group | |
1706 | @table @code | |
1707 | @kindex info | |
41afff9a | 1708 | @kindex i @r{(@code{info})} |
c906108c SS |
1709 | @item info |
1710 | This command (abbreviated @code{i}) is for describing the state of your | |
cda4ce5a | 1711 | program. For example, you can show the arguments passed to a function |
c906108c SS |
1712 | with @code{info args}, list the registers currently in use with @code{info |
1713 | registers}, or list the breakpoints you have set with @code{info breakpoints}. | |
1714 | You can get a complete list of the @code{info} sub-commands with | |
1715 | @w{@code{help info}}. | |
1716 | ||
1717 | @kindex set | |
1718 | @item set | |
5d161b24 | 1719 | You can assign the result of an expression to an environment variable with |
c906108c SS |
1720 | @code{set}. For example, you can set the @value{GDBN} prompt to a $-sign with |
1721 | @code{set prompt $}. | |
1722 | ||
1723 | @kindex show | |
1724 | @item show | |
5d161b24 | 1725 | In contrast to @code{info}, @code{show} is for describing the state of |
c906108c SS |
1726 | @value{GDBN} itself. |
1727 | You can change most of the things you can @code{show}, by using the | |
1728 | related command @code{set}; for example, you can control what number | |
1729 | system is used for displays with @code{set radix}, or simply inquire | |
1730 | which is currently in use with @code{show radix}. | |
1731 | ||
1732 | @kindex info set | |
1733 | To display all the settable parameters and their current | |
1734 | values, you can use @code{show} with no arguments; you may also use | |
1735 | @code{info set}. Both commands produce the same display. | |
1736 | @c FIXME: "info set" violates the rule that "info" is for state of | |
1737 | @c FIXME...program. Ck w/ GNU: "info set" to be called something else, | |
1738 | @c FIXME...or change desc of rule---eg "state of prog and debugging session"? | |
1739 | @end table | |
1740 | @c @end group | |
1741 | ||
1742 | Here are three miscellaneous @code{show} subcommands, all of which are | |
1743 | exceptional in lacking corresponding @code{set} commands: | |
1744 | ||
1745 | @table @code | |
1746 | @kindex show version | |
9c16f35a | 1747 | @cindex @value{GDBN} version number |
c906108c SS |
1748 | @item show version |
1749 | Show what version of @value{GDBN} is running. You should include this | |
2df3850c JM |
1750 | information in @value{GDBN} bug-reports. If multiple versions of |
1751 | @value{GDBN} are in use at your site, you may need to determine which | |
1752 | version of @value{GDBN} you are running; as @value{GDBN} evolves, new | |
1753 | commands are introduced, and old ones may wither away. Also, many | |
1754 | system vendors ship variant versions of @value{GDBN}, and there are | |
96a2c332 | 1755 | variant versions of @value{GDBN} in @sc{gnu}/Linux distributions as well. |
2df3850c JM |
1756 | The version number is the same as the one announced when you start |
1757 | @value{GDBN}. | |
c906108c SS |
1758 | |
1759 | @kindex show copying | |
09d4efe1 | 1760 | @kindex info copying |
9c16f35a | 1761 | @cindex display @value{GDBN} copyright |
c906108c | 1762 | @item show copying |
09d4efe1 | 1763 | @itemx info copying |
c906108c SS |
1764 | Display information about permission for copying @value{GDBN}. |
1765 | ||
1766 | @kindex show warranty | |
09d4efe1 | 1767 | @kindex info warranty |
c906108c | 1768 | @item show warranty |
09d4efe1 | 1769 | @itemx info warranty |
2df3850c | 1770 | Display the @sc{gnu} ``NO WARRANTY'' statement, or a warranty, |
96a2c332 | 1771 | if your version of @value{GDBN} comes with one. |
2df3850c | 1772 | |
c906108c SS |
1773 | @end table |
1774 | ||
6d2ebf8b | 1775 | @node Running |
c906108c SS |
1776 | @chapter Running Programs Under @value{GDBN} |
1777 | ||
1778 | When you run a program under @value{GDBN}, you must first generate | |
1779 | debugging information when you compile it. | |
7a292a7a SS |
1780 | |
1781 | You may start @value{GDBN} with its arguments, if any, in an environment | |
1782 | of your choice. If you are doing native debugging, you may redirect | |
1783 | your program's input and output, debug an already running process, or | |
1784 | kill a child process. | |
c906108c SS |
1785 | |
1786 | @menu | |
1787 | * Compilation:: Compiling for debugging | |
1788 | * Starting:: Starting your program | |
c906108c SS |
1789 | * Arguments:: Your program's arguments |
1790 | * Environment:: Your program's environment | |
c906108c SS |
1791 | |
1792 | * Working Directory:: Your program's working directory | |
1793 | * Input/Output:: Your program's input and output | |
1794 | * Attach:: Debugging an already-running process | |
1795 | * Kill Process:: Killing the child process | |
c906108c | 1796 | |
6c95b8df | 1797 | * Inferiors and Programs:: Debugging multiple inferiors and programs |
c906108c | 1798 | * Threads:: Debugging programs with multiple threads |
6c95b8df | 1799 | * Forks:: Debugging forks |
5c95884b | 1800 | * Checkpoint/Restart:: Setting a @emph{bookmark} to return to later |
c906108c SS |
1801 | @end menu |
1802 | ||
6d2ebf8b | 1803 | @node Compilation |
79a6e687 | 1804 | @section Compiling for Debugging |
c906108c SS |
1805 | |
1806 | In order to debug a program effectively, you need to generate | |
1807 | debugging information when you compile it. This debugging information | |
1808 | is stored in the object file; it describes the data type of each | |
1809 | variable or function and the correspondence between source line numbers | |
1810 | and addresses in the executable code. | |
1811 | ||
1812 | To request debugging information, specify the @samp{-g} option when you run | |
1813 | the compiler. | |
1814 | ||
514c4d71 | 1815 | Programs that are to be shipped to your customers are compiled with |
edb3359d | 1816 | optimizations, using the @samp{-O} compiler option. However, some |
514c4d71 EZ |
1817 | compilers are unable to handle the @samp{-g} and @samp{-O} options |
1818 | together. Using those compilers, you cannot generate optimized | |
c906108c SS |
1819 | executables containing debugging information. |
1820 | ||
514c4d71 | 1821 | @value{NGCC}, the @sc{gnu} C/C@t{++} compiler, supports @samp{-g} with or |
53a5351d JM |
1822 | without @samp{-O}, making it possible to debug optimized code. We |
1823 | recommend that you @emph{always} use @samp{-g} whenever you compile a | |
1824 | program. You may think your program is correct, but there is no sense | |
edb3359d | 1825 | in pushing your luck. For more information, see @ref{Optimized Code}. |
c906108c SS |
1826 | |
1827 | Older versions of the @sc{gnu} C compiler permitted a variant option | |
1828 | @w{@samp{-gg}} for debugging information. @value{GDBN} no longer supports this | |
1829 | format; if your @sc{gnu} C compiler has this option, do not use it. | |
1830 | ||
514c4d71 EZ |
1831 | @value{GDBN} knows about preprocessor macros and can show you their |
1832 | expansion (@pxref{Macros}). Most compilers do not include information | |
1833 | about preprocessor macros in the debugging information if you specify | |
1834 | the @option{-g} flag alone, because this information is rather large. | |
1835 | Version 3.1 and later of @value{NGCC}, the @sc{gnu} C compiler, | |
1836 | provides macro information if you specify the options | |
1837 | @option{-gdwarf-2} and @option{-g3}; the former option requests | |
1838 | debugging information in the Dwarf 2 format, and the latter requests | |
1839 | ``extra information''. In the future, we hope to find more compact | |
1840 | ways to represent macro information, so that it can be included with | |
1841 | @option{-g} alone. | |
1842 | ||
c906108c | 1843 | @need 2000 |
6d2ebf8b | 1844 | @node Starting |
79a6e687 | 1845 | @section Starting your Program |
c906108c SS |
1846 | @cindex starting |
1847 | @cindex running | |
1848 | ||
1849 | @table @code | |
1850 | @kindex run | |
41afff9a | 1851 | @kindex r @r{(@code{run})} |
c906108c SS |
1852 | @item run |
1853 | @itemx r | |
7a292a7a SS |
1854 | Use the @code{run} command to start your program under @value{GDBN}. |
1855 | You must first specify the program name (except on VxWorks) with an | |
1856 | argument to @value{GDBN} (@pxref{Invocation, ,Getting In and Out of | |
1857 | @value{GDBN}}), or by using the @code{file} or @code{exec-file} command | |
79a6e687 | 1858 | (@pxref{Files, ,Commands to Specify Files}). |
c906108c SS |
1859 | |
1860 | @end table | |
1861 | ||
c906108c SS |
1862 | If you are running your program in an execution environment that |
1863 | supports processes, @code{run} creates an inferior process and makes | |
8edfe269 DJ |
1864 | that process run your program. In some environments without processes, |
1865 | @code{run} jumps to the start of your program. Other targets, | |
1866 | like @samp{remote}, are always running. If you get an error | |
1867 | message like this one: | |
1868 | ||
1869 | @smallexample | |
1870 | The "remote" target does not support "run". | |
1871 | Try "help target" or "continue". | |
1872 | @end smallexample | |
1873 | ||
1874 | @noindent | |
1875 | then use @code{continue} to run your program. You may need @code{load} | |
1876 | first (@pxref{load}). | |
c906108c SS |
1877 | |
1878 | The execution of a program is affected by certain information it | |
1879 | receives from its superior. @value{GDBN} provides ways to specify this | |
1880 | information, which you must do @emph{before} starting your program. (You | |
1881 | can change it after starting your program, but such changes only affect | |
1882 | your program the next time you start it.) This information may be | |
1883 | divided into four categories: | |
1884 | ||
1885 | @table @asis | |
1886 | @item The @emph{arguments.} | |
1887 | Specify the arguments to give your program as the arguments of the | |
1888 | @code{run} command. If a shell is available on your target, the shell | |
1889 | is used to pass the arguments, so that you may use normal conventions | |
1890 | (such as wildcard expansion or variable substitution) in describing | |
1891 | the arguments. | |
1892 | In Unix systems, you can control which shell is used with the | |
1893 | @code{SHELL} environment variable. | |
79a6e687 | 1894 | @xref{Arguments, ,Your Program's Arguments}. |
c906108c SS |
1895 | |
1896 | @item The @emph{environment.} | |
1897 | Your program normally inherits its environment from @value{GDBN}, but you can | |
1898 | use the @value{GDBN} commands @code{set environment} and @code{unset | |
1899 | environment} to change parts of the environment that affect | |
79a6e687 | 1900 | your program. @xref{Environment, ,Your Program's Environment}. |
c906108c SS |
1901 | |
1902 | @item The @emph{working directory.} | |
1903 | Your program inherits its working directory from @value{GDBN}. You can set | |
1904 | the @value{GDBN} working directory with the @code{cd} command in @value{GDBN}. | |
79a6e687 | 1905 | @xref{Working Directory, ,Your Program's Working Directory}. |
c906108c SS |
1906 | |
1907 | @item The @emph{standard input and output.} | |
1908 | Your program normally uses the same device for standard input and | |
1909 | standard output as @value{GDBN} is using. You can redirect input and output | |
1910 | in the @code{run} command line, or you can use the @code{tty} command to | |
1911 | set a different device for your program. | |
79a6e687 | 1912 | @xref{Input/Output, ,Your Program's Input and Output}. |
c906108c SS |
1913 | |
1914 | @cindex pipes | |
1915 | @emph{Warning:} While input and output redirection work, you cannot use | |
1916 | pipes to pass the output of the program you are debugging to another | |
1917 | program; if you attempt this, @value{GDBN} is likely to wind up debugging the | |
1918 | wrong program. | |
1919 | @end table | |
c906108c SS |
1920 | |
1921 | When you issue the @code{run} command, your program begins to execute | |
79a6e687 | 1922 | immediately. @xref{Stopping, ,Stopping and Continuing}, for discussion |
c906108c SS |
1923 | of how to arrange for your program to stop. Once your program has |
1924 | stopped, you may call functions in your program, using the @code{print} | |
1925 | or @code{call} commands. @xref{Data, ,Examining Data}. | |
1926 | ||
1927 | If the modification time of your symbol file has changed since the last | |
1928 | time @value{GDBN} read its symbols, @value{GDBN} discards its symbol | |
1929 | table, and reads it again. When it does this, @value{GDBN} tries to retain | |
1930 | your current breakpoints. | |
1931 | ||
4e8b0763 JB |
1932 | @table @code |
1933 | @kindex start | |
1934 | @item start | |
1935 | @cindex run to main procedure | |
1936 | The name of the main procedure can vary from language to language. | |
1937 | With C or C@t{++}, the main procedure name is always @code{main}, but | |
1938 | other languages such as Ada do not require a specific name for their | |
1939 | main procedure. The debugger provides a convenient way to start the | |
1940 | execution of the program and to stop at the beginning of the main | |
1941 | procedure, depending on the language used. | |
1942 | ||
1943 | The @samp{start} command does the equivalent of setting a temporary | |
1944 | breakpoint at the beginning of the main procedure and then invoking | |
1945 | the @samp{run} command. | |
1946 | ||
f018e82f EZ |
1947 | @cindex elaboration phase |
1948 | Some programs contain an @dfn{elaboration} phase where some startup code is | |
1949 | executed before the main procedure is called. This depends on the | |
1950 | languages used to write your program. In C@t{++}, for instance, | |
4e8b0763 JB |
1951 | constructors for static and global objects are executed before |
1952 | @code{main} is called. It is therefore possible that the debugger stops | |
1953 | before reaching the main procedure. However, the temporary breakpoint | |
1954 | will remain to halt execution. | |
1955 | ||
1956 | Specify the arguments to give to your program as arguments to the | |
1957 | @samp{start} command. These arguments will be given verbatim to the | |
1958 | underlying @samp{run} command. Note that the same arguments will be | |
1959 | reused if no argument is provided during subsequent calls to | |
1960 | @samp{start} or @samp{run}. | |
1961 | ||
1962 | It is sometimes necessary to debug the program during elaboration. In | |
1963 | these cases, using the @code{start} command would stop the execution of | |
1964 | your program too late, as the program would have already completed the | |
1965 | elaboration phase. Under these circumstances, insert breakpoints in your | |
1966 | elaboration code before running your program. | |
ccd213ac DJ |
1967 | |
1968 | @kindex set exec-wrapper | |
1969 | @item set exec-wrapper @var{wrapper} | |
1970 | @itemx show exec-wrapper | |
1971 | @itemx unset exec-wrapper | |
1972 | When @samp{exec-wrapper} is set, the specified wrapper is used to | |
1973 | launch programs for debugging. @value{GDBN} starts your program | |
1974 | with a shell command of the form @kbd{exec @var{wrapper} | |
1975 | @var{program}}. Quoting is added to @var{program} and its | |
1976 | arguments, but not to @var{wrapper}, so you should add quotes if | |
1977 | appropriate for your shell. The wrapper runs until it executes | |
1978 | your program, and then @value{GDBN} takes control. | |
1979 | ||
1980 | You can use any program that eventually calls @code{execve} with | |
1981 | its arguments as a wrapper. Several standard Unix utilities do | |
1982 | this, e.g.@: @code{env} and @code{nohup}. Any Unix shell script ending | |
1983 | with @code{exec "$@@"} will also work. | |
1984 | ||
1985 | For example, you can use @code{env} to pass an environment variable to | |
1986 | the debugged program, without setting the variable in your shell's | |
1987 | environment: | |
1988 | ||
1989 | @smallexample | |
1990 | (@value{GDBP}) set exec-wrapper env 'LD_PRELOAD=libtest.so' | |
1991 | (@value{GDBP}) run | |
1992 | @end smallexample | |
1993 | ||
1994 | This command is available when debugging locally on most targets, excluding | |
1995 | @sc{djgpp}, Cygwin, MS Windows, and QNX Neutrino. | |
1996 | ||
10568435 JK |
1997 | @kindex set disable-randomization |
1998 | @item set disable-randomization | |
1999 | @itemx set disable-randomization on | |
2000 | This option (enabled by default in @value{GDBN}) will turn off the native | |
2001 | randomization of the virtual address space of the started program. This option | |
2002 | is useful for multiple debugging sessions to make the execution better | |
2003 | reproducible and memory addresses reusable across debugging sessions. | |
2004 | ||
2005 | This feature is implemented only on @sc{gnu}/Linux. You can get the same | |
2006 | behavior using | |
2007 | ||
2008 | @smallexample | |
2009 | (@value{GDBP}) set exec-wrapper setarch `uname -m` -R | |
2010 | @end smallexample | |
2011 | ||
2012 | @item set disable-randomization off | |
2013 | Leave the behavior of the started executable unchanged. Some bugs rear their | |
2014 | ugly heads only when the program is loaded at certain addresses. If your bug | |
2015 | disappears when you run the program under @value{GDBN}, that might be because | |
2016 | @value{GDBN} by default disables the address randomization on platforms, such | |
2017 | as @sc{gnu}/Linux, which do that for stand-alone programs. Use @kbd{set | |
2018 | disable-randomization off} to try to reproduce such elusive bugs. | |
2019 | ||
2020 | The virtual address space randomization is implemented only on @sc{gnu}/Linux. | |
2021 | It protects the programs against some kinds of security attacks. In these | |
2022 | cases the attacker needs to know the exact location of a concrete executable | |
2023 | code. Randomizing its location makes it impossible to inject jumps misusing | |
2024 | a code at its expected addresses. | |
2025 | ||
2026 | Prelinking shared libraries provides a startup performance advantage but it | |
2027 | makes addresses in these libraries predictable for privileged processes by | |
2028 | having just unprivileged access at the target system. Reading the shared | |
2029 | library binary gives enough information for assembling the malicious code | |
2030 | misusing it. Still even a prelinked shared library can get loaded at a new | |
2031 | random address just requiring the regular relocation process during the | |
2032 | startup. Shared libraries not already prelinked are always loaded at | |
2033 | a randomly chosen address. | |
2034 | ||
2035 | Position independent executables (PIE) contain position independent code | |
2036 | similar to the shared libraries and therefore such executables get loaded at | |
2037 | a randomly chosen address upon startup. PIE executables always load even | |
2038 | already prelinked shared libraries at a random address. You can build such | |
2039 | executable using @command{gcc -fPIE -pie}. | |
2040 | ||
2041 | Heap (malloc storage), stack and custom mmap areas are always placed randomly | |
2042 | (as long as the randomization is enabled). | |
2043 | ||
2044 | @item show disable-randomization | |
2045 | Show the current setting of the explicit disable of the native randomization of | |
2046 | the virtual address space of the started program. | |
2047 | ||
4e8b0763 JB |
2048 | @end table |
2049 | ||
6d2ebf8b | 2050 | @node Arguments |
79a6e687 | 2051 | @section Your Program's Arguments |
c906108c SS |
2052 | |
2053 | @cindex arguments (to your program) | |
2054 | The arguments to your program can be specified by the arguments of the | |
5d161b24 | 2055 | @code{run} command. |
c906108c SS |
2056 | They are passed to a shell, which expands wildcard characters and |
2057 | performs redirection of I/O, and thence to your program. Your | |
2058 | @code{SHELL} environment variable (if it exists) specifies what shell | |
2059 | @value{GDBN} uses. If you do not define @code{SHELL}, @value{GDBN} uses | |
d4f3574e SS |
2060 | the default shell (@file{/bin/sh} on Unix). |
2061 | ||
2062 | On non-Unix systems, the program is usually invoked directly by | |
2063 | @value{GDBN}, which emulates I/O redirection via the appropriate system | |
2064 | calls, and the wildcard characters are expanded by the startup code of | |
2065 | the program, not by the shell. | |
c906108c SS |
2066 | |
2067 | @code{run} with no arguments uses the same arguments used by the previous | |
2068 | @code{run}, or those set by the @code{set args} command. | |
2069 | ||
c906108c | 2070 | @table @code |
41afff9a | 2071 | @kindex set args |
c906108c SS |
2072 | @item set args |
2073 | Specify the arguments to be used the next time your program is run. If | |
2074 | @code{set args} has no arguments, @code{run} executes your program | |
2075 | with no arguments. Once you have run your program with arguments, | |
2076 | using @code{set args} before the next @code{run} is the only way to run | |
2077 | it again without arguments. | |
2078 | ||
2079 | @kindex show args | |
2080 | @item show args | |
2081 | Show the arguments to give your program when it is started. | |
2082 | @end table | |
2083 | ||
6d2ebf8b | 2084 | @node Environment |
79a6e687 | 2085 | @section Your Program's Environment |
c906108c SS |
2086 | |
2087 | @cindex environment (of your program) | |
2088 | The @dfn{environment} consists of a set of environment variables and | |
2089 | their values. Environment variables conventionally record such things as | |
2090 | your user name, your home directory, your terminal type, and your search | |
2091 | path for programs to run. Usually you set up environment variables with | |
2092 | the shell and they are inherited by all the other programs you run. When | |
2093 | debugging, it can be useful to try running your program with a modified | |
2094 | environment without having to start @value{GDBN} over again. | |
2095 | ||
2096 | @table @code | |
2097 | @kindex path | |
2098 | @item path @var{directory} | |
2099 | Add @var{directory} to the front of the @code{PATH} environment variable | |
17cc6a06 EZ |
2100 | (the search path for executables) that will be passed to your program. |
2101 | The value of @code{PATH} used by @value{GDBN} does not change. | |
d4f3574e SS |
2102 | You may specify several directory names, separated by whitespace or by a |
2103 | system-dependent separator character (@samp{:} on Unix, @samp{;} on | |
2104 | MS-DOS and MS-Windows). If @var{directory} is already in the path, it | |
2105 | is moved to the front, so it is searched sooner. | |
c906108c SS |
2106 | |
2107 | You can use the string @samp{$cwd} to refer to whatever is the current | |
2108 | working directory at the time @value{GDBN} searches the path. If you | |
2109 | use @samp{.} instead, it refers to the directory where you executed the | |
2110 | @code{path} command. @value{GDBN} replaces @samp{.} in the | |
2111 | @var{directory} argument (with the current path) before adding | |
2112 | @var{directory} to the search path. | |
2113 | @c 'path' is explicitly nonrepeatable, but RMS points out it is silly to | |
2114 | @c document that, since repeating it would be a no-op. | |
2115 | ||
2116 | @kindex show paths | |
2117 | @item show paths | |
2118 | Display the list of search paths for executables (the @code{PATH} | |
2119 | environment variable). | |
2120 | ||
2121 | @kindex show environment | |
2122 | @item show environment @r{[}@var{varname}@r{]} | |
2123 | Print the value of environment variable @var{varname} to be given to | |
2124 | your program when it starts. If you do not supply @var{varname}, | |
2125 | print the names and values of all environment variables to be given to | |
2126 | your program. You can abbreviate @code{environment} as @code{env}. | |
2127 | ||
2128 | @kindex set environment | |
53a5351d | 2129 | @item set environment @var{varname} @r{[}=@var{value}@r{]} |
c906108c SS |
2130 | Set environment variable @var{varname} to @var{value}. The value |
2131 | changes for your program only, not for @value{GDBN} itself. @var{value} may | |
2132 | be any string; the values of environment variables are just strings, and | |
2133 | any interpretation is supplied by your program itself. The @var{value} | |
2134 | parameter is optional; if it is eliminated, the variable is set to a | |
2135 | null value. | |
2136 | @c "any string" here does not include leading, trailing | |
2137 | @c blanks. Gnu asks: does anyone care? | |
2138 | ||
2139 | For example, this command: | |
2140 | ||
474c8240 | 2141 | @smallexample |
c906108c | 2142 | set env USER = foo |
474c8240 | 2143 | @end smallexample |
c906108c SS |
2144 | |
2145 | @noindent | |
d4f3574e | 2146 | tells the debugged program, when subsequently run, that its user is named |
c906108c SS |
2147 | @samp{foo}. (The spaces around @samp{=} are used for clarity here; they |
2148 | are not actually required.) | |
2149 | ||
2150 | @kindex unset environment | |
2151 | @item unset environment @var{varname} | |
2152 | Remove variable @var{varname} from the environment to be passed to your | |
2153 | program. This is different from @samp{set env @var{varname} =}; | |
2154 | @code{unset environment} removes the variable from the environment, | |
2155 | rather than assigning it an empty value. | |
2156 | @end table | |
2157 | ||
d4f3574e SS |
2158 | @emph{Warning:} On Unix systems, @value{GDBN} runs your program using |
2159 | the shell indicated | |
c906108c SS |
2160 | by your @code{SHELL} environment variable if it exists (or |
2161 | @code{/bin/sh} if not). If your @code{SHELL} variable names a shell | |
2162 | that runs an initialization file---such as @file{.cshrc} for C-shell, or | |
2163 | @file{.bashrc} for BASH---any variables you set in that file affect | |
2164 | your program. You may wish to move setting of environment variables to | |
2165 | files that are only run when you sign on, such as @file{.login} or | |
2166 | @file{.profile}. | |
2167 | ||
6d2ebf8b | 2168 | @node Working Directory |
79a6e687 | 2169 | @section Your Program's Working Directory |
c906108c SS |
2170 | |
2171 | @cindex working directory (of your program) | |
2172 | Each time you start your program with @code{run}, it inherits its | |
2173 | working directory from the current working directory of @value{GDBN}. | |
2174 | The @value{GDBN} working directory is initially whatever it inherited | |
2175 | from its parent process (typically the shell), but you can specify a new | |
2176 | working directory in @value{GDBN} with the @code{cd} command. | |
2177 | ||
2178 | The @value{GDBN} working directory also serves as a default for the commands | |
2179 | that specify files for @value{GDBN} to operate on. @xref{Files, ,Commands to | |
79a6e687 | 2180 | Specify Files}. |
c906108c SS |
2181 | |
2182 | @table @code | |
2183 | @kindex cd | |
721c2651 | 2184 | @cindex change working directory |
c906108c SS |
2185 | @item cd @var{directory} |
2186 | Set the @value{GDBN} working directory to @var{directory}. | |
2187 | ||
2188 | @kindex pwd | |
2189 | @item pwd | |
2190 | Print the @value{GDBN} working directory. | |
2191 | @end table | |
2192 | ||
60bf7e09 EZ |
2193 | It is generally impossible to find the current working directory of |
2194 | the process being debugged (since a program can change its directory | |
2195 | during its run). If you work on a system where @value{GDBN} is | |
2196 | configured with the @file{/proc} support, you can use the @code{info | |
2197 | proc} command (@pxref{SVR4 Process Information}) to find out the | |
2198 | current working directory of the debuggee. | |
2199 | ||
6d2ebf8b | 2200 | @node Input/Output |
79a6e687 | 2201 | @section Your Program's Input and Output |
c906108c SS |
2202 | |
2203 | @cindex redirection | |
2204 | @cindex i/o | |
2205 | @cindex terminal | |
2206 | By default, the program you run under @value{GDBN} does input and output to | |
5d161b24 | 2207 | the same terminal that @value{GDBN} uses. @value{GDBN} switches the terminal |
c906108c SS |
2208 | to its own terminal modes to interact with you, but it records the terminal |
2209 | modes your program was using and switches back to them when you continue | |
2210 | running your program. | |
2211 | ||
2212 | @table @code | |
2213 | @kindex info terminal | |
2214 | @item info terminal | |
2215 | Displays information recorded by @value{GDBN} about the terminal modes your | |
2216 | program is using. | |
2217 | @end table | |
2218 | ||
2219 | You can redirect your program's input and/or output using shell | |
2220 | redirection with the @code{run} command. For example, | |
2221 | ||
474c8240 | 2222 | @smallexample |
c906108c | 2223 | run > outfile |
474c8240 | 2224 | @end smallexample |
c906108c SS |
2225 | |
2226 | @noindent | |
2227 | starts your program, diverting its output to the file @file{outfile}. | |
2228 | ||
2229 | @kindex tty | |
2230 | @cindex controlling terminal | |
2231 | Another way to specify where your program should do input and output is | |
2232 | with the @code{tty} command. This command accepts a file name as | |
2233 | argument, and causes this file to be the default for future @code{run} | |
2234 | commands. It also resets the controlling terminal for the child | |
2235 | process, for future @code{run} commands. For example, | |
2236 | ||
474c8240 | 2237 | @smallexample |
c906108c | 2238 | tty /dev/ttyb |
474c8240 | 2239 | @end smallexample |
c906108c SS |
2240 | |
2241 | @noindent | |
2242 | directs that processes started with subsequent @code{run} commands | |
2243 | default to do input and output on the terminal @file{/dev/ttyb} and have | |
2244 | that as their controlling terminal. | |
2245 | ||
2246 | An explicit redirection in @code{run} overrides the @code{tty} command's | |
2247 | effect on the input/output device, but not its effect on the controlling | |
2248 | terminal. | |
2249 | ||
2250 | When you use the @code{tty} command or redirect input in the @code{run} | |
2251 | command, only the input @emph{for your program} is affected. The input | |
3cb3b8df BR |
2252 | for @value{GDBN} still comes from your terminal. @code{tty} is an alias |
2253 | for @code{set inferior-tty}. | |
2254 | ||
2255 | @cindex inferior tty | |
2256 | @cindex set inferior controlling terminal | |
2257 | You can use the @code{show inferior-tty} command to tell @value{GDBN} to | |
2258 | display the name of the terminal that will be used for future runs of your | |
2259 | program. | |
2260 | ||
2261 | @table @code | |
2262 | @item set inferior-tty /dev/ttyb | |
2263 | @kindex set inferior-tty | |
2264 | Set the tty for the program being debugged to /dev/ttyb. | |
2265 | ||
2266 | @item show inferior-tty | |
2267 | @kindex show inferior-tty | |
2268 | Show the current tty for the program being debugged. | |
2269 | @end table | |
c906108c | 2270 | |
6d2ebf8b | 2271 | @node Attach |
79a6e687 | 2272 | @section Debugging an Already-running Process |
c906108c SS |
2273 | @kindex attach |
2274 | @cindex attach | |
2275 | ||
2276 | @table @code | |
2277 | @item attach @var{process-id} | |
2278 | This command attaches to a running process---one that was started | |
2279 | outside @value{GDBN}. (@code{info files} shows your active | |
2280 | targets.) The command takes as argument a process ID. The usual way to | |
09d4efe1 | 2281 | find out the @var{process-id} of a Unix process is with the @code{ps} utility, |
c906108c SS |
2282 | or with the @samp{jobs -l} shell command. |
2283 | ||
2284 | @code{attach} does not repeat if you press @key{RET} a second time after | |
2285 | executing the command. | |
2286 | @end table | |
2287 | ||
2288 | To use @code{attach}, your program must be running in an environment | |
2289 | which supports processes; for example, @code{attach} does not work for | |
2290 | programs on bare-board targets that lack an operating system. You must | |
2291 | also have permission to send the process a signal. | |
2292 | ||
2293 | When you use @code{attach}, the debugger finds the program running in | |
2294 | the process first by looking in the current working directory, then (if | |
2295 | the program is not found) by using the source file search path | |
79a6e687 | 2296 | (@pxref{Source Path, ,Specifying Source Directories}). You can also use |
c906108c SS |
2297 | the @code{file} command to load the program. @xref{Files, ,Commands to |
2298 | Specify Files}. | |
2299 | ||
2300 | The first thing @value{GDBN} does after arranging to debug the specified | |
2301 | process is to stop it. You can examine and modify an attached process | |
53a5351d JM |
2302 | with all the @value{GDBN} commands that are ordinarily available when |
2303 | you start processes with @code{run}. You can insert breakpoints; you | |
2304 | can step and continue; you can modify storage. If you would rather the | |
2305 | process continue running, you may use the @code{continue} command after | |
c906108c SS |
2306 | attaching @value{GDBN} to the process. |
2307 | ||
2308 | @table @code | |
2309 | @kindex detach | |
2310 | @item detach | |
2311 | When you have finished debugging the attached process, you can use the | |
2312 | @code{detach} command to release it from @value{GDBN} control. Detaching | |
2313 | the process continues its execution. After the @code{detach} command, | |
2314 | that process and @value{GDBN} become completely independent once more, and you | |
2315 | are ready to @code{attach} another process or start one with @code{run}. | |
2316 | @code{detach} does not repeat if you press @key{RET} again after | |
2317 | executing the command. | |
2318 | @end table | |
2319 | ||
159fcc13 JK |
2320 | If you exit @value{GDBN} while you have an attached process, you detach |
2321 | that process. If you use the @code{run} command, you kill that process. | |
2322 | By default, @value{GDBN} asks for confirmation if you try to do either of these | |
2323 | things; you can control whether or not you need to confirm by using the | |
2324 | @code{set confirm} command (@pxref{Messages/Warnings, ,Optional Warnings and | |
79a6e687 | 2325 | Messages}). |
c906108c | 2326 | |
6d2ebf8b | 2327 | @node Kill Process |
79a6e687 | 2328 | @section Killing the Child Process |
c906108c SS |
2329 | |
2330 | @table @code | |
2331 | @kindex kill | |
2332 | @item kill | |
2333 | Kill the child process in which your program is running under @value{GDBN}. | |
2334 | @end table | |
2335 | ||
2336 | This command is useful if you wish to debug a core dump instead of a | |
2337 | running process. @value{GDBN} ignores any core dump file while your program | |
2338 | is running. | |
2339 | ||
2340 | On some operating systems, a program cannot be executed outside @value{GDBN} | |
2341 | while you have breakpoints set on it inside @value{GDBN}. You can use the | |
2342 | @code{kill} command in this situation to permit running your program | |
2343 | outside the debugger. | |
2344 | ||
2345 | The @code{kill} command is also useful if you wish to recompile and | |
2346 | relink your program, since on many systems it is impossible to modify an | |
2347 | executable file while it is running in a process. In this case, when you | |
2348 | next type @code{run}, @value{GDBN} notices that the file has changed, and | |
2349 | reads the symbol table again (while trying to preserve your current | |
2350 | breakpoint settings). | |
2351 | ||
6c95b8df PA |
2352 | @node Inferiors and Programs |
2353 | @section Debugging Multiple Inferiors and Programs | |
b77209e0 | 2354 | |
6c95b8df PA |
2355 | @value{GDBN} lets you run and debug multiple programs in a single |
2356 | session. In addition, @value{GDBN} on some systems may let you run | |
2357 | several programs simultaneously (otherwise you have to exit from one | |
2358 | before starting another). In the most general case, you can have | |
2359 | multiple threads of execution in each of multiple processes, launched | |
2360 | from multiple executables. | |
b77209e0 PA |
2361 | |
2362 | @cindex inferior | |
2363 | @value{GDBN} represents the state of each program execution with an | |
2364 | object called an @dfn{inferior}. An inferior typically corresponds to | |
2365 | a process, but is more general and applies also to targets that do not | |
2366 | have processes. Inferiors may be created before a process runs, and | |
6c95b8df PA |
2367 | may be retained after a process exits. Inferiors have unique |
2368 | identifiers that are different from process ids. Usually each | |
2369 | inferior will also have its own distinct address space, although some | |
2370 | embedded targets may have several inferiors running in different parts | |
2371 | of a single address space. Each inferior may in turn have multiple | |
2372 | threads running in it. | |
b77209e0 | 2373 | |
6c95b8df PA |
2374 | To find out what inferiors exist at any moment, use @w{@code{info |
2375 | inferiors}}: | |
b77209e0 PA |
2376 | |
2377 | @table @code | |
2378 | @kindex info inferiors | |
2379 | @item info inferiors | |
2380 | Print a list of all inferiors currently being managed by @value{GDBN}. | |
3a1ff0b6 PA |
2381 | |
2382 | @value{GDBN} displays for each inferior (in this order): | |
2383 | ||
2384 | @enumerate | |
2385 | @item | |
2386 | the inferior number assigned by @value{GDBN} | |
2387 | ||
2388 | @item | |
2389 | the target system's inferior identifier | |
6c95b8df PA |
2390 | |
2391 | @item | |
2392 | the name of the executable the inferior is running. | |
2393 | ||
3a1ff0b6 PA |
2394 | @end enumerate |
2395 | ||
2396 | @noindent | |
2397 | An asterisk @samp{*} preceding the @value{GDBN} inferior number | |
2398 | indicates the current inferior. | |
2399 | ||
2400 | For example, | |
2277426b | 2401 | @end table |
3a1ff0b6 PA |
2402 | @c end table here to get a little more width for example |
2403 | ||
2404 | @smallexample | |
2405 | (@value{GDBP}) info inferiors | |
6c95b8df PA |
2406 | Num Description Executable |
2407 | 2 process 2307 hello | |
2408 | * 1 process 3401 goodbye | |
3a1ff0b6 | 2409 | @end smallexample |
2277426b PA |
2410 | |
2411 | To switch focus between inferiors, use the @code{inferior} command: | |
2412 | ||
2413 | @table @code | |
3a1ff0b6 PA |
2414 | @kindex inferior @var{infno} |
2415 | @item inferior @var{infno} | |
2416 | Make inferior number @var{infno} the current inferior. The argument | |
2417 | @var{infno} is the inferior number assigned by @value{GDBN}, as shown | |
2418 | in the first field of the @samp{info inferiors} display. | |
2277426b PA |
2419 | @end table |
2420 | ||
6c95b8df PA |
2421 | |
2422 | You can get multiple executables into a debugging session via the | |
2423 | @code{add-inferior} and @w{@code{clone-inferior}} commands. On some | |
2424 | systems @value{GDBN} can add inferiors to the debug session | |
2425 | automatically by following calls to @code{fork} and @code{exec}. To | |
2426 | remove inferiors from the debugging session use the | |
2427 | @w{@code{remove-inferior}} command. | |
2428 | ||
2429 | @table @code | |
2430 | @kindex add-inferior | |
2431 | @item add-inferior [ -copies @var{n} ] [ -exec @var{executable} ] | |
2432 | Adds @var{n} inferiors to be run using @var{executable} as the | |
2433 | executable. @var{n} defaults to 1. If no executable is specified, | |
2434 | the inferiors begins empty, with no program. You can still assign or | |
2435 | change the program assigned to the inferior at any time by using the | |
2436 | @code{file} command with the executable name as its argument. | |
2437 | ||
2438 | @kindex clone-inferior | |
2439 | @item clone-inferior [ -copies @var{n} ] [ @var{infno} ] | |
2440 | Adds @var{n} inferiors ready to execute the same program as inferior | |
2441 | @var{infno}. @var{n} defaults to 1. @var{infno} defaults to the | |
2442 | number of the current inferior. This is a convenient command when you | |
2443 | want to run another instance of the inferior you are debugging. | |
2444 | ||
2445 | @smallexample | |
2446 | (@value{GDBP}) info inferiors | |
2447 | Num Description Executable | |
2448 | * 1 process 29964 helloworld | |
2449 | (@value{GDBP}) clone-inferior | |
2450 | Added inferior 2. | |
2451 | 1 inferiors added. | |
2452 | (@value{GDBP}) info inferiors | |
2453 | Num Description Executable | |
2454 | 2 <null> helloworld | |
2455 | * 1 process 29964 helloworld | |
2456 | @end smallexample | |
2457 | ||
2458 | You can now simply switch focus to inferior 2 and run it. | |
2459 | ||
2460 | @kindex remove-inferior | |
2461 | @item remove-inferior @var{infno} | |
2462 | Removes the inferior @var{infno}. It is not possible to remove an | |
2463 | inferior that is running with this command. For those, use the | |
2464 | @code{kill} or @code{detach} command first. | |
2465 | ||
2466 | @end table | |
2467 | ||
2468 | To quit debugging one of the running inferiors that is not the current | |
2469 | inferior, you can either detach from it by using the @w{@code{detach | |
2470 | inferior}} command (allowing it to run independently), or kill it | |
2471 | using the @w{@code{kill inferior}} command: | |
2277426b PA |
2472 | |
2473 | @table @code | |
3a1ff0b6 PA |
2474 | @kindex detach inferior @var{infno} |
2475 | @item detach inferior @var{infno} | |
2277426b | 2476 | Detach from the inferior identified by @value{GDBN} inferior number |
3a1ff0b6 | 2477 | @var{infno}, and remove it from the inferior list. |
2277426b | 2478 | |
3a1ff0b6 PA |
2479 | @kindex kill inferior @var{infno} |
2480 | @item kill inferior @var{infno} | |
2277426b | 2481 | Kill the inferior identified by @value{GDBN} inferior number |
3a1ff0b6 | 2482 | @var{infno}, and remove it from the inferior list. |
2277426b PA |
2483 | @end table |
2484 | ||
6c95b8df PA |
2485 | After the successful completion of a command such as @code{detach}, |
2486 | @code{detach inferior}, @code{kill} or @code{kill inferior}, or after | |
2487 | a normal process exit, the inferior is still valid and listed with | |
2488 | @code{info inferiors}, ready to be restarted. | |
2489 | ||
2490 | ||
2277426b PA |
2491 | To be notified when inferiors are started or exit under @value{GDBN}'s |
2492 | control use @w{@code{set print inferior-events}}: | |
b77209e0 | 2493 | |
2277426b | 2494 | @table @code |
b77209e0 PA |
2495 | @kindex set print inferior-events |
2496 | @cindex print messages on inferior start and exit | |
2497 | @item set print inferior-events | |
2498 | @itemx set print inferior-events on | |
2499 | @itemx set print inferior-events off | |
2500 | The @code{set print inferior-events} command allows you to enable or | |
2501 | disable printing of messages when @value{GDBN} notices that new | |
2502 | inferiors have started or that inferiors have exited or have been | |
2503 | detached. By default, these messages will not be printed. | |
2504 | ||
2505 | @kindex show print inferior-events | |
2506 | @item show print inferior-events | |
2507 | Show whether messages will be printed when @value{GDBN} detects that | |
2508 | inferiors have started, exited or have been detached. | |
2509 | @end table | |
2510 | ||
6c95b8df PA |
2511 | Many commands will work the same with multiple programs as with a |
2512 | single program: e.g., @code{print myglobal} will simply display the | |
2513 | value of @code{myglobal} in the current inferior. | |
2514 | ||
2515 | ||
2516 | Occasionaly, when debugging @value{GDBN} itself, it may be useful to | |
2517 | get more info about the relationship of inferiors, programs, address | |
2518 | spaces in a debug session. You can do that with the @w{@code{maint | |
2519 | info program-spaces}} command. | |
2520 | ||
2521 | @table @code | |
2522 | @kindex maint info program-spaces | |
2523 | @item maint info program-spaces | |
2524 | Print a list of all program spaces currently being managed by | |
2525 | @value{GDBN}. | |
2526 | ||
2527 | @value{GDBN} displays for each program space (in this order): | |
2528 | ||
2529 | @enumerate | |
2530 | @item | |
2531 | the program space number assigned by @value{GDBN} | |
2532 | ||
2533 | @item | |
2534 | the name of the executable loaded into the program space, with e.g., | |
2535 | the @code{file} command. | |
2536 | ||
2537 | @end enumerate | |
2538 | ||
2539 | @noindent | |
2540 | An asterisk @samp{*} preceding the @value{GDBN} program space number | |
2541 | indicates the current program space. | |
2542 | ||
2543 | In addition, below each program space line, @value{GDBN} prints extra | |
2544 | information that isn't suitable to display in tabular form. For | |
2545 | example, the list of inferiors bound to the program space. | |
2546 | ||
2547 | @smallexample | |
2548 | (@value{GDBP}) maint info program-spaces | |
2549 | Id Executable | |
2550 | 2 goodbye | |
2551 | Bound inferiors: ID 1 (process 21561) | |
2552 | * 1 hello | |
2553 | @end smallexample | |
2554 | ||
2555 | Here we can see that no inferior is running the program @code{hello}, | |
2556 | while @code{process 21561} is running the program @code{goodbye}. On | |
2557 | some targets, it is possible that multiple inferiors are bound to the | |
2558 | same program space. The most common example is that of debugging both | |
2559 | the parent and child processes of a @code{vfork} call. For example, | |
2560 | ||
2561 | @smallexample | |
2562 | (@value{GDBP}) maint info program-spaces | |
2563 | Id Executable | |
2564 | * 1 vfork-test | |
2565 | Bound inferiors: ID 2 (process 18050), ID 1 (process 18045) | |
2566 | @end smallexample | |
2567 | ||
2568 | Here, both inferior 2 and inferior 1 are running in the same program | |
2569 | space as a result of inferior 1 having executed a @code{vfork} call. | |
2570 | @end table | |
2571 | ||
6d2ebf8b | 2572 | @node Threads |
79a6e687 | 2573 | @section Debugging Programs with Multiple Threads |
c906108c SS |
2574 | |
2575 | @cindex threads of execution | |
2576 | @cindex multiple threads | |
2577 | @cindex switching threads | |
2578 | In some operating systems, such as HP-UX and Solaris, a single program | |
2579 | may have more than one @dfn{thread} of execution. The precise semantics | |
2580 | of threads differ from one operating system to another, but in general | |
2581 | the threads of a single program are akin to multiple processes---except | |
2582 | that they share one address space (that is, they can all examine and | |
2583 | modify the same variables). On the other hand, each thread has its own | |
2584 | registers and execution stack, and perhaps private memory. | |
2585 | ||
2586 | @value{GDBN} provides these facilities for debugging multi-thread | |
2587 | programs: | |
2588 | ||
2589 | @itemize @bullet | |
2590 | @item automatic notification of new threads | |
2591 | @item @samp{thread @var{threadno}}, a command to switch among threads | |
2592 | @item @samp{info threads}, a command to inquire about existing threads | |
5d161b24 | 2593 | @item @samp{thread apply [@var{threadno}] [@var{all}] @var{args}}, |
c906108c SS |
2594 | a command to apply a command to a list of threads |
2595 | @item thread-specific breakpoints | |
93815fbf VP |
2596 | @item @samp{set print thread-events}, which controls printing of |
2597 | messages on thread start and exit. | |
17a37d48 PP |
2598 | @item @samp{set libthread-db-search-path @var{path}}, which lets |
2599 | the user specify which @code{libthread_db} to use if the default choice | |
2600 | isn't compatible with the program. | |
c906108c SS |
2601 | @end itemize |
2602 | ||
c906108c SS |
2603 | @quotation |
2604 | @emph{Warning:} These facilities are not yet available on every | |
2605 | @value{GDBN} configuration where the operating system supports threads. | |
2606 | If your @value{GDBN} does not support threads, these commands have no | |
2607 | effect. For example, a system without thread support shows no output | |
2608 | from @samp{info threads}, and always rejects the @code{thread} command, | |
2609 | like this: | |
2610 | ||
2611 | @smallexample | |
2612 | (@value{GDBP}) info threads | |
2613 | (@value{GDBP}) thread 1 | |
2614 | Thread ID 1 not known. Use the "info threads" command to | |
2615 | see the IDs of currently known threads. | |
2616 | @end smallexample | |
2617 | @c FIXME to implementors: how hard would it be to say "sorry, this GDB | |
2618 | @c doesn't support threads"? | |
2619 | @end quotation | |
c906108c SS |
2620 | |
2621 | @cindex focus of debugging | |
2622 | @cindex current thread | |
2623 | The @value{GDBN} thread debugging facility allows you to observe all | |
2624 | threads while your program runs---but whenever @value{GDBN} takes | |
2625 | control, one thread in particular is always the focus of debugging. | |
2626 | This thread is called the @dfn{current thread}. Debugging commands show | |
2627 | program information from the perspective of the current thread. | |
2628 | ||
41afff9a | 2629 | @cindex @code{New} @var{systag} message |
c906108c SS |
2630 | @cindex thread identifier (system) |
2631 | @c FIXME-implementors!! It would be more helpful if the [New...] message | |
2632 | @c included GDB's numeric thread handle, so you could just go to that | |
2633 | @c thread without first checking `info threads'. | |
2634 | Whenever @value{GDBN} detects a new thread in your program, it displays | |
2635 | the target system's identification for the thread with a message in the | |
2636 | form @samp{[New @var{systag}]}. @var{systag} is a thread identifier | |
2637 | whose form varies depending on the particular system. For example, on | |
8807d78b | 2638 | @sc{gnu}/Linux, you might see |
c906108c | 2639 | |
474c8240 | 2640 | @smallexample |
8807d78b | 2641 | [New Thread 46912507313328 (LWP 25582)] |
474c8240 | 2642 | @end smallexample |
c906108c SS |
2643 | |
2644 | @noindent | |
2645 | when @value{GDBN} notices a new thread. In contrast, on an SGI system, | |
2646 | the @var{systag} is simply something like @samp{process 368}, with no | |
2647 | further qualifier. | |
2648 | ||
2649 | @c FIXME!! (1) Does the [New...] message appear even for the very first | |
2650 | @c thread of a program, or does it only appear for the | |
6ca652b0 | 2651 | @c second---i.e.@: when it becomes obvious we have a multithread |
c906108c SS |
2652 | @c program? |
2653 | @c (2) *Is* there necessarily a first thread always? Or do some | |
2654 | @c multithread systems permit starting a program with multiple | |
5d161b24 | 2655 | @c threads ab initio? |
c906108c SS |
2656 | |
2657 | @cindex thread number | |
2658 | @cindex thread identifier (GDB) | |
2659 | For debugging purposes, @value{GDBN} associates its own thread | |
2660 | number---always a single integer---with each thread in your program. | |
2661 | ||
2662 | @table @code | |
2663 | @kindex info threads | |
2664 | @item info threads | |
2665 | Display a summary of all threads currently in your | |
2666 | program. @value{GDBN} displays for each thread (in this order): | |
2667 | ||
2668 | @enumerate | |
09d4efe1 EZ |
2669 | @item |
2670 | the thread number assigned by @value{GDBN} | |
c906108c | 2671 | |
09d4efe1 EZ |
2672 | @item |
2673 | the target system's thread identifier (@var{systag}) | |
c906108c | 2674 | |
09d4efe1 EZ |
2675 | @item |
2676 | the current stack frame summary for that thread | |
c906108c SS |
2677 | @end enumerate |
2678 | ||
2679 | @noindent | |
2680 | An asterisk @samp{*} to the left of the @value{GDBN} thread number | |
2681 | indicates the current thread. | |
2682 | ||
5d161b24 | 2683 | For example, |
c906108c SS |
2684 | @end table |
2685 | @c end table here to get a little more width for example | |
2686 | ||
2687 | @smallexample | |
2688 | (@value{GDBP}) info threads | |
2689 | 3 process 35 thread 27 0x34e5 in sigpause () | |
2690 | 2 process 35 thread 23 0x34e5 in sigpause () | |
2691 | * 1 process 35 thread 13 main (argc=1, argv=0x7ffffff8) | |
2692 | at threadtest.c:68 | |
2693 | @end smallexample | |
53a5351d JM |
2694 | |
2695 | On HP-UX systems: | |
c906108c | 2696 | |
4644b6e3 EZ |
2697 | @cindex debugging multithreaded programs (on HP-UX) |
2698 | @cindex thread identifier (GDB), on HP-UX | |
c906108c SS |
2699 | For debugging purposes, @value{GDBN} associates its own thread |
2700 | number---a small integer assigned in thread-creation order---with each | |
2701 | thread in your program. | |
2702 | ||
41afff9a EZ |
2703 | @cindex @code{New} @var{systag} message, on HP-UX |
2704 | @cindex thread identifier (system), on HP-UX | |
c906108c SS |
2705 | @c FIXME-implementors!! It would be more helpful if the [New...] message |
2706 | @c included GDB's numeric thread handle, so you could just go to that | |
2707 | @c thread without first checking `info threads'. | |
2708 | Whenever @value{GDBN} detects a new thread in your program, it displays | |
2709 | both @value{GDBN}'s thread number and the target system's identification for the thread with a message in the | |
2710 | form @samp{[New @var{systag}]}. @var{systag} is a thread identifier | |
2711 | whose form varies depending on the particular system. For example, on | |
2712 | HP-UX, you see | |
2713 | ||
474c8240 | 2714 | @smallexample |
c906108c | 2715 | [New thread 2 (system thread 26594)] |
474c8240 | 2716 | @end smallexample |
c906108c SS |
2717 | |
2718 | @noindent | |
5d161b24 | 2719 | when @value{GDBN} notices a new thread. |
c906108c SS |
2720 | |
2721 | @table @code | |
4644b6e3 | 2722 | @kindex info threads (HP-UX) |
c906108c SS |
2723 | @item info threads |
2724 | Display a summary of all threads currently in your | |
2725 | program. @value{GDBN} displays for each thread (in this order): | |
2726 | ||
2727 | @enumerate | |
2728 | @item the thread number assigned by @value{GDBN} | |
2729 | ||
2730 | @item the target system's thread identifier (@var{systag}) | |
2731 | ||
2732 | @item the current stack frame summary for that thread | |
2733 | @end enumerate | |
2734 | ||
2735 | @noindent | |
2736 | An asterisk @samp{*} to the left of the @value{GDBN} thread number | |
2737 | indicates the current thread. | |
2738 | ||
5d161b24 | 2739 | For example, |
c906108c SS |
2740 | @end table |
2741 | @c end table here to get a little more width for example | |
2742 | ||
474c8240 | 2743 | @smallexample |
c906108c | 2744 | (@value{GDBP}) info threads |
6d2ebf8b SS |
2745 | * 3 system thread 26607 worker (wptr=0x7b09c318 "@@") \@* |
2746 | at quicksort.c:137 | |
2747 | 2 system thread 26606 0x7b0030d8 in __ksleep () \@* | |
2748 | from /usr/lib/libc.2 | |
2749 | 1 system thread 27905 0x7b003498 in _brk () \@* | |
2750 | from /usr/lib/libc.2 | |
474c8240 | 2751 | @end smallexample |
c906108c | 2752 | |
c45da7e6 EZ |
2753 | On Solaris, you can display more information about user threads with a |
2754 | Solaris-specific command: | |
2755 | ||
2756 | @table @code | |
2757 | @item maint info sol-threads | |
2758 | @kindex maint info sol-threads | |
2759 | @cindex thread info (Solaris) | |
2760 | Display info on Solaris user threads. | |
2761 | @end table | |
2762 | ||
c906108c SS |
2763 | @table @code |
2764 | @kindex thread @var{threadno} | |
2765 | @item thread @var{threadno} | |
2766 | Make thread number @var{threadno} the current thread. The command | |
2767 | argument @var{threadno} is the internal @value{GDBN} thread number, as | |
2768 | shown in the first field of the @samp{info threads} display. | |
2769 | @value{GDBN} responds by displaying the system identifier of the thread | |
2770 | you selected, and its current stack frame summary: | |
2771 | ||
2772 | @smallexample | |
2773 | @c FIXME!! This example made up; find a @value{GDBN} w/threads and get real one | |
2774 | (@value{GDBP}) thread 2 | |
c906108c | 2775 | [Switching to process 35 thread 23] |
c906108c SS |
2776 | 0x34e5 in sigpause () |
2777 | @end smallexample | |
2778 | ||
2779 | @noindent | |
2780 | As with the @samp{[New @dots{}]} message, the form of the text after | |
2781 | @samp{Switching to} depends on your system's conventions for identifying | |
5d161b24 | 2782 | threads. |
c906108c | 2783 | |
9c16f35a | 2784 | @kindex thread apply |
638ac427 | 2785 | @cindex apply command to several threads |
839c27b7 EZ |
2786 | @item thread apply [@var{threadno}] [@var{all}] @var{command} |
2787 | The @code{thread apply} command allows you to apply the named | |
2788 | @var{command} to one or more threads. Specify the numbers of the | |
2789 | threads that you want affected with the command argument | |
2790 | @var{threadno}. It can be a single thread number, one of the numbers | |
2791 | shown in the first field of the @samp{info threads} display; or it | |
2792 | could be a range of thread numbers, as in @code{2-4}. To apply a | |
2793 | command to all threads, type @kbd{thread apply all @var{command}}. | |
93815fbf VP |
2794 | |
2795 | @kindex set print thread-events | |
2796 | @cindex print messages on thread start and exit | |
2797 | @item set print thread-events | |
2798 | @itemx set print thread-events on | |
2799 | @itemx set print thread-events off | |
2800 | The @code{set print thread-events} command allows you to enable or | |
2801 | disable printing of messages when @value{GDBN} notices that new threads have | |
2802 | started or that threads have exited. By default, these messages will | |
2803 | be printed if detection of these events is supported by the target. | |
2804 | Note that these messages cannot be disabled on all targets. | |
2805 | ||
2806 | @kindex show print thread-events | |
2807 | @item show print thread-events | |
2808 | Show whether messages will be printed when @value{GDBN} detects that threads | |
2809 | have started and exited. | |
c906108c SS |
2810 | @end table |
2811 | ||
79a6e687 | 2812 | @xref{Thread Stops,,Stopping and Starting Multi-thread Programs}, for |
c906108c SS |
2813 | more information about how @value{GDBN} behaves when you stop and start |
2814 | programs with multiple threads. | |
2815 | ||
79a6e687 | 2816 | @xref{Set Watchpoints,,Setting Watchpoints}, for information about |
c906108c | 2817 | watchpoints in programs with multiple threads. |
c906108c | 2818 | |
17a37d48 PP |
2819 | @table @code |
2820 | @kindex set libthread-db-search-path | |
2821 | @cindex search path for @code{libthread_db} | |
2822 | @item set libthread-db-search-path @r{[}@var{path}@r{]} | |
2823 | If this variable is set, @var{path} is a colon-separated list of | |
2824 | directories @value{GDBN} will use to search for @code{libthread_db}. | |
2825 | If you omit @var{path}, @samp{libthread-db-search-path} will be reset to | |
2826 | an empty list. | |
2827 | ||
2828 | On @sc{gnu}/Linux and Solaris systems, @value{GDBN} uses a ``helper'' | |
2829 | @code{libthread_db} library to obtain information about threads in the | |
2830 | inferior process. @value{GDBN} will use @samp{libthread-db-search-path} | |
2831 | to find @code{libthread_db}. If that fails, @value{GDBN} will continue | |
2832 | with default system shared library directories, and finally the directory | |
2833 | from which @code{libpthread} was loaded in the inferior process. | |
2834 | ||
2835 | For any @code{libthread_db} library @value{GDBN} finds in above directories, | |
2836 | @value{GDBN} attempts to initialize it with the current inferior process. | |
2837 | If this initialization fails (which could happen because of a version | |
2838 | mismatch between @code{libthread_db} and @code{libpthread}), @value{GDBN} | |
2839 | will unload @code{libthread_db}, and continue with the next directory. | |
2840 | If none of @code{libthread_db} libraries initialize successfully, | |
2841 | @value{GDBN} will issue a warning and thread debugging will be disabled. | |
2842 | ||
2843 | Setting @code{libthread-db-search-path} is currently implemented | |
2844 | only on some platforms. | |
2845 | ||
2846 | @kindex show libthread-db-search-path | |
2847 | @item show libthread-db-search-path | |
2848 | Display current libthread_db search path. | |
2849 | @end table | |
2850 | ||
6c95b8df PA |
2851 | @node Forks |
2852 | @section Debugging Forks | |
c906108c SS |
2853 | |
2854 | @cindex fork, debugging programs which call | |
2855 | @cindex multiple processes | |
2856 | @cindex processes, multiple | |
53a5351d JM |
2857 | On most systems, @value{GDBN} has no special support for debugging |
2858 | programs which create additional processes using the @code{fork} | |
2859 | function. When a program forks, @value{GDBN} will continue to debug the | |
2860 | parent process and the child process will run unimpeded. If you have | |
2861 | set a breakpoint in any code which the child then executes, the child | |
2862 | will get a @code{SIGTRAP} signal which (unless it catches the signal) | |
2863 | will cause it to terminate. | |
c906108c SS |
2864 | |
2865 | However, if you want to debug the child process there is a workaround | |
2866 | which isn't too painful. Put a call to @code{sleep} in the code which | |
2867 | the child process executes after the fork. It may be useful to sleep | |
2868 | only if a certain environment variable is set, or a certain file exists, | |
2869 | so that the delay need not occur when you don't want to run @value{GDBN} | |
2870 | on the child. While the child is sleeping, use the @code{ps} program to | |
2871 | get its process ID. Then tell @value{GDBN} (a new invocation of | |
2872 | @value{GDBN} if you are also debugging the parent process) to attach to | |
d4f3574e | 2873 | the child process (@pxref{Attach}). From that point on you can debug |
c906108c | 2874 | the child process just like any other process which you attached to. |
c906108c | 2875 | |
b51970ac DJ |
2876 | On some systems, @value{GDBN} provides support for debugging programs that |
2877 | create additional processes using the @code{fork} or @code{vfork} functions. | |
2878 | Currently, the only platforms with this feature are HP-UX (11.x and later | |
a6b151f1 | 2879 | only?) and @sc{gnu}/Linux (kernel version 2.5.60 and later). |
c906108c SS |
2880 | |
2881 | By default, when a program forks, @value{GDBN} will continue to debug | |
2882 | the parent process and the child process will run unimpeded. | |
2883 | ||
2884 | If you want to follow the child process instead of the parent process, | |
2885 | use the command @w{@code{set follow-fork-mode}}. | |
2886 | ||
2887 | @table @code | |
2888 | @kindex set follow-fork-mode | |
2889 | @item set follow-fork-mode @var{mode} | |
2890 | Set the debugger response to a program call of @code{fork} or | |
2891 | @code{vfork}. A call to @code{fork} or @code{vfork} creates a new | |
9c16f35a | 2892 | process. The @var{mode} argument can be: |
c906108c SS |
2893 | |
2894 | @table @code | |
2895 | @item parent | |
2896 | The original process is debugged after a fork. The child process runs | |
2df3850c | 2897 | unimpeded. This is the default. |
c906108c SS |
2898 | |
2899 | @item child | |
2900 | The new process is debugged after a fork. The parent process runs | |
2901 | unimpeded. | |
2902 | ||
c906108c SS |
2903 | @end table |
2904 | ||
9c16f35a | 2905 | @kindex show follow-fork-mode |
c906108c | 2906 | @item show follow-fork-mode |
2df3850c | 2907 | Display the current debugger response to a @code{fork} or @code{vfork} call. |
c906108c SS |
2908 | @end table |
2909 | ||
5c95884b MS |
2910 | @cindex debugging multiple processes |
2911 | On Linux, if you want to debug both the parent and child processes, use the | |
2912 | command @w{@code{set detach-on-fork}}. | |
2913 | ||
2914 | @table @code | |
2915 | @kindex set detach-on-fork | |
2916 | @item set detach-on-fork @var{mode} | |
2917 | Tells gdb whether to detach one of the processes after a fork, or | |
2918 | retain debugger control over them both. | |
2919 | ||
2920 | @table @code | |
2921 | @item on | |
2922 | The child process (or parent process, depending on the value of | |
2923 | @code{follow-fork-mode}) will be detached and allowed to run | |
2924 | independently. This is the default. | |
2925 | ||
2926 | @item off | |
2927 | Both processes will be held under the control of @value{GDBN}. | |
2928 | One process (child or parent, depending on the value of | |
2929 | @code{follow-fork-mode}) is debugged as usual, while the other | |
2930 | is held suspended. | |
2931 | ||
2932 | @end table | |
2933 | ||
11310833 NR |
2934 | @kindex show detach-on-fork |
2935 | @item show detach-on-fork | |
2936 | Show whether detach-on-fork mode is on/off. | |
5c95884b MS |
2937 | @end table |
2938 | ||
2277426b PA |
2939 | If you choose to set @samp{detach-on-fork} mode off, then @value{GDBN} |
2940 | will retain control of all forked processes (including nested forks). | |
2941 | You can list the forked processes under the control of @value{GDBN} by | |
2942 | using the @w{@code{info inferiors}} command, and switch from one fork | |
6c95b8df PA |
2943 | to another by using the @code{inferior} command (@pxref{Inferiors and |
2944 | Programs, ,Debugging Multiple Inferiors and Programs}). | |
5c95884b MS |
2945 | |
2946 | To quit debugging one of the forked processes, you can either detach | |
2277426b PA |
2947 | from it by using the @w{@code{detach inferior}} command (allowing it |
2948 | to run independently), or kill it using the @w{@code{kill inferior}} | |
6c95b8df PA |
2949 | command. @xref{Inferiors and Programs, ,Debugging Multiple Inferiors |
2950 | and Programs}. | |
5c95884b | 2951 | |
c906108c SS |
2952 | If you ask to debug a child process and a @code{vfork} is followed by an |
2953 | @code{exec}, @value{GDBN} executes the new target up to the first | |
2954 | breakpoint in the new target. If you have a breakpoint set on | |
2955 | @code{main} in your original program, the breakpoint will also be set on | |
2956 | the child process's @code{main}. | |
2957 | ||
2277426b PA |
2958 | On some systems, when a child process is spawned by @code{vfork}, you |
2959 | cannot debug the child or parent until an @code{exec} call completes. | |
c906108c SS |
2960 | |
2961 | If you issue a @code{run} command to @value{GDBN} after an @code{exec} | |
6c95b8df PA |
2962 | call executes, the new target restarts. To restart the parent |
2963 | process, use the @code{file} command with the parent executable name | |
2964 | as its argument. By default, after an @code{exec} call executes, | |
2965 | @value{GDBN} discards the symbols of the previous executable image. | |
2966 | You can change this behaviour with the @w{@code{set follow-exec-mode}} | |
2967 | command. | |
2968 | ||
2969 | @table @code | |
2970 | @kindex set follow-exec-mode | |
2971 | @item set follow-exec-mode @var{mode} | |
2972 | ||
2973 | Set debugger response to a program call of @code{exec}. An | |
2974 | @code{exec} call replaces the program image of a process. | |
2975 | ||
2976 | @code{follow-exec-mode} can be: | |
2977 | ||
2978 | @table @code | |
2979 | @item new | |
2980 | @value{GDBN} creates a new inferior and rebinds the process to this | |
2981 | new inferior. The program the process was running before the | |
2982 | @code{exec} call can be restarted afterwards by restarting the | |
2983 | original inferior. | |
2984 | ||
2985 | For example: | |
2986 | ||
2987 | @smallexample | |
2988 | (@value{GDBP}) info inferiors | |
2989 | (gdb) info inferior | |
2990 | Id Description Executable | |
2991 | * 1 <null> prog1 | |
2992 | (@value{GDBP}) run | |
2993 | process 12020 is executing new program: prog2 | |
2994 | Program exited normally. | |
2995 | (@value{GDBP}) info inferiors | |
2996 | Id Description Executable | |
2997 | * 2 <null> prog2 | |
2998 | 1 <null> prog1 | |
2999 | @end smallexample | |
3000 | ||
3001 | @item same | |
3002 | @value{GDBN} keeps the process bound to the same inferior. The new | |
3003 | executable image replaces the previous executable loaded in the | |
3004 | inferior. Restarting the inferior after the @code{exec} call, with | |
3005 | e.g., the @code{run} command, restarts the executable the process was | |
3006 | running after the @code{exec} call. This is the default mode. | |
3007 | ||
3008 | For example: | |
3009 | ||
3010 | @smallexample | |
3011 | (@value{GDBP}) info inferiors | |
3012 | Id Description Executable | |
3013 | * 1 <null> prog1 | |
3014 | (@value{GDBP}) run | |
3015 | process 12020 is executing new program: prog2 | |
3016 | Program exited normally. | |
3017 | (@value{GDBP}) info inferiors | |
3018 | Id Description Executable | |
3019 | * 1 <null> prog2 | |
3020 | @end smallexample | |
3021 | ||
3022 | @end table | |
3023 | @end table | |
c906108c SS |
3024 | |
3025 | You can use the @code{catch} command to make @value{GDBN} stop whenever | |
3026 | a @code{fork}, @code{vfork}, or @code{exec} call is made. @xref{Set | |
79a6e687 | 3027 | Catchpoints, ,Setting Catchpoints}. |
c906108c | 3028 | |
5c95884b | 3029 | @node Checkpoint/Restart |
79a6e687 | 3030 | @section Setting a @emph{Bookmark} to Return to Later |
5c95884b MS |
3031 | |
3032 | @cindex checkpoint | |
3033 | @cindex restart | |
3034 | @cindex bookmark | |
3035 | @cindex snapshot of a process | |
3036 | @cindex rewind program state | |
3037 | ||
3038 | On certain operating systems@footnote{Currently, only | |
3039 | @sc{gnu}/Linux.}, @value{GDBN} is able to save a @dfn{snapshot} of a | |
3040 | program's state, called a @dfn{checkpoint}, and come back to it | |
3041 | later. | |
3042 | ||
3043 | Returning to a checkpoint effectively undoes everything that has | |
3044 | happened in the program since the @code{checkpoint} was saved. This | |
3045 | includes changes in memory, registers, and even (within some limits) | |
3046 | system state. Effectively, it is like going back in time to the | |
3047 | moment when the checkpoint was saved. | |
3048 | ||
3049 | Thus, if you're stepping thru a program and you think you're | |
3050 | getting close to the point where things go wrong, you can save | |
3051 | a checkpoint. Then, if you accidentally go too far and miss | |
3052 | the critical statement, instead of having to restart your program | |
3053 | from the beginning, you can just go back to the checkpoint and | |
3054 | start again from there. | |
3055 | ||
3056 | This can be especially useful if it takes a lot of time or | |
3057 | steps to reach the point where you think the bug occurs. | |
3058 | ||
3059 | To use the @code{checkpoint}/@code{restart} method of debugging: | |
3060 | ||
3061 | @table @code | |
3062 | @kindex checkpoint | |
3063 | @item checkpoint | |
3064 | Save a snapshot of the debugged program's current execution state. | |
3065 | The @code{checkpoint} command takes no arguments, but each checkpoint | |
3066 | is assigned a small integer id, similar to a breakpoint id. | |
3067 | ||
3068 | @kindex info checkpoints | |
3069 | @item info checkpoints | |
3070 | List the checkpoints that have been saved in the current debugging | |
3071 | session. For each checkpoint, the following information will be | |
3072 | listed: | |
3073 | ||
3074 | @table @code | |
3075 | @item Checkpoint ID | |
3076 | @item Process ID | |
3077 | @item Code Address | |
3078 | @item Source line, or label | |
3079 | @end table | |
3080 | ||
3081 | @kindex restart @var{checkpoint-id} | |
3082 | @item restart @var{checkpoint-id} | |
3083 | Restore the program state that was saved as checkpoint number | |
3084 | @var{checkpoint-id}. All program variables, registers, stack frames | |
3085 | etc.@: will be returned to the values that they had when the checkpoint | |
3086 | was saved. In essence, gdb will ``wind back the clock'' to the point | |
3087 | in time when the checkpoint was saved. | |
3088 | ||
3089 | Note that breakpoints, @value{GDBN} variables, command history etc. | |
3090 | are not affected by restoring a checkpoint. In general, a checkpoint | |
3091 | only restores things that reside in the program being debugged, not in | |
3092 | the debugger. | |
3093 | ||
b8db102d MS |
3094 | @kindex delete checkpoint @var{checkpoint-id} |
3095 | @item delete checkpoint @var{checkpoint-id} | |
5c95884b MS |
3096 | Delete the previously-saved checkpoint identified by @var{checkpoint-id}. |
3097 | ||
3098 | @end table | |
3099 | ||
3100 | Returning to a previously saved checkpoint will restore the user state | |
3101 | of the program being debugged, plus a significant subset of the system | |
3102 | (OS) state, including file pointers. It won't ``un-write'' data from | |
3103 | a file, but it will rewind the file pointer to the previous location, | |
3104 | so that the previously written data can be overwritten. For files | |
3105 | opened in read mode, the pointer will also be restored so that the | |
3106 | previously read data can be read again. | |
3107 | ||
3108 | Of course, characters that have been sent to a printer (or other | |
3109 | external device) cannot be ``snatched back'', and characters received | |
3110 | from eg.@: a serial device can be removed from internal program buffers, | |
3111 | but they cannot be ``pushed back'' into the serial pipeline, ready to | |
3112 | be received again. Similarly, the actual contents of files that have | |
3113 | been changed cannot be restored (at this time). | |
3114 | ||
3115 | However, within those constraints, you actually can ``rewind'' your | |
3116 | program to a previously saved point in time, and begin debugging it | |
3117 | again --- and you can change the course of events so as to debug a | |
3118 | different execution path this time. | |
3119 | ||
3120 | @cindex checkpoints and process id | |
3121 | Finally, there is one bit of internal program state that will be | |
3122 | different when you return to a checkpoint --- the program's process | |
3123 | id. Each checkpoint will have a unique process id (or @var{pid}), | |
3124 | and each will be different from the program's original @var{pid}. | |
3125 | If your program has saved a local copy of its process id, this could | |
3126 | potentially pose a problem. | |
3127 | ||
79a6e687 | 3128 | @subsection A Non-obvious Benefit of Using Checkpoints |
5c95884b MS |
3129 | |
3130 | On some systems such as @sc{gnu}/Linux, address space randomization | |
3131 | is performed on new processes for security reasons. This makes it | |
3132 | difficult or impossible to set a breakpoint, or watchpoint, on an | |
3133 | absolute address if you have to restart the program, since the | |
3134 | absolute location of a symbol will change from one execution to the | |
3135 | next. | |
3136 | ||
3137 | A checkpoint, however, is an @emph{identical} copy of a process. | |
3138 | Therefore if you create a checkpoint at (eg.@:) the start of main, | |
3139 | and simply return to that checkpoint instead of restarting the | |
3140 | process, you can avoid the effects of address randomization and | |
3141 | your symbols will all stay in the same place. | |
3142 | ||
6d2ebf8b | 3143 | @node Stopping |
c906108c SS |
3144 | @chapter Stopping and Continuing |
3145 | ||
3146 | The principal purposes of using a debugger are so that you can stop your | |
3147 | program before it terminates; or so that, if your program runs into | |
3148 | trouble, you can investigate and find out why. | |
3149 | ||
7a292a7a SS |
3150 | Inside @value{GDBN}, your program may stop for any of several reasons, |
3151 | such as a signal, a breakpoint, or reaching a new line after a | |
3152 | @value{GDBN} command such as @code{step}. You may then examine and | |
3153 | change variables, set new breakpoints or remove old ones, and then | |
3154 | continue execution. Usually, the messages shown by @value{GDBN} provide | |
3155 | ample explanation of the status of your program---but you can also | |
3156 | explicitly request this information at any time. | |
c906108c SS |
3157 | |
3158 | @table @code | |
3159 | @kindex info program | |
3160 | @item info program | |
3161 | Display information about the status of your program: whether it is | |
7a292a7a | 3162 | running or not, what process it is, and why it stopped. |
c906108c SS |
3163 | @end table |
3164 | ||
3165 | @menu | |
3166 | * Breakpoints:: Breakpoints, watchpoints, and catchpoints | |
3167 | * Continuing and Stepping:: Resuming execution | |
c906108c | 3168 | * Signals:: Signals |
c906108c | 3169 | * Thread Stops:: Stopping and starting multi-thread programs |
c906108c SS |
3170 | @end menu |
3171 | ||
6d2ebf8b | 3172 | @node Breakpoints |
79a6e687 | 3173 | @section Breakpoints, Watchpoints, and Catchpoints |
c906108c SS |
3174 | |
3175 | @cindex breakpoints | |
3176 | A @dfn{breakpoint} makes your program stop whenever a certain point in | |
3177 | the program is reached. For each breakpoint, you can add conditions to | |
3178 | control in finer detail whether your program stops. You can set | |
3179 | breakpoints with the @code{break} command and its variants (@pxref{Set | |
79a6e687 | 3180 | Breaks, ,Setting Breakpoints}), to specify the place where your program |
c906108c SS |
3181 | should stop by line number, function name or exact address in the |
3182 | program. | |
3183 | ||
09d4efe1 EZ |
3184 | On some systems, you can set breakpoints in shared libraries before |
3185 | the executable is run. There is a minor limitation on HP-UX systems: | |
3186 | you must wait until the executable is run in order to set breakpoints | |
3187 | in shared library routines that are not called directly by the program | |
3188 | (for example, routines that are arguments in a @code{pthread_create} | |
3189 | call). | |
c906108c SS |
3190 | |
3191 | @cindex watchpoints | |
fd60e0df | 3192 | @cindex data breakpoints |
c906108c SS |
3193 | @cindex memory tracing |
3194 | @cindex breakpoint on memory address | |
3195 | @cindex breakpoint on variable modification | |
3196 | A @dfn{watchpoint} is a special breakpoint that stops your program | |
fd60e0df | 3197 | when the value of an expression changes. The expression may be a value |
0ced0c34 | 3198 | of a variable, or it could involve values of one or more variables |
fd60e0df EZ |
3199 | combined by operators, such as @samp{a + b}. This is sometimes called |
3200 | @dfn{data breakpoints}. You must use a different command to set | |
79a6e687 | 3201 | watchpoints (@pxref{Set Watchpoints, ,Setting Watchpoints}), but aside |
fd60e0df EZ |
3202 | from that, you can manage a watchpoint like any other breakpoint: you |
3203 | enable, disable, and delete both breakpoints and watchpoints using the | |
3204 | same commands. | |
c906108c SS |
3205 | |
3206 | You can arrange to have values from your program displayed automatically | |
3207 | whenever @value{GDBN} stops at a breakpoint. @xref{Auto Display,, | |
79a6e687 | 3208 | Automatic Display}. |
c906108c SS |
3209 | |
3210 | @cindex catchpoints | |
3211 | @cindex breakpoint on events | |
3212 | A @dfn{catchpoint} is another special breakpoint that stops your program | |
b37052ae | 3213 | when a certain kind of event occurs, such as the throwing of a C@t{++} |
c906108c SS |
3214 | exception or the loading of a library. As with watchpoints, you use a |
3215 | different command to set a catchpoint (@pxref{Set Catchpoints, ,Setting | |
79a6e687 | 3216 | Catchpoints}), but aside from that, you can manage a catchpoint like any |
c906108c | 3217 | other breakpoint. (To stop when your program receives a signal, use the |
d4f3574e | 3218 | @code{handle} command; see @ref{Signals, ,Signals}.) |
c906108c SS |
3219 | |
3220 | @cindex breakpoint numbers | |
3221 | @cindex numbers for breakpoints | |
3222 | @value{GDBN} assigns a number to each breakpoint, watchpoint, or | |
3223 | catchpoint when you create it; these numbers are successive integers | |
3224 | starting with one. In many of the commands for controlling various | |
3225 | features of breakpoints you use the breakpoint number to say which | |
3226 | breakpoint you want to change. Each breakpoint may be @dfn{enabled} or | |
3227 | @dfn{disabled}; if disabled, it has no effect on your program until you | |
3228 | enable it again. | |
3229 | ||
c5394b80 JM |
3230 | @cindex breakpoint ranges |
3231 | @cindex ranges of breakpoints | |
3232 | Some @value{GDBN} commands accept a range of breakpoints on which to | |
3233 | operate. A breakpoint range is either a single breakpoint number, like | |
3234 | @samp{5}, or two such numbers, in increasing order, separated by a | |
3235 | hyphen, like @samp{5-7}. When a breakpoint range is given to a command, | |
d52fb0e9 | 3236 | all breakpoints in that range are operated on. |
c5394b80 | 3237 | |
c906108c SS |
3238 | @menu |
3239 | * Set Breaks:: Setting breakpoints | |
3240 | * Set Watchpoints:: Setting watchpoints | |
3241 | * Set Catchpoints:: Setting catchpoints | |
3242 | * Delete Breaks:: Deleting breakpoints | |
3243 | * Disabling:: Disabling breakpoints | |
3244 | * Conditions:: Break conditions | |
3245 | * Break Commands:: Breakpoint command lists | |
d4f3574e | 3246 | * Error in Breakpoints:: ``Cannot insert breakpoints'' |
79a6e687 | 3247 | * Breakpoint-related Warnings:: ``Breakpoint address adjusted...'' |
c906108c SS |
3248 | @end menu |
3249 | ||
6d2ebf8b | 3250 | @node Set Breaks |
79a6e687 | 3251 | @subsection Setting Breakpoints |
c906108c | 3252 | |
5d161b24 | 3253 | @c FIXME LMB what does GDB do if no code on line of breakpt? |
c906108c SS |
3254 | @c consider in particular declaration with/without initialization. |
3255 | @c | |
3256 | @c FIXME 2 is there stuff on this already? break at fun start, already init? | |
3257 | ||
3258 | @kindex break | |
41afff9a EZ |
3259 | @kindex b @r{(@code{break})} |
3260 | @vindex $bpnum@r{, convenience variable} | |
c906108c SS |
3261 | @cindex latest breakpoint |
3262 | Breakpoints are set with the @code{break} command (abbreviated | |
5d161b24 | 3263 | @code{b}). The debugger convenience variable @samp{$bpnum} records the |
f3b28801 | 3264 | number of the breakpoint you've set most recently; see @ref{Convenience |
79a6e687 | 3265 | Vars,, Convenience Variables}, for a discussion of what you can do with |
c906108c SS |
3266 | convenience variables. |
3267 | ||
c906108c | 3268 | @table @code |
2a25a5ba EZ |
3269 | @item break @var{location} |
3270 | Set a breakpoint at the given @var{location}, which can specify a | |
3271 | function name, a line number, or an address of an instruction. | |
3272 | (@xref{Specify Location}, for a list of all the possible ways to | |
3273 | specify a @var{location}.) The breakpoint will stop your program just | |
3274 | before it executes any of the code in the specified @var{location}. | |
3275 | ||
c906108c | 3276 | When using source languages that permit overloading of symbols, such as |
2a25a5ba | 3277 | C@t{++}, a function name may refer to more than one possible place to break. |
6ba66d6a JB |
3278 | @xref{Ambiguous Expressions,,Ambiguous Expressions}, for a discussion of |
3279 | that situation. | |
c906108c | 3280 | |
45ac276d | 3281 | It is also possible to insert a breakpoint that will stop the program |
2c88c651 JB |
3282 | only if a specific thread (@pxref{Thread-Specific Breakpoints}) |
3283 | or a specific task (@pxref{Ada Tasks}) hits that breakpoint. | |
45ac276d | 3284 | |
c906108c SS |
3285 | @item break |
3286 | When called without any arguments, @code{break} sets a breakpoint at | |
3287 | the next instruction to be executed in the selected stack frame | |
3288 | (@pxref{Stack, ,Examining the Stack}). In any selected frame but the | |
3289 | innermost, this makes your program stop as soon as control | |
3290 | returns to that frame. This is similar to the effect of a | |
3291 | @code{finish} command in the frame inside the selected frame---except | |
3292 | that @code{finish} does not leave an active breakpoint. If you use | |
3293 | @code{break} without an argument in the innermost frame, @value{GDBN} stops | |
3294 | the next time it reaches the current location; this may be useful | |
3295 | inside loops. | |
3296 | ||
3297 | @value{GDBN} normally ignores breakpoints when it resumes execution, until at | |
3298 | least one instruction has been executed. If it did not do this, you | |
3299 | would be unable to proceed past a breakpoint without first disabling the | |
3300 | breakpoint. This rule applies whether or not the breakpoint already | |
3301 | existed when your program stopped. | |
3302 | ||
3303 | @item break @dots{} if @var{cond} | |
3304 | Set a breakpoint with condition @var{cond}; evaluate the expression | |
3305 | @var{cond} each time the breakpoint is reached, and stop only if the | |
3306 | value is nonzero---that is, if @var{cond} evaluates as true. | |
3307 | @samp{@dots{}} stands for one of the possible arguments described | |
3308 | above (or no argument) specifying where to break. @xref{Conditions, | |
79a6e687 | 3309 | ,Break Conditions}, for more information on breakpoint conditions. |
c906108c SS |
3310 | |
3311 | @kindex tbreak | |
3312 | @item tbreak @var{args} | |
3313 | Set a breakpoint enabled only for one stop. @var{args} are the | |
3314 | same as for the @code{break} command, and the breakpoint is set in the same | |
3315 | way, but the breakpoint is automatically deleted after the first time your | |
79a6e687 | 3316 | program stops there. @xref{Disabling, ,Disabling Breakpoints}. |
c906108c | 3317 | |
c906108c | 3318 | @kindex hbreak |
ba04e063 | 3319 | @cindex hardware breakpoints |
c906108c | 3320 | @item hbreak @var{args} |
d4f3574e SS |
3321 | Set a hardware-assisted breakpoint. @var{args} are the same as for the |
3322 | @code{break} command and the breakpoint is set in the same way, but the | |
c906108c SS |
3323 | breakpoint requires hardware support and some target hardware may not |
3324 | have this support. The main purpose of this is EPROM/ROM code | |
d4f3574e SS |
3325 | debugging, so you can set a breakpoint at an instruction without |
3326 | changing the instruction. This can be used with the new trap-generation | |
09d4efe1 | 3327 | provided by SPARClite DSU and most x86-based targets. These targets |
d4f3574e SS |
3328 | will generate traps when a program accesses some data or instruction |
3329 | address that is assigned to the debug registers. However the hardware | |
3330 | breakpoint registers can take a limited number of breakpoints. For | |
3331 | example, on the DSU, only two data breakpoints can be set at a time, and | |
3332 | @value{GDBN} will reject this command if more than two are used. Delete | |
3333 | or disable unused hardware breakpoints before setting new ones | |
79a6e687 BW |
3334 | (@pxref{Disabling, ,Disabling Breakpoints}). |
3335 | @xref{Conditions, ,Break Conditions}. | |
9c16f35a EZ |
3336 | For remote targets, you can restrict the number of hardware |
3337 | breakpoints @value{GDBN} will use, see @ref{set remote | |
3338 | hardware-breakpoint-limit}. | |
501eef12 | 3339 | |
c906108c SS |
3340 | @kindex thbreak |
3341 | @item thbreak @var{args} | |
3342 | Set a hardware-assisted breakpoint enabled only for one stop. @var{args} | |
3343 | are the same as for the @code{hbreak} command and the breakpoint is set in | |
5d161b24 | 3344 | the same way. However, like the @code{tbreak} command, |
c906108c SS |
3345 | the breakpoint is automatically deleted after the |
3346 | first time your program stops there. Also, like the @code{hbreak} | |
5d161b24 | 3347 | command, the breakpoint requires hardware support and some target hardware |
79a6e687 BW |
3348 | may not have this support. @xref{Disabling, ,Disabling Breakpoints}. |
3349 | See also @ref{Conditions, ,Break Conditions}. | |
c906108c SS |
3350 | |
3351 | @kindex rbreak | |
3352 | @cindex regular expression | |
c45da7e6 EZ |
3353 | @cindex breakpoints in functions matching a regexp |
3354 | @cindex set breakpoints in many functions | |
c906108c | 3355 | @item rbreak @var{regex} |
c906108c | 3356 | Set breakpoints on all functions matching the regular expression |
11cf8741 JM |
3357 | @var{regex}. This command sets an unconditional breakpoint on all |
3358 | matches, printing a list of all breakpoints it set. Once these | |
3359 | breakpoints are set, they are treated just like the breakpoints set with | |
3360 | the @code{break} command. You can delete them, disable them, or make | |
3361 | them conditional the same way as any other breakpoint. | |
3362 | ||
3363 | The syntax of the regular expression is the standard one used with tools | |
3364 | like @file{grep}. Note that this is different from the syntax used by | |
3365 | shells, so for instance @code{foo*} matches all functions that include | |
3366 | an @code{fo} followed by zero or more @code{o}s. There is an implicit | |
3367 | @code{.*} leading and trailing the regular expression you supply, so to | |
3368 | match only functions that begin with @code{foo}, use @code{^foo}. | |
c906108c | 3369 | |
f7dc1244 | 3370 | @cindex non-member C@t{++} functions, set breakpoint in |
b37052ae | 3371 | When debugging C@t{++} programs, @code{rbreak} is useful for setting |
c906108c SS |
3372 | breakpoints on overloaded functions that are not members of any special |
3373 | classes. | |
c906108c | 3374 | |
f7dc1244 EZ |
3375 | @cindex set breakpoints on all functions |
3376 | The @code{rbreak} command can be used to set breakpoints in | |
3377 | @strong{all} the functions in a program, like this: | |
3378 | ||
3379 | @smallexample | |
3380 | (@value{GDBP}) rbreak . | |
3381 | @end smallexample | |
3382 | ||
c906108c SS |
3383 | @kindex info breakpoints |
3384 | @cindex @code{$_} and @code{info breakpoints} | |
3385 | @item info breakpoints @r{[}@var{n}@r{]} | |
3386 | @itemx info break @r{[}@var{n}@r{]} | |
3387 | @itemx info watchpoints @r{[}@var{n}@r{]} | |
3388 | Print a table of all breakpoints, watchpoints, and catchpoints set and | |
45ac1734 EZ |
3389 | not deleted. Optional argument @var{n} means print information only |
3390 | about the specified breakpoint (or watchpoint or catchpoint). For | |
3391 | each breakpoint, following columns are printed: | |
c906108c SS |
3392 | |
3393 | @table @emph | |
3394 | @item Breakpoint Numbers | |
3395 | @item Type | |
3396 | Breakpoint, watchpoint, or catchpoint. | |
3397 | @item Disposition | |
3398 | Whether the breakpoint is marked to be disabled or deleted when hit. | |
3399 | @item Enabled or Disabled | |
3400 | Enabled breakpoints are marked with @samp{y}. @samp{n} marks breakpoints | |
b3db7447 | 3401 | that are not enabled. |
c906108c | 3402 | @item Address |
fe6fbf8b | 3403 | Where the breakpoint is in your program, as a memory address. For a |
b3db7447 NR |
3404 | pending breakpoint whose address is not yet known, this field will |
3405 | contain @samp{<PENDING>}. Such breakpoint won't fire until a shared | |
3406 | library that has the symbol or line referred by breakpoint is loaded. | |
3407 | See below for details. A breakpoint with several locations will | |
3b784c4f | 3408 | have @samp{<MULTIPLE>} in this field---see below for details. |
c906108c SS |
3409 | @item What |
3410 | Where the breakpoint is in the source for your program, as a file and | |
2650777c JJ |
3411 | line number. For a pending breakpoint, the original string passed to |
3412 | the breakpoint command will be listed as it cannot be resolved until | |
3413 | the appropriate shared library is loaded in the future. | |
c906108c SS |
3414 | @end table |
3415 | ||
3416 | @noindent | |
3417 | If a breakpoint is conditional, @code{info break} shows the condition on | |
3418 | the line following the affected breakpoint; breakpoint commands, if any, | |
2650777c JJ |
3419 | are listed after that. A pending breakpoint is allowed to have a condition |
3420 | specified for it. The condition is not parsed for validity until a shared | |
3421 | library is loaded that allows the pending breakpoint to resolve to a | |
3422 | valid location. | |
c906108c SS |
3423 | |
3424 | @noindent | |
3425 | @code{info break} with a breakpoint | |
3426 | number @var{n} as argument lists only that breakpoint. The | |
3427 | convenience variable @code{$_} and the default examining-address for | |
3428 | the @code{x} command are set to the address of the last breakpoint | |
79a6e687 | 3429 | listed (@pxref{Memory, ,Examining Memory}). |
c906108c SS |
3430 | |
3431 | @noindent | |
3432 | @code{info break} displays a count of the number of times the breakpoint | |
3433 | has been hit. This is especially useful in conjunction with the | |
3434 | @code{ignore} command. You can ignore a large number of breakpoint | |
3435 | hits, look at the breakpoint info to see how many times the breakpoint | |
3436 | was hit, and then run again, ignoring one less than that number. This | |
3437 | will get you quickly to the last hit of that breakpoint. | |
3438 | @end table | |
3439 | ||
3440 | @value{GDBN} allows you to set any number of breakpoints at the same place in | |
3441 | your program. There is nothing silly or meaningless about this. When | |
3442 | the breakpoints are conditional, this is even useful | |
79a6e687 | 3443 | (@pxref{Conditions, ,Break Conditions}). |
c906108c | 3444 | |
2e9132cc EZ |
3445 | @cindex multiple locations, breakpoints |
3446 | @cindex breakpoints, multiple locations | |
fcda367b | 3447 | It is possible that a breakpoint corresponds to several locations |
fe6fbf8b VP |
3448 | in your program. Examples of this situation are: |
3449 | ||
3450 | @itemize @bullet | |
fe6fbf8b VP |
3451 | @item |
3452 | For a C@t{++} constructor, the @value{NGCC} compiler generates several | |
3453 | instances of the function body, used in different cases. | |
3454 | ||
3455 | @item | |
3456 | For a C@t{++} template function, a given line in the function can | |
3457 | correspond to any number of instantiations. | |
3458 | ||
3459 | @item | |
3460 | For an inlined function, a given source line can correspond to | |
3461 | several places where that function is inlined. | |
fe6fbf8b VP |
3462 | @end itemize |
3463 | ||
3464 | In all those cases, @value{GDBN} will insert a breakpoint at all | |
2e9132cc EZ |
3465 | the relevant locations@footnote{ |
3466 | As of this writing, multiple-location breakpoints work only if there's | |
3467 | line number information for all the locations. This means that they | |
3468 | will generally not work in system libraries, unless you have debug | |
3469 | info with line numbers for them.}. | |
fe6fbf8b | 3470 | |
3b784c4f EZ |
3471 | A breakpoint with multiple locations is displayed in the breakpoint |
3472 | table using several rows---one header row, followed by one row for | |
3473 | each breakpoint location. The header row has @samp{<MULTIPLE>} in the | |
3474 | address column. The rows for individual locations contain the actual | |
3475 | addresses for locations, and show the functions to which those | |
3476 | locations belong. The number column for a location is of the form | |
fe6fbf8b VP |
3477 | @var{breakpoint-number}.@var{location-number}. |
3478 | ||
3479 | For example: | |
3b784c4f | 3480 | |
fe6fbf8b VP |
3481 | @smallexample |
3482 | Num Type Disp Enb Address What | |
3483 | 1 breakpoint keep y <MULTIPLE> | |
3484 | stop only if i==1 | |
3485 | breakpoint already hit 1 time | |
3486 | 1.1 y 0x080486a2 in void foo<int>() at t.cc:8 | |
3487 | 1.2 y 0x080486ca in void foo<double>() at t.cc:8 | |
3488 | @end smallexample | |
3489 | ||
3490 | Each location can be individually enabled or disabled by passing | |
3491 | @var{breakpoint-number}.@var{location-number} as argument to the | |
3b784c4f EZ |
3492 | @code{enable} and @code{disable} commands. Note that you cannot |
3493 | delete the individual locations from the list, you can only delete the | |
16bfc218 | 3494 | entire list of locations that belong to their parent breakpoint (with |
3b784c4f EZ |
3495 | the @kbd{delete @var{num}} command, where @var{num} is the number of |
3496 | the parent breakpoint, 1 in the above example). Disabling or enabling | |
3497 | the parent breakpoint (@pxref{Disabling}) affects all of the locations | |
3498 | that belong to that breakpoint. | |
fe6fbf8b | 3499 | |
2650777c | 3500 | @cindex pending breakpoints |
fe6fbf8b | 3501 | It's quite common to have a breakpoint inside a shared library. |
3b784c4f | 3502 | Shared libraries can be loaded and unloaded explicitly, |
fe6fbf8b VP |
3503 | and possibly repeatedly, as the program is executed. To support |
3504 | this use case, @value{GDBN} updates breakpoint locations whenever | |
3505 | any shared library is loaded or unloaded. Typically, you would | |
fcda367b | 3506 | set a breakpoint in a shared library at the beginning of your |
fe6fbf8b VP |
3507 | debugging session, when the library is not loaded, and when the |
3508 | symbols from the library are not available. When you try to set | |
3509 | breakpoint, @value{GDBN} will ask you if you want to set | |
3b784c4f | 3510 | a so called @dfn{pending breakpoint}---breakpoint whose address |
fe6fbf8b VP |
3511 | is not yet resolved. |
3512 | ||
3513 | After the program is run, whenever a new shared library is loaded, | |
3514 | @value{GDBN} reevaluates all the breakpoints. When a newly loaded | |
3515 | shared library contains the symbol or line referred to by some | |
3516 | pending breakpoint, that breakpoint is resolved and becomes an | |
3517 | ordinary breakpoint. When a library is unloaded, all breakpoints | |
3518 | that refer to its symbols or source lines become pending again. | |
3519 | ||
3520 | This logic works for breakpoints with multiple locations, too. For | |
3521 | example, if you have a breakpoint in a C@t{++} template function, and | |
3522 | a newly loaded shared library has an instantiation of that template, | |
3523 | a new location is added to the list of locations for the breakpoint. | |
3524 | ||
3525 | Except for having unresolved address, pending breakpoints do not | |
3526 | differ from regular breakpoints. You can set conditions or commands, | |
3527 | enable and disable them and perform other breakpoint operations. | |
3528 | ||
3529 | @value{GDBN} provides some additional commands for controlling what | |
3530 | happens when the @samp{break} command cannot resolve breakpoint | |
3531 | address specification to an address: | |
dd79a6cf JJ |
3532 | |
3533 | @kindex set breakpoint pending | |
3534 | @kindex show breakpoint pending | |
3535 | @table @code | |
3536 | @item set breakpoint pending auto | |
3537 | This is the default behavior. When @value{GDBN} cannot find the breakpoint | |
3538 | location, it queries you whether a pending breakpoint should be created. | |
3539 | ||
3540 | @item set breakpoint pending on | |
3541 | This indicates that an unrecognized breakpoint location should automatically | |
3542 | result in a pending breakpoint being created. | |
3543 | ||
3544 | @item set breakpoint pending off | |
3545 | This indicates that pending breakpoints are not to be created. Any | |
3546 | unrecognized breakpoint location results in an error. This setting does | |
3547 | not affect any pending breakpoints previously created. | |
3548 | ||
3549 | @item show breakpoint pending | |
3550 | Show the current behavior setting for creating pending breakpoints. | |
3551 | @end table | |
2650777c | 3552 | |
fe6fbf8b VP |
3553 | The settings above only affect the @code{break} command and its |
3554 | variants. Once breakpoint is set, it will be automatically updated | |
3555 | as shared libraries are loaded and unloaded. | |
2650777c | 3556 | |
765dc015 VP |
3557 | @cindex automatic hardware breakpoints |
3558 | For some targets, @value{GDBN} can automatically decide if hardware or | |
3559 | software breakpoints should be used, depending on whether the | |
3560 | breakpoint address is read-only or read-write. This applies to | |
3561 | breakpoints set with the @code{break} command as well as to internal | |
3562 | breakpoints set by commands like @code{next} and @code{finish}. For | |
fcda367b | 3563 | breakpoints set with @code{hbreak}, @value{GDBN} will always use hardware |
765dc015 VP |
3564 | breakpoints. |
3565 | ||
3566 | You can control this automatic behaviour with the following commands:: | |
3567 | ||
3568 | @kindex set breakpoint auto-hw | |
3569 | @kindex show breakpoint auto-hw | |
3570 | @table @code | |
3571 | @item set breakpoint auto-hw on | |
3572 | This is the default behavior. When @value{GDBN} sets a breakpoint, it | |
3573 | will try to use the target memory map to decide if software or hardware | |
3574 | breakpoint must be used. | |
3575 | ||
3576 | @item set breakpoint auto-hw off | |
3577 | This indicates @value{GDBN} should not automatically select breakpoint | |
3578 | type. If the target provides a memory map, @value{GDBN} will warn when | |
3579 | trying to set software breakpoint at a read-only address. | |
3580 | @end table | |
3581 | ||
74960c60 VP |
3582 | @value{GDBN} normally implements breakpoints by replacing the program code |
3583 | at the breakpoint address with a special instruction, which, when | |
3584 | executed, given control to the debugger. By default, the program | |
3585 | code is so modified only when the program is resumed. As soon as | |
3586 | the program stops, @value{GDBN} restores the original instructions. This | |
3587 | behaviour guards against leaving breakpoints inserted in the | |
3588 | target should gdb abrubptly disconnect. However, with slow remote | |
3589 | targets, inserting and removing breakpoint can reduce the performance. | |
3590 | This behavior can be controlled with the following commands:: | |
3591 | ||
3592 | @kindex set breakpoint always-inserted | |
3593 | @kindex show breakpoint always-inserted | |
3594 | @table @code | |
3595 | @item set breakpoint always-inserted off | |
33e5cbd6 PA |
3596 | All breakpoints, including newly added by the user, are inserted in |
3597 | the target only when the target is resumed. All breakpoints are | |
3598 | removed from the target when it stops. | |
74960c60 VP |
3599 | |
3600 | @item set breakpoint always-inserted on | |
3601 | Causes all breakpoints to be inserted in the target at all times. If | |
3602 | the user adds a new breakpoint, or changes an existing breakpoint, the | |
3603 | breakpoints in the target are updated immediately. A breakpoint is | |
3604 | removed from the target only when breakpoint itself is removed. | |
33e5cbd6 PA |
3605 | |
3606 | @cindex non-stop mode, and @code{breakpoint always-inserted} | |
3607 | @item set breakpoint always-inserted auto | |
3608 | This is the default mode. If @value{GDBN} is controlling the inferior | |
3609 | in non-stop mode (@pxref{Non-Stop Mode}), gdb behaves as if | |
3610 | @code{breakpoint always-inserted} mode is on. If @value{GDBN} is | |
3611 | controlling the inferior in all-stop mode, @value{GDBN} behaves as if | |
3612 | @code{breakpoint always-inserted} mode is off. | |
74960c60 | 3613 | @end table |
765dc015 | 3614 | |
c906108c SS |
3615 | @cindex negative breakpoint numbers |
3616 | @cindex internal @value{GDBN} breakpoints | |
eb12ee30 AC |
3617 | @value{GDBN} itself sometimes sets breakpoints in your program for |
3618 | special purposes, such as proper handling of @code{longjmp} (in C | |
3619 | programs). These internal breakpoints are assigned negative numbers, | |
3620 | starting with @code{-1}; @samp{info breakpoints} does not display them. | |
c906108c | 3621 | You can see these breakpoints with the @value{GDBN} maintenance command |
eb12ee30 | 3622 | @samp{maint info breakpoints} (@pxref{maint info breakpoints}). |
c906108c SS |
3623 | |
3624 | ||
6d2ebf8b | 3625 | @node Set Watchpoints |
79a6e687 | 3626 | @subsection Setting Watchpoints |
c906108c SS |
3627 | |
3628 | @cindex setting watchpoints | |
c906108c SS |
3629 | You can use a watchpoint to stop execution whenever the value of an |
3630 | expression changes, without having to predict a particular place where | |
fd60e0df EZ |
3631 | this may happen. (This is sometimes called a @dfn{data breakpoint}.) |
3632 | The expression may be as simple as the value of a single variable, or | |
3633 | as complex as many variables combined by operators. Examples include: | |
3634 | ||
3635 | @itemize @bullet | |
3636 | @item | |
3637 | A reference to the value of a single variable. | |
3638 | ||
3639 | @item | |
3640 | An address cast to an appropriate data type. For example, | |
3641 | @samp{*(int *)0x12345678} will watch a 4-byte region at the specified | |
3642 | address (assuming an @code{int} occupies 4 bytes). | |
3643 | ||
3644 | @item | |
3645 | An arbitrarily complex expression, such as @samp{a*b + c/d}. The | |
3646 | expression can use any operators valid in the program's native | |
3647 | language (@pxref{Languages}). | |
3648 | @end itemize | |
c906108c | 3649 | |
fa4727a6 DJ |
3650 | You can set a watchpoint on an expression even if the expression can |
3651 | not be evaluated yet. For instance, you can set a watchpoint on | |
3652 | @samp{*global_ptr} before @samp{global_ptr} is initialized. | |
3653 | @value{GDBN} will stop when your program sets @samp{global_ptr} and | |
3654 | the expression produces a valid value. If the expression becomes | |
3655 | valid in some other way than changing a variable (e.g.@: if the memory | |
3656 | pointed to by @samp{*global_ptr} becomes readable as the result of a | |
3657 | @code{malloc} call), @value{GDBN} may not stop until the next time | |
3658 | the expression changes. | |
3659 | ||
82f2d802 EZ |
3660 | @cindex software watchpoints |
3661 | @cindex hardware watchpoints | |
c906108c | 3662 | Depending on your system, watchpoints may be implemented in software or |
2df3850c | 3663 | hardware. @value{GDBN} does software watchpointing by single-stepping your |
c906108c SS |
3664 | program and testing the variable's value each time, which is hundreds of |
3665 | times slower than normal execution. (But this may still be worth it, to | |
3666 | catch errors where you have no clue what part of your program is the | |
3667 | culprit.) | |
3668 | ||
37e4754d | 3669 | On some systems, such as HP-UX, PowerPC, @sc{gnu}/Linux and most other |
82f2d802 EZ |
3670 | x86-based targets, @value{GDBN} includes support for hardware |
3671 | watchpoints, which do not slow down the running of your program. | |
c906108c SS |
3672 | |
3673 | @table @code | |
3674 | @kindex watch | |
d8b2a693 | 3675 | @item watch @var{expr} @r{[}thread @var{threadnum}@r{]} |
fd60e0df EZ |
3676 | Set a watchpoint for an expression. @value{GDBN} will break when the |
3677 | expression @var{expr} is written into by the program and its value | |
3678 | changes. The simplest (and the most popular) use of this command is | |
3679 | to watch the value of a single variable: | |
3680 | ||
3681 | @smallexample | |
3682 | (@value{GDBP}) watch foo | |
3683 | @end smallexample | |
c906108c | 3684 | |
d8b2a693 JB |
3685 | If the command includes a @code{@r{[}thread @var{threadnum}@r{]}} |
3686 | clause, @value{GDBN} breaks only when the thread identified by | |
3687 | @var{threadnum} changes the value of @var{expr}. If any other threads | |
3688 | change the value of @var{expr}, @value{GDBN} will not break. Note | |
3689 | that watchpoints restricted to a single thread in this way only work | |
3690 | with Hardware Watchpoints. | |
3691 | ||
c906108c | 3692 | @kindex rwatch |
d8b2a693 | 3693 | @item rwatch @var{expr} @r{[}thread @var{threadnum}@r{]} |
09d4efe1 EZ |
3694 | Set a watchpoint that will break when the value of @var{expr} is read |
3695 | by the program. | |
c906108c SS |
3696 | |
3697 | @kindex awatch | |
d8b2a693 | 3698 | @item awatch @var{expr} @r{[}thread @var{threadnum}@r{]} |
09d4efe1 EZ |
3699 | Set a watchpoint that will break when @var{expr} is either read from |
3700 | or written into by the program. | |
c906108c | 3701 | |
45ac1734 | 3702 | @kindex info watchpoints @r{[}@var{n}@r{]} |
c906108c SS |
3703 | @item info watchpoints |
3704 | This command prints a list of watchpoints, breakpoints, and catchpoints; | |
09d4efe1 | 3705 | it is the same as @code{info break} (@pxref{Set Breaks}). |
c906108c SS |
3706 | @end table |
3707 | ||
3708 | @value{GDBN} sets a @dfn{hardware watchpoint} if possible. Hardware | |
3709 | watchpoints execute very quickly, and the debugger reports a change in | |
3710 | value at the exact instruction where the change occurs. If @value{GDBN} | |
3711 | cannot set a hardware watchpoint, it sets a software watchpoint, which | |
3712 | executes more slowly and reports the change in value at the next | |
82f2d802 EZ |
3713 | @emph{statement}, not the instruction, after the change occurs. |
3714 | ||
82f2d802 EZ |
3715 | @cindex use only software watchpoints |
3716 | You can force @value{GDBN} to use only software watchpoints with the | |
3717 | @kbd{set can-use-hw-watchpoints 0} command. With this variable set to | |
3718 | zero, @value{GDBN} will never try to use hardware watchpoints, even if | |
3719 | the underlying system supports them. (Note that hardware-assisted | |
3720 | watchpoints that were set @emph{before} setting | |
3721 | @code{can-use-hw-watchpoints} to zero will still use the hardware | |
d3e8051b | 3722 | mechanism of watching expression values.) |
c906108c | 3723 | |
9c16f35a EZ |
3724 | @table @code |
3725 | @item set can-use-hw-watchpoints | |
3726 | @kindex set can-use-hw-watchpoints | |
3727 | Set whether or not to use hardware watchpoints. | |
3728 | ||
3729 | @item show can-use-hw-watchpoints | |
3730 | @kindex show can-use-hw-watchpoints | |
3731 | Show the current mode of using hardware watchpoints. | |
3732 | @end table | |
3733 | ||
3734 | For remote targets, you can restrict the number of hardware | |
3735 | watchpoints @value{GDBN} will use, see @ref{set remote | |
3736 | hardware-breakpoint-limit}. | |
3737 | ||
c906108c SS |
3738 | When you issue the @code{watch} command, @value{GDBN} reports |
3739 | ||
474c8240 | 3740 | @smallexample |
c906108c | 3741 | Hardware watchpoint @var{num}: @var{expr} |
474c8240 | 3742 | @end smallexample |
c906108c SS |
3743 | |
3744 | @noindent | |
3745 | if it was able to set a hardware watchpoint. | |
3746 | ||
7be570e7 JM |
3747 | Currently, the @code{awatch} and @code{rwatch} commands can only set |
3748 | hardware watchpoints, because accesses to data that don't change the | |
3749 | value of the watched expression cannot be detected without examining | |
3750 | every instruction as it is being executed, and @value{GDBN} does not do | |
3751 | that currently. If @value{GDBN} finds that it is unable to set a | |
3752 | hardware breakpoint with the @code{awatch} or @code{rwatch} command, it | |
3753 | will print a message like this: | |
3754 | ||
3755 | @smallexample | |
3756 | Expression cannot be implemented with read/access watchpoint. | |
3757 | @end smallexample | |
3758 | ||
3759 | Sometimes, @value{GDBN} cannot set a hardware watchpoint because the | |
3760 | data type of the watched expression is wider than what a hardware | |
3761 | watchpoint on the target machine can handle. For example, some systems | |
3762 | can only watch regions that are up to 4 bytes wide; on such systems you | |
3763 | cannot set hardware watchpoints for an expression that yields a | |
3764 | double-precision floating-point number (which is typically 8 bytes | |
3765 | wide). As a work-around, it might be possible to break the large region | |
3766 | into a series of smaller ones and watch them with separate watchpoints. | |
3767 | ||
3768 | If you set too many hardware watchpoints, @value{GDBN} might be unable | |
3769 | to insert all of them when you resume the execution of your program. | |
3770 | Since the precise number of active watchpoints is unknown until such | |
3771 | time as the program is about to be resumed, @value{GDBN} might not be | |
3772 | able to warn you about this when you set the watchpoints, and the | |
3773 | warning will be printed only when the program is resumed: | |
3774 | ||
3775 | @smallexample | |
3776 | Hardware watchpoint @var{num}: Could not insert watchpoint | |
3777 | @end smallexample | |
3778 | ||
3779 | @noindent | |
3780 | If this happens, delete or disable some of the watchpoints. | |
3781 | ||
fd60e0df EZ |
3782 | Watching complex expressions that reference many variables can also |
3783 | exhaust the resources available for hardware-assisted watchpoints. | |
3784 | That's because @value{GDBN} needs to watch every variable in the | |
3785 | expression with separately allocated resources. | |
3786 | ||
c906108c | 3787 | If you call a function interactively using @code{print} or @code{call}, |
2df3850c | 3788 | any watchpoints you have set will be inactive until @value{GDBN} reaches another |
c906108c SS |
3789 | kind of breakpoint or the call completes. |
3790 | ||
7be570e7 JM |
3791 | @value{GDBN} automatically deletes watchpoints that watch local |
3792 | (automatic) variables, or expressions that involve such variables, when | |
3793 | they go out of scope, that is, when the execution leaves the block in | |
3794 | which these variables were defined. In particular, when the program | |
3795 | being debugged terminates, @emph{all} local variables go out of scope, | |
3796 | and so only watchpoints that watch global variables remain set. If you | |
3797 | rerun the program, you will need to set all such watchpoints again. One | |
3798 | way of doing that would be to set a code breakpoint at the entry to the | |
3799 | @code{main} function and when it breaks, set all the watchpoints. | |
3800 | ||
c906108c SS |
3801 | @cindex watchpoints and threads |
3802 | @cindex threads and watchpoints | |
d983da9c DJ |
3803 | In multi-threaded programs, watchpoints will detect changes to the |
3804 | watched expression from every thread. | |
3805 | ||
3806 | @quotation | |
3807 | @emph{Warning:} In multi-threaded programs, software watchpoints | |
53a5351d JM |
3808 | have only limited usefulness. If @value{GDBN} creates a software |
3809 | watchpoint, it can only watch the value of an expression @emph{in a | |
3810 | single thread}. If you are confident that the expression can only | |
3811 | change due to the current thread's activity (and if you are also | |
3812 | confident that no other thread can become current), then you can use | |
3813 | software watchpoints as usual. However, @value{GDBN} may not notice | |
3814 | when a non-current thread's activity changes the expression. (Hardware | |
3815 | watchpoints, in contrast, watch an expression in all threads.) | |
c906108c | 3816 | @end quotation |
c906108c | 3817 | |
501eef12 AC |
3818 | @xref{set remote hardware-watchpoint-limit}. |
3819 | ||
6d2ebf8b | 3820 | @node Set Catchpoints |
79a6e687 | 3821 | @subsection Setting Catchpoints |
d4f3574e | 3822 | @cindex catchpoints, setting |
c906108c SS |
3823 | @cindex exception handlers |
3824 | @cindex event handling | |
3825 | ||
3826 | You can use @dfn{catchpoints} to cause the debugger to stop for certain | |
b37052ae | 3827 | kinds of program events, such as C@t{++} exceptions or the loading of a |
c906108c SS |
3828 | shared library. Use the @code{catch} command to set a catchpoint. |
3829 | ||
3830 | @table @code | |
3831 | @kindex catch | |
3832 | @item catch @var{event} | |
3833 | Stop when @var{event} occurs. @var{event} can be any of the following: | |
3834 | @table @code | |
3835 | @item throw | |
4644b6e3 | 3836 | @cindex stop on C@t{++} exceptions |
b37052ae | 3837 | The throwing of a C@t{++} exception. |
c906108c SS |
3838 | |
3839 | @item catch | |
b37052ae | 3840 | The catching of a C@t{++} exception. |
c906108c | 3841 | |
8936fcda JB |
3842 | @item exception |
3843 | @cindex Ada exception catching | |
3844 | @cindex catch Ada exceptions | |
3845 | An Ada exception being raised. If an exception name is specified | |
3846 | at the end of the command (eg @code{catch exception Program_Error}), | |
3847 | the debugger will stop only when this specific exception is raised. | |
3848 | Otherwise, the debugger stops execution when any Ada exception is raised. | |
3849 | ||
87f67dba JB |
3850 | When inserting an exception catchpoint on a user-defined exception whose |
3851 | name is identical to one of the exceptions defined by the language, the | |
3852 | fully qualified name must be used as the exception name. Otherwise, | |
3853 | @value{GDBN} will assume that it should stop on the pre-defined exception | |
3854 | rather than the user-defined one. For instance, assuming an exception | |
3855 | called @code{Constraint_Error} is defined in package @code{Pck}, then | |
3856 | the command to use to catch such exceptions is @kbd{catch exception | |
3857 | Pck.Constraint_Error}. | |
3858 | ||
8936fcda JB |
3859 | @item exception unhandled |
3860 | An exception that was raised but is not handled by the program. | |
3861 | ||
3862 | @item assert | |
3863 | A failed Ada assertion. | |
3864 | ||
c906108c | 3865 | @item exec |
4644b6e3 | 3866 | @cindex break on fork/exec |
5ee187d7 DJ |
3867 | A call to @code{exec}. This is currently only available for HP-UX |
3868 | and @sc{gnu}/Linux. | |
c906108c | 3869 | |
a96d9b2e SDJ |
3870 | @item syscall |
3871 | @itemx syscall @r{[}@var{name} @r{|} @var{number}@r{]} @r{...} | |
3872 | @cindex break on a system call. | |
3873 | A call to or return from a system call, a.k.a.@: @dfn{syscall}. A | |
3874 | syscall is a mechanism for application programs to request a service | |
3875 | from the operating system (OS) or one of the OS system services. | |
3876 | @value{GDBN} can catch some or all of the syscalls issued by the | |
3877 | debuggee, and show the related information for each syscall. If no | |
3878 | argument is specified, calls to and returns from all system calls | |
3879 | will be caught. | |
3880 | ||
3881 | @var{name} can be any system call name that is valid for the | |
3882 | underlying OS. Just what syscalls are valid depends on the OS. On | |
3883 | GNU and Unix systems, you can find the full list of valid syscall | |
3884 | names on @file{/usr/include/asm/unistd.h}. | |
3885 | ||
3886 | @c For MS-Windows, the syscall names and the corresponding numbers | |
3887 | @c can be found, e.g., on this URL: | |
3888 | @c http://www.metasploit.com/users/opcode/syscalls.html | |
3889 | @c but we don't support Windows syscalls yet. | |
3890 | ||
3891 | Normally, @value{GDBN} knows in advance which syscalls are valid for | |
3892 | each OS, so you can use the @value{GDBN} command-line completion | |
3893 | facilities (@pxref{Completion,, command completion}) to list the | |
3894 | available choices. | |
3895 | ||
3896 | You may also specify the system call numerically. A syscall's | |
3897 | number is the value passed to the OS's syscall dispatcher to | |
3898 | identify the requested service. When you specify the syscall by its | |
3899 | name, @value{GDBN} uses its database of syscalls to convert the name | |
3900 | into the corresponding numeric code, but using the number directly | |
3901 | may be useful if @value{GDBN}'s database does not have the complete | |
3902 | list of syscalls on your system (e.g., because @value{GDBN} lags | |
3903 | behind the OS upgrades). | |
3904 | ||
3905 | The example below illustrates how this command works if you don't provide | |
3906 | arguments to it: | |
3907 | ||
3908 | @smallexample | |
3909 | (@value{GDBP}) catch syscall | |
3910 | Catchpoint 1 (syscall) | |
3911 | (@value{GDBP}) r | |
3912 | Starting program: /tmp/catch-syscall | |
3913 | ||
3914 | Catchpoint 1 (call to syscall 'close'), \ | |
3915 | 0xffffe424 in __kernel_vsyscall () | |
3916 | (@value{GDBP}) c | |
3917 | Continuing. | |
3918 | ||
3919 | Catchpoint 1 (returned from syscall 'close'), \ | |
3920 | 0xffffe424 in __kernel_vsyscall () | |
3921 | (@value{GDBP}) | |
3922 | @end smallexample | |
3923 | ||
3924 | Here is an example of catching a system call by name: | |
3925 | ||
3926 | @smallexample | |
3927 | (@value{GDBP}) catch syscall chroot | |
3928 | Catchpoint 1 (syscall 'chroot' [61]) | |
3929 | (@value{GDBP}) r | |
3930 | Starting program: /tmp/catch-syscall | |
3931 | ||
3932 | Catchpoint 1 (call to syscall 'chroot'), \ | |
3933 | 0xffffe424 in __kernel_vsyscall () | |
3934 | (@value{GDBP}) c | |
3935 | Continuing. | |
3936 | ||
3937 | Catchpoint 1 (returned from syscall 'chroot'), \ | |
3938 | 0xffffe424 in __kernel_vsyscall () | |
3939 | (@value{GDBP}) | |
3940 | @end smallexample | |
3941 | ||
3942 | An example of specifying a system call numerically. In the case | |
3943 | below, the syscall number has a corresponding entry in the XML | |
3944 | file, so @value{GDBN} finds its name and prints it: | |
3945 | ||
3946 | @smallexample | |
3947 | (@value{GDBP}) catch syscall 252 | |
3948 | Catchpoint 1 (syscall(s) 'exit_group') | |
3949 | (@value{GDBP}) r | |
3950 | Starting program: /tmp/catch-syscall | |
3951 | ||
3952 | Catchpoint 1 (call to syscall 'exit_group'), \ | |
3953 | 0xffffe424 in __kernel_vsyscall () | |
3954 | (@value{GDBP}) c | |
3955 | Continuing. | |
3956 | ||
3957 | Program exited normally. | |
3958 | (@value{GDBP}) | |
3959 | @end smallexample | |
3960 | ||
3961 | However, there can be situations when there is no corresponding name | |
3962 | in XML file for that syscall number. In this case, @value{GDBN} prints | |
3963 | a warning message saying that it was not able to find the syscall name, | |
3964 | but the catchpoint will be set anyway. See the example below: | |
3965 | ||
3966 | @smallexample | |
3967 | (@value{GDBP}) catch syscall 764 | |
3968 | warning: The number '764' does not represent a known syscall. | |
3969 | Catchpoint 2 (syscall 764) | |
3970 | (@value{GDBP}) | |
3971 | @end smallexample | |
3972 | ||
3973 | If you configure @value{GDBN} using the @samp{--without-expat} option, | |
3974 | it will not be able to display syscall names. Also, if your | |
3975 | architecture does not have an XML file describing its system calls, | |
3976 | you will not be able to see the syscall names. It is important to | |
3977 | notice that these two features are used for accessing the syscall | |
3978 | name database. In either case, you will see a warning like this: | |
3979 | ||
3980 | @smallexample | |
3981 | (@value{GDBP}) catch syscall | |
3982 | warning: Could not open "syscalls/i386-linux.xml" | |
3983 | warning: Could not load the syscall XML file 'syscalls/i386-linux.xml'. | |
3984 | GDB will not be able to display syscall names. | |
3985 | Catchpoint 1 (syscall) | |
3986 | (@value{GDBP}) | |
3987 | @end smallexample | |
3988 | ||
3989 | Of course, the file name will change depending on your architecture and system. | |
3990 | ||
3991 | Still using the example above, you can also try to catch a syscall by its | |
3992 | number. In this case, you would see something like: | |
3993 | ||
3994 | @smallexample | |
3995 | (@value{GDBP}) catch syscall 252 | |
3996 | Catchpoint 1 (syscall(s) 252) | |
3997 | @end smallexample | |
3998 | ||
3999 | Again, in this case @value{GDBN} would not be able to display syscall's names. | |
4000 | ||
c906108c | 4001 | @item fork |
5ee187d7 DJ |
4002 | A call to @code{fork}. This is currently only available for HP-UX |
4003 | and @sc{gnu}/Linux. | |
c906108c SS |
4004 | |
4005 | @item vfork | |
5ee187d7 DJ |
4006 | A call to @code{vfork}. This is currently only available for HP-UX |
4007 | and @sc{gnu}/Linux. | |
c906108c | 4008 | |
c906108c SS |
4009 | @end table |
4010 | ||
4011 | @item tcatch @var{event} | |
4012 | Set a catchpoint that is enabled only for one stop. The catchpoint is | |
4013 | automatically deleted after the first time the event is caught. | |
4014 | ||
4015 | @end table | |
4016 | ||
4017 | Use the @code{info break} command to list the current catchpoints. | |
4018 | ||
b37052ae | 4019 | There are currently some limitations to C@t{++} exception handling |
c906108c SS |
4020 | (@code{catch throw} and @code{catch catch}) in @value{GDBN}: |
4021 | ||
4022 | @itemize @bullet | |
4023 | @item | |
4024 | If you call a function interactively, @value{GDBN} normally returns | |
4025 | control to you when the function has finished executing. If the call | |
4026 | raises an exception, however, the call may bypass the mechanism that | |
4027 | returns control to you and cause your program either to abort or to | |
4028 | simply continue running until it hits a breakpoint, catches a signal | |
4029 | that @value{GDBN} is listening for, or exits. This is the case even if | |
4030 | you set a catchpoint for the exception; catchpoints on exceptions are | |
4031 | disabled within interactive calls. | |
4032 | ||
4033 | @item | |
4034 | You cannot raise an exception interactively. | |
4035 | ||
4036 | @item | |
4037 | You cannot install an exception handler interactively. | |
4038 | @end itemize | |
4039 | ||
4040 | @cindex raise exceptions | |
4041 | Sometimes @code{catch} is not the best way to debug exception handling: | |
4042 | if you need to know exactly where an exception is raised, it is better to | |
4043 | stop @emph{before} the exception handler is called, since that way you | |
4044 | can see the stack before any unwinding takes place. If you set a | |
4045 | breakpoint in an exception handler instead, it may not be easy to find | |
4046 | out where the exception was raised. | |
4047 | ||
4048 | To stop just before an exception handler is called, you need some | |
b37052ae | 4049 | knowledge of the implementation. In the case of @sc{gnu} C@t{++}, exceptions are |
c906108c SS |
4050 | raised by calling a library function named @code{__raise_exception} |
4051 | which has the following ANSI C interface: | |
4052 | ||
474c8240 | 4053 | @smallexample |
c906108c | 4054 | /* @var{addr} is where the exception identifier is stored. |
d4f3574e SS |
4055 | @var{id} is the exception identifier. */ |
4056 | void __raise_exception (void **addr, void *id); | |
474c8240 | 4057 | @end smallexample |
c906108c SS |
4058 | |
4059 | @noindent | |
4060 | To make the debugger catch all exceptions before any stack | |
4061 | unwinding takes place, set a breakpoint on @code{__raise_exception} | |
79a6e687 | 4062 | (@pxref{Breakpoints, ,Breakpoints; Watchpoints; and Exceptions}). |
c906108c | 4063 | |
79a6e687 | 4064 | With a conditional breakpoint (@pxref{Conditions, ,Break Conditions}) |
c906108c SS |
4065 | that depends on the value of @var{id}, you can stop your program when |
4066 | a specific exception is raised. You can use multiple conditional | |
4067 | breakpoints to stop your program when any of a number of exceptions are | |
4068 | raised. | |
4069 | ||
4070 | ||
6d2ebf8b | 4071 | @node Delete Breaks |
79a6e687 | 4072 | @subsection Deleting Breakpoints |
c906108c SS |
4073 | |
4074 | @cindex clearing breakpoints, watchpoints, catchpoints | |
4075 | @cindex deleting breakpoints, watchpoints, catchpoints | |
4076 | It is often necessary to eliminate a breakpoint, watchpoint, or | |
4077 | catchpoint once it has done its job and you no longer want your program | |
4078 | to stop there. This is called @dfn{deleting} the breakpoint. A | |
4079 | breakpoint that has been deleted no longer exists; it is forgotten. | |
4080 | ||
4081 | With the @code{clear} command you can delete breakpoints according to | |
4082 | where they are in your program. With the @code{delete} command you can | |
4083 | delete individual breakpoints, watchpoints, or catchpoints by specifying | |
4084 | their breakpoint numbers. | |
4085 | ||
4086 | It is not necessary to delete a breakpoint to proceed past it. @value{GDBN} | |
4087 | automatically ignores breakpoints on the first instruction to be executed | |
4088 | when you continue execution without changing the execution address. | |
4089 | ||
4090 | @table @code | |
4091 | @kindex clear | |
4092 | @item clear | |
4093 | Delete any breakpoints at the next instruction to be executed in the | |
79a6e687 | 4094 | selected stack frame (@pxref{Selection, ,Selecting a Frame}). When |
c906108c SS |
4095 | the innermost frame is selected, this is a good way to delete a |
4096 | breakpoint where your program just stopped. | |
4097 | ||
2a25a5ba EZ |
4098 | @item clear @var{location} |
4099 | Delete any breakpoints set at the specified @var{location}. | |
4100 | @xref{Specify Location}, for the various forms of @var{location}; the | |
4101 | most useful ones are listed below: | |
4102 | ||
4103 | @table @code | |
c906108c SS |
4104 | @item clear @var{function} |
4105 | @itemx clear @var{filename}:@var{function} | |
09d4efe1 | 4106 | Delete any breakpoints set at entry to the named @var{function}. |
c906108c SS |
4107 | |
4108 | @item clear @var{linenum} | |
4109 | @itemx clear @var{filename}:@var{linenum} | |
09d4efe1 EZ |
4110 | Delete any breakpoints set at or within the code of the specified |
4111 | @var{linenum} of the specified @var{filename}. | |
2a25a5ba | 4112 | @end table |
c906108c SS |
4113 | |
4114 | @cindex delete breakpoints | |
4115 | @kindex delete | |
41afff9a | 4116 | @kindex d @r{(@code{delete})} |
c5394b80 JM |
4117 | @item delete @r{[}breakpoints@r{]} @r{[}@var{range}@dots{}@r{]} |
4118 | Delete the breakpoints, watchpoints, or catchpoints of the breakpoint | |
4119 | ranges specified as arguments. If no argument is specified, delete all | |
c906108c SS |
4120 | breakpoints (@value{GDBN} asks confirmation, unless you have @code{set |
4121 | confirm off}). You can abbreviate this command as @code{d}. | |
4122 | @end table | |
4123 | ||
6d2ebf8b | 4124 | @node Disabling |
79a6e687 | 4125 | @subsection Disabling Breakpoints |
c906108c | 4126 | |
4644b6e3 | 4127 | @cindex enable/disable a breakpoint |
c906108c SS |
4128 | Rather than deleting a breakpoint, watchpoint, or catchpoint, you might |
4129 | prefer to @dfn{disable} it. This makes the breakpoint inoperative as if | |
4130 | it had been deleted, but remembers the information on the breakpoint so | |
4131 | that you can @dfn{enable} it again later. | |
4132 | ||
4133 | You disable and enable breakpoints, watchpoints, and catchpoints with | |
4134 | the @code{enable} and @code{disable} commands, optionally specifying one | |
4135 | or more breakpoint numbers as arguments. Use @code{info break} or | |
4136 | @code{info watch} to print a list of breakpoints, watchpoints, and | |
4137 | catchpoints if you do not know which numbers to use. | |
4138 | ||
3b784c4f EZ |
4139 | Disabling and enabling a breakpoint that has multiple locations |
4140 | affects all of its locations. | |
4141 | ||
c906108c SS |
4142 | A breakpoint, watchpoint, or catchpoint can have any of four different |
4143 | states of enablement: | |
4144 | ||
4145 | @itemize @bullet | |
4146 | @item | |
4147 | Enabled. The breakpoint stops your program. A breakpoint set | |
4148 | with the @code{break} command starts out in this state. | |
4149 | @item | |
4150 | Disabled. The breakpoint has no effect on your program. | |
4151 | @item | |
4152 | Enabled once. The breakpoint stops your program, but then becomes | |
d4f3574e | 4153 | disabled. |
c906108c SS |
4154 | @item |
4155 | Enabled for deletion. The breakpoint stops your program, but | |
d4f3574e SS |
4156 | immediately after it does so it is deleted permanently. A breakpoint |
4157 | set with the @code{tbreak} command starts out in this state. | |
c906108c SS |
4158 | @end itemize |
4159 | ||
4160 | You can use the following commands to enable or disable breakpoints, | |
4161 | watchpoints, and catchpoints: | |
4162 | ||
4163 | @table @code | |
c906108c | 4164 | @kindex disable |
41afff9a | 4165 | @kindex dis @r{(@code{disable})} |
c5394b80 | 4166 | @item disable @r{[}breakpoints@r{]} @r{[}@var{range}@dots{}@r{]} |
c906108c SS |
4167 | Disable the specified breakpoints---or all breakpoints, if none are |
4168 | listed. A disabled breakpoint has no effect but is not forgotten. All | |
4169 | options such as ignore-counts, conditions and commands are remembered in | |
4170 | case the breakpoint is enabled again later. You may abbreviate | |
4171 | @code{disable} as @code{dis}. | |
4172 | ||
c906108c | 4173 | @kindex enable |
c5394b80 | 4174 | @item enable @r{[}breakpoints@r{]} @r{[}@var{range}@dots{}@r{]} |
c906108c SS |
4175 | Enable the specified breakpoints (or all defined breakpoints). They |
4176 | become effective once again in stopping your program. | |
4177 | ||
c5394b80 | 4178 | @item enable @r{[}breakpoints@r{]} once @var{range}@dots{} |
c906108c SS |
4179 | Enable the specified breakpoints temporarily. @value{GDBN} disables any |
4180 | of these breakpoints immediately after stopping your program. | |
4181 | ||
c5394b80 | 4182 | @item enable @r{[}breakpoints@r{]} delete @var{range}@dots{} |
c906108c SS |
4183 | Enable the specified breakpoints to work once, then die. @value{GDBN} |
4184 | deletes any of these breakpoints as soon as your program stops there. | |
09d4efe1 | 4185 | Breakpoints set by the @code{tbreak} command start out in this state. |
c906108c SS |
4186 | @end table |
4187 | ||
d4f3574e SS |
4188 | @c FIXME: I think the following ``Except for [...] @code{tbreak}'' is |
4189 | @c confusing: tbreak is also initially enabled. | |
c906108c | 4190 | Except for a breakpoint set with @code{tbreak} (@pxref{Set Breaks, |
79a6e687 | 4191 | ,Setting Breakpoints}), breakpoints that you set are initially enabled; |
c906108c SS |
4192 | subsequently, they become disabled or enabled only when you use one of |
4193 | the commands above. (The command @code{until} can set and delete a | |
4194 | breakpoint of its own, but it does not change the state of your other | |
4195 | breakpoints; see @ref{Continuing and Stepping, ,Continuing and | |
79a6e687 | 4196 | Stepping}.) |
c906108c | 4197 | |
6d2ebf8b | 4198 | @node Conditions |
79a6e687 | 4199 | @subsection Break Conditions |
c906108c SS |
4200 | @cindex conditional breakpoints |
4201 | @cindex breakpoint conditions | |
4202 | ||
4203 | @c FIXME what is scope of break condition expr? Context where wanted? | |
5d161b24 | 4204 | @c in particular for a watchpoint? |
c906108c SS |
4205 | The simplest sort of breakpoint breaks every time your program reaches a |
4206 | specified place. You can also specify a @dfn{condition} for a | |
4207 | breakpoint. A condition is just a Boolean expression in your | |
4208 | programming language (@pxref{Expressions, ,Expressions}). A breakpoint with | |
4209 | a condition evaluates the expression each time your program reaches it, | |
4210 | and your program stops only if the condition is @emph{true}. | |
4211 | ||
4212 | This is the converse of using assertions for program validation; in that | |
4213 | situation, you want to stop when the assertion is violated---that is, | |
4214 | when the condition is false. In C, if you want to test an assertion expressed | |
4215 | by the condition @var{assert}, you should set the condition | |
4216 | @samp{! @var{assert}} on the appropriate breakpoint. | |
4217 | ||
4218 | Conditions are also accepted for watchpoints; you may not need them, | |
4219 | since a watchpoint is inspecting the value of an expression anyhow---but | |
4220 | it might be simpler, say, to just set a watchpoint on a variable name, | |
4221 | and specify a condition that tests whether the new value is an interesting | |
4222 | one. | |
4223 | ||
4224 | Break conditions can have side effects, and may even call functions in | |
4225 | your program. This can be useful, for example, to activate functions | |
4226 | that log program progress, or to use your own print functions to | |
99e008fe | 4227 | format special data structures. The effects are completely predictable |
c906108c SS |
4228 | unless there is another enabled breakpoint at the same address. (In |
4229 | that case, @value{GDBN} might see the other breakpoint first and stop your | |
4230 | program without checking the condition of this one.) Note that | |
d4f3574e SS |
4231 | breakpoint commands are usually more convenient and flexible than break |
4232 | conditions for the | |
c906108c | 4233 | purpose of performing side effects when a breakpoint is reached |
79a6e687 | 4234 | (@pxref{Break Commands, ,Breakpoint Command Lists}). |
c906108c SS |
4235 | |
4236 | Break conditions can be specified when a breakpoint is set, by using | |
4237 | @samp{if} in the arguments to the @code{break} command. @xref{Set | |
79a6e687 | 4238 | Breaks, ,Setting Breakpoints}. They can also be changed at any time |
c906108c | 4239 | with the @code{condition} command. |
53a5351d | 4240 | |
c906108c SS |
4241 | You can also use the @code{if} keyword with the @code{watch} command. |
4242 | The @code{catch} command does not recognize the @code{if} keyword; | |
4243 | @code{condition} is the only way to impose a further condition on a | |
4244 | catchpoint. | |
c906108c SS |
4245 | |
4246 | @table @code | |
4247 | @kindex condition | |
4248 | @item condition @var{bnum} @var{expression} | |
4249 | Specify @var{expression} as the break condition for breakpoint, | |
4250 | watchpoint, or catchpoint number @var{bnum}. After you set a condition, | |
4251 | breakpoint @var{bnum} stops your program only if the value of | |
4252 | @var{expression} is true (nonzero, in C). When you use | |
4253 | @code{condition}, @value{GDBN} checks @var{expression} immediately for | |
4254 | syntactic correctness, and to determine whether symbols in it have | |
d4f3574e SS |
4255 | referents in the context of your breakpoint. If @var{expression} uses |
4256 | symbols not referenced in the context of the breakpoint, @value{GDBN} | |
4257 | prints an error message: | |
4258 | ||
474c8240 | 4259 | @smallexample |
d4f3574e | 4260 | No symbol "foo" in current context. |
474c8240 | 4261 | @end smallexample |
d4f3574e SS |
4262 | |
4263 | @noindent | |
c906108c SS |
4264 | @value{GDBN} does |
4265 | not actually evaluate @var{expression} at the time the @code{condition} | |
d4f3574e SS |
4266 | command (or a command that sets a breakpoint with a condition, like |
4267 | @code{break if @dots{}}) is given, however. @xref{Expressions, ,Expressions}. | |
c906108c SS |
4268 | |
4269 | @item condition @var{bnum} | |
4270 | Remove the condition from breakpoint number @var{bnum}. It becomes | |
4271 | an ordinary unconditional breakpoint. | |
4272 | @end table | |
4273 | ||
4274 | @cindex ignore count (of breakpoint) | |
4275 | A special case of a breakpoint condition is to stop only when the | |
4276 | breakpoint has been reached a certain number of times. This is so | |
4277 | useful that there is a special way to do it, using the @dfn{ignore | |
4278 | count} of the breakpoint. Every breakpoint has an ignore count, which | |
4279 | is an integer. Most of the time, the ignore count is zero, and | |
4280 | therefore has no effect. But if your program reaches a breakpoint whose | |
4281 | ignore count is positive, then instead of stopping, it just decrements | |
4282 | the ignore count by one and continues. As a result, if the ignore count | |
4283 | value is @var{n}, the breakpoint does not stop the next @var{n} times | |
4284 | your program reaches it. | |
4285 | ||
4286 | @table @code | |
4287 | @kindex ignore | |
4288 | @item ignore @var{bnum} @var{count} | |
4289 | Set the ignore count of breakpoint number @var{bnum} to @var{count}. | |
4290 | The next @var{count} times the breakpoint is reached, your program's | |
4291 | execution does not stop; other than to decrement the ignore count, @value{GDBN} | |
4292 | takes no action. | |
4293 | ||
4294 | To make the breakpoint stop the next time it is reached, specify | |
4295 | a count of zero. | |
4296 | ||
4297 | When you use @code{continue} to resume execution of your program from a | |
4298 | breakpoint, you can specify an ignore count directly as an argument to | |
4299 | @code{continue}, rather than using @code{ignore}. @xref{Continuing and | |
79a6e687 | 4300 | Stepping,,Continuing and Stepping}. |
c906108c SS |
4301 | |
4302 | If a breakpoint has a positive ignore count and a condition, the | |
4303 | condition is not checked. Once the ignore count reaches zero, | |
4304 | @value{GDBN} resumes checking the condition. | |
4305 | ||
4306 | You could achieve the effect of the ignore count with a condition such | |
4307 | as @w{@samp{$foo-- <= 0}} using a debugger convenience variable that | |
4308 | is decremented each time. @xref{Convenience Vars, ,Convenience | |
79a6e687 | 4309 | Variables}. |
c906108c SS |
4310 | @end table |
4311 | ||
4312 | Ignore counts apply to breakpoints, watchpoints, and catchpoints. | |
4313 | ||
4314 | ||
6d2ebf8b | 4315 | @node Break Commands |
79a6e687 | 4316 | @subsection Breakpoint Command Lists |
c906108c SS |
4317 | |
4318 | @cindex breakpoint commands | |
4319 | You can give any breakpoint (or watchpoint or catchpoint) a series of | |
4320 | commands to execute when your program stops due to that breakpoint. For | |
4321 | example, you might want to print the values of certain expressions, or | |
4322 | enable other breakpoints. | |
4323 | ||
4324 | @table @code | |
4325 | @kindex commands | |
ca91424e | 4326 | @kindex end@r{ (breakpoint commands)} |
c906108c SS |
4327 | @item commands @r{[}@var{bnum}@r{]} |
4328 | @itemx @dots{} @var{command-list} @dots{} | |
4329 | @itemx end | |
4330 | Specify a list of commands for breakpoint number @var{bnum}. The commands | |
4331 | themselves appear on the following lines. Type a line containing just | |
4332 | @code{end} to terminate the commands. | |
4333 | ||
4334 | To remove all commands from a breakpoint, type @code{commands} and | |
4335 | follow it immediately with @code{end}; that is, give no commands. | |
4336 | ||
4337 | With no @var{bnum} argument, @code{commands} refers to the last | |
4338 | breakpoint, watchpoint, or catchpoint set (not to the breakpoint most | |
4339 | recently encountered). | |
4340 | @end table | |
4341 | ||
4342 | Pressing @key{RET} as a means of repeating the last @value{GDBN} command is | |
4343 | disabled within a @var{command-list}. | |
4344 | ||
4345 | You can use breakpoint commands to start your program up again. Simply | |
4346 | use the @code{continue} command, or @code{step}, or any other command | |
4347 | that resumes execution. | |
4348 | ||
4349 | Any other commands in the command list, after a command that resumes | |
4350 | execution, are ignored. This is because any time you resume execution | |
4351 | (even with a simple @code{next} or @code{step}), you may encounter | |
4352 | another breakpoint---which could have its own command list, leading to | |
4353 | ambiguities about which list to execute. | |
4354 | ||
4355 | @kindex silent | |
4356 | If the first command you specify in a command list is @code{silent}, the | |
4357 | usual message about stopping at a breakpoint is not printed. This may | |
4358 | be desirable for breakpoints that are to print a specific message and | |
4359 | then continue. If none of the remaining commands print anything, you | |
4360 | see no sign that the breakpoint was reached. @code{silent} is | |
4361 | meaningful only at the beginning of a breakpoint command list. | |
4362 | ||
4363 | The commands @code{echo}, @code{output}, and @code{printf} allow you to | |
4364 | print precisely controlled output, and are often useful in silent | |
79a6e687 | 4365 | breakpoints. @xref{Output, ,Commands for Controlled Output}. |
c906108c SS |
4366 | |
4367 | For example, here is how you could use breakpoint commands to print the | |
4368 | value of @code{x} at entry to @code{foo} whenever @code{x} is positive. | |
4369 | ||
474c8240 | 4370 | @smallexample |
c906108c SS |
4371 | break foo if x>0 |
4372 | commands | |
4373 | silent | |
4374 | printf "x is %d\n",x | |
4375 | cont | |
4376 | end | |
474c8240 | 4377 | @end smallexample |
c906108c SS |
4378 | |
4379 | One application for breakpoint commands is to compensate for one bug so | |
4380 | you can test for another. Put a breakpoint just after the erroneous line | |
4381 | of code, give it a condition to detect the case in which something | |
4382 | erroneous has been done, and give it commands to assign correct values | |
4383 | to any variables that need them. End with the @code{continue} command | |
4384 | so that your program does not stop, and start with the @code{silent} | |
4385 | command so that no output is produced. Here is an example: | |
4386 | ||
474c8240 | 4387 | @smallexample |
c906108c SS |
4388 | break 403 |
4389 | commands | |
4390 | silent | |
4391 | set x = y + 4 | |
4392 | cont | |
4393 | end | |
474c8240 | 4394 | @end smallexample |
c906108c | 4395 | |
c906108c | 4396 | @c @ifclear BARETARGET |
6d2ebf8b | 4397 | @node Error in Breakpoints |
d4f3574e | 4398 | @subsection ``Cannot insert breakpoints'' |
c906108c | 4399 | |
fa3a767f PA |
4400 | If you request too many active hardware-assisted breakpoints and |
4401 | watchpoints, you will see this error message: | |
d4f3574e SS |
4402 | |
4403 | @c FIXME: the precise wording of this message may change; the relevant | |
4404 | @c source change is not committed yet (Sep 3, 1999). | |
4405 | @smallexample | |
4406 | Stopped; cannot insert breakpoints. | |
4407 | You may have requested too many hardware breakpoints and watchpoints. | |
4408 | @end smallexample | |
4409 | ||
4410 | @noindent | |
4411 | This message is printed when you attempt to resume the program, since | |
4412 | only then @value{GDBN} knows exactly how many hardware breakpoints and | |
4413 | watchpoints it needs to insert. | |
4414 | ||
4415 | When this message is printed, you need to disable or remove some of the | |
4416 | hardware-assisted breakpoints and watchpoints, and then continue. | |
4417 | ||
79a6e687 | 4418 | @node Breakpoint-related Warnings |
1485d690 KB |
4419 | @subsection ``Breakpoint address adjusted...'' |
4420 | @cindex breakpoint address adjusted | |
4421 | ||
4422 | Some processor architectures place constraints on the addresses at | |
4423 | which breakpoints may be placed. For architectures thus constrained, | |
4424 | @value{GDBN} will attempt to adjust the breakpoint's address to comply | |
4425 | with the constraints dictated by the architecture. | |
4426 | ||
4427 | One example of such an architecture is the Fujitsu FR-V. The FR-V is | |
4428 | a VLIW architecture in which a number of RISC-like instructions may be | |
4429 | bundled together for parallel execution. The FR-V architecture | |
4430 | constrains the location of a breakpoint instruction within such a | |
4431 | bundle to the instruction with the lowest address. @value{GDBN} | |
4432 | honors this constraint by adjusting a breakpoint's address to the | |
4433 | first in the bundle. | |
4434 | ||
4435 | It is not uncommon for optimized code to have bundles which contain | |
4436 | instructions from different source statements, thus it may happen that | |
4437 | a breakpoint's address will be adjusted from one source statement to | |
4438 | another. Since this adjustment may significantly alter @value{GDBN}'s | |
4439 | breakpoint related behavior from what the user expects, a warning is | |
4440 | printed when the breakpoint is first set and also when the breakpoint | |
4441 | is hit. | |
4442 | ||
4443 | A warning like the one below is printed when setting a breakpoint | |
4444 | that's been subject to address adjustment: | |
4445 | ||
4446 | @smallexample | |
4447 | warning: Breakpoint address adjusted from 0x00010414 to 0x00010410. | |
4448 | @end smallexample | |
4449 | ||
4450 | Such warnings are printed both for user settable and @value{GDBN}'s | |
4451 | internal breakpoints. If you see one of these warnings, you should | |
4452 | verify that a breakpoint set at the adjusted address will have the | |
4453 | desired affect. If not, the breakpoint in question may be removed and | |
b383017d | 4454 | other breakpoints may be set which will have the desired behavior. |
1485d690 KB |
4455 | E.g., it may be sufficient to place the breakpoint at a later |
4456 | instruction. A conditional breakpoint may also be useful in some | |
4457 | cases to prevent the breakpoint from triggering too often. | |
4458 | ||
4459 | @value{GDBN} will also issue a warning when stopping at one of these | |
4460 | adjusted breakpoints: | |
4461 | ||
4462 | @smallexample | |
4463 | warning: Breakpoint 1 address previously adjusted from 0x00010414 | |
4464 | to 0x00010410. | |
4465 | @end smallexample | |
4466 | ||
4467 | When this warning is encountered, it may be too late to take remedial | |
4468 | action except in cases where the breakpoint is hit earlier or more | |
4469 | frequently than expected. | |
d4f3574e | 4470 | |
6d2ebf8b | 4471 | @node Continuing and Stepping |
79a6e687 | 4472 | @section Continuing and Stepping |
c906108c SS |
4473 | |
4474 | @cindex stepping | |
4475 | @cindex continuing | |
4476 | @cindex resuming execution | |
4477 | @dfn{Continuing} means resuming program execution until your program | |
4478 | completes normally. In contrast, @dfn{stepping} means executing just | |
4479 | one more ``step'' of your program, where ``step'' may mean either one | |
4480 | line of source code, or one machine instruction (depending on what | |
7a292a7a SS |
4481 | particular command you use). Either when continuing or when stepping, |
4482 | your program may stop even sooner, due to a breakpoint or a signal. (If | |
d4f3574e SS |
4483 | it stops due to a signal, you may want to use @code{handle}, or use |
4484 | @samp{signal 0} to resume execution. @xref{Signals, ,Signals}.) | |
c906108c SS |
4485 | |
4486 | @table @code | |
4487 | @kindex continue | |
41afff9a EZ |
4488 | @kindex c @r{(@code{continue})} |
4489 | @kindex fg @r{(resume foreground execution)} | |
c906108c SS |
4490 | @item continue @r{[}@var{ignore-count}@r{]} |
4491 | @itemx c @r{[}@var{ignore-count}@r{]} | |
4492 | @itemx fg @r{[}@var{ignore-count}@r{]} | |
4493 | Resume program execution, at the address where your program last stopped; | |
4494 | any breakpoints set at that address are bypassed. The optional argument | |
4495 | @var{ignore-count} allows you to specify a further number of times to | |
4496 | ignore a breakpoint at this location; its effect is like that of | |
79a6e687 | 4497 | @code{ignore} (@pxref{Conditions, ,Break Conditions}). |
c906108c SS |
4498 | |
4499 | The argument @var{ignore-count} is meaningful only when your program | |
4500 | stopped due to a breakpoint. At other times, the argument to | |
4501 | @code{continue} is ignored. | |
4502 | ||
d4f3574e SS |
4503 | The synonyms @code{c} and @code{fg} (for @dfn{foreground}, as the |
4504 | debugged program is deemed to be the foreground program) are provided | |
4505 | purely for convenience, and have exactly the same behavior as | |
4506 | @code{continue}. | |
c906108c SS |
4507 | @end table |
4508 | ||
4509 | To resume execution at a different place, you can use @code{return} | |
79a6e687 | 4510 | (@pxref{Returning, ,Returning from a Function}) to go back to the |
c906108c | 4511 | calling function; or @code{jump} (@pxref{Jumping, ,Continuing at a |
79a6e687 | 4512 | Different Address}) to go to an arbitrary location in your program. |
c906108c SS |
4513 | |
4514 | A typical technique for using stepping is to set a breakpoint | |
79a6e687 | 4515 | (@pxref{Breakpoints, ,Breakpoints; Watchpoints; and Catchpoints}) at the |
c906108c SS |
4516 | beginning of the function or the section of your program where a problem |
4517 | is believed to lie, run your program until it stops at that breakpoint, | |
4518 | and then step through the suspect area, examining the variables that are | |
4519 | interesting, until you see the problem happen. | |
4520 | ||
4521 | @table @code | |
4522 | @kindex step | |
41afff9a | 4523 | @kindex s @r{(@code{step})} |
c906108c SS |
4524 | @item step |
4525 | Continue running your program until control reaches a different source | |
4526 | line, then stop it and return control to @value{GDBN}. This command is | |
4527 | abbreviated @code{s}. | |
4528 | ||
4529 | @quotation | |
4530 | @c "without debugging information" is imprecise; actually "without line | |
4531 | @c numbers in the debugging information". (gcc -g1 has debugging info but | |
4532 | @c not line numbers). But it seems complex to try to make that | |
4533 | @c distinction here. | |
4534 | @emph{Warning:} If you use the @code{step} command while control is | |
4535 | within a function that was compiled without debugging information, | |
4536 | execution proceeds until control reaches a function that does have | |
4537 | debugging information. Likewise, it will not step into a function which | |
4538 | is compiled without debugging information. To step through functions | |
4539 | without debugging information, use the @code{stepi} command, described | |
4540 | below. | |
4541 | @end quotation | |
4542 | ||
4a92d011 EZ |
4543 | The @code{step} command only stops at the first instruction of a source |
4544 | line. This prevents the multiple stops that could otherwise occur in | |
4545 | @code{switch} statements, @code{for} loops, etc. @code{step} continues | |
4546 | to stop if a function that has debugging information is called within | |
4547 | the line. In other words, @code{step} @emph{steps inside} any functions | |
4548 | called within the line. | |
c906108c | 4549 | |
d4f3574e SS |
4550 | Also, the @code{step} command only enters a function if there is line |
4551 | number information for the function. Otherwise it acts like the | |
5d161b24 | 4552 | @code{next} command. This avoids problems when using @code{cc -gl} |
c906108c | 4553 | on MIPS machines. Previously, @code{step} entered subroutines if there |
5d161b24 | 4554 | was any debugging information about the routine. |
c906108c SS |
4555 | |
4556 | @item step @var{count} | |
4557 | Continue running as in @code{step}, but do so @var{count} times. If a | |
7a292a7a SS |
4558 | breakpoint is reached, or a signal not related to stepping occurs before |
4559 | @var{count} steps, stepping stops right away. | |
c906108c SS |
4560 | |
4561 | @kindex next | |
41afff9a | 4562 | @kindex n @r{(@code{next})} |
c906108c SS |
4563 | @item next @r{[}@var{count}@r{]} |
4564 | Continue to the next source line in the current (innermost) stack frame. | |
7a292a7a SS |
4565 | This is similar to @code{step}, but function calls that appear within |
4566 | the line of code are executed without stopping. Execution stops when | |
4567 | control reaches a different line of code at the original stack level | |
4568 | that was executing when you gave the @code{next} command. This command | |
4569 | is abbreviated @code{n}. | |
c906108c SS |
4570 | |
4571 | An argument @var{count} is a repeat count, as for @code{step}. | |
4572 | ||
4573 | ||
4574 | @c FIX ME!! Do we delete this, or is there a way it fits in with | |
4575 | @c the following paragraph? --- Vctoria | |
4576 | @c | |
4577 | @c @code{next} within a function that lacks debugging information acts like | |
4578 | @c @code{step}, but any function calls appearing within the code of the | |
4579 | @c function are executed without stopping. | |
4580 | ||
d4f3574e SS |
4581 | The @code{next} command only stops at the first instruction of a |
4582 | source line. This prevents multiple stops that could otherwise occur in | |
4a92d011 | 4583 | @code{switch} statements, @code{for} loops, etc. |
c906108c | 4584 | |
b90a5f51 CF |
4585 | @kindex set step-mode |
4586 | @item set step-mode | |
4587 | @cindex functions without line info, and stepping | |
4588 | @cindex stepping into functions with no line info | |
4589 | @itemx set step-mode on | |
4a92d011 | 4590 | The @code{set step-mode on} command causes the @code{step} command to |
b90a5f51 CF |
4591 | stop at the first instruction of a function which contains no debug line |
4592 | information rather than stepping over it. | |
4593 | ||
4a92d011 EZ |
4594 | This is useful in cases where you may be interested in inspecting the |
4595 | machine instructions of a function which has no symbolic info and do not | |
4596 | want @value{GDBN} to automatically skip over this function. | |
b90a5f51 CF |
4597 | |
4598 | @item set step-mode off | |
4a92d011 | 4599 | Causes the @code{step} command to step over any functions which contains no |
b90a5f51 CF |
4600 | debug information. This is the default. |
4601 | ||
9c16f35a EZ |
4602 | @item show step-mode |
4603 | Show whether @value{GDBN} will stop in or step over functions without | |
4604 | source line debug information. | |
4605 | ||
c906108c | 4606 | @kindex finish |
8dfa32fc | 4607 | @kindex fin @r{(@code{finish})} |
c906108c SS |
4608 | @item finish |
4609 | Continue running until just after function in the selected stack frame | |
8dfa32fc JB |
4610 | returns. Print the returned value (if any). This command can be |
4611 | abbreviated as @code{fin}. | |
c906108c SS |
4612 | |
4613 | Contrast this with the @code{return} command (@pxref{Returning, | |
79a6e687 | 4614 | ,Returning from a Function}). |
c906108c SS |
4615 | |
4616 | @kindex until | |
41afff9a | 4617 | @kindex u @r{(@code{until})} |
09d4efe1 | 4618 | @cindex run until specified location |
c906108c SS |
4619 | @item until |
4620 | @itemx u | |
4621 | Continue running until a source line past the current line, in the | |
4622 | current stack frame, is reached. This command is used to avoid single | |
4623 | stepping through a loop more than once. It is like the @code{next} | |
4624 | command, except that when @code{until} encounters a jump, it | |
4625 | automatically continues execution until the program counter is greater | |
4626 | than the address of the jump. | |
4627 | ||
4628 | This means that when you reach the end of a loop after single stepping | |
4629 | though it, @code{until} makes your program continue execution until it | |
4630 | exits the loop. In contrast, a @code{next} command at the end of a loop | |
4631 | simply steps back to the beginning of the loop, which forces you to step | |
4632 | through the next iteration. | |
4633 | ||
4634 | @code{until} always stops your program if it attempts to exit the current | |
4635 | stack frame. | |
4636 | ||
4637 | @code{until} may produce somewhat counterintuitive results if the order | |
4638 | of machine code does not match the order of the source lines. For | |
4639 | example, in the following excerpt from a debugging session, the @code{f} | |
4640 | (@code{frame}) command shows that execution is stopped at line | |
4641 | @code{206}; yet when we use @code{until}, we get to line @code{195}: | |
4642 | ||
474c8240 | 4643 | @smallexample |
c906108c SS |
4644 | (@value{GDBP}) f |
4645 | #0 main (argc=4, argv=0xf7fffae8) at m4.c:206 | |
4646 | 206 expand_input(); | |
4647 | (@value{GDBP}) until | |
4648 | 195 for ( ; argc > 0; NEXTARG) @{ | |
474c8240 | 4649 | @end smallexample |
c906108c SS |
4650 | |
4651 | This happened because, for execution efficiency, the compiler had | |
4652 | generated code for the loop closure test at the end, rather than the | |
4653 | start, of the loop---even though the test in a C @code{for}-loop is | |
4654 | written before the body of the loop. The @code{until} command appeared | |
4655 | to step back to the beginning of the loop when it advanced to this | |
4656 | expression; however, it has not really gone to an earlier | |
4657 | statement---not in terms of the actual machine code. | |
4658 | ||
4659 | @code{until} with no argument works by means of single | |
4660 | instruction stepping, and hence is slower than @code{until} with an | |
4661 | argument. | |
4662 | ||
4663 | @item until @var{location} | |
4664 | @itemx u @var{location} | |
4665 | Continue running your program until either the specified location is | |
4666 | reached, or the current stack frame returns. @var{location} is any of | |
2a25a5ba EZ |
4667 | the forms described in @ref{Specify Location}. |
4668 | This form of the command uses temporary breakpoints, and | |
c60eb6f1 EZ |
4669 | hence is quicker than @code{until} without an argument. The specified |
4670 | location is actually reached only if it is in the current frame. This | |
4671 | implies that @code{until} can be used to skip over recursive function | |
4672 | invocations. For instance in the code below, if the current location is | |
4673 | line @code{96}, issuing @code{until 99} will execute the program up to | |
db2e3e2e | 4674 | line @code{99} in the same invocation of factorial, i.e., after the inner |
c60eb6f1 EZ |
4675 | invocations have returned. |
4676 | ||
4677 | @smallexample | |
4678 | 94 int factorial (int value) | |
4679 | 95 @{ | |
4680 | 96 if (value > 1) @{ | |
4681 | 97 value *= factorial (value - 1); | |
4682 | 98 @} | |
4683 | 99 return (value); | |
4684 | 100 @} | |
4685 | @end smallexample | |
4686 | ||
4687 | ||
4688 | @kindex advance @var{location} | |
4689 | @itemx advance @var{location} | |
09d4efe1 | 4690 | Continue running the program up to the given @var{location}. An argument is |
2a25a5ba EZ |
4691 | required, which should be of one of the forms described in |
4692 | @ref{Specify Location}. | |
4693 | Execution will also stop upon exit from the current stack | |
c60eb6f1 EZ |
4694 | frame. This command is similar to @code{until}, but @code{advance} will |
4695 | not skip over recursive function calls, and the target location doesn't | |
4696 | have to be in the same frame as the current one. | |
4697 | ||
c906108c SS |
4698 | |
4699 | @kindex stepi | |
41afff9a | 4700 | @kindex si @r{(@code{stepi})} |
c906108c | 4701 | @item stepi |
96a2c332 | 4702 | @itemx stepi @var{arg} |
c906108c SS |
4703 | @itemx si |
4704 | Execute one machine instruction, then stop and return to the debugger. | |
4705 | ||
4706 | It is often useful to do @samp{display/i $pc} when stepping by machine | |
4707 | instructions. This makes @value{GDBN} automatically display the next | |
4708 | instruction to be executed, each time your program stops. @xref{Auto | |
79a6e687 | 4709 | Display,, Automatic Display}. |
c906108c SS |
4710 | |
4711 | An argument is a repeat count, as in @code{step}. | |
4712 | ||
4713 | @need 750 | |
4714 | @kindex nexti | |
41afff9a | 4715 | @kindex ni @r{(@code{nexti})} |
c906108c | 4716 | @item nexti |
96a2c332 | 4717 | @itemx nexti @var{arg} |
c906108c SS |
4718 | @itemx ni |
4719 | Execute one machine instruction, but if it is a function call, | |
4720 | proceed until the function returns. | |
4721 | ||
4722 | An argument is a repeat count, as in @code{next}. | |
4723 | @end table | |
4724 | ||
6d2ebf8b | 4725 | @node Signals |
c906108c SS |
4726 | @section Signals |
4727 | @cindex signals | |
4728 | ||
4729 | A signal is an asynchronous event that can happen in a program. The | |
4730 | operating system defines the possible kinds of signals, and gives each | |
4731 | kind a name and a number. For example, in Unix @code{SIGINT} is the | |
c8aa23ab | 4732 | signal a program gets when you type an interrupt character (often @kbd{Ctrl-c}); |
c906108c SS |
4733 | @code{SIGSEGV} is the signal a program gets from referencing a place in |
4734 | memory far away from all the areas in use; @code{SIGALRM} occurs when | |
4735 | the alarm clock timer goes off (which happens only if your program has | |
4736 | requested an alarm). | |
4737 | ||
4738 | @cindex fatal signals | |
4739 | Some signals, including @code{SIGALRM}, are a normal part of the | |
4740 | functioning of your program. Others, such as @code{SIGSEGV}, indicate | |
d4f3574e | 4741 | errors; these signals are @dfn{fatal} (they kill your program immediately) if the |
c906108c SS |
4742 | program has not specified in advance some other way to handle the signal. |
4743 | @code{SIGINT} does not indicate an error in your program, but it is normally | |
4744 | fatal so it can carry out the purpose of the interrupt: to kill the program. | |
4745 | ||
4746 | @value{GDBN} has the ability to detect any occurrence of a signal in your | |
4747 | program. You can tell @value{GDBN} in advance what to do for each kind of | |
4748 | signal. | |
4749 | ||
4750 | @cindex handling signals | |
24f93129 EZ |
4751 | Normally, @value{GDBN} is set up to let the non-erroneous signals like |
4752 | @code{SIGALRM} be silently passed to your program | |
4753 | (so as not to interfere with their role in the program's functioning) | |
c906108c SS |
4754 | but to stop your program immediately whenever an error signal happens. |
4755 | You can change these settings with the @code{handle} command. | |
4756 | ||
4757 | @table @code | |
4758 | @kindex info signals | |
09d4efe1 | 4759 | @kindex info handle |
c906108c | 4760 | @item info signals |
96a2c332 | 4761 | @itemx info handle |
c906108c SS |
4762 | Print a table of all the kinds of signals and how @value{GDBN} has been told to |
4763 | handle each one. You can use this to see the signal numbers of all | |
4764 | the defined types of signals. | |
4765 | ||
45ac1734 EZ |
4766 | @item info signals @var{sig} |
4767 | Similar, but print information only about the specified signal number. | |
4768 | ||
d4f3574e | 4769 | @code{info handle} is an alias for @code{info signals}. |
c906108c SS |
4770 | |
4771 | @kindex handle | |
45ac1734 | 4772 | @item handle @var{signal} @r{[}@var{keywords}@dots{}@r{]} |
5ece1a18 EZ |
4773 | Change the way @value{GDBN} handles signal @var{signal}. @var{signal} |
4774 | can be the number of a signal or its name (with or without the | |
24f93129 | 4775 | @samp{SIG} at the beginning); a list of signal numbers of the form |
5ece1a18 | 4776 | @samp{@var{low}-@var{high}}; or the word @samp{all}, meaning all the |
45ac1734 EZ |
4777 | known signals. Optional arguments @var{keywords}, described below, |
4778 | say what change to make. | |
c906108c SS |
4779 | @end table |
4780 | ||
4781 | @c @group | |
4782 | The keywords allowed by the @code{handle} command can be abbreviated. | |
4783 | Their full names are: | |
4784 | ||
4785 | @table @code | |
4786 | @item nostop | |
4787 | @value{GDBN} should not stop your program when this signal happens. It may | |
4788 | still print a message telling you that the signal has come in. | |
4789 | ||
4790 | @item stop | |
4791 | @value{GDBN} should stop your program when this signal happens. This implies | |
4792 | the @code{print} keyword as well. | |
4793 | ||
4794 | @item print | |
4795 | @value{GDBN} should print a message when this signal happens. | |
4796 | ||
4797 | @item noprint | |
4798 | @value{GDBN} should not mention the occurrence of the signal at all. This | |
4799 | implies the @code{nostop} keyword as well. | |
4800 | ||
4801 | @item pass | |
5ece1a18 | 4802 | @itemx noignore |
c906108c SS |
4803 | @value{GDBN} should allow your program to see this signal; your program |
4804 | can handle the signal, or else it may terminate if the signal is fatal | |
5ece1a18 | 4805 | and not handled. @code{pass} and @code{noignore} are synonyms. |
c906108c SS |
4806 | |
4807 | @item nopass | |
5ece1a18 | 4808 | @itemx ignore |
c906108c | 4809 | @value{GDBN} should not allow your program to see this signal. |
5ece1a18 | 4810 | @code{nopass} and @code{ignore} are synonyms. |
c906108c SS |
4811 | @end table |
4812 | @c @end group | |
4813 | ||
d4f3574e SS |
4814 | When a signal stops your program, the signal is not visible to the |
4815 | program until you | |
c906108c SS |
4816 | continue. Your program sees the signal then, if @code{pass} is in |
4817 | effect for the signal in question @emph{at that time}. In other words, | |
4818 | after @value{GDBN} reports a signal, you can use the @code{handle} | |
4819 | command with @code{pass} or @code{nopass} to control whether your | |
4820 | program sees that signal when you continue. | |
4821 | ||
24f93129 EZ |
4822 | The default is set to @code{nostop}, @code{noprint}, @code{pass} for |
4823 | non-erroneous signals such as @code{SIGALRM}, @code{SIGWINCH} and | |
4824 | @code{SIGCHLD}, and to @code{stop}, @code{print}, @code{pass} for the | |
4825 | erroneous signals. | |
4826 | ||
c906108c SS |
4827 | You can also use the @code{signal} command to prevent your program from |
4828 | seeing a signal, or cause it to see a signal it normally would not see, | |
4829 | or to give it any signal at any time. For example, if your program stopped | |
4830 | due to some sort of memory reference error, you might store correct | |
4831 | values into the erroneous variables and continue, hoping to see more | |
4832 | execution; but your program would probably terminate immediately as | |
4833 | a result of the fatal signal once it saw the signal. To prevent this, | |
4834 | you can continue with @samp{signal 0}. @xref{Signaling, ,Giving your | |
79a6e687 | 4835 | Program a Signal}. |
c906108c | 4836 | |
4aa995e1 PA |
4837 | @cindex extra signal information |
4838 | @anchor{extra signal information} | |
4839 | ||
4840 | On some targets, @value{GDBN} can inspect extra signal information | |
4841 | associated with the intercepted signal, before it is actually | |
4842 | delivered to the program being debugged. This information is exported | |
4843 | by the convenience variable @code{$_siginfo}, and consists of data | |
4844 | that is passed by the kernel to the signal handler at the time of the | |
4845 | receipt of a signal. The data type of the information itself is | |
4846 | target dependent. You can see the data type using the @code{ptype | |
4847 | $_siginfo} command. On Unix systems, it typically corresponds to the | |
4848 | standard @code{siginfo_t} type, as defined in the @file{signal.h} | |
4849 | system header. | |
4850 | ||
4851 | Here's an example, on a @sc{gnu}/Linux system, printing the stray | |
4852 | referenced address that raised a segmentation fault. | |
4853 | ||
4854 | @smallexample | |
4855 | @group | |
4856 | (@value{GDBP}) continue | |
4857 | Program received signal SIGSEGV, Segmentation fault. | |
4858 | 0x0000000000400766 in main () | |
4859 | 69 *(int *)p = 0; | |
4860 | (@value{GDBP}) ptype $_siginfo | |
4861 | type = struct @{ | |
4862 | int si_signo; | |
4863 | int si_errno; | |
4864 | int si_code; | |
4865 | union @{ | |
4866 | int _pad[28]; | |
4867 | struct @{...@} _kill; | |
4868 | struct @{...@} _timer; | |
4869 | struct @{...@} _rt; | |
4870 | struct @{...@} _sigchld; | |
4871 | struct @{...@} _sigfault; | |
4872 | struct @{...@} _sigpoll; | |
4873 | @} _sifields; | |
4874 | @} | |
4875 | (@value{GDBP}) ptype $_siginfo._sifields._sigfault | |
4876 | type = struct @{ | |
4877 | void *si_addr; | |
4878 | @} | |
4879 | (@value{GDBP}) p $_siginfo._sifields._sigfault.si_addr | |
4880 | $1 = (void *) 0x7ffff7ff7000 | |
4881 | @end group | |
4882 | @end smallexample | |
4883 | ||
4884 | Depending on target support, @code{$_siginfo} may also be writable. | |
4885 | ||
6d2ebf8b | 4886 | @node Thread Stops |
79a6e687 | 4887 | @section Stopping and Starting Multi-thread Programs |
c906108c | 4888 | |
0606b73b SL |
4889 | @cindex stopped threads |
4890 | @cindex threads, stopped | |
4891 | ||
4892 | @cindex continuing threads | |
4893 | @cindex threads, continuing | |
4894 | ||
4895 | @value{GDBN} supports debugging programs with multiple threads | |
4896 | (@pxref{Threads,, Debugging Programs with Multiple Threads}). There | |
4897 | are two modes of controlling execution of your program within the | |
4898 | debugger. In the default mode, referred to as @dfn{all-stop mode}, | |
4899 | when any thread in your program stops (for example, at a breakpoint | |
4900 | or while being stepped), all other threads in the program are also stopped by | |
4901 | @value{GDBN}. On some targets, @value{GDBN} also supports | |
4902 | @dfn{non-stop mode}, in which other threads can continue to run freely while | |
4903 | you examine the stopped thread in the debugger. | |
4904 | ||
4905 | @menu | |
4906 | * All-Stop Mode:: All threads stop when GDB takes control | |
4907 | * Non-Stop Mode:: Other threads continue to execute | |
4908 | * Background Execution:: Running your program asynchronously | |
4909 | * Thread-Specific Breakpoints:: Controlling breakpoints | |
4910 | * Interrupted System Calls:: GDB may interfere with system calls | |
4911 | @end menu | |
4912 | ||
4913 | @node All-Stop Mode | |
4914 | @subsection All-Stop Mode | |
4915 | ||
4916 | @cindex all-stop mode | |
4917 | ||
4918 | In all-stop mode, whenever your program stops under @value{GDBN} for any reason, | |
4919 | @emph{all} threads of execution stop, not just the current thread. This | |
4920 | allows you to examine the overall state of the program, including | |
4921 | switching between threads, without worrying that things may change | |
4922 | underfoot. | |
4923 | ||
4924 | Conversely, whenever you restart the program, @emph{all} threads start | |
4925 | executing. @emph{This is true even when single-stepping} with commands | |
4926 | like @code{step} or @code{next}. | |
4927 | ||
4928 | In particular, @value{GDBN} cannot single-step all threads in lockstep. | |
4929 | Since thread scheduling is up to your debugging target's operating | |
4930 | system (not controlled by @value{GDBN}), other threads may | |
4931 | execute more than one statement while the current thread completes a | |
4932 | single step. Moreover, in general other threads stop in the middle of a | |
4933 | statement, rather than at a clean statement boundary, when the program | |
4934 | stops. | |
4935 | ||
4936 | You might even find your program stopped in another thread after | |
4937 | continuing or even single-stepping. This happens whenever some other | |
4938 | thread runs into a breakpoint, a signal, or an exception before the | |
4939 | first thread completes whatever you requested. | |
4940 | ||
4941 | @cindex automatic thread selection | |
4942 | @cindex switching threads automatically | |
4943 | @cindex threads, automatic switching | |
4944 | Whenever @value{GDBN} stops your program, due to a breakpoint or a | |
4945 | signal, it automatically selects the thread where that breakpoint or | |
4946 | signal happened. @value{GDBN} alerts you to the context switch with a | |
4947 | message such as @samp{[Switching to Thread @var{n}]} to identify the | |
4948 | thread. | |
4949 | ||
4950 | On some OSes, you can modify @value{GDBN}'s default behavior by | |
4951 | locking the OS scheduler to allow only a single thread to run. | |
4952 | ||
4953 | @table @code | |
4954 | @item set scheduler-locking @var{mode} | |
4955 | @cindex scheduler locking mode | |
4956 | @cindex lock scheduler | |
4957 | Set the scheduler locking mode. If it is @code{off}, then there is no | |
4958 | locking and any thread may run at any time. If @code{on}, then only the | |
4959 | current thread may run when the inferior is resumed. The @code{step} | |
4960 | mode optimizes for single-stepping; it prevents other threads | |
4961 | from preempting the current thread while you are stepping, so that | |
4962 | the focus of debugging does not change unexpectedly. | |
4963 | Other threads only rarely (or never) get a chance to run | |
4964 | when you step. They are more likely to run when you @samp{next} over a | |
4965 | function call, and they are completely free to run when you use commands | |
4966 | like @samp{continue}, @samp{until}, or @samp{finish}. However, unless another | |
4967 | thread hits a breakpoint during its timeslice, @value{GDBN} does not change | |
4968 | the current thread away from the thread that you are debugging. | |
4969 | ||
4970 | @item show scheduler-locking | |
4971 | Display the current scheduler locking mode. | |
4972 | @end table | |
4973 | ||
d4db2f36 PA |
4974 | @cindex resume threads of multiple processes simultaneously |
4975 | By default, when you issue one of the execution commands such as | |
4976 | @code{continue}, @code{next} or @code{step}, @value{GDBN} allows only | |
4977 | threads of the current inferior to run. For example, if @value{GDBN} | |
4978 | is attached to two inferiors, each with two threads, the | |
4979 | @code{continue} command resumes only the two threads of the current | |
4980 | inferior. This is useful, for example, when you debug a program that | |
4981 | forks and you want to hold the parent stopped (so that, for instance, | |
4982 | it doesn't run to exit), while you debug the child. In other | |
4983 | situations, you may not be interested in inspecting the current state | |
4984 | of any of the processes @value{GDBN} is attached to, and you may want | |
4985 | to resume them all until some breakpoint is hit. In the latter case, | |
4986 | you can instruct @value{GDBN} to allow all threads of all the | |
4987 | inferiors to run with the @w{@code{set schedule-multiple}} command. | |
4988 | ||
4989 | @table @code | |
4990 | @kindex set schedule-multiple | |
4991 | @item set schedule-multiple | |
4992 | Set the mode for allowing threads of multiple processes to be resumed | |
4993 | when an execution command is issued. When @code{on}, all threads of | |
4994 | all processes are allowed to run. When @code{off}, only the threads | |
4995 | of the current process are resumed. The default is @code{off}. The | |
4996 | @code{scheduler-locking} mode takes precedence when set to @code{on}, | |
4997 | or while you are stepping and set to @code{step}. | |
4998 | ||
4999 | @item show schedule-multiple | |
5000 | Display the current mode for resuming the execution of threads of | |
5001 | multiple processes. | |
5002 | @end table | |
5003 | ||
0606b73b SL |
5004 | @node Non-Stop Mode |
5005 | @subsection Non-Stop Mode | |
5006 | ||
5007 | @cindex non-stop mode | |
5008 | ||
5009 | @c This section is really only a place-holder, and needs to be expanded | |
5010 | @c with more details. | |
5011 | ||
5012 | For some multi-threaded targets, @value{GDBN} supports an optional | |
5013 | mode of operation in which you can examine stopped program threads in | |
5014 | the debugger while other threads continue to execute freely. This | |
5015 | minimizes intrusion when debugging live systems, such as programs | |
5016 | where some threads have real-time constraints or must continue to | |
5017 | respond to external events. This is referred to as @dfn{non-stop} mode. | |
5018 | ||
5019 | In non-stop mode, when a thread stops to report a debugging event, | |
5020 | @emph{only} that thread is stopped; @value{GDBN} does not stop other | |
5021 | threads as well, in contrast to the all-stop mode behavior. Additionally, | |
5022 | execution commands such as @code{continue} and @code{step} apply by default | |
5023 | only to the current thread in non-stop mode, rather than all threads as | |
5024 | in all-stop mode. This allows you to control threads explicitly in | |
5025 | ways that are not possible in all-stop mode --- for example, stepping | |
5026 | one thread while allowing others to run freely, stepping | |
5027 | one thread while holding all others stopped, or stepping several threads | |
5028 | independently and simultaneously. | |
5029 | ||
5030 | To enter non-stop mode, use this sequence of commands before you run | |
5031 | or attach to your program: | |
5032 | ||
0606b73b SL |
5033 | @smallexample |
5034 | # Enable the async interface. | |
c6ebd6cf | 5035 | set target-async 1 |
0606b73b | 5036 | |
0606b73b SL |
5037 | # If using the CLI, pagination breaks non-stop. |
5038 | set pagination off | |
5039 | ||
5040 | # Finally, turn it on! | |
5041 | set non-stop on | |
5042 | @end smallexample | |
5043 | ||
5044 | You can use these commands to manipulate the non-stop mode setting: | |
5045 | ||
5046 | @table @code | |
5047 | @kindex set non-stop | |
5048 | @item set non-stop on | |
5049 | Enable selection of non-stop mode. | |
5050 | @item set non-stop off | |
5051 | Disable selection of non-stop mode. | |
5052 | @kindex show non-stop | |
5053 | @item show non-stop | |
5054 | Show the current non-stop enablement setting. | |
5055 | @end table | |
5056 | ||
5057 | Note these commands only reflect whether non-stop mode is enabled, | |
5058 | not whether the currently-executing program is being run in non-stop mode. | |
5059 | In particular, the @code{set non-stop} preference is only consulted when | |
5060 | @value{GDBN} starts or connects to the target program, and it is generally | |
5061 | not possible to switch modes once debugging has started. Furthermore, | |
5062 | since not all targets support non-stop mode, even when you have enabled | |
5063 | non-stop mode, @value{GDBN} may still fall back to all-stop operation by | |
5064 | default. | |
5065 | ||
5066 | In non-stop mode, all execution commands apply only to the current thread | |
5067 | by default. That is, @code{continue} only continues one thread. | |
5068 | To continue all threads, issue @code{continue -a} or @code{c -a}. | |
5069 | ||
5070 | You can use @value{GDBN}'s background execution commands | |
5071 | (@pxref{Background Execution}) to run some threads in the background | |
5072 | while you continue to examine or step others from @value{GDBN}. | |
5073 | The MI execution commands (@pxref{GDB/MI Program Execution}) are | |
5074 | always executed asynchronously in non-stop mode. | |
5075 | ||
5076 | Suspending execution is done with the @code{interrupt} command when | |
5077 | running in the background, or @kbd{Ctrl-c} during foreground execution. | |
5078 | In all-stop mode, this stops the whole process; | |
5079 | but in non-stop mode the interrupt applies only to the current thread. | |
5080 | To stop the whole program, use @code{interrupt -a}. | |
5081 | ||
5082 | Other execution commands do not currently support the @code{-a} option. | |
5083 | ||
5084 | In non-stop mode, when a thread stops, @value{GDBN} doesn't automatically make | |
5085 | that thread current, as it does in all-stop mode. This is because the | |
5086 | thread stop notifications are asynchronous with respect to @value{GDBN}'s | |
5087 | command interpreter, and it would be confusing if @value{GDBN} unexpectedly | |
5088 | changed to a different thread just as you entered a command to operate on the | |
5089 | previously current thread. | |
5090 | ||
5091 | @node Background Execution | |
5092 | @subsection Background Execution | |
5093 | ||
5094 | @cindex foreground execution | |
5095 | @cindex background execution | |
5096 | @cindex asynchronous execution | |
5097 | @cindex execution, foreground, background and asynchronous | |
5098 | ||
5099 | @value{GDBN}'s execution commands have two variants: the normal | |
5100 | foreground (synchronous) behavior, and a background | |
5101 | (asynchronous) behavior. In foreground execution, @value{GDBN} waits for | |
5102 | the program to report that some thread has stopped before prompting for | |
5103 | another command. In background execution, @value{GDBN} immediately gives | |
5104 | a command prompt so that you can issue other commands while your program runs. | |
5105 | ||
32fc0df9 PA |
5106 | You need to explicitly enable asynchronous mode before you can use |
5107 | background execution commands. You can use these commands to | |
5108 | manipulate the asynchronous mode setting: | |
5109 | ||
5110 | @table @code | |
5111 | @kindex set target-async | |
5112 | @item set target-async on | |
5113 | Enable asynchronous mode. | |
5114 | @item set target-async off | |
5115 | Disable asynchronous mode. | |
5116 | @kindex show target-async | |
5117 | @item show target-async | |
5118 | Show the current target-async setting. | |
5119 | @end table | |
5120 | ||
5121 | If the target doesn't support async mode, @value{GDBN} issues an error | |
5122 | message if you attempt to use the background execution commands. | |
5123 | ||
0606b73b SL |
5124 | To specify background execution, add a @code{&} to the command. For example, |
5125 | the background form of the @code{continue} command is @code{continue&}, or | |
5126 | just @code{c&}. The execution commands that accept background execution | |
5127 | are: | |
5128 | ||
5129 | @table @code | |
5130 | @kindex run& | |
5131 | @item run | |
5132 | @xref{Starting, , Starting your Program}. | |
5133 | ||
5134 | @item attach | |
5135 | @kindex attach& | |
5136 | @xref{Attach, , Debugging an Already-running Process}. | |
5137 | ||
5138 | @item step | |
5139 | @kindex step& | |
5140 | @xref{Continuing and Stepping, step}. | |
5141 | ||
5142 | @item stepi | |
5143 | @kindex stepi& | |
5144 | @xref{Continuing and Stepping, stepi}. | |
5145 | ||
5146 | @item next | |
5147 | @kindex next& | |
5148 | @xref{Continuing and Stepping, next}. | |
5149 | ||
7ce58dd2 DE |
5150 | @item nexti |
5151 | @kindex nexti& | |
5152 | @xref{Continuing and Stepping, nexti}. | |
5153 | ||
0606b73b SL |
5154 | @item continue |
5155 | @kindex continue& | |
5156 | @xref{Continuing and Stepping, continue}. | |
5157 | ||
5158 | @item finish | |
5159 | @kindex finish& | |
5160 | @xref{Continuing and Stepping, finish}. | |
5161 | ||
5162 | @item until | |
5163 | @kindex until& | |
5164 | @xref{Continuing and Stepping, until}. | |
5165 | ||
5166 | @end table | |
5167 | ||
5168 | Background execution is especially useful in conjunction with non-stop | |
5169 | mode for debugging programs with multiple threads; see @ref{Non-Stop Mode}. | |
5170 | However, you can also use these commands in the normal all-stop mode with | |
5171 | the restriction that you cannot issue another execution command until the | |
5172 | previous one finishes. Examples of commands that are valid in all-stop | |
5173 | mode while the program is running include @code{help} and @code{info break}. | |
5174 | ||
5175 | You can interrupt your program while it is running in the background by | |
5176 | using the @code{interrupt} command. | |
5177 | ||
5178 | @table @code | |
5179 | @kindex interrupt | |
5180 | @item interrupt | |
5181 | @itemx interrupt -a | |
5182 | ||
5183 | Suspend execution of the running program. In all-stop mode, | |
5184 | @code{interrupt} stops the whole process, but in non-stop mode, it stops | |
5185 | only the current thread. To stop the whole program in non-stop mode, | |
5186 | use @code{interrupt -a}. | |
5187 | @end table | |
5188 | ||
0606b73b SL |
5189 | @node Thread-Specific Breakpoints |
5190 | @subsection Thread-Specific Breakpoints | |
5191 | ||
c906108c | 5192 | When your program has multiple threads (@pxref{Threads,, Debugging |
79a6e687 | 5193 | Programs with Multiple Threads}), you can choose whether to set |
c906108c SS |
5194 | breakpoints on all threads, or on a particular thread. |
5195 | ||
5196 | @table @code | |
5197 | @cindex breakpoints and threads | |
5198 | @cindex thread breakpoints | |
5199 | @kindex break @dots{} thread @var{threadno} | |
5200 | @item break @var{linespec} thread @var{threadno} | |
5201 | @itemx break @var{linespec} thread @var{threadno} if @dots{} | |
5202 | @var{linespec} specifies source lines; there are several ways of | |
2a25a5ba EZ |
5203 | writing them (@pxref{Specify Location}), but the effect is always to |
5204 | specify some source line. | |
c906108c SS |
5205 | |
5206 | Use the qualifier @samp{thread @var{threadno}} with a breakpoint command | |
5207 | to specify that you only want @value{GDBN} to stop the program when a | |
5208 | particular thread reaches this breakpoint. @var{threadno} is one of the | |
5209 | numeric thread identifiers assigned by @value{GDBN}, shown in the first | |
5210 | column of the @samp{info threads} display. | |
5211 | ||
5212 | If you do not specify @samp{thread @var{threadno}} when you set a | |
5213 | breakpoint, the breakpoint applies to @emph{all} threads of your | |
5214 | program. | |
5215 | ||
5216 | You can use the @code{thread} qualifier on conditional breakpoints as | |
5217 | well; in this case, place @samp{thread @var{threadno}} before the | |
5218 | breakpoint condition, like this: | |
5219 | ||
5220 | @smallexample | |
2df3850c | 5221 | (@value{GDBP}) break frik.c:13 thread 28 if bartab > lim |
c906108c SS |
5222 | @end smallexample |
5223 | ||
5224 | @end table | |
5225 | ||
0606b73b SL |
5226 | @node Interrupted System Calls |
5227 | @subsection Interrupted System Calls | |
c906108c | 5228 | |
36d86913 MC |
5229 | @cindex thread breakpoints and system calls |
5230 | @cindex system calls and thread breakpoints | |
5231 | @cindex premature return from system calls | |
0606b73b SL |
5232 | There is an unfortunate side effect when using @value{GDBN} to debug |
5233 | multi-threaded programs. If one thread stops for a | |
36d86913 MC |
5234 | breakpoint, or for some other reason, and another thread is blocked in a |
5235 | system call, then the system call may return prematurely. This is a | |
5236 | consequence of the interaction between multiple threads and the signals | |
5237 | that @value{GDBN} uses to implement breakpoints and other events that | |
5238 | stop execution. | |
5239 | ||
5240 | To handle this problem, your program should check the return value of | |
5241 | each system call and react appropriately. This is good programming | |
5242 | style anyways. | |
5243 | ||
5244 | For example, do not write code like this: | |
5245 | ||
5246 | @smallexample | |
5247 | sleep (10); | |
5248 | @end smallexample | |
5249 | ||
5250 | The call to @code{sleep} will return early if a different thread stops | |
5251 | at a breakpoint or for some other reason. | |
5252 | ||
5253 | Instead, write this: | |
5254 | ||
5255 | @smallexample | |
5256 | int unslept = 10; | |
5257 | while (unslept > 0) | |
5258 | unslept = sleep (unslept); | |
5259 | @end smallexample | |
5260 | ||
5261 | A system call is allowed to return early, so the system is still | |
5262 | conforming to its specification. But @value{GDBN} does cause your | |
5263 | multi-threaded program to behave differently than it would without | |
5264 | @value{GDBN}. | |
5265 | ||
5266 | Also, @value{GDBN} uses internal breakpoints in the thread library to | |
5267 | monitor certain events such as thread creation and thread destruction. | |
5268 | When such an event happens, a system call in another thread may return | |
5269 | prematurely, even though your program does not appear to stop. | |
5270 | ||
c906108c | 5271 | |
bacec72f MS |
5272 | @node Reverse Execution |
5273 | @chapter Running programs backward | |
5274 | @cindex reverse execution | |
5275 | @cindex running programs backward | |
5276 | ||
5277 | When you are debugging a program, it is not unusual to realize that | |
5278 | you have gone too far, and some event of interest has already happened. | |
5279 | If the target environment supports it, @value{GDBN} can allow you to | |
5280 | ``rewind'' the program by running it backward. | |
5281 | ||
5282 | A target environment that supports reverse execution should be able | |
5283 | to ``undo'' the changes in machine state that have taken place as the | |
5284 | program was executing normally. Variables, registers etc.@: should | |
5285 | revert to their previous values. Obviously this requires a great | |
5286 | deal of sophistication on the part of the target environment; not | |
5287 | all target environments can support reverse execution. | |
5288 | ||
5289 | When a program is executed in reverse, the instructions that | |
5290 | have most recently been executed are ``un-executed'', in reverse | |
5291 | order. The program counter runs backward, following the previous | |
5292 | thread of execution in reverse. As each instruction is ``un-executed'', | |
5293 | the values of memory and/or registers that were changed by that | |
5294 | instruction are reverted to their previous states. After executing | |
5295 | a piece of source code in reverse, all side effects of that code | |
5296 | should be ``undone'', and all variables should be returned to their | |
5297 | prior values@footnote{ | |
5298 | Note that some side effects are easier to undo than others. For instance, | |
5299 | memory and registers are relatively easy, but device I/O is hard. Some | |
5300 | targets may be able undo things like device I/O, and some may not. | |
5301 | ||
5302 | The contract between @value{GDBN} and the reverse executing target | |
5303 | requires only that the target do something reasonable when | |
5304 | @value{GDBN} tells it to execute backwards, and then report the | |
5305 | results back to @value{GDBN}. Whatever the target reports back to | |
5306 | @value{GDBN}, @value{GDBN} will report back to the user. @value{GDBN} | |
5307 | assumes that the memory and registers that the target reports are in a | |
5308 | consistant state, but @value{GDBN} accepts whatever it is given. | |
5309 | }. | |
5310 | ||
5311 | If you are debugging in a target environment that supports | |
5312 | reverse execution, @value{GDBN} provides the following commands. | |
5313 | ||
5314 | @table @code | |
5315 | @kindex reverse-continue | |
5316 | @kindex rc @r{(@code{reverse-continue})} | |
5317 | @item reverse-continue @r{[}@var{ignore-count}@r{]} | |
5318 | @itemx rc @r{[}@var{ignore-count}@r{]} | |
5319 | Beginning at the point where your program last stopped, start executing | |
5320 | in reverse. Reverse execution will stop for breakpoints and synchronous | |
5321 | exceptions (signals), just like normal execution. Behavior of | |
5322 | asynchronous signals depends on the target environment. | |
5323 | ||
5324 | @kindex reverse-step | |
5325 | @kindex rs @r{(@code{step})} | |
5326 | @item reverse-step @r{[}@var{count}@r{]} | |
5327 | Run the program backward until control reaches the start of a | |
5328 | different source line; then stop it, and return control to @value{GDBN}. | |
5329 | ||
5330 | Like the @code{step} command, @code{reverse-step} will only stop | |
5331 | at the beginning of a source line. It ``un-executes'' the previously | |
5332 | executed source line. If the previous source line included calls to | |
5333 | debuggable functions, @code{reverse-step} will step (backward) into | |
5334 | the called function, stopping at the beginning of the @emph{last} | |
5335 | statement in the called function (typically a return statement). | |
5336 | ||
5337 | Also, as with the @code{step} command, if non-debuggable functions are | |
5338 | called, @code{reverse-step} will run thru them backward without stopping. | |
5339 | ||
5340 | @kindex reverse-stepi | |
5341 | @kindex rsi @r{(@code{reverse-stepi})} | |
5342 | @item reverse-stepi @r{[}@var{count}@r{]} | |
5343 | Reverse-execute one machine instruction. Note that the instruction | |
5344 | to be reverse-executed is @emph{not} the one pointed to by the program | |
5345 | counter, but the instruction executed prior to that one. For instance, | |
5346 | if the last instruction was a jump, @code{reverse-stepi} will take you | |
5347 | back from the destination of the jump to the jump instruction itself. | |
5348 | ||
5349 | @kindex reverse-next | |
5350 | @kindex rn @r{(@code{reverse-next})} | |
5351 | @item reverse-next @r{[}@var{count}@r{]} | |
5352 | Run backward to the beginning of the previous line executed in | |
5353 | the current (innermost) stack frame. If the line contains function | |
5354 | calls, they will be ``un-executed'' without stopping. Starting from | |
5355 | the first line of a function, @code{reverse-next} will take you back | |
5356 | to the caller of that function, @emph{before} the function was called, | |
5357 | just as the normal @code{next} command would take you from the last | |
5358 | line of a function back to its return to its caller | |
5359 | @footnote{Unles the code is too heavily optimized.}. | |
5360 | ||
5361 | @kindex reverse-nexti | |
5362 | @kindex rni @r{(@code{reverse-nexti})} | |
5363 | @item reverse-nexti @r{[}@var{count}@r{]} | |
5364 | Like @code{nexti}, @code{reverse-nexti} executes a single instruction | |
5365 | in reverse, except that called functions are ``un-executed'' atomically. | |
5366 | That is, if the previously executed instruction was a return from | |
5367 | another instruction, @code{reverse-nexti} will continue to execute | |
5368 | in reverse until the call to that function (from the current stack | |
5369 | frame) is reached. | |
5370 | ||
5371 | @kindex reverse-finish | |
5372 | @item reverse-finish | |
5373 | Just as the @code{finish} command takes you to the point where the | |
5374 | current function returns, @code{reverse-finish} takes you to the point | |
5375 | where it was called. Instead of ending up at the end of the current | |
5376 | function invocation, you end up at the beginning. | |
5377 | ||
5378 | @kindex set exec-direction | |
5379 | @item set exec-direction | |
5380 | Set the direction of target execution. | |
5381 | @itemx set exec-direction reverse | |
5382 | @cindex execute forward or backward in time | |
5383 | @value{GDBN} will perform all execution commands in reverse, until the | |
5384 | exec-direction mode is changed to ``forward''. Affected commands include | |
5385 | @code{step, stepi, next, nexti, continue, and finish}. The @code{return} | |
5386 | command cannot be used in reverse mode. | |
5387 | @item set exec-direction forward | |
5388 | @value{GDBN} will perform all execution commands in the normal fashion. | |
5389 | This is the default. | |
5390 | @end table | |
5391 | ||
c906108c | 5392 | |
a2311334 EZ |
5393 | @node Process Record and Replay |
5394 | @chapter Recording Inferior's Execution and Replaying It | |
53cc454a HZ |
5395 | @cindex process record and replay |
5396 | @cindex recording inferior's execution and replaying it | |
5397 | ||
8e05493c EZ |
5398 | On some platforms, @value{GDBN} provides a special @dfn{process record |
5399 | and replay} target that can record a log of the process execution, and | |
5400 | replay it later with both forward and reverse execution commands. | |
a2311334 EZ |
5401 | |
5402 | @cindex replay mode | |
5403 | When this target is in use, if the execution log includes the record | |
5404 | for the next instruction, @value{GDBN} will debug in @dfn{replay | |
5405 | mode}. In the replay mode, the inferior does not really execute code | |
5406 | instructions. Instead, all the events that normally happen during | |
5407 | code execution are taken from the execution log. While code is not | |
5408 | really executed in replay mode, the values of registers (including the | |
5409 | program counter register) and the memory of the inferior are still | |
8e05493c EZ |
5410 | changed as they normally would. Their contents are taken from the |
5411 | execution log. | |
a2311334 EZ |
5412 | |
5413 | @cindex record mode | |
5414 | If the record for the next instruction is not in the execution log, | |
5415 | @value{GDBN} will debug in @dfn{record mode}. In this mode, the | |
5416 | inferior executes normally, and @value{GDBN} records the execution log | |
5417 | for future replay. | |
5418 | ||
8e05493c EZ |
5419 | The process record and replay target supports reverse execution |
5420 | (@pxref{Reverse Execution}), even if the platform on which the | |
5421 | inferior runs does not. However, the reverse execution is limited in | |
5422 | this case by the range of the instructions recorded in the execution | |
5423 | log. In other words, reverse execution on platforms that don't | |
5424 | support it directly can only be done in the replay mode. | |
5425 | ||
5426 | When debugging in the reverse direction, @value{GDBN} will work in | |
5427 | replay mode as long as the execution log includes the record for the | |
5428 | previous instruction; otherwise, it will work in record mode, if the | |
5429 | platform supports reverse execution, or stop if not. | |
5430 | ||
a2311334 EZ |
5431 | For architecture environments that support process record and replay, |
5432 | @value{GDBN} provides the following commands: | |
53cc454a HZ |
5433 | |
5434 | @table @code | |
5435 | @kindex target record | |
5436 | @kindex record | |
5437 | @kindex rec | |
5438 | @item target record | |
a2311334 EZ |
5439 | This command starts the process record and replay target. The process |
5440 | record and replay target can only debug a process that is already | |
5441 | running. Therefore, you need first to start the process with the | |
5442 | @kbd{run} or @kbd{start} commands, and then start the recording with | |
5443 | the @kbd{target record} command. | |
5444 | ||
5445 | Both @code{record} and @code{rec} are aliases of @code{target record}. | |
5446 | ||
5447 | @cindex displaced stepping, and process record and replay | |
5448 | Displaced stepping (@pxref{Maintenance Commands,, displaced stepping}) | |
5449 | will be automatically disabled when process record and replay target | |
5450 | is started. That's because the process record and replay target | |
5451 | doesn't support displaced stepping. | |
5452 | ||
5453 | @cindex non-stop mode, and process record and replay | |
5454 | @cindex asynchronous execution, and process record and replay | |
5455 | If the inferior is in the non-stop mode (@pxref{Non-Stop Mode}) or in | |
5456 | the asynchronous execution mode (@pxref{Background Execution}), the | |
5457 | process record and replay target cannot be started because it doesn't | |
5458 | support these two modes. | |
53cc454a HZ |
5459 | |
5460 | @kindex record stop | |
5461 | @kindex rec s | |
5462 | @item record stop | |
a2311334 EZ |
5463 | Stop the process record and replay target. When process record and |
5464 | replay target stops, the entire execution log will be deleted and the | |
5465 | inferior will either be terminated, or will remain in its final state. | |
53cc454a | 5466 | |
a2311334 EZ |
5467 | When you stop the process record and replay target in record mode (at |
5468 | the end of the execution log), the inferior will be stopped at the | |
5469 | next instruction that would have been recorded. In other words, if | |
5470 | you record for a while and then stop recording, the inferior process | |
5471 | will be left in the same state as if the recording never happened. | |
53cc454a | 5472 | |
a2311334 EZ |
5473 | On the other hand, if the process record and replay target is stopped |
5474 | while in replay mode (that is, not at the end of the execution log, | |
5475 | but at some earlier point), the inferior process will become ``live'' | |
5476 | at that earlier state, and it will then be possible to continue the | |
5477 | usual ``live'' debugging of the process from that state. | |
53cc454a | 5478 | |
a2311334 EZ |
5479 | When the inferior process exits, or @value{GDBN} detaches from it, |
5480 | process record and replay target will automatically stop itself. | |
53cc454a HZ |
5481 | |
5482 | @kindex set record insn-number-max | |
5483 | @item set record insn-number-max @var{limit} | |
5484 | Set the limit of instructions to be recorded. Default value is 200000. | |
5485 | ||
a2311334 EZ |
5486 | If @var{limit} is a positive number, then @value{GDBN} will start |
5487 | deleting instructions from the log once the number of the record | |
5488 | instructions becomes greater than @var{limit}. For every new recorded | |
5489 | instruction, @value{GDBN} will delete the earliest recorded | |
5490 | instruction to keep the number of recorded instructions at the limit. | |
5491 | (Since deleting recorded instructions loses information, @value{GDBN} | |
5492 | lets you control what happens when the limit is reached, by means of | |
5493 | the @code{stop-at-limit} option, described below.) | |
53cc454a | 5494 | |
a2311334 EZ |
5495 | If @var{limit} is zero, @value{GDBN} will never delete recorded |
5496 | instructions from the execution log. The number of recorded | |
5497 | instructions is unlimited in this case. | |
53cc454a HZ |
5498 | |
5499 | @kindex show record insn-number-max | |
5500 | @item show record insn-number-max | |
a2311334 | 5501 | Show the limit of instructions to be recorded. |
53cc454a HZ |
5502 | |
5503 | @kindex set record stop-at-limit | |
a2311334 EZ |
5504 | @item set record stop-at-limit |
5505 | Control the behavior when the number of recorded instructions reaches | |
5506 | the limit. If ON (the default), @value{GDBN} will stop when the limit | |
5507 | is reached for the first time and ask you whether you want to stop the | |
5508 | inferior or continue running it and recording the execution log. If | |
5509 | you decide to continue recording, each new recorded instruction will | |
5510 | cause the oldest one to be deleted. | |
53cc454a | 5511 | |
a2311334 EZ |
5512 | If this option is OFF, @value{GDBN} will automatically delete the |
5513 | oldest record to make room for each new one, without asking. | |
53cc454a HZ |
5514 | |
5515 | @kindex show record stop-at-limit | |
5516 | @item show record stop-at-limit | |
a2311334 | 5517 | Show the current setting of @code{stop-at-limit}. |
53cc454a HZ |
5518 | |
5519 | @kindex info record insn-number | |
5520 | @item info record insn-number | |
5521 | Show the current number of recorded instructions. | |
5522 | ||
5523 | @kindex record delete | |
5524 | @kindex rec del | |
5525 | @item record delete | |
a2311334 | 5526 | When record target runs in replay mode (``in the past''), delete the |
53cc454a | 5527 | subsequent execution log and begin to record a new execution log starting |
a2311334 | 5528 | from the current address. This means you will abandon the previously |
53cc454a HZ |
5529 | recorded ``future'' and begin recording a new ``future''. |
5530 | @end table | |
5531 | ||
5532 | ||
6d2ebf8b | 5533 | @node Stack |
c906108c SS |
5534 | @chapter Examining the Stack |
5535 | ||
5536 | When your program has stopped, the first thing you need to know is where it | |
5537 | stopped and how it got there. | |
5538 | ||
5539 | @cindex call stack | |
5d161b24 DB |
5540 | Each time your program performs a function call, information about the call |
5541 | is generated. | |
5542 | That information includes the location of the call in your program, | |
5543 | the arguments of the call, | |
c906108c | 5544 | and the local variables of the function being called. |
5d161b24 | 5545 | The information is saved in a block of data called a @dfn{stack frame}. |
c906108c SS |
5546 | The stack frames are allocated in a region of memory called the @dfn{call |
5547 | stack}. | |
5548 | ||
5549 | When your program stops, the @value{GDBN} commands for examining the | |
5550 | stack allow you to see all of this information. | |
5551 | ||
5552 | @cindex selected frame | |
5553 | One of the stack frames is @dfn{selected} by @value{GDBN} and many | |
5554 | @value{GDBN} commands refer implicitly to the selected frame. In | |
5555 | particular, whenever you ask @value{GDBN} for the value of a variable in | |
5556 | your program, the value is found in the selected frame. There are | |
5557 | special @value{GDBN} commands to select whichever frame you are | |
79a6e687 | 5558 | interested in. @xref{Selection, ,Selecting a Frame}. |
c906108c SS |
5559 | |
5560 | When your program stops, @value{GDBN} automatically selects the | |
5d161b24 | 5561 | currently executing frame and describes it briefly, similar to the |
79a6e687 | 5562 | @code{frame} command (@pxref{Frame Info, ,Information about a Frame}). |
c906108c SS |
5563 | |
5564 | @menu | |
5565 | * Frames:: Stack frames | |
5566 | * Backtrace:: Backtraces | |
5567 | * Selection:: Selecting a frame | |
5568 | * Frame Info:: Information on a frame | |
c906108c SS |
5569 | |
5570 | @end menu | |
5571 | ||
6d2ebf8b | 5572 | @node Frames |
79a6e687 | 5573 | @section Stack Frames |
c906108c | 5574 | |
d4f3574e | 5575 | @cindex frame, definition |
c906108c SS |
5576 | @cindex stack frame |
5577 | The call stack is divided up into contiguous pieces called @dfn{stack | |
5578 | frames}, or @dfn{frames} for short; each frame is the data associated | |
5579 | with one call to one function. The frame contains the arguments given | |
5580 | to the function, the function's local variables, and the address at | |
5581 | which the function is executing. | |
5582 | ||
5583 | @cindex initial frame | |
5584 | @cindex outermost frame | |
5585 | @cindex innermost frame | |
5586 | When your program is started, the stack has only one frame, that of the | |
5587 | function @code{main}. This is called the @dfn{initial} frame or the | |
5588 | @dfn{outermost} frame. Each time a function is called, a new frame is | |
5589 | made. Each time a function returns, the frame for that function invocation | |
5590 | is eliminated. If a function is recursive, there can be many frames for | |
5591 | the same function. The frame for the function in which execution is | |
5592 | actually occurring is called the @dfn{innermost} frame. This is the most | |
5593 | recently created of all the stack frames that still exist. | |
5594 | ||
5595 | @cindex frame pointer | |
5596 | Inside your program, stack frames are identified by their addresses. A | |
5597 | stack frame consists of many bytes, each of which has its own address; each | |
5598 | kind of computer has a convention for choosing one byte whose | |
5599 | address serves as the address of the frame. Usually this address is kept | |
e09f16f9 EZ |
5600 | in a register called the @dfn{frame pointer register} |
5601 | (@pxref{Registers, $fp}) while execution is going on in that frame. | |
c906108c SS |
5602 | |
5603 | @cindex frame number | |
5604 | @value{GDBN} assigns numbers to all existing stack frames, starting with | |
5605 | zero for the innermost frame, one for the frame that called it, | |
5606 | and so on upward. These numbers do not really exist in your program; | |
5607 | they are assigned by @value{GDBN} to give you a way of designating stack | |
5608 | frames in @value{GDBN} commands. | |
5609 | ||
6d2ebf8b SS |
5610 | @c The -fomit-frame-pointer below perennially causes hbox overflow |
5611 | @c underflow problems. | |
c906108c SS |
5612 | @cindex frameless execution |
5613 | Some compilers provide a way to compile functions so that they operate | |
e22ea452 | 5614 | without stack frames. (For example, the @value{NGCC} option |
474c8240 | 5615 | @smallexample |
6d2ebf8b | 5616 | @samp{-fomit-frame-pointer} |
474c8240 | 5617 | @end smallexample |
6d2ebf8b | 5618 | generates functions without a frame.) |
c906108c SS |
5619 | This is occasionally done with heavily used library functions to save |
5620 | the frame setup time. @value{GDBN} has limited facilities for dealing | |
5621 | with these function invocations. If the innermost function invocation | |
5622 | has no stack frame, @value{GDBN} nevertheless regards it as though | |
5623 | it had a separate frame, which is numbered zero as usual, allowing | |
5624 | correct tracing of the function call chain. However, @value{GDBN} has | |
5625 | no provision for frameless functions elsewhere in the stack. | |
5626 | ||
5627 | @table @code | |
d4f3574e | 5628 | @kindex frame@r{, command} |
41afff9a | 5629 | @cindex current stack frame |
c906108c | 5630 | @item frame @var{args} |
5d161b24 | 5631 | The @code{frame} command allows you to move from one stack frame to another, |
c906108c | 5632 | and to print the stack frame you select. @var{args} may be either the |
5d161b24 DB |
5633 | address of the frame or the stack frame number. Without an argument, |
5634 | @code{frame} prints the current stack frame. | |
c906108c SS |
5635 | |
5636 | @kindex select-frame | |
41afff9a | 5637 | @cindex selecting frame silently |
c906108c SS |
5638 | @item select-frame |
5639 | The @code{select-frame} command allows you to move from one stack frame | |
5640 | to another without printing the frame. This is the silent version of | |
5641 | @code{frame}. | |
5642 | @end table | |
5643 | ||
6d2ebf8b | 5644 | @node Backtrace |
c906108c SS |
5645 | @section Backtraces |
5646 | ||
09d4efe1 EZ |
5647 | @cindex traceback |
5648 | @cindex call stack traces | |
c906108c SS |
5649 | A backtrace is a summary of how your program got where it is. It shows one |
5650 | line per frame, for many frames, starting with the currently executing | |
5651 | frame (frame zero), followed by its caller (frame one), and on up the | |
5652 | stack. | |
5653 | ||
5654 | @table @code | |
5655 | @kindex backtrace | |
41afff9a | 5656 | @kindex bt @r{(@code{backtrace})} |
c906108c SS |
5657 | @item backtrace |
5658 | @itemx bt | |
5659 | Print a backtrace of the entire stack: one line per frame for all | |
5660 | frames in the stack. | |
5661 | ||
5662 | You can stop the backtrace at any time by typing the system interrupt | |
c8aa23ab | 5663 | character, normally @kbd{Ctrl-c}. |
c906108c SS |
5664 | |
5665 | @item backtrace @var{n} | |
5666 | @itemx bt @var{n} | |
5667 | Similar, but print only the innermost @var{n} frames. | |
5668 | ||
5669 | @item backtrace -@var{n} | |
5670 | @itemx bt -@var{n} | |
5671 | Similar, but print only the outermost @var{n} frames. | |
0f061b69 NR |
5672 | |
5673 | @item backtrace full | |
0f061b69 | 5674 | @itemx bt full |
dd74f6ae NR |
5675 | @itemx bt full @var{n} |
5676 | @itemx bt full -@var{n} | |
e7109c7e | 5677 | Print the values of the local variables also. @var{n} specifies the |
286ba84d | 5678 | number of frames to print, as described above. |
c906108c SS |
5679 | @end table |
5680 | ||
5681 | @kindex where | |
5682 | @kindex info stack | |
c906108c SS |
5683 | The names @code{where} and @code{info stack} (abbreviated @code{info s}) |
5684 | are additional aliases for @code{backtrace}. | |
5685 | ||
839c27b7 EZ |
5686 | @cindex multiple threads, backtrace |
5687 | In a multi-threaded program, @value{GDBN} by default shows the | |
5688 | backtrace only for the current thread. To display the backtrace for | |
5689 | several or all of the threads, use the command @code{thread apply} | |
5690 | (@pxref{Threads, thread apply}). For example, if you type @kbd{thread | |
5691 | apply all backtrace}, @value{GDBN} will display the backtrace for all | |
5692 | the threads; this is handy when you debug a core dump of a | |
5693 | multi-threaded program. | |
5694 | ||
c906108c SS |
5695 | Each line in the backtrace shows the frame number and the function name. |
5696 | The program counter value is also shown---unless you use @code{set | |
5697 | print address off}. The backtrace also shows the source file name and | |
5698 | line number, as well as the arguments to the function. The program | |
5699 | counter value is omitted if it is at the beginning of the code for that | |
5700 | line number. | |
5701 | ||
5702 | Here is an example of a backtrace. It was made with the command | |
5703 | @samp{bt 3}, so it shows the innermost three frames. | |
5704 | ||
5705 | @smallexample | |
5706 | @group | |
5d161b24 | 5707 | #0 m4_traceon (obs=0x24eb0, argc=1, argv=0x2b8c8) |
c906108c | 5708 | at builtin.c:993 |
4f5376b2 | 5709 | #1 0x6e38 in expand_macro (sym=0x2b600, data=...) at macro.c:242 |
c906108c SS |
5710 | #2 0x6840 in expand_token (obs=0x0, t=177664, td=0xf7fffb08) |
5711 | at macro.c:71 | |
5712 | (More stack frames follow...) | |
5713 | @end group | |
5714 | @end smallexample | |
5715 | ||
5716 | @noindent | |
5717 | The display for frame zero does not begin with a program counter | |
5718 | value, indicating that your program has stopped at the beginning of the | |
5719 | code for line @code{993} of @code{builtin.c}. | |
5720 | ||
4f5376b2 JB |
5721 | @noindent |
5722 | The value of parameter @code{data} in frame 1 has been replaced by | |
5723 | @code{@dots{}}. By default, @value{GDBN} prints the value of a parameter | |
5724 | only if it is a scalar (integer, pointer, enumeration, etc). See command | |
5725 | @kbd{set print frame-arguments} in @ref{Print Settings} for more details | |
5726 | on how to configure the way function parameter values are printed. | |
5727 | ||
18999be5 EZ |
5728 | @cindex value optimized out, in backtrace |
5729 | @cindex function call arguments, optimized out | |
5730 | If your program was compiled with optimizations, some compilers will | |
5731 | optimize away arguments passed to functions if those arguments are | |
5732 | never used after the call. Such optimizations generate code that | |
5733 | passes arguments through registers, but doesn't store those arguments | |
5734 | in the stack frame. @value{GDBN} has no way of displaying such | |
5735 | arguments in stack frames other than the innermost one. Here's what | |
5736 | such a backtrace might look like: | |
5737 | ||
5738 | @smallexample | |
5739 | @group | |
5740 | #0 m4_traceon (obs=0x24eb0, argc=1, argv=0x2b8c8) | |
5741 | at builtin.c:993 | |
5742 | #1 0x6e38 in expand_macro (sym=<value optimized out>) at macro.c:242 | |
5743 | #2 0x6840 in expand_token (obs=0x0, t=<value optimized out>, td=0xf7fffb08) | |
5744 | at macro.c:71 | |
5745 | (More stack frames follow...) | |
5746 | @end group | |
5747 | @end smallexample | |
5748 | ||
5749 | @noindent | |
5750 | The values of arguments that were not saved in their stack frames are | |
5751 | shown as @samp{<value optimized out>}. | |
5752 | ||
5753 | If you need to display the values of such optimized-out arguments, | |
5754 | either deduce that from other variables whose values depend on the one | |
5755 | you are interested in, or recompile without optimizations. | |
5756 | ||
a8f24a35 EZ |
5757 | @cindex backtrace beyond @code{main} function |
5758 | @cindex program entry point | |
5759 | @cindex startup code, and backtrace | |
25d29d70 AC |
5760 | Most programs have a standard user entry point---a place where system |
5761 | libraries and startup code transition into user code. For C this is | |
d416eeec EZ |
5762 | @code{main}@footnote{ |
5763 | Note that embedded programs (the so-called ``free-standing'' | |
5764 | environment) are not required to have a @code{main} function as the | |
5765 | entry point. They could even have multiple entry points.}. | |
5766 | When @value{GDBN} finds the entry function in a backtrace | |
25d29d70 AC |
5767 | it will terminate the backtrace, to avoid tracing into highly |
5768 | system-specific (and generally uninteresting) code. | |
5769 | ||
5770 | If you need to examine the startup code, or limit the number of levels | |
5771 | in a backtrace, you can change this behavior: | |
95f90d25 DJ |
5772 | |
5773 | @table @code | |
25d29d70 AC |
5774 | @item set backtrace past-main |
5775 | @itemx set backtrace past-main on | |
4644b6e3 | 5776 | @kindex set backtrace |
25d29d70 AC |
5777 | Backtraces will continue past the user entry point. |
5778 | ||
5779 | @item set backtrace past-main off | |
95f90d25 DJ |
5780 | Backtraces will stop when they encounter the user entry point. This is the |
5781 | default. | |
5782 | ||
25d29d70 | 5783 | @item show backtrace past-main |
4644b6e3 | 5784 | @kindex show backtrace |
25d29d70 AC |
5785 | Display the current user entry point backtrace policy. |
5786 | ||
2315ffec RC |
5787 | @item set backtrace past-entry |
5788 | @itemx set backtrace past-entry on | |
a8f24a35 | 5789 | Backtraces will continue past the internal entry point of an application. |
2315ffec RC |
5790 | This entry point is encoded by the linker when the application is built, |
5791 | and is likely before the user entry point @code{main} (or equivalent) is called. | |
5792 | ||
5793 | @item set backtrace past-entry off | |
d3e8051b | 5794 | Backtraces will stop when they encounter the internal entry point of an |
2315ffec RC |
5795 | application. This is the default. |
5796 | ||
5797 | @item show backtrace past-entry | |
5798 | Display the current internal entry point backtrace policy. | |
5799 | ||
25d29d70 AC |
5800 | @item set backtrace limit @var{n} |
5801 | @itemx set backtrace limit 0 | |
5802 | @cindex backtrace limit | |
5803 | Limit the backtrace to @var{n} levels. A value of zero means | |
5804 | unlimited. | |
95f90d25 | 5805 | |
25d29d70 AC |
5806 | @item show backtrace limit |
5807 | Display the current limit on backtrace levels. | |
95f90d25 DJ |
5808 | @end table |
5809 | ||
6d2ebf8b | 5810 | @node Selection |
79a6e687 | 5811 | @section Selecting a Frame |
c906108c SS |
5812 | |
5813 | Most commands for examining the stack and other data in your program work on | |
5814 | whichever stack frame is selected at the moment. Here are the commands for | |
5815 | selecting a stack frame; all of them finish by printing a brief description | |
5816 | of the stack frame just selected. | |
5817 | ||
5818 | @table @code | |
d4f3574e | 5819 | @kindex frame@r{, selecting} |
41afff9a | 5820 | @kindex f @r{(@code{frame})} |
c906108c SS |
5821 | @item frame @var{n} |
5822 | @itemx f @var{n} | |
5823 | Select frame number @var{n}. Recall that frame zero is the innermost | |
5824 | (currently executing) frame, frame one is the frame that called the | |
5825 | innermost one, and so on. The highest-numbered frame is the one for | |
5826 | @code{main}. | |
5827 | ||
5828 | @item frame @var{addr} | |
5829 | @itemx f @var{addr} | |
5830 | Select the frame at address @var{addr}. This is useful mainly if the | |
5831 | chaining of stack frames has been damaged by a bug, making it | |
5832 | impossible for @value{GDBN} to assign numbers properly to all frames. In | |
5833 | addition, this can be useful when your program has multiple stacks and | |
5834 | switches between them. | |
5835 | ||
c906108c SS |
5836 | On the SPARC architecture, @code{frame} needs two addresses to |
5837 | select an arbitrary frame: a frame pointer and a stack pointer. | |
5838 | ||
5839 | On the MIPS and Alpha architecture, it needs two addresses: a stack | |
5840 | pointer and a program counter. | |
5841 | ||
5842 | On the 29k architecture, it needs three addresses: a register stack | |
5843 | pointer, a program counter, and a memory stack pointer. | |
c906108c SS |
5844 | |
5845 | @kindex up | |
5846 | @item up @var{n} | |
5847 | Move @var{n} frames up the stack. For positive numbers @var{n}, this | |
5848 | advances toward the outermost frame, to higher frame numbers, to frames | |
5849 | that have existed longer. @var{n} defaults to one. | |
5850 | ||
5851 | @kindex down | |
41afff9a | 5852 | @kindex do @r{(@code{down})} |
c906108c SS |
5853 | @item down @var{n} |
5854 | Move @var{n} frames down the stack. For positive numbers @var{n}, this | |
5855 | advances toward the innermost frame, to lower frame numbers, to frames | |
5856 | that were created more recently. @var{n} defaults to one. You may | |
5857 | abbreviate @code{down} as @code{do}. | |
5858 | @end table | |
5859 | ||
5860 | All of these commands end by printing two lines of output describing the | |
5861 | frame. The first line shows the frame number, the function name, the | |
5862 | arguments, and the source file and line number of execution in that | |
5d161b24 | 5863 | frame. The second line shows the text of that source line. |
c906108c SS |
5864 | |
5865 | @need 1000 | |
5866 | For example: | |
5867 | ||
5868 | @smallexample | |
5869 | @group | |
5870 | (@value{GDBP}) up | |
5871 | #1 0x22f0 in main (argc=1, argv=0xf7fffbf4, env=0xf7fffbfc) | |
5872 | at env.c:10 | |
5873 | 10 read_input_file (argv[i]); | |
5874 | @end group | |
5875 | @end smallexample | |
5876 | ||
5877 | After such a printout, the @code{list} command with no arguments | |
5878 | prints ten lines centered on the point of execution in the frame. | |
87885426 FN |
5879 | You can also edit the program at the point of execution with your favorite |
5880 | editing program by typing @code{edit}. | |
79a6e687 | 5881 | @xref{List, ,Printing Source Lines}, |
87885426 | 5882 | for details. |
c906108c SS |
5883 | |
5884 | @table @code | |
5885 | @kindex down-silently | |
5886 | @kindex up-silently | |
5887 | @item up-silently @var{n} | |
5888 | @itemx down-silently @var{n} | |
5889 | These two commands are variants of @code{up} and @code{down}, | |
5890 | respectively; they differ in that they do their work silently, without | |
5891 | causing display of the new frame. They are intended primarily for use | |
5892 | in @value{GDBN} command scripts, where the output might be unnecessary and | |
5893 | distracting. | |
5894 | @end table | |
5895 | ||
6d2ebf8b | 5896 | @node Frame Info |
79a6e687 | 5897 | @section Information About a Frame |
c906108c SS |
5898 | |
5899 | There are several other commands to print information about the selected | |
5900 | stack frame. | |
5901 | ||
5902 | @table @code | |
5903 | @item frame | |
5904 | @itemx f | |
5905 | When used without any argument, this command does not change which | |
5906 | frame is selected, but prints a brief description of the currently | |
5907 | selected stack frame. It can be abbreviated @code{f}. With an | |
5908 | argument, this command is used to select a stack frame. | |
79a6e687 | 5909 | @xref{Selection, ,Selecting a Frame}. |
c906108c SS |
5910 | |
5911 | @kindex info frame | |
41afff9a | 5912 | @kindex info f @r{(@code{info frame})} |
c906108c SS |
5913 | @item info frame |
5914 | @itemx info f | |
5915 | This command prints a verbose description of the selected stack frame, | |
5916 | including: | |
5917 | ||
5918 | @itemize @bullet | |
5d161b24 DB |
5919 | @item |
5920 | the address of the frame | |
c906108c SS |
5921 | @item |
5922 | the address of the next frame down (called by this frame) | |
5923 | @item | |
5924 | the address of the next frame up (caller of this frame) | |
5925 | @item | |
5926 | the language in which the source code corresponding to this frame is written | |
5927 | @item | |
5928 | the address of the frame's arguments | |
5929 | @item | |
d4f3574e SS |
5930 | the address of the frame's local variables |
5931 | @item | |
c906108c SS |
5932 | the program counter saved in it (the address of execution in the caller frame) |
5933 | @item | |
5934 | which registers were saved in the frame | |
5935 | @end itemize | |
5936 | ||
5937 | @noindent The verbose description is useful when | |
5938 | something has gone wrong that has made the stack format fail to fit | |
5939 | the usual conventions. | |
5940 | ||
5941 | @item info frame @var{addr} | |
5942 | @itemx info f @var{addr} | |
5943 | Print a verbose description of the frame at address @var{addr}, without | |
5944 | selecting that frame. The selected frame remains unchanged by this | |
5945 | command. This requires the same kind of address (more than one for some | |
5946 | architectures) that you specify in the @code{frame} command. | |
79a6e687 | 5947 | @xref{Selection, ,Selecting a Frame}. |
c906108c SS |
5948 | |
5949 | @kindex info args | |
5950 | @item info args | |
5951 | Print the arguments of the selected frame, each on a separate line. | |
5952 | ||
5953 | @item info locals | |
5954 | @kindex info locals | |
5955 | Print the local variables of the selected frame, each on a separate | |
5956 | line. These are all variables (declared either static or automatic) | |
5957 | accessible at the point of execution of the selected frame. | |
5958 | ||
c906108c | 5959 | @kindex info catch |
d4f3574e SS |
5960 | @cindex catch exceptions, list active handlers |
5961 | @cindex exception handlers, how to list | |
c906108c SS |
5962 | @item info catch |
5963 | Print a list of all the exception handlers that are active in the | |
5964 | current stack frame at the current point of execution. To see other | |
5965 | exception handlers, visit the associated frame (using the @code{up}, | |
5966 | @code{down}, or @code{frame} commands); then type @code{info catch}. | |
79a6e687 | 5967 | @xref{Set Catchpoints, , Setting Catchpoints}. |
53a5351d | 5968 | |
c906108c SS |
5969 | @end table |
5970 | ||
c906108c | 5971 | |
6d2ebf8b | 5972 | @node Source |
c906108c SS |
5973 | @chapter Examining Source Files |
5974 | ||
5975 | @value{GDBN} can print parts of your program's source, since the debugging | |
5976 | information recorded in the program tells @value{GDBN} what source files were | |
5977 | used to build it. When your program stops, @value{GDBN} spontaneously prints | |
5978 | the line where it stopped. Likewise, when you select a stack frame | |
79a6e687 | 5979 | (@pxref{Selection, ,Selecting a Frame}), @value{GDBN} prints the line where |
c906108c SS |
5980 | execution in that frame has stopped. You can print other portions of |
5981 | source files by explicit command. | |
5982 | ||
7a292a7a | 5983 | If you use @value{GDBN} through its @sc{gnu} Emacs interface, you may |
d4f3574e | 5984 | prefer to use Emacs facilities to view source; see @ref{Emacs, ,Using |
7a292a7a | 5985 | @value{GDBN} under @sc{gnu} Emacs}. |
c906108c SS |
5986 | |
5987 | @menu | |
5988 | * List:: Printing source lines | |
2a25a5ba | 5989 | * Specify Location:: How to specify code locations |
87885426 | 5990 | * Edit:: Editing source files |
c906108c | 5991 | * Search:: Searching source files |
c906108c SS |
5992 | * Source Path:: Specifying source directories |
5993 | * Machine Code:: Source and machine code | |
5994 | @end menu | |
5995 | ||
6d2ebf8b | 5996 | @node List |
79a6e687 | 5997 | @section Printing Source Lines |
c906108c SS |
5998 | |
5999 | @kindex list | |
41afff9a | 6000 | @kindex l @r{(@code{list})} |
c906108c | 6001 | To print lines from a source file, use the @code{list} command |
5d161b24 | 6002 | (abbreviated @code{l}). By default, ten lines are printed. |
2a25a5ba EZ |
6003 | There are several ways to specify what part of the file you want to |
6004 | print; see @ref{Specify Location}, for the full list. | |
c906108c SS |
6005 | |
6006 | Here are the forms of the @code{list} command most commonly used: | |
6007 | ||
6008 | @table @code | |
6009 | @item list @var{linenum} | |
6010 | Print lines centered around line number @var{linenum} in the | |
6011 | current source file. | |
6012 | ||
6013 | @item list @var{function} | |
6014 | Print lines centered around the beginning of function | |
6015 | @var{function}. | |
6016 | ||
6017 | @item list | |
6018 | Print more lines. If the last lines printed were printed with a | |
6019 | @code{list} command, this prints lines following the last lines | |
6020 | printed; however, if the last line printed was a solitary line printed | |
6021 | as part of displaying a stack frame (@pxref{Stack, ,Examining the | |
6022 | Stack}), this prints lines centered around that line. | |
6023 | ||
6024 | @item list - | |
6025 | Print lines just before the lines last printed. | |
6026 | @end table | |
6027 | ||
9c16f35a | 6028 | @cindex @code{list}, how many lines to display |
c906108c SS |
6029 | By default, @value{GDBN} prints ten source lines with any of these forms of |
6030 | the @code{list} command. You can change this using @code{set listsize}: | |
6031 | ||
6032 | @table @code | |
6033 | @kindex set listsize | |
6034 | @item set listsize @var{count} | |
6035 | Make the @code{list} command display @var{count} source lines (unless | |
6036 | the @code{list} argument explicitly specifies some other number). | |
6037 | ||
6038 | @kindex show listsize | |
6039 | @item show listsize | |
6040 | Display the number of lines that @code{list} prints. | |
6041 | @end table | |
6042 | ||
6043 | Repeating a @code{list} command with @key{RET} discards the argument, | |
6044 | so it is equivalent to typing just @code{list}. This is more useful | |
6045 | than listing the same lines again. An exception is made for an | |
6046 | argument of @samp{-}; that argument is preserved in repetition so that | |
6047 | each repetition moves up in the source file. | |
6048 | ||
c906108c SS |
6049 | In general, the @code{list} command expects you to supply zero, one or two |
6050 | @dfn{linespecs}. Linespecs specify source lines; there are several ways | |
2a25a5ba EZ |
6051 | of writing them (@pxref{Specify Location}), but the effect is always |
6052 | to specify some source line. | |
6053 | ||
c906108c SS |
6054 | Here is a complete description of the possible arguments for @code{list}: |
6055 | ||
6056 | @table @code | |
6057 | @item list @var{linespec} | |
6058 | Print lines centered around the line specified by @var{linespec}. | |
6059 | ||
6060 | @item list @var{first},@var{last} | |
6061 | Print lines from @var{first} to @var{last}. Both arguments are | |
2a25a5ba EZ |
6062 | linespecs. When a @code{list} command has two linespecs, and the |
6063 | source file of the second linespec is omitted, this refers to | |
6064 | the same source file as the first linespec. | |
c906108c SS |
6065 | |
6066 | @item list ,@var{last} | |
6067 | Print lines ending with @var{last}. | |
6068 | ||
6069 | @item list @var{first}, | |
6070 | Print lines starting with @var{first}. | |
6071 | ||
6072 | @item list + | |
6073 | Print lines just after the lines last printed. | |
6074 | ||
6075 | @item list - | |
6076 | Print lines just before the lines last printed. | |
6077 | ||
6078 | @item list | |
6079 | As described in the preceding table. | |
6080 | @end table | |
6081 | ||
2a25a5ba EZ |
6082 | @node Specify Location |
6083 | @section Specifying a Location | |
6084 | @cindex specifying location | |
6085 | @cindex linespec | |
c906108c | 6086 | |
2a25a5ba EZ |
6087 | Several @value{GDBN} commands accept arguments that specify a location |
6088 | of your program's code. Since @value{GDBN} is a source-level | |
6089 | debugger, a location usually specifies some line in the source code; | |
6090 | for that reason, locations are also known as @dfn{linespecs}. | |
c906108c | 6091 | |
2a25a5ba EZ |
6092 | Here are all the different ways of specifying a code location that |
6093 | @value{GDBN} understands: | |
c906108c | 6094 | |
2a25a5ba EZ |
6095 | @table @code |
6096 | @item @var{linenum} | |
6097 | Specifies the line number @var{linenum} of the current source file. | |
c906108c | 6098 | |
2a25a5ba EZ |
6099 | @item -@var{offset} |
6100 | @itemx +@var{offset} | |
6101 | Specifies the line @var{offset} lines before or after the @dfn{current | |
6102 | line}. For the @code{list} command, the current line is the last one | |
6103 | printed; for the breakpoint commands, this is the line at which | |
6104 | execution stopped in the currently selected @dfn{stack frame} | |
6105 | (@pxref{Frames, ,Frames}, for a description of stack frames.) When | |
6106 | used as the second of the two linespecs in a @code{list} command, | |
6107 | this specifies the line @var{offset} lines up or down from the first | |
6108 | linespec. | |
6109 | ||
6110 | @item @var{filename}:@var{linenum} | |
6111 | Specifies the line @var{linenum} in the source file @var{filename}. | |
c906108c SS |
6112 | |
6113 | @item @var{function} | |
6114 | Specifies the line that begins the body of the function @var{function}. | |
2a25a5ba | 6115 | For example, in C, this is the line with the open brace. |
c906108c SS |
6116 | |
6117 | @item @var{filename}:@var{function} | |
2a25a5ba EZ |
6118 | Specifies the line that begins the body of the function @var{function} |
6119 | in the file @var{filename}. You only need the file name with a | |
6120 | function name to avoid ambiguity when there are identically named | |
6121 | functions in different source files. | |
c906108c SS |
6122 | |
6123 | @item *@var{address} | |
2a25a5ba EZ |
6124 | Specifies the program address @var{address}. For line-oriented |
6125 | commands, such as @code{list} and @code{edit}, this specifies a source | |
6126 | line that contains @var{address}. For @code{break} and other | |
6127 | breakpoint oriented commands, this can be used to set breakpoints in | |
6128 | parts of your program which do not have debugging information or | |
6129 | source files. | |
6130 | ||
6131 | Here @var{address} may be any expression valid in the current working | |
6132 | language (@pxref{Languages, working language}) that specifies a code | |
5fa54e5d EZ |
6133 | address. In addition, as a convenience, @value{GDBN} extends the |
6134 | semantics of expressions used in locations to cover the situations | |
6135 | that frequently happen during debugging. Here are the various forms | |
6136 | of @var{address}: | |
2a25a5ba EZ |
6137 | |
6138 | @table @code | |
6139 | @item @var{expression} | |
6140 | Any expression valid in the current working language. | |
6141 | ||
6142 | @item @var{funcaddr} | |
6143 | An address of a function or procedure derived from its name. In C, | |
6144 | C@t{++}, Java, Objective-C, Fortran, minimal, and assembly, this is | |
6145 | simply the function's name @var{function} (and actually a special case | |
6146 | of a valid expression). In Pascal and Modula-2, this is | |
6147 | @code{&@var{function}}. In Ada, this is @code{@var{function}'Address} | |
6148 | (although the Pascal form also works). | |
6149 | ||
6150 | This form specifies the address of the function's first instruction, | |
6151 | before the stack frame and arguments have been set up. | |
6152 | ||
6153 | @item '@var{filename}'::@var{funcaddr} | |
6154 | Like @var{funcaddr} above, but also specifies the name of the source | |
6155 | file explicitly. This is useful if the name of the function does not | |
6156 | specify the function unambiguously, e.g., if there are several | |
6157 | functions with identical names in different source files. | |
c906108c SS |
6158 | @end table |
6159 | ||
2a25a5ba EZ |
6160 | @end table |
6161 | ||
6162 | ||
87885426 | 6163 | @node Edit |
79a6e687 | 6164 | @section Editing Source Files |
87885426 FN |
6165 | @cindex editing source files |
6166 | ||
6167 | @kindex edit | |
6168 | @kindex e @r{(@code{edit})} | |
6169 | To edit the lines in a source file, use the @code{edit} command. | |
6170 | The editing program of your choice | |
6171 | is invoked with the current line set to | |
6172 | the active line in the program. | |
6173 | Alternatively, there are several ways to specify what part of the file you | |
2a25a5ba | 6174 | want to print if you want to see other parts of the program: |
87885426 FN |
6175 | |
6176 | @table @code | |
2a25a5ba EZ |
6177 | @item edit @var{location} |
6178 | Edit the source file specified by @code{location}. Editing starts at | |
6179 | that @var{location}, e.g., at the specified source line of the | |
6180 | specified file. @xref{Specify Location}, for all the possible forms | |
6181 | of the @var{location} argument; here are the forms of the @code{edit} | |
6182 | command most commonly used: | |
87885426 | 6183 | |
2a25a5ba | 6184 | @table @code |
87885426 FN |
6185 | @item edit @var{number} |
6186 | Edit the current source file with @var{number} as the active line number. | |
6187 | ||
6188 | @item edit @var{function} | |
6189 | Edit the file containing @var{function} at the beginning of its definition. | |
2a25a5ba | 6190 | @end table |
87885426 | 6191 | |
87885426 FN |
6192 | @end table |
6193 | ||
79a6e687 | 6194 | @subsection Choosing your Editor |
87885426 FN |
6195 | You can customize @value{GDBN} to use any editor you want |
6196 | @footnote{ | |
6197 | The only restriction is that your editor (say @code{ex}), recognizes the | |
6198 | following command-line syntax: | |
10998722 | 6199 | @smallexample |
87885426 | 6200 | ex +@var{number} file |
10998722 | 6201 | @end smallexample |
15387254 EZ |
6202 | The optional numeric value +@var{number} specifies the number of the line in |
6203 | the file where to start editing.}. | |
6204 | By default, it is @file{@value{EDITOR}}, but you can change this | |
10998722 AC |
6205 | by setting the environment variable @code{EDITOR} before using |
6206 | @value{GDBN}. For example, to configure @value{GDBN} to use the | |
6207 | @code{vi} editor, you could use these commands with the @code{sh} shell: | |
6208 | @smallexample | |
87885426 FN |
6209 | EDITOR=/usr/bin/vi |
6210 | export EDITOR | |
15387254 | 6211 | gdb @dots{} |
10998722 | 6212 | @end smallexample |
87885426 | 6213 | or in the @code{csh} shell, |
10998722 | 6214 | @smallexample |
87885426 | 6215 | setenv EDITOR /usr/bin/vi |
15387254 | 6216 | gdb @dots{} |
10998722 | 6217 | @end smallexample |
87885426 | 6218 | |
6d2ebf8b | 6219 | @node Search |
79a6e687 | 6220 | @section Searching Source Files |
15387254 | 6221 | @cindex searching source files |
c906108c SS |
6222 | |
6223 | There are two commands for searching through the current source file for a | |
6224 | regular expression. | |
6225 | ||
6226 | @table @code | |
6227 | @kindex search | |
6228 | @kindex forward-search | |
6229 | @item forward-search @var{regexp} | |
6230 | @itemx search @var{regexp} | |
6231 | The command @samp{forward-search @var{regexp}} checks each line, | |
6232 | starting with the one following the last line listed, for a match for | |
5d161b24 | 6233 | @var{regexp}. It lists the line that is found. You can use the |
c906108c SS |
6234 | synonym @samp{search @var{regexp}} or abbreviate the command name as |
6235 | @code{fo}. | |
6236 | ||
09d4efe1 | 6237 | @kindex reverse-search |
c906108c SS |
6238 | @item reverse-search @var{regexp} |
6239 | The command @samp{reverse-search @var{regexp}} checks each line, starting | |
6240 | with the one before the last line listed and going backward, for a match | |
6241 | for @var{regexp}. It lists the line that is found. You can abbreviate | |
6242 | this command as @code{rev}. | |
6243 | @end table | |
c906108c | 6244 | |
6d2ebf8b | 6245 | @node Source Path |
79a6e687 | 6246 | @section Specifying Source Directories |
c906108c SS |
6247 | |
6248 | @cindex source path | |
6249 | @cindex directories for source files | |
6250 | Executable programs sometimes do not record the directories of the source | |
6251 | files from which they were compiled, just the names. Even when they do, | |
6252 | the directories could be moved between the compilation and your debugging | |
6253 | session. @value{GDBN} has a list of directories to search for source files; | |
6254 | this is called the @dfn{source path}. Each time @value{GDBN} wants a source file, | |
6255 | it tries all the directories in the list, in the order they are present | |
0b66e38c EZ |
6256 | in the list, until it finds a file with the desired name. |
6257 | ||
6258 | For example, suppose an executable references the file | |
6259 | @file{/usr/src/foo-1.0/lib/foo.c}, and our source path is | |
6260 | @file{/mnt/cross}. The file is first looked up literally; if this | |
6261 | fails, @file{/mnt/cross/usr/src/foo-1.0/lib/foo.c} is tried; if this | |
6262 | fails, @file{/mnt/cross/foo.c} is opened; if this fails, an error | |
6263 | message is printed. @value{GDBN} does not look up the parts of the | |
6264 | source file name, such as @file{/mnt/cross/src/foo-1.0/lib/foo.c}. | |
6265 | Likewise, the subdirectories of the source path are not searched: if | |
6266 | the source path is @file{/mnt/cross}, and the binary refers to | |
6267 | @file{foo.c}, @value{GDBN} would not find it under | |
6268 | @file{/mnt/cross/usr/src/foo-1.0/lib}. | |
6269 | ||
6270 | Plain file names, relative file names with leading directories, file | |
6271 | names containing dots, etc.@: are all treated as described above; for | |
6272 | instance, if the source path is @file{/mnt/cross}, and the source file | |
6273 | is recorded as @file{../lib/foo.c}, @value{GDBN} would first try | |
6274 | @file{../lib/foo.c}, then @file{/mnt/cross/../lib/foo.c}, and after | |
6275 | that---@file{/mnt/cross/foo.c}. | |
6276 | ||
6277 | Note that the executable search path is @emph{not} used to locate the | |
cd852561 | 6278 | source files. |
c906108c SS |
6279 | |
6280 | Whenever you reset or rearrange the source path, @value{GDBN} clears out | |
6281 | any information it has cached about where source files are found and where | |
6282 | each line is in the file. | |
6283 | ||
6284 | @kindex directory | |
6285 | @kindex dir | |
d4f3574e SS |
6286 | When you start @value{GDBN}, its source path includes only @samp{cdir} |
6287 | and @samp{cwd}, in that order. | |
c906108c SS |
6288 | To add other directories, use the @code{directory} command. |
6289 | ||
4b505b12 AS |
6290 | The search path is used to find both program source files and @value{GDBN} |
6291 | script files (read using the @samp{-command} option and @samp{source} command). | |
6292 | ||
30daae6c JB |
6293 | In addition to the source path, @value{GDBN} provides a set of commands |
6294 | that manage a list of source path substitution rules. A @dfn{substitution | |
6295 | rule} specifies how to rewrite source directories stored in the program's | |
6296 | debug information in case the sources were moved to a different | |
6297 | directory between compilation and debugging. A rule is made of | |
6298 | two strings, the first specifying what needs to be rewritten in | |
6299 | the path, and the second specifying how it should be rewritten. | |
6300 | In @ref{set substitute-path}, we name these two parts @var{from} and | |
6301 | @var{to} respectively. @value{GDBN} does a simple string replacement | |
6302 | of @var{from} with @var{to} at the start of the directory part of the | |
6303 | source file name, and uses that result instead of the original file | |
6304 | name to look up the sources. | |
6305 | ||
6306 | Using the previous example, suppose the @file{foo-1.0} tree has been | |
6307 | moved from @file{/usr/src} to @file{/mnt/cross}, then you can tell | |
3f94c067 | 6308 | @value{GDBN} to replace @file{/usr/src} in all source path names with |
30daae6c JB |
6309 | @file{/mnt/cross}. The first lookup will then be |
6310 | @file{/mnt/cross/foo-1.0/lib/foo.c} in place of the original location | |
6311 | of @file{/usr/src/foo-1.0/lib/foo.c}. To define a source path | |
6312 | substitution rule, use the @code{set substitute-path} command | |
6313 | (@pxref{set substitute-path}). | |
6314 | ||
6315 | To avoid unexpected substitution results, a rule is applied only if the | |
6316 | @var{from} part of the directory name ends at a directory separator. | |
6317 | For instance, a rule substituting @file{/usr/source} into | |
6318 | @file{/mnt/cross} will be applied to @file{/usr/source/foo-1.0} but | |
6319 | not to @file{/usr/sourceware/foo-2.0}. And because the substitution | |
d3e8051b | 6320 | is applied only at the beginning of the directory name, this rule will |
30daae6c JB |
6321 | not be applied to @file{/root/usr/source/baz.c} either. |
6322 | ||
6323 | In many cases, you can achieve the same result using the @code{directory} | |
6324 | command. However, @code{set substitute-path} can be more efficient in | |
6325 | the case where the sources are organized in a complex tree with multiple | |
6326 | subdirectories. With the @code{directory} command, you need to add each | |
6327 | subdirectory of your project. If you moved the entire tree while | |
6328 | preserving its internal organization, then @code{set substitute-path} | |
6329 | allows you to direct the debugger to all the sources with one single | |
6330 | command. | |
6331 | ||
6332 | @code{set substitute-path} is also more than just a shortcut command. | |
6333 | The source path is only used if the file at the original location no | |
6334 | longer exists. On the other hand, @code{set substitute-path} modifies | |
6335 | the debugger behavior to look at the rewritten location instead. So, if | |
6336 | for any reason a source file that is not relevant to your executable is | |
6337 | located at the original location, a substitution rule is the only | |
3f94c067 | 6338 | method available to point @value{GDBN} at the new location. |
30daae6c | 6339 | |
29b0e8a2 JM |
6340 | @cindex @samp{--with-relocated-sources} |
6341 | @cindex default source path substitution | |
6342 | You can configure a default source path substitution rule by | |
6343 | configuring @value{GDBN} with the | |
6344 | @samp{--with-relocated-sources=@var{dir}} option. The @var{dir} | |
6345 | should be the name of a directory under @value{GDBN}'s configured | |
6346 | prefix (set with @samp{--prefix} or @samp{--exec-prefix}), and | |
6347 | directory names in debug information under @var{dir} will be adjusted | |
6348 | automatically if the installed @value{GDBN} is moved to a new | |
6349 | location. This is useful if @value{GDBN}, libraries or executables | |
6350 | with debug information and corresponding source code are being moved | |
6351 | together. | |
6352 | ||
c906108c SS |
6353 | @table @code |
6354 | @item directory @var{dirname} @dots{} | |
6355 | @item dir @var{dirname} @dots{} | |
6356 | Add directory @var{dirname} to the front of the source path. Several | |
d4f3574e SS |
6357 | directory names may be given to this command, separated by @samp{:} |
6358 | (@samp{;} on MS-DOS and MS-Windows, where @samp{:} usually appears as | |
6359 | part of absolute file names) or | |
c906108c SS |
6360 | whitespace. You may specify a directory that is already in the source |
6361 | path; this moves it forward, so @value{GDBN} searches it sooner. | |
6362 | ||
6363 | @kindex cdir | |
6364 | @kindex cwd | |
41afff9a | 6365 | @vindex $cdir@r{, convenience variable} |
d3e8051b | 6366 | @vindex $cwd@r{, convenience variable} |
c906108c SS |
6367 | @cindex compilation directory |
6368 | @cindex current directory | |
6369 | @cindex working directory | |
6370 | @cindex directory, current | |
6371 | @cindex directory, compilation | |
6372 | You can use the string @samp{$cdir} to refer to the compilation | |
6373 | directory (if one is recorded), and @samp{$cwd} to refer to the current | |
6374 | working directory. @samp{$cwd} is not the same as @samp{.}---the former | |
6375 | tracks the current working directory as it changes during your @value{GDBN} | |
6376 | session, while the latter is immediately expanded to the current | |
6377 | directory at the time you add an entry to the source path. | |
6378 | ||
6379 | @item directory | |
cd852561 | 6380 | Reset the source path to its default value (@samp{$cdir:$cwd} on Unix systems). This requires confirmation. |
c906108c SS |
6381 | |
6382 | @c RET-repeat for @code{directory} is explicitly disabled, but since | |
6383 | @c repeating it would be a no-op we do not say that. (thanks to RMS) | |
6384 | ||
6385 | @item show directories | |
6386 | @kindex show directories | |
6387 | Print the source path: show which directories it contains. | |
30daae6c JB |
6388 | |
6389 | @anchor{set substitute-path} | |
6390 | @item set substitute-path @var{from} @var{to} | |
6391 | @kindex set substitute-path | |
6392 | Define a source path substitution rule, and add it at the end of the | |
6393 | current list of existing substitution rules. If a rule with the same | |
6394 | @var{from} was already defined, then the old rule is also deleted. | |
6395 | ||
6396 | For example, if the file @file{/foo/bar/baz.c} was moved to | |
6397 | @file{/mnt/cross/baz.c}, then the command | |
6398 | ||
6399 | @smallexample | |
6400 | (@value{GDBP}) set substitute-path /usr/src /mnt/cross | |
6401 | @end smallexample | |
6402 | ||
6403 | @noindent | |
6404 | will tell @value{GDBN} to replace @samp{/usr/src} with | |
6405 | @samp{/mnt/cross}, which will allow @value{GDBN} to find the file | |
6406 | @file{baz.c} even though it was moved. | |
6407 | ||
6408 | In the case when more than one substitution rule have been defined, | |
6409 | the rules are evaluated one by one in the order where they have been | |
6410 | defined. The first one matching, if any, is selected to perform | |
6411 | the substitution. | |
6412 | ||
6413 | For instance, if we had entered the following commands: | |
6414 | ||
6415 | @smallexample | |
6416 | (@value{GDBP}) set substitute-path /usr/src/include /mnt/include | |
6417 | (@value{GDBP}) set substitute-path /usr/src /mnt/src | |
6418 | @end smallexample | |
6419 | ||
6420 | @noindent | |
6421 | @value{GDBN} would then rewrite @file{/usr/src/include/defs.h} into | |
6422 | @file{/mnt/include/defs.h} by using the first rule. However, it would | |
6423 | use the second rule to rewrite @file{/usr/src/lib/foo.c} into | |
6424 | @file{/mnt/src/lib/foo.c}. | |
6425 | ||
6426 | ||
6427 | @item unset substitute-path [path] | |
6428 | @kindex unset substitute-path | |
6429 | If a path is specified, search the current list of substitution rules | |
6430 | for a rule that would rewrite that path. Delete that rule if found. | |
6431 | A warning is emitted by the debugger if no rule could be found. | |
6432 | ||
6433 | If no path is specified, then all substitution rules are deleted. | |
6434 | ||
6435 | @item show substitute-path [path] | |
6436 | @kindex show substitute-path | |
6437 | If a path is specified, then print the source path substitution rule | |
6438 | which would rewrite that path, if any. | |
6439 | ||
6440 | If no path is specified, then print all existing source path substitution | |
6441 | rules. | |
6442 | ||
c906108c SS |
6443 | @end table |
6444 | ||
6445 | If your source path is cluttered with directories that are no longer of | |
6446 | interest, @value{GDBN} may sometimes cause confusion by finding the wrong | |
6447 | versions of source. You can correct the situation as follows: | |
6448 | ||
6449 | @enumerate | |
6450 | @item | |
cd852561 | 6451 | Use @code{directory} with no argument to reset the source path to its default value. |
c906108c SS |
6452 | |
6453 | @item | |
6454 | Use @code{directory} with suitable arguments to reinstall the | |
6455 | directories you want in the source path. You can add all the | |
6456 | directories in one command. | |
6457 | @end enumerate | |
6458 | ||
6d2ebf8b | 6459 | @node Machine Code |
79a6e687 | 6460 | @section Source and Machine Code |
15387254 | 6461 | @cindex source line and its code address |
c906108c SS |
6462 | |
6463 | You can use the command @code{info line} to map source lines to program | |
6464 | addresses (and vice versa), and the command @code{disassemble} to display | |
91440f57 HZ |
6465 | a range of addresses as machine instructions. You can use the command |
6466 | @code{set disassemble-next-line} to set whether to disassemble next | |
6467 | source line when execution stops. When run under @sc{gnu} Emacs | |
d4f3574e | 6468 | mode, the @code{info line} command causes the arrow to point to the |
5d161b24 | 6469 | line specified. Also, @code{info line} prints addresses in symbolic form as |
c906108c SS |
6470 | well as hex. |
6471 | ||
6472 | @table @code | |
6473 | @kindex info line | |
6474 | @item info line @var{linespec} | |
6475 | Print the starting and ending addresses of the compiled code for | |
6476 | source line @var{linespec}. You can specify source lines in any of | |
2a25a5ba | 6477 | the ways documented in @ref{Specify Location}. |
c906108c SS |
6478 | @end table |
6479 | ||
6480 | For example, we can use @code{info line} to discover the location of | |
6481 | the object code for the first line of function | |
6482 | @code{m4_changequote}: | |
6483 | ||
d4f3574e SS |
6484 | @c FIXME: I think this example should also show the addresses in |
6485 | @c symbolic form, as they usually would be displayed. | |
c906108c | 6486 | @smallexample |
96a2c332 | 6487 | (@value{GDBP}) info line m4_changequote |
c906108c SS |
6488 | Line 895 of "builtin.c" starts at pc 0x634c and ends at 0x6350. |
6489 | @end smallexample | |
6490 | ||
6491 | @noindent | |
15387254 | 6492 | @cindex code address and its source line |
c906108c SS |
6493 | We can also inquire (using @code{*@var{addr}} as the form for |
6494 | @var{linespec}) what source line covers a particular address: | |
6495 | @smallexample | |
6496 | (@value{GDBP}) info line *0x63ff | |
6497 | Line 926 of "builtin.c" starts at pc 0x63e4 and ends at 0x6404. | |
6498 | @end smallexample | |
6499 | ||
6500 | @cindex @code{$_} and @code{info line} | |
15387254 | 6501 | @cindex @code{x} command, default address |
41afff9a | 6502 | @kindex x@r{(examine), and} info line |
c906108c SS |
6503 | After @code{info line}, the default address for the @code{x} command |
6504 | is changed to the starting address of the line, so that @samp{x/i} is | |
6505 | sufficient to begin examining the machine code (@pxref{Memory, | |
79a6e687 | 6506 | ,Examining Memory}). Also, this address is saved as the value of the |
c906108c | 6507 | convenience variable @code{$_} (@pxref{Convenience Vars, ,Convenience |
79a6e687 | 6508 | Variables}). |
c906108c SS |
6509 | |
6510 | @table @code | |
6511 | @kindex disassemble | |
6512 | @cindex assembly instructions | |
6513 | @cindex instructions, assembly | |
6514 | @cindex machine instructions | |
6515 | @cindex listing machine instructions | |
6516 | @item disassemble | |
d14508fe | 6517 | @itemx disassemble /m |
9b117ef3 | 6518 | @itemx disassemble /r |
c906108c | 6519 | This specialized command dumps a range of memory as machine |
d14508fe | 6520 | instructions. It can also print mixed source+disassembly by specifying |
9b117ef3 HZ |
6521 | the @code{/m} modifier and print the raw instructions in hex as well as |
6522 | in symbolic form by specifying the @code{/r}. | |
d14508fe | 6523 | The default memory range is the function surrounding the |
c906108c SS |
6524 | program counter of the selected frame. A single argument to this |
6525 | command is a program counter value; @value{GDBN} dumps the function | |
6526 | surrounding this value. Two arguments specify a range of addresses | |
6527 | (first inclusive, second exclusive) to dump. | |
2b28d209 PP |
6528 | |
6529 | If the range of memory being disassembled contains current program counter, | |
6530 | the instruction at that location is shown with a @code{=>} marker. | |
c906108c SS |
6531 | @end table |
6532 | ||
c906108c SS |
6533 | The following example shows the disassembly of a range of addresses of |
6534 | HP PA-RISC 2.0 code: | |
6535 | ||
6536 | @smallexample | |
6537 | (@value{GDBP}) disas 0x32c4 0x32e4 | |
6538 | Dump of assembler code from 0x32c4 to 0x32e4: | |
2b28d209 PP |
6539 | 0x32c4 <main+204>: addil 0,dp |
6540 | 0x32c8 <main+208>: ldw 0x22c(sr0,r1),r26 | |
6541 | 0x32cc <main+212>: ldil 0x3000,r31 | |
6542 | 0x32d0 <main+216>: ble 0x3f8(sr4,r31) | |
6543 | 0x32d4 <main+220>: ldo 0(r31),rp | |
6544 | 0x32d8 <main+224>: addil -0x800,dp | |
6545 | 0x32dc <main+228>: ldo 0x588(r1),r26 | |
6546 | 0x32e0 <main+232>: ldil 0x3000,r31 | |
c906108c SS |
6547 | End of assembler dump. |
6548 | @end smallexample | |
c906108c | 6549 | |
2b28d209 PP |
6550 | Here is an example showing mixed source+assembly for Intel x86, when the |
6551 | program is stopped just after function prologue: | |
d14508fe DE |
6552 | |
6553 | @smallexample | |
6554 | (@value{GDBP}) disas /m main | |
6555 | Dump of assembler code for function main: | |
6556 | 5 @{ | |
2b28d209 PP |
6557 | 0x08048330 <main+0>: push %ebp |
6558 | 0x08048331 <main+1>: mov %esp,%ebp | |
6559 | 0x08048333 <main+3>: sub $0x8,%esp | |
6560 | 0x08048336 <main+6>: and $0xfffffff0,%esp | |
6561 | 0x08048339 <main+9>: sub $0x10,%esp | |
d14508fe DE |
6562 | |
6563 | 6 printf ("Hello.\n"); | |
2b28d209 PP |
6564 | => 0x0804833c <main+12>: movl $0x8048440,(%esp) |
6565 | 0x08048343 <main+19>: call 0x8048284 <puts@@plt> | |
d14508fe DE |
6566 | |
6567 | 7 return 0; | |
6568 | 8 @} | |
2b28d209 PP |
6569 | 0x08048348 <main+24>: mov $0x0,%eax |
6570 | 0x0804834d <main+29>: leave | |
6571 | 0x0804834e <main+30>: ret | |
d14508fe DE |
6572 | |
6573 | End of assembler dump. | |
6574 | @end smallexample | |
6575 | ||
c906108c SS |
6576 | Some architectures have more than one commonly-used set of instruction |
6577 | mnemonics or other syntax. | |
6578 | ||
76d17f34 EZ |
6579 | For programs that were dynamically linked and use shared libraries, |
6580 | instructions that call functions or branch to locations in the shared | |
6581 | libraries might show a seemingly bogus location---it's actually a | |
6582 | location of the relocation table. On some architectures, @value{GDBN} | |
6583 | might be able to resolve these to actual function names. | |
6584 | ||
c906108c | 6585 | @table @code |
d4f3574e | 6586 | @kindex set disassembly-flavor |
d4f3574e SS |
6587 | @cindex Intel disassembly flavor |
6588 | @cindex AT&T disassembly flavor | |
6589 | @item set disassembly-flavor @var{instruction-set} | |
c906108c SS |
6590 | Select the instruction set to use when disassembling the |
6591 | program via the @code{disassemble} or @code{x/i} commands. | |
6592 | ||
6593 | Currently this command is only defined for the Intel x86 family. You | |
d4f3574e SS |
6594 | can set @var{instruction-set} to either @code{intel} or @code{att}. |
6595 | The default is @code{att}, the AT&T flavor used by default by Unix | |
6596 | assemblers for x86-based targets. | |
9c16f35a EZ |
6597 | |
6598 | @kindex show disassembly-flavor | |
6599 | @item show disassembly-flavor | |
6600 | Show the current setting of the disassembly flavor. | |
c906108c SS |
6601 | @end table |
6602 | ||
91440f57 HZ |
6603 | @table @code |
6604 | @kindex set disassemble-next-line | |
6605 | @kindex show disassemble-next-line | |
6606 | @item set disassemble-next-line | |
6607 | @itemx show disassemble-next-line | |
32ae1842 EZ |
6608 | Control whether or not @value{GDBN} will disassemble the next source |
6609 | line or instruction when execution stops. If ON, @value{GDBN} will | |
6610 | display disassembly of the next source line when execution of the | |
6611 | program being debugged stops. This is @emph{in addition} to | |
6612 | displaying the source line itself, which @value{GDBN} always does if | |
6613 | possible. If the next source line cannot be displayed for some reason | |
6614 | (e.g., if @value{GDBN} cannot find the source file, or there's no line | |
6615 | info in the debug info), @value{GDBN} will display disassembly of the | |
6616 | next @emph{instruction} instead of showing the next source line. If | |
6617 | AUTO, @value{GDBN} will display disassembly of next instruction only | |
6618 | if the source line cannot be displayed. This setting causes | |
6619 | @value{GDBN} to display some feedback when you step through a function | |
6620 | with no line info or whose source file is unavailable. The default is | |
6621 | OFF, which means never display the disassembly of the next line or | |
6622 | instruction. | |
91440f57 HZ |
6623 | @end table |
6624 | ||
c906108c | 6625 | |
6d2ebf8b | 6626 | @node Data |
c906108c SS |
6627 | @chapter Examining Data |
6628 | ||
6629 | @cindex printing data | |
6630 | @cindex examining data | |
6631 | @kindex print | |
6632 | @kindex inspect | |
6633 | @c "inspect" is not quite a synonym if you are using Epoch, which we do not | |
6634 | @c document because it is nonstandard... Under Epoch it displays in a | |
6635 | @c different window or something like that. | |
6636 | The usual way to examine data in your program is with the @code{print} | |
7a292a7a SS |
6637 | command (abbreviated @code{p}), or its synonym @code{inspect}. It |
6638 | evaluates and prints the value of an expression of the language your | |
6639 | program is written in (@pxref{Languages, ,Using @value{GDBN} with | |
6640 | Different Languages}). | |
c906108c SS |
6641 | |
6642 | @table @code | |
d4f3574e SS |
6643 | @item print @var{expr} |
6644 | @itemx print /@var{f} @var{expr} | |
6645 | @var{expr} is an expression (in the source language). By default the | |
6646 | value of @var{expr} is printed in a format appropriate to its data type; | |
c906108c | 6647 | you can choose a different format by specifying @samp{/@var{f}}, where |
d4f3574e | 6648 | @var{f} is a letter specifying the format; see @ref{Output Formats,,Output |
79a6e687 | 6649 | Formats}. |
c906108c SS |
6650 | |
6651 | @item print | |
6652 | @itemx print /@var{f} | |
15387254 | 6653 | @cindex reprint the last value |
d4f3574e | 6654 | If you omit @var{expr}, @value{GDBN} displays the last value again (from the |
79a6e687 | 6655 | @dfn{value history}; @pxref{Value History, ,Value History}). This allows you to |
c906108c SS |
6656 | conveniently inspect the same value in an alternative format. |
6657 | @end table | |
6658 | ||
6659 | A more low-level way of examining data is with the @code{x} command. | |
6660 | It examines data in memory at a specified address and prints it in a | |
79a6e687 | 6661 | specified format. @xref{Memory, ,Examining Memory}. |
c906108c | 6662 | |
7a292a7a | 6663 | If you are interested in information about types, or about how the |
d4f3574e SS |
6664 | fields of a struct or a class are declared, use the @code{ptype @var{exp}} |
6665 | command rather than @code{print}. @xref{Symbols, ,Examining the Symbol | |
7a292a7a | 6666 | Table}. |
c906108c SS |
6667 | |
6668 | @menu | |
6669 | * Expressions:: Expressions | |
6ba66d6a | 6670 | * Ambiguous Expressions:: Ambiguous Expressions |
c906108c SS |
6671 | * Variables:: Program variables |
6672 | * Arrays:: Artificial arrays | |
6673 | * Output Formats:: Output formats | |
6674 | * Memory:: Examining memory | |
6675 | * Auto Display:: Automatic display | |
6676 | * Print Settings:: Print settings | |
6677 | * Value History:: Value history | |
6678 | * Convenience Vars:: Convenience variables | |
6679 | * Registers:: Registers | |
c906108c | 6680 | * Floating Point Hardware:: Floating point hardware |
53c69bd7 | 6681 | * Vector Unit:: Vector Unit |
721c2651 | 6682 | * OS Information:: Auxiliary data provided by operating system |
29e57380 | 6683 | * Memory Region Attributes:: Memory region attributes |
16d9dec6 | 6684 | * Dump/Restore Files:: Copy between memory and a file |
384ee23f | 6685 | * Core File Generation:: Cause a program dump its core |
a0eb71c5 KB |
6686 | * Character Sets:: Debugging programs that use a different |
6687 | character set than GDB does | |
09d4efe1 | 6688 | * Caching Remote Data:: Data caching for remote targets |
08388c79 | 6689 | * Searching Memory:: Searching memory for a sequence of bytes |
c906108c SS |
6690 | @end menu |
6691 | ||
6d2ebf8b | 6692 | @node Expressions |
c906108c SS |
6693 | @section Expressions |
6694 | ||
6695 | @cindex expressions | |
6696 | @code{print} and many other @value{GDBN} commands accept an expression and | |
6697 | compute its value. Any kind of constant, variable or operator defined | |
6698 | by the programming language you are using is valid in an expression in | |
e2e0bcd1 JB |
6699 | @value{GDBN}. This includes conditional expressions, function calls, |
6700 | casts, and string constants. It also includes preprocessor macros, if | |
6701 | you compiled your program to include this information; see | |
6702 | @ref{Compilation}. | |
c906108c | 6703 | |
15387254 | 6704 | @cindex arrays in expressions |
d4f3574e SS |
6705 | @value{GDBN} supports array constants in expressions input by |
6706 | the user. The syntax is @{@var{element}, @var{element}@dots{}@}. For example, | |
63092375 DJ |
6707 | you can use the command @code{print @{1, 2, 3@}} to create an array |
6708 | of three integers. If you pass an array to a function or assign it | |
6709 | to a program variable, @value{GDBN} copies the array to memory that | |
6710 | is @code{malloc}ed in the target program. | |
c906108c | 6711 | |
c906108c SS |
6712 | Because C is so widespread, most of the expressions shown in examples in |
6713 | this manual are in C. @xref{Languages, , Using @value{GDBN} with Different | |
6714 | Languages}, for information on how to use expressions in other | |
6715 | languages. | |
6716 | ||
6717 | In this section, we discuss operators that you can use in @value{GDBN} | |
6718 | expressions regardless of your programming language. | |
6719 | ||
15387254 | 6720 | @cindex casts, in expressions |
c906108c SS |
6721 | Casts are supported in all languages, not just in C, because it is so |
6722 | useful to cast a number into a pointer in order to examine a structure | |
6723 | at that address in memory. | |
6724 | @c FIXME: casts supported---Mod2 true? | |
c906108c SS |
6725 | |
6726 | @value{GDBN} supports these operators, in addition to those common | |
6727 | to programming languages: | |
6728 | ||
6729 | @table @code | |
6730 | @item @@ | |
6731 | @samp{@@} is a binary operator for treating parts of memory as arrays. | |
79a6e687 | 6732 | @xref{Arrays, ,Artificial Arrays}, for more information. |
c906108c SS |
6733 | |
6734 | @item :: | |
6735 | @samp{::} allows you to specify a variable in terms of the file or | |
79a6e687 | 6736 | function where it is defined. @xref{Variables, ,Program Variables}. |
c906108c SS |
6737 | |
6738 | @cindex @{@var{type}@} | |
6739 | @cindex type casting memory | |
6740 | @cindex memory, viewing as typed object | |
6741 | @cindex casts, to view memory | |
6742 | @item @{@var{type}@} @var{addr} | |
6743 | Refers to an object of type @var{type} stored at address @var{addr} in | |
6744 | memory. @var{addr} may be any expression whose value is an integer or | |
6745 | pointer (but parentheses are required around binary operators, just as in | |
6746 | a cast). This construct is allowed regardless of what kind of data is | |
6747 | normally supposed to reside at @var{addr}. | |
6748 | @end table | |
6749 | ||
6ba66d6a JB |
6750 | @node Ambiguous Expressions |
6751 | @section Ambiguous Expressions | |
6752 | @cindex ambiguous expressions | |
6753 | ||
6754 | Expressions can sometimes contain some ambiguous elements. For instance, | |
6755 | some programming languages (notably Ada, C@t{++} and Objective-C) permit | |
6756 | a single function name to be defined several times, for application in | |
6757 | different contexts. This is called @dfn{overloading}. Another example | |
6758 | involving Ada is generics. A @dfn{generic package} is similar to C@t{++} | |
6759 | templates and is typically instantiated several times, resulting in | |
6760 | the same function name being defined in different contexts. | |
6761 | ||
6762 | In some cases and depending on the language, it is possible to adjust | |
6763 | the expression to remove the ambiguity. For instance in C@t{++}, you | |
6764 | can specify the signature of the function you want to break on, as in | |
6765 | @kbd{break @var{function}(@var{types})}. In Ada, using the fully | |
6766 | qualified name of your function often makes the expression unambiguous | |
6767 | as well. | |
6768 | ||
6769 | When an ambiguity that needs to be resolved is detected, the debugger | |
6770 | has the capability to display a menu of numbered choices for each | |
6771 | possibility, and then waits for the selection with the prompt @samp{>}. | |
6772 | The first option is always @samp{[0] cancel}, and typing @kbd{0 @key{RET}} | |
6773 | aborts the current command. If the command in which the expression was | |
6774 | used allows more than one choice to be selected, the next option in the | |
6775 | menu is @samp{[1] all}, and typing @kbd{1 @key{RET}} selects all possible | |
6776 | choices. | |
6777 | ||
6778 | For example, the following session excerpt shows an attempt to set a | |
6779 | breakpoint at the overloaded symbol @code{String::after}. | |
6780 | We choose three particular definitions of that function name: | |
6781 | ||
6782 | @c FIXME! This is likely to change to show arg type lists, at least | |
6783 | @smallexample | |
6784 | @group | |
6785 | (@value{GDBP}) b String::after | |
6786 | [0] cancel | |
6787 | [1] all | |
6788 | [2] file:String.cc; line number:867 | |
6789 | [3] file:String.cc; line number:860 | |
6790 | [4] file:String.cc; line number:875 | |
6791 | [5] file:String.cc; line number:853 | |
6792 | [6] file:String.cc; line number:846 | |
6793 | [7] file:String.cc; line number:735 | |
6794 | > 2 4 6 | |
6795 | Breakpoint 1 at 0xb26c: file String.cc, line 867. | |
6796 | Breakpoint 2 at 0xb344: file String.cc, line 875. | |
6797 | Breakpoint 3 at 0xafcc: file String.cc, line 846. | |
6798 | Multiple breakpoints were set. | |
6799 | Use the "delete" command to delete unwanted | |
6800 | breakpoints. | |
6801 | (@value{GDBP}) | |
6802 | @end group | |
6803 | @end smallexample | |
6804 | ||
6805 | @table @code | |
6806 | @kindex set multiple-symbols | |
6807 | @item set multiple-symbols @var{mode} | |
6808 | @cindex multiple-symbols menu | |
6809 | ||
6810 | This option allows you to adjust the debugger behavior when an expression | |
6811 | is ambiguous. | |
6812 | ||
6813 | By default, @var{mode} is set to @code{all}. If the command with which | |
6814 | the expression is used allows more than one choice, then @value{GDBN} | |
6815 | automatically selects all possible choices. For instance, inserting | |
6816 | a breakpoint on a function using an ambiguous name results in a breakpoint | |
6817 | inserted on each possible match. However, if a unique choice must be made, | |
6818 | then @value{GDBN} uses the menu to help you disambiguate the expression. | |
6819 | For instance, printing the address of an overloaded function will result | |
6820 | in the use of the menu. | |
6821 | ||
6822 | When @var{mode} is set to @code{ask}, the debugger always uses the menu | |
6823 | when an ambiguity is detected. | |
6824 | ||
6825 | Finally, when @var{mode} is set to @code{cancel}, the debugger reports | |
6826 | an error due to the ambiguity and the command is aborted. | |
6827 | ||
6828 | @kindex show multiple-symbols | |
6829 | @item show multiple-symbols | |
6830 | Show the current value of the @code{multiple-symbols} setting. | |
6831 | @end table | |
6832 | ||
6d2ebf8b | 6833 | @node Variables |
79a6e687 | 6834 | @section Program Variables |
c906108c SS |
6835 | |
6836 | The most common kind of expression to use is the name of a variable | |
6837 | in your program. | |
6838 | ||
6839 | Variables in expressions are understood in the selected stack frame | |
79a6e687 | 6840 | (@pxref{Selection, ,Selecting a Frame}); they must be either: |
c906108c SS |
6841 | |
6842 | @itemize @bullet | |
6843 | @item | |
6844 | global (or file-static) | |
6845 | @end itemize | |
6846 | ||
5d161b24 | 6847 | @noindent or |
c906108c SS |
6848 | |
6849 | @itemize @bullet | |
6850 | @item | |
6851 | visible according to the scope rules of the | |
6852 | programming language from the point of execution in that frame | |
5d161b24 | 6853 | @end itemize |
c906108c SS |
6854 | |
6855 | @noindent This means that in the function | |
6856 | ||
474c8240 | 6857 | @smallexample |
c906108c SS |
6858 | foo (a) |
6859 | int a; | |
6860 | @{ | |
6861 | bar (a); | |
6862 | @{ | |
6863 | int b = test (); | |
6864 | bar (b); | |
6865 | @} | |
6866 | @} | |
474c8240 | 6867 | @end smallexample |
c906108c SS |
6868 | |
6869 | @noindent | |
6870 | you can examine and use the variable @code{a} whenever your program is | |
6871 | executing within the function @code{foo}, but you can only use or | |
6872 | examine the variable @code{b} while your program is executing inside | |
6873 | the block where @code{b} is declared. | |
6874 | ||
6875 | @cindex variable name conflict | |
6876 | There is an exception: you can refer to a variable or function whose | |
6877 | scope is a single source file even if the current execution point is not | |
6878 | in this file. But it is possible to have more than one such variable or | |
6879 | function with the same name (in different source files). If that | |
6880 | happens, referring to that name has unpredictable effects. If you wish, | |
6881 | you can specify a static variable in a particular function or file, | |
15387254 | 6882 | using the colon-colon (@code{::}) notation: |
c906108c | 6883 | |
d4f3574e | 6884 | @cindex colon-colon, context for variables/functions |
12c27660 | 6885 | @ifnotinfo |
c906108c | 6886 | @c info cannot cope with a :: index entry, but why deprive hard copy readers? |
41afff9a | 6887 | @cindex @code{::}, context for variables/functions |
12c27660 | 6888 | @end ifnotinfo |
474c8240 | 6889 | @smallexample |
c906108c SS |
6890 | @var{file}::@var{variable} |
6891 | @var{function}::@var{variable} | |
474c8240 | 6892 | @end smallexample |
c906108c SS |
6893 | |
6894 | @noindent | |
6895 | Here @var{file} or @var{function} is the name of the context for the | |
6896 | static @var{variable}. In the case of file names, you can use quotes to | |
6897 | make sure @value{GDBN} parses the file name as a single word---for example, | |
6898 | to print a global value of @code{x} defined in @file{f2.c}: | |
6899 | ||
474c8240 | 6900 | @smallexample |
c906108c | 6901 | (@value{GDBP}) p 'f2.c'::x |
474c8240 | 6902 | @end smallexample |
c906108c | 6903 | |
b37052ae | 6904 | @cindex C@t{++} scope resolution |
c906108c | 6905 | This use of @samp{::} is very rarely in conflict with the very similar |
b37052ae | 6906 | use of the same notation in C@t{++}. @value{GDBN} also supports use of the C@t{++} |
c906108c SS |
6907 | scope resolution operator in @value{GDBN} expressions. |
6908 | @c FIXME: Um, so what happens in one of those rare cases where it's in | |
6909 | @c conflict?? --mew | |
c906108c SS |
6910 | |
6911 | @cindex wrong values | |
6912 | @cindex variable values, wrong | |
15387254 EZ |
6913 | @cindex function entry/exit, wrong values of variables |
6914 | @cindex optimized code, wrong values of variables | |
c906108c SS |
6915 | @quotation |
6916 | @emph{Warning:} Occasionally, a local variable may appear to have the | |
6917 | wrong value at certain points in a function---just after entry to a new | |
6918 | scope, and just before exit. | |
6919 | @end quotation | |
6920 | You may see this problem when you are stepping by machine instructions. | |
6921 | This is because, on most machines, it takes more than one instruction to | |
6922 | set up a stack frame (including local variable definitions); if you are | |
6923 | stepping by machine instructions, variables may appear to have the wrong | |
6924 | values until the stack frame is completely built. On exit, it usually | |
6925 | also takes more than one machine instruction to destroy a stack frame; | |
6926 | after you begin stepping through that group of instructions, local | |
6927 | variable definitions may be gone. | |
6928 | ||
6929 | This may also happen when the compiler does significant optimizations. | |
6930 | To be sure of always seeing accurate values, turn off all optimization | |
6931 | when compiling. | |
6932 | ||
d4f3574e SS |
6933 | @cindex ``No symbol "foo" in current context'' |
6934 | Another possible effect of compiler optimizations is to optimize | |
6935 | unused variables out of existence, or assign variables to registers (as | |
6936 | opposed to memory addresses). Depending on the support for such cases | |
6937 | offered by the debug info format used by the compiler, @value{GDBN} | |
6938 | might not be able to display values for such local variables. If that | |
6939 | happens, @value{GDBN} will print a message like this: | |
6940 | ||
474c8240 | 6941 | @smallexample |
d4f3574e | 6942 | No symbol "foo" in current context. |
474c8240 | 6943 | @end smallexample |
d4f3574e SS |
6944 | |
6945 | To solve such problems, either recompile without optimizations, or use a | |
6946 | different debug info format, if the compiler supports several such | |
15387254 | 6947 | formats. For example, @value{NGCC}, the @sc{gnu} C/C@t{++} compiler, |
0179ffac DC |
6948 | usually supports the @option{-gstabs+} option. @option{-gstabs+} |
6949 | produces debug info in a format that is superior to formats such as | |
6950 | COFF. You may be able to use DWARF 2 (@option{-gdwarf-2}), which is also | |
6951 | an effective form for debug info. @xref{Debugging Options,,Options | |
ce9341a1 BW |
6952 | for Debugging Your Program or GCC, gcc.info, Using the @sc{gnu} |
6953 | Compiler Collection (GCC)}. | |
79a6e687 | 6954 | @xref{C, ,C and C@t{++}}, for more information about debug info formats |
15387254 | 6955 | that are best suited to C@t{++} programs. |
d4f3574e | 6956 | |
ab1adacd EZ |
6957 | If you ask to print an object whose contents are unknown to |
6958 | @value{GDBN}, e.g., because its data type is not completely specified | |
6959 | by the debug information, @value{GDBN} will say @samp{<incomplete | |
6960 | type>}. @xref{Symbols, incomplete type}, for more about this. | |
6961 | ||
3a60f64e JK |
6962 | Strings are identified as arrays of @code{char} values without specified |
6963 | signedness. Arrays of either @code{signed char} or @code{unsigned char} get | |
6964 | printed as arrays of 1 byte sized integers. @code{-fsigned-char} or | |
6965 | @code{-funsigned-char} @value{NGCC} options have no effect as @value{GDBN} | |
6966 | defines literal string type @code{"char"} as @code{char} without a sign. | |
6967 | For program code | |
6968 | ||
6969 | @smallexample | |
6970 | char var0[] = "A"; | |
6971 | signed char var1[] = "A"; | |
6972 | @end smallexample | |
6973 | ||
6974 | You get during debugging | |
6975 | @smallexample | |
6976 | (gdb) print var0 | |
6977 | $1 = "A" | |
6978 | (gdb) print var1 | |
6979 | $2 = @{65 'A', 0 '\0'@} | |
6980 | @end smallexample | |
6981 | ||
6d2ebf8b | 6982 | @node Arrays |
79a6e687 | 6983 | @section Artificial Arrays |
c906108c SS |
6984 | |
6985 | @cindex artificial array | |
15387254 | 6986 | @cindex arrays |
41afff9a | 6987 | @kindex @@@r{, referencing memory as an array} |
c906108c SS |
6988 | It is often useful to print out several successive objects of the |
6989 | same type in memory; a section of an array, or an array of | |
6990 | dynamically determined size for which only a pointer exists in the | |
6991 | program. | |
6992 | ||
6993 | You can do this by referring to a contiguous span of memory as an | |
6994 | @dfn{artificial array}, using the binary operator @samp{@@}. The left | |
6995 | operand of @samp{@@} should be the first element of the desired array | |
6996 | and be an individual object. The right operand should be the desired length | |
6997 | of the array. The result is an array value whose elements are all of | |
6998 | the type of the left argument. The first element is actually the left | |
6999 | argument; the second element comes from bytes of memory immediately | |
7000 | following those that hold the first element, and so on. Here is an | |
7001 | example. If a program says | |
7002 | ||
474c8240 | 7003 | @smallexample |
c906108c | 7004 | int *array = (int *) malloc (len * sizeof (int)); |
474c8240 | 7005 | @end smallexample |
c906108c SS |
7006 | |
7007 | @noindent | |
7008 | you can print the contents of @code{array} with | |
7009 | ||
474c8240 | 7010 | @smallexample |
c906108c | 7011 | p *array@@len |
474c8240 | 7012 | @end smallexample |
c906108c SS |
7013 | |
7014 | The left operand of @samp{@@} must reside in memory. Array values made | |
7015 | with @samp{@@} in this way behave just like other arrays in terms of | |
7016 | subscripting, and are coerced to pointers when used in expressions. | |
7017 | Artificial arrays most often appear in expressions via the value history | |
79a6e687 | 7018 | (@pxref{Value History, ,Value History}), after printing one out. |
c906108c SS |
7019 | |
7020 | Another way to create an artificial array is to use a cast. | |
7021 | This re-interprets a value as if it were an array. | |
7022 | The value need not be in memory: | |
474c8240 | 7023 | @smallexample |
c906108c SS |
7024 | (@value{GDBP}) p/x (short[2])0x12345678 |
7025 | $1 = @{0x1234, 0x5678@} | |
474c8240 | 7026 | @end smallexample |
c906108c SS |
7027 | |
7028 | As a convenience, if you leave the array length out (as in | |
c3f6f71d | 7029 | @samp{(@var{type}[])@var{value}}) @value{GDBN} calculates the size to fill |
c906108c | 7030 | the value (as @samp{sizeof(@var{value})/sizeof(@var{type})}: |
474c8240 | 7031 | @smallexample |
c906108c SS |
7032 | (@value{GDBP}) p/x (short[])0x12345678 |
7033 | $2 = @{0x1234, 0x5678@} | |
474c8240 | 7034 | @end smallexample |
c906108c SS |
7035 | |
7036 | Sometimes the artificial array mechanism is not quite enough; in | |
7037 | moderately complex data structures, the elements of interest may not | |
7038 | actually be adjacent---for example, if you are interested in the values | |
7039 | of pointers in an array. One useful work-around in this situation is | |
7040 | to use a convenience variable (@pxref{Convenience Vars, ,Convenience | |
79a6e687 | 7041 | Variables}) as a counter in an expression that prints the first |
c906108c SS |
7042 | interesting value, and then repeat that expression via @key{RET}. For |
7043 | instance, suppose you have an array @code{dtab} of pointers to | |
7044 | structures, and you are interested in the values of a field @code{fv} | |
7045 | in each structure. Here is an example of what you might type: | |
7046 | ||
474c8240 | 7047 | @smallexample |
c906108c SS |
7048 | set $i = 0 |
7049 | p dtab[$i++]->fv | |
7050 | @key{RET} | |
7051 | @key{RET} | |
7052 | @dots{} | |
474c8240 | 7053 | @end smallexample |
c906108c | 7054 | |
6d2ebf8b | 7055 | @node Output Formats |
79a6e687 | 7056 | @section Output Formats |
c906108c SS |
7057 | |
7058 | @cindex formatted output | |
7059 | @cindex output formats | |
7060 | By default, @value{GDBN} prints a value according to its data type. Sometimes | |
7061 | this is not what you want. For example, you might want to print a number | |
7062 | in hex, or a pointer in decimal. Or you might want to view data in memory | |
7063 | at a certain address as a character string or as an instruction. To do | |
7064 | these things, specify an @dfn{output format} when you print a value. | |
7065 | ||
7066 | The simplest use of output formats is to say how to print a value | |
7067 | already computed. This is done by starting the arguments of the | |
7068 | @code{print} command with a slash and a format letter. The format | |
7069 | letters supported are: | |
7070 | ||
7071 | @table @code | |
7072 | @item x | |
7073 | Regard the bits of the value as an integer, and print the integer in | |
7074 | hexadecimal. | |
7075 | ||
7076 | @item d | |
7077 | Print as integer in signed decimal. | |
7078 | ||
7079 | @item u | |
7080 | Print as integer in unsigned decimal. | |
7081 | ||
7082 | @item o | |
7083 | Print as integer in octal. | |
7084 | ||
7085 | @item t | |
7086 | Print as integer in binary. The letter @samp{t} stands for ``two''. | |
7087 | @footnote{@samp{b} cannot be used because these format letters are also | |
7088 | used with the @code{x} command, where @samp{b} stands for ``byte''; | |
79a6e687 | 7089 | see @ref{Memory,,Examining Memory}.} |
c906108c SS |
7090 | |
7091 | @item a | |
7092 | @cindex unknown address, locating | |
3d67e040 | 7093 | @cindex locate address |
c906108c SS |
7094 | Print as an address, both absolute in hexadecimal and as an offset from |
7095 | the nearest preceding symbol. You can use this format used to discover | |
7096 | where (in what function) an unknown address is located: | |
7097 | ||
474c8240 | 7098 | @smallexample |
c906108c SS |
7099 | (@value{GDBP}) p/a 0x54320 |
7100 | $3 = 0x54320 <_initialize_vx+396> | |
474c8240 | 7101 | @end smallexample |
c906108c | 7102 | |
3d67e040 EZ |
7103 | @noindent |
7104 | The command @code{info symbol 0x54320} yields similar results. | |
7105 | @xref{Symbols, info symbol}. | |
7106 | ||
c906108c | 7107 | @item c |
51274035 EZ |
7108 | Regard as an integer and print it as a character constant. This |
7109 | prints both the numerical value and its character representation. The | |
7110 | character representation is replaced with the octal escape @samp{\nnn} | |
7111 | for characters outside the 7-bit @sc{ascii} range. | |
c906108c | 7112 | |
ea37ba09 DJ |
7113 | Without this format, @value{GDBN} displays @code{char}, |
7114 | @w{@code{unsigned char}}, and @w{@code{signed char}} data as character | |
7115 | constants. Single-byte members of vectors are displayed as integer | |
7116 | data. | |
7117 | ||
c906108c SS |
7118 | @item f |
7119 | Regard the bits of the value as a floating point number and print | |
7120 | using typical floating point syntax. | |
ea37ba09 DJ |
7121 | |
7122 | @item s | |
7123 | @cindex printing strings | |
7124 | @cindex printing byte arrays | |
7125 | Regard as a string, if possible. With this format, pointers to single-byte | |
7126 | data are displayed as null-terminated strings and arrays of single-byte data | |
7127 | are displayed as fixed-length strings. Other values are displayed in their | |
7128 | natural types. | |
7129 | ||
7130 | Without this format, @value{GDBN} displays pointers to and arrays of | |
7131 | @code{char}, @w{@code{unsigned char}}, and @w{@code{signed char}} as | |
7132 | strings. Single-byte members of a vector are displayed as an integer | |
7133 | array. | |
a6bac58e TT |
7134 | |
7135 | @item r | |
7136 | @cindex raw printing | |
7137 | Print using the @samp{raw} formatting. By default, @value{GDBN} will | |
7138 | use a type-specific pretty-printer. The @samp{r} format bypasses any | |
7139 | pretty-printer which might exist for the value's type. | |
c906108c SS |
7140 | @end table |
7141 | ||
7142 | For example, to print the program counter in hex (@pxref{Registers}), type | |
7143 | ||
474c8240 | 7144 | @smallexample |
c906108c | 7145 | p/x $pc |
474c8240 | 7146 | @end smallexample |
c906108c SS |
7147 | |
7148 | @noindent | |
7149 | Note that no space is required before the slash; this is because command | |
7150 | names in @value{GDBN} cannot contain a slash. | |
7151 | ||
7152 | To reprint the last value in the value history with a different format, | |
7153 | you can use the @code{print} command with just a format and no | |
7154 | expression. For example, @samp{p/x} reprints the last value in hex. | |
7155 | ||
6d2ebf8b | 7156 | @node Memory |
79a6e687 | 7157 | @section Examining Memory |
c906108c SS |
7158 | |
7159 | You can use the command @code{x} (for ``examine'') to examine memory in | |
7160 | any of several formats, independently of your program's data types. | |
7161 | ||
7162 | @cindex examining memory | |
7163 | @table @code | |
41afff9a | 7164 | @kindex x @r{(examine memory)} |
c906108c SS |
7165 | @item x/@var{nfu} @var{addr} |
7166 | @itemx x @var{addr} | |
7167 | @itemx x | |
7168 | Use the @code{x} command to examine memory. | |
7169 | @end table | |
7170 | ||
7171 | @var{n}, @var{f}, and @var{u} are all optional parameters that specify how | |
7172 | much memory to display and how to format it; @var{addr} is an | |
7173 | expression giving the address where you want to start displaying memory. | |
7174 | If you use defaults for @var{nfu}, you need not type the slash @samp{/}. | |
7175 | Several commands set convenient defaults for @var{addr}. | |
7176 | ||
7177 | @table @r | |
7178 | @item @var{n}, the repeat count | |
7179 | The repeat count is a decimal integer; the default is 1. It specifies | |
7180 | how much memory (counting by units @var{u}) to display. | |
7181 | @c This really is **decimal**; unaffected by 'set radix' as of GDB | |
7182 | @c 4.1.2. | |
7183 | ||
7184 | @item @var{f}, the display format | |
51274035 EZ |
7185 | The display format is one of the formats used by @code{print} |
7186 | (@samp{x}, @samp{d}, @samp{u}, @samp{o}, @samp{t}, @samp{a}, @samp{c}, | |
ea37ba09 DJ |
7187 | @samp{f}, @samp{s}), and in addition @samp{i} (for machine instructions). |
7188 | The default is @samp{x} (hexadecimal) initially. The default changes | |
7189 | each time you use either @code{x} or @code{print}. | |
c906108c SS |
7190 | |
7191 | @item @var{u}, the unit size | |
7192 | The unit size is any of | |
7193 | ||
7194 | @table @code | |
7195 | @item b | |
7196 | Bytes. | |
7197 | @item h | |
7198 | Halfwords (two bytes). | |
7199 | @item w | |
7200 | Words (four bytes). This is the initial default. | |
7201 | @item g | |
7202 | Giant words (eight bytes). | |
7203 | @end table | |
7204 | ||
7205 | Each time you specify a unit size with @code{x}, that size becomes the | |
7206 | default unit the next time you use @code{x}. (For the @samp{s} and | |
7207 | @samp{i} formats, the unit size is ignored and is normally not written.) | |
7208 | ||
7209 | @item @var{addr}, starting display address | |
7210 | @var{addr} is the address where you want @value{GDBN} to begin displaying | |
7211 | memory. The expression need not have a pointer value (though it may); | |
7212 | it is always interpreted as an integer address of a byte of memory. | |
7213 | @xref{Expressions, ,Expressions}, for more information on expressions. The default for | |
7214 | @var{addr} is usually just after the last address examined---but several | |
7215 | other commands also set the default address: @code{info breakpoints} (to | |
7216 | the address of the last breakpoint listed), @code{info line} (to the | |
7217 | starting address of a line), and @code{print} (if you use it to display | |
7218 | a value from memory). | |
7219 | @end table | |
7220 | ||
7221 | For example, @samp{x/3uh 0x54320} is a request to display three halfwords | |
7222 | (@code{h}) of memory, formatted as unsigned decimal integers (@samp{u}), | |
7223 | starting at address @code{0x54320}. @samp{x/4xw $sp} prints the four | |
7224 | words (@samp{w}) of memory above the stack pointer (here, @samp{$sp}; | |
d4f3574e | 7225 | @pxref{Registers, ,Registers}) in hexadecimal (@samp{x}). |
c906108c SS |
7226 | |
7227 | Since the letters indicating unit sizes are all distinct from the | |
7228 | letters specifying output formats, you do not have to remember whether | |
7229 | unit size or format comes first; either order works. The output | |
7230 | specifications @samp{4xw} and @samp{4wx} mean exactly the same thing. | |
7231 | (However, the count @var{n} must come first; @samp{wx4} does not work.) | |
7232 | ||
7233 | Even though the unit size @var{u} is ignored for the formats @samp{s} | |
7234 | and @samp{i}, you might still want to use a count @var{n}; for example, | |
7235 | @samp{3i} specifies that you want to see three machine instructions, | |
a4642986 MR |
7236 | including any operands. For convenience, especially when used with |
7237 | the @code{display} command, the @samp{i} format also prints branch delay | |
7238 | slot instructions, if any, beyond the count specified, which immediately | |
7239 | follow the last instruction that is within the count. The command | |
7240 | @code{disassemble} gives an alternative way of inspecting machine | |
7241 | instructions; see @ref{Machine Code,,Source and Machine Code}. | |
c906108c SS |
7242 | |
7243 | All the defaults for the arguments to @code{x} are designed to make it | |
7244 | easy to continue scanning memory with minimal specifications each time | |
7245 | you use @code{x}. For example, after you have inspected three machine | |
7246 | instructions with @samp{x/3i @var{addr}}, you can inspect the next seven | |
7247 | with just @samp{x/7}. If you use @key{RET} to repeat the @code{x} command, | |
7248 | the repeat count @var{n} is used again; the other arguments default as | |
7249 | for successive uses of @code{x}. | |
7250 | ||
2b28d209 PP |
7251 | When examining machine instructions, the instruction at current program |
7252 | counter is shown with a @code{=>} marker. For example: | |
7253 | ||
7254 | @smallexample | |
7255 | (@value{GDBP}) x/5i $pc-6 | |
7256 | 0x804837f <main+11>: mov %esp,%ebp | |
7257 | 0x8048381 <main+13>: push %ecx | |
7258 | 0x8048382 <main+14>: sub $0x4,%esp | |
7259 | => 0x8048385 <main+17>: movl $0x8048460,(%esp) | |
7260 | 0x804838c <main+24>: call 0x80482d4 <puts@@plt> | |
7261 | @end smallexample | |
7262 | ||
c906108c SS |
7263 | @cindex @code{$_}, @code{$__}, and value history |
7264 | The addresses and contents printed by the @code{x} command are not saved | |
7265 | in the value history because there is often too much of them and they | |
7266 | would get in the way. Instead, @value{GDBN} makes these values available for | |
7267 | subsequent use in expressions as values of the convenience variables | |
7268 | @code{$_} and @code{$__}. After an @code{x} command, the last address | |
7269 | examined is available for use in expressions in the convenience variable | |
7270 | @code{$_}. The contents of that address, as examined, are available in | |
7271 | the convenience variable @code{$__}. | |
7272 | ||
7273 | If the @code{x} command has a repeat count, the address and contents saved | |
7274 | are from the last memory unit printed; this is not the same as the last | |
7275 | address printed if several units were printed on the last line of output. | |
7276 | ||
09d4efe1 EZ |
7277 | @cindex remote memory comparison |
7278 | @cindex verify remote memory image | |
7279 | When you are debugging a program running on a remote target machine | |
ea35711c | 7280 | (@pxref{Remote Debugging}), you may wish to verify the program's image in the |
09d4efe1 EZ |
7281 | remote machine's memory against the executable file you downloaded to |
7282 | the target. The @code{compare-sections} command is provided for such | |
7283 | situations. | |
7284 | ||
7285 | @table @code | |
7286 | @kindex compare-sections | |
7287 | @item compare-sections @r{[}@var{section-name}@r{]} | |
7288 | Compare the data of a loadable section @var{section-name} in the | |
7289 | executable file of the program being debugged with the same section in | |
7290 | the remote machine's memory, and report any mismatches. With no | |
7291 | arguments, compares all loadable sections. This command's | |
7292 | availability depends on the target's support for the @code{"qCRC"} | |
7293 | remote request. | |
7294 | @end table | |
7295 | ||
6d2ebf8b | 7296 | @node Auto Display |
79a6e687 | 7297 | @section Automatic Display |
c906108c SS |
7298 | @cindex automatic display |
7299 | @cindex display of expressions | |
7300 | ||
7301 | If you find that you want to print the value of an expression frequently | |
7302 | (to see how it changes), you might want to add it to the @dfn{automatic | |
7303 | display list} so that @value{GDBN} prints its value each time your program stops. | |
7304 | Each expression added to the list is given a number to identify it; | |
7305 | to remove an expression from the list, you specify that number. | |
7306 | The automatic display looks like this: | |
7307 | ||
474c8240 | 7308 | @smallexample |
c906108c SS |
7309 | 2: foo = 38 |
7310 | 3: bar[5] = (struct hack *) 0x3804 | |
474c8240 | 7311 | @end smallexample |
c906108c SS |
7312 | |
7313 | @noindent | |
7314 | This display shows item numbers, expressions and their current values. As with | |
7315 | displays you request manually using @code{x} or @code{print}, you can | |
7316 | specify the output format you prefer; in fact, @code{display} decides | |
ea37ba09 DJ |
7317 | whether to use @code{print} or @code{x} depending your format |
7318 | specification---it uses @code{x} if you specify either the @samp{i} | |
7319 | or @samp{s} format, or a unit size; otherwise it uses @code{print}. | |
c906108c SS |
7320 | |
7321 | @table @code | |
7322 | @kindex display | |
d4f3574e SS |
7323 | @item display @var{expr} |
7324 | Add the expression @var{expr} to the list of expressions to display | |
c906108c SS |
7325 | each time your program stops. @xref{Expressions, ,Expressions}. |
7326 | ||
7327 | @code{display} does not repeat if you press @key{RET} again after using it. | |
7328 | ||
d4f3574e | 7329 | @item display/@var{fmt} @var{expr} |
c906108c | 7330 | For @var{fmt} specifying only a display format and not a size or |
d4f3574e | 7331 | count, add the expression @var{expr} to the auto-display list but |
c906108c | 7332 | arrange to display it each time in the specified format @var{fmt}. |
79a6e687 | 7333 | @xref{Output Formats,,Output Formats}. |
c906108c SS |
7334 | |
7335 | @item display/@var{fmt} @var{addr} | |
7336 | For @var{fmt} @samp{i} or @samp{s}, or including a unit-size or a | |
7337 | number of units, add the expression @var{addr} as a memory address to | |
7338 | be examined each time your program stops. Examining means in effect | |
79a6e687 | 7339 | doing @samp{x/@var{fmt} @var{addr}}. @xref{Memory, ,Examining Memory}. |
c906108c SS |
7340 | @end table |
7341 | ||
7342 | For example, @samp{display/i $pc} can be helpful, to see the machine | |
7343 | instruction about to be executed each time execution stops (@samp{$pc} | |
d4f3574e | 7344 | is a common name for the program counter; @pxref{Registers, ,Registers}). |
c906108c SS |
7345 | |
7346 | @table @code | |
7347 | @kindex delete display | |
7348 | @kindex undisplay | |
7349 | @item undisplay @var{dnums}@dots{} | |
7350 | @itemx delete display @var{dnums}@dots{} | |
7351 | Remove item numbers @var{dnums} from the list of expressions to display. | |
7352 | ||
7353 | @code{undisplay} does not repeat if you press @key{RET} after using it. | |
7354 | (Otherwise you would just get the error @samp{No display number @dots{}}.) | |
7355 | ||
7356 | @kindex disable display | |
7357 | @item disable display @var{dnums}@dots{} | |
7358 | Disable the display of item numbers @var{dnums}. A disabled display | |
7359 | item is not printed automatically, but is not forgotten. It may be | |
7360 | enabled again later. | |
7361 | ||
7362 | @kindex enable display | |
7363 | @item enable display @var{dnums}@dots{} | |
7364 | Enable display of item numbers @var{dnums}. It becomes effective once | |
7365 | again in auto display of its expression, until you specify otherwise. | |
7366 | ||
7367 | @item display | |
7368 | Display the current values of the expressions on the list, just as is | |
7369 | done when your program stops. | |
7370 | ||
7371 | @kindex info display | |
7372 | @item info display | |
7373 | Print the list of expressions previously set up to display | |
7374 | automatically, each one with its item number, but without showing the | |
7375 | values. This includes disabled expressions, which are marked as such. | |
7376 | It also includes expressions which would not be displayed right now | |
7377 | because they refer to automatic variables not currently available. | |
7378 | @end table | |
7379 | ||
15387254 | 7380 | @cindex display disabled out of scope |
c906108c SS |
7381 | If a display expression refers to local variables, then it does not make |
7382 | sense outside the lexical context for which it was set up. Such an | |
7383 | expression is disabled when execution enters a context where one of its | |
7384 | variables is not defined. For example, if you give the command | |
7385 | @code{display last_char} while inside a function with an argument | |
7386 | @code{last_char}, @value{GDBN} displays this argument while your program | |
7387 | continues to stop inside that function. When it stops elsewhere---where | |
7388 | there is no variable @code{last_char}---the display is disabled | |
7389 | automatically. The next time your program stops where @code{last_char} | |
7390 | is meaningful, you can enable the display expression once again. | |
7391 | ||
6d2ebf8b | 7392 | @node Print Settings |
79a6e687 | 7393 | @section Print Settings |
c906108c SS |
7394 | |
7395 | @cindex format options | |
7396 | @cindex print settings | |
7397 | @value{GDBN} provides the following ways to control how arrays, structures, | |
7398 | and symbols are printed. | |
7399 | ||
7400 | @noindent | |
7401 | These settings are useful for debugging programs in any language: | |
7402 | ||
7403 | @table @code | |
4644b6e3 | 7404 | @kindex set print |
c906108c SS |
7405 | @item set print address |
7406 | @itemx set print address on | |
4644b6e3 | 7407 | @cindex print/don't print memory addresses |
c906108c SS |
7408 | @value{GDBN} prints memory addresses showing the location of stack |
7409 | traces, structure values, pointer values, breakpoints, and so forth, | |
7410 | even when it also displays the contents of those addresses. The default | |
7411 | is @code{on}. For example, this is what a stack frame display looks like with | |
7412 | @code{set print address on}: | |
7413 | ||
7414 | @smallexample | |
7415 | @group | |
7416 | (@value{GDBP}) f | |
7417 | #0 set_quotes (lq=0x34c78 "<<", rq=0x34c88 ">>") | |
7418 | at input.c:530 | |
7419 | 530 if (lquote != def_lquote) | |
7420 | @end group | |
7421 | @end smallexample | |
7422 | ||
7423 | @item set print address off | |
7424 | Do not print addresses when displaying their contents. For example, | |
7425 | this is the same stack frame displayed with @code{set print address off}: | |
7426 | ||
7427 | @smallexample | |
7428 | @group | |
7429 | (@value{GDBP}) set print addr off | |
7430 | (@value{GDBP}) f | |
7431 | #0 set_quotes (lq="<<", rq=">>") at input.c:530 | |
7432 | 530 if (lquote != def_lquote) | |
7433 | @end group | |
7434 | @end smallexample | |
7435 | ||
7436 | You can use @samp{set print address off} to eliminate all machine | |
7437 | dependent displays from the @value{GDBN} interface. For example, with | |
7438 | @code{print address off}, you should get the same text for backtraces on | |
7439 | all machines---whether or not they involve pointer arguments. | |
7440 | ||
4644b6e3 | 7441 | @kindex show print |
c906108c SS |
7442 | @item show print address |
7443 | Show whether or not addresses are to be printed. | |
7444 | @end table | |
7445 | ||
7446 | When @value{GDBN} prints a symbolic address, it normally prints the | |
7447 | closest earlier symbol plus an offset. If that symbol does not uniquely | |
7448 | identify the address (for example, it is a name whose scope is a single | |
7449 | source file), you may need to clarify. One way to do this is with | |
7450 | @code{info line}, for example @samp{info line *0x4537}. Alternately, | |
7451 | you can set @value{GDBN} to print the source file and line number when | |
7452 | it prints a symbolic address: | |
7453 | ||
7454 | @table @code | |
c906108c | 7455 | @item set print symbol-filename on |
9c16f35a EZ |
7456 | @cindex source file and line of a symbol |
7457 | @cindex symbol, source file and line | |
c906108c SS |
7458 | Tell @value{GDBN} to print the source file name and line number of a |
7459 | symbol in the symbolic form of an address. | |
7460 | ||
7461 | @item set print symbol-filename off | |
7462 | Do not print source file name and line number of a symbol. This is the | |
7463 | default. | |
7464 | ||
c906108c SS |
7465 | @item show print symbol-filename |
7466 | Show whether or not @value{GDBN} will print the source file name and | |
7467 | line number of a symbol in the symbolic form of an address. | |
7468 | @end table | |
7469 | ||
7470 | Another situation where it is helpful to show symbol filenames and line | |
7471 | numbers is when disassembling code; @value{GDBN} shows you the line | |
7472 | number and source file that corresponds to each instruction. | |
7473 | ||
7474 | Also, you may wish to see the symbolic form only if the address being | |
7475 | printed is reasonably close to the closest earlier symbol: | |
7476 | ||
7477 | @table @code | |
c906108c | 7478 | @item set print max-symbolic-offset @var{max-offset} |
4644b6e3 | 7479 | @cindex maximum value for offset of closest symbol |
c906108c SS |
7480 | Tell @value{GDBN} to only display the symbolic form of an address if the |
7481 | offset between the closest earlier symbol and the address is less than | |
5d161b24 | 7482 | @var{max-offset}. The default is 0, which tells @value{GDBN} |
c906108c SS |
7483 | to always print the symbolic form of an address if any symbol precedes it. |
7484 | ||
c906108c SS |
7485 | @item show print max-symbolic-offset |
7486 | Ask how large the maximum offset is that @value{GDBN} prints in a | |
7487 | symbolic address. | |
7488 | @end table | |
7489 | ||
7490 | @cindex wild pointer, interpreting | |
7491 | @cindex pointer, finding referent | |
7492 | If you have a pointer and you are not sure where it points, try | |
7493 | @samp{set print symbol-filename on}. Then you can determine the name | |
7494 | and source file location of the variable where it points, using | |
7495 | @samp{p/a @var{pointer}}. This interprets the address in symbolic form. | |
7496 | For example, here @value{GDBN} shows that a variable @code{ptt} points | |
7497 | at another variable @code{t}, defined in @file{hi2.c}: | |
7498 | ||
474c8240 | 7499 | @smallexample |
c906108c SS |
7500 | (@value{GDBP}) set print symbol-filename on |
7501 | (@value{GDBP}) p/a ptt | |
7502 | $4 = 0xe008 <t in hi2.c> | |
474c8240 | 7503 | @end smallexample |
c906108c SS |
7504 | |
7505 | @quotation | |
7506 | @emph{Warning:} For pointers that point to a local variable, @samp{p/a} | |
7507 | does not show the symbol name and filename of the referent, even with | |
7508 | the appropriate @code{set print} options turned on. | |
7509 | @end quotation | |
7510 | ||
7511 | Other settings control how different kinds of objects are printed: | |
7512 | ||
7513 | @table @code | |
c906108c SS |
7514 | @item set print array |
7515 | @itemx set print array on | |
4644b6e3 | 7516 | @cindex pretty print arrays |
c906108c SS |
7517 | Pretty print arrays. This format is more convenient to read, |
7518 | but uses more space. The default is off. | |
7519 | ||
7520 | @item set print array off | |
7521 | Return to compressed format for arrays. | |
7522 | ||
c906108c SS |
7523 | @item show print array |
7524 | Show whether compressed or pretty format is selected for displaying | |
7525 | arrays. | |
7526 | ||
3c9c013a JB |
7527 | @cindex print array indexes |
7528 | @item set print array-indexes | |
7529 | @itemx set print array-indexes on | |
7530 | Print the index of each element when displaying arrays. May be more | |
7531 | convenient to locate a given element in the array or quickly find the | |
7532 | index of a given element in that printed array. The default is off. | |
7533 | ||
7534 | @item set print array-indexes off | |
7535 | Stop printing element indexes when displaying arrays. | |
7536 | ||
7537 | @item show print array-indexes | |
7538 | Show whether the index of each element is printed when displaying | |
7539 | arrays. | |
7540 | ||
c906108c | 7541 | @item set print elements @var{number-of-elements} |
4644b6e3 | 7542 | @cindex number of array elements to print |
9c16f35a | 7543 | @cindex limit on number of printed array elements |
c906108c SS |
7544 | Set a limit on how many elements of an array @value{GDBN} will print. |
7545 | If @value{GDBN} is printing a large array, it stops printing after it has | |
7546 | printed the number of elements set by the @code{set print elements} command. | |
7547 | This limit also applies to the display of strings. | |
d4f3574e | 7548 | When @value{GDBN} starts, this limit is set to 200. |
c906108c SS |
7549 | Setting @var{number-of-elements} to zero means that the printing is unlimited. |
7550 | ||
c906108c SS |
7551 | @item show print elements |
7552 | Display the number of elements of a large array that @value{GDBN} will print. | |
7553 | If the number is 0, then the printing is unlimited. | |
7554 | ||
b4740add | 7555 | @item set print frame-arguments @var{value} |
a0381d3a | 7556 | @kindex set print frame-arguments |
b4740add JB |
7557 | @cindex printing frame argument values |
7558 | @cindex print all frame argument values | |
7559 | @cindex print frame argument values for scalars only | |
7560 | @cindex do not print frame argument values | |
7561 | This command allows to control how the values of arguments are printed | |
7562 | when the debugger prints a frame (@pxref{Frames}). The possible | |
7563 | values are: | |
7564 | ||
7565 | @table @code | |
7566 | @item all | |
4f5376b2 | 7567 | The values of all arguments are printed. |
b4740add JB |
7568 | |
7569 | @item scalars | |
7570 | Print the value of an argument only if it is a scalar. The value of more | |
7571 | complex arguments such as arrays, structures, unions, etc, is replaced | |
4f5376b2 JB |
7572 | by @code{@dots{}}. This is the default. Here is an example where |
7573 | only scalar arguments are shown: | |
b4740add JB |
7574 | |
7575 | @smallexample | |
7576 | #1 0x08048361 in call_me (i=3, s=@dots{}, ss=0xbf8d508c, u=@dots{}, e=green) | |
7577 | at frame-args.c:23 | |
7578 | @end smallexample | |
7579 | ||
7580 | @item none | |
7581 | None of the argument values are printed. Instead, the value of each argument | |
7582 | is replaced by @code{@dots{}}. In this case, the example above now becomes: | |
7583 | ||
7584 | @smallexample | |
7585 | #1 0x08048361 in call_me (i=@dots{}, s=@dots{}, ss=@dots{}, u=@dots{}, e=@dots{}) | |
7586 | at frame-args.c:23 | |
7587 | @end smallexample | |
7588 | @end table | |
7589 | ||
4f5376b2 JB |
7590 | By default, only scalar arguments are printed. This command can be used |
7591 | to configure the debugger to print the value of all arguments, regardless | |
7592 | of their type. However, it is often advantageous to not print the value | |
7593 | of more complex parameters. For instance, it reduces the amount of | |
7594 | information printed in each frame, making the backtrace more readable. | |
7595 | Also, it improves performance when displaying Ada frames, because | |
7596 | the computation of large arguments can sometimes be CPU-intensive, | |
7597 | especially in large applications. Setting @code{print frame-arguments} | |
7598 | to @code{scalars} (the default) or @code{none} avoids this computation, | |
7599 | thus speeding up the display of each Ada frame. | |
b4740add JB |
7600 | |
7601 | @item show print frame-arguments | |
7602 | Show how the value of arguments should be displayed when printing a frame. | |
7603 | ||
9c16f35a EZ |
7604 | @item set print repeats |
7605 | @cindex repeated array elements | |
7606 | Set the threshold for suppressing display of repeated array | |
d3e8051b | 7607 | elements. When the number of consecutive identical elements of an |
9c16f35a EZ |
7608 | array exceeds the threshold, @value{GDBN} prints the string |
7609 | @code{"<repeats @var{n} times>"}, where @var{n} is the number of | |
7610 | identical repetitions, instead of displaying the identical elements | |
7611 | themselves. Setting the threshold to zero will cause all elements to | |
7612 | be individually printed. The default threshold is 10. | |
7613 | ||
7614 | @item show print repeats | |
7615 | Display the current threshold for printing repeated identical | |
7616 | elements. | |
7617 | ||
c906108c | 7618 | @item set print null-stop |
4644b6e3 | 7619 | @cindex @sc{null} elements in arrays |
c906108c | 7620 | Cause @value{GDBN} to stop printing the characters of an array when the first |
d4f3574e | 7621 | @sc{null} is encountered. This is useful when large arrays actually |
c906108c | 7622 | contain only short strings. |
d4f3574e | 7623 | The default is off. |
c906108c | 7624 | |
9c16f35a EZ |
7625 | @item show print null-stop |
7626 | Show whether @value{GDBN} stops printing an array on the first | |
7627 | @sc{null} character. | |
7628 | ||
c906108c | 7629 | @item set print pretty on |
9c16f35a EZ |
7630 | @cindex print structures in indented form |
7631 | @cindex indentation in structure display | |
5d161b24 | 7632 | Cause @value{GDBN} to print structures in an indented format with one member |
c906108c SS |
7633 | per line, like this: |
7634 | ||
7635 | @smallexample | |
7636 | @group | |
7637 | $1 = @{ | |
7638 | next = 0x0, | |
7639 | flags = @{ | |
7640 | sweet = 1, | |
7641 | sour = 1 | |
7642 | @}, | |
7643 | meat = 0x54 "Pork" | |
7644 | @} | |
7645 | @end group | |
7646 | @end smallexample | |
7647 | ||
7648 | @item set print pretty off | |
7649 | Cause @value{GDBN} to print structures in a compact format, like this: | |
7650 | ||
7651 | @smallexample | |
7652 | @group | |
7653 | $1 = @{next = 0x0, flags = @{sweet = 1, sour = 1@}, \ | |
7654 | meat = 0x54 "Pork"@} | |
7655 | @end group | |
7656 | @end smallexample | |
7657 | ||
7658 | @noindent | |
7659 | This is the default format. | |
7660 | ||
c906108c SS |
7661 | @item show print pretty |
7662 | Show which format @value{GDBN} is using to print structures. | |
7663 | ||
c906108c | 7664 | @item set print sevenbit-strings on |
4644b6e3 EZ |
7665 | @cindex eight-bit characters in strings |
7666 | @cindex octal escapes in strings | |
c906108c SS |
7667 | Print using only seven-bit characters; if this option is set, |
7668 | @value{GDBN} displays any eight-bit characters (in strings or | |
7669 | character values) using the notation @code{\}@var{nnn}. This setting is | |
7670 | best if you are working in English (@sc{ascii}) and you use the | |
7671 | high-order bit of characters as a marker or ``meta'' bit. | |
7672 | ||
7673 | @item set print sevenbit-strings off | |
7674 | Print full eight-bit characters. This allows the use of more | |
7675 | international character sets, and is the default. | |
7676 | ||
c906108c SS |
7677 | @item show print sevenbit-strings |
7678 | Show whether or not @value{GDBN} is printing only seven-bit characters. | |
7679 | ||
c906108c | 7680 | @item set print union on |
4644b6e3 | 7681 | @cindex unions in structures, printing |
9c16f35a EZ |
7682 | Tell @value{GDBN} to print unions which are contained in structures |
7683 | and other unions. This is the default setting. | |
c906108c SS |
7684 | |
7685 | @item set print union off | |
9c16f35a EZ |
7686 | Tell @value{GDBN} not to print unions which are contained in |
7687 | structures and other unions. @value{GDBN} will print @code{"@{...@}"} | |
7688 | instead. | |
c906108c | 7689 | |
c906108c SS |
7690 | @item show print union |
7691 | Ask @value{GDBN} whether or not it will print unions which are contained in | |
9c16f35a | 7692 | structures and other unions. |
c906108c SS |
7693 | |
7694 | For example, given the declarations | |
7695 | ||
7696 | @smallexample | |
7697 | typedef enum @{Tree, Bug@} Species; | |
7698 | typedef enum @{Big_tree, Acorn, Seedling@} Tree_forms; | |
5d161b24 | 7699 | typedef enum @{Caterpillar, Cocoon, Butterfly@} |
c906108c SS |
7700 | Bug_forms; |
7701 | ||
7702 | struct thing @{ | |
7703 | Species it; | |
7704 | union @{ | |
7705 | Tree_forms tree; | |
7706 | Bug_forms bug; | |
7707 | @} form; | |
7708 | @}; | |
7709 | ||
7710 | struct thing foo = @{Tree, @{Acorn@}@}; | |
7711 | @end smallexample | |
7712 | ||
7713 | @noindent | |
7714 | with @code{set print union on} in effect @samp{p foo} would print | |
7715 | ||
7716 | @smallexample | |
7717 | $1 = @{it = Tree, form = @{tree = Acorn, bug = Cocoon@}@} | |
7718 | @end smallexample | |
7719 | ||
7720 | @noindent | |
7721 | and with @code{set print union off} in effect it would print | |
7722 | ||
7723 | @smallexample | |
7724 | $1 = @{it = Tree, form = @{...@}@} | |
7725 | @end smallexample | |
9c16f35a EZ |
7726 | |
7727 | @noindent | |
7728 | @code{set print union} affects programs written in C-like languages | |
7729 | and in Pascal. | |
c906108c SS |
7730 | @end table |
7731 | ||
c906108c SS |
7732 | @need 1000 |
7733 | @noindent | |
b37052ae | 7734 | These settings are of interest when debugging C@t{++} programs: |
c906108c SS |
7735 | |
7736 | @table @code | |
4644b6e3 | 7737 | @cindex demangling C@t{++} names |
c906108c SS |
7738 | @item set print demangle |
7739 | @itemx set print demangle on | |
b37052ae | 7740 | Print C@t{++} names in their source form rather than in the encoded |
c906108c | 7741 | (``mangled'') form passed to the assembler and linker for type-safe |
d4f3574e | 7742 | linkage. The default is on. |
c906108c | 7743 | |
c906108c | 7744 | @item show print demangle |
b37052ae | 7745 | Show whether C@t{++} names are printed in mangled or demangled form. |
c906108c | 7746 | |
c906108c SS |
7747 | @item set print asm-demangle |
7748 | @itemx set print asm-demangle on | |
b37052ae | 7749 | Print C@t{++} names in their source form rather than their mangled form, even |
c906108c SS |
7750 | in assembler code printouts such as instruction disassemblies. |
7751 | The default is off. | |
7752 | ||
c906108c | 7753 | @item show print asm-demangle |
b37052ae | 7754 | Show whether C@t{++} names in assembly listings are printed in mangled |
c906108c SS |
7755 | or demangled form. |
7756 | ||
b37052ae EZ |
7757 | @cindex C@t{++} symbol decoding style |
7758 | @cindex symbol decoding style, C@t{++} | |
a8f24a35 | 7759 | @kindex set demangle-style |
c906108c SS |
7760 | @item set demangle-style @var{style} |
7761 | Choose among several encoding schemes used by different compilers to | |
b37052ae | 7762 | represent C@t{++} names. The choices for @var{style} are currently: |
c906108c SS |
7763 | |
7764 | @table @code | |
7765 | @item auto | |
7766 | Allow @value{GDBN} to choose a decoding style by inspecting your program. | |
7767 | ||
7768 | @item gnu | |
b37052ae | 7769 | Decode based on the @sc{gnu} C@t{++} compiler (@code{g++}) encoding algorithm. |
c906108c | 7770 | This is the default. |
c906108c SS |
7771 | |
7772 | @item hp | |
b37052ae | 7773 | Decode based on the HP ANSI C@t{++} (@code{aCC}) encoding algorithm. |
c906108c SS |
7774 | |
7775 | @item lucid | |
b37052ae | 7776 | Decode based on the Lucid C@t{++} compiler (@code{lcc}) encoding algorithm. |
c906108c SS |
7777 | |
7778 | @item arm | |
b37052ae | 7779 | Decode using the algorithm in the @cite{C@t{++} Annotated Reference Manual}. |
c906108c SS |
7780 | @strong{Warning:} this setting alone is not sufficient to allow |
7781 | debugging @code{cfront}-generated executables. @value{GDBN} would | |
7782 | require further enhancement to permit that. | |
7783 | ||
7784 | @end table | |
7785 | If you omit @var{style}, you will see a list of possible formats. | |
7786 | ||
c906108c | 7787 | @item show demangle-style |
b37052ae | 7788 | Display the encoding style currently in use for decoding C@t{++} symbols. |
c906108c | 7789 | |
c906108c SS |
7790 | @item set print object |
7791 | @itemx set print object on | |
4644b6e3 | 7792 | @cindex derived type of an object, printing |
9c16f35a | 7793 | @cindex display derived types |
c906108c SS |
7794 | When displaying a pointer to an object, identify the @emph{actual} |
7795 | (derived) type of the object rather than the @emph{declared} type, using | |
7796 | the virtual function table. | |
7797 | ||
7798 | @item set print object off | |
7799 | Display only the declared type of objects, without reference to the | |
7800 | virtual function table. This is the default setting. | |
7801 | ||
c906108c SS |
7802 | @item show print object |
7803 | Show whether actual, or declared, object types are displayed. | |
7804 | ||
c906108c SS |
7805 | @item set print static-members |
7806 | @itemx set print static-members on | |
4644b6e3 | 7807 | @cindex static members of C@t{++} objects |
b37052ae | 7808 | Print static members when displaying a C@t{++} object. The default is on. |
c906108c SS |
7809 | |
7810 | @item set print static-members off | |
b37052ae | 7811 | Do not print static members when displaying a C@t{++} object. |
c906108c | 7812 | |
c906108c | 7813 | @item show print static-members |
9c16f35a EZ |
7814 | Show whether C@t{++} static members are printed or not. |
7815 | ||
7816 | @item set print pascal_static-members | |
7817 | @itemx set print pascal_static-members on | |
d3e8051b EZ |
7818 | @cindex static members of Pascal objects |
7819 | @cindex Pascal objects, static members display | |
9c16f35a EZ |
7820 | Print static members when displaying a Pascal object. The default is on. |
7821 | ||
7822 | @item set print pascal_static-members off | |
7823 | Do not print static members when displaying a Pascal object. | |
7824 | ||
7825 | @item show print pascal_static-members | |
7826 | Show whether Pascal static members are printed or not. | |
c906108c SS |
7827 | |
7828 | @c These don't work with HP ANSI C++ yet. | |
c906108c SS |
7829 | @item set print vtbl |
7830 | @itemx set print vtbl on | |
4644b6e3 | 7831 | @cindex pretty print C@t{++} virtual function tables |
9c16f35a EZ |
7832 | @cindex virtual functions (C@t{++}) display |
7833 | @cindex VTBL display | |
b37052ae | 7834 | Pretty print C@t{++} virtual function tables. The default is off. |
c906108c | 7835 | (The @code{vtbl} commands do not work on programs compiled with the HP |
b37052ae | 7836 | ANSI C@t{++} compiler (@code{aCC}).) |
c906108c SS |
7837 | |
7838 | @item set print vtbl off | |
b37052ae | 7839 | Do not pretty print C@t{++} virtual function tables. |
c906108c | 7840 | |
c906108c | 7841 | @item show print vtbl |
b37052ae | 7842 | Show whether C@t{++} virtual function tables are pretty printed, or not. |
c906108c | 7843 | @end table |
c906108c | 7844 | |
6d2ebf8b | 7845 | @node Value History |
79a6e687 | 7846 | @section Value History |
c906108c SS |
7847 | |
7848 | @cindex value history | |
9c16f35a | 7849 | @cindex history of values printed by @value{GDBN} |
5d161b24 DB |
7850 | Values printed by the @code{print} command are saved in the @value{GDBN} |
7851 | @dfn{value history}. This allows you to refer to them in other expressions. | |
7852 | Values are kept until the symbol table is re-read or discarded | |
7853 | (for example with the @code{file} or @code{symbol-file} commands). | |
7854 | When the symbol table changes, the value history is discarded, | |
7855 | since the values may contain pointers back to the types defined in the | |
c906108c SS |
7856 | symbol table. |
7857 | ||
7858 | @cindex @code{$} | |
7859 | @cindex @code{$$} | |
7860 | @cindex history number | |
7861 | The values printed are given @dfn{history numbers} by which you can | |
7862 | refer to them. These are successive integers starting with one. | |
7863 | @code{print} shows you the history number assigned to a value by | |
7864 | printing @samp{$@var{num} = } before the value; here @var{num} is the | |
7865 | history number. | |
7866 | ||
7867 | To refer to any previous value, use @samp{$} followed by the value's | |
7868 | history number. The way @code{print} labels its output is designed to | |
7869 | remind you of this. Just @code{$} refers to the most recent value in | |
7870 | the history, and @code{$$} refers to the value before that. | |
7871 | @code{$$@var{n}} refers to the @var{n}th value from the end; @code{$$2} | |
7872 | is the value just prior to @code{$$}, @code{$$1} is equivalent to | |
7873 | @code{$$}, and @code{$$0} is equivalent to @code{$}. | |
7874 | ||
7875 | For example, suppose you have just printed a pointer to a structure and | |
7876 | want to see the contents of the structure. It suffices to type | |
7877 | ||
474c8240 | 7878 | @smallexample |
c906108c | 7879 | p *$ |
474c8240 | 7880 | @end smallexample |
c906108c SS |
7881 | |
7882 | If you have a chain of structures where the component @code{next} points | |
7883 | to the next one, you can print the contents of the next one with this: | |
7884 | ||
474c8240 | 7885 | @smallexample |
c906108c | 7886 | p *$.next |
474c8240 | 7887 | @end smallexample |
c906108c SS |
7888 | |
7889 | @noindent | |
7890 | You can print successive links in the chain by repeating this | |
7891 | command---which you can do by just typing @key{RET}. | |
7892 | ||
7893 | Note that the history records values, not expressions. If the value of | |
7894 | @code{x} is 4 and you type these commands: | |
7895 | ||
474c8240 | 7896 | @smallexample |
c906108c SS |
7897 | print x |
7898 | set x=5 | |
474c8240 | 7899 | @end smallexample |
c906108c SS |
7900 | |
7901 | @noindent | |
7902 | then the value recorded in the value history by the @code{print} command | |
7903 | remains 4 even though the value of @code{x} has changed. | |
7904 | ||
7905 | @table @code | |
7906 | @kindex show values | |
7907 | @item show values | |
7908 | Print the last ten values in the value history, with their item numbers. | |
7909 | This is like @samp{p@ $$9} repeated ten times, except that @code{show | |
7910 | values} does not change the history. | |
7911 | ||
7912 | @item show values @var{n} | |
7913 | Print ten history values centered on history item number @var{n}. | |
7914 | ||
7915 | @item show values + | |
7916 | Print ten history values just after the values last printed. If no more | |
7917 | values are available, @code{show values +} produces no display. | |
7918 | @end table | |
7919 | ||
7920 | Pressing @key{RET} to repeat @code{show values @var{n}} has exactly the | |
7921 | same effect as @samp{show values +}. | |
7922 | ||
6d2ebf8b | 7923 | @node Convenience Vars |
79a6e687 | 7924 | @section Convenience Variables |
c906108c SS |
7925 | |
7926 | @cindex convenience variables | |
9c16f35a | 7927 | @cindex user-defined variables |
c906108c SS |
7928 | @value{GDBN} provides @dfn{convenience variables} that you can use within |
7929 | @value{GDBN} to hold on to a value and refer to it later. These variables | |
7930 | exist entirely within @value{GDBN}; they are not part of your program, and | |
7931 | setting a convenience variable has no direct effect on further execution | |
7932 | of your program. That is why you can use them freely. | |
7933 | ||
7934 | Convenience variables are prefixed with @samp{$}. Any name preceded by | |
7935 | @samp{$} can be used for a convenience variable, unless it is one of | |
d4f3574e | 7936 | the predefined machine-specific register names (@pxref{Registers, ,Registers}). |
c906108c | 7937 | (Value history references, in contrast, are @emph{numbers} preceded |
79a6e687 | 7938 | by @samp{$}. @xref{Value History, ,Value History}.) |
c906108c SS |
7939 | |
7940 | You can save a value in a convenience variable with an assignment | |
7941 | expression, just as you would set a variable in your program. | |
7942 | For example: | |
7943 | ||
474c8240 | 7944 | @smallexample |
c906108c | 7945 | set $foo = *object_ptr |
474c8240 | 7946 | @end smallexample |
c906108c SS |
7947 | |
7948 | @noindent | |
7949 | would save in @code{$foo} the value contained in the object pointed to by | |
7950 | @code{object_ptr}. | |
7951 | ||
7952 | Using a convenience variable for the first time creates it, but its | |
7953 | value is @code{void} until you assign a new value. You can alter the | |
7954 | value with another assignment at any time. | |
7955 | ||
7956 | Convenience variables have no fixed types. You can assign a convenience | |
7957 | variable any type of value, including structures and arrays, even if | |
7958 | that variable already has a value of a different type. The convenience | |
7959 | variable, when used as an expression, has the type of its current value. | |
7960 | ||
7961 | @table @code | |
7962 | @kindex show convenience | |
9c16f35a | 7963 | @cindex show all user variables |
c906108c SS |
7964 | @item show convenience |
7965 | Print a list of convenience variables used so far, and their values. | |
d4f3574e | 7966 | Abbreviated @code{show conv}. |
53e5f3cf AS |
7967 | |
7968 | @kindex init-if-undefined | |
7969 | @cindex convenience variables, initializing | |
7970 | @item init-if-undefined $@var{variable} = @var{expression} | |
7971 | Set a convenience variable if it has not already been set. This is useful | |
7972 | for user-defined commands that keep some state. It is similar, in concept, | |
7973 | to using local static variables with initializers in C (except that | |
7974 | convenience variables are global). It can also be used to allow users to | |
7975 | override default values used in a command script. | |
7976 | ||
7977 | If the variable is already defined then the expression is not evaluated so | |
7978 | any side-effects do not occur. | |
c906108c SS |
7979 | @end table |
7980 | ||
7981 | One of the ways to use a convenience variable is as a counter to be | |
7982 | incremented or a pointer to be advanced. For example, to print | |
7983 | a field from successive elements of an array of structures: | |
7984 | ||
474c8240 | 7985 | @smallexample |
c906108c SS |
7986 | set $i = 0 |
7987 | print bar[$i++]->contents | |
474c8240 | 7988 | @end smallexample |
c906108c | 7989 | |
d4f3574e SS |
7990 | @noindent |
7991 | Repeat that command by typing @key{RET}. | |
c906108c SS |
7992 | |
7993 | Some convenience variables are created automatically by @value{GDBN} and given | |
7994 | values likely to be useful. | |
7995 | ||
7996 | @table @code | |
41afff9a | 7997 | @vindex $_@r{, convenience variable} |
c906108c SS |
7998 | @item $_ |
7999 | The variable @code{$_} is automatically set by the @code{x} command to | |
79a6e687 | 8000 | the last address examined (@pxref{Memory, ,Examining Memory}). Other |
c906108c SS |
8001 | commands which provide a default address for @code{x} to examine also |
8002 | set @code{$_} to that address; these commands include @code{info line} | |
8003 | and @code{info breakpoint}. The type of @code{$_} is @code{void *} | |
8004 | except when set by the @code{x} command, in which case it is a pointer | |
8005 | to the type of @code{$__}. | |
8006 | ||
41afff9a | 8007 | @vindex $__@r{, convenience variable} |
c906108c SS |
8008 | @item $__ |
8009 | The variable @code{$__} is automatically set by the @code{x} command | |
8010 | to the value found in the last address examined. Its type is chosen | |
8011 | to match the format in which the data was printed. | |
8012 | ||
8013 | @item $_exitcode | |
41afff9a | 8014 | @vindex $_exitcode@r{, convenience variable} |
c906108c SS |
8015 | The variable @code{$_exitcode} is automatically set to the exit code when |
8016 | the program being debugged terminates. | |
4aa995e1 PA |
8017 | |
8018 | @item $_siginfo | |
8019 | @vindex $_siginfo@r{, convenience variable} | |
ec7e75e7 PP |
8020 | The variable @code{$_siginfo} contains extra signal information |
8021 | (@pxref{extra signal information}). Note that @code{$_siginfo} | |
8022 | could be empty, if the application has not yet received any signals. | |
8023 | For example, it will be empty before you execute the @code{run} command. | |
c906108c SS |
8024 | @end table |
8025 | ||
53a5351d JM |
8026 | On HP-UX systems, if you refer to a function or variable name that |
8027 | begins with a dollar sign, @value{GDBN} searches for a user or system | |
8028 | name first, before it searches for a convenience variable. | |
c906108c | 8029 | |
bc3b79fd TJB |
8030 | @cindex convenience functions |
8031 | @value{GDBN} also supplies some @dfn{convenience functions}. These | |
8032 | have a syntax similar to convenience variables. A convenience | |
8033 | function can be used in an expression just like an ordinary function; | |
8034 | however, a convenience function is implemented internally to | |
8035 | @value{GDBN}. | |
8036 | ||
8037 | @table @code | |
8038 | @item help function | |
8039 | @kindex help function | |
8040 | @cindex show all convenience functions | |
8041 | Print a list of all convenience functions. | |
8042 | @end table | |
8043 | ||
6d2ebf8b | 8044 | @node Registers |
c906108c SS |
8045 | @section Registers |
8046 | ||
8047 | @cindex registers | |
8048 | You can refer to machine register contents, in expressions, as variables | |
8049 | with names starting with @samp{$}. The names of registers are different | |
8050 | for each machine; use @code{info registers} to see the names used on | |
8051 | your machine. | |
8052 | ||
8053 | @table @code | |
8054 | @kindex info registers | |
8055 | @item info registers | |
8056 | Print the names and values of all registers except floating-point | |
c85508ee | 8057 | and vector registers (in the selected stack frame). |
c906108c SS |
8058 | |
8059 | @kindex info all-registers | |
8060 | @cindex floating point registers | |
8061 | @item info all-registers | |
8062 | Print the names and values of all registers, including floating-point | |
c85508ee | 8063 | and vector registers (in the selected stack frame). |
c906108c SS |
8064 | |
8065 | @item info registers @var{regname} @dots{} | |
8066 | Print the @dfn{relativized} value of each specified register @var{regname}. | |
5d161b24 DB |
8067 | As discussed in detail below, register values are normally relative to |
8068 | the selected stack frame. @var{regname} may be any register name valid on | |
c906108c SS |
8069 | the machine you are using, with or without the initial @samp{$}. |
8070 | @end table | |
8071 | ||
e09f16f9 EZ |
8072 | @cindex stack pointer register |
8073 | @cindex program counter register | |
8074 | @cindex process status register | |
8075 | @cindex frame pointer register | |
8076 | @cindex standard registers | |
c906108c SS |
8077 | @value{GDBN} has four ``standard'' register names that are available (in |
8078 | expressions) on most machines---whenever they do not conflict with an | |
8079 | architecture's canonical mnemonics for registers. The register names | |
8080 | @code{$pc} and @code{$sp} are used for the program counter register and | |
8081 | the stack pointer. @code{$fp} is used for a register that contains a | |
8082 | pointer to the current stack frame, and @code{$ps} is used for a | |
8083 | register that contains the processor status. For example, | |
8084 | you could print the program counter in hex with | |
8085 | ||
474c8240 | 8086 | @smallexample |
c906108c | 8087 | p/x $pc |
474c8240 | 8088 | @end smallexample |
c906108c SS |
8089 | |
8090 | @noindent | |
8091 | or print the instruction to be executed next with | |
8092 | ||
474c8240 | 8093 | @smallexample |
c906108c | 8094 | x/i $pc |
474c8240 | 8095 | @end smallexample |
c906108c SS |
8096 | |
8097 | @noindent | |
8098 | or add four to the stack pointer@footnote{This is a way of removing | |
8099 | one word from the stack, on machines where stacks grow downward in | |
8100 | memory (most machines, nowadays). This assumes that the innermost | |
8101 | stack frame is selected; setting @code{$sp} is not allowed when other | |
8102 | stack frames are selected. To pop entire frames off the stack, | |
8103 | regardless of machine architecture, use @code{return}; | |
79a6e687 | 8104 | see @ref{Returning, ,Returning from a Function}.} with |
c906108c | 8105 | |
474c8240 | 8106 | @smallexample |
c906108c | 8107 | set $sp += 4 |
474c8240 | 8108 | @end smallexample |
c906108c SS |
8109 | |
8110 | Whenever possible, these four standard register names are available on | |
8111 | your machine even though the machine has different canonical mnemonics, | |
8112 | so long as there is no conflict. The @code{info registers} command | |
8113 | shows the canonical names. For example, on the SPARC, @code{info | |
8114 | registers} displays the processor status register as @code{$psr} but you | |
d4f3574e SS |
8115 | can also refer to it as @code{$ps}; and on x86-based machines @code{$ps} |
8116 | is an alias for the @sc{eflags} register. | |
c906108c SS |
8117 | |
8118 | @value{GDBN} always considers the contents of an ordinary register as an | |
8119 | integer when the register is examined in this way. Some machines have | |
8120 | special registers which can hold nothing but floating point; these | |
8121 | registers are considered to have floating point values. There is no way | |
8122 | to refer to the contents of an ordinary register as floating point value | |
8123 | (although you can @emph{print} it as a floating point value with | |
8124 | @samp{print/f $@var{regname}}). | |
8125 | ||
8126 | Some registers have distinct ``raw'' and ``virtual'' data formats. This | |
8127 | means that the data format in which the register contents are saved by | |
8128 | the operating system is not the same one that your program normally | |
8129 | sees. For example, the registers of the 68881 floating point | |
8130 | coprocessor are always saved in ``extended'' (raw) format, but all C | |
8131 | programs expect to work with ``double'' (virtual) format. In such | |
5d161b24 | 8132 | cases, @value{GDBN} normally works with the virtual format only (the format |
c906108c SS |
8133 | that makes sense for your program), but the @code{info registers} command |
8134 | prints the data in both formats. | |
8135 | ||
36b80e65 EZ |
8136 | @cindex SSE registers (x86) |
8137 | @cindex MMX registers (x86) | |
8138 | Some machines have special registers whose contents can be interpreted | |
8139 | in several different ways. For example, modern x86-based machines | |
8140 | have SSE and MMX registers that can hold several values packed | |
8141 | together in several different formats. @value{GDBN} refers to such | |
8142 | registers in @code{struct} notation: | |
8143 | ||
8144 | @smallexample | |
8145 | (@value{GDBP}) print $xmm1 | |
8146 | $1 = @{ | |
8147 | v4_float = @{0, 3.43859137e-038, 1.54142831e-044, 1.821688e-044@}, | |
8148 | v2_double = @{9.92129282474342e-303, 2.7585945287983262e-313@}, | |
8149 | v16_int8 = "\000\000\000\000\3706;\001\v\000\000\000\r\000\000", | |
8150 | v8_int16 = @{0, 0, 14072, 315, 11, 0, 13, 0@}, | |
8151 | v4_int32 = @{0, 20657912, 11, 13@}, | |
8152 | v2_int64 = @{88725056443645952, 55834574859@}, | |
8153 | uint128 = 0x0000000d0000000b013b36f800000000 | |
8154 | @} | |
8155 | @end smallexample | |
8156 | ||
8157 | @noindent | |
8158 | To set values of such registers, you need to tell @value{GDBN} which | |
8159 | view of the register you wish to change, as if you were assigning | |
8160 | value to a @code{struct} member: | |
8161 | ||
8162 | @smallexample | |
8163 | (@value{GDBP}) set $xmm1.uint128 = 0x000000000000000000000000FFFFFFFF | |
8164 | @end smallexample | |
8165 | ||
c906108c | 8166 | Normally, register values are relative to the selected stack frame |
79a6e687 | 8167 | (@pxref{Selection, ,Selecting a Frame}). This means that you get the |
c906108c SS |
8168 | value that the register would contain if all stack frames farther in |
8169 | were exited and their saved registers restored. In order to see the | |
8170 | true contents of hardware registers, you must select the innermost | |
8171 | frame (with @samp{frame 0}). | |
8172 | ||
8173 | However, @value{GDBN} must deduce where registers are saved, from the machine | |
8174 | code generated by your compiler. If some registers are not saved, or if | |
8175 | @value{GDBN} is unable to locate the saved registers, the selected stack | |
8176 | frame makes no difference. | |
8177 | ||
6d2ebf8b | 8178 | @node Floating Point Hardware |
79a6e687 | 8179 | @section Floating Point Hardware |
c906108c SS |
8180 | @cindex floating point |
8181 | ||
8182 | Depending on the configuration, @value{GDBN} may be able to give | |
8183 | you more information about the status of the floating point hardware. | |
8184 | ||
8185 | @table @code | |
8186 | @kindex info float | |
8187 | @item info float | |
8188 | Display hardware-dependent information about the floating | |
8189 | point unit. The exact contents and layout vary depending on the | |
8190 | floating point chip. Currently, @samp{info float} is supported on | |
8191 | the ARM and x86 machines. | |
8192 | @end table | |
c906108c | 8193 | |
e76f1f2e AC |
8194 | @node Vector Unit |
8195 | @section Vector Unit | |
8196 | @cindex vector unit | |
8197 | ||
8198 | Depending on the configuration, @value{GDBN} may be able to give you | |
8199 | more information about the status of the vector unit. | |
8200 | ||
8201 | @table @code | |
8202 | @kindex info vector | |
8203 | @item info vector | |
8204 | Display information about the vector unit. The exact contents and | |
8205 | layout vary depending on the hardware. | |
8206 | @end table | |
8207 | ||
721c2651 | 8208 | @node OS Information |
79a6e687 | 8209 | @section Operating System Auxiliary Information |
721c2651 EZ |
8210 | @cindex OS information |
8211 | ||
8212 | @value{GDBN} provides interfaces to useful OS facilities that can help | |
8213 | you debug your program. | |
8214 | ||
8215 | @cindex @code{ptrace} system call | |
8216 | @cindex @code{struct user} contents | |
8217 | When @value{GDBN} runs on a @dfn{Posix system} (such as GNU or Unix | |
8218 | machines), it interfaces with the inferior via the @code{ptrace} | |
8219 | system call. The operating system creates a special sata structure, | |
8220 | called @code{struct user}, for this interface. You can use the | |
8221 | command @code{info udot} to display the contents of this data | |
8222 | structure. | |
8223 | ||
8224 | @table @code | |
8225 | @item info udot | |
8226 | @kindex info udot | |
8227 | Display the contents of the @code{struct user} maintained by the OS | |
8228 | kernel for the program being debugged. @value{GDBN} displays the | |
8229 | contents of @code{struct user} as a list of hex numbers, similar to | |
8230 | the @code{examine} command. | |
8231 | @end table | |
8232 | ||
b383017d RM |
8233 | @cindex auxiliary vector |
8234 | @cindex vector, auxiliary | |
b383017d RM |
8235 | Some operating systems supply an @dfn{auxiliary vector} to programs at |
8236 | startup. This is akin to the arguments and environment that you | |
8237 | specify for a program, but contains a system-dependent variety of | |
8238 | binary values that tell system libraries important details about the | |
8239 | hardware, operating system, and process. Each value's purpose is | |
8240 | identified by an integer tag; the meanings are well-known but system-specific. | |
8241 | Depending on the configuration and operating system facilities, | |
9c16f35a EZ |
8242 | @value{GDBN} may be able to show you this information. For remote |
8243 | targets, this functionality may further depend on the remote stub's | |
427c3a89 DJ |
8244 | support of the @samp{qXfer:auxv:read} packet, see |
8245 | @ref{qXfer auxiliary vector read}. | |
b383017d RM |
8246 | |
8247 | @table @code | |
8248 | @kindex info auxv | |
8249 | @item info auxv | |
8250 | Display the auxiliary vector of the inferior, which can be either a | |
e4937fc1 | 8251 | live process or a core dump file. @value{GDBN} prints each tag value |
b383017d RM |
8252 | numerically, and also shows names and text descriptions for recognized |
8253 | tags. Some values in the vector are numbers, some bit masks, and some | |
e4937fc1 | 8254 | pointers to strings or other data. @value{GDBN} displays each value in the |
b383017d RM |
8255 | most appropriate form for a recognized tag, and in hexadecimal for |
8256 | an unrecognized tag. | |
8257 | @end table | |
8258 | ||
07e059b5 VP |
8259 | On some targets, @value{GDBN} can access operating-system-specific information |
8260 | and display it to user, without interpretation. For remote targets, | |
8261 | this functionality depends on the remote stub's support of the | |
8262 | @samp{qXfer:osdata:read} packet, see @ref{qXfer osdata read}. | |
8263 | ||
8264 | @table @code | |
8265 | @kindex info os processes | |
8266 | @item info os processes | |
8267 | Display the list of processes on the target. For each process, | |
8268 | @value{GDBN} prints the process identifier, the name of the user, and | |
8269 | the command corresponding to the process. | |
8270 | @end table | |
721c2651 | 8271 | |
29e57380 | 8272 | @node Memory Region Attributes |
79a6e687 | 8273 | @section Memory Region Attributes |
29e57380 C |
8274 | @cindex memory region attributes |
8275 | ||
b383017d | 8276 | @dfn{Memory region attributes} allow you to describe special handling |
fd79ecee DJ |
8277 | required by regions of your target's memory. @value{GDBN} uses |
8278 | attributes to determine whether to allow certain types of memory | |
8279 | accesses; whether to use specific width accesses; and whether to cache | |
8280 | target memory. By default the description of memory regions is | |
8281 | fetched from the target (if the current target supports this), but the | |
8282 | user can override the fetched regions. | |
29e57380 C |
8283 | |
8284 | Defined memory regions can be individually enabled and disabled. When a | |
8285 | memory region is disabled, @value{GDBN} uses the default attributes when | |
8286 | accessing memory in that region. Similarly, if no memory regions have | |
8287 | been defined, @value{GDBN} uses the default attributes when accessing | |
8288 | all memory. | |
8289 | ||
b383017d | 8290 | When a memory region is defined, it is given a number to identify it; |
29e57380 C |
8291 | to enable, disable, or remove a memory region, you specify that number. |
8292 | ||
8293 | @table @code | |
8294 | @kindex mem | |
bfac230e | 8295 | @item mem @var{lower} @var{upper} @var{attributes}@dots{} |
09d4efe1 EZ |
8296 | Define a memory region bounded by @var{lower} and @var{upper} with |
8297 | attributes @var{attributes}@dots{}, and add it to the list of regions | |
8298 | monitored by @value{GDBN}. Note that @var{upper} == 0 is a special | |
d3e8051b | 8299 | case: it is treated as the target's maximum memory address. |
bfac230e | 8300 | (0xffff on 16 bit targets, 0xffffffff on 32 bit targets, etc.) |
29e57380 | 8301 | |
fd79ecee DJ |
8302 | @item mem auto |
8303 | Discard any user changes to the memory regions and use target-supplied | |
8304 | regions, if available, or no regions if the target does not support. | |
8305 | ||
29e57380 C |
8306 | @kindex delete mem |
8307 | @item delete mem @var{nums}@dots{} | |
09d4efe1 EZ |
8308 | Remove memory regions @var{nums}@dots{} from the list of regions |
8309 | monitored by @value{GDBN}. | |
29e57380 C |
8310 | |
8311 | @kindex disable mem | |
8312 | @item disable mem @var{nums}@dots{} | |
09d4efe1 | 8313 | Disable monitoring of memory regions @var{nums}@dots{}. |
b383017d | 8314 | A disabled memory region is not forgotten. |
29e57380 C |
8315 | It may be enabled again later. |
8316 | ||
8317 | @kindex enable mem | |
8318 | @item enable mem @var{nums}@dots{} | |
09d4efe1 | 8319 | Enable monitoring of memory regions @var{nums}@dots{}. |
29e57380 C |
8320 | |
8321 | @kindex info mem | |
8322 | @item info mem | |
8323 | Print a table of all defined memory regions, with the following columns | |
09d4efe1 | 8324 | for each region: |
29e57380 C |
8325 | |
8326 | @table @emph | |
8327 | @item Memory Region Number | |
8328 | @item Enabled or Disabled. | |
b383017d | 8329 | Enabled memory regions are marked with @samp{y}. |
29e57380 C |
8330 | Disabled memory regions are marked with @samp{n}. |
8331 | ||
8332 | @item Lo Address | |
8333 | The address defining the inclusive lower bound of the memory region. | |
8334 | ||
8335 | @item Hi Address | |
8336 | The address defining the exclusive upper bound of the memory region. | |
8337 | ||
8338 | @item Attributes | |
8339 | The list of attributes set for this memory region. | |
8340 | @end table | |
8341 | @end table | |
8342 | ||
8343 | ||
8344 | @subsection Attributes | |
8345 | ||
b383017d | 8346 | @subsubsection Memory Access Mode |
29e57380 C |
8347 | The access mode attributes set whether @value{GDBN} may make read or |
8348 | write accesses to a memory region. | |
8349 | ||
8350 | While these attributes prevent @value{GDBN} from performing invalid | |
8351 | memory accesses, they do nothing to prevent the target system, I/O DMA, | |
359df76b | 8352 | etc.@: from accessing memory. |
29e57380 C |
8353 | |
8354 | @table @code | |
8355 | @item ro | |
8356 | Memory is read only. | |
8357 | @item wo | |
8358 | Memory is write only. | |
8359 | @item rw | |
6ca652b0 | 8360 | Memory is read/write. This is the default. |
29e57380 C |
8361 | @end table |
8362 | ||
8363 | @subsubsection Memory Access Size | |
d3e8051b | 8364 | The access size attribute tells @value{GDBN} to use specific sized |
29e57380 C |
8365 | accesses in the memory region. Often memory mapped device registers |
8366 | require specific sized accesses. If no access size attribute is | |
8367 | specified, @value{GDBN} may use accesses of any size. | |
8368 | ||
8369 | @table @code | |
8370 | @item 8 | |
8371 | Use 8 bit memory accesses. | |
8372 | @item 16 | |
8373 | Use 16 bit memory accesses. | |
8374 | @item 32 | |
8375 | Use 32 bit memory accesses. | |
8376 | @item 64 | |
8377 | Use 64 bit memory accesses. | |
8378 | @end table | |
8379 | ||
8380 | @c @subsubsection Hardware/Software Breakpoints | |
8381 | @c The hardware/software breakpoint attributes set whether @value{GDBN} | |
8382 | @c will use hardware or software breakpoints for the internal breakpoints | |
8383 | @c used by the step, next, finish, until, etc. commands. | |
8384 | @c | |
8385 | @c @table @code | |
8386 | @c @item hwbreak | |
b383017d | 8387 | @c Always use hardware breakpoints |
29e57380 C |
8388 | @c @item swbreak (default) |
8389 | @c @end table | |
8390 | ||
8391 | @subsubsection Data Cache | |
8392 | The data cache attributes set whether @value{GDBN} will cache target | |
8393 | memory. While this generally improves performance by reducing debug | |
8394 | protocol overhead, it can lead to incorrect results because @value{GDBN} | |
8395 | does not know about volatile variables or memory mapped device | |
8396 | registers. | |
8397 | ||
8398 | @table @code | |
8399 | @item cache | |
b383017d | 8400 | Enable @value{GDBN} to cache target memory. |
6ca652b0 EZ |
8401 | @item nocache |
8402 | Disable @value{GDBN} from caching target memory. This is the default. | |
29e57380 C |
8403 | @end table |
8404 | ||
4b5752d0 VP |
8405 | @subsection Memory Access Checking |
8406 | @value{GDBN} can be instructed to refuse accesses to memory that is | |
8407 | not explicitly described. This can be useful if accessing such | |
8408 | regions has undesired effects for a specific target, or to provide | |
8409 | better error checking. The following commands control this behaviour. | |
8410 | ||
8411 | @table @code | |
8412 | @kindex set mem inaccessible-by-default | |
8413 | @item set mem inaccessible-by-default [on|off] | |
8414 | If @code{on} is specified, make @value{GDBN} treat memory not | |
8415 | explicitly described by the memory ranges as non-existent and refuse accesses | |
8416 | to such memory. The checks are only performed if there's at least one | |
8417 | memory range defined. If @code{off} is specified, make @value{GDBN} | |
8418 | treat the memory not explicitly described by the memory ranges as RAM. | |
56cf5405 | 8419 | The default value is @code{on}. |
4b5752d0 VP |
8420 | @kindex show mem inaccessible-by-default |
8421 | @item show mem inaccessible-by-default | |
8422 | Show the current handling of accesses to unknown memory. | |
8423 | @end table | |
8424 | ||
8425 | ||
29e57380 | 8426 | @c @subsubsection Memory Write Verification |
b383017d | 8427 | @c The memory write verification attributes set whether @value{GDBN} |
29e57380 C |
8428 | @c will re-reads data after each write to verify the write was successful. |
8429 | @c | |
8430 | @c @table @code | |
8431 | @c @item verify | |
8432 | @c @item noverify (default) | |
8433 | @c @end table | |
8434 | ||
16d9dec6 | 8435 | @node Dump/Restore Files |
79a6e687 | 8436 | @section Copy Between Memory and a File |
16d9dec6 MS |
8437 | @cindex dump/restore files |
8438 | @cindex append data to a file | |
8439 | @cindex dump data to a file | |
8440 | @cindex restore data from a file | |
16d9dec6 | 8441 | |
df5215a6 JB |
8442 | You can use the commands @code{dump}, @code{append}, and |
8443 | @code{restore} to copy data between target memory and a file. The | |
8444 | @code{dump} and @code{append} commands write data to a file, and the | |
8445 | @code{restore} command reads data from a file back into the inferior's | |
8446 | memory. Files may be in binary, Motorola S-record, Intel hex, or | |
8447 | Tektronix Hex format; however, @value{GDBN} can only append to binary | |
8448 | files. | |
8449 | ||
8450 | @table @code | |
8451 | ||
8452 | @kindex dump | |
8453 | @item dump @r{[}@var{format}@r{]} memory @var{filename} @var{start_addr} @var{end_addr} | |
8454 | @itemx dump @r{[}@var{format}@r{]} value @var{filename} @var{expr} | |
8455 | Dump the contents of memory from @var{start_addr} to @var{end_addr}, | |
8456 | or the value of @var{expr}, to @var{filename} in the given format. | |
16d9dec6 | 8457 | |
df5215a6 | 8458 | The @var{format} parameter may be any one of: |
16d9dec6 | 8459 | @table @code |
df5215a6 JB |
8460 | @item binary |
8461 | Raw binary form. | |
8462 | @item ihex | |
8463 | Intel hex format. | |
8464 | @item srec | |
8465 | Motorola S-record format. | |
8466 | @item tekhex | |
8467 | Tektronix Hex format. | |
8468 | @end table | |
8469 | ||
8470 | @value{GDBN} uses the same definitions of these formats as the | |
8471 | @sc{gnu} binary utilities, like @samp{objdump} and @samp{objcopy}. If | |
8472 | @var{format} is omitted, @value{GDBN} dumps the data in raw binary | |
8473 | form. | |
8474 | ||
8475 | @kindex append | |
8476 | @item append @r{[}binary@r{]} memory @var{filename} @var{start_addr} @var{end_addr} | |
8477 | @itemx append @r{[}binary@r{]} value @var{filename} @var{expr} | |
8478 | Append the contents of memory from @var{start_addr} to @var{end_addr}, | |
09d4efe1 | 8479 | or the value of @var{expr}, to the file @var{filename}, in raw binary form. |
df5215a6 JB |
8480 | (@value{GDBN} can only append data to files in raw binary form.) |
8481 | ||
8482 | @kindex restore | |
8483 | @item restore @var{filename} @r{[}binary@r{]} @var{bias} @var{start} @var{end} | |
8484 | Restore the contents of file @var{filename} into memory. The | |
8485 | @code{restore} command can automatically recognize any known @sc{bfd} | |
8486 | file format, except for raw binary. To restore a raw binary file you | |
8487 | must specify the optional keyword @code{binary} after the filename. | |
16d9dec6 | 8488 | |
b383017d | 8489 | If @var{bias} is non-zero, its value will be added to the addresses |
16d9dec6 MS |
8490 | contained in the file. Binary files always start at address zero, so |
8491 | they will be restored at address @var{bias}. Other bfd files have | |
8492 | a built-in location; they will be restored at offset @var{bias} | |
8493 | from that location. | |
8494 | ||
8495 | If @var{start} and/or @var{end} are non-zero, then only data between | |
8496 | file offset @var{start} and file offset @var{end} will be restored. | |
b383017d | 8497 | These offsets are relative to the addresses in the file, before |
16d9dec6 MS |
8498 | the @var{bias} argument is applied. |
8499 | ||
8500 | @end table | |
8501 | ||
384ee23f EZ |
8502 | @node Core File Generation |
8503 | @section How to Produce a Core File from Your Program | |
8504 | @cindex dump core from inferior | |
8505 | ||
8506 | A @dfn{core file} or @dfn{core dump} is a file that records the memory | |
8507 | image of a running process and its process status (register values | |
8508 | etc.). Its primary use is post-mortem debugging of a program that | |
8509 | crashed while it ran outside a debugger. A program that crashes | |
8510 | automatically produces a core file, unless this feature is disabled by | |
8511 | the user. @xref{Files}, for information on invoking @value{GDBN} in | |
8512 | the post-mortem debugging mode. | |
8513 | ||
8514 | Occasionally, you may wish to produce a core file of the program you | |
8515 | are debugging in order to preserve a snapshot of its state. | |
8516 | @value{GDBN} has a special command for that. | |
8517 | ||
8518 | @table @code | |
8519 | @kindex gcore | |
8520 | @kindex generate-core-file | |
8521 | @item generate-core-file [@var{file}] | |
8522 | @itemx gcore [@var{file}] | |
8523 | Produce a core dump of the inferior process. The optional argument | |
8524 | @var{file} specifies the file name where to put the core dump. If not | |
8525 | specified, the file name defaults to @file{core.@var{pid}}, where | |
8526 | @var{pid} is the inferior process ID. | |
8527 | ||
8528 | Note that this command is implemented only for some systems (as of | |
8529 | this writing, @sc{gnu}/Linux, FreeBSD, Solaris, Unixware, and S390). | |
8530 | @end table | |
8531 | ||
a0eb71c5 KB |
8532 | @node Character Sets |
8533 | @section Character Sets | |
8534 | @cindex character sets | |
8535 | @cindex charset | |
8536 | @cindex translating between character sets | |
8537 | @cindex host character set | |
8538 | @cindex target character set | |
8539 | ||
8540 | If the program you are debugging uses a different character set to | |
8541 | represent characters and strings than the one @value{GDBN} uses itself, | |
8542 | @value{GDBN} can automatically translate between the character sets for | |
8543 | you. The character set @value{GDBN} uses we call the @dfn{host | |
8544 | character set}; the one the inferior program uses we call the | |
8545 | @dfn{target character set}. | |
8546 | ||
8547 | For example, if you are running @value{GDBN} on a @sc{gnu}/Linux system, which | |
8548 | uses the ISO Latin 1 character set, but you are using @value{GDBN}'s | |
ea35711c | 8549 | remote protocol (@pxref{Remote Debugging}) to debug a program |
a0eb71c5 KB |
8550 | running on an IBM mainframe, which uses the @sc{ebcdic} character set, |
8551 | then the host character set is Latin-1, and the target character set is | |
8552 | @sc{ebcdic}. If you give @value{GDBN} the command @code{set | |
e33d66ec | 8553 | target-charset EBCDIC-US}, then @value{GDBN} translates between |
a0eb71c5 KB |
8554 | @sc{ebcdic} and Latin 1 as you print character or string values, or use |
8555 | character and string literals in expressions. | |
8556 | ||
8557 | @value{GDBN} has no way to automatically recognize which character set | |
8558 | the inferior program uses; you must tell it, using the @code{set | |
8559 | target-charset} command, described below. | |
8560 | ||
8561 | Here are the commands for controlling @value{GDBN}'s character set | |
8562 | support: | |
8563 | ||
8564 | @table @code | |
8565 | @item set target-charset @var{charset} | |
8566 | @kindex set target-charset | |
10af6951 EZ |
8567 | Set the current target character set to @var{charset}. To display the |
8568 | list of supported target character sets, type | |
8569 | @kbd{@w{set target-charset @key{TAB}@key{TAB}}}. | |
a0eb71c5 | 8570 | |
a0eb71c5 KB |
8571 | @item set host-charset @var{charset} |
8572 | @kindex set host-charset | |
8573 | Set the current host character set to @var{charset}. | |
8574 | ||
8575 | By default, @value{GDBN} uses a host character set appropriate to the | |
8576 | system it is running on; you can override that default using the | |
732f6a93 TT |
8577 | @code{set host-charset} command. On some systems, @value{GDBN} cannot |
8578 | automatically determine the appropriate host character set. In this | |
8579 | case, @value{GDBN} uses @samp{UTF-8}. | |
a0eb71c5 KB |
8580 | |
8581 | @value{GDBN} can only use certain character sets as its host character | |
10af6951 EZ |
8582 | set. If you type @kbd{@w{set target-charset @key{TAB}@key{TAB}}}, |
8583 | @value{GDBN} will list the host character sets it supports. | |
a0eb71c5 KB |
8584 | |
8585 | @item set charset @var{charset} | |
8586 | @kindex set charset | |
e33d66ec | 8587 | Set the current host and target character sets to @var{charset}. As |
10af6951 EZ |
8588 | above, if you type @kbd{@w{set charset @key{TAB}@key{TAB}}}, |
8589 | @value{GDBN} will list the names of the character sets that can be used | |
e33d66ec EZ |
8590 | for both host and target. |
8591 | ||
a0eb71c5 | 8592 | @item show charset |
a0eb71c5 | 8593 | @kindex show charset |
10af6951 | 8594 | Show the names of the current host and target character sets. |
e33d66ec | 8595 | |
10af6951 | 8596 | @item show host-charset |
a0eb71c5 | 8597 | @kindex show host-charset |
10af6951 | 8598 | Show the name of the current host character set. |
e33d66ec | 8599 | |
10af6951 | 8600 | @item show target-charset |
a0eb71c5 | 8601 | @kindex show target-charset |
10af6951 | 8602 | Show the name of the current target character set. |
a0eb71c5 | 8603 | |
10af6951 EZ |
8604 | @item set target-wide-charset @var{charset} |
8605 | @kindex set target-wide-charset | |
8606 | Set the current target's wide character set to @var{charset}. This is | |
8607 | the character set used by the target's @code{wchar_t} type. To | |
8608 | display the list of supported wide character sets, type | |
8609 | @kbd{@w{set target-wide-charset @key{TAB}@key{TAB}}}. | |
8610 | ||
8611 | @item show target-wide-charset | |
8612 | @kindex show target-wide-charset | |
8613 | Show the name of the current target's wide character set. | |
a0eb71c5 KB |
8614 | @end table |
8615 | ||
a0eb71c5 KB |
8616 | Here is an example of @value{GDBN}'s character set support in action. |
8617 | Assume that the following source code has been placed in the file | |
8618 | @file{charset-test.c}: | |
8619 | ||
8620 | @smallexample | |
8621 | #include <stdio.h> | |
8622 | ||
8623 | char ascii_hello[] | |
8624 | = @{72, 101, 108, 108, 111, 44, 32, 119, | |
8625 | 111, 114, 108, 100, 33, 10, 0@}; | |
8626 | char ibm1047_hello[] | |
8627 | = @{200, 133, 147, 147, 150, 107, 64, 166, | |
8628 | 150, 153, 147, 132, 90, 37, 0@}; | |
8629 | ||
8630 | main () | |
8631 | @{ | |
8632 | printf ("Hello, world!\n"); | |
8633 | @} | |
10998722 | 8634 | @end smallexample |
a0eb71c5 KB |
8635 | |
8636 | In this program, @code{ascii_hello} and @code{ibm1047_hello} are arrays | |
8637 | containing the string @samp{Hello, world!} followed by a newline, | |
8638 | encoded in the @sc{ascii} and @sc{ibm1047} character sets. | |
8639 | ||
8640 | We compile the program, and invoke the debugger on it: | |
8641 | ||
8642 | @smallexample | |
8643 | $ gcc -g charset-test.c -o charset-test | |
8644 | $ gdb -nw charset-test | |
8645 | GNU gdb 2001-12-19-cvs | |
8646 | Copyright 2001 Free Software Foundation, Inc. | |
8647 | @dots{} | |
f7dc1244 | 8648 | (@value{GDBP}) |
10998722 | 8649 | @end smallexample |
a0eb71c5 KB |
8650 | |
8651 | We can use the @code{show charset} command to see what character sets | |
8652 | @value{GDBN} is currently using to interpret and display characters and | |
8653 | strings: | |
8654 | ||
8655 | @smallexample | |
f7dc1244 | 8656 | (@value{GDBP}) show charset |
e33d66ec | 8657 | The current host and target character set is `ISO-8859-1'. |
f7dc1244 | 8658 | (@value{GDBP}) |
10998722 | 8659 | @end smallexample |
a0eb71c5 KB |
8660 | |
8661 | For the sake of printing this manual, let's use @sc{ascii} as our | |
8662 | initial character set: | |
8663 | @smallexample | |
f7dc1244 EZ |
8664 | (@value{GDBP}) set charset ASCII |
8665 | (@value{GDBP}) show charset | |
e33d66ec | 8666 | The current host and target character set is `ASCII'. |
f7dc1244 | 8667 | (@value{GDBP}) |
10998722 | 8668 | @end smallexample |
a0eb71c5 KB |
8669 | |
8670 | Let's assume that @sc{ascii} is indeed the correct character set for our | |
8671 | host system --- in other words, let's assume that if @value{GDBN} prints | |
8672 | characters using the @sc{ascii} character set, our terminal will display | |
8673 | them properly. Since our current target character set is also | |
8674 | @sc{ascii}, the contents of @code{ascii_hello} print legibly: | |
8675 | ||
8676 | @smallexample | |
f7dc1244 | 8677 | (@value{GDBP}) print ascii_hello |
a0eb71c5 | 8678 | $1 = 0x401698 "Hello, world!\n" |
f7dc1244 | 8679 | (@value{GDBP}) print ascii_hello[0] |
a0eb71c5 | 8680 | $2 = 72 'H' |
f7dc1244 | 8681 | (@value{GDBP}) |
10998722 | 8682 | @end smallexample |
a0eb71c5 KB |
8683 | |
8684 | @value{GDBN} uses the target character set for character and string | |
8685 | literals you use in expressions: | |
8686 | ||
8687 | @smallexample | |
f7dc1244 | 8688 | (@value{GDBP}) print '+' |
a0eb71c5 | 8689 | $3 = 43 '+' |
f7dc1244 | 8690 | (@value{GDBP}) |
10998722 | 8691 | @end smallexample |
a0eb71c5 KB |
8692 | |
8693 | The @sc{ascii} character set uses the number 43 to encode the @samp{+} | |
8694 | character. | |
8695 | ||
8696 | @value{GDBN} relies on the user to tell it which character set the | |
8697 | target program uses. If we print @code{ibm1047_hello} while our target | |
8698 | character set is still @sc{ascii}, we get jibberish: | |
8699 | ||
8700 | @smallexample | |
f7dc1244 | 8701 | (@value{GDBP}) print ibm1047_hello |
a0eb71c5 | 8702 | $4 = 0x4016a8 "\310\205\223\223\226k@@\246\226\231\223\204Z%" |
f7dc1244 | 8703 | (@value{GDBP}) print ibm1047_hello[0] |
a0eb71c5 | 8704 | $5 = 200 '\310' |
f7dc1244 | 8705 | (@value{GDBP}) |
10998722 | 8706 | @end smallexample |
a0eb71c5 | 8707 | |
e33d66ec | 8708 | If we invoke the @code{set target-charset} followed by @key{TAB}@key{TAB}, |
a0eb71c5 KB |
8709 | @value{GDBN} tells us the character sets it supports: |
8710 | ||
8711 | @smallexample | |
f7dc1244 | 8712 | (@value{GDBP}) set target-charset |
b383017d | 8713 | ASCII EBCDIC-US IBM1047 ISO-8859-1 |
f7dc1244 | 8714 | (@value{GDBP}) set target-charset |
10998722 | 8715 | @end smallexample |
a0eb71c5 KB |
8716 | |
8717 | We can select @sc{ibm1047} as our target character set, and examine the | |
8718 | program's strings again. Now the @sc{ascii} string is wrong, but | |
8719 | @value{GDBN} translates the contents of @code{ibm1047_hello} from the | |
8720 | target character set, @sc{ibm1047}, to the host character set, | |
8721 | @sc{ascii}, and they display correctly: | |
8722 | ||
8723 | @smallexample | |
f7dc1244 EZ |
8724 | (@value{GDBP}) set target-charset IBM1047 |
8725 | (@value{GDBP}) show charset | |
e33d66ec EZ |
8726 | The current host character set is `ASCII'. |
8727 | The current target character set is `IBM1047'. | |
f7dc1244 | 8728 | (@value{GDBP}) print ascii_hello |
a0eb71c5 | 8729 | $6 = 0x401698 "\110\145%%?\054\040\167?\162%\144\041\012" |
f7dc1244 | 8730 | (@value{GDBP}) print ascii_hello[0] |
a0eb71c5 | 8731 | $7 = 72 '\110' |
f7dc1244 | 8732 | (@value{GDBP}) print ibm1047_hello |
a0eb71c5 | 8733 | $8 = 0x4016a8 "Hello, world!\n" |
f7dc1244 | 8734 | (@value{GDBP}) print ibm1047_hello[0] |
a0eb71c5 | 8735 | $9 = 200 'H' |
f7dc1244 | 8736 | (@value{GDBP}) |
10998722 | 8737 | @end smallexample |
a0eb71c5 KB |
8738 | |
8739 | As above, @value{GDBN} uses the target character set for character and | |
8740 | string literals you use in expressions: | |
8741 | ||
8742 | @smallexample | |
f7dc1244 | 8743 | (@value{GDBP}) print '+' |
a0eb71c5 | 8744 | $10 = 78 '+' |
f7dc1244 | 8745 | (@value{GDBP}) |
10998722 | 8746 | @end smallexample |
a0eb71c5 | 8747 | |
e33d66ec | 8748 | The @sc{ibm1047} character set uses the number 78 to encode the @samp{+} |
a0eb71c5 KB |
8749 | character. |
8750 | ||
09d4efe1 EZ |
8751 | @node Caching Remote Data |
8752 | @section Caching Data of Remote Targets | |
8753 | @cindex caching data of remote targets | |
8754 | ||
4e5d721f | 8755 | @value{GDBN} caches data exchanged between the debugger and a |
ea35711c | 8756 | remote target (@pxref{Remote Debugging}). Such caching generally improves |
09d4efe1 | 8757 | performance, because it reduces the overhead of the remote protocol by |
4e5d721f DE |
8758 | bundling memory reads and writes into large chunks. Unfortunately, simply |
8759 | caching everything would lead to incorrect results, since @value{GDBN} | |
8760 | does not necessarily know anything about volatile values, memory-mapped I/O | |
29b090c0 DE |
8761 | addresses, etc. Furthermore, in non-stop mode (@pxref{Non-Stop Mode}) |
8762 | memory can be changed @emph{while} a gdb command is executing. | |
8763 | Therefore, by default, @value{GDBN} only caches data | |
8764 | known to be on the stack@footnote{In non-stop mode, it is moderately | |
8765 | rare for a running thread to modify the stack of a stopped thread | |
8766 | in a way that would interfere with a backtrace, and caching of | |
8767 | stack reads provides a significant speed up of remote backtraces.}. | |
8768 | Other regions of memory can be explicitly marked as | |
4e5d721f | 8769 | cacheable; see @pxref{Memory Region Attributes}. |
09d4efe1 EZ |
8770 | |
8771 | @table @code | |
8772 | @kindex set remotecache | |
8773 | @item set remotecache on | |
8774 | @itemx set remotecache off | |
4e5d721f DE |
8775 | This option no longer does anything; it exists for compatibility |
8776 | with old scripts. | |
09d4efe1 EZ |
8777 | |
8778 | @kindex show remotecache | |
8779 | @item show remotecache | |
4e5d721f DE |
8780 | Show the current state of the obsolete remotecache flag. |
8781 | ||
8782 | @kindex set stack-cache | |
8783 | @item set stack-cache on | |
8784 | @itemx set stack-cache off | |
8785 | Enable or disable caching of stack accesses. When @code{ON}, use | |
8786 | caching. By default, this option is @code{ON}. | |
8787 | ||
8788 | @kindex show stack-cache | |
8789 | @item show stack-cache | |
8790 | Show the current state of data caching for memory accesses. | |
09d4efe1 EZ |
8791 | |
8792 | @kindex info dcache | |
4e5d721f | 8793 | @item info dcache @r{[}line@r{]} |
09d4efe1 | 8794 | Print the information about the data cache performance. The |
4e5d721f DE |
8795 | information displayed includes the dcache width and depth, and for |
8796 | each cache line, its number, address, and how many times it was | |
8797 | referenced. This command is useful for debugging the data cache | |
8798 | operation. | |
8799 | ||
8800 | If a line number is specified, the contents of that line will be | |
8801 | printed in hex. | |
09d4efe1 EZ |
8802 | @end table |
8803 | ||
08388c79 DE |
8804 | @node Searching Memory |
8805 | @section Search Memory | |
8806 | @cindex searching memory | |
8807 | ||
8808 | Memory can be searched for a particular sequence of bytes with the | |
8809 | @code{find} command. | |
8810 | ||
8811 | @table @code | |
8812 | @kindex find | |
8813 | @item find @r{[}/@var{sn}@r{]} @var{start_addr}, +@var{len}, @var{val1} @r{[}, @var{val2}, @dots{}@r{]} | |
8814 | @itemx find @r{[}/@var{sn}@r{]} @var{start_addr}, @var{end_addr}, @var{val1} @r{[}, @var{val2}, @dots{}@r{]} | |
8815 | Search memory for the sequence of bytes specified by @var{val1}, @var{val2}, | |
8816 | etc. The search begins at address @var{start_addr} and continues for either | |
8817 | @var{len} bytes or through to @var{end_addr} inclusive. | |
8818 | @end table | |
8819 | ||
8820 | @var{s} and @var{n} are optional parameters. | |
8821 | They may be specified in either order, apart or together. | |
8822 | ||
8823 | @table @r | |
8824 | @item @var{s}, search query size | |
8825 | The size of each search query value. | |
8826 | ||
8827 | @table @code | |
8828 | @item b | |
8829 | bytes | |
8830 | @item h | |
8831 | halfwords (two bytes) | |
8832 | @item w | |
8833 | words (four bytes) | |
8834 | @item g | |
8835 | giant words (eight bytes) | |
8836 | @end table | |
8837 | ||
8838 | All values are interpreted in the current language. | |
8839 | This means, for example, that if the current source language is C/C@t{++} | |
8840 | then searching for the string ``hello'' includes the trailing '\0'. | |
8841 | ||
8842 | If the value size is not specified, it is taken from the | |
8843 | value's type in the current language. | |
8844 | This is useful when one wants to specify the search | |
8845 | pattern as a mixture of types. | |
8846 | Note that this means, for example, that in the case of C-like languages | |
8847 | a search for an untyped 0x42 will search for @samp{(int) 0x42} | |
8848 | which is typically four bytes. | |
8849 | ||
8850 | @item @var{n}, maximum number of finds | |
8851 | The maximum number of matches to print. The default is to print all finds. | |
8852 | @end table | |
8853 | ||
8854 | You can use strings as search values. Quote them with double-quotes | |
8855 | (@code{"}). | |
8856 | The string value is copied into the search pattern byte by byte, | |
8857 | regardless of the endianness of the target and the size specification. | |
8858 | ||
8859 | The address of each match found is printed as well as a count of the | |
8860 | number of matches found. | |
8861 | ||
8862 | The address of the last value found is stored in convenience variable | |
8863 | @samp{$_}. | |
8864 | A count of the number of matches is stored in @samp{$numfound}. | |
8865 | ||
8866 | For example, if stopped at the @code{printf} in this function: | |
8867 | ||
8868 | @smallexample | |
8869 | void | |
8870 | hello () | |
8871 | @{ | |
8872 | static char hello[] = "hello-hello"; | |
8873 | static struct @{ char c; short s; int i; @} | |
8874 | __attribute__ ((packed)) mixed | |
8875 | = @{ 'c', 0x1234, 0x87654321 @}; | |
8876 | printf ("%s\n", hello); | |
8877 | @} | |
8878 | @end smallexample | |
8879 | ||
8880 | @noindent | |
8881 | you get during debugging: | |
8882 | ||
8883 | @smallexample | |
8884 | (gdb) find &hello[0], +sizeof(hello), "hello" | |
8885 | 0x804956d <hello.1620+6> | |
8886 | 1 pattern found | |
8887 | (gdb) find &hello[0], +sizeof(hello), 'h', 'e', 'l', 'l', 'o' | |
8888 | 0x8049567 <hello.1620> | |
8889 | 0x804956d <hello.1620+6> | |
8890 | 2 patterns found | |
8891 | (gdb) find /b1 &hello[0], +sizeof(hello), 'h', 0x65, 'l' | |
8892 | 0x8049567 <hello.1620> | |
8893 | 1 pattern found | |
8894 | (gdb) find &mixed, +sizeof(mixed), (char) 'c', (short) 0x1234, (int) 0x87654321 | |
8895 | 0x8049560 <mixed.1625> | |
8896 | 1 pattern found | |
8897 | (gdb) print $numfound | |
8898 | $1 = 1 | |
8899 | (gdb) print $_ | |
8900 | $2 = (void *) 0x8049560 | |
8901 | @end smallexample | |
a0eb71c5 | 8902 | |
edb3359d DJ |
8903 | @node Optimized Code |
8904 | @chapter Debugging Optimized Code | |
8905 | @cindex optimized code, debugging | |
8906 | @cindex debugging optimized code | |
8907 | ||
8908 | Almost all compilers support optimization. With optimization | |
8909 | disabled, the compiler generates assembly code that corresponds | |
8910 | directly to your source code, in a simplistic way. As the compiler | |
8911 | applies more powerful optimizations, the generated assembly code | |
8912 | diverges from your original source code. With help from debugging | |
8913 | information generated by the compiler, @value{GDBN} can map from | |
8914 | the running program back to constructs from your original source. | |
8915 | ||
8916 | @value{GDBN} is more accurate with optimization disabled. If you | |
8917 | can recompile without optimization, it is easier to follow the | |
8918 | progress of your program during debugging. But, there are many cases | |
8919 | where you may need to debug an optimized version. | |
8920 | ||
8921 | When you debug a program compiled with @samp{-g -O}, remember that the | |
8922 | optimizer has rearranged your code; the debugger shows you what is | |
8923 | really there. Do not be too surprised when the execution path does not | |
8924 | exactly match your source file! An extreme example: if you define a | |
8925 | variable, but never use it, @value{GDBN} never sees that | |
8926 | variable---because the compiler optimizes it out of existence. | |
8927 | ||
8928 | Some things do not work as well with @samp{-g -O} as with just | |
8929 | @samp{-g}, particularly on machines with instruction scheduling. If in | |
8930 | doubt, recompile with @samp{-g} alone, and if this fixes the problem, | |
8931 | please report it to us as a bug (including a test case!). | |
8932 | @xref{Variables}, for more information about debugging optimized code. | |
8933 | ||
8934 | @menu | |
8935 | * Inline Functions:: How @value{GDBN} presents inlining | |
8936 | @end menu | |
8937 | ||
8938 | @node Inline Functions | |
8939 | @section Inline Functions | |
8940 | @cindex inline functions, debugging | |
8941 | ||
8942 | @dfn{Inlining} is an optimization that inserts a copy of the function | |
8943 | body directly at each call site, instead of jumping to a shared | |
8944 | routine. @value{GDBN} displays inlined functions just like | |
8945 | non-inlined functions. They appear in backtraces. You can view their | |
8946 | arguments and local variables, step into them with @code{step}, skip | |
8947 | them with @code{next}, and escape from them with @code{finish}. | |
8948 | You can check whether a function was inlined by using the | |
8949 | @code{info frame} command. | |
8950 | ||
8951 | For @value{GDBN} to support inlined functions, the compiler must | |
8952 | record information about inlining in the debug information --- | |
8953 | @value{NGCC} using the @sc{dwarf 2} format does this, and several | |
8954 | other compilers do also. @value{GDBN} only supports inlined functions | |
8955 | when using @sc{dwarf 2}. Versions of @value{NGCC} before 4.1 | |
8956 | do not emit two required attributes (@samp{DW_AT_call_file} and | |
8957 | @samp{DW_AT_call_line}); @value{GDBN} does not display inlined | |
8958 | function calls with earlier versions of @value{NGCC}. It instead | |
8959 | displays the arguments and local variables of inlined functions as | |
8960 | local variables in the caller. | |
8961 | ||
8962 | The body of an inlined function is directly included at its call site; | |
8963 | unlike a non-inlined function, there are no instructions devoted to | |
8964 | the call. @value{GDBN} still pretends that the call site and the | |
8965 | start of the inlined function are different instructions. Stepping to | |
8966 | the call site shows the call site, and then stepping again shows | |
8967 | the first line of the inlined function, even though no additional | |
8968 | instructions are executed. | |
8969 | ||
8970 | This makes source-level debugging much clearer; you can see both the | |
8971 | context of the call and then the effect of the call. Only stepping by | |
8972 | a single instruction using @code{stepi} or @code{nexti} does not do | |
8973 | this; single instruction steps always show the inlined body. | |
8974 | ||
8975 | There are some ways that @value{GDBN} does not pretend that inlined | |
8976 | function calls are the same as normal calls: | |
8977 | ||
8978 | @itemize @bullet | |
8979 | @item | |
8980 | You cannot set breakpoints on inlined functions. @value{GDBN} | |
8981 | either reports that there is no symbol with that name, or else sets the | |
8982 | breakpoint only on non-inlined copies of the function. This limitation | |
8983 | will be removed in a future version of @value{GDBN}; until then, | |
8984 | set a breakpoint by line number on the first line of the inlined | |
8985 | function instead. | |
8986 | ||
8987 | @item | |
8988 | Setting breakpoints at the call site of an inlined function may not | |
8989 | work, because the call site does not contain any code. @value{GDBN} | |
8990 | may incorrectly move the breakpoint to the next line of the enclosing | |
8991 | function, after the call. This limitation will be removed in a future | |
8992 | version of @value{GDBN}; until then, set a breakpoint on an earlier line | |
8993 | or inside the inlined function instead. | |
8994 | ||
8995 | @item | |
8996 | @value{GDBN} cannot locate the return value of inlined calls after | |
8997 | using the @code{finish} command. This is a limitation of compiler-generated | |
8998 | debugging information; after @code{finish}, you can step to the next line | |
8999 | and print a variable where your program stored the return value. | |
9000 | ||
9001 | @end itemize | |
9002 | ||
9003 | ||
e2e0bcd1 JB |
9004 | @node Macros |
9005 | @chapter C Preprocessor Macros | |
9006 | ||
49efadf5 | 9007 | Some languages, such as C and C@t{++}, provide a way to define and invoke |
e2e0bcd1 JB |
9008 | ``preprocessor macros'' which expand into strings of tokens. |
9009 | @value{GDBN} can evaluate expressions containing macro invocations, show | |
9010 | the result of macro expansion, and show a macro's definition, including | |
9011 | where it was defined. | |
9012 | ||
9013 | You may need to compile your program specially to provide @value{GDBN} | |
9014 | with information about preprocessor macros. Most compilers do not | |
9015 | include macros in their debugging information, even when you compile | |
9016 | with the @option{-g} flag. @xref{Compilation}. | |
9017 | ||
9018 | A program may define a macro at one point, remove that definition later, | |
9019 | and then provide a different definition after that. Thus, at different | |
9020 | points in the program, a macro may have different definitions, or have | |
9021 | no definition at all. If there is a current stack frame, @value{GDBN} | |
9022 | uses the macros in scope at that frame's source code line. Otherwise, | |
9023 | @value{GDBN} uses the macros in scope at the current listing location; | |
9024 | see @ref{List}. | |
9025 | ||
e2e0bcd1 JB |
9026 | Whenever @value{GDBN} evaluates an expression, it always expands any |
9027 | macro invocations present in the expression. @value{GDBN} also provides | |
9028 | the following commands for working with macros explicitly. | |
9029 | ||
9030 | @table @code | |
9031 | ||
9032 | @kindex macro expand | |
9033 | @cindex macro expansion, showing the results of preprocessor | |
9034 | @cindex preprocessor macro expansion, showing the results of | |
9035 | @cindex expanding preprocessor macros | |
9036 | @item macro expand @var{expression} | |
9037 | @itemx macro exp @var{expression} | |
9038 | Show the results of expanding all preprocessor macro invocations in | |
9039 | @var{expression}. Since @value{GDBN} simply expands macros, but does | |
9040 | not parse the result, @var{expression} need not be a valid expression; | |
9041 | it can be any string of tokens. | |
9042 | ||
09d4efe1 | 9043 | @kindex macro exp1 |
e2e0bcd1 JB |
9044 | @item macro expand-once @var{expression} |
9045 | @itemx macro exp1 @var{expression} | |
4644b6e3 | 9046 | @cindex expand macro once |
e2e0bcd1 JB |
9047 | @i{(This command is not yet implemented.)} Show the results of |
9048 | expanding those preprocessor macro invocations that appear explicitly in | |
9049 | @var{expression}. Macro invocations appearing in that expansion are | |
9050 | left unchanged. This command allows you to see the effect of a | |
9051 | particular macro more clearly, without being confused by further | |
9052 | expansions. Since @value{GDBN} simply expands macros, but does not | |
9053 | parse the result, @var{expression} need not be a valid expression; it | |
9054 | can be any string of tokens. | |
9055 | ||
475b0867 | 9056 | @kindex info macro |
e2e0bcd1 JB |
9057 | @cindex macro definition, showing |
9058 | @cindex definition, showing a macro's | |
475b0867 | 9059 | @item info macro @var{macro} |
e2e0bcd1 | 9060 | Show the definition of the macro named @var{macro}, and describe the |
484086b7 | 9061 | source location or compiler command-line where that definition was established. |
e2e0bcd1 JB |
9062 | |
9063 | @kindex macro define | |
9064 | @cindex user-defined macros | |
9065 | @cindex defining macros interactively | |
9066 | @cindex macros, user-defined | |
9067 | @item macro define @var{macro} @var{replacement-list} | |
9068 | @itemx macro define @var{macro}(@var{arglist}) @var{replacement-list} | |
d7d9f01e TT |
9069 | Introduce a definition for a preprocessor macro named @var{macro}, |
9070 | invocations of which are replaced by the tokens given in | |
9071 | @var{replacement-list}. The first form of this command defines an | |
9072 | ``object-like'' macro, which takes no arguments; the second form | |
9073 | defines a ``function-like'' macro, which takes the arguments given in | |
9074 | @var{arglist}. | |
9075 | ||
9076 | A definition introduced by this command is in scope in every | |
9077 | expression evaluated in @value{GDBN}, until it is removed with the | |
9078 | @code{macro undef} command, described below. The definition overrides | |
9079 | all definitions for @var{macro} present in the program being debugged, | |
9080 | as well as any previous user-supplied definition. | |
e2e0bcd1 JB |
9081 | |
9082 | @kindex macro undef | |
9083 | @item macro undef @var{macro} | |
d7d9f01e TT |
9084 | Remove any user-supplied definition for the macro named @var{macro}. |
9085 | This command only affects definitions provided with the @code{macro | |
9086 | define} command, described above; it cannot remove definitions present | |
9087 | in the program being debugged. | |
e2e0bcd1 | 9088 | |
09d4efe1 EZ |
9089 | @kindex macro list |
9090 | @item macro list | |
d7d9f01e | 9091 | List all the macros defined using the @code{macro define} command. |
e2e0bcd1 JB |
9092 | @end table |
9093 | ||
9094 | @cindex macros, example of debugging with | |
9095 | Here is a transcript showing the above commands in action. First, we | |
9096 | show our source files: | |
9097 | ||
9098 | @smallexample | |
9099 | $ cat sample.c | |
9100 | #include <stdio.h> | |
9101 | #include "sample.h" | |
9102 | ||
9103 | #define M 42 | |
9104 | #define ADD(x) (M + x) | |
9105 | ||
9106 | main () | |
9107 | @{ | |
9108 | #define N 28 | |
9109 | printf ("Hello, world!\n"); | |
9110 | #undef N | |
9111 | printf ("We're so creative.\n"); | |
9112 | #define N 1729 | |
9113 | printf ("Goodbye, world!\n"); | |
9114 | @} | |
9115 | $ cat sample.h | |
9116 | #define Q < | |
9117 | $ | |
9118 | @end smallexample | |
9119 | ||
9120 | Now, we compile the program using the @sc{gnu} C compiler, @value{NGCC}. | |
9121 | We pass the @option{-gdwarf-2} and @option{-g3} flags to ensure the | |
9122 | compiler includes information about preprocessor macros in the debugging | |
9123 | information. | |
9124 | ||
9125 | @smallexample | |
9126 | $ gcc -gdwarf-2 -g3 sample.c -o sample | |
9127 | $ | |
9128 | @end smallexample | |
9129 | ||
9130 | Now, we start @value{GDBN} on our sample program: | |
9131 | ||
9132 | @smallexample | |
9133 | $ gdb -nw sample | |
9134 | GNU gdb 2002-05-06-cvs | |
9135 | Copyright 2002 Free Software Foundation, Inc. | |
9136 | GDB is free software, @dots{} | |
f7dc1244 | 9137 | (@value{GDBP}) |
e2e0bcd1 JB |
9138 | @end smallexample |
9139 | ||
9140 | We can expand macros and examine their definitions, even when the | |
9141 | program is not running. @value{GDBN} uses the current listing position | |
9142 | to decide which macro definitions are in scope: | |
9143 | ||
9144 | @smallexample | |
f7dc1244 | 9145 | (@value{GDBP}) list main |
e2e0bcd1 JB |
9146 | 3 |
9147 | 4 #define M 42 | |
9148 | 5 #define ADD(x) (M + x) | |
9149 | 6 | |
9150 | 7 main () | |
9151 | 8 @{ | |
9152 | 9 #define N 28 | |
9153 | 10 printf ("Hello, world!\n"); | |
9154 | 11 #undef N | |
9155 | 12 printf ("We're so creative.\n"); | |
f7dc1244 | 9156 | (@value{GDBP}) info macro ADD |
e2e0bcd1 JB |
9157 | Defined at /home/jimb/gdb/macros/play/sample.c:5 |
9158 | #define ADD(x) (M + x) | |
f7dc1244 | 9159 | (@value{GDBP}) info macro Q |
e2e0bcd1 JB |
9160 | Defined at /home/jimb/gdb/macros/play/sample.h:1 |
9161 | included at /home/jimb/gdb/macros/play/sample.c:2 | |
9162 | #define Q < | |
f7dc1244 | 9163 | (@value{GDBP}) macro expand ADD(1) |
e2e0bcd1 | 9164 | expands to: (42 + 1) |
f7dc1244 | 9165 | (@value{GDBP}) macro expand-once ADD(1) |
e2e0bcd1 | 9166 | expands to: once (M + 1) |
f7dc1244 | 9167 | (@value{GDBP}) |
e2e0bcd1 JB |
9168 | @end smallexample |
9169 | ||
d7d9f01e | 9170 | In the example above, note that @code{macro expand-once} expands only |
e2e0bcd1 JB |
9171 | the macro invocation explicit in the original text --- the invocation of |
9172 | @code{ADD} --- but does not expand the invocation of the macro @code{M}, | |
9173 | which was introduced by @code{ADD}. | |
9174 | ||
3f94c067 BW |
9175 | Once the program is running, @value{GDBN} uses the macro definitions in |
9176 | force at the source line of the current stack frame: | |
e2e0bcd1 JB |
9177 | |
9178 | @smallexample | |
f7dc1244 | 9179 | (@value{GDBP}) break main |
e2e0bcd1 | 9180 | Breakpoint 1 at 0x8048370: file sample.c, line 10. |
f7dc1244 | 9181 | (@value{GDBP}) run |
b383017d | 9182 | Starting program: /home/jimb/gdb/macros/play/sample |
e2e0bcd1 JB |
9183 | |
9184 | Breakpoint 1, main () at sample.c:10 | |
9185 | 10 printf ("Hello, world!\n"); | |
f7dc1244 | 9186 | (@value{GDBP}) |
e2e0bcd1 JB |
9187 | @end smallexample |
9188 | ||
9189 | At line 10, the definition of the macro @code{N} at line 9 is in force: | |
9190 | ||
9191 | @smallexample | |
f7dc1244 | 9192 | (@value{GDBP}) info macro N |
e2e0bcd1 JB |
9193 | Defined at /home/jimb/gdb/macros/play/sample.c:9 |
9194 | #define N 28 | |
f7dc1244 | 9195 | (@value{GDBP}) macro expand N Q M |
e2e0bcd1 | 9196 | expands to: 28 < 42 |
f7dc1244 | 9197 | (@value{GDBP}) print N Q M |
e2e0bcd1 | 9198 | $1 = 1 |
f7dc1244 | 9199 | (@value{GDBP}) |
e2e0bcd1 JB |
9200 | @end smallexample |
9201 | ||
9202 | As we step over directives that remove @code{N}'s definition, and then | |
9203 | give it a new definition, @value{GDBN} finds the definition (or lack | |
9204 | thereof) in force at each point: | |
9205 | ||
9206 | @smallexample | |
f7dc1244 | 9207 | (@value{GDBP}) next |
e2e0bcd1 JB |
9208 | Hello, world! |
9209 | 12 printf ("We're so creative.\n"); | |
f7dc1244 | 9210 | (@value{GDBP}) info macro N |
e2e0bcd1 JB |
9211 | The symbol `N' has no definition as a C/C++ preprocessor macro |
9212 | at /home/jimb/gdb/macros/play/sample.c:12 | |
f7dc1244 | 9213 | (@value{GDBP}) next |
e2e0bcd1 JB |
9214 | We're so creative. |
9215 | 14 printf ("Goodbye, world!\n"); | |
f7dc1244 | 9216 | (@value{GDBP}) info macro N |
e2e0bcd1 JB |
9217 | Defined at /home/jimb/gdb/macros/play/sample.c:13 |
9218 | #define N 1729 | |
f7dc1244 | 9219 | (@value{GDBP}) macro expand N Q M |
e2e0bcd1 | 9220 | expands to: 1729 < 42 |
f7dc1244 | 9221 | (@value{GDBP}) print N Q M |
e2e0bcd1 | 9222 | $2 = 0 |
f7dc1244 | 9223 | (@value{GDBP}) |
e2e0bcd1 JB |
9224 | @end smallexample |
9225 | ||
484086b7 JK |
9226 | In addition to source files, macros can be defined on the compilation command |
9227 | line using the @option{-D@var{name}=@var{value}} syntax. For macros defined in | |
9228 | such a way, @value{GDBN} displays the location of their definition as line zero | |
9229 | of the source file submitted to the compiler. | |
9230 | ||
9231 | @smallexample | |
9232 | (@value{GDBP}) info macro __STDC__ | |
9233 | Defined at /home/jimb/gdb/macros/play/sample.c:0 | |
9234 | -D__STDC__=1 | |
9235 | (@value{GDBP}) | |
9236 | @end smallexample | |
9237 | ||
e2e0bcd1 | 9238 | |
b37052ae EZ |
9239 | @node Tracepoints |
9240 | @chapter Tracepoints | |
9241 | @c This chapter is based on the documentation written by Michael | |
9242 | @c Snyder, David Taylor, Jim Blandy, and Elena Zannoni. | |
9243 | ||
9244 | @cindex tracepoints | |
9245 | In some applications, it is not feasible for the debugger to interrupt | |
9246 | the program's execution long enough for the developer to learn | |
9247 | anything helpful about its behavior. If the program's correctness | |
9248 | depends on its real-time behavior, delays introduced by a debugger | |
9249 | might cause the program to change its behavior drastically, or perhaps | |
9250 | fail, even when the code itself is correct. It is useful to be able | |
9251 | to observe the program's behavior without interrupting it. | |
9252 | ||
9253 | Using @value{GDBN}'s @code{trace} and @code{collect} commands, you can | |
9254 | specify locations in the program, called @dfn{tracepoints}, and | |
9255 | arbitrary expressions to evaluate when those tracepoints are reached. | |
9256 | Later, using the @code{tfind} command, you can examine the values | |
9257 | those expressions had when the program hit the tracepoints. The | |
9258 | expressions may also denote objects in memory---structures or arrays, | |
9259 | for example---whose values @value{GDBN} should record; while visiting | |
9260 | a particular tracepoint, you may inspect those objects as if they were | |
9261 | in memory at that moment. However, because @value{GDBN} records these | |
9262 | values without interacting with you, it can do so quickly and | |
9263 | unobtrusively, hopefully not disturbing the program's behavior. | |
9264 | ||
9265 | The tracepoint facility is currently available only for remote | |
9d29849a JB |
9266 | targets. @xref{Targets}. In addition, your remote target must know |
9267 | how to collect trace data. This functionality is implemented in the | |
9268 | remote stub; however, none of the stubs distributed with @value{GDBN} | |
9269 | support tracepoints as of this writing. The format of the remote | |
9270 | packets used to implement tracepoints are described in @ref{Tracepoint | |
9271 | Packets}. | |
b37052ae EZ |
9272 | |
9273 | This chapter describes the tracepoint commands and features. | |
9274 | ||
9275 | @menu | |
b383017d RM |
9276 | * Set Tracepoints:: |
9277 | * Analyze Collected Data:: | |
9278 | * Tracepoint Variables:: | |
b37052ae EZ |
9279 | @end menu |
9280 | ||
9281 | @node Set Tracepoints | |
9282 | @section Commands to Set Tracepoints | |
9283 | ||
9284 | Before running such a @dfn{trace experiment}, an arbitrary number of | |
1042e4c0 SS |
9285 | tracepoints can be set. A tracepoint is actually a special type of |
9286 | breakpoint (@pxref{Set Breaks}), so you can manipulate it using | |
9287 | standard breakpoint commands. For instance, as with breakpoints, | |
9288 | tracepoint numbers are successive integers starting from one, and many | |
9289 | of the commands associated with tracepoints take the tracepoint number | |
9290 | as their argument, to identify which tracepoint to work on. | |
b37052ae EZ |
9291 | |
9292 | For each tracepoint, you can specify, in advance, some arbitrary set | |
9293 | of data that you want the target to collect in the trace buffer when | |
9294 | it hits that tracepoint. The collected data can include registers, | |
9295 | local variables, or global data. Later, you can use @value{GDBN} | |
9296 | commands to examine the values these data had at the time the | |
9297 | tracepoint was hit. | |
9298 | ||
1042e4c0 SS |
9299 | Tracepoints do not support every breakpoint feature. Conditional |
9300 | expressions and ignore counts on tracepoints have no effect, and | |
9301 | tracepoints cannot run @value{GDBN} commands when they are | |
9302 | hit. Tracepoints may not be thread-specific either. | |
9303 | ||
b37052ae EZ |
9304 | This section describes commands to set tracepoints and associated |
9305 | conditions and actions. | |
9306 | ||
9307 | @menu | |
b383017d RM |
9308 | * Create and Delete Tracepoints:: |
9309 | * Enable and Disable Tracepoints:: | |
9310 | * Tracepoint Passcounts:: | |
782b2b07 | 9311 | * Tracepoint Conditions:: |
b383017d RM |
9312 | * Tracepoint Actions:: |
9313 | * Listing Tracepoints:: | |
79a6e687 | 9314 | * Starting and Stopping Trace Experiments:: |
b37052ae EZ |
9315 | @end menu |
9316 | ||
9317 | @node Create and Delete Tracepoints | |
9318 | @subsection Create and Delete Tracepoints | |
9319 | ||
9320 | @table @code | |
9321 | @cindex set tracepoint | |
9322 | @kindex trace | |
1042e4c0 | 9323 | @item trace @var{location} |
b37052ae | 9324 | The @code{trace} command is very similar to the @code{break} command. |
1042e4c0 SS |
9325 | Its argument @var{location} can be a source line, a function name, or |
9326 | an address in the target program. @xref{Specify Location}. The | |
9327 | @code{trace} command defines a tracepoint, which is a point in the | |
9328 | target program where the debugger will briefly stop, collect some | |
9329 | data, and then allow the program to continue. Setting a tracepoint or | |
9330 | changing its actions doesn't take effect until the next @code{tstart} | |
9331 | command, and once a trace experiment is running, further changes will | |
9332 | not have any effect until the next trace experiment starts. | |
b37052ae EZ |
9333 | |
9334 | Here are some examples of using the @code{trace} command: | |
9335 | ||
9336 | @smallexample | |
9337 | (@value{GDBP}) @b{trace foo.c:121} // a source file and line number | |
9338 | ||
9339 | (@value{GDBP}) @b{trace +2} // 2 lines forward | |
9340 | ||
9341 | (@value{GDBP}) @b{trace my_function} // first source line of function | |
9342 | ||
9343 | (@value{GDBP}) @b{trace *my_function} // EXACT start address of function | |
9344 | ||
9345 | (@value{GDBP}) @b{trace *0x2117c4} // an address | |
9346 | @end smallexample | |
9347 | ||
9348 | @noindent | |
9349 | You can abbreviate @code{trace} as @code{tr}. | |
9350 | ||
782b2b07 SS |
9351 | @item trace @var{location} if @var{cond} |
9352 | Set a tracepoint with condition @var{cond}; evaluate the expression | |
9353 | @var{cond} each time the tracepoint is reached, and collect data only | |
9354 | if the value is nonzero---that is, if @var{cond} evaluates as true. | |
9355 | @xref{Tracepoint Conditions, ,Tracepoint Conditions}, for more | |
9356 | information on tracepoint conditions. | |
9357 | ||
b37052ae EZ |
9358 | @vindex $tpnum |
9359 | @cindex last tracepoint number | |
9360 | @cindex recent tracepoint number | |
9361 | @cindex tracepoint number | |
9362 | The convenience variable @code{$tpnum} records the tracepoint number | |
9363 | of the most recently set tracepoint. | |
9364 | ||
9365 | @kindex delete tracepoint | |
9366 | @cindex tracepoint deletion | |
9367 | @item delete tracepoint @r{[}@var{num}@r{]} | |
9368 | Permanently delete one or more tracepoints. With no argument, the | |
1042e4c0 SS |
9369 | default is to delete all tracepoints. Note that the regular |
9370 | @code{delete} command can remove tracepoints also. | |
b37052ae EZ |
9371 | |
9372 | Examples: | |
9373 | ||
9374 | @smallexample | |
9375 | (@value{GDBP}) @b{delete trace 1 2 3} // remove three tracepoints | |
9376 | ||
9377 | (@value{GDBP}) @b{delete trace} // remove all tracepoints | |
9378 | @end smallexample | |
9379 | ||
9380 | @noindent | |
9381 | You can abbreviate this command as @code{del tr}. | |
9382 | @end table | |
9383 | ||
9384 | @node Enable and Disable Tracepoints | |
9385 | @subsection Enable and Disable Tracepoints | |
9386 | ||
1042e4c0 SS |
9387 | These commands are deprecated; they are equivalent to plain @code{disable} and @code{enable}. |
9388 | ||
b37052ae EZ |
9389 | @table @code |
9390 | @kindex disable tracepoint | |
9391 | @item disable tracepoint @r{[}@var{num}@r{]} | |
9392 | Disable tracepoint @var{num}, or all tracepoints if no argument | |
9393 | @var{num} is given. A disabled tracepoint will have no effect during | |
9394 | the next trace experiment, but it is not forgotten. You can re-enable | |
9395 | a disabled tracepoint using the @code{enable tracepoint} command. | |
9396 | ||
9397 | @kindex enable tracepoint | |
9398 | @item enable tracepoint @r{[}@var{num}@r{]} | |
9399 | Enable tracepoint @var{num}, or all tracepoints. The enabled | |
9400 | tracepoints will become effective the next time a trace experiment is | |
9401 | run. | |
9402 | @end table | |
9403 | ||
9404 | @node Tracepoint Passcounts | |
9405 | @subsection Tracepoint Passcounts | |
9406 | ||
9407 | @table @code | |
9408 | @kindex passcount | |
9409 | @cindex tracepoint pass count | |
9410 | @item passcount @r{[}@var{n} @r{[}@var{num}@r{]]} | |
9411 | Set the @dfn{passcount} of a tracepoint. The passcount is a way to | |
9412 | automatically stop a trace experiment. If a tracepoint's passcount is | |
9413 | @var{n}, then the trace experiment will be automatically stopped on | |
9414 | the @var{n}'th time that tracepoint is hit. If the tracepoint number | |
9415 | @var{num} is not specified, the @code{passcount} command sets the | |
9416 | passcount of the most recently defined tracepoint. If no passcount is | |
9417 | given, the trace experiment will run until stopped explicitly by the | |
9418 | user. | |
9419 | ||
9420 | Examples: | |
9421 | ||
9422 | @smallexample | |
b383017d | 9423 | (@value{GDBP}) @b{passcount 5 2} // Stop on the 5th execution of |
6826cf00 | 9424 | @exdent @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @code{// tracepoint 2} |
b37052ae EZ |
9425 | |
9426 | (@value{GDBP}) @b{passcount 12} // Stop on the 12th execution of the | |
6826cf00 | 9427 | @exdent @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @code{// most recently defined tracepoint.} |
b37052ae EZ |
9428 | (@value{GDBP}) @b{trace foo} |
9429 | (@value{GDBP}) @b{pass 3} | |
9430 | (@value{GDBP}) @b{trace bar} | |
9431 | (@value{GDBP}) @b{pass 2} | |
9432 | (@value{GDBP}) @b{trace baz} | |
9433 | (@value{GDBP}) @b{pass 1} // Stop tracing when foo has been | |
6826cf00 EZ |
9434 | @exdent @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @code{// executed 3 times OR when bar has} |
9435 | @exdent @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @code{// been executed 2 times} | |
9436 | @exdent @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @code{// OR when baz has been executed 1 time.} | |
b37052ae EZ |
9437 | @end smallexample |
9438 | @end table | |
9439 | ||
782b2b07 SS |
9440 | @node Tracepoint Conditions |
9441 | @subsection Tracepoint Conditions | |
9442 | @cindex conditional tracepoints | |
9443 | @cindex tracepoint conditions | |
9444 | ||
9445 | The simplest sort of tracepoint collects data every time your program | |
9446 | reaches a specified place. You can also specify a @dfn{condition} for | |
9447 | a tracepoint. A condition is just a Boolean expression in your | |
9448 | programming language (@pxref{Expressions, ,Expressions}). A | |
9449 | tracepoint with a condition evaluates the expression each time your | |
9450 | program reaches it, and data collection happens only if the condition | |
9451 | is true. | |
9452 | ||
9453 | Tracepoint conditions can be specified when a tracepoint is set, by | |
9454 | using @samp{if} in the arguments to the @code{trace} command. | |
9455 | @xref{Create and Delete Tracepoints, ,Setting Tracepoints}. They can | |
9456 | also be set or changed at any time with the @code{condition} command, | |
9457 | just as with breakpoints. | |
9458 | ||
9459 | Unlike breakpoint conditions, @value{GDBN} does not actually evaluate | |
9460 | the conditional expression itself. Instead, @value{GDBN} encodes the | |
9461 | expression into an agent expression (@pxref{Agent Expressions} | |
9462 | suitable for execution on the target, independently of @value{GDBN}. | |
9463 | Global variables become raw memory locations, locals become stack | |
9464 | accesses, and so forth. | |
9465 | ||
9466 | For instance, suppose you have a function that is usually called | |
9467 | frequently, but should not be called after an error has occurred. You | |
9468 | could use the following tracepoint command to collect data about calls | |
9469 | of that function that happen while the error code is propagating | |
9470 | through the program; an unconditional tracepoint could end up | |
9471 | collecting thousands of useless trace frames that you would have to | |
9472 | search through. | |
9473 | ||
9474 | @smallexample | |
9475 | (@value{GDBP}) @kbd{trace normal_operation if errcode > 0} | |
9476 | @end smallexample | |
9477 | ||
b37052ae EZ |
9478 | @node Tracepoint Actions |
9479 | @subsection Tracepoint Action Lists | |
9480 | ||
9481 | @table @code | |
9482 | @kindex actions | |
9483 | @cindex tracepoint actions | |
9484 | @item actions @r{[}@var{num}@r{]} | |
9485 | This command will prompt for a list of actions to be taken when the | |
9486 | tracepoint is hit. If the tracepoint number @var{num} is not | |
9487 | specified, this command sets the actions for the one that was most | |
9488 | recently defined (so that you can define a tracepoint and then say | |
9489 | @code{actions} without bothering about its number). You specify the | |
9490 | actions themselves on the following lines, one action at a time, and | |
9491 | terminate the actions list with a line containing just @code{end}. So | |
9492 | far, the only defined actions are @code{collect} and | |
9493 | @code{while-stepping}. | |
9494 | ||
9495 | @cindex remove actions from a tracepoint | |
9496 | To remove all actions from a tracepoint, type @samp{actions @var{num}} | |
9497 | and follow it immediately with @samp{end}. | |
9498 | ||
9499 | @smallexample | |
9500 | (@value{GDBP}) @b{collect @var{data}} // collect some data | |
9501 | ||
6826cf00 | 9502 | (@value{GDBP}) @b{while-stepping 5} // single-step 5 times, collect data |
b37052ae | 9503 | |
6826cf00 | 9504 | (@value{GDBP}) @b{end} // signals the end of actions. |
b37052ae EZ |
9505 | @end smallexample |
9506 | ||
9507 | In the following example, the action list begins with @code{collect} | |
9508 | commands indicating the things to be collected when the tracepoint is | |
9509 | hit. Then, in order to single-step and collect additional data | |
9510 | following the tracepoint, a @code{while-stepping} command is used, | |
9511 | followed by the list of things to be collected while stepping. The | |
9512 | @code{while-stepping} command is terminated by its own separate | |
9513 | @code{end} command. Lastly, the action list is terminated by an | |
9514 | @code{end} command. | |
9515 | ||
9516 | @smallexample | |
9517 | (@value{GDBP}) @b{trace foo} | |
9518 | (@value{GDBP}) @b{actions} | |
9519 | Enter actions for tracepoint 1, one per line: | |
9520 | > collect bar,baz | |
9521 | > collect $regs | |
9522 | > while-stepping 12 | |
9523 | > collect $fp, $sp | |
9524 | > end | |
9525 | end | |
9526 | @end smallexample | |
9527 | ||
9528 | @kindex collect @r{(tracepoints)} | |
9529 | @item collect @var{expr1}, @var{expr2}, @dots{} | |
9530 | Collect values of the given expressions when the tracepoint is hit. | |
9531 | This command accepts a comma-separated list of any valid expressions. | |
9532 | In addition to global, static, or local variables, the following | |
9533 | special arguments are supported: | |
9534 | ||
9535 | @table @code | |
9536 | @item $regs | |
9537 | collect all registers | |
9538 | ||
9539 | @item $args | |
9540 | collect all function arguments | |
9541 | ||
9542 | @item $locals | |
9543 | collect all local variables. | |
9544 | @end table | |
9545 | ||
9546 | You can give several consecutive @code{collect} commands, each one | |
9547 | with a single argument, or one @code{collect} command with several | |
9548 | arguments separated by commas: the effect is the same. | |
9549 | ||
f5c37c66 EZ |
9550 | The command @code{info scope} (@pxref{Symbols, info scope}) is |
9551 | particularly useful for figuring out what data to collect. | |
9552 | ||
b37052ae EZ |
9553 | @kindex while-stepping @r{(tracepoints)} |
9554 | @item while-stepping @var{n} | |
9555 | Perform @var{n} single-step traces after the tracepoint, collecting | |
9556 | new data at each step. The @code{while-stepping} command is | |
9557 | followed by the list of what to collect while stepping (followed by | |
9558 | its own @code{end} command): | |
9559 | ||
9560 | @smallexample | |
9561 | > while-stepping 12 | |
9562 | > collect $regs, myglobal | |
9563 | > end | |
9564 | > | |
9565 | @end smallexample | |
9566 | ||
9567 | @noindent | |
9568 | You may abbreviate @code{while-stepping} as @code{ws} or | |
9569 | @code{stepping}. | |
9570 | @end table | |
9571 | ||
9572 | @node Listing Tracepoints | |
9573 | @subsection Listing Tracepoints | |
9574 | ||
9575 | @table @code | |
9576 | @kindex info tracepoints | |
09d4efe1 | 9577 | @kindex info tp |
b37052ae EZ |
9578 | @cindex information about tracepoints |
9579 | @item info tracepoints @r{[}@var{num}@r{]} | |
1042e4c0 SS |
9580 | Display information about the tracepoint @var{num}. If you don't |
9581 | specify a tracepoint number, displays information about all the | |
9582 | tracepoints defined so far. The format is similar to that used for | |
9583 | @code{info breakpoints}; in fact, @code{info tracepoints} is the same | |
9584 | command, simply restricting itself to tracepoints. | |
9585 | ||
9586 | A tracepoint's listing may include additional information specific to | |
9587 | tracing: | |
b37052ae EZ |
9588 | |
9589 | @itemize @bullet | |
9590 | @item | |
b37052ae EZ |
9591 | its passcount as given by the @code{passcount @var{n}} command |
9592 | @item | |
9593 | its step count as given by the @code{while-stepping @var{n}} command | |
9594 | @item | |
1042e4c0 SS |
9595 | its action list as given by the @code{actions} command. The actions |
9596 | are prefixed with an @samp{A} so as to distinguish them from commands. | |
b37052ae EZ |
9597 | @end itemize |
9598 | ||
9599 | @smallexample | |
9600 | (@value{GDBP}) @b{info trace} | |
1042e4c0 SS |
9601 | Num Type Disp Enb Address What |
9602 | 1 tracepoint keep y 0x0804ab57 in foo() at main.cxx:7 | |
9603 | pass count 1200 | |
9604 | step count 20 | |
9605 | A while-stepping 20 | |
9606 | A collect globfoo, $regs | |
9607 | A end | |
9608 | A collect globfoo2 | |
9609 | A end | |
b37052ae EZ |
9610 | (@value{GDBP}) |
9611 | @end smallexample | |
9612 | ||
9613 | @noindent | |
9614 | This command can be abbreviated @code{info tp}. | |
9615 | @end table | |
9616 | ||
79a6e687 BW |
9617 | @node Starting and Stopping Trace Experiments |
9618 | @subsection Starting and Stopping Trace Experiments | |
b37052ae EZ |
9619 | |
9620 | @table @code | |
9621 | @kindex tstart | |
9622 | @cindex start a new trace experiment | |
9623 | @cindex collected data discarded | |
9624 | @item tstart | |
9625 | This command takes no arguments. It starts the trace experiment, and | |
9626 | begins collecting data. This has the side effect of discarding all | |
9627 | the data collected in the trace buffer during the previous trace | |
9628 | experiment. | |
9629 | ||
9630 | @kindex tstop | |
9631 | @cindex stop a running trace experiment | |
9632 | @item tstop | |
9633 | This command takes no arguments. It ends the trace experiment, and | |
9634 | stops collecting data. | |
9635 | ||
68c71a2e | 9636 | @strong{Note}: a trace experiment and data collection may stop |
b37052ae EZ |
9637 | automatically if any tracepoint's passcount is reached |
9638 | (@pxref{Tracepoint Passcounts}), or if the trace buffer becomes full. | |
9639 | ||
9640 | @kindex tstatus | |
9641 | @cindex status of trace data collection | |
9642 | @cindex trace experiment, status of | |
9643 | @item tstatus | |
9644 | This command displays the status of the current trace data | |
9645 | collection. | |
9646 | @end table | |
9647 | ||
9648 | Here is an example of the commands we described so far: | |
9649 | ||
9650 | @smallexample | |
9651 | (@value{GDBP}) @b{trace gdb_c_test} | |
9652 | (@value{GDBP}) @b{actions} | |
9653 | Enter actions for tracepoint #1, one per line. | |
9654 | > collect $regs,$locals,$args | |
9655 | > while-stepping 11 | |
9656 | > collect $regs | |
9657 | > end | |
9658 | > end | |
9659 | (@value{GDBP}) @b{tstart} | |
9660 | [time passes @dots{}] | |
9661 | (@value{GDBP}) @b{tstop} | |
9662 | @end smallexample | |
9663 | ||
9664 | ||
9665 | @node Analyze Collected Data | |
79a6e687 | 9666 | @section Using the Collected Data |
b37052ae EZ |
9667 | |
9668 | After the tracepoint experiment ends, you use @value{GDBN} commands | |
9669 | for examining the trace data. The basic idea is that each tracepoint | |
9670 | collects a trace @dfn{snapshot} every time it is hit and another | |
9671 | snapshot every time it single-steps. All these snapshots are | |
9672 | consecutively numbered from zero and go into a buffer, and you can | |
9673 | examine them later. The way you examine them is to @dfn{focus} on a | |
9674 | specific trace snapshot. When the remote stub is focused on a trace | |
9675 | snapshot, it will respond to all @value{GDBN} requests for memory and | |
9676 | registers by reading from the buffer which belongs to that snapshot, | |
9677 | rather than from @emph{real} memory or registers of the program being | |
9678 | debugged. This means that @strong{all} @value{GDBN} commands | |
9679 | (@code{print}, @code{info registers}, @code{backtrace}, etc.) will | |
9680 | behave as if we were currently debugging the program state as it was | |
9681 | when the tracepoint occurred. Any requests for data that are not in | |
9682 | the buffer will fail. | |
9683 | ||
9684 | @menu | |
9685 | * tfind:: How to select a trace snapshot | |
9686 | * tdump:: How to display all data for a snapshot | |
9687 | * save-tracepoints:: How to save tracepoints for a future run | |
9688 | @end menu | |
9689 | ||
9690 | @node tfind | |
9691 | @subsection @code{tfind @var{n}} | |
9692 | ||
9693 | @kindex tfind | |
9694 | @cindex select trace snapshot | |
9695 | @cindex find trace snapshot | |
9696 | The basic command for selecting a trace snapshot from the buffer is | |
9697 | @code{tfind @var{n}}, which finds trace snapshot number @var{n}, | |
9698 | counting from zero. If no argument @var{n} is given, the next | |
9699 | snapshot is selected. | |
9700 | ||
9701 | Here are the various forms of using the @code{tfind} command. | |
9702 | ||
9703 | @table @code | |
9704 | @item tfind start | |
9705 | Find the first snapshot in the buffer. This is a synonym for | |
9706 | @code{tfind 0} (since 0 is the number of the first snapshot). | |
9707 | ||
9708 | @item tfind none | |
9709 | Stop debugging trace snapshots, resume @emph{live} debugging. | |
9710 | ||
9711 | @item tfind end | |
9712 | Same as @samp{tfind none}. | |
9713 | ||
9714 | @item tfind | |
9715 | No argument means find the next trace snapshot. | |
9716 | ||
9717 | @item tfind - | |
9718 | Find the previous trace snapshot before the current one. This permits | |
9719 | retracing earlier steps. | |
9720 | ||
9721 | @item tfind tracepoint @var{num} | |
9722 | Find the next snapshot associated with tracepoint @var{num}. Search | |
9723 | proceeds forward from the last examined trace snapshot. If no | |
9724 | argument @var{num} is given, it means find the next snapshot collected | |
9725 | for the same tracepoint as the current snapshot. | |
9726 | ||
9727 | @item tfind pc @var{addr} | |
9728 | Find the next snapshot associated with the value @var{addr} of the | |
9729 | program counter. Search proceeds forward from the last examined trace | |
9730 | snapshot. If no argument @var{addr} is given, it means find the next | |
9731 | snapshot with the same value of PC as the current snapshot. | |
9732 | ||
9733 | @item tfind outside @var{addr1}, @var{addr2} | |
9734 | Find the next snapshot whose PC is outside the given range of | |
9735 | addresses. | |
9736 | ||
9737 | @item tfind range @var{addr1}, @var{addr2} | |
9738 | Find the next snapshot whose PC is between @var{addr1} and | |
9739 | @var{addr2}. @c FIXME: Is the range inclusive or exclusive? | |
9740 | ||
9741 | @item tfind line @r{[}@var{file}:@r{]}@var{n} | |
9742 | Find the next snapshot associated with the source line @var{n}. If | |
9743 | the optional argument @var{file} is given, refer to line @var{n} in | |
9744 | that source file. Search proceeds forward from the last examined | |
9745 | trace snapshot. If no argument @var{n} is given, it means find the | |
9746 | next line other than the one currently being examined; thus saying | |
9747 | @code{tfind line} repeatedly can appear to have the same effect as | |
9748 | stepping from line to line in a @emph{live} debugging session. | |
9749 | @end table | |
9750 | ||
9751 | The default arguments for the @code{tfind} commands are specifically | |
9752 | designed to make it easy to scan through the trace buffer. For | |
9753 | instance, @code{tfind} with no argument selects the next trace | |
9754 | snapshot, and @code{tfind -} with no argument selects the previous | |
9755 | trace snapshot. So, by giving one @code{tfind} command, and then | |
9756 | simply hitting @key{RET} repeatedly you can examine all the trace | |
9757 | snapshots in order. Or, by saying @code{tfind -} and then hitting | |
9758 | @key{RET} repeatedly you can examine the snapshots in reverse order. | |
9759 | The @code{tfind line} command with no argument selects the snapshot | |
9760 | for the next source line executed. The @code{tfind pc} command with | |
9761 | no argument selects the next snapshot with the same program counter | |
9762 | (PC) as the current frame. The @code{tfind tracepoint} command with | |
9763 | no argument selects the next trace snapshot collected by the same | |
9764 | tracepoint as the current one. | |
9765 | ||
9766 | In addition to letting you scan through the trace buffer manually, | |
9767 | these commands make it easy to construct @value{GDBN} scripts that | |
9768 | scan through the trace buffer and print out whatever collected data | |
9769 | you are interested in. Thus, if we want to examine the PC, FP, and SP | |
9770 | registers from each trace frame in the buffer, we can say this: | |
9771 | ||
9772 | @smallexample | |
9773 | (@value{GDBP}) @b{tfind start} | |
9774 | (@value{GDBP}) @b{while ($trace_frame != -1)} | |
9775 | > printf "Frame %d, PC = %08X, SP = %08X, FP = %08X\n", \ | |
9776 | $trace_frame, $pc, $sp, $fp | |
9777 | > tfind | |
9778 | > end | |
9779 | ||
9780 | Frame 0, PC = 0020DC64, SP = 0030BF3C, FP = 0030BF44 | |
9781 | Frame 1, PC = 0020DC6C, SP = 0030BF38, FP = 0030BF44 | |
9782 | Frame 2, PC = 0020DC70, SP = 0030BF34, FP = 0030BF44 | |
9783 | Frame 3, PC = 0020DC74, SP = 0030BF30, FP = 0030BF44 | |
9784 | Frame 4, PC = 0020DC78, SP = 0030BF2C, FP = 0030BF44 | |
9785 | Frame 5, PC = 0020DC7C, SP = 0030BF28, FP = 0030BF44 | |
9786 | Frame 6, PC = 0020DC80, SP = 0030BF24, FP = 0030BF44 | |
9787 | Frame 7, PC = 0020DC84, SP = 0030BF20, FP = 0030BF44 | |
9788 | Frame 8, PC = 0020DC88, SP = 0030BF1C, FP = 0030BF44 | |
9789 | Frame 9, PC = 0020DC8E, SP = 0030BF18, FP = 0030BF44 | |
9790 | Frame 10, PC = 00203F6C, SP = 0030BE3C, FP = 0030BF14 | |
9791 | @end smallexample | |
9792 | ||
9793 | Or, if we want to examine the variable @code{X} at each source line in | |
9794 | the buffer: | |
9795 | ||
9796 | @smallexample | |
9797 | (@value{GDBP}) @b{tfind start} | |
9798 | (@value{GDBP}) @b{while ($trace_frame != -1)} | |
9799 | > printf "Frame %d, X == %d\n", $trace_frame, X | |
9800 | > tfind line | |
9801 | > end | |
9802 | ||
9803 | Frame 0, X = 1 | |
9804 | Frame 7, X = 2 | |
9805 | Frame 13, X = 255 | |
9806 | @end smallexample | |
9807 | ||
9808 | @node tdump | |
9809 | @subsection @code{tdump} | |
9810 | @kindex tdump | |
9811 | @cindex dump all data collected at tracepoint | |
9812 | @cindex tracepoint data, display | |
9813 | ||
9814 | This command takes no arguments. It prints all the data collected at | |
9815 | the current trace snapshot. | |
9816 | ||
9817 | @smallexample | |
9818 | (@value{GDBP}) @b{trace 444} | |
9819 | (@value{GDBP}) @b{actions} | |
9820 | Enter actions for tracepoint #2, one per line: | |
9821 | > collect $regs, $locals, $args, gdb_long_test | |
9822 | > end | |
9823 | ||
9824 | (@value{GDBP}) @b{tstart} | |
9825 | ||
9826 | (@value{GDBP}) @b{tfind line 444} | |
9827 | #0 gdb_test (p1=0x11, p2=0x22, p3=0x33, p4=0x44, p5=0x55, p6=0x66) | |
9828 | at gdb_test.c:444 | |
9829 | 444 printp( "%s: arguments = 0x%X 0x%X 0x%X 0x%X 0x%X 0x%X\n", ) | |
9830 | ||
9831 | (@value{GDBP}) @b{tdump} | |
9832 | Data collected at tracepoint 2, trace frame 1: | |
9833 | d0 0xc4aa0085 -995491707 | |
9834 | d1 0x18 24 | |
9835 | d2 0x80 128 | |
9836 | d3 0x33 51 | |
9837 | d4 0x71aea3d 119204413 | |
9838 | d5 0x22 34 | |
9839 | d6 0xe0 224 | |
9840 | d7 0x380035 3670069 | |
9841 | a0 0x19e24a 1696330 | |
9842 | a1 0x3000668 50333288 | |
9843 | a2 0x100 256 | |
9844 | a3 0x322000 3284992 | |
9845 | a4 0x3000698 50333336 | |
9846 | a5 0x1ad3cc 1758156 | |
9847 | fp 0x30bf3c 0x30bf3c | |
9848 | sp 0x30bf34 0x30bf34 | |
9849 | ps 0x0 0 | |
9850 | pc 0x20b2c8 0x20b2c8 | |
9851 | fpcontrol 0x0 0 | |
9852 | fpstatus 0x0 0 | |
9853 | fpiaddr 0x0 0 | |
9854 | p = 0x20e5b4 "gdb-test" | |
9855 | p1 = (void *) 0x11 | |
9856 | p2 = (void *) 0x22 | |
9857 | p3 = (void *) 0x33 | |
9858 | p4 = (void *) 0x44 | |
9859 | p5 = (void *) 0x55 | |
9860 | p6 = (void *) 0x66 | |
9861 | gdb_long_test = 17 '\021' | |
9862 | ||
9863 | (@value{GDBP}) | |
9864 | @end smallexample | |
9865 | ||
9866 | @node save-tracepoints | |
9867 | @subsection @code{save-tracepoints @var{filename}} | |
9868 | @kindex save-tracepoints | |
9869 | @cindex save tracepoints for future sessions | |
9870 | ||
9871 | This command saves all current tracepoint definitions together with | |
9872 | their actions and passcounts, into a file @file{@var{filename}} | |
9873 | suitable for use in a later debugging session. To read the saved | |
9874 | tracepoint definitions, use the @code{source} command (@pxref{Command | |
9875 | Files}). | |
9876 | ||
9877 | @node Tracepoint Variables | |
9878 | @section Convenience Variables for Tracepoints | |
9879 | @cindex tracepoint variables | |
9880 | @cindex convenience variables for tracepoints | |
9881 | ||
9882 | @table @code | |
9883 | @vindex $trace_frame | |
9884 | @item (int) $trace_frame | |
9885 | The current trace snapshot (a.k.a.@: @dfn{frame}) number, or -1 if no | |
9886 | snapshot is selected. | |
9887 | ||
9888 | @vindex $tracepoint | |
9889 | @item (int) $tracepoint | |
9890 | The tracepoint for the current trace snapshot. | |
9891 | ||
9892 | @vindex $trace_line | |
9893 | @item (int) $trace_line | |
9894 | The line number for the current trace snapshot. | |
9895 | ||
9896 | @vindex $trace_file | |
9897 | @item (char []) $trace_file | |
9898 | The source file for the current trace snapshot. | |
9899 | ||
9900 | @vindex $trace_func | |
9901 | @item (char []) $trace_func | |
9902 | The name of the function containing @code{$tracepoint}. | |
9903 | @end table | |
9904 | ||
9905 | Note: @code{$trace_file} is not suitable for use in @code{printf}, | |
9906 | use @code{output} instead. | |
9907 | ||
9908 | Here's a simple example of using these convenience variables for | |
9909 | stepping through all the trace snapshots and printing some of their | |
9910 | data. | |
9911 | ||
9912 | @smallexample | |
9913 | (@value{GDBP}) @b{tfind start} | |
9914 | ||
9915 | (@value{GDBP}) @b{while $trace_frame != -1} | |
9916 | > output $trace_file | |
9917 | > printf ", line %d (tracepoint #%d)\n", $trace_line, $tracepoint | |
9918 | > tfind | |
9919 | > end | |
9920 | @end smallexample | |
9921 | ||
df0cd8c5 JB |
9922 | @node Overlays |
9923 | @chapter Debugging Programs That Use Overlays | |
9924 | @cindex overlays | |
9925 | ||
9926 | If your program is too large to fit completely in your target system's | |
9927 | memory, you can sometimes use @dfn{overlays} to work around this | |
9928 | problem. @value{GDBN} provides some support for debugging programs that | |
9929 | use overlays. | |
9930 | ||
9931 | @menu | |
9932 | * How Overlays Work:: A general explanation of overlays. | |
9933 | * Overlay Commands:: Managing overlays in @value{GDBN}. | |
9934 | * Automatic Overlay Debugging:: @value{GDBN} can find out which overlays are | |
9935 | mapped by asking the inferior. | |
9936 | * Overlay Sample Program:: A sample program using overlays. | |
9937 | @end menu | |
9938 | ||
9939 | @node How Overlays Work | |
9940 | @section How Overlays Work | |
9941 | @cindex mapped overlays | |
9942 | @cindex unmapped overlays | |
9943 | @cindex load address, overlay's | |
9944 | @cindex mapped address | |
9945 | @cindex overlay area | |
9946 | ||
9947 | Suppose you have a computer whose instruction address space is only 64 | |
9948 | kilobytes long, but which has much more memory which can be accessed by | |
9949 | other means: special instructions, segment registers, or memory | |
9950 | management hardware, for example. Suppose further that you want to | |
9951 | adapt a program which is larger than 64 kilobytes to run on this system. | |
9952 | ||
9953 | One solution is to identify modules of your program which are relatively | |
9954 | independent, and need not call each other directly; call these modules | |
9955 | @dfn{overlays}. Separate the overlays from the main program, and place | |
9956 | their machine code in the larger memory. Place your main program in | |
9957 | instruction memory, but leave at least enough space there to hold the | |
9958 | largest overlay as well. | |
9959 | ||
9960 | Now, to call a function located in an overlay, you must first copy that | |
9961 | overlay's machine code from the large memory into the space set aside | |
9962 | for it in the instruction memory, and then jump to its entry point | |
9963 | there. | |
9964 | ||
c928edc0 AC |
9965 | @c NB: In the below the mapped area's size is greater or equal to the |
9966 | @c size of all overlays. This is intentional to remind the developer | |
9967 | @c that overlays don't necessarily need to be the same size. | |
9968 | ||
474c8240 | 9969 | @smallexample |
df0cd8c5 | 9970 | @group |
c928edc0 AC |
9971 | Data Instruction Larger |
9972 | Address Space Address Space Address Space | |
9973 | +-----------+ +-----------+ +-----------+ | |
9974 | | | | | | | | |
9975 | +-----------+ +-----------+ +-----------+<-- overlay 1 | |
9976 | | program | | main | .----| overlay 1 | load address | |
9977 | | variables | | program | | +-----------+ | |
9978 | | and heap | | | | | | | |
9979 | +-----------+ | | | +-----------+<-- overlay 2 | |
9980 | | | +-----------+ | | | load address | |
9981 | +-----------+ | | | .-| overlay 2 | | |
9982 | | | | | | | | |
9983 | mapped --->+-----------+ | | +-----------+ | |
9984 | address | | | | | | | |
9985 | | overlay | <-' | | | | |
9986 | | area | <---' +-----------+<-- overlay 3 | |
9987 | | | <---. | | load address | |
9988 | +-----------+ `--| overlay 3 | | |
9989 | | | | | | |
9990 | +-----------+ | | | |
9991 | +-----------+ | |
9992 | | | | |
9993 | +-----------+ | |
9994 | ||
9995 | @anchor{A code overlay}A code overlay | |
df0cd8c5 | 9996 | @end group |
474c8240 | 9997 | @end smallexample |
df0cd8c5 | 9998 | |
c928edc0 AC |
9999 | The diagram (@pxref{A code overlay}) shows a system with separate data |
10000 | and instruction address spaces. To map an overlay, the program copies | |
10001 | its code from the larger address space to the instruction address space. | |
10002 | Since the overlays shown here all use the same mapped address, only one | |
10003 | may be mapped at a time. For a system with a single address space for | |
10004 | data and instructions, the diagram would be similar, except that the | |
10005 | program variables and heap would share an address space with the main | |
10006 | program and the overlay area. | |
df0cd8c5 JB |
10007 | |
10008 | An overlay loaded into instruction memory and ready for use is called a | |
10009 | @dfn{mapped} overlay; its @dfn{mapped address} is its address in the | |
10010 | instruction memory. An overlay not present (or only partially present) | |
10011 | in instruction memory is called @dfn{unmapped}; its @dfn{load address} | |
10012 | is its address in the larger memory. The mapped address is also called | |
10013 | the @dfn{virtual memory address}, or @dfn{VMA}; the load address is also | |
10014 | called the @dfn{load memory address}, or @dfn{LMA}. | |
10015 | ||
10016 | Unfortunately, overlays are not a completely transparent way to adapt a | |
10017 | program to limited instruction memory. They introduce a new set of | |
10018 | global constraints you must keep in mind as you design your program: | |
10019 | ||
10020 | @itemize @bullet | |
10021 | ||
10022 | @item | |
10023 | Before calling or returning to a function in an overlay, your program | |
10024 | must make sure that overlay is actually mapped. Otherwise, the call or | |
10025 | return will transfer control to the right address, but in the wrong | |
10026 | overlay, and your program will probably crash. | |
10027 | ||
10028 | @item | |
10029 | If the process of mapping an overlay is expensive on your system, you | |
10030 | will need to choose your overlays carefully to minimize their effect on | |
10031 | your program's performance. | |
10032 | ||
10033 | @item | |
10034 | The executable file you load onto your system must contain each | |
10035 | overlay's instructions, appearing at the overlay's load address, not its | |
10036 | mapped address. However, each overlay's instructions must be relocated | |
10037 | and its symbols defined as if the overlay were at its mapped address. | |
10038 | You can use GNU linker scripts to specify different load and relocation | |
10039 | addresses for pieces of your program; see @ref{Overlay Description,,, | |
10040 | ld.info, Using ld: the GNU linker}. | |
10041 | ||
10042 | @item | |
10043 | The procedure for loading executable files onto your system must be able | |
10044 | to load their contents into the larger address space as well as the | |
10045 | instruction and data spaces. | |
10046 | ||
10047 | @end itemize | |
10048 | ||
10049 | The overlay system described above is rather simple, and could be | |
10050 | improved in many ways: | |
10051 | ||
10052 | @itemize @bullet | |
10053 | ||
10054 | @item | |
10055 | If your system has suitable bank switch registers or memory management | |
10056 | hardware, you could use those facilities to make an overlay's load area | |
10057 | contents simply appear at their mapped address in instruction space. | |
10058 | This would probably be faster than copying the overlay to its mapped | |
10059 | area in the usual way. | |
10060 | ||
10061 | @item | |
10062 | If your overlays are small enough, you could set aside more than one | |
10063 | overlay area, and have more than one overlay mapped at a time. | |
10064 | ||
10065 | @item | |
10066 | You can use overlays to manage data, as well as instructions. In | |
10067 | general, data overlays are even less transparent to your design than | |
10068 | code overlays: whereas code overlays only require care when you call or | |
10069 | return to functions, data overlays require care every time you access | |
10070 | the data. Also, if you change the contents of a data overlay, you | |
10071 | must copy its contents back out to its load address before you can copy a | |
10072 | different data overlay into the same mapped area. | |
10073 | ||
10074 | @end itemize | |
10075 | ||
10076 | ||
10077 | @node Overlay Commands | |
10078 | @section Overlay Commands | |
10079 | ||
10080 | To use @value{GDBN}'s overlay support, each overlay in your program must | |
10081 | correspond to a separate section of the executable file. The section's | |
10082 | virtual memory address and load memory address must be the overlay's | |
10083 | mapped and load addresses. Identifying overlays with sections allows | |
10084 | @value{GDBN} to determine the appropriate address of a function or | |
10085 | variable, depending on whether the overlay is mapped or not. | |
10086 | ||
10087 | @value{GDBN}'s overlay commands all start with the word @code{overlay}; | |
10088 | you can abbreviate this as @code{ov} or @code{ovly}. The commands are: | |
10089 | ||
10090 | @table @code | |
10091 | @item overlay off | |
4644b6e3 | 10092 | @kindex overlay |
df0cd8c5 JB |
10093 | Disable @value{GDBN}'s overlay support. When overlay support is |
10094 | disabled, @value{GDBN} assumes that all functions and variables are | |
10095 | always present at their mapped addresses. By default, @value{GDBN}'s | |
10096 | overlay support is disabled. | |
10097 | ||
10098 | @item overlay manual | |
df0cd8c5 JB |
10099 | @cindex manual overlay debugging |
10100 | Enable @dfn{manual} overlay debugging. In this mode, @value{GDBN} | |
10101 | relies on you to tell it which overlays are mapped, and which are not, | |
10102 | using the @code{overlay map-overlay} and @code{overlay unmap-overlay} | |
10103 | commands described below. | |
10104 | ||
10105 | @item overlay map-overlay @var{overlay} | |
10106 | @itemx overlay map @var{overlay} | |
df0cd8c5 JB |
10107 | @cindex map an overlay |
10108 | Tell @value{GDBN} that @var{overlay} is now mapped; @var{overlay} must | |
10109 | be the name of the object file section containing the overlay. When an | |
10110 | overlay is mapped, @value{GDBN} assumes it can find the overlay's | |
10111 | functions and variables at their mapped addresses. @value{GDBN} assumes | |
10112 | that any other overlays whose mapped ranges overlap that of | |
10113 | @var{overlay} are now unmapped. | |
10114 | ||
10115 | @item overlay unmap-overlay @var{overlay} | |
10116 | @itemx overlay unmap @var{overlay} | |
df0cd8c5 JB |
10117 | @cindex unmap an overlay |
10118 | Tell @value{GDBN} that @var{overlay} is no longer mapped; @var{overlay} | |
10119 | must be the name of the object file section containing the overlay. | |
10120 | When an overlay is unmapped, @value{GDBN} assumes it can find the | |
10121 | overlay's functions and variables at their load addresses. | |
10122 | ||
10123 | @item overlay auto | |
df0cd8c5 JB |
10124 | Enable @dfn{automatic} overlay debugging. In this mode, @value{GDBN} |
10125 | consults a data structure the overlay manager maintains in the inferior | |
10126 | to see which overlays are mapped. For details, see @ref{Automatic | |
10127 | Overlay Debugging}. | |
10128 | ||
10129 | @item overlay load-target | |
10130 | @itemx overlay load | |
df0cd8c5 JB |
10131 | @cindex reloading the overlay table |
10132 | Re-read the overlay table from the inferior. Normally, @value{GDBN} | |
10133 | re-reads the table @value{GDBN} automatically each time the inferior | |
10134 | stops, so this command should only be necessary if you have changed the | |
10135 | overlay mapping yourself using @value{GDBN}. This command is only | |
10136 | useful when using automatic overlay debugging. | |
10137 | ||
10138 | @item overlay list-overlays | |
10139 | @itemx overlay list | |
10140 | @cindex listing mapped overlays | |
10141 | Display a list of the overlays currently mapped, along with their mapped | |
10142 | addresses, load addresses, and sizes. | |
10143 | ||
10144 | @end table | |
10145 | ||
10146 | Normally, when @value{GDBN} prints a code address, it includes the name | |
10147 | of the function the address falls in: | |
10148 | ||
474c8240 | 10149 | @smallexample |
f7dc1244 | 10150 | (@value{GDBP}) print main |
df0cd8c5 | 10151 | $3 = @{int ()@} 0x11a0 <main> |
474c8240 | 10152 | @end smallexample |
df0cd8c5 JB |
10153 | @noindent |
10154 | When overlay debugging is enabled, @value{GDBN} recognizes code in | |
10155 | unmapped overlays, and prints the names of unmapped functions with | |
10156 | asterisks around them. For example, if @code{foo} is a function in an | |
10157 | unmapped overlay, @value{GDBN} prints it this way: | |
10158 | ||
474c8240 | 10159 | @smallexample |
f7dc1244 | 10160 | (@value{GDBP}) overlay list |
df0cd8c5 | 10161 | No sections are mapped. |
f7dc1244 | 10162 | (@value{GDBP}) print foo |
df0cd8c5 | 10163 | $5 = @{int (int)@} 0x100000 <*foo*> |
474c8240 | 10164 | @end smallexample |
df0cd8c5 JB |
10165 | @noindent |
10166 | When @code{foo}'s overlay is mapped, @value{GDBN} prints the function's | |
10167 | name normally: | |
10168 | ||
474c8240 | 10169 | @smallexample |
f7dc1244 | 10170 | (@value{GDBP}) overlay list |
b383017d | 10171 | Section .ov.foo.text, loaded at 0x100000 - 0x100034, |
df0cd8c5 | 10172 | mapped at 0x1016 - 0x104a |
f7dc1244 | 10173 | (@value{GDBP}) print foo |
df0cd8c5 | 10174 | $6 = @{int (int)@} 0x1016 <foo> |
474c8240 | 10175 | @end smallexample |
df0cd8c5 JB |
10176 | |
10177 | When overlay debugging is enabled, @value{GDBN} can find the correct | |
10178 | address for functions and variables in an overlay, whether or not the | |
10179 | overlay is mapped. This allows most @value{GDBN} commands, like | |
10180 | @code{break} and @code{disassemble}, to work normally, even on unmapped | |
10181 | code. However, @value{GDBN}'s breakpoint support has some limitations: | |
10182 | ||
10183 | @itemize @bullet | |
10184 | @item | |
10185 | @cindex breakpoints in overlays | |
10186 | @cindex overlays, setting breakpoints in | |
10187 | You can set breakpoints in functions in unmapped overlays, as long as | |
10188 | @value{GDBN} can write to the overlay at its load address. | |
10189 | @item | |
10190 | @value{GDBN} can not set hardware or simulator-based breakpoints in | |
10191 | unmapped overlays. However, if you set a breakpoint at the end of your | |
10192 | overlay manager (and tell @value{GDBN} which overlays are now mapped, if | |
10193 | you are using manual overlay management), @value{GDBN} will re-set its | |
10194 | breakpoints properly. | |
10195 | @end itemize | |
10196 | ||
10197 | ||
10198 | @node Automatic Overlay Debugging | |
10199 | @section Automatic Overlay Debugging | |
10200 | @cindex automatic overlay debugging | |
10201 | ||
10202 | @value{GDBN} can automatically track which overlays are mapped and which | |
10203 | are not, given some simple co-operation from the overlay manager in the | |
10204 | inferior. If you enable automatic overlay debugging with the | |
10205 | @code{overlay auto} command (@pxref{Overlay Commands}), @value{GDBN} | |
10206 | looks in the inferior's memory for certain variables describing the | |
10207 | current state of the overlays. | |
10208 | ||
10209 | Here are the variables your overlay manager must define to support | |
10210 | @value{GDBN}'s automatic overlay debugging: | |
10211 | ||
10212 | @table @asis | |
10213 | ||
10214 | @item @code{_ovly_table}: | |
10215 | This variable must be an array of the following structures: | |
10216 | ||
474c8240 | 10217 | @smallexample |
df0cd8c5 JB |
10218 | struct |
10219 | @{ | |
10220 | /* The overlay's mapped address. */ | |
10221 | unsigned long vma; | |
10222 | ||
10223 | /* The size of the overlay, in bytes. */ | |
10224 | unsigned long size; | |
10225 | ||
10226 | /* The overlay's load address. */ | |
10227 | unsigned long lma; | |
10228 | ||
10229 | /* Non-zero if the overlay is currently mapped; | |
10230 | zero otherwise. */ | |
10231 | unsigned long mapped; | |
10232 | @} | |
474c8240 | 10233 | @end smallexample |
df0cd8c5 JB |
10234 | |
10235 | @item @code{_novlys}: | |
10236 | This variable must be a four-byte signed integer, holding the total | |
10237 | number of elements in @code{_ovly_table}. | |
10238 | ||
10239 | @end table | |
10240 | ||
10241 | To decide whether a particular overlay is mapped or not, @value{GDBN} | |
10242 | looks for an entry in @w{@code{_ovly_table}} whose @code{vma} and | |
10243 | @code{lma} members equal the VMA and LMA of the overlay's section in the | |
10244 | executable file. When @value{GDBN} finds a matching entry, it consults | |
10245 | the entry's @code{mapped} member to determine whether the overlay is | |
10246 | currently mapped. | |
10247 | ||
81d46470 | 10248 | In addition, your overlay manager may define a function called |
def71bfa | 10249 | @code{_ovly_debug_event}. If this function is defined, @value{GDBN} |
81d46470 MS |
10250 | will silently set a breakpoint there. If the overlay manager then |
10251 | calls this function whenever it has changed the overlay table, this | |
10252 | will enable @value{GDBN} to accurately keep track of which overlays | |
10253 | are in program memory, and update any breakpoints that may be set | |
b383017d | 10254 | in overlays. This will allow breakpoints to work even if the |
81d46470 MS |
10255 | overlays are kept in ROM or other non-writable memory while they |
10256 | are not being executed. | |
df0cd8c5 JB |
10257 | |
10258 | @node Overlay Sample Program | |
10259 | @section Overlay Sample Program | |
10260 | @cindex overlay example program | |
10261 | ||
10262 | When linking a program which uses overlays, you must place the overlays | |
10263 | at their load addresses, while relocating them to run at their mapped | |
10264 | addresses. To do this, you must write a linker script (@pxref{Overlay | |
10265 | Description,,, ld.info, Using ld: the GNU linker}). Unfortunately, | |
10266 | since linker scripts are specific to a particular host system, target | |
10267 | architecture, and target memory layout, this manual cannot provide | |
10268 | portable sample code demonstrating @value{GDBN}'s overlay support. | |
10269 | ||
10270 | However, the @value{GDBN} source distribution does contain an overlaid | |
10271 | program, with linker scripts for a few systems, as part of its test | |
10272 | suite. The program consists of the following files from | |
10273 | @file{gdb/testsuite/gdb.base}: | |
10274 | ||
10275 | @table @file | |
10276 | @item overlays.c | |
10277 | The main program file. | |
10278 | @item ovlymgr.c | |
10279 | A simple overlay manager, used by @file{overlays.c}. | |
10280 | @item foo.c | |
10281 | @itemx bar.c | |
10282 | @itemx baz.c | |
10283 | @itemx grbx.c | |
10284 | Overlay modules, loaded and used by @file{overlays.c}. | |
10285 | @item d10v.ld | |
10286 | @itemx m32r.ld | |
10287 | Linker scripts for linking the test program on the @code{d10v-elf} | |
10288 | and @code{m32r-elf} targets. | |
10289 | @end table | |
10290 | ||
10291 | You can build the test program using the @code{d10v-elf} GCC | |
10292 | cross-compiler like this: | |
10293 | ||
474c8240 | 10294 | @smallexample |
df0cd8c5 JB |
10295 | $ d10v-elf-gcc -g -c overlays.c |
10296 | $ d10v-elf-gcc -g -c ovlymgr.c | |
10297 | $ d10v-elf-gcc -g -c foo.c | |
10298 | $ d10v-elf-gcc -g -c bar.c | |
10299 | $ d10v-elf-gcc -g -c baz.c | |
10300 | $ d10v-elf-gcc -g -c grbx.c | |
10301 | $ d10v-elf-gcc -g overlays.o ovlymgr.o foo.o bar.o \ | |
10302 | baz.o grbx.o -Wl,-Td10v.ld -o overlays | |
474c8240 | 10303 | @end smallexample |
df0cd8c5 JB |
10304 | |
10305 | The build process is identical for any other architecture, except that | |
10306 | you must substitute the appropriate compiler and linker script for the | |
10307 | target system for @code{d10v-elf-gcc} and @code{d10v.ld}. | |
10308 | ||
10309 | ||
6d2ebf8b | 10310 | @node Languages |
c906108c SS |
10311 | @chapter Using @value{GDBN} with Different Languages |
10312 | @cindex languages | |
10313 | ||
c906108c SS |
10314 | Although programming languages generally have common aspects, they are |
10315 | rarely expressed in the same manner. For instance, in ANSI C, | |
10316 | dereferencing a pointer @code{p} is accomplished by @code{*p}, but in | |
10317 | Modula-2, it is accomplished by @code{p^}. Values can also be | |
5d161b24 | 10318 | represented (and displayed) differently. Hex numbers in C appear as |
c906108c | 10319 | @samp{0x1ae}, while in Modula-2 they appear as @samp{1AEH}. |
c906108c SS |
10320 | |
10321 | @cindex working language | |
10322 | Language-specific information is built into @value{GDBN} for some languages, | |
10323 | allowing you to express operations like the above in your program's | |
10324 | native language, and allowing @value{GDBN} to output values in a manner | |
10325 | consistent with the syntax of your program's native language. The | |
10326 | language you use to build expressions is called the @dfn{working | |
10327 | language}. | |
10328 | ||
10329 | @menu | |
10330 | * Setting:: Switching between source languages | |
10331 | * Show:: Displaying the language | |
c906108c | 10332 | * Checks:: Type and range checks |
79a6e687 BW |
10333 | * Supported Languages:: Supported languages |
10334 | * Unsupported Languages:: Unsupported languages | |
c906108c SS |
10335 | @end menu |
10336 | ||
6d2ebf8b | 10337 | @node Setting |
79a6e687 | 10338 | @section Switching Between Source Languages |
c906108c SS |
10339 | |
10340 | There are two ways to control the working language---either have @value{GDBN} | |
10341 | set it automatically, or select it manually yourself. You can use the | |
10342 | @code{set language} command for either purpose. On startup, @value{GDBN} | |
10343 | defaults to setting the language automatically. The working language is | |
10344 | used to determine how expressions you type are interpreted, how values | |
10345 | are printed, etc. | |
10346 | ||
10347 | In addition to the working language, every source file that | |
10348 | @value{GDBN} knows about has its own working language. For some object | |
10349 | file formats, the compiler might indicate which language a particular | |
10350 | source file is in. However, most of the time @value{GDBN} infers the | |
10351 | language from the name of the file. The language of a source file | |
b37052ae | 10352 | controls whether C@t{++} names are demangled---this way @code{backtrace} can |
c906108c | 10353 | show each frame appropriately for its own language. There is no way to |
d4f3574e SS |
10354 | set the language of a source file from within @value{GDBN}, but you can |
10355 | set the language associated with a filename extension. @xref{Show, , | |
79a6e687 | 10356 | Displaying the Language}. |
c906108c SS |
10357 | |
10358 | This is most commonly a problem when you use a program, such | |
5d161b24 | 10359 | as @code{cfront} or @code{f2c}, that generates C but is written in |
c906108c SS |
10360 | another language. In that case, make the |
10361 | program use @code{#line} directives in its C output; that way | |
10362 | @value{GDBN} will know the correct language of the source code of the original | |
10363 | program, and will display that source code, not the generated C code. | |
10364 | ||
10365 | @menu | |
10366 | * Filenames:: Filename extensions and languages. | |
10367 | * Manually:: Setting the working language manually | |
10368 | * Automatically:: Having @value{GDBN} infer the source language | |
10369 | @end menu | |
10370 | ||
6d2ebf8b | 10371 | @node Filenames |
79a6e687 | 10372 | @subsection List of Filename Extensions and Languages |
c906108c SS |
10373 | |
10374 | If a source file name ends in one of the following extensions, then | |
10375 | @value{GDBN} infers that its language is the one indicated. | |
10376 | ||
10377 | @table @file | |
e07c999f PH |
10378 | @item .ada |
10379 | @itemx .ads | |
10380 | @itemx .adb | |
10381 | @itemx .a | |
10382 | Ada source file. | |
c906108c SS |
10383 | |
10384 | @item .c | |
10385 | C source file | |
10386 | ||
10387 | @item .C | |
10388 | @itemx .cc | |
10389 | @itemx .cp | |
10390 | @itemx .cpp | |
10391 | @itemx .cxx | |
10392 | @itemx .c++ | |
b37052ae | 10393 | C@t{++} source file |
c906108c | 10394 | |
b37303ee AF |
10395 | @item .m |
10396 | Objective-C source file | |
10397 | ||
c906108c SS |
10398 | @item .f |
10399 | @itemx .F | |
10400 | Fortran source file | |
10401 | ||
c906108c SS |
10402 | @item .mod |
10403 | Modula-2 source file | |
c906108c SS |
10404 | |
10405 | @item .s | |
10406 | @itemx .S | |
10407 | Assembler source file. This actually behaves almost like C, but | |
10408 | @value{GDBN} does not skip over function prologues when stepping. | |
10409 | @end table | |
10410 | ||
10411 | In addition, you may set the language associated with a filename | |
79a6e687 | 10412 | extension. @xref{Show, , Displaying the Language}. |
c906108c | 10413 | |
6d2ebf8b | 10414 | @node Manually |
79a6e687 | 10415 | @subsection Setting the Working Language |
c906108c SS |
10416 | |
10417 | If you allow @value{GDBN} to set the language automatically, | |
10418 | expressions are interpreted the same way in your debugging session and | |
10419 | your program. | |
10420 | ||
10421 | @kindex set language | |
10422 | If you wish, you may set the language manually. To do this, issue the | |
10423 | command @samp{set language @var{lang}}, where @var{lang} is the name of | |
5d161b24 | 10424 | a language, such as |
c906108c | 10425 | @code{c} or @code{modula-2}. |
c906108c SS |
10426 | For a list of the supported languages, type @samp{set language}. |
10427 | ||
c906108c SS |
10428 | Setting the language manually prevents @value{GDBN} from updating the working |
10429 | language automatically. This can lead to confusion if you try | |
10430 | to debug a program when the working language is not the same as the | |
10431 | source language, when an expression is acceptable to both | |
10432 | languages---but means different things. For instance, if the current | |
10433 | source file were written in C, and @value{GDBN} was parsing Modula-2, a | |
10434 | command such as: | |
10435 | ||
474c8240 | 10436 | @smallexample |
c906108c | 10437 | print a = b + c |
474c8240 | 10438 | @end smallexample |
c906108c SS |
10439 | |
10440 | @noindent | |
10441 | might not have the effect you intended. In C, this means to add | |
10442 | @code{b} and @code{c} and place the result in @code{a}. The result | |
10443 | printed would be the value of @code{a}. In Modula-2, this means to compare | |
10444 | @code{a} to the result of @code{b+c}, yielding a @code{BOOLEAN} value. | |
c906108c | 10445 | |
6d2ebf8b | 10446 | @node Automatically |
79a6e687 | 10447 | @subsection Having @value{GDBN} Infer the Source Language |
c906108c SS |
10448 | |
10449 | To have @value{GDBN} set the working language automatically, use | |
10450 | @samp{set language local} or @samp{set language auto}. @value{GDBN} | |
10451 | then infers the working language. That is, when your program stops in a | |
10452 | frame (usually by encountering a breakpoint), @value{GDBN} sets the | |
10453 | working language to the language recorded for the function in that | |
10454 | frame. If the language for a frame is unknown (that is, if the function | |
10455 | or block corresponding to the frame was defined in a source file that | |
10456 | does not have a recognized extension), the current working language is | |
10457 | not changed, and @value{GDBN} issues a warning. | |
10458 | ||
10459 | This may not seem necessary for most programs, which are written | |
10460 | entirely in one source language. However, program modules and libraries | |
10461 | written in one source language can be used by a main program written in | |
10462 | a different source language. Using @samp{set language auto} in this | |
10463 | case frees you from having to set the working language manually. | |
10464 | ||
6d2ebf8b | 10465 | @node Show |
79a6e687 | 10466 | @section Displaying the Language |
c906108c SS |
10467 | |
10468 | The following commands help you find out which language is the | |
10469 | working language, and also what language source files were written in. | |
10470 | ||
c906108c SS |
10471 | @table @code |
10472 | @item show language | |
9c16f35a | 10473 | @kindex show language |
c906108c SS |
10474 | Display the current working language. This is the |
10475 | language you can use with commands such as @code{print} to | |
10476 | build and compute expressions that may involve variables in your program. | |
10477 | ||
10478 | @item info frame | |
4644b6e3 | 10479 | @kindex info frame@r{, show the source language} |
5d161b24 | 10480 | Display the source language for this frame. This language becomes the |
c906108c | 10481 | working language if you use an identifier from this frame. |
79a6e687 | 10482 | @xref{Frame Info, ,Information about a Frame}, to identify the other |
c906108c SS |
10483 | information listed here. |
10484 | ||
10485 | @item info source | |
4644b6e3 | 10486 | @kindex info source@r{, show the source language} |
c906108c | 10487 | Display the source language of this source file. |
5d161b24 | 10488 | @xref{Symbols, ,Examining the Symbol Table}, to identify the other |
c906108c SS |
10489 | information listed here. |
10490 | @end table | |
10491 | ||
10492 | In unusual circumstances, you may have source files with extensions | |
10493 | not in the standard list. You can then set the extension associated | |
10494 | with a language explicitly: | |
10495 | ||
c906108c | 10496 | @table @code |
09d4efe1 | 10497 | @item set extension-language @var{ext} @var{language} |
9c16f35a | 10498 | @kindex set extension-language |
09d4efe1 EZ |
10499 | Tell @value{GDBN} that source files with extension @var{ext} are to be |
10500 | assumed as written in the source language @var{language}. | |
c906108c SS |
10501 | |
10502 | @item info extensions | |
9c16f35a | 10503 | @kindex info extensions |
c906108c SS |
10504 | List all the filename extensions and the associated languages. |
10505 | @end table | |
10506 | ||
6d2ebf8b | 10507 | @node Checks |
79a6e687 | 10508 | @section Type and Range Checking |
c906108c SS |
10509 | |
10510 | @quotation | |
10511 | @emph{Warning:} In this release, the @value{GDBN} commands for type and range | |
10512 | checking are included, but they do not yet have any effect. This | |
10513 | section documents the intended facilities. | |
10514 | @end quotation | |
10515 | @c FIXME remove warning when type/range code added | |
10516 | ||
10517 | Some languages are designed to guard you against making seemingly common | |
10518 | errors through a series of compile- and run-time checks. These include | |
10519 | checking the type of arguments to functions and operators, and making | |
10520 | sure mathematical overflows are caught at run time. Checks such as | |
10521 | these help to ensure a program's correctness once it has been compiled | |
10522 | by eliminating type mismatches, and providing active checks for range | |
10523 | errors when your program is running. | |
10524 | ||
10525 | @value{GDBN} can check for conditions like the above if you wish. | |
9c16f35a EZ |
10526 | Although @value{GDBN} does not check the statements in your program, |
10527 | it can check expressions entered directly into @value{GDBN} for | |
10528 | evaluation via the @code{print} command, for example. As with the | |
10529 | working language, @value{GDBN} can also decide whether or not to check | |
10530 | automatically based on your program's source language. | |
79a6e687 | 10531 | @xref{Supported Languages, ,Supported Languages}, for the default |
9c16f35a | 10532 | settings of supported languages. |
c906108c SS |
10533 | |
10534 | @menu | |
10535 | * Type Checking:: An overview of type checking | |
10536 | * Range Checking:: An overview of range checking | |
10537 | @end menu | |
10538 | ||
10539 | @cindex type checking | |
10540 | @cindex checks, type | |
6d2ebf8b | 10541 | @node Type Checking |
79a6e687 | 10542 | @subsection An Overview of Type Checking |
c906108c SS |
10543 | |
10544 | Some languages, such as Modula-2, are strongly typed, meaning that the | |
10545 | arguments to operators and functions have to be of the correct type, | |
10546 | otherwise an error occurs. These checks prevent type mismatch | |
10547 | errors from ever causing any run-time problems. For example, | |
10548 | ||
10549 | @smallexample | |
10550 | 1 + 2 @result{} 3 | |
10551 | @exdent but | |
10552 | @error{} 1 + 2.3 | |
10553 | @end smallexample | |
10554 | ||
10555 | The second example fails because the @code{CARDINAL} 1 is not | |
10556 | type-compatible with the @code{REAL} 2.3. | |
10557 | ||
5d161b24 DB |
10558 | For the expressions you use in @value{GDBN} commands, you can tell the |
10559 | @value{GDBN} type checker to skip checking; | |
10560 | to treat any mismatches as errors and abandon the expression; | |
10561 | or to only issue warnings when type mismatches occur, | |
c906108c SS |
10562 | but evaluate the expression anyway. When you choose the last of |
10563 | these, @value{GDBN} evaluates expressions like the second example above, but | |
10564 | also issues a warning. | |
10565 | ||
5d161b24 DB |
10566 | Even if you turn type checking off, there may be other reasons |
10567 | related to type that prevent @value{GDBN} from evaluating an expression. | |
10568 | For instance, @value{GDBN} does not know how to add an @code{int} and | |
10569 | a @code{struct foo}. These particular type errors have nothing to do | |
10570 | with the language in use, and usually arise from expressions, such as | |
c906108c SS |
10571 | the one described above, which make little sense to evaluate anyway. |
10572 | ||
10573 | Each language defines to what degree it is strict about type. For | |
10574 | instance, both Modula-2 and C require the arguments to arithmetical | |
10575 | operators to be numbers. In C, enumerated types and pointers can be | |
10576 | represented as numbers, so that they are valid arguments to mathematical | |
79a6e687 | 10577 | operators. @xref{Supported Languages, ,Supported Languages}, for further |
c906108c SS |
10578 | details on specific languages. |
10579 | ||
10580 | @value{GDBN} provides some additional commands for controlling the type checker: | |
10581 | ||
c906108c SS |
10582 | @kindex set check type |
10583 | @kindex show check type | |
10584 | @table @code | |
10585 | @item set check type auto | |
10586 | Set type checking on or off based on the current working language. | |
79a6e687 | 10587 | @xref{Supported Languages, ,Supported Languages}, for the default settings for |
c906108c SS |
10588 | each language. |
10589 | ||
10590 | @item set check type on | |
10591 | @itemx set check type off | |
10592 | Set type checking on or off, overriding the default setting for the | |
10593 | current working language. Issue a warning if the setting does not | |
10594 | match the language default. If any type mismatches occur in | |
d4f3574e | 10595 | evaluating an expression while type checking is on, @value{GDBN} prints a |
c906108c SS |
10596 | message and aborts evaluation of the expression. |
10597 | ||
10598 | @item set check type warn | |
10599 | Cause the type checker to issue warnings, but to always attempt to | |
10600 | evaluate the expression. Evaluating the expression may still | |
10601 | be impossible for other reasons. For example, @value{GDBN} cannot add | |
10602 | numbers and structures. | |
10603 | ||
10604 | @item show type | |
5d161b24 | 10605 | Show the current setting of the type checker, and whether or not @value{GDBN} |
c906108c SS |
10606 | is setting it automatically. |
10607 | @end table | |
10608 | ||
10609 | @cindex range checking | |
10610 | @cindex checks, range | |
6d2ebf8b | 10611 | @node Range Checking |
79a6e687 | 10612 | @subsection An Overview of Range Checking |
c906108c SS |
10613 | |
10614 | In some languages (such as Modula-2), it is an error to exceed the | |
10615 | bounds of a type; this is enforced with run-time checks. Such range | |
10616 | checking is meant to ensure program correctness by making sure | |
10617 | computations do not overflow, or indices on an array element access do | |
10618 | not exceed the bounds of the array. | |
10619 | ||
10620 | For expressions you use in @value{GDBN} commands, you can tell | |
10621 | @value{GDBN} to treat range errors in one of three ways: ignore them, | |
10622 | always treat them as errors and abandon the expression, or issue | |
10623 | warnings but evaluate the expression anyway. | |
10624 | ||
10625 | A range error can result from numerical overflow, from exceeding an | |
10626 | array index bound, or when you type a constant that is not a member | |
10627 | of any type. Some languages, however, do not treat overflows as an | |
10628 | error. In many implementations of C, mathematical overflow causes the | |
10629 | result to ``wrap around'' to lower values---for example, if @var{m} is | |
10630 | the largest integer value, and @var{s} is the smallest, then | |
10631 | ||
474c8240 | 10632 | @smallexample |
c906108c | 10633 | @var{m} + 1 @result{} @var{s} |
474c8240 | 10634 | @end smallexample |
c906108c SS |
10635 | |
10636 | This, too, is specific to individual languages, and in some cases | |
79a6e687 BW |
10637 | specific to individual compilers or machines. @xref{Supported Languages, , |
10638 | Supported Languages}, for further details on specific languages. | |
c906108c SS |
10639 | |
10640 | @value{GDBN} provides some additional commands for controlling the range checker: | |
10641 | ||
c906108c SS |
10642 | @kindex set check range |
10643 | @kindex show check range | |
10644 | @table @code | |
10645 | @item set check range auto | |
10646 | Set range checking on or off based on the current working language. | |
79a6e687 | 10647 | @xref{Supported Languages, ,Supported Languages}, for the default settings for |
c906108c SS |
10648 | each language. |
10649 | ||
10650 | @item set check range on | |
10651 | @itemx set check range off | |
10652 | Set range checking on or off, overriding the default setting for the | |
10653 | current working language. A warning is issued if the setting does not | |
c3f6f71d JM |
10654 | match the language default. If a range error occurs and range checking is on, |
10655 | then a message is printed and evaluation of the expression is aborted. | |
c906108c SS |
10656 | |
10657 | @item set check range warn | |
10658 | Output messages when the @value{GDBN} range checker detects a range error, | |
10659 | but attempt to evaluate the expression anyway. Evaluating the | |
10660 | expression may still be impossible for other reasons, such as accessing | |
10661 | memory that the process does not own (a typical example from many Unix | |
10662 | systems). | |
10663 | ||
10664 | @item show range | |
10665 | Show the current setting of the range checker, and whether or not it is | |
10666 | being set automatically by @value{GDBN}. | |
10667 | @end table | |
c906108c | 10668 | |
79a6e687 BW |
10669 | @node Supported Languages |
10670 | @section Supported Languages | |
c906108c | 10671 | |
9c16f35a EZ |
10672 | @value{GDBN} supports C, C@t{++}, Objective-C, Fortran, Java, Pascal, |
10673 | assembly, Modula-2, and Ada. | |
cce74817 | 10674 | @c This is false ... |
c906108c SS |
10675 | Some @value{GDBN} features may be used in expressions regardless of the |
10676 | language you use: the @value{GDBN} @code{@@} and @code{::} operators, | |
10677 | and the @samp{@{type@}addr} construct (@pxref{Expressions, | |
10678 | ,Expressions}) can be used with the constructs of any supported | |
10679 | language. | |
10680 | ||
10681 | The following sections detail to what degree each source language is | |
10682 | supported by @value{GDBN}. These sections are not meant to be language | |
10683 | tutorials or references, but serve only as a reference guide to what the | |
10684 | @value{GDBN} expression parser accepts, and what input and output | |
10685 | formats should look like for different languages. There are many good | |
10686 | books written on each of these languages; please look to these for a | |
10687 | language reference or tutorial. | |
10688 | ||
c906108c | 10689 | @menu |
b37303ee | 10690 | * C:: C and C@t{++} |
b383017d | 10691 | * Objective-C:: Objective-C |
09d4efe1 | 10692 | * Fortran:: Fortran |
9c16f35a | 10693 | * Pascal:: Pascal |
b37303ee | 10694 | * Modula-2:: Modula-2 |
e07c999f | 10695 | * Ada:: Ada |
c906108c SS |
10696 | @end menu |
10697 | ||
6d2ebf8b | 10698 | @node C |
b37052ae | 10699 | @subsection C and C@t{++} |
7a292a7a | 10700 | |
b37052ae EZ |
10701 | @cindex C and C@t{++} |
10702 | @cindex expressions in C or C@t{++} | |
c906108c | 10703 | |
b37052ae | 10704 | Since C and C@t{++} are so closely related, many features of @value{GDBN} apply |
c906108c SS |
10705 | to both languages. Whenever this is the case, we discuss those languages |
10706 | together. | |
10707 | ||
41afff9a EZ |
10708 | @cindex C@t{++} |
10709 | @cindex @code{g++}, @sc{gnu} C@t{++} compiler | |
b37052ae EZ |
10710 | @cindex @sc{gnu} C@t{++} |
10711 | The C@t{++} debugging facilities are jointly implemented by the C@t{++} | |
10712 | compiler and @value{GDBN}. Therefore, to debug your C@t{++} code | |
10713 | effectively, you must compile your C@t{++} programs with a supported | |
10714 | C@t{++} compiler, such as @sc{gnu} @code{g++}, or the HP ANSI C@t{++} | |
c906108c SS |
10715 | compiler (@code{aCC}). |
10716 | ||
0179ffac DC |
10717 | For best results when using @sc{gnu} C@t{++}, use the DWARF 2 debugging |
10718 | format; if it doesn't work on your system, try the stabs+ debugging | |
10719 | format. You can select those formats explicitly with the @code{g++} | |
10720 | command-line options @option{-gdwarf-2} and @option{-gstabs+}. | |
ce9341a1 BW |
10721 | @xref{Debugging Options,,Options for Debugging Your Program or GCC, |
10722 | gcc.info, Using the @sc{gnu} Compiler Collection (GCC)}. | |
c906108c | 10723 | |
c906108c | 10724 | @menu |
b37052ae EZ |
10725 | * C Operators:: C and C@t{++} operators |
10726 | * C Constants:: C and C@t{++} constants | |
79a6e687 | 10727 | * C Plus Plus Expressions:: C@t{++} expressions |
b37052ae EZ |
10728 | * C Defaults:: Default settings for C and C@t{++} |
10729 | * C Checks:: C and C@t{++} type and range checks | |
c906108c | 10730 | * Debugging C:: @value{GDBN} and C |
79a6e687 | 10731 | * Debugging C Plus Plus:: @value{GDBN} features for C@t{++} |
febe4383 | 10732 | * Decimal Floating Point:: Numbers in Decimal Floating Point format |
c906108c | 10733 | @end menu |
c906108c | 10734 | |
6d2ebf8b | 10735 | @node C Operators |
79a6e687 | 10736 | @subsubsection C and C@t{++} Operators |
7a292a7a | 10737 | |
b37052ae | 10738 | @cindex C and C@t{++} operators |
c906108c SS |
10739 | |
10740 | Operators must be defined on values of specific types. For instance, | |
10741 | @code{+} is defined on numbers, but not on structures. Operators are | |
5d161b24 | 10742 | often defined on groups of types. |
c906108c | 10743 | |
b37052ae | 10744 | For the purposes of C and C@t{++}, the following definitions hold: |
c906108c SS |
10745 | |
10746 | @itemize @bullet | |
53a5351d | 10747 | |
c906108c | 10748 | @item |
c906108c | 10749 | @emph{Integral types} include @code{int} with any of its storage-class |
b37052ae | 10750 | specifiers; @code{char}; @code{enum}; and, for C@t{++}, @code{bool}. |
c906108c SS |
10751 | |
10752 | @item | |
d4f3574e SS |
10753 | @emph{Floating-point types} include @code{float}, @code{double}, and |
10754 | @code{long double} (if supported by the target platform). | |
c906108c SS |
10755 | |
10756 | @item | |
53a5351d | 10757 | @emph{Pointer types} include all types defined as @code{(@var{type} *)}. |
c906108c SS |
10758 | |
10759 | @item | |
10760 | @emph{Scalar types} include all of the above. | |
53a5351d | 10761 | |
c906108c SS |
10762 | @end itemize |
10763 | ||
10764 | @noindent | |
10765 | The following operators are supported. They are listed here | |
10766 | in order of increasing precedence: | |
10767 | ||
10768 | @table @code | |
10769 | @item , | |
10770 | The comma or sequencing operator. Expressions in a comma-separated list | |
10771 | are evaluated from left to right, with the result of the entire | |
10772 | expression being the last expression evaluated. | |
10773 | ||
10774 | @item = | |
10775 | Assignment. The value of an assignment expression is the value | |
10776 | assigned. Defined on scalar types. | |
10777 | ||
10778 | @item @var{op}= | |
10779 | Used in an expression of the form @w{@code{@var{a} @var{op}= @var{b}}}, | |
10780 | and translated to @w{@code{@var{a} = @var{a op b}}}. | |
d4f3574e | 10781 | @w{@code{@var{op}=}} and @code{=} have the same precedence. |
c906108c SS |
10782 | @var{op} is any one of the operators @code{|}, @code{^}, @code{&}, |
10783 | @code{<<}, @code{>>}, @code{+}, @code{-}, @code{*}, @code{/}, @code{%}. | |
10784 | ||
10785 | @item ?: | |
10786 | The ternary operator. @code{@var{a} ? @var{b} : @var{c}} can be thought | |
10787 | of as: if @var{a} then @var{b} else @var{c}. @var{a} should be of an | |
10788 | integral type. | |
10789 | ||
10790 | @item || | |
10791 | Logical @sc{or}. Defined on integral types. | |
10792 | ||
10793 | @item && | |
10794 | Logical @sc{and}. Defined on integral types. | |
10795 | ||
10796 | @item | | |
10797 | Bitwise @sc{or}. Defined on integral types. | |
10798 | ||
10799 | @item ^ | |
10800 | Bitwise exclusive-@sc{or}. Defined on integral types. | |
10801 | ||
10802 | @item & | |
10803 | Bitwise @sc{and}. Defined on integral types. | |
10804 | ||
10805 | @item ==@r{, }!= | |
10806 | Equality and inequality. Defined on scalar types. The value of these | |
10807 | expressions is 0 for false and non-zero for true. | |
10808 | ||
10809 | @item <@r{, }>@r{, }<=@r{, }>= | |
10810 | Less than, greater than, less than or equal, greater than or equal. | |
10811 | Defined on scalar types. The value of these expressions is 0 for false | |
10812 | and non-zero for true. | |
10813 | ||
10814 | @item <<@r{, }>> | |
10815 | left shift, and right shift. Defined on integral types. | |
10816 | ||
10817 | @item @@ | |
10818 | The @value{GDBN} ``artificial array'' operator (@pxref{Expressions, ,Expressions}). | |
10819 | ||
10820 | @item +@r{, }- | |
10821 | Addition and subtraction. Defined on integral types, floating-point types and | |
10822 | pointer types. | |
10823 | ||
10824 | @item *@r{, }/@r{, }% | |
10825 | Multiplication, division, and modulus. Multiplication and division are | |
10826 | defined on integral and floating-point types. Modulus is defined on | |
10827 | integral types. | |
10828 | ||
10829 | @item ++@r{, }-- | |
10830 | Increment and decrement. When appearing before a variable, the | |
10831 | operation is performed before the variable is used in an expression; | |
10832 | when appearing after it, the variable's value is used before the | |
10833 | operation takes place. | |
10834 | ||
10835 | @item * | |
10836 | Pointer dereferencing. Defined on pointer types. Same precedence as | |
10837 | @code{++}. | |
10838 | ||
10839 | @item & | |
10840 | Address operator. Defined on variables. Same precedence as @code{++}. | |
10841 | ||
b37052ae EZ |
10842 | For debugging C@t{++}, @value{GDBN} implements a use of @samp{&} beyond what is |
10843 | allowed in the C@t{++} language itself: you can use @samp{&(&@var{ref})} | |
b17828ca | 10844 | to examine the address |
b37052ae | 10845 | where a C@t{++} reference variable (declared with @samp{&@var{ref}}) is |
c906108c | 10846 | stored. |
c906108c SS |
10847 | |
10848 | @item - | |
10849 | Negative. Defined on integral and floating-point types. Same | |
10850 | precedence as @code{++}. | |
10851 | ||
10852 | @item ! | |
10853 | Logical negation. Defined on integral types. Same precedence as | |
10854 | @code{++}. | |
10855 | ||
10856 | @item ~ | |
10857 | Bitwise complement operator. Defined on integral types. Same precedence as | |
10858 | @code{++}. | |
10859 | ||
10860 | ||
10861 | @item .@r{, }-> | |
10862 | Structure member, and pointer-to-structure member. For convenience, | |
10863 | @value{GDBN} regards the two as equivalent, choosing whether to dereference a | |
10864 | pointer based on the stored type information. | |
10865 | Defined on @code{struct} and @code{union} data. | |
10866 | ||
c906108c SS |
10867 | @item .*@r{, }->* |
10868 | Dereferences of pointers to members. | |
c906108c SS |
10869 | |
10870 | @item [] | |
10871 | Array indexing. @code{@var{a}[@var{i}]} is defined as | |
10872 | @code{*(@var{a}+@var{i})}. Same precedence as @code{->}. | |
10873 | ||
10874 | @item () | |
10875 | Function parameter list. Same precedence as @code{->}. | |
10876 | ||
c906108c | 10877 | @item :: |
b37052ae | 10878 | C@t{++} scope resolution operator. Defined on @code{struct}, @code{union}, |
7a292a7a | 10879 | and @code{class} types. |
c906108c SS |
10880 | |
10881 | @item :: | |
7a292a7a SS |
10882 | Doubled colons also represent the @value{GDBN} scope operator |
10883 | (@pxref{Expressions, ,Expressions}). Same precedence as @code{::}, | |
10884 | above. | |
c906108c SS |
10885 | @end table |
10886 | ||
c906108c SS |
10887 | If an operator is redefined in the user code, @value{GDBN} usually |
10888 | attempts to invoke the redefined version instead of using the operator's | |
10889 | predefined meaning. | |
c906108c | 10890 | |
6d2ebf8b | 10891 | @node C Constants |
79a6e687 | 10892 | @subsubsection C and C@t{++} Constants |
c906108c | 10893 | |
b37052ae | 10894 | @cindex C and C@t{++} constants |
c906108c | 10895 | |
b37052ae | 10896 | @value{GDBN} allows you to express the constants of C and C@t{++} in the |
c906108c | 10897 | following ways: |
c906108c SS |
10898 | |
10899 | @itemize @bullet | |
10900 | @item | |
10901 | Integer constants are a sequence of digits. Octal constants are | |
6ca652b0 EZ |
10902 | specified by a leading @samp{0} (i.e.@: zero), and hexadecimal constants |
10903 | by a leading @samp{0x} or @samp{0X}. Constants may also end with a letter | |
c906108c SS |
10904 | @samp{l}, specifying that the constant should be treated as a |
10905 | @code{long} value. | |
10906 | ||
10907 | @item | |
10908 | Floating point constants are a sequence of digits, followed by a decimal | |
10909 | point, followed by a sequence of digits, and optionally followed by an | |
10910 | exponent. An exponent is of the form: | |
10911 | @samp{@w{e@r{[[}+@r{]|}-@r{]}@var{nnn}}}, where @var{nnn} is another | |
10912 | sequence of digits. The @samp{+} is optional for positive exponents. | |
d4f3574e SS |
10913 | A floating-point constant may also end with a letter @samp{f} or |
10914 | @samp{F}, specifying that the constant should be treated as being of | |
10915 | the @code{float} (as opposed to the default @code{double}) type; or with | |
10916 | a letter @samp{l} or @samp{L}, which specifies a @code{long double} | |
10917 | constant. | |
c906108c SS |
10918 | |
10919 | @item | |
10920 | Enumerated constants consist of enumerated identifiers, or their | |
10921 | integral equivalents. | |
10922 | ||
10923 | @item | |
10924 | Character constants are a single character surrounded by single quotes | |
10925 | (@code{'}), or a number---the ordinal value of the corresponding character | |
d4f3574e | 10926 | (usually its @sc{ascii} value). Within quotes, the single character may |
c906108c SS |
10927 | be represented by a letter or by @dfn{escape sequences}, which are of |
10928 | the form @samp{\@var{nnn}}, where @var{nnn} is the octal representation | |
10929 | of the character's ordinal value; or of the form @samp{\@var{x}}, where | |
10930 | @samp{@var{x}} is a predefined special character---for example, | |
10931 | @samp{\n} for newline. | |
10932 | ||
10933 | @item | |
96a2c332 SS |
10934 | String constants are a sequence of character constants surrounded by |
10935 | double quotes (@code{"}). Any valid character constant (as described | |
10936 | above) may appear. Double quotes within the string must be preceded by | |
10937 | a backslash, so for instance @samp{"a\"b'c"} is a string of five | |
10938 | characters. | |
c906108c SS |
10939 | |
10940 | @item | |
10941 | Pointer constants are an integral value. You can also write pointers | |
10942 | to constants using the C operator @samp{&}. | |
10943 | ||
10944 | @item | |
10945 | Array constants are comma-separated lists surrounded by braces @samp{@{} | |
10946 | and @samp{@}}; for example, @samp{@{1,2,3@}} is a three-element array of | |
10947 | integers, @samp{@{@{1,2@}, @{3,4@}, @{5,6@}@}} is a three-by-two array, | |
10948 | and @samp{@{&"hi", &"there", &"fred"@}} is a three-element array of pointers. | |
10949 | @end itemize | |
10950 | ||
79a6e687 BW |
10951 | @node C Plus Plus Expressions |
10952 | @subsubsection C@t{++} Expressions | |
b37052ae EZ |
10953 | |
10954 | @cindex expressions in C@t{++} | |
10955 | @value{GDBN} expression handling can interpret most C@t{++} expressions. | |
10956 | ||
0179ffac DC |
10957 | @cindex debugging C@t{++} programs |
10958 | @cindex C@t{++} compilers | |
10959 | @cindex debug formats and C@t{++} | |
10960 | @cindex @value{NGCC} and C@t{++} | |
c906108c | 10961 | @quotation |
b37052ae | 10962 | @emph{Warning:} @value{GDBN} can only debug C@t{++} code if you use the |
0179ffac DC |
10963 | proper compiler and the proper debug format. Currently, @value{GDBN} |
10964 | works best when debugging C@t{++} code that is compiled with | |
10965 | @value{NGCC} 2.95.3 or with @value{NGCC} 3.1 or newer, using the options | |
10966 | @option{-gdwarf-2} or @option{-gstabs+}. DWARF 2 is preferred over | |
10967 | stabs+. Most configurations of @value{NGCC} emit either DWARF 2 or | |
10968 | stabs+ as their default debug format, so you usually don't need to | |
10969 | specify a debug format explicitly. Other compilers and/or debug formats | |
10970 | are likely to work badly or not at all when using @value{GDBN} to debug | |
10971 | C@t{++} code. | |
c906108c | 10972 | @end quotation |
c906108c SS |
10973 | |
10974 | @enumerate | |
10975 | ||
10976 | @cindex member functions | |
10977 | @item | |
10978 | Member function calls are allowed; you can use expressions like | |
10979 | ||
474c8240 | 10980 | @smallexample |
c906108c | 10981 | count = aml->GetOriginal(x, y) |
474c8240 | 10982 | @end smallexample |
c906108c | 10983 | |
41afff9a | 10984 | @vindex this@r{, inside C@t{++} member functions} |
b37052ae | 10985 | @cindex namespace in C@t{++} |
c906108c SS |
10986 | @item |
10987 | While a member function is active (in the selected stack frame), your | |
10988 | expressions have the same namespace available as the member function; | |
10989 | that is, @value{GDBN} allows implicit references to the class instance | |
b37052ae | 10990 | pointer @code{this} following the same rules as C@t{++}. |
c906108c | 10991 | |
c906108c | 10992 | @cindex call overloaded functions |
d4f3574e | 10993 | @cindex overloaded functions, calling |
b37052ae | 10994 | @cindex type conversions in C@t{++} |
c906108c SS |
10995 | @item |
10996 | You can call overloaded functions; @value{GDBN} resolves the function | |
d4f3574e | 10997 | call to the right definition, with some restrictions. @value{GDBN} does not |
c906108c SS |
10998 | perform overload resolution involving user-defined type conversions, |
10999 | calls to constructors, or instantiations of templates that do not exist | |
11000 | in the program. It also cannot handle ellipsis argument lists or | |
11001 | default arguments. | |
11002 | ||
11003 | It does perform integral conversions and promotions, floating-point | |
11004 | promotions, arithmetic conversions, pointer conversions, conversions of | |
11005 | class objects to base classes, and standard conversions such as those of | |
11006 | functions or arrays to pointers; it requires an exact match on the | |
11007 | number of function arguments. | |
11008 | ||
11009 | Overload resolution is always performed, unless you have specified | |
79a6e687 BW |
11010 | @code{set overload-resolution off}. @xref{Debugging C Plus Plus, |
11011 | ,@value{GDBN} Features for C@t{++}}. | |
c906108c | 11012 | |
d4f3574e | 11013 | You must specify @code{set overload-resolution off} in order to use an |
c906108c SS |
11014 | explicit function signature to call an overloaded function, as in |
11015 | @smallexample | |
11016 | p 'foo(char,int)'('x', 13) | |
11017 | @end smallexample | |
d4f3574e | 11018 | |
c906108c | 11019 | The @value{GDBN} command-completion facility can simplify this; |
79a6e687 | 11020 | see @ref{Completion, ,Command Completion}. |
c906108c | 11021 | |
c906108c SS |
11022 | @cindex reference declarations |
11023 | @item | |
b37052ae EZ |
11024 | @value{GDBN} understands variables declared as C@t{++} references; you can use |
11025 | them in expressions just as you do in C@t{++} source---they are automatically | |
c906108c SS |
11026 | dereferenced. |
11027 | ||
11028 | In the parameter list shown when @value{GDBN} displays a frame, the values of | |
11029 | reference variables are not displayed (unlike other variables); this | |
11030 | avoids clutter, since references are often used for large structures. | |
11031 | The @emph{address} of a reference variable is always shown, unless | |
11032 | you have specified @samp{set print address off}. | |
11033 | ||
11034 | @item | |
b37052ae | 11035 | @value{GDBN} supports the C@t{++} name resolution operator @code{::}---your |
c906108c SS |
11036 | expressions can use it just as expressions in your program do. Since |
11037 | one scope may be defined in another, you can use @code{::} repeatedly if | |
11038 | necessary, for example in an expression like | |
11039 | @samp{@var{scope1}::@var{scope2}::@var{name}}. @value{GDBN} also allows | |
b37052ae | 11040 | resolving name scope by reference to source files, in both C and C@t{++} |
79a6e687 | 11041 | debugging (@pxref{Variables, ,Program Variables}). |
c906108c SS |
11042 | @end enumerate |
11043 | ||
b37052ae | 11044 | In addition, when used with HP's C@t{++} compiler, @value{GDBN} supports |
53a5351d JM |
11045 | calling virtual functions correctly, printing out virtual bases of |
11046 | objects, calling functions in a base subobject, casting objects, and | |
11047 | invoking user-defined operators. | |
c906108c | 11048 | |
6d2ebf8b | 11049 | @node C Defaults |
79a6e687 | 11050 | @subsubsection C and C@t{++} Defaults |
7a292a7a | 11051 | |
b37052ae | 11052 | @cindex C and C@t{++} defaults |
c906108c | 11053 | |
c906108c SS |
11054 | If you allow @value{GDBN} to set type and range checking automatically, they |
11055 | both default to @code{off} whenever the working language changes to | |
b37052ae | 11056 | C or C@t{++}. This happens regardless of whether you or @value{GDBN} |
c906108c | 11057 | selects the working language. |
c906108c SS |
11058 | |
11059 | If you allow @value{GDBN} to set the language automatically, it | |
11060 | recognizes source files whose names end with @file{.c}, @file{.C}, or | |
11061 | @file{.cc}, etc, and when @value{GDBN} enters code compiled from one of | |
b37052ae | 11062 | these files, it sets the working language to C or C@t{++}. |
79a6e687 | 11063 | @xref{Automatically, ,Having @value{GDBN} Infer the Source Language}, |
c906108c SS |
11064 | for further details. |
11065 | ||
c906108c SS |
11066 | @c Type checking is (a) primarily motivated by Modula-2, and (b) |
11067 | @c unimplemented. If (b) changes, it might make sense to let this node | |
11068 | @c appear even if Mod-2 does not, but meanwhile ignore it. roland 16jul93. | |
7a292a7a | 11069 | |
6d2ebf8b | 11070 | @node C Checks |
79a6e687 | 11071 | @subsubsection C and C@t{++} Type and Range Checks |
7a292a7a | 11072 | |
b37052ae | 11073 | @cindex C and C@t{++} checks |
c906108c | 11074 | |
b37052ae | 11075 | By default, when @value{GDBN} parses C or C@t{++} expressions, type checking |
c906108c SS |
11076 | is not used. However, if you turn type checking on, @value{GDBN} |
11077 | considers two variables type equivalent if: | |
11078 | ||
11079 | @itemize @bullet | |
11080 | @item | |
11081 | The two variables are structured and have the same structure, union, or | |
11082 | enumerated tag. | |
11083 | ||
11084 | @item | |
11085 | The two variables have the same type name, or types that have been | |
11086 | declared equivalent through @code{typedef}. | |
11087 | ||
11088 | @ignore | |
11089 | @c leaving this out because neither J Gilmore nor R Pesch understand it. | |
11090 | @c FIXME--beers? | |
11091 | @item | |
11092 | The two @code{struct}, @code{union}, or @code{enum} variables are | |
11093 | declared in the same declaration. (Note: this may not be true for all C | |
11094 | compilers.) | |
11095 | @end ignore | |
11096 | @end itemize | |
11097 | ||
11098 | Range checking, if turned on, is done on mathematical operations. Array | |
11099 | indices are not checked, since they are often used to index a pointer | |
11100 | that is not itself an array. | |
c906108c | 11101 | |
6d2ebf8b | 11102 | @node Debugging C |
c906108c | 11103 | @subsubsection @value{GDBN} and C |
c906108c SS |
11104 | |
11105 | The @code{set print union} and @code{show print union} commands apply to | |
11106 | the @code{union} type. When set to @samp{on}, any @code{union} that is | |
7a292a7a SS |
11107 | inside a @code{struct} or @code{class} is also printed. Otherwise, it |
11108 | appears as @samp{@{...@}}. | |
c906108c SS |
11109 | |
11110 | The @code{@@} operator aids in the debugging of dynamic arrays, formed | |
11111 | with pointers and a memory allocation function. @xref{Expressions, | |
11112 | ,Expressions}. | |
11113 | ||
79a6e687 BW |
11114 | @node Debugging C Plus Plus |
11115 | @subsubsection @value{GDBN} Features for C@t{++} | |
c906108c | 11116 | |
b37052ae | 11117 | @cindex commands for C@t{++} |
7a292a7a | 11118 | |
b37052ae EZ |
11119 | Some @value{GDBN} commands are particularly useful with C@t{++}, and some are |
11120 | designed specifically for use with C@t{++}. Here is a summary: | |
c906108c SS |
11121 | |
11122 | @table @code | |
11123 | @cindex break in overloaded functions | |
11124 | @item @r{breakpoint menus} | |
11125 | When you want a breakpoint in a function whose name is overloaded, | |
6ba66d6a JB |
11126 | @value{GDBN} has the capability to display a menu of possible breakpoint |
11127 | locations to help you specify which function definition you want. | |
11128 | @xref{Ambiguous Expressions,,Ambiguous Expressions}. | |
c906108c | 11129 | |
b37052ae | 11130 | @cindex overloading in C@t{++} |
c906108c SS |
11131 | @item rbreak @var{regex} |
11132 | Setting breakpoints using regular expressions is helpful for setting | |
11133 | breakpoints on overloaded functions that are not members of any special | |
11134 | classes. | |
79a6e687 | 11135 | @xref{Set Breaks, ,Setting Breakpoints}. |
c906108c | 11136 | |
b37052ae | 11137 | @cindex C@t{++} exception handling |
c906108c SS |
11138 | @item catch throw |
11139 | @itemx catch catch | |
b37052ae | 11140 | Debug C@t{++} exception handling using these commands. @xref{Set |
79a6e687 | 11141 | Catchpoints, , Setting Catchpoints}. |
c906108c SS |
11142 | |
11143 | @cindex inheritance | |
11144 | @item ptype @var{typename} | |
11145 | Print inheritance relationships as well as other information for type | |
11146 | @var{typename}. | |
11147 | @xref{Symbols, ,Examining the Symbol Table}. | |
11148 | ||
b37052ae | 11149 | @cindex C@t{++} symbol display |
c906108c SS |
11150 | @item set print demangle |
11151 | @itemx show print demangle | |
11152 | @itemx set print asm-demangle | |
11153 | @itemx show print asm-demangle | |
b37052ae EZ |
11154 | Control whether C@t{++} symbols display in their source form, both when |
11155 | displaying code as C@t{++} source and when displaying disassemblies. | |
79a6e687 | 11156 | @xref{Print Settings, ,Print Settings}. |
c906108c SS |
11157 | |
11158 | @item set print object | |
11159 | @itemx show print object | |
11160 | Choose whether to print derived (actual) or declared types of objects. | |
79a6e687 | 11161 | @xref{Print Settings, ,Print Settings}. |
c906108c SS |
11162 | |
11163 | @item set print vtbl | |
11164 | @itemx show print vtbl | |
11165 | Control the format for printing virtual function tables. | |
79a6e687 | 11166 | @xref{Print Settings, ,Print Settings}. |
c906108c | 11167 | (The @code{vtbl} commands do not work on programs compiled with the HP |
b37052ae | 11168 | ANSI C@t{++} compiler (@code{aCC}).) |
c906108c SS |
11169 | |
11170 | @kindex set overload-resolution | |
d4f3574e | 11171 | @cindex overloaded functions, overload resolution |
c906108c | 11172 | @item set overload-resolution on |
b37052ae | 11173 | Enable overload resolution for C@t{++} expression evaluation. The default |
c906108c SS |
11174 | is on. For overloaded functions, @value{GDBN} evaluates the arguments |
11175 | and searches for a function whose signature matches the argument types, | |
79a6e687 BW |
11176 | using the standard C@t{++} conversion rules (see @ref{C Plus Plus |
11177 | Expressions, ,C@t{++} Expressions}, for details). | |
11178 | If it cannot find a match, it emits a message. | |
c906108c SS |
11179 | |
11180 | @item set overload-resolution off | |
b37052ae | 11181 | Disable overload resolution for C@t{++} expression evaluation. For |
c906108c SS |
11182 | overloaded functions that are not class member functions, @value{GDBN} |
11183 | chooses the first function of the specified name that it finds in the | |
11184 | symbol table, whether or not its arguments are of the correct type. For | |
11185 | overloaded functions that are class member functions, @value{GDBN} | |
11186 | searches for a function whose signature @emph{exactly} matches the | |
11187 | argument types. | |
c906108c | 11188 | |
9c16f35a EZ |
11189 | @kindex show overload-resolution |
11190 | @item show overload-resolution | |
11191 | Show the current setting of overload resolution. | |
11192 | ||
c906108c SS |
11193 | @item @r{Overloaded symbol names} |
11194 | You can specify a particular definition of an overloaded symbol, using | |
b37052ae | 11195 | the same notation that is used to declare such symbols in C@t{++}: type |
c906108c SS |
11196 | @code{@var{symbol}(@var{types})} rather than just @var{symbol}. You can |
11197 | also use the @value{GDBN} command-line word completion facilities to list the | |
11198 | available choices, or to finish the type list for you. | |
79a6e687 | 11199 | @xref{Completion,, Command Completion}, for details on how to do this. |
c906108c | 11200 | @end table |
c906108c | 11201 | |
febe4383 TJB |
11202 | @node Decimal Floating Point |
11203 | @subsubsection Decimal Floating Point format | |
11204 | @cindex decimal floating point format | |
11205 | ||
11206 | @value{GDBN} can examine, set and perform computations with numbers in | |
11207 | decimal floating point format, which in the C language correspond to the | |
11208 | @code{_Decimal32}, @code{_Decimal64} and @code{_Decimal128} types as | |
11209 | specified by the extension to support decimal floating-point arithmetic. | |
11210 | ||
11211 | There are two encodings in use, depending on the architecture: BID (Binary | |
11212 | Integer Decimal) for x86 and x86-64, and DPD (Densely Packed Decimal) for | |
99e008fe | 11213 | PowerPC. @value{GDBN} will use the appropriate encoding for the configured |
febe4383 TJB |
11214 | target. |
11215 | ||
11216 | Because of a limitation in @file{libdecnumber}, the library used by @value{GDBN} | |
11217 | to manipulate decimal floating point numbers, it is not possible to convert | |
11218 | (using a cast, for example) integers wider than 32-bit to decimal float. | |
11219 | ||
11220 | In addition, in order to imitate @value{GDBN}'s behaviour with binary floating | |
11221 | point computations, error checking in decimal float operations ignores | |
11222 | underflow, overflow and divide by zero exceptions. | |
11223 | ||
4acd40f3 | 11224 | In the PowerPC architecture, @value{GDBN} provides a set of pseudo-registers |
99e008fe EZ |
11225 | to inspect @code{_Decimal128} values stored in floating point registers. |
11226 | See @ref{PowerPC,,PowerPC} for more details. | |
4acd40f3 | 11227 | |
b37303ee AF |
11228 | @node Objective-C |
11229 | @subsection Objective-C | |
11230 | ||
11231 | @cindex Objective-C | |
11232 | This section provides information about some commands and command | |
721c2651 EZ |
11233 | options that are useful for debugging Objective-C code. See also |
11234 | @ref{Symbols, info classes}, and @ref{Symbols, info selectors}, for a | |
11235 | few more commands specific to Objective-C support. | |
b37303ee AF |
11236 | |
11237 | @menu | |
b383017d RM |
11238 | * Method Names in Commands:: |
11239 | * The Print Command with Objective-C:: | |
b37303ee AF |
11240 | @end menu |
11241 | ||
c8f4133a | 11242 | @node Method Names in Commands |
b37303ee AF |
11243 | @subsubsection Method Names in Commands |
11244 | ||
11245 | The following commands have been extended to accept Objective-C method | |
11246 | names as line specifications: | |
11247 | ||
11248 | @kindex clear@r{, and Objective-C} | |
11249 | @kindex break@r{, and Objective-C} | |
11250 | @kindex info line@r{, and Objective-C} | |
11251 | @kindex jump@r{, and Objective-C} | |
11252 | @kindex list@r{, and Objective-C} | |
11253 | @itemize | |
11254 | @item @code{clear} | |
11255 | @item @code{break} | |
11256 | @item @code{info line} | |
11257 | @item @code{jump} | |
11258 | @item @code{list} | |
11259 | @end itemize | |
11260 | ||
11261 | A fully qualified Objective-C method name is specified as | |
11262 | ||
11263 | @smallexample | |
11264 | -[@var{Class} @var{methodName}] | |
11265 | @end smallexample | |
11266 | ||
c552b3bb JM |
11267 | where the minus sign is used to indicate an instance method and a |
11268 | plus sign (not shown) is used to indicate a class method. The class | |
11269 | name @var{Class} and method name @var{methodName} are enclosed in | |
11270 | brackets, similar to the way messages are specified in Objective-C | |
11271 | source code. For example, to set a breakpoint at the @code{create} | |
11272 | instance method of class @code{Fruit} in the program currently being | |
11273 | debugged, enter: | |
b37303ee AF |
11274 | |
11275 | @smallexample | |
11276 | break -[Fruit create] | |
11277 | @end smallexample | |
11278 | ||
11279 | To list ten program lines around the @code{initialize} class method, | |
11280 | enter: | |
11281 | ||
11282 | @smallexample | |
11283 | list +[NSText initialize] | |
11284 | @end smallexample | |
11285 | ||
c552b3bb JM |
11286 | In the current version of @value{GDBN}, the plus or minus sign is |
11287 | required. In future versions of @value{GDBN}, the plus or minus | |
11288 | sign will be optional, but you can use it to narrow the search. It | |
11289 | is also possible to specify just a method name: | |
b37303ee AF |
11290 | |
11291 | @smallexample | |
11292 | break create | |
11293 | @end smallexample | |
11294 | ||
11295 | You must specify the complete method name, including any colons. If | |
11296 | your program's source files contain more than one @code{create} method, | |
11297 | you'll be presented with a numbered list of classes that implement that | |
11298 | method. Indicate your choice by number, or type @samp{0} to exit if | |
11299 | none apply. | |
11300 | ||
11301 | As another example, to clear a breakpoint established at the | |
11302 | @code{makeKeyAndOrderFront:} method of the @code{NSWindow} class, enter: | |
11303 | ||
11304 | @smallexample | |
11305 | clear -[NSWindow makeKeyAndOrderFront:] | |
11306 | @end smallexample | |
11307 | ||
11308 | @node The Print Command with Objective-C | |
11309 | @subsubsection The Print Command With Objective-C | |
721c2651 | 11310 | @cindex Objective-C, print objects |
c552b3bb JM |
11311 | @kindex print-object |
11312 | @kindex po @r{(@code{print-object})} | |
b37303ee | 11313 | |
c552b3bb | 11314 | The print command has also been extended to accept methods. For example: |
b37303ee AF |
11315 | |
11316 | @smallexample | |
c552b3bb | 11317 | print -[@var{object} hash] |
b37303ee AF |
11318 | @end smallexample |
11319 | ||
11320 | @cindex print an Objective-C object description | |
c552b3bb JM |
11321 | @cindex @code{_NSPrintForDebugger}, and printing Objective-C objects |
11322 | @noindent | |
11323 | will tell @value{GDBN} to send the @code{hash} message to @var{object} | |
11324 | and print the result. Also, an additional command has been added, | |
11325 | @code{print-object} or @code{po} for short, which is meant to print | |
11326 | the description of an object. However, this command may only work | |
11327 | with certain Objective-C libraries that have a particular hook | |
11328 | function, @code{_NSPrintForDebugger}, defined. | |
b37303ee | 11329 | |
09d4efe1 EZ |
11330 | @node Fortran |
11331 | @subsection Fortran | |
11332 | @cindex Fortran-specific support in @value{GDBN} | |
11333 | ||
814e32d7 WZ |
11334 | @value{GDBN} can be used to debug programs written in Fortran, but it |
11335 | currently supports only the features of Fortran 77 language. | |
11336 | ||
11337 | @cindex trailing underscore, in Fortran symbols | |
11338 | Some Fortran compilers (@sc{gnu} Fortran 77 and Fortran 95 compilers | |
11339 | among them) append an underscore to the names of variables and | |
11340 | functions. When you debug programs compiled by those compilers, you | |
11341 | will need to refer to variables and functions with a trailing | |
11342 | underscore. | |
11343 | ||
11344 | @menu | |
11345 | * Fortran Operators:: Fortran operators and expressions | |
11346 | * Fortran Defaults:: Default settings for Fortran | |
79a6e687 | 11347 | * Special Fortran Commands:: Special @value{GDBN} commands for Fortran |
814e32d7 WZ |
11348 | @end menu |
11349 | ||
11350 | @node Fortran Operators | |
79a6e687 | 11351 | @subsubsection Fortran Operators and Expressions |
814e32d7 WZ |
11352 | |
11353 | @cindex Fortran operators and expressions | |
11354 | ||
11355 | Operators must be defined on values of specific types. For instance, | |
11356 | @code{+} is defined on numbers, but not on characters or other non- | |
ff2587ec | 11357 | arithmetic types. Operators are often defined on groups of types. |
814e32d7 WZ |
11358 | |
11359 | @table @code | |
11360 | @item ** | |
99e008fe | 11361 | The exponentiation operator. It raises the first operand to the power |
814e32d7 WZ |
11362 | of the second one. |
11363 | ||
11364 | @item : | |
11365 | The range operator. Normally used in the form of array(low:high) to | |
11366 | represent a section of array. | |
68837c9d MD |
11367 | |
11368 | @item % | |
11369 | The access component operator. Normally used to access elements in derived | |
11370 | types. Also suitable for unions. As unions aren't part of regular Fortran, | |
11371 | this can only happen when accessing a register that uses a gdbarch-defined | |
11372 | union type. | |
814e32d7 WZ |
11373 | @end table |
11374 | ||
11375 | @node Fortran Defaults | |
11376 | @subsubsection Fortran Defaults | |
11377 | ||
11378 | @cindex Fortran Defaults | |
11379 | ||
11380 | Fortran symbols are usually case-insensitive, so @value{GDBN} by | |
11381 | default uses case-insensitive matches for Fortran symbols. You can | |
11382 | change that with the @samp{set case-insensitive} command, see | |
11383 | @ref{Symbols}, for the details. | |
11384 | ||
79a6e687 BW |
11385 | @node Special Fortran Commands |
11386 | @subsubsection Special Fortran Commands | |
814e32d7 WZ |
11387 | |
11388 | @cindex Special Fortran commands | |
11389 | ||
db2e3e2e BW |
11390 | @value{GDBN} has some commands to support Fortran-specific features, |
11391 | such as displaying common blocks. | |
814e32d7 | 11392 | |
09d4efe1 EZ |
11393 | @table @code |
11394 | @cindex @code{COMMON} blocks, Fortran | |
11395 | @kindex info common | |
11396 | @item info common @r{[}@var{common-name}@r{]} | |
11397 | This command prints the values contained in the Fortran @code{COMMON} | |
11398 | block whose name is @var{common-name}. With no argument, the names of | |
d52fb0e9 | 11399 | all @code{COMMON} blocks visible at the current program location are |
09d4efe1 EZ |
11400 | printed. |
11401 | @end table | |
11402 | ||
9c16f35a EZ |
11403 | @node Pascal |
11404 | @subsection Pascal | |
11405 | ||
11406 | @cindex Pascal support in @value{GDBN}, limitations | |
11407 | Debugging Pascal programs which use sets, subranges, file variables, or | |
11408 | nested functions does not currently work. @value{GDBN} does not support | |
11409 | entering expressions, printing values, or similar features using Pascal | |
11410 | syntax. | |
11411 | ||
11412 | The Pascal-specific command @code{set print pascal_static-members} | |
11413 | controls whether static members of Pascal objects are displayed. | |
11414 | @xref{Print Settings, pascal_static-members}. | |
11415 | ||
09d4efe1 | 11416 | @node Modula-2 |
c906108c | 11417 | @subsection Modula-2 |
7a292a7a | 11418 | |
d4f3574e | 11419 | @cindex Modula-2, @value{GDBN} support |
c906108c SS |
11420 | |
11421 | The extensions made to @value{GDBN} to support Modula-2 only support | |
11422 | output from the @sc{gnu} Modula-2 compiler (which is currently being | |
11423 | developed). Other Modula-2 compilers are not currently supported, and | |
11424 | attempting to debug executables produced by them is most likely | |
11425 | to give an error as @value{GDBN} reads in the executable's symbol | |
11426 | table. | |
11427 | ||
11428 | @cindex expressions in Modula-2 | |
11429 | @menu | |
11430 | * M2 Operators:: Built-in operators | |
11431 | * Built-In Func/Proc:: Built-in functions and procedures | |
11432 | * M2 Constants:: Modula-2 constants | |
72019c9c | 11433 | * M2 Types:: Modula-2 types |
c906108c SS |
11434 | * M2 Defaults:: Default settings for Modula-2 |
11435 | * Deviations:: Deviations from standard Modula-2 | |
11436 | * M2 Checks:: Modula-2 type and range checks | |
11437 | * M2 Scope:: The scope operators @code{::} and @code{.} | |
11438 | * GDB/M2:: @value{GDBN} and Modula-2 | |
11439 | @end menu | |
11440 | ||
6d2ebf8b | 11441 | @node M2 Operators |
c906108c SS |
11442 | @subsubsection Operators |
11443 | @cindex Modula-2 operators | |
11444 | ||
11445 | Operators must be defined on values of specific types. For instance, | |
11446 | @code{+} is defined on numbers, but not on structures. Operators are | |
11447 | often defined on groups of types. For the purposes of Modula-2, the | |
11448 | following definitions hold: | |
11449 | ||
11450 | @itemize @bullet | |
11451 | ||
11452 | @item | |
11453 | @emph{Integral types} consist of @code{INTEGER}, @code{CARDINAL}, and | |
11454 | their subranges. | |
11455 | ||
11456 | @item | |
11457 | @emph{Character types} consist of @code{CHAR} and its subranges. | |
11458 | ||
11459 | @item | |
11460 | @emph{Floating-point types} consist of @code{REAL}. | |
11461 | ||
11462 | @item | |
11463 | @emph{Pointer types} consist of anything declared as @code{POINTER TO | |
11464 | @var{type}}. | |
11465 | ||
11466 | @item | |
11467 | @emph{Scalar types} consist of all of the above. | |
11468 | ||
11469 | @item | |
11470 | @emph{Set types} consist of @code{SET} and @code{BITSET} types. | |
11471 | ||
11472 | @item | |
11473 | @emph{Boolean types} consist of @code{BOOLEAN}. | |
11474 | @end itemize | |
11475 | ||
11476 | @noindent | |
11477 | The following operators are supported, and appear in order of | |
11478 | increasing precedence: | |
11479 | ||
11480 | @table @code | |
11481 | @item , | |
11482 | Function argument or array index separator. | |
11483 | ||
11484 | @item := | |
11485 | Assignment. The value of @var{var} @code{:=} @var{value} is | |
11486 | @var{value}. | |
11487 | ||
11488 | @item <@r{, }> | |
11489 | Less than, greater than on integral, floating-point, or enumerated | |
11490 | types. | |
11491 | ||
11492 | @item <=@r{, }>= | |
96a2c332 | 11493 | Less than or equal to, greater than or equal to |
c906108c SS |
11494 | on integral, floating-point and enumerated types, or set inclusion on |
11495 | set types. Same precedence as @code{<}. | |
11496 | ||
11497 | @item =@r{, }<>@r{, }# | |
11498 | Equality and two ways of expressing inequality, valid on scalar types. | |
11499 | Same precedence as @code{<}. In @value{GDBN} scripts, only @code{<>} is | |
11500 | available for inequality, since @code{#} conflicts with the script | |
11501 | comment character. | |
11502 | ||
11503 | @item IN | |
11504 | Set membership. Defined on set types and the types of their members. | |
11505 | Same precedence as @code{<}. | |
11506 | ||
11507 | @item OR | |
11508 | Boolean disjunction. Defined on boolean types. | |
11509 | ||
11510 | @item AND@r{, }& | |
d4f3574e | 11511 | Boolean conjunction. Defined on boolean types. |
c906108c SS |
11512 | |
11513 | @item @@ | |
11514 | The @value{GDBN} ``artificial array'' operator (@pxref{Expressions, ,Expressions}). | |
11515 | ||
11516 | @item +@r{, }- | |
11517 | Addition and subtraction on integral and floating-point types, or union | |
11518 | and difference on set types. | |
11519 | ||
11520 | @item * | |
11521 | Multiplication on integral and floating-point types, or set intersection | |
11522 | on set types. | |
11523 | ||
11524 | @item / | |
11525 | Division on floating-point types, or symmetric set difference on set | |
11526 | types. Same precedence as @code{*}. | |
11527 | ||
11528 | @item DIV@r{, }MOD | |
11529 | Integer division and remainder. Defined on integral types. Same | |
11530 | precedence as @code{*}. | |
11531 | ||
11532 | @item - | |
99e008fe | 11533 | Negative. Defined on @code{INTEGER} and @code{REAL} data. |
c906108c SS |
11534 | |
11535 | @item ^ | |
11536 | Pointer dereferencing. Defined on pointer types. | |
11537 | ||
11538 | @item NOT | |
11539 | Boolean negation. Defined on boolean types. Same precedence as | |
11540 | @code{^}. | |
11541 | ||
11542 | @item . | |
11543 | @code{RECORD} field selector. Defined on @code{RECORD} data. Same | |
11544 | precedence as @code{^}. | |
11545 | ||
11546 | @item [] | |
11547 | Array indexing. Defined on @code{ARRAY} data. Same precedence as @code{^}. | |
11548 | ||
11549 | @item () | |
11550 | Procedure argument list. Defined on @code{PROCEDURE} objects. Same precedence | |
11551 | as @code{^}. | |
11552 | ||
11553 | @item ::@r{, }. | |
11554 | @value{GDBN} and Modula-2 scope operators. | |
11555 | @end table | |
11556 | ||
11557 | @quotation | |
72019c9c | 11558 | @emph{Warning:} Set expressions and their operations are not yet supported, so @value{GDBN} |
c906108c SS |
11559 | treats the use of the operator @code{IN}, or the use of operators |
11560 | @code{+}, @code{-}, @code{*}, @code{/}, @code{=}, , @code{<>}, @code{#}, | |
11561 | @code{<=}, and @code{>=} on sets as an error. | |
11562 | @end quotation | |
11563 | ||
cb51c4e0 | 11564 | |
6d2ebf8b | 11565 | @node Built-In Func/Proc |
79a6e687 | 11566 | @subsubsection Built-in Functions and Procedures |
cb51c4e0 | 11567 | @cindex Modula-2 built-ins |
c906108c SS |
11568 | |
11569 | Modula-2 also makes available several built-in procedures and functions. | |
11570 | In describing these, the following metavariables are used: | |
11571 | ||
11572 | @table @var | |
11573 | ||
11574 | @item a | |
11575 | represents an @code{ARRAY} variable. | |
11576 | ||
11577 | @item c | |
11578 | represents a @code{CHAR} constant or variable. | |
11579 | ||
11580 | @item i | |
11581 | represents a variable or constant of integral type. | |
11582 | ||
11583 | @item m | |
11584 | represents an identifier that belongs to a set. Generally used in the | |
11585 | same function with the metavariable @var{s}. The type of @var{s} should | |
11586 | be @code{SET OF @var{mtype}} (where @var{mtype} is the type of @var{m}). | |
11587 | ||
11588 | @item n | |
11589 | represents a variable or constant of integral or floating-point type. | |
11590 | ||
11591 | @item r | |
11592 | represents a variable or constant of floating-point type. | |
11593 | ||
11594 | @item t | |
11595 | represents a type. | |
11596 | ||
11597 | @item v | |
11598 | represents a variable. | |
11599 | ||
11600 | @item x | |
11601 | represents a variable or constant of one of many types. See the | |
11602 | explanation of the function for details. | |
11603 | @end table | |
11604 | ||
11605 | All Modula-2 built-in procedures also return a result, described below. | |
11606 | ||
11607 | @table @code | |
11608 | @item ABS(@var{n}) | |
11609 | Returns the absolute value of @var{n}. | |
11610 | ||
11611 | @item CAP(@var{c}) | |
11612 | If @var{c} is a lower case letter, it returns its upper case | |
c3f6f71d | 11613 | equivalent, otherwise it returns its argument. |
c906108c SS |
11614 | |
11615 | @item CHR(@var{i}) | |
11616 | Returns the character whose ordinal value is @var{i}. | |
11617 | ||
11618 | @item DEC(@var{v}) | |
c3f6f71d | 11619 | Decrements the value in the variable @var{v} by one. Returns the new value. |
c906108c SS |
11620 | |
11621 | @item DEC(@var{v},@var{i}) | |
11622 | Decrements the value in the variable @var{v} by @var{i}. Returns the | |
11623 | new value. | |
11624 | ||
11625 | @item EXCL(@var{m},@var{s}) | |
11626 | Removes the element @var{m} from the set @var{s}. Returns the new | |
11627 | set. | |
11628 | ||
11629 | @item FLOAT(@var{i}) | |
11630 | Returns the floating point equivalent of the integer @var{i}. | |
11631 | ||
11632 | @item HIGH(@var{a}) | |
11633 | Returns the index of the last member of @var{a}. | |
11634 | ||
11635 | @item INC(@var{v}) | |
c3f6f71d | 11636 | Increments the value in the variable @var{v} by one. Returns the new value. |
c906108c SS |
11637 | |
11638 | @item INC(@var{v},@var{i}) | |
11639 | Increments the value in the variable @var{v} by @var{i}. Returns the | |
11640 | new value. | |
11641 | ||
11642 | @item INCL(@var{m},@var{s}) | |
11643 | Adds the element @var{m} to the set @var{s} if it is not already | |
11644 | there. Returns the new set. | |
11645 | ||
11646 | @item MAX(@var{t}) | |
11647 | Returns the maximum value of the type @var{t}. | |
11648 | ||
11649 | @item MIN(@var{t}) | |
11650 | Returns the minimum value of the type @var{t}. | |
11651 | ||
11652 | @item ODD(@var{i}) | |
11653 | Returns boolean TRUE if @var{i} is an odd number. | |
11654 | ||
11655 | @item ORD(@var{x}) | |
11656 | Returns the ordinal value of its argument. For example, the ordinal | |
c3f6f71d JM |
11657 | value of a character is its @sc{ascii} value (on machines supporting the |
11658 | @sc{ascii} character set). @var{x} must be of an ordered type, which include | |
c906108c SS |
11659 | integral, character and enumerated types. |
11660 | ||
11661 | @item SIZE(@var{x}) | |
11662 | Returns the size of its argument. @var{x} can be a variable or a type. | |
11663 | ||
11664 | @item TRUNC(@var{r}) | |
11665 | Returns the integral part of @var{r}. | |
11666 | ||
844781a1 GM |
11667 | @item TSIZE(@var{x}) |
11668 | Returns the size of its argument. @var{x} can be a variable or a type. | |
11669 | ||
c906108c SS |
11670 | @item VAL(@var{t},@var{i}) |
11671 | Returns the member of the type @var{t} whose ordinal value is @var{i}. | |
11672 | @end table | |
11673 | ||
11674 | @quotation | |
11675 | @emph{Warning:} Sets and their operations are not yet supported, so | |
11676 | @value{GDBN} treats the use of procedures @code{INCL} and @code{EXCL} as | |
11677 | an error. | |
11678 | @end quotation | |
11679 | ||
11680 | @cindex Modula-2 constants | |
6d2ebf8b | 11681 | @node M2 Constants |
c906108c SS |
11682 | @subsubsection Constants |
11683 | ||
11684 | @value{GDBN} allows you to express the constants of Modula-2 in the following | |
11685 | ways: | |
11686 | ||
11687 | @itemize @bullet | |
11688 | ||
11689 | @item | |
11690 | Integer constants are simply a sequence of digits. When used in an | |
11691 | expression, a constant is interpreted to be type-compatible with the | |
11692 | rest of the expression. Hexadecimal integers are specified by a | |
11693 | trailing @samp{H}, and octal integers by a trailing @samp{B}. | |
11694 | ||
11695 | @item | |
11696 | Floating point constants appear as a sequence of digits, followed by a | |
11697 | decimal point and another sequence of digits. An optional exponent can | |
11698 | then be specified, in the form @samp{E@r{[}+@r{|}-@r{]}@var{nnn}}, where | |
11699 | @samp{@r{[}+@r{|}-@r{]}@var{nnn}} is the desired exponent. All of the | |
11700 | digits of the floating point constant must be valid decimal (base 10) | |
11701 | digits. | |
11702 | ||
11703 | @item | |
11704 | Character constants consist of a single character enclosed by a pair of | |
11705 | like quotes, either single (@code{'}) or double (@code{"}). They may | |
c3f6f71d | 11706 | also be expressed by their ordinal value (their @sc{ascii} value, usually) |
c906108c SS |
11707 | followed by a @samp{C}. |
11708 | ||
11709 | @item | |
11710 | String constants consist of a sequence of characters enclosed by a | |
11711 | pair of like quotes, either single (@code{'}) or double (@code{"}). | |
11712 | Escape sequences in the style of C are also allowed. @xref{C | |
79a6e687 | 11713 | Constants, ,C and C@t{++} Constants}, for a brief explanation of escape |
c906108c SS |
11714 | sequences. |
11715 | ||
11716 | @item | |
11717 | Enumerated constants consist of an enumerated identifier. | |
11718 | ||
11719 | @item | |
11720 | Boolean constants consist of the identifiers @code{TRUE} and | |
11721 | @code{FALSE}. | |
11722 | ||
11723 | @item | |
11724 | Pointer constants consist of integral values only. | |
11725 | ||
11726 | @item | |
11727 | Set constants are not yet supported. | |
11728 | @end itemize | |
11729 | ||
72019c9c GM |
11730 | @node M2 Types |
11731 | @subsubsection Modula-2 Types | |
11732 | @cindex Modula-2 types | |
11733 | ||
11734 | Currently @value{GDBN} can print the following data types in Modula-2 | |
11735 | syntax: array types, record types, set types, pointer types, procedure | |
11736 | types, enumerated types, subrange types and base types. You can also | |
11737 | print the contents of variables declared using these type. | |
11738 | This section gives a number of simple source code examples together with | |
11739 | sample @value{GDBN} sessions. | |
11740 | ||
11741 | The first example contains the following section of code: | |
11742 | ||
11743 | @smallexample | |
11744 | VAR | |
11745 | s: SET OF CHAR ; | |
11746 | r: [20..40] ; | |
11747 | @end smallexample | |
11748 | ||
11749 | @noindent | |
11750 | and you can request @value{GDBN} to interrogate the type and value of | |
11751 | @code{r} and @code{s}. | |
11752 | ||
11753 | @smallexample | |
11754 | (@value{GDBP}) print s | |
11755 | @{'A'..'C', 'Z'@} | |
11756 | (@value{GDBP}) ptype s | |
11757 | SET OF CHAR | |
11758 | (@value{GDBP}) print r | |
11759 | 21 | |
11760 | (@value{GDBP}) ptype r | |
11761 | [20..40] | |
11762 | @end smallexample | |
11763 | ||
11764 | @noindent | |
11765 | Likewise if your source code declares @code{s} as: | |
11766 | ||
11767 | @smallexample | |
11768 | VAR | |
11769 | s: SET ['A'..'Z'] ; | |
11770 | @end smallexample | |
11771 | ||
11772 | @noindent | |
11773 | then you may query the type of @code{s} by: | |
11774 | ||
11775 | @smallexample | |
11776 | (@value{GDBP}) ptype s | |
11777 | type = SET ['A'..'Z'] | |
11778 | @end smallexample | |
11779 | ||
11780 | @noindent | |
11781 | Note that at present you cannot interactively manipulate set | |
11782 | expressions using the debugger. | |
11783 | ||
11784 | The following example shows how you might declare an array in Modula-2 | |
11785 | and how you can interact with @value{GDBN} to print its type and contents: | |
11786 | ||
11787 | @smallexample | |
11788 | VAR | |
11789 | s: ARRAY [-10..10] OF CHAR ; | |
11790 | @end smallexample | |
11791 | ||
11792 | @smallexample | |
11793 | (@value{GDBP}) ptype s | |
11794 | ARRAY [-10..10] OF CHAR | |
11795 | @end smallexample | |
11796 | ||
11797 | Note that the array handling is not yet complete and although the type | |
11798 | is printed correctly, expression handling still assumes that all | |
11799 | arrays have a lower bound of zero and not @code{-10} as in the example | |
844781a1 | 11800 | above. |
72019c9c GM |
11801 | |
11802 | Here are some more type related Modula-2 examples: | |
11803 | ||
11804 | @smallexample | |
11805 | TYPE | |
11806 | colour = (blue, red, yellow, green) ; | |
11807 | t = [blue..yellow] ; | |
11808 | VAR | |
11809 | s: t ; | |
11810 | BEGIN | |
11811 | s := blue ; | |
11812 | @end smallexample | |
11813 | ||
11814 | @noindent | |
11815 | The @value{GDBN} interaction shows how you can query the data type | |
11816 | and value of a variable. | |
11817 | ||
11818 | @smallexample | |
11819 | (@value{GDBP}) print s | |
11820 | $1 = blue | |
11821 | (@value{GDBP}) ptype t | |
11822 | type = [blue..yellow] | |
11823 | @end smallexample | |
11824 | ||
11825 | @noindent | |
11826 | In this example a Modula-2 array is declared and its contents | |
11827 | displayed. Observe that the contents are written in the same way as | |
11828 | their @code{C} counterparts. | |
11829 | ||
11830 | @smallexample | |
11831 | VAR | |
11832 | s: ARRAY [1..5] OF CARDINAL ; | |
11833 | BEGIN | |
11834 | s[1] := 1 ; | |
11835 | @end smallexample | |
11836 | ||
11837 | @smallexample | |
11838 | (@value{GDBP}) print s | |
11839 | $1 = @{1, 0, 0, 0, 0@} | |
11840 | (@value{GDBP}) ptype s | |
11841 | type = ARRAY [1..5] OF CARDINAL | |
11842 | @end smallexample | |
11843 | ||
11844 | The Modula-2 language interface to @value{GDBN} also understands | |
11845 | pointer types as shown in this example: | |
11846 | ||
11847 | @smallexample | |
11848 | VAR | |
11849 | s: POINTER TO ARRAY [1..5] OF CARDINAL ; | |
11850 | BEGIN | |
11851 | NEW(s) ; | |
11852 | s^[1] := 1 ; | |
11853 | @end smallexample | |
11854 | ||
11855 | @noindent | |
11856 | and you can request that @value{GDBN} describes the type of @code{s}. | |
11857 | ||
11858 | @smallexample | |
11859 | (@value{GDBP}) ptype s | |
11860 | type = POINTER TO ARRAY [1..5] OF CARDINAL | |
11861 | @end smallexample | |
11862 | ||
11863 | @value{GDBN} handles compound types as we can see in this example. | |
11864 | Here we combine array types, record types, pointer types and subrange | |
11865 | types: | |
11866 | ||
11867 | @smallexample | |
11868 | TYPE | |
11869 | foo = RECORD | |
11870 | f1: CARDINAL ; | |
11871 | f2: CHAR ; | |
11872 | f3: myarray ; | |
11873 | END ; | |
11874 | ||
11875 | myarray = ARRAY myrange OF CARDINAL ; | |
11876 | myrange = [-2..2] ; | |
11877 | VAR | |
11878 | s: POINTER TO ARRAY myrange OF foo ; | |
11879 | @end smallexample | |
11880 | ||
11881 | @noindent | |
11882 | and you can ask @value{GDBN} to describe the type of @code{s} as shown | |
11883 | below. | |
11884 | ||
11885 | @smallexample | |
11886 | (@value{GDBP}) ptype s | |
11887 | type = POINTER TO ARRAY [-2..2] OF foo = RECORD | |
11888 | f1 : CARDINAL; | |
11889 | f2 : CHAR; | |
11890 | f3 : ARRAY [-2..2] OF CARDINAL; | |
11891 | END | |
11892 | @end smallexample | |
11893 | ||
6d2ebf8b | 11894 | @node M2 Defaults |
79a6e687 | 11895 | @subsubsection Modula-2 Defaults |
c906108c SS |
11896 | @cindex Modula-2 defaults |
11897 | ||
11898 | If type and range checking are set automatically by @value{GDBN}, they | |
11899 | both default to @code{on} whenever the working language changes to | |
d4f3574e | 11900 | Modula-2. This happens regardless of whether you or @value{GDBN} |
c906108c SS |
11901 | selected the working language. |
11902 | ||
11903 | If you allow @value{GDBN} to set the language automatically, then entering | |
11904 | code compiled from a file whose name ends with @file{.mod} sets the | |
79a6e687 BW |
11905 | working language to Modula-2. @xref{Automatically, ,Having @value{GDBN} |
11906 | Infer the Source Language}, for further details. | |
c906108c | 11907 | |
6d2ebf8b | 11908 | @node Deviations |
79a6e687 | 11909 | @subsubsection Deviations from Standard Modula-2 |
c906108c SS |
11910 | @cindex Modula-2, deviations from |
11911 | ||
11912 | A few changes have been made to make Modula-2 programs easier to debug. | |
11913 | This is done primarily via loosening its type strictness: | |
11914 | ||
11915 | @itemize @bullet | |
11916 | @item | |
11917 | Unlike in standard Modula-2, pointer constants can be formed by | |
11918 | integers. This allows you to modify pointer variables during | |
11919 | debugging. (In standard Modula-2, the actual address contained in a | |
11920 | pointer variable is hidden from you; it can only be modified | |
11921 | through direct assignment to another pointer variable or expression that | |
11922 | returned a pointer.) | |
11923 | ||
11924 | @item | |
11925 | C escape sequences can be used in strings and characters to represent | |
11926 | non-printable characters. @value{GDBN} prints out strings with these | |
11927 | escape sequences embedded. Single non-printable characters are | |
11928 | printed using the @samp{CHR(@var{nnn})} format. | |
11929 | ||
11930 | @item | |
11931 | The assignment operator (@code{:=}) returns the value of its right-hand | |
11932 | argument. | |
11933 | ||
11934 | @item | |
11935 | All built-in procedures both modify @emph{and} return their argument. | |
11936 | @end itemize | |
11937 | ||
6d2ebf8b | 11938 | @node M2 Checks |
79a6e687 | 11939 | @subsubsection Modula-2 Type and Range Checks |
c906108c SS |
11940 | @cindex Modula-2 checks |
11941 | ||
11942 | @quotation | |
11943 | @emph{Warning:} in this release, @value{GDBN} does not yet perform type or | |
11944 | range checking. | |
11945 | @end quotation | |
11946 | @c FIXME remove warning when type/range checks added | |
11947 | ||
11948 | @value{GDBN} considers two Modula-2 variables type equivalent if: | |
11949 | ||
11950 | @itemize @bullet | |
11951 | @item | |
11952 | They are of types that have been declared equivalent via a @code{TYPE | |
11953 | @var{t1} = @var{t2}} statement | |
11954 | ||
11955 | @item | |
11956 | They have been declared on the same line. (Note: This is true of the | |
11957 | @sc{gnu} Modula-2 compiler, but it may not be true of other compilers.) | |
11958 | @end itemize | |
11959 | ||
11960 | As long as type checking is enabled, any attempt to combine variables | |
11961 | whose types are not equivalent is an error. | |
11962 | ||
11963 | Range checking is done on all mathematical operations, assignment, array | |
11964 | index bounds, and all built-in functions and procedures. | |
11965 | ||
6d2ebf8b | 11966 | @node M2 Scope |
79a6e687 | 11967 | @subsubsection The Scope Operators @code{::} and @code{.} |
c906108c | 11968 | @cindex scope |
41afff9a | 11969 | @cindex @code{.}, Modula-2 scope operator |
c906108c SS |
11970 | @cindex colon, doubled as scope operator |
11971 | @ifinfo | |
41afff9a | 11972 | @vindex colon-colon@r{, in Modula-2} |
c906108c SS |
11973 | @c Info cannot handle :: but TeX can. |
11974 | @end ifinfo | |
a67ec3f4 | 11975 | @ifnotinfo |
41afff9a | 11976 | @vindex ::@r{, in Modula-2} |
a67ec3f4 | 11977 | @end ifnotinfo |
c906108c SS |
11978 | |
11979 | There are a few subtle differences between the Modula-2 scope operator | |
11980 | (@code{.}) and the @value{GDBN} scope operator (@code{::}). The two have | |
11981 | similar syntax: | |
11982 | ||
474c8240 | 11983 | @smallexample |
c906108c SS |
11984 | |
11985 | @var{module} . @var{id} | |
11986 | @var{scope} :: @var{id} | |
474c8240 | 11987 | @end smallexample |
c906108c SS |
11988 | |
11989 | @noindent | |
11990 | where @var{scope} is the name of a module or a procedure, | |
11991 | @var{module} the name of a module, and @var{id} is any declared | |
11992 | identifier within your program, except another module. | |
11993 | ||
11994 | Using the @code{::} operator makes @value{GDBN} search the scope | |
11995 | specified by @var{scope} for the identifier @var{id}. If it is not | |
11996 | found in the specified scope, then @value{GDBN} searches all scopes | |
11997 | enclosing the one specified by @var{scope}. | |
11998 | ||
11999 | Using the @code{.} operator makes @value{GDBN} search the current scope for | |
12000 | the identifier specified by @var{id} that was imported from the | |
12001 | definition module specified by @var{module}. With this operator, it is | |
12002 | an error if the identifier @var{id} was not imported from definition | |
12003 | module @var{module}, or if @var{id} is not an identifier in | |
12004 | @var{module}. | |
12005 | ||
6d2ebf8b | 12006 | @node GDB/M2 |
c906108c SS |
12007 | @subsubsection @value{GDBN} and Modula-2 |
12008 | ||
12009 | Some @value{GDBN} commands have little use when debugging Modula-2 programs. | |
12010 | Five subcommands of @code{set print} and @code{show print} apply | |
b37052ae | 12011 | specifically to C and C@t{++}: @samp{vtbl}, @samp{demangle}, |
c906108c | 12012 | @samp{asm-demangle}, @samp{object}, and @samp{union}. The first four |
b37052ae | 12013 | apply to C@t{++}, and the last to the C @code{union} type, which has no direct |
c906108c SS |
12014 | analogue in Modula-2. |
12015 | ||
12016 | The @code{@@} operator (@pxref{Expressions, ,Expressions}), while available | |
d4f3574e | 12017 | with any language, is not useful with Modula-2. Its |
c906108c | 12018 | intent is to aid the debugging of @dfn{dynamic arrays}, which cannot be |
b37052ae | 12019 | created in Modula-2 as they can in C or C@t{++}. However, because an |
c906108c | 12020 | address can be specified by an integral constant, the construct |
d4f3574e | 12021 | @samp{@{@var{type}@}@var{adrexp}} is still useful. |
c906108c SS |
12022 | |
12023 | @cindex @code{#} in Modula-2 | |
12024 | In @value{GDBN} scripts, the Modula-2 inequality operator @code{#} is | |
12025 | interpreted as the beginning of a comment. Use @code{<>} instead. | |
c906108c | 12026 | |
e07c999f PH |
12027 | @node Ada |
12028 | @subsection Ada | |
12029 | @cindex Ada | |
12030 | ||
12031 | The extensions made to @value{GDBN} for Ada only support | |
12032 | output from the @sc{gnu} Ada (GNAT) compiler. | |
12033 | Other Ada compilers are not currently supported, and | |
12034 | attempting to debug executables produced by them is most likely | |
12035 | to be difficult. | |
12036 | ||
12037 | ||
12038 | @cindex expressions in Ada | |
12039 | @menu | |
12040 | * Ada Mode Intro:: General remarks on the Ada syntax | |
12041 | and semantics supported by Ada mode | |
12042 | in @value{GDBN}. | |
12043 | * Omissions from Ada:: Restrictions on the Ada expression syntax. | |
12044 | * Additions to Ada:: Extensions of the Ada expression syntax. | |
12045 | * Stopping Before Main Program:: Debugging the program during elaboration. | |
20924a55 JB |
12046 | * Ada Tasks:: Listing and setting breakpoints in tasks. |
12047 | * Ada Tasks and Core Files:: Tasking Support when Debugging Core Files | |
e07c999f PH |
12048 | * Ada Glitches:: Known peculiarities of Ada mode. |
12049 | @end menu | |
12050 | ||
12051 | @node Ada Mode Intro | |
12052 | @subsubsection Introduction | |
12053 | @cindex Ada mode, general | |
12054 | ||
12055 | The Ada mode of @value{GDBN} supports a fairly large subset of Ada expression | |
12056 | syntax, with some extensions. | |
12057 | The philosophy behind the design of this subset is | |
12058 | ||
12059 | @itemize @bullet | |
12060 | @item | |
12061 | That @value{GDBN} should provide basic literals and access to operations for | |
12062 | arithmetic, dereferencing, field selection, indexing, and subprogram calls, | |
12063 | leaving more sophisticated computations to subprograms written into the | |
12064 | program (which therefore may be called from @value{GDBN}). | |
12065 | ||
12066 | @item | |
12067 | That type safety and strict adherence to Ada language restrictions | |
12068 | are not particularly important to the @value{GDBN} user. | |
12069 | ||
12070 | @item | |
12071 | That brevity is important to the @value{GDBN} user. | |
12072 | @end itemize | |
12073 | ||
f3a2dd1a JB |
12074 | Thus, for brevity, the debugger acts as if all names declared in |
12075 | user-written packages are directly visible, even if they are not visible | |
12076 | according to Ada rules, thus making it unnecessary to fully qualify most | |
12077 | names with their packages, regardless of context. Where this causes | |
12078 | ambiguity, @value{GDBN} asks the user's intent. | |
e07c999f PH |
12079 | |
12080 | The debugger will start in Ada mode if it detects an Ada main program. | |
12081 | As for other languages, it will enter Ada mode when stopped in a program that | |
12082 | was translated from an Ada source file. | |
12083 | ||
12084 | While in Ada mode, you may use `@t{--}' for comments. This is useful | |
12085 | mostly for documenting command files. The standard @value{GDBN} comment | |
12086 | (@samp{#}) still works at the beginning of a line in Ada mode, but not in the | |
12087 | middle (to allow based literals). | |
12088 | ||
12089 | The debugger supports limited overloading. Given a subprogram call in which | |
12090 | the function symbol has multiple definitions, it will use the number of | |
12091 | actual parameters and some information about their types to attempt to narrow | |
12092 | the set of definitions. It also makes very limited use of context, preferring | |
12093 | procedures to functions in the context of the @code{call} command, and | |
12094 | functions to procedures elsewhere. | |
12095 | ||
12096 | @node Omissions from Ada | |
12097 | @subsubsection Omissions from Ada | |
12098 | @cindex Ada, omissions from | |
12099 | ||
12100 | Here are the notable omissions from the subset: | |
12101 | ||
12102 | @itemize @bullet | |
12103 | @item | |
12104 | Only a subset of the attributes are supported: | |
12105 | ||
12106 | @itemize @minus | |
12107 | @item | |
12108 | @t{'First}, @t{'Last}, and @t{'Length} | |
12109 | on array objects (not on types and subtypes). | |
12110 | ||
12111 | @item | |
12112 | @t{'Min} and @t{'Max}. | |
12113 | ||
12114 | @item | |
12115 | @t{'Pos} and @t{'Val}. | |
12116 | ||
12117 | @item | |
12118 | @t{'Tag}. | |
12119 | ||
12120 | @item | |
12121 | @t{'Range} on array objects (not subtypes), but only as the right | |
12122 | operand of the membership (@code{in}) operator. | |
12123 | ||
12124 | @item | |
12125 | @t{'Access}, @t{'Unchecked_Access}, and | |
12126 | @t{'Unrestricted_Access} (a GNAT extension). | |
12127 | ||
12128 | @item | |
12129 | @t{'Address}. | |
12130 | @end itemize | |
12131 | ||
12132 | @item | |
12133 | The names in | |
12134 | @code{Characters.Latin_1} are not available and | |
12135 | concatenation is not implemented. Thus, escape characters in strings are | |
12136 | not currently available. | |
12137 | ||
12138 | @item | |
12139 | Equality tests (@samp{=} and @samp{/=}) on arrays test for bitwise | |
12140 | equality of representations. They will generally work correctly | |
12141 | for strings and arrays whose elements have integer or enumeration types. | |
12142 | They may not work correctly for arrays whose element | |
12143 | types have user-defined equality, for arrays of real values | |
12144 | (in particular, IEEE-conformant floating point, because of negative | |
12145 | zeroes and NaNs), and for arrays whose elements contain unused bits with | |
12146 | indeterminate values. | |
12147 | ||
12148 | @item | |
12149 | The other component-by-component array operations (@code{and}, @code{or}, | |
12150 | @code{xor}, @code{not}, and relational tests other than equality) | |
12151 | are not implemented. | |
12152 | ||
12153 | @item | |
860701dc PH |
12154 | @cindex array aggregates (Ada) |
12155 | @cindex record aggregates (Ada) | |
12156 | @cindex aggregates (Ada) | |
12157 | There is limited support for array and record aggregates. They are | |
12158 | permitted only on the right sides of assignments, as in these examples: | |
12159 | ||
12160 | @smallexample | |
077e0a52 JB |
12161 | (@value{GDBP}) set An_Array := (1, 2, 3, 4, 5, 6) |
12162 | (@value{GDBP}) set An_Array := (1, others => 0) | |
12163 | (@value{GDBP}) set An_Array := (0|4 => 1, 1..3 => 2, 5 => 6) | |
12164 | (@value{GDBP}) set A_2D_Array := ((1, 2, 3), (4, 5, 6), (7, 8, 9)) | |
12165 | (@value{GDBP}) set A_Record := (1, "Peter", True); | |
12166 | (@value{GDBP}) set A_Record := (Name => "Peter", Id => 1, Alive => True) | |
860701dc PH |
12167 | @end smallexample |
12168 | ||
12169 | Changing a | |
12170 | discriminant's value by assigning an aggregate has an | |
12171 | undefined effect if that discriminant is used within the record. | |
12172 | However, you can first modify discriminants by directly assigning to | |
12173 | them (which normally would not be allowed in Ada), and then performing an | |
12174 | aggregate assignment. For example, given a variable @code{A_Rec} | |
12175 | declared to have a type such as: | |
12176 | ||
12177 | @smallexample | |
12178 | type Rec (Len : Small_Integer := 0) is record | |
12179 | Id : Integer; | |
12180 | Vals : IntArray (1 .. Len); | |
12181 | end record; | |
12182 | @end smallexample | |
12183 | ||
12184 | you can assign a value with a different size of @code{Vals} with two | |
12185 | assignments: | |
12186 | ||
12187 | @smallexample | |
077e0a52 JB |
12188 | (@value{GDBP}) set A_Rec.Len := 4 |
12189 | (@value{GDBP}) set A_Rec := (Id => 42, Vals => (1, 2, 3, 4)) | |
860701dc PH |
12190 | @end smallexample |
12191 | ||
12192 | As this example also illustrates, @value{GDBN} is very loose about the usual | |
12193 | rules concerning aggregates. You may leave out some of the | |
12194 | components of an array or record aggregate (such as the @code{Len} | |
12195 | component in the assignment to @code{A_Rec} above); they will retain their | |
12196 | original values upon assignment. You may freely use dynamic values as | |
12197 | indices in component associations. You may even use overlapping or | |
12198 | redundant component associations, although which component values are | |
12199 | assigned in such cases is not defined. | |
e07c999f PH |
12200 | |
12201 | @item | |
12202 | Calls to dispatching subprograms are not implemented. | |
12203 | ||
12204 | @item | |
12205 | The overloading algorithm is much more limited (i.e., less selective) | |
ae21e955 BW |
12206 | than that of real Ada. It makes only limited use of the context in |
12207 | which a subexpression appears to resolve its meaning, and it is much | |
12208 | looser in its rules for allowing type matches. As a result, some | |
12209 | function calls will be ambiguous, and the user will be asked to choose | |
12210 | the proper resolution. | |
e07c999f PH |
12211 | |
12212 | @item | |
12213 | The @code{new} operator is not implemented. | |
12214 | ||
12215 | @item | |
12216 | Entry calls are not implemented. | |
12217 | ||
12218 | @item | |
12219 | Aside from printing, arithmetic operations on the native VAX floating-point | |
12220 | formats are not supported. | |
12221 | ||
12222 | @item | |
12223 | It is not possible to slice a packed array. | |
158c7665 PH |
12224 | |
12225 | @item | |
12226 | The names @code{True} and @code{False}, when not part of a qualified name, | |
12227 | are interpreted as if implicitly prefixed by @code{Standard}, regardless of | |
12228 | context. | |
12229 | Should your program | |
12230 | redefine these names in a package or procedure (at best a dubious practice), | |
12231 | you will have to use fully qualified names to access their new definitions. | |
e07c999f PH |
12232 | @end itemize |
12233 | ||
12234 | @node Additions to Ada | |
12235 | @subsubsection Additions to Ada | |
12236 | @cindex Ada, deviations from | |
12237 | ||
12238 | As it does for other languages, @value{GDBN} makes certain generic | |
12239 | extensions to Ada (@pxref{Expressions}): | |
12240 | ||
12241 | @itemize @bullet | |
12242 | @item | |
ae21e955 BW |
12243 | If the expression @var{E} is a variable residing in memory (typically |
12244 | a local variable or array element) and @var{N} is a positive integer, | |
12245 | then @code{@var{E}@@@var{N}} displays the values of @var{E} and the | |
12246 | @var{N}-1 adjacent variables following it in memory as an array. In | |
12247 | Ada, this operator is generally not necessary, since its prime use is | |
12248 | in displaying parts of an array, and slicing will usually do this in | |
12249 | Ada. However, there are occasional uses when debugging programs in | |
12250 | which certain debugging information has been optimized away. | |
e07c999f PH |
12251 | |
12252 | @item | |
ae21e955 BW |
12253 | @code{@var{B}::@var{var}} means ``the variable named @var{var} that |
12254 | appears in function or file @var{B}.'' When @var{B} is a file name, | |
12255 | you must typically surround it in single quotes. | |
e07c999f PH |
12256 | |
12257 | @item | |
12258 | The expression @code{@{@var{type}@} @var{addr}} means ``the variable of type | |
12259 | @var{type} that appears at address @var{addr}.'' | |
12260 | ||
12261 | @item | |
12262 | A name starting with @samp{$} is a convenience variable | |
12263 | (@pxref{Convenience Vars}) or a machine register (@pxref{Registers}). | |
12264 | @end itemize | |
12265 | ||
ae21e955 BW |
12266 | In addition, @value{GDBN} provides a few other shortcuts and outright |
12267 | additions specific to Ada: | |
e07c999f PH |
12268 | |
12269 | @itemize @bullet | |
12270 | @item | |
12271 | The assignment statement is allowed as an expression, returning | |
12272 | its right-hand operand as its value. Thus, you may enter | |
12273 | ||
12274 | @smallexample | |
077e0a52 JB |
12275 | (@value{GDBP}) set x := y + 3 |
12276 | (@value{GDBP}) print A(tmp := y + 1) | |
e07c999f PH |
12277 | @end smallexample |
12278 | ||
12279 | @item | |
12280 | The semicolon is allowed as an ``operator,'' returning as its value | |
12281 | the value of its right-hand operand. | |
12282 | This allows, for example, | |
12283 | complex conditional breaks: | |
12284 | ||
12285 | @smallexample | |
077e0a52 JB |
12286 | (@value{GDBP}) break f |
12287 | (@value{GDBP}) condition 1 (report(i); k += 1; A(k) > 100) | |
e07c999f PH |
12288 | @end smallexample |
12289 | ||
12290 | @item | |
12291 | Rather than use catenation and symbolic character names to introduce special | |
12292 | characters into strings, one may instead use a special bracket notation, | |
12293 | which is also used to print strings. A sequence of characters of the form | |
12294 | @samp{["@var{XX}"]} within a string or character literal denotes the | |
12295 | (single) character whose numeric encoding is @var{XX} in hexadecimal. The | |
12296 | sequence of characters @samp{["""]} also denotes a single quotation mark | |
12297 | in strings. For example, | |
12298 | @smallexample | |
12299 | "One line.["0a"]Next line.["0a"]" | |
12300 | @end smallexample | |
12301 | @noindent | |
ae21e955 BW |
12302 | contains an ASCII newline character (@code{Ada.Characters.Latin_1.LF}) |
12303 | after each period. | |
e07c999f PH |
12304 | |
12305 | @item | |
12306 | The subtype used as a prefix for the attributes @t{'Pos}, @t{'Min}, and | |
12307 | @t{'Max} is optional (and is ignored in any case). For example, it is valid | |
12308 | to write | |
12309 | ||
12310 | @smallexample | |
077e0a52 | 12311 | (@value{GDBP}) print 'max(x, y) |
e07c999f PH |
12312 | @end smallexample |
12313 | ||
12314 | @item | |
12315 | When printing arrays, @value{GDBN} uses positional notation when the | |
12316 | array has a lower bound of 1, and uses a modified named notation otherwise. | |
ae21e955 BW |
12317 | For example, a one-dimensional array of three integers with a lower bound |
12318 | of 3 might print as | |
e07c999f PH |
12319 | |
12320 | @smallexample | |
12321 | (3 => 10, 17, 1) | |
12322 | @end smallexample | |
12323 | ||
12324 | @noindent | |
12325 | That is, in contrast to valid Ada, only the first component has a @code{=>} | |
12326 | clause. | |
12327 | ||
12328 | @item | |
12329 | You may abbreviate attributes in expressions with any unique, | |
12330 | multi-character subsequence of | |
12331 | their names (an exact match gets preference). | |
12332 | For example, you may use @t{a'len}, @t{a'gth}, or @t{a'lh} | |
12333 | in place of @t{a'length}. | |
12334 | ||
12335 | @item | |
12336 | @cindex quoting Ada internal identifiers | |
12337 | Since Ada is case-insensitive, the debugger normally maps identifiers you type | |
12338 | to lower case. The GNAT compiler uses upper-case characters for | |
12339 | some of its internal identifiers, which are normally of no interest to users. | |
12340 | For the rare occasions when you actually have to look at them, | |
12341 | enclose them in angle brackets to avoid the lower-case mapping. | |
12342 | For example, | |
12343 | @smallexample | |
077e0a52 | 12344 | (@value{GDBP}) print <JMPBUF_SAVE>[0] |
e07c999f PH |
12345 | @end smallexample |
12346 | ||
12347 | @item | |
12348 | Printing an object of class-wide type or dereferencing an | |
12349 | access-to-class-wide value will display all the components of the object's | |
12350 | specific type (as indicated by its run-time tag). Likewise, component | |
12351 | selection on such a value will operate on the specific type of the | |
12352 | object. | |
12353 | ||
12354 | @end itemize | |
12355 | ||
12356 | @node Stopping Before Main Program | |
12357 | @subsubsection Stopping at the Very Beginning | |
12358 | ||
12359 | @cindex breakpointing Ada elaboration code | |
12360 | It is sometimes necessary to debug the program during elaboration, and | |
12361 | before reaching the main procedure. | |
12362 | As defined in the Ada Reference | |
12363 | Manual, the elaboration code is invoked from a procedure called | |
12364 | @code{adainit}. To run your program up to the beginning of | |
12365 | elaboration, simply use the following two commands: | |
12366 | @code{tbreak adainit} and @code{run}. | |
12367 | ||
20924a55 JB |
12368 | @node Ada Tasks |
12369 | @subsubsection Extensions for Ada Tasks | |
12370 | @cindex Ada, tasking | |
12371 | ||
12372 | Support for Ada tasks is analogous to that for threads (@pxref{Threads}). | |
12373 | @value{GDBN} provides the following task-related commands: | |
12374 | ||
12375 | @table @code | |
12376 | @kindex info tasks | |
12377 | @item info tasks | |
12378 | This command shows a list of current Ada tasks, as in the following example: | |
12379 | ||
12380 | ||
12381 | @smallexample | |
12382 | @iftex | |
12383 | @leftskip=0.5cm | |
12384 | @end iftex | |
12385 | (@value{GDBP}) info tasks | |
12386 | ID TID P-ID Pri State Name | |
12387 | 1 8088000 0 15 Child Activation Wait main_task | |
12388 | 2 80a4000 1 15 Accept Statement b | |
12389 | 3 809a800 1 15 Child Activation Wait a | |
32cd1edc | 12390 | * 4 80ae800 3 15 Runnable c |
20924a55 JB |
12391 | |
12392 | @end smallexample | |
12393 | ||
12394 | @noindent | |
12395 | In this listing, the asterisk before the last task indicates it to be the | |
12396 | task currently being inspected. | |
12397 | ||
12398 | @table @asis | |
12399 | @item ID | |
12400 | Represents @value{GDBN}'s internal task number. | |
12401 | ||
12402 | @item TID | |
12403 | The Ada task ID. | |
12404 | ||
12405 | @item P-ID | |
12406 | The parent's task ID (@value{GDBN}'s internal task number). | |
12407 | ||
12408 | @item Pri | |
12409 | The base priority of the task. | |
12410 | ||
12411 | @item State | |
12412 | Current state of the task. | |
12413 | ||
12414 | @table @code | |
12415 | @item Unactivated | |
12416 | The task has been created but has not been activated. It cannot be | |
12417 | executing. | |
12418 | ||
20924a55 JB |
12419 | @item Runnable |
12420 | The task is not blocked for any reason known to Ada. (It may be waiting | |
12421 | for a mutex, though.) It is conceptually "executing" in normal mode. | |
12422 | ||
12423 | @item Terminated | |
12424 | The task is terminated, in the sense of ARM 9.3 (5). Any dependents | |
12425 | that were waiting on terminate alternatives have been awakened and have | |
12426 | terminated themselves. | |
12427 | ||
12428 | @item Child Activation Wait | |
12429 | The task is waiting for created tasks to complete activation. | |
12430 | ||
12431 | @item Accept Statement | |
12432 | The task is waiting on an accept or selective wait statement. | |
12433 | ||
12434 | @item Waiting on entry call | |
12435 | The task is waiting on an entry call. | |
12436 | ||
12437 | @item Async Select Wait | |
12438 | The task is waiting to start the abortable part of an asynchronous | |
12439 | select statement. | |
12440 | ||
12441 | @item Delay Sleep | |
12442 | The task is waiting on a select statement with only a delay | |
12443 | alternative open. | |
12444 | ||
12445 | @item Child Termination Wait | |
12446 | The task is sleeping having completed a master within itself, and is | |
12447 | waiting for the tasks dependent on that master to become terminated or | |
12448 | waiting on a terminate Phase. | |
12449 | ||
12450 | @item Wait Child in Term Alt | |
12451 | The task is sleeping waiting for tasks on terminate alternatives to | |
12452 | finish terminating. | |
12453 | ||
12454 | @item Accepting RV with @var{taskno} | |
12455 | The task is accepting a rendez-vous with the task @var{taskno}. | |
12456 | @end table | |
12457 | ||
12458 | @item Name | |
12459 | Name of the task in the program. | |
12460 | ||
12461 | @end table | |
12462 | ||
12463 | @kindex info task @var{taskno} | |
12464 | @item info task @var{taskno} | |
12465 | This command shows detailled informations on the specified task, as in | |
12466 | the following example: | |
12467 | @smallexample | |
12468 | @iftex | |
12469 | @leftskip=0.5cm | |
12470 | @end iftex | |
12471 | (@value{GDBP}) info tasks | |
12472 | ID TID P-ID Pri State Name | |
12473 | 1 8077880 0 15 Child Activation Wait main_task | |
32cd1edc | 12474 | * 2 807c468 1 15 Runnable task_1 |
20924a55 JB |
12475 | (@value{GDBP}) info task 2 |
12476 | Ada Task: 0x807c468 | |
12477 | Name: task_1 | |
12478 | Thread: 0x807f378 | |
12479 | Parent: 1 (main_task) | |
12480 | Base Priority: 15 | |
12481 | State: Runnable | |
12482 | @end smallexample | |
12483 | ||
12484 | @item task | |
12485 | @kindex task@r{ (Ada)} | |
12486 | @cindex current Ada task ID | |
12487 | This command prints the ID of the current task. | |
12488 | ||
12489 | @smallexample | |
12490 | @iftex | |
12491 | @leftskip=0.5cm | |
12492 | @end iftex | |
12493 | (@value{GDBP}) info tasks | |
12494 | ID TID P-ID Pri State Name | |
12495 | 1 8077870 0 15 Child Activation Wait main_task | |
32cd1edc | 12496 | * 2 807c458 1 15 Runnable t |
20924a55 JB |
12497 | (@value{GDBP}) task |
12498 | [Current task is 2] | |
12499 | @end smallexample | |
12500 | ||
12501 | @item task @var{taskno} | |
12502 | @cindex Ada task switching | |
12503 | This command is like the @code{thread @var{threadno}} | |
12504 | command (@pxref{Threads}). It switches the context of debugging | |
12505 | from the current task to the given task. | |
12506 | ||
12507 | @smallexample | |
12508 | @iftex | |
12509 | @leftskip=0.5cm | |
12510 | @end iftex | |
12511 | (@value{GDBP}) info tasks | |
12512 | ID TID P-ID Pri State Name | |
12513 | 1 8077870 0 15 Child Activation Wait main_task | |
32cd1edc | 12514 | * 2 807c458 1 15 Runnable t |
20924a55 JB |
12515 | (@value{GDBP}) task 1 |
12516 | [Switching to task 1] | |
12517 | #0 0x8067726 in pthread_cond_wait () | |
12518 | (@value{GDBP}) bt | |
12519 | #0 0x8067726 in pthread_cond_wait () | |
12520 | #1 0x8056714 in system.os_interface.pthread_cond_wait () | |
12521 | #2 0x805cb63 in system.task_primitives.operations.sleep () | |
12522 | #3 0x806153e in system.tasking.stages.activate_tasks () | |
12523 | #4 0x804aacc in un () at un.adb:5 | |
12524 | @end smallexample | |
12525 | ||
45ac276d JB |
12526 | @item break @var{linespec} task @var{taskno} |
12527 | @itemx break @var{linespec} task @var{taskno} if @dots{} | |
12528 | @cindex breakpoints and tasks, in Ada | |
12529 | @cindex task breakpoints, in Ada | |
12530 | @kindex break @dots{} task @var{taskno}@r{ (Ada)} | |
12531 | These commands are like the @code{break @dots{} thread @dots{}} | |
12532 | command (@pxref{Thread Stops}). | |
12533 | @var{linespec} specifies source lines, as described | |
12534 | in @ref{Specify Location}. | |
12535 | ||
12536 | Use the qualifier @samp{task @var{taskno}} with a breakpoint command | |
12537 | to specify that you only want @value{GDBN} to stop the program when a | |
12538 | particular Ada task reaches this breakpoint. @var{taskno} is one of the | |
12539 | numeric task identifiers assigned by @value{GDBN}, shown in the first | |
12540 | column of the @samp{info tasks} display. | |
12541 | ||
12542 | If you do not specify @samp{task @var{taskno}} when you set a | |
12543 | breakpoint, the breakpoint applies to @emph{all} tasks of your | |
12544 | program. | |
12545 | ||
12546 | You can use the @code{task} qualifier on conditional breakpoints as | |
12547 | well; in this case, place @samp{task @var{taskno}} before the | |
12548 | breakpoint condition (before the @code{if}). | |
12549 | ||
12550 | For example, | |
12551 | ||
12552 | @smallexample | |
12553 | @iftex | |
12554 | @leftskip=0.5cm | |
12555 | @end iftex | |
12556 | (@value{GDBP}) info tasks | |
12557 | ID TID P-ID Pri State Name | |
12558 | 1 140022020 0 15 Child Activation Wait main_task | |
12559 | 2 140045060 1 15 Accept/Select Wait t2 | |
12560 | 3 140044840 1 15 Runnable t1 | |
12561 | * 4 140056040 1 15 Runnable t3 | |
12562 | (@value{GDBP}) b 15 task 2 | |
12563 | Breakpoint 5 at 0x120044cb0: file test_task_debug.adb, line 15. | |
12564 | (@value{GDBP}) cont | |
12565 | Continuing. | |
12566 | task # 1 running | |
12567 | task # 2 running | |
12568 | ||
12569 | Breakpoint 5, test_task_debug () at test_task_debug.adb:15 | |
12570 | 15 flush; | |
12571 | (@value{GDBP}) info tasks | |
12572 | ID TID P-ID Pri State Name | |
12573 | 1 140022020 0 15 Child Activation Wait main_task | |
12574 | * 2 140045060 1 15 Runnable t2 | |
12575 | 3 140044840 1 15 Runnable t1 | |
12576 | 4 140056040 1 15 Delay Sleep t3 | |
12577 | @end smallexample | |
20924a55 JB |
12578 | @end table |
12579 | ||
12580 | @node Ada Tasks and Core Files | |
12581 | @subsubsection Tasking Support when Debugging Core Files | |
12582 | @cindex Ada tasking and core file debugging | |
12583 | ||
12584 | When inspecting a core file, as opposed to debugging a live program, | |
12585 | tasking support may be limited or even unavailable, depending on | |
12586 | the platform being used. | |
12587 | For instance, on x86-linux, the list of tasks is available, but task | |
12588 | switching is not supported. On Tru64, however, task switching will work | |
12589 | as usual. | |
12590 | ||
12591 | On certain platforms, including Tru64, the debugger needs to perform some | |
12592 | memory writes in order to provide Ada tasking support. When inspecting | |
12593 | a core file, this means that the core file must be opened with read-write | |
12594 | privileges, using the command @samp{"set write on"} (@pxref{Patching}). | |
12595 | Under these circumstances, you should make a backup copy of the core | |
12596 | file before inspecting it with @value{GDBN}. | |
12597 | ||
e07c999f PH |
12598 | @node Ada Glitches |
12599 | @subsubsection Known Peculiarities of Ada Mode | |
12600 | @cindex Ada, problems | |
12601 | ||
12602 | Besides the omissions listed previously (@pxref{Omissions from Ada}), | |
12603 | we know of several problems with and limitations of Ada mode in | |
12604 | @value{GDBN}, | |
12605 | some of which will be fixed with planned future releases of the debugger | |
12606 | and the GNU Ada compiler. | |
12607 | ||
12608 | @itemize @bullet | |
12609 | @item | |
12610 | Currently, the debugger | |
12611 | has insufficient information to determine whether certain pointers represent | |
12612 | pointers to objects or the objects themselves. | |
12613 | Thus, the user may have to tack an extra @code{.all} after an expression | |
12614 | to get it printed properly. | |
12615 | ||
12616 | @item | |
12617 | Static constants that the compiler chooses not to materialize as objects in | |
12618 | storage are invisible to the debugger. | |
12619 | ||
12620 | @item | |
12621 | Named parameter associations in function argument lists are ignored (the | |
12622 | argument lists are treated as positional). | |
12623 | ||
12624 | @item | |
12625 | Many useful library packages are currently invisible to the debugger. | |
12626 | ||
12627 | @item | |
12628 | Fixed-point arithmetic, conversions, input, and output is carried out using | |
12629 | floating-point arithmetic, and may give results that only approximate those on | |
12630 | the host machine. | |
12631 | ||
e07c999f PH |
12632 | @item |
12633 | The GNAT compiler never generates the prefix @code{Standard} for any of | |
12634 | the standard symbols defined by the Ada language. @value{GDBN} knows about | |
12635 | this: it will strip the prefix from names when you use it, and will never | |
12636 | look for a name you have so qualified among local symbols, nor match against | |
12637 | symbols in other packages or subprograms. If you have | |
12638 | defined entities anywhere in your program other than parameters and | |
12639 | local variables whose simple names match names in @code{Standard}, | |
12640 | GNAT's lack of qualification here can cause confusion. When this happens, | |
12641 | you can usually resolve the confusion | |
12642 | by qualifying the problematic names with package | |
12643 | @code{Standard} explicitly. | |
12644 | @end itemize | |
12645 | ||
79a6e687 BW |
12646 | @node Unsupported Languages |
12647 | @section Unsupported Languages | |
4e562065 JB |
12648 | |
12649 | @cindex unsupported languages | |
12650 | @cindex minimal language | |
12651 | In addition to the other fully-supported programming languages, | |
12652 | @value{GDBN} also provides a pseudo-language, called @code{minimal}. | |
12653 | It does not represent a real programming language, but provides a set | |
12654 | of capabilities close to what the C or assembly languages provide. | |
12655 | This should allow most simple operations to be performed while debugging | |
12656 | an application that uses a language currently not supported by @value{GDBN}. | |
12657 | ||
12658 | If the language is set to @code{auto}, @value{GDBN} will automatically | |
12659 | select this language if the current frame corresponds to an unsupported | |
12660 | language. | |
12661 | ||
6d2ebf8b | 12662 | @node Symbols |
c906108c SS |
12663 | @chapter Examining the Symbol Table |
12664 | ||
d4f3574e | 12665 | The commands described in this chapter allow you to inquire about the |
c906108c SS |
12666 | symbols (names of variables, functions and types) defined in your |
12667 | program. This information is inherent in the text of your program and | |
12668 | does not change as your program executes. @value{GDBN} finds it in your | |
12669 | program's symbol table, in the file indicated when you started @value{GDBN} | |
79a6e687 BW |
12670 | (@pxref{File Options, ,Choosing Files}), or by one of the |
12671 | file-management commands (@pxref{Files, ,Commands to Specify Files}). | |
c906108c SS |
12672 | |
12673 | @cindex symbol names | |
12674 | @cindex names of symbols | |
12675 | @cindex quoting names | |
12676 | Occasionally, you may need to refer to symbols that contain unusual | |
12677 | characters, which @value{GDBN} ordinarily treats as word delimiters. The | |
12678 | most frequent case is in referring to static variables in other | |
79a6e687 | 12679 | source files (@pxref{Variables,,Program Variables}). File names |
c906108c SS |
12680 | are recorded in object files as debugging symbols, but @value{GDBN} would |
12681 | ordinarily parse a typical file name, like @file{foo.c}, as the three words | |
12682 | @samp{foo} @samp{.} @samp{c}. To allow @value{GDBN} to recognize | |
12683 | @samp{foo.c} as a single symbol, enclose it in single quotes; for example, | |
12684 | ||
474c8240 | 12685 | @smallexample |
c906108c | 12686 | p 'foo.c'::x |
474c8240 | 12687 | @end smallexample |
c906108c SS |
12688 | |
12689 | @noindent | |
12690 | looks up the value of @code{x} in the scope of the file @file{foo.c}. | |
12691 | ||
12692 | @table @code | |
a8f24a35 EZ |
12693 | @cindex case-insensitive symbol names |
12694 | @cindex case sensitivity in symbol names | |
12695 | @kindex set case-sensitive | |
12696 | @item set case-sensitive on | |
12697 | @itemx set case-sensitive off | |
12698 | @itemx set case-sensitive auto | |
12699 | Normally, when @value{GDBN} looks up symbols, it matches their names | |
12700 | with case sensitivity determined by the current source language. | |
12701 | Occasionally, you may wish to control that. The command @code{set | |
12702 | case-sensitive} lets you do that by specifying @code{on} for | |
12703 | case-sensitive matches or @code{off} for case-insensitive ones. If | |
12704 | you specify @code{auto}, case sensitivity is reset to the default | |
12705 | suitable for the source language. The default is case-sensitive | |
12706 | matches for all languages except for Fortran, for which the default is | |
12707 | case-insensitive matches. | |
12708 | ||
9c16f35a EZ |
12709 | @kindex show case-sensitive |
12710 | @item show case-sensitive | |
a8f24a35 EZ |
12711 | This command shows the current setting of case sensitivity for symbols |
12712 | lookups. | |
12713 | ||
c906108c | 12714 | @kindex info address |
b37052ae | 12715 | @cindex address of a symbol |
c906108c SS |
12716 | @item info address @var{symbol} |
12717 | Describe where the data for @var{symbol} is stored. For a register | |
12718 | variable, this says which register it is kept in. For a non-register | |
12719 | local variable, this prints the stack-frame offset at which the variable | |
12720 | is always stored. | |
12721 | ||
12722 | Note the contrast with @samp{print &@var{symbol}}, which does not work | |
12723 | at all for a register variable, and for a stack local variable prints | |
12724 | the exact address of the current instantiation of the variable. | |
12725 | ||
3d67e040 | 12726 | @kindex info symbol |
b37052ae | 12727 | @cindex symbol from address |
9c16f35a | 12728 | @cindex closest symbol and offset for an address |
3d67e040 EZ |
12729 | @item info symbol @var{addr} |
12730 | Print the name of a symbol which is stored at the address @var{addr}. | |
12731 | If no symbol is stored exactly at @var{addr}, @value{GDBN} prints the | |
12732 | nearest symbol and an offset from it: | |
12733 | ||
474c8240 | 12734 | @smallexample |
3d67e040 EZ |
12735 | (@value{GDBP}) info symbol 0x54320 |
12736 | _initialize_vx + 396 in section .text | |
474c8240 | 12737 | @end smallexample |
3d67e040 EZ |
12738 | |
12739 | @noindent | |
12740 | This is the opposite of the @code{info address} command. You can use | |
12741 | it to find out the name of a variable or a function given its address. | |
12742 | ||
c14c28ba PP |
12743 | For dynamically linked executables, the name of executable or shared |
12744 | library containing the symbol is also printed: | |
12745 | ||
12746 | @smallexample | |
12747 | (@value{GDBP}) info symbol 0x400225 | |
12748 | _start + 5 in section .text of /tmp/a.out | |
12749 | (@value{GDBP}) info symbol 0x2aaaac2811cf | |
12750 | __read_nocancel + 6 in section .text of /usr/lib64/libc.so.6 | |
12751 | @end smallexample | |
12752 | ||
c906108c | 12753 | @kindex whatis |
62f3a2ba FF |
12754 | @item whatis [@var{arg}] |
12755 | Print the data type of @var{arg}, which can be either an expression or | |
12756 | a data type. With no argument, print the data type of @code{$}, the | |
12757 | last value in the value history. If @var{arg} is an expression, it is | |
12758 | not actually evaluated, and any side-effecting operations (such as | |
12759 | assignments or function calls) inside it do not take place. If | |
12760 | @var{arg} is a type name, it may be the name of a type or typedef, or | |
12761 | for C code it may have the form @samp{class @var{class-name}}, | |
12762 | @samp{struct @var{struct-tag}}, @samp{union @var{union-tag}} or | |
12763 | @samp{enum @var{enum-tag}}. | |
c906108c SS |
12764 | @xref{Expressions, ,Expressions}. |
12765 | ||
c906108c | 12766 | @kindex ptype |
62f3a2ba FF |
12767 | @item ptype [@var{arg}] |
12768 | @code{ptype} accepts the same arguments as @code{whatis}, but prints a | |
12769 | detailed description of the type, instead of just the name of the type. | |
12770 | @xref{Expressions, ,Expressions}. | |
c906108c SS |
12771 | |
12772 | For example, for this variable declaration: | |
12773 | ||
474c8240 | 12774 | @smallexample |
c906108c | 12775 | struct complex @{double real; double imag;@} v; |
474c8240 | 12776 | @end smallexample |
c906108c SS |
12777 | |
12778 | @noindent | |
12779 | the two commands give this output: | |
12780 | ||
474c8240 | 12781 | @smallexample |
c906108c SS |
12782 | @group |
12783 | (@value{GDBP}) whatis v | |
12784 | type = struct complex | |
12785 | (@value{GDBP}) ptype v | |
12786 | type = struct complex @{ | |
12787 | double real; | |
12788 | double imag; | |
12789 | @} | |
12790 | @end group | |
474c8240 | 12791 | @end smallexample |
c906108c SS |
12792 | |
12793 | @noindent | |
12794 | As with @code{whatis}, using @code{ptype} without an argument refers to | |
12795 | the type of @code{$}, the last value in the value history. | |
12796 | ||
ab1adacd EZ |
12797 | @cindex incomplete type |
12798 | Sometimes, programs use opaque data types or incomplete specifications | |
12799 | of complex data structure. If the debug information included in the | |
12800 | program does not allow @value{GDBN} to display a full declaration of | |
12801 | the data type, it will say @samp{<incomplete type>}. For example, | |
12802 | given these declarations: | |
12803 | ||
12804 | @smallexample | |
12805 | struct foo; | |
12806 | struct foo *fooptr; | |
12807 | @end smallexample | |
12808 | ||
12809 | @noindent | |
12810 | but no definition for @code{struct foo} itself, @value{GDBN} will say: | |
12811 | ||
12812 | @smallexample | |
ddb50cd7 | 12813 | (@value{GDBP}) ptype foo |
ab1adacd EZ |
12814 | $1 = <incomplete type> |
12815 | @end smallexample | |
12816 | ||
12817 | @noindent | |
12818 | ``Incomplete type'' is C terminology for data types that are not | |
12819 | completely specified. | |
12820 | ||
c906108c SS |
12821 | @kindex info types |
12822 | @item info types @var{regexp} | |
12823 | @itemx info types | |
09d4efe1 EZ |
12824 | Print a brief description of all types whose names match the regular |
12825 | expression @var{regexp} (or all types in your program, if you supply | |
12826 | no argument). Each complete typename is matched as though it were a | |
12827 | complete line; thus, @samp{i type value} gives information on all | |
12828 | types in your program whose names include the string @code{value}, but | |
12829 | @samp{i type ^value$} gives information only on types whose complete | |
12830 | name is @code{value}. | |
c906108c SS |
12831 | |
12832 | This command differs from @code{ptype} in two ways: first, like | |
12833 | @code{whatis}, it does not print a detailed description; second, it | |
12834 | lists all source files where a type is defined. | |
12835 | ||
b37052ae EZ |
12836 | @kindex info scope |
12837 | @cindex local variables | |
09d4efe1 | 12838 | @item info scope @var{location} |
b37052ae | 12839 | List all the variables local to a particular scope. This command |
09d4efe1 EZ |
12840 | accepts a @var{location} argument---a function name, a source line, or |
12841 | an address preceded by a @samp{*}, and prints all the variables local | |
2a25a5ba EZ |
12842 | to the scope defined by that location. (@xref{Specify Location}, for |
12843 | details about supported forms of @var{location}.) For example: | |
b37052ae EZ |
12844 | |
12845 | @smallexample | |
12846 | (@value{GDBP}) @b{info scope command_line_handler} | |
12847 | Scope for command_line_handler: | |
12848 | Symbol rl is an argument at stack/frame offset 8, length 4. | |
12849 | Symbol linebuffer is in static storage at address 0x150a18, length 4. | |
12850 | Symbol linelength is in static storage at address 0x150a1c, length 4. | |
12851 | Symbol p is a local variable in register $esi, length 4. | |
12852 | Symbol p1 is a local variable in register $ebx, length 4. | |
12853 | Symbol nline is a local variable in register $edx, length 4. | |
12854 | Symbol repeat is a local variable at frame offset -8, length 4. | |
12855 | @end smallexample | |
12856 | ||
f5c37c66 EZ |
12857 | @noindent |
12858 | This command is especially useful for determining what data to collect | |
12859 | during a @dfn{trace experiment}, see @ref{Tracepoint Actions, | |
12860 | collect}. | |
12861 | ||
c906108c SS |
12862 | @kindex info source |
12863 | @item info source | |
919d772c JB |
12864 | Show information about the current source file---that is, the source file for |
12865 | the function containing the current point of execution: | |
12866 | @itemize @bullet | |
12867 | @item | |
12868 | the name of the source file, and the directory containing it, | |
12869 | @item | |
12870 | the directory it was compiled in, | |
12871 | @item | |
12872 | its length, in lines, | |
12873 | @item | |
12874 | which programming language it is written in, | |
12875 | @item | |
12876 | whether the executable includes debugging information for that file, and | |
12877 | if so, what format the information is in (e.g., STABS, Dwarf 2, etc.), and | |
12878 | @item | |
12879 | whether the debugging information includes information about | |
12880 | preprocessor macros. | |
12881 | @end itemize | |
12882 | ||
c906108c SS |
12883 | |
12884 | @kindex info sources | |
12885 | @item info sources | |
12886 | Print the names of all source files in your program for which there is | |
12887 | debugging information, organized into two lists: files whose symbols | |
12888 | have already been read, and files whose symbols will be read when needed. | |
12889 | ||
12890 | @kindex info functions | |
12891 | @item info functions | |
12892 | Print the names and data types of all defined functions. | |
12893 | ||
12894 | @item info functions @var{regexp} | |
12895 | Print the names and data types of all defined functions | |
12896 | whose names contain a match for regular expression @var{regexp}. | |
12897 | Thus, @samp{info fun step} finds all functions whose names | |
12898 | include @code{step}; @samp{info fun ^step} finds those whose names | |
b383017d | 12899 | start with @code{step}. If a function name contains characters |
c1468174 | 12900 | that conflict with the regular expression language (e.g.@: |
1c5dfdad | 12901 | @samp{operator*()}), they may be quoted with a backslash. |
c906108c SS |
12902 | |
12903 | @kindex info variables | |
12904 | @item info variables | |
12905 | Print the names and data types of all variables that are declared | |
6ca652b0 | 12906 | outside of functions (i.e.@: excluding local variables). |
c906108c SS |
12907 | |
12908 | @item info variables @var{regexp} | |
12909 | Print the names and data types of all variables (except for local | |
12910 | variables) whose names contain a match for regular expression | |
12911 | @var{regexp}. | |
12912 | ||
b37303ee | 12913 | @kindex info classes |
721c2651 | 12914 | @cindex Objective-C, classes and selectors |
b37303ee AF |
12915 | @item info classes |
12916 | @itemx info classes @var{regexp} | |
12917 | Display all Objective-C classes in your program, or | |
12918 | (with the @var{regexp} argument) all those matching a particular regular | |
12919 | expression. | |
12920 | ||
12921 | @kindex info selectors | |
12922 | @item info selectors | |
12923 | @itemx info selectors @var{regexp} | |
12924 | Display all Objective-C selectors in your program, or | |
12925 | (with the @var{regexp} argument) all those matching a particular regular | |
12926 | expression. | |
12927 | ||
c906108c SS |
12928 | @ignore |
12929 | This was never implemented. | |
12930 | @kindex info methods | |
12931 | @item info methods | |
12932 | @itemx info methods @var{regexp} | |
12933 | The @code{info methods} command permits the user to examine all defined | |
b37052ae EZ |
12934 | methods within C@t{++} program, or (with the @var{regexp} argument) a |
12935 | specific set of methods found in the various C@t{++} classes. Many | |
12936 | C@t{++} classes provide a large number of methods. Thus, the output | |
c906108c SS |
12937 | from the @code{ptype} command can be overwhelming and hard to use. The |
12938 | @code{info-methods} command filters the methods, printing only those | |
12939 | which match the regular-expression @var{regexp}. | |
12940 | @end ignore | |
12941 | ||
c906108c SS |
12942 | @cindex reloading symbols |
12943 | Some systems allow individual object files that make up your program to | |
7a292a7a SS |
12944 | be replaced without stopping and restarting your program. For example, |
12945 | in VxWorks you can simply recompile a defective object file and keep on | |
12946 | running. If you are running on one of these systems, you can allow | |
12947 | @value{GDBN} to reload the symbols for automatically relinked modules: | |
c906108c SS |
12948 | |
12949 | @table @code | |
12950 | @kindex set symbol-reloading | |
12951 | @item set symbol-reloading on | |
12952 | Replace symbol definitions for the corresponding source file when an | |
12953 | object file with a particular name is seen again. | |
12954 | ||
12955 | @item set symbol-reloading off | |
6d2ebf8b SS |
12956 | Do not replace symbol definitions when encountering object files of the |
12957 | same name more than once. This is the default state; if you are not | |
12958 | running on a system that permits automatic relinking of modules, you | |
12959 | should leave @code{symbol-reloading} off, since otherwise @value{GDBN} | |
12960 | may discard symbols when linking large programs, that may contain | |
12961 | several modules (from different directories or libraries) with the same | |
12962 | name. | |
c906108c SS |
12963 | |
12964 | @kindex show symbol-reloading | |
12965 | @item show symbol-reloading | |
12966 | Show the current @code{on} or @code{off} setting. | |
12967 | @end table | |
c906108c | 12968 | |
9c16f35a | 12969 | @cindex opaque data types |
c906108c SS |
12970 | @kindex set opaque-type-resolution |
12971 | @item set opaque-type-resolution on | |
12972 | Tell @value{GDBN} to resolve opaque types. An opaque type is a type | |
12973 | declared as a pointer to a @code{struct}, @code{class}, or | |
12974 | @code{union}---for example, @code{struct MyType *}---that is used in one | |
12975 | source file although the full declaration of @code{struct MyType} is in | |
12976 | another source file. The default is on. | |
12977 | ||
12978 | A change in the setting of this subcommand will not take effect until | |
12979 | the next time symbols for a file are loaded. | |
12980 | ||
12981 | @item set opaque-type-resolution off | |
12982 | Tell @value{GDBN} not to resolve opaque types. In this case, the type | |
12983 | is printed as follows: | |
12984 | @smallexample | |
12985 | @{<no data fields>@} | |
12986 | @end smallexample | |
12987 | ||
12988 | @kindex show opaque-type-resolution | |
12989 | @item show opaque-type-resolution | |
12990 | Show whether opaque types are resolved or not. | |
c906108c SS |
12991 | |
12992 | @kindex maint print symbols | |
12993 | @cindex symbol dump | |
12994 | @kindex maint print psymbols | |
12995 | @cindex partial symbol dump | |
12996 | @item maint print symbols @var{filename} | |
12997 | @itemx maint print psymbols @var{filename} | |
12998 | @itemx maint print msymbols @var{filename} | |
12999 | Write a dump of debugging symbol data into the file @var{filename}. | |
13000 | These commands are used to debug the @value{GDBN} symbol-reading code. Only | |
13001 | symbols with debugging data are included. If you use @samp{maint print | |
13002 | symbols}, @value{GDBN} includes all the symbols for which it has already | |
13003 | collected full details: that is, @var{filename} reflects symbols for | |
13004 | only those files whose symbols @value{GDBN} has read. You can use the | |
13005 | command @code{info sources} to find out which files these are. If you | |
13006 | use @samp{maint print psymbols} instead, the dump shows information about | |
13007 | symbols that @value{GDBN} only knows partially---that is, symbols defined in | |
13008 | files that @value{GDBN} has skimmed, but not yet read completely. Finally, | |
13009 | @samp{maint print msymbols} dumps just the minimal symbol information | |
13010 | required for each object file from which @value{GDBN} has read some symbols. | |
79a6e687 | 13011 | @xref{Files, ,Commands to Specify Files}, for a discussion of how |
c906108c | 13012 | @value{GDBN} reads symbols (in the description of @code{symbol-file}). |
44ea7b70 | 13013 | |
5e7b2f39 JB |
13014 | @kindex maint info symtabs |
13015 | @kindex maint info psymtabs | |
44ea7b70 JB |
13016 | @cindex listing @value{GDBN}'s internal symbol tables |
13017 | @cindex symbol tables, listing @value{GDBN}'s internal | |
13018 | @cindex full symbol tables, listing @value{GDBN}'s internal | |
13019 | @cindex partial symbol tables, listing @value{GDBN}'s internal | |
5e7b2f39 JB |
13020 | @item maint info symtabs @r{[} @var{regexp} @r{]} |
13021 | @itemx maint info psymtabs @r{[} @var{regexp} @r{]} | |
44ea7b70 JB |
13022 | |
13023 | List the @code{struct symtab} or @code{struct partial_symtab} | |
13024 | structures whose names match @var{regexp}. If @var{regexp} is not | |
13025 | given, list them all. The output includes expressions which you can | |
13026 | copy into a @value{GDBN} debugging this one to examine a particular | |
13027 | structure in more detail. For example: | |
13028 | ||
13029 | @smallexample | |
5e7b2f39 | 13030 | (@value{GDBP}) maint info psymtabs dwarf2read |
44ea7b70 JB |
13031 | @{ objfile /home/gnu/build/gdb/gdb |
13032 | ((struct objfile *) 0x82e69d0) | |
b383017d | 13033 | @{ psymtab /home/gnu/src/gdb/dwarf2read.c |
44ea7b70 JB |
13034 | ((struct partial_symtab *) 0x8474b10) |
13035 | readin no | |
13036 | fullname (null) | |
13037 | text addresses 0x814d3c8 -- 0x8158074 | |
13038 | globals (* (struct partial_symbol **) 0x8507a08 @@ 9) | |
13039 | statics (* (struct partial_symbol **) 0x40e95b78 @@ 2882) | |
13040 | dependencies (none) | |
13041 | @} | |
13042 | @} | |
5e7b2f39 | 13043 | (@value{GDBP}) maint info symtabs |
44ea7b70 JB |
13044 | (@value{GDBP}) |
13045 | @end smallexample | |
13046 | @noindent | |
13047 | We see that there is one partial symbol table whose filename contains | |
13048 | the string @samp{dwarf2read}, belonging to the @samp{gdb} executable; | |
13049 | and we see that @value{GDBN} has not read in any symtabs yet at all. | |
13050 | If we set a breakpoint on a function, that will cause @value{GDBN} to | |
13051 | read the symtab for the compilation unit containing that function: | |
13052 | ||
13053 | @smallexample | |
13054 | (@value{GDBP}) break dwarf2_psymtab_to_symtab | |
13055 | Breakpoint 1 at 0x814e5da: file /home/gnu/src/gdb/dwarf2read.c, | |
13056 | line 1574. | |
5e7b2f39 | 13057 | (@value{GDBP}) maint info symtabs |
b383017d | 13058 | @{ objfile /home/gnu/build/gdb/gdb |
44ea7b70 | 13059 | ((struct objfile *) 0x82e69d0) |
b383017d | 13060 | @{ symtab /home/gnu/src/gdb/dwarf2read.c |
44ea7b70 JB |
13061 | ((struct symtab *) 0x86c1f38) |
13062 | dirname (null) | |
13063 | fullname (null) | |
13064 | blockvector ((struct blockvector *) 0x86c1bd0) (primary) | |
1b39d5c0 | 13065 | linetable ((struct linetable *) 0x8370fa0) |
44ea7b70 JB |
13066 | debugformat DWARF 2 |
13067 | @} | |
13068 | @} | |
b383017d | 13069 | (@value{GDBP}) |
44ea7b70 | 13070 | @end smallexample |
c906108c SS |
13071 | @end table |
13072 | ||
44ea7b70 | 13073 | |
6d2ebf8b | 13074 | @node Altering |
c906108c SS |
13075 | @chapter Altering Execution |
13076 | ||
13077 | Once you think you have found an error in your program, you might want to | |
13078 | find out for certain whether correcting the apparent error would lead to | |
13079 | correct results in the rest of the run. You can find the answer by | |
13080 | experiment, using the @value{GDBN} features for altering execution of the | |
13081 | program. | |
13082 | ||
13083 | For example, you can store new values into variables or memory | |
7a292a7a SS |
13084 | locations, give your program a signal, restart it at a different |
13085 | address, or even return prematurely from a function. | |
c906108c SS |
13086 | |
13087 | @menu | |
13088 | * Assignment:: Assignment to variables | |
13089 | * Jumping:: Continuing at a different address | |
c906108c | 13090 | * Signaling:: Giving your program a signal |
c906108c SS |
13091 | * Returning:: Returning from a function |
13092 | * Calling:: Calling your program's functions | |
13093 | * Patching:: Patching your program | |
13094 | @end menu | |
13095 | ||
6d2ebf8b | 13096 | @node Assignment |
79a6e687 | 13097 | @section Assignment to Variables |
c906108c SS |
13098 | |
13099 | @cindex assignment | |
13100 | @cindex setting variables | |
13101 | To alter the value of a variable, evaluate an assignment expression. | |
13102 | @xref{Expressions, ,Expressions}. For example, | |
13103 | ||
474c8240 | 13104 | @smallexample |
c906108c | 13105 | print x=4 |
474c8240 | 13106 | @end smallexample |
c906108c SS |
13107 | |
13108 | @noindent | |
13109 | stores the value 4 into the variable @code{x}, and then prints the | |
5d161b24 | 13110 | value of the assignment expression (which is 4). |
c906108c SS |
13111 | @xref{Languages, ,Using @value{GDBN} with Different Languages}, for more |
13112 | information on operators in supported languages. | |
c906108c SS |
13113 | |
13114 | @kindex set variable | |
13115 | @cindex variables, setting | |
13116 | If you are not interested in seeing the value of the assignment, use the | |
13117 | @code{set} command instead of the @code{print} command. @code{set} is | |
13118 | really the same as @code{print} except that the expression's value is | |
13119 | not printed and is not put in the value history (@pxref{Value History, | |
79a6e687 | 13120 | ,Value History}). The expression is evaluated only for its effects. |
c906108c | 13121 | |
c906108c SS |
13122 | If the beginning of the argument string of the @code{set} command |
13123 | appears identical to a @code{set} subcommand, use the @code{set | |
13124 | variable} command instead of just @code{set}. This command is identical | |
13125 | to @code{set} except for its lack of subcommands. For example, if your | |
13126 | program has a variable @code{width}, you get an error if you try to set | |
13127 | a new value with just @samp{set width=13}, because @value{GDBN} has the | |
13128 | command @code{set width}: | |
13129 | ||
474c8240 | 13130 | @smallexample |
c906108c SS |
13131 | (@value{GDBP}) whatis width |
13132 | type = double | |
13133 | (@value{GDBP}) p width | |
13134 | $4 = 13 | |
13135 | (@value{GDBP}) set width=47 | |
13136 | Invalid syntax in expression. | |
474c8240 | 13137 | @end smallexample |
c906108c SS |
13138 | |
13139 | @noindent | |
13140 | The invalid expression, of course, is @samp{=47}. In | |
13141 | order to actually set the program's variable @code{width}, use | |
13142 | ||
474c8240 | 13143 | @smallexample |
c906108c | 13144 | (@value{GDBP}) set var width=47 |
474c8240 | 13145 | @end smallexample |
53a5351d | 13146 | |
c906108c SS |
13147 | Because the @code{set} command has many subcommands that can conflict |
13148 | with the names of program variables, it is a good idea to use the | |
13149 | @code{set variable} command instead of just @code{set}. For example, if | |
13150 | your program has a variable @code{g}, you run into problems if you try | |
13151 | to set a new value with just @samp{set g=4}, because @value{GDBN} has | |
13152 | the command @code{set gnutarget}, abbreviated @code{set g}: | |
13153 | ||
474c8240 | 13154 | @smallexample |
c906108c SS |
13155 | @group |
13156 | (@value{GDBP}) whatis g | |
13157 | type = double | |
13158 | (@value{GDBP}) p g | |
13159 | $1 = 1 | |
13160 | (@value{GDBP}) set g=4 | |
2df3850c | 13161 | (@value{GDBP}) p g |
c906108c SS |
13162 | $2 = 1 |
13163 | (@value{GDBP}) r | |
13164 | The program being debugged has been started already. | |
13165 | Start it from the beginning? (y or n) y | |
13166 | Starting program: /home/smith/cc_progs/a.out | |
6d2ebf8b SS |
13167 | "/home/smith/cc_progs/a.out": can't open to read symbols: |
13168 | Invalid bfd target. | |
c906108c SS |
13169 | (@value{GDBP}) show g |
13170 | The current BFD target is "=4". | |
13171 | @end group | |
474c8240 | 13172 | @end smallexample |
c906108c SS |
13173 | |
13174 | @noindent | |
13175 | The program variable @code{g} did not change, and you silently set the | |
13176 | @code{gnutarget} to an invalid value. In order to set the variable | |
13177 | @code{g}, use | |
13178 | ||
474c8240 | 13179 | @smallexample |
c906108c | 13180 | (@value{GDBP}) set var g=4 |
474c8240 | 13181 | @end smallexample |
c906108c SS |
13182 | |
13183 | @value{GDBN} allows more implicit conversions in assignments than C; you can | |
13184 | freely store an integer value into a pointer variable or vice versa, | |
13185 | and you can convert any structure to any other structure that is the | |
13186 | same length or shorter. | |
13187 | @comment FIXME: how do structs align/pad in these conversions? | |
13188 | @comment /doc@cygnus.com 18dec1990 | |
13189 | ||
13190 | To store values into arbitrary places in memory, use the @samp{@{@dots{}@}} | |
13191 | construct to generate a value of specified type at a specified address | |
13192 | (@pxref{Expressions, ,Expressions}). For example, @code{@{int@}0x83040} refers | |
13193 | to memory location @code{0x83040} as an integer (which implies a certain size | |
13194 | and representation in memory), and | |
13195 | ||
474c8240 | 13196 | @smallexample |
c906108c | 13197 | set @{int@}0x83040 = 4 |
474c8240 | 13198 | @end smallexample |
c906108c SS |
13199 | |
13200 | @noindent | |
13201 | stores the value 4 into that memory location. | |
13202 | ||
6d2ebf8b | 13203 | @node Jumping |
79a6e687 | 13204 | @section Continuing at a Different Address |
c906108c SS |
13205 | |
13206 | Ordinarily, when you continue your program, you do so at the place where | |
13207 | it stopped, with the @code{continue} command. You can instead continue at | |
13208 | an address of your own choosing, with the following commands: | |
13209 | ||
13210 | @table @code | |
13211 | @kindex jump | |
13212 | @item jump @var{linespec} | |
2a25a5ba EZ |
13213 | @itemx jump @var{location} |
13214 | Resume execution at line @var{linespec} or at address given by | |
13215 | @var{location}. Execution stops again immediately if there is a | |
13216 | breakpoint there. @xref{Specify Location}, for a description of the | |
13217 | different forms of @var{linespec} and @var{location}. It is common | |
13218 | practice to use the @code{tbreak} command in conjunction with | |
13219 | @code{jump}. @xref{Set Breaks, ,Setting Breakpoints}. | |
c906108c SS |
13220 | |
13221 | The @code{jump} command does not change the current stack frame, or | |
13222 | the stack pointer, or the contents of any memory location or any | |
13223 | register other than the program counter. If line @var{linespec} is in | |
13224 | a different function from the one currently executing, the results may | |
13225 | be bizarre if the two functions expect different patterns of arguments or | |
13226 | of local variables. For this reason, the @code{jump} command requests | |
13227 | confirmation if the specified line is not in the function currently | |
13228 | executing. However, even bizarre results are predictable if you are | |
13229 | well acquainted with the machine-language code of your program. | |
c906108c SS |
13230 | @end table |
13231 | ||
c906108c | 13232 | @c Doesn't work on HP-UX; have to set $pcoqh and $pcoqt. |
53a5351d JM |
13233 | On many systems, you can get much the same effect as the @code{jump} |
13234 | command by storing a new value into the register @code{$pc}. The | |
13235 | difference is that this does not start your program running; it only | |
13236 | changes the address of where it @emph{will} run when you continue. For | |
13237 | example, | |
c906108c | 13238 | |
474c8240 | 13239 | @smallexample |
c906108c | 13240 | set $pc = 0x485 |
474c8240 | 13241 | @end smallexample |
c906108c SS |
13242 | |
13243 | @noindent | |
13244 | makes the next @code{continue} command or stepping command execute at | |
13245 | address @code{0x485}, rather than at the address where your program stopped. | |
79a6e687 | 13246 | @xref{Continuing and Stepping, ,Continuing and Stepping}. |
c906108c SS |
13247 | |
13248 | The most common occasion to use the @code{jump} command is to back | |
13249 | up---perhaps with more breakpoints set---over a portion of a program | |
13250 | that has already executed, in order to examine its execution in more | |
13251 | detail. | |
13252 | ||
c906108c | 13253 | @c @group |
6d2ebf8b | 13254 | @node Signaling |
79a6e687 | 13255 | @section Giving your Program a Signal |
9c16f35a | 13256 | @cindex deliver a signal to a program |
c906108c SS |
13257 | |
13258 | @table @code | |
13259 | @kindex signal | |
13260 | @item signal @var{signal} | |
13261 | Resume execution where your program stopped, but immediately give it the | |
13262 | signal @var{signal}. @var{signal} can be the name or the number of a | |
13263 | signal. For example, on many systems @code{signal 2} and @code{signal | |
13264 | SIGINT} are both ways of sending an interrupt signal. | |
13265 | ||
13266 | Alternatively, if @var{signal} is zero, continue execution without | |
13267 | giving a signal. This is useful when your program stopped on account of | |
13268 | a signal and would ordinary see the signal when resumed with the | |
13269 | @code{continue} command; @samp{signal 0} causes it to resume without a | |
13270 | signal. | |
13271 | ||
13272 | @code{signal} does not repeat when you press @key{RET} a second time | |
13273 | after executing the command. | |
13274 | @end table | |
13275 | @c @end group | |
13276 | ||
13277 | Invoking the @code{signal} command is not the same as invoking the | |
13278 | @code{kill} utility from the shell. Sending a signal with @code{kill} | |
13279 | causes @value{GDBN} to decide what to do with the signal depending on | |
13280 | the signal handling tables (@pxref{Signals}). The @code{signal} command | |
13281 | passes the signal directly to your program. | |
13282 | ||
c906108c | 13283 | |
6d2ebf8b | 13284 | @node Returning |
79a6e687 | 13285 | @section Returning from a Function |
c906108c SS |
13286 | |
13287 | @table @code | |
13288 | @cindex returning from a function | |
13289 | @kindex return | |
13290 | @item return | |
13291 | @itemx return @var{expression} | |
13292 | You can cancel execution of a function call with the @code{return} | |
13293 | command. If you give an | |
13294 | @var{expression} argument, its value is used as the function's return | |
13295 | value. | |
13296 | @end table | |
13297 | ||
13298 | When you use @code{return}, @value{GDBN} discards the selected stack frame | |
13299 | (and all frames within it). You can think of this as making the | |
13300 | discarded frame return prematurely. If you wish to specify a value to | |
13301 | be returned, give that value as the argument to @code{return}. | |
13302 | ||
13303 | This pops the selected stack frame (@pxref{Selection, ,Selecting a | |
79a6e687 | 13304 | Frame}), and any other frames inside of it, leaving its caller as the |
c906108c SS |
13305 | innermost remaining frame. That frame becomes selected. The |
13306 | specified value is stored in the registers used for returning values | |
13307 | of functions. | |
13308 | ||
13309 | The @code{return} command does not resume execution; it leaves the | |
13310 | program stopped in the state that would exist if the function had just | |
13311 | returned. In contrast, the @code{finish} command (@pxref{Continuing | |
79a6e687 | 13312 | and Stepping, ,Continuing and Stepping}) resumes execution until the |
c906108c SS |
13313 | selected stack frame returns naturally. |
13314 | ||
61ff14c6 JK |
13315 | @value{GDBN} needs to know how the @var{expression} argument should be set for |
13316 | the inferior. The concrete registers assignment depends on the OS ABI and the | |
13317 | type being returned by the selected stack frame. For example it is common for | |
13318 | OS ABI to return floating point values in FPU registers while integer values in | |
13319 | CPU registers. Still some ABIs return even floating point values in CPU | |
13320 | registers. Larger integer widths (such as @code{long long int}) also have | |
13321 | specific placement rules. @value{GDBN} already knows the OS ABI from its | |
13322 | current target so it needs to find out also the type being returned to make the | |
13323 | assignment into the right register(s). | |
13324 | ||
13325 | Normally, the selected stack frame has debug info. @value{GDBN} will always | |
13326 | use the debug info instead of the implicit type of @var{expression} when the | |
13327 | debug info is available. For example, if you type @kbd{return -1}, and the | |
13328 | function in the current stack frame is declared to return a @code{long long | |
13329 | int}, @value{GDBN} transparently converts the implicit @code{int} value of -1 | |
13330 | into a @code{long long int}: | |
13331 | ||
13332 | @smallexample | |
13333 | Breakpoint 1, func () at gdb.base/return-nodebug.c:29 | |
13334 | 29 return 31; | |
13335 | (@value{GDBP}) return -1 | |
13336 | Make func return now? (y or n) y | |
13337 | #0 0x004004f6 in main () at gdb.base/return-nodebug.c:43 | |
13338 | 43 printf ("result=%lld\n", func ()); | |
13339 | (@value{GDBP}) | |
13340 | @end smallexample | |
13341 | ||
13342 | However, if the selected stack frame does not have a debug info, e.g., if the | |
13343 | function was compiled without debug info, @value{GDBN} has to find out the type | |
13344 | to return from user. Specifying a different type by mistake may set the value | |
13345 | in different inferior registers than the caller code expects. For example, | |
13346 | typing @kbd{return -1} with its implicit type @code{int} would set only a part | |
13347 | of a @code{long long int} result for a debug info less function (on 32-bit | |
13348 | architectures). Therefore the user is required to specify the return type by | |
13349 | an appropriate cast explicitly: | |
13350 | ||
13351 | @smallexample | |
13352 | Breakpoint 2, 0x0040050b in func () | |
13353 | (@value{GDBP}) return -1 | |
13354 | Return value type not available for selected stack frame. | |
13355 | Please use an explicit cast of the value to return. | |
13356 | (@value{GDBP}) return (long long int) -1 | |
13357 | Make selected stack frame return now? (y or n) y | |
13358 | #0 0x00400526 in main () | |
13359 | (@value{GDBP}) | |
13360 | @end smallexample | |
13361 | ||
6d2ebf8b | 13362 | @node Calling |
79a6e687 | 13363 | @section Calling Program Functions |
c906108c | 13364 | |
f8568604 | 13365 | @table @code |
c906108c | 13366 | @cindex calling functions |
f8568604 EZ |
13367 | @cindex inferior functions, calling |
13368 | @item print @var{expr} | |
d3e8051b | 13369 | Evaluate the expression @var{expr} and display the resulting value. |
f8568604 EZ |
13370 | @var{expr} may include calls to functions in the program being |
13371 | debugged. | |
13372 | ||
c906108c | 13373 | @kindex call |
c906108c SS |
13374 | @item call @var{expr} |
13375 | Evaluate the expression @var{expr} without displaying @code{void} | |
13376 | returned values. | |
c906108c SS |
13377 | |
13378 | You can use this variant of the @code{print} command if you want to | |
f8568604 EZ |
13379 | execute a function from your program that does not return anything |
13380 | (a.k.a.@: @dfn{a void function}), but without cluttering the output | |
13381 | with @code{void} returned values that @value{GDBN} will otherwise | |
13382 | print. If the result is not void, it is printed and saved in the | |
13383 | value history. | |
13384 | @end table | |
13385 | ||
9c16f35a EZ |
13386 | It is possible for the function you call via the @code{print} or |
13387 | @code{call} command to generate a signal (e.g., if there's a bug in | |
13388 | the function, or if you passed it incorrect arguments). What happens | |
13389 | in that case is controlled by the @code{set unwindonsignal} command. | |
13390 | ||
7cd1089b PM |
13391 | Similarly, with a C@t{++} program it is possible for the function you |
13392 | call via the @code{print} or @code{call} command to generate an | |
13393 | exception that is not handled due to the constraints of the dummy | |
13394 | frame. In this case, any exception that is raised in the frame, but has | |
13395 | an out-of-frame exception handler will not be found. GDB builds a | |
13396 | dummy-frame for the inferior function call, and the unwinder cannot | |
13397 | seek for exception handlers outside of this dummy-frame. What happens | |
13398 | in that case is controlled by the | |
13399 | @code{set unwind-on-terminating-exception} command. | |
13400 | ||
9c16f35a EZ |
13401 | @table @code |
13402 | @item set unwindonsignal | |
13403 | @kindex set unwindonsignal | |
13404 | @cindex unwind stack in called functions | |
13405 | @cindex call dummy stack unwinding | |
13406 | Set unwinding of the stack if a signal is received while in a function | |
13407 | that @value{GDBN} called in the program being debugged. If set to on, | |
13408 | @value{GDBN} unwinds the stack it created for the call and restores | |
13409 | the context to what it was before the call. If set to off (the | |
13410 | default), @value{GDBN} stops in the frame where the signal was | |
13411 | received. | |
13412 | ||
13413 | @item show unwindonsignal | |
13414 | @kindex show unwindonsignal | |
13415 | Show the current setting of stack unwinding in the functions called by | |
13416 | @value{GDBN}. | |
7cd1089b PM |
13417 | |
13418 | @item set unwind-on-terminating-exception | |
13419 | @kindex set unwind-on-terminating-exception | |
13420 | @cindex unwind stack in called functions with unhandled exceptions | |
13421 | @cindex call dummy stack unwinding on unhandled exception. | |
13422 | Set unwinding of the stack if a C@t{++} exception is raised, but left | |
13423 | unhandled while in a function that @value{GDBN} called in the program being | |
13424 | debugged. If set to on (the default), @value{GDBN} unwinds the stack | |
13425 | it created for the call and restores the context to what it was before | |
13426 | the call. If set to off, @value{GDBN} the exception is delivered to | |
13427 | the default C@t{++} exception handler and the inferior terminated. | |
13428 | ||
13429 | @item show unwind-on-terminating-exception | |
13430 | @kindex show unwind-on-terminating-exception | |
13431 | Show the current setting of stack unwinding in the functions called by | |
13432 | @value{GDBN}. | |
13433 | ||
9c16f35a EZ |
13434 | @end table |
13435 | ||
f8568604 EZ |
13436 | @cindex weak alias functions |
13437 | Sometimes, a function you wish to call is actually a @dfn{weak alias} | |
13438 | for another function. In such case, @value{GDBN} might not pick up | |
13439 | the type information, including the types of the function arguments, | |
13440 | which causes @value{GDBN} to call the inferior function incorrectly. | |
13441 | As a result, the called function will function erroneously and may | |
13442 | even crash. A solution to that is to use the name of the aliased | |
13443 | function instead. | |
c906108c | 13444 | |
6d2ebf8b | 13445 | @node Patching |
79a6e687 | 13446 | @section Patching Programs |
7a292a7a | 13447 | |
c906108c SS |
13448 | @cindex patching binaries |
13449 | @cindex writing into executables | |
c906108c | 13450 | @cindex writing into corefiles |
c906108c | 13451 | |
7a292a7a SS |
13452 | By default, @value{GDBN} opens the file containing your program's |
13453 | executable code (or the corefile) read-only. This prevents accidental | |
13454 | alterations to machine code; but it also prevents you from intentionally | |
13455 | patching your program's binary. | |
c906108c SS |
13456 | |
13457 | If you'd like to be able to patch the binary, you can specify that | |
13458 | explicitly with the @code{set write} command. For example, you might | |
13459 | want to turn on internal debugging flags, or even to make emergency | |
13460 | repairs. | |
13461 | ||
13462 | @table @code | |
13463 | @kindex set write | |
13464 | @item set write on | |
13465 | @itemx set write off | |
7a292a7a | 13466 | If you specify @samp{set write on}, @value{GDBN} opens executable and |
20924a55 | 13467 | core files for both reading and writing; if you specify @kbd{set write |
c906108c SS |
13468 | off} (the default), @value{GDBN} opens them read-only. |
13469 | ||
13470 | If you have already loaded a file, you must load it again (using the | |
7a292a7a SS |
13471 | @code{exec-file} or @code{core-file} command) after changing @code{set |
13472 | write}, for your new setting to take effect. | |
c906108c SS |
13473 | |
13474 | @item show write | |
13475 | @kindex show write | |
7a292a7a SS |
13476 | Display whether executable files and core files are opened for writing |
13477 | as well as reading. | |
c906108c SS |
13478 | @end table |
13479 | ||
6d2ebf8b | 13480 | @node GDB Files |
c906108c SS |
13481 | @chapter @value{GDBN} Files |
13482 | ||
7a292a7a SS |
13483 | @value{GDBN} needs to know the file name of the program to be debugged, |
13484 | both in order to read its symbol table and in order to start your | |
13485 | program. To debug a core dump of a previous run, you must also tell | |
13486 | @value{GDBN} the name of the core dump file. | |
c906108c SS |
13487 | |
13488 | @menu | |
13489 | * Files:: Commands to specify files | |
5b5d99cf | 13490 | * Separate Debug Files:: Debugging information in separate files |
c906108c | 13491 | * Symbol Errors:: Errors reading symbol files |
b14b1491 | 13492 | * Data Files:: GDB data files |
c906108c SS |
13493 | @end menu |
13494 | ||
6d2ebf8b | 13495 | @node Files |
79a6e687 | 13496 | @section Commands to Specify Files |
c906108c | 13497 | |
7a292a7a | 13498 | @cindex symbol table |
c906108c | 13499 | @cindex core dump file |
7a292a7a SS |
13500 | |
13501 | You may want to specify executable and core dump file names. The usual | |
13502 | way to do this is at start-up time, using the arguments to | |
13503 | @value{GDBN}'s start-up commands (@pxref{Invocation, , Getting In and | |
13504 | Out of @value{GDBN}}). | |
c906108c SS |
13505 | |
13506 | Occasionally it is necessary to change to a different file during a | |
397ca115 EZ |
13507 | @value{GDBN} session. Or you may run @value{GDBN} and forget to |
13508 | specify a file you want to use. Or you are debugging a remote target | |
79a6e687 BW |
13509 | via @code{gdbserver} (@pxref{Server, file, Using the @code{gdbserver} |
13510 | Program}). In these situations the @value{GDBN} commands to specify | |
0869d01b | 13511 | new files are useful. |
c906108c SS |
13512 | |
13513 | @table @code | |
13514 | @cindex executable file | |
13515 | @kindex file | |
13516 | @item file @var{filename} | |
13517 | Use @var{filename} as the program to be debugged. It is read for its | |
13518 | symbols and for the contents of pure memory. It is also the program | |
13519 | executed when you use the @code{run} command. If you do not specify a | |
5d161b24 DB |
13520 | directory and the file is not found in the @value{GDBN} working directory, |
13521 | @value{GDBN} uses the environment variable @code{PATH} as a list of | |
13522 | directories to search, just as the shell does when looking for a program | |
13523 | to run. You can change the value of this variable, for both @value{GDBN} | |
c906108c SS |
13524 | and your program, using the @code{path} command. |
13525 | ||
fc8be69e EZ |
13526 | @cindex unlinked object files |
13527 | @cindex patching object files | |
13528 | You can load unlinked object @file{.o} files into @value{GDBN} using | |
13529 | the @code{file} command. You will not be able to ``run'' an object | |
13530 | file, but you can disassemble functions and inspect variables. Also, | |
13531 | if the underlying BFD functionality supports it, you could use | |
13532 | @kbd{gdb -write} to patch object files using this technique. Note | |
13533 | that @value{GDBN} can neither interpret nor modify relocations in this | |
13534 | case, so branches and some initialized variables will appear to go to | |
13535 | the wrong place. But this feature is still handy from time to time. | |
13536 | ||
c906108c SS |
13537 | @item file |
13538 | @code{file} with no argument makes @value{GDBN} discard any information it | |
13539 | has on both executable file and the symbol table. | |
13540 | ||
13541 | @kindex exec-file | |
13542 | @item exec-file @r{[} @var{filename} @r{]} | |
13543 | Specify that the program to be run (but not the symbol table) is found | |
13544 | in @var{filename}. @value{GDBN} searches the environment variable @code{PATH} | |
13545 | if necessary to locate your program. Omitting @var{filename} means to | |
13546 | discard information on the executable file. | |
13547 | ||
13548 | @kindex symbol-file | |
13549 | @item symbol-file @r{[} @var{filename} @r{]} | |
13550 | Read symbol table information from file @var{filename}. @code{PATH} is | |
13551 | searched when necessary. Use the @code{file} command to get both symbol | |
13552 | table and program to run from the same file. | |
13553 | ||
13554 | @code{symbol-file} with no argument clears out @value{GDBN} information on your | |
13555 | program's symbol table. | |
13556 | ||
ae5a43e0 DJ |
13557 | The @code{symbol-file} command causes @value{GDBN} to forget the contents of |
13558 | some breakpoints and auto-display expressions. This is because they may | |
13559 | contain pointers to the internal data recording symbols and data types, | |
13560 | which are part of the old symbol table data being discarded inside | |
13561 | @value{GDBN}. | |
c906108c SS |
13562 | |
13563 | @code{symbol-file} does not repeat if you press @key{RET} again after | |
13564 | executing it once. | |
13565 | ||
13566 | When @value{GDBN} is configured for a particular environment, it | |
13567 | understands debugging information in whatever format is the standard | |
13568 | generated for that environment; you may use either a @sc{gnu} compiler, or | |
13569 | other compilers that adhere to the local conventions. | |
c906108c | 13570 | Best results are usually obtained from @sc{gnu} compilers; for example, |
e22ea452 | 13571 | using @code{@value{NGCC}} you can generate debugging information for |
c906108c | 13572 | optimized code. |
c906108c SS |
13573 | |
13574 | For most kinds of object files, with the exception of old SVR3 systems | |
13575 | using COFF, the @code{symbol-file} command does not normally read the | |
13576 | symbol table in full right away. Instead, it scans the symbol table | |
13577 | quickly to find which source files and which symbols are present. The | |
13578 | details are read later, one source file at a time, as they are needed. | |
13579 | ||
13580 | The purpose of this two-stage reading strategy is to make @value{GDBN} | |
13581 | start up faster. For the most part, it is invisible except for | |
13582 | occasional pauses while the symbol table details for a particular source | |
13583 | file are being read. (The @code{set verbose} command can turn these | |
13584 | pauses into messages if desired. @xref{Messages/Warnings, ,Optional | |
79a6e687 | 13585 | Warnings and Messages}.) |
c906108c | 13586 | |
c906108c SS |
13587 | We have not implemented the two-stage strategy for COFF yet. When the |
13588 | symbol table is stored in COFF format, @code{symbol-file} reads the | |
13589 | symbol table data in full right away. Note that ``stabs-in-COFF'' | |
13590 | still does the two-stage strategy, since the debug info is actually | |
13591 | in stabs format. | |
13592 | ||
13593 | @kindex readnow | |
13594 | @cindex reading symbols immediately | |
13595 | @cindex symbols, reading immediately | |
a94ab193 EZ |
13596 | @item symbol-file @var{filename} @r{[} -readnow @r{]} |
13597 | @itemx file @var{filename} @r{[} -readnow @r{]} | |
c906108c SS |
13598 | You can override the @value{GDBN} two-stage strategy for reading symbol |
13599 | tables by using the @samp{-readnow} option with any of the commands that | |
13600 | load symbol table information, if you want to be sure @value{GDBN} has the | |
5d161b24 | 13601 | entire symbol table available. |
c906108c | 13602 | |
c906108c SS |
13603 | @c FIXME: for now no mention of directories, since this seems to be in |
13604 | @c flux. 13mar1992 status is that in theory GDB would look either in | |
13605 | @c current dir or in same dir as myprog; but issues like competing | |
13606 | @c GDB's, or clutter in system dirs, mean that in practice right now | |
13607 | @c only current dir is used. FFish says maybe a special GDB hierarchy | |
13608 | @c (eg rooted in val of env var GDBSYMS) could exist for mappable symbol | |
13609 | @c files. | |
13610 | ||
c906108c | 13611 | @kindex core-file |
09d4efe1 | 13612 | @item core-file @r{[}@var{filename}@r{]} |
4644b6e3 | 13613 | @itemx core |
c906108c SS |
13614 | Specify the whereabouts of a core dump file to be used as the ``contents |
13615 | of memory''. Traditionally, core files contain only some parts of the | |
13616 | address space of the process that generated them; @value{GDBN} can access the | |
13617 | executable file itself for other parts. | |
13618 | ||
13619 | @code{core-file} with no argument specifies that no core file is | |
13620 | to be used. | |
13621 | ||
13622 | Note that the core file is ignored when your program is actually running | |
7a292a7a SS |
13623 | under @value{GDBN}. So, if you have been running your program and you |
13624 | wish to debug a core file instead, you must kill the subprocess in which | |
13625 | the program is running. To do this, use the @code{kill} command | |
79a6e687 | 13626 | (@pxref{Kill Process, ,Killing the Child Process}). |
c906108c | 13627 | |
c906108c SS |
13628 | @kindex add-symbol-file |
13629 | @cindex dynamic linking | |
13630 | @item add-symbol-file @var{filename} @var{address} | |
a94ab193 | 13631 | @itemx add-symbol-file @var{filename} @var{address} @r{[} -readnow @r{]} |
17d9d558 | 13632 | @itemx add-symbol-file @var{filename} @r{-s}@var{section} @var{address} @dots{} |
96a2c332 SS |
13633 | The @code{add-symbol-file} command reads additional symbol table |
13634 | information from the file @var{filename}. You would use this command | |
13635 | when @var{filename} has been dynamically loaded (by some other means) | |
13636 | into the program that is running. @var{address} should be the memory | |
13637 | address at which the file has been loaded; @value{GDBN} cannot figure | |
d167840f EZ |
13638 | this out for itself. You can additionally specify an arbitrary number |
13639 | of @samp{@r{-s}@var{section} @var{address}} pairs, to give an explicit | |
13640 | section name and base address for that section. You can specify any | |
13641 | @var{address} as an expression. | |
c906108c SS |
13642 | |
13643 | The symbol table of the file @var{filename} is added to the symbol table | |
13644 | originally read with the @code{symbol-file} command. You can use the | |
96a2c332 SS |
13645 | @code{add-symbol-file} command any number of times; the new symbol data |
13646 | thus read keeps adding to the old. To discard all old symbol data | |
13647 | instead, use the @code{symbol-file} command without any arguments. | |
c906108c | 13648 | |
17d9d558 JB |
13649 | @cindex relocatable object files, reading symbols from |
13650 | @cindex object files, relocatable, reading symbols from | |
13651 | @cindex reading symbols from relocatable object files | |
13652 | @cindex symbols, reading from relocatable object files | |
13653 | @cindex @file{.o} files, reading symbols from | |
13654 | Although @var{filename} is typically a shared library file, an | |
13655 | executable file, or some other object file which has been fully | |
13656 | relocated for loading into a process, you can also load symbolic | |
13657 | information from relocatable @file{.o} files, as long as: | |
13658 | ||
13659 | @itemize @bullet | |
13660 | @item | |
13661 | the file's symbolic information refers only to linker symbols defined in | |
13662 | that file, not to symbols defined by other object files, | |
13663 | @item | |
13664 | every section the file's symbolic information refers to has actually | |
13665 | been loaded into the inferior, as it appears in the file, and | |
13666 | @item | |
13667 | you can determine the address at which every section was loaded, and | |
13668 | provide these to the @code{add-symbol-file} command. | |
13669 | @end itemize | |
13670 | ||
13671 | @noindent | |
13672 | Some embedded operating systems, like Sun Chorus and VxWorks, can load | |
13673 | relocatable files into an already running program; such systems | |
13674 | typically make the requirements above easy to meet. However, it's | |
13675 | important to recognize that many native systems use complex link | |
49efadf5 | 13676 | procedures (@code{.linkonce} section factoring and C@t{++} constructor table |
17d9d558 JB |
13677 | assembly, for example) that make the requirements difficult to meet. In |
13678 | general, one cannot assume that using @code{add-symbol-file} to read a | |
13679 | relocatable object file's symbolic information will have the same effect | |
13680 | as linking the relocatable object file into the program in the normal | |
13681 | way. | |
13682 | ||
c906108c SS |
13683 | @code{add-symbol-file} does not repeat if you press @key{RET} after using it. |
13684 | ||
c45da7e6 EZ |
13685 | @kindex add-symbol-file-from-memory |
13686 | @cindex @code{syscall DSO} | |
13687 | @cindex load symbols from memory | |
13688 | @item add-symbol-file-from-memory @var{address} | |
13689 | Load symbols from the given @var{address} in a dynamically loaded | |
13690 | object file whose image is mapped directly into the inferior's memory. | |
13691 | For example, the Linux kernel maps a @code{syscall DSO} into each | |
13692 | process's address space; this DSO provides kernel-specific code for | |
13693 | some system calls. The argument can be any expression whose | |
13694 | evaluation yields the address of the file's shared object file header. | |
13695 | For this command to work, you must have used @code{symbol-file} or | |
13696 | @code{exec-file} commands in advance. | |
13697 | ||
09d4efe1 EZ |
13698 | @kindex add-shared-symbol-files |
13699 | @kindex assf | |
13700 | @item add-shared-symbol-files @var{library-file} | |
13701 | @itemx assf @var{library-file} | |
13702 | The @code{add-shared-symbol-files} command can currently be used only | |
13703 | in the Cygwin build of @value{GDBN} on MS-Windows OS, where it is an | |
13704 | alias for the @code{dll-symbols} command (@pxref{Cygwin Native}). | |
13705 | @value{GDBN} automatically looks for shared libraries, however if | |
13706 | @value{GDBN} does not find yours, you can invoke | |
13707 | @code{add-shared-symbol-files}. It takes one argument: the shared | |
13708 | library's file name. @code{assf} is a shorthand alias for | |
13709 | @code{add-shared-symbol-files}. | |
c906108c | 13710 | |
c906108c | 13711 | @kindex section |
09d4efe1 EZ |
13712 | @item section @var{section} @var{addr} |
13713 | The @code{section} command changes the base address of the named | |
13714 | @var{section} of the exec file to @var{addr}. This can be used if the | |
13715 | exec file does not contain section addresses, (such as in the | |
13716 | @code{a.out} format), or when the addresses specified in the file | |
13717 | itself are wrong. Each section must be changed separately. The | |
13718 | @code{info files} command, described below, lists all the sections and | |
13719 | their addresses. | |
c906108c SS |
13720 | |
13721 | @kindex info files | |
13722 | @kindex info target | |
13723 | @item info files | |
13724 | @itemx info target | |
7a292a7a SS |
13725 | @code{info files} and @code{info target} are synonymous; both print the |
13726 | current target (@pxref{Targets, ,Specifying a Debugging Target}), | |
13727 | including the names of the executable and core dump files currently in | |
13728 | use by @value{GDBN}, and the files from which symbols were loaded. The | |
13729 | command @code{help target} lists all possible targets rather than | |
13730 | current ones. | |
13731 | ||
fe95c787 MS |
13732 | @kindex maint info sections |
13733 | @item maint info sections | |
13734 | Another command that can give you extra information about program sections | |
13735 | is @code{maint info sections}. In addition to the section information | |
13736 | displayed by @code{info files}, this command displays the flags and file | |
13737 | offset of each section in the executable and core dump files. In addition, | |
13738 | @code{maint info sections} provides the following command options (which | |
13739 | may be arbitrarily combined): | |
13740 | ||
13741 | @table @code | |
13742 | @item ALLOBJ | |
13743 | Display sections for all loaded object files, including shared libraries. | |
13744 | @item @var{sections} | |
6600abed | 13745 | Display info only for named @var{sections}. |
fe95c787 MS |
13746 | @item @var{section-flags} |
13747 | Display info only for sections for which @var{section-flags} are true. | |
13748 | The section flags that @value{GDBN} currently knows about are: | |
13749 | @table @code | |
13750 | @item ALLOC | |
13751 | Section will have space allocated in the process when loaded. | |
13752 | Set for all sections except those containing debug information. | |
13753 | @item LOAD | |
13754 | Section will be loaded from the file into the child process memory. | |
13755 | Set for pre-initialized code and data, clear for @code{.bss} sections. | |
13756 | @item RELOC | |
13757 | Section needs to be relocated before loading. | |
13758 | @item READONLY | |
13759 | Section cannot be modified by the child process. | |
13760 | @item CODE | |
13761 | Section contains executable code only. | |
6600abed | 13762 | @item DATA |
fe95c787 MS |
13763 | Section contains data only (no executable code). |
13764 | @item ROM | |
13765 | Section will reside in ROM. | |
13766 | @item CONSTRUCTOR | |
13767 | Section contains data for constructor/destructor lists. | |
13768 | @item HAS_CONTENTS | |
13769 | Section is not empty. | |
13770 | @item NEVER_LOAD | |
13771 | An instruction to the linker to not output the section. | |
13772 | @item COFF_SHARED_LIBRARY | |
13773 | A notification to the linker that the section contains | |
13774 | COFF shared library information. | |
13775 | @item IS_COMMON | |
13776 | Section contains common symbols. | |
13777 | @end table | |
13778 | @end table | |
6763aef9 | 13779 | @kindex set trust-readonly-sections |
9c16f35a | 13780 | @cindex read-only sections |
6763aef9 MS |
13781 | @item set trust-readonly-sections on |
13782 | Tell @value{GDBN} that readonly sections in your object file | |
6ca652b0 | 13783 | really are read-only (i.e.@: that their contents will not change). |
6763aef9 MS |
13784 | In that case, @value{GDBN} can fetch values from these sections |
13785 | out of the object file, rather than from the target program. | |
13786 | For some targets (notably embedded ones), this can be a significant | |
13787 | enhancement to debugging performance. | |
13788 | ||
13789 | The default is off. | |
13790 | ||
13791 | @item set trust-readonly-sections off | |
15110bc3 | 13792 | Tell @value{GDBN} not to trust readonly sections. This means that |
6763aef9 MS |
13793 | the contents of the section might change while the program is running, |
13794 | and must therefore be fetched from the target when needed. | |
9c16f35a EZ |
13795 | |
13796 | @item show trust-readonly-sections | |
13797 | Show the current setting of trusting readonly sections. | |
c906108c SS |
13798 | @end table |
13799 | ||
13800 | All file-specifying commands allow both absolute and relative file names | |
13801 | as arguments. @value{GDBN} always converts the file name to an absolute file | |
13802 | name and remembers it that way. | |
13803 | ||
c906108c | 13804 | @cindex shared libraries |
9cceb671 DJ |
13805 | @anchor{Shared Libraries} |
13806 | @value{GDBN} supports @sc{gnu}/Linux, MS-Windows, HP-UX, SunOS, SVr4, Irix, | |
9c16f35a | 13807 | and IBM RS/6000 AIX shared libraries. |
53a5351d | 13808 | |
9cceb671 DJ |
13809 | On MS-Windows @value{GDBN} must be linked with the Expat library to support |
13810 | shared libraries. @xref{Expat}. | |
13811 | ||
c906108c SS |
13812 | @value{GDBN} automatically loads symbol definitions from shared libraries |
13813 | when you use the @code{run} command, or when you examine a core file. | |
13814 | (Before you issue the @code{run} command, @value{GDBN} does not understand | |
13815 | references to a function in a shared library, however---unless you are | |
13816 | debugging a core file). | |
53a5351d JM |
13817 | |
13818 | On HP-UX, if the program loads a library explicitly, @value{GDBN} | |
13819 | automatically loads the symbols at the time of the @code{shl_load} call. | |
13820 | ||
c906108c SS |
13821 | @c FIXME: some @value{GDBN} release may permit some refs to undef |
13822 | @c FIXME...symbols---eg in a break cmd---assuming they are from a shared | |
13823 | @c FIXME...lib; check this from time to time when updating manual | |
13824 | ||
b7209cb4 FF |
13825 | There are times, however, when you may wish to not automatically load |
13826 | symbol definitions from shared libraries, such as when they are | |
13827 | particularly large or there are many of them. | |
13828 | ||
13829 | To control the automatic loading of shared library symbols, use the | |
13830 | commands: | |
13831 | ||
13832 | @table @code | |
13833 | @kindex set auto-solib-add | |
13834 | @item set auto-solib-add @var{mode} | |
13835 | If @var{mode} is @code{on}, symbols from all shared object libraries | |
13836 | will be loaded automatically when the inferior begins execution, you | |
13837 | attach to an independently started inferior, or when the dynamic linker | |
13838 | informs @value{GDBN} that a new library has been loaded. If @var{mode} | |
13839 | is @code{off}, symbols must be loaded manually, using the | |
13840 | @code{sharedlibrary} command. The default value is @code{on}. | |
13841 | ||
dcaf7c2c EZ |
13842 | @cindex memory used for symbol tables |
13843 | If your program uses lots of shared libraries with debug info that | |
13844 | takes large amounts of memory, you can decrease the @value{GDBN} | |
13845 | memory footprint by preventing it from automatically loading the | |
13846 | symbols from shared libraries. To that end, type @kbd{set | |
13847 | auto-solib-add off} before running the inferior, then load each | |
13848 | library whose debug symbols you do need with @kbd{sharedlibrary | |
d3e8051b | 13849 | @var{regexp}}, where @var{regexp} is a regular expression that matches |
dcaf7c2c EZ |
13850 | the libraries whose symbols you want to be loaded. |
13851 | ||
b7209cb4 FF |
13852 | @kindex show auto-solib-add |
13853 | @item show auto-solib-add | |
13854 | Display the current autoloading mode. | |
13855 | @end table | |
13856 | ||
c45da7e6 | 13857 | @cindex load shared library |
b7209cb4 FF |
13858 | To explicitly load shared library symbols, use the @code{sharedlibrary} |
13859 | command: | |
13860 | ||
c906108c SS |
13861 | @table @code |
13862 | @kindex info sharedlibrary | |
13863 | @kindex info share | |
55333a84 DE |
13864 | @item info share @var{regex} |
13865 | @itemx info sharedlibrary @var{regex} | |
13866 | Print the names of the shared libraries which are currently loaded | |
13867 | that match @var{regex}. If @var{regex} is omitted then print | |
13868 | all shared libraries that are loaded. | |
c906108c SS |
13869 | |
13870 | @kindex sharedlibrary | |
13871 | @kindex share | |
13872 | @item sharedlibrary @var{regex} | |
13873 | @itemx share @var{regex} | |
c906108c SS |
13874 | Load shared object library symbols for files matching a |
13875 | Unix regular expression. | |
13876 | As with files loaded automatically, it only loads shared libraries | |
13877 | required by your program for a core file or after typing @code{run}. If | |
13878 | @var{regex} is omitted all shared libraries required by your program are | |
13879 | loaded. | |
c45da7e6 EZ |
13880 | |
13881 | @item nosharedlibrary | |
13882 | @kindex nosharedlibrary | |
13883 | @cindex unload symbols from shared libraries | |
13884 | Unload all shared object library symbols. This discards all symbols | |
13885 | that have been loaded from all shared libraries. Symbols from shared | |
13886 | libraries that were loaded by explicit user requests are not | |
13887 | discarded. | |
c906108c SS |
13888 | @end table |
13889 | ||
721c2651 EZ |
13890 | Sometimes you may wish that @value{GDBN} stops and gives you control |
13891 | when any of shared library events happen. Use the @code{set | |
13892 | stop-on-solib-events} command for this: | |
13893 | ||
13894 | @table @code | |
13895 | @item set stop-on-solib-events | |
13896 | @kindex set stop-on-solib-events | |
13897 | This command controls whether @value{GDBN} should give you control | |
13898 | when the dynamic linker notifies it about some shared library event. | |
13899 | The most common event of interest is loading or unloading of a new | |
13900 | shared library. | |
13901 | ||
13902 | @item show stop-on-solib-events | |
13903 | @kindex show stop-on-solib-events | |
13904 | Show whether @value{GDBN} stops and gives you control when shared | |
13905 | library events happen. | |
13906 | @end table | |
13907 | ||
f5ebfba0 | 13908 | Shared libraries are also supported in many cross or remote debugging |
f1838a98 UW |
13909 | configurations. @value{GDBN} needs to have access to the target's libraries; |
13910 | this can be accomplished either by providing copies of the libraries | |
13911 | on the host system, or by asking @value{GDBN} to automatically retrieve the | |
13912 | libraries from the target. If copies of the target libraries are | |
13913 | provided, they need to be the same as the target libraries, although the | |
f5ebfba0 DJ |
13914 | copies on the target can be stripped as long as the copies on the host are |
13915 | not. | |
13916 | ||
59b7b46f EZ |
13917 | @cindex where to look for shared libraries |
13918 | For remote debugging, you need to tell @value{GDBN} where the target | |
13919 | libraries are, so that it can load the correct copies---otherwise, it | |
13920 | may try to load the host's libraries. @value{GDBN} has two variables | |
13921 | to specify the search directories for target libraries. | |
f5ebfba0 DJ |
13922 | |
13923 | @table @code | |
59b7b46f | 13924 | @cindex prefix for shared library file names |
f822c95b | 13925 | @cindex system root, alternate |
f5ebfba0 | 13926 | @kindex set solib-absolute-prefix |
f822c95b DJ |
13927 | @kindex set sysroot |
13928 | @item set sysroot @var{path} | |
13929 | Use @var{path} as the system root for the program being debugged. Any | |
13930 | absolute shared library paths will be prefixed with @var{path}; many | |
13931 | runtime loaders store the absolute paths to the shared library in the | |
13932 | target program's memory. If you use @code{set sysroot} to find shared | |
13933 | libraries, they need to be laid out in the same way that they are on | |
13934 | the target, with e.g.@: a @file{/lib} and @file{/usr/lib} hierarchy | |
13935 | under @var{path}. | |
13936 | ||
f1838a98 UW |
13937 | If @var{path} starts with the sequence @file{remote:}, @value{GDBN} will |
13938 | retrieve the target libraries from the remote system. This is only | |
13939 | supported when using a remote target that supports the @code{remote get} | |
13940 | command (@pxref{File Transfer,,Sending files to a remote system}). | |
13941 | The part of @var{path} following the initial @file{remote:} | |
13942 | (if present) is used as system root prefix on the remote file system. | |
13943 | @footnote{If you want to specify a local system root using a directory | |
13944 | that happens to be named @file{remote:}, you need to use some equivalent | |
13945 | variant of the name like @file{./remote:}.} | |
13946 | ||
f822c95b DJ |
13947 | The @code{set solib-absolute-prefix} command is an alias for @code{set |
13948 | sysroot}. | |
13949 | ||
13950 | @cindex default system root | |
59b7b46f | 13951 | @cindex @samp{--with-sysroot} |
f822c95b DJ |
13952 | You can set the default system root by using the configure-time |
13953 | @samp{--with-sysroot} option. If the system root is inside | |
13954 | @value{GDBN}'s configured binary prefix (set with @samp{--prefix} or | |
13955 | @samp{--exec-prefix}), then the default system root will be updated | |
13956 | automatically if the installed @value{GDBN} is moved to a new | |
13957 | location. | |
13958 | ||
13959 | @kindex show sysroot | |
13960 | @item show sysroot | |
f5ebfba0 DJ |
13961 | Display the current shared library prefix. |
13962 | ||
13963 | @kindex set solib-search-path | |
13964 | @item set solib-search-path @var{path} | |
f822c95b DJ |
13965 | If this variable is set, @var{path} is a colon-separated list of |
13966 | directories to search for shared libraries. @samp{solib-search-path} | |
13967 | is used after @samp{sysroot} fails to locate the library, or if the | |
13968 | path to the library is relative instead of absolute. If you want to | |
13969 | use @samp{solib-search-path} instead of @samp{sysroot}, be sure to set | |
d3e8051b | 13970 | @samp{sysroot} to a nonexistent directory to prevent @value{GDBN} from |
f822c95b | 13971 | finding your host's libraries. @samp{sysroot} is preferred; setting |
d3e8051b | 13972 | it to a nonexistent directory may interfere with automatic loading |
f822c95b | 13973 | of shared library symbols. |
f5ebfba0 DJ |
13974 | |
13975 | @kindex show solib-search-path | |
13976 | @item show solib-search-path | |
13977 | Display the current shared library search path. | |
13978 | @end table | |
13979 | ||
5b5d99cf JB |
13980 | |
13981 | @node Separate Debug Files | |
13982 | @section Debugging Information in Separate Files | |
13983 | @cindex separate debugging information files | |
13984 | @cindex debugging information in separate files | |
13985 | @cindex @file{.debug} subdirectories | |
13986 | @cindex debugging information directory, global | |
13987 | @cindex global debugging information directory | |
c7e83d54 EZ |
13988 | @cindex build ID, and separate debugging files |
13989 | @cindex @file{.build-id} directory | |
5b5d99cf JB |
13990 | |
13991 | @value{GDBN} allows you to put a program's debugging information in a | |
13992 | file separate from the executable itself, in a way that allows | |
13993 | @value{GDBN} to find and load the debugging information automatically. | |
c7e83d54 EZ |
13994 | Since debugging information can be very large---sometimes larger |
13995 | than the executable code itself---some systems distribute debugging | |
5b5d99cf JB |
13996 | information for their executables in separate files, which users can |
13997 | install only when they need to debug a problem. | |
13998 | ||
c7e83d54 EZ |
13999 | @value{GDBN} supports two ways of specifying the separate debug info |
14000 | file: | |
5b5d99cf JB |
14001 | |
14002 | @itemize @bullet | |
14003 | @item | |
c7e83d54 EZ |
14004 | The executable contains a @dfn{debug link} that specifies the name of |
14005 | the separate debug info file. The separate debug file's name is | |
14006 | usually @file{@var{executable}.debug}, where @var{executable} is the | |
14007 | name of the corresponding executable file without leading directories | |
14008 | (e.g., @file{ls.debug} for @file{/usr/bin/ls}). In addition, the | |
99e008fe EZ |
14009 | debug link specifies a 32-bit @dfn{Cyclic Redundancy Check} (CRC) |
14010 | checksum for the debug file, which @value{GDBN} uses to validate that | |
14011 | the executable and the debug file came from the same build. | |
c7e83d54 EZ |
14012 | |
14013 | @item | |
7e27a47a | 14014 | The executable contains a @dfn{build ID}, a unique bit string that is |
c7e83d54 | 14015 | also present in the corresponding debug info file. (This is supported |
7e27a47a EZ |
14016 | only on some operating systems, notably those which use the ELF format |
14017 | for binary files and the @sc{gnu} Binutils.) For more details about | |
14018 | this feature, see the description of the @option{--build-id} | |
14019 | command-line option in @ref{Options, , Command Line Options, ld.info, | |
14020 | The GNU Linker}. The debug info file's name is not specified | |
14021 | explicitly by the build ID, but can be computed from the build ID, see | |
14022 | below. | |
d3750b24 JK |
14023 | @end itemize |
14024 | ||
c7e83d54 EZ |
14025 | Depending on the way the debug info file is specified, @value{GDBN} |
14026 | uses two different methods of looking for the debug file: | |
d3750b24 JK |
14027 | |
14028 | @itemize @bullet | |
14029 | @item | |
c7e83d54 EZ |
14030 | For the ``debug link'' method, @value{GDBN} looks up the named file in |
14031 | the directory of the executable file, then in a subdirectory of that | |
14032 | directory named @file{.debug}, and finally under the global debug | |
14033 | directory, in a subdirectory whose name is identical to the leading | |
14034 | directories of the executable's absolute file name. | |
14035 | ||
14036 | @item | |
83f83d7f | 14037 | For the ``build ID'' method, @value{GDBN} looks in the |
c7e83d54 EZ |
14038 | @file{.build-id} subdirectory of the global debug directory for a file |
14039 | named @file{@var{nn}/@var{nnnnnnnn}.debug}, where @var{nn} are the | |
7e27a47a EZ |
14040 | first 2 hex characters of the build ID bit string, and @var{nnnnnnnn} |
14041 | are the rest of the bit string. (Real build ID strings are 32 or more | |
14042 | hex characters, not 10.) | |
c7e83d54 EZ |
14043 | @end itemize |
14044 | ||
14045 | So, for example, suppose you ask @value{GDBN} to debug | |
7e27a47a EZ |
14046 | @file{/usr/bin/ls}, which has a debug link that specifies the |
14047 | file @file{ls.debug}, and a build ID whose value in hex is | |
c7e83d54 EZ |
14048 | @code{abcdef1234}. If the global debug directory is |
14049 | @file{/usr/lib/debug}, then @value{GDBN} will look for the following | |
14050 | debug information files, in the indicated order: | |
14051 | ||
14052 | @itemize @minus | |
14053 | @item | |
14054 | @file{/usr/lib/debug/.build-id/ab/cdef1234.debug} | |
d3750b24 | 14055 | @item |
c7e83d54 | 14056 | @file{/usr/bin/ls.debug} |
5b5d99cf | 14057 | @item |
c7e83d54 | 14058 | @file{/usr/bin/.debug/ls.debug} |
5b5d99cf | 14059 | @item |
c7e83d54 | 14060 | @file{/usr/lib/debug/usr/bin/ls.debug}. |
5b5d99cf | 14061 | @end itemize |
5b5d99cf JB |
14062 | |
14063 | You can set the global debugging info directory's name, and view the | |
14064 | name @value{GDBN} is currently using. | |
14065 | ||
14066 | @table @code | |
14067 | ||
14068 | @kindex set debug-file-directory | |
14069 | @item set debug-file-directory @var{directory} | |
14070 | Set the directory which @value{GDBN} searches for separate debugging | |
14071 | information files to @var{directory}. | |
14072 | ||
14073 | @kindex show debug-file-directory | |
14074 | @item show debug-file-directory | |
14075 | Show the directory @value{GDBN} searches for separate debugging | |
14076 | information files. | |
14077 | ||
14078 | @end table | |
14079 | ||
14080 | @cindex @code{.gnu_debuglink} sections | |
c7e83d54 | 14081 | @cindex debug link sections |
5b5d99cf JB |
14082 | A debug link is a special section of the executable file named |
14083 | @code{.gnu_debuglink}. The section must contain: | |
14084 | ||
14085 | @itemize | |
14086 | @item | |
14087 | A filename, with any leading directory components removed, followed by | |
14088 | a zero byte, | |
14089 | @item | |
14090 | zero to three bytes of padding, as needed to reach the next four-byte | |
14091 | boundary within the section, and | |
14092 | @item | |
14093 | a four-byte CRC checksum, stored in the same endianness used for the | |
14094 | executable file itself. The checksum is computed on the debugging | |
14095 | information file's full contents by the function given below, passing | |
14096 | zero as the @var{crc} argument. | |
14097 | @end itemize | |
14098 | ||
14099 | Any executable file format can carry a debug link, as long as it can | |
14100 | contain a section named @code{.gnu_debuglink} with the contents | |
14101 | described above. | |
14102 | ||
d3750b24 | 14103 | @cindex @code{.note.gnu.build-id} sections |
c7e83d54 | 14104 | @cindex build ID sections |
7e27a47a EZ |
14105 | The build ID is a special section in the executable file (and in other |
14106 | ELF binary files that @value{GDBN} may consider). This section is | |
14107 | often named @code{.note.gnu.build-id}, but that name is not mandatory. | |
14108 | It contains unique identification for the built files---the ID remains | |
14109 | the same across multiple builds of the same build tree. The default | |
14110 | algorithm SHA1 produces 160 bits (40 hexadecimal characters) of the | |
14111 | content for the build ID string. The same section with an identical | |
14112 | value is present in the original built binary with symbols, in its | |
14113 | stripped variant, and in the separate debugging information file. | |
d3750b24 | 14114 | |
5b5d99cf JB |
14115 | The debugging information file itself should be an ordinary |
14116 | executable, containing a full set of linker symbols, sections, and | |
14117 | debugging information. The sections of the debugging information file | |
c7e83d54 EZ |
14118 | should have the same names, addresses, and sizes as the original file, |
14119 | but they need not contain any data---much like a @code{.bss} section | |
5b5d99cf JB |
14120 | in an ordinary executable. |
14121 | ||
7e27a47a | 14122 | The @sc{gnu} binary utilities (Binutils) package includes the |
c7e83d54 EZ |
14123 | @samp{objcopy} utility that can produce |
14124 | the separated executable / debugging information file pairs using the | |
14125 | following commands: | |
14126 | ||
14127 | @smallexample | |
14128 | @kbd{objcopy --only-keep-debug foo foo.debug} | |
14129 | @kbd{strip -g foo} | |
c7e83d54 EZ |
14130 | @end smallexample |
14131 | ||
14132 | @noindent | |
14133 | These commands remove the debugging | |
83f83d7f JK |
14134 | information from the executable file @file{foo} and place it in the file |
14135 | @file{foo.debug}. You can use the first, second or both methods to link the | |
14136 | two files: | |
14137 | ||
14138 | @itemize @bullet | |
14139 | @item | |
14140 | The debug link method needs the following additional command to also leave | |
14141 | behind a debug link in @file{foo}: | |
14142 | ||
14143 | @smallexample | |
14144 | @kbd{objcopy --add-gnu-debuglink=foo.debug foo} | |
14145 | @end smallexample | |
14146 | ||
14147 | Ulrich Drepper's @file{elfutils} package, starting with version 0.53, contains | |
d3750b24 | 14148 | a version of the @code{strip} command such that the command @kbd{strip foo -f |
83f83d7f JK |
14149 | foo.debug} has the same functionality as the two @code{objcopy} commands and |
14150 | the @code{ln -s} command above, together. | |
14151 | ||
14152 | @item | |
14153 | Build ID gets embedded into the main executable using @code{ld --build-id} or | |
14154 | the @value{NGCC} counterpart @code{gcc -Wl,--build-id}. Build ID support plus | |
14155 | compatibility fixes for debug files separation are present in @sc{gnu} binary | |
7e27a47a | 14156 | utilities (Binutils) package since version 2.18. |
83f83d7f JK |
14157 | @end itemize |
14158 | ||
14159 | @noindent | |
d3750b24 | 14160 | |
99e008fe EZ |
14161 | @cindex CRC algorithm definition |
14162 | The CRC used in @code{.gnu_debuglink} is the CRC-32 defined in | |
14163 | IEEE 802.3 using the polynomial: | |
14164 | ||
14165 | @c TexInfo requires naked braces for multi-digit exponents for Tex | |
14166 | @c output, but this causes HTML output to barf. HTML has to be set using | |
14167 | @c raw commands. So we end up having to specify this equation in 2 | |
14168 | @c different ways! | |
14169 | @ifhtml | |
14170 | @display | |
14171 | @html | |
14172 | <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> | |
14173 | + <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 | |
14174 | @end html | |
14175 | @end display | |
14176 | @end ifhtml | |
14177 | @ifnothtml | |
14178 | @display | |
14179 | @math{x^{32} + x^{26} + x^{23} + x^{22} + x^{16} + x^{12} + x^{11}} | |
14180 | @math{+ x^{10} + x^8 + x^7 + x^5 + x^4 + x^2 + x + 1} | |
14181 | @end display | |
14182 | @end ifnothtml | |
14183 | ||
14184 | The function is computed byte at a time, taking the least | |
14185 | significant bit of each byte first. The initial pattern | |
14186 | @code{0xffffffff} is used, to ensure leading zeros affect the CRC and | |
14187 | the final result is inverted to ensure trailing zeros also affect the | |
14188 | CRC. | |
14189 | ||
14190 | @emph{Note:} This is the same CRC polynomial as used in handling the | |
14191 | @dfn{Remote Serial Protocol} @code{qCRC} packet (@pxref{Remote Protocol, | |
14192 | , @value{GDBN} Remote Serial Protocol}). However in the | |
14193 | case of the Remote Serial Protocol, the CRC is computed @emph{most} | |
14194 | significant bit first, and the result is not inverted, so trailing | |
14195 | zeros have no effect on the CRC value. | |
14196 | ||
14197 | To complete the description, we show below the code of the function | |
14198 | which produces the CRC used in @code{.gnu_debuglink}. Inverting the | |
14199 | initially supplied @code{crc} argument means that an initial call to | |
14200 | this function passing in zero will start computing the CRC using | |
14201 | @code{0xffffffff}. | |
5b5d99cf | 14202 | |
4644b6e3 | 14203 | @kindex gnu_debuglink_crc32 |
5b5d99cf JB |
14204 | @smallexample |
14205 | unsigned long | |
14206 | gnu_debuglink_crc32 (unsigned long crc, | |
14207 | unsigned char *buf, size_t len) | |
14208 | @{ | |
14209 | static const unsigned long crc32_table[256] = | |
14210 | @{ | |
14211 | 0x00000000, 0x77073096, 0xee0e612c, 0x990951ba, 0x076dc419, | |
14212 | 0x706af48f, 0xe963a535, 0x9e6495a3, 0x0edb8832, 0x79dcb8a4, | |
14213 | 0xe0d5e91e, 0x97d2d988, 0x09b64c2b, 0x7eb17cbd, 0xe7b82d07, | |
14214 | 0x90bf1d91, 0x1db71064, 0x6ab020f2, 0xf3b97148, 0x84be41de, | |
14215 | 0x1adad47d, 0x6ddde4eb, 0xf4d4b551, 0x83d385c7, 0x136c9856, | |
14216 | 0x646ba8c0, 0xfd62f97a, 0x8a65c9ec, 0x14015c4f, 0x63066cd9, | |
14217 | 0xfa0f3d63, 0x8d080df5, 0x3b6e20c8, 0x4c69105e, 0xd56041e4, | |
14218 | 0xa2677172, 0x3c03e4d1, 0x4b04d447, 0xd20d85fd, 0xa50ab56b, | |
14219 | 0x35b5a8fa, 0x42b2986c, 0xdbbbc9d6, 0xacbcf940, 0x32d86ce3, | |
14220 | 0x45df5c75, 0xdcd60dcf, 0xabd13d59, 0x26d930ac, 0x51de003a, | |
14221 | 0xc8d75180, 0xbfd06116, 0x21b4f4b5, 0x56b3c423, 0xcfba9599, | |
14222 | 0xb8bda50f, 0x2802b89e, 0x5f058808, 0xc60cd9b2, 0xb10be924, | |
14223 | 0x2f6f7c87, 0x58684c11, 0xc1611dab, 0xb6662d3d, 0x76dc4190, | |
14224 | 0x01db7106, 0x98d220bc, 0xefd5102a, 0x71b18589, 0x06b6b51f, | |
14225 | 0x9fbfe4a5, 0xe8b8d433, 0x7807c9a2, 0x0f00f934, 0x9609a88e, | |
14226 | 0xe10e9818, 0x7f6a0dbb, 0x086d3d2d, 0x91646c97, 0xe6635c01, | |
14227 | 0x6b6b51f4, 0x1c6c6162, 0x856530d8, 0xf262004e, 0x6c0695ed, | |
14228 | 0x1b01a57b, 0x8208f4c1, 0xf50fc457, 0x65b0d9c6, 0x12b7e950, | |
14229 | 0x8bbeb8ea, 0xfcb9887c, 0x62dd1ddf, 0x15da2d49, 0x8cd37cf3, | |
14230 | 0xfbd44c65, 0x4db26158, 0x3ab551ce, 0xa3bc0074, 0xd4bb30e2, | |
14231 | 0x4adfa541, 0x3dd895d7, 0xa4d1c46d, 0xd3d6f4fb, 0x4369e96a, | |
14232 | 0x346ed9fc, 0xad678846, 0xda60b8d0, 0x44042d73, 0x33031de5, | |
14233 | 0xaa0a4c5f, 0xdd0d7cc9, 0x5005713c, 0x270241aa, 0xbe0b1010, | |
14234 | 0xc90c2086, 0x5768b525, 0x206f85b3, 0xb966d409, 0xce61e49f, | |
14235 | 0x5edef90e, 0x29d9c998, 0xb0d09822, 0xc7d7a8b4, 0x59b33d17, | |
14236 | 0x2eb40d81, 0xb7bd5c3b, 0xc0ba6cad, 0xedb88320, 0x9abfb3b6, | |
14237 | 0x03b6e20c, 0x74b1d29a, 0xead54739, 0x9dd277af, 0x04db2615, | |
14238 | 0x73dc1683, 0xe3630b12, 0x94643b84, 0x0d6d6a3e, 0x7a6a5aa8, | |
14239 | 0xe40ecf0b, 0x9309ff9d, 0x0a00ae27, 0x7d079eb1, 0xf00f9344, | |
14240 | 0x8708a3d2, 0x1e01f268, 0x6906c2fe, 0xf762575d, 0x806567cb, | |
14241 | 0x196c3671, 0x6e6b06e7, 0xfed41b76, 0x89d32be0, 0x10da7a5a, | |
14242 | 0x67dd4acc, 0xf9b9df6f, 0x8ebeeff9, 0x17b7be43, 0x60b08ed5, | |
14243 | 0xd6d6a3e8, 0xa1d1937e, 0x38d8c2c4, 0x4fdff252, 0xd1bb67f1, | |
14244 | 0xa6bc5767, 0x3fb506dd, 0x48b2364b, 0xd80d2bda, 0xaf0a1b4c, | |
14245 | 0x36034af6, 0x41047a60, 0xdf60efc3, 0xa867df55, 0x316e8eef, | |
14246 | 0x4669be79, 0xcb61b38c, 0xbc66831a, 0x256fd2a0, 0x5268e236, | |
14247 | 0xcc0c7795, 0xbb0b4703, 0x220216b9, 0x5505262f, 0xc5ba3bbe, | |
14248 | 0xb2bd0b28, 0x2bb45a92, 0x5cb36a04, 0xc2d7ffa7, 0xb5d0cf31, | |
14249 | 0x2cd99e8b, 0x5bdeae1d, 0x9b64c2b0, 0xec63f226, 0x756aa39c, | |
14250 | 0x026d930a, 0x9c0906a9, 0xeb0e363f, 0x72076785, 0x05005713, | |
14251 | 0x95bf4a82, 0xe2b87a14, 0x7bb12bae, 0x0cb61b38, 0x92d28e9b, | |
14252 | 0xe5d5be0d, 0x7cdcefb7, 0x0bdbdf21, 0x86d3d2d4, 0xf1d4e242, | |
14253 | 0x68ddb3f8, 0x1fda836e, 0x81be16cd, 0xf6b9265b, 0x6fb077e1, | |
14254 | 0x18b74777, 0x88085ae6, 0xff0f6a70, 0x66063bca, 0x11010b5c, | |
14255 | 0x8f659eff, 0xf862ae69, 0x616bffd3, 0x166ccf45, 0xa00ae278, | |
14256 | 0xd70dd2ee, 0x4e048354, 0x3903b3c2, 0xa7672661, 0xd06016f7, | |
14257 | 0x4969474d, 0x3e6e77db, 0xaed16a4a, 0xd9d65adc, 0x40df0b66, | |
14258 | 0x37d83bf0, 0xa9bcae53, 0xdebb9ec5, 0x47b2cf7f, 0x30b5ffe9, | |
14259 | 0xbdbdf21c, 0xcabac28a, 0x53b39330, 0x24b4a3a6, 0xbad03605, | |
14260 | 0xcdd70693, 0x54de5729, 0x23d967bf, 0xb3667a2e, 0xc4614ab8, | |
14261 | 0x5d681b02, 0x2a6f2b94, 0xb40bbe37, 0xc30c8ea1, 0x5a05df1b, | |
14262 | 0x2d02ef8d | |
14263 | @}; | |
14264 | unsigned char *end; | |
14265 | ||
14266 | crc = ~crc & 0xffffffff; | |
14267 | for (end = buf + len; buf < end; ++buf) | |
14268 | crc = crc32_table[(crc ^ *buf) & 0xff] ^ (crc >> 8); | |
e7a3abfc | 14269 | return ~crc & 0xffffffff; |
5b5d99cf JB |
14270 | @} |
14271 | @end smallexample | |
14272 | ||
c7e83d54 EZ |
14273 | @noindent |
14274 | This computation does not apply to the ``build ID'' method. | |
14275 | ||
5b5d99cf | 14276 | |
6d2ebf8b | 14277 | @node Symbol Errors |
79a6e687 | 14278 | @section Errors Reading Symbol Files |
c906108c SS |
14279 | |
14280 | While reading a symbol file, @value{GDBN} occasionally encounters problems, | |
14281 | such as symbol types it does not recognize, or known bugs in compiler | |
14282 | output. By default, @value{GDBN} does not notify you of such problems, since | |
14283 | they are relatively common and primarily of interest to people | |
14284 | debugging compilers. If you are interested in seeing information | |
14285 | about ill-constructed symbol tables, you can either ask @value{GDBN} to print | |
14286 | only one message about each such type of problem, no matter how many | |
14287 | times the problem occurs; or you can ask @value{GDBN} to print more messages, | |
14288 | to see how many times the problems occur, with the @code{set | |
79a6e687 BW |
14289 | complaints} command (@pxref{Messages/Warnings, ,Optional Warnings and |
14290 | Messages}). | |
c906108c SS |
14291 | |
14292 | The messages currently printed, and their meanings, include: | |
14293 | ||
14294 | @table @code | |
14295 | @item inner block not inside outer block in @var{symbol} | |
14296 | ||
14297 | The symbol information shows where symbol scopes begin and end | |
14298 | (such as at the start of a function or a block of statements). This | |
14299 | error indicates that an inner scope block is not fully contained | |
14300 | in its outer scope blocks. | |
14301 | ||
14302 | @value{GDBN} circumvents the problem by treating the inner block as if it had | |
14303 | the same scope as the outer block. In the error message, @var{symbol} | |
14304 | may be shown as ``@code{(don't know)}'' if the outer block is not a | |
14305 | function. | |
14306 | ||
14307 | @item block at @var{address} out of order | |
14308 | ||
14309 | The symbol information for symbol scope blocks should occur in | |
14310 | order of increasing addresses. This error indicates that it does not | |
14311 | do so. | |
14312 | ||
14313 | @value{GDBN} does not circumvent this problem, and has trouble | |
14314 | locating symbols in the source file whose symbols it is reading. (You | |
14315 | can often determine what source file is affected by specifying | |
79a6e687 BW |
14316 | @code{set verbose on}. @xref{Messages/Warnings, ,Optional Warnings and |
14317 | Messages}.) | |
c906108c SS |
14318 | |
14319 | @item bad block start address patched | |
14320 | ||
14321 | The symbol information for a symbol scope block has a start address | |
14322 | smaller than the address of the preceding source line. This is known | |
14323 | to occur in the SunOS 4.1.1 (and earlier) C compiler. | |
14324 | ||
14325 | @value{GDBN} circumvents the problem by treating the symbol scope block as | |
14326 | starting on the previous source line. | |
14327 | ||
14328 | @item bad string table offset in symbol @var{n} | |
14329 | ||
14330 | @cindex foo | |
14331 | Symbol number @var{n} contains a pointer into the string table which is | |
14332 | larger than the size of the string table. | |
14333 | ||
14334 | @value{GDBN} circumvents the problem by considering the symbol to have the | |
14335 | name @code{foo}, which may cause other problems if many symbols end up | |
14336 | with this name. | |
14337 | ||
14338 | @item unknown symbol type @code{0x@var{nn}} | |
14339 | ||
7a292a7a SS |
14340 | The symbol information contains new data types that @value{GDBN} does |
14341 | not yet know how to read. @code{0x@var{nn}} is the symbol type of the | |
d4f3574e | 14342 | uncomprehended information, in hexadecimal. |
c906108c | 14343 | |
7a292a7a SS |
14344 | @value{GDBN} circumvents the error by ignoring this symbol information. |
14345 | This usually allows you to debug your program, though certain symbols | |
c906108c | 14346 | are not accessible. If you encounter such a problem and feel like |
7a292a7a SS |
14347 | debugging it, you can debug @code{@value{GDBP}} with itself, breakpoint |
14348 | on @code{complain}, then go up to the function @code{read_dbx_symtab} | |
14349 | and examine @code{*bufp} to see the symbol. | |
c906108c SS |
14350 | |
14351 | @item stub type has NULL name | |
c906108c | 14352 | |
7a292a7a | 14353 | @value{GDBN} could not find the full definition for a struct or class. |
c906108c | 14354 | |
7a292a7a | 14355 | @item const/volatile indicator missing (ok if using g++ v1.x), got@dots{} |
b37052ae | 14356 | The symbol information for a C@t{++} member function is missing some |
7a292a7a SS |
14357 | information that recent versions of the compiler should have output for |
14358 | it. | |
c906108c SS |
14359 | |
14360 | @item info mismatch between compiler and debugger | |
14361 | ||
14362 | @value{GDBN} could not parse a type specification output by the compiler. | |
7a292a7a | 14363 | |
c906108c SS |
14364 | @end table |
14365 | ||
b14b1491 TT |
14366 | @node Data Files |
14367 | @section GDB Data Files | |
14368 | ||
14369 | @cindex prefix for data files | |
14370 | @value{GDBN} will sometimes read an auxiliary data file. These files | |
14371 | are kept in a directory known as the @dfn{data directory}. | |
14372 | ||
14373 | You can set the data directory's name, and view the name @value{GDBN} | |
14374 | is currently using. | |
14375 | ||
14376 | @table @code | |
14377 | @kindex set data-directory | |
14378 | @item set data-directory @var{directory} | |
14379 | Set the directory which @value{GDBN} searches for auxiliary data files | |
14380 | to @var{directory}. | |
14381 | ||
14382 | @kindex show data-directory | |
14383 | @item show data-directory | |
14384 | Show the directory @value{GDBN} searches for auxiliary data files. | |
14385 | @end table | |
14386 | ||
14387 | @cindex default data directory | |
14388 | @cindex @samp{--with-gdb-datadir} | |
14389 | You can set the default data directory by using the configure-time | |
14390 | @samp{--with-gdb-datadir} option. If the data directory is inside | |
14391 | @value{GDBN}'s configured binary prefix (set with @samp{--prefix} or | |
14392 | @samp{--exec-prefix}), then the default data directory will be updated | |
14393 | automatically if the installed @value{GDBN} is moved to a new | |
14394 | location. | |
14395 | ||
6d2ebf8b | 14396 | @node Targets |
c906108c | 14397 | @chapter Specifying a Debugging Target |
7a292a7a | 14398 | |
c906108c | 14399 | @cindex debugging target |
c906108c | 14400 | A @dfn{target} is the execution environment occupied by your program. |
53a5351d JM |
14401 | |
14402 | Often, @value{GDBN} runs in the same host environment as your program; | |
14403 | in that case, the debugging target is specified as a side effect when | |
14404 | you use the @code{file} or @code{core} commands. When you need more | |
c906108c SS |
14405 | flexibility---for example, running @value{GDBN} on a physically separate |
14406 | host, or controlling a standalone system over a serial port or a | |
53a5351d JM |
14407 | realtime system over a TCP/IP connection---you can use the @code{target} |
14408 | command to specify one of the target types configured for @value{GDBN} | |
79a6e687 | 14409 | (@pxref{Target Commands, ,Commands for Managing Targets}). |
c906108c | 14410 | |
a8f24a35 EZ |
14411 | @cindex target architecture |
14412 | It is possible to build @value{GDBN} for several different @dfn{target | |
14413 | architectures}. When @value{GDBN} is built like that, you can choose | |
14414 | one of the available architectures with the @kbd{set architecture} | |
14415 | command. | |
14416 | ||
14417 | @table @code | |
14418 | @kindex set architecture | |
14419 | @kindex show architecture | |
14420 | @item set architecture @var{arch} | |
14421 | This command sets the current target architecture to @var{arch}. The | |
14422 | value of @var{arch} can be @code{"auto"}, in addition to one of the | |
14423 | supported architectures. | |
14424 | ||
14425 | @item show architecture | |
14426 | Show the current target architecture. | |
9c16f35a EZ |
14427 | |
14428 | @item set processor | |
14429 | @itemx processor | |
14430 | @kindex set processor | |
14431 | @kindex show processor | |
14432 | These are alias commands for, respectively, @code{set architecture} | |
14433 | and @code{show architecture}. | |
a8f24a35 EZ |
14434 | @end table |
14435 | ||
c906108c SS |
14436 | @menu |
14437 | * Active Targets:: Active targets | |
14438 | * Target Commands:: Commands for managing targets | |
c906108c | 14439 | * Byte Order:: Choosing target byte order |
c906108c SS |
14440 | @end menu |
14441 | ||
6d2ebf8b | 14442 | @node Active Targets |
79a6e687 | 14443 | @section Active Targets |
7a292a7a | 14444 | |
c906108c SS |
14445 | @cindex stacking targets |
14446 | @cindex active targets | |
14447 | @cindex multiple targets | |
14448 | ||
c906108c | 14449 | There are three classes of targets: processes, core files, and |
7a292a7a SS |
14450 | executable files. @value{GDBN} can work concurrently on up to three |
14451 | active targets, one in each class. This allows you to (for example) | |
14452 | start a process and inspect its activity without abandoning your work on | |
14453 | a core file. | |
c906108c SS |
14454 | |
14455 | For example, if you execute @samp{gdb a.out}, then the executable file | |
14456 | @code{a.out} is the only active target. If you designate a core file as | |
14457 | well---presumably from a prior run that crashed and coredumped---then | |
14458 | @value{GDBN} has two active targets and uses them in tandem, looking | |
14459 | first in the corefile target, then in the executable file, to satisfy | |
14460 | requests for memory addresses. (Typically, these two classes of target | |
14461 | are complementary, since core files contain only a program's | |
14462 | read-write memory---variables and so on---plus machine status, while | |
14463 | executable files contain only the program text and initialized data.) | |
c906108c SS |
14464 | |
14465 | When you type @code{run}, your executable file becomes an active process | |
7a292a7a SS |
14466 | target as well. When a process target is active, all @value{GDBN} |
14467 | commands requesting memory addresses refer to that target; addresses in | |
14468 | an active core file or executable file target are obscured while the | |
14469 | process target is active. | |
c906108c | 14470 | |
7a292a7a | 14471 | Use the @code{core-file} and @code{exec-file} commands to select a new |
79a6e687 BW |
14472 | core file or executable target (@pxref{Files, ,Commands to Specify |
14473 | Files}). To specify as a target a process that is already running, use | |
14474 | the @code{attach} command (@pxref{Attach, ,Debugging an Already-running | |
14475 | Process}). | |
c906108c | 14476 | |
6d2ebf8b | 14477 | @node Target Commands |
79a6e687 | 14478 | @section Commands for Managing Targets |
c906108c SS |
14479 | |
14480 | @table @code | |
14481 | @item target @var{type} @var{parameters} | |
7a292a7a SS |
14482 | Connects the @value{GDBN} host environment to a target machine or |
14483 | process. A target is typically a protocol for talking to debugging | |
14484 | facilities. You use the argument @var{type} to specify the type or | |
14485 | protocol of the target machine. | |
c906108c SS |
14486 | |
14487 | Further @var{parameters} are interpreted by the target protocol, but | |
14488 | typically include things like device names or host names to connect | |
14489 | with, process numbers, and baud rates. | |
c906108c SS |
14490 | |
14491 | The @code{target} command does not repeat if you press @key{RET} again | |
14492 | after executing the command. | |
14493 | ||
14494 | @kindex help target | |
14495 | @item help target | |
14496 | Displays the names of all targets available. To display targets | |
14497 | currently selected, use either @code{info target} or @code{info files} | |
79a6e687 | 14498 | (@pxref{Files, ,Commands to Specify Files}). |
c906108c SS |
14499 | |
14500 | @item help target @var{name} | |
14501 | Describe a particular target, including any parameters necessary to | |
14502 | select it. | |
14503 | ||
14504 | @kindex set gnutarget | |
14505 | @item set gnutarget @var{args} | |
5d161b24 | 14506 | @value{GDBN} uses its own library BFD to read your files. @value{GDBN} |
c906108c | 14507 | knows whether it is reading an @dfn{executable}, |
5d161b24 DB |
14508 | a @dfn{core}, or a @dfn{.o} file; however, you can specify the file format |
14509 | with the @code{set gnutarget} command. Unlike most @code{target} commands, | |
c906108c SS |
14510 | with @code{gnutarget} the @code{target} refers to a program, not a machine. |
14511 | ||
d4f3574e | 14512 | @quotation |
c906108c SS |
14513 | @emph{Warning:} To specify a file format with @code{set gnutarget}, |
14514 | you must know the actual BFD name. | |
d4f3574e | 14515 | @end quotation |
c906108c | 14516 | |
d4f3574e | 14517 | @noindent |
79a6e687 | 14518 | @xref{Files, , Commands to Specify Files}. |
c906108c | 14519 | |
5d161b24 | 14520 | @kindex show gnutarget |
c906108c SS |
14521 | @item show gnutarget |
14522 | Use the @code{show gnutarget} command to display what file format | |
14523 | @code{gnutarget} is set to read. If you have not set @code{gnutarget}, | |
14524 | @value{GDBN} will determine the file format for each file automatically, | |
14525 | and @code{show gnutarget} displays @samp{The current BDF target is "auto"}. | |
14526 | @end table | |
14527 | ||
4644b6e3 | 14528 | @cindex common targets |
c906108c SS |
14529 | Here are some common targets (available, or not, depending on the GDB |
14530 | configuration): | |
c906108c SS |
14531 | |
14532 | @table @code | |
4644b6e3 | 14533 | @kindex target |
c906108c | 14534 | @item target exec @var{program} |
4644b6e3 | 14535 | @cindex executable file target |
c906108c SS |
14536 | An executable file. @samp{target exec @var{program}} is the same as |
14537 | @samp{exec-file @var{program}}. | |
14538 | ||
c906108c | 14539 | @item target core @var{filename} |
4644b6e3 | 14540 | @cindex core dump file target |
c906108c SS |
14541 | A core dump file. @samp{target core @var{filename}} is the same as |
14542 | @samp{core-file @var{filename}}. | |
c906108c | 14543 | |
1a10341b | 14544 | @item target remote @var{medium} |
4644b6e3 | 14545 | @cindex remote target |
1a10341b JB |
14546 | A remote system connected to @value{GDBN} via a serial line or network |
14547 | connection. This command tells @value{GDBN} to use its own remote | |
14548 | protocol over @var{medium} for debugging. @xref{Remote Debugging}. | |
14549 | ||
14550 | For example, if you have a board connected to @file{/dev/ttya} on the | |
14551 | machine running @value{GDBN}, you could say: | |
14552 | ||
14553 | @smallexample | |
14554 | target remote /dev/ttya | |
14555 | @end smallexample | |
14556 | ||
14557 | @code{target remote} supports the @code{load} command. This is only | |
14558 | useful if you have some other way of getting the stub to the target | |
14559 | system, and you can put it somewhere in memory where it won't get | |
14560 | clobbered by the download. | |
c906108c | 14561 | |
c906108c | 14562 | @item target sim |
4644b6e3 | 14563 | @cindex built-in simulator target |
2df3850c | 14564 | Builtin CPU simulator. @value{GDBN} includes simulators for most architectures. |
104c1213 | 14565 | In general, |
474c8240 | 14566 | @smallexample |
104c1213 JM |
14567 | target sim |
14568 | load | |
14569 | run | |
474c8240 | 14570 | @end smallexample |
d4f3574e | 14571 | @noindent |
104c1213 | 14572 | works; however, you cannot assume that a specific memory map, device |
d4f3574e | 14573 | drivers, or even basic I/O is available, although some simulators do |
104c1213 JM |
14574 | provide these. For info about any processor-specific simulator details, |
14575 | see the appropriate section in @ref{Embedded Processors, ,Embedded | |
14576 | Processors}. | |
14577 | ||
c906108c SS |
14578 | @end table |
14579 | ||
104c1213 | 14580 | Some configurations may include these targets as well: |
c906108c SS |
14581 | |
14582 | @table @code | |
14583 | ||
c906108c | 14584 | @item target nrom @var{dev} |
4644b6e3 | 14585 | @cindex NetROM ROM emulator target |
c906108c SS |
14586 | NetROM ROM emulator. This target only supports downloading. |
14587 | ||
c906108c SS |
14588 | @end table |
14589 | ||
5d161b24 | 14590 | Different targets are available on different configurations of @value{GDBN}; |
c906108c | 14591 | your configuration may have more or fewer targets. |
c906108c | 14592 | |
721c2651 EZ |
14593 | Many remote targets require you to download the executable's code once |
14594 | you've successfully established a connection. You may wish to control | |
3d00d119 DJ |
14595 | various aspects of this process. |
14596 | ||
14597 | @table @code | |
721c2651 EZ |
14598 | |
14599 | @item set hash | |
14600 | @kindex set hash@r{, for remote monitors} | |
14601 | @cindex hash mark while downloading | |
14602 | This command controls whether a hash mark @samp{#} is displayed while | |
14603 | downloading a file to the remote monitor. If on, a hash mark is | |
14604 | displayed after each S-record is successfully downloaded to the | |
14605 | monitor. | |
14606 | ||
14607 | @item show hash | |
14608 | @kindex show hash@r{, for remote monitors} | |
14609 | Show the current status of displaying the hash mark. | |
14610 | ||
14611 | @item set debug monitor | |
14612 | @kindex set debug monitor | |
14613 | @cindex display remote monitor communications | |
14614 | Enable or disable display of communications messages between | |
14615 | @value{GDBN} and the remote monitor. | |
14616 | ||
14617 | @item show debug monitor | |
14618 | @kindex show debug monitor | |
14619 | Show the current status of displaying communications between | |
14620 | @value{GDBN} and the remote monitor. | |
a8f24a35 | 14621 | @end table |
c906108c SS |
14622 | |
14623 | @table @code | |
14624 | ||
14625 | @kindex load @var{filename} | |
14626 | @item load @var{filename} | |
8edfe269 | 14627 | @anchor{load} |
c906108c SS |
14628 | Depending on what remote debugging facilities are configured into |
14629 | @value{GDBN}, the @code{load} command may be available. Where it exists, it | |
14630 | is meant to make @var{filename} (an executable) available for debugging | |
14631 | on the remote system---by downloading, or dynamic linking, for example. | |
14632 | @code{load} also records the @var{filename} symbol table in @value{GDBN}, like | |
14633 | the @code{add-symbol-file} command. | |
14634 | ||
14635 | If your @value{GDBN} does not have a @code{load} command, attempting to | |
14636 | execute it gets the error message ``@code{You can't do that when your | |
14637 | target is @dots{}}'' | |
c906108c SS |
14638 | |
14639 | The file is loaded at whatever address is specified in the executable. | |
14640 | For some object file formats, you can specify the load address when you | |
14641 | link the program; for other formats, like a.out, the object file format | |
14642 | specifies a fixed address. | |
14643 | @c FIXME! This would be a good place for an xref to the GNU linker doc. | |
14644 | ||
68437a39 DJ |
14645 | Depending on the remote side capabilities, @value{GDBN} may be able to |
14646 | load programs into flash memory. | |
14647 | ||
c906108c SS |
14648 | @code{load} does not repeat if you press @key{RET} again after using it. |
14649 | @end table | |
14650 | ||
6d2ebf8b | 14651 | @node Byte Order |
79a6e687 | 14652 | @section Choosing Target Byte Order |
7a292a7a | 14653 | |
c906108c SS |
14654 | @cindex choosing target byte order |
14655 | @cindex target byte order | |
c906108c | 14656 | |
172c2a43 | 14657 | Some types of processors, such as the MIPS, PowerPC, and Renesas SH, |
c906108c SS |
14658 | offer the ability to run either big-endian or little-endian byte |
14659 | orders. Usually the executable or symbol will include a bit to | |
14660 | designate the endian-ness, and you will not need to worry about | |
14661 | which to use. However, you may still find it useful to adjust | |
d4f3574e | 14662 | @value{GDBN}'s idea of processor endian-ness manually. |
c906108c SS |
14663 | |
14664 | @table @code | |
4644b6e3 | 14665 | @kindex set endian |
c906108c SS |
14666 | @item set endian big |
14667 | Instruct @value{GDBN} to assume the target is big-endian. | |
14668 | ||
c906108c SS |
14669 | @item set endian little |
14670 | Instruct @value{GDBN} to assume the target is little-endian. | |
14671 | ||
c906108c SS |
14672 | @item set endian auto |
14673 | Instruct @value{GDBN} to use the byte order associated with the | |
14674 | executable. | |
14675 | ||
14676 | @item show endian | |
14677 | Display @value{GDBN}'s current idea of the target byte order. | |
14678 | ||
14679 | @end table | |
14680 | ||
14681 | Note that these commands merely adjust interpretation of symbolic | |
14682 | data on the host, and that they have absolutely no effect on the | |
14683 | target system. | |
14684 | ||
ea35711c DJ |
14685 | |
14686 | @node Remote Debugging | |
14687 | @chapter Debugging Remote Programs | |
c906108c SS |
14688 | @cindex remote debugging |
14689 | ||
14690 | If you are trying to debug a program running on a machine that cannot run | |
5d161b24 DB |
14691 | @value{GDBN} in the usual way, it is often useful to use remote debugging. |
14692 | For example, you might use remote debugging on an operating system kernel, | |
c906108c SS |
14693 | or on a small system which does not have a general purpose operating system |
14694 | powerful enough to run a full-featured debugger. | |
14695 | ||
14696 | Some configurations of @value{GDBN} have special serial or TCP/IP interfaces | |
14697 | to make this work with particular debugging targets. In addition, | |
5d161b24 | 14698 | @value{GDBN} comes with a generic serial protocol (specific to @value{GDBN}, |
c906108c SS |
14699 | but not specific to any particular target system) which you can use if you |
14700 | write the remote stubs---the code that runs on the remote system to | |
14701 | communicate with @value{GDBN}. | |
14702 | ||
14703 | Other remote targets may be available in your | |
14704 | configuration of @value{GDBN}; use @code{help target} to list them. | |
c906108c | 14705 | |
6b2f586d | 14706 | @menu |
07f31aa6 | 14707 | * Connecting:: Connecting to a remote target |
a6b151f1 | 14708 | * File Transfer:: Sending files to a remote system |
6b2f586d | 14709 | * Server:: Using the gdbserver program |
79a6e687 BW |
14710 | * Remote Configuration:: Remote configuration |
14711 | * Remote Stub:: Implementing a remote stub | |
6b2f586d AC |
14712 | @end menu |
14713 | ||
07f31aa6 | 14714 | @node Connecting |
79a6e687 | 14715 | @section Connecting to a Remote Target |
07f31aa6 DJ |
14716 | |
14717 | On the @value{GDBN} host machine, you will need an unstripped copy of | |
d3e8051b | 14718 | your program, since @value{GDBN} needs symbol and debugging information. |
07f31aa6 DJ |
14719 | Start up @value{GDBN} as usual, using the name of the local copy of your |
14720 | program as the first argument. | |
14721 | ||
86941c27 JB |
14722 | @cindex @code{target remote} |
14723 | @value{GDBN} can communicate with the target over a serial line, or | |
14724 | over an @acronym{IP} network using @acronym{TCP} or @acronym{UDP}. In | |
14725 | each case, @value{GDBN} uses the same protocol for debugging your | |
14726 | program; only the medium carrying the debugging packets varies. The | |
14727 | @code{target remote} command establishes a connection to the target. | |
14728 | Its arguments indicate which medium to use: | |
14729 | ||
14730 | @table @code | |
14731 | ||
14732 | @item target remote @var{serial-device} | |
07f31aa6 | 14733 | @cindex serial line, @code{target remote} |
86941c27 JB |
14734 | Use @var{serial-device} to communicate with the target. For example, |
14735 | to use a serial line connected to the device named @file{/dev/ttyb}: | |
14736 | ||
14737 | @smallexample | |
14738 | target remote /dev/ttyb | |
14739 | @end smallexample | |
14740 | ||
07f31aa6 DJ |
14741 | If you're using a serial line, you may want to give @value{GDBN} the |
14742 | @w{@samp{--baud}} option, or use the @code{set remotebaud} command | |
79a6e687 | 14743 | (@pxref{Remote Configuration, set remotebaud}) before the |
9c16f35a | 14744 | @code{target} command. |
07f31aa6 | 14745 | |
86941c27 JB |
14746 | @item target remote @code{@var{host}:@var{port}} |
14747 | @itemx target remote @code{tcp:@var{host}:@var{port}} | |
14748 | @cindex @acronym{TCP} port, @code{target remote} | |
14749 | Debug using a @acronym{TCP} connection to @var{port} on @var{host}. | |
14750 | The @var{host} may be either a host name or a numeric @acronym{IP} | |
14751 | address; @var{port} must be a decimal number. The @var{host} could be | |
14752 | the target machine itself, if it is directly connected to the net, or | |
14753 | it might be a terminal server which in turn has a serial line to the | |
14754 | target. | |
07f31aa6 | 14755 | |
86941c27 JB |
14756 | For example, to connect to port 2828 on a terminal server named |
14757 | @code{manyfarms}: | |
07f31aa6 DJ |
14758 | |
14759 | @smallexample | |
14760 | target remote manyfarms:2828 | |
14761 | @end smallexample | |
14762 | ||
86941c27 JB |
14763 | If your remote target is actually running on the same machine as your |
14764 | debugger session (e.g.@: a simulator for your target running on the | |
14765 | same host), you can omit the hostname. For example, to connect to | |
14766 | port 1234 on your local machine: | |
07f31aa6 DJ |
14767 | |
14768 | @smallexample | |
14769 | target remote :1234 | |
14770 | @end smallexample | |
14771 | @noindent | |
14772 | ||
14773 | Note that the colon is still required here. | |
14774 | ||
86941c27 JB |
14775 | @item target remote @code{udp:@var{host}:@var{port}} |
14776 | @cindex @acronym{UDP} port, @code{target remote} | |
14777 | Debug using @acronym{UDP} packets to @var{port} on @var{host}. For example, to | |
14778 | connect to @acronym{UDP} port 2828 on a terminal server named @code{manyfarms}: | |
07f31aa6 DJ |
14779 | |
14780 | @smallexample | |
14781 | target remote udp:manyfarms:2828 | |
14782 | @end smallexample | |
14783 | ||
86941c27 JB |
14784 | When using a @acronym{UDP} connection for remote debugging, you should |
14785 | keep in mind that the `U' stands for ``Unreliable''. @acronym{UDP} | |
14786 | can silently drop packets on busy or unreliable networks, which will | |
14787 | cause havoc with your debugging session. | |
14788 | ||
66b8c7f6 JB |
14789 | @item target remote | @var{command} |
14790 | @cindex pipe, @code{target remote} to | |
14791 | Run @var{command} in the background and communicate with it using a | |
14792 | pipe. The @var{command} is a shell command, to be parsed and expanded | |
14793 | by the system's command shell, @code{/bin/sh}; it should expect remote | |
14794 | protocol packets on its standard input, and send replies on its | |
14795 | standard output. You could use this to run a stand-alone simulator | |
14796 | that speaks the remote debugging protocol, to make net connections | |
14797 | using programs like @code{ssh}, or for other similar tricks. | |
14798 | ||
14799 | If @var{command} closes its standard output (perhaps by exiting), | |
14800 | @value{GDBN} will try to send it a @code{SIGTERM} signal. (If the | |
14801 | program has already exited, this will have no effect.) | |
14802 | ||
86941c27 | 14803 | @end table |
07f31aa6 | 14804 | |
86941c27 | 14805 | Once the connection has been established, you can use all the usual |
8edfe269 DJ |
14806 | commands to examine and change data. The remote program is already |
14807 | running; you can use @kbd{step} and @kbd{continue}, and you do not | |
14808 | need to use @kbd{run}. | |
07f31aa6 DJ |
14809 | |
14810 | @cindex interrupting remote programs | |
14811 | @cindex remote programs, interrupting | |
14812 | Whenever @value{GDBN} is waiting for the remote program, if you type the | |
c8aa23ab | 14813 | interrupt character (often @kbd{Ctrl-c}), @value{GDBN} attempts to stop the |
07f31aa6 DJ |
14814 | program. This may or may not succeed, depending in part on the hardware |
14815 | and the serial drivers the remote system uses. If you type the | |
14816 | interrupt character once again, @value{GDBN} displays this prompt: | |
14817 | ||
14818 | @smallexample | |
14819 | Interrupted while waiting for the program. | |
14820 | Give up (and stop debugging it)? (y or n) | |
14821 | @end smallexample | |
14822 | ||
14823 | If you type @kbd{y}, @value{GDBN} abandons the remote debugging session. | |
14824 | (If you decide you want to try again later, you can use @samp{target | |
14825 | remote} again to connect once more.) If you type @kbd{n}, @value{GDBN} | |
14826 | goes back to waiting. | |
14827 | ||
14828 | @table @code | |
14829 | @kindex detach (remote) | |
14830 | @item detach | |
14831 | When you have finished debugging the remote program, you can use the | |
14832 | @code{detach} command to release it from @value{GDBN} control. | |
14833 | Detaching from the target normally resumes its execution, but the results | |
14834 | will depend on your particular remote stub. After the @code{detach} | |
14835 | command, @value{GDBN} is free to connect to another target. | |
14836 | ||
14837 | @kindex disconnect | |
14838 | @item disconnect | |
14839 | The @code{disconnect} command behaves like @code{detach}, except that | |
14840 | the target is generally not resumed. It will wait for @value{GDBN} | |
14841 | (this instance or another one) to connect and continue debugging. After | |
14842 | the @code{disconnect} command, @value{GDBN} is again free to connect to | |
14843 | another target. | |
09d4efe1 EZ |
14844 | |
14845 | @cindex send command to remote monitor | |
fad38dfa EZ |
14846 | @cindex extend @value{GDBN} for remote targets |
14847 | @cindex add new commands for external monitor | |
09d4efe1 EZ |
14848 | @kindex monitor |
14849 | @item monitor @var{cmd} | |
fad38dfa EZ |
14850 | This command allows you to send arbitrary commands directly to the |
14851 | remote monitor. Since @value{GDBN} doesn't care about the commands it | |
14852 | sends like this, this command is the way to extend @value{GDBN}---you | |
14853 | can add new commands that only the external monitor will understand | |
14854 | and implement. | |
07f31aa6 DJ |
14855 | @end table |
14856 | ||
a6b151f1 DJ |
14857 | @node File Transfer |
14858 | @section Sending files to a remote system | |
14859 | @cindex remote target, file transfer | |
14860 | @cindex file transfer | |
14861 | @cindex sending files to remote systems | |
14862 | ||
14863 | Some remote targets offer the ability to transfer files over the same | |
14864 | connection used to communicate with @value{GDBN}. This is convenient | |
14865 | for targets accessible through other means, e.g.@: @sc{gnu}/Linux systems | |
14866 | running @code{gdbserver} over a network interface. For other targets, | |
14867 | e.g.@: embedded devices with only a single serial port, this may be | |
14868 | the only way to upload or download files. | |
14869 | ||
14870 | Not all remote targets support these commands. | |
14871 | ||
14872 | @table @code | |
14873 | @kindex remote put | |
14874 | @item remote put @var{hostfile} @var{targetfile} | |
14875 | Copy file @var{hostfile} from the host system (the machine running | |
14876 | @value{GDBN}) to @var{targetfile} on the target system. | |
14877 | ||
14878 | @kindex remote get | |
14879 | @item remote get @var{targetfile} @var{hostfile} | |
14880 | Copy file @var{targetfile} from the target system to @var{hostfile} | |
14881 | on the host system. | |
14882 | ||
14883 | @kindex remote delete | |
14884 | @item remote delete @var{targetfile} | |
14885 | Delete @var{targetfile} from the target system. | |
14886 | ||
14887 | @end table | |
14888 | ||
6f05cf9f | 14889 | @node Server |
79a6e687 | 14890 | @section Using the @code{gdbserver} Program |
6f05cf9f AC |
14891 | |
14892 | @kindex gdbserver | |
14893 | @cindex remote connection without stubs | |
14894 | @code{gdbserver} is a control program for Unix-like systems, which | |
14895 | allows you to connect your program with a remote @value{GDBN} via | |
14896 | @code{target remote}---but without linking in the usual debugging stub. | |
14897 | ||
14898 | @code{gdbserver} is not a complete replacement for the debugging stubs, | |
14899 | because it requires essentially the same operating-system facilities | |
14900 | that @value{GDBN} itself does. In fact, a system that can run | |
14901 | @code{gdbserver} to connect to a remote @value{GDBN} could also run | |
14902 | @value{GDBN} locally! @code{gdbserver} is sometimes useful nevertheless, | |
14903 | because it is a much smaller program than @value{GDBN} itself. It is | |
14904 | also easier to port than all of @value{GDBN}, so you may be able to get | |
14905 | started more quickly on a new system by using @code{gdbserver}. | |
14906 | Finally, if you develop code for real-time systems, you may find that | |
14907 | the tradeoffs involved in real-time operation make it more convenient to | |
14908 | do as much development work as possible on another system, for example | |
14909 | by cross-compiling. You can use @code{gdbserver} to make a similar | |
14910 | choice for debugging. | |
14911 | ||
14912 | @value{GDBN} and @code{gdbserver} communicate via either a serial line | |
14913 | or a TCP connection, using the standard @value{GDBN} remote serial | |
14914 | protocol. | |
14915 | ||
2d717e4f DJ |
14916 | @quotation |
14917 | @emph{Warning:} @code{gdbserver} does not have any built-in security. | |
14918 | Do not run @code{gdbserver} connected to any public network; a | |
14919 | @value{GDBN} connection to @code{gdbserver} provides access to the | |
14920 | target system with the same privileges as the user running | |
14921 | @code{gdbserver}. | |
14922 | @end quotation | |
14923 | ||
14924 | @subsection Running @code{gdbserver} | |
14925 | @cindex arguments, to @code{gdbserver} | |
14926 | ||
14927 | Run @code{gdbserver} on the target system. You need a copy of the | |
14928 | program you want to debug, including any libraries it requires. | |
6f05cf9f AC |
14929 | @code{gdbserver} does not need your program's symbol table, so you can |
14930 | strip the program if necessary to save space. @value{GDBN} on the host | |
14931 | system does all the symbol handling. | |
14932 | ||
14933 | To use the server, you must tell it how to communicate with @value{GDBN}; | |
56460a61 | 14934 | the name of your program; and the arguments for your program. The usual |
6f05cf9f AC |
14935 | syntax is: |
14936 | ||
14937 | @smallexample | |
14938 | target> gdbserver @var{comm} @var{program} [ @var{args} @dots{} ] | |
14939 | @end smallexample | |
14940 | ||
14941 | @var{comm} is either a device name (to use a serial line) or a TCP | |
14942 | hostname and portnumber. For example, to debug Emacs with the argument | |
14943 | @samp{foo.txt} and communicate with @value{GDBN} over the serial port | |
14944 | @file{/dev/com1}: | |
14945 | ||
14946 | @smallexample | |
14947 | target> gdbserver /dev/com1 emacs foo.txt | |
14948 | @end smallexample | |
14949 | ||
14950 | @code{gdbserver} waits passively for the host @value{GDBN} to communicate | |
14951 | with it. | |
14952 | ||
14953 | To use a TCP connection instead of a serial line: | |
14954 | ||
14955 | @smallexample | |
14956 | target> gdbserver host:2345 emacs foo.txt | |
14957 | @end smallexample | |
14958 | ||
14959 | The only difference from the previous example is the first argument, | |
14960 | specifying that you are communicating with the host @value{GDBN} via | |
14961 | TCP. The @samp{host:2345} argument means that @code{gdbserver} is to | |
14962 | expect a TCP connection from machine @samp{host} to local TCP port 2345. | |
14963 | (Currently, the @samp{host} part is ignored.) You can choose any number | |
14964 | you want for the port number as long as it does not conflict with any | |
14965 | TCP ports already in use on the target system (for example, @code{23} is | |
14966 | reserved for @code{telnet}).@footnote{If you choose a port number that | |
14967 | conflicts with another service, @code{gdbserver} prints an error message | |
14968 | and exits.} You must use the same port number with the host @value{GDBN} | |
14969 | @code{target remote} command. | |
14970 | ||
2d717e4f DJ |
14971 | @subsubsection Attaching to a Running Program |
14972 | ||
56460a61 DJ |
14973 | On some targets, @code{gdbserver} can also attach to running programs. |
14974 | This is accomplished via the @code{--attach} argument. The syntax is: | |
14975 | ||
14976 | @smallexample | |
2d717e4f | 14977 | target> gdbserver --attach @var{comm} @var{pid} |
56460a61 DJ |
14978 | @end smallexample |
14979 | ||
14980 | @var{pid} is the process ID of a currently running process. It isn't necessary | |
14981 | to point @code{gdbserver} at a binary for the running process. | |
14982 | ||
b1fe9455 DJ |
14983 | @pindex pidof |
14984 | @cindex attach to a program by name | |
14985 | You can debug processes by name instead of process ID if your target has the | |
14986 | @code{pidof} utility: | |
14987 | ||
14988 | @smallexample | |
2d717e4f | 14989 | target> gdbserver --attach @var{comm} `pidof @var{program}` |
b1fe9455 DJ |
14990 | @end smallexample |
14991 | ||
f822c95b | 14992 | In case more than one copy of @var{program} is running, or @var{program} |
b1fe9455 DJ |
14993 | has multiple threads, most versions of @code{pidof} support the |
14994 | @code{-s} option to only return the first process ID. | |
14995 | ||
2d717e4f DJ |
14996 | @subsubsection Multi-Process Mode for @code{gdbserver} |
14997 | @cindex gdbserver, multiple processes | |
14998 | @cindex multiple processes with gdbserver | |
14999 | ||
15000 | When you connect to @code{gdbserver} using @code{target remote}, | |
15001 | @code{gdbserver} debugs the specified program only once. When the | |
15002 | program exits, or you detach from it, @value{GDBN} closes the connection | |
15003 | and @code{gdbserver} exits. | |
15004 | ||
6e6c6f50 | 15005 | If you connect using @kbd{target extended-remote}, @code{gdbserver} |
2d717e4f DJ |
15006 | enters multi-process mode. When the debugged program exits, or you |
15007 | detach from it, @value{GDBN} stays connected to @code{gdbserver} even | |
15008 | though no program is running. The @code{run} and @code{attach} | |
15009 | commands instruct @code{gdbserver} to run or attach to a new program. | |
15010 | The @code{run} command uses @code{set remote exec-file} (@pxref{set | |
15011 | remote exec-file}) to select the program to run. Command line | |
15012 | arguments are supported, except for wildcard expansion and I/O | |
15013 | redirection (@pxref{Arguments}). | |
15014 | ||
15015 | To start @code{gdbserver} without supplying an initial command to run | |
15016 | or process ID to attach, use the @option{--multi} command line option. | |
6e6c6f50 | 15017 | Then you can connect using @kbd{target extended-remote} and start |
2d717e4f DJ |
15018 | the program you want to debug. |
15019 | ||
15020 | @code{gdbserver} does not automatically exit in multi-process mode. | |
15021 | You can terminate it by using @code{monitor exit} | |
15022 | (@pxref{Monitor Commands for gdbserver}). | |
15023 | ||
15024 | @subsubsection Other Command-Line Arguments for @code{gdbserver} | |
15025 | ||
62709adf PA |
15026 | The @option{--debug} option tells @code{gdbserver} to display extra |
15027 | status information about the debugging process. The | |
15028 | @option{--remote-debug} option tells @code{gdbserver} to display | |
15029 | remote protocol debug output. These options are intended for | |
15030 | @code{gdbserver} development and for bug reports to the developers. | |
2d717e4f | 15031 | |
ccd213ac DJ |
15032 | The @option{--wrapper} option specifies a wrapper to launch programs |
15033 | for debugging. The option should be followed by the name of the | |
15034 | wrapper, then any command-line arguments to pass to the wrapper, then | |
15035 | @kbd{--} indicating the end of the wrapper arguments. | |
15036 | ||
15037 | @code{gdbserver} runs the specified wrapper program with a combined | |
15038 | command line including the wrapper arguments, then the name of the | |
15039 | program to debug, then any arguments to the program. The wrapper | |
15040 | runs until it executes your program, and then @value{GDBN} gains control. | |
15041 | ||
15042 | You can use any program that eventually calls @code{execve} with | |
15043 | its arguments as a wrapper. Several standard Unix utilities do | |
15044 | this, e.g.@: @code{env} and @code{nohup}. Any Unix shell script ending | |
15045 | with @code{exec "$@@"} will also work. | |
15046 | ||
15047 | For example, you can use @code{env} to pass an environment variable to | |
15048 | the debugged program, without setting the variable in @code{gdbserver}'s | |
15049 | environment: | |
15050 | ||
15051 | @smallexample | |
15052 | $ gdbserver --wrapper env LD_PRELOAD=libtest.so -- :2222 ./testprog | |
15053 | @end smallexample | |
15054 | ||
2d717e4f DJ |
15055 | @subsection Connecting to @code{gdbserver} |
15056 | ||
15057 | Run @value{GDBN} on the host system. | |
15058 | ||
15059 | First make sure you have the necessary symbol files. Load symbols for | |
f822c95b DJ |
15060 | your application using the @code{file} command before you connect. Use |
15061 | @code{set sysroot} to locate target libraries (unless your @value{GDBN} | |
2d717e4f | 15062 | was compiled with the correct sysroot using @code{--with-sysroot}). |
f822c95b DJ |
15063 | |
15064 | The symbol file and target libraries must exactly match the executable | |
15065 | and libraries on the target, with one exception: the files on the host | |
15066 | system should not be stripped, even if the files on the target system | |
15067 | are. Mismatched or missing files will lead to confusing results | |
15068 | during debugging. On @sc{gnu}/Linux targets, mismatched or missing | |
15069 | files may also prevent @code{gdbserver} from debugging multi-threaded | |
15070 | programs. | |
15071 | ||
79a6e687 | 15072 | Connect to your target (@pxref{Connecting,,Connecting to a Remote Target}). |
6f05cf9f AC |
15073 | For TCP connections, you must start up @code{gdbserver} prior to using |
15074 | the @code{target remote} command. Otherwise you may get an error whose | |
15075 | text depends on the host system, but which usually looks something like | |
2d717e4f | 15076 | @samp{Connection refused}. Don't use the @code{load} |
397ca115 | 15077 | command in @value{GDBN} when using @code{gdbserver}, since the program is |
f822c95b | 15078 | already on the target. |
07f31aa6 | 15079 | |
79a6e687 | 15080 | @subsection Monitor Commands for @code{gdbserver} |
c74d0ad8 | 15081 | @cindex monitor commands, for @code{gdbserver} |
2d717e4f | 15082 | @anchor{Monitor Commands for gdbserver} |
c74d0ad8 DJ |
15083 | |
15084 | During a @value{GDBN} session using @code{gdbserver}, you can use the | |
15085 | @code{monitor} command to send special requests to @code{gdbserver}. | |
2d717e4f | 15086 | Here are the available commands. |
c74d0ad8 DJ |
15087 | |
15088 | @table @code | |
15089 | @item monitor help | |
15090 | List the available monitor commands. | |
15091 | ||
15092 | @item monitor set debug 0 | |
15093 | @itemx monitor set debug 1 | |
15094 | Disable or enable general debugging messages. | |
15095 | ||
15096 | @item monitor set remote-debug 0 | |
15097 | @itemx monitor set remote-debug 1 | |
15098 | Disable or enable specific debugging messages associated with the remote | |
15099 | protocol (@pxref{Remote Protocol}). | |
15100 | ||
cdbfd419 PP |
15101 | @item monitor set libthread-db-search-path [PATH] |
15102 | @cindex gdbserver, search path for @code{libthread_db} | |
15103 | When this command is issued, @var{path} is a colon-separated list of | |
15104 | directories to search for @code{libthread_db} (@pxref{Threads,,set | |
15105 | libthread-db-search-path}). If you omit @var{path}, | |
15106 | @samp{libthread-db-search-path} will be reset to an empty list. | |
15107 | ||
2d717e4f DJ |
15108 | @item monitor exit |
15109 | Tell gdbserver to exit immediately. This command should be followed by | |
15110 | @code{disconnect} to close the debugging session. @code{gdbserver} will | |
15111 | detach from any attached processes and kill any processes it created. | |
15112 | Use @code{monitor exit} to terminate @code{gdbserver} at the end | |
15113 | of a multi-process mode debug session. | |
15114 | ||
c74d0ad8 DJ |
15115 | @end table |
15116 | ||
79a6e687 BW |
15117 | @node Remote Configuration |
15118 | @section Remote Configuration | |
501eef12 | 15119 | |
9c16f35a EZ |
15120 | @kindex set remote |
15121 | @kindex show remote | |
15122 | This section documents the configuration options available when | |
15123 | debugging remote programs. For the options related to the File I/O | |
fc320d37 | 15124 | extensions of the remote protocol, see @ref{system, |
9c16f35a | 15125 | system-call-allowed}. |
501eef12 AC |
15126 | |
15127 | @table @code | |
9c16f35a | 15128 | @item set remoteaddresssize @var{bits} |
d3e8051b | 15129 | @cindex address size for remote targets |
9c16f35a EZ |
15130 | @cindex bits in remote address |
15131 | Set the maximum size of address in a memory packet to the specified | |
15132 | number of bits. @value{GDBN} will mask off the address bits above | |
15133 | that number, when it passes addresses to the remote target. The | |
15134 | default value is the number of bits in the target's address. | |
15135 | ||
15136 | @item show remoteaddresssize | |
15137 | Show the current value of remote address size in bits. | |
15138 | ||
15139 | @item set remotebaud @var{n} | |
15140 | @cindex baud rate for remote targets | |
15141 | Set the baud rate for the remote serial I/O to @var{n} baud. The | |
15142 | value is used to set the speed of the serial port used for debugging | |
15143 | remote targets. | |
15144 | ||
15145 | @item show remotebaud | |
15146 | Show the current speed of the remote connection. | |
15147 | ||
15148 | @item set remotebreak | |
15149 | @cindex interrupt remote programs | |
15150 | @cindex BREAK signal instead of Ctrl-C | |
9a6253be | 15151 | @anchor{set remotebreak} |
9c16f35a | 15152 | If set to on, @value{GDBN} sends a @code{BREAK} signal to the remote |
c8aa23ab | 15153 | when you type @kbd{Ctrl-c} to interrupt the program running |
9a7a1b36 | 15154 | on the remote. If set to off, @value{GDBN} sends the @samp{Ctrl-C} |
9c16f35a EZ |
15155 | character instead. The default is off, since most remote systems |
15156 | expect to see @samp{Ctrl-C} as the interrupt signal. | |
15157 | ||
15158 | @item show remotebreak | |
15159 | Show whether @value{GDBN} sends @code{BREAK} or @samp{Ctrl-C} to | |
15160 | interrupt the remote program. | |
15161 | ||
23776285 MR |
15162 | @item set remoteflow on |
15163 | @itemx set remoteflow off | |
15164 | @kindex set remoteflow | |
15165 | Enable or disable hardware flow control (@code{RTS}/@code{CTS}) | |
15166 | on the serial port used to communicate to the remote target. | |
15167 | ||
15168 | @item show remoteflow | |
15169 | @kindex show remoteflow | |
15170 | Show the current setting of hardware flow control. | |
15171 | ||
9c16f35a EZ |
15172 | @item set remotelogbase @var{base} |
15173 | Set the base (a.k.a.@: radix) of logging serial protocol | |
15174 | communications to @var{base}. Supported values of @var{base} are: | |
15175 | @code{ascii}, @code{octal}, and @code{hex}. The default is | |
15176 | @code{ascii}. | |
15177 | ||
15178 | @item show remotelogbase | |
15179 | Show the current setting of the radix for logging remote serial | |
15180 | protocol. | |
15181 | ||
15182 | @item set remotelogfile @var{file} | |
15183 | @cindex record serial communications on file | |
15184 | Record remote serial communications on the named @var{file}. The | |
15185 | default is not to record at all. | |
15186 | ||
15187 | @item show remotelogfile. | |
15188 | Show the current setting of the file name on which to record the | |
15189 | serial communications. | |
15190 | ||
15191 | @item set remotetimeout @var{num} | |
15192 | @cindex timeout for serial communications | |
15193 | @cindex remote timeout | |
15194 | Set the timeout limit to wait for the remote target to respond to | |
15195 | @var{num} seconds. The default is 2 seconds. | |
15196 | ||
15197 | @item show remotetimeout | |
15198 | Show the current number of seconds to wait for the remote target | |
15199 | responses. | |
15200 | ||
15201 | @cindex limit hardware breakpoints and watchpoints | |
15202 | @cindex remote target, limit break- and watchpoints | |
501eef12 AC |
15203 | @anchor{set remote hardware-watchpoint-limit} |
15204 | @anchor{set remote hardware-breakpoint-limit} | |
15205 | @item set remote hardware-watchpoint-limit @var{limit} | |
15206 | @itemx set remote hardware-breakpoint-limit @var{limit} | |
15207 | Restrict @value{GDBN} to using @var{limit} remote hardware breakpoint or | |
15208 | watchpoints. A limit of -1, the default, is treated as unlimited. | |
2d717e4f DJ |
15209 | |
15210 | @item set remote exec-file @var{filename} | |
15211 | @itemx show remote exec-file | |
15212 | @anchor{set remote exec-file} | |
15213 | @cindex executable file, for remote target | |
15214 | Select the file used for @code{run} with @code{target | |
15215 | extended-remote}. This should be set to a filename valid on the | |
15216 | target system. If it is not set, the target will use a default | |
15217 | filename (e.g.@: the last program run). | |
84603566 SL |
15218 | |
15219 | @kindex set tcp | |
15220 | @kindex show tcp | |
15221 | @item set tcp auto-retry on | |
15222 | @cindex auto-retry, for remote TCP target | |
15223 | Enable auto-retry for remote TCP connections. This is useful if the remote | |
15224 | debugging agent is launched in parallel with @value{GDBN}; there is a race | |
15225 | condition because the agent may not become ready to accept the connection | |
15226 | before @value{GDBN} attempts to connect. When auto-retry is | |
15227 | enabled, if the initial attempt to connect fails, @value{GDBN} reattempts | |
15228 | to establish the connection using the timeout specified by | |
15229 | @code{set tcp connect-timeout}. | |
15230 | ||
15231 | @item set tcp auto-retry off | |
15232 | Do not auto-retry failed TCP connections. | |
15233 | ||
15234 | @item show tcp auto-retry | |
15235 | Show the current auto-retry setting. | |
15236 | ||
15237 | @item set tcp connect-timeout @var{seconds} | |
15238 | @cindex connection timeout, for remote TCP target | |
15239 | @cindex timeout, for remote target connection | |
15240 | Set the timeout for establishing a TCP connection to the remote target to | |
15241 | @var{seconds}. The timeout affects both polling to retry failed connections | |
15242 | (enabled by @code{set tcp auto-retry on}) and waiting for connections | |
15243 | that are merely slow to complete, and represents an approximate cumulative | |
15244 | value. | |
15245 | ||
15246 | @item show tcp connect-timeout | |
15247 | Show the current connection timeout setting. | |
501eef12 AC |
15248 | @end table |
15249 | ||
427c3a89 DJ |
15250 | @cindex remote packets, enabling and disabling |
15251 | The @value{GDBN} remote protocol autodetects the packets supported by | |
15252 | your debugging stub. If you need to override the autodetection, you | |
15253 | can use these commands to enable or disable individual packets. Each | |
15254 | packet can be set to @samp{on} (the remote target supports this | |
15255 | packet), @samp{off} (the remote target does not support this packet), | |
15256 | or @samp{auto} (detect remote target support for this packet). They | |
15257 | all default to @samp{auto}. For more information about each packet, | |
15258 | see @ref{Remote Protocol}. | |
15259 | ||
15260 | During normal use, you should not have to use any of these commands. | |
15261 | If you do, that may be a bug in your remote debugging stub, or a bug | |
15262 | in @value{GDBN}. You may want to report the problem to the | |
15263 | @value{GDBN} developers. | |
15264 | ||
cfa9d6d9 DJ |
15265 | For each packet @var{name}, the command to enable or disable the |
15266 | packet is @code{set remote @var{name}-packet}. The available settings | |
15267 | are: | |
427c3a89 | 15268 | |
cfa9d6d9 | 15269 | @multitable @columnfractions 0.28 0.32 0.25 |
427c3a89 DJ |
15270 | @item Command Name |
15271 | @tab Remote Packet | |
15272 | @tab Related Features | |
15273 | ||
cfa9d6d9 | 15274 | @item @code{fetch-register} |
427c3a89 DJ |
15275 | @tab @code{p} |
15276 | @tab @code{info registers} | |
15277 | ||
cfa9d6d9 | 15278 | @item @code{set-register} |
427c3a89 DJ |
15279 | @tab @code{P} |
15280 | @tab @code{set} | |
15281 | ||
cfa9d6d9 | 15282 | @item @code{binary-download} |
427c3a89 DJ |
15283 | @tab @code{X} |
15284 | @tab @code{load}, @code{set} | |
15285 | ||
cfa9d6d9 | 15286 | @item @code{read-aux-vector} |
427c3a89 DJ |
15287 | @tab @code{qXfer:auxv:read} |
15288 | @tab @code{info auxv} | |
15289 | ||
cfa9d6d9 | 15290 | @item @code{symbol-lookup} |
427c3a89 DJ |
15291 | @tab @code{qSymbol} |
15292 | @tab Detecting multiple threads | |
15293 | ||
2d717e4f DJ |
15294 | @item @code{attach} |
15295 | @tab @code{vAttach} | |
15296 | @tab @code{attach} | |
15297 | ||
cfa9d6d9 | 15298 | @item @code{verbose-resume} |
427c3a89 DJ |
15299 | @tab @code{vCont} |
15300 | @tab Stepping or resuming multiple threads | |
15301 | ||
2d717e4f DJ |
15302 | @item @code{run} |
15303 | @tab @code{vRun} | |
15304 | @tab @code{run} | |
15305 | ||
cfa9d6d9 | 15306 | @item @code{software-breakpoint} |
427c3a89 DJ |
15307 | @tab @code{Z0} |
15308 | @tab @code{break} | |
15309 | ||
cfa9d6d9 | 15310 | @item @code{hardware-breakpoint} |
427c3a89 DJ |
15311 | @tab @code{Z1} |
15312 | @tab @code{hbreak} | |
15313 | ||
cfa9d6d9 | 15314 | @item @code{write-watchpoint} |
427c3a89 DJ |
15315 | @tab @code{Z2} |
15316 | @tab @code{watch} | |
15317 | ||
cfa9d6d9 | 15318 | @item @code{read-watchpoint} |
427c3a89 DJ |
15319 | @tab @code{Z3} |
15320 | @tab @code{rwatch} | |
15321 | ||
cfa9d6d9 | 15322 | @item @code{access-watchpoint} |
427c3a89 DJ |
15323 | @tab @code{Z4} |
15324 | @tab @code{awatch} | |
15325 | ||
cfa9d6d9 DJ |
15326 | @item @code{target-features} |
15327 | @tab @code{qXfer:features:read} | |
15328 | @tab @code{set architecture} | |
15329 | ||
15330 | @item @code{library-info} | |
15331 | @tab @code{qXfer:libraries:read} | |
15332 | @tab @code{info sharedlibrary} | |
15333 | ||
15334 | @item @code{memory-map} | |
15335 | @tab @code{qXfer:memory-map:read} | |
15336 | @tab @code{info mem} | |
15337 | ||
15338 | @item @code{read-spu-object} | |
15339 | @tab @code{qXfer:spu:read} | |
15340 | @tab @code{info spu} | |
15341 | ||
15342 | @item @code{write-spu-object} | |
15343 | @tab @code{qXfer:spu:write} | |
15344 | @tab @code{info spu} | |
15345 | ||
4aa995e1 PA |
15346 | @item @code{read-siginfo-object} |
15347 | @tab @code{qXfer:siginfo:read} | |
15348 | @tab @code{print $_siginfo} | |
15349 | ||
15350 | @item @code{write-siginfo-object} | |
15351 | @tab @code{qXfer:siginfo:write} | |
15352 | @tab @code{set $_siginfo} | |
15353 | ||
cfa9d6d9 | 15354 | @item @code{get-thread-local-@*storage-address} |
427c3a89 DJ |
15355 | @tab @code{qGetTLSAddr} |
15356 | @tab Displaying @code{__thread} variables | |
15357 | ||
08388c79 DE |
15358 | @item @code{search-memory} |
15359 | @tab @code{qSearch:memory} | |
15360 | @tab @code{find} | |
15361 | ||
427c3a89 DJ |
15362 | @item @code{supported-packets} |
15363 | @tab @code{qSupported} | |
15364 | @tab Remote communications parameters | |
15365 | ||
cfa9d6d9 | 15366 | @item @code{pass-signals} |
89be2091 DJ |
15367 | @tab @code{QPassSignals} |
15368 | @tab @code{handle @var{signal}} | |
15369 | ||
a6b151f1 DJ |
15370 | @item @code{hostio-close-packet} |
15371 | @tab @code{vFile:close} | |
15372 | @tab @code{remote get}, @code{remote put} | |
15373 | ||
15374 | @item @code{hostio-open-packet} | |
15375 | @tab @code{vFile:open} | |
15376 | @tab @code{remote get}, @code{remote put} | |
15377 | ||
15378 | @item @code{hostio-pread-packet} | |
15379 | @tab @code{vFile:pread} | |
15380 | @tab @code{remote get}, @code{remote put} | |
15381 | ||
15382 | @item @code{hostio-pwrite-packet} | |
15383 | @tab @code{vFile:pwrite} | |
15384 | @tab @code{remote get}, @code{remote put} | |
15385 | ||
15386 | @item @code{hostio-unlink-packet} | |
15387 | @tab @code{vFile:unlink} | |
15388 | @tab @code{remote delete} | |
a6f3e723 SL |
15389 | |
15390 | @item @code{noack-packet} | |
15391 | @tab @code{QStartNoAckMode} | |
15392 | @tab Packet acknowledgment | |
07e059b5 VP |
15393 | |
15394 | @item @code{osdata} | |
15395 | @tab @code{qXfer:osdata:read} | |
15396 | @tab @code{info os} | |
0b16c5cf PA |
15397 | |
15398 | @item @code{query-attached} | |
15399 | @tab @code{qAttached} | |
15400 | @tab Querying remote process attach state. | |
427c3a89 DJ |
15401 | @end multitable |
15402 | ||
79a6e687 BW |
15403 | @node Remote Stub |
15404 | @section Implementing a Remote Stub | |
7a292a7a | 15405 | |
8e04817f AC |
15406 | @cindex debugging stub, example |
15407 | @cindex remote stub, example | |
15408 | @cindex stub example, remote debugging | |
15409 | The stub files provided with @value{GDBN} implement the target side of the | |
15410 | communication protocol, and the @value{GDBN} side is implemented in the | |
15411 | @value{GDBN} source file @file{remote.c}. Normally, you can simply allow | |
15412 | these subroutines to communicate, and ignore the details. (If you're | |
15413 | implementing your own stub file, you can still ignore the details: start | |
15414 | with one of the existing stub files. @file{sparc-stub.c} is the best | |
15415 | organized, and therefore the easiest to read.) | |
15416 | ||
104c1213 JM |
15417 | @cindex remote serial debugging, overview |
15418 | To debug a program running on another machine (the debugging | |
15419 | @dfn{target} machine), you must first arrange for all the usual | |
15420 | prerequisites for the program to run by itself. For example, for a C | |
15421 | program, you need: | |
c906108c | 15422 | |
104c1213 JM |
15423 | @enumerate |
15424 | @item | |
15425 | A startup routine to set up the C runtime environment; these usually | |
15426 | have a name like @file{crt0}. The startup routine may be supplied by | |
15427 | your hardware supplier, or you may have to write your own. | |
96baa820 | 15428 | |
5d161b24 | 15429 | @item |
d4f3574e | 15430 | A C subroutine library to support your program's |
104c1213 | 15431 | subroutine calls, notably managing input and output. |
96baa820 | 15432 | |
104c1213 JM |
15433 | @item |
15434 | A way of getting your program to the other machine---for example, a | |
15435 | download program. These are often supplied by the hardware | |
15436 | manufacturer, but you may have to write your own from hardware | |
15437 | documentation. | |
15438 | @end enumerate | |
96baa820 | 15439 | |
104c1213 JM |
15440 | The next step is to arrange for your program to use a serial port to |
15441 | communicate with the machine where @value{GDBN} is running (the @dfn{host} | |
15442 | machine). In general terms, the scheme looks like this: | |
96baa820 | 15443 | |
104c1213 JM |
15444 | @table @emph |
15445 | @item On the host, | |
15446 | @value{GDBN} already understands how to use this protocol; when everything | |
15447 | else is set up, you can simply use the @samp{target remote} command | |
15448 | (@pxref{Targets,,Specifying a Debugging Target}). | |
15449 | ||
15450 | @item On the target, | |
15451 | you must link with your program a few special-purpose subroutines that | |
15452 | implement the @value{GDBN} remote serial protocol. The file containing these | |
15453 | subroutines is called a @dfn{debugging stub}. | |
15454 | ||
15455 | On certain remote targets, you can use an auxiliary program | |
15456 | @code{gdbserver} instead of linking a stub into your program. | |
79a6e687 | 15457 | @xref{Server,,Using the @code{gdbserver} Program}, for details. |
104c1213 | 15458 | @end table |
96baa820 | 15459 | |
104c1213 JM |
15460 | The debugging stub is specific to the architecture of the remote |
15461 | machine; for example, use @file{sparc-stub.c} to debug programs on | |
15462 | @sc{sparc} boards. | |
96baa820 | 15463 | |
104c1213 JM |
15464 | @cindex remote serial stub list |
15465 | These working remote stubs are distributed with @value{GDBN}: | |
96baa820 | 15466 | |
104c1213 JM |
15467 | @table @code |
15468 | ||
15469 | @item i386-stub.c | |
41afff9a | 15470 | @cindex @file{i386-stub.c} |
104c1213 JM |
15471 | @cindex Intel |
15472 | @cindex i386 | |
15473 | For Intel 386 and compatible architectures. | |
15474 | ||
15475 | @item m68k-stub.c | |
41afff9a | 15476 | @cindex @file{m68k-stub.c} |
104c1213 JM |
15477 | @cindex Motorola 680x0 |
15478 | @cindex m680x0 | |
15479 | For Motorola 680x0 architectures. | |
15480 | ||
15481 | @item sh-stub.c | |
41afff9a | 15482 | @cindex @file{sh-stub.c} |
172c2a43 | 15483 | @cindex Renesas |
104c1213 | 15484 | @cindex SH |
172c2a43 | 15485 | For Renesas SH architectures. |
104c1213 JM |
15486 | |
15487 | @item sparc-stub.c | |
41afff9a | 15488 | @cindex @file{sparc-stub.c} |
104c1213 JM |
15489 | @cindex Sparc |
15490 | For @sc{sparc} architectures. | |
15491 | ||
15492 | @item sparcl-stub.c | |
41afff9a | 15493 | @cindex @file{sparcl-stub.c} |
104c1213 JM |
15494 | @cindex Fujitsu |
15495 | @cindex SparcLite | |
15496 | For Fujitsu @sc{sparclite} architectures. | |
15497 | ||
15498 | @end table | |
15499 | ||
15500 | The @file{README} file in the @value{GDBN} distribution may list other | |
15501 | recently added stubs. | |
15502 | ||
15503 | @menu | |
15504 | * Stub Contents:: What the stub can do for you | |
15505 | * Bootstrapping:: What you must do for the stub | |
15506 | * Debug Session:: Putting it all together | |
104c1213 JM |
15507 | @end menu |
15508 | ||
6d2ebf8b | 15509 | @node Stub Contents |
79a6e687 | 15510 | @subsection What the Stub Can Do for You |
104c1213 JM |
15511 | |
15512 | @cindex remote serial stub | |
15513 | The debugging stub for your architecture supplies these three | |
15514 | subroutines: | |
15515 | ||
15516 | @table @code | |
15517 | @item set_debug_traps | |
4644b6e3 | 15518 | @findex set_debug_traps |
104c1213 JM |
15519 | @cindex remote serial stub, initialization |
15520 | This routine arranges for @code{handle_exception} to run when your | |
15521 | program stops. You must call this subroutine explicitly near the | |
15522 | beginning of your program. | |
15523 | ||
15524 | @item handle_exception | |
4644b6e3 | 15525 | @findex handle_exception |
104c1213 JM |
15526 | @cindex remote serial stub, main routine |
15527 | This is the central workhorse, but your program never calls it | |
15528 | explicitly---the setup code arranges for @code{handle_exception} to | |
15529 | run when a trap is triggered. | |
15530 | ||
15531 | @code{handle_exception} takes control when your program stops during | |
15532 | execution (for example, on a breakpoint), and mediates communications | |
15533 | with @value{GDBN} on the host machine. This is where the communications | |
15534 | protocol is implemented; @code{handle_exception} acts as the @value{GDBN} | |
d4f3574e | 15535 | representative on the target machine. It begins by sending summary |
104c1213 JM |
15536 | information on the state of your program, then continues to execute, |
15537 | retrieving and transmitting any information @value{GDBN} needs, until you | |
15538 | execute a @value{GDBN} command that makes your program resume; at that point, | |
15539 | @code{handle_exception} returns control to your own code on the target | |
5d161b24 | 15540 | machine. |
104c1213 JM |
15541 | |
15542 | @item breakpoint | |
15543 | @cindex @code{breakpoint} subroutine, remote | |
15544 | Use this auxiliary subroutine to make your program contain a | |
15545 | breakpoint. Depending on the particular situation, this may be the only | |
15546 | way for @value{GDBN} to get control. For instance, if your target | |
15547 | machine has some sort of interrupt button, you won't need to call this; | |
15548 | pressing the interrupt button transfers control to | |
15549 | @code{handle_exception}---in effect, to @value{GDBN}. On some machines, | |
15550 | simply receiving characters on the serial port may also trigger a trap; | |
15551 | again, in that situation, you don't need to call @code{breakpoint} from | |
15552 | your own program---simply running @samp{target remote} from the host | |
5d161b24 | 15553 | @value{GDBN} session gets control. |
104c1213 JM |
15554 | |
15555 | Call @code{breakpoint} if none of these is true, or if you simply want | |
15556 | to make certain your program stops at a predetermined point for the | |
15557 | start of your debugging session. | |
15558 | @end table | |
15559 | ||
6d2ebf8b | 15560 | @node Bootstrapping |
79a6e687 | 15561 | @subsection What You Must Do for the Stub |
104c1213 JM |
15562 | |
15563 | @cindex remote stub, support routines | |
15564 | The debugging stubs that come with @value{GDBN} are set up for a particular | |
15565 | chip architecture, but they have no information about the rest of your | |
15566 | debugging target machine. | |
15567 | ||
15568 | First of all you need to tell the stub how to communicate with the | |
15569 | serial port. | |
15570 | ||
15571 | @table @code | |
15572 | @item int getDebugChar() | |
4644b6e3 | 15573 | @findex getDebugChar |
104c1213 JM |
15574 | Write this subroutine to read a single character from the serial port. |
15575 | It may be identical to @code{getchar} for your target system; a | |
15576 | different name is used to allow you to distinguish the two if you wish. | |
15577 | ||
15578 | @item void putDebugChar(int) | |
4644b6e3 | 15579 | @findex putDebugChar |
104c1213 | 15580 | Write this subroutine to write a single character to the serial port. |
5d161b24 | 15581 | It may be identical to @code{putchar} for your target system; a |
104c1213 JM |
15582 | different name is used to allow you to distinguish the two if you wish. |
15583 | @end table | |
15584 | ||
15585 | @cindex control C, and remote debugging | |
15586 | @cindex interrupting remote targets | |
15587 | If you want @value{GDBN} to be able to stop your program while it is | |
15588 | running, you need to use an interrupt-driven serial driver, and arrange | |
15589 | for it to stop when it receives a @code{^C} (@samp{\003}, the control-C | |
15590 | character). That is the character which @value{GDBN} uses to tell the | |
15591 | remote system to stop. | |
15592 | ||
15593 | Getting the debugging target to return the proper status to @value{GDBN} | |
15594 | probably requires changes to the standard stub; one quick and dirty way | |
15595 | is to just execute a breakpoint instruction (the ``dirty'' part is that | |
15596 | @value{GDBN} reports a @code{SIGTRAP} instead of a @code{SIGINT}). | |
15597 | ||
15598 | Other routines you need to supply are: | |
15599 | ||
15600 | @table @code | |
15601 | @item void exceptionHandler (int @var{exception_number}, void *@var{exception_address}) | |
4644b6e3 | 15602 | @findex exceptionHandler |
104c1213 JM |
15603 | Write this function to install @var{exception_address} in the exception |
15604 | handling tables. You need to do this because the stub does not have any | |
15605 | way of knowing what the exception handling tables on your target system | |
15606 | are like (for example, the processor's table might be in @sc{rom}, | |
15607 | containing entries which point to a table in @sc{ram}). | |
15608 | @var{exception_number} is the exception number which should be changed; | |
15609 | its meaning is architecture-dependent (for example, different numbers | |
15610 | might represent divide by zero, misaligned access, etc). When this | |
15611 | exception occurs, control should be transferred directly to | |
15612 | @var{exception_address}, and the processor state (stack, registers, | |
15613 | and so on) should be just as it is when a processor exception occurs. So if | |
15614 | you want to use a jump instruction to reach @var{exception_address}, it | |
15615 | should be a simple jump, not a jump to subroutine. | |
15616 | ||
15617 | For the 386, @var{exception_address} should be installed as an interrupt | |
15618 | gate so that interrupts are masked while the handler runs. The gate | |
15619 | should be at privilege level 0 (the most privileged level). The | |
15620 | @sc{sparc} and 68k stubs are able to mask interrupts themselves without | |
15621 | help from @code{exceptionHandler}. | |
15622 | ||
15623 | @item void flush_i_cache() | |
4644b6e3 | 15624 | @findex flush_i_cache |
d4f3574e | 15625 | On @sc{sparc} and @sc{sparclite} only, write this subroutine to flush the |
104c1213 JM |
15626 | instruction cache, if any, on your target machine. If there is no |
15627 | instruction cache, this subroutine may be a no-op. | |
15628 | ||
15629 | On target machines that have instruction caches, @value{GDBN} requires this | |
15630 | function to make certain that the state of your program is stable. | |
15631 | @end table | |
15632 | ||
15633 | @noindent | |
15634 | You must also make sure this library routine is available: | |
15635 | ||
15636 | @table @code | |
15637 | @item void *memset(void *, int, int) | |
4644b6e3 | 15638 | @findex memset |
104c1213 JM |
15639 | This is the standard library function @code{memset} that sets an area of |
15640 | memory to a known value. If you have one of the free versions of | |
15641 | @code{libc.a}, @code{memset} can be found there; otherwise, you must | |
15642 | either obtain it from your hardware manufacturer, or write your own. | |
15643 | @end table | |
15644 | ||
15645 | If you do not use the GNU C compiler, you may need other standard | |
15646 | library subroutines as well; this varies from one stub to another, | |
15647 | but in general the stubs are likely to use any of the common library | |
e22ea452 | 15648 | subroutines which @code{@value{NGCC}} generates as inline code. |
104c1213 JM |
15649 | |
15650 | ||
6d2ebf8b | 15651 | @node Debug Session |
79a6e687 | 15652 | @subsection Putting it All Together |
104c1213 JM |
15653 | |
15654 | @cindex remote serial debugging summary | |
15655 | In summary, when your program is ready to debug, you must follow these | |
15656 | steps. | |
15657 | ||
15658 | @enumerate | |
15659 | @item | |
6d2ebf8b | 15660 | Make sure you have defined the supporting low-level routines |
79a6e687 | 15661 | (@pxref{Bootstrapping,,What You Must Do for the Stub}): |
104c1213 JM |
15662 | @display |
15663 | @code{getDebugChar}, @code{putDebugChar}, | |
15664 | @code{flush_i_cache}, @code{memset}, @code{exceptionHandler}. | |
15665 | @end display | |
15666 | ||
15667 | @item | |
15668 | Insert these lines near the top of your program: | |
15669 | ||
474c8240 | 15670 | @smallexample |
104c1213 JM |
15671 | set_debug_traps(); |
15672 | breakpoint(); | |
474c8240 | 15673 | @end smallexample |
104c1213 JM |
15674 | |
15675 | @item | |
15676 | For the 680x0 stub only, you need to provide a variable called | |
15677 | @code{exceptionHook}. Normally you just use: | |
15678 | ||
474c8240 | 15679 | @smallexample |
104c1213 | 15680 | void (*exceptionHook)() = 0; |
474c8240 | 15681 | @end smallexample |
104c1213 | 15682 | |
d4f3574e | 15683 | @noindent |
104c1213 | 15684 | but if before calling @code{set_debug_traps}, you set it to point to a |
598ca718 | 15685 | function in your program, that function is called when |
104c1213 JM |
15686 | @code{@value{GDBN}} continues after stopping on a trap (for example, bus |
15687 | error). The function indicated by @code{exceptionHook} is called with | |
15688 | one parameter: an @code{int} which is the exception number. | |
15689 | ||
15690 | @item | |
15691 | Compile and link together: your program, the @value{GDBN} debugging stub for | |
15692 | your target architecture, and the supporting subroutines. | |
15693 | ||
15694 | @item | |
15695 | Make sure you have a serial connection between your target machine and | |
15696 | the @value{GDBN} host, and identify the serial port on the host. | |
15697 | ||
15698 | @item | |
15699 | @c The "remote" target now provides a `load' command, so we should | |
15700 | @c document that. FIXME. | |
15701 | Download your program to your target machine (or get it there by | |
15702 | whatever means the manufacturer provides), and start it. | |
15703 | ||
15704 | @item | |
07f31aa6 | 15705 | Start @value{GDBN} on the host, and connect to the target |
79a6e687 | 15706 | (@pxref{Connecting,,Connecting to a Remote Target}). |
9db8d71f | 15707 | |
104c1213 JM |
15708 | @end enumerate |
15709 | ||
8e04817f AC |
15710 | @node Configurations |
15711 | @chapter Configuration-Specific Information | |
104c1213 | 15712 | |
8e04817f AC |
15713 | While nearly all @value{GDBN} commands are available for all native and |
15714 | cross versions of the debugger, there are some exceptions. This chapter | |
15715 | describes things that are only available in certain configurations. | |
104c1213 | 15716 | |
8e04817f AC |
15717 | There are three major categories of configurations: native |
15718 | configurations, where the host and target are the same, embedded | |
15719 | operating system configurations, which are usually the same for several | |
15720 | different processor architectures, and bare embedded processors, which | |
15721 | are quite different from each other. | |
104c1213 | 15722 | |
8e04817f AC |
15723 | @menu |
15724 | * Native:: | |
15725 | * Embedded OS:: | |
15726 | * Embedded Processors:: | |
15727 | * Architectures:: | |
15728 | @end menu | |
104c1213 | 15729 | |
8e04817f AC |
15730 | @node Native |
15731 | @section Native | |
104c1213 | 15732 | |
8e04817f AC |
15733 | This section describes details specific to particular native |
15734 | configurations. | |
6cf7e474 | 15735 | |
8e04817f AC |
15736 | @menu |
15737 | * HP-UX:: HP-UX | |
7561d450 | 15738 | * BSD libkvm Interface:: Debugging BSD kernel memory images |
8e04817f AC |
15739 | * SVR4 Process Information:: SVR4 process information |
15740 | * DJGPP Native:: Features specific to the DJGPP port | |
78c47bea | 15741 | * Cygwin Native:: Features specific to the Cygwin port |
14d6dd68 | 15742 | * Hurd Native:: Features specific to @sc{gnu} Hurd |
a64548ea | 15743 | * Neutrino:: Features specific to QNX Neutrino |
a80b95ba | 15744 | * Darwin:: Features specific to Darwin |
8e04817f | 15745 | @end menu |
6cf7e474 | 15746 | |
8e04817f AC |
15747 | @node HP-UX |
15748 | @subsection HP-UX | |
104c1213 | 15749 | |
8e04817f AC |
15750 | On HP-UX systems, if you refer to a function or variable name that |
15751 | begins with a dollar sign, @value{GDBN} searches for a user or system | |
15752 | name first, before it searches for a convenience variable. | |
104c1213 | 15753 | |
9c16f35a | 15754 | |
7561d450 MK |
15755 | @node BSD libkvm Interface |
15756 | @subsection BSD libkvm Interface | |
15757 | ||
15758 | @cindex libkvm | |
15759 | @cindex kernel memory image | |
15760 | @cindex kernel crash dump | |
15761 | ||
15762 | BSD-derived systems (FreeBSD/NetBSD/OpenBSD) have a kernel memory | |
15763 | interface that provides a uniform interface for accessing kernel virtual | |
15764 | memory images, including live systems and crash dumps. @value{GDBN} | |
15765 | uses this interface to allow you to debug live kernels and kernel crash | |
15766 | dumps on many native BSD configurations. This is implemented as a | |
15767 | special @code{kvm} debugging target. For debugging a live system, load | |
15768 | the currently running kernel into @value{GDBN} and connect to the | |
15769 | @code{kvm} target: | |
15770 | ||
15771 | @smallexample | |
15772 | (@value{GDBP}) @b{target kvm} | |
15773 | @end smallexample | |
15774 | ||
15775 | For debugging crash dumps, provide the file name of the crash dump as an | |
15776 | argument: | |
15777 | ||
15778 | @smallexample | |
15779 | (@value{GDBP}) @b{target kvm /var/crash/bsd.0} | |
15780 | @end smallexample | |
15781 | ||
15782 | Once connected to the @code{kvm} target, the following commands are | |
15783 | available: | |
15784 | ||
15785 | @table @code | |
15786 | @kindex kvm | |
15787 | @item kvm pcb | |
721c2651 | 15788 | Set current context from the @dfn{Process Control Block} (PCB) address. |
7561d450 MK |
15789 | |
15790 | @item kvm proc | |
15791 | Set current context from proc address. This command isn't available on | |
15792 | modern FreeBSD systems. | |
15793 | @end table | |
15794 | ||
8e04817f | 15795 | @node SVR4 Process Information |
79a6e687 | 15796 | @subsection SVR4 Process Information |
60bf7e09 EZ |
15797 | @cindex /proc |
15798 | @cindex examine process image | |
15799 | @cindex process info via @file{/proc} | |
104c1213 | 15800 | |
60bf7e09 EZ |
15801 | Many versions of SVR4 and compatible systems provide a facility called |
15802 | @samp{/proc} that can be used to examine the image of a running | |
15803 | process using file-system subroutines. If @value{GDBN} is configured | |
15804 | for an operating system with this facility, the command @code{info | |
15805 | proc} is available to report information about the process running | |
15806 | your program, or about any process running on your system. @code{info | |
15807 | proc} works only on SVR4 systems that include the @code{procfs} code. | |
15808 | This includes, as of this writing, @sc{gnu}/Linux, OSF/1 (Digital | |
15809 | Unix), Solaris, Irix, and Unixware, but not HP-UX, for example. | |
104c1213 | 15810 | |
8e04817f AC |
15811 | @table @code |
15812 | @kindex info proc | |
60bf7e09 | 15813 | @cindex process ID |
8e04817f | 15814 | @item info proc |
60bf7e09 EZ |
15815 | @itemx info proc @var{process-id} |
15816 | Summarize available information about any running process. If a | |
15817 | process ID is specified by @var{process-id}, display information about | |
15818 | that process; otherwise display information about the program being | |
15819 | debugged. The summary includes the debugged process ID, the command | |
15820 | line used to invoke it, its current working directory, and its | |
15821 | executable file's absolute file name. | |
15822 | ||
15823 | On some systems, @var{process-id} can be of the form | |
15824 | @samp{[@var{pid}]/@var{tid}} which specifies a certain thread ID | |
15825 | within a process. If the optional @var{pid} part is missing, it means | |
15826 | a thread from the process being debugged (the leading @samp{/} still | |
15827 | needs to be present, or else @value{GDBN} will interpret the number as | |
15828 | a process ID rather than a thread ID). | |
6cf7e474 | 15829 | |
8e04817f | 15830 | @item info proc mappings |
60bf7e09 EZ |
15831 | @cindex memory address space mappings |
15832 | Report the memory address space ranges accessible in the program, with | |
15833 | information on whether the process has read, write, or execute access | |
15834 | rights to each range. On @sc{gnu}/Linux systems, each memory range | |
15835 | includes the object file which is mapped to that range, instead of the | |
15836 | memory access rights to that range. | |
15837 | ||
15838 | @item info proc stat | |
15839 | @itemx info proc status | |
15840 | @cindex process detailed status information | |
15841 | These subcommands are specific to @sc{gnu}/Linux systems. They show | |
15842 | the process-related information, including the user ID and group ID; | |
15843 | how many threads are there in the process; its virtual memory usage; | |
15844 | the signals that are pending, blocked, and ignored; its TTY; its | |
15845 | consumption of system and user time; its stack size; its @samp{nice} | |
2eecc4ab | 15846 | value; etc. For more information, see the @samp{proc} man page |
60bf7e09 EZ |
15847 | (type @kbd{man 5 proc} from your shell prompt). |
15848 | ||
15849 | @item info proc all | |
15850 | Show all the information about the process described under all of the | |
15851 | above @code{info proc} subcommands. | |
15852 | ||
8e04817f AC |
15853 | @ignore |
15854 | @comment These sub-options of 'info proc' were not included when | |
15855 | @comment procfs.c was re-written. Keep their descriptions around | |
15856 | @comment against the day when someone finds the time to put them back in. | |
15857 | @kindex info proc times | |
15858 | @item info proc times | |
15859 | Starting time, user CPU time, and system CPU time for your program and | |
15860 | its children. | |
6cf7e474 | 15861 | |
8e04817f AC |
15862 | @kindex info proc id |
15863 | @item info proc id | |
15864 | Report on the process IDs related to your program: its own process ID, | |
15865 | the ID of its parent, the process group ID, and the session ID. | |
8e04817f | 15866 | @end ignore |
721c2651 EZ |
15867 | |
15868 | @item set procfs-trace | |
15869 | @kindex set procfs-trace | |
15870 | @cindex @code{procfs} API calls | |
15871 | This command enables and disables tracing of @code{procfs} API calls. | |
15872 | ||
15873 | @item show procfs-trace | |
15874 | @kindex show procfs-trace | |
15875 | Show the current state of @code{procfs} API call tracing. | |
15876 | ||
15877 | @item set procfs-file @var{file} | |
15878 | @kindex set procfs-file | |
15879 | Tell @value{GDBN} to write @code{procfs} API trace to the named | |
15880 | @var{file}. @value{GDBN} appends the trace info to the previous | |
15881 | contents of the file. The default is to display the trace on the | |
15882 | standard output. | |
15883 | ||
15884 | @item show procfs-file | |
15885 | @kindex show procfs-file | |
15886 | Show the file to which @code{procfs} API trace is written. | |
15887 | ||
15888 | @item proc-trace-entry | |
15889 | @itemx proc-trace-exit | |
15890 | @itemx proc-untrace-entry | |
15891 | @itemx proc-untrace-exit | |
15892 | @kindex proc-trace-entry | |
15893 | @kindex proc-trace-exit | |
15894 | @kindex proc-untrace-entry | |
15895 | @kindex proc-untrace-exit | |
15896 | These commands enable and disable tracing of entries into and exits | |
15897 | from the @code{syscall} interface. | |
15898 | ||
15899 | @item info pidlist | |
15900 | @kindex info pidlist | |
15901 | @cindex process list, QNX Neutrino | |
15902 | For QNX Neutrino only, this command displays the list of all the | |
15903 | processes and all the threads within each process. | |
15904 | ||
15905 | @item info meminfo | |
15906 | @kindex info meminfo | |
15907 | @cindex mapinfo list, QNX Neutrino | |
15908 | For QNX Neutrino only, this command displays the list of all mapinfos. | |
8e04817f | 15909 | @end table |
104c1213 | 15910 | |
8e04817f AC |
15911 | @node DJGPP Native |
15912 | @subsection Features for Debugging @sc{djgpp} Programs | |
15913 | @cindex @sc{djgpp} debugging | |
15914 | @cindex native @sc{djgpp} debugging | |
15915 | @cindex MS-DOS-specific commands | |
104c1213 | 15916 | |
514c4d71 EZ |
15917 | @cindex DPMI |
15918 | @sc{djgpp} is a port of the @sc{gnu} development tools to MS-DOS and | |
8e04817f AC |
15919 | MS-Windows. @sc{djgpp} programs are 32-bit protected-mode programs |
15920 | that use the @dfn{DPMI} (DOS Protected-Mode Interface) API to run on | |
15921 | top of real-mode DOS systems and their emulations. | |
104c1213 | 15922 | |
8e04817f AC |
15923 | @value{GDBN} supports native debugging of @sc{djgpp} programs, and |
15924 | defines a few commands specific to the @sc{djgpp} port. This | |
15925 | subsection describes those commands. | |
104c1213 | 15926 | |
8e04817f AC |
15927 | @table @code |
15928 | @kindex info dos | |
15929 | @item info dos | |
15930 | This is a prefix of @sc{djgpp}-specific commands which print | |
15931 | information about the target system and important OS structures. | |
f1251bdd | 15932 | |
8e04817f AC |
15933 | @kindex sysinfo |
15934 | @cindex MS-DOS system info | |
15935 | @cindex free memory information (MS-DOS) | |
15936 | @item info dos sysinfo | |
15937 | This command displays assorted information about the underlying | |
15938 | platform: the CPU type and features, the OS version and flavor, the | |
15939 | DPMI version, and the available conventional and DPMI memory. | |
104c1213 | 15940 | |
8e04817f AC |
15941 | @cindex GDT |
15942 | @cindex LDT | |
15943 | @cindex IDT | |
15944 | @cindex segment descriptor tables | |
15945 | @cindex descriptor tables display | |
15946 | @item info dos gdt | |
15947 | @itemx info dos ldt | |
15948 | @itemx info dos idt | |
15949 | These 3 commands display entries from, respectively, Global, Local, | |
15950 | and Interrupt Descriptor Tables (GDT, LDT, and IDT). The descriptor | |
15951 | tables are data structures which store a descriptor for each segment | |
15952 | that is currently in use. The segment's selector is an index into a | |
15953 | descriptor table; the table entry for that index holds the | |
15954 | descriptor's base address and limit, and its attributes and access | |
15955 | rights. | |
104c1213 | 15956 | |
8e04817f AC |
15957 | A typical @sc{djgpp} program uses 3 segments: a code segment, a data |
15958 | segment (used for both data and the stack), and a DOS segment (which | |
15959 | allows access to DOS/BIOS data structures and absolute addresses in | |
15960 | conventional memory). However, the DPMI host will usually define | |
15961 | additional segments in order to support the DPMI environment. | |
d4f3574e | 15962 | |
8e04817f AC |
15963 | @cindex garbled pointers |
15964 | These commands allow to display entries from the descriptor tables. | |
15965 | Without an argument, all entries from the specified table are | |
15966 | displayed. An argument, which should be an integer expression, means | |
15967 | display a single entry whose index is given by the argument. For | |
15968 | example, here's a convenient way to display information about the | |
15969 | debugged program's data segment: | |
104c1213 | 15970 | |
8e04817f AC |
15971 | @smallexample |
15972 | @exdent @code{(@value{GDBP}) info dos ldt $ds} | |
15973 | @exdent @code{0x13f: base=0x11970000 limit=0x0009ffff 32-Bit Data (Read/Write, Exp-up)} | |
15974 | @end smallexample | |
104c1213 | 15975 | |
8e04817f AC |
15976 | @noindent |
15977 | This comes in handy when you want to see whether a pointer is outside | |
15978 | the data segment's limit (i.e.@: @dfn{garbled}). | |
104c1213 | 15979 | |
8e04817f AC |
15980 | @cindex page tables display (MS-DOS) |
15981 | @item info dos pde | |
15982 | @itemx info dos pte | |
15983 | These two commands display entries from, respectively, the Page | |
15984 | Directory and the Page Tables. Page Directories and Page Tables are | |
15985 | data structures which control how virtual memory addresses are mapped | |
15986 | into physical addresses. A Page Table includes an entry for every | |
15987 | page of memory that is mapped into the program's address space; there | |
15988 | may be several Page Tables, each one holding up to 4096 entries. A | |
15989 | Page Directory has up to 4096 entries, one each for every Page Table | |
15990 | that is currently in use. | |
104c1213 | 15991 | |
8e04817f AC |
15992 | Without an argument, @kbd{info dos pde} displays the entire Page |
15993 | Directory, and @kbd{info dos pte} displays all the entries in all of | |
15994 | the Page Tables. An argument, an integer expression, given to the | |
15995 | @kbd{info dos pde} command means display only that entry from the Page | |
15996 | Directory table. An argument given to the @kbd{info dos pte} command | |
15997 | means display entries from a single Page Table, the one pointed to by | |
15998 | the specified entry in the Page Directory. | |
104c1213 | 15999 | |
8e04817f AC |
16000 | @cindex direct memory access (DMA) on MS-DOS |
16001 | These commands are useful when your program uses @dfn{DMA} (Direct | |
16002 | Memory Access), which needs physical addresses to program the DMA | |
16003 | controller. | |
104c1213 | 16004 | |
8e04817f | 16005 | These commands are supported only with some DPMI servers. |
104c1213 | 16006 | |
8e04817f AC |
16007 | @cindex physical address from linear address |
16008 | @item info dos address-pte @var{addr} | |
16009 | This command displays the Page Table entry for a specified linear | |
514c4d71 EZ |
16010 | address. The argument @var{addr} is a linear address which should |
16011 | already have the appropriate segment's base address added to it, | |
16012 | because this command accepts addresses which may belong to @emph{any} | |
16013 | segment. For example, here's how to display the Page Table entry for | |
16014 | the page where a variable @code{i} is stored: | |
104c1213 | 16015 | |
b383017d | 16016 | @smallexample |
8e04817f AC |
16017 | @exdent @code{(@value{GDBP}) info dos address-pte __djgpp_base_address + (char *)&i} |
16018 | @exdent @code{Page Table entry for address 0x11a00d30:} | |
b383017d | 16019 | @exdent @code{Base=0x02698000 Dirty Acc. Not-Cached Write-Back Usr Read-Write +0xd30} |
8e04817f | 16020 | @end smallexample |
104c1213 | 16021 | |
8e04817f AC |
16022 | @noindent |
16023 | This says that @code{i} is stored at offset @code{0xd30} from the page | |
514c4d71 | 16024 | whose physical base address is @code{0x02698000}, and shows all the |
8e04817f | 16025 | attributes of that page. |
104c1213 | 16026 | |
8e04817f AC |
16027 | Note that you must cast the addresses of variables to a @code{char *}, |
16028 | since otherwise the value of @code{__djgpp_base_address}, the base | |
16029 | address of all variables and functions in a @sc{djgpp} program, will | |
16030 | be added using the rules of C pointer arithmetics: if @code{i} is | |
16031 | declared an @code{int}, @value{GDBN} will add 4 times the value of | |
16032 | @code{__djgpp_base_address} to the address of @code{i}. | |
104c1213 | 16033 | |
8e04817f AC |
16034 | Here's another example, it displays the Page Table entry for the |
16035 | transfer buffer: | |
104c1213 | 16036 | |
8e04817f AC |
16037 | @smallexample |
16038 | @exdent @code{(@value{GDBP}) info dos address-pte *((unsigned *)&_go32_info_block + 3)} | |
16039 | @exdent @code{Page Table entry for address 0x29110:} | |
16040 | @exdent @code{Base=0x00029000 Dirty Acc. Not-Cached Write-Back Usr Read-Write +0x110} | |
16041 | @end smallexample | |
104c1213 | 16042 | |
8e04817f AC |
16043 | @noindent |
16044 | (The @code{+ 3} offset is because the transfer buffer's address is the | |
514c4d71 EZ |
16045 | 3rd member of the @code{_go32_info_block} structure.) The output |
16046 | clearly shows that this DPMI server maps the addresses in conventional | |
16047 | memory 1:1, i.e.@: the physical (@code{0x00029000} + @code{0x110}) and | |
16048 | linear (@code{0x29110}) addresses are identical. | |
104c1213 | 16049 | |
8e04817f AC |
16050 | This command is supported only with some DPMI servers. |
16051 | @end table | |
104c1213 | 16052 | |
c45da7e6 | 16053 | @cindex DOS serial data link, remote debugging |
a8f24a35 EZ |
16054 | In addition to native debugging, the DJGPP port supports remote |
16055 | debugging via a serial data link. The following commands are specific | |
16056 | to remote serial debugging in the DJGPP port of @value{GDBN}. | |
16057 | ||
16058 | @table @code | |
16059 | @kindex set com1base | |
16060 | @kindex set com1irq | |
16061 | @kindex set com2base | |
16062 | @kindex set com2irq | |
16063 | @kindex set com3base | |
16064 | @kindex set com3irq | |
16065 | @kindex set com4base | |
16066 | @kindex set com4irq | |
16067 | @item set com1base @var{addr} | |
16068 | This command sets the base I/O port address of the @file{COM1} serial | |
16069 | port. | |
16070 | ||
16071 | @item set com1irq @var{irq} | |
16072 | This command sets the @dfn{Interrupt Request} (@code{IRQ}) line to use | |
16073 | for the @file{COM1} serial port. | |
16074 | ||
16075 | There are similar commands @samp{set com2base}, @samp{set com3irq}, | |
16076 | etc.@: for setting the port address and the @code{IRQ} lines for the | |
16077 | other 3 COM ports. | |
16078 | ||
16079 | @kindex show com1base | |
16080 | @kindex show com1irq | |
16081 | @kindex show com2base | |
16082 | @kindex show com2irq | |
16083 | @kindex show com3base | |
16084 | @kindex show com3irq | |
16085 | @kindex show com4base | |
16086 | @kindex show com4irq | |
16087 | The related commands @samp{show com1base}, @samp{show com1irq} etc.@: | |
16088 | display the current settings of the base address and the @code{IRQ} | |
16089 | lines used by the COM ports. | |
c45da7e6 EZ |
16090 | |
16091 | @item info serial | |
16092 | @kindex info serial | |
16093 | @cindex DOS serial port status | |
16094 | This command prints the status of the 4 DOS serial ports. For each | |
16095 | port, it prints whether it's active or not, its I/O base address and | |
16096 | IRQ number, whether it uses a 16550-style FIFO, its baudrate, and the | |
16097 | counts of various errors encountered so far. | |
a8f24a35 EZ |
16098 | @end table |
16099 | ||
16100 | ||
78c47bea | 16101 | @node Cygwin Native |
79a6e687 | 16102 | @subsection Features for Debugging MS Windows PE Executables |
78c47bea PM |
16103 | @cindex MS Windows debugging |
16104 | @cindex native Cygwin debugging | |
16105 | @cindex Cygwin-specific commands | |
16106 | ||
be448670 | 16107 | @value{GDBN} supports native debugging of MS Windows programs, including |
cbb8f428 EZ |
16108 | DLLs with and without symbolic debugging information. |
16109 | ||
16110 | @cindex Ctrl-BREAK, MS-Windows | |
16111 | @cindex interrupt debuggee on MS-Windows | |
16112 | MS-Windows programs that call @code{SetConsoleMode} to switch off the | |
16113 | special meaning of the @samp{Ctrl-C} keystroke cannot be interrupted | |
16114 | by typing @kbd{C-c}. For this reason, @value{GDBN} on MS-Windows | |
16115 | supports @kbd{C-@key{BREAK}} as an alternative interrupt key | |
16116 | sequence, which can be used to interrupt the debuggee even if it | |
16117 | ignores @kbd{C-c}. | |
16118 | ||
16119 | There are various additional Cygwin-specific commands, described in | |
16120 | this section. Working with DLLs that have no debugging symbols is | |
16121 | described in @ref{Non-debug DLL Symbols}. | |
78c47bea PM |
16122 | |
16123 | @table @code | |
16124 | @kindex info w32 | |
16125 | @item info w32 | |
db2e3e2e | 16126 | This is a prefix of MS Windows-specific commands which print |
78c47bea PM |
16127 | information about the target system and important OS structures. |
16128 | ||
16129 | @item info w32 selector | |
16130 | This command displays information returned by | |
16131 | the Win32 API @code{GetThreadSelectorEntry} function. | |
16132 | It takes an optional argument that is evaluated to | |
16133 | a long value to give the information about this given selector. | |
16134 | Without argument, this command displays information | |
d3e8051b | 16135 | about the six segment registers. |
78c47bea PM |
16136 | |
16137 | @kindex info dll | |
16138 | @item info dll | |
db2e3e2e | 16139 | This is a Cygwin-specific alias of @code{info shared}. |
78c47bea PM |
16140 | |
16141 | @kindex dll-symbols | |
16142 | @item dll-symbols | |
16143 | This command loads symbols from a dll similarly to | |
16144 | add-sym command but without the need to specify a base address. | |
16145 | ||
be90c084 | 16146 | @kindex set cygwin-exceptions |
e16b02ee EZ |
16147 | @cindex debugging the Cygwin DLL |
16148 | @cindex Cygwin DLL, debugging | |
be90c084 | 16149 | @item set cygwin-exceptions @var{mode} |
e16b02ee EZ |
16150 | If @var{mode} is @code{on}, @value{GDBN} will break on exceptions that |
16151 | happen inside the Cygwin DLL. If @var{mode} is @code{off}, | |
16152 | @value{GDBN} will delay recognition of exceptions, and may ignore some | |
16153 | exceptions which seem to be caused by internal Cygwin DLL | |
16154 | ``bookkeeping''. This option is meant primarily for debugging the | |
16155 | Cygwin DLL itself; the default value is @code{off} to avoid annoying | |
16156 | @value{GDBN} users with false @code{SIGSEGV} signals. | |
be90c084 CF |
16157 | |
16158 | @kindex show cygwin-exceptions | |
16159 | @item show cygwin-exceptions | |
e16b02ee EZ |
16160 | Displays whether @value{GDBN} will break on exceptions that happen |
16161 | inside the Cygwin DLL itself. | |
be90c084 | 16162 | |
b383017d | 16163 | @kindex set new-console |
78c47bea | 16164 | @item set new-console @var{mode} |
b383017d | 16165 | If @var{mode} is @code{on} the debuggee will |
78c47bea PM |
16166 | be started in a new console on next start. |
16167 | If @var{mode} is @code{off}i, the debuggee will | |
16168 | be started in the same console as the debugger. | |
16169 | ||
16170 | @kindex show new-console | |
16171 | @item show new-console | |
16172 | Displays whether a new console is used | |
16173 | when the debuggee is started. | |
16174 | ||
16175 | @kindex set new-group | |
16176 | @item set new-group @var{mode} | |
16177 | This boolean value controls whether the debuggee should | |
16178 | start a new group or stay in the same group as the debugger. | |
16179 | This affects the way the Windows OS handles | |
c8aa23ab | 16180 | @samp{Ctrl-C}. |
78c47bea PM |
16181 | |
16182 | @kindex show new-group | |
16183 | @item show new-group | |
16184 | Displays current value of new-group boolean. | |
16185 | ||
16186 | @kindex set debugevents | |
16187 | @item set debugevents | |
219eec71 EZ |
16188 | This boolean value adds debug output concerning kernel events related |
16189 | to the debuggee seen by the debugger. This includes events that | |
16190 | signal thread and process creation and exit, DLL loading and | |
16191 | unloading, console interrupts, and debugging messages produced by the | |
16192 | Windows @code{OutputDebugString} API call. | |
78c47bea PM |
16193 | |
16194 | @kindex set debugexec | |
16195 | @item set debugexec | |
b383017d | 16196 | This boolean value adds debug output concerning execute events |
219eec71 | 16197 | (such as resume thread) seen by the debugger. |
78c47bea PM |
16198 | |
16199 | @kindex set debugexceptions | |
16200 | @item set debugexceptions | |
219eec71 EZ |
16201 | This boolean value adds debug output concerning exceptions in the |
16202 | debuggee seen by the debugger. | |
78c47bea PM |
16203 | |
16204 | @kindex set debugmemory | |
16205 | @item set debugmemory | |
219eec71 EZ |
16206 | This boolean value adds debug output concerning debuggee memory reads |
16207 | and writes by the debugger. | |
78c47bea PM |
16208 | |
16209 | @kindex set shell | |
16210 | @item set shell | |
16211 | This boolean values specifies whether the debuggee is called | |
16212 | via a shell or directly (default value is on). | |
16213 | ||
16214 | @kindex show shell | |
16215 | @item show shell | |
16216 | Displays if the debuggee will be started with a shell. | |
16217 | ||
16218 | @end table | |
16219 | ||
be448670 | 16220 | @menu |
79a6e687 | 16221 | * Non-debug DLL Symbols:: Support for DLLs without debugging symbols |
be448670 CF |
16222 | @end menu |
16223 | ||
79a6e687 BW |
16224 | @node Non-debug DLL Symbols |
16225 | @subsubsection Support for DLLs without Debugging Symbols | |
be448670 CF |
16226 | @cindex DLLs with no debugging symbols |
16227 | @cindex Minimal symbols and DLLs | |
16228 | ||
16229 | Very often on windows, some of the DLLs that your program relies on do | |
16230 | not include symbolic debugging information (for example, | |
db2e3e2e | 16231 | @file{kernel32.dll}). When @value{GDBN} doesn't recognize any debugging |
be448670 | 16232 | symbols in a DLL, it relies on the minimal amount of symbolic |
db2e3e2e | 16233 | information contained in the DLL's export table. This section |
be448670 CF |
16234 | describes working with such symbols, known internally to @value{GDBN} as |
16235 | ``minimal symbols''. | |
16236 | ||
16237 | Note that before the debugged program has started execution, no DLLs | |
db2e3e2e | 16238 | will have been loaded. The easiest way around this problem is simply to |
be448670 | 16239 | start the program --- either by setting a breakpoint or letting the |
db2e3e2e | 16240 | program run once to completion. It is also possible to force |
be448670 | 16241 | @value{GDBN} to load a particular DLL before starting the executable --- |
12c27660 | 16242 | see the shared library information in @ref{Files}, or the |
db2e3e2e | 16243 | @code{dll-symbols} command in @ref{Cygwin Native}. Currently, |
be448670 CF |
16244 | explicitly loading symbols from a DLL with no debugging information will |
16245 | cause the symbol names to be duplicated in @value{GDBN}'s lookup table, | |
16246 | which may adversely affect symbol lookup performance. | |
16247 | ||
79a6e687 | 16248 | @subsubsection DLL Name Prefixes |
be448670 CF |
16249 | |
16250 | In keeping with the naming conventions used by the Microsoft debugging | |
16251 | tools, DLL export symbols are made available with a prefix based on the | |
16252 | DLL name, for instance @code{KERNEL32!CreateFileA}. The plain name is | |
16253 | also entered into the symbol table, so @code{CreateFileA} is often | |
99e008fe | 16254 | sufficient. In some cases there will be name clashes within a program |
be448670 CF |
16255 | (particularly if the executable itself includes full debugging symbols) |
16256 | necessitating the use of the fully qualified name when referring to the | |
99e008fe | 16257 | contents of the DLL. Use single-quotes around the name to avoid the |
be448670 CF |
16258 | exclamation mark (``!'') being interpreted as a language operator. |
16259 | ||
16260 | Note that the internal name of the DLL may be all upper-case, even | |
99e008fe | 16261 | though the file name of the DLL is lower-case, or vice-versa. Since |
be448670 CF |
16262 | symbols within @value{GDBN} are @emph{case-sensitive} this may cause |
16263 | some confusion. If in doubt, try the @code{info functions} and | |
0869d01b NR |
16264 | @code{info variables} commands or even @code{maint print msymbols} |
16265 | (@pxref{Symbols}). Here's an example: | |
be448670 CF |
16266 | |
16267 | @smallexample | |
f7dc1244 | 16268 | (@value{GDBP}) info function CreateFileA |
be448670 CF |
16269 | All functions matching regular expression "CreateFileA": |
16270 | ||
16271 | Non-debugging symbols: | |
16272 | 0x77e885f4 CreateFileA | |
16273 | 0x77e885f4 KERNEL32!CreateFileA | |
16274 | @end smallexample | |
16275 | ||
16276 | @smallexample | |
f7dc1244 | 16277 | (@value{GDBP}) info function ! |
be448670 CF |
16278 | All functions matching regular expression "!": |
16279 | ||
16280 | Non-debugging symbols: | |
16281 | 0x6100114c cygwin1!__assert | |
16282 | 0x61004034 cygwin1!_dll_crt0@@0 | |
16283 | 0x61004240 cygwin1!dll_crt0(per_process *) | |
16284 | [etc...] | |
16285 | @end smallexample | |
16286 | ||
79a6e687 | 16287 | @subsubsection Working with Minimal Symbols |
be448670 CF |
16288 | |
16289 | Symbols extracted from a DLL's export table do not contain very much | |
16290 | type information. All that @value{GDBN} can do is guess whether a symbol | |
16291 | refers to a function or variable depending on the linker section that | |
16292 | contains the symbol. Also note that the actual contents of the memory | |
16293 | contained in a DLL are not available unless the program is running. This | |
16294 | means that you cannot examine the contents of a variable or disassemble | |
16295 | a function within a DLL without a running program. | |
16296 | ||
16297 | Variables are generally treated as pointers and dereferenced | |
16298 | automatically. For this reason, it is often necessary to prefix a | |
16299 | variable name with the address-of operator (``&'') and provide explicit | |
16300 | type information in the command. Here's an example of the type of | |
16301 | problem: | |
16302 | ||
16303 | @smallexample | |
f7dc1244 | 16304 | (@value{GDBP}) print 'cygwin1!__argv' |
be448670 CF |
16305 | $1 = 268572168 |
16306 | @end smallexample | |
16307 | ||
16308 | @smallexample | |
f7dc1244 | 16309 | (@value{GDBP}) x 'cygwin1!__argv' |
be448670 CF |
16310 | 0x10021610: "\230y\"" |
16311 | @end smallexample | |
16312 | ||
16313 | And two possible solutions: | |
16314 | ||
16315 | @smallexample | |
f7dc1244 | 16316 | (@value{GDBP}) print ((char **)'cygwin1!__argv')[0] |
be448670 CF |
16317 | $2 = 0x22fd98 "/cygdrive/c/mydirectory/myprogram" |
16318 | @end smallexample | |
16319 | ||
16320 | @smallexample | |
f7dc1244 | 16321 | (@value{GDBP}) x/2x &'cygwin1!__argv' |
be448670 | 16322 | 0x610c0aa8 <cygwin1!__argv>: 0x10021608 0x00000000 |
f7dc1244 | 16323 | (@value{GDBP}) x/x 0x10021608 |
be448670 | 16324 | 0x10021608: 0x0022fd98 |
f7dc1244 | 16325 | (@value{GDBP}) x/s 0x0022fd98 |
be448670 CF |
16326 | 0x22fd98: "/cygdrive/c/mydirectory/myprogram" |
16327 | @end smallexample | |
16328 | ||
16329 | Setting a break point within a DLL is possible even before the program | |
16330 | starts execution. However, under these circumstances, @value{GDBN} can't | |
16331 | examine the initial instructions of the function in order to skip the | |
16332 | function's frame set-up code. You can work around this by using ``*&'' | |
16333 | to set the breakpoint at a raw memory address: | |
16334 | ||
16335 | @smallexample | |
f7dc1244 | 16336 | (@value{GDBP}) break *&'python22!PyOS_Readline' |
be448670 CF |
16337 | Breakpoint 1 at 0x1e04eff0 |
16338 | @end smallexample | |
16339 | ||
16340 | The author of these extensions is not entirely convinced that setting a | |
16341 | break point within a shared DLL like @file{kernel32.dll} is completely | |
16342 | safe. | |
16343 | ||
14d6dd68 | 16344 | @node Hurd Native |
79a6e687 | 16345 | @subsection Commands Specific to @sc{gnu} Hurd Systems |
14d6dd68 EZ |
16346 | @cindex @sc{gnu} Hurd debugging |
16347 | ||
16348 | This subsection describes @value{GDBN} commands specific to the | |
16349 | @sc{gnu} Hurd native debugging. | |
16350 | ||
16351 | @table @code | |
16352 | @item set signals | |
16353 | @itemx set sigs | |
16354 | @kindex set signals@r{, Hurd command} | |
16355 | @kindex set sigs@r{, Hurd command} | |
16356 | This command toggles the state of inferior signal interception by | |
16357 | @value{GDBN}. Mach exceptions, such as breakpoint traps, are not | |
16358 | affected by this command. @code{sigs} is a shorthand alias for | |
16359 | @code{signals}. | |
16360 | ||
16361 | @item show signals | |
16362 | @itemx show sigs | |
16363 | @kindex show signals@r{, Hurd command} | |
16364 | @kindex show sigs@r{, Hurd command} | |
16365 | Show the current state of intercepting inferior's signals. | |
16366 | ||
16367 | @item set signal-thread | |
16368 | @itemx set sigthread | |
16369 | @kindex set signal-thread | |
16370 | @kindex set sigthread | |
16371 | This command tells @value{GDBN} which thread is the @code{libc} signal | |
16372 | thread. That thread is run when a signal is delivered to a running | |
16373 | process. @code{set sigthread} is the shorthand alias of @code{set | |
16374 | signal-thread}. | |
16375 | ||
16376 | @item show signal-thread | |
16377 | @itemx show sigthread | |
16378 | @kindex show signal-thread | |
16379 | @kindex show sigthread | |
16380 | These two commands show which thread will run when the inferior is | |
16381 | delivered a signal. | |
16382 | ||
16383 | @item set stopped | |
16384 | @kindex set stopped@r{, Hurd command} | |
16385 | This commands tells @value{GDBN} that the inferior process is stopped, | |
16386 | as with the @code{SIGSTOP} signal. The stopped process can be | |
16387 | continued by delivering a signal to it. | |
16388 | ||
16389 | @item show stopped | |
16390 | @kindex show stopped@r{, Hurd command} | |
16391 | This command shows whether @value{GDBN} thinks the debuggee is | |
16392 | stopped. | |
16393 | ||
16394 | @item set exceptions | |
16395 | @kindex set exceptions@r{, Hurd command} | |
16396 | Use this command to turn off trapping of exceptions in the inferior. | |
16397 | When exception trapping is off, neither breakpoints nor | |
16398 | single-stepping will work. To restore the default, set exception | |
16399 | trapping on. | |
16400 | ||
16401 | @item show exceptions | |
16402 | @kindex show exceptions@r{, Hurd command} | |
16403 | Show the current state of trapping exceptions in the inferior. | |
16404 | ||
16405 | @item set task pause | |
16406 | @kindex set task@r{, Hurd commands} | |
16407 | @cindex task attributes (@sc{gnu} Hurd) | |
16408 | @cindex pause current task (@sc{gnu} Hurd) | |
16409 | This command toggles task suspension when @value{GDBN} has control. | |
16410 | Setting it to on takes effect immediately, and the task is suspended | |
16411 | whenever @value{GDBN} gets control. Setting it to off will take | |
16412 | effect the next time the inferior is continued. If this option is set | |
16413 | to off, you can use @code{set thread default pause on} or @code{set | |
16414 | thread pause on} (see below) to pause individual threads. | |
16415 | ||
16416 | @item show task pause | |
16417 | @kindex show task@r{, Hurd commands} | |
16418 | Show the current state of task suspension. | |
16419 | ||
16420 | @item set task detach-suspend-count | |
16421 | @cindex task suspend count | |
16422 | @cindex detach from task, @sc{gnu} Hurd | |
16423 | This command sets the suspend count the task will be left with when | |
16424 | @value{GDBN} detaches from it. | |
16425 | ||
16426 | @item show task detach-suspend-count | |
16427 | Show the suspend count the task will be left with when detaching. | |
16428 | ||
16429 | @item set task exception-port | |
16430 | @itemx set task excp | |
16431 | @cindex task exception port, @sc{gnu} Hurd | |
16432 | This command sets the task exception port to which @value{GDBN} will | |
16433 | forward exceptions. The argument should be the value of the @dfn{send | |
16434 | rights} of the task. @code{set task excp} is a shorthand alias. | |
16435 | ||
16436 | @item set noninvasive | |
16437 | @cindex noninvasive task options | |
16438 | This command switches @value{GDBN} to a mode that is the least | |
16439 | invasive as far as interfering with the inferior is concerned. This | |
16440 | is the same as using @code{set task pause}, @code{set exceptions}, and | |
16441 | @code{set signals} to values opposite to the defaults. | |
16442 | ||
16443 | @item info send-rights | |
16444 | @itemx info receive-rights | |
16445 | @itemx info port-rights | |
16446 | @itemx info port-sets | |
16447 | @itemx info dead-names | |
16448 | @itemx info ports | |
16449 | @itemx info psets | |
16450 | @cindex send rights, @sc{gnu} Hurd | |
16451 | @cindex receive rights, @sc{gnu} Hurd | |
16452 | @cindex port rights, @sc{gnu} Hurd | |
16453 | @cindex port sets, @sc{gnu} Hurd | |
16454 | @cindex dead names, @sc{gnu} Hurd | |
16455 | These commands display information about, respectively, send rights, | |
16456 | receive rights, port rights, port sets, and dead names of a task. | |
16457 | There are also shorthand aliases: @code{info ports} for @code{info | |
16458 | port-rights} and @code{info psets} for @code{info port-sets}. | |
16459 | ||
16460 | @item set thread pause | |
16461 | @kindex set thread@r{, Hurd command} | |
16462 | @cindex thread properties, @sc{gnu} Hurd | |
16463 | @cindex pause current thread (@sc{gnu} Hurd) | |
16464 | This command toggles current thread suspension when @value{GDBN} has | |
16465 | control. Setting it to on takes effect immediately, and the current | |
16466 | thread is suspended whenever @value{GDBN} gets control. Setting it to | |
16467 | off will take effect the next time the inferior is continued. | |
16468 | Normally, this command has no effect, since when @value{GDBN} has | |
16469 | control, the whole task is suspended. However, if you used @code{set | |
16470 | task pause off} (see above), this command comes in handy to suspend | |
16471 | only the current thread. | |
16472 | ||
16473 | @item show thread pause | |
16474 | @kindex show thread@r{, Hurd command} | |
16475 | This command shows the state of current thread suspension. | |
16476 | ||
16477 | @item set thread run | |
d3e8051b | 16478 | This command sets whether the current thread is allowed to run. |
14d6dd68 EZ |
16479 | |
16480 | @item show thread run | |
16481 | Show whether the current thread is allowed to run. | |
16482 | ||
16483 | @item set thread detach-suspend-count | |
16484 | @cindex thread suspend count, @sc{gnu} Hurd | |
16485 | @cindex detach from thread, @sc{gnu} Hurd | |
16486 | This command sets the suspend count @value{GDBN} will leave on a | |
16487 | thread when detaching. This number is relative to the suspend count | |
16488 | found by @value{GDBN} when it notices the thread; use @code{set thread | |
16489 | takeover-suspend-count} to force it to an absolute value. | |
16490 | ||
16491 | @item show thread detach-suspend-count | |
16492 | Show the suspend count @value{GDBN} will leave on the thread when | |
16493 | detaching. | |
16494 | ||
16495 | @item set thread exception-port | |
16496 | @itemx set thread excp | |
16497 | Set the thread exception port to which to forward exceptions. This | |
16498 | overrides the port set by @code{set task exception-port} (see above). | |
16499 | @code{set thread excp} is the shorthand alias. | |
16500 | ||
16501 | @item set thread takeover-suspend-count | |
16502 | Normally, @value{GDBN}'s thread suspend counts are relative to the | |
16503 | value @value{GDBN} finds when it notices each thread. This command | |
16504 | changes the suspend counts to be absolute instead. | |
16505 | ||
16506 | @item set thread default | |
16507 | @itemx show thread default | |
16508 | @cindex thread default settings, @sc{gnu} Hurd | |
16509 | Each of the above @code{set thread} commands has a @code{set thread | |
16510 | default} counterpart (e.g., @code{set thread default pause}, @code{set | |
16511 | thread default exception-port}, etc.). The @code{thread default} | |
16512 | variety of commands sets the default thread properties for all | |
16513 | threads; you can then change the properties of individual threads with | |
16514 | the non-default commands. | |
16515 | @end table | |
16516 | ||
16517 | ||
a64548ea EZ |
16518 | @node Neutrino |
16519 | @subsection QNX Neutrino | |
16520 | @cindex QNX Neutrino | |
16521 | ||
16522 | @value{GDBN} provides the following commands specific to the QNX | |
16523 | Neutrino target: | |
16524 | ||
16525 | @table @code | |
16526 | @item set debug nto-debug | |
16527 | @kindex set debug nto-debug | |
16528 | When set to on, enables debugging messages specific to the QNX | |
16529 | Neutrino support. | |
16530 | ||
16531 | @item show debug nto-debug | |
16532 | @kindex show debug nto-debug | |
16533 | Show the current state of QNX Neutrino messages. | |
16534 | @end table | |
16535 | ||
a80b95ba TG |
16536 | @node Darwin |
16537 | @subsection Darwin | |
16538 | @cindex Darwin | |
16539 | ||
16540 | @value{GDBN} provides the following commands specific to the Darwin target: | |
16541 | ||
16542 | @table @code | |
16543 | @item set debug darwin @var{num} | |
16544 | @kindex set debug darwin | |
16545 | When set to a non zero value, enables debugging messages specific to | |
16546 | the Darwin support. Higher values produce more verbose output. | |
16547 | ||
16548 | @item show debug darwin | |
16549 | @kindex show debug darwin | |
16550 | Show the current state of Darwin messages. | |
16551 | ||
16552 | @item set debug mach-o @var{num} | |
16553 | @kindex set debug mach-o | |
16554 | When set to a non zero value, enables debugging messages while | |
16555 | @value{GDBN} is reading Darwin object files. (@dfn{Mach-O} is the | |
16556 | file format used on Darwin for object and executable files.) Higher | |
16557 | values produce more verbose output. This is a command to diagnose | |
16558 | problems internal to @value{GDBN} and should not be needed in normal | |
16559 | usage. | |
16560 | ||
16561 | @item show debug mach-o | |
16562 | @kindex show debug mach-o | |
16563 | Show the current state of Mach-O file messages. | |
16564 | ||
16565 | @item set mach-exceptions on | |
16566 | @itemx set mach-exceptions off | |
16567 | @kindex set mach-exceptions | |
16568 | On Darwin, faults are first reported as a Mach exception and are then | |
16569 | mapped to a Posix signal. Use this command to turn on trapping of | |
16570 | Mach exceptions in the inferior. This might be sometimes useful to | |
16571 | better understand the cause of a fault. The default is off. | |
16572 | ||
16573 | @item show mach-exceptions | |
16574 | @kindex show mach-exceptions | |
16575 | Show the current state of exceptions trapping. | |
16576 | @end table | |
16577 | ||
a64548ea | 16578 | |
8e04817f AC |
16579 | @node Embedded OS |
16580 | @section Embedded Operating Systems | |
104c1213 | 16581 | |
8e04817f AC |
16582 | This section describes configurations involving the debugging of |
16583 | embedded operating systems that are available for several different | |
16584 | architectures. | |
d4f3574e | 16585 | |
8e04817f AC |
16586 | @menu |
16587 | * VxWorks:: Using @value{GDBN} with VxWorks | |
16588 | @end menu | |
104c1213 | 16589 | |
8e04817f AC |
16590 | @value{GDBN} includes the ability to debug programs running on |
16591 | various real-time operating systems. | |
104c1213 | 16592 | |
8e04817f AC |
16593 | @node VxWorks |
16594 | @subsection Using @value{GDBN} with VxWorks | |
104c1213 | 16595 | |
8e04817f | 16596 | @cindex VxWorks |
104c1213 | 16597 | |
8e04817f | 16598 | @table @code |
104c1213 | 16599 | |
8e04817f AC |
16600 | @kindex target vxworks |
16601 | @item target vxworks @var{machinename} | |
16602 | A VxWorks system, attached via TCP/IP. The argument @var{machinename} | |
16603 | is the target system's machine name or IP address. | |
104c1213 | 16604 | |
8e04817f | 16605 | @end table |
104c1213 | 16606 | |
8e04817f AC |
16607 | On VxWorks, @code{load} links @var{filename} dynamically on the |
16608 | current target system as well as adding its symbols in @value{GDBN}. | |
104c1213 | 16609 | |
8e04817f AC |
16610 | @value{GDBN} enables developers to spawn and debug tasks running on networked |
16611 | VxWorks targets from a Unix host. Already-running tasks spawned from | |
16612 | the VxWorks shell can also be debugged. @value{GDBN} uses code that runs on | |
16613 | both the Unix host and on the VxWorks target. The program | |
16614 | @code{@value{GDBP}} is installed and executed on the Unix host. (It may be | |
16615 | installed with the name @code{vxgdb}, to distinguish it from a | |
16616 | @value{GDBN} for debugging programs on the host itself.) | |
104c1213 | 16617 | |
8e04817f AC |
16618 | @table @code |
16619 | @item VxWorks-timeout @var{args} | |
16620 | @kindex vxworks-timeout | |
16621 | All VxWorks-based targets now support the option @code{vxworks-timeout}. | |
16622 | This option is set by the user, and @var{args} represents the number of | |
16623 | seconds @value{GDBN} waits for responses to rpc's. You might use this if | |
16624 | your VxWorks target is a slow software simulator or is on the far side | |
16625 | of a thin network line. | |
16626 | @end table | |
104c1213 | 16627 | |
8e04817f AC |
16628 | The following information on connecting to VxWorks was current when |
16629 | this manual was produced; newer releases of VxWorks may use revised | |
16630 | procedures. | |
104c1213 | 16631 | |
4644b6e3 | 16632 | @findex INCLUDE_RDB |
8e04817f AC |
16633 | To use @value{GDBN} with VxWorks, you must rebuild your VxWorks kernel |
16634 | to include the remote debugging interface routines in the VxWorks | |
16635 | library @file{rdb.a}. To do this, define @code{INCLUDE_RDB} in the | |
16636 | VxWorks configuration file @file{configAll.h} and rebuild your VxWorks | |
16637 | kernel. The resulting kernel contains @file{rdb.a}, and spawns the | |
16638 | source debugging task @code{tRdbTask} when VxWorks is booted. For more | |
16639 | information on configuring and remaking VxWorks, see the manufacturer's | |
16640 | manual. | |
16641 | @c VxWorks, see the @cite{VxWorks Programmer's Guide}. | |
104c1213 | 16642 | |
8e04817f AC |
16643 | Once you have included @file{rdb.a} in your VxWorks system image and set |
16644 | your Unix execution search path to find @value{GDBN}, you are ready to | |
16645 | run @value{GDBN}. From your Unix host, run @code{@value{GDBP}} (or | |
16646 | @code{vxgdb}, depending on your installation). | |
104c1213 | 16647 | |
8e04817f | 16648 | @value{GDBN} comes up showing the prompt: |
104c1213 | 16649 | |
474c8240 | 16650 | @smallexample |
8e04817f | 16651 | (vxgdb) |
474c8240 | 16652 | @end smallexample |
104c1213 | 16653 | |
8e04817f AC |
16654 | @menu |
16655 | * VxWorks Connection:: Connecting to VxWorks | |
16656 | * VxWorks Download:: VxWorks download | |
16657 | * VxWorks Attach:: Running tasks | |
16658 | @end menu | |
104c1213 | 16659 | |
8e04817f AC |
16660 | @node VxWorks Connection |
16661 | @subsubsection Connecting to VxWorks | |
104c1213 | 16662 | |
8e04817f AC |
16663 | The @value{GDBN} command @code{target} lets you connect to a VxWorks target on the |
16664 | network. To connect to a target whose host name is ``@code{tt}'', type: | |
104c1213 | 16665 | |
474c8240 | 16666 | @smallexample |
8e04817f | 16667 | (vxgdb) target vxworks tt |
474c8240 | 16668 | @end smallexample |
104c1213 | 16669 | |
8e04817f AC |
16670 | @need 750 |
16671 | @value{GDBN} displays messages like these: | |
104c1213 | 16672 | |
8e04817f AC |
16673 | @smallexample |
16674 | Attaching remote machine across net... | |
16675 | Connected to tt. | |
16676 | @end smallexample | |
104c1213 | 16677 | |
8e04817f AC |
16678 | @need 1000 |
16679 | @value{GDBN} then attempts to read the symbol tables of any object modules | |
16680 | loaded into the VxWorks target since it was last booted. @value{GDBN} locates | |
16681 | these files by searching the directories listed in the command search | |
79a6e687 | 16682 | path (@pxref{Environment, ,Your Program's Environment}); if it fails |
8e04817f | 16683 | to find an object file, it displays a message such as: |
5d161b24 | 16684 | |
474c8240 | 16685 | @smallexample |
8e04817f | 16686 | prog.o: No such file or directory. |
474c8240 | 16687 | @end smallexample |
104c1213 | 16688 | |
8e04817f AC |
16689 | When this happens, add the appropriate directory to the search path with |
16690 | the @value{GDBN} command @code{path}, and execute the @code{target} | |
16691 | command again. | |
104c1213 | 16692 | |
8e04817f | 16693 | @node VxWorks Download |
79a6e687 | 16694 | @subsubsection VxWorks Download |
104c1213 | 16695 | |
8e04817f AC |
16696 | @cindex download to VxWorks |
16697 | If you have connected to the VxWorks target and you want to debug an | |
16698 | object that has not yet been loaded, you can use the @value{GDBN} | |
16699 | @code{load} command to download a file from Unix to VxWorks | |
16700 | incrementally. The object file given as an argument to the @code{load} | |
16701 | command is actually opened twice: first by the VxWorks target in order | |
16702 | to download the code, then by @value{GDBN} in order to read the symbol | |
16703 | table. This can lead to problems if the current working directories on | |
16704 | the two systems differ. If both systems have NFS mounted the same | |
16705 | filesystems, you can avoid these problems by using absolute paths. | |
16706 | Otherwise, it is simplest to set the working directory on both systems | |
16707 | to the directory in which the object file resides, and then to reference | |
16708 | the file by its name, without any path. For instance, a program | |
16709 | @file{prog.o} may reside in @file{@var{vxpath}/vw/demo/rdb} in VxWorks | |
16710 | and in @file{@var{hostpath}/vw/demo/rdb} on the host. To load this | |
16711 | program, type this on VxWorks: | |
104c1213 | 16712 | |
474c8240 | 16713 | @smallexample |
8e04817f | 16714 | -> cd "@var{vxpath}/vw/demo/rdb" |
474c8240 | 16715 | @end smallexample |
104c1213 | 16716 | |
8e04817f AC |
16717 | @noindent |
16718 | Then, in @value{GDBN}, type: | |
104c1213 | 16719 | |
474c8240 | 16720 | @smallexample |
8e04817f AC |
16721 | (vxgdb) cd @var{hostpath}/vw/demo/rdb |
16722 | (vxgdb) load prog.o | |
474c8240 | 16723 | @end smallexample |
104c1213 | 16724 | |
8e04817f | 16725 | @value{GDBN} displays a response similar to this: |
104c1213 | 16726 | |
8e04817f AC |
16727 | @smallexample |
16728 | Reading symbol data from wherever/vw/demo/rdb/prog.o... done. | |
16729 | @end smallexample | |
104c1213 | 16730 | |
8e04817f AC |
16731 | You can also use the @code{load} command to reload an object module |
16732 | after editing and recompiling the corresponding source file. Note that | |
16733 | this makes @value{GDBN} delete all currently-defined breakpoints, | |
16734 | auto-displays, and convenience variables, and to clear the value | |
16735 | history. (This is necessary in order to preserve the integrity of | |
16736 | debugger's data structures that reference the target system's symbol | |
16737 | table.) | |
104c1213 | 16738 | |
8e04817f | 16739 | @node VxWorks Attach |
79a6e687 | 16740 | @subsubsection Running Tasks |
104c1213 JM |
16741 | |
16742 | @cindex running VxWorks tasks | |
16743 | You can also attach to an existing task using the @code{attach} command as | |
16744 | follows: | |
16745 | ||
474c8240 | 16746 | @smallexample |
104c1213 | 16747 | (vxgdb) attach @var{task} |
474c8240 | 16748 | @end smallexample |
104c1213 JM |
16749 | |
16750 | @noindent | |
16751 | where @var{task} is the VxWorks hexadecimal task ID. The task can be running | |
16752 | or suspended when you attach to it. Running tasks are suspended at | |
16753 | the time of attachment. | |
16754 | ||
6d2ebf8b | 16755 | @node Embedded Processors |
104c1213 JM |
16756 | @section Embedded Processors |
16757 | ||
16758 | This section goes into details specific to particular embedded | |
16759 | configurations. | |
16760 | ||
c45da7e6 EZ |
16761 | @cindex send command to simulator |
16762 | Whenever a specific embedded processor has a simulator, @value{GDBN} | |
16763 | allows to send an arbitrary command to the simulator. | |
16764 | ||
16765 | @table @code | |
16766 | @item sim @var{command} | |
16767 | @kindex sim@r{, a command} | |
16768 | Send an arbitrary @var{command} string to the simulator. Consult the | |
16769 | documentation for the specific simulator in use for information about | |
16770 | acceptable commands. | |
16771 | @end table | |
16772 | ||
7d86b5d5 | 16773 | |
104c1213 | 16774 | @menu |
c45da7e6 | 16775 | * ARM:: ARM RDI |
172c2a43 | 16776 | * M32R/D:: Renesas M32R/D |
104c1213 | 16777 | * M68K:: Motorola M68K |
08be9d71 | 16778 | * MicroBlaze:: Xilinx MicroBlaze |
104c1213 | 16779 | * MIPS Embedded:: MIPS Embedded |
a37295f9 | 16780 | * OpenRISC 1000:: OpenRisc 1000 |
104c1213 | 16781 | * PA:: HP PA Embedded |
4acd40f3 | 16782 | * PowerPC Embedded:: PowerPC Embedded |
104c1213 JM |
16783 | * Sparclet:: Tsqware Sparclet |
16784 | * Sparclite:: Fujitsu Sparclite | |
104c1213 | 16785 | * Z8000:: Zilog Z8000 |
a64548ea EZ |
16786 | * AVR:: Atmel AVR |
16787 | * CRIS:: CRIS | |
16788 | * Super-H:: Renesas Super-H | |
104c1213 JM |
16789 | @end menu |
16790 | ||
6d2ebf8b | 16791 | @node ARM |
104c1213 | 16792 | @subsection ARM |
c45da7e6 | 16793 | @cindex ARM RDI |
104c1213 JM |
16794 | |
16795 | @table @code | |
8e04817f AC |
16796 | @kindex target rdi |
16797 | @item target rdi @var{dev} | |
16798 | ARM Angel monitor, via RDI library interface to ADP protocol. You may | |
16799 | use this target to communicate with both boards running the Angel | |
16800 | monitor, or with the EmbeddedICE JTAG debug device. | |
16801 | ||
16802 | @kindex target rdp | |
16803 | @item target rdp @var{dev} | |
16804 | ARM Demon monitor. | |
16805 | ||
16806 | @end table | |
16807 | ||
e2f4edfd EZ |
16808 | @value{GDBN} provides the following ARM-specific commands: |
16809 | ||
16810 | @table @code | |
16811 | @item set arm disassembler | |
16812 | @kindex set arm | |
16813 | This commands selects from a list of disassembly styles. The | |
16814 | @code{"std"} style is the standard style. | |
16815 | ||
16816 | @item show arm disassembler | |
16817 | @kindex show arm | |
16818 | Show the current disassembly style. | |
16819 | ||
16820 | @item set arm apcs32 | |
16821 | @cindex ARM 32-bit mode | |
16822 | This command toggles ARM operation mode between 32-bit and 26-bit. | |
16823 | ||
16824 | @item show arm apcs32 | |
16825 | Display the current usage of the ARM 32-bit mode. | |
16826 | ||
16827 | @item set arm fpu @var{fputype} | |
16828 | This command sets the ARM floating-point unit (FPU) type. The | |
16829 | argument @var{fputype} can be one of these: | |
16830 | ||
16831 | @table @code | |
16832 | @item auto | |
16833 | Determine the FPU type by querying the OS ABI. | |
16834 | @item softfpa | |
16835 | Software FPU, with mixed-endian doubles on little-endian ARM | |
16836 | processors. | |
16837 | @item fpa | |
16838 | GCC-compiled FPA co-processor. | |
16839 | @item softvfp | |
16840 | Software FPU with pure-endian doubles. | |
16841 | @item vfp | |
16842 | VFP co-processor. | |
16843 | @end table | |
16844 | ||
16845 | @item show arm fpu | |
16846 | Show the current type of the FPU. | |
16847 | ||
16848 | @item set arm abi | |
16849 | This command forces @value{GDBN} to use the specified ABI. | |
16850 | ||
16851 | @item show arm abi | |
16852 | Show the currently used ABI. | |
16853 | ||
0428b8f5 DJ |
16854 | @item set arm fallback-mode (arm|thumb|auto) |
16855 | @value{GDBN} uses the symbol table, when available, to determine | |
16856 | whether instructions are ARM or Thumb. This command controls | |
16857 | @value{GDBN}'s default behavior when the symbol table is not | |
16858 | available. The default is @samp{auto}, which causes @value{GDBN} to | |
16859 | use the current execution mode (from the @code{T} bit in the @code{CPSR} | |
16860 | register). | |
16861 | ||
16862 | @item show arm fallback-mode | |
16863 | Show the current fallback instruction mode. | |
16864 | ||
16865 | @item set arm force-mode (arm|thumb|auto) | |
16866 | This command overrides use of the symbol table to determine whether | |
16867 | instructions are ARM or Thumb. The default is @samp{auto}, which | |
16868 | causes @value{GDBN} to use the symbol table and then the setting | |
16869 | of @samp{set arm fallback-mode}. | |
16870 | ||
16871 | @item show arm force-mode | |
16872 | Show the current forced instruction mode. | |
16873 | ||
e2f4edfd EZ |
16874 | @item set debug arm |
16875 | Toggle whether to display ARM-specific debugging messages from the ARM | |
16876 | target support subsystem. | |
16877 | ||
16878 | @item show debug arm | |
16879 | Show whether ARM-specific debugging messages are enabled. | |
16880 | @end table | |
16881 | ||
c45da7e6 EZ |
16882 | The following commands are available when an ARM target is debugged |
16883 | using the RDI interface: | |
16884 | ||
16885 | @table @code | |
16886 | @item rdilogfile @r{[}@var{file}@r{]} | |
16887 | @kindex rdilogfile | |
16888 | @cindex ADP (Angel Debugger Protocol) logging | |
16889 | Set the filename for the ADP (Angel Debugger Protocol) packet log. | |
16890 | With an argument, sets the log file to the specified @var{file}. With | |
16891 | no argument, show the current log file name. The default log file is | |
16892 | @file{rdi.log}. | |
16893 | ||
16894 | @item rdilogenable @r{[}@var{arg}@r{]} | |
16895 | @kindex rdilogenable | |
16896 | Control logging of ADP packets. With an argument of 1 or @code{"yes"} | |
16897 | enables logging, with an argument 0 or @code{"no"} disables it. With | |
16898 | no arguments displays the current setting. When logging is enabled, | |
16899 | ADP packets exchanged between @value{GDBN} and the RDI target device | |
16900 | are logged to a file. | |
16901 | ||
16902 | @item set rdiromatzero | |
16903 | @kindex set rdiromatzero | |
16904 | @cindex ROM at zero address, RDI | |
16905 | Tell @value{GDBN} whether the target has ROM at address 0. If on, | |
16906 | vector catching is disabled, so that zero address can be used. If off | |
16907 | (the default), vector catching is enabled. For this command to take | |
16908 | effect, it needs to be invoked prior to the @code{target rdi} command. | |
16909 | ||
16910 | @item show rdiromatzero | |
16911 | @kindex show rdiromatzero | |
16912 | Show the current setting of ROM at zero address. | |
16913 | ||
16914 | @item set rdiheartbeat | |
16915 | @kindex set rdiheartbeat | |
16916 | @cindex RDI heartbeat | |
16917 | Enable or disable RDI heartbeat packets. It is not recommended to | |
16918 | turn on this option, since it confuses ARM and EPI JTAG interface, as | |
16919 | well as the Angel monitor. | |
16920 | ||
16921 | @item show rdiheartbeat | |
16922 | @kindex show rdiheartbeat | |
16923 | Show the setting of RDI heartbeat packets. | |
16924 | @end table | |
16925 | ||
e2f4edfd | 16926 | |
8e04817f | 16927 | @node M32R/D |
ba04e063 | 16928 | @subsection Renesas M32R/D and M32R/SDI |
8e04817f AC |
16929 | |
16930 | @table @code | |
8e04817f AC |
16931 | @kindex target m32r |
16932 | @item target m32r @var{dev} | |
172c2a43 | 16933 | Renesas M32R/D ROM monitor. |
8e04817f | 16934 | |
fb3e19c0 KI |
16935 | @kindex target m32rsdi |
16936 | @item target m32rsdi @var{dev} | |
16937 | Renesas M32R SDI server, connected via parallel port to the board. | |
721c2651 EZ |
16938 | @end table |
16939 | ||
16940 | The following @value{GDBN} commands are specific to the M32R monitor: | |
16941 | ||
16942 | @table @code | |
16943 | @item set download-path @var{path} | |
16944 | @kindex set download-path | |
16945 | @cindex find downloadable @sc{srec} files (M32R) | |
d3e8051b | 16946 | Set the default path for finding downloadable @sc{srec} files. |
721c2651 EZ |
16947 | |
16948 | @item show download-path | |
16949 | @kindex show download-path | |
16950 | Show the default path for downloadable @sc{srec} files. | |
fb3e19c0 | 16951 | |
721c2651 EZ |
16952 | @item set board-address @var{addr} |
16953 | @kindex set board-address | |
16954 | @cindex M32-EVA target board address | |
16955 | Set the IP address for the M32R-EVA target board. | |
16956 | ||
16957 | @item show board-address | |
16958 | @kindex show board-address | |
16959 | Show the current IP address of the target board. | |
16960 | ||
16961 | @item set server-address @var{addr} | |
16962 | @kindex set server-address | |
16963 | @cindex download server address (M32R) | |
16964 | Set the IP address for the download server, which is the @value{GDBN}'s | |
16965 | host machine. | |
16966 | ||
16967 | @item show server-address | |
16968 | @kindex show server-address | |
16969 | Display the IP address of the download server. | |
16970 | ||
16971 | @item upload @r{[}@var{file}@r{]} | |
16972 | @kindex upload@r{, M32R} | |
16973 | Upload the specified @sc{srec} @var{file} via the monitor's Ethernet | |
16974 | upload capability. If no @var{file} argument is given, the current | |
16975 | executable file is uploaded. | |
16976 | ||
16977 | @item tload @r{[}@var{file}@r{]} | |
16978 | @kindex tload@r{, M32R} | |
16979 | Test the @code{upload} command. | |
8e04817f AC |
16980 | @end table |
16981 | ||
ba04e063 EZ |
16982 | The following commands are available for M32R/SDI: |
16983 | ||
16984 | @table @code | |
16985 | @item sdireset | |
16986 | @kindex sdireset | |
16987 | @cindex reset SDI connection, M32R | |
16988 | This command resets the SDI connection. | |
16989 | ||
16990 | @item sdistatus | |
16991 | @kindex sdistatus | |
16992 | This command shows the SDI connection status. | |
16993 | ||
16994 | @item debug_chaos | |
16995 | @kindex debug_chaos | |
16996 | @cindex M32R/Chaos debugging | |
16997 | Instructs the remote that M32R/Chaos debugging is to be used. | |
16998 | ||
16999 | @item use_debug_dma | |
17000 | @kindex use_debug_dma | |
17001 | Instructs the remote to use the DEBUG_DMA method of accessing memory. | |
17002 | ||
17003 | @item use_mon_code | |
17004 | @kindex use_mon_code | |
17005 | Instructs the remote to use the MON_CODE method of accessing memory. | |
17006 | ||
17007 | @item use_ib_break | |
17008 | @kindex use_ib_break | |
17009 | Instructs the remote to set breakpoints by IB break. | |
17010 | ||
17011 | @item use_dbt_break | |
17012 | @kindex use_dbt_break | |
17013 | Instructs the remote to set breakpoints by DBT. | |
17014 | @end table | |
17015 | ||
8e04817f AC |
17016 | @node M68K |
17017 | @subsection M68k | |
17018 | ||
7ce59000 DJ |
17019 | The Motorola m68k configuration includes ColdFire support, and a |
17020 | target command for the following ROM monitor. | |
8e04817f AC |
17021 | |
17022 | @table @code | |
17023 | ||
8e04817f AC |
17024 | @kindex target dbug |
17025 | @item target dbug @var{dev} | |
17026 | dBUG ROM monitor for Motorola ColdFire. | |
17027 | ||
8e04817f AC |
17028 | @end table |
17029 | ||
08be9d71 ME |
17030 | @node MicroBlaze |
17031 | @subsection MicroBlaze | |
17032 | @cindex Xilinx MicroBlaze | |
17033 | @cindex XMD, Xilinx Microprocessor Debugger | |
17034 | ||
17035 | The MicroBlaze is a soft-core processor supported on various Xilinx | |
17036 | FPGAs, such as Spartan or Virtex series. Boards with these processors | |
17037 | usually have JTAG ports which connect to a host system running the Xilinx | |
17038 | Embedded Development Kit (EDK) or Software Development Kit (SDK). | |
17039 | This host system is used to download the configuration bitstream to | |
17040 | the target FPGA. The Xilinx Microprocessor Debugger (XMD) program | |
17041 | communicates with the target board using the JTAG interface and | |
17042 | presents a @code{gdbserver} interface to the board. By default | |
17043 | @code{xmd} uses port @code{1234}. (While it is possible to change | |
17044 | this default port, it requires the use of undocumented @code{xmd} | |
17045 | commands. Contact Xilinx support if you need to do this.) | |
17046 | ||
17047 | Use these GDB commands to connect to the MicroBlaze target processor. | |
17048 | ||
17049 | @table @code | |
17050 | @item target remote :1234 | |
17051 | Use this command to connect to the target if you are running @value{GDBN} | |
17052 | on the same system as @code{xmd}. | |
17053 | ||
17054 | @item target remote @var{xmd-host}:1234 | |
17055 | Use this command to connect to the target if it is connected to @code{xmd} | |
17056 | running on a different system named @var{xmd-host}. | |
17057 | ||
17058 | @item load | |
17059 | Use this command to download a program to the MicroBlaze target. | |
17060 | ||
17061 | @item set debug microblaze @var{n} | |
17062 | Enable MicroBlaze-specific debugging messages if non-zero. | |
17063 | ||
17064 | @item show debug microblaze @var{n} | |
17065 | Show MicroBlaze-specific debugging level. | |
17066 | @end table | |
17067 | ||
8e04817f AC |
17068 | @node MIPS Embedded |
17069 | @subsection MIPS Embedded | |
17070 | ||
17071 | @cindex MIPS boards | |
17072 | @value{GDBN} can use the MIPS remote debugging protocol to talk to a | |
17073 | MIPS board attached to a serial line. This is available when | |
17074 | you configure @value{GDBN} with @samp{--target=mips-idt-ecoff}. | |
104c1213 | 17075 | |
8e04817f AC |
17076 | @need 1000 |
17077 | Use these @value{GDBN} commands to specify the connection to your target board: | |
104c1213 | 17078 | |
8e04817f AC |
17079 | @table @code |
17080 | @item target mips @var{port} | |
17081 | @kindex target mips @var{port} | |
17082 | To run a program on the board, start up @code{@value{GDBP}} with the | |
17083 | name of your program as the argument. To connect to the board, use the | |
17084 | command @samp{target mips @var{port}}, where @var{port} is the name of | |
17085 | the serial port connected to the board. If the program has not already | |
17086 | been downloaded to the board, you may use the @code{load} command to | |
17087 | download it. You can then use all the usual @value{GDBN} commands. | |
104c1213 | 17088 | |
8e04817f AC |
17089 | For example, this sequence connects to the target board through a serial |
17090 | port, and loads and runs a program called @var{prog} through the | |
17091 | debugger: | |
104c1213 | 17092 | |
474c8240 | 17093 | @smallexample |
8e04817f AC |
17094 | host$ @value{GDBP} @var{prog} |
17095 | @value{GDBN} is free software and @dots{} | |
17096 | (@value{GDBP}) target mips /dev/ttyb | |
17097 | (@value{GDBP}) load @var{prog} | |
17098 | (@value{GDBP}) run | |
474c8240 | 17099 | @end smallexample |
104c1213 | 17100 | |
8e04817f AC |
17101 | @item target mips @var{hostname}:@var{portnumber} |
17102 | On some @value{GDBN} host configurations, you can specify a TCP | |
17103 | connection (for instance, to a serial line managed by a terminal | |
17104 | concentrator) instead of a serial port, using the syntax | |
17105 | @samp{@var{hostname}:@var{portnumber}}. | |
104c1213 | 17106 | |
8e04817f AC |
17107 | @item target pmon @var{port} |
17108 | @kindex target pmon @var{port} | |
17109 | PMON ROM monitor. | |
104c1213 | 17110 | |
8e04817f AC |
17111 | @item target ddb @var{port} |
17112 | @kindex target ddb @var{port} | |
17113 | NEC's DDB variant of PMON for Vr4300. | |
104c1213 | 17114 | |
8e04817f AC |
17115 | @item target lsi @var{port} |
17116 | @kindex target lsi @var{port} | |
17117 | LSI variant of PMON. | |
104c1213 | 17118 | |
8e04817f AC |
17119 | @kindex target r3900 |
17120 | @item target r3900 @var{dev} | |
17121 | Densan DVE-R3900 ROM monitor for Toshiba R3900 Mips. | |
104c1213 | 17122 | |
8e04817f AC |
17123 | @kindex target array |
17124 | @item target array @var{dev} | |
17125 | Array Tech LSI33K RAID controller board. | |
104c1213 | 17126 | |
8e04817f | 17127 | @end table |
104c1213 | 17128 | |
104c1213 | 17129 | |
8e04817f AC |
17130 | @noindent |
17131 | @value{GDBN} also supports these special commands for MIPS targets: | |
104c1213 | 17132 | |
8e04817f | 17133 | @table @code |
8e04817f AC |
17134 | @item set mipsfpu double |
17135 | @itemx set mipsfpu single | |
17136 | @itemx set mipsfpu none | |
a64548ea | 17137 | @itemx set mipsfpu auto |
8e04817f AC |
17138 | @itemx show mipsfpu |
17139 | @kindex set mipsfpu | |
17140 | @kindex show mipsfpu | |
17141 | @cindex MIPS remote floating point | |
17142 | @cindex floating point, MIPS remote | |
17143 | If your target board does not support the MIPS floating point | |
17144 | coprocessor, you should use the command @samp{set mipsfpu none} (if you | |
17145 | need this, you may wish to put the command in your @value{GDBN} init | |
17146 | file). This tells @value{GDBN} how to find the return value of | |
17147 | functions which return floating point values. It also allows | |
17148 | @value{GDBN} to avoid saving the floating point registers when calling | |
17149 | functions on the board. If you are using a floating point coprocessor | |
17150 | with only single precision floating point support, as on the @sc{r4650} | |
17151 | processor, use the command @samp{set mipsfpu single}. The default | |
17152 | double precision floating point coprocessor may be selected using | |
17153 | @samp{set mipsfpu double}. | |
104c1213 | 17154 | |
8e04817f AC |
17155 | In previous versions the only choices were double precision or no |
17156 | floating point, so @samp{set mipsfpu on} will select double precision | |
17157 | and @samp{set mipsfpu off} will select no floating point. | |
104c1213 | 17158 | |
8e04817f AC |
17159 | As usual, you can inquire about the @code{mipsfpu} variable with |
17160 | @samp{show mipsfpu}. | |
104c1213 | 17161 | |
8e04817f AC |
17162 | @item set timeout @var{seconds} |
17163 | @itemx set retransmit-timeout @var{seconds} | |
17164 | @itemx show timeout | |
17165 | @itemx show retransmit-timeout | |
17166 | @cindex @code{timeout}, MIPS protocol | |
17167 | @cindex @code{retransmit-timeout}, MIPS protocol | |
17168 | @kindex set timeout | |
17169 | @kindex show timeout | |
17170 | @kindex set retransmit-timeout | |
17171 | @kindex show retransmit-timeout | |
17172 | You can control the timeout used while waiting for a packet, in the MIPS | |
17173 | remote protocol, with the @code{set timeout @var{seconds}} command. The | |
17174 | default is 5 seconds. Similarly, you can control the timeout used while | |
a6f3e723 | 17175 | waiting for an acknowledgment of a packet with the @code{set |
8e04817f AC |
17176 | retransmit-timeout @var{seconds}} command. The default is 3 seconds. |
17177 | You can inspect both values with @code{show timeout} and @code{show | |
17178 | retransmit-timeout}. (These commands are @emph{only} available when | |
17179 | @value{GDBN} is configured for @samp{--target=mips-idt-ecoff}.) | |
104c1213 | 17180 | |
8e04817f AC |
17181 | The timeout set by @code{set timeout} does not apply when @value{GDBN} |
17182 | is waiting for your program to stop. In that case, @value{GDBN} waits | |
17183 | forever because it has no way of knowing how long the program is going | |
17184 | to run before stopping. | |
ba04e063 EZ |
17185 | |
17186 | @item set syn-garbage-limit @var{num} | |
17187 | @kindex set syn-garbage-limit@r{, MIPS remote} | |
17188 | @cindex synchronize with remote MIPS target | |
17189 | Limit the maximum number of characters @value{GDBN} should ignore when | |
17190 | it tries to synchronize with the remote target. The default is 10 | |
17191 | characters. Setting the limit to -1 means there's no limit. | |
17192 | ||
17193 | @item show syn-garbage-limit | |
17194 | @kindex show syn-garbage-limit@r{, MIPS remote} | |
17195 | Show the current limit on the number of characters to ignore when | |
17196 | trying to synchronize with the remote system. | |
17197 | ||
17198 | @item set monitor-prompt @var{prompt} | |
17199 | @kindex set monitor-prompt@r{, MIPS remote} | |
17200 | @cindex remote monitor prompt | |
17201 | Tell @value{GDBN} to expect the specified @var{prompt} string from the | |
17202 | remote monitor. The default depends on the target: | |
17203 | @table @asis | |
17204 | @item pmon target | |
17205 | @samp{PMON} | |
17206 | @item ddb target | |
17207 | @samp{NEC010} | |
17208 | @item lsi target | |
17209 | @samp{PMON>} | |
17210 | @end table | |
17211 | ||
17212 | @item show monitor-prompt | |
17213 | @kindex show monitor-prompt@r{, MIPS remote} | |
17214 | Show the current strings @value{GDBN} expects as the prompt from the | |
17215 | remote monitor. | |
17216 | ||
17217 | @item set monitor-warnings | |
17218 | @kindex set monitor-warnings@r{, MIPS remote} | |
17219 | Enable or disable monitor warnings about hardware breakpoints. This | |
17220 | has effect only for the @code{lsi} target. When on, @value{GDBN} will | |
17221 | display warning messages whose codes are returned by the @code{lsi} | |
17222 | PMON monitor for breakpoint commands. | |
17223 | ||
17224 | @item show monitor-warnings | |
17225 | @kindex show monitor-warnings@r{, MIPS remote} | |
17226 | Show the current setting of printing monitor warnings. | |
17227 | ||
17228 | @item pmon @var{command} | |
17229 | @kindex pmon@r{, MIPS remote} | |
17230 | @cindex send PMON command | |
17231 | This command allows sending an arbitrary @var{command} string to the | |
17232 | monitor. The monitor must be in debug mode for this to work. | |
8e04817f | 17233 | @end table |
104c1213 | 17234 | |
a37295f9 MM |
17235 | @node OpenRISC 1000 |
17236 | @subsection OpenRISC 1000 | |
17237 | @cindex OpenRISC 1000 | |
17238 | ||
17239 | @cindex or1k boards | |
17240 | See OR1k Architecture document (@uref{www.opencores.org}) for more information | |
17241 | about platform and commands. | |
17242 | ||
17243 | @table @code | |
17244 | ||
17245 | @kindex target jtag | |
17246 | @item target jtag jtag://@var{host}:@var{port} | |
17247 | ||
17248 | Connects to remote JTAG server. | |
17249 | JTAG remote server can be either an or1ksim or JTAG server, | |
17250 | connected via parallel port to the board. | |
17251 | ||
17252 | Example: @code{target jtag jtag://localhost:9999} | |
17253 | ||
17254 | @kindex or1ksim | |
17255 | @item or1ksim @var{command} | |
17256 | If connected to @code{or1ksim} OpenRISC 1000 Architectural | |
17257 | Simulator, proprietary commands can be executed. | |
17258 | ||
17259 | @kindex info or1k spr | |
17260 | @item info or1k spr | |
17261 | Displays spr groups. | |
17262 | ||
17263 | @item info or1k spr @var{group} | |
17264 | @itemx info or1k spr @var{groupno} | |
17265 | Displays register names in selected group. | |
17266 | ||
17267 | @item info or1k spr @var{group} @var{register} | |
17268 | @itemx info or1k spr @var{register} | |
17269 | @itemx info or1k spr @var{groupno} @var{registerno} | |
17270 | @itemx info or1k spr @var{registerno} | |
17271 | Shows information about specified spr register. | |
17272 | ||
17273 | @kindex spr | |
17274 | @item spr @var{group} @var{register} @var{value} | |
17275 | @itemx spr @var{register @var{value}} | |
17276 | @itemx spr @var{groupno} @var{registerno @var{value}} | |
17277 | @itemx spr @var{registerno @var{value}} | |
17278 | Writes @var{value} to specified spr register. | |
17279 | @end table | |
17280 | ||
17281 | Some implementations of OpenRISC 1000 Architecture also have hardware trace. | |
17282 | It is very similar to @value{GDBN} trace, except it does not interfere with normal | |
17283 | program execution and is thus much faster. Hardware breakpoints/watchpoint | |
17284 | triggers can be set using: | |
17285 | @table @code | |
17286 | @item $LEA/$LDATA | |
17287 | Load effective address/data | |
17288 | @item $SEA/$SDATA | |
17289 | Store effective address/data | |
17290 | @item $AEA/$ADATA | |
17291 | Access effective address ($SEA or $LEA) or data ($SDATA/$LDATA) | |
17292 | @item $FETCH | |
17293 | Fetch data | |
17294 | @end table | |
17295 | ||
17296 | When triggered, it can capture low level data, like: @code{PC}, @code{LSEA}, | |
17297 | @code{LDATA}, @code{SDATA}, @code{READSPR}, @code{WRITESPR}, @code{INSTR}. | |
17298 | ||
17299 | @code{htrace} commands: | |
17300 | @cindex OpenRISC 1000 htrace | |
17301 | @table @code | |
17302 | @kindex hwatch | |
17303 | @item hwatch @var{conditional} | |
d3e8051b | 17304 | Set hardware watchpoint on combination of Load/Store Effective Address(es) |
a37295f9 MM |
17305 | or Data. For example: |
17306 | ||
17307 | @code{hwatch ($LEA == my_var) && ($LDATA < 50) || ($SEA == my_var) && ($SDATA >= 50)} | |
17308 | ||
17309 | @code{hwatch ($LEA == my_var) && ($LDATA < 50) || ($SEA == my_var) && ($SDATA >= 50)} | |
17310 | ||
4644b6e3 | 17311 | @kindex htrace |
a37295f9 MM |
17312 | @item htrace info |
17313 | Display information about current HW trace configuration. | |
17314 | ||
a37295f9 MM |
17315 | @item htrace trigger @var{conditional} |
17316 | Set starting criteria for HW trace. | |
17317 | ||
a37295f9 MM |
17318 | @item htrace qualifier @var{conditional} |
17319 | Set acquisition qualifier for HW trace. | |
17320 | ||
a37295f9 MM |
17321 | @item htrace stop @var{conditional} |
17322 | Set HW trace stopping criteria. | |
17323 | ||
f153cc92 | 17324 | @item htrace record [@var{data}]* |
a37295f9 MM |
17325 | Selects the data to be recorded, when qualifier is met and HW trace was |
17326 | triggered. | |
17327 | ||
a37295f9 | 17328 | @item htrace enable |
a37295f9 MM |
17329 | @itemx htrace disable |
17330 | Enables/disables the HW trace. | |
17331 | ||
f153cc92 | 17332 | @item htrace rewind [@var{filename}] |
a37295f9 MM |
17333 | Clears currently recorded trace data. |
17334 | ||
17335 | If filename is specified, new trace file is made and any newly collected data | |
17336 | will be written there. | |
17337 | ||
f153cc92 | 17338 | @item htrace print [@var{start} [@var{len}]] |
a37295f9 MM |
17339 | Prints trace buffer, using current record configuration. |
17340 | ||
a37295f9 MM |
17341 | @item htrace mode continuous |
17342 | Set continuous trace mode. | |
17343 | ||
a37295f9 MM |
17344 | @item htrace mode suspend |
17345 | Set suspend trace mode. | |
17346 | ||
17347 | @end table | |
17348 | ||
4acd40f3 TJB |
17349 | @node PowerPC Embedded |
17350 | @subsection PowerPC Embedded | |
104c1213 | 17351 | |
55eddb0f DJ |
17352 | @value{GDBN} provides the following PowerPC-specific commands: |
17353 | ||
104c1213 | 17354 | @table @code |
55eddb0f DJ |
17355 | @kindex set powerpc |
17356 | @item set powerpc soft-float | |
17357 | @itemx show powerpc soft-float | |
17358 | Force @value{GDBN} to use (or not use) a software floating point calling | |
17359 | convention. By default, @value{GDBN} selects the calling convention based | |
17360 | on the selected architecture and the provided executable file. | |
17361 | ||
17362 | @item set powerpc vector-abi | |
17363 | @itemx show powerpc vector-abi | |
17364 | Force @value{GDBN} to use the specified calling convention for vector | |
17365 | arguments and return values. The valid options are @samp{auto}; | |
17366 | @samp{generic}, to avoid vector registers even if they are present; | |
17367 | @samp{altivec}, to use AltiVec registers; and @samp{spe} to use SPE | |
17368 | registers. By default, @value{GDBN} selects the calling convention | |
17369 | based on the selected architecture and the provided executable file. | |
17370 | ||
8e04817f AC |
17371 | @kindex target dink32 |
17372 | @item target dink32 @var{dev} | |
17373 | DINK32 ROM monitor. | |
104c1213 | 17374 | |
8e04817f AC |
17375 | @kindex target ppcbug |
17376 | @item target ppcbug @var{dev} | |
17377 | @kindex target ppcbug1 | |
17378 | @item target ppcbug1 @var{dev} | |
17379 | PPCBUG ROM monitor for PowerPC. | |
104c1213 | 17380 | |
8e04817f AC |
17381 | @kindex target sds |
17382 | @item target sds @var{dev} | |
17383 | SDS monitor, running on a PowerPC board (such as Motorola's ADS). | |
c45da7e6 | 17384 | @end table |
8e04817f | 17385 | |
c45da7e6 | 17386 | @cindex SDS protocol |
d52fb0e9 | 17387 | The following commands specific to the SDS protocol are supported |
55eddb0f | 17388 | by @value{GDBN}: |
c45da7e6 EZ |
17389 | |
17390 | @table @code | |
17391 | @item set sdstimeout @var{nsec} | |
17392 | @kindex set sdstimeout | |
17393 | Set the timeout for SDS protocol reads to be @var{nsec} seconds. The | |
17394 | default is 2 seconds. | |
17395 | ||
17396 | @item show sdstimeout | |
17397 | @kindex show sdstimeout | |
17398 | Show the current value of the SDS timeout. | |
17399 | ||
17400 | @item sds @var{command} | |
17401 | @kindex sds@r{, a command} | |
17402 | Send the specified @var{command} string to the SDS monitor. | |
8e04817f AC |
17403 | @end table |
17404 | ||
c45da7e6 | 17405 | |
8e04817f AC |
17406 | @node PA |
17407 | @subsection HP PA Embedded | |
104c1213 JM |
17408 | |
17409 | @table @code | |
17410 | ||
8e04817f AC |
17411 | @kindex target op50n |
17412 | @item target op50n @var{dev} | |
17413 | OP50N monitor, running on an OKI HPPA board. | |
17414 | ||
17415 | @kindex target w89k | |
17416 | @item target w89k @var{dev} | |
17417 | W89K monitor, running on a Winbond HPPA board. | |
104c1213 JM |
17418 | |
17419 | @end table | |
17420 | ||
8e04817f AC |
17421 | @node Sparclet |
17422 | @subsection Tsqware Sparclet | |
104c1213 | 17423 | |
8e04817f AC |
17424 | @cindex Sparclet |
17425 | ||
17426 | @value{GDBN} enables developers to debug tasks running on | |
17427 | Sparclet targets from a Unix host. | |
17428 | @value{GDBN} uses code that runs on | |
17429 | both the Unix host and on the Sparclet target. The program | |
17430 | @code{@value{GDBP}} is installed and executed on the Unix host. | |
104c1213 | 17431 | |
8e04817f AC |
17432 | @table @code |
17433 | @item remotetimeout @var{args} | |
17434 | @kindex remotetimeout | |
17435 | @value{GDBN} supports the option @code{remotetimeout}. | |
17436 | This option is set by the user, and @var{args} represents the number of | |
17437 | seconds @value{GDBN} waits for responses. | |
104c1213 JM |
17438 | @end table |
17439 | ||
8e04817f AC |
17440 | @cindex compiling, on Sparclet |
17441 | When compiling for debugging, include the options @samp{-g} to get debug | |
17442 | information and @samp{-Ttext} to relocate the program to where you wish to | |
17443 | load it on the target. You may also want to add the options @samp{-n} or | |
17444 | @samp{-N} in order to reduce the size of the sections. Example: | |
104c1213 | 17445 | |
474c8240 | 17446 | @smallexample |
8e04817f | 17447 | sparclet-aout-gcc prog.c -Ttext 0x12010000 -g -o prog -N |
474c8240 | 17448 | @end smallexample |
104c1213 | 17449 | |
8e04817f | 17450 | You can use @code{objdump} to verify that the addresses are what you intended: |
104c1213 | 17451 | |
474c8240 | 17452 | @smallexample |
8e04817f | 17453 | sparclet-aout-objdump --headers --syms prog |
474c8240 | 17454 | @end smallexample |
104c1213 | 17455 | |
8e04817f AC |
17456 | @cindex running, on Sparclet |
17457 | Once you have set | |
17458 | your Unix execution search path to find @value{GDBN}, you are ready to | |
17459 | run @value{GDBN}. From your Unix host, run @code{@value{GDBP}} | |
17460 | (or @code{sparclet-aout-gdb}, depending on your installation). | |
104c1213 | 17461 | |
8e04817f AC |
17462 | @value{GDBN} comes up showing the prompt: |
17463 | ||
474c8240 | 17464 | @smallexample |
8e04817f | 17465 | (gdbslet) |
474c8240 | 17466 | @end smallexample |
104c1213 JM |
17467 | |
17468 | @menu | |
8e04817f AC |
17469 | * Sparclet File:: Setting the file to debug |
17470 | * Sparclet Connection:: Connecting to Sparclet | |
17471 | * Sparclet Download:: Sparclet download | |
17472 | * Sparclet Execution:: Running and debugging | |
104c1213 JM |
17473 | @end menu |
17474 | ||
8e04817f | 17475 | @node Sparclet File |
79a6e687 | 17476 | @subsubsection Setting File to Debug |
104c1213 | 17477 | |
8e04817f | 17478 | The @value{GDBN} command @code{file} lets you choose with program to debug. |
104c1213 | 17479 | |
474c8240 | 17480 | @smallexample |
8e04817f | 17481 | (gdbslet) file prog |
474c8240 | 17482 | @end smallexample |
104c1213 | 17483 | |
8e04817f AC |
17484 | @need 1000 |
17485 | @value{GDBN} then attempts to read the symbol table of @file{prog}. | |
17486 | @value{GDBN} locates | |
17487 | the file by searching the directories listed in the command search | |
17488 | path. | |
12c27660 | 17489 | If the file was compiled with debug information (option @samp{-g}), source |
8e04817f AC |
17490 | files will be searched as well. |
17491 | @value{GDBN} locates | |
17492 | the source files by searching the directories listed in the directory search | |
79a6e687 | 17493 | path (@pxref{Environment, ,Your Program's Environment}). |
8e04817f AC |
17494 | If it fails |
17495 | to find a file, it displays a message such as: | |
104c1213 | 17496 | |
474c8240 | 17497 | @smallexample |
8e04817f | 17498 | prog: No such file or directory. |
474c8240 | 17499 | @end smallexample |
104c1213 | 17500 | |
8e04817f AC |
17501 | When this happens, add the appropriate directories to the search paths with |
17502 | the @value{GDBN} commands @code{path} and @code{dir}, and execute the | |
17503 | @code{target} command again. | |
104c1213 | 17504 | |
8e04817f AC |
17505 | @node Sparclet Connection |
17506 | @subsubsection Connecting to Sparclet | |
104c1213 | 17507 | |
8e04817f AC |
17508 | The @value{GDBN} command @code{target} lets you connect to a Sparclet target. |
17509 | To connect to a target on serial port ``@code{ttya}'', type: | |
104c1213 | 17510 | |
474c8240 | 17511 | @smallexample |
8e04817f AC |
17512 | (gdbslet) target sparclet /dev/ttya |
17513 | Remote target sparclet connected to /dev/ttya | |
17514 | main () at ../prog.c:3 | |
474c8240 | 17515 | @end smallexample |
104c1213 | 17516 | |
8e04817f AC |
17517 | @need 750 |
17518 | @value{GDBN} displays messages like these: | |
104c1213 | 17519 | |
474c8240 | 17520 | @smallexample |
8e04817f | 17521 | Connected to ttya. |
474c8240 | 17522 | @end smallexample |
104c1213 | 17523 | |
8e04817f | 17524 | @node Sparclet Download |
79a6e687 | 17525 | @subsubsection Sparclet Download |
104c1213 | 17526 | |
8e04817f AC |
17527 | @cindex download to Sparclet |
17528 | Once connected to the Sparclet target, | |
17529 | you can use the @value{GDBN} | |
17530 | @code{load} command to download the file from the host to the target. | |
17531 | The file name and load offset should be given as arguments to the @code{load} | |
17532 | command. | |
17533 | Since the file format is aout, the program must be loaded to the starting | |
17534 | address. You can use @code{objdump} to find out what this value is. The load | |
17535 | offset is an offset which is added to the VMA (virtual memory address) | |
17536 | of each of the file's sections. | |
17537 | For instance, if the program | |
17538 | @file{prog} was linked to text address 0x1201000, with data at 0x12010160 | |
17539 | and bss at 0x12010170, in @value{GDBN}, type: | |
104c1213 | 17540 | |
474c8240 | 17541 | @smallexample |
8e04817f AC |
17542 | (gdbslet) load prog 0x12010000 |
17543 | Loading section .text, size 0xdb0 vma 0x12010000 | |
474c8240 | 17544 | @end smallexample |
104c1213 | 17545 | |
8e04817f AC |
17546 | If the code is loaded at a different address then what the program was linked |
17547 | to, you may need to use the @code{section} and @code{add-symbol-file} commands | |
17548 | to tell @value{GDBN} where to map the symbol table. | |
17549 | ||
17550 | @node Sparclet Execution | |
79a6e687 | 17551 | @subsubsection Running and Debugging |
8e04817f AC |
17552 | |
17553 | @cindex running and debugging Sparclet programs | |
17554 | You can now begin debugging the task using @value{GDBN}'s execution control | |
17555 | commands, @code{b}, @code{step}, @code{run}, etc. See the @value{GDBN} | |
17556 | manual for the list of commands. | |
17557 | ||
474c8240 | 17558 | @smallexample |
8e04817f AC |
17559 | (gdbslet) b main |
17560 | Breakpoint 1 at 0x12010000: file prog.c, line 3. | |
17561 | (gdbslet) run | |
17562 | Starting program: prog | |
17563 | Breakpoint 1, main (argc=1, argv=0xeffff21c) at prog.c:3 | |
17564 | 3 char *symarg = 0; | |
17565 | (gdbslet) step | |
17566 | 4 char *execarg = "hello!"; | |
17567 | (gdbslet) | |
474c8240 | 17568 | @end smallexample |
8e04817f AC |
17569 | |
17570 | @node Sparclite | |
17571 | @subsection Fujitsu Sparclite | |
104c1213 JM |
17572 | |
17573 | @table @code | |
17574 | ||
8e04817f AC |
17575 | @kindex target sparclite |
17576 | @item target sparclite @var{dev} | |
17577 | Fujitsu sparclite boards, used only for the purpose of loading. | |
17578 | You must use an additional command to debug the program. | |
17579 | For example: target remote @var{dev} using @value{GDBN} standard | |
17580 | remote protocol. | |
104c1213 JM |
17581 | |
17582 | @end table | |
17583 | ||
8e04817f AC |
17584 | @node Z8000 |
17585 | @subsection Zilog Z8000 | |
104c1213 | 17586 | |
8e04817f AC |
17587 | @cindex Z8000 |
17588 | @cindex simulator, Z8000 | |
17589 | @cindex Zilog Z8000 simulator | |
104c1213 | 17590 | |
8e04817f AC |
17591 | When configured for debugging Zilog Z8000 targets, @value{GDBN} includes |
17592 | a Z8000 simulator. | |
17593 | ||
17594 | For the Z8000 family, @samp{target sim} simulates either the Z8002 (the | |
17595 | unsegmented variant of the Z8000 architecture) or the Z8001 (the | |
17596 | segmented variant). The simulator recognizes which architecture is | |
17597 | appropriate by inspecting the object code. | |
104c1213 | 17598 | |
8e04817f AC |
17599 | @table @code |
17600 | @item target sim @var{args} | |
17601 | @kindex sim | |
17602 | @kindex target sim@r{, with Z8000} | |
17603 | Debug programs on a simulated CPU. If the simulator supports setup | |
17604 | options, specify them via @var{args}. | |
104c1213 JM |
17605 | @end table |
17606 | ||
8e04817f AC |
17607 | @noindent |
17608 | After specifying this target, you can debug programs for the simulated | |
17609 | CPU in the same style as programs for your host computer; use the | |
17610 | @code{file} command to load a new program image, the @code{run} command | |
17611 | to run your program, and so on. | |
17612 | ||
17613 | As well as making available all the usual machine registers | |
17614 | (@pxref{Registers, ,Registers}), the Z8000 simulator provides three | |
17615 | additional items of information as specially named registers: | |
104c1213 JM |
17616 | |
17617 | @table @code | |
17618 | ||
8e04817f AC |
17619 | @item cycles |
17620 | Counts clock-ticks in the simulator. | |
104c1213 | 17621 | |
8e04817f AC |
17622 | @item insts |
17623 | Counts instructions run in the simulator. | |
104c1213 | 17624 | |
8e04817f AC |
17625 | @item time |
17626 | Execution time in 60ths of a second. | |
104c1213 | 17627 | |
8e04817f | 17628 | @end table |
104c1213 | 17629 | |
8e04817f AC |
17630 | You can refer to these values in @value{GDBN} expressions with the usual |
17631 | conventions; for example, @w{@samp{b fputc if $cycles>5000}} sets a | |
17632 | conditional breakpoint that suspends only after at least 5000 | |
17633 | simulated clock ticks. | |
104c1213 | 17634 | |
a64548ea EZ |
17635 | @node AVR |
17636 | @subsection Atmel AVR | |
17637 | @cindex AVR | |
17638 | ||
17639 | When configured for debugging the Atmel AVR, @value{GDBN} supports the | |
17640 | following AVR-specific commands: | |
17641 | ||
17642 | @table @code | |
17643 | @item info io_registers | |
17644 | @kindex info io_registers@r{, AVR} | |
17645 | @cindex I/O registers (Atmel AVR) | |
17646 | This command displays information about the AVR I/O registers. For | |
17647 | each register, @value{GDBN} prints its number and value. | |
17648 | @end table | |
17649 | ||
17650 | @node CRIS | |
17651 | @subsection CRIS | |
17652 | @cindex CRIS | |
17653 | ||
17654 | When configured for debugging CRIS, @value{GDBN} provides the | |
17655 | following CRIS-specific commands: | |
17656 | ||
17657 | @table @code | |
17658 | @item set cris-version @var{ver} | |
17659 | @cindex CRIS version | |
e22e55c9 OF |
17660 | Set the current CRIS version to @var{ver}, either @samp{10} or @samp{32}. |
17661 | The CRIS version affects register names and sizes. This command is useful in | |
17662 | case autodetection of the CRIS version fails. | |
a64548ea EZ |
17663 | |
17664 | @item show cris-version | |
17665 | Show the current CRIS version. | |
17666 | ||
17667 | @item set cris-dwarf2-cfi | |
17668 | @cindex DWARF-2 CFI and CRIS | |
e22e55c9 OF |
17669 | Set the usage of DWARF-2 CFI for CRIS debugging. The default is @samp{on}. |
17670 | Change to @samp{off} when using @code{gcc-cris} whose version is below | |
17671 | @code{R59}. | |
a64548ea EZ |
17672 | |
17673 | @item show cris-dwarf2-cfi | |
17674 | Show the current state of using DWARF-2 CFI. | |
e22e55c9 OF |
17675 | |
17676 | @item set cris-mode @var{mode} | |
17677 | @cindex CRIS mode | |
17678 | Set the current CRIS mode to @var{mode}. It should only be changed when | |
17679 | debugging in guru mode, in which case it should be set to | |
17680 | @samp{guru} (the default is @samp{normal}). | |
17681 | ||
17682 | @item show cris-mode | |
17683 | Show the current CRIS mode. | |
a64548ea EZ |
17684 | @end table |
17685 | ||
17686 | @node Super-H | |
17687 | @subsection Renesas Super-H | |
17688 | @cindex Super-H | |
17689 | ||
17690 | For the Renesas Super-H processor, @value{GDBN} provides these | |
17691 | commands: | |
17692 | ||
17693 | @table @code | |
17694 | @item regs | |
17695 | @kindex regs@r{, Super-H} | |
17696 | Show the values of all Super-H registers. | |
c055b101 CV |
17697 | |
17698 | @item set sh calling-convention @var{convention} | |
17699 | @kindex set sh calling-convention | |
17700 | Set the calling-convention used when calling functions from @value{GDBN}. | |
17701 | Allowed values are @samp{gcc}, which is the default setting, and @samp{renesas}. | |
17702 | With the @samp{gcc} setting, functions are called using the @value{NGCC} calling | |
17703 | convention. If the DWARF-2 information of the called function specifies | |
17704 | that the function follows the Renesas calling convention, the function | |
17705 | is called using the Renesas calling convention. If the calling convention | |
17706 | is set to @samp{renesas}, the Renesas calling convention is always used, | |
17707 | regardless of the DWARF-2 information. This can be used to override the | |
17708 | default of @samp{gcc} if debug information is missing, or the compiler | |
17709 | does not emit the DWARF-2 calling convention entry for a function. | |
17710 | ||
17711 | @item show sh calling-convention | |
17712 | @kindex show sh calling-convention | |
17713 | Show the current calling convention setting. | |
17714 | ||
a64548ea EZ |
17715 | @end table |
17716 | ||
17717 | ||
8e04817f AC |
17718 | @node Architectures |
17719 | @section Architectures | |
104c1213 | 17720 | |
8e04817f AC |
17721 | This section describes characteristics of architectures that affect |
17722 | all uses of @value{GDBN} with the architecture, both native and cross. | |
104c1213 | 17723 | |
8e04817f | 17724 | @menu |
9c16f35a | 17725 | * i386:: |
8e04817f AC |
17726 | * A29K:: |
17727 | * Alpha:: | |
17728 | * MIPS:: | |
a64548ea | 17729 | * HPPA:: HP PA architecture |
23d964e7 | 17730 | * SPU:: Cell Broadband Engine SPU architecture |
4acd40f3 | 17731 | * PowerPC:: |
8e04817f | 17732 | @end menu |
104c1213 | 17733 | |
9c16f35a | 17734 | @node i386 |
db2e3e2e | 17735 | @subsection x86 Architecture-specific Issues |
9c16f35a EZ |
17736 | |
17737 | @table @code | |
17738 | @item set struct-convention @var{mode} | |
17739 | @kindex set struct-convention | |
17740 | @cindex struct return convention | |
17741 | @cindex struct/union returned in registers | |
17742 | Set the convention used by the inferior to return @code{struct}s and | |
17743 | @code{union}s from functions to @var{mode}. Possible values of | |
17744 | @var{mode} are @code{"pcc"}, @code{"reg"}, and @code{"default"} (the | |
17745 | default). @code{"default"} or @code{"pcc"} means that @code{struct}s | |
17746 | are returned on the stack, while @code{"reg"} means that a | |
17747 | @code{struct} or a @code{union} whose size is 1, 2, 4, or 8 bytes will | |
17748 | be returned in a register. | |
17749 | ||
17750 | @item show struct-convention | |
17751 | @kindex show struct-convention | |
17752 | Show the current setting of the convention to return @code{struct}s | |
17753 | from functions. | |
17754 | @end table | |
17755 | ||
8e04817f AC |
17756 | @node A29K |
17757 | @subsection A29K | |
104c1213 JM |
17758 | |
17759 | @table @code | |
104c1213 | 17760 | |
8e04817f AC |
17761 | @kindex set rstack_high_address |
17762 | @cindex AMD 29K register stack | |
17763 | @cindex register stack, AMD29K | |
17764 | @item set rstack_high_address @var{address} | |
17765 | On AMD 29000 family processors, registers are saved in a separate | |
17766 | @dfn{register stack}. There is no way for @value{GDBN} to determine the | |
17767 | extent of this stack. Normally, @value{GDBN} just assumes that the | |
17768 | stack is ``large enough''. This may result in @value{GDBN} referencing | |
17769 | memory locations that do not exist. If necessary, you can get around | |
17770 | this problem by specifying the ending address of the register stack with | |
17771 | the @code{set rstack_high_address} command. The argument should be an | |
17772 | address, which you probably want to precede with @samp{0x} to specify in | |
17773 | hexadecimal. | |
104c1213 | 17774 | |
8e04817f AC |
17775 | @kindex show rstack_high_address |
17776 | @item show rstack_high_address | |
17777 | Display the current limit of the register stack, on AMD 29000 family | |
17778 | processors. | |
104c1213 | 17779 | |
8e04817f | 17780 | @end table |
104c1213 | 17781 | |
8e04817f AC |
17782 | @node Alpha |
17783 | @subsection Alpha | |
104c1213 | 17784 | |
8e04817f | 17785 | See the following section. |
104c1213 | 17786 | |
8e04817f AC |
17787 | @node MIPS |
17788 | @subsection MIPS | |
104c1213 | 17789 | |
8e04817f AC |
17790 | @cindex stack on Alpha |
17791 | @cindex stack on MIPS | |
17792 | @cindex Alpha stack | |
17793 | @cindex MIPS stack | |
17794 | Alpha- and MIPS-based computers use an unusual stack frame, which | |
17795 | sometimes requires @value{GDBN} to search backward in the object code to | |
17796 | find the beginning of a function. | |
104c1213 | 17797 | |
8e04817f AC |
17798 | @cindex response time, MIPS debugging |
17799 | To improve response time (especially for embedded applications, where | |
17800 | @value{GDBN} may be restricted to a slow serial line for this search) | |
17801 | you may want to limit the size of this search, using one of these | |
17802 | commands: | |
104c1213 | 17803 | |
8e04817f AC |
17804 | @table @code |
17805 | @cindex @code{heuristic-fence-post} (Alpha, MIPS) | |
17806 | @item set heuristic-fence-post @var{limit} | |
17807 | Restrict @value{GDBN} to examining at most @var{limit} bytes in its | |
17808 | search for the beginning of a function. A value of @var{0} (the | |
17809 | default) means there is no limit. However, except for @var{0}, the | |
17810 | larger the limit the more bytes @code{heuristic-fence-post} must search | |
e2f4edfd EZ |
17811 | and therefore the longer it takes to run. You should only need to use |
17812 | this command when debugging a stripped executable. | |
104c1213 | 17813 | |
8e04817f AC |
17814 | @item show heuristic-fence-post |
17815 | Display the current limit. | |
17816 | @end table | |
104c1213 JM |
17817 | |
17818 | @noindent | |
8e04817f AC |
17819 | These commands are available @emph{only} when @value{GDBN} is configured |
17820 | for debugging programs on Alpha or MIPS processors. | |
104c1213 | 17821 | |
a64548ea EZ |
17822 | Several MIPS-specific commands are available when debugging MIPS |
17823 | programs: | |
17824 | ||
17825 | @table @code | |
a64548ea EZ |
17826 | @item set mips abi @var{arg} |
17827 | @kindex set mips abi | |
17828 | @cindex set ABI for MIPS | |
17829 | Tell @value{GDBN} which MIPS ABI is used by the inferior. Possible | |
17830 | values of @var{arg} are: | |
17831 | ||
17832 | @table @samp | |
17833 | @item auto | |
17834 | The default ABI associated with the current binary (this is the | |
17835 | default). | |
17836 | @item o32 | |
17837 | @item o64 | |
17838 | @item n32 | |
17839 | @item n64 | |
17840 | @item eabi32 | |
17841 | @item eabi64 | |
17842 | @item auto | |
17843 | @end table | |
17844 | ||
17845 | @item show mips abi | |
17846 | @kindex show mips abi | |
17847 | Show the MIPS ABI used by @value{GDBN} to debug the inferior. | |
17848 | ||
17849 | @item set mipsfpu | |
17850 | @itemx show mipsfpu | |
17851 | @xref{MIPS Embedded, set mipsfpu}. | |
17852 | ||
17853 | @item set mips mask-address @var{arg} | |
17854 | @kindex set mips mask-address | |
17855 | @cindex MIPS addresses, masking | |
17856 | This command determines whether the most-significant 32 bits of 64-bit | |
17857 | MIPS addresses are masked off. The argument @var{arg} can be | |
17858 | @samp{on}, @samp{off}, or @samp{auto}. The latter is the default | |
17859 | setting, which lets @value{GDBN} determine the correct value. | |
17860 | ||
17861 | @item show mips mask-address | |
17862 | @kindex show mips mask-address | |
17863 | Show whether the upper 32 bits of MIPS addresses are masked off or | |
17864 | not. | |
17865 | ||
17866 | @item set remote-mips64-transfers-32bit-regs | |
17867 | @kindex set remote-mips64-transfers-32bit-regs | |
17868 | This command controls compatibility with 64-bit MIPS targets that | |
17869 | transfer data in 32-bit quantities. If you have an old MIPS 64 target | |
17870 | that transfers 32 bits for some registers, like @sc{sr} and @sc{fsr}, | |
17871 | and 64 bits for other registers, set this option to @samp{on}. | |
17872 | ||
17873 | @item show remote-mips64-transfers-32bit-regs | |
17874 | @kindex show remote-mips64-transfers-32bit-regs | |
17875 | Show the current setting of compatibility with older MIPS 64 targets. | |
17876 | ||
17877 | @item set debug mips | |
17878 | @kindex set debug mips | |
17879 | This command turns on and off debugging messages for the MIPS-specific | |
17880 | target code in @value{GDBN}. | |
17881 | ||
17882 | @item show debug mips | |
17883 | @kindex show debug mips | |
17884 | Show the current setting of MIPS debugging messages. | |
17885 | @end table | |
17886 | ||
17887 | ||
17888 | @node HPPA | |
17889 | @subsection HPPA | |
17890 | @cindex HPPA support | |
17891 | ||
d3e8051b | 17892 | When @value{GDBN} is debugging the HP PA architecture, it provides the |
a64548ea EZ |
17893 | following special commands: |
17894 | ||
17895 | @table @code | |
17896 | @item set debug hppa | |
17897 | @kindex set debug hppa | |
db2e3e2e | 17898 | This command determines whether HPPA architecture-specific debugging |
a64548ea EZ |
17899 | messages are to be displayed. |
17900 | ||
17901 | @item show debug hppa | |
17902 | Show whether HPPA debugging messages are displayed. | |
17903 | ||
17904 | @item maint print unwind @var{address} | |
17905 | @kindex maint print unwind@r{, HPPA} | |
17906 | This command displays the contents of the unwind table entry at the | |
17907 | given @var{address}. | |
17908 | ||
17909 | @end table | |
17910 | ||
104c1213 | 17911 | |
23d964e7 UW |
17912 | @node SPU |
17913 | @subsection Cell Broadband Engine SPU architecture | |
17914 | @cindex Cell Broadband Engine | |
17915 | @cindex SPU | |
17916 | ||
17917 | When @value{GDBN} is debugging the Cell Broadband Engine SPU architecture, | |
17918 | it provides the following special commands: | |
17919 | ||
17920 | @table @code | |
17921 | @item info spu event | |
17922 | @kindex info spu | |
17923 | Display SPU event facility status. Shows current event mask | |
17924 | and pending event status. | |
17925 | ||
17926 | @item info spu signal | |
17927 | Display SPU signal notification facility status. Shows pending | |
17928 | signal-control word and signal notification mode of both signal | |
17929 | notification channels. | |
17930 | ||
17931 | @item info spu mailbox | |
17932 | Display SPU mailbox facility status. Shows all pending entries, | |
17933 | in order of processing, in each of the SPU Write Outbound, | |
17934 | SPU Write Outbound Interrupt, and SPU Read Inbound mailboxes. | |
17935 | ||
17936 | @item info spu dma | |
17937 | Display MFC DMA status. Shows all pending commands in the MFC | |
17938 | DMA queue. For each entry, opcode, tag, class IDs, effective | |
17939 | and local store addresses and transfer size are shown. | |
17940 | ||
17941 | @item info spu proxydma | |
17942 | Display MFC Proxy-DMA status. Shows all pending commands in the MFC | |
17943 | Proxy-DMA queue. For each entry, opcode, tag, class IDs, effective | |
17944 | and local store addresses and transfer size are shown. | |
17945 | ||
17946 | @end table | |
17947 | ||
3285f3fe UW |
17948 | When @value{GDBN} is debugging a combined PowerPC/SPU application |
17949 | on the Cell Broadband Engine, it provides in addition the following | |
17950 | special commands: | |
17951 | ||
17952 | @table @code | |
17953 | @item set spu stop-on-load @var{arg} | |
17954 | @kindex set spu | |
17955 | Set whether to stop for new SPE threads. When set to @code{on}, @value{GDBN} | |
17956 | will give control to the user when a new SPE thread enters its @code{main} | |
17957 | function. The default is @code{off}. | |
17958 | ||
17959 | @item show spu stop-on-load | |
17960 | @kindex show spu | |
17961 | Show whether to stop for new SPE threads. | |
17962 | ||
ff1a52c6 UW |
17963 | @item set spu auto-flush-cache @var{arg} |
17964 | Set whether to automatically flush the software-managed cache. When set to | |
17965 | @code{on}, @value{GDBN} will automatically cause the SPE software-managed | |
17966 | cache to be flushed whenever SPE execution stops. This provides a consistent | |
17967 | view of PowerPC memory that is accessed via the cache. If an application | |
17968 | does not use the software-managed cache, this option has no effect. | |
17969 | ||
17970 | @item show spu auto-flush-cache | |
17971 | Show whether to automatically flush the software-managed cache. | |
17972 | ||
3285f3fe UW |
17973 | @end table |
17974 | ||
4acd40f3 TJB |
17975 | @node PowerPC |
17976 | @subsection PowerPC | |
17977 | @cindex PowerPC architecture | |
17978 | ||
17979 | When @value{GDBN} is debugging the PowerPC architecture, it provides a set of | |
17980 | pseudo-registers to enable inspection of 128-bit wide Decimal Floating Point | |
17981 | numbers stored in the floating point registers. These values must be stored | |
17982 | in two consecutive registers, always starting at an even register like | |
17983 | @code{f0} or @code{f2}. | |
17984 | ||
17985 | The pseudo-registers go from @code{$dl0} through @code{$dl15}, and are formed | |
17986 | by joining the even/odd register pairs @code{f0} and @code{f1} for @code{$dl0}, | |
17987 | @code{f2} and @code{f3} for @code{$dl1} and so on. | |
17988 | ||
aeac0ff9 | 17989 | For POWER7 processors, @value{GDBN} provides a set of pseudo-registers, the 64-bit |
677c5bb1 LM |
17990 | wide Extended Floating Point Registers (@samp{f32} through @samp{f63}). |
17991 | ||
23d964e7 | 17992 | |
8e04817f AC |
17993 | @node Controlling GDB |
17994 | @chapter Controlling @value{GDBN} | |
17995 | ||
17996 | You can alter the way @value{GDBN} interacts with you by using the | |
17997 | @code{set} command. For commands controlling how @value{GDBN} displays | |
79a6e687 | 17998 | data, see @ref{Print Settings, ,Print Settings}. Other settings are |
8e04817f AC |
17999 | described here. |
18000 | ||
18001 | @menu | |
18002 | * Prompt:: Prompt | |
18003 | * Editing:: Command editing | |
d620b259 | 18004 | * Command History:: Command history |
8e04817f AC |
18005 | * Screen Size:: Screen size |
18006 | * Numbers:: Numbers | |
1e698235 | 18007 | * ABI:: Configuring the current ABI |
8e04817f AC |
18008 | * Messages/Warnings:: Optional warnings and messages |
18009 | * Debugging Output:: Optional messages about internal happenings | |
14fb1bac | 18010 | * Other Misc Settings:: Other Miscellaneous Settings |
8e04817f AC |
18011 | @end menu |
18012 | ||
18013 | @node Prompt | |
18014 | @section Prompt | |
104c1213 | 18015 | |
8e04817f | 18016 | @cindex prompt |
104c1213 | 18017 | |
8e04817f AC |
18018 | @value{GDBN} indicates its readiness to read a command by printing a string |
18019 | called the @dfn{prompt}. This string is normally @samp{(@value{GDBP})}. You | |
18020 | can change the prompt string with the @code{set prompt} command. For | |
18021 | instance, when debugging @value{GDBN} with @value{GDBN}, it is useful to change | |
18022 | the prompt in one of the @value{GDBN} sessions so that you can always tell | |
18023 | which one you are talking to. | |
104c1213 | 18024 | |
8e04817f AC |
18025 | @emph{Note:} @code{set prompt} does not add a space for you after the |
18026 | prompt you set. This allows you to set a prompt which ends in a space | |
18027 | or a prompt that does not. | |
104c1213 | 18028 | |
8e04817f AC |
18029 | @table @code |
18030 | @kindex set prompt | |
18031 | @item set prompt @var{newprompt} | |
18032 | Directs @value{GDBN} to use @var{newprompt} as its prompt string henceforth. | |
104c1213 | 18033 | |
8e04817f AC |
18034 | @kindex show prompt |
18035 | @item show prompt | |
18036 | Prints a line of the form: @samp{Gdb's prompt is: @var{your-prompt}} | |
104c1213 JM |
18037 | @end table |
18038 | ||
8e04817f | 18039 | @node Editing |
79a6e687 | 18040 | @section Command Editing |
8e04817f AC |
18041 | @cindex readline |
18042 | @cindex command line editing | |
104c1213 | 18043 | |
703663ab | 18044 | @value{GDBN} reads its input commands via the @dfn{Readline} interface. This |
8e04817f AC |
18045 | @sc{gnu} library provides consistent behavior for programs which provide a |
18046 | command line interface to the user. Advantages are @sc{gnu} Emacs-style | |
18047 | or @dfn{vi}-style inline editing of commands, @code{csh}-like history | |
18048 | substitution, and a storage and recall of command history across | |
18049 | debugging sessions. | |
104c1213 | 18050 | |
8e04817f AC |
18051 | You may control the behavior of command line editing in @value{GDBN} with the |
18052 | command @code{set}. | |
104c1213 | 18053 | |
8e04817f AC |
18054 | @table @code |
18055 | @kindex set editing | |
18056 | @cindex editing | |
18057 | @item set editing | |
18058 | @itemx set editing on | |
18059 | Enable command line editing (enabled by default). | |
104c1213 | 18060 | |
8e04817f AC |
18061 | @item set editing off |
18062 | Disable command line editing. | |
104c1213 | 18063 | |
8e04817f AC |
18064 | @kindex show editing |
18065 | @item show editing | |
18066 | Show whether command line editing is enabled. | |
104c1213 JM |
18067 | @end table |
18068 | ||
703663ab EZ |
18069 | @xref{Command Line Editing}, for more details about the Readline |
18070 | interface. Users unfamiliar with @sc{gnu} Emacs or @code{vi} are | |
18071 | encouraged to read that chapter. | |
18072 | ||
d620b259 | 18073 | @node Command History |
79a6e687 | 18074 | @section Command History |
703663ab | 18075 | @cindex command history |
8e04817f AC |
18076 | |
18077 | @value{GDBN} can keep track of the commands you type during your | |
18078 | debugging sessions, so that you can be certain of precisely what | |
18079 | happened. Use these commands to manage the @value{GDBN} command | |
18080 | history facility. | |
104c1213 | 18081 | |
703663ab EZ |
18082 | @value{GDBN} uses the @sc{gnu} History library, a part of the Readline |
18083 | package, to provide the history facility. @xref{Using History | |
18084 | Interactively}, for the detailed description of the History library. | |
18085 | ||
d620b259 | 18086 | To issue a command to @value{GDBN} without affecting certain aspects of |
9e6c4bd5 NR |
18087 | the state which is seen by users, prefix it with @samp{server } |
18088 | (@pxref{Server Prefix}). This | |
d620b259 NR |
18089 | means that this command will not affect the command history, nor will it |
18090 | affect @value{GDBN}'s notion of which command to repeat if @key{RET} is | |
18091 | pressed on a line by itself. | |
18092 | ||
18093 | @cindex @code{server}, command prefix | |
18094 | The server prefix does not affect the recording of values into the value | |
18095 | history; to print a value without recording it into the value history, | |
18096 | use the @code{output} command instead of the @code{print} command. | |
18097 | ||
703663ab EZ |
18098 | Here is the description of @value{GDBN} commands related to command |
18099 | history. | |
18100 | ||
104c1213 | 18101 | @table @code |
8e04817f AC |
18102 | @cindex history substitution |
18103 | @cindex history file | |
18104 | @kindex set history filename | |
4644b6e3 | 18105 | @cindex @env{GDBHISTFILE}, environment variable |
8e04817f AC |
18106 | @item set history filename @var{fname} |
18107 | Set the name of the @value{GDBN} command history file to @var{fname}. | |
18108 | This is the file where @value{GDBN} reads an initial command history | |
18109 | list, and where it writes the command history from this session when it | |
18110 | exits. You can access this list through history expansion or through | |
18111 | the history command editing characters listed below. This file defaults | |
18112 | to the value of the environment variable @code{GDBHISTFILE}, or to | |
18113 | @file{./.gdb_history} (@file{./_gdb_history} on MS-DOS) if this variable | |
18114 | is not set. | |
104c1213 | 18115 | |
9c16f35a EZ |
18116 | @cindex save command history |
18117 | @kindex set history save | |
8e04817f AC |
18118 | @item set history save |
18119 | @itemx set history save on | |
18120 | Record command history in a file, whose name may be specified with the | |
18121 | @code{set history filename} command. By default, this option is disabled. | |
104c1213 | 18122 | |
8e04817f AC |
18123 | @item set history save off |
18124 | Stop recording command history in a file. | |
104c1213 | 18125 | |
8e04817f | 18126 | @cindex history size |
9c16f35a | 18127 | @kindex set history size |
6fc08d32 | 18128 | @cindex @env{HISTSIZE}, environment variable |
8e04817f AC |
18129 | @item set history size @var{size} |
18130 | Set the number of commands which @value{GDBN} keeps in its history list. | |
18131 | This defaults to the value of the environment variable | |
18132 | @code{HISTSIZE}, or to 256 if this variable is not set. | |
104c1213 JM |
18133 | @end table |
18134 | ||
8e04817f | 18135 | History expansion assigns special meaning to the character @kbd{!}. |
703663ab | 18136 | @xref{Event Designators}, for more details. |
8e04817f | 18137 | |
703663ab | 18138 | @cindex history expansion, turn on/off |
8e04817f AC |
18139 | Since @kbd{!} is also the logical not operator in C, history expansion |
18140 | is off by default. If you decide to enable history expansion with the | |
18141 | @code{set history expansion on} command, you may sometimes need to | |
18142 | follow @kbd{!} (when it is used as logical not, in an expression) with | |
18143 | a space or a tab to prevent it from being expanded. The readline | |
18144 | history facilities do not attempt substitution on the strings | |
18145 | @kbd{!=} and @kbd{!(}, even when history expansion is enabled. | |
18146 | ||
18147 | The commands to control history expansion are: | |
104c1213 JM |
18148 | |
18149 | @table @code | |
8e04817f AC |
18150 | @item set history expansion on |
18151 | @itemx set history expansion | |
703663ab | 18152 | @kindex set history expansion |
8e04817f | 18153 | Enable history expansion. History expansion is off by default. |
104c1213 | 18154 | |
8e04817f AC |
18155 | @item set history expansion off |
18156 | Disable history expansion. | |
104c1213 | 18157 | |
8e04817f AC |
18158 | @c @group |
18159 | @kindex show history | |
18160 | @item show history | |
18161 | @itemx show history filename | |
18162 | @itemx show history save | |
18163 | @itemx show history size | |
18164 | @itemx show history expansion | |
18165 | These commands display the state of the @value{GDBN} history parameters. | |
18166 | @code{show history} by itself displays all four states. | |
18167 | @c @end group | |
18168 | @end table | |
18169 | ||
18170 | @table @code | |
9c16f35a EZ |
18171 | @kindex show commands |
18172 | @cindex show last commands | |
18173 | @cindex display command history | |
8e04817f AC |
18174 | @item show commands |
18175 | Display the last ten commands in the command history. | |
104c1213 | 18176 | |
8e04817f AC |
18177 | @item show commands @var{n} |
18178 | Print ten commands centered on command number @var{n}. | |
18179 | ||
18180 | @item show commands + | |
18181 | Print ten commands just after the commands last printed. | |
104c1213 JM |
18182 | @end table |
18183 | ||
8e04817f | 18184 | @node Screen Size |
79a6e687 | 18185 | @section Screen Size |
8e04817f AC |
18186 | @cindex size of screen |
18187 | @cindex pauses in output | |
104c1213 | 18188 | |
8e04817f AC |
18189 | Certain commands to @value{GDBN} may produce large amounts of |
18190 | information output to the screen. To help you read all of it, | |
18191 | @value{GDBN} pauses and asks you for input at the end of each page of | |
18192 | output. Type @key{RET} when you want to continue the output, or @kbd{q} | |
18193 | to discard the remaining output. Also, the screen width setting | |
18194 | determines when to wrap lines of output. Depending on what is being | |
18195 | printed, @value{GDBN} tries to break the line at a readable place, | |
18196 | rather than simply letting it overflow onto the following line. | |
18197 | ||
18198 | Normally @value{GDBN} knows the size of the screen from the terminal | |
18199 | driver software. For example, on Unix @value{GDBN} uses the termcap data base | |
18200 | together with the value of the @code{TERM} environment variable and the | |
18201 | @code{stty rows} and @code{stty cols} settings. If this is not correct, | |
18202 | you can override it with the @code{set height} and @code{set | |
18203 | width} commands: | |
18204 | ||
18205 | @table @code | |
18206 | @kindex set height | |
18207 | @kindex set width | |
18208 | @kindex show width | |
18209 | @kindex show height | |
18210 | @item set height @var{lpp} | |
18211 | @itemx show height | |
18212 | @itemx set width @var{cpl} | |
18213 | @itemx show width | |
18214 | These @code{set} commands specify a screen height of @var{lpp} lines and | |
18215 | a screen width of @var{cpl} characters. The associated @code{show} | |
18216 | commands display the current settings. | |
104c1213 | 18217 | |
8e04817f AC |
18218 | If you specify a height of zero lines, @value{GDBN} does not pause during |
18219 | output no matter how long the output is. This is useful if output is to a | |
18220 | file or to an editor buffer. | |
104c1213 | 18221 | |
8e04817f AC |
18222 | Likewise, you can specify @samp{set width 0} to prevent @value{GDBN} |
18223 | from wrapping its output. | |
9c16f35a EZ |
18224 | |
18225 | @item set pagination on | |
18226 | @itemx set pagination off | |
18227 | @kindex set pagination | |
18228 | Turn the output pagination on or off; the default is on. Turning | |
18229 | pagination off is the alternative to @code{set height 0}. | |
18230 | ||
18231 | @item show pagination | |
18232 | @kindex show pagination | |
18233 | Show the current pagination mode. | |
104c1213 JM |
18234 | @end table |
18235 | ||
8e04817f AC |
18236 | @node Numbers |
18237 | @section Numbers | |
18238 | @cindex number representation | |
18239 | @cindex entering numbers | |
104c1213 | 18240 | |
8e04817f AC |
18241 | You can always enter numbers in octal, decimal, or hexadecimal in |
18242 | @value{GDBN} by the usual conventions: octal numbers begin with | |
18243 | @samp{0}, decimal numbers end with @samp{.}, and hexadecimal numbers | |
eb2dae08 EZ |
18244 | begin with @samp{0x}. Numbers that neither begin with @samp{0} or |
18245 | @samp{0x}, nor end with a @samp{.} are, by default, entered in base | |
18246 | 10; likewise, the default display for numbers---when no particular | |
18247 | format is specified---is base 10. You can change the default base for | |
18248 | both input and output with the commands described below. | |
104c1213 | 18249 | |
8e04817f AC |
18250 | @table @code |
18251 | @kindex set input-radix | |
18252 | @item set input-radix @var{base} | |
18253 | Set the default base for numeric input. Supported choices | |
18254 | for @var{base} are decimal 8, 10, or 16. @var{base} must itself be | |
eb2dae08 | 18255 | specified either unambiguously or using the current input radix; for |
8e04817f | 18256 | example, any of |
104c1213 | 18257 | |
8e04817f | 18258 | @smallexample |
9c16f35a EZ |
18259 | set input-radix 012 |
18260 | set input-radix 10. | |
18261 | set input-radix 0xa | |
8e04817f | 18262 | @end smallexample |
104c1213 | 18263 | |
8e04817f | 18264 | @noindent |
9c16f35a | 18265 | sets the input base to decimal. On the other hand, @samp{set input-radix 10} |
eb2dae08 EZ |
18266 | leaves the input radix unchanged, no matter what it was, since |
18267 | @samp{10}, being without any leading or trailing signs of its base, is | |
18268 | interpreted in the current radix. Thus, if the current radix is 16, | |
18269 | @samp{10} is interpreted in hex, i.e.@: as 16 decimal, which doesn't | |
18270 | change the radix. | |
104c1213 | 18271 | |
8e04817f AC |
18272 | @kindex set output-radix |
18273 | @item set output-radix @var{base} | |
18274 | Set the default base for numeric display. Supported choices | |
18275 | for @var{base} are decimal 8, 10, or 16. @var{base} must itself be | |
eb2dae08 | 18276 | specified either unambiguously or using the current input radix. |
104c1213 | 18277 | |
8e04817f AC |
18278 | @kindex show input-radix |
18279 | @item show input-radix | |
18280 | Display the current default base for numeric input. | |
104c1213 | 18281 | |
8e04817f AC |
18282 | @kindex show output-radix |
18283 | @item show output-radix | |
18284 | Display the current default base for numeric display. | |
9c16f35a EZ |
18285 | |
18286 | @item set radix @r{[}@var{base}@r{]} | |
18287 | @itemx show radix | |
18288 | @kindex set radix | |
18289 | @kindex show radix | |
18290 | These commands set and show the default base for both input and output | |
18291 | of numbers. @code{set radix} sets the radix of input and output to | |
18292 | the same base; without an argument, it resets the radix back to its | |
18293 | default value of 10. | |
18294 | ||
8e04817f | 18295 | @end table |
104c1213 | 18296 | |
1e698235 | 18297 | @node ABI |
79a6e687 | 18298 | @section Configuring the Current ABI |
1e698235 DJ |
18299 | |
18300 | @value{GDBN} can determine the @dfn{ABI} (Application Binary Interface) of your | |
18301 | application automatically. However, sometimes you need to override its | |
18302 | conclusions. Use these commands to manage @value{GDBN}'s view of the | |
18303 | current ABI. | |
18304 | ||
98b45e30 DJ |
18305 | @cindex OS ABI |
18306 | @kindex set osabi | |
b4e9345d | 18307 | @kindex show osabi |
98b45e30 DJ |
18308 | |
18309 | One @value{GDBN} configuration can debug binaries for multiple operating | |
b383017d | 18310 | system targets, either via remote debugging or native emulation. |
98b45e30 DJ |
18311 | @value{GDBN} will autodetect the @dfn{OS ABI} (Operating System ABI) in use, |
18312 | but you can override its conclusion using the @code{set osabi} command. | |
18313 | One example where this is useful is in debugging of binaries which use | |
18314 | an alternate C library (e.g.@: @sc{uClibc} for @sc{gnu}/Linux) which does | |
18315 | not have the same identifying marks that the standard C library for your | |
18316 | platform provides. | |
18317 | ||
18318 | @table @code | |
18319 | @item show osabi | |
18320 | Show the OS ABI currently in use. | |
18321 | ||
18322 | @item set osabi | |
18323 | With no argument, show the list of registered available OS ABI's. | |
18324 | ||
18325 | @item set osabi @var{abi} | |
18326 | Set the current OS ABI to @var{abi}. | |
18327 | @end table | |
18328 | ||
1e698235 | 18329 | @cindex float promotion |
1e698235 DJ |
18330 | |
18331 | Generally, the way that an argument of type @code{float} is passed to a | |
18332 | function depends on whether the function is prototyped. For a prototyped | |
18333 | (i.e.@: ANSI/ISO style) function, @code{float} arguments are passed unchanged, | |
18334 | according to the architecture's convention for @code{float}. For unprototyped | |
18335 | (i.e.@: K&R style) functions, @code{float} arguments are first promoted to type | |
18336 | @code{double} and then passed. | |
18337 | ||
18338 | Unfortunately, some forms of debug information do not reliably indicate whether | |
18339 | a function is prototyped. If @value{GDBN} calls a function that is not marked | |
18340 | as prototyped, it consults @kbd{set coerce-float-to-double}. | |
18341 | ||
18342 | @table @code | |
a8f24a35 | 18343 | @kindex set coerce-float-to-double |
1e698235 DJ |
18344 | @item set coerce-float-to-double |
18345 | @itemx set coerce-float-to-double on | |
18346 | Arguments of type @code{float} will be promoted to @code{double} when passed | |
18347 | to an unprototyped function. This is the default setting. | |
18348 | ||
18349 | @item set coerce-float-to-double off | |
18350 | Arguments of type @code{float} will be passed directly to unprototyped | |
18351 | functions. | |
9c16f35a EZ |
18352 | |
18353 | @kindex show coerce-float-to-double | |
18354 | @item show coerce-float-to-double | |
18355 | Show the current setting of promoting @code{float} to @code{double}. | |
1e698235 DJ |
18356 | @end table |
18357 | ||
f1212245 DJ |
18358 | @kindex set cp-abi |
18359 | @kindex show cp-abi | |
18360 | @value{GDBN} needs to know the ABI used for your program's C@t{++} | |
18361 | objects. The correct C@t{++} ABI depends on which C@t{++} compiler was | |
18362 | used to build your application. @value{GDBN} only fully supports | |
18363 | programs with a single C@t{++} ABI; if your program contains code using | |
18364 | multiple C@t{++} ABI's or if @value{GDBN} can not identify your | |
18365 | program's ABI correctly, you can tell @value{GDBN} which ABI to use. | |
18366 | Currently supported ABI's include ``gnu-v2'', for @code{g++} versions | |
18367 | before 3.0, ``gnu-v3'', for @code{g++} versions 3.0 and later, and | |
18368 | ``hpaCC'' for the HP ANSI C@t{++} compiler. Other C@t{++} compilers may | |
18369 | use the ``gnu-v2'' or ``gnu-v3'' ABI's as well. The default setting is | |
18370 | ``auto''. | |
18371 | ||
18372 | @table @code | |
18373 | @item show cp-abi | |
18374 | Show the C@t{++} ABI currently in use. | |
18375 | ||
18376 | @item set cp-abi | |
18377 | With no argument, show the list of supported C@t{++} ABI's. | |
18378 | ||
18379 | @item set cp-abi @var{abi} | |
18380 | @itemx set cp-abi auto | |
18381 | Set the current C@t{++} ABI to @var{abi}, or return to automatic detection. | |
18382 | @end table | |
18383 | ||
8e04817f | 18384 | @node Messages/Warnings |
79a6e687 | 18385 | @section Optional Warnings and Messages |
104c1213 | 18386 | |
9c16f35a EZ |
18387 | @cindex verbose operation |
18388 | @cindex optional warnings | |
8e04817f AC |
18389 | By default, @value{GDBN} is silent about its inner workings. If you are |
18390 | running on a slow machine, you may want to use the @code{set verbose} | |
18391 | command. This makes @value{GDBN} tell you when it does a lengthy | |
18392 | internal operation, so you will not think it has crashed. | |
104c1213 | 18393 | |
8e04817f AC |
18394 | Currently, the messages controlled by @code{set verbose} are those |
18395 | which announce that the symbol table for a source file is being read; | |
79a6e687 | 18396 | see @code{symbol-file} in @ref{Files, ,Commands to Specify Files}. |
104c1213 | 18397 | |
8e04817f AC |
18398 | @table @code |
18399 | @kindex set verbose | |
18400 | @item set verbose on | |
18401 | Enables @value{GDBN} output of certain informational messages. | |
104c1213 | 18402 | |
8e04817f AC |
18403 | @item set verbose off |
18404 | Disables @value{GDBN} output of certain informational messages. | |
104c1213 | 18405 | |
8e04817f AC |
18406 | @kindex show verbose |
18407 | @item show verbose | |
18408 | Displays whether @code{set verbose} is on or off. | |
18409 | @end table | |
104c1213 | 18410 | |
8e04817f AC |
18411 | By default, if @value{GDBN} encounters bugs in the symbol table of an |
18412 | object file, it is silent; but if you are debugging a compiler, you may | |
79a6e687 BW |
18413 | find this information useful (@pxref{Symbol Errors, ,Errors Reading |
18414 | Symbol Files}). | |
104c1213 | 18415 | |
8e04817f | 18416 | @table @code |
104c1213 | 18417 | |
8e04817f AC |
18418 | @kindex set complaints |
18419 | @item set complaints @var{limit} | |
18420 | Permits @value{GDBN} to output @var{limit} complaints about each type of | |
18421 | unusual symbols before becoming silent about the problem. Set | |
18422 | @var{limit} to zero to suppress all complaints; set it to a large number | |
18423 | to prevent complaints from being suppressed. | |
104c1213 | 18424 | |
8e04817f AC |
18425 | @kindex show complaints |
18426 | @item show complaints | |
18427 | Displays how many symbol complaints @value{GDBN} is permitted to produce. | |
104c1213 | 18428 | |
8e04817f | 18429 | @end table |
104c1213 | 18430 | |
d837706a | 18431 | @anchor{confirmation requests} |
8e04817f AC |
18432 | By default, @value{GDBN} is cautious, and asks what sometimes seems to be a |
18433 | lot of stupid questions to confirm certain commands. For example, if | |
18434 | you try to run a program which is already running: | |
104c1213 | 18435 | |
474c8240 | 18436 | @smallexample |
8e04817f AC |
18437 | (@value{GDBP}) run |
18438 | The program being debugged has been started already. | |
18439 | Start it from the beginning? (y or n) | |
474c8240 | 18440 | @end smallexample |
104c1213 | 18441 | |
8e04817f AC |
18442 | If you are willing to unflinchingly face the consequences of your own |
18443 | commands, you can disable this ``feature'': | |
104c1213 | 18444 | |
8e04817f | 18445 | @table @code |
104c1213 | 18446 | |
8e04817f AC |
18447 | @kindex set confirm |
18448 | @cindex flinching | |
18449 | @cindex confirmation | |
18450 | @cindex stupid questions | |
18451 | @item set confirm off | |
18452 | Disables confirmation requests. | |
104c1213 | 18453 | |
8e04817f AC |
18454 | @item set confirm on |
18455 | Enables confirmation requests (the default). | |
104c1213 | 18456 | |
8e04817f AC |
18457 | @kindex show confirm |
18458 | @item show confirm | |
18459 | Displays state of confirmation requests. | |
18460 | ||
18461 | @end table | |
104c1213 | 18462 | |
16026cd7 AS |
18463 | @cindex command tracing |
18464 | If you need to debug user-defined commands or sourced files you may find it | |
18465 | useful to enable @dfn{command tracing}. In this mode each command will be | |
18466 | printed as it is executed, prefixed with one or more @samp{+} symbols, the | |
18467 | quantity denoting the call depth of each command. | |
18468 | ||
18469 | @table @code | |
18470 | @kindex set trace-commands | |
18471 | @cindex command scripts, debugging | |
18472 | @item set trace-commands on | |
18473 | Enable command tracing. | |
18474 | @item set trace-commands off | |
18475 | Disable command tracing. | |
18476 | @item show trace-commands | |
18477 | Display the current state of command tracing. | |
18478 | @end table | |
18479 | ||
8e04817f | 18480 | @node Debugging Output |
79a6e687 | 18481 | @section Optional Messages about Internal Happenings |
4644b6e3 EZ |
18482 | @cindex optional debugging messages |
18483 | ||
da316a69 EZ |
18484 | @value{GDBN} has commands that enable optional debugging messages from |
18485 | various @value{GDBN} subsystems; normally these commands are of | |
18486 | interest to @value{GDBN} maintainers, or when reporting a bug. This | |
18487 | section documents those commands. | |
18488 | ||
104c1213 | 18489 | @table @code |
a8f24a35 EZ |
18490 | @kindex set exec-done-display |
18491 | @item set exec-done-display | |
18492 | Turns on or off the notification of asynchronous commands' | |
18493 | completion. When on, @value{GDBN} will print a message when an | |
18494 | asynchronous command finishes its execution. The default is off. | |
18495 | @kindex show exec-done-display | |
18496 | @item show exec-done-display | |
18497 | Displays the current setting of asynchronous command completion | |
18498 | notification. | |
4644b6e3 EZ |
18499 | @kindex set debug |
18500 | @cindex gdbarch debugging info | |
a8f24a35 | 18501 | @cindex architecture debugging info |
8e04817f | 18502 | @item set debug arch |
a8f24a35 | 18503 | Turns on or off display of gdbarch debugging info. The default is off |
4644b6e3 | 18504 | @kindex show debug |
8e04817f AC |
18505 | @item show debug arch |
18506 | Displays the current state of displaying gdbarch debugging info. | |
721c2651 EZ |
18507 | @item set debug aix-thread |
18508 | @cindex AIX threads | |
18509 | Display debugging messages about inner workings of the AIX thread | |
18510 | module. | |
18511 | @item show debug aix-thread | |
18512 | Show the current state of AIX thread debugging info display. | |
d97bc12b DE |
18513 | @item set debug dwarf2-die |
18514 | @cindex DWARF2 DIEs | |
18515 | Dump DWARF2 DIEs after they are read in. | |
18516 | The value is the number of nesting levels to print. | |
18517 | A value of zero turns off the display. | |
18518 | @item show debug dwarf2-die | |
18519 | Show the current state of DWARF2 DIE debugging. | |
237fc4c9 PA |
18520 | @item set debug displaced |
18521 | @cindex displaced stepping debugging info | |
18522 | Turns on or off display of @value{GDBN} debugging info for the | |
18523 | displaced stepping support. The default is off. | |
18524 | @item show debug displaced | |
18525 | Displays the current state of displaying @value{GDBN} debugging info | |
18526 | related to displaced stepping. | |
8e04817f | 18527 | @item set debug event |
4644b6e3 | 18528 | @cindex event debugging info |
a8f24a35 | 18529 | Turns on or off display of @value{GDBN} event debugging info. The |
8e04817f | 18530 | default is off. |
8e04817f AC |
18531 | @item show debug event |
18532 | Displays the current state of displaying @value{GDBN} event debugging | |
18533 | info. | |
8e04817f | 18534 | @item set debug expression |
4644b6e3 | 18535 | @cindex expression debugging info |
721c2651 EZ |
18536 | Turns on or off display of debugging info about @value{GDBN} |
18537 | expression parsing. The default is off. | |
8e04817f | 18538 | @item show debug expression |
721c2651 EZ |
18539 | Displays the current state of displaying debugging info about |
18540 | @value{GDBN} expression parsing. | |
7453dc06 | 18541 | @item set debug frame |
4644b6e3 | 18542 | @cindex frame debugging info |
7453dc06 AC |
18543 | Turns on or off display of @value{GDBN} frame debugging info. The |
18544 | default is off. | |
7453dc06 AC |
18545 | @item show debug frame |
18546 | Displays the current state of displaying @value{GDBN} frame debugging | |
18547 | info. | |
cbe54154 PA |
18548 | @item set debug gnu-nat |
18549 | @cindex @sc{gnu}/Hurd debug messages | |
18550 | Turns on or off debugging messages from the @sc{gnu}/Hurd debug support. | |
18551 | @item show debug gnu-nat | |
18552 | Show the current state of @sc{gnu}/Hurd debugging messages. | |
30e91e0b RC |
18553 | @item set debug infrun |
18554 | @cindex inferior debugging info | |
18555 | Turns on or off display of @value{GDBN} debugging info for running the inferior. | |
18556 | The default is off. @file{infrun.c} contains GDB's runtime state machine used | |
18557 | for implementing operations such as single-stepping the inferior. | |
18558 | @item show debug infrun | |
18559 | Displays the current state of @value{GDBN} inferior debugging. | |
da316a69 EZ |
18560 | @item set debug lin-lwp |
18561 | @cindex @sc{gnu}/Linux LWP debug messages | |
18562 | @cindex Linux lightweight processes | |
721c2651 | 18563 | Turns on or off debugging messages from the Linux LWP debug support. |
da316a69 EZ |
18564 | @item show debug lin-lwp |
18565 | Show the current state of Linux LWP debugging messages. | |
b84876c2 PA |
18566 | @item set debug lin-lwp-async |
18567 | @cindex @sc{gnu}/Linux LWP async debug messages | |
18568 | @cindex Linux lightweight processes | |
18569 | Turns on or off debugging messages from the Linux LWP async debug support. | |
18570 | @item show debug lin-lwp-async | |
18571 | Show the current state of Linux LWP async debugging messages. | |
2b4855ab | 18572 | @item set debug observer |
4644b6e3 | 18573 | @cindex observer debugging info |
2b4855ab AC |
18574 | Turns on or off display of @value{GDBN} observer debugging. This |
18575 | includes info such as the notification of observable events. | |
2b4855ab AC |
18576 | @item show debug observer |
18577 | Displays the current state of observer debugging. | |
8e04817f | 18578 | @item set debug overload |
4644b6e3 | 18579 | @cindex C@t{++} overload debugging info |
8e04817f | 18580 | Turns on or off display of @value{GDBN} C@t{++} overload debugging |
359df76b | 18581 | info. This includes info such as ranking of functions, etc. The default |
8e04817f | 18582 | is off. |
8e04817f AC |
18583 | @item show debug overload |
18584 | Displays the current state of displaying @value{GDBN} C@t{++} overload | |
18585 | debugging info. | |
8e04817f AC |
18586 | @cindex packets, reporting on stdout |
18587 | @cindex serial connections, debugging | |
605a56cb DJ |
18588 | @cindex debug remote protocol |
18589 | @cindex remote protocol debugging | |
18590 | @cindex display remote packets | |
8e04817f AC |
18591 | @item set debug remote |
18592 | Turns on or off display of reports on all packets sent back and forth across | |
18593 | the serial line to the remote machine. The info is printed on the | |
18594 | @value{GDBN} standard output stream. The default is off. | |
8e04817f AC |
18595 | @item show debug remote |
18596 | Displays the state of display of remote packets. | |
8e04817f AC |
18597 | @item set debug serial |
18598 | Turns on or off display of @value{GDBN} serial debugging info. The | |
18599 | default is off. | |
8e04817f AC |
18600 | @item show debug serial |
18601 | Displays the current state of displaying @value{GDBN} serial debugging | |
18602 | info. | |
c45da7e6 EZ |
18603 | @item set debug solib-frv |
18604 | @cindex FR-V shared-library debugging | |
18605 | Turns on or off debugging messages for FR-V shared-library code. | |
18606 | @item show debug solib-frv | |
18607 | Display the current state of FR-V shared-library code debugging | |
18608 | messages. | |
8e04817f | 18609 | @item set debug target |
4644b6e3 | 18610 | @cindex target debugging info |
8e04817f AC |
18611 | Turns on or off display of @value{GDBN} target debugging info. This info |
18612 | includes what is going on at the target level of GDB, as it happens. The | |
701b08bb DJ |
18613 | default is 0. Set it to 1 to track events, and to 2 to also track the |
18614 | value of large memory transfers. Changes to this flag do not take effect | |
18615 | until the next time you connect to a target or use the @code{run} command. | |
8e04817f AC |
18616 | @item show debug target |
18617 | Displays the current state of displaying @value{GDBN} target debugging | |
18618 | info. | |
75feb17d DJ |
18619 | @item set debug timestamp |
18620 | @cindex timestampping debugging info | |
18621 | Turns on or off display of timestamps with @value{GDBN} debugging info. | |
18622 | When enabled, seconds and microseconds are displayed before each debugging | |
18623 | message. | |
18624 | @item show debug timestamp | |
18625 | Displays the current state of displaying timestamps with @value{GDBN} | |
18626 | debugging info. | |
c45da7e6 | 18627 | @item set debugvarobj |
4644b6e3 | 18628 | @cindex variable object debugging info |
8e04817f AC |
18629 | Turns on or off display of @value{GDBN} variable object debugging |
18630 | info. The default is off. | |
c45da7e6 | 18631 | @item show debugvarobj |
8e04817f AC |
18632 | Displays the current state of displaying @value{GDBN} variable object |
18633 | debugging info. | |
e776119f DJ |
18634 | @item set debug xml |
18635 | @cindex XML parser debugging | |
18636 | Turns on or off debugging messages for built-in XML parsers. | |
18637 | @item show debug xml | |
18638 | Displays the current state of XML debugging messages. | |
8e04817f | 18639 | @end table |
104c1213 | 18640 | |
14fb1bac JB |
18641 | @node Other Misc Settings |
18642 | @section Other Miscellaneous Settings | |
18643 | @cindex miscellaneous settings | |
18644 | ||
18645 | @table @code | |
18646 | @kindex set interactive-mode | |
18647 | @item set interactive-mode | |
18648 | If @code{on}, forces @value{GDBN} to operate interactively. | |
18649 | If @code{off}, forces @value{GDBN} to operate non-interactively, | |
18650 | If @code{auto} (the default), @value{GDBN} guesses which mode to use, | |
18651 | based on whether the debugger was started in a terminal or not. | |
18652 | ||
18653 | In the vast majority of cases, the debugger should be able to guess | |
18654 | correctly which mode should be used. But this setting can be useful | |
18655 | in certain specific cases, such as running a MinGW @value{GDBN} | |
18656 | inside a cygwin window. | |
18657 | ||
18658 | @kindex show interactive-mode | |
18659 | @item show interactive-mode | |
18660 | Displays whether the debugger is operating in interactive mode or not. | |
18661 | @end table | |
18662 | ||
d57a3c85 TJB |
18663 | @node Extending GDB |
18664 | @chapter Extending @value{GDBN} | |
18665 | @cindex extending GDB | |
18666 | ||
18667 | @value{GDBN} provides two mechanisms for extension. The first is based | |
18668 | on composition of @value{GDBN} commands, and the second is based on the | |
18669 | Python scripting language. | |
18670 | ||
18671 | @menu | |
18672 | * Sequences:: Canned Sequences of Commands | |
18673 | * Python:: Scripting @value{GDBN} using Python | |
18674 | @end menu | |
18675 | ||
8e04817f | 18676 | @node Sequences |
d57a3c85 | 18677 | @section Canned Sequences of Commands |
104c1213 | 18678 | |
8e04817f | 18679 | Aside from breakpoint commands (@pxref{Break Commands, ,Breakpoint |
79a6e687 | 18680 | Command Lists}), @value{GDBN} provides two ways to store sequences of |
8e04817f AC |
18681 | commands for execution as a unit: user-defined commands and command |
18682 | files. | |
104c1213 | 18683 | |
8e04817f | 18684 | @menu |
fcc73fe3 EZ |
18685 | * Define:: How to define your own commands |
18686 | * Hooks:: Hooks for user-defined commands | |
18687 | * Command Files:: How to write scripts of commands to be stored in a file | |
18688 | * Output:: Commands for controlled output | |
8e04817f | 18689 | @end menu |
104c1213 | 18690 | |
8e04817f | 18691 | @node Define |
d57a3c85 | 18692 | @subsection User-defined Commands |
104c1213 | 18693 | |
8e04817f | 18694 | @cindex user-defined command |
fcc73fe3 | 18695 | @cindex arguments, to user-defined commands |
8e04817f AC |
18696 | A @dfn{user-defined command} is a sequence of @value{GDBN} commands to |
18697 | which you assign a new name as a command. This is done with the | |
18698 | @code{define} command. User commands may accept up to 10 arguments | |
18699 | separated by whitespace. Arguments are accessed within the user command | |
c03c782f | 18700 | via @code{$arg0@dots{}$arg9}. A trivial example: |
104c1213 | 18701 | |
8e04817f AC |
18702 | @smallexample |
18703 | define adder | |
18704 | print $arg0 + $arg1 + $arg2 | |
c03c782f | 18705 | end |
8e04817f | 18706 | @end smallexample |
104c1213 JM |
18707 | |
18708 | @noindent | |
8e04817f | 18709 | To execute the command use: |
104c1213 | 18710 | |
8e04817f AC |
18711 | @smallexample |
18712 | adder 1 2 3 | |
18713 | @end smallexample | |
104c1213 | 18714 | |
8e04817f AC |
18715 | @noindent |
18716 | This defines the command @code{adder}, which prints the sum of | |
18717 | its three arguments. Note the arguments are text substitutions, so they may | |
18718 | reference variables, use complex expressions, or even perform inferior | |
18719 | functions calls. | |
104c1213 | 18720 | |
fcc73fe3 EZ |
18721 | @cindex argument count in user-defined commands |
18722 | @cindex how many arguments (user-defined commands) | |
c03c782f AS |
18723 | In addition, @code{$argc} may be used to find out how many arguments have |
18724 | been passed. This expands to a number in the range 0@dots{}10. | |
18725 | ||
18726 | @smallexample | |
18727 | define adder | |
18728 | if $argc == 2 | |
18729 | print $arg0 + $arg1 | |
18730 | end | |
18731 | if $argc == 3 | |
18732 | print $arg0 + $arg1 + $arg2 | |
18733 | end | |
18734 | end | |
18735 | @end smallexample | |
18736 | ||
104c1213 | 18737 | @table @code |
104c1213 | 18738 | |
8e04817f AC |
18739 | @kindex define |
18740 | @item define @var{commandname} | |
18741 | Define a command named @var{commandname}. If there is already a command | |
18742 | by that name, you are asked to confirm that you want to redefine it. | |
adb483fe DJ |
18743 | @var{commandname} may be a bare command name consisting of letters, |
18744 | numbers, dashes, and underscores. It may also start with any predefined | |
18745 | prefix command. For example, @samp{define target my-target} creates | |
18746 | a user-defined @samp{target my-target} command. | |
104c1213 | 18747 | |
8e04817f AC |
18748 | The definition of the command is made up of other @value{GDBN} command lines, |
18749 | which are given following the @code{define} command. The end of these | |
18750 | commands is marked by a line containing @code{end}. | |
104c1213 | 18751 | |
8e04817f | 18752 | @kindex document |
ca91424e | 18753 | @kindex end@r{ (user-defined commands)} |
8e04817f AC |
18754 | @item document @var{commandname} |
18755 | Document the user-defined command @var{commandname}, so that it can be | |
18756 | accessed by @code{help}. The command @var{commandname} must already be | |
18757 | defined. This command reads lines of documentation just as @code{define} | |
18758 | reads the lines of the command definition, ending with @code{end}. | |
18759 | After the @code{document} command is finished, @code{help} on command | |
18760 | @var{commandname} displays the documentation you have written. | |
104c1213 | 18761 | |
8e04817f AC |
18762 | You may use the @code{document} command again to change the |
18763 | documentation of a command. Redefining the command with @code{define} | |
18764 | does not change the documentation. | |
104c1213 | 18765 | |
c45da7e6 EZ |
18766 | @kindex dont-repeat |
18767 | @cindex don't repeat command | |
18768 | @item dont-repeat | |
18769 | Used inside a user-defined command, this tells @value{GDBN} that this | |
18770 | command should not be repeated when the user hits @key{RET} | |
18771 | (@pxref{Command Syntax, repeat last command}). | |
18772 | ||
8e04817f AC |
18773 | @kindex help user-defined |
18774 | @item help user-defined | |
18775 | List all user-defined commands, with the first line of the documentation | |
18776 | (if any) for each. | |
104c1213 | 18777 | |
8e04817f AC |
18778 | @kindex show user |
18779 | @item show user | |
18780 | @itemx show user @var{commandname} | |
18781 | Display the @value{GDBN} commands used to define @var{commandname} (but | |
18782 | not its documentation). If no @var{commandname} is given, display the | |
18783 | definitions for all user-defined commands. | |
104c1213 | 18784 | |
fcc73fe3 | 18785 | @cindex infinite recursion in user-defined commands |
20f01a46 DH |
18786 | @kindex show max-user-call-depth |
18787 | @kindex set max-user-call-depth | |
18788 | @item show max-user-call-depth | |
5ca0cb28 DH |
18789 | @itemx set max-user-call-depth |
18790 | The value of @code{max-user-call-depth} controls how many recursion | |
3f94c067 | 18791 | levels are allowed in user-defined commands before @value{GDBN} suspects an |
5ca0cb28 | 18792 | infinite recursion and aborts the command. |
104c1213 JM |
18793 | @end table |
18794 | ||
fcc73fe3 EZ |
18795 | In addition to the above commands, user-defined commands frequently |
18796 | use control flow commands, described in @ref{Command Files}. | |
18797 | ||
8e04817f AC |
18798 | When user-defined commands are executed, the |
18799 | commands of the definition are not printed. An error in any command | |
18800 | stops execution of the user-defined command. | |
104c1213 | 18801 | |
8e04817f AC |
18802 | If used interactively, commands that would ask for confirmation proceed |
18803 | without asking when used inside a user-defined command. Many @value{GDBN} | |
18804 | commands that normally print messages to say what they are doing omit the | |
18805 | messages when used in a user-defined command. | |
104c1213 | 18806 | |
8e04817f | 18807 | @node Hooks |
d57a3c85 | 18808 | @subsection User-defined Command Hooks |
8e04817f AC |
18809 | @cindex command hooks |
18810 | @cindex hooks, for commands | |
18811 | @cindex hooks, pre-command | |
104c1213 | 18812 | |
8e04817f | 18813 | @kindex hook |
8e04817f AC |
18814 | You may define @dfn{hooks}, which are a special kind of user-defined |
18815 | command. Whenever you run the command @samp{foo}, if the user-defined | |
18816 | command @samp{hook-foo} exists, it is executed (with no arguments) | |
18817 | before that command. | |
104c1213 | 18818 | |
8e04817f AC |
18819 | @cindex hooks, post-command |
18820 | @kindex hookpost | |
8e04817f AC |
18821 | A hook may also be defined which is run after the command you executed. |
18822 | Whenever you run the command @samp{foo}, if the user-defined command | |
18823 | @samp{hookpost-foo} exists, it is executed (with no arguments) after | |
18824 | that command. Post-execution hooks may exist simultaneously with | |
18825 | pre-execution hooks, for the same command. | |
104c1213 | 18826 | |
8e04817f | 18827 | It is valid for a hook to call the command which it hooks. If this |
9f1c6395 | 18828 | occurs, the hook is not re-executed, thereby avoiding infinite recursion. |
104c1213 | 18829 | |
8e04817f AC |
18830 | @c It would be nice if hookpost could be passed a parameter indicating |
18831 | @c if the command it hooks executed properly or not. FIXME! | |
104c1213 | 18832 | |
8e04817f AC |
18833 | @kindex stop@r{, a pseudo-command} |
18834 | In addition, a pseudo-command, @samp{stop} exists. Defining | |
18835 | (@samp{hook-stop}) makes the associated commands execute every time | |
18836 | execution stops in your program: before breakpoint commands are run, | |
18837 | displays are printed, or the stack frame is printed. | |
104c1213 | 18838 | |
8e04817f AC |
18839 | For example, to ignore @code{SIGALRM} signals while |
18840 | single-stepping, but treat them normally during normal execution, | |
18841 | you could define: | |
104c1213 | 18842 | |
474c8240 | 18843 | @smallexample |
8e04817f AC |
18844 | define hook-stop |
18845 | handle SIGALRM nopass | |
18846 | end | |
104c1213 | 18847 | |
8e04817f AC |
18848 | define hook-run |
18849 | handle SIGALRM pass | |
18850 | end | |
104c1213 | 18851 | |
8e04817f | 18852 | define hook-continue |
d3e8051b | 18853 | handle SIGALRM pass |
8e04817f | 18854 | end |
474c8240 | 18855 | @end smallexample |
104c1213 | 18856 | |
d3e8051b | 18857 | As a further example, to hook at the beginning and end of the @code{echo} |
b383017d | 18858 | command, and to add extra text to the beginning and end of the message, |
8e04817f | 18859 | you could define: |
104c1213 | 18860 | |
474c8240 | 18861 | @smallexample |
8e04817f AC |
18862 | define hook-echo |
18863 | echo <<<--- | |
18864 | end | |
104c1213 | 18865 | |
8e04817f AC |
18866 | define hookpost-echo |
18867 | echo --->>>\n | |
18868 | end | |
104c1213 | 18869 | |
8e04817f AC |
18870 | (@value{GDBP}) echo Hello World |
18871 | <<<---Hello World--->>> | |
18872 | (@value{GDBP}) | |
104c1213 | 18873 | |
474c8240 | 18874 | @end smallexample |
104c1213 | 18875 | |
8e04817f AC |
18876 | You can define a hook for any single-word command in @value{GDBN}, but |
18877 | not for command aliases; you should define a hook for the basic command | |
c1468174 | 18878 | name, e.g.@: @code{backtrace} rather than @code{bt}. |
8e04817f AC |
18879 | @c FIXME! So how does Joe User discover whether a command is an alias |
18880 | @c or not? | |
adb483fe DJ |
18881 | You can hook a multi-word command by adding @code{hook-} or |
18882 | @code{hookpost-} to the last word of the command, e.g.@: | |
18883 | @samp{define target hook-remote} to add a hook to @samp{target remote}. | |
18884 | ||
8e04817f AC |
18885 | If an error occurs during the execution of your hook, execution of |
18886 | @value{GDBN} commands stops and @value{GDBN} issues a prompt | |
18887 | (before the command that you actually typed had a chance to run). | |
104c1213 | 18888 | |
8e04817f AC |
18889 | If you try to define a hook which does not match any known command, you |
18890 | get a warning from the @code{define} command. | |
c906108c | 18891 | |
8e04817f | 18892 | @node Command Files |
d57a3c85 | 18893 | @subsection Command Files |
c906108c | 18894 | |
8e04817f | 18895 | @cindex command files |
fcc73fe3 | 18896 | @cindex scripting commands |
6fc08d32 EZ |
18897 | A command file for @value{GDBN} is a text file made of lines that are |
18898 | @value{GDBN} commands. Comments (lines starting with @kbd{#}) may | |
18899 | also be included. An empty line in a command file does nothing; it | |
18900 | does not mean to repeat the last command, as it would from the | |
18901 | terminal. | |
c906108c | 18902 | |
6fc08d32 EZ |
18903 | You can request the execution of a command file with the @code{source} |
18904 | command: | |
c906108c | 18905 | |
8e04817f AC |
18906 | @table @code |
18907 | @kindex source | |
ca91424e | 18908 | @cindex execute commands from a file |
16026cd7 | 18909 | @item source [@code{-v}] @var{filename} |
8e04817f | 18910 | Execute the command file @var{filename}. |
c906108c SS |
18911 | @end table |
18912 | ||
fcc73fe3 EZ |
18913 | The lines in a command file are generally executed sequentially, |
18914 | unless the order of execution is changed by one of the | |
18915 | @emph{flow-control commands} described below. The commands are not | |
a71ec265 DH |
18916 | printed as they are executed. An error in any command terminates |
18917 | execution of the command file and control is returned to the console. | |
c906108c | 18918 | |
4b505b12 AS |
18919 | @value{GDBN} searches for @var{filename} in the current directory and then |
18920 | on the search path (specified with the @samp{directory} command). | |
18921 | ||
16026cd7 AS |
18922 | If @code{-v}, for verbose mode, is given then @value{GDBN} displays |
18923 | each command as it is executed. The option must be given before | |
18924 | @var{filename}, and is interpreted as part of the filename anywhere else. | |
18925 | ||
8e04817f AC |
18926 | Commands that would ask for confirmation if used interactively proceed |
18927 | without asking when used in a command file. Many @value{GDBN} commands that | |
18928 | normally print messages to say what they are doing omit the messages | |
18929 | when called from command files. | |
c906108c | 18930 | |
8e04817f AC |
18931 | @value{GDBN} also accepts command input from standard input. In this |
18932 | mode, normal output goes to standard output and error output goes to | |
18933 | standard error. Errors in a command file supplied on standard input do | |
6fc08d32 | 18934 | not terminate execution of the command file---execution continues with |
8e04817f | 18935 | the next command. |
c906108c | 18936 | |
474c8240 | 18937 | @smallexample |
8e04817f | 18938 | gdb < cmds > log 2>&1 |
474c8240 | 18939 | @end smallexample |
c906108c | 18940 | |
8e04817f AC |
18941 | (The syntax above will vary depending on the shell used.) This example |
18942 | will execute commands from the file @file{cmds}. All output and errors | |
18943 | would be directed to @file{log}. | |
c906108c | 18944 | |
fcc73fe3 EZ |
18945 | Since commands stored on command files tend to be more general than |
18946 | commands typed interactively, they frequently need to deal with | |
18947 | complicated situations, such as different or unexpected values of | |
18948 | variables and symbols, changes in how the program being debugged is | |
18949 | built, etc. @value{GDBN} provides a set of flow-control commands to | |
18950 | deal with these complexities. Using these commands, you can write | |
18951 | complex scripts that loop over data structures, execute commands | |
18952 | conditionally, etc. | |
18953 | ||
18954 | @table @code | |
18955 | @kindex if | |
18956 | @kindex else | |
18957 | @item if | |
18958 | @itemx else | |
18959 | This command allows to include in your script conditionally executed | |
18960 | commands. The @code{if} command takes a single argument, which is an | |
18961 | expression to evaluate. It is followed by a series of commands that | |
18962 | are executed only if the expression is true (its value is nonzero). | |
18963 | There can then optionally be an @code{else} line, followed by a series | |
18964 | of commands that are only executed if the expression was false. The | |
18965 | end of the list is marked by a line containing @code{end}. | |
18966 | ||
18967 | @kindex while | |
18968 | @item while | |
18969 | This command allows to write loops. Its syntax is similar to | |
18970 | @code{if}: the command takes a single argument, which is an expression | |
18971 | to evaluate, and must be followed by the commands to execute, one per | |
18972 | line, terminated by an @code{end}. These commands are called the | |
18973 | @dfn{body} of the loop. The commands in the body of @code{while} are | |
18974 | executed repeatedly as long as the expression evaluates to true. | |
18975 | ||
18976 | @kindex loop_break | |
18977 | @item loop_break | |
18978 | This command exits the @code{while} loop in whose body it is included. | |
18979 | Execution of the script continues after that @code{while}s @code{end} | |
18980 | line. | |
18981 | ||
18982 | @kindex loop_continue | |
18983 | @item loop_continue | |
18984 | This command skips the execution of the rest of the body of commands | |
18985 | in the @code{while} loop in whose body it is included. Execution | |
18986 | branches to the beginning of the @code{while} loop, where it evaluates | |
18987 | the controlling expression. | |
ca91424e EZ |
18988 | |
18989 | @kindex end@r{ (if/else/while commands)} | |
18990 | @item end | |
18991 | Terminate the block of commands that are the body of @code{if}, | |
18992 | @code{else}, or @code{while} flow-control commands. | |
fcc73fe3 EZ |
18993 | @end table |
18994 | ||
18995 | ||
8e04817f | 18996 | @node Output |
d57a3c85 | 18997 | @subsection Commands for Controlled Output |
c906108c | 18998 | |
8e04817f AC |
18999 | During the execution of a command file or a user-defined command, normal |
19000 | @value{GDBN} output is suppressed; the only output that appears is what is | |
19001 | explicitly printed by the commands in the definition. This section | |
19002 | describes three commands useful for generating exactly the output you | |
19003 | want. | |
c906108c SS |
19004 | |
19005 | @table @code | |
8e04817f AC |
19006 | @kindex echo |
19007 | @item echo @var{text} | |
19008 | @c I do not consider backslash-space a standard C escape sequence | |
19009 | @c because it is not in ANSI. | |
19010 | Print @var{text}. Nonprinting characters can be included in | |
19011 | @var{text} using C escape sequences, such as @samp{\n} to print a | |
19012 | newline. @strong{No newline is printed unless you specify one.} | |
19013 | In addition to the standard C escape sequences, a backslash followed | |
19014 | by a space stands for a space. This is useful for displaying a | |
19015 | string with spaces at the beginning or the end, since leading and | |
19016 | trailing spaces are otherwise trimmed from all arguments. | |
19017 | To print @samp{@w{ }and foo =@w{ }}, use the command | |
19018 | @samp{echo \@w{ }and foo = \@w{ }}. | |
c906108c | 19019 | |
8e04817f AC |
19020 | A backslash at the end of @var{text} can be used, as in C, to continue |
19021 | the command onto subsequent lines. For example, | |
c906108c | 19022 | |
474c8240 | 19023 | @smallexample |
8e04817f AC |
19024 | echo This is some text\n\ |
19025 | which is continued\n\ | |
19026 | onto several lines.\n | |
474c8240 | 19027 | @end smallexample |
c906108c | 19028 | |
8e04817f | 19029 | produces the same output as |
c906108c | 19030 | |
474c8240 | 19031 | @smallexample |
8e04817f AC |
19032 | echo This is some text\n |
19033 | echo which is continued\n | |
19034 | echo onto several lines.\n | |
474c8240 | 19035 | @end smallexample |
c906108c | 19036 | |
8e04817f AC |
19037 | @kindex output |
19038 | @item output @var{expression} | |
19039 | Print the value of @var{expression} and nothing but that value: no | |
19040 | newlines, no @samp{$@var{nn} = }. The value is not entered in the | |
19041 | value history either. @xref{Expressions, ,Expressions}, for more information | |
19042 | on expressions. | |
c906108c | 19043 | |
8e04817f AC |
19044 | @item output/@var{fmt} @var{expression} |
19045 | Print the value of @var{expression} in format @var{fmt}. You can use | |
19046 | the same formats as for @code{print}. @xref{Output Formats,,Output | |
79a6e687 | 19047 | Formats}, for more information. |
c906108c | 19048 | |
8e04817f | 19049 | @kindex printf |
82160952 EZ |
19050 | @item printf @var{template}, @var{expressions}@dots{} |
19051 | Print the values of one or more @var{expressions} under the control of | |
19052 | the string @var{template}. To print several values, make | |
19053 | @var{expressions} be a comma-separated list of individual expressions, | |
19054 | which may be either numbers or pointers. Their values are printed as | |
19055 | specified by @var{template}, exactly as a C program would do by | |
19056 | executing the code below: | |
c906108c | 19057 | |
474c8240 | 19058 | @smallexample |
82160952 | 19059 | printf (@var{template}, @var{expressions}@dots{}); |
474c8240 | 19060 | @end smallexample |
c906108c | 19061 | |
82160952 EZ |
19062 | As in @code{C} @code{printf}, ordinary characters in @var{template} |
19063 | are printed verbatim, while @dfn{conversion specification} introduced | |
19064 | by the @samp{%} character cause subsequent @var{expressions} to be | |
19065 | evaluated, their values converted and formatted according to type and | |
19066 | style information encoded in the conversion specifications, and then | |
19067 | printed. | |
19068 | ||
8e04817f | 19069 | For example, you can print two values in hex like this: |
c906108c | 19070 | |
8e04817f AC |
19071 | @smallexample |
19072 | printf "foo, bar-foo = 0x%x, 0x%x\n", foo, bar-foo | |
19073 | @end smallexample | |
c906108c | 19074 | |
82160952 EZ |
19075 | @code{printf} supports all the standard @code{C} conversion |
19076 | specifications, including the flags and modifiers between the @samp{%} | |
19077 | character and the conversion letter, with the following exceptions: | |
19078 | ||
19079 | @itemize @bullet | |
19080 | @item | |
19081 | The argument-ordering modifiers, such as @samp{2$}, are not supported. | |
19082 | ||
19083 | @item | |
19084 | The modifier @samp{*} is not supported for specifying precision or | |
19085 | width. | |
19086 | ||
19087 | @item | |
19088 | The @samp{'} flag (for separation of digits into groups according to | |
19089 | @code{LC_NUMERIC'}) is not supported. | |
19090 | ||
19091 | @item | |
19092 | The type modifiers @samp{hh}, @samp{j}, @samp{t}, and @samp{z} are not | |
19093 | supported. | |
19094 | ||
19095 | @item | |
19096 | The conversion letter @samp{n} (as in @samp{%n}) is not supported. | |
19097 | ||
19098 | @item | |
19099 | The conversion letters @samp{a} and @samp{A} are not supported. | |
19100 | @end itemize | |
19101 | ||
19102 | @noindent | |
19103 | Note that the @samp{ll} type modifier is supported only if the | |
19104 | underlying @code{C} implementation used to build @value{GDBN} supports | |
19105 | the @code{long long int} type, and the @samp{L} type modifier is | |
19106 | supported only if @code{long double} type is available. | |
19107 | ||
19108 | As in @code{C}, @code{printf} supports simple backslash-escape | |
19109 | sequences, such as @code{\n}, @samp{\t}, @samp{\\}, @samp{\"}, | |
19110 | @samp{\a}, and @samp{\f}, that consist of backslash followed by a | |
19111 | single character. Octal and hexadecimal escape sequences are not | |
19112 | supported. | |
1a619819 LM |
19113 | |
19114 | Additionally, @code{printf} supports conversion specifications for DFP | |
0aea4bf3 LM |
19115 | (@dfn{Decimal Floating Point}) types using the following length modifiers |
19116 | together with a floating point specifier. | |
1a619819 LM |
19117 | letters: |
19118 | ||
19119 | @itemize @bullet | |
19120 | @item | |
19121 | @samp{H} for printing @code{Decimal32} types. | |
19122 | ||
19123 | @item | |
19124 | @samp{D} for printing @code{Decimal64} types. | |
19125 | ||
19126 | @item | |
19127 | @samp{DD} for printing @code{Decimal128} types. | |
19128 | @end itemize | |
19129 | ||
19130 | If the underlying @code{C} implementation used to build @value{GDBN} has | |
0aea4bf3 | 19131 | support for the three length modifiers for DFP types, other modifiers |
3b784c4f | 19132 | such as width and precision will also be available for @value{GDBN} to use. |
1a619819 LM |
19133 | |
19134 | In case there is no such @code{C} support, no additional modifiers will be | |
19135 | available and the value will be printed in the standard way. | |
19136 | ||
19137 | Here's an example of printing DFP types using the above conversion letters: | |
19138 | @smallexample | |
0aea4bf3 | 19139 | printf "D32: %Hf - D64: %Df - D128: %DDf\n",1.2345df,1.2E10dd,1.2E1dl |
1a619819 LM |
19140 | @end smallexample |
19141 | ||
c906108c SS |
19142 | @end table |
19143 | ||
d57a3c85 TJB |
19144 | @node Python |
19145 | @section Scripting @value{GDBN} using Python | |
19146 | @cindex python scripting | |
19147 | @cindex scripting with python | |
19148 | ||
19149 | You can script @value{GDBN} using the @uref{http://www.python.org/, | |
19150 | Python programming language}. This feature is available only if | |
19151 | @value{GDBN} was configured using @option{--with-python}. | |
19152 | ||
19153 | @menu | |
19154 | * Python Commands:: Accessing Python from @value{GDBN}. | |
19155 | * Python API:: Accessing @value{GDBN} from Python. | |
19156 | @end menu | |
19157 | ||
19158 | @node Python Commands | |
19159 | @subsection Python Commands | |
19160 | @cindex python commands | |
19161 | @cindex commands to access python | |
19162 | ||
19163 | @value{GDBN} provides one command for accessing the Python interpreter, | |
19164 | and one related setting: | |
19165 | ||
19166 | @table @code | |
19167 | @kindex python | |
19168 | @item python @r{[}@var{code}@r{]} | |
19169 | The @code{python} command can be used to evaluate Python code. | |
19170 | ||
19171 | If given an argument, the @code{python} command will evaluate the | |
19172 | argument as a Python command. For example: | |
19173 | ||
19174 | @smallexample | |
19175 | (@value{GDBP}) python print 23 | |
19176 | 23 | |
19177 | @end smallexample | |
19178 | ||
19179 | If you do not provide an argument to @code{python}, it will act as a | |
19180 | multi-line command, like @code{define}. In this case, the Python | |
19181 | script is made up of subsequent command lines, given after the | |
19182 | @code{python} command. This command list is terminated using a line | |
19183 | containing @code{end}. For example: | |
19184 | ||
19185 | @smallexample | |
19186 | (@value{GDBP}) python | |
19187 | Type python script | |
19188 | End with a line saying just "end". | |
19189 | >print 23 | |
19190 | >end | |
19191 | 23 | |
19192 | @end smallexample | |
19193 | ||
19194 | @kindex maint set python print-stack | |
19195 | @item maint set python print-stack | |
19196 | By default, @value{GDBN} will print a stack trace when an error occurs | |
19197 | in a Python script. This can be controlled using @code{maint set | |
19198 | python print-stack}: if @code{on}, the default, then Python stack | |
19199 | printing is enabled; if @code{off}, then Python stack printing is | |
19200 | disabled. | |
19201 | @end table | |
19202 | ||
19203 | @node Python API | |
19204 | @subsection Python API | |
19205 | @cindex python api | |
19206 | @cindex programming in python | |
19207 | ||
19208 | @cindex python stdout | |
19209 | @cindex python pagination | |
19210 | At startup, @value{GDBN} overrides Python's @code{sys.stdout} and | |
19211 | @code{sys.stderr} to print using @value{GDBN}'s output-paging streams. | |
19212 | A Python program which outputs to one of these streams may have its | |
19213 | output interrupted by the user (@pxref{Screen Size}). In this | |
19214 | situation, a Python @code{KeyboardInterrupt} exception is thrown. | |
19215 | ||
19216 | @menu | |
19217 | * Basic Python:: Basic Python Functions. | |
19218 | * Exception Handling:: | |
89c73ade | 19219 | * Auto-loading:: Automatically loading Python code. |
a08702d6 | 19220 | * Values From Inferior:: |
2c74e833 | 19221 | * Types In Python:: Python representation of types. |
a6bac58e TT |
19222 | * Pretty Printing:: Pretty-printing values. |
19223 | * Selecting Pretty-Printers:: How GDB chooses a pretty-printer. | |
d8906c6f | 19224 | * Commands In Python:: Implementing new commands in Python. |
bc3b79fd | 19225 | * Functions In Python:: Writing new convenience functions. |
89c73ade | 19226 | * Objfiles In Python:: Object files. |
f8f6f20b | 19227 | * Frames In Python:: Acessing inferior stack frames from Python. |
d57a3c85 TJB |
19228 | @end menu |
19229 | ||
19230 | @node Basic Python | |
19231 | @subsubsection Basic Python | |
19232 | ||
19233 | @cindex python functions | |
19234 | @cindex python module | |
19235 | @cindex gdb module | |
19236 | @value{GDBN} introduces a new Python module, named @code{gdb}. All | |
19237 | methods and classes added by @value{GDBN} are placed in this module. | |
19238 | @value{GDBN} automatically @code{import}s the @code{gdb} module for | |
19239 | use in all scripts evaluated by the @code{python} command. | |
19240 | ||
19241 | @findex gdb.execute | |
12453b93 | 19242 | @defun execute command [from_tty] |
d57a3c85 TJB |
19243 | Evaluate @var{command}, a string, as a @value{GDBN} CLI command. |
19244 | If a GDB exception happens while @var{command} runs, it is | |
19245 | translated as described in @ref{Exception Handling,,Exception Handling}. | |
19246 | If no exceptions occur, this function returns @code{None}. | |
12453b93 TJB |
19247 | |
19248 | @var{from_tty} specifies whether @value{GDBN} ought to consider this | |
19249 | command as having originated from the user invoking it interactively. | |
19250 | It must be a boolean value. If omitted, it defaults to @code{False}. | |
d57a3c85 TJB |
19251 | @end defun |
19252 | ||
8f500870 TT |
19253 | @findex gdb.parameter |
19254 | @defun parameter parameter | |
d57a3c85 TJB |
19255 | Return the value of a @value{GDBN} parameter. @var{parameter} is a |
19256 | string naming the parameter to look up; @var{parameter} may contain | |
19257 | spaces if the parameter has a multi-part name. For example, | |
19258 | @samp{print object} is a valid parameter name. | |
19259 | ||
19260 | If the named parameter does not exist, this function throws a | |
19261 | @code{RuntimeError}. Otherwise, the parameter's value is converted to | |
19262 | a Python value of the appropriate type, and returned. | |
19263 | @end defun | |
19264 | ||
08c637de TJB |
19265 | @findex gdb.history |
19266 | @defun history number | |
19267 | Return a value from @value{GDBN}'s value history (@pxref{Value | |
19268 | History}). @var{number} indicates which history element to return. | |
19269 | If @var{number} is negative, then @value{GDBN} will take its absolute value | |
19270 | and count backward from the last element (i.e., the most recent element) to | |
19271 | find the value to return. If @var{number} is zero, then @value{GDBN} will | |
a0c36267 | 19272 | return the most recent element. If the element specified by @var{number} |
08c637de TJB |
19273 | doesn't exist in the value history, a @code{RuntimeError} exception will be |
19274 | raised. | |
19275 | ||
19276 | If no exception is raised, the return value is always an instance of | |
19277 | @code{gdb.Value} (@pxref{Values From Inferior}). | |
19278 | @end defun | |
19279 | ||
d57a3c85 TJB |
19280 | @findex gdb.write |
19281 | @defun write string | |
19282 | Print a string to @value{GDBN}'s paginated standard output stream. | |
19283 | Writing to @code{sys.stdout} or @code{sys.stderr} will automatically | |
19284 | call this function. | |
19285 | @end defun | |
19286 | ||
19287 | @findex gdb.flush | |
19288 | @defun flush | |
19289 | Flush @value{GDBN}'s paginated standard output stream. Flushing | |
19290 | @code{sys.stdout} or @code{sys.stderr} will automatically call this | |
19291 | function. | |
19292 | @end defun | |
19293 | ||
19294 | @node Exception Handling | |
19295 | @subsubsection Exception Handling | |
19296 | @cindex python exceptions | |
19297 | @cindex exceptions, python | |
19298 | ||
19299 | When executing the @code{python} command, Python exceptions | |
19300 | uncaught within the Python code are translated to calls to | |
19301 | @value{GDBN} error-reporting mechanism. If the command that called | |
19302 | @code{python} does not handle the error, @value{GDBN} will | |
19303 | terminate it and print an error message containing the Python | |
19304 | exception name, the associated value, and the Python call stack | |
19305 | backtrace at the point where the exception was raised. Example: | |
19306 | ||
19307 | @smallexample | |
19308 | (@value{GDBP}) python print foo | |
19309 | Traceback (most recent call last): | |
19310 | File "<string>", line 1, in <module> | |
19311 | NameError: name 'foo' is not defined | |
19312 | @end smallexample | |
19313 | ||
19314 | @value{GDBN} errors that happen in @value{GDBN} commands invoked by Python | |
19315 | code are converted to Python @code{RuntimeError} exceptions. User | |
19316 | interrupt (via @kbd{C-c} or by typing @kbd{q} at a pagination | |
19317 | prompt) is translated to a Python @code{KeyboardInterrupt} | |
19318 | exception. If you catch these exceptions in your Python code, your | |
19319 | exception handler will see @code{RuntimeError} or | |
19320 | @code{KeyboardInterrupt} as the exception type, the @value{GDBN} error | |
19321 | message as its value, and the Python call stack backtrace at the | |
19322 | Python statement closest to where the @value{GDBN} error occured as the | |
19323 | traceback. | |
19324 | ||
89c73ade TT |
19325 | @node Auto-loading |
19326 | @subsubsection Auto-loading | |
19327 | @cindex auto-loading, Python | |
19328 | ||
19329 | When a new object file is read (for example, due to the @code{file} | |
19330 | command, or because the inferior has loaded a shared library), | |
19331 | @value{GDBN} will look for a file named @file{@var{objfile}-gdb.py}, | |
19332 | where @var{objfile} is the object file's real name, formed by ensuring | |
19333 | that the file name is absolute, following all symlinks, and resolving | |
19334 | @code{.} and @code{..} components. If this file exists and is | |
19335 | readable, @value{GDBN} will evaluate it as a Python script. | |
19336 | ||
19337 | If this file does not exist, and if the parameter | |
19338 | @code{debug-file-directory} is set (@pxref{Separate Debug Files}), | |
19339 | then @value{GDBN} will use the file named | |
19340 | @file{@var{debug-file-directory}/@var{real-name}}, where | |
19341 | @var{real-name} is the object file's real name, as described above. | |
19342 | ||
19343 | Finally, if this file does not exist, then @value{GDBN} will look for | |
19344 | a file named @file{@var{data-directory}/python/auto-load/@var{real-name}}, where | |
19345 | @var{data-directory} is @value{GDBN}'s data directory (available via | |
19346 | @code{show data-directory}, @pxref{Data Files}), and @var{real-name} | |
19347 | is the object file's real name, as described above. | |
19348 | ||
19349 | When reading an auto-loaded file, @value{GDBN} sets the ``current | |
19350 | objfile''. This is available via the @code{gdb.current_objfile} | |
19351 | function (@pxref{Objfiles In Python}). This can be useful for | |
19352 | registering objfile-specific pretty-printers. | |
19353 | ||
19354 | The auto-loading feature is useful for supplying application-specific | |
19355 | debugging commands and scripts. You can enable or disable this | |
19356 | feature, and view its current state. | |
19357 | ||
19358 | @table @code | |
19359 | @kindex maint set python auto-load | |
19360 | @item maint set python auto-load [yes|no] | |
19361 | Enable or disable the Python auto-loading feature. | |
19362 | ||
19363 | @kindex show python auto-load | |
19364 | @item show python auto-load | |
19365 | Show whether Python auto-loading is enabled or disabled. | |
19366 | @end table | |
19367 | ||
19368 | @value{GDBN} does not track which files it has already auto-loaded. | |
19369 | So, your @samp{-gdb.py} file should take care to ensure that it may be | |
19370 | evaluated multiple times without error. | |
19371 | ||
a08702d6 TJB |
19372 | @node Values From Inferior |
19373 | @subsubsection Values From Inferior | |
19374 | @cindex values from inferior, with Python | |
19375 | @cindex python, working with values from inferior | |
19376 | ||
19377 | @cindex @code{gdb.Value} | |
19378 | @value{GDBN} provides values it obtains from the inferior program in | |
19379 | an object of type @code{gdb.Value}. @value{GDBN} uses this object | |
19380 | for its internal bookkeeping of the inferior's values, and for | |
19381 | fetching values when necessary. | |
19382 | ||
19383 | Inferior values that are simple scalars can be used directly in | |
19384 | Python expressions that are valid for the value's data type. Here's | |
19385 | an example for an integer or floating-point value @code{some_val}: | |
19386 | ||
19387 | @smallexample | |
19388 | bar = some_val + 2 | |
19389 | @end smallexample | |
19390 | ||
19391 | @noindent | |
19392 | As result of this, @code{bar} will also be a @code{gdb.Value} object | |
19393 | whose values are of the same type as those of @code{some_val}. | |
19394 | ||
19395 | Inferior values that are structures or instances of some class can | |
19396 | be accessed using the Python @dfn{dictionary syntax}. For example, if | |
19397 | @code{some_val} is a @code{gdb.Value} instance holding a structure, you | |
19398 | can access its @code{foo} element with: | |
19399 | ||
19400 | @smallexample | |
19401 | bar = some_val['foo'] | |
19402 | @end smallexample | |
19403 | ||
19404 | Again, @code{bar} will also be a @code{gdb.Value} object. | |
19405 | ||
c0c6f777 | 19406 | The following attributes are provided: |
a08702d6 | 19407 | |
def2b000 | 19408 | @table @code |
2c74e833 | 19409 | @defivar Value address |
c0c6f777 TJB |
19410 | If this object is addressable, this read-only attribute holds a |
19411 | @code{gdb.Value} object representing the address. Otherwise, | |
19412 | this attribute holds @code{None}. | |
2c74e833 | 19413 | @end defivar |
c0c6f777 | 19414 | |
def2b000 | 19415 | @cindex optimized out value in Python |
2c74e833 | 19416 | @defivar Value is_optimized_out |
def2b000 TJB |
19417 | This read-only boolean attribute is true if the compiler optimized out |
19418 | this value, thus it is not available for fetching from the inferior. | |
2c74e833 TT |
19419 | @end defivar |
19420 | ||
19421 | @defivar Value type | |
19422 | The type of this @code{gdb.Value}. The value of this attribute is a | |
19423 | @code{gdb.Type} object. | |
19424 | @end defivar | |
def2b000 TJB |
19425 | @end table |
19426 | ||
19427 | The following methods are provided: | |
19428 | ||
19429 | @table @code | |
a08702d6 | 19430 | @defmethod Value dereference |
def2b000 TJB |
19431 | For pointer data types, this method returns a new @code{gdb.Value} object |
19432 | whose contents is the object pointed to by the pointer. For example, if | |
19433 | @code{foo} is a C pointer to an @code{int}, declared in your C program as | |
a08702d6 TJB |
19434 | |
19435 | @smallexample | |
19436 | int *foo; | |
19437 | @end smallexample | |
19438 | ||
19439 | @noindent | |
19440 | then you can use the corresponding @code{gdb.Value} to access what | |
19441 | @code{foo} points to like this: | |
19442 | ||
19443 | @smallexample | |
19444 | bar = foo.dereference () | |
19445 | @end smallexample | |
19446 | ||
19447 | The result @code{bar} will be a @code{gdb.Value} object holding the | |
19448 | value pointed to by @code{foo}. | |
19449 | @end defmethod | |
19450 | ||
fbb8f299 | 19451 | @defmethod Value string @r{[}encoding@r{]} @r{[}errors@r{]} @r{[}length@r{]} |
b6cb8e7d TJB |
19452 | If this @code{gdb.Value} represents a string, then this method |
19453 | converts the contents to a Python string. Otherwise, this method will | |
19454 | throw an exception. | |
19455 | ||
19456 | Strings are recognized in a language-specific way; whether a given | |
19457 | @code{gdb.Value} represents a string is determined by the current | |
19458 | language. | |
19459 | ||
19460 | For C-like languages, a value is a string if it is a pointer to or an | |
19461 | array of characters or ints. The string is assumed to be terminated | |
fbb8f299 PM |
19462 | by a zero of the appropriate width. However if the optional length |
19463 | argument is given, the string will be converted to that given length, | |
19464 | ignoring any embedded zeros that the string may contain. | |
b6cb8e7d TJB |
19465 | |
19466 | If the optional @var{encoding} argument is given, it must be a string | |
19467 | naming the encoding of the string in the @code{gdb.Value}, such as | |
19468 | @code{"ascii"}, @code{"iso-8859-6"} or @code{"utf-8"}. It accepts | |
19469 | the same encodings as the corresponding argument to Python's | |
19470 | @code{string.decode} method, and the Python codec machinery will be used | |
19471 | to convert the string. If @var{encoding} is not given, or if | |
19472 | @var{encoding} is the empty string, then either the @code{target-charset} | |
19473 | (@pxref{Character Sets}) will be used, or a language-specific encoding | |
19474 | will be used, if the current language is able to supply one. | |
19475 | ||
19476 | The optional @var{errors} argument is the same as the corresponding | |
19477 | argument to Python's @code{string.decode} method. | |
fbb8f299 PM |
19478 | |
19479 | If the optional @var{length} argument is given, the string will be | |
19480 | fetched and converted to the given length. | |
b6cb8e7d | 19481 | @end defmethod |
def2b000 | 19482 | @end table |
b6cb8e7d | 19483 | |
2c74e833 TT |
19484 | @node Types In Python |
19485 | @subsubsection Types In Python | |
19486 | @cindex types in Python | |
19487 | @cindex Python, working with types | |
19488 | ||
19489 | @tindex gdb.Type | |
19490 | @value{GDBN} represents types from the inferior using the class | |
19491 | @code{gdb.Type}. | |
19492 | ||
19493 | The following type-related functions are available in the @code{gdb} | |
19494 | module: | |
19495 | ||
19496 | @findex gdb.lookup_type | |
19497 | @defun lookup_type name [block] | |
19498 | This function looks up a type by name. @var{name} is the name of the | |
19499 | type to look up. It must be a string. | |
19500 | ||
19501 | Ordinarily, this function will return an instance of @code{gdb.Type}. | |
19502 | If the named type cannot be found, it will throw an exception. | |
19503 | @end defun | |
19504 | ||
19505 | An instance of @code{Type} has the following attributes: | |
19506 | ||
19507 | @table @code | |
19508 | @defivar Type code | |
19509 | The type code for this type. The type code will be one of the | |
19510 | @code{TYPE_CODE_} constants defined below. | |
19511 | @end defivar | |
19512 | ||
19513 | @defivar Type sizeof | |
19514 | The size of this type, in target @code{char} units. Usually, a | |
19515 | target's @code{char} type will be an 8-bit byte. However, on some | |
19516 | unusual platforms, this type may have a different size. | |
19517 | @end defivar | |
19518 | ||
19519 | @defivar Type tag | |
19520 | The tag name for this type. The tag name is the name after | |
19521 | @code{struct}, @code{union}, or @code{enum} in C and C@t{++}; not all | |
19522 | languages have this concept. If this type has no tag name, then | |
19523 | @code{None} is returned. | |
19524 | @end defivar | |
19525 | @end table | |
19526 | ||
19527 | The following methods are provided: | |
19528 | ||
19529 | @table @code | |
19530 | @defmethod Type fields | |
19531 | For structure and union types, this method returns the fields. Range | |
19532 | types have two fields, the minimum and maximum values. Enum types | |
19533 | have one field per enum constant. Function and method types have one | |
19534 | field per parameter. The base types of C@t{++} classes are also | |
19535 | represented as fields. If the type has no fields, or does not fit | |
19536 | into one of these categories, an empty sequence will be returned. | |
19537 | ||
19538 | Each field is an object, with some pre-defined attributes: | |
19539 | @table @code | |
19540 | @item bitpos | |
19541 | This attribute is not available for @code{static} fields (as in | |
19542 | C@t{++} or Java). For non-@code{static} fields, the value is the bit | |
19543 | position of the field. | |
19544 | ||
19545 | @item name | |
19546 | The name of the field, or @code{None} for anonymous fields. | |
19547 | ||
19548 | @item artificial | |
19549 | This is @code{True} if the field is artificial, usually meaning that | |
19550 | it was provided by the compiler and not the user. This attribute is | |
19551 | always provided, and is @code{False} if the field is not artificial. | |
19552 | ||
19553 | @item bitsize | |
19554 | If the field is packed, or is a bitfield, then this will have a | |
19555 | non-zero value, which is the size of the field in bits. Otherwise, | |
19556 | this will be zero; in this case the field's size is given by its type. | |
19557 | ||
19558 | @item type | |
19559 | The type of the field. This is usually an instance of @code{Type}, | |
19560 | but it can be @code{None} in some situations. | |
19561 | @end table | |
19562 | @end defmethod | |
19563 | ||
19564 | @defmethod Type const | |
19565 | Return a new @code{gdb.Type} object which represents a | |
19566 | @code{const}-qualified variant of this type. | |
19567 | @end defmethod | |
19568 | ||
19569 | @defmethod Type volatile | |
19570 | Return a new @code{gdb.Type} object which represents a | |
19571 | @code{volatile}-qualified variant of this type. | |
19572 | @end defmethod | |
19573 | ||
19574 | @defmethod Type unqualified | |
19575 | Return a new @code{gdb.Type} object which represents an unqualified | |
19576 | variant of this type. That is, the result is neither @code{const} nor | |
19577 | @code{volatile}. | |
19578 | @end defmethod | |
19579 | ||
19580 | @defmethod Type reference | |
19581 | Return a new @code{gdb.Type} object which represents a reference to this | |
19582 | type. | |
19583 | @end defmethod | |
19584 | ||
19585 | @defmethod Type strip_typedefs | |
19586 | Return a new @code{gdb.Type} that represents the real type, | |
19587 | after removing all layers of typedefs. | |
19588 | @end defmethod | |
19589 | ||
19590 | @defmethod Type target | |
19591 | Return a new @code{gdb.Type} object which represents the target type | |
19592 | of this type. | |
19593 | ||
19594 | For a pointer type, the target type is the type of the pointed-to | |
19595 | object. For an array type (meaning C-like arrays), the target type is | |
19596 | the type of the elements of the array. For a function or method type, | |
19597 | the target type is the type of the return value. For a complex type, | |
19598 | the target type is the type of the elements. For a typedef, the | |
19599 | target type is the aliased type. | |
19600 | ||
19601 | If the type does not have a target, this method will throw an | |
19602 | exception. | |
19603 | @end defmethod | |
19604 | ||
19605 | @defmethod Type template_argument n | |
19606 | If this @code{gdb.Type} is an instantiation of a template, this will | |
19607 | return a new @code{gdb.Type} which represents the type of the | |
19608 | @var{n}th template argument. | |
19609 | ||
19610 | If this @code{gdb.Type} is not a template type, this will throw an | |
19611 | exception. Ordinarily, only C@t{++} code will have template types. | |
19612 | ||
19613 | @var{name} is searched for globally. | |
19614 | @end defmethod | |
19615 | @end table | |
19616 | ||
19617 | ||
19618 | Each type has a code, which indicates what category this type falls | |
19619 | into. The available type categories are represented by constants | |
19620 | defined in the @code{gdb} module: | |
19621 | ||
19622 | @table @code | |
19623 | @findex TYPE_CODE_PTR | |
19624 | @findex gdb.TYPE_CODE_PTR | |
19625 | @item TYPE_CODE_PTR | |
19626 | The type is a pointer. | |
19627 | ||
19628 | @findex TYPE_CODE_ARRAY | |
19629 | @findex gdb.TYPE_CODE_ARRAY | |
19630 | @item TYPE_CODE_ARRAY | |
19631 | The type is an array. | |
19632 | ||
19633 | @findex TYPE_CODE_STRUCT | |
19634 | @findex gdb.TYPE_CODE_STRUCT | |
19635 | @item TYPE_CODE_STRUCT | |
19636 | The type is a structure. | |
19637 | ||
19638 | @findex TYPE_CODE_UNION | |
19639 | @findex gdb.TYPE_CODE_UNION | |
19640 | @item TYPE_CODE_UNION | |
19641 | The type is a union. | |
19642 | ||
19643 | @findex TYPE_CODE_ENUM | |
19644 | @findex gdb.TYPE_CODE_ENUM | |
19645 | @item TYPE_CODE_ENUM | |
19646 | The type is an enum. | |
19647 | ||
19648 | @findex TYPE_CODE_FLAGS | |
19649 | @findex gdb.TYPE_CODE_FLAGS | |
19650 | @item TYPE_CODE_FLAGS | |
19651 | A bit flags type, used for things such as status registers. | |
19652 | ||
19653 | @findex TYPE_CODE_FUNC | |
19654 | @findex gdb.TYPE_CODE_FUNC | |
19655 | @item TYPE_CODE_FUNC | |
19656 | The type is a function. | |
19657 | ||
19658 | @findex TYPE_CODE_INT | |
19659 | @findex gdb.TYPE_CODE_INT | |
19660 | @item TYPE_CODE_INT | |
19661 | The type is an integer type. | |
19662 | ||
19663 | @findex TYPE_CODE_FLT | |
19664 | @findex gdb.TYPE_CODE_FLT | |
19665 | @item TYPE_CODE_FLT | |
19666 | A floating point type. | |
19667 | ||
19668 | @findex TYPE_CODE_VOID | |
19669 | @findex gdb.TYPE_CODE_VOID | |
19670 | @item TYPE_CODE_VOID | |
19671 | The special type @code{void}. | |
19672 | ||
19673 | @findex TYPE_CODE_SET | |
19674 | @findex gdb.TYPE_CODE_SET | |
19675 | @item TYPE_CODE_SET | |
19676 | A Pascal set type. | |
19677 | ||
19678 | @findex TYPE_CODE_RANGE | |
19679 | @findex gdb.TYPE_CODE_RANGE | |
19680 | @item TYPE_CODE_RANGE | |
19681 | A range type, that is, an integer type with bounds. | |
19682 | ||
19683 | @findex TYPE_CODE_STRING | |
19684 | @findex gdb.TYPE_CODE_STRING | |
19685 | @item TYPE_CODE_STRING | |
19686 | A string type. Note that this is only used for certain languages with | |
19687 | language-defined string types; C strings are not represented this way. | |
19688 | ||
19689 | @findex TYPE_CODE_BITSTRING | |
19690 | @findex gdb.TYPE_CODE_BITSTRING | |
19691 | @item TYPE_CODE_BITSTRING | |
19692 | A string of bits. | |
19693 | ||
19694 | @findex TYPE_CODE_ERROR | |
19695 | @findex gdb.TYPE_CODE_ERROR | |
19696 | @item TYPE_CODE_ERROR | |
19697 | An unknown or erroneous type. | |
19698 | ||
19699 | @findex TYPE_CODE_METHOD | |
19700 | @findex gdb.TYPE_CODE_METHOD | |
19701 | @item TYPE_CODE_METHOD | |
19702 | A method type, as found in C@t{++} or Java. | |
19703 | ||
19704 | @findex TYPE_CODE_METHODPTR | |
19705 | @findex gdb.TYPE_CODE_METHODPTR | |
19706 | @item TYPE_CODE_METHODPTR | |
19707 | A pointer-to-member-function. | |
19708 | ||
19709 | @findex TYPE_CODE_MEMBERPTR | |
19710 | @findex gdb.TYPE_CODE_MEMBERPTR | |
19711 | @item TYPE_CODE_MEMBERPTR | |
19712 | A pointer-to-member. | |
19713 | ||
19714 | @findex TYPE_CODE_REF | |
19715 | @findex gdb.TYPE_CODE_REF | |
19716 | @item TYPE_CODE_REF | |
19717 | A reference type. | |
19718 | ||
19719 | @findex TYPE_CODE_CHAR | |
19720 | @findex gdb.TYPE_CODE_CHAR | |
19721 | @item TYPE_CODE_CHAR | |
19722 | A character type. | |
19723 | ||
19724 | @findex TYPE_CODE_BOOL | |
19725 | @findex gdb.TYPE_CODE_BOOL | |
19726 | @item TYPE_CODE_BOOL | |
19727 | A boolean type. | |
19728 | ||
19729 | @findex TYPE_CODE_COMPLEX | |
19730 | @findex gdb.TYPE_CODE_COMPLEX | |
19731 | @item TYPE_CODE_COMPLEX | |
19732 | A complex float type. | |
19733 | ||
19734 | @findex TYPE_CODE_TYPEDEF | |
19735 | @findex gdb.TYPE_CODE_TYPEDEF | |
19736 | @item TYPE_CODE_TYPEDEF | |
19737 | A typedef to some other type. | |
19738 | ||
19739 | @findex TYPE_CODE_NAMESPACE | |
19740 | @findex gdb.TYPE_CODE_NAMESPACE | |
19741 | @item TYPE_CODE_NAMESPACE | |
19742 | A C@t{++} namespace. | |
19743 | ||
19744 | @findex TYPE_CODE_DECFLOAT | |
19745 | @findex gdb.TYPE_CODE_DECFLOAT | |
19746 | @item TYPE_CODE_DECFLOAT | |
19747 | A decimal floating point type. | |
19748 | ||
19749 | @findex TYPE_CODE_INTERNAL_FUNCTION | |
19750 | @findex gdb.TYPE_CODE_INTERNAL_FUNCTION | |
19751 | @item TYPE_CODE_INTERNAL_FUNCTION | |
19752 | A function internal to @value{GDBN}. This is the type used to represent | |
19753 | convenience functions. | |
19754 | @end table | |
19755 | ||
a6bac58e TT |
19756 | @node Pretty Printing |
19757 | @subsubsection Pretty Printing | |
19758 | ||
19759 | @value{GDBN} provides a mechanism to allow pretty-printing of values | |
19760 | using Python code. The pretty-printer API allows application-specific | |
19761 | code to greatly simplify the display of complex objects. This | |
19762 | mechanism works for both MI and the CLI. | |
19763 | ||
19764 | For example, here is how a C@t{++} @code{std::string} looks without a | |
19765 | pretty-printer: | |
19766 | ||
19767 | @smallexample | |
19768 | (@value{GDBP}) print s | |
19769 | $1 = @{ | |
19770 | static npos = 4294967295, | |
19771 | _M_dataplus = @{ | |
19772 | <std::allocator<char>> = @{ | |
19773 | <__gnu_cxx::new_allocator<char>> = @{<No data fields>@}, <No data fields>@}, | |
19774 | members of std::basic_string<char, std::char_traits<char>, std::allocator<char> >::_Alloc_hider: | |
19775 | _M_p = 0x804a014 "abcd" | |
19776 | @} | |
19777 | @} | |
19778 | @end smallexample | |
19779 | ||
19780 | After a pretty-printer for @code{std::string} has been installed, only | |
19781 | the contents are printed: | |
19782 | ||
19783 | @smallexample | |
19784 | (@value{GDBP}) print s | |
19785 | $2 = "abcd" | |
19786 | @end smallexample | |
19787 | ||
19788 | A pretty-printer is just an object that holds a value and implements a | |
19789 | specific interface, defined here. | |
19790 | ||
19791 | @defop Operation {pretty printer} children (self) | |
19792 | @value{GDBN} will call this method on a pretty-printer to compute the | |
19793 | children of the pretty-printer's value. | |
19794 | ||
19795 | This method must return an object conforming to the Python iterator | |
19796 | protocol. Each item returned by the iterator must be a tuple holding | |
19797 | two elements. The first element is the ``name'' of the child; the | |
19798 | second element is the child's value. The value can be any Python | |
19799 | object which is convertible to a @value{GDBN} value. | |
19800 | ||
19801 | This method is optional. If it does not exist, @value{GDBN} will act | |
19802 | as though the value has no children. | |
19803 | @end defop | |
19804 | ||
19805 | @defop Operation {pretty printer} display_hint (self) | |
19806 | The CLI may call this method and use its result to change the | |
19807 | formatting of a value. The result will also be supplied to an MI | |
19808 | consumer as a @samp{displayhint} attribute of the variable being | |
19809 | printed. | |
19810 | ||
19811 | This method is optional. If it does exist, this method must return a | |
19812 | string. | |
19813 | ||
19814 | Some display hints are predefined by @value{GDBN}: | |
19815 | ||
19816 | @table @samp | |
19817 | @item array | |
19818 | Indicate that the object being printed is ``array-like''. The CLI | |
19819 | uses this to respect parameters such as @code{set print elements} and | |
19820 | @code{set print array}. | |
19821 | ||
19822 | @item map | |
19823 | Indicate that the object being printed is ``map-like'', and that the | |
19824 | children of this value can be assumed to alternate between keys and | |
19825 | values. | |
19826 | ||
19827 | @item string | |
19828 | Indicate that the object being printed is ``string-like''. If the | |
19829 | printer's @code{to_string} method returns a Python string of some | |
19830 | kind, then @value{GDBN} will call its internal language-specific | |
19831 | string-printing function to format the string. For the CLI this means | |
19832 | adding quotation marks, possibly escaping some characters, respecting | |
19833 | @code{set print elements}, and the like. | |
19834 | @end table | |
19835 | @end defop | |
19836 | ||
19837 | @defop Operation {pretty printer} to_string (self) | |
19838 | @value{GDBN} will call this method to display the string | |
19839 | representation of the value passed to the object's constructor. | |
19840 | ||
19841 | When printing from the CLI, if the @code{to_string} method exists, | |
19842 | then @value{GDBN} will prepend its result to the values returned by | |
19843 | @code{children}. Exactly how this formatting is done is dependent on | |
19844 | the display hint, and may change as more hints are added. Also, | |
19845 | depending on the print settings (@pxref{Print Settings}), the CLI may | |
19846 | print just the result of @code{to_string} in a stack trace, omitting | |
19847 | the result of @code{children}. | |
19848 | ||
19849 | If this method returns a string, it is printed verbatim. | |
19850 | ||
19851 | Otherwise, if this method returns an instance of @code{gdb.Value}, | |
19852 | then @value{GDBN} prints this value. This may result in a call to | |
19853 | another pretty-printer. | |
19854 | ||
19855 | If instead the method returns a Python value which is convertible to a | |
19856 | @code{gdb.Value}, then @value{GDBN} performs the conversion and prints | |
19857 | the resulting value. Again, this may result in a call to another | |
19858 | pretty-printer. Python scalars (integers, floats, and booleans) and | |
19859 | strings are convertible to @code{gdb.Value}; other types are not. | |
19860 | ||
19861 | If the result is not one of these types, an exception is raised. | |
19862 | @end defop | |
19863 | ||
19864 | @node Selecting Pretty-Printers | |
19865 | @subsubsection Selecting Pretty-Printers | |
19866 | ||
19867 | The Python list @code{gdb.pretty_printers} contains an array of | |
19868 | functions that have been registered via addition as a pretty-printer. | |
19869 | Each @code{gdb.Objfile} also contains a @code{pretty_printers} | |
19870 | attribute. | |
19871 | ||
19872 | A function on one of these lists is passed a single @code{gdb.Value} | |
19873 | argument and should return a pretty-printer object conforming to the | |
19874 | interface definition above (@pxref{Pretty Printing}). If a function | |
19875 | cannot create a pretty-printer for the value, it should return | |
19876 | @code{None}. | |
19877 | ||
19878 | @value{GDBN} first checks the @code{pretty_printers} attribute of each | |
19879 | @code{gdb.Objfile} and iteratively calls each function in the list for | |
19880 | that @code{gdb.Objfile} until it receives a pretty-printer object. | |
19881 | After these lists have been exhausted, it tries the global | |
19882 | @code{gdb.pretty-printers} list, again calling each function until an | |
19883 | object is returned. | |
19884 | ||
19885 | The order in which the objfiles are searched is not specified. For a | |
19886 | given list, functions are always invoked from the head of the list, | |
19887 | and iterated over sequentially until the end of the list, or a printer | |
19888 | object is returned. | |
19889 | ||
19890 | Here is an example showing how a @code{std::string} printer might be | |
19891 | written: | |
19892 | ||
19893 | @smallexample | |
19894 | class StdStringPrinter: | |
19895 | "Print a std::string" | |
19896 | ||
19897 | def __init__ (self, val): | |
19898 | self.val = val | |
19899 | ||
19900 | def to_string (self): | |
19901 | return self.val['_M_dataplus']['_M_p'] | |
19902 | ||
19903 | def display_hint (self): | |
19904 | return 'string' | |
19905 | @end smallexample | |
19906 | ||
19907 | And here is an example showing how a lookup function for the printer | |
19908 | example above might be written. | |
19909 | ||
19910 | @smallexample | |
19911 | def str_lookup_function (val): | |
19912 | ||
19913 | lookup_tag = val.type.tag | |
19914 | regex = re.compile ("^std::basic_string<char,.*>$") | |
19915 | if lookup_tag == None: | |
19916 | return None | |
19917 | if regex.match (lookup_tag): | |
19918 | return StdStringPrinter (val) | |
19919 | ||
19920 | return None | |
19921 | @end smallexample | |
19922 | ||
19923 | The example lookup function extracts the value's type, and attempts to | |
19924 | match it to a type that it can pretty-print. If it is a type the | |
19925 | printer can pretty-print, it will return a printer object. If not, it | |
19926 | returns @code{None}. | |
19927 | ||
19928 | We recommend that you put your core pretty-printers into a Python | |
19929 | package. If your pretty-printers are for use with a library, we | |
19930 | further recommend embedding a version number into the package name. | |
19931 | This practice will enable @value{GDBN} to load multiple versions of | |
19932 | your pretty-printers at the same time, because they will have | |
19933 | different names. | |
19934 | ||
19935 | You should write auto-loaded code (@pxref{Auto-loading}) such that it | |
19936 | can be evaluated multiple times without changing its meaning. An | |
19937 | ideal auto-load file will consist solely of @code{import}s of your | |
19938 | printer modules, followed by a call to a register pretty-printers with | |
19939 | the current objfile. | |
19940 | ||
19941 | Taken as a whole, this approach will scale nicely to multiple | |
19942 | inferiors, each potentially using a different library version. | |
19943 | Embedding a version number in the Python package name will ensure that | |
19944 | @value{GDBN} is able to load both sets of printers simultaneously. | |
19945 | Then, because the search for pretty-printers is done by objfile, and | |
19946 | because your auto-loaded code took care to register your library's | |
19947 | printers with a specific objfile, @value{GDBN} will find the correct | |
19948 | printers for the specific version of the library used by each | |
19949 | inferior. | |
19950 | ||
19951 | To continue the @code{std::string} example (@pxref{Pretty Printing}), | |
19952 | this code might appear in @code{gdb.libstdcxx.v6}: | |
19953 | ||
19954 | @smallexample | |
19955 | def register_printers (objfile): | |
19956 | objfile.pretty_printers.add (str_lookup_function) | |
19957 | @end smallexample | |
19958 | ||
19959 | @noindent | |
19960 | And then the corresponding contents of the auto-load file would be: | |
19961 | ||
19962 | @smallexample | |
19963 | import gdb.libstdcxx.v6 | |
19964 | gdb.libstdcxx.v6.register_printers (gdb.current_objfile ()) | |
19965 | @end smallexample | |
19966 | ||
d8906c6f TJB |
19967 | @node Commands In Python |
19968 | @subsubsection Commands In Python | |
19969 | ||
19970 | @cindex commands in python | |
19971 | @cindex python commands | |
d8906c6f TJB |
19972 | You can implement new @value{GDBN} CLI commands in Python. A CLI |
19973 | command is implemented using an instance of the @code{gdb.Command} | |
19974 | class, most commonly using a subclass. | |
19975 | ||
cc924cad | 19976 | @defmethod Command __init__ name @var{command_class} @r{[}@var{completer_class}@r{]} @r{[}@var{prefix}@r{]} |
d8906c6f TJB |
19977 | The object initializer for @code{Command} registers the new command |
19978 | with @value{GDBN}. This initializer is normally invoked from the | |
19979 | subclass' own @code{__init__} method. | |
19980 | ||
19981 | @var{name} is the name of the command. If @var{name} consists of | |
19982 | multiple words, then the initial words are looked for as prefix | |
19983 | commands. In this case, if one of the prefix commands does not exist, | |
19984 | an exception is raised. | |
19985 | ||
19986 | There is no support for multi-line commands. | |
19987 | ||
cc924cad | 19988 | @var{command_class} should be one of the @samp{COMMAND_} constants |
d8906c6f TJB |
19989 | defined below. This argument tells @value{GDBN} how to categorize the |
19990 | new command in the help system. | |
19991 | ||
cc924cad | 19992 | @var{completer_class} is an optional argument. If given, it should be |
d8906c6f TJB |
19993 | one of the @samp{COMPLETE_} constants defined below. This argument |
19994 | tells @value{GDBN} how to perform completion for this command. If not | |
19995 | given, @value{GDBN} will attempt to complete using the object's | |
19996 | @code{complete} method (see below); if no such method is found, an | |
19997 | error will occur when completion is attempted. | |
19998 | ||
19999 | @var{prefix} is an optional argument. If @code{True}, then the new | |
20000 | command is a prefix command; sub-commands of this command may be | |
20001 | registered. | |
20002 | ||
20003 | The help text for the new command is taken from the Python | |
20004 | documentation string for the command's class, if there is one. If no | |
20005 | documentation string is provided, the default value ``This command is | |
20006 | not documented.'' is used. | |
20007 | @end defmethod | |
20008 | ||
a0c36267 | 20009 | @cindex don't repeat Python command |
d8906c6f TJB |
20010 | @defmethod Command dont_repeat |
20011 | By default, a @value{GDBN} command is repeated when the user enters a | |
20012 | blank line at the command prompt. A command can suppress this | |
20013 | behavior by invoking the @code{dont_repeat} method. This is similar | |
20014 | to the user command @code{dont-repeat}, see @ref{Define, dont-repeat}. | |
20015 | @end defmethod | |
20016 | ||
20017 | @defmethod Command invoke argument from_tty | |
20018 | This method is called by @value{GDBN} when this command is invoked. | |
20019 | ||
20020 | @var{argument} is a string. It is the argument to the command, after | |
20021 | leading and trailing whitespace has been stripped. | |
20022 | ||
20023 | @var{from_tty} is a boolean argument. When true, this means that the | |
20024 | command was entered by the user at the terminal; when false it means | |
20025 | that the command came from elsewhere. | |
20026 | ||
20027 | If this method throws an exception, it is turned into a @value{GDBN} | |
20028 | @code{error} call. Otherwise, the return value is ignored. | |
20029 | @end defmethod | |
20030 | ||
a0c36267 | 20031 | @cindex completion of Python commands |
d8906c6f TJB |
20032 | @defmethod Command complete text word |
20033 | This method is called by @value{GDBN} when the user attempts | |
20034 | completion on this command. All forms of completion are handled by | |
a0c36267 EZ |
20035 | this method, that is, the @key{TAB} and @key{M-?} key bindings |
20036 | (@pxref{Completion}), and the @code{complete} command (@pxref{Help, | |
20037 | complete}). | |
d8906c6f TJB |
20038 | |
20039 | The arguments @var{text} and @var{word} are both strings. @var{text} | |
20040 | holds the complete command line up to the cursor's location. | |
20041 | @var{word} holds the last word of the command line; this is computed | |
20042 | using a word-breaking heuristic. | |
20043 | ||
20044 | The @code{complete} method can return several values: | |
20045 | @itemize @bullet | |
20046 | @item | |
20047 | If the return value is a sequence, the contents of the sequence are | |
20048 | used as the completions. It is up to @code{complete} to ensure that the | |
20049 | contents actually do complete the word. A zero-length sequence is | |
20050 | allowed, it means that there were no completions available. Only | |
20051 | string elements of the sequence are used; other elements in the | |
20052 | sequence are ignored. | |
20053 | ||
20054 | @item | |
20055 | If the return value is one of the @samp{COMPLETE_} constants defined | |
20056 | below, then the corresponding @value{GDBN}-internal completion | |
20057 | function is invoked, and its result is used. | |
20058 | ||
20059 | @item | |
20060 | All other results are treated as though there were no available | |
20061 | completions. | |
20062 | @end itemize | |
20063 | @end defmethod | |
20064 | ||
d8906c6f TJB |
20065 | When a new command is registered, it must be declared as a member of |
20066 | some general class of commands. This is used to classify top-level | |
20067 | commands in the on-line help system; note that prefix commands are not | |
20068 | listed under their own category but rather that of their top-level | |
20069 | command. The available classifications are represented by constants | |
20070 | defined in the @code{gdb} module: | |
20071 | ||
20072 | @table @code | |
20073 | @findex COMMAND_NONE | |
20074 | @findex gdb.COMMAND_NONE | |
20075 | @item COMMAND_NONE | |
20076 | The command does not belong to any particular class. A command in | |
20077 | this category will not be displayed in any of the help categories. | |
20078 | ||
20079 | @findex COMMAND_RUNNING | |
20080 | @findex gdb.COMMAND_RUNNING | |
a0c36267 | 20081 | @item COMMAND_RUNNING |
d8906c6f TJB |
20082 | The command is related to running the inferior. For example, |
20083 | @code{start}, @code{step}, and @code{continue} are in this category. | |
a0c36267 | 20084 | Type @kbd{help running} at the @value{GDBN} prompt to see a list of |
d8906c6f TJB |
20085 | commands in this category. |
20086 | ||
20087 | @findex COMMAND_DATA | |
20088 | @findex gdb.COMMAND_DATA | |
a0c36267 | 20089 | @item COMMAND_DATA |
d8906c6f TJB |
20090 | The command is related to data or variables. For example, |
20091 | @code{call}, @code{find}, and @code{print} are in this category. Type | |
a0c36267 | 20092 | @kbd{help data} at the @value{GDBN} prompt to see a list of commands |
d8906c6f TJB |
20093 | in this category. |
20094 | ||
20095 | @findex COMMAND_STACK | |
20096 | @findex gdb.COMMAND_STACK | |
20097 | @item COMMAND_STACK | |
20098 | The command has to do with manipulation of the stack. For example, | |
20099 | @code{backtrace}, @code{frame}, and @code{return} are in this | |
a0c36267 | 20100 | category. Type @kbd{help stack} at the @value{GDBN} prompt to see a |
d8906c6f TJB |
20101 | list of commands in this category. |
20102 | ||
20103 | @findex COMMAND_FILES | |
20104 | @findex gdb.COMMAND_FILES | |
20105 | @item COMMAND_FILES | |
20106 | This class is used for file-related commands. For example, | |
20107 | @code{file}, @code{list} and @code{section} are in this category. | |
a0c36267 | 20108 | Type @kbd{help files} at the @value{GDBN} prompt to see a list of |
d8906c6f TJB |
20109 | commands in this category. |
20110 | ||
20111 | @findex COMMAND_SUPPORT | |
20112 | @findex gdb.COMMAND_SUPPORT | |
20113 | @item COMMAND_SUPPORT | |
20114 | This should be used for ``support facilities'', generally meaning | |
20115 | things that are useful to the user when interacting with @value{GDBN}, | |
20116 | but not related to the state of the inferior. For example, | |
20117 | @code{help}, @code{make}, and @code{shell} are in this category. Type | |
a0c36267 | 20118 | @kbd{help support} at the @value{GDBN} prompt to see a list of |
d8906c6f TJB |
20119 | commands in this category. |
20120 | ||
20121 | @findex COMMAND_STATUS | |
20122 | @findex gdb.COMMAND_STATUS | |
a0c36267 | 20123 | @item COMMAND_STATUS |
d8906c6f TJB |
20124 | The command is an @samp{info}-related command, that is, related to the |
20125 | state of @value{GDBN} itself. For example, @code{info}, @code{macro}, | |
a0c36267 | 20126 | and @code{show} are in this category. Type @kbd{help status} at the |
d8906c6f TJB |
20127 | @value{GDBN} prompt to see a list of commands in this category. |
20128 | ||
20129 | @findex COMMAND_BREAKPOINTS | |
20130 | @findex gdb.COMMAND_BREAKPOINTS | |
a0c36267 | 20131 | @item COMMAND_BREAKPOINTS |
d8906c6f | 20132 | The command has to do with breakpoints. For example, @code{break}, |
a0c36267 | 20133 | @code{clear}, and @code{delete} are in this category. Type @kbd{help |
d8906c6f TJB |
20134 | breakpoints} at the @value{GDBN} prompt to see a list of commands in |
20135 | this category. | |
20136 | ||
20137 | @findex COMMAND_TRACEPOINTS | |
20138 | @findex gdb.COMMAND_TRACEPOINTS | |
a0c36267 | 20139 | @item COMMAND_TRACEPOINTS |
d8906c6f TJB |
20140 | The command has to do with tracepoints. For example, @code{trace}, |
20141 | @code{actions}, and @code{tfind} are in this category. Type | |
a0c36267 | 20142 | @kbd{help tracepoints} at the @value{GDBN} prompt to see a list of |
d8906c6f TJB |
20143 | commands in this category. |
20144 | ||
20145 | @findex COMMAND_OBSCURE | |
20146 | @findex gdb.COMMAND_OBSCURE | |
20147 | @item COMMAND_OBSCURE | |
20148 | The command is only used in unusual circumstances, or is not of | |
20149 | general interest to users. For example, @code{checkpoint}, | |
a0c36267 | 20150 | @code{fork}, and @code{stop} are in this category. Type @kbd{help |
d8906c6f TJB |
20151 | obscure} at the @value{GDBN} prompt to see a list of commands in this |
20152 | category. | |
20153 | ||
20154 | @findex COMMAND_MAINTENANCE | |
20155 | @findex gdb.COMMAND_MAINTENANCE | |
20156 | @item COMMAND_MAINTENANCE | |
20157 | The command is only useful to @value{GDBN} maintainers. The | |
20158 | @code{maintenance} and @code{flushregs} commands are in this category. | |
a0c36267 | 20159 | Type @kbd{help internals} at the @value{GDBN} prompt to see a list of |
d8906c6f TJB |
20160 | commands in this category. |
20161 | @end table | |
20162 | ||
d8906c6f TJB |
20163 | A new command can use a predefined completion function, either by |
20164 | specifying it via an argument at initialization, or by returning it | |
20165 | from the @code{complete} method. These predefined completion | |
20166 | constants are all defined in the @code{gdb} module: | |
20167 | ||
20168 | @table @code | |
20169 | @findex COMPLETE_NONE | |
20170 | @findex gdb.COMPLETE_NONE | |
20171 | @item COMPLETE_NONE | |
20172 | This constant means that no completion should be done. | |
20173 | ||
20174 | @findex COMPLETE_FILENAME | |
20175 | @findex gdb.COMPLETE_FILENAME | |
20176 | @item COMPLETE_FILENAME | |
20177 | This constant means that filename completion should be performed. | |
20178 | ||
20179 | @findex COMPLETE_LOCATION | |
20180 | @findex gdb.COMPLETE_LOCATION | |
20181 | @item COMPLETE_LOCATION | |
20182 | This constant means that location completion should be done. | |
20183 | @xref{Specify Location}. | |
20184 | ||
20185 | @findex COMPLETE_COMMAND | |
20186 | @findex gdb.COMPLETE_COMMAND | |
20187 | @item COMPLETE_COMMAND | |
20188 | This constant means that completion should examine @value{GDBN} | |
20189 | command names. | |
20190 | ||
20191 | @findex COMPLETE_SYMBOL | |
20192 | @findex gdb.COMPLETE_SYMBOL | |
20193 | @item COMPLETE_SYMBOL | |
20194 | This constant means that completion should be done using symbol names | |
20195 | as the source. | |
20196 | @end table | |
20197 | ||
20198 | The following code snippet shows how a trivial CLI command can be | |
20199 | implemented in Python: | |
20200 | ||
20201 | @smallexample | |
20202 | class HelloWorld (gdb.Command): | |
20203 | """Greet the whole world.""" | |
20204 | ||
20205 | def __init__ (self): | |
20206 | super (HelloWorld, self).__init__ ("hello-world", gdb.COMMAND_OBSCURE) | |
20207 | ||
20208 | def invoke (self, arg, from_tty): | |
20209 | print "Hello, World!" | |
20210 | ||
20211 | HelloWorld () | |
20212 | @end smallexample | |
20213 | ||
20214 | The last line instantiates the class, and is necessary to trigger the | |
20215 | registration of the command with @value{GDBN}. Depending on how the | |
20216 | Python code is read into @value{GDBN}, you may need to import the | |
20217 | @code{gdb} module explicitly. | |
20218 | ||
bc3b79fd TJB |
20219 | @node Functions In Python |
20220 | @subsubsection Writing new convenience functions | |
20221 | ||
20222 | @cindex writing convenience functions | |
20223 | @cindex convenience functions in python | |
20224 | @cindex python convenience functions | |
20225 | @tindex gdb.Function | |
20226 | @tindex Function | |
20227 | You can implement new convenience functions (@pxref{Convenience Vars}) | |
20228 | in Python. A convenience function is an instance of a subclass of the | |
20229 | class @code{gdb.Function}. | |
20230 | ||
20231 | @defmethod Function __init__ name | |
20232 | The initializer for @code{Function} registers the new function with | |
20233 | @value{GDBN}. The argument @var{name} is the name of the function, | |
20234 | a string. The function will be visible to the user as a convenience | |
20235 | variable of type @code{internal function}, whose name is the same as | |
20236 | the given @var{name}. | |
20237 | ||
20238 | The documentation for the new function is taken from the documentation | |
20239 | string for the new class. | |
20240 | @end defmethod | |
20241 | ||
20242 | @defmethod Function invoke @var{*args} | |
20243 | When a convenience function is evaluated, its arguments are converted | |
20244 | to instances of @code{gdb.Value}, and then the function's | |
20245 | @code{invoke} method is called. Note that @value{GDBN} does not | |
20246 | predetermine the arity of convenience functions. Instead, all | |
20247 | available arguments are passed to @code{invoke}, following the | |
20248 | standard Python calling convention. In particular, a convenience | |
20249 | function can have default values for parameters without ill effect. | |
20250 | ||
20251 | The return value of this method is used as its value in the enclosing | |
20252 | expression. If an ordinary Python value is returned, it is converted | |
20253 | to a @code{gdb.Value} following the usual rules. | |
20254 | @end defmethod | |
20255 | ||
20256 | The following code snippet shows how a trivial convenience function can | |
20257 | be implemented in Python: | |
20258 | ||
20259 | @smallexample | |
20260 | class Greet (gdb.Function): | |
20261 | """Return string to greet someone. | |
20262 | Takes a name as argument.""" | |
20263 | ||
20264 | def __init__ (self): | |
20265 | super (Greet, self).__init__ ("greet") | |
20266 | ||
20267 | def invoke (self, name): | |
20268 | return "Hello, %s!" % name.string () | |
20269 | ||
20270 | Greet () | |
20271 | @end smallexample | |
20272 | ||
20273 | The last line instantiates the class, and is necessary to trigger the | |
20274 | registration of the function with @value{GDBN}. Depending on how the | |
20275 | Python code is read into @value{GDBN}, you may need to import the | |
20276 | @code{gdb} module explicitly. | |
20277 | ||
89c73ade TT |
20278 | @node Objfiles In Python |
20279 | @subsubsection Objfiles In Python | |
20280 | ||
20281 | @cindex objfiles in python | |
20282 | @tindex gdb.Objfile | |
20283 | @tindex Objfile | |
20284 | @value{GDBN} loads symbols for an inferior from various | |
20285 | symbol-containing files (@pxref{Files}). These include the primary | |
20286 | executable file, any shared libraries used by the inferior, and any | |
20287 | separate debug info files (@pxref{Separate Debug Files}). | |
20288 | @value{GDBN} calls these symbol-containing files @dfn{objfiles}. | |
20289 | ||
20290 | The following objfile-related functions are available in the | |
20291 | @code{gdb} module: | |
20292 | ||
20293 | @findex gdb.current_objfile | |
20294 | @defun current_objfile | |
20295 | When auto-loading a Python script (@pxref{Auto-loading}), @value{GDBN} | |
20296 | sets the ``current objfile'' to the corresponding objfile. This | |
20297 | function returns the current objfile. If there is no current objfile, | |
20298 | this function returns @code{None}. | |
20299 | @end defun | |
20300 | ||
20301 | @findex gdb.objfiles | |
20302 | @defun objfiles | |
20303 | Return a sequence of all the objfiles current known to @value{GDBN}. | |
20304 | @xref{Objfiles In Python}. | |
20305 | @end defun | |
20306 | ||
20307 | Each objfile is represented by an instance of the @code{gdb.Objfile} | |
20308 | class. | |
20309 | ||
20310 | @defivar Objfile filename | |
20311 | The file name of the objfile as a string. | |
20312 | @end defivar | |
20313 | ||
20314 | @defivar Objfile pretty_printers | |
20315 | The @code{pretty_printers} attribute is a list of functions. It is | |
20316 | used to look up pretty-printers. A @code{Value} is passed to each | |
20317 | function in order; if the function returns @code{None}, then the | |
20318 | search continues. Otherwise, the return value should be an object | |
a6bac58e TT |
20319 | which is used to format the value. @xref{Pretty Printing}, for more |
20320 | information. | |
89c73ade TT |
20321 | @end defivar |
20322 | ||
f8f6f20b TJB |
20323 | @node Frames In Python |
20324 | @subsubsection Acessing inferior stack frames from Python. | |
20325 | ||
20326 | @cindex frames in python | |
20327 | When the debugged program stops, @value{GDBN} is able to analyze its call | |
20328 | stack (@pxref{Frames,,Stack frames}). The @code{gdb.Frame} class | |
20329 | represents a frame in the stack. A @code{gdb.Frame} object is only valid | |
20330 | while its corresponding frame exists in the inferior's stack. If you try | |
20331 | to use an invalid frame object, @value{GDBN} will throw a @code{RuntimeError} | |
20332 | exception. | |
20333 | ||
20334 | Two @code{gdb.Frame} objects can be compared for equality with the @code{==} | |
20335 | operator, like: | |
20336 | ||
20337 | @smallexample | |
20338 | (@value{GDBP}) python print gdb.newest_frame() == gdb.selected_frame () | |
20339 | True | |
20340 | @end smallexample | |
20341 | ||
20342 | The following frame-related functions are available in the @code{gdb} module: | |
20343 | ||
20344 | @findex gdb.selected_frame | |
20345 | @defun selected_frame | |
20346 | Return the selected frame object. (@pxref{Selection,,Selecting a Frame}). | |
20347 | @end defun | |
20348 | ||
20349 | @defun frame_stop_reason_string reason | |
20350 | Return a string explaining the reason why @value{GDBN} stopped unwinding | |
20351 | frames, as expressed by the given @var{reason} code (an integer, see the | |
20352 | @code{unwind_stop_reason} method further down in this section). | |
20353 | @end defun | |
20354 | ||
20355 | A @code{gdb.Frame} object has the following methods: | |
20356 | ||
20357 | @table @code | |
20358 | @defmethod Frame is_valid | |
20359 | Returns true if the @code{gdb.Frame} object is valid, false if not. | |
20360 | A frame object can become invalid if the frame it refers to doesn't | |
20361 | exist anymore in the inferior. All @code{gdb.Frame} methods will throw | |
20362 | an exception if it is invalid at the time the method is called. | |
20363 | @end defmethod | |
20364 | ||
20365 | @defmethod Frame name | |
20366 | Returns the function name of the frame, or @code{None} if it can't be | |
20367 | obtained. | |
20368 | @end defmethod | |
20369 | ||
20370 | @defmethod Frame type | |
20371 | Returns the type of the frame. The value can be one of | |
20372 | @code{gdb.NORMAL_FRAME}, @code{gdb.DUMMY_FRAME}, @code{gdb.SIGTRAMP_FRAME} | |
20373 | or @code{gdb.SENTINEL_FRAME}. | |
20374 | @end defmethod | |
20375 | ||
20376 | @defmethod Frame unwind_stop_reason | |
20377 | Return an integer representing the reason why it's not possible to find | |
20378 | more frames toward the outermost frame. Use | |
20379 | @code{gdb.frame_stop_reason_string} to convert the value returned by this | |
20380 | function to a string. | |
20381 | @end defmethod | |
20382 | ||
20383 | @defmethod Frame pc | |
20384 | Returns the frame's resume address. | |
20385 | @end defmethod | |
20386 | ||
20387 | @defmethod Frame older | |
20388 | Return the frame that called this frame. | |
20389 | @end defmethod | |
20390 | ||
20391 | @defmethod Frame newer | |
20392 | Return the frame called by this frame. | |
20393 | @end defmethod | |
20394 | ||
20395 | @defmethod Frame read_var variable | |
20396 | Return the value of the given variable in this frame. @var{variable} must | |
20397 | be a string. | |
20398 | @end defmethod | |
20399 | @end table | |
20400 | ||
21c294e6 AC |
20401 | @node Interpreters |
20402 | @chapter Command Interpreters | |
20403 | @cindex command interpreters | |
20404 | ||
20405 | @value{GDBN} supports multiple command interpreters, and some command | |
20406 | infrastructure to allow users or user interface writers to switch | |
20407 | between interpreters or run commands in other interpreters. | |
20408 | ||
20409 | @value{GDBN} currently supports two command interpreters, the console | |
20410 | interpreter (sometimes called the command-line interpreter or @sc{cli}) | |
20411 | and the machine interface interpreter (or @sc{gdb/mi}). This manual | |
20412 | describes both of these interfaces in great detail. | |
20413 | ||
20414 | By default, @value{GDBN} will start with the console interpreter. | |
20415 | However, the user may choose to start @value{GDBN} with another | |
20416 | interpreter by specifying the @option{-i} or @option{--interpreter} | |
20417 | startup options. Defined interpreters include: | |
20418 | ||
20419 | @table @code | |
20420 | @item console | |
20421 | @cindex console interpreter | |
20422 | The traditional console or command-line interpreter. This is the most often | |
20423 | used interpreter with @value{GDBN}. With no interpreter specified at runtime, | |
20424 | @value{GDBN} will use this interpreter. | |
20425 | ||
20426 | @item mi | |
20427 | @cindex mi interpreter | |
20428 | The newest @sc{gdb/mi} interface (currently @code{mi2}). Used primarily | |
20429 | by programs wishing to use @value{GDBN} as a backend for a debugger GUI | |
20430 | or an IDE. For more information, see @ref{GDB/MI, ,The @sc{gdb/mi} | |
20431 | Interface}. | |
20432 | ||
20433 | @item mi2 | |
20434 | @cindex mi2 interpreter | |
20435 | The current @sc{gdb/mi} interface. | |
20436 | ||
20437 | @item mi1 | |
20438 | @cindex mi1 interpreter | |
20439 | The @sc{gdb/mi} interface included in @value{GDBN} 5.1, 5.2, and 5.3. | |
20440 | ||
20441 | @end table | |
20442 | ||
20443 | @cindex invoke another interpreter | |
20444 | The interpreter being used by @value{GDBN} may not be dynamically | |
20445 | switched at runtime. Although possible, this could lead to a very | |
20446 | precarious situation. Consider an IDE using @sc{gdb/mi}. If a user | |
20447 | enters the command "interpreter-set console" in a console view, | |
20448 | @value{GDBN} would switch to using the console interpreter, rendering | |
20449 | the IDE inoperable! | |
20450 | ||
20451 | @kindex interpreter-exec | |
20452 | Although you may only choose a single interpreter at startup, you may execute | |
20453 | commands in any interpreter from the current interpreter using the appropriate | |
20454 | command. If you are running the console interpreter, simply use the | |
20455 | @code{interpreter-exec} command: | |
20456 | ||
20457 | @smallexample | |
20458 | interpreter-exec mi "-data-list-register-names" | |
20459 | @end smallexample | |
20460 | ||
20461 | @sc{gdb/mi} has a similar command, although it is only available in versions of | |
20462 | @value{GDBN} which support @sc{gdb/mi} version 2 (or greater). | |
20463 | ||
8e04817f AC |
20464 | @node TUI |
20465 | @chapter @value{GDBN} Text User Interface | |
20466 | @cindex TUI | |
d0d5df6f | 20467 | @cindex Text User Interface |
c906108c | 20468 | |
8e04817f AC |
20469 | @menu |
20470 | * TUI Overview:: TUI overview | |
20471 | * TUI Keys:: TUI key bindings | |
7cf36c78 | 20472 | * TUI Single Key Mode:: TUI single key mode |
db2e3e2e | 20473 | * TUI Commands:: TUI-specific commands |
8e04817f AC |
20474 | * TUI Configuration:: TUI configuration variables |
20475 | @end menu | |
c906108c | 20476 | |
46ba6afa | 20477 | The @value{GDBN} Text User Interface (TUI) is a terminal |
d0d5df6f AC |
20478 | interface which uses the @code{curses} library to show the source |
20479 | file, the assembly output, the program registers and @value{GDBN} | |
46ba6afa BW |
20480 | commands in separate text windows. The TUI mode is supported only |
20481 | on platforms where a suitable version of the @code{curses} library | |
20482 | is available. | |
d0d5df6f | 20483 | |
46ba6afa BW |
20484 | @pindex @value{GDBTUI} |
20485 | The TUI mode is enabled by default when you invoke @value{GDBN} as | |
20486 | either @samp{@value{GDBTUI}} or @samp{@value{GDBP} -tui}. | |
20487 | You can also switch in and out of TUI mode while @value{GDBN} runs by | |
20488 | using various TUI commands and key bindings, such as @kbd{C-x C-a}. | |
20489 | @xref{TUI Keys, ,TUI Key Bindings}. | |
c906108c | 20490 | |
8e04817f | 20491 | @node TUI Overview |
79a6e687 | 20492 | @section TUI Overview |
c906108c | 20493 | |
46ba6afa | 20494 | In TUI mode, @value{GDBN} can display several text windows: |
c906108c | 20495 | |
8e04817f AC |
20496 | @table @emph |
20497 | @item command | |
20498 | This window is the @value{GDBN} command window with the @value{GDBN} | |
46ba6afa BW |
20499 | prompt and the @value{GDBN} output. The @value{GDBN} input is still |
20500 | managed using readline. | |
c906108c | 20501 | |
8e04817f AC |
20502 | @item source |
20503 | The source window shows the source file of the program. The current | |
46ba6afa | 20504 | line and active breakpoints are displayed in this window. |
c906108c | 20505 | |
8e04817f AC |
20506 | @item assembly |
20507 | The assembly window shows the disassembly output of the program. | |
c906108c | 20508 | |
8e04817f | 20509 | @item register |
46ba6afa BW |
20510 | This window shows the processor registers. Registers are highlighted |
20511 | when their values change. | |
c906108c SS |
20512 | @end table |
20513 | ||
269c21fe | 20514 | The source and assembly windows show the current program position |
46ba6afa BW |
20515 | by highlighting the current line and marking it with a @samp{>} marker. |
20516 | Breakpoints are indicated with two markers. The first marker | |
269c21fe SC |
20517 | indicates the breakpoint type: |
20518 | ||
20519 | @table @code | |
20520 | @item B | |
20521 | Breakpoint which was hit at least once. | |
20522 | ||
20523 | @item b | |
20524 | Breakpoint which was never hit. | |
20525 | ||
20526 | @item H | |
20527 | Hardware breakpoint which was hit at least once. | |
20528 | ||
20529 | @item h | |
20530 | Hardware breakpoint which was never hit. | |
269c21fe SC |
20531 | @end table |
20532 | ||
20533 | The second marker indicates whether the breakpoint is enabled or not: | |
20534 | ||
20535 | @table @code | |
20536 | @item + | |
20537 | Breakpoint is enabled. | |
20538 | ||
20539 | @item - | |
20540 | Breakpoint is disabled. | |
269c21fe SC |
20541 | @end table |
20542 | ||
46ba6afa BW |
20543 | The source, assembly and register windows are updated when the current |
20544 | thread changes, when the frame changes, or when the program counter | |
20545 | changes. | |
20546 | ||
20547 | These windows are not all visible at the same time. The command | |
20548 | window is always visible. The others can be arranged in several | |
20549 | layouts: | |
c906108c | 20550 | |
8e04817f AC |
20551 | @itemize @bullet |
20552 | @item | |
46ba6afa | 20553 | source only, |
2df3850c | 20554 | |
8e04817f | 20555 | @item |
46ba6afa | 20556 | assembly only, |
8e04817f AC |
20557 | |
20558 | @item | |
46ba6afa | 20559 | source and assembly, |
8e04817f AC |
20560 | |
20561 | @item | |
46ba6afa | 20562 | source and registers, or |
c906108c | 20563 | |
8e04817f | 20564 | @item |
46ba6afa | 20565 | assembly and registers. |
8e04817f | 20566 | @end itemize |
c906108c | 20567 | |
46ba6afa | 20568 | A status line above the command window shows the following information: |
b7bb15bc SC |
20569 | |
20570 | @table @emph | |
20571 | @item target | |
46ba6afa | 20572 | Indicates the current @value{GDBN} target. |
b7bb15bc SC |
20573 | (@pxref{Targets, ,Specifying a Debugging Target}). |
20574 | ||
20575 | @item process | |
46ba6afa | 20576 | Gives the current process or thread number. |
b7bb15bc SC |
20577 | When no process is being debugged, this field is set to @code{No process}. |
20578 | ||
20579 | @item function | |
20580 | Gives the current function name for the selected frame. | |
20581 | The name is demangled if demangling is turned on (@pxref{Print Settings}). | |
46ba6afa | 20582 | When there is no symbol corresponding to the current program counter, |
b7bb15bc SC |
20583 | the string @code{??} is displayed. |
20584 | ||
20585 | @item line | |
20586 | Indicates the current line number for the selected frame. | |
46ba6afa | 20587 | When the current line number is not known, the string @code{??} is displayed. |
b7bb15bc SC |
20588 | |
20589 | @item pc | |
20590 | Indicates the current program counter address. | |
b7bb15bc SC |
20591 | @end table |
20592 | ||
8e04817f AC |
20593 | @node TUI Keys |
20594 | @section TUI Key Bindings | |
20595 | @cindex TUI key bindings | |
c906108c | 20596 | |
8e04817f | 20597 | The TUI installs several key bindings in the readline keymaps |
46ba6afa | 20598 | (@pxref{Command Line Editing}). The following key bindings |
8e04817f | 20599 | are installed for both TUI mode and the @value{GDBN} standard mode. |
c906108c | 20600 | |
8e04817f AC |
20601 | @table @kbd |
20602 | @kindex C-x C-a | |
20603 | @item C-x C-a | |
20604 | @kindex C-x a | |
20605 | @itemx C-x a | |
20606 | @kindex C-x A | |
20607 | @itemx C-x A | |
46ba6afa BW |
20608 | Enter or leave the TUI mode. When leaving the TUI mode, |
20609 | the curses window management stops and @value{GDBN} operates using | |
20610 | its standard mode, writing on the terminal directly. When reentering | |
20611 | the TUI mode, control is given back to the curses windows. | |
8e04817f | 20612 | The screen is then refreshed. |
c906108c | 20613 | |
8e04817f AC |
20614 | @kindex C-x 1 |
20615 | @item C-x 1 | |
20616 | Use a TUI layout with only one window. The layout will | |
20617 | either be @samp{source} or @samp{assembly}. When the TUI mode | |
20618 | is not active, it will switch to the TUI mode. | |
2df3850c | 20619 | |
8e04817f | 20620 | Think of this key binding as the Emacs @kbd{C-x 1} binding. |
c906108c | 20621 | |
8e04817f AC |
20622 | @kindex C-x 2 |
20623 | @item C-x 2 | |
20624 | Use a TUI layout with at least two windows. When the current | |
46ba6afa | 20625 | layout already has two windows, the next layout with two windows is used. |
8e04817f AC |
20626 | When a new layout is chosen, one window will always be common to the |
20627 | previous layout and the new one. | |
c906108c | 20628 | |
8e04817f | 20629 | Think of it as the Emacs @kbd{C-x 2} binding. |
2df3850c | 20630 | |
72ffddc9 SC |
20631 | @kindex C-x o |
20632 | @item C-x o | |
20633 | Change the active window. The TUI associates several key bindings | |
46ba6afa | 20634 | (like scrolling and arrow keys) with the active window. This command |
72ffddc9 SC |
20635 | gives the focus to the next TUI window. |
20636 | ||
20637 | Think of it as the Emacs @kbd{C-x o} binding. | |
20638 | ||
7cf36c78 SC |
20639 | @kindex C-x s |
20640 | @item C-x s | |
46ba6afa BW |
20641 | Switch in and out of the TUI SingleKey mode that binds single |
20642 | keys to @value{GDBN} commands (@pxref{TUI Single Key Mode}). | |
c906108c SS |
20643 | @end table |
20644 | ||
46ba6afa | 20645 | The following key bindings only work in the TUI mode: |
5d161b24 | 20646 | |
46ba6afa | 20647 | @table @asis |
8e04817f | 20648 | @kindex PgUp |
46ba6afa | 20649 | @item @key{PgUp} |
8e04817f | 20650 | Scroll the active window one page up. |
c906108c | 20651 | |
8e04817f | 20652 | @kindex PgDn |
46ba6afa | 20653 | @item @key{PgDn} |
8e04817f | 20654 | Scroll the active window one page down. |
c906108c | 20655 | |
8e04817f | 20656 | @kindex Up |
46ba6afa | 20657 | @item @key{Up} |
8e04817f | 20658 | Scroll the active window one line up. |
c906108c | 20659 | |
8e04817f | 20660 | @kindex Down |
46ba6afa | 20661 | @item @key{Down} |
8e04817f | 20662 | Scroll the active window one line down. |
c906108c | 20663 | |
8e04817f | 20664 | @kindex Left |
46ba6afa | 20665 | @item @key{Left} |
8e04817f | 20666 | Scroll the active window one column left. |
c906108c | 20667 | |
8e04817f | 20668 | @kindex Right |
46ba6afa | 20669 | @item @key{Right} |
8e04817f | 20670 | Scroll the active window one column right. |
c906108c | 20671 | |
8e04817f | 20672 | @kindex C-L |
46ba6afa | 20673 | @item @kbd{C-L} |
8e04817f | 20674 | Refresh the screen. |
8e04817f | 20675 | @end table |
c906108c | 20676 | |
46ba6afa BW |
20677 | Because the arrow keys scroll the active window in the TUI mode, they |
20678 | are not available for their normal use by readline unless the command | |
20679 | window has the focus. When another window is active, you must use | |
20680 | other readline key bindings such as @kbd{C-p}, @kbd{C-n}, @kbd{C-b} | |
20681 | and @kbd{C-f} to control the command window. | |
8e04817f | 20682 | |
7cf36c78 SC |
20683 | @node TUI Single Key Mode |
20684 | @section TUI Single Key Mode | |
20685 | @cindex TUI single key mode | |
20686 | ||
46ba6afa BW |
20687 | The TUI also provides a @dfn{SingleKey} mode, which binds several |
20688 | frequently used @value{GDBN} commands to single keys. Type @kbd{C-x s} to | |
20689 | switch into this mode, where the following key bindings are used: | |
7cf36c78 SC |
20690 | |
20691 | @table @kbd | |
20692 | @kindex c @r{(SingleKey TUI key)} | |
20693 | @item c | |
20694 | continue | |
20695 | ||
20696 | @kindex d @r{(SingleKey TUI key)} | |
20697 | @item d | |
20698 | down | |
20699 | ||
20700 | @kindex f @r{(SingleKey TUI key)} | |
20701 | @item f | |
20702 | finish | |
20703 | ||
20704 | @kindex n @r{(SingleKey TUI key)} | |
20705 | @item n | |
20706 | next | |
20707 | ||
20708 | @kindex q @r{(SingleKey TUI key)} | |
20709 | @item q | |
46ba6afa | 20710 | exit the SingleKey mode. |
7cf36c78 SC |
20711 | |
20712 | @kindex r @r{(SingleKey TUI key)} | |
20713 | @item r | |
20714 | run | |
20715 | ||
20716 | @kindex s @r{(SingleKey TUI key)} | |
20717 | @item s | |
20718 | step | |
20719 | ||
20720 | @kindex u @r{(SingleKey TUI key)} | |
20721 | @item u | |
20722 | up | |
20723 | ||
20724 | @kindex v @r{(SingleKey TUI key)} | |
20725 | @item v | |
20726 | info locals | |
20727 | ||
20728 | @kindex w @r{(SingleKey TUI key)} | |
20729 | @item w | |
20730 | where | |
7cf36c78 SC |
20731 | @end table |
20732 | ||
20733 | Other keys temporarily switch to the @value{GDBN} command prompt. | |
20734 | The key that was pressed is inserted in the editing buffer so that | |
20735 | it is possible to type most @value{GDBN} commands without interaction | |
46ba6afa BW |
20736 | with the TUI SingleKey mode. Once the command is entered the TUI |
20737 | SingleKey mode is restored. The only way to permanently leave | |
7f9087cb | 20738 | this mode is by typing @kbd{q} or @kbd{C-x s}. |
7cf36c78 SC |
20739 | |
20740 | ||
8e04817f | 20741 | @node TUI Commands |
db2e3e2e | 20742 | @section TUI-specific Commands |
8e04817f AC |
20743 | @cindex TUI commands |
20744 | ||
20745 | The TUI has specific commands to control the text windows. | |
46ba6afa BW |
20746 | These commands are always available, even when @value{GDBN} is not in |
20747 | the TUI mode. When @value{GDBN} is in the standard mode, most | |
20748 | of these commands will automatically switch to the TUI mode. | |
c906108c SS |
20749 | |
20750 | @table @code | |
3d757584 SC |
20751 | @item info win |
20752 | @kindex info win | |
20753 | List and give the size of all displayed windows. | |
20754 | ||
8e04817f | 20755 | @item layout next |
4644b6e3 | 20756 | @kindex layout |
8e04817f | 20757 | Display the next layout. |
2df3850c | 20758 | |
8e04817f | 20759 | @item layout prev |
8e04817f | 20760 | Display the previous layout. |
c906108c | 20761 | |
8e04817f | 20762 | @item layout src |
8e04817f | 20763 | Display the source window only. |
c906108c | 20764 | |
8e04817f | 20765 | @item layout asm |
8e04817f | 20766 | Display the assembly window only. |
c906108c | 20767 | |
8e04817f | 20768 | @item layout split |
8e04817f | 20769 | Display the source and assembly window. |
c906108c | 20770 | |
8e04817f | 20771 | @item layout regs |
8e04817f AC |
20772 | Display the register window together with the source or assembly window. |
20773 | ||
46ba6afa | 20774 | @item focus next |
8e04817f | 20775 | @kindex focus |
46ba6afa BW |
20776 | Make the next window active for scrolling. |
20777 | ||
20778 | @item focus prev | |
20779 | Make the previous window active for scrolling. | |
20780 | ||
20781 | @item focus src | |
20782 | Make the source window active for scrolling. | |
20783 | ||
20784 | @item focus asm | |
20785 | Make the assembly window active for scrolling. | |
20786 | ||
20787 | @item focus regs | |
20788 | Make the register window active for scrolling. | |
20789 | ||
20790 | @item focus cmd | |
20791 | Make the command window active for scrolling. | |
c906108c | 20792 | |
8e04817f AC |
20793 | @item refresh |
20794 | @kindex refresh | |
7f9087cb | 20795 | Refresh the screen. This is similar to typing @kbd{C-L}. |
c906108c | 20796 | |
6a1b180d SC |
20797 | @item tui reg float |
20798 | @kindex tui reg | |
20799 | Show the floating point registers in the register window. | |
20800 | ||
20801 | @item tui reg general | |
20802 | Show the general registers in the register window. | |
20803 | ||
20804 | @item tui reg next | |
20805 | Show the next register group. The list of register groups as well as | |
20806 | their order is target specific. The predefined register groups are the | |
20807 | following: @code{general}, @code{float}, @code{system}, @code{vector}, | |
20808 | @code{all}, @code{save}, @code{restore}. | |
20809 | ||
20810 | @item tui reg system | |
20811 | Show the system registers in the register window. | |
20812 | ||
8e04817f AC |
20813 | @item update |
20814 | @kindex update | |
20815 | Update the source window and the current execution point. | |
c906108c | 20816 | |
8e04817f AC |
20817 | @item winheight @var{name} +@var{count} |
20818 | @itemx winheight @var{name} -@var{count} | |
20819 | @kindex winheight | |
20820 | Change the height of the window @var{name} by @var{count} | |
20821 | lines. Positive counts increase the height, while negative counts | |
20822 | decrease it. | |
2df3850c | 20823 | |
46ba6afa BW |
20824 | @item tabset @var{nchars} |
20825 | @kindex tabset | |
c45da7e6 | 20826 | Set the width of tab stops to be @var{nchars} characters. |
c906108c SS |
20827 | @end table |
20828 | ||
8e04817f | 20829 | @node TUI Configuration |
79a6e687 | 20830 | @section TUI Configuration Variables |
8e04817f | 20831 | @cindex TUI configuration variables |
c906108c | 20832 | |
46ba6afa | 20833 | Several configuration variables control the appearance of TUI windows. |
c906108c | 20834 | |
8e04817f AC |
20835 | @table @code |
20836 | @item set tui border-kind @var{kind} | |
20837 | @kindex set tui border-kind | |
20838 | Select the border appearance for the source, assembly and register windows. | |
20839 | The possible values are the following: | |
20840 | @table @code | |
20841 | @item space | |
20842 | Use a space character to draw the border. | |
c906108c | 20843 | |
8e04817f | 20844 | @item ascii |
46ba6afa | 20845 | Use @sc{ascii} characters @samp{+}, @samp{-} and @samp{|} to draw the border. |
c906108c | 20846 | |
8e04817f AC |
20847 | @item acs |
20848 | Use the Alternate Character Set to draw the border. The border is | |
20849 | drawn using character line graphics if the terminal supports them. | |
8e04817f | 20850 | @end table |
c78b4128 | 20851 | |
8e04817f AC |
20852 | @item set tui border-mode @var{mode} |
20853 | @kindex set tui border-mode | |
46ba6afa BW |
20854 | @itemx set tui active-border-mode @var{mode} |
20855 | @kindex set tui active-border-mode | |
20856 | Select the display attributes for the borders of the inactive windows | |
20857 | or the active window. The @var{mode} can be one of the following: | |
8e04817f AC |
20858 | @table @code |
20859 | @item normal | |
20860 | Use normal attributes to display the border. | |
c906108c | 20861 | |
8e04817f AC |
20862 | @item standout |
20863 | Use standout mode. | |
c906108c | 20864 | |
8e04817f AC |
20865 | @item reverse |
20866 | Use reverse video mode. | |
c906108c | 20867 | |
8e04817f AC |
20868 | @item half |
20869 | Use half bright mode. | |
c906108c | 20870 | |
8e04817f AC |
20871 | @item half-standout |
20872 | Use half bright and standout mode. | |
c906108c | 20873 | |
8e04817f AC |
20874 | @item bold |
20875 | Use extra bright or bold mode. | |
c78b4128 | 20876 | |
8e04817f AC |
20877 | @item bold-standout |
20878 | Use extra bright or bold and standout mode. | |
8e04817f | 20879 | @end table |
8e04817f | 20880 | @end table |
c78b4128 | 20881 | |
8e04817f AC |
20882 | @node Emacs |
20883 | @chapter Using @value{GDBN} under @sc{gnu} Emacs | |
c78b4128 | 20884 | |
8e04817f AC |
20885 | @cindex Emacs |
20886 | @cindex @sc{gnu} Emacs | |
20887 | A special interface allows you to use @sc{gnu} Emacs to view (and | |
20888 | edit) the source files for the program you are debugging with | |
20889 | @value{GDBN}. | |
c906108c | 20890 | |
8e04817f AC |
20891 | To use this interface, use the command @kbd{M-x gdb} in Emacs. Give the |
20892 | executable file you want to debug as an argument. This command starts | |
20893 | @value{GDBN} as a subprocess of Emacs, with input and output through a newly | |
20894 | created Emacs buffer. | |
20895 | @c (Do not use the @code{-tui} option to run @value{GDBN} from Emacs.) | |
c906108c | 20896 | |
5e252a2e | 20897 | Running @value{GDBN} under Emacs can be just like running @value{GDBN} normally except for two |
8e04817f | 20898 | things: |
c906108c | 20899 | |
8e04817f AC |
20900 | @itemize @bullet |
20901 | @item | |
5e252a2e NR |
20902 | All ``terminal'' input and output goes through an Emacs buffer, called |
20903 | the GUD buffer. | |
c906108c | 20904 | |
8e04817f AC |
20905 | This applies both to @value{GDBN} commands and their output, and to the input |
20906 | and output done by the program you are debugging. | |
bf0184be | 20907 | |
8e04817f AC |
20908 | This is useful because it means that you can copy the text of previous |
20909 | commands and input them again; you can even use parts of the output | |
20910 | in this way. | |
bf0184be | 20911 | |
8e04817f AC |
20912 | All the facilities of Emacs' Shell mode are available for interacting |
20913 | with your program. In particular, you can send signals the usual | |
20914 | way---for example, @kbd{C-c C-c} for an interrupt, @kbd{C-c C-z} for a | |
20915 | stop. | |
bf0184be ND |
20916 | |
20917 | @item | |
8e04817f | 20918 | @value{GDBN} displays source code through Emacs. |
bf0184be | 20919 | |
8e04817f AC |
20920 | Each time @value{GDBN} displays a stack frame, Emacs automatically finds the |
20921 | source file for that frame and puts an arrow (@samp{=>}) at the | |
20922 | left margin of the current line. Emacs uses a separate buffer for | |
20923 | source display, and splits the screen to show both your @value{GDBN} session | |
20924 | and the source. | |
bf0184be | 20925 | |
8e04817f AC |
20926 | Explicit @value{GDBN} @code{list} or search commands still produce output as |
20927 | usual, but you probably have no reason to use them from Emacs. | |
5e252a2e NR |
20928 | @end itemize |
20929 | ||
20930 | We call this @dfn{text command mode}. Emacs 22.1, and later, also uses | |
20931 | a graphical mode, enabled by default, which provides further buffers | |
20932 | that can control the execution and describe the state of your program. | |
20933 | @xref{GDB Graphical Interface,,, Emacs, The @sc{gnu} Emacs Manual}. | |
c906108c | 20934 | |
64fabec2 AC |
20935 | If you specify an absolute file name when prompted for the @kbd{M-x |
20936 | gdb} argument, then Emacs sets your current working directory to where | |
20937 | your program resides. If you only specify the file name, then Emacs | |
20938 | sets your current working directory to to the directory associated | |
20939 | with the previous buffer. In this case, @value{GDBN} may find your | |
20940 | program by searching your environment's @code{PATH} variable, but on | |
20941 | some operating systems it might not find the source. So, although the | |
20942 | @value{GDBN} input and output session proceeds normally, the auxiliary | |
20943 | buffer does not display the current source and line of execution. | |
20944 | ||
20945 | The initial working directory of @value{GDBN} is printed on the top | |
5e252a2e NR |
20946 | line of the GUD buffer and this serves as a default for the commands |
20947 | that specify files for @value{GDBN} to operate on. @xref{Files, | |
20948 | ,Commands to Specify Files}. | |
64fabec2 AC |
20949 | |
20950 | By default, @kbd{M-x gdb} calls the program called @file{gdb}. If you | |
20951 | need to call @value{GDBN} by a different name (for example, if you | |
20952 | keep several configurations around, with different names) you can | |
20953 | customize the Emacs variable @code{gud-gdb-command-name} to run the | |
20954 | one you want. | |
8e04817f | 20955 | |
5e252a2e | 20956 | In the GUD buffer, you can use these special Emacs commands in |
8e04817f | 20957 | addition to the standard Shell mode commands: |
c906108c | 20958 | |
8e04817f AC |
20959 | @table @kbd |
20960 | @item C-h m | |
5e252a2e | 20961 | Describe the features of Emacs' GUD Mode. |
c906108c | 20962 | |
64fabec2 | 20963 | @item C-c C-s |
8e04817f AC |
20964 | Execute to another source line, like the @value{GDBN} @code{step} command; also |
20965 | update the display window to show the current file and location. | |
c906108c | 20966 | |
64fabec2 | 20967 | @item C-c C-n |
8e04817f AC |
20968 | Execute to next source line in this function, skipping all function |
20969 | calls, like the @value{GDBN} @code{next} command. Then update the display window | |
20970 | to show the current file and location. | |
c906108c | 20971 | |
64fabec2 | 20972 | @item C-c C-i |
8e04817f AC |
20973 | Execute one instruction, like the @value{GDBN} @code{stepi} command; update |
20974 | display window accordingly. | |
c906108c | 20975 | |
8e04817f AC |
20976 | @item C-c C-f |
20977 | Execute until exit from the selected stack frame, like the @value{GDBN} | |
20978 | @code{finish} command. | |
c906108c | 20979 | |
64fabec2 | 20980 | @item C-c C-r |
8e04817f AC |
20981 | Continue execution of your program, like the @value{GDBN} @code{continue} |
20982 | command. | |
b433d00b | 20983 | |
64fabec2 | 20984 | @item C-c < |
8e04817f AC |
20985 | Go up the number of frames indicated by the numeric argument |
20986 | (@pxref{Arguments, , Numeric Arguments, Emacs, The @sc{gnu} Emacs Manual}), | |
20987 | like the @value{GDBN} @code{up} command. | |
b433d00b | 20988 | |
64fabec2 | 20989 | @item C-c > |
8e04817f AC |
20990 | Go down the number of frames indicated by the numeric argument, like the |
20991 | @value{GDBN} @code{down} command. | |
8e04817f | 20992 | @end table |
c906108c | 20993 | |
7f9087cb | 20994 | In any source file, the Emacs command @kbd{C-x @key{SPC}} (@code{gud-break}) |
8e04817f | 20995 | tells @value{GDBN} to set a breakpoint on the source line point is on. |
c906108c | 20996 | |
5e252a2e NR |
20997 | In text command mode, if you type @kbd{M-x speedbar}, Emacs displays a |
20998 | separate frame which shows a backtrace when the GUD buffer is current. | |
20999 | Move point to any frame in the stack and type @key{RET} to make it | |
21000 | become the current frame and display the associated source in the | |
21001 | source buffer. Alternatively, click @kbd{Mouse-2} to make the | |
21002 | selected frame become the current one. In graphical mode, the | |
21003 | speedbar displays watch expressions. | |
64fabec2 | 21004 | |
8e04817f AC |
21005 | If you accidentally delete the source-display buffer, an easy way to get |
21006 | it back is to type the command @code{f} in the @value{GDBN} buffer, to | |
21007 | request a frame display; when you run under Emacs, this recreates | |
21008 | the source buffer if necessary to show you the context of the current | |
21009 | frame. | |
c906108c | 21010 | |
8e04817f AC |
21011 | The source files displayed in Emacs are in ordinary Emacs buffers |
21012 | which are visiting the source files in the usual way. You can edit | |
21013 | the files with these buffers if you wish; but keep in mind that @value{GDBN} | |
21014 | communicates with Emacs in terms of line numbers. If you add or | |
21015 | delete lines from the text, the line numbers that @value{GDBN} knows cease | |
21016 | to correspond properly with the code. | |
b383017d | 21017 | |
5e252a2e NR |
21018 | A more detailed description of Emacs' interaction with @value{GDBN} is |
21019 | given in the Emacs manual (@pxref{Debuggers,,, Emacs, The @sc{gnu} | |
21020 | Emacs Manual}). | |
c906108c | 21021 | |
8e04817f AC |
21022 | @c The following dropped because Epoch is nonstandard. Reactivate |
21023 | @c if/when v19 does something similar. ---doc@cygnus.com 19dec1990 | |
21024 | @ignore | |
21025 | @kindex Emacs Epoch environment | |
21026 | @kindex Epoch | |
21027 | @kindex inspect | |
c906108c | 21028 | |
8e04817f AC |
21029 | Version 18 of @sc{gnu} Emacs has a built-in window system |
21030 | called the @code{epoch} | |
21031 | environment. Users of this environment can use a new command, | |
21032 | @code{inspect} which performs identically to @code{print} except that | |
21033 | each value is printed in its own window. | |
21034 | @end ignore | |
c906108c | 21035 | |
922fbb7b AC |
21036 | |
21037 | @node GDB/MI | |
21038 | @chapter The @sc{gdb/mi} Interface | |
21039 | ||
21040 | @unnumberedsec Function and Purpose | |
21041 | ||
21042 | @cindex @sc{gdb/mi}, its purpose | |
6b5e8c01 NR |
21043 | @sc{gdb/mi} is a line based machine oriented text interface to |
21044 | @value{GDBN} and is activated by specifying using the | |
21045 | @option{--interpreter} command line option (@pxref{Mode Options}). It | |
21046 | is specifically intended to support the development of systems which | |
21047 | use the debugger as just one small component of a larger system. | |
922fbb7b AC |
21048 | |
21049 | This chapter is a specification of the @sc{gdb/mi} interface. It is written | |
21050 | in the form of a reference manual. | |
21051 | ||
21052 | Note that @sc{gdb/mi} is still under construction, so some of the | |
af6eff6f NR |
21053 | features described below are incomplete and subject to change |
21054 | (@pxref{GDB/MI Development and Front Ends, , @sc{gdb/mi} Development and Front Ends}). | |
922fbb7b AC |
21055 | |
21056 | @unnumberedsec Notation and Terminology | |
21057 | ||
21058 | @cindex notational conventions, for @sc{gdb/mi} | |
21059 | This chapter uses the following notation: | |
21060 | ||
21061 | @itemize @bullet | |
21062 | @item | |
21063 | @code{|} separates two alternatives. | |
21064 | ||
21065 | @item | |
21066 | @code{[ @var{something} ]} indicates that @var{something} is optional: | |
21067 | it may or may not be given. | |
21068 | ||
21069 | @item | |
21070 | @code{( @var{group} )*} means that @var{group} inside the parentheses | |
21071 | may repeat zero or more times. | |
21072 | ||
21073 | @item | |
21074 | @code{( @var{group} )+} means that @var{group} inside the parentheses | |
21075 | may repeat one or more times. | |
21076 | ||
21077 | @item | |
21078 | @code{"@var{string}"} means a literal @var{string}. | |
21079 | @end itemize | |
21080 | ||
21081 | @ignore | |
21082 | @heading Dependencies | |
21083 | @end ignore | |
21084 | ||
922fbb7b | 21085 | @menu |
c3b108f7 | 21086 | * GDB/MI General Design:: |
922fbb7b AC |
21087 | * GDB/MI Command Syntax:: |
21088 | * GDB/MI Compatibility with CLI:: | |
af6eff6f | 21089 | * GDB/MI Development and Front Ends:: |
922fbb7b | 21090 | * GDB/MI Output Records:: |
ef21caaf | 21091 | * GDB/MI Simple Examples:: |
922fbb7b | 21092 | * GDB/MI Command Description Format:: |
ef21caaf | 21093 | * GDB/MI Breakpoint Commands:: |
a2c02241 NR |
21094 | * GDB/MI Program Context:: |
21095 | * GDB/MI Thread Commands:: | |
21096 | * GDB/MI Program Execution:: | |
21097 | * GDB/MI Stack Manipulation:: | |
21098 | * GDB/MI Variable Objects:: | |
922fbb7b | 21099 | * GDB/MI Data Manipulation:: |
a2c02241 NR |
21100 | * GDB/MI Tracepoint Commands:: |
21101 | * GDB/MI Symbol Query:: | |
351ff01a | 21102 | * GDB/MI File Commands:: |
922fbb7b AC |
21103 | @ignore |
21104 | * GDB/MI Kod Commands:: | |
21105 | * GDB/MI Memory Overlay Commands:: | |
21106 | * GDB/MI Signal Handling Commands:: | |
21107 | @end ignore | |
922fbb7b | 21108 | * GDB/MI Target Manipulation:: |
a6b151f1 | 21109 | * GDB/MI File Transfer Commands:: |
ef21caaf | 21110 | * GDB/MI Miscellaneous Commands:: |
922fbb7b AC |
21111 | @end menu |
21112 | ||
c3b108f7 VP |
21113 | @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% |
21114 | @node GDB/MI General Design | |
21115 | @section @sc{gdb/mi} General Design | |
21116 | @cindex GDB/MI General Design | |
21117 | ||
21118 | Interaction of a @sc{GDB/MI} frontend with @value{GDBN} involves three | |
21119 | parts---commands sent to @value{GDBN}, responses to those commands | |
21120 | and notifications. Each command results in exactly one response, | |
21121 | indicating either successful completion of the command, or an error. | |
21122 | For the commands that do not resume the target, the response contains the | |
21123 | requested information. For the commands that resume the target, the | |
21124 | response only indicates whether the target was successfully resumed. | |
21125 | Notifications is the mechanism for reporting changes in the state of the | |
21126 | target, or in @value{GDBN} state, that cannot conveniently be associated with | |
21127 | a command and reported as part of that command response. | |
21128 | ||
21129 | The important examples of notifications are: | |
21130 | @itemize @bullet | |
21131 | ||
21132 | @item | |
21133 | Exec notifications. These are used to report changes in | |
21134 | target state---when a target is resumed, or stopped. It would not | |
21135 | be feasible to include this information in response of resuming | |
21136 | commands, because one resume commands can result in multiple events in | |
21137 | different threads. Also, quite some time may pass before any event | |
21138 | happens in the target, while a frontend needs to know whether the resuming | |
21139 | command itself was successfully executed. | |
21140 | ||
21141 | @item | |
21142 | Console output, and status notifications. Console output | |
21143 | notifications are used to report output of CLI commands, as well as | |
21144 | diagnostics for other commands. Status notifications are used to | |
21145 | report the progress of a long-running operation. Naturally, including | |
21146 | this information in command response would mean no output is produced | |
21147 | until the command is finished, which is undesirable. | |
21148 | ||
21149 | @item | |
21150 | General notifications. Commands may have various side effects on | |
21151 | the @value{GDBN} or target state beyond their official purpose. For example, | |
21152 | a command may change the selected thread. Although such changes can | |
21153 | be included in command response, using notification allows for more | |
21154 | orthogonal frontend design. | |
21155 | ||
21156 | @end itemize | |
21157 | ||
21158 | There's no guarantee that whenever an MI command reports an error, | |
21159 | @value{GDBN} or the target are in any specific state, and especially, | |
21160 | the state is not reverted to the state before the MI command was | |
21161 | processed. Therefore, whenever an MI command results in an error, | |
21162 | we recommend that the frontend refreshes all the information shown in | |
21163 | the user interface. | |
21164 | ||
508094de NR |
21165 | |
21166 | @menu | |
21167 | * Context management:: | |
21168 | * Asynchronous and non-stop modes:: | |
21169 | * Thread groups:: | |
21170 | @end menu | |
21171 | ||
21172 | @node Context management | |
c3b108f7 VP |
21173 | @subsection Context management |
21174 | ||
21175 | In most cases when @value{GDBN} accesses the target, this access is | |
21176 | done in context of a specific thread and frame (@pxref{Frames}). | |
21177 | Often, even when accessing global data, the target requires that a thread | |
21178 | be specified. The CLI interface maintains the selected thread and frame, | |
21179 | and supplies them to target on each command. This is convenient, | |
21180 | because a command line user would not want to specify that information | |
21181 | explicitly on each command, and because user interacts with | |
21182 | @value{GDBN} via a single terminal, so no confusion is possible as | |
21183 | to what thread and frame are the current ones. | |
21184 | ||
21185 | In the case of MI, the concept of selected thread and frame is less | |
21186 | useful. First, a frontend can easily remember this information | |
21187 | itself. Second, a graphical frontend can have more than one window, | |
21188 | each one used for debugging a different thread, and the frontend might | |
21189 | want to access additional threads for internal purposes. This | |
21190 | increases the risk that by relying on implicitly selected thread, the | |
21191 | frontend may be operating on a wrong one. Therefore, each MI command | |
21192 | should explicitly specify which thread and frame to operate on. To | |
21193 | make it possible, each MI command accepts the @samp{--thread} and | |
21194 | @samp{--frame} options, the value to each is @value{GDBN} identifier | |
21195 | for thread and frame to operate on. | |
21196 | ||
21197 | Usually, each top-level window in a frontend allows the user to select | |
21198 | a thread and a frame, and remembers the user selection for further | |
21199 | operations. However, in some cases @value{GDBN} may suggest that the | |
21200 | current thread be changed. For example, when stopping on a breakpoint | |
21201 | it is reasonable to switch to the thread where breakpoint is hit. For | |
21202 | another example, if the user issues the CLI @samp{thread} command via | |
21203 | the frontend, it is desirable to change the frontend's selected thread to the | |
21204 | one specified by user. @value{GDBN} communicates the suggestion to | |
21205 | change current thread using the @samp{=thread-selected} notification. | |
21206 | No such notification is available for the selected frame at the moment. | |
21207 | ||
21208 | Note that historically, MI shares the selected thread with CLI, so | |
21209 | frontends used the @code{-thread-select} to execute commands in the | |
21210 | right context. However, getting this to work right is cumbersome. The | |
21211 | simplest way is for frontend to emit @code{-thread-select} command | |
21212 | before every command. This doubles the number of commands that need | |
21213 | to be sent. The alternative approach is to suppress @code{-thread-select} | |
21214 | if the selected thread in @value{GDBN} is supposed to be identical to the | |
21215 | thread the frontend wants to operate on. However, getting this | |
21216 | optimization right can be tricky. In particular, if the frontend | |
21217 | sends several commands to @value{GDBN}, and one of the commands changes the | |
21218 | selected thread, then the behaviour of subsequent commands will | |
21219 | change. So, a frontend should either wait for response from such | |
21220 | problematic commands, or explicitly add @code{-thread-select} for | |
21221 | all subsequent commands. No frontend is known to do this exactly | |
21222 | right, so it is suggested to just always pass the @samp{--thread} and | |
21223 | @samp{--frame} options. | |
21224 | ||
508094de | 21225 | @node Asynchronous and non-stop modes |
c3b108f7 VP |
21226 | @subsection Asynchronous command execution and non-stop mode |
21227 | ||
21228 | On some targets, @value{GDBN} is capable of processing MI commands | |
21229 | even while the target is running. This is called @dfn{asynchronous | |
21230 | command execution} (@pxref{Background Execution}). The frontend may | |
21231 | specify a preferrence for asynchronous execution using the | |
21232 | @code{-gdb-set target-async 1} command, which should be emitted before | |
21233 | either running the executable or attaching to the target. After the | |
21234 | frontend has started the executable or attached to the target, it can | |
21235 | find if asynchronous execution is enabled using the | |
21236 | @code{-list-target-features} command. | |
21237 | ||
21238 | Even if @value{GDBN} can accept a command while target is running, | |
21239 | many commands that access the target do not work when the target is | |
21240 | running. Therefore, asynchronous command execution is most useful | |
21241 | when combined with non-stop mode (@pxref{Non-Stop Mode}). Then, | |
21242 | it is possible to examine the state of one thread, while other threads | |
21243 | are running. | |
21244 | ||
21245 | When a given thread is running, MI commands that try to access the | |
21246 | target in the context of that thread may not work, or may work only on | |
21247 | some targets. In particular, commands that try to operate on thread's | |
21248 | stack will not work, on any target. Commands that read memory, or | |
21249 | modify breakpoints, may work or not work, depending on the target. Note | |
21250 | that even commands that operate on global state, such as @code{print}, | |
21251 | @code{set}, and breakpoint commands, still access the target in the | |
21252 | context of a specific thread, so frontend should try to find a | |
21253 | stopped thread and perform the operation on that thread (using the | |
21254 | @samp{--thread} option). | |
21255 | ||
21256 | Which commands will work in the context of a running thread is | |
21257 | highly target dependent. However, the two commands | |
21258 | @code{-exec-interrupt}, to stop a thread, and @code{-thread-info}, | |
21259 | to find the state of a thread, will always work. | |
21260 | ||
508094de | 21261 | @node Thread groups |
c3b108f7 VP |
21262 | @subsection Thread groups |
21263 | @value{GDBN} may be used to debug several processes at the same time. | |
21264 | On some platfroms, @value{GDBN} may support debugging of several | |
21265 | hardware systems, each one having several cores with several different | |
21266 | processes running on each core. This section describes the MI | |
21267 | mechanism to support such debugging scenarios. | |
21268 | ||
21269 | The key observation is that regardless of the structure of the | |
21270 | target, MI can have a global list of threads, because most commands that | |
21271 | accept the @samp{--thread} option do not need to know what process that | |
21272 | thread belongs to. Therefore, it is not necessary to introduce | |
21273 | neither additional @samp{--process} option, nor an notion of the | |
21274 | current process in the MI interface. The only strictly new feature | |
21275 | that is required is the ability to find how the threads are grouped | |
21276 | into processes. | |
21277 | ||
21278 | To allow the user to discover such grouping, and to support arbitrary | |
21279 | hierarchy of machines/cores/processes, MI introduces the concept of a | |
21280 | @dfn{thread group}. Thread group is a collection of threads and other | |
21281 | thread groups. A thread group always has a string identifier, a type, | |
21282 | and may have additional attributes specific to the type. A new | |
21283 | command, @code{-list-thread-groups}, returns the list of top-level | |
21284 | thread groups, which correspond to processes that @value{GDBN} is | |
21285 | debugging at the moment. By passing an identifier of a thread group | |
21286 | to the @code{-list-thread-groups} command, it is possible to obtain | |
21287 | the members of specific thread group. | |
21288 | ||
21289 | To allow the user to easily discover processes, and other objects, he | |
21290 | wishes to debug, a concept of @dfn{available thread group} is | |
21291 | introduced. Available thread group is an thread group that | |
21292 | @value{GDBN} is not debugging, but that can be attached to, using the | |
21293 | @code{-target-attach} command. The list of available top-level thread | |
21294 | groups can be obtained using @samp{-list-thread-groups --available}. | |
21295 | In general, the content of a thread group may be only retrieved only | |
21296 | after attaching to that thread group. | |
21297 | ||
922fbb7b AC |
21298 | @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% |
21299 | @node GDB/MI Command Syntax | |
21300 | @section @sc{gdb/mi} Command Syntax | |
21301 | ||
21302 | @menu | |
21303 | * GDB/MI Input Syntax:: | |
21304 | * GDB/MI Output Syntax:: | |
922fbb7b AC |
21305 | @end menu |
21306 | ||
21307 | @node GDB/MI Input Syntax | |
21308 | @subsection @sc{gdb/mi} Input Syntax | |
21309 | ||
21310 | @cindex input syntax for @sc{gdb/mi} | |
21311 | @cindex @sc{gdb/mi}, input syntax | |
21312 | @table @code | |
21313 | @item @var{command} @expansion{} | |
21314 | @code{@var{cli-command} | @var{mi-command}} | |
21315 | ||
21316 | @item @var{cli-command} @expansion{} | |
21317 | @code{[ @var{token} ] @var{cli-command} @var{nl}}, where | |
21318 | @var{cli-command} is any existing @value{GDBN} CLI command. | |
21319 | ||
21320 | @item @var{mi-command} @expansion{} | |
21321 | @code{[ @var{token} ] "-" @var{operation} ( " " @var{option} )* | |
21322 | @code{[} " --" @code{]} ( " " @var{parameter} )* @var{nl}} | |
21323 | ||
21324 | @item @var{token} @expansion{} | |
21325 | "any sequence of digits" | |
21326 | ||
21327 | @item @var{option} @expansion{} | |
21328 | @code{"-" @var{parameter} [ " " @var{parameter} ]} | |
21329 | ||
21330 | @item @var{parameter} @expansion{} | |
21331 | @code{@var{non-blank-sequence} | @var{c-string}} | |
21332 | ||
21333 | @item @var{operation} @expansion{} | |
21334 | @emph{any of the operations described in this chapter} | |
21335 | ||
21336 | @item @var{non-blank-sequence} @expansion{} | |
21337 | @emph{anything, provided it doesn't contain special characters such as | |
21338 | "-", @var{nl}, """ and of course " "} | |
21339 | ||
21340 | @item @var{c-string} @expansion{} | |
21341 | @code{""" @var{seven-bit-iso-c-string-content} """} | |
21342 | ||
21343 | @item @var{nl} @expansion{} | |
21344 | @code{CR | CR-LF} | |
21345 | @end table | |
21346 | ||
21347 | @noindent | |
21348 | Notes: | |
21349 | ||
21350 | @itemize @bullet | |
21351 | @item | |
21352 | The CLI commands are still handled by the @sc{mi} interpreter; their | |
21353 | output is described below. | |
21354 | ||
21355 | @item | |
21356 | The @code{@var{token}}, when present, is passed back when the command | |
21357 | finishes. | |
21358 | ||
21359 | @item | |
21360 | Some @sc{mi} commands accept optional arguments as part of the parameter | |
21361 | list. Each option is identified by a leading @samp{-} (dash) and may be | |
21362 | followed by an optional argument parameter. Options occur first in the | |
21363 | parameter list and can be delimited from normal parameters using | |
21364 | @samp{--} (this is useful when some parameters begin with a dash). | |
21365 | @end itemize | |
21366 | ||
21367 | Pragmatics: | |
21368 | ||
21369 | @itemize @bullet | |
21370 | @item | |
21371 | We want easy access to the existing CLI syntax (for debugging). | |
21372 | ||
21373 | @item | |
21374 | We want it to be easy to spot a @sc{mi} operation. | |
21375 | @end itemize | |
21376 | ||
21377 | @node GDB/MI Output Syntax | |
21378 | @subsection @sc{gdb/mi} Output Syntax | |
21379 | ||
21380 | @cindex output syntax of @sc{gdb/mi} | |
21381 | @cindex @sc{gdb/mi}, output syntax | |
21382 | The output from @sc{gdb/mi} consists of zero or more out-of-band records | |
21383 | followed, optionally, by a single result record. This result record | |
21384 | is for the most recent command. The sequence of output records is | |
594fe323 | 21385 | terminated by @samp{(gdb)}. |
922fbb7b AC |
21386 | |
21387 | If an input command was prefixed with a @code{@var{token}} then the | |
21388 | corresponding output for that command will also be prefixed by that same | |
21389 | @var{token}. | |
21390 | ||
21391 | @table @code | |
21392 | @item @var{output} @expansion{} | |
594fe323 | 21393 | @code{( @var{out-of-band-record} )* [ @var{result-record} ] "(gdb)" @var{nl}} |
922fbb7b AC |
21394 | |
21395 | @item @var{result-record} @expansion{} | |
21396 | @code{ [ @var{token} ] "^" @var{result-class} ( "," @var{result} )* @var{nl}} | |
21397 | ||
21398 | @item @var{out-of-band-record} @expansion{} | |
21399 | @code{@var{async-record} | @var{stream-record}} | |
21400 | ||
21401 | @item @var{async-record} @expansion{} | |
21402 | @code{@var{exec-async-output} | @var{status-async-output} | @var{notify-async-output}} | |
21403 | ||
21404 | @item @var{exec-async-output} @expansion{} | |
21405 | @code{[ @var{token} ] "*" @var{async-output}} | |
21406 | ||
21407 | @item @var{status-async-output} @expansion{} | |
21408 | @code{[ @var{token} ] "+" @var{async-output}} | |
21409 | ||
21410 | @item @var{notify-async-output} @expansion{} | |
21411 | @code{[ @var{token} ] "=" @var{async-output}} | |
21412 | ||
21413 | @item @var{async-output} @expansion{} | |
21414 | @code{@var{async-class} ( "," @var{result} )* @var{nl}} | |
21415 | ||
21416 | @item @var{result-class} @expansion{} | |
21417 | @code{"done" | "running" | "connected" | "error" | "exit"} | |
21418 | ||
21419 | @item @var{async-class} @expansion{} | |
21420 | @code{"stopped" | @var{others}} (where @var{others} will be added | |
21421 | depending on the needs---this is still in development). | |
21422 | ||
21423 | @item @var{result} @expansion{} | |
21424 | @code{ @var{variable} "=" @var{value}} | |
21425 | ||
21426 | @item @var{variable} @expansion{} | |
21427 | @code{ @var{string} } | |
21428 | ||
21429 | @item @var{value} @expansion{} | |
21430 | @code{ @var{const} | @var{tuple} | @var{list} } | |
21431 | ||
21432 | @item @var{const} @expansion{} | |
21433 | @code{@var{c-string}} | |
21434 | ||
21435 | @item @var{tuple} @expansion{} | |
21436 | @code{ "@{@}" | "@{" @var{result} ( "," @var{result} )* "@}" } | |
21437 | ||
21438 | @item @var{list} @expansion{} | |
21439 | @code{ "[]" | "[" @var{value} ( "," @var{value} )* "]" | "[" | |
21440 | @var{result} ( "," @var{result} )* "]" } | |
21441 | ||
21442 | @item @var{stream-record} @expansion{} | |
21443 | @code{@var{console-stream-output} | @var{target-stream-output} | @var{log-stream-output}} | |
21444 | ||
21445 | @item @var{console-stream-output} @expansion{} | |
21446 | @code{"~" @var{c-string}} | |
21447 | ||
21448 | @item @var{target-stream-output} @expansion{} | |
21449 | @code{"@@" @var{c-string}} | |
21450 | ||
21451 | @item @var{log-stream-output} @expansion{} | |
21452 | @code{"&" @var{c-string}} | |
21453 | ||
21454 | @item @var{nl} @expansion{} | |
21455 | @code{CR | CR-LF} | |
21456 | ||
21457 | @item @var{token} @expansion{} | |
21458 | @emph{any sequence of digits}. | |
21459 | @end table | |
21460 | ||
21461 | @noindent | |
21462 | Notes: | |
21463 | ||
21464 | @itemize @bullet | |
21465 | @item | |
21466 | All output sequences end in a single line containing a period. | |
21467 | ||
21468 | @item | |
721c02de VP |
21469 | The @code{@var{token}} is from the corresponding request. Note that |
21470 | for all async output, while the token is allowed by the grammar and | |
21471 | may be output by future versions of @value{GDBN} for select async | |
21472 | output messages, it is generally omitted. Frontends should treat | |
21473 | all async output as reporting general changes in the state of the | |
21474 | target and there should be no need to associate async output to any | |
21475 | prior command. | |
922fbb7b AC |
21476 | |
21477 | @item | |
21478 | @cindex status output in @sc{gdb/mi} | |
21479 | @var{status-async-output} contains on-going status information about the | |
21480 | progress of a slow operation. It can be discarded. All status output is | |
21481 | prefixed by @samp{+}. | |
21482 | ||
21483 | @item | |
21484 | @cindex async output in @sc{gdb/mi} | |
21485 | @var{exec-async-output} contains asynchronous state change on the target | |
21486 | (stopped, started, disappeared). All async output is prefixed by | |
21487 | @samp{*}. | |
21488 | ||
21489 | @item | |
21490 | @cindex notify output in @sc{gdb/mi} | |
21491 | @var{notify-async-output} contains supplementary information that the | |
21492 | client should handle (e.g., a new breakpoint information). All notify | |
21493 | output is prefixed by @samp{=}. | |
21494 | ||
21495 | @item | |
21496 | @cindex console output in @sc{gdb/mi} | |
21497 | @var{console-stream-output} is output that should be displayed as is in the | |
21498 | console. It is the textual response to a CLI command. All the console | |
21499 | output is prefixed by @samp{~}. | |
21500 | ||
21501 | @item | |
21502 | @cindex target output in @sc{gdb/mi} | |
21503 | @var{target-stream-output} is the output produced by the target program. | |
21504 | All the target output is prefixed by @samp{@@}. | |
21505 | ||
21506 | @item | |
21507 | @cindex log output in @sc{gdb/mi} | |
21508 | @var{log-stream-output} is output text coming from @value{GDBN}'s internals, for | |
21509 | instance messages that should be displayed as part of an error log. All | |
21510 | the log output is prefixed by @samp{&}. | |
21511 | ||
21512 | @item | |
21513 | @cindex list output in @sc{gdb/mi} | |
21514 | New @sc{gdb/mi} commands should only output @var{lists} containing | |
21515 | @var{values}. | |
21516 | ||
21517 | ||
21518 | @end itemize | |
21519 | ||
21520 | @xref{GDB/MI Stream Records, , @sc{gdb/mi} Stream Records}, for more | |
21521 | details about the various output records. | |
21522 | ||
922fbb7b AC |
21523 | @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% |
21524 | @node GDB/MI Compatibility with CLI | |
21525 | @section @sc{gdb/mi} Compatibility with CLI | |
21526 | ||
21527 | @cindex compatibility, @sc{gdb/mi} and CLI | |
21528 | @cindex @sc{gdb/mi}, compatibility with CLI | |
922fbb7b | 21529 | |
a2c02241 NR |
21530 | For the developers convenience CLI commands can be entered directly, |
21531 | but there may be some unexpected behaviour. For example, commands | |
21532 | that query the user will behave as if the user replied yes, breakpoint | |
21533 | command lists are not executed and some CLI commands, such as | |
21534 | @code{if}, @code{when} and @code{define}, prompt for further input with | |
21535 | @samp{>}, which is not valid MI output. | |
ef21caaf NR |
21536 | |
21537 | This feature may be removed at some stage in the future and it is | |
a2c02241 NR |
21538 | recommended that front ends use the @code{-interpreter-exec} command |
21539 | (@pxref{-interpreter-exec}). | |
922fbb7b | 21540 | |
af6eff6f NR |
21541 | @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% |
21542 | @node GDB/MI Development and Front Ends | |
21543 | @section @sc{gdb/mi} Development and Front Ends | |
21544 | @cindex @sc{gdb/mi} development | |
21545 | ||
21546 | The application which takes the MI output and presents the state of the | |
21547 | program being debugged to the user is called a @dfn{front end}. | |
21548 | ||
21549 | Although @sc{gdb/mi} is still incomplete, it is currently being used | |
21550 | by a variety of front ends to @value{GDBN}. This makes it difficult | |
21551 | to introduce new functionality without breaking existing usage. This | |
21552 | section tries to minimize the problems by describing how the protocol | |
21553 | might change. | |
21554 | ||
21555 | Some changes in MI need not break a carefully designed front end, and | |
21556 | for these the MI version will remain unchanged. The following is a | |
21557 | list of changes that may occur within one level, so front ends should | |
21558 | parse MI output in a way that can handle them: | |
21559 | ||
21560 | @itemize @bullet | |
21561 | @item | |
21562 | New MI commands may be added. | |
21563 | ||
21564 | @item | |
21565 | New fields may be added to the output of any MI command. | |
21566 | ||
36ece8b3 NR |
21567 | @item |
21568 | The range of values for fields with specified values, e.g., | |
9f708cb2 | 21569 | @code{in_scope} (@pxref{-var-update}) may be extended. |
36ece8b3 | 21570 | |
af6eff6f NR |
21571 | @c The format of field's content e.g type prefix, may change so parse it |
21572 | @c at your own risk. Yes, in general? | |
21573 | ||
21574 | @c The order of fields may change? Shouldn't really matter but it might | |
21575 | @c resolve inconsistencies. | |
21576 | @end itemize | |
21577 | ||
21578 | If the changes are likely to break front ends, the MI version level | |
21579 | will be increased by one. This will allow the front end to parse the | |
21580 | output according to the MI version. Apart from mi0, new versions of | |
21581 | @value{GDBN} will not support old versions of MI and it will be the | |
21582 | responsibility of the front end to work with the new one. | |
21583 | ||
21584 | @c Starting with mi3, add a new command -mi-version that prints the MI | |
21585 | @c version? | |
21586 | ||
21587 | The best way to avoid unexpected changes in MI that might break your front | |
21588 | end is to make your project known to @value{GDBN} developers and | |
7a9a6b69 | 21589 | follow development on @email{gdb@@sourceware.org} and |
fa0f268d | 21590 | @email{gdb-patches@@sourceware.org}. |
af6eff6f NR |
21591 | @cindex mailing lists |
21592 | ||
922fbb7b AC |
21593 | @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% |
21594 | @node GDB/MI Output Records | |
21595 | @section @sc{gdb/mi} Output Records | |
21596 | ||
21597 | @menu | |
21598 | * GDB/MI Result Records:: | |
21599 | * GDB/MI Stream Records:: | |
82f68b1c | 21600 | * GDB/MI Async Records:: |
c3b108f7 | 21601 | * GDB/MI Frame Information:: |
922fbb7b AC |
21602 | @end menu |
21603 | ||
21604 | @node GDB/MI Result Records | |
21605 | @subsection @sc{gdb/mi} Result Records | |
21606 | ||
21607 | @cindex result records in @sc{gdb/mi} | |
21608 | @cindex @sc{gdb/mi}, result records | |
21609 | In addition to a number of out-of-band notifications, the response to a | |
21610 | @sc{gdb/mi} command includes one of the following result indications: | |
21611 | ||
21612 | @table @code | |
21613 | @findex ^done | |
21614 | @item "^done" [ "," @var{results} ] | |
21615 | The synchronous operation was successful, @code{@var{results}} are the return | |
21616 | values. | |
21617 | ||
21618 | @item "^running" | |
21619 | @findex ^running | |
21620 | @c Is this one correct? Should it be an out-of-band notification? | |
21621 | The asynchronous operation was successfully started. The target is | |
21622 | running. | |
21623 | ||
ef21caaf NR |
21624 | @item "^connected" |
21625 | @findex ^connected | |
3f94c067 | 21626 | @value{GDBN} has connected to a remote target. |
ef21caaf | 21627 | |
922fbb7b AC |
21628 | @item "^error" "," @var{c-string} |
21629 | @findex ^error | |
21630 | The operation failed. The @code{@var{c-string}} contains the corresponding | |
21631 | error message. | |
ef21caaf NR |
21632 | |
21633 | @item "^exit" | |
21634 | @findex ^exit | |
3f94c067 | 21635 | @value{GDBN} has terminated. |
ef21caaf | 21636 | |
922fbb7b AC |
21637 | @end table |
21638 | ||
21639 | @node GDB/MI Stream Records | |
21640 | @subsection @sc{gdb/mi} Stream Records | |
21641 | ||
21642 | @cindex @sc{gdb/mi}, stream records | |
21643 | @cindex stream records in @sc{gdb/mi} | |
21644 | @value{GDBN} internally maintains a number of output streams: the console, the | |
21645 | target, and the log. The output intended for each of these streams is | |
21646 | funneled through the @sc{gdb/mi} interface using @dfn{stream records}. | |
21647 | ||
21648 | Each stream record begins with a unique @dfn{prefix character} which | |
21649 | identifies its stream (@pxref{GDB/MI Output Syntax, , @sc{gdb/mi} Output | |
21650 | Syntax}). In addition to the prefix, each stream record contains a | |
21651 | @code{@var{string-output}}. This is either raw text (with an implicit new | |
21652 | line) or a quoted C string (which does not contain an implicit newline). | |
21653 | ||
21654 | @table @code | |
21655 | @item "~" @var{string-output} | |
21656 | The console output stream contains text that should be displayed in the | |
21657 | CLI console window. It contains the textual responses to CLI commands. | |
21658 | ||
21659 | @item "@@" @var{string-output} | |
21660 | The target output stream contains any textual output from the running | |
ef21caaf NR |
21661 | target. This is only present when GDB's event loop is truly |
21662 | asynchronous, which is currently only the case for remote targets. | |
922fbb7b AC |
21663 | |
21664 | @item "&" @var{string-output} | |
21665 | The log stream contains debugging messages being produced by @value{GDBN}'s | |
21666 | internals. | |
21667 | @end table | |
21668 | ||
82f68b1c VP |
21669 | @node GDB/MI Async Records |
21670 | @subsection @sc{gdb/mi} Async Records | |
922fbb7b | 21671 | |
82f68b1c VP |
21672 | @cindex async records in @sc{gdb/mi} |
21673 | @cindex @sc{gdb/mi}, async records | |
21674 | @dfn{Async} records are used to notify the @sc{gdb/mi} client of | |
922fbb7b | 21675 | additional changes that have occurred. Those changes can either be a |
82f68b1c | 21676 | consequence of @sc{gdb/mi} commands (e.g., a breakpoint modified) or a result of |
922fbb7b AC |
21677 | target activity (e.g., target stopped). |
21678 | ||
8eb41542 | 21679 | The following is the list of possible async records: |
922fbb7b AC |
21680 | |
21681 | @table @code | |
034dad6f | 21682 | |
e1ac3328 VP |
21683 | @item *running,thread-id="@var{thread}" |
21684 | The target is now running. The @var{thread} field tells which | |
21685 | specific thread is now running, and can be @samp{all} if all threads | |
21686 | are running. The frontend should assume that no interaction with a | |
21687 | running thread is possible after this notification is produced. | |
21688 | The frontend should not assume that this notification is output | |
21689 | only once for any command. @value{GDBN} may emit this notification | |
21690 | several times, either for different threads, because it cannot resume | |
21691 | all threads together, or even for a single thread, if the thread must | |
21692 | be stepped though some code before letting it run freely. | |
21693 | ||
c3b108f7 | 21694 | @item *stopped,reason="@var{reason}",thread-id="@var{id}",stopped-threads="@var{stopped}" |
82f68b1c VP |
21695 | The target has stopped. The @var{reason} field can have one of the |
21696 | following values: | |
034dad6f BR |
21697 | |
21698 | @table @code | |
21699 | @item breakpoint-hit | |
21700 | A breakpoint was reached. | |
21701 | @item watchpoint-trigger | |
21702 | A watchpoint was triggered. | |
21703 | @item read-watchpoint-trigger | |
21704 | A read watchpoint was triggered. | |
21705 | @item access-watchpoint-trigger | |
21706 | An access watchpoint was triggered. | |
21707 | @item function-finished | |
21708 | An -exec-finish or similar CLI command was accomplished. | |
21709 | @item location-reached | |
21710 | An -exec-until or similar CLI command was accomplished. | |
21711 | @item watchpoint-scope | |
21712 | A watchpoint has gone out of scope. | |
21713 | @item end-stepping-range | |
21714 | An -exec-next, -exec-next-instruction, -exec-step, -exec-step-instruction or | |
21715 | similar CLI command was accomplished. | |
21716 | @item exited-signalled | |
21717 | The inferior exited because of a signal. | |
21718 | @item exited | |
21719 | The inferior exited. | |
21720 | @item exited-normally | |
21721 | The inferior exited normally. | |
21722 | @item signal-received | |
21723 | A signal was received by the inferior. | |
922fbb7b AC |
21724 | @end table |
21725 | ||
c3b108f7 VP |
21726 | The @var{id} field identifies the thread that directly caused the stop |
21727 | -- for example by hitting a breakpoint. Depending on whether all-stop | |
21728 | mode is in effect (@pxref{All-Stop Mode}), @value{GDBN} may either | |
21729 | stop all threads, or only the thread that directly triggered the stop. | |
21730 | If all threads are stopped, the @var{stopped} field will have the | |
21731 | value of @code{"all"}. Otherwise, the value of the @var{stopped} | |
21732 | field will be a list of thread identifiers. Presently, this list will | |
21733 | always include a single thread, but frontend should be prepared to see | |
21734 | several threads in the list. | |
21735 | ||
21736 | @item =thread-group-created,id="@var{id}" | |
21737 | @itemx =thread-group-exited,id="@var{id}" | |
21738 | A thread thread group either was attached to, or has exited/detached | |
21739 | from. The @var{id} field contains the @value{GDBN} identifier of the | |
21740 | thread group. | |
21741 | ||
21742 | @item =thread-created,id="@var{id}",group-id="@var{gid}" | |
21743 | @itemx =thread-exited,id="@var{id}",group-id="@var{gid}" | |
82f68b1c | 21744 | A thread either was created, or has exited. The @var{id} field |
c3b108f7 VP |
21745 | contains the @value{GDBN} identifier of the thread. The @var{gid} |
21746 | field identifies the thread group this thread belongs to. | |
66bb093b VP |
21747 | |
21748 | @item =thread-selected,id="@var{id}" | |
21749 | Informs that the selected thread was changed as result of the last | |
21750 | command. This notification is not emitted as result of @code{-thread-select} | |
21751 | command but is emitted whenever an MI command that is not documented | |
21752 | to change the selected thread actually changes it. In particular, | |
21753 | invoking, directly or indirectly (via user-defined command), the CLI | |
21754 | @code{thread} command, will generate this notification. | |
21755 | ||
21756 | We suggest that in response to this notification, front ends | |
21757 | highlight the selected thread and cause subsequent commands to apply to | |
21758 | that thread. | |
21759 | ||
c86cf029 VP |
21760 | @item =library-loaded,... |
21761 | Reports that a new library file was loaded by the program. This | |
21762 | notification has 4 fields---@var{id}, @var{target-name}, | |
134eb42c | 21763 | @var{host-name}, and @var{symbols-loaded}. The @var{id} field is an |
c86cf029 VP |
21764 | opaque identifier of the library. For remote debugging case, |
21765 | @var{target-name} and @var{host-name} fields give the name of the | |
134eb42c VP |
21766 | library file on the target, and on the host respectively. For native |
21767 | debugging, both those fields have the same value. The | |
c86cf029 VP |
21768 | @var{symbols-loaded} field reports if the debug symbols for this |
21769 | library are loaded. | |
21770 | ||
21771 | @item =library-unloaded,... | |
134eb42c | 21772 | Reports that a library was unloaded by the program. This notification |
c86cf029 VP |
21773 | has 3 fields---@var{id}, @var{target-name} and @var{host-name} with |
21774 | the same meaning as for the @code{=library-loaded} notification | |
21775 | ||
82f68b1c VP |
21776 | @end table |
21777 | ||
c3b108f7 VP |
21778 | @node GDB/MI Frame Information |
21779 | @subsection @sc{gdb/mi} Frame Information | |
21780 | ||
21781 | Response from many MI commands includes an information about stack | |
21782 | frame. This information is a tuple that may have the following | |
21783 | fields: | |
21784 | ||
21785 | @table @code | |
21786 | @item level | |
21787 | The level of the stack frame. The innermost frame has the level of | |
21788 | zero. This field is always present. | |
21789 | ||
21790 | @item func | |
21791 | The name of the function corresponding to the frame. This field may | |
21792 | be absent if @value{GDBN} is unable to determine the function name. | |
21793 | ||
21794 | @item addr | |
21795 | The code address for the frame. This field is always present. | |
21796 | ||
21797 | @item file | |
21798 | The name of the source files that correspond to the frame's code | |
21799 | address. This field may be absent. | |
21800 | ||
21801 | @item line | |
21802 | The source line corresponding to the frames' code address. This field | |
21803 | may be absent. | |
21804 | ||
21805 | @item from | |
21806 | The name of the binary file (either executable or shared library) the | |
21807 | corresponds to the frame's code address. This field may be absent. | |
21808 | ||
21809 | @end table | |
82f68b1c | 21810 | |
922fbb7b | 21811 | |
ef21caaf NR |
21812 | @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% |
21813 | @node GDB/MI Simple Examples | |
21814 | @section Simple Examples of @sc{gdb/mi} Interaction | |
21815 | @cindex @sc{gdb/mi}, simple examples | |
21816 | ||
21817 | This subsection presents several simple examples of interaction using | |
21818 | the @sc{gdb/mi} interface. In these examples, @samp{->} means that the | |
21819 | following line is passed to @sc{gdb/mi} as input, while @samp{<-} means | |
21820 | the output received from @sc{gdb/mi}. | |
21821 | ||
d3e8051b | 21822 | Note the line breaks shown in the examples are here only for |
ef21caaf NR |
21823 | readability, they don't appear in the real output. |
21824 | ||
79a6e687 | 21825 | @subheading Setting a Breakpoint |
ef21caaf NR |
21826 | |
21827 | Setting a breakpoint generates synchronous output which contains detailed | |
21828 | information of the breakpoint. | |
21829 | ||
21830 | @smallexample | |
21831 | -> -break-insert main | |
21832 | <- ^done,bkpt=@{number="1",type="breakpoint",disp="keep", | |
21833 | enabled="y",addr="0x08048564",func="main",file="myprog.c", | |
21834 | fullname="/home/nickrob/myprog.c",line="68",times="0"@} | |
21835 | <- (gdb) | |
21836 | @end smallexample | |
21837 | ||
21838 | @subheading Program Execution | |
21839 | ||
21840 | Program execution generates asynchronous records and MI gives the | |
21841 | reason that execution stopped. | |
21842 | ||
21843 | @smallexample | |
21844 | -> -exec-run | |
21845 | <- ^running | |
21846 | <- (gdb) | |
a47ec5fe | 21847 | <- *stopped,reason="breakpoint-hit",disp="keep",bkptno="1",thread-id="0", |
ef21caaf NR |
21848 | frame=@{addr="0x08048564",func="main", |
21849 | args=[@{name="argc",value="1"@},@{name="argv",value="0xbfc4d4d4"@}], | |
21850 | file="myprog.c",fullname="/home/nickrob/myprog.c",line="68"@} | |
21851 | <- (gdb) | |
21852 | -> -exec-continue | |
21853 | <- ^running | |
21854 | <- (gdb) | |
21855 | <- *stopped,reason="exited-normally" | |
21856 | <- (gdb) | |
21857 | @end smallexample | |
21858 | ||
3f94c067 | 21859 | @subheading Quitting @value{GDBN} |
ef21caaf | 21860 | |
3f94c067 | 21861 | Quitting @value{GDBN} just prints the result class @samp{^exit}. |
ef21caaf NR |
21862 | |
21863 | @smallexample | |
21864 | -> (gdb) | |
21865 | <- -gdb-exit | |
21866 | <- ^exit | |
21867 | @end smallexample | |
21868 | ||
a2c02241 | 21869 | @subheading A Bad Command |
ef21caaf NR |
21870 | |
21871 | Here's what happens if you pass a non-existent command: | |
21872 | ||
21873 | @smallexample | |
21874 | -> -rubbish | |
21875 | <- ^error,msg="Undefined MI command: rubbish" | |
594fe323 | 21876 | <- (gdb) |
ef21caaf NR |
21877 | @end smallexample |
21878 | ||
21879 | ||
922fbb7b AC |
21880 | @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% |
21881 | @node GDB/MI Command Description Format | |
21882 | @section @sc{gdb/mi} Command Description Format | |
21883 | ||
21884 | The remaining sections describe blocks of commands. Each block of | |
21885 | commands is laid out in a fashion similar to this section. | |
21886 | ||
922fbb7b AC |
21887 | @subheading Motivation |
21888 | ||
21889 | The motivation for this collection of commands. | |
21890 | ||
21891 | @subheading Introduction | |
21892 | ||
21893 | A brief introduction to this collection of commands as a whole. | |
21894 | ||
21895 | @subheading Commands | |
21896 | ||
21897 | For each command in the block, the following is described: | |
21898 | ||
21899 | @subsubheading Synopsis | |
21900 | ||
21901 | @smallexample | |
21902 | -command @var{args}@dots{} | |
21903 | @end smallexample | |
21904 | ||
922fbb7b AC |
21905 | @subsubheading Result |
21906 | ||
265eeb58 | 21907 | @subsubheading @value{GDBN} Command |
922fbb7b | 21908 | |
265eeb58 | 21909 | The corresponding @value{GDBN} CLI command(s), if any. |
922fbb7b AC |
21910 | |
21911 | @subsubheading Example | |
21912 | ||
ef21caaf NR |
21913 | Example(s) formatted for readability. Some of the described commands have |
21914 | not been implemented yet and these are labeled N.A.@: (not available). | |
21915 | ||
21916 | ||
922fbb7b | 21917 | @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% |
ef21caaf NR |
21918 | @node GDB/MI Breakpoint Commands |
21919 | @section @sc{gdb/mi} Breakpoint Commands | |
922fbb7b AC |
21920 | |
21921 | @cindex breakpoint commands for @sc{gdb/mi} | |
21922 | @cindex @sc{gdb/mi}, breakpoint commands | |
21923 | This section documents @sc{gdb/mi} commands for manipulating | |
21924 | breakpoints. | |
21925 | ||
21926 | @subheading The @code{-break-after} Command | |
21927 | @findex -break-after | |
21928 | ||
21929 | @subsubheading Synopsis | |
21930 | ||
21931 | @smallexample | |
21932 | -break-after @var{number} @var{count} | |
21933 | @end smallexample | |
21934 | ||
21935 | The breakpoint number @var{number} is not in effect until it has been | |
21936 | hit @var{count} times. To see how this is reflected in the output of | |
21937 | the @samp{-break-list} command, see the description of the | |
21938 | @samp{-break-list} command below. | |
21939 | ||
21940 | @subsubheading @value{GDBN} Command | |
21941 | ||
21942 | The corresponding @value{GDBN} command is @samp{ignore}. | |
21943 | ||
21944 | @subsubheading Example | |
21945 | ||
21946 | @smallexample | |
594fe323 | 21947 | (gdb) |
922fbb7b | 21948 | -break-insert main |
a47ec5fe AR |
21949 | ^done,bkpt=@{number="1",type="breakpoint",disp="keep", |
21950 | enabled="y",addr="0x000100d0",func="main",file="hello.c", | |
948d5102 | 21951 | fullname="/home/foo/hello.c",line="5",times="0"@} |
594fe323 | 21952 | (gdb) |
922fbb7b AC |
21953 | -break-after 1 3 |
21954 | ~ | |
21955 | ^done | |
594fe323 | 21956 | (gdb) |
922fbb7b AC |
21957 | -break-list |
21958 | ^done,BreakpointTable=@{nr_rows="1",nr_cols="6", | |
21959 | hdr=[@{width="3",alignment="-1",col_name="number",colhdr="Num"@}, | |
21960 | @{width="14",alignment="-1",col_name="type",colhdr="Type"@}, | |
21961 | @{width="4",alignment="-1",col_name="disp",colhdr="Disp"@}, | |
21962 | @{width="3",alignment="-1",col_name="enabled",colhdr="Enb"@}, | |
21963 | @{width="10",alignment="-1",col_name="addr",colhdr="Address"@}, | |
21964 | @{width="40",alignment="2",col_name="what",colhdr="What"@}], | |
21965 | body=[bkpt=@{number="1",type="breakpoint",disp="keep",enabled="y", | |
948d5102 NR |
21966 | addr="0x000100d0",func="main",file="hello.c",fullname="/home/foo/hello.c", |
21967 | line="5",times="0",ignore="3"@}]@} | |
594fe323 | 21968 | (gdb) |
922fbb7b AC |
21969 | @end smallexample |
21970 | ||
21971 | @ignore | |
21972 | @subheading The @code{-break-catch} Command | |
21973 | @findex -break-catch | |
48cb2d85 | 21974 | @end ignore |
922fbb7b AC |
21975 | |
21976 | @subheading The @code{-break-commands} Command | |
21977 | @findex -break-commands | |
922fbb7b | 21978 | |
48cb2d85 VP |
21979 | @subsubheading Synopsis |
21980 | ||
21981 | @smallexample | |
21982 | -break-commands @var{number} [ @var{command1} ... @var{commandN} ] | |
21983 | @end smallexample | |
21984 | ||
21985 | Specifies the CLI commands that should be executed when breakpoint | |
21986 | @var{number} is hit. The parameters @var{command1} to @var{commandN} | |
21987 | are the commands. If no command is specified, any previously-set | |
21988 | commands are cleared. @xref{Break Commands}. Typical use of this | |
21989 | functionality is tracing a program, that is, printing of values of | |
21990 | some variables whenever breakpoint is hit and then continuing. | |
21991 | ||
21992 | @subsubheading @value{GDBN} Command | |
21993 | ||
21994 | The corresponding @value{GDBN} command is @samp{commands}. | |
21995 | ||
21996 | @subsubheading Example | |
21997 | ||
21998 | @smallexample | |
21999 | (gdb) | |
22000 | -break-insert main | |
22001 | ^done,bkpt=@{number="1",type="breakpoint",disp="keep", | |
22002 | enabled="y",addr="0x000100d0",func="main",file="hello.c", | |
22003 | fullname="/home/foo/hello.c",line="5",times="0"@} | |
22004 | (gdb) | |
22005 | -break-commands 1 "print v" "continue" | |
22006 | ^done | |
22007 | (gdb) | |
22008 | @end smallexample | |
922fbb7b AC |
22009 | |
22010 | @subheading The @code{-break-condition} Command | |
22011 | @findex -break-condition | |
22012 | ||
22013 | @subsubheading Synopsis | |
22014 | ||
22015 | @smallexample | |
22016 | -break-condition @var{number} @var{expr} | |
22017 | @end smallexample | |
22018 | ||
22019 | Breakpoint @var{number} will stop the program only if the condition in | |
22020 | @var{expr} is true. The condition becomes part of the | |
22021 | @samp{-break-list} output (see the description of the @samp{-break-list} | |
22022 | command below). | |
22023 | ||
22024 | @subsubheading @value{GDBN} Command | |
22025 | ||
22026 | The corresponding @value{GDBN} command is @samp{condition}. | |
22027 | ||
22028 | @subsubheading Example | |
22029 | ||
22030 | @smallexample | |
594fe323 | 22031 | (gdb) |
922fbb7b AC |
22032 | -break-condition 1 1 |
22033 | ^done | |
594fe323 | 22034 | (gdb) |
922fbb7b AC |
22035 | -break-list |
22036 | ^done,BreakpointTable=@{nr_rows="1",nr_cols="6", | |
22037 | hdr=[@{width="3",alignment="-1",col_name="number",colhdr="Num"@}, | |
22038 | @{width="14",alignment="-1",col_name="type",colhdr="Type"@}, | |
22039 | @{width="4",alignment="-1",col_name="disp",colhdr="Disp"@}, | |
22040 | @{width="3",alignment="-1",col_name="enabled",colhdr="Enb"@}, | |
22041 | @{width="10",alignment="-1",col_name="addr",colhdr="Address"@}, | |
22042 | @{width="40",alignment="2",col_name="what",colhdr="What"@}], | |
22043 | body=[bkpt=@{number="1",type="breakpoint",disp="keep",enabled="y", | |
948d5102 NR |
22044 | addr="0x000100d0",func="main",file="hello.c",fullname="/home/foo/hello.c", |
22045 | line="5",cond="1",times="0",ignore="3"@}]@} | |
594fe323 | 22046 | (gdb) |
922fbb7b AC |
22047 | @end smallexample |
22048 | ||
22049 | @subheading The @code{-break-delete} Command | |
22050 | @findex -break-delete | |
22051 | ||
22052 | @subsubheading Synopsis | |
22053 | ||
22054 | @smallexample | |
22055 | -break-delete ( @var{breakpoint} )+ | |
22056 | @end smallexample | |
22057 | ||
22058 | Delete the breakpoint(s) whose number(s) are specified in the argument | |
22059 | list. This is obviously reflected in the breakpoint list. | |
22060 | ||
79a6e687 | 22061 | @subsubheading @value{GDBN} Command |
922fbb7b AC |
22062 | |
22063 | The corresponding @value{GDBN} command is @samp{delete}. | |
22064 | ||
22065 | @subsubheading Example | |
22066 | ||
22067 | @smallexample | |
594fe323 | 22068 | (gdb) |
922fbb7b AC |
22069 | -break-delete 1 |
22070 | ^done | |
594fe323 | 22071 | (gdb) |
922fbb7b AC |
22072 | -break-list |
22073 | ^done,BreakpointTable=@{nr_rows="0",nr_cols="6", | |
22074 | hdr=[@{width="3",alignment="-1",col_name="number",colhdr="Num"@}, | |
22075 | @{width="14",alignment="-1",col_name="type",colhdr="Type"@}, | |
22076 | @{width="4",alignment="-1",col_name="disp",colhdr="Disp"@}, | |
22077 | @{width="3",alignment="-1",col_name="enabled",colhdr="Enb"@}, | |
22078 | @{width="10",alignment="-1",col_name="addr",colhdr="Address"@}, | |
22079 | @{width="40",alignment="2",col_name="what",colhdr="What"@}], | |
22080 | body=[]@} | |
594fe323 | 22081 | (gdb) |
922fbb7b AC |
22082 | @end smallexample |
22083 | ||
22084 | @subheading The @code{-break-disable} Command | |
22085 | @findex -break-disable | |
22086 | ||
22087 | @subsubheading Synopsis | |
22088 | ||
22089 | @smallexample | |
22090 | -break-disable ( @var{breakpoint} )+ | |
22091 | @end smallexample | |
22092 | ||
22093 | Disable the named @var{breakpoint}(s). The field @samp{enabled} in the | |
22094 | break list is now set to @samp{n} for the named @var{breakpoint}(s). | |
22095 | ||
22096 | @subsubheading @value{GDBN} Command | |
22097 | ||
22098 | The corresponding @value{GDBN} command is @samp{disable}. | |
22099 | ||
22100 | @subsubheading Example | |
22101 | ||
22102 | @smallexample | |
594fe323 | 22103 | (gdb) |
922fbb7b AC |
22104 | -break-disable 2 |
22105 | ^done | |
594fe323 | 22106 | (gdb) |
922fbb7b AC |
22107 | -break-list |
22108 | ^done,BreakpointTable=@{nr_rows="1",nr_cols="6", | |
22109 | hdr=[@{width="3",alignment="-1",col_name="number",colhdr="Num"@}, | |
22110 | @{width="14",alignment="-1",col_name="type",colhdr="Type"@}, | |
22111 | @{width="4",alignment="-1",col_name="disp",colhdr="Disp"@}, | |
22112 | @{width="3",alignment="-1",col_name="enabled",colhdr="Enb"@}, | |
22113 | @{width="10",alignment="-1",col_name="addr",colhdr="Address"@}, | |
22114 | @{width="40",alignment="2",col_name="what",colhdr="What"@}], | |
22115 | body=[bkpt=@{number="2",type="breakpoint",disp="keep",enabled="n", | |
948d5102 NR |
22116 | addr="0x000100d0",func="main",file="hello.c",fullname="/home/foo/hello.c", |
22117 | line="5",times="0"@}]@} | |
594fe323 | 22118 | (gdb) |
922fbb7b AC |
22119 | @end smallexample |
22120 | ||
22121 | @subheading The @code{-break-enable} Command | |
22122 | @findex -break-enable | |
22123 | ||
22124 | @subsubheading Synopsis | |
22125 | ||
22126 | @smallexample | |
22127 | -break-enable ( @var{breakpoint} )+ | |
22128 | @end smallexample | |
22129 | ||
22130 | Enable (previously disabled) @var{breakpoint}(s). | |
22131 | ||
22132 | @subsubheading @value{GDBN} Command | |
22133 | ||
22134 | The corresponding @value{GDBN} command is @samp{enable}. | |
22135 | ||
22136 | @subsubheading Example | |
22137 | ||
22138 | @smallexample | |
594fe323 | 22139 | (gdb) |
922fbb7b AC |
22140 | -break-enable 2 |
22141 | ^done | |
594fe323 | 22142 | (gdb) |
922fbb7b AC |
22143 | -break-list |
22144 | ^done,BreakpointTable=@{nr_rows="1",nr_cols="6", | |
22145 | hdr=[@{width="3",alignment="-1",col_name="number",colhdr="Num"@}, | |
22146 | @{width="14",alignment="-1",col_name="type",colhdr="Type"@}, | |
22147 | @{width="4",alignment="-1",col_name="disp",colhdr="Disp"@}, | |
22148 | @{width="3",alignment="-1",col_name="enabled",colhdr="Enb"@}, | |
22149 | @{width="10",alignment="-1",col_name="addr",colhdr="Address"@}, | |
22150 | @{width="40",alignment="2",col_name="what",colhdr="What"@}], | |
22151 | body=[bkpt=@{number="2",type="breakpoint",disp="keep",enabled="y", | |
948d5102 NR |
22152 | addr="0x000100d0",func="main",file="hello.c",fullname="/home/foo/hello.c", |
22153 | line="5",times="0"@}]@} | |
594fe323 | 22154 | (gdb) |
922fbb7b AC |
22155 | @end smallexample |
22156 | ||
22157 | @subheading The @code{-break-info} Command | |
22158 | @findex -break-info | |
22159 | ||
22160 | @subsubheading Synopsis | |
22161 | ||
22162 | @smallexample | |
22163 | -break-info @var{breakpoint} | |
22164 | @end smallexample | |
22165 | ||
22166 | @c REDUNDANT??? | |
22167 | Get information about a single breakpoint. | |
22168 | ||
79a6e687 | 22169 | @subsubheading @value{GDBN} Command |
922fbb7b AC |
22170 | |
22171 | The corresponding @value{GDBN} command is @samp{info break @var{breakpoint}}. | |
22172 | ||
22173 | @subsubheading Example | |
22174 | N.A. | |
22175 | ||
22176 | @subheading The @code{-break-insert} Command | |
22177 | @findex -break-insert | |
22178 | ||
22179 | @subsubheading Synopsis | |
22180 | ||
22181 | @smallexample | |
41447f92 | 22182 | -break-insert [ -t ] [ -h ] [ -f ] [ -d ] |
922fbb7b | 22183 | [ -c @var{condition} ] [ -i @var{ignore-count} ] |
afe8ab22 | 22184 | [ -p @var{thread} ] [ @var{location} ] |
922fbb7b AC |
22185 | @end smallexample |
22186 | ||
22187 | @noindent | |
afe8ab22 | 22188 | If specified, @var{location}, can be one of: |
922fbb7b AC |
22189 | |
22190 | @itemize @bullet | |
22191 | @item function | |
22192 | @c @item +offset | |
22193 | @c @item -offset | |
22194 | @c @item linenum | |
22195 | @item filename:linenum | |
22196 | @item filename:function | |
22197 | @item *address | |
22198 | @end itemize | |
22199 | ||
22200 | The possible optional parameters of this command are: | |
22201 | ||
22202 | @table @samp | |
22203 | @item -t | |
948d5102 | 22204 | Insert a temporary breakpoint. |
922fbb7b AC |
22205 | @item -h |
22206 | Insert a hardware breakpoint. | |
22207 | @item -c @var{condition} | |
22208 | Make the breakpoint conditional on @var{condition}. | |
22209 | @item -i @var{ignore-count} | |
22210 | Initialize the @var{ignore-count}. | |
afe8ab22 VP |
22211 | @item -f |
22212 | If @var{location} cannot be parsed (for example if it | |
22213 | refers to unknown files or functions), create a pending | |
22214 | breakpoint. Without this flag, @value{GDBN} will report | |
22215 | an error, and won't create a breakpoint, if @var{location} | |
22216 | cannot be parsed. | |
41447f92 VP |
22217 | @item -d |
22218 | Create a disabled breakpoint. | |
922fbb7b AC |
22219 | @end table |
22220 | ||
22221 | @subsubheading Result | |
22222 | ||
22223 | The result is in the form: | |
22224 | ||
22225 | @smallexample | |
948d5102 NR |
22226 | ^done,bkpt=@{number="@var{number}",type="@var{type}",disp="del"|"keep", |
22227 | enabled="y"|"n",addr="@var{hex}",func="@var{funcname}",file="@var{filename}", | |
ef21caaf NR |
22228 | fullname="@var{full_filename}",line="@var{lineno}",[thread="@var{threadno},] |
22229 | times="@var{times}"@} | |
922fbb7b AC |
22230 | @end smallexample |
22231 | ||
22232 | @noindent | |
948d5102 NR |
22233 | where @var{number} is the @value{GDBN} number for this breakpoint, |
22234 | @var{funcname} is the name of the function where the breakpoint was | |
22235 | inserted, @var{filename} is the name of the source file which contains | |
22236 | this function, @var{lineno} is the source line number within that file | |
22237 | and @var{times} the number of times that the breakpoint has been hit | |
22238 | (always 0 for -break-insert but may be greater for -break-info or -break-list | |
22239 | which use the same output). | |
922fbb7b AC |
22240 | |
22241 | Note: this format is open to change. | |
22242 | @c An out-of-band breakpoint instead of part of the result? | |
22243 | ||
22244 | @subsubheading @value{GDBN} Command | |
22245 | ||
22246 | The corresponding @value{GDBN} commands are @samp{break}, @samp{tbreak}, | |
22247 | @samp{hbreak}, @samp{thbreak}, and @samp{rbreak}. | |
22248 | ||
22249 | @subsubheading Example | |
22250 | ||
22251 | @smallexample | |
594fe323 | 22252 | (gdb) |
922fbb7b | 22253 | -break-insert main |
948d5102 NR |
22254 | ^done,bkpt=@{number="1",addr="0x0001072c",file="recursive2.c", |
22255 | fullname="/home/foo/recursive2.c,line="4",times="0"@} | |
594fe323 | 22256 | (gdb) |
922fbb7b | 22257 | -break-insert -t foo |
948d5102 NR |
22258 | ^done,bkpt=@{number="2",addr="0x00010774",file="recursive2.c", |
22259 | fullname="/home/foo/recursive2.c,line="11",times="0"@} | |
594fe323 | 22260 | (gdb) |
922fbb7b AC |
22261 | -break-list |
22262 | ^done,BreakpointTable=@{nr_rows="2",nr_cols="6", | |
22263 | hdr=[@{width="3",alignment="-1",col_name="number",colhdr="Num"@}, | |
22264 | @{width="14",alignment="-1",col_name="type",colhdr="Type"@}, | |
22265 | @{width="4",alignment="-1",col_name="disp",colhdr="Disp"@}, | |
22266 | @{width="3",alignment="-1",col_name="enabled",colhdr="Enb"@}, | |
22267 | @{width="10",alignment="-1",col_name="addr",colhdr="Address"@}, | |
22268 | @{width="40",alignment="2",col_name="what",colhdr="What"@}], | |
22269 | body=[bkpt=@{number="1",type="breakpoint",disp="keep",enabled="y", | |
948d5102 NR |
22270 | addr="0x0001072c", func="main",file="recursive2.c", |
22271 | fullname="/home/foo/recursive2.c,"line="4",times="0"@}, | |
922fbb7b | 22272 | bkpt=@{number="2",type="breakpoint",disp="del",enabled="y", |
948d5102 NR |
22273 | addr="0x00010774",func="foo",file="recursive2.c", |
22274 | fullname="/home/foo/recursive2.c",line="11",times="0"@}]@} | |
594fe323 | 22275 | (gdb) |
922fbb7b AC |
22276 | -break-insert -r foo.* |
22277 | ~int foo(int, int); | |
948d5102 NR |
22278 | ^done,bkpt=@{number="3",addr="0x00010774",file="recursive2.c, |
22279 | "fullname="/home/foo/recursive2.c",line="11",times="0"@} | |
594fe323 | 22280 | (gdb) |
922fbb7b AC |
22281 | @end smallexample |
22282 | ||
22283 | @subheading The @code{-break-list} Command | |
22284 | @findex -break-list | |
22285 | ||
22286 | @subsubheading Synopsis | |
22287 | ||
22288 | @smallexample | |
22289 | -break-list | |
22290 | @end smallexample | |
22291 | ||
22292 | Displays the list of inserted breakpoints, showing the following fields: | |
22293 | ||
22294 | @table @samp | |
22295 | @item Number | |
22296 | number of the breakpoint | |
22297 | @item Type | |
22298 | type of the breakpoint: @samp{breakpoint} or @samp{watchpoint} | |
22299 | @item Disposition | |
22300 | should the breakpoint be deleted or disabled when it is hit: @samp{keep} | |
22301 | or @samp{nokeep} | |
22302 | @item Enabled | |
22303 | is the breakpoint enabled or no: @samp{y} or @samp{n} | |
22304 | @item Address | |
22305 | memory location at which the breakpoint is set | |
22306 | @item What | |
22307 | logical location of the breakpoint, expressed by function name, file | |
22308 | name, line number | |
22309 | @item Times | |
22310 | number of times the breakpoint has been hit | |
22311 | @end table | |
22312 | ||
22313 | If there are no breakpoints or watchpoints, the @code{BreakpointTable} | |
22314 | @code{body} field is an empty list. | |
22315 | ||
22316 | @subsubheading @value{GDBN} Command | |
22317 | ||
22318 | The corresponding @value{GDBN} command is @samp{info break}. | |
22319 | ||
22320 | @subsubheading Example | |
22321 | ||
22322 | @smallexample | |
594fe323 | 22323 | (gdb) |
922fbb7b AC |
22324 | -break-list |
22325 | ^done,BreakpointTable=@{nr_rows="2",nr_cols="6", | |
22326 | hdr=[@{width="3",alignment="-1",col_name="number",colhdr="Num"@}, | |
22327 | @{width="14",alignment="-1",col_name="type",colhdr="Type"@}, | |
22328 | @{width="4",alignment="-1",col_name="disp",colhdr="Disp"@}, | |
22329 | @{width="3",alignment="-1",col_name="enabled",colhdr="Enb"@}, | |
22330 | @{width="10",alignment="-1",col_name="addr",colhdr="Address"@}, | |
22331 | @{width="40",alignment="2",col_name="what",colhdr="What"@}], | |
22332 | body=[bkpt=@{number="1",type="breakpoint",disp="keep",enabled="y", | |
22333 | addr="0x000100d0",func="main",file="hello.c",line="5",times="0"@}, | |
22334 | bkpt=@{number="2",type="breakpoint",disp="keep",enabled="y", | |
948d5102 NR |
22335 | addr="0x00010114",func="foo",file="hello.c",fullname="/home/foo/hello.c", |
22336 | line="13",times="0"@}]@} | |
594fe323 | 22337 | (gdb) |
922fbb7b AC |
22338 | @end smallexample |
22339 | ||
22340 | Here's an example of the result when there are no breakpoints: | |
22341 | ||
22342 | @smallexample | |
594fe323 | 22343 | (gdb) |
922fbb7b AC |
22344 | -break-list |
22345 | ^done,BreakpointTable=@{nr_rows="0",nr_cols="6", | |
22346 | hdr=[@{width="3",alignment="-1",col_name="number",colhdr="Num"@}, | |
22347 | @{width="14",alignment="-1",col_name="type",colhdr="Type"@}, | |
22348 | @{width="4",alignment="-1",col_name="disp",colhdr="Disp"@}, | |
22349 | @{width="3",alignment="-1",col_name="enabled",colhdr="Enb"@}, | |
22350 | @{width="10",alignment="-1",col_name="addr",colhdr="Address"@}, | |
22351 | @{width="40",alignment="2",col_name="what",colhdr="What"@}], | |
22352 | body=[]@} | |
594fe323 | 22353 | (gdb) |
922fbb7b AC |
22354 | @end smallexample |
22355 | ||
22356 | @subheading The @code{-break-watch} Command | |
22357 | @findex -break-watch | |
22358 | ||
22359 | @subsubheading Synopsis | |
22360 | ||
22361 | @smallexample | |
22362 | -break-watch [ -a | -r ] | |
22363 | @end smallexample | |
22364 | ||
22365 | Create a watchpoint. With the @samp{-a} option it will create an | |
d3e8051b | 22366 | @dfn{access} watchpoint, i.e., a watchpoint that triggers either on a |
922fbb7b | 22367 | read from or on a write to the memory location. With the @samp{-r} |
d3e8051b | 22368 | option, the watchpoint created is a @dfn{read} watchpoint, i.e., it will |
922fbb7b AC |
22369 | trigger only when the memory location is accessed for reading. Without |
22370 | either of the options, the watchpoint created is a regular watchpoint, | |
d3e8051b | 22371 | i.e., it will trigger when the memory location is accessed for writing. |
79a6e687 | 22372 | @xref{Set Watchpoints, , Setting Watchpoints}. |
922fbb7b AC |
22373 | |
22374 | Note that @samp{-break-list} will report a single list of watchpoints and | |
22375 | breakpoints inserted. | |
22376 | ||
22377 | @subsubheading @value{GDBN} Command | |
22378 | ||
22379 | The corresponding @value{GDBN} commands are @samp{watch}, @samp{awatch}, and | |
22380 | @samp{rwatch}. | |
22381 | ||
22382 | @subsubheading Example | |
22383 | ||
22384 | Setting a watchpoint on a variable in the @code{main} function: | |
22385 | ||
22386 | @smallexample | |
594fe323 | 22387 | (gdb) |
922fbb7b AC |
22388 | -break-watch x |
22389 | ^done,wpt=@{number="2",exp="x"@} | |
594fe323 | 22390 | (gdb) |
922fbb7b AC |
22391 | -exec-continue |
22392 | ^running | |
0869d01b NR |
22393 | (gdb) |
22394 | *stopped,reason="watchpoint-trigger",wpt=@{number="2",exp="x"@}, | |
922fbb7b | 22395 | value=@{old="-268439212",new="55"@}, |
76ff342d | 22396 | frame=@{func="main",args=[],file="recursive2.c", |
948d5102 | 22397 | fullname="/home/foo/bar/recursive2.c",line="5"@} |
594fe323 | 22398 | (gdb) |
922fbb7b AC |
22399 | @end smallexample |
22400 | ||
22401 | Setting a watchpoint on a variable local to a function. @value{GDBN} will stop | |
22402 | the program execution twice: first for the variable changing value, then | |
22403 | for the watchpoint going out of scope. | |
22404 | ||
22405 | @smallexample | |
594fe323 | 22406 | (gdb) |
922fbb7b AC |
22407 | -break-watch C |
22408 | ^done,wpt=@{number="5",exp="C"@} | |
594fe323 | 22409 | (gdb) |
922fbb7b AC |
22410 | -exec-continue |
22411 | ^running | |
0869d01b NR |
22412 | (gdb) |
22413 | *stopped,reason="watchpoint-trigger", | |
922fbb7b AC |
22414 | wpt=@{number="5",exp="C"@},value=@{old="-276895068",new="3"@}, |
22415 | frame=@{func="callee4",args=[], | |
76ff342d DJ |
22416 | file="../../../devo/gdb/testsuite/gdb.mi/basics.c", |
22417 | fullname="/home/foo/bar/devo/gdb/testsuite/gdb.mi/basics.c",line="13"@} | |
594fe323 | 22418 | (gdb) |
922fbb7b AC |
22419 | -exec-continue |
22420 | ^running | |
0869d01b NR |
22421 | (gdb) |
22422 | *stopped,reason="watchpoint-scope",wpnum="5", | |
922fbb7b AC |
22423 | frame=@{func="callee3",args=[@{name="strarg", |
22424 | value="0x11940 \"A string argument.\""@}], | |
76ff342d DJ |
22425 | file="../../../devo/gdb/testsuite/gdb.mi/basics.c", |
22426 | fullname="/home/foo/bar/devo/gdb/testsuite/gdb.mi/basics.c",line="18"@} | |
594fe323 | 22427 | (gdb) |
922fbb7b AC |
22428 | @end smallexample |
22429 | ||
22430 | Listing breakpoints and watchpoints, at different points in the program | |
22431 | execution. Note that once the watchpoint goes out of scope, it is | |
22432 | deleted. | |
22433 | ||
22434 | @smallexample | |
594fe323 | 22435 | (gdb) |
922fbb7b AC |
22436 | -break-watch C |
22437 | ^done,wpt=@{number="2",exp="C"@} | |
594fe323 | 22438 | (gdb) |
922fbb7b AC |
22439 | -break-list |
22440 | ^done,BreakpointTable=@{nr_rows="2",nr_cols="6", | |
22441 | hdr=[@{width="3",alignment="-1",col_name="number",colhdr="Num"@}, | |
22442 | @{width="14",alignment="-1",col_name="type",colhdr="Type"@}, | |
22443 | @{width="4",alignment="-1",col_name="disp",colhdr="Disp"@}, | |
22444 | @{width="3",alignment="-1",col_name="enabled",colhdr="Enb"@}, | |
22445 | @{width="10",alignment="-1",col_name="addr",colhdr="Address"@}, | |
22446 | @{width="40",alignment="2",col_name="what",colhdr="What"@}], | |
22447 | body=[bkpt=@{number="1",type="breakpoint",disp="keep",enabled="y", | |
22448 | addr="0x00010734",func="callee4", | |
948d5102 NR |
22449 | file="../../../devo/gdb/testsuite/gdb.mi/basics.c", |
22450 | fullname="/home/foo/devo/gdb/testsuite/gdb.mi/basics.c"line="8",times="1"@}, | |
922fbb7b AC |
22451 | bkpt=@{number="2",type="watchpoint",disp="keep", |
22452 | enabled="y",addr="",what="C",times="0"@}]@} | |
594fe323 | 22453 | (gdb) |
922fbb7b AC |
22454 | -exec-continue |
22455 | ^running | |
0869d01b NR |
22456 | (gdb) |
22457 | *stopped,reason="watchpoint-trigger",wpt=@{number="2",exp="C"@}, | |
922fbb7b AC |
22458 | value=@{old="-276895068",new="3"@}, |
22459 | frame=@{func="callee4",args=[], | |
76ff342d DJ |
22460 | file="../../../devo/gdb/testsuite/gdb.mi/basics.c", |
22461 | fullname="/home/foo/bar/devo/gdb/testsuite/gdb.mi/basics.c",line="13"@} | |
594fe323 | 22462 | (gdb) |
922fbb7b AC |
22463 | -break-list |
22464 | ^done,BreakpointTable=@{nr_rows="2",nr_cols="6", | |
22465 | hdr=[@{width="3",alignment="-1",col_name="number",colhdr="Num"@}, | |
22466 | @{width="14",alignment="-1",col_name="type",colhdr="Type"@}, | |
22467 | @{width="4",alignment="-1",col_name="disp",colhdr="Disp"@}, | |
22468 | @{width="3",alignment="-1",col_name="enabled",colhdr="Enb"@}, | |
22469 | @{width="10",alignment="-1",col_name="addr",colhdr="Address"@}, | |
22470 | @{width="40",alignment="2",col_name="what",colhdr="What"@}], | |
22471 | body=[bkpt=@{number="1",type="breakpoint",disp="keep",enabled="y", | |
22472 | addr="0x00010734",func="callee4", | |
948d5102 NR |
22473 | file="../../../devo/gdb/testsuite/gdb.mi/basics.c", |
22474 | fullname="/home/foo/devo/gdb/testsuite/gdb.mi/basics.c",line="8",times="1"@}, | |
922fbb7b AC |
22475 | bkpt=@{number="2",type="watchpoint",disp="keep", |
22476 | enabled="y",addr="",what="C",times="-5"@}]@} | |
594fe323 | 22477 | (gdb) |
922fbb7b AC |
22478 | -exec-continue |
22479 | ^running | |
22480 | ^done,reason="watchpoint-scope",wpnum="2", | |
22481 | frame=@{func="callee3",args=[@{name="strarg", | |
22482 | value="0x11940 \"A string argument.\""@}], | |
76ff342d DJ |
22483 | file="../../../devo/gdb/testsuite/gdb.mi/basics.c", |
22484 | fullname="/home/foo/bar/devo/gdb/testsuite/gdb.mi/basics.c",line="18"@} | |
594fe323 | 22485 | (gdb) |
922fbb7b AC |
22486 | -break-list |
22487 | ^done,BreakpointTable=@{nr_rows="1",nr_cols="6", | |
22488 | hdr=[@{width="3",alignment="-1",col_name="number",colhdr="Num"@}, | |
22489 | @{width="14",alignment="-1",col_name="type",colhdr="Type"@}, | |
22490 | @{width="4",alignment="-1",col_name="disp",colhdr="Disp"@}, | |
22491 | @{width="3",alignment="-1",col_name="enabled",colhdr="Enb"@}, | |
22492 | @{width="10",alignment="-1",col_name="addr",colhdr="Address"@}, | |
22493 | @{width="40",alignment="2",col_name="what",colhdr="What"@}], | |
22494 | body=[bkpt=@{number="1",type="breakpoint",disp="keep",enabled="y", | |
22495 | addr="0x00010734",func="callee4", | |
948d5102 NR |
22496 | file="../../../devo/gdb/testsuite/gdb.mi/basics.c", |
22497 | fullname="/home/foo/devo/gdb/testsuite/gdb.mi/basics.c",line="8", | |
22498 | times="1"@}]@} | |
594fe323 | 22499 | (gdb) |
922fbb7b AC |
22500 | @end smallexample |
22501 | ||
22502 | @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% | |
a2c02241 NR |
22503 | @node GDB/MI Program Context |
22504 | @section @sc{gdb/mi} Program Context | |
922fbb7b | 22505 | |
a2c02241 NR |
22506 | @subheading The @code{-exec-arguments} Command |
22507 | @findex -exec-arguments | |
922fbb7b | 22508 | |
922fbb7b AC |
22509 | |
22510 | @subsubheading Synopsis | |
22511 | ||
22512 | @smallexample | |
a2c02241 | 22513 | -exec-arguments @var{args} |
922fbb7b AC |
22514 | @end smallexample |
22515 | ||
a2c02241 NR |
22516 | Set the inferior program arguments, to be used in the next |
22517 | @samp{-exec-run}. | |
922fbb7b | 22518 | |
a2c02241 | 22519 | @subsubheading @value{GDBN} Command |
922fbb7b | 22520 | |
a2c02241 | 22521 | The corresponding @value{GDBN} command is @samp{set args}. |
922fbb7b | 22522 | |
a2c02241 | 22523 | @subsubheading Example |
922fbb7b | 22524 | |
fbc5282e MK |
22525 | @smallexample |
22526 | (gdb) | |
22527 | -exec-arguments -v word | |
22528 | ^done | |
22529 | (gdb) | |
22530 | @end smallexample | |
922fbb7b | 22531 | |
a2c02241 | 22532 | |
9901a55b | 22533 | @ignore |
a2c02241 NR |
22534 | @subheading The @code{-exec-show-arguments} Command |
22535 | @findex -exec-show-arguments | |
22536 | ||
22537 | @subsubheading Synopsis | |
22538 | ||
22539 | @smallexample | |
22540 | -exec-show-arguments | |
22541 | @end smallexample | |
22542 | ||
22543 | Print the arguments of the program. | |
922fbb7b AC |
22544 | |
22545 | @subsubheading @value{GDBN} Command | |
22546 | ||
a2c02241 | 22547 | The corresponding @value{GDBN} command is @samp{show args}. |
922fbb7b AC |
22548 | |
22549 | @subsubheading Example | |
a2c02241 | 22550 | N.A. |
9901a55b | 22551 | @end ignore |
922fbb7b | 22552 | |
922fbb7b | 22553 | |
a2c02241 NR |
22554 | @subheading The @code{-environment-cd} Command |
22555 | @findex -environment-cd | |
922fbb7b | 22556 | |
a2c02241 | 22557 | @subsubheading Synopsis |
922fbb7b AC |
22558 | |
22559 | @smallexample | |
a2c02241 | 22560 | -environment-cd @var{pathdir} |
922fbb7b AC |
22561 | @end smallexample |
22562 | ||
a2c02241 | 22563 | Set @value{GDBN}'s working directory. |
922fbb7b | 22564 | |
a2c02241 | 22565 | @subsubheading @value{GDBN} Command |
922fbb7b | 22566 | |
a2c02241 NR |
22567 | The corresponding @value{GDBN} command is @samp{cd}. |
22568 | ||
22569 | @subsubheading Example | |
922fbb7b AC |
22570 | |
22571 | @smallexample | |
594fe323 | 22572 | (gdb) |
a2c02241 NR |
22573 | -environment-cd /kwikemart/marge/ezannoni/flathead-dev/devo/gdb |
22574 | ^done | |
594fe323 | 22575 | (gdb) |
922fbb7b AC |
22576 | @end smallexample |
22577 | ||
22578 | ||
a2c02241 NR |
22579 | @subheading The @code{-environment-directory} Command |
22580 | @findex -environment-directory | |
922fbb7b AC |
22581 | |
22582 | @subsubheading Synopsis | |
22583 | ||
22584 | @smallexample | |
a2c02241 | 22585 | -environment-directory [ -r ] [ @var{pathdir} ]+ |
922fbb7b AC |
22586 | @end smallexample |
22587 | ||
a2c02241 NR |
22588 | Add directories @var{pathdir} to beginning of search path for source files. |
22589 | If the @samp{-r} option is used, the search path is reset to the default | |
22590 | search path. If directories @var{pathdir} are supplied in addition to the | |
22591 | @samp{-r} option, the search path is first reset and then addition | |
22592 | occurs as normal. | |
22593 | Multiple directories may be specified, separated by blanks. Specifying | |
22594 | multiple directories in a single command | |
22595 | results in the directories added to the beginning of the | |
22596 | search path in the same order they were presented in the command. | |
22597 | If blanks are needed as | |
22598 | part of a directory name, double-quotes should be used around | |
22599 | the name. In the command output, the path will show up separated | |
d3e8051b | 22600 | by the system directory-separator character. The directory-separator |
a2c02241 NR |
22601 | character must not be used |
22602 | in any directory name. | |
22603 | If no directories are specified, the current search path is displayed. | |
922fbb7b AC |
22604 | |
22605 | @subsubheading @value{GDBN} Command | |
22606 | ||
a2c02241 | 22607 | The corresponding @value{GDBN} command is @samp{dir}. |
922fbb7b AC |
22608 | |
22609 | @subsubheading Example | |
22610 | ||
922fbb7b | 22611 | @smallexample |
594fe323 | 22612 | (gdb) |
a2c02241 NR |
22613 | -environment-directory /kwikemart/marge/ezannoni/flathead-dev/devo/gdb |
22614 | ^done,source-path="/kwikemart/marge/ezannoni/flathead-dev/devo/gdb:$cdir:$cwd" | |
594fe323 | 22615 | (gdb) |
a2c02241 NR |
22616 | -environment-directory "" |
22617 | ^done,source-path="/kwikemart/marge/ezannoni/flathead-dev/devo/gdb:$cdir:$cwd" | |
594fe323 | 22618 | (gdb) |
a2c02241 NR |
22619 | -environment-directory -r /home/jjohnstn/src/gdb /usr/src |
22620 | ^done,source-path="/home/jjohnstn/src/gdb:/usr/src:$cdir:$cwd" | |
594fe323 | 22621 | (gdb) |
a2c02241 NR |
22622 | -environment-directory -r |
22623 | ^done,source-path="$cdir:$cwd" | |
594fe323 | 22624 | (gdb) |
922fbb7b AC |
22625 | @end smallexample |
22626 | ||
22627 | ||
a2c02241 NR |
22628 | @subheading The @code{-environment-path} Command |
22629 | @findex -environment-path | |
922fbb7b AC |
22630 | |
22631 | @subsubheading Synopsis | |
22632 | ||
22633 | @smallexample | |
a2c02241 | 22634 | -environment-path [ -r ] [ @var{pathdir} ]+ |
922fbb7b AC |
22635 | @end smallexample |
22636 | ||
a2c02241 NR |
22637 | Add directories @var{pathdir} to beginning of search path for object files. |
22638 | If the @samp{-r} option is used, the search path is reset to the original | |
22639 | search path that existed at gdb start-up. If directories @var{pathdir} are | |
22640 | supplied in addition to the | |
22641 | @samp{-r} option, the search path is first reset and then addition | |
22642 | occurs as normal. | |
22643 | Multiple directories may be specified, separated by blanks. Specifying | |
22644 | multiple directories in a single command | |
22645 | results in the directories added to the beginning of the | |
22646 | search path in the same order they were presented in the command. | |
22647 | If blanks are needed as | |
22648 | part of a directory name, double-quotes should be used around | |
22649 | the name. In the command output, the path will show up separated | |
d3e8051b | 22650 | by the system directory-separator character. The directory-separator |
a2c02241 NR |
22651 | character must not be used |
22652 | in any directory name. | |
22653 | If no directories are specified, the current path is displayed. | |
22654 | ||
922fbb7b AC |
22655 | |
22656 | @subsubheading @value{GDBN} Command | |
22657 | ||
a2c02241 | 22658 | The corresponding @value{GDBN} command is @samp{path}. |
922fbb7b AC |
22659 | |
22660 | @subsubheading Example | |
22661 | ||
922fbb7b | 22662 | @smallexample |
594fe323 | 22663 | (gdb) |
a2c02241 NR |
22664 | -environment-path |
22665 | ^done,path="/usr/bin" | |
594fe323 | 22666 | (gdb) |
a2c02241 NR |
22667 | -environment-path /kwikemart/marge/ezannoni/flathead-dev/ppc-eabi/gdb /bin |
22668 | ^done,path="/kwikemart/marge/ezannoni/flathead-dev/ppc-eabi/gdb:/bin:/usr/bin" | |
594fe323 | 22669 | (gdb) |
a2c02241 NR |
22670 | -environment-path -r /usr/local/bin |
22671 | ^done,path="/usr/local/bin:/usr/bin" | |
594fe323 | 22672 | (gdb) |
922fbb7b AC |
22673 | @end smallexample |
22674 | ||
22675 | ||
a2c02241 NR |
22676 | @subheading The @code{-environment-pwd} Command |
22677 | @findex -environment-pwd | |
922fbb7b AC |
22678 | |
22679 | @subsubheading Synopsis | |
22680 | ||
22681 | @smallexample | |
a2c02241 | 22682 | -environment-pwd |
922fbb7b AC |
22683 | @end smallexample |
22684 | ||
a2c02241 | 22685 | Show the current working directory. |
922fbb7b | 22686 | |
79a6e687 | 22687 | @subsubheading @value{GDBN} Command |
922fbb7b | 22688 | |
a2c02241 | 22689 | The corresponding @value{GDBN} command is @samp{pwd}. |
922fbb7b AC |
22690 | |
22691 | @subsubheading Example | |
22692 | ||
922fbb7b | 22693 | @smallexample |
594fe323 | 22694 | (gdb) |
a2c02241 NR |
22695 | -environment-pwd |
22696 | ^done,cwd="/kwikemart/marge/ezannoni/flathead-dev/devo/gdb" | |
594fe323 | 22697 | (gdb) |
922fbb7b AC |
22698 | @end smallexample |
22699 | ||
a2c02241 NR |
22700 | @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% |
22701 | @node GDB/MI Thread Commands | |
22702 | @section @sc{gdb/mi} Thread Commands | |
22703 | ||
22704 | ||
22705 | @subheading The @code{-thread-info} Command | |
22706 | @findex -thread-info | |
922fbb7b AC |
22707 | |
22708 | @subsubheading Synopsis | |
22709 | ||
22710 | @smallexample | |
8e8901c5 | 22711 | -thread-info [ @var{thread-id} ] |
922fbb7b AC |
22712 | @end smallexample |
22713 | ||
8e8901c5 VP |
22714 | Reports information about either a specific thread, if |
22715 | the @var{thread-id} parameter is present, or about all | |
22716 | threads. When printing information about all threads, | |
22717 | also reports the current thread. | |
22718 | ||
79a6e687 | 22719 | @subsubheading @value{GDBN} Command |
922fbb7b | 22720 | |
8e8901c5 VP |
22721 | The @samp{info thread} command prints the same information |
22722 | about all threads. | |
922fbb7b AC |
22723 | |
22724 | @subsubheading Example | |
922fbb7b AC |
22725 | |
22726 | @smallexample | |
8e8901c5 VP |
22727 | -thread-info |
22728 | ^done,threads=[ | |
22729 | @{id="2",target-id="Thread 0xb7e14b90 (LWP 21257)", | |
c3b108f7 | 22730 | frame=@{level="0",addr="0xffffe410",func="__kernel_vsyscall",args=[]@},state="running"@}, |
8e8901c5 VP |
22731 | @{id="1",target-id="Thread 0xb7e156b0 (LWP 21254)", |
22732 | frame=@{level="0",addr="0x0804891f",func="foo",args=[@{name="i",value="10"@}], | |
c3b108f7 | 22733 | file="/tmp/a.c",fullname="/tmp/a.c",line="158"@},state="running"@}], |
8e8901c5 VP |
22734 | current-thread-id="1" |
22735 | (gdb) | |
922fbb7b AC |
22736 | @end smallexample |
22737 | ||
c3b108f7 VP |
22738 | The @samp{state} field may have the following values: |
22739 | ||
22740 | @table @code | |
22741 | @item stopped | |
22742 | The thread is stopped. Frame information is available for stopped | |
22743 | threads. | |
22744 | ||
22745 | @item running | |
22746 | The thread is running. There's no frame information for running | |
22747 | threads. | |
22748 | ||
22749 | @end table | |
22750 | ||
a2c02241 NR |
22751 | @subheading The @code{-thread-list-ids} Command |
22752 | @findex -thread-list-ids | |
922fbb7b | 22753 | |
a2c02241 | 22754 | @subsubheading Synopsis |
922fbb7b | 22755 | |
a2c02241 NR |
22756 | @smallexample |
22757 | -thread-list-ids | |
22758 | @end smallexample | |
922fbb7b | 22759 | |
a2c02241 NR |
22760 | Produces a list of the currently known @value{GDBN} thread ids. At the |
22761 | end of the list it also prints the total number of such threads. | |
922fbb7b | 22762 | |
c3b108f7 VP |
22763 | This command is retained for historical reasons, the |
22764 | @code{-thread-info} command should be used instead. | |
22765 | ||
922fbb7b AC |
22766 | @subsubheading @value{GDBN} Command |
22767 | ||
a2c02241 | 22768 | Part of @samp{info threads} supplies the same information. |
922fbb7b AC |
22769 | |
22770 | @subsubheading Example | |
22771 | ||
922fbb7b | 22772 | @smallexample |
594fe323 | 22773 | (gdb) |
a2c02241 NR |
22774 | -thread-list-ids |
22775 | ^done,thread-ids=@{thread-id="3",thread-id="2",thread-id="1"@}, | |
592375cd | 22776 | current-thread-id="1",number-of-threads="3" |
594fe323 | 22777 | (gdb) |
922fbb7b AC |
22778 | @end smallexample |
22779 | ||
a2c02241 NR |
22780 | |
22781 | @subheading The @code{-thread-select} Command | |
22782 | @findex -thread-select | |
922fbb7b AC |
22783 | |
22784 | @subsubheading Synopsis | |
22785 | ||
22786 | @smallexample | |
a2c02241 | 22787 | -thread-select @var{threadnum} |
922fbb7b AC |
22788 | @end smallexample |
22789 | ||
a2c02241 NR |
22790 | Make @var{threadnum} the current thread. It prints the number of the new |
22791 | current thread, and the topmost frame for that thread. | |
922fbb7b | 22792 | |
c3b108f7 VP |
22793 | This command is deprecated in favor of explicitly using the |
22794 | @samp{--thread} option to each command. | |
22795 | ||
922fbb7b AC |
22796 | @subsubheading @value{GDBN} Command |
22797 | ||
a2c02241 | 22798 | The corresponding @value{GDBN} command is @samp{thread}. |
922fbb7b AC |
22799 | |
22800 | @subsubheading Example | |
922fbb7b AC |
22801 | |
22802 | @smallexample | |
594fe323 | 22803 | (gdb) |
a2c02241 NR |
22804 | -exec-next |
22805 | ^running | |
594fe323 | 22806 | (gdb) |
a2c02241 NR |
22807 | *stopped,reason="end-stepping-range",thread-id="2",line="187", |
22808 | file="../../../devo/gdb/testsuite/gdb.threads/linux-dp.c" | |
594fe323 | 22809 | (gdb) |
a2c02241 NR |
22810 | -thread-list-ids |
22811 | ^done, | |
22812 | thread-ids=@{thread-id="3",thread-id="2",thread-id="1"@}, | |
22813 | number-of-threads="3" | |
594fe323 | 22814 | (gdb) |
a2c02241 NR |
22815 | -thread-select 3 |
22816 | ^done,new-thread-id="3", | |
22817 | frame=@{level="0",func="vprintf", | |
22818 | args=[@{name="format",value="0x8048e9c \"%*s%c %d %c\\n\""@}, | |
22819 | @{name="arg",value="0x2"@}],file="vprintf.c",line="31"@} | |
594fe323 | 22820 | (gdb) |
922fbb7b AC |
22821 | @end smallexample |
22822 | ||
a2c02241 NR |
22823 | @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% |
22824 | @node GDB/MI Program Execution | |
22825 | @section @sc{gdb/mi} Program Execution | |
922fbb7b | 22826 | |
ef21caaf | 22827 | These are the asynchronous commands which generate the out-of-band |
3f94c067 | 22828 | record @samp{*stopped}. Currently @value{GDBN} only really executes |
ef21caaf NR |
22829 | asynchronously with remote targets and this interaction is mimicked in |
22830 | other cases. | |
922fbb7b | 22831 | |
922fbb7b AC |
22832 | @subheading The @code{-exec-continue} Command |
22833 | @findex -exec-continue | |
22834 | ||
22835 | @subsubheading Synopsis | |
22836 | ||
22837 | @smallexample | |
c3b108f7 | 22838 | -exec-continue [--all|--thread-group N] |
922fbb7b AC |
22839 | @end smallexample |
22840 | ||
ef21caaf | 22841 | Resumes the execution of the inferior program until a breakpoint is |
c3b108f7 VP |
22842 | encountered, or until the inferior exits. In all-stop mode |
22843 | (@pxref{All-Stop Mode}), may resume only one thread, or all threads, | |
22844 | depending on the value of the @samp{scheduler-locking} variable. In | |
22845 | non-stop mode (@pxref{Non-Stop Mode}), if the @samp{--all} is not | |
22846 | specified, only the thread specified with the @samp{--thread} option | |
22847 | (or current thread, if no @samp{--thread} is provided) is resumed. If | |
22848 | @samp{--all} is specified, all threads will be resumed. The | |
22849 | @samp{--all} option is ignored in all-stop mode. If the | |
22850 | @samp{--thread-group} options is specified, then all threads in that | |
22851 | thread group are resumed. | |
922fbb7b AC |
22852 | |
22853 | @subsubheading @value{GDBN} Command | |
22854 | ||
22855 | The corresponding @value{GDBN} corresponding is @samp{continue}. | |
22856 | ||
22857 | @subsubheading Example | |
22858 | ||
22859 | @smallexample | |
22860 | -exec-continue | |
22861 | ^running | |
594fe323 | 22862 | (gdb) |
922fbb7b | 22863 | @@Hello world |
a47ec5fe AR |
22864 | *stopped,reason="breakpoint-hit",disp="keep",bkptno="2",frame=@{ |
22865 | func="foo",args=[],file="hello.c",fullname="/home/foo/bar/hello.c", | |
22866 | line="13"@} | |
594fe323 | 22867 | (gdb) |
922fbb7b AC |
22868 | @end smallexample |
22869 | ||
22870 | ||
22871 | @subheading The @code{-exec-finish} Command | |
22872 | @findex -exec-finish | |
22873 | ||
22874 | @subsubheading Synopsis | |
22875 | ||
22876 | @smallexample | |
22877 | -exec-finish | |
22878 | @end smallexample | |
22879 | ||
ef21caaf NR |
22880 | Resumes the execution of the inferior program until the current |
22881 | function is exited. Displays the results returned by the function. | |
922fbb7b AC |
22882 | |
22883 | @subsubheading @value{GDBN} Command | |
22884 | ||
22885 | The corresponding @value{GDBN} command is @samp{finish}. | |
22886 | ||
22887 | @subsubheading Example | |
22888 | ||
22889 | Function returning @code{void}. | |
22890 | ||
22891 | @smallexample | |
22892 | -exec-finish | |
22893 | ^running | |
594fe323 | 22894 | (gdb) |
922fbb7b AC |
22895 | @@hello from foo |
22896 | *stopped,reason="function-finished",frame=@{func="main",args=[], | |
948d5102 | 22897 | file="hello.c",fullname="/home/foo/bar/hello.c",line="7"@} |
594fe323 | 22898 | (gdb) |
922fbb7b AC |
22899 | @end smallexample |
22900 | ||
22901 | Function returning other than @code{void}. The name of the internal | |
22902 | @value{GDBN} variable storing the result is printed, together with the | |
22903 | value itself. | |
22904 | ||
22905 | @smallexample | |
22906 | -exec-finish | |
22907 | ^running | |
594fe323 | 22908 | (gdb) |
922fbb7b AC |
22909 | *stopped,reason="function-finished",frame=@{addr="0x000107b0",func="foo", |
22910 | args=[@{name="a",value="1"],@{name="b",value="9"@}@}, | |
948d5102 | 22911 | file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@}, |
922fbb7b | 22912 | gdb-result-var="$1",return-value="0" |
594fe323 | 22913 | (gdb) |
922fbb7b AC |
22914 | @end smallexample |
22915 | ||
22916 | ||
22917 | @subheading The @code{-exec-interrupt} Command | |
22918 | @findex -exec-interrupt | |
22919 | ||
22920 | @subsubheading Synopsis | |
22921 | ||
22922 | @smallexample | |
c3b108f7 | 22923 | -exec-interrupt [--all|--thread-group N] |
922fbb7b AC |
22924 | @end smallexample |
22925 | ||
ef21caaf NR |
22926 | Interrupts the background execution of the target. Note how the token |
22927 | associated with the stop message is the one for the execution command | |
22928 | that has been interrupted. The token for the interrupt itself only | |
22929 | appears in the @samp{^done} output. If the user is trying to | |
922fbb7b AC |
22930 | interrupt a non-running program, an error message will be printed. |
22931 | ||
c3b108f7 VP |
22932 | Note that when asynchronous execution is enabled, this command is |
22933 | asynchronous just like other execution commands. That is, first the | |
22934 | @samp{^done} response will be printed, and the target stop will be | |
22935 | reported after that using the @samp{*stopped} notification. | |
22936 | ||
22937 | In non-stop mode, only the context thread is interrupted by default. | |
22938 | All threads will be interrupted if the @samp{--all} option is | |
22939 | specified. If the @samp{--thread-group} option is specified, all | |
22940 | threads in that group will be interrupted. | |
22941 | ||
922fbb7b AC |
22942 | @subsubheading @value{GDBN} Command |
22943 | ||
22944 | The corresponding @value{GDBN} command is @samp{interrupt}. | |
22945 | ||
22946 | @subsubheading Example | |
22947 | ||
22948 | @smallexample | |
594fe323 | 22949 | (gdb) |
922fbb7b AC |
22950 | 111-exec-continue |
22951 | 111^running | |
22952 | ||
594fe323 | 22953 | (gdb) |
922fbb7b AC |
22954 | 222-exec-interrupt |
22955 | 222^done | |
594fe323 | 22956 | (gdb) |
922fbb7b | 22957 | 111*stopped,signal-name="SIGINT",signal-meaning="Interrupt", |
76ff342d | 22958 | frame=@{addr="0x00010140",func="foo",args=[],file="try.c", |
948d5102 | 22959 | fullname="/home/foo/bar/try.c",line="13"@} |
594fe323 | 22960 | (gdb) |
922fbb7b | 22961 | |
594fe323 | 22962 | (gdb) |
922fbb7b AC |
22963 | -exec-interrupt |
22964 | ^error,msg="mi_cmd_exec_interrupt: Inferior not executing." | |
594fe323 | 22965 | (gdb) |
922fbb7b AC |
22966 | @end smallexample |
22967 | ||
83eba9b7 VP |
22968 | @subheading The @code{-exec-jump} Command |
22969 | @findex -exec-jump | |
22970 | ||
22971 | @subsubheading Synopsis | |
22972 | ||
22973 | @smallexample | |
22974 | -exec-jump @var{location} | |
22975 | @end smallexample | |
22976 | ||
22977 | Resumes execution of the inferior program at the location specified by | |
22978 | parameter. @xref{Specify Location}, for a description of the | |
22979 | different forms of @var{location}. | |
22980 | ||
22981 | @subsubheading @value{GDBN} Command | |
22982 | ||
22983 | The corresponding @value{GDBN} command is @samp{jump}. | |
22984 | ||
22985 | @subsubheading Example | |
22986 | ||
22987 | @smallexample | |
22988 | -exec-jump foo.c:10 | |
22989 | *running,thread-id="all" | |
22990 | ^running | |
22991 | @end smallexample | |
22992 | ||
922fbb7b AC |
22993 | |
22994 | @subheading The @code{-exec-next} Command | |
22995 | @findex -exec-next | |
22996 | ||
22997 | @subsubheading Synopsis | |
22998 | ||
22999 | @smallexample | |
23000 | -exec-next | |
23001 | @end smallexample | |
23002 | ||
ef21caaf NR |
23003 | Resumes execution of the inferior program, stopping when the beginning |
23004 | of the next source line is reached. | |
922fbb7b AC |
23005 | |
23006 | @subsubheading @value{GDBN} Command | |
23007 | ||
23008 | The corresponding @value{GDBN} command is @samp{next}. | |
23009 | ||
23010 | @subsubheading Example | |
23011 | ||
23012 | @smallexample | |
23013 | -exec-next | |
23014 | ^running | |
594fe323 | 23015 | (gdb) |
922fbb7b | 23016 | *stopped,reason="end-stepping-range",line="8",file="hello.c" |
594fe323 | 23017 | (gdb) |
922fbb7b AC |
23018 | @end smallexample |
23019 | ||
23020 | ||
23021 | @subheading The @code{-exec-next-instruction} Command | |
23022 | @findex -exec-next-instruction | |
23023 | ||
23024 | @subsubheading Synopsis | |
23025 | ||
23026 | @smallexample | |
23027 | -exec-next-instruction | |
23028 | @end smallexample | |
23029 | ||
ef21caaf NR |
23030 | Executes one machine instruction. If the instruction is a function |
23031 | call, continues until the function returns. If the program stops at an | |
23032 | instruction in the middle of a source line, the address will be | |
23033 | printed as well. | |
922fbb7b AC |
23034 | |
23035 | @subsubheading @value{GDBN} Command | |
23036 | ||
23037 | The corresponding @value{GDBN} command is @samp{nexti}. | |
23038 | ||
23039 | @subsubheading Example | |
23040 | ||
23041 | @smallexample | |
594fe323 | 23042 | (gdb) |
922fbb7b AC |
23043 | -exec-next-instruction |
23044 | ^running | |
23045 | ||
594fe323 | 23046 | (gdb) |
922fbb7b AC |
23047 | *stopped,reason="end-stepping-range", |
23048 | addr="0x000100d4",line="5",file="hello.c" | |
594fe323 | 23049 | (gdb) |
922fbb7b AC |
23050 | @end smallexample |
23051 | ||
23052 | ||
23053 | @subheading The @code{-exec-return} Command | |
23054 | @findex -exec-return | |
23055 | ||
23056 | @subsubheading Synopsis | |
23057 | ||
23058 | @smallexample | |
23059 | -exec-return | |
23060 | @end smallexample | |
23061 | ||
23062 | Makes current function return immediately. Doesn't execute the inferior. | |
23063 | Displays the new current frame. | |
23064 | ||
23065 | @subsubheading @value{GDBN} Command | |
23066 | ||
23067 | The corresponding @value{GDBN} command is @samp{return}. | |
23068 | ||
23069 | @subsubheading Example | |
23070 | ||
23071 | @smallexample | |
594fe323 | 23072 | (gdb) |
922fbb7b AC |
23073 | 200-break-insert callee4 |
23074 | 200^done,bkpt=@{number="1",addr="0x00010734", | |
23075 | file="../../../devo/gdb/testsuite/gdb.mi/basics.c",line="8"@} | |
594fe323 | 23076 | (gdb) |
922fbb7b AC |
23077 | 000-exec-run |
23078 | 000^running | |
594fe323 | 23079 | (gdb) |
a47ec5fe | 23080 | 000*stopped,reason="breakpoint-hit",disp="keep",bkptno="1", |
922fbb7b | 23081 | frame=@{func="callee4",args=[], |
76ff342d DJ |
23082 | file="../../../devo/gdb/testsuite/gdb.mi/basics.c", |
23083 | fullname="/home/foo/bar/devo/gdb/testsuite/gdb.mi/basics.c",line="8"@} | |
594fe323 | 23084 | (gdb) |
922fbb7b AC |
23085 | 205-break-delete |
23086 | 205^done | |
594fe323 | 23087 | (gdb) |
922fbb7b AC |
23088 | 111-exec-return |
23089 | 111^done,frame=@{level="0",func="callee3", | |
23090 | args=[@{name="strarg", | |
23091 | value="0x11940 \"A string argument.\""@}], | |
76ff342d DJ |
23092 | file="../../../devo/gdb/testsuite/gdb.mi/basics.c", |
23093 | fullname="/home/foo/bar/devo/gdb/testsuite/gdb.mi/basics.c",line="18"@} | |
594fe323 | 23094 | (gdb) |
922fbb7b AC |
23095 | @end smallexample |
23096 | ||
23097 | ||
23098 | @subheading The @code{-exec-run} Command | |
23099 | @findex -exec-run | |
23100 | ||
23101 | @subsubheading Synopsis | |
23102 | ||
23103 | @smallexample | |
23104 | -exec-run | |
23105 | @end smallexample | |
23106 | ||
ef21caaf NR |
23107 | Starts execution of the inferior from the beginning. The inferior |
23108 | executes until either a breakpoint is encountered or the program | |
23109 | exits. In the latter case the output will include an exit code, if | |
23110 | the program has exited exceptionally. | |
922fbb7b AC |
23111 | |
23112 | @subsubheading @value{GDBN} Command | |
23113 | ||
23114 | The corresponding @value{GDBN} command is @samp{run}. | |
23115 | ||
ef21caaf | 23116 | @subsubheading Examples |
922fbb7b AC |
23117 | |
23118 | @smallexample | |
594fe323 | 23119 | (gdb) |
922fbb7b AC |
23120 | -break-insert main |
23121 | ^done,bkpt=@{number="1",addr="0x0001072c",file="recursive2.c",line="4"@} | |
594fe323 | 23122 | (gdb) |
922fbb7b AC |
23123 | -exec-run |
23124 | ^running | |
594fe323 | 23125 | (gdb) |
a47ec5fe | 23126 | *stopped,reason="breakpoint-hit",disp="keep",bkptno="1", |
76ff342d | 23127 | frame=@{func="main",args=[],file="recursive2.c", |
948d5102 | 23128 | fullname="/home/foo/bar/recursive2.c",line="4"@} |
594fe323 | 23129 | (gdb) |
922fbb7b AC |
23130 | @end smallexample |
23131 | ||
ef21caaf NR |
23132 | @noindent |
23133 | Program exited normally: | |
23134 | ||
23135 | @smallexample | |
594fe323 | 23136 | (gdb) |
ef21caaf NR |
23137 | -exec-run |
23138 | ^running | |
594fe323 | 23139 | (gdb) |
ef21caaf NR |
23140 | x = 55 |
23141 | *stopped,reason="exited-normally" | |
594fe323 | 23142 | (gdb) |
ef21caaf NR |
23143 | @end smallexample |
23144 | ||
23145 | @noindent | |
23146 | Program exited exceptionally: | |
23147 | ||
23148 | @smallexample | |
594fe323 | 23149 | (gdb) |
ef21caaf NR |
23150 | -exec-run |
23151 | ^running | |
594fe323 | 23152 | (gdb) |
ef21caaf NR |
23153 | x = 55 |
23154 | *stopped,reason="exited",exit-code="01" | |
594fe323 | 23155 | (gdb) |
ef21caaf NR |
23156 | @end smallexample |
23157 | ||
23158 | Another way the program can terminate is if it receives a signal such as | |
23159 | @code{SIGINT}. In this case, @sc{gdb/mi} displays this: | |
23160 | ||
23161 | @smallexample | |
594fe323 | 23162 | (gdb) |
ef21caaf NR |
23163 | *stopped,reason="exited-signalled",signal-name="SIGINT", |
23164 | signal-meaning="Interrupt" | |
23165 | @end smallexample | |
23166 | ||
922fbb7b | 23167 | |
a2c02241 NR |
23168 | @c @subheading -exec-signal |
23169 | ||
23170 | ||
23171 | @subheading The @code{-exec-step} Command | |
23172 | @findex -exec-step | |
922fbb7b AC |
23173 | |
23174 | @subsubheading Synopsis | |
23175 | ||
23176 | @smallexample | |
a2c02241 | 23177 | -exec-step |
922fbb7b AC |
23178 | @end smallexample |
23179 | ||
a2c02241 NR |
23180 | Resumes execution of the inferior program, stopping when the beginning |
23181 | of the next source line is reached, if the next source line is not a | |
23182 | function call. If it is, stop at the first instruction of the called | |
23183 | function. | |
922fbb7b AC |
23184 | |
23185 | @subsubheading @value{GDBN} Command | |
23186 | ||
a2c02241 | 23187 | The corresponding @value{GDBN} command is @samp{step}. |
922fbb7b AC |
23188 | |
23189 | @subsubheading Example | |
23190 | ||
23191 | Stepping into a function: | |
23192 | ||
23193 | @smallexample | |
23194 | -exec-step | |
23195 | ^running | |
594fe323 | 23196 | (gdb) |
922fbb7b AC |
23197 | *stopped,reason="end-stepping-range", |
23198 | frame=@{func="foo",args=[@{name="a",value="10"@}, | |
76ff342d | 23199 | @{name="b",value="0"@}],file="recursive2.c", |
948d5102 | 23200 | fullname="/home/foo/bar/recursive2.c",line="11"@} |
594fe323 | 23201 | (gdb) |
922fbb7b AC |
23202 | @end smallexample |
23203 | ||
23204 | Regular stepping: | |
23205 | ||
23206 | @smallexample | |
23207 | -exec-step | |
23208 | ^running | |
594fe323 | 23209 | (gdb) |
922fbb7b | 23210 | *stopped,reason="end-stepping-range",line="14",file="recursive2.c" |
594fe323 | 23211 | (gdb) |
922fbb7b AC |
23212 | @end smallexample |
23213 | ||
23214 | ||
23215 | @subheading The @code{-exec-step-instruction} Command | |
23216 | @findex -exec-step-instruction | |
23217 | ||
23218 | @subsubheading Synopsis | |
23219 | ||
23220 | @smallexample | |
23221 | -exec-step-instruction | |
23222 | @end smallexample | |
23223 | ||
ef21caaf NR |
23224 | Resumes the inferior which executes one machine instruction. The |
23225 | output, once @value{GDBN} has stopped, will vary depending on whether | |
23226 | we have stopped in the middle of a source line or not. In the former | |
23227 | case, the address at which the program stopped will be printed as | |
922fbb7b AC |
23228 | well. |
23229 | ||
23230 | @subsubheading @value{GDBN} Command | |
23231 | ||
23232 | The corresponding @value{GDBN} command is @samp{stepi}. | |
23233 | ||
23234 | @subsubheading Example | |
23235 | ||
23236 | @smallexample | |
594fe323 | 23237 | (gdb) |
922fbb7b AC |
23238 | -exec-step-instruction |
23239 | ^running | |
23240 | ||
594fe323 | 23241 | (gdb) |
922fbb7b | 23242 | *stopped,reason="end-stepping-range", |
76ff342d | 23243 | frame=@{func="foo",args=[],file="try.c", |
948d5102 | 23244 | fullname="/home/foo/bar/try.c",line="10"@} |
594fe323 | 23245 | (gdb) |
922fbb7b AC |
23246 | -exec-step-instruction |
23247 | ^running | |
23248 | ||
594fe323 | 23249 | (gdb) |
922fbb7b | 23250 | *stopped,reason="end-stepping-range", |
76ff342d | 23251 | frame=@{addr="0x000100f4",func="foo",args=[],file="try.c", |
948d5102 | 23252 | fullname="/home/foo/bar/try.c",line="10"@} |
594fe323 | 23253 | (gdb) |
922fbb7b AC |
23254 | @end smallexample |
23255 | ||
23256 | ||
23257 | @subheading The @code{-exec-until} Command | |
23258 | @findex -exec-until | |
23259 | ||
23260 | @subsubheading Synopsis | |
23261 | ||
23262 | @smallexample | |
23263 | -exec-until [ @var{location} ] | |
23264 | @end smallexample | |
23265 | ||
ef21caaf NR |
23266 | Executes the inferior until the @var{location} specified in the |
23267 | argument is reached. If there is no argument, the inferior executes | |
23268 | until a source line greater than the current one is reached. The | |
23269 | reason for stopping in this case will be @samp{location-reached}. | |
922fbb7b AC |
23270 | |
23271 | @subsubheading @value{GDBN} Command | |
23272 | ||
23273 | The corresponding @value{GDBN} command is @samp{until}. | |
23274 | ||
23275 | @subsubheading Example | |
23276 | ||
23277 | @smallexample | |
594fe323 | 23278 | (gdb) |
922fbb7b AC |
23279 | -exec-until recursive2.c:6 |
23280 | ^running | |
594fe323 | 23281 | (gdb) |
922fbb7b AC |
23282 | x = 55 |
23283 | *stopped,reason="location-reached",frame=@{func="main",args=[], | |
948d5102 | 23284 | file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="6"@} |
594fe323 | 23285 | (gdb) |
922fbb7b AC |
23286 | @end smallexample |
23287 | ||
23288 | @ignore | |
23289 | @subheading -file-clear | |
23290 | Is this going away???? | |
23291 | @end ignore | |
23292 | ||
351ff01a | 23293 | @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% |
a2c02241 NR |
23294 | @node GDB/MI Stack Manipulation |
23295 | @section @sc{gdb/mi} Stack Manipulation Commands | |
351ff01a | 23296 | |
922fbb7b | 23297 | |
a2c02241 NR |
23298 | @subheading The @code{-stack-info-frame} Command |
23299 | @findex -stack-info-frame | |
922fbb7b AC |
23300 | |
23301 | @subsubheading Synopsis | |
23302 | ||
23303 | @smallexample | |
a2c02241 | 23304 | -stack-info-frame |
922fbb7b AC |
23305 | @end smallexample |
23306 | ||
a2c02241 | 23307 | Get info on the selected frame. |
922fbb7b AC |
23308 | |
23309 | @subsubheading @value{GDBN} Command | |
23310 | ||
a2c02241 NR |
23311 | The corresponding @value{GDBN} command is @samp{info frame} or @samp{frame} |
23312 | (without arguments). | |
922fbb7b AC |
23313 | |
23314 | @subsubheading Example | |
23315 | ||
23316 | @smallexample | |
594fe323 | 23317 | (gdb) |
a2c02241 NR |
23318 | -stack-info-frame |
23319 | ^done,frame=@{level="1",addr="0x0001076c",func="callee3", | |
23320 | file="../../../devo/gdb/testsuite/gdb.mi/basics.c", | |
23321 | fullname="/home/foo/bar/devo/gdb/testsuite/gdb.mi/basics.c",line="17"@} | |
594fe323 | 23322 | (gdb) |
922fbb7b AC |
23323 | @end smallexample |
23324 | ||
a2c02241 NR |
23325 | @subheading The @code{-stack-info-depth} Command |
23326 | @findex -stack-info-depth | |
922fbb7b AC |
23327 | |
23328 | @subsubheading Synopsis | |
23329 | ||
23330 | @smallexample | |
a2c02241 | 23331 | -stack-info-depth [ @var{max-depth} ] |
922fbb7b AC |
23332 | @end smallexample |
23333 | ||
a2c02241 NR |
23334 | Return the depth of the stack. If the integer argument @var{max-depth} |
23335 | is specified, do not count beyond @var{max-depth} frames. | |
922fbb7b AC |
23336 | |
23337 | @subsubheading @value{GDBN} Command | |
23338 | ||
a2c02241 | 23339 | There's no equivalent @value{GDBN} command. |
922fbb7b AC |
23340 | |
23341 | @subsubheading Example | |
23342 | ||
a2c02241 NR |
23343 | For a stack with frame levels 0 through 11: |
23344 | ||
922fbb7b | 23345 | @smallexample |
594fe323 | 23346 | (gdb) |
a2c02241 NR |
23347 | -stack-info-depth |
23348 | ^done,depth="12" | |
594fe323 | 23349 | (gdb) |
a2c02241 NR |
23350 | -stack-info-depth 4 |
23351 | ^done,depth="4" | |
594fe323 | 23352 | (gdb) |
a2c02241 NR |
23353 | -stack-info-depth 12 |
23354 | ^done,depth="12" | |
594fe323 | 23355 | (gdb) |
a2c02241 NR |
23356 | -stack-info-depth 11 |
23357 | ^done,depth="11" | |
594fe323 | 23358 | (gdb) |
a2c02241 NR |
23359 | -stack-info-depth 13 |
23360 | ^done,depth="12" | |
594fe323 | 23361 | (gdb) |
922fbb7b AC |
23362 | @end smallexample |
23363 | ||
a2c02241 NR |
23364 | @subheading The @code{-stack-list-arguments} Command |
23365 | @findex -stack-list-arguments | |
922fbb7b AC |
23366 | |
23367 | @subsubheading Synopsis | |
23368 | ||
23369 | @smallexample | |
a2c02241 NR |
23370 | -stack-list-arguments @var{show-values} |
23371 | [ @var{low-frame} @var{high-frame} ] | |
922fbb7b AC |
23372 | @end smallexample |
23373 | ||
a2c02241 NR |
23374 | Display a list of the arguments for the frames between @var{low-frame} |
23375 | and @var{high-frame} (inclusive). If @var{low-frame} and | |
2f1acb09 VP |
23376 | @var{high-frame} are not provided, list the arguments for the whole |
23377 | call stack. If the two arguments are equal, show the single frame | |
23378 | at the corresponding level. It is an error if @var{low-frame} is | |
23379 | larger than the actual number of frames. On the other hand, | |
23380 | @var{high-frame} may be larger than the actual number of frames, in | |
23381 | which case only existing frames will be returned. | |
a2c02241 NR |
23382 | |
23383 | The @var{show-values} argument must have a value of 0 or 1. A value of | |
23384 | 0 means that only the names of the arguments are listed, a value of 1 | |
23385 | means that both names and values of the arguments are printed. | |
922fbb7b | 23386 | |
b3372f91 VP |
23387 | Use of this command to obtain arguments in a single frame is |
23388 | deprecated in favor of the @samp{-stack-list-variables} command. | |
23389 | ||
922fbb7b AC |
23390 | @subsubheading @value{GDBN} Command |
23391 | ||
a2c02241 NR |
23392 | @value{GDBN} does not have an equivalent command. @code{gdbtk} has a |
23393 | @samp{gdb_get_args} command which partially overlaps with the | |
23394 | functionality of @samp{-stack-list-arguments}. | |
922fbb7b AC |
23395 | |
23396 | @subsubheading Example | |
922fbb7b | 23397 | |
a2c02241 | 23398 | @smallexample |
594fe323 | 23399 | (gdb) |
a2c02241 NR |
23400 | -stack-list-frames |
23401 | ^done, | |
23402 | stack=[ | |
23403 | frame=@{level="0",addr="0x00010734",func="callee4", | |
23404 | file="../../../devo/gdb/testsuite/gdb.mi/basics.c", | |
23405 | fullname="/home/foo/bar/devo/gdb/testsuite/gdb.mi/basics.c",line="8"@}, | |
23406 | frame=@{level="1",addr="0x0001076c",func="callee3", | |
23407 | file="../../../devo/gdb/testsuite/gdb.mi/basics.c", | |
23408 | fullname="/home/foo/bar/devo/gdb/testsuite/gdb.mi/basics.c",line="17"@}, | |
23409 | frame=@{level="2",addr="0x0001078c",func="callee2", | |
23410 | file="../../../devo/gdb/testsuite/gdb.mi/basics.c", | |
23411 | fullname="/home/foo/bar/devo/gdb/testsuite/gdb.mi/basics.c",line="22"@}, | |
23412 | frame=@{level="3",addr="0x000107b4",func="callee1", | |
23413 | file="../../../devo/gdb/testsuite/gdb.mi/basics.c", | |
23414 | fullname="/home/foo/bar/devo/gdb/testsuite/gdb.mi/basics.c",line="27"@}, | |
23415 | frame=@{level="4",addr="0x000107e0",func="main", | |
23416 | file="../../../devo/gdb/testsuite/gdb.mi/basics.c", | |
23417 | fullname="/home/foo/bar/devo/gdb/testsuite/gdb.mi/basics.c",line="32"@}] | |
594fe323 | 23418 | (gdb) |
a2c02241 NR |
23419 | -stack-list-arguments 0 |
23420 | ^done, | |
23421 | stack-args=[ | |
23422 | frame=@{level="0",args=[]@}, | |
23423 | frame=@{level="1",args=[name="strarg"]@}, | |
23424 | frame=@{level="2",args=[name="intarg",name="strarg"]@}, | |
23425 | frame=@{level="3",args=[name="intarg",name="strarg",name="fltarg"]@}, | |
23426 | frame=@{level="4",args=[]@}] | |
594fe323 | 23427 | (gdb) |
a2c02241 NR |
23428 | -stack-list-arguments 1 |
23429 | ^done, | |
23430 | stack-args=[ | |
23431 | frame=@{level="0",args=[]@}, | |
23432 | frame=@{level="1", | |
23433 | args=[@{name="strarg",value="0x11940 \"A string argument.\""@}]@}, | |
23434 | frame=@{level="2",args=[ | |
23435 | @{name="intarg",value="2"@}, | |
23436 | @{name="strarg",value="0x11940 \"A string argument.\""@}]@}, | |
23437 | @{frame=@{level="3",args=[ | |
23438 | @{name="intarg",value="2"@}, | |
23439 | @{name="strarg",value="0x11940 \"A string argument.\""@}, | |
23440 | @{name="fltarg",value="3.5"@}]@}, | |
23441 | frame=@{level="4",args=[]@}] | |
594fe323 | 23442 | (gdb) |
a2c02241 NR |
23443 | -stack-list-arguments 0 2 2 |
23444 | ^done,stack-args=[frame=@{level="2",args=[name="intarg",name="strarg"]@}] | |
594fe323 | 23445 | (gdb) |
a2c02241 NR |
23446 | -stack-list-arguments 1 2 2 |
23447 | ^done,stack-args=[frame=@{level="2", | |
23448 | args=[@{name="intarg",value="2"@}, | |
23449 | @{name="strarg",value="0x11940 \"A string argument.\""@}]@}] | |
594fe323 | 23450 | (gdb) |
a2c02241 NR |
23451 | @end smallexample |
23452 | ||
23453 | @c @subheading -stack-list-exception-handlers | |
922fbb7b | 23454 | |
a2c02241 NR |
23455 | |
23456 | @subheading The @code{-stack-list-frames} Command | |
23457 | @findex -stack-list-frames | |
1abaf70c BR |
23458 | |
23459 | @subsubheading Synopsis | |
23460 | ||
23461 | @smallexample | |
a2c02241 | 23462 | -stack-list-frames [ @var{low-frame} @var{high-frame} ] |
1abaf70c BR |
23463 | @end smallexample |
23464 | ||
a2c02241 NR |
23465 | List the frames currently on the stack. For each frame it displays the |
23466 | following info: | |
23467 | ||
23468 | @table @samp | |
23469 | @item @var{level} | |
d3e8051b | 23470 | The frame number, 0 being the topmost frame, i.e., the innermost function. |
a2c02241 NR |
23471 | @item @var{addr} |
23472 | The @code{$pc} value for that frame. | |
23473 | @item @var{func} | |
23474 | Function name. | |
23475 | @item @var{file} | |
23476 | File name of the source file where the function lives. | |
23477 | @item @var{line} | |
23478 | Line number corresponding to the @code{$pc}. | |
23479 | @end table | |
23480 | ||
23481 | If invoked without arguments, this command prints a backtrace for the | |
23482 | whole stack. If given two integer arguments, it shows the frames whose | |
23483 | levels are between the two arguments (inclusive). If the two arguments | |
2ab1eb7a VP |
23484 | are equal, it shows the single frame at the corresponding level. It is |
23485 | an error if @var{low-frame} is larger than the actual number of | |
a5451f4e | 23486 | frames. On the other hand, @var{high-frame} may be larger than the |
2ab1eb7a | 23487 | actual number of frames, in which case only existing frames will be returned. |
1abaf70c BR |
23488 | |
23489 | @subsubheading @value{GDBN} Command | |
23490 | ||
a2c02241 | 23491 | The corresponding @value{GDBN} commands are @samp{backtrace} and @samp{where}. |
1abaf70c BR |
23492 | |
23493 | @subsubheading Example | |
23494 | ||
a2c02241 NR |
23495 | Full stack backtrace: |
23496 | ||
1abaf70c | 23497 | @smallexample |
594fe323 | 23498 | (gdb) |
a2c02241 NR |
23499 | -stack-list-frames |
23500 | ^done,stack= | |
23501 | [frame=@{level="0",addr="0x0001076c",func="foo", | |
23502 | file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="11"@}, | |
23503 | frame=@{level="1",addr="0x000107a4",func="foo", | |
23504 | file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@}, | |
23505 | frame=@{level="2",addr="0x000107a4",func="foo", | |
23506 | file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@}, | |
23507 | frame=@{level="3",addr="0x000107a4",func="foo", | |
23508 | file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@}, | |
23509 | frame=@{level="4",addr="0x000107a4",func="foo", | |
23510 | file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@}, | |
23511 | frame=@{level="5",addr="0x000107a4",func="foo", | |
23512 | file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@}, | |
23513 | frame=@{level="6",addr="0x000107a4",func="foo", | |
23514 | file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@}, | |
23515 | frame=@{level="7",addr="0x000107a4",func="foo", | |
23516 | file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@}, | |
23517 | frame=@{level="8",addr="0x000107a4",func="foo", | |
23518 | file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@}, | |
23519 | frame=@{level="9",addr="0x000107a4",func="foo", | |
23520 | file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@}, | |
23521 | frame=@{level="10",addr="0x000107a4",func="foo", | |
23522 | file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@}, | |
23523 | frame=@{level="11",addr="0x00010738",func="main", | |
23524 | file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="4"@}] | |
594fe323 | 23525 | (gdb) |
1abaf70c BR |
23526 | @end smallexample |
23527 | ||
a2c02241 | 23528 | Show frames between @var{low_frame} and @var{high_frame}: |
1abaf70c | 23529 | |
a2c02241 | 23530 | @smallexample |
594fe323 | 23531 | (gdb) |
a2c02241 NR |
23532 | -stack-list-frames 3 5 |
23533 | ^done,stack= | |
23534 | [frame=@{level="3",addr="0x000107a4",func="foo", | |
23535 | file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@}, | |
23536 | frame=@{level="4",addr="0x000107a4",func="foo", | |
23537 | file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@}, | |
23538 | frame=@{level="5",addr="0x000107a4",func="foo", | |
23539 | file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@}] | |
594fe323 | 23540 | (gdb) |
a2c02241 | 23541 | @end smallexample |
922fbb7b | 23542 | |
a2c02241 | 23543 | Show a single frame: |
922fbb7b AC |
23544 | |
23545 | @smallexample | |
594fe323 | 23546 | (gdb) |
a2c02241 NR |
23547 | -stack-list-frames 3 3 |
23548 | ^done,stack= | |
23549 | [frame=@{level="3",addr="0x000107a4",func="foo", | |
23550 | file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@}] | |
594fe323 | 23551 | (gdb) |
922fbb7b AC |
23552 | @end smallexample |
23553 | ||
922fbb7b | 23554 | |
a2c02241 NR |
23555 | @subheading The @code{-stack-list-locals} Command |
23556 | @findex -stack-list-locals | |
57c22c6c | 23557 | |
a2c02241 | 23558 | @subsubheading Synopsis |
922fbb7b AC |
23559 | |
23560 | @smallexample | |
a2c02241 | 23561 | -stack-list-locals @var{print-values} |
922fbb7b AC |
23562 | @end smallexample |
23563 | ||
a2c02241 NR |
23564 | Display the local variable names for the selected frame. If |
23565 | @var{print-values} is 0 or @code{--no-values}, print only the names of | |
23566 | the variables; if it is 1 or @code{--all-values}, print also their | |
23567 | values; and if it is 2 or @code{--simple-values}, print the name, | |
23568 | type and value for simple data types and the name and type for arrays, | |
23569 | structures and unions. In this last case, a frontend can immediately | |
23570 | display the value of simple data types and create variable objects for | |
d3e8051b | 23571 | other data types when the user wishes to explore their values in |
a2c02241 | 23572 | more detail. |
922fbb7b | 23573 | |
b3372f91 VP |
23574 | This command is deprecated in favor of the |
23575 | @samp{-stack-list-variables} command. | |
23576 | ||
922fbb7b AC |
23577 | @subsubheading @value{GDBN} Command |
23578 | ||
a2c02241 | 23579 | @samp{info locals} in @value{GDBN}, @samp{gdb_get_locals} in @code{gdbtk}. |
922fbb7b AC |
23580 | |
23581 | @subsubheading Example | |
922fbb7b AC |
23582 | |
23583 | @smallexample | |
594fe323 | 23584 | (gdb) |
a2c02241 NR |
23585 | -stack-list-locals 0 |
23586 | ^done,locals=[name="A",name="B",name="C"] | |
594fe323 | 23587 | (gdb) |
a2c02241 NR |
23588 | -stack-list-locals --all-values |
23589 | ^done,locals=[@{name="A",value="1"@},@{name="B",value="2"@}, | |
23590 | @{name="C",value="@{1, 2, 3@}"@}] | |
23591 | -stack-list-locals --simple-values | |
23592 | ^done,locals=[@{name="A",type="int",value="1"@}, | |
23593 | @{name="B",type="int",value="2"@},@{name="C",type="int [3]"@}] | |
594fe323 | 23594 | (gdb) |
922fbb7b AC |
23595 | @end smallexample |
23596 | ||
b3372f91 VP |
23597 | @subheading The @code{-stack-list-variables} Command |
23598 | @findex -stack-list-variables | |
23599 | ||
23600 | @subsubheading Synopsis | |
23601 | ||
23602 | @smallexample | |
23603 | -stack-list-variables @var{print-values} | |
23604 | @end smallexample | |
23605 | ||
23606 | Display the names of local variables and function arguments for the selected frame. If | |
23607 | @var{print-values} is 0 or @code{--no-values}, print only the names of | |
23608 | the variables; if it is 1 or @code{--all-values}, print also their | |
23609 | values; and if it is 2 or @code{--simple-values}, print the name, | |
23610 | type and value for simple data types and the name and type for arrays, | |
23611 | structures and unions. | |
23612 | ||
23613 | @subsubheading Example | |
23614 | ||
23615 | @smallexample | |
23616 | (gdb) | |
23617 | -stack-list-variables --thread 1 --frame 0 --all-values | |
4f412fd0 | 23618 | ^done,variables=[@{name="x",value="11"@},@{name="s",value="@{a = 1, b = 2@}"@}] |
b3372f91 VP |
23619 | (gdb) |
23620 | @end smallexample | |
23621 | ||
922fbb7b | 23622 | |
a2c02241 NR |
23623 | @subheading The @code{-stack-select-frame} Command |
23624 | @findex -stack-select-frame | |
922fbb7b AC |
23625 | |
23626 | @subsubheading Synopsis | |
23627 | ||
23628 | @smallexample | |
a2c02241 | 23629 | -stack-select-frame @var{framenum} |
922fbb7b AC |
23630 | @end smallexample |
23631 | ||
a2c02241 NR |
23632 | Change the selected frame. Select a different frame @var{framenum} on |
23633 | the stack. | |
922fbb7b | 23634 | |
c3b108f7 VP |
23635 | This command in deprecated in favor of passing the @samp{--frame} |
23636 | option to every command. | |
23637 | ||
922fbb7b AC |
23638 | @subsubheading @value{GDBN} Command |
23639 | ||
a2c02241 NR |
23640 | The corresponding @value{GDBN} commands are @samp{frame}, @samp{up}, |
23641 | @samp{down}, @samp{select-frame}, @samp{up-silent}, and @samp{down-silent}. | |
922fbb7b AC |
23642 | |
23643 | @subsubheading Example | |
23644 | ||
23645 | @smallexample | |
594fe323 | 23646 | (gdb) |
a2c02241 | 23647 | -stack-select-frame 2 |
922fbb7b | 23648 | ^done |
594fe323 | 23649 | (gdb) |
922fbb7b AC |
23650 | @end smallexample |
23651 | ||
23652 | @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% | |
a2c02241 NR |
23653 | @node GDB/MI Variable Objects |
23654 | @section @sc{gdb/mi} Variable Objects | |
922fbb7b | 23655 | |
a1b5960f | 23656 | @ignore |
922fbb7b | 23657 | |
a2c02241 | 23658 | @subheading Motivation for Variable Objects in @sc{gdb/mi} |
922fbb7b | 23659 | |
a2c02241 NR |
23660 | For the implementation of a variable debugger window (locals, watched |
23661 | expressions, etc.), we are proposing the adaptation of the existing code | |
23662 | used by @code{Insight}. | |
922fbb7b | 23663 | |
a2c02241 | 23664 | The two main reasons for that are: |
922fbb7b | 23665 | |
a2c02241 NR |
23666 | @enumerate 1 |
23667 | @item | |
23668 | It has been proven in practice (it is already on its second generation). | |
922fbb7b | 23669 | |
a2c02241 NR |
23670 | @item |
23671 | It will shorten development time (needless to say how important it is | |
23672 | now). | |
23673 | @end enumerate | |
922fbb7b | 23674 | |
a2c02241 NR |
23675 | The original interface was designed to be used by Tcl code, so it was |
23676 | slightly changed so it could be used through @sc{gdb/mi}. This section | |
23677 | describes the @sc{gdb/mi} operations that will be available and gives some | |
23678 | hints about their use. | |
922fbb7b | 23679 | |
a2c02241 NR |
23680 | @emph{Note}: In addition to the set of operations described here, we |
23681 | expect the @sc{gui} implementation of a variable window to require, at | |
23682 | least, the following operations: | |
922fbb7b | 23683 | |
a2c02241 NR |
23684 | @itemize @bullet |
23685 | @item @code{-gdb-show} @code{output-radix} | |
23686 | @item @code{-stack-list-arguments} | |
23687 | @item @code{-stack-list-locals} | |
23688 | @item @code{-stack-select-frame} | |
23689 | @end itemize | |
922fbb7b | 23690 | |
a1b5960f VP |
23691 | @end ignore |
23692 | ||
c8b2f53c | 23693 | @subheading Introduction to Variable Objects |
922fbb7b | 23694 | |
a2c02241 | 23695 | @cindex variable objects in @sc{gdb/mi} |
c8b2f53c VP |
23696 | |
23697 | Variable objects are "object-oriented" MI interface for examining and | |
23698 | changing values of expressions. Unlike some other MI interfaces that | |
23699 | work with expressions, variable objects are specifically designed for | |
23700 | simple and efficient presentation in the frontend. A variable object | |
23701 | is identified by string name. When a variable object is created, the | |
23702 | frontend specifies the expression for that variable object. The | |
23703 | expression can be a simple variable, or it can be an arbitrary complex | |
23704 | expression, and can even involve CPU registers. After creating a | |
23705 | variable object, the frontend can invoke other variable object | |
23706 | operations---for example to obtain or change the value of a variable | |
23707 | object, or to change display format. | |
23708 | ||
23709 | Variable objects have hierarchical tree structure. Any variable object | |
23710 | that corresponds to a composite type, such as structure in C, has | |
23711 | a number of child variable objects, for example corresponding to each | |
23712 | element of a structure. A child variable object can itself have | |
23713 | children, recursively. Recursion ends when we reach | |
25d5ea92 VP |
23714 | leaf variable objects, which always have built-in types. Child variable |
23715 | objects are created only by explicit request, so if a frontend | |
23716 | is not interested in the children of a particular variable object, no | |
23717 | child will be created. | |
c8b2f53c VP |
23718 | |
23719 | For a leaf variable object it is possible to obtain its value as a | |
23720 | string, or set the value from a string. String value can be also | |
23721 | obtained for a non-leaf variable object, but it's generally a string | |
23722 | that only indicates the type of the object, and does not list its | |
23723 | contents. Assignment to a non-leaf variable object is not allowed. | |
23724 | ||
23725 | A frontend does not need to read the values of all variable objects each time | |
23726 | the program stops. Instead, MI provides an update command that lists all | |
23727 | variable objects whose values has changed since the last update | |
23728 | operation. This considerably reduces the amount of data that must | |
25d5ea92 VP |
23729 | be transferred to the frontend. As noted above, children variable |
23730 | objects are created on demand, and only leaf variable objects have a | |
23731 | real value. As result, gdb will read target memory only for leaf | |
23732 | variables that frontend has created. | |
23733 | ||
23734 | The automatic update is not always desirable. For example, a frontend | |
23735 | might want to keep a value of some expression for future reference, | |
23736 | and never update it. For another example, fetching memory is | |
23737 | relatively slow for embedded targets, so a frontend might want | |
23738 | to disable automatic update for the variables that are either not | |
23739 | visible on the screen, or ``closed''. This is possible using so | |
23740 | called ``frozen variable objects''. Such variable objects are never | |
23741 | implicitly updated. | |
922fbb7b | 23742 | |
c3b108f7 VP |
23743 | Variable objects can be either @dfn{fixed} or @dfn{floating}. For the |
23744 | fixed variable object, the expression is parsed when the variable | |
23745 | object is created, including associating identifiers to specific | |
23746 | variables. The meaning of expression never changes. For a floating | |
23747 | variable object the values of variables whose names appear in the | |
23748 | expressions are re-evaluated every time in the context of the current | |
23749 | frame. Consider this example: | |
23750 | ||
23751 | @smallexample | |
23752 | void do_work(...) | |
23753 | @{ | |
23754 | struct work_state state; | |
23755 | ||
23756 | if (...) | |
23757 | do_work(...); | |
23758 | @} | |
23759 | @end smallexample | |
23760 | ||
23761 | If a fixed variable object for the @code{state} variable is created in | |
23762 | this function, and we enter the recursive call, the the variable | |
23763 | object will report the value of @code{state} in the top-level | |
23764 | @code{do_work} invocation. On the other hand, a floating variable | |
23765 | object will report the value of @code{state} in the current frame. | |
23766 | ||
23767 | If an expression specified when creating a fixed variable object | |
23768 | refers to a local variable, the variable object becomes bound to the | |
23769 | thread and frame in which the variable object is created. When such | |
23770 | variable object is updated, @value{GDBN} makes sure that the | |
23771 | thread/frame combination the variable object is bound to still exists, | |
23772 | and re-evaluates the variable object in context of that thread/frame. | |
23773 | ||
a2c02241 NR |
23774 | The following is the complete set of @sc{gdb/mi} operations defined to |
23775 | access this functionality: | |
922fbb7b | 23776 | |
a2c02241 NR |
23777 | @multitable @columnfractions .4 .6 |
23778 | @item @strong{Operation} | |
23779 | @tab @strong{Description} | |
922fbb7b | 23780 | |
0cc7d26f TT |
23781 | @item @code{-enable-pretty-printing} |
23782 | @tab enable Python-based pretty-printing | |
a2c02241 NR |
23783 | @item @code{-var-create} |
23784 | @tab create a variable object | |
23785 | @item @code{-var-delete} | |
22d8a470 | 23786 | @tab delete the variable object and/or its children |
a2c02241 NR |
23787 | @item @code{-var-set-format} |
23788 | @tab set the display format of this variable | |
23789 | @item @code{-var-show-format} | |
23790 | @tab show the display format of this variable | |
23791 | @item @code{-var-info-num-children} | |
23792 | @tab tells how many children this object has | |
23793 | @item @code{-var-list-children} | |
23794 | @tab return a list of the object's children | |
23795 | @item @code{-var-info-type} | |
23796 | @tab show the type of this variable object | |
23797 | @item @code{-var-info-expression} | |
02142340 VP |
23798 | @tab print parent-relative expression that this variable object represents |
23799 | @item @code{-var-info-path-expression} | |
23800 | @tab print full expression that this variable object represents | |
a2c02241 NR |
23801 | @item @code{-var-show-attributes} |
23802 | @tab is this variable editable? does it exist here? | |
23803 | @item @code{-var-evaluate-expression} | |
23804 | @tab get the value of this variable | |
23805 | @item @code{-var-assign} | |
23806 | @tab set the value of this variable | |
23807 | @item @code{-var-update} | |
23808 | @tab update the variable and its children | |
25d5ea92 VP |
23809 | @item @code{-var-set-frozen} |
23810 | @tab set frozeness attribute | |
0cc7d26f TT |
23811 | @item @code{-var-set-update-range} |
23812 | @tab set range of children to display on update | |
a2c02241 | 23813 | @end multitable |
922fbb7b | 23814 | |
a2c02241 NR |
23815 | In the next subsection we describe each operation in detail and suggest |
23816 | how it can be used. | |
922fbb7b | 23817 | |
a2c02241 | 23818 | @subheading Description And Use of Operations on Variable Objects |
922fbb7b | 23819 | |
0cc7d26f TT |
23820 | @subheading The @code{-enable-pretty-printing} Command |
23821 | @findex -enable-pretty-printing | |
23822 | ||
23823 | @smallexample | |
23824 | -enable-pretty-printing | |
23825 | @end smallexample | |
23826 | ||
23827 | @value{GDBN} allows Python-based visualizers to affect the output of the | |
23828 | MI variable object commands. However, because there was no way to | |
23829 | implement this in a fully backward-compatible way, a front end must | |
23830 | request that this functionality be enabled. | |
23831 | ||
23832 | Once enabled, this feature cannot be disabled. | |
23833 | ||
23834 | Note that if Python support has not been compiled into @value{GDBN}, | |
23835 | this command will still succeed (and do nothing). | |
23836 | ||
f43030c4 TT |
23837 | This feature is currently (as of @value{GDBN} 7.0) experimental, and |
23838 | may work differently in future versions of @value{GDBN}. | |
23839 | ||
a2c02241 NR |
23840 | @subheading The @code{-var-create} Command |
23841 | @findex -var-create | |
ef21caaf | 23842 | |
a2c02241 | 23843 | @subsubheading Synopsis |
ef21caaf | 23844 | |
a2c02241 NR |
23845 | @smallexample |
23846 | -var-create @{@var{name} | "-"@} | |
c3b108f7 | 23847 | @{@var{frame-addr} | "*" | "@@"@} @var{expression} |
a2c02241 NR |
23848 | @end smallexample |
23849 | ||
23850 | This operation creates a variable object, which allows the monitoring of | |
23851 | a variable, the result of an expression, a memory cell or a CPU | |
23852 | register. | |
ef21caaf | 23853 | |
a2c02241 NR |
23854 | The @var{name} parameter is the string by which the object can be |
23855 | referenced. It must be unique. If @samp{-} is specified, the varobj | |
23856 | system will generate a string ``varNNNNNN'' automatically. It will be | |
c3b108f7 | 23857 | unique provided that one does not specify @var{name} of that format. |
a2c02241 | 23858 | The command fails if a duplicate name is found. |
ef21caaf | 23859 | |
a2c02241 NR |
23860 | The frame under which the expression should be evaluated can be |
23861 | specified by @var{frame-addr}. A @samp{*} indicates that the current | |
c3b108f7 VP |
23862 | frame should be used. A @samp{@@} indicates that a floating variable |
23863 | object must be created. | |
922fbb7b | 23864 | |
a2c02241 NR |
23865 | @var{expression} is any expression valid on the current language set (must not |
23866 | begin with a @samp{*}), or one of the following: | |
922fbb7b | 23867 | |
a2c02241 NR |
23868 | @itemize @bullet |
23869 | @item | |
23870 | @samp{*@var{addr}}, where @var{addr} is the address of a memory cell | |
922fbb7b | 23871 | |
a2c02241 NR |
23872 | @item |
23873 | @samp{*@var{addr}-@var{addr}} --- a memory address range (TBD) | |
922fbb7b | 23874 | |
a2c02241 NR |
23875 | @item |
23876 | @samp{$@var{regname}} --- a CPU register name | |
23877 | @end itemize | |
922fbb7b | 23878 | |
0cc7d26f TT |
23879 | @cindex dynamic varobj |
23880 | A varobj's contents may be provided by a Python-based pretty-printer. In this | |
23881 | case the varobj is known as a @dfn{dynamic varobj}. Dynamic varobjs | |
23882 | have slightly different semantics in some cases. If the | |
23883 | @code{-enable-pretty-printing} command is not sent, then @value{GDBN} | |
23884 | will never create a dynamic varobj. This ensures backward | |
23885 | compatibility for existing clients. | |
23886 | ||
a2c02241 | 23887 | @subsubheading Result |
922fbb7b | 23888 | |
0cc7d26f TT |
23889 | This operation returns attributes of the newly-created varobj. These |
23890 | are: | |
23891 | ||
23892 | @table @samp | |
23893 | @item name | |
23894 | The name of the varobj. | |
23895 | ||
23896 | @item numchild | |
23897 | The number of children of the varobj. This number is not necessarily | |
23898 | reliable for a dynamic varobj. Instead, you must examine the | |
23899 | @samp{has_more} attribute. | |
23900 | ||
23901 | @item value | |
23902 | The varobj's scalar value. For a varobj whose type is some sort of | |
23903 | aggregate (e.g., a @code{struct}), or for a dynamic varobj, this value | |
23904 | will not be interesting. | |
23905 | ||
23906 | @item type | |
23907 | The varobj's type. This is a string representation of the type, as | |
23908 | would be printed by the @value{GDBN} CLI. | |
23909 | ||
23910 | @item thread-id | |
23911 | If a variable object is bound to a specific thread, then this is the | |
23912 | thread's identifier. | |
23913 | ||
23914 | @item has_more | |
23915 | For a dynamic varobj, this indicates whether there appear to be any | |
23916 | children available. For a non-dynamic varobj, this will be 0. | |
23917 | ||
23918 | @item dynamic | |
23919 | This attribute will be present and have the value @samp{1} if the | |
23920 | varobj is a dynamic varobj. If the varobj is not a dynamic varobj, | |
23921 | then this attribute will not be present. | |
23922 | ||
23923 | @item displayhint | |
23924 | A dynamic varobj can supply a display hint to the front end. The | |
23925 | value comes directly from the Python pretty-printer object's | |
23926 | @code{display_hint} method. @xref{Pretty Printing}. | |
23927 | @end table | |
23928 | ||
23929 | Typical output will look like this: | |
922fbb7b AC |
23930 | |
23931 | @smallexample | |
0cc7d26f TT |
23932 | name="@var{name}",numchild="@var{N}",type="@var{type}",thread-id="@var{M}", |
23933 | has_more="@var{has_more}" | |
dcaaae04 NR |
23934 | @end smallexample |
23935 | ||
a2c02241 NR |
23936 | |
23937 | @subheading The @code{-var-delete} Command | |
23938 | @findex -var-delete | |
922fbb7b AC |
23939 | |
23940 | @subsubheading Synopsis | |
23941 | ||
23942 | @smallexample | |
22d8a470 | 23943 | -var-delete [ -c ] @var{name} |
922fbb7b AC |
23944 | @end smallexample |
23945 | ||
a2c02241 | 23946 | Deletes a previously created variable object and all of its children. |
22d8a470 | 23947 | With the @samp{-c} option, just deletes the children. |
922fbb7b | 23948 | |
a2c02241 | 23949 | Returns an error if the object @var{name} is not found. |
922fbb7b | 23950 | |
922fbb7b | 23951 | |
a2c02241 NR |
23952 | @subheading The @code{-var-set-format} Command |
23953 | @findex -var-set-format | |
922fbb7b | 23954 | |
a2c02241 | 23955 | @subsubheading Synopsis |
922fbb7b AC |
23956 | |
23957 | @smallexample | |
a2c02241 | 23958 | -var-set-format @var{name} @var{format-spec} |
922fbb7b AC |
23959 | @end smallexample |
23960 | ||
a2c02241 NR |
23961 | Sets the output format for the value of the object @var{name} to be |
23962 | @var{format-spec}. | |
23963 | ||
de051565 | 23964 | @anchor{-var-set-format} |
a2c02241 NR |
23965 | The syntax for the @var{format-spec} is as follows: |
23966 | ||
23967 | @smallexample | |
23968 | @var{format-spec} @expansion{} | |
23969 | @{binary | decimal | hexadecimal | octal | natural@} | |
23970 | @end smallexample | |
23971 | ||
c8b2f53c VP |
23972 | The natural format is the default format choosen automatically |
23973 | based on the variable type (like decimal for an @code{int}, hex | |
23974 | for pointers, etc.). | |
23975 | ||
23976 | For a variable with children, the format is set only on the | |
23977 | variable itself, and the children are not affected. | |
a2c02241 NR |
23978 | |
23979 | @subheading The @code{-var-show-format} Command | |
23980 | @findex -var-show-format | |
922fbb7b AC |
23981 | |
23982 | @subsubheading Synopsis | |
23983 | ||
23984 | @smallexample | |
a2c02241 | 23985 | -var-show-format @var{name} |
922fbb7b AC |
23986 | @end smallexample |
23987 | ||
a2c02241 | 23988 | Returns the format used to display the value of the object @var{name}. |
922fbb7b | 23989 | |
a2c02241 NR |
23990 | @smallexample |
23991 | @var{format} @expansion{} | |
23992 | @var{format-spec} | |
23993 | @end smallexample | |
922fbb7b | 23994 | |
922fbb7b | 23995 | |
a2c02241 NR |
23996 | @subheading The @code{-var-info-num-children} Command |
23997 | @findex -var-info-num-children | |
23998 | ||
23999 | @subsubheading Synopsis | |
24000 | ||
24001 | @smallexample | |
24002 | -var-info-num-children @var{name} | |
24003 | @end smallexample | |
24004 | ||
24005 | Returns the number of children of a variable object @var{name}: | |
24006 | ||
24007 | @smallexample | |
24008 | numchild=@var{n} | |
24009 | @end smallexample | |
24010 | ||
0cc7d26f TT |
24011 | Note that this number is not completely reliable for a dynamic varobj. |
24012 | It will return the current number of children, but more children may | |
24013 | be available. | |
24014 | ||
a2c02241 NR |
24015 | |
24016 | @subheading The @code{-var-list-children} Command | |
24017 | @findex -var-list-children | |
24018 | ||
24019 | @subsubheading Synopsis | |
24020 | ||
24021 | @smallexample | |
0cc7d26f | 24022 | -var-list-children [@var{print-values}] @var{name} [@var{from} @var{to}] |
a2c02241 | 24023 | @end smallexample |
b569d230 | 24024 | @anchor{-var-list-children} |
a2c02241 NR |
24025 | |
24026 | Return a list of the children of the specified variable object and | |
24027 | create variable objects for them, if they do not already exist. With | |
24028 | a single argument or if @var{print-values} has a value for of 0 or | |
24029 | @code{--no-values}, print only the names of the variables; if | |
24030 | @var{print-values} is 1 or @code{--all-values}, also print their | |
24031 | values; and if it is 2 or @code{--simple-values} print the name and | |
24032 | value for simple data types and just the name for arrays, structures | |
24033 | and unions. | |
922fbb7b | 24034 | |
0cc7d26f TT |
24035 | @var{from} and @var{to}, if specified, indicate the range of children |
24036 | to report. If @var{from} or @var{to} is less than zero, the range is | |
24037 | reset and all children will be reported. Otherwise, children starting | |
24038 | at @var{from} (zero-based) and up to and excluding @var{to} will be | |
24039 | reported. | |
24040 | ||
24041 | If a child range is requested, it will only affect the current call to | |
24042 | @code{-var-list-children}, but not future calls to @code{-var-update}. | |
24043 | For this, you must instead use @code{-var-set-update-range}. The | |
24044 | intent of this approach is to enable a front end to implement any | |
24045 | update approach it likes; for example, scrolling a view may cause the | |
24046 | front end to request more children with @code{-var-list-children}, and | |
24047 | then the front end could call @code{-var-set-update-range} with a | |
24048 | different range to ensure that future updates are restricted to just | |
24049 | the visible items. | |
24050 | ||
b569d230 EZ |
24051 | For each child the following results are returned: |
24052 | ||
24053 | @table @var | |
24054 | ||
24055 | @item name | |
24056 | Name of the variable object created for this child. | |
24057 | ||
24058 | @item exp | |
24059 | The expression to be shown to the user by the front end to designate this child. | |
24060 | For example this may be the name of a structure member. | |
24061 | ||
0cc7d26f TT |
24062 | For a dynamic varobj, this value cannot be used to form an |
24063 | expression. There is no way to do this at all with a dynamic varobj. | |
24064 | ||
b569d230 EZ |
24065 | For C/C@t{++} structures there are several pseudo children returned to |
24066 | designate access qualifiers. For these pseudo children @var{exp} is | |
24067 | @samp{public}, @samp{private}, or @samp{protected}. In this case the | |
24068 | type and value are not present. | |
24069 | ||
0cc7d26f TT |
24070 | A dynamic varobj will not report the access qualifying |
24071 | pseudo-children, regardless of the language. This information is not | |
24072 | available at all with a dynamic varobj. | |
24073 | ||
b569d230 | 24074 | @item numchild |
0cc7d26f TT |
24075 | Number of children this child has. For a dynamic varobj, this will be |
24076 | 0. | |
b569d230 EZ |
24077 | |
24078 | @item type | |
24079 | The type of the child. | |
24080 | ||
24081 | @item value | |
24082 | If values were requested, this is the value. | |
24083 | ||
24084 | @item thread-id | |
24085 | If this variable object is associated with a thread, this is the thread id. | |
24086 | Otherwise this result is not present. | |
24087 | ||
24088 | @item frozen | |
24089 | If the variable object is frozen, this variable will be present with a value of 1. | |
24090 | @end table | |
24091 | ||
0cc7d26f TT |
24092 | The result may have its own attributes: |
24093 | ||
24094 | @table @samp | |
24095 | @item displayhint | |
24096 | A dynamic varobj can supply a display hint to the front end. The | |
24097 | value comes directly from the Python pretty-printer object's | |
24098 | @code{display_hint} method. @xref{Pretty Printing}. | |
24099 | ||
24100 | @item has_more | |
24101 | This is an integer attribute which is nonzero if there are children | |
24102 | remaining after the end of the selected range. | |
24103 | @end table | |
24104 | ||
922fbb7b AC |
24105 | @subsubheading Example |
24106 | ||
24107 | @smallexample | |
594fe323 | 24108 | (gdb) |
a2c02241 | 24109 | -var-list-children n |
b569d230 | 24110 | ^done,numchild=@var{n},children=[child=@{name=@var{name},exp=@var{exp}, |
a2c02241 | 24111 | numchild=@var{n},type=@var{type}@},@r{(repeats N times)}] |
594fe323 | 24112 | (gdb) |
a2c02241 | 24113 | -var-list-children --all-values n |
b569d230 | 24114 | ^done,numchild=@var{n},children=[child=@{name=@var{name},exp=@var{exp}, |
a2c02241 | 24115 | numchild=@var{n},value=@var{value},type=@var{type}@},@r{(repeats N times)}] |
922fbb7b AC |
24116 | @end smallexample |
24117 | ||
922fbb7b | 24118 | |
a2c02241 NR |
24119 | @subheading The @code{-var-info-type} Command |
24120 | @findex -var-info-type | |
922fbb7b | 24121 | |
a2c02241 NR |
24122 | @subsubheading Synopsis |
24123 | ||
24124 | @smallexample | |
24125 | -var-info-type @var{name} | |
24126 | @end smallexample | |
24127 | ||
24128 | Returns the type of the specified variable @var{name}. The type is | |
24129 | returned as a string in the same format as it is output by the | |
24130 | @value{GDBN} CLI: | |
24131 | ||
24132 | @smallexample | |
24133 | type=@var{typename} | |
24134 | @end smallexample | |
24135 | ||
24136 | ||
24137 | @subheading The @code{-var-info-expression} Command | |
24138 | @findex -var-info-expression | |
922fbb7b AC |
24139 | |
24140 | @subsubheading Synopsis | |
24141 | ||
24142 | @smallexample | |
a2c02241 | 24143 | -var-info-expression @var{name} |
922fbb7b AC |
24144 | @end smallexample |
24145 | ||
02142340 VP |
24146 | Returns a string that is suitable for presenting this |
24147 | variable object in user interface. The string is generally | |
24148 | not valid expression in the current language, and cannot be evaluated. | |
24149 | ||
24150 | For example, if @code{a} is an array, and variable object | |
24151 | @code{A} was created for @code{a}, then we'll get this output: | |
922fbb7b | 24152 | |
a2c02241 | 24153 | @smallexample |
02142340 VP |
24154 | (gdb) -var-info-expression A.1 |
24155 | ^done,lang="C",exp="1" | |
a2c02241 | 24156 | @end smallexample |
922fbb7b | 24157 | |
a2c02241 | 24158 | @noindent |
02142340 VP |
24159 | Here, the values of @code{lang} can be @code{@{"C" | "C++" | "Java"@}}. |
24160 | ||
24161 | Note that the output of the @code{-var-list-children} command also | |
24162 | includes those expressions, so the @code{-var-info-expression} command | |
24163 | is of limited use. | |
24164 | ||
24165 | @subheading The @code{-var-info-path-expression} Command | |
24166 | @findex -var-info-path-expression | |
24167 | ||
24168 | @subsubheading Synopsis | |
24169 | ||
24170 | @smallexample | |
24171 | -var-info-path-expression @var{name} | |
24172 | @end smallexample | |
24173 | ||
24174 | Returns an expression that can be evaluated in the current | |
24175 | context and will yield the same value that a variable object has. | |
24176 | Compare this with the @code{-var-info-expression} command, which | |
24177 | result can be used only for UI presentation. Typical use of | |
24178 | the @code{-var-info-path-expression} command is creating a | |
24179 | watchpoint from a variable object. | |
24180 | ||
0cc7d26f TT |
24181 | This command is currently not valid for children of a dynamic varobj, |
24182 | and will give an error when invoked on one. | |
24183 | ||
02142340 VP |
24184 | For example, suppose @code{C} is a C@t{++} class, derived from class |
24185 | @code{Base}, and that the @code{Base} class has a member called | |
24186 | @code{m_size}. Assume a variable @code{c} is has the type of | |
24187 | @code{C} and a variable object @code{C} was created for variable | |
24188 | @code{c}. Then, we'll get this output: | |
24189 | @smallexample | |
24190 | (gdb) -var-info-path-expression C.Base.public.m_size | |
24191 | ^done,path_expr=((Base)c).m_size) | |
24192 | @end smallexample | |
922fbb7b | 24193 | |
a2c02241 NR |
24194 | @subheading The @code{-var-show-attributes} Command |
24195 | @findex -var-show-attributes | |
922fbb7b | 24196 | |
a2c02241 | 24197 | @subsubheading Synopsis |
922fbb7b | 24198 | |
a2c02241 NR |
24199 | @smallexample |
24200 | -var-show-attributes @var{name} | |
24201 | @end smallexample | |
922fbb7b | 24202 | |
a2c02241 | 24203 | List attributes of the specified variable object @var{name}: |
922fbb7b AC |
24204 | |
24205 | @smallexample | |
a2c02241 | 24206 | status=@var{attr} [ ( ,@var{attr} )* ] |
922fbb7b AC |
24207 | @end smallexample |
24208 | ||
a2c02241 NR |
24209 | @noindent |
24210 | where @var{attr} is @code{@{ @{ editable | noneditable @} | TBD @}}. | |
24211 | ||
24212 | @subheading The @code{-var-evaluate-expression} Command | |
24213 | @findex -var-evaluate-expression | |
24214 | ||
24215 | @subsubheading Synopsis | |
24216 | ||
24217 | @smallexample | |
de051565 | 24218 | -var-evaluate-expression [-f @var{format-spec}] @var{name} |
a2c02241 NR |
24219 | @end smallexample |
24220 | ||
24221 | Evaluates the expression that is represented by the specified variable | |
de051565 MK |
24222 | object and returns its value as a string. The format of the string |
24223 | can be specified with the @samp{-f} option. The possible values of | |
24224 | this option are the same as for @code{-var-set-format} | |
24225 | (@pxref{-var-set-format}). If the @samp{-f} option is not specified, | |
24226 | the current display format will be used. The current display format | |
24227 | can be changed using the @code{-var-set-format} command. | |
a2c02241 NR |
24228 | |
24229 | @smallexample | |
24230 | value=@var{value} | |
24231 | @end smallexample | |
24232 | ||
24233 | Note that one must invoke @code{-var-list-children} for a variable | |
24234 | before the value of a child variable can be evaluated. | |
24235 | ||
24236 | @subheading The @code{-var-assign} Command | |
24237 | @findex -var-assign | |
24238 | ||
24239 | @subsubheading Synopsis | |
24240 | ||
24241 | @smallexample | |
24242 | -var-assign @var{name} @var{expression} | |
24243 | @end smallexample | |
24244 | ||
24245 | Assigns the value of @var{expression} to the variable object specified | |
24246 | by @var{name}. The object must be @samp{editable}. If the variable's | |
24247 | value is altered by the assign, the variable will show up in any | |
24248 | subsequent @code{-var-update} list. | |
24249 | ||
24250 | @subsubheading Example | |
922fbb7b AC |
24251 | |
24252 | @smallexample | |
594fe323 | 24253 | (gdb) |
a2c02241 NR |
24254 | -var-assign var1 3 |
24255 | ^done,value="3" | |
594fe323 | 24256 | (gdb) |
a2c02241 NR |
24257 | -var-update * |
24258 | ^done,changelist=[@{name="var1",in_scope="true",type_changed="false"@}] | |
594fe323 | 24259 | (gdb) |
922fbb7b AC |
24260 | @end smallexample |
24261 | ||
a2c02241 NR |
24262 | @subheading The @code{-var-update} Command |
24263 | @findex -var-update | |
24264 | ||
24265 | @subsubheading Synopsis | |
24266 | ||
24267 | @smallexample | |
24268 | -var-update [@var{print-values}] @{@var{name} | "*"@} | |
24269 | @end smallexample | |
24270 | ||
c8b2f53c VP |
24271 | Reevaluate the expressions corresponding to the variable object |
24272 | @var{name} and all its direct and indirect children, and return the | |
36ece8b3 NR |
24273 | list of variable objects whose values have changed; @var{name} must |
24274 | be a root variable object. Here, ``changed'' means that the result of | |
24275 | @code{-var-evaluate-expression} before and after the | |
24276 | @code{-var-update} is different. If @samp{*} is used as the variable | |
9f708cb2 VP |
24277 | object names, all existing variable objects are updated, except |
24278 | for frozen ones (@pxref{-var-set-frozen}). The option | |
36ece8b3 | 24279 | @var{print-values} determines whether both names and values, or just |
de051565 | 24280 | names are printed. The possible values of this option are the same |
36ece8b3 NR |
24281 | as for @code{-var-list-children} (@pxref{-var-list-children}). It is |
24282 | recommended to use the @samp{--all-values} option, to reduce the | |
24283 | number of MI commands needed on each program stop. | |
c8b2f53c | 24284 | |
c3b108f7 VP |
24285 | With the @samp{*} parameter, if a variable object is bound to a |
24286 | currently running thread, it will not be updated, without any | |
24287 | diagnostic. | |
a2c02241 | 24288 | |
0cc7d26f TT |
24289 | If @code{-var-set-update-range} was previously used on a varobj, then |
24290 | only the selected range of children will be reported. | |
922fbb7b | 24291 | |
0cc7d26f TT |
24292 | @code{-var-update} reports all the changed varobjs in a tuple named |
24293 | @samp{changelist}. | |
24294 | ||
24295 | Each item in the change list is itself a tuple holding: | |
24296 | ||
24297 | @table @samp | |
24298 | @item name | |
24299 | The name of the varobj. | |
24300 | ||
24301 | @item value | |
24302 | If values were requested for this update, then this field will be | |
24303 | present and will hold the value of the varobj. | |
922fbb7b | 24304 | |
0cc7d26f | 24305 | @item in_scope |
9f708cb2 | 24306 | @anchor{-var-update} |
0cc7d26f | 24307 | This field is a string which may take one of three values: |
36ece8b3 NR |
24308 | |
24309 | @table @code | |
24310 | @item "true" | |
24311 | The variable object's current value is valid. | |
24312 | ||
24313 | @item "false" | |
24314 | The variable object does not currently hold a valid value but it may | |
24315 | hold one in the future if its associated expression comes back into | |
24316 | scope. | |
24317 | ||
24318 | @item "invalid" | |
24319 | The variable object no longer holds a valid value. | |
24320 | This can occur when the executable file being debugged has changed, | |
24321 | either through recompilation or by using the @value{GDBN} @code{file} | |
24322 | command. The front end should normally choose to delete these variable | |
24323 | objects. | |
24324 | @end table | |
24325 | ||
24326 | In the future new values may be added to this list so the front should | |
24327 | be prepared for this possibility. @xref{GDB/MI Development and Front Ends, ,@sc{GDB/MI} Development and Front Ends}. | |
24328 | ||
0cc7d26f TT |
24329 | @item type_changed |
24330 | This is only present if the varobj is still valid. If the type | |
24331 | changed, then this will be the string @samp{true}; otherwise it will | |
24332 | be @samp{false}. | |
24333 | ||
24334 | @item new_type | |
24335 | If the varobj's type changed, then this field will be present and will | |
24336 | hold the new type. | |
24337 | ||
24338 | @item new_num_children | |
24339 | For a dynamic varobj, if the number of children changed, or if the | |
24340 | type changed, this will be the new number of children. | |
24341 | ||
24342 | The @samp{numchild} field in other varobj responses is generally not | |
24343 | valid for a dynamic varobj -- it will show the number of children that | |
24344 | @value{GDBN} knows about, but because dynamic varobjs lazily | |
24345 | instantiate their children, this will not reflect the number of | |
24346 | children which may be available. | |
24347 | ||
24348 | The @samp{new_num_children} attribute only reports changes to the | |
24349 | number of children known by @value{GDBN}. This is the only way to | |
24350 | detect whether an update has removed children (which necessarily can | |
24351 | only happen at the end of the update range). | |
24352 | ||
24353 | @item displayhint | |
24354 | The display hint, if any. | |
24355 | ||
24356 | @item has_more | |
24357 | This is an integer value, which will be 1 if there are more children | |
24358 | available outside the varobj's update range. | |
24359 | ||
24360 | @item dynamic | |
24361 | This attribute will be present and have the value @samp{1} if the | |
24362 | varobj is a dynamic varobj. If the varobj is not a dynamic varobj, | |
24363 | then this attribute will not be present. | |
24364 | ||
24365 | @item new_children | |
24366 | If new children were added to a dynamic varobj within the selected | |
24367 | update range (as set by @code{-var-set-update-range}), then they will | |
24368 | be listed in this attribute. | |
24369 | @end table | |
24370 | ||
24371 | @subsubheading Example | |
24372 | ||
24373 | @smallexample | |
24374 | (gdb) | |
24375 | -var-assign var1 3 | |
24376 | ^done,value="3" | |
24377 | (gdb) | |
24378 | -var-update --all-values var1 | |
24379 | ^done,changelist=[@{name="var1",value="3",in_scope="true", | |
24380 | type_changed="false"@}] | |
24381 | (gdb) | |
24382 | @end smallexample | |
24383 | ||
25d5ea92 VP |
24384 | @subheading The @code{-var-set-frozen} Command |
24385 | @findex -var-set-frozen | |
9f708cb2 | 24386 | @anchor{-var-set-frozen} |
25d5ea92 VP |
24387 | |
24388 | @subsubheading Synopsis | |
24389 | ||
24390 | @smallexample | |
9f708cb2 | 24391 | -var-set-frozen @var{name} @var{flag} |
25d5ea92 VP |
24392 | @end smallexample |
24393 | ||
9f708cb2 | 24394 | Set the frozenness flag on the variable object @var{name}. The |
25d5ea92 | 24395 | @var{flag} parameter should be either @samp{1} to make the variable |
9f708cb2 | 24396 | frozen or @samp{0} to make it unfrozen. If a variable object is |
25d5ea92 | 24397 | frozen, then neither itself, nor any of its children, are |
9f708cb2 | 24398 | implicitly updated by @code{-var-update} of |
25d5ea92 VP |
24399 | a parent variable or by @code{-var-update *}. Only |
24400 | @code{-var-update} of the variable itself will update its value and | |
24401 | values of its children. After a variable object is unfrozen, it is | |
24402 | implicitly updated by all subsequent @code{-var-update} operations. | |
24403 | Unfreezing a variable does not update it, only subsequent | |
24404 | @code{-var-update} does. | |
24405 | ||
24406 | @subsubheading Example | |
24407 | ||
24408 | @smallexample | |
24409 | (gdb) | |
24410 | -var-set-frozen V 1 | |
24411 | ^done | |
24412 | (gdb) | |
24413 | @end smallexample | |
24414 | ||
0cc7d26f TT |
24415 | @subheading The @code{-var-set-update-range} command |
24416 | @findex -var-set-update-range | |
24417 | @anchor{-var-set-update-range} | |
24418 | ||
24419 | @subsubheading Synopsis | |
24420 | ||
24421 | @smallexample | |
24422 | -var-set-update-range @var{name} @var{from} @var{to} | |
24423 | @end smallexample | |
24424 | ||
24425 | Set the range of children to be returned by future invocations of | |
24426 | @code{-var-update}. | |
24427 | ||
24428 | @var{from} and @var{to} indicate the range of children to report. If | |
24429 | @var{from} or @var{to} is less than zero, the range is reset and all | |
24430 | children will be reported. Otherwise, children starting at @var{from} | |
24431 | (zero-based) and up to and excluding @var{to} will be reported. | |
24432 | ||
24433 | @subsubheading Example | |
24434 | ||
24435 | @smallexample | |
24436 | (gdb) | |
24437 | -var-set-update-range V 1 2 | |
24438 | ^done | |
24439 | @end smallexample | |
24440 | ||
b6313243 TT |
24441 | @subheading The @code{-var-set-visualizer} command |
24442 | @findex -var-set-visualizer | |
24443 | @anchor{-var-set-visualizer} | |
24444 | ||
24445 | @subsubheading Synopsis | |
24446 | ||
24447 | @smallexample | |
24448 | -var-set-visualizer @var{name} @var{visualizer} | |
24449 | @end smallexample | |
24450 | ||
24451 | Set a visualizer for the variable object @var{name}. | |
24452 | ||
24453 | @var{visualizer} is the visualizer to use. The special value | |
24454 | @samp{None} means to disable any visualizer in use. | |
24455 | ||
24456 | If not @samp{None}, @var{visualizer} must be a Python expression. | |
24457 | This expression must evaluate to a callable object which accepts a | |
24458 | single argument. @value{GDBN} will call this object with the value of | |
24459 | the varobj @var{name} as an argument (this is done so that the same | |
24460 | Python pretty-printing code can be used for both the CLI and MI). | |
24461 | When called, this object must return an object which conforms to the | |
24462 | pretty-printing interface (@pxref{Pretty Printing}). | |
24463 | ||
24464 | The pre-defined function @code{gdb.default_visualizer} may be used to | |
24465 | select a visualizer by following the built-in process | |
24466 | (@pxref{Selecting Pretty-Printers}). This is done automatically when | |
24467 | a varobj is created, and so ordinarily is not needed. | |
24468 | ||
24469 | This feature is only available if Python support is enabled. The MI | |
24470 | command @code{-list-features} (@pxref{GDB/MI Miscellaneous Commands}) | |
24471 | can be used to check this. | |
24472 | ||
24473 | @subsubheading Example | |
24474 | ||
24475 | Resetting the visualizer: | |
24476 | ||
24477 | @smallexample | |
24478 | (gdb) | |
24479 | -var-set-visualizer V None | |
24480 | ^done | |
24481 | @end smallexample | |
24482 | ||
24483 | Reselecting the default (type-based) visualizer: | |
24484 | ||
24485 | @smallexample | |
24486 | (gdb) | |
24487 | -var-set-visualizer V gdb.default_visualizer | |
24488 | ^done | |
24489 | @end smallexample | |
24490 | ||
24491 | Suppose @code{SomeClass} is a visualizer class. A lambda expression | |
24492 | can be used to instantiate this class for a varobj: | |
24493 | ||
24494 | @smallexample | |
24495 | (gdb) | |
24496 | -var-set-visualizer V "lambda val: SomeClass()" | |
24497 | ^done | |
24498 | @end smallexample | |
25d5ea92 | 24499 | |
a2c02241 NR |
24500 | @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% |
24501 | @node GDB/MI Data Manipulation | |
24502 | @section @sc{gdb/mi} Data Manipulation | |
922fbb7b | 24503 | |
a2c02241 NR |
24504 | @cindex data manipulation, in @sc{gdb/mi} |
24505 | @cindex @sc{gdb/mi}, data manipulation | |
24506 | This section describes the @sc{gdb/mi} commands that manipulate data: | |
24507 | examine memory and registers, evaluate expressions, etc. | |
24508 | ||
24509 | @c REMOVED FROM THE INTERFACE. | |
24510 | @c @subheading -data-assign | |
24511 | @c Change the value of a program variable. Plenty of side effects. | |
79a6e687 | 24512 | @c @subsubheading GDB Command |
a2c02241 NR |
24513 | @c set variable |
24514 | @c @subsubheading Example | |
24515 | @c N.A. | |
24516 | ||
24517 | @subheading The @code{-data-disassemble} Command | |
24518 | @findex -data-disassemble | |
922fbb7b AC |
24519 | |
24520 | @subsubheading Synopsis | |
24521 | ||
24522 | @smallexample | |
a2c02241 NR |
24523 | -data-disassemble |
24524 | [ -s @var{start-addr} -e @var{end-addr} ] | |
24525 | | [ -f @var{filename} -l @var{linenum} [ -n @var{lines} ] ] | |
24526 | -- @var{mode} | |
922fbb7b AC |
24527 | @end smallexample |
24528 | ||
a2c02241 NR |
24529 | @noindent |
24530 | Where: | |
24531 | ||
24532 | @table @samp | |
24533 | @item @var{start-addr} | |
24534 | is the beginning address (or @code{$pc}) | |
24535 | @item @var{end-addr} | |
24536 | is the end address | |
24537 | @item @var{filename} | |
24538 | is the name of the file to disassemble | |
24539 | @item @var{linenum} | |
24540 | is the line number to disassemble around | |
24541 | @item @var{lines} | |
d3e8051b | 24542 | is the number of disassembly lines to be produced. If it is -1, |
a2c02241 NR |
24543 | the whole function will be disassembled, in case no @var{end-addr} is |
24544 | specified. If @var{end-addr} is specified as a non-zero value, and | |
24545 | @var{lines} is lower than the number of disassembly lines between | |
24546 | @var{start-addr} and @var{end-addr}, only @var{lines} lines are | |
24547 | displayed; if @var{lines} is higher than the number of lines between | |
24548 | @var{start-addr} and @var{end-addr}, only the lines up to @var{end-addr} | |
24549 | are displayed. | |
24550 | @item @var{mode} | |
24551 | is either 0 (meaning only disassembly) or 1 (meaning mixed source and | |
24552 | disassembly). | |
24553 | @end table | |
24554 | ||
24555 | @subsubheading Result | |
24556 | ||
24557 | The output for each instruction is composed of four fields: | |
24558 | ||
24559 | @itemize @bullet | |
24560 | @item Address | |
24561 | @item Func-name | |
24562 | @item Offset | |
24563 | @item Instruction | |
24564 | @end itemize | |
24565 | ||
24566 | Note that whatever included in the instruction field, is not manipulated | |
d3e8051b | 24567 | directly by @sc{gdb/mi}, i.e., it is not possible to adjust its format. |
922fbb7b AC |
24568 | |
24569 | @subsubheading @value{GDBN} Command | |
24570 | ||
a2c02241 | 24571 | There's no direct mapping from this command to the CLI. |
922fbb7b AC |
24572 | |
24573 | @subsubheading Example | |
24574 | ||
a2c02241 NR |
24575 | Disassemble from the current value of @code{$pc} to @code{$pc + 20}: |
24576 | ||
922fbb7b | 24577 | @smallexample |
594fe323 | 24578 | (gdb) |
a2c02241 NR |
24579 | -data-disassemble -s $pc -e "$pc + 20" -- 0 |
24580 | ^done, | |
24581 | asm_insns=[ | |
24582 | @{address="0x000107c0",func-name="main",offset="4", | |
24583 | inst="mov 2, %o0"@}, | |
24584 | @{address="0x000107c4",func-name="main",offset="8", | |
24585 | inst="sethi %hi(0x11800), %o2"@}, | |
24586 | @{address="0x000107c8",func-name="main",offset="12", | |
24587 | inst="or %o2, 0x140, %o1\t! 0x11940 <_lib_version+8>"@}, | |
24588 | @{address="0x000107cc",func-name="main",offset="16", | |
24589 | inst="sethi %hi(0x11800), %o2"@}, | |
24590 | @{address="0x000107d0",func-name="main",offset="20", | |
24591 | inst="or %o2, 0x168, %o4\t! 0x11968 <_lib_version+48>"@}] | |
594fe323 | 24592 | (gdb) |
a2c02241 NR |
24593 | @end smallexample |
24594 | ||
24595 | Disassemble the whole @code{main} function. Line 32 is part of | |
24596 | @code{main}. | |
24597 | ||
24598 | @smallexample | |
24599 | -data-disassemble -f basics.c -l 32 -- 0 | |
24600 | ^done,asm_insns=[ | |
24601 | @{address="0x000107bc",func-name="main",offset="0", | |
24602 | inst="save %sp, -112, %sp"@}, | |
24603 | @{address="0x000107c0",func-name="main",offset="4", | |
24604 | inst="mov 2, %o0"@}, | |
24605 | @{address="0x000107c4",func-name="main",offset="8", | |
24606 | inst="sethi %hi(0x11800), %o2"@}, | |
24607 | [@dots{}] | |
24608 | @{address="0x0001081c",func-name="main",offset="96",inst="ret "@}, | |
24609 | @{address="0x00010820",func-name="main",offset="100",inst="restore "@}] | |
594fe323 | 24610 | (gdb) |
922fbb7b AC |
24611 | @end smallexample |
24612 | ||
a2c02241 | 24613 | Disassemble 3 instructions from the start of @code{main}: |
922fbb7b | 24614 | |
a2c02241 | 24615 | @smallexample |
594fe323 | 24616 | (gdb) |
a2c02241 NR |
24617 | -data-disassemble -f basics.c -l 32 -n 3 -- 0 |
24618 | ^done,asm_insns=[ | |
24619 | @{address="0x000107bc",func-name="main",offset="0", | |
24620 | inst="save %sp, -112, %sp"@}, | |
24621 | @{address="0x000107c0",func-name="main",offset="4", | |
24622 | inst="mov 2, %o0"@}, | |
24623 | @{address="0x000107c4",func-name="main",offset="8", | |
24624 | inst="sethi %hi(0x11800), %o2"@}] | |
594fe323 | 24625 | (gdb) |
a2c02241 NR |
24626 | @end smallexample |
24627 | ||
24628 | Disassemble 3 instructions from the start of @code{main} in mixed mode: | |
24629 | ||
24630 | @smallexample | |
594fe323 | 24631 | (gdb) |
a2c02241 NR |
24632 | -data-disassemble -f basics.c -l 32 -n 3 -- 1 |
24633 | ^done,asm_insns=[ | |
24634 | src_and_asm_line=@{line="31", | |
24635 | file="/kwikemart/marge/ezannoni/flathead-dev/devo/gdb/ \ | |
24636 | testsuite/gdb.mi/basics.c",line_asm_insn=[ | |
24637 | @{address="0x000107bc",func-name="main",offset="0", | |
24638 | inst="save %sp, -112, %sp"@}]@}, | |
24639 | src_and_asm_line=@{line="32", | |
24640 | file="/kwikemart/marge/ezannoni/flathead-dev/devo/gdb/ \ | |
24641 | testsuite/gdb.mi/basics.c",line_asm_insn=[ | |
24642 | @{address="0x000107c0",func-name="main",offset="4", | |
24643 | inst="mov 2, %o0"@}, | |
24644 | @{address="0x000107c4",func-name="main",offset="8", | |
24645 | inst="sethi %hi(0x11800), %o2"@}]@}] | |
594fe323 | 24646 | (gdb) |
a2c02241 NR |
24647 | @end smallexample |
24648 | ||
24649 | ||
24650 | @subheading The @code{-data-evaluate-expression} Command | |
24651 | @findex -data-evaluate-expression | |
922fbb7b AC |
24652 | |
24653 | @subsubheading Synopsis | |
24654 | ||
24655 | @smallexample | |
a2c02241 | 24656 | -data-evaluate-expression @var{expr} |
922fbb7b AC |
24657 | @end smallexample |
24658 | ||
a2c02241 NR |
24659 | Evaluate @var{expr} as an expression. The expression could contain an |
24660 | inferior function call. The function call will execute synchronously. | |
24661 | If the expression contains spaces, it must be enclosed in double quotes. | |
922fbb7b AC |
24662 | |
24663 | @subsubheading @value{GDBN} Command | |
24664 | ||
a2c02241 NR |
24665 | The corresponding @value{GDBN} commands are @samp{print}, @samp{output}, and |
24666 | @samp{call}. In @code{gdbtk} only, there's a corresponding | |
24667 | @samp{gdb_eval} command. | |
922fbb7b AC |
24668 | |
24669 | @subsubheading Example | |
24670 | ||
a2c02241 NR |
24671 | In the following example, the numbers that precede the commands are the |
24672 | @dfn{tokens} described in @ref{GDB/MI Command Syntax, ,@sc{gdb/mi} | |
24673 | Command Syntax}. Notice how @sc{gdb/mi} returns the same tokens in its | |
24674 | output. | |
24675 | ||
922fbb7b | 24676 | @smallexample |
a2c02241 NR |
24677 | 211-data-evaluate-expression A |
24678 | 211^done,value="1" | |
594fe323 | 24679 | (gdb) |
a2c02241 NR |
24680 | 311-data-evaluate-expression &A |
24681 | 311^done,value="0xefffeb7c" | |
594fe323 | 24682 | (gdb) |
a2c02241 NR |
24683 | 411-data-evaluate-expression A+3 |
24684 | 411^done,value="4" | |
594fe323 | 24685 | (gdb) |
a2c02241 NR |
24686 | 511-data-evaluate-expression "A + 3" |
24687 | 511^done,value="4" | |
594fe323 | 24688 | (gdb) |
a2c02241 | 24689 | @end smallexample |
922fbb7b AC |
24690 | |
24691 | ||
a2c02241 NR |
24692 | @subheading The @code{-data-list-changed-registers} Command |
24693 | @findex -data-list-changed-registers | |
922fbb7b AC |
24694 | |
24695 | @subsubheading Synopsis | |
24696 | ||
24697 | @smallexample | |
a2c02241 | 24698 | -data-list-changed-registers |
922fbb7b AC |
24699 | @end smallexample |
24700 | ||
a2c02241 | 24701 | Display a list of the registers that have changed. |
922fbb7b AC |
24702 | |
24703 | @subsubheading @value{GDBN} Command | |
24704 | ||
a2c02241 NR |
24705 | @value{GDBN} doesn't have a direct analog for this command; @code{gdbtk} |
24706 | has the corresponding command @samp{gdb_changed_register_list}. | |
922fbb7b AC |
24707 | |
24708 | @subsubheading Example | |
922fbb7b | 24709 | |
a2c02241 | 24710 | On a PPC MBX board: |
922fbb7b AC |
24711 | |
24712 | @smallexample | |
594fe323 | 24713 | (gdb) |
a2c02241 NR |
24714 | -exec-continue |
24715 | ^running | |
922fbb7b | 24716 | |
594fe323 | 24717 | (gdb) |
a47ec5fe AR |
24718 | *stopped,reason="breakpoint-hit",disp="keep",bkptno="1",frame=@{ |
24719 | func="main",args=[],file="try.c",fullname="/home/foo/bar/try.c", | |
24720 | line="5"@} | |
594fe323 | 24721 | (gdb) |
a2c02241 NR |
24722 | -data-list-changed-registers |
24723 | ^done,changed-registers=["0","1","2","4","5","6","7","8","9", | |
24724 | "10","11","13","14","15","16","17","18","19","20","21","22","23", | |
24725 | "24","25","26","27","28","30","31","64","65","66","67","69"] | |
594fe323 | 24726 | (gdb) |
a2c02241 | 24727 | @end smallexample |
922fbb7b AC |
24728 | |
24729 | ||
a2c02241 NR |
24730 | @subheading The @code{-data-list-register-names} Command |
24731 | @findex -data-list-register-names | |
922fbb7b AC |
24732 | |
24733 | @subsubheading Synopsis | |
24734 | ||
24735 | @smallexample | |
a2c02241 | 24736 | -data-list-register-names [ ( @var{regno} )+ ] |
922fbb7b AC |
24737 | @end smallexample |
24738 | ||
a2c02241 NR |
24739 | Show a list of register names for the current target. If no arguments |
24740 | are given, it shows a list of the names of all the registers. If | |
24741 | integer numbers are given as arguments, it will print a list of the | |
24742 | names of the registers corresponding to the arguments. To ensure | |
24743 | consistency between a register name and its number, the output list may | |
24744 | include empty register names. | |
922fbb7b AC |
24745 | |
24746 | @subsubheading @value{GDBN} Command | |
24747 | ||
a2c02241 NR |
24748 | @value{GDBN} does not have a command which corresponds to |
24749 | @samp{-data-list-register-names}. In @code{gdbtk} there is a | |
24750 | corresponding command @samp{gdb_regnames}. | |
922fbb7b AC |
24751 | |
24752 | @subsubheading Example | |
922fbb7b | 24753 | |
a2c02241 NR |
24754 | For the PPC MBX board: |
24755 | @smallexample | |
594fe323 | 24756 | (gdb) |
a2c02241 NR |
24757 | -data-list-register-names |
24758 | ^done,register-names=["r0","r1","r2","r3","r4","r5","r6","r7", | |
24759 | "r8","r9","r10","r11","r12","r13","r14","r15","r16","r17","r18", | |
24760 | "r19","r20","r21","r22","r23","r24","r25","r26","r27","r28","r29", | |
24761 | "r30","r31","f0","f1","f2","f3","f4","f5","f6","f7","f8","f9", | |
24762 | "f10","f11","f12","f13","f14","f15","f16","f17","f18","f19","f20", | |
24763 | "f21","f22","f23","f24","f25","f26","f27","f28","f29","f30","f31", | |
24764 | "", "pc","ps","cr","lr","ctr","xer"] | |
594fe323 | 24765 | (gdb) |
a2c02241 NR |
24766 | -data-list-register-names 1 2 3 |
24767 | ^done,register-names=["r1","r2","r3"] | |
594fe323 | 24768 | (gdb) |
a2c02241 | 24769 | @end smallexample |
922fbb7b | 24770 | |
a2c02241 NR |
24771 | @subheading The @code{-data-list-register-values} Command |
24772 | @findex -data-list-register-values | |
922fbb7b AC |
24773 | |
24774 | @subsubheading Synopsis | |
24775 | ||
24776 | @smallexample | |
a2c02241 | 24777 | -data-list-register-values @var{fmt} [ ( @var{regno} )*] |
922fbb7b AC |
24778 | @end smallexample |
24779 | ||
a2c02241 NR |
24780 | Display the registers' contents. @var{fmt} is the format according to |
24781 | which the registers' contents are to be returned, followed by an optional | |
24782 | list of numbers specifying the registers to display. A missing list of | |
24783 | numbers indicates that the contents of all the registers must be returned. | |
24784 | ||
24785 | Allowed formats for @var{fmt} are: | |
24786 | ||
24787 | @table @code | |
24788 | @item x | |
24789 | Hexadecimal | |
24790 | @item o | |
24791 | Octal | |
24792 | @item t | |
24793 | Binary | |
24794 | @item d | |
24795 | Decimal | |
24796 | @item r | |
24797 | Raw | |
24798 | @item N | |
24799 | Natural | |
24800 | @end table | |
922fbb7b AC |
24801 | |
24802 | @subsubheading @value{GDBN} Command | |
24803 | ||
a2c02241 NR |
24804 | The corresponding @value{GDBN} commands are @samp{info reg}, @samp{info |
24805 | all-reg}, and (in @code{gdbtk}) @samp{gdb_fetch_registers}. | |
922fbb7b AC |
24806 | |
24807 | @subsubheading Example | |
922fbb7b | 24808 | |
a2c02241 NR |
24809 | For a PPC MBX board (note: line breaks are for readability only, they |
24810 | don't appear in the actual output): | |
24811 | ||
24812 | @smallexample | |
594fe323 | 24813 | (gdb) |
a2c02241 NR |
24814 | -data-list-register-values r 64 65 |
24815 | ^done,register-values=[@{number="64",value="0xfe00a300"@}, | |
24816 | @{number="65",value="0x00029002"@}] | |
594fe323 | 24817 | (gdb) |
a2c02241 NR |
24818 | -data-list-register-values x |
24819 | ^done,register-values=[@{number="0",value="0xfe0043c8"@}, | |
24820 | @{number="1",value="0x3fff88"@},@{number="2",value="0xfffffffe"@}, | |
24821 | @{number="3",value="0x0"@},@{number="4",value="0xa"@}, | |
24822 | @{number="5",value="0x3fff68"@},@{number="6",value="0x3fff58"@}, | |
24823 | @{number="7",value="0xfe011e98"@},@{number="8",value="0x2"@}, | |
24824 | @{number="9",value="0xfa202820"@},@{number="10",value="0xfa202808"@}, | |
24825 | @{number="11",value="0x1"@},@{number="12",value="0x0"@}, | |
24826 | @{number="13",value="0x4544"@},@{number="14",value="0xffdfffff"@}, | |
24827 | @{number="15",value="0xffffffff"@},@{number="16",value="0xfffffeff"@}, | |
24828 | @{number="17",value="0xefffffed"@},@{number="18",value="0xfffffffe"@}, | |
24829 | @{number="19",value="0xffffffff"@},@{number="20",value="0xffffffff"@}, | |
24830 | @{number="21",value="0xffffffff"@},@{number="22",value="0xfffffff7"@}, | |
24831 | @{number="23",value="0xffffffff"@},@{number="24",value="0xffffffff"@}, | |
24832 | @{number="25",value="0xffffffff"@},@{number="26",value="0xfffffffb"@}, | |
24833 | @{number="27",value="0xffffffff"@},@{number="28",value="0xf7bfffff"@}, | |
24834 | @{number="29",value="0x0"@},@{number="30",value="0xfe010000"@}, | |
24835 | @{number="31",value="0x0"@},@{number="32",value="0x0"@}, | |
24836 | @{number="33",value="0x0"@},@{number="34",value="0x0"@}, | |
24837 | @{number="35",value="0x0"@},@{number="36",value="0x0"@}, | |
24838 | @{number="37",value="0x0"@},@{number="38",value="0x0"@}, | |
24839 | @{number="39",value="0x0"@},@{number="40",value="0x0"@}, | |
24840 | @{number="41",value="0x0"@},@{number="42",value="0x0"@}, | |
24841 | @{number="43",value="0x0"@},@{number="44",value="0x0"@}, | |
24842 | @{number="45",value="0x0"@},@{number="46",value="0x0"@}, | |
24843 | @{number="47",value="0x0"@},@{number="48",value="0x0"@}, | |
24844 | @{number="49",value="0x0"@},@{number="50",value="0x0"@}, | |
24845 | @{number="51",value="0x0"@},@{number="52",value="0x0"@}, | |
24846 | @{number="53",value="0x0"@},@{number="54",value="0x0"@}, | |
24847 | @{number="55",value="0x0"@},@{number="56",value="0x0"@}, | |
24848 | @{number="57",value="0x0"@},@{number="58",value="0x0"@}, | |
24849 | @{number="59",value="0x0"@},@{number="60",value="0x0"@}, | |
24850 | @{number="61",value="0x0"@},@{number="62",value="0x0"@}, | |
24851 | @{number="63",value="0x0"@},@{number="64",value="0xfe00a300"@}, | |
24852 | @{number="65",value="0x29002"@},@{number="66",value="0x202f04b5"@}, | |
24853 | @{number="67",value="0xfe0043b0"@},@{number="68",value="0xfe00b3e4"@}, | |
24854 | @{number="69",value="0x20002b03"@}] | |
594fe323 | 24855 | (gdb) |
a2c02241 | 24856 | @end smallexample |
922fbb7b | 24857 | |
a2c02241 NR |
24858 | |
24859 | @subheading The @code{-data-read-memory} Command | |
24860 | @findex -data-read-memory | |
922fbb7b AC |
24861 | |
24862 | @subsubheading Synopsis | |
24863 | ||
24864 | @smallexample | |
a2c02241 NR |
24865 | -data-read-memory [ -o @var{byte-offset} ] |
24866 | @var{address} @var{word-format} @var{word-size} | |
24867 | @var{nr-rows} @var{nr-cols} [ @var{aschar} ] | |
922fbb7b AC |
24868 | @end smallexample |
24869 | ||
a2c02241 NR |
24870 | @noindent |
24871 | where: | |
922fbb7b | 24872 | |
a2c02241 NR |
24873 | @table @samp |
24874 | @item @var{address} | |
24875 | An expression specifying the address of the first memory word to be | |
24876 | read. Complex expressions containing embedded white space should be | |
24877 | quoted using the C convention. | |
922fbb7b | 24878 | |
a2c02241 NR |
24879 | @item @var{word-format} |
24880 | The format to be used to print the memory words. The notation is the | |
24881 | same as for @value{GDBN}'s @code{print} command (@pxref{Output Formats, | |
79a6e687 | 24882 | ,Output Formats}). |
922fbb7b | 24883 | |
a2c02241 NR |
24884 | @item @var{word-size} |
24885 | The size of each memory word in bytes. | |
922fbb7b | 24886 | |
a2c02241 NR |
24887 | @item @var{nr-rows} |
24888 | The number of rows in the output table. | |
922fbb7b | 24889 | |
a2c02241 NR |
24890 | @item @var{nr-cols} |
24891 | The number of columns in the output table. | |
922fbb7b | 24892 | |
a2c02241 NR |
24893 | @item @var{aschar} |
24894 | If present, indicates that each row should include an @sc{ascii} dump. The | |
24895 | value of @var{aschar} is used as a padding character when a byte is not a | |
24896 | member of the printable @sc{ascii} character set (printable @sc{ascii} | |
24897 | characters are those whose code is between 32 and 126, inclusively). | |
922fbb7b | 24898 | |
a2c02241 NR |
24899 | @item @var{byte-offset} |
24900 | An offset to add to the @var{address} before fetching memory. | |
24901 | @end table | |
922fbb7b | 24902 | |
a2c02241 NR |
24903 | This command displays memory contents as a table of @var{nr-rows} by |
24904 | @var{nr-cols} words, each word being @var{word-size} bytes. In total, | |
24905 | @code{@var{nr-rows} * @var{nr-cols} * @var{word-size}} bytes are read | |
24906 | (returned as @samp{total-bytes}). Should less than the requested number | |
24907 | of bytes be returned by the target, the missing words are identified | |
24908 | using @samp{N/A}. The number of bytes read from the target is returned | |
24909 | in @samp{nr-bytes} and the starting address used to read memory in | |
24910 | @samp{addr}. | |
24911 | ||
24912 | The address of the next/previous row or page is available in | |
24913 | @samp{next-row} and @samp{prev-row}, @samp{next-page} and | |
24914 | @samp{prev-page}. | |
922fbb7b AC |
24915 | |
24916 | @subsubheading @value{GDBN} Command | |
24917 | ||
a2c02241 NR |
24918 | The corresponding @value{GDBN} command is @samp{x}. @code{gdbtk} has |
24919 | @samp{gdb_get_mem} memory read command. | |
922fbb7b AC |
24920 | |
24921 | @subsubheading Example | |
32e7087d | 24922 | |
a2c02241 NR |
24923 | Read six bytes of memory starting at @code{bytes+6} but then offset by |
24924 | @code{-6} bytes. Format as three rows of two columns. One byte per | |
24925 | word. Display each word in hex. | |
32e7087d JB |
24926 | |
24927 | @smallexample | |
594fe323 | 24928 | (gdb) |
a2c02241 NR |
24929 | 9-data-read-memory -o -6 -- bytes+6 x 1 3 2 |
24930 | 9^done,addr="0x00001390",nr-bytes="6",total-bytes="6", | |
24931 | next-row="0x00001396",prev-row="0x0000138e",next-page="0x00001396", | |
24932 | prev-page="0x0000138a",memory=[ | |
24933 | @{addr="0x00001390",data=["0x00","0x01"]@}, | |
24934 | @{addr="0x00001392",data=["0x02","0x03"]@}, | |
24935 | @{addr="0x00001394",data=["0x04","0x05"]@}] | |
594fe323 | 24936 | (gdb) |
32e7087d JB |
24937 | @end smallexample |
24938 | ||
a2c02241 NR |
24939 | Read two bytes of memory starting at address @code{shorts + 64} and |
24940 | display as a single word formatted in decimal. | |
32e7087d | 24941 | |
32e7087d | 24942 | @smallexample |
594fe323 | 24943 | (gdb) |
a2c02241 NR |
24944 | 5-data-read-memory shorts+64 d 2 1 1 |
24945 | 5^done,addr="0x00001510",nr-bytes="2",total-bytes="2", | |
24946 | next-row="0x00001512",prev-row="0x0000150e", | |
24947 | next-page="0x00001512",prev-page="0x0000150e",memory=[ | |
24948 | @{addr="0x00001510",data=["128"]@}] | |
594fe323 | 24949 | (gdb) |
32e7087d JB |
24950 | @end smallexample |
24951 | ||
a2c02241 NR |
24952 | Read thirty two bytes of memory starting at @code{bytes+16} and format |
24953 | as eight rows of four columns. Include a string encoding with @samp{x} | |
24954 | used as the non-printable character. | |
922fbb7b AC |
24955 | |
24956 | @smallexample | |
594fe323 | 24957 | (gdb) |
a2c02241 NR |
24958 | 4-data-read-memory bytes+16 x 1 8 4 x |
24959 | 4^done,addr="0x000013a0",nr-bytes="32",total-bytes="32", | |
24960 | next-row="0x000013c0",prev-row="0x0000139c", | |
24961 | next-page="0x000013c0",prev-page="0x00001380",memory=[ | |
24962 | @{addr="0x000013a0",data=["0x10","0x11","0x12","0x13"],ascii="xxxx"@}, | |
24963 | @{addr="0x000013a4",data=["0x14","0x15","0x16","0x17"],ascii="xxxx"@}, | |
24964 | @{addr="0x000013a8",data=["0x18","0x19","0x1a","0x1b"],ascii="xxxx"@}, | |
24965 | @{addr="0x000013ac",data=["0x1c","0x1d","0x1e","0x1f"],ascii="xxxx"@}, | |
24966 | @{addr="0x000013b0",data=["0x20","0x21","0x22","0x23"],ascii=" !\"#"@}, | |
24967 | @{addr="0x000013b4",data=["0x24","0x25","0x26","0x27"],ascii="$%&'"@}, | |
24968 | @{addr="0x000013b8",data=["0x28","0x29","0x2a","0x2b"],ascii="()*+"@}, | |
24969 | @{addr="0x000013bc",data=["0x2c","0x2d","0x2e","0x2f"],ascii=",-./"@}] | |
594fe323 | 24970 | (gdb) |
922fbb7b AC |
24971 | @end smallexample |
24972 | ||
a2c02241 NR |
24973 | @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% |
24974 | @node GDB/MI Tracepoint Commands | |
24975 | @section @sc{gdb/mi} Tracepoint Commands | |
922fbb7b | 24976 | |
a2c02241 | 24977 | The tracepoint commands are not yet implemented. |
922fbb7b | 24978 | |
a2c02241 | 24979 | @c @subheading -trace-actions |
922fbb7b | 24980 | |
a2c02241 | 24981 | @c @subheading -trace-delete |
922fbb7b | 24982 | |
a2c02241 | 24983 | @c @subheading -trace-disable |
922fbb7b | 24984 | |
a2c02241 | 24985 | @c @subheading -trace-dump |
922fbb7b | 24986 | |
a2c02241 | 24987 | @c @subheading -trace-enable |
922fbb7b | 24988 | |
a2c02241 | 24989 | @c @subheading -trace-exists |
922fbb7b | 24990 | |
a2c02241 | 24991 | @c @subheading -trace-find |
922fbb7b | 24992 | |
a2c02241 | 24993 | @c @subheading -trace-frame-number |
922fbb7b | 24994 | |
a2c02241 | 24995 | @c @subheading -trace-info |
922fbb7b | 24996 | |
a2c02241 | 24997 | @c @subheading -trace-insert |
922fbb7b | 24998 | |
a2c02241 | 24999 | @c @subheading -trace-list |
922fbb7b | 25000 | |
a2c02241 | 25001 | @c @subheading -trace-pass-count |
922fbb7b | 25002 | |
a2c02241 | 25003 | @c @subheading -trace-save |
922fbb7b | 25004 | |
a2c02241 | 25005 | @c @subheading -trace-start |
922fbb7b | 25006 | |
a2c02241 | 25007 | @c @subheading -trace-stop |
922fbb7b | 25008 | |
922fbb7b | 25009 | |
a2c02241 NR |
25010 | @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% |
25011 | @node GDB/MI Symbol Query | |
25012 | @section @sc{gdb/mi} Symbol Query Commands | |
922fbb7b AC |
25013 | |
25014 | ||
9901a55b | 25015 | @ignore |
a2c02241 NR |
25016 | @subheading The @code{-symbol-info-address} Command |
25017 | @findex -symbol-info-address | |
922fbb7b AC |
25018 | |
25019 | @subsubheading Synopsis | |
25020 | ||
25021 | @smallexample | |
a2c02241 | 25022 | -symbol-info-address @var{symbol} |
922fbb7b AC |
25023 | @end smallexample |
25024 | ||
a2c02241 | 25025 | Describe where @var{symbol} is stored. |
922fbb7b AC |
25026 | |
25027 | @subsubheading @value{GDBN} Command | |
25028 | ||
a2c02241 | 25029 | The corresponding @value{GDBN} command is @samp{info address}. |
922fbb7b AC |
25030 | |
25031 | @subsubheading Example | |
25032 | N.A. | |
25033 | ||
25034 | ||
a2c02241 NR |
25035 | @subheading The @code{-symbol-info-file} Command |
25036 | @findex -symbol-info-file | |
922fbb7b AC |
25037 | |
25038 | @subsubheading Synopsis | |
25039 | ||
25040 | @smallexample | |
a2c02241 | 25041 | -symbol-info-file |
922fbb7b AC |
25042 | @end smallexample |
25043 | ||
a2c02241 | 25044 | Show the file for the symbol. |
922fbb7b | 25045 | |
a2c02241 | 25046 | @subsubheading @value{GDBN} Command |
922fbb7b | 25047 | |
a2c02241 NR |
25048 | There's no equivalent @value{GDBN} command. @code{gdbtk} has |
25049 | @samp{gdb_find_file}. | |
922fbb7b AC |
25050 | |
25051 | @subsubheading Example | |
25052 | N.A. | |
25053 | ||
25054 | ||
a2c02241 NR |
25055 | @subheading The @code{-symbol-info-function} Command |
25056 | @findex -symbol-info-function | |
922fbb7b AC |
25057 | |
25058 | @subsubheading Synopsis | |
25059 | ||
25060 | @smallexample | |
a2c02241 | 25061 | -symbol-info-function |
922fbb7b AC |
25062 | @end smallexample |
25063 | ||
a2c02241 | 25064 | Show which function the symbol lives in. |
922fbb7b AC |
25065 | |
25066 | @subsubheading @value{GDBN} Command | |
25067 | ||
a2c02241 | 25068 | @samp{gdb_get_function} in @code{gdbtk}. |
922fbb7b AC |
25069 | |
25070 | @subsubheading Example | |
25071 | N.A. | |
25072 | ||
25073 | ||
a2c02241 NR |
25074 | @subheading The @code{-symbol-info-line} Command |
25075 | @findex -symbol-info-line | |
922fbb7b AC |
25076 | |
25077 | @subsubheading Synopsis | |
25078 | ||
25079 | @smallexample | |
a2c02241 | 25080 | -symbol-info-line |
922fbb7b AC |
25081 | @end smallexample |
25082 | ||
a2c02241 | 25083 | Show the core addresses of the code for a source line. |
922fbb7b | 25084 | |
a2c02241 | 25085 | @subsubheading @value{GDBN} Command |
922fbb7b | 25086 | |
a2c02241 NR |
25087 | The corresponding @value{GDBN} command is @samp{info line}. |
25088 | @code{gdbtk} has the @samp{gdb_get_line} and @samp{gdb_get_file} commands. | |
922fbb7b AC |
25089 | |
25090 | @subsubheading Example | |
a2c02241 | 25091 | N.A. |
922fbb7b AC |
25092 | |
25093 | ||
a2c02241 NR |
25094 | @subheading The @code{-symbol-info-symbol} Command |
25095 | @findex -symbol-info-symbol | |
07f31aa6 DJ |
25096 | |
25097 | @subsubheading Synopsis | |
25098 | ||
a2c02241 NR |
25099 | @smallexample |
25100 | -symbol-info-symbol @var{addr} | |
25101 | @end smallexample | |
07f31aa6 | 25102 | |
a2c02241 | 25103 | Describe what symbol is at location @var{addr}. |
07f31aa6 | 25104 | |
a2c02241 | 25105 | @subsubheading @value{GDBN} Command |
07f31aa6 | 25106 | |
a2c02241 | 25107 | The corresponding @value{GDBN} command is @samp{info symbol}. |
07f31aa6 DJ |
25108 | |
25109 | @subsubheading Example | |
a2c02241 | 25110 | N.A. |
07f31aa6 DJ |
25111 | |
25112 | ||
a2c02241 NR |
25113 | @subheading The @code{-symbol-list-functions} Command |
25114 | @findex -symbol-list-functions | |
922fbb7b AC |
25115 | |
25116 | @subsubheading Synopsis | |
25117 | ||
25118 | @smallexample | |
a2c02241 | 25119 | -symbol-list-functions |
922fbb7b AC |
25120 | @end smallexample |
25121 | ||
a2c02241 | 25122 | List the functions in the executable. |
922fbb7b AC |
25123 | |
25124 | @subsubheading @value{GDBN} Command | |
25125 | ||
a2c02241 NR |
25126 | @samp{info functions} in @value{GDBN}, @samp{gdb_listfunc} and |
25127 | @samp{gdb_search} in @code{gdbtk}. | |
922fbb7b AC |
25128 | |
25129 | @subsubheading Example | |
a2c02241 | 25130 | N.A. |
9901a55b | 25131 | @end ignore |
922fbb7b AC |
25132 | |
25133 | ||
a2c02241 NR |
25134 | @subheading The @code{-symbol-list-lines} Command |
25135 | @findex -symbol-list-lines | |
922fbb7b AC |
25136 | |
25137 | @subsubheading Synopsis | |
25138 | ||
25139 | @smallexample | |
a2c02241 | 25140 | -symbol-list-lines @var{filename} |
922fbb7b AC |
25141 | @end smallexample |
25142 | ||
a2c02241 NR |
25143 | Print the list of lines that contain code and their associated program |
25144 | addresses for the given source filename. The entries are sorted in | |
25145 | ascending PC order. | |
922fbb7b AC |
25146 | |
25147 | @subsubheading @value{GDBN} Command | |
25148 | ||
a2c02241 | 25149 | There is no corresponding @value{GDBN} command. |
922fbb7b AC |
25150 | |
25151 | @subsubheading Example | |
a2c02241 | 25152 | @smallexample |
594fe323 | 25153 | (gdb) |
a2c02241 NR |
25154 | -symbol-list-lines basics.c |
25155 | ^done,lines=[@{pc="0x08048554",line="7"@},@{pc="0x0804855a",line="8"@}] | |
594fe323 | 25156 | (gdb) |
a2c02241 | 25157 | @end smallexample |
922fbb7b AC |
25158 | |
25159 | ||
9901a55b | 25160 | @ignore |
a2c02241 NR |
25161 | @subheading The @code{-symbol-list-types} Command |
25162 | @findex -symbol-list-types | |
922fbb7b AC |
25163 | |
25164 | @subsubheading Synopsis | |
25165 | ||
25166 | @smallexample | |
a2c02241 | 25167 | -symbol-list-types |
922fbb7b AC |
25168 | @end smallexample |
25169 | ||
a2c02241 | 25170 | List all the type names. |
922fbb7b AC |
25171 | |
25172 | @subsubheading @value{GDBN} Command | |
25173 | ||
a2c02241 NR |
25174 | The corresponding commands are @samp{info types} in @value{GDBN}, |
25175 | @samp{gdb_search} in @code{gdbtk}. | |
922fbb7b AC |
25176 | |
25177 | @subsubheading Example | |
25178 | N.A. | |
25179 | ||
25180 | ||
a2c02241 NR |
25181 | @subheading The @code{-symbol-list-variables} Command |
25182 | @findex -symbol-list-variables | |
922fbb7b AC |
25183 | |
25184 | @subsubheading Synopsis | |
25185 | ||
25186 | @smallexample | |
a2c02241 | 25187 | -symbol-list-variables |
922fbb7b AC |
25188 | @end smallexample |
25189 | ||
a2c02241 | 25190 | List all the global and static variable names. |
922fbb7b AC |
25191 | |
25192 | @subsubheading @value{GDBN} Command | |
25193 | ||
a2c02241 | 25194 | @samp{info variables} in @value{GDBN}, @samp{gdb_search} in @code{gdbtk}. |
922fbb7b AC |
25195 | |
25196 | @subsubheading Example | |
25197 | N.A. | |
25198 | ||
25199 | ||
a2c02241 NR |
25200 | @subheading The @code{-symbol-locate} Command |
25201 | @findex -symbol-locate | |
922fbb7b AC |
25202 | |
25203 | @subsubheading Synopsis | |
25204 | ||
25205 | @smallexample | |
a2c02241 | 25206 | -symbol-locate |
922fbb7b AC |
25207 | @end smallexample |
25208 | ||
922fbb7b AC |
25209 | @subsubheading @value{GDBN} Command |
25210 | ||
a2c02241 | 25211 | @samp{gdb_loc} in @code{gdbtk}. |
922fbb7b AC |
25212 | |
25213 | @subsubheading Example | |
25214 | N.A. | |
25215 | ||
25216 | ||
a2c02241 NR |
25217 | @subheading The @code{-symbol-type} Command |
25218 | @findex -symbol-type | |
922fbb7b AC |
25219 | |
25220 | @subsubheading Synopsis | |
25221 | ||
25222 | @smallexample | |
a2c02241 | 25223 | -symbol-type @var{variable} |
922fbb7b AC |
25224 | @end smallexample |
25225 | ||
a2c02241 | 25226 | Show type of @var{variable}. |
922fbb7b | 25227 | |
a2c02241 | 25228 | @subsubheading @value{GDBN} Command |
922fbb7b | 25229 | |
a2c02241 NR |
25230 | The corresponding @value{GDBN} command is @samp{ptype}, @code{gdbtk} has |
25231 | @samp{gdb_obj_variable}. | |
25232 | ||
25233 | @subsubheading Example | |
25234 | N.A. | |
9901a55b | 25235 | @end ignore |
a2c02241 NR |
25236 | |
25237 | ||
25238 | @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% | |
25239 | @node GDB/MI File Commands | |
25240 | @section @sc{gdb/mi} File Commands | |
25241 | ||
25242 | This section describes the GDB/MI commands to specify executable file names | |
25243 | and to read in and obtain symbol table information. | |
25244 | ||
25245 | @subheading The @code{-file-exec-and-symbols} Command | |
25246 | @findex -file-exec-and-symbols | |
25247 | ||
25248 | @subsubheading Synopsis | |
922fbb7b AC |
25249 | |
25250 | @smallexample | |
a2c02241 | 25251 | -file-exec-and-symbols @var{file} |
922fbb7b AC |
25252 | @end smallexample |
25253 | ||
a2c02241 NR |
25254 | Specify the executable file to be debugged. This file is the one from |
25255 | which the symbol table is also read. If no file is specified, the | |
25256 | command clears the executable and symbol information. If breakpoints | |
25257 | are set when using this command with no arguments, @value{GDBN} will produce | |
25258 | error messages. Otherwise, no output is produced, except a completion | |
25259 | notification. | |
25260 | ||
922fbb7b AC |
25261 | @subsubheading @value{GDBN} Command |
25262 | ||
a2c02241 | 25263 | The corresponding @value{GDBN} command is @samp{file}. |
922fbb7b AC |
25264 | |
25265 | @subsubheading Example | |
25266 | ||
25267 | @smallexample | |
594fe323 | 25268 | (gdb) |
a2c02241 NR |
25269 | -file-exec-and-symbols /kwikemart/marge/ezannoni/TRUNK/mbx/hello.mbx |
25270 | ^done | |
594fe323 | 25271 | (gdb) |
922fbb7b AC |
25272 | @end smallexample |
25273 | ||
922fbb7b | 25274 | |
a2c02241 NR |
25275 | @subheading The @code{-file-exec-file} Command |
25276 | @findex -file-exec-file | |
922fbb7b AC |
25277 | |
25278 | @subsubheading Synopsis | |
25279 | ||
25280 | @smallexample | |
a2c02241 | 25281 | -file-exec-file @var{file} |
922fbb7b AC |
25282 | @end smallexample |
25283 | ||
a2c02241 NR |
25284 | Specify the executable file to be debugged. Unlike |
25285 | @samp{-file-exec-and-symbols}, the symbol table is @emph{not} read | |
25286 | from this file. If used without argument, @value{GDBN} clears the information | |
25287 | about the executable file. No output is produced, except a completion | |
25288 | notification. | |
922fbb7b | 25289 | |
a2c02241 NR |
25290 | @subsubheading @value{GDBN} Command |
25291 | ||
25292 | The corresponding @value{GDBN} command is @samp{exec-file}. | |
922fbb7b AC |
25293 | |
25294 | @subsubheading Example | |
a2c02241 NR |
25295 | |
25296 | @smallexample | |
594fe323 | 25297 | (gdb) |
a2c02241 NR |
25298 | -file-exec-file /kwikemart/marge/ezannoni/TRUNK/mbx/hello.mbx |
25299 | ^done | |
594fe323 | 25300 | (gdb) |
a2c02241 | 25301 | @end smallexample |
922fbb7b AC |
25302 | |
25303 | ||
9901a55b | 25304 | @ignore |
a2c02241 NR |
25305 | @subheading The @code{-file-list-exec-sections} Command |
25306 | @findex -file-list-exec-sections | |
922fbb7b AC |
25307 | |
25308 | @subsubheading Synopsis | |
25309 | ||
25310 | @smallexample | |
a2c02241 | 25311 | -file-list-exec-sections |
922fbb7b AC |
25312 | @end smallexample |
25313 | ||
a2c02241 NR |
25314 | List the sections of the current executable file. |
25315 | ||
922fbb7b AC |
25316 | @subsubheading @value{GDBN} Command |
25317 | ||
a2c02241 NR |
25318 | The @value{GDBN} command @samp{info file} shows, among the rest, the same |
25319 | information as this command. @code{gdbtk} has a corresponding command | |
25320 | @samp{gdb_load_info}. | |
922fbb7b AC |
25321 | |
25322 | @subsubheading Example | |
25323 | N.A. | |
9901a55b | 25324 | @end ignore |
922fbb7b AC |
25325 | |
25326 | ||
a2c02241 NR |
25327 | @subheading The @code{-file-list-exec-source-file} Command |
25328 | @findex -file-list-exec-source-file | |
922fbb7b AC |
25329 | |
25330 | @subsubheading Synopsis | |
25331 | ||
25332 | @smallexample | |
a2c02241 | 25333 | -file-list-exec-source-file |
922fbb7b AC |
25334 | @end smallexample |
25335 | ||
a2c02241 | 25336 | List the line number, the current source file, and the absolute path |
44288b44 NR |
25337 | to the current source file for the current executable. The macro |
25338 | information field has a value of @samp{1} or @samp{0} depending on | |
25339 | whether or not the file includes preprocessor macro information. | |
922fbb7b AC |
25340 | |
25341 | @subsubheading @value{GDBN} Command | |
25342 | ||
a2c02241 | 25343 | The @value{GDBN} equivalent is @samp{info source} |
922fbb7b AC |
25344 | |
25345 | @subsubheading Example | |
25346 | ||
922fbb7b | 25347 | @smallexample |
594fe323 | 25348 | (gdb) |
a2c02241 | 25349 | 123-file-list-exec-source-file |
44288b44 | 25350 | 123^done,line="1",file="foo.c",fullname="/home/bar/foo.c,macro-info="1" |
594fe323 | 25351 | (gdb) |
922fbb7b AC |
25352 | @end smallexample |
25353 | ||
25354 | ||
a2c02241 NR |
25355 | @subheading The @code{-file-list-exec-source-files} Command |
25356 | @findex -file-list-exec-source-files | |
922fbb7b AC |
25357 | |
25358 | @subsubheading Synopsis | |
25359 | ||
25360 | @smallexample | |
a2c02241 | 25361 | -file-list-exec-source-files |
922fbb7b AC |
25362 | @end smallexample |
25363 | ||
a2c02241 NR |
25364 | List the source files for the current executable. |
25365 | ||
3f94c067 BW |
25366 | It will always output the filename, but only when @value{GDBN} can find |
25367 | the absolute file name of a source file, will it output the fullname. | |
922fbb7b AC |
25368 | |
25369 | @subsubheading @value{GDBN} Command | |
25370 | ||
a2c02241 NR |
25371 | The @value{GDBN} equivalent is @samp{info sources}. |
25372 | @code{gdbtk} has an analogous command @samp{gdb_listfiles}. | |
922fbb7b AC |
25373 | |
25374 | @subsubheading Example | |
922fbb7b | 25375 | @smallexample |
594fe323 | 25376 | (gdb) |
a2c02241 NR |
25377 | -file-list-exec-source-files |
25378 | ^done,files=[ | |
25379 | @{file=foo.c,fullname=/home/foo.c@}, | |
25380 | @{file=/home/bar.c,fullname=/home/bar.c@}, | |
25381 | @{file=gdb_could_not_find_fullpath.c@}] | |
594fe323 | 25382 | (gdb) |
922fbb7b AC |
25383 | @end smallexample |
25384 | ||
9901a55b | 25385 | @ignore |
a2c02241 NR |
25386 | @subheading The @code{-file-list-shared-libraries} Command |
25387 | @findex -file-list-shared-libraries | |
922fbb7b | 25388 | |
a2c02241 | 25389 | @subsubheading Synopsis |
922fbb7b | 25390 | |
a2c02241 NR |
25391 | @smallexample |
25392 | -file-list-shared-libraries | |
25393 | @end smallexample | |
922fbb7b | 25394 | |
a2c02241 | 25395 | List the shared libraries in the program. |
922fbb7b | 25396 | |
a2c02241 | 25397 | @subsubheading @value{GDBN} Command |
922fbb7b | 25398 | |
a2c02241 | 25399 | The corresponding @value{GDBN} command is @samp{info shared}. |
922fbb7b | 25400 | |
a2c02241 NR |
25401 | @subsubheading Example |
25402 | N.A. | |
922fbb7b AC |
25403 | |
25404 | ||
a2c02241 NR |
25405 | @subheading The @code{-file-list-symbol-files} Command |
25406 | @findex -file-list-symbol-files | |
922fbb7b | 25407 | |
a2c02241 | 25408 | @subsubheading Synopsis |
922fbb7b | 25409 | |
a2c02241 NR |
25410 | @smallexample |
25411 | -file-list-symbol-files | |
25412 | @end smallexample | |
922fbb7b | 25413 | |
a2c02241 | 25414 | List symbol files. |
922fbb7b | 25415 | |
a2c02241 | 25416 | @subsubheading @value{GDBN} Command |
922fbb7b | 25417 | |
a2c02241 | 25418 | The corresponding @value{GDBN} command is @samp{info file} (part of it). |
922fbb7b | 25419 | |
a2c02241 NR |
25420 | @subsubheading Example |
25421 | N.A. | |
9901a55b | 25422 | @end ignore |
922fbb7b | 25423 | |
922fbb7b | 25424 | |
a2c02241 NR |
25425 | @subheading The @code{-file-symbol-file} Command |
25426 | @findex -file-symbol-file | |
922fbb7b | 25427 | |
a2c02241 | 25428 | @subsubheading Synopsis |
922fbb7b | 25429 | |
a2c02241 NR |
25430 | @smallexample |
25431 | -file-symbol-file @var{file} | |
25432 | @end smallexample | |
922fbb7b | 25433 | |
a2c02241 NR |
25434 | Read symbol table info from the specified @var{file} argument. When |
25435 | used without arguments, clears @value{GDBN}'s symbol table info. No output is | |
25436 | produced, except for a completion notification. | |
922fbb7b | 25437 | |
a2c02241 | 25438 | @subsubheading @value{GDBN} Command |
922fbb7b | 25439 | |
a2c02241 | 25440 | The corresponding @value{GDBN} command is @samp{symbol-file}. |
922fbb7b | 25441 | |
a2c02241 | 25442 | @subsubheading Example |
922fbb7b | 25443 | |
a2c02241 | 25444 | @smallexample |
594fe323 | 25445 | (gdb) |
a2c02241 NR |
25446 | -file-symbol-file /kwikemart/marge/ezannoni/TRUNK/mbx/hello.mbx |
25447 | ^done | |
594fe323 | 25448 | (gdb) |
a2c02241 | 25449 | @end smallexample |
922fbb7b | 25450 | |
a2c02241 | 25451 | @ignore |
a2c02241 NR |
25452 | @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% |
25453 | @node GDB/MI Memory Overlay Commands | |
25454 | @section @sc{gdb/mi} Memory Overlay Commands | |
922fbb7b | 25455 | |
a2c02241 | 25456 | The memory overlay commands are not implemented. |
922fbb7b | 25457 | |
a2c02241 | 25458 | @c @subheading -overlay-auto |
922fbb7b | 25459 | |
a2c02241 | 25460 | @c @subheading -overlay-list-mapping-state |
922fbb7b | 25461 | |
a2c02241 | 25462 | @c @subheading -overlay-list-overlays |
922fbb7b | 25463 | |
a2c02241 | 25464 | @c @subheading -overlay-map |
922fbb7b | 25465 | |
a2c02241 | 25466 | @c @subheading -overlay-off |
922fbb7b | 25467 | |
a2c02241 | 25468 | @c @subheading -overlay-on |
922fbb7b | 25469 | |
a2c02241 | 25470 | @c @subheading -overlay-unmap |
922fbb7b | 25471 | |
a2c02241 NR |
25472 | @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% |
25473 | @node GDB/MI Signal Handling Commands | |
25474 | @section @sc{gdb/mi} Signal Handling Commands | |
922fbb7b | 25475 | |
a2c02241 | 25476 | Signal handling commands are not implemented. |
922fbb7b | 25477 | |
a2c02241 | 25478 | @c @subheading -signal-handle |
922fbb7b | 25479 | |
a2c02241 | 25480 | @c @subheading -signal-list-handle-actions |
922fbb7b | 25481 | |
a2c02241 NR |
25482 | @c @subheading -signal-list-signal-types |
25483 | @end ignore | |
922fbb7b | 25484 | |
922fbb7b | 25485 | |
a2c02241 NR |
25486 | @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% |
25487 | @node GDB/MI Target Manipulation | |
25488 | @section @sc{gdb/mi} Target Manipulation Commands | |
922fbb7b AC |
25489 | |
25490 | ||
a2c02241 NR |
25491 | @subheading The @code{-target-attach} Command |
25492 | @findex -target-attach | |
922fbb7b AC |
25493 | |
25494 | @subsubheading Synopsis | |
25495 | ||
25496 | @smallexample | |
c3b108f7 | 25497 | -target-attach @var{pid} | @var{gid} | @var{file} |
922fbb7b AC |
25498 | @end smallexample |
25499 | ||
c3b108f7 VP |
25500 | Attach to a process @var{pid} or a file @var{file} outside of |
25501 | @value{GDBN}, or a thread group @var{gid}. If attaching to a thread | |
25502 | group, the id previously returned by | |
25503 | @samp{-list-thread-groups --available} must be used. | |
922fbb7b | 25504 | |
79a6e687 | 25505 | @subsubheading @value{GDBN} Command |
922fbb7b | 25506 | |
a2c02241 | 25507 | The corresponding @value{GDBN} command is @samp{attach}. |
922fbb7b | 25508 | |
a2c02241 | 25509 | @subsubheading Example |
b56e7235 VP |
25510 | @smallexample |
25511 | (gdb) | |
25512 | -target-attach 34 | |
25513 | =thread-created,id="1" | |
5ae4183a | 25514 | *stopped,thread-id="1",frame=@{addr="0xb7f7e410",func="bar",args=[]@} |
b56e7235 VP |
25515 | ^done |
25516 | (gdb) | |
25517 | @end smallexample | |
a2c02241 | 25518 | |
9901a55b | 25519 | @ignore |
a2c02241 NR |
25520 | @subheading The @code{-target-compare-sections} Command |
25521 | @findex -target-compare-sections | |
922fbb7b AC |
25522 | |
25523 | @subsubheading Synopsis | |
25524 | ||
25525 | @smallexample | |
a2c02241 | 25526 | -target-compare-sections [ @var{section} ] |
922fbb7b AC |
25527 | @end smallexample |
25528 | ||
a2c02241 NR |
25529 | Compare data of section @var{section} on target to the exec file. |
25530 | Without the argument, all sections are compared. | |
922fbb7b | 25531 | |
a2c02241 | 25532 | @subsubheading @value{GDBN} Command |
922fbb7b | 25533 | |
a2c02241 | 25534 | The @value{GDBN} equivalent is @samp{compare-sections}. |
922fbb7b | 25535 | |
a2c02241 NR |
25536 | @subsubheading Example |
25537 | N.A. | |
9901a55b | 25538 | @end ignore |
a2c02241 NR |
25539 | |
25540 | ||
25541 | @subheading The @code{-target-detach} Command | |
25542 | @findex -target-detach | |
922fbb7b AC |
25543 | |
25544 | @subsubheading Synopsis | |
25545 | ||
25546 | @smallexample | |
c3b108f7 | 25547 | -target-detach [ @var{pid} | @var{gid} ] |
922fbb7b AC |
25548 | @end smallexample |
25549 | ||
a2c02241 | 25550 | Detach from the remote target which normally resumes its execution. |
c3b108f7 VP |
25551 | If either @var{pid} or @var{gid} is specified, detaches from either |
25552 | the specified process, or specified thread group. There's no output. | |
a2c02241 | 25553 | |
79a6e687 | 25554 | @subsubheading @value{GDBN} Command |
a2c02241 NR |
25555 | |
25556 | The corresponding @value{GDBN} command is @samp{detach}. | |
25557 | ||
25558 | @subsubheading Example | |
922fbb7b AC |
25559 | |
25560 | @smallexample | |
594fe323 | 25561 | (gdb) |
a2c02241 NR |
25562 | -target-detach |
25563 | ^done | |
594fe323 | 25564 | (gdb) |
922fbb7b AC |
25565 | @end smallexample |
25566 | ||
25567 | ||
a2c02241 NR |
25568 | @subheading The @code{-target-disconnect} Command |
25569 | @findex -target-disconnect | |
922fbb7b AC |
25570 | |
25571 | @subsubheading Synopsis | |
25572 | ||
123dc839 | 25573 | @smallexample |
a2c02241 | 25574 | -target-disconnect |
123dc839 | 25575 | @end smallexample |
922fbb7b | 25576 | |
a2c02241 NR |
25577 | Disconnect from the remote target. There's no output and the target is |
25578 | generally not resumed. | |
25579 | ||
79a6e687 | 25580 | @subsubheading @value{GDBN} Command |
a2c02241 NR |
25581 | |
25582 | The corresponding @value{GDBN} command is @samp{disconnect}. | |
bc8ced35 NR |
25583 | |
25584 | @subsubheading Example | |
922fbb7b AC |
25585 | |
25586 | @smallexample | |
594fe323 | 25587 | (gdb) |
a2c02241 NR |
25588 | -target-disconnect |
25589 | ^done | |
594fe323 | 25590 | (gdb) |
922fbb7b AC |
25591 | @end smallexample |
25592 | ||
25593 | ||
a2c02241 NR |
25594 | @subheading The @code{-target-download} Command |
25595 | @findex -target-download | |
922fbb7b AC |
25596 | |
25597 | @subsubheading Synopsis | |
25598 | ||
25599 | @smallexample | |
a2c02241 | 25600 | -target-download |
922fbb7b AC |
25601 | @end smallexample |
25602 | ||
a2c02241 NR |
25603 | Loads the executable onto the remote target. |
25604 | It prints out an update message every half second, which includes the fields: | |
25605 | ||
25606 | @table @samp | |
25607 | @item section | |
25608 | The name of the section. | |
25609 | @item section-sent | |
25610 | The size of what has been sent so far for that section. | |
25611 | @item section-size | |
25612 | The size of the section. | |
25613 | @item total-sent | |
25614 | The total size of what was sent so far (the current and the previous sections). | |
25615 | @item total-size | |
25616 | The size of the overall executable to download. | |
25617 | @end table | |
25618 | ||
25619 | @noindent | |
25620 | Each message is sent as status record (@pxref{GDB/MI Output Syntax, , | |
25621 | @sc{gdb/mi} Output Syntax}). | |
25622 | ||
25623 | In addition, it prints the name and size of the sections, as they are | |
25624 | downloaded. These messages include the following fields: | |
25625 | ||
25626 | @table @samp | |
25627 | @item section | |
25628 | The name of the section. | |
25629 | @item section-size | |
25630 | The size of the section. | |
25631 | @item total-size | |
25632 | The size of the overall executable to download. | |
25633 | @end table | |
25634 | ||
25635 | @noindent | |
25636 | At the end, a summary is printed. | |
25637 | ||
25638 | @subsubheading @value{GDBN} Command | |
25639 | ||
25640 | The corresponding @value{GDBN} command is @samp{load}. | |
25641 | ||
25642 | @subsubheading Example | |
25643 | ||
25644 | Note: each status message appears on a single line. Here the messages | |
25645 | have been broken down so that they can fit onto a page. | |
922fbb7b AC |
25646 | |
25647 | @smallexample | |
594fe323 | 25648 | (gdb) |
a2c02241 NR |
25649 | -target-download |
25650 | +download,@{section=".text",section-size="6668",total-size="9880"@} | |
25651 | +download,@{section=".text",section-sent="512",section-size="6668", | |
25652 | total-sent="512",total-size="9880"@} | |
25653 | +download,@{section=".text",section-sent="1024",section-size="6668", | |
25654 | total-sent="1024",total-size="9880"@} | |
25655 | +download,@{section=".text",section-sent="1536",section-size="6668", | |
25656 | total-sent="1536",total-size="9880"@} | |
25657 | +download,@{section=".text",section-sent="2048",section-size="6668", | |
25658 | total-sent="2048",total-size="9880"@} | |
25659 | +download,@{section=".text",section-sent="2560",section-size="6668", | |
25660 | total-sent="2560",total-size="9880"@} | |
25661 | +download,@{section=".text",section-sent="3072",section-size="6668", | |
25662 | total-sent="3072",total-size="9880"@} | |
25663 | +download,@{section=".text",section-sent="3584",section-size="6668", | |
25664 | total-sent="3584",total-size="9880"@} | |
25665 | +download,@{section=".text",section-sent="4096",section-size="6668", | |
25666 | total-sent="4096",total-size="9880"@} | |
25667 | +download,@{section=".text",section-sent="4608",section-size="6668", | |
25668 | total-sent="4608",total-size="9880"@} | |
25669 | +download,@{section=".text",section-sent="5120",section-size="6668", | |
25670 | total-sent="5120",total-size="9880"@} | |
25671 | +download,@{section=".text",section-sent="5632",section-size="6668", | |
25672 | total-sent="5632",total-size="9880"@} | |
25673 | +download,@{section=".text",section-sent="6144",section-size="6668", | |
25674 | total-sent="6144",total-size="9880"@} | |
25675 | +download,@{section=".text",section-sent="6656",section-size="6668", | |
25676 | total-sent="6656",total-size="9880"@} | |
25677 | +download,@{section=".init",section-size="28",total-size="9880"@} | |
25678 | +download,@{section=".fini",section-size="28",total-size="9880"@} | |
25679 | +download,@{section=".data",section-size="3156",total-size="9880"@} | |
25680 | +download,@{section=".data",section-sent="512",section-size="3156", | |
25681 | total-sent="7236",total-size="9880"@} | |
25682 | +download,@{section=".data",section-sent="1024",section-size="3156", | |
25683 | total-sent="7748",total-size="9880"@} | |
25684 | +download,@{section=".data",section-sent="1536",section-size="3156", | |
25685 | total-sent="8260",total-size="9880"@} | |
25686 | +download,@{section=".data",section-sent="2048",section-size="3156", | |
25687 | total-sent="8772",total-size="9880"@} | |
25688 | +download,@{section=".data",section-sent="2560",section-size="3156", | |
25689 | total-sent="9284",total-size="9880"@} | |
25690 | +download,@{section=".data",section-sent="3072",section-size="3156", | |
25691 | total-sent="9796",total-size="9880"@} | |
25692 | ^done,address="0x10004",load-size="9880",transfer-rate="6586", | |
25693 | write-rate="429" | |
594fe323 | 25694 | (gdb) |
922fbb7b AC |
25695 | @end smallexample |
25696 | ||
25697 | ||
9901a55b | 25698 | @ignore |
a2c02241 NR |
25699 | @subheading The @code{-target-exec-status} Command |
25700 | @findex -target-exec-status | |
922fbb7b AC |
25701 | |
25702 | @subsubheading Synopsis | |
25703 | ||
25704 | @smallexample | |
a2c02241 | 25705 | -target-exec-status |
922fbb7b AC |
25706 | @end smallexample |
25707 | ||
a2c02241 NR |
25708 | Provide information on the state of the target (whether it is running or |
25709 | not, for instance). | |
922fbb7b | 25710 | |
a2c02241 | 25711 | @subsubheading @value{GDBN} Command |
922fbb7b | 25712 | |
a2c02241 NR |
25713 | There's no equivalent @value{GDBN} command. |
25714 | ||
25715 | @subsubheading Example | |
25716 | N.A. | |
922fbb7b | 25717 | |
a2c02241 NR |
25718 | |
25719 | @subheading The @code{-target-list-available-targets} Command | |
25720 | @findex -target-list-available-targets | |
922fbb7b AC |
25721 | |
25722 | @subsubheading Synopsis | |
25723 | ||
25724 | @smallexample | |
a2c02241 | 25725 | -target-list-available-targets |
922fbb7b AC |
25726 | @end smallexample |
25727 | ||
a2c02241 | 25728 | List the possible targets to connect to. |
922fbb7b | 25729 | |
a2c02241 | 25730 | @subsubheading @value{GDBN} Command |
922fbb7b | 25731 | |
a2c02241 | 25732 | The corresponding @value{GDBN} command is @samp{help target}. |
922fbb7b | 25733 | |
a2c02241 NR |
25734 | @subsubheading Example |
25735 | N.A. | |
25736 | ||
25737 | ||
25738 | @subheading The @code{-target-list-current-targets} Command | |
25739 | @findex -target-list-current-targets | |
922fbb7b AC |
25740 | |
25741 | @subsubheading Synopsis | |
25742 | ||
25743 | @smallexample | |
a2c02241 | 25744 | -target-list-current-targets |
922fbb7b AC |
25745 | @end smallexample |
25746 | ||
a2c02241 | 25747 | Describe the current target. |
922fbb7b | 25748 | |
a2c02241 | 25749 | @subsubheading @value{GDBN} Command |
922fbb7b | 25750 | |
a2c02241 NR |
25751 | The corresponding information is printed by @samp{info file} (among |
25752 | other things). | |
922fbb7b | 25753 | |
a2c02241 NR |
25754 | @subsubheading Example |
25755 | N.A. | |
25756 | ||
25757 | ||
25758 | @subheading The @code{-target-list-parameters} Command | |
25759 | @findex -target-list-parameters | |
922fbb7b AC |
25760 | |
25761 | @subsubheading Synopsis | |
25762 | ||
25763 | @smallexample | |
a2c02241 | 25764 | -target-list-parameters |
922fbb7b AC |
25765 | @end smallexample |
25766 | ||
a2c02241 | 25767 | @c ???? |
9901a55b | 25768 | @end ignore |
a2c02241 NR |
25769 | |
25770 | @subsubheading @value{GDBN} Command | |
25771 | ||
25772 | No equivalent. | |
922fbb7b AC |
25773 | |
25774 | @subsubheading Example | |
a2c02241 NR |
25775 | N.A. |
25776 | ||
25777 | ||
25778 | @subheading The @code{-target-select} Command | |
25779 | @findex -target-select | |
25780 | ||
25781 | @subsubheading Synopsis | |
922fbb7b AC |
25782 | |
25783 | @smallexample | |
a2c02241 | 25784 | -target-select @var{type} @var{parameters @dots{}} |
922fbb7b AC |
25785 | @end smallexample |
25786 | ||
a2c02241 | 25787 | Connect @value{GDBN} to the remote target. This command takes two args: |
922fbb7b | 25788 | |
a2c02241 NR |
25789 | @table @samp |
25790 | @item @var{type} | |
75c99385 | 25791 | The type of target, for instance @samp{remote}, etc. |
a2c02241 NR |
25792 | @item @var{parameters} |
25793 | Device names, host names and the like. @xref{Target Commands, , | |
79a6e687 | 25794 | Commands for Managing Targets}, for more details. |
a2c02241 NR |
25795 | @end table |
25796 | ||
25797 | The output is a connection notification, followed by the address at | |
25798 | which the target program is, in the following form: | |
922fbb7b AC |
25799 | |
25800 | @smallexample | |
a2c02241 NR |
25801 | ^connected,addr="@var{address}",func="@var{function name}", |
25802 | args=[@var{arg list}] | |
922fbb7b AC |
25803 | @end smallexample |
25804 | ||
a2c02241 NR |
25805 | @subsubheading @value{GDBN} Command |
25806 | ||
25807 | The corresponding @value{GDBN} command is @samp{target}. | |
265eeb58 NR |
25808 | |
25809 | @subsubheading Example | |
922fbb7b | 25810 | |
265eeb58 | 25811 | @smallexample |
594fe323 | 25812 | (gdb) |
75c99385 | 25813 | -target-select remote /dev/ttya |
a2c02241 | 25814 | ^connected,addr="0xfe00a300",func="??",args=[] |
594fe323 | 25815 | (gdb) |
265eeb58 | 25816 | @end smallexample |
ef21caaf | 25817 | |
a6b151f1 DJ |
25818 | @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% |
25819 | @node GDB/MI File Transfer Commands | |
25820 | @section @sc{gdb/mi} File Transfer Commands | |
25821 | ||
25822 | ||
25823 | @subheading The @code{-target-file-put} Command | |
25824 | @findex -target-file-put | |
25825 | ||
25826 | @subsubheading Synopsis | |
25827 | ||
25828 | @smallexample | |
25829 | -target-file-put @var{hostfile} @var{targetfile} | |
25830 | @end smallexample | |
25831 | ||
25832 | Copy file @var{hostfile} from the host system (the machine running | |
25833 | @value{GDBN}) to @var{targetfile} on the target system. | |
25834 | ||
25835 | @subsubheading @value{GDBN} Command | |
25836 | ||
25837 | The corresponding @value{GDBN} command is @samp{remote put}. | |
25838 | ||
25839 | @subsubheading Example | |
25840 | ||
25841 | @smallexample | |
25842 | (gdb) | |
25843 | -target-file-put localfile remotefile | |
25844 | ^done | |
25845 | (gdb) | |
25846 | @end smallexample | |
25847 | ||
25848 | ||
1763a388 | 25849 | @subheading The @code{-target-file-get} Command |
a6b151f1 DJ |
25850 | @findex -target-file-get |
25851 | ||
25852 | @subsubheading Synopsis | |
25853 | ||
25854 | @smallexample | |
25855 | -target-file-get @var{targetfile} @var{hostfile} | |
25856 | @end smallexample | |
25857 | ||
25858 | Copy file @var{targetfile} from the target system to @var{hostfile} | |
25859 | on the host system. | |
25860 | ||
25861 | @subsubheading @value{GDBN} Command | |
25862 | ||
25863 | The corresponding @value{GDBN} command is @samp{remote get}. | |
25864 | ||
25865 | @subsubheading Example | |
25866 | ||
25867 | @smallexample | |
25868 | (gdb) | |
25869 | -target-file-get remotefile localfile | |
25870 | ^done | |
25871 | (gdb) | |
25872 | @end smallexample | |
25873 | ||
25874 | ||
25875 | @subheading The @code{-target-file-delete} Command | |
25876 | @findex -target-file-delete | |
25877 | ||
25878 | @subsubheading Synopsis | |
25879 | ||
25880 | @smallexample | |
25881 | -target-file-delete @var{targetfile} | |
25882 | @end smallexample | |
25883 | ||
25884 | Delete @var{targetfile} from the target system. | |
25885 | ||
25886 | @subsubheading @value{GDBN} Command | |
25887 | ||
25888 | The corresponding @value{GDBN} command is @samp{remote delete}. | |
25889 | ||
25890 | @subsubheading Example | |
25891 | ||
25892 | @smallexample | |
25893 | (gdb) | |
25894 | -target-file-delete remotefile | |
25895 | ^done | |
25896 | (gdb) | |
25897 | @end smallexample | |
25898 | ||
25899 | ||
ef21caaf NR |
25900 | @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% |
25901 | @node GDB/MI Miscellaneous Commands | |
25902 | @section Miscellaneous @sc{gdb/mi} Commands | |
25903 | ||
25904 | @c @subheading -gdb-complete | |
25905 | ||
25906 | @subheading The @code{-gdb-exit} Command | |
25907 | @findex -gdb-exit | |
25908 | ||
25909 | @subsubheading Synopsis | |
25910 | ||
25911 | @smallexample | |
25912 | -gdb-exit | |
25913 | @end smallexample | |
25914 | ||
25915 | Exit @value{GDBN} immediately. | |
25916 | ||
25917 | @subsubheading @value{GDBN} Command | |
25918 | ||
25919 | Approximately corresponds to @samp{quit}. | |
25920 | ||
25921 | @subsubheading Example | |
25922 | ||
25923 | @smallexample | |
594fe323 | 25924 | (gdb) |
ef21caaf NR |
25925 | -gdb-exit |
25926 | ^exit | |
25927 | @end smallexample | |
25928 | ||
a2c02241 | 25929 | |
9901a55b | 25930 | @ignore |
a2c02241 NR |
25931 | @subheading The @code{-exec-abort} Command |
25932 | @findex -exec-abort | |
25933 | ||
25934 | @subsubheading Synopsis | |
25935 | ||
25936 | @smallexample | |
25937 | -exec-abort | |
25938 | @end smallexample | |
25939 | ||
25940 | Kill the inferior running program. | |
25941 | ||
25942 | @subsubheading @value{GDBN} Command | |
25943 | ||
25944 | The corresponding @value{GDBN} command is @samp{kill}. | |
25945 | ||
25946 | @subsubheading Example | |
25947 | N.A. | |
9901a55b | 25948 | @end ignore |
a2c02241 NR |
25949 | |
25950 | ||
ef21caaf NR |
25951 | @subheading The @code{-gdb-set} Command |
25952 | @findex -gdb-set | |
25953 | ||
25954 | @subsubheading Synopsis | |
25955 | ||
25956 | @smallexample | |
25957 | -gdb-set | |
25958 | @end smallexample | |
25959 | ||
25960 | Set an internal @value{GDBN} variable. | |
25961 | @c IS THIS A DOLLAR VARIABLE? OR SOMETHING LIKE ANNOTATE ????? | |
25962 | ||
25963 | @subsubheading @value{GDBN} Command | |
25964 | ||
25965 | The corresponding @value{GDBN} command is @samp{set}. | |
25966 | ||
25967 | @subsubheading Example | |
25968 | ||
25969 | @smallexample | |
594fe323 | 25970 | (gdb) |
ef21caaf NR |
25971 | -gdb-set $foo=3 |
25972 | ^done | |
594fe323 | 25973 | (gdb) |
ef21caaf NR |
25974 | @end smallexample |
25975 | ||
25976 | ||
25977 | @subheading The @code{-gdb-show} Command | |
25978 | @findex -gdb-show | |
25979 | ||
25980 | @subsubheading Synopsis | |
25981 | ||
25982 | @smallexample | |
25983 | -gdb-show | |
25984 | @end smallexample | |
25985 | ||
25986 | Show the current value of a @value{GDBN} variable. | |
25987 | ||
79a6e687 | 25988 | @subsubheading @value{GDBN} Command |
ef21caaf NR |
25989 | |
25990 | The corresponding @value{GDBN} command is @samp{show}. | |
25991 | ||
25992 | @subsubheading Example | |
25993 | ||
25994 | @smallexample | |
594fe323 | 25995 | (gdb) |
ef21caaf NR |
25996 | -gdb-show annotate |
25997 | ^done,value="0" | |
594fe323 | 25998 | (gdb) |
ef21caaf NR |
25999 | @end smallexample |
26000 | ||
26001 | @c @subheading -gdb-source | |
26002 | ||
26003 | ||
26004 | @subheading The @code{-gdb-version} Command | |
26005 | @findex -gdb-version | |
26006 | ||
26007 | @subsubheading Synopsis | |
26008 | ||
26009 | @smallexample | |
26010 | -gdb-version | |
26011 | @end smallexample | |
26012 | ||
26013 | Show version information for @value{GDBN}. Used mostly in testing. | |
26014 | ||
26015 | @subsubheading @value{GDBN} Command | |
26016 | ||
26017 | The @value{GDBN} equivalent is @samp{show version}. @value{GDBN} by | |
26018 | default shows this information when you start an interactive session. | |
26019 | ||
26020 | @subsubheading Example | |
26021 | ||
26022 | @c This example modifies the actual output from GDB to avoid overfull | |
26023 | @c box in TeX. | |
26024 | @smallexample | |
594fe323 | 26025 | (gdb) |
ef21caaf NR |
26026 | -gdb-version |
26027 | ~GNU gdb 5.2.1 | |
26028 | ~Copyright 2000 Free Software Foundation, Inc. | |
26029 | ~GDB is free software, covered by the GNU General Public License, and | |
26030 | ~you are welcome to change it and/or distribute copies of it under | |
26031 | ~ certain conditions. | |
26032 | ~Type "show copying" to see the conditions. | |
26033 | ~There is absolutely no warranty for GDB. Type "show warranty" for | |
26034 | ~ details. | |
26035 | ~This GDB was configured as | |
26036 | "--host=sparc-sun-solaris2.5.1 --target=ppc-eabi". | |
26037 | ^done | |
594fe323 | 26038 | (gdb) |
ef21caaf NR |
26039 | @end smallexample |
26040 | ||
084344da VP |
26041 | @subheading The @code{-list-features} Command |
26042 | @findex -list-features | |
26043 | ||
26044 | Returns a list of particular features of the MI protocol that | |
26045 | this version of gdb implements. A feature can be a command, | |
26046 | or a new field in an output of some command, or even an | |
26047 | important bugfix. While a frontend can sometimes detect presence | |
26048 | of a feature at runtime, it is easier to perform detection at debugger | |
26049 | startup. | |
26050 | ||
26051 | The command returns a list of strings, with each string naming an | |
26052 | available feature. Each returned string is just a name, it does not | |
26053 | have any internal structure. The list of possible feature names | |
26054 | is given below. | |
26055 | ||
26056 | Example output: | |
26057 | ||
26058 | @smallexample | |
26059 | (gdb) -list-features | |
26060 | ^done,result=["feature1","feature2"] | |
26061 | @end smallexample | |
26062 | ||
26063 | The current list of features is: | |
26064 | ||
30e026bb VP |
26065 | @table @samp |
26066 | @item frozen-varobjs | |
26067 | Indicates presence of the @code{-var-set-frozen} command, as well | |
26068 | as possible presense of the @code{frozen} field in the output | |
26069 | of @code{-varobj-create}. | |
26070 | @item pending-breakpoints | |
26071 | Indicates presence of the @option{-f} option to the @code{-break-insert} command. | |
b6313243 TT |
26072 | @item python |
26073 | Indicates presence of Python scripting support, Python-based | |
26074 | pretty-printing commands, and possible presence of the | |
26075 | @samp{display_hint} field in the output of @code{-var-list-children} | |
30e026bb VP |
26076 | @item thread-info |
26077 | Indicates presence of the @code{-thread-info} command. | |
8b4ed427 | 26078 | |
30e026bb | 26079 | @end table |
084344da | 26080 | |
c6ebd6cf VP |
26081 | @subheading The @code{-list-target-features} Command |
26082 | @findex -list-target-features | |
26083 | ||
26084 | Returns a list of particular features that are supported by the | |
26085 | target. Those features affect the permitted MI commands, but | |
26086 | unlike the features reported by the @code{-list-features} command, the | |
26087 | features depend on which target GDB is using at the moment. Whenever | |
26088 | a target can change, due to commands such as @code{-target-select}, | |
26089 | @code{-target-attach} or @code{-exec-run}, the list of target features | |
26090 | may change, and the frontend should obtain it again. | |
26091 | Example output: | |
26092 | ||
26093 | @smallexample | |
26094 | (gdb) -list-features | |
26095 | ^done,result=["async"] | |
26096 | @end smallexample | |
26097 | ||
26098 | The current list of features is: | |
26099 | ||
26100 | @table @samp | |
26101 | @item async | |
26102 | Indicates that the target is capable of asynchronous command | |
26103 | execution, which means that @value{GDBN} will accept further commands | |
26104 | while the target is running. | |
26105 | ||
26106 | @end table | |
26107 | ||
c3b108f7 VP |
26108 | @subheading The @code{-list-thread-groups} Command |
26109 | @findex -list-thread-groups | |
26110 | ||
26111 | @subheading Synopsis | |
26112 | ||
26113 | @smallexample | |
26114 | -list-thread-groups [ --available ] [ @var{group} ] | |
26115 | @end smallexample | |
26116 | ||
26117 | When used without the @var{group} parameter, lists top-level thread | |
26118 | groups that are being debugged. When used with the @var{group} | |
26119 | parameter, the children of the specified group are listed. The | |
26120 | children can be either threads, or other groups. At present, | |
26121 | @value{GDBN} will not report both threads and groups as children at | |
26122 | the same time, but it may change in future. | |
26123 | ||
26124 | With the @samp{--available} option, instead of reporting groups that | |
26125 | are been debugged, GDB will report all thread groups available on the | |
26126 | target. Using the @samp{--available} option together with @var{group} | |
26127 | is not allowed. | |
26128 | ||
26129 | @subheading Example | |
26130 | ||
26131 | @smallexample | |
26132 | @value{GDBP} | |
26133 | -list-thread-groups | |
26134 | ^done,groups=[@{id="17",type="process",pid="yyy",num_children="2"@}] | |
26135 | -list-thread-groups 17 | |
26136 | ^done,threads=[@{id="2",target-id="Thread 0xb7e14b90 (LWP 21257)", | |
26137 | frame=@{level="0",addr="0xffffe410",func="__kernel_vsyscall",args=[]@},state="running"@}, | |
26138 | @{id="1",target-id="Thread 0xb7e156b0 (LWP 21254)", | |
26139 | frame=@{level="0",addr="0x0804891f",func="foo",args=[@{name="i",value="10"@}], | |
26140 | file="/tmp/a.c",fullname="/tmp/a.c",line="158"@},state="running"@}]] | |
26141 | @end smallexample | |
c6ebd6cf | 26142 | |
ef21caaf NR |
26143 | @subheading The @code{-interpreter-exec} Command |
26144 | @findex -interpreter-exec | |
26145 | ||
26146 | @subheading Synopsis | |
26147 | ||
26148 | @smallexample | |
26149 | -interpreter-exec @var{interpreter} @var{command} | |
26150 | @end smallexample | |
a2c02241 | 26151 | @anchor{-interpreter-exec} |
ef21caaf NR |
26152 | |
26153 | Execute the specified @var{command} in the given @var{interpreter}. | |
26154 | ||
26155 | @subheading @value{GDBN} Command | |
26156 | ||
26157 | The corresponding @value{GDBN} command is @samp{interpreter-exec}. | |
26158 | ||
26159 | @subheading Example | |
26160 | ||
26161 | @smallexample | |
594fe323 | 26162 | (gdb) |
ef21caaf NR |
26163 | -interpreter-exec console "break main" |
26164 | &"During symbol reading, couldn't parse type; debugger out of date?.\n" | |
26165 | &"During symbol reading, bad structure-type format.\n" | |
26166 | ~"Breakpoint 1 at 0x8074fc6: file ../../src/gdb/main.c, line 743.\n" | |
26167 | ^done | |
594fe323 | 26168 | (gdb) |
ef21caaf NR |
26169 | @end smallexample |
26170 | ||
26171 | @subheading The @code{-inferior-tty-set} Command | |
26172 | @findex -inferior-tty-set | |
26173 | ||
26174 | @subheading Synopsis | |
26175 | ||
26176 | @smallexample | |
26177 | -inferior-tty-set /dev/pts/1 | |
26178 | @end smallexample | |
26179 | ||
26180 | Set terminal for future runs of the program being debugged. | |
26181 | ||
26182 | @subheading @value{GDBN} Command | |
26183 | ||
26184 | The corresponding @value{GDBN} command is @samp{set inferior-tty} /dev/pts/1. | |
26185 | ||
26186 | @subheading Example | |
26187 | ||
26188 | @smallexample | |
594fe323 | 26189 | (gdb) |
ef21caaf NR |
26190 | -inferior-tty-set /dev/pts/1 |
26191 | ^done | |
594fe323 | 26192 | (gdb) |
ef21caaf NR |
26193 | @end smallexample |
26194 | ||
26195 | @subheading The @code{-inferior-tty-show} Command | |
26196 | @findex -inferior-tty-show | |
26197 | ||
26198 | @subheading Synopsis | |
26199 | ||
26200 | @smallexample | |
26201 | -inferior-tty-show | |
26202 | @end smallexample | |
26203 | ||
26204 | Show terminal for future runs of program being debugged. | |
26205 | ||
26206 | @subheading @value{GDBN} Command | |
26207 | ||
26208 | The corresponding @value{GDBN} command is @samp{show inferior-tty}. | |
26209 | ||
26210 | @subheading Example | |
26211 | ||
26212 | @smallexample | |
594fe323 | 26213 | (gdb) |
ef21caaf NR |
26214 | -inferior-tty-set /dev/pts/1 |
26215 | ^done | |
594fe323 | 26216 | (gdb) |
ef21caaf NR |
26217 | -inferior-tty-show |
26218 | ^done,inferior_tty_terminal="/dev/pts/1" | |
594fe323 | 26219 | (gdb) |
ef21caaf | 26220 | @end smallexample |
922fbb7b | 26221 | |
a4eefcd8 NR |
26222 | @subheading The @code{-enable-timings} Command |
26223 | @findex -enable-timings | |
26224 | ||
26225 | @subheading Synopsis | |
26226 | ||
26227 | @smallexample | |
26228 | -enable-timings [yes | no] | |
26229 | @end smallexample | |
26230 | ||
26231 | Toggle the printing of the wallclock, user and system times for an MI | |
26232 | command as a field in its output. This command is to help frontend | |
26233 | developers optimize the performance of their code. No argument is | |
26234 | equivalent to @samp{yes}. | |
26235 | ||
26236 | @subheading @value{GDBN} Command | |
26237 | ||
26238 | No equivalent. | |
26239 | ||
26240 | @subheading Example | |
26241 | ||
26242 | @smallexample | |
26243 | (gdb) | |
26244 | -enable-timings | |
26245 | ^done | |
26246 | (gdb) | |
26247 | -break-insert main | |
26248 | ^done,bkpt=@{number="1",type="breakpoint",disp="keep",enabled="y", | |
26249 | addr="0x080484ed",func="main",file="myprog.c", | |
26250 | fullname="/home/nickrob/myprog.c",line="73",times="0"@}, | |
26251 | time=@{wallclock="0.05185",user="0.00800",system="0.00000"@} | |
26252 | (gdb) | |
26253 | -enable-timings no | |
26254 | ^done | |
26255 | (gdb) | |
26256 | -exec-run | |
26257 | ^running | |
26258 | (gdb) | |
a47ec5fe | 26259 | *stopped,reason="breakpoint-hit",disp="keep",bkptno="1",thread-id="0", |
a4eefcd8 NR |
26260 | frame=@{addr="0x080484ed",func="main",args=[@{name="argc",value="1"@}, |
26261 | @{name="argv",value="0xbfb60364"@}],file="myprog.c", | |
26262 | fullname="/home/nickrob/myprog.c",line="73"@} | |
26263 | (gdb) | |
26264 | @end smallexample | |
26265 | ||
922fbb7b AC |
26266 | @node Annotations |
26267 | @chapter @value{GDBN} Annotations | |
26268 | ||
086432e2 AC |
26269 | This chapter describes annotations in @value{GDBN}. Annotations were |
26270 | designed to interface @value{GDBN} to graphical user interfaces or other | |
26271 | similar programs which want to interact with @value{GDBN} at a | |
922fbb7b AC |
26272 | relatively high level. |
26273 | ||
d3e8051b | 26274 | The annotation mechanism has largely been superseded by @sc{gdb/mi} |
086432e2 AC |
26275 | (@pxref{GDB/MI}). |
26276 | ||
922fbb7b AC |
26277 | @ignore |
26278 | This is Edition @value{EDITION}, @value{DATE}. | |
26279 | @end ignore | |
26280 | ||
26281 | @menu | |
26282 | * Annotations Overview:: What annotations are; the general syntax. | |
9e6c4bd5 | 26283 | * Server Prefix:: Issuing a command without affecting user state. |
922fbb7b AC |
26284 | * Prompting:: Annotations marking @value{GDBN}'s need for input. |
26285 | * Errors:: Annotations for error messages. | |
922fbb7b AC |
26286 | * Invalidation:: Some annotations describe things now invalid. |
26287 | * Annotations for Running:: | |
26288 | Whether the program is running, how it stopped, etc. | |
26289 | * Source Annotations:: Annotations describing source code. | |
922fbb7b AC |
26290 | @end menu |
26291 | ||
26292 | @node Annotations Overview | |
26293 | @section What is an Annotation? | |
26294 | @cindex annotations | |
26295 | ||
922fbb7b AC |
26296 | Annotations start with a newline character, two @samp{control-z} |
26297 | characters, and the name of the annotation. If there is no additional | |
26298 | information associated with this annotation, the name of the annotation | |
26299 | is followed immediately by a newline. If there is additional | |
26300 | information, the name of the annotation is followed by a space, the | |
26301 | additional information, and a newline. The additional information | |
26302 | cannot contain newline characters. | |
26303 | ||
26304 | Any output not beginning with a newline and two @samp{control-z} | |
26305 | characters denotes literal output from @value{GDBN}. Currently there is | |
26306 | no need for @value{GDBN} to output a newline followed by two | |
26307 | @samp{control-z} characters, but if there was such a need, the | |
26308 | annotations could be extended with an @samp{escape} annotation which | |
26309 | means those three characters as output. | |
26310 | ||
086432e2 AC |
26311 | The annotation @var{level}, which is specified using the |
26312 | @option{--annotate} command line option (@pxref{Mode Options}), controls | |
26313 | how much information @value{GDBN} prints together with its prompt, | |
26314 | values of expressions, source lines, and other types of output. Level 0 | |
d3e8051b | 26315 | is for no annotations, level 1 is for use when @value{GDBN} is run as a |
086432e2 AC |
26316 | subprocess of @sc{gnu} Emacs, level 3 is the maximum annotation suitable |
26317 | for programs that control @value{GDBN}, and level 2 annotations have | |
26318 | been made obsolete (@pxref{Limitations, , Limitations of the Annotation | |
09d4efe1 EZ |
26319 | Interface, annotate, GDB's Obsolete Annotations}). |
26320 | ||
26321 | @table @code | |
26322 | @kindex set annotate | |
26323 | @item set annotate @var{level} | |
e09f16f9 | 26324 | The @value{GDBN} command @code{set annotate} sets the level of |
09d4efe1 | 26325 | annotations to the specified @var{level}. |
9c16f35a EZ |
26326 | |
26327 | @item show annotate | |
26328 | @kindex show annotate | |
26329 | Show the current annotation level. | |
09d4efe1 EZ |
26330 | @end table |
26331 | ||
26332 | This chapter describes level 3 annotations. | |
086432e2 | 26333 | |
922fbb7b AC |
26334 | A simple example of starting up @value{GDBN} with annotations is: |
26335 | ||
26336 | @smallexample | |
086432e2 AC |
26337 | $ @kbd{gdb --annotate=3} |
26338 | GNU gdb 6.0 | |
26339 | Copyright 2003 Free Software Foundation, Inc. | |
922fbb7b AC |
26340 | GDB is free software, covered by the GNU General Public License, |
26341 | and you are welcome to change it and/or distribute copies of it | |
26342 | under certain conditions. | |
26343 | Type "show copying" to see the conditions. | |
26344 | There is absolutely no warranty for GDB. Type "show warranty" | |
26345 | for details. | |
086432e2 | 26346 | This GDB was configured as "i386-pc-linux-gnu" |
922fbb7b AC |
26347 | |
26348 | ^Z^Zpre-prompt | |
f7dc1244 | 26349 | (@value{GDBP}) |
922fbb7b | 26350 | ^Z^Zprompt |
086432e2 | 26351 | @kbd{quit} |
922fbb7b AC |
26352 | |
26353 | ^Z^Zpost-prompt | |
b383017d | 26354 | $ |
922fbb7b AC |
26355 | @end smallexample |
26356 | ||
26357 | Here @samp{quit} is input to @value{GDBN}; the rest is output from | |
26358 | @value{GDBN}. The three lines beginning @samp{^Z^Z} (where @samp{^Z} | |
26359 | denotes a @samp{control-z} character) are annotations; the rest is | |
26360 | output from @value{GDBN}. | |
26361 | ||
9e6c4bd5 NR |
26362 | @node Server Prefix |
26363 | @section The Server Prefix | |
26364 | @cindex server prefix | |
26365 | ||
26366 | If you prefix a command with @samp{server } then it will not affect | |
26367 | the command history, nor will it affect @value{GDBN}'s notion of which | |
26368 | command to repeat if @key{RET} is pressed on a line by itself. This | |
26369 | means that commands can be run behind a user's back by a front-end in | |
26370 | a transparent manner. | |
26371 | ||
d837706a NR |
26372 | The @code{server } prefix does not affect the recording of values into |
26373 | the value history; to print a value without recording it into the | |
26374 | value history, use the @code{output} command instead of the | |
26375 | @code{print} command. | |
26376 | ||
26377 | Using this prefix also disables confirmation requests | |
26378 | (@pxref{confirmation requests}). | |
9e6c4bd5 | 26379 | |
922fbb7b AC |
26380 | @node Prompting |
26381 | @section Annotation for @value{GDBN} Input | |
26382 | ||
26383 | @cindex annotations for prompts | |
26384 | When @value{GDBN} prompts for input, it annotates this fact so it is possible | |
26385 | to know when to send output, when the output from a given command is | |
26386 | over, etc. | |
26387 | ||
26388 | Different kinds of input each have a different @dfn{input type}. Each | |
26389 | input type has three annotations: a @code{pre-} annotation, which | |
26390 | denotes the beginning of any prompt which is being output, a plain | |
26391 | annotation, which denotes the end of the prompt, and then a @code{post-} | |
26392 | annotation which denotes the end of any echo which may (or may not) be | |
26393 | associated with the input. For example, the @code{prompt} input type | |
26394 | features the following annotations: | |
26395 | ||
26396 | @smallexample | |
26397 | ^Z^Zpre-prompt | |
26398 | ^Z^Zprompt | |
26399 | ^Z^Zpost-prompt | |
26400 | @end smallexample | |
26401 | ||
26402 | The input types are | |
26403 | ||
26404 | @table @code | |
e5ac9b53 EZ |
26405 | @findex pre-prompt annotation |
26406 | @findex prompt annotation | |
26407 | @findex post-prompt annotation | |
922fbb7b AC |
26408 | @item prompt |
26409 | When @value{GDBN} is prompting for a command (the main @value{GDBN} prompt). | |
26410 | ||
e5ac9b53 EZ |
26411 | @findex pre-commands annotation |
26412 | @findex commands annotation | |
26413 | @findex post-commands annotation | |
922fbb7b AC |
26414 | @item commands |
26415 | When @value{GDBN} prompts for a set of commands, like in the @code{commands} | |
26416 | command. The annotations are repeated for each command which is input. | |
26417 | ||
e5ac9b53 EZ |
26418 | @findex pre-overload-choice annotation |
26419 | @findex overload-choice annotation | |
26420 | @findex post-overload-choice annotation | |
922fbb7b AC |
26421 | @item overload-choice |
26422 | When @value{GDBN} wants the user to select between various overloaded functions. | |
26423 | ||
e5ac9b53 EZ |
26424 | @findex pre-query annotation |
26425 | @findex query annotation | |
26426 | @findex post-query annotation | |
922fbb7b AC |
26427 | @item query |
26428 | When @value{GDBN} wants the user to confirm a potentially dangerous operation. | |
26429 | ||
e5ac9b53 EZ |
26430 | @findex pre-prompt-for-continue annotation |
26431 | @findex prompt-for-continue annotation | |
26432 | @findex post-prompt-for-continue annotation | |
922fbb7b AC |
26433 | @item prompt-for-continue |
26434 | When @value{GDBN} is asking the user to press return to continue. Note: Don't | |
26435 | expect this to work well; instead use @code{set height 0} to disable | |
26436 | prompting. This is because the counting of lines is buggy in the | |
26437 | presence of annotations. | |
26438 | @end table | |
26439 | ||
26440 | @node Errors | |
26441 | @section Errors | |
26442 | @cindex annotations for errors, warnings and interrupts | |
26443 | ||
e5ac9b53 | 26444 | @findex quit annotation |
922fbb7b AC |
26445 | @smallexample |
26446 | ^Z^Zquit | |
26447 | @end smallexample | |
26448 | ||
26449 | This annotation occurs right before @value{GDBN} responds to an interrupt. | |
26450 | ||
e5ac9b53 | 26451 | @findex error annotation |
922fbb7b AC |
26452 | @smallexample |
26453 | ^Z^Zerror | |
26454 | @end smallexample | |
26455 | ||
26456 | This annotation occurs right before @value{GDBN} responds to an error. | |
26457 | ||
26458 | Quit and error annotations indicate that any annotations which @value{GDBN} was | |
26459 | in the middle of may end abruptly. For example, if a | |
26460 | @code{value-history-begin} annotation is followed by a @code{error}, one | |
26461 | cannot expect to receive the matching @code{value-history-end}. One | |
26462 | cannot expect not to receive it either, however; an error annotation | |
26463 | does not necessarily mean that @value{GDBN} is immediately returning all the way | |
26464 | to the top level. | |
26465 | ||
e5ac9b53 | 26466 | @findex error-begin annotation |
922fbb7b AC |
26467 | A quit or error annotation may be preceded by |
26468 | ||
26469 | @smallexample | |
26470 | ^Z^Zerror-begin | |
26471 | @end smallexample | |
26472 | ||
26473 | Any output between that and the quit or error annotation is the error | |
26474 | message. | |
26475 | ||
26476 | Warning messages are not yet annotated. | |
26477 | @c If we want to change that, need to fix warning(), type_error(), | |
26478 | @c range_error(), and possibly other places. | |
26479 | ||
922fbb7b AC |
26480 | @node Invalidation |
26481 | @section Invalidation Notices | |
26482 | ||
26483 | @cindex annotations for invalidation messages | |
26484 | The following annotations say that certain pieces of state may have | |
26485 | changed. | |
26486 | ||
26487 | @table @code | |
e5ac9b53 | 26488 | @findex frames-invalid annotation |
922fbb7b AC |
26489 | @item ^Z^Zframes-invalid |
26490 | ||
26491 | The frames (for example, output from the @code{backtrace} command) may | |
26492 | have changed. | |
26493 | ||
e5ac9b53 | 26494 | @findex breakpoints-invalid annotation |
922fbb7b AC |
26495 | @item ^Z^Zbreakpoints-invalid |
26496 | ||
26497 | The breakpoints may have changed. For example, the user just added or | |
26498 | deleted a breakpoint. | |
26499 | @end table | |
26500 | ||
26501 | @node Annotations for Running | |
26502 | @section Running the Program | |
26503 | @cindex annotations for running programs | |
26504 | ||
e5ac9b53 EZ |
26505 | @findex starting annotation |
26506 | @findex stopping annotation | |
922fbb7b | 26507 | When the program starts executing due to a @value{GDBN} command such as |
b383017d | 26508 | @code{step} or @code{continue}, |
922fbb7b AC |
26509 | |
26510 | @smallexample | |
26511 | ^Z^Zstarting | |
26512 | @end smallexample | |
26513 | ||
b383017d | 26514 | is output. When the program stops, |
922fbb7b AC |
26515 | |
26516 | @smallexample | |
26517 | ^Z^Zstopped | |
26518 | @end smallexample | |
26519 | ||
26520 | is output. Before the @code{stopped} annotation, a variety of | |
26521 | annotations describe how the program stopped. | |
26522 | ||
26523 | @table @code | |
e5ac9b53 | 26524 | @findex exited annotation |
922fbb7b AC |
26525 | @item ^Z^Zexited @var{exit-status} |
26526 | The program exited, and @var{exit-status} is the exit status (zero for | |
26527 | successful exit, otherwise nonzero). | |
26528 | ||
e5ac9b53 EZ |
26529 | @findex signalled annotation |
26530 | @findex signal-name annotation | |
26531 | @findex signal-name-end annotation | |
26532 | @findex signal-string annotation | |
26533 | @findex signal-string-end annotation | |
922fbb7b AC |
26534 | @item ^Z^Zsignalled |
26535 | The program exited with a signal. After the @code{^Z^Zsignalled}, the | |
26536 | annotation continues: | |
26537 | ||
26538 | @smallexample | |
26539 | @var{intro-text} | |
26540 | ^Z^Zsignal-name | |
26541 | @var{name} | |
26542 | ^Z^Zsignal-name-end | |
26543 | @var{middle-text} | |
26544 | ^Z^Zsignal-string | |
26545 | @var{string} | |
26546 | ^Z^Zsignal-string-end | |
26547 | @var{end-text} | |
26548 | @end smallexample | |
26549 | ||
26550 | @noindent | |
26551 | where @var{name} is the name of the signal, such as @code{SIGILL} or | |
26552 | @code{SIGSEGV}, and @var{string} is the explanation of the signal, such | |
26553 | as @code{Illegal Instruction} or @code{Segmentation fault}. | |
26554 | @var{intro-text}, @var{middle-text}, and @var{end-text} are for the | |
26555 | user's benefit and have no particular format. | |
26556 | ||
e5ac9b53 | 26557 | @findex signal annotation |
922fbb7b AC |
26558 | @item ^Z^Zsignal |
26559 | The syntax of this annotation is just like @code{signalled}, but @value{GDBN} is | |
26560 | just saying that the program received the signal, not that it was | |
26561 | terminated with it. | |
26562 | ||
e5ac9b53 | 26563 | @findex breakpoint annotation |
922fbb7b AC |
26564 | @item ^Z^Zbreakpoint @var{number} |
26565 | The program hit breakpoint number @var{number}. | |
26566 | ||
e5ac9b53 | 26567 | @findex watchpoint annotation |
922fbb7b AC |
26568 | @item ^Z^Zwatchpoint @var{number} |
26569 | The program hit watchpoint number @var{number}. | |
26570 | @end table | |
26571 | ||
26572 | @node Source Annotations | |
26573 | @section Displaying Source | |
26574 | @cindex annotations for source display | |
26575 | ||
e5ac9b53 | 26576 | @findex source annotation |
922fbb7b AC |
26577 | The following annotation is used instead of displaying source code: |
26578 | ||
26579 | @smallexample | |
26580 | ^Z^Zsource @var{filename}:@var{line}:@var{character}:@var{middle}:@var{addr} | |
26581 | @end smallexample | |
26582 | ||
26583 | where @var{filename} is an absolute file name indicating which source | |
26584 | file, @var{line} is the line number within that file (where 1 is the | |
26585 | first line in the file), @var{character} is the character position | |
26586 | within the file (where 0 is the first character in the file) (for most | |
26587 | debug formats this will necessarily point to the beginning of a line), | |
26588 | @var{middle} is @samp{middle} if @var{addr} is in the middle of the | |
26589 | line, or @samp{beg} if @var{addr} is at the beginning of the line, and | |
26590 | @var{addr} is the address in the target program associated with the | |
26591 | source which is being displayed. @var{addr} is in the form @samp{0x} | |
26592 | followed by one or more lowercase hex digits (note that this does not | |
26593 | depend on the language). | |
26594 | ||
4efc6507 DE |
26595 | @node JIT Interface |
26596 | @chapter JIT Compilation Interface | |
26597 | @cindex just-in-time compilation | |
26598 | @cindex JIT compilation interface | |
26599 | ||
26600 | This chapter documents @value{GDBN}'s @dfn{just-in-time} (JIT) compilation | |
26601 | interface. A JIT compiler is a program or library that generates native | |
26602 | executable code at runtime and executes it, usually in order to achieve good | |
26603 | performance while maintaining platform independence. | |
26604 | ||
26605 | Programs that use JIT compilation are normally difficult to debug because | |
26606 | portions of their code are generated at runtime, instead of being loaded from | |
26607 | object files, which is where @value{GDBN} normally finds the program's symbols | |
26608 | and debug information. In order to debug programs that use JIT compilation, | |
26609 | @value{GDBN} has an interface that allows the program to register in-memory | |
26610 | symbol files with @value{GDBN} at runtime. | |
26611 | ||
26612 | If you are using @value{GDBN} to debug a program that uses this interface, then | |
26613 | it should work transparently so long as you have not stripped the binary. If | |
26614 | you are developing a JIT compiler, then the interface is documented in the rest | |
26615 | of this chapter. At this time, the only known client of this interface is the | |
26616 | LLVM JIT. | |
26617 | ||
26618 | Broadly speaking, the JIT interface mirrors the dynamic loader interface. The | |
26619 | JIT compiler communicates with @value{GDBN} by writing data into a global | |
26620 | variable and calling a fuction at a well-known symbol. When @value{GDBN} | |
26621 | attaches, it reads a linked list of symbol files from the global variable to | |
26622 | find existing code, and puts a breakpoint in the function so that it can find | |
26623 | out about additional code. | |
26624 | ||
26625 | @menu | |
26626 | * Declarations:: Relevant C struct declarations | |
26627 | * Registering Code:: Steps to register code | |
26628 | * Unregistering Code:: Steps to unregister code | |
26629 | @end menu | |
26630 | ||
26631 | @node Declarations | |
26632 | @section JIT Declarations | |
26633 | ||
26634 | These are the relevant struct declarations that a C program should include to | |
26635 | implement the interface: | |
26636 | ||
26637 | @smallexample | |
26638 | typedef enum | |
26639 | @{ | |
26640 | JIT_NOACTION = 0, | |
26641 | JIT_REGISTER_FN, | |
26642 | JIT_UNREGISTER_FN | |
26643 | @} jit_actions_t; | |
26644 | ||
26645 | struct jit_code_entry | |
26646 | @{ | |
26647 | struct jit_code_entry *next_entry; | |
26648 | struct jit_code_entry *prev_entry; | |
26649 | const char *symfile_addr; | |
26650 | uint64_t symfile_size; | |
26651 | @}; | |
26652 | ||
26653 | struct jit_descriptor | |
26654 | @{ | |
26655 | uint32_t version; | |
26656 | /* This type should be jit_actions_t, but we use uint32_t | |
26657 | to be explicit about the bitwidth. */ | |
26658 | uint32_t action_flag; | |
26659 | struct jit_code_entry *relevant_entry; | |
26660 | struct jit_code_entry *first_entry; | |
26661 | @}; | |
26662 | ||
26663 | /* GDB puts a breakpoint in this function. */ | |
26664 | void __attribute__((noinline)) __jit_debug_register_code() @{ @}; | |
26665 | ||
26666 | /* Make sure to specify the version statically, because the | |
26667 | debugger may check the version before we can set it. */ | |
26668 | struct jit_descriptor __jit_debug_descriptor = @{ 1, 0, 0, 0 @}; | |
26669 | @end smallexample | |
26670 | ||
26671 | If the JIT is multi-threaded, then it is important that the JIT synchronize any | |
26672 | modifications to this global data properly, which can easily be done by putting | |
26673 | a global mutex around modifications to these structures. | |
26674 | ||
26675 | @node Registering Code | |
26676 | @section Registering Code | |
26677 | ||
26678 | To register code with @value{GDBN}, the JIT should follow this protocol: | |
26679 | ||
26680 | @itemize @bullet | |
26681 | @item | |
26682 | Generate an object file in memory with symbols and other desired debug | |
26683 | information. The file must include the virtual addresses of the sections. | |
26684 | ||
26685 | @item | |
26686 | Create a code entry for the file, which gives the start and size of the symbol | |
26687 | file. | |
26688 | ||
26689 | @item | |
26690 | Add it to the linked list in the JIT descriptor. | |
26691 | ||
26692 | @item | |
26693 | Point the relevant_entry field of the descriptor at the entry. | |
26694 | ||
26695 | @item | |
26696 | Set @code{action_flag} to @code{JIT_REGISTER} and call | |
26697 | @code{__jit_debug_register_code}. | |
26698 | @end itemize | |
26699 | ||
26700 | When @value{GDBN} is attached and the breakpoint fires, @value{GDBN} uses the | |
26701 | @code{relevant_entry} pointer so it doesn't have to walk the list looking for | |
26702 | new code. However, the linked list must still be maintained in order to allow | |
26703 | @value{GDBN} to attach to a running process and still find the symbol files. | |
26704 | ||
26705 | @node Unregistering Code | |
26706 | @section Unregistering Code | |
26707 | ||
26708 | If code is freed, then the JIT should use the following protocol: | |
26709 | ||
26710 | @itemize @bullet | |
26711 | @item | |
26712 | Remove the code entry corresponding to the code from the linked list. | |
26713 | ||
26714 | @item | |
26715 | Point the @code{relevant_entry} field of the descriptor at the code entry. | |
26716 | ||
26717 | @item | |
26718 | Set @code{action_flag} to @code{JIT_UNREGISTER} and call | |
26719 | @code{__jit_debug_register_code}. | |
26720 | @end itemize | |
26721 | ||
26722 | If the JIT frees or recompiles code without unregistering it, then @value{GDBN} | |
26723 | and the JIT will leak the memory used for the associated symbol files. | |
26724 | ||
8e04817f AC |
26725 | @node GDB Bugs |
26726 | @chapter Reporting Bugs in @value{GDBN} | |
26727 | @cindex bugs in @value{GDBN} | |
26728 | @cindex reporting bugs in @value{GDBN} | |
c906108c | 26729 | |
8e04817f | 26730 | Your bug reports play an essential role in making @value{GDBN} reliable. |
c906108c | 26731 | |
8e04817f AC |
26732 | Reporting a bug may help you by bringing a solution to your problem, or it |
26733 | may not. But in any case the principal function of a bug report is to help | |
26734 | the entire community by making the next version of @value{GDBN} work better. Bug | |
26735 | reports are your contribution to the maintenance of @value{GDBN}. | |
c906108c | 26736 | |
8e04817f AC |
26737 | In order for a bug report to serve its purpose, you must include the |
26738 | information that enables us to fix the bug. | |
c4555f82 SC |
26739 | |
26740 | @menu | |
8e04817f AC |
26741 | * Bug Criteria:: Have you found a bug? |
26742 | * Bug Reporting:: How to report bugs | |
c4555f82 SC |
26743 | @end menu |
26744 | ||
8e04817f | 26745 | @node Bug Criteria |
79a6e687 | 26746 | @section Have You Found a Bug? |
8e04817f | 26747 | @cindex bug criteria |
c4555f82 | 26748 | |
8e04817f | 26749 | If you are not sure whether you have found a bug, here are some guidelines: |
c4555f82 SC |
26750 | |
26751 | @itemize @bullet | |
8e04817f AC |
26752 | @cindex fatal signal |
26753 | @cindex debugger crash | |
26754 | @cindex crash of debugger | |
c4555f82 | 26755 | @item |
8e04817f AC |
26756 | If the debugger gets a fatal signal, for any input whatever, that is a |
26757 | @value{GDBN} bug. Reliable debuggers never crash. | |
26758 | ||
26759 | @cindex error on valid input | |
26760 | @item | |
26761 | If @value{GDBN} produces an error message for valid input, that is a | |
26762 | bug. (Note that if you're cross debugging, the problem may also be | |
26763 | somewhere in the connection to the target.) | |
c4555f82 | 26764 | |
8e04817f | 26765 | @cindex invalid input |
c4555f82 | 26766 | @item |
8e04817f AC |
26767 | If @value{GDBN} does not produce an error message for invalid input, |
26768 | that is a bug. However, you should note that your idea of | |
26769 | ``invalid input'' might be our idea of ``an extension'' or ``support | |
26770 | for traditional practice''. | |
26771 | ||
26772 | @item | |
26773 | If you are an experienced user of debugging tools, your suggestions | |
26774 | for improvement of @value{GDBN} are welcome in any case. | |
c4555f82 SC |
26775 | @end itemize |
26776 | ||
8e04817f | 26777 | @node Bug Reporting |
79a6e687 | 26778 | @section How to Report Bugs |
8e04817f AC |
26779 | @cindex bug reports |
26780 | @cindex @value{GDBN} bugs, reporting | |
26781 | ||
26782 | A number of companies and individuals offer support for @sc{gnu} products. | |
26783 | If you obtained @value{GDBN} from a support organization, we recommend you | |
26784 | contact that organization first. | |
26785 | ||
26786 | You can find contact information for many support companies and | |
26787 | individuals in the file @file{etc/SERVICE} in the @sc{gnu} Emacs | |
26788 | distribution. | |
26789 | @c should add a web page ref... | |
26790 | ||
c16158bc JM |
26791 | @ifset BUGURL |
26792 | @ifset BUGURL_DEFAULT | |
129188f6 | 26793 | In any event, we also recommend that you submit bug reports for |
d3e8051b | 26794 | @value{GDBN}. The preferred method is to submit them directly using |
129188f6 AC |
26795 | @uref{http://www.gnu.org/software/gdb/bugs/, @value{GDBN}'s Bugs web |
26796 | page}. Alternatively, the @email{bug-gdb@@gnu.org, e-mail gateway} can | |
26797 | be used. | |
8e04817f AC |
26798 | |
26799 | @strong{Do not send bug reports to @samp{info-gdb}, or to | |
26800 | @samp{help-gdb}, or to any newsgroups.} Most users of @value{GDBN} do | |
26801 | not want to receive bug reports. Those that do have arranged to receive | |
26802 | @samp{bug-gdb}. | |
26803 | ||
26804 | The mailing list @samp{bug-gdb} has a newsgroup @samp{gnu.gdb.bug} which | |
26805 | serves as a repeater. The mailing list and the newsgroup carry exactly | |
26806 | the same messages. Often people think of posting bug reports to the | |
26807 | newsgroup instead of mailing them. This appears to work, but it has one | |
26808 | problem which can be crucial: a newsgroup posting often lacks a mail | |
26809 | path back to the sender. Thus, if we need to ask for more information, | |
26810 | we may be unable to reach you. For this reason, it is better to send | |
26811 | bug reports to the mailing list. | |
c16158bc JM |
26812 | @end ifset |
26813 | @ifclear BUGURL_DEFAULT | |
26814 | In any event, we also recommend that you submit bug reports for | |
26815 | @value{GDBN} to @value{BUGURL}. | |
26816 | @end ifclear | |
26817 | @end ifset | |
c4555f82 | 26818 | |
8e04817f AC |
26819 | The fundamental principle of reporting bugs usefully is this: |
26820 | @strong{report all the facts}. If you are not sure whether to state a | |
26821 | fact or leave it out, state it! | |
c4555f82 | 26822 | |
8e04817f AC |
26823 | Often people omit facts because they think they know what causes the |
26824 | problem and assume that some details do not matter. Thus, you might | |
26825 | assume that the name of the variable you use in an example does not matter. | |
26826 | Well, probably it does not, but one cannot be sure. Perhaps the bug is a | |
26827 | stray memory reference which happens to fetch from the location where that | |
26828 | name is stored in memory; perhaps, if the name were different, the contents | |
26829 | of that location would fool the debugger into doing the right thing despite | |
26830 | the bug. Play it safe and give a specific, complete example. That is the | |
26831 | easiest thing for you to do, and the most helpful. | |
c4555f82 | 26832 | |
8e04817f AC |
26833 | Keep in mind that the purpose of a bug report is to enable us to fix the |
26834 | bug. It may be that the bug has been reported previously, but neither | |
26835 | you nor we can know that unless your bug report is complete and | |
26836 | self-contained. | |
c4555f82 | 26837 | |
8e04817f AC |
26838 | Sometimes people give a few sketchy facts and ask, ``Does this ring a |
26839 | bell?'' Those bug reports are useless, and we urge everyone to | |
26840 | @emph{refuse to respond to them} except to chide the sender to report | |
26841 | bugs properly. | |
26842 | ||
26843 | To enable us to fix the bug, you should include all these things: | |
c4555f82 SC |
26844 | |
26845 | @itemize @bullet | |
26846 | @item | |
8e04817f AC |
26847 | The version of @value{GDBN}. @value{GDBN} announces it if you start |
26848 | with no arguments; you can also print it at any time using @code{show | |
26849 | version}. | |
c4555f82 | 26850 | |
8e04817f AC |
26851 | Without this, we will not know whether there is any point in looking for |
26852 | the bug in the current version of @value{GDBN}. | |
c4555f82 SC |
26853 | |
26854 | @item | |
8e04817f AC |
26855 | The type of machine you are using, and the operating system name and |
26856 | version number. | |
c4555f82 SC |
26857 | |
26858 | @item | |
c1468174 | 26859 | What compiler (and its version) was used to compile @value{GDBN}---e.g.@: |
8e04817f | 26860 | ``@value{GCC}--2.8.1''. |
c4555f82 SC |
26861 | |
26862 | @item | |
8e04817f | 26863 | What compiler (and its version) was used to compile the program you are |
c1468174 | 26864 | debugging---e.g.@: ``@value{GCC}--2.8.1'', or ``HP92453-01 A.10.32.03 HP |
3f94c067 BW |
26865 | C Compiler''. For @value{NGCC}, you can say @kbd{@value{GCC} --version} |
26866 | to get this information; for other compilers, see the documentation for | |
26867 | those compilers. | |
c4555f82 | 26868 | |
8e04817f AC |
26869 | @item |
26870 | The command arguments you gave the compiler to compile your example and | |
26871 | observe the bug. For example, did you use @samp{-O}? To guarantee | |
26872 | you will not omit something important, list them all. A copy of the | |
26873 | Makefile (or the output from make) is sufficient. | |
c4555f82 | 26874 | |
8e04817f AC |
26875 | If we were to try to guess the arguments, we would probably guess wrong |
26876 | and then we might not encounter the bug. | |
c4555f82 | 26877 | |
8e04817f AC |
26878 | @item |
26879 | A complete input script, and all necessary source files, that will | |
26880 | reproduce the bug. | |
c4555f82 | 26881 | |
8e04817f AC |
26882 | @item |
26883 | A description of what behavior you observe that you believe is | |
26884 | incorrect. For example, ``It gets a fatal signal.'' | |
c4555f82 | 26885 | |
8e04817f AC |
26886 | Of course, if the bug is that @value{GDBN} gets a fatal signal, then we |
26887 | will certainly notice it. But if the bug is incorrect output, we might | |
26888 | not notice unless it is glaringly wrong. You might as well not give us | |
26889 | a chance to make a mistake. | |
c4555f82 | 26890 | |
8e04817f AC |
26891 | Even if the problem you experience is a fatal signal, you should still |
26892 | say so explicitly. Suppose something strange is going on, such as, your | |
26893 | copy of @value{GDBN} is out of synch, or you have encountered a bug in | |
26894 | the C library on your system. (This has happened!) Your copy might | |
26895 | crash and ours would not. If you told us to expect a crash, then when | |
26896 | ours fails to crash, we would know that the bug was not happening for | |
26897 | us. If you had not told us to expect a crash, then we would not be able | |
26898 | to draw any conclusion from our observations. | |
c4555f82 | 26899 | |
e0c07bf0 MC |
26900 | @pindex script |
26901 | @cindex recording a session script | |
26902 | To collect all this information, you can use a session recording program | |
26903 | such as @command{script}, which is available on many Unix systems. | |
26904 | Just run your @value{GDBN} session inside @command{script} and then | |
26905 | include the @file{typescript} file with your bug report. | |
26906 | ||
26907 | Another way to record a @value{GDBN} session is to run @value{GDBN} | |
26908 | inside Emacs and then save the entire buffer to a file. | |
26909 | ||
8e04817f AC |
26910 | @item |
26911 | If you wish to suggest changes to the @value{GDBN} source, send us context | |
26912 | diffs. If you even discuss something in the @value{GDBN} source, refer to | |
26913 | it by context, not by line number. | |
c4555f82 | 26914 | |
8e04817f AC |
26915 | The line numbers in our development sources will not match those in your |
26916 | sources. Your line numbers would convey no useful information to us. | |
c4555f82 | 26917 | |
8e04817f | 26918 | @end itemize |
c4555f82 | 26919 | |
8e04817f | 26920 | Here are some things that are not necessary: |
c4555f82 | 26921 | |
8e04817f AC |
26922 | @itemize @bullet |
26923 | @item | |
26924 | A description of the envelope of the bug. | |
c4555f82 | 26925 | |
8e04817f AC |
26926 | Often people who encounter a bug spend a lot of time investigating |
26927 | which changes to the input file will make the bug go away and which | |
26928 | changes will not affect it. | |
c4555f82 | 26929 | |
8e04817f AC |
26930 | This is often time consuming and not very useful, because the way we |
26931 | will find the bug is by running a single example under the debugger | |
26932 | with breakpoints, not by pure deduction from a series of examples. | |
26933 | We recommend that you save your time for something else. | |
c4555f82 | 26934 | |
8e04817f AC |
26935 | Of course, if you can find a simpler example to report @emph{instead} |
26936 | of the original one, that is a convenience for us. Errors in the | |
26937 | output will be easier to spot, running under the debugger will take | |
26938 | less time, and so on. | |
c4555f82 | 26939 | |
8e04817f AC |
26940 | However, simplification is not vital; if you do not want to do this, |
26941 | report the bug anyway and send us the entire test case you used. | |
c4555f82 | 26942 | |
8e04817f AC |
26943 | @item |
26944 | A patch for the bug. | |
c4555f82 | 26945 | |
8e04817f AC |
26946 | A patch for the bug does help us if it is a good one. But do not omit |
26947 | the necessary information, such as the test case, on the assumption that | |
26948 | a patch is all we need. We might see problems with your patch and decide | |
26949 | to fix the problem another way, or we might not understand it at all. | |
c4555f82 | 26950 | |
8e04817f AC |
26951 | Sometimes with a program as complicated as @value{GDBN} it is very hard to |
26952 | construct an example that will make the program follow a certain path | |
26953 | through the code. If you do not send us the example, we will not be able | |
26954 | to construct one, so we will not be able to verify that the bug is fixed. | |
c4555f82 | 26955 | |
8e04817f AC |
26956 | And if we cannot understand what bug you are trying to fix, or why your |
26957 | patch should be an improvement, we will not install it. A test case will | |
26958 | help us to understand. | |
c4555f82 | 26959 | |
8e04817f AC |
26960 | @item |
26961 | A guess about what the bug is or what it depends on. | |
c4555f82 | 26962 | |
8e04817f AC |
26963 | Such guesses are usually wrong. Even we cannot guess right about such |
26964 | things without first using the debugger to find the facts. | |
26965 | @end itemize | |
c4555f82 | 26966 | |
8e04817f AC |
26967 | @c The readline documentation is distributed with the readline code |
26968 | @c and consists of the two following files: | |
26969 | @c rluser.texinfo | |
26970 | @c inc-hist.texinfo | |
26971 | @c Use -I with makeinfo to point to the appropriate directory, | |
26972 | @c environment var TEXINPUTS with TeX. | |
5bdf8622 | 26973 | @include rluser.texi |
8e04817f | 26974 | @include inc-hist.texinfo |
c4555f82 | 26975 | |
c4555f82 | 26976 | |
8e04817f AC |
26977 | @node Formatting Documentation |
26978 | @appendix Formatting Documentation | |
c4555f82 | 26979 | |
8e04817f AC |
26980 | @cindex @value{GDBN} reference card |
26981 | @cindex reference card | |
26982 | The @value{GDBN} 4 release includes an already-formatted reference card, ready | |
26983 | for printing with PostScript or Ghostscript, in the @file{gdb} | |
26984 | subdirectory of the main source directory@footnote{In | |
26985 | @file{gdb-@value{GDBVN}/gdb/refcard.ps} of the version @value{GDBVN} | |
26986 | release.}. If you can use PostScript or Ghostscript with your printer, | |
26987 | you can print the reference card immediately with @file{refcard.ps}. | |
c4555f82 | 26988 | |
8e04817f AC |
26989 | The release also includes the source for the reference card. You |
26990 | can format it, using @TeX{}, by typing: | |
c4555f82 | 26991 | |
474c8240 | 26992 | @smallexample |
8e04817f | 26993 | make refcard.dvi |
474c8240 | 26994 | @end smallexample |
c4555f82 | 26995 | |
8e04817f AC |
26996 | The @value{GDBN} reference card is designed to print in @dfn{landscape} |
26997 | mode on US ``letter'' size paper; | |
26998 | that is, on a sheet 11 inches wide by 8.5 inches | |
26999 | high. You will need to specify this form of printing as an option to | |
27000 | your @sc{dvi} output program. | |
c4555f82 | 27001 | |
8e04817f | 27002 | @cindex documentation |
c4555f82 | 27003 | |
8e04817f AC |
27004 | All the documentation for @value{GDBN} comes as part of the machine-readable |
27005 | distribution. The documentation is written in Texinfo format, which is | |
27006 | a documentation system that uses a single source file to produce both | |
27007 | on-line information and a printed manual. You can use one of the Info | |
27008 | formatting commands to create the on-line version of the documentation | |
27009 | and @TeX{} (or @code{texi2roff}) to typeset the printed version. | |
c4555f82 | 27010 | |
8e04817f AC |
27011 | @value{GDBN} includes an already formatted copy of the on-line Info |
27012 | version of this manual in the @file{gdb} subdirectory. The main Info | |
27013 | file is @file{gdb-@value{GDBVN}/gdb/gdb.info}, and it refers to | |
27014 | subordinate files matching @samp{gdb.info*} in the same directory. If | |
27015 | necessary, you can print out these files, or read them with any editor; | |
27016 | but they are easier to read using the @code{info} subsystem in @sc{gnu} | |
27017 | Emacs or the standalone @code{info} program, available as part of the | |
27018 | @sc{gnu} Texinfo distribution. | |
c4555f82 | 27019 | |
8e04817f AC |
27020 | If you want to format these Info files yourself, you need one of the |
27021 | Info formatting programs, such as @code{texinfo-format-buffer} or | |
27022 | @code{makeinfo}. | |
c4555f82 | 27023 | |
8e04817f AC |
27024 | If you have @code{makeinfo} installed, and are in the top level |
27025 | @value{GDBN} source directory (@file{gdb-@value{GDBVN}}, in the case of | |
27026 | version @value{GDBVN}), you can make the Info file by typing: | |
c4555f82 | 27027 | |
474c8240 | 27028 | @smallexample |
8e04817f AC |
27029 | cd gdb |
27030 | make gdb.info | |
474c8240 | 27031 | @end smallexample |
c4555f82 | 27032 | |
8e04817f AC |
27033 | If you want to typeset and print copies of this manual, you need @TeX{}, |
27034 | a program to print its @sc{dvi} output files, and @file{texinfo.tex}, the | |
27035 | Texinfo definitions file. | |
c4555f82 | 27036 | |
8e04817f AC |
27037 | @TeX{} is a typesetting program; it does not print files directly, but |
27038 | produces output files called @sc{dvi} files. To print a typeset | |
27039 | document, you need a program to print @sc{dvi} files. If your system | |
27040 | has @TeX{} installed, chances are it has such a program. The precise | |
27041 | command to use depends on your system; @kbd{lpr -d} is common; another | |
27042 | (for PostScript devices) is @kbd{dvips}. The @sc{dvi} print command may | |
27043 | require a file name without any extension or a @samp{.dvi} extension. | |
c4555f82 | 27044 | |
8e04817f AC |
27045 | @TeX{} also requires a macro definitions file called |
27046 | @file{texinfo.tex}. This file tells @TeX{} how to typeset a document | |
27047 | written in Texinfo format. On its own, @TeX{} cannot either read or | |
27048 | typeset a Texinfo file. @file{texinfo.tex} is distributed with GDB | |
27049 | and is located in the @file{gdb-@var{version-number}/texinfo} | |
27050 | directory. | |
c4555f82 | 27051 | |
8e04817f | 27052 | If you have @TeX{} and a @sc{dvi} printer program installed, you can |
d3e8051b | 27053 | typeset and print this manual. First switch to the @file{gdb} |
8e04817f AC |
27054 | subdirectory of the main source directory (for example, to |
27055 | @file{gdb-@value{GDBVN}/gdb}) and type: | |
c4555f82 | 27056 | |
474c8240 | 27057 | @smallexample |
8e04817f | 27058 | make gdb.dvi |
474c8240 | 27059 | @end smallexample |
c4555f82 | 27060 | |
8e04817f | 27061 | Then give @file{gdb.dvi} to your @sc{dvi} printing program. |
c4555f82 | 27062 | |
8e04817f AC |
27063 | @node Installing GDB |
27064 | @appendix Installing @value{GDBN} | |
8e04817f | 27065 | @cindex installation |
c4555f82 | 27066 | |
7fa2210b DJ |
27067 | @menu |
27068 | * Requirements:: Requirements for building @value{GDBN} | |
db2e3e2e | 27069 | * Running Configure:: Invoking the @value{GDBN} @file{configure} script |
7fa2210b DJ |
27070 | * Separate Objdir:: Compiling @value{GDBN} in another directory |
27071 | * Config Names:: Specifying names for hosts and targets | |
27072 | * Configure Options:: Summary of options for configure | |
098b41a6 | 27073 | * System-wide configuration:: Having a system-wide init file |
7fa2210b DJ |
27074 | @end menu |
27075 | ||
27076 | @node Requirements | |
79a6e687 | 27077 | @section Requirements for Building @value{GDBN} |
7fa2210b DJ |
27078 | @cindex building @value{GDBN}, requirements for |
27079 | ||
27080 | Building @value{GDBN} requires various tools and packages to be available. | |
27081 | Other packages will be used only if they are found. | |
27082 | ||
79a6e687 | 27083 | @heading Tools/Packages Necessary for Building @value{GDBN} |
7fa2210b DJ |
27084 | @table @asis |
27085 | @item ISO C90 compiler | |
27086 | @value{GDBN} is written in ISO C90. It should be buildable with any | |
27087 | working C90 compiler, e.g.@: GCC. | |
27088 | ||
27089 | @end table | |
27090 | ||
79a6e687 | 27091 | @heading Tools/Packages Optional for Building @value{GDBN} |
7fa2210b DJ |
27092 | @table @asis |
27093 | @item Expat | |
123dc839 | 27094 | @anchor{Expat} |
7fa2210b DJ |
27095 | @value{GDBN} can use the Expat XML parsing library. This library may be |
27096 | included with your operating system distribution; if it is not, you | |
27097 | can get the latest version from @url{http://expat.sourceforge.net}. | |
db2e3e2e | 27098 | The @file{configure} script will search for this library in several |
7fa2210b DJ |
27099 | standard locations; if it is installed in an unusual path, you can |
27100 | use the @option{--with-libexpat-prefix} option to specify its location. | |
27101 | ||
9cceb671 DJ |
27102 | Expat is used for: |
27103 | ||
27104 | @itemize @bullet | |
27105 | @item | |
27106 | Remote protocol memory maps (@pxref{Memory Map Format}) | |
27107 | @item | |
27108 | Target descriptions (@pxref{Target Descriptions}) | |
27109 | @item | |
27110 | Remote shared library lists (@pxref{Library List Format}) | |
27111 | @item | |
27112 | MS-Windows shared libraries (@pxref{Shared Libraries}) | |
27113 | @end itemize | |
7fa2210b | 27114 | |
31fffb02 CS |
27115 | @item zlib |
27116 | @cindex compressed debug sections | |
27117 | @value{GDBN} will use the @samp{zlib} library, if available, to read | |
27118 | compressed debug sections. Some linkers, such as GNU gold, are capable | |
27119 | of producing binaries with compressed debug sections. If @value{GDBN} | |
27120 | is compiled with @samp{zlib}, it will be able to read the debug | |
27121 | information in such binaries. | |
27122 | ||
27123 | The @samp{zlib} library is likely included with your operating system | |
27124 | distribution; if it is not, you can get the latest version from | |
27125 | @url{http://zlib.net}. | |
27126 | ||
6c7a06a3 TT |
27127 | @item iconv |
27128 | @value{GDBN}'s features related to character sets (@pxref{Character | |
27129 | Sets}) require a functioning @code{iconv} implementation. If you are | |
27130 | on a GNU system, then this is provided by the GNU C Library. Some | |
27131 | other systems also provide a working @code{iconv}. | |
27132 | ||
27133 | On systems with @code{iconv}, you can install GNU Libiconv. If you | |
27134 | have previously installed Libiconv, you can use the | |
27135 | @option{--with-libiconv-prefix} option to configure. | |
27136 | ||
27137 | @value{GDBN}'s top-level @file{configure} and @file{Makefile} will | |
27138 | arrange to build Libiconv if a directory named @file{libiconv} appears | |
27139 | in the top-most source directory. If Libiconv is built this way, and | |
27140 | if the operating system does not provide a suitable @code{iconv} | |
27141 | implementation, then the just-built library will automatically be used | |
27142 | by @value{GDBN}. One easy way to set this up is to download GNU | |
27143 | Libiconv, unpack it, and then rename the directory holding the | |
27144 | Libiconv source code to @samp{libiconv}. | |
7fa2210b DJ |
27145 | @end table |
27146 | ||
27147 | @node Running Configure | |
db2e3e2e | 27148 | @section Invoking the @value{GDBN} @file{configure} Script |
7fa2210b | 27149 | @cindex configuring @value{GDBN} |
db2e3e2e | 27150 | @value{GDBN} comes with a @file{configure} script that automates the process |
8e04817f AC |
27151 | of preparing @value{GDBN} for installation; you can then use @code{make} to |
27152 | build the @code{gdb} program. | |
27153 | @iftex | |
27154 | @c irrelevant in info file; it's as current as the code it lives with. | |
27155 | @footnote{If you have a more recent version of @value{GDBN} than @value{GDBVN}, | |
27156 | look at the @file{README} file in the sources; we may have improved the | |
27157 | installation procedures since publishing this manual.} | |
27158 | @end iftex | |
c4555f82 | 27159 | |
8e04817f AC |
27160 | The @value{GDBN} distribution includes all the source code you need for |
27161 | @value{GDBN} in a single directory, whose name is usually composed by | |
27162 | appending the version number to @samp{gdb}. | |
c4555f82 | 27163 | |
8e04817f AC |
27164 | For example, the @value{GDBN} version @value{GDBVN} distribution is in the |
27165 | @file{gdb-@value{GDBVN}} directory. That directory contains: | |
c4555f82 | 27166 | |
8e04817f AC |
27167 | @table @code |
27168 | @item gdb-@value{GDBVN}/configure @r{(and supporting files)} | |
27169 | script for configuring @value{GDBN} and all its supporting libraries | |
c4555f82 | 27170 | |
8e04817f AC |
27171 | @item gdb-@value{GDBVN}/gdb |
27172 | the source specific to @value{GDBN} itself | |
c4555f82 | 27173 | |
8e04817f AC |
27174 | @item gdb-@value{GDBVN}/bfd |
27175 | source for the Binary File Descriptor library | |
c906108c | 27176 | |
8e04817f AC |
27177 | @item gdb-@value{GDBVN}/include |
27178 | @sc{gnu} include files | |
c906108c | 27179 | |
8e04817f AC |
27180 | @item gdb-@value{GDBVN}/libiberty |
27181 | source for the @samp{-liberty} free software library | |
c906108c | 27182 | |
8e04817f AC |
27183 | @item gdb-@value{GDBVN}/opcodes |
27184 | source for the library of opcode tables and disassemblers | |
c906108c | 27185 | |
8e04817f AC |
27186 | @item gdb-@value{GDBVN}/readline |
27187 | source for the @sc{gnu} command-line interface | |
c906108c | 27188 | |
8e04817f AC |
27189 | @item gdb-@value{GDBVN}/glob |
27190 | source for the @sc{gnu} filename pattern-matching subroutine | |
c906108c | 27191 | |
8e04817f AC |
27192 | @item gdb-@value{GDBVN}/mmalloc |
27193 | source for the @sc{gnu} memory-mapped malloc package | |
27194 | @end table | |
c906108c | 27195 | |
db2e3e2e | 27196 | The simplest way to configure and build @value{GDBN} is to run @file{configure} |
8e04817f AC |
27197 | from the @file{gdb-@var{version-number}} source directory, which in |
27198 | this example is the @file{gdb-@value{GDBVN}} directory. | |
c906108c | 27199 | |
8e04817f | 27200 | First switch to the @file{gdb-@var{version-number}} source directory |
db2e3e2e | 27201 | if you are not already in it; then run @file{configure}. Pass the |
8e04817f AC |
27202 | identifier for the platform on which @value{GDBN} will run as an |
27203 | argument. | |
c906108c | 27204 | |
8e04817f | 27205 | For example: |
c906108c | 27206 | |
474c8240 | 27207 | @smallexample |
8e04817f AC |
27208 | cd gdb-@value{GDBVN} |
27209 | ./configure @var{host} | |
27210 | make | |
474c8240 | 27211 | @end smallexample |
c906108c | 27212 | |
8e04817f AC |
27213 | @noindent |
27214 | where @var{host} is an identifier such as @samp{sun4} or | |
27215 | @samp{decstation}, that identifies the platform where @value{GDBN} will run. | |
db2e3e2e | 27216 | (You can often leave off @var{host}; @file{configure} tries to guess the |
8e04817f | 27217 | correct value by examining your system.) |
c906108c | 27218 | |
8e04817f AC |
27219 | Running @samp{configure @var{host}} and then running @code{make} builds the |
27220 | @file{bfd}, @file{readline}, @file{mmalloc}, and @file{libiberty} | |
27221 | libraries, then @code{gdb} itself. The configured source files, and the | |
27222 | binaries, are left in the corresponding source directories. | |
c906108c | 27223 | |
8e04817f | 27224 | @need 750 |
db2e3e2e | 27225 | @file{configure} is a Bourne-shell (@code{/bin/sh}) script; if your |
8e04817f AC |
27226 | system does not recognize this automatically when you run a different |
27227 | shell, you may need to run @code{sh} on it explicitly: | |
c906108c | 27228 | |
474c8240 | 27229 | @smallexample |
8e04817f | 27230 | sh configure @var{host} |
474c8240 | 27231 | @end smallexample |
c906108c | 27232 | |
db2e3e2e | 27233 | If you run @file{configure} from a directory that contains source |
8e04817f | 27234 | directories for multiple libraries or programs, such as the |
db2e3e2e BW |
27235 | @file{gdb-@value{GDBVN}} source directory for version @value{GDBVN}, |
27236 | @file{configure} | |
8e04817f AC |
27237 | creates configuration files for every directory level underneath (unless |
27238 | you tell it not to, with the @samp{--norecursion} option). | |
27239 | ||
db2e3e2e | 27240 | You should run the @file{configure} script from the top directory in the |
94e91d6d | 27241 | source tree, the @file{gdb-@var{version-number}} directory. If you run |
db2e3e2e | 27242 | @file{configure} from one of the subdirectories, you will configure only |
94e91d6d | 27243 | that subdirectory. That is usually not what you want. In particular, |
db2e3e2e | 27244 | if you run the first @file{configure} from the @file{gdb} subdirectory |
94e91d6d MC |
27245 | of the @file{gdb-@var{version-number}} directory, you will omit the |
27246 | configuration of @file{bfd}, @file{readline}, and other sibling | |
27247 | directories of the @file{gdb} subdirectory. This leads to build errors | |
27248 | about missing include files such as @file{bfd/bfd.h}. | |
c906108c | 27249 | |
8e04817f AC |
27250 | You can install @code{@value{GDBP}} anywhere; it has no hardwired paths. |
27251 | However, you should make sure that the shell on your path (named by | |
27252 | the @samp{SHELL} environment variable) is publicly readable. Remember | |
27253 | that @value{GDBN} uses the shell to start your program---some systems refuse to | |
27254 | let @value{GDBN} debug child processes whose programs are not readable. | |
c906108c | 27255 | |
8e04817f | 27256 | @node Separate Objdir |
79a6e687 | 27257 | @section Compiling @value{GDBN} in Another Directory |
c906108c | 27258 | |
8e04817f AC |
27259 | If you want to run @value{GDBN} versions for several host or target machines, |
27260 | you need a different @code{gdb} compiled for each combination of | |
db2e3e2e | 27261 | host and target. @file{configure} is designed to make this easy by |
8e04817f AC |
27262 | allowing you to generate each configuration in a separate subdirectory, |
27263 | rather than in the source directory. If your @code{make} program | |
27264 | handles the @samp{VPATH} feature (@sc{gnu} @code{make} does), running | |
27265 | @code{make} in each of these directories builds the @code{gdb} | |
27266 | program specified there. | |
c906108c | 27267 | |
db2e3e2e | 27268 | To build @code{gdb} in a separate directory, run @file{configure} |
8e04817f | 27269 | with the @samp{--srcdir} option to specify where to find the source. |
db2e3e2e BW |
27270 | (You also need to specify a path to find @file{configure} |
27271 | itself from your working directory. If the path to @file{configure} | |
8e04817f AC |
27272 | would be the same as the argument to @samp{--srcdir}, you can leave out |
27273 | the @samp{--srcdir} option; it is assumed.) | |
c906108c | 27274 | |
8e04817f AC |
27275 | For example, with version @value{GDBVN}, you can build @value{GDBN} in a |
27276 | separate directory for a Sun 4 like this: | |
c906108c | 27277 | |
474c8240 | 27278 | @smallexample |
8e04817f AC |
27279 | @group |
27280 | cd gdb-@value{GDBVN} | |
27281 | mkdir ../gdb-sun4 | |
27282 | cd ../gdb-sun4 | |
27283 | ../gdb-@value{GDBVN}/configure sun4 | |
27284 | make | |
27285 | @end group | |
474c8240 | 27286 | @end smallexample |
c906108c | 27287 | |
db2e3e2e | 27288 | When @file{configure} builds a configuration using a remote source |
8e04817f AC |
27289 | directory, it creates a tree for the binaries with the same structure |
27290 | (and using the same names) as the tree under the source directory. In | |
27291 | the example, you'd find the Sun 4 library @file{libiberty.a} in the | |
27292 | directory @file{gdb-sun4/libiberty}, and @value{GDBN} itself in | |
27293 | @file{gdb-sun4/gdb}. | |
c906108c | 27294 | |
94e91d6d MC |
27295 | Make sure that your path to the @file{configure} script has just one |
27296 | instance of @file{gdb} in it. If your path to @file{configure} looks | |
27297 | like @file{../gdb-@value{GDBVN}/gdb/configure}, you are configuring only | |
27298 | one subdirectory of @value{GDBN}, not the whole package. This leads to | |
27299 | build errors about missing include files such as @file{bfd/bfd.h}. | |
27300 | ||
8e04817f AC |
27301 | One popular reason to build several @value{GDBN} configurations in separate |
27302 | directories is to configure @value{GDBN} for cross-compiling (where | |
27303 | @value{GDBN} runs on one machine---the @dfn{host}---while debugging | |
27304 | programs that run on another machine---the @dfn{target}). | |
27305 | You specify a cross-debugging target by | |
db2e3e2e | 27306 | giving the @samp{--target=@var{target}} option to @file{configure}. |
c906108c | 27307 | |
8e04817f AC |
27308 | When you run @code{make} to build a program or library, you must run |
27309 | it in a configured directory---whatever directory you were in when you | |
db2e3e2e | 27310 | called @file{configure} (or one of its subdirectories). |
c906108c | 27311 | |
db2e3e2e | 27312 | The @code{Makefile} that @file{configure} generates in each source |
8e04817f AC |
27313 | directory also runs recursively. If you type @code{make} in a source |
27314 | directory such as @file{gdb-@value{GDBVN}} (or in a separate configured | |
27315 | directory configured with @samp{--srcdir=@var{dirname}/gdb-@value{GDBVN}}), you | |
27316 | will build all the required libraries, and then build GDB. | |
c906108c | 27317 | |
8e04817f AC |
27318 | When you have multiple hosts or targets configured in separate |
27319 | directories, you can run @code{make} on them in parallel (for example, | |
27320 | if they are NFS-mounted on each of the hosts); they will not interfere | |
27321 | with each other. | |
c906108c | 27322 | |
8e04817f | 27323 | @node Config Names |
79a6e687 | 27324 | @section Specifying Names for Hosts and Targets |
c906108c | 27325 | |
db2e3e2e | 27326 | The specifications used for hosts and targets in the @file{configure} |
8e04817f AC |
27327 | script are based on a three-part naming scheme, but some short predefined |
27328 | aliases are also supported. The full naming scheme encodes three pieces | |
27329 | of information in the following pattern: | |
c906108c | 27330 | |
474c8240 | 27331 | @smallexample |
8e04817f | 27332 | @var{architecture}-@var{vendor}-@var{os} |
474c8240 | 27333 | @end smallexample |
c906108c | 27334 | |
8e04817f AC |
27335 | For example, you can use the alias @code{sun4} as a @var{host} argument, |
27336 | or as the value for @var{target} in a @code{--target=@var{target}} | |
27337 | option. The equivalent full name is @samp{sparc-sun-sunos4}. | |
c906108c | 27338 | |
db2e3e2e | 27339 | The @file{configure} script accompanying @value{GDBN} does not provide |
8e04817f | 27340 | any query facility to list all supported host and target names or |
db2e3e2e | 27341 | aliases. @file{configure} calls the Bourne shell script |
8e04817f AC |
27342 | @code{config.sub} to map abbreviations to full names; you can read the |
27343 | script, if you wish, or you can use it to test your guesses on | |
27344 | abbreviations---for example: | |
c906108c | 27345 | |
8e04817f AC |
27346 | @smallexample |
27347 | % sh config.sub i386-linux | |
27348 | i386-pc-linux-gnu | |
27349 | % sh config.sub alpha-linux | |
27350 | alpha-unknown-linux-gnu | |
27351 | % sh config.sub hp9k700 | |
27352 | hppa1.1-hp-hpux | |
27353 | % sh config.sub sun4 | |
27354 | sparc-sun-sunos4.1.1 | |
27355 | % sh config.sub sun3 | |
27356 | m68k-sun-sunos4.1.1 | |
27357 | % sh config.sub i986v | |
27358 | Invalid configuration `i986v': machine `i986v' not recognized | |
27359 | @end smallexample | |
c906108c | 27360 | |
8e04817f AC |
27361 | @noindent |
27362 | @code{config.sub} is also distributed in the @value{GDBN} source | |
27363 | directory (@file{gdb-@value{GDBVN}}, for version @value{GDBVN}). | |
d700128c | 27364 | |
8e04817f | 27365 | @node Configure Options |
db2e3e2e | 27366 | @section @file{configure} Options |
c906108c | 27367 | |
db2e3e2e BW |
27368 | Here is a summary of the @file{configure} options and arguments that |
27369 | are most often useful for building @value{GDBN}. @file{configure} also has | |
8e04817f | 27370 | several other options not listed here. @inforef{What Configure |
db2e3e2e | 27371 | Does,,configure.info}, for a full explanation of @file{configure}. |
c906108c | 27372 | |
474c8240 | 27373 | @smallexample |
8e04817f AC |
27374 | configure @r{[}--help@r{]} |
27375 | @r{[}--prefix=@var{dir}@r{]} | |
27376 | @r{[}--exec-prefix=@var{dir}@r{]} | |
27377 | @r{[}--srcdir=@var{dirname}@r{]} | |
27378 | @r{[}--norecursion@r{]} @r{[}--rm@r{]} | |
27379 | @r{[}--target=@var{target}@r{]} | |
27380 | @var{host} | |
474c8240 | 27381 | @end smallexample |
c906108c | 27382 | |
8e04817f AC |
27383 | @noindent |
27384 | You may introduce options with a single @samp{-} rather than | |
27385 | @samp{--} if you prefer; but you may abbreviate option names if you use | |
27386 | @samp{--}. | |
c906108c | 27387 | |
8e04817f AC |
27388 | @table @code |
27389 | @item --help | |
db2e3e2e | 27390 | Display a quick summary of how to invoke @file{configure}. |
c906108c | 27391 | |
8e04817f AC |
27392 | @item --prefix=@var{dir} |
27393 | Configure the source to install programs and files under directory | |
27394 | @file{@var{dir}}. | |
c906108c | 27395 | |
8e04817f AC |
27396 | @item --exec-prefix=@var{dir} |
27397 | Configure the source to install programs under directory | |
27398 | @file{@var{dir}}. | |
c906108c | 27399 | |
8e04817f AC |
27400 | @c avoid splitting the warning from the explanation: |
27401 | @need 2000 | |
27402 | @item --srcdir=@var{dirname} | |
27403 | @strong{Warning: using this option requires @sc{gnu} @code{make}, or another | |
27404 | @code{make} that implements the @code{VPATH} feature.}@* | |
27405 | Use this option to make configurations in directories separate from the | |
27406 | @value{GDBN} source directories. Among other things, you can use this to | |
27407 | build (or maintain) several configurations simultaneously, in separate | |
db2e3e2e | 27408 | directories. @file{configure} writes configuration-specific files in |
8e04817f | 27409 | the current directory, but arranges for them to use the source in the |
db2e3e2e | 27410 | directory @var{dirname}. @file{configure} creates directories under |
8e04817f AC |
27411 | the working directory in parallel to the source directories below |
27412 | @var{dirname}. | |
c906108c | 27413 | |
8e04817f | 27414 | @item --norecursion |
db2e3e2e | 27415 | Configure only the directory level where @file{configure} is executed; do not |
8e04817f | 27416 | propagate configuration to subdirectories. |
c906108c | 27417 | |
8e04817f AC |
27418 | @item --target=@var{target} |
27419 | Configure @value{GDBN} for cross-debugging programs running on the specified | |
27420 | @var{target}. Without this option, @value{GDBN} is configured to debug | |
27421 | programs that run on the same machine (@var{host}) as @value{GDBN} itself. | |
c906108c | 27422 | |
8e04817f | 27423 | There is no convenient way to generate a list of all available targets. |
c906108c | 27424 | |
8e04817f AC |
27425 | @item @var{host} @dots{} |
27426 | Configure @value{GDBN} to run on the specified @var{host}. | |
c906108c | 27427 | |
8e04817f AC |
27428 | There is no convenient way to generate a list of all available hosts. |
27429 | @end table | |
c906108c | 27430 | |
8e04817f AC |
27431 | There are many other options available as well, but they are generally |
27432 | needed for special purposes only. | |
c906108c | 27433 | |
098b41a6 JG |
27434 | @node System-wide configuration |
27435 | @section System-wide configuration and settings | |
27436 | @cindex system-wide init file | |
27437 | ||
27438 | @value{GDBN} can be configured to have a system-wide init file; | |
27439 | this file will be read and executed at startup (@pxref{Startup, , What | |
27440 | @value{GDBN} does during startup}). | |
27441 | ||
27442 | Here is the corresponding configure option: | |
27443 | ||
27444 | @table @code | |
27445 | @item --with-system-gdbinit=@var{file} | |
27446 | Specify that the default location of the system-wide init file is | |
27447 | @var{file}. | |
27448 | @end table | |
27449 | ||
27450 | If @value{GDBN} has been configured with the option @option{--prefix=$prefix}, | |
27451 | it may be subject to relocation. Two possible cases: | |
27452 | ||
27453 | @itemize @bullet | |
27454 | @item | |
27455 | If the default location of this init file contains @file{$prefix}, | |
27456 | it will be subject to relocation. Suppose that the configure options | |
27457 | are @option{--prefix=$prefix --with-system-gdbinit=$prefix/etc/gdbinit}; | |
27458 | if @value{GDBN} is moved from @file{$prefix} to @file{$install}, the system | |
27459 | init file is looked for as @file{$install/etc/gdbinit} instead of | |
27460 | @file{$prefix/etc/gdbinit}. | |
27461 | ||
27462 | @item | |
27463 | By contrast, if the default location does not contain the prefix, | |
27464 | it will not be relocated. E.g.@: if @value{GDBN} has been configured with | |
27465 | @option{--prefix=/usr/local --with-system-gdbinit=/usr/share/gdb/gdbinit}, | |
27466 | then @value{GDBN} will always look for @file{/usr/share/gdb/gdbinit}, | |
27467 | wherever @value{GDBN} is installed. | |
27468 | @end itemize | |
27469 | ||
8e04817f AC |
27470 | @node Maintenance Commands |
27471 | @appendix Maintenance Commands | |
27472 | @cindex maintenance commands | |
27473 | @cindex internal commands | |
c906108c | 27474 | |
8e04817f | 27475 | In addition to commands intended for @value{GDBN} users, @value{GDBN} |
09d4efe1 EZ |
27476 | includes a number of commands intended for @value{GDBN} developers, |
27477 | that are not documented elsewhere in this manual. These commands are | |
da316a69 EZ |
27478 | provided here for reference. (For commands that turn on debugging |
27479 | messages, see @ref{Debugging Output}.) | |
c906108c | 27480 | |
8e04817f | 27481 | @table @code |
09d4efe1 | 27482 | @kindex maint agent |
782b2b07 | 27483 | @kindex maint agent-eval |
09d4efe1 | 27484 | @item maint agent @var{expression} |
782b2b07 | 27485 | @itemx maint agent-eval @var{expression} |
09d4efe1 EZ |
27486 | Translate the given @var{expression} into remote agent bytecodes. |
27487 | This command is useful for debugging the Agent Expression mechanism | |
782b2b07 SS |
27488 | (@pxref{Agent Expressions}). The @samp{agent} version produces an |
27489 | expression useful for data collection, such as by tracepoints, while | |
27490 | @samp{maint agent-eval} produces an expression that evaluates directly | |
27491 | to a result. For instance, a collection expression for @code{globa + | |
27492 | globb} will include bytecodes to record four bytes of memory at each | |
27493 | of the addresses of @code{globa} and @code{globb}, while discarding | |
27494 | the result of the addition, while an evaluation expression will do the | |
27495 | addition and return the sum. | |
09d4efe1 | 27496 | |
8e04817f AC |
27497 | @kindex maint info breakpoints |
27498 | @item @anchor{maint info breakpoints}maint info breakpoints | |
27499 | Using the same format as @samp{info breakpoints}, display both the | |
27500 | breakpoints you've set explicitly, and those @value{GDBN} is using for | |
27501 | internal purposes. Internal breakpoints are shown with negative | |
27502 | breakpoint numbers. The type column identifies what kind of breakpoint | |
27503 | is shown: | |
c906108c | 27504 | |
8e04817f AC |
27505 | @table @code |
27506 | @item breakpoint | |
27507 | Normal, explicitly set breakpoint. | |
c906108c | 27508 | |
8e04817f AC |
27509 | @item watchpoint |
27510 | Normal, explicitly set watchpoint. | |
c906108c | 27511 | |
8e04817f AC |
27512 | @item longjmp |
27513 | Internal breakpoint, used to handle correctly stepping through | |
27514 | @code{longjmp} calls. | |
c906108c | 27515 | |
8e04817f AC |
27516 | @item longjmp resume |
27517 | Internal breakpoint at the target of a @code{longjmp}. | |
c906108c | 27518 | |
8e04817f AC |
27519 | @item until |
27520 | Temporary internal breakpoint used by the @value{GDBN} @code{until} command. | |
c906108c | 27521 | |
8e04817f AC |
27522 | @item finish |
27523 | Temporary internal breakpoint used by the @value{GDBN} @code{finish} command. | |
c906108c | 27524 | |
8e04817f AC |
27525 | @item shlib events |
27526 | Shared library events. | |
c906108c | 27527 | |
8e04817f | 27528 | @end table |
c906108c | 27529 | |
fff08868 HZ |
27530 | @kindex set displaced-stepping |
27531 | @kindex show displaced-stepping | |
237fc4c9 PA |
27532 | @cindex displaced stepping support |
27533 | @cindex out-of-line single-stepping | |
fff08868 HZ |
27534 | @item set displaced-stepping |
27535 | @itemx show displaced-stepping | |
237fc4c9 | 27536 | Control whether or not @value{GDBN} will do @dfn{displaced stepping} |
fff08868 HZ |
27537 | if the target supports it. Displaced stepping is a way to single-step |
27538 | over breakpoints without removing them from the inferior, by executing | |
27539 | an out-of-line copy of the instruction that was originally at the | |
27540 | breakpoint location. It is also known as out-of-line single-stepping. | |
27541 | ||
27542 | @table @code | |
27543 | @item set displaced-stepping on | |
27544 | If the target architecture supports it, @value{GDBN} will use | |
27545 | displaced stepping to step over breakpoints. | |
27546 | ||
27547 | @item set displaced-stepping off | |
27548 | @value{GDBN} will not use displaced stepping to step over breakpoints, | |
27549 | even if such is supported by the target architecture. | |
27550 | ||
27551 | @cindex non-stop mode, and @samp{set displaced-stepping} | |
27552 | @item set displaced-stepping auto | |
27553 | This is the default mode. @value{GDBN} will use displaced stepping | |
27554 | only if non-stop mode is active (@pxref{Non-Stop Mode}) and the target | |
27555 | architecture supports displaced stepping. | |
27556 | @end table | |
237fc4c9 | 27557 | |
09d4efe1 EZ |
27558 | @kindex maint check-symtabs |
27559 | @item maint check-symtabs | |
27560 | Check the consistency of psymtabs and symtabs. | |
27561 | ||
27562 | @kindex maint cplus first_component | |
27563 | @item maint cplus first_component @var{name} | |
27564 | Print the first C@t{++} class/namespace component of @var{name}. | |
27565 | ||
27566 | @kindex maint cplus namespace | |
27567 | @item maint cplus namespace | |
27568 | Print the list of possible C@t{++} namespaces. | |
27569 | ||
27570 | @kindex maint demangle | |
27571 | @item maint demangle @var{name} | |
d3e8051b | 27572 | Demangle a C@t{++} or Objective-C mangled @var{name}. |
09d4efe1 EZ |
27573 | |
27574 | @kindex maint deprecate | |
27575 | @kindex maint undeprecate | |
27576 | @cindex deprecated commands | |
27577 | @item maint deprecate @var{command} @r{[}@var{replacement}@r{]} | |
27578 | @itemx maint undeprecate @var{command} | |
27579 | Deprecate or undeprecate the named @var{command}. Deprecated commands | |
27580 | cause @value{GDBN} to issue a warning when you use them. The optional | |
27581 | argument @var{replacement} says which newer command should be used in | |
27582 | favor of the deprecated one; if it is given, @value{GDBN} will mention | |
27583 | the replacement as part of the warning. | |
27584 | ||
27585 | @kindex maint dump-me | |
27586 | @item maint dump-me | |
721c2651 | 27587 | @cindex @code{SIGQUIT} signal, dump core of @value{GDBN} |
09d4efe1 | 27588 | Cause a fatal signal in the debugger and force it to dump its core. |
721c2651 EZ |
27589 | This is supported only on systems which support aborting a program |
27590 | with the @code{SIGQUIT} signal. | |
09d4efe1 | 27591 | |
8d30a00d AC |
27592 | @kindex maint internal-error |
27593 | @kindex maint internal-warning | |
09d4efe1 EZ |
27594 | @item maint internal-error @r{[}@var{message-text}@r{]} |
27595 | @itemx maint internal-warning @r{[}@var{message-text}@r{]} | |
8d30a00d AC |
27596 | Cause @value{GDBN} to call the internal function @code{internal_error} |
27597 | or @code{internal_warning} and hence behave as though an internal error | |
27598 | or internal warning has been detected. In addition to reporting the | |
27599 | internal problem, these functions give the user the opportunity to | |
27600 | either quit @value{GDBN} or create a core file of the current | |
27601 | @value{GDBN} session. | |
27602 | ||
09d4efe1 EZ |
27603 | These commands take an optional parameter @var{message-text} that is |
27604 | used as the text of the error or warning message. | |
27605 | ||
d3e8051b | 27606 | Here's an example of using @code{internal-error}: |
09d4efe1 | 27607 | |
8d30a00d | 27608 | @smallexample |
f7dc1244 | 27609 | (@value{GDBP}) @kbd{maint internal-error testing, 1, 2} |
8d30a00d AC |
27610 | @dots{}/maint.c:121: internal-error: testing, 1, 2 |
27611 | A problem internal to GDB has been detected. Further | |
27612 | debugging may prove unreliable. | |
27613 | Quit this debugging session? (y or n) @kbd{n} | |
27614 | Create a core file? (y or n) @kbd{n} | |
f7dc1244 | 27615 | (@value{GDBP}) |
8d30a00d AC |
27616 | @end smallexample |
27617 | ||
3c16cced PA |
27618 | @cindex @value{GDBN} internal error |
27619 | @cindex internal errors, control of @value{GDBN} behavior | |
27620 | ||
27621 | @kindex maint set internal-error | |
27622 | @kindex maint show internal-error | |
27623 | @kindex maint set internal-warning | |
27624 | @kindex maint show internal-warning | |
27625 | @item maint set internal-error @var{action} [ask|yes|no] | |
27626 | @itemx maint show internal-error @var{action} | |
27627 | @itemx maint set internal-warning @var{action} [ask|yes|no] | |
27628 | @itemx maint show internal-warning @var{action} | |
27629 | When @value{GDBN} reports an internal problem (error or warning) it | |
27630 | gives the user the opportunity to both quit @value{GDBN} and create a | |
27631 | core file of the current @value{GDBN} session. These commands let you | |
27632 | override the default behaviour for each particular @var{action}, | |
27633 | described in the table below. | |
27634 | ||
27635 | @table @samp | |
27636 | @item quit | |
27637 | You can specify that @value{GDBN} should always (yes) or never (no) | |
27638 | quit. The default is to ask the user what to do. | |
27639 | ||
27640 | @item corefile | |
27641 | You can specify that @value{GDBN} should always (yes) or never (no) | |
27642 | create a core file. The default is to ask the user what to do. | |
27643 | @end table | |
27644 | ||
09d4efe1 EZ |
27645 | @kindex maint packet |
27646 | @item maint packet @var{text} | |
27647 | If @value{GDBN} is talking to an inferior via the serial protocol, | |
27648 | then this command sends the string @var{text} to the inferior, and | |
27649 | displays the response packet. @value{GDBN} supplies the initial | |
27650 | @samp{$} character, the terminating @samp{#} character, and the | |
27651 | checksum. | |
27652 | ||
27653 | @kindex maint print architecture | |
27654 | @item maint print architecture @r{[}@var{file}@r{]} | |
27655 | Print the entire architecture configuration. The optional argument | |
27656 | @var{file} names the file where the output goes. | |
8d30a00d | 27657 | |
81adfced DJ |
27658 | @kindex maint print c-tdesc |
27659 | @item maint print c-tdesc | |
27660 | Print the current target description (@pxref{Target Descriptions}) as | |
27661 | a C source file. The created source file can be used in @value{GDBN} | |
27662 | when an XML parser is not available to parse the description. | |
27663 | ||
00905d52 AC |
27664 | @kindex maint print dummy-frames |
27665 | @item maint print dummy-frames | |
00905d52 AC |
27666 | Prints the contents of @value{GDBN}'s internal dummy-frame stack. |
27667 | ||
27668 | @smallexample | |
f7dc1244 | 27669 | (@value{GDBP}) @kbd{b add} |
00905d52 | 27670 | @dots{} |
f7dc1244 | 27671 | (@value{GDBP}) @kbd{print add(2,3)} |
00905d52 AC |
27672 | Breakpoint 2, add (a=2, b=3) at @dots{} |
27673 | 58 return (a + b); | |
27674 | The program being debugged stopped while in a function called from GDB. | |
27675 | @dots{} | |
f7dc1244 | 27676 | (@value{GDBP}) @kbd{maint print dummy-frames} |
00905d52 AC |
27677 | 0x1a57c80: pc=0x01014068 fp=0x0200bddc sp=0x0200bdd6 |
27678 | top=0x0200bdd4 id=@{stack=0x200bddc,code=0x101405c@} | |
27679 | call_lo=0x01014000 call_hi=0x01014001 | |
f7dc1244 | 27680 | (@value{GDBP}) |
00905d52 AC |
27681 | @end smallexample |
27682 | ||
27683 | Takes an optional file parameter. | |
27684 | ||
0680b120 AC |
27685 | @kindex maint print registers |
27686 | @kindex maint print raw-registers | |
27687 | @kindex maint print cooked-registers | |
617073a9 | 27688 | @kindex maint print register-groups |
09d4efe1 EZ |
27689 | @item maint print registers @r{[}@var{file}@r{]} |
27690 | @itemx maint print raw-registers @r{[}@var{file}@r{]} | |
27691 | @itemx maint print cooked-registers @r{[}@var{file}@r{]} | |
27692 | @itemx maint print register-groups @r{[}@var{file}@r{]} | |
0680b120 AC |
27693 | Print @value{GDBN}'s internal register data structures. |
27694 | ||
617073a9 AC |
27695 | The command @code{maint print raw-registers} includes the contents of |
27696 | the raw register cache; the command @code{maint print cooked-registers} | |
27697 | includes the (cooked) value of all registers; and the command | |
27698 | @code{maint print register-groups} includes the groups that each | |
27699 | register is a member of. @xref{Registers,, Registers, gdbint, | |
27700 | @value{GDBN} Internals}. | |
0680b120 | 27701 | |
09d4efe1 EZ |
27702 | These commands take an optional parameter, a file name to which to |
27703 | write the information. | |
0680b120 | 27704 | |
617073a9 | 27705 | @kindex maint print reggroups |
09d4efe1 EZ |
27706 | @item maint print reggroups @r{[}@var{file}@r{]} |
27707 | Print @value{GDBN}'s internal register group data structures. The | |
27708 | optional argument @var{file} tells to what file to write the | |
27709 | information. | |
617073a9 | 27710 | |
09d4efe1 | 27711 | The register groups info looks like this: |
617073a9 AC |
27712 | |
27713 | @smallexample | |
f7dc1244 | 27714 | (@value{GDBP}) @kbd{maint print reggroups} |
b383017d RM |
27715 | Group Type |
27716 | general user | |
27717 | float user | |
27718 | all user | |
27719 | vector user | |
27720 | system user | |
27721 | save internal | |
27722 | restore internal | |
617073a9 AC |
27723 | @end smallexample |
27724 | ||
09d4efe1 EZ |
27725 | @kindex flushregs |
27726 | @item flushregs | |
27727 | This command forces @value{GDBN} to flush its internal register cache. | |
27728 | ||
27729 | @kindex maint print objfiles | |
27730 | @cindex info for known object files | |
27731 | @item maint print objfiles | |
27732 | Print a dump of all known object files. For each object file, this | |
27733 | command prints its name, address in memory, and all of its psymtabs | |
27734 | and symtabs. | |
27735 | ||
27736 | @kindex maint print statistics | |
27737 | @cindex bcache statistics | |
27738 | @item maint print statistics | |
27739 | This command prints, for each object file in the program, various data | |
27740 | about that object file followed by the byte cache (@dfn{bcache}) | |
27741 | statistics for the object file. The objfile data includes the number | |
d3e8051b | 27742 | of minimal, partial, full, and stabs symbols, the number of types |
09d4efe1 EZ |
27743 | defined by the objfile, the number of as yet unexpanded psym tables, |
27744 | the number of line tables and string tables, and the amount of memory | |
27745 | used by the various tables. The bcache statistics include the counts, | |
27746 | sizes, and counts of duplicates of all and unique objects, max, | |
27747 | average, and median entry size, total memory used and its overhead and | |
27748 | savings, and various measures of the hash table size and chain | |
27749 | lengths. | |
27750 | ||
c7ba131e JB |
27751 | @kindex maint print target-stack |
27752 | @cindex target stack description | |
27753 | @item maint print target-stack | |
27754 | A @dfn{target} is an interface between the debugger and a particular | |
27755 | kind of file or process. Targets can be stacked in @dfn{strata}, | |
27756 | so that more than one target can potentially respond to a request. | |
27757 | In particular, memory accesses will walk down the stack of targets | |
27758 | until they find a target that is interested in handling that particular | |
27759 | address. | |
27760 | ||
27761 | This command prints a short description of each layer that was pushed on | |
27762 | the @dfn{target stack}, starting from the top layer down to the bottom one. | |
27763 | ||
09d4efe1 EZ |
27764 | @kindex maint print type |
27765 | @cindex type chain of a data type | |
27766 | @item maint print type @var{expr} | |
27767 | Print the type chain for a type specified by @var{expr}. The argument | |
27768 | can be either a type name or a symbol. If it is a symbol, the type of | |
27769 | that symbol is described. The type chain produced by this command is | |
27770 | a recursive definition of the data type as stored in @value{GDBN}'s | |
27771 | data structures, including its flags and contained types. | |
27772 | ||
27773 | @kindex maint set dwarf2 max-cache-age | |
27774 | @kindex maint show dwarf2 max-cache-age | |
27775 | @item maint set dwarf2 max-cache-age | |
27776 | @itemx maint show dwarf2 max-cache-age | |
27777 | Control the DWARF 2 compilation unit cache. | |
27778 | ||
27779 | @cindex DWARF 2 compilation units cache | |
27780 | In object files with inter-compilation-unit references, such as those | |
27781 | produced by the GCC option @samp{-feliminate-dwarf2-dups}, the DWARF 2 | |
27782 | reader needs to frequently refer to previously read compilation units. | |
27783 | This setting controls how long a compilation unit will remain in the | |
27784 | cache if it is not referenced. A higher limit means that cached | |
27785 | compilation units will be stored in memory longer, and more total | |
27786 | memory will be used. Setting it to zero disables caching, which will | |
27787 | slow down @value{GDBN} startup, but reduce memory consumption. | |
27788 | ||
e7ba9c65 DJ |
27789 | @kindex maint set profile |
27790 | @kindex maint show profile | |
27791 | @cindex profiling GDB | |
27792 | @item maint set profile | |
27793 | @itemx maint show profile | |
27794 | Control profiling of @value{GDBN}. | |
27795 | ||
27796 | Profiling will be disabled until you use the @samp{maint set profile} | |
27797 | command to enable it. When you enable profiling, the system will begin | |
27798 | collecting timing and execution count data; when you disable profiling or | |
27799 | exit @value{GDBN}, the results will be written to a log file. Remember that | |
27800 | if you use profiling, @value{GDBN} will overwrite the profiling log file | |
27801 | (often called @file{gmon.out}). If you have a record of important profiling | |
27802 | data in a @file{gmon.out} file, be sure to move it to a safe location. | |
27803 | ||
27804 | Configuring with @samp{--enable-profiling} arranges for @value{GDBN} to be | |
b383017d | 27805 | compiled with the @samp{-pg} compiler option. |
e7ba9c65 | 27806 | |
cbe54154 PA |
27807 | @kindex maint set show-debug-regs |
27808 | @kindex maint show show-debug-regs | |
eac35c4e | 27809 | @cindex hardware debug registers |
cbe54154 PA |
27810 | @item maint set show-debug-regs |
27811 | @itemx maint show show-debug-regs | |
eac35c4e | 27812 | Control whether to show variables that mirror the hardware debug |
09d4efe1 | 27813 | registers. Use @code{ON} to enable, @code{OFF} to disable. If |
3f94c067 | 27814 | enabled, the debug registers values are shown when @value{GDBN} inserts or |
09d4efe1 EZ |
27815 | removes a hardware breakpoint or watchpoint, and when the inferior |
27816 | triggers a hardware-assisted breakpoint or watchpoint. | |
27817 | ||
27818 | @kindex maint space | |
27819 | @cindex memory used by commands | |
27820 | @item maint space | |
27821 | Control whether to display memory usage for each command. If set to a | |
27822 | nonzero value, @value{GDBN} will display how much memory each command | |
27823 | took, following the command's own output. This can also be requested | |
27824 | by invoking @value{GDBN} with the @option{--statistics} command-line | |
27825 | switch (@pxref{Mode Options}). | |
27826 | ||
27827 | @kindex maint time | |
27828 | @cindex time of command execution | |
27829 | @item maint time | |
27830 | Control whether to display the execution time for each command. If | |
27831 | set to a nonzero value, @value{GDBN} will display how much time it | |
27832 | took to execute each command, following the command's own output. | |
e2b7ddea VP |
27833 | The time is not printed for the commands that run the target, since |
27834 | there's no mechanism currently to compute how much time was spend | |
27835 | by @value{GDBN} and how much time was spend by the program been debugged. | |
27836 | it's not possibly currently | |
09d4efe1 EZ |
27837 | This can also be requested by invoking @value{GDBN} with the |
27838 | @option{--statistics} command-line switch (@pxref{Mode Options}). | |
27839 | ||
27840 | @kindex maint translate-address | |
27841 | @item maint translate-address @r{[}@var{section}@r{]} @var{addr} | |
27842 | Find the symbol stored at the location specified by the address | |
27843 | @var{addr} and an optional section name @var{section}. If found, | |
27844 | @value{GDBN} prints the name of the closest symbol and an offset from | |
27845 | the symbol's location to the specified address. This is similar to | |
27846 | the @code{info address} command (@pxref{Symbols}), except that this | |
27847 | command also allows to find symbols in other sections. | |
ae038cb0 | 27848 | |
c14c28ba PP |
27849 | If section was not specified, the section in which the symbol was found |
27850 | is also printed. For dynamically linked executables, the name of | |
27851 | executable or shared library containing the symbol is printed as well. | |
27852 | ||
8e04817f | 27853 | @end table |
c906108c | 27854 | |
9c16f35a EZ |
27855 | The following command is useful for non-interactive invocations of |
27856 | @value{GDBN}, such as in the test suite. | |
27857 | ||
27858 | @table @code | |
27859 | @item set watchdog @var{nsec} | |
27860 | @kindex set watchdog | |
27861 | @cindex watchdog timer | |
27862 | @cindex timeout for commands | |
27863 | Set the maximum number of seconds @value{GDBN} will wait for the | |
27864 | target operation to finish. If this time expires, @value{GDBN} | |
27865 | reports and error and the command is aborted. | |
27866 | ||
27867 | @item show watchdog | |
27868 | Show the current setting of the target wait timeout. | |
27869 | @end table | |
c906108c | 27870 | |
e0ce93ac | 27871 | @node Remote Protocol |
8e04817f | 27872 | @appendix @value{GDBN} Remote Serial Protocol |
c906108c | 27873 | |
ee2d5c50 AC |
27874 | @menu |
27875 | * Overview:: | |
27876 | * Packets:: | |
27877 | * Stop Reply Packets:: | |
27878 | * General Query Packets:: | |
27879 | * Register Packet Format:: | |
9d29849a | 27880 | * Tracepoint Packets:: |
a6b151f1 | 27881 | * Host I/O Packets:: |
9a6253be | 27882 | * Interrupts:: |
8b23ecc4 SL |
27883 | * Notification Packets:: |
27884 | * Remote Non-Stop:: | |
a6f3e723 | 27885 | * Packet Acknowledgment:: |
ee2d5c50 | 27886 | * Examples:: |
79a6e687 | 27887 | * File-I/O Remote Protocol Extension:: |
cfa9d6d9 | 27888 | * Library List Format:: |
79a6e687 | 27889 | * Memory Map Format:: |
ee2d5c50 AC |
27890 | @end menu |
27891 | ||
27892 | @node Overview | |
27893 | @section Overview | |
27894 | ||
8e04817f AC |
27895 | There may be occasions when you need to know something about the |
27896 | protocol---for example, if there is only one serial port to your target | |
27897 | machine, you might want your program to do something special if it | |
27898 | recognizes a packet meant for @value{GDBN}. | |
c906108c | 27899 | |
d2c6833e | 27900 | In the examples below, @samp{->} and @samp{<-} are used to indicate |
bf06d120 | 27901 | transmitted and received data, respectively. |
c906108c | 27902 | |
8e04817f AC |
27903 | @cindex protocol, @value{GDBN} remote serial |
27904 | @cindex serial protocol, @value{GDBN} remote | |
27905 | @cindex remote serial protocol | |
8b23ecc4 SL |
27906 | All @value{GDBN} commands and responses (other than acknowledgments |
27907 | and notifications, see @ref{Notification Packets}) are sent as a | |
27908 | @var{packet}. A @var{packet} is introduced with the character | |
8e04817f AC |
27909 | @samp{$}, the actual @var{packet-data}, and the terminating character |
27910 | @samp{#} followed by a two-digit @var{checksum}: | |
c906108c | 27911 | |
474c8240 | 27912 | @smallexample |
8e04817f | 27913 | @code{$}@var{packet-data}@code{#}@var{checksum} |
474c8240 | 27914 | @end smallexample |
8e04817f | 27915 | @noindent |
c906108c | 27916 | |
8e04817f AC |
27917 | @cindex checksum, for @value{GDBN} remote |
27918 | @noindent | |
27919 | The two-digit @var{checksum} is computed as the modulo 256 sum of all | |
27920 | characters between the leading @samp{$} and the trailing @samp{#} (an | |
27921 | eight bit unsigned checksum). | |
c906108c | 27922 | |
8e04817f AC |
27923 | Implementors should note that prior to @value{GDBN} 5.0 the protocol |
27924 | specification also included an optional two-digit @var{sequence-id}: | |
c906108c | 27925 | |
474c8240 | 27926 | @smallexample |
8e04817f | 27927 | @code{$}@var{sequence-id}@code{:}@var{packet-data}@code{#}@var{checksum} |
474c8240 | 27928 | @end smallexample |
c906108c | 27929 | |
8e04817f AC |
27930 | @cindex sequence-id, for @value{GDBN} remote |
27931 | @noindent | |
27932 | That @var{sequence-id} was appended to the acknowledgment. @value{GDBN} | |
27933 | has never output @var{sequence-id}s. Stubs that handle packets added | |
27934 | since @value{GDBN} 5.0 must not accept @var{sequence-id}. | |
c906108c | 27935 | |
8e04817f AC |
27936 | When either the host or the target machine receives a packet, the first |
27937 | response expected is an acknowledgment: either @samp{+} (to indicate | |
27938 | the package was received correctly) or @samp{-} (to request | |
27939 | retransmission): | |
c906108c | 27940 | |
474c8240 | 27941 | @smallexample |
d2c6833e AC |
27942 | -> @code{$}@var{packet-data}@code{#}@var{checksum} |
27943 | <- @code{+} | |
474c8240 | 27944 | @end smallexample |
8e04817f | 27945 | @noindent |
53a5351d | 27946 | |
a6f3e723 SL |
27947 | The @samp{+}/@samp{-} acknowledgments can be disabled |
27948 | once a connection is established. | |
27949 | @xref{Packet Acknowledgment}, for details. | |
27950 | ||
8e04817f AC |
27951 | The host (@value{GDBN}) sends @var{command}s, and the target (the |
27952 | debugging stub incorporated in your program) sends a @var{response}. In | |
27953 | the case of step and continue @var{command}s, the response is only sent | |
8b23ecc4 SL |
27954 | when the operation has completed, and the target has again stopped all |
27955 | threads in all attached processes. This is the default all-stop mode | |
27956 | behavior, but the remote protocol also supports @value{GDBN}'s non-stop | |
27957 | execution mode; see @ref{Remote Non-Stop}, for details. | |
c906108c | 27958 | |
8e04817f AC |
27959 | @var{packet-data} consists of a sequence of characters with the |
27960 | exception of @samp{#} and @samp{$} (see @samp{X} packet for additional | |
27961 | exceptions). | |
c906108c | 27962 | |
ee2d5c50 | 27963 | @cindex remote protocol, field separator |
0876f84a | 27964 | Fields within the packet should be separated using @samp{,} @samp{;} or |
8e04817f | 27965 | @samp{:}. Except where otherwise noted all numbers are represented in |
ee2d5c50 | 27966 | @sc{hex} with leading zeros suppressed. |
c906108c | 27967 | |
8e04817f AC |
27968 | Implementors should note that prior to @value{GDBN} 5.0, the character |
27969 | @samp{:} could not appear as the third character in a packet (as it | |
27970 | would potentially conflict with the @var{sequence-id}). | |
c906108c | 27971 | |
0876f84a DJ |
27972 | @cindex remote protocol, binary data |
27973 | @anchor{Binary Data} | |
27974 | Binary data in most packets is encoded either as two hexadecimal | |
27975 | digits per byte of binary data. This allowed the traditional remote | |
27976 | protocol to work over connections which were only seven-bit clean. | |
27977 | Some packets designed more recently assume an eight-bit clean | |
27978 | connection, and use a more efficient encoding to send and receive | |
27979 | binary data. | |
27980 | ||
27981 | The binary data representation uses @code{7d} (@sc{ascii} @samp{@}}) | |
27982 | as an escape character. Any escaped byte is transmitted as the escape | |
27983 | character followed by the original character XORed with @code{0x20}. | |
27984 | For example, the byte @code{0x7d} would be transmitted as the two | |
27985 | bytes @code{0x7d 0x5d}. The bytes @code{0x23} (@sc{ascii} @samp{#}), | |
27986 | @code{0x24} (@sc{ascii} @samp{$}), and @code{0x7d} (@sc{ascii} | |
27987 | @samp{@}}) must always be escaped. Responses sent by the stub | |
27988 | must also escape @code{0x2a} (@sc{ascii} @samp{*}), so that it | |
27989 | is not interpreted as the start of a run-length encoded sequence | |
27990 | (described next). | |
27991 | ||
1d3811f6 DJ |
27992 | Response @var{data} can be run-length encoded to save space. |
27993 | Run-length encoding replaces runs of identical characters with one | |
27994 | instance of the repeated character, followed by a @samp{*} and a | |
27995 | repeat count. The repeat count is itself sent encoded, to avoid | |
27996 | binary characters in @var{data}: a value of @var{n} is sent as | |
27997 | @code{@var{n}+29}. For a repeat count greater or equal to 3, this | |
27998 | produces a printable @sc{ascii} character, e.g.@: a space (@sc{ascii} | |
27999 | code 32) for a repeat count of 3. (This is because run-length | |
28000 | encoding starts to win for counts 3 or more.) Thus, for example, | |
28001 | @samp{0* } is a run-length encoding of ``0000'': the space character | |
28002 | after @samp{*} means repeat the leading @code{0} @w{@code{32 - 29 = | |
28003 | 3}} more times. | |
28004 | ||
28005 | The printable characters @samp{#} and @samp{$} or with a numeric value | |
28006 | greater than 126 must not be used. Runs of six repeats (@samp{#}) or | |
28007 | seven repeats (@samp{$}) can be expanded using a repeat count of only | |
28008 | five (@samp{"}). For example, @samp{00000000} can be encoded as | |
28009 | @samp{0*"00}. | |
c906108c | 28010 | |
8e04817f AC |
28011 | The error response returned for some packets includes a two character |
28012 | error number. That number is not well defined. | |
c906108c | 28013 | |
f8da2bff | 28014 | @cindex empty response, for unsupported packets |
8e04817f AC |
28015 | For any @var{command} not supported by the stub, an empty response |
28016 | (@samp{$#00}) should be returned. That way it is possible to extend the | |
28017 | protocol. A newer @value{GDBN} can tell if a packet is supported based | |
28018 | on that response. | |
c906108c | 28019 | |
b383017d RM |
28020 | A stub is required to support the @samp{g}, @samp{G}, @samp{m}, @samp{M}, |
28021 | @samp{c}, and @samp{s} @var{command}s. All other @var{command}s are | |
8e04817f | 28022 | optional. |
c906108c | 28023 | |
ee2d5c50 AC |
28024 | @node Packets |
28025 | @section Packets | |
28026 | ||
28027 | The following table provides a complete list of all currently defined | |
28028 | @var{command}s and their corresponding response @var{data}. | |
79a6e687 | 28029 | @xref{File-I/O Remote Protocol Extension}, for details about the File |
9c16f35a | 28030 | I/O extension of the remote protocol. |
ee2d5c50 | 28031 | |
b8ff78ce JB |
28032 | Each packet's description has a template showing the packet's overall |
28033 | syntax, followed by an explanation of the packet's meaning. We | |
28034 | include spaces in some of the templates for clarity; these are not | |
28035 | part of the packet's syntax. No @value{GDBN} packet uses spaces to | |
28036 | separate its components. For example, a template like @samp{foo | |
28037 | @var{bar} @var{baz}} describes a packet beginning with the three ASCII | |
28038 | bytes @samp{foo}, followed by a @var{bar}, followed directly by a | |
3f94c067 | 28039 | @var{baz}. @value{GDBN} does not transmit a space character between the |
b8ff78ce JB |
28040 | @samp{foo} and the @var{bar}, or between the @var{bar} and the |
28041 | @var{baz}. | |
28042 | ||
b90a069a SL |
28043 | @cindex @var{thread-id}, in remote protocol |
28044 | @anchor{thread-id syntax} | |
28045 | Several packets and replies include a @var{thread-id} field to identify | |
28046 | a thread. Normally these are positive numbers with a target-specific | |
28047 | interpretation, formatted as big-endian hex strings. A @var{thread-id} | |
28048 | can also be a literal @samp{-1} to indicate all threads, or @samp{0} to | |
28049 | pick any thread. | |
28050 | ||
28051 | In addition, the remote protocol supports a multiprocess feature in | |
28052 | which the @var{thread-id} syntax is extended to optionally include both | |
28053 | process and thread ID fields, as @samp{p@var{pid}.@var{tid}}. | |
28054 | The @var{pid} (process) and @var{tid} (thread) components each have the | |
28055 | format described above: a positive number with target-specific | |
28056 | interpretation formatted as a big-endian hex string, literal @samp{-1} | |
28057 | to indicate all processes or threads (respectively), or @samp{0} to | |
28058 | indicate an arbitrary process or thread. Specifying just a process, as | |
28059 | @samp{p@var{pid}}, is equivalent to @samp{p@var{pid}.-1}. It is an | |
28060 | error to specify all processes but a specific thread, such as | |
28061 | @samp{p-1.@var{tid}}. Note that the @samp{p} prefix is @emph{not} used | |
28062 | for those packets and replies explicitly documented to include a process | |
28063 | ID, rather than a @var{thread-id}. | |
28064 | ||
28065 | The multiprocess @var{thread-id} syntax extensions are only used if both | |
28066 | @value{GDBN} and the stub report support for the @samp{multiprocess} | |
28067 | feature using @samp{qSupported}. @xref{multiprocess extensions}, for | |
28068 | more information. | |
28069 | ||
8ffe2530 JB |
28070 | Note that all packet forms beginning with an upper- or lower-case |
28071 | letter, other than those described here, are reserved for future use. | |
28072 | ||
b8ff78ce | 28073 | Here are the packet descriptions. |
ee2d5c50 | 28074 | |
b8ff78ce | 28075 | @table @samp |
ee2d5c50 | 28076 | |
b8ff78ce JB |
28077 | @item ! |
28078 | @cindex @samp{!} packet | |
2d717e4f | 28079 | @anchor{extended mode} |
8e04817f AC |
28080 | Enable extended mode. In extended mode, the remote server is made |
28081 | persistent. The @samp{R} packet is used to restart the program being | |
28082 | debugged. | |
ee2d5c50 AC |
28083 | |
28084 | Reply: | |
28085 | @table @samp | |
28086 | @item OK | |
8e04817f | 28087 | The remote target both supports and has enabled extended mode. |
ee2d5c50 | 28088 | @end table |
c906108c | 28089 | |
b8ff78ce JB |
28090 | @item ? |
28091 | @cindex @samp{?} packet | |
ee2d5c50 | 28092 | Indicate the reason the target halted. The reply is the same as for |
8b23ecc4 SL |
28093 | step and continue. This packet has a special interpretation when the |
28094 | target is in non-stop mode; see @ref{Remote Non-Stop}. | |
c906108c | 28095 | |
ee2d5c50 AC |
28096 | Reply: |
28097 | @xref{Stop Reply Packets}, for the reply specifications. | |
28098 | ||
b8ff78ce JB |
28099 | @item A @var{arglen},@var{argnum},@var{arg},@dots{} |
28100 | @cindex @samp{A} packet | |
28101 | Initialized @code{argv[]} array passed into program. @var{arglen} | |
28102 | specifies the number of bytes in the hex encoded byte stream | |
28103 | @var{arg}. See @code{gdbserver} for more details. | |
ee2d5c50 AC |
28104 | |
28105 | Reply: | |
28106 | @table @samp | |
28107 | @item OK | |
b8ff78ce JB |
28108 | The arguments were set. |
28109 | @item E @var{NN} | |
28110 | An error occurred. | |
ee2d5c50 AC |
28111 | @end table |
28112 | ||
b8ff78ce JB |
28113 | @item b @var{baud} |
28114 | @cindex @samp{b} packet | |
28115 | (Don't use this packet; its behavior is not well-defined.) | |
ee2d5c50 AC |
28116 | Change the serial line speed to @var{baud}. |
28117 | ||
28118 | JTC: @emph{When does the transport layer state change? When it's | |
28119 | received, or after the ACK is transmitted. In either case, there are | |
28120 | problems if the command or the acknowledgment packet is dropped.} | |
28121 | ||
28122 | Stan: @emph{If people really wanted to add something like this, and get | |
28123 | it working for the first time, they ought to modify ser-unix.c to send | |
28124 | some kind of out-of-band message to a specially-setup stub and have the | |
28125 | switch happen "in between" packets, so that from remote protocol's point | |
28126 | of view, nothing actually happened.} | |
28127 | ||
b8ff78ce JB |
28128 | @item B @var{addr},@var{mode} |
28129 | @cindex @samp{B} packet | |
8e04817f | 28130 | Set (@var{mode} is @samp{S}) or clear (@var{mode} is @samp{C}) a |
2f870471 AC |
28131 | breakpoint at @var{addr}. |
28132 | ||
b8ff78ce | 28133 | Don't use this packet. Use the @samp{Z} and @samp{z} packets instead |
2f870471 | 28134 | (@pxref{insert breakpoint or watchpoint packet}). |
c906108c | 28135 | |
bacec72f | 28136 | @cindex @samp{bc} packet |
0d772ac9 MS |
28137 | @anchor{bc} |
28138 | @item bc | |
bacec72f MS |
28139 | Backward continue. Execute the target system in reverse. No parameter. |
28140 | @xref{Reverse Execution}, for more information. | |
28141 | ||
28142 | Reply: | |
28143 | @xref{Stop Reply Packets}, for the reply specifications. | |
28144 | ||
bacec72f | 28145 | @cindex @samp{bs} packet |
0d772ac9 MS |
28146 | @anchor{bs} |
28147 | @item bs | |
bacec72f MS |
28148 | Backward single step. Execute one instruction in reverse. No parameter. |
28149 | @xref{Reverse Execution}, for more information. | |
28150 | ||
28151 | Reply: | |
28152 | @xref{Stop Reply Packets}, for the reply specifications. | |
28153 | ||
4f553f88 | 28154 | @item c @r{[}@var{addr}@r{]} |
b8ff78ce JB |
28155 | @cindex @samp{c} packet |
28156 | Continue. @var{addr} is address to resume. If @var{addr} is omitted, | |
28157 | resume at current address. | |
c906108c | 28158 | |
ee2d5c50 AC |
28159 | Reply: |
28160 | @xref{Stop Reply Packets}, for the reply specifications. | |
28161 | ||
4f553f88 | 28162 | @item C @var{sig}@r{[};@var{addr}@r{]} |
b8ff78ce | 28163 | @cindex @samp{C} packet |
8e04817f | 28164 | Continue with signal @var{sig} (hex signal number). If |
b8ff78ce | 28165 | @samp{;@var{addr}} is omitted, resume at same address. |
c906108c | 28166 | |
ee2d5c50 AC |
28167 | Reply: |
28168 | @xref{Stop Reply Packets}, for the reply specifications. | |
c906108c | 28169 | |
b8ff78ce JB |
28170 | @item d |
28171 | @cindex @samp{d} packet | |
ee2d5c50 AC |
28172 | Toggle debug flag. |
28173 | ||
b8ff78ce JB |
28174 | Don't use this packet; instead, define a general set packet |
28175 | (@pxref{General Query Packets}). | |
ee2d5c50 | 28176 | |
b8ff78ce | 28177 | @item D |
b90a069a | 28178 | @itemx D;@var{pid} |
b8ff78ce | 28179 | @cindex @samp{D} packet |
b90a069a SL |
28180 | The first form of the packet is used to detach @value{GDBN} from the |
28181 | remote system. It is sent to the remote target | |
07f31aa6 | 28182 | before @value{GDBN} disconnects via the @code{detach} command. |
ee2d5c50 | 28183 | |
b90a069a SL |
28184 | The second form, including a process ID, is used when multiprocess |
28185 | protocol extensions are enabled (@pxref{multiprocess extensions}), to | |
28186 | detach only a specific process. The @var{pid} is specified as a | |
28187 | big-endian hex string. | |
28188 | ||
ee2d5c50 AC |
28189 | Reply: |
28190 | @table @samp | |
10fac096 NW |
28191 | @item OK |
28192 | for success | |
b8ff78ce | 28193 | @item E @var{NN} |
10fac096 | 28194 | for an error |
ee2d5c50 | 28195 | @end table |
c906108c | 28196 | |
b8ff78ce JB |
28197 | @item F @var{RC},@var{EE},@var{CF};@var{XX} |
28198 | @cindex @samp{F} packet | |
28199 | A reply from @value{GDBN} to an @samp{F} packet sent by the target. | |
28200 | This is part of the File-I/O protocol extension. @xref{File-I/O | |
79a6e687 | 28201 | Remote Protocol Extension}, for the specification. |
ee2d5c50 | 28202 | |
b8ff78ce | 28203 | @item g |
ee2d5c50 | 28204 | @anchor{read registers packet} |
b8ff78ce | 28205 | @cindex @samp{g} packet |
ee2d5c50 AC |
28206 | Read general registers. |
28207 | ||
28208 | Reply: | |
28209 | @table @samp | |
28210 | @item @var{XX@dots{}} | |
8e04817f AC |
28211 | Each byte of register data is described by two hex digits. The bytes |
28212 | with the register are transmitted in target byte order. The size of | |
b8ff78ce | 28213 | each register and their position within the @samp{g} packet are |
4a9bb1df UW |
28214 | determined by the @value{GDBN} internal gdbarch functions |
28215 | @code{DEPRECATED_REGISTER_RAW_SIZE} and @code{gdbarch_register_name}. The | |
b8ff78ce JB |
28216 | specification of several standard @samp{g} packets is specified below. |
28217 | @item E @var{NN} | |
ee2d5c50 AC |
28218 | for an error. |
28219 | @end table | |
c906108c | 28220 | |
b8ff78ce JB |
28221 | @item G @var{XX@dots{}} |
28222 | @cindex @samp{G} packet | |
28223 | Write general registers. @xref{read registers packet}, for a | |
28224 | description of the @var{XX@dots{}} data. | |
ee2d5c50 AC |
28225 | |
28226 | Reply: | |
28227 | @table @samp | |
28228 | @item OK | |
28229 | for success | |
b8ff78ce | 28230 | @item E @var{NN} |
ee2d5c50 AC |
28231 | for an error |
28232 | @end table | |
28233 | ||
b90a069a | 28234 | @item H @var{c} @var{thread-id} |
b8ff78ce | 28235 | @cindex @samp{H} packet |
8e04817f | 28236 | Set thread for subsequent operations (@samp{m}, @samp{M}, @samp{g}, |
ee2d5c50 AC |
28237 | @samp{G}, et.al.). @var{c} depends on the operation to be performed: it |
28238 | should be @samp{c} for step and continue operations, @samp{g} for other | |
b90a069a SL |
28239 | operations. The thread designator @var{thread-id} has the format and |
28240 | interpretation described in @ref{thread-id syntax}. | |
ee2d5c50 AC |
28241 | |
28242 | Reply: | |
28243 | @table @samp | |
28244 | @item OK | |
28245 | for success | |
b8ff78ce | 28246 | @item E @var{NN} |
ee2d5c50 AC |
28247 | for an error |
28248 | @end table | |
c906108c | 28249 | |
8e04817f AC |
28250 | @c FIXME: JTC: |
28251 | @c 'H': How restrictive (or permissive) is the thread model. If a | |
28252 | @c thread is selected and stopped, are other threads allowed | |
28253 | @c to continue to execute? As I mentioned above, I think the | |
28254 | @c semantics of each command when a thread is selected must be | |
28255 | @c described. For example: | |
28256 | @c | |
28257 | @c 'g': If the stub supports threads and a specific thread is | |
28258 | @c selected, returns the register block from that thread; | |
28259 | @c otherwise returns current registers. | |
28260 | @c | |
28261 | @c 'G' If the stub supports threads and a specific thread is | |
28262 | @c selected, sets the registers of the register block of | |
28263 | @c that thread; otherwise sets current registers. | |
c906108c | 28264 | |
b8ff78ce | 28265 | @item i @r{[}@var{addr}@r{[},@var{nnn}@r{]]} |
ee2d5c50 | 28266 | @anchor{cycle step packet} |
b8ff78ce JB |
28267 | @cindex @samp{i} packet |
28268 | Step the remote target by a single clock cycle. If @samp{,@var{nnn}} is | |
8e04817f AC |
28269 | present, cycle step @var{nnn} cycles. If @var{addr} is present, cycle |
28270 | step starting at that address. | |
c906108c | 28271 | |
b8ff78ce JB |
28272 | @item I |
28273 | @cindex @samp{I} packet | |
28274 | Signal, then cycle step. @xref{step with signal packet}. @xref{cycle | |
28275 | step packet}. | |
ee2d5c50 | 28276 | |
b8ff78ce JB |
28277 | @item k |
28278 | @cindex @samp{k} packet | |
28279 | Kill request. | |
c906108c | 28280 | |
ac282366 | 28281 | FIXME: @emph{There is no description of how to operate when a specific |
ee2d5c50 AC |
28282 | thread context has been selected (i.e.@: does 'k' kill only that |
28283 | thread?)}. | |
c906108c | 28284 | |
b8ff78ce JB |
28285 | @item m @var{addr},@var{length} |
28286 | @cindex @samp{m} packet | |
8e04817f | 28287 | Read @var{length} bytes of memory starting at address @var{addr}. |
fb031cdf JB |
28288 | Note that @var{addr} may not be aligned to any particular boundary. |
28289 | ||
28290 | The stub need not use any particular size or alignment when gathering | |
28291 | data from memory for the response; even if @var{addr} is word-aligned | |
28292 | and @var{length} is a multiple of the word size, the stub is free to | |
28293 | use byte accesses, or not. For this reason, this packet may not be | |
28294 | suitable for accessing memory-mapped I/O devices. | |
c43c5473 JB |
28295 | @cindex alignment of remote memory accesses |
28296 | @cindex size of remote memory accesses | |
28297 | @cindex memory, alignment and size of remote accesses | |
c906108c | 28298 | |
ee2d5c50 AC |
28299 | Reply: |
28300 | @table @samp | |
28301 | @item @var{XX@dots{}} | |
599b237a | 28302 | Memory contents; each byte is transmitted as a two-digit hexadecimal |
b8ff78ce JB |
28303 | number. The reply may contain fewer bytes than requested if the |
28304 | server was able to read only part of the region of memory. | |
28305 | @item E @var{NN} | |
ee2d5c50 AC |
28306 | @var{NN} is errno |
28307 | @end table | |
28308 | ||
b8ff78ce JB |
28309 | @item M @var{addr},@var{length}:@var{XX@dots{}} |
28310 | @cindex @samp{M} packet | |
8e04817f | 28311 | Write @var{length} bytes of memory starting at address @var{addr}. |
b8ff78ce | 28312 | @var{XX@dots{}} is the data; each byte is transmitted as a two-digit |
599b237a | 28313 | hexadecimal number. |
ee2d5c50 AC |
28314 | |
28315 | Reply: | |
28316 | @table @samp | |
28317 | @item OK | |
28318 | for success | |
b8ff78ce | 28319 | @item E @var{NN} |
8e04817f AC |
28320 | for an error (this includes the case where only part of the data was |
28321 | written). | |
ee2d5c50 | 28322 | @end table |
c906108c | 28323 | |
b8ff78ce JB |
28324 | @item p @var{n} |
28325 | @cindex @samp{p} packet | |
28326 | Read the value of register @var{n}; @var{n} is in hex. | |
2e868123 AC |
28327 | @xref{read registers packet}, for a description of how the returned |
28328 | register value is encoded. | |
ee2d5c50 AC |
28329 | |
28330 | Reply: | |
28331 | @table @samp | |
2e868123 AC |
28332 | @item @var{XX@dots{}} |
28333 | the register's value | |
b8ff78ce | 28334 | @item E @var{NN} |
2e868123 AC |
28335 | for an error |
28336 | @item | |
28337 | Indicating an unrecognized @var{query}. | |
ee2d5c50 AC |
28338 | @end table |
28339 | ||
b8ff78ce | 28340 | @item P @var{n@dots{}}=@var{r@dots{}} |
ee2d5c50 | 28341 | @anchor{write register packet} |
b8ff78ce JB |
28342 | @cindex @samp{P} packet |
28343 | Write register @var{n@dots{}} with value @var{r@dots{}}. The register | |
599b237a | 28344 | number @var{n} is in hexadecimal, and @var{r@dots{}} contains two hex |
8e04817f | 28345 | digits for each byte in the register (target byte order). |
c906108c | 28346 | |
ee2d5c50 AC |
28347 | Reply: |
28348 | @table @samp | |
28349 | @item OK | |
28350 | for success | |
b8ff78ce | 28351 | @item E @var{NN} |
ee2d5c50 AC |
28352 | for an error |
28353 | @end table | |
28354 | ||
5f3bebba JB |
28355 | @item q @var{name} @var{params}@dots{} |
28356 | @itemx Q @var{name} @var{params}@dots{} | |
b8ff78ce | 28357 | @cindex @samp{q} packet |
b8ff78ce | 28358 | @cindex @samp{Q} packet |
5f3bebba JB |
28359 | General query (@samp{q}) and set (@samp{Q}). These packets are |
28360 | described fully in @ref{General Query Packets}. | |
c906108c | 28361 | |
b8ff78ce JB |
28362 | @item r |
28363 | @cindex @samp{r} packet | |
8e04817f | 28364 | Reset the entire system. |
c906108c | 28365 | |
b8ff78ce | 28366 | Don't use this packet; use the @samp{R} packet instead. |
ee2d5c50 | 28367 | |
b8ff78ce JB |
28368 | @item R @var{XX} |
28369 | @cindex @samp{R} packet | |
8e04817f | 28370 | Restart the program being debugged. @var{XX}, while needed, is ignored. |
2d717e4f | 28371 | This packet is only available in extended mode (@pxref{extended mode}). |
ee2d5c50 | 28372 | |
8e04817f | 28373 | The @samp{R} packet has no reply. |
ee2d5c50 | 28374 | |
4f553f88 | 28375 | @item s @r{[}@var{addr}@r{]} |
b8ff78ce JB |
28376 | @cindex @samp{s} packet |
28377 | Single step. @var{addr} is the address at which to resume. If | |
28378 | @var{addr} is omitted, resume at same address. | |
c906108c | 28379 | |
ee2d5c50 AC |
28380 | Reply: |
28381 | @xref{Stop Reply Packets}, for the reply specifications. | |
28382 | ||
4f553f88 | 28383 | @item S @var{sig}@r{[};@var{addr}@r{]} |
ee2d5c50 | 28384 | @anchor{step with signal packet} |
b8ff78ce JB |
28385 | @cindex @samp{S} packet |
28386 | Step with signal. This is analogous to the @samp{C} packet, but | |
28387 | requests a single-step, rather than a normal resumption of execution. | |
c906108c | 28388 | |
ee2d5c50 AC |
28389 | Reply: |
28390 | @xref{Stop Reply Packets}, for the reply specifications. | |
28391 | ||
b8ff78ce JB |
28392 | @item t @var{addr}:@var{PP},@var{MM} |
28393 | @cindex @samp{t} packet | |
8e04817f | 28394 | Search backwards starting at address @var{addr} for a match with pattern |
ee2d5c50 AC |
28395 | @var{PP} and mask @var{MM}. @var{PP} and @var{MM} are 4 bytes. |
28396 | @var{addr} must be at least 3 digits. | |
c906108c | 28397 | |
b90a069a | 28398 | @item T @var{thread-id} |
b8ff78ce | 28399 | @cindex @samp{T} packet |
b90a069a | 28400 | Find out if the thread @var{thread-id} is alive. @xref{thread-id syntax}. |
c906108c | 28401 | |
ee2d5c50 AC |
28402 | Reply: |
28403 | @table @samp | |
28404 | @item OK | |
28405 | thread is still alive | |
b8ff78ce | 28406 | @item E @var{NN} |
ee2d5c50 AC |
28407 | thread is dead |
28408 | @end table | |
28409 | ||
b8ff78ce JB |
28410 | @item v |
28411 | Packets starting with @samp{v} are identified by a multi-letter name, | |
28412 | up to the first @samp{;} or @samp{?} (or the end of the packet). | |
86d30acc | 28413 | |
2d717e4f DJ |
28414 | @item vAttach;@var{pid} |
28415 | @cindex @samp{vAttach} packet | |
8b23ecc4 SL |
28416 | Attach to a new process with the specified process ID @var{pid}. |
28417 | The process ID is a | |
28418 | hexadecimal integer identifying the process. In all-stop mode, all | |
28419 | threads in the attached process are stopped; in non-stop mode, it may be | |
28420 | attached without being stopped if that is supported by the target. | |
28421 | ||
28422 | @c In non-stop mode, on a successful vAttach, the stub should set the | |
28423 | @c current thread to a thread of the newly-attached process. After | |
28424 | @c attaching, GDB queries for the attached process's thread ID with qC. | |
28425 | @c Also note that, from a user perspective, whether or not the | |
28426 | @c target is stopped on attach in non-stop mode depends on whether you | |
28427 | @c use the foreground or background version of the attach command, not | |
28428 | @c on what vAttach does; GDB does the right thing with respect to either | |
28429 | @c stopping or restarting threads. | |
2d717e4f DJ |
28430 | |
28431 | This packet is only available in extended mode (@pxref{extended mode}). | |
28432 | ||
28433 | Reply: | |
28434 | @table @samp | |
28435 | @item E @var{nn} | |
28436 | for an error | |
28437 | @item @r{Any stop packet} | |
8b23ecc4 SL |
28438 | for success in all-stop mode (@pxref{Stop Reply Packets}) |
28439 | @item OK | |
28440 | for success in non-stop mode (@pxref{Remote Non-Stop}) | |
2d717e4f DJ |
28441 | @end table |
28442 | ||
b90a069a | 28443 | @item vCont@r{[};@var{action}@r{[}:@var{thread-id}@r{]]}@dots{} |
b8ff78ce JB |
28444 | @cindex @samp{vCont} packet |
28445 | Resume the inferior, specifying different actions for each thread. | |
b90a069a | 28446 | If an action is specified with no @var{thread-id}, then it is applied to any |
86d30acc | 28447 | threads that don't have a specific action specified; if no default action is |
8b23ecc4 SL |
28448 | specified then other threads should remain stopped in all-stop mode and |
28449 | in their current state in non-stop mode. | |
28450 | Specifying multiple | |
86d30acc | 28451 | default actions is an error; specifying no actions is also an error. |
b90a069a SL |
28452 | Thread IDs are specified using the syntax described in @ref{thread-id syntax}. |
28453 | ||
28454 | Currently supported actions are: | |
86d30acc | 28455 | |
b8ff78ce | 28456 | @table @samp |
86d30acc DJ |
28457 | @item c |
28458 | Continue. | |
b8ff78ce | 28459 | @item C @var{sig} |
8b23ecc4 | 28460 | Continue with signal @var{sig}. The signal @var{sig} should be two hex digits. |
86d30acc DJ |
28461 | @item s |
28462 | Step. | |
b8ff78ce | 28463 | @item S @var{sig} |
8b23ecc4 SL |
28464 | Step with signal @var{sig}. The signal @var{sig} should be two hex digits. |
28465 | @item t | |
28466 | Stop. | |
86d30acc DJ |
28467 | @end table |
28468 | ||
8b23ecc4 SL |
28469 | The optional argument @var{addr} normally associated with the |
28470 | @samp{c}, @samp{C}, @samp{s}, and @samp{S} packets is | |
b8ff78ce | 28471 | not supported in @samp{vCont}. |
86d30acc | 28472 | |
08a0efd0 PA |
28473 | The @samp{t} action is only relevant in non-stop mode |
28474 | (@pxref{Remote Non-Stop}) and may be ignored by the stub otherwise. | |
8b23ecc4 SL |
28475 | A stop reply should be generated for any affected thread not already stopped. |
28476 | When a thread is stopped by means of a @samp{t} action, | |
28477 | the corresponding stop reply should indicate that the thread has stopped with | |
28478 | signal @samp{0}, regardless of whether the target uses some other signal | |
28479 | as an implementation detail. | |
28480 | ||
86d30acc DJ |
28481 | Reply: |
28482 | @xref{Stop Reply Packets}, for the reply specifications. | |
28483 | ||
b8ff78ce JB |
28484 | @item vCont? |
28485 | @cindex @samp{vCont?} packet | |
d3e8051b | 28486 | Request a list of actions supported by the @samp{vCont} packet. |
86d30acc DJ |
28487 | |
28488 | Reply: | |
28489 | @table @samp | |
b8ff78ce JB |
28490 | @item vCont@r{[};@var{action}@dots{}@r{]} |
28491 | The @samp{vCont} packet is supported. Each @var{action} is a supported | |
28492 | command in the @samp{vCont} packet. | |
86d30acc | 28493 | @item |
b8ff78ce | 28494 | The @samp{vCont} packet is not supported. |
86d30acc | 28495 | @end table |
ee2d5c50 | 28496 | |
a6b151f1 DJ |
28497 | @item vFile:@var{operation}:@var{parameter}@dots{} |
28498 | @cindex @samp{vFile} packet | |
28499 | Perform a file operation on the target system. For details, | |
28500 | see @ref{Host I/O Packets}. | |
28501 | ||
68437a39 DJ |
28502 | @item vFlashErase:@var{addr},@var{length} |
28503 | @cindex @samp{vFlashErase} packet | |
28504 | Direct the stub to erase @var{length} bytes of flash starting at | |
28505 | @var{addr}. The region may enclose any number of flash blocks, but | |
28506 | its start and end must fall on block boundaries, as indicated by the | |
79a6e687 BW |
28507 | flash block size appearing in the memory map (@pxref{Memory Map |
28508 | Format}). @value{GDBN} groups flash memory programming operations | |
68437a39 DJ |
28509 | together, and sends a @samp{vFlashDone} request after each group; the |
28510 | stub is allowed to delay erase operation until the @samp{vFlashDone} | |
28511 | packet is received. | |
28512 | ||
b90a069a SL |
28513 | The stub must support @samp{vCont} if it reports support for |
28514 | multiprocess extensions (@pxref{multiprocess extensions}). Note that in | |
28515 | this case @samp{vCont} actions can be specified to apply to all threads | |
28516 | in a process by using the @samp{p@var{pid}.-1} form of the | |
28517 | @var{thread-id}. | |
28518 | ||
68437a39 DJ |
28519 | Reply: |
28520 | @table @samp | |
28521 | @item OK | |
28522 | for success | |
28523 | @item E @var{NN} | |
28524 | for an error | |
28525 | @end table | |
28526 | ||
28527 | @item vFlashWrite:@var{addr}:@var{XX@dots{}} | |
28528 | @cindex @samp{vFlashWrite} packet | |
28529 | Direct the stub to write data to flash address @var{addr}. The data | |
28530 | is passed in binary form using the same encoding as for the @samp{X} | |
28531 | packet (@pxref{Binary Data}). The memory ranges specified by | |
28532 | @samp{vFlashWrite} packets preceding a @samp{vFlashDone} packet must | |
28533 | not overlap, and must appear in order of increasing addresses | |
28534 | (although @samp{vFlashErase} packets for higher addresses may already | |
28535 | have been received; the ordering is guaranteed only between | |
28536 | @samp{vFlashWrite} packets). If a packet writes to an address that was | |
28537 | neither erased by a preceding @samp{vFlashErase} packet nor by some other | |
28538 | target-specific method, the results are unpredictable. | |
28539 | ||
28540 | ||
28541 | Reply: | |
28542 | @table @samp | |
28543 | @item OK | |
28544 | for success | |
28545 | @item E.memtype | |
28546 | for vFlashWrite addressing non-flash memory | |
28547 | @item E @var{NN} | |
28548 | for an error | |
28549 | @end table | |
28550 | ||
28551 | @item vFlashDone | |
28552 | @cindex @samp{vFlashDone} packet | |
28553 | Indicate to the stub that flash programming operation is finished. | |
28554 | The stub is permitted to delay or batch the effects of a group of | |
28555 | @samp{vFlashErase} and @samp{vFlashWrite} packets until a | |
28556 | @samp{vFlashDone} packet is received. The contents of the affected | |
28557 | regions of flash memory are unpredictable until the @samp{vFlashDone} | |
28558 | request is completed. | |
28559 | ||
b90a069a SL |
28560 | @item vKill;@var{pid} |
28561 | @cindex @samp{vKill} packet | |
28562 | Kill the process with the specified process ID. @var{pid} is a | |
28563 | hexadecimal integer identifying the process. This packet is used in | |
28564 | preference to @samp{k} when multiprocess protocol extensions are | |
28565 | supported; see @ref{multiprocess extensions}. | |
28566 | ||
28567 | Reply: | |
28568 | @table @samp | |
28569 | @item E @var{nn} | |
28570 | for an error | |
28571 | @item OK | |
28572 | for success | |
28573 | @end table | |
28574 | ||
2d717e4f DJ |
28575 | @item vRun;@var{filename}@r{[};@var{argument}@r{]}@dots{} |
28576 | @cindex @samp{vRun} packet | |
28577 | Run the program @var{filename}, passing it each @var{argument} on its | |
28578 | command line. The file and arguments are hex-encoded strings. If | |
28579 | @var{filename} is an empty string, the stub may use a default program | |
28580 | (e.g.@: the last program run). The program is created in the stopped | |
9b562ab8 | 28581 | state. |
2d717e4f | 28582 | |
8b23ecc4 SL |
28583 | @c FIXME: What about non-stop mode? |
28584 | ||
2d717e4f DJ |
28585 | This packet is only available in extended mode (@pxref{extended mode}). |
28586 | ||
28587 | Reply: | |
28588 | @table @samp | |
28589 | @item E @var{nn} | |
28590 | for an error | |
28591 | @item @r{Any stop packet} | |
28592 | for success (@pxref{Stop Reply Packets}) | |
28593 | @end table | |
28594 | ||
8b23ecc4 SL |
28595 | @item vStopped |
28596 | @anchor{vStopped packet} | |
28597 | @cindex @samp{vStopped} packet | |
28598 | ||
28599 | In non-stop mode (@pxref{Remote Non-Stop}), acknowledge a previous stop | |
28600 | reply and prompt for the stub to report another one. | |
28601 | ||
28602 | Reply: | |
28603 | @table @samp | |
28604 | @item @r{Any stop packet} | |
28605 | if there is another unreported stop event (@pxref{Stop Reply Packets}) | |
28606 | @item OK | |
28607 | if there are no unreported stop events | |
28608 | @end table | |
28609 | ||
b8ff78ce | 28610 | @item X @var{addr},@var{length}:@var{XX@dots{}} |
9a6253be | 28611 | @anchor{X packet} |
b8ff78ce JB |
28612 | @cindex @samp{X} packet |
28613 | Write data to memory, where the data is transmitted in binary. | |
28614 | @var{addr} is address, @var{length} is number of bytes, | |
0876f84a | 28615 | @samp{@var{XX}@dots{}} is binary data (@pxref{Binary Data}). |
c906108c | 28616 | |
ee2d5c50 AC |
28617 | Reply: |
28618 | @table @samp | |
28619 | @item OK | |
28620 | for success | |
b8ff78ce | 28621 | @item E @var{NN} |
ee2d5c50 AC |
28622 | for an error |
28623 | @end table | |
28624 | ||
b8ff78ce JB |
28625 | @item z @var{type},@var{addr},@var{length} |
28626 | @itemx Z @var{type},@var{addr},@var{length} | |
2f870471 | 28627 | @anchor{insert breakpoint or watchpoint packet} |
b8ff78ce JB |
28628 | @cindex @samp{z} packet |
28629 | @cindex @samp{Z} packets | |
28630 | Insert (@samp{Z}) or remove (@samp{z}) a @var{type} breakpoint or | |
2f870471 AC |
28631 | watchpoint starting at address @var{address} and covering the next |
28632 | @var{length} bytes. | |
ee2d5c50 | 28633 | |
2f870471 AC |
28634 | Each breakpoint and watchpoint packet @var{type} is documented |
28635 | separately. | |
28636 | ||
512217c7 AC |
28637 | @emph{Implementation notes: A remote target shall return an empty string |
28638 | for an unrecognized breakpoint or watchpoint packet @var{type}. A | |
28639 | remote target shall support either both or neither of a given | |
b8ff78ce | 28640 | @samp{Z@var{type}@dots{}} and @samp{z@var{type}@dots{}} packet pair. To |
2f870471 AC |
28641 | avoid potential problems with duplicate packets, the operations should |
28642 | be implemented in an idempotent way.} | |
28643 | ||
b8ff78ce JB |
28644 | @item z0,@var{addr},@var{length} |
28645 | @itemx Z0,@var{addr},@var{length} | |
28646 | @cindex @samp{z0} packet | |
28647 | @cindex @samp{Z0} packet | |
28648 | Insert (@samp{Z0}) or remove (@samp{z0}) a memory breakpoint at address | |
28649 | @var{addr} of size @var{length}. | |
2f870471 AC |
28650 | |
28651 | A memory breakpoint is implemented by replacing the instruction at | |
28652 | @var{addr} with a software breakpoint or trap instruction. The | |
b8ff78ce | 28653 | @var{length} is used by targets that indicates the size of the |
2f870471 AC |
28654 | breakpoint (in bytes) that should be inserted (e.g., the @sc{arm} and |
28655 | @sc{mips} can insert either a 2 or 4 byte breakpoint). | |
c906108c | 28656 | |
2f870471 AC |
28657 | @emph{Implementation note: It is possible for a target to copy or move |
28658 | code that contains memory breakpoints (e.g., when implementing | |
28659 | overlays). The behavior of this packet, in the presence of such a | |
28660 | target, is not defined.} | |
c906108c | 28661 | |
ee2d5c50 AC |
28662 | Reply: |
28663 | @table @samp | |
2f870471 AC |
28664 | @item OK |
28665 | success | |
28666 | @item | |
28667 | not supported | |
b8ff78ce | 28668 | @item E @var{NN} |
ee2d5c50 | 28669 | for an error |
2f870471 AC |
28670 | @end table |
28671 | ||
b8ff78ce JB |
28672 | @item z1,@var{addr},@var{length} |
28673 | @itemx Z1,@var{addr},@var{length} | |
28674 | @cindex @samp{z1} packet | |
28675 | @cindex @samp{Z1} packet | |
28676 | Insert (@samp{Z1}) or remove (@samp{z1}) a hardware breakpoint at | |
28677 | address @var{addr} of size @var{length}. | |
2f870471 AC |
28678 | |
28679 | A hardware breakpoint is implemented using a mechanism that is not | |
28680 | dependant on being able to modify the target's memory. | |
28681 | ||
28682 | @emph{Implementation note: A hardware breakpoint is not affected by code | |
28683 | movement.} | |
28684 | ||
28685 | Reply: | |
28686 | @table @samp | |
ee2d5c50 | 28687 | @item OK |
2f870471 AC |
28688 | success |
28689 | @item | |
28690 | not supported | |
b8ff78ce | 28691 | @item E @var{NN} |
2f870471 AC |
28692 | for an error |
28693 | @end table | |
28694 | ||
b8ff78ce JB |
28695 | @item z2,@var{addr},@var{length} |
28696 | @itemx Z2,@var{addr},@var{length} | |
28697 | @cindex @samp{z2} packet | |
28698 | @cindex @samp{Z2} packet | |
28699 | Insert (@samp{Z2}) or remove (@samp{z2}) a write watchpoint. | |
2f870471 AC |
28700 | |
28701 | Reply: | |
28702 | @table @samp | |
28703 | @item OK | |
28704 | success | |
28705 | @item | |
28706 | not supported | |
b8ff78ce | 28707 | @item E @var{NN} |
2f870471 AC |
28708 | for an error |
28709 | @end table | |
28710 | ||
b8ff78ce JB |
28711 | @item z3,@var{addr},@var{length} |
28712 | @itemx Z3,@var{addr},@var{length} | |
28713 | @cindex @samp{z3} packet | |
28714 | @cindex @samp{Z3} packet | |
28715 | Insert (@samp{Z3}) or remove (@samp{z3}) a read watchpoint. | |
2f870471 AC |
28716 | |
28717 | Reply: | |
28718 | @table @samp | |
28719 | @item OK | |
28720 | success | |
28721 | @item | |
28722 | not supported | |
b8ff78ce | 28723 | @item E @var{NN} |
2f870471 AC |
28724 | for an error |
28725 | @end table | |
28726 | ||
b8ff78ce JB |
28727 | @item z4,@var{addr},@var{length} |
28728 | @itemx Z4,@var{addr},@var{length} | |
28729 | @cindex @samp{z4} packet | |
28730 | @cindex @samp{Z4} packet | |
28731 | Insert (@samp{Z4}) or remove (@samp{z4}) an access watchpoint. | |
2f870471 AC |
28732 | |
28733 | Reply: | |
28734 | @table @samp | |
28735 | @item OK | |
28736 | success | |
28737 | @item | |
28738 | not supported | |
b8ff78ce | 28739 | @item E @var{NN} |
2f870471 | 28740 | for an error |
ee2d5c50 AC |
28741 | @end table |
28742 | ||
28743 | @end table | |
c906108c | 28744 | |
ee2d5c50 AC |
28745 | @node Stop Reply Packets |
28746 | @section Stop Reply Packets | |
28747 | @cindex stop reply packets | |
c906108c | 28748 | |
8b23ecc4 SL |
28749 | The @samp{C}, @samp{c}, @samp{S}, @samp{s}, @samp{vCont}, |
28750 | @samp{vAttach}, @samp{vRun}, @samp{vStopped}, and @samp{?} packets can | |
28751 | receive any of the below as a reply. Except for @samp{?} | |
28752 | and @samp{vStopped}, that reply is only returned | |
b8ff78ce | 28753 | when the target halts. In the below the exact meaning of @dfn{signal |
89be2091 DJ |
28754 | number} is defined by the header @file{include/gdb/signals.h} in the |
28755 | @value{GDBN} source code. | |
c906108c | 28756 | |
b8ff78ce JB |
28757 | As in the description of request packets, we include spaces in the |
28758 | reply templates for clarity; these are not part of the reply packet's | |
28759 | syntax. No @value{GDBN} stop reply packet uses spaces to separate its | |
28760 | components. | |
c906108c | 28761 | |
b8ff78ce | 28762 | @table @samp |
ee2d5c50 | 28763 | |
b8ff78ce | 28764 | @item S @var{AA} |
599b237a | 28765 | The program received signal number @var{AA} (a two-digit hexadecimal |
940178d3 JB |
28766 | number). This is equivalent to a @samp{T} response with no |
28767 | @var{n}:@var{r} pairs. | |
c906108c | 28768 | |
b8ff78ce JB |
28769 | @item T @var{AA} @var{n1}:@var{r1};@var{n2}:@var{r2};@dots{} |
28770 | @cindex @samp{T} packet reply | |
599b237a | 28771 | The program received signal number @var{AA} (a two-digit hexadecimal |
940178d3 JB |
28772 | number). This is equivalent to an @samp{S} response, except that the |
28773 | @samp{@var{n}:@var{r}} pairs can carry values of important registers | |
28774 | and other information directly in the stop reply packet, reducing | |
28775 | round-trip latency. Single-step and breakpoint traps are reported | |
28776 | this way. Each @samp{@var{n}:@var{r}} pair is interpreted as follows: | |
cfa9d6d9 DJ |
28777 | |
28778 | @itemize @bullet | |
b8ff78ce | 28779 | @item |
599b237a | 28780 | If @var{n} is a hexadecimal number, it is a register number, and the |
b8ff78ce JB |
28781 | corresponding @var{r} gives that register's value. @var{r} is a |
28782 | series of bytes in target byte order, with each byte given by a | |
28783 | two-digit hex number. | |
cfa9d6d9 | 28784 | |
b8ff78ce | 28785 | @item |
b90a069a SL |
28786 | If @var{n} is @samp{thread}, then @var{r} is the @var{thread-id} of |
28787 | the stopped thread, as specified in @ref{thread-id syntax}. | |
cfa9d6d9 | 28788 | |
b8ff78ce | 28789 | @item |
cfa9d6d9 DJ |
28790 | If @var{n} is a recognized @dfn{stop reason}, it describes a more |
28791 | specific event that stopped the target. The currently defined stop | |
28792 | reasons are listed below. @var{aa} should be @samp{05}, the trap | |
28793 | signal. At most one stop reason should be present. | |
28794 | ||
b8ff78ce JB |
28795 | @item |
28796 | Otherwise, @value{GDBN} should ignore this @samp{@var{n}:@var{r}} pair | |
28797 | and go on to the next; this allows us to extend the protocol in the | |
28798 | future. | |
cfa9d6d9 DJ |
28799 | @end itemize |
28800 | ||
28801 | The currently defined stop reasons are: | |
28802 | ||
28803 | @table @samp | |
28804 | @item watch | |
28805 | @itemx rwatch | |
28806 | @itemx awatch | |
28807 | The packet indicates a watchpoint hit, and @var{r} is the data address, in | |
28808 | hex. | |
28809 | ||
28810 | @cindex shared library events, remote reply | |
28811 | @item library | |
28812 | The packet indicates that the loaded libraries have changed. | |
28813 | @value{GDBN} should use @samp{qXfer:libraries:read} to fetch a new | |
28814 | list of loaded libraries. @var{r} is ignored. | |
bacec72f MS |
28815 | |
28816 | @cindex replay log events, remote reply | |
28817 | @item replaylog | |
28818 | The packet indicates that the target cannot continue replaying | |
28819 | logged execution events, because it has reached the end (or the | |
28820 | beginning when executing backward) of the log. The value of @var{r} | |
28821 | will be either @samp{begin} or @samp{end}. @xref{Reverse Execution}, | |
28822 | for more information. | |
28823 | ||
28824 | ||
cfa9d6d9 | 28825 | @end table |
ee2d5c50 | 28826 | |
b8ff78ce | 28827 | @item W @var{AA} |
b90a069a | 28828 | @itemx W @var{AA} ; process:@var{pid} |
8e04817f | 28829 | The process exited, and @var{AA} is the exit status. This is only |
ee2d5c50 AC |
28830 | applicable to certain targets. |
28831 | ||
b90a069a SL |
28832 | The second form of the response, including the process ID of the exited |
28833 | process, can be used only when @value{GDBN} has reported support for | |
28834 | multiprocess protocol extensions; see @ref{multiprocess extensions}. | |
28835 | The @var{pid} is formatted as a big-endian hex string. | |
28836 | ||
b8ff78ce | 28837 | @item X @var{AA} |
b90a069a | 28838 | @itemx X @var{AA} ; process:@var{pid} |
8e04817f | 28839 | The process terminated with signal @var{AA}. |
c906108c | 28840 | |
b90a069a SL |
28841 | The second form of the response, including the process ID of the |
28842 | terminated process, can be used only when @value{GDBN} has reported | |
28843 | support for multiprocess protocol extensions; see @ref{multiprocess | |
28844 | extensions}. The @var{pid} is formatted as a big-endian hex string. | |
28845 | ||
b8ff78ce JB |
28846 | @item O @var{XX}@dots{} |
28847 | @samp{@var{XX}@dots{}} is hex encoding of @sc{ascii} data, to be | |
28848 | written as the program's console output. This can happen at any time | |
28849 | while the program is running and the debugger should continue to wait | |
8b23ecc4 | 28850 | for @samp{W}, @samp{T}, etc. This reply is not permitted in non-stop mode. |
0ce1b118 | 28851 | |
b8ff78ce | 28852 | @item F @var{call-id},@var{parameter}@dots{} |
0ce1b118 CV |
28853 | @var{call-id} is the identifier which says which host system call should |
28854 | be called. This is just the name of the function. Translation into the | |
28855 | correct system call is only applicable as it's defined in @value{GDBN}. | |
79a6e687 | 28856 | @xref{File-I/O Remote Protocol Extension}, for a list of implemented |
0ce1b118 CV |
28857 | system calls. |
28858 | ||
b8ff78ce JB |
28859 | @samp{@var{parameter}@dots{}} is a list of parameters as defined for |
28860 | this very system call. | |
0ce1b118 | 28861 | |
b8ff78ce JB |
28862 | The target replies with this packet when it expects @value{GDBN} to |
28863 | call a host system call on behalf of the target. @value{GDBN} replies | |
28864 | with an appropriate @samp{F} packet and keeps up waiting for the next | |
28865 | reply packet from the target. The latest @samp{C}, @samp{c}, @samp{S} | |
79a6e687 BW |
28866 | or @samp{s} action is expected to be continued. @xref{File-I/O Remote |
28867 | Protocol Extension}, for more details. | |
0ce1b118 | 28868 | |
ee2d5c50 AC |
28869 | @end table |
28870 | ||
28871 | @node General Query Packets | |
28872 | @section General Query Packets | |
9c16f35a | 28873 | @cindex remote query requests |
c906108c | 28874 | |
5f3bebba JB |
28875 | Packets starting with @samp{q} are @dfn{general query packets}; |
28876 | packets starting with @samp{Q} are @dfn{general set packets}. General | |
28877 | query and set packets are a semi-unified form for retrieving and | |
28878 | sending information to and from the stub. | |
28879 | ||
28880 | The initial letter of a query or set packet is followed by a name | |
28881 | indicating what sort of thing the packet applies to. For example, | |
28882 | @value{GDBN} may use a @samp{qSymbol} packet to exchange symbol | |
28883 | definitions with the stub. These packet names follow some | |
28884 | conventions: | |
28885 | ||
28886 | @itemize @bullet | |
28887 | @item | |
28888 | The name must not contain commas, colons or semicolons. | |
28889 | @item | |
28890 | Most @value{GDBN} query and set packets have a leading upper case | |
28891 | letter. | |
28892 | @item | |
28893 | The names of custom vendor packets should use a company prefix, in | |
28894 | lower case, followed by a period. For example, packets designed at | |
28895 | the Acme Corporation might begin with @samp{qacme.foo} (for querying | |
28896 | foos) or @samp{Qacme.bar} (for setting bars). | |
28897 | @end itemize | |
28898 | ||
aa56d27a JB |
28899 | The name of a query or set packet should be separated from any |
28900 | parameters by a @samp{:}; the parameters themselves should be | |
28901 | separated by @samp{,} or @samp{;}. Stubs must be careful to match the | |
369af7bd DJ |
28902 | full packet name, and check for a separator or the end of the packet, |
28903 | in case two packet names share a common prefix. New packets should not begin | |
28904 | with @samp{qC}, @samp{qP}, or @samp{qL}@footnote{The @samp{qP} and @samp{qL} | |
28905 | packets predate these conventions, and have arguments without any terminator | |
28906 | for the packet name; we suspect they are in widespread use in places that | |
28907 | are difficult to upgrade. The @samp{qC} packet has no arguments, but some | |
28908 | existing stubs (e.g.@: RedBoot) are known to not check for the end of the | |
28909 | packet.}. | |
c906108c | 28910 | |
b8ff78ce JB |
28911 | Like the descriptions of the other packets, each description here |
28912 | has a template showing the packet's overall syntax, followed by an | |
28913 | explanation of the packet's meaning. We include spaces in some of the | |
28914 | templates for clarity; these are not part of the packet's syntax. No | |
28915 | @value{GDBN} packet uses spaces to separate its components. | |
28916 | ||
5f3bebba JB |
28917 | Here are the currently defined query and set packets: |
28918 | ||
b8ff78ce | 28919 | @table @samp |
c906108c | 28920 | |
b8ff78ce | 28921 | @item qC |
9c16f35a | 28922 | @cindex current thread, remote request |
b8ff78ce | 28923 | @cindex @samp{qC} packet |
b90a069a | 28924 | Return the current thread ID. |
ee2d5c50 AC |
28925 | |
28926 | Reply: | |
28927 | @table @samp | |
b90a069a SL |
28928 | @item QC @var{thread-id} |
28929 | Where @var{thread-id} is a thread ID as documented in | |
28930 | @ref{thread-id syntax}. | |
b8ff78ce | 28931 | @item @r{(anything else)} |
b90a069a | 28932 | Any other reply implies the old thread ID. |
ee2d5c50 AC |
28933 | @end table |
28934 | ||
b8ff78ce | 28935 | @item qCRC:@var{addr},@var{length} |
ff2587ec | 28936 | @cindex CRC of memory block, remote request |
b8ff78ce | 28937 | @cindex @samp{qCRC} packet |
99e008fe EZ |
28938 | Compute the CRC checksum of a block of memory using CRC-32 defined in |
28939 | IEEE 802.3. The CRC is computed byte at a time, taking the most | |
28940 | significant bit of each byte first. The initial pattern code | |
28941 | @code{0xffffffff} is used to ensure leading zeros affect the CRC. | |
28942 | ||
28943 | @emph{Note:} This is the same CRC used in validating separate debug | |
28944 | files (@pxref{Separate Debug Files, , Debugging Information in Separate | |
28945 | Files}). However the algorithm is slightly different. When validating | |
28946 | separate debug files, the CRC is computed taking the @emph{least} | |
28947 | significant bit of each byte first, and the final result is inverted to | |
28948 | detect trailing zeros. | |
28949 | ||
ff2587ec WZ |
28950 | Reply: |
28951 | @table @samp | |
b8ff78ce | 28952 | @item E @var{NN} |
ff2587ec | 28953 | An error (such as memory fault) |
b8ff78ce JB |
28954 | @item C @var{crc32} |
28955 | The specified memory region's checksum is @var{crc32}. | |
ff2587ec WZ |
28956 | @end table |
28957 | ||
b8ff78ce JB |
28958 | @item qfThreadInfo |
28959 | @itemx qsThreadInfo | |
9c16f35a | 28960 | @cindex list active threads, remote request |
b8ff78ce JB |
28961 | @cindex @samp{qfThreadInfo} packet |
28962 | @cindex @samp{qsThreadInfo} packet | |
b90a069a | 28963 | Obtain a list of all active thread IDs from the target (OS). Since there |
8e04817f AC |
28964 | may be too many active threads to fit into one reply packet, this query |
28965 | works iteratively: it may require more than one query/reply sequence to | |
28966 | obtain the entire list of threads. The first query of the sequence will | |
b8ff78ce JB |
28967 | be the @samp{qfThreadInfo} query; subsequent queries in the |
28968 | sequence will be the @samp{qsThreadInfo} query. | |
ee2d5c50 | 28969 | |
b8ff78ce | 28970 | NOTE: This packet replaces the @samp{qL} query (see below). |
ee2d5c50 AC |
28971 | |
28972 | Reply: | |
28973 | @table @samp | |
b90a069a SL |
28974 | @item m @var{thread-id} |
28975 | A single thread ID | |
28976 | @item m @var{thread-id},@var{thread-id}@dots{} | |
28977 | a comma-separated list of thread IDs | |
b8ff78ce JB |
28978 | @item l |
28979 | (lower case letter @samp{L}) denotes end of list. | |
ee2d5c50 AC |
28980 | @end table |
28981 | ||
28982 | In response to each query, the target will reply with a list of one or | |
b90a069a | 28983 | more thread IDs, separated by commas. |
e1aac25b | 28984 | @value{GDBN} will respond to each reply with a request for more thread |
b8ff78ce | 28985 | ids (using the @samp{qs} form of the query), until the target responds |
b90a069a SL |
28986 | with @samp{l} (lower-case el, for @dfn{last}). |
28987 | Refer to @ref{thread-id syntax}, for the format of the @var{thread-id} | |
28988 | fields. | |
c906108c | 28989 | |
b8ff78ce | 28990 | @item qGetTLSAddr:@var{thread-id},@var{offset},@var{lm} |
ff2587ec | 28991 | @cindex get thread-local storage address, remote request |
b8ff78ce | 28992 | @cindex @samp{qGetTLSAddr} packet |
ff2587ec WZ |
28993 | Fetch the address associated with thread local storage specified |
28994 | by @var{thread-id}, @var{offset}, and @var{lm}. | |
28995 | ||
b90a069a SL |
28996 | @var{thread-id} is the thread ID associated with the |
28997 | thread for which to fetch the TLS address. @xref{thread-id syntax}. | |
ff2587ec WZ |
28998 | |
28999 | @var{offset} is the (big endian, hex encoded) offset associated with the | |
29000 | thread local variable. (This offset is obtained from the debug | |
29001 | information associated with the variable.) | |
29002 | ||
db2e3e2e | 29003 | @var{lm} is the (big endian, hex encoded) OS/ABI-specific encoding of the |
ff2587ec WZ |
29004 | the load module associated with the thread local storage. For example, |
29005 | a @sc{gnu}/Linux system will pass the link map address of the shared | |
29006 | object associated with the thread local storage under consideration. | |
29007 | Other operating environments may choose to represent the load module | |
29008 | differently, so the precise meaning of this parameter will vary. | |
ee2d5c50 AC |
29009 | |
29010 | Reply: | |
b8ff78ce JB |
29011 | @table @samp |
29012 | @item @var{XX}@dots{} | |
ff2587ec WZ |
29013 | Hex encoded (big endian) bytes representing the address of the thread |
29014 | local storage requested. | |
29015 | ||
b8ff78ce JB |
29016 | @item E @var{nn} |
29017 | An error occurred. @var{nn} are hex digits. | |
ff2587ec | 29018 | |
b8ff78ce JB |
29019 | @item |
29020 | An empty reply indicates that @samp{qGetTLSAddr} is not supported by the stub. | |
ee2d5c50 AC |
29021 | @end table |
29022 | ||
b8ff78ce | 29023 | @item qL @var{startflag} @var{threadcount} @var{nextthread} |
8e04817f AC |
29024 | Obtain thread information from RTOS. Where: @var{startflag} (one hex |
29025 | digit) is one to indicate the first query and zero to indicate a | |
29026 | subsequent query; @var{threadcount} (two hex digits) is the maximum | |
29027 | number of threads the response packet can contain; and @var{nextthread} | |
29028 | (eight hex digits), for subsequent queries (@var{startflag} is zero), is | |
29029 | returned in the response as @var{argthread}. | |
ee2d5c50 | 29030 | |
b8ff78ce | 29031 | Don't use this packet; use the @samp{qfThreadInfo} query instead (see above). |
ee2d5c50 AC |
29032 | |
29033 | Reply: | |
29034 | @table @samp | |
b8ff78ce | 29035 | @item qM @var{count} @var{done} @var{argthread} @var{thread}@dots{} |
8e04817f AC |
29036 | Where: @var{count} (two hex digits) is the number of threads being |
29037 | returned; @var{done} (one hex digit) is zero to indicate more threads | |
29038 | and one indicates no further threads; @var{argthreadid} (eight hex | |
b8ff78ce | 29039 | digits) is @var{nextthread} from the request packet; @var{thread}@dots{} |
ee2d5c50 | 29040 | is a sequence of thread IDs from the target. @var{threadid} (eight hex |
8e04817f | 29041 | digits). See @code{remote.c:parse_threadlist_response()}. |
ee2d5c50 | 29042 | @end table |
c906108c | 29043 | |
b8ff78ce | 29044 | @item qOffsets |
9c16f35a | 29045 | @cindex section offsets, remote request |
b8ff78ce | 29046 | @cindex @samp{qOffsets} packet |
31d99776 DJ |
29047 | Get section offsets that the target used when relocating the downloaded |
29048 | image. | |
c906108c | 29049 | |
ee2d5c50 AC |
29050 | Reply: |
29051 | @table @samp | |
31d99776 DJ |
29052 | @item Text=@var{xxx};Data=@var{yyy}@r{[};Bss=@var{zzz}@r{]} |
29053 | Relocate the @code{Text} section by @var{xxx} from its original address. | |
29054 | Relocate the @code{Data} section by @var{yyy} from its original address. | |
29055 | If the object file format provides segment information (e.g.@: @sc{elf} | |
29056 | @samp{PT_LOAD} program headers), @value{GDBN} will relocate entire | |
29057 | segments by the supplied offsets. | |
29058 | ||
29059 | @emph{Note: while a @code{Bss} offset may be included in the response, | |
29060 | @value{GDBN} ignores this and instead applies the @code{Data} offset | |
29061 | to the @code{Bss} section.} | |
29062 | ||
29063 | @item TextSeg=@var{xxx}@r{[};DataSeg=@var{yyy}@r{]} | |
29064 | Relocate the first segment of the object file, which conventionally | |
29065 | contains program code, to a starting address of @var{xxx}. If | |
29066 | @samp{DataSeg} is specified, relocate the second segment, which | |
29067 | conventionally contains modifiable data, to a starting address of | |
29068 | @var{yyy}. @value{GDBN} will report an error if the object file | |
29069 | does not contain segment information, or does not contain at least | |
29070 | as many segments as mentioned in the reply. Extra segments are | |
29071 | kept at fixed offsets relative to the last relocated segment. | |
ee2d5c50 AC |
29072 | @end table |
29073 | ||
b90a069a | 29074 | @item qP @var{mode} @var{thread-id} |
9c16f35a | 29075 | @cindex thread information, remote request |
b8ff78ce | 29076 | @cindex @samp{qP} packet |
b90a069a SL |
29077 | Returns information on @var{thread-id}. Where: @var{mode} is a hex |
29078 | encoded 32 bit mode; @var{thread-id} is a thread ID | |
29079 | (@pxref{thread-id syntax}). | |
ee2d5c50 | 29080 | |
aa56d27a JB |
29081 | Don't use this packet; use the @samp{qThreadExtraInfo} query instead |
29082 | (see below). | |
29083 | ||
b8ff78ce | 29084 | Reply: see @code{remote.c:remote_unpack_thread_info_response()}. |
c906108c | 29085 | |
8b23ecc4 SL |
29086 | @item QNonStop:1 |
29087 | @item QNonStop:0 | |
29088 | @cindex non-stop mode, remote request | |
29089 | @cindex @samp{QNonStop} packet | |
29090 | @anchor{QNonStop} | |
29091 | Enter non-stop (@samp{QNonStop:1}) or all-stop (@samp{QNonStop:0}) mode. | |
29092 | @xref{Remote Non-Stop}, for more information. | |
29093 | ||
29094 | Reply: | |
29095 | @table @samp | |
29096 | @item OK | |
29097 | The request succeeded. | |
29098 | ||
29099 | @item E @var{nn} | |
29100 | An error occurred. @var{nn} are hex digits. | |
29101 | ||
29102 | @item | |
29103 | An empty reply indicates that @samp{QNonStop} is not supported by | |
29104 | the stub. | |
29105 | @end table | |
29106 | ||
29107 | This packet is not probed by default; the remote stub must request it, | |
29108 | by supplying an appropriate @samp{qSupported} response (@pxref{qSupported}). | |
29109 | Use of this packet is controlled by the @code{set non-stop} command; | |
29110 | @pxref{Non-Stop Mode}. | |
29111 | ||
89be2091 DJ |
29112 | @item QPassSignals: @var{signal} @r{[};@var{signal}@r{]}@dots{} |
29113 | @cindex pass signals to inferior, remote request | |
29114 | @cindex @samp{QPassSignals} packet | |
23181151 | 29115 | @anchor{QPassSignals} |
89be2091 DJ |
29116 | Each listed @var{signal} should be passed directly to the inferior process. |
29117 | Signals are numbered identically to continue packets and stop replies | |
29118 | (@pxref{Stop Reply Packets}). Each @var{signal} list item should be | |
29119 | strictly greater than the previous item. These signals do not need to stop | |
29120 | the inferior, or be reported to @value{GDBN}. All other signals should be | |
29121 | reported to @value{GDBN}. Multiple @samp{QPassSignals} packets do not | |
29122 | combine; any earlier @samp{QPassSignals} list is completely replaced by the | |
29123 | new list. This packet improves performance when using @samp{handle | |
29124 | @var{signal} nostop noprint pass}. | |
29125 | ||
29126 | Reply: | |
29127 | @table @samp | |
29128 | @item OK | |
29129 | The request succeeded. | |
29130 | ||
29131 | @item E @var{nn} | |
29132 | An error occurred. @var{nn} are hex digits. | |
29133 | ||
29134 | @item | |
29135 | An empty reply indicates that @samp{QPassSignals} is not supported by | |
29136 | the stub. | |
29137 | @end table | |
29138 | ||
29139 | Use of this packet is controlled by the @code{set remote pass-signals} | |
79a6e687 | 29140 | command (@pxref{Remote Configuration, set remote pass-signals}). |
89be2091 DJ |
29141 | This packet is not probed by default; the remote stub must request it, |
29142 | by supplying an appropriate @samp{qSupported} response (@pxref{qSupported}). | |
29143 | ||
b8ff78ce | 29144 | @item qRcmd,@var{command} |
ff2587ec | 29145 | @cindex execute remote command, remote request |
b8ff78ce | 29146 | @cindex @samp{qRcmd} packet |
ff2587ec | 29147 | @var{command} (hex encoded) is passed to the local interpreter for |
b8ff78ce JB |
29148 | execution. Invalid commands should be reported using the output |
29149 | string. Before the final result packet, the target may also respond | |
29150 | with a number of intermediate @samp{O@var{output}} console output | |
29151 | packets. @emph{Implementors should note that providing access to a | |
29152 | stubs's interpreter may have security implications}. | |
fa93a9d8 | 29153 | |
ff2587ec WZ |
29154 | Reply: |
29155 | @table @samp | |
29156 | @item OK | |
29157 | A command response with no output. | |
29158 | @item @var{OUTPUT} | |
29159 | A command response with the hex encoded output string @var{OUTPUT}. | |
b8ff78ce | 29160 | @item E @var{NN} |
ff2587ec | 29161 | Indicate a badly formed request. |
b8ff78ce JB |
29162 | @item |
29163 | An empty reply indicates that @samp{qRcmd} is not recognized. | |
ff2587ec | 29164 | @end table |
fa93a9d8 | 29165 | |
aa56d27a JB |
29166 | (Note that the @code{qRcmd} packet's name is separated from the |
29167 | command by a @samp{,}, not a @samp{:}, contrary to the naming | |
29168 | conventions above. Please don't use this packet as a model for new | |
29169 | packets.) | |
29170 | ||
08388c79 DE |
29171 | @item qSearch:memory:@var{address};@var{length};@var{search-pattern} |
29172 | @cindex searching memory, in remote debugging | |
29173 | @cindex @samp{qSearch:memory} packet | |
29174 | @anchor{qSearch memory} | |
29175 | Search @var{length} bytes at @var{address} for @var{search-pattern}. | |
29176 | @var{address} and @var{length} are encoded in hex. | |
29177 | @var{search-pattern} is a sequence of bytes, hex encoded. | |
29178 | ||
29179 | Reply: | |
29180 | @table @samp | |
29181 | @item 0 | |
29182 | The pattern was not found. | |
29183 | @item 1,address | |
29184 | The pattern was found at @var{address}. | |
29185 | @item E @var{NN} | |
29186 | A badly formed request or an error was encountered while searching memory. | |
29187 | @item | |
29188 | An empty reply indicates that @samp{qSearch:memory} is not recognized. | |
29189 | @end table | |
29190 | ||
a6f3e723 SL |
29191 | @item QStartNoAckMode |
29192 | @cindex @samp{QStartNoAckMode} packet | |
29193 | @anchor{QStartNoAckMode} | |
29194 | Request that the remote stub disable the normal @samp{+}/@samp{-} | |
29195 | protocol acknowledgments (@pxref{Packet Acknowledgment}). | |
29196 | ||
29197 | Reply: | |
29198 | @table @samp | |
29199 | @item OK | |
29200 | The stub has switched to no-acknowledgment mode. | |
29201 | @value{GDBN} acknowledges this reponse, | |
29202 | but neither the stub nor @value{GDBN} shall send or expect further | |
29203 | @samp{+}/@samp{-} acknowledgments in the current connection. | |
29204 | @item | |
29205 | An empty reply indicates that the stub does not support no-acknowledgment mode. | |
29206 | @end table | |
29207 | ||
be2a5f71 DJ |
29208 | @item qSupported @r{[}:@var{gdbfeature} @r{[};@var{gdbfeature}@r{]}@dots{} @r{]} |
29209 | @cindex supported packets, remote query | |
29210 | @cindex features of the remote protocol | |
29211 | @cindex @samp{qSupported} packet | |
0876f84a | 29212 | @anchor{qSupported} |
be2a5f71 DJ |
29213 | Tell the remote stub about features supported by @value{GDBN}, and |
29214 | query the stub for features it supports. This packet allows | |
29215 | @value{GDBN} and the remote stub to take advantage of each others' | |
29216 | features. @samp{qSupported} also consolidates multiple feature probes | |
29217 | at startup, to improve @value{GDBN} performance---a single larger | |
29218 | packet performs better than multiple smaller probe packets on | |
29219 | high-latency links. Some features may enable behavior which must not | |
29220 | be on by default, e.g.@: because it would confuse older clients or | |
29221 | stubs. Other features may describe packets which could be | |
29222 | automatically probed for, but are not. These features must be | |
29223 | reported before @value{GDBN} will use them. This ``default | |
29224 | unsupported'' behavior is not appropriate for all packets, but it | |
29225 | helps to keep the initial connection time under control with new | |
29226 | versions of @value{GDBN} which support increasing numbers of packets. | |
29227 | ||
29228 | Reply: | |
29229 | @table @samp | |
29230 | @item @var{stubfeature} @r{[};@var{stubfeature}@r{]}@dots{} | |
29231 | The stub supports or does not support each returned @var{stubfeature}, | |
29232 | depending on the form of each @var{stubfeature} (see below for the | |
29233 | possible forms). | |
29234 | @item | |
29235 | An empty reply indicates that @samp{qSupported} is not recognized, | |
29236 | or that no features needed to be reported to @value{GDBN}. | |
29237 | @end table | |
29238 | ||
29239 | The allowed forms for each feature (either a @var{gdbfeature} in the | |
29240 | @samp{qSupported} packet, or a @var{stubfeature} in the response) | |
29241 | are: | |
29242 | ||
29243 | @table @samp | |
29244 | @item @var{name}=@var{value} | |
29245 | The remote protocol feature @var{name} is supported, and associated | |
29246 | with the specified @var{value}. The format of @var{value} depends | |
29247 | on the feature, but it must not include a semicolon. | |
29248 | @item @var{name}+ | |
29249 | The remote protocol feature @var{name} is supported, and does not | |
29250 | need an associated value. | |
29251 | @item @var{name}- | |
29252 | The remote protocol feature @var{name} is not supported. | |
29253 | @item @var{name}? | |
29254 | The remote protocol feature @var{name} may be supported, and | |
29255 | @value{GDBN} should auto-detect support in some other way when it is | |
29256 | needed. This form will not be used for @var{gdbfeature} notifications, | |
29257 | but may be used for @var{stubfeature} responses. | |
29258 | @end table | |
29259 | ||
29260 | Whenever the stub receives a @samp{qSupported} request, the | |
29261 | supplied set of @value{GDBN} features should override any previous | |
29262 | request. This allows @value{GDBN} to put the stub in a known | |
29263 | state, even if the stub had previously been communicating with | |
29264 | a different version of @value{GDBN}. | |
29265 | ||
b90a069a SL |
29266 | The following values of @var{gdbfeature} (for the packet sent by @value{GDBN}) |
29267 | are defined: | |
29268 | ||
29269 | @table @samp | |
29270 | @item multiprocess | |
29271 | This feature indicates whether @value{GDBN} supports multiprocess | |
29272 | extensions to the remote protocol. @value{GDBN} does not use such | |
29273 | extensions unless the stub also reports that it supports them by | |
29274 | including @samp{multiprocess+} in its @samp{qSupported} reply. | |
29275 | @xref{multiprocess extensions}, for details. | |
29276 | @end table | |
29277 | ||
29278 | Stubs should ignore any unknown values for | |
be2a5f71 DJ |
29279 | @var{gdbfeature}. Any @value{GDBN} which sends a @samp{qSupported} |
29280 | packet supports receiving packets of unlimited length (earlier | |
b90a069a | 29281 | versions of @value{GDBN} may reject overly long responses). Additional values |
be2a5f71 DJ |
29282 | for @var{gdbfeature} may be defined in the future to let the stub take |
29283 | advantage of new features in @value{GDBN}, e.g.@: incompatible | |
b90a069a SL |
29284 | improvements in the remote protocol---the @samp{multiprocess} feature is |
29285 | an example of such a feature. The stub's reply should be independent | |
be2a5f71 DJ |
29286 | of the @var{gdbfeature} entries sent by @value{GDBN}; first @value{GDBN} |
29287 | describes all the features it supports, and then the stub replies with | |
29288 | all the features it supports. | |
29289 | ||
29290 | Similarly, @value{GDBN} will silently ignore unrecognized stub feature | |
29291 | responses, as long as each response uses one of the standard forms. | |
29292 | ||
29293 | Some features are flags. A stub which supports a flag feature | |
29294 | should respond with a @samp{+} form response. Other features | |
29295 | require values, and the stub should respond with an @samp{=} | |
29296 | form response. | |
29297 | ||
29298 | Each feature has a default value, which @value{GDBN} will use if | |
29299 | @samp{qSupported} is not available or if the feature is not mentioned | |
29300 | in the @samp{qSupported} response. The default values are fixed; a | |
29301 | stub is free to omit any feature responses that match the defaults. | |
29302 | ||
29303 | Not all features can be probed, but for those which can, the probing | |
29304 | mechanism is useful: in some cases, a stub's internal | |
29305 | architecture may not allow the protocol layer to know some information | |
29306 | about the underlying target in advance. This is especially common in | |
29307 | stubs which may be configured for multiple targets. | |
29308 | ||
29309 | These are the currently defined stub features and their properties: | |
29310 | ||
cfa9d6d9 | 29311 | @multitable @columnfractions 0.35 0.2 0.12 0.2 |
be2a5f71 DJ |
29312 | @c NOTE: The first row should be @headitem, but we do not yet require |
29313 | @c a new enough version of Texinfo (4.7) to use @headitem. | |
0876f84a | 29314 | @item Feature Name |
be2a5f71 DJ |
29315 | @tab Value Required |
29316 | @tab Default | |
29317 | @tab Probe Allowed | |
29318 | ||
29319 | @item @samp{PacketSize} | |
29320 | @tab Yes | |
29321 | @tab @samp{-} | |
29322 | @tab No | |
29323 | ||
0876f84a DJ |
29324 | @item @samp{qXfer:auxv:read} |
29325 | @tab No | |
29326 | @tab @samp{-} | |
29327 | @tab Yes | |
29328 | ||
23181151 DJ |
29329 | @item @samp{qXfer:features:read} |
29330 | @tab No | |
29331 | @tab @samp{-} | |
29332 | @tab Yes | |
29333 | ||
cfa9d6d9 DJ |
29334 | @item @samp{qXfer:libraries:read} |
29335 | @tab No | |
29336 | @tab @samp{-} | |
29337 | @tab Yes | |
29338 | ||
68437a39 DJ |
29339 | @item @samp{qXfer:memory-map:read} |
29340 | @tab No | |
29341 | @tab @samp{-} | |
29342 | @tab Yes | |
29343 | ||
0e7f50da UW |
29344 | @item @samp{qXfer:spu:read} |
29345 | @tab No | |
29346 | @tab @samp{-} | |
29347 | @tab Yes | |
29348 | ||
29349 | @item @samp{qXfer:spu:write} | |
29350 | @tab No | |
29351 | @tab @samp{-} | |
29352 | @tab Yes | |
29353 | ||
4aa995e1 PA |
29354 | @item @samp{qXfer:siginfo:read} |
29355 | @tab No | |
29356 | @tab @samp{-} | |
29357 | @tab Yes | |
29358 | ||
29359 | @item @samp{qXfer:siginfo:write} | |
29360 | @tab No | |
29361 | @tab @samp{-} | |
29362 | @tab Yes | |
29363 | ||
8b23ecc4 SL |
29364 | @item @samp{QNonStop} |
29365 | @tab No | |
29366 | @tab @samp{-} | |
29367 | @tab Yes | |
29368 | ||
89be2091 DJ |
29369 | @item @samp{QPassSignals} |
29370 | @tab No | |
29371 | @tab @samp{-} | |
29372 | @tab Yes | |
29373 | ||
a6f3e723 SL |
29374 | @item @samp{QStartNoAckMode} |
29375 | @tab No | |
29376 | @tab @samp{-} | |
29377 | @tab Yes | |
29378 | ||
b90a069a SL |
29379 | @item @samp{multiprocess} |
29380 | @tab No | |
29381 | @tab @samp{-} | |
29382 | @tab No | |
29383 | ||
782b2b07 SS |
29384 | @item @samp{ConditionalTracepoints} |
29385 | @tab No | |
29386 | @tab @samp{-} | |
29387 | @tab No | |
29388 | ||
0d772ac9 MS |
29389 | @item @samp{ReverseContinue} |
29390 | @tab No | |
2f8132f3 | 29391 | @tab @samp{-} |
0d772ac9 MS |
29392 | @tab No |
29393 | ||
29394 | @item @samp{ReverseStep} | |
29395 | @tab No | |
2f8132f3 | 29396 | @tab @samp{-} |
0d772ac9 MS |
29397 | @tab No |
29398 | ||
be2a5f71 DJ |
29399 | @end multitable |
29400 | ||
29401 | These are the currently defined stub features, in more detail: | |
29402 | ||
29403 | @table @samp | |
29404 | @cindex packet size, remote protocol | |
29405 | @item PacketSize=@var{bytes} | |
29406 | The remote stub can accept packets up to at least @var{bytes} in | |
29407 | length. @value{GDBN} will send packets up to this size for bulk | |
29408 | transfers, and will never send larger packets. This is a limit on the | |
29409 | data characters in the packet, including the frame and checksum. | |
29410 | There is no trailing NUL byte in a remote protocol packet; if the stub | |
29411 | stores packets in a NUL-terminated format, it should allow an extra | |
29412 | byte in its buffer for the NUL. If this stub feature is not supported, | |
29413 | @value{GDBN} guesses based on the size of the @samp{g} packet response. | |
29414 | ||
0876f84a DJ |
29415 | @item qXfer:auxv:read |
29416 | The remote stub understands the @samp{qXfer:auxv:read} packet | |
29417 | (@pxref{qXfer auxiliary vector read}). | |
29418 | ||
23181151 DJ |
29419 | @item qXfer:features:read |
29420 | The remote stub understands the @samp{qXfer:features:read} packet | |
29421 | (@pxref{qXfer target description read}). | |
29422 | ||
cfa9d6d9 DJ |
29423 | @item qXfer:libraries:read |
29424 | The remote stub understands the @samp{qXfer:libraries:read} packet | |
29425 | (@pxref{qXfer library list read}). | |
29426 | ||
23181151 DJ |
29427 | @item qXfer:memory-map:read |
29428 | The remote stub understands the @samp{qXfer:memory-map:read} packet | |
29429 | (@pxref{qXfer memory map read}). | |
29430 | ||
0e7f50da UW |
29431 | @item qXfer:spu:read |
29432 | The remote stub understands the @samp{qXfer:spu:read} packet | |
29433 | (@pxref{qXfer spu read}). | |
29434 | ||
29435 | @item qXfer:spu:write | |
29436 | The remote stub understands the @samp{qXfer:spu:write} packet | |
29437 | (@pxref{qXfer spu write}). | |
29438 | ||
4aa995e1 PA |
29439 | @item qXfer:siginfo:read |
29440 | The remote stub understands the @samp{qXfer:siginfo:read} packet | |
29441 | (@pxref{qXfer siginfo read}). | |
29442 | ||
29443 | @item qXfer:siginfo:write | |
29444 | The remote stub understands the @samp{qXfer:siginfo:write} packet | |
29445 | (@pxref{qXfer siginfo write}). | |
29446 | ||
8b23ecc4 SL |
29447 | @item QNonStop |
29448 | The remote stub understands the @samp{QNonStop} packet | |
29449 | (@pxref{QNonStop}). | |
29450 | ||
23181151 DJ |
29451 | @item QPassSignals |
29452 | The remote stub understands the @samp{QPassSignals} packet | |
29453 | (@pxref{QPassSignals}). | |
29454 | ||
a6f3e723 SL |
29455 | @item QStartNoAckMode |
29456 | The remote stub understands the @samp{QStartNoAckMode} packet and | |
29457 | prefers to operate in no-acknowledgment mode. @xref{Packet Acknowledgment}. | |
29458 | ||
b90a069a SL |
29459 | @item multiprocess |
29460 | @anchor{multiprocess extensions} | |
29461 | @cindex multiprocess extensions, in remote protocol | |
29462 | The remote stub understands the multiprocess extensions to the remote | |
29463 | protocol syntax. The multiprocess extensions affect the syntax of | |
29464 | thread IDs in both packets and replies (@pxref{thread-id syntax}), and | |
29465 | add process IDs to the @samp{D} packet and @samp{W} and @samp{X} | |
29466 | replies. Note that reporting this feature indicates support for the | |
29467 | syntactic extensions only, not that the stub necessarily supports | |
29468 | debugging of more than one process at a time. The stub must not use | |
29469 | multiprocess extensions in packet replies unless @value{GDBN} has also | |
29470 | indicated it supports them in its @samp{qSupported} request. | |
29471 | ||
07e059b5 VP |
29472 | @item qXfer:osdata:read |
29473 | The remote stub understands the @samp{qXfer:osdata:read} packet | |
29474 | ((@pxref{qXfer osdata read}). | |
29475 | ||
782b2b07 SS |
29476 | @item ConditionalTracepoints |
29477 | The remote stub accepts and implements conditional expressions defined | |
29478 | for tracepoints (@pxref{Tracepoint Conditions}). | |
29479 | ||
0d772ac9 MS |
29480 | @item ReverseContinue |
29481 | The remote stub accepts and implements the reverse continue packet | |
29482 | (@pxref{bc}). | |
29483 | ||
29484 | @item ReverseStep | |
29485 | The remote stub accepts and implements the reverse step packet | |
29486 | (@pxref{bs}). | |
29487 | ||
be2a5f71 DJ |
29488 | @end table |
29489 | ||
b8ff78ce | 29490 | @item qSymbol:: |
ff2587ec | 29491 | @cindex symbol lookup, remote request |
b8ff78ce | 29492 | @cindex @samp{qSymbol} packet |
ff2587ec WZ |
29493 | Notify the target that @value{GDBN} is prepared to serve symbol lookup |
29494 | requests. Accept requests from the target for the values of symbols. | |
fa93a9d8 JB |
29495 | |
29496 | Reply: | |
ff2587ec | 29497 | @table @samp |
b8ff78ce | 29498 | @item OK |
ff2587ec | 29499 | The target does not need to look up any (more) symbols. |
b8ff78ce | 29500 | @item qSymbol:@var{sym_name} |
ff2587ec WZ |
29501 | The target requests the value of symbol @var{sym_name} (hex encoded). |
29502 | @value{GDBN} may provide the value by using the | |
b8ff78ce JB |
29503 | @samp{qSymbol:@var{sym_value}:@var{sym_name}} message, described |
29504 | below. | |
ff2587ec | 29505 | @end table |
83761cbd | 29506 | |
b8ff78ce | 29507 | @item qSymbol:@var{sym_value}:@var{sym_name} |
ff2587ec WZ |
29508 | Set the value of @var{sym_name} to @var{sym_value}. |
29509 | ||
29510 | @var{sym_name} (hex encoded) is the name of a symbol whose value the | |
29511 | target has previously requested. | |
29512 | ||
29513 | @var{sym_value} (hex) is the value for symbol @var{sym_name}. If | |
29514 | @value{GDBN} cannot supply a value for @var{sym_name}, then this field | |
29515 | will be empty. | |
29516 | ||
29517 | Reply: | |
29518 | @table @samp | |
b8ff78ce | 29519 | @item OK |
ff2587ec | 29520 | The target does not need to look up any (more) symbols. |
b8ff78ce | 29521 | @item qSymbol:@var{sym_name} |
ff2587ec WZ |
29522 | The target requests the value of a new symbol @var{sym_name} (hex |
29523 | encoded). @value{GDBN} will continue to supply the values of symbols | |
29524 | (if available), until the target ceases to request them. | |
fa93a9d8 | 29525 | @end table |
0abb7bc7 | 29526 | |
9d29849a JB |
29527 | @item QTDP |
29528 | @itemx QTFrame | |
29529 | @xref{Tracepoint Packets}. | |
29530 | ||
b90a069a | 29531 | @item qThreadExtraInfo,@var{thread-id} |
ff2587ec | 29532 | @cindex thread attributes info, remote request |
b8ff78ce JB |
29533 | @cindex @samp{qThreadExtraInfo} packet |
29534 | Obtain a printable string description of a thread's attributes from | |
b90a069a SL |
29535 | the target OS. @var{thread-id} is a thread ID; |
29536 | see @ref{thread-id syntax}. This | |
b8ff78ce JB |
29537 | string may contain anything that the target OS thinks is interesting |
29538 | for @value{GDBN} to tell the user about the thread. The string is | |
29539 | displayed in @value{GDBN}'s @code{info threads} display. Some | |
29540 | examples of possible thread extra info strings are @samp{Runnable}, or | |
29541 | @samp{Blocked on Mutex}. | |
ff2587ec WZ |
29542 | |
29543 | Reply: | |
29544 | @table @samp | |
b8ff78ce JB |
29545 | @item @var{XX}@dots{} |
29546 | Where @samp{@var{XX}@dots{}} is a hex encoding of @sc{ascii} data, | |
29547 | comprising the printable string containing the extra information about | |
29548 | the thread's attributes. | |
ff2587ec | 29549 | @end table |
814e32d7 | 29550 | |
aa56d27a JB |
29551 | (Note that the @code{qThreadExtraInfo} packet's name is separated from |
29552 | the command by a @samp{,}, not a @samp{:}, contrary to the naming | |
29553 | conventions above. Please don't use this packet as a model for new | |
29554 | packets.) | |
29555 | ||
9d29849a JB |
29556 | @item QTStart |
29557 | @itemx QTStop | |
29558 | @itemx QTinit | |
29559 | @itemx QTro | |
29560 | @itemx qTStatus | |
29561 | @xref{Tracepoint Packets}. | |
29562 | ||
0876f84a DJ |
29563 | @item qXfer:@var{object}:read:@var{annex}:@var{offset},@var{length} |
29564 | @cindex read special object, remote request | |
29565 | @cindex @samp{qXfer} packet | |
68437a39 | 29566 | @anchor{qXfer read} |
0876f84a DJ |
29567 | Read uninterpreted bytes from the target's special data area |
29568 | identified by the keyword @var{object}. Request @var{length} bytes | |
29569 | starting at @var{offset} bytes into the data. The content and | |
0e7f50da | 29570 | encoding of @var{annex} is specific to @var{object}; it can supply |
0876f84a DJ |
29571 | additional details about what data to access. |
29572 | ||
29573 | Here are the specific requests of this form defined so far. All | |
29574 | @samp{qXfer:@var{object}:read:@dots{}} requests use the same reply | |
29575 | formats, listed below. | |
29576 | ||
29577 | @table @samp | |
29578 | @item qXfer:auxv:read::@var{offset},@var{length} | |
29579 | @anchor{qXfer auxiliary vector read} | |
29580 | Access the target's @dfn{auxiliary vector}. @xref{OS Information, | |
427c3a89 | 29581 | auxiliary vector}. Note @var{annex} must be empty. |
0876f84a DJ |
29582 | |
29583 | This packet is not probed by default; the remote stub must request it, | |
89be2091 | 29584 | by supplying an appropriate @samp{qSupported} response (@pxref{qSupported}). |
0876f84a | 29585 | |
23181151 DJ |
29586 | @item qXfer:features:read:@var{annex}:@var{offset},@var{length} |
29587 | @anchor{qXfer target description read} | |
29588 | Access the @dfn{target description}. @xref{Target Descriptions}. The | |
29589 | annex specifies which XML document to access. The main description is | |
29590 | always loaded from the @samp{target.xml} annex. | |
29591 | ||
29592 | This packet is not probed by default; the remote stub must request it, | |
29593 | by supplying an appropriate @samp{qSupported} response (@pxref{qSupported}). | |
29594 | ||
cfa9d6d9 DJ |
29595 | @item qXfer:libraries:read:@var{annex}:@var{offset},@var{length} |
29596 | @anchor{qXfer library list read} | |
29597 | Access the target's list of loaded libraries. @xref{Library List Format}. | |
29598 | The annex part of the generic @samp{qXfer} packet must be empty | |
29599 | (@pxref{qXfer read}). | |
29600 | ||
29601 | Targets which maintain a list of libraries in the program's memory do | |
29602 | not need to implement this packet; it is designed for platforms where | |
29603 | the operating system manages the list of loaded libraries. | |
29604 | ||
29605 | This packet is not probed by default; the remote stub must request it, | |
29606 | by supplying an appropriate @samp{qSupported} response (@pxref{qSupported}). | |
29607 | ||
68437a39 DJ |
29608 | @item qXfer:memory-map:read::@var{offset},@var{length} |
29609 | @anchor{qXfer memory map read} | |
79a6e687 | 29610 | Access the target's @dfn{memory-map}. @xref{Memory Map Format}. The |
68437a39 DJ |
29611 | annex part of the generic @samp{qXfer} packet must be empty |
29612 | (@pxref{qXfer read}). | |
29613 | ||
0e7f50da UW |
29614 | This packet is not probed by default; the remote stub must request it, |
29615 | by supplying an appropriate @samp{qSupported} response (@pxref{qSupported}). | |
29616 | ||
4aa995e1 PA |
29617 | @item qXfer:siginfo:read::@var{offset},@var{length} |
29618 | @anchor{qXfer siginfo read} | |
29619 | Read contents of the extra signal information on the target | |
29620 | system. The annex part of the generic @samp{qXfer} packet must be | |
29621 | empty (@pxref{qXfer read}). | |
29622 | ||
29623 | This packet is not probed by default; the remote stub must request it, | |
29624 | by supplying an appropriate @samp{qSupported} response | |
29625 | (@pxref{qSupported}). | |
29626 | ||
0e7f50da UW |
29627 | @item qXfer:spu:read:@var{annex}:@var{offset},@var{length} |
29628 | @anchor{qXfer spu read} | |
29629 | Read contents of an @code{spufs} file on the target system. The | |
29630 | annex specifies which file to read; it must be of the form | |
29631 | @file{@var{id}/@var{name}}, where @var{id} specifies an SPU context ID | |
29632 | in the target process, and @var{name} identifes the @code{spufs} file | |
29633 | in that context to be accessed. | |
29634 | ||
68437a39 | 29635 | This packet is not probed by default; the remote stub must request it, |
07e059b5 VP |
29636 | by supplying an appropriate @samp{qSupported} response |
29637 | (@pxref{qSupported}). | |
29638 | ||
29639 | @item qXfer:osdata:read::@var{offset},@var{length} | |
29640 | @anchor{qXfer osdata read} | |
29641 | Access the target's @dfn{operating system information}. | |
29642 | @xref{Operating System Information}. | |
29643 | ||
68437a39 DJ |
29644 | @end table |
29645 | ||
0876f84a DJ |
29646 | Reply: |
29647 | @table @samp | |
29648 | @item m @var{data} | |
29649 | Data @var{data} (@pxref{Binary Data}) has been read from the | |
29650 | target. There may be more data at a higher address (although | |
29651 | it is permitted to return @samp{m} even for the last valid | |
29652 | block of data, as long as at least one byte of data was read). | |
29653 | @var{data} may have fewer bytes than the @var{length} in the | |
29654 | request. | |
29655 | ||
29656 | @item l @var{data} | |
29657 | Data @var{data} (@pxref{Binary Data}) has been read from the target. | |
29658 | There is no more data to be read. @var{data} may have fewer bytes | |
29659 | than the @var{length} in the request. | |
29660 | ||
29661 | @item l | |
29662 | The @var{offset} in the request is at the end of the data. | |
29663 | There is no more data to be read. | |
29664 | ||
29665 | @item E00 | |
29666 | The request was malformed, or @var{annex} was invalid. | |
29667 | ||
29668 | @item E @var{nn} | |
29669 | The offset was invalid, or there was an error encountered reading the data. | |
29670 | @var{nn} is a hex-encoded @code{errno} value. | |
29671 | ||
29672 | @item | |
29673 | An empty reply indicates the @var{object} string was not recognized by | |
29674 | the stub, or that the object does not support reading. | |
29675 | @end table | |
29676 | ||
29677 | @item qXfer:@var{object}:write:@var{annex}:@var{offset}:@var{data}@dots{} | |
29678 | @cindex write data into object, remote request | |
4aa995e1 | 29679 | @anchor{qXfer write} |
0876f84a DJ |
29680 | Write uninterpreted bytes into the target's special data area |
29681 | identified by the keyword @var{object}, starting at @var{offset} bytes | |
0e7f50da | 29682 | into the data. @var{data}@dots{} is the binary-encoded data |
0876f84a | 29683 | (@pxref{Binary Data}) to be written. The content and encoding of @var{annex} |
0e7f50da | 29684 | is specific to @var{object}; it can supply additional details about what data |
0876f84a DJ |
29685 | to access. |
29686 | ||
0e7f50da UW |
29687 | Here are the specific requests of this form defined so far. All |
29688 | @samp{qXfer:@var{object}:write:@dots{}} requests use the same reply | |
29689 | formats, listed below. | |
29690 | ||
29691 | @table @samp | |
4aa995e1 PA |
29692 | @item qXfer:siginfo:write::@var{offset}:@var{data}@dots{} |
29693 | @anchor{qXfer siginfo write} | |
29694 | Write @var{data} to the extra signal information on the target system. | |
29695 | The annex part of the generic @samp{qXfer} packet must be | |
29696 | empty (@pxref{qXfer write}). | |
29697 | ||
29698 | This packet is not probed by default; the remote stub must request it, | |
29699 | by supplying an appropriate @samp{qSupported} response | |
29700 | (@pxref{qSupported}). | |
29701 | ||
84fcdf95 | 29702 | @item qXfer:spu:write:@var{annex}:@var{offset}:@var{data}@dots{} |
0e7f50da UW |
29703 | @anchor{qXfer spu write} |
29704 | Write @var{data} to an @code{spufs} file on the target system. The | |
29705 | annex specifies which file to write; it must be of the form | |
29706 | @file{@var{id}/@var{name}}, where @var{id} specifies an SPU context ID | |
29707 | in the target process, and @var{name} identifes the @code{spufs} file | |
29708 | in that context to be accessed. | |
29709 | ||
29710 | This packet is not probed by default; the remote stub must request it, | |
29711 | by supplying an appropriate @samp{qSupported} response (@pxref{qSupported}). | |
29712 | @end table | |
0876f84a DJ |
29713 | |
29714 | Reply: | |
29715 | @table @samp | |
29716 | @item @var{nn} | |
29717 | @var{nn} (hex encoded) is the number of bytes written. | |
29718 | This may be fewer bytes than supplied in the request. | |
29719 | ||
29720 | @item E00 | |
29721 | The request was malformed, or @var{annex} was invalid. | |
29722 | ||
29723 | @item E @var{nn} | |
29724 | The offset was invalid, or there was an error encountered writing the data. | |
29725 | @var{nn} is a hex-encoded @code{errno} value. | |
29726 | ||
29727 | @item | |
29728 | An empty reply indicates the @var{object} string was not | |
29729 | recognized by the stub, or that the object does not support writing. | |
29730 | @end table | |
29731 | ||
29732 | @item qXfer:@var{object}:@var{operation}:@dots{} | |
29733 | Requests of this form may be added in the future. When a stub does | |
29734 | not recognize the @var{object} keyword, or its support for | |
29735 | @var{object} does not recognize the @var{operation} keyword, the stub | |
29736 | must respond with an empty packet. | |
29737 | ||
0b16c5cf PA |
29738 | @item qAttached:@var{pid} |
29739 | @cindex query attached, remote request | |
29740 | @cindex @samp{qAttached} packet | |
29741 | Return an indication of whether the remote server attached to an | |
29742 | existing process or created a new process. When the multiprocess | |
29743 | protocol extensions are supported (@pxref{multiprocess extensions}), | |
29744 | @var{pid} is an integer in hexadecimal format identifying the target | |
29745 | process. Otherwise, @value{GDBN} will omit the @var{pid} field and | |
29746 | the query packet will be simplified as @samp{qAttached}. | |
29747 | ||
29748 | This query is used, for example, to know whether the remote process | |
29749 | should be detached or killed when a @value{GDBN} session is ended with | |
29750 | the @code{quit} command. | |
29751 | ||
29752 | Reply: | |
29753 | @table @samp | |
29754 | @item 1 | |
29755 | The remote server attached to an existing process. | |
29756 | @item 0 | |
29757 | The remote server created a new process. | |
29758 | @item E @var{NN} | |
29759 | A badly formed request or an error was encountered. | |
29760 | @end table | |
29761 | ||
ee2d5c50 AC |
29762 | @end table |
29763 | ||
29764 | @node Register Packet Format | |
29765 | @section Register Packet Format | |
eb12ee30 | 29766 | |
b8ff78ce | 29767 | The following @code{g}/@code{G} packets have previously been defined. |
ee2d5c50 AC |
29768 | In the below, some thirty-two bit registers are transferred as |
29769 | sixty-four bits. Those registers should be zero/sign extended (which?) | |
599b237a BW |
29770 | to fill the space allocated. Register bytes are transferred in target |
29771 | byte order. The two nibbles within a register byte are transferred | |
ee2d5c50 | 29772 | most-significant - least-significant. |
eb12ee30 | 29773 | |
ee2d5c50 | 29774 | @table @r |
eb12ee30 | 29775 | |
8e04817f | 29776 | @item MIPS32 |
ee2d5c50 | 29777 | |
599b237a | 29778 | All registers are transferred as thirty-two bit quantities in the order: |
8e04817f AC |
29779 | 32 general-purpose; sr; lo; hi; bad; cause; pc; 32 floating-point |
29780 | registers; fsr; fir; fp. | |
eb12ee30 | 29781 | |
8e04817f | 29782 | @item MIPS64 |
ee2d5c50 | 29783 | |
599b237a | 29784 | All registers are transferred as sixty-four bit quantities (including |
8e04817f AC |
29785 | thirty-two bit registers such as @code{sr}). The ordering is the same |
29786 | as @code{MIPS32}. | |
eb12ee30 | 29787 | |
ee2d5c50 AC |
29788 | @end table |
29789 | ||
9d29849a JB |
29790 | @node Tracepoint Packets |
29791 | @section Tracepoint Packets | |
29792 | @cindex tracepoint packets | |
29793 | @cindex packets, tracepoint | |
29794 | ||
29795 | Here we describe the packets @value{GDBN} uses to implement | |
29796 | tracepoints (@pxref{Tracepoints}). | |
29797 | ||
29798 | @table @samp | |
29799 | ||
782b2b07 | 29800 | @item QTDP:@var{n}:@var{addr}:@var{ena}:@var{step}:@var{pass}[:X@var{len},@var{bytes}]@r{[}-@r{]} |
9d29849a JB |
29801 | Create a new tracepoint, number @var{n}, at @var{addr}. If @var{ena} |
29802 | is @samp{E}, then the tracepoint is enabled; if it is @samp{D}, then | |
29803 | the tracepoint is disabled. @var{step} is the tracepoint's step | |
782b2b07 SS |
29804 | count, and @var{pass} is its pass count. If an @samp{X} is present, |
29805 | it introduces a tracepoint condition, which consists of a hexadecimal | |
29806 | length, followed by a comma and hex-encoded bytes, in a manner similar | |
29807 | to action encodings as described below. If the trailing @samp{-} is | |
9d29849a JB |
29808 | present, further @samp{QTDP} packets will follow to specify this |
29809 | tracepoint's actions. | |
29810 | ||
29811 | Replies: | |
29812 | @table @samp | |
29813 | @item OK | |
29814 | The packet was understood and carried out. | |
29815 | @item | |
29816 | The packet was not recognized. | |
29817 | @end table | |
29818 | ||
29819 | @item QTDP:-@var{n}:@var{addr}:@r{[}S@r{]}@var{action}@dots{}@r{[}-@r{]} | |
29820 | Define actions to be taken when a tracepoint is hit. @var{n} and | |
29821 | @var{addr} must be the same as in the initial @samp{QTDP} packet for | |
29822 | this tracepoint. This packet may only be sent immediately after | |
29823 | another @samp{QTDP} packet that ended with a @samp{-}. If the | |
29824 | trailing @samp{-} is present, further @samp{QTDP} packets will follow, | |
29825 | specifying more actions for this tracepoint. | |
29826 | ||
29827 | In the series of action packets for a given tracepoint, at most one | |
29828 | can have an @samp{S} before its first @var{action}. If such a packet | |
29829 | is sent, it and the following packets define ``while-stepping'' | |
29830 | actions. Any prior packets define ordinary actions --- that is, those | |
29831 | taken when the tracepoint is first hit. If no action packet has an | |
29832 | @samp{S}, then all the packets in the series specify ordinary | |
29833 | tracepoint actions. | |
29834 | ||
29835 | The @samp{@var{action}@dots{}} portion of the packet is a series of | |
29836 | actions, concatenated without separators. Each action has one of the | |
29837 | following forms: | |
29838 | ||
29839 | @table @samp | |
29840 | ||
29841 | @item R @var{mask} | |
29842 | Collect the registers whose bits are set in @var{mask}. @var{mask} is | |
599b237a | 29843 | a hexadecimal number whose @var{i}'th bit is set if register number |
9d29849a JB |
29844 | @var{i} should be collected. (The least significant bit is numbered |
29845 | zero.) Note that @var{mask} may be any number of digits long; it may | |
29846 | not fit in a 32-bit word. | |
29847 | ||
29848 | @item M @var{basereg},@var{offset},@var{len} | |
29849 | Collect @var{len} bytes of memory starting at the address in register | |
29850 | number @var{basereg}, plus @var{offset}. If @var{basereg} is | |
29851 | @samp{-1}, then the range has a fixed address: @var{offset} is the | |
29852 | address of the lowest byte to collect. The @var{basereg}, | |
599b237a | 29853 | @var{offset}, and @var{len} parameters are all unsigned hexadecimal |
9d29849a JB |
29854 | values (the @samp{-1} value for @var{basereg} is a special case). |
29855 | ||
29856 | @item X @var{len},@var{expr} | |
29857 | Evaluate @var{expr}, whose length is @var{len}, and collect memory as | |
29858 | it directs. @var{expr} is an agent expression, as described in | |
29859 | @ref{Agent Expressions}. Each byte of the expression is encoded as a | |
29860 | two-digit hex number in the packet; @var{len} is the number of bytes | |
29861 | in the expression (and thus one-half the number of hex digits in the | |
29862 | packet). | |
29863 | ||
29864 | @end table | |
29865 | ||
29866 | Any number of actions may be packed together in a single @samp{QTDP} | |
29867 | packet, as long as the packet does not exceed the maximum packet | |
c1947b85 JB |
29868 | length (400 bytes, for many stubs). There may be only one @samp{R} |
29869 | action per tracepoint, and it must precede any @samp{M} or @samp{X} | |
29870 | actions. Any registers referred to by @samp{M} and @samp{X} actions | |
29871 | must be collected by a preceding @samp{R} action. (The | |
29872 | ``while-stepping'' actions are treated as if they were attached to a | |
29873 | separate tracepoint, as far as these restrictions are concerned.) | |
9d29849a JB |
29874 | |
29875 | Replies: | |
29876 | @table @samp | |
29877 | @item OK | |
29878 | The packet was understood and carried out. | |
29879 | @item | |
29880 | The packet was not recognized. | |
29881 | @end table | |
29882 | ||
29883 | @item QTFrame:@var{n} | |
29884 | Select the @var{n}'th tracepoint frame from the buffer, and use the | |
29885 | register and memory contents recorded there to answer subsequent | |
29886 | request packets from @value{GDBN}. | |
29887 | ||
29888 | A successful reply from the stub indicates that the stub has found the | |
29889 | requested frame. The response is a series of parts, concatenated | |
29890 | without separators, describing the frame we selected. Each part has | |
29891 | one of the following forms: | |
29892 | ||
29893 | @table @samp | |
29894 | @item F @var{f} | |
29895 | The selected frame is number @var{n} in the trace frame buffer; | |
599b237a | 29896 | @var{f} is a hexadecimal number. If @var{f} is @samp{-1}, then there |
9d29849a JB |
29897 | was no frame matching the criteria in the request packet. |
29898 | ||
29899 | @item T @var{t} | |
29900 | The selected trace frame records a hit of tracepoint number @var{t}; | |
599b237a | 29901 | @var{t} is a hexadecimal number. |
9d29849a JB |
29902 | |
29903 | @end table | |
29904 | ||
29905 | @item QTFrame:pc:@var{addr} | |
29906 | Like @samp{QTFrame:@var{n}}, but select the first tracepoint frame after the | |
29907 | currently selected frame whose PC is @var{addr}; | |
599b237a | 29908 | @var{addr} is a hexadecimal number. |
9d29849a JB |
29909 | |
29910 | @item QTFrame:tdp:@var{t} | |
29911 | Like @samp{QTFrame:@var{n}}, but select the first tracepoint frame after the | |
29912 | currently selected frame that is a hit of tracepoint @var{t}; @var{t} | |
599b237a | 29913 | is a hexadecimal number. |
9d29849a JB |
29914 | |
29915 | @item QTFrame:range:@var{start}:@var{end} | |
29916 | Like @samp{QTFrame:@var{n}}, but select the first tracepoint frame after the | |
29917 | currently selected frame whose PC is between @var{start} (inclusive) | |
599b237a | 29918 | and @var{end} (exclusive); @var{start} and @var{end} are hexadecimal |
9d29849a JB |
29919 | numbers. |
29920 | ||
29921 | @item QTFrame:outside:@var{start}:@var{end} | |
29922 | Like @samp{QTFrame:range:@var{start}:@var{end}}, but select the first | |
29923 | frame @emph{outside} the given range of addresses. | |
29924 | ||
29925 | @item QTStart | |
29926 | Begin the tracepoint experiment. Begin collecting data from tracepoint | |
29927 | hits in the trace frame buffer. | |
29928 | ||
29929 | @item QTStop | |
29930 | End the tracepoint experiment. Stop collecting trace frames. | |
29931 | ||
29932 | @item QTinit | |
29933 | Clear the table of tracepoints, and empty the trace frame buffer. | |
29934 | ||
29935 | @item QTro:@var{start1},@var{end1}:@var{start2},@var{end2}:@dots{} | |
29936 | Establish the given ranges of memory as ``transparent''. The stub | |
29937 | will answer requests for these ranges from memory's current contents, | |
29938 | if they were not collected as part of the tracepoint hit. | |
29939 | ||
29940 | @value{GDBN} uses this to mark read-only regions of memory, like those | |
29941 | containing program code. Since these areas never change, they should | |
29942 | still have the same contents they did when the tracepoint was hit, so | |
29943 | there's no reason for the stub to refuse to provide their contents. | |
29944 | ||
29945 | @item qTStatus | |
29946 | Ask the stub if there is a trace experiment running right now. | |
29947 | ||
29948 | Replies: | |
29949 | @table @samp | |
29950 | @item T0 | |
29951 | There is no trace experiment running. | |
29952 | @item T1 | |
29953 | There is a trace experiment running. | |
29954 | @end table | |
29955 | ||
29956 | @end table | |
29957 | ||
29958 | ||
a6b151f1 DJ |
29959 | @node Host I/O Packets |
29960 | @section Host I/O Packets | |
29961 | @cindex Host I/O, remote protocol | |
29962 | @cindex file transfer, remote protocol | |
29963 | ||
29964 | The @dfn{Host I/O} packets allow @value{GDBN} to perform I/O | |
29965 | operations on the far side of a remote link. For example, Host I/O is | |
29966 | used to upload and download files to a remote target with its own | |
29967 | filesystem. Host I/O uses the same constant values and data structure | |
29968 | layout as the target-initiated File-I/O protocol. However, the | |
29969 | Host I/O packets are structured differently. The target-initiated | |
29970 | protocol relies on target memory to store parameters and buffers. | |
29971 | Host I/O requests are initiated by @value{GDBN}, and the | |
29972 | target's memory is not involved. @xref{File-I/O Remote Protocol | |
29973 | Extension}, for more details on the target-initiated protocol. | |
29974 | ||
29975 | The Host I/O request packets all encode a single operation along with | |
29976 | its arguments. They have this format: | |
29977 | ||
29978 | @table @samp | |
29979 | ||
29980 | @item vFile:@var{operation}: @var{parameter}@dots{} | |
29981 | @var{operation} is the name of the particular request; the target | |
29982 | should compare the entire packet name up to the second colon when checking | |
29983 | for a supported operation. The format of @var{parameter} depends on | |
29984 | the operation. Numbers are always passed in hexadecimal. Negative | |
29985 | numbers have an explicit minus sign (i.e.@: two's complement is not | |
29986 | used). Strings (e.g.@: filenames) are encoded as a series of | |
29987 | hexadecimal bytes. The last argument to a system call may be a | |
29988 | buffer of escaped binary data (@pxref{Binary Data}). | |
29989 | ||
29990 | @end table | |
29991 | ||
29992 | The valid responses to Host I/O packets are: | |
29993 | ||
29994 | @table @samp | |
29995 | ||
29996 | @item F @var{result} [, @var{errno}] [; @var{attachment}] | |
29997 | @var{result} is the integer value returned by this operation, usually | |
29998 | non-negative for success and -1 for errors. If an error has occured, | |
29999 | @var{errno} will be included in the result. @var{errno} will have a | |
30000 | value defined by the File-I/O protocol (@pxref{Errno Values}). For | |
30001 | operations which return data, @var{attachment} supplies the data as a | |
30002 | binary buffer. Binary buffers in response packets are escaped in the | |
30003 | normal way (@pxref{Binary Data}). See the individual packet | |
30004 | documentation for the interpretation of @var{result} and | |
30005 | @var{attachment}. | |
30006 | ||
30007 | @item | |
30008 | An empty response indicates that this operation is not recognized. | |
30009 | ||
30010 | @end table | |
30011 | ||
30012 | These are the supported Host I/O operations: | |
30013 | ||
30014 | @table @samp | |
30015 | @item vFile:open: @var{pathname}, @var{flags}, @var{mode} | |
30016 | Open a file at @var{pathname} and return a file descriptor for it, or | |
30017 | return -1 if an error occurs. @var{pathname} is a string, | |
30018 | @var{flags} is an integer indicating a mask of open flags | |
30019 | (@pxref{Open Flags}), and @var{mode} is an integer indicating a mask | |
30020 | of mode bits to use if the file is created (@pxref{mode_t Values}). | |
c1c25a1a | 30021 | @xref{open}, for details of the open flags and mode values. |
a6b151f1 DJ |
30022 | |
30023 | @item vFile:close: @var{fd} | |
30024 | Close the open file corresponding to @var{fd} and return 0, or | |
30025 | -1 if an error occurs. | |
30026 | ||
30027 | @item vFile:pread: @var{fd}, @var{count}, @var{offset} | |
30028 | Read data from the open file corresponding to @var{fd}. Up to | |
30029 | @var{count} bytes will be read from the file, starting at @var{offset} | |
30030 | relative to the start of the file. The target may read fewer bytes; | |
30031 | common reasons include packet size limits and an end-of-file | |
30032 | condition. The number of bytes read is returned. Zero should only be | |
30033 | returned for a successful read at the end of the file, or if | |
30034 | @var{count} was zero. | |
30035 | ||
30036 | The data read should be returned as a binary attachment on success. | |
30037 | If zero bytes were read, the response should include an empty binary | |
30038 | attachment (i.e.@: a trailing semicolon). The return value is the | |
30039 | number of target bytes read; the binary attachment may be longer if | |
30040 | some characters were escaped. | |
30041 | ||
30042 | @item vFile:pwrite: @var{fd}, @var{offset}, @var{data} | |
30043 | Write @var{data} (a binary buffer) to the open file corresponding | |
30044 | to @var{fd}. Start the write at @var{offset} from the start of the | |
30045 | file. Unlike many @code{write} system calls, there is no | |
30046 | separate @var{count} argument; the length of @var{data} in the | |
30047 | packet is used. @samp{vFile:write} returns the number of bytes written, | |
30048 | which may be shorter than the length of @var{data}, or -1 if an | |
30049 | error occurred. | |
30050 | ||
30051 | @item vFile:unlink: @var{pathname} | |
30052 | Delete the file at @var{pathname} on the target. Return 0, | |
30053 | or -1 if an error occurs. @var{pathname} is a string. | |
30054 | ||
30055 | @end table | |
30056 | ||
9a6253be KB |
30057 | @node Interrupts |
30058 | @section Interrupts | |
30059 | @cindex interrupts (remote protocol) | |
30060 | ||
30061 | When a program on the remote target is running, @value{GDBN} may | |
30062 | attempt to interrupt it by sending a @samp{Ctrl-C} or a @code{BREAK}, | |
30063 | control of which is specified via @value{GDBN}'s @samp{remotebreak} | |
30064 | setting (@pxref{set remotebreak}). | |
30065 | ||
30066 | The precise meaning of @code{BREAK} is defined by the transport | |
8775bb90 MS |
30067 | mechanism and may, in fact, be undefined. @value{GDBN} does not |
30068 | currently define a @code{BREAK} mechanism for any of the network | |
30069 | interfaces except for TCP, in which case @value{GDBN} sends the | |
30070 | @code{telnet} BREAK sequence. | |
9a6253be KB |
30071 | |
30072 | @samp{Ctrl-C}, on the other hand, is defined and implemented for all | |
30073 | transport mechanisms. It is represented by sending the single byte | |
30074 | @code{0x03} without any of the usual packet overhead described in | |
30075 | the Overview section (@pxref{Overview}). When a @code{0x03} byte is | |
30076 | transmitted as part of a packet, it is considered to be packet data | |
30077 | and does @emph{not} represent an interrupt. E.g., an @samp{X} packet | |
0876f84a | 30078 | (@pxref{X packet}), used for binary downloads, may include an unescaped |
9a6253be KB |
30079 | @code{0x03} as part of its packet. |
30080 | ||
30081 | Stubs are not required to recognize these interrupt mechanisms and the | |
30082 | precise meaning associated with receipt of the interrupt is | |
8b23ecc4 SL |
30083 | implementation defined. If the target supports debugging of multiple |
30084 | threads and/or processes, it should attempt to interrupt all | |
30085 | currently-executing threads and processes. | |
30086 | If the stub is successful at interrupting the | |
30087 | running program, it should send one of the stop | |
30088 | reply packets (@pxref{Stop Reply Packets}) to @value{GDBN} as a result | |
30089 | of successfully stopping the program in all-stop mode, and a stop reply | |
30090 | for each stopped thread in non-stop mode. | |
30091 | Interrupts received while the | |
30092 | program is stopped are discarded. | |
30093 | ||
30094 | @node Notification Packets | |
30095 | @section Notification Packets | |
30096 | @cindex notification packets | |
30097 | @cindex packets, notification | |
30098 | ||
30099 | The @value{GDBN} remote serial protocol includes @dfn{notifications}, | |
30100 | packets that require no acknowledgment. Both the GDB and the stub | |
30101 | may send notifications (although the only notifications defined at | |
30102 | present are sent by the stub). Notifications carry information | |
30103 | without incurring the round-trip latency of an acknowledgment, and so | |
30104 | are useful for low-impact communications where occasional packet loss | |
30105 | is not a problem. | |
30106 | ||
30107 | A notification packet has the form @samp{% @var{data} # | |
30108 | @var{checksum}}, where @var{data} is the content of the notification, | |
30109 | and @var{checksum} is a checksum of @var{data}, computed and formatted | |
30110 | as for ordinary @value{GDBN} packets. A notification's @var{data} | |
30111 | never contains @samp{$}, @samp{%} or @samp{#} characters. Upon | |
30112 | receiving a notification, the recipient sends no @samp{+} or @samp{-} | |
30113 | to acknowledge the notification's receipt or to report its corruption. | |
30114 | ||
30115 | Every notification's @var{data} begins with a name, which contains no | |
30116 | colon characters, followed by a colon character. | |
30117 | ||
30118 | Recipients should silently ignore corrupted notifications and | |
30119 | notifications they do not understand. Recipients should restart | |
30120 | timeout periods on receipt of a well-formed notification, whether or | |
30121 | not they understand it. | |
30122 | ||
30123 | Senders should only send the notifications described here when this | |
30124 | protocol description specifies that they are permitted. In the | |
30125 | future, we may extend the protocol to permit existing notifications in | |
30126 | new contexts; this rule helps older senders avoid confusing newer | |
30127 | recipients. | |
30128 | ||
30129 | (Older versions of @value{GDBN} ignore bytes received until they see | |
30130 | the @samp{$} byte that begins an ordinary packet, so new stubs may | |
30131 | transmit notifications without fear of confusing older clients. There | |
30132 | are no notifications defined for @value{GDBN} to send at the moment, but we | |
30133 | assume that most older stubs would ignore them, as well.) | |
30134 | ||
30135 | The following notification packets from the stub to @value{GDBN} are | |
30136 | defined: | |
30137 | ||
30138 | @table @samp | |
30139 | @item Stop: @var{reply} | |
30140 | Report an asynchronous stop event in non-stop mode. | |
30141 | The @var{reply} has the form of a stop reply, as | |
30142 | described in @ref{Stop Reply Packets}. Refer to @ref{Remote Non-Stop}, | |
30143 | for information on how these notifications are acknowledged by | |
30144 | @value{GDBN}. | |
30145 | @end table | |
30146 | ||
30147 | @node Remote Non-Stop | |
30148 | @section Remote Protocol Support for Non-Stop Mode | |
30149 | ||
30150 | @value{GDBN}'s remote protocol supports non-stop debugging of | |
30151 | multi-threaded programs, as described in @ref{Non-Stop Mode}. If the stub | |
30152 | supports non-stop mode, it should report that to @value{GDBN} by including | |
30153 | @samp{QNonStop+} in its @samp{qSupported} response (@pxref{qSupported}). | |
30154 | ||
30155 | @value{GDBN} typically sends a @samp{QNonStop} packet only when | |
30156 | establishing a new connection with the stub. Entering non-stop mode | |
30157 | does not alter the state of any currently-running threads, but targets | |
30158 | must stop all threads in any already-attached processes when entering | |
30159 | all-stop mode. @value{GDBN} uses the @samp{?} packet as necessary to | |
30160 | probe the target state after a mode change. | |
30161 | ||
30162 | In non-stop mode, when an attached process encounters an event that | |
30163 | would otherwise be reported with a stop reply, it uses the | |
30164 | asynchronous notification mechanism (@pxref{Notification Packets}) to | |
30165 | inform @value{GDBN}. In contrast to all-stop mode, where all threads | |
30166 | in all processes are stopped when a stop reply is sent, in non-stop | |
30167 | mode only the thread reporting the stop event is stopped. That is, | |
30168 | when reporting a @samp{S} or @samp{T} response to indicate completion | |
30169 | of a step operation, hitting a breakpoint, or a fault, only the | |
30170 | affected thread is stopped; any other still-running threads continue | |
30171 | to run. When reporting a @samp{W} or @samp{X} response, all running | |
30172 | threads belonging to other attached processes continue to run. | |
30173 | ||
30174 | Only one stop reply notification at a time may be pending; if | |
30175 | additional stop events occur before @value{GDBN} has acknowledged the | |
30176 | previous notification, they must be queued by the stub for later | |
30177 | synchronous transmission in response to @samp{vStopped} packets from | |
30178 | @value{GDBN}. Because the notification mechanism is unreliable, | |
30179 | the stub is permitted to resend a stop reply notification | |
30180 | if it believes @value{GDBN} may not have received it. @value{GDBN} | |
30181 | ignores additional stop reply notifications received before it has | |
30182 | finished processing a previous notification and the stub has completed | |
30183 | sending any queued stop events. | |
30184 | ||
30185 | Otherwise, @value{GDBN} must be prepared to receive a stop reply | |
30186 | notification at any time. Specifically, they may appear when | |
30187 | @value{GDBN} is not otherwise reading input from the stub, or when | |
30188 | @value{GDBN} is expecting to read a normal synchronous response or a | |
30189 | @samp{+}/@samp{-} acknowledgment to a packet it has sent. | |
30190 | Notification packets are distinct from any other communication from | |
30191 | the stub so there is no ambiguity. | |
30192 | ||
30193 | After receiving a stop reply notification, @value{GDBN} shall | |
30194 | acknowledge it by sending a @samp{vStopped} packet (@pxref{vStopped packet}) | |
30195 | as a regular, synchronous request to the stub. Such acknowledgment | |
30196 | is not required to happen immediately, as @value{GDBN} is permitted to | |
30197 | send other, unrelated packets to the stub first, which the stub should | |
30198 | process normally. | |
30199 | ||
30200 | Upon receiving a @samp{vStopped} packet, if the stub has other queued | |
30201 | stop events to report to @value{GDBN}, it shall respond by sending a | |
30202 | normal stop reply response. @value{GDBN} shall then send another | |
30203 | @samp{vStopped} packet to solicit further responses; again, it is | |
30204 | permitted to send other, unrelated packets as well which the stub | |
30205 | should process normally. | |
30206 | ||
30207 | If the stub receives a @samp{vStopped} packet and there are no | |
30208 | additional stop events to report, the stub shall return an @samp{OK} | |
30209 | response. At this point, if further stop events occur, the stub shall | |
30210 | send a new stop reply notification, @value{GDBN} shall accept the | |
30211 | notification, and the process shall be repeated. | |
30212 | ||
30213 | In non-stop mode, the target shall respond to the @samp{?} packet as | |
30214 | follows. First, any incomplete stop reply notification/@samp{vStopped} | |
30215 | sequence in progress is abandoned. The target must begin a new | |
30216 | sequence reporting stop events for all stopped threads, whether or not | |
30217 | it has previously reported those events to @value{GDBN}. The first | |
30218 | stop reply is sent as a synchronous reply to the @samp{?} packet, and | |
30219 | subsequent stop replies are sent as responses to @samp{vStopped} packets | |
30220 | using the mechanism described above. The target must not send | |
30221 | asynchronous stop reply notifications until the sequence is complete. | |
30222 | If all threads are running when the target receives the @samp{?} packet, | |
30223 | or if the target is not attached to any process, it shall respond | |
30224 | @samp{OK}. | |
9a6253be | 30225 | |
a6f3e723 SL |
30226 | @node Packet Acknowledgment |
30227 | @section Packet Acknowledgment | |
30228 | ||
30229 | @cindex acknowledgment, for @value{GDBN} remote | |
30230 | @cindex packet acknowledgment, for @value{GDBN} remote | |
30231 | By default, when either the host or the target machine receives a packet, | |
30232 | the first response expected is an acknowledgment: either @samp{+} (to indicate | |
30233 | the package was received correctly) or @samp{-} (to request retransmission). | |
30234 | This mechanism allows the @value{GDBN} remote protocol to operate over | |
30235 | unreliable transport mechanisms, such as a serial line. | |
30236 | ||
30237 | In cases where the transport mechanism is itself reliable (such as a pipe or | |
30238 | TCP connection), the @samp{+}/@samp{-} acknowledgments are redundant. | |
30239 | It may be desirable to disable them in that case to reduce communication | |
30240 | overhead, or for other reasons. This can be accomplished by means of the | |
30241 | @samp{QStartNoAckMode} packet; @pxref{QStartNoAckMode}. | |
30242 | ||
30243 | When in no-acknowledgment mode, neither the stub nor @value{GDBN} shall send or | |
30244 | expect @samp{+}/@samp{-} protocol acknowledgments. The packet | |
30245 | and response format still includes the normal checksum, as described in | |
30246 | @ref{Overview}, but the checksum may be ignored by the receiver. | |
30247 | ||
30248 | If the stub supports @samp{QStartNoAckMode} and prefers to operate in | |
30249 | no-acknowledgment mode, it should report that to @value{GDBN} | |
30250 | by including @samp{QStartNoAckMode+} in its response to @samp{qSupported}; | |
30251 | @pxref{qSupported}. | |
30252 | If @value{GDBN} also supports @samp{QStartNoAckMode} and it has not been | |
30253 | disabled via the @code{set remote noack-packet off} command | |
30254 | (@pxref{Remote Configuration}), | |
30255 | @value{GDBN} may then send a @samp{QStartNoAckMode} packet to the stub. | |
30256 | Only then may the stub actually turn off packet acknowledgments. | |
30257 | @value{GDBN} sends a final @samp{+} acknowledgment of the stub's @samp{OK} | |
30258 | response, which can be safely ignored by the stub. | |
30259 | ||
30260 | Note that @code{set remote noack-packet} command only affects negotiation | |
30261 | between @value{GDBN} and the stub when subsequent connections are made; | |
30262 | it does not affect the protocol acknowledgment state for any current | |
30263 | connection. | |
30264 | Since @samp{+}/@samp{-} acknowledgments are enabled by default when a | |
30265 | new connection is established, | |
30266 | there is also no protocol request to re-enable the acknowledgments | |
30267 | for the current connection, once disabled. | |
30268 | ||
ee2d5c50 AC |
30269 | @node Examples |
30270 | @section Examples | |
eb12ee30 | 30271 | |
8e04817f AC |
30272 | Example sequence of a target being re-started. Notice how the restart |
30273 | does not get any direct output: | |
eb12ee30 | 30274 | |
474c8240 | 30275 | @smallexample |
d2c6833e AC |
30276 | -> @code{R00} |
30277 | <- @code{+} | |
8e04817f | 30278 | @emph{target restarts} |
d2c6833e | 30279 | -> @code{?} |
8e04817f | 30280 | <- @code{+} |
d2c6833e AC |
30281 | <- @code{T001:1234123412341234} |
30282 | -> @code{+} | |
474c8240 | 30283 | @end smallexample |
eb12ee30 | 30284 | |
8e04817f | 30285 | Example sequence of a target being stepped by a single instruction: |
eb12ee30 | 30286 | |
474c8240 | 30287 | @smallexample |
d2c6833e | 30288 | -> @code{G1445@dots{}} |
8e04817f | 30289 | <- @code{+} |
d2c6833e AC |
30290 | -> @code{s} |
30291 | <- @code{+} | |
30292 | @emph{time passes} | |
30293 | <- @code{T001:1234123412341234} | |
8e04817f | 30294 | -> @code{+} |
d2c6833e | 30295 | -> @code{g} |
8e04817f | 30296 | <- @code{+} |
d2c6833e AC |
30297 | <- @code{1455@dots{}} |
30298 | -> @code{+} | |
474c8240 | 30299 | @end smallexample |
eb12ee30 | 30300 | |
79a6e687 BW |
30301 | @node File-I/O Remote Protocol Extension |
30302 | @section File-I/O Remote Protocol Extension | |
0ce1b118 CV |
30303 | @cindex File-I/O remote protocol extension |
30304 | ||
30305 | @menu | |
30306 | * File-I/O Overview:: | |
79a6e687 BW |
30307 | * Protocol Basics:: |
30308 | * The F Request Packet:: | |
30309 | * The F Reply Packet:: | |
30310 | * The Ctrl-C Message:: | |
0ce1b118 | 30311 | * Console I/O:: |
79a6e687 | 30312 | * List of Supported Calls:: |
db2e3e2e | 30313 | * Protocol-specific Representation of Datatypes:: |
0ce1b118 CV |
30314 | * Constants:: |
30315 | * File-I/O Examples:: | |
30316 | @end menu | |
30317 | ||
30318 | @node File-I/O Overview | |
30319 | @subsection File-I/O Overview | |
30320 | @cindex file-i/o overview | |
30321 | ||
9c16f35a | 30322 | The @dfn{File I/O remote protocol extension} (short: File-I/O) allows the |
fc320d37 | 30323 | target to use the host's file system and console I/O to perform various |
0ce1b118 | 30324 | system calls. System calls on the target system are translated into a |
fc320d37 SL |
30325 | remote protocol packet to the host system, which then performs the needed |
30326 | actions and returns a response packet to the target system. | |
0ce1b118 CV |
30327 | This simulates file system operations even on targets that lack file systems. |
30328 | ||
fc320d37 SL |
30329 | The protocol is defined to be independent of both the host and target systems. |
30330 | It uses its own internal representation of datatypes and values. Both | |
0ce1b118 | 30331 | @value{GDBN} and the target's @value{GDBN} stub are responsible for |
fc320d37 SL |
30332 | translating the system-dependent value representations into the internal |
30333 | protocol representations when data is transmitted. | |
0ce1b118 | 30334 | |
fc320d37 SL |
30335 | The communication is synchronous. A system call is possible only when |
30336 | @value{GDBN} is waiting for a response from the @samp{C}, @samp{c}, @samp{S} | |
30337 | or @samp{s} packets. While @value{GDBN} handles the request for a system call, | |
0ce1b118 | 30338 | the target is stopped to allow deterministic access to the target's |
fc320d37 SL |
30339 | memory. Therefore File-I/O is not interruptible by target signals. On |
30340 | the other hand, it is possible to interrupt File-I/O by a user interrupt | |
c8aa23ab | 30341 | (@samp{Ctrl-C}) within @value{GDBN}. |
0ce1b118 CV |
30342 | |
30343 | The target's request to perform a host system call does not finish | |
30344 | the latest @samp{C}, @samp{c}, @samp{S} or @samp{s} action. That means, | |
30345 | after finishing the system call, the target returns to continuing the | |
30346 | previous activity (continue, step). No additional continue or step | |
30347 | request from @value{GDBN} is required. | |
30348 | ||
30349 | @smallexample | |
f7dc1244 | 30350 | (@value{GDBP}) continue |
0ce1b118 CV |
30351 | <- target requests 'system call X' |
30352 | target is stopped, @value{GDBN} executes system call | |
3f94c067 BW |
30353 | -> @value{GDBN} returns result |
30354 | ... target continues, @value{GDBN} returns to wait for the target | |
0ce1b118 CV |
30355 | <- target hits breakpoint and sends a Txx packet |
30356 | @end smallexample | |
30357 | ||
fc320d37 SL |
30358 | The protocol only supports I/O on the console and to regular files on |
30359 | the host file system. Character or block special devices, pipes, | |
30360 | named pipes, sockets or any other communication method on the host | |
0ce1b118 CV |
30361 | system are not supported by this protocol. |
30362 | ||
8b23ecc4 SL |
30363 | File I/O is not supported in non-stop mode. |
30364 | ||
79a6e687 BW |
30365 | @node Protocol Basics |
30366 | @subsection Protocol Basics | |
0ce1b118 CV |
30367 | @cindex protocol basics, file-i/o |
30368 | ||
fc320d37 SL |
30369 | The File-I/O protocol uses the @code{F} packet as the request as well |
30370 | as reply packet. Since a File-I/O system call can only occur when | |
30371 | @value{GDBN} is waiting for a response from the continuing or stepping target, | |
30372 | the File-I/O request is a reply that @value{GDBN} has to expect as a result | |
30373 | of a previous @samp{C}, @samp{c}, @samp{S} or @samp{s} packet. | |
0ce1b118 CV |
30374 | This @code{F} packet contains all information needed to allow @value{GDBN} |
30375 | to call the appropriate host system call: | |
30376 | ||
30377 | @itemize @bullet | |
b383017d | 30378 | @item |
0ce1b118 CV |
30379 | A unique identifier for the requested system call. |
30380 | ||
30381 | @item | |
30382 | All parameters to the system call. Pointers are given as addresses | |
30383 | in the target memory address space. Pointers to strings are given as | |
b383017d | 30384 | pointer/length pair. Numerical values are given as they are. |
db2e3e2e | 30385 | Numerical control flags are given in a protocol-specific representation. |
0ce1b118 CV |
30386 | |
30387 | @end itemize | |
30388 | ||
fc320d37 | 30389 | At this point, @value{GDBN} has to perform the following actions. |
0ce1b118 CV |
30390 | |
30391 | @itemize @bullet | |
b383017d | 30392 | @item |
fc320d37 SL |
30393 | If the parameters include pointer values to data needed as input to a |
30394 | system call, @value{GDBN} requests this data from the target with a | |
0ce1b118 CV |
30395 | standard @code{m} packet request. This additional communication has to be |
30396 | expected by the target implementation and is handled as any other @code{m} | |
30397 | packet. | |
30398 | ||
30399 | @item | |
30400 | @value{GDBN} translates all value from protocol representation to host | |
30401 | representation as needed. Datatypes are coerced into the host types. | |
30402 | ||
30403 | @item | |
fc320d37 | 30404 | @value{GDBN} calls the system call. |
0ce1b118 CV |
30405 | |
30406 | @item | |
30407 | It then coerces datatypes back to protocol representation. | |
30408 | ||
30409 | @item | |
fc320d37 SL |
30410 | If the system call is expected to return data in buffer space specified |
30411 | by pointer parameters to the call, the data is transmitted to the | |
0ce1b118 CV |
30412 | target using a @code{M} or @code{X} packet. This packet has to be expected |
30413 | by the target implementation and is handled as any other @code{M} or @code{X} | |
30414 | packet. | |
30415 | ||
30416 | @end itemize | |
30417 | ||
30418 | Eventually @value{GDBN} replies with another @code{F} packet which contains all | |
30419 | necessary information for the target to continue. This at least contains | |
30420 | ||
30421 | @itemize @bullet | |
30422 | @item | |
30423 | Return value. | |
30424 | ||
30425 | @item | |
30426 | @code{errno}, if has been changed by the system call. | |
30427 | ||
30428 | @item | |
30429 | ``Ctrl-C'' flag. | |
30430 | ||
30431 | @end itemize | |
30432 | ||
30433 | After having done the needed type and value coercion, the target continues | |
30434 | the latest continue or step action. | |
30435 | ||
79a6e687 BW |
30436 | @node The F Request Packet |
30437 | @subsection The @code{F} Request Packet | |
0ce1b118 CV |
30438 | @cindex file-i/o request packet |
30439 | @cindex @code{F} request packet | |
30440 | ||
30441 | The @code{F} request packet has the following format: | |
30442 | ||
30443 | @table @samp | |
fc320d37 | 30444 | @item F@var{call-id},@var{parameter@dots{}} |
0ce1b118 CV |
30445 | |
30446 | @var{call-id} is the identifier to indicate the host system call to be called. | |
30447 | This is just the name of the function. | |
30448 | ||
fc320d37 SL |
30449 | @var{parameter@dots{}} are the parameters to the system call. |
30450 | Parameters are hexadecimal integer values, either the actual values in case | |
30451 | of scalar datatypes, pointers to target buffer space in case of compound | |
30452 | datatypes and unspecified memory areas, or pointer/length pairs in case | |
30453 | of string parameters. These are appended to the @var{call-id} as a | |
30454 | comma-delimited list. All values are transmitted in ASCII | |
30455 | string representation, pointer/length pairs separated by a slash. | |
0ce1b118 | 30456 | |
b383017d | 30457 | @end table |
0ce1b118 | 30458 | |
fc320d37 | 30459 | |
0ce1b118 | 30460 | |
79a6e687 BW |
30461 | @node The F Reply Packet |
30462 | @subsection The @code{F} Reply Packet | |
0ce1b118 CV |
30463 | @cindex file-i/o reply packet |
30464 | @cindex @code{F} reply packet | |
30465 | ||
30466 | The @code{F} reply packet has the following format: | |
30467 | ||
30468 | @table @samp | |
30469 | ||
d3bdde98 | 30470 | @item F@var{retcode},@var{errno},@var{Ctrl-C flag};@var{call-specific attachment} |
0ce1b118 CV |
30471 | |
30472 | @var{retcode} is the return code of the system call as hexadecimal value. | |
30473 | ||
db2e3e2e BW |
30474 | @var{errno} is the @code{errno} set by the call, in protocol-specific |
30475 | representation. | |
0ce1b118 CV |
30476 | This parameter can be omitted if the call was successful. |
30477 | ||
fc320d37 SL |
30478 | @var{Ctrl-C flag} is only sent if the user requested a break. In this |
30479 | case, @var{errno} must be sent as well, even if the call was successful. | |
30480 | The @var{Ctrl-C flag} itself consists of the character @samp{C}: | |
0ce1b118 CV |
30481 | |
30482 | @smallexample | |
30483 | F0,0,C | |
30484 | @end smallexample | |
30485 | ||
30486 | @noindent | |
fc320d37 | 30487 | or, if the call was interrupted before the host call has been performed: |
0ce1b118 CV |
30488 | |
30489 | @smallexample | |
30490 | F-1,4,C | |
30491 | @end smallexample | |
30492 | ||
30493 | @noindent | |
db2e3e2e | 30494 | assuming 4 is the protocol-specific representation of @code{EINTR}. |
0ce1b118 CV |
30495 | |
30496 | @end table | |
30497 | ||
0ce1b118 | 30498 | |
79a6e687 BW |
30499 | @node The Ctrl-C Message |
30500 | @subsection The @samp{Ctrl-C} Message | |
0ce1b118 CV |
30501 | @cindex ctrl-c message, in file-i/o protocol |
30502 | ||
c8aa23ab | 30503 | If the @samp{Ctrl-C} flag is set in the @value{GDBN} |
79a6e687 | 30504 | reply packet (@pxref{The F Reply Packet}), |
fc320d37 | 30505 | the target should behave as if it had |
0ce1b118 | 30506 | gotten a break message. The meaning for the target is ``system call |
fc320d37 | 30507 | interrupted by @code{SIGINT}''. Consequentially, the target should actually stop |
0ce1b118 | 30508 | (as with a break message) and return to @value{GDBN} with a @code{T02} |
c8aa23ab | 30509 | packet. |
fc320d37 SL |
30510 | |
30511 | It's important for the target to know in which | |
30512 | state the system call was interrupted. There are two possible cases: | |
0ce1b118 CV |
30513 | |
30514 | @itemize @bullet | |
30515 | @item | |
30516 | The system call hasn't been performed on the host yet. | |
30517 | ||
30518 | @item | |
30519 | The system call on the host has been finished. | |
30520 | ||
30521 | @end itemize | |
30522 | ||
30523 | These two states can be distinguished by the target by the value of the | |
30524 | returned @code{errno}. If it's the protocol representation of @code{EINTR}, the system | |
30525 | call hasn't been performed. This is equivalent to the @code{EINTR} handling | |
30526 | on POSIX systems. In any other case, the target may presume that the | |
fc320d37 | 30527 | system call has been finished --- successfully or not --- and should behave |
0ce1b118 CV |
30528 | as if the break message arrived right after the system call. |
30529 | ||
fc320d37 | 30530 | @value{GDBN} must behave reliably. If the system call has not been called |
0ce1b118 CV |
30531 | yet, @value{GDBN} may send the @code{F} reply immediately, setting @code{EINTR} as |
30532 | @code{errno} in the packet. If the system call on the host has been finished | |
fc320d37 SL |
30533 | before the user requests a break, the full action must be finished by |
30534 | @value{GDBN}. This requires sending @code{M} or @code{X} packets as necessary. | |
30535 | The @code{F} packet may only be sent when either nothing has happened | |
0ce1b118 CV |
30536 | or the full action has been completed. |
30537 | ||
30538 | @node Console I/O | |
30539 | @subsection Console I/O | |
30540 | @cindex console i/o as part of file-i/o | |
30541 | ||
d3e8051b | 30542 | By default and if not explicitly closed by the target system, the file |
0ce1b118 CV |
30543 | descriptors 0, 1 and 2 are connected to the @value{GDBN} console. Output |
30544 | on the @value{GDBN} console is handled as any other file output operation | |
30545 | (@code{write(1, @dots{})} or @code{write(2, @dots{})}). Console input is handled | |
30546 | by @value{GDBN} so that after the target read request from file descriptor | |
30547 | 0 all following typing is buffered until either one of the following | |
30548 | conditions is met: | |
30549 | ||
30550 | @itemize @bullet | |
30551 | @item | |
c8aa23ab | 30552 | The user types @kbd{Ctrl-c}. The behaviour is as explained above, and the |
0ce1b118 CV |
30553 | @code{read} |
30554 | system call is treated as finished. | |
30555 | ||
30556 | @item | |
7f9087cb | 30557 | The user presses @key{RET}. This is treated as end of input with a trailing |
fc320d37 | 30558 | newline. |
0ce1b118 CV |
30559 | |
30560 | @item | |
c8aa23ab EZ |
30561 | The user types @kbd{Ctrl-d}. This is treated as end of input. No trailing |
30562 | character (neither newline nor @samp{Ctrl-D}) is appended to the input. | |
0ce1b118 CV |
30563 | |
30564 | @end itemize | |
30565 | ||
fc320d37 SL |
30566 | If the user has typed more characters than fit in the buffer given to |
30567 | the @code{read} call, the trailing characters are buffered in @value{GDBN} until | |
30568 | either another @code{read(0, @dots{})} is requested by the target, or debugging | |
30569 | is stopped at the user's request. | |
0ce1b118 | 30570 | |
0ce1b118 | 30571 | |
79a6e687 BW |
30572 | @node List of Supported Calls |
30573 | @subsection List of Supported Calls | |
0ce1b118 CV |
30574 | @cindex list of supported file-i/o calls |
30575 | ||
30576 | @menu | |
30577 | * open:: | |
30578 | * close:: | |
30579 | * read:: | |
30580 | * write:: | |
30581 | * lseek:: | |
30582 | * rename:: | |
30583 | * unlink:: | |
30584 | * stat/fstat:: | |
30585 | * gettimeofday:: | |
30586 | * isatty:: | |
30587 | * system:: | |
30588 | @end menu | |
30589 | ||
30590 | @node open | |
30591 | @unnumberedsubsubsec open | |
30592 | @cindex open, file-i/o system call | |
30593 | ||
fc320d37 SL |
30594 | @table @asis |
30595 | @item Synopsis: | |
0ce1b118 | 30596 | @smallexample |
0ce1b118 CV |
30597 | int open(const char *pathname, int flags); |
30598 | int open(const char *pathname, int flags, mode_t mode); | |
0ce1b118 CV |
30599 | @end smallexample |
30600 | ||
fc320d37 SL |
30601 | @item Request: |
30602 | @samp{Fopen,@var{pathptr}/@var{len},@var{flags},@var{mode}} | |
30603 | ||
0ce1b118 | 30604 | @noindent |
fc320d37 | 30605 | @var{flags} is the bitwise @code{OR} of the following values: |
0ce1b118 CV |
30606 | |
30607 | @table @code | |
b383017d | 30608 | @item O_CREAT |
0ce1b118 CV |
30609 | If the file does not exist it will be created. The host |
30610 | rules apply as far as file ownership and time stamps | |
30611 | are concerned. | |
30612 | ||
b383017d | 30613 | @item O_EXCL |
fc320d37 | 30614 | When used with @code{O_CREAT}, if the file already exists it is |
0ce1b118 CV |
30615 | an error and open() fails. |
30616 | ||
b383017d | 30617 | @item O_TRUNC |
0ce1b118 | 30618 | If the file already exists and the open mode allows |
fc320d37 SL |
30619 | writing (@code{O_RDWR} or @code{O_WRONLY} is given) it will be |
30620 | truncated to zero length. | |
0ce1b118 | 30621 | |
b383017d | 30622 | @item O_APPEND |
0ce1b118 CV |
30623 | The file is opened in append mode. |
30624 | ||
b383017d | 30625 | @item O_RDONLY |
0ce1b118 CV |
30626 | The file is opened for reading only. |
30627 | ||
b383017d | 30628 | @item O_WRONLY |
0ce1b118 CV |
30629 | The file is opened for writing only. |
30630 | ||
b383017d | 30631 | @item O_RDWR |
0ce1b118 | 30632 | The file is opened for reading and writing. |
fc320d37 | 30633 | @end table |
0ce1b118 CV |
30634 | |
30635 | @noindent | |
fc320d37 | 30636 | Other bits are silently ignored. |
0ce1b118 | 30637 | |
0ce1b118 CV |
30638 | |
30639 | @noindent | |
fc320d37 | 30640 | @var{mode} is the bitwise @code{OR} of the following values: |
0ce1b118 CV |
30641 | |
30642 | @table @code | |
b383017d | 30643 | @item S_IRUSR |
0ce1b118 CV |
30644 | User has read permission. |
30645 | ||
b383017d | 30646 | @item S_IWUSR |
0ce1b118 CV |
30647 | User has write permission. |
30648 | ||
b383017d | 30649 | @item S_IRGRP |
0ce1b118 CV |
30650 | Group has read permission. |
30651 | ||
b383017d | 30652 | @item S_IWGRP |
0ce1b118 CV |
30653 | Group has write permission. |
30654 | ||
b383017d | 30655 | @item S_IROTH |
0ce1b118 CV |
30656 | Others have read permission. |
30657 | ||
b383017d | 30658 | @item S_IWOTH |
0ce1b118 | 30659 | Others have write permission. |
fc320d37 | 30660 | @end table |
0ce1b118 CV |
30661 | |
30662 | @noindent | |
fc320d37 | 30663 | Other bits are silently ignored. |
0ce1b118 | 30664 | |
0ce1b118 | 30665 | |
fc320d37 SL |
30666 | @item Return value: |
30667 | @code{open} returns the new file descriptor or -1 if an error | |
30668 | occurred. | |
0ce1b118 | 30669 | |
fc320d37 | 30670 | @item Errors: |
0ce1b118 CV |
30671 | |
30672 | @table @code | |
b383017d | 30673 | @item EEXIST |
fc320d37 | 30674 | @var{pathname} already exists and @code{O_CREAT} and @code{O_EXCL} were used. |
0ce1b118 | 30675 | |
b383017d | 30676 | @item EISDIR |
fc320d37 | 30677 | @var{pathname} refers to a directory. |
0ce1b118 | 30678 | |
b383017d | 30679 | @item EACCES |
0ce1b118 CV |
30680 | The requested access is not allowed. |
30681 | ||
30682 | @item ENAMETOOLONG | |
fc320d37 | 30683 | @var{pathname} was too long. |
0ce1b118 | 30684 | |
b383017d | 30685 | @item ENOENT |
fc320d37 | 30686 | A directory component in @var{pathname} does not exist. |
0ce1b118 | 30687 | |
b383017d | 30688 | @item ENODEV |
fc320d37 | 30689 | @var{pathname} refers to a device, pipe, named pipe or socket. |
0ce1b118 | 30690 | |
b383017d | 30691 | @item EROFS |
fc320d37 | 30692 | @var{pathname} refers to a file on a read-only filesystem and |
0ce1b118 CV |
30693 | write access was requested. |
30694 | ||
b383017d | 30695 | @item EFAULT |
fc320d37 | 30696 | @var{pathname} is an invalid pointer value. |
0ce1b118 | 30697 | |
b383017d | 30698 | @item ENOSPC |
0ce1b118 CV |
30699 | No space on device to create the file. |
30700 | ||
b383017d | 30701 | @item EMFILE |
0ce1b118 CV |
30702 | The process already has the maximum number of files open. |
30703 | ||
b383017d | 30704 | @item ENFILE |
0ce1b118 CV |
30705 | The limit on the total number of files open on the system |
30706 | has been reached. | |
30707 | ||
b383017d | 30708 | @item EINTR |
0ce1b118 CV |
30709 | The call was interrupted by the user. |
30710 | @end table | |
30711 | ||
fc320d37 SL |
30712 | @end table |
30713 | ||
0ce1b118 CV |
30714 | @node close |
30715 | @unnumberedsubsubsec close | |
30716 | @cindex close, file-i/o system call | |
30717 | ||
fc320d37 SL |
30718 | @table @asis |
30719 | @item Synopsis: | |
0ce1b118 | 30720 | @smallexample |
0ce1b118 | 30721 | int close(int fd); |
fc320d37 | 30722 | @end smallexample |
0ce1b118 | 30723 | |
fc320d37 SL |
30724 | @item Request: |
30725 | @samp{Fclose,@var{fd}} | |
0ce1b118 | 30726 | |
fc320d37 SL |
30727 | @item Return value: |
30728 | @code{close} returns zero on success, or -1 if an error occurred. | |
0ce1b118 | 30729 | |
fc320d37 | 30730 | @item Errors: |
0ce1b118 CV |
30731 | |
30732 | @table @code | |
b383017d | 30733 | @item EBADF |
fc320d37 | 30734 | @var{fd} isn't a valid open file descriptor. |
0ce1b118 | 30735 | |
b383017d | 30736 | @item EINTR |
0ce1b118 CV |
30737 | The call was interrupted by the user. |
30738 | @end table | |
30739 | ||
fc320d37 SL |
30740 | @end table |
30741 | ||
0ce1b118 CV |
30742 | @node read |
30743 | @unnumberedsubsubsec read | |
30744 | @cindex read, file-i/o system call | |
30745 | ||
fc320d37 SL |
30746 | @table @asis |
30747 | @item Synopsis: | |
0ce1b118 | 30748 | @smallexample |
0ce1b118 | 30749 | int read(int fd, void *buf, unsigned int count); |
fc320d37 | 30750 | @end smallexample |
0ce1b118 | 30751 | |
fc320d37 SL |
30752 | @item Request: |
30753 | @samp{Fread,@var{fd},@var{bufptr},@var{count}} | |
0ce1b118 | 30754 | |
fc320d37 | 30755 | @item Return value: |
0ce1b118 CV |
30756 | On success, the number of bytes read is returned. |
30757 | Zero indicates end of file. If count is zero, read | |
b383017d | 30758 | returns zero as well. On error, -1 is returned. |
0ce1b118 | 30759 | |
fc320d37 | 30760 | @item Errors: |
0ce1b118 CV |
30761 | |
30762 | @table @code | |
b383017d | 30763 | @item EBADF |
fc320d37 | 30764 | @var{fd} is not a valid file descriptor or is not open for |
0ce1b118 CV |
30765 | reading. |
30766 | ||
b383017d | 30767 | @item EFAULT |
fc320d37 | 30768 | @var{bufptr} is an invalid pointer value. |
0ce1b118 | 30769 | |
b383017d | 30770 | @item EINTR |
0ce1b118 CV |
30771 | The call was interrupted by the user. |
30772 | @end table | |
30773 | ||
fc320d37 SL |
30774 | @end table |
30775 | ||
0ce1b118 CV |
30776 | @node write |
30777 | @unnumberedsubsubsec write | |
30778 | @cindex write, file-i/o system call | |
30779 | ||
fc320d37 SL |
30780 | @table @asis |
30781 | @item Synopsis: | |
0ce1b118 | 30782 | @smallexample |
0ce1b118 | 30783 | int write(int fd, const void *buf, unsigned int count); |
fc320d37 | 30784 | @end smallexample |
0ce1b118 | 30785 | |
fc320d37 SL |
30786 | @item Request: |
30787 | @samp{Fwrite,@var{fd},@var{bufptr},@var{count}} | |
0ce1b118 | 30788 | |
fc320d37 | 30789 | @item Return value: |
0ce1b118 CV |
30790 | On success, the number of bytes written are returned. |
30791 | Zero indicates nothing was written. On error, -1 | |
30792 | is returned. | |
30793 | ||
fc320d37 | 30794 | @item Errors: |
0ce1b118 CV |
30795 | |
30796 | @table @code | |
b383017d | 30797 | @item EBADF |
fc320d37 | 30798 | @var{fd} is not a valid file descriptor or is not open for |
0ce1b118 CV |
30799 | writing. |
30800 | ||
b383017d | 30801 | @item EFAULT |
fc320d37 | 30802 | @var{bufptr} is an invalid pointer value. |
0ce1b118 | 30803 | |
b383017d | 30804 | @item EFBIG |
0ce1b118 | 30805 | An attempt was made to write a file that exceeds the |
db2e3e2e | 30806 | host-specific maximum file size allowed. |
0ce1b118 | 30807 | |
b383017d | 30808 | @item ENOSPC |
0ce1b118 CV |
30809 | No space on device to write the data. |
30810 | ||
b383017d | 30811 | @item EINTR |
0ce1b118 CV |
30812 | The call was interrupted by the user. |
30813 | @end table | |
30814 | ||
fc320d37 SL |
30815 | @end table |
30816 | ||
0ce1b118 CV |
30817 | @node lseek |
30818 | @unnumberedsubsubsec lseek | |
30819 | @cindex lseek, file-i/o system call | |
30820 | ||
fc320d37 SL |
30821 | @table @asis |
30822 | @item Synopsis: | |
0ce1b118 | 30823 | @smallexample |
0ce1b118 | 30824 | long lseek (int fd, long offset, int flag); |
0ce1b118 CV |
30825 | @end smallexample |
30826 | ||
fc320d37 SL |
30827 | @item Request: |
30828 | @samp{Flseek,@var{fd},@var{offset},@var{flag}} | |
30829 | ||
30830 | @var{flag} is one of: | |
0ce1b118 CV |
30831 | |
30832 | @table @code | |
b383017d | 30833 | @item SEEK_SET |
fc320d37 | 30834 | The offset is set to @var{offset} bytes. |
0ce1b118 | 30835 | |
b383017d | 30836 | @item SEEK_CUR |
fc320d37 | 30837 | The offset is set to its current location plus @var{offset} |
0ce1b118 CV |
30838 | bytes. |
30839 | ||
b383017d | 30840 | @item SEEK_END |
fc320d37 | 30841 | The offset is set to the size of the file plus @var{offset} |
0ce1b118 CV |
30842 | bytes. |
30843 | @end table | |
30844 | ||
fc320d37 | 30845 | @item Return value: |
0ce1b118 CV |
30846 | On success, the resulting unsigned offset in bytes from |
30847 | the beginning of the file is returned. Otherwise, a | |
30848 | value of -1 is returned. | |
30849 | ||
fc320d37 | 30850 | @item Errors: |
0ce1b118 CV |
30851 | |
30852 | @table @code | |
b383017d | 30853 | @item EBADF |
fc320d37 | 30854 | @var{fd} is not a valid open file descriptor. |
0ce1b118 | 30855 | |
b383017d | 30856 | @item ESPIPE |
fc320d37 | 30857 | @var{fd} is associated with the @value{GDBN} console. |
0ce1b118 | 30858 | |
b383017d | 30859 | @item EINVAL |
fc320d37 | 30860 | @var{flag} is not a proper value. |
0ce1b118 | 30861 | |
b383017d | 30862 | @item EINTR |
0ce1b118 CV |
30863 | The call was interrupted by the user. |
30864 | @end table | |
30865 | ||
fc320d37 SL |
30866 | @end table |
30867 | ||
0ce1b118 CV |
30868 | @node rename |
30869 | @unnumberedsubsubsec rename | |
30870 | @cindex rename, file-i/o system call | |
30871 | ||
fc320d37 SL |
30872 | @table @asis |
30873 | @item Synopsis: | |
0ce1b118 | 30874 | @smallexample |
0ce1b118 | 30875 | int rename(const char *oldpath, const char *newpath); |
fc320d37 | 30876 | @end smallexample |
0ce1b118 | 30877 | |
fc320d37 SL |
30878 | @item Request: |
30879 | @samp{Frename,@var{oldpathptr}/@var{len},@var{newpathptr}/@var{len}} | |
0ce1b118 | 30880 | |
fc320d37 | 30881 | @item Return value: |
0ce1b118 CV |
30882 | On success, zero is returned. On error, -1 is returned. |
30883 | ||
fc320d37 | 30884 | @item Errors: |
0ce1b118 CV |
30885 | |
30886 | @table @code | |
b383017d | 30887 | @item EISDIR |
fc320d37 | 30888 | @var{newpath} is an existing directory, but @var{oldpath} is not a |
0ce1b118 CV |
30889 | directory. |
30890 | ||
b383017d | 30891 | @item EEXIST |
fc320d37 | 30892 | @var{newpath} is a non-empty directory. |
0ce1b118 | 30893 | |
b383017d | 30894 | @item EBUSY |
fc320d37 | 30895 | @var{oldpath} or @var{newpath} is a directory that is in use by some |
0ce1b118 CV |
30896 | process. |
30897 | ||
b383017d | 30898 | @item EINVAL |
0ce1b118 CV |
30899 | An attempt was made to make a directory a subdirectory |
30900 | of itself. | |
30901 | ||
b383017d | 30902 | @item ENOTDIR |
fc320d37 SL |
30903 | A component used as a directory in @var{oldpath} or new |
30904 | path is not a directory. Or @var{oldpath} is a directory | |
30905 | and @var{newpath} exists but is not a directory. | |
0ce1b118 | 30906 | |
b383017d | 30907 | @item EFAULT |
fc320d37 | 30908 | @var{oldpathptr} or @var{newpathptr} are invalid pointer values. |
0ce1b118 | 30909 | |
b383017d | 30910 | @item EACCES |
0ce1b118 CV |
30911 | No access to the file or the path of the file. |
30912 | ||
30913 | @item ENAMETOOLONG | |
b383017d | 30914 | |
fc320d37 | 30915 | @var{oldpath} or @var{newpath} was too long. |
0ce1b118 | 30916 | |
b383017d | 30917 | @item ENOENT |
fc320d37 | 30918 | A directory component in @var{oldpath} or @var{newpath} does not exist. |
0ce1b118 | 30919 | |
b383017d | 30920 | @item EROFS |
0ce1b118 CV |
30921 | The file is on a read-only filesystem. |
30922 | ||
b383017d | 30923 | @item ENOSPC |
0ce1b118 CV |
30924 | The device containing the file has no room for the new |
30925 | directory entry. | |
30926 | ||
b383017d | 30927 | @item EINTR |
0ce1b118 CV |
30928 | The call was interrupted by the user. |
30929 | @end table | |
30930 | ||
fc320d37 SL |
30931 | @end table |
30932 | ||
0ce1b118 CV |
30933 | @node unlink |
30934 | @unnumberedsubsubsec unlink | |
30935 | @cindex unlink, file-i/o system call | |
30936 | ||
fc320d37 SL |
30937 | @table @asis |
30938 | @item Synopsis: | |
0ce1b118 | 30939 | @smallexample |
0ce1b118 | 30940 | int unlink(const char *pathname); |
fc320d37 | 30941 | @end smallexample |
0ce1b118 | 30942 | |
fc320d37 SL |
30943 | @item Request: |
30944 | @samp{Funlink,@var{pathnameptr}/@var{len}} | |
0ce1b118 | 30945 | |
fc320d37 | 30946 | @item Return value: |
0ce1b118 CV |
30947 | On success, zero is returned. On error, -1 is returned. |
30948 | ||
fc320d37 | 30949 | @item Errors: |
0ce1b118 CV |
30950 | |
30951 | @table @code | |
b383017d | 30952 | @item EACCES |
0ce1b118 CV |
30953 | No access to the file or the path of the file. |
30954 | ||
b383017d | 30955 | @item EPERM |
0ce1b118 CV |
30956 | The system does not allow unlinking of directories. |
30957 | ||
b383017d | 30958 | @item EBUSY |
fc320d37 | 30959 | The file @var{pathname} cannot be unlinked because it's |
0ce1b118 CV |
30960 | being used by another process. |
30961 | ||
b383017d | 30962 | @item EFAULT |
fc320d37 | 30963 | @var{pathnameptr} is an invalid pointer value. |
0ce1b118 CV |
30964 | |
30965 | @item ENAMETOOLONG | |
fc320d37 | 30966 | @var{pathname} was too long. |
0ce1b118 | 30967 | |
b383017d | 30968 | @item ENOENT |
fc320d37 | 30969 | A directory component in @var{pathname} does not exist. |
0ce1b118 | 30970 | |
b383017d | 30971 | @item ENOTDIR |
0ce1b118 CV |
30972 | A component of the path is not a directory. |
30973 | ||
b383017d | 30974 | @item EROFS |
0ce1b118 CV |
30975 | The file is on a read-only filesystem. |
30976 | ||
b383017d | 30977 | @item EINTR |
0ce1b118 CV |
30978 | The call was interrupted by the user. |
30979 | @end table | |
30980 | ||
fc320d37 SL |
30981 | @end table |
30982 | ||
0ce1b118 CV |
30983 | @node stat/fstat |
30984 | @unnumberedsubsubsec stat/fstat | |
30985 | @cindex fstat, file-i/o system call | |
30986 | @cindex stat, file-i/o system call | |
30987 | ||
fc320d37 SL |
30988 | @table @asis |
30989 | @item Synopsis: | |
0ce1b118 | 30990 | @smallexample |
0ce1b118 CV |
30991 | int stat(const char *pathname, struct stat *buf); |
30992 | int fstat(int fd, struct stat *buf); | |
fc320d37 | 30993 | @end smallexample |
0ce1b118 | 30994 | |
fc320d37 SL |
30995 | @item Request: |
30996 | @samp{Fstat,@var{pathnameptr}/@var{len},@var{bufptr}}@* | |
30997 | @samp{Ffstat,@var{fd},@var{bufptr}} | |
0ce1b118 | 30998 | |
fc320d37 | 30999 | @item Return value: |
0ce1b118 CV |
31000 | On success, zero is returned. On error, -1 is returned. |
31001 | ||
fc320d37 | 31002 | @item Errors: |
0ce1b118 CV |
31003 | |
31004 | @table @code | |
b383017d | 31005 | @item EBADF |
fc320d37 | 31006 | @var{fd} is not a valid open file. |
0ce1b118 | 31007 | |
b383017d | 31008 | @item ENOENT |
fc320d37 | 31009 | A directory component in @var{pathname} does not exist or the |
0ce1b118 CV |
31010 | path is an empty string. |
31011 | ||
b383017d | 31012 | @item ENOTDIR |
0ce1b118 CV |
31013 | A component of the path is not a directory. |
31014 | ||
b383017d | 31015 | @item EFAULT |
fc320d37 | 31016 | @var{pathnameptr} is an invalid pointer value. |
0ce1b118 | 31017 | |
b383017d | 31018 | @item EACCES |
0ce1b118 CV |
31019 | No access to the file or the path of the file. |
31020 | ||
31021 | @item ENAMETOOLONG | |
fc320d37 | 31022 | @var{pathname} was too long. |
0ce1b118 | 31023 | |
b383017d | 31024 | @item EINTR |
0ce1b118 CV |
31025 | The call was interrupted by the user. |
31026 | @end table | |
31027 | ||
fc320d37 SL |
31028 | @end table |
31029 | ||
0ce1b118 CV |
31030 | @node gettimeofday |
31031 | @unnumberedsubsubsec gettimeofday | |
31032 | @cindex gettimeofday, file-i/o system call | |
31033 | ||
fc320d37 SL |
31034 | @table @asis |
31035 | @item Synopsis: | |
0ce1b118 | 31036 | @smallexample |
0ce1b118 | 31037 | int gettimeofday(struct timeval *tv, void *tz); |
fc320d37 | 31038 | @end smallexample |
0ce1b118 | 31039 | |
fc320d37 SL |
31040 | @item Request: |
31041 | @samp{Fgettimeofday,@var{tvptr},@var{tzptr}} | |
0ce1b118 | 31042 | |
fc320d37 | 31043 | @item Return value: |
0ce1b118 CV |
31044 | On success, 0 is returned, -1 otherwise. |
31045 | ||
fc320d37 | 31046 | @item Errors: |
0ce1b118 CV |
31047 | |
31048 | @table @code | |
b383017d | 31049 | @item EINVAL |
fc320d37 | 31050 | @var{tz} is a non-NULL pointer. |
0ce1b118 | 31051 | |
b383017d | 31052 | @item EFAULT |
fc320d37 SL |
31053 | @var{tvptr} and/or @var{tzptr} is an invalid pointer value. |
31054 | @end table | |
31055 | ||
0ce1b118 CV |
31056 | @end table |
31057 | ||
31058 | @node isatty | |
31059 | @unnumberedsubsubsec isatty | |
31060 | @cindex isatty, file-i/o system call | |
31061 | ||
fc320d37 SL |
31062 | @table @asis |
31063 | @item Synopsis: | |
0ce1b118 | 31064 | @smallexample |
0ce1b118 | 31065 | int isatty(int fd); |
fc320d37 | 31066 | @end smallexample |
0ce1b118 | 31067 | |
fc320d37 SL |
31068 | @item Request: |
31069 | @samp{Fisatty,@var{fd}} | |
0ce1b118 | 31070 | |
fc320d37 SL |
31071 | @item Return value: |
31072 | Returns 1 if @var{fd} refers to the @value{GDBN} console, 0 otherwise. | |
0ce1b118 | 31073 | |
fc320d37 | 31074 | @item Errors: |
0ce1b118 CV |
31075 | |
31076 | @table @code | |
b383017d | 31077 | @item EINTR |
0ce1b118 CV |
31078 | The call was interrupted by the user. |
31079 | @end table | |
31080 | ||
fc320d37 SL |
31081 | @end table |
31082 | ||
31083 | Note that the @code{isatty} call is treated as a special case: it returns | |
31084 | 1 to the target if the file descriptor is attached | |
31085 | to the @value{GDBN} console, 0 otherwise. Implementing through system calls | |
31086 | would require implementing @code{ioctl} and would be more complex than | |
31087 | needed. | |
31088 | ||
31089 | ||
0ce1b118 CV |
31090 | @node system |
31091 | @unnumberedsubsubsec system | |
31092 | @cindex system, file-i/o system call | |
31093 | ||
fc320d37 SL |
31094 | @table @asis |
31095 | @item Synopsis: | |
0ce1b118 | 31096 | @smallexample |
0ce1b118 | 31097 | int system(const char *command); |
fc320d37 | 31098 | @end smallexample |
0ce1b118 | 31099 | |
fc320d37 SL |
31100 | @item Request: |
31101 | @samp{Fsystem,@var{commandptr}/@var{len}} | |
0ce1b118 | 31102 | |
fc320d37 | 31103 | @item Return value: |
5600ea19 NS |
31104 | If @var{len} is zero, the return value indicates whether a shell is |
31105 | available. A zero return value indicates a shell is not available. | |
31106 | For non-zero @var{len}, the value returned is -1 on error and the | |
31107 | return status of the command otherwise. Only the exit status of the | |
31108 | command is returned, which is extracted from the host's @code{system} | |
31109 | return value by calling @code{WEXITSTATUS(retval)}. In case | |
31110 | @file{/bin/sh} could not be executed, 127 is returned. | |
0ce1b118 | 31111 | |
fc320d37 | 31112 | @item Errors: |
0ce1b118 CV |
31113 | |
31114 | @table @code | |
b383017d | 31115 | @item EINTR |
0ce1b118 CV |
31116 | The call was interrupted by the user. |
31117 | @end table | |
31118 | ||
fc320d37 SL |
31119 | @end table |
31120 | ||
31121 | @value{GDBN} takes over the full task of calling the necessary host calls | |
31122 | to perform the @code{system} call. The return value of @code{system} on | |
31123 | the host is simplified before it's returned | |
31124 | to the target. Any termination signal information from the child process | |
31125 | is discarded, and the return value consists | |
31126 | entirely of the exit status of the called command. | |
31127 | ||
31128 | Due to security concerns, the @code{system} call is by default refused | |
31129 | by @value{GDBN}. The user has to allow this call explicitly with the | |
31130 | @code{set remote system-call-allowed 1} command. | |
31131 | ||
31132 | @table @code | |
31133 | @item set remote system-call-allowed | |
31134 | @kindex set remote system-call-allowed | |
31135 | Control whether to allow the @code{system} calls in the File I/O | |
31136 | protocol for the remote target. The default is zero (disabled). | |
31137 | ||
31138 | @item show remote system-call-allowed | |
31139 | @kindex show remote system-call-allowed | |
31140 | Show whether the @code{system} calls are allowed in the File I/O | |
31141 | protocol. | |
31142 | @end table | |
31143 | ||
db2e3e2e BW |
31144 | @node Protocol-specific Representation of Datatypes |
31145 | @subsection Protocol-specific Representation of Datatypes | |
31146 | @cindex protocol-specific representation of datatypes, in file-i/o protocol | |
0ce1b118 CV |
31147 | |
31148 | @menu | |
79a6e687 BW |
31149 | * Integral Datatypes:: |
31150 | * Pointer Values:: | |
31151 | * Memory Transfer:: | |
0ce1b118 CV |
31152 | * struct stat:: |
31153 | * struct timeval:: | |
31154 | @end menu | |
31155 | ||
79a6e687 BW |
31156 | @node Integral Datatypes |
31157 | @unnumberedsubsubsec Integral Datatypes | |
0ce1b118 CV |
31158 | @cindex integral datatypes, in file-i/o protocol |
31159 | ||
fc320d37 SL |
31160 | The integral datatypes used in the system calls are @code{int}, |
31161 | @code{unsigned int}, @code{long}, @code{unsigned long}, | |
31162 | @code{mode_t}, and @code{time_t}. | |
0ce1b118 | 31163 | |
fc320d37 | 31164 | @code{int}, @code{unsigned int}, @code{mode_t} and @code{time_t} are |
0ce1b118 CV |
31165 | implemented as 32 bit values in this protocol. |
31166 | ||
fc320d37 | 31167 | @code{long} and @code{unsigned long} are implemented as 64 bit types. |
b383017d | 31168 | |
0ce1b118 CV |
31169 | @xref{Limits}, for corresponding MIN and MAX values (similar to those |
31170 | in @file{limits.h}) to allow range checking on host and target. | |
31171 | ||
31172 | @code{time_t} datatypes are defined as seconds since the Epoch. | |
31173 | ||
31174 | All integral datatypes transferred as part of a memory read or write of a | |
31175 | structured datatype e.g.@: a @code{struct stat} have to be given in big endian | |
31176 | byte order. | |
31177 | ||
79a6e687 BW |
31178 | @node Pointer Values |
31179 | @unnumberedsubsubsec Pointer Values | |
0ce1b118 CV |
31180 | @cindex pointer values, in file-i/o protocol |
31181 | ||
31182 | Pointers to target data are transmitted as they are. An exception | |
31183 | is made for pointers to buffers for which the length isn't | |
31184 | transmitted as part of the function call, namely strings. Strings | |
31185 | are transmitted as a pointer/length pair, both as hex values, e.g.@: | |
31186 | ||
31187 | @smallexample | |
31188 | @code{1aaf/12} | |
31189 | @end smallexample | |
31190 | ||
31191 | @noindent | |
31192 | which is a pointer to data of length 18 bytes at position 0x1aaf. | |
31193 | The length is defined as the full string length in bytes, including | |
fc320d37 SL |
31194 | the trailing null byte. For example, the string @code{"hello world"} |
31195 | at address 0x123456 is transmitted as | |
0ce1b118 CV |
31196 | |
31197 | @smallexample | |
fc320d37 | 31198 | @code{123456/d} |
0ce1b118 CV |
31199 | @end smallexample |
31200 | ||
79a6e687 BW |
31201 | @node Memory Transfer |
31202 | @unnumberedsubsubsec Memory Transfer | |
fc320d37 SL |
31203 | @cindex memory transfer, in file-i/o protocol |
31204 | ||
31205 | Structured data which is transferred using a memory read or write (for | |
db2e3e2e | 31206 | example, a @code{struct stat}) is expected to be in a protocol-specific format |
fc320d37 SL |
31207 | with all scalar multibyte datatypes being big endian. Translation to |
31208 | this representation needs to be done both by the target before the @code{F} | |
31209 | packet is sent, and by @value{GDBN} before | |
31210 | it transfers memory to the target. Transferred pointers to structured | |
31211 | data should point to the already-coerced data at any time. | |
0ce1b118 | 31212 | |
0ce1b118 CV |
31213 | |
31214 | @node struct stat | |
31215 | @unnumberedsubsubsec struct stat | |
31216 | @cindex struct stat, in file-i/o protocol | |
31217 | ||
fc320d37 SL |
31218 | The buffer of type @code{struct stat} used by the target and @value{GDBN} |
31219 | is defined as follows: | |
0ce1b118 CV |
31220 | |
31221 | @smallexample | |
31222 | struct stat @{ | |
31223 | unsigned int st_dev; /* device */ | |
31224 | unsigned int st_ino; /* inode */ | |
31225 | mode_t st_mode; /* protection */ | |
31226 | unsigned int st_nlink; /* number of hard links */ | |
31227 | unsigned int st_uid; /* user ID of owner */ | |
31228 | unsigned int st_gid; /* group ID of owner */ | |
31229 | unsigned int st_rdev; /* device type (if inode device) */ | |
31230 | unsigned long st_size; /* total size, in bytes */ | |
31231 | unsigned long st_blksize; /* blocksize for filesystem I/O */ | |
31232 | unsigned long st_blocks; /* number of blocks allocated */ | |
31233 | time_t st_atime; /* time of last access */ | |
31234 | time_t st_mtime; /* time of last modification */ | |
31235 | time_t st_ctime; /* time of last change */ | |
31236 | @}; | |
31237 | @end smallexample | |
31238 | ||
fc320d37 | 31239 | The integral datatypes conform to the definitions given in the |
79a6e687 | 31240 | appropriate section (see @ref{Integral Datatypes}, for details) so this |
0ce1b118 CV |
31241 | structure is of size 64 bytes. |
31242 | ||
31243 | The values of several fields have a restricted meaning and/or | |
31244 | range of values. | |
31245 | ||
fc320d37 | 31246 | @table @code |
0ce1b118 | 31247 | |
fc320d37 SL |
31248 | @item st_dev |
31249 | A value of 0 represents a file, 1 the console. | |
0ce1b118 | 31250 | |
fc320d37 SL |
31251 | @item st_ino |
31252 | No valid meaning for the target. Transmitted unchanged. | |
0ce1b118 | 31253 | |
fc320d37 SL |
31254 | @item st_mode |
31255 | Valid mode bits are described in @ref{Constants}. Any other | |
31256 | bits have currently no meaning for the target. | |
0ce1b118 | 31257 | |
fc320d37 SL |
31258 | @item st_uid |
31259 | @itemx st_gid | |
31260 | @itemx st_rdev | |
31261 | No valid meaning for the target. Transmitted unchanged. | |
0ce1b118 | 31262 | |
fc320d37 SL |
31263 | @item st_atime |
31264 | @itemx st_mtime | |
31265 | @itemx st_ctime | |
31266 | These values have a host and file system dependent | |
31267 | accuracy. Especially on Windows hosts, the file system may not | |
31268 | support exact timing values. | |
31269 | @end table | |
0ce1b118 | 31270 | |
fc320d37 SL |
31271 | The target gets a @code{struct stat} of the above representation and is |
31272 | responsible for coercing it to the target representation before | |
0ce1b118 CV |
31273 | continuing. |
31274 | ||
fc320d37 SL |
31275 | Note that due to size differences between the host, target, and protocol |
31276 | representations of @code{struct stat} members, these members could eventually | |
0ce1b118 CV |
31277 | get truncated on the target. |
31278 | ||
31279 | @node struct timeval | |
31280 | @unnumberedsubsubsec struct timeval | |
31281 | @cindex struct timeval, in file-i/o protocol | |
31282 | ||
fc320d37 | 31283 | The buffer of type @code{struct timeval} used by the File-I/O protocol |
0ce1b118 CV |
31284 | is defined as follows: |
31285 | ||
31286 | @smallexample | |
b383017d | 31287 | struct timeval @{ |
0ce1b118 CV |
31288 | time_t tv_sec; /* second */ |
31289 | long tv_usec; /* microsecond */ | |
31290 | @}; | |
31291 | @end smallexample | |
31292 | ||
fc320d37 | 31293 | The integral datatypes conform to the definitions given in the |
79a6e687 | 31294 | appropriate section (see @ref{Integral Datatypes}, for details) so this |
0ce1b118 CV |
31295 | structure is of size 8 bytes. |
31296 | ||
31297 | @node Constants | |
31298 | @subsection Constants | |
31299 | @cindex constants, in file-i/o protocol | |
31300 | ||
31301 | The following values are used for the constants inside of the | |
fc320d37 | 31302 | protocol. @value{GDBN} and target are responsible for translating these |
0ce1b118 CV |
31303 | values before and after the call as needed. |
31304 | ||
31305 | @menu | |
79a6e687 BW |
31306 | * Open Flags:: |
31307 | * mode_t Values:: | |
31308 | * Errno Values:: | |
31309 | * Lseek Flags:: | |
0ce1b118 CV |
31310 | * Limits:: |
31311 | @end menu | |
31312 | ||
79a6e687 BW |
31313 | @node Open Flags |
31314 | @unnumberedsubsubsec Open Flags | |
0ce1b118 CV |
31315 | @cindex open flags, in file-i/o protocol |
31316 | ||
31317 | All values are given in hexadecimal representation. | |
31318 | ||
31319 | @smallexample | |
31320 | O_RDONLY 0x0 | |
31321 | O_WRONLY 0x1 | |
31322 | O_RDWR 0x2 | |
31323 | O_APPEND 0x8 | |
31324 | O_CREAT 0x200 | |
31325 | O_TRUNC 0x400 | |
31326 | O_EXCL 0x800 | |
31327 | @end smallexample | |
31328 | ||
79a6e687 BW |
31329 | @node mode_t Values |
31330 | @unnumberedsubsubsec mode_t Values | |
0ce1b118 CV |
31331 | @cindex mode_t values, in file-i/o protocol |
31332 | ||
31333 | All values are given in octal representation. | |
31334 | ||
31335 | @smallexample | |
31336 | S_IFREG 0100000 | |
31337 | S_IFDIR 040000 | |
31338 | S_IRUSR 0400 | |
31339 | S_IWUSR 0200 | |
31340 | S_IXUSR 0100 | |
31341 | S_IRGRP 040 | |
31342 | S_IWGRP 020 | |
31343 | S_IXGRP 010 | |
31344 | S_IROTH 04 | |
31345 | S_IWOTH 02 | |
31346 | S_IXOTH 01 | |
31347 | @end smallexample | |
31348 | ||
79a6e687 BW |
31349 | @node Errno Values |
31350 | @unnumberedsubsubsec Errno Values | |
0ce1b118 CV |
31351 | @cindex errno values, in file-i/o protocol |
31352 | ||
31353 | All values are given in decimal representation. | |
31354 | ||
31355 | @smallexample | |
31356 | EPERM 1 | |
31357 | ENOENT 2 | |
31358 | EINTR 4 | |
31359 | EBADF 9 | |
31360 | EACCES 13 | |
31361 | EFAULT 14 | |
31362 | EBUSY 16 | |
31363 | EEXIST 17 | |
31364 | ENODEV 19 | |
31365 | ENOTDIR 20 | |
31366 | EISDIR 21 | |
31367 | EINVAL 22 | |
31368 | ENFILE 23 | |
31369 | EMFILE 24 | |
31370 | EFBIG 27 | |
31371 | ENOSPC 28 | |
31372 | ESPIPE 29 | |
31373 | EROFS 30 | |
31374 | ENAMETOOLONG 91 | |
31375 | EUNKNOWN 9999 | |
31376 | @end smallexample | |
31377 | ||
fc320d37 | 31378 | @code{EUNKNOWN} is used as a fallback error value if a host system returns |
0ce1b118 CV |
31379 | any error value not in the list of supported error numbers. |
31380 | ||
79a6e687 BW |
31381 | @node Lseek Flags |
31382 | @unnumberedsubsubsec Lseek Flags | |
0ce1b118 CV |
31383 | @cindex lseek flags, in file-i/o protocol |
31384 | ||
31385 | @smallexample | |
31386 | SEEK_SET 0 | |
31387 | SEEK_CUR 1 | |
31388 | SEEK_END 2 | |
31389 | @end smallexample | |
31390 | ||
31391 | @node Limits | |
31392 | @unnumberedsubsubsec Limits | |
31393 | @cindex limits, in file-i/o protocol | |
31394 | ||
31395 | All values are given in decimal representation. | |
31396 | ||
31397 | @smallexample | |
31398 | INT_MIN -2147483648 | |
31399 | INT_MAX 2147483647 | |
31400 | UINT_MAX 4294967295 | |
31401 | LONG_MIN -9223372036854775808 | |
31402 | LONG_MAX 9223372036854775807 | |
31403 | ULONG_MAX 18446744073709551615 | |
31404 | @end smallexample | |
31405 | ||
31406 | @node File-I/O Examples | |
31407 | @subsection File-I/O Examples | |
31408 | @cindex file-i/o examples | |
31409 | ||
31410 | Example sequence of a write call, file descriptor 3, buffer is at target | |
31411 | address 0x1234, 6 bytes should be written: | |
31412 | ||
31413 | @smallexample | |
31414 | <- @code{Fwrite,3,1234,6} | |
31415 | @emph{request memory read from target} | |
31416 | -> @code{m1234,6} | |
31417 | <- XXXXXX | |
31418 | @emph{return "6 bytes written"} | |
31419 | -> @code{F6} | |
31420 | @end smallexample | |
31421 | ||
31422 | Example sequence of a read call, file descriptor 3, buffer is at target | |
31423 | address 0x1234, 6 bytes should be read: | |
31424 | ||
31425 | @smallexample | |
31426 | <- @code{Fread,3,1234,6} | |
31427 | @emph{request memory write to target} | |
31428 | -> @code{X1234,6:XXXXXX} | |
31429 | @emph{return "6 bytes read"} | |
31430 | -> @code{F6} | |
31431 | @end smallexample | |
31432 | ||
31433 | Example sequence of a read call, call fails on the host due to invalid | |
fc320d37 | 31434 | file descriptor (@code{EBADF}): |
0ce1b118 CV |
31435 | |
31436 | @smallexample | |
31437 | <- @code{Fread,3,1234,6} | |
31438 | -> @code{F-1,9} | |
31439 | @end smallexample | |
31440 | ||
c8aa23ab | 31441 | Example sequence of a read call, user presses @kbd{Ctrl-c} before syscall on |
0ce1b118 CV |
31442 | host is called: |
31443 | ||
31444 | @smallexample | |
31445 | <- @code{Fread,3,1234,6} | |
31446 | -> @code{F-1,4,C} | |
31447 | <- @code{T02} | |
31448 | @end smallexample | |
31449 | ||
c8aa23ab | 31450 | Example sequence of a read call, user presses @kbd{Ctrl-c} after syscall on |
0ce1b118 CV |
31451 | host is called: |
31452 | ||
31453 | @smallexample | |
31454 | <- @code{Fread,3,1234,6} | |
31455 | -> @code{X1234,6:XXXXXX} | |
31456 | <- @code{T02} | |
31457 | @end smallexample | |
31458 | ||
cfa9d6d9 DJ |
31459 | @node Library List Format |
31460 | @section Library List Format | |
31461 | @cindex library list format, remote protocol | |
31462 | ||
31463 | On some platforms, a dynamic loader (e.g.@: @file{ld.so}) runs in the | |
31464 | same process as your application to manage libraries. In this case, | |
31465 | @value{GDBN} can use the loader's symbol table and normal memory | |
31466 | operations to maintain a list of shared libraries. On other | |
31467 | platforms, the operating system manages loaded libraries. | |
31468 | @value{GDBN} can not retrieve the list of currently loaded libraries | |
31469 | through memory operations, so it uses the @samp{qXfer:libraries:read} | |
31470 | packet (@pxref{qXfer library list read}) instead. The remote stub | |
31471 | queries the target's operating system and reports which libraries | |
31472 | are loaded. | |
31473 | ||
31474 | The @samp{qXfer:libraries:read} packet returns an XML document which | |
31475 | lists loaded libraries and their offsets. Each library has an | |
1fddbabb PA |
31476 | associated name and one or more segment or section base addresses, |
31477 | which report where the library was loaded in memory. | |
31478 | ||
31479 | For the common case of libraries that are fully linked binaries, the | |
31480 | library should have a list of segments. If the target supports | |
31481 | dynamic linking of a relocatable object file, its library XML element | |
31482 | should instead include a list of allocated sections. The segment or | |
31483 | section bases are start addresses, not relocation offsets; they do not | |
31484 | depend on the library's link-time base addresses. | |
cfa9d6d9 | 31485 | |
9cceb671 DJ |
31486 | @value{GDBN} must be linked with the Expat library to support XML |
31487 | library lists. @xref{Expat}. | |
31488 | ||
cfa9d6d9 DJ |
31489 | A simple memory map, with one loaded library relocated by a single |
31490 | offset, looks like this: | |
31491 | ||
31492 | @smallexample | |
31493 | <library-list> | |
31494 | <library name="/lib/libc.so.6"> | |
31495 | <segment address="0x10000000"/> | |
31496 | </library> | |
31497 | </library-list> | |
31498 | @end smallexample | |
31499 | ||
1fddbabb PA |
31500 | Another simple memory map, with one loaded library with three |
31501 | allocated sections (.text, .data, .bss), looks like this: | |
31502 | ||
31503 | @smallexample | |
31504 | <library-list> | |
31505 | <library name="sharedlib.o"> | |
31506 | <section address="0x10000000"/> | |
31507 | <section address="0x20000000"/> | |
31508 | <section address="0x30000000"/> | |
31509 | </library> | |
31510 | </library-list> | |
31511 | @end smallexample | |
31512 | ||
cfa9d6d9 DJ |
31513 | The format of a library list is described by this DTD: |
31514 | ||
31515 | @smallexample | |
31516 | <!-- library-list: Root element with versioning --> | |
31517 | <!ELEMENT library-list (library)*> | |
31518 | <!ATTLIST library-list version CDATA #FIXED "1.0"> | |
1fddbabb | 31519 | <!ELEMENT library (segment*, section*)> |
cfa9d6d9 DJ |
31520 | <!ATTLIST library name CDATA #REQUIRED> |
31521 | <!ELEMENT segment EMPTY> | |
31522 | <!ATTLIST segment address CDATA #REQUIRED> | |
1fddbabb PA |
31523 | <!ELEMENT section EMPTY> |
31524 | <!ATTLIST section address CDATA #REQUIRED> | |
cfa9d6d9 DJ |
31525 | @end smallexample |
31526 | ||
1fddbabb PA |
31527 | In addition, segments and section descriptors cannot be mixed within a |
31528 | single library element, and you must supply at least one segment or | |
31529 | section for each library. | |
31530 | ||
79a6e687 BW |
31531 | @node Memory Map Format |
31532 | @section Memory Map Format | |
68437a39 DJ |
31533 | @cindex memory map format |
31534 | ||
31535 | To be able to write into flash memory, @value{GDBN} needs to obtain a | |
31536 | memory map from the target. This section describes the format of the | |
31537 | memory map. | |
31538 | ||
31539 | The memory map is obtained using the @samp{qXfer:memory-map:read} | |
31540 | (@pxref{qXfer memory map read}) packet and is an XML document that | |
9cceb671 DJ |
31541 | lists memory regions. |
31542 | ||
31543 | @value{GDBN} must be linked with the Expat library to support XML | |
31544 | memory maps. @xref{Expat}. | |
31545 | ||
31546 | The top-level structure of the document is shown below: | |
68437a39 DJ |
31547 | |
31548 | @smallexample | |
31549 | <?xml version="1.0"?> | |
31550 | <!DOCTYPE memory-map | |
31551 | PUBLIC "+//IDN gnu.org//DTD GDB Memory Map V1.0//EN" | |
31552 | "http://sourceware.org/gdb/gdb-memory-map.dtd"> | |
31553 | <memory-map> | |
31554 | region... | |
31555 | </memory-map> | |
31556 | @end smallexample | |
31557 | ||
31558 | Each region can be either: | |
31559 | ||
31560 | @itemize | |
31561 | ||
31562 | @item | |
31563 | A region of RAM starting at @var{addr} and extending for @var{length} | |
31564 | bytes from there: | |
31565 | ||
31566 | @smallexample | |
31567 | <memory type="ram" start="@var{addr}" length="@var{length}"/> | |
31568 | @end smallexample | |
31569 | ||
31570 | ||
31571 | @item | |
31572 | A region of read-only memory: | |
31573 | ||
31574 | @smallexample | |
31575 | <memory type="rom" start="@var{addr}" length="@var{length}"/> | |
31576 | @end smallexample | |
31577 | ||
31578 | ||
31579 | @item | |
31580 | A region of flash memory, with erasure blocks @var{blocksize} | |
31581 | bytes in length: | |
31582 | ||
31583 | @smallexample | |
31584 | <memory type="flash" start="@var{addr}" length="@var{length}"> | |
31585 | <property name="blocksize">@var{blocksize}</property> | |
31586 | </memory> | |
31587 | @end smallexample | |
31588 | ||
31589 | @end itemize | |
31590 | ||
31591 | Regions must not overlap. @value{GDBN} assumes that areas of memory not covered | |
31592 | by the memory map are RAM, and uses the ordinary @samp{M} and @samp{X} | |
31593 | packets to write to addresses in such ranges. | |
31594 | ||
31595 | The formal DTD for memory map format is given below: | |
31596 | ||
31597 | @smallexample | |
31598 | <!-- ................................................... --> | |
31599 | <!-- Memory Map XML DTD ................................ --> | |
31600 | <!-- File: memory-map.dtd .............................. --> | |
31601 | <!-- .................................... .............. --> | |
31602 | <!-- memory-map.dtd --> | |
31603 | <!-- memory-map: Root element with versioning --> | |
31604 | <!ELEMENT memory-map (memory | property)> | |
31605 | <!ATTLIST memory-map version CDATA #FIXED "1.0.0"> | |
31606 | <!ELEMENT memory (property)> | |
31607 | <!-- memory: Specifies a memory region, | |
31608 | and its type, or device. --> | |
31609 | <!ATTLIST memory type CDATA #REQUIRED | |
31610 | start CDATA #REQUIRED | |
31611 | length CDATA #REQUIRED | |
31612 | device CDATA #IMPLIED> | |
31613 | <!-- property: Generic attribute tag --> | |
31614 | <!ELEMENT property (#PCDATA | property)*> | |
31615 | <!ATTLIST property name CDATA #REQUIRED> | |
31616 | @end smallexample | |
31617 | ||
f418dd93 DJ |
31618 | @include agentexpr.texi |
31619 | ||
23181151 DJ |
31620 | @node Target Descriptions |
31621 | @appendix Target Descriptions | |
31622 | @cindex target descriptions | |
31623 | ||
31624 | @strong{Warning:} target descriptions are still under active development, | |
31625 | and the contents and format may change between @value{GDBN} releases. | |
31626 | The format is expected to stabilize in the future. | |
31627 | ||
31628 | One of the challenges of using @value{GDBN} to debug embedded systems | |
31629 | is that there are so many minor variants of each processor | |
31630 | architecture in use. It is common practice for vendors to start with | |
31631 | a standard processor core --- ARM, PowerPC, or MIPS, for example --- | |
31632 | and then make changes to adapt it to a particular market niche. Some | |
31633 | architectures have hundreds of variants, available from dozens of | |
31634 | vendors. This leads to a number of problems: | |
31635 | ||
31636 | @itemize @bullet | |
31637 | @item | |
31638 | With so many different customized processors, it is difficult for | |
31639 | the @value{GDBN} maintainers to keep up with the changes. | |
31640 | @item | |
31641 | Since individual variants may have short lifetimes or limited | |
31642 | audiences, it may not be worthwhile to carry information about every | |
31643 | variant in the @value{GDBN} source tree. | |
31644 | @item | |
31645 | When @value{GDBN} does support the architecture of the embedded system | |
31646 | at hand, the task of finding the correct architecture name to give the | |
31647 | @command{set architecture} command can be error-prone. | |
31648 | @end itemize | |
31649 | ||
31650 | To address these problems, the @value{GDBN} remote protocol allows a | |
31651 | target system to not only identify itself to @value{GDBN}, but to | |
31652 | actually describe its own features. This lets @value{GDBN} support | |
31653 | processor variants it has never seen before --- to the extent that the | |
31654 | descriptions are accurate, and that @value{GDBN} understands them. | |
31655 | ||
9cceb671 DJ |
31656 | @value{GDBN} must be linked with the Expat library to support XML |
31657 | target descriptions. @xref{Expat}. | |
123dc839 | 31658 | |
23181151 DJ |
31659 | @menu |
31660 | * Retrieving Descriptions:: How descriptions are fetched from a target. | |
31661 | * Target Description Format:: The contents of a target description. | |
123dc839 DJ |
31662 | * Predefined Target Types:: Standard types available for target |
31663 | descriptions. | |
31664 | * Standard Target Features:: Features @value{GDBN} knows about. | |
23181151 DJ |
31665 | @end menu |
31666 | ||
31667 | @node Retrieving Descriptions | |
31668 | @section Retrieving Descriptions | |
31669 | ||
31670 | Target descriptions can be read from the target automatically, or | |
31671 | specified by the user manually. The default behavior is to read the | |
31672 | description from the target. @value{GDBN} retrieves it via the remote | |
31673 | protocol using @samp{qXfer} requests (@pxref{General Query Packets, | |
31674 | qXfer}). The @var{annex} in the @samp{qXfer} packet will be | |
31675 | @samp{target.xml}. The contents of the @samp{target.xml} annex are an | |
31676 | XML document, of the form described in @ref{Target Description | |
31677 | Format}. | |
31678 | ||
31679 | Alternatively, you can specify a file to read for the target description. | |
31680 | If a file is set, the target will not be queried. The commands to | |
31681 | specify a file are: | |
31682 | ||
31683 | @table @code | |
31684 | @cindex set tdesc filename | |
31685 | @item set tdesc filename @var{path} | |
31686 | Read the target description from @var{path}. | |
31687 | ||
31688 | @cindex unset tdesc filename | |
31689 | @item unset tdesc filename | |
31690 | Do not read the XML target description from a file. @value{GDBN} | |
31691 | will use the description supplied by the current target. | |
31692 | ||
31693 | @cindex show tdesc filename | |
31694 | @item show tdesc filename | |
31695 | Show the filename to read for a target description, if any. | |
31696 | @end table | |
31697 | ||
31698 | ||
31699 | @node Target Description Format | |
31700 | @section Target Description Format | |
31701 | @cindex target descriptions, XML format | |
31702 | ||
31703 | A target description annex is an @uref{http://www.w3.org/XML/, XML} | |
31704 | document which complies with the Document Type Definition provided in | |
31705 | the @value{GDBN} sources in @file{gdb/features/gdb-target.dtd}. This | |
31706 | means you can use generally available tools like @command{xmllint} to | |
31707 | check that your feature descriptions are well-formed and valid. | |
31708 | However, to help people unfamiliar with XML write descriptions for | |
31709 | their targets, we also describe the grammar here. | |
31710 | ||
123dc839 DJ |
31711 | Target descriptions can identify the architecture of the remote target |
31712 | and (for some architectures) provide information about custom register | |
08d16641 PA |
31713 | sets. They can also identify the OS ABI of the remote target. |
31714 | @value{GDBN} can use this information to autoconfigure for your | |
123dc839 | 31715 | target, or to warn you if you connect to an unsupported target. |
23181151 DJ |
31716 | |
31717 | Here is a simple target description: | |
31718 | ||
123dc839 | 31719 | @smallexample |
1780a0ed | 31720 | <target version="1.0"> |
23181151 DJ |
31721 | <architecture>i386:x86-64</architecture> |
31722 | </target> | |
123dc839 | 31723 | @end smallexample |
23181151 DJ |
31724 | |
31725 | @noindent | |
31726 | This minimal description only says that the target uses | |
31727 | the x86-64 architecture. | |
31728 | ||
123dc839 DJ |
31729 | A target description has the following overall form, with [ ] marking |
31730 | optional elements and @dots{} marking repeatable elements. The elements | |
31731 | are explained further below. | |
23181151 | 31732 | |
123dc839 | 31733 | @smallexample |
23181151 DJ |
31734 | <?xml version="1.0"?> |
31735 | <!DOCTYPE target SYSTEM "gdb-target.dtd"> | |
1780a0ed | 31736 | <target version="1.0"> |
123dc839 | 31737 | @r{[}@var{architecture}@r{]} |
08d16641 | 31738 | @r{[}@var{osabi}@r{]} |
e35359c5 | 31739 | @r{[}@var{compatible}@r{]} |
123dc839 | 31740 | @r{[}@var{feature}@dots{}@r{]} |
23181151 | 31741 | </target> |
123dc839 | 31742 | @end smallexample |
23181151 DJ |
31743 | |
31744 | @noindent | |
31745 | The description is generally insensitive to whitespace and line | |
31746 | breaks, under the usual common-sense rules. The XML version | |
31747 | declaration and document type declaration can generally be omitted | |
31748 | (@value{GDBN} does not require them), but specifying them may be | |
1780a0ed DJ |
31749 | useful for XML validation tools. The @samp{version} attribute for |
31750 | @samp{<target>} may also be omitted, but we recommend | |
31751 | including it; if future versions of @value{GDBN} use an incompatible | |
31752 | revision of @file{gdb-target.dtd}, they will detect and report | |
31753 | the version mismatch. | |
23181151 | 31754 | |
108546a0 DJ |
31755 | @subsection Inclusion |
31756 | @cindex target descriptions, inclusion | |
31757 | @cindex XInclude | |
31758 | @ifnotinfo | |
31759 | @cindex <xi:include> | |
31760 | @end ifnotinfo | |
31761 | ||
31762 | It can sometimes be valuable to split a target description up into | |
31763 | several different annexes, either for organizational purposes, or to | |
31764 | share files between different possible target descriptions. You can | |
31765 | divide a description into multiple files by replacing any element of | |
31766 | the target description with an inclusion directive of the form: | |
31767 | ||
123dc839 | 31768 | @smallexample |
108546a0 | 31769 | <xi:include href="@var{document}"/> |
123dc839 | 31770 | @end smallexample |
108546a0 DJ |
31771 | |
31772 | @noindent | |
31773 | When @value{GDBN} encounters an element of this form, it will retrieve | |
31774 | the named XML @var{document}, and replace the inclusion directive with | |
31775 | the contents of that document. If the current description was read | |
31776 | using @samp{qXfer}, then so will be the included document; | |
31777 | @var{document} will be interpreted as the name of an annex. If the | |
31778 | current description was read from a file, @value{GDBN} will look for | |
31779 | @var{document} as a file in the same directory where it found the | |
31780 | original description. | |
31781 | ||
123dc839 DJ |
31782 | @subsection Architecture |
31783 | @cindex <architecture> | |
31784 | ||
31785 | An @samp{<architecture>} element has this form: | |
31786 | ||
31787 | @smallexample | |
31788 | <architecture>@var{arch}</architecture> | |
31789 | @end smallexample | |
31790 | ||
e35359c5 UW |
31791 | @var{arch} is one of the architectures from the set accepted by |
31792 | @code{set architecture} (@pxref{Targets, ,Specifying a Debugging Target}). | |
123dc839 | 31793 | |
08d16641 PA |
31794 | @subsection OS ABI |
31795 | @cindex @code{<osabi>} | |
31796 | ||
31797 | This optional field was introduced in @value{GDBN} version 7.0. | |
31798 | Previous versions of @value{GDBN} ignore it. | |
31799 | ||
31800 | An @samp{<osabi>} element has this form: | |
31801 | ||
31802 | @smallexample | |
31803 | <osabi>@var{abi-name}</osabi> | |
31804 | @end smallexample | |
31805 | ||
31806 | @var{abi-name} is an OS ABI name from the same selection accepted by | |
31807 | @w{@code{set osabi}} (@pxref{ABI, ,Configuring the Current ABI}). | |
31808 | ||
e35359c5 UW |
31809 | @subsection Compatible Architecture |
31810 | @cindex @code{<compatible>} | |
31811 | ||
31812 | This optional field was introduced in @value{GDBN} version 7.0. | |
31813 | Previous versions of @value{GDBN} ignore it. | |
31814 | ||
31815 | A @samp{<compatible>} element has this form: | |
31816 | ||
31817 | @smallexample | |
31818 | <compatible>@var{arch}</compatible> | |
31819 | @end smallexample | |
31820 | ||
31821 | @var{arch} is one of the architectures from the set accepted by | |
31822 | @code{set architecture} (@pxref{Targets, ,Specifying a Debugging Target}). | |
31823 | ||
31824 | A @samp{<compatible>} element is used to specify that the target | |
31825 | is able to run binaries in some other than the main target architecture | |
31826 | given by the @samp{<architecture>} element. For example, on the | |
31827 | Cell Broadband Engine, the main architecture is @code{powerpc:common} | |
31828 | or @code{powerpc:common64}, but the system is able to run binaries | |
31829 | in the @code{spu} architecture as well. The way to describe this | |
31830 | capability with @samp{<compatible>} is as follows: | |
31831 | ||
31832 | @smallexample | |
31833 | <architecture>powerpc:common</architecture> | |
31834 | <compatible>spu</compatible> | |
31835 | @end smallexample | |
31836 | ||
123dc839 DJ |
31837 | @subsection Features |
31838 | @cindex <feature> | |
31839 | ||
31840 | Each @samp{<feature>} describes some logical portion of the target | |
31841 | system. Features are currently used to describe available CPU | |
31842 | registers and the types of their contents. A @samp{<feature>} element | |
31843 | has this form: | |
31844 | ||
31845 | @smallexample | |
31846 | <feature name="@var{name}"> | |
31847 | @r{[}@var{type}@dots{}@r{]} | |
31848 | @var{reg}@dots{} | |
31849 | </feature> | |
31850 | @end smallexample | |
31851 | ||
31852 | @noindent | |
31853 | Each feature's name should be unique within the description. The name | |
31854 | of a feature does not matter unless @value{GDBN} has some special | |
31855 | knowledge of the contents of that feature; if it does, the feature | |
31856 | should have its standard name. @xref{Standard Target Features}. | |
31857 | ||
31858 | @subsection Types | |
31859 | ||
31860 | Any register's value is a collection of bits which @value{GDBN} must | |
31861 | interpret. The default interpretation is a two's complement integer, | |
31862 | but other types can be requested by name in the register description. | |
31863 | Some predefined types are provided by @value{GDBN} (@pxref{Predefined | |
31864 | Target Types}), and the description can define additional composite types. | |
31865 | ||
31866 | Each type element must have an @samp{id} attribute, which gives | |
31867 | a unique (within the containing @samp{<feature>}) name to the type. | |
31868 | Types must be defined before they are used. | |
31869 | ||
31870 | @cindex <vector> | |
31871 | Some targets offer vector registers, which can be treated as arrays | |
31872 | of scalar elements. These types are written as @samp{<vector>} elements, | |
31873 | specifying the array element type, @var{type}, and the number of elements, | |
31874 | @var{count}: | |
31875 | ||
31876 | @smallexample | |
31877 | <vector id="@var{id}" type="@var{type}" count="@var{count}"/> | |
31878 | @end smallexample | |
31879 | ||
31880 | @cindex <union> | |
31881 | If a register's value is usefully viewed in multiple ways, define it | |
31882 | with a union type containing the useful representations. The | |
31883 | @samp{<union>} element contains one or more @samp{<field>} elements, | |
31884 | each of which has a @var{name} and a @var{type}: | |
31885 | ||
31886 | @smallexample | |
31887 | <union id="@var{id}"> | |
31888 | <field name="@var{name}" type="@var{type}"/> | |
31889 | @dots{} | |
31890 | </union> | |
31891 | @end smallexample | |
31892 | ||
31893 | @subsection Registers | |
31894 | @cindex <reg> | |
31895 | ||
31896 | Each register is represented as an element with this form: | |
31897 | ||
31898 | @smallexample | |
31899 | <reg name="@var{name}" | |
31900 | bitsize="@var{size}" | |
31901 | @r{[}regnum="@var{num}"@r{]} | |
31902 | @r{[}save-restore="@var{save-restore}"@r{]} | |
31903 | @r{[}type="@var{type}"@r{]} | |
31904 | @r{[}group="@var{group}"@r{]}/> | |
31905 | @end smallexample | |
31906 | ||
31907 | @noindent | |
31908 | The components are as follows: | |
31909 | ||
31910 | @table @var | |
31911 | ||
31912 | @item name | |
31913 | The register's name; it must be unique within the target description. | |
31914 | ||
31915 | @item bitsize | |
31916 | The register's size, in bits. | |
31917 | ||
31918 | @item regnum | |
31919 | The register's number. If omitted, a register's number is one greater | |
31920 | than that of the previous register (either in the current feature or in | |
31921 | a preceeding feature); the first register in the target description | |
31922 | defaults to zero. This register number is used to read or write | |
31923 | the register; e.g.@: it is used in the remote @code{p} and @code{P} | |
31924 | packets, and registers appear in the @code{g} and @code{G} packets | |
31925 | in order of increasing register number. | |
31926 | ||
31927 | @item save-restore | |
31928 | Whether the register should be preserved across inferior function | |
31929 | calls; this must be either @code{yes} or @code{no}. The default is | |
31930 | @code{yes}, which is appropriate for most registers except for | |
31931 | some system control registers; this is not related to the target's | |
31932 | ABI. | |
31933 | ||
31934 | @item type | |
31935 | The type of the register. @var{type} may be a predefined type, a type | |
31936 | defined in the current feature, or one of the special types @code{int} | |
31937 | and @code{float}. @code{int} is an integer type of the correct size | |
31938 | for @var{bitsize}, and @code{float} is a floating point type (in the | |
31939 | architecture's normal floating point format) of the correct size for | |
31940 | @var{bitsize}. The default is @code{int}. | |
31941 | ||
31942 | @item group | |
31943 | The register group to which this register belongs. @var{group} must | |
31944 | be either @code{general}, @code{float}, or @code{vector}. If no | |
31945 | @var{group} is specified, @value{GDBN} will not display the register | |
31946 | in @code{info registers}. | |
31947 | ||
31948 | @end table | |
31949 | ||
31950 | @node Predefined Target Types | |
31951 | @section Predefined Target Types | |
31952 | @cindex target descriptions, predefined types | |
31953 | ||
31954 | Type definitions in the self-description can build up composite types | |
31955 | from basic building blocks, but can not define fundamental types. Instead, | |
31956 | standard identifiers are provided by @value{GDBN} for the fundamental | |
31957 | types. The currently supported types are: | |
31958 | ||
31959 | @table @code | |
31960 | ||
31961 | @item int8 | |
31962 | @itemx int16 | |
31963 | @itemx int32 | |
31964 | @itemx int64 | |
7cc46491 | 31965 | @itemx int128 |
123dc839 DJ |
31966 | Signed integer types holding the specified number of bits. |
31967 | ||
31968 | @item uint8 | |
31969 | @itemx uint16 | |
31970 | @itemx uint32 | |
31971 | @itemx uint64 | |
7cc46491 | 31972 | @itemx uint128 |
123dc839 DJ |
31973 | Unsigned integer types holding the specified number of bits. |
31974 | ||
31975 | @item code_ptr | |
31976 | @itemx data_ptr | |
31977 | Pointers to unspecified code and data. The program counter and | |
31978 | any dedicated return address register may be marked as code | |
31979 | pointers; printing a code pointer converts it into a symbolic | |
31980 | address. The stack pointer and any dedicated address registers | |
31981 | may be marked as data pointers. | |
31982 | ||
6e3bbd1a PB |
31983 | @item ieee_single |
31984 | Single precision IEEE floating point. | |
31985 | ||
31986 | @item ieee_double | |
31987 | Double precision IEEE floating point. | |
31988 | ||
123dc839 DJ |
31989 | @item arm_fpa_ext |
31990 | The 12-byte extended precision format used by ARM FPA registers. | |
31991 | ||
31992 | @end table | |
31993 | ||
31994 | @node Standard Target Features | |
31995 | @section Standard Target Features | |
31996 | @cindex target descriptions, standard features | |
31997 | ||
31998 | A target description must contain either no registers or all the | |
31999 | target's registers. If the description contains no registers, then | |
32000 | @value{GDBN} will assume a default register layout, selected based on | |
32001 | the architecture. If the description contains any registers, the | |
32002 | default layout will not be used; the standard registers must be | |
32003 | described in the target description, in such a way that @value{GDBN} | |
32004 | can recognize them. | |
32005 | ||
32006 | This is accomplished by giving specific names to feature elements | |
32007 | which contain standard registers. @value{GDBN} will look for features | |
32008 | with those names and verify that they contain the expected registers; | |
32009 | if any known feature is missing required registers, or if any required | |
32010 | feature is missing, @value{GDBN} will reject the target | |
32011 | description. You can add additional registers to any of the | |
32012 | standard features --- @value{GDBN} will display them just as if | |
32013 | they were added to an unrecognized feature. | |
32014 | ||
32015 | This section lists the known features and their expected contents. | |
32016 | Sample XML documents for these features are included in the | |
32017 | @value{GDBN} source tree, in the directory @file{gdb/features}. | |
32018 | ||
32019 | Names recognized by @value{GDBN} should include the name of the | |
32020 | company or organization which selected the name, and the overall | |
32021 | architecture to which the feature applies; so e.g.@: the feature | |
32022 | containing ARM core registers is named @samp{org.gnu.gdb.arm.core}. | |
32023 | ||
ff6f572f DJ |
32024 | The names of registers are not case sensitive for the purpose |
32025 | of recognizing standard features, but @value{GDBN} will only display | |
32026 | registers using the capitalization used in the description. | |
32027 | ||
e9c17194 VP |
32028 | @menu |
32029 | * ARM Features:: | |
1e26b4f8 | 32030 | * MIPS Features:: |
e9c17194 | 32031 | * M68K Features:: |
1e26b4f8 | 32032 | * PowerPC Features:: |
e9c17194 VP |
32033 | @end menu |
32034 | ||
32035 | ||
32036 | @node ARM Features | |
123dc839 DJ |
32037 | @subsection ARM Features |
32038 | @cindex target descriptions, ARM features | |
32039 | ||
32040 | The @samp{org.gnu.gdb.arm.core} feature is required for ARM targets. | |
32041 | It should contain registers @samp{r0} through @samp{r13}, @samp{sp}, | |
32042 | @samp{lr}, @samp{pc}, and @samp{cpsr}. | |
32043 | ||
32044 | The @samp{org.gnu.gdb.arm.fpa} feature is optional. If present, it | |
32045 | should contain registers @samp{f0} through @samp{f7} and @samp{fps}. | |
32046 | ||
ff6f572f DJ |
32047 | The @samp{org.gnu.gdb.xscale.iwmmxt} feature is optional. If present, |
32048 | it should contain at least registers @samp{wR0} through @samp{wR15} and | |
32049 | @samp{wCGR0} through @samp{wCGR3}. The @samp{wCID}, @samp{wCon}, | |
32050 | @samp{wCSSF}, and @samp{wCASF} registers are optional. | |
23181151 | 32051 | |
58d6951d DJ |
32052 | The @samp{org.gnu.gdb.arm.vfp} feature is optional. If present, it |
32053 | should contain at least registers @samp{d0} through @samp{d15}. If | |
32054 | they are present, @samp{d16} through @samp{d31} should also be included. | |
32055 | @value{GDBN} will synthesize the single-precision registers from | |
32056 | halves of the double-precision registers. | |
32057 | ||
32058 | The @samp{org.gnu.gdb.arm.neon} feature is optional. It does not | |
32059 | need to contain registers; it instructs @value{GDBN} to display the | |
32060 | VFP double-precision registers as vectors and to synthesize the | |
32061 | quad-precision registers from pairs of double-precision registers. | |
32062 | If this feature is present, @samp{org.gnu.gdb.arm.vfp} must also | |
32063 | be present and include 32 double-precision registers. | |
32064 | ||
1e26b4f8 | 32065 | @node MIPS Features |
f8b73d13 DJ |
32066 | @subsection MIPS Features |
32067 | @cindex target descriptions, MIPS features | |
32068 | ||
32069 | The @samp{org.gnu.gdb.mips.cpu} feature is required for MIPS targets. | |
32070 | It should contain registers @samp{r0} through @samp{r31}, @samp{lo}, | |
32071 | @samp{hi}, and @samp{pc}. They may be 32-bit or 64-bit depending | |
32072 | on the target. | |
32073 | ||
32074 | The @samp{org.gnu.gdb.mips.cp0} feature is also required. It should | |
32075 | contain at least the @samp{status}, @samp{badvaddr}, and @samp{cause} | |
32076 | registers. They may be 32-bit or 64-bit depending on the target. | |
32077 | ||
32078 | The @samp{org.gnu.gdb.mips.fpu} feature is currently required, though | |
32079 | it may be optional in a future version of @value{GDBN}. It should | |
32080 | contain registers @samp{f0} through @samp{f31}, @samp{fcsr}, and | |
32081 | @samp{fir}. They may be 32-bit or 64-bit depending on the target. | |
32082 | ||
822b6570 DJ |
32083 | The @samp{org.gnu.gdb.mips.linux} feature is optional. It should |
32084 | contain a single register, @samp{restart}, which is used by the | |
32085 | Linux kernel to control restartable syscalls. | |
32086 | ||
e9c17194 VP |
32087 | @node M68K Features |
32088 | @subsection M68K Features | |
32089 | @cindex target descriptions, M68K features | |
32090 | ||
32091 | @table @code | |
32092 | @item @samp{org.gnu.gdb.m68k.core} | |
32093 | @itemx @samp{org.gnu.gdb.coldfire.core} | |
32094 | @itemx @samp{org.gnu.gdb.fido.core} | |
32095 | One of those features must be always present. | |
249e1128 | 32096 | The feature that is present determines which flavor of m68k is |
e9c17194 VP |
32097 | used. The feature that is present should contain registers |
32098 | @samp{d0} through @samp{d7}, @samp{a0} through @samp{a5}, @samp{fp}, | |
32099 | @samp{sp}, @samp{ps} and @samp{pc}. | |
32100 | ||
32101 | @item @samp{org.gnu.gdb.coldfire.fp} | |
32102 | This feature is optional. If present, it should contain registers | |
32103 | @samp{fp0} through @samp{fp7}, @samp{fpcontrol}, @samp{fpstatus} and | |
32104 | @samp{fpiaddr}. | |
32105 | @end table | |
32106 | ||
1e26b4f8 | 32107 | @node PowerPC Features |
7cc46491 DJ |
32108 | @subsection PowerPC Features |
32109 | @cindex target descriptions, PowerPC features | |
32110 | ||
32111 | The @samp{org.gnu.gdb.power.core} feature is required for PowerPC | |
32112 | targets. It should contain registers @samp{r0} through @samp{r31}, | |
32113 | @samp{pc}, @samp{msr}, @samp{cr}, @samp{lr}, @samp{ctr}, and | |
32114 | @samp{xer}. They may be 32-bit or 64-bit depending on the target. | |
32115 | ||
32116 | The @samp{org.gnu.gdb.power.fpu} feature is optional. It should | |
32117 | contain registers @samp{f0} through @samp{f31} and @samp{fpscr}. | |
32118 | ||
32119 | The @samp{org.gnu.gdb.power.altivec} feature is optional. It should | |
32120 | contain registers @samp{vr0} through @samp{vr31}, @samp{vscr}, | |
32121 | and @samp{vrsave}. | |
32122 | ||
677c5bb1 LM |
32123 | The @samp{org.gnu.gdb.power.vsx} feature is optional. It should |
32124 | contain registers @samp{vs0h} through @samp{vs31h}. @value{GDBN} | |
32125 | will combine these registers with the floating point registers | |
32126 | (@samp{f0} through @samp{f31}) and the altivec registers (@samp{vr0} | |
aeac0ff9 | 32127 | through @samp{vr31}) to present the 128-bit wide registers @samp{vs0} |
677c5bb1 LM |
32128 | through @samp{vs63}, the set of vector registers for POWER7. |
32129 | ||
7cc46491 DJ |
32130 | The @samp{org.gnu.gdb.power.spe} feature is optional. It should |
32131 | contain registers @samp{ev0h} through @samp{ev31h}, @samp{acc}, and | |
32132 | @samp{spefscr}. SPE targets should provide 32-bit registers in | |
32133 | @samp{org.gnu.gdb.power.core} and provide the upper halves in | |
32134 | @samp{ev0h} through @samp{ev31h}. @value{GDBN} will combine | |
32135 | these to present registers @samp{ev0} through @samp{ev31} to the | |
32136 | user. | |
32137 | ||
07e059b5 VP |
32138 | @node Operating System Information |
32139 | @appendix Operating System Information | |
32140 | @cindex operating system information | |
32141 | ||
32142 | @menu | |
32143 | * Process list:: | |
32144 | @end menu | |
32145 | ||
32146 | Users of @value{GDBN} often wish to obtain information about the state of | |
32147 | the operating system running on the target---for example the list of | |
32148 | processes, or the list of open files. This section describes the | |
32149 | mechanism that makes it possible. This mechanism is similar to the | |
32150 | target features mechanism (@pxref{Target Descriptions}), but focuses | |
32151 | on a different aspect of target. | |
32152 | ||
32153 | Operating system information is retrived from the target via the | |
32154 | remote protocol, using @samp{qXfer} requests (@pxref{qXfer osdata | |
32155 | read}). The object name in the request should be @samp{osdata}, and | |
32156 | the @var{annex} identifies the data to be fetched. | |
32157 | ||
32158 | @node Process list | |
32159 | @appendixsection Process list | |
32160 | @cindex operating system information, process list | |
32161 | ||
32162 | When requesting the process list, the @var{annex} field in the | |
32163 | @samp{qXfer} request should be @samp{processes}. The returned data is | |
32164 | an XML document. The formal syntax of this document is defined in | |
32165 | @file{gdb/features/osdata.dtd}. | |
32166 | ||
32167 | An example document is: | |
32168 | ||
32169 | @smallexample | |
32170 | <?xml version="1.0"?> | |
32171 | <!DOCTYPE target SYSTEM "osdata.dtd"> | |
32172 | <osdata type="processes"> | |
32173 | <item> | |
32174 | <column name="pid">1</column> | |
32175 | <column name="user">root</column> | |
32176 | <column name="command">/sbin/init</column> | |
32177 | </item> | |
32178 | </osdata> | |
32179 | @end smallexample | |
32180 | ||
32181 | Each item should include a column whose name is @samp{pid}. The value | |
32182 | of that column should identify the process on the target. The | |
32183 | @samp{user} and @samp{command} columns are optional, and will be | |
32184 | displayed by @value{GDBN}. Target may provide additional columns, | |
32185 | which @value{GDBN} currently ignores. | |
32186 | ||
aab4e0ec | 32187 | @include gpl.texi |
eb12ee30 | 32188 | |
2154891a | 32189 | @raisesections |
6826cf00 | 32190 | @include fdl.texi |
2154891a | 32191 | @lowersections |
6826cf00 | 32192 | |
6d2ebf8b | 32193 | @node Index |
c906108c SS |
32194 | @unnumbered Index |
32195 | ||
32196 | @printindex cp | |
32197 | ||
32198 | @tex | |
32199 | % I think something like @colophon should be in texinfo. In the | |
32200 | % meantime: | |
32201 | \long\def\colophon{\hbox to0pt{}\vfill | |
32202 | \centerline{The body of this manual is set in} | |
32203 | \centerline{\fontname\tenrm,} | |
32204 | \centerline{with headings in {\bf\fontname\tenbf}} | |
32205 | \centerline{and examples in {\tt\fontname\tentt}.} | |
32206 | \centerline{{\it\fontname\tenit\/},} | |
32207 | \centerline{{\bf\fontname\tenbf}, and} | |
32208 | \centerline{{\sl\fontname\tensl\/}} | |
32209 | \centerline{are used for emphasis.}\vfill} | |
32210 | \page\colophon | |
32211 | % Blame: doc@cygnus.com, 1991. | |
32212 | @end tex | |
32213 | ||
c906108c | 32214 | @bye |