Commit | Line | Data |
---|---|---|
c906108c | 1 | \input texinfo @c -*-texinfo-*- |
c02a867d | 2 | @c Copyright (C) 1988, 1989, 1990, 1991, 1992, 1993, 1994, 1995, 1996, 1998, |
9d2897ad | 3 | @c 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010 |
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, | |
9d2897ad | 49 | 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009, 2010 |
a67ec3f4 | 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 | |
9d2897ad | 123 | Copyright (C) 1988-2010 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 | |
00bf0b85 | 177 | * Trace File Format:: GDB trace file format |
aab4e0ec AC |
178 | * Copying:: GNU General Public License says |
179 | how you can copy and share GDB | |
6826cf00 | 180 | * GNU Free Documentation License:: The license for this documentation |
6d2ebf8b SS |
181 | * Index:: Index |
182 | @end menu | |
183 | ||
6c0e9fb3 | 184 | @end ifnottex |
c906108c | 185 | |
449f3b6c | 186 | @contents |
449f3b6c | 187 | |
6d2ebf8b | 188 | @node Summary |
c906108c SS |
189 | @unnumbered Summary of @value{GDBN} |
190 | ||
191 | The purpose of a debugger such as @value{GDBN} is to allow you to see what is | |
192 | going on ``inside'' another program while it executes---or what another | |
193 | program was doing at the moment it crashed. | |
194 | ||
195 | @value{GDBN} can do four main kinds of things (plus other things in support of | |
196 | these) to help you catch bugs in the act: | |
197 | ||
198 | @itemize @bullet | |
199 | @item | |
200 | Start your program, specifying anything that might affect its behavior. | |
201 | ||
202 | @item | |
203 | Make your program stop on specified conditions. | |
204 | ||
205 | @item | |
206 | Examine what has happened, when your program has stopped. | |
207 | ||
208 | @item | |
209 | Change things in your program, so you can experiment with correcting the | |
210 | effects of one bug and go on to learn about another. | |
211 | @end itemize | |
212 | ||
49efadf5 | 213 | You can use @value{GDBN} to debug programs written in C and C@t{++}. |
79a6e687 | 214 | For more information, see @ref{Supported Languages,,Supported Languages}. |
c906108c SS |
215 | For more information, see @ref{C,,C and C++}. |
216 | ||
cce74817 | 217 | @cindex Modula-2 |
e632838e AC |
218 | Support for Modula-2 is partial. For information on Modula-2, see |
219 | @ref{Modula-2,,Modula-2}. | |
c906108c | 220 | |
cce74817 JM |
221 | @cindex Pascal |
222 | Debugging Pascal programs which use sets, subranges, file variables, or | |
223 | nested functions does not currently work. @value{GDBN} does not support | |
224 | entering expressions, printing values, or similar features using Pascal | |
225 | syntax. | |
c906108c | 226 | |
c906108c SS |
227 | @cindex Fortran |
228 | @value{GDBN} can be used to debug programs written in Fortran, although | |
53a5351d | 229 | it may be necessary to refer to some variables with a trailing |
cce74817 | 230 | underscore. |
c906108c | 231 | |
b37303ee AF |
232 | @value{GDBN} can be used to debug programs written in Objective-C, |
233 | using either the Apple/NeXT or the GNU Objective-C runtime. | |
234 | ||
c906108c SS |
235 | @menu |
236 | * Free Software:: Freely redistributable software | |
237 | * Contributors:: Contributors to GDB | |
238 | @end menu | |
239 | ||
6d2ebf8b | 240 | @node Free Software |
79a6e687 | 241 | @unnumberedsec Free Software |
c906108c | 242 | |
5d161b24 | 243 | @value{GDBN} is @dfn{free software}, protected by the @sc{gnu} |
c906108c SS |
244 | General Public License |
245 | (GPL). The GPL gives you the freedom to copy or adapt a licensed | |
246 | program---but every person getting a copy also gets with it the | |
247 | freedom to modify that copy (which means that they must get access to | |
248 | the source code), and the freedom to distribute further copies. | |
249 | Typical software companies use copyrights to limit your freedoms; the | |
250 | Free Software Foundation uses the GPL to preserve these freedoms. | |
251 | ||
252 | Fundamentally, the General Public License is a license which says that | |
253 | you have these freedoms and that you cannot take these freedoms away | |
254 | from anyone else. | |
255 | ||
2666264b | 256 | @unnumberedsec Free Software Needs Free Documentation |
959acfd1 EZ |
257 | |
258 | The biggest deficiency in the free software community today is not in | |
259 | the software---it is the lack of good free documentation that we can | |
260 | include with the free software. Many of our most important | |
261 | programs do not come with free reference manuals and free introductory | |
262 | texts. Documentation is an essential part of any software package; | |
263 | when an important free software package does not come with a free | |
264 | manual and a free tutorial, that is a major gap. We have many such | |
265 | gaps today. | |
266 | ||
267 | Consider Perl, for instance. The tutorial manuals that people | |
268 | normally use are non-free. How did this come about? Because the | |
269 | authors of those manuals published them with restrictive terms---no | |
270 | copying, no modification, source files not available---which exclude | |
271 | them from the free software world. | |
272 | ||
273 | That wasn't the first time this sort of thing happened, and it was far | |
274 | from the last. Many times we have heard a GNU user eagerly describe a | |
275 | manual that he is writing, his intended contribution to the community, | |
276 | only to learn that he had ruined everything by signing a publication | |
277 | contract to make it non-free. | |
278 | ||
279 | Free documentation, like free software, is a matter of freedom, not | |
280 | price. The problem with the non-free manual is not that publishers | |
281 | charge a price for printed copies---that in itself is fine. (The Free | |
282 | Software Foundation sells printed copies of manuals, too.) The | |
283 | problem is the restrictions on the use of the manual. Free manuals | |
284 | are available in source code form, and give you permission to copy and | |
285 | modify. Non-free manuals do not allow this. | |
286 | ||
287 | The criteria of freedom for a free manual are roughly the same as for | |
288 | free software. Redistribution (including the normal kinds of | |
289 | commercial redistribution) must be permitted, so that the manual can | |
290 | accompany every copy of the program, both on-line and on paper. | |
291 | ||
292 | Permission for modification of the technical content is crucial too. | |
293 | When people modify the software, adding or changing features, if they | |
294 | are conscientious they will change the manual too---so they can | |
295 | provide accurate and clear documentation for the modified program. A | |
296 | manual that leaves you no choice but to write a new manual to document | |
297 | a changed version of the program is not really available to our | |
298 | community. | |
299 | ||
300 | Some kinds of limits on the way modification is handled are | |
301 | acceptable. For example, requirements to preserve the original | |
302 | author's copyright notice, the distribution terms, or the list of | |
303 | authors, are ok. It is also no problem to require modified versions | |
304 | to include notice that they were modified. Even entire sections that | |
305 | may not be deleted or changed are acceptable, as long as they deal | |
306 | with nontechnical topics (like this one). These kinds of restrictions | |
307 | are acceptable because they don't obstruct the community's normal use | |
308 | of the manual. | |
309 | ||
310 | However, it must be possible to modify all the @emph{technical} | |
311 | content of the manual, and then distribute the result in all the usual | |
312 | media, through all the usual channels. Otherwise, the restrictions | |
313 | obstruct the use of the manual, it is not free, and we need another | |
314 | manual to replace it. | |
315 | ||
316 | Please spread the word about this issue. Our community continues to | |
317 | lose manuals to proprietary publishing. If we spread the word that | |
318 | free software needs free reference manuals and free tutorials, perhaps | |
319 | the next person who wants to contribute by writing documentation will | |
320 | realize, before it is too late, that only free manuals contribute to | |
321 | the free software community. | |
322 | ||
323 | If you are writing documentation, please insist on publishing it under | |
324 | the GNU Free Documentation License or another free documentation | |
325 | license. Remember that this decision requires your approval---you | |
326 | don't have to let the publisher decide. Some commercial publishers | |
327 | will use a free license if you insist, but they will not propose the | |
328 | option; it is up to you to raise the issue and say firmly that this is | |
329 | what you want. If the publisher you are dealing with refuses, please | |
330 | try other publishers. If you're not sure whether a proposed license | |
42584a72 | 331 | is free, write to @email{licensing@@gnu.org}. |
959acfd1 EZ |
332 | |
333 | You can encourage commercial publishers to sell more free, copylefted | |
334 | manuals and tutorials by buying them, and particularly by buying | |
335 | copies from the publishers that paid for their writing or for major | |
336 | improvements. Meanwhile, try to avoid buying non-free documentation | |
337 | at all. Check the distribution terms of a manual before you buy it, | |
338 | and insist that whoever seeks your business must respect your freedom. | |
72c9928d EZ |
339 | Check the history of the book, and try to reward the publishers that |
340 | have paid or pay the authors to work on it. | |
959acfd1 EZ |
341 | |
342 | The Free Software Foundation maintains a list of free documentation | |
343 | published by other publishers, at | |
344 | @url{http://www.fsf.org/doc/other-free-books.html}. | |
345 | ||
6d2ebf8b | 346 | @node Contributors |
96a2c332 SS |
347 | @unnumberedsec Contributors to @value{GDBN} |
348 | ||
349 | Richard Stallman was the original author of @value{GDBN}, and of many | |
350 | other @sc{gnu} programs. Many others have contributed to its | |
351 | development. This section attempts to credit major contributors. One | |
352 | of the virtues of free software is that everyone is free to contribute | |
353 | to it; with regret, we cannot actually acknowledge everyone here. The | |
354 | file @file{ChangeLog} in the @value{GDBN} distribution approximates a | |
c906108c SS |
355 | blow-by-blow account. |
356 | ||
357 | Changes much prior to version 2.0 are lost in the mists of time. | |
358 | ||
359 | @quotation | |
360 | @emph{Plea:} Additions to this section are particularly welcome. If you | |
361 | or your friends (or enemies, to be evenhanded) have been unfairly | |
362 | omitted from this list, we would like to add your names! | |
363 | @end quotation | |
364 | ||
365 | So that they may not regard their many labors as thankless, we | |
366 | particularly thank those who shepherded @value{GDBN} through major | |
367 | releases: | |
7ba3cf9c | 368 | Andrew Cagney (releases 6.3, 6.2, 6.1, 6.0, 5.3, 5.2, 5.1 and 5.0); |
c906108c SS |
369 | Jim Blandy (release 4.18); |
370 | Jason Molenda (release 4.17); | |
371 | Stan Shebs (release 4.14); | |
372 | Fred Fish (releases 4.16, 4.15, 4.13, 4.12, 4.11, 4.10, and 4.9); | |
373 | Stu Grossman and John Gilmore (releases 4.8, 4.7, 4.6, 4.5, and 4.4); | |
374 | John Gilmore (releases 4.3, 4.2, 4.1, 4.0, and 3.9); | |
375 | Jim Kingdon (releases 3.5, 3.4, and 3.3); | |
376 | and Randy Smith (releases 3.2, 3.1, and 3.0). | |
377 | ||
378 | Richard Stallman, assisted at various times by Peter TerMaat, Chris | |
379 | Hanson, and Richard Mlynarik, handled releases through 2.8. | |
380 | ||
b37052ae EZ |
381 | Michael Tiemann is the author of most of the @sc{gnu} C@t{++} support |
382 | in @value{GDBN}, with significant additional contributions from Per | |
383 | Bothner and Daniel Berlin. James Clark wrote the @sc{gnu} C@t{++} | |
384 | demangler. Early work on C@t{++} was by Peter TerMaat (who also did | |
385 | much general update work leading to release 3.0). | |
c906108c | 386 | |
b37052ae | 387 | @value{GDBN} uses the BFD subroutine library to examine multiple |
c906108c SS |
388 | object-file formats; BFD was a joint project of David V. |
389 | Henkel-Wallace, Rich Pixley, Steve Chamberlain, and John Gilmore. | |
390 | ||
391 | David Johnson wrote the original COFF support; Pace Willison did | |
392 | the original support for encapsulated COFF. | |
393 | ||
0179ffac | 394 | Brent Benson of Harris Computer Systems contributed DWARF 2 support. |
c906108c SS |
395 | |
396 | Adam de Boor and Bradley Davis contributed the ISI Optimum V support. | |
397 | Per Bothner, Noboyuki Hikichi, and Alessandro Forin contributed MIPS | |
398 | support. | |
399 | Jean-Daniel Fekete contributed Sun 386i support. | |
400 | Chris Hanson improved the HP9000 support. | |
401 | Noboyuki Hikichi and Tomoyuki Hasei contributed Sony/News OS 3 support. | |
402 | David Johnson contributed Encore Umax support. | |
403 | Jyrki Kuoppala contributed Altos 3068 support. | |
404 | Jeff Law contributed HP PA and SOM support. | |
405 | Keith Packard contributed NS32K support. | |
406 | Doug Rabson contributed Acorn Risc Machine support. | |
407 | Bob Rusk contributed Harris Nighthawk CX-UX support. | |
408 | Chris Smith contributed Convex support (and Fortran debugging). | |
409 | Jonathan Stone contributed Pyramid support. | |
410 | Michael Tiemann contributed SPARC support. | |
411 | Tim Tucker contributed support for the Gould NP1 and Gould Powernode. | |
412 | Pace Willison contributed Intel 386 support. | |
413 | Jay Vosburgh contributed Symmetry support. | |
a37295f9 | 414 | Marko Mlinar contributed OpenRISC 1000 support. |
c906108c | 415 | |
1104b9e7 | 416 | Andreas Schwab contributed M68K @sc{gnu}/Linux support. |
c906108c SS |
417 | |
418 | Rich Schaefer and Peter Schauer helped with support of SunOS shared | |
419 | libraries. | |
420 | ||
421 | Jay Fenlason and Roland McGrath ensured that @value{GDBN} and GAS agree | |
422 | about several machine instruction sets. | |
423 | ||
424 | Patrick Duval, Ted Goldstein, Vikram Koka and Glenn Engel helped develop | |
425 | remote debugging. Intel Corporation, Wind River Systems, AMD, and ARM | |
426 | contributed remote debugging modules for the i960, VxWorks, A29K UDI, | |
427 | and RDI targets, respectively. | |
428 | ||
429 | Brian Fox is the author of the readline libraries providing | |
430 | command-line editing and command history. | |
431 | ||
7a292a7a SS |
432 | Andrew Beers of SUNY Buffalo wrote the language-switching code, the |
433 | Modula-2 support, and contributed the Languages chapter of this manual. | |
c906108c | 434 | |
5d161b24 | 435 | Fred Fish wrote most of the support for Unix System Vr4. |
b37052ae | 436 | He also enhanced the command-completion support to cover C@t{++} overloaded |
c906108c | 437 | symbols. |
c906108c | 438 | |
f24c5e49 KI |
439 | Hitachi America (now Renesas America), Ltd. sponsored the support for |
440 | H8/300, H8/500, and Super-H processors. | |
c906108c SS |
441 | |
442 | NEC sponsored the support for the v850, Vr4xxx, and Vr5xxx processors. | |
443 | ||
f24c5e49 KI |
444 | Mitsubishi (now Renesas) sponsored the support for D10V, D30V, and M32R/D |
445 | processors. | |
c906108c SS |
446 | |
447 | Toshiba sponsored the support for the TX39 Mips processor. | |
448 | ||
449 | Matsushita sponsored the support for the MN10200 and MN10300 processors. | |
450 | ||
96a2c332 | 451 | Fujitsu sponsored the support for SPARClite and FR30 processors. |
c906108c SS |
452 | |
453 | Kung Hsu, Jeff Law, and Rick Sladkey added support for hardware | |
454 | watchpoints. | |
455 | ||
456 | Michael Snyder added support for tracepoints. | |
457 | ||
458 | Stu Grossman wrote gdbserver. | |
459 | ||
460 | Jim Kingdon, Peter Schauer, Ian Taylor, and Stu Grossman made | |
96a2c332 | 461 | nearly innumerable bug fixes and cleanups throughout @value{GDBN}. |
c906108c SS |
462 | |
463 | The following people at the Hewlett-Packard Company contributed | |
464 | support for the PA-RISC 2.0 architecture, HP-UX 10.20, 10.30, and 11.0 | |
b37052ae | 465 | (narrow mode), HP's implementation of kernel threads, HP's aC@t{++} |
d0d5df6f AC |
466 | compiler, and the Text User Interface (nee Terminal User Interface): |
467 | Ben Krepp, Richard Title, John Bishop, Susan Macchia, Kathy Mann, | |
468 | Satish Pai, India Paul, Steve Rehrauer, and Elena Zannoni. Kim Haase | |
469 | provided HP-specific information in this manual. | |
c906108c | 470 | |
b37052ae EZ |
471 | DJ Delorie ported @value{GDBN} to MS-DOS, for the DJGPP project. |
472 | Robert Hoehne made significant contributions to the DJGPP port. | |
473 | ||
96a2c332 SS |
474 | Cygnus Solutions has sponsored @value{GDBN} maintenance and much of its |
475 | development since 1991. Cygnus engineers who have worked on @value{GDBN} | |
2df3850c JM |
476 | fulltime include Mark Alexander, Jim Blandy, Per Bothner, Kevin |
477 | Buettner, Edith Epstein, Chris Faylor, Fred Fish, Martin Hunt, Jim | |
478 | Ingham, John Gilmore, Stu Grossman, Kung Hsu, Jim Kingdon, John Metzler, | |
479 | Fernando Nasser, Geoffrey Noer, Dawn Perchik, Rich Pixley, Zdenek | |
480 | Radouch, Keith Seitz, Stan Shebs, David Taylor, and Elena Zannoni. In | |
481 | addition, Dave Brolley, Ian Carmichael, Steve Chamberlain, Nick Clifton, | |
482 | JT Conklin, Stan Cox, DJ Delorie, Ulrich Drepper, Frank Eigler, Doug | |
483 | Evans, Sean Fagan, David Henkel-Wallace, Richard Henderson, Jeff | |
484 | Holcomb, Jeff Law, Jim Lemke, Tom Lord, Bob Manson, Michael Meissner, | |
485 | Jason Merrill, Catherine Moore, Drew Moseley, Ken Raeburn, Gavin | |
486 | Romig-Koch, Rob Savoye, Jamie Smith, Mike Stump, Ian Taylor, Angela | |
487 | Thomas, Michael Tiemann, Tom Tromey, Ron Unrau, Jim Wilson, and David | |
488 | Zuhn have made contributions both large and small. | |
c906108c | 489 | |
ffed4509 AC |
490 | Andrew Cagney, Fernando Nasser, and Elena Zannoni, while working for |
491 | Cygnus Solutions, implemented the original @sc{gdb/mi} interface. | |
492 | ||
e2e0bcd1 JB |
493 | Jim Blandy added support for preprocessor macros, while working for Red |
494 | Hat. | |
c906108c | 495 | |
a9967aef AC |
496 | Andrew Cagney designed @value{GDBN}'s architecture vector. Many |
497 | people including Andrew Cagney, Stephane Carrez, Randolph Chung, Nick | |
498 | Duffek, Richard Henderson, Mark Kettenis, Grace Sainsbury, Kei | |
499 | Sakamoto, Yoshinori Sato, Michael Snyder, Andreas Schwab, Jason | |
500 | Thorpe, Corinna Vinschen, Ulrich Weigand, and Elena Zannoni, helped | |
501 | with the migration of old architectures to this new framework. | |
502 | ||
c5e30d01 AC |
503 | Andrew Cagney completely re-designed and re-implemented @value{GDBN}'s |
504 | unwinder framework, this consisting of a fresh new design featuring | |
505 | frame IDs, independent frame sniffers, and the sentinel frame. Mark | |
506 | Kettenis implemented the @sc{dwarf 2} unwinder, Jeff Johnston the | |
507 | libunwind unwinder, and Andrew Cagney the dummy, sentinel, tramp, and | |
db2e3e2e | 508 | trad unwinders. The architecture-specific changes, each involving a |
c5e30d01 AC |
509 | complete rewrite of the architecture's frame code, were carried out by |
510 | Jim Blandy, Joel Brobecker, Kevin Buettner, Andrew Cagney, Stephane | |
511 | Carrez, Randolph Chung, Orjan Friberg, Richard Henderson, Daniel | |
512 | Jacobowitz, Jeff Johnston, Mark Kettenis, Theodore A. Roth, Kei | |
513 | Sakamoto, Yoshinori Sato, Michael Snyder, Corinna Vinschen, and Ulrich | |
514 | Weigand. | |
515 | ||
ca3bf3bd DJ |
516 | Christian Zankel, Ross Morley, Bob Wilson, and Maxim Grigoriev from |
517 | Tensilica, Inc.@: contributed support for Xtensa processors. Others | |
518 | who have worked on the Xtensa port of @value{GDBN} in the past include | |
519 | Steve Tjiang, John Newlin, and Scott Foehner. | |
520 | ||
08be9d71 ME |
521 | Michael Eager and staff of Xilinx, Inc., contributed support for the |
522 | Xilinx MicroBlaze architecture. | |
523 | ||
6d2ebf8b | 524 | @node Sample Session |
c906108c SS |
525 | @chapter A Sample @value{GDBN} Session |
526 | ||
527 | You can use this manual at your leisure to read all about @value{GDBN}. | |
528 | However, a handful of commands are enough to get started using the | |
529 | debugger. This chapter illustrates those commands. | |
530 | ||
531 | @iftex | |
532 | In this sample session, we emphasize user input like this: @b{input}, | |
533 | to make it easier to pick out from the surrounding output. | |
534 | @end iftex | |
535 | ||
536 | @c FIXME: this example may not be appropriate for some configs, where | |
537 | @c FIXME...primary interest is in remote use. | |
538 | ||
539 | One of the preliminary versions of @sc{gnu} @code{m4} (a generic macro | |
540 | processor) exhibits the following bug: sometimes, when we change its | |
541 | quote strings from the default, the commands used to capture one macro | |
542 | definition within another stop working. In the following short @code{m4} | |
543 | session, we define a macro @code{foo} which expands to @code{0000}; we | |
544 | then use the @code{m4} built-in @code{defn} to define @code{bar} as the | |
545 | same thing. However, when we change the open quote string to | |
546 | @code{<QUOTE>} and the close quote string to @code{<UNQUOTE>}, the same | |
547 | procedure fails to define a new synonym @code{baz}: | |
548 | ||
549 | @smallexample | |
550 | $ @b{cd gnu/m4} | |
551 | $ @b{./m4} | |
552 | @b{define(foo,0000)} | |
553 | ||
554 | @b{foo} | |
555 | 0000 | |
556 | @b{define(bar,defn(`foo'))} | |
557 | ||
558 | @b{bar} | |
559 | 0000 | |
560 | @b{changequote(<QUOTE>,<UNQUOTE>)} | |
561 | ||
562 | @b{define(baz,defn(<QUOTE>foo<UNQUOTE>))} | |
563 | @b{baz} | |
c8aa23ab | 564 | @b{Ctrl-d} |
c906108c SS |
565 | m4: End of input: 0: fatal error: EOF in string |
566 | @end smallexample | |
567 | ||
568 | @noindent | |
569 | Let us use @value{GDBN} to try to see what is going on. | |
570 | ||
c906108c SS |
571 | @smallexample |
572 | $ @b{@value{GDBP} m4} | |
573 | @c FIXME: this falsifies the exact text played out, to permit smallbook | |
574 | @c FIXME... format to come out better. | |
575 | @value{GDBN} is free software and you are welcome to distribute copies | |
5d161b24 | 576 | of it under certain conditions; type "show copying" to see |
c906108c | 577 | the conditions. |
5d161b24 | 578 | There is absolutely no warranty for @value{GDBN}; type "show warranty" |
c906108c SS |
579 | for details. |
580 | ||
581 | @value{GDBN} @value{GDBVN}, Copyright 1999 Free Software Foundation, Inc... | |
582 | (@value{GDBP}) | |
583 | @end smallexample | |
c906108c SS |
584 | |
585 | @noindent | |
586 | @value{GDBN} reads only enough symbol data to know where to find the | |
587 | rest when needed; as a result, the first prompt comes up very quickly. | |
588 | We now tell @value{GDBN} to use a narrower display width than usual, so | |
589 | that examples fit in this manual. | |
590 | ||
591 | @smallexample | |
592 | (@value{GDBP}) @b{set width 70} | |
593 | @end smallexample | |
594 | ||
595 | @noindent | |
596 | We need to see how the @code{m4} built-in @code{changequote} works. | |
597 | Having looked at the source, we know the relevant subroutine is | |
598 | @code{m4_changequote}, so we set a breakpoint there with the @value{GDBN} | |
599 | @code{break} command. | |
600 | ||
601 | @smallexample | |
602 | (@value{GDBP}) @b{break m4_changequote} | |
603 | Breakpoint 1 at 0x62f4: file builtin.c, line 879. | |
604 | @end smallexample | |
605 | ||
606 | @noindent | |
607 | Using the @code{run} command, we start @code{m4} running under @value{GDBN} | |
608 | control; as long as control does not reach the @code{m4_changequote} | |
609 | subroutine, the program runs as usual: | |
610 | ||
611 | @smallexample | |
612 | (@value{GDBP}) @b{run} | |
613 | Starting program: /work/Editorial/gdb/gnu/m4/m4 | |
614 | @b{define(foo,0000)} | |
615 | ||
616 | @b{foo} | |
617 | 0000 | |
618 | @end smallexample | |
619 | ||
620 | @noindent | |
621 | To trigger the breakpoint, we call @code{changequote}. @value{GDBN} | |
622 | suspends execution of @code{m4}, displaying information about the | |
623 | context where it stops. | |
624 | ||
625 | @smallexample | |
626 | @b{changequote(<QUOTE>,<UNQUOTE>)} | |
627 | ||
5d161b24 | 628 | Breakpoint 1, m4_changequote (argc=3, argv=0x33c70) |
c906108c SS |
629 | at builtin.c:879 |
630 | 879 if (bad_argc(TOKEN_DATA_TEXT(argv[0]),argc,1,3)) | |
631 | @end smallexample | |
632 | ||
633 | @noindent | |
634 | Now we use the command @code{n} (@code{next}) to advance execution to | |
635 | the next line of the current function. | |
636 | ||
637 | @smallexample | |
638 | (@value{GDBP}) @b{n} | |
639 | 882 set_quotes((argc >= 2) ? TOKEN_DATA_TEXT(argv[1])\ | |
640 | : nil, | |
641 | @end smallexample | |
642 | ||
643 | @noindent | |
644 | @code{set_quotes} looks like a promising subroutine. We can go into it | |
645 | by using the command @code{s} (@code{step}) instead of @code{next}. | |
646 | @code{step} goes to the next line to be executed in @emph{any} | |
647 | subroutine, so it steps into @code{set_quotes}. | |
648 | ||
649 | @smallexample | |
650 | (@value{GDBP}) @b{s} | |
651 | set_quotes (lq=0x34c78 "<QUOTE>", rq=0x34c88 "<UNQUOTE>") | |
652 | at input.c:530 | |
653 | 530 if (lquote != def_lquote) | |
654 | @end smallexample | |
655 | ||
656 | @noindent | |
657 | The display that shows the subroutine where @code{m4} is now | |
658 | suspended (and its arguments) is called a stack frame display. It | |
659 | shows a summary of the stack. We can use the @code{backtrace} | |
660 | command (which can also be spelled @code{bt}), to see where we are | |
661 | in the stack as a whole: the @code{backtrace} command displays a | |
662 | stack frame for each active subroutine. | |
663 | ||
664 | @smallexample | |
665 | (@value{GDBP}) @b{bt} | |
666 | #0 set_quotes (lq=0x34c78 "<QUOTE>", rq=0x34c88 "<UNQUOTE>") | |
667 | at input.c:530 | |
5d161b24 | 668 | #1 0x6344 in m4_changequote (argc=3, argv=0x33c70) |
c906108c SS |
669 | at builtin.c:882 |
670 | #2 0x8174 in expand_macro (sym=0x33320) at macro.c:242 | |
671 | #3 0x7a88 in expand_token (obs=0x0, t=209696, td=0xf7fffa30) | |
672 | at macro.c:71 | |
673 | #4 0x79dc in expand_input () at macro.c:40 | |
674 | #5 0x2930 in main (argc=0, argv=0xf7fffb20) at m4.c:195 | |
675 | @end smallexample | |
676 | ||
677 | @noindent | |
678 | We step through a few more lines to see what happens. The first two | |
679 | times, we can use @samp{s}; the next two times we use @code{n} to avoid | |
680 | falling into the @code{xstrdup} subroutine. | |
681 | ||
682 | @smallexample | |
683 | (@value{GDBP}) @b{s} | |
684 | 0x3b5c 532 if (rquote != def_rquote) | |
685 | (@value{GDBP}) @b{s} | |
686 | 0x3b80 535 lquote = (lq == nil || *lq == '\0') ? \ | |
687 | def_lquote : xstrdup(lq); | |
688 | (@value{GDBP}) @b{n} | |
689 | 536 rquote = (rq == nil || *rq == '\0') ? def_rquote\ | |
690 | : xstrdup(rq); | |
691 | (@value{GDBP}) @b{n} | |
692 | 538 len_lquote = strlen(rquote); | |
693 | @end smallexample | |
694 | ||
695 | @noindent | |
696 | The last line displayed looks a little odd; we can examine the variables | |
697 | @code{lquote} and @code{rquote} to see if they are in fact the new left | |
698 | and right quotes we specified. We use the command @code{p} | |
699 | (@code{print}) to see their values. | |
700 | ||
701 | @smallexample | |
702 | (@value{GDBP}) @b{p lquote} | |
703 | $1 = 0x35d40 "<QUOTE>" | |
704 | (@value{GDBP}) @b{p rquote} | |
705 | $2 = 0x35d50 "<UNQUOTE>" | |
706 | @end smallexample | |
707 | ||
708 | @noindent | |
709 | @code{lquote} and @code{rquote} are indeed the new left and right quotes. | |
710 | To look at some context, we can display ten lines of source | |
711 | surrounding the current line with the @code{l} (@code{list}) command. | |
712 | ||
713 | @smallexample | |
714 | (@value{GDBP}) @b{l} | |
715 | 533 xfree(rquote); | |
716 | 534 | |
717 | 535 lquote = (lq == nil || *lq == '\0') ? def_lquote\ | |
718 | : xstrdup (lq); | |
719 | 536 rquote = (rq == nil || *rq == '\0') ? def_rquote\ | |
720 | : xstrdup (rq); | |
721 | 537 | |
722 | 538 len_lquote = strlen(rquote); | |
723 | 539 len_rquote = strlen(lquote); | |
724 | 540 @} | |
725 | 541 | |
726 | 542 void | |
727 | @end smallexample | |
728 | ||
729 | @noindent | |
730 | Let us step past the two lines that set @code{len_lquote} and | |
731 | @code{len_rquote}, and then examine the values of those variables. | |
732 | ||
733 | @smallexample | |
734 | (@value{GDBP}) @b{n} | |
735 | 539 len_rquote = strlen(lquote); | |
736 | (@value{GDBP}) @b{n} | |
737 | 540 @} | |
738 | (@value{GDBP}) @b{p len_lquote} | |
739 | $3 = 9 | |
740 | (@value{GDBP}) @b{p len_rquote} | |
741 | $4 = 7 | |
742 | @end smallexample | |
743 | ||
744 | @noindent | |
745 | That certainly looks wrong, assuming @code{len_lquote} and | |
746 | @code{len_rquote} are meant to be the lengths of @code{lquote} and | |
747 | @code{rquote} respectively. We can set them to better values using | |
748 | the @code{p} command, since it can print the value of | |
749 | any expression---and that expression can include subroutine calls and | |
750 | assignments. | |
751 | ||
752 | @smallexample | |
753 | (@value{GDBP}) @b{p len_lquote=strlen(lquote)} | |
754 | $5 = 7 | |
755 | (@value{GDBP}) @b{p len_rquote=strlen(rquote)} | |
756 | $6 = 9 | |
757 | @end smallexample | |
758 | ||
759 | @noindent | |
760 | Is that enough to fix the problem of using the new quotes with the | |
761 | @code{m4} built-in @code{defn}? We can allow @code{m4} to continue | |
762 | executing with the @code{c} (@code{continue}) command, and then try the | |
763 | example that caused trouble initially: | |
764 | ||
765 | @smallexample | |
766 | (@value{GDBP}) @b{c} | |
767 | Continuing. | |
768 | ||
769 | @b{define(baz,defn(<QUOTE>foo<UNQUOTE>))} | |
770 | ||
771 | baz | |
772 | 0000 | |
773 | @end smallexample | |
774 | ||
775 | @noindent | |
776 | Success! The new quotes now work just as well as the default ones. The | |
777 | problem seems to have been just the two typos defining the wrong | |
778 | lengths. We allow @code{m4} exit by giving it an EOF as input: | |
779 | ||
780 | @smallexample | |
c8aa23ab | 781 | @b{Ctrl-d} |
c906108c SS |
782 | Program exited normally. |
783 | @end smallexample | |
784 | ||
785 | @noindent | |
786 | The message @samp{Program exited normally.} is from @value{GDBN}; it | |
787 | indicates @code{m4} has finished executing. We can end our @value{GDBN} | |
788 | session with the @value{GDBN} @code{quit} command. | |
789 | ||
790 | @smallexample | |
791 | (@value{GDBP}) @b{quit} | |
792 | @end smallexample | |
c906108c | 793 | |
6d2ebf8b | 794 | @node Invocation |
c906108c SS |
795 | @chapter Getting In and Out of @value{GDBN} |
796 | ||
797 | This chapter discusses how to start @value{GDBN}, and how to get out of it. | |
5d161b24 | 798 | The essentials are: |
c906108c | 799 | @itemize @bullet |
5d161b24 | 800 | @item |
53a5351d | 801 | type @samp{@value{GDBP}} to start @value{GDBN}. |
5d161b24 | 802 | @item |
c8aa23ab | 803 | type @kbd{quit} or @kbd{Ctrl-d} to exit. |
c906108c SS |
804 | @end itemize |
805 | ||
806 | @menu | |
807 | * Invoking GDB:: How to start @value{GDBN} | |
808 | * Quitting GDB:: How to quit @value{GDBN} | |
809 | * Shell Commands:: How to use shell commands inside @value{GDBN} | |
79a6e687 | 810 | * Logging Output:: How to log @value{GDBN}'s output to a file |
c906108c SS |
811 | @end menu |
812 | ||
6d2ebf8b | 813 | @node Invoking GDB |
c906108c SS |
814 | @section Invoking @value{GDBN} |
815 | ||
c906108c SS |
816 | Invoke @value{GDBN} by running the program @code{@value{GDBP}}. Once started, |
817 | @value{GDBN} reads commands from the terminal until you tell it to exit. | |
818 | ||
819 | You can also run @code{@value{GDBP}} with a variety of arguments and options, | |
820 | to specify more of your debugging environment at the outset. | |
821 | ||
c906108c SS |
822 | The command-line options described here are designed |
823 | to cover a variety of situations; in some environments, some of these | |
5d161b24 | 824 | options may effectively be unavailable. |
c906108c SS |
825 | |
826 | The most usual way to start @value{GDBN} is with one argument, | |
827 | specifying an executable program: | |
828 | ||
474c8240 | 829 | @smallexample |
c906108c | 830 | @value{GDBP} @var{program} |
474c8240 | 831 | @end smallexample |
c906108c | 832 | |
c906108c SS |
833 | @noindent |
834 | You can also start with both an executable program and a core file | |
835 | specified: | |
836 | ||
474c8240 | 837 | @smallexample |
c906108c | 838 | @value{GDBP} @var{program} @var{core} |
474c8240 | 839 | @end smallexample |
c906108c SS |
840 | |
841 | You can, instead, specify a process ID as a second argument, if you want | |
842 | to debug a running process: | |
843 | ||
474c8240 | 844 | @smallexample |
c906108c | 845 | @value{GDBP} @var{program} 1234 |
474c8240 | 846 | @end smallexample |
c906108c SS |
847 | |
848 | @noindent | |
849 | would attach @value{GDBN} to process @code{1234} (unless you also have a file | |
850 | named @file{1234}; @value{GDBN} does check for a core file first). | |
851 | ||
c906108c | 852 | Taking advantage of the second command-line argument requires a fairly |
2df3850c JM |
853 | complete operating system; when you use @value{GDBN} as a remote |
854 | debugger attached to a bare board, there may not be any notion of | |
855 | ``process'', and there is often no way to get a core dump. @value{GDBN} | |
856 | will warn you if it is unable to attach or to read core dumps. | |
c906108c | 857 | |
aa26fa3a TT |
858 | You can optionally have @code{@value{GDBP}} pass any arguments after the |
859 | executable file to the inferior using @code{--args}. This option stops | |
860 | option processing. | |
474c8240 | 861 | @smallexample |
3f94c067 | 862 | @value{GDBP} --args gcc -O2 -c foo.c |
474c8240 | 863 | @end smallexample |
aa26fa3a TT |
864 | This will cause @code{@value{GDBP}} to debug @code{gcc}, and to set |
865 | @code{gcc}'s command-line arguments (@pxref{Arguments}) to @samp{-O2 -c foo.c}. | |
866 | ||
96a2c332 | 867 | You can run @code{@value{GDBP}} without printing the front material, which describes |
c906108c SS |
868 | @value{GDBN}'s non-warranty, by specifying @code{-silent}: |
869 | ||
870 | @smallexample | |
871 | @value{GDBP} -silent | |
872 | @end smallexample | |
873 | ||
874 | @noindent | |
875 | You can further control how @value{GDBN} starts up by using command-line | |
876 | options. @value{GDBN} itself can remind you of the options available. | |
877 | ||
878 | @noindent | |
879 | Type | |
880 | ||
474c8240 | 881 | @smallexample |
c906108c | 882 | @value{GDBP} -help |
474c8240 | 883 | @end smallexample |
c906108c SS |
884 | |
885 | @noindent | |
886 | to display all available options and briefly describe their use | |
887 | (@samp{@value{GDBP} -h} is a shorter equivalent). | |
888 | ||
889 | All options and command line arguments you give are processed | |
890 | in sequential order. The order makes a difference when the | |
891 | @samp{-x} option is used. | |
892 | ||
893 | ||
894 | @menu | |
c906108c SS |
895 | * File Options:: Choosing files |
896 | * Mode Options:: Choosing modes | |
6fc08d32 | 897 | * Startup:: What @value{GDBN} does during startup |
c906108c SS |
898 | @end menu |
899 | ||
6d2ebf8b | 900 | @node File Options |
79a6e687 | 901 | @subsection Choosing Files |
c906108c | 902 | |
2df3850c | 903 | When @value{GDBN} starts, it reads any arguments other than options as |
c906108c SS |
904 | specifying an executable file and core file (or process ID). This is |
905 | the same as if the arguments were specified by the @samp{-se} and | |
d52fb0e9 | 906 | @samp{-c} (or @samp{-p}) options respectively. (@value{GDBN} reads the |
19837790 MS |
907 | first argument that does not have an associated option flag as |
908 | equivalent to the @samp{-se} option followed by that argument; and the | |
909 | second argument that does not have an associated option flag, if any, as | |
910 | equivalent to the @samp{-c}/@samp{-p} option followed by that argument.) | |
911 | If the second argument begins with a decimal digit, @value{GDBN} will | |
912 | first attempt to attach to it as a process, and if that fails, attempt | |
913 | to open it as a corefile. If you have a corefile whose name begins with | |
b383017d | 914 | a digit, you can prevent @value{GDBN} from treating it as a pid by |
c1468174 | 915 | prefixing it with @file{./}, e.g.@: @file{./12345}. |
7a292a7a SS |
916 | |
917 | If @value{GDBN} has not been configured to included core file support, | |
918 | such as for most embedded targets, then it will complain about a second | |
919 | argument and ignore it. | |
c906108c SS |
920 | |
921 | Many options have both long and short forms; both are shown in the | |
922 | following list. @value{GDBN} also recognizes the long forms if you truncate | |
923 | them, so long as enough of the option is present to be unambiguous. | |
924 | (If you prefer, you can flag option arguments with @samp{--} rather | |
925 | than @samp{-}, though we illustrate the more usual convention.) | |
926 | ||
d700128c EZ |
927 | @c NOTE: the @cindex entries here use double dashes ON PURPOSE. This |
928 | @c way, both those who look for -foo and --foo in the index, will find | |
929 | @c it. | |
930 | ||
c906108c SS |
931 | @table @code |
932 | @item -symbols @var{file} | |
933 | @itemx -s @var{file} | |
d700128c EZ |
934 | @cindex @code{--symbols} |
935 | @cindex @code{-s} | |
c906108c SS |
936 | Read symbol table from file @var{file}. |
937 | ||
938 | @item -exec @var{file} | |
939 | @itemx -e @var{file} | |
d700128c EZ |
940 | @cindex @code{--exec} |
941 | @cindex @code{-e} | |
7a292a7a SS |
942 | Use file @var{file} as the executable file to execute when appropriate, |
943 | and for examining pure data in conjunction with a core dump. | |
c906108c SS |
944 | |
945 | @item -se @var{file} | |
d700128c | 946 | @cindex @code{--se} |
c906108c SS |
947 | Read symbol table from file @var{file} and use it as the executable |
948 | file. | |
949 | ||
c906108c SS |
950 | @item -core @var{file} |
951 | @itemx -c @var{file} | |
d700128c EZ |
952 | @cindex @code{--core} |
953 | @cindex @code{-c} | |
b383017d | 954 | Use file @var{file} as a core dump to examine. |
c906108c | 955 | |
19837790 MS |
956 | @item -pid @var{number} |
957 | @itemx -p @var{number} | |
958 | @cindex @code{--pid} | |
959 | @cindex @code{-p} | |
960 | Connect to process ID @var{number}, as with the @code{attach} command. | |
c906108c SS |
961 | |
962 | @item -command @var{file} | |
963 | @itemx -x @var{file} | |
d700128c EZ |
964 | @cindex @code{--command} |
965 | @cindex @code{-x} | |
95433b34 JB |
966 | Execute commands from file @var{file}. The contents of this file is |
967 | evaluated exactly as the @code{source} command would. | |
8150ff9c | 968 | @xref{Command Files,, Command files}. |
c906108c | 969 | |
8a5a3c82 AS |
970 | @item -eval-command @var{command} |
971 | @itemx -ex @var{command} | |
972 | @cindex @code{--eval-command} | |
973 | @cindex @code{-ex} | |
974 | Execute a single @value{GDBN} command. | |
975 | ||
976 | This option may be used multiple times to call multiple commands. It may | |
977 | also be interleaved with @samp{-command} as required. | |
978 | ||
979 | @smallexample | |
980 | @value{GDBP} -ex 'target sim' -ex 'load' \ | |
981 | -x setbreakpoints -ex 'run' a.out | |
982 | @end smallexample | |
983 | ||
c906108c SS |
984 | @item -directory @var{directory} |
985 | @itemx -d @var{directory} | |
d700128c EZ |
986 | @cindex @code{--directory} |
987 | @cindex @code{-d} | |
4b505b12 | 988 | Add @var{directory} to the path to search for source and script files. |
c906108c | 989 | |
c906108c SS |
990 | @item -r |
991 | @itemx -readnow | |
d700128c EZ |
992 | @cindex @code{--readnow} |
993 | @cindex @code{-r} | |
c906108c SS |
994 | Read each symbol file's entire symbol table immediately, rather than |
995 | the default, which is to read it incrementally as it is needed. | |
996 | This makes startup slower, but makes future operations faster. | |
53a5351d | 997 | |
c906108c SS |
998 | @end table |
999 | ||
6d2ebf8b | 1000 | @node Mode Options |
79a6e687 | 1001 | @subsection Choosing Modes |
c906108c SS |
1002 | |
1003 | You can run @value{GDBN} in various alternative modes---for example, in | |
1004 | batch mode or quiet mode. | |
1005 | ||
1006 | @table @code | |
1007 | @item -nx | |
1008 | @itemx -n | |
d700128c EZ |
1009 | @cindex @code{--nx} |
1010 | @cindex @code{-n} | |
96565e91 | 1011 | Do not execute commands found in any initialization files. Normally, |
2df3850c JM |
1012 | @value{GDBN} executes the commands in these files after all the command |
1013 | options and arguments have been processed. @xref{Command Files,,Command | |
79a6e687 | 1014 | Files}. |
c906108c SS |
1015 | |
1016 | @item -quiet | |
d700128c | 1017 | @itemx -silent |
c906108c | 1018 | @itemx -q |
d700128c EZ |
1019 | @cindex @code{--quiet} |
1020 | @cindex @code{--silent} | |
1021 | @cindex @code{-q} | |
c906108c SS |
1022 | ``Quiet''. Do not print the introductory and copyright messages. These |
1023 | messages are also suppressed in batch mode. | |
1024 | ||
1025 | @item -batch | |
d700128c | 1026 | @cindex @code{--batch} |
c906108c SS |
1027 | Run in batch mode. Exit with status @code{0} after processing all the |
1028 | command files specified with @samp{-x} (and all commands from | |
1029 | initialization files, if not inhibited with @samp{-n}). Exit with | |
1030 | nonzero status if an error occurs in executing the @value{GDBN} commands | |
7c953934 TT |
1031 | in the command files. Batch mode also disables pagination; |
1032 | @pxref{Screen Size} and acts as if @kbd{set confirm off} were in | |
1033 | effect (@pxref{Messages/Warnings}). | |
c906108c | 1034 | |
2df3850c JM |
1035 | Batch mode may be useful for running @value{GDBN} as a filter, for |
1036 | example to download and run a program on another computer; in order to | |
1037 | make this more useful, the message | |
c906108c | 1038 | |
474c8240 | 1039 | @smallexample |
c906108c | 1040 | Program exited normally. |
474c8240 | 1041 | @end smallexample |
c906108c SS |
1042 | |
1043 | @noindent | |
2df3850c JM |
1044 | (which is ordinarily issued whenever a program running under |
1045 | @value{GDBN} control terminates) is not issued when running in batch | |
1046 | mode. | |
1047 | ||
1a088d06 AS |
1048 | @item -batch-silent |
1049 | @cindex @code{--batch-silent} | |
1050 | Run in batch mode exactly like @samp{-batch}, but totally silently. All | |
1051 | @value{GDBN} output to @code{stdout} is prevented (@code{stderr} is | |
1052 | unaffected). This is much quieter than @samp{-silent} and would be useless | |
1053 | for an interactive session. | |
1054 | ||
1055 | This is particularly useful when using targets that give @samp{Loading section} | |
1056 | messages, for example. | |
1057 | ||
1058 | Note that targets that give their output via @value{GDBN}, as opposed to | |
1059 | writing directly to @code{stdout}, will also be made silent. | |
1060 | ||
4b0ad762 AS |
1061 | @item -return-child-result |
1062 | @cindex @code{--return-child-result} | |
1063 | The return code from @value{GDBN} will be the return code from the child | |
1064 | process (the process being debugged), with the following exceptions: | |
1065 | ||
1066 | @itemize @bullet | |
1067 | @item | |
1068 | @value{GDBN} exits abnormally. E.g., due to an incorrect argument or an | |
1069 | internal error. In this case the exit code is the same as it would have been | |
1070 | without @samp{-return-child-result}. | |
1071 | @item | |
1072 | The user quits with an explicit value. E.g., @samp{quit 1}. | |
1073 | @item | |
1074 | The child process never runs, or is not allowed to terminate, in which case | |
1075 | the exit code will be -1. | |
1076 | @end itemize | |
1077 | ||
1078 | This option is useful in conjunction with @samp{-batch} or @samp{-batch-silent}, | |
1079 | when @value{GDBN} is being used as a remote program loader or simulator | |
1080 | interface. | |
1081 | ||
2df3850c JM |
1082 | @item -nowindows |
1083 | @itemx -nw | |
d700128c EZ |
1084 | @cindex @code{--nowindows} |
1085 | @cindex @code{-nw} | |
2df3850c | 1086 | ``No windows''. If @value{GDBN} comes with a graphical user interface |
96a2c332 | 1087 | (GUI) built in, then this option tells @value{GDBN} to only use the command-line |
2df3850c JM |
1088 | interface. If no GUI is available, this option has no effect. |
1089 | ||
1090 | @item -windows | |
1091 | @itemx -w | |
d700128c EZ |
1092 | @cindex @code{--windows} |
1093 | @cindex @code{-w} | |
2df3850c JM |
1094 | If @value{GDBN} includes a GUI, then this option requires it to be |
1095 | used if possible. | |
c906108c SS |
1096 | |
1097 | @item -cd @var{directory} | |
d700128c | 1098 | @cindex @code{--cd} |
c906108c SS |
1099 | Run @value{GDBN} using @var{directory} as its working directory, |
1100 | instead of the current directory. | |
1101 | ||
c906108c SS |
1102 | @item -fullname |
1103 | @itemx -f | |
d700128c EZ |
1104 | @cindex @code{--fullname} |
1105 | @cindex @code{-f} | |
7a292a7a SS |
1106 | @sc{gnu} Emacs sets this option when it runs @value{GDBN} as a |
1107 | subprocess. It tells @value{GDBN} to output the full file name and line | |
1108 | number in a standard, recognizable fashion each time a stack frame is | |
1109 | displayed (which includes each time your program stops). This | |
1110 | recognizable format looks like two @samp{\032} characters, followed by | |
1111 | the file name, line number and character position separated by colons, | |
1112 | and a newline. The Emacs-to-@value{GDBN} interface program uses the two | |
1113 | @samp{\032} characters as a signal to display the source code for the | |
1114 | frame. | |
c906108c | 1115 | |
d700128c EZ |
1116 | @item -epoch |
1117 | @cindex @code{--epoch} | |
1118 | The Epoch Emacs-@value{GDBN} interface sets this option when it runs | |
1119 | @value{GDBN} as a subprocess. It tells @value{GDBN} to modify its print | |
1120 | routines so as to allow Epoch to display values of expressions in a | |
1121 | separate window. | |
1122 | ||
1123 | @item -annotate @var{level} | |
1124 | @cindex @code{--annotate} | |
1125 | This option sets the @dfn{annotation level} inside @value{GDBN}. Its | |
1126 | effect is identical to using @samp{set annotate @var{level}} | |
086432e2 AC |
1127 | (@pxref{Annotations}). The annotation @var{level} controls how much |
1128 | information @value{GDBN} prints together with its prompt, values of | |
1129 | expressions, source lines, and other types of output. Level 0 is the | |
1130 | normal, level 1 is for use when @value{GDBN} is run as a subprocess of | |
1131 | @sc{gnu} Emacs, level 3 is the maximum annotation suitable for programs | |
1132 | that control @value{GDBN}, and level 2 has been deprecated. | |
1133 | ||
265eeb58 | 1134 | The annotation mechanism has largely been superseded by @sc{gdb/mi} |
086432e2 | 1135 | (@pxref{GDB/MI}). |
d700128c | 1136 | |
aa26fa3a TT |
1137 | @item --args |
1138 | @cindex @code{--args} | |
1139 | Change interpretation of command line so that arguments following the | |
1140 | executable file are passed as command line arguments to the inferior. | |
1141 | This option stops option processing. | |
1142 | ||
2df3850c JM |
1143 | @item -baud @var{bps} |
1144 | @itemx -b @var{bps} | |
d700128c EZ |
1145 | @cindex @code{--baud} |
1146 | @cindex @code{-b} | |
c906108c SS |
1147 | Set the line speed (baud rate or bits per second) of any serial |
1148 | interface used by @value{GDBN} for remote debugging. | |
c906108c | 1149 | |
f47b1503 AS |
1150 | @item -l @var{timeout} |
1151 | @cindex @code{-l} | |
1152 | Set the timeout (in seconds) of any communication used by @value{GDBN} | |
1153 | for remote debugging. | |
1154 | ||
c906108c | 1155 | @item -tty @var{device} |
d700128c EZ |
1156 | @itemx -t @var{device} |
1157 | @cindex @code{--tty} | |
1158 | @cindex @code{-t} | |
c906108c SS |
1159 | Run using @var{device} for your program's standard input and output. |
1160 | @c FIXME: kingdon thinks there is more to -tty. Investigate. | |
c906108c | 1161 | |
53a5351d | 1162 | @c resolve the situation of these eventually |
c4555f82 SC |
1163 | @item -tui |
1164 | @cindex @code{--tui} | |
d0d5df6f AC |
1165 | Activate the @dfn{Text User Interface} when starting. The Text User |
1166 | Interface manages several text windows on the terminal, showing | |
1167 | source, assembly, registers and @value{GDBN} command outputs | |
1168 | (@pxref{TUI, ,@value{GDBN} Text User Interface}). Alternatively, the | |
1169 | Text User Interface can be enabled by invoking the program | |
46ba6afa | 1170 | @samp{@value{GDBTUI}}. Do not use this option if you run @value{GDBN} from |
d0d5df6f | 1171 | Emacs (@pxref{Emacs, ,Using @value{GDBN} under @sc{gnu} Emacs}). |
53a5351d JM |
1172 | |
1173 | @c @item -xdb | |
d700128c | 1174 | @c @cindex @code{--xdb} |
53a5351d JM |
1175 | @c Run in XDB compatibility mode, allowing the use of certain XDB commands. |
1176 | @c For information, see the file @file{xdb_trans.html}, which is usually | |
1177 | @c installed in the directory @code{/opt/langtools/wdb/doc} on HP-UX | |
1178 | @c systems. | |
1179 | ||
d700128c EZ |
1180 | @item -interpreter @var{interp} |
1181 | @cindex @code{--interpreter} | |
1182 | Use the interpreter @var{interp} for interface with the controlling | |
1183 | program or device. This option is meant to be set by programs which | |
94bbb2c0 | 1184 | communicate with @value{GDBN} using it as a back end. |
21c294e6 | 1185 | @xref{Interpreters, , Command Interpreters}. |
94bbb2c0 | 1186 | |
da0f9dcd | 1187 | @samp{--interpreter=mi} (or @samp{--interpreter=mi2}) causes |
2fcf52f0 | 1188 | @value{GDBN} to use the @dfn{@sc{gdb/mi} interface} (@pxref{GDB/MI, , |
6b5e8c01 | 1189 | The @sc{gdb/mi} Interface}) included since @value{GDBN} version 6.0. The |
6c74ac8b AC |
1190 | previous @sc{gdb/mi} interface, included in @value{GDBN} version 5.3 and |
1191 | selected with @samp{--interpreter=mi1}, is deprecated. Earlier | |
1192 | @sc{gdb/mi} interfaces are no longer supported. | |
d700128c EZ |
1193 | |
1194 | @item -write | |
1195 | @cindex @code{--write} | |
1196 | Open the executable and core files for both reading and writing. This | |
1197 | is equivalent to the @samp{set write on} command inside @value{GDBN} | |
1198 | (@pxref{Patching}). | |
1199 | ||
1200 | @item -statistics | |
1201 | @cindex @code{--statistics} | |
1202 | This option causes @value{GDBN} to print statistics about time and | |
1203 | memory usage after it completes each command and returns to the prompt. | |
1204 | ||
1205 | @item -version | |
1206 | @cindex @code{--version} | |
1207 | This option causes @value{GDBN} to print its version number and | |
1208 | no-warranty blurb, and exit. | |
1209 | ||
c906108c SS |
1210 | @end table |
1211 | ||
6fc08d32 | 1212 | @node Startup |
79a6e687 | 1213 | @subsection What @value{GDBN} Does During Startup |
6fc08d32 EZ |
1214 | @cindex @value{GDBN} startup |
1215 | ||
1216 | Here's the description of what @value{GDBN} does during session startup: | |
1217 | ||
1218 | @enumerate | |
1219 | @item | |
1220 | Sets up the command interpreter as specified by the command line | |
1221 | (@pxref{Mode Options, interpreter}). | |
1222 | ||
1223 | @item | |
1224 | @cindex init file | |
098b41a6 JG |
1225 | Reads the system-wide @dfn{init file} (if @option{--with-system-gdbinit} was |
1226 | used when building @value{GDBN}; @pxref{System-wide configuration, | |
1227 | ,System-wide configuration and settings}) and executes all the commands in | |
1228 | that file. | |
1229 | ||
1230 | @item | |
1231 | Reads the init file (if any) in your home directory@footnote{On | |
6fc08d32 EZ |
1232 | DOS/Windows systems, the home directory is the one pointed to by the |
1233 | @code{HOME} environment variable.} and executes all the commands in | |
1234 | that file. | |
1235 | ||
1236 | @item | |
1237 | Processes command line options and operands. | |
1238 | ||
1239 | @item | |
1240 | Reads and executes the commands from init file (if any) in the current | |
119b882a EZ |
1241 | working directory. This is only done if the current directory is |
1242 | different from your home directory. Thus, you can have more than one | |
1243 | init file, one generic in your home directory, and another, specific | |
1244 | to the program you are debugging, in the directory where you invoke | |
6fc08d32 EZ |
1245 | @value{GDBN}. |
1246 | ||
1247 | @item | |
1248 | Reads command files specified by the @samp{-x} option. @xref{Command | |
1249 | Files}, for more details about @value{GDBN} command files. | |
1250 | ||
1251 | @item | |
1252 | Reads the command history recorded in the @dfn{history file}. | |
d620b259 | 1253 | @xref{Command History}, for more details about the command history and the |
6fc08d32 EZ |
1254 | files where @value{GDBN} records it. |
1255 | @end enumerate | |
1256 | ||
1257 | Init files use the same syntax as @dfn{command files} (@pxref{Command | |
1258 | Files}) and are processed by @value{GDBN} in the same way. The init | |
1259 | file in your home directory can set options (such as @samp{set | |
1260 | complaints}) that affect subsequent processing of command line options | |
1261 | and operands. Init files are not executed if you use the @samp{-nx} | |
79a6e687 | 1262 | option (@pxref{Mode Options, ,Choosing Modes}). |
6fc08d32 | 1263 | |
098b41a6 JG |
1264 | To display the list of init files loaded by gdb at startup, you |
1265 | can use @kbd{gdb --help}. | |
1266 | ||
6fc08d32 EZ |
1267 | @cindex init file name |
1268 | @cindex @file{.gdbinit} | |
119b882a | 1269 | @cindex @file{gdb.ini} |
8807d78b | 1270 | The @value{GDBN} init files are normally called @file{.gdbinit}. |
119b882a EZ |
1271 | The DJGPP port of @value{GDBN} uses the name @file{gdb.ini}, due to |
1272 | the limitations of file names imposed by DOS filesystems. The Windows | |
1273 | ports of @value{GDBN} use the standard name, but if they find a | |
1274 | @file{gdb.ini} file, they warn you about that and suggest to rename | |
1275 | the file to the standard name. | |
1276 | ||
6fc08d32 | 1277 | |
6d2ebf8b | 1278 | @node Quitting GDB |
c906108c SS |
1279 | @section Quitting @value{GDBN} |
1280 | @cindex exiting @value{GDBN} | |
1281 | @cindex leaving @value{GDBN} | |
1282 | ||
1283 | @table @code | |
1284 | @kindex quit @r{[}@var{expression}@r{]} | |
41afff9a | 1285 | @kindex q @r{(@code{quit})} |
96a2c332 SS |
1286 | @item quit @r{[}@var{expression}@r{]} |
1287 | @itemx q | |
1288 | To exit @value{GDBN}, use the @code{quit} command (abbreviated | |
c8aa23ab | 1289 | @code{q}), or type an end-of-file character (usually @kbd{Ctrl-d}). If you |
96a2c332 SS |
1290 | do not supply @var{expression}, @value{GDBN} will terminate normally; |
1291 | otherwise it will terminate using the result of @var{expression} as the | |
1292 | error code. | |
c906108c SS |
1293 | @end table |
1294 | ||
1295 | @cindex interrupt | |
c8aa23ab | 1296 | An interrupt (often @kbd{Ctrl-c}) does not exit from @value{GDBN}, but rather |
c906108c SS |
1297 | terminates the action of any @value{GDBN} command that is in progress and |
1298 | returns to @value{GDBN} command level. It is safe to type the interrupt | |
1299 | character at any time because @value{GDBN} does not allow it to take effect | |
1300 | until a time when it is safe. | |
1301 | ||
c906108c SS |
1302 | If you have been using @value{GDBN} to control an attached process or |
1303 | device, you can release it with the @code{detach} command | |
79a6e687 | 1304 | (@pxref{Attach, ,Debugging an Already-running Process}). |
c906108c | 1305 | |
6d2ebf8b | 1306 | @node Shell Commands |
79a6e687 | 1307 | @section Shell Commands |
c906108c SS |
1308 | |
1309 | If you need to execute occasional shell commands during your | |
1310 | debugging session, there is no need to leave or suspend @value{GDBN}; you can | |
1311 | just use the @code{shell} command. | |
1312 | ||
1313 | @table @code | |
1314 | @kindex shell | |
1315 | @cindex shell escape | |
1316 | @item shell @var{command string} | |
1317 | Invoke a standard shell to execute @var{command string}. | |
c906108c | 1318 | If it exists, the environment variable @code{SHELL} determines which |
d4f3574e SS |
1319 | shell to run. Otherwise @value{GDBN} uses the default shell |
1320 | (@file{/bin/sh} on Unix systems, @file{COMMAND.COM} on MS-DOS, etc.). | |
c906108c SS |
1321 | @end table |
1322 | ||
1323 | The utility @code{make} is often needed in development environments. | |
1324 | You do not have to use the @code{shell} command for this purpose in | |
1325 | @value{GDBN}: | |
1326 | ||
1327 | @table @code | |
1328 | @kindex make | |
1329 | @cindex calling make | |
1330 | @item make @var{make-args} | |
1331 | Execute the @code{make} program with the specified | |
1332 | arguments. This is equivalent to @samp{shell make @var{make-args}}. | |
1333 | @end table | |
1334 | ||
79a6e687 BW |
1335 | @node Logging Output |
1336 | @section Logging Output | |
0fac0b41 | 1337 | @cindex logging @value{GDBN} output |
9c16f35a | 1338 | @cindex save @value{GDBN} output to a file |
0fac0b41 DJ |
1339 | |
1340 | You may want to save the output of @value{GDBN} commands to a file. | |
1341 | There are several commands to control @value{GDBN}'s logging. | |
1342 | ||
1343 | @table @code | |
1344 | @kindex set logging | |
1345 | @item set logging on | |
1346 | Enable logging. | |
1347 | @item set logging off | |
1348 | Disable logging. | |
9c16f35a | 1349 | @cindex logging file name |
0fac0b41 DJ |
1350 | @item set logging file @var{file} |
1351 | Change the name of the current logfile. The default logfile is @file{gdb.txt}. | |
1352 | @item set logging overwrite [on|off] | |
1353 | By default, @value{GDBN} will append to the logfile. Set @code{overwrite} if | |
1354 | you want @code{set logging on} to overwrite the logfile instead. | |
1355 | @item set logging redirect [on|off] | |
1356 | By default, @value{GDBN} output will go to both the terminal and the logfile. | |
1357 | Set @code{redirect} if you want output to go only to the log file. | |
1358 | @kindex show logging | |
1359 | @item show logging | |
1360 | Show the current values of the logging settings. | |
1361 | @end table | |
1362 | ||
6d2ebf8b | 1363 | @node Commands |
c906108c SS |
1364 | @chapter @value{GDBN} Commands |
1365 | ||
1366 | You can abbreviate a @value{GDBN} command to the first few letters of the command | |
1367 | name, if that abbreviation is unambiguous; and you can repeat certain | |
1368 | @value{GDBN} commands by typing just @key{RET}. You can also use the @key{TAB} | |
1369 | key to get @value{GDBN} to fill out the rest of a word in a command (or to | |
1370 | show you the alternatives available, if there is more than one possibility). | |
1371 | ||
1372 | @menu | |
1373 | * Command Syntax:: How to give commands to @value{GDBN} | |
1374 | * Completion:: Command completion | |
1375 | * Help:: How to ask @value{GDBN} for help | |
1376 | @end menu | |
1377 | ||
6d2ebf8b | 1378 | @node Command Syntax |
79a6e687 | 1379 | @section Command Syntax |
c906108c SS |
1380 | |
1381 | A @value{GDBN} command is a single line of input. There is no limit on | |
1382 | how long it can be. It starts with a command name, which is followed by | |
1383 | arguments whose meaning depends on the command name. For example, the | |
1384 | command @code{step} accepts an argument which is the number of times to | |
1385 | step, as in @samp{step 5}. You can also use the @code{step} command | |
96a2c332 | 1386 | with no arguments. Some commands do not allow any arguments. |
c906108c SS |
1387 | |
1388 | @cindex abbreviation | |
1389 | @value{GDBN} command names may always be truncated if that abbreviation is | |
1390 | unambiguous. Other possible command abbreviations are listed in the | |
1391 | documentation for individual commands. In some cases, even ambiguous | |
1392 | abbreviations are allowed; for example, @code{s} is specially defined as | |
1393 | equivalent to @code{step} even though there are other commands whose | |
1394 | names start with @code{s}. You can test abbreviations by using them as | |
1395 | arguments to the @code{help} command. | |
1396 | ||
1397 | @cindex repeating commands | |
41afff9a | 1398 | @kindex RET @r{(repeat last command)} |
c906108c | 1399 | A blank line as input to @value{GDBN} (typing just @key{RET}) means to |
96a2c332 | 1400 | repeat the previous command. Certain commands (for example, @code{run}) |
c906108c SS |
1401 | will not repeat this way; these are commands whose unintentional |
1402 | repetition might cause trouble and which you are unlikely to want to | |
c45da7e6 EZ |
1403 | repeat. User-defined commands can disable this feature; see |
1404 | @ref{Define, dont-repeat}. | |
c906108c SS |
1405 | |
1406 | The @code{list} and @code{x} commands, when you repeat them with | |
1407 | @key{RET}, construct new arguments rather than repeating | |
1408 | exactly as typed. This permits easy scanning of source or memory. | |
1409 | ||
1410 | @value{GDBN} can also use @key{RET} in another way: to partition lengthy | |
1411 | output, in a way similar to the common utility @code{more} | |
79a6e687 | 1412 | (@pxref{Screen Size,,Screen Size}). Since it is easy to press one |
c906108c SS |
1413 | @key{RET} too many in this situation, @value{GDBN} disables command |
1414 | repetition after any command that generates this sort of display. | |
1415 | ||
41afff9a | 1416 | @kindex # @r{(a comment)} |
c906108c SS |
1417 | @cindex comment |
1418 | Any text from a @kbd{#} to the end of the line is a comment; it does | |
1419 | nothing. This is useful mainly in command files (@pxref{Command | |
79a6e687 | 1420 | Files,,Command Files}). |
c906108c | 1421 | |
88118b3a | 1422 | @cindex repeating command sequences |
c8aa23ab EZ |
1423 | @kindex Ctrl-o @r{(operate-and-get-next)} |
1424 | The @kbd{Ctrl-o} binding is useful for repeating a complex sequence of | |
7f9087cb | 1425 | commands. This command accepts the current line, like @key{RET}, and |
88118b3a TT |
1426 | then fetches the next line relative to the current line from the history |
1427 | for editing. | |
1428 | ||
6d2ebf8b | 1429 | @node Completion |
79a6e687 | 1430 | @section Command Completion |
c906108c SS |
1431 | |
1432 | @cindex completion | |
1433 | @cindex word completion | |
1434 | @value{GDBN} can fill in the rest of a word in a command for you, if there is | |
1435 | only one possibility; it can also show you what the valid possibilities | |
1436 | are for the next word in a command, at any time. This works for @value{GDBN} | |
1437 | commands, @value{GDBN} subcommands, and the names of symbols in your program. | |
1438 | ||
1439 | Press the @key{TAB} key whenever you want @value{GDBN} to fill out the rest | |
1440 | of a word. If there is only one possibility, @value{GDBN} fills in the | |
1441 | word, and waits for you to finish the command (or press @key{RET} to | |
1442 | enter it). For example, if you type | |
1443 | ||
1444 | @c FIXME "@key" does not distinguish its argument sufficiently to permit | |
1445 | @c complete accuracy in these examples; space introduced for clarity. | |
1446 | @c If texinfo enhancements make it unnecessary, it would be nice to | |
1447 | @c replace " @key" by "@key" in the following... | |
474c8240 | 1448 | @smallexample |
c906108c | 1449 | (@value{GDBP}) info bre @key{TAB} |
474c8240 | 1450 | @end smallexample |
c906108c SS |
1451 | |
1452 | @noindent | |
1453 | @value{GDBN} fills in the rest of the word @samp{breakpoints}, since that is | |
1454 | the only @code{info} subcommand beginning with @samp{bre}: | |
1455 | ||
474c8240 | 1456 | @smallexample |
c906108c | 1457 | (@value{GDBP}) info breakpoints |
474c8240 | 1458 | @end smallexample |
c906108c SS |
1459 | |
1460 | @noindent | |
1461 | You can either press @key{RET} at this point, to run the @code{info | |
1462 | breakpoints} command, or backspace and enter something else, if | |
1463 | @samp{breakpoints} does not look like the command you expected. (If you | |
1464 | were sure you wanted @code{info breakpoints} in the first place, you | |
1465 | might as well just type @key{RET} immediately after @samp{info bre}, | |
1466 | to exploit command abbreviations rather than command completion). | |
1467 | ||
1468 | If there is more than one possibility for the next word when you press | |
1469 | @key{TAB}, @value{GDBN} sounds a bell. You can either supply more | |
1470 | characters and try again, or just press @key{TAB} a second time; | |
1471 | @value{GDBN} displays all the possible completions for that word. For | |
1472 | example, you might want to set a breakpoint on a subroutine whose name | |
1473 | begins with @samp{make_}, but when you type @kbd{b make_@key{TAB}} @value{GDBN} | |
1474 | just sounds the bell. Typing @key{TAB} again displays all the | |
1475 | function names in your program that begin with those characters, for | |
1476 | example: | |
1477 | ||
474c8240 | 1478 | @smallexample |
c906108c SS |
1479 | (@value{GDBP}) b make_ @key{TAB} |
1480 | @exdent @value{GDBN} sounds bell; press @key{TAB} again, to see: | |
5d161b24 DB |
1481 | make_a_section_from_file make_environ |
1482 | make_abs_section make_function_type | |
1483 | make_blockvector make_pointer_type | |
1484 | make_cleanup make_reference_type | |
c906108c SS |
1485 | make_command make_symbol_completion_list |
1486 | (@value{GDBP}) b make_ | |
474c8240 | 1487 | @end smallexample |
c906108c SS |
1488 | |
1489 | @noindent | |
1490 | After displaying the available possibilities, @value{GDBN} copies your | |
1491 | partial input (@samp{b make_} in the example) so you can finish the | |
1492 | command. | |
1493 | ||
1494 | If you just want to see the list of alternatives in the first place, you | |
b37052ae | 1495 | can press @kbd{M-?} rather than pressing @key{TAB} twice. @kbd{M-?} |
7a292a7a | 1496 | means @kbd{@key{META} ?}. You can type this either by holding down a |
c906108c | 1497 | key designated as the @key{META} shift on your keyboard (if there is |
7a292a7a | 1498 | one) while typing @kbd{?}, or as @key{ESC} followed by @kbd{?}. |
c906108c SS |
1499 | |
1500 | @cindex quotes in commands | |
1501 | @cindex completion of quoted strings | |
1502 | Sometimes the string you need, while logically a ``word'', may contain | |
7a292a7a SS |
1503 | parentheses or other characters that @value{GDBN} normally excludes from |
1504 | its notion of a word. To permit word completion to work in this | |
1505 | situation, you may enclose words in @code{'} (single quote marks) in | |
1506 | @value{GDBN} commands. | |
c906108c | 1507 | |
c906108c | 1508 | The most likely situation where you might need this is in typing the |
b37052ae EZ |
1509 | name of a C@t{++} function. This is because C@t{++} allows function |
1510 | overloading (multiple definitions of the same function, distinguished | |
1511 | by argument type). For example, when you want to set a breakpoint you | |
1512 | may need to distinguish whether you mean the version of @code{name} | |
1513 | that takes an @code{int} parameter, @code{name(int)}, or the version | |
1514 | that takes a @code{float} parameter, @code{name(float)}. To use the | |
1515 | word-completion facilities in this situation, type a single quote | |
1516 | @code{'} at the beginning of the function name. This alerts | |
1517 | @value{GDBN} that it may need to consider more information than usual | |
1518 | when you press @key{TAB} or @kbd{M-?} to request word completion: | |
c906108c | 1519 | |
474c8240 | 1520 | @smallexample |
96a2c332 | 1521 | (@value{GDBP}) b 'bubble( @kbd{M-?} |
c906108c SS |
1522 | bubble(double,double) bubble(int,int) |
1523 | (@value{GDBP}) b 'bubble( | |
474c8240 | 1524 | @end smallexample |
c906108c SS |
1525 | |
1526 | In some cases, @value{GDBN} can tell that completing a name requires using | |
1527 | quotes. When this happens, @value{GDBN} inserts the quote for you (while | |
1528 | completing as much as it can) if you do not type the quote in the first | |
1529 | place: | |
1530 | ||
474c8240 | 1531 | @smallexample |
c906108c SS |
1532 | (@value{GDBP}) b bub @key{TAB} |
1533 | @exdent @value{GDBN} alters your input line to the following, and rings a bell: | |
1534 | (@value{GDBP}) b 'bubble( | |
474c8240 | 1535 | @end smallexample |
c906108c SS |
1536 | |
1537 | @noindent | |
1538 | In general, @value{GDBN} can tell that a quote is needed (and inserts it) if | |
1539 | you have not yet started typing the argument list when you ask for | |
1540 | completion on an overloaded symbol. | |
1541 | ||
79a6e687 BW |
1542 | For more information about overloaded functions, see @ref{C Plus Plus |
1543 | Expressions, ,C@t{++} Expressions}. You can use the command @code{set | |
c906108c | 1544 | overload-resolution off} to disable overload resolution; |
79a6e687 | 1545 | see @ref{Debugging C Plus Plus, ,@value{GDBN} Features for C@t{++}}. |
c906108c | 1546 | |
65d12d83 TT |
1547 | @cindex completion of structure field names |
1548 | @cindex structure field name completion | |
1549 | @cindex completion of union field names | |
1550 | @cindex union field name completion | |
1551 | When completing in an expression which looks up a field in a | |
1552 | structure, @value{GDBN} also tries@footnote{The completer can be | |
1553 | confused by certain kinds of invalid expressions. Also, it only | |
1554 | examines the static type of the expression, not the dynamic type.} to | |
1555 | limit completions to the field names available in the type of the | |
1556 | left-hand-side: | |
1557 | ||
1558 | @smallexample | |
1559 | (@value{GDBP}) p gdb_stdout.@kbd{M-?} | |
1560 | magic to_delete to_fputs to_put to_rewind | |
1561 | to_data to_flush to_isatty to_read to_write | |
1562 | @end smallexample | |
1563 | ||
1564 | @noindent | |
1565 | This is because the @code{gdb_stdout} is a variable of the type | |
1566 | @code{struct ui_file} that is defined in @value{GDBN} sources as | |
1567 | follows: | |
1568 | ||
1569 | @smallexample | |
1570 | struct ui_file | |
1571 | @{ | |
1572 | int *magic; | |
1573 | ui_file_flush_ftype *to_flush; | |
1574 | ui_file_write_ftype *to_write; | |
1575 | ui_file_fputs_ftype *to_fputs; | |
1576 | ui_file_read_ftype *to_read; | |
1577 | ui_file_delete_ftype *to_delete; | |
1578 | ui_file_isatty_ftype *to_isatty; | |
1579 | ui_file_rewind_ftype *to_rewind; | |
1580 | ui_file_put_ftype *to_put; | |
1581 | void *to_data; | |
1582 | @} | |
1583 | @end smallexample | |
1584 | ||
c906108c | 1585 | |
6d2ebf8b | 1586 | @node Help |
79a6e687 | 1587 | @section Getting Help |
c906108c SS |
1588 | @cindex online documentation |
1589 | @kindex help | |
1590 | ||
5d161b24 | 1591 | You can always ask @value{GDBN} itself for information on its commands, |
c906108c SS |
1592 | using the command @code{help}. |
1593 | ||
1594 | @table @code | |
41afff9a | 1595 | @kindex h @r{(@code{help})} |
c906108c SS |
1596 | @item help |
1597 | @itemx h | |
1598 | You can use @code{help} (abbreviated @code{h}) with no arguments to | |
1599 | display a short list of named classes of commands: | |
1600 | ||
1601 | @smallexample | |
1602 | (@value{GDBP}) help | |
1603 | List of classes of commands: | |
1604 | ||
2df3850c | 1605 | aliases -- Aliases of other commands |
c906108c | 1606 | breakpoints -- Making program stop at certain points |
2df3850c | 1607 | data -- Examining data |
c906108c | 1608 | files -- Specifying and examining files |
2df3850c JM |
1609 | internals -- Maintenance commands |
1610 | obscure -- Obscure features | |
1611 | running -- Running the program | |
1612 | stack -- Examining the stack | |
c906108c SS |
1613 | status -- Status inquiries |
1614 | support -- Support facilities | |
12c27660 | 1615 | tracepoints -- Tracing of program execution without |
96a2c332 | 1616 | stopping the program |
c906108c | 1617 | user-defined -- User-defined commands |
c906108c | 1618 | |
5d161b24 | 1619 | Type "help" followed by a class name for a list of |
c906108c | 1620 | commands in that class. |
5d161b24 | 1621 | Type "help" followed by command name for full |
c906108c SS |
1622 | documentation. |
1623 | Command name abbreviations are allowed if unambiguous. | |
1624 | (@value{GDBP}) | |
1625 | @end smallexample | |
96a2c332 | 1626 | @c the above line break eliminates huge line overfull... |
c906108c SS |
1627 | |
1628 | @item help @var{class} | |
1629 | Using one of the general help classes as an argument, you can get a | |
1630 | list of the individual commands in that class. For example, here is the | |
1631 | help display for the class @code{status}: | |
1632 | ||
1633 | @smallexample | |
1634 | (@value{GDBP}) help status | |
1635 | Status inquiries. | |
1636 | ||
1637 | List of commands: | |
1638 | ||
1639 | @c Line break in "show" line falsifies real output, but needed | |
1640 | @c to fit in smallbook page size. | |
2df3850c | 1641 | info -- Generic command for showing things |
12c27660 | 1642 | about the program being debugged |
2df3850c | 1643 | show -- Generic command for showing things |
12c27660 | 1644 | about the debugger |
c906108c | 1645 | |
5d161b24 | 1646 | Type "help" followed by command name for full |
c906108c SS |
1647 | documentation. |
1648 | Command name abbreviations are allowed if unambiguous. | |
1649 | (@value{GDBP}) | |
1650 | @end smallexample | |
1651 | ||
1652 | @item help @var{command} | |
1653 | With a command name as @code{help} argument, @value{GDBN} displays a | |
1654 | short paragraph on how to use that command. | |
1655 | ||
6837a0a2 DB |
1656 | @kindex apropos |
1657 | @item apropos @var{args} | |
09d4efe1 | 1658 | The @code{apropos} command searches through all of the @value{GDBN} |
6837a0a2 | 1659 | commands, and their documentation, for the regular expression specified in |
99e008fe | 1660 | @var{args}. It prints out all matches found. For example: |
6837a0a2 DB |
1661 | |
1662 | @smallexample | |
1663 | apropos reload | |
1664 | @end smallexample | |
1665 | ||
b37052ae EZ |
1666 | @noindent |
1667 | results in: | |
6837a0a2 DB |
1668 | |
1669 | @smallexample | |
6d2ebf8b SS |
1670 | @c @group |
1671 | set symbol-reloading -- Set dynamic symbol table reloading | |
12c27660 | 1672 | multiple times in one run |
6d2ebf8b | 1673 | show symbol-reloading -- Show dynamic symbol table reloading |
12c27660 | 1674 | multiple times in one run |
6d2ebf8b | 1675 | @c @end group |
6837a0a2 DB |
1676 | @end smallexample |
1677 | ||
c906108c SS |
1678 | @kindex complete |
1679 | @item complete @var{args} | |
1680 | The @code{complete @var{args}} command lists all the possible completions | |
1681 | for the beginning of a command. Use @var{args} to specify the beginning of the | |
1682 | command you want completed. For example: | |
1683 | ||
1684 | @smallexample | |
1685 | complete i | |
1686 | @end smallexample | |
1687 | ||
1688 | @noindent results in: | |
1689 | ||
1690 | @smallexample | |
1691 | @group | |
2df3850c JM |
1692 | if |
1693 | ignore | |
c906108c SS |
1694 | info |
1695 | inspect | |
c906108c SS |
1696 | @end group |
1697 | @end smallexample | |
1698 | ||
1699 | @noindent This is intended for use by @sc{gnu} Emacs. | |
1700 | @end table | |
1701 | ||
1702 | In addition to @code{help}, you can use the @value{GDBN} commands @code{info} | |
1703 | and @code{show} to inquire about the state of your program, or the state | |
1704 | of @value{GDBN} itself. Each command supports many topics of inquiry; this | |
1705 | manual introduces each of them in the appropriate context. The listings | |
1706 | under @code{info} and under @code{show} in the Index point to | |
1707 | all the sub-commands. @xref{Index}. | |
1708 | ||
1709 | @c @group | |
1710 | @table @code | |
1711 | @kindex info | |
41afff9a | 1712 | @kindex i @r{(@code{info})} |
c906108c SS |
1713 | @item info |
1714 | This command (abbreviated @code{i}) is for describing the state of your | |
cda4ce5a | 1715 | program. For example, you can show the arguments passed to a function |
c906108c SS |
1716 | with @code{info args}, list the registers currently in use with @code{info |
1717 | registers}, or list the breakpoints you have set with @code{info breakpoints}. | |
1718 | You can get a complete list of the @code{info} sub-commands with | |
1719 | @w{@code{help info}}. | |
1720 | ||
1721 | @kindex set | |
1722 | @item set | |
5d161b24 | 1723 | You can assign the result of an expression to an environment variable with |
c906108c SS |
1724 | @code{set}. For example, you can set the @value{GDBN} prompt to a $-sign with |
1725 | @code{set prompt $}. | |
1726 | ||
1727 | @kindex show | |
1728 | @item show | |
5d161b24 | 1729 | In contrast to @code{info}, @code{show} is for describing the state of |
c906108c SS |
1730 | @value{GDBN} itself. |
1731 | You can change most of the things you can @code{show}, by using the | |
1732 | related command @code{set}; for example, you can control what number | |
1733 | system is used for displays with @code{set radix}, or simply inquire | |
1734 | which is currently in use with @code{show radix}. | |
1735 | ||
1736 | @kindex info set | |
1737 | To display all the settable parameters and their current | |
1738 | values, you can use @code{show} with no arguments; you may also use | |
1739 | @code{info set}. Both commands produce the same display. | |
1740 | @c FIXME: "info set" violates the rule that "info" is for state of | |
1741 | @c FIXME...program. Ck w/ GNU: "info set" to be called something else, | |
1742 | @c FIXME...or change desc of rule---eg "state of prog and debugging session"? | |
1743 | @end table | |
1744 | @c @end group | |
1745 | ||
1746 | Here are three miscellaneous @code{show} subcommands, all of which are | |
1747 | exceptional in lacking corresponding @code{set} commands: | |
1748 | ||
1749 | @table @code | |
1750 | @kindex show version | |
9c16f35a | 1751 | @cindex @value{GDBN} version number |
c906108c SS |
1752 | @item show version |
1753 | Show what version of @value{GDBN} is running. You should include this | |
2df3850c JM |
1754 | information in @value{GDBN} bug-reports. If multiple versions of |
1755 | @value{GDBN} are in use at your site, you may need to determine which | |
1756 | version of @value{GDBN} you are running; as @value{GDBN} evolves, new | |
1757 | commands are introduced, and old ones may wither away. Also, many | |
1758 | system vendors ship variant versions of @value{GDBN}, and there are | |
96a2c332 | 1759 | variant versions of @value{GDBN} in @sc{gnu}/Linux distributions as well. |
2df3850c JM |
1760 | The version number is the same as the one announced when you start |
1761 | @value{GDBN}. | |
c906108c SS |
1762 | |
1763 | @kindex show copying | |
09d4efe1 | 1764 | @kindex info copying |
9c16f35a | 1765 | @cindex display @value{GDBN} copyright |
c906108c | 1766 | @item show copying |
09d4efe1 | 1767 | @itemx info copying |
c906108c SS |
1768 | Display information about permission for copying @value{GDBN}. |
1769 | ||
1770 | @kindex show warranty | |
09d4efe1 | 1771 | @kindex info warranty |
c906108c | 1772 | @item show warranty |
09d4efe1 | 1773 | @itemx info warranty |
2df3850c | 1774 | Display the @sc{gnu} ``NO WARRANTY'' statement, or a warranty, |
96a2c332 | 1775 | if your version of @value{GDBN} comes with one. |
2df3850c | 1776 | |
c906108c SS |
1777 | @end table |
1778 | ||
6d2ebf8b | 1779 | @node Running |
c906108c SS |
1780 | @chapter Running Programs Under @value{GDBN} |
1781 | ||
1782 | When you run a program under @value{GDBN}, you must first generate | |
1783 | debugging information when you compile it. | |
7a292a7a SS |
1784 | |
1785 | You may start @value{GDBN} with its arguments, if any, in an environment | |
1786 | of your choice. If you are doing native debugging, you may redirect | |
1787 | your program's input and output, debug an already running process, or | |
1788 | kill a child process. | |
c906108c SS |
1789 | |
1790 | @menu | |
1791 | * Compilation:: Compiling for debugging | |
1792 | * Starting:: Starting your program | |
c906108c SS |
1793 | * Arguments:: Your program's arguments |
1794 | * Environment:: Your program's environment | |
c906108c SS |
1795 | |
1796 | * Working Directory:: Your program's working directory | |
1797 | * Input/Output:: Your program's input and output | |
1798 | * Attach:: Debugging an already-running process | |
1799 | * Kill Process:: Killing the child process | |
c906108c | 1800 | |
6c95b8df | 1801 | * Inferiors and Programs:: Debugging multiple inferiors and programs |
c906108c | 1802 | * Threads:: Debugging programs with multiple threads |
6c95b8df | 1803 | * Forks:: Debugging forks |
5c95884b | 1804 | * Checkpoint/Restart:: Setting a @emph{bookmark} to return to later |
c906108c SS |
1805 | @end menu |
1806 | ||
6d2ebf8b | 1807 | @node Compilation |
79a6e687 | 1808 | @section Compiling for Debugging |
c906108c SS |
1809 | |
1810 | In order to debug a program effectively, you need to generate | |
1811 | debugging information when you compile it. This debugging information | |
1812 | is stored in the object file; it describes the data type of each | |
1813 | variable or function and the correspondence between source line numbers | |
1814 | and addresses in the executable code. | |
1815 | ||
1816 | To request debugging information, specify the @samp{-g} option when you run | |
1817 | the compiler. | |
1818 | ||
514c4d71 | 1819 | Programs that are to be shipped to your customers are compiled with |
edb3359d | 1820 | optimizations, using the @samp{-O} compiler option. However, some |
514c4d71 EZ |
1821 | compilers are unable to handle the @samp{-g} and @samp{-O} options |
1822 | together. Using those compilers, you cannot generate optimized | |
c906108c SS |
1823 | executables containing debugging information. |
1824 | ||
514c4d71 | 1825 | @value{NGCC}, the @sc{gnu} C/C@t{++} compiler, supports @samp{-g} with or |
53a5351d JM |
1826 | without @samp{-O}, making it possible to debug optimized code. We |
1827 | recommend that you @emph{always} use @samp{-g} whenever you compile a | |
1828 | program. You may think your program is correct, but there is no sense | |
edb3359d | 1829 | in pushing your luck. For more information, see @ref{Optimized Code}. |
c906108c SS |
1830 | |
1831 | Older versions of the @sc{gnu} C compiler permitted a variant option | |
1832 | @w{@samp{-gg}} for debugging information. @value{GDBN} no longer supports this | |
1833 | format; if your @sc{gnu} C compiler has this option, do not use it. | |
1834 | ||
514c4d71 EZ |
1835 | @value{GDBN} knows about preprocessor macros and can show you their |
1836 | expansion (@pxref{Macros}). Most compilers do not include information | |
1837 | about preprocessor macros in the debugging information if you specify | |
1838 | the @option{-g} flag alone, because this information is rather large. | |
1839 | Version 3.1 and later of @value{NGCC}, the @sc{gnu} C compiler, | |
1840 | provides macro information if you specify the options | |
1841 | @option{-gdwarf-2} and @option{-g3}; the former option requests | |
1842 | debugging information in the Dwarf 2 format, and the latter requests | |
1843 | ``extra information''. In the future, we hope to find more compact | |
1844 | ways to represent macro information, so that it can be included with | |
1845 | @option{-g} alone. | |
1846 | ||
c906108c | 1847 | @need 2000 |
6d2ebf8b | 1848 | @node Starting |
79a6e687 | 1849 | @section Starting your Program |
c906108c SS |
1850 | @cindex starting |
1851 | @cindex running | |
1852 | ||
1853 | @table @code | |
1854 | @kindex run | |
41afff9a | 1855 | @kindex r @r{(@code{run})} |
c906108c SS |
1856 | @item run |
1857 | @itemx r | |
7a292a7a SS |
1858 | Use the @code{run} command to start your program under @value{GDBN}. |
1859 | You must first specify the program name (except on VxWorks) with an | |
1860 | argument to @value{GDBN} (@pxref{Invocation, ,Getting In and Out of | |
1861 | @value{GDBN}}), or by using the @code{file} or @code{exec-file} command | |
79a6e687 | 1862 | (@pxref{Files, ,Commands to Specify Files}). |
c906108c SS |
1863 | |
1864 | @end table | |
1865 | ||
c906108c SS |
1866 | If you are running your program in an execution environment that |
1867 | supports processes, @code{run} creates an inferior process and makes | |
8edfe269 DJ |
1868 | that process run your program. In some environments without processes, |
1869 | @code{run} jumps to the start of your program. Other targets, | |
1870 | like @samp{remote}, are always running. If you get an error | |
1871 | message like this one: | |
1872 | ||
1873 | @smallexample | |
1874 | The "remote" target does not support "run". | |
1875 | Try "help target" or "continue". | |
1876 | @end smallexample | |
1877 | ||
1878 | @noindent | |
1879 | then use @code{continue} to run your program. You may need @code{load} | |
1880 | first (@pxref{load}). | |
c906108c SS |
1881 | |
1882 | The execution of a program is affected by certain information it | |
1883 | receives from its superior. @value{GDBN} provides ways to specify this | |
1884 | information, which you must do @emph{before} starting your program. (You | |
1885 | can change it after starting your program, but such changes only affect | |
1886 | your program the next time you start it.) This information may be | |
1887 | divided into four categories: | |
1888 | ||
1889 | @table @asis | |
1890 | @item The @emph{arguments.} | |
1891 | Specify the arguments to give your program as the arguments of the | |
1892 | @code{run} command. If a shell is available on your target, the shell | |
1893 | is used to pass the arguments, so that you may use normal conventions | |
1894 | (such as wildcard expansion or variable substitution) in describing | |
1895 | the arguments. | |
1896 | In Unix systems, you can control which shell is used with the | |
1897 | @code{SHELL} environment variable. | |
79a6e687 | 1898 | @xref{Arguments, ,Your Program's Arguments}. |
c906108c SS |
1899 | |
1900 | @item The @emph{environment.} | |
1901 | Your program normally inherits its environment from @value{GDBN}, but you can | |
1902 | use the @value{GDBN} commands @code{set environment} and @code{unset | |
1903 | environment} to change parts of the environment that affect | |
79a6e687 | 1904 | your program. @xref{Environment, ,Your Program's Environment}. |
c906108c SS |
1905 | |
1906 | @item The @emph{working directory.} | |
1907 | Your program inherits its working directory from @value{GDBN}. You can set | |
1908 | the @value{GDBN} working directory with the @code{cd} command in @value{GDBN}. | |
79a6e687 | 1909 | @xref{Working Directory, ,Your Program's Working Directory}. |
c906108c SS |
1910 | |
1911 | @item The @emph{standard input and output.} | |
1912 | Your program normally uses the same device for standard input and | |
1913 | standard output as @value{GDBN} is using. You can redirect input and output | |
1914 | in the @code{run} command line, or you can use the @code{tty} command to | |
1915 | set a different device for your program. | |
79a6e687 | 1916 | @xref{Input/Output, ,Your Program's Input and Output}. |
c906108c SS |
1917 | |
1918 | @cindex pipes | |
1919 | @emph{Warning:} While input and output redirection work, you cannot use | |
1920 | pipes to pass the output of the program you are debugging to another | |
1921 | program; if you attempt this, @value{GDBN} is likely to wind up debugging the | |
1922 | wrong program. | |
1923 | @end table | |
c906108c SS |
1924 | |
1925 | When you issue the @code{run} command, your program begins to execute | |
79a6e687 | 1926 | immediately. @xref{Stopping, ,Stopping and Continuing}, for discussion |
c906108c SS |
1927 | of how to arrange for your program to stop. Once your program has |
1928 | stopped, you may call functions in your program, using the @code{print} | |
1929 | or @code{call} commands. @xref{Data, ,Examining Data}. | |
1930 | ||
1931 | If the modification time of your symbol file has changed since the last | |
1932 | time @value{GDBN} read its symbols, @value{GDBN} discards its symbol | |
1933 | table, and reads it again. When it does this, @value{GDBN} tries to retain | |
1934 | your current breakpoints. | |
1935 | ||
4e8b0763 JB |
1936 | @table @code |
1937 | @kindex start | |
1938 | @item start | |
1939 | @cindex run to main procedure | |
1940 | The name of the main procedure can vary from language to language. | |
1941 | With C or C@t{++}, the main procedure name is always @code{main}, but | |
1942 | other languages such as Ada do not require a specific name for their | |
1943 | main procedure. The debugger provides a convenient way to start the | |
1944 | execution of the program and to stop at the beginning of the main | |
1945 | procedure, depending on the language used. | |
1946 | ||
1947 | The @samp{start} command does the equivalent of setting a temporary | |
1948 | breakpoint at the beginning of the main procedure and then invoking | |
1949 | the @samp{run} command. | |
1950 | ||
f018e82f EZ |
1951 | @cindex elaboration phase |
1952 | Some programs contain an @dfn{elaboration} phase where some startup code is | |
1953 | executed before the main procedure is called. This depends on the | |
1954 | languages used to write your program. In C@t{++}, for instance, | |
4e8b0763 JB |
1955 | constructors for static and global objects are executed before |
1956 | @code{main} is called. It is therefore possible that the debugger stops | |
1957 | before reaching the main procedure. However, the temporary breakpoint | |
1958 | will remain to halt execution. | |
1959 | ||
1960 | Specify the arguments to give to your program as arguments to the | |
1961 | @samp{start} command. These arguments will be given verbatim to the | |
1962 | underlying @samp{run} command. Note that the same arguments will be | |
1963 | reused if no argument is provided during subsequent calls to | |
1964 | @samp{start} or @samp{run}. | |
1965 | ||
1966 | It is sometimes necessary to debug the program during elaboration. In | |
1967 | these cases, using the @code{start} command would stop the execution of | |
1968 | your program too late, as the program would have already completed the | |
1969 | elaboration phase. Under these circumstances, insert breakpoints in your | |
1970 | elaboration code before running your program. | |
ccd213ac DJ |
1971 | |
1972 | @kindex set exec-wrapper | |
1973 | @item set exec-wrapper @var{wrapper} | |
1974 | @itemx show exec-wrapper | |
1975 | @itemx unset exec-wrapper | |
1976 | When @samp{exec-wrapper} is set, the specified wrapper is used to | |
1977 | launch programs for debugging. @value{GDBN} starts your program | |
1978 | with a shell command of the form @kbd{exec @var{wrapper} | |
1979 | @var{program}}. Quoting is added to @var{program} and its | |
1980 | arguments, but not to @var{wrapper}, so you should add quotes if | |
1981 | appropriate for your shell. The wrapper runs until it executes | |
1982 | your program, and then @value{GDBN} takes control. | |
1983 | ||
1984 | You can use any program that eventually calls @code{execve} with | |
1985 | its arguments as a wrapper. Several standard Unix utilities do | |
1986 | this, e.g.@: @code{env} and @code{nohup}. Any Unix shell script ending | |
1987 | with @code{exec "$@@"} will also work. | |
1988 | ||
1989 | For example, you can use @code{env} to pass an environment variable to | |
1990 | the debugged program, without setting the variable in your shell's | |
1991 | environment: | |
1992 | ||
1993 | @smallexample | |
1994 | (@value{GDBP}) set exec-wrapper env 'LD_PRELOAD=libtest.so' | |
1995 | (@value{GDBP}) run | |
1996 | @end smallexample | |
1997 | ||
1998 | This command is available when debugging locally on most targets, excluding | |
1999 | @sc{djgpp}, Cygwin, MS Windows, and QNX Neutrino. | |
2000 | ||
10568435 JK |
2001 | @kindex set disable-randomization |
2002 | @item set disable-randomization | |
2003 | @itemx set disable-randomization on | |
2004 | This option (enabled by default in @value{GDBN}) will turn off the native | |
2005 | randomization of the virtual address space of the started program. This option | |
2006 | is useful for multiple debugging sessions to make the execution better | |
2007 | reproducible and memory addresses reusable across debugging sessions. | |
2008 | ||
2009 | This feature is implemented only on @sc{gnu}/Linux. You can get the same | |
2010 | behavior using | |
2011 | ||
2012 | @smallexample | |
2013 | (@value{GDBP}) set exec-wrapper setarch `uname -m` -R | |
2014 | @end smallexample | |
2015 | ||
2016 | @item set disable-randomization off | |
2017 | Leave the behavior of the started executable unchanged. Some bugs rear their | |
2018 | ugly heads only when the program is loaded at certain addresses. If your bug | |
2019 | disappears when you run the program under @value{GDBN}, that might be because | |
2020 | @value{GDBN} by default disables the address randomization on platforms, such | |
2021 | as @sc{gnu}/Linux, which do that for stand-alone programs. Use @kbd{set | |
2022 | disable-randomization off} to try to reproduce such elusive bugs. | |
2023 | ||
2024 | The virtual address space randomization is implemented only on @sc{gnu}/Linux. | |
2025 | It protects the programs against some kinds of security attacks. In these | |
2026 | cases the attacker needs to know the exact location of a concrete executable | |
2027 | code. Randomizing its location makes it impossible to inject jumps misusing | |
2028 | a code at its expected addresses. | |
2029 | ||
2030 | Prelinking shared libraries provides a startup performance advantage but it | |
2031 | makes addresses in these libraries predictable for privileged processes by | |
2032 | having just unprivileged access at the target system. Reading the shared | |
2033 | library binary gives enough information for assembling the malicious code | |
2034 | misusing it. Still even a prelinked shared library can get loaded at a new | |
2035 | random address just requiring the regular relocation process during the | |
2036 | startup. Shared libraries not already prelinked are always loaded at | |
2037 | a randomly chosen address. | |
2038 | ||
2039 | Position independent executables (PIE) contain position independent code | |
2040 | similar to the shared libraries and therefore such executables get loaded at | |
2041 | a randomly chosen address upon startup. PIE executables always load even | |
2042 | already prelinked shared libraries at a random address. You can build such | |
2043 | executable using @command{gcc -fPIE -pie}. | |
2044 | ||
2045 | Heap (malloc storage), stack and custom mmap areas are always placed randomly | |
2046 | (as long as the randomization is enabled). | |
2047 | ||
2048 | @item show disable-randomization | |
2049 | Show the current setting of the explicit disable of the native randomization of | |
2050 | the virtual address space of the started program. | |
2051 | ||
4e8b0763 JB |
2052 | @end table |
2053 | ||
6d2ebf8b | 2054 | @node Arguments |
79a6e687 | 2055 | @section Your Program's Arguments |
c906108c SS |
2056 | |
2057 | @cindex arguments (to your program) | |
2058 | The arguments to your program can be specified by the arguments of the | |
5d161b24 | 2059 | @code{run} command. |
c906108c SS |
2060 | They are passed to a shell, which expands wildcard characters and |
2061 | performs redirection of I/O, and thence to your program. Your | |
2062 | @code{SHELL} environment variable (if it exists) specifies what shell | |
2063 | @value{GDBN} uses. If you do not define @code{SHELL}, @value{GDBN} uses | |
d4f3574e SS |
2064 | the default shell (@file{/bin/sh} on Unix). |
2065 | ||
2066 | On non-Unix systems, the program is usually invoked directly by | |
2067 | @value{GDBN}, which emulates I/O redirection via the appropriate system | |
2068 | calls, and the wildcard characters are expanded by the startup code of | |
2069 | the program, not by the shell. | |
c906108c SS |
2070 | |
2071 | @code{run} with no arguments uses the same arguments used by the previous | |
2072 | @code{run}, or those set by the @code{set args} command. | |
2073 | ||
c906108c | 2074 | @table @code |
41afff9a | 2075 | @kindex set args |
c906108c SS |
2076 | @item set args |
2077 | Specify the arguments to be used the next time your program is run. If | |
2078 | @code{set args} has no arguments, @code{run} executes your program | |
2079 | with no arguments. Once you have run your program with arguments, | |
2080 | using @code{set args} before the next @code{run} is the only way to run | |
2081 | it again without arguments. | |
2082 | ||
2083 | @kindex show args | |
2084 | @item show args | |
2085 | Show the arguments to give your program when it is started. | |
2086 | @end table | |
2087 | ||
6d2ebf8b | 2088 | @node Environment |
79a6e687 | 2089 | @section Your Program's Environment |
c906108c SS |
2090 | |
2091 | @cindex environment (of your program) | |
2092 | The @dfn{environment} consists of a set of environment variables and | |
2093 | their values. Environment variables conventionally record such things as | |
2094 | your user name, your home directory, your terminal type, and your search | |
2095 | path for programs to run. Usually you set up environment variables with | |
2096 | the shell and they are inherited by all the other programs you run. When | |
2097 | debugging, it can be useful to try running your program with a modified | |
2098 | environment without having to start @value{GDBN} over again. | |
2099 | ||
2100 | @table @code | |
2101 | @kindex path | |
2102 | @item path @var{directory} | |
2103 | Add @var{directory} to the front of the @code{PATH} environment variable | |
17cc6a06 EZ |
2104 | (the search path for executables) that will be passed to your program. |
2105 | The value of @code{PATH} used by @value{GDBN} does not change. | |
d4f3574e SS |
2106 | You may specify several directory names, separated by whitespace or by a |
2107 | system-dependent separator character (@samp{:} on Unix, @samp{;} on | |
2108 | MS-DOS and MS-Windows). If @var{directory} is already in the path, it | |
2109 | is moved to the front, so it is searched sooner. | |
c906108c SS |
2110 | |
2111 | You can use the string @samp{$cwd} to refer to whatever is the current | |
2112 | working directory at the time @value{GDBN} searches the path. If you | |
2113 | use @samp{.} instead, it refers to the directory where you executed the | |
2114 | @code{path} command. @value{GDBN} replaces @samp{.} in the | |
2115 | @var{directory} argument (with the current path) before adding | |
2116 | @var{directory} to the search path. | |
2117 | @c 'path' is explicitly nonrepeatable, but RMS points out it is silly to | |
2118 | @c document that, since repeating it would be a no-op. | |
2119 | ||
2120 | @kindex show paths | |
2121 | @item show paths | |
2122 | Display the list of search paths for executables (the @code{PATH} | |
2123 | environment variable). | |
2124 | ||
2125 | @kindex show environment | |
2126 | @item show environment @r{[}@var{varname}@r{]} | |
2127 | Print the value of environment variable @var{varname} to be given to | |
2128 | your program when it starts. If you do not supply @var{varname}, | |
2129 | print the names and values of all environment variables to be given to | |
2130 | your program. You can abbreviate @code{environment} as @code{env}. | |
2131 | ||
2132 | @kindex set environment | |
53a5351d | 2133 | @item set environment @var{varname} @r{[}=@var{value}@r{]} |
c906108c SS |
2134 | Set environment variable @var{varname} to @var{value}. The value |
2135 | changes for your program only, not for @value{GDBN} itself. @var{value} may | |
2136 | be any string; the values of environment variables are just strings, and | |
2137 | any interpretation is supplied by your program itself. The @var{value} | |
2138 | parameter is optional; if it is eliminated, the variable is set to a | |
2139 | null value. | |
2140 | @c "any string" here does not include leading, trailing | |
2141 | @c blanks. Gnu asks: does anyone care? | |
2142 | ||
2143 | For example, this command: | |
2144 | ||
474c8240 | 2145 | @smallexample |
c906108c | 2146 | set env USER = foo |
474c8240 | 2147 | @end smallexample |
c906108c SS |
2148 | |
2149 | @noindent | |
d4f3574e | 2150 | tells the debugged program, when subsequently run, that its user is named |
c906108c SS |
2151 | @samp{foo}. (The spaces around @samp{=} are used for clarity here; they |
2152 | are not actually required.) | |
2153 | ||
2154 | @kindex unset environment | |
2155 | @item unset environment @var{varname} | |
2156 | Remove variable @var{varname} from the environment to be passed to your | |
2157 | program. This is different from @samp{set env @var{varname} =}; | |
2158 | @code{unset environment} removes the variable from the environment, | |
2159 | rather than assigning it an empty value. | |
2160 | @end table | |
2161 | ||
d4f3574e SS |
2162 | @emph{Warning:} On Unix systems, @value{GDBN} runs your program using |
2163 | the shell indicated | |
c906108c SS |
2164 | by your @code{SHELL} environment variable if it exists (or |
2165 | @code{/bin/sh} if not). If your @code{SHELL} variable names a shell | |
2166 | that runs an initialization file---such as @file{.cshrc} for C-shell, or | |
2167 | @file{.bashrc} for BASH---any variables you set in that file affect | |
2168 | your program. You may wish to move setting of environment variables to | |
2169 | files that are only run when you sign on, such as @file{.login} or | |
2170 | @file{.profile}. | |
2171 | ||
6d2ebf8b | 2172 | @node Working Directory |
79a6e687 | 2173 | @section Your Program's Working Directory |
c906108c SS |
2174 | |
2175 | @cindex working directory (of your program) | |
2176 | Each time you start your program with @code{run}, it inherits its | |
2177 | working directory from the current working directory of @value{GDBN}. | |
2178 | The @value{GDBN} working directory is initially whatever it inherited | |
2179 | from its parent process (typically the shell), but you can specify a new | |
2180 | working directory in @value{GDBN} with the @code{cd} command. | |
2181 | ||
2182 | The @value{GDBN} working directory also serves as a default for the commands | |
2183 | that specify files for @value{GDBN} to operate on. @xref{Files, ,Commands to | |
79a6e687 | 2184 | Specify Files}. |
c906108c SS |
2185 | |
2186 | @table @code | |
2187 | @kindex cd | |
721c2651 | 2188 | @cindex change working directory |
c906108c SS |
2189 | @item cd @var{directory} |
2190 | Set the @value{GDBN} working directory to @var{directory}. | |
2191 | ||
2192 | @kindex pwd | |
2193 | @item pwd | |
2194 | Print the @value{GDBN} working directory. | |
2195 | @end table | |
2196 | ||
60bf7e09 EZ |
2197 | It is generally impossible to find the current working directory of |
2198 | the process being debugged (since a program can change its directory | |
2199 | during its run). If you work on a system where @value{GDBN} is | |
2200 | configured with the @file{/proc} support, you can use the @code{info | |
2201 | proc} command (@pxref{SVR4 Process Information}) to find out the | |
2202 | current working directory of the debuggee. | |
2203 | ||
6d2ebf8b | 2204 | @node Input/Output |
79a6e687 | 2205 | @section Your Program's Input and Output |
c906108c SS |
2206 | |
2207 | @cindex redirection | |
2208 | @cindex i/o | |
2209 | @cindex terminal | |
2210 | By default, the program you run under @value{GDBN} does input and output to | |
5d161b24 | 2211 | the same terminal that @value{GDBN} uses. @value{GDBN} switches the terminal |
c906108c SS |
2212 | to its own terminal modes to interact with you, but it records the terminal |
2213 | modes your program was using and switches back to them when you continue | |
2214 | running your program. | |
2215 | ||
2216 | @table @code | |
2217 | @kindex info terminal | |
2218 | @item info terminal | |
2219 | Displays information recorded by @value{GDBN} about the terminal modes your | |
2220 | program is using. | |
2221 | @end table | |
2222 | ||
2223 | You can redirect your program's input and/or output using shell | |
2224 | redirection with the @code{run} command. For example, | |
2225 | ||
474c8240 | 2226 | @smallexample |
c906108c | 2227 | run > outfile |
474c8240 | 2228 | @end smallexample |
c906108c SS |
2229 | |
2230 | @noindent | |
2231 | starts your program, diverting its output to the file @file{outfile}. | |
2232 | ||
2233 | @kindex tty | |
2234 | @cindex controlling terminal | |
2235 | Another way to specify where your program should do input and output is | |
2236 | with the @code{tty} command. This command accepts a file name as | |
2237 | argument, and causes this file to be the default for future @code{run} | |
2238 | commands. It also resets the controlling terminal for the child | |
2239 | process, for future @code{run} commands. For example, | |
2240 | ||
474c8240 | 2241 | @smallexample |
c906108c | 2242 | tty /dev/ttyb |
474c8240 | 2243 | @end smallexample |
c906108c SS |
2244 | |
2245 | @noindent | |
2246 | directs that processes started with subsequent @code{run} commands | |
2247 | default to do input and output on the terminal @file{/dev/ttyb} and have | |
2248 | that as their controlling terminal. | |
2249 | ||
2250 | An explicit redirection in @code{run} overrides the @code{tty} command's | |
2251 | effect on the input/output device, but not its effect on the controlling | |
2252 | terminal. | |
2253 | ||
2254 | When you use the @code{tty} command or redirect input in the @code{run} | |
2255 | command, only the input @emph{for your program} is affected. The input | |
3cb3b8df BR |
2256 | for @value{GDBN} still comes from your terminal. @code{tty} is an alias |
2257 | for @code{set inferior-tty}. | |
2258 | ||
2259 | @cindex inferior tty | |
2260 | @cindex set inferior controlling terminal | |
2261 | You can use the @code{show inferior-tty} command to tell @value{GDBN} to | |
2262 | display the name of the terminal that will be used for future runs of your | |
2263 | program. | |
2264 | ||
2265 | @table @code | |
2266 | @item set inferior-tty /dev/ttyb | |
2267 | @kindex set inferior-tty | |
2268 | Set the tty for the program being debugged to /dev/ttyb. | |
2269 | ||
2270 | @item show inferior-tty | |
2271 | @kindex show inferior-tty | |
2272 | Show the current tty for the program being debugged. | |
2273 | @end table | |
c906108c | 2274 | |
6d2ebf8b | 2275 | @node Attach |
79a6e687 | 2276 | @section Debugging an Already-running Process |
c906108c SS |
2277 | @kindex attach |
2278 | @cindex attach | |
2279 | ||
2280 | @table @code | |
2281 | @item attach @var{process-id} | |
2282 | This command attaches to a running process---one that was started | |
2283 | outside @value{GDBN}. (@code{info files} shows your active | |
2284 | targets.) The command takes as argument a process ID. The usual way to | |
09d4efe1 | 2285 | find out the @var{process-id} of a Unix process is with the @code{ps} utility, |
c906108c SS |
2286 | or with the @samp{jobs -l} shell command. |
2287 | ||
2288 | @code{attach} does not repeat if you press @key{RET} a second time after | |
2289 | executing the command. | |
2290 | @end table | |
2291 | ||
2292 | To use @code{attach}, your program must be running in an environment | |
2293 | which supports processes; for example, @code{attach} does not work for | |
2294 | programs on bare-board targets that lack an operating system. You must | |
2295 | also have permission to send the process a signal. | |
2296 | ||
2297 | When you use @code{attach}, the debugger finds the program running in | |
2298 | the process first by looking in the current working directory, then (if | |
2299 | the program is not found) by using the source file search path | |
79a6e687 | 2300 | (@pxref{Source Path, ,Specifying Source Directories}). You can also use |
c906108c SS |
2301 | the @code{file} command to load the program. @xref{Files, ,Commands to |
2302 | Specify Files}. | |
2303 | ||
2304 | The first thing @value{GDBN} does after arranging to debug the specified | |
2305 | process is to stop it. You can examine and modify an attached process | |
53a5351d JM |
2306 | with all the @value{GDBN} commands that are ordinarily available when |
2307 | you start processes with @code{run}. You can insert breakpoints; you | |
2308 | can step and continue; you can modify storage. If you would rather the | |
2309 | process continue running, you may use the @code{continue} command after | |
c906108c SS |
2310 | attaching @value{GDBN} to the process. |
2311 | ||
2312 | @table @code | |
2313 | @kindex detach | |
2314 | @item detach | |
2315 | When you have finished debugging the attached process, you can use the | |
2316 | @code{detach} command to release it from @value{GDBN} control. Detaching | |
2317 | the process continues its execution. After the @code{detach} command, | |
2318 | that process and @value{GDBN} become completely independent once more, and you | |
2319 | are ready to @code{attach} another process or start one with @code{run}. | |
2320 | @code{detach} does not repeat if you press @key{RET} again after | |
2321 | executing the command. | |
2322 | @end table | |
2323 | ||
159fcc13 JK |
2324 | If you exit @value{GDBN} while you have an attached process, you detach |
2325 | that process. If you use the @code{run} command, you kill that process. | |
2326 | By default, @value{GDBN} asks for confirmation if you try to do either of these | |
2327 | things; you can control whether or not you need to confirm by using the | |
2328 | @code{set confirm} command (@pxref{Messages/Warnings, ,Optional Warnings and | |
79a6e687 | 2329 | Messages}). |
c906108c | 2330 | |
6d2ebf8b | 2331 | @node Kill Process |
79a6e687 | 2332 | @section Killing the Child Process |
c906108c SS |
2333 | |
2334 | @table @code | |
2335 | @kindex kill | |
2336 | @item kill | |
2337 | Kill the child process in which your program is running under @value{GDBN}. | |
2338 | @end table | |
2339 | ||
2340 | This command is useful if you wish to debug a core dump instead of a | |
2341 | running process. @value{GDBN} ignores any core dump file while your program | |
2342 | is running. | |
2343 | ||
2344 | On some operating systems, a program cannot be executed outside @value{GDBN} | |
2345 | while you have breakpoints set on it inside @value{GDBN}. You can use the | |
2346 | @code{kill} command in this situation to permit running your program | |
2347 | outside the debugger. | |
2348 | ||
2349 | The @code{kill} command is also useful if you wish to recompile and | |
2350 | relink your program, since on many systems it is impossible to modify an | |
2351 | executable file while it is running in a process. In this case, when you | |
2352 | next type @code{run}, @value{GDBN} notices that the file has changed, and | |
2353 | reads the symbol table again (while trying to preserve your current | |
2354 | breakpoint settings). | |
2355 | ||
6c95b8df PA |
2356 | @node Inferiors and Programs |
2357 | @section Debugging Multiple Inferiors and Programs | |
b77209e0 | 2358 | |
6c95b8df PA |
2359 | @value{GDBN} lets you run and debug multiple programs in a single |
2360 | session. In addition, @value{GDBN} on some systems may let you run | |
2361 | several programs simultaneously (otherwise you have to exit from one | |
2362 | before starting another). In the most general case, you can have | |
2363 | multiple threads of execution in each of multiple processes, launched | |
2364 | from multiple executables. | |
b77209e0 PA |
2365 | |
2366 | @cindex inferior | |
2367 | @value{GDBN} represents the state of each program execution with an | |
2368 | object called an @dfn{inferior}. An inferior typically corresponds to | |
2369 | a process, but is more general and applies also to targets that do not | |
2370 | have processes. Inferiors may be created before a process runs, and | |
6c95b8df PA |
2371 | may be retained after a process exits. Inferiors have unique |
2372 | identifiers that are different from process ids. Usually each | |
2373 | inferior will also have its own distinct address space, although some | |
2374 | embedded targets may have several inferiors running in different parts | |
2375 | of a single address space. Each inferior may in turn have multiple | |
2376 | threads running in it. | |
b77209e0 | 2377 | |
6c95b8df PA |
2378 | To find out what inferiors exist at any moment, use @w{@code{info |
2379 | inferiors}}: | |
b77209e0 PA |
2380 | |
2381 | @table @code | |
2382 | @kindex info inferiors | |
2383 | @item info inferiors | |
2384 | Print a list of all inferiors currently being managed by @value{GDBN}. | |
3a1ff0b6 PA |
2385 | |
2386 | @value{GDBN} displays for each inferior (in this order): | |
2387 | ||
2388 | @enumerate | |
2389 | @item | |
2390 | the inferior number assigned by @value{GDBN} | |
2391 | ||
2392 | @item | |
2393 | the target system's inferior identifier | |
6c95b8df PA |
2394 | |
2395 | @item | |
2396 | the name of the executable the inferior is running. | |
2397 | ||
3a1ff0b6 PA |
2398 | @end enumerate |
2399 | ||
2400 | @noindent | |
2401 | An asterisk @samp{*} preceding the @value{GDBN} inferior number | |
2402 | indicates the current inferior. | |
2403 | ||
2404 | For example, | |
2277426b | 2405 | @end table |
3a1ff0b6 PA |
2406 | @c end table here to get a little more width for example |
2407 | ||
2408 | @smallexample | |
2409 | (@value{GDBP}) info inferiors | |
6c95b8df PA |
2410 | Num Description Executable |
2411 | 2 process 2307 hello | |
2412 | * 1 process 3401 goodbye | |
3a1ff0b6 | 2413 | @end smallexample |
2277426b PA |
2414 | |
2415 | To switch focus between inferiors, use the @code{inferior} command: | |
2416 | ||
2417 | @table @code | |
3a1ff0b6 PA |
2418 | @kindex inferior @var{infno} |
2419 | @item inferior @var{infno} | |
2420 | Make inferior number @var{infno} the current inferior. The argument | |
2421 | @var{infno} is the inferior number assigned by @value{GDBN}, as shown | |
2422 | in the first field of the @samp{info inferiors} display. | |
2277426b PA |
2423 | @end table |
2424 | ||
6c95b8df PA |
2425 | |
2426 | You can get multiple executables into a debugging session via the | |
2427 | @code{add-inferior} and @w{@code{clone-inferior}} commands. On some | |
2428 | systems @value{GDBN} can add inferiors to the debug session | |
2429 | automatically by following calls to @code{fork} and @code{exec}. To | |
2430 | remove inferiors from the debugging session use the | |
2431 | @w{@code{remove-inferior}} command. | |
2432 | ||
2433 | @table @code | |
2434 | @kindex add-inferior | |
2435 | @item add-inferior [ -copies @var{n} ] [ -exec @var{executable} ] | |
2436 | Adds @var{n} inferiors to be run using @var{executable} as the | |
2437 | executable. @var{n} defaults to 1. If no executable is specified, | |
2438 | the inferiors begins empty, with no program. You can still assign or | |
2439 | change the program assigned to the inferior at any time by using the | |
2440 | @code{file} command with the executable name as its argument. | |
2441 | ||
2442 | @kindex clone-inferior | |
2443 | @item clone-inferior [ -copies @var{n} ] [ @var{infno} ] | |
2444 | Adds @var{n} inferiors ready to execute the same program as inferior | |
2445 | @var{infno}. @var{n} defaults to 1. @var{infno} defaults to the | |
2446 | number of the current inferior. This is a convenient command when you | |
2447 | want to run another instance of the inferior you are debugging. | |
2448 | ||
2449 | @smallexample | |
2450 | (@value{GDBP}) info inferiors | |
2451 | Num Description Executable | |
2452 | * 1 process 29964 helloworld | |
2453 | (@value{GDBP}) clone-inferior | |
2454 | Added inferior 2. | |
2455 | 1 inferiors added. | |
2456 | (@value{GDBP}) info inferiors | |
2457 | Num Description Executable | |
2458 | 2 <null> helloworld | |
2459 | * 1 process 29964 helloworld | |
2460 | @end smallexample | |
2461 | ||
2462 | You can now simply switch focus to inferior 2 and run it. | |
2463 | ||
2464 | @kindex remove-inferior | |
2465 | @item remove-inferior @var{infno} | |
2466 | Removes the inferior @var{infno}. It is not possible to remove an | |
2467 | inferior that is running with this command. For those, use the | |
2468 | @code{kill} or @code{detach} command first. | |
2469 | ||
2470 | @end table | |
2471 | ||
2472 | To quit debugging one of the running inferiors that is not the current | |
2473 | inferior, you can either detach from it by using the @w{@code{detach | |
2474 | inferior}} command (allowing it to run independently), or kill it | |
2475 | using the @w{@code{kill inferior}} command: | |
2277426b PA |
2476 | |
2477 | @table @code | |
3a1ff0b6 PA |
2478 | @kindex detach inferior @var{infno} |
2479 | @item detach inferior @var{infno} | |
2277426b | 2480 | Detach from the inferior identified by @value{GDBN} inferior number |
3a1ff0b6 | 2481 | @var{infno}, and remove it from the inferior list. |
2277426b | 2482 | |
3a1ff0b6 PA |
2483 | @kindex kill inferior @var{infno} |
2484 | @item kill inferior @var{infno} | |
2277426b | 2485 | Kill the inferior identified by @value{GDBN} inferior number |
3a1ff0b6 | 2486 | @var{infno}, and remove it from the inferior list. |
2277426b PA |
2487 | @end table |
2488 | ||
6c95b8df PA |
2489 | After the successful completion of a command such as @code{detach}, |
2490 | @code{detach inferior}, @code{kill} or @code{kill inferior}, or after | |
2491 | a normal process exit, the inferior is still valid and listed with | |
2492 | @code{info inferiors}, ready to be restarted. | |
2493 | ||
2494 | ||
2277426b PA |
2495 | To be notified when inferiors are started or exit under @value{GDBN}'s |
2496 | control use @w{@code{set print inferior-events}}: | |
b77209e0 | 2497 | |
2277426b | 2498 | @table @code |
b77209e0 PA |
2499 | @kindex set print inferior-events |
2500 | @cindex print messages on inferior start and exit | |
2501 | @item set print inferior-events | |
2502 | @itemx set print inferior-events on | |
2503 | @itemx set print inferior-events off | |
2504 | The @code{set print inferior-events} command allows you to enable or | |
2505 | disable printing of messages when @value{GDBN} notices that new | |
2506 | inferiors have started or that inferiors have exited or have been | |
2507 | detached. By default, these messages will not be printed. | |
2508 | ||
2509 | @kindex show print inferior-events | |
2510 | @item show print inferior-events | |
2511 | Show whether messages will be printed when @value{GDBN} detects that | |
2512 | inferiors have started, exited or have been detached. | |
2513 | @end table | |
2514 | ||
6c95b8df PA |
2515 | Many commands will work the same with multiple programs as with a |
2516 | single program: e.g., @code{print myglobal} will simply display the | |
2517 | value of @code{myglobal} in the current inferior. | |
2518 | ||
2519 | ||
2520 | Occasionaly, when debugging @value{GDBN} itself, it may be useful to | |
2521 | get more info about the relationship of inferiors, programs, address | |
2522 | spaces in a debug session. You can do that with the @w{@code{maint | |
2523 | info program-spaces}} command. | |
2524 | ||
2525 | @table @code | |
2526 | @kindex maint info program-spaces | |
2527 | @item maint info program-spaces | |
2528 | Print a list of all program spaces currently being managed by | |
2529 | @value{GDBN}. | |
2530 | ||
2531 | @value{GDBN} displays for each program space (in this order): | |
2532 | ||
2533 | @enumerate | |
2534 | @item | |
2535 | the program space number assigned by @value{GDBN} | |
2536 | ||
2537 | @item | |
2538 | the name of the executable loaded into the program space, with e.g., | |
2539 | the @code{file} command. | |
2540 | ||
2541 | @end enumerate | |
2542 | ||
2543 | @noindent | |
2544 | An asterisk @samp{*} preceding the @value{GDBN} program space number | |
2545 | indicates the current program space. | |
2546 | ||
2547 | In addition, below each program space line, @value{GDBN} prints extra | |
2548 | information that isn't suitable to display in tabular form. For | |
2549 | example, the list of inferiors bound to the program space. | |
2550 | ||
2551 | @smallexample | |
2552 | (@value{GDBP}) maint info program-spaces | |
2553 | Id Executable | |
2554 | 2 goodbye | |
2555 | Bound inferiors: ID 1 (process 21561) | |
2556 | * 1 hello | |
2557 | @end smallexample | |
2558 | ||
2559 | Here we can see that no inferior is running the program @code{hello}, | |
2560 | while @code{process 21561} is running the program @code{goodbye}. On | |
2561 | some targets, it is possible that multiple inferiors are bound to the | |
2562 | same program space. The most common example is that of debugging both | |
2563 | the parent and child processes of a @code{vfork} call. For example, | |
2564 | ||
2565 | @smallexample | |
2566 | (@value{GDBP}) maint info program-spaces | |
2567 | Id Executable | |
2568 | * 1 vfork-test | |
2569 | Bound inferiors: ID 2 (process 18050), ID 1 (process 18045) | |
2570 | @end smallexample | |
2571 | ||
2572 | Here, both inferior 2 and inferior 1 are running in the same program | |
2573 | space as a result of inferior 1 having executed a @code{vfork} call. | |
2574 | @end table | |
2575 | ||
6d2ebf8b | 2576 | @node Threads |
79a6e687 | 2577 | @section Debugging Programs with Multiple Threads |
c906108c SS |
2578 | |
2579 | @cindex threads of execution | |
2580 | @cindex multiple threads | |
2581 | @cindex switching threads | |
2582 | In some operating systems, such as HP-UX and Solaris, a single program | |
2583 | may have more than one @dfn{thread} of execution. The precise semantics | |
2584 | of threads differ from one operating system to another, but in general | |
2585 | the threads of a single program are akin to multiple processes---except | |
2586 | that they share one address space (that is, they can all examine and | |
2587 | modify the same variables). On the other hand, each thread has its own | |
2588 | registers and execution stack, and perhaps private memory. | |
2589 | ||
2590 | @value{GDBN} provides these facilities for debugging multi-thread | |
2591 | programs: | |
2592 | ||
2593 | @itemize @bullet | |
2594 | @item automatic notification of new threads | |
2595 | @item @samp{thread @var{threadno}}, a command to switch among threads | |
2596 | @item @samp{info threads}, a command to inquire about existing threads | |
5d161b24 | 2597 | @item @samp{thread apply [@var{threadno}] [@var{all}] @var{args}}, |
c906108c SS |
2598 | a command to apply a command to a list of threads |
2599 | @item thread-specific breakpoints | |
93815fbf VP |
2600 | @item @samp{set print thread-events}, which controls printing of |
2601 | messages on thread start and exit. | |
17a37d48 PP |
2602 | @item @samp{set libthread-db-search-path @var{path}}, which lets |
2603 | the user specify which @code{libthread_db} to use if the default choice | |
2604 | isn't compatible with the program. | |
c906108c SS |
2605 | @end itemize |
2606 | ||
c906108c SS |
2607 | @quotation |
2608 | @emph{Warning:} These facilities are not yet available on every | |
2609 | @value{GDBN} configuration where the operating system supports threads. | |
2610 | If your @value{GDBN} does not support threads, these commands have no | |
2611 | effect. For example, a system without thread support shows no output | |
2612 | from @samp{info threads}, and always rejects the @code{thread} command, | |
2613 | like this: | |
2614 | ||
2615 | @smallexample | |
2616 | (@value{GDBP}) info threads | |
2617 | (@value{GDBP}) thread 1 | |
2618 | Thread ID 1 not known. Use the "info threads" command to | |
2619 | see the IDs of currently known threads. | |
2620 | @end smallexample | |
2621 | @c FIXME to implementors: how hard would it be to say "sorry, this GDB | |
2622 | @c doesn't support threads"? | |
2623 | @end quotation | |
c906108c SS |
2624 | |
2625 | @cindex focus of debugging | |
2626 | @cindex current thread | |
2627 | The @value{GDBN} thread debugging facility allows you to observe all | |
2628 | threads while your program runs---but whenever @value{GDBN} takes | |
2629 | control, one thread in particular is always the focus of debugging. | |
2630 | This thread is called the @dfn{current thread}. Debugging commands show | |
2631 | program information from the perspective of the current thread. | |
2632 | ||
41afff9a | 2633 | @cindex @code{New} @var{systag} message |
c906108c SS |
2634 | @cindex thread identifier (system) |
2635 | @c FIXME-implementors!! It would be more helpful if the [New...] message | |
2636 | @c included GDB's numeric thread handle, so you could just go to that | |
2637 | @c thread without first checking `info threads'. | |
2638 | Whenever @value{GDBN} detects a new thread in your program, it displays | |
2639 | the target system's identification for the thread with a message in the | |
2640 | form @samp{[New @var{systag}]}. @var{systag} is a thread identifier | |
2641 | whose form varies depending on the particular system. For example, on | |
8807d78b | 2642 | @sc{gnu}/Linux, you might see |
c906108c | 2643 | |
474c8240 | 2644 | @smallexample |
8807d78b | 2645 | [New Thread 46912507313328 (LWP 25582)] |
474c8240 | 2646 | @end smallexample |
c906108c SS |
2647 | |
2648 | @noindent | |
2649 | when @value{GDBN} notices a new thread. In contrast, on an SGI system, | |
2650 | the @var{systag} is simply something like @samp{process 368}, with no | |
2651 | further qualifier. | |
2652 | ||
2653 | @c FIXME!! (1) Does the [New...] message appear even for the very first | |
2654 | @c thread of a program, or does it only appear for the | |
6ca652b0 | 2655 | @c second---i.e.@: when it becomes obvious we have a multithread |
c906108c SS |
2656 | @c program? |
2657 | @c (2) *Is* there necessarily a first thread always? Or do some | |
2658 | @c multithread systems permit starting a program with multiple | |
5d161b24 | 2659 | @c threads ab initio? |
c906108c SS |
2660 | |
2661 | @cindex thread number | |
2662 | @cindex thread identifier (GDB) | |
2663 | For debugging purposes, @value{GDBN} associates its own thread | |
2664 | number---always a single integer---with each thread in your program. | |
2665 | ||
2666 | @table @code | |
2667 | @kindex info threads | |
2668 | @item info threads | |
2669 | Display a summary of all threads currently in your | |
2670 | program. @value{GDBN} displays for each thread (in this order): | |
2671 | ||
2672 | @enumerate | |
09d4efe1 EZ |
2673 | @item |
2674 | the thread number assigned by @value{GDBN} | |
c906108c | 2675 | |
09d4efe1 EZ |
2676 | @item |
2677 | the target system's thread identifier (@var{systag}) | |
c906108c | 2678 | |
09d4efe1 EZ |
2679 | @item |
2680 | the current stack frame summary for that thread | |
c906108c SS |
2681 | @end enumerate |
2682 | ||
2683 | @noindent | |
2684 | An asterisk @samp{*} to the left of the @value{GDBN} thread number | |
2685 | indicates the current thread. | |
2686 | ||
5d161b24 | 2687 | For example, |
c906108c SS |
2688 | @end table |
2689 | @c end table here to get a little more width for example | |
2690 | ||
2691 | @smallexample | |
2692 | (@value{GDBP}) info threads | |
2693 | 3 process 35 thread 27 0x34e5 in sigpause () | |
2694 | 2 process 35 thread 23 0x34e5 in sigpause () | |
2695 | * 1 process 35 thread 13 main (argc=1, argv=0x7ffffff8) | |
2696 | at threadtest.c:68 | |
2697 | @end smallexample | |
53a5351d JM |
2698 | |
2699 | On HP-UX systems: | |
c906108c | 2700 | |
4644b6e3 EZ |
2701 | @cindex debugging multithreaded programs (on HP-UX) |
2702 | @cindex thread identifier (GDB), on HP-UX | |
c906108c SS |
2703 | For debugging purposes, @value{GDBN} associates its own thread |
2704 | number---a small integer assigned in thread-creation order---with each | |
2705 | thread in your program. | |
2706 | ||
41afff9a EZ |
2707 | @cindex @code{New} @var{systag} message, on HP-UX |
2708 | @cindex thread identifier (system), on HP-UX | |
c906108c SS |
2709 | @c FIXME-implementors!! It would be more helpful if the [New...] message |
2710 | @c included GDB's numeric thread handle, so you could just go to that | |
2711 | @c thread without first checking `info threads'. | |
2712 | Whenever @value{GDBN} detects a new thread in your program, it displays | |
2713 | both @value{GDBN}'s thread number and the target system's identification for the thread with a message in the | |
2714 | form @samp{[New @var{systag}]}. @var{systag} is a thread identifier | |
2715 | whose form varies depending on the particular system. For example, on | |
2716 | HP-UX, you see | |
2717 | ||
474c8240 | 2718 | @smallexample |
c906108c | 2719 | [New thread 2 (system thread 26594)] |
474c8240 | 2720 | @end smallexample |
c906108c SS |
2721 | |
2722 | @noindent | |
5d161b24 | 2723 | when @value{GDBN} notices a new thread. |
c906108c SS |
2724 | |
2725 | @table @code | |
4644b6e3 | 2726 | @kindex info threads (HP-UX) |
c906108c SS |
2727 | @item info threads |
2728 | Display a summary of all threads currently in your | |
2729 | program. @value{GDBN} displays for each thread (in this order): | |
2730 | ||
2731 | @enumerate | |
2732 | @item the thread number assigned by @value{GDBN} | |
2733 | ||
2734 | @item the target system's thread identifier (@var{systag}) | |
2735 | ||
2736 | @item the current stack frame summary for that thread | |
2737 | @end enumerate | |
2738 | ||
2739 | @noindent | |
2740 | An asterisk @samp{*} to the left of the @value{GDBN} thread number | |
2741 | indicates the current thread. | |
2742 | ||
5d161b24 | 2743 | For example, |
c906108c SS |
2744 | @end table |
2745 | @c end table here to get a little more width for example | |
2746 | ||
474c8240 | 2747 | @smallexample |
c906108c | 2748 | (@value{GDBP}) info threads |
6d2ebf8b SS |
2749 | * 3 system thread 26607 worker (wptr=0x7b09c318 "@@") \@* |
2750 | at quicksort.c:137 | |
2751 | 2 system thread 26606 0x7b0030d8 in __ksleep () \@* | |
2752 | from /usr/lib/libc.2 | |
2753 | 1 system thread 27905 0x7b003498 in _brk () \@* | |
2754 | from /usr/lib/libc.2 | |
474c8240 | 2755 | @end smallexample |
c906108c | 2756 | |
c45da7e6 EZ |
2757 | On Solaris, you can display more information about user threads with a |
2758 | Solaris-specific command: | |
2759 | ||
2760 | @table @code | |
2761 | @item maint info sol-threads | |
2762 | @kindex maint info sol-threads | |
2763 | @cindex thread info (Solaris) | |
2764 | Display info on Solaris user threads. | |
2765 | @end table | |
2766 | ||
c906108c SS |
2767 | @table @code |
2768 | @kindex thread @var{threadno} | |
2769 | @item thread @var{threadno} | |
2770 | Make thread number @var{threadno} the current thread. The command | |
2771 | argument @var{threadno} is the internal @value{GDBN} thread number, as | |
2772 | shown in the first field of the @samp{info threads} display. | |
2773 | @value{GDBN} responds by displaying the system identifier of the thread | |
2774 | you selected, and its current stack frame summary: | |
2775 | ||
2776 | @smallexample | |
2777 | @c FIXME!! This example made up; find a @value{GDBN} w/threads and get real one | |
2778 | (@value{GDBP}) thread 2 | |
c906108c | 2779 | [Switching to process 35 thread 23] |
c906108c SS |
2780 | 0x34e5 in sigpause () |
2781 | @end smallexample | |
2782 | ||
2783 | @noindent | |
2784 | As with the @samp{[New @dots{}]} message, the form of the text after | |
2785 | @samp{Switching to} depends on your system's conventions for identifying | |
5d161b24 | 2786 | threads. |
c906108c | 2787 | |
9c16f35a | 2788 | @kindex thread apply |
638ac427 | 2789 | @cindex apply command to several threads |
839c27b7 EZ |
2790 | @item thread apply [@var{threadno}] [@var{all}] @var{command} |
2791 | The @code{thread apply} command allows you to apply the named | |
2792 | @var{command} to one or more threads. Specify the numbers of the | |
2793 | threads that you want affected with the command argument | |
2794 | @var{threadno}. It can be a single thread number, one of the numbers | |
2795 | shown in the first field of the @samp{info threads} display; or it | |
2796 | could be a range of thread numbers, as in @code{2-4}. To apply a | |
2797 | command to all threads, type @kbd{thread apply all @var{command}}. | |
93815fbf VP |
2798 | |
2799 | @kindex set print thread-events | |
2800 | @cindex print messages on thread start and exit | |
2801 | @item set print thread-events | |
2802 | @itemx set print thread-events on | |
2803 | @itemx set print thread-events off | |
2804 | The @code{set print thread-events} command allows you to enable or | |
2805 | disable printing of messages when @value{GDBN} notices that new threads have | |
2806 | started or that threads have exited. By default, these messages will | |
2807 | be printed if detection of these events is supported by the target. | |
2808 | Note that these messages cannot be disabled on all targets. | |
2809 | ||
2810 | @kindex show print thread-events | |
2811 | @item show print thread-events | |
2812 | Show whether messages will be printed when @value{GDBN} detects that threads | |
2813 | have started and exited. | |
c906108c SS |
2814 | @end table |
2815 | ||
79a6e687 | 2816 | @xref{Thread Stops,,Stopping and Starting Multi-thread Programs}, for |
c906108c SS |
2817 | more information about how @value{GDBN} behaves when you stop and start |
2818 | programs with multiple threads. | |
2819 | ||
79a6e687 | 2820 | @xref{Set Watchpoints,,Setting Watchpoints}, for information about |
c906108c | 2821 | watchpoints in programs with multiple threads. |
c906108c | 2822 | |
17a37d48 PP |
2823 | @table @code |
2824 | @kindex set libthread-db-search-path | |
2825 | @cindex search path for @code{libthread_db} | |
2826 | @item set libthread-db-search-path @r{[}@var{path}@r{]} | |
2827 | If this variable is set, @var{path} is a colon-separated list of | |
2828 | directories @value{GDBN} will use to search for @code{libthread_db}. | |
2829 | If you omit @var{path}, @samp{libthread-db-search-path} will be reset to | |
2830 | an empty list. | |
2831 | ||
2832 | On @sc{gnu}/Linux and Solaris systems, @value{GDBN} uses a ``helper'' | |
2833 | @code{libthread_db} library to obtain information about threads in the | |
2834 | inferior process. @value{GDBN} will use @samp{libthread-db-search-path} | |
2835 | to find @code{libthread_db}. If that fails, @value{GDBN} will continue | |
2836 | with default system shared library directories, and finally the directory | |
2837 | from which @code{libpthread} was loaded in the inferior process. | |
2838 | ||
2839 | For any @code{libthread_db} library @value{GDBN} finds in above directories, | |
2840 | @value{GDBN} attempts to initialize it with the current inferior process. | |
2841 | If this initialization fails (which could happen because of a version | |
2842 | mismatch between @code{libthread_db} and @code{libpthread}), @value{GDBN} | |
2843 | will unload @code{libthread_db}, and continue with the next directory. | |
2844 | If none of @code{libthread_db} libraries initialize successfully, | |
2845 | @value{GDBN} will issue a warning and thread debugging will be disabled. | |
2846 | ||
2847 | Setting @code{libthread-db-search-path} is currently implemented | |
2848 | only on some platforms. | |
2849 | ||
2850 | @kindex show libthread-db-search-path | |
2851 | @item show libthread-db-search-path | |
2852 | Display current libthread_db search path. | |
2853 | @end table | |
2854 | ||
6c95b8df PA |
2855 | @node Forks |
2856 | @section Debugging Forks | |
c906108c SS |
2857 | |
2858 | @cindex fork, debugging programs which call | |
2859 | @cindex multiple processes | |
2860 | @cindex processes, multiple | |
53a5351d JM |
2861 | On most systems, @value{GDBN} has no special support for debugging |
2862 | programs which create additional processes using the @code{fork} | |
2863 | function. When a program forks, @value{GDBN} will continue to debug the | |
2864 | parent process and the child process will run unimpeded. If you have | |
2865 | set a breakpoint in any code which the child then executes, the child | |
2866 | will get a @code{SIGTRAP} signal which (unless it catches the signal) | |
2867 | will cause it to terminate. | |
c906108c SS |
2868 | |
2869 | However, if you want to debug the child process there is a workaround | |
2870 | which isn't too painful. Put a call to @code{sleep} in the code which | |
2871 | the child process executes after the fork. It may be useful to sleep | |
2872 | only if a certain environment variable is set, or a certain file exists, | |
2873 | so that the delay need not occur when you don't want to run @value{GDBN} | |
2874 | on the child. While the child is sleeping, use the @code{ps} program to | |
2875 | get its process ID. Then tell @value{GDBN} (a new invocation of | |
2876 | @value{GDBN} if you are also debugging the parent process) to attach to | |
d4f3574e | 2877 | the child process (@pxref{Attach}). From that point on you can debug |
c906108c | 2878 | the child process just like any other process which you attached to. |
c906108c | 2879 | |
b51970ac DJ |
2880 | On some systems, @value{GDBN} provides support for debugging programs that |
2881 | create additional processes using the @code{fork} or @code{vfork} functions. | |
2882 | Currently, the only platforms with this feature are HP-UX (11.x and later | |
a6b151f1 | 2883 | only?) and @sc{gnu}/Linux (kernel version 2.5.60 and later). |
c906108c SS |
2884 | |
2885 | By default, when a program forks, @value{GDBN} will continue to debug | |
2886 | the parent process and the child process will run unimpeded. | |
2887 | ||
2888 | If you want to follow the child process instead of the parent process, | |
2889 | use the command @w{@code{set follow-fork-mode}}. | |
2890 | ||
2891 | @table @code | |
2892 | @kindex set follow-fork-mode | |
2893 | @item set follow-fork-mode @var{mode} | |
2894 | Set the debugger response to a program call of @code{fork} or | |
2895 | @code{vfork}. A call to @code{fork} or @code{vfork} creates a new | |
9c16f35a | 2896 | process. The @var{mode} argument can be: |
c906108c SS |
2897 | |
2898 | @table @code | |
2899 | @item parent | |
2900 | The original process is debugged after a fork. The child process runs | |
2df3850c | 2901 | unimpeded. This is the default. |
c906108c SS |
2902 | |
2903 | @item child | |
2904 | The new process is debugged after a fork. The parent process runs | |
2905 | unimpeded. | |
2906 | ||
c906108c SS |
2907 | @end table |
2908 | ||
9c16f35a | 2909 | @kindex show follow-fork-mode |
c906108c | 2910 | @item show follow-fork-mode |
2df3850c | 2911 | Display the current debugger response to a @code{fork} or @code{vfork} call. |
c906108c SS |
2912 | @end table |
2913 | ||
5c95884b MS |
2914 | @cindex debugging multiple processes |
2915 | On Linux, if you want to debug both the parent and child processes, use the | |
2916 | command @w{@code{set detach-on-fork}}. | |
2917 | ||
2918 | @table @code | |
2919 | @kindex set detach-on-fork | |
2920 | @item set detach-on-fork @var{mode} | |
2921 | Tells gdb whether to detach one of the processes after a fork, or | |
2922 | retain debugger control over them both. | |
2923 | ||
2924 | @table @code | |
2925 | @item on | |
2926 | The child process (or parent process, depending on the value of | |
2927 | @code{follow-fork-mode}) will be detached and allowed to run | |
2928 | independently. This is the default. | |
2929 | ||
2930 | @item off | |
2931 | Both processes will be held under the control of @value{GDBN}. | |
2932 | One process (child or parent, depending on the value of | |
2933 | @code{follow-fork-mode}) is debugged as usual, while the other | |
2934 | is held suspended. | |
2935 | ||
2936 | @end table | |
2937 | ||
11310833 NR |
2938 | @kindex show detach-on-fork |
2939 | @item show detach-on-fork | |
2940 | Show whether detach-on-fork mode is on/off. | |
5c95884b MS |
2941 | @end table |
2942 | ||
2277426b PA |
2943 | If you choose to set @samp{detach-on-fork} mode off, then @value{GDBN} |
2944 | will retain control of all forked processes (including nested forks). | |
2945 | You can list the forked processes under the control of @value{GDBN} by | |
2946 | using the @w{@code{info inferiors}} command, and switch from one fork | |
6c95b8df PA |
2947 | to another by using the @code{inferior} command (@pxref{Inferiors and |
2948 | Programs, ,Debugging Multiple Inferiors and Programs}). | |
5c95884b MS |
2949 | |
2950 | To quit debugging one of the forked processes, you can either detach | |
2277426b PA |
2951 | from it by using the @w{@code{detach inferior}} command (allowing it |
2952 | to run independently), or kill it using the @w{@code{kill inferior}} | |
6c95b8df PA |
2953 | command. @xref{Inferiors and Programs, ,Debugging Multiple Inferiors |
2954 | and Programs}. | |
5c95884b | 2955 | |
c906108c SS |
2956 | If you ask to debug a child process and a @code{vfork} is followed by an |
2957 | @code{exec}, @value{GDBN} executes the new target up to the first | |
2958 | breakpoint in the new target. If you have a breakpoint set on | |
2959 | @code{main} in your original program, the breakpoint will also be set on | |
2960 | the child process's @code{main}. | |
2961 | ||
2277426b PA |
2962 | On some systems, when a child process is spawned by @code{vfork}, you |
2963 | cannot debug the child or parent until an @code{exec} call completes. | |
c906108c SS |
2964 | |
2965 | If you issue a @code{run} command to @value{GDBN} after an @code{exec} | |
6c95b8df PA |
2966 | call executes, the new target restarts. To restart the parent |
2967 | process, use the @code{file} command with the parent executable name | |
2968 | as its argument. By default, after an @code{exec} call executes, | |
2969 | @value{GDBN} discards the symbols of the previous executable image. | |
2970 | You can change this behaviour with the @w{@code{set follow-exec-mode}} | |
2971 | command. | |
2972 | ||
2973 | @table @code | |
2974 | @kindex set follow-exec-mode | |
2975 | @item set follow-exec-mode @var{mode} | |
2976 | ||
2977 | Set debugger response to a program call of @code{exec}. An | |
2978 | @code{exec} call replaces the program image of a process. | |
2979 | ||
2980 | @code{follow-exec-mode} can be: | |
2981 | ||
2982 | @table @code | |
2983 | @item new | |
2984 | @value{GDBN} creates a new inferior and rebinds the process to this | |
2985 | new inferior. The program the process was running before the | |
2986 | @code{exec} call can be restarted afterwards by restarting the | |
2987 | original inferior. | |
2988 | ||
2989 | For example: | |
2990 | ||
2991 | @smallexample | |
2992 | (@value{GDBP}) info inferiors | |
2993 | (gdb) info inferior | |
2994 | Id Description Executable | |
2995 | * 1 <null> prog1 | |
2996 | (@value{GDBP}) run | |
2997 | process 12020 is executing new program: prog2 | |
2998 | Program exited normally. | |
2999 | (@value{GDBP}) info inferiors | |
3000 | Id Description Executable | |
3001 | * 2 <null> prog2 | |
3002 | 1 <null> prog1 | |
3003 | @end smallexample | |
3004 | ||
3005 | @item same | |
3006 | @value{GDBN} keeps the process bound to the same inferior. The new | |
3007 | executable image replaces the previous executable loaded in the | |
3008 | inferior. Restarting the inferior after the @code{exec} call, with | |
3009 | e.g., the @code{run} command, restarts the executable the process was | |
3010 | running after the @code{exec} call. This is the default mode. | |
3011 | ||
3012 | For example: | |
3013 | ||
3014 | @smallexample | |
3015 | (@value{GDBP}) info inferiors | |
3016 | Id Description Executable | |
3017 | * 1 <null> prog1 | |
3018 | (@value{GDBP}) run | |
3019 | process 12020 is executing new program: prog2 | |
3020 | Program exited normally. | |
3021 | (@value{GDBP}) info inferiors | |
3022 | Id Description Executable | |
3023 | * 1 <null> prog2 | |
3024 | @end smallexample | |
3025 | ||
3026 | @end table | |
3027 | @end table | |
c906108c SS |
3028 | |
3029 | You can use the @code{catch} command to make @value{GDBN} stop whenever | |
3030 | a @code{fork}, @code{vfork}, or @code{exec} call is made. @xref{Set | |
79a6e687 | 3031 | Catchpoints, ,Setting Catchpoints}. |
c906108c | 3032 | |
5c95884b | 3033 | @node Checkpoint/Restart |
79a6e687 | 3034 | @section Setting a @emph{Bookmark} to Return to Later |
5c95884b MS |
3035 | |
3036 | @cindex checkpoint | |
3037 | @cindex restart | |
3038 | @cindex bookmark | |
3039 | @cindex snapshot of a process | |
3040 | @cindex rewind program state | |
3041 | ||
3042 | On certain operating systems@footnote{Currently, only | |
3043 | @sc{gnu}/Linux.}, @value{GDBN} is able to save a @dfn{snapshot} of a | |
3044 | program's state, called a @dfn{checkpoint}, and come back to it | |
3045 | later. | |
3046 | ||
3047 | Returning to a checkpoint effectively undoes everything that has | |
3048 | happened in the program since the @code{checkpoint} was saved. This | |
3049 | includes changes in memory, registers, and even (within some limits) | |
3050 | system state. Effectively, it is like going back in time to the | |
3051 | moment when the checkpoint was saved. | |
3052 | ||
3053 | Thus, if you're stepping thru a program and you think you're | |
3054 | getting close to the point where things go wrong, you can save | |
3055 | a checkpoint. Then, if you accidentally go too far and miss | |
3056 | the critical statement, instead of having to restart your program | |
3057 | from the beginning, you can just go back to the checkpoint and | |
3058 | start again from there. | |
3059 | ||
3060 | This can be especially useful if it takes a lot of time or | |
3061 | steps to reach the point where you think the bug occurs. | |
3062 | ||
3063 | To use the @code{checkpoint}/@code{restart} method of debugging: | |
3064 | ||
3065 | @table @code | |
3066 | @kindex checkpoint | |
3067 | @item checkpoint | |
3068 | Save a snapshot of the debugged program's current execution state. | |
3069 | The @code{checkpoint} command takes no arguments, but each checkpoint | |
3070 | is assigned a small integer id, similar to a breakpoint id. | |
3071 | ||
3072 | @kindex info checkpoints | |
3073 | @item info checkpoints | |
3074 | List the checkpoints that have been saved in the current debugging | |
3075 | session. For each checkpoint, the following information will be | |
3076 | listed: | |
3077 | ||
3078 | @table @code | |
3079 | @item Checkpoint ID | |
3080 | @item Process ID | |
3081 | @item Code Address | |
3082 | @item Source line, or label | |
3083 | @end table | |
3084 | ||
3085 | @kindex restart @var{checkpoint-id} | |
3086 | @item restart @var{checkpoint-id} | |
3087 | Restore the program state that was saved as checkpoint number | |
3088 | @var{checkpoint-id}. All program variables, registers, stack frames | |
3089 | etc.@: will be returned to the values that they had when the checkpoint | |
3090 | was saved. In essence, gdb will ``wind back the clock'' to the point | |
3091 | in time when the checkpoint was saved. | |
3092 | ||
3093 | Note that breakpoints, @value{GDBN} variables, command history etc. | |
3094 | are not affected by restoring a checkpoint. In general, a checkpoint | |
3095 | only restores things that reside in the program being debugged, not in | |
3096 | the debugger. | |
3097 | ||
b8db102d MS |
3098 | @kindex delete checkpoint @var{checkpoint-id} |
3099 | @item delete checkpoint @var{checkpoint-id} | |
5c95884b MS |
3100 | Delete the previously-saved checkpoint identified by @var{checkpoint-id}. |
3101 | ||
3102 | @end table | |
3103 | ||
3104 | Returning to a previously saved checkpoint will restore the user state | |
3105 | of the program being debugged, plus a significant subset of the system | |
3106 | (OS) state, including file pointers. It won't ``un-write'' data from | |
3107 | a file, but it will rewind the file pointer to the previous location, | |
3108 | so that the previously written data can be overwritten. For files | |
3109 | opened in read mode, the pointer will also be restored so that the | |
3110 | previously read data can be read again. | |
3111 | ||
3112 | Of course, characters that have been sent to a printer (or other | |
3113 | external device) cannot be ``snatched back'', and characters received | |
3114 | from eg.@: a serial device can be removed from internal program buffers, | |
3115 | but they cannot be ``pushed back'' into the serial pipeline, ready to | |
3116 | be received again. Similarly, the actual contents of files that have | |
3117 | been changed cannot be restored (at this time). | |
3118 | ||
3119 | However, within those constraints, you actually can ``rewind'' your | |
3120 | program to a previously saved point in time, and begin debugging it | |
3121 | again --- and you can change the course of events so as to debug a | |
3122 | different execution path this time. | |
3123 | ||
3124 | @cindex checkpoints and process id | |
3125 | Finally, there is one bit of internal program state that will be | |
3126 | different when you return to a checkpoint --- the program's process | |
3127 | id. Each checkpoint will have a unique process id (or @var{pid}), | |
3128 | and each will be different from the program's original @var{pid}. | |
3129 | If your program has saved a local copy of its process id, this could | |
3130 | potentially pose a problem. | |
3131 | ||
79a6e687 | 3132 | @subsection A Non-obvious Benefit of Using Checkpoints |
5c95884b MS |
3133 | |
3134 | On some systems such as @sc{gnu}/Linux, address space randomization | |
3135 | is performed on new processes for security reasons. This makes it | |
3136 | difficult or impossible to set a breakpoint, or watchpoint, on an | |
3137 | absolute address if you have to restart the program, since the | |
3138 | absolute location of a symbol will change from one execution to the | |
3139 | next. | |
3140 | ||
3141 | A checkpoint, however, is an @emph{identical} copy of a process. | |
3142 | Therefore if you create a checkpoint at (eg.@:) the start of main, | |
3143 | and simply return to that checkpoint instead of restarting the | |
3144 | process, you can avoid the effects of address randomization and | |
3145 | your symbols will all stay in the same place. | |
3146 | ||
6d2ebf8b | 3147 | @node Stopping |
c906108c SS |
3148 | @chapter Stopping and Continuing |
3149 | ||
3150 | The principal purposes of using a debugger are so that you can stop your | |
3151 | program before it terminates; or so that, if your program runs into | |
3152 | trouble, you can investigate and find out why. | |
3153 | ||
7a292a7a SS |
3154 | Inside @value{GDBN}, your program may stop for any of several reasons, |
3155 | such as a signal, a breakpoint, or reaching a new line after a | |
3156 | @value{GDBN} command such as @code{step}. You may then examine and | |
3157 | change variables, set new breakpoints or remove old ones, and then | |
3158 | continue execution. Usually, the messages shown by @value{GDBN} provide | |
3159 | ample explanation of the status of your program---but you can also | |
3160 | explicitly request this information at any time. | |
c906108c SS |
3161 | |
3162 | @table @code | |
3163 | @kindex info program | |
3164 | @item info program | |
3165 | Display information about the status of your program: whether it is | |
7a292a7a | 3166 | running or not, what process it is, and why it stopped. |
c906108c SS |
3167 | @end table |
3168 | ||
3169 | @menu | |
3170 | * Breakpoints:: Breakpoints, watchpoints, and catchpoints | |
3171 | * Continuing and Stepping:: Resuming execution | |
c906108c | 3172 | * Signals:: Signals |
c906108c | 3173 | * Thread Stops:: Stopping and starting multi-thread programs |
c906108c SS |
3174 | @end menu |
3175 | ||
6d2ebf8b | 3176 | @node Breakpoints |
79a6e687 | 3177 | @section Breakpoints, Watchpoints, and Catchpoints |
c906108c SS |
3178 | |
3179 | @cindex breakpoints | |
3180 | A @dfn{breakpoint} makes your program stop whenever a certain point in | |
3181 | the program is reached. For each breakpoint, you can add conditions to | |
3182 | control in finer detail whether your program stops. You can set | |
3183 | breakpoints with the @code{break} command and its variants (@pxref{Set | |
79a6e687 | 3184 | Breaks, ,Setting Breakpoints}), to specify the place where your program |
c906108c SS |
3185 | should stop by line number, function name or exact address in the |
3186 | program. | |
3187 | ||
09d4efe1 EZ |
3188 | On some systems, you can set breakpoints in shared libraries before |
3189 | the executable is run. There is a minor limitation on HP-UX systems: | |
3190 | you must wait until the executable is run in order to set breakpoints | |
3191 | in shared library routines that are not called directly by the program | |
3192 | (for example, routines that are arguments in a @code{pthread_create} | |
3193 | call). | |
c906108c SS |
3194 | |
3195 | @cindex watchpoints | |
fd60e0df | 3196 | @cindex data breakpoints |
c906108c SS |
3197 | @cindex memory tracing |
3198 | @cindex breakpoint on memory address | |
3199 | @cindex breakpoint on variable modification | |
3200 | A @dfn{watchpoint} is a special breakpoint that stops your program | |
fd60e0df | 3201 | when the value of an expression changes. The expression may be a value |
0ced0c34 | 3202 | of a variable, or it could involve values of one or more variables |
fd60e0df EZ |
3203 | combined by operators, such as @samp{a + b}. This is sometimes called |
3204 | @dfn{data breakpoints}. You must use a different command to set | |
79a6e687 | 3205 | watchpoints (@pxref{Set Watchpoints, ,Setting Watchpoints}), but aside |
fd60e0df EZ |
3206 | from that, you can manage a watchpoint like any other breakpoint: you |
3207 | enable, disable, and delete both breakpoints and watchpoints using the | |
3208 | same commands. | |
c906108c SS |
3209 | |
3210 | You can arrange to have values from your program displayed automatically | |
3211 | whenever @value{GDBN} stops at a breakpoint. @xref{Auto Display,, | |
79a6e687 | 3212 | Automatic Display}. |
c906108c SS |
3213 | |
3214 | @cindex catchpoints | |
3215 | @cindex breakpoint on events | |
3216 | A @dfn{catchpoint} is another special breakpoint that stops your program | |
b37052ae | 3217 | when a certain kind of event occurs, such as the throwing of a C@t{++} |
c906108c SS |
3218 | exception or the loading of a library. As with watchpoints, you use a |
3219 | different command to set a catchpoint (@pxref{Set Catchpoints, ,Setting | |
79a6e687 | 3220 | Catchpoints}), but aside from that, you can manage a catchpoint like any |
c906108c | 3221 | other breakpoint. (To stop when your program receives a signal, use the |
d4f3574e | 3222 | @code{handle} command; see @ref{Signals, ,Signals}.) |
c906108c SS |
3223 | |
3224 | @cindex breakpoint numbers | |
3225 | @cindex numbers for breakpoints | |
3226 | @value{GDBN} assigns a number to each breakpoint, watchpoint, or | |
3227 | catchpoint when you create it; these numbers are successive integers | |
3228 | starting with one. In many of the commands for controlling various | |
3229 | features of breakpoints you use the breakpoint number to say which | |
3230 | breakpoint you want to change. Each breakpoint may be @dfn{enabled} or | |
3231 | @dfn{disabled}; if disabled, it has no effect on your program until you | |
3232 | enable it again. | |
3233 | ||
c5394b80 JM |
3234 | @cindex breakpoint ranges |
3235 | @cindex ranges of breakpoints | |
3236 | Some @value{GDBN} commands accept a range of breakpoints on which to | |
3237 | operate. A breakpoint range is either a single breakpoint number, like | |
3238 | @samp{5}, or two such numbers, in increasing order, separated by a | |
3239 | hyphen, like @samp{5-7}. When a breakpoint range is given to a command, | |
d52fb0e9 | 3240 | all breakpoints in that range are operated on. |
c5394b80 | 3241 | |
c906108c SS |
3242 | @menu |
3243 | * Set Breaks:: Setting breakpoints | |
3244 | * Set Watchpoints:: Setting watchpoints | |
3245 | * Set Catchpoints:: Setting catchpoints | |
3246 | * Delete Breaks:: Deleting breakpoints | |
3247 | * Disabling:: Disabling breakpoints | |
3248 | * Conditions:: Break conditions | |
3249 | * Break Commands:: Breakpoint command lists | |
d4f3574e | 3250 | * Error in Breakpoints:: ``Cannot insert breakpoints'' |
79a6e687 | 3251 | * Breakpoint-related Warnings:: ``Breakpoint address adjusted...'' |
c906108c SS |
3252 | @end menu |
3253 | ||
6d2ebf8b | 3254 | @node Set Breaks |
79a6e687 | 3255 | @subsection Setting Breakpoints |
c906108c | 3256 | |
5d161b24 | 3257 | @c FIXME LMB what does GDB do if no code on line of breakpt? |
c906108c SS |
3258 | @c consider in particular declaration with/without initialization. |
3259 | @c | |
3260 | @c FIXME 2 is there stuff on this already? break at fun start, already init? | |
3261 | ||
3262 | @kindex break | |
41afff9a EZ |
3263 | @kindex b @r{(@code{break})} |
3264 | @vindex $bpnum@r{, convenience variable} | |
c906108c SS |
3265 | @cindex latest breakpoint |
3266 | Breakpoints are set with the @code{break} command (abbreviated | |
5d161b24 | 3267 | @code{b}). The debugger convenience variable @samp{$bpnum} records the |
f3b28801 | 3268 | number of the breakpoint you've set most recently; see @ref{Convenience |
79a6e687 | 3269 | Vars,, Convenience Variables}, for a discussion of what you can do with |
c906108c SS |
3270 | convenience variables. |
3271 | ||
c906108c | 3272 | @table @code |
2a25a5ba EZ |
3273 | @item break @var{location} |
3274 | Set a breakpoint at the given @var{location}, which can specify a | |
3275 | function name, a line number, or an address of an instruction. | |
3276 | (@xref{Specify Location}, for a list of all the possible ways to | |
3277 | specify a @var{location}.) The breakpoint will stop your program just | |
3278 | before it executes any of the code in the specified @var{location}. | |
3279 | ||
c906108c | 3280 | When using source languages that permit overloading of symbols, such as |
2a25a5ba | 3281 | C@t{++}, a function name may refer to more than one possible place to break. |
6ba66d6a JB |
3282 | @xref{Ambiguous Expressions,,Ambiguous Expressions}, for a discussion of |
3283 | that situation. | |
c906108c | 3284 | |
45ac276d | 3285 | It is also possible to insert a breakpoint that will stop the program |
2c88c651 JB |
3286 | only if a specific thread (@pxref{Thread-Specific Breakpoints}) |
3287 | or a specific task (@pxref{Ada Tasks}) hits that breakpoint. | |
45ac276d | 3288 | |
c906108c SS |
3289 | @item break |
3290 | When called without any arguments, @code{break} sets a breakpoint at | |
3291 | the next instruction to be executed in the selected stack frame | |
3292 | (@pxref{Stack, ,Examining the Stack}). In any selected frame but the | |
3293 | innermost, this makes your program stop as soon as control | |
3294 | returns to that frame. This is similar to the effect of a | |
3295 | @code{finish} command in the frame inside the selected frame---except | |
3296 | that @code{finish} does not leave an active breakpoint. If you use | |
3297 | @code{break} without an argument in the innermost frame, @value{GDBN} stops | |
3298 | the next time it reaches the current location; this may be useful | |
3299 | inside loops. | |
3300 | ||
3301 | @value{GDBN} normally ignores breakpoints when it resumes execution, until at | |
3302 | least one instruction has been executed. If it did not do this, you | |
3303 | would be unable to proceed past a breakpoint without first disabling the | |
3304 | breakpoint. This rule applies whether or not the breakpoint already | |
3305 | existed when your program stopped. | |
3306 | ||
3307 | @item break @dots{} if @var{cond} | |
3308 | Set a breakpoint with condition @var{cond}; evaluate the expression | |
3309 | @var{cond} each time the breakpoint is reached, and stop only if the | |
3310 | value is nonzero---that is, if @var{cond} evaluates as true. | |
3311 | @samp{@dots{}} stands for one of the possible arguments described | |
3312 | above (or no argument) specifying where to break. @xref{Conditions, | |
79a6e687 | 3313 | ,Break Conditions}, for more information on breakpoint conditions. |
c906108c SS |
3314 | |
3315 | @kindex tbreak | |
3316 | @item tbreak @var{args} | |
3317 | Set a breakpoint enabled only for one stop. @var{args} are the | |
3318 | same as for the @code{break} command, and the breakpoint is set in the same | |
3319 | way, but the breakpoint is automatically deleted after the first time your | |
79a6e687 | 3320 | program stops there. @xref{Disabling, ,Disabling Breakpoints}. |
c906108c | 3321 | |
c906108c | 3322 | @kindex hbreak |
ba04e063 | 3323 | @cindex hardware breakpoints |
c906108c | 3324 | @item hbreak @var{args} |
d4f3574e SS |
3325 | Set a hardware-assisted breakpoint. @var{args} are the same as for the |
3326 | @code{break} command and the breakpoint is set in the same way, but the | |
c906108c SS |
3327 | breakpoint requires hardware support and some target hardware may not |
3328 | have this support. The main purpose of this is EPROM/ROM code | |
d4f3574e SS |
3329 | debugging, so you can set a breakpoint at an instruction without |
3330 | changing the instruction. This can be used with the new trap-generation | |
09d4efe1 | 3331 | provided by SPARClite DSU and most x86-based targets. These targets |
d4f3574e SS |
3332 | will generate traps when a program accesses some data or instruction |
3333 | address that is assigned to the debug registers. However the hardware | |
3334 | breakpoint registers can take a limited number of breakpoints. For | |
3335 | example, on the DSU, only two data breakpoints can be set at a time, and | |
3336 | @value{GDBN} will reject this command if more than two are used. Delete | |
3337 | or disable unused hardware breakpoints before setting new ones | |
79a6e687 BW |
3338 | (@pxref{Disabling, ,Disabling Breakpoints}). |
3339 | @xref{Conditions, ,Break Conditions}. | |
9c16f35a EZ |
3340 | For remote targets, you can restrict the number of hardware |
3341 | breakpoints @value{GDBN} will use, see @ref{set remote | |
3342 | hardware-breakpoint-limit}. | |
501eef12 | 3343 | |
c906108c SS |
3344 | @kindex thbreak |
3345 | @item thbreak @var{args} | |
3346 | Set a hardware-assisted breakpoint enabled only for one stop. @var{args} | |
3347 | are the same as for the @code{hbreak} command and the breakpoint is set in | |
5d161b24 | 3348 | the same way. However, like the @code{tbreak} command, |
c906108c SS |
3349 | the breakpoint is automatically deleted after the |
3350 | first time your program stops there. Also, like the @code{hbreak} | |
5d161b24 | 3351 | command, the breakpoint requires hardware support and some target hardware |
79a6e687 BW |
3352 | may not have this support. @xref{Disabling, ,Disabling Breakpoints}. |
3353 | See also @ref{Conditions, ,Break Conditions}. | |
c906108c SS |
3354 | |
3355 | @kindex rbreak | |
3356 | @cindex regular expression | |
c45da7e6 EZ |
3357 | @cindex breakpoints in functions matching a regexp |
3358 | @cindex set breakpoints in many functions | |
c906108c | 3359 | @item rbreak @var{regex} |
c906108c | 3360 | Set breakpoints on all functions matching the regular expression |
11cf8741 JM |
3361 | @var{regex}. This command sets an unconditional breakpoint on all |
3362 | matches, printing a list of all breakpoints it set. Once these | |
3363 | breakpoints are set, they are treated just like the breakpoints set with | |
3364 | the @code{break} command. You can delete them, disable them, or make | |
3365 | them conditional the same way as any other breakpoint. | |
3366 | ||
3367 | The syntax of the regular expression is the standard one used with tools | |
3368 | like @file{grep}. Note that this is different from the syntax used by | |
3369 | shells, so for instance @code{foo*} matches all functions that include | |
3370 | an @code{fo} followed by zero or more @code{o}s. There is an implicit | |
3371 | @code{.*} leading and trailing the regular expression you supply, so to | |
3372 | match only functions that begin with @code{foo}, use @code{^foo}. | |
c906108c | 3373 | |
f7dc1244 | 3374 | @cindex non-member C@t{++} functions, set breakpoint in |
b37052ae | 3375 | When debugging C@t{++} programs, @code{rbreak} is useful for setting |
c906108c SS |
3376 | breakpoints on overloaded functions that are not members of any special |
3377 | classes. | |
c906108c | 3378 | |
f7dc1244 EZ |
3379 | @cindex set breakpoints on all functions |
3380 | The @code{rbreak} command can be used to set breakpoints in | |
3381 | @strong{all} the functions in a program, like this: | |
3382 | ||
3383 | @smallexample | |
3384 | (@value{GDBP}) rbreak . | |
3385 | @end smallexample | |
3386 | ||
c906108c SS |
3387 | @kindex info breakpoints |
3388 | @cindex @code{$_} and @code{info breakpoints} | |
3389 | @item info breakpoints @r{[}@var{n}@r{]} | |
3390 | @itemx info break @r{[}@var{n}@r{]} | |
3391 | @itemx info watchpoints @r{[}@var{n}@r{]} | |
3392 | Print a table of all breakpoints, watchpoints, and catchpoints set and | |
45ac1734 EZ |
3393 | not deleted. Optional argument @var{n} means print information only |
3394 | about the specified breakpoint (or watchpoint or catchpoint). For | |
3395 | each breakpoint, following columns are printed: | |
c906108c SS |
3396 | |
3397 | @table @emph | |
3398 | @item Breakpoint Numbers | |
3399 | @item Type | |
3400 | Breakpoint, watchpoint, or catchpoint. | |
3401 | @item Disposition | |
3402 | Whether the breakpoint is marked to be disabled or deleted when hit. | |
3403 | @item Enabled or Disabled | |
3404 | Enabled breakpoints are marked with @samp{y}. @samp{n} marks breakpoints | |
b3db7447 | 3405 | that are not enabled. |
c906108c | 3406 | @item Address |
fe6fbf8b | 3407 | Where the breakpoint is in your program, as a memory address. For a |
b3db7447 NR |
3408 | pending breakpoint whose address is not yet known, this field will |
3409 | contain @samp{<PENDING>}. Such breakpoint won't fire until a shared | |
3410 | library that has the symbol or line referred by breakpoint is loaded. | |
3411 | See below for details. A breakpoint with several locations will | |
3b784c4f | 3412 | have @samp{<MULTIPLE>} in this field---see below for details. |
c906108c SS |
3413 | @item What |
3414 | Where the breakpoint is in the source for your program, as a file and | |
2650777c JJ |
3415 | line number. For a pending breakpoint, the original string passed to |
3416 | the breakpoint command will be listed as it cannot be resolved until | |
3417 | the appropriate shared library is loaded in the future. | |
c906108c SS |
3418 | @end table |
3419 | ||
3420 | @noindent | |
3421 | If a breakpoint is conditional, @code{info break} shows the condition on | |
3422 | the line following the affected breakpoint; breakpoint commands, if any, | |
2650777c JJ |
3423 | are listed after that. A pending breakpoint is allowed to have a condition |
3424 | specified for it. The condition is not parsed for validity until a shared | |
3425 | library is loaded that allows the pending breakpoint to resolve to a | |
3426 | valid location. | |
c906108c SS |
3427 | |
3428 | @noindent | |
3429 | @code{info break} with a breakpoint | |
3430 | number @var{n} as argument lists only that breakpoint. The | |
3431 | convenience variable @code{$_} and the default examining-address for | |
3432 | the @code{x} command are set to the address of the last breakpoint | |
79a6e687 | 3433 | listed (@pxref{Memory, ,Examining Memory}). |
c906108c SS |
3434 | |
3435 | @noindent | |
3436 | @code{info break} displays a count of the number of times the breakpoint | |
3437 | has been hit. This is especially useful in conjunction with the | |
3438 | @code{ignore} command. You can ignore a large number of breakpoint | |
3439 | hits, look at the breakpoint info to see how many times the breakpoint | |
3440 | was hit, and then run again, ignoring one less than that number. This | |
3441 | will get you quickly to the last hit of that breakpoint. | |
3442 | @end table | |
3443 | ||
3444 | @value{GDBN} allows you to set any number of breakpoints at the same place in | |
3445 | your program. There is nothing silly or meaningless about this. When | |
3446 | the breakpoints are conditional, this is even useful | |
79a6e687 | 3447 | (@pxref{Conditions, ,Break Conditions}). |
c906108c | 3448 | |
2e9132cc EZ |
3449 | @cindex multiple locations, breakpoints |
3450 | @cindex breakpoints, multiple locations | |
fcda367b | 3451 | It is possible that a breakpoint corresponds to several locations |
fe6fbf8b VP |
3452 | in your program. Examples of this situation are: |
3453 | ||
3454 | @itemize @bullet | |
fe6fbf8b VP |
3455 | @item |
3456 | For a C@t{++} constructor, the @value{NGCC} compiler generates several | |
3457 | instances of the function body, used in different cases. | |
3458 | ||
3459 | @item | |
3460 | For a C@t{++} template function, a given line in the function can | |
3461 | correspond to any number of instantiations. | |
3462 | ||
3463 | @item | |
3464 | For an inlined function, a given source line can correspond to | |
3465 | several places where that function is inlined. | |
fe6fbf8b VP |
3466 | @end itemize |
3467 | ||
3468 | In all those cases, @value{GDBN} will insert a breakpoint at all | |
2e9132cc EZ |
3469 | the relevant locations@footnote{ |
3470 | As of this writing, multiple-location breakpoints work only if there's | |
3471 | line number information for all the locations. This means that they | |
3472 | will generally not work in system libraries, unless you have debug | |
3473 | info with line numbers for them.}. | |
fe6fbf8b | 3474 | |
3b784c4f EZ |
3475 | A breakpoint with multiple locations is displayed in the breakpoint |
3476 | table using several rows---one header row, followed by one row for | |
3477 | each breakpoint location. The header row has @samp{<MULTIPLE>} in the | |
3478 | address column. The rows for individual locations contain the actual | |
3479 | addresses for locations, and show the functions to which those | |
3480 | locations belong. The number column for a location is of the form | |
fe6fbf8b VP |
3481 | @var{breakpoint-number}.@var{location-number}. |
3482 | ||
3483 | For example: | |
3b784c4f | 3484 | |
fe6fbf8b VP |
3485 | @smallexample |
3486 | Num Type Disp Enb Address What | |
3487 | 1 breakpoint keep y <MULTIPLE> | |
3488 | stop only if i==1 | |
3489 | breakpoint already hit 1 time | |
3490 | 1.1 y 0x080486a2 in void foo<int>() at t.cc:8 | |
3491 | 1.2 y 0x080486ca in void foo<double>() at t.cc:8 | |
3492 | @end smallexample | |
3493 | ||
3494 | Each location can be individually enabled or disabled by passing | |
3495 | @var{breakpoint-number}.@var{location-number} as argument to the | |
3b784c4f EZ |
3496 | @code{enable} and @code{disable} commands. Note that you cannot |
3497 | delete the individual locations from the list, you can only delete the | |
16bfc218 | 3498 | entire list of locations that belong to their parent breakpoint (with |
3b784c4f EZ |
3499 | the @kbd{delete @var{num}} command, where @var{num} is the number of |
3500 | the parent breakpoint, 1 in the above example). Disabling or enabling | |
3501 | the parent breakpoint (@pxref{Disabling}) affects all of the locations | |
3502 | that belong to that breakpoint. | |
fe6fbf8b | 3503 | |
2650777c | 3504 | @cindex pending breakpoints |
fe6fbf8b | 3505 | It's quite common to have a breakpoint inside a shared library. |
3b784c4f | 3506 | Shared libraries can be loaded and unloaded explicitly, |
fe6fbf8b VP |
3507 | and possibly repeatedly, as the program is executed. To support |
3508 | this use case, @value{GDBN} updates breakpoint locations whenever | |
3509 | any shared library is loaded or unloaded. Typically, you would | |
fcda367b | 3510 | set a breakpoint in a shared library at the beginning of your |
fe6fbf8b VP |
3511 | debugging session, when the library is not loaded, and when the |
3512 | symbols from the library are not available. When you try to set | |
3513 | breakpoint, @value{GDBN} will ask you if you want to set | |
3b784c4f | 3514 | a so called @dfn{pending breakpoint}---breakpoint whose address |
fe6fbf8b VP |
3515 | is not yet resolved. |
3516 | ||
3517 | After the program is run, whenever a new shared library is loaded, | |
3518 | @value{GDBN} reevaluates all the breakpoints. When a newly loaded | |
3519 | shared library contains the symbol or line referred to by some | |
3520 | pending breakpoint, that breakpoint is resolved and becomes an | |
3521 | ordinary breakpoint. When a library is unloaded, all breakpoints | |
3522 | that refer to its symbols or source lines become pending again. | |
3523 | ||
3524 | This logic works for breakpoints with multiple locations, too. For | |
3525 | example, if you have a breakpoint in a C@t{++} template function, and | |
3526 | a newly loaded shared library has an instantiation of that template, | |
3527 | a new location is added to the list of locations for the breakpoint. | |
3528 | ||
3529 | Except for having unresolved address, pending breakpoints do not | |
3530 | differ from regular breakpoints. You can set conditions or commands, | |
3531 | enable and disable them and perform other breakpoint operations. | |
3532 | ||
3533 | @value{GDBN} provides some additional commands for controlling what | |
3534 | happens when the @samp{break} command cannot resolve breakpoint | |
3535 | address specification to an address: | |
dd79a6cf JJ |
3536 | |
3537 | @kindex set breakpoint pending | |
3538 | @kindex show breakpoint pending | |
3539 | @table @code | |
3540 | @item set breakpoint pending auto | |
3541 | This is the default behavior. When @value{GDBN} cannot find the breakpoint | |
3542 | location, it queries you whether a pending breakpoint should be created. | |
3543 | ||
3544 | @item set breakpoint pending on | |
3545 | This indicates that an unrecognized breakpoint location should automatically | |
3546 | result in a pending breakpoint being created. | |
3547 | ||
3548 | @item set breakpoint pending off | |
3549 | This indicates that pending breakpoints are not to be created. Any | |
3550 | unrecognized breakpoint location results in an error. This setting does | |
3551 | not affect any pending breakpoints previously created. | |
3552 | ||
3553 | @item show breakpoint pending | |
3554 | Show the current behavior setting for creating pending breakpoints. | |
3555 | @end table | |
2650777c | 3556 | |
fe6fbf8b VP |
3557 | The settings above only affect the @code{break} command and its |
3558 | variants. Once breakpoint is set, it will be automatically updated | |
3559 | as shared libraries are loaded and unloaded. | |
2650777c | 3560 | |
765dc015 VP |
3561 | @cindex automatic hardware breakpoints |
3562 | For some targets, @value{GDBN} can automatically decide if hardware or | |
3563 | software breakpoints should be used, depending on whether the | |
3564 | breakpoint address is read-only or read-write. This applies to | |
3565 | breakpoints set with the @code{break} command as well as to internal | |
3566 | breakpoints set by commands like @code{next} and @code{finish}. For | |
fcda367b | 3567 | breakpoints set with @code{hbreak}, @value{GDBN} will always use hardware |
765dc015 VP |
3568 | breakpoints. |
3569 | ||
3570 | You can control this automatic behaviour with the following commands:: | |
3571 | ||
3572 | @kindex set breakpoint auto-hw | |
3573 | @kindex show breakpoint auto-hw | |
3574 | @table @code | |
3575 | @item set breakpoint auto-hw on | |
3576 | This is the default behavior. When @value{GDBN} sets a breakpoint, it | |
3577 | will try to use the target memory map to decide if software or hardware | |
3578 | breakpoint must be used. | |
3579 | ||
3580 | @item set breakpoint auto-hw off | |
3581 | This indicates @value{GDBN} should not automatically select breakpoint | |
3582 | type. If the target provides a memory map, @value{GDBN} will warn when | |
3583 | trying to set software breakpoint at a read-only address. | |
3584 | @end table | |
3585 | ||
74960c60 VP |
3586 | @value{GDBN} normally implements breakpoints by replacing the program code |
3587 | at the breakpoint address with a special instruction, which, when | |
3588 | executed, given control to the debugger. By default, the program | |
3589 | code is so modified only when the program is resumed. As soon as | |
3590 | the program stops, @value{GDBN} restores the original instructions. This | |
3591 | behaviour guards against leaving breakpoints inserted in the | |
3592 | target should gdb abrubptly disconnect. However, with slow remote | |
3593 | targets, inserting and removing breakpoint can reduce the performance. | |
3594 | This behavior can be controlled with the following commands:: | |
3595 | ||
3596 | @kindex set breakpoint always-inserted | |
3597 | @kindex show breakpoint always-inserted | |
3598 | @table @code | |
3599 | @item set breakpoint always-inserted off | |
33e5cbd6 PA |
3600 | All breakpoints, including newly added by the user, are inserted in |
3601 | the target only when the target is resumed. All breakpoints are | |
3602 | removed from the target when it stops. | |
74960c60 VP |
3603 | |
3604 | @item set breakpoint always-inserted on | |
3605 | Causes all breakpoints to be inserted in the target at all times. If | |
3606 | the user adds a new breakpoint, or changes an existing breakpoint, the | |
3607 | breakpoints in the target are updated immediately. A breakpoint is | |
3608 | removed from the target only when breakpoint itself is removed. | |
33e5cbd6 PA |
3609 | |
3610 | @cindex non-stop mode, and @code{breakpoint always-inserted} | |
3611 | @item set breakpoint always-inserted auto | |
3612 | This is the default mode. If @value{GDBN} is controlling the inferior | |
3613 | in non-stop mode (@pxref{Non-Stop Mode}), gdb behaves as if | |
3614 | @code{breakpoint always-inserted} mode is on. If @value{GDBN} is | |
3615 | controlling the inferior in all-stop mode, @value{GDBN} behaves as if | |
3616 | @code{breakpoint always-inserted} mode is off. | |
74960c60 | 3617 | @end table |
765dc015 | 3618 | |
c906108c SS |
3619 | @cindex negative breakpoint numbers |
3620 | @cindex internal @value{GDBN} breakpoints | |
eb12ee30 AC |
3621 | @value{GDBN} itself sometimes sets breakpoints in your program for |
3622 | special purposes, such as proper handling of @code{longjmp} (in C | |
3623 | programs). These internal breakpoints are assigned negative numbers, | |
3624 | starting with @code{-1}; @samp{info breakpoints} does not display them. | |
c906108c | 3625 | You can see these breakpoints with the @value{GDBN} maintenance command |
eb12ee30 | 3626 | @samp{maint info breakpoints} (@pxref{maint info breakpoints}). |
c906108c SS |
3627 | |
3628 | ||
6d2ebf8b | 3629 | @node Set Watchpoints |
79a6e687 | 3630 | @subsection Setting Watchpoints |
c906108c SS |
3631 | |
3632 | @cindex setting watchpoints | |
c906108c SS |
3633 | You can use a watchpoint to stop execution whenever the value of an |
3634 | expression changes, without having to predict a particular place where | |
fd60e0df EZ |
3635 | this may happen. (This is sometimes called a @dfn{data breakpoint}.) |
3636 | The expression may be as simple as the value of a single variable, or | |
3637 | as complex as many variables combined by operators. Examples include: | |
3638 | ||
3639 | @itemize @bullet | |
3640 | @item | |
3641 | A reference to the value of a single variable. | |
3642 | ||
3643 | @item | |
3644 | An address cast to an appropriate data type. For example, | |
3645 | @samp{*(int *)0x12345678} will watch a 4-byte region at the specified | |
3646 | address (assuming an @code{int} occupies 4 bytes). | |
3647 | ||
3648 | @item | |
3649 | An arbitrarily complex expression, such as @samp{a*b + c/d}. The | |
3650 | expression can use any operators valid in the program's native | |
3651 | language (@pxref{Languages}). | |
3652 | @end itemize | |
c906108c | 3653 | |
fa4727a6 DJ |
3654 | You can set a watchpoint on an expression even if the expression can |
3655 | not be evaluated yet. For instance, you can set a watchpoint on | |
3656 | @samp{*global_ptr} before @samp{global_ptr} is initialized. | |
3657 | @value{GDBN} will stop when your program sets @samp{global_ptr} and | |
3658 | the expression produces a valid value. If the expression becomes | |
3659 | valid in some other way than changing a variable (e.g.@: if the memory | |
3660 | pointed to by @samp{*global_ptr} becomes readable as the result of a | |
3661 | @code{malloc} call), @value{GDBN} may not stop until the next time | |
3662 | the expression changes. | |
3663 | ||
82f2d802 EZ |
3664 | @cindex software watchpoints |
3665 | @cindex hardware watchpoints | |
c906108c | 3666 | Depending on your system, watchpoints may be implemented in software or |
2df3850c | 3667 | hardware. @value{GDBN} does software watchpointing by single-stepping your |
c906108c SS |
3668 | program and testing the variable's value each time, which is hundreds of |
3669 | times slower than normal execution. (But this may still be worth it, to | |
3670 | catch errors where you have no clue what part of your program is the | |
3671 | culprit.) | |
3672 | ||
37e4754d | 3673 | On some systems, such as HP-UX, PowerPC, @sc{gnu}/Linux and most other |
82f2d802 EZ |
3674 | x86-based targets, @value{GDBN} includes support for hardware |
3675 | watchpoints, which do not slow down the running of your program. | |
c906108c SS |
3676 | |
3677 | @table @code | |
3678 | @kindex watch | |
d8b2a693 | 3679 | @item watch @var{expr} @r{[}thread @var{threadnum}@r{]} |
fd60e0df EZ |
3680 | Set a watchpoint for an expression. @value{GDBN} will break when the |
3681 | expression @var{expr} is written into by the program and its value | |
3682 | changes. The simplest (and the most popular) use of this command is | |
3683 | to watch the value of a single variable: | |
3684 | ||
3685 | @smallexample | |
3686 | (@value{GDBP}) watch foo | |
3687 | @end smallexample | |
c906108c | 3688 | |
d8b2a693 JB |
3689 | If the command includes a @code{@r{[}thread @var{threadnum}@r{]}} |
3690 | clause, @value{GDBN} breaks only when the thread identified by | |
3691 | @var{threadnum} changes the value of @var{expr}. If any other threads | |
3692 | change the value of @var{expr}, @value{GDBN} will not break. Note | |
3693 | that watchpoints restricted to a single thread in this way only work | |
3694 | with Hardware Watchpoints. | |
3695 | ||
c906108c | 3696 | @kindex rwatch |
d8b2a693 | 3697 | @item rwatch @var{expr} @r{[}thread @var{threadnum}@r{]} |
09d4efe1 EZ |
3698 | Set a watchpoint that will break when the value of @var{expr} is read |
3699 | by the program. | |
c906108c SS |
3700 | |
3701 | @kindex awatch | |
d8b2a693 | 3702 | @item awatch @var{expr} @r{[}thread @var{threadnum}@r{]} |
09d4efe1 EZ |
3703 | Set a watchpoint that will break when @var{expr} is either read from |
3704 | or written into by the program. | |
c906108c | 3705 | |
45ac1734 | 3706 | @kindex info watchpoints @r{[}@var{n}@r{]} |
c906108c SS |
3707 | @item info watchpoints |
3708 | This command prints a list of watchpoints, breakpoints, and catchpoints; | |
09d4efe1 | 3709 | it is the same as @code{info break} (@pxref{Set Breaks}). |
c906108c SS |
3710 | @end table |
3711 | ||
3712 | @value{GDBN} sets a @dfn{hardware watchpoint} if possible. Hardware | |
3713 | watchpoints execute very quickly, and the debugger reports a change in | |
3714 | value at the exact instruction where the change occurs. If @value{GDBN} | |
3715 | cannot set a hardware watchpoint, it sets a software watchpoint, which | |
3716 | executes more slowly and reports the change in value at the next | |
82f2d802 EZ |
3717 | @emph{statement}, not the instruction, after the change occurs. |
3718 | ||
82f2d802 EZ |
3719 | @cindex use only software watchpoints |
3720 | You can force @value{GDBN} to use only software watchpoints with the | |
3721 | @kbd{set can-use-hw-watchpoints 0} command. With this variable set to | |
3722 | zero, @value{GDBN} will never try to use hardware watchpoints, even if | |
3723 | the underlying system supports them. (Note that hardware-assisted | |
3724 | watchpoints that were set @emph{before} setting | |
3725 | @code{can-use-hw-watchpoints} to zero will still use the hardware | |
d3e8051b | 3726 | mechanism of watching expression values.) |
c906108c | 3727 | |
9c16f35a EZ |
3728 | @table @code |
3729 | @item set can-use-hw-watchpoints | |
3730 | @kindex set can-use-hw-watchpoints | |
3731 | Set whether or not to use hardware watchpoints. | |
3732 | ||
3733 | @item show can-use-hw-watchpoints | |
3734 | @kindex show can-use-hw-watchpoints | |
3735 | Show the current mode of using hardware watchpoints. | |
3736 | @end table | |
3737 | ||
3738 | For remote targets, you can restrict the number of hardware | |
3739 | watchpoints @value{GDBN} will use, see @ref{set remote | |
3740 | hardware-breakpoint-limit}. | |
3741 | ||
c906108c SS |
3742 | When you issue the @code{watch} command, @value{GDBN} reports |
3743 | ||
474c8240 | 3744 | @smallexample |
c906108c | 3745 | Hardware watchpoint @var{num}: @var{expr} |
474c8240 | 3746 | @end smallexample |
c906108c SS |
3747 | |
3748 | @noindent | |
3749 | if it was able to set a hardware watchpoint. | |
3750 | ||
7be570e7 JM |
3751 | Currently, the @code{awatch} and @code{rwatch} commands can only set |
3752 | hardware watchpoints, because accesses to data that don't change the | |
3753 | value of the watched expression cannot be detected without examining | |
3754 | every instruction as it is being executed, and @value{GDBN} does not do | |
3755 | that currently. If @value{GDBN} finds that it is unable to set a | |
3756 | hardware breakpoint with the @code{awatch} or @code{rwatch} command, it | |
3757 | will print a message like this: | |
3758 | ||
3759 | @smallexample | |
3760 | Expression cannot be implemented with read/access watchpoint. | |
3761 | @end smallexample | |
3762 | ||
3763 | Sometimes, @value{GDBN} cannot set a hardware watchpoint because the | |
3764 | data type of the watched expression is wider than what a hardware | |
3765 | watchpoint on the target machine can handle. For example, some systems | |
3766 | can only watch regions that are up to 4 bytes wide; on such systems you | |
3767 | cannot set hardware watchpoints for an expression that yields a | |
3768 | double-precision floating-point number (which is typically 8 bytes | |
3769 | wide). As a work-around, it might be possible to break the large region | |
3770 | into a series of smaller ones and watch them with separate watchpoints. | |
3771 | ||
3772 | If you set too many hardware watchpoints, @value{GDBN} might be unable | |
3773 | to insert all of them when you resume the execution of your program. | |
3774 | Since the precise number of active watchpoints is unknown until such | |
3775 | time as the program is about to be resumed, @value{GDBN} might not be | |
3776 | able to warn you about this when you set the watchpoints, and the | |
3777 | warning will be printed only when the program is resumed: | |
3778 | ||
3779 | @smallexample | |
3780 | Hardware watchpoint @var{num}: Could not insert watchpoint | |
3781 | @end smallexample | |
3782 | ||
3783 | @noindent | |
3784 | If this happens, delete or disable some of the watchpoints. | |
3785 | ||
fd60e0df EZ |
3786 | Watching complex expressions that reference many variables can also |
3787 | exhaust the resources available for hardware-assisted watchpoints. | |
3788 | That's because @value{GDBN} needs to watch every variable in the | |
3789 | expression with separately allocated resources. | |
3790 | ||
c906108c | 3791 | If you call a function interactively using @code{print} or @code{call}, |
2df3850c | 3792 | any watchpoints you have set will be inactive until @value{GDBN} reaches another |
c906108c SS |
3793 | kind of breakpoint or the call completes. |
3794 | ||
7be570e7 JM |
3795 | @value{GDBN} automatically deletes watchpoints that watch local |
3796 | (automatic) variables, or expressions that involve such variables, when | |
3797 | they go out of scope, that is, when the execution leaves the block in | |
3798 | which these variables were defined. In particular, when the program | |
3799 | being debugged terminates, @emph{all} local variables go out of scope, | |
3800 | and so only watchpoints that watch global variables remain set. If you | |
3801 | rerun the program, you will need to set all such watchpoints again. One | |
3802 | way of doing that would be to set a code breakpoint at the entry to the | |
3803 | @code{main} function and when it breaks, set all the watchpoints. | |
3804 | ||
c906108c SS |
3805 | @cindex watchpoints and threads |
3806 | @cindex threads and watchpoints | |
d983da9c DJ |
3807 | In multi-threaded programs, watchpoints will detect changes to the |
3808 | watched expression from every thread. | |
3809 | ||
3810 | @quotation | |
3811 | @emph{Warning:} In multi-threaded programs, software watchpoints | |
53a5351d JM |
3812 | have only limited usefulness. If @value{GDBN} creates a software |
3813 | watchpoint, it can only watch the value of an expression @emph{in a | |
3814 | single thread}. If you are confident that the expression can only | |
3815 | change due to the current thread's activity (and if you are also | |
3816 | confident that no other thread can become current), then you can use | |
3817 | software watchpoints as usual. However, @value{GDBN} may not notice | |
3818 | when a non-current thread's activity changes the expression. (Hardware | |
3819 | watchpoints, in contrast, watch an expression in all threads.) | |
c906108c | 3820 | @end quotation |
c906108c | 3821 | |
501eef12 AC |
3822 | @xref{set remote hardware-watchpoint-limit}. |
3823 | ||
6d2ebf8b | 3824 | @node Set Catchpoints |
79a6e687 | 3825 | @subsection Setting Catchpoints |
d4f3574e | 3826 | @cindex catchpoints, setting |
c906108c SS |
3827 | @cindex exception handlers |
3828 | @cindex event handling | |
3829 | ||
3830 | You can use @dfn{catchpoints} to cause the debugger to stop for certain | |
b37052ae | 3831 | kinds of program events, such as C@t{++} exceptions or the loading of a |
c906108c SS |
3832 | shared library. Use the @code{catch} command to set a catchpoint. |
3833 | ||
3834 | @table @code | |
3835 | @kindex catch | |
3836 | @item catch @var{event} | |
3837 | Stop when @var{event} occurs. @var{event} can be any of the following: | |
3838 | @table @code | |
3839 | @item throw | |
4644b6e3 | 3840 | @cindex stop on C@t{++} exceptions |
b37052ae | 3841 | The throwing of a C@t{++} exception. |
c906108c SS |
3842 | |
3843 | @item catch | |
b37052ae | 3844 | The catching of a C@t{++} exception. |
c906108c | 3845 | |
8936fcda JB |
3846 | @item exception |
3847 | @cindex Ada exception catching | |
3848 | @cindex catch Ada exceptions | |
3849 | An Ada exception being raised. If an exception name is specified | |
3850 | at the end of the command (eg @code{catch exception Program_Error}), | |
3851 | the debugger will stop only when this specific exception is raised. | |
3852 | Otherwise, the debugger stops execution when any Ada exception is raised. | |
3853 | ||
87f67dba JB |
3854 | When inserting an exception catchpoint on a user-defined exception whose |
3855 | name is identical to one of the exceptions defined by the language, the | |
3856 | fully qualified name must be used as the exception name. Otherwise, | |
3857 | @value{GDBN} will assume that it should stop on the pre-defined exception | |
3858 | rather than the user-defined one. For instance, assuming an exception | |
3859 | called @code{Constraint_Error} is defined in package @code{Pck}, then | |
3860 | the command to use to catch such exceptions is @kbd{catch exception | |
3861 | Pck.Constraint_Error}. | |
3862 | ||
8936fcda JB |
3863 | @item exception unhandled |
3864 | An exception that was raised but is not handled by the program. | |
3865 | ||
3866 | @item assert | |
3867 | A failed Ada assertion. | |
3868 | ||
c906108c | 3869 | @item exec |
4644b6e3 | 3870 | @cindex break on fork/exec |
5ee187d7 DJ |
3871 | A call to @code{exec}. This is currently only available for HP-UX |
3872 | and @sc{gnu}/Linux. | |
c906108c | 3873 | |
a96d9b2e SDJ |
3874 | @item syscall |
3875 | @itemx syscall @r{[}@var{name} @r{|} @var{number}@r{]} @r{...} | |
3876 | @cindex break on a system call. | |
3877 | A call to or return from a system call, a.k.a.@: @dfn{syscall}. A | |
3878 | syscall is a mechanism for application programs to request a service | |
3879 | from the operating system (OS) or one of the OS system services. | |
3880 | @value{GDBN} can catch some or all of the syscalls issued by the | |
3881 | debuggee, and show the related information for each syscall. If no | |
3882 | argument is specified, calls to and returns from all system calls | |
3883 | will be caught. | |
3884 | ||
3885 | @var{name} can be any system call name that is valid for the | |
3886 | underlying OS. Just what syscalls are valid depends on the OS. On | |
3887 | GNU and Unix systems, you can find the full list of valid syscall | |
3888 | names on @file{/usr/include/asm/unistd.h}. | |
3889 | ||
3890 | @c For MS-Windows, the syscall names and the corresponding numbers | |
3891 | @c can be found, e.g., on this URL: | |
3892 | @c http://www.metasploit.com/users/opcode/syscalls.html | |
3893 | @c but we don't support Windows syscalls yet. | |
3894 | ||
3895 | Normally, @value{GDBN} knows in advance which syscalls are valid for | |
3896 | each OS, so you can use the @value{GDBN} command-line completion | |
3897 | facilities (@pxref{Completion,, command completion}) to list the | |
3898 | available choices. | |
3899 | ||
3900 | You may also specify the system call numerically. A syscall's | |
3901 | number is the value passed to the OS's syscall dispatcher to | |
3902 | identify the requested service. When you specify the syscall by its | |
3903 | name, @value{GDBN} uses its database of syscalls to convert the name | |
3904 | into the corresponding numeric code, but using the number directly | |
3905 | may be useful if @value{GDBN}'s database does not have the complete | |
3906 | list of syscalls on your system (e.g., because @value{GDBN} lags | |
3907 | behind the OS upgrades). | |
3908 | ||
3909 | The example below illustrates how this command works if you don't provide | |
3910 | arguments to it: | |
3911 | ||
3912 | @smallexample | |
3913 | (@value{GDBP}) catch syscall | |
3914 | Catchpoint 1 (syscall) | |
3915 | (@value{GDBP}) r | |
3916 | Starting program: /tmp/catch-syscall | |
3917 | ||
3918 | Catchpoint 1 (call to syscall 'close'), \ | |
3919 | 0xffffe424 in __kernel_vsyscall () | |
3920 | (@value{GDBP}) c | |
3921 | Continuing. | |
3922 | ||
3923 | Catchpoint 1 (returned from syscall 'close'), \ | |
3924 | 0xffffe424 in __kernel_vsyscall () | |
3925 | (@value{GDBP}) | |
3926 | @end smallexample | |
3927 | ||
3928 | Here is an example of catching a system call by name: | |
3929 | ||
3930 | @smallexample | |
3931 | (@value{GDBP}) catch syscall chroot | |
3932 | Catchpoint 1 (syscall 'chroot' [61]) | |
3933 | (@value{GDBP}) r | |
3934 | Starting program: /tmp/catch-syscall | |
3935 | ||
3936 | Catchpoint 1 (call to syscall 'chroot'), \ | |
3937 | 0xffffe424 in __kernel_vsyscall () | |
3938 | (@value{GDBP}) c | |
3939 | Continuing. | |
3940 | ||
3941 | Catchpoint 1 (returned from syscall 'chroot'), \ | |
3942 | 0xffffe424 in __kernel_vsyscall () | |
3943 | (@value{GDBP}) | |
3944 | @end smallexample | |
3945 | ||
3946 | An example of specifying a system call numerically. In the case | |
3947 | below, the syscall number has a corresponding entry in the XML | |
3948 | file, so @value{GDBN} finds its name and prints it: | |
3949 | ||
3950 | @smallexample | |
3951 | (@value{GDBP}) catch syscall 252 | |
3952 | Catchpoint 1 (syscall(s) 'exit_group') | |
3953 | (@value{GDBP}) r | |
3954 | Starting program: /tmp/catch-syscall | |
3955 | ||
3956 | Catchpoint 1 (call to syscall 'exit_group'), \ | |
3957 | 0xffffe424 in __kernel_vsyscall () | |
3958 | (@value{GDBP}) c | |
3959 | Continuing. | |
3960 | ||
3961 | Program exited normally. | |
3962 | (@value{GDBP}) | |
3963 | @end smallexample | |
3964 | ||
3965 | However, there can be situations when there is no corresponding name | |
3966 | in XML file for that syscall number. In this case, @value{GDBN} prints | |
3967 | a warning message saying that it was not able to find the syscall name, | |
3968 | but the catchpoint will be set anyway. See the example below: | |
3969 | ||
3970 | @smallexample | |
3971 | (@value{GDBP}) catch syscall 764 | |
3972 | warning: The number '764' does not represent a known syscall. | |
3973 | Catchpoint 2 (syscall 764) | |
3974 | (@value{GDBP}) | |
3975 | @end smallexample | |
3976 | ||
3977 | If you configure @value{GDBN} using the @samp{--without-expat} option, | |
3978 | it will not be able to display syscall names. Also, if your | |
3979 | architecture does not have an XML file describing its system calls, | |
3980 | you will not be able to see the syscall names. It is important to | |
3981 | notice that these two features are used for accessing the syscall | |
3982 | name database. In either case, you will see a warning like this: | |
3983 | ||
3984 | @smallexample | |
3985 | (@value{GDBP}) catch syscall | |
3986 | warning: Could not open "syscalls/i386-linux.xml" | |
3987 | warning: Could not load the syscall XML file 'syscalls/i386-linux.xml'. | |
3988 | GDB will not be able to display syscall names. | |
3989 | Catchpoint 1 (syscall) | |
3990 | (@value{GDBP}) | |
3991 | @end smallexample | |
3992 | ||
3993 | Of course, the file name will change depending on your architecture and system. | |
3994 | ||
3995 | Still using the example above, you can also try to catch a syscall by its | |
3996 | number. In this case, you would see something like: | |
3997 | ||
3998 | @smallexample | |
3999 | (@value{GDBP}) catch syscall 252 | |
4000 | Catchpoint 1 (syscall(s) 252) | |
4001 | @end smallexample | |
4002 | ||
4003 | Again, in this case @value{GDBN} would not be able to display syscall's names. | |
4004 | ||
c906108c | 4005 | @item fork |
5ee187d7 DJ |
4006 | A call to @code{fork}. This is currently only available for HP-UX |
4007 | and @sc{gnu}/Linux. | |
c906108c SS |
4008 | |
4009 | @item vfork | |
5ee187d7 DJ |
4010 | A call to @code{vfork}. This is currently only available for HP-UX |
4011 | and @sc{gnu}/Linux. | |
c906108c | 4012 | |
c906108c SS |
4013 | @end table |
4014 | ||
4015 | @item tcatch @var{event} | |
4016 | Set a catchpoint that is enabled only for one stop. The catchpoint is | |
4017 | automatically deleted after the first time the event is caught. | |
4018 | ||
4019 | @end table | |
4020 | ||
4021 | Use the @code{info break} command to list the current catchpoints. | |
4022 | ||
b37052ae | 4023 | There are currently some limitations to C@t{++} exception handling |
c906108c SS |
4024 | (@code{catch throw} and @code{catch catch}) in @value{GDBN}: |
4025 | ||
4026 | @itemize @bullet | |
4027 | @item | |
4028 | If you call a function interactively, @value{GDBN} normally returns | |
4029 | control to you when the function has finished executing. If the call | |
4030 | raises an exception, however, the call may bypass the mechanism that | |
4031 | returns control to you and cause your program either to abort or to | |
4032 | simply continue running until it hits a breakpoint, catches a signal | |
4033 | that @value{GDBN} is listening for, or exits. This is the case even if | |
4034 | you set a catchpoint for the exception; catchpoints on exceptions are | |
4035 | disabled within interactive calls. | |
4036 | ||
4037 | @item | |
4038 | You cannot raise an exception interactively. | |
4039 | ||
4040 | @item | |
4041 | You cannot install an exception handler interactively. | |
4042 | @end itemize | |
4043 | ||
4044 | @cindex raise exceptions | |
4045 | Sometimes @code{catch} is not the best way to debug exception handling: | |
4046 | if you need to know exactly where an exception is raised, it is better to | |
4047 | stop @emph{before} the exception handler is called, since that way you | |
4048 | can see the stack before any unwinding takes place. If you set a | |
4049 | breakpoint in an exception handler instead, it may not be easy to find | |
4050 | out where the exception was raised. | |
4051 | ||
4052 | To stop just before an exception handler is called, you need some | |
b37052ae | 4053 | knowledge of the implementation. In the case of @sc{gnu} C@t{++}, exceptions are |
c906108c SS |
4054 | raised by calling a library function named @code{__raise_exception} |
4055 | which has the following ANSI C interface: | |
4056 | ||
474c8240 | 4057 | @smallexample |
c906108c | 4058 | /* @var{addr} is where the exception identifier is stored. |
d4f3574e SS |
4059 | @var{id} is the exception identifier. */ |
4060 | void __raise_exception (void **addr, void *id); | |
474c8240 | 4061 | @end smallexample |
c906108c SS |
4062 | |
4063 | @noindent | |
4064 | To make the debugger catch all exceptions before any stack | |
4065 | unwinding takes place, set a breakpoint on @code{__raise_exception} | |
79a6e687 | 4066 | (@pxref{Breakpoints, ,Breakpoints; Watchpoints; and Exceptions}). |
c906108c | 4067 | |
79a6e687 | 4068 | With a conditional breakpoint (@pxref{Conditions, ,Break Conditions}) |
c906108c SS |
4069 | that depends on the value of @var{id}, you can stop your program when |
4070 | a specific exception is raised. You can use multiple conditional | |
4071 | breakpoints to stop your program when any of a number of exceptions are | |
4072 | raised. | |
4073 | ||
4074 | ||
6d2ebf8b | 4075 | @node Delete Breaks |
79a6e687 | 4076 | @subsection Deleting Breakpoints |
c906108c SS |
4077 | |
4078 | @cindex clearing breakpoints, watchpoints, catchpoints | |
4079 | @cindex deleting breakpoints, watchpoints, catchpoints | |
4080 | It is often necessary to eliminate a breakpoint, watchpoint, or | |
4081 | catchpoint once it has done its job and you no longer want your program | |
4082 | to stop there. This is called @dfn{deleting} the breakpoint. A | |
4083 | breakpoint that has been deleted no longer exists; it is forgotten. | |
4084 | ||
4085 | With the @code{clear} command you can delete breakpoints according to | |
4086 | where they are in your program. With the @code{delete} command you can | |
4087 | delete individual breakpoints, watchpoints, or catchpoints by specifying | |
4088 | their breakpoint numbers. | |
4089 | ||
4090 | It is not necessary to delete a breakpoint to proceed past it. @value{GDBN} | |
4091 | automatically ignores breakpoints on the first instruction to be executed | |
4092 | when you continue execution without changing the execution address. | |
4093 | ||
4094 | @table @code | |
4095 | @kindex clear | |
4096 | @item clear | |
4097 | Delete any breakpoints at the next instruction to be executed in the | |
79a6e687 | 4098 | selected stack frame (@pxref{Selection, ,Selecting a Frame}). When |
c906108c SS |
4099 | the innermost frame is selected, this is a good way to delete a |
4100 | breakpoint where your program just stopped. | |
4101 | ||
2a25a5ba EZ |
4102 | @item clear @var{location} |
4103 | Delete any breakpoints set at the specified @var{location}. | |
4104 | @xref{Specify Location}, for the various forms of @var{location}; the | |
4105 | most useful ones are listed below: | |
4106 | ||
4107 | @table @code | |
c906108c SS |
4108 | @item clear @var{function} |
4109 | @itemx clear @var{filename}:@var{function} | |
09d4efe1 | 4110 | Delete any breakpoints set at entry to the named @var{function}. |
c906108c SS |
4111 | |
4112 | @item clear @var{linenum} | |
4113 | @itemx clear @var{filename}:@var{linenum} | |
09d4efe1 EZ |
4114 | Delete any breakpoints set at or within the code of the specified |
4115 | @var{linenum} of the specified @var{filename}. | |
2a25a5ba | 4116 | @end table |
c906108c SS |
4117 | |
4118 | @cindex delete breakpoints | |
4119 | @kindex delete | |
41afff9a | 4120 | @kindex d @r{(@code{delete})} |
c5394b80 JM |
4121 | @item delete @r{[}breakpoints@r{]} @r{[}@var{range}@dots{}@r{]} |
4122 | Delete the breakpoints, watchpoints, or catchpoints of the breakpoint | |
4123 | ranges specified as arguments. If no argument is specified, delete all | |
c906108c SS |
4124 | breakpoints (@value{GDBN} asks confirmation, unless you have @code{set |
4125 | confirm off}). You can abbreviate this command as @code{d}. | |
4126 | @end table | |
4127 | ||
6d2ebf8b | 4128 | @node Disabling |
79a6e687 | 4129 | @subsection Disabling Breakpoints |
c906108c | 4130 | |
4644b6e3 | 4131 | @cindex enable/disable a breakpoint |
c906108c SS |
4132 | Rather than deleting a breakpoint, watchpoint, or catchpoint, you might |
4133 | prefer to @dfn{disable} it. This makes the breakpoint inoperative as if | |
4134 | it had been deleted, but remembers the information on the breakpoint so | |
4135 | that you can @dfn{enable} it again later. | |
4136 | ||
4137 | You disable and enable breakpoints, watchpoints, and catchpoints with | |
4138 | the @code{enable} and @code{disable} commands, optionally specifying one | |
4139 | or more breakpoint numbers as arguments. Use @code{info break} or | |
4140 | @code{info watch} to print a list of breakpoints, watchpoints, and | |
4141 | catchpoints if you do not know which numbers to use. | |
4142 | ||
3b784c4f EZ |
4143 | Disabling and enabling a breakpoint that has multiple locations |
4144 | affects all of its locations. | |
4145 | ||
c906108c SS |
4146 | A breakpoint, watchpoint, or catchpoint can have any of four different |
4147 | states of enablement: | |
4148 | ||
4149 | @itemize @bullet | |
4150 | @item | |
4151 | Enabled. The breakpoint stops your program. A breakpoint set | |
4152 | with the @code{break} command starts out in this state. | |
4153 | @item | |
4154 | Disabled. The breakpoint has no effect on your program. | |
4155 | @item | |
4156 | Enabled once. The breakpoint stops your program, but then becomes | |
d4f3574e | 4157 | disabled. |
c906108c SS |
4158 | @item |
4159 | Enabled for deletion. The breakpoint stops your program, but | |
d4f3574e SS |
4160 | immediately after it does so it is deleted permanently. A breakpoint |
4161 | set with the @code{tbreak} command starts out in this state. | |
c906108c SS |
4162 | @end itemize |
4163 | ||
4164 | You can use the following commands to enable or disable breakpoints, | |
4165 | watchpoints, and catchpoints: | |
4166 | ||
4167 | @table @code | |
c906108c | 4168 | @kindex disable |
41afff9a | 4169 | @kindex dis @r{(@code{disable})} |
c5394b80 | 4170 | @item disable @r{[}breakpoints@r{]} @r{[}@var{range}@dots{}@r{]} |
c906108c SS |
4171 | Disable the specified breakpoints---or all breakpoints, if none are |
4172 | listed. A disabled breakpoint has no effect but is not forgotten. All | |
4173 | options such as ignore-counts, conditions and commands are remembered in | |
4174 | case the breakpoint is enabled again later. You may abbreviate | |
4175 | @code{disable} as @code{dis}. | |
4176 | ||
c906108c | 4177 | @kindex enable |
c5394b80 | 4178 | @item enable @r{[}breakpoints@r{]} @r{[}@var{range}@dots{}@r{]} |
c906108c SS |
4179 | Enable the specified breakpoints (or all defined breakpoints). They |
4180 | become effective once again in stopping your program. | |
4181 | ||
c5394b80 | 4182 | @item enable @r{[}breakpoints@r{]} once @var{range}@dots{} |
c906108c SS |
4183 | Enable the specified breakpoints temporarily. @value{GDBN} disables any |
4184 | of these breakpoints immediately after stopping your program. | |
4185 | ||
c5394b80 | 4186 | @item enable @r{[}breakpoints@r{]} delete @var{range}@dots{} |
c906108c SS |
4187 | Enable the specified breakpoints to work once, then die. @value{GDBN} |
4188 | deletes any of these breakpoints as soon as your program stops there. | |
09d4efe1 | 4189 | Breakpoints set by the @code{tbreak} command start out in this state. |
c906108c SS |
4190 | @end table |
4191 | ||
d4f3574e SS |
4192 | @c FIXME: I think the following ``Except for [...] @code{tbreak}'' is |
4193 | @c confusing: tbreak is also initially enabled. | |
c906108c | 4194 | Except for a breakpoint set with @code{tbreak} (@pxref{Set Breaks, |
79a6e687 | 4195 | ,Setting Breakpoints}), breakpoints that you set are initially enabled; |
c906108c SS |
4196 | subsequently, they become disabled or enabled only when you use one of |
4197 | the commands above. (The command @code{until} can set and delete a | |
4198 | breakpoint of its own, but it does not change the state of your other | |
4199 | breakpoints; see @ref{Continuing and Stepping, ,Continuing and | |
79a6e687 | 4200 | Stepping}.) |
c906108c | 4201 | |
6d2ebf8b | 4202 | @node Conditions |
79a6e687 | 4203 | @subsection Break Conditions |
c906108c SS |
4204 | @cindex conditional breakpoints |
4205 | @cindex breakpoint conditions | |
4206 | ||
4207 | @c FIXME what is scope of break condition expr? Context where wanted? | |
5d161b24 | 4208 | @c in particular for a watchpoint? |
c906108c SS |
4209 | The simplest sort of breakpoint breaks every time your program reaches a |
4210 | specified place. You can also specify a @dfn{condition} for a | |
4211 | breakpoint. A condition is just a Boolean expression in your | |
4212 | programming language (@pxref{Expressions, ,Expressions}). A breakpoint with | |
4213 | a condition evaluates the expression each time your program reaches it, | |
4214 | and your program stops only if the condition is @emph{true}. | |
4215 | ||
4216 | This is the converse of using assertions for program validation; in that | |
4217 | situation, you want to stop when the assertion is violated---that is, | |
4218 | when the condition is false. In C, if you want to test an assertion expressed | |
4219 | by the condition @var{assert}, you should set the condition | |
4220 | @samp{! @var{assert}} on the appropriate breakpoint. | |
4221 | ||
4222 | Conditions are also accepted for watchpoints; you may not need them, | |
4223 | since a watchpoint is inspecting the value of an expression anyhow---but | |
4224 | it might be simpler, say, to just set a watchpoint on a variable name, | |
4225 | and specify a condition that tests whether the new value is an interesting | |
4226 | one. | |
4227 | ||
4228 | Break conditions can have side effects, and may even call functions in | |
4229 | your program. This can be useful, for example, to activate functions | |
4230 | that log program progress, or to use your own print functions to | |
99e008fe | 4231 | format special data structures. The effects are completely predictable |
c906108c SS |
4232 | unless there is another enabled breakpoint at the same address. (In |
4233 | that case, @value{GDBN} might see the other breakpoint first and stop your | |
4234 | program without checking the condition of this one.) Note that | |
d4f3574e SS |
4235 | breakpoint commands are usually more convenient and flexible than break |
4236 | conditions for the | |
c906108c | 4237 | purpose of performing side effects when a breakpoint is reached |
79a6e687 | 4238 | (@pxref{Break Commands, ,Breakpoint Command Lists}). |
c906108c SS |
4239 | |
4240 | Break conditions can be specified when a breakpoint is set, by using | |
4241 | @samp{if} in the arguments to the @code{break} command. @xref{Set | |
79a6e687 | 4242 | Breaks, ,Setting Breakpoints}. They can also be changed at any time |
c906108c | 4243 | with the @code{condition} command. |
53a5351d | 4244 | |
c906108c SS |
4245 | You can also use the @code{if} keyword with the @code{watch} command. |
4246 | The @code{catch} command does not recognize the @code{if} keyword; | |
4247 | @code{condition} is the only way to impose a further condition on a | |
4248 | catchpoint. | |
c906108c SS |
4249 | |
4250 | @table @code | |
4251 | @kindex condition | |
4252 | @item condition @var{bnum} @var{expression} | |
4253 | Specify @var{expression} as the break condition for breakpoint, | |
4254 | watchpoint, or catchpoint number @var{bnum}. After you set a condition, | |
4255 | breakpoint @var{bnum} stops your program only if the value of | |
4256 | @var{expression} is true (nonzero, in C). When you use | |
4257 | @code{condition}, @value{GDBN} checks @var{expression} immediately for | |
4258 | syntactic correctness, and to determine whether symbols in it have | |
d4f3574e SS |
4259 | referents in the context of your breakpoint. If @var{expression} uses |
4260 | symbols not referenced in the context of the breakpoint, @value{GDBN} | |
4261 | prints an error message: | |
4262 | ||
474c8240 | 4263 | @smallexample |
d4f3574e | 4264 | No symbol "foo" in current context. |
474c8240 | 4265 | @end smallexample |
d4f3574e SS |
4266 | |
4267 | @noindent | |
c906108c SS |
4268 | @value{GDBN} does |
4269 | not actually evaluate @var{expression} at the time the @code{condition} | |
d4f3574e SS |
4270 | command (or a command that sets a breakpoint with a condition, like |
4271 | @code{break if @dots{}}) is given, however. @xref{Expressions, ,Expressions}. | |
c906108c SS |
4272 | |
4273 | @item condition @var{bnum} | |
4274 | Remove the condition from breakpoint number @var{bnum}. It becomes | |
4275 | an ordinary unconditional breakpoint. | |
4276 | @end table | |
4277 | ||
4278 | @cindex ignore count (of breakpoint) | |
4279 | A special case of a breakpoint condition is to stop only when the | |
4280 | breakpoint has been reached a certain number of times. This is so | |
4281 | useful that there is a special way to do it, using the @dfn{ignore | |
4282 | count} of the breakpoint. Every breakpoint has an ignore count, which | |
4283 | is an integer. Most of the time, the ignore count is zero, and | |
4284 | therefore has no effect. But if your program reaches a breakpoint whose | |
4285 | ignore count is positive, then instead of stopping, it just decrements | |
4286 | the ignore count by one and continues. As a result, if the ignore count | |
4287 | value is @var{n}, the breakpoint does not stop the next @var{n} times | |
4288 | your program reaches it. | |
4289 | ||
4290 | @table @code | |
4291 | @kindex ignore | |
4292 | @item ignore @var{bnum} @var{count} | |
4293 | Set the ignore count of breakpoint number @var{bnum} to @var{count}. | |
4294 | The next @var{count} times the breakpoint is reached, your program's | |
4295 | execution does not stop; other than to decrement the ignore count, @value{GDBN} | |
4296 | takes no action. | |
4297 | ||
4298 | To make the breakpoint stop the next time it is reached, specify | |
4299 | a count of zero. | |
4300 | ||
4301 | When you use @code{continue} to resume execution of your program from a | |
4302 | breakpoint, you can specify an ignore count directly as an argument to | |
4303 | @code{continue}, rather than using @code{ignore}. @xref{Continuing and | |
79a6e687 | 4304 | Stepping,,Continuing and Stepping}. |
c906108c SS |
4305 | |
4306 | If a breakpoint has a positive ignore count and a condition, the | |
4307 | condition is not checked. Once the ignore count reaches zero, | |
4308 | @value{GDBN} resumes checking the condition. | |
4309 | ||
4310 | You could achieve the effect of the ignore count with a condition such | |
4311 | as @w{@samp{$foo-- <= 0}} using a debugger convenience variable that | |
4312 | is decremented each time. @xref{Convenience Vars, ,Convenience | |
79a6e687 | 4313 | Variables}. |
c906108c SS |
4314 | @end table |
4315 | ||
4316 | Ignore counts apply to breakpoints, watchpoints, and catchpoints. | |
4317 | ||
4318 | ||
6d2ebf8b | 4319 | @node Break Commands |
79a6e687 | 4320 | @subsection Breakpoint Command Lists |
c906108c SS |
4321 | |
4322 | @cindex breakpoint commands | |
4323 | You can give any breakpoint (or watchpoint or catchpoint) a series of | |
4324 | commands to execute when your program stops due to that breakpoint. For | |
4325 | example, you might want to print the values of certain expressions, or | |
4326 | enable other breakpoints. | |
4327 | ||
4328 | @table @code | |
4329 | @kindex commands | |
ca91424e | 4330 | @kindex end@r{ (breakpoint commands)} |
c906108c SS |
4331 | @item commands @r{[}@var{bnum}@r{]} |
4332 | @itemx @dots{} @var{command-list} @dots{} | |
4333 | @itemx end | |
4334 | Specify a list of commands for breakpoint number @var{bnum}. The commands | |
4335 | themselves appear on the following lines. Type a line containing just | |
4336 | @code{end} to terminate the commands. | |
4337 | ||
4338 | To remove all commands from a breakpoint, type @code{commands} and | |
4339 | follow it immediately with @code{end}; that is, give no commands. | |
4340 | ||
4341 | With no @var{bnum} argument, @code{commands} refers to the last | |
4342 | breakpoint, watchpoint, or catchpoint set (not to the breakpoint most | |
4343 | recently encountered). | |
4344 | @end table | |
4345 | ||
4346 | Pressing @key{RET} as a means of repeating the last @value{GDBN} command is | |
4347 | disabled within a @var{command-list}. | |
4348 | ||
4349 | You can use breakpoint commands to start your program up again. Simply | |
4350 | use the @code{continue} command, or @code{step}, or any other command | |
4351 | that resumes execution. | |
4352 | ||
4353 | Any other commands in the command list, after a command that resumes | |
4354 | execution, are ignored. This is because any time you resume execution | |
4355 | (even with a simple @code{next} or @code{step}), you may encounter | |
4356 | another breakpoint---which could have its own command list, leading to | |
4357 | ambiguities about which list to execute. | |
4358 | ||
4359 | @kindex silent | |
4360 | If the first command you specify in a command list is @code{silent}, the | |
4361 | usual message about stopping at a breakpoint is not printed. This may | |
4362 | be desirable for breakpoints that are to print a specific message and | |
4363 | then continue. If none of the remaining commands print anything, you | |
4364 | see no sign that the breakpoint was reached. @code{silent} is | |
4365 | meaningful only at the beginning of a breakpoint command list. | |
4366 | ||
4367 | The commands @code{echo}, @code{output}, and @code{printf} allow you to | |
4368 | print precisely controlled output, and are often useful in silent | |
79a6e687 | 4369 | breakpoints. @xref{Output, ,Commands for Controlled Output}. |
c906108c SS |
4370 | |
4371 | For example, here is how you could use breakpoint commands to print the | |
4372 | value of @code{x} at entry to @code{foo} whenever @code{x} is positive. | |
4373 | ||
474c8240 | 4374 | @smallexample |
c906108c SS |
4375 | break foo if x>0 |
4376 | commands | |
4377 | silent | |
4378 | printf "x is %d\n",x | |
4379 | cont | |
4380 | end | |
474c8240 | 4381 | @end smallexample |
c906108c SS |
4382 | |
4383 | One application for breakpoint commands is to compensate for one bug so | |
4384 | you can test for another. Put a breakpoint just after the erroneous line | |
4385 | of code, give it a condition to detect the case in which something | |
4386 | erroneous has been done, and give it commands to assign correct values | |
4387 | to any variables that need them. End with the @code{continue} command | |
4388 | so that your program does not stop, and start with the @code{silent} | |
4389 | command so that no output is produced. Here is an example: | |
4390 | ||
474c8240 | 4391 | @smallexample |
c906108c SS |
4392 | break 403 |
4393 | commands | |
4394 | silent | |
4395 | set x = y + 4 | |
4396 | cont | |
4397 | end | |
474c8240 | 4398 | @end smallexample |
c906108c | 4399 | |
c906108c | 4400 | @c @ifclear BARETARGET |
6d2ebf8b | 4401 | @node Error in Breakpoints |
d4f3574e | 4402 | @subsection ``Cannot insert breakpoints'' |
c906108c | 4403 | |
fa3a767f PA |
4404 | If you request too many active hardware-assisted breakpoints and |
4405 | watchpoints, you will see this error message: | |
d4f3574e SS |
4406 | |
4407 | @c FIXME: the precise wording of this message may change; the relevant | |
4408 | @c source change is not committed yet (Sep 3, 1999). | |
4409 | @smallexample | |
4410 | Stopped; cannot insert breakpoints. | |
4411 | You may have requested too many hardware breakpoints and watchpoints. | |
4412 | @end smallexample | |
4413 | ||
4414 | @noindent | |
4415 | This message is printed when you attempt to resume the program, since | |
4416 | only then @value{GDBN} knows exactly how many hardware breakpoints and | |
4417 | watchpoints it needs to insert. | |
4418 | ||
4419 | When this message is printed, you need to disable or remove some of the | |
4420 | hardware-assisted breakpoints and watchpoints, and then continue. | |
4421 | ||
79a6e687 | 4422 | @node Breakpoint-related Warnings |
1485d690 KB |
4423 | @subsection ``Breakpoint address adjusted...'' |
4424 | @cindex breakpoint address adjusted | |
4425 | ||
4426 | Some processor architectures place constraints on the addresses at | |
4427 | which breakpoints may be placed. For architectures thus constrained, | |
4428 | @value{GDBN} will attempt to adjust the breakpoint's address to comply | |
4429 | with the constraints dictated by the architecture. | |
4430 | ||
4431 | One example of such an architecture is the Fujitsu FR-V. The FR-V is | |
4432 | a VLIW architecture in which a number of RISC-like instructions may be | |
4433 | bundled together for parallel execution. The FR-V architecture | |
4434 | constrains the location of a breakpoint instruction within such a | |
4435 | bundle to the instruction with the lowest address. @value{GDBN} | |
4436 | honors this constraint by adjusting a breakpoint's address to the | |
4437 | first in the bundle. | |
4438 | ||
4439 | It is not uncommon for optimized code to have bundles which contain | |
4440 | instructions from different source statements, thus it may happen that | |
4441 | a breakpoint's address will be adjusted from one source statement to | |
4442 | another. Since this adjustment may significantly alter @value{GDBN}'s | |
4443 | breakpoint related behavior from what the user expects, a warning is | |
4444 | printed when the breakpoint is first set and also when the breakpoint | |
4445 | is hit. | |
4446 | ||
4447 | A warning like the one below is printed when setting a breakpoint | |
4448 | that's been subject to address adjustment: | |
4449 | ||
4450 | @smallexample | |
4451 | warning: Breakpoint address adjusted from 0x00010414 to 0x00010410. | |
4452 | @end smallexample | |
4453 | ||
4454 | Such warnings are printed both for user settable and @value{GDBN}'s | |
4455 | internal breakpoints. If you see one of these warnings, you should | |
4456 | verify that a breakpoint set at the adjusted address will have the | |
4457 | desired affect. If not, the breakpoint in question may be removed and | |
b383017d | 4458 | other breakpoints may be set which will have the desired behavior. |
1485d690 KB |
4459 | E.g., it may be sufficient to place the breakpoint at a later |
4460 | instruction. A conditional breakpoint may also be useful in some | |
4461 | cases to prevent the breakpoint from triggering too often. | |
4462 | ||
4463 | @value{GDBN} will also issue a warning when stopping at one of these | |
4464 | adjusted breakpoints: | |
4465 | ||
4466 | @smallexample | |
4467 | warning: Breakpoint 1 address previously adjusted from 0x00010414 | |
4468 | to 0x00010410. | |
4469 | @end smallexample | |
4470 | ||
4471 | When this warning is encountered, it may be too late to take remedial | |
4472 | action except in cases where the breakpoint is hit earlier or more | |
4473 | frequently than expected. | |
d4f3574e | 4474 | |
6d2ebf8b | 4475 | @node Continuing and Stepping |
79a6e687 | 4476 | @section Continuing and Stepping |
c906108c SS |
4477 | |
4478 | @cindex stepping | |
4479 | @cindex continuing | |
4480 | @cindex resuming execution | |
4481 | @dfn{Continuing} means resuming program execution until your program | |
4482 | completes normally. In contrast, @dfn{stepping} means executing just | |
4483 | one more ``step'' of your program, where ``step'' may mean either one | |
4484 | line of source code, or one machine instruction (depending on what | |
7a292a7a SS |
4485 | particular command you use). Either when continuing or when stepping, |
4486 | your program may stop even sooner, due to a breakpoint or a signal. (If | |
d4f3574e SS |
4487 | it stops due to a signal, you may want to use @code{handle}, or use |
4488 | @samp{signal 0} to resume execution. @xref{Signals, ,Signals}.) | |
c906108c SS |
4489 | |
4490 | @table @code | |
4491 | @kindex continue | |
41afff9a EZ |
4492 | @kindex c @r{(@code{continue})} |
4493 | @kindex fg @r{(resume foreground execution)} | |
c906108c SS |
4494 | @item continue @r{[}@var{ignore-count}@r{]} |
4495 | @itemx c @r{[}@var{ignore-count}@r{]} | |
4496 | @itemx fg @r{[}@var{ignore-count}@r{]} | |
4497 | Resume program execution, at the address where your program last stopped; | |
4498 | any breakpoints set at that address are bypassed. The optional argument | |
4499 | @var{ignore-count} allows you to specify a further number of times to | |
4500 | ignore a breakpoint at this location; its effect is like that of | |
79a6e687 | 4501 | @code{ignore} (@pxref{Conditions, ,Break Conditions}). |
c906108c SS |
4502 | |
4503 | The argument @var{ignore-count} is meaningful only when your program | |
4504 | stopped due to a breakpoint. At other times, the argument to | |
4505 | @code{continue} is ignored. | |
4506 | ||
d4f3574e SS |
4507 | The synonyms @code{c} and @code{fg} (for @dfn{foreground}, as the |
4508 | debugged program is deemed to be the foreground program) are provided | |
4509 | purely for convenience, and have exactly the same behavior as | |
4510 | @code{continue}. | |
c906108c SS |
4511 | @end table |
4512 | ||
4513 | To resume execution at a different place, you can use @code{return} | |
79a6e687 | 4514 | (@pxref{Returning, ,Returning from a Function}) to go back to the |
c906108c | 4515 | calling function; or @code{jump} (@pxref{Jumping, ,Continuing at a |
79a6e687 | 4516 | Different Address}) to go to an arbitrary location in your program. |
c906108c SS |
4517 | |
4518 | A typical technique for using stepping is to set a breakpoint | |
79a6e687 | 4519 | (@pxref{Breakpoints, ,Breakpoints; Watchpoints; and Catchpoints}) at the |
c906108c SS |
4520 | beginning of the function or the section of your program where a problem |
4521 | is believed to lie, run your program until it stops at that breakpoint, | |
4522 | and then step through the suspect area, examining the variables that are | |
4523 | interesting, until you see the problem happen. | |
4524 | ||
4525 | @table @code | |
4526 | @kindex step | |
41afff9a | 4527 | @kindex s @r{(@code{step})} |
c906108c SS |
4528 | @item step |
4529 | Continue running your program until control reaches a different source | |
4530 | line, then stop it and return control to @value{GDBN}. This command is | |
4531 | abbreviated @code{s}. | |
4532 | ||
4533 | @quotation | |
4534 | @c "without debugging information" is imprecise; actually "without line | |
4535 | @c numbers in the debugging information". (gcc -g1 has debugging info but | |
4536 | @c not line numbers). But it seems complex to try to make that | |
4537 | @c distinction here. | |
4538 | @emph{Warning:} If you use the @code{step} command while control is | |
4539 | within a function that was compiled without debugging information, | |
4540 | execution proceeds until control reaches a function that does have | |
4541 | debugging information. Likewise, it will not step into a function which | |
4542 | is compiled without debugging information. To step through functions | |
4543 | without debugging information, use the @code{stepi} command, described | |
4544 | below. | |
4545 | @end quotation | |
4546 | ||
4a92d011 EZ |
4547 | The @code{step} command only stops at the first instruction of a source |
4548 | line. This prevents the multiple stops that could otherwise occur in | |
4549 | @code{switch} statements, @code{for} loops, etc. @code{step} continues | |
4550 | to stop if a function that has debugging information is called within | |
4551 | the line. In other words, @code{step} @emph{steps inside} any functions | |
4552 | called within the line. | |
c906108c | 4553 | |
d4f3574e SS |
4554 | Also, the @code{step} command only enters a function if there is line |
4555 | number information for the function. Otherwise it acts like the | |
5d161b24 | 4556 | @code{next} command. This avoids problems when using @code{cc -gl} |
c906108c | 4557 | on MIPS machines. Previously, @code{step} entered subroutines if there |
5d161b24 | 4558 | was any debugging information about the routine. |
c906108c SS |
4559 | |
4560 | @item step @var{count} | |
4561 | Continue running as in @code{step}, but do so @var{count} times. If a | |
7a292a7a SS |
4562 | breakpoint is reached, or a signal not related to stepping occurs before |
4563 | @var{count} steps, stepping stops right away. | |
c906108c SS |
4564 | |
4565 | @kindex next | |
41afff9a | 4566 | @kindex n @r{(@code{next})} |
c906108c SS |
4567 | @item next @r{[}@var{count}@r{]} |
4568 | Continue to the next source line in the current (innermost) stack frame. | |
7a292a7a SS |
4569 | This is similar to @code{step}, but function calls that appear within |
4570 | the line of code are executed without stopping. Execution stops when | |
4571 | control reaches a different line of code at the original stack level | |
4572 | that was executing when you gave the @code{next} command. This command | |
4573 | is abbreviated @code{n}. | |
c906108c SS |
4574 | |
4575 | An argument @var{count} is a repeat count, as for @code{step}. | |
4576 | ||
4577 | ||
4578 | @c FIX ME!! Do we delete this, or is there a way it fits in with | |
4579 | @c the following paragraph? --- Vctoria | |
4580 | @c | |
4581 | @c @code{next} within a function that lacks debugging information acts like | |
4582 | @c @code{step}, but any function calls appearing within the code of the | |
4583 | @c function are executed without stopping. | |
4584 | ||
d4f3574e SS |
4585 | The @code{next} command only stops at the first instruction of a |
4586 | source line. This prevents multiple stops that could otherwise occur in | |
4a92d011 | 4587 | @code{switch} statements, @code{for} loops, etc. |
c906108c | 4588 | |
b90a5f51 CF |
4589 | @kindex set step-mode |
4590 | @item set step-mode | |
4591 | @cindex functions without line info, and stepping | |
4592 | @cindex stepping into functions with no line info | |
4593 | @itemx set step-mode on | |
4a92d011 | 4594 | The @code{set step-mode on} command causes the @code{step} command to |
b90a5f51 CF |
4595 | stop at the first instruction of a function which contains no debug line |
4596 | information rather than stepping over it. | |
4597 | ||
4a92d011 EZ |
4598 | This is useful in cases where you may be interested in inspecting the |
4599 | machine instructions of a function which has no symbolic info and do not | |
4600 | want @value{GDBN} to automatically skip over this function. | |
b90a5f51 CF |
4601 | |
4602 | @item set step-mode off | |
4a92d011 | 4603 | Causes the @code{step} command to step over any functions which contains no |
b90a5f51 CF |
4604 | debug information. This is the default. |
4605 | ||
9c16f35a EZ |
4606 | @item show step-mode |
4607 | Show whether @value{GDBN} will stop in or step over functions without | |
4608 | source line debug information. | |
4609 | ||
c906108c | 4610 | @kindex finish |
8dfa32fc | 4611 | @kindex fin @r{(@code{finish})} |
c906108c SS |
4612 | @item finish |
4613 | Continue running until just after function in the selected stack frame | |
8dfa32fc JB |
4614 | returns. Print the returned value (if any). This command can be |
4615 | abbreviated as @code{fin}. | |
c906108c SS |
4616 | |
4617 | Contrast this with the @code{return} command (@pxref{Returning, | |
79a6e687 | 4618 | ,Returning from a Function}). |
c906108c SS |
4619 | |
4620 | @kindex until | |
41afff9a | 4621 | @kindex u @r{(@code{until})} |
09d4efe1 | 4622 | @cindex run until specified location |
c906108c SS |
4623 | @item until |
4624 | @itemx u | |
4625 | Continue running until a source line past the current line, in the | |
4626 | current stack frame, is reached. This command is used to avoid single | |
4627 | stepping through a loop more than once. It is like the @code{next} | |
4628 | command, except that when @code{until} encounters a jump, it | |
4629 | automatically continues execution until the program counter is greater | |
4630 | than the address of the jump. | |
4631 | ||
4632 | This means that when you reach the end of a loop after single stepping | |
4633 | though it, @code{until} makes your program continue execution until it | |
4634 | exits the loop. In contrast, a @code{next} command at the end of a loop | |
4635 | simply steps back to the beginning of the loop, which forces you to step | |
4636 | through the next iteration. | |
4637 | ||
4638 | @code{until} always stops your program if it attempts to exit the current | |
4639 | stack frame. | |
4640 | ||
4641 | @code{until} may produce somewhat counterintuitive results if the order | |
4642 | of machine code does not match the order of the source lines. For | |
4643 | example, in the following excerpt from a debugging session, the @code{f} | |
4644 | (@code{frame}) command shows that execution is stopped at line | |
4645 | @code{206}; yet when we use @code{until}, we get to line @code{195}: | |
4646 | ||
474c8240 | 4647 | @smallexample |
c906108c SS |
4648 | (@value{GDBP}) f |
4649 | #0 main (argc=4, argv=0xf7fffae8) at m4.c:206 | |
4650 | 206 expand_input(); | |
4651 | (@value{GDBP}) until | |
4652 | 195 for ( ; argc > 0; NEXTARG) @{ | |
474c8240 | 4653 | @end smallexample |
c906108c SS |
4654 | |
4655 | This happened because, for execution efficiency, the compiler had | |
4656 | generated code for the loop closure test at the end, rather than the | |
4657 | start, of the loop---even though the test in a C @code{for}-loop is | |
4658 | written before the body of the loop. The @code{until} command appeared | |
4659 | to step back to the beginning of the loop when it advanced to this | |
4660 | expression; however, it has not really gone to an earlier | |
4661 | statement---not in terms of the actual machine code. | |
4662 | ||
4663 | @code{until} with no argument works by means of single | |
4664 | instruction stepping, and hence is slower than @code{until} with an | |
4665 | argument. | |
4666 | ||
4667 | @item until @var{location} | |
4668 | @itemx u @var{location} | |
4669 | Continue running your program until either the specified location is | |
4670 | reached, or the current stack frame returns. @var{location} is any of | |
2a25a5ba EZ |
4671 | the forms described in @ref{Specify Location}. |
4672 | This form of the command uses temporary breakpoints, and | |
c60eb6f1 EZ |
4673 | hence is quicker than @code{until} without an argument. The specified |
4674 | location is actually reached only if it is in the current frame. This | |
4675 | implies that @code{until} can be used to skip over recursive function | |
4676 | invocations. For instance in the code below, if the current location is | |
4677 | line @code{96}, issuing @code{until 99} will execute the program up to | |
db2e3e2e | 4678 | line @code{99} in the same invocation of factorial, i.e., after the inner |
c60eb6f1 EZ |
4679 | invocations have returned. |
4680 | ||
4681 | @smallexample | |
4682 | 94 int factorial (int value) | |
4683 | 95 @{ | |
4684 | 96 if (value > 1) @{ | |
4685 | 97 value *= factorial (value - 1); | |
4686 | 98 @} | |
4687 | 99 return (value); | |
4688 | 100 @} | |
4689 | @end smallexample | |
4690 | ||
4691 | ||
4692 | @kindex advance @var{location} | |
4693 | @itemx advance @var{location} | |
09d4efe1 | 4694 | Continue running the program up to the given @var{location}. An argument is |
2a25a5ba EZ |
4695 | required, which should be of one of the forms described in |
4696 | @ref{Specify Location}. | |
4697 | Execution will also stop upon exit from the current stack | |
c60eb6f1 EZ |
4698 | frame. This command is similar to @code{until}, but @code{advance} will |
4699 | not skip over recursive function calls, and the target location doesn't | |
4700 | have to be in the same frame as the current one. | |
4701 | ||
c906108c SS |
4702 | |
4703 | @kindex stepi | |
41afff9a | 4704 | @kindex si @r{(@code{stepi})} |
c906108c | 4705 | @item stepi |
96a2c332 | 4706 | @itemx stepi @var{arg} |
c906108c SS |
4707 | @itemx si |
4708 | Execute one machine instruction, then stop and return to the debugger. | |
4709 | ||
4710 | It is often useful to do @samp{display/i $pc} when stepping by machine | |
4711 | instructions. This makes @value{GDBN} automatically display the next | |
4712 | instruction to be executed, each time your program stops. @xref{Auto | |
79a6e687 | 4713 | Display,, Automatic Display}. |
c906108c SS |
4714 | |
4715 | An argument is a repeat count, as in @code{step}. | |
4716 | ||
4717 | @need 750 | |
4718 | @kindex nexti | |
41afff9a | 4719 | @kindex ni @r{(@code{nexti})} |
c906108c | 4720 | @item nexti |
96a2c332 | 4721 | @itemx nexti @var{arg} |
c906108c SS |
4722 | @itemx ni |
4723 | Execute one machine instruction, but if it is a function call, | |
4724 | proceed until the function returns. | |
4725 | ||
4726 | An argument is a repeat count, as in @code{next}. | |
4727 | @end table | |
4728 | ||
6d2ebf8b | 4729 | @node Signals |
c906108c SS |
4730 | @section Signals |
4731 | @cindex signals | |
4732 | ||
4733 | A signal is an asynchronous event that can happen in a program. The | |
4734 | operating system defines the possible kinds of signals, and gives each | |
4735 | kind a name and a number. For example, in Unix @code{SIGINT} is the | |
c8aa23ab | 4736 | signal a program gets when you type an interrupt character (often @kbd{Ctrl-c}); |
c906108c SS |
4737 | @code{SIGSEGV} is the signal a program gets from referencing a place in |
4738 | memory far away from all the areas in use; @code{SIGALRM} occurs when | |
4739 | the alarm clock timer goes off (which happens only if your program has | |
4740 | requested an alarm). | |
4741 | ||
4742 | @cindex fatal signals | |
4743 | Some signals, including @code{SIGALRM}, are a normal part of the | |
4744 | functioning of your program. Others, such as @code{SIGSEGV}, indicate | |
d4f3574e | 4745 | errors; these signals are @dfn{fatal} (they kill your program immediately) if the |
c906108c SS |
4746 | program has not specified in advance some other way to handle the signal. |
4747 | @code{SIGINT} does not indicate an error in your program, but it is normally | |
4748 | fatal so it can carry out the purpose of the interrupt: to kill the program. | |
4749 | ||
4750 | @value{GDBN} has the ability to detect any occurrence of a signal in your | |
4751 | program. You can tell @value{GDBN} in advance what to do for each kind of | |
4752 | signal. | |
4753 | ||
4754 | @cindex handling signals | |
24f93129 EZ |
4755 | Normally, @value{GDBN} is set up to let the non-erroneous signals like |
4756 | @code{SIGALRM} be silently passed to your program | |
4757 | (so as not to interfere with their role in the program's functioning) | |
c906108c SS |
4758 | but to stop your program immediately whenever an error signal happens. |
4759 | You can change these settings with the @code{handle} command. | |
4760 | ||
4761 | @table @code | |
4762 | @kindex info signals | |
09d4efe1 | 4763 | @kindex info handle |
c906108c | 4764 | @item info signals |
96a2c332 | 4765 | @itemx info handle |
c906108c SS |
4766 | Print a table of all the kinds of signals and how @value{GDBN} has been told to |
4767 | handle each one. You can use this to see the signal numbers of all | |
4768 | the defined types of signals. | |
4769 | ||
45ac1734 EZ |
4770 | @item info signals @var{sig} |
4771 | Similar, but print information only about the specified signal number. | |
4772 | ||
d4f3574e | 4773 | @code{info handle} is an alias for @code{info signals}. |
c906108c SS |
4774 | |
4775 | @kindex handle | |
45ac1734 | 4776 | @item handle @var{signal} @r{[}@var{keywords}@dots{}@r{]} |
5ece1a18 EZ |
4777 | Change the way @value{GDBN} handles signal @var{signal}. @var{signal} |
4778 | can be the number of a signal or its name (with or without the | |
24f93129 | 4779 | @samp{SIG} at the beginning); a list of signal numbers of the form |
5ece1a18 | 4780 | @samp{@var{low}-@var{high}}; or the word @samp{all}, meaning all the |
45ac1734 EZ |
4781 | known signals. Optional arguments @var{keywords}, described below, |
4782 | say what change to make. | |
c906108c SS |
4783 | @end table |
4784 | ||
4785 | @c @group | |
4786 | The keywords allowed by the @code{handle} command can be abbreviated. | |
4787 | Their full names are: | |
4788 | ||
4789 | @table @code | |
4790 | @item nostop | |
4791 | @value{GDBN} should not stop your program when this signal happens. It may | |
4792 | still print a message telling you that the signal has come in. | |
4793 | ||
4794 | @item stop | |
4795 | @value{GDBN} should stop your program when this signal happens. This implies | |
4796 | the @code{print} keyword as well. | |
4797 | ||
4798 | @item print | |
4799 | @value{GDBN} should print a message when this signal happens. | |
4800 | ||
4801 | @item noprint | |
4802 | @value{GDBN} should not mention the occurrence of the signal at all. This | |
4803 | implies the @code{nostop} keyword as well. | |
4804 | ||
4805 | @item pass | |
5ece1a18 | 4806 | @itemx noignore |
c906108c SS |
4807 | @value{GDBN} should allow your program to see this signal; your program |
4808 | can handle the signal, or else it may terminate if the signal is fatal | |
5ece1a18 | 4809 | and not handled. @code{pass} and @code{noignore} are synonyms. |
c906108c SS |
4810 | |
4811 | @item nopass | |
5ece1a18 | 4812 | @itemx ignore |
c906108c | 4813 | @value{GDBN} should not allow your program to see this signal. |
5ece1a18 | 4814 | @code{nopass} and @code{ignore} are synonyms. |
c906108c SS |
4815 | @end table |
4816 | @c @end group | |
4817 | ||
d4f3574e SS |
4818 | When a signal stops your program, the signal is not visible to the |
4819 | program until you | |
c906108c SS |
4820 | continue. Your program sees the signal then, if @code{pass} is in |
4821 | effect for the signal in question @emph{at that time}. In other words, | |
4822 | after @value{GDBN} reports a signal, you can use the @code{handle} | |
4823 | command with @code{pass} or @code{nopass} to control whether your | |
4824 | program sees that signal when you continue. | |
4825 | ||
24f93129 EZ |
4826 | The default is set to @code{nostop}, @code{noprint}, @code{pass} for |
4827 | non-erroneous signals such as @code{SIGALRM}, @code{SIGWINCH} and | |
4828 | @code{SIGCHLD}, and to @code{stop}, @code{print}, @code{pass} for the | |
4829 | erroneous signals. | |
4830 | ||
c906108c SS |
4831 | You can also use the @code{signal} command to prevent your program from |
4832 | seeing a signal, or cause it to see a signal it normally would not see, | |
4833 | or to give it any signal at any time. For example, if your program stopped | |
4834 | due to some sort of memory reference error, you might store correct | |
4835 | values into the erroneous variables and continue, hoping to see more | |
4836 | execution; but your program would probably terminate immediately as | |
4837 | a result of the fatal signal once it saw the signal. To prevent this, | |
4838 | you can continue with @samp{signal 0}. @xref{Signaling, ,Giving your | |
79a6e687 | 4839 | Program a Signal}. |
c906108c | 4840 | |
4aa995e1 PA |
4841 | @cindex extra signal information |
4842 | @anchor{extra signal information} | |
4843 | ||
4844 | On some targets, @value{GDBN} can inspect extra signal information | |
4845 | associated with the intercepted signal, before it is actually | |
4846 | delivered to the program being debugged. This information is exported | |
4847 | by the convenience variable @code{$_siginfo}, and consists of data | |
4848 | that is passed by the kernel to the signal handler at the time of the | |
4849 | receipt of a signal. The data type of the information itself is | |
4850 | target dependent. You can see the data type using the @code{ptype | |
4851 | $_siginfo} command. On Unix systems, it typically corresponds to the | |
4852 | standard @code{siginfo_t} type, as defined in the @file{signal.h} | |
4853 | system header. | |
4854 | ||
4855 | Here's an example, on a @sc{gnu}/Linux system, printing the stray | |
4856 | referenced address that raised a segmentation fault. | |
4857 | ||
4858 | @smallexample | |
4859 | @group | |
4860 | (@value{GDBP}) continue | |
4861 | Program received signal SIGSEGV, Segmentation fault. | |
4862 | 0x0000000000400766 in main () | |
4863 | 69 *(int *)p = 0; | |
4864 | (@value{GDBP}) ptype $_siginfo | |
4865 | type = struct @{ | |
4866 | int si_signo; | |
4867 | int si_errno; | |
4868 | int si_code; | |
4869 | union @{ | |
4870 | int _pad[28]; | |
4871 | struct @{...@} _kill; | |
4872 | struct @{...@} _timer; | |
4873 | struct @{...@} _rt; | |
4874 | struct @{...@} _sigchld; | |
4875 | struct @{...@} _sigfault; | |
4876 | struct @{...@} _sigpoll; | |
4877 | @} _sifields; | |
4878 | @} | |
4879 | (@value{GDBP}) ptype $_siginfo._sifields._sigfault | |
4880 | type = struct @{ | |
4881 | void *si_addr; | |
4882 | @} | |
4883 | (@value{GDBP}) p $_siginfo._sifields._sigfault.si_addr | |
4884 | $1 = (void *) 0x7ffff7ff7000 | |
4885 | @end group | |
4886 | @end smallexample | |
4887 | ||
4888 | Depending on target support, @code{$_siginfo} may also be writable. | |
4889 | ||
6d2ebf8b | 4890 | @node Thread Stops |
79a6e687 | 4891 | @section Stopping and Starting Multi-thread Programs |
c906108c | 4892 | |
0606b73b SL |
4893 | @cindex stopped threads |
4894 | @cindex threads, stopped | |
4895 | ||
4896 | @cindex continuing threads | |
4897 | @cindex threads, continuing | |
4898 | ||
4899 | @value{GDBN} supports debugging programs with multiple threads | |
4900 | (@pxref{Threads,, Debugging Programs with Multiple Threads}). There | |
4901 | are two modes of controlling execution of your program within the | |
4902 | debugger. In the default mode, referred to as @dfn{all-stop mode}, | |
4903 | when any thread in your program stops (for example, at a breakpoint | |
4904 | or while being stepped), all other threads in the program are also stopped by | |
4905 | @value{GDBN}. On some targets, @value{GDBN} also supports | |
4906 | @dfn{non-stop mode}, in which other threads can continue to run freely while | |
4907 | you examine the stopped thread in the debugger. | |
4908 | ||
4909 | @menu | |
4910 | * All-Stop Mode:: All threads stop when GDB takes control | |
4911 | * Non-Stop Mode:: Other threads continue to execute | |
4912 | * Background Execution:: Running your program asynchronously | |
4913 | * Thread-Specific Breakpoints:: Controlling breakpoints | |
4914 | * Interrupted System Calls:: GDB may interfere with system calls | |
4915 | @end menu | |
4916 | ||
4917 | @node All-Stop Mode | |
4918 | @subsection All-Stop Mode | |
4919 | ||
4920 | @cindex all-stop mode | |
4921 | ||
4922 | In all-stop mode, whenever your program stops under @value{GDBN} for any reason, | |
4923 | @emph{all} threads of execution stop, not just the current thread. This | |
4924 | allows you to examine the overall state of the program, including | |
4925 | switching between threads, without worrying that things may change | |
4926 | underfoot. | |
4927 | ||
4928 | Conversely, whenever you restart the program, @emph{all} threads start | |
4929 | executing. @emph{This is true even when single-stepping} with commands | |
4930 | like @code{step} or @code{next}. | |
4931 | ||
4932 | In particular, @value{GDBN} cannot single-step all threads in lockstep. | |
4933 | Since thread scheduling is up to your debugging target's operating | |
4934 | system (not controlled by @value{GDBN}), other threads may | |
4935 | execute more than one statement while the current thread completes a | |
4936 | single step. Moreover, in general other threads stop in the middle of a | |
4937 | statement, rather than at a clean statement boundary, when the program | |
4938 | stops. | |
4939 | ||
4940 | You might even find your program stopped in another thread after | |
4941 | continuing or even single-stepping. This happens whenever some other | |
4942 | thread runs into a breakpoint, a signal, or an exception before the | |
4943 | first thread completes whatever you requested. | |
4944 | ||
4945 | @cindex automatic thread selection | |
4946 | @cindex switching threads automatically | |
4947 | @cindex threads, automatic switching | |
4948 | Whenever @value{GDBN} stops your program, due to a breakpoint or a | |
4949 | signal, it automatically selects the thread where that breakpoint or | |
4950 | signal happened. @value{GDBN} alerts you to the context switch with a | |
4951 | message such as @samp{[Switching to Thread @var{n}]} to identify the | |
4952 | thread. | |
4953 | ||
4954 | On some OSes, you can modify @value{GDBN}'s default behavior by | |
4955 | locking the OS scheduler to allow only a single thread to run. | |
4956 | ||
4957 | @table @code | |
4958 | @item set scheduler-locking @var{mode} | |
4959 | @cindex scheduler locking mode | |
4960 | @cindex lock scheduler | |
4961 | Set the scheduler locking mode. If it is @code{off}, then there is no | |
4962 | locking and any thread may run at any time. If @code{on}, then only the | |
4963 | current thread may run when the inferior is resumed. The @code{step} | |
4964 | mode optimizes for single-stepping; it prevents other threads | |
4965 | from preempting the current thread while you are stepping, so that | |
4966 | the focus of debugging does not change unexpectedly. | |
4967 | Other threads only rarely (or never) get a chance to run | |
4968 | when you step. They are more likely to run when you @samp{next} over a | |
4969 | function call, and they are completely free to run when you use commands | |
4970 | like @samp{continue}, @samp{until}, or @samp{finish}. However, unless another | |
4971 | thread hits a breakpoint during its timeslice, @value{GDBN} does not change | |
4972 | the current thread away from the thread that you are debugging. | |
4973 | ||
4974 | @item show scheduler-locking | |
4975 | Display the current scheduler locking mode. | |
4976 | @end table | |
4977 | ||
d4db2f36 PA |
4978 | @cindex resume threads of multiple processes simultaneously |
4979 | By default, when you issue one of the execution commands such as | |
4980 | @code{continue}, @code{next} or @code{step}, @value{GDBN} allows only | |
4981 | threads of the current inferior to run. For example, if @value{GDBN} | |
4982 | is attached to two inferiors, each with two threads, the | |
4983 | @code{continue} command resumes only the two threads of the current | |
4984 | inferior. This is useful, for example, when you debug a program that | |
4985 | forks and you want to hold the parent stopped (so that, for instance, | |
4986 | it doesn't run to exit), while you debug the child. In other | |
4987 | situations, you may not be interested in inspecting the current state | |
4988 | of any of the processes @value{GDBN} is attached to, and you may want | |
4989 | to resume them all until some breakpoint is hit. In the latter case, | |
4990 | you can instruct @value{GDBN} to allow all threads of all the | |
4991 | inferiors to run with the @w{@code{set schedule-multiple}} command. | |
4992 | ||
4993 | @table @code | |
4994 | @kindex set schedule-multiple | |
4995 | @item set schedule-multiple | |
4996 | Set the mode for allowing threads of multiple processes to be resumed | |
4997 | when an execution command is issued. When @code{on}, all threads of | |
4998 | all processes are allowed to run. When @code{off}, only the threads | |
4999 | of the current process are resumed. The default is @code{off}. The | |
5000 | @code{scheduler-locking} mode takes precedence when set to @code{on}, | |
5001 | or while you are stepping and set to @code{step}. | |
5002 | ||
5003 | @item show schedule-multiple | |
5004 | Display the current mode for resuming the execution of threads of | |
5005 | multiple processes. | |
5006 | @end table | |
5007 | ||
0606b73b SL |
5008 | @node Non-Stop Mode |
5009 | @subsection Non-Stop Mode | |
5010 | ||
5011 | @cindex non-stop mode | |
5012 | ||
5013 | @c This section is really only a place-holder, and needs to be expanded | |
5014 | @c with more details. | |
5015 | ||
5016 | For some multi-threaded targets, @value{GDBN} supports an optional | |
5017 | mode of operation in which you can examine stopped program threads in | |
5018 | the debugger while other threads continue to execute freely. This | |
5019 | minimizes intrusion when debugging live systems, such as programs | |
5020 | where some threads have real-time constraints or must continue to | |
5021 | respond to external events. This is referred to as @dfn{non-stop} mode. | |
5022 | ||
5023 | In non-stop mode, when a thread stops to report a debugging event, | |
5024 | @emph{only} that thread is stopped; @value{GDBN} does not stop other | |
5025 | threads as well, in contrast to the all-stop mode behavior. Additionally, | |
5026 | execution commands such as @code{continue} and @code{step} apply by default | |
5027 | only to the current thread in non-stop mode, rather than all threads as | |
5028 | in all-stop mode. This allows you to control threads explicitly in | |
5029 | ways that are not possible in all-stop mode --- for example, stepping | |
5030 | one thread while allowing others to run freely, stepping | |
5031 | one thread while holding all others stopped, or stepping several threads | |
5032 | independently and simultaneously. | |
5033 | ||
5034 | To enter non-stop mode, use this sequence of commands before you run | |
5035 | or attach to your program: | |
5036 | ||
0606b73b SL |
5037 | @smallexample |
5038 | # Enable the async interface. | |
c6ebd6cf | 5039 | set target-async 1 |
0606b73b | 5040 | |
0606b73b SL |
5041 | # If using the CLI, pagination breaks non-stop. |
5042 | set pagination off | |
5043 | ||
5044 | # Finally, turn it on! | |
5045 | set non-stop on | |
5046 | @end smallexample | |
5047 | ||
5048 | You can use these commands to manipulate the non-stop mode setting: | |
5049 | ||
5050 | @table @code | |
5051 | @kindex set non-stop | |
5052 | @item set non-stop on | |
5053 | Enable selection of non-stop mode. | |
5054 | @item set non-stop off | |
5055 | Disable selection of non-stop mode. | |
5056 | @kindex show non-stop | |
5057 | @item show non-stop | |
5058 | Show the current non-stop enablement setting. | |
5059 | @end table | |
5060 | ||
5061 | Note these commands only reflect whether non-stop mode is enabled, | |
5062 | not whether the currently-executing program is being run in non-stop mode. | |
5063 | In particular, the @code{set non-stop} preference is only consulted when | |
5064 | @value{GDBN} starts or connects to the target program, and it is generally | |
5065 | not possible to switch modes once debugging has started. Furthermore, | |
5066 | since not all targets support non-stop mode, even when you have enabled | |
5067 | non-stop mode, @value{GDBN} may still fall back to all-stop operation by | |
5068 | default. | |
5069 | ||
5070 | In non-stop mode, all execution commands apply only to the current thread | |
5071 | by default. That is, @code{continue} only continues one thread. | |
5072 | To continue all threads, issue @code{continue -a} or @code{c -a}. | |
5073 | ||
5074 | You can use @value{GDBN}'s background execution commands | |
5075 | (@pxref{Background Execution}) to run some threads in the background | |
5076 | while you continue to examine or step others from @value{GDBN}. | |
5077 | The MI execution commands (@pxref{GDB/MI Program Execution}) are | |
5078 | always executed asynchronously in non-stop mode. | |
5079 | ||
5080 | Suspending execution is done with the @code{interrupt} command when | |
5081 | running in the background, or @kbd{Ctrl-c} during foreground execution. | |
5082 | In all-stop mode, this stops the whole process; | |
5083 | but in non-stop mode the interrupt applies only to the current thread. | |
5084 | To stop the whole program, use @code{interrupt -a}. | |
5085 | ||
5086 | Other execution commands do not currently support the @code{-a} option. | |
5087 | ||
5088 | In non-stop mode, when a thread stops, @value{GDBN} doesn't automatically make | |
5089 | that thread current, as it does in all-stop mode. This is because the | |
5090 | thread stop notifications are asynchronous with respect to @value{GDBN}'s | |
5091 | command interpreter, and it would be confusing if @value{GDBN} unexpectedly | |
5092 | changed to a different thread just as you entered a command to operate on the | |
5093 | previously current thread. | |
5094 | ||
5095 | @node Background Execution | |
5096 | @subsection Background Execution | |
5097 | ||
5098 | @cindex foreground execution | |
5099 | @cindex background execution | |
5100 | @cindex asynchronous execution | |
5101 | @cindex execution, foreground, background and asynchronous | |
5102 | ||
5103 | @value{GDBN}'s execution commands have two variants: the normal | |
5104 | foreground (synchronous) behavior, and a background | |
5105 | (asynchronous) behavior. In foreground execution, @value{GDBN} waits for | |
5106 | the program to report that some thread has stopped before prompting for | |
5107 | another command. In background execution, @value{GDBN} immediately gives | |
5108 | a command prompt so that you can issue other commands while your program runs. | |
5109 | ||
32fc0df9 PA |
5110 | You need to explicitly enable asynchronous mode before you can use |
5111 | background execution commands. You can use these commands to | |
5112 | manipulate the asynchronous mode setting: | |
5113 | ||
5114 | @table @code | |
5115 | @kindex set target-async | |
5116 | @item set target-async on | |
5117 | Enable asynchronous mode. | |
5118 | @item set target-async off | |
5119 | Disable asynchronous mode. | |
5120 | @kindex show target-async | |
5121 | @item show target-async | |
5122 | Show the current target-async setting. | |
5123 | @end table | |
5124 | ||
5125 | If the target doesn't support async mode, @value{GDBN} issues an error | |
5126 | message if you attempt to use the background execution commands. | |
5127 | ||
0606b73b SL |
5128 | To specify background execution, add a @code{&} to the command. For example, |
5129 | the background form of the @code{continue} command is @code{continue&}, or | |
5130 | just @code{c&}. The execution commands that accept background execution | |
5131 | are: | |
5132 | ||
5133 | @table @code | |
5134 | @kindex run& | |
5135 | @item run | |
5136 | @xref{Starting, , Starting your Program}. | |
5137 | ||
5138 | @item attach | |
5139 | @kindex attach& | |
5140 | @xref{Attach, , Debugging an Already-running Process}. | |
5141 | ||
5142 | @item step | |
5143 | @kindex step& | |
5144 | @xref{Continuing and Stepping, step}. | |
5145 | ||
5146 | @item stepi | |
5147 | @kindex stepi& | |
5148 | @xref{Continuing and Stepping, stepi}. | |
5149 | ||
5150 | @item next | |
5151 | @kindex next& | |
5152 | @xref{Continuing and Stepping, next}. | |
5153 | ||
7ce58dd2 DE |
5154 | @item nexti |
5155 | @kindex nexti& | |
5156 | @xref{Continuing and Stepping, nexti}. | |
5157 | ||
0606b73b SL |
5158 | @item continue |
5159 | @kindex continue& | |
5160 | @xref{Continuing and Stepping, continue}. | |
5161 | ||
5162 | @item finish | |
5163 | @kindex finish& | |
5164 | @xref{Continuing and Stepping, finish}. | |
5165 | ||
5166 | @item until | |
5167 | @kindex until& | |
5168 | @xref{Continuing and Stepping, until}. | |
5169 | ||
5170 | @end table | |
5171 | ||
5172 | Background execution is especially useful in conjunction with non-stop | |
5173 | mode for debugging programs with multiple threads; see @ref{Non-Stop Mode}. | |
5174 | However, you can also use these commands in the normal all-stop mode with | |
5175 | the restriction that you cannot issue another execution command until the | |
5176 | previous one finishes. Examples of commands that are valid in all-stop | |
5177 | mode while the program is running include @code{help} and @code{info break}. | |
5178 | ||
5179 | You can interrupt your program while it is running in the background by | |
5180 | using the @code{interrupt} command. | |
5181 | ||
5182 | @table @code | |
5183 | @kindex interrupt | |
5184 | @item interrupt | |
5185 | @itemx interrupt -a | |
5186 | ||
5187 | Suspend execution of the running program. In all-stop mode, | |
5188 | @code{interrupt} stops the whole process, but in non-stop mode, it stops | |
5189 | only the current thread. To stop the whole program in non-stop mode, | |
5190 | use @code{interrupt -a}. | |
5191 | @end table | |
5192 | ||
0606b73b SL |
5193 | @node Thread-Specific Breakpoints |
5194 | @subsection Thread-Specific Breakpoints | |
5195 | ||
c906108c | 5196 | When your program has multiple threads (@pxref{Threads,, Debugging |
79a6e687 | 5197 | Programs with Multiple Threads}), you can choose whether to set |
c906108c SS |
5198 | breakpoints on all threads, or on a particular thread. |
5199 | ||
5200 | @table @code | |
5201 | @cindex breakpoints and threads | |
5202 | @cindex thread breakpoints | |
5203 | @kindex break @dots{} thread @var{threadno} | |
5204 | @item break @var{linespec} thread @var{threadno} | |
5205 | @itemx break @var{linespec} thread @var{threadno} if @dots{} | |
5206 | @var{linespec} specifies source lines; there are several ways of | |
2a25a5ba EZ |
5207 | writing them (@pxref{Specify Location}), but the effect is always to |
5208 | specify some source line. | |
c906108c SS |
5209 | |
5210 | Use the qualifier @samp{thread @var{threadno}} with a breakpoint command | |
5211 | to specify that you only want @value{GDBN} to stop the program when a | |
5212 | particular thread reaches this breakpoint. @var{threadno} is one of the | |
5213 | numeric thread identifiers assigned by @value{GDBN}, shown in the first | |
5214 | column of the @samp{info threads} display. | |
5215 | ||
5216 | If you do not specify @samp{thread @var{threadno}} when you set a | |
5217 | breakpoint, the breakpoint applies to @emph{all} threads of your | |
5218 | program. | |
5219 | ||
5220 | You can use the @code{thread} qualifier on conditional breakpoints as | |
b6199126 DJ |
5221 | well; in this case, place @samp{thread @var{threadno}} before or |
5222 | after the breakpoint condition, like this: | |
c906108c SS |
5223 | |
5224 | @smallexample | |
2df3850c | 5225 | (@value{GDBP}) break frik.c:13 thread 28 if bartab > lim |
c906108c SS |
5226 | @end smallexample |
5227 | ||
5228 | @end table | |
5229 | ||
0606b73b SL |
5230 | @node Interrupted System Calls |
5231 | @subsection Interrupted System Calls | |
c906108c | 5232 | |
36d86913 MC |
5233 | @cindex thread breakpoints and system calls |
5234 | @cindex system calls and thread breakpoints | |
5235 | @cindex premature return from system calls | |
0606b73b SL |
5236 | There is an unfortunate side effect when using @value{GDBN} to debug |
5237 | multi-threaded programs. If one thread stops for a | |
36d86913 MC |
5238 | breakpoint, or for some other reason, and another thread is blocked in a |
5239 | system call, then the system call may return prematurely. This is a | |
5240 | consequence of the interaction between multiple threads and the signals | |
5241 | that @value{GDBN} uses to implement breakpoints and other events that | |
5242 | stop execution. | |
5243 | ||
5244 | To handle this problem, your program should check the return value of | |
5245 | each system call and react appropriately. This is good programming | |
5246 | style anyways. | |
5247 | ||
5248 | For example, do not write code like this: | |
5249 | ||
5250 | @smallexample | |
5251 | sleep (10); | |
5252 | @end smallexample | |
5253 | ||
5254 | The call to @code{sleep} will return early if a different thread stops | |
5255 | at a breakpoint or for some other reason. | |
5256 | ||
5257 | Instead, write this: | |
5258 | ||
5259 | @smallexample | |
5260 | int unslept = 10; | |
5261 | while (unslept > 0) | |
5262 | unslept = sleep (unslept); | |
5263 | @end smallexample | |
5264 | ||
5265 | A system call is allowed to return early, so the system is still | |
5266 | conforming to its specification. But @value{GDBN} does cause your | |
5267 | multi-threaded program to behave differently than it would without | |
5268 | @value{GDBN}. | |
5269 | ||
5270 | Also, @value{GDBN} uses internal breakpoints in the thread library to | |
5271 | monitor certain events such as thread creation and thread destruction. | |
5272 | When such an event happens, a system call in another thread may return | |
5273 | prematurely, even though your program does not appear to stop. | |
5274 | ||
c906108c | 5275 | |
bacec72f MS |
5276 | @node Reverse Execution |
5277 | @chapter Running programs backward | |
5278 | @cindex reverse execution | |
5279 | @cindex running programs backward | |
5280 | ||
5281 | When you are debugging a program, it is not unusual to realize that | |
5282 | you have gone too far, and some event of interest has already happened. | |
5283 | If the target environment supports it, @value{GDBN} can allow you to | |
5284 | ``rewind'' the program by running it backward. | |
5285 | ||
5286 | A target environment that supports reverse execution should be able | |
5287 | to ``undo'' the changes in machine state that have taken place as the | |
5288 | program was executing normally. Variables, registers etc.@: should | |
5289 | revert to their previous values. Obviously this requires a great | |
5290 | deal of sophistication on the part of the target environment; not | |
5291 | all target environments can support reverse execution. | |
5292 | ||
5293 | When a program is executed in reverse, the instructions that | |
5294 | have most recently been executed are ``un-executed'', in reverse | |
5295 | order. The program counter runs backward, following the previous | |
5296 | thread of execution in reverse. As each instruction is ``un-executed'', | |
5297 | the values of memory and/or registers that were changed by that | |
5298 | instruction are reverted to their previous states. After executing | |
5299 | a piece of source code in reverse, all side effects of that code | |
5300 | should be ``undone'', and all variables should be returned to their | |
5301 | prior values@footnote{ | |
5302 | Note that some side effects are easier to undo than others. For instance, | |
5303 | memory and registers are relatively easy, but device I/O is hard. Some | |
5304 | targets may be able undo things like device I/O, and some may not. | |
5305 | ||
5306 | The contract between @value{GDBN} and the reverse executing target | |
5307 | requires only that the target do something reasonable when | |
5308 | @value{GDBN} tells it to execute backwards, and then report the | |
5309 | results back to @value{GDBN}. Whatever the target reports back to | |
5310 | @value{GDBN}, @value{GDBN} will report back to the user. @value{GDBN} | |
5311 | assumes that the memory and registers that the target reports are in a | |
5312 | consistant state, but @value{GDBN} accepts whatever it is given. | |
5313 | }. | |
5314 | ||
5315 | If you are debugging in a target environment that supports | |
5316 | reverse execution, @value{GDBN} provides the following commands. | |
5317 | ||
5318 | @table @code | |
5319 | @kindex reverse-continue | |
5320 | @kindex rc @r{(@code{reverse-continue})} | |
5321 | @item reverse-continue @r{[}@var{ignore-count}@r{]} | |
5322 | @itemx rc @r{[}@var{ignore-count}@r{]} | |
5323 | Beginning at the point where your program last stopped, start executing | |
5324 | in reverse. Reverse execution will stop for breakpoints and synchronous | |
5325 | exceptions (signals), just like normal execution. Behavior of | |
5326 | asynchronous signals depends on the target environment. | |
5327 | ||
5328 | @kindex reverse-step | |
5329 | @kindex rs @r{(@code{step})} | |
5330 | @item reverse-step @r{[}@var{count}@r{]} | |
5331 | Run the program backward until control reaches the start of a | |
5332 | different source line; then stop it, and return control to @value{GDBN}. | |
5333 | ||
5334 | Like the @code{step} command, @code{reverse-step} will only stop | |
5335 | at the beginning of a source line. It ``un-executes'' the previously | |
5336 | executed source line. If the previous source line included calls to | |
5337 | debuggable functions, @code{reverse-step} will step (backward) into | |
5338 | the called function, stopping at the beginning of the @emph{last} | |
5339 | statement in the called function (typically a return statement). | |
5340 | ||
5341 | Also, as with the @code{step} command, if non-debuggable functions are | |
5342 | called, @code{reverse-step} will run thru them backward without stopping. | |
5343 | ||
5344 | @kindex reverse-stepi | |
5345 | @kindex rsi @r{(@code{reverse-stepi})} | |
5346 | @item reverse-stepi @r{[}@var{count}@r{]} | |
5347 | Reverse-execute one machine instruction. Note that the instruction | |
5348 | to be reverse-executed is @emph{not} the one pointed to by the program | |
5349 | counter, but the instruction executed prior to that one. For instance, | |
5350 | if the last instruction was a jump, @code{reverse-stepi} will take you | |
5351 | back from the destination of the jump to the jump instruction itself. | |
5352 | ||
5353 | @kindex reverse-next | |
5354 | @kindex rn @r{(@code{reverse-next})} | |
5355 | @item reverse-next @r{[}@var{count}@r{]} | |
5356 | Run backward to the beginning of the previous line executed in | |
5357 | the current (innermost) stack frame. If the line contains function | |
5358 | calls, they will be ``un-executed'' without stopping. Starting from | |
5359 | the first line of a function, @code{reverse-next} will take you back | |
5360 | to the caller of that function, @emph{before} the function was called, | |
5361 | just as the normal @code{next} command would take you from the last | |
5362 | line of a function back to its return to its caller | |
16af530a | 5363 | @footnote{Unless the code is too heavily optimized.}. |
bacec72f MS |
5364 | |
5365 | @kindex reverse-nexti | |
5366 | @kindex rni @r{(@code{reverse-nexti})} | |
5367 | @item reverse-nexti @r{[}@var{count}@r{]} | |
5368 | Like @code{nexti}, @code{reverse-nexti} executes a single instruction | |
5369 | in reverse, except that called functions are ``un-executed'' atomically. | |
5370 | That is, if the previously executed instruction was a return from | |
540aa8e7 | 5371 | another function, @code{reverse-nexti} will continue to execute |
bacec72f MS |
5372 | in reverse until the call to that function (from the current stack |
5373 | frame) is reached. | |
5374 | ||
5375 | @kindex reverse-finish | |
5376 | @item reverse-finish | |
5377 | Just as the @code{finish} command takes you to the point where the | |
5378 | current function returns, @code{reverse-finish} takes you to the point | |
5379 | where it was called. Instead of ending up at the end of the current | |
5380 | function invocation, you end up at the beginning. | |
5381 | ||
5382 | @kindex set exec-direction | |
5383 | @item set exec-direction | |
5384 | Set the direction of target execution. | |
5385 | @itemx set exec-direction reverse | |
5386 | @cindex execute forward or backward in time | |
5387 | @value{GDBN} will perform all execution commands in reverse, until the | |
5388 | exec-direction mode is changed to ``forward''. Affected commands include | |
5389 | @code{step, stepi, next, nexti, continue, and finish}. The @code{return} | |
5390 | command cannot be used in reverse mode. | |
5391 | @item set exec-direction forward | |
5392 | @value{GDBN} will perform all execution commands in the normal fashion. | |
5393 | This is the default. | |
5394 | @end table | |
5395 | ||
c906108c | 5396 | |
a2311334 EZ |
5397 | @node Process Record and Replay |
5398 | @chapter Recording Inferior's Execution and Replaying It | |
53cc454a HZ |
5399 | @cindex process record and replay |
5400 | @cindex recording inferior's execution and replaying it | |
5401 | ||
8e05493c EZ |
5402 | On some platforms, @value{GDBN} provides a special @dfn{process record |
5403 | and replay} target that can record a log of the process execution, and | |
5404 | replay it later with both forward and reverse execution commands. | |
a2311334 EZ |
5405 | |
5406 | @cindex replay mode | |
5407 | When this target is in use, if the execution log includes the record | |
5408 | for the next instruction, @value{GDBN} will debug in @dfn{replay | |
5409 | mode}. In the replay mode, the inferior does not really execute code | |
5410 | instructions. Instead, all the events that normally happen during | |
5411 | code execution are taken from the execution log. While code is not | |
5412 | really executed in replay mode, the values of registers (including the | |
5413 | program counter register) and the memory of the inferior are still | |
8e05493c EZ |
5414 | changed as they normally would. Their contents are taken from the |
5415 | execution log. | |
a2311334 EZ |
5416 | |
5417 | @cindex record mode | |
5418 | If the record for the next instruction is not in the execution log, | |
5419 | @value{GDBN} will debug in @dfn{record mode}. In this mode, the | |
5420 | inferior executes normally, and @value{GDBN} records the execution log | |
5421 | for future replay. | |
5422 | ||
8e05493c EZ |
5423 | The process record and replay target supports reverse execution |
5424 | (@pxref{Reverse Execution}), even if the platform on which the | |
5425 | inferior runs does not. However, the reverse execution is limited in | |
5426 | this case by the range of the instructions recorded in the execution | |
5427 | log. In other words, reverse execution on platforms that don't | |
5428 | support it directly can only be done in the replay mode. | |
5429 | ||
5430 | When debugging in the reverse direction, @value{GDBN} will work in | |
5431 | replay mode as long as the execution log includes the record for the | |
5432 | previous instruction; otherwise, it will work in record mode, if the | |
5433 | platform supports reverse execution, or stop if not. | |
5434 | ||
a2311334 EZ |
5435 | For architecture environments that support process record and replay, |
5436 | @value{GDBN} provides the following commands: | |
53cc454a HZ |
5437 | |
5438 | @table @code | |
5439 | @kindex target record | |
5440 | @kindex record | |
5441 | @kindex rec | |
5442 | @item target record | |
a2311334 EZ |
5443 | This command starts the process record and replay target. The process |
5444 | record and replay target can only debug a process that is already | |
5445 | running. Therefore, you need first to start the process with the | |
5446 | @kbd{run} or @kbd{start} commands, and then start the recording with | |
5447 | the @kbd{target record} command. | |
5448 | ||
5449 | Both @code{record} and @code{rec} are aliases of @code{target record}. | |
5450 | ||
5451 | @cindex displaced stepping, and process record and replay | |
5452 | Displaced stepping (@pxref{Maintenance Commands,, displaced stepping}) | |
5453 | will be automatically disabled when process record and replay target | |
5454 | is started. That's because the process record and replay target | |
5455 | doesn't support displaced stepping. | |
5456 | ||
5457 | @cindex non-stop mode, and process record and replay | |
5458 | @cindex asynchronous execution, and process record and replay | |
5459 | If the inferior is in the non-stop mode (@pxref{Non-Stop Mode}) or in | |
5460 | the asynchronous execution mode (@pxref{Background Execution}), the | |
5461 | process record and replay target cannot be started because it doesn't | |
5462 | support these two modes. | |
53cc454a HZ |
5463 | |
5464 | @kindex record stop | |
5465 | @kindex rec s | |
5466 | @item record stop | |
a2311334 EZ |
5467 | Stop the process record and replay target. When process record and |
5468 | replay target stops, the entire execution log will be deleted and the | |
5469 | inferior will either be terminated, or will remain in its final state. | |
53cc454a | 5470 | |
a2311334 EZ |
5471 | When you stop the process record and replay target in record mode (at |
5472 | the end of the execution log), the inferior will be stopped at the | |
5473 | next instruction that would have been recorded. In other words, if | |
5474 | you record for a while and then stop recording, the inferior process | |
5475 | will be left in the same state as if the recording never happened. | |
53cc454a | 5476 | |
a2311334 EZ |
5477 | On the other hand, if the process record and replay target is stopped |
5478 | while in replay mode (that is, not at the end of the execution log, | |
5479 | but at some earlier point), the inferior process will become ``live'' | |
5480 | at that earlier state, and it will then be possible to continue the | |
5481 | usual ``live'' debugging of the process from that state. | |
53cc454a | 5482 | |
a2311334 EZ |
5483 | When the inferior process exits, or @value{GDBN} detaches from it, |
5484 | process record and replay target will automatically stop itself. | |
53cc454a HZ |
5485 | |
5486 | @kindex set record insn-number-max | |
5487 | @item set record insn-number-max @var{limit} | |
5488 | Set the limit of instructions to be recorded. Default value is 200000. | |
5489 | ||
a2311334 EZ |
5490 | If @var{limit} is a positive number, then @value{GDBN} will start |
5491 | deleting instructions from the log once the number of the record | |
5492 | instructions becomes greater than @var{limit}. For every new recorded | |
5493 | instruction, @value{GDBN} will delete the earliest recorded | |
5494 | instruction to keep the number of recorded instructions at the limit. | |
5495 | (Since deleting recorded instructions loses information, @value{GDBN} | |
5496 | lets you control what happens when the limit is reached, by means of | |
5497 | the @code{stop-at-limit} option, described below.) | |
53cc454a | 5498 | |
a2311334 EZ |
5499 | If @var{limit} is zero, @value{GDBN} will never delete recorded |
5500 | instructions from the execution log. The number of recorded | |
5501 | instructions is unlimited in this case. | |
53cc454a HZ |
5502 | |
5503 | @kindex show record insn-number-max | |
5504 | @item show record insn-number-max | |
a2311334 | 5505 | Show the limit of instructions to be recorded. |
53cc454a HZ |
5506 | |
5507 | @kindex set record stop-at-limit | |
a2311334 EZ |
5508 | @item set record stop-at-limit |
5509 | Control the behavior when the number of recorded instructions reaches | |
5510 | the limit. If ON (the default), @value{GDBN} will stop when the limit | |
5511 | is reached for the first time and ask you whether you want to stop the | |
5512 | inferior or continue running it and recording the execution log. If | |
5513 | you decide to continue recording, each new recorded instruction will | |
5514 | cause the oldest one to be deleted. | |
53cc454a | 5515 | |
a2311334 EZ |
5516 | If this option is OFF, @value{GDBN} will automatically delete the |
5517 | oldest record to make room for each new one, without asking. | |
53cc454a HZ |
5518 | |
5519 | @kindex show record stop-at-limit | |
5520 | @item show record stop-at-limit | |
a2311334 | 5521 | Show the current setting of @code{stop-at-limit}. |
53cc454a | 5522 | |
29153c24 MS |
5523 | @kindex info record |
5524 | @item info record | |
5525 | Show various statistics about the state of process record and its | |
5526 | in-memory execution log buffer, including: | |
5527 | ||
5528 | @itemize @bullet | |
5529 | @item | |
5530 | Whether in record mode or replay mode. | |
5531 | @item | |
5532 | Lowest recorded instruction number (counting from when the current execution log started recording instructions). | |
5533 | @item | |
5534 | Highest recorded instruction number. | |
5535 | @item | |
5536 | Current instruction about to be replayed (if in replay mode). | |
5537 | @item | |
5538 | Number of instructions contained in the execution log. | |
5539 | @item | |
5540 | Maximum number of instructions that may be contained in the execution log. | |
5541 | @end itemize | |
53cc454a HZ |
5542 | |
5543 | @kindex record delete | |
5544 | @kindex rec del | |
5545 | @item record delete | |
a2311334 | 5546 | When record target runs in replay mode (``in the past''), delete the |
53cc454a | 5547 | subsequent execution log and begin to record a new execution log starting |
a2311334 | 5548 | from the current address. This means you will abandon the previously |
53cc454a HZ |
5549 | recorded ``future'' and begin recording a new ``future''. |
5550 | @end table | |
5551 | ||
5552 | ||
6d2ebf8b | 5553 | @node Stack |
c906108c SS |
5554 | @chapter Examining the Stack |
5555 | ||
5556 | When your program has stopped, the first thing you need to know is where it | |
5557 | stopped and how it got there. | |
5558 | ||
5559 | @cindex call stack | |
5d161b24 DB |
5560 | Each time your program performs a function call, information about the call |
5561 | is generated. | |
5562 | That information includes the location of the call in your program, | |
5563 | the arguments of the call, | |
c906108c | 5564 | and the local variables of the function being called. |
5d161b24 | 5565 | The information is saved in a block of data called a @dfn{stack frame}. |
c906108c SS |
5566 | The stack frames are allocated in a region of memory called the @dfn{call |
5567 | stack}. | |
5568 | ||
5569 | When your program stops, the @value{GDBN} commands for examining the | |
5570 | stack allow you to see all of this information. | |
5571 | ||
5572 | @cindex selected frame | |
5573 | One of the stack frames is @dfn{selected} by @value{GDBN} and many | |
5574 | @value{GDBN} commands refer implicitly to the selected frame. In | |
5575 | particular, whenever you ask @value{GDBN} for the value of a variable in | |
5576 | your program, the value is found in the selected frame. There are | |
5577 | special @value{GDBN} commands to select whichever frame you are | |
79a6e687 | 5578 | interested in. @xref{Selection, ,Selecting a Frame}. |
c906108c SS |
5579 | |
5580 | When your program stops, @value{GDBN} automatically selects the | |
5d161b24 | 5581 | currently executing frame and describes it briefly, similar to the |
79a6e687 | 5582 | @code{frame} command (@pxref{Frame Info, ,Information about a Frame}). |
c906108c SS |
5583 | |
5584 | @menu | |
5585 | * Frames:: Stack frames | |
5586 | * Backtrace:: Backtraces | |
5587 | * Selection:: Selecting a frame | |
5588 | * Frame Info:: Information on a frame | |
c906108c SS |
5589 | |
5590 | @end menu | |
5591 | ||
6d2ebf8b | 5592 | @node Frames |
79a6e687 | 5593 | @section Stack Frames |
c906108c | 5594 | |
d4f3574e | 5595 | @cindex frame, definition |
c906108c SS |
5596 | @cindex stack frame |
5597 | The call stack is divided up into contiguous pieces called @dfn{stack | |
5598 | frames}, or @dfn{frames} for short; each frame is the data associated | |
5599 | with one call to one function. The frame contains the arguments given | |
5600 | to the function, the function's local variables, and the address at | |
5601 | which the function is executing. | |
5602 | ||
5603 | @cindex initial frame | |
5604 | @cindex outermost frame | |
5605 | @cindex innermost frame | |
5606 | When your program is started, the stack has only one frame, that of the | |
5607 | function @code{main}. This is called the @dfn{initial} frame or the | |
5608 | @dfn{outermost} frame. Each time a function is called, a new frame is | |
5609 | made. Each time a function returns, the frame for that function invocation | |
5610 | is eliminated. If a function is recursive, there can be many frames for | |
5611 | the same function. The frame for the function in which execution is | |
5612 | actually occurring is called the @dfn{innermost} frame. This is the most | |
5613 | recently created of all the stack frames that still exist. | |
5614 | ||
5615 | @cindex frame pointer | |
5616 | Inside your program, stack frames are identified by their addresses. A | |
5617 | stack frame consists of many bytes, each of which has its own address; each | |
5618 | kind of computer has a convention for choosing one byte whose | |
5619 | address serves as the address of the frame. Usually this address is kept | |
e09f16f9 EZ |
5620 | in a register called the @dfn{frame pointer register} |
5621 | (@pxref{Registers, $fp}) while execution is going on in that frame. | |
c906108c SS |
5622 | |
5623 | @cindex frame number | |
5624 | @value{GDBN} assigns numbers to all existing stack frames, starting with | |
5625 | zero for the innermost frame, one for the frame that called it, | |
5626 | and so on upward. These numbers do not really exist in your program; | |
5627 | they are assigned by @value{GDBN} to give you a way of designating stack | |
5628 | frames in @value{GDBN} commands. | |
5629 | ||
6d2ebf8b SS |
5630 | @c The -fomit-frame-pointer below perennially causes hbox overflow |
5631 | @c underflow problems. | |
c906108c SS |
5632 | @cindex frameless execution |
5633 | Some compilers provide a way to compile functions so that they operate | |
e22ea452 | 5634 | without stack frames. (For example, the @value{NGCC} option |
474c8240 | 5635 | @smallexample |
6d2ebf8b | 5636 | @samp{-fomit-frame-pointer} |
474c8240 | 5637 | @end smallexample |
6d2ebf8b | 5638 | generates functions without a frame.) |
c906108c SS |
5639 | This is occasionally done with heavily used library functions to save |
5640 | the frame setup time. @value{GDBN} has limited facilities for dealing | |
5641 | with these function invocations. If the innermost function invocation | |
5642 | has no stack frame, @value{GDBN} nevertheless regards it as though | |
5643 | it had a separate frame, which is numbered zero as usual, allowing | |
5644 | correct tracing of the function call chain. However, @value{GDBN} has | |
5645 | no provision for frameless functions elsewhere in the stack. | |
5646 | ||
5647 | @table @code | |
d4f3574e | 5648 | @kindex frame@r{, command} |
41afff9a | 5649 | @cindex current stack frame |
c906108c | 5650 | @item frame @var{args} |
5d161b24 | 5651 | The @code{frame} command allows you to move from one stack frame to another, |
c906108c | 5652 | and to print the stack frame you select. @var{args} may be either the |
5d161b24 DB |
5653 | address of the frame or the stack frame number. Without an argument, |
5654 | @code{frame} prints the current stack frame. | |
c906108c SS |
5655 | |
5656 | @kindex select-frame | |
41afff9a | 5657 | @cindex selecting frame silently |
c906108c SS |
5658 | @item select-frame |
5659 | The @code{select-frame} command allows you to move from one stack frame | |
5660 | to another without printing the frame. This is the silent version of | |
5661 | @code{frame}. | |
5662 | @end table | |
5663 | ||
6d2ebf8b | 5664 | @node Backtrace |
c906108c SS |
5665 | @section Backtraces |
5666 | ||
09d4efe1 EZ |
5667 | @cindex traceback |
5668 | @cindex call stack traces | |
c906108c SS |
5669 | A backtrace is a summary of how your program got where it is. It shows one |
5670 | line per frame, for many frames, starting with the currently executing | |
5671 | frame (frame zero), followed by its caller (frame one), and on up the | |
5672 | stack. | |
5673 | ||
5674 | @table @code | |
5675 | @kindex backtrace | |
41afff9a | 5676 | @kindex bt @r{(@code{backtrace})} |
c906108c SS |
5677 | @item backtrace |
5678 | @itemx bt | |
5679 | Print a backtrace of the entire stack: one line per frame for all | |
5680 | frames in the stack. | |
5681 | ||
5682 | You can stop the backtrace at any time by typing the system interrupt | |
c8aa23ab | 5683 | character, normally @kbd{Ctrl-c}. |
c906108c SS |
5684 | |
5685 | @item backtrace @var{n} | |
5686 | @itemx bt @var{n} | |
5687 | Similar, but print only the innermost @var{n} frames. | |
5688 | ||
5689 | @item backtrace -@var{n} | |
5690 | @itemx bt -@var{n} | |
5691 | Similar, but print only the outermost @var{n} frames. | |
0f061b69 NR |
5692 | |
5693 | @item backtrace full | |
0f061b69 | 5694 | @itemx bt full |
dd74f6ae NR |
5695 | @itemx bt full @var{n} |
5696 | @itemx bt full -@var{n} | |
e7109c7e | 5697 | Print the values of the local variables also. @var{n} specifies the |
286ba84d | 5698 | number of frames to print, as described above. |
c906108c SS |
5699 | @end table |
5700 | ||
5701 | @kindex where | |
5702 | @kindex info stack | |
c906108c SS |
5703 | The names @code{where} and @code{info stack} (abbreviated @code{info s}) |
5704 | are additional aliases for @code{backtrace}. | |
5705 | ||
839c27b7 EZ |
5706 | @cindex multiple threads, backtrace |
5707 | In a multi-threaded program, @value{GDBN} by default shows the | |
5708 | backtrace only for the current thread. To display the backtrace for | |
5709 | several or all of the threads, use the command @code{thread apply} | |
5710 | (@pxref{Threads, thread apply}). For example, if you type @kbd{thread | |
5711 | apply all backtrace}, @value{GDBN} will display the backtrace for all | |
5712 | the threads; this is handy when you debug a core dump of a | |
5713 | multi-threaded program. | |
5714 | ||
c906108c SS |
5715 | Each line in the backtrace shows the frame number and the function name. |
5716 | The program counter value is also shown---unless you use @code{set | |
5717 | print address off}. The backtrace also shows the source file name and | |
5718 | line number, as well as the arguments to the function. The program | |
5719 | counter value is omitted if it is at the beginning of the code for that | |
5720 | line number. | |
5721 | ||
5722 | Here is an example of a backtrace. It was made with the command | |
5723 | @samp{bt 3}, so it shows the innermost three frames. | |
5724 | ||
5725 | @smallexample | |
5726 | @group | |
5d161b24 | 5727 | #0 m4_traceon (obs=0x24eb0, argc=1, argv=0x2b8c8) |
c906108c | 5728 | at builtin.c:993 |
4f5376b2 | 5729 | #1 0x6e38 in expand_macro (sym=0x2b600, data=...) at macro.c:242 |
c906108c SS |
5730 | #2 0x6840 in expand_token (obs=0x0, t=177664, td=0xf7fffb08) |
5731 | at macro.c:71 | |
5732 | (More stack frames follow...) | |
5733 | @end group | |
5734 | @end smallexample | |
5735 | ||
5736 | @noindent | |
5737 | The display for frame zero does not begin with a program counter | |
5738 | value, indicating that your program has stopped at the beginning of the | |
5739 | code for line @code{993} of @code{builtin.c}. | |
5740 | ||
4f5376b2 JB |
5741 | @noindent |
5742 | The value of parameter @code{data} in frame 1 has been replaced by | |
5743 | @code{@dots{}}. By default, @value{GDBN} prints the value of a parameter | |
5744 | only if it is a scalar (integer, pointer, enumeration, etc). See command | |
5745 | @kbd{set print frame-arguments} in @ref{Print Settings} for more details | |
5746 | on how to configure the way function parameter values are printed. | |
5747 | ||
18999be5 EZ |
5748 | @cindex value optimized out, in backtrace |
5749 | @cindex function call arguments, optimized out | |
5750 | If your program was compiled with optimizations, some compilers will | |
5751 | optimize away arguments passed to functions if those arguments are | |
5752 | never used after the call. Such optimizations generate code that | |
5753 | passes arguments through registers, but doesn't store those arguments | |
5754 | in the stack frame. @value{GDBN} has no way of displaying such | |
5755 | arguments in stack frames other than the innermost one. Here's what | |
5756 | such a backtrace might look like: | |
5757 | ||
5758 | @smallexample | |
5759 | @group | |
5760 | #0 m4_traceon (obs=0x24eb0, argc=1, argv=0x2b8c8) | |
5761 | at builtin.c:993 | |
5762 | #1 0x6e38 in expand_macro (sym=<value optimized out>) at macro.c:242 | |
5763 | #2 0x6840 in expand_token (obs=0x0, t=<value optimized out>, td=0xf7fffb08) | |
5764 | at macro.c:71 | |
5765 | (More stack frames follow...) | |
5766 | @end group | |
5767 | @end smallexample | |
5768 | ||
5769 | @noindent | |
5770 | The values of arguments that were not saved in their stack frames are | |
5771 | shown as @samp{<value optimized out>}. | |
5772 | ||
5773 | If you need to display the values of such optimized-out arguments, | |
5774 | either deduce that from other variables whose values depend on the one | |
5775 | you are interested in, or recompile without optimizations. | |
5776 | ||
a8f24a35 EZ |
5777 | @cindex backtrace beyond @code{main} function |
5778 | @cindex program entry point | |
5779 | @cindex startup code, and backtrace | |
25d29d70 AC |
5780 | Most programs have a standard user entry point---a place where system |
5781 | libraries and startup code transition into user code. For C this is | |
d416eeec EZ |
5782 | @code{main}@footnote{ |
5783 | Note that embedded programs (the so-called ``free-standing'' | |
5784 | environment) are not required to have a @code{main} function as the | |
5785 | entry point. They could even have multiple entry points.}. | |
5786 | When @value{GDBN} finds the entry function in a backtrace | |
25d29d70 AC |
5787 | it will terminate the backtrace, to avoid tracing into highly |
5788 | system-specific (and generally uninteresting) code. | |
5789 | ||
5790 | If you need to examine the startup code, or limit the number of levels | |
5791 | in a backtrace, you can change this behavior: | |
95f90d25 DJ |
5792 | |
5793 | @table @code | |
25d29d70 AC |
5794 | @item set backtrace past-main |
5795 | @itemx set backtrace past-main on | |
4644b6e3 | 5796 | @kindex set backtrace |
25d29d70 AC |
5797 | Backtraces will continue past the user entry point. |
5798 | ||
5799 | @item set backtrace past-main off | |
95f90d25 DJ |
5800 | Backtraces will stop when they encounter the user entry point. This is the |
5801 | default. | |
5802 | ||
25d29d70 | 5803 | @item show backtrace past-main |
4644b6e3 | 5804 | @kindex show backtrace |
25d29d70 AC |
5805 | Display the current user entry point backtrace policy. |
5806 | ||
2315ffec RC |
5807 | @item set backtrace past-entry |
5808 | @itemx set backtrace past-entry on | |
a8f24a35 | 5809 | Backtraces will continue past the internal entry point of an application. |
2315ffec RC |
5810 | This entry point is encoded by the linker when the application is built, |
5811 | and is likely before the user entry point @code{main} (or equivalent) is called. | |
5812 | ||
5813 | @item set backtrace past-entry off | |
d3e8051b | 5814 | Backtraces will stop when they encounter the internal entry point of an |
2315ffec RC |
5815 | application. This is the default. |
5816 | ||
5817 | @item show backtrace past-entry | |
5818 | Display the current internal entry point backtrace policy. | |
5819 | ||
25d29d70 AC |
5820 | @item set backtrace limit @var{n} |
5821 | @itemx set backtrace limit 0 | |
5822 | @cindex backtrace limit | |
5823 | Limit the backtrace to @var{n} levels. A value of zero means | |
5824 | unlimited. | |
95f90d25 | 5825 | |
25d29d70 AC |
5826 | @item show backtrace limit |
5827 | Display the current limit on backtrace levels. | |
95f90d25 DJ |
5828 | @end table |
5829 | ||
6d2ebf8b | 5830 | @node Selection |
79a6e687 | 5831 | @section Selecting a Frame |
c906108c SS |
5832 | |
5833 | Most commands for examining the stack and other data in your program work on | |
5834 | whichever stack frame is selected at the moment. Here are the commands for | |
5835 | selecting a stack frame; all of them finish by printing a brief description | |
5836 | of the stack frame just selected. | |
5837 | ||
5838 | @table @code | |
d4f3574e | 5839 | @kindex frame@r{, selecting} |
41afff9a | 5840 | @kindex f @r{(@code{frame})} |
c906108c SS |
5841 | @item frame @var{n} |
5842 | @itemx f @var{n} | |
5843 | Select frame number @var{n}. Recall that frame zero is the innermost | |
5844 | (currently executing) frame, frame one is the frame that called the | |
5845 | innermost one, and so on. The highest-numbered frame is the one for | |
5846 | @code{main}. | |
5847 | ||
5848 | @item frame @var{addr} | |
5849 | @itemx f @var{addr} | |
5850 | Select the frame at address @var{addr}. This is useful mainly if the | |
5851 | chaining of stack frames has been damaged by a bug, making it | |
5852 | impossible for @value{GDBN} to assign numbers properly to all frames. In | |
5853 | addition, this can be useful when your program has multiple stacks and | |
5854 | switches between them. | |
5855 | ||
c906108c SS |
5856 | On the SPARC architecture, @code{frame} needs two addresses to |
5857 | select an arbitrary frame: a frame pointer and a stack pointer. | |
5858 | ||
5859 | On the MIPS and Alpha architecture, it needs two addresses: a stack | |
5860 | pointer and a program counter. | |
5861 | ||
5862 | On the 29k architecture, it needs three addresses: a register stack | |
5863 | pointer, a program counter, and a memory stack pointer. | |
c906108c SS |
5864 | |
5865 | @kindex up | |
5866 | @item up @var{n} | |
5867 | Move @var{n} frames up the stack. For positive numbers @var{n}, this | |
5868 | advances toward the outermost frame, to higher frame numbers, to frames | |
5869 | that have existed longer. @var{n} defaults to one. | |
5870 | ||
5871 | @kindex down | |
41afff9a | 5872 | @kindex do @r{(@code{down})} |
c906108c SS |
5873 | @item down @var{n} |
5874 | Move @var{n} frames down the stack. For positive numbers @var{n}, this | |
5875 | advances toward the innermost frame, to lower frame numbers, to frames | |
5876 | that were created more recently. @var{n} defaults to one. You may | |
5877 | abbreviate @code{down} as @code{do}. | |
5878 | @end table | |
5879 | ||
5880 | All of these commands end by printing two lines of output describing the | |
5881 | frame. The first line shows the frame number, the function name, the | |
5882 | arguments, and the source file and line number of execution in that | |
5d161b24 | 5883 | frame. The second line shows the text of that source line. |
c906108c SS |
5884 | |
5885 | @need 1000 | |
5886 | For example: | |
5887 | ||
5888 | @smallexample | |
5889 | @group | |
5890 | (@value{GDBP}) up | |
5891 | #1 0x22f0 in main (argc=1, argv=0xf7fffbf4, env=0xf7fffbfc) | |
5892 | at env.c:10 | |
5893 | 10 read_input_file (argv[i]); | |
5894 | @end group | |
5895 | @end smallexample | |
5896 | ||
5897 | After such a printout, the @code{list} command with no arguments | |
5898 | prints ten lines centered on the point of execution in the frame. | |
87885426 FN |
5899 | You can also edit the program at the point of execution with your favorite |
5900 | editing program by typing @code{edit}. | |
79a6e687 | 5901 | @xref{List, ,Printing Source Lines}, |
87885426 | 5902 | for details. |
c906108c SS |
5903 | |
5904 | @table @code | |
5905 | @kindex down-silently | |
5906 | @kindex up-silently | |
5907 | @item up-silently @var{n} | |
5908 | @itemx down-silently @var{n} | |
5909 | These two commands are variants of @code{up} and @code{down}, | |
5910 | respectively; they differ in that they do their work silently, without | |
5911 | causing display of the new frame. They are intended primarily for use | |
5912 | in @value{GDBN} command scripts, where the output might be unnecessary and | |
5913 | distracting. | |
5914 | @end table | |
5915 | ||
6d2ebf8b | 5916 | @node Frame Info |
79a6e687 | 5917 | @section Information About a Frame |
c906108c SS |
5918 | |
5919 | There are several other commands to print information about the selected | |
5920 | stack frame. | |
5921 | ||
5922 | @table @code | |
5923 | @item frame | |
5924 | @itemx f | |
5925 | When used without any argument, this command does not change which | |
5926 | frame is selected, but prints a brief description of the currently | |
5927 | selected stack frame. It can be abbreviated @code{f}. With an | |
5928 | argument, this command is used to select a stack frame. | |
79a6e687 | 5929 | @xref{Selection, ,Selecting a Frame}. |
c906108c SS |
5930 | |
5931 | @kindex info frame | |
41afff9a | 5932 | @kindex info f @r{(@code{info frame})} |
c906108c SS |
5933 | @item info frame |
5934 | @itemx info f | |
5935 | This command prints a verbose description of the selected stack frame, | |
5936 | including: | |
5937 | ||
5938 | @itemize @bullet | |
5d161b24 DB |
5939 | @item |
5940 | the address of the frame | |
c906108c SS |
5941 | @item |
5942 | the address of the next frame down (called by this frame) | |
5943 | @item | |
5944 | the address of the next frame up (caller of this frame) | |
5945 | @item | |
5946 | the language in which the source code corresponding to this frame is written | |
5947 | @item | |
5948 | the address of the frame's arguments | |
5949 | @item | |
d4f3574e SS |
5950 | the address of the frame's local variables |
5951 | @item | |
c906108c SS |
5952 | the program counter saved in it (the address of execution in the caller frame) |
5953 | @item | |
5954 | which registers were saved in the frame | |
5955 | @end itemize | |
5956 | ||
5957 | @noindent The verbose description is useful when | |
5958 | something has gone wrong that has made the stack format fail to fit | |
5959 | the usual conventions. | |
5960 | ||
5961 | @item info frame @var{addr} | |
5962 | @itemx info f @var{addr} | |
5963 | Print a verbose description of the frame at address @var{addr}, without | |
5964 | selecting that frame. The selected frame remains unchanged by this | |
5965 | command. This requires the same kind of address (more than one for some | |
5966 | architectures) that you specify in the @code{frame} command. | |
79a6e687 | 5967 | @xref{Selection, ,Selecting a Frame}. |
c906108c SS |
5968 | |
5969 | @kindex info args | |
5970 | @item info args | |
5971 | Print the arguments of the selected frame, each on a separate line. | |
5972 | ||
5973 | @item info locals | |
5974 | @kindex info locals | |
5975 | Print the local variables of the selected frame, each on a separate | |
5976 | line. These are all variables (declared either static or automatic) | |
5977 | accessible at the point of execution of the selected frame. | |
5978 | ||
c906108c | 5979 | @kindex info catch |
d4f3574e SS |
5980 | @cindex catch exceptions, list active handlers |
5981 | @cindex exception handlers, how to list | |
c906108c SS |
5982 | @item info catch |
5983 | Print a list of all the exception handlers that are active in the | |
5984 | current stack frame at the current point of execution. To see other | |
5985 | exception handlers, visit the associated frame (using the @code{up}, | |
5986 | @code{down}, or @code{frame} commands); then type @code{info catch}. | |
79a6e687 | 5987 | @xref{Set Catchpoints, , Setting Catchpoints}. |
53a5351d | 5988 | |
c906108c SS |
5989 | @end table |
5990 | ||
c906108c | 5991 | |
6d2ebf8b | 5992 | @node Source |
c906108c SS |
5993 | @chapter Examining Source Files |
5994 | ||
5995 | @value{GDBN} can print parts of your program's source, since the debugging | |
5996 | information recorded in the program tells @value{GDBN} what source files were | |
5997 | used to build it. When your program stops, @value{GDBN} spontaneously prints | |
5998 | the line where it stopped. Likewise, when you select a stack frame | |
79a6e687 | 5999 | (@pxref{Selection, ,Selecting a Frame}), @value{GDBN} prints the line where |
c906108c SS |
6000 | execution in that frame has stopped. You can print other portions of |
6001 | source files by explicit command. | |
6002 | ||
7a292a7a | 6003 | If you use @value{GDBN} through its @sc{gnu} Emacs interface, you may |
d4f3574e | 6004 | prefer to use Emacs facilities to view source; see @ref{Emacs, ,Using |
7a292a7a | 6005 | @value{GDBN} under @sc{gnu} Emacs}. |
c906108c SS |
6006 | |
6007 | @menu | |
6008 | * List:: Printing source lines | |
2a25a5ba | 6009 | * Specify Location:: How to specify code locations |
87885426 | 6010 | * Edit:: Editing source files |
c906108c | 6011 | * Search:: Searching source files |
c906108c SS |
6012 | * Source Path:: Specifying source directories |
6013 | * Machine Code:: Source and machine code | |
6014 | @end menu | |
6015 | ||
6d2ebf8b | 6016 | @node List |
79a6e687 | 6017 | @section Printing Source Lines |
c906108c SS |
6018 | |
6019 | @kindex list | |
41afff9a | 6020 | @kindex l @r{(@code{list})} |
c906108c | 6021 | To print lines from a source file, use the @code{list} command |
5d161b24 | 6022 | (abbreviated @code{l}). By default, ten lines are printed. |
2a25a5ba EZ |
6023 | There are several ways to specify what part of the file you want to |
6024 | print; see @ref{Specify Location}, for the full list. | |
c906108c SS |
6025 | |
6026 | Here are the forms of the @code{list} command most commonly used: | |
6027 | ||
6028 | @table @code | |
6029 | @item list @var{linenum} | |
6030 | Print lines centered around line number @var{linenum} in the | |
6031 | current source file. | |
6032 | ||
6033 | @item list @var{function} | |
6034 | Print lines centered around the beginning of function | |
6035 | @var{function}. | |
6036 | ||
6037 | @item list | |
6038 | Print more lines. If the last lines printed were printed with a | |
6039 | @code{list} command, this prints lines following the last lines | |
6040 | printed; however, if the last line printed was a solitary line printed | |
6041 | as part of displaying a stack frame (@pxref{Stack, ,Examining the | |
6042 | Stack}), this prints lines centered around that line. | |
6043 | ||
6044 | @item list - | |
6045 | Print lines just before the lines last printed. | |
6046 | @end table | |
6047 | ||
9c16f35a | 6048 | @cindex @code{list}, how many lines to display |
c906108c SS |
6049 | By default, @value{GDBN} prints ten source lines with any of these forms of |
6050 | the @code{list} command. You can change this using @code{set listsize}: | |
6051 | ||
6052 | @table @code | |
6053 | @kindex set listsize | |
6054 | @item set listsize @var{count} | |
6055 | Make the @code{list} command display @var{count} source lines (unless | |
6056 | the @code{list} argument explicitly specifies some other number). | |
6057 | ||
6058 | @kindex show listsize | |
6059 | @item show listsize | |
6060 | Display the number of lines that @code{list} prints. | |
6061 | @end table | |
6062 | ||
6063 | Repeating a @code{list} command with @key{RET} discards the argument, | |
6064 | so it is equivalent to typing just @code{list}. This is more useful | |
6065 | than listing the same lines again. An exception is made for an | |
6066 | argument of @samp{-}; that argument is preserved in repetition so that | |
6067 | each repetition moves up in the source file. | |
6068 | ||
c906108c SS |
6069 | In general, the @code{list} command expects you to supply zero, one or two |
6070 | @dfn{linespecs}. Linespecs specify source lines; there are several ways | |
2a25a5ba EZ |
6071 | of writing them (@pxref{Specify Location}), but the effect is always |
6072 | to specify some source line. | |
6073 | ||
c906108c SS |
6074 | Here is a complete description of the possible arguments for @code{list}: |
6075 | ||
6076 | @table @code | |
6077 | @item list @var{linespec} | |
6078 | Print lines centered around the line specified by @var{linespec}. | |
6079 | ||
6080 | @item list @var{first},@var{last} | |
6081 | Print lines from @var{first} to @var{last}. Both arguments are | |
2a25a5ba EZ |
6082 | linespecs. When a @code{list} command has two linespecs, and the |
6083 | source file of the second linespec is omitted, this refers to | |
6084 | the same source file as the first linespec. | |
c906108c SS |
6085 | |
6086 | @item list ,@var{last} | |
6087 | Print lines ending with @var{last}. | |
6088 | ||
6089 | @item list @var{first}, | |
6090 | Print lines starting with @var{first}. | |
6091 | ||
6092 | @item list + | |
6093 | Print lines just after the lines last printed. | |
6094 | ||
6095 | @item list - | |
6096 | Print lines just before the lines last printed. | |
6097 | ||
6098 | @item list | |
6099 | As described in the preceding table. | |
6100 | @end table | |
6101 | ||
2a25a5ba EZ |
6102 | @node Specify Location |
6103 | @section Specifying a Location | |
6104 | @cindex specifying location | |
6105 | @cindex linespec | |
c906108c | 6106 | |
2a25a5ba EZ |
6107 | Several @value{GDBN} commands accept arguments that specify a location |
6108 | of your program's code. Since @value{GDBN} is a source-level | |
6109 | debugger, a location usually specifies some line in the source code; | |
6110 | for that reason, locations are also known as @dfn{linespecs}. | |
c906108c | 6111 | |
2a25a5ba EZ |
6112 | Here are all the different ways of specifying a code location that |
6113 | @value{GDBN} understands: | |
c906108c | 6114 | |
2a25a5ba EZ |
6115 | @table @code |
6116 | @item @var{linenum} | |
6117 | Specifies the line number @var{linenum} of the current source file. | |
c906108c | 6118 | |
2a25a5ba EZ |
6119 | @item -@var{offset} |
6120 | @itemx +@var{offset} | |
6121 | Specifies the line @var{offset} lines before or after the @dfn{current | |
6122 | line}. For the @code{list} command, the current line is the last one | |
6123 | printed; for the breakpoint commands, this is the line at which | |
6124 | execution stopped in the currently selected @dfn{stack frame} | |
6125 | (@pxref{Frames, ,Frames}, for a description of stack frames.) When | |
6126 | used as the second of the two linespecs in a @code{list} command, | |
6127 | this specifies the line @var{offset} lines up or down from the first | |
6128 | linespec. | |
6129 | ||
6130 | @item @var{filename}:@var{linenum} | |
6131 | Specifies the line @var{linenum} in the source file @var{filename}. | |
c906108c SS |
6132 | |
6133 | @item @var{function} | |
6134 | Specifies the line that begins the body of the function @var{function}. | |
2a25a5ba | 6135 | For example, in C, this is the line with the open brace. |
c906108c SS |
6136 | |
6137 | @item @var{filename}:@var{function} | |
2a25a5ba EZ |
6138 | Specifies the line that begins the body of the function @var{function} |
6139 | in the file @var{filename}. You only need the file name with a | |
6140 | function name to avoid ambiguity when there are identically named | |
6141 | functions in different source files. | |
c906108c SS |
6142 | |
6143 | @item *@var{address} | |
2a25a5ba EZ |
6144 | Specifies the program address @var{address}. For line-oriented |
6145 | commands, such as @code{list} and @code{edit}, this specifies a source | |
6146 | line that contains @var{address}. For @code{break} and other | |
6147 | breakpoint oriented commands, this can be used to set breakpoints in | |
6148 | parts of your program which do not have debugging information or | |
6149 | source files. | |
6150 | ||
6151 | Here @var{address} may be any expression valid in the current working | |
6152 | language (@pxref{Languages, working language}) that specifies a code | |
5fa54e5d EZ |
6153 | address. In addition, as a convenience, @value{GDBN} extends the |
6154 | semantics of expressions used in locations to cover the situations | |
6155 | that frequently happen during debugging. Here are the various forms | |
6156 | of @var{address}: | |
2a25a5ba EZ |
6157 | |
6158 | @table @code | |
6159 | @item @var{expression} | |
6160 | Any expression valid in the current working language. | |
6161 | ||
6162 | @item @var{funcaddr} | |
6163 | An address of a function or procedure derived from its name. In C, | |
6164 | C@t{++}, Java, Objective-C, Fortran, minimal, and assembly, this is | |
6165 | simply the function's name @var{function} (and actually a special case | |
6166 | of a valid expression). In Pascal and Modula-2, this is | |
6167 | @code{&@var{function}}. In Ada, this is @code{@var{function}'Address} | |
6168 | (although the Pascal form also works). | |
6169 | ||
6170 | This form specifies the address of the function's first instruction, | |
6171 | before the stack frame and arguments have been set up. | |
6172 | ||
6173 | @item '@var{filename}'::@var{funcaddr} | |
6174 | Like @var{funcaddr} above, but also specifies the name of the source | |
6175 | file explicitly. This is useful if the name of the function does not | |
6176 | specify the function unambiguously, e.g., if there are several | |
6177 | functions with identical names in different source files. | |
c906108c SS |
6178 | @end table |
6179 | ||
2a25a5ba EZ |
6180 | @end table |
6181 | ||
6182 | ||
87885426 | 6183 | @node Edit |
79a6e687 | 6184 | @section Editing Source Files |
87885426 FN |
6185 | @cindex editing source files |
6186 | ||
6187 | @kindex edit | |
6188 | @kindex e @r{(@code{edit})} | |
6189 | To edit the lines in a source file, use the @code{edit} command. | |
6190 | The editing program of your choice | |
6191 | is invoked with the current line set to | |
6192 | the active line in the program. | |
6193 | Alternatively, there are several ways to specify what part of the file you | |
2a25a5ba | 6194 | want to print if you want to see other parts of the program: |
87885426 FN |
6195 | |
6196 | @table @code | |
2a25a5ba EZ |
6197 | @item edit @var{location} |
6198 | Edit the source file specified by @code{location}. Editing starts at | |
6199 | that @var{location}, e.g., at the specified source line of the | |
6200 | specified file. @xref{Specify Location}, for all the possible forms | |
6201 | of the @var{location} argument; here are the forms of the @code{edit} | |
6202 | command most commonly used: | |
87885426 | 6203 | |
2a25a5ba | 6204 | @table @code |
87885426 FN |
6205 | @item edit @var{number} |
6206 | Edit the current source file with @var{number} as the active line number. | |
6207 | ||
6208 | @item edit @var{function} | |
6209 | Edit the file containing @var{function} at the beginning of its definition. | |
2a25a5ba | 6210 | @end table |
87885426 | 6211 | |
87885426 FN |
6212 | @end table |
6213 | ||
79a6e687 | 6214 | @subsection Choosing your Editor |
87885426 FN |
6215 | You can customize @value{GDBN} to use any editor you want |
6216 | @footnote{ | |
6217 | The only restriction is that your editor (say @code{ex}), recognizes the | |
6218 | following command-line syntax: | |
10998722 | 6219 | @smallexample |
87885426 | 6220 | ex +@var{number} file |
10998722 | 6221 | @end smallexample |
15387254 EZ |
6222 | The optional numeric value +@var{number} specifies the number of the line in |
6223 | the file where to start editing.}. | |
6224 | By default, it is @file{@value{EDITOR}}, but you can change this | |
10998722 AC |
6225 | by setting the environment variable @code{EDITOR} before using |
6226 | @value{GDBN}. For example, to configure @value{GDBN} to use the | |
6227 | @code{vi} editor, you could use these commands with the @code{sh} shell: | |
6228 | @smallexample | |
87885426 FN |
6229 | EDITOR=/usr/bin/vi |
6230 | export EDITOR | |
15387254 | 6231 | gdb @dots{} |
10998722 | 6232 | @end smallexample |
87885426 | 6233 | or in the @code{csh} shell, |
10998722 | 6234 | @smallexample |
87885426 | 6235 | setenv EDITOR /usr/bin/vi |
15387254 | 6236 | gdb @dots{} |
10998722 | 6237 | @end smallexample |
87885426 | 6238 | |
6d2ebf8b | 6239 | @node Search |
79a6e687 | 6240 | @section Searching Source Files |
15387254 | 6241 | @cindex searching source files |
c906108c SS |
6242 | |
6243 | There are two commands for searching through the current source file for a | |
6244 | regular expression. | |
6245 | ||
6246 | @table @code | |
6247 | @kindex search | |
6248 | @kindex forward-search | |
6249 | @item forward-search @var{regexp} | |
6250 | @itemx search @var{regexp} | |
6251 | The command @samp{forward-search @var{regexp}} checks each line, | |
6252 | starting with the one following the last line listed, for a match for | |
5d161b24 | 6253 | @var{regexp}. It lists the line that is found. You can use the |
c906108c SS |
6254 | synonym @samp{search @var{regexp}} or abbreviate the command name as |
6255 | @code{fo}. | |
6256 | ||
09d4efe1 | 6257 | @kindex reverse-search |
c906108c SS |
6258 | @item reverse-search @var{regexp} |
6259 | The command @samp{reverse-search @var{regexp}} checks each line, starting | |
6260 | with the one before the last line listed and going backward, for a match | |
6261 | for @var{regexp}. It lists the line that is found. You can abbreviate | |
6262 | this command as @code{rev}. | |
6263 | @end table | |
c906108c | 6264 | |
6d2ebf8b | 6265 | @node Source Path |
79a6e687 | 6266 | @section Specifying Source Directories |
c906108c SS |
6267 | |
6268 | @cindex source path | |
6269 | @cindex directories for source files | |
6270 | Executable programs sometimes do not record the directories of the source | |
6271 | files from which they were compiled, just the names. Even when they do, | |
6272 | the directories could be moved between the compilation and your debugging | |
6273 | session. @value{GDBN} has a list of directories to search for source files; | |
6274 | this is called the @dfn{source path}. Each time @value{GDBN} wants a source file, | |
6275 | it tries all the directories in the list, in the order they are present | |
0b66e38c EZ |
6276 | in the list, until it finds a file with the desired name. |
6277 | ||
6278 | For example, suppose an executable references the file | |
6279 | @file{/usr/src/foo-1.0/lib/foo.c}, and our source path is | |
6280 | @file{/mnt/cross}. The file is first looked up literally; if this | |
6281 | fails, @file{/mnt/cross/usr/src/foo-1.0/lib/foo.c} is tried; if this | |
6282 | fails, @file{/mnt/cross/foo.c} is opened; if this fails, an error | |
6283 | message is printed. @value{GDBN} does not look up the parts of the | |
6284 | source file name, such as @file{/mnt/cross/src/foo-1.0/lib/foo.c}. | |
6285 | Likewise, the subdirectories of the source path are not searched: if | |
6286 | the source path is @file{/mnt/cross}, and the binary refers to | |
6287 | @file{foo.c}, @value{GDBN} would not find it under | |
6288 | @file{/mnt/cross/usr/src/foo-1.0/lib}. | |
6289 | ||
6290 | Plain file names, relative file names with leading directories, file | |
6291 | names containing dots, etc.@: are all treated as described above; for | |
6292 | instance, if the source path is @file{/mnt/cross}, and the source file | |
6293 | is recorded as @file{../lib/foo.c}, @value{GDBN} would first try | |
6294 | @file{../lib/foo.c}, then @file{/mnt/cross/../lib/foo.c}, and after | |
6295 | that---@file{/mnt/cross/foo.c}. | |
6296 | ||
6297 | Note that the executable search path is @emph{not} used to locate the | |
cd852561 | 6298 | source files. |
c906108c SS |
6299 | |
6300 | Whenever you reset or rearrange the source path, @value{GDBN} clears out | |
6301 | any information it has cached about where source files are found and where | |
6302 | each line is in the file. | |
6303 | ||
6304 | @kindex directory | |
6305 | @kindex dir | |
d4f3574e SS |
6306 | When you start @value{GDBN}, its source path includes only @samp{cdir} |
6307 | and @samp{cwd}, in that order. | |
c906108c SS |
6308 | To add other directories, use the @code{directory} command. |
6309 | ||
4b505b12 AS |
6310 | The search path is used to find both program source files and @value{GDBN} |
6311 | script files (read using the @samp{-command} option and @samp{source} command). | |
6312 | ||
30daae6c JB |
6313 | In addition to the source path, @value{GDBN} provides a set of commands |
6314 | that manage a list of source path substitution rules. A @dfn{substitution | |
6315 | rule} specifies how to rewrite source directories stored in the program's | |
6316 | debug information in case the sources were moved to a different | |
6317 | directory between compilation and debugging. A rule is made of | |
6318 | two strings, the first specifying what needs to be rewritten in | |
6319 | the path, and the second specifying how it should be rewritten. | |
6320 | In @ref{set substitute-path}, we name these two parts @var{from} and | |
6321 | @var{to} respectively. @value{GDBN} does a simple string replacement | |
6322 | of @var{from} with @var{to} at the start of the directory part of the | |
6323 | source file name, and uses that result instead of the original file | |
6324 | name to look up the sources. | |
6325 | ||
6326 | Using the previous example, suppose the @file{foo-1.0} tree has been | |
6327 | moved from @file{/usr/src} to @file{/mnt/cross}, then you can tell | |
3f94c067 | 6328 | @value{GDBN} to replace @file{/usr/src} in all source path names with |
30daae6c JB |
6329 | @file{/mnt/cross}. The first lookup will then be |
6330 | @file{/mnt/cross/foo-1.0/lib/foo.c} in place of the original location | |
6331 | of @file{/usr/src/foo-1.0/lib/foo.c}. To define a source path | |
6332 | substitution rule, use the @code{set substitute-path} command | |
6333 | (@pxref{set substitute-path}). | |
6334 | ||
6335 | To avoid unexpected substitution results, a rule is applied only if the | |
6336 | @var{from} part of the directory name ends at a directory separator. | |
6337 | For instance, a rule substituting @file{/usr/source} into | |
6338 | @file{/mnt/cross} will be applied to @file{/usr/source/foo-1.0} but | |
6339 | not to @file{/usr/sourceware/foo-2.0}. And because the substitution | |
d3e8051b | 6340 | is applied only at the beginning of the directory name, this rule will |
30daae6c JB |
6341 | not be applied to @file{/root/usr/source/baz.c} either. |
6342 | ||
6343 | In many cases, you can achieve the same result using the @code{directory} | |
6344 | command. However, @code{set substitute-path} can be more efficient in | |
6345 | the case where the sources are organized in a complex tree with multiple | |
6346 | subdirectories. With the @code{directory} command, you need to add each | |
6347 | subdirectory of your project. If you moved the entire tree while | |
6348 | preserving its internal organization, then @code{set substitute-path} | |
6349 | allows you to direct the debugger to all the sources with one single | |
6350 | command. | |
6351 | ||
6352 | @code{set substitute-path} is also more than just a shortcut command. | |
6353 | The source path is only used if the file at the original location no | |
6354 | longer exists. On the other hand, @code{set substitute-path} modifies | |
6355 | the debugger behavior to look at the rewritten location instead. So, if | |
6356 | for any reason a source file that is not relevant to your executable is | |
6357 | located at the original location, a substitution rule is the only | |
3f94c067 | 6358 | method available to point @value{GDBN} at the new location. |
30daae6c | 6359 | |
29b0e8a2 JM |
6360 | @cindex @samp{--with-relocated-sources} |
6361 | @cindex default source path substitution | |
6362 | You can configure a default source path substitution rule by | |
6363 | configuring @value{GDBN} with the | |
6364 | @samp{--with-relocated-sources=@var{dir}} option. The @var{dir} | |
6365 | should be the name of a directory under @value{GDBN}'s configured | |
6366 | prefix (set with @samp{--prefix} or @samp{--exec-prefix}), and | |
6367 | directory names in debug information under @var{dir} will be adjusted | |
6368 | automatically if the installed @value{GDBN} is moved to a new | |
6369 | location. This is useful if @value{GDBN}, libraries or executables | |
6370 | with debug information and corresponding source code are being moved | |
6371 | together. | |
6372 | ||
c906108c SS |
6373 | @table @code |
6374 | @item directory @var{dirname} @dots{} | |
6375 | @item dir @var{dirname} @dots{} | |
6376 | Add directory @var{dirname} to the front of the source path. Several | |
d4f3574e SS |
6377 | directory names may be given to this command, separated by @samp{:} |
6378 | (@samp{;} on MS-DOS and MS-Windows, where @samp{:} usually appears as | |
6379 | part of absolute file names) or | |
c906108c SS |
6380 | whitespace. You may specify a directory that is already in the source |
6381 | path; this moves it forward, so @value{GDBN} searches it sooner. | |
6382 | ||
6383 | @kindex cdir | |
6384 | @kindex cwd | |
41afff9a | 6385 | @vindex $cdir@r{, convenience variable} |
d3e8051b | 6386 | @vindex $cwd@r{, convenience variable} |
c906108c SS |
6387 | @cindex compilation directory |
6388 | @cindex current directory | |
6389 | @cindex working directory | |
6390 | @cindex directory, current | |
6391 | @cindex directory, compilation | |
6392 | You can use the string @samp{$cdir} to refer to the compilation | |
6393 | directory (if one is recorded), and @samp{$cwd} to refer to the current | |
6394 | working directory. @samp{$cwd} is not the same as @samp{.}---the former | |
6395 | tracks the current working directory as it changes during your @value{GDBN} | |
6396 | session, while the latter is immediately expanded to the current | |
6397 | directory at the time you add an entry to the source path. | |
6398 | ||
6399 | @item directory | |
cd852561 | 6400 | Reset the source path to its default value (@samp{$cdir:$cwd} on Unix systems). This requires confirmation. |
c906108c SS |
6401 | |
6402 | @c RET-repeat for @code{directory} is explicitly disabled, but since | |
6403 | @c repeating it would be a no-op we do not say that. (thanks to RMS) | |
6404 | ||
6405 | @item show directories | |
6406 | @kindex show directories | |
6407 | Print the source path: show which directories it contains. | |
30daae6c JB |
6408 | |
6409 | @anchor{set substitute-path} | |
6410 | @item set substitute-path @var{from} @var{to} | |
6411 | @kindex set substitute-path | |
6412 | Define a source path substitution rule, and add it at the end of the | |
6413 | current list of existing substitution rules. If a rule with the same | |
6414 | @var{from} was already defined, then the old rule is also deleted. | |
6415 | ||
6416 | For example, if the file @file{/foo/bar/baz.c} was moved to | |
6417 | @file{/mnt/cross/baz.c}, then the command | |
6418 | ||
6419 | @smallexample | |
6420 | (@value{GDBP}) set substitute-path /usr/src /mnt/cross | |
6421 | @end smallexample | |
6422 | ||
6423 | @noindent | |
6424 | will tell @value{GDBN} to replace @samp{/usr/src} with | |
6425 | @samp{/mnt/cross}, which will allow @value{GDBN} to find the file | |
6426 | @file{baz.c} even though it was moved. | |
6427 | ||
6428 | In the case when more than one substitution rule have been defined, | |
6429 | the rules are evaluated one by one in the order where they have been | |
6430 | defined. The first one matching, if any, is selected to perform | |
6431 | the substitution. | |
6432 | ||
6433 | For instance, if we had entered the following commands: | |
6434 | ||
6435 | @smallexample | |
6436 | (@value{GDBP}) set substitute-path /usr/src/include /mnt/include | |
6437 | (@value{GDBP}) set substitute-path /usr/src /mnt/src | |
6438 | @end smallexample | |
6439 | ||
6440 | @noindent | |
6441 | @value{GDBN} would then rewrite @file{/usr/src/include/defs.h} into | |
6442 | @file{/mnt/include/defs.h} by using the first rule. However, it would | |
6443 | use the second rule to rewrite @file{/usr/src/lib/foo.c} into | |
6444 | @file{/mnt/src/lib/foo.c}. | |
6445 | ||
6446 | ||
6447 | @item unset substitute-path [path] | |
6448 | @kindex unset substitute-path | |
6449 | If a path is specified, search the current list of substitution rules | |
6450 | for a rule that would rewrite that path. Delete that rule if found. | |
6451 | A warning is emitted by the debugger if no rule could be found. | |
6452 | ||
6453 | If no path is specified, then all substitution rules are deleted. | |
6454 | ||
6455 | @item show substitute-path [path] | |
6456 | @kindex show substitute-path | |
6457 | If a path is specified, then print the source path substitution rule | |
6458 | which would rewrite that path, if any. | |
6459 | ||
6460 | If no path is specified, then print all existing source path substitution | |
6461 | rules. | |
6462 | ||
c906108c SS |
6463 | @end table |
6464 | ||
6465 | If your source path is cluttered with directories that are no longer of | |
6466 | interest, @value{GDBN} may sometimes cause confusion by finding the wrong | |
6467 | versions of source. You can correct the situation as follows: | |
6468 | ||
6469 | @enumerate | |
6470 | @item | |
cd852561 | 6471 | Use @code{directory} with no argument to reset the source path to its default value. |
c906108c SS |
6472 | |
6473 | @item | |
6474 | Use @code{directory} with suitable arguments to reinstall the | |
6475 | directories you want in the source path. You can add all the | |
6476 | directories in one command. | |
6477 | @end enumerate | |
6478 | ||
6d2ebf8b | 6479 | @node Machine Code |
79a6e687 | 6480 | @section Source and Machine Code |
15387254 | 6481 | @cindex source line and its code address |
c906108c SS |
6482 | |
6483 | You can use the command @code{info line} to map source lines to program | |
6484 | addresses (and vice versa), and the command @code{disassemble} to display | |
91440f57 HZ |
6485 | a range of addresses as machine instructions. You can use the command |
6486 | @code{set disassemble-next-line} to set whether to disassemble next | |
6487 | source line when execution stops. When run under @sc{gnu} Emacs | |
d4f3574e | 6488 | mode, the @code{info line} command causes the arrow to point to the |
5d161b24 | 6489 | line specified. Also, @code{info line} prints addresses in symbolic form as |
c906108c SS |
6490 | well as hex. |
6491 | ||
6492 | @table @code | |
6493 | @kindex info line | |
6494 | @item info line @var{linespec} | |
6495 | Print the starting and ending addresses of the compiled code for | |
6496 | source line @var{linespec}. You can specify source lines in any of | |
2a25a5ba | 6497 | the ways documented in @ref{Specify Location}. |
c906108c SS |
6498 | @end table |
6499 | ||
6500 | For example, we can use @code{info line} to discover the location of | |
6501 | the object code for the first line of function | |
6502 | @code{m4_changequote}: | |
6503 | ||
d4f3574e SS |
6504 | @c FIXME: I think this example should also show the addresses in |
6505 | @c symbolic form, as they usually would be displayed. | |
c906108c | 6506 | @smallexample |
96a2c332 | 6507 | (@value{GDBP}) info line m4_changequote |
c906108c SS |
6508 | Line 895 of "builtin.c" starts at pc 0x634c and ends at 0x6350. |
6509 | @end smallexample | |
6510 | ||
6511 | @noindent | |
15387254 | 6512 | @cindex code address and its source line |
c906108c SS |
6513 | We can also inquire (using @code{*@var{addr}} as the form for |
6514 | @var{linespec}) what source line covers a particular address: | |
6515 | @smallexample | |
6516 | (@value{GDBP}) info line *0x63ff | |
6517 | Line 926 of "builtin.c" starts at pc 0x63e4 and ends at 0x6404. | |
6518 | @end smallexample | |
6519 | ||
6520 | @cindex @code{$_} and @code{info line} | |
15387254 | 6521 | @cindex @code{x} command, default address |
41afff9a | 6522 | @kindex x@r{(examine), and} info line |
c906108c SS |
6523 | After @code{info line}, the default address for the @code{x} command |
6524 | is changed to the starting address of the line, so that @samp{x/i} is | |
6525 | sufficient to begin examining the machine code (@pxref{Memory, | |
79a6e687 | 6526 | ,Examining Memory}). Also, this address is saved as the value of the |
c906108c | 6527 | convenience variable @code{$_} (@pxref{Convenience Vars, ,Convenience |
79a6e687 | 6528 | Variables}). |
c906108c SS |
6529 | |
6530 | @table @code | |
6531 | @kindex disassemble | |
6532 | @cindex assembly instructions | |
6533 | @cindex instructions, assembly | |
6534 | @cindex machine instructions | |
6535 | @cindex listing machine instructions | |
6536 | @item disassemble | |
d14508fe | 6537 | @itemx disassemble /m |
9b117ef3 | 6538 | @itemx disassemble /r |
c906108c | 6539 | This specialized command dumps a range of memory as machine |
d14508fe | 6540 | instructions. It can also print mixed source+disassembly by specifying |
9b117ef3 HZ |
6541 | the @code{/m} modifier and print the raw instructions in hex as well as |
6542 | in symbolic form by specifying the @code{/r}. | |
d14508fe | 6543 | The default memory range is the function surrounding the |
c906108c SS |
6544 | program counter of the selected frame. A single argument to this |
6545 | command is a program counter value; @value{GDBN} dumps the function | |
21a0512e PP |
6546 | surrounding this value. When two arguments are given, they should |
6547 | be separated by a comma, possibly surrounded by whitespace. The | |
6548 | arguments specify a range of addresses (first inclusive, second exclusive) | |
6549 | to dump. In that case, the name of the function is also printed (since | |
6550 | there could be several functions in the given range). | |
6551 | ||
6552 | The argument(s) can be any expression yielding a numeric value, such as | |
6553 | @samp{0x32c4}, @samp{&main+10} or @samp{$pc - 8}. | |
2b28d209 PP |
6554 | |
6555 | If the range of memory being disassembled contains current program counter, | |
6556 | the instruction at that location is shown with a @code{=>} marker. | |
c906108c SS |
6557 | @end table |
6558 | ||
c906108c SS |
6559 | The following example shows the disassembly of a range of addresses of |
6560 | HP PA-RISC 2.0 code: | |
6561 | ||
6562 | @smallexample | |
21a0512e | 6563 | (@value{GDBP}) disas 0x32c4, 0x32e4 |
c906108c | 6564 | Dump of assembler code from 0x32c4 to 0x32e4: |
2b28d209 PP |
6565 | 0x32c4 <main+204>: addil 0,dp |
6566 | 0x32c8 <main+208>: ldw 0x22c(sr0,r1),r26 | |
6567 | 0x32cc <main+212>: ldil 0x3000,r31 | |
6568 | 0x32d0 <main+216>: ble 0x3f8(sr4,r31) | |
6569 | 0x32d4 <main+220>: ldo 0(r31),rp | |
6570 | 0x32d8 <main+224>: addil -0x800,dp | |
6571 | 0x32dc <main+228>: ldo 0x588(r1),r26 | |
6572 | 0x32e0 <main+232>: ldil 0x3000,r31 | |
c906108c SS |
6573 | End of assembler dump. |
6574 | @end smallexample | |
c906108c | 6575 | |
2b28d209 PP |
6576 | Here is an example showing mixed source+assembly for Intel x86, when the |
6577 | program is stopped just after function prologue: | |
d14508fe DE |
6578 | |
6579 | @smallexample | |
6580 | (@value{GDBP}) disas /m main | |
6581 | Dump of assembler code for function main: | |
6582 | 5 @{ | |
9c419145 PP |
6583 | 0x08048330 <+0>: push %ebp |
6584 | 0x08048331 <+1>: mov %esp,%ebp | |
6585 | 0x08048333 <+3>: sub $0x8,%esp | |
6586 | 0x08048336 <+6>: and $0xfffffff0,%esp | |
6587 | 0x08048339 <+9>: sub $0x10,%esp | |
d14508fe DE |
6588 | |
6589 | 6 printf ("Hello.\n"); | |
9c419145 PP |
6590 | => 0x0804833c <+12>: movl $0x8048440,(%esp) |
6591 | 0x08048343 <+19>: call 0x8048284 <puts@@plt> | |
d14508fe DE |
6592 | |
6593 | 7 return 0; | |
6594 | 8 @} | |
9c419145 PP |
6595 | 0x08048348 <+24>: mov $0x0,%eax |
6596 | 0x0804834d <+29>: leave | |
6597 | 0x0804834e <+30>: ret | |
d14508fe DE |
6598 | |
6599 | End of assembler dump. | |
6600 | @end smallexample | |
6601 | ||
c906108c SS |
6602 | Some architectures have more than one commonly-used set of instruction |
6603 | mnemonics or other syntax. | |
6604 | ||
76d17f34 EZ |
6605 | For programs that were dynamically linked and use shared libraries, |
6606 | instructions that call functions or branch to locations in the shared | |
6607 | libraries might show a seemingly bogus location---it's actually a | |
6608 | location of the relocation table. On some architectures, @value{GDBN} | |
6609 | might be able to resolve these to actual function names. | |
6610 | ||
c906108c | 6611 | @table @code |
d4f3574e | 6612 | @kindex set disassembly-flavor |
d4f3574e SS |
6613 | @cindex Intel disassembly flavor |
6614 | @cindex AT&T disassembly flavor | |
6615 | @item set disassembly-flavor @var{instruction-set} | |
c906108c SS |
6616 | Select the instruction set to use when disassembling the |
6617 | program via the @code{disassemble} or @code{x/i} commands. | |
6618 | ||
6619 | Currently this command is only defined for the Intel x86 family. You | |
d4f3574e SS |
6620 | can set @var{instruction-set} to either @code{intel} or @code{att}. |
6621 | The default is @code{att}, the AT&T flavor used by default by Unix | |
6622 | assemblers for x86-based targets. | |
9c16f35a EZ |
6623 | |
6624 | @kindex show disassembly-flavor | |
6625 | @item show disassembly-flavor | |
6626 | Show the current setting of the disassembly flavor. | |
c906108c SS |
6627 | @end table |
6628 | ||
91440f57 HZ |
6629 | @table @code |
6630 | @kindex set disassemble-next-line | |
6631 | @kindex show disassemble-next-line | |
6632 | @item set disassemble-next-line | |
6633 | @itemx show disassemble-next-line | |
32ae1842 EZ |
6634 | Control whether or not @value{GDBN} will disassemble the next source |
6635 | line or instruction when execution stops. If ON, @value{GDBN} will | |
6636 | display disassembly of the next source line when execution of the | |
6637 | program being debugged stops. This is @emph{in addition} to | |
6638 | displaying the source line itself, which @value{GDBN} always does if | |
6639 | possible. If the next source line cannot be displayed for some reason | |
6640 | (e.g., if @value{GDBN} cannot find the source file, or there's no line | |
6641 | info in the debug info), @value{GDBN} will display disassembly of the | |
6642 | next @emph{instruction} instead of showing the next source line. If | |
6643 | AUTO, @value{GDBN} will display disassembly of next instruction only | |
6644 | if the source line cannot be displayed. This setting causes | |
6645 | @value{GDBN} to display some feedback when you step through a function | |
6646 | with no line info or whose source file is unavailable. The default is | |
6647 | OFF, which means never display the disassembly of the next line or | |
6648 | instruction. | |
91440f57 HZ |
6649 | @end table |
6650 | ||
c906108c | 6651 | |
6d2ebf8b | 6652 | @node Data |
c906108c SS |
6653 | @chapter Examining Data |
6654 | ||
6655 | @cindex printing data | |
6656 | @cindex examining data | |
6657 | @kindex print | |
6658 | @kindex inspect | |
6659 | @c "inspect" is not quite a synonym if you are using Epoch, which we do not | |
6660 | @c document because it is nonstandard... Under Epoch it displays in a | |
6661 | @c different window or something like that. | |
6662 | The usual way to examine data in your program is with the @code{print} | |
7a292a7a SS |
6663 | command (abbreviated @code{p}), or its synonym @code{inspect}. It |
6664 | evaluates and prints the value of an expression of the language your | |
6665 | program is written in (@pxref{Languages, ,Using @value{GDBN} with | |
78e2826b TT |
6666 | Different Languages}). It may also print the expression using a |
6667 | Python-based pretty-printer (@pxref{Pretty Printing}). | |
c906108c SS |
6668 | |
6669 | @table @code | |
d4f3574e SS |
6670 | @item print @var{expr} |
6671 | @itemx print /@var{f} @var{expr} | |
6672 | @var{expr} is an expression (in the source language). By default the | |
6673 | value of @var{expr} is printed in a format appropriate to its data type; | |
c906108c | 6674 | you can choose a different format by specifying @samp{/@var{f}}, where |
d4f3574e | 6675 | @var{f} is a letter specifying the format; see @ref{Output Formats,,Output |
79a6e687 | 6676 | Formats}. |
c906108c SS |
6677 | |
6678 | @item print | |
6679 | @itemx print /@var{f} | |
15387254 | 6680 | @cindex reprint the last value |
d4f3574e | 6681 | If you omit @var{expr}, @value{GDBN} displays the last value again (from the |
79a6e687 | 6682 | @dfn{value history}; @pxref{Value History, ,Value History}). This allows you to |
c906108c SS |
6683 | conveniently inspect the same value in an alternative format. |
6684 | @end table | |
6685 | ||
6686 | A more low-level way of examining data is with the @code{x} command. | |
6687 | It examines data in memory at a specified address and prints it in a | |
79a6e687 | 6688 | specified format. @xref{Memory, ,Examining Memory}. |
c906108c | 6689 | |
7a292a7a | 6690 | If you are interested in information about types, or about how the |
d4f3574e SS |
6691 | fields of a struct or a class are declared, use the @code{ptype @var{exp}} |
6692 | command rather than @code{print}. @xref{Symbols, ,Examining the Symbol | |
7a292a7a | 6693 | Table}. |
c906108c SS |
6694 | |
6695 | @menu | |
6696 | * Expressions:: Expressions | |
6ba66d6a | 6697 | * Ambiguous Expressions:: Ambiguous Expressions |
c906108c SS |
6698 | * Variables:: Program variables |
6699 | * Arrays:: Artificial arrays | |
6700 | * Output Formats:: Output formats | |
6701 | * Memory:: Examining memory | |
6702 | * Auto Display:: Automatic display | |
6703 | * Print Settings:: Print settings | |
6704 | * Value History:: Value history | |
6705 | * Convenience Vars:: Convenience variables | |
6706 | * Registers:: Registers | |
c906108c | 6707 | * Floating Point Hardware:: Floating point hardware |
53c69bd7 | 6708 | * Vector Unit:: Vector Unit |
721c2651 | 6709 | * OS Information:: Auxiliary data provided by operating system |
29e57380 | 6710 | * Memory Region Attributes:: Memory region attributes |
16d9dec6 | 6711 | * Dump/Restore Files:: Copy between memory and a file |
384ee23f | 6712 | * Core File Generation:: Cause a program dump its core |
a0eb71c5 KB |
6713 | * Character Sets:: Debugging programs that use a different |
6714 | character set than GDB does | |
09d4efe1 | 6715 | * Caching Remote Data:: Data caching for remote targets |
08388c79 | 6716 | * Searching Memory:: Searching memory for a sequence of bytes |
c906108c SS |
6717 | @end menu |
6718 | ||
6d2ebf8b | 6719 | @node Expressions |
c906108c SS |
6720 | @section Expressions |
6721 | ||
6722 | @cindex expressions | |
6723 | @code{print} and many other @value{GDBN} commands accept an expression and | |
6724 | compute its value. Any kind of constant, variable or operator defined | |
6725 | by the programming language you are using is valid in an expression in | |
e2e0bcd1 JB |
6726 | @value{GDBN}. This includes conditional expressions, function calls, |
6727 | casts, and string constants. It also includes preprocessor macros, if | |
6728 | you compiled your program to include this information; see | |
6729 | @ref{Compilation}. | |
c906108c | 6730 | |
15387254 | 6731 | @cindex arrays in expressions |
d4f3574e SS |
6732 | @value{GDBN} supports array constants in expressions input by |
6733 | the user. The syntax is @{@var{element}, @var{element}@dots{}@}. For example, | |
63092375 DJ |
6734 | you can use the command @code{print @{1, 2, 3@}} to create an array |
6735 | of three integers. If you pass an array to a function or assign it | |
6736 | to a program variable, @value{GDBN} copies the array to memory that | |
6737 | is @code{malloc}ed in the target program. | |
c906108c | 6738 | |
c906108c SS |
6739 | Because C is so widespread, most of the expressions shown in examples in |
6740 | this manual are in C. @xref{Languages, , Using @value{GDBN} with Different | |
6741 | Languages}, for information on how to use expressions in other | |
6742 | languages. | |
6743 | ||
6744 | In this section, we discuss operators that you can use in @value{GDBN} | |
6745 | expressions regardless of your programming language. | |
6746 | ||
15387254 | 6747 | @cindex casts, in expressions |
c906108c SS |
6748 | Casts are supported in all languages, not just in C, because it is so |
6749 | useful to cast a number into a pointer in order to examine a structure | |
6750 | at that address in memory. | |
6751 | @c FIXME: casts supported---Mod2 true? | |
c906108c SS |
6752 | |
6753 | @value{GDBN} supports these operators, in addition to those common | |
6754 | to programming languages: | |
6755 | ||
6756 | @table @code | |
6757 | @item @@ | |
6758 | @samp{@@} is a binary operator for treating parts of memory as arrays. | |
79a6e687 | 6759 | @xref{Arrays, ,Artificial Arrays}, for more information. |
c906108c SS |
6760 | |
6761 | @item :: | |
6762 | @samp{::} allows you to specify a variable in terms of the file or | |
79a6e687 | 6763 | function where it is defined. @xref{Variables, ,Program Variables}. |
c906108c SS |
6764 | |
6765 | @cindex @{@var{type}@} | |
6766 | @cindex type casting memory | |
6767 | @cindex memory, viewing as typed object | |
6768 | @cindex casts, to view memory | |
6769 | @item @{@var{type}@} @var{addr} | |
6770 | Refers to an object of type @var{type} stored at address @var{addr} in | |
6771 | memory. @var{addr} may be any expression whose value is an integer or | |
6772 | pointer (but parentheses are required around binary operators, just as in | |
6773 | a cast). This construct is allowed regardless of what kind of data is | |
6774 | normally supposed to reside at @var{addr}. | |
6775 | @end table | |
6776 | ||
6ba66d6a JB |
6777 | @node Ambiguous Expressions |
6778 | @section Ambiguous Expressions | |
6779 | @cindex ambiguous expressions | |
6780 | ||
6781 | Expressions can sometimes contain some ambiguous elements. For instance, | |
6782 | some programming languages (notably Ada, C@t{++} and Objective-C) permit | |
6783 | a single function name to be defined several times, for application in | |
6784 | different contexts. This is called @dfn{overloading}. Another example | |
6785 | involving Ada is generics. A @dfn{generic package} is similar to C@t{++} | |
6786 | templates and is typically instantiated several times, resulting in | |
6787 | the same function name being defined in different contexts. | |
6788 | ||
6789 | In some cases and depending on the language, it is possible to adjust | |
6790 | the expression to remove the ambiguity. For instance in C@t{++}, you | |
6791 | can specify the signature of the function you want to break on, as in | |
6792 | @kbd{break @var{function}(@var{types})}. In Ada, using the fully | |
6793 | qualified name of your function often makes the expression unambiguous | |
6794 | as well. | |
6795 | ||
6796 | When an ambiguity that needs to be resolved is detected, the debugger | |
6797 | has the capability to display a menu of numbered choices for each | |
6798 | possibility, and then waits for the selection with the prompt @samp{>}. | |
6799 | The first option is always @samp{[0] cancel}, and typing @kbd{0 @key{RET}} | |
6800 | aborts the current command. If the command in which the expression was | |
6801 | used allows more than one choice to be selected, the next option in the | |
6802 | menu is @samp{[1] all}, and typing @kbd{1 @key{RET}} selects all possible | |
6803 | choices. | |
6804 | ||
6805 | For example, the following session excerpt shows an attempt to set a | |
6806 | breakpoint at the overloaded symbol @code{String::after}. | |
6807 | We choose three particular definitions of that function name: | |
6808 | ||
6809 | @c FIXME! This is likely to change to show arg type lists, at least | |
6810 | @smallexample | |
6811 | @group | |
6812 | (@value{GDBP}) b String::after | |
6813 | [0] cancel | |
6814 | [1] all | |
6815 | [2] file:String.cc; line number:867 | |
6816 | [3] file:String.cc; line number:860 | |
6817 | [4] file:String.cc; line number:875 | |
6818 | [5] file:String.cc; line number:853 | |
6819 | [6] file:String.cc; line number:846 | |
6820 | [7] file:String.cc; line number:735 | |
6821 | > 2 4 6 | |
6822 | Breakpoint 1 at 0xb26c: file String.cc, line 867. | |
6823 | Breakpoint 2 at 0xb344: file String.cc, line 875. | |
6824 | Breakpoint 3 at 0xafcc: file String.cc, line 846. | |
6825 | Multiple breakpoints were set. | |
6826 | Use the "delete" command to delete unwanted | |
6827 | breakpoints. | |
6828 | (@value{GDBP}) | |
6829 | @end group | |
6830 | @end smallexample | |
6831 | ||
6832 | @table @code | |
6833 | @kindex set multiple-symbols | |
6834 | @item set multiple-symbols @var{mode} | |
6835 | @cindex multiple-symbols menu | |
6836 | ||
6837 | This option allows you to adjust the debugger behavior when an expression | |
6838 | is ambiguous. | |
6839 | ||
6840 | By default, @var{mode} is set to @code{all}. If the command with which | |
6841 | the expression is used allows more than one choice, then @value{GDBN} | |
6842 | automatically selects all possible choices. For instance, inserting | |
6843 | a breakpoint on a function using an ambiguous name results in a breakpoint | |
6844 | inserted on each possible match. However, if a unique choice must be made, | |
6845 | then @value{GDBN} uses the menu to help you disambiguate the expression. | |
6846 | For instance, printing the address of an overloaded function will result | |
6847 | in the use of the menu. | |
6848 | ||
6849 | When @var{mode} is set to @code{ask}, the debugger always uses the menu | |
6850 | when an ambiguity is detected. | |
6851 | ||
6852 | Finally, when @var{mode} is set to @code{cancel}, the debugger reports | |
6853 | an error due to the ambiguity and the command is aborted. | |
6854 | ||
6855 | @kindex show multiple-symbols | |
6856 | @item show multiple-symbols | |
6857 | Show the current value of the @code{multiple-symbols} setting. | |
6858 | @end table | |
6859 | ||
6d2ebf8b | 6860 | @node Variables |
79a6e687 | 6861 | @section Program Variables |
c906108c SS |
6862 | |
6863 | The most common kind of expression to use is the name of a variable | |
6864 | in your program. | |
6865 | ||
6866 | Variables in expressions are understood in the selected stack frame | |
79a6e687 | 6867 | (@pxref{Selection, ,Selecting a Frame}); they must be either: |
c906108c SS |
6868 | |
6869 | @itemize @bullet | |
6870 | @item | |
6871 | global (or file-static) | |
6872 | @end itemize | |
6873 | ||
5d161b24 | 6874 | @noindent or |
c906108c SS |
6875 | |
6876 | @itemize @bullet | |
6877 | @item | |
6878 | visible according to the scope rules of the | |
6879 | programming language from the point of execution in that frame | |
5d161b24 | 6880 | @end itemize |
c906108c SS |
6881 | |
6882 | @noindent This means that in the function | |
6883 | ||
474c8240 | 6884 | @smallexample |
c906108c SS |
6885 | foo (a) |
6886 | int a; | |
6887 | @{ | |
6888 | bar (a); | |
6889 | @{ | |
6890 | int b = test (); | |
6891 | bar (b); | |
6892 | @} | |
6893 | @} | |
474c8240 | 6894 | @end smallexample |
c906108c SS |
6895 | |
6896 | @noindent | |
6897 | you can examine and use the variable @code{a} whenever your program is | |
6898 | executing within the function @code{foo}, but you can only use or | |
6899 | examine the variable @code{b} while your program is executing inside | |
6900 | the block where @code{b} is declared. | |
6901 | ||
6902 | @cindex variable name conflict | |
6903 | There is an exception: you can refer to a variable or function whose | |
6904 | scope is a single source file even if the current execution point is not | |
6905 | in this file. But it is possible to have more than one such variable or | |
6906 | function with the same name (in different source files). If that | |
6907 | happens, referring to that name has unpredictable effects. If you wish, | |
6908 | you can specify a static variable in a particular function or file, | |
15387254 | 6909 | using the colon-colon (@code{::}) notation: |
c906108c | 6910 | |
d4f3574e | 6911 | @cindex colon-colon, context for variables/functions |
12c27660 | 6912 | @ifnotinfo |
c906108c | 6913 | @c info cannot cope with a :: index entry, but why deprive hard copy readers? |
41afff9a | 6914 | @cindex @code{::}, context for variables/functions |
12c27660 | 6915 | @end ifnotinfo |
474c8240 | 6916 | @smallexample |
c906108c SS |
6917 | @var{file}::@var{variable} |
6918 | @var{function}::@var{variable} | |
474c8240 | 6919 | @end smallexample |
c906108c SS |
6920 | |
6921 | @noindent | |
6922 | Here @var{file} or @var{function} is the name of the context for the | |
6923 | static @var{variable}. In the case of file names, you can use quotes to | |
6924 | make sure @value{GDBN} parses the file name as a single word---for example, | |
6925 | to print a global value of @code{x} defined in @file{f2.c}: | |
6926 | ||
474c8240 | 6927 | @smallexample |
c906108c | 6928 | (@value{GDBP}) p 'f2.c'::x |
474c8240 | 6929 | @end smallexample |
c906108c | 6930 | |
b37052ae | 6931 | @cindex C@t{++} scope resolution |
c906108c | 6932 | This use of @samp{::} is very rarely in conflict with the very similar |
b37052ae | 6933 | use of the same notation in C@t{++}. @value{GDBN} also supports use of the C@t{++} |
c906108c SS |
6934 | scope resolution operator in @value{GDBN} expressions. |
6935 | @c FIXME: Um, so what happens in one of those rare cases where it's in | |
6936 | @c conflict?? --mew | |
c906108c SS |
6937 | |
6938 | @cindex wrong values | |
6939 | @cindex variable values, wrong | |
15387254 EZ |
6940 | @cindex function entry/exit, wrong values of variables |
6941 | @cindex optimized code, wrong values of variables | |
c906108c SS |
6942 | @quotation |
6943 | @emph{Warning:} Occasionally, a local variable may appear to have the | |
6944 | wrong value at certain points in a function---just after entry to a new | |
6945 | scope, and just before exit. | |
6946 | @end quotation | |
6947 | You may see this problem when you are stepping by machine instructions. | |
6948 | This is because, on most machines, it takes more than one instruction to | |
6949 | set up a stack frame (including local variable definitions); if you are | |
6950 | stepping by machine instructions, variables may appear to have the wrong | |
6951 | values until the stack frame is completely built. On exit, it usually | |
6952 | also takes more than one machine instruction to destroy a stack frame; | |
6953 | after you begin stepping through that group of instructions, local | |
6954 | variable definitions may be gone. | |
6955 | ||
6956 | This may also happen when the compiler does significant optimizations. | |
6957 | To be sure of always seeing accurate values, turn off all optimization | |
6958 | when compiling. | |
6959 | ||
d4f3574e SS |
6960 | @cindex ``No symbol "foo" in current context'' |
6961 | Another possible effect of compiler optimizations is to optimize | |
6962 | unused variables out of existence, or assign variables to registers (as | |
6963 | opposed to memory addresses). Depending on the support for such cases | |
6964 | offered by the debug info format used by the compiler, @value{GDBN} | |
6965 | might not be able to display values for such local variables. If that | |
6966 | happens, @value{GDBN} will print a message like this: | |
6967 | ||
474c8240 | 6968 | @smallexample |
d4f3574e | 6969 | No symbol "foo" in current context. |
474c8240 | 6970 | @end smallexample |
d4f3574e SS |
6971 | |
6972 | To solve such problems, either recompile without optimizations, or use a | |
6973 | different debug info format, if the compiler supports several such | |
15387254 | 6974 | formats. For example, @value{NGCC}, the @sc{gnu} C/C@t{++} compiler, |
0179ffac DC |
6975 | usually supports the @option{-gstabs+} option. @option{-gstabs+} |
6976 | produces debug info in a format that is superior to formats such as | |
6977 | COFF. You may be able to use DWARF 2 (@option{-gdwarf-2}), which is also | |
6978 | an effective form for debug info. @xref{Debugging Options,,Options | |
ce9341a1 BW |
6979 | for Debugging Your Program or GCC, gcc.info, Using the @sc{gnu} |
6980 | Compiler Collection (GCC)}. | |
79a6e687 | 6981 | @xref{C, ,C and C@t{++}}, for more information about debug info formats |
15387254 | 6982 | that are best suited to C@t{++} programs. |
d4f3574e | 6983 | |
ab1adacd EZ |
6984 | If you ask to print an object whose contents are unknown to |
6985 | @value{GDBN}, e.g., because its data type is not completely specified | |
6986 | by the debug information, @value{GDBN} will say @samp{<incomplete | |
6987 | type>}. @xref{Symbols, incomplete type}, for more about this. | |
6988 | ||
3a60f64e JK |
6989 | Strings are identified as arrays of @code{char} values without specified |
6990 | signedness. Arrays of either @code{signed char} or @code{unsigned char} get | |
6991 | printed as arrays of 1 byte sized integers. @code{-fsigned-char} or | |
6992 | @code{-funsigned-char} @value{NGCC} options have no effect as @value{GDBN} | |
6993 | defines literal string type @code{"char"} as @code{char} without a sign. | |
6994 | For program code | |
6995 | ||
6996 | @smallexample | |
6997 | char var0[] = "A"; | |
6998 | signed char var1[] = "A"; | |
6999 | @end smallexample | |
7000 | ||
7001 | You get during debugging | |
7002 | @smallexample | |
7003 | (gdb) print var0 | |
7004 | $1 = "A" | |
7005 | (gdb) print var1 | |
7006 | $2 = @{65 'A', 0 '\0'@} | |
7007 | @end smallexample | |
7008 | ||
6d2ebf8b | 7009 | @node Arrays |
79a6e687 | 7010 | @section Artificial Arrays |
c906108c SS |
7011 | |
7012 | @cindex artificial array | |
15387254 | 7013 | @cindex arrays |
41afff9a | 7014 | @kindex @@@r{, referencing memory as an array} |
c906108c SS |
7015 | It is often useful to print out several successive objects of the |
7016 | same type in memory; a section of an array, or an array of | |
7017 | dynamically determined size for which only a pointer exists in the | |
7018 | program. | |
7019 | ||
7020 | You can do this by referring to a contiguous span of memory as an | |
7021 | @dfn{artificial array}, using the binary operator @samp{@@}. The left | |
7022 | operand of @samp{@@} should be the first element of the desired array | |
7023 | and be an individual object. The right operand should be the desired length | |
7024 | of the array. The result is an array value whose elements are all of | |
7025 | the type of the left argument. The first element is actually the left | |
7026 | argument; the second element comes from bytes of memory immediately | |
7027 | following those that hold the first element, and so on. Here is an | |
7028 | example. If a program says | |
7029 | ||
474c8240 | 7030 | @smallexample |
c906108c | 7031 | int *array = (int *) malloc (len * sizeof (int)); |
474c8240 | 7032 | @end smallexample |
c906108c SS |
7033 | |
7034 | @noindent | |
7035 | you can print the contents of @code{array} with | |
7036 | ||
474c8240 | 7037 | @smallexample |
c906108c | 7038 | p *array@@len |
474c8240 | 7039 | @end smallexample |
c906108c SS |
7040 | |
7041 | The left operand of @samp{@@} must reside in memory. Array values made | |
7042 | with @samp{@@} in this way behave just like other arrays in terms of | |
7043 | subscripting, and are coerced to pointers when used in expressions. | |
7044 | Artificial arrays most often appear in expressions via the value history | |
79a6e687 | 7045 | (@pxref{Value History, ,Value History}), after printing one out. |
c906108c SS |
7046 | |
7047 | Another way to create an artificial array is to use a cast. | |
7048 | This re-interprets a value as if it were an array. | |
7049 | The value need not be in memory: | |
474c8240 | 7050 | @smallexample |
c906108c SS |
7051 | (@value{GDBP}) p/x (short[2])0x12345678 |
7052 | $1 = @{0x1234, 0x5678@} | |
474c8240 | 7053 | @end smallexample |
c906108c SS |
7054 | |
7055 | As a convenience, if you leave the array length out (as in | |
c3f6f71d | 7056 | @samp{(@var{type}[])@var{value}}) @value{GDBN} calculates the size to fill |
c906108c | 7057 | the value (as @samp{sizeof(@var{value})/sizeof(@var{type})}: |
474c8240 | 7058 | @smallexample |
c906108c SS |
7059 | (@value{GDBP}) p/x (short[])0x12345678 |
7060 | $2 = @{0x1234, 0x5678@} | |
474c8240 | 7061 | @end smallexample |
c906108c SS |
7062 | |
7063 | Sometimes the artificial array mechanism is not quite enough; in | |
7064 | moderately complex data structures, the elements of interest may not | |
7065 | actually be adjacent---for example, if you are interested in the values | |
7066 | of pointers in an array. One useful work-around in this situation is | |
7067 | to use a convenience variable (@pxref{Convenience Vars, ,Convenience | |
79a6e687 | 7068 | Variables}) as a counter in an expression that prints the first |
c906108c SS |
7069 | interesting value, and then repeat that expression via @key{RET}. For |
7070 | instance, suppose you have an array @code{dtab} of pointers to | |
7071 | structures, and you are interested in the values of a field @code{fv} | |
7072 | in each structure. Here is an example of what you might type: | |
7073 | ||
474c8240 | 7074 | @smallexample |
c906108c SS |
7075 | set $i = 0 |
7076 | p dtab[$i++]->fv | |
7077 | @key{RET} | |
7078 | @key{RET} | |
7079 | @dots{} | |
474c8240 | 7080 | @end smallexample |
c906108c | 7081 | |
6d2ebf8b | 7082 | @node Output Formats |
79a6e687 | 7083 | @section Output Formats |
c906108c SS |
7084 | |
7085 | @cindex formatted output | |
7086 | @cindex output formats | |
7087 | By default, @value{GDBN} prints a value according to its data type. Sometimes | |
7088 | this is not what you want. For example, you might want to print a number | |
7089 | in hex, or a pointer in decimal. Or you might want to view data in memory | |
7090 | at a certain address as a character string or as an instruction. To do | |
7091 | these things, specify an @dfn{output format} when you print a value. | |
7092 | ||
7093 | The simplest use of output formats is to say how to print a value | |
7094 | already computed. This is done by starting the arguments of the | |
7095 | @code{print} command with a slash and a format letter. The format | |
7096 | letters supported are: | |
7097 | ||
7098 | @table @code | |
7099 | @item x | |
7100 | Regard the bits of the value as an integer, and print the integer in | |
7101 | hexadecimal. | |
7102 | ||
7103 | @item d | |
7104 | Print as integer in signed decimal. | |
7105 | ||
7106 | @item u | |
7107 | Print as integer in unsigned decimal. | |
7108 | ||
7109 | @item o | |
7110 | Print as integer in octal. | |
7111 | ||
7112 | @item t | |
7113 | Print as integer in binary. The letter @samp{t} stands for ``two''. | |
7114 | @footnote{@samp{b} cannot be used because these format letters are also | |
7115 | used with the @code{x} command, where @samp{b} stands for ``byte''; | |
79a6e687 | 7116 | see @ref{Memory,,Examining Memory}.} |
c906108c SS |
7117 | |
7118 | @item a | |
7119 | @cindex unknown address, locating | |
3d67e040 | 7120 | @cindex locate address |
c906108c SS |
7121 | Print as an address, both absolute in hexadecimal and as an offset from |
7122 | the nearest preceding symbol. You can use this format used to discover | |
7123 | where (in what function) an unknown address is located: | |
7124 | ||
474c8240 | 7125 | @smallexample |
c906108c SS |
7126 | (@value{GDBP}) p/a 0x54320 |
7127 | $3 = 0x54320 <_initialize_vx+396> | |
474c8240 | 7128 | @end smallexample |
c906108c | 7129 | |
3d67e040 EZ |
7130 | @noindent |
7131 | The command @code{info symbol 0x54320} yields similar results. | |
7132 | @xref{Symbols, info symbol}. | |
7133 | ||
c906108c | 7134 | @item c |
51274035 EZ |
7135 | Regard as an integer and print it as a character constant. This |
7136 | prints both the numerical value and its character representation. The | |
7137 | character representation is replaced with the octal escape @samp{\nnn} | |
7138 | for characters outside the 7-bit @sc{ascii} range. | |
c906108c | 7139 | |
ea37ba09 DJ |
7140 | Without this format, @value{GDBN} displays @code{char}, |
7141 | @w{@code{unsigned char}}, and @w{@code{signed char}} data as character | |
7142 | constants. Single-byte members of vectors are displayed as integer | |
7143 | data. | |
7144 | ||
c906108c SS |
7145 | @item f |
7146 | Regard the bits of the value as a floating point number and print | |
7147 | using typical floating point syntax. | |
ea37ba09 DJ |
7148 | |
7149 | @item s | |
7150 | @cindex printing strings | |
7151 | @cindex printing byte arrays | |
7152 | Regard as a string, if possible. With this format, pointers to single-byte | |
7153 | data are displayed as null-terminated strings and arrays of single-byte data | |
7154 | are displayed as fixed-length strings. Other values are displayed in their | |
7155 | natural types. | |
7156 | ||
7157 | Without this format, @value{GDBN} displays pointers to and arrays of | |
7158 | @code{char}, @w{@code{unsigned char}}, and @w{@code{signed char}} as | |
7159 | strings. Single-byte members of a vector are displayed as an integer | |
7160 | array. | |
a6bac58e TT |
7161 | |
7162 | @item r | |
7163 | @cindex raw printing | |
7164 | Print using the @samp{raw} formatting. By default, @value{GDBN} will | |
78e2826b TT |
7165 | use a Python-based pretty-printer, if one is available (@pxref{Pretty |
7166 | Printing}). This typically results in a higher-level display of the | |
7167 | value's contents. The @samp{r} format bypasses any Python | |
7168 | pretty-printer which might exist. | |
c906108c SS |
7169 | @end table |
7170 | ||
7171 | For example, to print the program counter in hex (@pxref{Registers}), type | |
7172 | ||
474c8240 | 7173 | @smallexample |
c906108c | 7174 | p/x $pc |
474c8240 | 7175 | @end smallexample |
c906108c SS |
7176 | |
7177 | @noindent | |
7178 | Note that no space is required before the slash; this is because command | |
7179 | names in @value{GDBN} cannot contain a slash. | |
7180 | ||
7181 | To reprint the last value in the value history with a different format, | |
7182 | you can use the @code{print} command with just a format and no | |
7183 | expression. For example, @samp{p/x} reprints the last value in hex. | |
7184 | ||
6d2ebf8b | 7185 | @node Memory |
79a6e687 | 7186 | @section Examining Memory |
c906108c SS |
7187 | |
7188 | You can use the command @code{x} (for ``examine'') to examine memory in | |
7189 | any of several formats, independently of your program's data types. | |
7190 | ||
7191 | @cindex examining memory | |
7192 | @table @code | |
41afff9a | 7193 | @kindex x @r{(examine memory)} |
c906108c SS |
7194 | @item x/@var{nfu} @var{addr} |
7195 | @itemx x @var{addr} | |
7196 | @itemx x | |
7197 | Use the @code{x} command to examine memory. | |
7198 | @end table | |
7199 | ||
7200 | @var{n}, @var{f}, and @var{u} are all optional parameters that specify how | |
7201 | much memory to display and how to format it; @var{addr} is an | |
7202 | expression giving the address where you want to start displaying memory. | |
7203 | If you use defaults for @var{nfu}, you need not type the slash @samp{/}. | |
7204 | Several commands set convenient defaults for @var{addr}. | |
7205 | ||
7206 | @table @r | |
7207 | @item @var{n}, the repeat count | |
7208 | The repeat count is a decimal integer; the default is 1. It specifies | |
7209 | how much memory (counting by units @var{u}) to display. | |
7210 | @c This really is **decimal**; unaffected by 'set radix' as of GDB | |
7211 | @c 4.1.2. | |
7212 | ||
7213 | @item @var{f}, the display format | |
51274035 EZ |
7214 | The display format is one of the formats used by @code{print} |
7215 | (@samp{x}, @samp{d}, @samp{u}, @samp{o}, @samp{t}, @samp{a}, @samp{c}, | |
ea37ba09 DJ |
7216 | @samp{f}, @samp{s}), and in addition @samp{i} (for machine instructions). |
7217 | The default is @samp{x} (hexadecimal) initially. The default changes | |
7218 | each time you use either @code{x} or @code{print}. | |
c906108c SS |
7219 | |
7220 | @item @var{u}, the unit size | |
7221 | The unit size is any of | |
7222 | ||
7223 | @table @code | |
7224 | @item b | |
7225 | Bytes. | |
7226 | @item h | |
7227 | Halfwords (two bytes). | |
7228 | @item w | |
7229 | Words (four bytes). This is the initial default. | |
7230 | @item g | |
7231 | Giant words (eight bytes). | |
7232 | @end table | |
7233 | ||
7234 | Each time you specify a unit size with @code{x}, that size becomes the | |
7235 | default unit the next time you use @code{x}. (For the @samp{s} and | |
7236 | @samp{i} formats, the unit size is ignored and is normally not written.) | |
7237 | ||
7238 | @item @var{addr}, starting display address | |
7239 | @var{addr} is the address where you want @value{GDBN} to begin displaying | |
7240 | memory. The expression need not have a pointer value (though it may); | |
7241 | it is always interpreted as an integer address of a byte of memory. | |
7242 | @xref{Expressions, ,Expressions}, for more information on expressions. The default for | |
7243 | @var{addr} is usually just after the last address examined---but several | |
7244 | other commands also set the default address: @code{info breakpoints} (to | |
7245 | the address of the last breakpoint listed), @code{info line} (to the | |
7246 | starting address of a line), and @code{print} (if you use it to display | |
7247 | a value from memory). | |
7248 | @end table | |
7249 | ||
7250 | For example, @samp{x/3uh 0x54320} is a request to display three halfwords | |
7251 | (@code{h}) of memory, formatted as unsigned decimal integers (@samp{u}), | |
7252 | starting at address @code{0x54320}. @samp{x/4xw $sp} prints the four | |
7253 | words (@samp{w}) of memory above the stack pointer (here, @samp{$sp}; | |
d4f3574e | 7254 | @pxref{Registers, ,Registers}) in hexadecimal (@samp{x}). |
c906108c SS |
7255 | |
7256 | Since the letters indicating unit sizes are all distinct from the | |
7257 | letters specifying output formats, you do not have to remember whether | |
7258 | unit size or format comes first; either order works. The output | |
7259 | specifications @samp{4xw} and @samp{4wx} mean exactly the same thing. | |
7260 | (However, the count @var{n} must come first; @samp{wx4} does not work.) | |
7261 | ||
7262 | Even though the unit size @var{u} is ignored for the formats @samp{s} | |
7263 | and @samp{i}, you might still want to use a count @var{n}; for example, | |
7264 | @samp{3i} specifies that you want to see three machine instructions, | |
a4642986 MR |
7265 | including any operands. For convenience, especially when used with |
7266 | the @code{display} command, the @samp{i} format also prints branch delay | |
7267 | slot instructions, if any, beyond the count specified, which immediately | |
7268 | follow the last instruction that is within the count. The command | |
7269 | @code{disassemble} gives an alternative way of inspecting machine | |
7270 | instructions; see @ref{Machine Code,,Source and Machine Code}. | |
c906108c SS |
7271 | |
7272 | All the defaults for the arguments to @code{x} are designed to make it | |
7273 | easy to continue scanning memory with minimal specifications each time | |
7274 | you use @code{x}. For example, after you have inspected three machine | |
7275 | instructions with @samp{x/3i @var{addr}}, you can inspect the next seven | |
7276 | with just @samp{x/7}. If you use @key{RET} to repeat the @code{x} command, | |
7277 | the repeat count @var{n} is used again; the other arguments default as | |
7278 | for successive uses of @code{x}. | |
7279 | ||
2b28d209 PP |
7280 | When examining machine instructions, the instruction at current program |
7281 | counter is shown with a @code{=>} marker. For example: | |
7282 | ||
7283 | @smallexample | |
7284 | (@value{GDBP}) x/5i $pc-6 | |
7285 | 0x804837f <main+11>: mov %esp,%ebp | |
7286 | 0x8048381 <main+13>: push %ecx | |
7287 | 0x8048382 <main+14>: sub $0x4,%esp | |
7288 | => 0x8048385 <main+17>: movl $0x8048460,(%esp) | |
7289 | 0x804838c <main+24>: call 0x80482d4 <puts@@plt> | |
7290 | @end smallexample | |
7291 | ||
c906108c SS |
7292 | @cindex @code{$_}, @code{$__}, and value history |
7293 | The addresses and contents printed by the @code{x} command are not saved | |
7294 | in the value history because there is often too much of them and they | |
7295 | would get in the way. Instead, @value{GDBN} makes these values available for | |
7296 | subsequent use in expressions as values of the convenience variables | |
7297 | @code{$_} and @code{$__}. After an @code{x} command, the last address | |
7298 | examined is available for use in expressions in the convenience variable | |
7299 | @code{$_}. The contents of that address, as examined, are available in | |
7300 | the convenience variable @code{$__}. | |
7301 | ||
7302 | If the @code{x} command has a repeat count, the address and contents saved | |
7303 | are from the last memory unit printed; this is not the same as the last | |
7304 | address printed if several units were printed on the last line of output. | |
7305 | ||
09d4efe1 EZ |
7306 | @cindex remote memory comparison |
7307 | @cindex verify remote memory image | |
7308 | When you are debugging a program running on a remote target machine | |
ea35711c | 7309 | (@pxref{Remote Debugging}), you may wish to verify the program's image in the |
09d4efe1 EZ |
7310 | remote machine's memory against the executable file you downloaded to |
7311 | the target. The @code{compare-sections} command is provided for such | |
7312 | situations. | |
7313 | ||
7314 | @table @code | |
7315 | @kindex compare-sections | |
7316 | @item compare-sections @r{[}@var{section-name}@r{]} | |
7317 | Compare the data of a loadable section @var{section-name} in the | |
7318 | executable file of the program being debugged with the same section in | |
7319 | the remote machine's memory, and report any mismatches. With no | |
7320 | arguments, compares all loadable sections. This command's | |
7321 | availability depends on the target's support for the @code{"qCRC"} | |
7322 | remote request. | |
7323 | @end table | |
7324 | ||
6d2ebf8b | 7325 | @node Auto Display |
79a6e687 | 7326 | @section Automatic Display |
c906108c SS |
7327 | @cindex automatic display |
7328 | @cindex display of expressions | |
7329 | ||
7330 | If you find that you want to print the value of an expression frequently | |
7331 | (to see how it changes), you might want to add it to the @dfn{automatic | |
7332 | display list} so that @value{GDBN} prints its value each time your program stops. | |
7333 | Each expression added to the list is given a number to identify it; | |
7334 | to remove an expression from the list, you specify that number. | |
7335 | The automatic display looks like this: | |
7336 | ||
474c8240 | 7337 | @smallexample |
c906108c SS |
7338 | 2: foo = 38 |
7339 | 3: bar[5] = (struct hack *) 0x3804 | |
474c8240 | 7340 | @end smallexample |
c906108c SS |
7341 | |
7342 | @noindent | |
7343 | This display shows item numbers, expressions and their current values. As with | |
7344 | displays you request manually using @code{x} or @code{print}, you can | |
7345 | specify the output format you prefer; in fact, @code{display} decides | |
ea37ba09 DJ |
7346 | whether to use @code{print} or @code{x} depending your format |
7347 | specification---it uses @code{x} if you specify either the @samp{i} | |
7348 | or @samp{s} format, or a unit size; otherwise it uses @code{print}. | |
c906108c SS |
7349 | |
7350 | @table @code | |
7351 | @kindex display | |
d4f3574e SS |
7352 | @item display @var{expr} |
7353 | Add the expression @var{expr} to the list of expressions to display | |
c906108c SS |
7354 | each time your program stops. @xref{Expressions, ,Expressions}. |
7355 | ||
7356 | @code{display} does not repeat if you press @key{RET} again after using it. | |
7357 | ||
d4f3574e | 7358 | @item display/@var{fmt} @var{expr} |
c906108c | 7359 | For @var{fmt} specifying only a display format and not a size or |
d4f3574e | 7360 | count, add the expression @var{expr} to the auto-display list but |
c906108c | 7361 | arrange to display it each time in the specified format @var{fmt}. |
79a6e687 | 7362 | @xref{Output Formats,,Output Formats}. |
c906108c SS |
7363 | |
7364 | @item display/@var{fmt} @var{addr} | |
7365 | For @var{fmt} @samp{i} or @samp{s}, or including a unit-size or a | |
7366 | number of units, add the expression @var{addr} as a memory address to | |
7367 | be examined each time your program stops. Examining means in effect | |
79a6e687 | 7368 | doing @samp{x/@var{fmt} @var{addr}}. @xref{Memory, ,Examining Memory}. |
c906108c SS |
7369 | @end table |
7370 | ||
7371 | For example, @samp{display/i $pc} can be helpful, to see the machine | |
7372 | instruction about to be executed each time execution stops (@samp{$pc} | |
d4f3574e | 7373 | is a common name for the program counter; @pxref{Registers, ,Registers}). |
c906108c SS |
7374 | |
7375 | @table @code | |
7376 | @kindex delete display | |
7377 | @kindex undisplay | |
7378 | @item undisplay @var{dnums}@dots{} | |
7379 | @itemx delete display @var{dnums}@dots{} | |
7380 | Remove item numbers @var{dnums} from the list of expressions to display. | |
7381 | ||
7382 | @code{undisplay} does not repeat if you press @key{RET} after using it. | |
7383 | (Otherwise you would just get the error @samp{No display number @dots{}}.) | |
7384 | ||
7385 | @kindex disable display | |
7386 | @item disable display @var{dnums}@dots{} | |
7387 | Disable the display of item numbers @var{dnums}. A disabled display | |
7388 | item is not printed automatically, but is not forgotten. It may be | |
7389 | enabled again later. | |
7390 | ||
7391 | @kindex enable display | |
7392 | @item enable display @var{dnums}@dots{} | |
7393 | Enable display of item numbers @var{dnums}. It becomes effective once | |
7394 | again in auto display of its expression, until you specify otherwise. | |
7395 | ||
7396 | @item display | |
7397 | Display the current values of the expressions on the list, just as is | |
7398 | done when your program stops. | |
7399 | ||
7400 | @kindex info display | |
7401 | @item info display | |
7402 | Print the list of expressions previously set up to display | |
7403 | automatically, each one with its item number, but without showing the | |
7404 | values. This includes disabled expressions, which are marked as such. | |
7405 | It also includes expressions which would not be displayed right now | |
7406 | because they refer to automatic variables not currently available. | |
7407 | @end table | |
7408 | ||
15387254 | 7409 | @cindex display disabled out of scope |
c906108c SS |
7410 | If a display expression refers to local variables, then it does not make |
7411 | sense outside the lexical context for which it was set up. Such an | |
7412 | expression is disabled when execution enters a context where one of its | |
7413 | variables is not defined. For example, if you give the command | |
7414 | @code{display last_char} while inside a function with an argument | |
7415 | @code{last_char}, @value{GDBN} displays this argument while your program | |
7416 | continues to stop inside that function. When it stops elsewhere---where | |
7417 | there is no variable @code{last_char}---the display is disabled | |
7418 | automatically. The next time your program stops where @code{last_char} | |
7419 | is meaningful, you can enable the display expression once again. | |
7420 | ||
6d2ebf8b | 7421 | @node Print Settings |
79a6e687 | 7422 | @section Print Settings |
c906108c SS |
7423 | |
7424 | @cindex format options | |
7425 | @cindex print settings | |
7426 | @value{GDBN} provides the following ways to control how arrays, structures, | |
7427 | and symbols are printed. | |
7428 | ||
7429 | @noindent | |
7430 | These settings are useful for debugging programs in any language: | |
7431 | ||
7432 | @table @code | |
4644b6e3 | 7433 | @kindex set print |
c906108c SS |
7434 | @item set print address |
7435 | @itemx set print address on | |
4644b6e3 | 7436 | @cindex print/don't print memory addresses |
c906108c SS |
7437 | @value{GDBN} prints memory addresses showing the location of stack |
7438 | traces, structure values, pointer values, breakpoints, and so forth, | |
7439 | even when it also displays the contents of those addresses. The default | |
7440 | is @code{on}. For example, this is what a stack frame display looks like with | |
7441 | @code{set print address on}: | |
7442 | ||
7443 | @smallexample | |
7444 | @group | |
7445 | (@value{GDBP}) f | |
7446 | #0 set_quotes (lq=0x34c78 "<<", rq=0x34c88 ">>") | |
7447 | at input.c:530 | |
7448 | 530 if (lquote != def_lquote) | |
7449 | @end group | |
7450 | @end smallexample | |
7451 | ||
7452 | @item set print address off | |
7453 | Do not print addresses when displaying their contents. For example, | |
7454 | this is the same stack frame displayed with @code{set print address off}: | |
7455 | ||
7456 | @smallexample | |
7457 | @group | |
7458 | (@value{GDBP}) set print addr off | |
7459 | (@value{GDBP}) f | |
7460 | #0 set_quotes (lq="<<", rq=">>") at input.c:530 | |
7461 | 530 if (lquote != def_lquote) | |
7462 | @end group | |
7463 | @end smallexample | |
7464 | ||
7465 | You can use @samp{set print address off} to eliminate all machine | |
7466 | dependent displays from the @value{GDBN} interface. For example, with | |
7467 | @code{print address off}, you should get the same text for backtraces on | |
7468 | all machines---whether or not they involve pointer arguments. | |
7469 | ||
4644b6e3 | 7470 | @kindex show print |
c906108c SS |
7471 | @item show print address |
7472 | Show whether or not addresses are to be printed. | |
7473 | @end table | |
7474 | ||
7475 | When @value{GDBN} prints a symbolic address, it normally prints the | |
7476 | closest earlier symbol plus an offset. If that symbol does not uniquely | |
7477 | identify the address (for example, it is a name whose scope is a single | |
7478 | source file), you may need to clarify. One way to do this is with | |
7479 | @code{info line}, for example @samp{info line *0x4537}. Alternately, | |
7480 | you can set @value{GDBN} to print the source file and line number when | |
7481 | it prints a symbolic address: | |
7482 | ||
7483 | @table @code | |
c906108c | 7484 | @item set print symbol-filename on |
9c16f35a EZ |
7485 | @cindex source file and line of a symbol |
7486 | @cindex symbol, source file and line | |
c906108c SS |
7487 | Tell @value{GDBN} to print the source file name and line number of a |
7488 | symbol in the symbolic form of an address. | |
7489 | ||
7490 | @item set print symbol-filename off | |
7491 | Do not print source file name and line number of a symbol. This is the | |
7492 | default. | |
7493 | ||
c906108c SS |
7494 | @item show print symbol-filename |
7495 | Show whether or not @value{GDBN} will print the source file name and | |
7496 | line number of a symbol in the symbolic form of an address. | |
7497 | @end table | |
7498 | ||
7499 | Another situation where it is helpful to show symbol filenames and line | |
7500 | numbers is when disassembling code; @value{GDBN} shows you the line | |
7501 | number and source file that corresponds to each instruction. | |
7502 | ||
7503 | Also, you may wish to see the symbolic form only if the address being | |
7504 | printed is reasonably close to the closest earlier symbol: | |
7505 | ||
7506 | @table @code | |
c906108c | 7507 | @item set print max-symbolic-offset @var{max-offset} |
4644b6e3 | 7508 | @cindex maximum value for offset of closest symbol |
c906108c SS |
7509 | Tell @value{GDBN} to only display the symbolic form of an address if the |
7510 | offset between the closest earlier symbol and the address is less than | |
5d161b24 | 7511 | @var{max-offset}. The default is 0, which tells @value{GDBN} |
c906108c SS |
7512 | to always print the symbolic form of an address if any symbol precedes it. |
7513 | ||
c906108c SS |
7514 | @item show print max-symbolic-offset |
7515 | Ask how large the maximum offset is that @value{GDBN} prints in a | |
7516 | symbolic address. | |
7517 | @end table | |
7518 | ||
7519 | @cindex wild pointer, interpreting | |
7520 | @cindex pointer, finding referent | |
7521 | If you have a pointer and you are not sure where it points, try | |
7522 | @samp{set print symbol-filename on}. Then you can determine the name | |
7523 | and source file location of the variable where it points, using | |
7524 | @samp{p/a @var{pointer}}. This interprets the address in symbolic form. | |
7525 | For example, here @value{GDBN} shows that a variable @code{ptt} points | |
7526 | at another variable @code{t}, defined in @file{hi2.c}: | |
7527 | ||
474c8240 | 7528 | @smallexample |
c906108c SS |
7529 | (@value{GDBP}) set print symbol-filename on |
7530 | (@value{GDBP}) p/a ptt | |
7531 | $4 = 0xe008 <t in hi2.c> | |
474c8240 | 7532 | @end smallexample |
c906108c SS |
7533 | |
7534 | @quotation | |
7535 | @emph{Warning:} For pointers that point to a local variable, @samp{p/a} | |
7536 | does not show the symbol name and filename of the referent, even with | |
7537 | the appropriate @code{set print} options turned on. | |
7538 | @end quotation | |
7539 | ||
7540 | Other settings control how different kinds of objects are printed: | |
7541 | ||
7542 | @table @code | |
c906108c SS |
7543 | @item set print array |
7544 | @itemx set print array on | |
4644b6e3 | 7545 | @cindex pretty print arrays |
c906108c SS |
7546 | Pretty print arrays. This format is more convenient to read, |
7547 | but uses more space. The default is off. | |
7548 | ||
7549 | @item set print array off | |
7550 | Return to compressed format for arrays. | |
7551 | ||
c906108c SS |
7552 | @item show print array |
7553 | Show whether compressed or pretty format is selected for displaying | |
7554 | arrays. | |
7555 | ||
3c9c013a JB |
7556 | @cindex print array indexes |
7557 | @item set print array-indexes | |
7558 | @itemx set print array-indexes on | |
7559 | Print the index of each element when displaying arrays. May be more | |
7560 | convenient to locate a given element in the array or quickly find the | |
7561 | index of a given element in that printed array. The default is off. | |
7562 | ||
7563 | @item set print array-indexes off | |
7564 | Stop printing element indexes when displaying arrays. | |
7565 | ||
7566 | @item show print array-indexes | |
7567 | Show whether the index of each element is printed when displaying | |
7568 | arrays. | |
7569 | ||
c906108c | 7570 | @item set print elements @var{number-of-elements} |
4644b6e3 | 7571 | @cindex number of array elements to print |
9c16f35a | 7572 | @cindex limit on number of printed array elements |
c906108c SS |
7573 | Set a limit on how many elements of an array @value{GDBN} will print. |
7574 | If @value{GDBN} is printing a large array, it stops printing after it has | |
7575 | printed the number of elements set by the @code{set print elements} command. | |
7576 | This limit also applies to the display of strings. | |
d4f3574e | 7577 | When @value{GDBN} starts, this limit is set to 200. |
c906108c SS |
7578 | Setting @var{number-of-elements} to zero means that the printing is unlimited. |
7579 | ||
c906108c SS |
7580 | @item show print elements |
7581 | Display the number of elements of a large array that @value{GDBN} will print. | |
7582 | If the number is 0, then the printing is unlimited. | |
7583 | ||
b4740add | 7584 | @item set print frame-arguments @var{value} |
a0381d3a | 7585 | @kindex set print frame-arguments |
b4740add JB |
7586 | @cindex printing frame argument values |
7587 | @cindex print all frame argument values | |
7588 | @cindex print frame argument values for scalars only | |
7589 | @cindex do not print frame argument values | |
7590 | This command allows to control how the values of arguments are printed | |
7591 | when the debugger prints a frame (@pxref{Frames}). The possible | |
7592 | values are: | |
7593 | ||
7594 | @table @code | |
7595 | @item all | |
4f5376b2 | 7596 | The values of all arguments are printed. |
b4740add JB |
7597 | |
7598 | @item scalars | |
7599 | Print the value of an argument only if it is a scalar. The value of more | |
7600 | complex arguments such as arrays, structures, unions, etc, is replaced | |
4f5376b2 JB |
7601 | by @code{@dots{}}. This is the default. Here is an example where |
7602 | only scalar arguments are shown: | |
b4740add JB |
7603 | |
7604 | @smallexample | |
7605 | #1 0x08048361 in call_me (i=3, s=@dots{}, ss=0xbf8d508c, u=@dots{}, e=green) | |
7606 | at frame-args.c:23 | |
7607 | @end smallexample | |
7608 | ||
7609 | @item none | |
7610 | None of the argument values are printed. Instead, the value of each argument | |
7611 | is replaced by @code{@dots{}}. In this case, the example above now becomes: | |
7612 | ||
7613 | @smallexample | |
7614 | #1 0x08048361 in call_me (i=@dots{}, s=@dots{}, ss=@dots{}, u=@dots{}, e=@dots{}) | |
7615 | at frame-args.c:23 | |
7616 | @end smallexample | |
7617 | @end table | |
7618 | ||
4f5376b2 JB |
7619 | By default, only scalar arguments are printed. This command can be used |
7620 | to configure the debugger to print the value of all arguments, regardless | |
7621 | of their type. However, it is often advantageous to not print the value | |
7622 | of more complex parameters. For instance, it reduces the amount of | |
7623 | information printed in each frame, making the backtrace more readable. | |
7624 | Also, it improves performance when displaying Ada frames, because | |
7625 | the computation of large arguments can sometimes be CPU-intensive, | |
7626 | especially in large applications. Setting @code{print frame-arguments} | |
7627 | to @code{scalars} (the default) or @code{none} avoids this computation, | |
7628 | thus speeding up the display of each Ada frame. | |
b4740add JB |
7629 | |
7630 | @item show print frame-arguments | |
7631 | Show how the value of arguments should be displayed when printing a frame. | |
7632 | ||
9c16f35a EZ |
7633 | @item set print repeats |
7634 | @cindex repeated array elements | |
7635 | Set the threshold for suppressing display of repeated array | |
d3e8051b | 7636 | elements. When the number of consecutive identical elements of an |
9c16f35a EZ |
7637 | array exceeds the threshold, @value{GDBN} prints the string |
7638 | @code{"<repeats @var{n} times>"}, where @var{n} is the number of | |
7639 | identical repetitions, instead of displaying the identical elements | |
7640 | themselves. Setting the threshold to zero will cause all elements to | |
7641 | be individually printed. The default threshold is 10. | |
7642 | ||
7643 | @item show print repeats | |
7644 | Display the current threshold for printing repeated identical | |
7645 | elements. | |
7646 | ||
c906108c | 7647 | @item set print null-stop |
4644b6e3 | 7648 | @cindex @sc{null} elements in arrays |
c906108c | 7649 | Cause @value{GDBN} to stop printing the characters of an array when the first |
d4f3574e | 7650 | @sc{null} is encountered. This is useful when large arrays actually |
c906108c | 7651 | contain only short strings. |
d4f3574e | 7652 | The default is off. |
c906108c | 7653 | |
9c16f35a EZ |
7654 | @item show print null-stop |
7655 | Show whether @value{GDBN} stops printing an array on the first | |
7656 | @sc{null} character. | |
7657 | ||
c906108c | 7658 | @item set print pretty on |
9c16f35a EZ |
7659 | @cindex print structures in indented form |
7660 | @cindex indentation in structure display | |
5d161b24 | 7661 | Cause @value{GDBN} to print structures in an indented format with one member |
c906108c SS |
7662 | per line, like this: |
7663 | ||
7664 | @smallexample | |
7665 | @group | |
7666 | $1 = @{ | |
7667 | next = 0x0, | |
7668 | flags = @{ | |
7669 | sweet = 1, | |
7670 | sour = 1 | |
7671 | @}, | |
7672 | meat = 0x54 "Pork" | |
7673 | @} | |
7674 | @end group | |
7675 | @end smallexample | |
7676 | ||
7677 | @item set print pretty off | |
7678 | Cause @value{GDBN} to print structures in a compact format, like this: | |
7679 | ||
7680 | @smallexample | |
7681 | @group | |
7682 | $1 = @{next = 0x0, flags = @{sweet = 1, sour = 1@}, \ | |
7683 | meat = 0x54 "Pork"@} | |
7684 | @end group | |
7685 | @end smallexample | |
7686 | ||
7687 | @noindent | |
7688 | This is the default format. | |
7689 | ||
c906108c SS |
7690 | @item show print pretty |
7691 | Show which format @value{GDBN} is using to print structures. | |
7692 | ||
c906108c | 7693 | @item set print sevenbit-strings on |
4644b6e3 EZ |
7694 | @cindex eight-bit characters in strings |
7695 | @cindex octal escapes in strings | |
c906108c SS |
7696 | Print using only seven-bit characters; if this option is set, |
7697 | @value{GDBN} displays any eight-bit characters (in strings or | |
7698 | character values) using the notation @code{\}@var{nnn}. This setting is | |
7699 | best if you are working in English (@sc{ascii}) and you use the | |
7700 | high-order bit of characters as a marker or ``meta'' bit. | |
7701 | ||
7702 | @item set print sevenbit-strings off | |
7703 | Print full eight-bit characters. This allows the use of more | |
7704 | international character sets, and is the default. | |
7705 | ||
c906108c SS |
7706 | @item show print sevenbit-strings |
7707 | Show whether or not @value{GDBN} is printing only seven-bit characters. | |
7708 | ||
c906108c | 7709 | @item set print union on |
4644b6e3 | 7710 | @cindex unions in structures, printing |
9c16f35a EZ |
7711 | Tell @value{GDBN} to print unions which are contained in structures |
7712 | and other unions. This is the default setting. | |
c906108c SS |
7713 | |
7714 | @item set print union off | |
9c16f35a EZ |
7715 | Tell @value{GDBN} not to print unions which are contained in |
7716 | structures and other unions. @value{GDBN} will print @code{"@{...@}"} | |
7717 | instead. | |
c906108c | 7718 | |
c906108c SS |
7719 | @item show print union |
7720 | Ask @value{GDBN} whether or not it will print unions which are contained in | |
9c16f35a | 7721 | structures and other unions. |
c906108c SS |
7722 | |
7723 | For example, given the declarations | |
7724 | ||
7725 | @smallexample | |
7726 | typedef enum @{Tree, Bug@} Species; | |
7727 | typedef enum @{Big_tree, Acorn, Seedling@} Tree_forms; | |
5d161b24 | 7728 | typedef enum @{Caterpillar, Cocoon, Butterfly@} |
c906108c SS |
7729 | Bug_forms; |
7730 | ||
7731 | struct thing @{ | |
7732 | Species it; | |
7733 | union @{ | |
7734 | Tree_forms tree; | |
7735 | Bug_forms bug; | |
7736 | @} form; | |
7737 | @}; | |
7738 | ||
7739 | struct thing foo = @{Tree, @{Acorn@}@}; | |
7740 | @end smallexample | |
7741 | ||
7742 | @noindent | |
7743 | with @code{set print union on} in effect @samp{p foo} would print | |
7744 | ||
7745 | @smallexample | |
7746 | $1 = @{it = Tree, form = @{tree = Acorn, bug = Cocoon@}@} | |
7747 | @end smallexample | |
7748 | ||
7749 | @noindent | |
7750 | and with @code{set print union off} in effect it would print | |
7751 | ||
7752 | @smallexample | |
7753 | $1 = @{it = Tree, form = @{...@}@} | |
7754 | @end smallexample | |
9c16f35a EZ |
7755 | |
7756 | @noindent | |
7757 | @code{set print union} affects programs written in C-like languages | |
7758 | and in Pascal. | |
c906108c SS |
7759 | @end table |
7760 | ||
c906108c SS |
7761 | @need 1000 |
7762 | @noindent | |
b37052ae | 7763 | These settings are of interest when debugging C@t{++} programs: |
c906108c SS |
7764 | |
7765 | @table @code | |
4644b6e3 | 7766 | @cindex demangling C@t{++} names |
c906108c SS |
7767 | @item set print demangle |
7768 | @itemx set print demangle on | |
b37052ae | 7769 | Print C@t{++} names in their source form rather than in the encoded |
c906108c | 7770 | (``mangled'') form passed to the assembler and linker for type-safe |
d4f3574e | 7771 | linkage. The default is on. |
c906108c | 7772 | |
c906108c | 7773 | @item show print demangle |
b37052ae | 7774 | Show whether C@t{++} names are printed in mangled or demangled form. |
c906108c | 7775 | |
c906108c SS |
7776 | @item set print asm-demangle |
7777 | @itemx set print asm-demangle on | |
b37052ae | 7778 | Print C@t{++} names in their source form rather than their mangled form, even |
c906108c SS |
7779 | in assembler code printouts such as instruction disassemblies. |
7780 | The default is off. | |
7781 | ||
c906108c | 7782 | @item show print asm-demangle |
b37052ae | 7783 | Show whether C@t{++} names in assembly listings are printed in mangled |
c906108c SS |
7784 | or demangled form. |
7785 | ||
b37052ae EZ |
7786 | @cindex C@t{++} symbol decoding style |
7787 | @cindex symbol decoding style, C@t{++} | |
a8f24a35 | 7788 | @kindex set demangle-style |
c906108c SS |
7789 | @item set demangle-style @var{style} |
7790 | Choose among several encoding schemes used by different compilers to | |
b37052ae | 7791 | represent C@t{++} names. The choices for @var{style} are currently: |
c906108c SS |
7792 | |
7793 | @table @code | |
7794 | @item auto | |
7795 | Allow @value{GDBN} to choose a decoding style by inspecting your program. | |
7796 | ||
7797 | @item gnu | |
b37052ae | 7798 | Decode based on the @sc{gnu} C@t{++} compiler (@code{g++}) encoding algorithm. |
c906108c | 7799 | This is the default. |
c906108c SS |
7800 | |
7801 | @item hp | |
b37052ae | 7802 | Decode based on the HP ANSI C@t{++} (@code{aCC}) encoding algorithm. |
c906108c SS |
7803 | |
7804 | @item lucid | |
b37052ae | 7805 | Decode based on the Lucid C@t{++} compiler (@code{lcc}) encoding algorithm. |
c906108c SS |
7806 | |
7807 | @item arm | |
b37052ae | 7808 | Decode using the algorithm in the @cite{C@t{++} Annotated Reference Manual}. |
c906108c SS |
7809 | @strong{Warning:} this setting alone is not sufficient to allow |
7810 | debugging @code{cfront}-generated executables. @value{GDBN} would | |
7811 | require further enhancement to permit that. | |
7812 | ||
7813 | @end table | |
7814 | If you omit @var{style}, you will see a list of possible formats. | |
7815 | ||
c906108c | 7816 | @item show demangle-style |
b37052ae | 7817 | Display the encoding style currently in use for decoding C@t{++} symbols. |
c906108c | 7818 | |
c906108c SS |
7819 | @item set print object |
7820 | @itemx set print object on | |
4644b6e3 | 7821 | @cindex derived type of an object, printing |
9c16f35a | 7822 | @cindex display derived types |
c906108c SS |
7823 | When displaying a pointer to an object, identify the @emph{actual} |
7824 | (derived) type of the object rather than the @emph{declared} type, using | |
7825 | the virtual function table. | |
7826 | ||
7827 | @item set print object off | |
7828 | Display only the declared type of objects, without reference to the | |
7829 | virtual function table. This is the default setting. | |
7830 | ||
c906108c SS |
7831 | @item show print object |
7832 | Show whether actual, or declared, object types are displayed. | |
7833 | ||
c906108c SS |
7834 | @item set print static-members |
7835 | @itemx set print static-members on | |
4644b6e3 | 7836 | @cindex static members of C@t{++} objects |
b37052ae | 7837 | Print static members when displaying a C@t{++} object. The default is on. |
c906108c SS |
7838 | |
7839 | @item set print static-members off | |
b37052ae | 7840 | Do not print static members when displaying a C@t{++} object. |
c906108c | 7841 | |
c906108c | 7842 | @item show print static-members |
9c16f35a EZ |
7843 | Show whether C@t{++} static members are printed or not. |
7844 | ||
7845 | @item set print pascal_static-members | |
7846 | @itemx set print pascal_static-members on | |
d3e8051b EZ |
7847 | @cindex static members of Pascal objects |
7848 | @cindex Pascal objects, static members display | |
9c16f35a EZ |
7849 | Print static members when displaying a Pascal object. The default is on. |
7850 | ||
7851 | @item set print pascal_static-members off | |
7852 | Do not print static members when displaying a Pascal object. | |
7853 | ||
7854 | @item show print pascal_static-members | |
7855 | Show whether Pascal static members are printed or not. | |
c906108c SS |
7856 | |
7857 | @c These don't work with HP ANSI C++ yet. | |
c906108c SS |
7858 | @item set print vtbl |
7859 | @itemx set print vtbl on | |
4644b6e3 | 7860 | @cindex pretty print C@t{++} virtual function tables |
9c16f35a EZ |
7861 | @cindex virtual functions (C@t{++}) display |
7862 | @cindex VTBL display | |
b37052ae | 7863 | Pretty print C@t{++} virtual function tables. The default is off. |
c906108c | 7864 | (The @code{vtbl} commands do not work on programs compiled with the HP |
b37052ae | 7865 | ANSI C@t{++} compiler (@code{aCC}).) |
c906108c SS |
7866 | |
7867 | @item set print vtbl off | |
b37052ae | 7868 | Do not pretty print C@t{++} virtual function tables. |
c906108c | 7869 | |
c906108c | 7870 | @item show print vtbl |
b37052ae | 7871 | Show whether C@t{++} virtual function tables are pretty printed, or not. |
c906108c | 7872 | @end table |
c906108c | 7873 | |
6d2ebf8b | 7874 | @node Value History |
79a6e687 | 7875 | @section Value History |
c906108c SS |
7876 | |
7877 | @cindex value history | |
9c16f35a | 7878 | @cindex history of values printed by @value{GDBN} |
5d161b24 DB |
7879 | Values printed by the @code{print} command are saved in the @value{GDBN} |
7880 | @dfn{value history}. This allows you to refer to them in other expressions. | |
7881 | Values are kept until the symbol table is re-read or discarded | |
7882 | (for example with the @code{file} or @code{symbol-file} commands). | |
7883 | When the symbol table changes, the value history is discarded, | |
7884 | since the values may contain pointers back to the types defined in the | |
c906108c SS |
7885 | symbol table. |
7886 | ||
7887 | @cindex @code{$} | |
7888 | @cindex @code{$$} | |
7889 | @cindex history number | |
7890 | The values printed are given @dfn{history numbers} by which you can | |
7891 | refer to them. These are successive integers starting with one. | |
7892 | @code{print} shows you the history number assigned to a value by | |
7893 | printing @samp{$@var{num} = } before the value; here @var{num} is the | |
7894 | history number. | |
7895 | ||
7896 | To refer to any previous value, use @samp{$} followed by the value's | |
7897 | history number. The way @code{print} labels its output is designed to | |
7898 | remind you of this. Just @code{$} refers to the most recent value in | |
7899 | the history, and @code{$$} refers to the value before that. | |
7900 | @code{$$@var{n}} refers to the @var{n}th value from the end; @code{$$2} | |
7901 | is the value just prior to @code{$$}, @code{$$1} is equivalent to | |
7902 | @code{$$}, and @code{$$0} is equivalent to @code{$}. | |
7903 | ||
7904 | For example, suppose you have just printed a pointer to a structure and | |
7905 | want to see the contents of the structure. It suffices to type | |
7906 | ||
474c8240 | 7907 | @smallexample |
c906108c | 7908 | p *$ |
474c8240 | 7909 | @end smallexample |
c906108c SS |
7910 | |
7911 | If you have a chain of structures where the component @code{next} points | |
7912 | to the next one, you can print the contents of the next one with this: | |
7913 | ||
474c8240 | 7914 | @smallexample |
c906108c | 7915 | p *$.next |
474c8240 | 7916 | @end smallexample |
c906108c SS |
7917 | |
7918 | @noindent | |
7919 | You can print successive links in the chain by repeating this | |
7920 | command---which you can do by just typing @key{RET}. | |
7921 | ||
7922 | Note that the history records values, not expressions. If the value of | |
7923 | @code{x} is 4 and you type these commands: | |
7924 | ||
474c8240 | 7925 | @smallexample |
c906108c SS |
7926 | print x |
7927 | set x=5 | |
474c8240 | 7928 | @end smallexample |
c906108c SS |
7929 | |
7930 | @noindent | |
7931 | then the value recorded in the value history by the @code{print} command | |
7932 | remains 4 even though the value of @code{x} has changed. | |
7933 | ||
7934 | @table @code | |
7935 | @kindex show values | |
7936 | @item show values | |
7937 | Print the last ten values in the value history, with their item numbers. | |
7938 | This is like @samp{p@ $$9} repeated ten times, except that @code{show | |
7939 | values} does not change the history. | |
7940 | ||
7941 | @item show values @var{n} | |
7942 | Print ten history values centered on history item number @var{n}. | |
7943 | ||
7944 | @item show values + | |
7945 | Print ten history values just after the values last printed. If no more | |
7946 | values are available, @code{show values +} produces no display. | |
7947 | @end table | |
7948 | ||
7949 | Pressing @key{RET} to repeat @code{show values @var{n}} has exactly the | |
7950 | same effect as @samp{show values +}. | |
7951 | ||
6d2ebf8b | 7952 | @node Convenience Vars |
79a6e687 | 7953 | @section Convenience Variables |
c906108c SS |
7954 | |
7955 | @cindex convenience variables | |
9c16f35a | 7956 | @cindex user-defined variables |
c906108c SS |
7957 | @value{GDBN} provides @dfn{convenience variables} that you can use within |
7958 | @value{GDBN} to hold on to a value and refer to it later. These variables | |
7959 | exist entirely within @value{GDBN}; they are not part of your program, and | |
7960 | setting a convenience variable has no direct effect on further execution | |
7961 | of your program. That is why you can use them freely. | |
7962 | ||
7963 | Convenience variables are prefixed with @samp{$}. Any name preceded by | |
7964 | @samp{$} can be used for a convenience variable, unless it is one of | |
d4f3574e | 7965 | the predefined machine-specific register names (@pxref{Registers, ,Registers}). |
c906108c | 7966 | (Value history references, in contrast, are @emph{numbers} preceded |
79a6e687 | 7967 | by @samp{$}. @xref{Value History, ,Value History}.) |
c906108c SS |
7968 | |
7969 | You can save a value in a convenience variable with an assignment | |
7970 | expression, just as you would set a variable in your program. | |
7971 | For example: | |
7972 | ||
474c8240 | 7973 | @smallexample |
c906108c | 7974 | set $foo = *object_ptr |
474c8240 | 7975 | @end smallexample |
c906108c SS |
7976 | |
7977 | @noindent | |
7978 | would save in @code{$foo} the value contained in the object pointed to by | |
7979 | @code{object_ptr}. | |
7980 | ||
7981 | Using a convenience variable for the first time creates it, but its | |
7982 | value is @code{void} until you assign a new value. You can alter the | |
7983 | value with another assignment at any time. | |
7984 | ||
7985 | Convenience variables have no fixed types. You can assign a convenience | |
7986 | variable any type of value, including structures and arrays, even if | |
7987 | that variable already has a value of a different type. The convenience | |
7988 | variable, when used as an expression, has the type of its current value. | |
7989 | ||
7990 | @table @code | |
7991 | @kindex show convenience | |
9c16f35a | 7992 | @cindex show all user variables |
c906108c SS |
7993 | @item show convenience |
7994 | Print a list of convenience variables used so far, and their values. | |
d4f3574e | 7995 | Abbreviated @code{show conv}. |
53e5f3cf AS |
7996 | |
7997 | @kindex init-if-undefined | |
7998 | @cindex convenience variables, initializing | |
7999 | @item init-if-undefined $@var{variable} = @var{expression} | |
8000 | Set a convenience variable if it has not already been set. This is useful | |
8001 | for user-defined commands that keep some state. It is similar, in concept, | |
8002 | to using local static variables with initializers in C (except that | |
8003 | convenience variables are global). It can also be used to allow users to | |
8004 | override default values used in a command script. | |
8005 | ||
8006 | If the variable is already defined then the expression is not evaluated so | |
8007 | any side-effects do not occur. | |
c906108c SS |
8008 | @end table |
8009 | ||
8010 | One of the ways to use a convenience variable is as a counter to be | |
8011 | incremented or a pointer to be advanced. For example, to print | |
8012 | a field from successive elements of an array of structures: | |
8013 | ||
474c8240 | 8014 | @smallexample |
c906108c SS |
8015 | set $i = 0 |
8016 | print bar[$i++]->contents | |
474c8240 | 8017 | @end smallexample |
c906108c | 8018 | |
d4f3574e SS |
8019 | @noindent |
8020 | Repeat that command by typing @key{RET}. | |
c906108c SS |
8021 | |
8022 | Some convenience variables are created automatically by @value{GDBN} and given | |
8023 | values likely to be useful. | |
8024 | ||
8025 | @table @code | |
41afff9a | 8026 | @vindex $_@r{, convenience variable} |
c906108c SS |
8027 | @item $_ |
8028 | The variable @code{$_} is automatically set by the @code{x} command to | |
79a6e687 | 8029 | the last address examined (@pxref{Memory, ,Examining Memory}). Other |
c906108c SS |
8030 | commands which provide a default address for @code{x} to examine also |
8031 | set @code{$_} to that address; these commands include @code{info line} | |
8032 | and @code{info breakpoint}. The type of @code{$_} is @code{void *} | |
8033 | except when set by the @code{x} command, in which case it is a pointer | |
8034 | to the type of @code{$__}. | |
8035 | ||
41afff9a | 8036 | @vindex $__@r{, convenience variable} |
c906108c SS |
8037 | @item $__ |
8038 | The variable @code{$__} is automatically set by the @code{x} command | |
8039 | to the value found in the last address examined. Its type is chosen | |
8040 | to match the format in which the data was printed. | |
8041 | ||
8042 | @item $_exitcode | |
41afff9a | 8043 | @vindex $_exitcode@r{, convenience variable} |
c906108c SS |
8044 | The variable @code{$_exitcode} is automatically set to the exit code when |
8045 | the program being debugged terminates. | |
4aa995e1 PA |
8046 | |
8047 | @item $_siginfo | |
8048 | @vindex $_siginfo@r{, convenience variable} | |
ec7e75e7 PP |
8049 | The variable @code{$_siginfo} contains extra signal information |
8050 | (@pxref{extra signal information}). Note that @code{$_siginfo} | |
8051 | could be empty, if the application has not yet received any signals. | |
8052 | For example, it will be empty before you execute the @code{run} command. | |
c906108c SS |
8053 | @end table |
8054 | ||
53a5351d JM |
8055 | On HP-UX systems, if you refer to a function or variable name that |
8056 | begins with a dollar sign, @value{GDBN} searches for a user or system | |
8057 | name first, before it searches for a convenience variable. | |
c906108c | 8058 | |
bc3b79fd TJB |
8059 | @cindex convenience functions |
8060 | @value{GDBN} also supplies some @dfn{convenience functions}. These | |
8061 | have a syntax similar to convenience variables. A convenience | |
8062 | function can be used in an expression just like an ordinary function; | |
8063 | however, a convenience function is implemented internally to | |
8064 | @value{GDBN}. | |
8065 | ||
8066 | @table @code | |
8067 | @item help function | |
8068 | @kindex help function | |
8069 | @cindex show all convenience functions | |
8070 | Print a list of all convenience functions. | |
8071 | @end table | |
8072 | ||
6d2ebf8b | 8073 | @node Registers |
c906108c SS |
8074 | @section Registers |
8075 | ||
8076 | @cindex registers | |
8077 | You can refer to machine register contents, in expressions, as variables | |
8078 | with names starting with @samp{$}. The names of registers are different | |
8079 | for each machine; use @code{info registers} to see the names used on | |
8080 | your machine. | |
8081 | ||
8082 | @table @code | |
8083 | @kindex info registers | |
8084 | @item info registers | |
8085 | Print the names and values of all registers except floating-point | |
c85508ee | 8086 | and vector registers (in the selected stack frame). |
c906108c SS |
8087 | |
8088 | @kindex info all-registers | |
8089 | @cindex floating point registers | |
8090 | @item info all-registers | |
8091 | Print the names and values of all registers, including floating-point | |
c85508ee | 8092 | and vector registers (in the selected stack frame). |
c906108c SS |
8093 | |
8094 | @item info registers @var{regname} @dots{} | |
8095 | Print the @dfn{relativized} value of each specified register @var{regname}. | |
5d161b24 DB |
8096 | As discussed in detail below, register values are normally relative to |
8097 | the selected stack frame. @var{regname} may be any register name valid on | |
c906108c SS |
8098 | the machine you are using, with or without the initial @samp{$}. |
8099 | @end table | |
8100 | ||
e09f16f9 EZ |
8101 | @cindex stack pointer register |
8102 | @cindex program counter register | |
8103 | @cindex process status register | |
8104 | @cindex frame pointer register | |
8105 | @cindex standard registers | |
c906108c SS |
8106 | @value{GDBN} has four ``standard'' register names that are available (in |
8107 | expressions) on most machines---whenever they do not conflict with an | |
8108 | architecture's canonical mnemonics for registers. The register names | |
8109 | @code{$pc} and @code{$sp} are used for the program counter register and | |
8110 | the stack pointer. @code{$fp} is used for a register that contains a | |
8111 | pointer to the current stack frame, and @code{$ps} is used for a | |
8112 | register that contains the processor status. For example, | |
8113 | you could print the program counter in hex with | |
8114 | ||
474c8240 | 8115 | @smallexample |
c906108c | 8116 | p/x $pc |
474c8240 | 8117 | @end smallexample |
c906108c SS |
8118 | |
8119 | @noindent | |
8120 | or print the instruction to be executed next with | |
8121 | ||
474c8240 | 8122 | @smallexample |
c906108c | 8123 | x/i $pc |
474c8240 | 8124 | @end smallexample |
c906108c SS |
8125 | |
8126 | @noindent | |
8127 | or add four to the stack pointer@footnote{This is a way of removing | |
8128 | one word from the stack, on machines where stacks grow downward in | |
8129 | memory (most machines, nowadays). This assumes that the innermost | |
8130 | stack frame is selected; setting @code{$sp} is not allowed when other | |
8131 | stack frames are selected. To pop entire frames off the stack, | |
8132 | regardless of machine architecture, use @code{return}; | |
79a6e687 | 8133 | see @ref{Returning, ,Returning from a Function}.} with |
c906108c | 8134 | |
474c8240 | 8135 | @smallexample |
c906108c | 8136 | set $sp += 4 |
474c8240 | 8137 | @end smallexample |
c906108c SS |
8138 | |
8139 | Whenever possible, these four standard register names are available on | |
8140 | your machine even though the machine has different canonical mnemonics, | |
8141 | so long as there is no conflict. The @code{info registers} command | |
8142 | shows the canonical names. For example, on the SPARC, @code{info | |
8143 | registers} displays the processor status register as @code{$psr} but you | |
d4f3574e SS |
8144 | can also refer to it as @code{$ps}; and on x86-based machines @code{$ps} |
8145 | is an alias for the @sc{eflags} register. | |
c906108c SS |
8146 | |
8147 | @value{GDBN} always considers the contents of an ordinary register as an | |
8148 | integer when the register is examined in this way. Some machines have | |
8149 | special registers which can hold nothing but floating point; these | |
8150 | registers are considered to have floating point values. There is no way | |
8151 | to refer to the contents of an ordinary register as floating point value | |
8152 | (although you can @emph{print} it as a floating point value with | |
8153 | @samp{print/f $@var{regname}}). | |
8154 | ||
8155 | Some registers have distinct ``raw'' and ``virtual'' data formats. This | |
8156 | means that the data format in which the register contents are saved by | |
8157 | the operating system is not the same one that your program normally | |
8158 | sees. For example, the registers of the 68881 floating point | |
8159 | coprocessor are always saved in ``extended'' (raw) format, but all C | |
8160 | programs expect to work with ``double'' (virtual) format. In such | |
5d161b24 | 8161 | cases, @value{GDBN} normally works with the virtual format only (the format |
c906108c SS |
8162 | that makes sense for your program), but the @code{info registers} command |
8163 | prints the data in both formats. | |
8164 | ||
36b80e65 EZ |
8165 | @cindex SSE registers (x86) |
8166 | @cindex MMX registers (x86) | |
8167 | Some machines have special registers whose contents can be interpreted | |
8168 | in several different ways. For example, modern x86-based machines | |
8169 | have SSE and MMX registers that can hold several values packed | |
8170 | together in several different formats. @value{GDBN} refers to such | |
8171 | registers in @code{struct} notation: | |
8172 | ||
8173 | @smallexample | |
8174 | (@value{GDBP}) print $xmm1 | |
8175 | $1 = @{ | |
8176 | v4_float = @{0, 3.43859137e-038, 1.54142831e-044, 1.821688e-044@}, | |
8177 | v2_double = @{9.92129282474342e-303, 2.7585945287983262e-313@}, | |
8178 | v16_int8 = "\000\000\000\000\3706;\001\v\000\000\000\r\000\000", | |
8179 | v8_int16 = @{0, 0, 14072, 315, 11, 0, 13, 0@}, | |
8180 | v4_int32 = @{0, 20657912, 11, 13@}, | |
8181 | v2_int64 = @{88725056443645952, 55834574859@}, | |
8182 | uint128 = 0x0000000d0000000b013b36f800000000 | |
8183 | @} | |
8184 | @end smallexample | |
8185 | ||
8186 | @noindent | |
8187 | To set values of such registers, you need to tell @value{GDBN} which | |
8188 | view of the register you wish to change, as if you were assigning | |
8189 | value to a @code{struct} member: | |
8190 | ||
8191 | @smallexample | |
8192 | (@value{GDBP}) set $xmm1.uint128 = 0x000000000000000000000000FFFFFFFF | |
8193 | @end smallexample | |
8194 | ||
c906108c | 8195 | Normally, register values are relative to the selected stack frame |
79a6e687 | 8196 | (@pxref{Selection, ,Selecting a Frame}). This means that you get the |
c906108c SS |
8197 | value that the register would contain if all stack frames farther in |
8198 | were exited and their saved registers restored. In order to see the | |
8199 | true contents of hardware registers, you must select the innermost | |
8200 | frame (with @samp{frame 0}). | |
8201 | ||
8202 | However, @value{GDBN} must deduce where registers are saved, from the machine | |
8203 | code generated by your compiler. If some registers are not saved, or if | |
8204 | @value{GDBN} is unable to locate the saved registers, the selected stack | |
8205 | frame makes no difference. | |
8206 | ||
6d2ebf8b | 8207 | @node Floating Point Hardware |
79a6e687 | 8208 | @section Floating Point Hardware |
c906108c SS |
8209 | @cindex floating point |
8210 | ||
8211 | Depending on the configuration, @value{GDBN} may be able to give | |
8212 | you more information about the status of the floating point hardware. | |
8213 | ||
8214 | @table @code | |
8215 | @kindex info float | |
8216 | @item info float | |
8217 | Display hardware-dependent information about the floating | |
8218 | point unit. The exact contents and layout vary depending on the | |
8219 | floating point chip. Currently, @samp{info float} is supported on | |
8220 | the ARM and x86 machines. | |
8221 | @end table | |
c906108c | 8222 | |
e76f1f2e AC |
8223 | @node Vector Unit |
8224 | @section Vector Unit | |
8225 | @cindex vector unit | |
8226 | ||
8227 | Depending on the configuration, @value{GDBN} may be able to give you | |
8228 | more information about the status of the vector unit. | |
8229 | ||
8230 | @table @code | |
8231 | @kindex info vector | |
8232 | @item info vector | |
8233 | Display information about the vector unit. The exact contents and | |
8234 | layout vary depending on the hardware. | |
8235 | @end table | |
8236 | ||
721c2651 | 8237 | @node OS Information |
79a6e687 | 8238 | @section Operating System Auxiliary Information |
721c2651 EZ |
8239 | @cindex OS information |
8240 | ||
8241 | @value{GDBN} provides interfaces to useful OS facilities that can help | |
8242 | you debug your program. | |
8243 | ||
8244 | @cindex @code{ptrace} system call | |
8245 | @cindex @code{struct user} contents | |
8246 | When @value{GDBN} runs on a @dfn{Posix system} (such as GNU or Unix | |
8247 | machines), it interfaces with the inferior via the @code{ptrace} | |
8248 | system call. The operating system creates a special sata structure, | |
8249 | called @code{struct user}, for this interface. You can use the | |
8250 | command @code{info udot} to display the contents of this data | |
8251 | structure. | |
8252 | ||
8253 | @table @code | |
8254 | @item info udot | |
8255 | @kindex info udot | |
8256 | Display the contents of the @code{struct user} maintained by the OS | |
8257 | kernel for the program being debugged. @value{GDBN} displays the | |
8258 | contents of @code{struct user} as a list of hex numbers, similar to | |
8259 | the @code{examine} command. | |
8260 | @end table | |
8261 | ||
b383017d RM |
8262 | @cindex auxiliary vector |
8263 | @cindex vector, auxiliary | |
b383017d RM |
8264 | Some operating systems supply an @dfn{auxiliary vector} to programs at |
8265 | startup. This is akin to the arguments and environment that you | |
8266 | specify for a program, but contains a system-dependent variety of | |
8267 | binary values that tell system libraries important details about the | |
8268 | hardware, operating system, and process. Each value's purpose is | |
8269 | identified by an integer tag; the meanings are well-known but system-specific. | |
8270 | Depending on the configuration and operating system facilities, | |
9c16f35a EZ |
8271 | @value{GDBN} may be able to show you this information. For remote |
8272 | targets, this functionality may further depend on the remote stub's | |
427c3a89 DJ |
8273 | support of the @samp{qXfer:auxv:read} packet, see |
8274 | @ref{qXfer auxiliary vector read}. | |
b383017d RM |
8275 | |
8276 | @table @code | |
8277 | @kindex info auxv | |
8278 | @item info auxv | |
8279 | Display the auxiliary vector of the inferior, which can be either a | |
e4937fc1 | 8280 | live process or a core dump file. @value{GDBN} prints each tag value |
b383017d RM |
8281 | numerically, and also shows names and text descriptions for recognized |
8282 | tags. Some values in the vector are numbers, some bit masks, and some | |
e4937fc1 | 8283 | pointers to strings or other data. @value{GDBN} displays each value in the |
b383017d RM |
8284 | most appropriate form for a recognized tag, and in hexadecimal for |
8285 | an unrecognized tag. | |
8286 | @end table | |
8287 | ||
07e059b5 VP |
8288 | On some targets, @value{GDBN} can access operating-system-specific information |
8289 | and display it to user, without interpretation. For remote targets, | |
8290 | this functionality depends on the remote stub's support of the | |
8291 | @samp{qXfer:osdata:read} packet, see @ref{qXfer osdata read}. | |
8292 | ||
8293 | @table @code | |
8294 | @kindex info os processes | |
8295 | @item info os processes | |
8296 | Display the list of processes on the target. For each process, | |
8297 | @value{GDBN} prints the process identifier, the name of the user, and | |
8298 | the command corresponding to the process. | |
8299 | @end table | |
721c2651 | 8300 | |
29e57380 | 8301 | @node Memory Region Attributes |
79a6e687 | 8302 | @section Memory Region Attributes |
29e57380 C |
8303 | @cindex memory region attributes |
8304 | ||
b383017d | 8305 | @dfn{Memory region attributes} allow you to describe special handling |
fd79ecee DJ |
8306 | required by regions of your target's memory. @value{GDBN} uses |
8307 | attributes to determine whether to allow certain types of memory | |
8308 | accesses; whether to use specific width accesses; and whether to cache | |
8309 | target memory. By default the description of memory regions is | |
8310 | fetched from the target (if the current target supports this), but the | |
8311 | user can override the fetched regions. | |
29e57380 C |
8312 | |
8313 | Defined memory regions can be individually enabled and disabled. When a | |
8314 | memory region is disabled, @value{GDBN} uses the default attributes when | |
8315 | accessing memory in that region. Similarly, if no memory regions have | |
8316 | been defined, @value{GDBN} uses the default attributes when accessing | |
8317 | all memory. | |
8318 | ||
b383017d | 8319 | When a memory region is defined, it is given a number to identify it; |
29e57380 C |
8320 | to enable, disable, or remove a memory region, you specify that number. |
8321 | ||
8322 | @table @code | |
8323 | @kindex mem | |
bfac230e | 8324 | @item mem @var{lower} @var{upper} @var{attributes}@dots{} |
09d4efe1 EZ |
8325 | Define a memory region bounded by @var{lower} and @var{upper} with |
8326 | attributes @var{attributes}@dots{}, and add it to the list of regions | |
8327 | monitored by @value{GDBN}. Note that @var{upper} == 0 is a special | |
d3e8051b | 8328 | case: it is treated as the target's maximum memory address. |
bfac230e | 8329 | (0xffff on 16 bit targets, 0xffffffff on 32 bit targets, etc.) |
29e57380 | 8330 | |
fd79ecee DJ |
8331 | @item mem auto |
8332 | Discard any user changes to the memory regions and use target-supplied | |
8333 | regions, if available, or no regions if the target does not support. | |
8334 | ||
29e57380 C |
8335 | @kindex delete mem |
8336 | @item delete mem @var{nums}@dots{} | |
09d4efe1 EZ |
8337 | Remove memory regions @var{nums}@dots{} from the list of regions |
8338 | monitored by @value{GDBN}. | |
29e57380 C |
8339 | |
8340 | @kindex disable mem | |
8341 | @item disable mem @var{nums}@dots{} | |
09d4efe1 | 8342 | Disable monitoring of memory regions @var{nums}@dots{}. |
b383017d | 8343 | A disabled memory region is not forgotten. |
29e57380 C |
8344 | It may be enabled again later. |
8345 | ||
8346 | @kindex enable mem | |
8347 | @item enable mem @var{nums}@dots{} | |
09d4efe1 | 8348 | Enable monitoring of memory regions @var{nums}@dots{}. |
29e57380 C |
8349 | |
8350 | @kindex info mem | |
8351 | @item info mem | |
8352 | Print a table of all defined memory regions, with the following columns | |
09d4efe1 | 8353 | for each region: |
29e57380 C |
8354 | |
8355 | @table @emph | |
8356 | @item Memory Region Number | |
8357 | @item Enabled or Disabled. | |
b383017d | 8358 | Enabled memory regions are marked with @samp{y}. |
29e57380 C |
8359 | Disabled memory regions are marked with @samp{n}. |
8360 | ||
8361 | @item Lo Address | |
8362 | The address defining the inclusive lower bound of the memory region. | |
8363 | ||
8364 | @item Hi Address | |
8365 | The address defining the exclusive upper bound of the memory region. | |
8366 | ||
8367 | @item Attributes | |
8368 | The list of attributes set for this memory region. | |
8369 | @end table | |
8370 | @end table | |
8371 | ||
8372 | ||
8373 | @subsection Attributes | |
8374 | ||
b383017d | 8375 | @subsubsection Memory Access Mode |
29e57380 C |
8376 | The access mode attributes set whether @value{GDBN} may make read or |
8377 | write accesses to a memory region. | |
8378 | ||
8379 | While these attributes prevent @value{GDBN} from performing invalid | |
8380 | memory accesses, they do nothing to prevent the target system, I/O DMA, | |
359df76b | 8381 | etc.@: from accessing memory. |
29e57380 C |
8382 | |
8383 | @table @code | |
8384 | @item ro | |
8385 | Memory is read only. | |
8386 | @item wo | |
8387 | Memory is write only. | |
8388 | @item rw | |
6ca652b0 | 8389 | Memory is read/write. This is the default. |
29e57380 C |
8390 | @end table |
8391 | ||
8392 | @subsubsection Memory Access Size | |
d3e8051b | 8393 | The access size attribute tells @value{GDBN} to use specific sized |
29e57380 C |
8394 | accesses in the memory region. Often memory mapped device registers |
8395 | require specific sized accesses. If no access size attribute is | |
8396 | specified, @value{GDBN} may use accesses of any size. | |
8397 | ||
8398 | @table @code | |
8399 | @item 8 | |
8400 | Use 8 bit memory accesses. | |
8401 | @item 16 | |
8402 | Use 16 bit memory accesses. | |
8403 | @item 32 | |
8404 | Use 32 bit memory accesses. | |
8405 | @item 64 | |
8406 | Use 64 bit memory accesses. | |
8407 | @end table | |
8408 | ||
8409 | @c @subsubsection Hardware/Software Breakpoints | |
8410 | @c The hardware/software breakpoint attributes set whether @value{GDBN} | |
8411 | @c will use hardware or software breakpoints for the internal breakpoints | |
8412 | @c used by the step, next, finish, until, etc. commands. | |
8413 | @c | |
8414 | @c @table @code | |
8415 | @c @item hwbreak | |
b383017d | 8416 | @c Always use hardware breakpoints |
29e57380 C |
8417 | @c @item swbreak (default) |
8418 | @c @end table | |
8419 | ||
8420 | @subsubsection Data Cache | |
8421 | The data cache attributes set whether @value{GDBN} will cache target | |
8422 | memory. While this generally improves performance by reducing debug | |
8423 | protocol overhead, it can lead to incorrect results because @value{GDBN} | |
8424 | does not know about volatile variables or memory mapped device | |
8425 | registers. | |
8426 | ||
8427 | @table @code | |
8428 | @item cache | |
b383017d | 8429 | Enable @value{GDBN} to cache target memory. |
6ca652b0 EZ |
8430 | @item nocache |
8431 | Disable @value{GDBN} from caching target memory. This is the default. | |
29e57380 C |
8432 | @end table |
8433 | ||
4b5752d0 VP |
8434 | @subsection Memory Access Checking |
8435 | @value{GDBN} can be instructed to refuse accesses to memory that is | |
8436 | not explicitly described. This can be useful if accessing such | |
8437 | regions has undesired effects for a specific target, or to provide | |
8438 | better error checking. The following commands control this behaviour. | |
8439 | ||
8440 | @table @code | |
8441 | @kindex set mem inaccessible-by-default | |
8442 | @item set mem inaccessible-by-default [on|off] | |
8443 | If @code{on} is specified, make @value{GDBN} treat memory not | |
8444 | explicitly described by the memory ranges as non-existent and refuse accesses | |
8445 | to such memory. The checks are only performed if there's at least one | |
8446 | memory range defined. If @code{off} is specified, make @value{GDBN} | |
8447 | treat the memory not explicitly described by the memory ranges as RAM. | |
56cf5405 | 8448 | The default value is @code{on}. |
4b5752d0 VP |
8449 | @kindex show mem inaccessible-by-default |
8450 | @item show mem inaccessible-by-default | |
8451 | Show the current handling of accesses to unknown memory. | |
8452 | @end table | |
8453 | ||
8454 | ||
29e57380 | 8455 | @c @subsubsection Memory Write Verification |
b383017d | 8456 | @c The memory write verification attributes set whether @value{GDBN} |
29e57380 C |
8457 | @c will re-reads data after each write to verify the write was successful. |
8458 | @c | |
8459 | @c @table @code | |
8460 | @c @item verify | |
8461 | @c @item noverify (default) | |
8462 | @c @end table | |
8463 | ||
16d9dec6 | 8464 | @node Dump/Restore Files |
79a6e687 | 8465 | @section Copy Between Memory and a File |
16d9dec6 MS |
8466 | @cindex dump/restore files |
8467 | @cindex append data to a file | |
8468 | @cindex dump data to a file | |
8469 | @cindex restore data from a file | |
16d9dec6 | 8470 | |
df5215a6 JB |
8471 | You can use the commands @code{dump}, @code{append}, and |
8472 | @code{restore} to copy data between target memory and a file. The | |
8473 | @code{dump} and @code{append} commands write data to a file, and the | |
8474 | @code{restore} command reads data from a file back into the inferior's | |
8475 | memory. Files may be in binary, Motorola S-record, Intel hex, or | |
8476 | Tektronix Hex format; however, @value{GDBN} can only append to binary | |
8477 | files. | |
8478 | ||
8479 | @table @code | |
8480 | ||
8481 | @kindex dump | |
8482 | @item dump @r{[}@var{format}@r{]} memory @var{filename} @var{start_addr} @var{end_addr} | |
8483 | @itemx dump @r{[}@var{format}@r{]} value @var{filename} @var{expr} | |
8484 | Dump the contents of memory from @var{start_addr} to @var{end_addr}, | |
8485 | or the value of @var{expr}, to @var{filename} in the given format. | |
16d9dec6 | 8486 | |
df5215a6 | 8487 | The @var{format} parameter may be any one of: |
16d9dec6 | 8488 | @table @code |
df5215a6 JB |
8489 | @item binary |
8490 | Raw binary form. | |
8491 | @item ihex | |
8492 | Intel hex format. | |
8493 | @item srec | |
8494 | Motorola S-record format. | |
8495 | @item tekhex | |
8496 | Tektronix Hex format. | |
8497 | @end table | |
8498 | ||
8499 | @value{GDBN} uses the same definitions of these formats as the | |
8500 | @sc{gnu} binary utilities, like @samp{objdump} and @samp{objcopy}. If | |
8501 | @var{format} is omitted, @value{GDBN} dumps the data in raw binary | |
8502 | form. | |
8503 | ||
8504 | @kindex append | |
8505 | @item append @r{[}binary@r{]} memory @var{filename} @var{start_addr} @var{end_addr} | |
8506 | @itemx append @r{[}binary@r{]} value @var{filename} @var{expr} | |
8507 | Append the contents of memory from @var{start_addr} to @var{end_addr}, | |
09d4efe1 | 8508 | or the value of @var{expr}, to the file @var{filename}, in raw binary form. |
df5215a6 JB |
8509 | (@value{GDBN} can only append data to files in raw binary form.) |
8510 | ||
8511 | @kindex restore | |
8512 | @item restore @var{filename} @r{[}binary@r{]} @var{bias} @var{start} @var{end} | |
8513 | Restore the contents of file @var{filename} into memory. The | |
8514 | @code{restore} command can automatically recognize any known @sc{bfd} | |
8515 | file format, except for raw binary. To restore a raw binary file you | |
8516 | must specify the optional keyword @code{binary} after the filename. | |
16d9dec6 | 8517 | |
b383017d | 8518 | If @var{bias} is non-zero, its value will be added to the addresses |
16d9dec6 MS |
8519 | contained in the file. Binary files always start at address zero, so |
8520 | they will be restored at address @var{bias}. Other bfd files have | |
8521 | a built-in location; they will be restored at offset @var{bias} | |
8522 | from that location. | |
8523 | ||
8524 | If @var{start} and/or @var{end} are non-zero, then only data between | |
8525 | file offset @var{start} and file offset @var{end} will be restored. | |
b383017d | 8526 | These offsets are relative to the addresses in the file, before |
16d9dec6 MS |
8527 | the @var{bias} argument is applied. |
8528 | ||
8529 | @end table | |
8530 | ||
384ee23f EZ |
8531 | @node Core File Generation |
8532 | @section How to Produce a Core File from Your Program | |
8533 | @cindex dump core from inferior | |
8534 | ||
8535 | A @dfn{core file} or @dfn{core dump} is a file that records the memory | |
8536 | image of a running process and its process status (register values | |
8537 | etc.). Its primary use is post-mortem debugging of a program that | |
8538 | crashed while it ran outside a debugger. A program that crashes | |
8539 | automatically produces a core file, unless this feature is disabled by | |
8540 | the user. @xref{Files}, for information on invoking @value{GDBN} in | |
8541 | the post-mortem debugging mode. | |
8542 | ||
8543 | Occasionally, you may wish to produce a core file of the program you | |
8544 | are debugging in order to preserve a snapshot of its state. | |
8545 | @value{GDBN} has a special command for that. | |
8546 | ||
8547 | @table @code | |
8548 | @kindex gcore | |
8549 | @kindex generate-core-file | |
8550 | @item generate-core-file [@var{file}] | |
8551 | @itemx gcore [@var{file}] | |
8552 | Produce a core dump of the inferior process. The optional argument | |
8553 | @var{file} specifies the file name where to put the core dump. If not | |
8554 | specified, the file name defaults to @file{core.@var{pid}}, where | |
8555 | @var{pid} is the inferior process ID. | |
8556 | ||
8557 | Note that this command is implemented only for some systems (as of | |
8558 | this writing, @sc{gnu}/Linux, FreeBSD, Solaris, Unixware, and S390). | |
8559 | @end table | |
8560 | ||
a0eb71c5 KB |
8561 | @node Character Sets |
8562 | @section Character Sets | |
8563 | @cindex character sets | |
8564 | @cindex charset | |
8565 | @cindex translating between character sets | |
8566 | @cindex host character set | |
8567 | @cindex target character set | |
8568 | ||
8569 | If the program you are debugging uses a different character set to | |
8570 | represent characters and strings than the one @value{GDBN} uses itself, | |
8571 | @value{GDBN} can automatically translate between the character sets for | |
8572 | you. The character set @value{GDBN} uses we call the @dfn{host | |
8573 | character set}; the one the inferior program uses we call the | |
8574 | @dfn{target character set}. | |
8575 | ||
8576 | For example, if you are running @value{GDBN} on a @sc{gnu}/Linux system, which | |
8577 | uses the ISO Latin 1 character set, but you are using @value{GDBN}'s | |
ea35711c | 8578 | remote protocol (@pxref{Remote Debugging}) to debug a program |
a0eb71c5 KB |
8579 | running on an IBM mainframe, which uses the @sc{ebcdic} character set, |
8580 | then the host character set is Latin-1, and the target character set is | |
8581 | @sc{ebcdic}. If you give @value{GDBN} the command @code{set | |
e33d66ec | 8582 | target-charset EBCDIC-US}, then @value{GDBN} translates between |
a0eb71c5 KB |
8583 | @sc{ebcdic} and Latin 1 as you print character or string values, or use |
8584 | character and string literals in expressions. | |
8585 | ||
8586 | @value{GDBN} has no way to automatically recognize which character set | |
8587 | the inferior program uses; you must tell it, using the @code{set | |
8588 | target-charset} command, described below. | |
8589 | ||
8590 | Here are the commands for controlling @value{GDBN}'s character set | |
8591 | support: | |
8592 | ||
8593 | @table @code | |
8594 | @item set target-charset @var{charset} | |
8595 | @kindex set target-charset | |
10af6951 EZ |
8596 | Set the current target character set to @var{charset}. To display the |
8597 | list of supported target character sets, type | |
8598 | @kbd{@w{set target-charset @key{TAB}@key{TAB}}}. | |
a0eb71c5 | 8599 | |
a0eb71c5 KB |
8600 | @item set host-charset @var{charset} |
8601 | @kindex set host-charset | |
8602 | Set the current host character set to @var{charset}. | |
8603 | ||
8604 | By default, @value{GDBN} uses a host character set appropriate to the | |
8605 | system it is running on; you can override that default using the | |
732f6a93 TT |
8606 | @code{set host-charset} command. On some systems, @value{GDBN} cannot |
8607 | automatically determine the appropriate host character set. In this | |
8608 | case, @value{GDBN} uses @samp{UTF-8}. | |
a0eb71c5 KB |
8609 | |
8610 | @value{GDBN} can only use certain character sets as its host character | |
10af6951 EZ |
8611 | set. If you type @kbd{@w{set target-charset @key{TAB}@key{TAB}}}, |
8612 | @value{GDBN} will list the host character sets it supports. | |
a0eb71c5 KB |
8613 | |
8614 | @item set charset @var{charset} | |
8615 | @kindex set charset | |
e33d66ec | 8616 | Set the current host and target character sets to @var{charset}. As |
10af6951 EZ |
8617 | above, if you type @kbd{@w{set charset @key{TAB}@key{TAB}}}, |
8618 | @value{GDBN} will list the names of the character sets that can be used | |
e33d66ec EZ |
8619 | for both host and target. |
8620 | ||
a0eb71c5 | 8621 | @item show charset |
a0eb71c5 | 8622 | @kindex show charset |
10af6951 | 8623 | Show the names of the current host and target character sets. |
e33d66ec | 8624 | |
10af6951 | 8625 | @item show host-charset |
a0eb71c5 | 8626 | @kindex show host-charset |
10af6951 | 8627 | Show the name of the current host character set. |
e33d66ec | 8628 | |
10af6951 | 8629 | @item show target-charset |
a0eb71c5 | 8630 | @kindex show target-charset |
10af6951 | 8631 | Show the name of the current target character set. |
a0eb71c5 | 8632 | |
10af6951 EZ |
8633 | @item set target-wide-charset @var{charset} |
8634 | @kindex set target-wide-charset | |
8635 | Set the current target's wide character set to @var{charset}. This is | |
8636 | the character set used by the target's @code{wchar_t} type. To | |
8637 | display the list of supported wide character sets, type | |
8638 | @kbd{@w{set target-wide-charset @key{TAB}@key{TAB}}}. | |
8639 | ||
8640 | @item show target-wide-charset | |
8641 | @kindex show target-wide-charset | |
8642 | Show the name of the current target's wide character set. | |
a0eb71c5 KB |
8643 | @end table |
8644 | ||
a0eb71c5 KB |
8645 | Here is an example of @value{GDBN}'s character set support in action. |
8646 | Assume that the following source code has been placed in the file | |
8647 | @file{charset-test.c}: | |
8648 | ||
8649 | @smallexample | |
8650 | #include <stdio.h> | |
8651 | ||
8652 | char ascii_hello[] | |
8653 | = @{72, 101, 108, 108, 111, 44, 32, 119, | |
8654 | 111, 114, 108, 100, 33, 10, 0@}; | |
8655 | char ibm1047_hello[] | |
8656 | = @{200, 133, 147, 147, 150, 107, 64, 166, | |
8657 | 150, 153, 147, 132, 90, 37, 0@}; | |
8658 | ||
8659 | main () | |
8660 | @{ | |
8661 | printf ("Hello, world!\n"); | |
8662 | @} | |
10998722 | 8663 | @end smallexample |
a0eb71c5 KB |
8664 | |
8665 | In this program, @code{ascii_hello} and @code{ibm1047_hello} are arrays | |
8666 | containing the string @samp{Hello, world!} followed by a newline, | |
8667 | encoded in the @sc{ascii} and @sc{ibm1047} character sets. | |
8668 | ||
8669 | We compile the program, and invoke the debugger on it: | |
8670 | ||
8671 | @smallexample | |
8672 | $ gcc -g charset-test.c -o charset-test | |
8673 | $ gdb -nw charset-test | |
8674 | GNU gdb 2001-12-19-cvs | |
8675 | Copyright 2001 Free Software Foundation, Inc. | |
8676 | @dots{} | |
f7dc1244 | 8677 | (@value{GDBP}) |
10998722 | 8678 | @end smallexample |
a0eb71c5 KB |
8679 | |
8680 | We can use the @code{show charset} command to see what character sets | |
8681 | @value{GDBN} is currently using to interpret and display characters and | |
8682 | strings: | |
8683 | ||
8684 | @smallexample | |
f7dc1244 | 8685 | (@value{GDBP}) show charset |
e33d66ec | 8686 | The current host and target character set is `ISO-8859-1'. |
f7dc1244 | 8687 | (@value{GDBP}) |
10998722 | 8688 | @end smallexample |
a0eb71c5 KB |
8689 | |
8690 | For the sake of printing this manual, let's use @sc{ascii} as our | |
8691 | initial character set: | |
8692 | @smallexample | |
f7dc1244 EZ |
8693 | (@value{GDBP}) set charset ASCII |
8694 | (@value{GDBP}) show charset | |
e33d66ec | 8695 | The current host and target character set is `ASCII'. |
f7dc1244 | 8696 | (@value{GDBP}) |
10998722 | 8697 | @end smallexample |
a0eb71c5 KB |
8698 | |
8699 | Let's assume that @sc{ascii} is indeed the correct character set for our | |
8700 | host system --- in other words, let's assume that if @value{GDBN} prints | |
8701 | characters using the @sc{ascii} character set, our terminal will display | |
8702 | them properly. Since our current target character set is also | |
8703 | @sc{ascii}, the contents of @code{ascii_hello} print legibly: | |
8704 | ||
8705 | @smallexample | |
f7dc1244 | 8706 | (@value{GDBP}) print ascii_hello |
a0eb71c5 | 8707 | $1 = 0x401698 "Hello, world!\n" |
f7dc1244 | 8708 | (@value{GDBP}) print ascii_hello[0] |
a0eb71c5 | 8709 | $2 = 72 'H' |
f7dc1244 | 8710 | (@value{GDBP}) |
10998722 | 8711 | @end smallexample |
a0eb71c5 KB |
8712 | |
8713 | @value{GDBN} uses the target character set for character and string | |
8714 | literals you use in expressions: | |
8715 | ||
8716 | @smallexample | |
f7dc1244 | 8717 | (@value{GDBP}) print '+' |
a0eb71c5 | 8718 | $3 = 43 '+' |
f7dc1244 | 8719 | (@value{GDBP}) |
10998722 | 8720 | @end smallexample |
a0eb71c5 KB |
8721 | |
8722 | The @sc{ascii} character set uses the number 43 to encode the @samp{+} | |
8723 | character. | |
8724 | ||
8725 | @value{GDBN} relies on the user to tell it which character set the | |
8726 | target program uses. If we print @code{ibm1047_hello} while our target | |
8727 | character set is still @sc{ascii}, we get jibberish: | |
8728 | ||
8729 | @smallexample | |
f7dc1244 | 8730 | (@value{GDBP}) print ibm1047_hello |
a0eb71c5 | 8731 | $4 = 0x4016a8 "\310\205\223\223\226k@@\246\226\231\223\204Z%" |
f7dc1244 | 8732 | (@value{GDBP}) print ibm1047_hello[0] |
a0eb71c5 | 8733 | $5 = 200 '\310' |
f7dc1244 | 8734 | (@value{GDBP}) |
10998722 | 8735 | @end smallexample |
a0eb71c5 | 8736 | |
e33d66ec | 8737 | If we invoke the @code{set target-charset} followed by @key{TAB}@key{TAB}, |
a0eb71c5 KB |
8738 | @value{GDBN} tells us the character sets it supports: |
8739 | ||
8740 | @smallexample | |
f7dc1244 | 8741 | (@value{GDBP}) set target-charset |
b383017d | 8742 | ASCII EBCDIC-US IBM1047 ISO-8859-1 |
f7dc1244 | 8743 | (@value{GDBP}) set target-charset |
10998722 | 8744 | @end smallexample |
a0eb71c5 KB |
8745 | |
8746 | We can select @sc{ibm1047} as our target character set, and examine the | |
8747 | program's strings again. Now the @sc{ascii} string is wrong, but | |
8748 | @value{GDBN} translates the contents of @code{ibm1047_hello} from the | |
8749 | target character set, @sc{ibm1047}, to the host character set, | |
8750 | @sc{ascii}, and they display correctly: | |
8751 | ||
8752 | @smallexample | |
f7dc1244 EZ |
8753 | (@value{GDBP}) set target-charset IBM1047 |
8754 | (@value{GDBP}) show charset | |
e33d66ec EZ |
8755 | The current host character set is `ASCII'. |
8756 | The current target character set is `IBM1047'. | |
f7dc1244 | 8757 | (@value{GDBP}) print ascii_hello |
a0eb71c5 | 8758 | $6 = 0x401698 "\110\145%%?\054\040\167?\162%\144\041\012" |
f7dc1244 | 8759 | (@value{GDBP}) print ascii_hello[0] |
a0eb71c5 | 8760 | $7 = 72 '\110' |
f7dc1244 | 8761 | (@value{GDBP}) print ibm1047_hello |
a0eb71c5 | 8762 | $8 = 0x4016a8 "Hello, world!\n" |
f7dc1244 | 8763 | (@value{GDBP}) print ibm1047_hello[0] |
a0eb71c5 | 8764 | $9 = 200 'H' |
f7dc1244 | 8765 | (@value{GDBP}) |
10998722 | 8766 | @end smallexample |
a0eb71c5 KB |
8767 | |
8768 | As above, @value{GDBN} uses the target character set for character and | |
8769 | string literals you use in expressions: | |
8770 | ||
8771 | @smallexample | |
f7dc1244 | 8772 | (@value{GDBP}) print '+' |
a0eb71c5 | 8773 | $10 = 78 '+' |
f7dc1244 | 8774 | (@value{GDBP}) |
10998722 | 8775 | @end smallexample |
a0eb71c5 | 8776 | |
e33d66ec | 8777 | The @sc{ibm1047} character set uses the number 78 to encode the @samp{+} |
a0eb71c5 KB |
8778 | character. |
8779 | ||
09d4efe1 EZ |
8780 | @node Caching Remote Data |
8781 | @section Caching Data of Remote Targets | |
8782 | @cindex caching data of remote targets | |
8783 | ||
4e5d721f | 8784 | @value{GDBN} caches data exchanged between the debugger and a |
ea35711c | 8785 | remote target (@pxref{Remote Debugging}). Such caching generally improves |
09d4efe1 | 8786 | performance, because it reduces the overhead of the remote protocol by |
4e5d721f DE |
8787 | bundling memory reads and writes into large chunks. Unfortunately, simply |
8788 | caching everything would lead to incorrect results, since @value{GDBN} | |
8789 | does not necessarily know anything about volatile values, memory-mapped I/O | |
29b090c0 DE |
8790 | addresses, etc. Furthermore, in non-stop mode (@pxref{Non-Stop Mode}) |
8791 | memory can be changed @emph{while} a gdb command is executing. | |
8792 | Therefore, by default, @value{GDBN} only caches data | |
8793 | known to be on the stack@footnote{In non-stop mode, it is moderately | |
8794 | rare for a running thread to modify the stack of a stopped thread | |
8795 | in a way that would interfere with a backtrace, and caching of | |
8796 | stack reads provides a significant speed up of remote backtraces.}. | |
8797 | Other regions of memory can be explicitly marked as | |
4e5d721f | 8798 | cacheable; see @pxref{Memory Region Attributes}. |
09d4efe1 EZ |
8799 | |
8800 | @table @code | |
8801 | @kindex set remotecache | |
8802 | @item set remotecache on | |
8803 | @itemx set remotecache off | |
4e5d721f DE |
8804 | This option no longer does anything; it exists for compatibility |
8805 | with old scripts. | |
09d4efe1 EZ |
8806 | |
8807 | @kindex show remotecache | |
8808 | @item show remotecache | |
4e5d721f DE |
8809 | Show the current state of the obsolete remotecache flag. |
8810 | ||
8811 | @kindex set stack-cache | |
8812 | @item set stack-cache on | |
8813 | @itemx set stack-cache off | |
8814 | Enable or disable caching of stack accesses. When @code{ON}, use | |
8815 | caching. By default, this option is @code{ON}. | |
8816 | ||
8817 | @kindex show stack-cache | |
8818 | @item show stack-cache | |
8819 | Show the current state of data caching for memory accesses. | |
09d4efe1 EZ |
8820 | |
8821 | @kindex info dcache | |
4e5d721f | 8822 | @item info dcache @r{[}line@r{]} |
09d4efe1 | 8823 | Print the information about the data cache performance. The |
4e5d721f DE |
8824 | information displayed includes the dcache width and depth, and for |
8825 | each cache line, its number, address, and how many times it was | |
8826 | referenced. This command is useful for debugging the data cache | |
8827 | operation. | |
8828 | ||
8829 | If a line number is specified, the contents of that line will be | |
8830 | printed in hex. | |
09d4efe1 EZ |
8831 | @end table |
8832 | ||
08388c79 DE |
8833 | @node Searching Memory |
8834 | @section Search Memory | |
8835 | @cindex searching memory | |
8836 | ||
8837 | Memory can be searched for a particular sequence of bytes with the | |
8838 | @code{find} command. | |
8839 | ||
8840 | @table @code | |
8841 | @kindex find | |
8842 | @item find @r{[}/@var{sn}@r{]} @var{start_addr}, +@var{len}, @var{val1} @r{[}, @var{val2}, @dots{}@r{]} | |
8843 | @itemx find @r{[}/@var{sn}@r{]} @var{start_addr}, @var{end_addr}, @var{val1} @r{[}, @var{val2}, @dots{}@r{]} | |
8844 | Search memory for the sequence of bytes specified by @var{val1}, @var{val2}, | |
8845 | etc. The search begins at address @var{start_addr} and continues for either | |
8846 | @var{len} bytes or through to @var{end_addr} inclusive. | |
8847 | @end table | |
8848 | ||
8849 | @var{s} and @var{n} are optional parameters. | |
8850 | They may be specified in either order, apart or together. | |
8851 | ||
8852 | @table @r | |
8853 | @item @var{s}, search query size | |
8854 | The size of each search query value. | |
8855 | ||
8856 | @table @code | |
8857 | @item b | |
8858 | bytes | |
8859 | @item h | |
8860 | halfwords (two bytes) | |
8861 | @item w | |
8862 | words (four bytes) | |
8863 | @item g | |
8864 | giant words (eight bytes) | |
8865 | @end table | |
8866 | ||
8867 | All values are interpreted in the current language. | |
8868 | This means, for example, that if the current source language is C/C@t{++} | |
8869 | then searching for the string ``hello'' includes the trailing '\0'. | |
8870 | ||
8871 | If the value size is not specified, it is taken from the | |
8872 | value's type in the current language. | |
8873 | This is useful when one wants to specify the search | |
8874 | pattern as a mixture of types. | |
8875 | Note that this means, for example, that in the case of C-like languages | |
8876 | a search for an untyped 0x42 will search for @samp{(int) 0x42} | |
8877 | which is typically four bytes. | |
8878 | ||
8879 | @item @var{n}, maximum number of finds | |
8880 | The maximum number of matches to print. The default is to print all finds. | |
8881 | @end table | |
8882 | ||
8883 | You can use strings as search values. Quote them with double-quotes | |
8884 | (@code{"}). | |
8885 | The string value is copied into the search pattern byte by byte, | |
8886 | regardless of the endianness of the target and the size specification. | |
8887 | ||
8888 | The address of each match found is printed as well as a count of the | |
8889 | number of matches found. | |
8890 | ||
8891 | The address of the last value found is stored in convenience variable | |
8892 | @samp{$_}. | |
8893 | A count of the number of matches is stored in @samp{$numfound}. | |
8894 | ||
8895 | For example, if stopped at the @code{printf} in this function: | |
8896 | ||
8897 | @smallexample | |
8898 | void | |
8899 | hello () | |
8900 | @{ | |
8901 | static char hello[] = "hello-hello"; | |
8902 | static struct @{ char c; short s; int i; @} | |
8903 | __attribute__ ((packed)) mixed | |
8904 | = @{ 'c', 0x1234, 0x87654321 @}; | |
8905 | printf ("%s\n", hello); | |
8906 | @} | |
8907 | @end smallexample | |
8908 | ||
8909 | @noindent | |
8910 | you get during debugging: | |
8911 | ||
8912 | @smallexample | |
8913 | (gdb) find &hello[0], +sizeof(hello), "hello" | |
8914 | 0x804956d <hello.1620+6> | |
8915 | 1 pattern found | |
8916 | (gdb) find &hello[0], +sizeof(hello), 'h', 'e', 'l', 'l', 'o' | |
8917 | 0x8049567 <hello.1620> | |
8918 | 0x804956d <hello.1620+6> | |
8919 | 2 patterns found | |
8920 | (gdb) find /b1 &hello[0], +sizeof(hello), 'h', 0x65, 'l' | |
8921 | 0x8049567 <hello.1620> | |
8922 | 1 pattern found | |
8923 | (gdb) find &mixed, +sizeof(mixed), (char) 'c', (short) 0x1234, (int) 0x87654321 | |
8924 | 0x8049560 <mixed.1625> | |
8925 | 1 pattern found | |
8926 | (gdb) print $numfound | |
8927 | $1 = 1 | |
8928 | (gdb) print $_ | |
8929 | $2 = (void *) 0x8049560 | |
8930 | @end smallexample | |
a0eb71c5 | 8931 | |
edb3359d DJ |
8932 | @node Optimized Code |
8933 | @chapter Debugging Optimized Code | |
8934 | @cindex optimized code, debugging | |
8935 | @cindex debugging optimized code | |
8936 | ||
8937 | Almost all compilers support optimization. With optimization | |
8938 | disabled, the compiler generates assembly code that corresponds | |
8939 | directly to your source code, in a simplistic way. As the compiler | |
8940 | applies more powerful optimizations, the generated assembly code | |
8941 | diverges from your original source code. With help from debugging | |
8942 | information generated by the compiler, @value{GDBN} can map from | |
8943 | the running program back to constructs from your original source. | |
8944 | ||
8945 | @value{GDBN} is more accurate with optimization disabled. If you | |
8946 | can recompile without optimization, it is easier to follow the | |
8947 | progress of your program during debugging. But, there are many cases | |
8948 | where you may need to debug an optimized version. | |
8949 | ||
8950 | When you debug a program compiled with @samp{-g -O}, remember that the | |
8951 | optimizer has rearranged your code; the debugger shows you what is | |
8952 | really there. Do not be too surprised when the execution path does not | |
8953 | exactly match your source file! An extreme example: if you define a | |
8954 | variable, but never use it, @value{GDBN} never sees that | |
8955 | variable---because the compiler optimizes it out of existence. | |
8956 | ||
8957 | Some things do not work as well with @samp{-g -O} as with just | |
8958 | @samp{-g}, particularly on machines with instruction scheduling. If in | |
8959 | doubt, recompile with @samp{-g} alone, and if this fixes the problem, | |
8960 | please report it to us as a bug (including a test case!). | |
8961 | @xref{Variables}, for more information about debugging optimized code. | |
8962 | ||
8963 | @menu | |
8964 | * Inline Functions:: How @value{GDBN} presents inlining | |
8965 | @end menu | |
8966 | ||
8967 | @node Inline Functions | |
8968 | @section Inline Functions | |
8969 | @cindex inline functions, debugging | |
8970 | ||
8971 | @dfn{Inlining} is an optimization that inserts a copy of the function | |
8972 | body directly at each call site, instead of jumping to a shared | |
8973 | routine. @value{GDBN} displays inlined functions just like | |
8974 | non-inlined functions. They appear in backtraces. You can view their | |
8975 | arguments and local variables, step into them with @code{step}, skip | |
8976 | them with @code{next}, and escape from them with @code{finish}. | |
8977 | You can check whether a function was inlined by using the | |
8978 | @code{info frame} command. | |
8979 | ||
8980 | For @value{GDBN} to support inlined functions, the compiler must | |
8981 | record information about inlining in the debug information --- | |
8982 | @value{NGCC} using the @sc{dwarf 2} format does this, and several | |
8983 | other compilers do also. @value{GDBN} only supports inlined functions | |
8984 | when using @sc{dwarf 2}. Versions of @value{NGCC} before 4.1 | |
8985 | do not emit two required attributes (@samp{DW_AT_call_file} and | |
8986 | @samp{DW_AT_call_line}); @value{GDBN} does not display inlined | |
8987 | function calls with earlier versions of @value{NGCC}. It instead | |
8988 | displays the arguments and local variables of inlined functions as | |
8989 | local variables in the caller. | |
8990 | ||
8991 | The body of an inlined function is directly included at its call site; | |
8992 | unlike a non-inlined function, there are no instructions devoted to | |
8993 | the call. @value{GDBN} still pretends that the call site and the | |
8994 | start of the inlined function are different instructions. Stepping to | |
8995 | the call site shows the call site, and then stepping again shows | |
8996 | the first line of the inlined function, even though no additional | |
8997 | instructions are executed. | |
8998 | ||
8999 | This makes source-level debugging much clearer; you can see both the | |
9000 | context of the call and then the effect of the call. Only stepping by | |
9001 | a single instruction using @code{stepi} or @code{nexti} does not do | |
9002 | this; single instruction steps always show the inlined body. | |
9003 | ||
9004 | There are some ways that @value{GDBN} does not pretend that inlined | |
9005 | function calls are the same as normal calls: | |
9006 | ||
9007 | @itemize @bullet | |
9008 | @item | |
9009 | You cannot set breakpoints on inlined functions. @value{GDBN} | |
9010 | either reports that there is no symbol with that name, or else sets the | |
9011 | breakpoint only on non-inlined copies of the function. This limitation | |
9012 | will be removed in a future version of @value{GDBN}; until then, | |
9013 | set a breakpoint by line number on the first line of the inlined | |
9014 | function instead. | |
9015 | ||
9016 | @item | |
9017 | Setting breakpoints at the call site of an inlined function may not | |
9018 | work, because the call site does not contain any code. @value{GDBN} | |
9019 | may incorrectly move the breakpoint to the next line of the enclosing | |
9020 | function, after the call. This limitation will be removed in a future | |
9021 | version of @value{GDBN}; until then, set a breakpoint on an earlier line | |
9022 | or inside the inlined function instead. | |
9023 | ||
9024 | @item | |
9025 | @value{GDBN} cannot locate the return value of inlined calls after | |
9026 | using the @code{finish} command. This is a limitation of compiler-generated | |
9027 | debugging information; after @code{finish}, you can step to the next line | |
9028 | and print a variable where your program stored the return value. | |
9029 | ||
9030 | @end itemize | |
9031 | ||
9032 | ||
e2e0bcd1 JB |
9033 | @node Macros |
9034 | @chapter C Preprocessor Macros | |
9035 | ||
49efadf5 | 9036 | Some languages, such as C and C@t{++}, provide a way to define and invoke |
e2e0bcd1 JB |
9037 | ``preprocessor macros'' which expand into strings of tokens. |
9038 | @value{GDBN} can evaluate expressions containing macro invocations, show | |
9039 | the result of macro expansion, and show a macro's definition, including | |
9040 | where it was defined. | |
9041 | ||
9042 | You may need to compile your program specially to provide @value{GDBN} | |
9043 | with information about preprocessor macros. Most compilers do not | |
9044 | include macros in their debugging information, even when you compile | |
9045 | with the @option{-g} flag. @xref{Compilation}. | |
9046 | ||
9047 | A program may define a macro at one point, remove that definition later, | |
9048 | and then provide a different definition after that. Thus, at different | |
9049 | points in the program, a macro may have different definitions, or have | |
9050 | no definition at all. If there is a current stack frame, @value{GDBN} | |
9051 | uses the macros in scope at that frame's source code line. Otherwise, | |
9052 | @value{GDBN} uses the macros in scope at the current listing location; | |
9053 | see @ref{List}. | |
9054 | ||
e2e0bcd1 JB |
9055 | Whenever @value{GDBN} evaluates an expression, it always expands any |
9056 | macro invocations present in the expression. @value{GDBN} also provides | |
9057 | the following commands for working with macros explicitly. | |
9058 | ||
9059 | @table @code | |
9060 | ||
9061 | @kindex macro expand | |
9062 | @cindex macro expansion, showing the results of preprocessor | |
9063 | @cindex preprocessor macro expansion, showing the results of | |
9064 | @cindex expanding preprocessor macros | |
9065 | @item macro expand @var{expression} | |
9066 | @itemx macro exp @var{expression} | |
9067 | Show the results of expanding all preprocessor macro invocations in | |
9068 | @var{expression}. Since @value{GDBN} simply expands macros, but does | |
9069 | not parse the result, @var{expression} need not be a valid expression; | |
9070 | it can be any string of tokens. | |
9071 | ||
09d4efe1 | 9072 | @kindex macro exp1 |
e2e0bcd1 JB |
9073 | @item macro expand-once @var{expression} |
9074 | @itemx macro exp1 @var{expression} | |
4644b6e3 | 9075 | @cindex expand macro once |
e2e0bcd1 JB |
9076 | @i{(This command is not yet implemented.)} Show the results of |
9077 | expanding those preprocessor macro invocations that appear explicitly in | |
9078 | @var{expression}. Macro invocations appearing in that expansion are | |
9079 | left unchanged. This command allows you to see the effect of a | |
9080 | particular macro more clearly, without being confused by further | |
9081 | expansions. Since @value{GDBN} simply expands macros, but does not | |
9082 | parse the result, @var{expression} need not be a valid expression; it | |
9083 | can be any string of tokens. | |
9084 | ||
475b0867 | 9085 | @kindex info macro |
e2e0bcd1 JB |
9086 | @cindex macro definition, showing |
9087 | @cindex definition, showing a macro's | |
475b0867 | 9088 | @item info macro @var{macro} |
e2e0bcd1 | 9089 | Show the definition of the macro named @var{macro}, and describe the |
484086b7 | 9090 | source location or compiler command-line where that definition was established. |
e2e0bcd1 JB |
9091 | |
9092 | @kindex macro define | |
9093 | @cindex user-defined macros | |
9094 | @cindex defining macros interactively | |
9095 | @cindex macros, user-defined | |
9096 | @item macro define @var{macro} @var{replacement-list} | |
9097 | @itemx macro define @var{macro}(@var{arglist}) @var{replacement-list} | |
d7d9f01e TT |
9098 | Introduce a definition for a preprocessor macro named @var{macro}, |
9099 | invocations of which are replaced by the tokens given in | |
9100 | @var{replacement-list}. The first form of this command defines an | |
9101 | ``object-like'' macro, which takes no arguments; the second form | |
9102 | defines a ``function-like'' macro, which takes the arguments given in | |
9103 | @var{arglist}. | |
9104 | ||
9105 | A definition introduced by this command is in scope in every | |
9106 | expression evaluated in @value{GDBN}, until it is removed with the | |
9107 | @code{macro undef} command, described below. The definition overrides | |
9108 | all definitions for @var{macro} present in the program being debugged, | |
9109 | as well as any previous user-supplied definition. | |
e2e0bcd1 JB |
9110 | |
9111 | @kindex macro undef | |
9112 | @item macro undef @var{macro} | |
d7d9f01e TT |
9113 | Remove any user-supplied definition for the macro named @var{macro}. |
9114 | This command only affects definitions provided with the @code{macro | |
9115 | define} command, described above; it cannot remove definitions present | |
9116 | in the program being debugged. | |
e2e0bcd1 | 9117 | |
09d4efe1 EZ |
9118 | @kindex macro list |
9119 | @item macro list | |
d7d9f01e | 9120 | List all the macros defined using the @code{macro define} command. |
e2e0bcd1 JB |
9121 | @end table |
9122 | ||
9123 | @cindex macros, example of debugging with | |
9124 | Here is a transcript showing the above commands in action. First, we | |
9125 | show our source files: | |
9126 | ||
9127 | @smallexample | |
9128 | $ cat sample.c | |
9129 | #include <stdio.h> | |
9130 | #include "sample.h" | |
9131 | ||
9132 | #define M 42 | |
9133 | #define ADD(x) (M + x) | |
9134 | ||
9135 | main () | |
9136 | @{ | |
9137 | #define N 28 | |
9138 | printf ("Hello, world!\n"); | |
9139 | #undef N | |
9140 | printf ("We're so creative.\n"); | |
9141 | #define N 1729 | |
9142 | printf ("Goodbye, world!\n"); | |
9143 | @} | |
9144 | $ cat sample.h | |
9145 | #define Q < | |
9146 | $ | |
9147 | @end smallexample | |
9148 | ||
9149 | Now, we compile the program using the @sc{gnu} C compiler, @value{NGCC}. | |
9150 | We pass the @option{-gdwarf-2} and @option{-g3} flags to ensure the | |
9151 | compiler includes information about preprocessor macros in the debugging | |
9152 | information. | |
9153 | ||
9154 | @smallexample | |
9155 | $ gcc -gdwarf-2 -g3 sample.c -o sample | |
9156 | $ | |
9157 | @end smallexample | |
9158 | ||
9159 | Now, we start @value{GDBN} on our sample program: | |
9160 | ||
9161 | @smallexample | |
9162 | $ gdb -nw sample | |
9163 | GNU gdb 2002-05-06-cvs | |
9164 | Copyright 2002 Free Software Foundation, Inc. | |
9165 | GDB is free software, @dots{} | |
f7dc1244 | 9166 | (@value{GDBP}) |
e2e0bcd1 JB |
9167 | @end smallexample |
9168 | ||
9169 | We can expand macros and examine their definitions, even when the | |
9170 | program is not running. @value{GDBN} uses the current listing position | |
9171 | to decide which macro definitions are in scope: | |
9172 | ||
9173 | @smallexample | |
f7dc1244 | 9174 | (@value{GDBP}) list main |
e2e0bcd1 JB |
9175 | 3 |
9176 | 4 #define M 42 | |
9177 | 5 #define ADD(x) (M + x) | |
9178 | 6 | |
9179 | 7 main () | |
9180 | 8 @{ | |
9181 | 9 #define N 28 | |
9182 | 10 printf ("Hello, world!\n"); | |
9183 | 11 #undef N | |
9184 | 12 printf ("We're so creative.\n"); | |
f7dc1244 | 9185 | (@value{GDBP}) info macro ADD |
e2e0bcd1 JB |
9186 | Defined at /home/jimb/gdb/macros/play/sample.c:5 |
9187 | #define ADD(x) (M + x) | |
f7dc1244 | 9188 | (@value{GDBP}) info macro Q |
e2e0bcd1 JB |
9189 | Defined at /home/jimb/gdb/macros/play/sample.h:1 |
9190 | included at /home/jimb/gdb/macros/play/sample.c:2 | |
9191 | #define Q < | |
f7dc1244 | 9192 | (@value{GDBP}) macro expand ADD(1) |
e2e0bcd1 | 9193 | expands to: (42 + 1) |
f7dc1244 | 9194 | (@value{GDBP}) macro expand-once ADD(1) |
e2e0bcd1 | 9195 | expands to: once (M + 1) |
f7dc1244 | 9196 | (@value{GDBP}) |
e2e0bcd1 JB |
9197 | @end smallexample |
9198 | ||
d7d9f01e | 9199 | In the example above, note that @code{macro expand-once} expands only |
e2e0bcd1 JB |
9200 | the macro invocation explicit in the original text --- the invocation of |
9201 | @code{ADD} --- but does not expand the invocation of the macro @code{M}, | |
9202 | which was introduced by @code{ADD}. | |
9203 | ||
3f94c067 BW |
9204 | Once the program is running, @value{GDBN} uses the macro definitions in |
9205 | force at the source line of the current stack frame: | |
e2e0bcd1 JB |
9206 | |
9207 | @smallexample | |
f7dc1244 | 9208 | (@value{GDBP}) break main |
e2e0bcd1 | 9209 | Breakpoint 1 at 0x8048370: file sample.c, line 10. |
f7dc1244 | 9210 | (@value{GDBP}) run |
b383017d | 9211 | Starting program: /home/jimb/gdb/macros/play/sample |
e2e0bcd1 JB |
9212 | |
9213 | Breakpoint 1, main () at sample.c:10 | |
9214 | 10 printf ("Hello, world!\n"); | |
f7dc1244 | 9215 | (@value{GDBP}) |
e2e0bcd1 JB |
9216 | @end smallexample |
9217 | ||
9218 | At line 10, the definition of the macro @code{N} at line 9 is in force: | |
9219 | ||
9220 | @smallexample | |
f7dc1244 | 9221 | (@value{GDBP}) info macro N |
e2e0bcd1 JB |
9222 | Defined at /home/jimb/gdb/macros/play/sample.c:9 |
9223 | #define N 28 | |
f7dc1244 | 9224 | (@value{GDBP}) macro expand N Q M |
e2e0bcd1 | 9225 | expands to: 28 < 42 |
f7dc1244 | 9226 | (@value{GDBP}) print N Q M |
e2e0bcd1 | 9227 | $1 = 1 |
f7dc1244 | 9228 | (@value{GDBP}) |
e2e0bcd1 JB |
9229 | @end smallexample |
9230 | ||
9231 | As we step over directives that remove @code{N}'s definition, and then | |
9232 | give it a new definition, @value{GDBN} finds the definition (or lack | |
9233 | thereof) in force at each point: | |
9234 | ||
9235 | @smallexample | |
f7dc1244 | 9236 | (@value{GDBP}) next |
e2e0bcd1 JB |
9237 | Hello, world! |
9238 | 12 printf ("We're so creative.\n"); | |
f7dc1244 | 9239 | (@value{GDBP}) info macro N |
e2e0bcd1 JB |
9240 | The symbol `N' has no definition as a C/C++ preprocessor macro |
9241 | at /home/jimb/gdb/macros/play/sample.c:12 | |
f7dc1244 | 9242 | (@value{GDBP}) next |
e2e0bcd1 JB |
9243 | We're so creative. |
9244 | 14 printf ("Goodbye, world!\n"); | |
f7dc1244 | 9245 | (@value{GDBP}) info macro N |
e2e0bcd1 JB |
9246 | Defined at /home/jimb/gdb/macros/play/sample.c:13 |
9247 | #define N 1729 | |
f7dc1244 | 9248 | (@value{GDBP}) macro expand N Q M |
e2e0bcd1 | 9249 | expands to: 1729 < 42 |
f7dc1244 | 9250 | (@value{GDBP}) print N Q M |
e2e0bcd1 | 9251 | $2 = 0 |
f7dc1244 | 9252 | (@value{GDBP}) |
e2e0bcd1 JB |
9253 | @end smallexample |
9254 | ||
484086b7 JK |
9255 | In addition to source files, macros can be defined on the compilation command |
9256 | line using the @option{-D@var{name}=@var{value}} syntax. For macros defined in | |
9257 | such a way, @value{GDBN} displays the location of their definition as line zero | |
9258 | of the source file submitted to the compiler. | |
9259 | ||
9260 | @smallexample | |
9261 | (@value{GDBP}) info macro __STDC__ | |
9262 | Defined at /home/jimb/gdb/macros/play/sample.c:0 | |
9263 | -D__STDC__=1 | |
9264 | (@value{GDBP}) | |
9265 | @end smallexample | |
9266 | ||
e2e0bcd1 | 9267 | |
b37052ae EZ |
9268 | @node Tracepoints |
9269 | @chapter Tracepoints | |
9270 | @c This chapter is based on the documentation written by Michael | |
9271 | @c Snyder, David Taylor, Jim Blandy, and Elena Zannoni. | |
9272 | ||
9273 | @cindex tracepoints | |
9274 | In some applications, it is not feasible for the debugger to interrupt | |
9275 | the program's execution long enough for the developer to learn | |
9276 | anything helpful about its behavior. If the program's correctness | |
9277 | depends on its real-time behavior, delays introduced by a debugger | |
9278 | might cause the program to change its behavior drastically, or perhaps | |
9279 | fail, even when the code itself is correct. It is useful to be able | |
9280 | to observe the program's behavior without interrupting it. | |
9281 | ||
9282 | Using @value{GDBN}'s @code{trace} and @code{collect} commands, you can | |
9283 | specify locations in the program, called @dfn{tracepoints}, and | |
9284 | arbitrary expressions to evaluate when those tracepoints are reached. | |
9285 | Later, using the @code{tfind} command, you can examine the values | |
9286 | those expressions had when the program hit the tracepoints. The | |
9287 | expressions may also denote objects in memory---structures or arrays, | |
9288 | for example---whose values @value{GDBN} should record; while visiting | |
9289 | a particular tracepoint, you may inspect those objects as if they were | |
9290 | in memory at that moment. However, because @value{GDBN} records these | |
9291 | values without interacting with you, it can do so quickly and | |
9292 | unobtrusively, hopefully not disturbing the program's behavior. | |
9293 | ||
9294 | The tracepoint facility is currently available only for remote | |
9d29849a JB |
9295 | targets. @xref{Targets}. In addition, your remote target must know |
9296 | how to collect trace data. This functionality is implemented in the | |
9297 | remote stub; however, none of the stubs distributed with @value{GDBN} | |
9298 | support tracepoints as of this writing. The format of the remote | |
9299 | packets used to implement tracepoints are described in @ref{Tracepoint | |
9300 | Packets}. | |
b37052ae | 9301 | |
00bf0b85 SS |
9302 | It is also possible to get trace data from a file, in a manner reminiscent |
9303 | of corefiles; you specify the filename, and use @code{tfind} to search | |
9304 | through the file. @xref{Trace Files}, for more details. | |
9305 | ||
b37052ae EZ |
9306 | This chapter describes the tracepoint commands and features. |
9307 | ||
9308 | @menu | |
b383017d RM |
9309 | * Set Tracepoints:: |
9310 | * Analyze Collected Data:: | |
9311 | * Tracepoint Variables:: | |
00bf0b85 | 9312 | * Trace Files:: |
b37052ae EZ |
9313 | @end menu |
9314 | ||
9315 | @node Set Tracepoints | |
9316 | @section Commands to Set Tracepoints | |
9317 | ||
9318 | Before running such a @dfn{trace experiment}, an arbitrary number of | |
1042e4c0 SS |
9319 | tracepoints can be set. A tracepoint is actually a special type of |
9320 | breakpoint (@pxref{Set Breaks}), so you can manipulate it using | |
9321 | standard breakpoint commands. For instance, as with breakpoints, | |
9322 | tracepoint numbers are successive integers starting from one, and many | |
9323 | of the commands associated with tracepoints take the tracepoint number | |
9324 | as their argument, to identify which tracepoint to work on. | |
b37052ae EZ |
9325 | |
9326 | For each tracepoint, you can specify, in advance, some arbitrary set | |
9327 | of data that you want the target to collect in the trace buffer when | |
9328 | it hits that tracepoint. The collected data can include registers, | |
9329 | local variables, or global data. Later, you can use @value{GDBN} | |
9330 | commands to examine the values these data had at the time the | |
9331 | tracepoint was hit. | |
9332 | ||
1042e4c0 SS |
9333 | Tracepoints do not support every breakpoint feature. Conditional |
9334 | expressions and ignore counts on tracepoints have no effect, and | |
9335 | tracepoints cannot run @value{GDBN} commands when they are | |
9336 | hit. Tracepoints may not be thread-specific either. | |
9337 | ||
7a697b8d SS |
9338 | @cindex fast tracepoints |
9339 | Some targets may support @dfn{fast tracepoints}, which are inserted in | |
9340 | a different way (such as with a jump instead of a trap), that is | |
9341 | faster but possibly restricted in where they may be installed. | |
9342 | ||
b37052ae EZ |
9343 | This section describes commands to set tracepoints and associated |
9344 | conditions and actions. | |
9345 | ||
9346 | @menu | |
b383017d RM |
9347 | * Create and Delete Tracepoints:: |
9348 | * Enable and Disable Tracepoints:: | |
9349 | * Tracepoint Passcounts:: | |
782b2b07 | 9350 | * Tracepoint Conditions:: |
f61e138d | 9351 | * Trace State Variables:: |
b383017d RM |
9352 | * Tracepoint Actions:: |
9353 | * Listing Tracepoints:: | |
79a6e687 | 9354 | * Starting and Stopping Trace Experiments:: |
b37052ae EZ |
9355 | @end menu |
9356 | ||
9357 | @node Create and Delete Tracepoints | |
9358 | @subsection Create and Delete Tracepoints | |
9359 | ||
9360 | @table @code | |
9361 | @cindex set tracepoint | |
9362 | @kindex trace | |
1042e4c0 | 9363 | @item trace @var{location} |
b37052ae | 9364 | The @code{trace} command is very similar to the @code{break} command. |
1042e4c0 SS |
9365 | Its argument @var{location} can be a source line, a function name, or |
9366 | an address in the target program. @xref{Specify Location}. The | |
9367 | @code{trace} command defines a tracepoint, which is a point in the | |
9368 | target program where the debugger will briefly stop, collect some | |
9369 | data, and then allow the program to continue. Setting a tracepoint or | |
9370 | changing its actions doesn't take effect until the next @code{tstart} | |
9371 | command, and once a trace experiment is running, further changes will | |
9372 | not have any effect until the next trace experiment starts. | |
b37052ae EZ |
9373 | |
9374 | Here are some examples of using the @code{trace} command: | |
9375 | ||
9376 | @smallexample | |
9377 | (@value{GDBP}) @b{trace foo.c:121} // a source file and line number | |
9378 | ||
9379 | (@value{GDBP}) @b{trace +2} // 2 lines forward | |
9380 | ||
9381 | (@value{GDBP}) @b{trace my_function} // first source line of function | |
9382 | ||
9383 | (@value{GDBP}) @b{trace *my_function} // EXACT start address of function | |
9384 | ||
9385 | (@value{GDBP}) @b{trace *0x2117c4} // an address | |
9386 | @end smallexample | |
9387 | ||
9388 | @noindent | |
9389 | You can abbreviate @code{trace} as @code{tr}. | |
9390 | ||
782b2b07 SS |
9391 | @item trace @var{location} if @var{cond} |
9392 | Set a tracepoint with condition @var{cond}; evaluate the expression | |
9393 | @var{cond} each time the tracepoint is reached, and collect data only | |
9394 | if the value is nonzero---that is, if @var{cond} evaluates as true. | |
9395 | @xref{Tracepoint Conditions, ,Tracepoint Conditions}, for more | |
9396 | information on tracepoint conditions. | |
9397 | ||
7a697b8d SS |
9398 | @item ftrace @var{location} [ if @var{cond} ] |
9399 | @cindex set fast tracepoint | |
9400 | @kindex ftrace | |
9401 | The @code{ftrace} command sets a fast tracepoint. For targets that | |
9402 | support them, fast tracepoints will use a more efficient but possibly | |
9403 | less general technique to trigger data collection, such as a jump | |
9404 | instruction instead of a trap, or some sort of hardware support. It | |
9405 | may not be possible to create a fast tracepoint at the desired | |
9406 | location, in which case the command will exit with an explanatory | |
9407 | message. | |
9408 | ||
9409 | @value{GDBN} handles arguments to @code{ftrace} exactly as for | |
9410 | @code{trace}. | |
9411 | ||
b37052ae EZ |
9412 | @vindex $tpnum |
9413 | @cindex last tracepoint number | |
9414 | @cindex recent tracepoint number | |
9415 | @cindex tracepoint number | |
9416 | The convenience variable @code{$tpnum} records the tracepoint number | |
9417 | of the most recently set tracepoint. | |
9418 | ||
9419 | @kindex delete tracepoint | |
9420 | @cindex tracepoint deletion | |
9421 | @item delete tracepoint @r{[}@var{num}@r{]} | |
9422 | Permanently delete one or more tracepoints. With no argument, the | |
1042e4c0 SS |
9423 | default is to delete all tracepoints. Note that the regular |
9424 | @code{delete} command can remove tracepoints also. | |
b37052ae EZ |
9425 | |
9426 | Examples: | |
9427 | ||
9428 | @smallexample | |
9429 | (@value{GDBP}) @b{delete trace 1 2 3} // remove three tracepoints | |
9430 | ||
9431 | (@value{GDBP}) @b{delete trace} // remove all tracepoints | |
9432 | @end smallexample | |
9433 | ||
9434 | @noindent | |
9435 | You can abbreviate this command as @code{del tr}. | |
9436 | @end table | |
9437 | ||
9438 | @node Enable and Disable Tracepoints | |
9439 | @subsection Enable and Disable Tracepoints | |
9440 | ||
1042e4c0 SS |
9441 | These commands are deprecated; they are equivalent to plain @code{disable} and @code{enable}. |
9442 | ||
b37052ae EZ |
9443 | @table @code |
9444 | @kindex disable tracepoint | |
9445 | @item disable tracepoint @r{[}@var{num}@r{]} | |
9446 | Disable tracepoint @var{num}, or all tracepoints if no argument | |
9447 | @var{num} is given. A disabled tracepoint will have no effect during | |
9448 | the next trace experiment, but it is not forgotten. You can re-enable | |
9449 | a disabled tracepoint using the @code{enable tracepoint} command. | |
9450 | ||
9451 | @kindex enable tracepoint | |
9452 | @item enable tracepoint @r{[}@var{num}@r{]} | |
9453 | Enable tracepoint @var{num}, or all tracepoints. The enabled | |
9454 | tracepoints will become effective the next time a trace experiment is | |
9455 | run. | |
9456 | @end table | |
9457 | ||
9458 | @node Tracepoint Passcounts | |
9459 | @subsection Tracepoint Passcounts | |
9460 | ||
9461 | @table @code | |
9462 | @kindex passcount | |
9463 | @cindex tracepoint pass count | |
9464 | @item passcount @r{[}@var{n} @r{[}@var{num}@r{]]} | |
9465 | Set the @dfn{passcount} of a tracepoint. The passcount is a way to | |
9466 | automatically stop a trace experiment. If a tracepoint's passcount is | |
9467 | @var{n}, then the trace experiment will be automatically stopped on | |
9468 | the @var{n}'th time that tracepoint is hit. If the tracepoint number | |
9469 | @var{num} is not specified, the @code{passcount} command sets the | |
9470 | passcount of the most recently defined tracepoint. If no passcount is | |
9471 | given, the trace experiment will run until stopped explicitly by the | |
9472 | user. | |
9473 | ||
9474 | Examples: | |
9475 | ||
9476 | @smallexample | |
b383017d | 9477 | (@value{GDBP}) @b{passcount 5 2} // Stop on the 5th execution of |
6826cf00 | 9478 | @exdent @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @code{// tracepoint 2} |
b37052ae EZ |
9479 | |
9480 | (@value{GDBP}) @b{passcount 12} // Stop on the 12th execution of the | |
6826cf00 | 9481 | @exdent @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @code{// most recently defined tracepoint.} |
b37052ae EZ |
9482 | (@value{GDBP}) @b{trace foo} |
9483 | (@value{GDBP}) @b{pass 3} | |
9484 | (@value{GDBP}) @b{trace bar} | |
9485 | (@value{GDBP}) @b{pass 2} | |
9486 | (@value{GDBP}) @b{trace baz} | |
9487 | (@value{GDBP}) @b{pass 1} // Stop tracing when foo has been | |
6826cf00 EZ |
9488 | @exdent @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @code{// executed 3 times OR when bar has} |
9489 | @exdent @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @code{// been executed 2 times} | |
9490 | @exdent @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @ @code{// OR when baz has been executed 1 time.} | |
b37052ae EZ |
9491 | @end smallexample |
9492 | @end table | |
9493 | ||
782b2b07 SS |
9494 | @node Tracepoint Conditions |
9495 | @subsection Tracepoint Conditions | |
9496 | @cindex conditional tracepoints | |
9497 | @cindex tracepoint conditions | |
9498 | ||
9499 | The simplest sort of tracepoint collects data every time your program | |
9500 | reaches a specified place. You can also specify a @dfn{condition} for | |
9501 | a tracepoint. A condition is just a Boolean expression in your | |
9502 | programming language (@pxref{Expressions, ,Expressions}). A | |
9503 | tracepoint with a condition evaluates the expression each time your | |
9504 | program reaches it, and data collection happens only if the condition | |
9505 | is true. | |
9506 | ||
9507 | Tracepoint conditions can be specified when a tracepoint is set, by | |
9508 | using @samp{if} in the arguments to the @code{trace} command. | |
9509 | @xref{Create and Delete Tracepoints, ,Setting Tracepoints}. They can | |
9510 | also be set or changed at any time with the @code{condition} command, | |
9511 | just as with breakpoints. | |
9512 | ||
9513 | Unlike breakpoint conditions, @value{GDBN} does not actually evaluate | |
9514 | the conditional expression itself. Instead, @value{GDBN} encodes the | |
9515 | expression into an agent expression (@pxref{Agent Expressions} | |
9516 | suitable for execution on the target, independently of @value{GDBN}. | |
9517 | Global variables become raw memory locations, locals become stack | |
9518 | accesses, and so forth. | |
9519 | ||
9520 | For instance, suppose you have a function that is usually called | |
9521 | frequently, but should not be called after an error has occurred. You | |
9522 | could use the following tracepoint command to collect data about calls | |
9523 | of that function that happen while the error code is propagating | |
9524 | through the program; an unconditional tracepoint could end up | |
9525 | collecting thousands of useless trace frames that you would have to | |
9526 | search through. | |
9527 | ||
9528 | @smallexample | |
9529 | (@value{GDBP}) @kbd{trace normal_operation if errcode > 0} | |
9530 | @end smallexample | |
9531 | ||
f61e138d SS |
9532 | @node Trace State Variables |
9533 | @subsection Trace State Variables | |
9534 | @cindex trace state variables | |
9535 | ||
9536 | A @dfn{trace state variable} is a special type of variable that is | |
9537 | created and managed by target-side code. The syntax is the same as | |
9538 | that for GDB's convenience variables (a string prefixed with ``$''), | |
9539 | but they are stored on the target. They must be created explicitly, | |
9540 | using a @code{tvariable} command. They are always 64-bit signed | |
9541 | integers. | |
9542 | ||
9543 | Trace state variables are remembered by @value{GDBN}, and downloaded | |
9544 | to the target along with tracepoint information when the trace | |
9545 | experiment starts. There are no intrinsic limits on the number of | |
9546 | trace state variables, beyond memory limitations of the target. | |
9547 | ||
9548 | @cindex convenience variables, and trace state variables | |
9549 | Although trace state variables are managed by the target, you can use | |
9550 | them in print commands and expressions as if they were convenience | |
9551 | variables; @value{GDBN} will get the current value from the target | |
9552 | while the trace experiment is running. Trace state variables share | |
9553 | the same namespace as other ``$'' variables, which means that you | |
9554 | cannot have trace state variables with names like @code{$23} or | |
9555 | @code{$pc}, nor can you have a trace state variable and a convenience | |
9556 | variable with the same name. | |
9557 | ||
9558 | @table @code | |
9559 | ||
9560 | @item tvariable $@var{name} [ = @var{expression} ] | |
9561 | @kindex tvariable | |
9562 | The @code{tvariable} command creates a new trace state variable named | |
9563 | @code{$@var{name}}, and optionally gives it an initial value of | |
9564 | @var{expression}. @var{expression} is evaluated when this command is | |
9565 | entered; the result will be converted to an integer if possible, | |
9566 | otherwise @value{GDBN} will report an error. A subsequent | |
9567 | @code{tvariable} command specifying the same name does not create a | |
9568 | variable, but instead assigns the supplied initial value to the | |
9569 | existing variable of that name, overwriting any previous initial | |
9570 | value. The default initial value is 0. | |
9571 | ||
9572 | @item info tvariables | |
9573 | @kindex info tvariables | |
9574 | List all the trace state variables along with their initial values. | |
9575 | Their current values may also be displayed, if the trace experiment is | |
9576 | currently running. | |
9577 | ||
9578 | @item delete tvariable @r{[} $@var{name} @dots{} @r{]} | |
9579 | @kindex delete tvariable | |
9580 | Delete the given trace state variables, or all of them if no arguments | |
9581 | are specified. | |
9582 | ||
9583 | @end table | |
9584 | ||
b37052ae EZ |
9585 | @node Tracepoint Actions |
9586 | @subsection Tracepoint Action Lists | |
9587 | ||
9588 | @table @code | |
9589 | @kindex actions | |
9590 | @cindex tracepoint actions | |
9591 | @item actions @r{[}@var{num}@r{]} | |
9592 | This command will prompt for a list of actions to be taken when the | |
9593 | tracepoint is hit. If the tracepoint number @var{num} is not | |
9594 | specified, this command sets the actions for the one that was most | |
9595 | recently defined (so that you can define a tracepoint and then say | |
9596 | @code{actions} without bothering about its number). You specify the | |
9597 | actions themselves on the following lines, one action at a time, and | |
9598 | terminate the actions list with a line containing just @code{end}. So | |
9599 | far, the only defined actions are @code{collect} and | |
9600 | @code{while-stepping}. | |
9601 | ||
9602 | @cindex remove actions from a tracepoint | |
9603 | To remove all actions from a tracepoint, type @samp{actions @var{num}} | |
9604 | and follow it immediately with @samp{end}. | |
9605 | ||
9606 | @smallexample | |
9607 | (@value{GDBP}) @b{collect @var{data}} // collect some data | |
9608 | ||
6826cf00 | 9609 | (@value{GDBP}) @b{while-stepping 5} // single-step 5 times, collect data |
b37052ae | 9610 | |
6826cf00 | 9611 | (@value{GDBP}) @b{end} // signals the end of actions. |
b37052ae EZ |
9612 | @end smallexample |
9613 | ||
9614 | In the following example, the action list begins with @code{collect} | |
9615 | commands indicating the things to be collected when the tracepoint is | |
9616 | hit. Then, in order to single-step and collect additional data | |
9617 | following the tracepoint, a @code{while-stepping} command is used, | |
9618 | followed by the list of things to be collected while stepping. The | |
9619 | @code{while-stepping} command is terminated by its own separate | |
9620 | @code{end} command. Lastly, the action list is terminated by an | |
9621 | @code{end} command. | |
9622 | ||
9623 | @smallexample | |
9624 | (@value{GDBP}) @b{trace foo} | |
9625 | (@value{GDBP}) @b{actions} | |
9626 | Enter actions for tracepoint 1, one per line: | |
9627 | > collect bar,baz | |
9628 | > collect $regs | |
9629 | > while-stepping 12 | |
9630 | > collect $fp, $sp | |
9631 | > end | |
9632 | end | |
9633 | @end smallexample | |
9634 | ||
9635 | @kindex collect @r{(tracepoints)} | |
9636 | @item collect @var{expr1}, @var{expr2}, @dots{} | |
9637 | Collect values of the given expressions when the tracepoint is hit. | |
9638 | This command accepts a comma-separated list of any valid expressions. | |
9639 | In addition to global, static, or local variables, the following | |
9640 | special arguments are supported: | |
9641 | ||
9642 | @table @code | |
9643 | @item $regs | |
9644 | collect all registers | |
9645 | ||
9646 | @item $args | |
9647 | collect all function arguments | |
9648 | ||
9649 | @item $locals | |
9650 | collect all local variables. | |
9651 | @end table | |
9652 | ||
9653 | You can give several consecutive @code{collect} commands, each one | |
9654 | with a single argument, or one @code{collect} command with several | |
9655 | arguments separated by commas: the effect is the same. | |
9656 | ||
f5c37c66 EZ |
9657 | The command @code{info scope} (@pxref{Symbols, info scope}) is |
9658 | particularly useful for figuring out what data to collect. | |
9659 | ||
6da95a67 SS |
9660 | @kindex teval @r{(tracepoints)} |
9661 | @item teval @var{expr1}, @var{expr2}, @dots{} | |
9662 | Evaluate the given expressions when the tracepoint is hit. This | |
9663 | command accepts a comma-separated list of expressions. The results | |
9664 | are discarded, so this is mainly useful for assigning values to trace | |
9665 | state variables (@pxref{Trace State Variables}) without adding those | |
9666 | values to the trace buffer, as would be the case if the @code{collect} | |
9667 | action were used. | |
9668 | ||
b37052ae EZ |
9669 | @kindex while-stepping @r{(tracepoints)} |
9670 | @item while-stepping @var{n} | |
9671 | Perform @var{n} single-step traces after the tracepoint, collecting | |
9672 | new data at each step. The @code{while-stepping} command is | |
9673 | followed by the list of what to collect while stepping (followed by | |
9674 | its own @code{end} command): | |
9675 | ||
9676 | @smallexample | |
9677 | > while-stepping 12 | |
9678 | > collect $regs, myglobal | |
9679 | > end | |
9680 | > | |
9681 | @end smallexample | |
9682 | ||
9683 | @noindent | |
9684 | You may abbreviate @code{while-stepping} as @code{ws} or | |
9685 | @code{stepping}. | |
236f1d4d SS |
9686 | |
9687 | @item set default-collect @var{expr1}, @var{expr2}, @dots{} | |
9688 | @kindex set default-collect | |
9689 | @cindex default collection action | |
9690 | This variable is a list of expressions to collect at each tracepoint | |
9691 | hit. It is effectively an additional @code{collect} action prepended | |
9692 | to every tracepoint action list. The expressions are parsed | |
9693 | individually for each tracepoint, so for instance a variable named | |
9694 | @code{xyz} may be interpreted as a global for one tracepoint, and a | |
9695 | local for another, as appropriate to the tracepoint's location. | |
9696 | ||
9697 | @item show default-collect | |
9698 | @kindex show default-collect | |
9699 | Show the list of expressions that are collected by default at each | |
9700 | tracepoint hit. | |
9701 | ||
b37052ae EZ |
9702 | @end table |
9703 | ||
9704 | @node Listing Tracepoints | |
9705 | @subsection Listing Tracepoints | |
9706 | ||
9707 | @table @code | |
9708 | @kindex info tracepoints | |
09d4efe1 | 9709 | @kindex info tp |
b37052ae EZ |
9710 | @cindex information about tracepoints |
9711 | @item info tracepoints @r{[}@var{num}@r{]} | |
1042e4c0 SS |
9712 | Display information about the tracepoint @var{num}. If you don't |
9713 | specify a tracepoint number, displays information about all the | |
9714 | tracepoints defined so far. The format is similar to that used for | |
9715 | @code{info breakpoints}; in fact, @code{info tracepoints} is the same | |
9716 | command, simply restricting itself to tracepoints. | |
9717 | ||
9718 | A tracepoint's listing may include additional information specific to | |
9719 | tracing: | |
b37052ae EZ |
9720 | |
9721 | @itemize @bullet | |
9722 | @item | |
b37052ae EZ |
9723 | its passcount as given by the @code{passcount @var{n}} command |
9724 | @item | |
9725 | its step count as given by the @code{while-stepping @var{n}} command | |
9726 | @item | |
1042e4c0 SS |
9727 | its action list as given by the @code{actions} command. The actions |
9728 | are prefixed with an @samp{A} so as to distinguish them from commands. | |
b37052ae EZ |
9729 | @end itemize |
9730 | ||
9731 | @smallexample | |
9732 | (@value{GDBP}) @b{info trace} | |
1042e4c0 SS |
9733 | Num Type Disp Enb Address What |
9734 | 1 tracepoint keep y 0x0804ab57 in foo() at main.cxx:7 | |
9735 | pass count 1200 | |
9736 | step count 20 | |
9737 | A while-stepping 20 | |
9738 | A collect globfoo, $regs | |
9739 | A end | |
9740 | A collect globfoo2 | |
9741 | A end | |
b37052ae EZ |
9742 | (@value{GDBP}) |
9743 | @end smallexample | |
9744 | ||
9745 | @noindent | |
9746 | This command can be abbreviated @code{info tp}. | |
9747 | @end table | |
9748 | ||
79a6e687 BW |
9749 | @node Starting and Stopping Trace Experiments |
9750 | @subsection Starting and Stopping Trace Experiments | |
b37052ae EZ |
9751 | |
9752 | @table @code | |
9753 | @kindex tstart | |
9754 | @cindex start a new trace experiment | |
9755 | @cindex collected data discarded | |
9756 | @item tstart | |
9757 | This command takes no arguments. It starts the trace experiment, and | |
9758 | begins collecting data. This has the side effect of discarding all | |
9759 | the data collected in the trace buffer during the previous trace | |
9760 | experiment. | |
9761 | ||
9762 | @kindex tstop | |
9763 | @cindex stop a running trace experiment | |
9764 | @item tstop | |
9765 | This command takes no arguments. It ends the trace experiment, and | |
9766 | stops collecting data. | |
9767 | ||
68c71a2e | 9768 | @strong{Note}: a trace experiment and data collection may stop |
b37052ae EZ |
9769 | automatically if any tracepoint's passcount is reached |
9770 | (@pxref{Tracepoint Passcounts}), or if the trace buffer becomes full. | |
9771 | ||
9772 | @kindex tstatus | |
9773 | @cindex status of trace data collection | |
9774 | @cindex trace experiment, status of | |
9775 | @item tstatus | |
9776 | This command displays the status of the current trace data | |
9777 | collection. | |
9778 | @end table | |
9779 | ||
9780 | Here is an example of the commands we described so far: | |
9781 | ||
9782 | @smallexample | |
9783 | (@value{GDBP}) @b{trace gdb_c_test} | |
9784 | (@value{GDBP}) @b{actions} | |
9785 | Enter actions for tracepoint #1, one per line. | |
9786 | > collect $regs,$locals,$args | |
9787 | > while-stepping 11 | |
9788 | > collect $regs | |
9789 | > end | |
9790 | > end | |
9791 | (@value{GDBP}) @b{tstart} | |
9792 | [time passes @dots{}] | |
9793 | (@value{GDBP}) @b{tstop} | |
9794 | @end smallexample | |
9795 | ||
d5551862 SS |
9796 | @cindex disconnected tracing |
9797 | You can choose to continue running the trace experiment even if | |
9798 | @value{GDBN} disconnects from the target, voluntarily or | |
9799 | involuntarily. For commands such as @code{detach}, the debugger will | |
9800 | ask what you want to do with the trace. But for unexpected | |
9801 | terminations (@value{GDBN} crash, network outage), it would be | |
9802 | unfortunate to lose hard-won trace data, so the variable | |
9803 | @code{disconnected-tracing} lets you decide whether the trace should | |
9804 | continue running without @value{GDBN}. | |
9805 | ||
9806 | @table @code | |
9807 | @item set disconnected-tracing on | |
9808 | @itemx set disconnected-tracing off | |
9809 | @kindex set disconnected-tracing | |
9810 | Choose whether a tracing run should continue to run if @value{GDBN} | |
9811 | has disconnected from the target. Note that @code{detach} or | |
9812 | @code{quit} will ask you directly what to do about a running trace no | |
9813 | matter what this variable's setting, so the variable is mainly useful | |
9814 | for handling unexpected situations, such as loss of the network. | |
9815 | ||
9816 | @item show disconnected-tracing | |
9817 | @kindex show disconnected-tracing | |
9818 | Show the current choice for disconnected tracing. | |
9819 | ||
9820 | @end table | |
9821 | ||
9822 | When you reconnect to the target, the trace experiment may or may not | |
9823 | still be running; it might have filled the trace buffer in the | |
9824 | meantime, or stopped for one of the other reasons. If it is running, | |
9825 | it will continue after reconnection. | |
9826 | ||
9827 | Upon reconnection, the target will upload information about the | |
9828 | tracepoints in effect. @value{GDBN} will then compare that | |
9829 | information to the set of tracepoints currently defined, and attempt | |
9830 | to match them up, allowing for the possibility that the numbers may | |
9831 | have changed due to creation and deletion in the meantime. If one of | |
9832 | the target's tracepoints does not match any in @value{GDBN}, the | |
9833 | debugger will create a new tracepoint, so that you have a number with | |
9834 | which to specify that tracepoint. This matching-up process is | |
9835 | necessarily heuristic, and it may result in useless tracepoints being | |
9836 | created; you may simply delete them if they are of no use. | |
b37052ae EZ |
9837 | |
9838 | @node Analyze Collected Data | |
79a6e687 | 9839 | @section Using the Collected Data |
b37052ae EZ |
9840 | |
9841 | After the tracepoint experiment ends, you use @value{GDBN} commands | |
9842 | for examining the trace data. The basic idea is that each tracepoint | |
9843 | collects a trace @dfn{snapshot} every time it is hit and another | |
9844 | snapshot every time it single-steps. All these snapshots are | |
9845 | consecutively numbered from zero and go into a buffer, and you can | |
9846 | examine them later. The way you examine them is to @dfn{focus} on a | |
9847 | specific trace snapshot. When the remote stub is focused on a trace | |
9848 | snapshot, it will respond to all @value{GDBN} requests for memory and | |
9849 | registers by reading from the buffer which belongs to that snapshot, | |
9850 | rather than from @emph{real} memory or registers of the program being | |
9851 | debugged. This means that @strong{all} @value{GDBN} commands | |
9852 | (@code{print}, @code{info registers}, @code{backtrace}, etc.) will | |
9853 | behave as if we were currently debugging the program state as it was | |
9854 | when the tracepoint occurred. Any requests for data that are not in | |
9855 | the buffer will fail. | |
9856 | ||
9857 | @menu | |
9858 | * tfind:: How to select a trace snapshot | |
9859 | * tdump:: How to display all data for a snapshot | |
9860 | * save-tracepoints:: How to save tracepoints for a future run | |
9861 | @end menu | |
9862 | ||
9863 | @node tfind | |
9864 | @subsection @code{tfind @var{n}} | |
9865 | ||
9866 | @kindex tfind | |
9867 | @cindex select trace snapshot | |
9868 | @cindex find trace snapshot | |
9869 | The basic command for selecting a trace snapshot from the buffer is | |
9870 | @code{tfind @var{n}}, which finds trace snapshot number @var{n}, | |
9871 | counting from zero. If no argument @var{n} is given, the next | |
9872 | snapshot is selected. | |
9873 | ||
9874 | Here are the various forms of using the @code{tfind} command. | |
9875 | ||
9876 | @table @code | |
9877 | @item tfind start | |
9878 | Find the first snapshot in the buffer. This is a synonym for | |
9879 | @code{tfind 0} (since 0 is the number of the first snapshot). | |
9880 | ||
9881 | @item tfind none | |
9882 | Stop debugging trace snapshots, resume @emph{live} debugging. | |
9883 | ||
9884 | @item tfind end | |
9885 | Same as @samp{tfind none}. | |
9886 | ||
9887 | @item tfind | |
9888 | No argument means find the next trace snapshot. | |
9889 | ||
9890 | @item tfind - | |
9891 | Find the previous trace snapshot before the current one. This permits | |
9892 | retracing earlier steps. | |
9893 | ||
9894 | @item tfind tracepoint @var{num} | |
9895 | Find the next snapshot associated with tracepoint @var{num}. Search | |
9896 | proceeds forward from the last examined trace snapshot. If no | |
9897 | argument @var{num} is given, it means find the next snapshot collected | |
9898 | for the same tracepoint as the current snapshot. | |
9899 | ||
9900 | @item tfind pc @var{addr} | |
9901 | Find the next snapshot associated with the value @var{addr} of the | |
9902 | program counter. Search proceeds forward from the last examined trace | |
9903 | snapshot. If no argument @var{addr} is given, it means find the next | |
9904 | snapshot with the same value of PC as the current snapshot. | |
9905 | ||
9906 | @item tfind outside @var{addr1}, @var{addr2} | |
9907 | Find the next snapshot whose PC is outside the given range of | |
081dfbf7 | 9908 | addresses (exclusive). |
b37052ae EZ |
9909 | |
9910 | @item tfind range @var{addr1}, @var{addr2} | |
9911 | Find the next snapshot whose PC is between @var{addr1} and | |
081dfbf7 | 9912 | @var{addr2} (inclusive). |
b37052ae EZ |
9913 | |
9914 | @item tfind line @r{[}@var{file}:@r{]}@var{n} | |
9915 | Find the next snapshot associated with the source line @var{n}. If | |
9916 | the optional argument @var{file} is given, refer to line @var{n} in | |
9917 | that source file. Search proceeds forward from the last examined | |
9918 | trace snapshot. If no argument @var{n} is given, it means find the | |
9919 | next line other than the one currently being examined; thus saying | |
9920 | @code{tfind line} repeatedly can appear to have the same effect as | |
9921 | stepping from line to line in a @emph{live} debugging session. | |
9922 | @end table | |
9923 | ||
9924 | The default arguments for the @code{tfind} commands are specifically | |
9925 | designed to make it easy to scan through the trace buffer. For | |
9926 | instance, @code{tfind} with no argument selects the next trace | |
9927 | snapshot, and @code{tfind -} with no argument selects the previous | |
9928 | trace snapshot. So, by giving one @code{tfind} command, and then | |
9929 | simply hitting @key{RET} repeatedly you can examine all the trace | |
9930 | snapshots in order. Or, by saying @code{tfind -} and then hitting | |
9931 | @key{RET} repeatedly you can examine the snapshots in reverse order. | |
9932 | The @code{tfind line} command with no argument selects the snapshot | |
9933 | for the next source line executed. The @code{tfind pc} command with | |
9934 | no argument selects the next snapshot with the same program counter | |
9935 | (PC) as the current frame. The @code{tfind tracepoint} command with | |
9936 | no argument selects the next trace snapshot collected by the same | |
9937 | tracepoint as the current one. | |
9938 | ||
9939 | In addition to letting you scan through the trace buffer manually, | |
9940 | these commands make it easy to construct @value{GDBN} scripts that | |
9941 | scan through the trace buffer and print out whatever collected data | |
9942 | you are interested in. Thus, if we want to examine the PC, FP, and SP | |
9943 | registers from each trace frame in the buffer, we can say this: | |
9944 | ||
9945 | @smallexample | |
9946 | (@value{GDBP}) @b{tfind start} | |
9947 | (@value{GDBP}) @b{while ($trace_frame != -1)} | |
9948 | > printf "Frame %d, PC = %08X, SP = %08X, FP = %08X\n", \ | |
9949 | $trace_frame, $pc, $sp, $fp | |
9950 | > tfind | |
9951 | > end | |
9952 | ||
9953 | Frame 0, PC = 0020DC64, SP = 0030BF3C, FP = 0030BF44 | |
9954 | Frame 1, PC = 0020DC6C, SP = 0030BF38, FP = 0030BF44 | |
9955 | Frame 2, PC = 0020DC70, SP = 0030BF34, FP = 0030BF44 | |
9956 | Frame 3, PC = 0020DC74, SP = 0030BF30, FP = 0030BF44 | |
9957 | Frame 4, PC = 0020DC78, SP = 0030BF2C, FP = 0030BF44 | |
9958 | Frame 5, PC = 0020DC7C, SP = 0030BF28, FP = 0030BF44 | |
9959 | Frame 6, PC = 0020DC80, SP = 0030BF24, FP = 0030BF44 | |
9960 | Frame 7, PC = 0020DC84, SP = 0030BF20, FP = 0030BF44 | |
9961 | Frame 8, PC = 0020DC88, SP = 0030BF1C, FP = 0030BF44 | |
9962 | Frame 9, PC = 0020DC8E, SP = 0030BF18, FP = 0030BF44 | |
9963 | Frame 10, PC = 00203F6C, SP = 0030BE3C, FP = 0030BF14 | |
9964 | @end smallexample | |
9965 | ||
9966 | Or, if we want to examine the variable @code{X} at each source line in | |
9967 | the buffer: | |
9968 | ||
9969 | @smallexample | |
9970 | (@value{GDBP}) @b{tfind start} | |
9971 | (@value{GDBP}) @b{while ($trace_frame != -1)} | |
9972 | > printf "Frame %d, X == %d\n", $trace_frame, X | |
9973 | > tfind line | |
9974 | > end | |
9975 | ||
9976 | Frame 0, X = 1 | |
9977 | Frame 7, X = 2 | |
9978 | Frame 13, X = 255 | |
9979 | @end smallexample | |
9980 | ||
9981 | @node tdump | |
9982 | @subsection @code{tdump} | |
9983 | @kindex tdump | |
9984 | @cindex dump all data collected at tracepoint | |
9985 | @cindex tracepoint data, display | |
9986 | ||
9987 | This command takes no arguments. It prints all the data collected at | |
9988 | the current trace snapshot. | |
9989 | ||
9990 | @smallexample | |
9991 | (@value{GDBP}) @b{trace 444} | |
9992 | (@value{GDBP}) @b{actions} | |
9993 | Enter actions for tracepoint #2, one per line: | |
9994 | > collect $regs, $locals, $args, gdb_long_test | |
9995 | > end | |
9996 | ||
9997 | (@value{GDBP}) @b{tstart} | |
9998 | ||
9999 | (@value{GDBP}) @b{tfind line 444} | |
10000 | #0 gdb_test (p1=0x11, p2=0x22, p3=0x33, p4=0x44, p5=0x55, p6=0x66) | |
10001 | at gdb_test.c:444 | |
10002 | 444 printp( "%s: arguments = 0x%X 0x%X 0x%X 0x%X 0x%X 0x%X\n", ) | |
10003 | ||
10004 | (@value{GDBP}) @b{tdump} | |
10005 | Data collected at tracepoint 2, trace frame 1: | |
10006 | d0 0xc4aa0085 -995491707 | |
10007 | d1 0x18 24 | |
10008 | d2 0x80 128 | |
10009 | d3 0x33 51 | |
10010 | d4 0x71aea3d 119204413 | |
10011 | d5 0x22 34 | |
10012 | d6 0xe0 224 | |
10013 | d7 0x380035 3670069 | |
10014 | a0 0x19e24a 1696330 | |
10015 | a1 0x3000668 50333288 | |
10016 | a2 0x100 256 | |
10017 | a3 0x322000 3284992 | |
10018 | a4 0x3000698 50333336 | |
10019 | a5 0x1ad3cc 1758156 | |
10020 | fp 0x30bf3c 0x30bf3c | |
10021 | sp 0x30bf34 0x30bf34 | |
10022 | ps 0x0 0 | |
10023 | pc 0x20b2c8 0x20b2c8 | |
10024 | fpcontrol 0x0 0 | |
10025 | fpstatus 0x0 0 | |
10026 | fpiaddr 0x0 0 | |
10027 | p = 0x20e5b4 "gdb-test" | |
10028 | p1 = (void *) 0x11 | |
10029 | p2 = (void *) 0x22 | |
10030 | p3 = (void *) 0x33 | |
10031 | p4 = (void *) 0x44 | |
10032 | p5 = (void *) 0x55 | |
10033 | p6 = (void *) 0x66 | |
10034 | gdb_long_test = 17 '\021' | |
10035 | ||
10036 | (@value{GDBP}) | |
10037 | @end smallexample | |
10038 | ||
10039 | @node save-tracepoints | |
10040 | @subsection @code{save-tracepoints @var{filename}} | |
10041 | @kindex save-tracepoints | |
10042 | @cindex save tracepoints for future sessions | |
10043 | ||
10044 | This command saves all current tracepoint definitions together with | |
10045 | their actions and passcounts, into a file @file{@var{filename}} | |
10046 | suitable for use in a later debugging session. To read the saved | |
10047 | tracepoint definitions, use the @code{source} command (@pxref{Command | |
10048 | Files}). | |
10049 | ||
10050 | @node Tracepoint Variables | |
10051 | @section Convenience Variables for Tracepoints | |
10052 | @cindex tracepoint variables | |
10053 | @cindex convenience variables for tracepoints | |
10054 | ||
10055 | @table @code | |
10056 | @vindex $trace_frame | |
10057 | @item (int) $trace_frame | |
10058 | The current trace snapshot (a.k.a.@: @dfn{frame}) number, or -1 if no | |
10059 | snapshot is selected. | |
10060 | ||
10061 | @vindex $tracepoint | |
10062 | @item (int) $tracepoint | |
10063 | The tracepoint for the current trace snapshot. | |
10064 | ||
10065 | @vindex $trace_line | |
10066 | @item (int) $trace_line | |
10067 | The line number for the current trace snapshot. | |
10068 | ||
10069 | @vindex $trace_file | |
10070 | @item (char []) $trace_file | |
10071 | The source file for the current trace snapshot. | |
10072 | ||
10073 | @vindex $trace_func | |
10074 | @item (char []) $trace_func | |
10075 | The name of the function containing @code{$tracepoint}. | |
10076 | @end table | |
10077 | ||
10078 | Note: @code{$trace_file} is not suitable for use in @code{printf}, | |
10079 | use @code{output} instead. | |
10080 | ||
10081 | Here's a simple example of using these convenience variables for | |
10082 | stepping through all the trace snapshots and printing some of their | |
f61e138d SS |
10083 | data. Note that these are not the same as trace state variables, |
10084 | which are managed by the target. | |
b37052ae EZ |
10085 | |
10086 | @smallexample | |
10087 | (@value{GDBP}) @b{tfind start} | |
10088 | ||
10089 | (@value{GDBP}) @b{while $trace_frame != -1} | |
10090 | > output $trace_file | |
10091 | > printf ", line %d (tracepoint #%d)\n", $trace_line, $tracepoint | |
10092 | > tfind | |
10093 | > end | |
10094 | @end smallexample | |
10095 | ||
00bf0b85 SS |
10096 | @node Trace Files |
10097 | @section Using Trace Files | |
10098 | @cindex trace files | |
10099 | ||
10100 | In some situations, the target running a trace experiment may no | |
10101 | longer be available; perhaps it crashed, or the hardware was needed | |
10102 | for a different activity. To handle these cases, you can arrange to | |
10103 | dump the trace data into a file, and later use that file as a source | |
10104 | of trace data, via the @code{target tfile} command. | |
10105 | ||
10106 | @table @code | |
10107 | ||
10108 | @kindex tsave | |
10109 | @item tsave [ -r ] @var{filename} | |
10110 | Save the trace data to @var{filename}. By default, this command | |
10111 | assumes that @var{filename} refers to the host filesystem, so if | |
10112 | necessary @value{GDBN} will copy raw trace data up from the target and | |
10113 | then save it. If the target supports it, you can also supply the | |
10114 | optional argument @code{-r} (``remote'') to direct the target to save | |
10115 | the data directly into @var{filename} in its own filesystem, which may be | |
10116 | more efficient if the trace buffer is very large. (Note, however, that | |
10117 | @code{target tfile} can only read from files accessible to the host.) | |
10118 | ||
10119 | @kindex target tfile | |
10120 | @kindex tfile | |
10121 | @item target tfile @var{filename} | |
10122 | Use the file named @var{filename} as a source of trace data. Commands | |
10123 | that examine data work as they do with a live target, but it is not | |
10124 | possible to run any new trace experiments. @code{tstatus} will report | |
10125 | the state of the trace run at the moment the data was saved, as well | |
10126 | as the current trace frame you are examining. @var{filename} must be | |
10127 | on a filesystem accessible to the host. | |
10128 | ||
10129 | @end table | |
10130 | ||
df0cd8c5 JB |
10131 | @node Overlays |
10132 | @chapter Debugging Programs That Use Overlays | |
10133 | @cindex overlays | |
10134 | ||
10135 | If your program is too large to fit completely in your target system's | |
10136 | memory, you can sometimes use @dfn{overlays} to work around this | |
10137 | problem. @value{GDBN} provides some support for debugging programs that | |
10138 | use overlays. | |
10139 | ||
10140 | @menu | |
10141 | * How Overlays Work:: A general explanation of overlays. | |
10142 | * Overlay Commands:: Managing overlays in @value{GDBN}. | |
10143 | * Automatic Overlay Debugging:: @value{GDBN} can find out which overlays are | |
10144 | mapped by asking the inferior. | |
10145 | * Overlay Sample Program:: A sample program using overlays. | |
10146 | @end menu | |
10147 | ||
10148 | @node How Overlays Work | |
10149 | @section How Overlays Work | |
10150 | @cindex mapped overlays | |
10151 | @cindex unmapped overlays | |
10152 | @cindex load address, overlay's | |
10153 | @cindex mapped address | |
10154 | @cindex overlay area | |
10155 | ||
10156 | Suppose you have a computer whose instruction address space is only 64 | |
10157 | kilobytes long, but which has much more memory which can be accessed by | |
10158 | other means: special instructions, segment registers, or memory | |
10159 | management hardware, for example. Suppose further that you want to | |
10160 | adapt a program which is larger than 64 kilobytes to run on this system. | |
10161 | ||
10162 | One solution is to identify modules of your program which are relatively | |
10163 | independent, and need not call each other directly; call these modules | |
10164 | @dfn{overlays}. Separate the overlays from the main program, and place | |
10165 | their machine code in the larger memory. Place your main program in | |
10166 | instruction memory, but leave at least enough space there to hold the | |
10167 | largest overlay as well. | |
10168 | ||
10169 | Now, to call a function located in an overlay, you must first copy that | |
10170 | overlay's machine code from the large memory into the space set aside | |
10171 | for it in the instruction memory, and then jump to its entry point | |
10172 | there. | |
10173 | ||
c928edc0 AC |
10174 | @c NB: In the below the mapped area's size is greater or equal to the |
10175 | @c size of all overlays. This is intentional to remind the developer | |
10176 | @c that overlays don't necessarily need to be the same size. | |
10177 | ||
474c8240 | 10178 | @smallexample |
df0cd8c5 | 10179 | @group |
c928edc0 AC |
10180 | Data Instruction Larger |
10181 | Address Space Address Space Address Space | |
10182 | +-----------+ +-----------+ +-----------+ | |
10183 | | | | | | | | |
10184 | +-----------+ +-----------+ +-----------+<-- overlay 1 | |
10185 | | program | | main | .----| overlay 1 | load address | |
10186 | | variables | | program | | +-----------+ | |
10187 | | and heap | | | | | | | |
10188 | +-----------+ | | | +-----------+<-- overlay 2 | |
10189 | | | +-----------+ | | | load address | |
10190 | +-----------+ | | | .-| overlay 2 | | |
10191 | | | | | | | | |
10192 | mapped --->+-----------+ | | +-----------+ | |
10193 | address | | | | | | | |
10194 | | overlay | <-' | | | | |
10195 | | area | <---' +-----------+<-- overlay 3 | |
10196 | | | <---. | | load address | |
10197 | +-----------+ `--| overlay 3 | | |
10198 | | | | | | |
10199 | +-----------+ | | | |
10200 | +-----------+ | |
10201 | | | | |
10202 | +-----------+ | |
10203 | ||
10204 | @anchor{A code overlay}A code overlay | |
df0cd8c5 | 10205 | @end group |
474c8240 | 10206 | @end smallexample |
df0cd8c5 | 10207 | |
c928edc0 AC |
10208 | The diagram (@pxref{A code overlay}) shows a system with separate data |
10209 | and instruction address spaces. To map an overlay, the program copies | |
10210 | its code from the larger address space to the instruction address space. | |
10211 | Since the overlays shown here all use the same mapped address, only one | |
10212 | may be mapped at a time. For a system with a single address space for | |
10213 | data and instructions, the diagram would be similar, except that the | |
10214 | program variables and heap would share an address space with the main | |
10215 | program and the overlay area. | |
df0cd8c5 JB |
10216 | |
10217 | An overlay loaded into instruction memory and ready for use is called a | |
10218 | @dfn{mapped} overlay; its @dfn{mapped address} is its address in the | |
10219 | instruction memory. An overlay not present (or only partially present) | |
10220 | in instruction memory is called @dfn{unmapped}; its @dfn{load address} | |
10221 | is its address in the larger memory. The mapped address is also called | |
10222 | the @dfn{virtual memory address}, or @dfn{VMA}; the load address is also | |
10223 | called the @dfn{load memory address}, or @dfn{LMA}. | |
10224 | ||
10225 | Unfortunately, overlays are not a completely transparent way to adapt a | |
10226 | program to limited instruction memory. They introduce a new set of | |
10227 | global constraints you must keep in mind as you design your program: | |
10228 | ||
10229 | @itemize @bullet | |
10230 | ||
10231 | @item | |
10232 | Before calling or returning to a function in an overlay, your program | |
10233 | must make sure that overlay is actually mapped. Otherwise, the call or | |
10234 | return will transfer control to the right address, but in the wrong | |
10235 | overlay, and your program will probably crash. | |
10236 | ||
10237 | @item | |
10238 | If the process of mapping an overlay is expensive on your system, you | |
10239 | will need to choose your overlays carefully to minimize their effect on | |
10240 | your program's performance. | |
10241 | ||
10242 | @item | |
10243 | The executable file you load onto your system must contain each | |
10244 | overlay's instructions, appearing at the overlay's load address, not its | |
10245 | mapped address. However, each overlay's instructions must be relocated | |
10246 | and its symbols defined as if the overlay were at its mapped address. | |
10247 | You can use GNU linker scripts to specify different load and relocation | |
10248 | addresses for pieces of your program; see @ref{Overlay Description,,, | |
10249 | ld.info, Using ld: the GNU linker}. | |
10250 | ||
10251 | @item | |
10252 | The procedure for loading executable files onto your system must be able | |
10253 | to load their contents into the larger address space as well as the | |
10254 | instruction and data spaces. | |
10255 | ||
10256 | @end itemize | |
10257 | ||
10258 | The overlay system described above is rather simple, and could be | |
10259 | improved in many ways: | |
10260 | ||
10261 | @itemize @bullet | |
10262 | ||
10263 | @item | |
10264 | If your system has suitable bank switch registers or memory management | |
10265 | hardware, you could use those facilities to make an overlay's load area | |
10266 | contents simply appear at their mapped address in instruction space. | |
10267 | This would probably be faster than copying the overlay to its mapped | |
10268 | area in the usual way. | |
10269 | ||
10270 | @item | |
10271 | If your overlays are small enough, you could set aside more than one | |
10272 | overlay area, and have more than one overlay mapped at a time. | |
10273 | ||
10274 | @item | |
10275 | You can use overlays to manage data, as well as instructions. In | |
10276 | general, data overlays are even less transparent to your design than | |
10277 | code overlays: whereas code overlays only require care when you call or | |
10278 | return to functions, data overlays require care every time you access | |
10279 | the data. Also, if you change the contents of a data overlay, you | |
10280 | must copy its contents back out to its load address before you can copy a | |
10281 | different data overlay into the same mapped area. | |
10282 | ||
10283 | @end itemize | |
10284 | ||
10285 | ||
10286 | @node Overlay Commands | |
10287 | @section Overlay Commands | |
10288 | ||
10289 | To use @value{GDBN}'s overlay support, each overlay in your program must | |
10290 | correspond to a separate section of the executable file. The section's | |
10291 | virtual memory address and load memory address must be the overlay's | |
10292 | mapped and load addresses. Identifying overlays with sections allows | |
10293 | @value{GDBN} to determine the appropriate address of a function or | |
10294 | variable, depending on whether the overlay is mapped or not. | |
10295 | ||
10296 | @value{GDBN}'s overlay commands all start with the word @code{overlay}; | |
10297 | you can abbreviate this as @code{ov} or @code{ovly}. The commands are: | |
10298 | ||
10299 | @table @code | |
10300 | @item overlay off | |
4644b6e3 | 10301 | @kindex overlay |
df0cd8c5 JB |
10302 | Disable @value{GDBN}'s overlay support. When overlay support is |
10303 | disabled, @value{GDBN} assumes that all functions and variables are | |
10304 | always present at their mapped addresses. By default, @value{GDBN}'s | |
10305 | overlay support is disabled. | |
10306 | ||
10307 | @item overlay manual | |
df0cd8c5 JB |
10308 | @cindex manual overlay debugging |
10309 | Enable @dfn{manual} overlay debugging. In this mode, @value{GDBN} | |
10310 | relies on you to tell it which overlays are mapped, and which are not, | |
10311 | using the @code{overlay map-overlay} and @code{overlay unmap-overlay} | |
10312 | commands described below. | |
10313 | ||
10314 | @item overlay map-overlay @var{overlay} | |
10315 | @itemx overlay map @var{overlay} | |
df0cd8c5 JB |
10316 | @cindex map an overlay |
10317 | Tell @value{GDBN} that @var{overlay} is now mapped; @var{overlay} must | |
10318 | be the name of the object file section containing the overlay. When an | |
10319 | overlay is mapped, @value{GDBN} assumes it can find the overlay's | |
10320 | functions and variables at their mapped addresses. @value{GDBN} assumes | |
10321 | that any other overlays whose mapped ranges overlap that of | |
10322 | @var{overlay} are now unmapped. | |
10323 | ||
10324 | @item overlay unmap-overlay @var{overlay} | |
10325 | @itemx overlay unmap @var{overlay} | |
df0cd8c5 JB |
10326 | @cindex unmap an overlay |
10327 | Tell @value{GDBN} that @var{overlay} is no longer mapped; @var{overlay} | |
10328 | must be the name of the object file section containing the overlay. | |
10329 | When an overlay is unmapped, @value{GDBN} assumes it can find the | |
10330 | overlay's functions and variables at their load addresses. | |
10331 | ||
10332 | @item overlay auto | |
df0cd8c5 JB |
10333 | Enable @dfn{automatic} overlay debugging. In this mode, @value{GDBN} |
10334 | consults a data structure the overlay manager maintains in the inferior | |
10335 | to see which overlays are mapped. For details, see @ref{Automatic | |
10336 | Overlay Debugging}. | |
10337 | ||
10338 | @item overlay load-target | |
10339 | @itemx overlay load | |
df0cd8c5 JB |
10340 | @cindex reloading the overlay table |
10341 | Re-read the overlay table from the inferior. Normally, @value{GDBN} | |
10342 | re-reads the table @value{GDBN} automatically each time the inferior | |
10343 | stops, so this command should only be necessary if you have changed the | |
10344 | overlay mapping yourself using @value{GDBN}. This command is only | |
10345 | useful when using automatic overlay debugging. | |
10346 | ||
10347 | @item overlay list-overlays | |
10348 | @itemx overlay list | |
10349 | @cindex listing mapped overlays | |
10350 | Display a list of the overlays currently mapped, along with their mapped | |
10351 | addresses, load addresses, and sizes. | |
10352 | ||
10353 | @end table | |
10354 | ||
10355 | Normally, when @value{GDBN} prints a code address, it includes the name | |
10356 | of the function the address falls in: | |
10357 | ||
474c8240 | 10358 | @smallexample |
f7dc1244 | 10359 | (@value{GDBP}) print main |
df0cd8c5 | 10360 | $3 = @{int ()@} 0x11a0 <main> |
474c8240 | 10361 | @end smallexample |
df0cd8c5 JB |
10362 | @noindent |
10363 | When overlay debugging is enabled, @value{GDBN} recognizes code in | |
10364 | unmapped overlays, and prints the names of unmapped functions with | |
10365 | asterisks around them. For example, if @code{foo} is a function in an | |
10366 | unmapped overlay, @value{GDBN} prints it this way: | |
10367 | ||
474c8240 | 10368 | @smallexample |
f7dc1244 | 10369 | (@value{GDBP}) overlay list |
df0cd8c5 | 10370 | No sections are mapped. |
f7dc1244 | 10371 | (@value{GDBP}) print foo |
df0cd8c5 | 10372 | $5 = @{int (int)@} 0x100000 <*foo*> |
474c8240 | 10373 | @end smallexample |
df0cd8c5 JB |
10374 | @noindent |
10375 | When @code{foo}'s overlay is mapped, @value{GDBN} prints the function's | |
10376 | name normally: | |
10377 | ||
474c8240 | 10378 | @smallexample |
f7dc1244 | 10379 | (@value{GDBP}) overlay list |
b383017d | 10380 | Section .ov.foo.text, loaded at 0x100000 - 0x100034, |
df0cd8c5 | 10381 | mapped at 0x1016 - 0x104a |
f7dc1244 | 10382 | (@value{GDBP}) print foo |
df0cd8c5 | 10383 | $6 = @{int (int)@} 0x1016 <foo> |
474c8240 | 10384 | @end smallexample |
df0cd8c5 JB |
10385 | |
10386 | When overlay debugging is enabled, @value{GDBN} can find the correct | |
10387 | address for functions and variables in an overlay, whether or not the | |
10388 | overlay is mapped. This allows most @value{GDBN} commands, like | |
10389 | @code{break} and @code{disassemble}, to work normally, even on unmapped | |
10390 | code. However, @value{GDBN}'s breakpoint support has some limitations: | |
10391 | ||
10392 | @itemize @bullet | |
10393 | @item | |
10394 | @cindex breakpoints in overlays | |
10395 | @cindex overlays, setting breakpoints in | |
10396 | You can set breakpoints in functions in unmapped overlays, as long as | |
10397 | @value{GDBN} can write to the overlay at its load address. | |
10398 | @item | |
10399 | @value{GDBN} can not set hardware or simulator-based breakpoints in | |
10400 | unmapped overlays. However, if you set a breakpoint at the end of your | |
10401 | overlay manager (and tell @value{GDBN} which overlays are now mapped, if | |
10402 | you are using manual overlay management), @value{GDBN} will re-set its | |
10403 | breakpoints properly. | |
10404 | @end itemize | |
10405 | ||
10406 | ||
10407 | @node Automatic Overlay Debugging | |
10408 | @section Automatic Overlay Debugging | |
10409 | @cindex automatic overlay debugging | |
10410 | ||
10411 | @value{GDBN} can automatically track which overlays are mapped and which | |
10412 | are not, given some simple co-operation from the overlay manager in the | |
10413 | inferior. If you enable automatic overlay debugging with the | |
10414 | @code{overlay auto} command (@pxref{Overlay Commands}), @value{GDBN} | |
10415 | looks in the inferior's memory for certain variables describing the | |
10416 | current state of the overlays. | |
10417 | ||
10418 | Here are the variables your overlay manager must define to support | |
10419 | @value{GDBN}'s automatic overlay debugging: | |
10420 | ||
10421 | @table @asis | |
10422 | ||
10423 | @item @code{_ovly_table}: | |
10424 | This variable must be an array of the following structures: | |
10425 | ||
474c8240 | 10426 | @smallexample |
df0cd8c5 JB |
10427 | struct |
10428 | @{ | |
10429 | /* The overlay's mapped address. */ | |
10430 | unsigned long vma; | |
10431 | ||
10432 | /* The size of the overlay, in bytes. */ | |
10433 | unsigned long size; | |
10434 | ||
10435 | /* The overlay's load address. */ | |
10436 | unsigned long lma; | |
10437 | ||
10438 | /* Non-zero if the overlay is currently mapped; | |
10439 | zero otherwise. */ | |
10440 | unsigned long mapped; | |
10441 | @} | |
474c8240 | 10442 | @end smallexample |
df0cd8c5 JB |
10443 | |
10444 | @item @code{_novlys}: | |
10445 | This variable must be a four-byte signed integer, holding the total | |
10446 | number of elements in @code{_ovly_table}. | |
10447 | ||
10448 | @end table | |
10449 | ||
10450 | To decide whether a particular overlay is mapped or not, @value{GDBN} | |
10451 | looks for an entry in @w{@code{_ovly_table}} whose @code{vma} and | |
10452 | @code{lma} members equal the VMA and LMA of the overlay's section in the | |
10453 | executable file. When @value{GDBN} finds a matching entry, it consults | |
10454 | the entry's @code{mapped} member to determine whether the overlay is | |
10455 | currently mapped. | |
10456 | ||
81d46470 | 10457 | In addition, your overlay manager may define a function called |
def71bfa | 10458 | @code{_ovly_debug_event}. If this function is defined, @value{GDBN} |
81d46470 MS |
10459 | will silently set a breakpoint there. If the overlay manager then |
10460 | calls this function whenever it has changed the overlay table, this | |
10461 | will enable @value{GDBN} to accurately keep track of which overlays | |
10462 | are in program memory, and update any breakpoints that may be set | |
b383017d | 10463 | in overlays. This will allow breakpoints to work even if the |
81d46470 MS |
10464 | overlays are kept in ROM or other non-writable memory while they |
10465 | are not being executed. | |
df0cd8c5 JB |
10466 | |
10467 | @node Overlay Sample Program | |
10468 | @section Overlay Sample Program | |
10469 | @cindex overlay example program | |
10470 | ||
10471 | When linking a program which uses overlays, you must place the overlays | |
10472 | at their load addresses, while relocating them to run at their mapped | |
10473 | addresses. To do this, you must write a linker script (@pxref{Overlay | |
10474 | Description,,, ld.info, Using ld: the GNU linker}). Unfortunately, | |
10475 | since linker scripts are specific to a particular host system, target | |
10476 | architecture, and target memory layout, this manual cannot provide | |
10477 | portable sample code demonstrating @value{GDBN}'s overlay support. | |
10478 | ||
10479 | However, the @value{GDBN} source distribution does contain an overlaid | |
10480 | program, with linker scripts for a few systems, as part of its test | |
10481 | suite. The program consists of the following files from | |
10482 | @file{gdb/testsuite/gdb.base}: | |
10483 | ||
10484 | @table @file | |
10485 | @item overlays.c | |
10486 | The main program file. | |
10487 | @item ovlymgr.c | |
10488 | A simple overlay manager, used by @file{overlays.c}. | |
10489 | @item foo.c | |
10490 | @itemx bar.c | |
10491 | @itemx baz.c | |
10492 | @itemx grbx.c | |
10493 | Overlay modules, loaded and used by @file{overlays.c}. | |
10494 | @item d10v.ld | |
10495 | @itemx m32r.ld | |
10496 | Linker scripts for linking the test program on the @code{d10v-elf} | |
10497 | and @code{m32r-elf} targets. | |
10498 | @end table | |
10499 | ||
10500 | You can build the test program using the @code{d10v-elf} GCC | |
10501 | cross-compiler like this: | |
10502 | ||
474c8240 | 10503 | @smallexample |
df0cd8c5 JB |
10504 | $ d10v-elf-gcc -g -c overlays.c |
10505 | $ d10v-elf-gcc -g -c ovlymgr.c | |
10506 | $ d10v-elf-gcc -g -c foo.c | |
10507 | $ d10v-elf-gcc -g -c bar.c | |
10508 | $ d10v-elf-gcc -g -c baz.c | |
10509 | $ d10v-elf-gcc -g -c grbx.c | |
10510 | $ d10v-elf-gcc -g overlays.o ovlymgr.o foo.o bar.o \ | |
10511 | baz.o grbx.o -Wl,-Td10v.ld -o overlays | |
474c8240 | 10512 | @end smallexample |
df0cd8c5 JB |
10513 | |
10514 | The build process is identical for any other architecture, except that | |
10515 | you must substitute the appropriate compiler and linker script for the | |
10516 | target system for @code{d10v-elf-gcc} and @code{d10v.ld}. | |
10517 | ||
10518 | ||
6d2ebf8b | 10519 | @node Languages |
c906108c SS |
10520 | @chapter Using @value{GDBN} with Different Languages |
10521 | @cindex languages | |
10522 | ||
c906108c SS |
10523 | Although programming languages generally have common aspects, they are |
10524 | rarely expressed in the same manner. For instance, in ANSI C, | |
10525 | dereferencing a pointer @code{p} is accomplished by @code{*p}, but in | |
10526 | Modula-2, it is accomplished by @code{p^}. Values can also be | |
5d161b24 | 10527 | represented (and displayed) differently. Hex numbers in C appear as |
c906108c | 10528 | @samp{0x1ae}, while in Modula-2 they appear as @samp{1AEH}. |
c906108c SS |
10529 | |
10530 | @cindex working language | |
10531 | Language-specific information is built into @value{GDBN} for some languages, | |
10532 | allowing you to express operations like the above in your program's | |
10533 | native language, and allowing @value{GDBN} to output values in a manner | |
10534 | consistent with the syntax of your program's native language. The | |
10535 | language you use to build expressions is called the @dfn{working | |
10536 | language}. | |
10537 | ||
10538 | @menu | |
10539 | * Setting:: Switching between source languages | |
10540 | * Show:: Displaying the language | |
c906108c | 10541 | * Checks:: Type and range checks |
79a6e687 BW |
10542 | * Supported Languages:: Supported languages |
10543 | * Unsupported Languages:: Unsupported languages | |
c906108c SS |
10544 | @end menu |
10545 | ||
6d2ebf8b | 10546 | @node Setting |
79a6e687 | 10547 | @section Switching Between Source Languages |
c906108c SS |
10548 | |
10549 | There are two ways to control the working language---either have @value{GDBN} | |
10550 | set it automatically, or select it manually yourself. You can use the | |
10551 | @code{set language} command for either purpose. On startup, @value{GDBN} | |
10552 | defaults to setting the language automatically. The working language is | |
10553 | used to determine how expressions you type are interpreted, how values | |
10554 | are printed, etc. | |
10555 | ||
10556 | In addition to the working language, every source file that | |
10557 | @value{GDBN} knows about has its own working language. For some object | |
10558 | file formats, the compiler might indicate which language a particular | |
10559 | source file is in. However, most of the time @value{GDBN} infers the | |
10560 | language from the name of the file. The language of a source file | |
b37052ae | 10561 | controls whether C@t{++} names are demangled---this way @code{backtrace} can |
c906108c | 10562 | show each frame appropriately for its own language. There is no way to |
d4f3574e SS |
10563 | set the language of a source file from within @value{GDBN}, but you can |
10564 | set the language associated with a filename extension. @xref{Show, , | |
79a6e687 | 10565 | Displaying the Language}. |
c906108c SS |
10566 | |
10567 | This is most commonly a problem when you use a program, such | |
5d161b24 | 10568 | as @code{cfront} or @code{f2c}, that generates C but is written in |
c906108c SS |
10569 | another language. In that case, make the |
10570 | program use @code{#line} directives in its C output; that way | |
10571 | @value{GDBN} will know the correct language of the source code of the original | |
10572 | program, and will display that source code, not the generated C code. | |
10573 | ||
10574 | @menu | |
10575 | * Filenames:: Filename extensions and languages. | |
10576 | * Manually:: Setting the working language manually | |
10577 | * Automatically:: Having @value{GDBN} infer the source language | |
10578 | @end menu | |
10579 | ||
6d2ebf8b | 10580 | @node Filenames |
79a6e687 | 10581 | @subsection List of Filename Extensions and Languages |
c906108c SS |
10582 | |
10583 | If a source file name ends in one of the following extensions, then | |
10584 | @value{GDBN} infers that its language is the one indicated. | |
10585 | ||
10586 | @table @file | |
e07c999f PH |
10587 | @item .ada |
10588 | @itemx .ads | |
10589 | @itemx .adb | |
10590 | @itemx .a | |
10591 | Ada source file. | |
c906108c SS |
10592 | |
10593 | @item .c | |
10594 | C source file | |
10595 | ||
10596 | @item .C | |
10597 | @itemx .cc | |
10598 | @itemx .cp | |
10599 | @itemx .cpp | |
10600 | @itemx .cxx | |
10601 | @itemx .c++ | |
b37052ae | 10602 | C@t{++} source file |
c906108c | 10603 | |
b37303ee AF |
10604 | @item .m |
10605 | Objective-C source file | |
10606 | ||
c906108c SS |
10607 | @item .f |
10608 | @itemx .F | |
10609 | Fortran source file | |
10610 | ||
c906108c SS |
10611 | @item .mod |
10612 | Modula-2 source file | |
c906108c SS |
10613 | |
10614 | @item .s | |
10615 | @itemx .S | |
10616 | Assembler source file. This actually behaves almost like C, but | |
10617 | @value{GDBN} does not skip over function prologues when stepping. | |
10618 | @end table | |
10619 | ||
10620 | In addition, you may set the language associated with a filename | |
79a6e687 | 10621 | extension. @xref{Show, , Displaying the Language}. |
c906108c | 10622 | |
6d2ebf8b | 10623 | @node Manually |
79a6e687 | 10624 | @subsection Setting the Working Language |
c906108c SS |
10625 | |
10626 | If you allow @value{GDBN} to set the language automatically, | |
10627 | expressions are interpreted the same way in your debugging session and | |
10628 | your program. | |
10629 | ||
10630 | @kindex set language | |
10631 | If you wish, you may set the language manually. To do this, issue the | |
10632 | command @samp{set language @var{lang}}, where @var{lang} is the name of | |
5d161b24 | 10633 | a language, such as |
c906108c | 10634 | @code{c} or @code{modula-2}. |
c906108c SS |
10635 | For a list of the supported languages, type @samp{set language}. |
10636 | ||
c906108c SS |
10637 | Setting the language manually prevents @value{GDBN} from updating the working |
10638 | language automatically. This can lead to confusion if you try | |
10639 | to debug a program when the working language is not the same as the | |
10640 | source language, when an expression is acceptable to both | |
10641 | languages---but means different things. For instance, if the current | |
10642 | source file were written in C, and @value{GDBN} was parsing Modula-2, a | |
10643 | command such as: | |
10644 | ||
474c8240 | 10645 | @smallexample |
c906108c | 10646 | print a = b + c |
474c8240 | 10647 | @end smallexample |
c906108c SS |
10648 | |
10649 | @noindent | |
10650 | might not have the effect you intended. In C, this means to add | |
10651 | @code{b} and @code{c} and place the result in @code{a}. The result | |
10652 | printed would be the value of @code{a}. In Modula-2, this means to compare | |
10653 | @code{a} to the result of @code{b+c}, yielding a @code{BOOLEAN} value. | |
c906108c | 10654 | |
6d2ebf8b | 10655 | @node Automatically |
79a6e687 | 10656 | @subsection Having @value{GDBN} Infer the Source Language |
c906108c SS |
10657 | |
10658 | To have @value{GDBN} set the working language automatically, use | |
10659 | @samp{set language local} or @samp{set language auto}. @value{GDBN} | |
10660 | then infers the working language. That is, when your program stops in a | |
10661 | frame (usually by encountering a breakpoint), @value{GDBN} sets the | |
10662 | working language to the language recorded for the function in that | |
10663 | frame. If the language for a frame is unknown (that is, if the function | |
10664 | or block corresponding to the frame was defined in a source file that | |
10665 | does not have a recognized extension), the current working language is | |
10666 | not changed, and @value{GDBN} issues a warning. | |
10667 | ||
10668 | This may not seem necessary for most programs, which are written | |
10669 | entirely in one source language. However, program modules and libraries | |
10670 | written in one source language can be used by a main program written in | |
10671 | a different source language. Using @samp{set language auto} in this | |
10672 | case frees you from having to set the working language manually. | |
10673 | ||
6d2ebf8b | 10674 | @node Show |
79a6e687 | 10675 | @section Displaying the Language |
c906108c SS |
10676 | |
10677 | The following commands help you find out which language is the | |
10678 | working language, and also what language source files were written in. | |
10679 | ||
c906108c SS |
10680 | @table @code |
10681 | @item show language | |
9c16f35a | 10682 | @kindex show language |
c906108c SS |
10683 | Display the current working language. This is the |
10684 | language you can use with commands such as @code{print} to | |
10685 | build and compute expressions that may involve variables in your program. | |
10686 | ||
10687 | @item info frame | |
4644b6e3 | 10688 | @kindex info frame@r{, show the source language} |
5d161b24 | 10689 | Display the source language for this frame. This language becomes the |
c906108c | 10690 | working language if you use an identifier from this frame. |
79a6e687 | 10691 | @xref{Frame Info, ,Information about a Frame}, to identify the other |
c906108c SS |
10692 | information listed here. |
10693 | ||
10694 | @item info source | |
4644b6e3 | 10695 | @kindex info source@r{, show the source language} |
c906108c | 10696 | Display the source language of this source file. |
5d161b24 | 10697 | @xref{Symbols, ,Examining the Symbol Table}, to identify the other |
c906108c SS |
10698 | information listed here. |
10699 | @end table | |
10700 | ||
10701 | In unusual circumstances, you may have source files with extensions | |
10702 | not in the standard list. You can then set the extension associated | |
10703 | with a language explicitly: | |
10704 | ||
c906108c | 10705 | @table @code |
09d4efe1 | 10706 | @item set extension-language @var{ext} @var{language} |
9c16f35a | 10707 | @kindex set extension-language |
09d4efe1 EZ |
10708 | Tell @value{GDBN} that source files with extension @var{ext} are to be |
10709 | assumed as written in the source language @var{language}. | |
c906108c SS |
10710 | |
10711 | @item info extensions | |
9c16f35a | 10712 | @kindex info extensions |
c906108c SS |
10713 | List all the filename extensions and the associated languages. |
10714 | @end table | |
10715 | ||
6d2ebf8b | 10716 | @node Checks |
79a6e687 | 10717 | @section Type and Range Checking |
c906108c SS |
10718 | |
10719 | @quotation | |
10720 | @emph{Warning:} In this release, the @value{GDBN} commands for type and range | |
10721 | checking are included, but they do not yet have any effect. This | |
10722 | section documents the intended facilities. | |
10723 | @end quotation | |
10724 | @c FIXME remove warning when type/range code added | |
10725 | ||
10726 | Some languages are designed to guard you against making seemingly common | |
10727 | errors through a series of compile- and run-time checks. These include | |
10728 | checking the type of arguments to functions and operators, and making | |
10729 | sure mathematical overflows are caught at run time. Checks such as | |
10730 | these help to ensure a program's correctness once it has been compiled | |
10731 | by eliminating type mismatches, and providing active checks for range | |
10732 | errors when your program is running. | |
10733 | ||
10734 | @value{GDBN} can check for conditions like the above if you wish. | |
9c16f35a EZ |
10735 | Although @value{GDBN} does not check the statements in your program, |
10736 | it can check expressions entered directly into @value{GDBN} for | |
10737 | evaluation via the @code{print} command, for example. As with the | |
10738 | working language, @value{GDBN} can also decide whether or not to check | |
10739 | automatically based on your program's source language. | |
79a6e687 | 10740 | @xref{Supported Languages, ,Supported Languages}, for the default |
9c16f35a | 10741 | settings of supported languages. |
c906108c SS |
10742 | |
10743 | @menu | |
10744 | * Type Checking:: An overview of type checking | |
10745 | * Range Checking:: An overview of range checking | |
10746 | @end menu | |
10747 | ||
10748 | @cindex type checking | |
10749 | @cindex checks, type | |
6d2ebf8b | 10750 | @node Type Checking |
79a6e687 | 10751 | @subsection An Overview of Type Checking |
c906108c SS |
10752 | |
10753 | Some languages, such as Modula-2, are strongly typed, meaning that the | |
10754 | arguments to operators and functions have to be of the correct type, | |
10755 | otherwise an error occurs. These checks prevent type mismatch | |
10756 | errors from ever causing any run-time problems. For example, | |
10757 | ||
10758 | @smallexample | |
10759 | 1 + 2 @result{} 3 | |
10760 | @exdent but | |
10761 | @error{} 1 + 2.3 | |
10762 | @end smallexample | |
10763 | ||
10764 | The second example fails because the @code{CARDINAL} 1 is not | |
10765 | type-compatible with the @code{REAL} 2.3. | |
10766 | ||
5d161b24 DB |
10767 | For the expressions you use in @value{GDBN} commands, you can tell the |
10768 | @value{GDBN} type checker to skip checking; | |
10769 | to treat any mismatches as errors and abandon the expression; | |
10770 | or to only issue warnings when type mismatches occur, | |
c906108c SS |
10771 | but evaluate the expression anyway. When you choose the last of |
10772 | these, @value{GDBN} evaluates expressions like the second example above, but | |
10773 | also issues a warning. | |
10774 | ||
5d161b24 DB |
10775 | Even if you turn type checking off, there may be other reasons |
10776 | related to type that prevent @value{GDBN} from evaluating an expression. | |
10777 | For instance, @value{GDBN} does not know how to add an @code{int} and | |
10778 | a @code{struct foo}. These particular type errors have nothing to do | |
10779 | with the language in use, and usually arise from expressions, such as | |
c906108c SS |
10780 | the one described above, which make little sense to evaluate anyway. |
10781 | ||
10782 | Each language defines to what degree it is strict about type. For | |
10783 | instance, both Modula-2 and C require the arguments to arithmetical | |
10784 | operators to be numbers. In C, enumerated types and pointers can be | |
10785 | represented as numbers, so that they are valid arguments to mathematical | |
79a6e687 | 10786 | operators. @xref{Supported Languages, ,Supported Languages}, for further |
c906108c SS |
10787 | details on specific languages. |
10788 | ||
10789 | @value{GDBN} provides some additional commands for controlling the type checker: | |
10790 | ||
c906108c SS |
10791 | @kindex set check type |
10792 | @kindex show check type | |
10793 | @table @code | |
10794 | @item set check type auto | |
10795 | Set type checking on or off based on the current working language. | |
79a6e687 | 10796 | @xref{Supported Languages, ,Supported Languages}, for the default settings for |
c906108c SS |
10797 | each language. |
10798 | ||
10799 | @item set check type on | |
10800 | @itemx set check type off | |
10801 | Set type checking on or off, overriding the default setting for the | |
10802 | current working language. Issue a warning if the setting does not | |
10803 | match the language default. If any type mismatches occur in | |
d4f3574e | 10804 | evaluating an expression while type checking is on, @value{GDBN} prints a |
c906108c SS |
10805 | message and aborts evaluation of the expression. |
10806 | ||
10807 | @item set check type warn | |
10808 | Cause the type checker to issue warnings, but to always attempt to | |
10809 | evaluate the expression. Evaluating the expression may still | |
10810 | be impossible for other reasons. For example, @value{GDBN} cannot add | |
10811 | numbers and structures. | |
10812 | ||
10813 | @item show type | |
5d161b24 | 10814 | Show the current setting of the type checker, and whether or not @value{GDBN} |
c906108c SS |
10815 | is setting it automatically. |
10816 | @end table | |
10817 | ||
10818 | @cindex range checking | |
10819 | @cindex checks, range | |
6d2ebf8b | 10820 | @node Range Checking |
79a6e687 | 10821 | @subsection An Overview of Range Checking |
c906108c SS |
10822 | |
10823 | In some languages (such as Modula-2), it is an error to exceed the | |
10824 | bounds of a type; this is enforced with run-time checks. Such range | |
10825 | checking is meant to ensure program correctness by making sure | |
10826 | computations do not overflow, or indices on an array element access do | |
10827 | not exceed the bounds of the array. | |
10828 | ||
10829 | For expressions you use in @value{GDBN} commands, you can tell | |
10830 | @value{GDBN} to treat range errors in one of three ways: ignore them, | |
10831 | always treat them as errors and abandon the expression, or issue | |
10832 | warnings but evaluate the expression anyway. | |
10833 | ||
10834 | A range error can result from numerical overflow, from exceeding an | |
10835 | array index bound, or when you type a constant that is not a member | |
10836 | of any type. Some languages, however, do not treat overflows as an | |
10837 | error. In many implementations of C, mathematical overflow causes the | |
10838 | result to ``wrap around'' to lower values---for example, if @var{m} is | |
10839 | the largest integer value, and @var{s} is the smallest, then | |
10840 | ||
474c8240 | 10841 | @smallexample |
c906108c | 10842 | @var{m} + 1 @result{} @var{s} |
474c8240 | 10843 | @end smallexample |
c906108c SS |
10844 | |
10845 | This, too, is specific to individual languages, and in some cases | |
79a6e687 BW |
10846 | specific to individual compilers or machines. @xref{Supported Languages, , |
10847 | Supported Languages}, for further details on specific languages. | |
c906108c SS |
10848 | |
10849 | @value{GDBN} provides some additional commands for controlling the range checker: | |
10850 | ||
c906108c SS |
10851 | @kindex set check range |
10852 | @kindex show check range | |
10853 | @table @code | |
10854 | @item set check range auto | |
10855 | Set range checking on or off based on the current working language. | |
79a6e687 | 10856 | @xref{Supported Languages, ,Supported Languages}, for the default settings for |
c906108c SS |
10857 | each language. |
10858 | ||
10859 | @item set check range on | |
10860 | @itemx set check range off | |
10861 | Set range checking on or off, overriding the default setting for the | |
10862 | current working language. A warning is issued if the setting does not | |
c3f6f71d JM |
10863 | match the language default. If a range error occurs and range checking is on, |
10864 | then a message is printed and evaluation of the expression is aborted. | |
c906108c SS |
10865 | |
10866 | @item set check range warn | |
10867 | Output messages when the @value{GDBN} range checker detects a range error, | |
10868 | but attempt to evaluate the expression anyway. Evaluating the | |
10869 | expression may still be impossible for other reasons, such as accessing | |
10870 | memory that the process does not own (a typical example from many Unix | |
10871 | systems). | |
10872 | ||
10873 | @item show range | |
10874 | Show the current setting of the range checker, and whether or not it is | |
10875 | being set automatically by @value{GDBN}. | |
10876 | @end table | |
c906108c | 10877 | |
79a6e687 BW |
10878 | @node Supported Languages |
10879 | @section Supported Languages | |
c906108c | 10880 | |
9c16f35a EZ |
10881 | @value{GDBN} supports C, C@t{++}, Objective-C, Fortran, Java, Pascal, |
10882 | assembly, Modula-2, and Ada. | |
cce74817 | 10883 | @c This is false ... |
c906108c SS |
10884 | Some @value{GDBN} features may be used in expressions regardless of the |
10885 | language you use: the @value{GDBN} @code{@@} and @code{::} operators, | |
10886 | and the @samp{@{type@}addr} construct (@pxref{Expressions, | |
10887 | ,Expressions}) can be used with the constructs of any supported | |
10888 | language. | |
10889 | ||
10890 | The following sections detail to what degree each source language is | |
10891 | supported by @value{GDBN}. These sections are not meant to be language | |
10892 | tutorials or references, but serve only as a reference guide to what the | |
10893 | @value{GDBN} expression parser accepts, and what input and output | |
10894 | formats should look like for different languages. There are many good | |
10895 | books written on each of these languages; please look to these for a | |
10896 | language reference or tutorial. | |
10897 | ||
c906108c | 10898 | @menu |
b37303ee | 10899 | * C:: C and C@t{++} |
b383017d | 10900 | * Objective-C:: Objective-C |
09d4efe1 | 10901 | * Fortran:: Fortran |
9c16f35a | 10902 | * Pascal:: Pascal |
b37303ee | 10903 | * Modula-2:: Modula-2 |
e07c999f | 10904 | * Ada:: Ada |
c906108c SS |
10905 | @end menu |
10906 | ||
6d2ebf8b | 10907 | @node C |
b37052ae | 10908 | @subsection C and C@t{++} |
7a292a7a | 10909 | |
b37052ae EZ |
10910 | @cindex C and C@t{++} |
10911 | @cindex expressions in C or C@t{++} | |
c906108c | 10912 | |
b37052ae | 10913 | Since C and C@t{++} are so closely related, many features of @value{GDBN} apply |
c906108c SS |
10914 | to both languages. Whenever this is the case, we discuss those languages |
10915 | together. | |
10916 | ||
41afff9a EZ |
10917 | @cindex C@t{++} |
10918 | @cindex @code{g++}, @sc{gnu} C@t{++} compiler | |
b37052ae EZ |
10919 | @cindex @sc{gnu} C@t{++} |
10920 | The C@t{++} debugging facilities are jointly implemented by the C@t{++} | |
10921 | compiler and @value{GDBN}. Therefore, to debug your C@t{++} code | |
10922 | effectively, you must compile your C@t{++} programs with a supported | |
10923 | C@t{++} compiler, such as @sc{gnu} @code{g++}, or the HP ANSI C@t{++} | |
c906108c SS |
10924 | compiler (@code{aCC}). |
10925 | ||
0179ffac DC |
10926 | For best results when using @sc{gnu} C@t{++}, use the DWARF 2 debugging |
10927 | format; if it doesn't work on your system, try the stabs+ debugging | |
10928 | format. You can select those formats explicitly with the @code{g++} | |
10929 | command-line options @option{-gdwarf-2} and @option{-gstabs+}. | |
ce9341a1 BW |
10930 | @xref{Debugging Options,,Options for Debugging Your Program or GCC, |
10931 | gcc.info, Using the @sc{gnu} Compiler Collection (GCC)}. | |
c906108c | 10932 | |
c906108c | 10933 | @menu |
b37052ae EZ |
10934 | * C Operators:: C and C@t{++} operators |
10935 | * C Constants:: C and C@t{++} constants | |
79a6e687 | 10936 | * C Plus Plus Expressions:: C@t{++} expressions |
b37052ae EZ |
10937 | * C Defaults:: Default settings for C and C@t{++} |
10938 | * C Checks:: C and C@t{++} type and range checks | |
c906108c | 10939 | * Debugging C:: @value{GDBN} and C |
79a6e687 | 10940 | * Debugging C Plus Plus:: @value{GDBN} features for C@t{++} |
febe4383 | 10941 | * Decimal Floating Point:: Numbers in Decimal Floating Point format |
c906108c | 10942 | @end menu |
c906108c | 10943 | |
6d2ebf8b | 10944 | @node C Operators |
79a6e687 | 10945 | @subsubsection C and C@t{++} Operators |
7a292a7a | 10946 | |
b37052ae | 10947 | @cindex C and C@t{++} operators |
c906108c SS |
10948 | |
10949 | Operators must be defined on values of specific types. For instance, | |
10950 | @code{+} is defined on numbers, but not on structures. Operators are | |
5d161b24 | 10951 | often defined on groups of types. |
c906108c | 10952 | |
b37052ae | 10953 | For the purposes of C and C@t{++}, the following definitions hold: |
c906108c SS |
10954 | |
10955 | @itemize @bullet | |
53a5351d | 10956 | |
c906108c | 10957 | @item |
c906108c | 10958 | @emph{Integral types} include @code{int} with any of its storage-class |
b37052ae | 10959 | specifiers; @code{char}; @code{enum}; and, for C@t{++}, @code{bool}. |
c906108c SS |
10960 | |
10961 | @item | |
d4f3574e SS |
10962 | @emph{Floating-point types} include @code{float}, @code{double}, and |
10963 | @code{long double} (if supported by the target platform). | |
c906108c SS |
10964 | |
10965 | @item | |
53a5351d | 10966 | @emph{Pointer types} include all types defined as @code{(@var{type} *)}. |
c906108c SS |
10967 | |
10968 | @item | |
10969 | @emph{Scalar types} include all of the above. | |
53a5351d | 10970 | |
c906108c SS |
10971 | @end itemize |
10972 | ||
10973 | @noindent | |
10974 | The following operators are supported. They are listed here | |
10975 | in order of increasing precedence: | |
10976 | ||
10977 | @table @code | |
10978 | @item , | |
10979 | The comma or sequencing operator. Expressions in a comma-separated list | |
10980 | are evaluated from left to right, with the result of the entire | |
10981 | expression being the last expression evaluated. | |
10982 | ||
10983 | @item = | |
10984 | Assignment. The value of an assignment expression is the value | |
10985 | assigned. Defined on scalar types. | |
10986 | ||
10987 | @item @var{op}= | |
10988 | Used in an expression of the form @w{@code{@var{a} @var{op}= @var{b}}}, | |
10989 | and translated to @w{@code{@var{a} = @var{a op b}}}. | |
d4f3574e | 10990 | @w{@code{@var{op}=}} and @code{=} have the same precedence. |
c906108c SS |
10991 | @var{op} is any one of the operators @code{|}, @code{^}, @code{&}, |
10992 | @code{<<}, @code{>>}, @code{+}, @code{-}, @code{*}, @code{/}, @code{%}. | |
10993 | ||
10994 | @item ?: | |
10995 | The ternary operator. @code{@var{a} ? @var{b} : @var{c}} can be thought | |
10996 | of as: if @var{a} then @var{b} else @var{c}. @var{a} should be of an | |
10997 | integral type. | |
10998 | ||
10999 | @item || | |
11000 | Logical @sc{or}. Defined on integral types. | |
11001 | ||
11002 | @item && | |
11003 | Logical @sc{and}. Defined on integral types. | |
11004 | ||
11005 | @item | | |
11006 | Bitwise @sc{or}. Defined on integral types. | |
11007 | ||
11008 | @item ^ | |
11009 | Bitwise exclusive-@sc{or}. Defined on integral types. | |
11010 | ||
11011 | @item & | |
11012 | Bitwise @sc{and}. Defined on integral types. | |
11013 | ||
11014 | @item ==@r{, }!= | |
11015 | Equality and inequality. Defined on scalar types. The value of these | |
11016 | expressions is 0 for false and non-zero for true. | |
11017 | ||
11018 | @item <@r{, }>@r{, }<=@r{, }>= | |
11019 | Less than, greater than, less than or equal, greater than or equal. | |
11020 | Defined on scalar types. The value of these expressions is 0 for false | |
11021 | and non-zero for true. | |
11022 | ||
11023 | @item <<@r{, }>> | |
11024 | left shift, and right shift. Defined on integral types. | |
11025 | ||
11026 | @item @@ | |
11027 | The @value{GDBN} ``artificial array'' operator (@pxref{Expressions, ,Expressions}). | |
11028 | ||
11029 | @item +@r{, }- | |
11030 | Addition and subtraction. Defined on integral types, floating-point types and | |
11031 | pointer types. | |
11032 | ||
11033 | @item *@r{, }/@r{, }% | |
11034 | Multiplication, division, and modulus. Multiplication and division are | |
11035 | defined on integral and floating-point types. Modulus is defined on | |
11036 | integral types. | |
11037 | ||
11038 | @item ++@r{, }-- | |
11039 | Increment and decrement. When appearing before a variable, the | |
11040 | operation is performed before the variable is used in an expression; | |
11041 | when appearing after it, the variable's value is used before the | |
11042 | operation takes place. | |
11043 | ||
11044 | @item * | |
11045 | Pointer dereferencing. Defined on pointer types. Same precedence as | |
11046 | @code{++}. | |
11047 | ||
11048 | @item & | |
11049 | Address operator. Defined on variables. Same precedence as @code{++}. | |
11050 | ||
b37052ae EZ |
11051 | For debugging C@t{++}, @value{GDBN} implements a use of @samp{&} beyond what is |
11052 | allowed in the C@t{++} language itself: you can use @samp{&(&@var{ref})} | |
b17828ca | 11053 | to examine the address |
b37052ae | 11054 | where a C@t{++} reference variable (declared with @samp{&@var{ref}}) is |
c906108c | 11055 | stored. |
c906108c SS |
11056 | |
11057 | @item - | |
11058 | Negative. Defined on integral and floating-point types. Same | |
11059 | precedence as @code{++}. | |
11060 | ||
11061 | @item ! | |
11062 | Logical negation. Defined on integral types. Same precedence as | |
11063 | @code{++}. | |
11064 | ||
11065 | @item ~ | |
11066 | Bitwise complement operator. Defined on integral types. Same precedence as | |
11067 | @code{++}. | |
11068 | ||
11069 | ||
11070 | @item .@r{, }-> | |
11071 | Structure member, and pointer-to-structure member. For convenience, | |
11072 | @value{GDBN} regards the two as equivalent, choosing whether to dereference a | |
11073 | pointer based on the stored type information. | |
11074 | Defined on @code{struct} and @code{union} data. | |
11075 | ||
c906108c SS |
11076 | @item .*@r{, }->* |
11077 | Dereferences of pointers to members. | |
c906108c SS |
11078 | |
11079 | @item [] | |
11080 | Array indexing. @code{@var{a}[@var{i}]} is defined as | |
11081 | @code{*(@var{a}+@var{i})}. Same precedence as @code{->}. | |
11082 | ||
11083 | @item () | |
11084 | Function parameter list. Same precedence as @code{->}. | |
11085 | ||
c906108c | 11086 | @item :: |
b37052ae | 11087 | C@t{++} scope resolution operator. Defined on @code{struct}, @code{union}, |
7a292a7a | 11088 | and @code{class} types. |
c906108c SS |
11089 | |
11090 | @item :: | |
7a292a7a SS |
11091 | Doubled colons also represent the @value{GDBN} scope operator |
11092 | (@pxref{Expressions, ,Expressions}). Same precedence as @code{::}, | |
11093 | above. | |
c906108c SS |
11094 | @end table |
11095 | ||
c906108c SS |
11096 | If an operator is redefined in the user code, @value{GDBN} usually |
11097 | attempts to invoke the redefined version instead of using the operator's | |
11098 | predefined meaning. | |
c906108c | 11099 | |
6d2ebf8b | 11100 | @node C Constants |
79a6e687 | 11101 | @subsubsection C and C@t{++} Constants |
c906108c | 11102 | |
b37052ae | 11103 | @cindex C and C@t{++} constants |
c906108c | 11104 | |
b37052ae | 11105 | @value{GDBN} allows you to express the constants of C and C@t{++} in the |
c906108c | 11106 | following ways: |
c906108c SS |
11107 | |
11108 | @itemize @bullet | |
11109 | @item | |
11110 | Integer constants are a sequence of digits. Octal constants are | |
6ca652b0 EZ |
11111 | specified by a leading @samp{0} (i.e.@: zero), and hexadecimal constants |
11112 | by a leading @samp{0x} or @samp{0X}. Constants may also end with a letter | |
c906108c SS |
11113 | @samp{l}, specifying that the constant should be treated as a |
11114 | @code{long} value. | |
11115 | ||
11116 | @item | |
11117 | Floating point constants are a sequence of digits, followed by a decimal | |
11118 | point, followed by a sequence of digits, and optionally followed by an | |
11119 | exponent. An exponent is of the form: | |
11120 | @samp{@w{e@r{[[}+@r{]|}-@r{]}@var{nnn}}}, where @var{nnn} is another | |
11121 | sequence of digits. The @samp{+} is optional for positive exponents. | |
d4f3574e SS |
11122 | A floating-point constant may also end with a letter @samp{f} or |
11123 | @samp{F}, specifying that the constant should be treated as being of | |
11124 | the @code{float} (as opposed to the default @code{double}) type; or with | |
11125 | a letter @samp{l} or @samp{L}, which specifies a @code{long double} | |
11126 | constant. | |
c906108c SS |
11127 | |
11128 | @item | |
11129 | Enumerated constants consist of enumerated identifiers, or their | |
11130 | integral equivalents. | |
11131 | ||
11132 | @item | |
11133 | Character constants are a single character surrounded by single quotes | |
11134 | (@code{'}), or a number---the ordinal value of the corresponding character | |
d4f3574e | 11135 | (usually its @sc{ascii} value). Within quotes, the single character may |
c906108c SS |
11136 | be represented by a letter or by @dfn{escape sequences}, which are of |
11137 | the form @samp{\@var{nnn}}, where @var{nnn} is the octal representation | |
11138 | of the character's ordinal value; or of the form @samp{\@var{x}}, where | |
11139 | @samp{@var{x}} is a predefined special character---for example, | |
11140 | @samp{\n} for newline. | |
11141 | ||
11142 | @item | |
96a2c332 SS |
11143 | String constants are a sequence of character constants surrounded by |
11144 | double quotes (@code{"}). Any valid character constant (as described | |
11145 | above) may appear. Double quotes within the string must be preceded by | |
11146 | a backslash, so for instance @samp{"a\"b'c"} is a string of five | |
11147 | characters. | |
c906108c SS |
11148 | |
11149 | @item | |
11150 | Pointer constants are an integral value. You can also write pointers | |
11151 | to constants using the C operator @samp{&}. | |
11152 | ||
11153 | @item | |
11154 | Array constants are comma-separated lists surrounded by braces @samp{@{} | |
11155 | and @samp{@}}; for example, @samp{@{1,2,3@}} is a three-element array of | |
11156 | integers, @samp{@{@{1,2@}, @{3,4@}, @{5,6@}@}} is a three-by-two array, | |
11157 | and @samp{@{&"hi", &"there", &"fred"@}} is a three-element array of pointers. | |
11158 | @end itemize | |
11159 | ||
79a6e687 BW |
11160 | @node C Plus Plus Expressions |
11161 | @subsubsection C@t{++} Expressions | |
b37052ae EZ |
11162 | |
11163 | @cindex expressions in C@t{++} | |
11164 | @value{GDBN} expression handling can interpret most C@t{++} expressions. | |
11165 | ||
0179ffac DC |
11166 | @cindex debugging C@t{++} programs |
11167 | @cindex C@t{++} compilers | |
11168 | @cindex debug formats and C@t{++} | |
11169 | @cindex @value{NGCC} and C@t{++} | |
c906108c | 11170 | @quotation |
b37052ae | 11171 | @emph{Warning:} @value{GDBN} can only debug C@t{++} code if you use the |
0179ffac DC |
11172 | proper compiler and the proper debug format. Currently, @value{GDBN} |
11173 | works best when debugging C@t{++} code that is compiled with | |
11174 | @value{NGCC} 2.95.3 or with @value{NGCC} 3.1 or newer, using the options | |
11175 | @option{-gdwarf-2} or @option{-gstabs+}. DWARF 2 is preferred over | |
11176 | stabs+. Most configurations of @value{NGCC} emit either DWARF 2 or | |
11177 | stabs+ as their default debug format, so you usually don't need to | |
11178 | specify a debug format explicitly. Other compilers and/or debug formats | |
11179 | are likely to work badly or not at all when using @value{GDBN} to debug | |
11180 | C@t{++} code. | |
c906108c | 11181 | @end quotation |
c906108c SS |
11182 | |
11183 | @enumerate | |
11184 | ||
11185 | @cindex member functions | |
11186 | @item | |
11187 | Member function calls are allowed; you can use expressions like | |
11188 | ||
474c8240 | 11189 | @smallexample |
c906108c | 11190 | count = aml->GetOriginal(x, y) |
474c8240 | 11191 | @end smallexample |
c906108c | 11192 | |
41afff9a | 11193 | @vindex this@r{, inside C@t{++} member functions} |
b37052ae | 11194 | @cindex namespace in C@t{++} |
c906108c SS |
11195 | @item |
11196 | While a member function is active (in the selected stack frame), your | |
11197 | expressions have the same namespace available as the member function; | |
11198 | that is, @value{GDBN} allows implicit references to the class instance | |
b37052ae | 11199 | pointer @code{this} following the same rules as C@t{++}. |
c906108c | 11200 | |
c906108c | 11201 | @cindex call overloaded functions |
d4f3574e | 11202 | @cindex overloaded functions, calling |
b37052ae | 11203 | @cindex type conversions in C@t{++} |
c906108c SS |
11204 | @item |
11205 | You can call overloaded functions; @value{GDBN} resolves the function | |
d4f3574e | 11206 | call to the right definition, with some restrictions. @value{GDBN} does not |
c906108c SS |
11207 | perform overload resolution involving user-defined type conversions, |
11208 | calls to constructors, or instantiations of templates that do not exist | |
11209 | in the program. It also cannot handle ellipsis argument lists or | |
11210 | default arguments. | |
11211 | ||
11212 | It does perform integral conversions and promotions, floating-point | |
11213 | promotions, arithmetic conversions, pointer conversions, conversions of | |
11214 | class objects to base classes, and standard conversions such as those of | |
11215 | functions or arrays to pointers; it requires an exact match on the | |
11216 | number of function arguments. | |
11217 | ||
11218 | Overload resolution is always performed, unless you have specified | |
79a6e687 BW |
11219 | @code{set overload-resolution off}. @xref{Debugging C Plus Plus, |
11220 | ,@value{GDBN} Features for C@t{++}}. | |
c906108c | 11221 | |
d4f3574e | 11222 | You must specify @code{set overload-resolution off} in order to use an |
c906108c SS |
11223 | explicit function signature to call an overloaded function, as in |
11224 | @smallexample | |
11225 | p 'foo(char,int)'('x', 13) | |
11226 | @end smallexample | |
d4f3574e | 11227 | |
c906108c | 11228 | The @value{GDBN} command-completion facility can simplify this; |
79a6e687 | 11229 | see @ref{Completion, ,Command Completion}. |
c906108c | 11230 | |
c906108c SS |
11231 | @cindex reference declarations |
11232 | @item | |
b37052ae EZ |
11233 | @value{GDBN} understands variables declared as C@t{++} references; you can use |
11234 | them in expressions just as you do in C@t{++} source---they are automatically | |
c906108c SS |
11235 | dereferenced. |
11236 | ||
11237 | In the parameter list shown when @value{GDBN} displays a frame, the values of | |
11238 | reference variables are not displayed (unlike other variables); this | |
11239 | avoids clutter, since references are often used for large structures. | |
11240 | The @emph{address} of a reference variable is always shown, unless | |
11241 | you have specified @samp{set print address off}. | |
11242 | ||
11243 | @item | |
b37052ae | 11244 | @value{GDBN} supports the C@t{++} name resolution operator @code{::}---your |
c906108c SS |
11245 | expressions can use it just as expressions in your program do. Since |
11246 | one scope may be defined in another, you can use @code{::} repeatedly if | |
11247 | necessary, for example in an expression like | |
11248 | @samp{@var{scope1}::@var{scope2}::@var{name}}. @value{GDBN} also allows | |
b37052ae | 11249 | resolving name scope by reference to source files, in both C and C@t{++} |
79a6e687 | 11250 | debugging (@pxref{Variables, ,Program Variables}). |
c906108c SS |
11251 | @end enumerate |
11252 | ||
b37052ae | 11253 | In addition, when used with HP's C@t{++} compiler, @value{GDBN} supports |
53a5351d JM |
11254 | calling virtual functions correctly, printing out virtual bases of |
11255 | objects, calling functions in a base subobject, casting objects, and | |
11256 | invoking user-defined operators. | |
c906108c | 11257 | |
6d2ebf8b | 11258 | @node C Defaults |
79a6e687 | 11259 | @subsubsection C and C@t{++} Defaults |
7a292a7a | 11260 | |
b37052ae | 11261 | @cindex C and C@t{++} defaults |
c906108c | 11262 | |
c906108c SS |
11263 | If you allow @value{GDBN} to set type and range checking automatically, they |
11264 | both default to @code{off} whenever the working language changes to | |
b37052ae | 11265 | C or C@t{++}. This happens regardless of whether you or @value{GDBN} |
c906108c | 11266 | selects the working language. |
c906108c SS |
11267 | |
11268 | If you allow @value{GDBN} to set the language automatically, it | |
11269 | recognizes source files whose names end with @file{.c}, @file{.C}, or | |
11270 | @file{.cc}, etc, and when @value{GDBN} enters code compiled from one of | |
b37052ae | 11271 | these files, it sets the working language to C or C@t{++}. |
79a6e687 | 11272 | @xref{Automatically, ,Having @value{GDBN} Infer the Source Language}, |
c906108c SS |
11273 | for further details. |
11274 | ||
c906108c SS |
11275 | @c Type checking is (a) primarily motivated by Modula-2, and (b) |
11276 | @c unimplemented. If (b) changes, it might make sense to let this node | |
11277 | @c appear even if Mod-2 does not, but meanwhile ignore it. roland 16jul93. | |
7a292a7a | 11278 | |
6d2ebf8b | 11279 | @node C Checks |
79a6e687 | 11280 | @subsubsection C and C@t{++} Type and Range Checks |
7a292a7a | 11281 | |
b37052ae | 11282 | @cindex C and C@t{++} checks |
c906108c | 11283 | |
b37052ae | 11284 | By default, when @value{GDBN} parses C or C@t{++} expressions, type checking |
c906108c SS |
11285 | is not used. However, if you turn type checking on, @value{GDBN} |
11286 | considers two variables type equivalent if: | |
11287 | ||
11288 | @itemize @bullet | |
11289 | @item | |
11290 | The two variables are structured and have the same structure, union, or | |
11291 | enumerated tag. | |
11292 | ||
11293 | @item | |
11294 | The two variables have the same type name, or types that have been | |
11295 | declared equivalent through @code{typedef}. | |
11296 | ||
11297 | @ignore | |
11298 | @c leaving this out because neither J Gilmore nor R Pesch understand it. | |
11299 | @c FIXME--beers? | |
11300 | @item | |
11301 | The two @code{struct}, @code{union}, or @code{enum} variables are | |
11302 | declared in the same declaration. (Note: this may not be true for all C | |
11303 | compilers.) | |
11304 | @end ignore | |
11305 | @end itemize | |
11306 | ||
11307 | Range checking, if turned on, is done on mathematical operations. Array | |
11308 | indices are not checked, since they are often used to index a pointer | |
11309 | that is not itself an array. | |
c906108c | 11310 | |
6d2ebf8b | 11311 | @node Debugging C |
c906108c | 11312 | @subsubsection @value{GDBN} and C |
c906108c SS |
11313 | |
11314 | The @code{set print union} and @code{show print union} commands apply to | |
11315 | the @code{union} type. When set to @samp{on}, any @code{union} that is | |
7a292a7a SS |
11316 | inside a @code{struct} or @code{class} is also printed. Otherwise, it |
11317 | appears as @samp{@{...@}}. | |
c906108c SS |
11318 | |
11319 | The @code{@@} operator aids in the debugging of dynamic arrays, formed | |
11320 | with pointers and a memory allocation function. @xref{Expressions, | |
11321 | ,Expressions}. | |
11322 | ||
79a6e687 BW |
11323 | @node Debugging C Plus Plus |
11324 | @subsubsection @value{GDBN} Features for C@t{++} | |
c906108c | 11325 | |
b37052ae | 11326 | @cindex commands for C@t{++} |
7a292a7a | 11327 | |
b37052ae EZ |
11328 | Some @value{GDBN} commands are particularly useful with C@t{++}, and some are |
11329 | designed specifically for use with C@t{++}. Here is a summary: | |
c906108c SS |
11330 | |
11331 | @table @code | |
11332 | @cindex break in overloaded functions | |
11333 | @item @r{breakpoint menus} | |
11334 | When you want a breakpoint in a function whose name is overloaded, | |
6ba66d6a JB |
11335 | @value{GDBN} has the capability to display a menu of possible breakpoint |
11336 | locations to help you specify which function definition you want. | |
11337 | @xref{Ambiguous Expressions,,Ambiguous Expressions}. | |
c906108c | 11338 | |
b37052ae | 11339 | @cindex overloading in C@t{++} |
c906108c SS |
11340 | @item rbreak @var{regex} |
11341 | Setting breakpoints using regular expressions is helpful for setting | |
11342 | breakpoints on overloaded functions that are not members of any special | |
11343 | classes. | |
79a6e687 | 11344 | @xref{Set Breaks, ,Setting Breakpoints}. |
c906108c | 11345 | |
b37052ae | 11346 | @cindex C@t{++} exception handling |
c906108c SS |
11347 | @item catch throw |
11348 | @itemx catch catch | |
b37052ae | 11349 | Debug C@t{++} exception handling using these commands. @xref{Set |
79a6e687 | 11350 | Catchpoints, , Setting Catchpoints}. |
c906108c SS |
11351 | |
11352 | @cindex inheritance | |
11353 | @item ptype @var{typename} | |
11354 | Print inheritance relationships as well as other information for type | |
11355 | @var{typename}. | |
11356 | @xref{Symbols, ,Examining the Symbol Table}. | |
11357 | ||
b37052ae | 11358 | @cindex C@t{++} symbol display |
c906108c SS |
11359 | @item set print demangle |
11360 | @itemx show print demangle | |
11361 | @itemx set print asm-demangle | |
11362 | @itemx show print asm-demangle | |
b37052ae EZ |
11363 | Control whether C@t{++} symbols display in their source form, both when |
11364 | displaying code as C@t{++} source and when displaying disassemblies. | |
79a6e687 | 11365 | @xref{Print Settings, ,Print Settings}. |
c906108c SS |
11366 | |
11367 | @item set print object | |
11368 | @itemx show print object | |
11369 | Choose whether to print derived (actual) or declared types of objects. | |
79a6e687 | 11370 | @xref{Print Settings, ,Print Settings}. |
c906108c SS |
11371 | |
11372 | @item set print vtbl | |
11373 | @itemx show print vtbl | |
11374 | Control the format for printing virtual function tables. | |
79a6e687 | 11375 | @xref{Print Settings, ,Print Settings}. |
c906108c | 11376 | (The @code{vtbl} commands do not work on programs compiled with the HP |
b37052ae | 11377 | ANSI C@t{++} compiler (@code{aCC}).) |
c906108c SS |
11378 | |
11379 | @kindex set overload-resolution | |
d4f3574e | 11380 | @cindex overloaded functions, overload resolution |
c906108c | 11381 | @item set overload-resolution on |
b37052ae | 11382 | Enable overload resolution for C@t{++} expression evaluation. The default |
c906108c SS |
11383 | is on. For overloaded functions, @value{GDBN} evaluates the arguments |
11384 | and searches for a function whose signature matches the argument types, | |
79a6e687 BW |
11385 | using the standard C@t{++} conversion rules (see @ref{C Plus Plus |
11386 | Expressions, ,C@t{++} Expressions}, for details). | |
11387 | If it cannot find a match, it emits a message. | |
c906108c SS |
11388 | |
11389 | @item set overload-resolution off | |
b37052ae | 11390 | Disable overload resolution for C@t{++} expression evaluation. For |
c906108c SS |
11391 | overloaded functions that are not class member functions, @value{GDBN} |
11392 | chooses the first function of the specified name that it finds in the | |
11393 | symbol table, whether or not its arguments are of the correct type. For | |
11394 | overloaded functions that are class member functions, @value{GDBN} | |
11395 | searches for a function whose signature @emph{exactly} matches the | |
11396 | argument types. | |
c906108c | 11397 | |
9c16f35a EZ |
11398 | @kindex show overload-resolution |
11399 | @item show overload-resolution | |
11400 | Show the current setting of overload resolution. | |
11401 | ||
c906108c SS |
11402 | @item @r{Overloaded symbol names} |
11403 | You can specify a particular definition of an overloaded symbol, using | |
b37052ae | 11404 | the same notation that is used to declare such symbols in C@t{++}: type |
c906108c SS |
11405 | @code{@var{symbol}(@var{types})} rather than just @var{symbol}. You can |
11406 | also use the @value{GDBN} command-line word completion facilities to list the | |
11407 | available choices, or to finish the type list for you. | |
79a6e687 | 11408 | @xref{Completion,, Command Completion}, for details on how to do this. |
c906108c | 11409 | @end table |
c906108c | 11410 | |
febe4383 TJB |
11411 | @node Decimal Floating Point |
11412 | @subsubsection Decimal Floating Point format | |
11413 | @cindex decimal floating point format | |
11414 | ||
11415 | @value{GDBN} can examine, set and perform computations with numbers in | |
11416 | decimal floating point format, which in the C language correspond to the | |
11417 | @code{_Decimal32}, @code{_Decimal64} and @code{_Decimal128} types as | |
11418 | specified by the extension to support decimal floating-point arithmetic. | |
11419 | ||
11420 | There are two encodings in use, depending on the architecture: BID (Binary | |
11421 | Integer Decimal) for x86 and x86-64, and DPD (Densely Packed Decimal) for | |
99e008fe | 11422 | PowerPC. @value{GDBN} will use the appropriate encoding for the configured |
febe4383 TJB |
11423 | target. |
11424 | ||
11425 | Because of a limitation in @file{libdecnumber}, the library used by @value{GDBN} | |
11426 | to manipulate decimal floating point numbers, it is not possible to convert | |
11427 | (using a cast, for example) integers wider than 32-bit to decimal float. | |
11428 | ||
11429 | In addition, in order to imitate @value{GDBN}'s behaviour with binary floating | |
11430 | point computations, error checking in decimal float operations ignores | |
11431 | underflow, overflow and divide by zero exceptions. | |
11432 | ||
4acd40f3 | 11433 | In the PowerPC architecture, @value{GDBN} provides a set of pseudo-registers |
99e008fe EZ |
11434 | to inspect @code{_Decimal128} values stored in floating point registers. |
11435 | See @ref{PowerPC,,PowerPC} for more details. | |
4acd40f3 | 11436 | |
b37303ee AF |
11437 | @node Objective-C |
11438 | @subsection Objective-C | |
11439 | ||
11440 | @cindex Objective-C | |
11441 | This section provides information about some commands and command | |
721c2651 EZ |
11442 | options that are useful for debugging Objective-C code. See also |
11443 | @ref{Symbols, info classes}, and @ref{Symbols, info selectors}, for a | |
11444 | few more commands specific to Objective-C support. | |
b37303ee AF |
11445 | |
11446 | @menu | |
b383017d RM |
11447 | * Method Names in Commands:: |
11448 | * The Print Command with Objective-C:: | |
b37303ee AF |
11449 | @end menu |
11450 | ||
c8f4133a | 11451 | @node Method Names in Commands |
b37303ee AF |
11452 | @subsubsection Method Names in Commands |
11453 | ||
11454 | The following commands have been extended to accept Objective-C method | |
11455 | names as line specifications: | |
11456 | ||
11457 | @kindex clear@r{, and Objective-C} | |
11458 | @kindex break@r{, and Objective-C} | |
11459 | @kindex info line@r{, and Objective-C} | |
11460 | @kindex jump@r{, and Objective-C} | |
11461 | @kindex list@r{, and Objective-C} | |
11462 | @itemize | |
11463 | @item @code{clear} | |
11464 | @item @code{break} | |
11465 | @item @code{info line} | |
11466 | @item @code{jump} | |
11467 | @item @code{list} | |
11468 | @end itemize | |
11469 | ||
11470 | A fully qualified Objective-C method name is specified as | |
11471 | ||
11472 | @smallexample | |
11473 | -[@var{Class} @var{methodName}] | |
11474 | @end smallexample | |
11475 | ||
c552b3bb JM |
11476 | where the minus sign is used to indicate an instance method and a |
11477 | plus sign (not shown) is used to indicate a class method. The class | |
11478 | name @var{Class} and method name @var{methodName} are enclosed in | |
11479 | brackets, similar to the way messages are specified in Objective-C | |
11480 | source code. For example, to set a breakpoint at the @code{create} | |
11481 | instance method of class @code{Fruit} in the program currently being | |
11482 | debugged, enter: | |
b37303ee AF |
11483 | |
11484 | @smallexample | |
11485 | break -[Fruit create] | |
11486 | @end smallexample | |
11487 | ||
11488 | To list ten program lines around the @code{initialize} class method, | |
11489 | enter: | |
11490 | ||
11491 | @smallexample | |
11492 | list +[NSText initialize] | |
11493 | @end smallexample | |
11494 | ||
c552b3bb JM |
11495 | In the current version of @value{GDBN}, the plus or minus sign is |
11496 | required. In future versions of @value{GDBN}, the plus or minus | |
11497 | sign will be optional, but you can use it to narrow the search. It | |
11498 | is also possible to specify just a method name: | |
b37303ee AF |
11499 | |
11500 | @smallexample | |
11501 | break create | |
11502 | @end smallexample | |
11503 | ||
11504 | You must specify the complete method name, including any colons. If | |
11505 | your program's source files contain more than one @code{create} method, | |
11506 | you'll be presented with a numbered list of classes that implement that | |
11507 | method. Indicate your choice by number, or type @samp{0} to exit if | |
11508 | none apply. | |
11509 | ||
11510 | As another example, to clear a breakpoint established at the | |
11511 | @code{makeKeyAndOrderFront:} method of the @code{NSWindow} class, enter: | |
11512 | ||
11513 | @smallexample | |
11514 | clear -[NSWindow makeKeyAndOrderFront:] | |
11515 | @end smallexample | |
11516 | ||
11517 | @node The Print Command with Objective-C | |
11518 | @subsubsection The Print Command With Objective-C | |
721c2651 | 11519 | @cindex Objective-C, print objects |
c552b3bb JM |
11520 | @kindex print-object |
11521 | @kindex po @r{(@code{print-object})} | |
b37303ee | 11522 | |
c552b3bb | 11523 | The print command has also been extended to accept methods. For example: |
b37303ee AF |
11524 | |
11525 | @smallexample | |
c552b3bb | 11526 | print -[@var{object} hash] |
b37303ee AF |
11527 | @end smallexample |
11528 | ||
11529 | @cindex print an Objective-C object description | |
c552b3bb JM |
11530 | @cindex @code{_NSPrintForDebugger}, and printing Objective-C objects |
11531 | @noindent | |
11532 | will tell @value{GDBN} to send the @code{hash} message to @var{object} | |
11533 | and print the result. Also, an additional command has been added, | |
11534 | @code{print-object} or @code{po} for short, which is meant to print | |
11535 | the description of an object. However, this command may only work | |
11536 | with certain Objective-C libraries that have a particular hook | |
11537 | function, @code{_NSPrintForDebugger}, defined. | |
b37303ee | 11538 | |
09d4efe1 EZ |
11539 | @node Fortran |
11540 | @subsection Fortran | |
11541 | @cindex Fortran-specific support in @value{GDBN} | |
11542 | ||
814e32d7 WZ |
11543 | @value{GDBN} can be used to debug programs written in Fortran, but it |
11544 | currently supports only the features of Fortran 77 language. | |
11545 | ||
11546 | @cindex trailing underscore, in Fortran symbols | |
11547 | Some Fortran compilers (@sc{gnu} Fortran 77 and Fortran 95 compilers | |
11548 | among them) append an underscore to the names of variables and | |
11549 | functions. When you debug programs compiled by those compilers, you | |
11550 | will need to refer to variables and functions with a trailing | |
11551 | underscore. | |
11552 | ||
11553 | @menu | |
11554 | * Fortran Operators:: Fortran operators and expressions | |
11555 | * Fortran Defaults:: Default settings for Fortran | |
79a6e687 | 11556 | * Special Fortran Commands:: Special @value{GDBN} commands for Fortran |
814e32d7 WZ |
11557 | @end menu |
11558 | ||
11559 | @node Fortran Operators | |
79a6e687 | 11560 | @subsubsection Fortran Operators and Expressions |
814e32d7 WZ |
11561 | |
11562 | @cindex Fortran operators and expressions | |
11563 | ||
11564 | Operators must be defined on values of specific types. For instance, | |
11565 | @code{+} is defined on numbers, but not on characters or other non- | |
ff2587ec | 11566 | arithmetic types. Operators are often defined on groups of types. |
814e32d7 WZ |
11567 | |
11568 | @table @code | |
11569 | @item ** | |
99e008fe | 11570 | The exponentiation operator. It raises the first operand to the power |
814e32d7 WZ |
11571 | of the second one. |
11572 | ||
11573 | @item : | |
11574 | The range operator. Normally used in the form of array(low:high) to | |
11575 | represent a section of array. | |
68837c9d MD |
11576 | |
11577 | @item % | |
11578 | The access component operator. Normally used to access elements in derived | |
11579 | types. Also suitable for unions. As unions aren't part of regular Fortran, | |
11580 | this can only happen when accessing a register that uses a gdbarch-defined | |
11581 | union type. | |
814e32d7 WZ |
11582 | @end table |
11583 | ||
11584 | @node Fortran Defaults | |
11585 | @subsubsection Fortran Defaults | |
11586 | ||
11587 | @cindex Fortran Defaults | |
11588 | ||
11589 | Fortran symbols are usually case-insensitive, so @value{GDBN} by | |
11590 | default uses case-insensitive matches for Fortran symbols. You can | |
11591 | change that with the @samp{set case-insensitive} command, see | |
11592 | @ref{Symbols}, for the details. | |
11593 | ||
79a6e687 BW |
11594 | @node Special Fortran Commands |
11595 | @subsubsection Special Fortran Commands | |
814e32d7 WZ |
11596 | |
11597 | @cindex Special Fortran commands | |
11598 | ||
db2e3e2e BW |
11599 | @value{GDBN} has some commands to support Fortran-specific features, |
11600 | such as displaying common blocks. | |
814e32d7 | 11601 | |
09d4efe1 EZ |
11602 | @table @code |
11603 | @cindex @code{COMMON} blocks, Fortran | |
11604 | @kindex info common | |
11605 | @item info common @r{[}@var{common-name}@r{]} | |
11606 | This command prints the values contained in the Fortran @code{COMMON} | |
11607 | block whose name is @var{common-name}. With no argument, the names of | |
d52fb0e9 | 11608 | all @code{COMMON} blocks visible at the current program location are |
09d4efe1 EZ |
11609 | printed. |
11610 | @end table | |
11611 | ||
9c16f35a EZ |
11612 | @node Pascal |
11613 | @subsection Pascal | |
11614 | ||
11615 | @cindex Pascal support in @value{GDBN}, limitations | |
11616 | Debugging Pascal programs which use sets, subranges, file variables, or | |
11617 | nested functions does not currently work. @value{GDBN} does not support | |
11618 | entering expressions, printing values, or similar features using Pascal | |
11619 | syntax. | |
11620 | ||
11621 | The Pascal-specific command @code{set print pascal_static-members} | |
11622 | controls whether static members of Pascal objects are displayed. | |
11623 | @xref{Print Settings, pascal_static-members}. | |
11624 | ||
09d4efe1 | 11625 | @node Modula-2 |
c906108c | 11626 | @subsection Modula-2 |
7a292a7a | 11627 | |
d4f3574e | 11628 | @cindex Modula-2, @value{GDBN} support |
c906108c SS |
11629 | |
11630 | The extensions made to @value{GDBN} to support Modula-2 only support | |
11631 | output from the @sc{gnu} Modula-2 compiler (which is currently being | |
11632 | developed). Other Modula-2 compilers are not currently supported, and | |
11633 | attempting to debug executables produced by them is most likely | |
11634 | to give an error as @value{GDBN} reads in the executable's symbol | |
11635 | table. | |
11636 | ||
11637 | @cindex expressions in Modula-2 | |
11638 | @menu | |
11639 | * M2 Operators:: Built-in operators | |
11640 | * Built-In Func/Proc:: Built-in functions and procedures | |
11641 | * M2 Constants:: Modula-2 constants | |
72019c9c | 11642 | * M2 Types:: Modula-2 types |
c906108c SS |
11643 | * M2 Defaults:: Default settings for Modula-2 |
11644 | * Deviations:: Deviations from standard Modula-2 | |
11645 | * M2 Checks:: Modula-2 type and range checks | |
11646 | * M2 Scope:: The scope operators @code{::} and @code{.} | |
11647 | * GDB/M2:: @value{GDBN} and Modula-2 | |
11648 | @end menu | |
11649 | ||
6d2ebf8b | 11650 | @node M2 Operators |
c906108c SS |
11651 | @subsubsection Operators |
11652 | @cindex Modula-2 operators | |
11653 | ||
11654 | Operators must be defined on values of specific types. For instance, | |
11655 | @code{+} is defined on numbers, but not on structures. Operators are | |
11656 | often defined on groups of types. For the purposes of Modula-2, the | |
11657 | following definitions hold: | |
11658 | ||
11659 | @itemize @bullet | |
11660 | ||
11661 | @item | |
11662 | @emph{Integral types} consist of @code{INTEGER}, @code{CARDINAL}, and | |
11663 | their subranges. | |
11664 | ||
11665 | @item | |
11666 | @emph{Character types} consist of @code{CHAR} and its subranges. | |
11667 | ||
11668 | @item | |
11669 | @emph{Floating-point types} consist of @code{REAL}. | |
11670 | ||
11671 | @item | |
11672 | @emph{Pointer types} consist of anything declared as @code{POINTER TO | |
11673 | @var{type}}. | |
11674 | ||
11675 | @item | |
11676 | @emph{Scalar types} consist of all of the above. | |
11677 | ||
11678 | @item | |
11679 | @emph{Set types} consist of @code{SET} and @code{BITSET} types. | |
11680 | ||
11681 | @item | |
11682 | @emph{Boolean types} consist of @code{BOOLEAN}. | |
11683 | @end itemize | |
11684 | ||
11685 | @noindent | |
11686 | The following operators are supported, and appear in order of | |
11687 | increasing precedence: | |
11688 | ||
11689 | @table @code | |
11690 | @item , | |
11691 | Function argument or array index separator. | |
11692 | ||
11693 | @item := | |
11694 | Assignment. The value of @var{var} @code{:=} @var{value} is | |
11695 | @var{value}. | |
11696 | ||
11697 | @item <@r{, }> | |
11698 | Less than, greater than on integral, floating-point, or enumerated | |
11699 | types. | |
11700 | ||
11701 | @item <=@r{, }>= | |
96a2c332 | 11702 | Less than or equal to, greater than or equal to |
c906108c SS |
11703 | on integral, floating-point and enumerated types, or set inclusion on |
11704 | set types. Same precedence as @code{<}. | |
11705 | ||
11706 | @item =@r{, }<>@r{, }# | |
11707 | Equality and two ways of expressing inequality, valid on scalar types. | |
11708 | Same precedence as @code{<}. In @value{GDBN} scripts, only @code{<>} is | |
11709 | available for inequality, since @code{#} conflicts with the script | |
11710 | comment character. | |
11711 | ||
11712 | @item IN | |
11713 | Set membership. Defined on set types and the types of their members. | |
11714 | Same precedence as @code{<}. | |
11715 | ||
11716 | @item OR | |
11717 | Boolean disjunction. Defined on boolean types. | |
11718 | ||
11719 | @item AND@r{, }& | |
d4f3574e | 11720 | Boolean conjunction. Defined on boolean types. |
c906108c SS |
11721 | |
11722 | @item @@ | |
11723 | The @value{GDBN} ``artificial array'' operator (@pxref{Expressions, ,Expressions}). | |
11724 | ||
11725 | @item +@r{, }- | |
11726 | Addition and subtraction on integral and floating-point types, or union | |
11727 | and difference on set types. | |
11728 | ||
11729 | @item * | |
11730 | Multiplication on integral and floating-point types, or set intersection | |
11731 | on set types. | |
11732 | ||
11733 | @item / | |
11734 | Division on floating-point types, or symmetric set difference on set | |
11735 | types. Same precedence as @code{*}. | |
11736 | ||
11737 | @item DIV@r{, }MOD | |
11738 | Integer division and remainder. Defined on integral types. Same | |
11739 | precedence as @code{*}. | |
11740 | ||
11741 | @item - | |
99e008fe | 11742 | Negative. Defined on @code{INTEGER} and @code{REAL} data. |
c906108c SS |
11743 | |
11744 | @item ^ | |
11745 | Pointer dereferencing. Defined on pointer types. | |
11746 | ||
11747 | @item NOT | |
11748 | Boolean negation. Defined on boolean types. Same precedence as | |
11749 | @code{^}. | |
11750 | ||
11751 | @item . | |
11752 | @code{RECORD} field selector. Defined on @code{RECORD} data. Same | |
11753 | precedence as @code{^}. | |
11754 | ||
11755 | @item [] | |
11756 | Array indexing. Defined on @code{ARRAY} data. Same precedence as @code{^}. | |
11757 | ||
11758 | @item () | |
11759 | Procedure argument list. Defined on @code{PROCEDURE} objects. Same precedence | |
11760 | as @code{^}. | |
11761 | ||
11762 | @item ::@r{, }. | |
11763 | @value{GDBN} and Modula-2 scope operators. | |
11764 | @end table | |
11765 | ||
11766 | @quotation | |
72019c9c | 11767 | @emph{Warning:} Set expressions and their operations are not yet supported, so @value{GDBN} |
c906108c SS |
11768 | treats the use of the operator @code{IN}, or the use of operators |
11769 | @code{+}, @code{-}, @code{*}, @code{/}, @code{=}, , @code{<>}, @code{#}, | |
11770 | @code{<=}, and @code{>=} on sets as an error. | |
11771 | @end quotation | |
11772 | ||
cb51c4e0 | 11773 | |
6d2ebf8b | 11774 | @node Built-In Func/Proc |
79a6e687 | 11775 | @subsubsection Built-in Functions and Procedures |
cb51c4e0 | 11776 | @cindex Modula-2 built-ins |
c906108c SS |
11777 | |
11778 | Modula-2 also makes available several built-in procedures and functions. | |
11779 | In describing these, the following metavariables are used: | |
11780 | ||
11781 | @table @var | |
11782 | ||
11783 | @item a | |
11784 | represents an @code{ARRAY} variable. | |
11785 | ||
11786 | @item c | |
11787 | represents a @code{CHAR} constant or variable. | |
11788 | ||
11789 | @item i | |
11790 | represents a variable or constant of integral type. | |
11791 | ||
11792 | @item m | |
11793 | represents an identifier that belongs to a set. Generally used in the | |
11794 | same function with the metavariable @var{s}. The type of @var{s} should | |
11795 | be @code{SET OF @var{mtype}} (where @var{mtype} is the type of @var{m}). | |
11796 | ||
11797 | @item n | |
11798 | represents a variable or constant of integral or floating-point type. | |
11799 | ||
11800 | @item r | |
11801 | represents a variable or constant of floating-point type. | |
11802 | ||
11803 | @item t | |
11804 | represents a type. | |
11805 | ||
11806 | @item v | |
11807 | represents a variable. | |
11808 | ||
11809 | @item x | |
11810 | represents a variable or constant of one of many types. See the | |
11811 | explanation of the function for details. | |
11812 | @end table | |
11813 | ||
11814 | All Modula-2 built-in procedures also return a result, described below. | |
11815 | ||
11816 | @table @code | |
11817 | @item ABS(@var{n}) | |
11818 | Returns the absolute value of @var{n}. | |
11819 | ||
11820 | @item CAP(@var{c}) | |
11821 | If @var{c} is a lower case letter, it returns its upper case | |
c3f6f71d | 11822 | equivalent, otherwise it returns its argument. |
c906108c SS |
11823 | |
11824 | @item CHR(@var{i}) | |
11825 | Returns the character whose ordinal value is @var{i}. | |
11826 | ||
11827 | @item DEC(@var{v}) | |
c3f6f71d | 11828 | Decrements the value in the variable @var{v} by one. Returns the new value. |
c906108c SS |
11829 | |
11830 | @item DEC(@var{v},@var{i}) | |
11831 | Decrements the value in the variable @var{v} by @var{i}. Returns the | |
11832 | new value. | |
11833 | ||
11834 | @item EXCL(@var{m},@var{s}) | |
11835 | Removes the element @var{m} from the set @var{s}. Returns the new | |
11836 | set. | |
11837 | ||
11838 | @item FLOAT(@var{i}) | |
11839 | Returns the floating point equivalent of the integer @var{i}. | |
11840 | ||
11841 | @item HIGH(@var{a}) | |
11842 | Returns the index of the last member of @var{a}. | |
11843 | ||
11844 | @item INC(@var{v}) | |
c3f6f71d | 11845 | Increments the value in the variable @var{v} by one. Returns the new value. |
c906108c SS |
11846 | |
11847 | @item INC(@var{v},@var{i}) | |
11848 | Increments the value in the variable @var{v} by @var{i}. Returns the | |
11849 | new value. | |
11850 | ||
11851 | @item INCL(@var{m},@var{s}) | |
11852 | Adds the element @var{m} to the set @var{s} if it is not already | |
11853 | there. Returns the new set. | |
11854 | ||
11855 | @item MAX(@var{t}) | |
11856 | Returns the maximum value of the type @var{t}. | |
11857 | ||
11858 | @item MIN(@var{t}) | |
11859 | Returns the minimum value of the type @var{t}. | |
11860 | ||
11861 | @item ODD(@var{i}) | |
11862 | Returns boolean TRUE if @var{i} is an odd number. | |
11863 | ||
11864 | @item ORD(@var{x}) | |
11865 | Returns the ordinal value of its argument. For example, the ordinal | |
c3f6f71d JM |
11866 | value of a character is its @sc{ascii} value (on machines supporting the |
11867 | @sc{ascii} character set). @var{x} must be of an ordered type, which include | |
c906108c SS |
11868 | integral, character and enumerated types. |
11869 | ||
11870 | @item SIZE(@var{x}) | |
11871 | Returns the size of its argument. @var{x} can be a variable or a type. | |
11872 | ||
11873 | @item TRUNC(@var{r}) | |
11874 | Returns the integral part of @var{r}. | |
11875 | ||
844781a1 GM |
11876 | @item TSIZE(@var{x}) |
11877 | Returns the size of its argument. @var{x} can be a variable or a type. | |
11878 | ||
c906108c SS |
11879 | @item VAL(@var{t},@var{i}) |
11880 | Returns the member of the type @var{t} whose ordinal value is @var{i}. | |
11881 | @end table | |
11882 | ||
11883 | @quotation | |
11884 | @emph{Warning:} Sets and their operations are not yet supported, so | |
11885 | @value{GDBN} treats the use of procedures @code{INCL} and @code{EXCL} as | |
11886 | an error. | |
11887 | @end quotation | |
11888 | ||
11889 | @cindex Modula-2 constants | |
6d2ebf8b | 11890 | @node M2 Constants |
c906108c SS |
11891 | @subsubsection Constants |
11892 | ||
11893 | @value{GDBN} allows you to express the constants of Modula-2 in the following | |
11894 | ways: | |
11895 | ||
11896 | @itemize @bullet | |
11897 | ||
11898 | @item | |
11899 | Integer constants are simply a sequence of digits. When used in an | |
11900 | expression, a constant is interpreted to be type-compatible with the | |
11901 | rest of the expression. Hexadecimal integers are specified by a | |
11902 | trailing @samp{H}, and octal integers by a trailing @samp{B}. | |
11903 | ||
11904 | @item | |
11905 | Floating point constants appear as a sequence of digits, followed by a | |
11906 | decimal point and another sequence of digits. An optional exponent can | |
11907 | then be specified, in the form @samp{E@r{[}+@r{|}-@r{]}@var{nnn}}, where | |
11908 | @samp{@r{[}+@r{|}-@r{]}@var{nnn}} is the desired exponent. All of the | |
11909 | digits of the floating point constant must be valid decimal (base 10) | |
11910 | digits. | |
11911 | ||
11912 | @item | |
11913 | Character constants consist of a single character enclosed by a pair of | |
11914 | like quotes, either single (@code{'}) or double (@code{"}). They may | |
c3f6f71d | 11915 | also be expressed by their ordinal value (their @sc{ascii} value, usually) |
c906108c SS |
11916 | followed by a @samp{C}. |
11917 | ||
11918 | @item | |
11919 | String constants consist of a sequence of characters enclosed by a | |
11920 | pair of like quotes, either single (@code{'}) or double (@code{"}). | |
11921 | Escape sequences in the style of C are also allowed. @xref{C | |
79a6e687 | 11922 | Constants, ,C and C@t{++} Constants}, for a brief explanation of escape |
c906108c SS |
11923 | sequences. |
11924 | ||
11925 | @item | |
11926 | Enumerated constants consist of an enumerated identifier. | |
11927 | ||
11928 | @item | |
11929 | Boolean constants consist of the identifiers @code{TRUE} and | |
11930 | @code{FALSE}. | |
11931 | ||
11932 | @item | |
11933 | Pointer constants consist of integral values only. | |
11934 | ||
11935 | @item | |
11936 | Set constants are not yet supported. | |
11937 | @end itemize | |
11938 | ||
72019c9c GM |
11939 | @node M2 Types |
11940 | @subsubsection Modula-2 Types | |
11941 | @cindex Modula-2 types | |
11942 | ||
11943 | Currently @value{GDBN} can print the following data types in Modula-2 | |
11944 | syntax: array types, record types, set types, pointer types, procedure | |
11945 | types, enumerated types, subrange types and base types. You can also | |
11946 | print the contents of variables declared using these type. | |
11947 | This section gives a number of simple source code examples together with | |
11948 | sample @value{GDBN} sessions. | |
11949 | ||
11950 | The first example contains the following section of code: | |
11951 | ||
11952 | @smallexample | |
11953 | VAR | |
11954 | s: SET OF CHAR ; | |
11955 | r: [20..40] ; | |
11956 | @end smallexample | |
11957 | ||
11958 | @noindent | |
11959 | and you can request @value{GDBN} to interrogate the type and value of | |
11960 | @code{r} and @code{s}. | |
11961 | ||
11962 | @smallexample | |
11963 | (@value{GDBP}) print s | |
11964 | @{'A'..'C', 'Z'@} | |
11965 | (@value{GDBP}) ptype s | |
11966 | SET OF CHAR | |
11967 | (@value{GDBP}) print r | |
11968 | 21 | |
11969 | (@value{GDBP}) ptype r | |
11970 | [20..40] | |
11971 | @end smallexample | |
11972 | ||
11973 | @noindent | |
11974 | Likewise if your source code declares @code{s} as: | |
11975 | ||
11976 | @smallexample | |
11977 | VAR | |
11978 | s: SET ['A'..'Z'] ; | |
11979 | @end smallexample | |
11980 | ||
11981 | @noindent | |
11982 | then you may query the type of @code{s} by: | |
11983 | ||
11984 | @smallexample | |
11985 | (@value{GDBP}) ptype s | |
11986 | type = SET ['A'..'Z'] | |
11987 | @end smallexample | |
11988 | ||
11989 | @noindent | |
11990 | Note that at present you cannot interactively manipulate set | |
11991 | expressions using the debugger. | |
11992 | ||
11993 | The following example shows how you might declare an array in Modula-2 | |
11994 | and how you can interact with @value{GDBN} to print its type and contents: | |
11995 | ||
11996 | @smallexample | |
11997 | VAR | |
11998 | s: ARRAY [-10..10] OF CHAR ; | |
11999 | @end smallexample | |
12000 | ||
12001 | @smallexample | |
12002 | (@value{GDBP}) ptype s | |
12003 | ARRAY [-10..10] OF CHAR | |
12004 | @end smallexample | |
12005 | ||
12006 | Note that the array handling is not yet complete and although the type | |
12007 | is printed correctly, expression handling still assumes that all | |
12008 | arrays have a lower bound of zero and not @code{-10} as in the example | |
844781a1 | 12009 | above. |
72019c9c GM |
12010 | |
12011 | Here are some more type related Modula-2 examples: | |
12012 | ||
12013 | @smallexample | |
12014 | TYPE | |
12015 | colour = (blue, red, yellow, green) ; | |
12016 | t = [blue..yellow] ; | |
12017 | VAR | |
12018 | s: t ; | |
12019 | BEGIN | |
12020 | s := blue ; | |
12021 | @end smallexample | |
12022 | ||
12023 | @noindent | |
12024 | The @value{GDBN} interaction shows how you can query the data type | |
12025 | and value of a variable. | |
12026 | ||
12027 | @smallexample | |
12028 | (@value{GDBP}) print s | |
12029 | $1 = blue | |
12030 | (@value{GDBP}) ptype t | |
12031 | type = [blue..yellow] | |
12032 | @end smallexample | |
12033 | ||
12034 | @noindent | |
12035 | In this example a Modula-2 array is declared and its contents | |
12036 | displayed. Observe that the contents are written in the same way as | |
12037 | their @code{C} counterparts. | |
12038 | ||
12039 | @smallexample | |
12040 | VAR | |
12041 | s: ARRAY [1..5] OF CARDINAL ; | |
12042 | BEGIN | |
12043 | s[1] := 1 ; | |
12044 | @end smallexample | |
12045 | ||
12046 | @smallexample | |
12047 | (@value{GDBP}) print s | |
12048 | $1 = @{1, 0, 0, 0, 0@} | |
12049 | (@value{GDBP}) ptype s | |
12050 | type = ARRAY [1..5] OF CARDINAL | |
12051 | @end smallexample | |
12052 | ||
12053 | The Modula-2 language interface to @value{GDBN} also understands | |
12054 | pointer types as shown in this example: | |
12055 | ||
12056 | @smallexample | |
12057 | VAR | |
12058 | s: POINTER TO ARRAY [1..5] OF CARDINAL ; | |
12059 | BEGIN | |
12060 | NEW(s) ; | |
12061 | s^[1] := 1 ; | |
12062 | @end smallexample | |
12063 | ||
12064 | @noindent | |
12065 | and you can request that @value{GDBN} describes the type of @code{s}. | |
12066 | ||
12067 | @smallexample | |
12068 | (@value{GDBP}) ptype s | |
12069 | type = POINTER TO ARRAY [1..5] OF CARDINAL | |
12070 | @end smallexample | |
12071 | ||
12072 | @value{GDBN} handles compound types as we can see in this example. | |
12073 | Here we combine array types, record types, pointer types and subrange | |
12074 | types: | |
12075 | ||
12076 | @smallexample | |
12077 | TYPE | |
12078 | foo = RECORD | |
12079 | f1: CARDINAL ; | |
12080 | f2: CHAR ; | |
12081 | f3: myarray ; | |
12082 | END ; | |
12083 | ||
12084 | myarray = ARRAY myrange OF CARDINAL ; | |
12085 | myrange = [-2..2] ; | |
12086 | VAR | |
12087 | s: POINTER TO ARRAY myrange OF foo ; | |
12088 | @end smallexample | |
12089 | ||
12090 | @noindent | |
12091 | and you can ask @value{GDBN} to describe the type of @code{s} as shown | |
12092 | below. | |
12093 | ||
12094 | @smallexample | |
12095 | (@value{GDBP}) ptype s | |
12096 | type = POINTER TO ARRAY [-2..2] OF foo = RECORD | |
12097 | f1 : CARDINAL; | |
12098 | f2 : CHAR; | |
12099 | f3 : ARRAY [-2..2] OF CARDINAL; | |
12100 | END | |
12101 | @end smallexample | |
12102 | ||
6d2ebf8b | 12103 | @node M2 Defaults |
79a6e687 | 12104 | @subsubsection Modula-2 Defaults |
c906108c SS |
12105 | @cindex Modula-2 defaults |
12106 | ||
12107 | If type and range checking are set automatically by @value{GDBN}, they | |
12108 | both default to @code{on} whenever the working language changes to | |
d4f3574e | 12109 | Modula-2. This happens regardless of whether you or @value{GDBN} |
c906108c SS |
12110 | selected the working language. |
12111 | ||
12112 | If you allow @value{GDBN} to set the language automatically, then entering | |
12113 | code compiled from a file whose name ends with @file{.mod} sets the | |
79a6e687 BW |
12114 | working language to Modula-2. @xref{Automatically, ,Having @value{GDBN} |
12115 | Infer the Source Language}, for further details. | |
c906108c | 12116 | |
6d2ebf8b | 12117 | @node Deviations |
79a6e687 | 12118 | @subsubsection Deviations from Standard Modula-2 |
c906108c SS |
12119 | @cindex Modula-2, deviations from |
12120 | ||
12121 | A few changes have been made to make Modula-2 programs easier to debug. | |
12122 | This is done primarily via loosening its type strictness: | |
12123 | ||
12124 | @itemize @bullet | |
12125 | @item | |
12126 | Unlike in standard Modula-2, pointer constants can be formed by | |
12127 | integers. This allows you to modify pointer variables during | |
12128 | debugging. (In standard Modula-2, the actual address contained in a | |
12129 | pointer variable is hidden from you; it can only be modified | |
12130 | through direct assignment to another pointer variable or expression that | |
12131 | returned a pointer.) | |
12132 | ||
12133 | @item | |
12134 | C escape sequences can be used in strings and characters to represent | |
12135 | non-printable characters. @value{GDBN} prints out strings with these | |
12136 | escape sequences embedded. Single non-printable characters are | |
12137 | printed using the @samp{CHR(@var{nnn})} format. | |
12138 | ||
12139 | @item | |
12140 | The assignment operator (@code{:=}) returns the value of its right-hand | |
12141 | argument. | |
12142 | ||
12143 | @item | |
12144 | All built-in procedures both modify @emph{and} return their argument. | |
12145 | @end itemize | |
12146 | ||
6d2ebf8b | 12147 | @node M2 Checks |
79a6e687 | 12148 | @subsubsection Modula-2 Type and Range Checks |
c906108c SS |
12149 | @cindex Modula-2 checks |
12150 | ||
12151 | @quotation | |
12152 | @emph{Warning:} in this release, @value{GDBN} does not yet perform type or | |
12153 | range checking. | |
12154 | @end quotation | |
12155 | @c FIXME remove warning when type/range checks added | |
12156 | ||
12157 | @value{GDBN} considers two Modula-2 variables type equivalent if: | |
12158 | ||
12159 | @itemize @bullet | |
12160 | @item | |
12161 | They are of types that have been declared equivalent via a @code{TYPE | |
12162 | @var{t1} = @var{t2}} statement | |
12163 | ||
12164 | @item | |
12165 | They have been declared on the same line. (Note: This is true of the | |
12166 | @sc{gnu} Modula-2 compiler, but it may not be true of other compilers.) | |
12167 | @end itemize | |
12168 | ||
12169 | As long as type checking is enabled, any attempt to combine variables | |
12170 | whose types are not equivalent is an error. | |
12171 | ||
12172 | Range checking is done on all mathematical operations, assignment, array | |
12173 | index bounds, and all built-in functions and procedures. | |
12174 | ||
6d2ebf8b | 12175 | @node M2 Scope |
79a6e687 | 12176 | @subsubsection The Scope Operators @code{::} and @code{.} |
c906108c | 12177 | @cindex scope |
41afff9a | 12178 | @cindex @code{.}, Modula-2 scope operator |
c906108c SS |
12179 | @cindex colon, doubled as scope operator |
12180 | @ifinfo | |
41afff9a | 12181 | @vindex colon-colon@r{, in Modula-2} |
c906108c SS |
12182 | @c Info cannot handle :: but TeX can. |
12183 | @end ifinfo | |
a67ec3f4 | 12184 | @ifnotinfo |
41afff9a | 12185 | @vindex ::@r{, in Modula-2} |
a67ec3f4 | 12186 | @end ifnotinfo |
c906108c SS |
12187 | |
12188 | There are a few subtle differences between the Modula-2 scope operator | |
12189 | (@code{.}) and the @value{GDBN} scope operator (@code{::}). The two have | |
12190 | similar syntax: | |
12191 | ||
474c8240 | 12192 | @smallexample |
c906108c SS |
12193 | |
12194 | @var{module} . @var{id} | |
12195 | @var{scope} :: @var{id} | |
474c8240 | 12196 | @end smallexample |
c906108c SS |
12197 | |
12198 | @noindent | |
12199 | where @var{scope} is the name of a module or a procedure, | |
12200 | @var{module} the name of a module, and @var{id} is any declared | |
12201 | identifier within your program, except another module. | |
12202 | ||
12203 | Using the @code{::} operator makes @value{GDBN} search the scope | |
12204 | specified by @var{scope} for the identifier @var{id}. If it is not | |
12205 | found in the specified scope, then @value{GDBN} searches all scopes | |
12206 | enclosing the one specified by @var{scope}. | |
12207 | ||
12208 | Using the @code{.} operator makes @value{GDBN} search the current scope for | |
12209 | the identifier specified by @var{id} that was imported from the | |
12210 | definition module specified by @var{module}. With this operator, it is | |
12211 | an error if the identifier @var{id} was not imported from definition | |
12212 | module @var{module}, or if @var{id} is not an identifier in | |
12213 | @var{module}. | |
12214 | ||
6d2ebf8b | 12215 | @node GDB/M2 |
c906108c SS |
12216 | @subsubsection @value{GDBN} and Modula-2 |
12217 | ||
12218 | Some @value{GDBN} commands have little use when debugging Modula-2 programs. | |
12219 | Five subcommands of @code{set print} and @code{show print} apply | |
b37052ae | 12220 | specifically to C and C@t{++}: @samp{vtbl}, @samp{demangle}, |
c906108c | 12221 | @samp{asm-demangle}, @samp{object}, and @samp{union}. The first four |
b37052ae | 12222 | apply to C@t{++}, and the last to the C @code{union} type, which has no direct |
c906108c SS |
12223 | analogue in Modula-2. |
12224 | ||
12225 | The @code{@@} operator (@pxref{Expressions, ,Expressions}), while available | |
d4f3574e | 12226 | with any language, is not useful with Modula-2. Its |
c906108c | 12227 | intent is to aid the debugging of @dfn{dynamic arrays}, which cannot be |
b37052ae | 12228 | created in Modula-2 as they can in C or C@t{++}. However, because an |
c906108c | 12229 | address can be specified by an integral constant, the construct |
d4f3574e | 12230 | @samp{@{@var{type}@}@var{adrexp}} is still useful. |
c906108c SS |
12231 | |
12232 | @cindex @code{#} in Modula-2 | |
12233 | In @value{GDBN} scripts, the Modula-2 inequality operator @code{#} is | |
12234 | interpreted as the beginning of a comment. Use @code{<>} instead. | |
c906108c | 12235 | |
e07c999f PH |
12236 | @node Ada |
12237 | @subsection Ada | |
12238 | @cindex Ada | |
12239 | ||
12240 | The extensions made to @value{GDBN} for Ada only support | |
12241 | output from the @sc{gnu} Ada (GNAT) compiler. | |
12242 | Other Ada compilers are not currently supported, and | |
12243 | attempting to debug executables produced by them is most likely | |
12244 | to be difficult. | |
12245 | ||
12246 | ||
12247 | @cindex expressions in Ada | |
12248 | @menu | |
12249 | * Ada Mode Intro:: General remarks on the Ada syntax | |
12250 | and semantics supported by Ada mode | |
12251 | in @value{GDBN}. | |
12252 | * Omissions from Ada:: Restrictions on the Ada expression syntax. | |
12253 | * Additions to Ada:: Extensions of the Ada expression syntax. | |
12254 | * Stopping Before Main Program:: Debugging the program during elaboration. | |
20924a55 JB |
12255 | * Ada Tasks:: Listing and setting breakpoints in tasks. |
12256 | * Ada Tasks and Core Files:: Tasking Support when Debugging Core Files | |
e07c999f PH |
12257 | * Ada Glitches:: Known peculiarities of Ada mode. |
12258 | @end menu | |
12259 | ||
12260 | @node Ada Mode Intro | |
12261 | @subsubsection Introduction | |
12262 | @cindex Ada mode, general | |
12263 | ||
12264 | The Ada mode of @value{GDBN} supports a fairly large subset of Ada expression | |
12265 | syntax, with some extensions. | |
12266 | The philosophy behind the design of this subset is | |
12267 | ||
12268 | @itemize @bullet | |
12269 | @item | |
12270 | That @value{GDBN} should provide basic literals and access to operations for | |
12271 | arithmetic, dereferencing, field selection, indexing, and subprogram calls, | |
12272 | leaving more sophisticated computations to subprograms written into the | |
12273 | program (which therefore may be called from @value{GDBN}). | |
12274 | ||
12275 | @item | |
12276 | That type safety and strict adherence to Ada language restrictions | |
12277 | are not particularly important to the @value{GDBN} user. | |
12278 | ||
12279 | @item | |
12280 | That brevity is important to the @value{GDBN} user. | |
12281 | @end itemize | |
12282 | ||
f3a2dd1a JB |
12283 | Thus, for brevity, the debugger acts as if all names declared in |
12284 | user-written packages are directly visible, even if they are not visible | |
12285 | according to Ada rules, thus making it unnecessary to fully qualify most | |
12286 | names with their packages, regardless of context. Where this causes | |
12287 | ambiguity, @value{GDBN} asks the user's intent. | |
e07c999f PH |
12288 | |
12289 | The debugger will start in Ada mode if it detects an Ada main program. | |
12290 | As for other languages, it will enter Ada mode when stopped in a program that | |
12291 | was translated from an Ada source file. | |
12292 | ||
12293 | While in Ada mode, you may use `@t{--}' for comments. This is useful | |
12294 | mostly for documenting command files. The standard @value{GDBN} comment | |
12295 | (@samp{#}) still works at the beginning of a line in Ada mode, but not in the | |
12296 | middle (to allow based literals). | |
12297 | ||
12298 | The debugger supports limited overloading. Given a subprogram call in which | |
12299 | the function symbol has multiple definitions, it will use the number of | |
12300 | actual parameters and some information about their types to attempt to narrow | |
12301 | the set of definitions. It also makes very limited use of context, preferring | |
12302 | procedures to functions in the context of the @code{call} command, and | |
12303 | functions to procedures elsewhere. | |
12304 | ||
12305 | @node Omissions from Ada | |
12306 | @subsubsection Omissions from Ada | |
12307 | @cindex Ada, omissions from | |
12308 | ||
12309 | Here are the notable omissions from the subset: | |
12310 | ||
12311 | @itemize @bullet | |
12312 | @item | |
12313 | Only a subset of the attributes are supported: | |
12314 | ||
12315 | @itemize @minus | |
12316 | @item | |
12317 | @t{'First}, @t{'Last}, and @t{'Length} | |
12318 | on array objects (not on types and subtypes). | |
12319 | ||
12320 | @item | |
12321 | @t{'Min} and @t{'Max}. | |
12322 | ||
12323 | @item | |
12324 | @t{'Pos} and @t{'Val}. | |
12325 | ||
12326 | @item | |
12327 | @t{'Tag}. | |
12328 | ||
12329 | @item | |
12330 | @t{'Range} on array objects (not subtypes), but only as the right | |
12331 | operand of the membership (@code{in}) operator. | |
12332 | ||
12333 | @item | |
12334 | @t{'Access}, @t{'Unchecked_Access}, and | |
12335 | @t{'Unrestricted_Access} (a GNAT extension). | |
12336 | ||
12337 | @item | |
12338 | @t{'Address}. | |
12339 | @end itemize | |
12340 | ||
12341 | @item | |
12342 | The names in | |
12343 | @code{Characters.Latin_1} are not available and | |
12344 | concatenation is not implemented. Thus, escape characters in strings are | |
12345 | not currently available. | |
12346 | ||
12347 | @item | |
12348 | Equality tests (@samp{=} and @samp{/=}) on arrays test for bitwise | |
12349 | equality of representations. They will generally work correctly | |
12350 | for strings and arrays whose elements have integer or enumeration types. | |
12351 | They may not work correctly for arrays whose element | |
12352 | types have user-defined equality, for arrays of real values | |
12353 | (in particular, IEEE-conformant floating point, because of negative | |
12354 | zeroes and NaNs), and for arrays whose elements contain unused bits with | |
12355 | indeterminate values. | |
12356 | ||
12357 | @item | |
12358 | The other component-by-component array operations (@code{and}, @code{or}, | |
12359 | @code{xor}, @code{not}, and relational tests other than equality) | |
12360 | are not implemented. | |
12361 | ||
12362 | @item | |
860701dc PH |
12363 | @cindex array aggregates (Ada) |
12364 | @cindex record aggregates (Ada) | |
12365 | @cindex aggregates (Ada) | |
12366 | There is limited support for array and record aggregates. They are | |
12367 | permitted only on the right sides of assignments, as in these examples: | |
12368 | ||
12369 | @smallexample | |
077e0a52 JB |
12370 | (@value{GDBP}) set An_Array := (1, 2, 3, 4, 5, 6) |
12371 | (@value{GDBP}) set An_Array := (1, others => 0) | |
12372 | (@value{GDBP}) set An_Array := (0|4 => 1, 1..3 => 2, 5 => 6) | |
12373 | (@value{GDBP}) set A_2D_Array := ((1, 2, 3), (4, 5, 6), (7, 8, 9)) | |
12374 | (@value{GDBP}) set A_Record := (1, "Peter", True); | |
12375 | (@value{GDBP}) set A_Record := (Name => "Peter", Id => 1, Alive => True) | |
860701dc PH |
12376 | @end smallexample |
12377 | ||
12378 | Changing a | |
12379 | discriminant's value by assigning an aggregate has an | |
12380 | undefined effect if that discriminant is used within the record. | |
12381 | However, you can first modify discriminants by directly assigning to | |
12382 | them (which normally would not be allowed in Ada), and then performing an | |
12383 | aggregate assignment. For example, given a variable @code{A_Rec} | |
12384 | declared to have a type such as: | |
12385 | ||
12386 | @smallexample | |
12387 | type Rec (Len : Small_Integer := 0) is record | |
12388 | Id : Integer; | |
12389 | Vals : IntArray (1 .. Len); | |
12390 | end record; | |
12391 | @end smallexample | |
12392 | ||
12393 | you can assign a value with a different size of @code{Vals} with two | |
12394 | assignments: | |
12395 | ||
12396 | @smallexample | |
077e0a52 JB |
12397 | (@value{GDBP}) set A_Rec.Len := 4 |
12398 | (@value{GDBP}) set A_Rec := (Id => 42, Vals => (1, 2, 3, 4)) | |
860701dc PH |
12399 | @end smallexample |
12400 | ||
12401 | As this example also illustrates, @value{GDBN} is very loose about the usual | |
12402 | rules concerning aggregates. You may leave out some of the | |
12403 | components of an array or record aggregate (such as the @code{Len} | |
12404 | component in the assignment to @code{A_Rec} above); they will retain their | |
12405 | original values upon assignment. You may freely use dynamic values as | |
12406 | indices in component associations. You may even use overlapping or | |
12407 | redundant component associations, although which component values are | |
12408 | assigned in such cases is not defined. | |
e07c999f PH |
12409 | |
12410 | @item | |
12411 | Calls to dispatching subprograms are not implemented. | |
12412 | ||
12413 | @item | |
12414 | The overloading algorithm is much more limited (i.e., less selective) | |
ae21e955 BW |
12415 | than that of real Ada. It makes only limited use of the context in |
12416 | which a subexpression appears to resolve its meaning, and it is much | |
12417 | looser in its rules for allowing type matches. As a result, some | |
12418 | function calls will be ambiguous, and the user will be asked to choose | |
12419 | the proper resolution. | |
e07c999f PH |
12420 | |
12421 | @item | |
12422 | The @code{new} operator is not implemented. | |
12423 | ||
12424 | @item | |
12425 | Entry calls are not implemented. | |
12426 | ||
12427 | @item | |
12428 | Aside from printing, arithmetic operations on the native VAX floating-point | |
12429 | formats are not supported. | |
12430 | ||
12431 | @item | |
12432 | It is not possible to slice a packed array. | |
158c7665 PH |
12433 | |
12434 | @item | |
12435 | The names @code{True} and @code{False}, when not part of a qualified name, | |
12436 | are interpreted as if implicitly prefixed by @code{Standard}, regardless of | |
12437 | context. | |
12438 | Should your program | |
12439 | redefine these names in a package or procedure (at best a dubious practice), | |
12440 | you will have to use fully qualified names to access their new definitions. | |
e07c999f PH |
12441 | @end itemize |
12442 | ||
12443 | @node Additions to Ada | |
12444 | @subsubsection Additions to Ada | |
12445 | @cindex Ada, deviations from | |
12446 | ||
12447 | As it does for other languages, @value{GDBN} makes certain generic | |
12448 | extensions to Ada (@pxref{Expressions}): | |
12449 | ||
12450 | @itemize @bullet | |
12451 | @item | |
ae21e955 BW |
12452 | If the expression @var{E} is a variable residing in memory (typically |
12453 | a local variable or array element) and @var{N} is a positive integer, | |
12454 | then @code{@var{E}@@@var{N}} displays the values of @var{E} and the | |
12455 | @var{N}-1 adjacent variables following it in memory as an array. In | |
12456 | Ada, this operator is generally not necessary, since its prime use is | |
12457 | in displaying parts of an array, and slicing will usually do this in | |
12458 | Ada. However, there are occasional uses when debugging programs in | |
12459 | which certain debugging information has been optimized away. | |
e07c999f PH |
12460 | |
12461 | @item | |
ae21e955 BW |
12462 | @code{@var{B}::@var{var}} means ``the variable named @var{var} that |
12463 | appears in function or file @var{B}.'' When @var{B} is a file name, | |
12464 | you must typically surround it in single quotes. | |
e07c999f PH |
12465 | |
12466 | @item | |
12467 | The expression @code{@{@var{type}@} @var{addr}} means ``the variable of type | |
12468 | @var{type} that appears at address @var{addr}.'' | |
12469 | ||
12470 | @item | |
12471 | A name starting with @samp{$} is a convenience variable | |
12472 | (@pxref{Convenience Vars}) or a machine register (@pxref{Registers}). | |
12473 | @end itemize | |
12474 | ||
ae21e955 BW |
12475 | In addition, @value{GDBN} provides a few other shortcuts and outright |
12476 | additions specific to Ada: | |
e07c999f PH |
12477 | |
12478 | @itemize @bullet | |
12479 | @item | |
12480 | The assignment statement is allowed as an expression, returning | |
12481 | its right-hand operand as its value. Thus, you may enter | |
12482 | ||
12483 | @smallexample | |
077e0a52 JB |
12484 | (@value{GDBP}) set x := y + 3 |
12485 | (@value{GDBP}) print A(tmp := y + 1) | |
e07c999f PH |
12486 | @end smallexample |
12487 | ||
12488 | @item | |
12489 | The semicolon is allowed as an ``operator,'' returning as its value | |
12490 | the value of its right-hand operand. | |
12491 | This allows, for example, | |
12492 | complex conditional breaks: | |
12493 | ||
12494 | @smallexample | |
077e0a52 JB |
12495 | (@value{GDBP}) break f |
12496 | (@value{GDBP}) condition 1 (report(i); k += 1; A(k) > 100) | |
e07c999f PH |
12497 | @end smallexample |
12498 | ||
12499 | @item | |
12500 | Rather than use catenation and symbolic character names to introduce special | |
12501 | characters into strings, one may instead use a special bracket notation, | |
12502 | which is also used to print strings. A sequence of characters of the form | |
12503 | @samp{["@var{XX}"]} within a string or character literal denotes the | |
12504 | (single) character whose numeric encoding is @var{XX} in hexadecimal. The | |
12505 | sequence of characters @samp{["""]} also denotes a single quotation mark | |
12506 | in strings. For example, | |
12507 | @smallexample | |
12508 | "One line.["0a"]Next line.["0a"]" | |
12509 | @end smallexample | |
12510 | @noindent | |
ae21e955 BW |
12511 | contains an ASCII newline character (@code{Ada.Characters.Latin_1.LF}) |
12512 | after each period. | |
e07c999f PH |
12513 | |
12514 | @item | |
12515 | The subtype used as a prefix for the attributes @t{'Pos}, @t{'Min}, and | |
12516 | @t{'Max} is optional (and is ignored in any case). For example, it is valid | |
12517 | to write | |
12518 | ||
12519 | @smallexample | |
077e0a52 | 12520 | (@value{GDBP}) print 'max(x, y) |
e07c999f PH |
12521 | @end smallexample |
12522 | ||
12523 | @item | |
12524 | When printing arrays, @value{GDBN} uses positional notation when the | |
12525 | array has a lower bound of 1, and uses a modified named notation otherwise. | |
ae21e955 BW |
12526 | For example, a one-dimensional array of three integers with a lower bound |
12527 | of 3 might print as | |
e07c999f PH |
12528 | |
12529 | @smallexample | |
12530 | (3 => 10, 17, 1) | |
12531 | @end smallexample | |
12532 | ||
12533 | @noindent | |
12534 | That is, in contrast to valid Ada, only the first component has a @code{=>} | |
12535 | clause. | |
12536 | ||
12537 | @item | |
12538 | You may abbreviate attributes in expressions with any unique, | |
12539 | multi-character subsequence of | |
12540 | their names (an exact match gets preference). | |
12541 | For example, you may use @t{a'len}, @t{a'gth}, or @t{a'lh} | |
12542 | in place of @t{a'length}. | |
12543 | ||
12544 | @item | |
12545 | @cindex quoting Ada internal identifiers | |
12546 | Since Ada is case-insensitive, the debugger normally maps identifiers you type | |
12547 | to lower case. The GNAT compiler uses upper-case characters for | |
12548 | some of its internal identifiers, which are normally of no interest to users. | |
12549 | For the rare occasions when you actually have to look at them, | |
12550 | enclose them in angle brackets to avoid the lower-case mapping. | |
12551 | For example, | |
12552 | @smallexample | |
077e0a52 | 12553 | (@value{GDBP}) print <JMPBUF_SAVE>[0] |
e07c999f PH |
12554 | @end smallexample |
12555 | ||
12556 | @item | |
12557 | Printing an object of class-wide type or dereferencing an | |
12558 | access-to-class-wide value will display all the components of the object's | |
12559 | specific type (as indicated by its run-time tag). Likewise, component | |
12560 | selection on such a value will operate on the specific type of the | |
12561 | object. | |
12562 | ||
12563 | @end itemize | |
12564 | ||
12565 | @node Stopping Before Main Program | |
12566 | @subsubsection Stopping at the Very Beginning | |
12567 | ||
12568 | @cindex breakpointing Ada elaboration code | |
12569 | It is sometimes necessary to debug the program during elaboration, and | |
12570 | before reaching the main procedure. | |
12571 | As defined in the Ada Reference | |
12572 | Manual, the elaboration code is invoked from a procedure called | |
12573 | @code{adainit}. To run your program up to the beginning of | |
12574 | elaboration, simply use the following two commands: | |
12575 | @code{tbreak adainit} and @code{run}. | |
12576 | ||
20924a55 JB |
12577 | @node Ada Tasks |
12578 | @subsubsection Extensions for Ada Tasks | |
12579 | @cindex Ada, tasking | |
12580 | ||
12581 | Support for Ada tasks is analogous to that for threads (@pxref{Threads}). | |
12582 | @value{GDBN} provides the following task-related commands: | |
12583 | ||
12584 | @table @code | |
12585 | @kindex info tasks | |
12586 | @item info tasks | |
12587 | This command shows a list of current Ada tasks, as in the following example: | |
12588 | ||
12589 | ||
12590 | @smallexample | |
12591 | @iftex | |
12592 | @leftskip=0.5cm | |
12593 | @end iftex | |
12594 | (@value{GDBP}) info tasks | |
12595 | ID TID P-ID Pri State Name | |
12596 | 1 8088000 0 15 Child Activation Wait main_task | |
12597 | 2 80a4000 1 15 Accept Statement b | |
12598 | 3 809a800 1 15 Child Activation Wait a | |
32cd1edc | 12599 | * 4 80ae800 3 15 Runnable c |
20924a55 JB |
12600 | |
12601 | @end smallexample | |
12602 | ||
12603 | @noindent | |
12604 | In this listing, the asterisk before the last task indicates it to be the | |
12605 | task currently being inspected. | |
12606 | ||
12607 | @table @asis | |
12608 | @item ID | |
12609 | Represents @value{GDBN}'s internal task number. | |
12610 | ||
12611 | @item TID | |
12612 | The Ada task ID. | |
12613 | ||
12614 | @item P-ID | |
12615 | The parent's task ID (@value{GDBN}'s internal task number). | |
12616 | ||
12617 | @item Pri | |
12618 | The base priority of the task. | |
12619 | ||
12620 | @item State | |
12621 | Current state of the task. | |
12622 | ||
12623 | @table @code | |
12624 | @item Unactivated | |
12625 | The task has been created but has not been activated. It cannot be | |
12626 | executing. | |
12627 | ||
20924a55 JB |
12628 | @item Runnable |
12629 | The task is not blocked for any reason known to Ada. (It may be waiting | |
12630 | for a mutex, though.) It is conceptually "executing" in normal mode. | |
12631 | ||
12632 | @item Terminated | |
12633 | The task is terminated, in the sense of ARM 9.3 (5). Any dependents | |
12634 | that were waiting on terminate alternatives have been awakened and have | |
12635 | terminated themselves. | |
12636 | ||
12637 | @item Child Activation Wait | |
12638 | The task is waiting for created tasks to complete activation. | |
12639 | ||
12640 | @item Accept Statement | |
12641 | The task is waiting on an accept or selective wait statement. | |
12642 | ||
12643 | @item Waiting on entry call | |
12644 | The task is waiting on an entry call. | |
12645 | ||
12646 | @item Async Select Wait | |
12647 | The task is waiting to start the abortable part of an asynchronous | |
12648 | select statement. | |
12649 | ||
12650 | @item Delay Sleep | |
12651 | The task is waiting on a select statement with only a delay | |
12652 | alternative open. | |
12653 | ||
12654 | @item Child Termination Wait | |
12655 | The task is sleeping having completed a master within itself, and is | |
12656 | waiting for the tasks dependent on that master to become terminated or | |
12657 | waiting on a terminate Phase. | |
12658 | ||
12659 | @item Wait Child in Term Alt | |
12660 | The task is sleeping waiting for tasks on terminate alternatives to | |
12661 | finish terminating. | |
12662 | ||
12663 | @item Accepting RV with @var{taskno} | |
12664 | The task is accepting a rendez-vous with the task @var{taskno}. | |
12665 | @end table | |
12666 | ||
12667 | @item Name | |
12668 | Name of the task in the program. | |
12669 | ||
12670 | @end table | |
12671 | ||
12672 | @kindex info task @var{taskno} | |
12673 | @item info task @var{taskno} | |
12674 | This command shows detailled informations on the specified task, as in | |
12675 | the following example: | |
12676 | @smallexample | |
12677 | @iftex | |
12678 | @leftskip=0.5cm | |
12679 | @end iftex | |
12680 | (@value{GDBP}) info tasks | |
12681 | ID TID P-ID Pri State Name | |
12682 | 1 8077880 0 15 Child Activation Wait main_task | |
32cd1edc | 12683 | * 2 807c468 1 15 Runnable task_1 |
20924a55 JB |
12684 | (@value{GDBP}) info task 2 |
12685 | Ada Task: 0x807c468 | |
12686 | Name: task_1 | |
12687 | Thread: 0x807f378 | |
12688 | Parent: 1 (main_task) | |
12689 | Base Priority: 15 | |
12690 | State: Runnable | |
12691 | @end smallexample | |
12692 | ||
12693 | @item task | |
12694 | @kindex task@r{ (Ada)} | |
12695 | @cindex current Ada task ID | |
12696 | This command prints the ID of the current task. | |
12697 | ||
12698 | @smallexample | |
12699 | @iftex | |
12700 | @leftskip=0.5cm | |
12701 | @end iftex | |
12702 | (@value{GDBP}) info tasks | |
12703 | ID TID P-ID Pri State Name | |
12704 | 1 8077870 0 15 Child Activation Wait main_task | |
32cd1edc | 12705 | * 2 807c458 1 15 Runnable t |
20924a55 JB |
12706 | (@value{GDBP}) task |
12707 | [Current task is 2] | |
12708 | @end smallexample | |
12709 | ||
12710 | @item task @var{taskno} | |
12711 | @cindex Ada task switching | |
12712 | This command is like the @code{thread @var{threadno}} | |
12713 | command (@pxref{Threads}). It switches the context of debugging | |
12714 | from the current task to the given task. | |
12715 | ||
12716 | @smallexample | |
12717 | @iftex | |
12718 | @leftskip=0.5cm | |
12719 | @end iftex | |
12720 | (@value{GDBP}) info tasks | |
12721 | ID TID P-ID Pri State Name | |
12722 | 1 8077870 0 15 Child Activation Wait main_task | |
32cd1edc | 12723 | * 2 807c458 1 15 Runnable t |
20924a55 JB |
12724 | (@value{GDBP}) task 1 |
12725 | [Switching to task 1] | |
12726 | #0 0x8067726 in pthread_cond_wait () | |
12727 | (@value{GDBP}) bt | |
12728 | #0 0x8067726 in pthread_cond_wait () | |
12729 | #1 0x8056714 in system.os_interface.pthread_cond_wait () | |
12730 | #2 0x805cb63 in system.task_primitives.operations.sleep () | |
12731 | #3 0x806153e in system.tasking.stages.activate_tasks () | |
12732 | #4 0x804aacc in un () at un.adb:5 | |
12733 | @end smallexample | |
12734 | ||
45ac276d JB |
12735 | @item break @var{linespec} task @var{taskno} |
12736 | @itemx break @var{linespec} task @var{taskno} if @dots{} | |
12737 | @cindex breakpoints and tasks, in Ada | |
12738 | @cindex task breakpoints, in Ada | |
12739 | @kindex break @dots{} task @var{taskno}@r{ (Ada)} | |
12740 | These commands are like the @code{break @dots{} thread @dots{}} | |
12741 | command (@pxref{Thread Stops}). | |
12742 | @var{linespec} specifies source lines, as described | |
12743 | in @ref{Specify Location}. | |
12744 | ||
12745 | Use the qualifier @samp{task @var{taskno}} with a breakpoint command | |
12746 | to specify that you only want @value{GDBN} to stop the program when a | |
12747 | particular Ada task reaches this breakpoint. @var{taskno} is one of the | |
12748 | numeric task identifiers assigned by @value{GDBN}, shown in the first | |
12749 | column of the @samp{info tasks} display. | |
12750 | ||
12751 | If you do not specify @samp{task @var{taskno}} when you set a | |
12752 | breakpoint, the breakpoint applies to @emph{all} tasks of your | |
12753 | program. | |
12754 | ||
12755 | You can use the @code{task} qualifier on conditional breakpoints as | |
12756 | well; in this case, place @samp{task @var{taskno}} before the | |
12757 | breakpoint condition (before the @code{if}). | |
12758 | ||
12759 | For example, | |
12760 | ||
12761 | @smallexample | |
12762 | @iftex | |
12763 | @leftskip=0.5cm | |
12764 | @end iftex | |
12765 | (@value{GDBP}) info tasks | |
12766 | ID TID P-ID Pri State Name | |
12767 | 1 140022020 0 15 Child Activation Wait main_task | |
12768 | 2 140045060 1 15 Accept/Select Wait t2 | |
12769 | 3 140044840 1 15 Runnable t1 | |
12770 | * 4 140056040 1 15 Runnable t3 | |
12771 | (@value{GDBP}) b 15 task 2 | |
12772 | Breakpoint 5 at 0x120044cb0: file test_task_debug.adb, line 15. | |
12773 | (@value{GDBP}) cont | |
12774 | Continuing. | |
12775 | task # 1 running | |
12776 | task # 2 running | |
12777 | ||
12778 | Breakpoint 5, test_task_debug () at test_task_debug.adb:15 | |
12779 | 15 flush; | |
12780 | (@value{GDBP}) info tasks | |
12781 | ID TID P-ID Pri State Name | |
12782 | 1 140022020 0 15 Child Activation Wait main_task | |
12783 | * 2 140045060 1 15 Runnable t2 | |
12784 | 3 140044840 1 15 Runnable t1 | |
12785 | 4 140056040 1 15 Delay Sleep t3 | |
12786 | @end smallexample | |
20924a55 JB |
12787 | @end table |
12788 | ||
12789 | @node Ada Tasks and Core Files | |
12790 | @subsubsection Tasking Support when Debugging Core Files | |
12791 | @cindex Ada tasking and core file debugging | |
12792 | ||
12793 | When inspecting a core file, as opposed to debugging a live program, | |
12794 | tasking support may be limited or even unavailable, depending on | |
12795 | the platform being used. | |
12796 | For instance, on x86-linux, the list of tasks is available, but task | |
12797 | switching is not supported. On Tru64, however, task switching will work | |
12798 | as usual. | |
12799 | ||
12800 | On certain platforms, including Tru64, the debugger needs to perform some | |
12801 | memory writes in order to provide Ada tasking support. When inspecting | |
12802 | a core file, this means that the core file must be opened with read-write | |
12803 | privileges, using the command @samp{"set write on"} (@pxref{Patching}). | |
12804 | Under these circumstances, you should make a backup copy of the core | |
12805 | file before inspecting it with @value{GDBN}. | |
12806 | ||
e07c999f PH |
12807 | @node Ada Glitches |
12808 | @subsubsection Known Peculiarities of Ada Mode | |
12809 | @cindex Ada, problems | |
12810 | ||
12811 | Besides the omissions listed previously (@pxref{Omissions from Ada}), | |
12812 | we know of several problems with and limitations of Ada mode in | |
12813 | @value{GDBN}, | |
12814 | some of which will be fixed with planned future releases of the debugger | |
12815 | and the GNU Ada compiler. | |
12816 | ||
12817 | @itemize @bullet | |
12818 | @item | |
12819 | Currently, the debugger | |
12820 | has insufficient information to determine whether certain pointers represent | |
12821 | pointers to objects or the objects themselves. | |
12822 | Thus, the user may have to tack an extra @code{.all} after an expression | |
12823 | to get it printed properly. | |
12824 | ||
12825 | @item | |
12826 | Static constants that the compiler chooses not to materialize as objects in | |
12827 | storage are invisible to the debugger. | |
12828 | ||
12829 | @item | |
12830 | Named parameter associations in function argument lists are ignored (the | |
12831 | argument lists are treated as positional). | |
12832 | ||
12833 | @item | |
12834 | Many useful library packages are currently invisible to the debugger. | |
12835 | ||
12836 | @item | |
12837 | Fixed-point arithmetic, conversions, input, and output is carried out using | |
12838 | floating-point arithmetic, and may give results that only approximate those on | |
12839 | the host machine. | |
12840 | ||
e07c999f PH |
12841 | @item |
12842 | The GNAT compiler never generates the prefix @code{Standard} for any of | |
12843 | the standard symbols defined by the Ada language. @value{GDBN} knows about | |
12844 | this: it will strip the prefix from names when you use it, and will never | |
12845 | look for a name you have so qualified among local symbols, nor match against | |
12846 | symbols in other packages or subprograms. If you have | |
12847 | defined entities anywhere in your program other than parameters and | |
12848 | local variables whose simple names match names in @code{Standard}, | |
12849 | GNAT's lack of qualification here can cause confusion. When this happens, | |
12850 | you can usually resolve the confusion | |
12851 | by qualifying the problematic names with package | |
12852 | @code{Standard} explicitly. | |
12853 | @end itemize | |
12854 | ||
95433b34 JB |
12855 | Older versions of the compiler sometimes generate erroneous debugging |
12856 | information, resulting in the debugger incorrectly printing the value | |
12857 | of affected entities. In some cases, the debugger is able to work | |
12858 | around an issue automatically. In other cases, the debugger is able | |
12859 | to work around the issue, but the work-around has to be specifically | |
12860 | enabled. | |
12861 | ||
12862 | @kindex set ada trust-PAD-over-XVS | |
12863 | @kindex show ada trust-PAD-over-XVS | |
12864 | @table @code | |
12865 | ||
12866 | @item set ada trust-PAD-over-XVS on | |
12867 | Configure GDB to strictly follow the GNAT encoding when computing the | |
12868 | value of Ada entities, particularly when @code{PAD} and @code{PAD___XVS} | |
12869 | types are involved (see @code{ada/exp_dbug.ads} in the GCC sources for | |
12870 | a complete description of the encoding used by the GNAT compiler). | |
12871 | This is the default. | |
12872 | ||
12873 | @item set ada trust-PAD-over-XVS off | |
12874 | This is related to the encoding using by the GNAT compiler. If @value{GDBN} | |
12875 | sometimes prints the wrong value for certain entities, changing @code{ada | |
12876 | trust-PAD-over-XVS} to @code{off} activates a work-around which may fix | |
12877 | the issue. It is always safe to set @code{ada trust-PAD-over-XVS} to | |
12878 | @code{off}, but this incurs a slight performance penalty, so it is | |
12879 | recommended to leave this setting to @code{on} unless necessary. | |
12880 | ||
12881 | @end table | |
12882 | ||
79a6e687 BW |
12883 | @node Unsupported Languages |
12884 | @section Unsupported Languages | |
4e562065 JB |
12885 | |
12886 | @cindex unsupported languages | |
12887 | @cindex minimal language | |
12888 | In addition to the other fully-supported programming languages, | |
12889 | @value{GDBN} also provides a pseudo-language, called @code{minimal}. | |
12890 | It does not represent a real programming language, but provides a set | |
12891 | of capabilities close to what the C or assembly languages provide. | |
12892 | This should allow most simple operations to be performed while debugging | |
12893 | an application that uses a language currently not supported by @value{GDBN}. | |
12894 | ||
12895 | If the language is set to @code{auto}, @value{GDBN} will automatically | |
12896 | select this language if the current frame corresponds to an unsupported | |
12897 | language. | |
12898 | ||
6d2ebf8b | 12899 | @node Symbols |
c906108c SS |
12900 | @chapter Examining the Symbol Table |
12901 | ||
d4f3574e | 12902 | The commands described in this chapter allow you to inquire about the |
c906108c SS |
12903 | symbols (names of variables, functions and types) defined in your |
12904 | program. This information is inherent in the text of your program and | |
12905 | does not change as your program executes. @value{GDBN} finds it in your | |
12906 | program's symbol table, in the file indicated when you started @value{GDBN} | |
79a6e687 BW |
12907 | (@pxref{File Options, ,Choosing Files}), or by one of the |
12908 | file-management commands (@pxref{Files, ,Commands to Specify Files}). | |
c906108c SS |
12909 | |
12910 | @cindex symbol names | |
12911 | @cindex names of symbols | |
12912 | @cindex quoting names | |
12913 | Occasionally, you may need to refer to symbols that contain unusual | |
12914 | characters, which @value{GDBN} ordinarily treats as word delimiters. The | |
12915 | most frequent case is in referring to static variables in other | |
79a6e687 | 12916 | source files (@pxref{Variables,,Program Variables}). File names |
c906108c SS |
12917 | are recorded in object files as debugging symbols, but @value{GDBN} would |
12918 | ordinarily parse a typical file name, like @file{foo.c}, as the three words | |
12919 | @samp{foo} @samp{.} @samp{c}. To allow @value{GDBN} to recognize | |
12920 | @samp{foo.c} as a single symbol, enclose it in single quotes; for example, | |
12921 | ||
474c8240 | 12922 | @smallexample |
c906108c | 12923 | p 'foo.c'::x |
474c8240 | 12924 | @end smallexample |
c906108c SS |
12925 | |
12926 | @noindent | |
12927 | looks up the value of @code{x} in the scope of the file @file{foo.c}. | |
12928 | ||
12929 | @table @code | |
a8f24a35 EZ |
12930 | @cindex case-insensitive symbol names |
12931 | @cindex case sensitivity in symbol names | |
12932 | @kindex set case-sensitive | |
12933 | @item set case-sensitive on | |
12934 | @itemx set case-sensitive off | |
12935 | @itemx set case-sensitive auto | |
12936 | Normally, when @value{GDBN} looks up symbols, it matches their names | |
12937 | with case sensitivity determined by the current source language. | |
12938 | Occasionally, you may wish to control that. The command @code{set | |
12939 | case-sensitive} lets you do that by specifying @code{on} for | |
12940 | case-sensitive matches or @code{off} for case-insensitive ones. If | |
12941 | you specify @code{auto}, case sensitivity is reset to the default | |
12942 | suitable for the source language. The default is case-sensitive | |
12943 | matches for all languages except for Fortran, for which the default is | |
12944 | case-insensitive matches. | |
12945 | ||
9c16f35a EZ |
12946 | @kindex show case-sensitive |
12947 | @item show case-sensitive | |
a8f24a35 EZ |
12948 | This command shows the current setting of case sensitivity for symbols |
12949 | lookups. | |
12950 | ||
c906108c | 12951 | @kindex info address |
b37052ae | 12952 | @cindex address of a symbol |
c906108c SS |
12953 | @item info address @var{symbol} |
12954 | Describe where the data for @var{symbol} is stored. For a register | |
12955 | variable, this says which register it is kept in. For a non-register | |
12956 | local variable, this prints the stack-frame offset at which the variable | |
12957 | is always stored. | |
12958 | ||
12959 | Note the contrast with @samp{print &@var{symbol}}, which does not work | |
12960 | at all for a register variable, and for a stack local variable prints | |
12961 | the exact address of the current instantiation of the variable. | |
12962 | ||
3d67e040 | 12963 | @kindex info symbol |
b37052ae | 12964 | @cindex symbol from address |
9c16f35a | 12965 | @cindex closest symbol and offset for an address |
3d67e040 EZ |
12966 | @item info symbol @var{addr} |
12967 | Print the name of a symbol which is stored at the address @var{addr}. | |
12968 | If no symbol is stored exactly at @var{addr}, @value{GDBN} prints the | |
12969 | nearest symbol and an offset from it: | |
12970 | ||
474c8240 | 12971 | @smallexample |
3d67e040 EZ |
12972 | (@value{GDBP}) info symbol 0x54320 |
12973 | _initialize_vx + 396 in section .text | |
474c8240 | 12974 | @end smallexample |
3d67e040 EZ |
12975 | |
12976 | @noindent | |
12977 | This is the opposite of the @code{info address} command. You can use | |
12978 | it to find out the name of a variable or a function given its address. | |
12979 | ||
c14c28ba PP |
12980 | For dynamically linked executables, the name of executable or shared |
12981 | library containing the symbol is also printed: | |
12982 | ||
12983 | @smallexample | |
12984 | (@value{GDBP}) info symbol 0x400225 | |
12985 | _start + 5 in section .text of /tmp/a.out | |
12986 | (@value{GDBP}) info symbol 0x2aaaac2811cf | |
12987 | __read_nocancel + 6 in section .text of /usr/lib64/libc.so.6 | |
12988 | @end smallexample | |
12989 | ||
c906108c | 12990 | @kindex whatis |
62f3a2ba FF |
12991 | @item whatis [@var{arg}] |
12992 | Print the data type of @var{arg}, which can be either an expression or | |
12993 | a data type. With no argument, print the data type of @code{$}, the | |
12994 | last value in the value history. If @var{arg} is an expression, it is | |
12995 | not actually evaluated, and any side-effecting operations (such as | |
12996 | assignments or function calls) inside it do not take place. If | |
12997 | @var{arg} is a type name, it may be the name of a type or typedef, or | |
12998 | for C code it may have the form @samp{class @var{class-name}}, | |
12999 | @samp{struct @var{struct-tag}}, @samp{union @var{union-tag}} or | |
13000 | @samp{enum @var{enum-tag}}. | |
c906108c SS |
13001 | @xref{Expressions, ,Expressions}. |
13002 | ||
c906108c | 13003 | @kindex ptype |
62f3a2ba FF |
13004 | @item ptype [@var{arg}] |
13005 | @code{ptype} accepts the same arguments as @code{whatis}, but prints a | |
13006 | detailed description of the type, instead of just the name of the type. | |
13007 | @xref{Expressions, ,Expressions}. | |
c906108c SS |
13008 | |
13009 | For example, for this variable declaration: | |
13010 | ||
474c8240 | 13011 | @smallexample |
c906108c | 13012 | struct complex @{double real; double imag;@} v; |
474c8240 | 13013 | @end smallexample |
c906108c SS |
13014 | |
13015 | @noindent | |
13016 | the two commands give this output: | |
13017 | ||
474c8240 | 13018 | @smallexample |
c906108c SS |
13019 | @group |
13020 | (@value{GDBP}) whatis v | |
13021 | type = struct complex | |
13022 | (@value{GDBP}) ptype v | |
13023 | type = struct complex @{ | |
13024 | double real; | |
13025 | double imag; | |
13026 | @} | |
13027 | @end group | |
474c8240 | 13028 | @end smallexample |
c906108c SS |
13029 | |
13030 | @noindent | |
13031 | As with @code{whatis}, using @code{ptype} without an argument refers to | |
13032 | the type of @code{$}, the last value in the value history. | |
13033 | ||
ab1adacd EZ |
13034 | @cindex incomplete type |
13035 | Sometimes, programs use opaque data types or incomplete specifications | |
13036 | of complex data structure. If the debug information included in the | |
13037 | program does not allow @value{GDBN} to display a full declaration of | |
13038 | the data type, it will say @samp{<incomplete type>}. For example, | |
13039 | given these declarations: | |
13040 | ||
13041 | @smallexample | |
13042 | struct foo; | |
13043 | struct foo *fooptr; | |
13044 | @end smallexample | |
13045 | ||
13046 | @noindent | |
13047 | but no definition for @code{struct foo} itself, @value{GDBN} will say: | |
13048 | ||
13049 | @smallexample | |
ddb50cd7 | 13050 | (@value{GDBP}) ptype foo |
ab1adacd EZ |
13051 | $1 = <incomplete type> |
13052 | @end smallexample | |
13053 | ||
13054 | @noindent | |
13055 | ``Incomplete type'' is C terminology for data types that are not | |
13056 | completely specified. | |
13057 | ||
c906108c SS |
13058 | @kindex info types |
13059 | @item info types @var{regexp} | |
13060 | @itemx info types | |
09d4efe1 EZ |
13061 | Print a brief description of all types whose names match the regular |
13062 | expression @var{regexp} (or all types in your program, if you supply | |
13063 | no argument). Each complete typename is matched as though it were a | |
13064 | complete line; thus, @samp{i type value} gives information on all | |
13065 | types in your program whose names include the string @code{value}, but | |
13066 | @samp{i type ^value$} gives information only on types whose complete | |
13067 | name is @code{value}. | |
c906108c SS |
13068 | |
13069 | This command differs from @code{ptype} in two ways: first, like | |
13070 | @code{whatis}, it does not print a detailed description; second, it | |
13071 | lists all source files where a type is defined. | |
13072 | ||
b37052ae EZ |
13073 | @kindex info scope |
13074 | @cindex local variables | |
09d4efe1 | 13075 | @item info scope @var{location} |
b37052ae | 13076 | List all the variables local to a particular scope. This command |
09d4efe1 EZ |
13077 | accepts a @var{location} argument---a function name, a source line, or |
13078 | an address preceded by a @samp{*}, and prints all the variables local | |
2a25a5ba EZ |
13079 | to the scope defined by that location. (@xref{Specify Location}, for |
13080 | details about supported forms of @var{location}.) For example: | |
b37052ae EZ |
13081 | |
13082 | @smallexample | |
13083 | (@value{GDBP}) @b{info scope command_line_handler} | |
13084 | Scope for command_line_handler: | |
13085 | Symbol rl is an argument at stack/frame offset 8, length 4. | |
13086 | Symbol linebuffer is in static storage at address 0x150a18, length 4. | |
13087 | Symbol linelength is in static storage at address 0x150a1c, length 4. | |
13088 | Symbol p is a local variable in register $esi, length 4. | |
13089 | Symbol p1 is a local variable in register $ebx, length 4. | |
13090 | Symbol nline is a local variable in register $edx, length 4. | |
13091 | Symbol repeat is a local variable at frame offset -8, length 4. | |
13092 | @end smallexample | |
13093 | ||
f5c37c66 EZ |
13094 | @noindent |
13095 | This command is especially useful for determining what data to collect | |
13096 | during a @dfn{trace experiment}, see @ref{Tracepoint Actions, | |
13097 | collect}. | |
13098 | ||
c906108c SS |
13099 | @kindex info source |
13100 | @item info source | |
919d772c JB |
13101 | Show information about the current source file---that is, the source file for |
13102 | the function containing the current point of execution: | |
13103 | @itemize @bullet | |
13104 | @item | |
13105 | the name of the source file, and the directory containing it, | |
13106 | @item | |
13107 | the directory it was compiled in, | |
13108 | @item | |
13109 | its length, in lines, | |
13110 | @item | |
13111 | which programming language it is written in, | |
13112 | @item | |
13113 | whether the executable includes debugging information for that file, and | |
13114 | if so, what format the information is in (e.g., STABS, Dwarf 2, etc.), and | |
13115 | @item | |
13116 | whether the debugging information includes information about | |
13117 | preprocessor macros. | |
13118 | @end itemize | |
13119 | ||
c906108c SS |
13120 | |
13121 | @kindex info sources | |
13122 | @item info sources | |
13123 | Print the names of all source files in your program for which there is | |
13124 | debugging information, organized into two lists: files whose symbols | |
13125 | have already been read, and files whose symbols will be read when needed. | |
13126 | ||
13127 | @kindex info functions | |
13128 | @item info functions | |
13129 | Print the names and data types of all defined functions. | |
13130 | ||
13131 | @item info functions @var{regexp} | |
13132 | Print the names and data types of all defined functions | |
13133 | whose names contain a match for regular expression @var{regexp}. | |
13134 | Thus, @samp{info fun step} finds all functions whose names | |
13135 | include @code{step}; @samp{info fun ^step} finds those whose names | |
b383017d | 13136 | start with @code{step}. If a function name contains characters |
c1468174 | 13137 | that conflict with the regular expression language (e.g.@: |
1c5dfdad | 13138 | @samp{operator*()}), they may be quoted with a backslash. |
c906108c SS |
13139 | |
13140 | @kindex info variables | |
13141 | @item info variables | |
0fe7935b | 13142 | Print the names and data types of all variables that are defined |
6ca652b0 | 13143 | outside of functions (i.e.@: excluding local variables). |
c906108c SS |
13144 | |
13145 | @item info variables @var{regexp} | |
13146 | Print the names and data types of all variables (except for local | |
13147 | variables) whose names contain a match for regular expression | |
13148 | @var{regexp}. | |
13149 | ||
b37303ee | 13150 | @kindex info classes |
721c2651 | 13151 | @cindex Objective-C, classes and selectors |
b37303ee AF |
13152 | @item info classes |
13153 | @itemx info classes @var{regexp} | |
13154 | Display all Objective-C classes in your program, or | |
13155 | (with the @var{regexp} argument) all those matching a particular regular | |
13156 | expression. | |
13157 | ||
13158 | @kindex info selectors | |
13159 | @item info selectors | |
13160 | @itemx info selectors @var{regexp} | |
13161 | Display all Objective-C selectors in your program, or | |
13162 | (with the @var{regexp} argument) all those matching a particular regular | |
13163 | expression. | |
13164 | ||
c906108c SS |
13165 | @ignore |
13166 | This was never implemented. | |
13167 | @kindex info methods | |
13168 | @item info methods | |
13169 | @itemx info methods @var{regexp} | |
13170 | The @code{info methods} command permits the user to examine all defined | |
b37052ae EZ |
13171 | methods within C@t{++} program, or (with the @var{regexp} argument) a |
13172 | specific set of methods found in the various C@t{++} classes. Many | |
13173 | C@t{++} classes provide a large number of methods. Thus, the output | |
c906108c SS |
13174 | from the @code{ptype} command can be overwhelming and hard to use. The |
13175 | @code{info-methods} command filters the methods, printing only those | |
13176 | which match the regular-expression @var{regexp}. | |
13177 | @end ignore | |
13178 | ||
c906108c SS |
13179 | @cindex reloading symbols |
13180 | Some systems allow individual object files that make up your program to | |
7a292a7a SS |
13181 | be replaced without stopping and restarting your program. For example, |
13182 | in VxWorks you can simply recompile a defective object file and keep on | |
13183 | running. If you are running on one of these systems, you can allow | |
13184 | @value{GDBN} to reload the symbols for automatically relinked modules: | |
c906108c SS |
13185 | |
13186 | @table @code | |
13187 | @kindex set symbol-reloading | |
13188 | @item set symbol-reloading on | |
13189 | Replace symbol definitions for the corresponding source file when an | |
13190 | object file with a particular name is seen again. | |
13191 | ||
13192 | @item set symbol-reloading off | |
6d2ebf8b SS |
13193 | Do not replace symbol definitions when encountering object files of the |
13194 | same name more than once. This is the default state; if you are not | |
13195 | running on a system that permits automatic relinking of modules, you | |
13196 | should leave @code{symbol-reloading} off, since otherwise @value{GDBN} | |
13197 | may discard symbols when linking large programs, that may contain | |
13198 | several modules (from different directories or libraries) with the same | |
13199 | name. | |
c906108c SS |
13200 | |
13201 | @kindex show symbol-reloading | |
13202 | @item show symbol-reloading | |
13203 | Show the current @code{on} or @code{off} setting. | |
13204 | @end table | |
c906108c | 13205 | |
9c16f35a | 13206 | @cindex opaque data types |
c906108c SS |
13207 | @kindex set opaque-type-resolution |
13208 | @item set opaque-type-resolution on | |
13209 | Tell @value{GDBN} to resolve opaque types. An opaque type is a type | |
13210 | declared as a pointer to a @code{struct}, @code{class}, or | |
13211 | @code{union}---for example, @code{struct MyType *}---that is used in one | |
13212 | source file although the full declaration of @code{struct MyType} is in | |
13213 | another source file. The default is on. | |
13214 | ||
13215 | A change in the setting of this subcommand will not take effect until | |
13216 | the next time symbols for a file are loaded. | |
13217 | ||
13218 | @item set opaque-type-resolution off | |
13219 | Tell @value{GDBN} not to resolve opaque types. In this case, the type | |
13220 | is printed as follows: | |
13221 | @smallexample | |
13222 | @{<no data fields>@} | |
13223 | @end smallexample | |
13224 | ||
13225 | @kindex show opaque-type-resolution | |
13226 | @item show opaque-type-resolution | |
13227 | Show whether opaque types are resolved or not. | |
c906108c SS |
13228 | |
13229 | @kindex maint print symbols | |
13230 | @cindex symbol dump | |
13231 | @kindex maint print psymbols | |
13232 | @cindex partial symbol dump | |
13233 | @item maint print symbols @var{filename} | |
13234 | @itemx maint print psymbols @var{filename} | |
13235 | @itemx maint print msymbols @var{filename} | |
13236 | Write a dump of debugging symbol data into the file @var{filename}. | |
13237 | These commands are used to debug the @value{GDBN} symbol-reading code. Only | |
13238 | symbols with debugging data are included. If you use @samp{maint print | |
13239 | symbols}, @value{GDBN} includes all the symbols for which it has already | |
13240 | collected full details: that is, @var{filename} reflects symbols for | |
13241 | only those files whose symbols @value{GDBN} has read. You can use the | |
13242 | command @code{info sources} to find out which files these are. If you | |
13243 | use @samp{maint print psymbols} instead, the dump shows information about | |
13244 | symbols that @value{GDBN} only knows partially---that is, symbols defined in | |
13245 | files that @value{GDBN} has skimmed, but not yet read completely. Finally, | |
13246 | @samp{maint print msymbols} dumps just the minimal symbol information | |
13247 | required for each object file from which @value{GDBN} has read some symbols. | |
79a6e687 | 13248 | @xref{Files, ,Commands to Specify Files}, for a discussion of how |
c906108c | 13249 | @value{GDBN} reads symbols (in the description of @code{symbol-file}). |
44ea7b70 | 13250 | |
5e7b2f39 JB |
13251 | @kindex maint info symtabs |
13252 | @kindex maint info psymtabs | |
44ea7b70 JB |
13253 | @cindex listing @value{GDBN}'s internal symbol tables |
13254 | @cindex symbol tables, listing @value{GDBN}'s internal | |
13255 | @cindex full symbol tables, listing @value{GDBN}'s internal | |
13256 | @cindex partial symbol tables, listing @value{GDBN}'s internal | |
5e7b2f39 JB |
13257 | @item maint info symtabs @r{[} @var{regexp} @r{]} |
13258 | @itemx maint info psymtabs @r{[} @var{regexp} @r{]} | |
44ea7b70 JB |
13259 | |
13260 | List the @code{struct symtab} or @code{struct partial_symtab} | |
13261 | structures whose names match @var{regexp}. If @var{regexp} is not | |
13262 | given, list them all. The output includes expressions which you can | |
13263 | copy into a @value{GDBN} debugging this one to examine a particular | |
13264 | structure in more detail. For example: | |
13265 | ||
13266 | @smallexample | |
5e7b2f39 | 13267 | (@value{GDBP}) maint info psymtabs dwarf2read |
44ea7b70 JB |
13268 | @{ objfile /home/gnu/build/gdb/gdb |
13269 | ((struct objfile *) 0x82e69d0) | |
b383017d | 13270 | @{ psymtab /home/gnu/src/gdb/dwarf2read.c |
44ea7b70 JB |
13271 | ((struct partial_symtab *) 0x8474b10) |
13272 | readin no | |
13273 | fullname (null) | |
13274 | text addresses 0x814d3c8 -- 0x8158074 | |
13275 | globals (* (struct partial_symbol **) 0x8507a08 @@ 9) | |
13276 | statics (* (struct partial_symbol **) 0x40e95b78 @@ 2882) | |
13277 | dependencies (none) | |
13278 | @} | |
13279 | @} | |
5e7b2f39 | 13280 | (@value{GDBP}) maint info symtabs |
44ea7b70 JB |
13281 | (@value{GDBP}) |
13282 | @end smallexample | |
13283 | @noindent | |
13284 | We see that there is one partial symbol table whose filename contains | |
13285 | the string @samp{dwarf2read}, belonging to the @samp{gdb} executable; | |
13286 | and we see that @value{GDBN} has not read in any symtabs yet at all. | |
13287 | If we set a breakpoint on a function, that will cause @value{GDBN} to | |
13288 | read the symtab for the compilation unit containing that function: | |
13289 | ||
13290 | @smallexample | |
13291 | (@value{GDBP}) break dwarf2_psymtab_to_symtab | |
13292 | Breakpoint 1 at 0x814e5da: file /home/gnu/src/gdb/dwarf2read.c, | |
13293 | line 1574. | |
5e7b2f39 | 13294 | (@value{GDBP}) maint info symtabs |
b383017d | 13295 | @{ objfile /home/gnu/build/gdb/gdb |
44ea7b70 | 13296 | ((struct objfile *) 0x82e69d0) |
b383017d | 13297 | @{ symtab /home/gnu/src/gdb/dwarf2read.c |
44ea7b70 JB |
13298 | ((struct symtab *) 0x86c1f38) |
13299 | dirname (null) | |
13300 | fullname (null) | |
13301 | blockvector ((struct blockvector *) 0x86c1bd0) (primary) | |
1b39d5c0 | 13302 | linetable ((struct linetable *) 0x8370fa0) |
44ea7b70 JB |
13303 | debugformat DWARF 2 |
13304 | @} | |
13305 | @} | |
b383017d | 13306 | (@value{GDBP}) |
44ea7b70 | 13307 | @end smallexample |
c906108c SS |
13308 | @end table |
13309 | ||
44ea7b70 | 13310 | |
6d2ebf8b | 13311 | @node Altering |
c906108c SS |
13312 | @chapter Altering Execution |
13313 | ||
13314 | Once you think you have found an error in your program, you might want to | |
13315 | find out for certain whether correcting the apparent error would lead to | |
13316 | correct results in the rest of the run. You can find the answer by | |
13317 | experiment, using the @value{GDBN} features for altering execution of the | |
13318 | program. | |
13319 | ||
13320 | For example, you can store new values into variables or memory | |
7a292a7a SS |
13321 | locations, give your program a signal, restart it at a different |
13322 | address, or even return prematurely from a function. | |
c906108c SS |
13323 | |
13324 | @menu | |
13325 | * Assignment:: Assignment to variables | |
13326 | * Jumping:: Continuing at a different address | |
c906108c | 13327 | * Signaling:: Giving your program a signal |
c906108c SS |
13328 | * Returning:: Returning from a function |
13329 | * Calling:: Calling your program's functions | |
13330 | * Patching:: Patching your program | |
13331 | @end menu | |
13332 | ||
6d2ebf8b | 13333 | @node Assignment |
79a6e687 | 13334 | @section Assignment to Variables |
c906108c SS |
13335 | |
13336 | @cindex assignment | |
13337 | @cindex setting variables | |
13338 | To alter the value of a variable, evaluate an assignment expression. | |
13339 | @xref{Expressions, ,Expressions}. For example, | |
13340 | ||
474c8240 | 13341 | @smallexample |
c906108c | 13342 | print x=4 |
474c8240 | 13343 | @end smallexample |
c906108c SS |
13344 | |
13345 | @noindent | |
13346 | stores the value 4 into the variable @code{x}, and then prints the | |
5d161b24 | 13347 | value of the assignment expression (which is 4). |
c906108c SS |
13348 | @xref{Languages, ,Using @value{GDBN} with Different Languages}, for more |
13349 | information on operators in supported languages. | |
c906108c SS |
13350 | |
13351 | @kindex set variable | |
13352 | @cindex variables, setting | |
13353 | If you are not interested in seeing the value of the assignment, use the | |
13354 | @code{set} command instead of the @code{print} command. @code{set} is | |
13355 | really the same as @code{print} except that the expression's value is | |
13356 | not printed and is not put in the value history (@pxref{Value History, | |
79a6e687 | 13357 | ,Value History}). The expression is evaluated only for its effects. |
c906108c | 13358 | |
c906108c SS |
13359 | If the beginning of the argument string of the @code{set} command |
13360 | appears identical to a @code{set} subcommand, use the @code{set | |
13361 | variable} command instead of just @code{set}. This command is identical | |
13362 | to @code{set} except for its lack of subcommands. For example, if your | |
13363 | program has a variable @code{width}, you get an error if you try to set | |
13364 | a new value with just @samp{set width=13}, because @value{GDBN} has the | |
13365 | command @code{set width}: | |
13366 | ||
474c8240 | 13367 | @smallexample |
c906108c SS |
13368 | (@value{GDBP}) whatis width |
13369 | type = double | |
13370 | (@value{GDBP}) p width | |
13371 | $4 = 13 | |
13372 | (@value{GDBP}) set width=47 | |
13373 | Invalid syntax in expression. | |
474c8240 | 13374 | @end smallexample |
c906108c SS |
13375 | |
13376 | @noindent | |
13377 | The invalid expression, of course, is @samp{=47}. In | |
13378 | order to actually set the program's variable @code{width}, use | |
13379 | ||
474c8240 | 13380 | @smallexample |
c906108c | 13381 | (@value{GDBP}) set var width=47 |
474c8240 | 13382 | @end smallexample |
53a5351d | 13383 | |
c906108c SS |
13384 | Because the @code{set} command has many subcommands that can conflict |
13385 | with the names of program variables, it is a good idea to use the | |
13386 | @code{set variable} command instead of just @code{set}. For example, if | |
13387 | your program has a variable @code{g}, you run into problems if you try | |
13388 | to set a new value with just @samp{set g=4}, because @value{GDBN} has | |
13389 | the command @code{set gnutarget}, abbreviated @code{set g}: | |
13390 | ||
474c8240 | 13391 | @smallexample |
c906108c SS |
13392 | @group |
13393 | (@value{GDBP}) whatis g | |
13394 | type = double | |
13395 | (@value{GDBP}) p g | |
13396 | $1 = 1 | |
13397 | (@value{GDBP}) set g=4 | |
2df3850c | 13398 | (@value{GDBP}) p g |
c906108c SS |
13399 | $2 = 1 |
13400 | (@value{GDBP}) r | |
13401 | The program being debugged has been started already. | |
13402 | Start it from the beginning? (y or n) y | |
13403 | Starting program: /home/smith/cc_progs/a.out | |
6d2ebf8b SS |
13404 | "/home/smith/cc_progs/a.out": can't open to read symbols: |
13405 | Invalid bfd target. | |
c906108c SS |
13406 | (@value{GDBP}) show g |
13407 | The current BFD target is "=4". | |
13408 | @end group | |
474c8240 | 13409 | @end smallexample |
c906108c SS |
13410 | |
13411 | @noindent | |
13412 | The program variable @code{g} did not change, and you silently set the | |
13413 | @code{gnutarget} to an invalid value. In order to set the variable | |
13414 | @code{g}, use | |
13415 | ||
474c8240 | 13416 | @smallexample |
c906108c | 13417 | (@value{GDBP}) set var g=4 |
474c8240 | 13418 | @end smallexample |
c906108c SS |
13419 | |
13420 | @value{GDBN} allows more implicit conversions in assignments than C; you can | |
13421 | freely store an integer value into a pointer variable or vice versa, | |
13422 | and you can convert any structure to any other structure that is the | |
13423 | same length or shorter. | |
13424 | @comment FIXME: how do structs align/pad in these conversions? | |
13425 | @comment /doc@cygnus.com 18dec1990 | |
13426 | ||
13427 | To store values into arbitrary places in memory, use the @samp{@{@dots{}@}} | |
13428 | construct to generate a value of specified type at a specified address | |
13429 | (@pxref{Expressions, ,Expressions}). For example, @code{@{int@}0x83040} refers | |
13430 | to memory location @code{0x83040} as an integer (which implies a certain size | |
13431 | and representation in memory), and | |
13432 | ||
474c8240 | 13433 | @smallexample |
c906108c | 13434 | set @{int@}0x83040 = 4 |
474c8240 | 13435 | @end smallexample |
c906108c SS |
13436 | |
13437 | @noindent | |
13438 | stores the value 4 into that memory location. | |
13439 | ||
6d2ebf8b | 13440 | @node Jumping |
79a6e687 | 13441 | @section Continuing at a Different Address |
c906108c SS |
13442 | |
13443 | Ordinarily, when you continue your program, you do so at the place where | |
13444 | it stopped, with the @code{continue} command. You can instead continue at | |
13445 | an address of your own choosing, with the following commands: | |
13446 | ||
13447 | @table @code | |
13448 | @kindex jump | |
13449 | @item jump @var{linespec} | |
2a25a5ba EZ |
13450 | @itemx jump @var{location} |
13451 | Resume execution at line @var{linespec} or at address given by | |
13452 | @var{location}. Execution stops again immediately if there is a | |
13453 | breakpoint there. @xref{Specify Location}, for a description of the | |
13454 | different forms of @var{linespec} and @var{location}. It is common | |
13455 | practice to use the @code{tbreak} command in conjunction with | |
13456 | @code{jump}. @xref{Set Breaks, ,Setting Breakpoints}. | |
c906108c SS |
13457 | |
13458 | The @code{jump} command does not change the current stack frame, or | |
13459 | the stack pointer, or the contents of any memory location or any | |
13460 | register other than the program counter. If line @var{linespec} is in | |
13461 | a different function from the one currently executing, the results may | |
13462 | be bizarre if the two functions expect different patterns of arguments or | |
13463 | of local variables. For this reason, the @code{jump} command requests | |
13464 | confirmation if the specified line is not in the function currently | |
13465 | executing. However, even bizarre results are predictable if you are | |
13466 | well acquainted with the machine-language code of your program. | |
c906108c SS |
13467 | @end table |
13468 | ||
c906108c | 13469 | @c Doesn't work on HP-UX; have to set $pcoqh and $pcoqt. |
53a5351d JM |
13470 | On many systems, you can get much the same effect as the @code{jump} |
13471 | command by storing a new value into the register @code{$pc}. The | |
13472 | difference is that this does not start your program running; it only | |
13473 | changes the address of where it @emph{will} run when you continue. For | |
13474 | example, | |
c906108c | 13475 | |
474c8240 | 13476 | @smallexample |
c906108c | 13477 | set $pc = 0x485 |
474c8240 | 13478 | @end smallexample |
c906108c SS |
13479 | |
13480 | @noindent | |
13481 | makes the next @code{continue} command or stepping command execute at | |
13482 | address @code{0x485}, rather than at the address where your program stopped. | |
79a6e687 | 13483 | @xref{Continuing and Stepping, ,Continuing and Stepping}. |
c906108c SS |
13484 | |
13485 | The most common occasion to use the @code{jump} command is to back | |
13486 | up---perhaps with more breakpoints set---over a portion of a program | |
13487 | that has already executed, in order to examine its execution in more | |
13488 | detail. | |
13489 | ||
c906108c | 13490 | @c @group |
6d2ebf8b | 13491 | @node Signaling |
79a6e687 | 13492 | @section Giving your Program a Signal |
9c16f35a | 13493 | @cindex deliver a signal to a program |
c906108c SS |
13494 | |
13495 | @table @code | |
13496 | @kindex signal | |
13497 | @item signal @var{signal} | |
13498 | Resume execution where your program stopped, but immediately give it the | |
13499 | signal @var{signal}. @var{signal} can be the name or the number of a | |
13500 | signal. For example, on many systems @code{signal 2} and @code{signal | |
13501 | SIGINT} are both ways of sending an interrupt signal. | |
13502 | ||
13503 | Alternatively, if @var{signal} is zero, continue execution without | |
13504 | giving a signal. This is useful when your program stopped on account of | |
13505 | a signal and would ordinary see the signal when resumed with the | |
13506 | @code{continue} command; @samp{signal 0} causes it to resume without a | |
13507 | signal. | |
13508 | ||
13509 | @code{signal} does not repeat when you press @key{RET} a second time | |
13510 | after executing the command. | |
13511 | @end table | |
13512 | @c @end group | |
13513 | ||
13514 | Invoking the @code{signal} command is not the same as invoking the | |
13515 | @code{kill} utility from the shell. Sending a signal with @code{kill} | |
13516 | causes @value{GDBN} to decide what to do with the signal depending on | |
13517 | the signal handling tables (@pxref{Signals}). The @code{signal} command | |
13518 | passes the signal directly to your program. | |
13519 | ||
c906108c | 13520 | |
6d2ebf8b | 13521 | @node Returning |
79a6e687 | 13522 | @section Returning from a Function |
c906108c SS |
13523 | |
13524 | @table @code | |
13525 | @cindex returning from a function | |
13526 | @kindex return | |
13527 | @item return | |
13528 | @itemx return @var{expression} | |
13529 | You can cancel execution of a function call with the @code{return} | |
13530 | command. If you give an | |
13531 | @var{expression} argument, its value is used as the function's return | |
13532 | value. | |
13533 | @end table | |
13534 | ||
13535 | When you use @code{return}, @value{GDBN} discards the selected stack frame | |
13536 | (and all frames within it). You can think of this as making the | |
13537 | discarded frame return prematurely. If you wish to specify a value to | |
13538 | be returned, give that value as the argument to @code{return}. | |
13539 | ||
13540 | This pops the selected stack frame (@pxref{Selection, ,Selecting a | |
79a6e687 | 13541 | Frame}), and any other frames inside of it, leaving its caller as the |
c906108c SS |
13542 | innermost remaining frame. That frame becomes selected. The |
13543 | specified value is stored in the registers used for returning values | |
13544 | of functions. | |
13545 | ||
13546 | The @code{return} command does not resume execution; it leaves the | |
13547 | program stopped in the state that would exist if the function had just | |
13548 | returned. In contrast, the @code{finish} command (@pxref{Continuing | |
79a6e687 | 13549 | and Stepping, ,Continuing and Stepping}) resumes execution until the |
c906108c SS |
13550 | selected stack frame returns naturally. |
13551 | ||
61ff14c6 JK |
13552 | @value{GDBN} needs to know how the @var{expression} argument should be set for |
13553 | the inferior. The concrete registers assignment depends on the OS ABI and the | |
13554 | type being returned by the selected stack frame. For example it is common for | |
13555 | OS ABI to return floating point values in FPU registers while integer values in | |
13556 | CPU registers. Still some ABIs return even floating point values in CPU | |
13557 | registers. Larger integer widths (such as @code{long long int}) also have | |
13558 | specific placement rules. @value{GDBN} already knows the OS ABI from its | |
13559 | current target so it needs to find out also the type being returned to make the | |
13560 | assignment into the right register(s). | |
13561 | ||
13562 | Normally, the selected stack frame has debug info. @value{GDBN} will always | |
13563 | use the debug info instead of the implicit type of @var{expression} when the | |
13564 | debug info is available. For example, if you type @kbd{return -1}, and the | |
13565 | function in the current stack frame is declared to return a @code{long long | |
13566 | int}, @value{GDBN} transparently converts the implicit @code{int} value of -1 | |
13567 | into a @code{long long int}: | |
13568 | ||
13569 | @smallexample | |
13570 | Breakpoint 1, func () at gdb.base/return-nodebug.c:29 | |
13571 | 29 return 31; | |
13572 | (@value{GDBP}) return -1 | |
13573 | Make func return now? (y or n) y | |
13574 | #0 0x004004f6 in main () at gdb.base/return-nodebug.c:43 | |
13575 | 43 printf ("result=%lld\n", func ()); | |
13576 | (@value{GDBP}) | |
13577 | @end smallexample | |
13578 | ||
13579 | However, if the selected stack frame does not have a debug info, e.g., if the | |
13580 | function was compiled without debug info, @value{GDBN} has to find out the type | |
13581 | to return from user. Specifying a different type by mistake may set the value | |
13582 | in different inferior registers than the caller code expects. For example, | |
13583 | typing @kbd{return -1} with its implicit type @code{int} would set only a part | |
13584 | of a @code{long long int} result for a debug info less function (on 32-bit | |
13585 | architectures). Therefore the user is required to specify the return type by | |
13586 | an appropriate cast explicitly: | |
13587 | ||
13588 | @smallexample | |
13589 | Breakpoint 2, 0x0040050b in func () | |
13590 | (@value{GDBP}) return -1 | |
13591 | Return value type not available for selected stack frame. | |
13592 | Please use an explicit cast of the value to return. | |
13593 | (@value{GDBP}) return (long long int) -1 | |
13594 | Make selected stack frame return now? (y or n) y | |
13595 | #0 0x00400526 in main () | |
13596 | (@value{GDBP}) | |
13597 | @end smallexample | |
13598 | ||
6d2ebf8b | 13599 | @node Calling |
79a6e687 | 13600 | @section Calling Program Functions |
c906108c | 13601 | |
f8568604 | 13602 | @table @code |
c906108c | 13603 | @cindex calling functions |
f8568604 EZ |
13604 | @cindex inferior functions, calling |
13605 | @item print @var{expr} | |
d3e8051b | 13606 | Evaluate the expression @var{expr} and display the resulting value. |
f8568604 EZ |
13607 | @var{expr} may include calls to functions in the program being |
13608 | debugged. | |
13609 | ||
c906108c | 13610 | @kindex call |
c906108c SS |
13611 | @item call @var{expr} |
13612 | Evaluate the expression @var{expr} without displaying @code{void} | |
13613 | returned values. | |
c906108c SS |
13614 | |
13615 | You can use this variant of the @code{print} command if you want to | |
f8568604 EZ |
13616 | execute a function from your program that does not return anything |
13617 | (a.k.a.@: @dfn{a void function}), but without cluttering the output | |
13618 | with @code{void} returned values that @value{GDBN} will otherwise | |
13619 | print. If the result is not void, it is printed and saved in the | |
13620 | value history. | |
13621 | @end table | |
13622 | ||
9c16f35a EZ |
13623 | It is possible for the function you call via the @code{print} or |
13624 | @code{call} command to generate a signal (e.g., if there's a bug in | |
13625 | the function, or if you passed it incorrect arguments). What happens | |
13626 | in that case is controlled by the @code{set unwindonsignal} command. | |
13627 | ||
7cd1089b PM |
13628 | Similarly, with a C@t{++} program it is possible for the function you |
13629 | call via the @code{print} or @code{call} command to generate an | |
13630 | exception that is not handled due to the constraints of the dummy | |
13631 | frame. In this case, any exception that is raised in the frame, but has | |
13632 | an out-of-frame exception handler will not be found. GDB builds a | |
13633 | dummy-frame for the inferior function call, and the unwinder cannot | |
13634 | seek for exception handlers outside of this dummy-frame. What happens | |
13635 | in that case is controlled by the | |
13636 | @code{set unwind-on-terminating-exception} command. | |
13637 | ||
9c16f35a EZ |
13638 | @table @code |
13639 | @item set unwindonsignal | |
13640 | @kindex set unwindonsignal | |
13641 | @cindex unwind stack in called functions | |
13642 | @cindex call dummy stack unwinding | |
13643 | Set unwinding of the stack if a signal is received while in a function | |
13644 | that @value{GDBN} called in the program being debugged. If set to on, | |
13645 | @value{GDBN} unwinds the stack it created for the call and restores | |
13646 | the context to what it was before the call. If set to off (the | |
13647 | default), @value{GDBN} stops in the frame where the signal was | |
13648 | received. | |
13649 | ||
13650 | @item show unwindonsignal | |
13651 | @kindex show unwindonsignal | |
13652 | Show the current setting of stack unwinding in the functions called by | |
13653 | @value{GDBN}. | |
7cd1089b PM |
13654 | |
13655 | @item set unwind-on-terminating-exception | |
13656 | @kindex set unwind-on-terminating-exception | |
13657 | @cindex unwind stack in called functions with unhandled exceptions | |
13658 | @cindex call dummy stack unwinding on unhandled exception. | |
13659 | Set unwinding of the stack if a C@t{++} exception is raised, but left | |
13660 | unhandled while in a function that @value{GDBN} called in the program being | |
13661 | debugged. If set to on (the default), @value{GDBN} unwinds the stack | |
13662 | it created for the call and restores the context to what it was before | |
13663 | the call. If set to off, @value{GDBN} the exception is delivered to | |
13664 | the default C@t{++} exception handler and the inferior terminated. | |
13665 | ||
13666 | @item show unwind-on-terminating-exception | |
13667 | @kindex show unwind-on-terminating-exception | |
13668 | Show the current setting of stack unwinding in the functions called by | |
13669 | @value{GDBN}. | |
13670 | ||
9c16f35a EZ |
13671 | @end table |
13672 | ||
f8568604 EZ |
13673 | @cindex weak alias functions |
13674 | Sometimes, a function you wish to call is actually a @dfn{weak alias} | |
13675 | for another function. In such case, @value{GDBN} might not pick up | |
13676 | the type information, including the types of the function arguments, | |
13677 | which causes @value{GDBN} to call the inferior function incorrectly. | |
13678 | As a result, the called function will function erroneously and may | |
13679 | even crash. A solution to that is to use the name of the aliased | |
13680 | function instead. | |
c906108c | 13681 | |
6d2ebf8b | 13682 | @node Patching |
79a6e687 | 13683 | @section Patching Programs |
7a292a7a | 13684 | |
c906108c SS |
13685 | @cindex patching binaries |
13686 | @cindex writing into executables | |
c906108c | 13687 | @cindex writing into corefiles |
c906108c | 13688 | |
7a292a7a SS |
13689 | By default, @value{GDBN} opens the file containing your program's |
13690 | executable code (or the corefile) read-only. This prevents accidental | |
13691 | alterations to machine code; but it also prevents you from intentionally | |
13692 | patching your program's binary. | |
c906108c SS |
13693 | |
13694 | If you'd like to be able to patch the binary, you can specify that | |
13695 | explicitly with the @code{set write} command. For example, you might | |
13696 | want to turn on internal debugging flags, or even to make emergency | |
13697 | repairs. | |
13698 | ||
13699 | @table @code | |
13700 | @kindex set write | |
13701 | @item set write on | |
13702 | @itemx set write off | |
7a292a7a | 13703 | If you specify @samp{set write on}, @value{GDBN} opens executable and |
20924a55 | 13704 | core files for both reading and writing; if you specify @kbd{set write |
c906108c SS |
13705 | off} (the default), @value{GDBN} opens them read-only. |
13706 | ||
13707 | If you have already loaded a file, you must load it again (using the | |
7a292a7a SS |
13708 | @code{exec-file} or @code{core-file} command) after changing @code{set |
13709 | write}, for your new setting to take effect. | |
c906108c SS |
13710 | |
13711 | @item show write | |
13712 | @kindex show write | |
7a292a7a SS |
13713 | Display whether executable files and core files are opened for writing |
13714 | as well as reading. | |
c906108c SS |
13715 | @end table |
13716 | ||
6d2ebf8b | 13717 | @node GDB Files |
c906108c SS |
13718 | @chapter @value{GDBN} Files |
13719 | ||
7a292a7a SS |
13720 | @value{GDBN} needs to know the file name of the program to be debugged, |
13721 | both in order to read its symbol table and in order to start your | |
13722 | program. To debug a core dump of a previous run, you must also tell | |
13723 | @value{GDBN} the name of the core dump file. | |
c906108c SS |
13724 | |
13725 | @menu | |
13726 | * Files:: Commands to specify files | |
5b5d99cf | 13727 | * Separate Debug Files:: Debugging information in separate files |
c906108c | 13728 | * Symbol Errors:: Errors reading symbol files |
b14b1491 | 13729 | * Data Files:: GDB data files |
c906108c SS |
13730 | @end menu |
13731 | ||
6d2ebf8b | 13732 | @node Files |
79a6e687 | 13733 | @section Commands to Specify Files |
c906108c | 13734 | |
7a292a7a | 13735 | @cindex symbol table |
c906108c | 13736 | @cindex core dump file |
7a292a7a SS |
13737 | |
13738 | You may want to specify executable and core dump file names. The usual | |
13739 | way to do this is at start-up time, using the arguments to | |
13740 | @value{GDBN}'s start-up commands (@pxref{Invocation, , Getting In and | |
13741 | Out of @value{GDBN}}). | |
c906108c SS |
13742 | |
13743 | Occasionally it is necessary to change to a different file during a | |
397ca115 EZ |
13744 | @value{GDBN} session. Or you may run @value{GDBN} and forget to |
13745 | specify a file you want to use. Or you are debugging a remote target | |
79a6e687 BW |
13746 | via @code{gdbserver} (@pxref{Server, file, Using the @code{gdbserver} |
13747 | Program}). In these situations the @value{GDBN} commands to specify | |
0869d01b | 13748 | new files are useful. |
c906108c SS |
13749 | |
13750 | @table @code | |
13751 | @cindex executable file | |
13752 | @kindex file | |
13753 | @item file @var{filename} | |
13754 | Use @var{filename} as the program to be debugged. It is read for its | |
13755 | symbols and for the contents of pure memory. It is also the program | |
13756 | executed when you use the @code{run} command. If you do not specify a | |
5d161b24 DB |
13757 | directory and the file is not found in the @value{GDBN} working directory, |
13758 | @value{GDBN} uses the environment variable @code{PATH} as a list of | |
13759 | directories to search, just as the shell does when looking for a program | |
13760 | to run. You can change the value of this variable, for both @value{GDBN} | |
c906108c SS |
13761 | and your program, using the @code{path} command. |
13762 | ||
fc8be69e EZ |
13763 | @cindex unlinked object files |
13764 | @cindex patching object files | |
13765 | You can load unlinked object @file{.o} files into @value{GDBN} using | |
13766 | the @code{file} command. You will not be able to ``run'' an object | |
13767 | file, but you can disassemble functions and inspect variables. Also, | |
13768 | if the underlying BFD functionality supports it, you could use | |
13769 | @kbd{gdb -write} to patch object files using this technique. Note | |
13770 | that @value{GDBN} can neither interpret nor modify relocations in this | |
13771 | case, so branches and some initialized variables will appear to go to | |
13772 | the wrong place. But this feature is still handy from time to time. | |
13773 | ||
c906108c SS |
13774 | @item file |
13775 | @code{file} with no argument makes @value{GDBN} discard any information it | |
13776 | has on both executable file and the symbol table. | |
13777 | ||
13778 | @kindex exec-file | |
13779 | @item exec-file @r{[} @var{filename} @r{]} | |
13780 | Specify that the program to be run (but not the symbol table) is found | |
13781 | in @var{filename}. @value{GDBN} searches the environment variable @code{PATH} | |
13782 | if necessary to locate your program. Omitting @var{filename} means to | |
13783 | discard information on the executable file. | |
13784 | ||
13785 | @kindex symbol-file | |
13786 | @item symbol-file @r{[} @var{filename} @r{]} | |
13787 | Read symbol table information from file @var{filename}. @code{PATH} is | |
13788 | searched when necessary. Use the @code{file} command to get both symbol | |
13789 | table and program to run from the same file. | |
13790 | ||
13791 | @code{symbol-file} with no argument clears out @value{GDBN} information on your | |
13792 | program's symbol table. | |
13793 | ||
ae5a43e0 DJ |
13794 | The @code{symbol-file} command causes @value{GDBN} to forget the contents of |
13795 | some breakpoints and auto-display expressions. This is because they may | |
13796 | contain pointers to the internal data recording symbols and data types, | |
13797 | which are part of the old symbol table data being discarded inside | |
13798 | @value{GDBN}. | |
c906108c SS |
13799 | |
13800 | @code{symbol-file} does not repeat if you press @key{RET} again after | |
13801 | executing it once. | |
13802 | ||
13803 | When @value{GDBN} is configured for a particular environment, it | |
13804 | understands debugging information in whatever format is the standard | |
13805 | generated for that environment; you may use either a @sc{gnu} compiler, or | |
13806 | other compilers that adhere to the local conventions. | |
c906108c | 13807 | Best results are usually obtained from @sc{gnu} compilers; for example, |
e22ea452 | 13808 | using @code{@value{NGCC}} you can generate debugging information for |
c906108c | 13809 | optimized code. |
c906108c SS |
13810 | |
13811 | For most kinds of object files, with the exception of old SVR3 systems | |
13812 | using COFF, the @code{symbol-file} command does not normally read the | |
13813 | symbol table in full right away. Instead, it scans the symbol table | |
13814 | quickly to find which source files and which symbols are present. The | |
13815 | details are read later, one source file at a time, as they are needed. | |
13816 | ||
13817 | The purpose of this two-stage reading strategy is to make @value{GDBN} | |
13818 | start up faster. For the most part, it is invisible except for | |
13819 | occasional pauses while the symbol table details for a particular source | |
13820 | file are being read. (The @code{set verbose} command can turn these | |
13821 | pauses into messages if desired. @xref{Messages/Warnings, ,Optional | |
79a6e687 | 13822 | Warnings and Messages}.) |
c906108c | 13823 | |
c906108c SS |
13824 | We have not implemented the two-stage strategy for COFF yet. When the |
13825 | symbol table is stored in COFF format, @code{symbol-file} reads the | |
13826 | symbol table data in full right away. Note that ``stabs-in-COFF'' | |
13827 | still does the two-stage strategy, since the debug info is actually | |
13828 | in stabs format. | |
13829 | ||
13830 | @kindex readnow | |
13831 | @cindex reading symbols immediately | |
13832 | @cindex symbols, reading immediately | |
6ac33a4e TT |
13833 | @item symbol-file @r{[} -readnow @r{]} @var{filename} |
13834 | @itemx file @r{[} -readnow @r{]} @var{filename} | |
c906108c SS |
13835 | You can override the @value{GDBN} two-stage strategy for reading symbol |
13836 | tables by using the @samp{-readnow} option with any of the commands that | |
13837 | load symbol table information, if you want to be sure @value{GDBN} has the | |
5d161b24 | 13838 | entire symbol table available. |
c906108c | 13839 | |
c906108c SS |
13840 | @c FIXME: for now no mention of directories, since this seems to be in |
13841 | @c flux. 13mar1992 status is that in theory GDB would look either in | |
13842 | @c current dir or in same dir as myprog; but issues like competing | |
13843 | @c GDB's, or clutter in system dirs, mean that in practice right now | |
13844 | @c only current dir is used. FFish says maybe a special GDB hierarchy | |
13845 | @c (eg rooted in val of env var GDBSYMS) could exist for mappable symbol | |
13846 | @c files. | |
13847 | ||
c906108c | 13848 | @kindex core-file |
09d4efe1 | 13849 | @item core-file @r{[}@var{filename}@r{]} |
4644b6e3 | 13850 | @itemx core |
c906108c SS |
13851 | Specify the whereabouts of a core dump file to be used as the ``contents |
13852 | of memory''. Traditionally, core files contain only some parts of the | |
13853 | address space of the process that generated them; @value{GDBN} can access the | |
13854 | executable file itself for other parts. | |
13855 | ||
13856 | @code{core-file} with no argument specifies that no core file is | |
13857 | to be used. | |
13858 | ||
13859 | Note that the core file is ignored when your program is actually running | |
7a292a7a SS |
13860 | under @value{GDBN}. So, if you have been running your program and you |
13861 | wish to debug a core file instead, you must kill the subprocess in which | |
13862 | the program is running. To do this, use the @code{kill} command | |
79a6e687 | 13863 | (@pxref{Kill Process, ,Killing the Child Process}). |
c906108c | 13864 | |
c906108c SS |
13865 | @kindex add-symbol-file |
13866 | @cindex dynamic linking | |
13867 | @item add-symbol-file @var{filename} @var{address} | |
a94ab193 | 13868 | @itemx add-symbol-file @var{filename} @var{address} @r{[} -readnow @r{]} |
17d9d558 | 13869 | @itemx add-symbol-file @var{filename} @r{-s}@var{section} @var{address} @dots{} |
96a2c332 SS |
13870 | The @code{add-symbol-file} command reads additional symbol table |
13871 | information from the file @var{filename}. You would use this command | |
13872 | when @var{filename} has been dynamically loaded (by some other means) | |
13873 | into the program that is running. @var{address} should be the memory | |
13874 | address at which the file has been loaded; @value{GDBN} cannot figure | |
d167840f EZ |
13875 | this out for itself. You can additionally specify an arbitrary number |
13876 | of @samp{@r{-s}@var{section} @var{address}} pairs, to give an explicit | |
13877 | section name and base address for that section. You can specify any | |
13878 | @var{address} as an expression. | |
c906108c SS |
13879 | |
13880 | The symbol table of the file @var{filename} is added to the symbol table | |
13881 | originally read with the @code{symbol-file} command. You can use the | |
96a2c332 SS |
13882 | @code{add-symbol-file} command any number of times; the new symbol data |
13883 | thus read keeps adding to the old. To discard all old symbol data | |
13884 | instead, use the @code{symbol-file} command without any arguments. | |
c906108c | 13885 | |
17d9d558 JB |
13886 | @cindex relocatable object files, reading symbols from |
13887 | @cindex object files, relocatable, reading symbols from | |
13888 | @cindex reading symbols from relocatable object files | |
13889 | @cindex symbols, reading from relocatable object files | |
13890 | @cindex @file{.o} files, reading symbols from | |
13891 | Although @var{filename} is typically a shared library file, an | |
13892 | executable file, or some other object file which has been fully | |
13893 | relocated for loading into a process, you can also load symbolic | |
13894 | information from relocatable @file{.o} files, as long as: | |
13895 | ||
13896 | @itemize @bullet | |
13897 | @item | |
13898 | the file's symbolic information refers only to linker symbols defined in | |
13899 | that file, not to symbols defined by other object files, | |
13900 | @item | |
13901 | every section the file's symbolic information refers to has actually | |
13902 | been loaded into the inferior, as it appears in the file, and | |
13903 | @item | |
13904 | you can determine the address at which every section was loaded, and | |
13905 | provide these to the @code{add-symbol-file} command. | |
13906 | @end itemize | |
13907 | ||
13908 | @noindent | |
13909 | Some embedded operating systems, like Sun Chorus and VxWorks, can load | |
13910 | relocatable files into an already running program; such systems | |
13911 | typically make the requirements above easy to meet. However, it's | |
13912 | important to recognize that many native systems use complex link | |
49efadf5 | 13913 | procedures (@code{.linkonce} section factoring and C@t{++} constructor table |
17d9d558 JB |
13914 | assembly, for example) that make the requirements difficult to meet. In |
13915 | general, one cannot assume that using @code{add-symbol-file} to read a | |
13916 | relocatable object file's symbolic information will have the same effect | |
13917 | as linking the relocatable object file into the program in the normal | |
13918 | way. | |
13919 | ||
c906108c SS |
13920 | @code{add-symbol-file} does not repeat if you press @key{RET} after using it. |
13921 | ||
c45da7e6 EZ |
13922 | @kindex add-symbol-file-from-memory |
13923 | @cindex @code{syscall DSO} | |
13924 | @cindex load symbols from memory | |
13925 | @item add-symbol-file-from-memory @var{address} | |
13926 | Load symbols from the given @var{address} in a dynamically loaded | |
13927 | object file whose image is mapped directly into the inferior's memory. | |
13928 | For example, the Linux kernel maps a @code{syscall DSO} into each | |
13929 | process's address space; this DSO provides kernel-specific code for | |
13930 | some system calls. The argument can be any expression whose | |
13931 | evaluation yields the address of the file's shared object file header. | |
13932 | For this command to work, you must have used @code{symbol-file} or | |
13933 | @code{exec-file} commands in advance. | |
13934 | ||
09d4efe1 EZ |
13935 | @kindex add-shared-symbol-files |
13936 | @kindex assf | |
13937 | @item add-shared-symbol-files @var{library-file} | |
13938 | @itemx assf @var{library-file} | |
13939 | The @code{add-shared-symbol-files} command can currently be used only | |
13940 | in the Cygwin build of @value{GDBN} on MS-Windows OS, where it is an | |
13941 | alias for the @code{dll-symbols} command (@pxref{Cygwin Native}). | |
13942 | @value{GDBN} automatically looks for shared libraries, however if | |
13943 | @value{GDBN} does not find yours, you can invoke | |
13944 | @code{add-shared-symbol-files}. It takes one argument: the shared | |
13945 | library's file name. @code{assf} is a shorthand alias for | |
13946 | @code{add-shared-symbol-files}. | |
c906108c | 13947 | |
c906108c | 13948 | @kindex section |
09d4efe1 EZ |
13949 | @item section @var{section} @var{addr} |
13950 | The @code{section} command changes the base address of the named | |
13951 | @var{section} of the exec file to @var{addr}. This can be used if the | |
13952 | exec file does not contain section addresses, (such as in the | |
13953 | @code{a.out} format), or when the addresses specified in the file | |
13954 | itself are wrong. Each section must be changed separately. The | |
13955 | @code{info files} command, described below, lists all the sections and | |
13956 | their addresses. | |
c906108c SS |
13957 | |
13958 | @kindex info files | |
13959 | @kindex info target | |
13960 | @item info files | |
13961 | @itemx info target | |
7a292a7a SS |
13962 | @code{info files} and @code{info target} are synonymous; both print the |
13963 | current target (@pxref{Targets, ,Specifying a Debugging Target}), | |
13964 | including the names of the executable and core dump files currently in | |
13965 | use by @value{GDBN}, and the files from which symbols were loaded. The | |
13966 | command @code{help target} lists all possible targets rather than | |
13967 | current ones. | |
13968 | ||
fe95c787 MS |
13969 | @kindex maint info sections |
13970 | @item maint info sections | |
13971 | Another command that can give you extra information about program sections | |
13972 | is @code{maint info sections}. In addition to the section information | |
13973 | displayed by @code{info files}, this command displays the flags and file | |
13974 | offset of each section in the executable and core dump files. In addition, | |
13975 | @code{maint info sections} provides the following command options (which | |
13976 | may be arbitrarily combined): | |
13977 | ||
13978 | @table @code | |
13979 | @item ALLOBJ | |
13980 | Display sections for all loaded object files, including shared libraries. | |
13981 | @item @var{sections} | |
6600abed | 13982 | Display info only for named @var{sections}. |
fe95c787 MS |
13983 | @item @var{section-flags} |
13984 | Display info only for sections for which @var{section-flags} are true. | |
13985 | The section flags that @value{GDBN} currently knows about are: | |
13986 | @table @code | |
13987 | @item ALLOC | |
13988 | Section will have space allocated in the process when loaded. | |
13989 | Set for all sections except those containing debug information. | |
13990 | @item LOAD | |
13991 | Section will be loaded from the file into the child process memory. | |
13992 | Set for pre-initialized code and data, clear for @code{.bss} sections. | |
13993 | @item RELOC | |
13994 | Section needs to be relocated before loading. | |
13995 | @item READONLY | |
13996 | Section cannot be modified by the child process. | |
13997 | @item CODE | |
13998 | Section contains executable code only. | |
6600abed | 13999 | @item DATA |
fe95c787 MS |
14000 | Section contains data only (no executable code). |
14001 | @item ROM | |
14002 | Section will reside in ROM. | |
14003 | @item CONSTRUCTOR | |
14004 | Section contains data for constructor/destructor lists. | |
14005 | @item HAS_CONTENTS | |
14006 | Section is not empty. | |
14007 | @item NEVER_LOAD | |
14008 | An instruction to the linker to not output the section. | |
14009 | @item COFF_SHARED_LIBRARY | |
14010 | A notification to the linker that the section contains | |
14011 | COFF shared library information. | |
14012 | @item IS_COMMON | |
14013 | Section contains common symbols. | |
14014 | @end table | |
14015 | @end table | |
6763aef9 | 14016 | @kindex set trust-readonly-sections |
9c16f35a | 14017 | @cindex read-only sections |
6763aef9 MS |
14018 | @item set trust-readonly-sections on |
14019 | Tell @value{GDBN} that readonly sections in your object file | |
6ca652b0 | 14020 | really are read-only (i.e.@: that their contents will not change). |
6763aef9 MS |
14021 | In that case, @value{GDBN} can fetch values from these sections |
14022 | out of the object file, rather than from the target program. | |
14023 | For some targets (notably embedded ones), this can be a significant | |
14024 | enhancement to debugging performance. | |
14025 | ||
14026 | The default is off. | |
14027 | ||
14028 | @item set trust-readonly-sections off | |
15110bc3 | 14029 | Tell @value{GDBN} not to trust readonly sections. This means that |
6763aef9 MS |
14030 | the contents of the section might change while the program is running, |
14031 | and must therefore be fetched from the target when needed. | |
9c16f35a EZ |
14032 | |
14033 | @item show trust-readonly-sections | |
14034 | Show the current setting of trusting readonly sections. | |
c906108c SS |
14035 | @end table |
14036 | ||
14037 | All file-specifying commands allow both absolute and relative file names | |
14038 | as arguments. @value{GDBN} always converts the file name to an absolute file | |
14039 | name and remembers it that way. | |
14040 | ||
c906108c | 14041 | @cindex shared libraries |
9cceb671 DJ |
14042 | @anchor{Shared Libraries} |
14043 | @value{GDBN} supports @sc{gnu}/Linux, MS-Windows, HP-UX, SunOS, SVr4, Irix, | |
9c16f35a | 14044 | and IBM RS/6000 AIX shared libraries. |
53a5351d | 14045 | |
9cceb671 DJ |
14046 | On MS-Windows @value{GDBN} must be linked with the Expat library to support |
14047 | shared libraries. @xref{Expat}. | |
14048 | ||
c906108c SS |
14049 | @value{GDBN} automatically loads symbol definitions from shared libraries |
14050 | when you use the @code{run} command, or when you examine a core file. | |
14051 | (Before you issue the @code{run} command, @value{GDBN} does not understand | |
14052 | references to a function in a shared library, however---unless you are | |
14053 | debugging a core file). | |
53a5351d JM |
14054 | |
14055 | On HP-UX, if the program loads a library explicitly, @value{GDBN} | |
14056 | automatically loads the symbols at the time of the @code{shl_load} call. | |
14057 | ||
c906108c SS |
14058 | @c FIXME: some @value{GDBN} release may permit some refs to undef |
14059 | @c FIXME...symbols---eg in a break cmd---assuming they are from a shared | |
14060 | @c FIXME...lib; check this from time to time when updating manual | |
14061 | ||
b7209cb4 FF |
14062 | There are times, however, when you may wish to not automatically load |
14063 | symbol definitions from shared libraries, such as when they are | |
14064 | particularly large or there are many of them. | |
14065 | ||
14066 | To control the automatic loading of shared library symbols, use the | |
14067 | commands: | |
14068 | ||
14069 | @table @code | |
14070 | @kindex set auto-solib-add | |
14071 | @item set auto-solib-add @var{mode} | |
14072 | If @var{mode} is @code{on}, symbols from all shared object libraries | |
14073 | will be loaded automatically when the inferior begins execution, you | |
14074 | attach to an independently started inferior, or when the dynamic linker | |
14075 | informs @value{GDBN} that a new library has been loaded. If @var{mode} | |
14076 | is @code{off}, symbols must be loaded manually, using the | |
14077 | @code{sharedlibrary} command. The default value is @code{on}. | |
14078 | ||
dcaf7c2c EZ |
14079 | @cindex memory used for symbol tables |
14080 | If your program uses lots of shared libraries with debug info that | |
14081 | takes large amounts of memory, you can decrease the @value{GDBN} | |
14082 | memory footprint by preventing it from automatically loading the | |
14083 | symbols from shared libraries. To that end, type @kbd{set | |
14084 | auto-solib-add off} before running the inferior, then load each | |
14085 | library whose debug symbols you do need with @kbd{sharedlibrary | |
d3e8051b | 14086 | @var{regexp}}, where @var{regexp} is a regular expression that matches |
dcaf7c2c EZ |
14087 | the libraries whose symbols you want to be loaded. |
14088 | ||
b7209cb4 FF |
14089 | @kindex show auto-solib-add |
14090 | @item show auto-solib-add | |
14091 | Display the current autoloading mode. | |
14092 | @end table | |
14093 | ||
c45da7e6 | 14094 | @cindex load shared library |
b7209cb4 FF |
14095 | To explicitly load shared library symbols, use the @code{sharedlibrary} |
14096 | command: | |
14097 | ||
c906108c SS |
14098 | @table @code |
14099 | @kindex info sharedlibrary | |
14100 | @kindex info share | |
55333a84 DE |
14101 | @item info share @var{regex} |
14102 | @itemx info sharedlibrary @var{regex} | |
14103 | Print the names of the shared libraries which are currently loaded | |
14104 | that match @var{regex}. If @var{regex} is omitted then print | |
14105 | all shared libraries that are loaded. | |
c906108c SS |
14106 | |
14107 | @kindex sharedlibrary | |
14108 | @kindex share | |
14109 | @item sharedlibrary @var{regex} | |
14110 | @itemx share @var{regex} | |
c906108c SS |
14111 | Load shared object library symbols for files matching a |
14112 | Unix regular expression. | |
14113 | As with files loaded automatically, it only loads shared libraries | |
14114 | required by your program for a core file or after typing @code{run}. If | |
14115 | @var{regex} is omitted all shared libraries required by your program are | |
14116 | loaded. | |
c45da7e6 EZ |
14117 | |
14118 | @item nosharedlibrary | |
14119 | @kindex nosharedlibrary | |
14120 | @cindex unload symbols from shared libraries | |
14121 | Unload all shared object library symbols. This discards all symbols | |
14122 | that have been loaded from all shared libraries. Symbols from shared | |
14123 | libraries that were loaded by explicit user requests are not | |
14124 | discarded. | |
c906108c SS |
14125 | @end table |
14126 | ||
721c2651 EZ |
14127 | Sometimes you may wish that @value{GDBN} stops and gives you control |
14128 | when any of shared library events happen. Use the @code{set | |
14129 | stop-on-solib-events} command for this: | |
14130 | ||
14131 | @table @code | |
14132 | @item set stop-on-solib-events | |
14133 | @kindex set stop-on-solib-events | |
14134 | This command controls whether @value{GDBN} should give you control | |
14135 | when the dynamic linker notifies it about some shared library event. | |
14136 | The most common event of interest is loading or unloading of a new | |
14137 | shared library. | |
14138 | ||
14139 | @item show stop-on-solib-events | |
14140 | @kindex show stop-on-solib-events | |
14141 | Show whether @value{GDBN} stops and gives you control when shared | |
14142 | library events happen. | |
14143 | @end table | |
14144 | ||
f5ebfba0 | 14145 | Shared libraries are also supported in many cross or remote debugging |
f1838a98 UW |
14146 | configurations. @value{GDBN} needs to have access to the target's libraries; |
14147 | this can be accomplished either by providing copies of the libraries | |
14148 | on the host system, or by asking @value{GDBN} to automatically retrieve the | |
14149 | libraries from the target. If copies of the target libraries are | |
14150 | provided, they need to be the same as the target libraries, although the | |
f5ebfba0 DJ |
14151 | copies on the target can be stripped as long as the copies on the host are |
14152 | not. | |
14153 | ||
59b7b46f EZ |
14154 | @cindex where to look for shared libraries |
14155 | For remote debugging, you need to tell @value{GDBN} where the target | |
14156 | libraries are, so that it can load the correct copies---otherwise, it | |
14157 | may try to load the host's libraries. @value{GDBN} has two variables | |
14158 | to specify the search directories for target libraries. | |
f5ebfba0 DJ |
14159 | |
14160 | @table @code | |
59b7b46f | 14161 | @cindex prefix for shared library file names |
f822c95b | 14162 | @cindex system root, alternate |
f5ebfba0 | 14163 | @kindex set solib-absolute-prefix |
f822c95b DJ |
14164 | @kindex set sysroot |
14165 | @item set sysroot @var{path} | |
14166 | Use @var{path} as the system root for the program being debugged. Any | |
14167 | absolute shared library paths will be prefixed with @var{path}; many | |
14168 | runtime loaders store the absolute paths to the shared library in the | |
14169 | target program's memory. If you use @code{set sysroot} to find shared | |
14170 | libraries, they need to be laid out in the same way that they are on | |
14171 | the target, with e.g.@: a @file{/lib} and @file{/usr/lib} hierarchy | |
14172 | under @var{path}. | |
14173 | ||
f1838a98 UW |
14174 | If @var{path} starts with the sequence @file{remote:}, @value{GDBN} will |
14175 | retrieve the target libraries from the remote system. This is only | |
14176 | supported when using a remote target that supports the @code{remote get} | |
14177 | command (@pxref{File Transfer,,Sending files to a remote system}). | |
14178 | The part of @var{path} following the initial @file{remote:} | |
14179 | (if present) is used as system root prefix on the remote file system. | |
14180 | @footnote{If you want to specify a local system root using a directory | |
14181 | that happens to be named @file{remote:}, you need to use some equivalent | |
14182 | variant of the name like @file{./remote:}.} | |
14183 | ||
f822c95b DJ |
14184 | The @code{set solib-absolute-prefix} command is an alias for @code{set |
14185 | sysroot}. | |
14186 | ||
14187 | @cindex default system root | |
59b7b46f | 14188 | @cindex @samp{--with-sysroot} |
f822c95b DJ |
14189 | You can set the default system root by using the configure-time |
14190 | @samp{--with-sysroot} option. If the system root is inside | |
14191 | @value{GDBN}'s configured binary prefix (set with @samp{--prefix} or | |
14192 | @samp{--exec-prefix}), then the default system root will be updated | |
14193 | automatically if the installed @value{GDBN} is moved to a new | |
14194 | location. | |
14195 | ||
14196 | @kindex show sysroot | |
14197 | @item show sysroot | |
f5ebfba0 DJ |
14198 | Display the current shared library prefix. |
14199 | ||
14200 | @kindex set solib-search-path | |
14201 | @item set solib-search-path @var{path} | |
f822c95b DJ |
14202 | If this variable is set, @var{path} is a colon-separated list of |
14203 | directories to search for shared libraries. @samp{solib-search-path} | |
14204 | is used after @samp{sysroot} fails to locate the library, or if the | |
14205 | path to the library is relative instead of absolute. If you want to | |
14206 | use @samp{solib-search-path} instead of @samp{sysroot}, be sure to set | |
d3e8051b | 14207 | @samp{sysroot} to a nonexistent directory to prevent @value{GDBN} from |
f822c95b | 14208 | finding your host's libraries. @samp{sysroot} is preferred; setting |
d3e8051b | 14209 | it to a nonexistent directory may interfere with automatic loading |
f822c95b | 14210 | of shared library symbols. |
f5ebfba0 DJ |
14211 | |
14212 | @kindex show solib-search-path | |
14213 | @item show solib-search-path | |
14214 | Display the current shared library search path. | |
14215 | @end table | |
14216 | ||
5b5d99cf JB |
14217 | |
14218 | @node Separate Debug Files | |
14219 | @section Debugging Information in Separate Files | |
14220 | @cindex separate debugging information files | |
14221 | @cindex debugging information in separate files | |
14222 | @cindex @file{.debug} subdirectories | |
14223 | @cindex debugging information directory, global | |
14224 | @cindex global debugging information directory | |
c7e83d54 EZ |
14225 | @cindex build ID, and separate debugging files |
14226 | @cindex @file{.build-id} directory | |
5b5d99cf JB |
14227 | |
14228 | @value{GDBN} allows you to put a program's debugging information in a | |
14229 | file separate from the executable itself, in a way that allows | |
14230 | @value{GDBN} to find and load the debugging information automatically. | |
c7e83d54 EZ |
14231 | Since debugging information can be very large---sometimes larger |
14232 | than the executable code itself---some systems distribute debugging | |
5b5d99cf JB |
14233 | information for their executables in separate files, which users can |
14234 | install only when they need to debug a problem. | |
14235 | ||
c7e83d54 EZ |
14236 | @value{GDBN} supports two ways of specifying the separate debug info |
14237 | file: | |
5b5d99cf JB |
14238 | |
14239 | @itemize @bullet | |
14240 | @item | |
c7e83d54 EZ |
14241 | The executable contains a @dfn{debug link} that specifies the name of |
14242 | the separate debug info file. The separate debug file's name is | |
14243 | usually @file{@var{executable}.debug}, where @var{executable} is the | |
14244 | name of the corresponding executable file without leading directories | |
14245 | (e.g., @file{ls.debug} for @file{/usr/bin/ls}). In addition, the | |
99e008fe EZ |
14246 | debug link specifies a 32-bit @dfn{Cyclic Redundancy Check} (CRC) |
14247 | checksum for the debug file, which @value{GDBN} uses to validate that | |
14248 | the executable and the debug file came from the same build. | |
c7e83d54 EZ |
14249 | |
14250 | @item | |
7e27a47a | 14251 | The executable contains a @dfn{build ID}, a unique bit string that is |
c7e83d54 | 14252 | also present in the corresponding debug info file. (This is supported |
7e27a47a EZ |
14253 | only on some operating systems, notably those which use the ELF format |
14254 | for binary files and the @sc{gnu} Binutils.) For more details about | |
14255 | this feature, see the description of the @option{--build-id} | |
14256 | command-line option in @ref{Options, , Command Line Options, ld.info, | |
14257 | The GNU Linker}. The debug info file's name is not specified | |
14258 | explicitly by the build ID, but can be computed from the build ID, see | |
14259 | below. | |
d3750b24 JK |
14260 | @end itemize |
14261 | ||
c7e83d54 EZ |
14262 | Depending on the way the debug info file is specified, @value{GDBN} |
14263 | uses two different methods of looking for the debug file: | |
d3750b24 JK |
14264 | |
14265 | @itemize @bullet | |
14266 | @item | |
c7e83d54 EZ |
14267 | For the ``debug link'' method, @value{GDBN} looks up the named file in |
14268 | the directory of the executable file, then in a subdirectory of that | |
14269 | directory named @file{.debug}, and finally under the global debug | |
14270 | directory, in a subdirectory whose name is identical to the leading | |
14271 | directories of the executable's absolute file name. | |
14272 | ||
14273 | @item | |
83f83d7f | 14274 | For the ``build ID'' method, @value{GDBN} looks in the |
c7e83d54 EZ |
14275 | @file{.build-id} subdirectory of the global debug directory for a file |
14276 | named @file{@var{nn}/@var{nnnnnnnn}.debug}, where @var{nn} are the | |
7e27a47a EZ |
14277 | first 2 hex characters of the build ID bit string, and @var{nnnnnnnn} |
14278 | are the rest of the bit string. (Real build ID strings are 32 or more | |
14279 | hex characters, not 10.) | |
c7e83d54 EZ |
14280 | @end itemize |
14281 | ||
14282 | So, for example, suppose you ask @value{GDBN} to debug | |
7e27a47a EZ |
14283 | @file{/usr/bin/ls}, which has a debug link that specifies the |
14284 | file @file{ls.debug}, and a build ID whose value in hex is | |
c7e83d54 EZ |
14285 | @code{abcdef1234}. If the global debug directory is |
14286 | @file{/usr/lib/debug}, then @value{GDBN} will look for the following | |
14287 | debug information files, in the indicated order: | |
14288 | ||
14289 | @itemize @minus | |
14290 | @item | |
14291 | @file{/usr/lib/debug/.build-id/ab/cdef1234.debug} | |
d3750b24 | 14292 | @item |
c7e83d54 | 14293 | @file{/usr/bin/ls.debug} |
5b5d99cf | 14294 | @item |
c7e83d54 | 14295 | @file{/usr/bin/.debug/ls.debug} |
5b5d99cf | 14296 | @item |
c7e83d54 | 14297 | @file{/usr/lib/debug/usr/bin/ls.debug}. |
5b5d99cf | 14298 | @end itemize |
5b5d99cf JB |
14299 | |
14300 | You can set the global debugging info directory's name, and view the | |
14301 | name @value{GDBN} is currently using. | |
14302 | ||
14303 | @table @code | |
14304 | ||
14305 | @kindex set debug-file-directory | |
24ddea62 JK |
14306 | @item set debug-file-directory @var{directories} |
14307 | Set the directories which @value{GDBN} searches for separate debugging | |
14308 | information files to @var{directory}. Multiple directory components can be set | |
14309 | concatenating them by a directory separator. | |
5b5d99cf JB |
14310 | |
14311 | @kindex show debug-file-directory | |
14312 | @item show debug-file-directory | |
24ddea62 | 14313 | Show the directories @value{GDBN} searches for separate debugging |
5b5d99cf JB |
14314 | information files. |
14315 | ||
14316 | @end table | |
14317 | ||
14318 | @cindex @code{.gnu_debuglink} sections | |
c7e83d54 | 14319 | @cindex debug link sections |
5b5d99cf JB |
14320 | A debug link is a special section of the executable file named |
14321 | @code{.gnu_debuglink}. The section must contain: | |
14322 | ||
14323 | @itemize | |
14324 | @item | |
14325 | A filename, with any leading directory components removed, followed by | |
14326 | a zero byte, | |
14327 | @item | |
14328 | zero to three bytes of padding, as needed to reach the next four-byte | |
14329 | boundary within the section, and | |
14330 | @item | |
14331 | a four-byte CRC checksum, stored in the same endianness used for the | |
14332 | executable file itself. The checksum is computed on the debugging | |
14333 | information file's full contents by the function given below, passing | |
14334 | zero as the @var{crc} argument. | |
14335 | @end itemize | |
14336 | ||
14337 | Any executable file format can carry a debug link, as long as it can | |
14338 | contain a section named @code{.gnu_debuglink} with the contents | |
14339 | described above. | |
14340 | ||
d3750b24 | 14341 | @cindex @code{.note.gnu.build-id} sections |
c7e83d54 | 14342 | @cindex build ID sections |
7e27a47a EZ |
14343 | The build ID is a special section in the executable file (and in other |
14344 | ELF binary files that @value{GDBN} may consider). This section is | |
14345 | often named @code{.note.gnu.build-id}, but that name is not mandatory. | |
14346 | It contains unique identification for the built files---the ID remains | |
14347 | the same across multiple builds of the same build tree. The default | |
14348 | algorithm SHA1 produces 160 bits (40 hexadecimal characters) of the | |
14349 | content for the build ID string. The same section with an identical | |
14350 | value is present in the original built binary with symbols, in its | |
14351 | stripped variant, and in the separate debugging information file. | |
d3750b24 | 14352 | |
5b5d99cf JB |
14353 | The debugging information file itself should be an ordinary |
14354 | executable, containing a full set of linker symbols, sections, and | |
14355 | debugging information. The sections of the debugging information file | |
c7e83d54 EZ |
14356 | should have the same names, addresses, and sizes as the original file, |
14357 | but they need not contain any data---much like a @code{.bss} section | |
5b5d99cf JB |
14358 | in an ordinary executable. |
14359 | ||
7e27a47a | 14360 | The @sc{gnu} binary utilities (Binutils) package includes the |
c7e83d54 EZ |
14361 | @samp{objcopy} utility that can produce |
14362 | the separated executable / debugging information file pairs using the | |
14363 | following commands: | |
14364 | ||
14365 | @smallexample | |
14366 | @kbd{objcopy --only-keep-debug foo foo.debug} | |
14367 | @kbd{strip -g foo} | |
c7e83d54 EZ |
14368 | @end smallexample |
14369 | ||
14370 | @noindent | |
14371 | These commands remove the debugging | |
83f83d7f JK |
14372 | information from the executable file @file{foo} and place it in the file |
14373 | @file{foo.debug}. You can use the first, second or both methods to link the | |
14374 | two files: | |
14375 | ||
14376 | @itemize @bullet | |
14377 | @item | |
14378 | The debug link method needs the following additional command to also leave | |
14379 | behind a debug link in @file{foo}: | |
14380 | ||
14381 | @smallexample | |
14382 | @kbd{objcopy --add-gnu-debuglink=foo.debug foo} | |
14383 | @end smallexample | |
14384 | ||
14385 | Ulrich Drepper's @file{elfutils} package, starting with version 0.53, contains | |
d3750b24 | 14386 | a version of the @code{strip} command such that the command @kbd{strip foo -f |
83f83d7f JK |
14387 | foo.debug} has the same functionality as the two @code{objcopy} commands and |
14388 | the @code{ln -s} command above, together. | |
14389 | ||
14390 | @item | |
14391 | Build ID gets embedded into the main executable using @code{ld --build-id} or | |
14392 | the @value{NGCC} counterpart @code{gcc -Wl,--build-id}. Build ID support plus | |
14393 | compatibility fixes for debug files separation are present in @sc{gnu} binary | |
7e27a47a | 14394 | utilities (Binutils) package since version 2.18. |
83f83d7f JK |
14395 | @end itemize |
14396 | ||
14397 | @noindent | |
d3750b24 | 14398 | |
99e008fe EZ |
14399 | @cindex CRC algorithm definition |
14400 | The CRC used in @code{.gnu_debuglink} is the CRC-32 defined in | |
14401 | IEEE 802.3 using the polynomial: | |
14402 | ||
14403 | @c TexInfo requires naked braces for multi-digit exponents for Tex | |
14404 | @c output, but this causes HTML output to barf. HTML has to be set using | |
14405 | @c raw commands. So we end up having to specify this equation in 2 | |
14406 | @c different ways! | |
14407 | @ifhtml | |
14408 | @display | |
14409 | @html | |
14410 | <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> | |
14411 | + <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 | |
14412 | @end html | |
14413 | @end display | |
14414 | @end ifhtml | |
14415 | @ifnothtml | |
14416 | @display | |
14417 | @math{x^{32} + x^{26} + x^{23} + x^{22} + x^{16} + x^{12} + x^{11}} | |
14418 | @math{+ x^{10} + x^8 + x^7 + x^5 + x^4 + x^2 + x + 1} | |
14419 | @end display | |
14420 | @end ifnothtml | |
14421 | ||
14422 | The function is computed byte at a time, taking the least | |
14423 | significant bit of each byte first. The initial pattern | |
14424 | @code{0xffffffff} is used, to ensure leading zeros affect the CRC and | |
14425 | the final result is inverted to ensure trailing zeros also affect the | |
14426 | CRC. | |
14427 | ||
14428 | @emph{Note:} This is the same CRC polynomial as used in handling the | |
14429 | @dfn{Remote Serial Protocol} @code{qCRC} packet (@pxref{Remote Protocol, | |
14430 | , @value{GDBN} Remote Serial Protocol}). However in the | |
14431 | case of the Remote Serial Protocol, the CRC is computed @emph{most} | |
14432 | significant bit first, and the result is not inverted, so trailing | |
14433 | zeros have no effect on the CRC value. | |
14434 | ||
14435 | To complete the description, we show below the code of the function | |
14436 | which produces the CRC used in @code{.gnu_debuglink}. Inverting the | |
14437 | initially supplied @code{crc} argument means that an initial call to | |
14438 | this function passing in zero will start computing the CRC using | |
14439 | @code{0xffffffff}. | |
5b5d99cf | 14440 | |
4644b6e3 | 14441 | @kindex gnu_debuglink_crc32 |
5b5d99cf JB |
14442 | @smallexample |
14443 | unsigned long | |
14444 | gnu_debuglink_crc32 (unsigned long crc, | |
14445 | unsigned char *buf, size_t len) | |
14446 | @{ | |
14447 | static const unsigned long crc32_table[256] = | |
14448 | @{ | |
14449 | 0x00000000, 0x77073096, 0xee0e612c, 0x990951ba, 0x076dc419, | |
14450 | 0x706af48f, 0xe963a535, 0x9e6495a3, 0x0edb8832, 0x79dcb8a4, | |
14451 | 0xe0d5e91e, 0x97d2d988, 0x09b64c2b, 0x7eb17cbd, 0xe7b82d07, | |
14452 | 0x90bf1d91, 0x1db71064, 0x6ab020f2, 0xf3b97148, 0x84be41de, | |
14453 | 0x1adad47d, 0x6ddde4eb, 0xf4d4b551, 0x83d385c7, 0x136c9856, | |
14454 | 0x646ba8c0, 0xfd62f97a, 0x8a65c9ec, 0x14015c4f, 0x63066cd9, | |
14455 | 0xfa0f3d63, 0x8d080df5, 0x3b6e20c8, 0x4c69105e, 0xd56041e4, | |
14456 | 0xa2677172, 0x3c03e4d1, 0x4b04d447, 0xd20d85fd, 0xa50ab56b, | |
14457 | 0x35b5a8fa, 0x42b2986c, 0xdbbbc9d6, 0xacbcf940, 0x32d86ce3, | |
14458 | 0x45df5c75, 0xdcd60dcf, 0xabd13d59, 0x26d930ac, 0x51de003a, | |
14459 | 0xc8d75180, 0xbfd06116, 0x21b4f4b5, 0x56b3c423, 0xcfba9599, | |
14460 | 0xb8bda50f, 0x2802b89e, 0x5f058808, 0xc60cd9b2, 0xb10be924, | |
14461 | 0x2f6f7c87, 0x58684c11, 0xc1611dab, 0xb6662d3d, 0x76dc4190, | |
14462 | 0x01db7106, 0x98d220bc, 0xefd5102a, 0x71b18589, 0x06b6b51f, | |
14463 | 0x9fbfe4a5, 0xe8b8d433, 0x7807c9a2, 0x0f00f934, 0x9609a88e, | |
14464 | 0xe10e9818, 0x7f6a0dbb, 0x086d3d2d, 0x91646c97, 0xe6635c01, | |
14465 | 0x6b6b51f4, 0x1c6c6162, 0x856530d8, 0xf262004e, 0x6c0695ed, | |
14466 | 0x1b01a57b, 0x8208f4c1, 0xf50fc457, 0x65b0d9c6, 0x12b7e950, | |
14467 | 0x8bbeb8ea, 0xfcb9887c, 0x62dd1ddf, 0x15da2d49, 0x8cd37cf3, | |
14468 | 0xfbd44c65, 0x4db26158, 0x3ab551ce, 0xa3bc0074, 0xd4bb30e2, | |
14469 | 0x4adfa541, 0x3dd895d7, 0xa4d1c46d, 0xd3d6f4fb, 0x4369e96a, | |
14470 | 0x346ed9fc, 0xad678846, 0xda60b8d0, 0x44042d73, 0x33031de5, | |
14471 | 0xaa0a4c5f, 0xdd0d7cc9, 0x5005713c, 0x270241aa, 0xbe0b1010, | |
14472 | 0xc90c2086, 0x5768b525, 0x206f85b3, 0xb966d409, 0xce61e49f, | |
14473 | 0x5edef90e, 0x29d9c998, 0xb0d09822, 0xc7d7a8b4, 0x59b33d17, | |
14474 | 0x2eb40d81, 0xb7bd5c3b, 0xc0ba6cad, 0xedb88320, 0x9abfb3b6, | |
14475 | 0x03b6e20c, 0x74b1d29a, 0xead54739, 0x9dd277af, 0x04db2615, | |
14476 | 0x73dc1683, 0xe3630b12, 0x94643b84, 0x0d6d6a3e, 0x7a6a5aa8, | |
14477 | 0xe40ecf0b, 0x9309ff9d, 0x0a00ae27, 0x7d079eb1, 0xf00f9344, | |
14478 | 0x8708a3d2, 0x1e01f268, 0x6906c2fe, 0xf762575d, 0x806567cb, | |
14479 | 0x196c3671, 0x6e6b06e7, 0xfed41b76, 0x89d32be0, 0x10da7a5a, | |
14480 | 0x67dd4acc, 0xf9b9df6f, 0x8ebeeff9, 0x17b7be43, 0x60b08ed5, | |
14481 | 0xd6d6a3e8, 0xa1d1937e, 0x38d8c2c4, 0x4fdff252, 0xd1bb67f1, | |
14482 | 0xa6bc5767, 0x3fb506dd, 0x48b2364b, 0xd80d2bda, 0xaf0a1b4c, | |
14483 | 0x36034af6, 0x41047a60, 0xdf60efc3, 0xa867df55, 0x316e8eef, | |
14484 | 0x4669be79, 0xcb61b38c, 0xbc66831a, 0x256fd2a0, 0x5268e236, | |
14485 | 0xcc0c7795, 0xbb0b4703, 0x220216b9, 0x5505262f, 0xc5ba3bbe, | |
14486 | 0xb2bd0b28, 0x2bb45a92, 0x5cb36a04, 0xc2d7ffa7, 0xb5d0cf31, | |
14487 | 0x2cd99e8b, 0x5bdeae1d, 0x9b64c2b0, 0xec63f226, 0x756aa39c, | |
14488 | 0x026d930a, 0x9c0906a9, 0xeb0e363f, 0x72076785, 0x05005713, | |
14489 | 0x95bf4a82, 0xe2b87a14, 0x7bb12bae, 0x0cb61b38, 0x92d28e9b, | |
14490 | 0xe5d5be0d, 0x7cdcefb7, 0x0bdbdf21, 0x86d3d2d4, 0xf1d4e242, | |
14491 | 0x68ddb3f8, 0x1fda836e, 0x81be16cd, 0xf6b9265b, 0x6fb077e1, | |
14492 | 0x18b74777, 0x88085ae6, 0xff0f6a70, 0x66063bca, 0x11010b5c, | |
14493 | 0x8f659eff, 0xf862ae69, 0x616bffd3, 0x166ccf45, 0xa00ae278, | |
14494 | 0xd70dd2ee, 0x4e048354, 0x3903b3c2, 0xa7672661, 0xd06016f7, | |
14495 | 0x4969474d, 0x3e6e77db, 0xaed16a4a, 0xd9d65adc, 0x40df0b66, | |
14496 | 0x37d83bf0, 0xa9bcae53, 0xdebb9ec5, 0x47b2cf7f, 0x30b5ffe9, | |
14497 | 0xbdbdf21c, 0xcabac28a, 0x53b39330, 0x24b4a3a6, 0xbad03605, | |
14498 | 0xcdd70693, 0x54de5729, 0x23d967bf, 0xb3667a2e, 0xc4614ab8, | |
14499 | 0x5d681b02, 0x2a6f2b94, 0xb40bbe37, 0xc30c8ea1, 0x5a05df1b, | |
14500 | 0x2d02ef8d | |
14501 | @}; | |
14502 | unsigned char *end; | |
14503 | ||
14504 | crc = ~crc & 0xffffffff; | |
14505 | for (end = buf + len; buf < end; ++buf) | |
14506 | crc = crc32_table[(crc ^ *buf) & 0xff] ^ (crc >> 8); | |
e7a3abfc | 14507 | return ~crc & 0xffffffff; |
5b5d99cf JB |
14508 | @} |
14509 | @end smallexample | |
14510 | ||
c7e83d54 EZ |
14511 | @noindent |
14512 | This computation does not apply to the ``build ID'' method. | |
14513 | ||
5b5d99cf | 14514 | |
6d2ebf8b | 14515 | @node Symbol Errors |
79a6e687 | 14516 | @section Errors Reading Symbol Files |
c906108c SS |
14517 | |
14518 | While reading a symbol file, @value{GDBN} occasionally encounters problems, | |
14519 | such as symbol types it does not recognize, or known bugs in compiler | |
14520 | output. By default, @value{GDBN} does not notify you of such problems, since | |
14521 | they are relatively common and primarily of interest to people | |
14522 | debugging compilers. If you are interested in seeing information | |
14523 | about ill-constructed symbol tables, you can either ask @value{GDBN} to print | |
14524 | only one message about each such type of problem, no matter how many | |
14525 | times the problem occurs; or you can ask @value{GDBN} to print more messages, | |
14526 | to see how many times the problems occur, with the @code{set | |
79a6e687 BW |
14527 | complaints} command (@pxref{Messages/Warnings, ,Optional Warnings and |
14528 | Messages}). | |
c906108c SS |
14529 | |
14530 | The messages currently printed, and their meanings, include: | |
14531 | ||
14532 | @table @code | |
14533 | @item inner block not inside outer block in @var{symbol} | |
14534 | ||
14535 | The symbol information shows where symbol scopes begin and end | |
14536 | (such as at the start of a function or a block of statements). This | |
14537 | error indicates that an inner scope block is not fully contained | |
14538 | in its outer scope blocks. | |
14539 | ||
14540 | @value{GDBN} circumvents the problem by treating the inner block as if it had | |
14541 | the same scope as the outer block. In the error message, @var{symbol} | |
14542 | may be shown as ``@code{(don't know)}'' if the outer block is not a | |
14543 | function. | |
14544 | ||
14545 | @item block at @var{address} out of order | |
14546 | ||
14547 | The symbol information for symbol scope blocks should occur in | |
14548 | order of increasing addresses. This error indicates that it does not | |
14549 | do so. | |
14550 | ||
14551 | @value{GDBN} does not circumvent this problem, and has trouble | |
14552 | locating symbols in the source file whose symbols it is reading. (You | |
14553 | can often determine what source file is affected by specifying | |
79a6e687 BW |
14554 | @code{set verbose on}. @xref{Messages/Warnings, ,Optional Warnings and |
14555 | Messages}.) | |
c906108c SS |
14556 | |
14557 | @item bad block start address patched | |
14558 | ||
14559 | The symbol information for a symbol scope block has a start address | |
14560 | smaller than the address of the preceding source line. This is known | |
14561 | to occur in the SunOS 4.1.1 (and earlier) C compiler. | |
14562 | ||
14563 | @value{GDBN} circumvents the problem by treating the symbol scope block as | |
14564 | starting on the previous source line. | |
14565 | ||
14566 | @item bad string table offset in symbol @var{n} | |
14567 | ||
14568 | @cindex foo | |
14569 | Symbol number @var{n} contains a pointer into the string table which is | |
14570 | larger than the size of the string table. | |
14571 | ||
14572 | @value{GDBN} circumvents the problem by considering the symbol to have the | |
14573 | name @code{foo}, which may cause other problems if many symbols end up | |
14574 | with this name. | |
14575 | ||
14576 | @item unknown symbol type @code{0x@var{nn}} | |
14577 | ||
7a292a7a SS |
14578 | The symbol information contains new data types that @value{GDBN} does |
14579 | not yet know how to read. @code{0x@var{nn}} is the symbol type of the | |
d4f3574e | 14580 | uncomprehended information, in hexadecimal. |
c906108c | 14581 | |
7a292a7a SS |
14582 | @value{GDBN} circumvents the error by ignoring this symbol information. |
14583 | This usually allows you to debug your program, though certain symbols | |
c906108c | 14584 | are not accessible. If you encounter such a problem and feel like |
7a292a7a SS |
14585 | debugging it, you can debug @code{@value{GDBP}} with itself, breakpoint |
14586 | on @code{complain}, then go up to the function @code{read_dbx_symtab} | |
14587 | and examine @code{*bufp} to see the symbol. | |
c906108c SS |
14588 | |
14589 | @item stub type has NULL name | |
c906108c | 14590 | |
7a292a7a | 14591 | @value{GDBN} could not find the full definition for a struct or class. |
c906108c | 14592 | |
7a292a7a | 14593 | @item const/volatile indicator missing (ok if using g++ v1.x), got@dots{} |
b37052ae | 14594 | The symbol information for a C@t{++} member function is missing some |
7a292a7a SS |
14595 | information that recent versions of the compiler should have output for |
14596 | it. | |
c906108c SS |
14597 | |
14598 | @item info mismatch between compiler and debugger | |
14599 | ||
14600 | @value{GDBN} could not parse a type specification output by the compiler. | |
7a292a7a | 14601 | |
c906108c SS |
14602 | @end table |
14603 | ||
b14b1491 TT |
14604 | @node Data Files |
14605 | @section GDB Data Files | |
14606 | ||
14607 | @cindex prefix for data files | |
14608 | @value{GDBN} will sometimes read an auxiliary data file. These files | |
14609 | are kept in a directory known as the @dfn{data directory}. | |
14610 | ||
14611 | You can set the data directory's name, and view the name @value{GDBN} | |
14612 | is currently using. | |
14613 | ||
14614 | @table @code | |
14615 | @kindex set data-directory | |
14616 | @item set data-directory @var{directory} | |
14617 | Set the directory which @value{GDBN} searches for auxiliary data files | |
14618 | to @var{directory}. | |
14619 | ||
14620 | @kindex show data-directory | |
14621 | @item show data-directory | |
14622 | Show the directory @value{GDBN} searches for auxiliary data files. | |
14623 | @end table | |
14624 | ||
14625 | @cindex default data directory | |
14626 | @cindex @samp{--with-gdb-datadir} | |
14627 | You can set the default data directory by using the configure-time | |
14628 | @samp{--with-gdb-datadir} option. If the data directory is inside | |
14629 | @value{GDBN}'s configured binary prefix (set with @samp{--prefix} or | |
14630 | @samp{--exec-prefix}), then the default data directory will be updated | |
14631 | automatically if the installed @value{GDBN} is moved to a new | |
14632 | location. | |
14633 | ||
6d2ebf8b | 14634 | @node Targets |
c906108c | 14635 | @chapter Specifying a Debugging Target |
7a292a7a | 14636 | |
c906108c | 14637 | @cindex debugging target |
c906108c | 14638 | A @dfn{target} is the execution environment occupied by your program. |
53a5351d JM |
14639 | |
14640 | Often, @value{GDBN} runs in the same host environment as your program; | |
14641 | in that case, the debugging target is specified as a side effect when | |
14642 | you use the @code{file} or @code{core} commands. When you need more | |
c906108c SS |
14643 | flexibility---for example, running @value{GDBN} on a physically separate |
14644 | host, or controlling a standalone system over a serial port or a | |
53a5351d JM |
14645 | realtime system over a TCP/IP connection---you can use the @code{target} |
14646 | command to specify one of the target types configured for @value{GDBN} | |
79a6e687 | 14647 | (@pxref{Target Commands, ,Commands for Managing Targets}). |
c906108c | 14648 | |
a8f24a35 EZ |
14649 | @cindex target architecture |
14650 | It is possible to build @value{GDBN} for several different @dfn{target | |
14651 | architectures}. When @value{GDBN} is built like that, you can choose | |
14652 | one of the available architectures with the @kbd{set architecture} | |
14653 | command. | |
14654 | ||
14655 | @table @code | |
14656 | @kindex set architecture | |
14657 | @kindex show architecture | |
14658 | @item set architecture @var{arch} | |
14659 | This command sets the current target architecture to @var{arch}. The | |
14660 | value of @var{arch} can be @code{"auto"}, in addition to one of the | |
14661 | supported architectures. | |
14662 | ||
14663 | @item show architecture | |
14664 | Show the current target architecture. | |
9c16f35a EZ |
14665 | |
14666 | @item set processor | |
14667 | @itemx processor | |
14668 | @kindex set processor | |
14669 | @kindex show processor | |
14670 | These are alias commands for, respectively, @code{set architecture} | |
14671 | and @code{show architecture}. | |
a8f24a35 EZ |
14672 | @end table |
14673 | ||
c906108c SS |
14674 | @menu |
14675 | * Active Targets:: Active targets | |
14676 | * Target Commands:: Commands for managing targets | |
c906108c | 14677 | * Byte Order:: Choosing target byte order |
c906108c SS |
14678 | @end menu |
14679 | ||
6d2ebf8b | 14680 | @node Active Targets |
79a6e687 | 14681 | @section Active Targets |
7a292a7a | 14682 | |
c906108c SS |
14683 | @cindex stacking targets |
14684 | @cindex active targets | |
14685 | @cindex multiple targets | |
14686 | ||
c906108c | 14687 | There are three classes of targets: processes, core files, and |
7a292a7a SS |
14688 | executable files. @value{GDBN} can work concurrently on up to three |
14689 | active targets, one in each class. This allows you to (for example) | |
14690 | start a process and inspect its activity without abandoning your work on | |
14691 | a core file. | |
c906108c SS |
14692 | |
14693 | For example, if you execute @samp{gdb a.out}, then the executable file | |
14694 | @code{a.out} is the only active target. If you designate a core file as | |
14695 | well---presumably from a prior run that crashed and coredumped---then | |
14696 | @value{GDBN} has two active targets and uses them in tandem, looking | |
14697 | first in the corefile target, then in the executable file, to satisfy | |
14698 | requests for memory addresses. (Typically, these two classes of target | |
14699 | are complementary, since core files contain only a program's | |
14700 | read-write memory---variables and so on---plus machine status, while | |
14701 | executable files contain only the program text and initialized data.) | |
c906108c SS |
14702 | |
14703 | When you type @code{run}, your executable file becomes an active process | |
7a292a7a SS |
14704 | target as well. When a process target is active, all @value{GDBN} |
14705 | commands requesting memory addresses refer to that target; addresses in | |
14706 | an active core file or executable file target are obscured while the | |
14707 | process target is active. | |
c906108c | 14708 | |
7a292a7a | 14709 | Use the @code{core-file} and @code{exec-file} commands to select a new |
79a6e687 BW |
14710 | core file or executable target (@pxref{Files, ,Commands to Specify |
14711 | Files}). To specify as a target a process that is already running, use | |
14712 | the @code{attach} command (@pxref{Attach, ,Debugging an Already-running | |
14713 | Process}). | |
c906108c | 14714 | |
6d2ebf8b | 14715 | @node Target Commands |
79a6e687 | 14716 | @section Commands for Managing Targets |
c906108c SS |
14717 | |
14718 | @table @code | |
14719 | @item target @var{type} @var{parameters} | |
7a292a7a SS |
14720 | Connects the @value{GDBN} host environment to a target machine or |
14721 | process. A target is typically a protocol for talking to debugging | |
14722 | facilities. You use the argument @var{type} to specify the type or | |
14723 | protocol of the target machine. | |
c906108c SS |
14724 | |
14725 | Further @var{parameters} are interpreted by the target protocol, but | |
14726 | typically include things like device names or host names to connect | |
14727 | with, process numbers, and baud rates. | |
c906108c SS |
14728 | |
14729 | The @code{target} command does not repeat if you press @key{RET} again | |
14730 | after executing the command. | |
14731 | ||
14732 | @kindex help target | |
14733 | @item help target | |
14734 | Displays the names of all targets available. To display targets | |
14735 | currently selected, use either @code{info target} or @code{info files} | |
79a6e687 | 14736 | (@pxref{Files, ,Commands to Specify Files}). |
c906108c SS |
14737 | |
14738 | @item help target @var{name} | |
14739 | Describe a particular target, including any parameters necessary to | |
14740 | select it. | |
14741 | ||
14742 | @kindex set gnutarget | |
14743 | @item set gnutarget @var{args} | |
5d161b24 | 14744 | @value{GDBN} uses its own library BFD to read your files. @value{GDBN} |
c906108c | 14745 | knows whether it is reading an @dfn{executable}, |
5d161b24 DB |
14746 | a @dfn{core}, or a @dfn{.o} file; however, you can specify the file format |
14747 | with the @code{set gnutarget} command. Unlike most @code{target} commands, | |
c906108c SS |
14748 | with @code{gnutarget} the @code{target} refers to a program, not a machine. |
14749 | ||
d4f3574e | 14750 | @quotation |
c906108c SS |
14751 | @emph{Warning:} To specify a file format with @code{set gnutarget}, |
14752 | you must know the actual BFD name. | |
d4f3574e | 14753 | @end quotation |
c906108c | 14754 | |
d4f3574e | 14755 | @noindent |
79a6e687 | 14756 | @xref{Files, , Commands to Specify Files}. |
c906108c | 14757 | |
5d161b24 | 14758 | @kindex show gnutarget |
c906108c SS |
14759 | @item show gnutarget |
14760 | Use the @code{show gnutarget} command to display what file format | |
14761 | @code{gnutarget} is set to read. If you have not set @code{gnutarget}, | |
14762 | @value{GDBN} will determine the file format for each file automatically, | |
14763 | and @code{show gnutarget} displays @samp{The current BDF target is "auto"}. | |
14764 | @end table | |
14765 | ||
4644b6e3 | 14766 | @cindex common targets |
c906108c SS |
14767 | Here are some common targets (available, or not, depending on the GDB |
14768 | configuration): | |
c906108c SS |
14769 | |
14770 | @table @code | |
4644b6e3 | 14771 | @kindex target |
c906108c | 14772 | @item target exec @var{program} |
4644b6e3 | 14773 | @cindex executable file target |
c906108c SS |
14774 | An executable file. @samp{target exec @var{program}} is the same as |
14775 | @samp{exec-file @var{program}}. | |
14776 | ||
c906108c | 14777 | @item target core @var{filename} |
4644b6e3 | 14778 | @cindex core dump file target |
c906108c SS |
14779 | A core dump file. @samp{target core @var{filename}} is the same as |
14780 | @samp{core-file @var{filename}}. | |
c906108c | 14781 | |
1a10341b | 14782 | @item target remote @var{medium} |
4644b6e3 | 14783 | @cindex remote target |
1a10341b JB |
14784 | A remote system connected to @value{GDBN} via a serial line or network |
14785 | connection. This command tells @value{GDBN} to use its own remote | |
14786 | protocol over @var{medium} for debugging. @xref{Remote Debugging}. | |
14787 | ||
14788 | For example, if you have a board connected to @file{/dev/ttya} on the | |
14789 | machine running @value{GDBN}, you could say: | |
14790 | ||
14791 | @smallexample | |
14792 | target remote /dev/ttya | |
14793 | @end smallexample | |
14794 | ||
14795 | @code{target remote} supports the @code{load} command. This is only | |
14796 | useful if you have some other way of getting the stub to the target | |
14797 | system, and you can put it somewhere in memory where it won't get | |
14798 | clobbered by the download. | |
c906108c | 14799 | |
c906108c | 14800 | @item target sim |
4644b6e3 | 14801 | @cindex built-in simulator target |
2df3850c | 14802 | Builtin CPU simulator. @value{GDBN} includes simulators for most architectures. |
104c1213 | 14803 | In general, |
474c8240 | 14804 | @smallexample |
104c1213 JM |
14805 | target sim |
14806 | load | |
14807 | run | |
474c8240 | 14808 | @end smallexample |
d4f3574e | 14809 | @noindent |
104c1213 | 14810 | works; however, you cannot assume that a specific memory map, device |
d4f3574e | 14811 | drivers, or even basic I/O is available, although some simulators do |
104c1213 JM |
14812 | provide these. For info about any processor-specific simulator details, |
14813 | see the appropriate section in @ref{Embedded Processors, ,Embedded | |
14814 | Processors}. | |
14815 | ||
c906108c SS |
14816 | @end table |
14817 | ||
104c1213 | 14818 | Some configurations may include these targets as well: |
c906108c SS |
14819 | |
14820 | @table @code | |
14821 | ||
c906108c | 14822 | @item target nrom @var{dev} |
4644b6e3 | 14823 | @cindex NetROM ROM emulator target |
c906108c SS |
14824 | NetROM ROM emulator. This target only supports downloading. |
14825 | ||
c906108c SS |
14826 | @end table |
14827 | ||
5d161b24 | 14828 | Different targets are available on different configurations of @value{GDBN}; |
c906108c | 14829 | your configuration may have more or fewer targets. |
c906108c | 14830 | |
721c2651 EZ |
14831 | Many remote targets require you to download the executable's code once |
14832 | you've successfully established a connection. You may wish to control | |
3d00d119 DJ |
14833 | various aspects of this process. |
14834 | ||
14835 | @table @code | |
721c2651 EZ |
14836 | |
14837 | @item set hash | |
14838 | @kindex set hash@r{, for remote monitors} | |
14839 | @cindex hash mark while downloading | |
14840 | This command controls whether a hash mark @samp{#} is displayed while | |
14841 | downloading a file to the remote monitor. If on, a hash mark is | |
14842 | displayed after each S-record is successfully downloaded to the | |
14843 | monitor. | |
14844 | ||
14845 | @item show hash | |
14846 | @kindex show hash@r{, for remote monitors} | |
14847 | Show the current status of displaying the hash mark. | |
14848 | ||
14849 | @item set debug monitor | |
14850 | @kindex set debug monitor | |
14851 | @cindex display remote monitor communications | |
14852 | Enable or disable display of communications messages between | |
14853 | @value{GDBN} and the remote monitor. | |
14854 | ||
14855 | @item show debug monitor | |
14856 | @kindex show debug monitor | |
14857 | Show the current status of displaying communications between | |
14858 | @value{GDBN} and the remote monitor. | |
a8f24a35 | 14859 | @end table |
c906108c SS |
14860 | |
14861 | @table @code | |
14862 | ||
14863 | @kindex load @var{filename} | |
14864 | @item load @var{filename} | |
8edfe269 | 14865 | @anchor{load} |
c906108c SS |
14866 | Depending on what remote debugging facilities are configured into |
14867 | @value{GDBN}, the @code{load} command may be available. Where it exists, it | |
14868 | is meant to make @var{filename} (an executable) available for debugging | |
14869 | on the remote system---by downloading, or dynamic linking, for example. | |
14870 | @code{load} also records the @var{filename} symbol table in @value{GDBN}, like | |
14871 | the @code{add-symbol-file} command. | |
14872 | ||
14873 | If your @value{GDBN} does not have a @code{load} command, attempting to | |
14874 | execute it gets the error message ``@code{You can't do that when your | |
14875 | target is @dots{}}'' | |
c906108c SS |
14876 | |
14877 | The file is loaded at whatever address is specified in the executable. | |
14878 | For some object file formats, you can specify the load address when you | |
14879 | link the program; for other formats, like a.out, the object file format | |
14880 | specifies a fixed address. | |
14881 | @c FIXME! This would be a good place for an xref to the GNU linker doc. | |
14882 | ||
68437a39 DJ |
14883 | Depending on the remote side capabilities, @value{GDBN} may be able to |
14884 | load programs into flash memory. | |
14885 | ||
c906108c SS |
14886 | @code{load} does not repeat if you press @key{RET} again after using it. |
14887 | @end table | |
14888 | ||
6d2ebf8b | 14889 | @node Byte Order |
79a6e687 | 14890 | @section Choosing Target Byte Order |
7a292a7a | 14891 | |
c906108c SS |
14892 | @cindex choosing target byte order |
14893 | @cindex target byte order | |
c906108c | 14894 | |
172c2a43 | 14895 | Some types of processors, such as the MIPS, PowerPC, and Renesas SH, |
c906108c SS |
14896 | offer the ability to run either big-endian or little-endian byte |
14897 | orders. Usually the executable or symbol will include a bit to | |
14898 | designate the endian-ness, and you will not need to worry about | |
14899 | which to use. However, you may still find it useful to adjust | |
d4f3574e | 14900 | @value{GDBN}'s idea of processor endian-ness manually. |
c906108c SS |
14901 | |
14902 | @table @code | |
4644b6e3 | 14903 | @kindex set endian |
c906108c SS |
14904 | @item set endian big |
14905 | Instruct @value{GDBN} to assume the target is big-endian. | |
14906 | ||
c906108c SS |
14907 | @item set endian little |
14908 | Instruct @value{GDBN} to assume the target is little-endian. | |
14909 | ||
c906108c SS |
14910 | @item set endian auto |
14911 | Instruct @value{GDBN} to use the byte order associated with the | |
14912 | executable. | |
14913 | ||
14914 | @item show endian | |
14915 | Display @value{GDBN}'s current idea of the target byte order. | |
14916 | ||
14917 | @end table | |
14918 | ||
14919 | Note that these commands merely adjust interpretation of symbolic | |
14920 | data on the host, and that they have absolutely no effect on the | |
14921 | target system. | |
14922 | ||
ea35711c DJ |
14923 | |
14924 | @node Remote Debugging | |
14925 | @chapter Debugging Remote Programs | |
c906108c SS |
14926 | @cindex remote debugging |
14927 | ||
14928 | If you are trying to debug a program running on a machine that cannot run | |
5d161b24 DB |
14929 | @value{GDBN} in the usual way, it is often useful to use remote debugging. |
14930 | For example, you might use remote debugging on an operating system kernel, | |
c906108c SS |
14931 | or on a small system which does not have a general purpose operating system |
14932 | powerful enough to run a full-featured debugger. | |
14933 | ||
14934 | Some configurations of @value{GDBN} have special serial or TCP/IP interfaces | |
14935 | to make this work with particular debugging targets. In addition, | |
5d161b24 | 14936 | @value{GDBN} comes with a generic serial protocol (specific to @value{GDBN}, |
c906108c SS |
14937 | but not specific to any particular target system) which you can use if you |
14938 | write the remote stubs---the code that runs on the remote system to | |
14939 | communicate with @value{GDBN}. | |
14940 | ||
14941 | Other remote targets may be available in your | |
14942 | configuration of @value{GDBN}; use @code{help target} to list them. | |
c906108c | 14943 | |
6b2f586d | 14944 | @menu |
07f31aa6 | 14945 | * Connecting:: Connecting to a remote target |
a6b151f1 | 14946 | * File Transfer:: Sending files to a remote system |
6b2f586d | 14947 | * Server:: Using the gdbserver program |
79a6e687 BW |
14948 | * Remote Configuration:: Remote configuration |
14949 | * Remote Stub:: Implementing a remote stub | |
6b2f586d AC |
14950 | @end menu |
14951 | ||
07f31aa6 | 14952 | @node Connecting |
79a6e687 | 14953 | @section Connecting to a Remote Target |
07f31aa6 DJ |
14954 | |
14955 | On the @value{GDBN} host machine, you will need an unstripped copy of | |
d3e8051b | 14956 | your program, since @value{GDBN} needs symbol and debugging information. |
07f31aa6 DJ |
14957 | Start up @value{GDBN} as usual, using the name of the local copy of your |
14958 | program as the first argument. | |
14959 | ||
86941c27 JB |
14960 | @cindex @code{target remote} |
14961 | @value{GDBN} can communicate with the target over a serial line, or | |
14962 | over an @acronym{IP} network using @acronym{TCP} or @acronym{UDP}. In | |
14963 | each case, @value{GDBN} uses the same protocol for debugging your | |
14964 | program; only the medium carrying the debugging packets varies. The | |
14965 | @code{target remote} command establishes a connection to the target. | |
14966 | Its arguments indicate which medium to use: | |
14967 | ||
14968 | @table @code | |
14969 | ||
14970 | @item target remote @var{serial-device} | |
07f31aa6 | 14971 | @cindex serial line, @code{target remote} |
86941c27 JB |
14972 | Use @var{serial-device} to communicate with the target. For example, |
14973 | to use a serial line connected to the device named @file{/dev/ttyb}: | |
14974 | ||
14975 | @smallexample | |
14976 | target remote /dev/ttyb | |
14977 | @end smallexample | |
14978 | ||
07f31aa6 DJ |
14979 | If you're using a serial line, you may want to give @value{GDBN} the |
14980 | @w{@samp{--baud}} option, or use the @code{set remotebaud} command | |
79a6e687 | 14981 | (@pxref{Remote Configuration, set remotebaud}) before the |
9c16f35a | 14982 | @code{target} command. |
07f31aa6 | 14983 | |
86941c27 JB |
14984 | @item target remote @code{@var{host}:@var{port}} |
14985 | @itemx target remote @code{tcp:@var{host}:@var{port}} | |
14986 | @cindex @acronym{TCP} port, @code{target remote} | |
14987 | Debug using a @acronym{TCP} connection to @var{port} on @var{host}. | |
14988 | The @var{host} may be either a host name or a numeric @acronym{IP} | |
14989 | address; @var{port} must be a decimal number. The @var{host} could be | |
14990 | the target machine itself, if it is directly connected to the net, or | |
14991 | it might be a terminal server which in turn has a serial line to the | |
14992 | target. | |
07f31aa6 | 14993 | |
86941c27 JB |
14994 | For example, to connect to port 2828 on a terminal server named |
14995 | @code{manyfarms}: | |
07f31aa6 DJ |
14996 | |
14997 | @smallexample | |
14998 | target remote manyfarms:2828 | |
14999 | @end smallexample | |
15000 | ||
86941c27 JB |
15001 | If your remote target is actually running on the same machine as your |
15002 | debugger session (e.g.@: a simulator for your target running on the | |
15003 | same host), you can omit the hostname. For example, to connect to | |
15004 | port 1234 on your local machine: | |
07f31aa6 DJ |
15005 | |
15006 | @smallexample | |
15007 | target remote :1234 | |
15008 | @end smallexample | |
15009 | @noindent | |
15010 | ||
15011 | Note that the colon is still required here. | |
15012 | ||
86941c27 JB |
15013 | @item target remote @code{udp:@var{host}:@var{port}} |
15014 | @cindex @acronym{UDP} port, @code{target remote} | |
15015 | Debug using @acronym{UDP} packets to @var{port} on @var{host}. For example, to | |
15016 | connect to @acronym{UDP} port 2828 on a terminal server named @code{manyfarms}: | |
07f31aa6 DJ |
15017 | |
15018 | @smallexample | |
15019 | target remote udp:manyfarms:2828 | |
15020 | @end smallexample | |
15021 | ||
86941c27 JB |
15022 | When using a @acronym{UDP} connection for remote debugging, you should |
15023 | keep in mind that the `U' stands for ``Unreliable''. @acronym{UDP} | |
15024 | can silently drop packets on busy or unreliable networks, which will | |
15025 | cause havoc with your debugging session. | |
15026 | ||
66b8c7f6 JB |
15027 | @item target remote | @var{command} |
15028 | @cindex pipe, @code{target remote} to | |
15029 | Run @var{command} in the background and communicate with it using a | |
15030 | pipe. The @var{command} is a shell command, to be parsed and expanded | |
15031 | by the system's command shell, @code{/bin/sh}; it should expect remote | |
15032 | protocol packets on its standard input, and send replies on its | |
15033 | standard output. You could use this to run a stand-alone simulator | |
15034 | that speaks the remote debugging protocol, to make net connections | |
15035 | using programs like @code{ssh}, or for other similar tricks. | |
15036 | ||
15037 | If @var{command} closes its standard output (perhaps by exiting), | |
15038 | @value{GDBN} will try to send it a @code{SIGTERM} signal. (If the | |
15039 | program has already exited, this will have no effect.) | |
15040 | ||
86941c27 | 15041 | @end table |
07f31aa6 | 15042 | |
86941c27 | 15043 | Once the connection has been established, you can use all the usual |
8edfe269 DJ |
15044 | commands to examine and change data. The remote program is already |
15045 | running; you can use @kbd{step} and @kbd{continue}, and you do not | |
15046 | need to use @kbd{run}. | |
07f31aa6 DJ |
15047 | |
15048 | @cindex interrupting remote programs | |
15049 | @cindex remote programs, interrupting | |
15050 | Whenever @value{GDBN} is waiting for the remote program, if you type the | |
c8aa23ab | 15051 | interrupt character (often @kbd{Ctrl-c}), @value{GDBN} attempts to stop the |
07f31aa6 DJ |
15052 | program. This may or may not succeed, depending in part on the hardware |
15053 | and the serial drivers the remote system uses. If you type the | |
15054 | interrupt character once again, @value{GDBN} displays this prompt: | |
15055 | ||
15056 | @smallexample | |
15057 | Interrupted while waiting for the program. | |
15058 | Give up (and stop debugging it)? (y or n) | |
15059 | @end smallexample | |
15060 | ||
15061 | If you type @kbd{y}, @value{GDBN} abandons the remote debugging session. | |
15062 | (If you decide you want to try again later, you can use @samp{target | |
15063 | remote} again to connect once more.) If you type @kbd{n}, @value{GDBN} | |
15064 | goes back to waiting. | |
15065 | ||
15066 | @table @code | |
15067 | @kindex detach (remote) | |
15068 | @item detach | |
15069 | When you have finished debugging the remote program, you can use the | |
15070 | @code{detach} command to release it from @value{GDBN} control. | |
15071 | Detaching from the target normally resumes its execution, but the results | |
15072 | will depend on your particular remote stub. After the @code{detach} | |
15073 | command, @value{GDBN} is free to connect to another target. | |
15074 | ||
15075 | @kindex disconnect | |
15076 | @item disconnect | |
15077 | The @code{disconnect} command behaves like @code{detach}, except that | |
15078 | the target is generally not resumed. It will wait for @value{GDBN} | |
15079 | (this instance or another one) to connect and continue debugging. After | |
15080 | the @code{disconnect} command, @value{GDBN} is again free to connect to | |
15081 | another target. | |
09d4efe1 EZ |
15082 | |
15083 | @cindex send command to remote monitor | |
fad38dfa EZ |
15084 | @cindex extend @value{GDBN} for remote targets |
15085 | @cindex add new commands for external monitor | |
09d4efe1 EZ |
15086 | @kindex monitor |
15087 | @item monitor @var{cmd} | |
fad38dfa EZ |
15088 | This command allows you to send arbitrary commands directly to the |
15089 | remote monitor. Since @value{GDBN} doesn't care about the commands it | |
15090 | sends like this, this command is the way to extend @value{GDBN}---you | |
15091 | can add new commands that only the external monitor will understand | |
15092 | and implement. | |
07f31aa6 DJ |
15093 | @end table |
15094 | ||
a6b151f1 DJ |
15095 | @node File Transfer |
15096 | @section Sending files to a remote system | |
15097 | @cindex remote target, file transfer | |
15098 | @cindex file transfer | |
15099 | @cindex sending files to remote systems | |
15100 | ||
15101 | Some remote targets offer the ability to transfer files over the same | |
15102 | connection used to communicate with @value{GDBN}. This is convenient | |
15103 | for targets accessible through other means, e.g.@: @sc{gnu}/Linux systems | |
15104 | running @code{gdbserver} over a network interface. For other targets, | |
15105 | e.g.@: embedded devices with only a single serial port, this may be | |
15106 | the only way to upload or download files. | |
15107 | ||
15108 | Not all remote targets support these commands. | |
15109 | ||
15110 | @table @code | |
15111 | @kindex remote put | |
15112 | @item remote put @var{hostfile} @var{targetfile} | |
15113 | Copy file @var{hostfile} from the host system (the machine running | |
15114 | @value{GDBN}) to @var{targetfile} on the target system. | |
15115 | ||
15116 | @kindex remote get | |
15117 | @item remote get @var{targetfile} @var{hostfile} | |
15118 | Copy file @var{targetfile} from the target system to @var{hostfile} | |
15119 | on the host system. | |
15120 | ||
15121 | @kindex remote delete | |
15122 | @item remote delete @var{targetfile} | |
15123 | Delete @var{targetfile} from the target system. | |
15124 | ||
15125 | @end table | |
15126 | ||
6f05cf9f | 15127 | @node Server |
79a6e687 | 15128 | @section Using the @code{gdbserver} Program |
6f05cf9f AC |
15129 | |
15130 | @kindex gdbserver | |
15131 | @cindex remote connection without stubs | |
15132 | @code{gdbserver} is a control program for Unix-like systems, which | |
15133 | allows you to connect your program with a remote @value{GDBN} via | |
15134 | @code{target remote}---but without linking in the usual debugging stub. | |
15135 | ||
15136 | @code{gdbserver} is not a complete replacement for the debugging stubs, | |
15137 | because it requires essentially the same operating-system facilities | |
15138 | that @value{GDBN} itself does. In fact, a system that can run | |
15139 | @code{gdbserver} to connect to a remote @value{GDBN} could also run | |
15140 | @value{GDBN} locally! @code{gdbserver} is sometimes useful nevertheless, | |
15141 | because it is a much smaller program than @value{GDBN} itself. It is | |
15142 | also easier to port than all of @value{GDBN}, so you may be able to get | |
15143 | started more quickly on a new system by using @code{gdbserver}. | |
15144 | Finally, if you develop code for real-time systems, you may find that | |
15145 | the tradeoffs involved in real-time operation make it more convenient to | |
15146 | do as much development work as possible on another system, for example | |
15147 | by cross-compiling. You can use @code{gdbserver} to make a similar | |
15148 | choice for debugging. | |
15149 | ||
15150 | @value{GDBN} and @code{gdbserver} communicate via either a serial line | |
15151 | or a TCP connection, using the standard @value{GDBN} remote serial | |
15152 | protocol. | |
15153 | ||
2d717e4f DJ |
15154 | @quotation |
15155 | @emph{Warning:} @code{gdbserver} does not have any built-in security. | |
15156 | Do not run @code{gdbserver} connected to any public network; a | |
15157 | @value{GDBN} connection to @code{gdbserver} provides access to the | |
15158 | target system with the same privileges as the user running | |
15159 | @code{gdbserver}. | |
15160 | @end quotation | |
15161 | ||
15162 | @subsection Running @code{gdbserver} | |
15163 | @cindex arguments, to @code{gdbserver} | |
15164 | ||
15165 | Run @code{gdbserver} on the target system. You need a copy of the | |
15166 | program you want to debug, including any libraries it requires. | |
6f05cf9f AC |
15167 | @code{gdbserver} does not need your program's symbol table, so you can |
15168 | strip the program if necessary to save space. @value{GDBN} on the host | |
15169 | system does all the symbol handling. | |
15170 | ||
15171 | To use the server, you must tell it how to communicate with @value{GDBN}; | |
56460a61 | 15172 | the name of your program; and the arguments for your program. The usual |
6f05cf9f AC |
15173 | syntax is: |
15174 | ||
15175 | @smallexample | |
15176 | target> gdbserver @var{comm} @var{program} [ @var{args} @dots{} ] | |
15177 | @end smallexample | |
15178 | ||
15179 | @var{comm} is either a device name (to use a serial line) or a TCP | |
15180 | hostname and portnumber. For example, to debug Emacs with the argument | |
15181 | @samp{foo.txt} and communicate with @value{GDBN} over the serial port | |
15182 | @file{/dev/com1}: | |
15183 | ||
15184 | @smallexample | |
15185 | target> gdbserver /dev/com1 emacs foo.txt | |
15186 | @end smallexample | |
15187 | ||
15188 | @code{gdbserver} waits passively for the host @value{GDBN} to communicate | |
15189 | with it. | |
15190 | ||
15191 | To use a TCP connection instead of a serial line: | |
15192 | ||
15193 | @smallexample | |
15194 | target> gdbserver host:2345 emacs foo.txt | |
15195 | @end smallexample | |
15196 | ||
15197 | The only difference from the previous example is the first argument, | |
15198 | specifying that you are communicating with the host @value{GDBN} via | |
15199 | TCP. The @samp{host:2345} argument means that @code{gdbserver} is to | |
15200 | expect a TCP connection from machine @samp{host} to local TCP port 2345. | |
15201 | (Currently, the @samp{host} part is ignored.) You can choose any number | |
15202 | you want for the port number as long as it does not conflict with any | |
15203 | TCP ports already in use on the target system (for example, @code{23} is | |
15204 | reserved for @code{telnet}).@footnote{If you choose a port number that | |
15205 | conflicts with another service, @code{gdbserver} prints an error message | |
15206 | and exits.} You must use the same port number with the host @value{GDBN} | |
15207 | @code{target remote} command. | |
15208 | ||
2d717e4f DJ |
15209 | @subsubsection Attaching to a Running Program |
15210 | ||
56460a61 DJ |
15211 | On some targets, @code{gdbserver} can also attach to running programs. |
15212 | This is accomplished via the @code{--attach} argument. The syntax is: | |
15213 | ||
15214 | @smallexample | |
2d717e4f | 15215 | target> gdbserver --attach @var{comm} @var{pid} |
56460a61 DJ |
15216 | @end smallexample |
15217 | ||
15218 | @var{pid} is the process ID of a currently running process. It isn't necessary | |
15219 | to point @code{gdbserver} at a binary for the running process. | |
15220 | ||
b1fe9455 DJ |
15221 | @pindex pidof |
15222 | @cindex attach to a program by name | |
15223 | You can debug processes by name instead of process ID if your target has the | |
15224 | @code{pidof} utility: | |
15225 | ||
15226 | @smallexample | |
2d717e4f | 15227 | target> gdbserver --attach @var{comm} `pidof @var{program}` |
b1fe9455 DJ |
15228 | @end smallexample |
15229 | ||
f822c95b | 15230 | In case more than one copy of @var{program} is running, or @var{program} |
b1fe9455 DJ |
15231 | has multiple threads, most versions of @code{pidof} support the |
15232 | @code{-s} option to only return the first process ID. | |
15233 | ||
2d717e4f DJ |
15234 | @subsubsection Multi-Process Mode for @code{gdbserver} |
15235 | @cindex gdbserver, multiple processes | |
15236 | @cindex multiple processes with gdbserver | |
15237 | ||
15238 | When you connect to @code{gdbserver} using @code{target remote}, | |
15239 | @code{gdbserver} debugs the specified program only once. When the | |
15240 | program exits, or you detach from it, @value{GDBN} closes the connection | |
15241 | and @code{gdbserver} exits. | |
15242 | ||
6e6c6f50 | 15243 | If you connect using @kbd{target extended-remote}, @code{gdbserver} |
2d717e4f DJ |
15244 | enters multi-process mode. When the debugged program exits, or you |
15245 | detach from it, @value{GDBN} stays connected to @code{gdbserver} even | |
15246 | though no program is running. The @code{run} and @code{attach} | |
15247 | commands instruct @code{gdbserver} to run or attach to a new program. | |
15248 | The @code{run} command uses @code{set remote exec-file} (@pxref{set | |
15249 | remote exec-file}) to select the program to run. Command line | |
15250 | arguments are supported, except for wildcard expansion and I/O | |
15251 | redirection (@pxref{Arguments}). | |
15252 | ||
15253 | To start @code{gdbserver} without supplying an initial command to run | |
15254 | or process ID to attach, use the @option{--multi} command line option. | |
6e6c6f50 | 15255 | Then you can connect using @kbd{target extended-remote} and start |
2d717e4f DJ |
15256 | the program you want to debug. |
15257 | ||
15258 | @code{gdbserver} does not automatically exit in multi-process mode. | |
15259 | You can terminate it by using @code{monitor exit} | |
15260 | (@pxref{Monitor Commands for gdbserver}). | |
15261 | ||
15262 | @subsubsection Other Command-Line Arguments for @code{gdbserver} | |
15263 | ||
62709adf PA |
15264 | The @option{--debug} option tells @code{gdbserver} to display extra |
15265 | status information about the debugging process. The | |
15266 | @option{--remote-debug} option tells @code{gdbserver} to display | |
15267 | remote protocol debug output. These options are intended for | |
15268 | @code{gdbserver} development and for bug reports to the developers. | |
2d717e4f | 15269 | |
ccd213ac DJ |
15270 | The @option{--wrapper} option specifies a wrapper to launch programs |
15271 | for debugging. The option should be followed by the name of the | |
15272 | wrapper, then any command-line arguments to pass to the wrapper, then | |
15273 | @kbd{--} indicating the end of the wrapper arguments. | |
15274 | ||
15275 | @code{gdbserver} runs the specified wrapper program with a combined | |
15276 | command line including the wrapper arguments, then the name of the | |
15277 | program to debug, then any arguments to the program. The wrapper | |
15278 | runs until it executes your program, and then @value{GDBN} gains control. | |
15279 | ||
15280 | You can use any program that eventually calls @code{execve} with | |
15281 | its arguments as a wrapper. Several standard Unix utilities do | |
15282 | this, e.g.@: @code{env} and @code{nohup}. Any Unix shell script ending | |
15283 | with @code{exec "$@@"} will also work. | |
15284 | ||
15285 | For example, you can use @code{env} to pass an environment variable to | |
15286 | the debugged program, without setting the variable in @code{gdbserver}'s | |
15287 | environment: | |
15288 | ||
15289 | @smallexample | |
15290 | $ gdbserver --wrapper env LD_PRELOAD=libtest.so -- :2222 ./testprog | |
15291 | @end smallexample | |
15292 | ||
2d717e4f DJ |
15293 | @subsection Connecting to @code{gdbserver} |
15294 | ||
15295 | Run @value{GDBN} on the host system. | |
15296 | ||
15297 | First make sure you have the necessary symbol files. Load symbols for | |
f822c95b DJ |
15298 | your application using the @code{file} command before you connect. Use |
15299 | @code{set sysroot} to locate target libraries (unless your @value{GDBN} | |
2d717e4f | 15300 | was compiled with the correct sysroot using @code{--with-sysroot}). |
f822c95b DJ |
15301 | |
15302 | The symbol file and target libraries must exactly match the executable | |
15303 | and libraries on the target, with one exception: the files on the host | |
15304 | system should not be stripped, even if the files on the target system | |
15305 | are. Mismatched or missing files will lead to confusing results | |
15306 | during debugging. On @sc{gnu}/Linux targets, mismatched or missing | |
15307 | files may also prevent @code{gdbserver} from debugging multi-threaded | |
15308 | programs. | |
15309 | ||
79a6e687 | 15310 | Connect to your target (@pxref{Connecting,,Connecting to a Remote Target}). |
6f05cf9f AC |
15311 | For TCP connections, you must start up @code{gdbserver} prior to using |
15312 | the @code{target remote} command. Otherwise you may get an error whose | |
15313 | text depends on the host system, but which usually looks something like | |
2d717e4f | 15314 | @samp{Connection refused}. Don't use the @code{load} |
397ca115 | 15315 | command in @value{GDBN} when using @code{gdbserver}, since the program is |
f822c95b | 15316 | already on the target. |
07f31aa6 | 15317 | |
79a6e687 | 15318 | @subsection Monitor Commands for @code{gdbserver} |
c74d0ad8 | 15319 | @cindex monitor commands, for @code{gdbserver} |
2d717e4f | 15320 | @anchor{Monitor Commands for gdbserver} |
c74d0ad8 DJ |
15321 | |
15322 | During a @value{GDBN} session using @code{gdbserver}, you can use the | |
15323 | @code{monitor} command to send special requests to @code{gdbserver}. | |
2d717e4f | 15324 | Here are the available commands. |
c74d0ad8 DJ |
15325 | |
15326 | @table @code | |
15327 | @item monitor help | |
15328 | List the available monitor commands. | |
15329 | ||
15330 | @item monitor set debug 0 | |
15331 | @itemx monitor set debug 1 | |
15332 | Disable or enable general debugging messages. | |
15333 | ||
15334 | @item monitor set remote-debug 0 | |
15335 | @itemx monitor set remote-debug 1 | |
15336 | Disable or enable specific debugging messages associated with the remote | |
15337 | protocol (@pxref{Remote Protocol}). | |
15338 | ||
cdbfd419 PP |
15339 | @item monitor set libthread-db-search-path [PATH] |
15340 | @cindex gdbserver, search path for @code{libthread_db} | |
15341 | When this command is issued, @var{path} is a colon-separated list of | |
15342 | directories to search for @code{libthread_db} (@pxref{Threads,,set | |
15343 | libthread-db-search-path}). If you omit @var{path}, | |
15344 | @samp{libthread-db-search-path} will be reset to an empty list. | |
15345 | ||
2d717e4f DJ |
15346 | @item monitor exit |
15347 | Tell gdbserver to exit immediately. This command should be followed by | |
15348 | @code{disconnect} to close the debugging session. @code{gdbserver} will | |
15349 | detach from any attached processes and kill any processes it created. | |
15350 | Use @code{monitor exit} to terminate @code{gdbserver} at the end | |
15351 | of a multi-process mode debug session. | |
15352 | ||
c74d0ad8 DJ |
15353 | @end table |
15354 | ||
79a6e687 BW |
15355 | @node Remote Configuration |
15356 | @section Remote Configuration | |
501eef12 | 15357 | |
9c16f35a EZ |
15358 | @kindex set remote |
15359 | @kindex show remote | |
15360 | This section documents the configuration options available when | |
15361 | debugging remote programs. For the options related to the File I/O | |
fc320d37 | 15362 | extensions of the remote protocol, see @ref{system, |
9c16f35a | 15363 | system-call-allowed}. |
501eef12 AC |
15364 | |
15365 | @table @code | |
9c16f35a | 15366 | @item set remoteaddresssize @var{bits} |
d3e8051b | 15367 | @cindex address size for remote targets |
9c16f35a EZ |
15368 | @cindex bits in remote address |
15369 | Set the maximum size of address in a memory packet to the specified | |
15370 | number of bits. @value{GDBN} will mask off the address bits above | |
15371 | that number, when it passes addresses to the remote target. The | |
15372 | default value is the number of bits in the target's address. | |
15373 | ||
15374 | @item show remoteaddresssize | |
15375 | Show the current value of remote address size in bits. | |
15376 | ||
15377 | @item set remotebaud @var{n} | |
15378 | @cindex baud rate for remote targets | |
15379 | Set the baud rate for the remote serial I/O to @var{n} baud. The | |
15380 | value is used to set the speed of the serial port used for debugging | |
15381 | remote targets. | |
15382 | ||
15383 | @item show remotebaud | |
15384 | Show the current speed of the remote connection. | |
15385 | ||
15386 | @item set remotebreak | |
15387 | @cindex interrupt remote programs | |
15388 | @cindex BREAK signal instead of Ctrl-C | |
9a6253be | 15389 | @anchor{set remotebreak} |
9c16f35a | 15390 | If set to on, @value{GDBN} sends a @code{BREAK} signal to the remote |
c8aa23ab | 15391 | when you type @kbd{Ctrl-c} to interrupt the program running |
9a7a1b36 | 15392 | on the remote. If set to off, @value{GDBN} sends the @samp{Ctrl-C} |
9c16f35a EZ |
15393 | character instead. The default is off, since most remote systems |
15394 | expect to see @samp{Ctrl-C} as the interrupt signal. | |
15395 | ||
15396 | @item show remotebreak | |
15397 | Show whether @value{GDBN} sends @code{BREAK} or @samp{Ctrl-C} to | |
15398 | interrupt the remote program. | |
15399 | ||
23776285 MR |
15400 | @item set remoteflow on |
15401 | @itemx set remoteflow off | |
15402 | @kindex set remoteflow | |
15403 | Enable or disable hardware flow control (@code{RTS}/@code{CTS}) | |
15404 | on the serial port used to communicate to the remote target. | |
15405 | ||
15406 | @item show remoteflow | |
15407 | @kindex show remoteflow | |
15408 | Show the current setting of hardware flow control. | |
15409 | ||
9c16f35a EZ |
15410 | @item set remotelogbase @var{base} |
15411 | Set the base (a.k.a.@: radix) of logging serial protocol | |
15412 | communications to @var{base}. Supported values of @var{base} are: | |
15413 | @code{ascii}, @code{octal}, and @code{hex}. The default is | |
15414 | @code{ascii}. | |
15415 | ||
15416 | @item show remotelogbase | |
15417 | Show the current setting of the radix for logging remote serial | |
15418 | protocol. | |
15419 | ||
15420 | @item set remotelogfile @var{file} | |
15421 | @cindex record serial communications on file | |
15422 | Record remote serial communications on the named @var{file}. The | |
15423 | default is not to record at all. | |
15424 | ||
15425 | @item show remotelogfile. | |
15426 | Show the current setting of the file name on which to record the | |
15427 | serial communications. | |
15428 | ||
15429 | @item set remotetimeout @var{num} | |
15430 | @cindex timeout for serial communications | |
15431 | @cindex remote timeout | |
15432 | Set the timeout limit to wait for the remote target to respond to | |
15433 | @var{num} seconds. The default is 2 seconds. | |
15434 | ||
15435 | @item show remotetimeout | |
15436 | Show the current number of seconds to wait for the remote target | |
15437 | responses. | |
15438 | ||
15439 | @cindex limit hardware breakpoints and watchpoints | |
15440 | @cindex remote target, limit break- and watchpoints | |
501eef12 AC |
15441 | @anchor{set remote hardware-watchpoint-limit} |
15442 | @anchor{set remote hardware-breakpoint-limit} | |
15443 | @item set remote hardware-watchpoint-limit @var{limit} | |
15444 | @itemx set remote hardware-breakpoint-limit @var{limit} | |
15445 | Restrict @value{GDBN} to using @var{limit} remote hardware breakpoint or | |
15446 | watchpoints. A limit of -1, the default, is treated as unlimited. | |
2d717e4f DJ |
15447 | |
15448 | @item set remote exec-file @var{filename} | |
15449 | @itemx show remote exec-file | |
15450 | @anchor{set remote exec-file} | |
15451 | @cindex executable file, for remote target | |
15452 | Select the file used for @code{run} with @code{target | |
15453 | extended-remote}. This should be set to a filename valid on the | |
15454 | target system. If it is not set, the target will use a default | |
15455 | filename (e.g.@: the last program run). | |
84603566 | 15456 | |
9a7071a8 JB |
15457 | @item set remote interrupt-sequence |
15458 | @cindex interrupt remote programs | |
15459 | @cindex select Ctrl-C, BREAK or BREAK-g | |
15460 | Allow the user to select one of @samp{Ctrl-C}, a @code{BREAK} or | |
15461 | @samp{BREAK-g} as the | |
15462 | sequence to the remote target in order to interrupt the execution. | |
15463 | @samp{Ctrl-C} is a default. Some system prefers @code{BREAK} which | |
15464 | is high level of serial line for some certain time. | |
15465 | Linux kernel prefers @samp{BREAK-g}, a.k.a Magic SysRq g. | |
15466 | It is @code{BREAK} signal followed by character @code{g}. | |
15467 | ||
15468 | @item show interrupt-sequence | |
15469 | Show which of @samp{Ctrl-C}, @code{BREAK} or @code{BREAK-g} | |
15470 | is sent by @value{GDBN} to interrupt the remote program. | |
15471 | @code{BREAK-g} is BREAK signal followed by @code{g} and | |
15472 | also known as Magic SysRq g. | |
15473 | ||
15474 | @item set remote interrupt-on-connect | |
15475 | @cindex send interrupt-sequence on start | |
15476 | Specify whether interrupt-sequence is sent to remote target when | |
15477 | @value{GDBN} connects to it. This is mostly needed when you debug | |
15478 | Linux kernel. Linux kernel expects @code{BREAK} followed by @code{g} | |
15479 | which is known as Magic SysRq g in order to connect @value{GDBN}. | |
15480 | ||
15481 | @item show interrupt-on-connect | |
15482 | Show whether interrupt-sequence is sent | |
15483 | to remote target when @value{GDBN} connects to it. | |
15484 | ||
84603566 SL |
15485 | @kindex set tcp |
15486 | @kindex show tcp | |
15487 | @item set tcp auto-retry on | |
15488 | @cindex auto-retry, for remote TCP target | |
15489 | Enable auto-retry for remote TCP connections. This is useful if the remote | |
15490 | debugging agent is launched in parallel with @value{GDBN}; there is a race | |
15491 | condition because the agent may not become ready to accept the connection | |
15492 | before @value{GDBN} attempts to connect. When auto-retry is | |
15493 | enabled, if the initial attempt to connect fails, @value{GDBN} reattempts | |
15494 | to establish the connection using the timeout specified by | |
15495 | @code{set tcp connect-timeout}. | |
15496 | ||
15497 | @item set tcp auto-retry off | |
15498 | Do not auto-retry failed TCP connections. | |
15499 | ||
15500 | @item show tcp auto-retry | |
15501 | Show the current auto-retry setting. | |
15502 | ||
15503 | @item set tcp connect-timeout @var{seconds} | |
15504 | @cindex connection timeout, for remote TCP target | |
15505 | @cindex timeout, for remote target connection | |
15506 | Set the timeout for establishing a TCP connection to the remote target to | |
15507 | @var{seconds}. The timeout affects both polling to retry failed connections | |
15508 | (enabled by @code{set tcp auto-retry on}) and waiting for connections | |
15509 | that are merely slow to complete, and represents an approximate cumulative | |
15510 | value. | |
15511 | ||
15512 | @item show tcp connect-timeout | |
15513 | Show the current connection timeout setting. | |
501eef12 AC |
15514 | @end table |
15515 | ||
427c3a89 DJ |
15516 | @cindex remote packets, enabling and disabling |
15517 | The @value{GDBN} remote protocol autodetects the packets supported by | |
15518 | your debugging stub. If you need to override the autodetection, you | |
15519 | can use these commands to enable or disable individual packets. Each | |
15520 | packet can be set to @samp{on} (the remote target supports this | |
15521 | packet), @samp{off} (the remote target does not support this packet), | |
15522 | or @samp{auto} (detect remote target support for this packet). They | |
15523 | all default to @samp{auto}. For more information about each packet, | |
15524 | see @ref{Remote Protocol}. | |
15525 | ||
15526 | During normal use, you should not have to use any of these commands. | |
15527 | If you do, that may be a bug in your remote debugging stub, or a bug | |
15528 | in @value{GDBN}. You may want to report the problem to the | |
15529 | @value{GDBN} developers. | |
15530 | ||
cfa9d6d9 DJ |
15531 | For each packet @var{name}, the command to enable or disable the |
15532 | packet is @code{set remote @var{name}-packet}. The available settings | |
15533 | are: | |
427c3a89 | 15534 | |
cfa9d6d9 | 15535 | @multitable @columnfractions 0.28 0.32 0.25 |
427c3a89 DJ |
15536 | @item Command Name |
15537 | @tab Remote Packet | |
15538 | @tab Related Features | |
15539 | ||
cfa9d6d9 | 15540 | @item @code{fetch-register} |
427c3a89 DJ |
15541 | @tab @code{p} |
15542 | @tab @code{info registers} | |
15543 | ||
cfa9d6d9 | 15544 | @item @code{set-register} |
427c3a89 DJ |
15545 | @tab @code{P} |
15546 | @tab @code{set} | |
15547 | ||
cfa9d6d9 | 15548 | @item @code{binary-download} |
427c3a89 DJ |
15549 | @tab @code{X} |
15550 | @tab @code{load}, @code{set} | |
15551 | ||
cfa9d6d9 | 15552 | @item @code{read-aux-vector} |
427c3a89 DJ |
15553 | @tab @code{qXfer:auxv:read} |
15554 | @tab @code{info auxv} | |
15555 | ||
cfa9d6d9 | 15556 | @item @code{symbol-lookup} |
427c3a89 DJ |
15557 | @tab @code{qSymbol} |
15558 | @tab Detecting multiple threads | |
15559 | ||
2d717e4f DJ |
15560 | @item @code{attach} |
15561 | @tab @code{vAttach} | |
15562 | @tab @code{attach} | |
15563 | ||
cfa9d6d9 | 15564 | @item @code{verbose-resume} |
427c3a89 DJ |
15565 | @tab @code{vCont} |
15566 | @tab Stepping or resuming multiple threads | |
15567 | ||
2d717e4f DJ |
15568 | @item @code{run} |
15569 | @tab @code{vRun} | |
15570 | @tab @code{run} | |
15571 | ||
cfa9d6d9 | 15572 | @item @code{software-breakpoint} |
427c3a89 DJ |
15573 | @tab @code{Z0} |
15574 | @tab @code{break} | |
15575 | ||
cfa9d6d9 | 15576 | @item @code{hardware-breakpoint} |
427c3a89 DJ |
15577 | @tab @code{Z1} |
15578 | @tab @code{hbreak} | |
15579 | ||
cfa9d6d9 | 15580 | @item @code{write-watchpoint} |
427c3a89 DJ |
15581 | @tab @code{Z2} |
15582 | @tab @code{watch} | |
15583 | ||
cfa9d6d9 | 15584 | @item @code{read-watchpoint} |
427c3a89 DJ |
15585 | @tab @code{Z3} |
15586 | @tab @code{rwatch} | |
15587 | ||
cfa9d6d9 | 15588 | @item @code{access-watchpoint} |
427c3a89 DJ |
15589 | @tab @code{Z4} |
15590 | @tab @code{awatch} | |
15591 | ||
cfa9d6d9 DJ |
15592 | @item @code{target-features} |
15593 | @tab @code{qXfer:features:read} | |
15594 | @tab @code{set architecture} | |
15595 | ||
15596 | @item @code{library-info} | |
15597 | @tab @code{qXfer:libraries:read} | |
15598 | @tab @code{info sharedlibrary} | |
15599 | ||
15600 | @item @code{memory-map} | |
15601 | @tab @code{qXfer:memory-map:read} | |
15602 | @tab @code{info mem} | |
15603 | ||
15604 | @item @code{read-spu-object} | |
15605 | @tab @code{qXfer:spu:read} | |
15606 | @tab @code{info spu} | |
15607 | ||
15608 | @item @code{write-spu-object} | |
15609 | @tab @code{qXfer:spu:write} | |
15610 | @tab @code{info spu} | |
15611 | ||
4aa995e1 PA |
15612 | @item @code{read-siginfo-object} |
15613 | @tab @code{qXfer:siginfo:read} | |
15614 | @tab @code{print $_siginfo} | |
15615 | ||
15616 | @item @code{write-siginfo-object} | |
15617 | @tab @code{qXfer:siginfo:write} | |
15618 | @tab @code{set $_siginfo} | |
15619 | ||
dc146f7c VP |
15620 | @item @code{threads} |
15621 | @tab @code{qXfer:threads:read} | |
15622 | @tab @code{info threads} | |
15623 | ||
cfa9d6d9 | 15624 | @item @code{get-thread-local-@*storage-address} |
427c3a89 DJ |
15625 | @tab @code{qGetTLSAddr} |
15626 | @tab Displaying @code{__thread} variables | |
15627 | ||
08388c79 DE |
15628 | @item @code{search-memory} |
15629 | @tab @code{qSearch:memory} | |
15630 | @tab @code{find} | |
15631 | ||
427c3a89 DJ |
15632 | @item @code{supported-packets} |
15633 | @tab @code{qSupported} | |
15634 | @tab Remote communications parameters | |
15635 | ||
cfa9d6d9 | 15636 | @item @code{pass-signals} |
89be2091 DJ |
15637 | @tab @code{QPassSignals} |
15638 | @tab @code{handle @var{signal}} | |
15639 | ||
a6b151f1 DJ |
15640 | @item @code{hostio-close-packet} |
15641 | @tab @code{vFile:close} | |
15642 | @tab @code{remote get}, @code{remote put} | |
15643 | ||
15644 | @item @code{hostio-open-packet} | |
15645 | @tab @code{vFile:open} | |
15646 | @tab @code{remote get}, @code{remote put} | |
15647 | ||
15648 | @item @code{hostio-pread-packet} | |
15649 | @tab @code{vFile:pread} | |
15650 | @tab @code{remote get}, @code{remote put} | |
15651 | ||
15652 | @item @code{hostio-pwrite-packet} | |
15653 | @tab @code{vFile:pwrite} | |
15654 | @tab @code{remote get}, @code{remote put} | |
15655 | ||
15656 | @item @code{hostio-unlink-packet} | |
15657 | @tab @code{vFile:unlink} | |
15658 | @tab @code{remote delete} | |
a6f3e723 SL |
15659 | |
15660 | @item @code{noack-packet} | |
15661 | @tab @code{QStartNoAckMode} | |
15662 | @tab Packet acknowledgment | |
07e059b5 VP |
15663 | |
15664 | @item @code{osdata} | |
15665 | @tab @code{qXfer:osdata:read} | |
15666 | @tab @code{info os} | |
0b16c5cf PA |
15667 | |
15668 | @item @code{query-attached} | |
15669 | @tab @code{qAttached} | |
15670 | @tab Querying remote process attach state. | |
427c3a89 DJ |
15671 | @end multitable |
15672 | ||
79a6e687 BW |
15673 | @node Remote Stub |
15674 | @section Implementing a Remote Stub | |
7a292a7a | 15675 | |
8e04817f AC |
15676 | @cindex debugging stub, example |
15677 | @cindex remote stub, example | |
15678 | @cindex stub example, remote debugging | |
15679 | The stub files provided with @value{GDBN} implement the target side of the | |
15680 | communication protocol, and the @value{GDBN} side is implemented in the | |
15681 | @value{GDBN} source file @file{remote.c}. Normally, you can simply allow | |
15682 | these subroutines to communicate, and ignore the details. (If you're | |
15683 | implementing your own stub file, you can still ignore the details: start | |
15684 | with one of the existing stub files. @file{sparc-stub.c} is the best | |
15685 | organized, and therefore the easiest to read.) | |
15686 | ||
104c1213 JM |
15687 | @cindex remote serial debugging, overview |
15688 | To debug a program running on another machine (the debugging | |
15689 | @dfn{target} machine), you must first arrange for all the usual | |
15690 | prerequisites for the program to run by itself. For example, for a C | |
15691 | program, you need: | |
c906108c | 15692 | |
104c1213 JM |
15693 | @enumerate |
15694 | @item | |
15695 | A startup routine to set up the C runtime environment; these usually | |
15696 | have a name like @file{crt0}. The startup routine may be supplied by | |
15697 | your hardware supplier, or you may have to write your own. | |
96baa820 | 15698 | |
5d161b24 | 15699 | @item |
d4f3574e | 15700 | A C subroutine library to support your program's |
104c1213 | 15701 | subroutine calls, notably managing input and output. |
96baa820 | 15702 | |
104c1213 JM |
15703 | @item |
15704 | A way of getting your program to the other machine---for example, a | |
15705 | download program. These are often supplied by the hardware | |
15706 | manufacturer, but you may have to write your own from hardware | |
15707 | documentation. | |
15708 | @end enumerate | |
96baa820 | 15709 | |
104c1213 JM |
15710 | The next step is to arrange for your program to use a serial port to |
15711 | communicate with the machine where @value{GDBN} is running (the @dfn{host} | |
15712 | machine). In general terms, the scheme looks like this: | |
96baa820 | 15713 | |
104c1213 JM |
15714 | @table @emph |
15715 | @item On the host, | |
15716 | @value{GDBN} already understands how to use this protocol; when everything | |
15717 | else is set up, you can simply use the @samp{target remote} command | |
15718 | (@pxref{Targets,,Specifying a Debugging Target}). | |
15719 | ||
15720 | @item On the target, | |
15721 | you must link with your program a few special-purpose subroutines that | |
15722 | implement the @value{GDBN} remote serial protocol. The file containing these | |
15723 | subroutines is called a @dfn{debugging stub}. | |
15724 | ||
15725 | On certain remote targets, you can use an auxiliary program | |
15726 | @code{gdbserver} instead of linking a stub into your program. | |
79a6e687 | 15727 | @xref{Server,,Using the @code{gdbserver} Program}, for details. |
104c1213 | 15728 | @end table |
96baa820 | 15729 | |
104c1213 JM |
15730 | The debugging stub is specific to the architecture of the remote |
15731 | machine; for example, use @file{sparc-stub.c} to debug programs on | |
15732 | @sc{sparc} boards. | |
96baa820 | 15733 | |
104c1213 JM |
15734 | @cindex remote serial stub list |
15735 | These working remote stubs are distributed with @value{GDBN}: | |
96baa820 | 15736 | |
104c1213 JM |
15737 | @table @code |
15738 | ||
15739 | @item i386-stub.c | |
41afff9a | 15740 | @cindex @file{i386-stub.c} |
104c1213 JM |
15741 | @cindex Intel |
15742 | @cindex i386 | |
15743 | For Intel 386 and compatible architectures. | |
15744 | ||
15745 | @item m68k-stub.c | |
41afff9a | 15746 | @cindex @file{m68k-stub.c} |
104c1213 JM |
15747 | @cindex Motorola 680x0 |
15748 | @cindex m680x0 | |
15749 | For Motorola 680x0 architectures. | |
15750 | ||
15751 | @item sh-stub.c | |
41afff9a | 15752 | @cindex @file{sh-stub.c} |
172c2a43 | 15753 | @cindex Renesas |
104c1213 | 15754 | @cindex SH |
172c2a43 | 15755 | For Renesas SH architectures. |
104c1213 JM |
15756 | |
15757 | @item sparc-stub.c | |
41afff9a | 15758 | @cindex @file{sparc-stub.c} |
104c1213 JM |
15759 | @cindex Sparc |
15760 | For @sc{sparc} architectures. | |
15761 | ||
15762 | @item sparcl-stub.c | |
41afff9a | 15763 | @cindex @file{sparcl-stub.c} |
104c1213 JM |
15764 | @cindex Fujitsu |
15765 | @cindex SparcLite | |
15766 | For Fujitsu @sc{sparclite} architectures. | |
15767 | ||
15768 | @end table | |
15769 | ||
15770 | The @file{README} file in the @value{GDBN} distribution may list other | |
15771 | recently added stubs. | |
15772 | ||
15773 | @menu | |
15774 | * Stub Contents:: What the stub can do for you | |
15775 | * Bootstrapping:: What you must do for the stub | |
15776 | * Debug Session:: Putting it all together | |
104c1213 JM |
15777 | @end menu |
15778 | ||
6d2ebf8b | 15779 | @node Stub Contents |
79a6e687 | 15780 | @subsection What the Stub Can Do for You |
104c1213 JM |
15781 | |
15782 | @cindex remote serial stub | |
15783 | The debugging stub for your architecture supplies these three | |
15784 | subroutines: | |
15785 | ||
15786 | @table @code | |
15787 | @item set_debug_traps | |
4644b6e3 | 15788 | @findex set_debug_traps |
104c1213 JM |
15789 | @cindex remote serial stub, initialization |
15790 | This routine arranges for @code{handle_exception} to run when your | |
15791 | program stops. You must call this subroutine explicitly near the | |
15792 | beginning of your program. | |
15793 | ||
15794 | @item handle_exception | |
4644b6e3 | 15795 | @findex handle_exception |
104c1213 JM |
15796 | @cindex remote serial stub, main routine |
15797 | This is the central workhorse, but your program never calls it | |
15798 | explicitly---the setup code arranges for @code{handle_exception} to | |
15799 | run when a trap is triggered. | |
15800 | ||
15801 | @code{handle_exception} takes control when your program stops during | |
15802 | execution (for example, on a breakpoint), and mediates communications | |
15803 | with @value{GDBN} on the host machine. This is where the communications | |
15804 | protocol is implemented; @code{handle_exception} acts as the @value{GDBN} | |
d4f3574e | 15805 | representative on the target machine. It begins by sending summary |
104c1213 JM |
15806 | information on the state of your program, then continues to execute, |
15807 | retrieving and transmitting any information @value{GDBN} needs, until you | |
15808 | execute a @value{GDBN} command that makes your program resume; at that point, | |
15809 | @code{handle_exception} returns control to your own code on the target | |
5d161b24 | 15810 | machine. |
104c1213 JM |
15811 | |
15812 | @item breakpoint | |
15813 | @cindex @code{breakpoint} subroutine, remote | |
15814 | Use this auxiliary subroutine to make your program contain a | |
15815 | breakpoint. Depending on the particular situation, this may be the only | |
15816 | way for @value{GDBN} to get control. For instance, if your target | |
15817 | machine has some sort of interrupt button, you won't need to call this; | |
15818 | pressing the interrupt button transfers control to | |
15819 | @code{handle_exception}---in effect, to @value{GDBN}. On some machines, | |
15820 | simply receiving characters on the serial port may also trigger a trap; | |
15821 | again, in that situation, you don't need to call @code{breakpoint} from | |
15822 | your own program---simply running @samp{target remote} from the host | |
5d161b24 | 15823 | @value{GDBN} session gets control. |
104c1213 JM |
15824 | |
15825 | Call @code{breakpoint} if none of these is true, or if you simply want | |
15826 | to make certain your program stops at a predetermined point for the | |
15827 | start of your debugging session. | |
15828 | @end table | |
15829 | ||
6d2ebf8b | 15830 | @node Bootstrapping |
79a6e687 | 15831 | @subsection What You Must Do for the Stub |
104c1213 JM |
15832 | |
15833 | @cindex remote stub, support routines | |
15834 | The debugging stubs that come with @value{GDBN} are set up for a particular | |
15835 | chip architecture, but they have no information about the rest of your | |
15836 | debugging target machine. | |
15837 | ||
15838 | First of all you need to tell the stub how to communicate with the | |
15839 | serial port. | |
15840 | ||
15841 | @table @code | |
15842 | @item int getDebugChar() | |
4644b6e3 | 15843 | @findex getDebugChar |
104c1213 JM |
15844 | Write this subroutine to read a single character from the serial port. |
15845 | It may be identical to @code{getchar} for your target system; a | |
15846 | different name is used to allow you to distinguish the two if you wish. | |
15847 | ||
15848 | @item void putDebugChar(int) | |
4644b6e3 | 15849 | @findex putDebugChar |
104c1213 | 15850 | Write this subroutine to write a single character to the serial port. |
5d161b24 | 15851 | It may be identical to @code{putchar} for your target system; a |
104c1213 JM |
15852 | different name is used to allow you to distinguish the two if you wish. |
15853 | @end table | |
15854 | ||
15855 | @cindex control C, and remote debugging | |
15856 | @cindex interrupting remote targets | |
15857 | If you want @value{GDBN} to be able to stop your program while it is | |
15858 | running, you need to use an interrupt-driven serial driver, and arrange | |
15859 | for it to stop when it receives a @code{^C} (@samp{\003}, the control-C | |
15860 | character). That is the character which @value{GDBN} uses to tell the | |
15861 | remote system to stop. | |
15862 | ||
15863 | Getting the debugging target to return the proper status to @value{GDBN} | |
15864 | probably requires changes to the standard stub; one quick and dirty way | |
15865 | is to just execute a breakpoint instruction (the ``dirty'' part is that | |
15866 | @value{GDBN} reports a @code{SIGTRAP} instead of a @code{SIGINT}). | |
15867 | ||
15868 | Other routines you need to supply are: | |
15869 | ||
15870 | @table @code | |
15871 | @item void exceptionHandler (int @var{exception_number}, void *@var{exception_address}) | |
4644b6e3 | 15872 | @findex exceptionHandler |
104c1213 JM |
15873 | Write this function to install @var{exception_address} in the exception |
15874 | handling tables. You need to do this because the stub does not have any | |
15875 | way of knowing what the exception handling tables on your target system | |
15876 | are like (for example, the processor's table might be in @sc{rom}, | |
15877 | containing entries which point to a table in @sc{ram}). | |
15878 | @var{exception_number} is the exception number which should be changed; | |
15879 | its meaning is architecture-dependent (for example, different numbers | |
15880 | might represent divide by zero, misaligned access, etc). When this | |
15881 | exception occurs, control should be transferred directly to | |
15882 | @var{exception_address}, and the processor state (stack, registers, | |
15883 | and so on) should be just as it is when a processor exception occurs. So if | |
15884 | you want to use a jump instruction to reach @var{exception_address}, it | |
15885 | should be a simple jump, not a jump to subroutine. | |
15886 | ||
15887 | For the 386, @var{exception_address} should be installed as an interrupt | |
15888 | gate so that interrupts are masked while the handler runs. The gate | |
15889 | should be at privilege level 0 (the most privileged level). The | |
15890 | @sc{sparc} and 68k stubs are able to mask interrupts themselves without | |
15891 | help from @code{exceptionHandler}. | |
15892 | ||
15893 | @item void flush_i_cache() | |
4644b6e3 | 15894 | @findex flush_i_cache |
d4f3574e | 15895 | On @sc{sparc} and @sc{sparclite} only, write this subroutine to flush the |
104c1213 JM |
15896 | instruction cache, if any, on your target machine. If there is no |
15897 | instruction cache, this subroutine may be a no-op. | |
15898 | ||
15899 | On target machines that have instruction caches, @value{GDBN} requires this | |
15900 | function to make certain that the state of your program is stable. | |
15901 | @end table | |
15902 | ||
15903 | @noindent | |
15904 | You must also make sure this library routine is available: | |
15905 | ||
15906 | @table @code | |
15907 | @item void *memset(void *, int, int) | |
4644b6e3 | 15908 | @findex memset |
104c1213 JM |
15909 | This is the standard library function @code{memset} that sets an area of |
15910 | memory to a known value. If you have one of the free versions of | |
15911 | @code{libc.a}, @code{memset} can be found there; otherwise, you must | |
15912 | either obtain it from your hardware manufacturer, or write your own. | |
15913 | @end table | |
15914 | ||
15915 | If you do not use the GNU C compiler, you may need other standard | |
15916 | library subroutines as well; this varies from one stub to another, | |
15917 | but in general the stubs are likely to use any of the common library | |
e22ea452 | 15918 | subroutines which @code{@value{NGCC}} generates as inline code. |
104c1213 JM |
15919 | |
15920 | ||
6d2ebf8b | 15921 | @node Debug Session |
79a6e687 | 15922 | @subsection Putting it All Together |
104c1213 JM |
15923 | |
15924 | @cindex remote serial debugging summary | |
15925 | In summary, when your program is ready to debug, you must follow these | |
15926 | steps. | |
15927 | ||
15928 | @enumerate | |
15929 | @item | |
6d2ebf8b | 15930 | Make sure you have defined the supporting low-level routines |
79a6e687 | 15931 | (@pxref{Bootstrapping,,What You Must Do for the Stub}): |
104c1213 JM |
15932 | @display |
15933 | @code{getDebugChar}, @code{putDebugChar}, | |
15934 | @code{flush_i_cache}, @code{memset}, @code{exceptionHandler}. | |
15935 | @end display | |
15936 | ||
15937 | @item | |
15938 | Insert these lines near the top of your program: | |
15939 | ||
474c8240 | 15940 | @smallexample |
104c1213 JM |
15941 | set_debug_traps(); |
15942 | breakpoint(); | |
474c8240 | 15943 | @end smallexample |
104c1213 JM |
15944 | |
15945 | @item | |
15946 | For the 680x0 stub only, you need to provide a variable called | |
15947 | @code{exceptionHook}. Normally you just use: | |
15948 | ||
474c8240 | 15949 | @smallexample |
104c1213 | 15950 | void (*exceptionHook)() = 0; |
474c8240 | 15951 | @end smallexample |
104c1213 | 15952 | |
d4f3574e | 15953 | @noindent |
104c1213 | 15954 | but if before calling @code{set_debug_traps}, you set it to point to a |
598ca718 | 15955 | function in your program, that function is called when |
104c1213 JM |
15956 | @code{@value{GDBN}} continues after stopping on a trap (for example, bus |
15957 | error). The function indicated by @code{exceptionHook} is called with | |
15958 | one parameter: an @code{int} which is the exception number. | |
15959 | ||
15960 | @item | |
15961 | Compile and link together: your program, the @value{GDBN} debugging stub for | |
15962 | your target architecture, and the supporting subroutines. | |
15963 | ||
15964 | @item | |
15965 | Make sure you have a serial connection between your target machine and | |
15966 | the @value{GDBN} host, and identify the serial port on the host. | |
15967 | ||
15968 | @item | |
15969 | @c The "remote" target now provides a `load' command, so we should | |
15970 | @c document that. FIXME. | |
15971 | Download your program to your target machine (or get it there by | |
15972 | whatever means the manufacturer provides), and start it. | |
15973 | ||
15974 | @item | |
07f31aa6 | 15975 | Start @value{GDBN} on the host, and connect to the target |
79a6e687 | 15976 | (@pxref{Connecting,,Connecting to a Remote Target}). |
9db8d71f | 15977 | |
104c1213 JM |
15978 | @end enumerate |
15979 | ||
8e04817f AC |
15980 | @node Configurations |
15981 | @chapter Configuration-Specific Information | |
104c1213 | 15982 | |
8e04817f AC |
15983 | While nearly all @value{GDBN} commands are available for all native and |
15984 | cross versions of the debugger, there are some exceptions. This chapter | |
15985 | describes things that are only available in certain configurations. | |
104c1213 | 15986 | |
8e04817f AC |
15987 | There are three major categories of configurations: native |
15988 | configurations, where the host and target are the same, embedded | |
15989 | operating system configurations, which are usually the same for several | |
15990 | different processor architectures, and bare embedded processors, which | |
15991 | are quite different from each other. | |
104c1213 | 15992 | |
8e04817f AC |
15993 | @menu |
15994 | * Native:: | |
15995 | * Embedded OS:: | |
15996 | * Embedded Processors:: | |
15997 | * Architectures:: | |
15998 | @end menu | |
104c1213 | 15999 | |
8e04817f AC |
16000 | @node Native |
16001 | @section Native | |
104c1213 | 16002 | |
8e04817f AC |
16003 | This section describes details specific to particular native |
16004 | configurations. | |
6cf7e474 | 16005 | |
8e04817f AC |
16006 | @menu |
16007 | * HP-UX:: HP-UX | |
7561d450 | 16008 | * BSD libkvm Interface:: Debugging BSD kernel memory images |
8e04817f AC |
16009 | * SVR4 Process Information:: SVR4 process information |
16010 | * DJGPP Native:: Features specific to the DJGPP port | |
78c47bea | 16011 | * Cygwin Native:: Features specific to the Cygwin port |
14d6dd68 | 16012 | * Hurd Native:: Features specific to @sc{gnu} Hurd |
a64548ea | 16013 | * Neutrino:: Features specific to QNX Neutrino |
a80b95ba | 16014 | * Darwin:: Features specific to Darwin |
8e04817f | 16015 | @end menu |
6cf7e474 | 16016 | |
8e04817f AC |
16017 | @node HP-UX |
16018 | @subsection HP-UX | |
104c1213 | 16019 | |
8e04817f AC |
16020 | On HP-UX systems, if you refer to a function or variable name that |
16021 | begins with a dollar sign, @value{GDBN} searches for a user or system | |
16022 | name first, before it searches for a convenience variable. | |
104c1213 | 16023 | |
9c16f35a | 16024 | |
7561d450 MK |
16025 | @node BSD libkvm Interface |
16026 | @subsection BSD libkvm Interface | |
16027 | ||
16028 | @cindex libkvm | |
16029 | @cindex kernel memory image | |
16030 | @cindex kernel crash dump | |
16031 | ||
16032 | BSD-derived systems (FreeBSD/NetBSD/OpenBSD) have a kernel memory | |
16033 | interface that provides a uniform interface for accessing kernel virtual | |
16034 | memory images, including live systems and crash dumps. @value{GDBN} | |
16035 | uses this interface to allow you to debug live kernels and kernel crash | |
16036 | dumps on many native BSD configurations. This is implemented as a | |
16037 | special @code{kvm} debugging target. For debugging a live system, load | |
16038 | the currently running kernel into @value{GDBN} and connect to the | |
16039 | @code{kvm} target: | |
16040 | ||
16041 | @smallexample | |
16042 | (@value{GDBP}) @b{target kvm} | |
16043 | @end smallexample | |
16044 | ||
16045 | For debugging crash dumps, provide the file name of the crash dump as an | |
16046 | argument: | |
16047 | ||
16048 | @smallexample | |
16049 | (@value{GDBP}) @b{target kvm /var/crash/bsd.0} | |
16050 | @end smallexample | |
16051 | ||
16052 | Once connected to the @code{kvm} target, the following commands are | |
16053 | available: | |
16054 | ||
16055 | @table @code | |
16056 | @kindex kvm | |
16057 | @item kvm pcb | |
721c2651 | 16058 | Set current context from the @dfn{Process Control Block} (PCB) address. |
7561d450 MK |
16059 | |
16060 | @item kvm proc | |
16061 | Set current context from proc address. This command isn't available on | |
16062 | modern FreeBSD systems. | |
16063 | @end table | |
16064 | ||
8e04817f | 16065 | @node SVR4 Process Information |
79a6e687 | 16066 | @subsection SVR4 Process Information |
60bf7e09 EZ |
16067 | @cindex /proc |
16068 | @cindex examine process image | |
16069 | @cindex process info via @file{/proc} | |
104c1213 | 16070 | |
60bf7e09 EZ |
16071 | Many versions of SVR4 and compatible systems provide a facility called |
16072 | @samp{/proc} that can be used to examine the image of a running | |
16073 | process using file-system subroutines. If @value{GDBN} is configured | |
16074 | for an operating system with this facility, the command @code{info | |
16075 | proc} is available to report information about the process running | |
16076 | your program, or about any process running on your system. @code{info | |
16077 | proc} works only on SVR4 systems that include the @code{procfs} code. | |
16078 | This includes, as of this writing, @sc{gnu}/Linux, OSF/1 (Digital | |
16079 | Unix), Solaris, Irix, and Unixware, but not HP-UX, for example. | |
104c1213 | 16080 | |
8e04817f AC |
16081 | @table @code |
16082 | @kindex info proc | |
60bf7e09 | 16083 | @cindex process ID |
8e04817f | 16084 | @item info proc |
60bf7e09 EZ |
16085 | @itemx info proc @var{process-id} |
16086 | Summarize available information about any running process. If a | |
16087 | process ID is specified by @var{process-id}, display information about | |
16088 | that process; otherwise display information about the program being | |
16089 | debugged. The summary includes the debugged process ID, the command | |
16090 | line used to invoke it, its current working directory, and its | |
16091 | executable file's absolute file name. | |
16092 | ||
16093 | On some systems, @var{process-id} can be of the form | |
16094 | @samp{[@var{pid}]/@var{tid}} which specifies a certain thread ID | |
16095 | within a process. If the optional @var{pid} part is missing, it means | |
16096 | a thread from the process being debugged (the leading @samp{/} still | |
16097 | needs to be present, or else @value{GDBN} will interpret the number as | |
16098 | a process ID rather than a thread ID). | |
6cf7e474 | 16099 | |
8e04817f | 16100 | @item info proc mappings |
60bf7e09 EZ |
16101 | @cindex memory address space mappings |
16102 | Report the memory address space ranges accessible in the program, with | |
16103 | information on whether the process has read, write, or execute access | |
16104 | rights to each range. On @sc{gnu}/Linux systems, each memory range | |
16105 | includes the object file which is mapped to that range, instead of the | |
16106 | memory access rights to that range. | |
16107 | ||
16108 | @item info proc stat | |
16109 | @itemx info proc status | |
16110 | @cindex process detailed status information | |
16111 | These subcommands are specific to @sc{gnu}/Linux systems. They show | |
16112 | the process-related information, including the user ID and group ID; | |
16113 | how many threads are there in the process; its virtual memory usage; | |
16114 | the signals that are pending, blocked, and ignored; its TTY; its | |
16115 | consumption of system and user time; its stack size; its @samp{nice} | |
2eecc4ab | 16116 | value; etc. For more information, see the @samp{proc} man page |
60bf7e09 EZ |
16117 | (type @kbd{man 5 proc} from your shell prompt). |
16118 | ||
16119 | @item info proc all | |
16120 | Show all the information about the process described under all of the | |
16121 | above @code{info proc} subcommands. | |
16122 | ||
8e04817f AC |
16123 | @ignore |
16124 | @comment These sub-options of 'info proc' were not included when | |
16125 | @comment procfs.c was re-written. Keep their descriptions around | |
16126 | @comment against the day when someone finds the time to put them back in. | |
16127 | @kindex info proc times | |
16128 | @item info proc times | |
16129 | Starting time, user CPU time, and system CPU time for your program and | |
16130 | its children. | |
6cf7e474 | 16131 | |
8e04817f AC |
16132 | @kindex info proc id |
16133 | @item info proc id | |
16134 | Report on the process IDs related to your program: its own process ID, | |
16135 | the ID of its parent, the process group ID, and the session ID. | |
8e04817f | 16136 | @end ignore |
721c2651 EZ |
16137 | |
16138 | @item set procfs-trace | |
16139 | @kindex set procfs-trace | |
16140 | @cindex @code{procfs} API calls | |
16141 | This command enables and disables tracing of @code{procfs} API calls. | |
16142 | ||
16143 | @item show procfs-trace | |
16144 | @kindex show procfs-trace | |
16145 | Show the current state of @code{procfs} API call tracing. | |
16146 | ||
16147 | @item set procfs-file @var{file} | |
16148 | @kindex set procfs-file | |
16149 | Tell @value{GDBN} to write @code{procfs} API trace to the named | |
16150 | @var{file}. @value{GDBN} appends the trace info to the previous | |
16151 | contents of the file. The default is to display the trace on the | |
16152 | standard output. | |
16153 | ||
16154 | @item show procfs-file | |
16155 | @kindex show procfs-file | |
16156 | Show the file to which @code{procfs} API trace is written. | |
16157 | ||
16158 | @item proc-trace-entry | |
16159 | @itemx proc-trace-exit | |
16160 | @itemx proc-untrace-entry | |
16161 | @itemx proc-untrace-exit | |
16162 | @kindex proc-trace-entry | |
16163 | @kindex proc-trace-exit | |
16164 | @kindex proc-untrace-entry | |
16165 | @kindex proc-untrace-exit | |
16166 | These commands enable and disable tracing of entries into and exits | |
16167 | from the @code{syscall} interface. | |
16168 | ||
16169 | @item info pidlist | |
16170 | @kindex info pidlist | |
16171 | @cindex process list, QNX Neutrino | |
16172 | For QNX Neutrino only, this command displays the list of all the | |
16173 | processes and all the threads within each process. | |
16174 | ||
16175 | @item info meminfo | |
16176 | @kindex info meminfo | |
16177 | @cindex mapinfo list, QNX Neutrino | |
16178 | For QNX Neutrino only, this command displays the list of all mapinfos. | |
8e04817f | 16179 | @end table |
104c1213 | 16180 | |
8e04817f AC |
16181 | @node DJGPP Native |
16182 | @subsection Features for Debugging @sc{djgpp} Programs | |
16183 | @cindex @sc{djgpp} debugging | |
16184 | @cindex native @sc{djgpp} debugging | |
16185 | @cindex MS-DOS-specific commands | |
104c1213 | 16186 | |
514c4d71 EZ |
16187 | @cindex DPMI |
16188 | @sc{djgpp} is a port of the @sc{gnu} development tools to MS-DOS and | |
8e04817f AC |
16189 | MS-Windows. @sc{djgpp} programs are 32-bit protected-mode programs |
16190 | that use the @dfn{DPMI} (DOS Protected-Mode Interface) API to run on | |
16191 | top of real-mode DOS systems and their emulations. | |
104c1213 | 16192 | |
8e04817f AC |
16193 | @value{GDBN} supports native debugging of @sc{djgpp} programs, and |
16194 | defines a few commands specific to the @sc{djgpp} port. This | |
16195 | subsection describes those commands. | |
104c1213 | 16196 | |
8e04817f AC |
16197 | @table @code |
16198 | @kindex info dos | |
16199 | @item info dos | |
16200 | This is a prefix of @sc{djgpp}-specific commands which print | |
16201 | information about the target system and important OS structures. | |
f1251bdd | 16202 | |
8e04817f AC |
16203 | @kindex sysinfo |
16204 | @cindex MS-DOS system info | |
16205 | @cindex free memory information (MS-DOS) | |
16206 | @item info dos sysinfo | |
16207 | This command displays assorted information about the underlying | |
16208 | platform: the CPU type and features, the OS version and flavor, the | |
16209 | DPMI version, and the available conventional and DPMI memory. | |
104c1213 | 16210 | |
8e04817f AC |
16211 | @cindex GDT |
16212 | @cindex LDT | |
16213 | @cindex IDT | |
16214 | @cindex segment descriptor tables | |
16215 | @cindex descriptor tables display | |
16216 | @item info dos gdt | |
16217 | @itemx info dos ldt | |
16218 | @itemx info dos idt | |
16219 | These 3 commands display entries from, respectively, Global, Local, | |
16220 | and Interrupt Descriptor Tables (GDT, LDT, and IDT). The descriptor | |
16221 | tables are data structures which store a descriptor for each segment | |
16222 | that is currently in use. The segment's selector is an index into a | |
16223 | descriptor table; the table entry for that index holds the | |
16224 | descriptor's base address and limit, and its attributes and access | |
16225 | rights. | |
104c1213 | 16226 | |
8e04817f AC |
16227 | A typical @sc{djgpp} program uses 3 segments: a code segment, a data |
16228 | segment (used for both data and the stack), and a DOS segment (which | |
16229 | allows access to DOS/BIOS data structures and absolute addresses in | |
16230 | conventional memory). However, the DPMI host will usually define | |
16231 | additional segments in order to support the DPMI environment. | |
d4f3574e | 16232 | |
8e04817f AC |
16233 | @cindex garbled pointers |
16234 | These commands allow to display entries from the descriptor tables. | |
16235 | Without an argument, all entries from the specified table are | |
16236 | displayed. An argument, which should be an integer expression, means | |
16237 | display a single entry whose index is given by the argument. For | |
16238 | example, here's a convenient way to display information about the | |
16239 | debugged program's data segment: | |
104c1213 | 16240 | |
8e04817f AC |
16241 | @smallexample |
16242 | @exdent @code{(@value{GDBP}) info dos ldt $ds} | |
16243 | @exdent @code{0x13f: base=0x11970000 limit=0x0009ffff 32-Bit Data (Read/Write, Exp-up)} | |
16244 | @end smallexample | |
104c1213 | 16245 | |
8e04817f AC |
16246 | @noindent |
16247 | This comes in handy when you want to see whether a pointer is outside | |
16248 | the data segment's limit (i.e.@: @dfn{garbled}). | |
104c1213 | 16249 | |
8e04817f AC |
16250 | @cindex page tables display (MS-DOS) |
16251 | @item info dos pde | |
16252 | @itemx info dos pte | |
16253 | These two commands display entries from, respectively, the Page | |
16254 | Directory and the Page Tables. Page Directories and Page Tables are | |
16255 | data structures which control how virtual memory addresses are mapped | |
16256 | into physical addresses. A Page Table includes an entry for every | |
16257 | page of memory that is mapped into the program's address space; there | |
16258 | may be several Page Tables, each one holding up to 4096 entries. A | |
16259 | Page Directory has up to 4096 entries, one each for every Page Table | |
16260 | that is currently in use. | |
104c1213 | 16261 | |
8e04817f AC |
16262 | Without an argument, @kbd{info dos pde} displays the entire Page |
16263 | Directory, and @kbd{info dos pte} displays all the entries in all of | |
16264 | the Page Tables. An argument, an integer expression, given to the | |
16265 | @kbd{info dos pde} command means display only that entry from the Page | |
16266 | Directory table. An argument given to the @kbd{info dos pte} command | |
16267 | means display entries from a single Page Table, the one pointed to by | |
16268 | the specified entry in the Page Directory. | |
104c1213 | 16269 | |
8e04817f AC |
16270 | @cindex direct memory access (DMA) on MS-DOS |
16271 | These commands are useful when your program uses @dfn{DMA} (Direct | |
16272 | Memory Access), which needs physical addresses to program the DMA | |
16273 | controller. | |
104c1213 | 16274 | |
8e04817f | 16275 | These commands are supported only with some DPMI servers. |
104c1213 | 16276 | |
8e04817f AC |
16277 | @cindex physical address from linear address |
16278 | @item info dos address-pte @var{addr} | |
16279 | This command displays the Page Table entry for a specified linear | |
514c4d71 EZ |
16280 | address. The argument @var{addr} is a linear address which should |
16281 | already have the appropriate segment's base address added to it, | |
16282 | because this command accepts addresses which may belong to @emph{any} | |
16283 | segment. For example, here's how to display the Page Table entry for | |
16284 | the page where a variable @code{i} is stored: | |
104c1213 | 16285 | |
b383017d | 16286 | @smallexample |
8e04817f AC |
16287 | @exdent @code{(@value{GDBP}) info dos address-pte __djgpp_base_address + (char *)&i} |
16288 | @exdent @code{Page Table entry for address 0x11a00d30:} | |
b383017d | 16289 | @exdent @code{Base=0x02698000 Dirty Acc. Not-Cached Write-Back Usr Read-Write +0xd30} |
8e04817f | 16290 | @end smallexample |
104c1213 | 16291 | |
8e04817f AC |
16292 | @noindent |
16293 | This says that @code{i} is stored at offset @code{0xd30} from the page | |
514c4d71 | 16294 | whose physical base address is @code{0x02698000}, and shows all the |
8e04817f | 16295 | attributes of that page. |
104c1213 | 16296 | |
8e04817f AC |
16297 | Note that you must cast the addresses of variables to a @code{char *}, |
16298 | since otherwise the value of @code{__djgpp_base_address}, the base | |
16299 | address of all variables and functions in a @sc{djgpp} program, will | |
16300 | be added using the rules of C pointer arithmetics: if @code{i} is | |
16301 | declared an @code{int}, @value{GDBN} will add 4 times the value of | |
16302 | @code{__djgpp_base_address} to the address of @code{i}. | |
104c1213 | 16303 | |
8e04817f AC |
16304 | Here's another example, it displays the Page Table entry for the |
16305 | transfer buffer: | |
104c1213 | 16306 | |
8e04817f AC |
16307 | @smallexample |
16308 | @exdent @code{(@value{GDBP}) info dos address-pte *((unsigned *)&_go32_info_block + 3)} | |
16309 | @exdent @code{Page Table entry for address 0x29110:} | |
16310 | @exdent @code{Base=0x00029000 Dirty Acc. Not-Cached Write-Back Usr Read-Write +0x110} | |
16311 | @end smallexample | |
104c1213 | 16312 | |
8e04817f AC |
16313 | @noindent |
16314 | (The @code{+ 3} offset is because the transfer buffer's address is the | |
514c4d71 EZ |
16315 | 3rd member of the @code{_go32_info_block} structure.) The output |
16316 | clearly shows that this DPMI server maps the addresses in conventional | |
16317 | memory 1:1, i.e.@: the physical (@code{0x00029000} + @code{0x110}) and | |
16318 | linear (@code{0x29110}) addresses are identical. | |
104c1213 | 16319 | |
8e04817f AC |
16320 | This command is supported only with some DPMI servers. |
16321 | @end table | |
104c1213 | 16322 | |
c45da7e6 | 16323 | @cindex DOS serial data link, remote debugging |
a8f24a35 EZ |
16324 | In addition to native debugging, the DJGPP port supports remote |
16325 | debugging via a serial data link. The following commands are specific | |
16326 | to remote serial debugging in the DJGPP port of @value{GDBN}. | |
16327 | ||
16328 | @table @code | |
16329 | @kindex set com1base | |
16330 | @kindex set com1irq | |
16331 | @kindex set com2base | |
16332 | @kindex set com2irq | |
16333 | @kindex set com3base | |
16334 | @kindex set com3irq | |
16335 | @kindex set com4base | |
16336 | @kindex set com4irq | |
16337 | @item set com1base @var{addr} | |
16338 | This command sets the base I/O port address of the @file{COM1} serial | |
16339 | port. | |
16340 | ||
16341 | @item set com1irq @var{irq} | |
16342 | This command sets the @dfn{Interrupt Request} (@code{IRQ}) line to use | |
16343 | for the @file{COM1} serial port. | |
16344 | ||
16345 | There are similar commands @samp{set com2base}, @samp{set com3irq}, | |
16346 | etc.@: for setting the port address and the @code{IRQ} lines for the | |
16347 | other 3 COM ports. | |
16348 | ||
16349 | @kindex show com1base | |
16350 | @kindex show com1irq | |
16351 | @kindex show com2base | |
16352 | @kindex show com2irq | |
16353 | @kindex show com3base | |
16354 | @kindex show com3irq | |
16355 | @kindex show com4base | |
16356 | @kindex show com4irq | |
16357 | The related commands @samp{show com1base}, @samp{show com1irq} etc.@: | |
16358 | display the current settings of the base address and the @code{IRQ} | |
16359 | lines used by the COM ports. | |
c45da7e6 EZ |
16360 | |
16361 | @item info serial | |
16362 | @kindex info serial | |
16363 | @cindex DOS serial port status | |
16364 | This command prints the status of the 4 DOS serial ports. For each | |
16365 | port, it prints whether it's active or not, its I/O base address and | |
16366 | IRQ number, whether it uses a 16550-style FIFO, its baudrate, and the | |
16367 | counts of various errors encountered so far. | |
a8f24a35 EZ |
16368 | @end table |
16369 | ||
16370 | ||
78c47bea | 16371 | @node Cygwin Native |
79a6e687 | 16372 | @subsection Features for Debugging MS Windows PE Executables |
78c47bea PM |
16373 | @cindex MS Windows debugging |
16374 | @cindex native Cygwin debugging | |
16375 | @cindex Cygwin-specific commands | |
16376 | ||
be448670 | 16377 | @value{GDBN} supports native debugging of MS Windows programs, including |
cbb8f428 EZ |
16378 | DLLs with and without symbolic debugging information. |
16379 | ||
16380 | @cindex Ctrl-BREAK, MS-Windows | |
16381 | @cindex interrupt debuggee on MS-Windows | |
16382 | MS-Windows programs that call @code{SetConsoleMode} to switch off the | |
16383 | special meaning of the @samp{Ctrl-C} keystroke cannot be interrupted | |
16384 | by typing @kbd{C-c}. For this reason, @value{GDBN} on MS-Windows | |
16385 | supports @kbd{C-@key{BREAK}} as an alternative interrupt key | |
16386 | sequence, which can be used to interrupt the debuggee even if it | |
16387 | ignores @kbd{C-c}. | |
16388 | ||
16389 | There are various additional Cygwin-specific commands, described in | |
16390 | this section. Working with DLLs that have no debugging symbols is | |
16391 | described in @ref{Non-debug DLL Symbols}. | |
78c47bea PM |
16392 | |
16393 | @table @code | |
16394 | @kindex info w32 | |
16395 | @item info w32 | |
db2e3e2e | 16396 | This is a prefix of MS Windows-specific commands which print |
78c47bea PM |
16397 | information about the target system and important OS structures. |
16398 | ||
16399 | @item info w32 selector | |
16400 | This command displays information returned by | |
16401 | the Win32 API @code{GetThreadSelectorEntry} function. | |
16402 | It takes an optional argument that is evaluated to | |
16403 | a long value to give the information about this given selector. | |
16404 | Without argument, this command displays information | |
d3e8051b | 16405 | about the six segment registers. |
78c47bea PM |
16406 | |
16407 | @kindex info dll | |
16408 | @item info dll | |
db2e3e2e | 16409 | This is a Cygwin-specific alias of @code{info shared}. |
78c47bea PM |
16410 | |
16411 | @kindex dll-symbols | |
16412 | @item dll-symbols | |
16413 | This command loads symbols from a dll similarly to | |
16414 | add-sym command but without the need to specify a base address. | |
16415 | ||
be90c084 | 16416 | @kindex set cygwin-exceptions |
e16b02ee EZ |
16417 | @cindex debugging the Cygwin DLL |
16418 | @cindex Cygwin DLL, debugging | |
be90c084 | 16419 | @item set cygwin-exceptions @var{mode} |
e16b02ee EZ |
16420 | If @var{mode} is @code{on}, @value{GDBN} will break on exceptions that |
16421 | happen inside the Cygwin DLL. If @var{mode} is @code{off}, | |
16422 | @value{GDBN} will delay recognition of exceptions, and may ignore some | |
16423 | exceptions which seem to be caused by internal Cygwin DLL | |
16424 | ``bookkeeping''. This option is meant primarily for debugging the | |
16425 | Cygwin DLL itself; the default value is @code{off} to avoid annoying | |
16426 | @value{GDBN} users with false @code{SIGSEGV} signals. | |
be90c084 CF |
16427 | |
16428 | @kindex show cygwin-exceptions | |
16429 | @item show cygwin-exceptions | |
e16b02ee EZ |
16430 | Displays whether @value{GDBN} will break on exceptions that happen |
16431 | inside the Cygwin DLL itself. | |
be90c084 | 16432 | |
b383017d | 16433 | @kindex set new-console |
78c47bea | 16434 | @item set new-console @var{mode} |
b383017d | 16435 | If @var{mode} is @code{on} the debuggee will |
78c47bea | 16436 | be started in a new console on next start. |
e03e5e7b | 16437 | If @var{mode} is @code{off}, the debuggee will |
78c47bea PM |
16438 | be started in the same console as the debugger. |
16439 | ||
16440 | @kindex show new-console | |
16441 | @item show new-console | |
16442 | Displays whether a new console is used | |
16443 | when the debuggee is started. | |
16444 | ||
16445 | @kindex set new-group | |
16446 | @item set new-group @var{mode} | |
16447 | This boolean value controls whether the debuggee should | |
16448 | start a new group or stay in the same group as the debugger. | |
16449 | This affects the way the Windows OS handles | |
c8aa23ab | 16450 | @samp{Ctrl-C}. |
78c47bea PM |
16451 | |
16452 | @kindex show new-group | |
16453 | @item show new-group | |
16454 | Displays current value of new-group boolean. | |
16455 | ||
16456 | @kindex set debugevents | |
16457 | @item set debugevents | |
219eec71 EZ |
16458 | This boolean value adds debug output concerning kernel events related |
16459 | to the debuggee seen by the debugger. This includes events that | |
16460 | signal thread and process creation and exit, DLL loading and | |
16461 | unloading, console interrupts, and debugging messages produced by the | |
16462 | Windows @code{OutputDebugString} API call. | |
78c47bea PM |
16463 | |
16464 | @kindex set debugexec | |
16465 | @item set debugexec | |
b383017d | 16466 | This boolean value adds debug output concerning execute events |
219eec71 | 16467 | (such as resume thread) seen by the debugger. |
78c47bea PM |
16468 | |
16469 | @kindex set debugexceptions | |
16470 | @item set debugexceptions | |
219eec71 EZ |
16471 | This boolean value adds debug output concerning exceptions in the |
16472 | debuggee seen by the debugger. | |
78c47bea PM |
16473 | |
16474 | @kindex set debugmemory | |
16475 | @item set debugmemory | |
219eec71 EZ |
16476 | This boolean value adds debug output concerning debuggee memory reads |
16477 | and writes by the debugger. | |
78c47bea PM |
16478 | |
16479 | @kindex set shell | |
16480 | @item set shell | |
16481 | This boolean values specifies whether the debuggee is called | |
16482 | via a shell or directly (default value is on). | |
16483 | ||
16484 | @kindex show shell | |
16485 | @item show shell | |
16486 | Displays if the debuggee will be started with a shell. | |
16487 | ||
16488 | @end table | |
16489 | ||
be448670 | 16490 | @menu |
79a6e687 | 16491 | * Non-debug DLL Symbols:: Support for DLLs without debugging symbols |
be448670 CF |
16492 | @end menu |
16493 | ||
79a6e687 BW |
16494 | @node Non-debug DLL Symbols |
16495 | @subsubsection Support for DLLs without Debugging Symbols | |
be448670 CF |
16496 | @cindex DLLs with no debugging symbols |
16497 | @cindex Minimal symbols and DLLs | |
16498 | ||
16499 | Very often on windows, some of the DLLs that your program relies on do | |
16500 | not include symbolic debugging information (for example, | |
db2e3e2e | 16501 | @file{kernel32.dll}). When @value{GDBN} doesn't recognize any debugging |
be448670 | 16502 | symbols in a DLL, it relies on the minimal amount of symbolic |
db2e3e2e | 16503 | information contained in the DLL's export table. This section |
be448670 CF |
16504 | describes working with such symbols, known internally to @value{GDBN} as |
16505 | ``minimal symbols''. | |
16506 | ||
16507 | Note that before the debugged program has started execution, no DLLs | |
db2e3e2e | 16508 | will have been loaded. The easiest way around this problem is simply to |
be448670 | 16509 | start the program --- either by setting a breakpoint or letting the |
db2e3e2e | 16510 | program run once to completion. It is also possible to force |
be448670 | 16511 | @value{GDBN} to load a particular DLL before starting the executable --- |
12c27660 | 16512 | see the shared library information in @ref{Files}, or the |
db2e3e2e | 16513 | @code{dll-symbols} command in @ref{Cygwin Native}. Currently, |
be448670 CF |
16514 | explicitly loading symbols from a DLL with no debugging information will |
16515 | cause the symbol names to be duplicated in @value{GDBN}'s lookup table, | |
16516 | which may adversely affect symbol lookup performance. | |
16517 | ||
79a6e687 | 16518 | @subsubsection DLL Name Prefixes |
be448670 CF |
16519 | |
16520 | In keeping with the naming conventions used by the Microsoft debugging | |
16521 | tools, DLL export symbols are made available with a prefix based on the | |
16522 | DLL name, for instance @code{KERNEL32!CreateFileA}. The plain name is | |
16523 | also entered into the symbol table, so @code{CreateFileA} is often | |
99e008fe | 16524 | sufficient. In some cases there will be name clashes within a program |
be448670 CF |
16525 | (particularly if the executable itself includes full debugging symbols) |
16526 | necessitating the use of the fully qualified name when referring to the | |
99e008fe | 16527 | contents of the DLL. Use single-quotes around the name to avoid the |
be448670 CF |
16528 | exclamation mark (``!'') being interpreted as a language operator. |
16529 | ||
16530 | Note that the internal name of the DLL may be all upper-case, even | |
99e008fe | 16531 | though the file name of the DLL is lower-case, or vice-versa. Since |
be448670 CF |
16532 | symbols within @value{GDBN} are @emph{case-sensitive} this may cause |
16533 | some confusion. If in doubt, try the @code{info functions} and | |
0869d01b NR |
16534 | @code{info variables} commands or even @code{maint print msymbols} |
16535 | (@pxref{Symbols}). Here's an example: | |
be448670 CF |
16536 | |
16537 | @smallexample | |
f7dc1244 | 16538 | (@value{GDBP}) info function CreateFileA |
be448670 CF |
16539 | All functions matching regular expression "CreateFileA": |
16540 | ||
16541 | Non-debugging symbols: | |
16542 | 0x77e885f4 CreateFileA | |
16543 | 0x77e885f4 KERNEL32!CreateFileA | |
16544 | @end smallexample | |
16545 | ||
16546 | @smallexample | |
f7dc1244 | 16547 | (@value{GDBP}) info function ! |
be448670 CF |
16548 | All functions matching regular expression "!": |
16549 | ||
16550 | Non-debugging symbols: | |
16551 | 0x6100114c cygwin1!__assert | |
16552 | 0x61004034 cygwin1!_dll_crt0@@0 | |
16553 | 0x61004240 cygwin1!dll_crt0(per_process *) | |
16554 | [etc...] | |
16555 | @end smallexample | |
16556 | ||
79a6e687 | 16557 | @subsubsection Working with Minimal Symbols |
be448670 CF |
16558 | |
16559 | Symbols extracted from a DLL's export table do not contain very much | |
16560 | type information. All that @value{GDBN} can do is guess whether a symbol | |
16561 | refers to a function or variable depending on the linker section that | |
16562 | contains the symbol. Also note that the actual contents of the memory | |
16563 | contained in a DLL are not available unless the program is running. This | |
16564 | means that you cannot examine the contents of a variable or disassemble | |
16565 | a function within a DLL without a running program. | |
16566 | ||
16567 | Variables are generally treated as pointers and dereferenced | |
16568 | automatically. For this reason, it is often necessary to prefix a | |
16569 | variable name with the address-of operator (``&'') and provide explicit | |
16570 | type information in the command. Here's an example of the type of | |
16571 | problem: | |
16572 | ||
16573 | @smallexample | |
f7dc1244 | 16574 | (@value{GDBP}) print 'cygwin1!__argv' |
be448670 CF |
16575 | $1 = 268572168 |
16576 | @end smallexample | |
16577 | ||
16578 | @smallexample | |
f7dc1244 | 16579 | (@value{GDBP}) x 'cygwin1!__argv' |
be448670 CF |
16580 | 0x10021610: "\230y\"" |
16581 | @end smallexample | |
16582 | ||
16583 | And two possible solutions: | |
16584 | ||
16585 | @smallexample | |
f7dc1244 | 16586 | (@value{GDBP}) print ((char **)'cygwin1!__argv')[0] |
be448670 CF |
16587 | $2 = 0x22fd98 "/cygdrive/c/mydirectory/myprogram" |
16588 | @end smallexample | |
16589 | ||
16590 | @smallexample | |
f7dc1244 | 16591 | (@value{GDBP}) x/2x &'cygwin1!__argv' |
be448670 | 16592 | 0x610c0aa8 <cygwin1!__argv>: 0x10021608 0x00000000 |
f7dc1244 | 16593 | (@value{GDBP}) x/x 0x10021608 |
be448670 | 16594 | 0x10021608: 0x0022fd98 |
f7dc1244 | 16595 | (@value{GDBP}) x/s 0x0022fd98 |
be448670 CF |
16596 | 0x22fd98: "/cygdrive/c/mydirectory/myprogram" |
16597 | @end smallexample | |
16598 | ||
16599 | Setting a break point within a DLL is possible even before the program | |
16600 | starts execution. However, under these circumstances, @value{GDBN} can't | |
16601 | examine the initial instructions of the function in order to skip the | |
16602 | function's frame set-up code. You can work around this by using ``*&'' | |
16603 | to set the breakpoint at a raw memory address: | |
16604 | ||
16605 | @smallexample | |
f7dc1244 | 16606 | (@value{GDBP}) break *&'python22!PyOS_Readline' |
be448670 CF |
16607 | Breakpoint 1 at 0x1e04eff0 |
16608 | @end smallexample | |
16609 | ||
16610 | The author of these extensions is not entirely convinced that setting a | |
16611 | break point within a shared DLL like @file{kernel32.dll} is completely | |
16612 | safe. | |
16613 | ||
14d6dd68 | 16614 | @node Hurd Native |
79a6e687 | 16615 | @subsection Commands Specific to @sc{gnu} Hurd Systems |
14d6dd68 EZ |
16616 | @cindex @sc{gnu} Hurd debugging |
16617 | ||
16618 | This subsection describes @value{GDBN} commands specific to the | |
16619 | @sc{gnu} Hurd native debugging. | |
16620 | ||
16621 | @table @code | |
16622 | @item set signals | |
16623 | @itemx set sigs | |
16624 | @kindex set signals@r{, Hurd command} | |
16625 | @kindex set sigs@r{, Hurd command} | |
16626 | This command toggles the state of inferior signal interception by | |
16627 | @value{GDBN}. Mach exceptions, such as breakpoint traps, are not | |
16628 | affected by this command. @code{sigs} is a shorthand alias for | |
16629 | @code{signals}. | |
16630 | ||
16631 | @item show signals | |
16632 | @itemx show sigs | |
16633 | @kindex show signals@r{, Hurd command} | |
16634 | @kindex show sigs@r{, Hurd command} | |
16635 | Show the current state of intercepting inferior's signals. | |
16636 | ||
16637 | @item set signal-thread | |
16638 | @itemx set sigthread | |
16639 | @kindex set signal-thread | |
16640 | @kindex set sigthread | |
16641 | This command tells @value{GDBN} which thread is the @code{libc} signal | |
16642 | thread. That thread is run when a signal is delivered to a running | |
16643 | process. @code{set sigthread} is the shorthand alias of @code{set | |
16644 | signal-thread}. | |
16645 | ||
16646 | @item show signal-thread | |
16647 | @itemx show sigthread | |
16648 | @kindex show signal-thread | |
16649 | @kindex show sigthread | |
16650 | These two commands show which thread will run when the inferior is | |
16651 | delivered a signal. | |
16652 | ||
16653 | @item set stopped | |
16654 | @kindex set stopped@r{, Hurd command} | |
16655 | This commands tells @value{GDBN} that the inferior process is stopped, | |
16656 | as with the @code{SIGSTOP} signal. The stopped process can be | |
16657 | continued by delivering a signal to it. | |
16658 | ||
16659 | @item show stopped | |
16660 | @kindex show stopped@r{, Hurd command} | |
16661 | This command shows whether @value{GDBN} thinks the debuggee is | |
16662 | stopped. | |
16663 | ||
16664 | @item set exceptions | |
16665 | @kindex set exceptions@r{, Hurd command} | |
16666 | Use this command to turn off trapping of exceptions in the inferior. | |
16667 | When exception trapping is off, neither breakpoints nor | |
16668 | single-stepping will work. To restore the default, set exception | |
16669 | trapping on. | |
16670 | ||
16671 | @item show exceptions | |
16672 | @kindex show exceptions@r{, Hurd command} | |
16673 | Show the current state of trapping exceptions in the inferior. | |
16674 | ||
16675 | @item set task pause | |
16676 | @kindex set task@r{, Hurd commands} | |
16677 | @cindex task attributes (@sc{gnu} Hurd) | |
16678 | @cindex pause current task (@sc{gnu} Hurd) | |
16679 | This command toggles task suspension when @value{GDBN} has control. | |
16680 | Setting it to on takes effect immediately, and the task is suspended | |
16681 | whenever @value{GDBN} gets control. Setting it to off will take | |
16682 | effect the next time the inferior is continued. If this option is set | |
16683 | to off, you can use @code{set thread default pause on} or @code{set | |
16684 | thread pause on} (see below) to pause individual threads. | |
16685 | ||
16686 | @item show task pause | |
16687 | @kindex show task@r{, Hurd commands} | |
16688 | Show the current state of task suspension. | |
16689 | ||
16690 | @item set task detach-suspend-count | |
16691 | @cindex task suspend count | |
16692 | @cindex detach from task, @sc{gnu} Hurd | |
16693 | This command sets the suspend count the task will be left with when | |
16694 | @value{GDBN} detaches from it. | |
16695 | ||
16696 | @item show task detach-suspend-count | |
16697 | Show the suspend count the task will be left with when detaching. | |
16698 | ||
16699 | @item set task exception-port | |
16700 | @itemx set task excp | |
16701 | @cindex task exception port, @sc{gnu} Hurd | |
16702 | This command sets the task exception port to which @value{GDBN} will | |
16703 | forward exceptions. The argument should be the value of the @dfn{send | |
16704 | rights} of the task. @code{set task excp} is a shorthand alias. | |
16705 | ||
16706 | @item set noninvasive | |
16707 | @cindex noninvasive task options | |
16708 | This command switches @value{GDBN} to a mode that is the least | |
16709 | invasive as far as interfering with the inferior is concerned. This | |
16710 | is the same as using @code{set task pause}, @code{set exceptions}, and | |
16711 | @code{set signals} to values opposite to the defaults. | |
16712 | ||
16713 | @item info send-rights | |
16714 | @itemx info receive-rights | |
16715 | @itemx info port-rights | |
16716 | @itemx info port-sets | |
16717 | @itemx info dead-names | |
16718 | @itemx info ports | |
16719 | @itemx info psets | |
16720 | @cindex send rights, @sc{gnu} Hurd | |
16721 | @cindex receive rights, @sc{gnu} Hurd | |
16722 | @cindex port rights, @sc{gnu} Hurd | |
16723 | @cindex port sets, @sc{gnu} Hurd | |
16724 | @cindex dead names, @sc{gnu} Hurd | |
16725 | These commands display information about, respectively, send rights, | |
16726 | receive rights, port rights, port sets, and dead names of a task. | |
16727 | There are also shorthand aliases: @code{info ports} for @code{info | |
16728 | port-rights} and @code{info psets} for @code{info port-sets}. | |
16729 | ||
16730 | @item set thread pause | |
16731 | @kindex set thread@r{, Hurd command} | |
16732 | @cindex thread properties, @sc{gnu} Hurd | |
16733 | @cindex pause current thread (@sc{gnu} Hurd) | |
16734 | This command toggles current thread suspension when @value{GDBN} has | |
16735 | control. Setting it to on takes effect immediately, and the current | |
16736 | thread is suspended whenever @value{GDBN} gets control. Setting it to | |
16737 | off will take effect the next time the inferior is continued. | |
16738 | Normally, this command has no effect, since when @value{GDBN} has | |
16739 | control, the whole task is suspended. However, if you used @code{set | |
16740 | task pause off} (see above), this command comes in handy to suspend | |
16741 | only the current thread. | |
16742 | ||
16743 | @item show thread pause | |
16744 | @kindex show thread@r{, Hurd command} | |
16745 | This command shows the state of current thread suspension. | |
16746 | ||
16747 | @item set thread run | |
d3e8051b | 16748 | This command sets whether the current thread is allowed to run. |
14d6dd68 EZ |
16749 | |
16750 | @item show thread run | |
16751 | Show whether the current thread is allowed to run. | |
16752 | ||
16753 | @item set thread detach-suspend-count | |
16754 | @cindex thread suspend count, @sc{gnu} Hurd | |
16755 | @cindex detach from thread, @sc{gnu} Hurd | |
16756 | This command sets the suspend count @value{GDBN} will leave on a | |
16757 | thread when detaching. This number is relative to the suspend count | |
16758 | found by @value{GDBN} when it notices the thread; use @code{set thread | |
16759 | takeover-suspend-count} to force it to an absolute value. | |
16760 | ||
16761 | @item show thread detach-suspend-count | |
16762 | Show the suspend count @value{GDBN} will leave on the thread when | |
16763 | detaching. | |
16764 | ||
16765 | @item set thread exception-port | |
16766 | @itemx set thread excp | |
16767 | Set the thread exception port to which to forward exceptions. This | |
16768 | overrides the port set by @code{set task exception-port} (see above). | |
16769 | @code{set thread excp} is the shorthand alias. | |
16770 | ||
16771 | @item set thread takeover-suspend-count | |
16772 | Normally, @value{GDBN}'s thread suspend counts are relative to the | |
16773 | value @value{GDBN} finds when it notices each thread. This command | |
16774 | changes the suspend counts to be absolute instead. | |
16775 | ||
16776 | @item set thread default | |
16777 | @itemx show thread default | |
16778 | @cindex thread default settings, @sc{gnu} Hurd | |
16779 | Each of the above @code{set thread} commands has a @code{set thread | |
16780 | default} counterpart (e.g., @code{set thread default pause}, @code{set | |
16781 | thread default exception-port}, etc.). The @code{thread default} | |
16782 | variety of commands sets the default thread properties for all | |
16783 | threads; you can then change the properties of individual threads with | |
16784 | the non-default commands. | |
16785 | @end table | |
16786 | ||
16787 | ||
a64548ea EZ |
16788 | @node Neutrino |
16789 | @subsection QNX Neutrino | |
16790 | @cindex QNX Neutrino | |
16791 | ||
16792 | @value{GDBN} provides the following commands specific to the QNX | |
16793 | Neutrino target: | |
16794 | ||
16795 | @table @code | |
16796 | @item set debug nto-debug | |
16797 | @kindex set debug nto-debug | |
16798 | When set to on, enables debugging messages specific to the QNX | |
16799 | Neutrino support. | |
16800 | ||
16801 | @item show debug nto-debug | |
16802 | @kindex show debug nto-debug | |
16803 | Show the current state of QNX Neutrino messages. | |
16804 | @end table | |
16805 | ||
a80b95ba TG |
16806 | @node Darwin |
16807 | @subsection Darwin | |
16808 | @cindex Darwin | |
16809 | ||
16810 | @value{GDBN} provides the following commands specific to the Darwin target: | |
16811 | ||
16812 | @table @code | |
16813 | @item set debug darwin @var{num} | |
16814 | @kindex set debug darwin | |
16815 | When set to a non zero value, enables debugging messages specific to | |
16816 | the Darwin support. Higher values produce more verbose output. | |
16817 | ||
16818 | @item show debug darwin | |
16819 | @kindex show debug darwin | |
16820 | Show the current state of Darwin messages. | |
16821 | ||
16822 | @item set debug mach-o @var{num} | |
16823 | @kindex set debug mach-o | |
16824 | When set to a non zero value, enables debugging messages while | |
16825 | @value{GDBN} is reading Darwin object files. (@dfn{Mach-O} is the | |
16826 | file format used on Darwin for object and executable files.) Higher | |
16827 | values produce more verbose output. This is a command to diagnose | |
16828 | problems internal to @value{GDBN} and should not be needed in normal | |
16829 | usage. | |
16830 | ||
16831 | @item show debug mach-o | |
16832 | @kindex show debug mach-o | |
16833 | Show the current state of Mach-O file messages. | |
16834 | ||
16835 | @item set mach-exceptions on | |
16836 | @itemx set mach-exceptions off | |
16837 | @kindex set mach-exceptions | |
16838 | On Darwin, faults are first reported as a Mach exception and are then | |
16839 | mapped to a Posix signal. Use this command to turn on trapping of | |
16840 | Mach exceptions in the inferior. This might be sometimes useful to | |
16841 | better understand the cause of a fault. The default is off. | |
16842 | ||
16843 | @item show mach-exceptions | |
16844 | @kindex show mach-exceptions | |
16845 | Show the current state of exceptions trapping. | |
16846 | @end table | |
16847 | ||
a64548ea | 16848 | |
8e04817f AC |
16849 | @node Embedded OS |
16850 | @section Embedded Operating Systems | |
104c1213 | 16851 | |
8e04817f AC |
16852 | This section describes configurations involving the debugging of |
16853 | embedded operating systems that are available for several different | |
16854 | architectures. | |
d4f3574e | 16855 | |
8e04817f AC |
16856 | @menu |
16857 | * VxWorks:: Using @value{GDBN} with VxWorks | |
16858 | @end menu | |
104c1213 | 16859 | |
8e04817f AC |
16860 | @value{GDBN} includes the ability to debug programs running on |
16861 | various real-time operating systems. | |
104c1213 | 16862 | |
8e04817f AC |
16863 | @node VxWorks |
16864 | @subsection Using @value{GDBN} with VxWorks | |
104c1213 | 16865 | |
8e04817f | 16866 | @cindex VxWorks |
104c1213 | 16867 | |
8e04817f | 16868 | @table @code |
104c1213 | 16869 | |
8e04817f AC |
16870 | @kindex target vxworks |
16871 | @item target vxworks @var{machinename} | |
16872 | A VxWorks system, attached via TCP/IP. The argument @var{machinename} | |
16873 | is the target system's machine name or IP address. | |
104c1213 | 16874 | |
8e04817f | 16875 | @end table |
104c1213 | 16876 | |
8e04817f AC |
16877 | On VxWorks, @code{load} links @var{filename} dynamically on the |
16878 | current target system as well as adding its symbols in @value{GDBN}. | |
104c1213 | 16879 | |
8e04817f AC |
16880 | @value{GDBN} enables developers to spawn and debug tasks running on networked |
16881 | VxWorks targets from a Unix host. Already-running tasks spawned from | |
16882 | the VxWorks shell can also be debugged. @value{GDBN} uses code that runs on | |
16883 | both the Unix host and on the VxWorks target. The program | |
16884 | @code{@value{GDBP}} is installed and executed on the Unix host. (It may be | |
16885 | installed with the name @code{vxgdb}, to distinguish it from a | |
16886 | @value{GDBN} for debugging programs on the host itself.) | |
104c1213 | 16887 | |
8e04817f AC |
16888 | @table @code |
16889 | @item VxWorks-timeout @var{args} | |
16890 | @kindex vxworks-timeout | |
16891 | All VxWorks-based targets now support the option @code{vxworks-timeout}. | |
16892 | This option is set by the user, and @var{args} represents the number of | |
16893 | seconds @value{GDBN} waits for responses to rpc's. You might use this if | |
16894 | your VxWorks target is a slow software simulator or is on the far side | |
16895 | of a thin network line. | |
16896 | @end table | |
104c1213 | 16897 | |
8e04817f AC |
16898 | The following information on connecting to VxWorks was current when |
16899 | this manual was produced; newer releases of VxWorks may use revised | |
16900 | procedures. | |
104c1213 | 16901 | |
4644b6e3 | 16902 | @findex INCLUDE_RDB |
8e04817f AC |
16903 | To use @value{GDBN} with VxWorks, you must rebuild your VxWorks kernel |
16904 | to include the remote debugging interface routines in the VxWorks | |
16905 | library @file{rdb.a}. To do this, define @code{INCLUDE_RDB} in the | |
16906 | VxWorks configuration file @file{configAll.h} and rebuild your VxWorks | |
16907 | kernel. The resulting kernel contains @file{rdb.a}, and spawns the | |
16908 | source debugging task @code{tRdbTask} when VxWorks is booted. For more | |
16909 | information on configuring and remaking VxWorks, see the manufacturer's | |
16910 | manual. | |
16911 | @c VxWorks, see the @cite{VxWorks Programmer's Guide}. | |
104c1213 | 16912 | |
8e04817f AC |
16913 | Once you have included @file{rdb.a} in your VxWorks system image and set |
16914 | your Unix execution search path to find @value{GDBN}, you are ready to | |
16915 | run @value{GDBN}. From your Unix host, run @code{@value{GDBP}} (or | |
16916 | @code{vxgdb}, depending on your installation). | |
104c1213 | 16917 | |
8e04817f | 16918 | @value{GDBN} comes up showing the prompt: |
104c1213 | 16919 | |
474c8240 | 16920 | @smallexample |
8e04817f | 16921 | (vxgdb) |
474c8240 | 16922 | @end smallexample |
104c1213 | 16923 | |
8e04817f AC |
16924 | @menu |
16925 | * VxWorks Connection:: Connecting to VxWorks | |
16926 | * VxWorks Download:: VxWorks download | |
16927 | * VxWorks Attach:: Running tasks | |
16928 | @end menu | |
104c1213 | 16929 | |
8e04817f AC |
16930 | @node VxWorks Connection |
16931 | @subsubsection Connecting to VxWorks | |
104c1213 | 16932 | |
8e04817f AC |
16933 | The @value{GDBN} command @code{target} lets you connect to a VxWorks target on the |
16934 | network. To connect to a target whose host name is ``@code{tt}'', type: | |
104c1213 | 16935 | |
474c8240 | 16936 | @smallexample |
8e04817f | 16937 | (vxgdb) target vxworks tt |
474c8240 | 16938 | @end smallexample |
104c1213 | 16939 | |
8e04817f AC |
16940 | @need 750 |
16941 | @value{GDBN} displays messages like these: | |
104c1213 | 16942 | |
8e04817f AC |
16943 | @smallexample |
16944 | Attaching remote machine across net... | |
16945 | Connected to tt. | |
16946 | @end smallexample | |
104c1213 | 16947 | |
8e04817f AC |
16948 | @need 1000 |
16949 | @value{GDBN} then attempts to read the symbol tables of any object modules | |
16950 | loaded into the VxWorks target since it was last booted. @value{GDBN} locates | |
16951 | these files by searching the directories listed in the command search | |
79a6e687 | 16952 | path (@pxref{Environment, ,Your Program's Environment}); if it fails |
8e04817f | 16953 | to find an object file, it displays a message such as: |
5d161b24 | 16954 | |
474c8240 | 16955 | @smallexample |
8e04817f | 16956 | prog.o: No such file or directory. |
474c8240 | 16957 | @end smallexample |
104c1213 | 16958 | |
8e04817f AC |
16959 | When this happens, add the appropriate directory to the search path with |
16960 | the @value{GDBN} command @code{path}, and execute the @code{target} | |
16961 | command again. | |
104c1213 | 16962 | |
8e04817f | 16963 | @node VxWorks Download |
79a6e687 | 16964 | @subsubsection VxWorks Download |
104c1213 | 16965 | |
8e04817f AC |
16966 | @cindex download to VxWorks |
16967 | If you have connected to the VxWorks target and you want to debug an | |
16968 | object that has not yet been loaded, you can use the @value{GDBN} | |
16969 | @code{load} command to download a file from Unix to VxWorks | |
16970 | incrementally. The object file given as an argument to the @code{load} | |
16971 | command is actually opened twice: first by the VxWorks target in order | |
16972 | to download the code, then by @value{GDBN} in order to read the symbol | |
16973 | table. This can lead to problems if the current working directories on | |
16974 | the two systems differ. If both systems have NFS mounted the same | |
16975 | filesystems, you can avoid these problems by using absolute paths. | |
16976 | Otherwise, it is simplest to set the working directory on both systems | |
16977 | to the directory in which the object file resides, and then to reference | |
16978 | the file by its name, without any path. For instance, a program | |
16979 | @file{prog.o} may reside in @file{@var{vxpath}/vw/demo/rdb} in VxWorks | |
16980 | and in @file{@var{hostpath}/vw/demo/rdb} on the host. To load this | |
16981 | program, type this on VxWorks: | |
104c1213 | 16982 | |
474c8240 | 16983 | @smallexample |
8e04817f | 16984 | -> cd "@var{vxpath}/vw/demo/rdb" |
474c8240 | 16985 | @end smallexample |
104c1213 | 16986 | |
8e04817f AC |
16987 | @noindent |
16988 | Then, in @value{GDBN}, type: | |
104c1213 | 16989 | |
474c8240 | 16990 | @smallexample |
8e04817f AC |
16991 | (vxgdb) cd @var{hostpath}/vw/demo/rdb |
16992 | (vxgdb) load prog.o | |
474c8240 | 16993 | @end smallexample |
104c1213 | 16994 | |
8e04817f | 16995 | @value{GDBN} displays a response similar to this: |
104c1213 | 16996 | |
8e04817f AC |
16997 | @smallexample |
16998 | Reading symbol data from wherever/vw/demo/rdb/prog.o... done. | |
16999 | @end smallexample | |
104c1213 | 17000 | |
8e04817f AC |
17001 | You can also use the @code{load} command to reload an object module |
17002 | after editing and recompiling the corresponding source file. Note that | |
17003 | this makes @value{GDBN} delete all currently-defined breakpoints, | |
17004 | auto-displays, and convenience variables, and to clear the value | |
17005 | history. (This is necessary in order to preserve the integrity of | |
17006 | debugger's data structures that reference the target system's symbol | |
17007 | table.) | |
104c1213 | 17008 | |
8e04817f | 17009 | @node VxWorks Attach |
79a6e687 | 17010 | @subsubsection Running Tasks |
104c1213 JM |
17011 | |
17012 | @cindex running VxWorks tasks | |
17013 | You can also attach to an existing task using the @code{attach} command as | |
17014 | follows: | |
17015 | ||
474c8240 | 17016 | @smallexample |
104c1213 | 17017 | (vxgdb) attach @var{task} |
474c8240 | 17018 | @end smallexample |
104c1213 JM |
17019 | |
17020 | @noindent | |
17021 | where @var{task} is the VxWorks hexadecimal task ID. The task can be running | |
17022 | or suspended when you attach to it. Running tasks are suspended at | |
17023 | the time of attachment. | |
17024 | ||
6d2ebf8b | 17025 | @node Embedded Processors |
104c1213 JM |
17026 | @section Embedded Processors |
17027 | ||
17028 | This section goes into details specific to particular embedded | |
17029 | configurations. | |
17030 | ||
c45da7e6 EZ |
17031 | @cindex send command to simulator |
17032 | Whenever a specific embedded processor has a simulator, @value{GDBN} | |
17033 | allows to send an arbitrary command to the simulator. | |
17034 | ||
17035 | @table @code | |
17036 | @item sim @var{command} | |
17037 | @kindex sim@r{, a command} | |
17038 | Send an arbitrary @var{command} string to the simulator. Consult the | |
17039 | documentation for the specific simulator in use for information about | |
17040 | acceptable commands. | |
17041 | @end table | |
17042 | ||
7d86b5d5 | 17043 | |
104c1213 | 17044 | @menu |
c45da7e6 | 17045 | * ARM:: ARM RDI |
172c2a43 | 17046 | * M32R/D:: Renesas M32R/D |
104c1213 | 17047 | * M68K:: Motorola M68K |
08be9d71 | 17048 | * MicroBlaze:: Xilinx MicroBlaze |
104c1213 | 17049 | * MIPS Embedded:: MIPS Embedded |
a37295f9 | 17050 | * OpenRISC 1000:: OpenRisc 1000 |
104c1213 | 17051 | * PA:: HP PA Embedded |
4acd40f3 | 17052 | * PowerPC Embedded:: PowerPC Embedded |
104c1213 JM |
17053 | * Sparclet:: Tsqware Sparclet |
17054 | * Sparclite:: Fujitsu Sparclite | |
104c1213 | 17055 | * Z8000:: Zilog Z8000 |
a64548ea EZ |
17056 | * AVR:: Atmel AVR |
17057 | * CRIS:: CRIS | |
17058 | * Super-H:: Renesas Super-H | |
104c1213 JM |
17059 | @end menu |
17060 | ||
6d2ebf8b | 17061 | @node ARM |
104c1213 | 17062 | @subsection ARM |
c45da7e6 | 17063 | @cindex ARM RDI |
104c1213 JM |
17064 | |
17065 | @table @code | |
8e04817f AC |
17066 | @kindex target rdi |
17067 | @item target rdi @var{dev} | |
17068 | ARM Angel monitor, via RDI library interface to ADP protocol. You may | |
17069 | use this target to communicate with both boards running the Angel | |
17070 | monitor, or with the EmbeddedICE JTAG debug device. | |
17071 | ||
17072 | @kindex target rdp | |
17073 | @item target rdp @var{dev} | |
17074 | ARM Demon monitor. | |
17075 | ||
17076 | @end table | |
17077 | ||
e2f4edfd EZ |
17078 | @value{GDBN} provides the following ARM-specific commands: |
17079 | ||
17080 | @table @code | |
17081 | @item set arm disassembler | |
17082 | @kindex set arm | |
17083 | This commands selects from a list of disassembly styles. The | |
17084 | @code{"std"} style is the standard style. | |
17085 | ||
17086 | @item show arm disassembler | |
17087 | @kindex show arm | |
17088 | Show the current disassembly style. | |
17089 | ||
17090 | @item set arm apcs32 | |
17091 | @cindex ARM 32-bit mode | |
17092 | This command toggles ARM operation mode between 32-bit and 26-bit. | |
17093 | ||
17094 | @item show arm apcs32 | |
17095 | Display the current usage of the ARM 32-bit mode. | |
17096 | ||
17097 | @item set arm fpu @var{fputype} | |
17098 | This command sets the ARM floating-point unit (FPU) type. The | |
17099 | argument @var{fputype} can be one of these: | |
17100 | ||
17101 | @table @code | |
17102 | @item auto | |
17103 | Determine the FPU type by querying the OS ABI. | |
17104 | @item softfpa | |
17105 | Software FPU, with mixed-endian doubles on little-endian ARM | |
17106 | processors. | |
17107 | @item fpa | |
17108 | GCC-compiled FPA co-processor. | |
17109 | @item softvfp | |
17110 | Software FPU with pure-endian doubles. | |
17111 | @item vfp | |
17112 | VFP co-processor. | |
17113 | @end table | |
17114 | ||
17115 | @item show arm fpu | |
17116 | Show the current type of the FPU. | |
17117 | ||
17118 | @item set arm abi | |
17119 | This command forces @value{GDBN} to use the specified ABI. | |
17120 | ||
17121 | @item show arm abi | |
17122 | Show the currently used ABI. | |
17123 | ||
0428b8f5 DJ |
17124 | @item set arm fallback-mode (arm|thumb|auto) |
17125 | @value{GDBN} uses the symbol table, when available, to determine | |
17126 | whether instructions are ARM or Thumb. This command controls | |
17127 | @value{GDBN}'s default behavior when the symbol table is not | |
17128 | available. The default is @samp{auto}, which causes @value{GDBN} to | |
17129 | use the current execution mode (from the @code{T} bit in the @code{CPSR} | |
17130 | register). | |
17131 | ||
17132 | @item show arm fallback-mode | |
17133 | Show the current fallback instruction mode. | |
17134 | ||
17135 | @item set arm force-mode (arm|thumb|auto) | |
17136 | This command overrides use of the symbol table to determine whether | |
17137 | instructions are ARM or Thumb. The default is @samp{auto}, which | |
17138 | causes @value{GDBN} to use the symbol table and then the setting | |
17139 | of @samp{set arm fallback-mode}. | |
17140 | ||
17141 | @item show arm force-mode | |
17142 | Show the current forced instruction mode. | |
17143 | ||
e2f4edfd EZ |
17144 | @item set debug arm |
17145 | Toggle whether to display ARM-specific debugging messages from the ARM | |
17146 | target support subsystem. | |
17147 | ||
17148 | @item show debug arm | |
17149 | Show whether ARM-specific debugging messages are enabled. | |
17150 | @end table | |
17151 | ||
c45da7e6 EZ |
17152 | The following commands are available when an ARM target is debugged |
17153 | using the RDI interface: | |
17154 | ||
17155 | @table @code | |
17156 | @item rdilogfile @r{[}@var{file}@r{]} | |
17157 | @kindex rdilogfile | |
17158 | @cindex ADP (Angel Debugger Protocol) logging | |
17159 | Set the filename for the ADP (Angel Debugger Protocol) packet log. | |
17160 | With an argument, sets the log file to the specified @var{file}. With | |
17161 | no argument, show the current log file name. The default log file is | |
17162 | @file{rdi.log}. | |
17163 | ||
17164 | @item rdilogenable @r{[}@var{arg}@r{]} | |
17165 | @kindex rdilogenable | |
17166 | Control logging of ADP packets. With an argument of 1 or @code{"yes"} | |
17167 | enables logging, with an argument 0 or @code{"no"} disables it. With | |
17168 | no arguments displays the current setting. When logging is enabled, | |
17169 | ADP packets exchanged between @value{GDBN} and the RDI target device | |
17170 | are logged to a file. | |
17171 | ||
17172 | @item set rdiromatzero | |
17173 | @kindex set rdiromatzero | |
17174 | @cindex ROM at zero address, RDI | |
17175 | Tell @value{GDBN} whether the target has ROM at address 0. If on, | |
17176 | vector catching is disabled, so that zero address can be used. If off | |
17177 | (the default), vector catching is enabled. For this command to take | |
17178 | effect, it needs to be invoked prior to the @code{target rdi} command. | |
17179 | ||
17180 | @item show rdiromatzero | |
17181 | @kindex show rdiromatzero | |
17182 | Show the current setting of ROM at zero address. | |
17183 | ||
17184 | @item set rdiheartbeat | |
17185 | @kindex set rdiheartbeat | |
17186 | @cindex RDI heartbeat | |
17187 | Enable or disable RDI heartbeat packets. It is not recommended to | |
17188 | turn on this option, since it confuses ARM and EPI JTAG interface, as | |
17189 | well as the Angel monitor. | |
17190 | ||
17191 | @item show rdiheartbeat | |
17192 | @kindex show rdiheartbeat | |
17193 | Show the setting of RDI heartbeat packets. | |
17194 | @end table | |
17195 | ||
e2f4edfd | 17196 | |
8e04817f | 17197 | @node M32R/D |
ba04e063 | 17198 | @subsection Renesas M32R/D and M32R/SDI |
8e04817f AC |
17199 | |
17200 | @table @code | |
8e04817f AC |
17201 | @kindex target m32r |
17202 | @item target m32r @var{dev} | |
172c2a43 | 17203 | Renesas M32R/D ROM monitor. |
8e04817f | 17204 | |
fb3e19c0 KI |
17205 | @kindex target m32rsdi |
17206 | @item target m32rsdi @var{dev} | |
17207 | Renesas M32R SDI server, connected via parallel port to the board. | |
721c2651 EZ |
17208 | @end table |
17209 | ||
17210 | The following @value{GDBN} commands are specific to the M32R monitor: | |
17211 | ||
17212 | @table @code | |
17213 | @item set download-path @var{path} | |
17214 | @kindex set download-path | |
17215 | @cindex find downloadable @sc{srec} files (M32R) | |
d3e8051b | 17216 | Set the default path for finding downloadable @sc{srec} files. |
721c2651 EZ |
17217 | |
17218 | @item show download-path | |
17219 | @kindex show download-path | |
17220 | Show the default path for downloadable @sc{srec} files. | |
fb3e19c0 | 17221 | |
721c2651 EZ |
17222 | @item set board-address @var{addr} |
17223 | @kindex set board-address | |
17224 | @cindex M32-EVA target board address | |
17225 | Set the IP address for the M32R-EVA target board. | |
17226 | ||
17227 | @item show board-address | |
17228 | @kindex show board-address | |
17229 | Show the current IP address of the target board. | |
17230 | ||
17231 | @item set server-address @var{addr} | |
17232 | @kindex set server-address | |
17233 | @cindex download server address (M32R) | |
17234 | Set the IP address for the download server, which is the @value{GDBN}'s | |
17235 | host machine. | |
17236 | ||
17237 | @item show server-address | |
17238 | @kindex show server-address | |
17239 | Display the IP address of the download server. | |
17240 | ||
17241 | @item upload @r{[}@var{file}@r{]} | |
17242 | @kindex upload@r{, M32R} | |
17243 | Upload the specified @sc{srec} @var{file} via the monitor's Ethernet | |
17244 | upload capability. If no @var{file} argument is given, the current | |
17245 | executable file is uploaded. | |
17246 | ||
17247 | @item tload @r{[}@var{file}@r{]} | |
17248 | @kindex tload@r{, M32R} | |
17249 | Test the @code{upload} command. | |
8e04817f AC |
17250 | @end table |
17251 | ||
ba04e063 EZ |
17252 | The following commands are available for M32R/SDI: |
17253 | ||
17254 | @table @code | |
17255 | @item sdireset | |
17256 | @kindex sdireset | |
17257 | @cindex reset SDI connection, M32R | |
17258 | This command resets the SDI connection. | |
17259 | ||
17260 | @item sdistatus | |
17261 | @kindex sdistatus | |
17262 | This command shows the SDI connection status. | |
17263 | ||
17264 | @item debug_chaos | |
17265 | @kindex debug_chaos | |
17266 | @cindex M32R/Chaos debugging | |
17267 | Instructs the remote that M32R/Chaos debugging is to be used. | |
17268 | ||
17269 | @item use_debug_dma | |
17270 | @kindex use_debug_dma | |
17271 | Instructs the remote to use the DEBUG_DMA method of accessing memory. | |
17272 | ||
17273 | @item use_mon_code | |
17274 | @kindex use_mon_code | |
17275 | Instructs the remote to use the MON_CODE method of accessing memory. | |
17276 | ||
17277 | @item use_ib_break | |
17278 | @kindex use_ib_break | |
17279 | Instructs the remote to set breakpoints by IB break. | |
17280 | ||
17281 | @item use_dbt_break | |
17282 | @kindex use_dbt_break | |
17283 | Instructs the remote to set breakpoints by DBT. | |
17284 | @end table | |
17285 | ||
8e04817f AC |
17286 | @node M68K |
17287 | @subsection M68k | |
17288 | ||
7ce59000 DJ |
17289 | The Motorola m68k configuration includes ColdFire support, and a |
17290 | target command for the following ROM monitor. | |
8e04817f AC |
17291 | |
17292 | @table @code | |
17293 | ||
8e04817f AC |
17294 | @kindex target dbug |
17295 | @item target dbug @var{dev} | |
17296 | dBUG ROM monitor for Motorola ColdFire. | |
17297 | ||
8e04817f AC |
17298 | @end table |
17299 | ||
08be9d71 ME |
17300 | @node MicroBlaze |
17301 | @subsection MicroBlaze | |
17302 | @cindex Xilinx MicroBlaze | |
17303 | @cindex XMD, Xilinx Microprocessor Debugger | |
17304 | ||
17305 | The MicroBlaze is a soft-core processor supported on various Xilinx | |
17306 | FPGAs, such as Spartan or Virtex series. Boards with these processors | |
17307 | usually have JTAG ports which connect to a host system running the Xilinx | |
17308 | Embedded Development Kit (EDK) or Software Development Kit (SDK). | |
17309 | This host system is used to download the configuration bitstream to | |
17310 | the target FPGA. The Xilinx Microprocessor Debugger (XMD) program | |
17311 | communicates with the target board using the JTAG interface and | |
17312 | presents a @code{gdbserver} interface to the board. By default | |
17313 | @code{xmd} uses port @code{1234}. (While it is possible to change | |
17314 | this default port, it requires the use of undocumented @code{xmd} | |
17315 | commands. Contact Xilinx support if you need to do this.) | |
17316 | ||
17317 | Use these GDB commands to connect to the MicroBlaze target processor. | |
17318 | ||
17319 | @table @code | |
17320 | @item target remote :1234 | |
17321 | Use this command to connect to the target if you are running @value{GDBN} | |
17322 | on the same system as @code{xmd}. | |
17323 | ||
17324 | @item target remote @var{xmd-host}:1234 | |
17325 | Use this command to connect to the target if it is connected to @code{xmd} | |
17326 | running on a different system named @var{xmd-host}. | |
17327 | ||
17328 | @item load | |
17329 | Use this command to download a program to the MicroBlaze target. | |
17330 | ||
17331 | @item set debug microblaze @var{n} | |
17332 | Enable MicroBlaze-specific debugging messages if non-zero. | |
17333 | ||
17334 | @item show debug microblaze @var{n} | |
17335 | Show MicroBlaze-specific debugging level. | |
17336 | @end table | |
17337 | ||
8e04817f AC |
17338 | @node MIPS Embedded |
17339 | @subsection MIPS Embedded | |
17340 | ||
17341 | @cindex MIPS boards | |
17342 | @value{GDBN} can use the MIPS remote debugging protocol to talk to a | |
17343 | MIPS board attached to a serial line. This is available when | |
17344 | you configure @value{GDBN} with @samp{--target=mips-idt-ecoff}. | |
104c1213 | 17345 | |
8e04817f AC |
17346 | @need 1000 |
17347 | Use these @value{GDBN} commands to specify the connection to your target board: | |
104c1213 | 17348 | |
8e04817f AC |
17349 | @table @code |
17350 | @item target mips @var{port} | |
17351 | @kindex target mips @var{port} | |
17352 | To run a program on the board, start up @code{@value{GDBP}} with the | |
17353 | name of your program as the argument. To connect to the board, use the | |
17354 | command @samp{target mips @var{port}}, where @var{port} is the name of | |
17355 | the serial port connected to the board. If the program has not already | |
17356 | been downloaded to the board, you may use the @code{load} command to | |
17357 | download it. You can then use all the usual @value{GDBN} commands. | |
104c1213 | 17358 | |
8e04817f AC |
17359 | For example, this sequence connects to the target board through a serial |
17360 | port, and loads and runs a program called @var{prog} through the | |
17361 | debugger: | |
104c1213 | 17362 | |
474c8240 | 17363 | @smallexample |
8e04817f AC |
17364 | host$ @value{GDBP} @var{prog} |
17365 | @value{GDBN} is free software and @dots{} | |
17366 | (@value{GDBP}) target mips /dev/ttyb | |
17367 | (@value{GDBP}) load @var{prog} | |
17368 | (@value{GDBP}) run | |
474c8240 | 17369 | @end smallexample |
104c1213 | 17370 | |
8e04817f AC |
17371 | @item target mips @var{hostname}:@var{portnumber} |
17372 | On some @value{GDBN} host configurations, you can specify a TCP | |
17373 | connection (for instance, to a serial line managed by a terminal | |
17374 | concentrator) instead of a serial port, using the syntax | |
17375 | @samp{@var{hostname}:@var{portnumber}}. | |
104c1213 | 17376 | |
8e04817f AC |
17377 | @item target pmon @var{port} |
17378 | @kindex target pmon @var{port} | |
17379 | PMON ROM monitor. | |
104c1213 | 17380 | |
8e04817f AC |
17381 | @item target ddb @var{port} |
17382 | @kindex target ddb @var{port} | |
17383 | NEC's DDB variant of PMON for Vr4300. | |
104c1213 | 17384 | |
8e04817f AC |
17385 | @item target lsi @var{port} |
17386 | @kindex target lsi @var{port} | |
17387 | LSI variant of PMON. | |
104c1213 | 17388 | |
8e04817f AC |
17389 | @kindex target r3900 |
17390 | @item target r3900 @var{dev} | |
17391 | Densan DVE-R3900 ROM monitor for Toshiba R3900 Mips. | |
104c1213 | 17392 | |
8e04817f AC |
17393 | @kindex target array |
17394 | @item target array @var{dev} | |
17395 | Array Tech LSI33K RAID controller board. | |
104c1213 | 17396 | |
8e04817f | 17397 | @end table |
104c1213 | 17398 | |
104c1213 | 17399 | |
8e04817f AC |
17400 | @noindent |
17401 | @value{GDBN} also supports these special commands for MIPS targets: | |
104c1213 | 17402 | |
8e04817f | 17403 | @table @code |
8e04817f AC |
17404 | @item set mipsfpu double |
17405 | @itemx set mipsfpu single | |
17406 | @itemx set mipsfpu none | |
a64548ea | 17407 | @itemx set mipsfpu auto |
8e04817f AC |
17408 | @itemx show mipsfpu |
17409 | @kindex set mipsfpu | |
17410 | @kindex show mipsfpu | |
17411 | @cindex MIPS remote floating point | |
17412 | @cindex floating point, MIPS remote | |
17413 | If your target board does not support the MIPS floating point | |
17414 | coprocessor, you should use the command @samp{set mipsfpu none} (if you | |
17415 | need this, you may wish to put the command in your @value{GDBN} init | |
17416 | file). This tells @value{GDBN} how to find the return value of | |
17417 | functions which return floating point values. It also allows | |
17418 | @value{GDBN} to avoid saving the floating point registers when calling | |
17419 | functions on the board. If you are using a floating point coprocessor | |
17420 | with only single precision floating point support, as on the @sc{r4650} | |
17421 | processor, use the command @samp{set mipsfpu single}. The default | |
17422 | double precision floating point coprocessor may be selected using | |
17423 | @samp{set mipsfpu double}. | |
104c1213 | 17424 | |
8e04817f AC |
17425 | In previous versions the only choices were double precision or no |
17426 | floating point, so @samp{set mipsfpu on} will select double precision | |
17427 | and @samp{set mipsfpu off} will select no floating point. | |
104c1213 | 17428 | |
8e04817f AC |
17429 | As usual, you can inquire about the @code{mipsfpu} variable with |
17430 | @samp{show mipsfpu}. | |
104c1213 | 17431 | |
8e04817f AC |
17432 | @item set timeout @var{seconds} |
17433 | @itemx set retransmit-timeout @var{seconds} | |
17434 | @itemx show timeout | |
17435 | @itemx show retransmit-timeout | |
17436 | @cindex @code{timeout}, MIPS protocol | |
17437 | @cindex @code{retransmit-timeout}, MIPS protocol | |
17438 | @kindex set timeout | |
17439 | @kindex show timeout | |
17440 | @kindex set retransmit-timeout | |
17441 | @kindex show retransmit-timeout | |
17442 | You can control the timeout used while waiting for a packet, in the MIPS | |
17443 | remote protocol, with the @code{set timeout @var{seconds}} command. The | |
17444 | default is 5 seconds. Similarly, you can control the timeout used while | |
a6f3e723 | 17445 | waiting for an acknowledgment of a packet with the @code{set |
8e04817f AC |
17446 | retransmit-timeout @var{seconds}} command. The default is 3 seconds. |
17447 | You can inspect both values with @code{show timeout} and @code{show | |
17448 | retransmit-timeout}. (These commands are @emph{only} available when | |
17449 | @value{GDBN} is configured for @samp{--target=mips-idt-ecoff}.) | |
104c1213 | 17450 | |
8e04817f AC |
17451 | The timeout set by @code{set timeout} does not apply when @value{GDBN} |
17452 | is waiting for your program to stop. In that case, @value{GDBN} waits | |
17453 | forever because it has no way of knowing how long the program is going | |
17454 | to run before stopping. | |
ba04e063 EZ |
17455 | |
17456 | @item set syn-garbage-limit @var{num} | |
17457 | @kindex set syn-garbage-limit@r{, MIPS remote} | |
17458 | @cindex synchronize with remote MIPS target | |
17459 | Limit the maximum number of characters @value{GDBN} should ignore when | |
17460 | it tries to synchronize with the remote target. The default is 10 | |
17461 | characters. Setting the limit to -1 means there's no limit. | |
17462 | ||
17463 | @item show syn-garbage-limit | |
17464 | @kindex show syn-garbage-limit@r{, MIPS remote} | |
17465 | Show the current limit on the number of characters to ignore when | |
17466 | trying to synchronize with the remote system. | |
17467 | ||
17468 | @item set monitor-prompt @var{prompt} | |
17469 | @kindex set monitor-prompt@r{, MIPS remote} | |
17470 | @cindex remote monitor prompt | |
17471 | Tell @value{GDBN} to expect the specified @var{prompt} string from the | |
17472 | remote monitor. The default depends on the target: | |
17473 | @table @asis | |
17474 | @item pmon target | |
17475 | @samp{PMON} | |
17476 | @item ddb target | |
17477 | @samp{NEC010} | |
17478 | @item lsi target | |
17479 | @samp{PMON>} | |
17480 | @end table | |
17481 | ||
17482 | @item show monitor-prompt | |
17483 | @kindex show monitor-prompt@r{, MIPS remote} | |
17484 | Show the current strings @value{GDBN} expects as the prompt from the | |
17485 | remote monitor. | |
17486 | ||
17487 | @item set monitor-warnings | |
17488 | @kindex set monitor-warnings@r{, MIPS remote} | |
17489 | Enable or disable monitor warnings about hardware breakpoints. This | |
17490 | has effect only for the @code{lsi} target. When on, @value{GDBN} will | |
17491 | display warning messages whose codes are returned by the @code{lsi} | |
17492 | PMON monitor for breakpoint commands. | |
17493 | ||
17494 | @item show monitor-warnings | |
17495 | @kindex show monitor-warnings@r{, MIPS remote} | |
17496 | Show the current setting of printing monitor warnings. | |
17497 | ||
17498 | @item pmon @var{command} | |
17499 | @kindex pmon@r{, MIPS remote} | |
17500 | @cindex send PMON command | |
17501 | This command allows sending an arbitrary @var{command} string to the | |
17502 | monitor. The monitor must be in debug mode for this to work. | |
8e04817f | 17503 | @end table |
104c1213 | 17504 | |
a37295f9 MM |
17505 | @node OpenRISC 1000 |
17506 | @subsection OpenRISC 1000 | |
17507 | @cindex OpenRISC 1000 | |
17508 | ||
17509 | @cindex or1k boards | |
17510 | See OR1k Architecture document (@uref{www.opencores.org}) for more information | |
17511 | about platform and commands. | |
17512 | ||
17513 | @table @code | |
17514 | ||
17515 | @kindex target jtag | |
17516 | @item target jtag jtag://@var{host}:@var{port} | |
17517 | ||
17518 | Connects to remote JTAG server. | |
17519 | JTAG remote server can be either an or1ksim or JTAG server, | |
17520 | connected via parallel port to the board. | |
17521 | ||
17522 | Example: @code{target jtag jtag://localhost:9999} | |
17523 | ||
17524 | @kindex or1ksim | |
17525 | @item or1ksim @var{command} | |
17526 | If connected to @code{or1ksim} OpenRISC 1000 Architectural | |
17527 | Simulator, proprietary commands can be executed. | |
17528 | ||
17529 | @kindex info or1k spr | |
17530 | @item info or1k spr | |
17531 | Displays spr groups. | |
17532 | ||
17533 | @item info or1k spr @var{group} | |
17534 | @itemx info or1k spr @var{groupno} | |
17535 | Displays register names in selected group. | |
17536 | ||
17537 | @item info or1k spr @var{group} @var{register} | |
17538 | @itemx info or1k spr @var{register} | |
17539 | @itemx info or1k spr @var{groupno} @var{registerno} | |
17540 | @itemx info or1k spr @var{registerno} | |
17541 | Shows information about specified spr register. | |
17542 | ||
17543 | @kindex spr | |
17544 | @item spr @var{group} @var{register} @var{value} | |
17545 | @itemx spr @var{register @var{value}} | |
17546 | @itemx spr @var{groupno} @var{registerno @var{value}} | |
17547 | @itemx spr @var{registerno @var{value}} | |
17548 | Writes @var{value} to specified spr register. | |
17549 | @end table | |
17550 | ||
17551 | Some implementations of OpenRISC 1000 Architecture also have hardware trace. | |
17552 | It is very similar to @value{GDBN} trace, except it does not interfere with normal | |
17553 | program execution and is thus much faster. Hardware breakpoints/watchpoint | |
17554 | triggers can be set using: | |
17555 | @table @code | |
17556 | @item $LEA/$LDATA | |
17557 | Load effective address/data | |
17558 | @item $SEA/$SDATA | |
17559 | Store effective address/data | |
17560 | @item $AEA/$ADATA | |
17561 | Access effective address ($SEA or $LEA) or data ($SDATA/$LDATA) | |
17562 | @item $FETCH | |
17563 | Fetch data | |
17564 | @end table | |
17565 | ||
17566 | When triggered, it can capture low level data, like: @code{PC}, @code{LSEA}, | |
17567 | @code{LDATA}, @code{SDATA}, @code{READSPR}, @code{WRITESPR}, @code{INSTR}. | |
17568 | ||
17569 | @code{htrace} commands: | |
17570 | @cindex OpenRISC 1000 htrace | |
17571 | @table @code | |
17572 | @kindex hwatch | |
17573 | @item hwatch @var{conditional} | |
d3e8051b | 17574 | Set hardware watchpoint on combination of Load/Store Effective Address(es) |
a37295f9 MM |
17575 | or Data. For example: |
17576 | ||
17577 | @code{hwatch ($LEA == my_var) && ($LDATA < 50) || ($SEA == my_var) && ($SDATA >= 50)} | |
17578 | ||
17579 | @code{hwatch ($LEA == my_var) && ($LDATA < 50) || ($SEA == my_var) && ($SDATA >= 50)} | |
17580 | ||
4644b6e3 | 17581 | @kindex htrace |
a37295f9 MM |
17582 | @item htrace info |
17583 | Display information about current HW trace configuration. | |
17584 | ||
a37295f9 MM |
17585 | @item htrace trigger @var{conditional} |
17586 | Set starting criteria for HW trace. | |
17587 | ||
a37295f9 MM |
17588 | @item htrace qualifier @var{conditional} |
17589 | Set acquisition qualifier for HW trace. | |
17590 | ||
a37295f9 MM |
17591 | @item htrace stop @var{conditional} |
17592 | Set HW trace stopping criteria. | |
17593 | ||
f153cc92 | 17594 | @item htrace record [@var{data}]* |
a37295f9 MM |
17595 | Selects the data to be recorded, when qualifier is met and HW trace was |
17596 | triggered. | |
17597 | ||
a37295f9 | 17598 | @item htrace enable |
a37295f9 MM |
17599 | @itemx htrace disable |
17600 | Enables/disables the HW trace. | |
17601 | ||
f153cc92 | 17602 | @item htrace rewind [@var{filename}] |
a37295f9 MM |
17603 | Clears currently recorded trace data. |
17604 | ||
17605 | If filename is specified, new trace file is made and any newly collected data | |
17606 | will be written there. | |
17607 | ||
f153cc92 | 17608 | @item htrace print [@var{start} [@var{len}]] |
a37295f9 MM |
17609 | Prints trace buffer, using current record configuration. |
17610 | ||
a37295f9 MM |
17611 | @item htrace mode continuous |
17612 | Set continuous trace mode. | |
17613 | ||
a37295f9 MM |
17614 | @item htrace mode suspend |
17615 | Set suspend trace mode. | |
17616 | ||
17617 | @end table | |
17618 | ||
4acd40f3 TJB |
17619 | @node PowerPC Embedded |
17620 | @subsection PowerPC Embedded | |
104c1213 | 17621 | |
55eddb0f DJ |
17622 | @value{GDBN} provides the following PowerPC-specific commands: |
17623 | ||
104c1213 | 17624 | @table @code |
55eddb0f DJ |
17625 | @kindex set powerpc |
17626 | @item set powerpc soft-float | |
17627 | @itemx show powerpc soft-float | |
17628 | Force @value{GDBN} to use (or not use) a software floating point calling | |
17629 | convention. By default, @value{GDBN} selects the calling convention based | |
17630 | on the selected architecture and the provided executable file. | |
17631 | ||
17632 | @item set powerpc vector-abi | |
17633 | @itemx show powerpc vector-abi | |
17634 | Force @value{GDBN} to use the specified calling convention for vector | |
17635 | arguments and return values. The valid options are @samp{auto}; | |
17636 | @samp{generic}, to avoid vector registers even if they are present; | |
17637 | @samp{altivec}, to use AltiVec registers; and @samp{spe} to use SPE | |
17638 | registers. By default, @value{GDBN} selects the calling convention | |
17639 | based on the selected architecture and the provided executable file. | |
17640 | ||
8e04817f AC |
17641 | @kindex target dink32 |
17642 | @item target dink32 @var{dev} | |
17643 | DINK32 ROM monitor. | |
104c1213 | 17644 | |
8e04817f AC |
17645 | @kindex target ppcbug |
17646 | @item target ppcbug @var{dev} | |
17647 | @kindex target ppcbug1 | |
17648 | @item target ppcbug1 @var{dev} | |
17649 | PPCBUG ROM monitor for PowerPC. | |
104c1213 | 17650 | |
8e04817f AC |
17651 | @kindex target sds |
17652 | @item target sds @var{dev} | |
17653 | SDS monitor, running on a PowerPC board (such as Motorola's ADS). | |
c45da7e6 | 17654 | @end table |
8e04817f | 17655 | |
c45da7e6 | 17656 | @cindex SDS protocol |
d52fb0e9 | 17657 | The following commands specific to the SDS protocol are supported |
55eddb0f | 17658 | by @value{GDBN}: |
c45da7e6 EZ |
17659 | |
17660 | @table @code | |
17661 | @item set sdstimeout @var{nsec} | |
17662 | @kindex set sdstimeout | |
17663 | Set the timeout for SDS protocol reads to be @var{nsec} seconds. The | |
17664 | default is 2 seconds. | |
17665 | ||
17666 | @item show sdstimeout | |
17667 | @kindex show sdstimeout | |
17668 | Show the current value of the SDS timeout. | |
17669 | ||
17670 | @item sds @var{command} | |
17671 | @kindex sds@r{, a command} | |
17672 | Send the specified @var{command} string to the SDS monitor. | |
8e04817f AC |
17673 | @end table |
17674 | ||
c45da7e6 | 17675 | |
8e04817f AC |
17676 | @node PA |
17677 | @subsection HP PA Embedded | |
104c1213 JM |
17678 | |
17679 | @table @code | |
17680 | ||
8e04817f AC |
17681 | @kindex target op50n |
17682 | @item target op50n @var{dev} | |
17683 | OP50N monitor, running on an OKI HPPA board. | |
17684 | ||
17685 | @kindex target w89k | |
17686 | @item target w89k @var{dev} | |
17687 | W89K monitor, running on a Winbond HPPA board. | |
104c1213 JM |
17688 | |
17689 | @end table | |
17690 | ||
8e04817f AC |
17691 | @node Sparclet |
17692 | @subsection Tsqware Sparclet | |
104c1213 | 17693 | |
8e04817f AC |
17694 | @cindex Sparclet |
17695 | ||
17696 | @value{GDBN} enables developers to debug tasks running on | |
17697 | Sparclet targets from a Unix host. | |
17698 | @value{GDBN} uses code that runs on | |
17699 | both the Unix host and on the Sparclet target. The program | |
17700 | @code{@value{GDBP}} is installed and executed on the Unix host. | |
104c1213 | 17701 | |
8e04817f AC |
17702 | @table @code |
17703 | @item remotetimeout @var{args} | |
17704 | @kindex remotetimeout | |
17705 | @value{GDBN} supports the option @code{remotetimeout}. | |
17706 | This option is set by the user, and @var{args} represents the number of | |
17707 | seconds @value{GDBN} waits for responses. | |
104c1213 JM |
17708 | @end table |
17709 | ||
8e04817f AC |
17710 | @cindex compiling, on Sparclet |
17711 | When compiling for debugging, include the options @samp{-g} to get debug | |
17712 | information and @samp{-Ttext} to relocate the program to where you wish to | |
17713 | load it on the target. You may also want to add the options @samp{-n} or | |
17714 | @samp{-N} in order to reduce the size of the sections. Example: | |
104c1213 | 17715 | |
474c8240 | 17716 | @smallexample |
8e04817f | 17717 | sparclet-aout-gcc prog.c -Ttext 0x12010000 -g -o prog -N |
474c8240 | 17718 | @end smallexample |
104c1213 | 17719 | |
8e04817f | 17720 | You can use @code{objdump} to verify that the addresses are what you intended: |
104c1213 | 17721 | |
474c8240 | 17722 | @smallexample |
8e04817f | 17723 | sparclet-aout-objdump --headers --syms prog |
474c8240 | 17724 | @end smallexample |
104c1213 | 17725 | |
8e04817f AC |
17726 | @cindex running, on Sparclet |
17727 | Once you have set | |
17728 | your Unix execution search path to find @value{GDBN}, you are ready to | |
17729 | run @value{GDBN}. From your Unix host, run @code{@value{GDBP}} | |
17730 | (or @code{sparclet-aout-gdb}, depending on your installation). | |
104c1213 | 17731 | |
8e04817f AC |
17732 | @value{GDBN} comes up showing the prompt: |
17733 | ||
474c8240 | 17734 | @smallexample |
8e04817f | 17735 | (gdbslet) |
474c8240 | 17736 | @end smallexample |
104c1213 JM |
17737 | |
17738 | @menu | |
8e04817f AC |
17739 | * Sparclet File:: Setting the file to debug |
17740 | * Sparclet Connection:: Connecting to Sparclet | |
17741 | * Sparclet Download:: Sparclet download | |
17742 | * Sparclet Execution:: Running and debugging | |
104c1213 JM |
17743 | @end menu |
17744 | ||
8e04817f | 17745 | @node Sparclet File |
79a6e687 | 17746 | @subsubsection Setting File to Debug |
104c1213 | 17747 | |
8e04817f | 17748 | The @value{GDBN} command @code{file} lets you choose with program to debug. |
104c1213 | 17749 | |
474c8240 | 17750 | @smallexample |
8e04817f | 17751 | (gdbslet) file prog |
474c8240 | 17752 | @end smallexample |
104c1213 | 17753 | |
8e04817f AC |
17754 | @need 1000 |
17755 | @value{GDBN} then attempts to read the symbol table of @file{prog}. | |
17756 | @value{GDBN} locates | |
17757 | the file by searching the directories listed in the command search | |
17758 | path. | |
12c27660 | 17759 | If the file was compiled with debug information (option @samp{-g}), source |
8e04817f AC |
17760 | files will be searched as well. |
17761 | @value{GDBN} locates | |
17762 | the source files by searching the directories listed in the directory search | |
79a6e687 | 17763 | path (@pxref{Environment, ,Your Program's Environment}). |
8e04817f AC |
17764 | If it fails |
17765 | to find a file, it displays a message such as: | |
104c1213 | 17766 | |
474c8240 | 17767 | @smallexample |
8e04817f | 17768 | prog: No such file or directory. |
474c8240 | 17769 | @end smallexample |
104c1213 | 17770 | |
8e04817f AC |
17771 | When this happens, add the appropriate directories to the search paths with |
17772 | the @value{GDBN} commands @code{path} and @code{dir}, and execute the | |
17773 | @code{target} command again. | |
104c1213 | 17774 | |
8e04817f AC |
17775 | @node Sparclet Connection |
17776 | @subsubsection Connecting to Sparclet | |
104c1213 | 17777 | |
8e04817f AC |
17778 | The @value{GDBN} command @code{target} lets you connect to a Sparclet target. |
17779 | To connect to a target on serial port ``@code{ttya}'', type: | |
104c1213 | 17780 | |
474c8240 | 17781 | @smallexample |
8e04817f AC |
17782 | (gdbslet) target sparclet /dev/ttya |
17783 | Remote target sparclet connected to /dev/ttya | |
17784 | main () at ../prog.c:3 | |
474c8240 | 17785 | @end smallexample |
104c1213 | 17786 | |
8e04817f AC |
17787 | @need 750 |
17788 | @value{GDBN} displays messages like these: | |
104c1213 | 17789 | |
474c8240 | 17790 | @smallexample |
8e04817f | 17791 | Connected to ttya. |
474c8240 | 17792 | @end smallexample |
104c1213 | 17793 | |
8e04817f | 17794 | @node Sparclet Download |
79a6e687 | 17795 | @subsubsection Sparclet Download |
104c1213 | 17796 | |
8e04817f AC |
17797 | @cindex download to Sparclet |
17798 | Once connected to the Sparclet target, | |
17799 | you can use the @value{GDBN} | |
17800 | @code{load} command to download the file from the host to the target. | |
17801 | The file name and load offset should be given as arguments to the @code{load} | |
17802 | command. | |
17803 | Since the file format is aout, the program must be loaded to the starting | |
17804 | address. You can use @code{objdump} to find out what this value is. The load | |
17805 | offset is an offset which is added to the VMA (virtual memory address) | |
17806 | of each of the file's sections. | |
17807 | For instance, if the program | |
17808 | @file{prog} was linked to text address 0x1201000, with data at 0x12010160 | |
17809 | and bss at 0x12010170, in @value{GDBN}, type: | |
104c1213 | 17810 | |
474c8240 | 17811 | @smallexample |
8e04817f AC |
17812 | (gdbslet) load prog 0x12010000 |
17813 | Loading section .text, size 0xdb0 vma 0x12010000 | |
474c8240 | 17814 | @end smallexample |
104c1213 | 17815 | |
8e04817f AC |
17816 | If the code is loaded at a different address then what the program was linked |
17817 | to, you may need to use the @code{section} and @code{add-symbol-file} commands | |
17818 | to tell @value{GDBN} where to map the symbol table. | |
17819 | ||
17820 | @node Sparclet Execution | |
79a6e687 | 17821 | @subsubsection Running and Debugging |
8e04817f AC |
17822 | |
17823 | @cindex running and debugging Sparclet programs | |
17824 | You can now begin debugging the task using @value{GDBN}'s execution control | |
17825 | commands, @code{b}, @code{step}, @code{run}, etc. See the @value{GDBN} | |
17826 | manual for the list of commands. | |
17827 | ||
474c8240 | 17828 | @smallexample |
8e04817f AC |
17829 | (gdbslet) b main |
17830 | Breakpoint 1 at 0x12010000: file prog.c, line 3. | |
17831 | (gdbslet) run | |
17832 | Starting program: prog | |
17833 | Breakpoint 1, main (argc=1, argv=0xeffff21c) at prog.c:3 | |
17834 | 3 char *symarg = 0; | |
17835 | (gdbslet) step | |
17836 | 4 char *execarg = "hello!"; | |
17837 | (gdbslet) | |
474c8240 | 17838 | @end smallexample |
8e04817f AC |
17839 | |
17840 | @node Sparclite | |
17841 | @subsection Fujitsu Sparclite | |
104c1213 JM |
17842 | |
17843 | @table @code | |
17844 | ||
8e04817f AC |
17845 | @kindex target sparclite |
17846 | @item target sparclite @var{dev} | |
17847 | Fujitsu sparclite boards, used only for the purpose of loading. | |
17848 | You must use an additional command to debug the program. | |
17849 | For example: target remote @var{dev} using @value{GDBN} standard | |
17850 | remote protocol. | |
104c1213 JM |
17851 | |
17852 | @end table | |
17853 | ||
8e04817f AC |
17854 | @node Z8000 |
17855 | @subsection Zilog Z8000 | |
104c1213 | 17856 | |
8e04817f AC |
17857 | @cindex Z8000 |
17858 | @cindex simulator, Z8000 | |
17859 | @cindex Zilog Z8000 simulator | |
104c1213 | 17860 | |
8e04817f AC |
17861 | When configured for debugging Zilog Z8000 targets, @value{GDBN} includes |
17862 | a Z8000 simulator. | |
17863 | ||
17864 | For the Z8000 family, @samp{target sim} simulates either the Z8002 (the | |
17865 | unsegmented variant of the Z8000 architecture) or the Z8001 (the | |
17866 | segmented variant). The simulator recognizes which architecture is | |
17867 | appropriate by inspecting the object code. | |
104c1213 | 17868 | |
8e04817f AC |
17869 | @table @code |
17870 | @item target sim @var{args} | |
17871 | @kindex sim | |
17872 | @kindex target sim@r{, with Z8000} | |
17873 | Debug programs on a simulated CPU. If the simulator supports setup | |
17874 | options, specify them via @var{args}. | |
104c1213 JM |
17875 | @end table |
17876 | ||
8e04817f AC |
17877 | @noindent |
17878 | After specifying this target, you can debug programs for the simulated | |
17879 | CPU in the same style as programs for your host computer; use the | |
17880 | @code{file} command to load a new program image, the @code{run} command | |
17881 | to run your program, and so on. | |
17882 | ||
17883 | As well as making available all the usual machine registers | |
17884 | (@pxref{Registers, ,Registers}), the Z8000 simulator provides three | |
17885 | additional items of information as specially named registers: | |
104c1213 JM |
17886 | |
17887 | @table @code | |
17888 | ||
8e04817f AC |
17889 | @item cycles |
17890 | Counts clock-ticks in the simulator. | |
104c1213 | 17891 | |
8e04817f AC |
17892 | @item insts |
17893 | Counts instructions run in the simulator. | |
104c1213 | 17894 | |
8e04817f AC |
17895 | @item time |
17896 | Execution time in 60ths of a second. | |
104c1213 | 17897 | |
8e04817f | 17898 | @end table |
104c1213 | 17899 | |
8e04817f AC |
17900 | You can refer to these values in @value{GDBN} expressions with the usual |
17901 | conventions; for example, @w{@samp{b fputc if $cycles>5000}} sets a | |
17902 | conditional breakpoint that suspends only after at least 5000 | |
17903 | simulated clock ticks. | |
104c1213 | 17904 | |
a64548ea EZ |
17905 | @node AVR |
17906 | @subsection Atmel AVR | |
17907 | @cindex AVR | |
17908 | ||
17909 | When configured for debugging the Atmel AVR, @value{GDBN} supports the | |
17910 | following AVR-specific commands: | |
17911 | ||
17912 | @table @code | |
17913 | @item info io_registers | |
17914 | @kindex info io_registers@r{, AVR} | |
17915 | @cindex I/O registers (Atmel AVR) | |
17916 | This command displays information about the AVR I/O registers. For | |
17917 | each register, @value{GDBN} prints its number and value. | |
17918 | @end table | |
17919 | ||
17920 | @node CRIS | |
17921 | @subsection CRIS | |
17922 | @cindex CRIS | |
17923 | ||
17924 | When configured for debugging CRIS, @value{GDBN} provides the | |
17925 | following CRIS-specific commands: | |
17926 | ||
17927 | @table @code | |
17928 | @item set cris-version @var{ver} | |
17929 | @cindex CRIS version | |
e22e55c9 OF |
17930 | Set the current CRIS version to @var{ver}, either @samp{10} or @samp{32}. |
17931 | The CRIS version affects register names and sizes. This command is useful in | |
17932 | case autodetection of the CRIS version fails. | |
a64548ea EZ |
17933 | |
17934 | @item show cris-version | |
17935 | Show the current CRIS version. | |
17936 | ||
17937 | @item set cris-dwarf2-cfi | |
17938 | @cindex DWARF-2 CFI and CRIS | |
e22e55c9 OF |
17939 | Set the usage of DWARF-2 CFI for CRIS debugging. The default is @samp{on}. |
17940 | Change to @samp{off} when using @code{gcc-cris} whose version is below | |
17941 | @code{R59}. | |
a64548ea EZ |
17942 | |
17943 | @item show cris-dwarf2-cfi | |
17944 | Show the current state of using DWARF-2 CFI. | |
e22e55c9 OF |
17945 | |
17946 | @item set cris-mode @var{mode} | |
17947 | @cindex CRIS mode | |
17948 | Set the current CRIS mode to @var{mode}. It should only be changed when | |
17949 | debugging in guru mode, in which case it should be set to | |
17950 | @samp{guru} (the default is @samp{normal}). | |
17951 | ||
17952 | @item show cris-mode | |
17953 | Show the current CRIS mode. | |
a64548ea EZ |
17954 | @end table |
17955 | ||
17956 | @node Super-H | |
17957 | @subsection Renesas Super-H | |
17958 | @cindex Super-H | |
17959 | ||
17960 | For the Renesas Super-H processor, @value{GDBN} provides these | |
17961 | commands: | |
17962 | ||
17963 | @table @code | |
17964 | @item regs | |
17965 | @kindex regs@r{, Super-H} | |
17966 | Show the values of all Super-H registers. | |
c055b101 CV |
17967 | |
17968 | @item set sh calling-convention @var{convention} | |
17969 | @kindex set sh calling-convention | |
17970 | Set the calling-convention used when calling functions from @value{GDBN}. | |
17971 | Allowed values are @samp{gcc}, which is the default setting, and @samp{renesas}. | |
17972 | With the @samp{gcc} setting, functions are called using the @value{NGCC} calling | |
17973 | convention. If the DWARF-2 information of the called function specifies | |
17974 | that the function follows the Renesas calling convention, the function | |
17975 | is called using the Renesas calling convention. If the calling convention | |
17976 | is set to @samp{renesas}, the Renesas calling convention is always used, | |
17977 | regardless of the DWARF-2 information. This can be used to override the | |
17978 | default of @samp{gcc} if debug information is missing, or the compiler | |
17979 | does not emit the DWARF-2 calling convention entry for a function. | |
17980 | ||
17981 | @item show sh calling-convention | |
17982 | @kindex show sh calling-convention | |
17983 | Show the current calling convention setting. | |
17984 | ||
a64548ea EZ |
17985 | @end table |
17986 | ||
17987 | ||
8e04817f AC |
17988 | @node Architectures |
17989 | @section Architectures | |
104c1213 | 17990 | |
8e04817f AC |
17991 | This section describes characteristics of architectures that affect |
17992 | all uses of @value{GDBN} with the architecture, both native and cross. | |
104c1213 | 17993 | |
8e04817f | 17994 | @menu |
9c16f35a | 17995 | * i386:: |
8e04817f AC |
17996 | * A29K:: |
17997 | * Alpha:: | |
17998 | * MIPS:: | |
a64548ea | 17999 | * HPPA:: HP PA architecture |
23d964e7 | 18000 | * SPU:: Cell Broadband Engine SPU architecture |
4acd40f3 | 18001 | * PowerPC:: |
8e04817f | 18002 | @end menu |
104c1213 | 18003 | |
9c16f35a | 18004 | @node i386 |
db2e3e2e | 18005 | @subsection x86 Architecture-specific Issues |
9c16f35a EZ |
18006 | |
18007 | @table @code | |
18008 | @item set struct-convention @var{mode} | |
18009 | @kindex set struct-convention | |
18010 | @cindex struct return convention | |
18011 | @cindex struct/union returned in registers | |
18012 | Set the convention used by the inferior to return @code{struct}s and | |
18013 | @code{union}s from functions to @var{mode}. Possible values of | |
18014 | @var{mode} are @code{"pcc"}, @code{"reg"}, and @code{"default"} (the | |
18015 | default). @code{"default"} or @code{"pcc"} means that @code{struct}s | |
18016 | are returned on the stack, while @code{"reg"} means that a | |
18017 | @code{struct} or a @code{union} whose size is 1, 2, 4, or 8 bytes will | |
18018 | be returned in a register. | |
18019 | ||
18020 | @item show struct-convention | |
18021 | @kindex show struct-convention | |
18022 | Show the current setting of the convention to return @code{struct}s | |
18023 | from functions. | |
18024 | @end table | |
18025 | ||
8e04817f AC |
18026 | @node A29K |
18027 | @subsection A29K | |
104c1213 JM |
18028 | |
18029 | @table @code | |
104c1213 | 18030 | |
8e04817f AC |
18031 | @kindex set rstack_high_address |
18032 | @cindex AMD 29K register stack | |
18033 | @cindex register stack, AMD29K | |
18034 | @item set rstack_high_address @var{address} | |
18035 | On AMD 29000 family processors, registers are saved in a separate | |
18036 | @dfn{register stack}. There is no way for @value{GDBN} to determine the | |
18037 | extent of this stack. Normally, @value{GDBN} just assumes that the | |
18038 | stack is ``large enough''. This may result in @value{GDBN} referencing | |
18039 | memory locations that do not exist. If necessary, you can get around | |
18040 | this problem by specifying the ending address of the register stack with | |
18041 | the @code{set rstack_high_address} command. The argument should be an | |
18042 | address, which you probably want to precede with @samp{0x} to specify in | |
18043 | hexadecimal. | |
104c1213 | 18044 | |
8e04817f AC |
18045 | @kindex show rstack_high_address |
18046 | @item show rstack_high_address | |
18047 | Display the current limit of the register stack, on AMD 29000 family | |
18048 | processors. | |
104c1213 | 18049 | |
8e04817f | 18050 | @end table |
104c1213 | 18051 | |
8e04817f AC |
18052 | @node Alpha |
18053 | @subsection Alpha | |
104c1213 | 18054 | |
8e04817f | 18055 | See the following section. |
104c1213 | 18056 | |
8e04817f AC |
18057 | @node MIPS |
18058 | @subsection MIPS | |
104c1213 | 18059 | |
8e04817f AC |
18060 | @cindex stack on Alpha |
18061 | @cindex stack on MIPS | |
18062 | @cindex Alpha stack | |
18063 | @cindex MIPS stack | |
18064 | Alpha- and MIPS-based computers use an unusual stack frame, which | |
18065 | sometimes requires @value{GDBN} to search backward in the object code to | |
18066 | find the beginning of a function. | |
104c1213 | 18067 | |
8e04817f AC |
18068 | @cindex response time, MIPS debugging |
18069 | To improve response time (especially for embedded applications, where | |
18070 | @value{GDBN} may be restricted to a slow serial line for this search) | |
18071 | you may want to limit the size of this search, using one of these | |
18072 | commands: | |
104c1213 | 18073 | |
8e04817f AC |
18074 | @table @code |
18075 | @cindex @code{heuristic-fence-post} (Alpha, MIPS) | |
18076 | @item set heuristic-fence-post @var{limit} | |
18077 | Restrict @value{GDBN} to examining at most @var{limit} bytes in its | |
18078 | search for the beginning of a function. A value of @var{0} (the | |
18079 | default) means there is no limit. However, except for @var{0}, the | |
18080 | larger the limit the more bytes @code{heuristic-fence-post} must search | |
e2f4edfd EZ |
18081 | and therefore the longer it takes to run. You should only need to use |
18082 | this command when debugging a stripped executable. | |
104c1213 | 18083 | |
8e04817f AC |
18084 | @item show heuristic-fence-post |
18085 | Display the current limit. | |
18086 | @end table | |
104c1213 JM |
18087 | |
18088 | @noindent | |
8e04817f AC |
18089 | These commands are available @emph{only} when @value{GDBN} is configured |
18090 | for debugging programs on Alpha or MIPS processors. | |
104c1213 | 18091 | |
a64548ea EZ |
18092 | Several MIPS-specific commands are available when debugging MIPS |
18093 | programs: | |
18094 | ||
18095 | @table @code | |
a64548ea EZ |
18096 | @item set mips abi @var{arg} |
18097 | @kindex set mips abi | |
18098 | @cindex set ABI for MIPS | |
18099 | Tell @value{GDBN} which MIPS ABI is used by the inferior. Possible | |
18100 | values of @var{arg} are: | |
18101 | ||
18102 | @table @samp | |
18103 | @item auto | |
18104 | The default ABI associated with the current binary (this is the | |
18105 | default). | |
18106 | @item o32 | |
18107 | @item o64 | |
18108 | @item n32 | |
18109 | @item n64 | |
18110 | @item eabi32 | |
18111 | @item eabi64 | |
18112 | @item auto | |
18113 | @end table | |
18114 | ||
18115 | @item show mips abi | |
18116 | @kindex show mips abi | |
18117 | Show the MIPS ABI used by @value{GDBN} to debug the inferior. | |
18118 | ||
18119 | @item set mipsfpu | |
18120 | @itemx show mipsfpu | |
18121 | @xref{MIPS Embedded, set mipsfpu}. | |
18122 | ||
18123 | @item set mips mask-address @var{arg} | |
18124 | @kindex set mips mask-address | |
18125 | @cindex MIPS addresses, masking | |
18126 | This command determines whether the most-significant 32 bits of 64-bit | |
18127 | MIPS addresses are masked off. The argument @var{arg} can be | |
18128 | @samp{on}, @samp{off}, or @samp{auto}. The latter is the default | |
18129 | setting, which lets @value{GDBN} determine the correct value. | |
18130 | ||
18131 | @item show mips mask-address | |
18132 | @kindex show mips mask-address | |
18133 | Show whether the upper 32 bits of MIPS addresses are masked off or | |
18134 | not. | |
18135 | ||
18136 | @item set remote-mips64-transfers-32bit-regs | |
18137 | @kindex set remote-mips64-transfers-32bit-regs | |
18138 | This command controls compatibility with 64-bit MIPS targets that | |
18139 | transfer data in 32-bit quantities. If you have an old MIPS 64 target | |
18140 | that transfers 32 bits for some registers, like @sc{sr} and @sc{fsr}, | |
18141 | and 64 bits for other registers, set this option to @samp{on}. | |
18142 | ||
18143 | @item show remote-mips64-transfers-32bit-regs | |
18144 | @kindex show remote-mips64-transfers-32bit-regs | |
18145 | Show the current setting of compatibility with older MIPS 64 targets. | |
18146 | ||
18147 | @item set debug mips | |
18148 | @kindex set debug mips | |
18149 | This command turns on and off debugging messages for the MIPS-specific | |
18150 | target code in @value{GDBN}. | |
18151 | ||
18152 | @item show debug mips | |
18153 | @kindex show debug mips | |
18154 | Show the current setting of MIPS debugging messages. | |
18155 | @end table | |
18156 | ||
18157 | ||
18158 | @node HPPA | |
18159 | @subsection HPPA | |
18160 | @cindex HPPA support | |
18161 | ||
d3e8051b | 18162 | When @value{GDBN} is debugging the HP PA architecture, it provides the |
a64548ea EZ |
18163 | following special commands: |
18164 | ||
18165 | @table @code | |
18166 | @item set debug hppa | |
18167 | @kindex set debug hppa | |
db2e3e2e | 18168 | This command determines whether HPPA architecture-specific debugging |
a64548ea EZ |
18169 | messages are to be displayed. |
18170 | ||
18171 | @item show debug hppa | |
18172 | Show whether HPPA debugging messages are displayed. | |
18173 | ||
18174 | @item maint print unwind @var{address} | |
18175 | @kindex maint print unwind@r{, HPPA} | |
18176 | This command displays the contents of the unwind table entry at the | |
18177 | given @var{address}. | |
18178 | ||
18179 | @end table | |
18180 | ||
104c1213 | 18181 | |
23d964e7 UW |
18182 | @node SPU |
18183 | @subsection Cell Broadband Engine SPU architecture | |
18184 | @cindex Cell Broadband Engine | |
18185 | @cindex SPU | |
18186 | ||
18187 | When @value{GDBN} is debugging the Cell Broadband Engine SPU architecture, | |
18188 | it provides the following special commands: | |
18189 | ||
18190 | @table @code | |
18191 | @item info spu event | |
18192 | @kindex info spu | |
18193 | Display SPU event facility status. Shows current event mask | |
18194 | and pending event status. | |
18195 | ||
18196 | @item info spu signal | |
18197 | Display SPU signal notification facility status. Shows pending | |
18198 | signal-control word and signal notification mode of both signal | |
18199 | notification channels. | |
18200 | ||
18201 | @item info spu mailbox | |
18202 | Display SPU mailbox facility status. Shows all pending entries, | |
18203 | in order of processing, in each of the SPU Write Outbound, | |
18204 | SPU Write Outbound Interrupt, and SPU Read Inbound mailboxes. | |
18205 | ||
18206 | @item info spu dma | |
18207 | Display MFC DMA status. Shows all pending commands in the MFC | |
18208 | DMA queue. For each entry, opcode, tag, class IDs, effective | |
18209 | and local store addresses and transfer size are shown. | |
18210 | ||
18211 | @item info spu proxydma | |
18212 | Display MFC Proxy-DMA status. Shows all pending commands in the MFC | |
18213 | Proxy-DMA queue. For each entry, opcode, tag, class IDs, effective | |
18214 | and local store addresses and transfer size are shown. | |
18215 | ||
18216 | @end table | |
18217 | ||
3285f3fe UW |
18218 | When @value{GDBN} is debugging a combined PowerPC/SPU application |
18219 | on the Cell Broadband Engine, it provides in addition the following | |
18220 | special commands: | |
18221 | ||
18222 | @table @code | |
18223 | @item set spu stop-on-load @var{arg} | |
18224 | @kindex set spu | |
18225 | Set whether to stop for new SPE threads. When set to @code{on}, @value{GDBN} | |
18226 | will give control to the user when a new SPE thread enters its @code{main} | |
18227 | function. The default is @code{off}. | |
18228 | ||
18229 | @item show spu stop-on-load | |
18230 | @kindex show spu | |
18231 | Show whether to stop for new SPE threads. | |
18232 | ||
ff1a52c6 UW |
18233 | @item set spu auto-flush-cache @var{arg} |
18234 | Set whether to automatically flush the software-managed cache. When set to | |
18235 | @code{on}, @value{GDBN} will automatically cause the SPE software-managed | |
18236 | cache to be flushed whenever SPE execution stops. This provides a consistent | |
18237 | view of PowerPC memory that is accessed via the cache. If an application | |
18238 | does not use the software-managed cache, this option has no effect. | |
18239 | ||
18240 | @item show spu auto-flush-cache | |
18241 | Show whether to automatically flush the software-managed cache. | |
18242 | ||
3285f3fe UW |
18243 | @end table |
18244 | ||
4acd40f3 TJB |
18245 | @node PowerPC |
18246 | @subsection PowerPC | |
18247 | @cindex PowerPC architecture | |
18248 | ||
18249 | When @value{GDBN} is debugging the PowerPC architecture, it provides a set of | |
18250 | pseudo-registers to enable inspection of 128-bit wide Decimal Floating Point | |
18251 | numbers stored in the floating point registers. These values must be stored | |
18252 | in two consecutive registers, always starting at an even register like | |
18253 | @code{f0} or @code{f2}. | |
18254 | ||
18255 | The pseudo-registers go from @code{$dl0} through @code{$dl15}, and are formed | |
18256 | by joining the even/odd register pairs @code{f0} and @code{f1} for @code{$dl0}, | |
18257 | @code{f2} and @code{f3} for @code{$dl1} and so on. | |
18258 | ||
aeac0ff9 | 18259 | For POWER7 processors, @value{GDBN} provides a set of pseudo-registers, the 64-bit |
677c5bb1 LM |
18260 | wide Extended Floating Point Registers (@samp{f32} through @samp{f63}). |
18261 | ||
23d964e7 | 18262 | |
8e04817f AC |
18263 | @node Controlling GDB |
18264 | @chapter Controlling @value{GDBN} | |
18265 | ||
18266 | You can alter the way @value{GDBN} interacts with you by using the | |
18267 | @code{set} command. For commands controlling how @value{GDBN} displays | |
79a6e687 | 18268 | data, see @ref{Print Settings, ,Print Settings}. Other settings are |
8e04817f AC |
18269 | described here. |
18270 | ||
18271 | @menu | |
18272 | * Prompt:: Prompt | |
18273 | * Editing:: Command editing | |
d620b259 | 18274 | * Command History:: Command history |
8e04817f AC |
18275 | * Screen Size:: Screen size |
18276 | * Numbers:: Numbers | |
1e698235 | 18277 | * ABI:: Configuring the current ABI |
8e04817f AC |
18278 | * Messages/Warnings:: Optional warnings and messages |
18279 | * Debugging Output:: Optional messages about internal happenings | |
14fb1bac | 18280 | * Other Misc Settings:: Other Miscellaneous Settings |
8e04817f AC |
18281 | @end menu |
18282 | ||
18283 | @node Prompt | |
18284 | @section Prompt | |
104c1213 | 18285 | |
8e04817f | 18286 | @cindex prompt |
104c1213 | 18287 | |
8e04817f AC |
18288 | @value{GDBN} indicates its readiness to read a command by printing a string |
18289 | called the @dfn{prompt}. This string is normally @samp{(@value{GDBP})}. You | |
18290 | can change the prompt string with the @code{set prompt} command. For | |
18291 | instance, when debugging @value{GDBN} with @value{GDBN}, it is useful to change | |
18292 | the prompt in one of the @value{GDBN} sessions so that you can always tell | |
18293 | which one you are talking to. | |
104c1213 | 18294 | |
8e04817f AC |
18295 | @emph{Note:} @code{set prompt} does not add a space for you after the |
18296 | prompt you set. This allows you to set a prompt which ends in a space | |
18297 | or a prompt that does not. | |
104c1213 | 18298 | |
8e04817f AC |
18299 | @table @code |
18300 | @kindex set prompt | |
18301 | @item set prompt @var{newprompt} | |
18302 | Directs @value{GDBN} to use @var{newprompt} as its prompt string henceforth. | |
104c1213 | 18303 | |
8e04817f AC |
18304 | @kindex show prompt |
18305 | @item show prompt | |
18306 | Prints a line of the form: @samp{Gdb's prompt is: @var{your-prompt}} | |
104c1213 JM |
18307 | @end table |
18308 | ||
8e04817f | 18309 | @node Editing |
79a6e687 | 18310 | @section Command Editing |
8e04817f AC |
18311 | @cindex readline |
18312 | @cindex command line editing | |
104c1213 | 18313 | |
703663ab | 18314 | @value{GDBN} reads its input commands via the @dfn{Readline} interface. This |
8e04817f AC |
18315 | @sc{gnu} library provides consistent behavior for programs which provide a |
18316 | command line interface to the user. Advantages are @sc{gnu} Emacs-style | |
18317 | or @dfn{vi}-style inline editing of commands, @code{csh}-like history | |
18318 | substitution, and a storage and recall of command history across | |
18319 | debugging sessions. | |
104c1213 | 18320 | |
8e04817f AC |
18321 | You may control the behavior of command line editing in @value{GDBN} with the |
18322 | command @code{set}. | |
104c1213 | 18323 | |
8e04817f AC |
18324 | @table @code |
18325 | @kindex set editing | |
18326 | @cindex editing | |
18327 | @item set editing | |
18328 | @itemx set editing on | |
18329 | Enable command line editing (enabled by default). | |
104c1213 | 18330 | |
8e04817f AC |
18331 | @item set editing off |
18332 | Disable command line editing. | |
104c1213 | 18333 | |
8e04817f AC |
18334 | @kindex show editing |
18335 | @item show editing | |
18336 | Show whether command line editing is enabled. | |
104c1213 JM |
18337 | @end table |
18338 | ||
703663ab EZ |
18339 | @xref{Command Line Editing}, for more details about the Readline |
18340 | interface. Users unfamiliar with @sc{gnu} Emacs or @code{vi} are | |
18341 | encouraged to read that chapter. | |
18342 | ||
d620b259 | 18343 | @node Command History |
79a6e687 | 18344 | @section Command History |
703663ab | 18345 | @cindex command history |
8e04817f AC |
18346 | |
18347 | @value{GDBN} can keep track of the commands you type during your | |
18348 | debugging sessions, so that you can be certain of precisely what | |
18349 | happened. Use these commands to manage the @value{GDBN} command | |
18350 | history facility. | |
104c1213 | 18351 | |
703663ab EZ |
18352 | @value{GDBN} uses the @sc{gnu} History library, a part of the Readline |
18353 | package, to provide the history facility. @xref{Using History | |
18354 | Interactively}, for the detailed description of the History library. | |
18355 | ||
d620b259 | 18356 | To issue a command to @value{GDBN} without affecting certain aspects of |
9e6c4bd5 NR |
18357 | the state which is seen by users, prefix it with @samp{server } |
18358 | (@pxref{Server Prefix}). This | |
d620b259 NR |
18359 | means that this command will not affect the command history, nor will it |
18360 | affect @value{GDBN}'s notion of which command to repeat if @key{RET} is | |
18361 | pressed on a line by itself. | |
18362 | ||
18363 | @cindex @code{server}, command prefix | |
18364 | The server prefix does not affect the recording of values into the value | |
18365 | history; to print a value without recording it into the value history, | |
18366 | use the @code{output} command instead of the @code{print} command. | |
18367 | ||
703663ab EZ |
18368 | Here is the description of @value{GDBN} commands related to command |
18369 | history. | |
18370 | ||
104c1213 | 18371 | @table @code |
8e04817f AC |
18372 | @cindex history substitution |
18373 | @cindex history file | |
18374 | @kindex set history filename | |
4644b6e3 | 18375 | @cindex @env{GDBHISTFILE}, environment variable |
8e04817f AC |
18376 | @item set history filename @var{fname} |
18377 | Set the name of the @value{GDBN} command history file to @var{fname}. | |
18378 | This is the file where @value{GDBN} reads an initial command history | |
18379 | list, and where it writes the command history from this session when it | |
18380 | exits. You can access this list through history expansion or through | |
18381 | the history command editing characters listed below. This file defaults | |
18382 | to the value of the environment variable @code{GDBHISTFILE}, or to | |
18383 | @file{./.gdb_history} (@file{./_gdb_history} on MS-DOS) if this variable | |
18384 | is not set. | |
104c1213 | 18385 | |
9c16f35a EZ |
18386 | @cindex save command history |
18387 | @kindex set history save | |
8e04817f AC |
18388 | @item set history save |
18389 | @itemx set history save on | |
18390 | Record command history in a file, whose name may be specified with the | |
18391 | @code{set history filename} command. By default, this option is disabled. | |
104c1213 | 18392 | |
8e04817f AC |
18393 | @item set history save off |
18394 | Stop recording command history in a file. | |
104c1213 | 18395 | |
8e04817f | 18396 | @cindex history size |
9c16f35a | 18397 | @kindex set history size |
6fc08d32 | 18398 | @cindex @env{HISTSIZE}, environment variable |
8e04817f AC |
18399 | @item set history size @var{size} |
18400 | Set the number of commands which @value{GDBN} keeps in its history list. | |
18401 | This defaults to the value of the environment variable | |
18402 | @code{HISTSIZE}, or to 256 if this variable is not set. | |
104c1213 JM |
18403 | @end table |
18404 | ||
8e04817f | 18405 | History expansion assigns special meaning to the character @kbd{!}. |
703663ab | 18406 | @xref{Event Designators}, for more details. |
8e04817f | 18407 | |
703663ab | 18408 | @cindex history expansion, turn on/off |
8e04817f AC |
18409 | Since @kbd{!} is also the logical not operator in C, history expansion |
18410 | is off by default. If you decide to enable history expansion with the | |
18411 | @code{set history expansion on} command, you may sometimes need to | |
18412 | follow @kbd{!} (when it is used as logical not, in an expression) with | |
18413 | a space or a tab to prevent it from being expanded. The readline | |
18414 | history facilities do not attempt substitution on the strings | |
18415 | @kbd{!=} and @kbd{!(}, even when history expansion is enabled. | |
18416 | ||
18417 | The commands to control history expansion are: | |
104c1213 JM |
18418 | |
18419 | @table @code | |
8e04817f AC |
18420 | @item set history expansion on |
18421 | @itemx set history expansion | |
703663ab | 18422 | @kindex set history expansion |
8e04817f | 18423 | Enable history expansion. History expansion is off by default. |
104c1213 | 18424 | |
8e04817f AC |
18425 | @item set history expansion off |
18426 | Disable history expansion. | |
104c1213 | 18427 | |
8e04817f AC |
18428 | @c @group |
18429 | @kindex show history | |
18430 | @item show history | |
18431 | @itemx show history filename | |
18432 | @itemx show history save | |
18433 | @itemx show history size | |
18434 | @itemx show history expansion | |
18435 | These commands display the state of the @value{GDBN} history parameters. | |
18436 | @code{show history} by itself displays all four states. | |
18437 | @c @end group | |
18438 | @end table | |
18439 | ||
18440 | @table @code | |
9c16f35a EZ |
18441 | @kindex show commands |
18442 | @cindex show last commands | |
18443 | @cindex display command history | |
8e04817f AC |
18444 | @item show commands |
18445 | Display the last ten commands in the command history. | |
104c1213 | 18446 | |
8e04817f AC |
18447 | @item show commands @var{n} |
18448 | Print ten commands centered on command number @var{n}. | |
18449 | ||
18450 | @item show commands + | |
18451 | Print ten commands just after the commands last printed. | |
104c1213 JM |
18452 | @end table |
18453 | ||
8e04817f | 18454 | @node Screen Size |
79a6e687 | 18455 | @section Screen Size |
8e04817f AC |
18456 | @cindex size of screen |
18457 | @cindex pauses in output | |
104c1213 | 18458 | |
8e04817f AC |
18459 | Certain commands to @value{GDBN} may produce large amounts of |
18460 | information output to the screen. To help you read all of it, | |
18461 | @value{GDBN} pauses and asks you for input at the end of each page of | |
18462 | output. Type @key{RET} when you want to continue the output, or @kbd{q} | |
18463 | to discard the remaining output. Also, the screen width setting | |
18464 | determines when to wrap lines of output. Depending on what is being | |
18465 | printed, @value{GDBN} tries to break the line at a readable place, | |
18466 | rather than simply letting it overflow onto the following line. | |
18467 | ||
18468 | Normally @value{GDBN} knows the size of the screen from the terminal | |
18469 | driver software. For example, on Unix @value{GDBN} uses the termcap data base | |
18470 | together with the value of the @code{TERM} environment variable and the | |
18471 | @code{stty rows} and @code{stty cols} settings. If this is not correct, | |
18472 | you can override it with the @code{set height} and @code{set | |
18473 | width} commands: | |
18474 | ||
18475 | @table @code | |
18476 | @kindex set height | |
18477 | @kindex set width | |
18478 | @kindex show width | |
18479 | @kindex show height | |
18480 | @item set height @var{lpp} | |
18481 | @itemx show height | |
18482 | @itemx set width @var{cpl} | |
18483 | @itemx show width | |
18484 | These @code{set} commands specify a screen height of @var{lpp} lines and | |
18485 | a screen width of @var{cpl} characters. The associated @code{show} | |
18486 | commands display the current settings. | |
104c1213 | 18487 | |
8e04817f AC |
18488 | If you specify a height of zero lines, @value{GDBN} does not pause during |
18489 | output no matter how long the output is. This is useful if output is to a | |
18490 | file or to an editor buffer. | |
104c1213 | 18491 | |
8e04817f AC |
18492 | Likewise, you can specify @samp{set width 0} to prevent @value{GDBN} |
18493 | from wrapping its output. | |
9c16f35a EZ |
18494 | |
18495 | @item set pagination on | |
18496 | @itemx set pagination off | |
18497 | @kindex set pagination | |
18498 | Turn the output pagination on or off; the default is on. Turning | |
7c953934 TT |
18499 | pagination off is the alternative to @code{set height 0}. Note that |
18500 | running @value{GDBN} with the @option{--batch} option (@pxref{Mode | |
18501 | Options, -batch}) also automatically disables pagination. | |
9c16f35a EZ |
18502 | |
18503 | @item show pagination | |
18504 | @kindex show pagination | |
18505 | Show the current pagination mode. | |
104c1213 JM |
18506 | @end table |
18507 | ||
8e04817f AC |
18508 | @node Numbers |
18509 | @section Numbers | |
18510 | @cindex number representation | |
18511 | @cindex entering numbers | |
104c1213 | 18512 | |
8e04817f AC |
18513 | You can always enter numbers in octal, decimal, or hexadecimal in |
18514 | @value{GDBN} by the usual conventions: octal numbers begin with | |
18515 | @samp{0}, decimal numbers end with @samp{.}, and hexadecimal numbers | |
eb2dae08 EZ |
18516 | begin with @samp{0x}. Numbers that neither begin with @samp{0} or |
18517 | @samp{0x}, nor end with a @samp{.} are, by default, entered in base | |
18518 | 10; likewise, the default display for numbers---when no particular | |
18519 | format is specified---is base 10. You can change the default base for | |
18520 | both input and output with the commands described below. | |
104c1213 | 18521 | |
8e04817f AC |
18522 | @table @code |
18523 | @kindex set input-radix | |
18524 | @item set input-radix @var{base} | |
18525 | Set the default base for numeric input. Supported choices | |
18526 | for @var{base} are decimal 8, 10, or 16. @var{base} must itself be | |
eb2dae08 | 18527 | specified either unambiguously or using the current input radix; for |
8e04817f | 18528 | example, any of |
104c1213 | 18529 | |
8e04817f | 18530 | @smallexample |
9c16f35a EZ |
18531 | set input-radix 012 |
18532 | set input-radix 10. | |
18533 | set input-radix 0xa | |
8e04817f | 18534 | @end smallexample |
104c1213 | 18535 | |
8e04817f | 18536 | @noindent |
9c16f35a | 18537 | sets the input base to decimal. On the other hand, @samp{set input-radix 10} |
eb2dae08 EZ |
18538 | leaves the input radix unchanged, no matter what it was, since |
18539 | @samp{10}, being without any leading or trailing signs of its base, is | |
18540 | interpreted in the current radix. Thus, if the current radix is 16, | |
18541 | @samp{10} is interpreted in hex, i.e.@: as 16 decimal, which doesn't | |
18542 | change the radix. | |
104c1213 | 18543 | |
8e04817f AC |
18544 | @kindex set output-radix |
18545 | @item set output-radix @var{base} | |
18546 | Set the default base for numeric display. Supported choices | |
18547 | for @var{base} are decimal 8, 10, or 16. @var{base} must itself be | |
eb2dae08 | 18548 | specified either unambiguously or using the current input radix. |
104c1213 | 18549 | |
8e04817f AC |
18550 | @kindex show input-radix |
18551 | @item show input-radix | |
18552 | Display the current default base for numeric input. | |
104c1213 | 18553 | |
8e04817f AC |
18554 | @kindex show output-radix |
18555 | @item show output-radix | |
18556 | Display the current default base for numeric display. | |
9c16f35a EZ |
18557 | |
18558 | @item set radix @r{[}@var{base}@r{]} | |
18559 | @itemx show radix | |
18560 | @kindex set radix | |
18561 | @kindex show radix | |
18562 | These commands set and show the default base for both input and output | |
18563 | of numbers. @code{set radix} sets the radix of input and output to | |
18564 | the same base; without an argument, it resets the radix back to its | |
18565 | default value of 10. | |
18566 | ||
8e04817f | 18567 | @end table |
104c1213 | 18568 | |
1e698235 | 18569 | @node ABI |
79a6e687 | 18570 | @section Configuring the Current ABI |
1e698235 DJ |
18571 | |
18572 | @value{GDBN} can determine the @dfn{ABI} (Application Binary Interface) of your | |
18573 | application automatically. However, sometimes you need to override its | |
18574 | conclusions. Use these commands to manage @value{GDBN}'s view of the | |
18575 | current ABI. | |
18576 | ||
98b45e30 DJ |
18577 | @cindex OS ABI |
18578 | @kindex set osabi | |
b4e9345d | 18579 | @kindex show osabi |
98b45e30 DJ |
18580 | |
18581 | One @value{GDBN} configuration can debug binaries for multiple operating | |
b383017d | 18582 | system targets, either via remote debugging or native emulation. |
98b45e30 DJ |
18583 | @value{GDBN} will autodetect the @dfn{OS ABI} (Operating System ABI) in use, |
18584 | but you can override its conclusion using the @code{set osabi} command. | |
18585 | One example where this is useful is in debugging of binaries which use | |
18586 | an alternate C library (e.g.@: @sc{uClibc} for @sc{gnu}/Linux) which does | |
18587 | not have the same identifying marks that the standard C library for your | |
18588 | platform provides. | |
18589 | ||
18590 | @table @code | |
18591 | @item show osabi | |
18592 | Show the OS ABI currently in use. | |
18593 | ||
18594 | @item set osabi | |
18595 | With no argument, show the list of registered available OS ABI's. | |
18596 | ||
18597 | @item set osabi @var{abi} | |
18598 | Set the current OS ABI to @var{abi}. | |
18599 | @end table | |
18600 | ||
1e698235 | 18601 | @cindex float promotion |
1e698235 DJ |
18602 | |
18603 | Generally, the way that an argument of type @code{float} is passed to a | |
18604 | function depends on whether the function is prototyped. For a prototyped | |
18605 | (i.e.@: ANSI/ISO style) function, @code{float} arguments are passed unchanged, | |
18606 | according to the architecture's convention for @code{float}. For unprototyped | |
18607 | (i.e.@: K&R style) functions, @code{float} arguments are first promoted to type | |
18608 | @code{double} and then passed. | |
18609 | ||
18610 | Unfortunately, some forms of debug information do not reliably indicate whether | |
18611 | a function is prototyped. If @value{GDBN} calls a function that is not marked | |
18612 | as prototyped, it consults @kbd{set coerce-float-to-double}. | |
18613 | ||
18614 | @table @code | |
a8f24a35 | 18615 | @kindex set coerce-float-to-double |
1e698235 DJ |
18616 | @item set coerce-float-to-double |
18617 | @itemx set coerce-float-to-double on | |
18618 | Arguments of type @code{float} will be promoted to @code{double} when passed | |
18619 | to an unprototyped function. This is the default setting. | |
18620 | ||
18621 | @item set coerce-float-to-double off | |
18622 | Arguments of type @code{float} will be passed directly to unprototyped | |
18623 | functions. | |
9c16f35a EZ |
18624 | |
18625 | @kindex show coerce-float-to-double | |
18626 | @item show coerce-float-to-double | |
18627 | Show the current setting of promoting @code{float} to @code{double}. | |
1e698235 DJ |
18628 | @end table |
18629 | ||
f1212245 DJ |
18630 | @kindex set cp-abi |
18631 | @kindex show cp-abi | |
18632 | @value{GDBN} needs to know the ABI used for your program's C@t{++} | |
18633 | objects. The correct C@t{++} ABI depends on which C@t{++} compiler was | |
18634 | used to build your application. @value{GDBN} only fully supports | |
18635 | programs with a single C@t{++} ABI; if your program contains code using | |
18636 | multiple C@t{++} ABI's or if @value{GDBN} can not identify your | |
18637 | program's ABI correctly, you can tell @value{GDBN} which ABI to use. | |
18638 | Currently supported ABI's include ``gnu-v2'', for @code{g++} versions | |
18639 | before 3.0, ``gnu-v3'', for @code{g++} versions 3.0 and later, and | |
18640 | ``hpaCC'' for the HP ANSI C@t{++} compiler. Other C@t{++} compilers may | |
18641 | use the ``gnu-v2'' or ``gnu-v3'' ABI's as well. The default setting is | |
18642 | ``auto''. | |
18643 | ||
18644 | @table @code | |
18645 | @item show cp-abi | |
18646 | Show the C@t{++} ABI currently in use. | |
18647 | ||
18648 | @item set cp-abi | |
18649 | With no argument, show the list of supported C@t{++} ABI's. | |
18650 | ||
18651 | @item set cp-abi @var{abi} | |
18652 | @itemx set cp-abi auto | |
18653 | Set the current C@t{++} ABI to @var{abi}, or return to automatic detection. | |
18654 | @end table | |
18655 | ||
8e04817f | 18656 | @node Messages/Warnings |
79a6e687 | 18657 | @section Optional Warnings and Messages |
104c1213 | 18658 | |
9c16f35a EZ |
18659 | @cindex verbose operation |
18660 | @cindex optional warnings | |
8e04817f AC |
18661 | By default, @value{GDBN} is silent about its inner workings. If you are |
18662 | running on a slow machine, you may want to use the @code{set verbose} | |
18663 | command. This makes @value{GDBN} tell you when it does a lengthy | |
18664 | internal operation, so you will not think it has crashed. | |
104c1213 | 18665 | |
8e04817f AC |
18666 | Currently, the messages controlled by @code{set verbose} are those |
18667 | which announce that the symbol table for a source file is being read; | |
79a6e687 | 18668 | see @code{symbol-file} in @ref{Files, ,Commands to Specify Files}. |
104c1213 | 18669 | |
8e04817f AC |
18670 | @table @code |
18671 | @kindex set verbose | |
18672 | @item set verbose on | |
18673 | Enables @value{GDBN} output of certain informational messages. | |
104c1213 | 18674 | |
8e04817f AC |
18675 | @item set verbose off |
18676 | Disables @value{GDBN} output of certain informational messages. | |
104c1213 | 18677 | |
8e04817f AC |
18678 | @kindex show verbose |
18679 | @item show verbose | |
18680 | Displays whether @code{set verbose} is on or off. | |
18681 | @end table | |
104c1213 | 18682 | |
8e04817f AC |
18683 | By default, if @value{GDBN} encounters bugs in the symbol table of an |
18684 | object file, it is silent; but if you are debugging a compiler, you may | |
79a6e687 BW |
18685 | find this information useful (@pxref{Symbol Errors, ,Errors Reading |
18686 | Symbol Files}). | |
104c1213 | 18687 | |
8e04817f | 18688 | @table @code |
104c1213 | 18689 | |
8e04817f AC |
18690 | @kindex set complaints |
18691 | @item set complaints @var{limit} | |
18692 | Permits @value{GDBN} to output @var{limit} complaints about each type of | |
18693 | unusual symbols before becoming silent about the problem. Set | |
18694 | @var{limit} to zero to suppress all complaints; set it to a large number | |
18695 | to prevent complaints from being suppressed. | |
104c1213 | 18696 | |
8e04817f AC |
18697 | @kindex show complaints |
18698 | @item show complaints | |
18699 | Displays how many symbol complaints @value{GDBN} is permitted to produce. | |
104c1213 | 18700 | |
8e04817f | 18701 | @end table |
104c1213 | 18702 | |
d837706a | 18703 | @anchor{confirmation requests} |
8e04817f AC |
18704 | By default, @value{GDBN} is cautious, and asks what sometimes seems to be a |
18705 | lot of stupid questions to confirm certain commands. For example, if | |
18706 | you try to run a program which is already running: | |
104c1213 | 18707 | |
474c8240 | 18708 | @smallexample |
8e04817f AC |
18709 | (@value{GDBP}) run |
18710 | The program being debugged has been started already. | |
18711 | Start it from the beginning? (y or n) | |
474c8240 | 18712 | @end smallexample |
104c1213 | 18713 | |
8e04817f AC |
18714 | If you are willing to unflinchingly face the consequences of your own |
18715 | commands, you can disable this ``feature'': | |
104c1213 | 18716 | |
8e04817f | 18717 | @table @code |
104c1213 | 18718 | |
8e04817f AC |
18719 | @kindex set confirm |
18720 | @cindex flinching | |
18721 | @cindex confirmation | |
18722 | @cindex stupid questions | |
18723 | @item set confirm off | |
7c953934 TT |
18724 | Disables confirmation requests. Note that running @value{GDBN} with |
18725 | the @option{--batch} option (@pxref{Mode Options, -batch}) also | |
18726 | automatically disables confirmation requests. | |
104c1213 | 18727 | |
8e04817f AC |
18728 | @item set confirm on |
18729 | Enables confirmation requests (the default). | |
104c1213 | 18730 | |
8e04817f AC |
18731 | @kindex show confirm |
18732 | @item show confirm | |
18733 | Displays state of confirmation requests. | |
18734 | ||
18735 | @end table | |
104c1213 | 18736 | |
16026cd7 AS |
18737 | @cindex command tracing |
18738 | If you need to debug user-defined commands or sourced files you may find it | |
18739 | useful to enable @dfn{command tracing}. In this mode each command will be | |
18740 | printed as it is executed, prefixed with one or more @samp{+} symbols, the | |
18741 | quantity denoting the call depth of each command. | |
18742 | ||
18743 | @table @code | |
18744 | @kindex set trace-commands | |
18745 | @cindex command scripts, debugging | |
18746 | @item set trace-commands on | |
18747 | Enable command tracing. | |
18748 | @item set trace-commands off | |
18749 | Disable command tracing. | |
18750 | @item show trace-commands | |
18751 | Display the current state of command tracing. | |
18752 | @end table | |
18753 | ||
8e04817f | 18754 | @node Debugging Output |
79a6e687 | 18755 | @section Optional Messages about Internal Happenings |
4644b6e3 EZ |
18756 | @cindex optional debugging messages |
18757 | ||
da316a69 EZ |
18758 | @value{GDBN} has commands that enable optional debugging messages from |
18759 | various @value{GDBN} subsystems; normally these commands are of | |
18760 | interest to @value{GDBN} maintainers, or when reporting a bug. This | |
18761 | section documents those commands. | |
18762 | ||
104c1213 | 18763 | @table @code |
a8f24a35 EZ |
18764 | @kindex set exec-done-display |
18765 | @item set exec-done-display | |
18766 | Turns on or off the notification of asynchronous commands' | |
18767 | completion. When on, @value{GDBN} will print a message when an | |
18768 | asynchronous command finishes its execution. The default is off. | |
18769 | @kindex show exec-done-display | |
18770 | @item show exec-done-display | |
18771 | Displays the current setting of asynchronous command completion | |
18772 | notification. | |
4644b6e3 EZ |
18773 | @kindex set debug |
18774 | @cindex gdbarch debugging info | |
a8f24a35 | 18775 | @cindex architecture debugging info |
8e04817f | 18776 | @item set debug arch |
a8f24a35 | 18777 | Turns on or off display of gdbarch debugging info. The default is off |
4644b6e3 | 18778 | @kindex show debug |
8e04817f AC |
18779 | @item show debug arch |
18780 | Displays the current state of displaying gdbarch debugging info. | |
721c2651 EZ |
18781 | @item set debug aix-thread |
18782 | @cindex AIX threads | |
18783 | Display debugging messages about inner workings of the AIX thread | |
18784 | module. | |
18785 | @item show debug aix-thread | |
18786 | Show the current state of AIX thread debugging info display. | |
d97bc12b DE |
18787 | @item set debug dwarf2-die |
18788 | @cindex DWARF2 DIEs | |
18789 | Dump DWARF2 DIEs after they are read in. | |
18790 | The value is the number of nesting levels to print. | |
18791 | A value of zero turns off the display. | |
18792 | @item show debug dwarf2-die | |
18793 | Show the current state of DWARF2 DIE debugging. | |
237fc4c9 PA |
18794 | @item set debug displaced |
18795 | @cindex displaced stepping debugging info | |
18796 | Turns on or off display of @value{GDBN} debugging info for the | |
18797 | displaced stepping support. The default is off. | |
18798 | @item show debug displaced | |
18799 | Displays the current state of displaying @value{GDBN} debugging info | |
18800 | related to displaced stepping. | |
8e04817f | 18801 | @item set debug event |
4644b6e3 | 18802 | @cindex event debugging info |
a8f24a35 | 18803 | Turns on or off display of @value{GDBN} event debugging info. The |
8e04817f | 18804 | default is off. |
8e04817f AC |
18805 | @item show debug event |
18806 | Displays the current state of displaying @value{GDBN} event debugging | |
18807 | info. | |
8e04817f | 18808 | @item set debug expression |
4644b6e3 | 18809 | @cindex expression debugging info |
721c2651 EZ |
18810 | Turns on or off display of debugging info about @value{GDBN} |
18811 | expression parsing. The default is off. | |
8e04817f | 18812 | @item show debug expression |
721c2651 EZ |
18813 | Displays the current state of displaying debugging info about |
18814 | @value{GDBN} expression parsing. | |
7453dc06 | 18815 | @item set debug frame |
4644b6e3 | 18816 | @cindex frame debugging info |
7453dc06 AC |
18817 | Turns on or off display of @value{GDBN} frame debugging info. The |
18818 | default is off. | |
7453dc06 AC |
18819 | @item show debug frame |
18820 | Displays the current state of displaying @value{GDBN} frame debugging | |
18821 | info. | |
cbe54154 PA |
18822 | @item set debug gnu-nat |
18823 | @cindex @sc{gnu}/Hurd debug messages | |
18824 | Turns on or off debugging messages from the @sc{gnu}/Hurd debug support. | |
18825 | @item show debug gnu-nat | |
18826 | Show the current state of @sc{gnu}/Hurd debugging messages. | |
30e91e0b RC |
18827 | @item set debug infrun |
18828 | @cindex inferior debugging info | |
18829 | Turns on or off display of @value{GDBN} debugging info for running the inferior. | |
18830 | The default is off. @file{infrun.c} contains GDB's runtime state machine used | |
18831 | for implementing operations such as single-stepping the inferior. | |
18832 | @item show debug infrun | |
18833 | Displays the current state of @value{GDBN} inferior debugging. | |
da316a69 EZ |
18834 | @item set debug lin-lwp |
18835 | @cindex @sc{gnu}/Linux LWP debug messages | |
18836 | @cindex Linux lightweight processes | |
721c2651 | 18837 | Turns on or off debugging messages from the Linux LWP debug support. |
da316a69 EZ |
18838 | @item show debug lin-lwp |
18839 | Show the current state of Linux LWP debugging messages. | |
b84876c2 PA |
18840 | @item set debug lin-lwp-async |
18841 | @cindex @sc{gnu}/Linux LWP async debug messages | |
18842 | @cindex Linux lightweight processes | |
18843 | Turns on or off debugging messages from the Linux LWP async debug support. | |
18844 | @item show debug lin-lwp-async | |
18845 | Show the current state of Linux LWP async debugging messages. | |
2b4855ab | 18846 | @item set debug observer |
4644b6e3 | 18847 | @cindex observer debugging info |
2b4855ab AC |
18848 | Turns on or off display of @value{GDBN} observer debugging. This |
18849 | includes info such as the notification of observable events. | |
2b4855ab AC |
18850 | @item show debug observer |
18851 | Displays the current state of observer debugging. | |
8e04817f | 18852 | @item set debug overload |
4644b6e3 | 18853 | @cindex C@t{++} overload debugging info |
8e04817f | 18854 | Turns on or off display of @value{GDBN} C@t{++} overload debugging |
359df76b | 18855 | info. This includes info such as ranking of functions, etc. The default |
8e04817f | 18856 | is off. |
8e04817f AC |
18857 | @item show debug overload |
18858 | Displays the current state of displaying @value{GDBN} C@t{++} overload | |
18859 | debugging info. | |
92981e24 TT |
18860 | @cindex expression parser, debugging info |
18861 | @cindex debug expression parser | |
18862 | @item set debug parser | |
18863 | Turns on or off the display of expression parser debugging output. | |
18864 | Internally, this sets the @code{yydebug} variable in the expression | |
18865 | parser. @xref{Tracing, , Tracing Your Parser, bison, Bison}, for | |
18866 | details. The default is off. | |
18867 | @item show debug parser | |
18868 | Show the current state of expression parser debugging. | |
8e04817f AC |
18869 | @cindex packets, reporting on stdout |
18870 | @cindex serial connections, debugging | |
605a56cb DJ |
18871 | @cindex debug remote protocol |
18872 | @cindex remote protocol debugging | |
18873 | @cindex display remote packets | |
8e04817f AC |
18874 | @item set debug remote |
18875 | Turns on or off display of reports on all packets sent back and forth across | |
18876 | the serial line to the remote machine. The info is printed on the | |
18877 | @value{GDBN} standard output stream. The default is off. | |
8e04817f AC |
18878 | @item show debug remote |
18879 | Displays the state of display of remote packets. | |
8e04817f AC |
18880 | @item set debug serial |
18881 | Turns on or off display of @value{GDBN} serial debugging info. The | |
18882 | default is off. | |
8e04817f AC |
18883 | @item show debug serial |
18884 | Displays the current state of displaying @value{GDBN} serial debugging | |
18885 | info. | |
c45da7e6 EZ |
18886 | @item set debug solib-frv |
18887 | @cindex FR-V shared-library debugging | |
18888 | Turns on or off debugging messages for FR-V shared-library code. | |
18889 | @item show debug solib-frv | |
18890 | Display the current state of FR-V shared-library code debugging | |
18891 | messages. | |
8e04817f | 18892 | @item set debug target |
4644b6e3 | 18893 | @cindex target debugging info |
8e04817f AC |
18894 | Turns on or off display of @value{GDBN} target debugging info. This info |
18895 | includes what is going on at the target level of GDB, as it happens. The | |
701b08bb DJ |
18896 | default is 0. Set it to 1 to track events, and to 2 to also track the |
18897 | value of large memory transfers. Changes to this flag do not take effect | |
18898 | until the next time you connect to a target or use the @code{run} command. | |
8e04817f AC |
18899 | @item show debug target |
18900 | Displays the current state of displaying @value{GDBN} target debugging | |
18901 | info. | |
75feb17d DJ |
18902 | @item set debug timestamp |
18903 | @cindex timestampping debugging info | |
18904 | Turns on or off display of timestamps with @value{GDBN} debugging info. | |
18905 | When enabled, seconds and microseconds are displayed before each debugging | |
18906 | message. | |
18907 | @item show debug timestamp | |
18908 | Displays the current state of displaying timestamps with @value{GDBN} | |
18909 | debugging info. | |
c45da7e6 | 18910 | @item set debugvarobj |
4644b6e3 | 18911 | @cindex variable object debugging info |
8e04817f AC |
18912 | Turns on or off display of @value{GDBN} variable object debugging |
18913 | info. The default is off. | |
c45da7e6 | 18914 | @item show debugvarobj |
8e04817f AC |
18915 | Displays the current state of displaying @value{GDBN} variable object |
18916 | debugging info. | |
e776119f DJ |
18917 | @item set debug xml |
18918 | @cindex XML parser debugging | |
18919 | Turns on or off debugging messages for built-in XML parsers. | |
18920 | @item show debug xml | |
18921 | Displays the current state of XML debugging messages. | |
8e04817f | 18922 | @end table |
104c1213 | 18923 | |
14fb1bac JB |
18924 | @node Other Misc Settings |
18925 | @section Other Miscellaneous Settings | |
18926 | @cindex miscellaneous settings | |
18927 | ||
18928 | @table @code | |
18929 | @kindex set interactive-mode | |
18930 | @item set interactive-mode | |
18931 | If @code{on}, forces @value{GDBN} to operate interactively. | |
18932 | If @code{off}, forces @value{GDBN} to operate non-interactively, | |
18933 | If @code{auto} (the default), @value{GDBN} guesses which mode to use, | |
18934 | based on whether the debugger was started in a terminal or not. | |
18935 | ||
18936 | In the vast majority of cases, the debugger should be able to guess | |
18937 | correctly which mode should be used. But this setting can be useful | |
18938 | in certain specific cases, such as running a MinGW @value{GDBN} | |
18939 | inside a cygwin window. | |
18940 | ||
18941 | @kindex show interactive-mode | |
18942 | @item show interactive-mode | |
18943 | Displays whether the debugger is operating in interactive mode or not. | |
18944 | @end table | |
18945 | ||
d57a3c85 TJB |
18946 | @node Extending GDB |
18947 | @chapter Extending @value{GDBN} | |
18948 | @cindex extending GDB | |
18949 | ||
18950 | @value{GDBN} provides two mechanisms for extension. The first is based | |
18951 | on composition of @value{GDBN} commands, and the second is based on the | |
18952 | Python scripting language. | |
18953 | ||
95433b34 JB |
18954 | To facilitate the use of these extensions, @value{GDBN} is capable |
18955 | of evaluating the contents of a file. When doing so, @value{GDBN} | |
18956 | can recognize which scripting language is being used by looking at | |
18957 | the filename extension. Files with an unrecognized filename extension | |
18958 | are always treated as a @value{GDBN} Command Files. | |
18959 | @xref{Command Files,, Command files}. | |
18960 | ||
18961 | You can control how @value{GDBN} evaluates these files with the following | |
18962 | setting: | |
18963 | ||
18964 | @table @code | |
18965 | @kindex set script-extension | |
18966 | @kindex show script-extension | |
18967 | @item set script-extension off | |
18968 | All scripts are always evaluated as @value{GDBN} Command Files. | |
18969 | ||
18970 | @item set script-extension soft | |
18971 | The debugger determines the scripting language based on filename | |
18972 | extension. If this scripting language is supported, @value{GDBN} | |
18973 | evaluates the script using that language. Otherwise, it evaluates | |
18974 | the file as a @value{GDBN} Command File. | |
18975 | ||
18976 | @item set script-extension strict | |
18977 | The debugger determines the scripting language based on filename | |
18978 | extension, and evaluates the script using that language. If the | |
18979 | language is not supported, then the evaluation fails. | |
18980 | ||
18981 | @item show script-extension | |
18982 | Display the current value of the @code{script-extension} option. | |
18983 | ||
18984 | @end table | |
18985 | ||
d57a3c85 TJB |
18986 | @menu |
18987 | * Sequences:: Canned Sequences of Commands | |
18988 | * Python:: Scripting @value{GDBN} using Python | |
18989 | @end menu | |
18990 | ||
8e04817f | 18991 | @node Sequences |
d57a3c85 | 18992 | @section Canned Sequences of Commands |
104c1213 | 18993 | |
8e04817f | 18994 | Aside from breakpoint commands (@pxref{Break Commands, ,Breakpoint |
79a6e687 | 18995 | Command Lists}), @value{GDBN} provides two ways to store sequences of |
8e04817f AC |
18996 | commands for execution as a unit: user-defined commands and command |
18997 | files. | |
104c1213 | 18998 | |
8e04817f | 18999 | @menu |
fcc73fe3 EZ |
19000 | * Define:: How to define your own commands |
19001 | * Hooks:: Hooks for user-defined commands | |
19002 | * Command Files:: How to write scripts of commands to be stored in a file | |
19003 | * Output:: Commands for controlled output | |
8e04817f | 19004 | @end menu |
104c1213 | 19005 | |
8e04817f | 19006 | @node Define |
d57a3c85 | 19007 | @subsection User-defined Commands |
104c1213 | 19008 | |
8e04817f | 19009 | @cindex user-defined command |
fcc73fe3 | 19010 | @cindex arguments, to user-defined commands |
8e04817f AC |
19011 | A @dfn{user-defined command} is a sequence of @value{GDBN} commands to |
19012 | which you assign a new name as a command. This is done with the | |
19013 | @code{define} command. User commands may accept up to 10 arguments | |
19014 | separated by whitespace. Arguments are accessed within the user command | |
c03c782f | 19015 | via @code{$arg0@dots{}$arg9}. A trivial example: |
104c1213 | 19016 | |
8e04817f AC |
19017 | @smallexample |
19018 | define adder | |
19019 | print $arg0 + $arg1 + $arg2 | |
c03c782f | 19020 | end |
8e04817f | 19021 | @end smallexample |
104c1213 JM |
19022 | |
19023 | @noindent | |
8e04817f | 19024 | To execute the command use: |
104c1213 | 19025 | |
8e04817f AC |
19026 | @smallexample |
19027 | adder 1 2 3 | |
19028 | @end smallexample | |
104c1213 | 19029 | |
8e04817f AC |
19030 | @noindent |
19031 | This defines the command @code{adder}, which prints the sum of | |
19032 | its three arguments. Note the arguments are text substitutions, so they may | |
19033 | reference variables, use complex expressions, or even perform inferior | |
19034 | functions calls. | |
104c1213 | 19035 | |
fcc73fe3 EZ |
19036 | @cindex argument count in user-defined commands |
19037 | @cindex how many arguments (user-defined commands) | |
c03c782f AS |
19038 | In addition, @code{$argc} may be used to find out how many arguments have |
19039 | been passed. This expands to a number in the range 0@dots{}10. | |
19040 | ||
19041 | @smallexample | |
19042 | define adder | |
19043 | if $argc == 2 | |
19044 | print $arg0 + $arg1 | |
19045 | end | |
19046 | if $argc == 3 | |
19047 | print $arg0 + $arg1 + $arg2 | |
19048 | end | |
19049 | end | |
19050 | @end smallexample | |
19051 | ||
104c1213 | 19052 | @table @code |
104c1213 | 19053 | |
8e04817f AC |
19054 | @kindex define |
19055 | @item define @var{commandname} | |
19056 | Define a command named @var{commandname}. If there is already a command | |
19057 | by that name, you are asked to confirm that you want to redefine it. | |
adb483fe DJ |
19058 | @var{commandname} may be a bare command name consisting of letters, |
19059 | numbers, dashes, and underscores. It may also start with any predefined | |
19060 | prefix command. For example, @samp{define target my-target} creates | |
19061 | a user-defined @samp{target my-target} command. | |
104c1213 | 19062 | |
8e04817f AC |
19063 | The definition of the command is made up of other @value{GDBN} command lines, |
19064 | which are given following the @code{define} command. The end of these | |
19065 | commands is marked by a line containing @code{end}. | |
104c1213 | 19066 | |
8e04817f | 19067 | @kindex document |
ca91424e | 19068 | @kindex end@r{ (user-defined commands)} |
8e04817f AC |
19069 | @item document @var{commandname} |
19070 | Document the user-defined command @var{commandname}, so that it can be | |
19071 | accessed by @code{help}. The command @var{commandname} must already be | |
19072 | defined. This command reads lines of documentation just as @code{define} | |
19073 | reads the lines of the command definition, ending with @code{end}. | |
19074 | After the @code{document} command is finished, @code{help} on command | |
19075 | @var{commandname} displays the documentation you have written. | |
104c1213 | 19076 | |
8e04817f AC |
19077 | You may use the @code{document} command again to change the |
19078 | documentation of a command. Redefining the command with @code{define} | |
19079 | does not change the documentation. | |
104c1213 | 19080 | |
c45da7e6 EZ |
19081 | @kindex dont-repeat |
19082 | @cindex don't repeat command | |
19083 | @item dont-repeat | |
19084 | Used inside a user-defined command, this tells @value{GDBN} that this | |
19085 | command should not be repeated when the user hits @key{RET} | |
19086 | (@pxref{Command Syntax, repeat last command}). | |
19087 | ||
8e04817f AC |
19088 | @kindex help user-defined |
19089 | @item help user-defined | |
19090 | List all user-defined commands, with the first line of the documentation | |
19091 | (if any) for each. | |
104c1213 | 19092 | |
8e04817f AC |
19093 | @kindex show user |
19094 | @item show user | |
19095 | @itemx show user @var{commandname} | |
19096 | Display the @value{GDBN} commands used to define @var{commandname} (but | |
19097 | not its documentation). If no @var{commandname} is given, display the | |
19098 | definitions for all user-defined commands. | |
104c1213 | 19099 | |
fcc73fe3 | 19100 | @cindex infinite recursion in user-defined commands |
20f01a46 DH |
19101 | @kindex show max-user-call-depth |
19102 | @kindex set max-user-call-depth | |
19103 | @item show max-user-call-depth | |
5ca0cb28 DH |
19104 | @itemx set max-user-call-depth |
19105 | The value of @code{max-user-call-depth} controls how many recursion | |
3f94c067 | 19106 | levels are allowed in user-defined commands before @value{GDBN} suspects an |
5ca0cb28 | 19107 | infinite recursion and aborts the command. |
104c1213 JM |
19108 | @end table |
19109 | ||
fcc73fe3 EZ |
19110 | In addition to the above commands, user-defined commands frequently |
19111 | use control flow commands, described in @ref{Command Files}. | |
19112 | ||
8e04817f AC |
19113 | When user-defined commands are executed, the |
19114 | commands of the definition are not printed. An error in any command | |
19115 | stops execution of the user-defined command. | |
104c1213 | 19116 | |
8e04817f AC |
19117 | If used interactively, commands that would ask for confirmation proceed |
19118 | without asking when used inside a user-defined command. Many @value{GDBN} | |
19119 | commands that normally print messages to say what they are doing omit the | |
19120 | messages when used in a user-defined command. | |
104c1213 | 19121 | |
8e04817f | 19122 | @node Hooks |
d57a3c85 | 19123 | @subsection User-defined Command Hooks |
8e04817f AC |
19124 | @cindex command hooks |
19125 | @cindex hooks, for commands | |
19126 | @cindex hooks, pre-command | |
104c1213 | 19127 | |
8e04817f | 19128 | @kindex hook |
8e04817f AC |
19129 | You may define @dfn{hooks}, which are a special kind of user-defined |
19130 | command. Whenever you run the command @samp{foo}, if the user-defined | |
19131 | command @samp{hook-foo} exists, it is executed (with no arguments) | |
19132 | before that command. | |
104c1213 | 19133 | |
8e04817f AC |
19134 | @cindex hooks, post-command |
19135 | @kindex hookpost | |
8e04817f AC |
19136 | A hook may also be defined which is run after the command you executed. |
19137 | Whenever you run the command @samp{foo}, if the user-defined command | |
19138 | @samp{hookpost-foo} exists, it is executed (with no arguments) after | |
19139 | that command. Post-execution hooks may exist simultaneously with | |
19140 | pre-execution hooks, for the same command. | |
104c1213 | 19141 | |
8e04817f | 19142 | It is valid for a hook to call the command which it hooks. If this |
9f1c6395 | 19143 | occurs, the hook is not re-executed, thereby avoiding infinite recursion. |
104c1213 | 19144 | |
8e04817f AC |
19145 | @c It would be nice if hookpost could be passed a parameter indicating |
19146 | @c if the command it hooks executed properly or not. FIXME! | |
104c1213 | 19147 | |
8e04817f AC |
19148 | @kindex stop@r{, a pseudo-command} |
19149 | In addition, a pseudo-command, @samp{stop} exists. Defining | |
19150 | (@samp{hook-stop}) makes the associated commands execute every time | |
19151 | execution stops in your program: before breakpoint commands are run, | |
19152 | displays are printed, or the stack frame is printed. | |
104c1213 | 19153 | |
8e04817f AC |
19154 | For example, to ignore @code{SIGALRM} signals while |
19155 | single-stepping, but treat them normally during normal execution, | |
19156 | you could define: | |
104c1213 | 19157 | |
474c8240 | 19158 | @smallexample |
8e04817f AC |
19159 | define hook-stop |
19160 | handle SIGALRM nopass | |
19161 | end | |
104c1213 | 19162 | |
8e04817f AC |
19163 | define hook-run |
19164 | handle SIGALRM pass | |
19165 | end | |
104c1213 | 19166 | |
8e04817f | 19167 | define hook-continue |
d3e8051b | 19168 | handle SIGALRM pass |
8e04817f | 19169 | end |
474c8240 | 19170 | @end smallexample |
104c1213 | 19171 | |
d3e8051b | 19172 | As a further example, to hook at the beginning and end of the @code{echo} |
b383017d | 19173 | command, and to add extra text to the beginning and end of the message, |
8e04817f | 19174 | you could define: |
104c1213 | 19175 | |
474c8240 | 19176 | @smallexample |
8e04817f AC |
19177 | define hook-echo |
19178 | echo <<<--- | |
19179 | end | |
104c1213 | 19180 | |
8e04817f AC |
19181 | define hookpost-echo |
19182 | echo --->>>\n | |
19183 | end | |
104c1213 | 19184 | |
8e04817f AC |
19185 | (@value{GDBP}) echo Hello World |
19186 | <<<---Hello World--->>> | |
19187 | (@value{GDBP}) | |
104c1213 | 19188 | |
474c8240 | 19189 | @end smallexample |
104c1213 | 19190 | |
8e04817f AC |
19191 | You can define a hook for any single-word command in @value{GDBN}, but |
19192 | not for command aliases; you should define a hook for the basic command | |
c1468174 | 19193 | name, e.g.@: @code{backtrace} rather than @code{bt}. |
8e04817f AC |
19194 | @c FIXME! So how does Joe User discover whether a command is an alias |
19195 | @c or not? | |
adb483fe DJ |
19196 | You can hook a multi-word command by adding @code{hook-} or |
19197 | @code{hookpost-} to the last word of the command, e.g.@: | |
19198 | @samp{define target hook-remote} to add a hook to @samp{target remote}. | |
19199 | ||
8e04817f AC |
19200 | If an error occurs during the execution of your hook, execution of |
19201 | @value{GDBN} commands stops and @value{GDBN} issues a prompt | |
19202 | (before the command that you actually typed had a chance to run). | |
104c1213 | 19203 | |
8e04817f AC |
19204 | If you try to define a hook which does not match any known command, you |
19205 | get a warning from the @code{define} command. | |
c906108c | 19206 | |
8e04817f | 19207 | @node Command Files |
d57a3c85 | 19208 | @subsection Command Files |
c906108c | 19209 | |
8e04817f | 19210 | @cindex command files |
fcc73fe3 | 19211 | @cindex scripting commands |
6fc08d32 EZ |
19212 | A command file for @value{GDBN} is a text file made of lines that are |
19213 | @value{GDBN} commands. Comments (lines starting with @kbd{#}) may | |
19214 | also be included. An empty line in a command file does nothing; it | |
19215 | does not mean to repeat the last command, as it would from the | |
19216 | terminal. | |
c906108c | 19217 | |
6fc08d32 | 19218 | You can request the execution of a command file with the @code{source} |
95433b34 JB |
19219 | command. Note that the @code{source} command is also used to evaluate |
19220 | scripts that are not Command Files. The exact behavior can be configured | |
19221 | using the @code{script-extension} setting. | |
19222 | @xref{Extending GDB,, Extending GDB}. | |
c906108c | 19223 | |
8e04817f AC |
19224 | @table @code |
19225 | @kindex source | |
ca91424e | 19226 | @cindex execute commands from a file |
16026cd7 | 19227 | @item source [@code{-v}] @var{filename} |
8e04817f | 19228 | Execute the command file @var{filename}. |
c906108c SS |
19229 | @end table |
19230 | ||
fcc73fe3 EZ |
19231 | The lines in a command file are generally executed sequentially, |
19232 | unless the order of execution is changed by one of the | |
19233 | @emph{flow-control commands} described below. The commands are not | |
a71ec265 DH |
19234 | printed as they are executed. An error in any command terminates |
19235 | execution of the command file and control is returned to the console. | |
c906108c | 19236 | |
4b505b12 AS |
19237 | @value{GDBN} searches for @var{filename} in the current directory and then |
19238 | on the search path (specified with the @samp{directory} command). | |
19239 | ||
16026cd7 AS |
19240 | If @code{-v}, for verbose mode, is given then @value{GDBN} displays |
19241 | each command as it is executed. The option must be given before | |
19242 | @var{filename}, and is interpreted as part of the filename anywhere else. | |
19243 | ||
8e04817f AC |
19244 | Commands that would ask for confirmation if used interactively proceed |
19245 | without asking when used in a command file. Many @value{GDBN} commands that | |
19246 | normally print messages to say what they are doing omit the messages | |
19247 | when called from command files. | |
c906108c | 19248 | |
8e04817f AC |
19249 | @value{GDBN} also accepts command input from standard input. In this |
19250 | mode, normal output goes to standard output and error output goes to | |
19251 | standard error. Errors in a command file supplied on standard input do | |
6fc08d32 | 19252 | not terminate execution of the command file---execution continues with |
8e04817f | 19253 | the next command. |
c906108c | 19254 | |
474c8240 | 19255 | @smallexample |
8e04817f | 19256 | gdb < cmds > log 2>&1 |
474c8240 | 19257 | @end smallexample |
c906108c | 19258 | |
8e04817f AC |
19259 | (The syntax above will vary depending on the shell used.) This example |
19260 | will execute commands from the file @file{cmds}. All output and errors | |
19261 | would be directed to @file{log}. | |
c906108c | 19262 | |
fcc73fe3 EZ |
19263 | Since commands stored on command files tend to be more general than |
19264 | commands typed interactively, they frequently need to deal with | |
19265 | complicated situations, such as different or unexpected values of | |
19266 | variables and symbols, changes in how the program being debugged is | |
19267 | built, etc. @value{GDBN} provides a set of flow-control commands to | |
19268 | deal with these complexities. Using these commands, you can write | |
19269 | complex scripts that loop over data structures, execute commands | |
19270 | conditionally, etc. | |
19271 | ||
19272 | @table @code | |
19273 | @kindex if | |
19274 | @kindex else | |
19275 | @item if | |
19276 | @itemx else | |
19277 | This command allows to include in your script conditionally executed | |
19278 | commands. The @code{if} command takes a single argument, which is an | |
19279 | expression to evaluate. It is followed by a series of commands that | |
19280 | are executed only if the expression is true (its value is nonzero). | |
19281 | There can then optionally be an @code{else} line, followed by a series | |
19282 | of commands that are only executed if the expression was false. The | |
19283 | end of the list is marked by a line containing @code{end}. | |
19284 | ||
19285 | @kindex while | |
19286 | @item while | |
19287 | This command allows to write loops. Its syntax is similar to | |
19288 | @code{if}: the command takes a single argument, which is an expression | |
19289 | to evaluate, and must be followed by the commands to execute, one per | |
19290 | line, terminated by an @code{end}. These commands are called the | |
19291 | @dfn{body} of the loop. The commands in the body of @code{while} are | |
19292 | executed repeatedly as long as the expression evaluates to true. | |
19293 | ||
19294 | @kindex loop_break | |
19295 | @item loop_break | |
19296 | This command exits the @code{while} loop in whose body it is included. | |
19297 | Execution of the script continues after that @code{while}s @code{end} | |
19298 | line. | |
19299 | ||
19300 | @kindex loop_continue | |
19301 | @item loop_continue | |
19302 | This command skips the execution of the rest of the body of commands | |
19303 | in the @code{while} loop in whose body it is included. Execution | |
19304 | branches to the beginning of the @code{while} loop, where it evaluates | |
19305 | the controlling expression. | |
ca91424e EZ |
19306 | |
19307 | @kindex end@r{ (if/else/while commands)} | |
19308 | @item end | |
19309 | Terminate the block of commands that are the body of @code{if}, | |
19310 | @code{else}, or @code{while} flow-control commands. | |
fcc73fe3 EZ |
19311 | @end table |
19312 | ||
19313 | ||
8e04817f | 19314 | @node Output |
d57a3c85 | 19315 | @subsection Commands for Controlled Output |
c906108c | 19316 | |
8e04817f AC |
19317 | During the execution of a command file or a user-defined command, normal |
19318 | @value{GDBN} output is suppressed; the only output that appears is what is | |
19319 | explicitly printed by the commands in the definition. This section | |
19320 | describes three commands useful for generating exactly the output you | |
19321 | want. | |
c906108c SS |
19322 | |
19323 | @table @code | |
8e04817f AC |
19324 | @kindex echo |
19325 | @item echo @var{text} | |
19326 | @c I do not consider backslash-space a standard C escape sequence | |
19327 | @c because it is not in ANSI. | |
19328 | Print @var{text}. Nonprinting characters can be included in | |
19329 | @var{text} using C escape sequences, such as @samp{\n} to print a | |
19330 | newline. @strong{No newline is printed unless you specify one.} | |
19331 | In addition to the standard C escape sequences, a backslash followed | |
19332 | by a space stands for a space. This is useful for displaying a | |
19333 | string with spaces at the beginning or the end, since leading and | |
19334 | trailing spaces are otherwise trimmed from all arguments. | |
19335 | To print @samp{@w{ }and foo =@w{ }}, use the command | |
19336 | @samp{echo \@w{ }and foo = \@w{ }}. | |
c906108c | 19337 | |
8e04817f AC |
19338 | A backslash at the end of @var{text} can be used, as in C, to continue |
19339 | the command onto subsequent lines. For example, | |
c906108c | 19340 | |
474c8240 | 19341 | @smallexample |
8e04817f AC |
19342 | echo This is some text\n\ |
19343 | which is continued\n\ | |
19344 | onto several lines.\n | |
474c8240 | 19345 | @end smallexample |
c906108c | 19346 | |
8e04817f | 19347 | produces the same output as |
c906108c | 19348 | |
474c8240 | 19349 | @smallexample |
8e04817f AC |
19350 | echo This is some text\n |
19351 | echo which is continued\n | |
19352 | echo onto several lines.\n | |
474c8240 | 19353 | @end smallexample |
c906108c | 19354 | |
8e04817f AC |
19355 | @kindex output |
19356 | @item output @var{expression} | |
19357 | Print the value of @var{expression} and nothing but that value: no | |
19358 | newlines, no @samp{$@var{nn} = }. The value is not entered in the | |
19359 | value history either. @xref{Expressions, ,Expressions}, for more information | |
19360 | on expressions. | |
c906108c | 19361 | |
8e04817f AC |
19362 | @item output/@var{fmt} @var{expression} |
19363 | Print the value of @var{expression} in format @var{fmt}. You can use | |
19364 | the same formats as for @code{print}. @xref{Output Formats,,Output | |
79a6e687 | 19365 | Formats}, for more information. |
c906108c | 19366 | |
8e04817f | 19367 | @kindex printf |
82160952 EZ |
19368 | @item printf @var{template}, @var{expressions}@dots{} |
19369 | Print the values of one or more @var{expressions} under the control of | |
19370 | the string @var{template}. To print several values, make | |
19371 | @var{expressions} be a comma-separated list of individual expressions, | |
19372 | which may be either numbers or pointers. Their values are printed as | |
19373 | specified by @var{template}, exactly as a C program would do by | |
19374 | executing the code below: | |
c906108c | 19375 | |
474c8240 | 19376 | @smallexample |
82160952 | 19377 | printf (@var{template}, @var{expressions}@dots{}); |
474c8240 | 19378 | @end smallexample |
c906108c | 19379 | |
82160952 EZ |
19380 | As in @code{C} @code{printf}, ordinary characters in @var{template} |
19381 | are printed verbatim, while @dfn{conversion specification} introduced | |
19382 | by the @samp{%} character cause subsequent @var{expressions} to be | |
19383 | evaluated, their values converted and formatted according to type and | |
19384 | style information encoded in the conversion specifications, and then | |
19385 | printed. | |
19386 | ||
8e04817f | 19387 | For example, you can print two values in hex like this: |
c906108c | 19388 | |
8e04817f AC |
19389 | @smallexample |
19390 | printf "foo, bar-foo = 0x%x, 0x%x\n", foo, bar-foo | |
19391 | @end smallexample | |
c906108c | 19392 | |
82160952 EZ |
19393 | @code{printf} supports all the standard @code{C} conversion |
19394 | specifications, including the flags and modifiers between the @samp{%} | |
19395 | character and the conversion letter, with the following exceptions: | |
19396 | ||
19397 | @itemize @bullet | |
19398 | @item | |
19399 | The argument-ordering modifiers, such as @samp{2$}, are not supported. | |
19400 | ||
19401 | @item | |
19402 | The modifier @samp{*} is not supported for specifying precision or | |
19403 | width. | |
19404 | ||
19405 | @item | |
19406 | The @samp{'} flag (for separation of digits into groups according to | |
19407 | @code{LC_NUMERIC'}) is not supported. | |
19408 | ||
19409 | @item | |
19410 | The type modifiers @samp{hh}, @samp{j}, @samp{t}, and @samp{z} are not | |
19411 | supported. | |
19412 | ||
19413 | @item | |
19414 | The conversion letter @samp{n} (as in @samp{%n}) is not supported. | |
19415 | ||
19416 | @item | |
19417 | The conversion letters @samp{a} and @samp{A} are not supported. | |
19418 | @end itemize | |
19419 | ||
19420 | @noindent | |
19421 | Note that the @samp{ll} type modifier is supported only if the | |
19422 | underlying @code{C} implementation used to build @value{GDBN} supports | |
19423 | the @code{long long int} type, and the @samp{L} type modifier is | |
19424 | supported only if @code{long double} type is available. | |
19425 | ||
19426 | As in @code{C}, @code{printf} supports simple backslash-escape | |
19427 | sequences, such as @code{\n}, @samp{\t}, @samp{\\}, @samp{\"}, | |
19428 | @samp{\a}, and @samp{\f}, that consist of backslash followed by a | |
19429 | single character. Octal and hexadecimal escape sequences are not | |
19430 | supported. | |
1a619819 LM |
19431 | |
19432 | Additionally, @code{printf} supports conversion specifications for DFP | |
0aea4bf3 LM |
19433 | (@dfn{Decimal Floating Point}) types using the following length modifiers |
19434 | together with a floating point specifier. | |
1a619819 LM |
19435 | letters: |
19436 | ||
19437 | @itemize @bullet | |
19438 | @item | |
19439 | @samp{H} for printing @code{Decimal32} types. | |
19440 | ||
19441 | @item | |
19442 | @samp{D} for printing @code{Decimal64} types. | |
19443 | ||
19444 | @item | |
19445 | @samp{DD} for printing @code{Decimal128} types. | |
19446 | @end itemize | |
19447 | ||
19448 | If the underlying @code{C} implementation used to build @value{GDBN} has | |
0aea4bf3 | 19449 | support for the three length modifiers for DFP types, other modifiers |
3b784c4f | 19450 | such as width and precision will also be available for @value{GDBN} to use. |
1a619819 LM |
19451 | |
19452 | In case there is no such @code{C} support, no additional modifiers will be | |
19453 | available and the value will be printed in the standard way. | |
19454 | ||
19455 | Here's an example of printing DFP types using the above conversion letters: | |
19456 | @smallexample | |
0aea4bf3 | 19457 | printf "D32: %Hf - D64: %Df - D128: %DDf\n",1.2345df,1.2E10dd,1.2E1dl |
1a619819 LM |
19458 | @end smallexample |
19459 | ||
c906108c SS |
19460 | @end table |
19461 | ||
d57a3c85 TJB |
19462 | @node Python |
19463 | @section Scripting @value{GDBN} using Python | |
19464 | @cindex python scripting | |
19465 | @cindex scripting with python | |
19466 | ||
19467 | You can script @value{GDBN} using the @uref{http://www.python.org/, | |
19468 | Python programming language}. This feature is available only if | |
19469 | @value{GDBN} was configured using @option{--with-python}. | |
19470 | ||
19471 | @menu | |
19472 | * Python Commands:: Accessing Python from @value{GDBN}. | |
19473 | * Python API:: Accessing @value{GDBN} from Python. | |
19474 | @end menu | |
19475 | ||
19476 | @node Python Commands | |
19477 | @subsection Python Commands | |
19478 | @cindex python commands | |
19479 | @cindex commands to access python | |
19480 | ||
19481 | @value{GDBN} provides one command for accessing the Python interpreter, | |
19482 | and one related setting: | |
19483 | ||
19484 | @table @code | |
19485 | @kindex python | |
19486 | @item python @r{[}@var{code}@r{]} | |
19487 | The @code{python} command can be used to evaluate Python code. | |
19488 | ||
19489 | If given an argument, the @code{python} command will evaluate the | |
19490 | argument as a Python command. For example: | |
19491 | ||
19492 | @smallexample | |
19493 | (@value{GDBP}) python print 23 | |
19494 | 23 | |
19495 | @end smallexample | |
19496 | ||
19497 | If you do not provide an argument to @code{python}, it will act as a | |
19498 | multi-line command, like @code{define}. In this case, the Python | |
19499 | script is made up of subsequent command lines, given after the | |
19500 | @code{python} command. This command list is terminated using a line | |
19501 | containing @code{end}. For example: | |
19502 | ||
19503 | @smallexample | |
19504 | (@value{GDBP}) python | |
19505 | Type python script | |
19506 | End with a line saying just "end". | |
19507 | >print 23 | |
19508 | >end | |
19509 | 23 | |
19510 | @end smallexample | |
19511 | ||
19512 | @kindex maint set python print-stack | |
19513 | @item maint set python print-stack | |
19514 | By default, @value{GDBN} will print a stack trace when an error occurs | |
19515 | in a Python script. This can be controlled using @code{maint set | |
19516 | python print-stack}: if @code{on}, the default, then Python stack | |
19517 | printing is enabled; if @code{off}, then Python stack printing is | |
19518 | disabled. | |
19519 | @end table | |
19520 | ||
95433b34 JB |
19521 | It is also possible to execute a Python script from the @value{GDBN} |
19522 | interpreter: | |
19523 | ||
19524 | @table @code | |
19525 | @item source @file{script-name} | |
19526 | The script name must end with @samp{.py} and @value{GDBN} must be configured | |
19527 | to recognize the script language based on filename extension using | |
19528 | the @code{script-extension} setting. @xref{Extending GDB, ,Extending GDB}. | |
19529 | ||
19530 | @item python execfile ("script-name") | |
19531 | This method is based on the @code{execfile} Python built-in function, | |
19532 | and thus is always available. | |
19533 | @end table | |
19534 | ||
d57a3c85 TJB |
19535 | @node Python API |
19536 | @subsection Python API | |
19537 | @cindex python api | |
19538 | @cindex programming in python | |
19539 | ||
19540 | @cindex python stdout | |
19541 | @cindex python pagination | |
19542 | At startup, @value{GDBN} overrides Python's @code{sys.stdout} and | |
19543 | @code{sys.stderr} to print using @value{GDBN}'s output-paging streams. | |
19544 | A Python program which outputs to one of these streams may have its | |
19545 | output interrupted by the user (@pxref{Screen Size}). In this | |
19546 | situation, a Python @code{KeyboardInterrupt} exception is thrown. | |
19547 | ||
19548 | @menu | |
19549 | * Basic Python:: Basic Python Functions. | |
19550 | * Exception Handling:: | |
89c73ade | 19551 | * Auto-loading:: Automatically loading Python code. |
a08702d6 | 19552 | * Values From Inferior:: |
2c74e833 | 19553 | * Types In Python:: Python representation of types. |
a6bac58e TT |
19554 | * Pretty Printing:: Pretty-printing values. |
19555 | * Selecting Pretty-Printers:: How GDB chooses a pretty-printer. | |
d8906c6f | 19556 | * Commands In Python:: Implementing new commands in Python. |
bc3b79fd | 19557 | * Functions In Python:: Writing new convenience functions. |
89c73ade | 19558 | * Objfiles In Python:: Object files. |
f3e9a817 PM |
19559 | * Frames In Python:: Accessing inferior stack frames from Python. |
19560 | * Blocks In Python:: Accessing frame blocks from Python. | |
19561 | * Symbols In Python:: Python representation of symbols. | |
19562 | * Symbol Tables In Python:: Python representation of symbol tables. | |
be759fcf | 19563 | * Lazy Strings In Python:: Python representation of lazy strings. |
d57a3c85 TJB |
19564 | @end menu |
19565 | ||
19566 | @node Basic Python | |
19567 | @subsubsection Basic Python | |
19568 | ||
19569 | @cindex python functions | |
19570 | @cindex python module | |
19571 | @cindex gdb module | |
19572 | @value{GDBN} introduces a new Python module, named @code{gdb}. All | |
19573 | methods and classes added by @value{GDBN} are placed in this module. | |
19574 | @value{GDBN} automatically @code{import}s the @code{gdb} module for | |
19575 | use in all scripts evaluated by the @code{python} command. | |
19576 | ||
19577 | @findex gdb.execute | |
12453b93 | 19578 | @defun execute command [from_tty] |
d57a3c85 TJB |
19579 | Evaluate @var{command}, a string, as a @value{GDBN} CLI command. |
19580 | If a GDB exception happens while @var{command} runs, it is | |
19581 | translated as described in @ref{Exception Handling,,Exception Handling}. | |
19582 | If no exceptions occur, this function returns @code{None}. | |
12453b93 TJB |
19583 | |
19584 | @var{from_tty} specifies whether @value{GDBN} ought to consider this | |
19585 | command as having originated from the user invoking it interactively. | |
19586 | It must be a boolean value. If omitted, it defaults to @code{False}. | |
d57a3c85 TJB |
19587 | @end defun |
19588 | ||
8f500870 TT |
19589 | @findex gdb.parameter |
19590 | @defun parameter parameter | |
d57a3c85 TJB |
19591 | Return the value of a @value{GDBN} parameter. @var{parameter} is a |
19592 | string naming the parameter to look up; @var{parameter} may contain | |
19593 | spaces if the parameter has a multi-part name. For example, | |
19594 | @samp{print object} is a valid parameter name. | |
19595 | ||
19596 | If the named parameter does not exist, this function throws a | |
19597 | @code{RuntimeError}. Otherwise, the parameter's value is converted to | |
19598 | a Python value of the appropriate type, and returned. | |
19599 | @end defun | |
19600 | ||
08c637de TJB |
19601 | @findex gdb.history |
19602 | @defun history number | |
19603 | Return a value from @value{GDBN}'s value history (@pxref{Value | |
19604 | History}). @var{number} indicates which history element to return. | |
19605 | If @var{number} is negative, then @value{GDBN} will take its absolute value | |
19606 | and count backward from the last element (i.e., the most recent element) to | |
19607 | find the value to return. If @var{number} is zero, then @value{GDBN} will | |
a0c36267 | 19608 | return the most recent element. If the element specified by @var{number} |
08c637de TJB |
19609 | doesn't exist in the value history, a @code{RuntimeError} exception will be |
19610 | raised. | |
19611 | ||
19612 | If no exception is raised, the return value is always an instance of | |
19613 | @code{gdb.Value} (@pxref{Values From Inferior}). | |
19614 | @end defun | |
19615 | ||
57a1d736 TT |
19616 | @findex gdb.parse_and_eval |
19617 | @defun parse_and_eval expression | |
19618 | Parse @var{expression} as an expression in the current language, | |
19619 | evaluate it, and return the result as a @code{gdb.Value}. | |
19620 | @var{expression} must be a string. | |
19621 | ||
19622 | This function can be useful when implementing a new command | |
19623 | (@pxref{Commands In Python}), as it provides a way to parse the | |
19624 | command's argument as an expression. It is also useful simply to | |
19625 | compute values, for example, it is the only way to get the value of a | |
19626 | convenience variable (@pxref{Convenience Vars}) as a @code{gdb.Value}. | |
19627 | @end defun | |
19628 | ||
d57a3c85 TJB |
19629 | @findex gdb.write |
19630 | @defun write string | |
19631 | Print a string to @value{GDBN}'s paginated standard output stream. | |
19632 | Writing to @code{sys.stdout} or @code{sys.stderr} will automatically | |
19633 | call this function. | |
19634 | @end defun | |
19635 | ||
19636 | @findex gdb.flush | |
19637 | @defun flush | |
19638 | Flush @value{GDBN}'s paginated standard output stream. Flushing | |
19639 | @code{sys.stdout} or @code{sys.stderr} will automatically call this | |
19640 | function. | |
19641 | @end defun | |
19642 | ||
f870a310 TT |
19643 | @findex gdb.target_charset |
19644 | @defun target_charset | |
19645 | Return the name of the current target character set (@pxref{Character | |
19646 | Sets}). This differs from @code{gdb.parameter('target-charset')} in | |
19647 | that @samp{auto} is never returned. | |
19648 | @end defun | |
19649 | ||
19650 | @findex gdb.target_wide_charset | |
19651 | @defun target_wide_charset | |
19652 | Return the name of the current target wide character set | |
19653 | (@pxref{Character Sets}). This differs from | |
19654 | @code{gdb.parameter('target-wide-charset')} in that @samp{auto} is | |
19655 | never returned. | |
19656 | @end defun | |
19657 | ||
d57a3c85 TJB |
19658 | @node Exception Handling |
19659 | @subsubsection Exception Handling | |
19660 | @cindex python exceptions | |
19661 | @cindex exceptions, python | |
19662 | ||
19663 | When executing the @code{python} command, Python exceptions | |
19664 | uncaught within the Python code are translated to calls to | |
19665 | @value{GDBN} error-reporting mechanism. If the command that called | |
19666 | @code{python} does not handle the error, @value{GDBN} will | |
19667 | terminate it and print an error message containing the Python | |
19668 | exception name, the associated value, and the Python call stack | |
19669 | backtrace at the point where the exception was raised. Example: | |
19670 | ||
19671 | @smallexample | |
19672 | (@value{GDBP}) python print foo | |
19673 | Traceback (most recent call last): | |
19674 | File "<string>", line 1, in <module> | |
19675 | NameError: name 'foo' is not defined | |
19676 | @end smallexample | |
19677 | ||
19678 | @value{GDBN} errors that happen in @value{GDBN} commands invoked by Python | |
19679 | code are converted to Python @code{RuntimeError} exceptions. User | |
19680 | interrupt (via @kbd{C-c} or by typing @kbd{q} at a pagination | |
19681 | prompt) is translated to a Python @code{KeyboardInterrupt} | |
19682 | exception. If you catch these exceptions in your Python code, your | |
19683 | exception handler will see @code{RuntimeError} or | |
19684 | @code{KeyboardInterrupt} as the exception type, the @value{GDBN} error | |
19685 | message as its value, and the Python call stack backtrace at the | |
19686 | Python statement closest to where the @value{GDBN} error occured as the | |
19687 | traceback. | |
19688 | ||
89c73ade TT |
19689 | @node Auto-loading |
19690 | @subsubsection Auto-loading | |
19691 | @cindex auto-loading, Python | |
19692 | ||
19693 | When a new object file is read (for example, due to the @code{file} | |
19694 | command, or because the inferior has loaded a shared library), | |
19695 | @value{GDBN} will look for a file named @file{@var{objfile}-gdb.py}, | |
19696 | where @var{objfile} is the object file's real name, formed by ensuring | |
19697 | that the file name is absolute, following all symlinks, and resolving | |
19698 | @code{.} and @code{..} components. If this file exists and is | |
19699 | readable, @value{GDBN} will evaluate it as a Python script. | |
19700 | ||
19701 | If this file does not exist, and if the parameter | |
19702 | @code{debug-file-directory} is set (@pxref{Separate Debug Files}), | |
24ddea62 JK |
19703 | then @value{GDBN} will use for its each separated directory component |
19704 | @code{component} the file named @file{@code{component}/@var{real-name}}, where | |
89c73ade TT |
19705 | @var{real-name} is the object file's real name, as described above. |
19706 | ||
19707 | Finally, if this file does not exist, then @value{GDBN} will look for | |
19708 | a file named @file{@var{data-directory}/python/auto-load/@var{real-name}}, where | |
19709 | @var{data-directory} is @value{GDBN}'s data directory (available via | |
19710 | @code{show data-directory}, @pxref{Data Files}), and @var{real-name} | |
19711 | is the object file's real name, as described above. | |
19712 | ||
19713 | When reading an auto-loaded file, @value{GDBN} sets the ``current | |
19714 | objfile''. This is available via the @code{gdb.current_objfile} | |
19715 | function (@pxref{Objfiles In Python}). This can be useful for | |
19716 | registering objfile-specific pretty-printers. | |
19717 | ||
19718 | The auto-loading feature is useful for supplying application-specific | |
19719 | debugging commands and scripts. You can enable or disable this | |
19720 | feature, and view its current state. | |
19721 | ||
19722 | @table @code | |
19723 | @kindex maint set python auto-load | |
19724 | @item maint set python auto-load [yes|no] | |
19725 | Enable or disable the Python auto-loading feature. | |
19726 | ||
19727 | @kindex show python auto-load | |
19728 | @item show python auto-load | |
19729 | Show whether Python auto-loading is enabled or disabled. | |
19730 | @end table | |
19731 | ||
19732 | @value{GDBN} does not track which files it has already auto-loaded. | |
19733 | So, your @samp{-gdb.py} file should take care to ensure that it may be | |
19734 | evaluated multiple times without error. | |
19735 | ||
a08702d6 TJB |
19736 | @node Values From Inferior |
19737 | @subsubsection Values From Inferior | |
19738 | @cindex values from inferior, with Python | |
19739 | @cindex python, working with values from inferior | |
19740 | ||
19741 | @cindex @code{gdb.Value} | |
19742 | @value{GDBN} provides values it obtains from the inferior program in | |
19743 | an object of type @code{gdb.Value}. @value{GDBN} uses this object | |
19744 | for its internal bookkeeping of the inferior's values, and for | |
19745 | fetching values when necessary. | |
19746 | ||
19747 | Inferior values that are simple scalars can be used directly in | |
19748 | Python expressions that are valid for the value's data type. Here's | |
19749 | an example for an integer or floating-point value @code{some_val}: | |
19750 | ||
19751 | @smallexample | |
19752 | bar = some_val + 2 | |
19753 | @end smallexample | |
19754 | ||
19755 | @noindent | |
19756 | As result of this, @code{bar} will also be a @code{gdb.Value} object | |
19757 | whose values are of the same type as those of @code{some_val}. | |
19758 | ||
19759 | Inferior values that are structures or instances of some class can | |
19760 | be accessed using the Python @dfn{dictionary syntax}. For example, if | |
19761 | @code{some_val} is a @code{gdb.Value} instance holding a structure, you | |
19762 | can access its @code{foo} element with: | |
19763 | ||
19764 | @smallexample | |
19765 | bar = some_val['foo'] | |
19766 | @end smallexample | |
19767 | ||
19768 | Again, @code{bar} will also be a @code{gdb.Value} object. | |
19769 | ||
c0c6f777 | 19770 | The following attributes are provided: |
a08702d6 | 19771 | |
def2b000 | 19772 | @table @code |
2c74e833 | 19773 | @defivar Value address |
c0c6f777 TJB |
19774 | If this object is addressable, this read-only attribute holds a |
19775 | @code{gdb.Value} object representing the address. Otherwise, | |
19776 | this attribute holds @code{None}. | |
2c74e833 | 19777 | @end defivar |
c0c6f777 | 19778 | |
def2b000 | 19779 | @cindex optimized out value in Python |
2c74e833 | 19780 | @defivar Value is_optimized_out |
def2b000 TJB |
19781 | This read-only boolean attribute is true if the compiler optimized out |
19782 | this value, thus it is not available for fetching from the inferior. | |
2c74e833 TT |
19783 | @end defivar |
19784 | ||
19785 | @defivar Value type | |
19786 | The type of this @code{gdb.Value}. The value of this attribute is a | |
19787 | @code{gdb.Type} object. | |
19788 | @end defivar | |
def2b000 TJB |
19789 | @end table |
19790 | ||
19791 | The following methods are provided: | |
19792 | ||
19793 | @table @code | |
14ff2235 PM |
19794 | @defmethod Value cast type |
19795 | Return a new instance of @code{gdb.Value} that is the result of | |
19796 | casting this instance to the type described by @var{type}, which must | |
19797 | be a @code{gdb.Type} object. If the cast cannot be performed for some | |
19798 | reason, this method throws an exception. | |
19799 | @end defmethod | |
19800 | ||
a08702d6 | 19801 | @defmethod Value dereference |
def2b000 TJB |
19802 | For pointer data types, this method returns a new @code{gdb.Value} object |
19803 | whose contents is the object pointed to by the pointer. For example, if | |
19804 | @code{foo} is a C pointer to an @code{int}, declared in your C program as | |
a08702d6 TJB |
19805 | |
19806 | @smallexample | |
19807 | int *foo; | |
19808 | @end smallexample | |
19809 | ||
19810 | @noindent | |
19811 | then you can use the corresponding @code{gdb.Value} to access what | |
19812 | @code{foo} points to like this: | |
19813 | ||
19814 | @smallexample | |
19815 | bar = foo.dereference () | |
19816 | @end smallexample | |
19817 | ||
19818 | The result @code{bar} will be a @code{gdb.Value} object holding the | |
19819 | value pointed to by @code{foo}. | |
19820 | @end defmethod | |
19821 | ||
fbb8f299 | 19822 | @defmethod Value string @r{[}encoding@r{]} @r{[}errors@r{]} @r{[}length@r{]} |
b6cb8e7d TJB |
19823 | If this @code{gdb.Value} represents a string, then this method |
19824 | converts the contents to a Python string. Otherwise, this method will | |
19825 | throw an exception. | |
19826 | ||
19827 | Strings are recognized in a language-specific way; whether a given | |
19828 | @code{gdb.Value} represents a string is determined by the current | |
19829 | language. | |
19830 | ||
19831 | For C-like languages, a value is a string if it is a pointer to or an | |
19832 | array of characters or ints. The string is assumed to be terminated | |
fbb8f299 PM |
19833 | by a zero of the appropriate width. However if the optional length |
19834 | argument is given, the string will be converted to that given length, | |
19835 | ignoring any embedded zeros that the string may contain. | |
b6cb8e7d TJB |
19836 | |
19837 | If the optional @var{encoding} argument is given, it must be a string | |
19838 | naming the encoding of the string in the @code{gdb.Value}, such as | |
19839 | @code{"ascii"}, @code{"iso-8859-6"} or @code{"utf-8"}. It accepts | |
19840 | the same encodings as the corresponding argument to Python's | |
19841 | @code{string.decode} method, and the Python codec machinery will be used | |
19842 | to convert the string. If @var{encoding} is not given, or if | |
19843 | @var{encoding} is the empty string, then either the @code{target-charset} | |
19844 | (@pxref{Character Sets}) will be used, or a language-specific encoding | |
19845 | will be used, if the current language is able to supply one. | |
19846 | ||
19847 | The optional @var{errors} argument is the same as the corresponding | |
19848 | argument to Python's @code{string.decode} method. | |
fbb8f299 PM |
19849 | |
19850 | If the optional @var{length} argument is given, the string will be | |
19851 | fetched and converted to the given length. | |
b6cb8e7d | 19852 | @end defmethod |
be759fcf PM |
19853 | |
19854 | @defmethod Value lazy_string @r{[}encoding@r{]} @r{[}length@r{]} | |
19855 | If this @code{gdb.Value} represents a string, then this method | |
19856 | converts the contents to a @code{gdb.LazyString} (@pxref{Lazy Strings | |
19857 | In Python}). Otherwise, this method will throw an exception. | |
19858 | ||
19859 | If the optional @var{encoding} argument is given, it must be a string | |
19860 | naming the encoding of the @code{gdb.LazyString}. Some examples are: | |
19861 | @samp{ascii}, @samp{iso-8859-6} or @samp{utf-8}. If the | |
19862 | @var{encoding} argument is an encoding that @value{GDBN} does | |
19863 | recognize, @value{GDBN} will raise an error. | |
19864 | ||
19865 | When a lazy string is printed, the @value{GDBN} encoding machinery is | |
19866 | used to convert the string during printing. If the optional | |
19867 | @var{encoding} argument is not provided, or is an empty string, | |
19868 | @value{GDBN} will automatically select the encoding most suitable for | |
19869 | the string type. For further information on encoding in @value{GDBN} | |
19870 | please see @ref{Character Sets}. | |
19871 | ||
19872 | If the optional @var{length} argument is given, the string will be | |
19873 | fetched and encoded to the length of characters specified. If | |
19874 | the @var{length} argument is not provided, the string will be fetched | |
19875 | and encoded until a null of appropriate width is found. | |
19876 | @end defmethod | |
def2b000 | 19877 | @end table |
b6cb8e7d | 19878 | |
2c74e833 TT |
19879 | @node Types In Python |
19880 | @subsubsection Types In Python | |
19881 | @cindex types in Python | |
19882 | @cindex Python, working with types | |
19883 | ||
19884 | @tindex gdb.Type | |
19885 | @value{GDBN} represents types from the inferior using the class | |
19886 | @code{gdb.Type}. | |
19887 | ||
19888 | The following type-related functions are available in the @code{gdb} | |
19889 | module: | |
19890 | ||
19891 | @findex gdb.lookup_type | |
19892 | @defun lookup_type name [block] | |
19893 | This function looks up a type by name. @var{name} is the name of the | |
19894 | type to look up. It must be a string. | |
19895 | ||
5107b149 PM |
19896 | If @var{block} is given, then @var{name} is looked up in that scope. |
19897 | Otherwise, it is searched for globally. | |
19898 | ||
2c74e833 TT |
19899 | Ordinarily, this function will return an instance of @code{gdb.Type}. |
19900 | If the named type cannot be found, it will throw an exception. | |
19901 | @end defun | |
19902 | ||
19903 | An instance of @code{Type} has the following attributes: | |
19904 | ||
19905 | @table @code | |
19906 | @defivar Type code | |
19907 | The type code for this type. The type code will be one of the | |
19908 | @code{TYPE_CODE_} constants defined below. | |
19909 | @end defivar | |
19910 | ||
19911 | @defivar Type sizeof | |
19912 | The size of this type, in target @code{char} units. Usually, a | |
19913 | target's @code{char} type will be an 8-bit byte. However, on some | |
19914 | unusual platforms, this type may have a different size. | |
19915 | @end defivar | |
19916 | ||
19917 | @defivar Type tag | |
19918 | The tag name for this type. The tag name is the name after | |
19919 | @code{struct}, @code{union}, or @code{enum} in C and C@t{++}; not all | |
19920 | languages have this concept. If this type has no tag name, then | |
19921 | @code{None} is returned. | |
19922 | @end defivar | |
19923 | @end table | |
19924 | ||
19925 | The following methods are provided: | |
19926 | ||
19927 | @table @code | |
19928 | @defmethod Type fields | |
19929 | For structure and union types, this method returns the fields. Range | |
19930 | types have two fields, the minimum and maximum values. Enum types | |
19931 | have one field per enum constant. Function and method types have one | |
19932 | field per parameter. The base types of C@t{++} classes are also | |
19933 | represented as fields. If the type has no fields, or does not fit | |
19934 | into one of these categories, an empty sequence will be returned. | |
19935 | ||
19936 | Each field is an object, with some pre-defined attributes: | |
19937 | @table @code | |
19938 | @item bitpos | |
19939 | This attribute is not available for @code{static} fields (as in | |
19940 | C@t{++} or Java). For non-@code{static} fields, the value is the bit | |
19941 | position of the field. | |
19942 | ||
19943 | @item name | |
19944 | The name of the field, or @code{None} for anonymous fields. | |
19945 | ||
19946 | @item artificial | |
19947 | This is @code{True} if the field is artificial, usually meaning that | |
19948 | it was provided by the compiler and not the user. This attribute is | |
19949 | always provided, and is @code{False} if the field is not artificial. | |
19950 | ||
bfd31e71 PM |
19951 | @item is_base_class |
19952 | This is @code{True} if the field represents a base class of a C@t{++} | |
19953 | structure. This attribute is always provided, and is @code{False} | |
19954 | if the field is not a base class of the type that is the argument of | |
19955 | @code{fields}, or if that type was not a C@t{++} class. | |
19956 | ||
2c74e833 TT |
19957 | @item bitsize |
19958 | If the field is packed, or is a bitfield, then this will have a | |
19959 | non-zero value, which is the size of the field in bits. Otherwise, | |
19960 | this will be zero; in this case the field's size is given by its type. | |
19961 | ||
19962 | @item type | |
19963 | The type of the field. This is usually an instance of @code{Type}, | |
19964 | but it can be @code{None} in some situations. | |
19965 | @end table | |
19966 | @end defmethod | |
19967 | ||
19968 | @defmethod Type const | |
19969 | Return a new @code{gdb.Type} object which represents a | |
19970 | @code{const}-qualified variant of this type. | |
19971 | @end defmethod | |
19972 | ||
19973 | @defmethod Type volatile | |
19974 | Return a new @code{gdb.Type} object which represents a | |
19975 | @code{volatile}-qualified variant of this type. | |
19976 | @end defmethod | |
19977 | ||
19978 | @defmethod Type unqualified | |
19979 | Return a new @code{gdb.Type} object which represents an unqualified | |
19980 | variant of this type. That is, the result is neither @code{const} nor | |
19981 | @code{volatile}. | |
19982 | @end defmethod | |
19983 | ||
361ae042 PM |
19984 | @defmethod Type range |
19985 | Return a Python @code{Tuple} object that contains two elements: the | |
19986 | low bound of the argument type and the high bound of that type. If | |
19987 | the type does not have a range, @value{GDBN} will raise a | |
19988 | @code{RuntimeError} exception. | |
19989 | @end defmethod | |
19990 | ||
2c74e833 TT |
19991 | @defmethod Type reference |
19992 | Return a new @code{gdb.Type} object which represents a reference to this | |
19993 | type. | |
19994 | @end defmethod | |
19995 | ||
7a6973ad TT |
19996 | @defmethod Type pointer |
19997 | Return a new @code{gdb.Type} object which represents a pointer to this | |
19998 | type. | |
19999 | @end defmethod | |
20000 | ||
2c74e833 TT |
20001 | @defmethod Type strip_typedefs |
20002 | Return a new @code{gdb.Type} that represents the real type, | |
20003 | after removing all layers of typedefs. | |
20004 | @end defmethod | |
20005 | ||
20006 | @defmethod Type target | |
20007 | Return a new @code{gdb.Type} object which represents the target type | |
20008 | of this type. | |
20009 | ||
20010 | For a pointer type, the target type is the type of the pointed-to | |
20011 | object. For an array type (meaning C-like arrays), the target type is | |
20012 | the type of the elements of the array. For a function or method type, | |
20013 | the target type is the type of the return value. For a complex type, | |
20014 | the target type is the type of the elements. For a typedef, the | |
20015 | target type is the aliased type. | |
20016 | ||
20017 | If the type does not have a target, this method will throw an | |
20018 | exception. | |
20019 | @end defmethod | |
20020 | ||
5107b149 | 20021 | @defmethod Type template_argument n [block] |
2c74e833 TT |
20022 | If this @code{gdb.Type} is an instantiation of a template, this will |
20023 | return a new @code{gdb.Type} which represents the type of the | |
20024 | @var{n}th template argument. | |
20025 | ||
20026 | If this @code{gdb.Type} is not a template type, this will throw an | |
20027 | exception. Ordinarily, only C@t{++} code will have template types. | |
20028 | ||
5107b149 PM |
20029 | If @var{block} is given, then @var{name} is looked up in that scope. |
20030 | Otherwise, it is searched for globally. | |
2c74e833 TT |
20031 | @end defmethod |
20032 | @end table | |
20033 | ||
20034 | ||
20035 | Each type has a code, which indicates what category this type falls | |
20036 | into. The available type categories are represented by constants | |
20037 | defined in the @code{gdb} module: | |
20038 | ||
20039 | @table @code | |
20040 | @findex TYPE_CODE_PTR | |
20041 | @findex gdb.TYPE_CODE_PTR | |
20042 | @item TYPE_CODE_PTR | |
20043 | The type is a pointer. | |
20044 | ||
20045 | @findex TYPE_CODE_ARRAY | |
20046 | @findex gdb.TYPE_CODE_ARRAY | |
20047 | @item TYPE_CODE_ARRAY | |
20048 | The type is an array. | |
20049 | ||
20050 | @findex TYPE_CODE_STRUCT | |
20051 | @findex gdb.TYPE_CODE_STRUCT | |
20052 | @item TYPE_CODE_STRUCT | |
20053 | The type is a structure. | |
20054 | ||
20055 | @findex TYPE_CODE_UNION | |
20056 | @findex gdb.TYPE_CODE_UNION | |
20057 | @item TYPE_CODE_UNION | |
20058 | The type is a union. | |
20059 | ||
20060 | @findex TYPE_CODE_ENUM | |
20061 | @findex gdb.TYPE_CODE_ENUM | |
20062 | @item TYPE_CODE_ENUM | |
20063 | The type is an enum. | |
20064 | ||
20065 | @findex TYPE_CODE_FLAGS | |
20066 | @findex gdb.TYPE_CODE_FLAGS | |
20067 | @item TYPE_CODE_FLAGS | |
20068 | A bit flags type, used for things such as status registers. | |
20069 | ||
20070 | @findex TYPE_CODE_FUNC | |
20071 | @findex gdb.TYPE_CODE_FUNC | |
20072 | @item TYPE_CODE_FUNC | |
20073 | The type is a function. | |
20074 | ||
20075 | @findex TYPE_CODE_INT | |
20076 | @findex gdb.TYPE_CODE_INT | |
20077 | @item TYPE_CODE_INT | |
20078 | The type is an integer type. | |
20079 | ||
20080 | @findex TYPE_CODE_FLT | |
20081 | @findex gdb.TYPE_CODE_FLT | |
20082 | @item TYPE_CODE_FLT | |
20083 | A floating point type. | |
20084 | ||
20085 | @findex TYPE_CODE_VOID | |
20086 | @findex gdb.TYPE_CODE_VOID | |
20087 | @item TYPE_CODE_VOID | |
20088 | The special type @code{void}. | |
20089 | ||
20090 | @findex TYPE_CODE_SET | |
20091 | @findex gdb.TYPE_CODE_SET | |
20092 | @item TYPE_CODE_SET | |
20093 | A Pascal set type. | |
20094 | ||
20095 | @findex TYPE_CODE_RANGE | |
20096 | @findex gdb.TYPE_CODE_RANGE | |
20097 | @item TYPE_CODE_RANGE | |
20098 | A range type, that is, an integer type with bounds. | |
20099 | ||
20100 | @findex TYPE_CODE_STRING | |
20101 | @findex gdb.TYPE_CODE_STRING | |
20102 | @item TYPE_CODE_STRING | |
20103 | A string type. Note that this is only used for certain languages with | |
20104 | language-defined string types; C strings are not represented this way. | |
20105 | ||
20106 | @findex TYPE_CODE_BITSTRING | |
20107 | @findex gdb.TYPE_CODE_BITSTRING | |
20108 | @item TYPE_CODE_BITSTRING | |
20109 | A string of bits. | |
20110 | ||
20111 | @findex TYPE_CODE_ERROR | |
20112 | @findex gdb.TYPE_CODE_ERROR | |
20113 | @item TYPE_CODE_ERROR | |
20114 | An unknown or erroneous type. | |
20115 | ||
20116 | @findex TYPE_CODE_METHOD | |
20117 | @findex gdb.TYPE_CODE_METHOD | |
20118 | @item TYPE_CODE_METHOD | |
20119 | A method type, as found in C@t{++} or Java. | |
20120 | ||
20121 | @findex TYPE_CODE_METHODPTR | |
20122 | @findex gdb.TYPE_CODE_METHODPTR | |
20123 | @item TYPE_CODE_METHODPTR | |
20124 | A pointer-to-member-function. | |
20125 | ||
20126 | @findex TYPE_CODE_MEMBERPTR | |
20127 | @findex gdb.TYPE_CODE_MEMBERPTR | |
20128 | @item TYPE_CODE_MEMBERPTR | |
20129 | A pointer-to-member. | |
20130 | ||
20131 | @findex TYPE_CODE_REF | |
20132 | @findex gdb.TYPE_CODE_REF | |
20133 | @item TYPE_CODE_REF | |
20134 | A reference type. | |
20135 | ||
20136 | @findex TYPE_CODE_CHAR | |
20137 | @findex gdb.TYPE_CODE_CHAR | |
20138 | @item TYPE_CODE_CHAR | |
20139 | A character type. | |
20140 | ||
20141 | @findex TYPE_CODE_BOOL | |
20142 | @findex gdb.TYPE_CODE_BOOL | |
20143 | @item TYPE_CODE_BOOL | |
20144 | A boolean type. | |
20145 | ||
20146 | @findex TYPE_CODE_COMPLEX | |
20147 | @findex gdb.TYPE_CODE_COMPLEX | |
20148 | @item TYPE_CODE_COMPLEX | |
20149 | A complex float type. | |
20150 | ||
20151 | @findex TYPE_CODE_TYPEDEF | |
20152 | @findex gdb.TYPE_CODE_TYPEDEF | |
20153 | @item TYPE_CODE_TYPEDEF | |
20154 | A typedef to some other type. | |
20155 | ||
20156 | @findex TYPE_CODE_NAMESPACE | |
20157 | @findex gdb.TYPE_CODE_NAMESPACE | |
20158 | @item TYPE_CODE_NAMESPACE | |
20159 | A C@t{++} namespace. | |
20160 | ||
20161 | @findex TYPE_CODE_DECFLOAT | |
20162 | @findex gdb.TYPE_CODE_DECFLOAT | |
20163 | @item TYPE_CODE_DECFLOAT | |
20164 | A decimal floating point type. | |
20165 | ||
20166 | @findex TYPE_CODE_INTERNAL_FUNCTION | |
20167 | @findex gdb.TYPE_CODE_INTERNAL_FUNCTION | |
20168 | @item TYPE_CODE_INTERNAL_FUNCTION | |
20169 | A function internal to @value{GDBN}. This is the type used to represent | |
20170 | convenience functions. | |
20171 | @end table | |
20172 | ||
a6bac58e TT |
20173 | @node Pretty Printing |
20174 | @subsubsection Pretty Printing | |
20175 | ||
20176 | @value{GDBN} provides a mechanism to allow pretty-printing of values | |
20177 | using Python code. The pretty-printer API allows application-specific | |
20178 | code to greatly simplify the display of complex objects. This | |
20179 | mechanism works for both MI and the CLI. | |
20180 | ||
20181 | For example, here is how a C@t{++} @code{std::string} looks without a | |
20182 | pretty-printer: | |
20183 | ||
20184 | @smallexample | |
20185 | (@value{GDBP}) print s | |
20186 | $1 = @{ | |
20187 | static npos = 4294967295, | |
20188 | _M_dataplus = @{ | |
20189 | <std::allocator<char>> = @{ | |
20190 | <__gnu_cxx::new_allocator<char>> = @{<No data fields>@}, <No data fields>@}, | |
20191 | members of std::basic_string<char, std::char_traits<char>, std::allocator<char> >::_Alloc_hider: | |
20192 | _M_p = 0x804a014 "abcd" | |
20193 | @} | |
20194 | @} | |
20195 | @end smallexample | |
20196 | ||
20197 | After a pretty-printer for @code{std::string} has been installed, only | |
20198 | the contents are printed: | |
20199 | ||
20200 | @smallexample | |
20201 | (@value{GDBP}) print s | |
20202 | $2 = "abcd" | |
20203 | @end smallexample | |
20204 | ||
20205 | A pretty-printer is just an object that holds a value and implements a | |
20206 | specific interface, defined here. | |
20207 | ||
20208 | @defop Operation {pretty printer} children (self) | |
20209 | @value{GDBN} will call this method on a pretty-printer to compute the | |
20210 | children of the pretty-printer's value. | |
20211 | ||
20212 | This method must return an object conforming to the Python iterator | |
20213 | protocol. Each item returned by the iterator must be a tuple holding | |
20214 | two elements. The first element is the ``name'' of the child; the | |
20215 | second element is the child's value. The value can be any Python | |
20216 | object which is convertible to a @value{GDBN} value. | |
20217 | ||
20218 | This method is optional. If it does not exist, @value{GDBN} will act | |
20219 | as though the value has no children. | |
20220 | @end defop | |
20221 | ||
20222 | @defop Operation {pretty printer} display_hint (self) | |
20223 | The CLI may call this method and use its result to change the | |
20224 | formatting of a value. The result will also be supplied to an MI | |
20225 | consumer as a @samp{displayhint} attribute of the variable being | |
20226 | printed. | |
20227 | ||
20228 | This method is optional. If it does exist, this method must return a | |
20229 | string. | |
20230 | ||
20231 | Some display hints are predefined by @value{GDBN}: | |
20232 | ||
20233 | @table @samp | |
20234 | @item array | |
20235 | Indicate that the object being printed is ``array-like''. The CLI | |
20236 | uses this to respect parameters such as @code{set print elements} and | |
20237 | @code{set print array}. | |
20238 | ||
20239 | @item map | |
20240 | Indicate that the object being printed is ``map-like'', and that the | |
20241 | children of this value can be assumed to alternate between keys and | |
20242 | values. | |
20243 | ||
20244 | @item string | |
20245 | Indicate that the object being printed is ``string-like''. If the | |
20246 | printer's @code{to_string} method returns a Python string of some | |
20247 | kind, then @value{GDBN} will call its internal language-specific | |
20248 | string-printing function to format the string. For the CLI this means | |
20249 | adding quotation marks, possibly escaping some characters, respecting | |
20250 | @code{set print elements}, and the like. | |
20251 | @end table | |
20252 | @end defop | |
20253 | ||
20254 | @defop Operation {pretty printer} to_string (self) | |
20255 | @value{GDBN} will call this method to display the string | |
20256 | representation of the value passed to the object's constructor. | |
20257 | ||
20258 | When printing from the CLI, if the @code{to_string} method exists, | |
20259 | then @value{GDBN} will prepend its result to the values returned by | |
20260 | @code{children}. Exactly how this formatting is done is dependent on | |
20261 | the display hint, and may change as more hints are added. Also, | |
20262 | depending on the print settings (@pxref{Print Settings}), the CLI may | |
20263 | print just the result of @code{to_string} in a stack trace, omitting | |
20264 | the result of @code{children}. | |
20265 | ||
20266 | If this method returns a string, it is printed verbatim. | |
20267 | ||
20268 | Otherwise, if this method returns an instance of @code{gdb.Value}, | |
20269 | then @value{GDBN} prints this value. This may result in a call to | |
20270 | another pretty-printer. | |
20271 | ||
20272 | If instead the method returns a Python value which is convertible to a | |
20273 | @code{gdb.Value}, then @value{GDBN} performs the conversion and prints | |
20274 | the resulting value. Again, this may result in a call to another | |
20275 | pretty-printer. Python scalars (integers, floats, and booleans) and | |
20276 | strings are convertible to @code{gdb.Value}; other types are not. | |
20277 | ||
20278 | If the result is not one of these types, an exception is raised. | |
20279 | @end defop | |
20280 | ||
20281 | @node Selecting Pretty-Printers | |
20282 | @subsubsection Selecting Pretty-Printers | |
20283 | ||
20284 | The Python list @code{gdb.pretty_printers} contains an array of | |
20285 | functions that have been registered via addition as a pretty-printer. | |
20286 | Each @code{gdb.Objfile} also contains a @code{pretty_printers} | |
20287 | attribute. | |
20288 | ||
20289 | A function on one of these lists is passed a single @code{gdb.Value} | |
20290 | argument and should return a pretty-printer object conforming to the | |
20291 | interface definition above (@pxref{Pretty Printing}). If a function | |
20292 | cannot create a pretty-printer for the value, it should return | |
20293 | @code{None}. | |
20294 | ||
20295 | @value{GDBN} first checks the @code{pretty_printers} attribute of each | |
20296 | @code{gdb.Objfile} and iteratively calls each function in the list for | |
20297 | that @code{gdb.Objfile} until it receives a pretty-printer object. | |
20298 | After these lists have been exhausted, it tries the global | |
20299 | @code{gdb.pretty-printers} list, again calling each function until an | |
20300 | object is returned. | |
20301 | ||
20302 | The order in which the objfiles are searched is not specified. For a | |
20303 | given list, functions are always invoked from the head of the list, | |
20304 | and iterated over sequentially until the end of the list, or a printer | |
20305 | object is returned. | |
20306 | ||
20307 | Here is an example showing how a @code{std::string} printer might be | |
20308 | written: | |
20309 | ||
20310 | @smallexample | |
20311 | class StdStringPrinter: | |
20312 | "Print a std::string" | |
20313 | ||
20314 | def __init__ (self, val): | |
20315 | self.val = val | |
20316 | ||
20317 | def to_string (self): | |
20318 | return self.val['_M_dataplus']['_M_p'] | |
20319 | ||
20320 | def display_hint (self): | |
20321 | return 'string' | |
20322 | @end smallexample | |
20323 | ||
20324 | And here is an example showing how a lookup function for the printer | |
20325 | example above might be written. | |
20326 | ||
20327 | @smallexample | |
20328 | def str_lookup_function (val): | |
20329 | ||
20330 | lookup_tag = val.type.tag | |
20331 | regex = re.compile ("^std::basic_string<char,.*>$") | |
20332 | if lookup_tag == None: | |
20333 | return None | |
20334 | if regex.match (lookup_tag): | |
20335 | return StdStringPrinter (val) | |
20336 | ||
20337 | return None | |
20338 | @end smallexample | |
20339 | ||
20340 | The example lookup function extracts the value's type, and attempts to | |
20341 | match it to a type that it can pretty-print. If it is a type the | |
20342 | printer can pretty-print, it will return a printer object. If not, it | |
20343 | returns @code{None}. | |
20344 | ||
20345 | We recommend that you put your core pretty-printers into a Python | |
20346 | package. If your pretty-printers are for use with a library, we | |
20347 | further recommend embedding a version number into the package name. | |
20348 | This practice will enable @value{GDBN} to load multiple versions of | |
20349 | your pretty-printers at the same time, because they will have | |
20350 | different names. | |
20351 | ||
20352 | You should write auto-loaded code (@pxref{Auto-loading}) such that it | |
20353 | can be evaluated multiple times without changing its meaning. An | |
20354 | ideal auto-load file will consist solely of @code{import}s of your | |
20355 | printer modules, followed by a call to a register pretty-printers with | |
20356 | the current objfile. | |
20357 | ||
20358 | Taken as a whole, this approach will scale nicely to multiple | |
20359 | inferiors, each potentially using a different library version. | |
20360 | Embedding a version number in the Python package name will ensure that | |
20361 | @value{GDBN} is able to load both sets of printers simultaneously. | |
20362 | Then, because the search for pretty-printers is done by objfile, and | |
20363 | because your auto-loaded code took care to register your library's | |
20364 | printers with a specific objfile, @value{GDBN} will find the correct | |
20365 | printers for the specific version of the library used by each | |
20366 | inferior. | |
20367 | ||
20368 | To continue the @code{std::string} example (@pxref{Pretty Printing}), | |
20369 | this code might appear in @code{gdb.libstdcxx.v6}: | |
20370 | ||
20371 | @smallexample | |
20372 | def register_printers (objfile): | |
20373 | objfile.pretty_printers.add (str_lookup_function) | |
20374 | @end smallexample | |
20375 | ||
20376 | @noindent | |
20377 | And then the corresponding contents of the auto-load file would be: | |
20378 | ||
20379 | @smallexample | |
20380 | import gdb.libstdcxx.v6 | |
20381 | gdb.libstdcxx.v6.register_printers (gdb.current_objfile ()) | |
20382 | @end smallexample | |
20383 | ||
d8906c6f TJB |
20384 | @node Commands In Python |
20385 | @subsubsection Commands In Python | |
20386 | ||
20387 | @cindex commands in python | |
20388 | @cindex python commands | |
d8906c6f TJB |
20389 | You can implement new @value{GDBN} CLI commands in Python. A CLI |
20390 | command is implemented using an instance of the @code{gdb.Command} | |
20391 | class, most commonly using a subclass. | |
20392 | ||
cc924cad | 20393 | @defmethod Command __init__ name @var{command_class} @r{[}@var{completer_class}@r{]} @r{[}@var{prefix}@r{]} |
d8906c6f TJB |
20394 | The object initializer for @code{Command} registers the new command |
20395 | with @value{GDBN}. This initializer is normally invoked from the | |
20396 | subclass' own @code{__init__} method. | |
20397 | ||
20398 | @var{name} is the name of the command. If @var{name} consists of | |
20399 | multiple words, then the initial words are looked for as prefix | |
20400 | commands. In this case, if one of the prefix commands does not exist, | |
20401 | an exception is raised. | |
20402 | ||
20403 | There is no support for multi-line commands. | |
20404 | ||
cc924cad | 20405 | @var{command_class} should be one of the @samp{COMMAND_} constants |
d8906c6f TJB |
20406 | defined below. This argument tells @value{GDBN} how to categorize the |
20407 | new command in the help system. | |
20408 | ||
cc924cad | 20409 | @var{completer_class} is an optional argument. If given, it should be |
d8906c6f TJB |
20410 | one of the @samp{COMPLETE_} constants defined below. This argument |
20411 | tells @value{GDBN} how to perform completion for this command. If not | |
20412 | given, @value{GDBN} will attempt to complete using the object's | |
20413 | @code{complete} method (see below); if no such method is found, an | |
20414 | error will occur when completion is attempted. | |
20415 | ||
20416 | @var{prefix} is an optional argument. If @code{True}, then the new | |
20417 | command is a prefix command; sub-commands of this command may be | |
20418 | registered. | |
20419 | ||
20420 | The help text for the new command is taken from the Python | |
20421 | documentation string for the command's class, if there is one. If no | |
20422 | documentation string is provided, the default value ``This command is | |
20423 | not documented.'' is used. | |
20424 | @end defmethod | |
20425 | ||
a0c36267 | 20426 | @cindex don't repeat Python command |
d8906c6f TJB |
20427 | @defmethod Command dont_repeat |
20428 | By default, a @value{GDBN} command is repeated when the user enters a | |
20429 | blank line at the command prompt. A command can suppress this | |
20430 | behavior by invoking the @code{dont_repeat} method. This is similar | |
20431 | to the user command @code{dont-repeat}, see @ref{Define, dont-repeat}. | |
20432 | @end defmethod | |
20433 | ||
20434 | @defmethod Command invoke argument from_tty | |
20435 | This method is called by @value{GDBN} when this command is invoked. | |
20436 | ||
20437 | @var{argument} is a string. It is the argument to the command, after | |
20438 | leading and trailing whitespace has been stripped. | |
20439 | ||
20440 | @var{from_tty} is a boolean argument. When true, this means that the | |
20441 | command was entered by the user at the terminal; when false it means | |
20442 | that the command came from elsewhere. | |
20443 | ||
20444 | If this method throws an exception, it is turned into a @value{GDBN} | |
20445 | @code{error} call. Otherwise, the return value is ignored. | |
20446 | @end defmethod | |
20447 | ||
a0c36267 | 20448 | @cindex completion of Python commands |
d8906c6f TJB |
20449 | @defmethod Command complete text word |
20450 | This method is called by @value{GDBN} when the user attempts | |
20451 | completion on this command. All forms of completion are handled by | |
a0c36267 EZ |
20452 | this method, that is, the @key{TAB} and @key{M-?} key bindings |
20453 | (@pxref{Completion}), and the @code{complete} command (@pxref{Help, | |
20454 | complete}). | |
d8906c6f TJB |
20455 | |
20456 | The arguments @var{text} and @var{word} are both strings. @var{text} | |
20457 | holds the complete command line up to the cursor's location. | |
20458 | @var{word} holds the last word of the command line; this is computed | |
20459 | using a word-breaking heuristic. | |
20460 | ||
20461 | The @code{complete} method can return several values: | |
20462 | @itemize @bullet | |
20463 | @item | |
20464 | If the return value is a sequence, the contents of the sequence are | |
20465 | used as the completions. It is up to @code{complete} to ensure that the | |
20466 | contents actually do complete the word. A zero-length sequence is | |
20467 | allowed, it means that there were no completions available. Only | |
20468 | string elements of the sequence are used; other elements in the | |
20469 | sequence are ignored. | |
20470 | ||
20471 | @item | |
20472 | If the return value is one of the @samp{COMPLETE_} constants defined | |
20473 | below, then the corresponding @value{GDBN}-internal completion | |
20474 | function is invoked, and its result is used. | |
20475 | ||
20476 | @item | |
20477 | All other results are treated as though there were no available | |
20478 | completions. | |
20479 | @end itemize | |
20480 | @end defmethod | |
20481 | ||
d8906c6f TJB |
20482 | When a new command is registered, it must be declared as a member of |
20483 | some general class of commands. This is used to classify top-level | |
20484 | commands in the on-line help system; note that prefix commands are not | |
20485 | listed under their own category but rather that of their top-level | |
20486 | command. The available classifications are represented by constants | |
20487 | defined in the @code{gdb} module: | |
20488 | ||
20489 | @table @code | |
20490 | @findex COMMAND_NONE | |
20491 | @findex gdb.COMMAND_NONE | |
20492 | @item COMMAND_NONE | |
20493 | The command does not belong to any particular class. A command in | |
20494 | this category will not be displayed in any of the help categories. | |
20495 | ||
20496 | @findex COMMAND_RUNNING | |
20497 | @findex gdb.COMMAND_RUNNING | |
a0c36267 | 20498 | @item COMMAND_RUNNING |
d8906c6f TJB |
20499 | The command is related to running the inferior. For example, |
20500 | @code{start}, @code{step}, and @code{continue} are in this category. | |
a0c36267 | 20501 | Type @kbd{help running} at the @value{GDBN} prompt to see a list of |
d8906c6f TJB |
20502 | commands in this category. |
20503 | ||
20504 | @findex COMMAND_DATA | |
20505 | @findex gdb.COMMAND_DATA | |
a0c36267 | 20506 | @item COMMAND_DATA |
d8906c6f TJB |
20507 | The command is related to data or variables. For example, |
20508 | @code{call}, @code{find}, and @code{print} are in this category. Type | |
a0c36267 | 20509 | @kbd{help data} at the @value{GDBN} prompt to see a list of commands |
d8906c6f TJB |
20510 | in this category. |
20511 | ||
20512 | @findex COMMAND_STACK | |
20513 | @findex gdb.COMMAND_STACK | |
20514 | @item COMMAND_STACK | |
20515 | The command has to do with manipulation of the stack. For example, | |
20516 | @code{backtrace}, @code{frame}, and @code{return} are in this | |
a0c36267 | 20517 | category. Type @kbd{help stack} at the @value{GDBN} prompt to see a |
d8906c6f TJB |
20518 | list of commands in this category. |
20519 | ||
20520 | @findex COMMAND_FILES | |
20521 | @findex gdb.COMMAND_FILES | |
20522 | @item COMMAND_FILES | |
20523 | This class is used for file-related commands. For example, | |
20524 | @code{file}, @code{list} and @code{section} are in this category. | |
a0c36267 | 20525 | Type @kbd{help files} at the @value{GDBN} prompt to see a list of |
d8906c6f TJB |
20526 | commands in this category. |
20527 | ||
20528 | @findex COMMAND_SUPPORT | |
20529 | @findex gdb.COMMAND_SUPPORT | |
20530 | @item COMMAND_SUPPORT | |
20531 | This should be used for ``support facilities'', generally meaning | |
20532 | things that are useful to the user when interacting with @value{GDBN}, | |
20533 | but not related to the state of the inferior. For example, | |
20534 | @code{help}, @code{make}, and @code{shell} are in this category. Type | |
a0c36267 | 20535 | @kbd{help support} at the @value{GDBN} prompt to see a list of |
d8906c6f TJB |
20536 | commands in this category. |
20537 | ||
20538 | @findex COMMAND_STATUS | |
20539 | @findex gdb.COMMAND_STATUS | |
a0c36267 | 20540 | @item COMMAND_STATUS |
d8906c6f TJB |
20541 | The command is an @samp{info}-related command, that is, related to the |
20542 | state of @value{GDBN} itself. For example, @code{info}, @code{macro}, | |
a0c36267 | 20543 | and @code{show} are in this category. Type @kbd{help status} at the |
d8906c6f TJB |
20544 | @value{GDBN} prompt to see a list of commands in this category. |
20545 | ||
20546 | @findex COMMAND_BREAKPOINTS | |
20547 | @findex gdb.COMMAND_BREAKPOINTS | |
a0c36267 | 20548 | @item COMMAND_BREAKPOINTS |
d8906c6f | 20549 | The command has to do with breakpoints. For example, @code{break}, |
a0c36267 | 20550 | @code{clear}, and @code{delete} are in this category. Type @kbd{help |
d8906c6f TJB |
20551 | breakpoints} at the @value{GDBN} prompt to see a list of commands in |
20552 | this category. | |
20553 | ||
20554 | @findex COMMAND_TRACEPOINTS | |
20555 | @findex gdb.COMMAND_TRACEPOINTS | |
a0c36267 | 20556 | @item COMMAND_TRACEPOINTS |
d8906c6f TJB |
20557 | The command has to do with tracepoints. For example, @code{trace}, |
20558 | @code{actions}, and @code{tfind} are in this category. Type | |
a0c36267 | 20559 | @kbd{help tracepoints} at the @value{GDBN} prompt to see a list of |
d8906c6f TJB |
20560 | commands in this category. |
20561 | ||
20562 | @findex COMMAND_OBSCURE | |
20563 | @findex gdb.COMMAND_OBSCURE | |
20564 | @item COMMAND_OBSCURE | |
20565 | The command is only used in unusual circumstances, or is not of | |
20566 | general interest to users. For example, @code{checkpoint}, | |
a0c36267 | 20567 | @code{fork}, and @code{stop} are in this category. Type @kbd{help |
d8906c6f TJB |
20568 | obscure} at the @value{GDBN} prompt to see a list of commands in this |
20569 | category. | |
20570 | ||
20571 | @findex COMMAND_MAINTENANCE | |
20572 | @findex gdb.COMMAND_MAINTENANCE | |
20573 | @item COMMAND_MAINTENANCE | |
20574 | The command is only useful to @value{GDBN} maintainers. The | |
20575 | @code{maintenance} and @code{flushregs} commands are in this category. | |
a0c36267 | 20576 | Type @kbd{help internals} at the @value{GDBN} prompt to see a list of |
d8906c6f TJB |
20577 | commands in this category. |
20578 | @end table | |
20579 | ||
d8906c6f TJB |
20580 | A new command can use a predefined completion function, either by |
20581 | specifying it via an argument at initialization, or by returning it | |
20582 | from the @code{complete} method. These predefined completion | |
20583 | constants are all defined in the @code{gdb} module: | |
20584 | ||
20585 | @table @code | |
20586 | @findex COMPLETE_NONE | |
20587 | @findex gdb.COMPLETE_NONE | |
20588 | @item COMPLETE_NONE | |
20589 | This constant means that no completion should be done. | |
20590 | ||
20591 | @findex COMPLETE_FILENAME | |
20592 | @findex gdb.COMPLETE_FILENAME | |
20593 | @item COMPLETE_FILENAME | |
20594 | This constant means that filename completion should be performed. | |
20595 | ||
20596 | @findex COMPLETE_LOCATION | |
20597 | @findex gdb.COMPLETE_LOCATION | |
20598 | @item COMPLETE_LOCATION | |
20599 | This constant means that location completion should be done. | |
20600 | @xref{Specify Location}. | |
20601 | ||
20602 | @findex COMPLETE_COMMAND | |
20603 | @findex gdb.COMPLETE_COMMAND | |
20604 | @item COMPLETE_COMMAND | |
20605 | This constant means that completion should examine @value{GDBN} | |
20606 | command names. | |
20607 | ||
20608 | @findex COMPLETE_SYMBOL | |
20609 | @findex gdb.COMPLETE_SYMBOL | |
20610 | @item COMPLETE_SYMBOL | |
20611 | This constant means that completion should be done using symbol names | |
20612 | as the source. | |
20613 | @end table | |
20614 | ||
20615 | The following code snippet shows how a trivial CLI command can be | |
20616 | implemented in Python: | |
20617 | ||
20618 | @smallexample | |
20619 | class HelloWorld (gdb.Command): | |
20620 | """Greet the whole world.""" | |
20621 | ||
20622 | def __init__ (self): | |
20623 | super (HelloWorld, self).__init__ ("hello-world", gdb.COMMAND_OBSCURE) | |
20624 | ||
20625 | def invoke (self, arg, from_tty): | |
20626 | print "Hello, World!" | |
20627 | ||
20628 | HelloWorld () | |
20629 | @end smallexample | |
20630 | ||
20631 | The last line instantiates the class, and is necessary to trigger the | |
20632 | registration of the command with @value{GDBN}. Depending on how the | |
20633 | Python code is read into @value{GDBN}, you may need to import the | |
20634 | @code{gdb} module explicitly. | |
20635 | ||
bc3b79fd TJB |
20636 | @node Functions In Python |
20637 | @subsubsection Writing new convenience functions | |
20638 | ||
20639 | @cindex writing convenience functions | |
20640 | @cindex convenience functions in python | |
20641 | @cindex python convenience functions | |
20642 | @tindex gdb.Function | |
20643 | @tindex Function | |
20644 | You can implement new convenience functions (@pxref{Convenience Vars}) | |
20645 | in Python. A convenience function is an instance of a subclass of the | |
20646 | class @code{gdb.Function}. | |
20647 | ||
20648 | @defmethod Function __init__ name | |
20649 | The initializer for @code{Function} registers the new function with | |
20650 | @value{GDBN}. The argument @var{name} is the name of the function, | |
20651 | a string. The function will be visible to the user as a convenience | |
20652 | variable of type @code{internal function}, whose name is the same as | |
20653 | the given @var{name}. | |
20654 | ||
20655 | The documentation for the new function is taken from the documentation | |
20656 | string for the new class. | |
20657 | @end defmethod | |
20658 | ||
20659 | @defmethod Function invoke @var{*args} | |
20660 | When a convenience function is evaluated, its arguments are converted | |
20661 | to instances of @code{gdb.Value}, and then the function's | |
20662 | @code{invoke} method is called. Note that @value{GDBN} does not | |
20663 | predetermine the arity of convenience functions. Instead, all | |
20664 | available arguments are passed to @code{invoke}, following the | |
20665 | standard Python calling convention. In particular, a convenience | |
20666 | function can have default values for parameters without ill effect. | |
20667 | ||
20668 | The return value of this method is used as its value in the enclosing | |
20669 | expression. If an ordinary Python value is returned, it is converted | |
20670 | to a @code{gdb.Value} following the usual rules. | |
20671 | @end defmethod | |
20672 | ||
20673 | The following code snippet shows how a trivial convenience function can | |
20674 | be implemented in Python: | |
20675 | ||
20676 | @smallexample | |
20677 | class Greet (gdb.Function): | |
20678 | """Return string to greet someone. | |
20679 | Takes a name as argument.""" | |
20680 | ||
20681 | def __init__ (self): | |
20682 | super (Greet, self).__init__ ("greet") | |
20683 | ||
20684 | def invoke (self, name): | |
20685 | return "Hello, %s!" % name.string () | |
20686 | ||
20687 | Greet () | |
20688 | @end smallexample | |
20689 | ||
20690 | The last line instantiates the class, and is necessary to trigger the | |
20691 | registration of the function with @value{GDBN}. Depending on how the | |
20692 | Python code is read into @value{GDBN}, you may need to import the | |
20693 | @code{gdb} module explicitly. | |
20694 | ||
89c73ade TT |
20695 | @node Objfiles In Python |
20696 | @subsubsection Objfiles In Python | |
20697 | ||
20698 | @cindex objfiles in python | |
20699 | @tindex gdb.Objfile | |
20700 | @tindex Objfile | |
20701 | @value{GDBN} loads symbols for an inferior from various | |
20702 | symbol-containing files (@pxref{Files}). These include the primary | |
20703 | executable file, any shared libraries used by the inferior, and any | |
20704 | separate debug info files (@pxref{Separate Debug Files}). | |
20705 | @value{GDBN} calls these symbol-containing files @dfn{objfiles}. | |
20706 | ||
20707 | The following objfile-related functions are available in the | |
20708 | @code{gdb} module: | |
20709 | ||
20710 | @findex gdb.current_objfile | |
20711 | @defun current_objfile | |
20712 | When auto-loading a Python script (@pxref{Auto-loading}), @value{GDBN} | |
20713 | sets the ``current objfile'' to the corresponding objfile. This | |
20714 | function returns the current objfile. If there is no current objfile, | |
20715 | this function returns @code{None}. | |
20716 | @end defun | |
20717 | ||
20718 | @findex gdb.objfiles | |
20719 | @defun objfiles | |
20720 | Return a sequence of all the objfiles current known to @value{GDBN}. | |
20721 | @xref{Objfiles In Python}. | |
20722 | @end defun | |
20723 | ||
20724 | Each objfile is represented by an instance of the @code{gdb.Objfile} | |
20725 | class. | |
20726 | ||
20727 | @defivar Objfile filename | |
20728 | The file name of the objfile as a string. | |
20729 | @end defivar | |
20730 | ||
20731 | @defivar Objfile pretty_printers | |
20732 | The @code{pretty_printers} attribute is a list of functions. It is | |
20733 | used to look up pretty-printers. A @code{Value} is passed to each | |
20734 | function in order; if the function returns @code{None}, then the | |
20735 | search continues. Otherwise, the return value should be an object | |
a6bac58e TT |
20736 | which is used to format the value. @xref{Pretty Printing}, for more |
20737 | information. | |
89c73ade TT |
20738 | @end defivar |
20739 | ||
f8f6f20b | 20740 | @node Frames In Python |
f3e9a817 | 20741 | @subsubsection Accessing inferior stack frames from Python. |
f8f6f20b TJB |
20742 | |
20743 | @cindex frames in python | |
20744 | When the debugged program stops, @value{GDBN} is able to analyze its call | |
20745 | stack (@pxref{Frames,,Stack frames}). The @code{gdb.Frame} class | |
20746 | represents a frame in the stack. A @code{gdb.Frame} object is only valid | |
20747 | while its corresponding frame exists in the inferior's stack. If you try | |
20748 | to use an invalid frame object, @value{GDBN} will throw a @code{RuntimeError} | |
20749 | exception. | |
20750 | ||
20751 | Two @code{gdb.Frame} objects can be compared for equality with the @code{==} | |
20752 | operator, like: | |
20753 | ||
20754 | @smallexample | |
20755 | (@value{GDBP}) python print gdb.newest_frame() == gdb.selected_frame () | |
20756 | True | |
20757 | @end smallexample | |
20758 | ||
20759 | The following frame-related functions are available in the @code{gdb} module: | |
20760 | ||
20761 | @findex gdb.selected_frame | |
20762 | @defun selected_frame | |
20763 | Return the selected frame object. (@pxref{Selection,,Selecting a Frame}). | |
20764 | @end defun | |
20765 | ||
20766 | @defun frame_stop_reason_string reason | |
20767 | Return a string explaining the reason why @value{GDBN} stopped unwinding | |
20768 | frames, as expressed by the given @var{reason} code (an integer, see the | |
20769 | @code{unwind_stop_reason} method further down in this section). | |
20770 | @end defun | |
20771 | ||
20772 | A @code{gdb.Frame} object has the following methods: | |
20773 | ||
20774 | @table @code | |
20775 | @defmethod Frame is_valid | |
20776 | Returns true if the @code{gdb.Frame} object is valid, false if not. | |
20777 | A frame object can become invalid if the frame it refers to doesn't | |
20778 | exist anymore in the inferior. All @code{gdb.Frame} methods will throw | |
20779 | an exception if it is invalid at the time the method is called. | |
20780 | @end defmethod | |
20781 | ||
20782 | @defmethod Frame name | |
20783 | Returns the function name of the frame, or @code{None} if it can't be | |
20784 | obtained. | |
20785 | @end defmethod | |
20786 | ||
20787 | @defmethod Frame type | |
20788 | Returns the type of the frame. The value can be one of | |
20789 | @code{gdb.NORMAL_FRAME}, @code{gdb.DUMMY_FRAME}, @code{gdb.SIGTRAMP_FRAME} | |
20790 | or @code{gdb.SENTINEL_FRAME}. | |
20791 | @end defmethod | |
20792 | ||
20793 | @defmethod Frame unwind_stop_reason | |
20794 | Return an integer representing the reason why it's not possible to find | |
20795 | more frames toward the outermost frame. Use | |
20796 | @code{gdb.frame_stop_reason_string} to convert the value returned by this | |
20797 | function to a string. | |
20798 | @end defmethod | |
20799 | ||
20800 | @defmethod Frame pc | |
20801 | Returns the frame's resume address. | |
20802 | @end defmethod | |
20803 | ||
f3e9a817 PM |
20804 | @defmethod Frame block |
20805 | Return the frame's code block. @xref{Blocks In Python}. | |
20806 | @end defmethod | |
20807 | ||
20808 | @defmethod Frame function | |
20809 | Return the symbol for the function corresponding to this frame. | |
20810 | @xref{Symbols In Python}. | |
20811 | @end defmethod | |
20812 | ||
f8f6f20b TJB |
20813 | @defmethod Frame older |
20814 | Return the frame that called this frame. | |
20815 | @end defmethod | |
20816 | ||
20817 | @defmethod Frame newer | |
20818 | Return the frame called by this frame. | |
20819 | @end defmethod | |
20820 | ||
f3e9a817 PM |
20821 | @defmethod Frame find_sal |
20822 | Return the frame's symtab and line object. | |
20823 | @xref{Symbol Tables In Python}. | |
20824 | @end defmethod | |
20825 | ||
dc00d89f PM |
20826 | @defmethod Frame read_var variable @r{[}block@r{]} |
20827 | Return the value of @var{variable} in this frame. If the optional | |
20828 | argument @var{block} is provided, search for the variable from that | |
20829 | block; otherwise start at the frame's current block (which is | |
20830 | determined by the frame's current program counter). @var{variable} | |
20831 | must be a string or a @code{gdb.Symbol} object. @var{block} must be a | |
20832 | @code{gdb.Block} object. | |
f8f6f20b | 20833 | @end defmethod |
f3e9a817 PM |
20834 | |
20835 | @defmethod Frame select | |
20836 | Set this frame to be the selected frame. @xref{Stack, ,Examining the | |
20837 | Stack}. | |
20838 | @end defmethod | |
20839 | @end table | |
20840 | ||
20841 | @node Blocks In Python | |
20842 | @subsubsection Accessing frame blocks from Python. | |
20843 | ||
20844 | @cindex blocks in python | |
20845 | @tindex gdb.Block | |
20846 | ||
20847 | Within each frame, @value{GDBN} maintains information on each block | |
20848 | stored in that frame. These blocks are organized hierarchically, and | |
20849 | are represented individually in Python as a @code{gdb.Block}. | |
20850 | Please see @ref{Frames In Python}, for a more in-depth discussion on | |
20851 | frames. Furthermore, see @ref{Stack, ,Examining the Stack}, for more | |
20852 | detailed technical information on @value{GDBN}'s book-keeping of the | |
20853 | stack. | |
20854 | ||
20855 | The following block-related functions are available in the @code{gdb} | |
20856 | module: | |
20857 | ||
20858 | @findex gdb.block_for_pc | |
20859 | @defun block_for_pc pc | |
20860 | Return the @code{gdb.Block} containing the given @var{pc} value. If the | |
20861 | block cannot be found for the @var{pc} value specified, the function | |
20862 | will return @code{None}. | |
20863 | @end defun | |
20864 | ||
20865 | A @code{gdb.Block} object has the following attributes: | |
20866 | ||
20867 | @table @code | |
20868 | @defivar Block start | |
20869 | The start address of the block. This attribute is not writable. | |
20870 | @end defivar | |
20871 | ||
20872 | @defivar Block end | |
20873 | The end address of the block. This attribute is not writable. | |
20874 | @end defivar | |
20875 | ||
20876 | @defivar Block function | |
20877 | The name of the block represented as a @code{gdb.Symbol}. If the | |
20878 | block is not named, then this attribute holds @code{None}. This | |
20879 | attribute is not writable. | |
20880 | @end defivar | |
20881 | ||
20882 | @defivar Block superblock | |
20883 | The block containing this block. If this parent block does not exist, | |
20884 | this attribute holds @code{None}. This attribute is not writable. | |
20885 | @end defivar | |
20886 | @end table | |
20887 | ||
20888 | @node Symbols In Python | |
20889 | @subsubsection Python representation of Symbols. | |
20890 | ||
20891 | @cindex symbols in python | |
20892 | @tindex gdb.Symbol | |
20893 | ||
20894 | @value{GDBN} represents every variable, function and type as an | |
20895 | entry in a symbol table. @xref{Symbols, ,Examining the Symbol Table}. | |
20896 | Similarly, Python represents these symbols in @value{GDBN} with the | |
20897 | @code{gdb.Symbol} object. | |
20898 | ||
20899 | The following symbol-related functions are available in the @code{gdb} | |
20900 | module: | |
20901 | ||
20902 | @findex gdb.lookup_symbol | |
20903 | @defun lookup_symbol name [block] [domain] | |
20904 | This function searches for a symbol by name. The search scope can be | |
20905 | restricted to the parameters defined in the optional domain and block | |
20906 | arguments. | |
20907 | ||
20908 | @var{name} is the name of the symbol. It must be a string. The | |
20909 | optional @var{block} argument restricts the search to symbols visible | |
20910 | in that @var{block}. The @var{block} argument must be a | |
20911 | @code{gdb.Block} object. The optional @var{domain} argument restricts | |
20912 | the search to the domain type. The @var{domain} argument must be a | |
20913 | domain constant defined in the @code{gdb} module and described later | |
20914 | in this chapter. | |
20915 | @end defun | |
20916 | ||
20917 | A @code{gdb.Symbol} object has the following attributes: | |
20918 | ||
20919 | @table @code | |
20920 | @defivar Symbol symtab | |
20921 | The symbol table in which the symbol appears. This attribute is | |
20922 | represented as a @code{gdb.Symtab} object. @xref{Symbol Tables In | |
20923 | Python}. This attribute is not writable. | |
20924 | @end defivar | |
20925 | ||
20926 | @defivar Symbol name | |
20927 | The name of the symbol as a string. This attribute is not writable. | |
20928 | @end defivar | |
20929 | ||
20930 | @defivar Symbol linkage_name | |
20931 | The name of the symbol, as used by the linker (i.e., may be mangled). | |
20932 | This attribute is not writable. | |
20933 | @end defivar | |
20934 | ||
20935 | @defivar Symbol print_name | |
20936 | The name of the symbol in a form suitable for output. This is either | |
20937 | @code{name} or @code{linkage_name}, depending on whether the user | |
20938 | asked @value{GDBN} to display demangled or mangled names. | |
20939 | @end defivar | |
20940 | ||
20941 | @defivar Symbol addr_class | |
20942 | The address class of the symbol. This classifies how to find the value | |
20943 | of a symbol. Each address class is a constant defined in the | |
20944 | @code{gdb} module and described later in this chapter. | |
20945 | @end defivar | |
20946 | ||
20947 | @defivar Symbol is_argument | |
20948 | @code{True} if the symbol is an argument of a function. | |
20949 | @end defivar | |
20950 | ||
20951 | @defivar Symbol is_constant | |
20952 | @code{True} if the symbol is a constant. | |
20953 | @end defivar | |
20954 | ||
20955 | @defivar Symbol is_function | |
20956 | @code{True} if the symbol is a function or a method. | |
20957 | @end defivar | |
20958 | ||
20959 | @defivar Symbol is_variable | |
20960 | @code{True} if the symbol is a variable. | |
20961 | @end defivar | |
20962 | @end table | |
20963 | ||
20964 | The available domain categories in @code{gdb.Symbol} are represented | |
20965 | as constants in the @code{gdb} module: | |
20966 | ||
20967 | @table @code | |
20968 | @findex SYMBOL_UNDEF_DOMAIN | |
20969 | @findex gdb.SYMBOL_UNDEF_DOMAIN | |
20970 | @item SYMBOL_UNDEF_DOMAIN | |
20971 | This is used when a domain has not been discovered or none of the | |
20972 | following domains apply. This usually indicates an error either | |
20973 | in the symbol information or in @value{GDBN}'s handling of symbols. | |
20974 | @findex SYMBOL_VAR_DOMAIN | |
20975 | @findex gdb.SYMBOL_VAR_DOMAIN | |
20976 | @item SYMBOL_VAR_DOMAIN | |
20977 | This domain contains variables, function names, typedef names and enum | |
20978 | type values. | |
20979 | @findex SYMBOL_STRUCT_DOMAIN | |
20980 | @findex gdb.SYMBOL_STRUCT_DOMAIN | |
20981 | @item SYMBOL_STRUCT_DOMAIN | |
20982 | This domain holds struct, union and enum type names. | |
20983 | @findex SYMBOL_LABEL_DOMAIN | |
20984 | @findex gdb.SYMBOL_LABEL_DOMAIN | |
20985 | @item SYMBOL_LABEL_DOMAIN | |
20986 | This domain contains names of labels (for gotos). | |
20987 | @findex SYMBOL_VARIABLES_DOMAIN | |
20988 | @findex gdb.SYMBOL_VARIABLES_DOMAIN | |
20989 | @item SYMBOL_VARIABLES_DOMAIN | |
20990 | This domain holds a subset of the @code{SYMBOLS_VAR_DOMAIN}; it | |
20991 | contains everything minus functions and types. | |
20992 | @findex SYMBOL_FUNCTIONS_DOMAIN | |
20993 | @findex gdb.SYMBOL_FUNCTIONS_DOMAIN | |
20994 | @item SYMBOL_FUNCTION_DOMAIN | |
20995 | This domain contains all functions. | |
20996 | @findex SYMBOL_TYPES_DOMAIN | |
20997 | @findex gdb.SYMBOL_TYPES_DOMAIN | |
20998 | @item SYMBOL_TYPES_DOMAIN | |
20999 | This domain contains all types. | |
21000 | @end table | |
21001 | ||
21002 | The available address class categories in @code{gdb.Symbol} are represented | |
21003 | as constants in the @code{gdb} module: | |
21004 | ||
21005 | @table @code | |
21006 | @findex SYMBOL_LOC_UNDEF | |
21007 | @findex gdb.SYMBOL_LOC_UNDEF | |
21008 | @item SYMBOL_LOC_UNDEF | |
21009 | If this is returned by address class, it indicates an error either in | |
21010 | the symbol information or in @value{GDBN}'s handling of symbols. | |
21011 | @findex SYMBOL_LOC_CONST | |
21012 | @findex gdb.SYMBOL_LOC_CONST | |
21013 | @item SYMBOL_LOC_CONST | |
21014 | Value is constant int. | |
21015 | @findex SYMBOL_LOC_STATIC | |
21016 | @findex gdb.SYMBOL_LOC_STATIC | |
21017 | @item SYMBOL_LOC_STATIC | |
21018 | Value is at a fixed address. | |
21019 | @findex SYMBOL_LOC_REGISTER | |
21020 | @findex gdb.SYMBOL_LOC_REGISTER | |
21021 | @item SYMBOL_LOC_REGISTER | |
21022 | Value is in a register. | |
21023 | @findex SYMBOL_LOC_ARG | |
21024 | @findex gdb.SYMBOL_LOC_ARG | |
21025 | @item SYMBOL_LOC_ARG | |
21026 | Value is an argument. This value is at the offset stored within the | |
21027 | symbol inside the frame's argument list. | |
21028 | @findex SYMBOL_LOC_REF_ARG | |
21029 | @findex gdb.SYMBOL_LOC_REF_ARG | |
21030 | @item SYMBOL_LOC_REF_ARG | |
21031 | Value address is stored in the frame's argument list. Just like | |
21032 | @code{LOC_ARG} except that the value's address is stored at the | |
21033 | offset, not the value itself. | |
21034 | @findex SYMBOL_LOC_REGPARM_ADDR | |
21035 | @findex gdb.SYMBOL_LOC_REGPARM_ADDR | |
21036 | @item SYMBOL_LOC_REGPARM_ADDR | |
21037 | Value is a specified register. Just like @code{LOC_REGISTER} except | |
21038 | the register holds the address of the argument instead of the argument | |
21039 | itself. | |
21040 | @findex SYMBOL_LOC_LOCAL | |
21041 | @findex gdb.SYMBOL_LOC_LOCAL | |
21042 | @item SYMBOL_LOC_LOCAL | |
21043 | Value is a local variable. | |
21044 | @findex SYMBOL_LOC_TYPEDEF | |
21045 | @findex gdb.SYMBOL_LOC_TYPEDEF | |
21046 | @item SYMBOL_LOC_TYPEDEF | |
21047 | Value not used. Symbols in the domain @code{SYMBOL_STRUCT_DOMAIN} all | |
21048 | have this class. | |
21049 | @findex SYMBOL_LOC_BLOCK | |
21050 | @findex gdb.SYMBOL_LOC_BLOCK | |
21051 | @item SYMBOL_LOC_BLOCK | |
21052 | Value is a block. | |
21053 | @findex SYMBOL_LOC_CONST_BYTES | |
21054 | @findex gdb.SYMBOL_LOC_CONST_BYTES | |
21055 | @item SYMBOL_LOC_CONST_BYTES | |
21056 | Value is a byte-sequence. | |
21057 | @findex SYMBOL_LOC_UNRESOLVED | |
21058 | @findex gdb.SYMBOL_LOC_UNRESOLVED | |
21059 | @item SYMBOL_LOC_UNRESOLVED | |
21060 | Value is at a fixed address, but the address of the variable has to be | |
21061 | determined from the minimal symbol table whenever the variable is | |
21062 | referenced. | |
21063 | @findex SYMBOL_LOC_OPTIMIZED_OUT | |
21064 | @findex gdb.SYMBOL_LOC_OPTIMIZED_OUT | |
21065 | @item SYMBOL_LOC_OPTIMIZED_OUT | |
21066 | The value does not actually exist in the program. | |
21067 | @findex SYMBOL_LOC_COMPUTED | |
21068 | @findex gdb.SYMBOL_LOC_COMPUTED | |
21069 | @item SYMBOL_LOC_COMPUTED | |
21070 | The value's address is a computed location. | |
21071 | @end table | |
21072 | ||
21073 | @node Symbol Tables In Python | |
21074 | @subsubsection Symbol table representation in Python. | |
21075 | ||
21076 | @cindex symbol tables in python | |
21077 | @tindex gdb.Symtab | |
21078 | @tindex gdb.Symtab_and_line | |
21079 | ||
21080 | Access to symbol table data maintained by @value{GDBN} on the inferior | |
21081 | is exposed to Python via two objects: @code{gdb.Symtab_and_line} and | |
21082 | @code{gdb.Symtab}. Symbol table and line data for a frame is returned | |
21083 | from the @code{find_sal} method in @code{gdb.Frame} object. | |
21084 | @xref{Frames In Python}. | |
21085 | ||
21086 | For more information on @value{GDBN}'s symbol table management, see | |
21087 | @ref{Symbols, ,Examining the Symbol Table}, for more information. | |
21088 | ||
21089 | A @code{gdb.Symtab_and_line} object has the following attributes: | |
21090 | ||
21091 | @table @code | |
21092 | @defivar Symtab_and_line symtab | |
21093 | The symbol table object (@code{gdb.Symtab}) for this frame. | |
21094 | This attribute is not writable. | |
21095 | @end defivar | |
21096 | ||
21097 | @defivar Symtab_and_line pc | |
21098 | Indicates the current program counter address. This attribute is not | |
21099 | writable. | |
21100 | @end defivar | |
21101 | ||
21102 | @defivar Symtab_and_line line | |
21103 | Indicates the current line number for this object. This | |
21104 | attribute is not writable. | |
21105 | @end defivar | |
21106 | @end table | |
21107 | ||
21108 | A @code{gdb.Symtab} object has the following attributes: | |
21109 | ||
21110 | @table @code | |
21111 | @defivar Symtab filename | |
21112 | The symbol table's source filename. This attribute is not writable. | |
21113 | @end defivar | |
21114 | ||
21115 | @defivar Symtab objfile | |
21116 | The symbol table's backing object file. @xref{Objfiles In Python}. | |
21117 | This attribute is not writable. | |
21118 | @end defivar | |
21119 | @end table | |
21120 | ||
21121 | The following methods are provided: | |
21122 | ||
21123 | @table @code | |
21124 | @defmethod Symtab fullname | |
21125 | Return the symbol table's source absolute file name. | |
21126 | @end defmethod | |
f8f6f20b TJB |
21127 | @end table |
21128 | ||
be759fcf PM |
21129 | @node Lazy Strings In Python |
21130 | @subsubsection Python representation of lazy strings. | |
21131 | ||
21132 | @cindex lazy strings in python | |
21133 | @tindex gdb.LazyString | |
21134 | ||
21135 | A @dfn{lazy string} is a string whose contents is not retrieved or | |
21136 | encoded until it is needed. | |
21137 | ||
21138 | A @code{gdb.LazyString} is represented in @value{GDBN} as an | |
21139 | @code{address} that points to a region of memory, an @code{encoding} | |
21140 | that will be used to encode that region of memory, and a @code{length} | |
21141 | to delimit the region of memory that represents the string. The | |
21142 | difference between a @code{gdb.LazyString} and a string wrapped within | |
21143 | a @code{gdb.Value} is that a @code{gdb.LazyString} will be treated | |
21144 | differently by @value{GDBN} when printing. A @code{gdb.LazyString} is | |
21145 | retrieved and encoded during printing, while a @code{gdb.Value} | |
21146 | wrapping a string is immediately retrieved and encoded on creation. | |
21147 | ||
21148 | A @code{gdb.LazyString} object has the following functions: | |
21149 | ||
21150 | @defmethod LazyString value | |
21151 | Convert the @code{gdb.LazyString} to a @code{gdb.Value}. This value | |
21152 | will point to the string in memory, but will lose all the delayed | |
21153 | retrieval, encoding and handling that @value{GDBN} applies to a | |
21154 | @code{gdb.LazyString}. | |
21155 | @end defmethod | |
21156 | ||
21157 | @defivar LazyString address | |
21158 | This attribute holds the address of the string. This attribute is not | |
21159 | writable. | |
21160 | @end defivar | |
21161 | ||
21162 | @defivar LazyString length | |
21163 | This attribute holds the length of the string in characters. If the | |
21164 | length is -1, then the string will be fetched and encoded up to the | |
21165 | first null of appropriate width. This attribute is not writable. | |
21166 | @end defivar | |
21167 | ||
21168 | @defivar LazyString encoding | |
21169 | This attribute holds the encoding that will be applied to the string | |
21170 | when the string is printed by @value{GDBN}. If the encoding is not | |
21171 | set, or contains an empty string, then @value{GDBN} will select the | |
21172 | most appropriate encoding when the string is printed. This attribute | |
21173 | is not writable. | |
21174 | @end defivar | |
21175 | ||
21176 | @defivar LazyString type | |
21177 | This attribute holds the type that is represented by the lazy string's | |
21178 | type. For a lazy string this will always be a pointer type. To | |
21179 | resolve this to the lazy string's character type, use the type's | |
21180 | @code{target} method. @xref{Types In Python}. This attribute is not | |
21181 | writable. | |
21182 | @end defivar | |
21183 | ||
21c294e6 AC |
21184 | @node Interpreters |
21185 | @chapter Command Interpreters | |
21186 | @cindex command interpreters | |
21187 | ||
21188 | @value{GDBN} supports multiple command interpreters, and some command | |
21189 | infrastructure to allow users or user interface writers to switch | |
21190 | between interpreters or run commands in other interpreters. | |
21191 | ||
21192 | @value{GDBN} currently supports two command interpreters, the console | |
21193 | interpreter (sometimes called the command-line interpreter or @sc{cli}) | |
21194 | and the machine interface interpreter (or @sc{gdb/mi}). This manual | |
21195 | describes both of these interfaces in great detail. | |
21196 | ||
21197 | By default, @value{GDBN} will start with the console interpreter. | |
21198 | However, the user may choose to start @value{GDBN} with another | |
21199 | interpreter by specifying the @option{-i} or @option{--interpreter} | |
21200 | startup options. Defined interpreters include: | |
21201 | ||
21202 | @table @code | |
21203 | @item console | |
21204 | @cindex console interpreter | |
21205 | The traditional console or command-line interpreter. This is the most often | |
21206 | used interpreter with @value{GDBN}. With no interpreter specified at runtime, | |
21207 | @value{GDBN} will use this interpreter. | |
21208 | ||
21209 | @item mi | |
21210 | @cindex mi interpreter | |
21211 | The newest @sc{gdb/mi} interface (currently @code{mi2}). Used primarily | |
21212 | by programs wishing to use @value{GDBN} as a backend for a debugger GUI | |
21213 | or an IDE. For more information, see @ref{GDB/MI, ,The @sc{gdb/mi} | |
21214 | Interface}. | |
21215 | ||
21216 | @item mi2 | |
21217 | @cindex mi2 interpreter | |
21218 | The current @sc{gdb/mi} interface. | |
21219 | ||
21220 | @item mi1 | |
21221 | @cindex mi1 interpreter | |
21222 | The @sc{gdb/mi} interface included in @value{GDBN} 5.1, 5.2, and 5.3. | |
21223 | ||
21224 | @end table | |
21225 | ||
21226 | @cindex invoke another interpreter | |
21227 | The interpreter being used by @value{GDBN} may not be dynamically | |
21228 | switched at runtime. Although possible, this could lead to a very | |
21229 | precarious situation. Consider an IDE using @sc{gdb/mi}. If a user | |
21230 | enters the command "interpreter-set console" in a console view, | |
21231 | @value{GDBN} would switch to using the console interpreter, rendering | |
21232 | the IDE inoperable! | |
21233 | ||
21234 | @kindex interpreter-exec | |
21235 | Although you may only choose a single interpreter at startup, you may execute | |
21236 | commands in any interpreter from the current interpreter using the appropriate | |
21237 | command. If you are running the console interpreter, simply use the | |
21238 | @code{interpreter-exec} command: | |
21239 | ||
21240 | @smallexample | |
21241 | interpreter-exec mi "-data-list-register-names" | |
21242 | @end smallexample | |
21243 | ||
21244 | @sc{gdb/mi} has a similar command, although it is only available in versions of | |
21245 | @value{GDBN} which support @sc{gdb/mi} version 2 (or greater). | |
21246 | ||
8e04817f AC |
21247 | @node TUI |
21248 | @chapter @value{GDBN} Text User Interface | |
21249 | @cindex TUI | |
d0d5df6f | 21250 | @cindex Text User Interface |
c906108c | 21251 | |
8e04817f AC |
21252 | @menu |
21253 | * TUI Overview:: TUI overview | |
21254 | * TUI Keys:: TUI key bindings | |
7cf36c78 | 21255 | * TUI Single Key Mode:: TUI single key mode |
db2e3e2e | 21256 | * TUI Commands:: TUI-specific commands |
8e04817f AC |
21257 | * TUI Configuration:: TUI configuration variables |
21258 | @end menu | |
c906108c | 21259 | |
46ba6afa | 21260 | The @value{GDBN} Text User Interface (TUI) is a terminal |
d0d5df6f AC |
21261 | interface which uses the @code{curses} library to show the source |
21262 | file, the assembly output, the program registers and @value{GDBN} | |
46ba6afa BW |
21263 | commands in separate text windows. The TUI mode is supported only |
21264 | on platforms where a suitable version of the @code{curses} library | |
21265 | is available. | |
d0d5df6f | 21266 | |
46ba6afa BW |
21267 | @pindex @value{GDBTUI} |
21268 | The TUI mode is enabled by default when you invoke @value{GDBN} as | |
21269 | either @samp{@value{GDBTUI}} or @samp{@value{GDBP} -tui}. | |
21270 | You can also switch in and out of TUI mode while @value{GDBN} runs by | |
21271 | using various TUI commands and key bindings, such as @kbd{C-x C-a}. | |
21272 | @xref{TUI Keys, ,TUI Key Bindings}. | |
c906108c | 21273 | |
8e04817f | 21274 | @node TUI Overview |
79a6e687 | 21275 | @section TUI Overview |
c906108c | 21276 | |
46ba6afa | 21277 | In TUI mode, @value{GDBN} can display several text windows: |
c906108c | 21278 | |
8e04817f AC |
21279 | @table @emph |
21280 | @item command | |
21281 | This window is the @value{GDBN} command window with the @value{GDBN} | |
46ba6afa BW |
21282 | prompt and the @value{GDBN} output. The @value{GDBN} input is still |
21283 | managed using readline. | |
c906108c | 21284 | |
8e04817f AC |
21285 | @item source |
21286 | The source window shows the source file of the program. The current | |
46ba6afa | 21287 | line and active breakpoints are displayed in this window. |
c906108c | 21288 | |
8e04817f AC |
21289 | @item assembly |
21290 | The assembly window shows the disassembly output of the program. | |
c906108c | 21291 | |
8e04817f | 21292 | @item register |
46ba6afa BW |
21293 | This window shows the processor registers. Registers are highlighted |
21294 | when their values change. | |
c906108c SS |
21295 | @end table |
21296 | ||
269c21fe | 21297 | The source and assembly windows show the current program position |
46ba6afa BW |
21298 | by highlighting the current line and marking it with a @samp{>} marker. |
21299 | Breakpoints are indicated with two markers. The first marker | |
269c21fe SC |
21300 | indicates the breakpoint type: |
21301 | ||
21302 | @table @code | |
21303 | @item B | |
21304 | Breakpoint which was hit at least once. | |
21305 | ||
21306 | @item b | |
21307 | Breakpoint which was never hit. | |
21308 | ||
21309 | @item H | |
21310 | Hardware breakpoint which was hit at least once. | |
21311 | ||
21312 | @item h | |
21313 | Hardware breakpoint which was never hit. | |
269c21fe SC |
21314 | @end table |
21315 | ||
21316 | The second marker indicates whether the breakpoint is enabled or not: | |
21317 | ||
21318 | @table @code | |
21319 | @item + | |
21320 | Breakpoint is enabled. | |
21321 | ||
21322 | @item - | |
21323 | Breakpoint is disabled. | |
269c21fe SC |
21324 | @end table |
21325 | ||
46ba6afa BW |
21326 | The source, assembly and register windows are updated when the current |
21327 | thread changes, when the frame changes, or when the program counter | |
21328 | changes. | |
21329 | ||
21330 | These windows are not all visible at the same time. The command | |
21331 | window is always visible. The others can be arranged in several | |
21332 | layouts: | |
c906108c | 21333 | |
8e04817f AC |
21334 | @itemize @bullet |
21335 | @item | |
46ba6afa | 21336 | source only, |
2df3850c | 21337 | |
8e04817f | 21338 | @item |
46ba6afa | 21339 | assembly only, |
8e04817f AC |
21340 | |
21341 | @item | |
46ba6afa | 21342 | source and assembly, |
8e04817f AC |
21343 | |
21344 | @item | |
46ba6afa | 21345 | source and registers, or |
c906108c | 21346 | |
8e04817f | 21347 | @item |
46ba6afa | 21348 | assembly and registers. |
8e04817f | 21349 | @end itemize |
c906108c | 21350 | |
46ba6afa | 21351 | A status line above the command window shows the following information: |
b7bb15bc SC |
21352 | |
21353 | @table @emph | |
21354 | @item target | |
46ba6afa | 21355 | Indicates the current @value{GDBN} target. |
b7bb15bc SC |
21356 | (@pxref{Targets, ,Specifying a Debugging Target}). |
21357 | ||
21358 | @item process | |
46ba6afa | 21359 | Gives the current process or thread number. |
b7bb15bc SC |
21360 | When no process is being debugged, this field is set to @code{No process}. |
21361 | ||
21362 | @item function | |
21363 | Gives the current function name for the selected frame. | |
21364 | The name is demangled if demangling is turned on (@pxref{Print Settings}). | |
46ba6afa | 21365 | When there is no symbol corresponding to the current program counter, |
b7bb15bc SC |
21366 | the string @code{??} is displayed. |
21367 | ||
21368 | @item line | |
21369 | Indicates the current line number for the selected frame. | |
46ba6afa | 21370 | When the current line number is not known, the string @code{??} is displayed. |
b7bb15bc SC |
21371 | |
21372 | @item pc | |
21373 | Indicates the current program counter address. | |
b7bb15bc SC |
21374 | @end table |
21375 | ||
8e04817f AC |
21376 | @node TUI Keys |
21377 | @section TUI Key Bindings | |
21378 | @cindex TUI key bindings | |
c906108c | 21379 | |
8e04817f | 21380 | The TUI installs several key bindings in the readline keymaps |
46ba6afa | 21381 | (@pxref{Command Line Editing}). The following key bindings |
8e04817f | 21382 | are installed for both TUI mode and the @value{GDBN} standard mode. |
c906108c | 21383 | |
8e04817f AC |
21384 | @table @kbd |
21385 | @kindex C-x C-a | |
21386 | @item C-x C-a | |
21387 | @kindex C-x a | |
21388 | @itemx C-x a | |
21389 | @kindex C-x A | |
21390 | @itemx C-x A | |
46ba6afa BW |
21391 | Enter or leave the TUI mode. When leaving the TUI mode, |
21392 | the curses window management stops and @value{GDBN} operates using | |
21393 | its standard mode, writing on the terminal directly. When reentering | |
21394 | the TUI mode, control is given back to the curses windows. | |
8e04817f | 21395 | The screen is then refreshed. |
c906108c | 21396 | |
8e04817f AC |
21397 | @kindex C-x 1 |
21398 | @item C-x 1 | |
21399 | Use a TUI layout with only one window. The layout will | |
21400 | either be @samp{source} or @samp{assembly}. When the TUI mode | |
21401 | is not active, it will switch to the TUI mode. | |
2df3850c | 21402 | |
8e04817f | 21403 | Think of this key binding as the Emacs @kbd{C-x 1} binding. |
c906108c | 21404 | |
8e04817f AC |
21405 | @kindex C-x 2 |
21406 | @item C-x 2 | |
21407 | Use a TUI layout with at least two windows. When the current | |
46ba6afa | 21408 | layout already has two windows, the next layout with two windows is used. |
8e04817f AC |
21409 | When a new layout is chosen, one window will always be common to the |
21410 | previous layout and the new one. | |
c906108c | 21411 | |
8e04817f | 21412 | Think of it as the Emacs @kbd{C-x 2} binding. |
2df3850c | 21413 | |
72ffddc9 SC |
21414 | @kindex C-x o |
21415 | @item C-x o | |
21416 | Change the active window. The TUI associates several key bindings | |
46ba6afa | 21417 | (like scrolling and arrow keys) with the active window. This command |
72ffddc9 SC |
21418 | gives the focus to the next TUI window. |
21419 | ||
21420 | Think of it as the Emacs @kbd{C-x o} binding. | |
21421 | ||
7cf36c78 SC |
21422 | @kindex C-x s |
21423 | @item C-x s | |
46ba6afa BW |
21424 | Switch in and out of the TUI SingleKey mode that binds single |
21425 | keys to @value{GDBN} commands (@pxref{TUI Single Key Mode}). | |
c906108c SS |
21426 | @end table |
21427 | ||
46ba6afa | 21428 | The following key bindings only work in the TUI mode: |
5d161b24 | 21429 | |
46ba6afa | 21430 | @table @asis |
8e04817f | 21431 | @kindex PgUp |
46ba6afa | 21432 | @item @key{PgUp} |
8e04817f | 21433 | Scroll the active window one page up. |
c906108c | 21434 | |
8e04817f | 21435 | @kindex PgDn |
46ba6afa | 21436 | @item @key{PgDn} |
8e04817f | 21437 | Scroll the active window one page down. |
c906108c | 21438 | |
8e04817f | 21439 | @kindex Up |
46ba6afa | 21440 | @item @key{Up} |
8e04817f | 21441 | Scroll the active window one line up. |
c906108c | 21442 | |
8e04817f | 21443 | @kindex Down |
46ba6afa | 21444 | @item @key{Down} |
8e04817f | 21445 | Scroll the active window one line down. |
c906108c | 21446 | |
8e04817f | 21447 | @kindex Left |
46ba6afa | 21448 | @item @key{Left} |
8e04817f | 21449 | Scroll the active window one column left. |
c906108c | 21450 | |
8e04817f | 21451 | @kindex Right |
46ba6afa | 21452 | @item @key{Right} |
8e04817f | 21453 | Scroll the active window one column right. |
c906108c | 21454 | |
8e04817f | 21455 | @kindex C-L |
46ba6afa | 21456 | @item @kbd{C-L} |
8e04817f | 21457 | Refresh the screen. |
8e04817f | 21458 | @end table |
c906108c | 21459 | |
46ba6afa BW |
21460 | Because the arrow keys scroll the active window in the TUI mode, they |
21461 | are not available for their normal use by readline unless the command | |
21462 | window has the focus. When another window is active, you must use | |
21463 | other readline key bindings such as @kbd{C-p}, @kbd{C-n}, @kbd{C-b} | |
21464 | and @kbd{C-f} to control the command window. | |
8e04817f | 21465 | |
7cf36c78 SC |
21466 | @node TUI Single Key Mode |
21467 | @section TUI Single Key Mode | |
21468 | @cindex TUI single key mode | |
21469 | ||
46ba6afa BW |
21470 | The TUI also provides a @dfn{SingleKey} mode, which binds several |
21471 | frequently used @value{GDBN} commands to single keys. Type @kbd{C-x s} to | |
21472 | switch into this mode, where the following key bindings are used: | |
7cf36c78 SC |
21473 | |
21474 | @table @kbd | |
21475 | @kindex c @r{(SingleKey TUI key)} | |
21476 | @item c | |
21477 | continue | |
21478 | ||
21479 | @kindex d @r{(SingleKey TUI key)} | |
21480 | @item d | |
21481 | down | |
21482 | ||
21483 | @kindex f @r{(SingleKey TUI key)} | |
21484 | @item f | |
21485 | finish | |
21486 | ||
21487 | @kindex n @r{(SingleKey TUI key)} | |
21488 | @item n | |
21489 | next | |
21490 | ||
21491 | @kindex q @r{(SingleKey TUI key)} | |
21492 | @item q | |
46ba6afa | 21493 | exit the SingleKey mode. |
7cf36c78 SC |
21494 | |
21495 | @kindex r @r{(SingleKey TUI key)} | |
21496 | @item r | |
21497 | run | |
21498 | ||
21499 | @kindex s @r{(SingleKey TUI key)} | |
21500 | @item s | |
21501 | step | |
21502 | ||
21503 | @kindex u @r{(SingleKey TUI key)} | |
21504 | @item u | |
21505 | up | |
21506 | ||
21507 | @kindex v @r{(SingleKey TUI key)} | |
21508 | @item v | |
21509 | info locals | |
21510 | ||
21511 | @kindex w @r{(SingleKey TUI key)} | |
21512 | @item w | |
21513 | where | |
7cf36c78 SC |
21514 | @end table |
21515 | ||
21516 | Other keys temporarily switch to the @value{GDBN} command prompt. | |
21517 | The key that was pressed is inserted in the editing buffer so that | |
21518 | it is possible to type most @value{GDBN} commands without interaction | |
46ba6afa BW |
21519 | with the TUI SingleKey mode. Once the command is entered the TUI |
21520 | SingleKey mode is restored. The only way to permanently leave | |
7f9087cb | 21521 | this mode is by typing @kbd{q} or @kbd{C-x s}. |
7cf36c78 SC |
21522 | |
21523 | ||
8e04817f | 21524 | @node TUI Commands |
db2e3e2e | 21525 | @section TUI-specific Commands |
8e04817f AC |
21526 | @cindex TUI commands |
21527 | ||
21528 | The TUI has specific commands to control the text windows. | |
46ba6afa BW |
21529 | These commands are always available, even when @value{GDBN} is not in |
21530 | the TUI mode. When @value{GDBN} is in the standard mode, most | |
21531 | of these commands will automatically switch to the TUI mode. | |
c906108c SS |
21532 | |
21533 | @table @code | |
3d757584 SC |
21534 | @item info win |
21535 | @kindex info win | |
21536 | List and give the size of all displayed windows. | |
21537 | ||
8e04817f | 21538 | @item layout next |
4644b6e3 | 21539 | @kindex layout |
8e04817f | 21540 | Display the next layout. |
2df3850c | 21541 | |
8e04817f | 21542 | @item layout prev |
8e04817f | 21543 | Display the previous layout. |
c906108c | 21544 | |
8e04817f | 21545 | @item layout src |
8e04817f | 21546 | Display the source window only. |
c906108c | 21547 | |
8e04817f | 21548 | @item layout asm |
8e04817f | 21549 | Display the assembly window only. |
c906108c | 21550 | |
8e04817f | 21551 | @item layout split |
8e04817f | 21552 | Display the source and assembly window. |
c906108c | 21553 | |
8e04817f | 21554 | @item layout regs |
8e04817f AC |
21555 | Display the register window together with the source or assembly window. |
21556 | ||
46ba6afa | 21557 | @item focus next |
8e04817f | 21558 | @kindex focus |
46ba6afa BW |
21559 | Make the next window active for scrolling. |
21560 | ||
21561 | @item focus prev | |
21562 | Make the previous window active for scrolling. | |
21563 | ||
21564 | @item focus src | |
21565 | Make the source window active for scrolling. | |
21566 | ||
21567 | @item focus asm | |
21568 | Make the assembly window active for scrolling. | |
21569 | ||
21570 | @item focus regs | |
21571 | Make the register window active for scrolling. | |
21572 | ||
21573 | @item focus cmd | |
21574 | Make the command window active for scrolling. | |
c906108c | 21575 | |
8e04817f AC |
21576 | @item refresh |
21577 | @kindex refresh | |
7f9087cb | 21578 | Refresh the screen. This is similar to typing @kbd{C-L}. |
c906108c | 21579 | |
6a1b180d SC |
21580 | @item tui reg float |
21581 | @kindex tui reg | |
21582 | Show the floating point registers in the register window. | |
21583 | ||
21584 | @item tui reg general | |
21585 | Show the general registers in the register window. | |
21586 | ||
21587 | @item tui reg next | |
21588 | Show the next register group. The list of register groups as well as | |
21589 | their order is target specific. The predefined register groups are the | |
21590 | following: @code{general}, @code{float}, @code{system}, @code{vector}, | |
21591 | @code{all}, @code{save}, @code{restore}. | |
21592 | ||
21593 | @item tui reg system | |
21594 | Show the system registers in the register window. | |
21595 | ||
8e04817f AC |
21596 | @item update |
21597 | @kindex update | |
21598 | Update the source window and the current execution point. | |
c906108c | 21599 | |
8e04817f AC |
21600 | @item winheight @var{name} +@var{count} |
21601 | @itemx winheight @var{name} -@var{count} | |
21602 | @kindex winheight | |
21603 | Change the height of the window @var{name} by @var{count} | |
21604 | lines. Positive counts increase the height, while negative counts | |
21605 | decrease it. | |
2df3850c | 21606 | |
46ba6afa BW |
21607 | @item tabset @var{nchars} |
21608 | @kindex tabset | |
c45da7e6 | 21609 | Set the width of tab stops to be @var{nchars} characters. |
c906108c SS |
21610 | @end table |
21611 | ||
8e04817f | 21612 | @node TUI Configuration |
79a6e687 | 21613 | @section TUI Configuration Variables |
8e04817f | 21614 | @cindex TUI configuration variables |
c906108c | 21615 | |
46ba6afa | 21616 | Several configuration variables control the appearance of TUI windows. |
c906108c | 21617 | |
8e04817f AC |
21618 | @table @code |
21619 | @item set tui border-kind @var{kind} | |
21620 | @kindex set tui border-kind | |
21621 | Select the border appearance for the source, assembly and register windows. | |
21622 | The possible values are the following: | |
21623 | @table @code | |
21624 | @item space | |
21625 | Use a space character to draw the border. | |
c906108c | 21626 | |
8e04817f | 21627 | @item ascii |
46ba6afa | 21628 | Use @sc{ascii} characters @samp{+}, @samp{-} and @samp{|} to draw the border. |
c906108c | 21629 | |
8e04817f AC |
21630 | @item acs |
21631 | Use the Alternate Character Set to draw the border. The border is | |
21632 | drawn using character line graphics if the terminal supports them. | |
8e04817f | 21633 | @end table |
c78b4128 | 21634 | |
8e04817f AC |
21635 | @item set tui border-mode @var{mode} |
21636 | @kindex set tui border-mode | |
46ba6afa BW |
21637 | @itemx set tui active-border-mode @var{mode} |
21638 | @kindex set tui active-border-mode | |
21639 | Select the display attributes for the borders of the inactive windows | |
21640 | or the active window. The @var{mode} can be one of the following: | |
8e04817f AC |
21641 | @table @code |
21642 | @item normal | |
21643 | Use normal attributes to display the border. | |
c906108c | 21644 | |
8e04817f AC |
21645 | @item standout |
21646 | Use standout mode. | |
c906108c | 21647 | |
8e04817f AC |
21648 | @item reverse |
21649 | Use reverse video mode. | |
c906108c | 21650 | |
8e04817f AC |
21651 | @item half |
21652 | Use half bright mode. | |
c906108c | 21653 | |
8e04817f AC |
21654 | @item half-standout |
21655 | Use half bright and standout mode. | |
c906108c | 21656 | |
8e04817f AC |
21657 | @item bold |
21658 | Use extra bright or bold mode. | |
c78b4128 | 21659 | |
8e04817f AC |
21660 | @item bold-standout |
21661 | Use extra bright or bold and standout mode. | |
8e04817f | 21662 | @end table |
8e04817f | 21663 | @end table |
c78b4128 | 21664 | |
8e04817f AC |
21665 | @node Emacs |
21666 | @chapter Using @value{GDBN} under @sc{gnu} Emacs | |
c78b4128 | 21667 | |
8e04817f AC |
21668 | @cindex Emacs |
21669 | @cindex @sc{gnu} Emacs | |
21670 | A special interface allows you to use @sc{gnu} Emacs to view (and | |
21671 | edit) the source files for the program you are debugging with | |
21672 | @value{GDBN}. | |
c906108c | 21673 | |
8e04817f AC |
21674 | To use this interface, use the command @kbd{M-x gdb} in Emacs. Give the |
21675 | executable file you want to debug as an argument. This command starts | |
21676 | @value{GDBN} as a subprocess of Emacs, with input and output through a newly | |
21677 | created Emacs buffer. | |
21678 | @c (Do not use the @code{-tui} option to run @value{GDBN} from Emacs.) | |
c906108c | 21679 | |
5e252a2e | 21680 | Running @value{GDBN} under Emacs can be just like running @value{GDBN} normally except for two |
8e04817f | 21681 | things: |
c906108c | 21682 | |
8e04817f AC |
21683 | @itemize @bullet |
21684 | @item | |
5e252a2e NR |
21685 | All ``terminal'' input and output goes through an Emacs buffer, called |
21686 | the GUD buffer. | |
c906108c | 21687 | |
8e04817f AC |
21688 | This applies both to @value{GDBN} commands and their output, and to the input |
21689 | and output done by the program you are debugging. | |
bf0184be | 21690 | |
8e04817f AC |
21691 | This is useful because it means that you can copy the text of previous |
21692 | commands and input them again; you can even use parts of the output | |
21693 | in this way. | |
bf0184be | 21694 | |
8e04817f AC |
21695 | All the facilities of Emacs' Shell mode are available for interacting |
21696 | with your program. In particular, you can send signals the usual | |
21697 | way---for example, @kbd{C-c C-c} for an interrupt, @kbd{C-c C-z} for a | |
21698 | stop. | |
bf0184be ND |
21699 | |
21700 | @item | |
8e04817f | 21701 | @value{GDBN} displays source code through Emacs. |
bf0184be | 21702 | |
8e04817f AC |
21703 | Each time @value{GDBN} displays a stack frame, Emacs automatically finds the |
21704 | source file for that frame and puts an arrow (@samp{=>}) at the | |
21705 | left margin of the current line. Emacs uses a separate buffer for | |
21706 | source display, and splits the screen to show both your @value{GDBN} session | |
21707 | and the source. | |
bf0184be | 21708 | |
8e04817f AC |
21709 | Explicit @value{GDBN} @code{list} or search commands still produce output as |
21710 | usual, but you probably have no reason to use them from Emacs. | |
5e252a2e NR |
21711 | @end itemize |
21712 | ||
21713 | We call this @dfn{text command mode}. Emacs 22.1, and later, also uses | |
21714 | a graphical mode, enabled by default, which provides further buffers | |
21715 | that can control the execution and describe the state of your program. | |
21716 | @xref{GDB Graphical Interface,,, Emacs, The @sc{gnu} Emacs Manual}. | |
c906108c | 21717 | |
64fabec2 AC |
21718 | If you specify an absolute file name when prompted for the @kbd{M-x |
21719 | gdb} argument, then Emacs sets your current working directory to where | |
21720 | your program resides. If you only specify the file name, then Emacs | |
21721 | sets your current working directory to to the directory associated | |
21722 | with the previous buffer. In this case, @value{GDBN} may find your | |
21723 | program by searching your environment's @code{PATH} variable, but on | |
21724 | some operating systems it might not find the source. So, although the | |
21725 | @value{GDBN} input and output session proceeds normally, the auxiliary | |
21726 | buffer does not display the current source and line of execution. | |
21727 | ||
21728 | The initial working directory of @value{GDBN} is printed on the top | |
5e252a2e NR |
21729 | line of the GUD buffer and this serves as a default for the commands |
21730 | that specify files for @value{GDBN} to operate on. @xref{Files, | |
21731 | ,Commands to Specify Files}. | |
64fabec2 AC |
21732 | |
21733 | By default, @kbd{M-x gdb} calls the program called @file{gdb}. If you | |
21734 | need to call @value{GDBN} by a different name (for example, if you | |
21735 | keep several configurations around, with different names) you can | |
21736 | customize the Emacs variable @code{gud-gdb-command-name} to run the | |
21737 | one you want. | |
8e04817f | 21738 | |
5e252a2e | 21739 | In the GUD buffer, you can use these special Emacs commands in |
8e04817f | 21740 | addition to the standard Shell mode commands: |
c906108c | 21741 | |
8e04817f AC |
21742 | @table @kbd |
21743 | @item C-h m | |
5e252a2e | 21744 | Describe the features of Emacs' GUD Mode. |
c906108c | 21745 | |
64fabec2 | 21746 | @item C-c C-s |
8e04817f AC |
21747 | Execute to another source line, like the @value{GDBN} @code{step} command; also |
21748 | update the display window to show the current file and location. | |
c906108c | 21749 | |
64fabec2 | 21750 | @item C-c C-n |
8e04817f AC |
21751 | Execute to next source line in this function, skipping all function |
21752 | calls, like the @value{GDBN} @code{next} command. Then update the display window | |
21753 | to show the current file and location. | |
c906108c | 21754 | |
64fabec2 | 21755 | @item C-c C-i |
8e04817f AC |
21756 | Execute one instruction, like the @value{GDBN} @code{stepi} command; update |
21757 | display window accordingly. | |
c906108c | 21758 | |
8e04817f AC |
21759 | @item C-c C-f |
21760 | Execute until exit from the selected stack frame, like the @value{GDBN} | |
21761 | @code{finish} command. | |
c906108c | 21762 | |
64fabec2 | 21763 | @item C-c C-r |
8e04817f AC |
21764 | Continue execution of your program, like the @value{GDBN} @code{continue} |
21765 | command. | |
b433d00b | 21766 | |
64fabec2 | 21767 | @item C-c < |
8e04817f AC |
21768 | Go up the number of frames indicated by the numeric argument |
21769 | (@pxref{Arguments, , Numeric Arguments, Emacs, The @sc{gnu} Emacs Manual}), | |
21770 | like the @value{GDBN} @code{up} command. | |
b433d00b | 21771 | |
64fabec2 | 21772 | @item C-c > |
8e04817f AC |
21773 | Go down the number of frames indicated by the numeric argument, like the |
21774 | @value{GDBN} @code{down} command. | |
8e04817f | 21775 | @end table |
c906108c | 21776 | |
7f9087cb | 21777 | In any source file, the Emacs command @kbd{C-x @key{SPC}} (@code{gud-break}) |
8e04817f | 21778 | tells @value{GDBN} to set a breakpoint on the source line point is on. |
c906108c | 21779 | |
5e252a2e NR |
21780 | In text command mode, if you type @kbd{M-x speedbar}, Emacs displays a |
21781 | separate frame which shows a backtrace when the GUD buffer is current. | |
21782 | Move point to any frame in the stack and type @key{RET} to make it | |
21783 | become the current frame and display the associated source in the | |
21784 | source buffer. Alternatively, click @kbd{Mouse-2} to make the | |
21785 | selected frame become the current one. In graphical mode, the | |
21786 | speedbar displays watch expressions. | |
64fabec2 | 21787 | |
8e04817f AC |
21788 | If you accidentally delete the source-display buffer, an easy way to get |
21789 | it back is to type the command @code{f} in the @value{GDBN} buffer, to | |
21790 | request a frame display; when you run under Emacs, this recreates | |
21791 | the source buffer if necessary to show you the context of the current | |
21792 | frame. | |
c906108c | 21793 | |
8e04817f AC |
21794 | The source files displayed in Emacs are in ordinary Emacs buffers |
21795 | which are visiting the source files in the usual way. You can edit | |
21796 | the files with these buffers if you wish; but keep in mind that @value{GDBN} | |
21797 | communicates with Emacs in terms of line numbers. If you add or | |
21798 | delete lines from the text, the line numbers that @value{GDBN} knows cease | |
21799 | to correspond properly with the code. | |
b383017d | 21800 | |
5e252a2e NR |
21801 | A more detailed description of Emacs' interaction with @value{GDBN} is |
21802 | given in the Emacs manual (@pxref{Debuggers,,, Emacs, The @sc{gnu} | |
21803 | Emacs Manual}). | |
c906108c | 21804 | |
8e04817f AC |
21805 | @c The following dropped because Epoch is nonstandard. Reactivate |
21806 | @c if/when v19 does something similar. ---doc@cygnus.com 19dec1990 | |
21807 | @ignore | |
21808 | @kindex Emacs Epoch environment | |
21809 | @kindex Epoch | |
21810 | @kindex inspect | |
c906108c | 21811 | |
8e04817f AC |
21812 | Version 18 of @sc{gnu} Emacs has a built-in window system |
21813 | called the @code{epoch} | |
21814 | environment. Users of this environment can use a new command, | |
21815 | @code{inspect} which performs identically to @code{print} except that | |
21816 | each value is printed in its own window. | |
21817 | @end ignore | |
c906108c | 21818 | |
922fbb7b AC |
21819 | |
21820 | @node GDB/MI | |
21821 | @chapter The @sc{gdb/mi} Interface | |
21822 | ||
21823 | @unnumberedsec Function and Purpose | |
21824 | ||
21825 | @cindex @sc{gdb/mi}, its purpose | |
6b5e8c01 NR |
21826 | @sc{gdb/mi} is a line based machine oriented text interface to |
21827 | @value{GDBN} and is activated by specifying using the | |
21828 | @option{--interpreter} command line option (@pxref{Mode Options}). It | |
21829 | is specifically intended to support the development of systems which | |
21830 | use the debugger as just one small component of a larger system. | |
922fbb7b AC |
21831 | |
21832 | This chapter is a specification of the @sc{gdb/mi} interface. It is written | |
21833 | in the form of a reference manual. | |
21834 | ||
21835 | Note that @sc{gdb/mi} is still under construction, so some of the | |
af6eff6f NR |
21836 | features described below are incomplete and subject to change |
21837 | (@pxref{GDB/MI Development and Front Ends, , @sc{gdb/mi} Development and Front Ends}). | |
922fbb7b AC |
21838 | |
21839 | @unnumberedsec Notation and Terminology | |
21840 | ||
21841 | @cindex notational conventions, for @sc{gdb/mi} | |
21842 | This chapter uses the following notation: | |
21843 | ||
21844 | @itemize @bullet | |
21845 | @item | |
21846 | @code{|} separates two alternatives. | |
21847 | ||
21848 | @item | |
21849 | @code{[ @var{something} ]} indicates that @var{something} is optional: | |
21850 | it may or may not be given. | |
21851 | ||
21852 | @item | |
21853 | @code{( @var{group} )*} means that @var{group} inside the parentheses | |
21854 | may repeat zero or more times. | |
21855 | ||
21856 | @item | |
21857 | @code{( @var{group} )+} means that @var{group} inside the parentheses | |
21858 | may repeat one or more times. | |
21859 | ||
21860 | @item | |
21861 | @code{"@var{string}"} means a literal @var{string}. | |
21862 | @end itemize | |
21863 | ||
21864 | @ignore | |
21865 | @heading Dependencies | |
21866 | @end ignore | |
21867 | ||
922fbb7b | 21868 | @menu |
c3b108f7 | 21869 | * GDB/MI General Design:: |
922fbb7b AC |
21870 | * GDB/MI Command Syntax:: |
21871 | * GDB/MI Compatibility with CLI:: | |
af6eff6f | 21872 | * GDB/MI Development and Front Ends:: |
922fbb7b | 21873 | * GDB/MI Output Records:: |
ef21caaf | 21874 | * GDB/MI Simple Examples:: |
922fbb7b | 21875 | * GDB/MI Command Description Format:: |
ef21caaf | 21876 | * GDB/MI Breakpoint Commands:: |
a2c02241 NR |
21877 | * GDB/MI Program Context:: |
21878 | * GDB/MI Thread Commands:: | |
21879 | * GDB/MI Program Execution:: | |
21880 | * GDB/MI Stack Manipulation:: | |
21881 | * GDB/MI Variable Objects:: | |
922fbb7b | 21882 | * GDB/MI Data Manipulation:: |
a2c02241 NR |
21883 | * GDB/MI Tracepoint Commands:: |
21884 | * GDB/MI Symbol Query:: | |
351ff01a | 21885 | * GDB/MI File Commands:: |
922fbb7b AC |
21886 | @ignore |
21887 | * GDB/MI Kod Commands:: | |
21888 | * GDB/MI Memory Overlay Commands:: | |
21889 | * GDB/MI Signal Handling Commands:: | |
21890 | @end ignore | |
922fbb7b | 21891 | * GDB/MI Target Manipulation:: |
a6b151f1 | 21892 | * GDB/MI File Transfer Commands:: |
ef21caaf | 21893 | * GDB/MI Miscellaneous Commands:: |
922fbb7b AC |
21894 | @end menu |
21895 | ||
c3b108f7 VP |
21896 | @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% |
21897 | @node GDB/MI General Design | |
21898 | @section @sc{gdb/mi} General Design | |
21899 | @cindex GDB/MI General Design | |
21900 | ||
21901 | Interaction of a @sc{GDB/MI} frontend with @value{GDBN} involves three | |
21902 | parts---commands sent to @value{GDBN}, responses to those commands | |
21903 | and notifications. Each command results in exactly one response, | |
21904 | indicating either successful completion of the command, or an error. | |
21905 | For the commands that do not resume the target, the response contains the | |
21906 | requested information. For the commands that resume the target, the | |
21907 | response only indicates whether the target was successfully resumed. | |
21908 | Notifications is the mechanism for reporting changes in the state of the | |
21909 | target, or in @value{GDBN} state, that cannot conveniently be associated with | |
21910 | a command and reported as part of that command response. | |
21911 | ||
21912 | The important examples of notifications are: | |
21913 | @itemize @bullet | |
21914 | ||
21915 | @item | |
21916 | Exec notifications. These are used to report changes in | |
21917 | target state---when a target is resumed, or stopped. It would not | |
21918 | be feasible to include this information in response of resuming | |
21919 | commands, because one resume commands can result in multiple events in | |
21920 | different threads. Also, quite some time may pass before any event | |
21921 | happens in the target, while a frontend needs to know whether the resuming | |
21922 | command itself was successfully executed. | |
21923 | ||
21924 | @item | |
21925 | Console output, and status notifications. Console output | |
21926 | notifications are used to report output of CLI commands, as well as | |
21927 | diagnostics for other commands. Status notifications are used to | |
21928 | report the progress of a long-running operation. Naturally, including | |
21929 | this information in command response would mean no output is produced | |
21930 | until the command is finished, which is undesirable. | |
21931 | ||
21932 | @item | |
21933 | General notifications. Commands may have various side effects on | |
21934 | the @value{GDBN} or target state beyond their official purpose. For example, | |
21935 | a command may change the selected thread. Although such changes can | |
21936 | be included in command response, using notification allows for more | |
21937 | orthogonal frontend design. | |
21938 | ||
21939 | @end itemize | |
21940 | ||
21941 | There's no guarantee that whenever an MI command reports an error, | |
21942 | @value{GDBN} or the target are in any specific state, and especially, | |
21943 | the state is not reverted to the state before the MI command was | |
21944 | processed. Therefore, whenever an MI command results in an error, | |
21945 | we recommend that the frontend refreshes all the information shown in | |
21946 | the user interface. | |
21947 | ||
508094de NR |
21948 | |
21949 | @menu | |
21950 | * Context management:: | |
21951 | * Asynchronous and non-stop modes:: | |
21952 | * Thread groups:: | |
21953 | @end menu | |
21954 | ||
21955 | @node Context management | |
c3b108f7 VP |
21956 | @subsection Context management |
21957 | ||
21958 | In most cases when @value{GDBN} accesses the target, this access is | |
21959 | done in context of a specific thread and frame (@pxref{Frames}). | |
21960 | Often, even when accessing global data, the target requires that a thread | |
21961 | be specified. The CLI interface maintains the selected thread and frame, | |
21962 | and supplies them to target on each command. This is convenient, | |
21963 | because a command line user would not want to specify that information | |
21964 | explicitly on each command, and because user interacts with | |
21965 | @value{GDBN} via a single terminal, so no confusion is possible as | |
21966 | to what thread and frame are the current ones. | |
21967 | ||
21968 | In the case of MI, the concept of selected thread and frame is less | |
21969 | useful. First, a frontend can easily remember this information | |
21970 | itself. Second, a graphical frontend can have more than one window, | |
21971 | each one used for debugging a different thread, and the frontend might | |
21972 | want to access additional threads for internal purposes. This | |
21973 | increases the risk that by relying on implicitly selected thread, the | |
21974 | frontend may be operating on a wrong one. Therefore, each MI command | |
21975 | should explicitly specify which thread and frame to operate on. To | |
21976 | make it possible, each MI command accepts the @samp{--thread} and | |
21977 | @samp{--frame} options, the value to each is @value{GDBN} identifier | |
21978 | for thread and frame to operate on. | |
21979 | ||
21980 | Usually, each top-level window in a frontend allows the user to select | |
21981 | a thread and a frame, and remembers the user selection for further | |
21982 | operations. However, in some cases @value{GDBN} may suggest that the | |
21983 | current thread be changed. For example, when stopping on a breakpoint | |
21984 | it is reasonable to switch to the thread where breakpoint is hit. For | |
21985 | another example, if the user issues the CLI @samp{thread} command via | |
21986 | the frontend, it is desirable to change the frontend's selected thread to the | |
21987 | one specified by user. @value{GDBN} communicates the suggestion to | |
21988 | change current thread using the @samp{=thread-selected} notification. | |
21989 | No such notification is available for the selected frame at the moment. | |
21990 | ||
21991 | Note that historically, MI shares the selected thread with CLI, so | |
21992 | frontends used the @code{-thread-select} to execute commands in the | |
21993 | right context. However, getting this to work right is cumbersome. The | |
21994 | simplest way is for frontend to emit @code{-thread-select} command | |
21995 | before every command. This doubles the number of commands that need | |
21996 | to be sent. The alternative approach is to suppress @code{-thread-select} | |
21997 | if the selected thread in @value{GDBN} is supposed to be identical to the | |
21998 | thread the frontend wants to operate on. However, getting this | |
21999 | optimization right can be tricky. In particular, if the frontend | |
22000 | sends several commands to @value{GDBN}, and one of the commands changes the | |
22001 | selected thread, then the behaviour of subsequent commands will | |
22002 | change. So, a frontend should either wait for response from such | |
22003 | problematic commands, or explicitly add @code{-thread-select} for | |
22004 | all subsequent commands. No frontend is known to do this exactly | |
22005 | right, so it is suggested to just always pass the @samp{--thread} and | |
22006 | @samp{--frame} options. | |
22007 | ||
508094de | 22008 | @node Asynchronous and non-stop modes |
c3b108f7 VP |
22009 | @subsection Asynchronous command execution and non-stop mode |
22010 | ||
22011 | On some targets, @value{GDBN} is capable of processing MI commands | |
22012 | even while the target is running. This is called @dfn{asynchronous | |
22013 | command execution} (@pxref{Background Execution}). The frontend may | |
22014 | specify a preferrence for asynchronous execution using the | |
22015 | @code{-gdb-set target-async 1} command, which should be emitted before | |
22016 | either running the executable or attaching to the target. After the | |
22017 | frontend has started the executable or attached to the target, it can | |
22018 | find if asynchronous execution is enabled using the | |
22019 | @code{-list-target-features} command. | |
22020 | ||
22021 | Even if @value{GDBN} can accept a command while target is running, | |
22022 | many commands that access the target do not work when the target is | |
22023 | running. Therefore, asynchronous command execution is most useful | |
22024 | when combined with non-stop mode (@pxref{Non-Stop Mode}). Then, | |
22025 | it is possible to examine the state of one thread, while other threads | |
22026 | are running. | |
22027 | ||
22028 | When a given thread is running, MI commands that try to access the | |
22029 | target in the context of that thread may not work, or may work only on | |
22030 | some targets. In particular, commands that try to operate on thread's | |
22031 | stack will not work, on any target. Commands that read memory, or | |
22032 | modify breakpoints, may work or not work, depending on the target. Note | |
22033 | that even commands that operate on global state, such as @code{print}, | |
22034 | @code{set}, and breakpoint commands, still access the target in the | |
22035 | context of a specific thread, so frontend should try to find a | |
22036 | stopped thread and perform the operation on that thread (using the | |
22037 | @samp{--thread} option). | |
22038 | ||
22039 | Which commands will work in the context of a running thread is | |
22040 | highly target dependent. However, the two commands | |
22041 | @code{-exec-interrupt}, to stop a thread, and @code{-thread-info}, | |
22042 | to find the state of a thread, will always work. | |
22043 | ||
508094de | 22044 | @node Thread groups |
c3b108f7 VP |
22045 | @subsection Thread groups |
22046 | @value{GDBN} may be used to debug several processes at the same time. | |
22047 | On some platfroms, @value{GDBN} may support debugging of several | |
22048 | hardware systems, each one having several cores with several different | |
22049 | processes running on each core. This section describes the MI | |
22050 | mechanism to support such debugging scenarios. | |
22051 | ||
22052 | The key observation is that regardless of the structure of the | |
22053 | target, MI can have a global list of threads, because most commands that | |
22054 | accept the @samp{--thread} option do not need to know what process that | |
22055 | thread belongs to. Therefore, it is not necessary to introduce | |
22056 | neither additional @samp{--process} option, nor an notion of the | |
22057 | current process in the MI interface. The only strictly new feature | |
22058 | that is required is the ability to find how the threads are grouped | |
22059 | into processes. | |
22060 | ||
22061 | To allow the user to discover such grouping, and to support arbitrary | |
22062 | hierarchy of machines/cores/processes, MI introduces the concept of a | |
22063 | @dfn{thread group}. Thread group is a collection of threads and other | |
22064 | thread groups. A thread group always has a string identifier, a type, | |
22065 | and may have additional attributes specific to the type. A new | |
22066 | command, @code{-list-thread-groups}, returns the list of top-level | |
22067 | thread groups, which correspond to processes that @value{GDBN} is | |
22068 | debugging at the moment. By passing an identifier of a thread group | |
22069 | to the @code{-list-thread-groups} command, it is possible to obtain | |
22070 | the members of specific thread group. | |
22071 | ||
22072 | To allow the user to easily discover processes, and other objects, he | |
22073 | wishes to debug, a concept of @dfn{available thread group} is | |
22074 | introduced. Available thread group is an thread group that | |
22075 | @value{GDBN} is not debugging, but that can be attached to, using the | |
22076 | @code{-target-attach} command. The list of available top-level thread | |
22077 | groups can be obtained using @samp{-list-thread-groups --available}. | |
22078 | In general, the content of a thread group may be only retrieved only | |
22079 | after attaching to that thread group. | |
22080 | ||
a79b8f6e VP |
22081 | Thread groups are related to inferiors (@pxref{Inferiors and |
22082 | Programs}). Each inferior corresponds to a thread group of a special | |
22083 | type @samp{process}, and some additional operations are permitted on | |
22084 | such thread groups. | |
22085 | ||
922fbb7b AC |
22086 | @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% |
22087 | @node GDB/MI Command Syntax | |
22088 | @section @sc{gdb/mi} Command Syntax | |
22089 | ||
22090 | @menu | |
22091 | * GDB/MI Input Syntax:: | |
22092 | * GDB/MI Output Syntax:: | |
922fbb7b AC |
22093 | @end menu |
22094 | ||
22095 | @node GDB/MI Input Syntax | |
22096 | @subsection @sc{gdb/mi} Input Syntax | |
22097 | ||
22098 | @cindex input syntax for @sc{gdb/mi} | |
22099 | @cindex @sc{gdb/mi}, input syntax | |
22100 | @table @code | |
22101 | @item @var{command} @expansion{} | |
22102 | @code{@var{cli-command} | @var{mi-command}} | |
22103 | ||
22104 | @item @var{cli-command} @expansion{} | |
22105 | @code{[ @var{token} ] @var{cli-command} @var{nl}}, where | |
22106 | @var{cli-command} is any existing @value{GDBN} CLI command. | |
22107 | ||
22108 | @item @var{mi-command} @expansion{} | |
22109 | @code{[ @var{token} ] "-" @var{operation} ( " " @var{option} )* | |
22110 | @code{[} " --" @code{]} ( " " @var{parameter} )* @var{nl}} | |
22111 | ||
22112 | @item @var{token} @expansion{} | |
22113 | "any sequence of digits" | |
22114 | ||
22115 | @item @var{option} @expansion{} | |
22116 | @code{"-" @var{parameter} [ " " @var{parameter} ]} | |
22117 | ||
22118 | @item @var{parameter} @expansion{} | |
22119 | @code{@var{non-blank-sequence} | @var{c-string}} | |
22120 | ||
22121 | @item @var{operation} @expansion{} | |
22122 | @emph{any of the operations described in this chapter} | |
22123 | ||
22124 | @item @var{non-blank-sequence} @expansion{} | |
22125 | @emph{anything, provided it doesn't contain special characters such as | |
22126 | "-", @var{nl}, """ and of course " "} | |
22127 | ||
22128 | @item @var{c-string} @expansion{} | |
22129 | @code{""" @var{seven-bit-iso-c-string-content} """} | |
22130 | ||
22131 | @item @var{nl} @expansion{} | |
22132 | @code{CR | CR-LF} | |
22133 | @end table | |
22134 | ||
22135 | @noindent | |
22136 | Notes: | |
22137 | ||
22138 | @itemize @bullet | |
22139 | @item | |
22140 | The CLI commands are still handled by the @sc{mi} interpreter; their | |
22141 | output is described below. | |
22142 | ||
22143 | @item | |
22144 | The @code{@var{token}}, when present, is passed back when the command | |
22145 | finishes. | |
22146 | ||
22147 | @item | |
22148 | Some @sc{mi} commands accept optional arguments as part of the parameter | |
22149 | list. Each option is identified by a leading @samp{-} (dash) and may be | |
22150 | followed by an optional argument parameter. Options occur first in the | |
22151 | parameter list and can be delimited from normal parameters using | |
22152 | @samp{--} (this is useful when some parameters begin with a dash). | |
22153 | @end itemize | |
22154 | ||
22155 | Pragmatics: | |
22156 | ||
22157 | @itemize @bullet | |
22158 | @item | |
22159 | We want easy access to the existing CLI syntax (for debugging). | |
22160 | ||
22161 | @item | |
22162 | We want it to be easy to spot a @sc{mi} operation. | |
22163 | @end itemize | |
22164 | ||
22165 | @node GDB/MI Output Syntax | |
22166 | @subsection @sc{gdb/mi} Output Syntax | |
22167 | ||
22168 | @cindex output syntax of @sc{gdb/mi} | |
22169 | @cindex @sc{gdb/mi}, output syntax | |
22170 | The output from @sc{gdb/mi} consists of zero or more out-of-band records | |
22171 | followed, optionally, by a single result record. This result record | |
22172 | is for the most recent command. The sequence of output records is | |
594fe323 | 22173 | terminated by @samp{(gdb)}. |
922fbb7b AC |
22174 | |
22175 | If an input command was prefixed with a @code{@var{token}} then the | |
22176 | corresponding output for that command will also be prefixed by that same | |
22177 | @var{token}. | |
22178 | ||
22179 | @table @code | |
22180 | @item @var{output} @expansion{} | |
594fe323 | 22181 | @code{( @var{out-of-band-record} )* [ @var{result-record} ] "(gdb)" @var{nl}} |
922fbb7b AC |
22182 | |
22183 | @item @var{result-record} @expansion{} | |
22184 | @code{ [ @var{token} ] "^" @var{result-class} ( "," @var{result} )* @var{nl}} | |
22185 | ||
22186 | @item @var{out-of-band-record} @expansion{} | |
22187 | @code{@var{async-record} | @var{stream-record}} | |
22188 | ||
22189 | @item @var{async-record} @expansion{} | |
22190 | @code{@var{exec-async-output} | @var{status-async-output} | @var{notify-async-output}} | |
22191 | ||
22192 | @item @var{exec-async-output} @expansion{} | |
22193 | @code{[ @var{token} ] "*" @var{async-output}} | |
22194 | ||
22195 | @item @var{status-async-output} @expansion{} | |
22196 | @code{[ @var{token} ] "+" @var{async-output}} | |
22197 | ||
22198 | @item @var{notify-async-output} @expansion{} | |
22199 | @code{[ @var{token} ] "=" @var{async-output}} | |
22200 | ||
22201 | @item @var{async-output} @expansion{} | |
22202 | @code{@var{async-class} ( "," @var{result} )* @var{nl}} | |
22203 | ||
22204 | @item @var{result-class} @expansion{} | |
22205 | @code{"done" | "running" | "connected" | "error" | "exit"} | |
22206 | ||
22207 | @item @var{async-class} @expansion{} | |
22208 | @code{"stopped" | @var{others}} (where @var{others} will be added | |
22209 | depending on the needs---this is still in development). | |
22210 | ||
22211 | @item @var{result} @expansion{} | |
22212 | @code{ @var{variable} "=" @var{value}} | |
22213 | ||
22214 | @item @var{variable} @expansion{} | |
22215 | @code{ @var{string} } | |
22216 | ||
22217 | @item @var{value} @expansion{} | |
22218 | @code{ @var{const} | @var{tuple} | @var{list} } | |
22219 | ||
22220 | @item @var{const} @expansion{} | |
22221 | @code{@var{c-string}} | |
22222 | ||
22223 | @item @var{tuple} @expansion{} | |
22224 | @code{ "@{@}" | "@{" @var{result} ( "," @var{result} )* "@}" } | |
22225 | ||
22226 | @item @var{list} @expansion{} | |
22227 | @code{ "[]" | "[" @var{value} ( "," @var{value} )* "]" | "[" | |
22228 | @var{result} ( "," @var{result} )* "]" } | |
22229 | ||
22230 | @item @var{stream-record} @expansion{} | |
22231 | @code{@var{console-stream-output} | @var{target-stream-output} | @var{log-stream-output}} | |
22232 | ||
22233 | @item @var{console-stream-output} @expansion{} | |
22234 | @code{"~" @var{c-string}} | |
22235 | ||
22236 | @item @var{target-stream-output} @expansion{} | |
22237 | @code{"@@" @var{c-string}} | |
22238 | ||
22239 | @item @var{log-stream-output} @expansion{} | |
22240 | @code{"&" @var{c-string}} | |
22241 | ||
22242 | @item @var{nl} @expansion{} | |
22243 | @code{CR | CR-LF} | |
22244 | ||
22245 | @item @var{token} @expansion{} | |
22246 | @emph{any sequence of digits}. | |
22247 | @end table | |
22248 | ||
22249 | @noindent | |
22250 | Notes: | |
22251 | ||
22252 | @itemize @bullet | |
22253 | @item | |
22254 | All output sequences end in a single line containing a period. | |
22255 | ||
22256 | @item | |
721c02de VP |
22257 | The @code{@var{token}} is from the corresponding request. Note that |
22258 | for all async output, while the token is allowed by the grammar and | |
22259 | may be output by future versions of @value{GDBN} for select async | |
22260 | output messages, it is generally omitted. Frontends should treat | |
22261 | all async output as reporting general changes in the state of the | |
22262 | target and there should be no need to associate async output to any | |
22263 | prior command. | |
922fbb7b AC |
22264 | |
22265 | @item | |
22266 | @cindex status output in @sc{gdb/mi} | |
22267 | @var{status-async-output} contains on-going status information about the | |
22268 | progress of a slow operation. It can be discarded. All status output is | |
22269 | prefixed by @samp{+}. | |
22270 | ||
22271 | @item | |
22272 | @cindex async output in @sc{gdb/mi} | |
22273 | @var{exec-async-output} contains asynchronous state change on the target | |
22274 | (stopped, started, disappeared). All async output is prefixed by | |
22275 | @samp{*}. | |
22276 | ||
22277 | @item | |
22278 | @cindex notify output in @sc{gdb/mi} | |
22279 | @var{notify-async-output} contains supplementary information that the | |
22280 | client should handle (e.g., a new breakpoint information). All notify | |
22281 | output is prefixed by @samp{=}. | |
22282 | ||
22283 | @item | |
22284 | @cindex console output in @sc{gdb/mi} | |
22285 | @var{console-stream-output} is output that should be displayed as is in the | |
22286 | console. It is the textual response to a CLI command. All the console | |
22287 | output is prefixed by @samp{~}. | |
22288 | ||
22289 | @item | |
22290 | @cindex target output in @sc{gdb/mi} | |
22291 | @var{target-stream-output} is the output produced by the target program. | |
22292 | All the target output is prefixed by @samp{@@}. | |
22293 | ||
22294 | @item | |
22295 | @cindex log output in @sc{gdb/mi} | |
22296 | @var{log-stream-output} is output text coming from @value{GDBN}'s internals, for | |
22297 | instance messages that should be displayed as part of an error log. All | |
22298 | the log output is prefixed by @samp{&}. | |
22299 | ||
22300 | @item | |
22301 | @cindex list output in @sc{gdb/mi} | |
22302 | New @sc{gdb/mi} commands should only output @var{lists} containing | |
22303 | @var{values}. | |
22304 | ||
22305 | ||
22306 | @end itemize | |
22307 | ||
22308 | @xref{GDB/MI Stream Records, , @sc{gdb/mi} Stream Records}, for more | |
22309 | details about the various output records. | |
22310 | ||
922fbb7b AC |
22311 | @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% |
22312 | @node GDB/MI Compatibility with CLI | |
22313 | @section @sc{gdb/mi} Compatibility with CLI | |
22314 | ||
22315 | @cindex compatibility, @sc{gdb/mi} and CLI | |
22316 | @cindex @sc{gdb/mi}, compatibility with CLI | |
922fbb7b | 22317 | |
a2c02241 NR |
22318 | For the developers convenience CLI commands can be entered directly, |
22319 | but there may be some unexpected behaviour. For example, commands | |
22320 | that query the user will behave as if the user replied yes, breakpoint | |
22321 | command lists are not executed and some CLI commands, such as | |
22322 | @code{if}, @code{when} and @code{define}, prompt for further input with | |
22323 | @samp{>}, which is not valid MI output. | |
ef21caaf NR |
22324 | |
22325 | This feature may be removed at some stage in the future and it is | |
a2c02241 NR |
22326 | recommended that front ends use the @code{-interpreter-exec} command |
22327 | (@pxref{-interpreter-exec}). | |
922fbb7b | 22328 | |
af6eff6f NR |
22329 | @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% |
22330 | @node GDB/MI Development and Front Ends | |
22331 | @section @sc{gdb/mi} Development and Front Ends | |
22332 | @cindex @sc{gdb/mi} development | |
22333 | ||
22334 | The application which takes the MI output and presents the state of the | |
22335 | program being debugged to the user is called a @dfn{front end}. | |
22336 | ||
22337 | Although @sc{gdb/mi} is still incomplete, it is currently being used | |
22338 | by a variety of front ends to @value{GDBN}. This makes it difficult | |
22339 | to introduce new functionality without breaking existing usage. This | |
22340 | section tries to minimize the problems by describing how the protocol | |
22341 | might change. | |
22342 | ||
22343 | Some changes in MI need not break a carefully designed front end, and | |
22344 | for these the MI version will remain unchanged. The following is a | |
22345 | list of changes that may occur within one level, so front ends should | |
22346 | parse MI output in a way that can handle them: | |
22347 | ||
22348 | @itemize @bullet | |
22349 | @item | |
22350 | New MI commands may be added. | |
22351 | ||
22352 | @item | |
22353 | New fields may be added to the output of any MI command. | |
22354 | ||
36ece8b3 NR |
22355 | @item |
22356 | The range of values for fields with specified values, e.g., | |
9f708cb2 | 22357 | @code{in_scope} (@pxref{-var-update}) may be extended. |
36ece8b3 | 22358 | |
af6eff6f NR |
22359 | @c The format of field's content e.g type prefix, may change so parse it |
22360 | @c at your own risk. Yes, in general? | |
22361 | ||
22362 | @c The order of fields may change? Shouldn't really matter but it might | |
22363 | @c resolve inconsistencies. | |
22364 | @end itemize | |
22365 | ||
22366 | If the changes are likely to break front ends, the MI version level | |
22367 | will be increased by one. This will allow the front end to parse the | |
22368 | output according to the MI version. Apart from mi0, new versions of | |
22369 | @value{GDBN} will not support old versions of MI and it will be the | |
22370 | responsibility of the front end to work with the new one. | |
22371 | ||
22372 | @c Starting with mi3, add a new command -mi-version that prints the MI | |
22373 | @c version? | |
22374 | ||
22375 | The best way to avoid unexpected changes in MI that might break your front | |
22376 | end is to make your project known to @value{GDBN} developers and | |
7a9a6b69 | 22377 | follow development on @email{gdb@@sourceware.org} and |
fa0f268d | 22378 | @email{gdb-patches@@sourceware.org}. |
af6eff6f NR |
22379 | @cindex mailing lists |
22380 | ||
922fbb7b AC |
22381 | @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% |
22382 | @node GDB/MI Output Records | |
22383 | @section @sc{gdb/mi} Output Records | |
22384 | ||
22385 | @menu | |
22386 | * GDB/MI Result Records:: | |
22387 | * GDB/MI Stream Records:: | |
82f68b1c | 22388 | * GDB/MI Async Records:: |
c3b108f7 | 22389 | * GDB/MI Frame Information:: |
dc146f7c | 22390 | * GDB/MI Thread Information:: |
922fbb7b AC |
22391 | @end menu |
22392 | ||
22393 | @node GDB/MI Result Records | |
22394 | @subsection @sc{gdb/mi} Result Records | |
22395 | ||
22396 | @cindex result records in @sc{gdb/mi} | |
22397 | @cindex @sc{gdb/mi}, result records | |
22398 | In addition to a number of out-of-band notifications, the response to a | |
22399 | @sc{gdb/mi} command includes one of the following result indications: | |
22400 | ||
22401 | @table @code | |
22402 | @findex ^done | |
22403 | @item "^done" [ "," @var{results} ] | |
22404 | The synchronous operation was successful, @code{@var{results}} are the return | |
22405 | values. | |
22406 | ||
22407 | @item "^running" | |
22408 | @findex ^running | |
8e9c5e02 VP |
22409 | This result record is equivalent to @samp{^done}. Historically, it |
22410 | was output instead of @samp{^done} if the command has resumed the | |
22411 | target. This behaviour is maintained for backward compatibility, but | |
22412 | all frontends should treat @samp{^done} and @samp{^running} | |
22413 | identically and rely on the @samp{*running} output record to determine | |
22414 | which threads are resumed. | |
922fbb7b | 22415 | |
ef21caaf NR |
22416 | @item "^connected" |
22417 | @findex ^connected | |
3f94c067 | 22418 | @value{GDBN} has connected to a remote target. |
ef21caaf | 22419 | |
922fbb7b AC |
22420 | @item "^error" "," @var{c-string} |
22421 | @findex ^error | |
22422 | The operation failed. The @code{@var{c-string}} contains the corresponding | |
22423 | error message. | |
ef21caaf NR |
22424 | |
22425 | @item "^exit" | |
22426 | @findex ^exit | |
3f94c067 | 22427 | @value{GDBN} has terminated. |
ef21caaf | 22428 | |
922fbb7b AC |
22429 | @end table |
22430 | ||
22431 | @node GDB/MI Stream Records | |
22432 | @subsection @sc{gdb/mi} Stream Records | |
22433 | ||
22434 | @cindex @sc{gdb/mi}, stream records | |
22435 | @cindex stream records in @sc{gdb/mi} | |
22436 | @value{GDBN} internally maintains a number of output streams: the console, the | |
22437 | target, and the log. The output intended for each of these streams is | |
22438 | funneled through the @sc{gdb/mi} interface using @dfn{stream records}. | |
22439 | ||
22440 | Each stream record begins with a unique @dfn{prefix character} which | |
22441 | identifies its stream (@pxref{GDB/MI Output Syntax, , @sc{gdb/mi} Output | |
22442 | Syntax}). In addition to the prefix, each stream record contains a | |
22443 | @code{@var{string-output}}. This is either raw text (with an implicit new | |
22444 | line) or a quoted C string (which does not contain an implicit newline). | |
22445 | ||
22446 | @table @code | |
22447 | @item "~" @var{string-output} | |
22448 | The console output stream contains text that should be displayed in the | |
22449 | CLI console window. It contains the textual responses to CLI commands. | |
22450 | ||
22451 | @item "@@" @var{string-output} | |
22452 | The target output stream contains any textual output from the running | |
ef21caaf NR |
22453 | target. This is only present when GDB's event loop is truly |
22454 | asynchronous, which is currently only the case for remote targets. | |
922fbb7b AC |
22455 | |
22456 | @item "&" @var{string-output} | |
22457 | The log stream contains debugging messages being produced by @value{GDBN}'s | |
22458 | internals. | |
22459 | @end table | |
22460 | ||
82f68b1c VP |
22461 | @node GDB/MI Async Records |
22462 | @subsection @sc{gdb/mi} Async Records | |
922fbb7b | 22463 | |
82f68b1c VP |
22464 | @cindex async records in @sc{gdb/mi} |
22465 | @cindex @sc{gdb/mi}, async records | |
22466 | @dfn{Async} records are used to notify the @sc{gdb/mi} client of | |
922fbb7b | 22467 | additional changes that have occurred. Those changes can either be a |
82f68b1c | 22468 | consequence of @sc{gdb/mi} commands (e.g., a breakpoint modified) or a result of |
922fbb7b AC |
22469 | target activity (e.g., target stopped). |
22470 | ||
8eb41542 | 22471 | The following is the list of possible async records: |
922fbb7b AC |
22472 | |
22473 | @table @code | |
034dad6f | 22474 | |
e1ac3328 VP |
22475 | @item *running,thread-id="@var{thread}" |
22476 | The target is now running. The @var{thread} field tells which | |
22477 | specific thread is now running, and can be @samp{all} if all threads | |
22478 | are running. The frontend should assume that no interaction with a | |
22479 | running thread is possible after this notification is produced. | |
22480 | The frontend should not assume that this notification is output | |
22481 | only once for any command. @value{GDBN} may emit this notification | |
22482 | several times, either for different threads, because it cannot resume | |
22483 | all threads together, or even for a single thread, if the thread must | |
22484 | be stepped though some code before letting it run freely. | |
22485 | ||
dc146f7c | 22486 | @item *stopped,reason="@var{reason}",thread-id="@var{id}",stopped-threads="@var{stopped}",core="@var{core}" |
82f68b1c VP |
22487 | The target has stopped. The @var{reason} field can have one of the |
22488 | following values: | |
034dad6f BR |
22489 | |
22490 | @table @code | |
22491 | @item breakpoint-hit | |
22492 | A breakpoint was reached. | |
22493 | @item watchpoint-trigger | |
22494 | A watchpoint was triggered. | |
22495 | @item read-watchpoint-trigger | |
22496 | A read watchpoint was triggered. | |
22497 | @item access-watchpoint-trigger | |
22498 | An access watchpoint was triggered. | |
22499 | @item function-finished | |
22500 | An -exec-finish or similar CLI command was accomplished. | |
22501 | @item location-reached | |
22502 | An -exec-until or similar CLI command was accomplished. | |
22503 | @item watchpoint-scope | |
22504 | A watchpoint has gone out of scope. | |
22505 | @item end-stepping-range | |
22506 | An -exec-next, -exec-next-instruction, -exec-step, -exec-step-instruction or | |
22507 | similar CLI command was accomplished. | |
22508 | @item exited-signalled | |
22509 | The inferior exited because of a signal. | |
22510 | @item exited | |
22511 | The inferior exited. | |
22512 | @item exited-normally | |
22513 | The inferior exited normally. | |
22514 | @item signal-received | |
22515 | A signal was received by the inferior. | |
922fbb7b AC |
22516 | @end table |
22517 | ||
c3b108f7 VP |
22518 | The @var{id} field identifies the thread that directly caused the stop |
22519 | -- for example by hitting a breakpoint. Depending on whether all-stop | |
22520 | mode is in effect (@pxref{All-Stop Mode}), @value{GDBN} may either | |
22521 | stop all threads, or only the thread that directly triggered the stop. | |
22522 | If all threads are stopped, the @var{stopped} field will have the | |
22523 | value of @code{"all"}. Otherwise, the value of the @var{stopped} | |
22524 | field will be a list of thread identifiers. Presently, this list will | |
22525 | always include a single thread, but frontend should be prepared to see | |
dc146f7c VP |
22526 | several threads in the list. The @var{core} field reports the |
22527 | processor core on which the stop event has happened. This field may be absent | |
22528 | if such information is not available. | |
c3b108f7 | 22529 | |
a79b8f6e VP |
22530 | @item =thread-group-added,id="@var{id}" |
22531 | @itemx =thread-group-removed,id="@var{id}" | |
22532 | A thread group was either added or removed. The @var{id} field | |
22533 | contains the @value{GDBN} identifier of the thread group. When a thread | |
22534 | group is added, it generally might not be associated with a running | |
22535 | process. When a thread group is removed, its id becomes invalid and | |
22536 | cannot be used in any way. | |
22537 | ||
22538 | @item =thread-group-started,id="@var{id}",pid="@var{pid}" | |
22539 | A thread group became associated with a running program, | |
22540 | either because the program was just started or the thread group | |
22541 | was attached to a program. The @var{id} field contains the | |
22542 | @value{GDBN} identifier of the thread group. The @var{pid} field | |
22543 | contains process identifier, specific to the operating system. | |
22544 | ||
c3b108f7 | 22545 | @itemx =thread-group-exited,id="@var{id}" |
a79b8f6e VP |
22546 | A thread group is no longer associated with a running program, |
22547 | either because the program has exited, or because it was detached | |
c3b108f7 VP |
22548 | from. The @var{id} field contains the @value{GDBN} identifier of the |
22549 | thread group. | |
22550 | ||
22551 | @item =thread-created,id="@var{id}",group-id="@var{gid}" | |
22552 | @itemx =thread-exited,id="@var{id}",group-id="@var{gid}" | |
82f68b1c | 22553 | A thread either was created, or has exited. The @var{id} field |
c3b108f7 VP |
22554 | contains the @value{GDBN} identifier of the thread. The @var{gid} |
22555 | field identifies the thread group this thread belongs to. | |
66bb093b VP |
22556 | |
22557 | @item =thread-selected,id="@var{id}" | |
22558 | Informs that the selected thread was changed as result of the last | |
22559 | command. This notification is not emitted as result of @code{-thread-select} | |
22560 | command but is emitted whenever an MI command that is not documented | |
22561 | to change the selected thread actually changes it. In particular, | |
22562 | invoking, directly or indirectly (via user-defined command), the CLI | |
22563 | @code{thread} command, will generate this notification. | |
22564 | ||
22565 | We suggest that in response to this notification, front ends | |
22566 | highlight the selected thread and cause subsequent commands to apply to | |
22567 | that thread. | |
22568 | ||
c86cf029 VP |
22569 | @item =library-loaded,... |
22570 | Reports that a new library file was loaded by the program. This | |
22571 | notification has 4 fields---@var{id}, @var{target-name}, | |
134eb42c | 22572 | @var{host-name}, and @var{symbols-loaded}. The @var{id} field is an |
c86cf029 VP |
22573 | opaque identifier of the library. For remote debugging case, |
22574 | @var{target-name} and @var{host-name} fields give the name of the | |
134eb42c VP |
22575 | library file on the target, and on the host respectively. For native |
22576 | debugging, both those fields have the same value. The | |
c86cf029 | 22577 | @var{symbols-loaded} field reports if the debug symbols for this |
a79b8f6e VP |
22578 | library are loaded. The @var{thread-group} field, if present, |
22579 | specifies the id of the thread group in whose context the library was loaded. | |
22580 | If the field is absent, it means the library was loaded in the context | |
22581 | of all present thread groups. | |
c86cf029 VP |
22582 | |
22583 | @item =library-unloaded,... | |
134eb42c | 22584 | Reports that a library was unloaded by the program. This notification |
c86cf029 | 22585 | has 3 fields---@var{id}, @var{target-name} and @var{host-name} with |
a79b8f6e VP |
22586 | the same meaning as for the @code{=library-loaded} notification. |
22587 | The @var{thread-group} field, if present, specifies the id of the | |
22588 | thread group in whose context the library was unloaded. If the field is | |
22589 | absent, it means the library was unloaded in the context of all present | |
22590 | thread groups. | |
c86cf029 | 22591 | |
82f68b1c VP |
22592 | @end table |
22593 | ||
c3b108f7 VP |
22594 | @node GDB/MI Frame Information |
22595 | @subsection @sc{gdb/mi} Frame Information | |
22596 | ||
22597 | Response from many MI commands includes an information about stack | |
22598 | frame. This information is a tuple that may have the following | |
22599 | fields: | |
22600 | ||
22601 | @table @code | |
22602 | @item level | |
22603 | The level of the stack frame. The innermost frame has the level of | |
22604 | zero. This field is always present. | |
22605 | ||
22606 | @item func | |
22607 | The name of the function corresponding to the frame. This field may | |
22608 | be absent if @value{GDBN} is unable to determine the function name. | |
22609 | ||
22610 | @item addr | |
22611 | The code address for the frame. This field is always present. | |
22612 | ||
22613 | @item file | |
22614 | The name of the source files that correspond to the frame's code | |
22615 | address. This field may be absent. | |
22616 | ||
22617 | @item line | |
22618 | The source line corresponding to the frames' code address. This field | |
22619 | may be absent. | |
22620 | ||
22621 | @item from | |
22622 | The name of the binary file (either executable or shared library) the | |
22623 | corresponds to the frame's code address. This field may be absent. | |
22624 | ||
22625 | @end table | |
82f68b1c | 22626 | |
dc146f7c VP |
22627 | @node GDB/MI Thread Information |
22628 | @subsection @sc{gdb/mi} Thread Information | |
22629 | ||
22630 | Whenever @value{GDBN} has to report an information about a thread, it | |
22631 | uses a tuple with the following fields: | |
22632 | ||
22633 | @table @code | |
22634 | @item id | |
22635 | The numeric id assigned to the thread by @value{GDBN}. This field is | |
22636 | always present. | |
22637 | ||
22638 | @item target-id | |
22639 | Target-specific string identifying the thread. This field is always present. | |
22640 | ||
22641 | @item details | |
22642 | Additional information about the thread provided by the target. | |
22643 | It is supposed to be human-readable and not interpreted by the | |
22644 | frontend. This field is optional. | |
22645 | ||
22646 | @item state | |
22647 | Either @samp{stopped} or @samp{running}, depending on whether the | |
22648 | thread is presently running. This field is always present. | |
22649 | ||
22650 | @item core | |
22651 | The value of this field is an integer number of the processor core the | |
22652 | thread was last seen on. This field is optional. | |
22653 | @end table | |
22654 | ||
922fbb7b | 22655 | |
ef21caaf NR |
22656 | @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% |
22657 | @node GDB/MI Simple Examples | |
22658 | @section Simple Examples of @sc{gdb/mi} Interaction | |
22659 | @cindex @sc{gdb/mi}, simple examples | |
22660 | ||
22661 | This subsection presents several simple examples of interaction using | |
22662 | the @sc{gdb/mi} interface. In these examples, @samp{->} means that the | |
22663 | following line is passed to @sc{gdb/mi} as input, while @samp{<-} means | |
22664 | the output received from @sc{gdb/mi}. | |
22665 | ||
d3e8051b | 22666 | Note the line breaks shown in the examples are here only for |
ef21caaf NR |
22667 | readability, they don't appear in the real output. |
22668 | ||
79a6e687 | 22669 | @subheading Setting a Breakpoint |
ef21caaf NR |
22670 | |
22671 | Setting a breakpoint generates synchronous output which contains detailed | |
22672 | information of the breakpoint. | |
22673 | ||
22674 | @smallexample | |
22675 | -> -break-insert main | |
22676 | <- ^done,bkpt=@{number="1",type="breakpoint",disp="keep", | |
22677 | enabled="y",addr="0x08048564",func="main",file="myprog.c", | |
22678 | fullname="/home/nickrob/myprog.c",line="68",times="0"@} | |
22679 | <- (gdb) | |
22680 | @end smallexample | |
22681 | ||
22682 | @subheading Program Execution | |
22683 | ||
22684 | Program execution generates asynchronous records and MI gives the | |
22685 | reason that execution stopped. | |
22686 | ||
22687 | @smallexample | |
22688 | -> -exec-run | |
22689 | <- ^running | |
22690 | <- (gdb) | |
a47ec5fe | 22691 | <- *stopped,reason="breakpoint-hit",disp="keep",bkptno="1",thread-id="0", |
ef21caaf NR |
22692 | frame=@{addr="0x08048564",func="main", |
22693 | args=[@{name="argc",value="1"@},@{name="argv",value="0xbfc4d4d4"@}], | |
22694 | file="myprog.c",fullname="/home/nickrob/myprog.c",line="68"@} | |
22695 | <- (gdb) | |
22696 | -> -exec-continue | |
22697 | <- ^running | |
22698 | <- (gdb) | |
22699 | <- *stopped,reason="exited-normally" | |
22700 | <- (gdb) | |
22701 | @end smallexample | |
22702 | ||
3f94c067 | 22703 | @subheading Quitting @value{GDBN} |
ef21caaf | 22704 | |
3f94c067 | 22705 | Quitting @value{GDBN} just prints the result class @samp{^exit}. |
ef21caaf NR |
22706 | |
22707 | @smallexample | |
22708 | -> (gdb) | |
22709 | <- -gdb-exit | |
22710 | <- ^exit | |
22711 | @end smallexample | |
22712 | ||
a6b29f87 VP |
22713 | Please note that @samp{^exit} is printed immediately, but it might |
22714 | take some time for @value{GDBN} to actually exit. During that time, @value{GDBN} | |
22715 | performs necessary cleanups, including killing programs being debugged | |
22716 | or disconnecting from debug hardware, so the frontend should wait till | |
22717 | @value{GDBN} exits and should only forcibly kill @value{GDBN} if it | |
22718 | fails to exit in reasonable time. | |
22719 | ||
a2c02241 | 22720 | @subheading A Bad Command |
ef21caaf NR |
22721 | |
22722 | Here's what happens if you pass a non-existent command: | |
22723 | ||
22724 | @smallexample | |
22725 | -> -rubbish | |
22726 | <- ^error,msg="Undefined MI command: rubbish" | |
594fe323 | 22727 | <- (gdb) |
ef21caaf NR |
22728 | @end smallexample |
22729 | ||
22730 | ||
922fbb7b AC |
22731 | @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% |
22732 | @node GDB/MI Command Description Format | |
22733 | @section @sc{gdb/mi} Command Description Format | |
22734 | ||
22735 | The remaining sections describe blocks of commands. Each block of | |
22736 | commands is laid out in a fashion similar to this section. | |
22737 | ||
922fbb7b AC |
22738 | @subheading Motivation |
22739 | ||
22740 | The motivation for this collection of commands. | |
22741 | ||
22742 | @subheading Introduction | |
22743 | ||
22744 | A brief introduction to this collection of commands as a whole. | |
22745 | ||
22746 | @subheading Commands | |
22747 | ||
22748 | For each command in the block, the following is described: | |
22749 | ||
22750 | @subsubheading Synopsis | |
22751 | ||
22752 | @smallexample | |
22753 | -command @var{args}@dots{} | |
22754 | @end smallexample | |
22755 | ||
922fbb7b AC |
22756 | @subsubheading Result |
22757 | ||
265eeb58 | 22758 | @subsubheading @value{GDBN} Command |
922fbb7b | 22759 | |
265eeb58 | 22760 | The corresponding @value{GDBN} CLI command(s), if any. |
922fbb7b AC |
22761 | |
22762 | @subsubheading Example | |
22763 | ||
ef21caaf NR |
22764 | Example(s) formatted for readability. Some of the described commands have |
22765 | not been implemented yet and these are labeled N.A.@: (not available). | |
22766 | ||
22767 | ||
922fbb7b | 22768 | @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% |
ef21caaf NR |
22769 | @node GDB/MI Breakpoint Commands |
22770 | @section @sc{gdb/mi} Breakpoint Commands | |
922fbb7b AC |
22771 | |
22772 | @cindex breakpoint commands for @sc{gdb/mi} | |
22773 | @cindex @sc{gdb/mi}, breakpoint commands | |
22774 | This section documents @sc{gdb/mi} commands for manipulating | |
22775 | breakpoints. | |
22776 | ||
22777 | @subheading The @code{-break-after} Command | |
22778 | @findex -break-after | |
22779 | ||
22780 | @subsubheading Synopsis | |
22781 | ||
22782 | @smallexample | |
22783 | -break-after @var{number} @var{count} | |
22784 | @end smallexample | |
22785 | ||
22786 | The breakpoint number @var{number} is not in effect until it has been | |
22787 | hit @var{count} times. To see how this is reflected in the output of | |
22788 | the @samp{-break-list} command, see the description of the | |
22789 | @samp{-break-list} command below. | |
22790 | ||
22791 | @subsubheading @value{GDBN} Command | |
22792 | ||
22793 | The corresponding @value{GDBN} command is @samp{ignore}. | |
22794 | ||
22795 | @subsubheading Example | |
22796 | ||
22797 | @smallexample | |
594fe323 | 22798 | (gdb) |
922fbb7b | 22799 | -break-insert main |
a47ec5fe AR |
22800 | ^done,bkpt=@{number="1",type="breakpoint",disp="keep", |
22801 | enabled="y",addr="0x000100d0",func="main",file="hello.c", | |
948d5102 | 22802 | fullname="/home/foo/hello.c",line="5",times="0"@} |
594fe323 | 22803 | (gdb) |
922fbb7b AC |
22804 | -break-after 1 3 |
22805 | ~ | |
22806 | ^done | |
594fe323 | 22807 | (gdb) |
922fbb7b AC |
22808 | -break-list |
22809 | ^done,BreakpointTable=@{nr_rows="1",nr_cols="6", | |
22810 | hdr=[@{width="3",alignment="-1",col_name="number",colhdr="Num"@}, | |
22811 | @{width="14",alignment="-1",col_name="type",colhdr="Type"@}, | |
22812 | @{width="4",alignment="-1",col_name="disp",colhdr="Disp"@}, | |
22813 | @{width="3",alignment="-1",col_name="enabled",colhdr="Enb"@}, | |
22814 | @{width="10",alignment="-1",col_name="addr",colhdr="Address"@}, | |
22815 | @{width="40",alignment="2",col_name="what",colhdr="What"@}], | |
22816 | body=[bkpt=@{number="1",type="breakpoint",disp="keep",enabled="y", | |
948d5102 NR |
22817 | addr="0x000100d0",func="main",file="hello.c",fullname="/home/foo/hello.c", |
22818 | line="5",times="0",ignore="3"@}]@} | |
594fe323 | 22819 | (gdb) |
922fbb7b AC |
22820 | @end smallexample |
22821 | ||
22822 | @ignore | |
22823 | @subheading The @code{-break-catch} Command | |
22824 | @findex -break-catch | |
48cb2d85 | 22825 | @end ignore |
922fbb7b AC |
22826 | |
22827 | @subheading The @code{-break-commands} Command | |
22828 | @findex -break-commands | |
922fbb7b | 22829 | |
48cb2d85 VP |
22830 | @subsubheading Synopsis |
22831 | ||
22832 | @smallexample | |
22833 | -break-commands @var{number} [ @var{command1} ... @var{commandN} ] | |
22834 | @end smallexample | |
22835 | ||
22836 | Specifies the CLI commands that should be executed when breakpoint | |
22837 | @var{number} is hit. The parameters @var{command1} to @var{commandN} | |
22838 | are the commands. If no command is specified, any previously-set | |
22839 | commands are cleared. @xref{Break Commands}. Typical use of this | |
22840 | functionality is tracing a program, that is, printing of values of | |
22841 | some variables whenever breakpoint is hit and then continuing. | |
22842 | ||
22843 | @subsubheading @value{GDBN} Command | |
22844 | ||
22845 | The corresponding @value{GDBN} command is @samp{commands}. | |
22846 | ||
22847 | @subsubheading Example | |
22848 | ||
22849 | @smallexample | |
22850 | (gdb) | |
22851 | -break-insert main | |
22852 | ^done,bkpt=@{number="1",type="breakpoint",disp="keep", | |
22853 | enabled="y",addr="0x000100d0",func="main",file="hello.c", | |
22854 | fullname="/home/foo/hello.c",line="5",times="0"@} | |
22855 | (gdb) | |
22856 | -break-commands 1 "print v" "continue" | |
22857 | ^done | |
22858 | (gdb) | |
22859 | @end smallexample | |
922fbb7b AC |
22860 | |
22861 | @subheading The @code{-break-condition} Command | |
22862 | @findex -break-condition | |
22863 | ||
22864 | @subsubheading Synopsis | |
22865 | ||
22866 | @smallexample | |
22867 | -break-condition @var{number} @var{expr} | |
22868 | @end smallexample | |
22869 | ||
22870 | Breakpoint @var{number} will stop the program only if the condition in | |
22871 | @var{expr} is true. The condition becomes part of the | |
22872 | @samp{-break-list} output (see the description of the @samp{-break-list} | |
22873 | command below). | |
22874 | ||
22875 | @subsubheading @value{GDBN} Command | |
22876 | ||
22877 | The corresponding @value{GDBN} command is @samp{condition}. | |
22878 | ||
22879 | @subsubheading Example | |
22880 | ||
22881 | @smallexample | |
594fe323 | 22882 | (gdb) |
922fbb7b AC |
22883 | -break-condition 1 1 |
22884 | ^done | |
594fe323 | 22885 | (gdb) |
922fbb7b AC |
22886 | -break-list |
22887 | ^done,BreakpointTable=@{nr_rows="1",nr_cols="6", | |
22888 | hdr=[@{width="3",alignment="-1",col_name="number",colhdr="Num"@}, | |
22889 | @{width="14",alignment="-1",col_name="type",colhdr="Type"@}, | |
22890 | @{width="4",alignment="-1",col_name="disp",colhdr="Disp"@}, | |
22891 | @{width="3",alignment="-1",col_name="enabled",colhdr="Enb"@}, | |
22892 | @{width="10",alignment="-1",col_name="addr",colhdr="Address"@}, | |
22893 | @{width="40",alignment="2",col_name="what",colhdr="What"@}], | |
22894 | body=[bkpt=@{number="1",type="breakpoint",disp="keep",enabled="y", | |
948d5102 NR |
22895 | addr="0x000100d0",func="main",file="hello.c",fullname="/home/foo/hello.c", |
22896 | line="5",cond="1",times="0",ignore="3"@}]@} | |
594fe323 | 22897 | (gdb) |
922fbb7b AC |
22898 | @end smallexample |
22899 | ||
22900 | @subheading The @code{-break-delete} Command | |
22901 | @findex -break-delete | |
22902 | ||
22903 | @subsubheading Synopsis | |
22904 | ||
22905 | @smallexample | |
22906 | -break-delete ( @var{breakpoint} )+ | |
22907 | @end smallexample | |
22908 | ||
22909 | Delete the breakpoint(s) whose number(s) are specified in the argument | |
22910 | list. This is obviously reflected in the breakpoint list. | |
22911 | ||
79a6e687 | 22912 | @subsubheading @value{GDBN} Command |
922fbb7b AC |
22913 | |
22914 | The corresponding @value{GDBN} command is @samp{delete}. | |
22915 | ||
22916 | @subsubheading Example | |
22917 | ||
22918 | @smallexample | |
594fe323 | 22919 | (gdb) |
922fbb7b AC |
22920 | -break-delete 1 |
22921 | ^done | |
594fe323 | 22922 | (gdb) |
922fbb7b AC |
22923 | -break-list |
22924 | ^done,BreakpointTable=@{nr_rows="0",nr_cols="6", | |
22925 | hdr=[@{width="3",alignment="-1",col_name="number",colhdr="Num"@}, | |
22926 | @{width="14",alignment="-1",col_name="type",colhdr="Type"@}, | |
22927 | @{width="4",alignment="-1",col_name="disp",colhdr="Disp"@}, | |
22928 | @{width="3",alignment="-1",col_name="enabled",colhdr="Enb"@}, | |
22929 | @{width="10",alignment="-1",col_name="addr",colhdr="Address"@}, | |
22930 | @{width="40",alignment="2",col_name="what",colhdr="What"@}], | |
22931 | body=[]@} | |
594fe323 | 22932 | (gdb) |
922fbb7b AC |
22933 | @end smallexample |
22934 | ||
22935 | @subheading The @code{-break-disable} Command | |
22936 | @findex -break-disable | |
22937 | ||
22938 | @subsubheading Synopsis | |
22939 | ||
22940 | @smallexample | |
22941 | -break-disable ( @var{breakpoint} )+ | |
22942 | @end smallexample | |
22943 | ||
22944 | Disable the named @var{breakpoint}(s). The field @samp{enabled} in the | |
22945 | break list is now set to @samp{n} for the named @var{breakpoint}(s). | |
22946 | ||
22947 | @subsubheading @value{GDBN} Command | |
22948 | ||
22949 | The corresponding @value{GDBN} command is @samp{disable}. | |
22950 | ||
22951 | @subsubheading Example | |
22952 | ||
22953 | @smallexample | |
594fe323 | 22954 | (gdb) |
922fbb7b AC |
22955 | -break-disable 2 |
22956 | ^done | |
594fe323 | 22957 | (gdb) |
922fbb7b AC |
22958 | -break-list |
22959 | ^done,BreakpointTable=@{nr_rows="1",nr_cols="6", | |
22960 | hdr=[@{width="3",alignment="-1",col_name="number",colhdr="Num"@}, | |
22961 | @{width="14",alignment="-1",col_name="type",colhdr="Type"@}, | |
22962 | @{width="4",alignment="-1",col_name="disp",colhdr="Disp"@}, | |
22963 | @{width="3",alignment="-1",col_name="enabled",colhdr="Enb"@}, | |
22964 | @{width="10",alignment="-1",col_name="addr",colhdr="Address"@}, | |
22965 | @{width="40",alignment="2",col_name="what",colhdr="What"@}], | |
22966 | body=[bkpt=@{number="2",type="breakpoint",disp="keep",enabled="n", | |
948d5102 NR |
22967 | addr="0x000100d0",func="main",file="hello.c",fullname="/home/foo/hello.c", |
22968 | line="5",times="0"@}]@} | |
594fe323 | 22969 | (gdb) |
922fbb7b AC |
22970 | @end smallexample |
22971 | ||
22972 | @subheading The @code{-break-enable} Command | |
22973 | @findex -break-enable | |
22974 | ||
22975 | @subsubheading Synopsis | |
22976 | ||
22977 | @smallexample | |
22978 | -break-enable ( @var{breakpoint} )+ | |
22979 | @end smallexample | |
22980 | ||
22981 | Enable (previously disabled) @var{breakpoint}(s). | |
22982 | ||
22983 | @subsubheading @value{GDBN} Command | |
22984 | ||
22985 | The corresponding @value{GDBN} command is @samp{enable}. | |
22986 | ||
22987 | @subsubheading Example | |
22988 | ||
22989 | @smallexample | |
594fe323 | 22990 | (gdb) |
922fbb7b AC |
22991 | -break-enable 2 |
22992 | ^done | |
594fe323 | 22993 | (gdb) |
922fbb7b AC |
22994 | -break-list |
22995 | ^done,BreakpointTable=@{nr_rows="1",nr_cols="6", | |
22996 | hdr=[@{width="3",alignment="-1",col_name="number",colhdr="Num"@}, | |
22997 | @{width="14",alignment="-1",col_name="type",colhdr="Type"@}, | |
22998 | @{width="4",alignment="-1",col_name="disp",colhdr="Disp"@}, | |
22999 | @{width="3",alignment="-1",col_name="enabled",colhdr="Enb"@}, | |
23000 | @{width="10",alignment="-1",col_name="addr",colhdr="Address"@}, | |
23001 | @{width="40",alignment="2",col_name="what",colhdr="What"@}], | |
23002 | body=[bkpt=@{number="2",type="breakpoint",disp="keep",enabled="y", | |
948d5102 NR |
23003 | addr="0x000100d0",func="main",file="hello.c",fullname="/home/foo/hello.c", |
23004 | line="5",times="0"@}]@} | |
594fe323 | 23005 | (gdb) |
922fbb7b AC |
23006 | @end smallexample |
23007 | ||
23008 | @subheading The @code{-break-info} Command | |
23009 | @findex -break-info | |
23010 | ||
23011 | @subsubheading Synopsis | |
23012 | ||
23013 | @smallexample | |
23014 | -break-info @var{breakpoint} | |
23015 | @end smallexample | |
23016 | ||
23017 | @c REDUNDANT??? | |
23018 | Get information about a single breakpoint. | |
23019 | ||
79a6e687 | 23020 | @subsubheading @value{GDBN} Command |
922fbb7b AC |
23021 | |
23022 | The corresponding @value{GDBN} command is @samp{info break @var{breakpoint}}. | |
23023 | ||
23024 | @subsubheading Example | |
23025 | N.A. | |
23026 | ||
23027 | @subheading The @code{-break-insert} Command | |
23028 | @findex -break-insert | |
23029 | ||
23030 | @subsubheading Synopsis | |
23031 | ||
23032 | @smallexample | |
41447f92 | 23033 | -break-insert [ -t ] [ -h ] [ -f ] [ -d ] |
922fbb7b | 23034 | [ -c @var{condition} ] [ -i @var{ignore-count} ] |
afe8ab22 | 23035 | [ -p @var{thread} ] [ @var{location} ] |
922fbb7b AC |
23036 | @end smallexample |
23037 | ||
23038 | @noindent | |
afe8ab22 | 23039 | If specified, @var{location}, can be one of: |
922fbb7b AC |
23040 | |
23041 | @itemize @bullet | |
23042 | @item function | |
23043 | @c @item +offset | |
23044 | @c @item -offset | |
23045 | @c @item linenum | |
23046 | @item filename:linenum | |
23047 | @item filename:function | |
23048 | @item *address | |
23049 | @end itemize | |
23050 | ||
23051 | The possible optional parameters of this command are: | |
23052 | ||
23053 | @table @samp | |
23054 | @item -t | |
948d5102 | 23055 | Insert a temporary breakpoint. |
922fbb7b AC |
23056 | @item -h |
23057 | Insert a hardware breakpoint. | |
23058 | @item -c @var{condition} | |
23059 | Make the breakpoint conditional on @var{condition}. | |
23060 | @item -i @var{ignore-count} | |
23061 | Initialize the @var{ignore-count}. | |
afe8ab22 VP |
23062 | @item -f |
23063 | If @var{location} cannot be parsed (for example if it | |
23064 | refers to unknown files or functions), create a pending | |
23065 | breakpoint. Without this flag, @value{GDBN} will report | |
23066 | an error, and won't create a breakpoint, if @var{location} | |
23067 | cannot be parsed. | |
41447f92 VP |
23068 | @item -d |
23069 | Create a disabled breakpoint. | |
922fbb7b AC |
23070 | @end table |
23071 | ||
23072 | @subsubheading Result | |
23073 | ||
23074 | The result is in the form: | |
23075 | ||
23076 | @smallexample | |
948d5102 NR |
23077 | ^done,bkpt=@{number="@var{number}",type="@var{type}",disp="del"|"keep", |
23078 | enabled="y"|"n",addr="@var{hex}",func="@var{funcname}",file="@var{filename}", | |
ef21caaf NR |
23079 | fullname="@var{full_filename}",line="@var{lineno}",[thread="@var{threadno},] |
23080 | times="@var{times}"@} | |
922fbb7b AC |
23081 | @end smallexample |
23082 | ||
23083 | @noindent | |
948d5102 NR |
23084 | where @var{number} is the @value{GDBN} number for this breakpoint, |
23085 | @var{funcname} is the name of the function where the breakpoint was | |
23086 | inserted, @var{filename} is the name of the source file which contains | |
23087 | this function, @var{lineno} is the source line number within that file | |
23088 | and @var{times} the number of times that the breakpoint has been hit | |
23089 | (always 0 for -break-insert but may be greater for -break-info or -break-list | |
23090 | which use the same output). | |
922fbb7b AC |
23091 | |
23092 | Note: this format is open to change. | |
23093 | @c An out-of-band breakpoint instead of part of the result? | |
23094 | ||
23095 | @subsubheading @value{GDBN} Command | |
23096 | ||
23097 | The corresponding @value{GDBN} commands are @samp{break}, @samp{tbreak}, | |
23098 | @samp{hbreak}, @samp{thbreak}, and @samp{rbreak}. | |
23099 | ||
23100 | @subsubheading Example | |
23101 | ||
23102 | @smallexample | |
594fe323 | 23103 | (gdb) |
922fbb7b | 23104 | -break-insert main |
948d5102 NR |
23105 | ^done,bkpt=@{number="1",addr="0x0001072c",file="recursive2.c", |
23106 | fullname="/home/foo/recursive2.c,line="4",times="0"@} | |
594fe323 | 23107 | (gdb) |
922fbb7b | 23108 | -break-insert -t foo |
948d5102 NR |
23109 | ^done,bkpt=@{number="2",addr="0x00010774",file="recursive2.c", |
23110 | fullname="/home/foo/recursive2.c,line="11",times="0"@} | |
594fe323 | 23111 | (gdb) |
922fbb7b AC |
23112 | -break-list |
23113 | ^done,BreakpointTable=@{nr_rows="2",nr_cols="6", | |
23114 | hdr=[@{width="3",alignment="-1",col_name="number",colhdr="Num"@}, | |
23115 | @{width="14",alignment="-1",col_name="type",colhdr="Type"@}, | |
23116 | @{width="4",alignment="-1",col_name="disp",colhdr="Disp"@}, | |
23117 | @{width="3",alignment="-1",col_name="enabled",colhdr="Enb"@}, | |
23118 | @{width="10",alignment="-1",col_name="addr",colhdr="Address"@}, | |
23119 | @{width="40",alignment="2",col_name="what",colhdr="What"@}], | |
23120 | body=[bkpt=@{number="1",type="breakpoint",disp="keep",enabled="y", | |
948d5102 NR |
23121 | addr="0x0001072c", func="main",file="recursive2.c", |
23122 | fullname="/home/foo/recursive2.c,"line="4",times="0"@}, | |
922fbb7b | 23123 | bkpt=@{number="2",type="breakpoint",disp="del",enabled="y", |
948d5102 NR |
23124 | addr="0x00010774",func="foo",file="recursive2.c", |
23125 | fullname="/home/foo/recursive2.c",line="11",times="0"@}]@} | |
594fe323 | 23126 | (gdb) |
922fbb7b AC |
23127 | -break-insert -r foo.* |
23128 | ~int foo(int, int); | |
948d5102 NR |
23129 | ^done,bkpt=@{number="3",addr="0x00010774",file="recursive2.c, |
23130 | "fullname="/home/foo/recursive2.c",line="11",times="0"@} | |
594fe323 | 23131 | (gdb) |
922fbb7b AC |
23132 | @end smallexample |
23133 | ||
23134 | @subheading The @code{-break-list} Command | |
23135 | @findex -break-list | |
23136 | ||
23137 | @subsubheading Synopsis | |
23138 | ||
23139 | @smallexample | |
23140 | -break-list | |
23141 | @end smallexample | |
23142 | ||
23143 | Displays the list of inserted breakpoints, showing the following fields: | |
23144 | ||
23145 | @table @samp | |
23146 | @item Number | |
23147 | number of the breakpoint | |
23148 | @item Type | |
23149 | type of the breakpoint: @samp{breakpoint} or @samp{watchpoint} | |
23150 | @item Disposition | |
23151 | should the breakpoint be deleted or disabled when it is hit: @samp{keep} | |
23152 | or @samp{nokeep} | |
23153 | @item Enabled | |
23154 | is the breakpoint enabled or no: @samp{y} or @samp{n} | |
23155 | @item Address | |
23156 | memory location at which the breakpoint is set | |
23157 | @item What | |
23158 | logical location of the breakpoint, expressed by function name, file | |
23159 | name, line number | |
23160 | @item Times | |
23161 | number of times the breakpoint has been hit | |
23162 | @end table | |
23163 | ||
23164 | If there are no breakpoints or watchpoints, the @code{BreakpointTable} | |
23165 | @code{body} field is an empty list. | |
23166 | ||
23167 | @subsubheading @value{GDBN} Command | |
23168 | ||
23169 | The corresponding @value{GDBN} command is @samp{info break}. | |
23170 | ||
23171 | @subsubheading Example | |
23172 | ||
23173 | @smallexample | |
594fe323 | 23174 | (gdb) |
922fbb7b AC |
23175 | -break-list |
23176 | ^done,BreakpointTable=@{nr_rows="2",nr_cols="6", | |
23177 | hdr=[@{width="3",alignment="-1",col_name="number",colhdr="Num"@}, | |
23178 | @{width="14",alignment="-1",col_name="type",colhdr="Type"@}, | |
23179 | @{width="4",alignment="-1",col_name="disp",colhdr="Disp"@}, | |
23180 | @{width="3",alignment="-1",col_name="enabled",colhdr="Enb"@}, | |
23181 | @{width="10",alignment="-1",col_name="addr",colhdr="Address"@}, | |
23182 | @{width="40",alignment="2",col_name="what",colhdr="What"@}], | |
23183 | body=[bkpt=@{number="1",type="breakpoint",disp="keep",enabled="y", | |
23184 | addr="0x000100d0",func="main",file="hello.c",line="5",times="0"@}, | |
23185 | bkpt=@{number="2",type="breakpoint",disp="keep",enabled="y", | |
948d5102 NR |
23186 | addr="0x00010114",func="foo",file="hello.c",fullname="/home/foo/hello.c", |
23187 | line="13",times="0"@}]@} | |
594fe323 | 23188 | (gdb) |
922fbb7b AC |
23189 | @end smallexample |
23190 | ||
23191 | Here's an example of the result when there are no breakpoints: | |
23192 | ||
23193 | @smallexample | |
594fe323 | 23194 | (gdb) |
922fbb7b AC |
23195 | -break-list |
23196 | ^done,BreakpointTable=@{nr_rows="0",nr_cols="6", | |
23197 | hdr=[@{width="3",alignment="-1",col_name="number",colhdr="Num"@}, | |
23198 | @{width="14",alignment="-1",col_name="type",colhdr="Type"@}, | |
23199 | @{width="4",alignment="-1",col_name="disp",colhdr="Disp"@}, | |
23200 | @{width="3",alignment="-1",col_name="enabled",colhdr="Enb"@}, | |
23201 | @{width="10",alignment="-1",col_name="addr",colhdr="Address"@}, | |
23202 | @{width="40",alignment="2",col_name="what",colhdr="What"@}], | |
23203 | body=[]@} | |
594fe323 | 23204 | (gdb) |
922fbb7b AC |
23205 | @end smallexample |
23206 | ||
23207 | @subheading The @code{-break-watch} Command | |
23208 | @findex -break-watch | |
23209 | ||
23210 | @subsubheading Synopsis | |
23211 | ||
23212 | @smallexample | |
23213 | -break-watch [ -a | -r ] | |
23214 | @end smallexample | |
23215 | ||
23216 | Create a watchpoint. With the @samp{-a} option it will create an | |
d3e8051b | 23217 | @dfn{access} watchpoint, i.e., a watchpoint that triggers either on a |
922fbb7b | 23218 | read from or on a write to the memory location. With the @samp{-r} |
d3e8051b | 23219 | option, the watchpoint created is a @dfn{read} watchpoint, i.e., it will |
922fbb7b AC |
23220 | trigger only when the memory location is accessed for reading. Without |
23221 | either of the options, the watchpoint created is a regular watchpoint, | |
d3e8051b | 23222 | i.e., it will trigger when the memory location is accessed for writing. |
79a6e687 | 23223 | @xref{Set Watchpoints, , Setting Watchpoints}. |
922fbb7b AC |
23224 | |
23225 | Note that @samp{-break-list} will report a single list of watchpoints and | |
23226 | breakpoints inserted. | |
23227 | ||
23228 | @subsubheading @value{GDBN} Command | |
23229 | ||
23230 | The corresponding @value{GDBN} commands are @samp{watch}, @samp{awatch}, and | |
23231 | @samp{rwatch}. | |
23232 | ||
23233 | @subsubheading Example | |
23234 | ||
23235 | Setting a watchpoint on a variable in the @code{main} function: | |
23236 | ||
23237 | @smallexample | |
594fe323 | 23238 | (gdb) |
922fbb7b AC |
23239 | -break-watch x |
23240 | ^done,wpt=@{number="2",exp="x"@} | |
594fe323 | 23241 | (gdb) |
922fbb7b AC |
23242 | -exec-continue |
23243 | ^running | |
0869d01b NR |
23244 | (gdb) |
23245 | *stopped,reason="watchpoint-trigger",wpt=@{number="2",exp="x"@}, | |
922fbb7b | 23246 | value=@{old="-268439212",new="55"@}, |
76ff342d | 23247 | frame=@{func="main",args=[],file="recursive2.c", |
948d5102 | 23248 | fullname="/home/foo/bar/recursive2.c",line="5"@} |
594fe323 | 23249 | (gdb) |
922fbb7b AC |
23250 | @end smallexample |
23251 | ||
23252 | Setting a watchpoint on a variable local to a function. @value{GDBN} will stop | |
23253 | the program execution twice: first for the variable changing value, then | |
23254 | for the watchpoint going out of scope. | |
23255 | ||
23256 | @smallexample | |
594fe323 | 23257 | (gdb) |
922fbb7b AC |
23258 | -break-watch C |
23259 | ^done,wpt=@{number="5",exp="C"@} | |
594fe323 | 23260 | (gdb) |
922fbb7b AC |
23261 | -exec-continue |
23262 | ^running | |
0869d01b NR |
23263 | (gdb) |
23264 | *stopped,reason="watchpoint-trigger", | |
922fbb7b AC |
23265 | wpt=@{number="5",exp="C"@},value=@{old="-276895068",new="3"@}, |
23266 | frame=@{func="callee4",args=[], | |
76ff342d DJ |
23267 | file="../../../devo/gdb/testsuite/gdb.mi/basics.c", |
23268 | fullname="/home/foo/bar/devo/gdb/testsuite/gdb.mi/basics.c",line="13"@} | |
594fe323 | 23269 | (gdb) |
922fbb7b AC |
23270 | -exec-continue |
23271 | ^running | |
0869d01b NR |
23272 | (gdb) |
23273 | *stopped,reason="watchpoint-scope",wpnum="5", | |
922fbb7b AC |
23274 | frame=@{func="callee3",args=[@{name="strarg", |
23275 | value="0x11940 \"A string argument.\""@}], | |
76ff342d DJ |
23276 | file="../../../devo/gdb/testsuite/gdb.mi/basics.c", |
23277 | fullname="/home/foo/bar/devo/gdb/testsuite/gdb.mi/basics.c",line="18"@} | |
594fe323 | 23278 | (gdb) |
922fbb7b AC |
23279 | @end smallexample |
23280 | ||
23281 | Listing breakpoints and watchpoints, at different points in the program | |
23282 | execution. Note that once the watchpoint goes out of scope, it is | |
23283 | deleted. | |
23284 | ||
23285 | @smallexample | |
594fe323 | 23286 | (gdb) |
922fbb7b AC |
23287 | -break-watch C |
23288 | ^done,wpt=@{number="2",exp="C"@} | |
594fe323 | 23289 | (gdb) |
922fbb7b AC |
23290 | -break-list |
23291 | ^done,BreakpointTable=@{nr_rows="2",nr_cols="6", | |
23292 | hdr=[@{width="3",alignment="-1",col_name="number",colhdr="Num"@}, | |
23293 | @{width="14",alignment="-1",col_name="type",colhdr="Type"@}, | |
23294 | @{width="4",alignment="-1",col_name="disp",colhdr="Disp"@}, | |
23295 | @{width="3",alignment="-1",col_name="enabled",colhdr="Enb"@}, | |
23296 | @{width="10",alignment="-1",col_name="addr",colhdr="Address"@}, | |
23297 | @{width="40",alignment="2",col_name="what",colhdr="What"@}], | |
23298 | body=[bkpt=@{number="1",type="breakpoint",disp="keep",enabled="y", | |
23299 | addr="0x00010734",func="callee4", | |
948d5102 NR |
23300 | file="../../../devo/gdb/testsuite/gdb.mi/basics.c", |
23301 | fullname="/home/foo/devo/gdb/testsuite/gdb.mi/basics.c"line="8",times="1"@}, | |
922fbb7b AC |
23302 | bkpt=@{number="2",type="watchpoint",disp="keep", |
23303 | enabled="y",addr="",what="C",times="0"@}]@} | |
594fe323 | 23304 | (gdb) |
922fbb7b AC |
23305 | -exec-continue |
23306 | ^running | |
0869d01b NR |
23307 | (gdb) |
23308 | *stopped,reason="watchpoint-trigger",wpt=@{number="2",exp="C"@}, | |
922fbb7b AC |
23309 | value=@{old="-276895068",new="3"@}, |
23310 | frame=@{func="callee4",args=[], | |
76ff342d DJ |
23311 | file="../../../devo/gdb/testsuite/gdb.mi/basics.c", |
23312 | fullname="/home/foo/bar/devo/gdb/testsuite/gdb.mi/basics.c",line="13"@} | |
594fe323 | 23313 | (gdb) |
922fbb7b AC |
23314 | -break-list |
23315 | ^done,BreakpointTable=@{nr_rows="2",nr_cols="6", | |
23316 | hdr=[@{width="3",alignment="-1",col_name="number",colhdr="Num"@}, | |
23317 | @{width="14",alignment="-1",col_name="type",colhdr="Type"@}, | |
23318 | @{width="4",alignment="-1",col_name="disp",colhdr="Disp"@}, | |
23319 | @{width="3",alignment="-1",col_name="enabled",colhdr="Enb"@}, | |
23320 | @{width="10",alignment="-1",col_name="addr",colhdr="Address"@}, | |
23321 | @{width="40",alignment="2",col_name="what",colhdr="What"@}], | |
23322 | body=[bkpt=@{number="1",type="breakpoint",disp="keep",enabled="y", | |
23323 | addr="0x00010734",func="callee4", | |
948d5102 NR |
23324 | file="../../../devo/gdb/testsuite/gdb.mi/basics.c", |
23325 | fullname="/home/foo/devo/gdb/testsuite/gdb.mi/basics.c",line="8",times="1"@}, | |
922fbb7b AC |
23326 | bkpt=@{number="2",type="watchpoint",disp="keep", |
23327 | enabled="y",addr="",what="C",times="-5"@}]@} | |
594fe323 | 23328 | (gdb) |
922fbb7b AC |
23329 | -exec-continue |
23330 | ^running | |
23331 | ^done,reason="watchpoint-scope",wpnum="2", | |
23332 | frame=@{func="callee3",args=[@{name="strarg", | |
23333 | value="0x11940 \"A string argument.\""@}], | |
76ff342d DJ |
23334 | file="../../../devo/gdb/testsuite/gdb.mi/basics.c", |
23335 | fullname="/home/foo/bar/devo/gdb/testsuite/gdb.mi/basics.c",line="18"@} | |
594fe323 | 23336 | (gdb) |
922fbb7b AC |
23337 | -break-list |
23338 | ^done,BreakpointTable=@{nr_rows="1",nr_cols="6", | |
23339 | hdr=[@{width="3",alignment="-1",col_name="number",colhdr="Num"@}, | |
23340 | @{width="14",alignment="-1",col_name="type",colhdr="Type"@}, | |
23341 | @{width="4",alignment="-1",col_name="disp",colhdr="Disp"@}, | |
23342 | @{width="3",alignment="-1",col_name="enabled",colhdr="Enb"@}, | |
23343 | @{width="10",alignment="-1",col_name="addr",colhdr="Address"@}, | |
23344 | @{width="40",alignment="2",col_name="what",colhdr="What"@}], | |
23345 | body=[bkpt=@{number="1",type="breakpoint",disp="keep",enabled="y", | |
23346 | addr="0x00010734",func="callee4", | |
948d5102 NR |
23347 | file="../../../devo/gdb/testsuite/gdb.mi/basics.c", |
23348 | fullname="/home/foo/devo/gdb/testsuite/gdb.mi/basics.c",line="8", | |
23349 | times="1"@}]@} | |
594fe323 | 23350 | (gdb) |
922fbb7b AC |
23351 | @end smallexample |
23352 | ||
23353 | @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% | |
a2c02241 NR |
23354 | @node GDB/MI Program Context |
23355 | @section @sc{gdb/mi} Program Context | |
922fbb7b | 23356 | |
a2c02241 NR |
23357 | @subheading The @code{-exec-arguments} Command |
23358 | @findex -exec-arguments | |
922fbb7b | 23359 | |
922fbb7b AC |
23360 | |
23361 | @subsubheading Synopsis | |
23362 | ||
23363 | @smallexample | |
a2c02241 | 23364 | -exec-arguments @var{args} |
922fbb7b AC |
23365 | @end smallexample |
23366 | ||
a2c02241 NR |
23367 | Set the inferior program arguments, to be used in the next |
23368 | @samp{-exec-run}. | |
922fbb7b | 23369 | |
a2c02241 | 23370 | @subsubheading @value{GDBN} Command |
922fbb7b | 23371 | |
a2c02241 | 23372 | The corresponding @value{GDBN} command is @samp{set args}. |
922fbb7b | 23373 | |
a2c02241 | 23374 | @subsubheading Example |
922fbb7b | 23375 | |
fbc5282e MK |
23376 | @smallexample |
23377 | (gdb) | |
23378 | -exec-arguments -v word | |
23379 | ^done | |
23380 | (gdb) | |
23381 | @end smallexample | |
922fbb7b | 23382 | |
a2c02241 | 23383 | |
9901a55b | 23384 | @ignore |
a2c02241 NR |
23385 | @subheading The @code{-exec-show-arguments} Command |
23386 | @findex -exec-show-arguments | |
23387 | ||
23388 | @subsubheading Synopsis | |
23389 | ||
23390 | @smallexample | |
23391 | -exec-show-arguments | |
23392 | @end smallexample | |
23393 | ||
23394 | Print the arguments of the program. | |
922fbb7b AC |
23395 | |
23396 | @subsubheading @value{GDBN} Command | |
23397 | ||
a2c02241 | 23398 | The corresponding @value{GDBN} command is @samp{show args}. |
922fbb7b AC |
23399 | |
23400 | @subsubheading Example | |
a2c02241 | 23401 | N.A. |
9901a55b | 23402 | @end ignore |
922fbb7b | 23403 | |
922fbb7b | 23404 | |
a2c02241 NR |
23405 | @subheading The @code{-environment-cd} Command |
23406 | @findex -environment-cd | |
922fbb7b | 23407 | |
a2c02241 | 23408 | @subsubheading Synopsis |
922fbb7b AC |
23409 | |
23410 | @smallexample | |
a2c02241 | 23411 | -environment-cd @var{pathdir} |
922fbb7b AC |
23412 | @end smallexample |
23413 | ||
a2c02241 | 23414 | Set @value{GDBN}'s working directory. |
922fbb7b | 23415 | |
a2c02241 | 23416 | @subsubheading @value{GDBN} Command |
922fbb7b | 23417 | |
a2c02241 NR |
23418 | The corresponding @value{GDBN} command is @samp{cd}. |
23419 | ||
23420 | @subsubheading Example | |
922fbb7b AC |
23421 | |
23422 | @smallexample | |
594fe323 | 23423 | (gdb) |
a2c02241 NR |
23424 | -environment-cd /kwikemart/marge/ezannoni/flathead-dev/devo/gdb |
23425 | ^done | |
594fe323 | 23426 | (gdb) |
922fbb7b AC |
23427 | @end smallexample |
23428 | ||
23429 | ||
a2c02241 NR |
23430 | @subheading The @code{-environment-directory} Command |
23431 | @findex -environment-directory | |
922fbb7b AC |
23432 | |
23433 | @subsubheading Synopsis | |
23434 | ||
23435 | @smallexample | |
a2c02241 | 23436 | -environment-directory [ -r ] [ @var{pathdir} ]+ |
922fbb7b AC |
23437 | @end smallexample |
23438 | ||
a2c02241 NR |
23439 | Add directories @var{pathdir} to beginning of search path for source files. |
23440 | If the @samp{-r} option is used, the search path is reset to the default | |
23441 | search path. If directories @var{pathdir} are supplied in addition to the | |
23442 | @samp{-r} option, the search path is first reset and then addition | |
23443 | occurs as normal. | |
23444 | Multiple directories may be specified, separated by blanks. Specifying | |
23445 | multiple directories in a single command | |
23446 | results in the directories added to the beginning of the | |
23447 | search path in the same order they were presented in the command. | |
23448 | If blanks are needed as | |
23449 | part of a directory name, double-quotes should be used around | |
23450 | the name. In the command output, the path will show up separated | |
d3e8051b | 23451 | by the system directory-separator character. The directory-separator |
a2c02241 NR |
23452 | character must not be used |
23453 | in any directory name. | |
23454 | If no directories are specified, the current search path is displayed. | |
922fbb7b AC |
23455 | |
23456 | @subsubheading @value{GDBN} Command | |
23457 | ||
a2c02241 | 23458 | The corresponding @value{GDBN} command is @samp{dir}. |
922fbb7b AC |
23459 | |
23460 | @subsubheading Example | |
23461 | ||
922fbb7b | 23462 | @smallexample |
594fe323 | 23463 | (gdb) |
a2c02241 NR |
23464 | -environment-directory /kwikemart/marge/ezannoni/flathead-dev/devo/gdb |
23465 | ^done,source-path="/kwikemart/marge/ezannoni/flathead-dev/devo/gdb:$cdir:$cwd" | |
594fe323 | 23466 | (gdb) |
a2c02241 NR |
23467 | -environment-directory "" |
23468 | ^done,source-path="/kwikemart/marge/ezannoni/flathead-dev/devo/gdb:$cdir:$cwd" | |
594fe323 | 23469 | (gdb) |
a2c02241 NR |
23470 | -environment-directory -r /home/jjohnstn/src/gdb /usr/src |
23471 | ^done,source-path="/home/jjohnstn/src/gdb:/usr/src:$cdir:$cwd" | |
594fe323 | 23472 | (gdb) |
a2c02241 NR |
23473 | -environment-directory -r |
23474 | ^done,source-path="$cdir:$cwd" | |
594fe323 | 23475 | (gdb) |
922fbb7b AC |
23476 | @end smallexample |
23477 | ||
23478 | ||
a2c02241 NR |
23479 | @subheading The @code{-environment-path} Command |
23480 | @findex -environment-path | |
922fbb7b AC |
23481 | |
23482 | @subsubheading Synopsis | |
23483 | ||
23484 | @smallexample | |
a2c02241 | 23485 | -environment-path [ -r ] [ @var{pathdir} ]+ |
922fbb7b AC |
23486 | @end smallexample |
23487 | ||
a2c02241 NR |
23488 | Add directories @var{pathdir} to beginning of search path for object files. |
23489 | If the @samp{-r} option is used, the search path is reset to the original | |
23490 | search path that existed at gdb start-up. If directories @var{pathdir} are | |
23491 | supplied in addition to the | |
23492 | @samp{-r} option, the search path is first reset and then addition | |
23493 | occurs as normal. | |
23494 | Multiple directories may be specified, separated by blanks. Specifying | |
23495 | multiple directories in a single command | |
23496 | results in the directories added to the beginning of the | |
23497 | search path in the same order they were presented in the command. | |
23498 | If blanks are needed as | |
23499 | part of a directory name, double-quotes should be used around | |
23500 | the name. In the command output, the path will show up separated | |
d3e8051b | 23501 | by the system directory-separator character. The directory-separator |
a2c02241 NR |
23502 | character must not be used |
23503 | in any directory name. | |
23504 | If no directories are specified, the current path is displayed. | |
23505 | ||
922fbb7b AC |
23506 | |
23507 | @subsubheading @value{GDBN} Command | |
23508 | ||
a2c02241 | 23509 | The corresponding @value{GDBN} command is @samp{path}. |
922fbb7b AC |
23510 | |
23511 | @subsubheading Example | |
23512 | ||
922fbb7b | 23513 | @smallexample |
594fe323 | 23514 | (gdb) |
a2c02241 NR |
23515 | -environment-path |
23516 | ^done,path="/usr/bin" | |
594fe323 | 23517 | (gdb) |
a2c02241 NR |
23518 | -environment-path /kwikemart/marge/ezannoni/flathead-dev/ppc-eabi/gdb /bin |
23519 | ^done,path="/kwikemart/marge/ezannoni/flathead-dev/ppc-eabi/gdb:/bin:/usr/bin" | |
594fe323 | 23520 | (gdb) |
a2c02241 NR |
23521 | -environment-path -r /usr/local/bin |
23522 | ^done,path="/usr/local/bin:/usr/bin" | |
594fe323 | 23523 | (gdb) |
922fbb7b AC |
23524 | @end smallexample |
23525 | ||
23526 | ||
a2c02241 NR |
23527 | @subheading The @code{-environment-pwd} Command |
23528 | @findex -environment-pwd | |
922fbb7b AC |
23529 | |
23530 | @subsubheading Synopsis | |
23531 | ||
23532 | @smallexample | |
a2c02241 | 23533 | -environment-pwd |
922fbb7b AC |
23534 | @end smallexample |
23535 | ||
a2c02241 | 23536 | Show the current working directory. |
922fbb7b | 23537 | |
79a6e687 | 23538 | @subsubheading @value{GDBN} Command |
922fbb7b | 23539 | |
a2c02241 | 23540 | The corresponding @value{GDBN} command is @samp{pwd}. |
922fbb7b AC |
23541 | |
23542 | @subsubheading Example | |
23543 | ||
922fbb7b | 23544 | @smallexample |
594fe323 | 23545 | (gdb) |
a2c02241 NR |
23546 | -environment-pwd |
23547 | ^done,cwd="/kwikemart/marge/ezannoni/flathead-dev/devo/gdb" | |
594fe323 | 23548 | (gdb) |
922fbb7b AC |
23549 | @end smallexample |
23550 | ||
a2c02241 NR |
23551 | @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% |
23552 | @node GDB/MI Thread Commands | |
23553 | @section @sc{gdb/mi} Thread Commands | |
23554 | ||
23555 | ||
23556 | @subheading The @code{-thread-info} Command | |
23557 | @findex -thread-info | |
922fbb7b AC |
23558 | |
23559 | @subsubheading Synopsis | |
23560 | ||
23561 | @smallexample | |
8e8901c5 | 23562 | -thread-info [ @var{thread-id} ] |
922fbb7b AC |
23563 | @end smallexample |
23564 | ||
8e8901c5 VP |
23565 | Reports information about either a specific thread, if |
23566 | the @var{thread-id} parameter is present, or about all | |
23567 | threads. When printing information about all threads, | |
23568 | also reports the current thread. | |
23569 | ||
79a6e687 | 23570 | @subsubheading @value{GDBN} Command |
922fbb7b | 23571 | |
8e8901c5 VP |
23572 | The @samp{info thread} command prints the same information |
23573 | about all threads. | |
922fbb7b AC |
23574 | |
23575 | @subsubheading Example | |
922fbb7b AC |
23576 | |
23577 | @smallexample | |
8e8901c5 VP |
23578 | -thread-info |
23579 | ^done,threads=[ | |
23580 | @{id="2",target-id="Thread 0xb7e14b90 (LWP 21257)", | |
c3b108f7 | 23581 | frame=@{level="0",addr="0xffffe410",func="__kernel_vsyscall",args=[]@},state="running"@}, |
8e8901c5 VP |
23582 | @{id="1",target-id="Thread 0xb7e156b0 (LWP 21254)", |
23583 | frame=@{level="0",addr="0x0804891f",func="foo",args=[@{name="i",value="10"@}], | |
c3b108f7 | 23584 | file="/tmp/a.c",fullname="/tmp/a.c",line="158"@},state="running"@}], |
8e8901c5 VP |
23585 | current-thread-id="1" |
23586 | (gdb) | |
922fbb7b AC |
23587 | @end smallexample |
23588 | ||
c3b108f7 VP |
23589 | The @samp{state} field may have the following values: |
23590 | ||
23591 | @table @code | |
23592 | @item stopped | |
23593 | The thread is stopped. Frame information is available for stopped | |
23594 | threads. | |
23595 | ||
23596 | @item running | |
23597 | The thread is running. There's no frame information for running | |
23598 | threads. | |
23599 | ||
23600 | @end table | |
23601 | ||
a2c02241 NR |
23602 | @subheading The @code{-thread-list-ids} Command |
23603 | @findex -thread-list-ids | |
922fbb7b | 23604 | |
a2c02241 | 23605 | @subsubheading Synopsis |
922fbb7b | 23606 | |
a2c02241 NR |
23607 | @smallexample |
23608 | -thread-list-ids | |
23609 | @end smallexample | |
922fbb7b | 23610 | |
a2c02241 NR |
23611 | Produces a list of the currently known @value{GDBN} thread ids. At the |
23612 | end of the list it also prints the total number of such threads. | |
922fbb7b | 23613 | |
c3b108f7 VP |
23614 | This command is retained for historical reasons, the |
23615 | @code{-thread-info} command should be used instead. | |
23616 | ||
922fbb7b AC |
23617 | @subsubheading @value{GDBN} Command |
23618 | ||
a2c02241 | 23619 | Part of @samp{info threads} supplies the same information. |
922fbb7b AC |
23620 | |
23621 | @subsubheading Example | |
23622 | ||
922fbb7b | 23623 | @smallexample |
594fe323 | 23624 | (gdb) |
a2c02241 NR |
23625 | -thread-list-ids |
23626 | ^done,thread-ids=@{thread-id="3",thread-id="2",thread-id="1"@}, | |
592375cd | 23627 | current-thread-id="1",number-of-threads="3" |
594fe323 | 23628 | (gdb) |
922fbb7b AC |
23629 | @end smallexample |
23630 | ||
a2c02241 NR |
23631 | |
23632 | @subheading The @code{-thread-select} Command | |
23633 | @findex -thread-select | |
922fbb7b AC |
23634 | |
23635 | @subsubheading Synopsis | |
23636 | ||
23637 | @smallexample | |
a2c02241 | 23638 | -thread-select @var{threadnum} |
922fbb7b AC |
23639 | @end smallexample |
23640 | ||
a2c02241 NR |
23641 | Make @var{threadnum} the current thread. It prints the number of the new |
23642 | current thread, and the topmost frame for that thread. | |
922fbb7b | 23643 | |
c3b108f7 VP |
23644 | This command is deprecated in favor of explicitly using the |
23645 | @samp{--thread} option to each command. | |
23646 | ||
922fbb7b AC |
23647 | @subsubheading @value{GDBN} Command |
23648 | ||
a2c02241 | 23649 | The corresponding @value{GDBN} command is @samp{thread}. |
922fbb7b AC |
23650 | |
23651 | @subsubheading Example | |
922fbb7b AC |
23652 | |
23653 | @smallexample | |
594fe323 | 23654 | (gdb) |
a2c02241 NR |
23655 | -exec-next |
23656 | ^running | |
594fe323 | 23657 | (gdb) |
a2c02241 NR |
23658 | *stopped,reason="end-stepping-range",thread-id="2",line="187", |
23659 | file="../../../devo/gdb/testsuite/gdb.threads/linux-dp.c" | |
594fe323 | 23660 | (gdb) |
a2c02241 NR |
23661 | -thread-list-ids |
23662 | ^done, | |
23663 | thread-ids=@{thread-id="3",thread-id="2",thread-id="1"@}, | |
23664 | number-of-threads="3" | |
594fe323 | 23665 | (gdb) |
a2c02241 NR |
23666 | -thread-select 3 |
23667 | ^done,new-thread-id="3", | |
23668 | frame=@{level="0",func="vprintf", | |
23669 | args=[@{name="format",value="0x8048e9c \"%*s%c %d %c\\n\""@}, | |
23670 | @{name="arg",value="0x2"@}],file="vprintf.c",line="31"@} | |
594fe323 | 23671 | (gdb) |
922fbb7b AC |
23672 | @end smallexample |
23673 | ||
a2c02241 NR |
23674 | @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% |
23675 | @node GDB/MI Program Execution | |
23676 | @section @sc{gdb/mi} Program Execution | |
922fbb7b | 23677 | |
ef21caaf | 23678 | These are the asynchronous commands which generate the out-of-band |
3f94c067 | 23679 | record @samp{*stopped}. Currently @value{GDBN} only really executes |
ef21caaf NR |
23680 | asynchronously with remote targets and this interaction is mimicked in |
23681 | other cases. | |
922fbb7b | 23682 | |
922fbb7b AC |
23683 | @subheading The @code{-exec-continue} Command |
23684 | @findex -exec-continue | |
23685 | ||
23686 | @subsubheading Synopsis | |
23687 | ||
23688 | @smallexample | |
540aa8e7 | 23689 | -exec-continue [--reverse] [--all|--thread-group N] |
922fbb7b AC |
23690 | @end smallexample |
23691 | ||
540aa8e7 MS |
23692 | Resumes the execution of the inferior program, which will continue |
23693 | to execute until it reaches a debugger stop event. If the | |
23694 | @samp{--reverse} option is specified, execution resumes in reverse until | |
23695 | it reaches a stop event. Stop events may include | |
23696 | @itemize @bullet | |
23697 | @item | |
23698 | breakpoints or watchpoints | |
23699 | @item | |
23700 | signals or exceptions | |
23701 | @item | |
23702 | the end of the process (or its beginning under @samp{--reverse}) | |
23703 | @item | |
23704 | the end or beginning of a replay log if one is being used. | |
23705 | @end itemize | |
23706 | In all-stop mode (@pxref{All-Stop | |
23707 | Mode}), may resume only one thread, or all threads, depending on the | |
23708 | value of the @samp{scheduler-locking} variable. If @samp{--all} is | |
a79b8f6e | 23709 | specified, all threads (in all inferiors) will be resumed. The @samp{--all} option is |
540aa8e7 MS |
23710 | ignored in all-stop mode. If the @samp{--thread-group} options is |
23711 | specified, then all threads in that thread group are resumed. | |
922fbb7b AC |
23712 | |
23713 | @subsubheading @value{GDBN} Command | |
23714 | ||
23715 | The corresponding @value{GDBN} corresponding is @samp{continue}. | |
23716 | ||
23717 | @subsubheading Example | |
23718 | ||
23719 | @smallexample | |
23720 | -exec-continue | |
23721 | ^running | |
594fe323 | 23722 | (gdb) |
922fbb7b | 23723 | @@Hello world |
a47ec5fe AR |
23724 | *stopped,reason="breakpoint-hit",disp="keep",bkptno="2",frame=@{ |
23725 | func="foo",args=[],file="hello.c",fullname="/home/foo/bar/hello.c", | |
23726 | line="13"@} | |
594fe323 | 23727 | (gdb) |
922fbb7b AC |
23728 | @end smallexample |
23729 | ||
23730 | ||
23731 | @subheading The @code{-exec-finish} Command | |
23732 | @findex -exec-finish | |
23733 | ||
23734 | @subsubheading Synopsis | |
23735 | ||
23736 | @smallexample | |
540aa8e7 | 23737 | -exec-finish [--reverse] |
922fbb7b AC |
23738 | @end smallexample |
23739 | ||
ef21caaf NR |
23740 | Resumes the execution of the inferior program until the current |
23741 | function is exited. Displays the results returned by the function. | |
540aa8e7 MS |
23742 | If the @samp{--reverse} option is specified, resumes the reverse |
23743 | execution of the inferior program until the point where current | |
23744 | function was called. | |
922fbb7b AC |
23745 | |
23746 | @subsubheading @value{GDBN} Command | |
23747 | ||
23748 | The corresponding @value{GDBN} command is @samp{finish}. | |
23749 | ||
23750 | @subsubheading Example | |
23751 | ||
23752 | Function returning @code{void}. | |
23753 | ||
23754 | @smallexample | |
23755 | -exec-finish | |
23756 | ^running | |
594fe323 | 23757 | (gdb) |
922fbb7b AC |
23758 | @@hello from foo |
23759 | *stopped,reason="function-finished",frame=@{func="main",args=[], | |
948d5102 | 23760 | file="hello.c",fullname="/home/foo/bar/hello.c",line="7"@} |
594fe323 | 23761 | (gdb) |
922fbb7b AC |
23762 | @end smallexample |
23763 | ||
23764 | Function returning other than @code{void}. The name of the internal | |
23765 | @value{GDBN} variable storing the result is printed, together with the | |
23766 | value itself. | |
23767 | ||
23768 | @smallexample | |
23769 | -exec-finish | |
23770 | ^running | |
594fe323 | 23771 | (gdb) |
922fbb7b AC |
23772 | *stopped,reason="function-finished",frame=@{addr="0x000107b0",func="foo", |
23773 | args=[@{name="a",value="1"],@{name="b",value="9"@}@}, | |
948d5102 | 23774 | file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@}, |
922fbb7b | 23775 | gdb-result-var="$1",return-value="0" |
594fe323 | 23776 | (gdb) |
922fbb7b AC |
23777 | @end smallexample |
23778 | ||
23779 | ||
23780 | @subheading The @code{-exec-interrupt} Command | |
23781 | @findex -exec-interrupt | |
23782 | ||
23783 | @subsubheading Synopsis | |
23784 | ||
23785 | @smallexample | |
c3b108f7 | 23786 | -exec-interrupt [--all|--thread-group N] |
922fbb7b AC |
23787 | @end smallexample |
23788 | ||
ef21caaf NR |
23789 | Interrupts the background execution of the target. Note how the token |
23790 | associated with the stop message is the one for the execution command | |
23791 | that has been interrupted. The token for the interrupt itself only | |
23792 | appears in the @samp{^done} output. If the user is trying to | |
922fbb7b AC |
23793 | interrupt a non-running program, an error message will be printed. |
23794 | ||
c3b108f7 VP |
23795 | Note that when asynchronous execution is enabled, this command is |
23796 | asynchronous just like other execution commands. That is, first the | |
23797 | @samp{^done} response will be printed, and the target stop will be | |
23798 | reported after that using the @samp{*stopped} notification. | |
23799 | ||
23800 | In non-stop mode, only the context thread is interrupted by default. | |
a79b8f6e VP |
23801 | All threads (in all inferiors) will be interrupted if the |
23802 | @samp{--all} option is specified. If the @samp{--thread-group} | |
23803 | option is specified, all threads in that group will be interrupted. | |
c3b108f7 | 23804 | |
922fbb7b AC |
23805 | @subsubheading @value{GDBN} Command |
23806 | ||
23807 | The corresponding @value{GDBN} command is @samp{interrupt}. | |
23808 | ||
23809 | @subsubheading Example | |
23810 | ||
23811 | @smallexample | |
594fe323 | 23812 | (gdb) |
922fbb7b AC |
23813 | 111-exec-continue |
23814 | 111^running | |
23815 | ||
594fe323 | 23816 | (gdb) |
922fbb7b AC |
23817 | 222-exec-interrupt |
23818 | 222^done | |
594fe323 | 23819 | (gdb) |
922fbb7b | 23820 | 111*stopped,signal-name="SIGINT",signal-meaning="Interrupt", |
76ff342d | 23821 | frame=@{addr="0x00010140",func="foo",args=[],file="try.c", |
948d5102 | 23822 | fullname="/home/foo/bar/try.c",line="13"@} |
594fe323 | 23823 | (gdb) |
922fbb7b | 23824 | |
594fe323 | 23825 | (gdb) |
922fbb7b AC |
23826 | -exec-interrupt |
23827 | ^error,msg="mi_cmd_exec_interrupt: Inferior not executing." | |
594fe323 | 23828 | (gdb) |
922fbb7b AC |
23829 | @end smallexample |
23830 | ||
83eba9b7 VP |
23831 | @subheading The @code{-exec-jump} Command |
23832 | @findex -exec-jump | |
23833 | ||
23834 | @subsubheading Synopsis | |
23835 | ||
23836 | @smallexample | |
23837 | -exec-jump @var{location} | |
23838 | @end smallexample | |
23839 | ||
23840 | Resumes execution of the inferior program at the location specified by | |
23841 | parameter. @xref{Specify Location}, for a description of the | |
23842 | different forms of @var{location}. | |
23843 | ||
23844 | @subsubheading @value{GDBN} Command | |
23845 | ||
23846 | The corresponding @value{GDBN} command is @samp{jump}. | |
23847 | ||
23848 | @subsubheading Example | |
23849 | ||
23850 | @smallexample | |
23851 | -exec-jump foo.c:10 | |
23852 | *running,thread-id="all" | |
23853 | ^running | |
23854 | @end smallexample | |
23855 | ||
922fbb7b AC |
23856 | |
23857 | @subheading The @code{-exec-next} Command | |
23858 | @findex -exec-next | |
23859 | ||
23860 | @subsubheading Synopsis | |
23861 | ||
23862 | @smallexample | |
540aa8e7 | 23863 | -exec-next [--reverse] |
922fbb7b AC |
23864 | @end smallexample |
23865 | ||
ef21caaf NR |
23866 | Resumes execution of the inferior program, stopping when the beginning |
23867 | of the next source line is reached. | |
922fbb7b | 23868 | |
540aa8e7 MS |
23869 | If the @samp{--reverse} option is specified, resumes reverse execution |
23870 | of the inferior program, stopping at the beginning of the previous | |
23871 | source line. If you issue this command on the first line of a | |
23872 | function, it will take you back to the caller of that function, to the | |
23873 | source line where the function was called. | |
23874 | ||
23875 | ||
922fbb7b AC |
23876 | @subsubheading @value{GDBN} Command |
23877 | ||
23878 | The corresponding @value{GDBN} command is @samp{next}. | |
23879 | ||
23880 | @subsubheading Example | |
23881 | ||
23882 | @smallexample | |
23883 | -exec-next | |
23884 | ^running | |
594fe323 | 23885 | (gdb) |
922fbb7b | 23886 | *stopped,reason="end-stepping-range",line="8",file="hello.c" |
594fe323 | 23887 | (gdb) |
922fbb7b AC |
23888 | @end smallexample |
23889 | ||
23890 | ||
23891 | @subheading The @code{-exec-next-instruction} Command | |
23892 | @findex -exec-next-instruction | |
23893 | ||
23894 | @subsubheading Synopsis | |
23895 | ||
23896 | @smallexample | |
540aa8e7 | 23897 | -exec-next-instruction [--reverse] |
922fbb7b AC |
23898 | @end smallexample |
23899 | ||
ef21caaf NR |
23900 | Executes one machine instruction. If the instruction is a function |
23901 | call, continues until the function returns. If the program stops at an | |
23902 | instruction in the middle of a source line, the address will be | |
23903 | printed as well. | |
922fbb7b | 23904 | |
540aa8e7 MS |
23905 | If the @samp{--reverse} option is specified, resumes reverse execution |
23906 | of the inferior program, stopping at the previous instruction. If the | |
23907 | previously executed instruction was a return from another function, | |
23908 | it will continue to execute in reverse until the call to that function | |
23909 | (from the current stack frame) is reached. | |
23910 | ||
922fbb7b AC |
23911 | @subsubheading @value{GDBN} Command |
23912 | ||
23913 | The corresponding @value{GDBN} command is @samp{nexti}. | |
23914 | ||
23915 | @subsubheading Example | |
23916 | ||
23917 | @smallexample | |
594fe323 | 23918 | (gdb) |
922fbb7b AC |
23919 | -exec-next-instruction |
23920 | ^running | |
23921 | ||
594fe323 | 23922 | (gdb) |
922fbb7b AC |
23923 | *stopped,reason="end-stepping-range", |
23924 | addr="0x000100d4",line="5",file="hello.c" | |
594fe323 | 23925 | (gdb) |
922fbb7b AC |
23926 | @end smallexample |
23927 | ||
23928 | ||
23929 | @subheading The @code{-exec-return} Command | |
23930 | @findex -exec-return | |
23931 | ||
23932 | @subsubheading Synopsis | |
23933 | ||
23934 | @smallexample | |
23935 | -exec-return | |
23936 | @end smallexample | |
23937 | ||
23938 | Makes current function return immediately. Doesn't execute the inferior. | |
23939 | Displays the new current frame. | |
23940 | ||
23941 | @subsubheading @value{GDBN} Command | |
23942 | ||
23943 | The corresponding @value{GDBN} command is @samp{return}. | |
23944 | ||
23945 | @subsubheading Example | |
23946 | ||
23947 | @smallexample | |
594fe323 | 23948 | (gdb) |
922fbb7b AC |
23949 | 200-break-insert callee4 |
23950 | 200^done,bkpt=@{number="1",addr="0x00010734", | |
23951 | file="../../../devo/gdb/testsuite/gdb.mi/basics.c",line="8"@} | |
594fe323 | 23952 | (gdb) |
922fbb7b AC |
23953 | 000-exec-run |
23954 | 000^running | |
594fe323 | 23955 | (gdb) |
a47ec5fe | 23956 | 000*stopped,reason="breakpoint-hit",disp="keep",bkptno="1", |
922fbb7b | 23957 | frame=@{func="callee4",args=[], |
76ff342d DJ |
23958 | file="../../../devo/gdb/testsuite/gdb.mi/basics.c", |
23959 | fullname="/home/foo/bar/devo/gdb/testsuite/gdb.mi/basics.c",line="8"@} | |
594fe323 | 23960 | (gdb) |
922fbb7b AC |
23961 | 205-break-delete |
23962 | 205^done | |
594fe323 | 23963 | (gdb) |
922fbb7b AC |
23964 | 111-exec-return |
23965 | 111^done,frame=@{level="0",func="callee3", | |
23966 | args=[@{name="strarg", | |
23967 | value="0x11940 \"A string argument.\""@}], | |
76ff342d DJ |
23968 | file="../../../devo/gdb/testsuite/gdb.mi/basics.c", |
23969 | fullname="/home/foo/bar/devo/gdb/testsuite/gdb.mi/basics.c",line="18"@} | |
594fe323 | 23970 | (gdb) |
922fbb7b AC |
23971 | @end smallexample |
23972 | ||
23973 | ||
23974 | @subheading The @code{-exec-run} Command | |
23975 | @findex -exec-run | |
23976 | ||
23977 | @subsubheading Synopsis | |
23978 | ||
23979 | @smallexample | |
a79b8f6e | 23980 | -exec-run [--all | --thread-group N] |
922fbb7b AC |
23981 | @end smallexample |
23982 | ||
ef21caaf NR |
23983 | Starts execution of the inferior from the beginning. The inferior |
23984 | executes until either a breakpoint is encountered or the program | |
23985 | exits. In the latter case the output will include an exit code, if | |
23986 | the program has exited exceptionally. | |
922fbb7b | 23987 | |
a79b8f6e VP |
23988 | When no option is specified, the current inferior is started. If the |
23989 | @samp{--thread-group} option is specified, it should refer to a thread | |
23990 | group of type @samp{process}, and that thread group will be started. | |
23991 | If the @samp{--all} option is specified, then all inferiors will be started. | |
23992 | ||
922fbb7b AC |
23993 | @subsubheading @value{GDBN} Command |
23994 | ||
23995 | The corresponding @value{GDBN} command is @samp{run}. | |
23996 | ||
ef21caaf | 23997 | @subsubheading Examples |
922fbb7b AC |
23998 | |
23999 | @smallexample | |
594fe323 | 24000 | (gdb) |
922fbb7b AC |
24001 | -break-insert main |
24002 | ^done,bkpt=@{number="1",addr="0x0001072c",file="recursive2.c",line="4"@} | |
594fe323 | 24003 | (gdb) |
922fbb7b AC |
24004 | -exec-run |
24005 | ^running | |
594fe323 | 24006 | (gdb) |
a47ec5fe | 24007 | *stopped,reason="breakpoint-hit",disp="keep",bkptno="1", |
76ff342d | 24008 | frame=@{func="main",args=[],file="recursive2.c", |
948d5102 | 24009 | fullname="/home/foo/bar/recursive2.c",line="4"@} |
594fe323 | 24010 | (gdb) |
922fbb7b AC |
24011 | @end smallexample |
24012 | ||
ef21caaf NR |
24013 | @noindent |
24014 | Program exited normally: | |
24015 | ||
24016 | @smallexample | |
594fe323 | 24017 | (gdb) |
ef21caaf NR |
24018 | -exec-run |
24019 | ^running | |
594fe323 | 24020 | (gdb) |
ef21caaf NR |
24021 | x = 55 |
24022 | *stopped,reason="exited-normally" | |
594fe323 | 24023 | (gdb) |
ef21caaf NR |
24024 | @end smallexample |
24025 | ||
24026 | @noindent | |
24027 | Program exited exceptionally: | |
24028 | ||
24029 | @smallexample | |
594fe323 | 24030 | (gdb) |
ef21caaf NR |
24031 | -exec-run |
24032 | ^running | |
594fe323 | 24033 | (gdb) |
ef21caaf NR |
24034 | x = 55 |
24035 | *stopped,reason="exited",exit-code="01" | |
594fe323 | 24036 | (gdb) |
ef21caaf NR |
24037 | @end smallexample |
24038 | ||
24039 | Another way the program can terminate is if it receives a signal such as | |
24040 | @code{SIGINT}. In this case, @sc{gdb/mi} displays this: | |
24041 | ||
24042 | @smallexample | |
594fe323 | 24043 | (gdb) |
ef21caaf NR |
24044 | *stopped,reason="exited-signalled",signal-name="SIGINT", |
24045 | signal-meaning="Interrupt" | |
24046 | @end smallexample | |
24047 | ||
922fbb7b | 24048 | |
a2c02241 NR |
24049 | @c @subheading -exec-signal |
24050 | ||
24051 | ||
24052 | @subheading The @code{-exec-step} Command | |
24053 | @findex -exec-step | |
922fbb7b AC |
24054 | |
24055 | @subsubheading Synopsis | |
24056 | ||
24057 | @smallexample | |
540aa8e7 | 24058 | -exec-step [--reverse] |
922fbb7b AC |
24059 | @end smallexample |
24060 | ||
a2c02241 NR |
24061 | Resumes execution of the inferior program, stopping when the beginning |
24062 | of the next source line is reached, if the next source line is not a | |
24063 | function call. If it is, stop at the first instruction of the called | |
540aa8e7 MS |
24064 | function. If the @samp{--reverse} option is specified, resumes reverse |
24065 | execution of the inferior program, stopping at the beginning of the | |
24066 | previously executed source line. | |
922fbb7b AC |
24067 | |
24068 | @subsubheading @value{GDBN} Command | |
24069 | ||
a2c02241 | 24070 | The corresponding @value{GDBN} command is @samp{step}. |
922fbb7b AC |
24071 | |
24072 | @subsubheading Example | |
24073 | ||
24074 | Stepping into a function: | |
24075 | ||
24076 | @smallexample | |
24077 | -exec-step | |
24078 | ^running | |
594fe323 | 24079 | (gdb) |
922fbb7b AC |
24080 | *stopped,reason="end-stepping-range", |
24081 | frame=@{func="foo",args=[@{name="a",value="10"@}, | |
76ff342d | 24082 | @{name="b",value="0"@}],file="recursive2.c", |
948d5102 | 24083 | fullname="/home/foo/bar/recursive2.c",line="11"@} |
594fe323 | 24084 | (gdb) |
922fbb7b AC |
24085 | @end smallexample |
24086 | ||
24087 | Regular stepping: | |
24088 | ||
24089 | @smallexample | |
24090 | -exec-step | |
24091 | ^running | |
594fe323 | 24092 | (gdb) |
922fbb7b | 24093 | *stopped,reason="end-stepping-range",line="14",file="recursive2.c" |
594fe323 | 24094 | (gdb) |
922fbb7b AC |
24095 | @end smallexample |
24096 | ||
24097 | ||
24098 | @subheading The @code{-exec-step-instruction} Command | |
24099 | @findex -exec-step-instruction | |
24100 | ||
24101 | @subsubheading Synopsis | |
24102 | ||
24103 | @smallexample | |
540aa8e7 | 24104 | -exec-step-instruction [--reverse] |
922fbb7b AC |
24105 | @end smallexample |
24106 | ||
540aa8e7 MS |
24107 | Resumes the inferior which executes one machine instruction. If the |
24108 | @samp{--reverse} option is specified, resumes reverse execution of the | |
24109 | inferior program, stopping at the previously executed instruction. | |
24110 | The output, once @value{GDBN} has stopped, will vary depending on | |
24111 | whether we have stopped in the middle of a source line or not. In the | |
24112 | former case, the address at which the program stopped will be printed | |
24113 | as well. | |
922fbb7b AC |
24114 | |
24115 | @subsubheading @value{GDBN} Command | |
24116 | ||
24117 | The corresponding @value{GDBN} command is @samp{stepi}. | |
24118 | ||
24119 | @subsubheading Example | |
24120 | ||
24121 | @smallexample | |
594fe323 | 24122 | (gdb) |
922fbb7b AC |
24123 | -exec-step-instruction |
24124 | ^running | |
24125 | ||
594fe323 | 24126 | (gdb) |
922fbb7b | 24127 | *stopped,reason="end-stepping-range", |
76ff342d | 24128 | frame=@{func="foo",args=[],file="try.c", |
948d5102 | 24129 | fullname="/home/foo/bar/try.c",line="10"@} |
594fe323 | 24130 | (gdb) |
922fbb7b AC |
24131 | -exec-step-instruction |
24132 | ^running | |
24133 | ||
594fe323 | 24134 | (gdb) |
922fbb7b | 24135 | *stopped,reason="end-stepping-range", |
76ff342d | 24136 | frame=@{addr="0x000100f4",func="foo",args=[],file="try.c", |
948d5102 | 24137 | fullname="/home/foo/bar/try.c",line="10"@} |
594fe323 | 24138 | (gdb) |
922fbb7b AC |
24139 | @end smallexample |
24140 | ||
24141 | ||
24142 | @subheading The @code{-exec-until} Command | |
24143 | @findex -exec-until | |
24144 | ||
24145 | @subsubheading Synopsis | |
24146 | ||
24147 | @smallexample | |
24148 | -exec-until [ @var{location} ] | |
24149 | @end smallexample | |
24150 | ||
ef21caaf NR |
24151 | Executes the inferior until the @var{location} specified in the |
24152 | argument is reached. If there is no argument, the inferior executes | |
24153 | until a source line greater than the current one is reached. The | |
24154 | reason for stopping in this case will be @samp{location-reached}. | |
922fbb7b AC |
24155 | |
24156 | @subsubheading @value{GDBN} Command | |
24157 | ||
24158 | The corresponding @value{GDBN} command is @samp{until}. | |
24159 | ||
24160 | @subsubheading Example | |
24161 | ||
24162 | @smallexample | |
594fe323 | 24163 | (gdb) |
922fbb7b AC |
24164 | -exec-until recursive2.c:6 |
24165 | ^running | |
594fe323 | 24166 | (gdb) |
922fbb7b AC |
24167 | x = 55 |
24168 | *stopped,reason="location-reached",frame=@{func="main",args=[], | |
948d5102 | 24169 | file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="6"@} |
594fe323 | 24170 | (gdb) |
922fbb7b AC |
24171 | @end smallexample |
24172 | ||
24173 | @ignore | |
24174 | @subheading -file-clear | |
24175 | Is this going away???? | |
24176 | @end ignore | |
24177 | ||
351ff01a | 24178 | @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% |
a2c02241 NR |
24179 | @node GDB/MI Stack Manipulation |
24180 | @section @sc{gdb/mi} Stack Manipulation Commands | |
351ff01a | 24181 | |
922fbb7b | 24182 | |
a2c02241 NR |
24183 | @subheading The @code{-stack-info-frame} Command |
24184 | @findex -stack-info-frame | |
922fbb7b AC |
24185 | |
24186 | @subsubheading Synopsis | |
24187 | ||
24188 | @smallexample | |
a2c02241 | 24189 | -stack-info-frame |
922fbb7b AC |
24190 | @end smallexample |
24191 | ||
a2c02241 | 24192 | Get info on the selected frame. |
922fbb7b AC |
24193 | |
24194 | @subsubheading @value{GDBN} Command | |
24195 | ||
a2c02241 NR |
24196 | The corresponding @value{GDBN} command is @samp{info frame} or @samp{frame} |
24197 | (without arguments). | |
922fbb7b AC |
24198 | |
24199 | @subsubheading Example | |
24200 | ||
24201 | @smallexample | |
594fe323 | 24202 | (gdb) |
a2c02241 NR |
24203 | -stack-info-frame |
24204 | ^done,frame=@{level="1",addr="0x0001076c",func="callee3", | |
24205 | file="../../../devo/gdb/testsuite/gdb.mi/basics.c", | |
24206 | fullname="/home/foo/bar/devo/gdb/testsuite/gdb.mi/basics.c",line="17"@} | |
594fe323 | 24207 | (gdb) |
922fbb7b AC |
24208 | @end smallexample |
24209 | ||
a2c02241 NR |
24210 | @subheading The @code{-stack-info-depth} Command |
24211 | @findex -stack-info-depth | |
922fbb7b AC |
24212 | |
24213 | @subsubheading Synopsis | |
24214 | ||
24215 | @smallexample | |
a2c02241 | 24216 | -stack-info-depth [ @var{max-depth} ] |
922fbb7b AC |
24217 | @end smallexample |
24218 | ||
a2c02241 NR |
24219 | Return the depth of the stack. If the integer argument @var{max-depth} |
24220 | is specified, do not count beyond @var{max-depth} frames. | |
922fbb7b AC |
24221 | |
24222 | @subsubheading @value{GDBN} Command | |
24223 | ||
a2c02241 | 24224 | There's no equivalent @value{GDBN} command. |
922fbb7b AC |
24225 | |
24226 | @subsubheading Example | |
24227 | ||
a2c02241 NR |
24228 | For a stack with frame levels 0 through 11: |
24229 | ||
922fbb7b | 24230 | @smallexample |
594fe323 | 24231 | (gdb) |
a2c02241 NR |
24232 | -stack-info-depth |
24233 | ^done,depth="12" | |
594fe323 | 24234 | (gdb) |
a2c02241 NR |
24235 | -stack-info-depth 4 |
24236 | ^done,depth="4" | |
594fe323 | 24237 | (gdb) |
a2c02241 NR |
24238 | -stack-info-depth 12 |
24239 | ^done,depth="12" | |
594fe323 | 24240 | (gdb) |
a2c02241 NR |
24241 | -stack-info-depth 11 |
24242 | ^done,depth="11" | |
594fe323 | 24243 | (gdb) |
a2c02241 NR |
24244 | -stack-info-depth 13 |
24245 | ^done,depth="12" | |
594fe323 | 24246 | (gdb) |
922fbb7b AC |
24247 | @end smallexample |
24248 | ||
a2c02241 NR |
24249 | @subheading The @code{-stack-list-arguments} Command |
24250 | @findex -stack-list-arguments | |
922fbb7b AC |
24251 | |
24252 | @subsubheading Synopsis | |
24253 | ||
24254 | @smallexample | |
3afae151 | 24255 | -stack-list-arguments @var{print-values} |
a2c02241 | 24256 | [ @var{low-frame} @var{high-frame} ] |
922fbb7b AC |
24257 | @end smallexample |
24258 | ||
a2c02241 NR |
24259 | Display a list of the arguments for the frames between @var{low-frame} |
24260 | and @var{high-frame} (inclusive). If @var{low-frame} and | |
2f1acb09 VP |
24261 | @var{high-frame} are not provided, list the arguments for the whole |
24262 | call stack. If the two arguments are equal, show the single frame | |
24263 | at the corresponding level. It is an error if @var{low-frame} is | |
24264 | larger than the actual number of frames. On the other hand, | |
24265 | @var{high-frame} may be larger than the actual number of frames, in | |
24266 | which case only existing frames will be returned. | |
a2c02241 | 24267 | |
3afae151 VP |
24268 | If @var{print-values} is 0 or @code{--no-values}, print only the names of |
24269 | the variables; if it is 1 or @code{--all-values}, print also their | |
24270 | values; and if it is 2 or @code{--simple-values}, print the name, | |
24271 | type and value for simple data types, and the name and type for arrays, | |
24272 | structures and unions. | |
922fbb7b | 24273 | |
b3372f91 VP |
24274 | Use of this command to obtain arguments in a single frame is |
24275 | deprecated in favor of the @samp{-stack-list-variables} command. | |
24276 | ||
922fbb7b AC |
24277 | @subsubheading @value{GDBN} Command |
24278 | ||
a2c02241 NR |
24279 | @value{GDBN} does not have an equivalent command. @code{gdbtk} has a |
24280 | @samp{gdb_get_args} command which partially overlaps with the | |
24281 | functionality of @samp{-stack-list-arguments}. | |
922fbb7b AC |
24282 | |
24283 | @subsubheading Example | |
922fbb7b | 24284 | |
a2c02241 | 24285 | @smallexample |
594fe323 | 24286 | (gdb) |
a2c02241 NR |
24287 | -stack-list-frames |
24288 | ^done, | |
24289 | stack=[ | |
24290 | frame=@{level="0",addr="0x00010734",func="callee4", | |
24291 | file="../../../devo/gdb/testsuite/gdb.mi/basics.c", | |
24292 | fullname="/home/foo/bar/devo/gdb/testsuite/gdb.mi/basics.c",line="8"@}, | |
24293 | frame=@{level="1",addr="0x0001076c",func="callee3", | |
24294 | file="../../../devo/gdb/testsuite/gdb.mi/basics.c", | |
24295 | fullname="/home/foo/bar/devo/gdb/testsuite/gdb.mi/basics.c",line="17"@}, | |
24296 | frame=@{level="2",addr="0x0001078c",func="callee2", | |
24297 | file="../../../devo/gdb/testsuite/gdb.mi/basics.c", | |
24298 | fullname="/home/foo/bar/devo/gdb/testsuite/gdb.mi/basics.c",line="22"@}, | |
24299 | frame=@{level="3",addr="0x000107b4",func="callee1", | |
24300 | file="../../../devo/gdb/testsuite/gdb.mi/basics.c", | |
24301 | fullname="/home/foo/bar/devo/gdb/testsuite/gdb.mi/basics.c",line="27"@}, | |
24302 | frame=@{level="4",addr="0x000107e0",func="main", | |
24303 | file="../../../devo/gdb/testsuite/gdb.mi/basics.c", | |
24304 | fullname="/home/foo/bar/devo/gdb/testsuite/gdb.mi/basics.c",line="32"@}] | |
594fe323 | 24305 | (gdb) |
a2c02241 NR |
24306 | -stack-list-arguments 0 |
24307 | ^done, | |
24308 | stack-args=[ | |
24309 | frame=@{level="0",args=[]@}, | |
24310 | frame=@{level="1",args=[name="strarg"]@}, | |
24311 | frame=@{level="2",args=[name="intarg",name="strarg"]@}, | |
24312 | frame=@{level="3",args=[name="intarg",name="strarg",name="fltarg"]@}, | |
24313 | frame=@{level="4",args=[]@}] | |
594fe323 | 24314 | (gdb) |
a2c02241 NR |
24315 | -stack-list-arguments 1 |
24316 | ^done, | |
24317 | stack-args=[ | |
24318 | frame=@{level="0",args=[]@}, | |
24319 | frame=@{level="1", | |
24320 | args=[@{name="strarg",value="0x11940 \"A string argument.\""@}]@}, | |
24321 | frame=@{level="2",args=[ | |
24322 | @{name="intarg",value="2"@}, | |
24323 | @{name="strarg",value="0x11940 \"A string argument.\""@}]@}, | |
24324 | @{frame=@{level="3",args=[ | |
24325 | @{name="intarg",value="2"@}, | |
24326 | @{name="strarg",value="0x11940 \"A string argument.\""@}, | |
24327 | @{name="fltarg",value="3.5"@}]@}, | |
24328 | frame=@{level="4",args=[]@}] | |
594fe323 | 24329 | (gdb) |
a2c02241 NR |
24330 | -stack-list-arguments 0 2 2 |
24331 | ^done,stack-args=[frame=@{level="2",args=[name="intarg",name="strarg"]@}] | |
594fe323 | 24332 | (gdb) |
a2c02241 NR |
24333 | -stack-list-arguments 1 2 2 |
24334 | ^done,stack-args=[frame=@{level="2", | |
24335 | args=[@{name="intarg",value="2"@}, | |
24336 | @{name="strarg",value="0x11940 \"A string argument.\""@}]@}] | |
594fe323 | 24337 | (gdb) |
a2c02241 NR |
24338 | @end smallexample |
24339 | ||
24340 | @c @subheading -stack-list-exception-handlers | |
922fbb7b | 24341 | |
a2c02241 NR |
24342 | |
24343 | @subheading The @code{-stack-list-frames} Command | |
24344 | @findex -stack-list-frames | |
1abaf70c BR |
24345 | |
24346 | @subsubheading Synopsis | |
24347 | ||
24348 | @smallexample | |
a2c02241 | 24349 | -stack-list-frames [ @var{low-frame} @var{high-frame} ] |
1abaf70c BR |
24350 | @end smallexample |
24351 | ||
a2c02241 NR |
24352 | List the frames currently on the stack. For each frame it displays the |
24353 | following info: | |
24354 | ||
24355 | @table @samp | |
24356 | @item @var{level} | |
d3e8051b | 24357 | The frame number, 0 being the topmost frame, i.e., the innermost function. |
a2c02241 NR |
24358 | @item @var{addr} |
24359 | The @code{$pc} value for that frame. | |
24360 | @item @var{func} | |
24361 | Function name. | |
24362 | @item @var{file} | |
24363 | File name of the source file where the function lives. | |
24364 | @item @var{line} | |
24365 | Line number corresponding to the @code{$pc}. | |
24366 | @end table | |
24367 | ||
24368 | If invoked without arguments, this command prints a backtrace for the | |
24369 | whole stack. If given two integer arguments, it shows the frames whose | |
24370 | levels are between the two arguments (inclusive). If the two arguments | |
2ab1eb7a VP |
24371 | are equal, it shows the single frame at the corresponding level. It is |
24372 | an error if @var{low-frame} is larger than the actual number of | |
a5451f4e | 24373 | frames. On the other hand, @var{high-frame} may be larger than the |
2ab1eb7a | 24374 | actual number of frames, in which case only existing frames will be returned. |
1abaf70c BR |
24375 | |
24376 | @subsubheading @value{GDBN} Command | |
24377 | ||
a2c02241 | 24378 | The corresponding @value{GDBN} commands are @samp{backtrace} and @samp{where}. |
1abaf70c BR |
24379 | |
24380 | @subsubheading Example | |
24381 | ||
a2c02241 NR |
24382 | Full stack backtrace: |
24383 | ||
1abaf70c | 24384 | @smallexample |
594fe323 | 24385 | (gdb) |
a2c02241 NR |
24386 | -stack-list-frames |
24387 | ^done,stack= | |
24388 | [frame=@{level="0",addr="0x0001076c",func="foo", | |
24389 | file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="11"@}, | |
24390 | frame=@{level="1",addr="0x000107a4",func="foo", | |
24391 | file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@}, | |
24392 | frame=@{level="2",addr="0x000107a4",func="foo", | |
24393 | file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@}, | |
24394 | frame=@{level="3",addr="0x000107a4",func="foo", | |
24395 | file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@}, | |
24396 | frame=@{level="4",addr="0x000107a4",func="foo", | |
24397 | file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@}, | |
24398 | frame=@{level="5",addr="0x000107a4",func="foo", | |
24399 | file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@}, | |
24400 | frame=@{level="6",addr="0x000107a4",func="foo", | |
24401 | file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@}, | |
24402 | frame=@{level="7",addr="0x000107a4",func="foo", | |
24403 | file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@}, | |
24404 | frame=@{level="8",addr="0x000107a4",func="foo", | |
24405 | file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@}, | |
24406 | frame=@{level="9",addr="0x000107a4",func="foo", | |
24407 | file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@}, | |
24408 | frame=@{level="10",addr="0x000107a4",func="foo", | |
24409 | file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@}, | |
24410 | frame=@{level="11",addr="0x00010738",func="main", | |
24411 | file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="4"@}] | |
594fe323 | 24412 | (gdb) |
1abaf70c BR |
24413 | @end smallexample |
24414 | ||
a2c02241 | 24415 | Show frames between @var{low_frame} and @var{high_frame}: |
1abaf70c | 24416 | |
a2c02241 | 24417 | @smallexample |
594fe323 | 24418 | (gdb) |
a2c02241 NR |
24419 | -stack-list-frames 3 5 |
24420 | ^done,stack= | |
24421 | [frame=@{level="3",addr="0x000107a4",func="foo", | |
24422 | file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@}, | |
24423 | frame=@{level="4",addr="0x000107a4",func="foo", | |
24424 | file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@}, | |
24425 | frame=@{level="5",addr="0x000107a4",func="foo", | |
24426 | file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@}] | |
594fe323 | 24427 | (gdb) |
a2c02241 | 24428 | @end smallexample |
922fbb7b | 24429 | |
a2c02241 | 24430 | Show a single frame: |
922fbb7b AC |
24431 | |
24432 | @smallexample | |
594fe323 | 24433 | (gdb) |
a2c02241 NR |
24434 | -stack-list-frames 3 3 |
24435 | ^done,stack= | |
24436 | [frame=@{level="3",addr="0x000107a4",func="foo", | |
24437 | file="recursive2.c",fullname="/home/foo/bar/recursive2.c",line="14"@}] | |
594fe323 | 24438 | (gdb) |
922fbb7b AC |
24439 | @end smallexample |
24440 | ||
922fbb7b | 24441 | |
a2c02241 NR |
24442 | @subheading The @code{-stack-list-locals} Command |
24443 | @findex -stack-list-locals | |
57c22c6c | 24444 | |
a2c02241 | 24445 | @subsubheading Synopsis |
922fbb7b AC |
24446 | |
24447 | @smallexample | |
a2c02241 | 24448 | -stack-list-locals @var{print-values} |
922fbb7b AC |
24449 | @end smallexample |
24450 | ||
a2c02241 NR |
24451 | Display the local variable names for the selected frame. If |
24452 | @var{print-values} is 0 or @code{--no-values}, print only the names of | |
24453 | the variables; if it is 1 or @code{--all-values}, print also their | |
24454 | values; and if it is 2 or @code{--simple-values}, print the name, | |
3afae151 | 24455 | type and value for simple data types, and the name and type for arrays, |
a2c02241 NR |
24456 | structures and unions. In this last case, a frontend can immediately |
24457 | display the value of simple data types and create variable objects for | |
d3e8051b | 24458 | other data types when the user wishes to explore their values in |
a2c02241 | 24459 | more detail. |
922fbb7b | 24460 | |
b3372f91 VP |
24461 | This command is deprecated in favor of the |
24462 | @samp{-stack-list-variables} command. | |
24463 | ||
922fbb7b AC |
24464 | @subsubheading @value{GDBN} Command |
24465 | ||
a2c02241 | 24466 | @samp{info locals} in @value{GDBN}, @samp{gdb_get_locals} in @code{gdbtk}. |
922fbb7b AC |
24467 | |
24468 | @subsubheading Example | |
922fbb7b AC |
24469 | |
24470 | @smallexample | |
594fe323 | 24471 | (gdb) |
a2c02241 NR |
24472 | -stack-list-locals 0 |
24473 | ^done,locals=[name="A",name="B",name="C"] | |
594fe323 | 24474 | (gdb) |
a2c02241 NR |
24475 | -stack-list-locals --all-values |
24476 | ^done,locals=[@{name="A",value="1"@},@{name="B",value="2"@}, | |
24477 | @{name="C",value="@{1, 2, 3@}"@}] | |
24478 | -stack-list-locals --simple-values | |
24479 | ^done,locals=[@{name="A",type="int",value="1"@}, | |
24480 | @{name="B",type="int",value="2"@},@{name="C",type="int [3]"@}] | |
594fe323 | 24481 | (gdb) |
922fbb7b AC |
24482 | @end smallexample |
24483 | ||
b3372f91 VP |
24484 | @subheading The @code{-stack-list-variables} Command |
24485 | @findex -stack-list-variables | |
24486 | ||
24487 | @subsubheading Synopsis | |
24488 | ||
24489 | @smallexample | |
24490 | -stack-list-variables @var{print-values} | |
24491 | @end smallexample | |
24492 | ||
24493 | Display the names of local variables and function arguments for the selected frame. If | |
24494 | @var{print-values} is 0 or @code{--no-values}, print only the names of | |
24495 | the variables; if it is 1 or @code{--all-values}, print also their | |
24496 | values; and if it is 2 or @code{--simple-values}, print the name, | |
3afae151 | 24497 | type and value for simple data types, and the name and type for arrays, |
b3372f91 VP |
24498 | structures and unions. |
24499 | ||
24500 | @subsubheading Example | |
24501 | ||
24502 | @smallexample | |
24503 | (gdb) | |
24504 | -stack-list-variables --thread 1 --frame 0 --all-values | |
4f412fd0 | 24505 | ^done,variables=[@{name="x",value="11"@},@{name="s",value="@{a = 1, b = 2@}"@}] |
b3372f91 VP |
24506 | (gdb) |
24507 | @end smallexample | |
24508 | ||
922fbb7b | 24509 | |
a2c02241 NR |
24510 | @subheading The @code{-stack-select-frame} Command |
24511 | @findex -stack-select-frame | |
922fbb7b AC |
24512 | |
24513 | @subsubheading Synopsis | |
24514 | ||
24515 | @smallexample | |
a2c02241 | 24516 | -stack-select-frame @var{framenum} |
922fbb7b AC |
24517 | @end smallexample |
24518 | ||
a2c02241 NR |
24519 | Change the selected frame. Select a different frame @var{framenum} on |
24520 | the stack. | |
922fbb7b | 24521 | |
c3b108f7 VP |
24522 | This command in deprecated in favor of passing the @samp{--frame} |
24523 | option to every command. | |
24524 | ||
922fbb7b AC |
24525 | @subsubheading @value{GDBN} Command |
24526 | ||
a2c02241 NR |
24527 | The corresponding @value{GDBN} commands are @samp{frame}, @samp{up}, |
24528 | @samp{down}, @samp{select-frame}, @samp{up-silent}, and @samp{down-silent}. | |
922fbb7b AC |
24529 | |
24530 | @subsubheading Example | |
24531 | ||
24532 | @smallexample | |
594fe323 | 24533 | (gdb) |
a2c02241 | 24534 | -stack-select-frame 2 |
922fbb7b | 24535 | ^done |
594fe323 | 24536 | (gdb) |
922fbb7b AC |
24537 | @end smallexample |
24538 | ||
24539 | @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% | |
a2c02241 NR |
24540 | @node GDB/MI Variable Objects |
24541 | @section @sc{gdb/mi} Variable Objects | |
922fbb7b | 24542 | |
a1b5960f | 24543 | @ignore |
922fbb7b | 24544 | |
a2c02241 | 24545 | @subheading Motivation for Variable Objects in @sc{gdb/mi} |
922fbb7b | 24546 | |
a2c02241 NR |
24547 | For the implementation of a variable debugger window (locals, watched |
24548 | expressions, etc.), we are proposing the adaptation of the existing code | |
24549 | used by @code{Insight}. | |
922fbb7b | 24550 | |
a2c02241 | 24551 | The two main reasons for that are: |
922fbb7b | 24552 | |
a2c02241 NR |
24553 | @enumerate 1 |
24554 | @item | |
24555 | It has been proven in practice (it is already on its second generation). | |
922fbb7b | 24556 | |
a2c02241 NR |
24557 | @item |
24558 | It will shorten development time (needless to say how important it is | |
24559 | now). | |
24560 | @end enumerate | |
922fbb7b | 24561 | |
a2c02241 NR |
24562 | The original interface was designed to be used by Tcl code, so it was |
24563 | slightly changed so it could be used through @sc{gdb/mi}. This section | |
24564 | describes the @sc{gdb/mi} operations that will be available and gives some | |
24565 | hints about their use. | |
922fbb7b | 24566 | |
a2c02241 NR |
24567 | @emph{Note}: In addition to the set of operations described here, we |
24568 | expect the @sc{gui} implementation of a variable window to require, at | |
24569 | least, the following operations: | |
922fbb7b | 24570 | |
a2c02241 NR |
24571 | @itemize @bullet |
24572 | @item @code{-gdb-show} @code{output-radix} | |
24573 | @item @code{-stack-list-arguments} | |
24574 | @item @code{-stack-list-locals} | |
24575 | @item @code{-stack-select-frame} | |
24576 | @end itemize | |
922fbb7b | 24577 | |
a1b5960f VP |
24578 | @end ignore |
24579 | ||
c8b2f53c | 24580 | @subheading Introduction to Variable Objects |
922fbb7b | 24581 | |
a2c02241 | 24582 | @cindex variable objects in @sc{gdb/mi} |
c8b2f53c VP |
24583 | |
24584 | Variable objects are "object-oriented" MI interface for examining and | |
24585 | changing values of expressions. Unlike some other MI interfaces that | |
24586 | work with expressions, variable objects are specifically designed for | |
24587 | simple and efficient presentation in the frontend. A variable object | |
24588 | is identified by string name. When a variable object is created, the | |
24589 | frontend specifies the expression for that variable object. The | |
24590 | expression can be a simple variable, or it can be an arbitrary complex | |
24591 | expression, and can even involve CPU registers. After creating a | |
24592 | variable object, the frontend can invoke other variable object | |
24593 | operations---for example to obtain or change the value of a variable | |
24594 | object, or to change display format. | |
24595 | ||
24596 | Variable objects have hierarchical tree structure. Any variable object | |
24597 | that corresponds to a composite type, such as structure in C, has | |
24598 | a number of child variable objects, for example corresponding to each | |
24599 | element of a structure. A child variable object can itself have | |
24600 | children, recursively. Recursion ends when we reach | |
25d5ea92 VP |
24601 | leaf variable objects, which always have built-in types. Child variable |
24602 | objects are created only by explicit request, so if a frontend | |
24603 | is not interested in the children of a particular variable object, no | |
24604 | child will be created. | |
c8b2f53c VP |
24605 | |
24606 | For a leaf variable object it is possible to obtain its value as a | |
24607 | string, or set the value from a string. String value can be also | |
24608 | obtained for a non-leaf variable object, but it's generally a string | |
24609 | that only indicates the type of the object, and does not list its | |
24610 | contents. Assignment to a non-leaf variable object is not allowed. | |
24611 | ||
24612 | A frontend does not need to read the values of all variable objects each time | |
24613 | the program stops. Instead, MI provides an update command that lists all | |
24614 | variable objects whose values has changed since the last update | |
24615 | operation. This considerably reduces the amount of data that must | |
25d5ea92 VP |
24616 | be transferred to the frontend. As noted above, children variable |
24617 | objects are created on demand, and only leaf variable objects have a | |
24618 | real value. As result, gdb will read target memory only for leaf | |
24619 | variables that frontend has created. | |
24620 | ||
24621 | The automatic update is not always desirable. For example, a frontend | |
24622 | might want to keep a value of some expression for future reference, | |
24623 | and never update it. For another example, fetching memory is | |
24624 | relatively slow for embedded targets, so a frontend might want | |
24625 | to disable automatic update for the variables that are either not | |
24626 | visible on the screen, or ``closed''. This is possible using so | |
24627 | called ``frozen variable objects''. Such variable objects are never | |
24628 | implicitly updated. | |
922fbb7b | 24629 | |
c3b108f7 VP |
24630 | Variable objects can be either @dfn{fixed} or @dfn{floating}. For the |
24631 | fixed variable object, the expression is parsed when the variable | |
24632 | object is created, including associating identifiers to specific | |
24633 | variables. The meaning of expression never changes. For a floating | |
24634 | variable object the values of variables whose names appear in the | |
24635 | expressions are re-evaluated every time in the context of the current | |
24636 | frame. Consider this example: | |
24637 | ||
24638 | @smallexample | |
24639 | void do_work(...) | |
24640 | @{ | |
24641 | struct work_state state; | |
24642 | ||
24643 | if (...) | |
24644 | do_work(...); | |
24645 | @} | |
24646 | @end smallexample | |
24647 | ||
24648 | If a fixed variable object for the @code{state} variable is created in | |
24649 | this function, and we enter the recursive call, the the variable | |
24650 | object will report the value of @code{state} in the top-level | |
24651 | @code{do_work} invocation. On the other hand, a floating variable | |
24652 | object will report the value of @code{state} in the current frame. | |
24653 | ||
24654 | If an expression specified when creating a fixed variable object | |
24655 | refers to a local variable, the variable object becomes bound to the | |
24656 | thread and frame in which the variable object is created. When such | |
24657 | variable object is updated, @value{GDBN} makes sure that the | |
24658 | thread/frame combination the variable object is bound to still exists, | |
24659 | and re-evaluates the variable object in context of that thread/frame. | |
24660 | ||
a2c02241 NR |
24661 | The following is the complete set of @sc{gdb/mi} operations defined to |
24662 | access this functionality: | |
922fbb7b | 24663 | |
a2c02241 NR |
24664 | @multitable @columnfractions .4 .6 |
24665 | @item @strong{Operation} | |
24666 | @tab @strong{Description} | |
922fbb7b | 24667 | |
0cc7d26f TT |
24668 | @item @code{-enable-pretty-printing} |
24669 | @tab enable Python-based pretty-printing | |
a2c02241 NR |
24670 | @item @code{-var-create} |
24671 | @tab create a variable object | |
24672 | @item @code{-var-delete} | |
22d8a470 | 24673 | @tab delete the variable object and/or its children |
a2c02241 NR |
24674 | @item @code{-var-set-format} |
24675 | @tab set the display format of this variable | |
24676 | @item @code{-var-show-format} | |
24677 | @tab show the display format of this variable | |
24678 | @item @code{-var-info-num-children} | |
24679 | @tab tells how many children this object has | |
24680 | @item @code{-var-list-children} | |
24681 | @tab return a list of the object's children | |
24682 | @item @code{-var-info-type} | |
24683 | @tab show the type of this variable object | |
24684 | @item @code{-var-info-expression} | |
02142340 VP |
24685 | @tab print parent-relative expression that this variable object represents |
24686 | @item @code{-var-info-path-expression} | |
24687 | @tab print full expression that this variable object represents | |
a2c02241 NR |
24688 | @item @code{-var-show-attributes} |
24689 | @tab is this variable editable? does it exist here? | |
24690 | @item @code{-var-evaluate-expression} | |
24691 | @tab get the value of this variable | |
24692 | @item @code{-var-assign} | |
24693 | @tab set the value of this variable | |
24694 | @item @code{-var-update} | |
24695 | @tab update the variable and its children | |
25d5ea92 VP |
24696 | @item @code{-var-set-frozen} |
24697 | @tab set frozeness attribute | |
0cc7d26f TT |
24698 | @item @code{-var-set-update-range} |
24699 | @tab set range of children to display on update | |
a2c02241 | 24700 | @end multitable |
922fbb7b | 24701 | |
a2c02241 NR |
24702 | In the next subsection we describe each operation in detail and suggest |
24703 | how it can be used. | |
922fbb7b | 24704 | |
a2c02241 | 24705 | @subheading Description And Use of Operations on Variable Objects |
922fbb7b | 24706 | |
0cc7d26f TT |
24707 | @subheading The @code{-enable-pretty-printing} Command |
24708 | @findex -enable-pretty-printing | |
24709 | ||
24710 | @smallexample | |
24711 | -enable-pretty-printing | |
24712 | @end smallexample | |
24713 | ||
24714 | @value{GDBN} allows Python-based visualizers to affect the output of the | |
24715 | MI variable object commands. However, because there was no way to | |
24716 | implement this in a fully backward-compatible way, a front end must | |
24717 | request that this functionality be enabled. | |
24718 | ||
24719 | Once enabled, this feature cannot be disabled. | |
24720 | ||
24721 | Note that if Python support has not been compiled into @value{GDBN}, | |
24722 | this command will still succeed (and do nothing). | |
24723 | ||
f43030c4 TT |
24724 | This feature is currently (as of @value{GDBN} 7.0) experimental, and |
24725 | may work differently in future versions of @value{GDBN}. | |
24726 | ||
a2c02241 NR |
24727 | @subheading The @code{-var-create} Command |
24728 | @findex -var-create | |
ef21caaf | 24729 | |
a2c02241 | 24730 | @subsubheading Synopsis |
ef21caaf | 24731 | |
a2c02241 NR |
24732 | @smallexample |
24733 | -var-create @{@var{name} | "-"@} | |
c3b108f7 | 24734 | @{@var{frame-addr} | "*" | "@@"@} @var{expression} |
a2c02241 NR |
24735 | @end smallexample |
24736 | ||
24737 | This operation creates a variable object, which allows the monitoring of | |
24738 | a variable, the result of an expression, a memory cell or a CPU | |
24739 | register. | |
ef21caaf | 24740 | |
a2c02241 NR |
24741 | The @var{name} parameter is the string by which the object can be |
24742 | referenced. It must be unique. If @samp{-} is specified, the varobj | |
24743 | system will generate a string ``varNNNNNN'' automatically. It will be | |
c3b108f7 | 24744 | unique provided that one does not specify @var{name} of that format. |
a2c02241 | 24745 | The command fails if a duplicate name is found. |
ef21caaf | 24746 | |
a2c02241 NR |
24747 | The frame under which the expression should be evaluated can be |
24748 | specified by @var{frame-addr}. A @samp{*} indicates that the current | |
c3b108f7 VP |
24749 | frame should be used. A @samp{@@} indicates that a floating variable |
24750 | object must be created. | |
922fbb7b | 24751 | |
a2c02241 NR |
24752 | @var{expression} is any expression valid on the current language set (must not |
24753 | begin with a @samp{*}), or one of the following: | |
922fbb7b | 24754 | |
a2c02241 NR |
24755 | @itemize @bullet |
24756 | @item | |
24757 | @samp{*@var{addr}}, where @var{addr} is the address of a memory cell | |
922fbb7b | 24758 | |
a2c02241 NR |
24759 | @item |
24760 | @samp{*@var{addr}-@var{addr}} --- a memory address range (TBD) | |
922fbb7b | 24761 | |
a2c02241 NR |
24762 | @item |
24763 | @samp{$@var{regname}} --- a CPU register name | |
24764 | @end itemize | |
922fbb7b | 24765 | |
0cc7d26f TT |
24766 | @cindex dynamic varobj |
24767 | A varobj's contents may be provided by a Python-based pretty-printer. In this | |
24768 | case the varobj is known as a @dfn{dynamic varobj}. Dynamic varobjs | |
24769 | have slightly different semantics in some cases. If the | |
24770 | @code{-enable-pretty-printing} command is not sent, then @value{GDBN} | |
24771 | will never create a dynamic varobj. This ensures backward | |
24772 | compatibility for existing clients. | |
24773 | ||
a2c02241 | 24774 | @subsubheading Result |
922fbb7b | 24775 | |
0cc7d26f TT |
24776 | This operation returns attributes of the newly-created varobj. These |
24777 | are: | |
24778 | ||
24779 | @table @samp | |
24780 | @item name | |
24781 | The name of the varobj. | |
24782 | ||
24783 | @item numchild | |
24784 | The number of children of the varobj. This number is not necessarily | |
24785 | reliable for a dynamic varobj. Instead, you must examine the | |
24786 | @samp{has_more} attribute. | |
24787 | ||
24788 | @item value | |
24789 | The varobj's scalar value. For a varobj whose type is some sort of | |
24790 | aggregate (e.g., a @code{struct}), or for a dynamic varobj, this value | |
24791 | will not be interesting. | |
24792 | ||
24793 | @item type | |
24794 | The varobj's type. This is a string representation of the type, as | |
24795 | would be printed by the @value{GDBN} CLI. | |
24796 | ||
24797 | @item thread-id | |
24798 | If a variable object is bound to a specific thread, then this is the | |
24799 | thread's identifier. | |
24800 | ||
24801 | @item has_more | |
24802 | For a dynamic varobj, this indicates whether there appear to be any | |
24803 | children available. For a non-dynamic varobj, this will be 0. | |
24804 | ||
24805 | @item dynamic | |
24806 | This attribute will be present and have the value @samp{1} if the | |
24807 | varobj is a dynamic varobj. If the varobj is not a dynamic varobj, | |
24808 | then this attribute will not be present. | |
24809 | ||
24810 | @item displayhint | |
24811 | A dynamic varobj can supply a display hint to the front end. The | |
24812 | value comes directly from the Python pretty-printer object's | |
24813 | @code{display_hint} method. @xref{Pretty Printing}. | |
24814 | @end table | |
24815 | ||
24816 | Typical output will look like this: | |
922fbb7b AC |
24817 | |
24818 | @smallexample | |
0cc7d26f TT |
24819 | name="@var{name}",numchild="@var{N}",type="@var{type}",thread-id="@var{M}", |
24820 | has_more="@var{has_more}" | |
dcaaae04 NR |
24821 | @end smallexample |
24822 | ||
a2c02241 NR |
24823 | |
24824 | @subheading The @code{-var-delete} Command | |
24825 | @findex -var-delete | |
922fbb7b AC |
24826 | |
24827 | @subsubheading Synopsis | |
24828 | ||
24829 | @smallexample | |
22d8a470 | 24830 | -var-delete [ -c ] @var{name} |
922fbb7b AC |
24831 | @end smallexample |
24832 | ||
a2c02241 | 24833 | Deletes a previously created variable object and all of its children. |
22d8a470 | 24834 | With the @samp{-c} option, just deletes the children. |
922fbb7b | 24835 | |
a2c02241 | 24836 | Returns an error if the object @var{name} is not found. |
922fbb7b | 24837 | |
922fbb7b | 24838 | |
a2c02241 NR |
24839 | @subheading The @code{-var-set-format} Command |
24840 | @findex -var-set-format | |
922fbb7b | 24841 | |
a2c02241 | 24842 | @subsubheading Synopsis |
922fbb7b AC |
24843 | |
24844 | @smallexample | |
a2c02241 | 24845 | -var-set-format @var{name} @var{format-spec} |
922fbb7b AC |
24846 | @end smallexample |
24847 | ||
a2c02241 NR |
24848 | Sets the output format for the value of the object @var{name} to be |
24849 | @var{format-spec}. | |
24850 | ||
de051565 | 24851 | @anchor{-var-set-format} |
a2c02241 NR |
24852 | The syntax for the @var{format-spec} is as follows: |
24853 | ||
24854 | @smallexample | |
24855 | @var{format-spec} @expansion{} | |
24856 | @{binary | decimal | hexadecimal | octal | natural@} | |
24857 | @end smallexample | |
24858 | ||
c8b2f53c VP |
24859 | The natural format is the default format choosen automatically |
24860 | based on the variable type (like decimal for an @code{int}, hex | |
24861 | for pointers, etc.). | |
24862 | ||
24863 | For a variable with children, the format is set only on the | |
24864 | variable itself, and the children are not affected. | |
a2c02241 NR |
24865 | |
24866 | @subheading The @code{-var-show-format} Command | |
24867 | @findex -var-show-format | |
922fbb7b AC |
24868 | |
24869 | @subsubheading Synopsis | |
24870 | ||
24871 | @smallexample | |
a2c02241 | 24872 | -var-show-format @var{name} |
922fbb7b AC |
24873 | @end smallexample |
24874 | ||
a2c02241 | 24875 | Returns the format used to display the value of the object @var{name}. |
922fbb7b | 24876 | |
a2c02241 NR |
24877 | @smallexample |
24878 | @var{format} @expansion{} | |
24879 | @var{format-spec} | |
24880 | @end smallexample | |
922fbb7b | 24881 | |
922fbb7b | 24882 | |
a2c02241 NR |
24883 | @subheading The @code{-var-info-num-children} Command |
24884 | @findex -var-info-num-children | |
24885 | ||
24886 | @subsubheading Synopsis | |
24887 | ||
24888 | @smallexample | |
24889 | -var-info-num-children @var{name} | |
24890 | @end smallexample | |
24891 | ||
24892 | Returns the number of children of a variable object @var{name}: | |
24893 | ||
24894 | @smallexample | |
24895 | numchild=@var{n} | |
24896 | @end smallexample | |
24897 | ||
0cc7d26f TT |
24898 | Note that this number is not completely reliable for a dynamic varobj. |
24899 | It will return the current number of children, but more children may | |
24900 | be available. | |
24901 | ||
a2c02241 NR |
24902 | |
24903 | @subheading The @code{-var-list-children} Command | |
24904 | @findex -var-list-children | |
24905 | ||
24906 | @subsubheading Synopsis | |
24907 | ||
24908 | @smallexample | |
0cc7d26f | 24909 | -var-list-children [@var{print-values}] @var{name} [@var{from} @var{to}] |
a2c02241 | 24910 | @end smallexample |
b569d230 | 24911 | @anchor{-var-list-children} |
a2c02241 NR |
24912 | |
24913 | Return a list of the children of the specified variable object and | |
24914 | create variable objects for them, if they do not already exist. With | |
24915 | a single argument or if @var{print-values} has a value for of 0 or | |
24916 | @code{--no-values}, print only the names of the variables; if | |
24917 | @var{print-values} is 1 or @code{--all-values}, also print their | |
24918 | values; and if it is 2 or @code{--simple-values} print the name and | |
24919 | value for simple data types and just the name for arrays, structures | |
24920 | and unions. | |
922fbb7b | 24921 | |
0cc7d26f TT |
24922 | @var{from} and @var{to}, if specified, indicate the range of children |
24923 | to report. If @var{from} or @var{to} is less than zero, the range is | |
24924 | reset and all children will be reported. Otherwise, children starting | |
24925 | at @var{from} (zero-based) and up to and excluding @var{to} will be | |
24926 | reported. | |
24927 | ||
24928 | If a child range is requested, it will only affect the current call to | |
24929 | @code{-var-list-children}, but not future calls to @code{-var-update}. | |
24930 | For this, you must instead use @code{-var-set-update-range}. The | |
24931 | intent of this approach is to enable a front end to implement any | |
24932 | update approach it likes; for example, scrolling a view may cause the | |
24933 | front end to request more children with @code{-var-list-children}, and | |
24934 | then the front end could call @code{-var-set-update-range} with a | |
24935 | different range to ensure that future updates are restricted to just | |
24936 | the visible items. | |
24937 | ||
b569d230 EZ |
24938 | For each child the following results are returned: |
24939 | ||
24940 | @table @var | |
24941 | ||
24942 | @item name | |
24943 | Name of the variable object created for this child. | |
24944 | ||
24945 | @item exp | |
24946 | The expression to be shown to the user by the front end to designate this child. | |
24947 | For example this may be the name of a structure member. | |
24948 | ||
0cc7d26f TT |
24949 | For a dynamic varobj, this value cannot be used to form an |
24950 | expression. There is no way to do this at all with a dynamic varobj. | |
24951 | ||
b569d230 EZ |
24952 | For C/C@t{++} structures there are several pseudo children returned to |
24953 | designate access qualifiers. For these pseudo children @var{exp} is | |
24954 | @samp{public}, @samp{private}, or @samp{protected}. In this case the | |
24955 | type and value are not present. | |
24956 | ||
0cc7d26f TT |
24957 | A dynamic varobj will not report the access qualifying |
24958 | pseudo-children, regardless of the language. This information is not | |
24959 | available at all with a dynamic varobj. | |
24960 | ||
b569d230 | 24961 | @item numchild |
0cc7d26f TT |
24962 | Number of children this child has. For a dynamic varobj, this will be |
24963 | 0. | |
b569d230 EZ |
24964 | |
24965 | @item type | |
24966 | The type of the child. | |
24967 | ||
24968 | @item value | |
24969 | If values were requested, this is the value. | |
24970 | ||
24971 | @item thread-id | |
24972 | If this variable object is associated with a thread, this is the thread id. | |
24973 | Otherwise this result is not present. | |
24974 | ||
24975 | @item frozen | |
24976 | If the variable object is frozen, this variable will be present with a value of 1. | |
24977 | @end table | |
24978 | ||
0cc7d26f TT |
24979 | The result may have its own attributes: |
24980 | ||
24981 | @table @samp | |
24982 | @item displayhint | |
24983 | A dynamic varobj can supply a display hint to the front end. The | |
24984 | value comes directly from the Python pretty-printer object's | |
24985 | @code{display_hint} method. @xref{Pretty Printing}. | |
24986 | ||
24987 | @item has_more | |
24988 | This is an integer attribute which is nonzero if there are children | |
24989 | remaining after the end of the selected range. | |
24990 | @end table | |
24991 | ||
922fbb7b AC |
24992 | @subsubheading Example |
24993 | ||
24994 | @smallexample | |
594fe323 | 24995 | (gdb) |
a2c02241 | 24996 | -var-list-children n |
b569d230 | 24997 | ^done,numchild=@var{n},children=[child=@{name=@var{name},exp=@var{exp}, |
a2c02241 | 24998 | numchild=@var{n},type=@var{type}@},@r{(repeats N times)}] |
594fe323 | 24999 | (gdb) |
a2c02241 | 25000 | -var-list-children --all-values n |
b569d230 | 25001 | ^done,numchild=@var{n},children=[child=@{name=@var{name},exp=@var{exp}, |
a2c02241 | 25002 | numchild=@var{n},value=@var{value},type=@var{type}@},@r{(repeats N times)}] |
922fbb7b AC |
25003 | @end smallexample |
25004 | ||
922fbb7b | 25005 | |
a2c02241 NR |
25006 | @subheading The @code{-var-info-type} Command |
25007 | @findex -var-info-type | |
922fbb7b | 25008 | |
a2c02241 NR |
25009 | @subsubheading Synopsis |
25010 | ||
25011 | @smallexample | |
25012 | -var-info-type @var{name} | |
25013 | @end smallexample | |
25014 | ||
25015 | Returns the type of the specified variable @var{name}. The type is | |
25016 | returned as a string in the same format as it is output by the | |
25017 | @value{GDBN} CLI: | |
25018 | ||
25019 | @smallexample | |
25020 | type=@var{typename} | |
25021 | @end smallexample | |
25022 | ||
25023 | ||
25024 | @subheading The @code{-var-info-expression} Command | |
25025 | @findex -var-info-expression | |
922fbb7b AC |
25026 | |
25027 | @subsubheading Synopsis | |
25028 | ||
25029 | @smallexample | |
a2c02241 | 25030 | -var-info-expression @var{name} |
922fbb7b AC |
25031 | @end smallexample |
25032 | ||
02142340 VP |
25033 | Returns a string that is suitable for presenting this |
25034 | variable object in user interface. The string is generally | |
25035 | not valid expression in the current language, and cannot be evaluated. | |
25036 | ||
25037 | For example, if @code{a} is an array, and variable object | |
25038 | @code{A} was created for @code{a}, then we'll get this output: | |
922fbb7b | 25039 | |
a2c02241 | 25040 | @smallexample |
02142340 VP |
25041 | (gdb) -var-info-expression A.1 |
25042 | ^done,lang="C",exp="1" | |
a2c02241 | 25043 | @end smallexample |
922fbb7b | 25044 | |
a2c02241 | 25045 | @noindent |
02142340 VP |
25046 | Here, the values of @code{lang} can be @code{@{"C" | "C++" | "Java"@}}. |
25047 | ||
25048 | Note that the output of the @code{-var-list-children} command also | |
25049 | includes those expressions, so the @code{-var-info-expression} command | |
25050 | is of limited use. | |
25051 | ||
25052 | @subheading The @code{-var-info-path-expression} Command | |
25053 | @findex -var-info-path-expression | |
25054 | ||
25055 | @subsubheading Synopsis | |
25056 | ||
25057 | @smallexample | |
25058 | -var-info-path-expression @var{name} | |
25059 | @end smallexample | |
25060 | ||
25061 | Returns an expression that can be evaluated in the current | |
25062 | context and will yield the same value that a variable object has. | |
25063 | Compare this with the @code{-var-info-expression} command, which | |
25064 | result can be used only for UI presentation. Typical use of | |
25065 | the @code{-var-info-path-expression} command is creating a | |
25066 | watchpoint from a variable object. | |
25067 | ||
0cc7d26f TT |
25068 | This command is currently not valid for children of a dynamic varobj, |
25069 | and will give an error when invoked on one. | |
25070 | ||
02142340 VP |
25071 | For example, suppose @code{C} is a C@t{++} class, derived from class |
25072 | @code{Base}, and that the @code{Base} class has a member called | |
25073 | @code{m_size}. Assume a variable @code{c} is has the type of | |
25074 | @code{C} and a variable object @code{C} was created for variable | |
25075 | @code{c}. Then, we'll get this output: | |
25076 | @smallexample | |
25077 | (gdb) -var-info-path-expression C.Base.public.m_size | |
25078 | ^done,path_expr=((Base)c).m_size) | |
25079 | @end smallexample | |
922fbb7b | 25080 | |
a2c02241 NR |
25081 | @subheading The @code{-var-show-attributes} Command |
25082 | @findex -var-show-attributes | |
922fbb7b | 25083 | |
a2c02241 | 25084 | @subsubheading Synopsis |
922fbb7b | 25085 | |
a2c02241 NR |
25086 | @smallexample |
25087 | -var-show-attributes @var{name} | |
25088 | @end smallexample | |
922fbb7b | 25089 | |
a2c02241 | 25090 | List attributes of the specified variable object @var{name}: |
922fbb7b AC |
25091 | |
25092 | @smallexample | |
a2c02241 | 25093 | status=@var{attr} [ ( ,@var{attr} )* ] |
922fbb7b AC |
25094 | @end smallexample |
25095 | ||
a2c02241 NR |
25096 | @noindent |
25097 | where @var{attr} is @code{@{ @{ editable | noneditable @} | TBD @}}. | |
25098 | ||
25099 | @subheading The @code{-var-evaluate-expression} Command | |
25100 | @findex -var-evaluate-expression | |
25101 | ||
25102 | @subsubheading Synopsis | |
25103 | ||
25104 | @smallexample | |
de051565 | 25105 | -var-evaluate-expression [-f @var{format-spec}] @var{name} |
a2c02241 NR |
25106 | @end smallexample |
25107 | ||
25108 | Evaluates the expression that is represented by the specified variable | |
de051565 MK |
25109 | object and returns its value as a string. The format of the string |
25110 | can be specified with the @samp{-f} option. The possible values of | |
25111 | this option are the same as for @code{-var-set-format} | |
25112 | (@pxref{-var-set-format}). If the @samp{-f} option is not specified, | |
25113 | the current display format will be used. The current display format | |
25114 | can be changed using the @code{-var-set-format} command. | |
a2c02241 NR |
25115 | |
25116 | @smallexample | |
25117 | value=@var{value} | |
25118 | @end smallexample | |
25119 | ||
25120 | Note that one must invoke @code{-var-list-children} for a variable | |
25121 | before the value of a child variable can be evaluated. | |
25122 | ||
25123 | @subheading The @code{-var-assign} Command | |
25124 | @findex -var-assign | |
25125 | ||
25126 | @subsubheading Synopsis | |
25127 | ||
25128 | @smallexample | |
25129 | -var-assign @var{name} @var{expression} | |
25130 | @end smallexample | |
25131 | ||
25132 | Assigns the value of @var{expression} to the variable object specified | |
25133 | by @var{name}. The object must be @samp{editable}. If the variable's | |
25134 | value is altered by the assign, the variable will show up in any | |
25135 | subsequent @code{-var-update} list. | |
25136 | ||
25137 | @subsubheading Example | |
922fbb7b AC |
25138 | |
25139 | @smallexample | |
594fe323 | 25140 | (gdb) |
a2c02241 NR |
25141 | -var-assign var1 3 |
25142 | ^done,value="3" | |
594fe323 | 25143 | (gdb) |
a2c02241 NR |
25144 | -var-update * |
25145 | ^done,changelist=[@{name="var1",in_scope="true",type_changed="false"@}] | |
594fe323 | 25146 | (gdb) |
922fbb7b AC |
25147 | @end smallexample |
25148 | ||
a2c02241 NR |
25149 | @subheading The @code{-var-update} Command |
25150 | @findex -var-update | |
25151 | ||
25152 | @subsubheading Synopsis | |
25153 | ||
25154 | @smallexample | |
25155 | -var-update [@var{print-values}] @{@var{name} | "*"@} | |
25156 | @end smallexample | |
25157 | ||
c8b2f53c VP |
25158 | Reevaluate the expressions corresponding to the variable object |
25159 | @var{name} and all its direct and indirect children, and return the | |
36ece8b3 NR |
25160 | list of variable objects whose values have changed; @var{name} must |
25161 | be a root variable object. Here, ``changed'' means that the result of | |
25162 | @code{-var-evaluate-expression} before and after the | |
25163 | @code{-var-update} is different. If @samp{*} is used as the variable | |
9f708cb2 VP |
25164 | object names, all existing variable objects are updated, except |
25165 | for frozen ones (@pxref{-var-set-frozen}). The option | |
36ece8b3 | 25166 | @var{print-values} determines whether both names and values, or just |
de051565 | 25167 | names are printed. The possible values of this option are the same |
36ece8b3 NR |
25168 | as for @code{-var-list-children} (@pxref{-var-list-children}). It is |
25169 | recommended to use the @samp{--all-values} option, to reduce the | |
25170 | number of MI commands needed on each program stop. | |
c8b2f53c | 25171 | |
c3b108f7 VP |
25172 | With the @samp{*} parameter, if a variable object is bound to a |
25173 | currently running thread, it will not be updated, without any | |
25174 | diagnostic. | |
a2c02241 | 25175 | |
0cc7d26f TT |
25176 | If @code{-var-set-update-range} was previously used on a varobj, then |
25177 | only the selected range of children will be reported. | |
922fbb7b | 25178 | |
0cc7d26f TT |
25179 | @code{-var-update} reports all the changed varobjs in a tuple named |
25180 | @samp{changelist}. | |
25181 | ||
25182 | Each item in the change list is itself a tuple holding: | |
25183 | ||
25184 | @table @samp | |
25185 | @item name | |
25186 | The name of the varobj. | |
25187 | ||
25188 | @item value | |
25189 | If values were requested for this update, then this field will be | |
25190 | present and will hold the value of the varobj. | |
922fbb7b | 25191 | |
0cc7d26f | 25192 | @item in_scope |
9f708cb2 | 25193 | @anchor{-var-update} |
0cc7d26f | 25194 | This field is a string which may take one of three values: |
36ece8b3 NR |
25195 | |
25196 | @table @code | |
25197 | @item "true" | |
25198 | The variable object's current value is valid. | |
25199 | ||
25200 | @item "false" | |
25201 | The variable object does not currently hold a valid value but it may | |
25202 | hold one in the future if its associated expression comes back into | |
25203 | scope. | |
25204 | ||
25205 | @item "invalid" | |
25206 | The variable object no longer holds a valid value. | |
25207 | This can occur when the executable file being debugged has changed, | |
25208 | either through recompilation or by using the @value{GDBN} @code{file} | |
25209 | command. The front end should normally choose to delete these variable | |
25210 | objects. | |
25211 | @end table | |
25212 | ||
25213 | In the future new values may be added to this list so the front should | |
25214 | be prepared for this possibility. @xref{GDB/MI Development and Front Ends, ,@sc{GDB/MI} Development and Front Ends}. | |
25215 | ||
0cc7d26f TT |
25216 | @item type_changed |
25217 | This is only present if the varobj is still valid. If the type | |
25218 | changed, then this will be the string @samp{true}; otherwise it will | |
25219 | be @samp{false}. | |
25220 | ||
25221 | @item new_type | |
25222 | If the varobj's type changed, then this field will be present and will | |
25223 | hold the new type. | |
25224 | ||
25225 | @item new_num_children | |
25226 | For a dynamic varobj, if the number of children changed, or if the | |
25227 | type changed, this will be the new number of children. | |
25228 | ||
25229 | The @samp{numchild} field in other varobj responses is generally not | |
25230 | valid for a dynamic varobj -- it will show the number of children that | |
25231 | @value{GDBN} knows about, but because dynamic varobjs lazily | |
25232 | instantiate their children, this will not reflect the number of | |
25233 | children which may be available. | |
25234 | ||
25235 | The @samp{new_num_children} attribute only reports changes to the | |
25236 | number of children known by @value{GDBN}. This is the only way to | |
25237 | detect whether an update has removed children (which necessarily can | |
25238 | only happen at the end of the update range). | |
25239 | ||
25240 | @item displayhint | |
25241 | The display hint, if any. | |
25242 | ||
25243 | @item has_more | |
25244 | This is an integer value, which will be 1 if there are more children | |
25245 | available outside the varobj's update range. | |
25246 | ||
25247 | @item dynamic | |
25248 | This attribute will be present and have the value @samp{1} if the | |
25249 | varobj is a dynamic varobj. If the varobj is not a dynamic varobj, | |
25250 | then this attribute will not be present. | |
25251 | ||
25252 | @item new_children | |
25253 | If new children were added to a dynamic varobj within the selected | |
25254 | update range (as set by @code{-var-set-update-range}), then they will | |
25255 | be listed in this attribute. | |
25256 | @end table | |
25257 | ||
25258 | @subsubheading Example | |
25259 | ||
25260 | @smallexample | |
25261 | (gdb) | |
25262 | -var-assign var1 3 | |
25263 | ^done,value="3" | |
25264 | (gdb) | |
25265 | -var-update --all-values var1 | |
25266 | ^done,changelist=[@{name="var1",value="3",in_scope="true", | |
25267 | type_changed="false"@}] | |
25268 | (gdb) | |
25269 | @end smallexample | |
25270 | ||
25d5ea92 VP |
25271 | @subheading The @code{-var-set-frozen} Command |
25272 | @findex -var-set-frozen | |
9f708cb2 | 25273 | @anchor{-var-set-frozen} |
25d5ea92 VP |
25274 | |
25275 | @subsubheading Synopsis | |
25276 | ||
25277 | @smallexample | |
9f708cb2 | 25278 | -var-set-frozen @var{name} @var{flag} |
25d5ea92 VP |
25279 | @end smallexample |
25280 | ||
9f708cb2 | 25281 | Set the frozenness flag on the variable object @var{name}. The |
25d5ea92 | 25282 | @var{flag} parameter should be either @samp{1} to make the variable |
9f708cb2 | 25283 | frozen or @samp{0} to make it unfrozen. If a variable object is |
25d5ea92 | 25284 | frozen, then neither itself, nor any of its children, are |
9f708cb2 | 25285 | implicitly updated by @code{-var-update} of |
25d5ea92 VP |
25286 | a parent variable or by @code{-var-update *}. Only |
25287 | @code{-var-update} of the variable itself will update its value and | |
25288 | values of its children. After a variable object is unfrozen, it is | |
25289 | implicitly updated by all subsequent @code{-var-update} operations. | |
25290 | Unfreezing a variable does not update it, only subsequent | |
25291 | @code{-var-update} does. | |
25292 | ||
25293 | @subsubheading Example | |
25294 | ||
25295 | @smallexample | |
25296 | (gdb) | |
25297 | -var-set-frozen V 1 | |
25298 | ^done | |
25299 | (gdb) | |
25300 | @end smallexample | |
25301 | ||
0cc7d26f TT |
25302 | @subheading The @code{-var-set-update-range} command |
25303 | @findex -var-set-update-range | |
25304 | @anchor{-var-set-update-range} | |
25305 | ||
25306 | @subsubheading Synopsis | |
25307 | ||
25308 | @smallexample | |
25309 | -var-set-update-range @var{name} @var{from} @var{to} | |
25310 | @end smallexample | |
25311 | ||
25312 | Set the range of children to be returned by future invocations of | |
25313 | @code{-var-update}. | |
25314 | ||
25315 | @var{from} and @var{to} indicate the range of children to report. If | |
25316 | @var{from} or @var{to} is less than zero, the range is reset and all | |
25317 | children will be reported. Otherwise, children starting at @var{from} | |
25318 | (zero-based) and up to and excluding @var{to} will be reported. | |
25319 | ||
25320 | @subsubheading Example | |
25321 | ||
25322 | @smallexample | |
25323 | (gdb) | |
25324 | -var-set-update-range V 1 2 | |
25325 | ^done | |
25326 | @end smallexample | |
25327 | ||
b6313243 TT |
25328 | @subheading The @code{-var-set-visualizer} command |
25329 | @findex -var-set-visualizer | |
25330 | @anchor{-var-set-visualizer} | |
25331 | ||
25332 | @subsubheading Synopsis | |
25333 | ||
25334 | @smallexample | |
25335 | -var-set-visualizer @var{name} @var{visualizer} | |
25336 | @end smallexample | |
25337 | ||
25338 | Set a visualizer for the variable object @var{name}. | |
25339 | ||
25340 | @var{visualizer} is the visualizer to use. The special value | |
25341 | @samp{None} means to disable any visualizer in use. | |
25342 | ||
25343 | If not @samp{None}, @var{visualizer} must be a Python expression. | |
25344 | This expression must evaluate to a callable object which accepts a | |
25345 | single argument. @value{GDBN} will call this object with the value of | |
25346 | the varobj @var{name} as an argument (this is done so that the same | |
25347 | Python pretty-printing code can be used for both the CLI and MI). | |
25348 | When called, this object must return an object which conforms to the | |
25349 | pretty-printing interface (@pxref{Pretty Printing}). | |
25350 | ||
25351 | The pre-defined function @code{gdb.default_visualizer} may be used to | |
25352 | select a visualizer by following the built-in process | |
25353 | (@pxref{Selecting Pretty-Printers}). This is done automatically when | |
25354 | a varobj is created, and so ordinarily is not needed. | |
25355 | ||
25356 | This feature is only available if Python support is enabled. The MI | |
25357 | command @code{-list-features} (@pxref{GDB/MI Miscellaneous Commands}) | |
25358 | can be used to check this. | |
25359 | ||
25360 | @subsubheading Example | |
25361 | ||
25362 | Resetting the visualizer: | |
25363 | ||
25364 | @smallexample | |
25365 | (gdb) | |
25366 | -var-set-visualizer V None | |
25367 | ^done | |
25368 | @end smallexample | |
25369 | ||
25370 | Reselecting the default (type-based) visualizer: | |
25371 | ||
25372 | @smallexample | |
25373 | (gdb) | |
25374 | -var-set-visualizer V gdb.default_visualizer | |
25375 | ^done | |
25376 | @end smallexample | |
25377 | ||
25378 | Suppose @code{SomeClass} is a visualizer class. A lambda expression | |
25379 | can be used to instantiate this class for a varobj: | |
25380 | ||
25381 | @smallexample | |
25382 | (gdb) | |
25383 | -var-set-visualizer V "lambda val: SomeClass()" | |
25384 | ^done | |
25385 | @end smallexample | |
25d5ea92 | 25386 | |
a2c02241 NR |
25387 | @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% |
25388 | @node GDB/MI Data Manipulation | |
25389 | @section @sc{gdb/mi} Data Manipulation | |
922fbb7b | 25390 | |
a2c02241 NR |
25391 | @cindex data manipulation, in @sc{gdb/mi} |
25392 | @cindex @sc{gdb/mi}, data manipulation | |
25393 | This section describes the @sc{gdb/mi} commands that manipulate data: | |
25394 | examine memory and registers, evaluate expressions, etc. | |
25395 | ||
25396 | @c REMOVED FROM THE INTERFACE. | |
25397 | @c @subheading -data-assign | |
25398 | @c Change the value of a program variable. Plenty of side effects. | |
79a6e687 | 25399 | @c @subsubheading GDB Command |
a2c02241 NR |
25400 | @c set variable |
25401 | @c @subsubheading Example | |
25402 | @c N.A. | |
25403 | ||
25404 | @subheading The @code{-data-disassemble} Command | |
25405 | @findex -data-disassemble | |
922fbb7b AC |
25406 | |
25407 | @subsubheading Synopsis | |
25408 | ||
25409 | @smallexample | |
a2c02241 NR |
25410 | -data-disassemble |
25411 | [ -s @var{start-addr} -e @var{end-addr} ] | |
25412 | | [ -f @var{filename} -l @var{linenum} [ -n @var{lines} ] ] | |
25413 | -- @var{mode} | |
922fbb7b AC |
25414 | @end smallexample |
25415 | ||
a2c02241 NR |
25416 | @noindent |
25417 | Where: | |
25418 | ||
25419 | @table @samp | |
25420 | @item @var{start-addr} | |
25421 | is the beginning address (or @code{$pc}) | |
25422 | @item @var{end-addr} | |
25423 | is the end address | |
25424 | @item @var{filename} | |
25425 | is the name of the file to disassemble | |
25426 | @item @var{linenum} | |
25427 | is the line number to disassemble around | |
25428 | @item @var{lines} | |
d3e8051b | 25429 | is the number of disassembly lines to be produced. If it is -1, |
a2c02241 NR |
25430 | the whole function will be disassembled, in case no @var{end-addr} is |
25431 | specified. If @var{end-addr} is specified as a non-zero value, and | |
25432 | @var{lines} is lower than the number of disassembly lines between | |
25433 | @var{start-addr} and @var{end-addr}, only @var{lines} lines are | |
25434 | displayed; if @var{lines} is higher than the number of lines between | |
25435 | @var{start-addr} and @var{end-addr}, only the lines up to @var{end-addr} | |
25436 | are displayed. | |
25437 | @item @var{mode} | |
25438 | is either 0 (meaning only disassembly) or 1 (meaning mixed source and | |
25439 | disassembly). | |
25440 | @end table | |
25441 | ||
25442 | @subsubheading Result | |
25443 | ||
25444 | The output for each instruction is composed of four fields: | |
25445 | ||
25446 | @itemize @bullet | |
25447 | @item Address | |
25448 | @item Func-name | |
25449 | @item Offset | |
25450 | @item Instruction | |
25451 | @end itemize | |
25452 | ||
25453 | Note that whatever included in the instruction field, is not manipulated | |
d3e8051b | 25454 | directly by @sc{gdb/mi}, i.e., it is not possible to adjust its format. |
922fbb7b AC |
25455 | |
25456 | @subsubheading @value{GDBN} Command | |
25457 | ||
a2c02241 | 25458 | There's no direct mapping from this command to the CLI. |
922fbb7b AC |
25459 | |
25460 | @subsubheading Example | |
25461 | ||
a2c02241 NR |
25462 | Disassemble from the current value of @code{$pc} to @code{$pc + 20}: |
25463 | ||
922fbb7b | 25464 | @smallexample |
594fe323 | 25465 | (gdb) |
a2c02241 NR |
25466 | -data-disassemble -s $pc -e "$pc + 20" -- 0 |
25467 | ^done, | |
25468 | asm_insns=[ | |
25469 | @{address="0x000107c0",func-name="main",offset="4", | |
25470 | inst="mov 2, %o0"@}, | |
25471 | @{address="0x000107c4",func-name="main",offset="8", | |
25472 | inst="sethi %hi(0x11800), %o2"@}, | |
25473 | @{address="0x000107c8",func-name="main",offset="12", | |
25474 | inst="or %o2, 0x140, %o1\t! 0x11940 <_lib_version+8>"@}, | |
25475 | @{address="0x000107cc",func-name="main",offset="16", | |
25476 | inst="sethi %hi(0x11800), %o2"@}, | |
25477 | @{address="0x000107d0",func-name="main",offset="20", | |
25478 | inst="or %o2, 0x168, %o4\t! 0x11968 <_lib_version+48>"@}] | |
594fe323 | 25479 | (gdb) |
a2c02241 NR |
25480 | @end smallexample |
25481 | ||
25482 | Disassemble the whole @code{main} function. Line 32 is part of | |
25483 | @code{main}. | |
25484 | ||
25485 | @smallexample | |
25486 | -data-disassemble -f basics.c -l 32 -- 0 | |
25487 | ^done,asm_insns=[ | |
25488 | @{address="0x000107bc",func-name="main",offset="0", | |
25489 | inst="save %sp, -112, %sp"@}, | |
25490 | @{address="0x000107c0",func-name="main",offset="4", | |
25491 | inst="mov 2, %o0"@}, | |
25492 | @{address="0x000107c4",func-name="main",offset="8", | |
25493 | inst="sethi %hi(0x11800), %o2"@}, | |
25494 | [@dots{}] | |
25495 | @{address="0x0001081c",func-name="main",offset="96",inst="ret "@}, | |
25496 | @{address="0x00010820",func-name="main",offset="100",inst="restore "@}] | |
594fe323 | 25497 | (gdb) |
922fbb7b AC |
25498 | @end smallexample |
25499 | ||
a2c02241 | 25500 | Disassemble 3 instructions from the start of @code{main}: |
922fbb7b | 25501 | |
a2c02241 | 25502 | @smallexample |
594fe323 | 25503 | (gdb) |
a2c02241 NR |
25504 | -data-disassemble -f basics.c -l 32 -n 3 -- 0 |
25505 | ^done,asm_insns=[ | |
25506 | @{address="0x000107bc",func-name="main",offset="0", | |
25507 | inst="save %sp, -112, %sp"@}, | |
25508 | @{address="0x000107c0",func-name="main",offset="4", | |
25509 | inst="mov 2, %o0"@}, | |
25510 | @{address="0x000107c4",func-name="main",offset="8", | |
25511 | inst="sethi %hi(0x11800), %o2"@}] | |
594fe323 | 25512 | (gdb) |
a2c02241 NR |
25513 | @end smallexample |
25514 | ||
25515 | Disassemble 3 instructions from the start of @code{main} in mixed mode: | |
25516 | ||
25517 | @smallexample | |
594fe323 | 25518 | (gdb) |
a2c02241 NR |
25519 | -data-disassemble -f basics.c -l 32 -n 3 -- 1 |
25520 | ^done,asm_insns=[ | |
25521 | src_and_asm_line=@{line="31", | |
25522 | file="/kwikemart/marge/ezannoni/flathead-dev/devo/gdb/ \ | |
25523 | testsuite/gdb.mi/basics.c",line_asm_insn=[ | |
25524 | @{address="0x000107bc",func-name="main",offset="0", | |
25525 | inst="save %sp, -112, %sp"@}]@}, | |
25526 | src_and_asm_line=@{line="32", | |
25527 | file="/kwikemart/marge/ezannoni/flathead-dev/devo/gdb/ \ | |
25528 | testsuite/gdb.mi/basics.c",line_asm_insn=[ | |
25529 | @{address="0x000107c0",func-name="main",offset="4", | |
25530 | inst="mov 2, %o0"@}, | |
25531 | @{address="0x000107c4",func-name="main",offset="8", | |
25532 | inst="sethi %hi(0x11800), %o2"@}]@}] | |
594fe323 | 25533 | (gdb) |
a2c02241 NR |
25534 | @end smallexample |
25535 | ||
25536 | ||
25537 | @subheading The @code{-data-evaluate-expression} Command | |
25538 | @findex -data-evaluate-expression | |
922fbb7b AC |
25539 | |
25540 | @subsubheading Synopsis | |
25541 | ||
25542 | @smallexample | |
a2c02241 | 25543 | -data-evaluate-expression @var{expr} |
922fbb7b AC |
25544 | @end smallexample |
25545 | ||
a2c02241 NR |
25546 | Evaluate @var{expr} as an expression. The expression could contain an |
25547 | inferior function call. The function call will execute synchronously. | |
25548 | If the expression contains spaces, it must be enclosed in double quotes. | |
922fbb7b AC |
25549 | |
25550 | @subsubheading @value{GDBN} Command | |
25551 | ||
a2c02241 NR |
25552 | The corresponding @value{GDBN} commands are @samp{print}, @samp{output}, and |
25553 | @samp{call}. In @code{gdbtk} only, there's a corresponding | |
25554 | @samp{gdb_eval} command. | |
922fbb7b AC |
25555 | |
25556 | @subsubheading Example | |
25557 | ||
a2c02241 NR |
25558 | In the following example, the numbers that precede the commands are the |
25559 | @dfn{tokens} described in @ref{GDB/MI Command Syntax, ,@sc{gdb/mi} | |
25560 | Command Syntax}. Notice how @sc{gdb/mi} returns the same tokens in its | |
25561 | output. | |
25562 | ||
922fbb7b | 25563 | @smallexample |
a2c02241 NR |
25564 | 211-data-evaluate-expression A |
25565 | 211^done,value="1" | |
594fe323 | 25566 | (gdb) |
a2c02241 NR |
25567 | 311-data-evaluate-expression &A |
25568 | 311^done,value="0xefffeb7c" | |
594fe323 | 25569 | (gdb) |
a2c02241 NR |
25570 | 411-data-evaluate-expression A+3 |
25571 | 411^done,value="4" | |
594fe323 | 25572 | (gdb) |
a2c02241 NR |
25573 | 511-data-evaluate-expression "A + 3" |
25574 | 511^done,value="4" | |
594fe323 | 25575 | (gdb) |
a2c02241 | 25576 | @end smallexample |
922fbb7b AC |
25577 | |
25578 | ||
a2c02241 NR |
25579 | @subheading The @code{-data-list-changed-registers} Command |
25580 | @findex -data-list-changed-registers | |
922fbb7b AC |
25581 | |
25582 | @subsubheading Synopsis | |
25583 | ||
25584 | @smallexample | |
a2c02241 | 25585 | -data-list-changed-registers |
922fbb7b AC |
25586 | @end smallexample |
25587 | ||
a2c02241 | 25588 | Display a list of the registers that have changed. |
922fbb7b AC |
25589 | |
25590 | @subsubheading @value{GDBN} Command | |
25591 | ||
a2c02241 NR |
25592 | @value{GDBN} doesn't have a direct analog for this command; @code{gdbtk} |
25593 | has the corresponding command @samp{gdb_changed_register_list}. | |
922fbb7b AC |
25594 | |
25595 | @subsubheading Example | |
922fbb7b | 25596 | |
a2c02241 | 25597 | On a PPC MBX board: |
922fbb7b AC |
25598 | |
25599 | @smallexample | |
594fe323 | 25600 | (gdb) |
a2c02241 NR |
25601 | -exec-continue |
25602 | ^running | |
922fbb7b | 25603 | |
594fe323 | 25604 | (gdb) |
a47ec5fe AR |
25605 | *stopped,reason="breakpoint-hit",disp="keep",bkptno="1",frame=@{ |
25606 | func="main",args=[],file="try.c",fullname="/home/foo/bar/try.c", | |
25607 | line="5"@} | |
594fe323 | 25608 | (gdb) |
a2c02241 NR |
25609 | -data-list-changed-registers |
25610 | ^done,changed-registers=["0","1","2","4","5","6","7","8","9", | |
25611 | "10","11","13","14","15","16","17","18","19","20","21","22","23", | |
25612 | "24","25","26","27","28","30","31","64","65","66","67","69"] | |
594fe323 | 25613 | (gdb) |
a2c02241 | 25614 | @end smallexample |
922fbb7b AC |
25615 | |
25616 | ||
a2c02241 NR |
25617 | @subheading The @code{-data-list-register-names} Command |
25618 | @findex -data-list-register-names | |
922fbb7b AC |
25619 | |
25620 | @subsubheading Synopsis | |
25621 | ||
25622 | @smallexample | |
a2c02241 | 25623 | -data-list-register-names [ ( @var{regno} )+ ] |
922fbb7b AC |
25624 | @end smallexample |
25625 | ||
a2c02241 NR |
25626 | Show a list of register names for the current target. If no arguments |
25627 | are given, it shows a list of the names of all the registers. If | |
25628 | integer numbers are given as arguments, it will print a list of the | |
25629 | names of the registers corresponding to the arguments. To ensure | |
25630 | consistency between a register name and its number, the output list may | |
25631 | include empty register names. | |
922fbb7b AC |
25632 | |
25633 | @subsubheading @value{GDBN} Command | |
25634 | ||
a2c02241 NR |
25635 | @value{GDBN} does not have a command which corresponds to |
25636 | @samp{-data-list-register-names}. In @code{gdbtk} there is a | |
25637 | corresponding command @samp{gdb_regnames}. | |
922fbb7b AC |
25638 | |
25639 | @subsubheading Example | |
922fbb7b | 25640 | |
a2c02241 NR |
25641 | For the PPC MBX board: |
25642 | @smallexample | |
594fe323 | 25643 | (gdb) |
a2c02241 NR |
25644 | -data-list-register-names |
25645 | ^done,register-names=["r0","r1","r2","r3","r4","r5","r6","r7", | |
25646 | "r8","r9","r10","r11","r12","r13","r14","r15","r16","r17","r18", | |
25647 | "r19","r20","r21","r22","r23","r24","r25","r26","r27","r28","r29", | |
25648 | "r30","r31","f0","f1","f2","f3","f4","f5","f6","f7","f8","f9", | |
25649 | "f10","f11","f12","f13","f14","f15","f16","f17","f18","f19","f20", | |
25650 | "f21","f22","f23","f24","f25","f26","f27","f28","f29","f30","f31", | |
25651 | "", "pc","ps","cr","lr","ctr","xer"] | |
594fe323 | 25652 | (gdb) |
a2c02241 NR |
25653 | -data-list-register-names 1 2 3 |
25654 | ^done,register-names=["r1","r2","r3"] | |
594fe323 | 25655 | (gdb) |
a2c02241 | 25656 | @end smallexample |
922fbb7b | 25657 | |
a2c02241 NR |
25658 | @subheading The @code{-data-list-register-values} Command |
25659 | @findex -data-list-register-values | |
922fbb7b AC |
25660 | |
25661 | @subsubheading Synopsis | |
25662 | ||
25663 | @smallexample | |
a2c02241 | 25664 | -data-list-register-values @var{fmt} [ ( @var{regno} )*] |
922fbb7b AC |
25665 | @end smallexample |
25666 | ||
a2c02241 NR |
25667 | Display the registers' contents. @var{fmt} is the format according to |
25668 | which the registers' contents are to be returned, followed by an optional | |
25669 | list of numbers specifying the registers to display. A missing list of | |
25670 | numbers indicates that the contents of all the registers must be returned. | |
25671 | ||
25672 | Allowed formats for @var{fmt} are: | |
25673 | ||
25674 | @table @code | |
25675 | @item x | |
25676 | Hexadecimal | |
25677 | @item o | |
25678 | Octal | |
25679 | @item t | |
25680 | Binary | |
25681 | @item d | |
25682 | Decimal | |
25683 | @item r | |
25684 | Raw | |
25685 | @item N | |
25686 | Natural | |
25687 | @end table | |
922fbb7b AC |
25688 | |
25689 | @subsubheading @value{GDBN} Command | |
25690 | ||
a2c02241 NR |
25691 | The corresponding @value{GDBN} commands are @samp{info reg}, @samp{info |
25692 | all-reg}, and (in @code{gdbtk}) @samp{gdb_fetch_registers}. | |
922fbb7b AC |
25693 | |
25694 | @subsubheading Example | |
922fbb7b | 25695 | |
a2c02241 NR |
25696 | For a PPC MBX board (note: line breaks are for readability only, they |
25697 | don't appear in the actual output): | |
25698 | ||
25699 | @smallexample | |
594fe323 | 25700 | (gdb) |
a2c02241 NR |
25701 | -data-list-register-values r 64 65 |
25702 | ^done,register-values=[@{number="64",value="0xfe00a300"@}, | |
25703 | @{number="65",value="0x00029002"@}] | |
594fe323 | 25704 | (gdb) |
a2c02241 NR |
25705 | -data-list-register-values x |
25706 | ^done,register-values=[@{number="0",value="0xfe0043c8"@}, | |
25707 | @{number="1",value="0x3fff88"@},@{number="2",value="0xfffffffe"@}, | |
25708 | @{number="3",value="0x0"@},@{number="4",value="0xa"@}, | |
25709 | @{number="5",value="0x3fff68"@},@{number="6",value="0x3fff58"@}, | |
25710 | @{number="7",value="0xfe011e98"@},@{number="8",value="0x2"@}, | |
25711 | @{number="9",value="0xfa202820"@},@{number="10",value="0xfa202808"@}, | |
25712 | @{number="11",value="0x1"@},@{number="12",value="0x0"@}, | |
25713 | @{number="13",value="0x4544"@},@{number="14",value="0xffdfffff"@}, | |
25714 | @{number="15",value="0xffffffff"@},@{number="16",value="0xfffffeff"@}, | |
25715 | @{number="17",value="0xefffffed"@},@{number="18",value="0xfffffffe"@}, | |
25716 | @{number="19",value="0xffffffff"@},@{number="20",value="0xffffffff"@}, | |
25717 | @{number="21",value="0xffffffff"@},@{number="22",value="0xfffffff7"@}, | |
25718 | @{number="23",value="0xffffffff"@},@{number="24",value="0xffffffff"@}, | |
25719 | @{number="25",value="0xffffffff"@},@{number="26",value="0xfffffffb"@}, | |
25720 | @{number="27",value="0xffffffff"@},@{number="28",value="0xf7bfffff"@}, | |
25721 | @{number="29",value="0x0"@},@{number="30",value="0xfe010000"@}, | |
25722 | @{number="31",value="0x0"@},@{number="32",value="0x0"@}, | |
25723 | @{number="33",value="0x0"@},@{number="34",value="0x0"@}, | |
25724 | @{number="35",value="0x0"@},@{number="36",value="0x0"@}, | |
25725 | @{number="37",value="0x0"@},@{number="38",value="0x0"@}, | |
25726 | @{number="39",value="0x0"@},@{number="40",value="0x0"@}, | |
25727 | @{number="41",value="0x0"@},@{number="42",value="0x0"@}, | |
25728 | @{number="43",value="0x0"@},@{number="44",value="0x0"@}, | |
25729 | @{number="45",value="0x0"@},@{number="46",value="0x0"@}, | |
25730 | @{number="47",value="0x0"@},@{number="48",value="0x0"@}, | |
25731 | @{number="49",value="0x0"@},@{number="50",value="0x0"@}, | |
25732 | @{number="51",value="0x0"@},@{number="52",value="0x0"@}, | |
25733 | @{number="53",value="0x0"@},@{number="54",value="0x0"@}, | |
25734 | @{number="55",value="0x0"@},@{number="56",value="0x0"@}, | |
25735 | @{number="57",value="0x0"@},@{number="58",value="0x0"@}, | |
25736 | @{number="59",value="0x0"@},@{number="60",value="0x0"@}, | |
25737 | @{number="61",value="0x0"@},@{number="62",value="0x0"@}, | |
25738 | @{number="63",value="0x0"@},@{number="64",value="0xfe00a300"@}, | |
25739 | @{number="65",value="0x29002"@},@{number="66",value="0x202f04b5"@}, | |
25740 | @{number="67",value="0xfe0043b0"@},@{number="68",value="0xfe00b3e4"@}, | |
25741 | @{number="69",value="0x20002b03"@}] | |
594fe323 | 25742 | (gdb) |
a2c02241 | 25743 | @end smallexample |
922fbb7b | 25744 | |
a2c02241 NR |
25745 | |
25746 | @subheading The @code{-data-read-memory} Command | |
25747 | @findex -data-read-memory | |
922fbb7b AC |
25748 | |
25749 | @subsubheading Synopsis | |
25750 | ||
25751 | @smallexample | |
a2c02241 NR |
25752 | -data-read-memory [ -o @var{byte-offset} ] |
25753 | @var{address} @var{word-format} @var{word-size} | |
25754 | @var{nr-rows} @var{nr-cols} [ @var{aschar} ] | |
922fbb7b AC |
25755 | @end smallexample |
25756 | ||
a2c02241 NR |
25757 | @noindent |
25758 | where: | |
922fbb7b | 25759 | |
a2c02241 NR |
25760 | @table @samp |
25761 | @item @var{address} | |
25762 | An expression specifying the address of the first memory word to be | |
25763 | read. Complex expressions containing embedded white space should be | |
25764 | quoted using the C convention. | |
922fbb7b | 25765 | |
a2c02241 NR |
25766 | @item @var{word-format} |
25767 | The format to be used to print the memory words. The notation is the | |
25768 | same as for @value{GDBN}'s @code{print} command (@pxref{Output Formats, | |
79a6e687 | 25769 | ,Output Formats}). |
922fbb7b | 25770 | |
a2c02241 NR |
25771 | @item @var{word-size} |
25772 | The size of each memory word in bytes. | |
922fbb7b | 25773 | |
a2c02241 NR |
25774 | @item @var{nr-rows} |
25775 | The number of rows in the output table. | |
922fbb7b | 25776 | |
a2c02241 NR |
25777 | @item @var{nr-cols} |
25778 | The number of columns in the output table. | |
922fbb7b | 25779 | |
a2c02241 NR |
25780 | @item @var{aschar} |
25781 | If present, indicates that each row should include an @sc{ascii} dump. The | |
25782 | value of @var{aschar} is used as a padding character when a byte is not a | |
25783 | member of the printable @sc{ascii} character set (printable @sc{ascii} | |
25784 | characters are those whose code is between 32 and 126, inclusively). | |
922fbb7b | 25785 | |
a2c02241 NR |
25786 | @item @var{byte-offset} |
25787 | An offset to add to the @var{address} before fetching memory. | |
25788 | @end table | |
922fbb7b | 25789 | |
a2c02241 NR |
25790 | This command displays memory contents as a table of @var{nr-rows} by |
25791 | @var{nr-cols} words, each word being @var{word-size} bytes. In total, | |
25792 | @code{@var{nr-rows} * @var{nr-cols} * @var{word-size}} bytes are read | |
25793 | (returned as @samp{total-bytes}). Should less than the requested number | |
25794 | of bytes be returned by the target, the missing words are identified | |
25795 | using @samp{N/A}. The number of bytes read from the target is returned | |
25796 | in @samp{nr-bytes} and the starting address used to read memory in | |
25797 | @samp{addr}. | |
25798 | ||
25799 | The address of the next/previous row or page is available in | |
25800 | @samp{next-row} and @samp{prev-row}, @samp{next-page} and | |
25801 | @samp{prev-page}. | |
922fbb7b AC |
25802 | |
25803 | @subsubheading @value{GDBN} Command | |
25804 | ||
a2c02241 NR |
25805 | The corresponding @value{GDBN} command is @samp{x}. @code{gdbtk} has |
25806 | @samp{gdb_get_mem} memory read command. | |
922fbb7b AC |
25807 | |
25808 | @subsubheading Example | |
32e7087d | 25809 | |
a2c02241 NR |
25810 | Read six bytes of memory starting at @code{bytes+6} but then offset by |
25811 | @code{-6} bytes. Format as three rows of two columns. One byte per | |
25812 | word. Display each word in hex. | |
32e7087d JB |
25813 | |
25814 | @smallexample | |
594fe323 | 25815 | (gdb) |
a2c02241 NR |
25816 | 9-data-read-memory -o -6 -- bytes+6 x 1 3 2 |
25817 | 9^done,addr="0x00001390",nr-bytes="6",total-bytes="6", | |
25818 | next-row="0x00001396",prev-row="0x0000138e",next-page="0x00001396", | |
25819 | prev-page="0x0000138a",memory=[ | |
25820 | @{addr="0x00001390",data=["0x00","0x01"]@}, | |
25821 | @{addr="0x00001392",data=["0x02","0x03"]@}, | |
25822 | @{addr="0x00001394",data=["0x04","0x05"]@}] | |
594fe323 | 25823 | (gdb) |
32e7087d JB |
25824 | @end smallexample |
25825 | ||
a2c02241 NR |
25826 | Read two bytes of memory starting at address @code{shorts + 64} and |
25827 | display as a single word formatted in decimal. | |
32e7087d | 25828 | |
32e7087d | 25829 | @smallexample |
594fe323 | 25830 | (gdb) |
a2c02241 NR |
25831 | 5-data-read-memory shorts+64 d 2 1 1 |
25832 | 5^done,addr="0x00001510",nr-bytes="2",total-bytes="2", | |
25833 | next-row="0x00001512",prev-row="0x0000150e", | |
25834 | next-page="0x00001512",prev-page="0x0000150e",memory=[ | |
25835 | @{addr="0x00001510",data=["128"]@}] | |
594fe323 | 25836 | (gdb) |
32e7087d JB |
25837 | @end smallexample |
25838 | ||
a2c02241 NR |
25839 | Read thirty two bytes of memory starting at @code{bytes+16} and format |
25840 | as eight rows of four columns. Include a string encoding with @samp{x} | |
25841 | used as the non-printable character. | |
922fbb7b AC |
25842 | |
25843 | @smallexample | |
594fe323 | 25844 | (gdb) |
a2c02241 NR |
25845 | 4-data-read-memory bytes+16 x 1 8 4 x |
25846 | 4^done,addr="0x000013a0",nr-bytes="32",total-bytes="32", | |
25847 | next-row="0x000013c0",prev-row="0x0000139c", | |
25848 | next-page="0x000013c0",prev-page="0x00001380",memory=[ | |
25849 | @{addr="0x000013a0",data=["0x10","0x11","0x12","0x13"],ascii="xxxx"@}, | |
25850 | @{addr="0x000013a4",data=["0x14","0x15","0x16","0x17"],ascii="xxxx"@}, | |
25851 | @{addr="0x000013a8",data=["0x18","0x19","0x1a","0x1b"],ascii="xxxx"@}, | |
25852 | @{addr="0x000013ac",data=["0x1c","0x1d","0x1e","0x1f"],ascii="xxxx"@}, | |
25853 | @{addr="0x000013b0",data=["0x20","0x21","0x22","0x23"],ascii=" !\"#"@}, | |
25854 | @{addr="0x000013b4",data=["0x24","0x25","0x26","0x27"],ascii="$%&'"@}, | |
25855 | @{addr="0x000013b8",data=["0x28","0x29","0x2a","0x2b"],ascii="()*+"@}, | |
25856 | @{addr="0x000013bc",data=["0x2c","0x2d","0x2e","0x2f"],ascii=",-./"@}] | |
594fe323 | 25857 | (gdb) |
922fbb7b AC |
25858 | @end smallexample |
25859 | ||
a2c02241 NR |
25860 | @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% |
25861 | @node GDB/MI Tracepoint Commands | |
25862 | @section @sc{gdb/mi} Tracepoint Commands | |
922fbb7b | 25863 | |
a2c02241 | 25864 | The tracepoint commands are not yet implemented. |
922fbb7b | 25865 | |
a2c02241 | 25866 | @c @subheading -trace-actions |
922fbb7b | 25867 | |
a2c02241 | 25868 | @c @subheading -trace-delete |
922fbb7b | 25869 | |
a2c02241 | 25870 | @c @subheading -trace-disable |
922fbb7b | 25871 | |
a2c02241 | 25872 | @c @subheading -trace-dump |
922fbb7b | 25873 | |
a2c02241 | 25874 | @c @subheading -trace-enable |
922fbb7b | 25875 | |
a2c02241 | 25876 | @c @subheading -trace-exists |
922fbb7b | 25877 | |
a2c02241 | 25878 | @c @subheading -trace-find |
922fbb7b | 25879 | |
a2c02241 | 25880 | @c @subheading -trace-frame-number |
922fbb7b | 25881 | |
a2c02241 | 25882 | @c @subheading -trace-info |
922fbb7b | 25883 | |
a2c02241 | 25884 | @c @subheading -trace-insert |
922fbb7b | 25885 | |
a2c02241 | 25886 | @c @subheading -trace-list |
922fbb7b | 25887 | |
a2c02241 | 25888 | @c @subheading -trace-pass-count |
922fbb7b | 25889 | |
a2c02241 | 25890 | @c @subheading -trace-save |
922fbb7b | 25891 | |
a2c02241 | 25892 | @c @subheading -trace-start |
922fbb7b | 25893 | |
a2c02241 | 25894 | @c @subheading -trace-stop |
922fbb7b | 25895 | |
922fbb7b | 25896 | |
a2c02241 NR |
25897 | @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% |
25898 | @node GDB/MI Symbol Query | |
25899 | @section @sc{gdb/mi} Symbol Query Commands | |
922fbb7b AC |
25900 | |
25901 | ||
9901a55b | 25902 | @ignore |
a2c02241 NR |
25903 | @subheading The @code{-symbol-info-address} Command |
25904 | @findex -symbol-info-address | |
922fbb7b AC |
25905 | |
25906 | @subsubheading Synopsis | |
25907 | ||
25908 | @smallexample | |
a2c02241 | 25909 | -symbol-info-address @var{symbol} |
922fbb7b AC |
25910 | @end smallexample |
25911 | ||
a2c02241 | 25912 | Describe where @var{symbol} is stored. |
922fbb7b AC |
25913 | |
25914 | @subsubheading @value{GDBN} Command | |
25915 | ||
a2c02241 | 25916 | The corresponding @value{GDBN} command is @samp{info address}. |
922fbb7b AC |
25917 | |
25918 | @subsubheading Example | |
25919 | N.A. | |
25920 | ||
25921 | ||
a2c02241 NR |
25922 | @subheading The @code{-symbol-info-file} Command |
25923 | @findex -symbol-info-file | |
922fbb7b AC |
25924 | |
25925 | @subsubheading Synopsis | |
25926 | ||
25927 | @smallexample | |
a2c02241 | 25928 | -symbol-info-file |
922fbb7b AC |
25929 | @end smallexample |
25930 | ||
a2c02241 | 25931 | Show the file for the symbol. |
922fbb7b | 25932 | |
a2c02241 | 25933 | @subsubheading @value{GDBN} Command |
922fbb7b | 25934 | |
a2c02241 NR |
25935 | There's no equivalent @value{GDBN} command. @code{gdbtk} has |
25936 | @samp{gdb_find_file}. | |
922fbb7b AC |
25937 | |
25938 | @subsubheading Example | |
25939 | N.A. | |
25940 | ||
25941 | ||
a2c02241 NR |
25942 | @subheading The @code{-symbol-info-function} Command |
25943 | @findex -symbol-info-function | |
922fbb7b AC |
25944 | |
25945 | @subsubheading Synopsis | |
25946 | ||
25947 | @smallexample | |
a2c02241 | 25948 | -symbol-info-function |
922fbb7b AC |
25949 | @end smallexample |
25950 | ||
a2c02241 | 25951 | Show which function the symbol lives in. |
922fbb7b AC |
25952 | |
25953 | @subsubheading @value{GDBN} Command | |
25954 | ||
a2c02241 | 25955 | @samp{gdb_get_function} in @code{gdbtk}. |
922fbb7b AC |
25956 | |
25957 | @subsubheading Example | |
25958 | N.A. | |
25959 | ||
25960 | ||
a2c02241 NR |
25961 | @subheading The @code{-symbol-info-line} Command |
25962 | @findex -symbol-info-line | |
922fbb7b AC |
25963 | |
25964 | @subsubheading Synopsis | |
25965 | ||
25966 | @smallexample | |
a2c02241 | 25967 | -symbol-info-line |
922fbb7b AC |
25968 | @end smallexample |
25969 | ||
a2c02241 | 25970 | Show the core addresses of the code for a source line. |
922fbb7b | 25971 | |
a2c02241 | 25972 | @subsubheading @value{GDBN} Command |
922fbb7b | 25973 | |
a2c02241 NR |
25974 | The corresponding @value{GDBN} command is @samp{info line}. |
25975 | @code{gdbtk} has the @samp{gdb_get_line} and @samp{gdb_get_file} commands. | |
922fbb7b AC |
25976 | |
25977 | @subsubheading Example | |
a2c02241 | 25978 | N.A. |
922fbb7b AC |
25979 | |
25980 | ||
a2c02241 NR |
25981 | @subheading The @code{-symbol-info-symbol} Command |
25982 | @findex -symbol-info-symbol | |
07f31aa6 DJ |
25983 | |
25984 | @subsubheading Synopsis | |
25985 | ||
a2c02241 NR |
25986 | @smallexample |
25987 | -symbol-info-symbol @var{addr} | |
25988 | @end smallexample | |
07f31aa6 | 25989 | |
a2c02241 | 25990 | Describe what symbol is at location @var{addr}. |
07f31aa6 | 25991 | |
a2c02241 | 25992 | @subsubheading @value{GDBN} Command |
07f31aa6 | 25993 | |
a2c02241 | 25994 | The corresponding @value{GDBN} command is @samp{info symbol}. |
07f31aa6 DJ |
25995 | |
25996 | @subsubheading Example | |
a2c02241 | 25997 | N.A. |
07f31aa6 DJ |
25998 | |
25999 | ||
a2c02241 NR |
26000 | @subheading The @code{-symbol-list-functions} Command |
26001 | @findex -symbol-list-functions | |
922fbb7b AC |
26002 | |
26003 | @subsubheading Synopsis | |
26004 | ||
26005 | @smallexample | |
a2c02241 | 26006 | -symbol-list-functions |
922fbb7b AC |
26007 | @end smallexample |
26008 | ||
a2c02241 | 26009 | List the functions in the executable. |
922fbb7b AC |
26010 | |
26011 | @subsubheading @value{GDBN} Command | |
26012 | ||
a2c02241 NR |
26013 | @samp{info functions} in @value{GDBN}, @samp{gdb_listfunc} and |
26014 | @samp{gdb_search} in @code{gdbtk}. | |
922fbb7b AC |
26015 | |
26016 | @subsubheading Example | |
a2c02241 | 26017 | N.A. |
9901a55b | 26018 | @end ignore |
922fbb7b AC |
26019 | |
26020 | ||
a2c02241 NR |
26021 | @subheading The @code{-symbol-list-lines} Command |
26022 | @findex -symbol-list-lines | |
922fbb7b AC |
26023 | |
26024 | @subsubheading Synopsis | |
26025 | ||
26026 | @smallexample | |
a2c02241 | 26027 | -symbol-list-lines @var{filename} |
922fbb7b AC |
26028 | @end smallexample |
26029 | ||
a2c02241 NR |
26030 | Print the list of lines that contain code and their associated program |
26031 | addresses for the given source filename. The entries are sorted in | |
26032 | ascending PC order. | |
922fbb7b AC |
26033 | |
26034 | @subsubheading @value{GDBN} Command | |
26035 | ||
a2c02241 | 26036 | There is no corresponding @value{GDBN} command. |
922fbb7b AC |
26037 | |
26038 | @subsubheading Example | |
a2c02241 | 26039 | @smallexample |
594fe323 | 26040 | (gdb) |
a2c02241 NR |
26041 | -symbol-list-lines basics.c |
26042 | ^done,lines=[@{pc="0x08048554",line="7"@},@{pc="0x0804855a",line="8"@}] | |
594fe323 | 26043 | (gdb) |
a2c02241 | 26044 | @end smallexample |
922fbb7b AC |
26045 | |
26046 | ||
9901a55b | 26047 | @ignore |
a2c02241 NR |
26048 | @subheading The @code{-symbol-list-types} Command |
26049 | @findex -symbol-list-types | |
922fbb7b AC |
26050 | |
26051 | @subsubheading Synopsis | |
26052 | ||
26053 | @smallexample | |
a2c02241 | 26054 | -symbol-list-types |
922fbb7b AC |
26055 | @end smallexample |
26056 | ||
a2c02241 | 26057 | List all the type names. |
922fbb7b AC |
26058 | |
26059 | @subsubheading @value{GDBN} Command | |
26060 | ||
a2c02241 NR |
26061 | The corresponding commands are @samp{info types} in @value{GDBN}, |
26062 | @samp{gdb_search} in @code{gdbtk}. | |
922fbb7b AC |
26063 | |
26064 | @subsubheading Example | |
26065 | N.A. | |
26066 | ||
26067 | ||
a2c02241 NR |
26068 | @subheading The @code{-symbol-list-variables} Command |
26069 | @findex -symbol-list-variables | |
922fbb7b AC |
26070 | |
26071 | @subsubheading Synopsis | |
26072 | ||
26073 | @smallexample | |
a2c02241 | 26074 | -symbol-list-variables |
922fbb7b AC |
26075 | @end smallexample |
26076 | ||
a2c02241 | 26077 | List all the global and static variable names. |
922fbb7b AC |
26078 | |
26079 | @subsubheading @value{GDBN} Command | |
26080 | ||
a2c02241 | 26081 | @samp{info variables} in @value{GDBN}, @samp{gdb_search} in @code{gdbtk}. |
922fbb7b AC |
26082 | |
26083 | @subsubheading Example | |
26084 | N.A. | |
26085 | ||
26086 | ||
a2c02241 NR |
26087 | @subheading The @code{-symbol-locate} Command |
26088 | @findex -symbol-locate | |
922fbb7b AC |
26089 | |
26090 | @subsubheading Synopsis | |
26091 | ||
26092 | @smallexample | |
a2c02241 | 26093 | -symbol-locate |
922fbb7b AC |
26094 | @end smallexample |
26095 | ||
922fbb7b AC |
26096 | @subsubheading @value{GDBN} Command |
26097 | ||
a2c02241 | 26098 | @samp{gdb_loc} in @code{gdbtk}. |
922fbb7b AC |
26099 | |
26100 | @subsubheading Example | |
26101 | N.A. | |
26102 | ||
26103 | ||
a2c02241 NR |
26104 | @subheading The @code{-symbol-type} Command |
26105 | @findex -symbol-type | |
922fbb7b AC |
26106 | |
26107 | @subsubheading Synopsis | |
26108 | ||
26109 | @smallexample | |
a2c02241 | 26110 | -symbol-type @var{variable} |
922fbb7b AC |
26111 | @end smallexample |
26112 | ||
a2c02241 | 26113 | Show type of @var{variable}. |
922fbb7b | 26114 | |
a2c02241 | 26115 | @subsubheading @value{GDBN} Command |
922fbb7b | 26116 | |
a2c02241 NR |
26117 | The corresponding @value{GDBN} command is @samp{ptype}, @code{gdbtk} has |
26118 | @samp{gdb_obj_variable}. | |
26119 | ||
26120 | @subsubheading Example | |
26121 | N.A. | |
9901a55b | 26122 | @end ignore |
a2c02241 NR |
26123 | |
26124 | ||
26125 | @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% | |
26126 | @node GDB/MI File Commands | |
26127 | @section @sc{gdb/mi} File Commands | |
26128 | ||
26129 | This section describes the GDB/MI commands to specify executable file names | |
26130 | and to read in and obtain symbol table information. | |
26131 | ||
26132 | @subheading The @code{-file-exec-and-symbols} Command | |
26133 | @findex -file-exec-and-symbols | |
26134 | ||
26135 | @subsubheading Synopsis | |
922fbb7b AC |
26136 | |
26137 | @smallexample | |
a2c02241 | 26138 | -file-exec-and-symbols @var{file} |
922fbb7b AC |
26139 | @end smallexample |
26140 | ||
a2c02241 NR |
26141 | Specify the executable file to be debugged. This file is the one from |
26142 | which the symbol table is also read. If no file is specified, the | |
26143 | command clears the executable and symbol information. If breakpoints | |
26144 | are set when using this command with no arguments, @value{GDBN} will produce | |
26145 | error messages. Otherwise, no output is produced, except a completion | |
26146 | notification. | |
26147 | ||
922fbb7b AC |
26148 | @subsubheading @value{GDBN} Command |
26149 | ||
a2c02241 | 26150 | The corresponding @value{GDBN} command is @samp{file}. |
922fbb7b AC |
26151 | |
26152 | @subsubheading Example | |
26153 | ||
26154 | @smallexample | |
594fe323 | 26155 | (gdb) |
a2c02241 NR |
26156 | -file-exec-and-symbols /kwikemart/marge/ezannoni/TRUNK/mbx/hello.mbx |
26157 | ^done | |
594fe323 | 26158 | (gdb) |
922fbb7b AC |
26159 | @end smallexample |
26160 | ||
922fbb7b | 26161 | |
a2c02241 NR |
26162 | @subheading The @code{-file-exec-file} Command |
26163 | @findex -file-exec-file | |
922fbb7b AC |
26164 | |
26165 | @subsubheading Synopsis | |
26166 | ||
26167 | @smallexample | |
a2c02241 | 26168 | -file-exec-file @var{file} |
922fbb7b AC |
26169 | @end smallexample |
26170 | ||
a2c02241 NR |
26171 | Specify the executable file to be debugged. Unlike |
26172 | @samp{-file-exec-and-symbols}, the symbol table is @emph{not} read | |
26173 | from this file. If used without argument, @value{GDBN} clears the information | |
26174 | about the executable file. No output is produced, except a completion | |
26175 | notification. | |
922fbb7b | 26176 | |
a2c02241 NR |
26177 | @subsubheading @value{GDBN} Command |
26178 | ||
26179 | The corresponding @value{GDBN} command is @samp{exec-file}. | |
922fbb7b AC |
26180 | |
26181 | @subsubheading Example | |
a2c02241 NR |
26182 | |
26183 | @smallexample | |
594fe323 | 26184 | (gdb) |
a2c02241 NR |
26185 | -file-exec-file /kwikemart/marge/ezannoni/TRUNK/mbx/hello.mbx |
26186 | ^done | |
594fe323 | 26187 | (gdb) |
a2c02241 | 26188 | @end smallexample |
922fbb7b AC |
26189 | |
26190 | ||
9901a55b | 26191 | @ignore |
a2c02241 NR |
26192 | @subheading The @code{-file-list-exec-sections} Command |
26193 | @findex -file-list-exec-sections | |
922fbb7b AC |
26194 | |
26195 | @subsubheading Synopsis | |
26196 | ||
26197 | @smallexample | |
a2c02241 | 26198 | -file-list-exec-sections |
922fbb7b AC |
26199 | @end smallexample |
26200 | ||
a2c02241 NR |
26201 | List the sections of the current executable file. |
26202 | ||
922fbb7b AC |
26203 | @subsubheading @value{GDBN} Command |
26204 | ||
a2c02241 NR |
26205 | The @value{GDBN} command @samp{info file} shows, among the rest, the same |
26206 | information as this command. @code{gdbtk} has a corresponding command | |
26207 | @samp{gdb_load_info}. | |
922fbb7b AC |
26208 | |
26209 | @subsubheading Example | |
26210 | N.A. | |
9901a55b | 26211 | @end ignore |
922fbb7b AC |
26212 | |
26213 | ||
a2c02241 NR |
26214 | @subheading The @code{-file-list-exec-source-file} Command |
26215 | @findex -file-list-exec-source-file | |
922fbb7b AC |
26216 | |
26217 | @subsubheading Synopsis | |
26218 | ||
26219 | @smallexample | |
a2c02241 | 26220 | -file-list-exec-source-file |
922fbb7b AC |
26221 | @end smallexample |
26222 | ||
a2c02241 | 26223 | List the line number, the current source file, and the absolute path |
44288b44 NR |
26224 | to the current source file for the current executable. The macro |
26225 | information field has a value of @samp{1} or @samp{0} depending on | |
26226 | whether or not the file includes preprocessor macro information. | |
922fbb7b AC |
26227 | |
26228 | @subsubheading @value{GDBN} Command | |
26229 | ||
a2c02241 | 26230 | The @value{GDBN} equivalent is @samp{info source} |
922fbb7b AC |
26231 | |
26232 | @subsubheading Example | |
26233 | ||
922fbb7b | 26234 | @smallexample |
594fe323 | 26235 | (gdb) |
a2c02241 | 26236 | 123-file-list-exec-source-file |
44288b44 | 26237 | 123^done,line="1",file="foo.c",fullname="/home/bar/foo.c,macro-info="1" |
594fe323 | 26238 | (gdb) |
922fbb7b AC |
26239 | @end smallexample |
26240 | ||
26241 | ||
a2c02241 NR |
26242 | @subheading The @code{-file-list-exec-source-files} Command |
26243 | @findex -file-list-exec-source-files | |
922fbb7b AC |
26244 | |
26245 | @subsubheading Synopsis | |
26246 | ||
26247 | @smallexample | |
a2c02241 | 26248 | -file-list-exec-source-files |
922fbb7b AC |
26249 | @end smallexample |
26250 | ||
a2c02241 NR |
26251 | List the source files for the current executable. |
26252 | ||
3f94c067 BW |
26253 | It will always output the filename, but only when @value{GDBN} can find |
26254 | the absolute file name of a source file, will it output the fullname. | |
922fbb7b AC |
26255 | |
26256 | @subsubheading @value{GDBN} Command | |
26257 | ||
a2c02241 NR |
26258 | The @value{GDBN} equivalent is @samp{info sources}. |
26259 | @code{gdbtk} has an analogous command @samp{gdb_listfiles}. | |
922fbb7b AC |
26260 | |
26261 | @subsubheading Example | |
922fbb7b | 26262 | @smallexample |
594fe323 | 26263 | (gdb) |
a2c02241 NR |
26264 | -file-list-exec-source-files |
26265 | ^done,files=[ | |
26266 | @{file=foo.c,fullname=/home/foo.c@}, | |
26267 | @{file=/home/bar.c,fullname=/home/bar.c@}, | |
26268 | @{file=gdb_could_not_find_fullpath.c@}] | |
594fe323 | 26269 | (gdb) |
922fbb7b AC |
26270 | @end smallexample |
26271 | ||
9901a55b | 26272 | @ignore |
a2c02241 NR |
26273 | @subheading The @code{-file-list-shared-libraries} Command |
26274 | @findex -file-list-shared-libraries | |
922fbb7b | 26275 | |
a2c02241 | 26276 | @subsubheading Synopsis |
922fbb7b | 26277 | |
a2c02241 NR |
26278 | @smallexample |
26279 | -file-list-shared-libraries | |
26280 | @end smallexample | |
922fbb7b | 26281 | |
a2c02241 | 26282 | List the shared libraries in the program. |
922fbb7b | 26283 | |
a2c02241 | 26284 | @subsubheading @value{GDBN} Command |
922fbb7b | 26285 | |
a2c02241 | 26286 | The corresponding @value{GDBN} command is @samp{info shared}. |
922fbb7b | 26287 | |
a2c02241 NR |
26288 | @subsubheading Example |
26289 | N.A. | |
922fbb7b AC |
26290 | |
26291 | ||
a2c02241 NR |
26292 | @subheading The @code{-file-list-symbol-files} Command |
26293 | @findex -file-list-symbol-files | |
922fbb7b | 26294 | |
a2c02241 | 26295 | @subsubheading Synopsis |
922fbb7b | 26296 | |
a2c02241 NR |
26297 | @smallexample |
26298 | -file-list-symbol-files | |
26299 | @end smallexample | |
922fbb7b | 26300 | |
a2c02241 | 26301 | List symbol files. |
922fbb7b | 26302 | |
a2c02241 | 26303 | @subsubheading @value{GDBN} Command |
922fbb7b | 26304 | |
a2c02241 | 26305 | The corresponding @value{GDBN} command is @samp{info file} (part of it). |
922fbb7b | 26306 | |
a2c02241 NR |
26307 | @subsubheading Example |
26308 | N.A. | |
9901a55b | 26309 | @end ignore |
922fbb7b | 26310 | |
922fbb7b | 26311 | |
a2c02241 NR |
26312 | @subheading The @code{-file-symbol-file} Command |
26313 | @findex -file-symbol-file | |
922fbb7b | 26314 | |
a2c02241 | 26315 | @subsubheading Synopsis |
922fbb7b | 26316 | |
a2c02241 NR |
26317 | @smallexample |
26318 | -file-symbol-file @var{file} | |
26319 | @end smallexample | |
922fbb7b | 26320 | |
a2c02241 NR |
26321 | Read symbol table info from the specified @var{file} argument. When |
26322 | used without arguments, clears @value{GDBN}'s symbol table info. No output is | |
26323 | produced, except for a completion notification. | |
922fbb7b | 26324 | |
a2c02241 | 26325 | @subsubheading @value{GDBN} Command |
922fbb7b | 26326 | |
a2c02241 | 26327 | The corresponding @value{GDBN} command is @samp{symbol-file}. |
922fbb7b | 26328 | |
a2c02241 | 26329 | @subsubheading Example |
922fbb7b | 26330 | |
a2c02241 | 26331 | @smallexample |
594fe323 | 26332 | (gdb) |
a2c02241 NR |
26333 | -file-symbol-file /kwikemart/marge/ezannoni/TRUNK/mbx/hello.mbx |
26334 | ^done | |
594fe323 | 26335 | (gdb) |
a2c02241 | 26336 | @end smallexample |
922fbb7b | 26337 | |
a2c02241 | 26338 | @ignore |
a2c02241 NR |
26339 | @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% |
26340 | @node GDB/MI Memory Overlay Commands | |
26341 | @section @sc{gdb/mi} Memory Overlay Commands | |
922fbb7b | 26342 | |
a2c02241 | 26343 | The memory overlay commands are not implemented. |
922fbb7b | 26344 | |
a2c02241 | 26345 | @c @subheading -overlay-auto |
922fbb7b | 26346 | |
a2c02241 | 26347 | @c @subheading -overlay-list-mapping-state |
922fbb7b | 26348 | |
a2c02241 | 26349 | @c @subheading -overlay-list-overlays |
922fbb7b | 26350 | |
a2c02241 | 26351 | @c @subheading -overlay-map |
922fbb7b | 26352 | |
a2c02241 | 26353 | @c @subheading -overlay-off |
922fbb7b | 26354 | |
a2c02241 | 26355 | @c @subheading -overlay-on |
922fbb7b | 26356 | |
a2c02241 | 26357 | @c @subheading -overlay-unmap |
922fbb7b | 26358 | |
a2c02241 NR |
26359 | @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% |
26360 | @node GDB/MI Signal Handling Commands | |
26361 | @section @sc{gdb/mi} Signal Handling Commands | |
922fbb7b | 26362 | |
a2c02241 | 26363 | Signal handling commands are not implemented. |
922fbb7b | 26364 | |
a2c02241 | 26365 | @c @subheading -signal-handle |
922fbb7b | 26366 | |
a2c02241 | 26367 | @c @subheading -signal-list-handle-actions |
922fbb7b | 26368 | |
a2c02241 NR |
26369 | @c @subheading -signal-list-signal-types |
26370 | @end ignore | |
922fbb7b | 26371 | |
922fbb7b | 26372 | |
a2c02241 NR |
26373 | @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% |
26374 | @node GDB/MI Target Manipulation | |
26375 | @section @sc{gdb/mi} Target Manipulation Commands | |
922fbb7b AC |
26376 | |
26377 | ||
a2c02241 NR |
26378 | @subheading The @code{-target-attach} Command |
26379 | @findex -target-attach | |
922fbb7b AC |
26380 | |
26381 | @subsubheading Synopsis | |
26382 | ||
26383 | @smallexample | |
c3b108f7 | 26384 | -target-attach @var{pid} | @var{gid} | @var{file} |
922fbb7b AC |
26385 | @end smallexample |
26386 | ||
c3b108f7 VP |
26387 | Attach to a process @var{pid} or a file @var{file} outside of |
26388 | @value{GDBN}, or a thread group @var{gid}. If attaching to a thread | |
26389 | group, the id previously returned by | |
26390 | @samp{-list-thread-groups --available} must be used. | |
922fbb7b | 26391 | |
79a6e687 | 26392 | @subsubheading @value{GDBN} Command |
922fbb7b | 26393 | |
a2c02241 | 26394 | The corresponding @value{GDBN} command is @samp{attach}. |
922fbb7b | 26395 | |
a2c02241 | 26396 | @subsubheading Example |
b56e7235 VP |
26397 | @smallexample |
26398 | (gdb) | |
26399 | -target-attach 34 | |
26400 | =thread-created,id="1" | |
5ae4183a | 26401 | *stopped,thread-id="1",frame=@{addr="0xb7f7e410",func="bar",args=[]@} |
b56e7235 VP |
26402 | ^done |
26403 | (gdb) | |
26404 | @end smallexample | |
a2c02241 | 26405 | |
9901a55b | 26406 | @ignore |
a2c02241 NR |
26407 | @subheading The @code{-target-compare-sections} Command |
26408 | @findex -target-compare-sections | |
922fbb7b AC |
26409 | |
26410 | @subsubheading Synopsis | |
26411 | ||
26412 | @smallexample | |
a2c02241 | 26413 | -target-compare-sections [ @var{section} ] |
922fbb7b AC |
26414 | @end smallexample |
26415 | ||
a2c02241 NR |
26416 | Compare data of section @var{section} on target to the exec file. |
26417 | Without the argument, all sections are compared. | |
922fbb7b | 26418 | |
a2c02241 | 26419 | @subsubheading @value{GDBN} Command |
922fbb7b | 26420 | |
a2c02241 | 26421 | The @value{GDBN} equivalent is @samp{compare-sections}. |
922fbb7b | 26422 | |
a2c02241 NR |
26423 | @subsubheading Example |
26424 | N.A. | |
9901a55b | 26425 | @end ignore |
a2c02241 NR |
26426 | |
26427 | ||
26428 | @subheading The @code{-target-detach} Command | |
26429 | @findex -target-detach | |
922fbb7b AC |
26430 | |
26431 | @subsubheading Synopsis | |
26432 | ||
26433 | @smallexample | |
c3b108f7 | 26434 | -target-detach [ @var{pid} | @var{gid} ] |
922fbb7b AC |
26435 | @end smallexample |
26436 | ||
a2c02241 | 26437 | Detach from the remote target which normally resumes its execution. |
c3b108f7 VP |
26438 | If either @var{pid} or @var{gid} is specified, detaches from either |
26439 | the specified process, or specified thread group. There's no output. | |
a2c02241 | 26440 | |
79a6e687 | 26441 | @subsubheading @value{GDBN} Command |
a2c02241 NR |
26442 | |
26443 | The corresponding @value{GDBN} command is @samp{detach}. | |
26444 | ||
26445 | @subsubheading Example | |
922fbb7b AC |
26446 | |
26447 | @smallexample | |
594fe323 | 26448 | (gdb) |
a2c02241 NR |
26449 | -target-detach |
26450 | ^done | |
594fe323 | 26451 | (gdb) |
922fbb7b AC |
26452 | @end smallexample |
26453 | ||
26454 | ||
a2c02241 NR |
26455 | @subheading The @code{-target-disconnect} Command |
26456 | @findex -target-disconnect | |
922fbb7b AC |
26457 | |
26458 | @subsubheading Synopsis | |
26459 | ||
123dc839 | 26460 | @smallexample |
a2c02241 | 26461 | -target-disconnect |
123dc839 | 26462 | @end smallexample |
922fbb7b | 26463 | |
a2c02241 NR |
26464 | Disconnect from the remote target. There's no output and the target is |
26465 | generally not resumed. | |
26466 | ||
79a6e687 | 26467 | @subsubheading @value{GDBN} Command |
a2c02241 NR |
26468 | |
26469 | The corresponding @value{GDBN} command is @samp{disconnect}. | |
bc8ced35 NR |
26470 | |
26471 | @subsubheading Example | |
922fbb7b AC |
26472 | |
26473 | @smallexample | |
594fe323 | 26474 | (gdb) |
a2c02241 NR |
26475 | -target-disconnect |
26476 | ^done | |
594fe323 | 26477 | (gdb) |
922fbb7b AC |
26478 | @end smallexample |
26479 | ||
26480 | ||
a2c02241 NR |
26481 | @subheading The @code{-target-download} Command |
26482 | @findex -target-download | |
922fbb7b AC |
26483 | |
26484 | @subsubheading Synopsis | |
26485 | ||
26486 | @smallexample | |
a2c02241 | 26487 | -target-download |
922fbb7b AC |
26488 | @end smallexample |
26489 | ||
a2c02241 NR |
26490 | Loads the executable onto the remote target. |
26491 | It prints out an update message every half second, which includes the fields: | |
26492 | ||
26493 | @table @samp | |
26494 | @item section | |
26495 | The name of the section. | |
26496 | @item section-sent | |
26497 | The size of what has been sent so far for that section. | |
26498 | @item section-size | |
26499 | The size of the section. | |
26500 | @item total-sent | |
26501 | The total size of what was sent so far (the current and the previous sections). | |
26502 | @item total-size | |
26503 | The size of the overall executable to download. | |
26504 | @end table | |
26505 | ||
26506 | @noindent | |
26507 | Each message is sent as status record (@pxref{GDB/MI Output Syntax, , | |
26508 | @sc{gdb/mi} Output Syntax}). | |
26509 | ||
26510 | In addition, it prints the name and size of the sections, as they are | |
26511 | downloaded. These messages include the following fields: | |
26512 | ||
26513 | @table @samp | |
26514 | @item section | |
26515 | The name of the section. | |
26516 | @item section-size | |
26517 | The size of the section. | |
26518 | @item total-size | |
26519 | The size of the overall executable to download. | |
26520 | @end table | |
26521 | ||
26522 | @noindent | |
26523 | At the end, a summary is printed. | |
26524 | ||
26525 | @subsubheading @value{GDBN} Command | |
26526 | ||
26527 | The corresponding @value{GDBN} command is @samp{load}. | |
26528 | ||
26529 | @subsubheading Example | |
26530 | ||
26531 | Note: each status message appears on a single line. Here the messages | |
26532 | have been broken down so that they can fit onto a page. | |
922fbb7b AC |
26533 | |
26534 | @smallexample | |
594fe323 | 26535 | (gdb) |
a2c02241 NR |
26536 | -target-download |
26537 | +download,@{section=".text",section-size="6668",total-size="9880"@} | |
26538 | +download,@{section=".text",section-sent="512",section-size="6668", | |
26539 | total-sent="512",total-size="9880"@} | |
26540 | +download,@{section=".text",section-sent="1024",section-size="6668", | |
26541 | total-sent="1024",total-size="9880"@} | |
26542 | +download,@{section=".text",section-sent="1536",section-size="6668", | |
26543 | total-sent="1536",total-size="9880"@} | |
26544 | +download,@{section=".text",section-sent="2048",section-size="6668", | |
26545 | total-sent="2048",total-size="9880"@} | |
26546 | +download,@{section=".text",section-sent="2560",section-size="6668", | |
26547 | total-sent="2560",total-size="9880"@} | |
26548 | +download,@{section=".text",section-sent="3072",section-size="6668", | |
26549 | total-sent="3072",total-size="9880"@} | |
26550 | +download,@{section=".text",section-sent="3584",section-size="6668", | |
26551 | total-sent="3584",total-size="9880"@} | |
26552 | +download,@{section=".text",section-sent="4096",section-size="6668", | |
26553 | total-sent="4096",total-size="9880"@} | |
26554 | +download,@{section=".text",section-sent="4608",section-size="6668", | |
26555 | total-sent="4608",total-size="9880"@} | |
26556 | +download,@{section=".text",section-sent="5120",section-size="6668", | |
26557 | total-sent="5120",total-size="9880"@} | |
26558 | +download,@{section=".text",section-sent="5632",section-size="6668", | |
26559 | total-sent="5632",total-size="9880"@} | |
26560 | +download,@{section=".text",section-sent="6144",section-size="6668", | |
26561 | total-sent="6144",total-size="9880"@} | |
26562 | +download,@{section=".text",section-sent="6656",section-size="6668", | |
26563 | total-sent="6656",total-size="9880"@} | |
26564 | +download,@{section=".init",section-size="28",total-size="9880"@} | |
26565 | +download,@{section=".fini",section-size="28",total-size="9880"@} | |
26566 | +download,@{section=".data",section-size="3156",total-size="9880"@} | |
26567 | +download,@{section=".data",section-sent="512",section-size="3156", | |
26568 | total-sent="7236",total-size="9880"@} | |
26569 | +download,@{section=".data",section-sent="1024",section-size="3156", | |
26570 | total-sent="7748",total-size="9880"@} | |
26571 | +download,@{section=".data",section-sent="1536",section-size="3156", | |
26572 | total-sent="8260",total-size="9880"@} | |
26573 | +download,@{section=".data",section-sent="2048",section-size="3156", | |
26574 | total-sent="8772",total-size="9880"@} | |
26575 | +download,@{section=".data",section-sent="2560",section-size="3156", | |
26576 | total-sent="9284",total-size="9880"@} | |
26577 | +download,@{section=".data",section-sent="3072",section-size="3156", | |
26578 | total-sent="9796",total-size="9880"@} | |
26579 | ^done,address="0x10004",load-size="9880",transfer-rate="6586", | |
26580 | write-rate="429" | |
594fe323 | 26581 | (gdb) |
922fbb7b AC |
26582 | @end smallexample |
26583 | ||
26584 | ||
9901a55b | 26585 | @ignore |
a2c02241 NR |
26586 | @subheading The @code{-target-exec-status} Command |
26587 | @findex -target-exec-status | |
922fbb7b AC |
26588 | |
26589 | @subsubheading Synopsis | |
26590 | ||
26591 | @smallexample | |
a2c02241 | 26592 | -target-exec-status |
922fbb7b AC |
26593 | @end smallexample |
26594 | ||
a2c02241 NR |
26595 | Provide information on the state of the target (whether it is running or |
26596 | not, for instance). | |
922fbb7b | 26597 | |
a2c02241 | 26598 | @subsubheading @value{GDBN} Command |
922fbb7b | 26599 | |
a2c02241 NR |
26600 | There's no equivalent @value{GDBN} command. |
26601 | ||
26602 | @subsubheading Example | |
26603 | N.A. | |
922fbb7b | 26604 | |
a2c02241 NR |
26605 | |
26606 | @subheading The @code{-target-list-available-targets} Command | |
26607 | @findex -target-list-available-targets | |
922fbb7b AC |
26608 | |
26609 | @subsubheading Synopsis | |
26610 | ||
26611 | @smallexample | |
a2c02241 | 26612 | -target-list-available-targets |
922fbb7b AC |
26613 | @end smallexample |
26614 | ||
a2c02241 | 26615 | List the possible targets to connect to. |
922fbb7b | 26616 | |
a2c02241 | 26617 | @subsubheading @value{GDBN} Command |
922fbb7b | 26618 | |
a2c02241 | 26619 | The corresponding @value{GDBN} command is @samp{help target}. |
922fbb7b | 26620 | |
a2c02241 NR |
26621 | @subsubheading Example |
26622 | N.A. | |
26623 | ||
26624 | ||
26625 | @subheading The @code{-target-list-current-targets} Command | |
26626 | @findex -target-list-current-targets | |
922fbb7b AC |
26627 | |
26628 | @subsubheading Synopsis | |
26629 | ||
26630 | @smallexample | |
a2c02241 | 26631 | -target-list-current-targets |
922fbb7b AC |
26632 | @end smallexample |
26633 | ||
a2c02241 | 26634 | Describe the current target. |
922fbb7b | 26635 | |
a2c02241 | 26636 | @subsubheading @value{GDBN} Command |
922fbb7b | 26637 | |
a2c02241 NR |
26638 | The corresponding information is printed by @samp{info file} (among |
26639 | other things). | |
922fbb7b | 26640 | |
a2c02241 NR |
26641 | @subsubheading Example |
26642 | N.A. | |
26643 | ||
26644 | ||
26645 | @subheading The @code{-target-list-parameters} Command | |
26646 | @findex -target-list-parameters | |
922fbb7b AC |
26647 | |
26648 | @subsubheading Synopsis | |
26649 | ||
26650 | @smallexample | |
a2c02241 | 26651 | -target-list-parameters |
922fbb7b AC |
26652 | @end smallexample |
26653 | ||
a2c02241 | 26654 | @c ???? |
9901a55b | 26655 | @end ignore |
a2c02241 NR |
26656 | |
26657 | @subsubheading @value{GDBN} Command | |
26658 | ||
26659 | No equivalent. | |
922fbb7b AC |
26660 | |
26661 | @subsubheading Example | |
a2c02241 NR |
26662 | N.A. |
26663 | ||
26664 | ||
26665 | @subheading The @code{-target-select} Command | |
26666 | @findex -target-select | |
26667 | ||
26668 | @subsubheading Synopsis | |
922fbb7b AC |
26669 | |
26670 | @smallexample | |
a2c02241 | 26671 | -target-select @var{type} @var{parameters @dots{}} |
922fbb7b AC |
26672 | @end smallexample |
26673 | ||
a2c02241 | 26674 | Connect @value{GDBN} to the remote target. This command takes two args: |
922fbb7b | 26675 | |
a2c02241 NR |
26676 | @table @samp |
26677 | @item @var{type} | |
75c99385 | 26678 | The type of target, for instance @samp{remote}, etc. |
a2c02241 NR |
26679 | @item @var{parameters} |
26680 | Device names, host names and the like. @xref{Target Commands, , | |
79a6e687 | 26681 | Commands for Managing Targets}, for more details. |
a2c02241 NR |
26682 | @end table |
26683 | ||
26684 | The output is a connection notification, followed by the address at | |
26685 | which the target program is, in the following form: | |
922fbb7b AC |
26686 | |
26687 | @smallexample | |
a2c02241 NR |
26688 | ^connected,addr="@var{address}",func="@var{function name}", |
26689 | args=[@var{arg list}] | |
922fbb7b AC |
26690 | @end smallexample |
26691 | ||
a2c02241 NR |
26692 | @subsubheading @value{GDBN} Command |
26693 | ||
26694 | The corresponding @value{GDBN} command is @samp{target}. | |
265eeb58 NR |
26695 | |
26696 | @subsubheading Example | |
922fbb7b | 26697 | |
265eeb58 | 26698 | @smallexample |
594fe323 | 26699 | (gdb) |
75c99385 | 26700 | -target-select remote /dev/ttya |
a2c02241 | 26701 | ^connected,addr="0xfe00a300",func="??",args=[] |
594fe323 | 26702 | (gdb) |
265eeb58 | 26703 | @end smallexample |
ef21caaf | 26704 | |
a6b151f1 DJ |
26705 | @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% |
26706 | @node GDB/MI File Transfer Commands | |
26707 | @section @sc{gdb/mi} File Transfer Commands | |
26708 | ||
26709 | ||
26710 | @subheading The @code{-target-file-put} Command | |
26711 | @findex -target-file-put | |
26712 | ||
26713 | @subsubheading Synopsis | |
26714 | ||
26715 | @smallexample | |
26716 | -target-file-put @var{hostfile} @var{targetfile} | |
26717 | @end smallexample | |
26718 | ||
26719 | Copy file @var{hostfile} from the host system (the machine running | |
26720 | @value{GDBN}) to @var{targetfile} on the target system. | |
26721 | ||
26722 | @subsubheading @value{GDBN} Command | |
26723 | ||
26724 | The corresponding @value{GDBN} command is @samp{remote put}. | |
26725 | ||
26726 | @subsubheading Example | |
26727 | ||
26728 | @smallexample | |
26729 | (gdb) | |
26730 | -target-file-put localfile remotefile | |
26731 | ^done | |
26732 | (gdb) | |
26733 | @end smallexample | |
26734 | ||
26735 | ||
1763a388 | 26736 | @subheading The @code{-target-file-get} Command |
a6b151f1 DJ |
26737 | @findex -target-file-get |
26738 | ||
26739 | @subsubheading Synopsis | |
26740 | ||
26741 | @smallexample | |
26742 | -target-file-get @var{targetfile} @var{hostfile} | |
26743 | @end smallexample | |
26744 | ||
26745 | Copy file @var{targetfile} from the target system to @var{hostfile} | |
26746 | on the host system. | |
26747 | ||
26748 | @subsubheading @value{GDBN} Command | |
26749 | ||
26750 | The corresponding @value{GDBN} command is @samp{remote get}. | |
26751 | ||
26752 | @subsubheading Example | |
26753 | ||
26754 | @smallexample | |
26755 | (gdb) | |
26756 | -target-file-get remotefile localfile | |
26757 | ^done | |
26758 | (gdb) | |
26759 | @end smallexample | |
26760 | ||
26761 | ||
26762 | @subheading The @code{-target-file-delete} Command | |
26763 | @findex -target-file-delete | |
26764 | ||
26765 | @subsubheading Synopsis | |
26766 | ||
26767 | @smallexample | |
26768 | -target-file-delete @var{targetfile} | |
26769 | @end smallexample | |
26770 | ||
26771 | Delete @var{targetfile} from the target system. | |
26772 | ||
26773 | @subsubheading @value{GDBN} Command | |
26774 | ||
26775 | The corresponding @value{GDBN} command is @samp{remote delete}. | |
26776 | ||
26777 | @subsubheading Example | |
26778 | ||
26779 | @smallexample | |
26780 | (gdb) | |
26781 | -target-file-delete remotefile | |
26782 | ^done | |
26783 | (gdb) | |
26784 | @end smallexample | |
26785 | ||
26786 | ||
ef21caaf NR |
26787 | @c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% |
26788 | @node GDB/MI Miscellaneous Commands | |
26789 | @section Miscellaneous @sc{gdb/mi} Commands | |
26790 | ||
26791 | @c @subheading -gdb-complete | |
26792 | ||
26793 | @subheading The @code{-gdb-exit} Command | |
26794 | @findex -gdb-exit | |
26795 | ||
26796 | @subsubheading Synopsis | |
26797 | ||
26798 | @smallexample | |
26799 | -gdb-exit | |
26800 | @end smallexample | |
26801 | ||
26802 | Exit @value{GDBN} immediately. | |
26803 | ||
26804 | @subsubheading @value{GDBN} Command | |
26805 | ||
26806 | Approximately corresponds to @samp{quit}. | |
26807 | ||
26808 | @subsubheading Example | |
26809 | ||
26810 | @smallexample | |
594fe323 | 26811 | (gdb) |
ef21caaf NR |
26812 | -gdb-exit |
26813 | ^exit | |
26814 | @end smallexample | |
26815 | ||
a2c02241 | 26816 | |
9901a55b | 26817 | @ignore |
a2c02241 NR |
26818 | @subheading The @code{-exec-abort} Command |
26819 | @findex -exec-abort | |
26820 | ||
26821 | @subsubheading Synopsis | |
26822 | ||
26823 | @smallexample | |
26824 | -exec-abort | |
26825 | @end smallexample | |
26826 | ||
26827 | Kill the inferior running program. | |
26828 | ||
26829 | @subsubheading @value{GDBN} Command | |
26830 | ||
26831 | The corresponding @value{GDBN} command is @samp{kill}. | |
26832 | ||
26833 | @subsubheading Example | |
26834 | N.A. | |
9901a55b | 26835 | @end ignore |
a2c02241 NR |
26836 | |
26837 | ||
ef21caaf NR |
26838 | @subheading The @code{-gdb-set} Command |
26839 | @findex -gdb-set | |
26840 | ||
26841 | @subsubheading Synopsis | |
26842 | ||
26843 | @smallexample | |
26844 | -gdb-set | |
26845 | @end smallexample | |
26846 | ||
26847 | Set an internal @value{GDBN} variable. | |
26848 | @c IS THIS A DOLLAR VARIABLE? OR SOMETHING LIKE ANNOTATE ????? | |
26849 | ||
26850 | @subsubheading @value{GDBN} Command | |
26851 | ||
26852 | The corresponding @value{GDBN} command is @samp{set}. | |
26853 | ||
26854 | @subsubheading Example | |
26855 | ||
26856 | @smallexample | |
594fe323 | 26857 | (gdb) |
ef21caaf NR |
26858 | -gdb-set $foo=3 |
26859 | ^done | |
594fe323 | 26860 | (gdb) |
ef21caaf NR |
26861 | @end smallexample |
26862 | ||
26863 | ||
26864 | @subheading The @code{-gdb-show} Command | |
26865 | @findex -gdb-show | |
26866 | ||
26867 | @subsubheading Synopsis | |
26868 | ||
26869 | @smallexample | |
26870 | -gdb-show | |
26871 | @end smallexample | |
26872 | ||
26873 | Show the current value of a @value{GDBN} variable. | |
26874 | ||
79a6e687 | 26875 | @subsubheading @value{GDBN} Command |
ef21caaf NR |
26876 | |
26877 | The corresponding @value{GDBN} command is @samp{show}. | |
26878 | ||
26879 | @subsubheading Example | |
26880 | ||
26881 | @smallexample | |
594fe323 | 26882 | (gdb) |
ef21caaf NR |
26883 | -gdb-show annotate |
26884 | ^done,value="0" | |
594fe323 | 26885 | (gdb) |
ef21caaf NR |
26886 | @end smallexample |
26887 | ||
26888 | @c @subheading -gdb-source | |
26889 | ||
26890 | ||
26891 | @subheading The @code{-gdb-version} Command | |
26892 | @findex -gdb-version | |
26893 | ||
26894 | @subsubheading Synopsis | |
26895 | ||
26896 | @smallexample | |
26897 | -gdb-version | |
26898 | @end smallexample | |
26899 | ||
26900 | Show version information for @value{GDBN}. Used mostly in testing. | |
26901 | ||
26902 | @subsubheading @value{GDBN} Command | |
26903 | ||
26904 | The @value{GDBN} equivalent is @samp{show version}. @value{GDBN} by | |
26905 | default shows this information when you start an interactive session. | |
26906 | ||
26907 | @subsubheading Example | |
26908 | ||
26909 | @c This example modifies the actual output from GDB to avoid overfull | |
26910 | @c box in TeX. | |
26911 | @smallexample | |
594fe323 | 26912 | (gdb) |
ef21caaf NR |
26913 | -gdb-version |
26914 | ~GNU gdb 5.2.1 | |
26915 | ~Copyright 2000 Free Software Foundation, Inc. | |
26916 | ~GDB is free software, covered by the GNU General Public License, and | |
26917 | ~you are welcome to change it and/or distribute copies of it under | |
26918 | ~ certain conditions. | |
26919 | ~Type "show copying" to see the conditions. | |
26920 | ~There is absolutely no warranty for GDB. Type "show warranty" for | |
26921 | ~ details. | |
26922 | ~This GDB was configured as | |
26923 | "--host=sparc-sun-solaris2.5.1 --target=ppc-eabi". | |
26924 | ^done | |
594fe323 | 26925 | (gdb) |
ef21caaf NR |
26926 | @end smallexample |
26927 | ||
084344da VP |
26928 | @subheading The @code{-list-features} Command |
26929 | @findex -list-features | |
26930 | ||
26931 | Returns a list of particular features of the MI protocol that | |
26932 | this version of gdb implements. A feature can be a command, | |
26933 | or a new field in an output of some command, or even an | |
26934 | important bugfix. While a frontend can sometimes detect presence | |
26935 | of a feature at runtime, it is easier to perform detection at debugger | |
26936 | startup. | |
26937 | ||
26938 | The command returns a list of strings, with each string naming an | |
26939 | available feature. Each returned string is just a name, it does not | |
26940 | have any internal structure. The list of possible feature names | |
26941 | is given below. | |
26942 | ||
26943 | Example output: | |
26944 | ||
26945 | @smallexample | |
26946 | (gdb) -list-features | |
26947 | ^done,result=["feature1","feature2"] | |
26948 | @end smallexample | |
26949 | ||
26950 | The current list of features is: | |
26951 | ||
30e026bb VP |
26952 | @table @samp |
26953 | @item frozen-varobjs | |
26954 | Indicates presence of the @code{-var-set-frozen} command, as well | |
26955 | as possible presense of the @code{frozen} field in the output | |
26956 | of @code{-varobj-create}. | |
26957 | @item pending-breakpoints | |
26958 | Indicates presence of the @option{-f} option to the @code{-break-insert} command. | |
b6313243 TT |
26959 | @item python |
26960 | Indicates presence of Python scripting support, Python-based | |
26961 | pretty-printing commands, and possible presence of the | |
26962 | @samp{display_hint} field in the output of @code{-var-list-children} | |
30e026bb VP |
26963 | @item thread-info |
26964 | Indicates presence of the @code{-thread-info} command. | |
8b4ed427 | 26965 | |
30e026bb | 26966 | @end table |
084344da | 26967 | |
c6ebd6cf VP |
26968 | @subheading The @code{-list-target-features} Command |
26969 | @findex -list-target-features | |
26970 | ||
26971 | Returns a list of particular features that are supported by the | |
26972 | target. Those features affect the permitted MI commands, but | |
26973 | unlike the features reported by the @code{-list-features} command, the | |
26974 | features depend on which target GDB is using at the moment. Whenever | |
26975 | a target can change, due to commands such as @code{-target-select}, | |
26976 | @code{-target-attach} or @code{-exec-run}, the list of target features | |
26977 | may change, and the frontend should obtain it again. | |
26978 | Example output: | |
26979 | ||
26980 | @smallexample | |
26981 | (gdb) -list-features | |
26982 | ^done,result=["async"] | |
26983 | @end smallexample | |
26984 | ||
26985 | The current list of features is: | |
26986 | ||
26987 | @table @samp | |
26988 | @item async | |
26989 | Indicates that the target is capable of asynchronous command | |
26990 | execution, which means that @value{GDBN} will accept further commands | |
26991 | while the target is running. | |
26992 | ||
26993 | @end table | |
26994 | ||
c3b108f7 VP |
26995 | @subheading The @code{-list-thread-groups} Command |
26996 | @findex -list-thread-groups | |
26997 | ||
26998 | @subheading Synopsis | |
26999 | ||
27000 | @smallexample | |
dc146f7c | 27001 | -list-thread-groups [ --available ] [ --recurse 1 ] [ @var{group} ... ] |
c3b108f7 VP |
27002 | @end smallexample |
27003 | ||
dc146f7c VP |
27004 | Lists thread groups (@pxref{Thread groups}). When a single thread |
27005 | group is passed as the argument, lists the children of that group. | |
27006 | When several thread group are passed, lists information about those | |
27007 | thread groups. Without any parameters, lists information about all | |
27008 | top-level thread groups. | |
27009 | ||
27010 | Normally, thread groups that are being debugged are reported. | |
27011 | With the @samp{--available} option, @value{GDBN} reports thread groups | |
27012 | available on the target. | |
27013 | ||
27014 | The output of this command may have either a @samp{threads} result or | |
27015 | a @samp{groups} result. The @samp{thread} result has a list of tuples | |
27016 | as value, with each tuple describing a thread (@pxref{GDB/MI Thread | |
27017 | Information}). The @samp{groups} result has a list of tuples as value, | |
27018 | each tuple describing a thread group. If top-level groups are | |
27019 | requested (that is, no parameter is passed), or when several groups | |
27020 | are passed, the output always has a @samp{groups} result. The format | |
27021 | of the @samp{group} result is described below. | |
27022 | ||
27023 | To reduce the number of roundtrips it's possible to list thread groups | |
27024 | together with their children, by passing the @samp{--recurse} option | |
27025 | and the recursion depth. Presently, only recursion depth of 1 is | |
27026 | permitted. If this option is present, then every reported thread group | |
27027 | will also include its children, either as @samp{group} or | |
27028 | @samp{threads} field. | |
27029 | ||
27030 | In general, any combination of option and parameters is permitted, with | |
27031 | the following caveats: | |
27032 | ||
27033 | @itemize @bullet | |
27034 | @item | |
27035 | When a single thread group is passed, the output will typically | |
27036 | be the @samp{threads} result. Because threads may not contain | |
27037 | anything, the @samp{recurse} option will be ignored. | |
27038 | ||
27039 | @item | |
27040 | When the @samp{--available} option is passed, limited information may | |
27041 | be available. In particular, the list of threads of a process might | |
27042 | be inaccessible. Further, specifying specific thread groups might | |
27043 | not give any performance advantage over listing all thread groups. | |
27044 | The frontend should assume that @samp{-list-thread-groups --available} | |
27045 | is always an expensive operation and cache the results. | |
27046 | ||
27047 | @end itemize | |
27048 | ||
27049 | The @samp{groups} result is a list of tuples, where each tuple may | |
27050 | have the following fields: | |
27051 | ||
27052 | @table @code | |
27053 | @item id | |
27054 | Identifier of the thread group. This field is always present. | |
a79b8f6e VP |
27055 | The identifier is an opaque string; frontends should not try to |
27056 | convert it to an integer, even though it might look like one. | |
dc146f7c VP |
27057 | |
27058 | @item type | |
27059 | The type of the thread group. At present, only @samp{process} is a | |
27060 | valid type. | |
27061 | ||
27062 | @item pid | |
27063 | The target-specific process identifier. This field is only present | |
a79b8f6e | 27064 | for thread groups of type @samp{process} and only if the process exists. |
c3b108f7 | 27065 | |
dc146f7c VP |
27066 | @item num_children |
27067 | The number of children this thread group has. This field may be | |
27068 | absent for an available thread group. | |
27069 | ||
27070 | @item threads | |
27071 | This field has a list of tuples as value, each tuple describing a | |
27072 | thread. It may be present if the @samp{--recurse} option is | |
27073 | specified, and it's actually possible to obtain the threads. | |
27074 | ||
27075 | @item cores | |
27076 | This field is a list of integers, each identifying a core that one | |
27077 | thread of the group is running on. This field may be absent if | |
27078 | such information is not available. | |
27079 | ||
a79b8f6e VP |
27080 | @item executable |
27081 | The name of the executable file that corresponds to this thread group. | |
27082 | The field is only present for thread groups of type @samp{process}, | |
27083 | and only if there is a corresponding executable file. | |
27084 | ||
dc146f7c | 27085 | @end table |
c3b108f7 VP |
27086 | |
27087 | @subheading Example | |
27088 | ||
27089 | @smallexample | |
27090 | @value{GDBP} | |
27091 | -list-thread-groups | |
27092 | ^done,groups=[@{id="17",type="process",pid="yyy",num_children="2"@}] | |
27093 | -list-thread-groups 17 | |
27094 | ^done,threads=[@{id="2",target-id="Thread 0xb7e14b90 (LWP 21257)", | |
27095 | frame=@{level="0",addr="0xffffe410",func="__kernel_vsyscall",args=[]@},state="running"@}, | |
27096 | @{id="1",target-id="Thread 0xb7e156b0 (LWP 21254)", | |
27097 | frame=@{level="0",addr="0x0804891f",func="foo",args=[@{name="i",value="10"@}], | |
27098 | file="/tmp/a.c",fullname="/tmp/a.c",line="158"@},state="running"@}]] | |
dc146f7c VP |
27099 | -list-thread-groups --available |
27100 | ^done,groups=[@{id="17",type="process",pid="yyy",num_children="2",cores=[1,2]@}] | |
27101 | -list-thread-groups --available --recurse 1 | |
27102 | ^done,groups=[@{id="17", types="process",pid="yyy",num_children="2",cores=[1,2], | |
27103 | threads=[@{id="1",target-id="Thread 0xb7e14b90",cores=[1]@}, | |
27104 | @{id="2",target-id="Thread 0xb7e14b90",cores=[2]@}]@},..] | |
27105 | -list-thread-groups --available --recurse 1 17 18 | |
27106 | ^done,groups=[@{id="17", types="process",pid="yyy",num_children="2",cores=[1,2], | |
27107 | threads=[@{id="1",target-id="Thread 0xb7e14b90",cores=[1]@}, | |
27108 | @{id="2",target-id="Thread 0xb7e14b90",cores=[2]@}]@},...] | |
c3b108f7 | 27109 | @end smallexample |
c6ebd6cf | 27110 | |
a79b8f6e VP |
27111 | |
27112 | @subheading The @code{-add-inferior} Command | |
27113 | @findex -add-inferior | |
27114 | ||
27115 | @subheading Synopsis | |
27116 | ||
27117 | @smallexample | |
27118 | -add-inferior | |
27119 | @end smallexample | |
27120 | ||
27121 | Creates a new inferior (@pxref{Inferiors and Programs}). The created | |
27122 | inferior is not associated with any executable. Such association may | |
27123 | be established with the @samp{-file-exec-and-symbols} command | |
27124 | (@pxref{GDB/MI File Commands}). The command response has a single | |
27125 | field, @samp{thread-group}, whose value is the identifier of the | |
27126 | thread group corresponding to the new inferior. | |
27127 | ||
27128 | @subheading Example | |
27129 | ||
27130 | @smallexample | |
27131 | @value{GDBP} | |
27132 | -add-inferior | |
27133 | ^done,thread-group="i3" | |
27134 | @end smallexample | |
27135 | ||
ef21caaf NR |
27136 | @subheading The @code{-interpreter-exec} Command |
27137 | @findex -interpreter-exec | |
27138 | ||
27139 | @subheading Synopsis | |
27140 | ||
27141 | @smallexample | |
27142 | -interpreter-exec @var{interpreter} @var{command} | |
27143 | @end smallexample | |
a2c02241 | 27144 | @anchor{-interpreter-exec} |
ef21caaf NR |
27145 | |
27146 | Execute the specified @var{command} in the given @var{interpreter}. | |
27147 | ||
27148 | @subheading @value{GDBN} Command | |
27149 | ||
27150 | The corresponding @value{GDBN} command is @samp{interpreter-exec}. | |
27151 | ||
27152 | @subheading Example | |
27153 | ||
27154 | @smallexample | |
594fe323 | 27155 | (gdb) |
ef21caaf NR |
27156 | -interpreter-exec console "break main" |
27157 | &"During symbol reading, couldn't parse type; debugger out of date?.\n" | |
27158 | &"During symbol reading, bad structure-type format.\n" | |
27159 | ~"Breakpoint 1 at 0x8074fc6: file ../../src/gdb/main.c, line 743.\n" | |
27160 | ^done | |
594fe323 | 27161 | (gdb) |
ef21caaf NR |
27162 | @end smallexample |
27163 | ||
27164 | @subheading The @code{-inferior-tty-set} Command | |
27165 | @findex -inferior-tty-set | |
27166 | ||
27167 | @subheading Synopsis | |
27168 | ||
27169 | @smallexample | |
27170 | -inferior-tty-set /dev/pts/1 | |
27171 | @end smallexample | |
27172 | ||
27173 | Set terminal for future runs of the program being debugged. | |
27174 | ||
27175 | @subheading @value{GDBN} Command | |
27176 | ||
27177 | The corresponding @value{GDBN} command is @samp{set inferior-tty} /dev/pts/1. | |
27178 | ||
27179 | @subheading Example | |
27180 | ||
27181 | @smallexample | |
594fe323 | 27182 | (gdb) |
ef21caaf NR |
27183 | -inferior-tty-set /dev/pts/1 |
27184 | ^done | |
594fe323 | 27185 | (gdb) |
ef21caaf NR |
27186 | @end smallexample |
27187 | ||
27188 | @subheading The @code{-inferior-tty-show} Command | |
27189 | @findex -inferior-tty-show | |
27190 | ||
27191 | @subheading Synopsis | |
27192 | ||
27193 | @smallexample | |
27194 | -inferior-tty-show | |
27195 | @end smallexample | |
27196 | ||
27197 | Show terminal for future runs of program being debugged. | |
27198 | ||
27199 | @subheading @value{GDBN} Command | |
27200 | ||
27201 | The corresponding @value{GDBN} command is @samp{show inferior-tty}. | |
27202 | ||
27203 | @subheading Example | |
27204 | ||
27205 | @smallexample | |
594fe323 | 27206 | (gdb) |
ef21caaf NR |
27207 | -inferior-tty-set /dev/pts/1 |
27208 | ^done | |
594fe323 | 27209 | (gdb) |
ef21caaf NR |
27210 | -inferior-tty-show |
27211 | ^done,inferior_tty_terminal="/dev/pts/1" | |
594fe323 | 27212 | (gdb) |
ef21caaf | 27213 | @end smallexample |
922fbb7b | 27214 | |
a4eefcd8 NR |
27215 | @subheading The @code{-enable-timings} Command |
27216 | @findex -enable-timings | |
27217 | ||
27218 | @subheading Synopsis | |
27219 | ||
27220 | @smallexample | |
27221 | -enable-timings [yes | no] | |
27222 | @end smallexample | |
27223 | ||
27224 | Toggle the printing of the wallclock, user and system times for an MI | |
27225 | command as a field in its output. This command is to help frontend | |
27226 | developers optimize the performance of their code. No argument is | |
27227 | equivalent to @samp{yes}. | |
27228 | ||
27229 | @subheading @value{GDBN} Command | |
27230 | ||
27231 | No equivalent. | |
27232 | ||
27233 | @subheading Example | |
27234 | ||
27235 | @smallexample | |
27236 | (gdb) | |
27237 | -enable-timings | |
27238 | ^done | |
27239 | (gdb) | |
27240 | -break-insert main | |
27241 | ^done,bkpt=@{number="1",type="breakpoint",disp="keep",enabled="y", | |
27242 | addr="0x080484ed",func="main",file="myprog.c", | |
27243 | fullname="/home/nickrob/myprog.c",line="73",times="0"@}, | |
27244 | time=@{wallclock="0.05185",user="0.00800",system="0.00000"@} | |
27245 | (gdb) | |
27246 | -enable-timings no | |
27247 | ^done | |
27248 | (gdb) | |
27249 | -exec-run | |
27250 | ^running | |
27251 | (gdb) | |
a47ec5fe | 27252 | *stopped,reason="breakpoint-hit",disp="keep",bkptno="1",thread-id="0", |
a4eefcd8 NR |
27253 | frame=@{addr="0x080484ed",func="main",args=[@{name="argc",value="1"@}, |
27254 | @{name="argv",value="0xbfb60364"@}],file="myprog.c", | |
27255 | fullname="/home/nickrob/myprog.c",line="73"@} | |
27256 | (gdb) | |
27257 | @end smallexample | |
27258 | ||
922fbb7b AC |
27259 | @node Annotations |
27260 | @chapter @value{GDBN} Annotations | |
27261 | ||
086432e2 AC |
27262 | This chapter describes annotations in @value{GDBN}. Annotations were |
27263 | designed to interface @value{GDBN} to graphical user interfaces or other | |
27264 | similar programs which want to interact with @value{GDBN} at a | |
922fbb7b AC |
27265 | relatively high level. |
27266 | ||
d3e8051b | 27267 | The annotation mechanism has largely been superseded by @sc{gdb/mi} |
086432e2 AC |
27268 | (@pxref{GDB/MI}). |
27269 | ||
922fbb7b AC |
27270 | @ignore |
27271 | This is Edition @value{EDITION}, @value{DATE}. | |
27272 | @end ignore | |
27273 | ||
27274 | @menu | |
27275 | * Annotations Overview:: What annotations are; the general syntax. | |
9e6c4bd5 | 27276 | * Server Prefix:: Issuing a command without affecting user state. |
922fbb7b AC |
27277 | * Prompting:: Annotations marking @value{GDBN}'s need for input. |
27278 | * Errors:: Annotations for error messages. | |
922fbb7b AC |
27279 | * Invalidation:: Some annotations describe things now invalid. |
27280 | * Annotations for Running:: | |
27281 | Whether the program is running, how it stopped, etc. | |
27282 | * Source Annotations:: Annotations describing source code. | |
922fbb7b AC |
27283 | @end menu |
27284 | ||
27285 | @node Annotations Overview | |
27286 | @section What is an Annotation? | |
27287 | @cindex annotations | |
27288 | ||
922fbb7b AC |
27289 | Annotations start with a newline character, two @samp{control-z} |
27290 | characters, and the name of the annotation. If there is no additional | |
27291 | information associated with this annotation, the name of the annotation | |
27292 | is followed immediately by a newline. If there is additional | |
27293 | information, the name of the annotation is followed by a space, the | |
27294 | additional information, and a newline. The additional information | |
27295 | cannot contain newline characters. | |
27296 | ||
27297 | Any output not beginning with a newline and two @samp{control-z} | |
27298 | characters denotes literal output from @value{GDBN}. Currently there is | |
27299 | no need for @value{GDBN} to output a newline followed by two | |
27300 | @samp{control-z} characters, but if there was such a need, the | |
27301 | annotations could be extended with an @samp{escape} annotation which | |
27302 | means those three characters as output. | |
27303 | ||
086432e2 AC |
27304 | The annotation @var{level}, which is specified using the |
27305 | @option{--annotate} command line option (@pxref{Mode Options}), controls | |
27306 | how much information @value{GDBN} prints together with its prompt, | |
27307 | values of expressions, source lines, and other types of output. Level 0 | |
d3e8051b | 27308 | is for no annotations, level 1 is for use when @value{GDBN} is run as a |
086432e2 AC |
27309 | subprocess of @sc{gnu} Emacs, level 3 is the maximum annotation suitable |
27310 | for programs that control @value{GDBN}, and level 2 annotations have | |
27311 | been made obsolete (@pxref{Limitations, , Limitations of the Annotation | |
09d4efe1 EZ |
27312 | Interface, annotate, GDB's Obsolete Annotations}). |
27313 | ||
27314 | @table @code | |
27315 | @kindex set annotate | |
27316 | @item set annotate @var{level} | |
e09f16f9 | 27317 | The @value{GDBN} command @code{set annotate} sets the level of |
09d4efe1 | 27318 | annotations to the specified @var{level}. |
9c16f35a EZ |
27319 | |
27320 | @item show annotate | |
27321 | @kindex show annotate | |
27322 | Show the current annotation level. | |
09d4efe1 EZ |
27323 | @end table |
27324 | ||
27325 | This chapter describes level 3 annotations. | |
086432e2 | 27326 | |
922fbb7b AC |
27327 | A simple example of starting up @value{GDBN} with annotations is: |
27328 | ||
27329 | @smallexample | |
086432e2 AC |
27330 | $ @kbd{gdb --annotate=3} |
27331 | GNU gdb 6.0 | |
27332 | Copyright 2003 Free Software Foundation, Inc. | |
922fbb7b AC |
27333 | GDB is free software, covered by the GNU General Public License, |
27334 | and you are welcome to change it and/or distribute copies of it | |
27335 | under certain conditions. | |
27336 | Type "show copying" to see the conditions. | |
27337 | There is absolutely no warranty for GDB. Type "show warranty" | |
27338 | for details. | |
086432e2 | 27339 | This GDB was configured as "i386-pc-linux-gnu" |
922fbb7b AC |
27340 | |
27341 | ^Z^Zpre-prompt | |
f7dc1244 | 27342 | (@value{GDBP}) |
922fbb7b | 27343 | ^Z^Zprompt |
086432e2 | 27344 | @kbd{quit} |
922fbb7b AC |
27345 | |
27346 | ^Z^Zpost-prompt | |
b383017d | 27347 | $ |
922fbb7b AC |
27348 | @end smallexample |
27349 | ||
27350 | Here @samp{quit} is input to @value{GDBN}; the rest is output from | |
27351 | @value{GDBN}. The three lines beginning @samp{^Z^Z} (where @samp{^Z} | |
27352 | denotes a @samp{control-z} character) are annotations; the rest is | |
27353 | output from @value{GDBN}. | |
27354 | ||
9e6c4bd5 NR |
27355 | @node Server Prefix |
27356 | @section The Server Prefix | |
27357 | @cindex server prefix | |
27358 | ||
27359 | If you prefix a command with @samp{server } then it will not affect | |
27360 | the command history, nor will it affect @value{GDBN}'s notion of which | |
27361 | command to repeat if @key{RET} is pressed on a line by itself. This | |
27362 | means that commands can be run behind a user's back by a front-end in | |
27363 | a transparent manner. | |
27364 | ||
d837706a NR |
27365 | The @code{server } prefix does not affect the recording of values into |
27366 | the value history; to print a value without recording it into the | |
27367 | value history, use the @code{output} command instead of the | |
27368 | @code{print} command. | |
27369 | ||
27370 | Using this prefix also disables confirmation requests | |
27371 | (@pxref{confirmation requests}). | |
9e6c4bd5 | 27372 | |
922fbb7b AC |
27373 | @node Prompting |
27374 | @section Annotation for @value{GDBN} Input | |
27375 | ||
27376 | @cindex annotations for prompts | |
27377 | When @value{GDBN} prompts for input, it annotates this fact so it is possible | |
27378 | to know when to send output, when the output from a given command is | |
27379 | over, etc. | |
27380 | ||
27381 | Different kinds of input each have a different @dfn{input type}. Each | |
27382 | input type has three annotations: a @code{pre-} annotation, which | |
27383 | denotes the beginning of any prompt which is being output, a plain | |
27384 | annotation, which denotes the end of the prompt, and then a @code{post-} | |
27385 | annotation which denotes the end of any echo which may (or may not) be | |
27386 | associated with the input. For example, the @code{prompt} input type | |
27387 | features the following annotations: | |
27388 | ||
27389 | @smallexample | |
27390 | ^Z^Zpre-prompt | |
27391 | ^Z^Zprompt | |
27392 | ^Z^Zpost-prompt | |
27393 | @end smallexample | |
27394 | ||
27395 | The input types are | |
27396 | ||
27397 | @table @code | |
e5ac9b53 EZ |
27398 | @findex pre-prompt annotation |
27399 | @findex prompt annotation | |
27400 | @findex post-prompt annotation | |
922fbb7b AC |
27401 | @item prompt |
27402 | When @value{GDBN} is prompting for a command (the main @value{GDBN} prompt). | |
27403 | ||
e5ac9b53 EZ |
27404 | @findex pre-commands annotation |
27405 | @findex commands annotation | |
27406 | @findex post-commands annotation | |
922fbb7b AC |
27407 | @item commands |
27408 | When @value{GDBN} prompts for a set of commands, like in the @code{commands} | |
27409 | command. The annotations are repeated for each command which is input. | |
27410 | ||
e5ac9b53 EZ |
27411 | @findex pre-overload-choice annotation |
27412 | @findex overload-choice annotation | |
27413 | @findex post-overload-choice annotation | |
922fbb7b AC |
27414 | @item overload-choice |
27415 | When @value{GDBN} wants the user to select between various overloaded functions. | |
27416 | ||
e5ac9b53 EZ |
27417 | @findex pre-query annotation |
27418 | @findex query annotation | |
27419 | @findex post-query annotation | |
922fbb7b AC |
27420 | @item query |
27421 | When @value{GDBN} wants the user to confirm a potentially dangerous operation. | |
27422 | ||
e5ac9b53 EZ |
27423 | @findex pre-prompt-for-continue annotation |
27424 | @findex prompt-for-continue annotation | |
27425 | @findex post-prompt-for-continue annotation | |
922fbb7b AC |
27426 | @item prompt-for-continue |
27427 | When @value{GDBN} is asking the user to press return to continue. Note: Don't | |
27428 | expect this to work well; instead use @code{set height 0} to disable | |
27429 | prompting. This is because the counting of lines is buggy in the | |
27430 | presence of annotations. | |
27431 | @end table | |
27432 | ||
27433 | @node Errors | |
27434 | @section Errors | |
27435 | @cindex annotations for errors, warnings and interrupts | |
27436 | ||
e5ac9b53 | 27437 | @findex quit annotation |
922fbb7b AC |
27438 | @smallexample |
27439 | ^Z^Zquit | |
27440 | @end smallexample | |
27441 | ||
27442 | This annotation occurs right before @value{GDBN} responds to an interrupt. | |
27443 | ||
e5ac9b53 | 27444 | @findex error annotation |
922fbb7b AC |
27445 | @smallexample |
27446 | ^Z^Zerror | |
27447 | @end smallexample | |
27448 | ||
27449 | This annotation occurs right before @value{GDBN} responds to an error. | |
27450 | ||
27451 | Quit and error annotations indicate that any annotations which @value{GDBN} was | |
27452 | in the middle of may end abruptly. For example, if a | |
27453 | @code{value-history-begin} annotation is followed by a @code{error}, one | |
27454 | cannot expect to receive the matching @code{value-history-end}. One | |
27455 | cannot expect not to receive it either, however; an error annotation | |
27456 | does not necessarily mean that @value{GDBN} is immediately returning all the way | |
27457 | to the top level. | |
27458 | ||
e5ac9b53 | 27459 | @findex error-begin annotation |
922fbb7b AC |
27460 | A quit or error annotation may be preceded by |
27461 | ||
27462 | @smallexample | |
27463 | ^Z^Zerror-begin | |
27464 | @end smallexample | |
27465 | ||
27466 | Any output between that and the quit or error annotation is the error | |
27467 | message. | |
27468 | ||
27469 | Warning messages are not yet annotated. | |
27470 | @c If we want to change that, need to fix warning(), type_error(), | |
27471 | @c range_error(), and possibly other places. | |
27472 | ||
922fbb7b AC |
27473 | @node Invalidation |
27474 | @section Invalidation Notices | |
27475 | ||
27476 | @cindex annotations for invalidation messages | |
27477 | The following annotations say that certain pieces of state may have | |
27478 | changed. | |
27479 | ||
27480 | @table @code | |
e5ac9b53 | 27481 | @findex frames-invalid annotation |
922fbb7b AC |
27482 | @item ^Z^Zframes-invalid |
27483 | ||
27484 | The frames (for example, output from the @code{backtrace} command) may | |
27485 | have changed. | |
27486 | ||
e5ac9b53 | 27487 | @findex breakpoints-invalid annotation |
922fbb7b AC |
27488 | @item ^Z^Zbreakpoints-invalid |
27489 | ||
27490 | The breakpoints may have changed. For example, the user just added or | |
27491 | deleted a breakpoint. | |
27492 | @end table | |
27493 | ||
27494 | @node Annotations for Running | |
27495 | @section Running the Program | |
27496 | @cindex annotations for running programs | |
27497 | ||
e5ac9b53 EZ |
27498 | @findex starting annotation |
27499 | @findex stopping annotation | |
922fbb7b | 27500 | When the program starts executing due to a @value{GDBN} command such as |
b383017d | 27501 | @code{step} or @code{continue}, |
922fbb7b AC |
27502 | |
27503 | @smallexample | |
27504 | ^Z^Zstarting | |
27505 | @end smallexample | |
27506 | ||
b383017d | 27507 | is output. When the program stops, |
922fbb7b AC |
27508 | |
27509 | @smallexample | |
27510 | ^Z^Zstopped | |
27511 | @end smallexample | |
27512 | ||
27513 | is output. Before the @code{stopped} annotation, a variety of | |
27514 | annotations describe how the program stopped. | |
27515 | ||
27516 | @table @code | |
e5ac9b53 | 27517 | @findex exited annotation |
922fbb7b AC |
27518 | @item ^Z^Zexited @var{exit-status} |
27519 | The program exited, and @var{exit-status} is the exit status (zero for | |
27520 | successful exit, otherwise nonzero). | |
27521 | ||
e5ac9b53 EZ |
27522 | @findex signalled annotation |
27523 | @findex signal-name annotation | |
27524 | @findex signal-name-end annotation | |
27525 | @findex signal-string annotation | |
27526 | @findex signal-string-end annotation | |
922fbb7b AC |
27527 | @item ^Z^Zsignalled |
27528 | The program exited with a signal. After the @code{^Z^Zsignalled}, the | |
27529 | annotation continues: | |
27530 | ||
27531 | @smallexample | |
27532 | @var{intro-text} | |
27533 | ^Z^Zsignal-name | |
27534 | @var{name} | |
27535 | ^Z^Zsignal-name-end | |
27536 | @var{middle-text} | |
27537 | ^Z^Zsignal-string | |
27538 | @var{string} | |
27539 | ^Z^Zsignal-string-end | |
27540 | @var{end-text} | |
27541 | @end smallexample | |
27542 | ||
27543 | @noindent | |
27544 | where @var{name} is the name of the signal, such as @code{SIGILL} or | |
27545 | @code{SIGSEGV}, and @var{string} is the explanation of the signal, such | |
27546 | as @code{Illegal Instruction} or @code{Segmentation fault}. | |
27547 | @var{intro-text}, @var{middle-text}, and @var{end-text} are for the | |
27548 | user's benefit and have no particular format. | |
27549 | ||
e5ac9b53 | 27550 | @findex signal annotation |
922fbb7b AC |
27551 | @item ^Z^Zsignal |
27552 | The syntax of this annotation is just like @code{signalled}, but @value{GDBN} is | |
27553 | just saying that the program received the signal, not that it was | |
27554 | terminated with it. | |
27555 | ||
e5ac9b53 | 27556 | @findex breakpoint annotation |
922fbb7b AC |
27557 | @item ^Z^Zbreakpoint @var{number} |
27558 | The program hit breakpoint number @var{number}. | |
27559 | ||
e5ac9b53 | 27560 | @findex watchpoint annotation |
922fbb7b AC |
27561 | @item ^Z^Zwatchpoint @var{number} |
27562 | The program hit watchpoint number @var{number}. | |
27563 | @end table | |
27564 | ||
27565 | @node Source Annotations | |
27566 | @section Displaying Source | |
27567 | @cindex annotations for source display | |
27568 | ||
e5ac9b53 | 27569 | @findex source annotation |
922fbb7b AC |
27570 | The following annotation is used instead of displaying source code: |
27571 | ||
27572 | @smallexample | |
27573 | ^Z^Zsource @var{filename}:@var{line}:@var{character}:@var{middle}:@var{addr} | |
27574 | @end smallexample | |
27575 | ||
27576 | where @var{filename} is an absolute file name indicating which source | |
27577 | file, @var{line} is the line number within that file (where 1 is the | |
27578 | first line in the file), @var{character} is the character position | |
27579 | within the file (where 0 is the first character in the file) (for most | |
27580 | debug formats this will necessarily point to the beginning of a line), | |
27581 | @var{middle} is @samp{middle} if @var{addr} is in the middle of the | |
27582 | line, or @samp{beg} if @var{addr} is at the beginning of the line, and | |
27583 | @var{addr} is the address in the target program associated with the | |
27584 | source which is being displayed. @var{addr} is in the form @samp{0x} | |
27585 | followed by one or more lowercase hex digits (note that this does not | |
27586 | depend on the language). | |
27587 | ||
4efc6507 DE |
27588 | @node JIT Interface |
27589 | @chapter JIT Compilation Interface | |
27590 | @cindex just-in-time compilation | |
27591 | @cindex JIT compilation interface | |
27592 | ||
27593 | This chapter documents @value{GDBN}'s @dfn{just-in-time} (JIT) compilation | |
27594 | interface. A JIT compiler is a program or library that generates native | |
27595 | executable code at runtime and executes it, usually in order to achieve good | |
27596 | performance while maintaining platform independence. | |
27597 | ||
27598 | Programs that use JIT compilation are normally difficult to debug because | |
27599 | portions of their code are generated at runtime, instead of being loaded from | |
27600 | object files, which is where @value{GDBN} normally finds the program's symbols | |
27601 | and debug information. In order to debug programs that use JIT compilation, | |
27602 | @value{GDBN} has an interface that allows the program to register in-memory | |
27603 | symbol files with @value{GDBN} at runtime. | |
27604 | ||
27605 | If you are using @value{GDBN} to debug a program that uses this interface, then | |
27606 | it should work transparently so long as you have not stripped the binary. If | |
27607 | you are developing a JIT compiler, then the interface is documented in the rest | |
27608 | of this chapter. At this time, the only known client of this interface is the | |
27609 | LLVM JIT. | |
27610 | ||
27611 | Broadly speaking, the JIT interface mirrors the dynamic loader interface. The | |
27612 | JIT compiler communicates with @value{GDBN} by writing data into a global | |
27613 | variable and calling a fuction at a well-known symbol. When @value{GDBN} | |
27614 | attaches, it reads a linked list of symbol files from the global variable to | |
27615 | find existing code, and puts a breakpoint in the function so that it can find | |
27616 | out about additional code. | |
27617 | ||
27618 | @menu | |
27619 | * Declarations:: Relevant C struct declarations | |
27620 | * Registering Code:: Steps to register code | |
27621 | * Unregistering Code:: Steps to unregister code | |
27622 | @end menu | |
27623 | ||
27624 | @node Declarations | |
27625 | @section JIT Declarations | |
27626 | ||
27627 | These are the relevant struct declarations that a C program should include to | |
27628 | implement the interface: | |
27629 | ||
27630 | @smallexample | |
27631 | typedef enum | |
27632 | @{ | |
27633 | JIT_NOACTION = 0, | |
27634 | JIT_REGISTER_FN, | |
27635 | JIT_UNREGISTER_FN | |
27636 | @} jit_actions_t; | |
27637 | ||
27638 | struct jit_code_entry | |
27639 | @{ | |
27640 | struct jit_code_entry *next_entry; | |
27641 | struct jit_code_entry *prev_entry; | |
27642 | const char *symfile_addr; | |
27643 | uint64_t symfile_size; | |
27644 | @}; | |
27645 | ||
27646 | struct jit_descriptor | |
27647 | @{ | |
27648 | uint32_t version; | |
27649 | /* This type should be jit_actions_t, but we use uint32_t | |
27650 | to be explicit about the bitwidth. */ | |
27651 | uint32_t action_flag; | |
27652 | struct jit_code_entry *relevant_entry; | |
27653 | struct jit_code_entry *first_entry; | |
27654 | @}; | |
27655 | ||
27656 | /* GDB puts a breakpoint in this function. */ | |
27657 | void __attribute__((noinline)) __jit_debug_register_code() @{ @}; | |
27658 | ||
27659 | /* Make sure to specify the version statically, because the | |
27660 | debugger may check the version before we can set it. */ | |
27661 | struct jit_descriptor __jit_debug_descriptor = @{ 1, 0, 0, 0 @}; | |
27662 | @end smallexample | |
27663 | ||
27664 | If the JIT is multi-threaded, then it is important that the JIT synchronize any | |
27665 | modifications to this global data properly, which can easily be done by putting | |
27666 | a global mutex around modifications to these structures. | |
27667 | ||
27668 | @node Registering Code | |
27669 | @section Registering Code | |
27670 | ||
27671 | To register code with @value{GDBN}, the JIT should follow this protocol: | |
27672 | ||
27673 | @itemize @bullet | |
27674 | @item | |
27675 | Generate an object file in memory with symbols and other desired debug | |
27676 | information. The file must include the virtual addresses of the sections. | |
27677 | ||
27678 | @item | |
27679 | Create a code entry for the file, which gives the start and size of the symbol | |
27680 | file. | |
27681 | ||
27682 | @item | |
27683 | Add it to the linked list in the JIT descriptor. | |
27684 | ||
27685 | @item | |
27686 | Point the relevant_entry field of the descriptor at the entry. | |
27687 | ||
27688 | @item | |
27689 | Set @code{action_flag} to @code{JIT_REGISTER} and call | |
27690 | @code{__jit_debug_register_code}. | |
27691 | @end itemize | |
27692 | ||
27693 | When @value{GDBN} is attached and the breakpoint fires, @value{GDBN} uses the | |
27694 | @code{relevant_entry} pointer so it doesn't have to walk the list looking for | |
27695 | new code. However, the linked list must still be maintained in order to allow | |
27696 | @value{GDBN} to attach to a running process and still find the symbol files. | |
27697 | ||
27698 | @node Unregistering Code | |
27699 | @section Unregistering Code | |
27700 | ||
27701 | If code is freed, then the JIT should use the following protocol: | |
27702 | ||
27703 | @itemize @bullet | |
27704 | @item | |
27705 | Remove the code entry corresponding to the code from the linked list. | |
27706 | ||
27707 | @item | |
27708 | Point the @code{relevant_entry} field of the descriptor at the code entry. | |
27709 | ||
27710 | @item | |
27711 | Set @code{action_flag} to @code{JIT_UNREGISTER} and call | |
27712 | @code{__jit_debug_register_code}. | |
27713 | @end itemize | |
27714 | ||
27715 | If the JIT frees or recompiles code without unregistering it, then @value{GDBN} | |
27716 | and the JIT will leak the memory used for the associated symbol files. | |
27717 | ||
8e04817f AC |
27718 | @node GDB Bugs |
27719 | @chapter Reporting Bugs in @value{GDBN} | |
27720 | @cindex bugs in @value{GDBN} | |
27721 | @cindex reporting bugs in @value{GDBN} | |
c906108c | 27722 | |
8e04817f | 27723 | Your bug reports play an essential role in making @value{GDBN} reliable. |
c906108c | 27724 | |
8e04817f AC |
27725 | Reporting a bug may help you by bringing a solution to your problem, or it |
27726 | may not. But in any case the principal function of a bug report is to help | |
27727 | the entire community by making the next version of @value{GDBN} work better. Bug | |
27728 | reports are your contribution to the maintenance of @value{GDBN}. | |
c906108c | 27729 | |
8e04817f AC |
27730 | In order for a bug report to serve its purpose, you must include the |
27731 | information that enables us to fix the bug. | |
c4555f82 SC |
27732 | |
27733 | @menu | |
8e04817f AC |
27734 | * Bug Criteria:: Have you found a bug? |
27735 | * Bug Reporting:: How to report bugs | |
c4555f82 SC |
27736 | @end menu |
27737 | ||
8e04817f | 27738 | @node Bug Criteria |
79a6e687 | 27739 | @section Have You Found a Bug? |
8e04817f | 27740 | @cindex bug criteria |
c4555f82 | 27741 | |
8e04817f | 27742 | If you are not sure whether you have found a bug, here are some guidelines: |
c4555f82 SC |
27743 | |
27744 | @itemize @bullet | |
8e04817f AC |
27745 | @cindex fatal signal |
27746 | @cindex debugger crash | |
27747 | @cindex crash of debugger | |
c4555f82 | 27748 | @item |
8e04817f AC |
27749 | If the debugger gets a fatal signal, for any input whatever, that is a |
27750 | @value{GDBN} bug. Reliable debuggers never crash. | |
27751 | ||
27752 | @cindex error on valid input | |
27753 | @item | |
27754 | If @value{GDBN} produces an error message for valid input, that is a | |
27755 | bug. (Note that if you're cross debugging, the problem may also be | |
27756 | somewhere in the connection to the target.) | |
c4555f82 | 27757 | |
8e04817f | 27758 | @cindex invalid input |
c4555f82 | 27759 | @item |
8e04817f AC |
27760 | If @value{GDBN} does not produce an error message for invalid input, |
27761 | that is a bug. However, you should note that your idea of | |
27762 | ``invalid input'' might be our idea of ``an extension'' or ``support | |
27763 | for traditional practice''. | |
27764 | ||
27765 | @item | |
27766 | If you are an experienced user of debugging tools, your suggestions | |
27767 | for improvement of @value{GDBN} are welcome in any case. | |
c4555f82 SC |
27768 | @end itemize |
27769 | ||
8e04817f | 27770 | @node Bug Reporting |
79a6e687 | 27771 | @section How to Report Bugs |
8e04817f AC |
27772 | @cindex bug reports |
27773 | @cindex @value{GDBN} bugs, reporting | |
27774 | ||
27775 | A number of companies and individuals offer support for @sc{gnu} products. | |
27776 | If you obtained @value{GDBN} from a support organization, we recommend you | |
27777 | contact that organization first. | |
27778 | ||
27779 | You can find contact information for many support companies and | |
27780 | individuals in the file @file{etc/SERVICE} in the @sc{gnu} Emacs | |
27781 | distribution. | |
27782 | @c should add a web page ref... | |
27783 | ||
c16158bc JM |
27784 | @ifset BUGURL |
27785 | @ifset BUGURL_DEFAULT | |
129188f6 | 27786 | In any event, we also recommend that you submit bug reports for |
d3e8051b | 27787 | @value{GDBN}. The preferred method is to submit them directly using |
129188f6 AC |
27788 | @uref{http://www.gnu.org/software/gdb/bugs/, @value{GDBN}'s Bugs web |
27789 | page}. Alternatively, the @email{bug-gdb@@gnu.org, e-mail gateway} can | |
27790 | be used. | |
8e04817f AC |
27791 | |
27792 | @strong{Do not send bug reports to @samp{info-gdb}, or to | |
27793 | @samp{help-gdb}, or to any newsgroups.} Most users of @value{GDBN} do | |
27794 | not want to receive bug reports. Those that do have arranged to receive | |
27795 | @samp{bug-gdb}. | |
27796 | ||
27797 | The mailing list @samp{bug-gdb} has a newsgroup @samp{gnu.gdb.bug} which | |
27798 | serves as a repeater. The mailing list and the newsgroup carry exactly | |
27799 | the same messages. Often people think of posting bug reports to the | |
27800 | newsgroup instead of mailing them. This appears to work, but it has one | |
27801 | problem which can be crucial: a newsgroup posting often lacks a mail | |
27802 | path back to the sender. Thus, if we need to ask for more information, | |
27803 | we may be unable to reach you. For this reason, it is better to send | |
27804 | bug reports to the mailing list. | |
c16158bc JM |
27805 | @end ifset |
27806 | @ifclear BUGURL_DEFAULT | |
27807 | In any event, we also recommend that you submit bug reports for | |
27808 | @value{GDBN} to @value{BUGURL}. | |
27809 | @end ifclear | |
27810 | @end ifset | |
c4555f82 | 27811 | |
8e04817f AC |
27812 | The fundamental principle of reporting bugs usefully is this: |
27813 | @strong{report all the facts}. If you are not sure whether to state a | |
27814 | fact or leave it out, state it! | |
c4555f82 | 27815 | |
8e04817f AC |
27816 | Often people omit facts because they think they know what causes the |
27817 | problem and assume that some details do not matter. Thus, you might | |
27818 | assume that the name of the variable you use in an example does not matter. | |
27819 | Well, probably it does not, but one cannot be sure. Perhaps the bug is a | |
27820 | stray memory reference which happens to fetch from the location where that | |
27821 | name is stored in memory; perhaps, if the name were different, the contents | |
27822 | of that location would fool the debugger into doing the right thing despite | |
27823 | the bug. Play it safe and give a specific, complete example. That is the | |
27824 | easiest thing for you to do, and the most helpful. | |
c4555f82 | 27825 | |
8e04817f AC |
27826 | Keep in mind that the purpose of a bug report is to enable us to fix the |
27827 | bug. It may be that the bug has been reported previously, but neither | |
27828 | you nor we can know that unless your bug report is complete and | |
27829 | self-contained. | |
c4555f82 | 27830 | |
8e04817f AC |
27831 | Sometimes people give a few sketchy facts and ask, ``Does this ring a |
27832 | bell?'' Those bug reports are useless, and we urge everyone to | |
27833 | @emph{refuse to respond to them} except to chide the sender to report | |
27834 | bugs properly. | |
27835 | ||
27836 | To enable us to fix the bug, you should include all these things: | |
c4555f82 SC |
27837 | |
27838 | @itemize @bullet | |
27839 | @item | |
8e04817f AC |
27840 | The version of @value{GDBN}. @value{GDBN} announces it if you start |
27841 | with no arguments; you can also print it at any time using @code{show | |
27842 | version}. | |
c4555f82 | 27843 | |
8e04817f AC |
27844 | Without this, we will not know whether there is any point in looking for |
27845 | the bug in the current version of @value{GDBN}. | |
c4555f82 SC |
27846 | |
27847 | @item | |
8e04817f AC |
27848 | The type of machine you are using, and the operating system name and |
27849 | version number. | |
c4555f82 SC |
27850 | |
27851 | @item | |
c1468174 | 27852 | What compiler (and its version) was used to compile @value{GDBN}---e.g.@: |
8e04817f | 27853 | ``@value{GCC}--2.8.1''. |
c4555f82 SC |
27854 | |
27855 | @item | |
8e04817f | 27856 | What compiler (and its version) was used to compile the program you are |
c1468174 | 27857 | debugging---e.g.@: ``@value{GCC}--2.8.1'', or ``HP92453-01 A.10.32.03 HP |
3f94c067 BW |
27858 | C Compiler''. For @value{NGCC}, you can say @kbd{@value{GCC} --version} |
27859 | to get this information; for other compilers, see the documentation for | |
27860 | those compilers. | |
c4555f82 | 27861 | |
8e04817f AC |
27862 | @item |
27863 | The command arguments you gave the compiler to compile your example and | |
27864 | observe the bug. For example, did you use @samp{-O}? To guarantee | |
27865 | you will not omit something important, list them all. A copy of the | |
27866 | Makefile (or the output from make) is sufficient. | |
c4555f82 | 27867 | |
8e04817f AC |
27868 | If we were to try to guess the arguments, we would probably guess wrong |
27869 | and then we might not encounter the bug. | |
c4555f82 | 27870 | |
8e04817f AC |
27871 | @item |
27872 | A complete input script, and all necessary source files, that will | |
27873 | reproduce the bug. | |
c4555f82 | 27874 | |
8e04817f AC |
27875 | @item |
27876 | A description of what behavior you observe that you believe is | |
27877 | incorrect. For example, ``It gets a fatal signal.'' | |
c4555f82 | 27878 | |
8e04817f AC |
27879 | Of course, if the bug is that @value{GDBN} gets a fatal signal, then we |
27880 | will certainly notice it. But if the bug is incorrect output, we might | |
27881 | not notice unless it is glaringly wrong. You might as well not give us | |
27882 | a chance to make a mistake. | |
c4555f82 | 27883 | |
8e04817f AC |
27884 | Even if the problem you experience is a fatal signal, you should still |
27885 | say so explicitly. Suppose something strange is going on, such as, your | |
27886 | copy of @value{GDBN} is out of synch, or you have encountered a bug in | |
27887 | the C library on your system. (This has happened!) Your copy might | |
27888 | crash and ours would not. If you told us to expect a crash, then when | |
27889 | ours fails to crash, we would know that the bug was not happening for | |
27890 | us. If you had not told us to expect a crash, then we would not be able | |
27891 | to draw any conclusion from our observations. | |
c4555f82 | 27892 | |
e0c07bf0 MC |
27893 | @pindex script |
27894 | @cindex recording a session script | |
27895 | To collect all this information, you can use a session recording program | |
27896 | such as @command{script}, which is available on many Unix systems. | |
27897 | Just run your @value{GDBN} session inside @command{script} and then | |
27898 | include the @file{typescript} file with your bug report. | |
27899 | ||
27900 | Another way to record a @value{GDBN} session is to run @value{GDBN} | |
27901 | inside Emacs and then save the entire buffer to a file. | |
27902 | ||
8e04817f AC |
27903 | @item |
27904 | If you wish to suggest changes to the @value{GDBN} source, send us context | |
27905 | diffs. If you even discuss something in the @value{GDBN} source, refer to | |
27906 | it by context, not by line number. | |
c4555f82 | 27907 | |
8e04817f AC |
27908 | The line numbers in our development sources will not match those in your |
27909 | sources. Your line numbers would convey no useful information to us. | |
c4555f82 | 27910 | |
8e04817f | 27911 | @end itemize |
c4555f82 | 27912 | |
8e04817f | 27913 | Here are some things that are not necessary: |
c4555f82 | 27914 | |
8e04817f AC |
27915 | @itemize @bullet |
27916 | @item | |
27917 | A description of the envelope of the bug. | |
c4555f82 | 27918 | |
8e04817f AC |
27919 | Often people who encounter a bug spend a lot of time investigating |
27920 | which changes to the input file will make the bug go away and which | |
27921 | changes will not affect it. | |
c4555f82 | 27922 | |
8e04817f AC |
27923 | This is often time consuming and not very useful, because the way we |
27924 | will find the bug is by running a single example under the debugger | |
27925 | with breakpoints, not by pure deduction from a series of examples. | |
27926 | We recommend that you save your time for something else. | |
c4555f82 | 27927 | |
8e04817f AC |
27928 | Of course, if you can find a simpler example to report @emph{instead} |
27929 | of the original one, that is a convenience for us. Errors in the | |
27930 | output will be easier to spot, running under the debugger will take | |
27931 | less time, and so on. | |
c4555f82 | 27932 | |
8e04817f AC |
27933 | However, simplification is not vital; if you do not want to do this, |
27934 | report the bug anyway and send us the entire test case you used. | |
c4555f82 | 27935 | |
8e04817f AC |
27936 | @item |
27937 | A patch for the bug. | |
c4555f82 | 27938 | |
8e04817f AC |
27939 | A patch for the bug does help us if it is a good one. But do not omit |
27940 | the necessary information, such as the test case, on the assumption that | |
27941 | a patch is all we need. We might see problems with your patch and decide | |
27942 | to fix the problem another way, or we might not understand it at all. | |
c4555f82 | 27943 | |
8e04817f AC |
27944 | Sometimes with a program as complicated as @value{GDBN} it is very hard to |
27945 | construct an example that will make the program follow a certain path | |
27946 | through the code. If you do not send us the example, we will not be able | |
27947 | to construct one, so we will not be able to verify that the bug is fixed. | |
c4555f82 | 27948 | |
8e04817f AC |
27949 | And if we cannot understand what bug you are trying to fix, or why your |
27950 | patch should be an improvement, we will not install it. A test case will | |
27951 | help us to understand. | |
c4555f82 | 27952 | |
8e04817f AC |
27953 | @item |
27954 | A guess about what the bug is or what it depends on. | |
c4555f82 | 27955 | |
8e04817f AC |
27956 | Such guesses are usually wrong. Even we cannot guess right about such |
27957 | things without first using the debugger to find the facts. | |
27958 | @end itemize | |
c4555f82 | 27959 | |
8e04817f AC |
27960 | @c The readline documentation is distributed with the readline code |
27961 | @c and consists of the two following files: | |
27962 | @c rluser.texinfo | |
27963 | @c inc-hist.texinfo | |
27964 | @c Use -I with makeinfo to point to the appropriate directory, | |
27965 | @c environment var TEXINPUTS with TeX. | |
5bdf8622 | 27966 | @include rluser.texi |
8e04817f | 27967 | @include inc-hist.texinfo |
c4555f82 | 27968 | |
c4555f82 | 27969 | |
8e04817f AC |
27970 | @node Formatting Documentation |
27971 | @appendix Formatting Documentation | |
c4555f82 | 27972 | |
8e04817f AC |
27973 | @cindex @value{GDBN} reference card |
27974 | @cindex reference card | |
27975 | The @value{GDBN} 4 release includes an already-formatted reference card, ready | |
27976 | for printing with PostScript or Ghostscript, in the @file{gdb} | |
27977 | subdirectory of the main source directory@footnote{In | |
27978 | @file{gdb-@value{GDBVN}/gdb/refcard.ps} of the version @value{GDBVN} | |
27979 | release.}. If you can use PostScript or Ghostscript with your printer, | |
27980 | you can print the reference card immediately with @file{refcard.ps}. | |
c4555f82 | 27981 | |
8e04817f AC |
27982 | The release also includes the source for the reference card. You |
27983 | can format it, using @TeX{}, by typing: | |
c4555f82 | 27984 | |
474c8240 | 27985 | @smallexample |
8e04817f | 27986 | make refcard.dvi |
474c8240 | 27987 | @end smallexample |
c4555f82 | 27988 | |
8e04817f AC |
27989 | The @value{GDBN} reference card is designed to print in @dfn{landscape} |
27990 | mode on US ``letter'' size paper; | |
27991 | that is, on a sheet 11 inches wide by 8.5 inches | |
27992 | high. You will need to specify this form of printing as an option to | |
27993 | your @sc{dvi} output program. | |
c4555f82 | 27994 | |
8e04817f | 27995 | @cindex documentation |
c4555f82 | 27996 | |
8e04817f AC |
27997 | All the documentation for @value{GDBN} comes as part of the machine-readable |
27998 | distribution. The documentation is written in Texinfo format, which is | |
27999 | a documentation system that uses a single source file to produce both | |
28000 | on-line information and a printed manual. You can use one of the Info | |
28001 | formatting commands to create the on-line version of the documentation | |
28002 | and @TeX{} (or @code{texi2roff}) to typeset the printed version. | |
c4555f82 | 28003 | |
8e04817f AC |
28004 | @value{GDBN} includes an already formatted copy of the on-line Info |
28005 | version of this manual in the @file{gdb} subdirectory. The main Info | |
28006 | file is @file{gdb-@value{GDBVN}/gdb/gdb.info}, and it refers to | |
28007 | subordinate files matching @samp{gdb.info*} in the same directory. If | |
28008 | necessary, you can print out these files, or read them with any editor; | |
28009 | but they are easier to read using the @code{info} subsystem in @sc{gnu} | |
28010 | Emacs or the standalone @code{info} program, available as part of the | |
28011 | @sc{gnu} Texinfo distribution. | |
c4555f82 | 28012 | |
8e04817f AC |
28013 | If you want to format these Info files yourself, you need one of the |
28014 | Info formatting programs, such as @code{texinfo-format-buffer} or | |
28015 | @code{makeinfo}. | |
c4555f82 | 28016 | |
8e04817f AC |
28017 | If you have @code{makeinfo} installed, and are in the top level |
28018 | @value{GDBN} source directory (@file{gdb-@value{GDBVN}}, in the case of | |
28019 | version @value{GDBVN}), you can make the Info file by typing: | |
c4555f82 | 28020 | |
474c8240 | 28021 | @smallexample |
8e04817f AC |
28022 | cd gdb |
28023 | make gdb.info | |
474c8240 | 28024 | @end smallexample |
c4555f82 | 28025 | |
8e04817f AC |
28026 | If you want to typeset and print copies of this manual, you need @TeX{}, |
28027 | a program to print its @sc{dvi} output files, and @file{texinfo.tex}, the | |
28028 | Texinfo definitions file. | |
c4555f82 | 28029 | |
8e04817f AC |
28030 | @TeX{} is a typesetting program; it does not print files directly, but |
28031 | produces output files called @sc{dvi} files. To print a typeset | |
28032 | document, you need a program to print @sc{dvi} files. If your system | |
28033 | has @TeX{} installed, chances are it has such a program. The precise | |
28034 | command to use depends on your system; @kbd{lpr -d} is common; another | |
28035 | (for PostScript devices) is @kbd{dvips}. The @sc{dvi} print command may | |
28036 | require a file name without any extension or a @samp{.dvi} extension. | |
c4555f82 | 28037 | |
8e04817f AC |
28038 | @TeX{} also requires a macro definitions file called |
28039 | @file{texinfo.tex}. This file tells @TeX{} how to typeset a document | |
28040 | written in Texinfo format. On its own, @TeX{} cannot either read or | |
28041 | typeset a Texinfo file. @file{texinfo.tex} is distributed with GDB | |
28042 | and is located in the @file{gdb-@var{version-number}/texinfo} | |
28043 | directory. | |
c4555f82 | 28044 | |
8e04817f | 28045 | If you have @TeX{} and a @sc{dvi} printer program installed, you can |
d3e8051b | 28046 | typeset and print this manual. First switch to the @file{gdb} |
8e04817f AC |
28047 | subdirectory of the main source directory (for example, to |
28048 | @file{gdb-@value{GDBVN}/gdb}) and type: | |
c4555f82 | 28049 | |
474c8240 | 28050 | @smallexample |
8e04817f | 28051 | make gdb.dvi |
474c8240 | 28052 | @end smallexample |
c4555f82 | 28053 | |
8e04817f | 28054 | Then give @file{gdb.dvi} to your @sc{dvi} printing program. |
c4555f82 | 28055 | |
8e04817f AC |
28056 | @node Installing GDB |
28057 | @appendix Installing @value{GDBN} | |
8e04817f | 28058 | @cindex installation |
c4555f82 | 28059 | |
7fa2210b DJ |
28060 | @menu |
28061 | * Requirements:: Requirements for building @value{GDBN} | |
db2e3e2e | 28062 | * Running Configure:: Invoking the @value{GDBN} @file{configure} script |
7fa2210b DJ |
28063 | * Separate Objdir:: Compiling @value{GDBN} in another directory |
28064 | * Config Names:: Specifying names for hosts and targets | |
28065 | * Configure Options:: Summary of options for configure | |
098b41a6 | 28066 | * System-wide configuration:: Having a system-wide init file |
7fa2210b DJ |
28067 | @end menu |
28068 | ||
28069 | @node Requirements | |
79a6e687 | 28070 | @section Requirements for Building @value{GDBN} |
7fa2210b DJ |
28071 | @cindex building @value{GDBN}, requirements for |
28072 | ||
28073 | Building @value{GDBN} requires various tools and packages to be available. | |
28074 | Other packages will be used only if they are found. | |
28075 | ||
79a6e687 | 28076 | @heading Tools/Packages Necessary for Building @value{GDBN} |
7fa2210b DJ |
28077 | @table @asis |
28078 | @item ISO C90 compiler | |
28079 | @value{GDBN} is written in ISO C90. It should be buildable with any | |
28080 | working C90 compiler, e.g.@: GCC. | |
28081 | ||
28082 | @end table | |
28083 | ||
79a6e687 | 28084 | @heading Tools/Packages Optional for Building @value{GDBN} |
7fa2210b DJ |
28085 | @table @asis |
28086 | @item Expat | |
123dc839 | 28087 | @anchor{Expat} |
7fa2210b DJ |
28088 | @value{GDBN} can use the Expat XML parsing library. This library may be |
28089 | included with your operating system distribution; if it is not, you | |
28090 | can get the latest version from @url{http://expat.sourceforge.net}. | |
db2e3e2e | 28091 | The @file{configure} script will search for this library in several |
7fa2210b DJ |
28092 | standard locations; if it is installed in an unusual path, you can |
28093 | use the @option{--with-libexpat-prefix} option to specify its location. | |
28094 | ||
9cceb671 DJ |
28095 | Expat is used for: |
28096 | ||
28097 | @itemize @bullet | |
28098 | @item | |
28099 | Remote protocol memory maps (@pxref{Memory Map Format}) | |
28100 | @item | |
28101 | Target descriptions (@pxref{Target Descriptions}) | |
28102 | @item | |
28103 | Remote shared library lists (@pxref{Library List Format}) | |
28104 | @item | |
28105 | MS-Windows shared libraries (@pxref{Shared Libraries}) | |
28106 | @end itemize | |
7fa2210b | 28107 | |
31fffb02 CS |
28108 | @item zlib |
28109 | @cindex compressed debug sections | |
28110 | @value{GDBN} will use the @samp{zlib} library, if available, to read | |
28111 | compressed debug sections. Some linkers, such as GNU gold, are capable | |
28112 | of producing binaries with compressed debug sections. If @value{GDBN} | |
28113 | is compiled with @samp{zlib}, it will be able to read the debug | |
28114 | information in such binaries. | |
28115 | ||
28116 | The @samp{zlib} library is likely included with your operating system | |
28117 | distribution; if it is not, you can get the latest version from | |
28118 | @url{http://zlib.net}. | |
28119 | ||
6c7a06a3 TT |
28120 | @item iconv |
28121 | @value{GDBN}'s features related to character sets (@pxref{Character | |
28122 | Sets}) require a functioning @code{iconv} implementation. If you are | |
28123 | on a GNU system, then this is provided by the GNU C Library. Some | |
28124 | other systems also provide a working @code{iconv}. | |
28125 | ||
28126 | On systems with @code{iconv}, you can install GNU Libiconv. If you | |
28127 | have previously installed Libiconv, you can use the | |
28128 | @option{--with-libiconv-prefix} option to configure. | |
28129 | ||
28130 | @value{GDBN}'s top-level @file{configure} and @file{Makefile} will | |
28131 | arrange to build Libiconv if a directory named @file{libiconv} appears | |
28132 | in the top-most source directory. If Libiconv is built this way, and | |
28133 | if the operating system does not provide a suitable @code{iconv} | |
28134 | implementation, then the just-built library will automatically be used | |
28135 | by @value{GDBN}. One easy way to set this up is to download GNU | |
28136 | Libiconv, unpack it, and then rename the directory holding the | |
28137 | Libiconv source code to @samp{libiconv}. | |
7fa2210b DJ |
28138 | @end table |
28139 | ||
28140 | @node Running Configure | |
db2e3e2e | 28141 | @section Invoking the @value{GDBN} @file{configure} Script |
7fa2210b | 28142 | @cindex configuring @value{GDBN} |
db2e3e2e | 28143 | @value{GDBN} comes with a @file{configure} script that automates the process |
8e04817f AC |
28144 | of preparing @value{GDBN} for installation; you can then use @code{make} to |
28145 | build the @code{gdb} program. | |
28146 | @iftex | |
28147 | @c irrelevant in info file; it's as current as the code it lives with. | |
28148 | @footnote{If you have a more recent version of @value{GDBN} than @value{GDBVN}, | |
28149 | look at the @file{README} file in the sources; we may have improved the | |
28150 | installation procedures since publishing this manual.} | |
28151 | @end iftex | |
c4555f82 | 28152 | |
8e04817f AC |
28153 | The @value{GDBN} distribution includes all the source code you need for |
28154 | @value{GDBN} in a single directory, whose name is usually composed by | |
28155 | appending the version number to @samp{gdb}. | |
c4555f82 | 28156 | |
8e04817f AC |
28157 | For example, the @value{GDBN} version @value{GDBVN} distribution is in the |
28158 | @file{gdb-@value{GDBVN}} directory. That directory contains: | |
c4555f82 | 28159 | |
8e04817f AC |
28160 | @table @code |
28161 | @item gdb-@value{GDBVN}/configure @r{(and supporting files)} | |
28162 | script for configuring @value{GDBN} and all its supporting libraries | |
c4555f82 | 28163 | |
8e04817f AC |
28164 | @item gdb-@value{GDBVN}/gdb |
28165 | the source specific to @value{GDBN} itself | |
c4555f82 | 28166 | |
8e04817f AC |
28167 | @item gdb-@value{GDBVN}/bfd |
28168 | source for the Binary File Descriptor library | |
c906108c | 28169 | |
8e04817f AC |
28170 | @item gdb-@value{GDBVN}/include |
28171 | @sc{gnu} include files | |
c906108c | 28172 | |
8e04817f AC |
28173 | @item gdb-@value{GDBVN}/libiberty |
28174 | source for the @samp{-liberty} free software library | |
c906108c | 28175 | |
8e04817f AC |
28176 | @item gdb-@value{GDBVN}/opcodes |
28177 | source for the library of opcode tables and disassemblers | |
c906108c | 28178 | |
8e04817f AC |
28179 | @item gdb-@value{GDBVN}/readline |
28180 | source for the @sc{gnu} command-line interface | |
c906108c | 28181 | |
8e04817f AC |
28182 | @item gdb-@value{GDBVN}/glob |
28183 | source for the @sc{gnu} filename pattern-matching subroutine | |
c906108c | 28184 | |
8e04817f AC |
28185 | @item gdb-@value{GDBVN}/mmalloc |
28186 | source for the @sc{gnu} memory-mapped malloc package | |
28187 | @end table | |
c906108c | 28188 | |
db2e3e2e | 28189 | The simplest way to configure and build @value{GDBN} is to run @file{configure} |
8e04817f AC |
28190 | from the @file{gdb-@var{version-number}} source directory, which in |
28191 | this example is the @file{gdb-@value{GDBVN}} directory. | |
c906108c | 28192 | |
8e04817f | 28193 | First switch to the @file{gdb-@var{version-number}} source directory |
db2e3e2e | 28194 | if you are not already in it; then run @file{configure}. Pass the |
8e04817f AC |
28195 | identifier for the platform on which @value{GDBN} will run as an |
28196 | argument. | |
c906108c | 28197 | |
8e04817f | 28198 | For example: |
c906108c | 28199 | |
474c8240 | 28200 | @smallexample |
8e04817f AC |
28201 | cd gdb-@value{GDBVN} |
28202 | ./configure @var{host} | |
28203 | make | |
474c8240 | 28204 | @end smallexample |
c906108c | 28205 | |
8e04817f AC |
28206 | @noindent |
28207 | where @var{host} is an identifier such as @samp{sun4} or | |
28208 | @samp{decstation}, that identifies the platform where @value{GDBN} will run. | |
db2e3e2e | 28209 | (You can often leave off @var{host}; @file{configure} tries to guess the |
8e04817f | 28210 | correct value by examining your system.) |
c906108c | 28211 | |
8e04817f AC |
28212 | Running @samp{configure @var{host}} and then running @code{make} builds the |
28213 | @file{bfd}, @file{readline}, @file{mmalloc}, and @file{libiberty} | |
28214 | libraries, then @code{gdb} itself. The configured source files, and the | |
28215 | binaries, are left in the corresponding source directories. | |
c906108c | 28216 | |
8e04817f | 28217 | @need 750 |
db2e3e2e | 28218 | @file{configure} is a Bourne-shell (@code{/bin/sh}) script; if your |
8e04817f AC |
28219 | system does not recognize this automatically when you run a different |
28220 | shell, you may need to run @code{sh} on it explicitly: | |
c906108c | 28221 | |
474c8240 | 28222 | @smallexample |
8e04817f | 28223 | sh configure @var{host} |
474c8240 | 28224 | @end smallexample |
c906108c | 28225 | |
db2e3e2e | 28226 | If you run @file{configure} from a directory that contains source |
8e04817f | 28227 | directories for multiple libraries or programs, such as the |
db2e3e2e BW |
28228 | @file{gdb-@value{GDBVN}} source directory for version @value{GDBVN}, |
28229 | @file{configure} | |
8e04817f AC |
28230 | creates configuration files for every directory level underneath (unless |
28231 | you tell it not to, with the @samp{--norecursion} option). | |
28232 | ||
db2e3e2e | 28233 | You should run the @file{configure} script from the top directory in the |
94e91d6d | 28234 | source tree, the @file{gdb-@var{version-number}} directory. If you run |
db2e3e2e | 28235 | @file{configure} from one of the subdirectories, you will configure only |
94e91d6d | 28236 | that subdirectory. That is usually not what you want. In particular, |
db2e3e2e | 28237 | if you run the first @file{configure} from the @file{gdb} subdirectory |
94e91d6d MC |
28238 | of the @file{gdb-@var{version-number}} directory, you will omit the |
28239 | configuration of @file{bfd}, @file{readline}, and other sibling | |
28240 | directories of the @file{gdb} subdirectory. This leads to build errors | |
28241 | about missing include files such as @file{bfd/bfd.h}. | |
c906108c | 28242 | |
8e04817f AC |
28243 | You can install @code{@value{GDBP}} anywhere; it has no hardwired paths. |
28244 | However, you should make sure that the shell on your path (named by | |
28245 | the @samp{SHELL} environment variable) is publicly readable. Remember | |
28246 | that @value{GDBN} uses the shell to start your program---some systems refuse to | |
28247 | let @value{GDBN} debug child processes whose programs are not readable. | |
c906108c | 28248 | |
8e04817f | 28249 | @node Separate Objdir |
79a6e687 | 28250 | @section Compiling @value{GDBN} in Another Directory |
c906108c | 28251 | |
8e04817f AC |
28252 | If you want to run @value{GDBN} versions for several host or target machines, |
28253 | you need a different @code{gdb} compiled for each combination of | |
db2e3e2e | 28254 | host and target. @file{configure} is designed to make this easy by |
8e04817f AC |
28255 | allowing you to generate each configuration in a separate subdirectory, |
28256 | rather than in the source directory. If your @code{make} program | |
28257 | handles the @samp{VPATH} feature (@sc{gnu} @code{make} does), running | |
28258 | @code{make} in each of these directories builds the @code{gdb} | |
28259 | program specified there. | |
c906108c | 28260 | |
db2e3e2e | 28261 | To build @code{gdb} in a separate directory, run @file{configure} |
8e04817f | 28262 | with the @samp{--srcdir} option to specify where to find the source. |
db2e3e2e BW |
28263 | (You also need to specify a path to find @file{configure} |
28264 | itself from your working directory. If the path to @file{configure} | |
8e04817f AC |
28265 | would be the same as the argument to @samp{--srcdir}, you can leave out |
28266 | the @samp{--srcdir} option; it is assumed.) | |
c906108c | 28267 | |
8e04817f AC |
28268 | For example, with version @value{GDBVN}, you can build @value{GDBN} in a |
28269 | separate directory for a Sun 4 like this: | |
c906108c | 28270 | |
474c8240 | 28271 | @smallexample |
8e04817f AC |
28272 | @group |
28273 | cd gdb-@value{GDBVN} | |
28274 | mkdir ../gdb-sun4 | |
28275 | cd ../gdb-sun4 | |
28276 | ../gdb-@value{GDBVN}/configure sun4 | |
28277 | make | |
28278 | @end group | |
474c8240 | 28279 | @end smallexample |
c906108c | 28280 | |
db2e3e2e | 28281 | When @file{configure} builds a configuration using a remote source |
8e04817f AC |
28282 | directory, it creates a tree for the binaries with the same structure |
28283 | (and using the same names) as the tree under the source directory. In | |
28284 | the example, you'd find the Sun 4 library @file{libiberty.a} in the | |
28285 | directory @file{gdb-sun4/libiberty}, and @value{GDBN} itself in | |
28286 | @file{gdb-sun4/gdb}. | |
c906108c | 28287 | |
94e91d6d MC |
28288 | Make sure that your path to the @file{configure} script has just one |
28289 | instance of @file{gdb} in it. If your path to @file{configure} looks | |
28290 | like @file{../gdb-@value{GDBVN}/gdb/configure}, you are configuring only | |
28291 | one subdirectory of @value{GDBN}, not the whole package. This leads to | |
28292 | build errors about missing include files such as @file{bfd/bfd.h}. | |
28293 | ||
8e04817f AC |
28294 | One popular reason to build several @value{GDBN} configurations in separate |
28295 | directories is to configure @value{GDBN} for cross-compiling (where | |
28296 | @value{GDBN} runs on one machine---the @dfn{host}---while debugging | |
28297 | programs that run on another machine---the @dfn{target}). | |
28298 | You specify a cross-debugging target by | |
db2e3e2e | 28299 | giving the @samp{--target=@var{target}} option to @file{configure}. |
c906108c | 28300 | |
8e04817f AC |
28301 | When you run @code{make} to build a program or library, you must run |
28302 | it in a configured directory---whatever directory you were in when you | |
db2e3e2e | 28303 | called @file{configure} (or one of its subdirectories). |
c906108c | 28304 | |
db2e3e2e | 28305 | The @code{Makefile} that @file{configure} generates in each source |
8e04817f AC |
28306 | directory also runs recursively. If you type @code{make} in a source |
28307 | directory such as @file{gdb-@value{GDBVN}} (or in a separate configured | |
28308 | directory configured with @samp{--srcdir=@var{dirname}/gdb-@value{GDBVN}}), you | |
28309 | will build all the required libraries, and then build GDB. | |
c906108c | 28310 | |
8e04817f AC |
28311 | When you have multiple hosts or targets configured in separate |
28312 | directories, you can run @code{make} on them in parallel (for example, | |
28313 | if they are NFS-mounted on each of the hosts); they will not interfere | |
28314 | with each other. | |
c906108c | 28315 | |
8e04817f | 28316 | @node Config Names |
79a6e687 | 28317 | @section Specifying Names for Hosts and Targets |
c906108c | 28318 | |
db2e3e2e | 28319 | The specifications used for hosts and targets in the @file{configure} |
8e04817f AC |
28320 | script are based on a three-part naming scheme, but some short predefined |
28321 | aliases are also supported. The full naming scheme encodes three pieces | |
28322 | of information in the following pattern: | |
c906108c | 28323 | |
474c8240 | 28324 | @smallexample |
8e04817f | 28325 | @var{architecture}-@var{vendor}-@var{os} |
474c8240 | 28326 | @end smallexample |
c906108c | 28327 | |
8e04817f AC |
28328 | For example, you can use the alias @code{sun4} as a @var{host} argument, |
28329 | or as the value for @var{target} in a @code{--target=@var{target}} | |
28330 | option. The equivalent full name is @samp{sparc-sun-sunos4}. | |
c906108c | 28331 | |
db2e3e2e | 28332 | The @file{configure} script accompanying @value{GDBN} does not provide |
8e04817f | 28333 | any query facility to list all supported host and target names or |
db2e3e2e | 28334 | aliases. @file{configure} calls the Bourne shell script |
8e04817f AC |
28335 | @code{config.sub} to map abbreviations to full names; you can read the |
28336 | script, if you wish, or you can use it to test your guesses on | |
28337 | abbreviations---for example: | |
c906108c | 28338 | |
8e04817f AC |
28339 | @smallexample |
28340 | % sh config.sub i386-linux | |
28341 | i386-pc-linux-gnu | |
28342 | % sh config.sub alpha-linux | |
28343 | alpha-unknown-linux-gnu | |
28344 | % sh config.sub hp9k700 | |
28345 | hppa1.1-hp-hpux | |
28346 | % sh config.sub sun4 | |
28347 | sparc-sun-sunos4.1.1 | |
28348 | % sh config.sub sun3 | |
28349 | m68k-sun-sunos4.1.1 | |
28350 | % sh config.sub i986v | |
28351 | Invalid configuration `i986v': machine `i986v' not recognized | |
28352 | @end smallexample | |
c906108c | 28353 | |
8e04817f AC |
28354 | @noindent |
28355 | @code{config.sub} is also distributed in the @value{GDBN} source | |
28356 | directory (@file{gdb-@value{GDBVN}}, for version @value{GDBVN}). | |
d700128c | 28357 | |
8e04817f | 28358 | @node Configure Options |
db2e3e2e | 28359 | @section @file{configure} Options |
c906108c | 28360 | |
db2e3e2e BW |
28361 | Here is a summary of the @file{configure} options and arguments that |
28362 | are most often useful for building @value{GDBN}. @file{configure} also has | |
8e04817f | 28363 | several other options not listed here. @inforef{What Configure |
db2e3e2e | 28364 | Does,,configure.info}, for a full explanation of @file{configure}. |
c906108c | 28365 | |
474c8240 | 28366 | @smallexample |
8e04817f AC |
28367 | configure @r{[}--help@r{]} |
28368 | @r{[}--prefix=@var{dir}@r{]} | |
28369 | @r{[}--exec-prefix=@var{dir}@r{]} | |
28370 | @r{[}--srcdir=@var{dirname}@r{]} | |
28371 | @r{[}--norecursion@r{]} @r{[}--rm@r{]} | |
28372 | @r{[}--target=@var{target}@r{]} | |
28373 | @var{host} | |
474c8240 | 28374 | @end smallexample |
c906108c | 28375 | |
8e04817f AC |
28376 | @noindent |
28377 | You may introduce options with a single @samp{-} rather than | |
28378 | @samp{--} if you prefer; but you may abbreviate option names if you use | |
28379 | @samp{--}. | |
c906108c | 28380 | |
8e04817f AC |
28381 | @table @code |
28382 | @item --help | |
db2e3e2e | 28383 | Display a quick summary of how to invoke @file{configure}. |
c906108c | 28384 | |
8e04817f AC |
28385 | @item --prefix=@var{dir} |
28386 | Configure the source to install programs and files under directory | |
28387 | @file{@var{dir}}. | |
c906108c | 28388 | |
8e04817f AC |
28389 | @item --exec-prefix=@var{dir} |
28390 | Configure the source to install programs under directory | |
28391 | @file{@var{dir}}. | |
c906108c | 28392 | |
8e04817f AC |
28393 | @c avoid splitting the warning from the explanation: |
28394 | @need 2000 | |
28395 | @item --srcdir=@var{dirname} | |
28396 | @strong{Warning: using this option requires @sc{gnu} @code{make}, or another | |
28397 | @code{make} that implements the @code{VPATH} feature.}@* | |
28398 | Use this option to make configurations in directories separate from the | |
28399 | @value{GDBN} source directories. Among other things, you can use this to | |
28400 | build (or maintain) several configurations simultaneously, in separate | |
db2e3e2e | 28401 | directories. @file{configure} writes configuration-specific files in |
8e04817f | 28402 | the current directory, but arranges for them to use the source in the |
db2e3e2e | 28403 | directory @var{dirname}. @file{configure} creates directories under |
8e04817f AC |
28404 | the working directory in parallel to the source directories below |
28405 | @var{dirname}. | |
c906108c | 28406 | |
8e04817f | 28407 | @item --norecursion |
db2e3e2e | 28408 | Configure only the directory level where @file{configure} is executed; do not |
8e04817f | 28409 | propagate configuration to subdirectories. |
c906108c | 28410 | |
8e04817f AC |
28411 | @item --target=@var{target} |
28412 | Configure @value{GDBN} for cross-debugging programs running on the specified | |
28413 | @var{target}. Without this option, @value{GDBN} is configured to debug | |
28414 | programs that run on the same machine (@var{host}) as @value{GDBN} itself. | |
c906108c | 28415 | |
8e04817f | 28416 | There is no convenient way to generate a list of all available targets. |
c906108c | 28417 | |
8e04817f AC |
28418 | @item @var{host} @dots{} |
28419 | Configure @value{GDBN} to run on the specified @var{host}. | |
c906108c | 28420 | |
8e04817f AC |
28421 | There is no convenient way to generate a list of all available hosts. |
28422 | @end table | |
c906108c | 28423 | |
8e04817f AC |
28424 | There are many other options available as well, but they are generally |
28425 | needed for special purposes only. | |
c906108c | 28426 | |
098b41a6 JG |
28427 | @node System-wide configuration |
28428 | @section System-wide configuration and settings | |
28429 | @cindex system-wide init file | |
28430 | ||
28431 | @value{GDBN} can be configured to have a system-wide init file; | |
28432 | this file will be read and executed at startup (@pxref{Startup, , What | |
28433 | @value{GDBN} does during startup}). | |
28434 | ||
28435 | Here is the corresponding configure option: | |
28436 | ||
28437 | @table @code | |
28438 | @item --with-system-gdbinit=@var{file} | |
28439 | Specify that the default location of the system-wide init file is | |
28440 | @var{file}. | |
28441 | @end table | |
28442 | ||
28443 | If @value{GDBN} has been configured with the option @option{--prefix=$prefix}, | |
28444 | it may be subject to relocation. Two possible cases: | |
28445 | ||
28446 | @itemize @bullet | |
28447 | @item | |
28448 | If the default location of this init file contains @file{$prefix}, | |
28449 | it will be subject to relocation. Suppose that the configure options | |
28450 | are @option{--prefix=$prefix --with-system-gdbinit=$prefix/etc/gdbinit}; | |
28451 | if @value{GDBN} is moved from @file{$prefix} to @file{$install}, the system | |
28452 | init file is looked for as @file{$install/etc/gdbinit} instead of | |
28453 | @file{$prefix/etc/gdbinit}. | |
28454 | ||
28455 | @item | |
28456 | By contrast, if the default location does not contain the prefix, | |
28457 | it will not be relocated. E.g.@: if @value{GDBN} has been configured with | |
28458 | @option{--prefix=/usr/local --with-system-gdbinit=/usr/share/gdb/gdbinit}, | |
28459 | then @value{GDBN} will always look for @file{/usr/share/gdb/gdbinit}, | |
28460 | wherever @value{GDBN} is installed. | |
28461 | @end itemize | |
28462 | ||
8e04817f AC |
28463 | @node Maintenance Commands |
28464 | @appendix Maintenance Commands | |
28465 | @cindex maintenance commands | |
28466 | @cindex internal commands | |
c906108c | 28467 | |
8e04817f | 28468 | In addition to commands intended for @value{GDBN} users, @value{GDBN} |
09d4efe1 EZ |
28469 | includes a number of commands intended for @value{GDBN} developers, |
28470 | that are not documented elsewhere in this manual. These commands are | |
da316a69 EZ |
28471 | provided here for reference. (For commands that turn on debugging |
28472 | messages, see @ref{Debugging Output}.) | |
c906108c | 28473 | |
8e04817f | 28474 | @table @code |
09d4efe1 | 28475 | @kindex maint agent |
782b2b07 | 28476 | @kindex maint agent-eval |
09d4efe1 | 28477 | @item maint agent @var{expression} |
782b2b07 | 28478 | @itemx maint agent-eval @var{expression} |
09d4efe1 EZ |
28479 | Translate the given @var{expression} into remote agent bytecodes. |
28480 | This command is useful for debugging the Agent Expression mechanism | |
782b2b07 SS |
28481 | (@pxref{Agent Expressions}). The @samp{agent} version produces an |
28482 | expression useful for data collection, such as by tracepoints, while | |
28483 | @samp{maint agent-eval} produces an expression that evaluates directly | |
28484 | to a result. For instance, a collection expression for @code{globa + | |
28485 | globb} will include bytecodes to record four bytes of memory at each | |
28486 | of the addresses of @code{globa} and @code{globb}, while discarding | |
28487 | the result of the addition, while an evaluation expression will do the | |
28488 | addition and return the sum. | |
09d4efe1 | 28489 | |
8e04817f AC |
28490 | @kindex maint info breakpoints |
28491 | @item @anchor{maint info breakpoints}maint info breakpoints | |
28492 | Using the same format as @samp{info breakpoints}, display both the | |
28493 | breakpoints you've set explicitly, and those @value{GDBN} is using for | |
28494 | internal purposes. Internal breakpoints are shown with negative | |
28495 | breakpoint numbers. The type column identifies what kind of breakpoint | |
28496 | is shown: | |
c906108c | 28497 | |
8e04817f AC |
28498 | @table @code |
28499 | @item breakpoint | |
28500 | Normal, explicitly set breakpoint. | |
c906108c | 28501 | |
8e04817f AC |
28502 | @item watchpoint |
28503 | Normal, explicitly set watchpoint. | |
c906108c | 28504 | |
8e04817f AC |
28505 | @item longjmp |
28506 | Internal breakpoint, used to handle correctly stepping through | |
28507 | @code{longjmp} calls. | |
c906108c | 28508 | |
8e04817f AC |
28509 | @item longjmp resume |
28510 | Internal breakpoint at the target of a @code{longjmp}. | |
c906108c | 28511 | |
8e04817f AC |
28512 | @item until |
28513 | Temporary internal breakpoint used by the @value{GDBN} @code{until} command. | |
c906108c | 28514 | |
8e04817f AC |
28515 | @item finish |
28516 | Temporary internal breakpoint used by the @value{GDBN} @code{finish} command. | |
c906108c | 28517 | |
8e04817f AC |
28518 | @item shlib events |
28519 | Shared library events. | |
c906108c | 28520 | |
8e04817f | 28521 | @end table |
c906108c | 28522 | |
fff08868 HZ |
28523 | @kindex set displaced-stepping |
28524 | @kindex show displaced-stepping | |
237fc4c9 PA |
28525 | @cindex displaced stepping support |
28526 | @cindex out-of-line single-stepping | |
fff08868 HZ |
28527 | @item set displaced-stepping |
28528 | @itemx show displaced-stepping | |
237fc4c9 | 28529 | Control whether or not @value{GDBN} will do @dfn{displaced stepping} |
fff08868 HZ |
28530 | if the target supports it. Displaced stepping is a way to single-step |
28531 | over breakpoints without removing them from the inferior, by executing | |
28532 | an out-of-line copy of the instruction that was originally at the | |
28533 | breakpoint location. It is also known as out-of-line single-stepping. | |
28534 | ||
28535 | @table @code | |
28536 | @item set displaced-stepping on | |
28537 | If the target architecture supports it, @value{GDBN} will use | |
28538 | displaced stepping to step over breakpoints. | |
28539 | ||
28540 | @item set displaced-stepping off | |
28541 | @value{GDBN} will not use displaced stepping to step over breakpoints, | |
28542 | even if such is supported by the target architecture. | |
28543 | ||
28544 | @cindex non-stop mode, and @samp{set displaced-stepping} | |
28545 | @item set displaced-stepping auto | |
28546 | This is the default mode. @value{GDBN} will use displaced stepping | |
28547 | only if non-stop mode is active (@pxref{Non-Stop Mode}) and the target | |
28548 | architecture supports displaced stepping. | |
28549 | @end table | |
237fc4c9 | 28550 | |
09d4efe1 EZ |
28551 | @kindex maint check-symtabs |
28552 | @item maint check-symtabs | |
28553 | Check the consistency of psymtabs and symtabs. | |
28554 | ||
28555 | @kindex maint cplus first_component | |
28556 | @item maint cplus first_component @var{name} | |
28557 | Print the first C@t{++} class/namespace component of @var{name}. | |
28558 | ||
28559 | @kindex maint cplus namespace | |
28560 | @item maint cplus namespace | |
28561 | Print the list of possible C@t{++} namespaces. | |
28562 | ||
28563 | @kindex maint demangle | |
28564 | @item maint demangle @var{name} | |
d3e8051b | 28565 | Demangle a C@t{++} or Objective-C mangled @var{name}. |
09d4efe1 EZ |
28566 | |
28567 | @kindex maint deprecate | |
28568 | @kindex maint undeprecate | |
28569 | @cindex deprecated commands | |
28570 | @item maint deprecate @var{command} @r{[}@var{replacement}@r{]} | |
28571 | @itemx maint undeprecate @var{command} | |
28572 | Deprecate or undeprecate the named @var{command}. Deprecated commands | |
28573 | cause @value{GDBN} to issue a warning when you use them. The optional | |
28574 | argument @var{replacement} says which newer command should be used in | |
28575 | favor of the deprecated one; if it is given, @value{GDBN} will mention | |
28576 | the replacement as part of the warning. | |
28577 | ||
28578 | @kindex maint dump-me | |
28579 | @item maint dump-me | |
721c2651 | 28580 | @cindex @code{SIGQUIT} signal, dump core of @value{GDBN} |
09d4efe1 | 28581 | Cause a fatal signal in the debugger and force it to dump its core. |
721c2651 EZ |
28582 | This is supported only on systems which support aborting a program |
28583 | with the @code{SIGQUIT} signal. | |
09d4efe1 | 28584 | |
8d30a00d AC |
28585 | @kindex maint internal-error |
28586 | @kindex maint internal-warning | |
09d4efe1 EZ |
28587 | @item maint internal-error @r{[}@var{message-text}@r{]} |
28588 | @itemx maint internal-warning @r{[}@var{message-text}@r{]} | |
8d30a00d AC |
28589 | Cause @value{GDBN} to call the internal function @code{internal_error} |
28590 | or @code{internal_warning} and hence behave as though an internal error | |
28591 | or internal warning has been detected. In addition to reporting the | |
28592 | internal problem, these functions give the user the opportunity to | |
28593 | either quit @value{GDBN} or create a core file of the current | |
28594 | @value{GDBN} session. | |
28595 | ||
09d4efe1 EZ |
28596 | These commands take an optional parameter @var{message-text} that is |
28597 | used as the text of the error or warning message. | |
28598 | ||
d3e8051b | 28599 | Here's an example of using @code{internal-error}: |
09d4efe1 | 28600 | |
8d30a00d | 28601 | @smallexample |
f7dc1244 | 28602 | (@value{GDBP}) @kbd{maint internal-error testing, 1, 2} |
8d30a00d AC |
28603 | @dots{}/maint.c:121: internal-error: testing, 1, 2 |
28604 | A problem internal to GDB has been detected. Further | |
28605 | debugging may prove unreliable. | |
28606 | Quit this debugging session? (y or n) @kbd{n} | |
28607 | Create a core file? (y or n) @kbd{n} | |
f7dc1244 | 28608 | (@value{GDBP}) |
8d30a00d AC |
28609 | @end smallexample |
28610 | ||
3c16cced PA |
28611 | @cindex @value{GDBN} internal error |
28612 | @cindex internal errors, control of @value{GDBN} behavior | |
28613 | ||
28614 | @kindex maint set internal-error | |
28615 | @kindex maint show internal-error | |
28616 | @kindex maint set internal-warning | |
28617 | @kindex maint show internal-warning | |
28618 | @item maint set internal-error @var{action} [ask|yes|no] | |
28619 | @itemx maint show internal-error @var{action} | |
28620 | @itemx maint set internal-warning @var{action} [ask|yes|no] | |
28621 | @itemx maint show internal-warning @var{action} | |
28622 | When @value{GDBN} reports an internal problem (error or warning) it | |
28623 | gives the user the opportunity to both quit @value{GDBN} and create a | |
28624 | core file of the current @value{GDBN} session. These commands let you | |
28625 | override the default behaviour for each particular @var{action}, | |
28626 | described in the table below. | |
28627 | ||
28628 | @table @samp | |
28629 | @item quit | |
28630 | You can specify that @value{GDBN} should always (yes) or never (no) | |
28631 | quit. The default is to ask the user what to do. | |
28632 | ||
28633 | @item corefile | |
28634 | You can specify that @value{GDBN} should always (yes) or never (no) | |
28635 | create a core file. The default is to ask the user what to do. | |
28636 | @end table | |
28637 | ||
09d4efe1 EZ |
28638 | @kindex maint packet |
28639 | @item maint packet @var{text} | |
28640 | If @value{GDBN} is talking to an inferior via the serial protocol, | |
28641 | then this command sends the string @var{text} to the inferior, and | |
28642 | displays the response packet. @value{GDBN} supplies the initial | |
28643 | @samp{$} character, the terminating @samp{#} character, and the | |
28644 | checksum. | |
28645 | ||
28646 | @kindex maint print architecture | |
28647 | @item maint print architecture @r{[}@var{file}@r{]} | |
28648 | Print the entire architecture configuration. The optional argument | |
28649 | @var{file} names the file where the output goes. | |
8d30a00d | 28650 | |
81adfced DJ |
28651 | @kindex maint print c-tdesc |
28652 | @item maint print c-tdesc | |
28653 | Print the current target description (@pxref{Target Descriptions}) as | |
28654 | a C source file. The created source file can be used in @value{GDBN} | |
28655 | when an XML parser is not available to parse the description. | |
28656 | ||
00905d52 AC |
28657 | @kindex maint print dummy-frames |
28658 | @item maint print dummy-frames | |
00905d52 AC |
28659 | Prints the contents of @value{GDBN}'s internal dummy-frame stack. |
28660 | ||
28661 | @smallexample | |
f7dc1244 | 28662 | (@value{GDBP}) @kbd{b add} |
00905d52 | 28663 | @dots{} |
f7dc1244 | 28664 | (@value{GDBP}) @kbd{print add(2,3)} |
00905d52 AC |
28665 | Breakpoint 2, add (a=2, b=3) at @dots{} |
28666 | 58 return (a + b); | |
28667 | The program being debugged stopped while in a function called from GDB. | |
28668 | @dots{} | |
f7dc1244 | 28669 | (@value{GDBP}) @kbd{maint print dummy-frames} |
00905d52 AC |
28670 | 0x1a57c80: pc=0x01014068 fp=0x0200bddc sp=0x0200bdd6 |
28671 | top=0x0200bdd4 id=@{stack=0x200bddc,code=0x101405c@} | |
28672 | call_lo=0x01014000 call_hi=0x01014001 | |
f7dc1244 | 28673 | (@value{GDBP}) |
00905d52 AC |
28674 | @end smallexample |
28675 | ||
28676 | Takes an optional file parameter. | |
28677 | ||
0680b120 AC |
28678 | @kindex maint print registers |
28679 | @kindex maint print raw-registers | |
28680 | @kindex maint print cooked-registers | |
617073a9 | 28681 | @kindex maint print register-groups |
09d4efe1 EZ |
28682 | @item maint print registers @r{[}@var{file}@r{]} |
28683 | @itemx maint print raw-registers @r{[}@var{file}@r{]} | |
28684 | @itemx maint print cooked-registers @r{[}@var{file}@r{]} | |
28685 | @itemx maint print register-groups @r{[}@var{file}@r{]} | |
0680b120 AC |
28686 | Print @value{GDBN}'s internal register data structures. |
28687 | ||
617073a9 AC |
28688 | The command @code{maint print raw-registers} includes the contents of |
28689 | the raw register cache; the command @code{maint print cooked-registers} | |
28690 | includes the (cooked) value of all registers; and the command | |
28691 | @code{maint print register-groups} includes the groups that each | |
28692 | register is a member of. @xref{Registers,, Registers, gdbint, | |
28693 | @value{GDBN} Internals}. | |
0680b120 | 28694 | |
09d4efe1 EZ |
28695 | These commands take an optional parameter, a file name to which to |
28696 | write the information. | |
0680b120 | 28697 | |
617073a9 | 28698 | @kindex maint print reggroups |
09d4efe1 EZ |
28699 | @item maint print reggroups @r{[}@var{file}@r{]} |
28700 | Print @value{GDBN}'s internal register group data structures. The | |
28701 | optional argument @var{file} tells to what file to write the | |
28702 | information. | |
617073a9 | 28703 | |
09d4efe1 | 28704 | The register groups info looks like this: |
617073a9 AC |
28705 | |
28706 | @smallexample | |
f7dc1244 | 28707 | (@value{GDBP}) @kbd{maint print reggroups} |
b383017d RM |
28708 | Group Type |
28709 | general user | |
28710 | float user | |
28711 | all user | |
28712 | vector user | |
28713 | system user | |
28714 | save internal | |
28715 | restore internal | |
617073a9 AC |
28716 | @end smallexample |
28717 | ||
09d4efe1 EZ |
28718 | @kindex flushregs |
28719 | @item flushregs | |
28720 | This command forces @value{GDBN} to flush its internal register cache. | |
28721 | ||
28722 | @kindex maint print objfiles | |
28723 | @cindex info for known object files | |
28724 | @item maint print objfiles | |
28725 | Print a dump of all known object files. For each object file, this | |
28726 | command prints its name, address in memory, and all of its psymtabs | |
28727 | and symtabs. | |
28728 | ||
28729 | @kindex maint print statistics | |
28730 | @cindex bcache statistics | |
28731 | @item maint print statistics | |
28732 | This command prints, for each object file in the program, various data | |
28733 | about that object file followed by the byte cache (@dfn{bcache}) | |
28734 | statistics for the object file. The objfile data includes the number | |
d3e8051b | 28735 | of minimal, partial, full, and stabs symbols, the number of types |
09d4efe1 EZ |
28736 | defined by the objfile, the number of as yet unexpanded psym tables, |
28737 | the number of line tables and string tables, and the amount of memory | |
28738 | used by the various tables. The bcache statistics include the counts, | |
28739 | sizes, and counts of duplicates of all and unique objects, max, | |
28740 | average, and median entry size, total memory used and its overhead and | |
28741 | savings, and various measures of the hash table size and chain | |
28742 | lengths. | |
28743 | ||
c7ba131e JB |
28744 | @kindex maint print target-stack |
28745 | @cindex target stack description | |
28746 | @item maint print target-stack | |
28747 | A @dfn{target} is an interface between the debugger and a particular | |
28748 | kind of file or process. Targets can be stacked in @dfn{strata}, | |
28749 | so that more than one target can potentially respond to a request. | |
28750 | In particular, memory accesses will walk down the stack of targets | |
28751 | until they find a target that is interested in handling that particular | |
28752 | address. | |
28753 | ||
28754 | This command prints a short description of each layer that was pushed on | |
28755 | the @dfn{target stack}, starting from the top layer down to the bottom one. | |
28756 | ||
09d4efe1 EZ |
28757 | @kindex maint print type |
28758 | @cindex type chain of a data type | |
28759 | @item maint print type @var{expr} | |
28760 | Print the type chain for a type specified by @var{expr}. The argument | |
28761 | can be either a type name or a symbol. If it is a symbol, the type of | |
28762 | that symbol is described. The type chain produced by this command is | |
28763 | a recursive definition of the data type as stored in @value{GDBN}'s | |
28764 | data structures, including its flags and contained types. | |
28765 | ||
28766 | @kindex maint set dwarf2 max-cache-age | |
28767 | @kindex maint show dwarf2 max-cache-age | |
28768 | @item maint set dwarf2 max-cache-age | |
28769 | @itemx maint show dwarf2 max-cache-age | |
28770 | Control the DWARF 2 compilation unit cache. | |
28771 | ||
28772 | @cindex DWARF 2 compilation units cache | |
28773 | In object files with inter-compilation-unit references, such as those | |
28774 | produced by the GCC option @samp{-feliminate-dwarf2-dups}, the DWARF 2 | |
28775 | reader needs to frequently refer to previously read compilation units. | |
28776 | This setting controls how long a compilation unit will remain in the | |
28777 | cache if it is not referenced. A higher limit means that cached | |
28778 | compilation units will be stored in memory longer, and more total | |
28779 | memory will be used. Setting it to zero disables caching, which will | |
28780 | slow down @value{GDBN} startup, but reduce memory consumption. | |
28781 | ||
e7ba9c65 DJ |
28782 | @kindex maint set profile |
28783 | @kindex maint show profile | |
28784 | @cindex profiling GDB | |
28785 | @item maint set profile | |
28786 | @itemx maint show profile | |
28787 | Control profiling of @value{GDBN}. | |
28788 | ||
28789 | Profiling will be disabled until you use the @samp{maint set profile} | |
28790 | command to enable it. When you enable profiling, the system will begin | |
28791 | collecting timing and execution count data; when you disable profiling or | |
28792 | exit @value{GDBN}, the results will be written to a log file. Remember that | |
28793 | if you use profiling, @value{GDBN} will overwrite the profiling log file | |
28794 | (often called @file{gmon.out}). If you have a record of important profiling | |
28795 | data in a @file{gmon.out} file, be sure to move it to a safe location. | |
28796 | ||
28797 | Configuring with @samp{--enable-profiling} arranges for @value{GDBN} to be | |
b383017d | 28798 | compiled with the @samp{-pg} compiler option. |
e7ba9c65 | 28799 | |
cbe54154 PA |
28800 | @kindex maint set show-debug-regs |
28801 | @kindex maint show show-debug-regs | |
eac35c4e | 28802 | @cindex hardware debug registers |
cbe54154 PA |
28803 | @item maint set show-debug-regs |
28804 | @itemx maint show show-debug-regs | |
eac35c4e | 28805 | Control whether to show variables that mirror the hardware debug |
09d4efe1 | 28806 | registers. Use @code{ON} to enable, @code{OFF} to disable. If |
3f94c067 | 28807 | enabled, the debug registers values are shown when @value{GDBN} inserts or |
09d4efe1 EZ |
28808 | removes a hardware breakpoint or watchpoint, and when the inferior |
28809 | triggers a hardware-assisted breakpoint or watchpoint. | |
28810 | ||
28811 | @kindex maint space | |
28812 | @cindex memory used by commands | |
28813 | @item maint space | |
28814 | Control whether to display memory usage for each command. If set to a | |
28815 | nonzero value, @value{GDBN} will display how much memory each command | |
28816 | took, following the command's own output. This can also be requested | |
28817 | by invoking @value{GDBN} with the @option{--statistics} command-line | |
28818 | switch (@pxref{Mode Options}). | |
28819 | ||
28820 | @kindex maint time | |
28821 | @cindex time of command execution | |
28822 | @item maint time | |
28823 | Control whether to display the execution time for each command. If | |
28824 | set to a nonzero value, @value{GDBN} will display how much time it | |
28825 | took to execute each command, following the command's own output. | |
e2b7ddea VP |
28826 | The time is not printed for the commands that run the target, since |
28827 | there's no mechanism currently to compute how much time was spend | |
28828 | by @value{GDBN} and how much time was spend by the program been debugged. | |
28829 | it's not possibly currently | |
09d4efe1 EZ |
28830 | This can also be requested by invoking @value{GDBN} with the |
28831 | @option{--statistics} command-line switch (@pxref{Mode Options}). | |
28832 | ||
28833 | @kindex maint translate-address | |
28834 | @item maint translate-address @r{[}@var{section}@r{]} @var{addr} | |
28835 | Find the symbol stored at the location specified by the address | |
28836 | @var{addr} and an optional section name @var{section}. If found, | |
28837 | @value{GDBN} prints the name of the closest symbol and an offset from | |
28838 | the symbol's location to the specified address. This is similar to | |
28839 | the @code{info address} command (@pxref{Symbols}), except that this | |
28840 | command also allows to find symbols in other sections. | |
ae038cb0 | 28841 | |
c14c28ba PP |
28842 | If section was not specified, the section in which the symbol was found |
28843 | is also printed. For dynamically linked executables, the name of | |
28844 | executable or shared library containing the symbol is printed as well. | |
28845 | ||
8e04817f | 28846 | @end table |
c906108c | 28847 | |
9c16f35a EZ |
28848 | The following command is useful for non-interactive invocations of |
28849 | @value{GDBN}, such as in the test suite. | |
28850 | ||
28851 | @table @code | |
28852 | @item set watchdog @var{nsec} | |
28853 | @kindex set watchdog | |
28854 | @cindex watchdog timer | |
28855 | @cindex timeout for commands | |
28856 | Set the maximum number of seconds @value{GDBN} will wait for the | |
28857 | target operation to finish. If this time expires, @value{GDBN} | |
28858 | reports and error and the command is aborted. | |
28859 | ||
28860 | @item show watchdog | |
28861 | Show the current setting of the target wait timeout. | |
28862 | @end table | |
c906108c | 28863 | |
e0ce93ac | 28864 | @node Remote Protocol |
8e04817f | 28865 | @appendix @value{GDBN} Remote Serial Protocol |
c906108c | 28866 | |
ee2d5c50 AC |
28867 | @menu |
28868 | * Overview:: | |
28869 | * Packets:: | |
28870 | * Stop Reply Packets:: | |
28871 | * General Query Packets:: | |
a1dcb23a | 28872 | * Architecture-Specific Protocol Details:: |
9d29849a | 28873 | * Tracepoint Packets:: |
a6b151f1 | 28874 | * Host I/O Packets:: |
9a6253be | 28875 | * Interrupts:: |
8b23ecc4 SL |
28876 | * Notification Packets:: |
28877 | * Remote Non-Stop:: | |
a6f3e723 | 28878 | * Packet Acknowledgment:: |
ee2d5c50 | 28879 | * Examples:: |
79a6e687 | 28880 | * File-I/O Remote Protocol Extension:: |
cfa9d6d9 | 28881 | * Library List Format:: |
79a6e687 | 28882 | * Memory Map Format:: |
dc146f7c | 28883 | * Thread List Format:: |
ee2d5c50 AC |
28884 | @end menu |
28885 | ||
28886 | @node Overview | |
28887 | @section Overview | |
28888 | ||
8e04817f AC |
28889 | There may be occasions when you need to know something about the |
28890 | protocol---for example, if there is only one serial port to your target | |
28891 | machine, you might want your program to do something special if it | |
28892 | recognizes a packet meant for @value{GDBN}. | |
c906108c | 28893 | |
d2c6833e | 28894 | In the examples below, @samp{->} and @samp{<-} are used to indicate |
bf06d120 | 28895 | transmitted and received data, respectively. |
c906108c | 28896 | |
8e04817f AC |
28897 | @cindex protocol, @value{GDBN} remote serial |
28898 | @cindex serial protocol, @value{GDBN} remote | |
28899 | @cindex remote serial protocol | |
8b23ecc4 SL |
28900 | All @value{GDBN} commands and responses (other than acknowledgments |
28901 | and notifications, see @ref{Notification Packets}) are sent as a | |
28902 | @var{packet}. A @var{packet} is introduced with the character | |
8e04817f AC |
28903 | @samp{$}, the actual @var{packet-data}, and the terminating character |
28904 | @samp{#} followed by a two-digit @var{checksum}: | |
c906108c | 28905 | |
474c8240 | 28906 | @smallexample |
8e04817f | 28907 | @code{$}@var{packet-data}@code{#}@var{checksum} |
474c8240 | 28908 | @end smallexample |
8e04817f | 28909 | @noindent |
c906108c | 28910 | |
8e04817f AC |
28911 | @cindex checksum, for @value{GDBN} remote |
28912 | @noindent | |
28913 | The two-digit @var{checksum} is computed as the modulo 256 sum of all | |
28914 | characters between the leading @samp{$} and the trailing @samp{#} (an | |
28915 | eight bit unsigned checksum). | |
c906108c | 28916 | |
8e04817f AC |
28917 | Implementors should note that prior to @value{GDBN} 5.0 the protocol |
28918 | specification also included an optional two-digit @var{sequence-id}: | |
c906108c | 28919 | |
474c8240 | 28920 | @smallexample |
8e04817f | 28921 | @code{$}@var{sequence-id}@code{:}@var{packet-data}@code{#}@var{checksum} |
474c8240 | 28922 | @end smallexample |
c906108c | 28923 | |
8e04817f AC |
28924 | @cindex sequence-id, for @value{GDBN} remote |
28925 | @noindent | |
28926 | That @var{sequence-id} was appended to the acknowledgment. @value{GDBN} | |
28927 | has never output @var{sequence-id}s. Stubs that handle packets added | |
28928 | since @value{GDBN} 5.0 must not accept @var{sequence-id}. | |
c906108c | 28929 | |
8e04817f AC |
28930 | When either the host or the target machine receives a packet, the first |
28931 | response expected is an acknowledgment: either @samp{+} (to indicate | |
28932 | the package was received correctly) or @samp{-} (to request | |
28933 | retransmission): | |
c906108c | 28934 | |
474c8240 | 28935 | @smallexample |
d2c6833e AC |
28936 | -> @code{$}@var{packet-data}@code{#}@var{checksum} |
28937 | <- @code{+} | |
474c8240 | 28938 | @end smallexample |
8e04817f | 28939 | @noindent |
53a5351d | 28940 | |
a6f3e723 SL |
28941 | The @samp{+}/@samp{-} acknowledgments can be disabled |
28942 | once a connection is established. | |
28943 | @xref{Packet Acknowledgment}, for details. | |
28944 | ||
8e04817f AC |
28945 | The host (@value{GDBN}) sends @var{command}s, and the target (the |
28946 | debugging stub incorporated in your program) sends a @var{response}. In | |
28947 | the case of step and continue @var{command}s, the response is only sent | |
8b23ecc4 SL |
28948 | when the operation has completed, and the target has again stopped all |
28949 | threads in all attached processes. This is the default all-stop mode | |
28950 | behavior, but the remote protocol also supports @value{GDBN}'s non-stop | |
28951 | execution mode; see @ref{Remote Non-Stop}, for details. | |
c906108c | 28952 | |
8e04817f AC |
28953 | @var{packet-data} consists of a sequence of characters with the |
28954 | exception of @samp{#} and @samp{$} (see @samp{X} packet for additional | |
28955 | exceptions). | |
c906108c | 28956 | |
ee2d5c50 | 28957 | @cindex remote protocol, field separator |
0876f84a | 28958 | Fields within the packet should be separated using @samp{,} @samp{;} or |
8e04817f | 28959 | @samp{:}. Except where otherwise noted all numbers are represented in |
ee2d5c50 | 28960 | @sc{hex} with leading zeros suppressed. |
c906108c | 28961 | |
8e04817f AC |
28962 | Implementors should note that prior to @value{GDBN} 5.0, the character |
28963 | @samp{:} could not appear as the third character in a packet (as it | |
28964 | would potentially conflict with the @var{sequence-id}). | |
c906108c | 28965 | |
0876f84a DJ |
28966 | @cindex remote protocol, binary data |
28967 | @anchor{Binary Data} | |
28968 | Binary data in most packets is encoded either as two hexadecimal | |
28969 | digits per byte of binary data. This allowed the traditional remote | |
28970 | protocol to work over connections which were only seven-bit clean. | |
28971 | Some packets designed more recently assume an eight-bit clean | |
28972 | connection, and use a more efficient encoding to send and receive | |
28973 | binary data. | |
28974 | ||
28975 | The binary data representation uses @code{7d} (@sc{ascii} @samp{@}}) | |
28976 | as an escape character. Any escaped byte is transmitted as the escape | |
28977 | character followed by the original character XORed with @code{0x20}. | |
28978 | For example, the byte @code{0x7d} would be transmitted as the two | |
28979 | bytes @code{0x7d 0x5d}. The bytes @code{0x23} (@sc{ascii} @samp{#}), | |
28980 | @code{0x24} (@sc{ascii} @samp{$}), and @code{0x7d} (@sc{ascii} | |
28981 | @samp{@}}) must always be escaped. Responses sent by the stub | |
28982 | must also escape @code{0x2a} (@sc{ascii} @samp{*}), so that it | |
28983 | is not interpreted as the start of a run-length encoded sequence | |
28984 | (described next). | |
28985 | ||
1d3811f6 DJ |
28986 | Response @var{data} can be run-length encoded to save space. |
28987 | Run-length encoding replaces runs of identical characters with one | |
28988 | instance of the repeated character, followed by a @samp{*} and a | |
28989 | repeat count. The repeat count is itself sent encoded, to avoid | |
28990 | binary characters in @var{data}: a value of @var{n} is sent as | |
28991 | @code{@var{n}+29}. For a repeat count greater or equal to 3, this | |
28992 | produces a printable @sc{ascii} character, e.g.@: a space (@sc{ascii} | |
28993 | code 32) for a repeat count of 3. (This is because run-length | |
28994 | encoding starts to win for counts 3 or more.) Thus, for example, | |
28995 | @samp{0* } is a run-length encoding of ``0000'': the space character | |
28996 | after @samp{*} means repeat the leading @code{0} @w{@code{32 - 29 = | |
28997 | 3}} more times. | |
28998 | ||
28999 | The printable characters @samp{#} and @samp{$} or with a numeric value | |
29000 | greater than 126 must not be used. Runs of six repeats (@samp{#}) or | |
29001 | seven repeats (@samp{$}) can be expanded using a repeat count of only | |
29002 | five (@samp{"}). For example, @samp{00000000} can be encoded as | |
29003 | @samp{0*"00}. | |
c906108c | 29004 | |
8e04817f AC |
29005 | The error response returned for some packets includes a two character |
29006 | error number. That number is not well defined. | |
c906108c | 29007 | |
f8da2bff | 29008 | @cindex empty response, for unsupported packets |
8e04817f AC |
29009 | For any @var{command} not supported by the stub, an empty response |
29010 | (@samp{$#00}) should be returned. That way it is possible to extend the | |
29011 | protocol. A newer @value{GDBN} can tell if a packet is supported based | |
29012 | on that response. | |
c906108c | 29013 | |
b383017d RM |
29014 | A stub is required to support the @samp{g}, @samp{G}, @samp{m}, @samp{M}, |
29015 | @samp{c}, and @samp{s} @var{command}s. All other @var{command}s are | |
8e04817f | 29016 | optional. |
c906108c | 29017 | |
ee2d5c50 AC |
29018 | @node Packets |
29019 | @section Packets | |
29020 | ||
29021 | The following table provides a complete list of all currently defined | |
29022 | @var{command}s and their corresponding response @var{data}. | |
79a6e687 | 29023 | @xref{File-I/O Remote Protocol Extension}, for details about the File |
9c16f35a | 29024 | I/O extension of the remote protocol. |
ee2d5c50 | 29025 | |
b8ff78ce JB |
29026 | Each packet's description has a template showing the packet's overall |
29027 | syntax, followed by an explanation of the packet's meaning. We | |
29028 | include spaces in some of the templates for clarity; these are not | |
29029 | part of the packet's syntax. No @value{GDBN} packet uses spaces to | |
29030 | separate its components. For example, a template like @samp{foo | |
29031 | @var{bar} @var{baz}} describes a packet beginning with the three ASCII | |
29032 | bytes @samp{foo}, followed by a @var{bar}, followed directly by a | |
3f94c067 | 29033 | @var{baz}. @value{GDBN} does not transmit a space character between the |
b8ff78ce JB |
29034 | @samp{foo} and the @var{bar}, or between the @var{bar} and the |
29035 | @var{baz}. | |
29036 | ||
b90a069a SL |
29037 | @cindex @var{thread-id}, in remote protocol |
29038 | @anchor{thread-id syntax} | |
29039 | Several packets and replies include a @var{thread-id} field to identify | |
29040 | a thread. Normally these are positive numbers with a target-specific | |
29041 | interpretation, formatted as big-endian hex strings. A @var{thread-id} | |
29042 | can also be a literal @samp{-1} to indicate all threads, or @samp{0} to | |
29043 | pick any thread. | |
29044 | ||
29045 | In addition, the remote protocol supports a multiprocess feature in | |
29046 | which the @var{thread-id} syntax is extended to optionally include both | |
29047 | process and thread ID fields, as @samp{p@var{pid}.@var{tid}}. | |
29048 | The @var{pid} (process) and @var{tid} (thread) components each have the | |
29049 | format described above: a positive number with target-specific | |
29050 | interpretation formatted as a big-endian hex string, literal @samp{-1} | |
29051 | to indicate all processes or threads (respectively), or @samp{0} to | |
29052 | indicate an arbitrary process or thread. Specifying just a process, as | |
29053 | @samp{p@var{pid}}, is equivalent to @samp{p@var{pid}.-1}. It is an | |
29054 | error to specify all processes but a specific thread, such as | |
29055 | @samp{p-1.@var{tid}}. Note that the @samp{p} prefix is @emph{not} used | |
29056 | for those packets and replies explicitly documented to include a process | |
29057 | ID, rather than a @var{thread-id}. | |
29058 | ||
29059 | The multiprocess @var{thread-id} syntax extensions are only used if both | |
29060 | @value{GDBN} and the stub report support for the @samp{multiprocess} | |
29061 | feature using @samp{qSupported}. @xref{multiprocess extensions}, for | |
29062 | more information. | |
29063 | ||
8ffe2530 JB |
29064 | Note that all packet forms beginning with an upper- or lower-case |
29065 | letter, other than those described here, are reserved for future use. | |
29066 | ||
b8ff78ce | 29067 | Here are the packet descriptions. |
ee2d5c50 | 29068 | |
b8ff78ce | 29069 | @table @samp |
ee2d5c50 | 29070 | |
b8ff78ce JB |
29071 | @item ! |
29072 | @cindex @samp{!} packet | |
2d717e4f | 29073 | @anchor{extended mode} |
8e04817f AC |
29074 | Enable extended mode. In extended mode, the remote server is made |
29075 | persistent. The @samp{R} packet is used to restart the program being | |
29076 | debugged. | |
ee2d5c50 AC |
29077 | |
29078 | Reply: | |
29079 | @table @samp | |
29080 | @item OK | |
8e04817f | 29081 | The remote target both supports and has enabled extended mode. |
ee2d5c50 | 29082 | @end table |
c906108c | 29083 | |
b8ff78ce JB |
29084 | @item ? |
29085 | @cindex @samp{?} packet | |
ee2d5c50 | 29086 | Indicate the reason the target halted. The reply is the same as for |
8b23ecc4 SL |
29087 | step and continue. This packet has a special interpretation when the |
29088 | target is in non-stop mode; see @ref{Remote Non-Stop}. | |
c906108c | 29089 | |
ee2d5c50 AC |
29090 | Reply: |
29091 | @xref{Stop Reply Packets}, for the reply specifications. | |
29092 | ||
b8ff78ce JB |
29093 | @item A @var{arglen},@var{argnum},@var{arg},@dots{} |
29094 | @cindex @samp{A} packet | |
29095 | Initialized @code{argv[]} array passed into program. @var{arglen} | |
29096 | specifies the number of bytes in the hex encoded byte stream | |
29097 | @var{arg}. See @code{gdbserver} for more details. | |
ee2d5c50 AC |
29098 | |
29099 | Reply: | |
29100 | @table @samp | |
29101 | @item OK | |
b8ff78ce JB |
29102 | The arguments were set. |
29103 | @item E @var{NN} | |
29104 | An error occurred. | |
ee2d5c50 AC |
29105 | @end table |
29106 | ||
b8ff78ce JB |
29107 | @item b @var{baud} |
29108 | @cindex @samp{b} packet | |
29109 | (Don't use this packet; its behavior is not well-defined.) | |
ee2d5c50 AC |
29110 | Change the serial line speed to @var{baud}. |
29111 | ||
29112 | JTC: @emph{When does the transport layer state change? When it's | |
29113 | received, or after the ACK is transmitted. In either case, there are | |
29114 | problems if the command or the acknowledgment packet is dropped.} | |
29115 | ||
29116 | Stan: @emph{If people really wanted to add something like this, and get | |
29117 | it working for the first time, they ought to modify ser-unix.c to send | |
29118 | some kind of out-of-band message to a specially-setup stub and have the | |
29119 | switch happen "in between" packets, so that from remote protocol's point | |
29120 | of view, nothing actually happened.} | |
29121 | ||
b8ff78ce JB |
29122 | @item B @var{addr},@var{mode} |
29123 | @cindex @samp{B} packet | |
8e04817f | 29124 | Set (@var{mode} is @samp{S}) or clear (@var{mode} is @samp{C}) a |
2f870471 AC |
29125 | breakpoint at @var{addr}. |
29126 | ||
b8ff78ce | 29127 | Don't use this packet. Use the @samp{Z} and @samp{z} packets instead |
2f870471 | 29128 | (@pxref{insert breakpoint or watchpoint packet}). |
c906108c | 29129 | |
bacec72f | 29130 | @cindex @samp{bc} packet |
0d772ac9 MS |
29131 | @anchor{bc} |
29132 | @item bc | |
bacec72f MS |
29133 | Backward continue. Execute the target system in reverse. No parameter. |
29134 | @xref{Reverse Execution}, for more information. | |
29135 | ||
29136 | Reply: | |
29137 | @xref{Stop Reply Packets}, for the reply specifications. | |
29138 | ||
bacec72f | 29139 | @cindex @samp{bs} packet |
0d772ac9 MS |
29140 | @anchor{bs} |
29141 | @item bs | |
bacec72f MS |
29142 | Backward single step. Execute one instruction in reverse. No parameter. |
29143 | @xref{Reverse Execution}, for more information. | |
29144 | ||
29145 | Reply: | |
29146 | @xref{Stop Reply Packets}, for the reply specifications. | |
29147 | ||
4f553f88 | 29148 | @item c @r{[}@var{addr}@r{]} |
b8ff78ce JB |
29149 | @cindex @samp{c} packet |
29150 | Continue. @var{addr} is address to resume. If @var{addr} is omitted, | |
29151 | resume at current address. | |
c906108c | 29152 | |
ee2d5c50 AC |
29153 | Reply: |
29154 | @xref{Stop Reply Packets}, for the reply specifications. | |
29155 | ||
4f553f88 | 29156 | @item C @var{sig}@r{[};@var{addr}@r{]} |
b8ff78ce | 29157 | @cindex @samp{C} packet |
8e04817f | 29158 | Continue with signal @var{sig} (hex signal number). If |
b8ff78ce | 29159 | @samp{;@var{addr}} is omitted, resume at same address. |
c906108c | 29160 | |
ee2d5c50 AC |
29161 | Reply: |
29162 | @xref{Stop Reply Packets}, for the reply specifications. | |
c906108c | 29163 | |
b8ff78ce JB |
29164 | @item d |
29165 | @cindex @samp{d} packet | |
ee2d5c50 AC |
29166 | Toggle debug flag. |
29167 | ||
b8ff78ce JB |
29168 | Don't use this packet; instead, define a general set packet |
29169 | (@pxref{General Query Packets}). | |
ee2d5c50 | 29170 | |
b8ff78ce | 29171 | @item D |
b90a069a | 29172 | @itemx D;@var{pid} |
b8ff78ce | 29173 | @cindex @samp{D} packet |
b90a069a SL |
29174 | The first form of the packet is used to detach @value{GDBN} from the |
29175 | remote system. It is sent to the remote target | |
07f31aa6 | 29176 | before @value{GDBN} disconnects via the @code{detach} command. |
ee2d5c50 | 29177 | |
b90a069a SL |
29178 | The second form, including a process ID, is used when multiprocess |
29179 | protocol extensions are enabled (@pxref{multiprocess extensions}), to | |
29180 | detach only a specific process. The @var{pid} is specified as a | |
29181 | big-endian hex string. | |
29182 | ||
ee2d5c50 AC |
29183 | Reply: |
29184 | @table @samp | |
10fac096 NW |
29185 | @item OK |
29186 | for success | |
b8ff78ce | 29187 | @item E @var{NN} |
10fac096 | 29188 | for an error |
ee2d5c50 | 29189 | @end table |
c906108c | 29190 | |
b8ff78ce JB |
29191 | @item F @var{RC},@var{EE},@var{CF};@var{XX} |
29192 | @cindex @samp{F} packet | |
29193 | A reply from @value{GDBN} to an @samp{F} packet sent by the target. | |
29194 | This is part of the File-I/O protocol extension. @xref{File-I/O | |
79a6e687 | 29195 | Remote Protocol Extension}, for the specification. |
ee2d5c50 | 29196 | |
b8ff78ce | 29197 | @item g |
ee2d5c50 | 29198 | @anchor{read registers packet} |
b8ff78ce | 29199 | @cindex @samp{g} packet |
ee2d5c50 AC |
29200 | Read general registers. |
29201 | ||
29202 | Reply: | |
29203 | @table @samp | |
29204 | @item @var{XX@dots{}} | |
8e04817f AC |
29205 | Each byte of register data is described by two hex digits. The bytes |
29206 | with the register are transmitted in target byte order. The size of | |
b8ff78ce | 29207 | each register and their position within the @samp{g} packet are |
4a9bb1df UW |
29208 | determined by the @value{GDBN} internal gdbarch functions |
29209 | @code{DEPRECATED_REGISTER_RAW_SIZE} and @code{gdbarch_register_name}. The | |
b8ff78ce JB |
29210 | specification of several standard @samp{g} packets is specified below. |
29211 | @item E @var{NN} | |
ee2d5c50 AC |
29212 | for an error. |
29213 | @end table | |
c906108c | 29214 | |
b8ff78ce JB |
29215 | @item G @var{XX@dots{}} |
29216 | @cindex @samp{G} packet | |
29217 | Write general registers. @xref{read registers packet}, for a | |
29218 | description of the @var{XX@dots{}} data. | |
ee2d5c50 AC |
29219 | |
29220 | Reply: | |
29221 | @table @samp | |
29222 | @item OK | |
29223 | for success | |
b8ff78ce | 29224 | @item E @var{NN} |
ee2d5c50 AC |
29225 | for an error |
29226 | @end table | |
29227 | ||
b90a069a | 29228 | @item H @var{c} @var{thread-id} |
b8ff78ce | 29229 | @cindex @samp{H} packet |
8e04817f | 29230 | Set thread for subsequent operations (@samp{m}, @samp{M}, @samp{g}, |
ee2d5c50 AC |
29231 | @samp{G}, et.al.). @var{c} depends on the operation to be performed: it |
29232 | should be @samp{c} for step and continue operations, @samp{g} for other | |
b90a069a SL |
29233 | operations. The thread designator @var{thread-id} has the format and |
29234 | interpretation described in @ref{thread-id syntax}. | |
ee2d5c50 AC |
29235 | |
29236 | Reply: | |
29237 | @table @samp | |
29238 | @item OK | |
29239 | for success | |
b8ff78ce | 29240 | @item E @var{NN} |
ee2d5c50 AC |
29241 | for an error |
29242 | @end table | |
c906108c | 29243 | |
8e04817f AC |
29244 | @c FIXME: JTC: |
29245 | @c 'H': How restrictive (or permissive) is the thread model. If a | |
29246 | @c thread is selected and stopped, are other threads allowed | |
29247 | @c to continue to execute? As I mentioned above, I think the | |
29248 | @c semantics of each command when a thread is selected must be | |
29249 | @c described. For example: | |
29250 | @c | |
29251 | @c 'g': If the stub supports threads and a specific thread is | |
29252 | @c selected, returns the register block from that thread; | |
29253 | @c otherwise returns current registers. | |
29254 | @c | |
29255 | @c 'G' If the stub supports threads and a specific thread is | |
29256 | @c selected, sets the registers of the register block of | |
29257 | @c that thread; otherwise sets current registers. | |
c906108c | 29258 | |
b8ff78ce | 29259 | @item i @r{[}@var{addr}@r{[},@var{nnn}@r{]]} |
ee2d5c50 | 29260 | @anchor{cycle step packet} |
b8ff78ce JB |
29261 | @cindex @samp{i} packet |
29262 | Step the remote target by a single clock cycle. If @samp{,@var{nnn}} is | |
8e04817f AC |
29263 | present, cycle step @var{nnn} cycles. If @var{addr} is present, cycle |
29264 | step starting at that address. | |
c906108c | 29265 | |
b8ff78ce JB |
29266 | @item I |
29267 | @cindex @samp{I} packet | |
29268 | Signal, then cycle step. @xref{step with signal packet}. @xref{cycle | |
29269 | step packet}. | |
ee2d5c50 | 29270 | |
b8ff78ce JB |
29271 | @item k |
29272 | @cindex @samp{k} packet | |
29273 | Kill request. | |
c906108c | 29274 | |
ac282366 | 29275 | FIXME: @emph{There is no description of how to operate when a specific |
ee2d5c50 AC |
29276 | thread context has been selected (i.e.@: does 'k' kill only that |
29277 | thread?)}. | |
c906108c | 29278 | |
b8ff78ce JB |
29279 | @item m @var{addr},@var{length} |
29280 | @cindex @samp{m} packet | |
8e04817f | 29281 | Read @var{length} bytes of memory starting at address @var{addr}. |
fb031cdf JB |
29282 | Note that @var{addr} may not be aligned to any particular boundary. |
29283 | ||
29284 | The stub need not use any particular size or alignment when gathering | |
29285 | data from memory for the response; even if @var{addr} is word-aligned | |
29286 | and @var{length} is a multiple of the word size, the stub is free to | |
29287 | use byte accesses, or not. For this reason, this packet may not be | |
29288 | suitable for accessing memory-mapped I/O devices. | |
c43c5473 JB |
29289 | @cindex alignment of remote memory accesses |
29290 | @cindex size of remote memory accesses | |
29291 | @cindex memory, alignment and size of remote accesses | |
c906108c | 29292 | |
ee2d5c50 AC |
29293 | Reply: |
29294 | @table @samp | |
29295 | @item @var{XX@dots{}} | |
599b237a | 29296 | Memory contents; each byte is transmitted as a two-digit hexadecimal |
b8ff78ce JB |
29297 | number. The reply may contain fewer bytes than requested if the |
29298 | server was able to read only part of the region of memory. | |
29299 | @item E @var{NN} | |
ee2d5c50 AC |
29300 | @var{NN} is errno |
29301 | @end table | |
29302 | ||
b8ff78ce JB |
29303 | @item M @var{addr},@var{length}:@var{XX@dots{}} |
29304 | @cindex @samp{M} packet | |
8e04817f | 29305 | Write @var{length} bytes of memory starting at address @var{addr}. |
b8ff78ce | 29306 | @var{XX@dots{}} is the data; each byte is transmitted as a two-digit |
599b237a | 29307 | hexadecimal number. |
ee2d5c50 AC |
29308 | |
29309 | Reply: | |
29310 | @table @samp | |
29311 | @item OK | |
29312 | for success | |
b8ff78ce | 29313 | @item E @var{NN} |
8e04817f AC |
29314 | for an error (this includes the case where only part of the data was |
29315 | written). | |
ee2d5c50 | 29316 | @end table |
c906108c | 29317 | |
b8ff78ce JB |
29318 | @item p @var{n} |
29319 | @cindex @samp{p} packet | |
29320 | Read the value of register @var{n}; @var{n} is in hex. | |
2e868123 AC |
29321 | @xref{read registers packet}, for a description of how the returned |
29322 | register value is encoded. | |
ee2d5c50 AC |
29323 | |
29324 | Reply: | |
29325 | @table @samp | |
2e868123 AC |
29326 | @item @var{XX@dots{}} |
29327 | the register's value | |
b8ff78ce | 29328 | @item E @var{NN} |
2e868123 AC |
29329 | for an error |
29330 | @item | |
29331 | Indicating an unrecognized @var{query}. | |
ee2d5c50 AC |
29332 | @end table |
29333 | ||
b8ff78ce | 29334 | @item P @var{n@dots{}}=@var{r@dots{}} |
ee2d5c50 | 29335 | @anchor{write register packet} |
b8ff78ce JB |
29336 | @cindex @samp{P} packet |
29337 | Write register @var{n@dots{}} with value @var{r@dots{}}. The register | |
599b237a | 29338 | number @var{n} is in hexadecimal, and @var{r@dots{}} contains two hex |
8e04817f | 29339 | digits for each byte in the register (target byte order). |
c906108c | 29340 | |
ee2d5c50 AC |
29341 | Reply: |
29342 | @table @samp | |
29343 | @item OK | |
29344 | for success | |
b8ff78ce | 29345 | @item E @var{NN} |
ee2d5c50 AC |
29346 | for an error |
29347 | @end table | |
29348 | ||
5f3bebba JB |
29349 | @item q @var{name} @var{params}@dots{} |
29350 | @itemx Q @var{name} @var{params}@dots{} | |
b8ff78ce | 29351 | @cindex @samp{q} packet |
b8ff78ce | 29352 | @cindex @samp{Q} packet |
5f3bebba JB |
29353 | General query (@samp{q}) and set (@samp{Q}). These packets are |
29354 | described fully in @ref{General Query Packets}. | |
c906108c | 29355 | |
b8ff78ce JB |
29356 | @item r |
29357 | @cindex @samp{r} packet | |
8e04817f | 29358 | Reset the entire system. |
c906108c | 29359 | |
b8ff78ce | 29360 | Don't use this packet; use the @samp{R} packet instead. |
ee2d5c50 | 29361 | |
b8ff78ce JB |
29362 | @item R @var{XX} |
29363 | @cindex @samp{R} packet | |
8e04817f | 29364 | Restart the program being debugged. @var{XX}, while needed, is ignored. |
2d717e4f | 29365 | This packet is only available in extended mode (@pxref{extended mode}). |
ee2d5c50 | 29366 | |
8e04817f | 29367 | The @samp{R} packet has no reply. |
ee2d5c50 | 29368 | |
4f553f88 | 29369 | @item s @r{[}@var{addr}@r{]} |
b8ff78ce JB |
29370 | @cindex @samp{s} packet |
29371 | Single step. @var{addr} is the address at which to resume. If | |
29372 | @var{addr} is omitted, resume at same address. | |
c906108c | 29373 | |
ee2d5c50 AC |
29374 | Reply: |
29375 | @xref{Stop Reply Packets}, for the reply specifications. | |
29376 | ||
4f553f88 | 29377 | @item S @var{sig}@r{[};@var{addr}@r{]} |
ee2d5c50 | 29378 | @anchor{step with signal packet} |
b8ff78ce JB |
29379 | @cindex @samp{S} packet |
29380 | Step with signal. This is analogous to the @samp{C} packet, but | |
29381 | requests a single-step, rather than a normal resumption of execution. | |
c906108c | 29382 | |
ee2d5c50 AC |
29383 | Reply: |
29384 | @xref{Stop Reply Packets}, for the reply specifications. | |
29385 | ||
b8ff78ce JB |
29386 | @item t @var{addr}:@var{PP},@var{MM} |
29387 | @cindex @samp{t} packet | |
8e04817f | 29388 | Search backwards starting at address @var{addr} for a match with pattern |
ee2d5c50 AC |
29389 | @var{PP} and mask @var{MM}. @var{PP} and @var{MM} are 4 bytes. |
29390 | @var{addr} must be at least 3 digits. | |
c906108c | 29391 | |
b90a069a | 29392 | @item T @var{thread-id} |
b8ff78ce | 29393 | @cindex @samp{T} packet |
b90a069a | 29394 | Find out if the thread @var{thread-id} is alive. @xref{thread-id syntax}. |
c906108c | 29395 | |
ee2d5c50 AC |
29396 | Reply: |
29397 | @table @samp | |
29398 | @item OK | |
29399 | thread is still alive | |
b8ff78ce | 29400 | @item E @var{NN} |
ee2d5c50 AC |
29401 | thread is dead |
29402 | @end table | |
29403 | ||
b8ff78ce JB |
29404 | @item v |
29405 | Packets starting with @samp{v} are identified by a multi-letter name, | |
29406 | up to the first @samp{;} or @samp{?} (or the end of the packet). | |
86d30acc | 29407 | |
2d717e4f DJ |
29408 | @item vAttach;@var{pid} |
29409 | @cindex @samp{vAttach} packet | |
8b23ecc4 SL |
29410 | Attach to a new process with the specified process ID @var{pid}. |
29411 | The process ID is a | |
29412 | hexadecimal integer identifying the process. In all-stop mode, all | |
29413 | threads in the attached process are stopped; in non-stop mode, it may be | |
29414 | attached without being stopped if that is supported by the target. | |
29415 | ||
29416 | @c In non-stop mode, on a successful vAttach, the stub should set the | |
29417 | @c current thread to a thread of the newly-attached process. After | |
29418 | @c attaching, GDB queries for the attached process's thread ID with qC. | |
29419 | @c Also note that, from a user perspective, whether or not the | |
29420 | @c target is stopped on attach in non-stop mode depends on whether you | |
29421 | @c use the foreground or background version of the attach command, not | |
29422 | @c on what vAttach does; GDB does the right thing with respect to either | |
29423 | @c stopping or restarting threads. | |
2d717e4f DJ |
29424 | |
29425 | This packet is only available in extended mode (@pxref{extended mode}). | |
29426 | ||
29427 | Reply: | |
29428 | @table @samp | |
29429 | @item E @var{nn} | |
29430 | for an error | |
29431 | @item @r{Any stop packet} | |
8b23ecc4 SL |
29432 | for success in all-stop mode (@pxref{Stop Reply Packets}) |
29433 | @item OK | |
29434 | for success in non-stop mode (@pxref{Remote Non-Stop}) | |
2d717e4f DJ |
29435 | @end table |
29436 | ||
b90a069a | 29437 | @item vCont@r{[};@var{action}@r{[}:@var{thread-id}@r{]]}@dots{} |
b8ff78ce JB |
29438 | @cindex @samp{vCont} packet |
29439 | Resume the inferior, specifying different actions for each thread. | |
b90a069a | 29440 | If an action is specified with no @var{thread-id}, then it is applied to any |
86d30acc | 29441 | threads that don't have a specific action specified; if no default action is |
8b23ecc4 SL |
29442 | specified then other threads should remain stopped in all-stop mode and |
29443 | in their current state in non-stop mode. | |
29444 | Specifying multiple | |
86d30acc | 29445 | default actions is an error; specifying no actions is also an error. |
b90a069a SL |
29446 | Thread IDs are specified using the syntax described in @ref{thread-id syntax}. |
29447 | ||
29448 | Currently supported actions are: | |
86d30acc | 29449 | |
b8ff78ce | 29450 | @table @samp |
86d30acc DJ |
29451 | @item c |
29452 | Continue. | |
b8ff78ce | 29453 | @item C @var{sig} |
8b23ecc4 | 29454 | Continue with signal @var{sig}. The signal @var{sig} should be two hex digits. |
86d30acc DJ |
29455 | @item s |
29456 | Step. | |
b8ff78ce | 29457 | @item S @var{sig} |
8b23ecc4 SL |
29458 | Step with signal @var{sig}. The signal @var{sig} should be two hex digits. |
29459 | @item t | |
29460 | Stop. | |
86d30acc DJ |
29461 | @end table |
29462 | ||
8b23ecc4 SL |
29463 | The optional argument @var{addr} normally associated with the |
29464 | @samp{c}, @samp{C}, @samp{s}, and @samp{S} packets is | |
b8ff78ce | 29465 | not supported in @samp{vCont}. |
86d30acc | 29466 | |
08a0efd0 PA |
29467 | The @samp{t} action is only relevant in non-stop mode |
29468 | (@pxref{Remote Non-Stop}) and may be ignored by the stub otherwise. | |
8b23ecc4 SL |
29469 | A stop reply should be generated for any affected thread not already stopped. |
29470 | When a thread is stopped by means of a @samp{t} action, | |
29471 | the corresponding stop reply should indicate that the thread has stopped with | |
29472 | signal @samp{0}, regardless of whether the target uses some other signal | |
29473 | as an implementation detail. | |
29474 | ||
86d30acc DJ |
29475 | Reply: |
29476 | @xref{Stop Reply Packets}, for the reply specifications. | |
29477 | ||
b8ff78ce JB |
29478 | @item vCont? |
29479 | @cindex @samp{vCont?} packet | |
d3e8051b | 29480 | Request a list of actions supported by the @samp{vCont} packet. |
86d30acc DJ |
29481 | |
29482 | Reply: | |
29483 | @table @samp | |
b8ff78ce JB |
29484 | @item vCont@r{[};@var{action}@dots{}@r{]} |
29485 | The @samp{vCont} packet is supported. Each @var{action} is a supported | |
29486 | command in the @samp{vCont} packet. | |
86d30acc | 29487 | @item |
b8ff78ce | 29488 | The @samp{vCont} packet is not supported. |
86d30acc | 29489 | @end table |
ee2d5c50 | 29490 | |
a6b151f1 DJ |
29491 | @item vFile:@var{operation}:@var{parameter}@dots{} |
29492 | @cindex @samp{vFile} packet | |
29493 | Perform a file operation on the target system. For details, | |
29494 | see @ref{Host I/O Packets}. | |
29495 | ||
68437a39 DJ |
29496 | @item vFlashErase:@var{addr},@var{length} |
29497 | @cindex @samp{vFlashErase} packet | |
29498 | Direct the stub to erase @var{length} bytes of flash starting at | |
29499 | @var{addr}. The region may enclose any number of flash blocks, but | |
29500 | its start and end must fall on block boundaries, as indicated by the | |
79a6e687 BW |
29501 | flash block size appearing in the memory map (@pxref{Memory Map |
29502 | Format}). @value{GDBN} groups flash memory programming operations | |
68437a39 DJ |
29503 | together, and sends a @samp{vFlashDone} request after each group; the |
29504 | stub is allowed to delay erase operation until the @samp{vFlashDone} | |
29505 | packet is received. | |
29506 | ||
b90a069a SL |
29507 | The stub must support @samp{vCont} if it reports support for |
29508 | multiprocess extensions (@pxref{multiprocess extensions}). Note that in | |
29509 | this case @samp{vCont} actions can be specified to apply to all threads | |
29510 | in a process by using the @samp{p@var{pid}.-1} form of the | |
29511 | @var{thread-id}. | |
29512 | ||
68437a39 DJ |
29513 | Reply: |
29514 | @table @samp | |
29515 | @item OK | |
29516 | for success | |
29517 | @item E @var{NN} | |
29518 | for an error | |
29519 | @end table | |
29520 | ||
29521 | @item vFlashWrite:@var{addr}:@var{XX@dots{}} | |
29522 | @cindex @samp{vFlashWrite} packet | |
29523 | Direct the stub to write data to flash address @var{addr}. The data | |
29524 | is passed in binary form using the same encoding as for the @samp{X} | |
29525 | packet (@pxref{Binary Data}). The memory ranges specified by | |
29526 | @samp{vFlashWrite} packets preceding a @samp{vFlashDone} packet must | |
29527 | not overlap, and must appear in order of increasing addresses | |
29528 | (although @samp{vFlashErase} packets for higher addresses may already | |
29529 | have been received; the ordering is guaranteed only between | |
29530 | @samp{vFlashWrite} packets). If a packet writes to an address that was | |
29531 | neither erased by a preceding @samp{vFlashErase} packet nor by some other | |
29532 | target-specific method, the results are unpredictable. | |
29533 | ||
29534 | ||
29535 | Reply: | |
29536 | @table @samp | |
29537 | @item OK | |
29538 | for success | |
29539 | @item E.memtype | |
29540 | for vFlashWrite addressing non-flash memory | |
29541 | @item E @var{NN} | |
29542 | for an error | |
29543 | @end table | |
29544 | ||
29545 | @item vFlashDone | |
29546 | @cindex @samp{vFlashDone} packet | |
29547 | Indicate to the stub that flash programming operation is finished. | |
29548 | The stub is permitted to delay or batch the effects of a group of | |
29549 | @samp{vFlashErase} and @samp{vFlashWrite} packets until a | |
29550 | @samp{vFlashDone} packet is received. The contents of the affected | |
29551 | regions of flash memory are unpredictable until the @samp{vFlashDone} | |
29552 | request is completed. | |
29553 | ||
b90a069a SL |
29554 | @item vKill;@var{pid} |
29555 | @cindex @samp{vKill} packet | |
29556 | Kill the process with the specified process ID. @var{pid} is a | |
29557 | hexadecimal integer identifying the process. This packet is used in | |
29558 | preference to @samp{k} when multiprocess protocol extensions are | |
29559 | supported; see @ref{multiprocess extensions}. | |
29560 | ||
29561 | Reply: | |
29562 | @table @samp | |
29563 | @item E @var{nn} | |
29564 | for an error | |
29565 | @item OK | |
29566 | for success | |
29567 | @end table | |
29568 | ||
2d717e4f DJ |
29569 | @item vRun;@var{filename}@r{[};@var{argument}@r{]}@dots{} |
29570 | @cindex @samp{vRun} packet | |
29571 | Run the program @var{filename}, passing it each @var{argument} on its | |
29572 | command line. The file and arguments are hex-encoded strings. If | |
29573 | @var{filename} is an empty string, the stub may use a default program | |
29574 | (e.g.@: the last program run). The program is created in the stopped | |
9b562ab8 | 29575 | state. |
2d717e4f | 29576 | |
8b23ecc4 SL |
29577 | @c FIXME: What about non-stop mode? |
29578 | ||
2d717e4f DJ |
29579 | This packet is only available in extended mode (@pxref{extended mode}). |
29580 | ||
29581 | Reply: | |
29582 | @table @samp | |
29583 | @item E @var{nn} | |
29584 | for an error | |
29585 | @item @r{Any stop packet} | |
29586 | for success (@pxref{Stop Reply Packets}) | |
29587 | @end table | |
29588 | ||
8b23ecc4 SL |
29589 | @item vStopped |
29590 | @anchor{vStopped packet} | |
29591 | @cindex @samp{vStopped} packet | |
29592 | ||
29593 | In non-stop mode (@pxref{Remote Non-Stop}), acknowledge a previous stop | |
29594 | reply and prompt for the stub to report another one. | |
29595 | ||
29596 | Reply: | |
29597 | @table @samp | |
29598 | @item @r{Any stop packet} | |
29599 | if there is another unreported stop event (@pxref{Stop Reply Packets}) | |
29600 | @item OK | |
29601 | if there are no unreported stop events | |
29602 | @end table | |
29603 | ||
b8ff78ce | 29604 | @item X @var{addr},@var{length}:@var{XX@dots{}} |
9a6253be | 29605 | @anchor{X packet} |
b8ff78ce JB |
29606 | @cindex @samp{X} packet |
29607 | Write data to memory, where the data is transmitted in binary. | |
29608 | @var{addr} is address, @var{length} is number of bytes, | |
0876f84a | 29609 | @samp{@var{XX}@dots{}} is binary data (@pxref{Binary Data}). |
c906108c | 29610 | |
ee2d5c50 AC |
29611 | Reply: |
29612 | @table @samp | |
29613 | @item OK | |
29614 | for success | |
b8ff78ce | 29615 | @item E @var{NN} |
ee2d5c50 AC |
29616 | for an error |
29617 | @end table | |
29618 | ||
a1dcb23a DJ |
29619 | @item z @var{type},@var{addr},@var{kind} |
29620 | @itemx Z @var{type},@var{addr},@var{kind} | |
2f870471 | 29621 | @anchor{insert breakpoint or watchpoint packet} |
b8ff78ce JB |
29622 | @cindex @samp{z} packet |
29623 | @cindex @samp{Z} packets | |
29624 | Insert (@samp{Z}) or remove (@samp{z}) a @var{type} breakpoint or | |
a1dcb23a | 29625 | watchpoint starting at address @var{address} of kind @var{kind}. |
ee2d5c50 | 29626 | |
2f870471 AC |
29627 | Each breakpoint and watchpoint packet @var{type} is documented |
29628 | separately. | |
29629 | ||
512217c7 AC |
29630 | @emph{Implementation notes: A remote target shall return an empty string |
29631 | for an unrecognized breakpoint or watchpoint packet @var{type}. A | |
29632 | remote target shall support either both or neither of a given | |
b8ff78ce | 29633 | @samp{Z@var{type}@dots{}} and @samp{z@var{type}@dots{}} packet pair. To |
2f870471 AC |
29634 | avoid potential problems with duplicate packets, the operations should |
29635 | be implemented in an idempotent way.} | |
29636 | ||
a1dcb23a DJ |
29637 | @item z0,@var{addr},@var{kind} |
29638 | @itemx Z0,@var{addr},@var{kind} | |
b8ff78ce JB |
29639 | @cindex @samp{z0} packet |
29640 | @cindex @samp{Z0} packet | |
29641 | Insert (@samp{Z0}) or remove (@samp{z0}) a memory breakpoint at address | |
a1dcb23a | 29642 | @var{addr} of type @var{kind}. |
2f870471 AC |
29643 | |
29644 | A memory breakpoint is implemented by replacing the instruction at | |
29645 | @var{addr} with a software breakpoint or trap instruction. The | |
a1dcb23a DJ |
29646 | @var{kind} is target-specific and typically indicates the size of |
29647 | the breakpoint in bytes that should be inserted. E.g., the @sc{arm} | |
29648 | and @sc{mips} can insert either a 2 or 4 byte breakpoint. Some | |
29649 | architectures have additional meanings for @var{kind}; | |
29650 | see @ref{Architecture-Specific Protocol Details}. | |
c906108c | 29651 | |
2f870471 AC |
29652 | @emph{Implementation note: It is possible for a target to copy or move |
29653 | code that contains memory breakpoints (e.g., when implementing | |
29654 | overlays). The behavior of this packet, in the presence of such a | |
29655 | target, is not defined.} | |
c906108c | 29656 | |
ee2d5c50 AC |
29657 | Reply: |
29658 | @table @samp | |
2f870471 AC |
29659 | @item OK |
29660 | success | |
29661 | @item | |
29662 | not supported | |
b8ff78ce | 29663 | @item E @var{NN} |
ee2d5c50 | 29664 | for an error |
2f870471 AC |
29665 | @end table |
29666 | ||
a1dcb23a DJ |
29667 | @item z1,@var{addr},@var{kind} |
29668 | @itemx Z1,@var{addr},@var{kind} | |
b8ff78ce JB |
29669 | @cindex @samp{z1} packet |
29670 | @cindex @samp{Z1} packet | |
29671 | Insert (@samp{Z1}) or remove (@samp{z1}) a hardware breakpoint at | |
a1dcb23a | 29672 | address @var{addr}. |
2f870471 AC |
29673 | |
29674 | A hardware breakpoint is implemented using a mechanism that is not | |
a1dcb23a DJ |
29675 | dependant on being able to modify the target's memory. @var{kind} |
29676 | has the same meaning as in @samp{Z0} packets. | |
2f870471 AC |
29677 | |
29678 | @emph{Implementation note: A hardware breakpoint is not affected by code | |
29679 | movement.} | |
29680 | ||
29681 | Reply: | |
29682 | @table @samp | |
ee2d5c50 | 29683 | @item OK |
2f870471 AC |
29684 | success |
29685 | @item | |
29686 | not supported | |
b8ff78ce | 29687 | @item E @var{NN} |
2f870471 AC |
29688 | for an error |
29689 | @end table | |
29690 | ||
a1dcb23a DJ |
29691 | @item z2,@var{addr},@var{kind} |
29692 | @itemx Z2,@var{addr},@var{kind} | |
b8ff78ce JB |
29693 | @cindex @samp{z2} packet |
29694 | @cindex @samp{Z2} packet | |
a1dcb23a DJ |
29695 | Insert (@samp{Z2}) or remove (@samp{z2}) a write watchpoint at @var{addr}. |
29696 | @var{kind} is interpreted as the number of bytes to watch. | |
2f870471 AC |
29697 | |
29698 | Reply: | |
29699 | @table @samp | |
29700 | @item OK | |
29701 | success | |
29702 | @item | |
29703 | not supported | |
b8ff78ce | 29704 | @item E @var{NN} |
2f870471 AC |
29705 | for an error |
29706 | @end table | |
29707 | ||
a1dcb23a DJ |
29708 | @item z3,@var{addr},@var{kind} |
29709 | @itemx Z3,@var{addr},@var{kind} | |
b8ff78ce JB |
29710 | @cindex @samp{z3} packet |
29711 | @cindex @samp{Z3} packet | |
a1dcb23a DJ |
29712 | Insert (@samp{Z3}) or remove (@samp{z3}) a read watchpoint at @var{addr}. |
29713 | @var{kind} is interpreted as the number of bytes to watch. | |
2f870471 AC |
29714 | |
29715 | Reply: | |
29716 | @table @samp | |
29717 | @item OK | |
29718 | success | |
29719 | @item | |
29720 | not supported | |
b8ff78ce | 29721 | @item E @var{NN} |
2f870471 AC |
29722 | for an error |
29723 | @end table | |
29724 | ||
a1dcb23a DJ |
29725 | @item z4,@var{addr},@var{kind} |
29726 | @itemx Z4,@var{addr},@var{kind} | |
b8ff78ce JB |
29727 | @cindex @samp{z4} packet |
29728 | @cindex @samp{Z4} packet | |
a1dcb23a DJ |
29729 | Insert (@samp{Z4}) or remove (@samp{z4}) an access watchpoint at @var{addr}. |
29730 | @var{kind} is interpreted as the number of bytes to watch. | |
2f870471 AC |
29731 | |
29732 | Reply: | |
29733 | @table @samp | |
29734 | @item OK | |
29735 | success | |
29736 | @item | |
29737 | not supported | |
b8ff78ce | 29738 | @item E @var{NN} |
2f870471 | 29739 | for an error |
ee2d5c50 AC |
29740 | @end table |
29741 | ||
29742 | @end table | |
c906108c | 29743 | |
ee2d5c50 AC |
29744 | @node Stop Reply Packets |
29745 | @section Stop Reply Packets | |
29746 | @cindex stop reply packets | |
c906108c | 29747 | |
8b23ecc4 SL |
29748 | The @samp{C}, @samp{c}, @samp{S}, @samp{s}, @samp{vCont}, |
29749 | @samp{vAttach}, @samp{vRun}, @samp{vStopped}, and @samp{?} packets can | |
29750 | receive any of the below as a reply. Except for @samp{?} | |
29751 | and @samp{vStopped}, that reply is only returned | |
b8ff78ce | 29752 | when the target halts. In the below the exact meaning of @dfn{signal |
89be2091 DJ |
29753 | number} is defined by the header @file{include/gdb/signals.h} in the |
29754 | @value{GDBN} source code. | |
c906108c | 29755 | |
b8ff78ce JB |
29756 | As in the description of request packets, we include spaces in the |
29757 | reply templates for clarity; these are not part of the reply packet's | |
29758 | syntax. No @value{GDBN} stop reply packet uses spaces to separate its | |
29759 | components. | |
c906108c | 29760 | |
b8ff78ce | 29761 | @table @samp |
ee2d5c50 | 29762 | |
b8ff78ce | 29763 | @item S @var{AA} |
599b237a | 29764 | The program received signal number @var{AA} (a two-digit hexadecimal |
940178d3 JB |
29765 | number). This is equivalent to a @samp{T} response with no |
29766 | @var{n}:@var{r} pairs. | |
c906108c | 29767 | |
b8ff78ce JB |
29768 | @item T @var{AA} @var{n1}:@var{r1};@var{n2}:@var{r2};@dots{} |
29769 | @cindex @samp{T} packet reply | |
599b237a | 29770 | The program received signal number @var{AA} (a two-digit hexadecimal |
940178d3 JB |
29771 | number). This is equivalent to an @samp{S} response, except that the |
29772 | @samp{@var{n}:@var{r}} pairs can carry values of important registers | |
29773 | and other information directly in the stop reply packet, reducing | |
29774 | round-trip latency. Single-step and breakpoint traps are reported | |
29775 | this way. Each @samp{@var{n}:@var{r}} pair is interpreted as follows: | |
cfa9d6d9 DJ |
29776 | |
29777 | @itemize @bullet | |
b8ff78ce | 29778 | @item |
599b237a | 29779 | If @var{n} is a hexadecimal number, it is a register number, and the |
b8ff78ce JB |
29780 | corresponding @var{r} gives that register's value. @var{r} is a |
29781 | series of bytes in target byte order, with each byte given by a | |
29782 | two-digit hex number. | |
cfa9d6d9 | 29783 | |
b8ff78ce | 29784 | @item |
b90a069a SL |
29785 | If @var{n} is @samp{thread}, then @var{r} is the @var{thread-id} of |
29786 | the stopped thread, as specified in @ref{thread-id syntax}. | |
cfa9d6d9 | 29787 | |
dc146f7c VP |
29788 | @item |
29789 | If @var{n} is @samp{core}, then @var{r} is the hexadecimal number of | |
29790 | the core on which the stop event was detected. | |
29791 | ||
b8ff78ce | 29792 | @item |
cfa9d6d9 DJ |
29793 | If @var{n} is a recognized @dfn{stop reason}, it describes a more |
29794 | specific event that stopped the target. The currently defined stop | |
29795 | reasons are listed below. @var{aa} should be @samp{05}, the trap | |
29796 | signal. At most one stop reason should be present. | |
29797 | ||
b8ff78ce JB |
29798 | @item |
29799 | Otherwise, @value{GDBN} should ignore this @samp{@var{n}:@var{r}} pair | |
29800 | and go on to the next; this allows us to extend the protocol in the | |
29801 | future. | |
cfa9d6d9 DJ |
29802 | @end itemize |
29803 | ||
29804 | The currently defined stop reasons are: | |
29805 | ||
29806 | @table @samp | |
29807 | @item watch | |
29808 | @itemx rwatch | |
29809 | @itemx awatch | |
29810 | The packet indicates a watchpoint hit, and @var{r} is the data address, in | |
29811 | hex. | |
29812 | ||
29813 | @cindex shared library events, remote reply | |
29814 | @item library | |
29815 | The packet indicates that the loaded libraries have changed. | |
29816 | @value{GDBN} should use @samp{qXfer:libraries:read} to fetch a new | |
29817 | list of loaded libraries. @var{r} is ignored. | |
bacec72f MS |
29818 | |
29819 | @cindex replay log events, remote reply | |
29820 | @item replaylog | |
29821 | The packet indicates that the target cannot continue replaying | |
29822 | logged execution events, because it has reached the end (or the | |
29823 | beginning when executing backward) of the log. The value of @var{r} | |
29824 | will be either @samp{begin} or @samp{end}. @xref{Reverse Execution}, | |
29825 | for more information. | |
cfa9d6d9 | 29826 | @end table |
ee2d5c50 | 29827 | |
b8ff78ce | 29828 | @item W @var{AA} |
b90a069a | 29829 | @itemx W @var{AA} ; process:@var{pid} |
8e04817f | 29830 | The process exited, and @var{AA} is the exit status. This is only |
ee2d5c50 AC |
29831 | applicable to certain targets. |
29832 | ||
b90a069a SL |
29833 | The second form of the response, including the process ID of the exited |
29834 | process, can be used only when @value{GDBN} has reported support for | |
29835 | multiprocess protocol extensions; see @ref{multiprocess extensions}. | |
29836 | The @var{pid} is formatted as a big-endian hex string. | |
29837 | ||
b8ff78ce | 29838 | @item X @var{AA} |
b90a069a | 29839 | @itemx X @var{AA} ; process:@var{pid} |
8e04817f | 29840 | The process terminated with signal @var{AA}. |
c906108c | 29841 | |
b90a069a SL |
29842 | The second form of the response, including the process ID of the |
29843 | terminated process, can be used only when @value{GDBN} has reported | |
29844 | support for multiprocess protocol extensions; see @ref{multiprocess | |
29845 | extensions}. The @var{pid} is formatted as a big-endian hex string. | |
29846 | ||
b8ff78ce JB |
29847 | @item O @var{XX}@dots{} |
29848 | @samp{@var{XX}@dots{}} is hex encoding of @sc{ascii} data, to be | |
29849 | written as the program's console output. This can happen at any time | |
29850 | while the program is running and the debugger should continue to wait | |
8b23ecc4 | 29851 | for @samp{W}, @samp{T}, etc. This reply is not permitted in non-stop mode. |
0ce1b118 | 29852 | |
b8ff78ce | 29853 | @item F @var{call-id},@var{parameter}@dots{} |
0ce1b118 CV |
29854 | @var{call-id} is the identifier which says which host system call should |
29855 | be called. This is just the name of the function. Translation into the | |
29856 | correct system call is only applicable as it's defined in @value{GDBN}. | |
79a6e687 | 29857 | @xref{File-I/O Remote Protocol Extension}, for a list of implemented |
0ce1b118 CV |
29858 | system calls. |
29859 | ||
b8ff78ce JB |
29860 | @samp{@var{parameter}@dots{}} is a list of parameters as defined for |
29861 | this very system call. | |
0ce1b118 | 29862 | |
b8ff78ce JB |
29863 | The target replies with this packet when it expects @value{GDBN} to |
29864 | call a host system call on behalf of the target. @value{GDBN} replies | |
29865 | with an appropriate @samp{F} packet and keeps up waiting for the next | |
29866 | reply packet from the target. The latest @samp{C}, @samp{c}, @samp{S} | |
79a6e687 BW |
29867 | or @samp{s} action is expected to be continued. @xref{File-I/O Remote |
29868 | Protocol Extension}, for more details. | |
0ce1b118 | 29869 | |
ee2d5c50 AC |
29870 | @end table |
29871 | ||
29872 | @node General Query Packets | |
29873 | @section General Query Packets | |
9c16f35a | 29874 | @cindex remote query requests |
c906108c | 29875 | |
5f3bebba JB |
29876 | Packets starting with @samp{q} are @dfn{general query packets}; |
29877 | packets starting with @samp{Q} are @dfn{general set packets}. General | |
29878 | query and set packets are a semi-unified form for retrieving and | |
29879 | sending information to and from the stub. | |
29880 | ||
29881 | The initial letter of a query or set packet is followed by a name | |
29882 | indicating what sort of thing the packet applies to. For example, | |
29883 | @value{GDBN} may use a @samp{qSymbol} packet to exchange symbol | |
29884 | definitions with the stub. These packet names follow some | |
29885 | conventions: | |
29886 | ||
29887 | @itemize @bullet | |
29888 | @item | |
29889 | The name must not contain commas, colons or semicolons. | |
29890 | @item | |
29891 | Most @value{GDBN} query and set packets have a leading upper case | |
29892 | letter. | |
29893 | @item | |
29894 | The names of custom vendor packets should use a company prefix, in | |
29895 | lower case, followed by a period. For example, packets designed at | |
29896 | the Acme Corporation might begin with @samp{qacme.foo} (for querying | |
29897 | foos) or @samp{Qacme.bar} (for setting bars). | |
29898 | @end itemize | |
29899 | ||
aa56d27a JB |
29900 | The name of a query or set packet should be separated from any |
29901 | parameters by a @samp{:}; the parameters themselves should be | |
29902 | separated by @samp{,} or @samp{;}. Stubs must be careful to match the | |
369af7bd DJ |
29903 | full packet name, and check for a separator or the end of the packet, |
29904 | in case two packet names share a common prefix. New packets should not begin | |
29905 | with @samp{qC}, @samp{qP}, or @samp{qL}@footnote{The @samp{qP} and @samp{qL} | |
29906 | packets predate these conventions, and have arguments without any terminator | |
29907 | for the packet name; we suspect they are in widespread use in places that | |
29908 | are difficult to upgrade. The @samp{qC} packet has no arguments, but some | |
29909 | existing stubs (e.g.@: RedBoot) are known to not check for the end of the | |
29910 | packet.}. | |
c906108c | 29911 | |
b8ff78ce JB |
29912 | Like the descriptions of the other packets, each description here |
29913 | has a template showing the packet's overall syntax, followed by an | |
29914 | explanation of the packet's meaning. We include spaces in some of the | |
29915 | templates for clarity; these are not part of the packet's syntax. No | |
29916 | @value{GDBN} packet uses spaces to separate its components. | |
29917 | ||
5f3bebba JB |
29918 | Here are the currently defined query and set packets: |
29919 | ||
b8ff78ce | 29920 | @table @samp |
c906108c | 29921 | |
b8ff78ce | 29922 | @item qC |
9c16f35a | 29923 | @cindex current thread, remote request |
b8ff78ce | 29924 | @cindex @samp{qC} packet |
b90a069a | 29925 | Return the current thread ID. |
ee2d5c50 AC |
29926 | |
29927 | Reply: | |
29928 | @table @samp | |
b90a069a SL |
29929 | @item QC @var{thread-id} |
29930 | Where @var{thread-id} is a thread ID as documented in | |
29931 | @ref{thread-id syntax}. | |
b8ff78ce | 29932 | @item @r{(anything else)} |
b90a069a | 29933 | Any other reply implies the old thread ID. |
ee2d5c50 AC |
29934 | @end table |
29935 | ||
b8ff78ce | 29936 | @item qCRC:@var{addr},@var{length} |
ff2587ec | 29937 | @cindex CRC of memory block, remote request |
b8ff78ce | 29938 | @cindex @samp{qCRC} packet |
99e008fe EZ |
29939 | Compute the CRC checksum of a block of memory using CRC-32 defined in |
29940 | IEEE 802.3. The CRC is computed byte at a time, taking the most | |
29941 | significant bit of each byte first. The initial pattern code | |
29942 | @code{0xffffffff} is used to ensure leading zeros affect the CRC. | |
29943 | ||
29944 | @emph{Note:} This is the same CRC used in validating separate debug | |
29945 | files (@pxref{Separate Debug Files, , Debugging Information in Separate | |
29946 | Files}). However the algorithm is slightly different. When validating | |
29947 | separate debug files, the CRC is computed taking the @emph{least} | |
29948 | significant bit of each byte first, and the final result is inverted to | |
29949 | detect trailing zeros. | |
29950 | ||
ff2587ec WZ |
29951 | Reply: |
29952 | @table @samp | |
b8ff78ce | 29953 | @item E @var{NN} |
ff2587ec | 29954 | An error (such as memory fault) |
b8ff78ce JB |
29955 | @item C @var{crc32} |
29956 | The specified memory region's checksum is @var{crc32}. | |
ff2587ec WZ |
29957 | @end table |
29958 | ||
b8ff78ce JB |
29959 | @item qfThreadInfo |
29960 | @itemx qsThreadInfo | |
9c16f35a | 29961 | @cindex list active threads, remote request |
b8ff78ce JB |
29962 | @cindex @samp{qfThreadInfo} packet |
29963 | @cindex @samp{qsThreadInfo} packet | |
b90a069a | 29964 | Obtain a list of all active thread IDs from the target (OS). Since there |
8e04817f AC |
29965 | may be too many active threads to fit into one reply packet, this query |
29966 | works iteratively: it may require more than one query/reply sequence to | |
29967 | obtain the entire list of threads. The first query of the sequence will | |
b8ff78ce JB |
29968 | be the @samp{qfThreadInfo} query; subsequent queries in the |
29969 | sequence will be the @samp{qsThreadInfo} query. | |
ee2d5c50 | 29970 | |
b8ff78ce | 29971 | NOTE: This packet replaces the @samp{qL} query (see below). |
ee2d5c50 AC |
29972 | |
29973 | Reply: | |
29974 | @table @samp | |
b90a069a SL |
29975 | @item m @var{thread-id} |
29976 | A single thread ID | |
29977 | @item m @var{thread-id},@var{thread-id}@dots{} | |
29978 | a comma-separated list of thread IDs | |
b8ff78ce JB |
29979 | @item l |
29980 | (lower case letter @samp{L}) denotes end of list. | |
ee2d5c50 AC |
29981 | @end table |
29982 | ||
29983 | In response to each query, the target will reply with a list of one or | |
b90a069a | 29984 | more thread IDs, separated by commas. |
e1aac25b | 29985 | @value{GDBN} will respond to each reply with a request for more thread |
b8ff78ce | 29986 | ids (using the @samp{qs} form of the query), until the target responds |
b90a069a SL |
29987 | with @samp{l} (lower-case el, for @dfn{last}). |
29988 | Refer to @ref{thread-id syntax}, for the format of the @var{thread-id} | |
29989 | fields. | |
c906108c | 29990 | |
b8ff78ce | 29991 | @item qGetTLSAddr:@var{thread-id},@var{offset},@var{lm} |
ff2587ec | 29992 | @cindex get thread-local storage address, remote request |
b8ff78ce | 29993 | @cindex @samp{qGetTLSAddr} packet |
ff2587ec WZ |
29994 | Fetch the address associated with thread local storage specified |
29995 | by @var{thread-id}, @var{offset}, and @var{lm}. | |
29996 | ||
b90a069a SL |
29997 | @var{thread-id} is the thread ID associated with the |
29998 | thread for which to fetch the TLS address. @xref{thread-id syntax}. | |
ff2587ec WZ |
29999 | |
30000 | @var{offset} is the (big endian, hex encoded) offset associated with the | |
30001 | thread local variable. (This offset is obtained from the debug | |
30002 | information associated with the variable.) | |
30003 | ||
db2e3e2e | 30004 | @var{lm} is the (big endian, hex encoded) OS/ABI-specific encoding of the |
ff2587ec WZ |
30005 | the load module associated with the thread local storage. For example, |
30006 | a @sc{gnu}/Linux system will pass the link map address of the shared | |
30007 | object associated with the thread local storage under consideration. | |
30008 | Other operating environments may choose to represent the load module | |
30009 | differently, so the precise meaning of this parameter will vary. | |
ee2d5c50 AC |
30010 | |
30011 | Reply: | |
b8ff78ce JB |
30012 | @table @samp |
30013 | @item @var{XX}@dots{} | |
ff2587ec WZ |
30014 | Hex encoded (big endian) bytes representing the address of the thread |
30015 | local storage requested. | |
30016 | ||
b8ff78ce JB |
30017 | @item E @var{nn} |
30018 | An error occurred. @var{nn} are hex digits. | |
ff2587ec | 30019 | |
b8ff78ce JB |
30020 | @item |
30021 | An empty reply indicates that @samp{qGetTLSAddr} is not supported by the stub. | |
ee2d5c50 AC |
30022 | @end table |
30023 | ||
b8ff78ce | 30024 | @item qL @var{startflag} @var{threadcount} @var{nextthread} |
8e04817f AC |
30025 | Obtain thread information from RTOS. Where: @var{startflag} (one hex |
30026 | digit) is one to indicate the first query and zero to indicate a | |
30027 | subsequent query; @var{threadcount} (two hex digits) is the maximum | |
30028 | number of threads the response packet can contain; and @var{nextthread} | |
30029 | (eight hex digits), for subsequent queries (@var{startflag} is zero), is | |
30030 | returned in the response as @var{argthread}. | |
ee2d5c50 | 30031 | |
b8ff78ce | 30032 | Don't use this packet; use the @samp{qfThreadInfo} query instead (see above). |
ee2d5c50 AC |
30033 | |
30034 | Reply: | |
30035 | @table @samp | |
b8ff78ce | 30036 | @item qM @var{count} @var{done} @var{argthread} @var{thread}@dots{} |
8e04817f AC |
30037 | Where: @var{count} (two hex digits) is the number of threads being |
30038 | returned; @var{done} (one hex digit) is zero to indicate more threads | |
30039 | and one indicates no further threads; @var{argthreadid} (eight hex | |
b8ff78ce | 30040 | digits) is @var{nextthread} from the request packet; @var{thread}@dots{} |
ee2d5c50 | 30041 | is a sequence of thread IDs from the target. @var{threadid} (eight hex |
8e04817f | 30042 | digits). See @code{remote.c:parse_threadlist_response()}. |
ee2d5c50 | 30043 | @end table |
c906108c | 30044 | |
b8ff78ce | 30045 | @item qOffsets |
9c16f35a | 30046 | @cindex section offsets, remote request |
b8ff78ce | 30047 | @cindex @samp{qOffsets} packet |
31d99776 DJ |
30048 | Get section offsets that the target used when relocating the downloaded |
30049 | image. | |
c906108c | 30050 | |
ee2d5c50 AC |
30051 | Reply: |
30052 | @table @samp | |
31d99776 DJ |
30053 | @item Text=@var{xxx};Data=@var{yyy}@r{[};Bss=@var{zzz}@r{]} |
30054 | Relocate the @code{Text} section by @var{xxx} from its original address. | |
30055 | Relocate the @code{Data} section by @var{yyy} from its original address. | |
30056 | If the object file format provides segment information (e.g.@: @sc{elf} | |
30057 | @samp{PT_LOAD} program headers), @value{GDBN} will relocate entire | |
30058 | segments by the supplied offsets. | |
30059 | ||
30060 | @emph{Note: while a @code{Bss} offset may be included in the response, | |
30061 | @value{GDBN} ignores this and instead applies the @code{Data} offset | |
30062 | to the @code{Bss} section.} | |
30063 | ||
30064 | @item TextSeg=@var{xxx}@r{[};DataSeg=@var{yyy}@r{]} | |
30065 | Relocate the first segment of the object file, which conventionally | |
30066 | contains program code, to a starting address of @var{xxx}. If | |
30067 | @samp{DataSeg} is specified, relocate the second segment, which | |
30068 | conventionally contains modifiable data, to a starting address of | |
30069 | @var{yyy}. @value{GDBN} will report an error if the object file | |
30070 | does not contain segment information, or does not contain at least | |
30071 | as many segments as mentioned in the reply. Extra segments are | |
30072 | kept at fixed offsets relative to the last relocated segment. | |
ee2d5c50 AC |
30073 | @end table |
30074 | ||
b90a069a | 30075 | @item qP @var{mode} @var{thread-id} |
9c16f35a | 30076 | @cindex thread information, remote request |
b8ff78ce | 30077 | @cindex @samp{qP} packet |
b90a069a SL |
30078 | Returns information on @var{thread-id}. Where: @var{mode} is a hex |
30079 | encoded 32 bit mode; @var{thread-id} is a thread ID | |
30080 | (@pxref{thread-id syntax}). | |
ee2d5c50 | 30081 | |
aa56d27a JB |
30082 | Don't use this packet; use the @samp{qThreadExtraInfo} query instead |
30083 | (see below). | |
30084 | ||
b8ff78ce | 30085 | Reply: see @code{remote.c:remote_unpack_thread_info_response()}. |
c906108c | 30086 | |
8b23ecc4 SL |
30087 | @item QNonStop:1 |
30088 | @item QNonStop:0 | |
30089 | @cindex non-stop mode, remote request | |
30090 | @cindex @samp{QNonStop} packet | |
30091 | @anchor{QNonStop} | |
30092 | Enter non-stop (@samp{QNonStop:1}) or all-stop (@samp{QNonStop:0}) mode. | |
30093 | @xref{Remote Non-Stop}, for more information. | |
30094 | ||
30095 | Reply: | |
30096 | @table @samp | |
30097 | @item OK | |
30098 | The request succeeded. | |
30099 | ||
30100 | @item E @var{nn} | |
30101 | An error occurred. @var{nn} are hex digits. | |
30102 | ||
30103 | @item | |
30104 | An empty reply indicates that @samp{QNonStop} is not supported by | |
30105 | the stub. | |
30106 | @end table | |
30107 | ||
30108 | This packet is not probed by default; the remote stub must request it, | |
30109 | by supplying an appropriate @samp{qSupported} response (@pxref{qSupported}). | |
30110 | Use of this packet is controlled by the @code{set non-stop} command; | |
30111 | @pxref{Non-Stop Mode}. | |
30112 | ||
89be2091 DJ |
30113 | @item QPassSignals: @var{signal} @r{[};@var{signal}@r{]}@dots{} |
30114 | @cindex pass signals to inferior, remote request | |
30115 | @cindex @samp{QPassSignals} packet | |
23181151 | 30116 | @anchor{QPassSignals} |
89be2091 DJ |
30117 | Each listed @var{signal} should be passed directly to the inferior process. |
30118 | Signals are numbered identically to continue packets and stop replies | |
30119 | (@pxref{Stop Reply Packets}). Each @var{signal} list item should be | |
30120 | strictly greater than the previous item. These signals do not need to stop | |
30121 | the inferior, or be reported to @value{GDBN}. All other signals should be | |
30122 | reported to @value{GDBN}. Multiple @samp{QPassSignals} packets do not | |
30123 | combine; any earlier @samp{QPassSignals} list is completely replaced by the | |
30124 | new list. This packet improves performance when using @samp{handle | |
30125 | @var{signal} nostop noprint pass}. | |
30126 | ||
30127 | Reply: | |
30128 | @table @samp | |
30129 | @item OK | |
30130 | The request succeeded. | |
30131 | ||
30132 | @item E @var{nn} | |
30133 | An error occurred. @var{nn} are hex digits. | |
30134 | ||
30135 | @item | |
30136 | An empty reply indicates that @samp{QPassSignals} is not supported by | |
30137 | the stub. | |
30138 | @end table | |
30139 | ||
30140 | Use of this packet is controlled by the @code{set remote pass-signals} | |
79a6e687 | 30141 | command (@pxref{Remote Configuration, set remote pass-signals}). |
89be2091 DJ |
30142 | This packet is not probed by default; the remote stub must request it, |
30143 | by supplying an appropriate @samp{qSupported} response (@pxref{qSupported}). | |
30144 | ||
b8ff78ce | 30145 | @item qRcmd,@var{command} |
ff2587ec | 30146 | @cindex execute remote command, remote request |
b8ff78ce | 30147 | @cindex @samp{qRcmd} packet |
ff2587ec | 30148 | @var{command} (hex encoded) is passed to the local interpreter for |
b8ff78ce JB |
30149 | execution. Invalid commands should be reported using the output |
30150 | string. Before the final result packet, the target may also respond | |
30151 | with a number of intermediate @samp{O@var{output}} console output | |
30152 | packets. @emph{Implementors should note that providing access to a | |
30153 | stubs's interpreter may have security implications}. | |
fa93a9d8 | 30154 | |
ff2587ec WZ |
30155 | Reply: |
30156 | @table @samp | |
30157 | @item OK | |
30158 | A command response with no output. | |
30159 | @item @var{OUTPUT} | |
30160 | A command response with the hex encoded output string @var{OUTPUT}. | |
b8ff78ce | 30161 | @item E @var{NN} |
ff2587ec | 30162 | Indicate a badly formed request. |
b8ff78ce JB |
30163 | @item |
30164 | An empty reply indicates that @samp{qRcmd} is not recognized. | |
ff2587ec | 30165 | @end table |
fa93a9d8 | 30166 | |
aa56d27a JB |
30167 | (Note that the @code{qRcmd} packet's name is separated from the |
30168 | command by a @samp{,}, not a @samp{:}, contrary to the naming | |
30169 | conventions above. Please don't use this packet as a model for new | |
30170 | packets.) | |
30171 | ||
08388c79 DE |
30172 | @item qSearch:memory:@var{address};@var{length};@var{search-pattern} |
30173 | @cindex searching memory, in remote debugging | |
30174 | @cindex @samp{qSearch:memory} packet | |
30175 | @anchor{qSearch memory} | |
30176 | Search @var{length} bytes at @var{address} for @var{search-pattern}. | |
30177 | @var{address} and @var{length} are encoded in hex. | |
30178 | @var{search-pattern} is a sequence of bytes, hex encoded. | |
30179 | ||
30180 | Reply: | |
30181 | @table @samp | |
30182 | @item 0 | |
30183 | The pattern was not found. | |
30184 | @item 1,address | |
30185 | The pattern was found at @var{address}. | |
30186 | @item E @var{NN} | |
30187 | A badly formed request or an error was encountered while searching memory. | |
30188 | @item | |
30189 | An empty reply indicates that @samp{qSearch:memory} is not recognized. | |
30190 | @end table | |
30191 | ||
a6f3e723 SL |
30192 | @item QStartNoAckMode |
30193 | @cindex @samp{QStartNoAckMode} packet | |
30194 | @anchor{QStartNoAckMode} | |
30195 | Request that the remote stub disable the normal @samp{+}/@samp{-} | |
30196 | protocol acknowledgments (@pxref{Packet Acknowledgment}). | |
30197 | ||
30198 | Reply: | |
30199 | @table @samp | |
30200 | @item OK | |
30201 | The stub has switched to no-acknowledgment mode. | |
30202 | @value{GDBN} acknowledges this reponse, | |
30203 | but neither the stub nor @value{GDBN} shall send or expect further | |
30204 | @samp{+}/@samp{-} acknowledgments in the current connection. | |
30205 | @item | |
30206 | An empty reply indicates that the stub does not support no-acknowledgment mode. | |
30207 | @end table | |
30208 | ||
be2a5f71 DJ |
30209 | @item qSupported @r{[}:@var{gdbfeature} @r{[};@var{gdbfeature}@r{]}@dots{} @r{]} |
30210 | @cindex supported packets, remote query | |
30211 | @cindex features of the remote protocol | |
30212 | @cindex @samp{qSupported} packet | |
0876f84a | 30213 | @anchor{qSupported} |
be2a5f71 DJ |
30214 | Tell the remote stub about features supported by @value{GDBN}, and |
30215 | query the stub for features it supports. This packet allows | |
30216 | @value{GDBN} and the remote stub to take advantage of each others' | |
30217 | features. @samp{qSupported} also consolidates multiple feature probes | |
30218 | at startup, to improve @value{GDBN} performance---a single larger | |
30219 | packet performs better than multiple smaller probe packets on | |
30220 | high-latency links. Some features may enable behavior which must not | |
30221 | be on by default, e.g.@: because it would confuse older clients or | |
30222 | stubs. Other features may describe packets which could be | |
30223 | automatically probed for, but are not. These features must be | |
30224 | reported before @value{GDBN} will use them. This ``default | |
30225 | unsupported'' behavior is not appropriate for all packets, but it | |
30226 | helps to keep the initial connection time under control with new | |
30227 | versions of @value{GDBN} which support increasing numbers of packets. | |
30228 | ||
30229 | Reply: | |
30230 | @table @samp | |
30231 | @item @var{stubfeature} @r{[};@var{stubfeature}@r{]}@dots{} | |
30232 | The stub supports or does not support each returned @var{stubfeature}, | |
30233 | depending on the form of each @var{stubfeature} (see below for the | |
30234 | possible forms). | |
30235 | @item | |
30236 | An empty reply indicates that @samp{qSupported} is not recognized, | |
30237 | or that no features needed to be reported to @value{GDBN}. | |
30238 | @end table | |
30239 | ||
30240 | The allowed forms for each feature (either a @var{gdbfeature} in the | |
30241 | @samp{qSupported} packet, or a @var{stubfeature} in the response) | |
30242 | are: | |
30243 | ||
30244 | @table @samp | |
30245 | @item @var{name}=@var{value} | |
30246 | The remote protocol feature @var{name} is supported, and associated | |
30247 | with the specified @var{value}. The format of @var{value} depends | |
30248 | on the feature, but it must not include a semicolon. | |
30249 | @item @var{name}+ | |
30250 | The remote protocol feature @var{name} is supported, and does not | |
30251 | need an associated value. | |
30252 | @item @var{name}- | |
30253 | The remote protocol feature @var{name} is not supported. | |
30254 | @item @var{name}? | |
30255 | The remote protocol feature @var{name} may be supported, and | |
30256 | @value{GDBN} should auto-detect support in some other way when it is | |
30257 | needed. This form will not be used for @var{gdbfeature} notifications, | |
30258 | but may be used for @var{stubfeature} responses. | |
30259 | @end table | |
30260 | ||
30261 | Whenever the stub receives a @samp{qSupported} request, the | |
30262 | supplied set of @value{GDBN} features should override any previous | |
30263 | request. This allows @value{GDBN} to put the stub in a known | |
30264 | state, even if the stub had previously been communicating with | |
30265 | a different version of @value{GDBN}. | |
30266 | ||
b90a069a SL |
30267 | The following values of @var{gdbfeature} (for the packet sent by @value{GDBN}) |
30268 | are defined: | |
30269 | ||
30270 | @table @samp | |
30271 | @item multiprocess | |
30272 | This feature indicates whether @value{GDBN} supports multiprocess | |
30273 | extensions to the remote protocol. @value{GDBN} does not use such | |
30274 | extensions unless the stub also reports that it supports them by | |
30275 | including @samp{multiprocess+} in its @samp{qSupported} reply. | |
30276 | @xref{multiprocess extensions}, for details. | |
30277 | @end table | |
30278 | ||
30279 | Stubs should ignore any unknown values for | |
be2a5f71 DJ |
30280 | @var{gdbfeature}. Any @value{GDBN} which sends a @samp{qSupported} |
30281 | packet supports receiving packets of unlimited length (earlier | |
b90a069a | 30282 | versions of @value{GDBN} may reject overly long responses). Additional values |
be2a5f71 DJ |
30283 | for @var{gdbfeature} may be defined in the future to let the stub take |
30284 | advantage of new features in @value{GDBN}, e.g.@: incompatible | |
b90a069a SL |
30285 | improvements in the remote protocol---the @samp{multiprocess} feature is |
30286 | an example of such a feature. The stub's reply should be independent | |
be2a5f71 DJ |
30287 | of the @var{gdbfeature} entries sent by @value{GDBN}; first @value{GDBN} |
30288 | describes all the features it supports, and then the stub replies with | |
30289 | all the features it supports. | |
30290 | ||
30291 | Similarly, @value{GDBN} will silently ignore unrecognized stub feature | |
30292 | responses, as long as each response uses one of the standard forms. | |
30293 | ||
30294 | Some features are flags. A stub which supports a flag feature | |
30295 | should respond with a @samp{+} form response. Other features | |
30296 | require values, and the stub should respond with an @samp{=} | |
30297 | form response. | |
30298 | ||
30299 | Each feature has a default value, which @value{GDBN} will use if | |
30300 | @samp{qSupported} is not available or if the feature is not mentioned | |
30301 | in the @samp{qSupported} response. The default values are fixed; a | |
30302 | stub is free to omit any feature responses that match the defaults. | |
30303 | ||
30304 | Not all features can be probed, but for those which can, the probing | |
30305 | mechanism is useful: in some cases, a stub's internal | |
30306 | architecture may not allow the protocol layer to know some information | |
30307 | about the underlying target in advance. This is especially common in | |
30308 | stubs which may be configured for multiple targets. | |
30309 | ||
30310 | These are the currently defined stub features and their properties: | |
30311 | ||
cfa9d6d9 | 30312 | @multitable @columnfractions 0.35 0.2 0.12 0.2 |
be2a5f71 DJ |
30313 | @c NOTE: The first row should be @headitem, but we do not yet require |
30314 | @c a new enough version of Texinfo (4.7) to use @headitem. | |
0876f84a | 30315 | @item Feature Name |
be2a5f71 DJ |
30316 | @tab Value Required |
30317 | @tab Default | |
30318 | @tab Probe Allowed | |
30319 | ||
30320 | @item @samp{PacketSize} | |
30321 | @tab Yes | |
30322 | @tab @samp{-} | |
30323 | @tab No | |
30324 | ||
0876f84a DJ |
30325 | @item @samp{qXfer:auxv:read} |
30326 | @tab No | |
30327 | @tab @samp{-} | |
30328 | @tab Yes | |
30329 | ||
23181151 DJ |
30330 | @item @samp{qXfer:features:read} |
30331 | @tab No | |
30332 | @tab @samp{-} | |
30333 | @tab Yes | |
30334 | ||
cfa9d6d9 DJ |
30335 | @item @samp{qXfer:libraries:read} |
30336 | @tab No | |
30337 | @tab @samp{-} | |
30338 | @tab Yes | |
30339 | ||
68437a39 DJ |
30340 | @item @samp{qXfer:memory-map:read} |
30341 | @tab No | |
30342 | @tab @samp{-} | |
30343 | @tab Yes | |
30344 | ||
0e7f50da UW |
30345 | @item @samp{qXfer:spu:read} |
30346 | @tab No | |
30347 | @tab @samp{-} | |
30348 | @tab Yes | |
30349 | ||
30350 | @item @samp{qXfer:spu:write} | |
30351 | @tab No | |
30352 | @tab @samp{-} | |
30353 | @tab Yes | |
30354 | ||
4aa995e1 PA |
30355 | @item @samp{qXfer:siginfo:read} |
30356 | @tab No | |
30357 | @tab @samp{-} | |
30358 | @tab Yes | |
30359 | ||
30360 | @item @samp{qXfer:siginfo:write} | |
30361 | @tab No | |
30362 | @tab @samp{-} | |
30363 | @tab Yes | |
30364 | ||
dc146f7c VP |
30365 | @item @samp{qXfer:threads:read} |
30366 | @tab No | |
30367 | @tab @samp{-} | |
30368 | @tab Yes | |
30369 | ||
30370 | ||
8b23ecc4 SL |
30371 | @item @samp{QNonStop} |
30372 | @tab No | |
30373 | @tab @samp{-} | |
30374 | @tab Yes | |
30375 | ||
89be2091 DJ |
30376 | @item @samp{QPassSignals} |
30377 | @tab No | |
30378 | @tab @samp{-} | |
30379 | @tab Yes | |
30380 | ||
a6f3e723 SL |
30381 | @item @samp{QStartNoAckMode} |
30382 | @tab No | |
30383 | @tab @samp{-} | |
30384 | @tab Yes | |
30385 | ||
b90a069a SL |
30386 | @item @samp{multiprocess} |
30387 | @tab No | |
30388 | @tab @samp{-} | |
30389 | @tab No | |
30390 | ||
782b2b07 SS |
30391 | @item @samp{ConditionalTracepoints} |
30392 | @tab No | |
30393 | @tab @samp{-} | |
30394 | @tab No | |
30395 | ||
0d772ac9 MS |
30396 | @item @samp{ReverseContinue} |
30397 | @tab No | |
2f8132f3 | 30398 | @tab @samp{-} |
0d772ac9 MS |
30399 | @tab No |
30400 | ||
30401 | @item @samp{ReverseStep} | |
30402 | @tab No | |
2f8132f3 | 30403 | @tab @samp{-} |
0d772ac9 MS |
30404 | @tab No |
30405 | ||
be2a5f71 DJ |
30406 | @end multitable |
30407 | ||
30408 | These are the currently defined stub features, in more detail: | |
30409 | ||
30410 | @table @samp | |
30411 | @cindex packet size, remote protocol | |
30412 | @item PacketSize=@var{bytes} | |
30413 | The remote stub can accept packets up to at least @var{bytes} in | |
30414 | length. @value{GDBN} will send packets up to this size for bulk | |
30415 | transfers, and will never send larger packets. This is a limit on the | |
30416 | data characters in the packet, including the frame and checksum. | |
30417 | There is no trailing NUL byte in a remote protocol packet; if the stub | |
30418 | stores packets in a NUL-terminated format, it should allow an extra | |
30419 | byte in its buffer for the NUL. If this stub feature is not supported, | |
30420 | @value{GDBN} guesses based on the size of the @samp{g} packet response. | |
30421 | ||
0876f84a DJ |
30422 | @item qXfer:auxv:read |
30423 | The remote stub understands the @samp{qXfer:auxv:read} packet | |
30424 | (@pxref{qXfer auxiliary vector read}). | |
30425 | ||
23181151 DJ |
30426 | @item qXfer:features:read |
30427 | The remote stub understands the @samp{qXfer:features:read} packet | |
30428 | (@pxref{qXfer target description read}). | |
30429 | ||
cfa9d6d9 DJ |
30430 | @item qXfer:libraries:read |
30431 | The remote stub understands the @samp{qXfer:libraries:read} packet | |
30432 | (@pxref{qXfer library list read}). | |
30433 | ||
23181151 DJ |
30434 | @item qXfer:memory-map:read |
30435 | The remote stub understands the @samp{qXfer:memory-map:read} packet | |
30436 | (@pxref{qXfer memory map read}). | |
30437 | ||
0e7f50da UW |
30438 | @item qXfer:spu:read |
30439 | The remote stub understands the @samp{qXfer:spu:read} packet | |
30440 | (@pxref{qXfer spu read}). | |
30441 | ||
30442 | @item qXfer:spu:write | |
30443 | The remote stub understands the @samp{qXfer:spu:write} packet | |
30444 | (@pxref{qXfer spu write}). | |
30445 | ||
4aa995e1 PA |
30446 | @item qXfer:siginfo:read |
30447 | The remote stub understands the @samp{qXfer:siginfo:read} packet | |
30448 | (@pxref{qXfer siginfo read}). | |
30449 | ||
30450 | @item qXfer:siginfo:write | |
30451 | The remote stub understands the @samp{qXfer:siginfo:write} packet | |
30452 | (@pxref{qXfer siginfo write}). | |
30453 | ||
dc146f7c VP |
30454 | @item qXfer:threads:read |
30455 | The remote stub understands the @samp{qXfer:threads:read} packet | |
30456 | (@pxref{qXfer threads read}). | |
30457 | ||
8b23ecc4 SL |
30458 | @item QNonStop |
30459 | The remote stub understands the @samp{QNonStop} packet | |
30460 | (@pxref{QNonStop}). | |
30461 | ||
23181151 DJ |
30462 | @item QPassSignals |
30463 | The remote stub understands the @samp{QPassSignals} packet | |
30464 | (@pxref{QPassSignals}). | |
30465 | ||
a6f3e723 SL |
30466 | @item QStartNoAckMode |
30467 | The remote stub understands the @samp{QStartNoAckMode} packet and | |
30468 | prefers to operate in no-acknowledgment mode. @xref{Packet Acknowledgment}. | |
30469 | ||
b90a069a SL |
30470 | @item multiprocess |
30471 | @anchor{multiprocess extensions} | |
30472 | @cindex multiprocess extensions, in remote protocol | |
30473 | The remote stub understands the multiprocess extensions to the remote | |
30474 | protocol syntax. The multiprocess extensions affect the syntax of | |
30475 | thread IDs in both packets and replies (@pxref{thread-id syntax}), and | |
30476 | add process IDs to the @samp{D} packet and @samp{W} and @samp{X} | |
30477 | replies. Note that reporting this feature indicates support for the | |
30478 | syntactic extensions only, not that the stub necessarily supports | |
30479 | debugging of more than one process at a time. The stub must not use | |
30480 | multiprocess extensions in packet replies unless @value{GDBN} has also | |
30481 | indicated it supports them in its @samp{qSupported} request. | |
30482 | ||
07e059b5 VP |
30483 | @item qXfer:osdata:read |
30484 | The remote stub understands the @samp{qXfer:osdata:read} packet | |
30485 | ((@pxref{qXfer osdata read}). | |
30486 | ||
782b2b07 SS |
30487 | @item ConditionalTracepoints |
30488 | The remote stub accepts and implements conditional expressions defined | |
30489 | for tracepoints (@pxref{Tracepoint Conditions}). | |
30490 | ||
0d772ac9 MS |
30491 | @item ReverseContinue |
30492 | The remote stub accepts and implements the reverse continue packet | |
30493 | (@pxref{bc}). | |
30494 | ||
30495 | @item ReverseStep | |
30496 | The remote stub accepts and implements the reverse step packet | |
30497 | (@pxref{bs}). | |
30498 | ||
be2a5f71 DJ |
30499 | @end table |
30500 | ||
b8ff78ce | 30501 | @item qSymbol:: |
ff2587ec | 30502 | @cindex symbol lookup, remote request |
b8ff78ce | 30503 | @cindex @samp{qSymbol} packet |
ff2587ec WZ |
30504 | Notify the target that @value{GDBN} is prepared to serve symbol lookup |
30505 | requests. Accept requests from the target for the values of symbols. | |
fa93a9d8 JB |
30506 | |
30507 | Reply: | |
ff2587ec | 30508 | @table @samp |
b8ff78ce | 30509 | @item OK |
ff2587ec | 30510 | The target does not need to look up any (more) symbols. |
b8ff78ce | 30511 | @item qSymbol:@var{sym_name} |
ff2587ec WZ |
30512 | The target requests the value of symbol @var{sym_name} (hex encoded). |
30513 | @value{GDBN} may provide the value by using the | |
b8ff78ce JB |
30514 | @samp{qSymbol:@var{sym_value}:@var{sym_name}} message, described |
30515 | below. | |
ff2587ec | 30516 | @end table |
83761cbd | 30517 | |
b8ff78ce | 30518 | @item qSymbol:@var{sym_value}:@var{sym_name} |
ff2587ec WZ |
30519 | Set the value of @var{sym_name} to @var{sym_value}. |
30520 | ||
30521 | @var{sym_name} (hex encoded) is the name of a symbol whose value the | |
30522 | target has previously requested. | |
30523 | ||
30524 | @var{sym_value} (hex) is the value for symbol @var{sym_name}. If | |
30525 | @value{GDBN} cannot supply a value for @var{sym_name}, then this field | |
30526 | will be empty. | |
30527 | ||
30528 | Reply: | |
30529 | @table @samp | |
b8ff78ce | 30530 | @item OK |
ff2587ec | 30531 | The target does not need to look up any (more) symbols. |
b8ff78ce | 30532 | @item qSymbol:@var{sym_name} |
ff2587ec WZ |
30533 | The target requests the value of a new symbol @var{sym_name} (hex |
30534 | encoded). @value{GDBN} will continue to supply the values of symbols | |
30535 | (if available), until the target ceases to request them. | |
fa93a9d8 | 30536 | @end table |
0abb7bc7 | 30537 | |
00bf0b85 | 30538 | @item qTBuffer |
d5551862 SS |
30539 | @item QTDisconnected |
30540 | @itemx QTDP | |
30541 | @itemx QTDV | |
00bf0b85 SS |
30542 | @itemx qTfP |
30543 | @itemx qTfV | |
9d29849a JB |
30544 | @itemx QTFrame |
30545 | @xref{Tracepoint Packets}. | |
30546 | ||
b90a069a | 30547 | @item qThreadExtraInfo,@var{thread-id} |
ff2587ec | 30548 | @cindex thread attributes info, remote request |
b8ff78ce JB |
30549 | @cindex @samp{qThreadExtraInfo} packet |
30550 | Obtain a printable string description of a thread's attributes from | |
b90a069a SL |
30551 | the target OS. @var{thread-id} is a thread ID; |
30552 | see @ref{thread-id syntax}. This | |
b8ff78ce JB |
30553 | string may contain anything that the target OS thinks is interesting |
30554 | for @value{GDBN} to tell the user about the thread. The string is | |
30555 | displayed in @value{GDBN}'s @code{info threads} display. Some | |
30556 | examples of possible thread extra info strings are @samp{Runnable}, or | |
30557 | @samp{Blocked on Mutex}. | |
ff2587ec WZ |
30558 | |
30559 | Reply: | |
30560 | @table @samp | |
b8ff78ce JB |
30561 | @item @var{XX}@dots{} |
30562 | Where @samp{@var{XX}@dots{}} is a hex encoding of @sc{ascii} data, | |
30563 | comprising the printable string containing the extra information about | |
30564 | the thread's attributes. | |
ff2587ec | 30565 | @end table |
814e32d7 | 30566 | |
aa56d27a JB |
30567 | (Note that the @code{qThreadExtraInfo} packet's name is separated from |
30568 | the command by a @samp{,}, not a @samp{:}, contrary to the naming | |
30569 | conventions above. Please don't use this packet as a model for new | |
30570 | packets.) | |
30571 | ||
00bf0b85 SS |
30572 | @item QTSave |
30573 | @item qTsP | |
30574 | @item qTsV | |
d5551862 | 30575 | @itemx QTStart |
9d29849a JB |
30576 | @itemx QTStop |
30577 | @itemx QTinit | |
30578 | @itemx QTro | |
30579 | @itemx qTStatus | |
d5551862 | 30580 | @itemx qTV |
9d29849a JB |
30581 | @xref{Tracepoint Packets}. |
30582 | ||
0876f84a DJ |
30583 | @item qXfer:@var{object}:read:@var{annex}:@var{offset},@var{length} |
30584 | @cindex read special object, remote request | |
30585 | @cindex @samp{qXfer} packet | |
68437a39 | 30586 | @anchor{qXfer read} |
0876f84a DJ |
30587 | Read uninterpreted bytes from the target's special data area |
30588 | identified by the keyword @var{object}. Request @var{length} bytes | |
30589 | starting at @var{offset} bytes into the data. The content and | |
0e7f50da | 30590 | encoding of @var{annex} is specific to @var{object}; it can supply |
0876f84a DJ |
30591 | additional details about what data to access. |
30592 | ||
30593 | Here are the specific requests of this form defined so far. All | |
30594 | @samp{qXfer:@var{object}:read:@dots{}} requests use the same reply | |
30595 | formats, listed below. | |
30596 | ||
30597 | @table @samp | |
30598 | @item qXfer:auxv:read::@var{offset},@var{length} | |
30599 | @anchor{qXfer auxiliary vector read} | |
30600 | Access the target's @dfn{auxiliary vector}. @xref{OS Information, | |
427c3a89 | 30601 | auxiliary vector}. Note @var{annex} must be empty. |
0876f84a DJ |
30602 | |
30603 | This packet is not probed by default; the remote stub must request it, | |
89be2091 | 30604 | by supplying an appropriate @samp{qSupported} response (@pxref{qSupported}). |
0876f84a | 30605 | |
23181151 DJ |
30606 | @item qXfer:features:read:@var{annex}:@var{offset},@var{length} |
30607 | @anchor{qXfer target description read} | |
30608 | Access the @dfn{target description}. @xref{Target Descriptions}. The | |
30609 | annex specifies which XML document to access. The main description is | |
30610 | always loaded from the @samp{target.xml} annex. | |
30611 | ||
30612 | This packet is not probed by default; the remote stub must request it, | |
30613 | by supplying an appropriate @samp{qSupported} response (@pxref{qSupported}). | |
30614 | ||
cfa9d6d9 DJ |
30615 | @item qXfer:libraries:read:@var{annex}:@var{offset},@var{length} |
30616 | @anchor{qXfer library list read} | |
30617 | Access the target's list of loaded libraries. @xref{Library List Format}. | |
30618 | The annex part of the generic @samp{qXfer} packet must be empty | |
30619 | (@pxref{qXfer read}). | |
30620 | ||
30621 | Targets which maintain a list of libraries in the program's memory do | |
30622 | not need to implement this packet; it is designed for platforms where | |
30623 | the operating system manages the list of loaded libraries. | |
30624 | ||
30625 | This packet is not probed by default; the remote stub must request it, | |
30626 | by supplying an appropriate @samp{qSupported} response (@pxref{qSupported}). | |
30627 | ||
68437a39 DJ |
30628 | @item qXfer:memory-map:read::@var{offset},@var{length} |
30629 | @anchor{qXfer memory map read} | |
79a6e687 | 30630 | Access the target's @dfn{memory-map}. @xref{Memory Map Format}. The |
68437a39 DJ |
30631 | annex part of the generic @samp{qXfer} packet must be empty |
30632 | (@pxref{qXfer read}). | |
30633 | ||
0e7f50da UW |
30634 | This packet is not probed by default; the remote stub must request it, |
30635 | by supplying an appropriate @samp{qSupported} response (@pxref{qSupported}). | |
30636 | ||
4aa995e1 PA |
30637 | @item qXfer:siginfo:read::@var{offset},@var{length} |
30638 | @anchor{qXfer siginfo read} | |
30639 | Read contents of the extra signal information on the target | |
30640 | system. The annex part of the generic @samp{qXfer} packet must be | |
30641 | empty (@pxref{qXfer read}). | |
30642 | ||
30643 | This packet is not probed by default; the remote stub must request it, | |
30644 | by supplying an appropriate @samp{qSupported} response | |
30645 | (@pxref{qSupported}). | |
30646 | ||
0e7f50da UW |
30647 | @item qXfer:spu:read:@var{annex}:@var{offset},@var{length} |
30648 | @anchor{qXfer spu read} | |
30649 | Read contents of an @code{spufs} file on the target system. The | |
30650 | annex specifies which file to read; it must be of the form | |
30651 | @file{@var{id}/@var{name}}, where @var{id} specifies an SPU context ID | |
30652 | in the target process, and @var{name} identifes the @code{spufs} file | |
30653 | in that context to be accessed. | |
30654 | ||
68437a39 | 30655 | This packet is not probed by default; the remote stub must request it, |
07e059b5 VP |
30656 | by supplying an appropriate @samp{qSupported} response |
30657 | (@pxref{qSupported}). | |
30658 | ||
dc146f7c VP |
30659 | @item qXfer:threads:read::@var{offset},@var{length} |
30660 | @anchor{qXfer threads read} | |
30661 | Access the list of threads on target. @xref{Thread List Format}. The | |
30662 | annex part of the generic @samp{qXfer} packet must be empty | |
30663 | (@pxref{qXfer read}). | |
30664 | ||
30665 | This packet is not probed by default; the remote stub must request it, | |
30666 | by supplying an appropriate @samp{qSupported} response (@pxref{qSupported}). | |
30667 | ||
07e059b5 VP |
30668 | @item qXfer:osdata:read::@var{offset},@var{length} |
30669 | @anchor{qXfer osdata read} | |
30670 | Access the target's @dfn{operating system information}. | |
30671 | @xref{Operating System Information}. | |
30672 | ||
68437a39 DJ |
30673 | @end table |
30674 | ||
0876f84a DJ |
30675 | Reply: |
30676 | @table @samp | |
30677 | @item m @var{data} | |
30678 | Data @var{data} (@pxref{Binary Data}) has been read from the | |
30679 | target. There may be more data at a higher address (although | |
30680 | it is permitted to return @samp{m} even for the last valid | |
30681 | block of data, as long as at least one byte of data was read). | |
30682 | @var{data} may have fewer bytes than the @var{length} in the | |
30683 | request. | |
30684 | ||
30685 | @item l @var{data} | |
30686 | Data @var{data} (@pxref{Binary Data}) has been read from the target. | |
30687 | There is no more data to be read. @var{data} may have fewer bytes | |
30688 | than the @var{length} in the request. | |
30689 | ||
30690 | @item l | |
30691 | The @var{offset} in the request is at the end of the data. | |
30692 | There is no more data to be read. | |
30693 | ||
30694 | @item E00 | |
30695 | The request was malformed, or @var{annex} was invalid. | |
30696 | ||
30697 | @item E @var{nn} | |
30698 | The offset was invalid, or there was an error encountered reading the data. | |
30699 | @var{nn} is a hex-encoded @code{errno} value. | |
30700 | ||
30701 | @item | |
30702 | An empty reply indicates the @var{object} string was not recognized by | |
30703 | the stub, or that the object does not support reading. | |
30704 | @end table | |
30705 | ||
30706 | @item qXfer:@var{object}:write:@var{annex}:@var{offset}:@var{data}@dots{} | |
30707 | @cindex write data into object, remote request | |
4aa995e1 | 30708 | @anchor{qXfer write} |
0876f84a DJ |
30709 | Write uninterpreted bytes into the target's special data area |
30710 | identified by the keyword @var{object}, starting at @var{offset} bytes | |
0e7f50da | 30711 | into the data. @var{data}@dots{} is the binary-encoded data |
0876f84a | 30712 | (@pxref{Binary Data}) to be written. The content and encoding of @var{annex} |
0e7f50da | 30713 | is specific to @var{object}; it can supply additional details about what data |
0876f84a DJ |
30714 | to access. |
30715 | ||
0e7f50da UW |
30716 | Here are the specific requests of this form defined so far. All |
30717 | @samp{qXfer:@var{object}:write:@dots{}} requests use the same reply | |
30718 | formats, listed below. | |
30719 | ||
30720 | @table @samp | |
4aa995e1 PA |
30721 | @item qXfer:siginfo:write::@var{offset}:@var{data}@dots{} |
30722 | @anchor{qXfer siginfo write} | |
30723 | Write @var{data} to the extra signal information on the target system. | |
30724 | The annex part of the generic @samp{qXfer} packet must be | |
30725 | empty (@pxref{qXfer write}). | |
30726 | ||
30727 | This packet is not probed by default; the remote stub must request it, | |
30728 | by supplying an appropriate @samp{qSupported} response | |
30729 | (@pxref{qSupported}). | |
30730 | ||
84fcdf95 | 30731 | @item qXfer:spu:write:@var{annex}:@var{offset}:@var{data}@dots{} |
0e7f50da UW |
30732 | @anchor{qXfer spu write} |
30733 | Write @var{data} to an @code{spufs} file on the target system. The | |
30734 | annex specifies which file to write; it must be of the form | |
30735 | @file{@var{id}/@var{name}}, where @var{id} specifies an SPU context ID | |
30736 | in the target process, and @var{name} identifes the @code{spufs} file | |
30737 | in that context to be accessed. | |
30738 | ||
30739 | This packet is not probed by default; the remote stub must request it, | |
30740 | by supplying an appropriate @samp{qSupported} response (@pxref{qSupported}). | |
30741 | @end table | |
0876f84a DJ |
30742 | |
30743 | Reply: | |
30744 | @table @samp | |
30745 | @item @var{nn} | |
30746 | @var{nn} (hex encoded) is the number of bytes written. | |
30747 | This may be fewer bytes than supplied in the request. | |
30748 | ||
30749 | @item E00 | |
30750 | The request was malformed, or @var{annex} was invalid. | |
30751 | ||
30752 | @item E @var{nn} | |
30753 | The offset was invalid, or there was an error encountered writing the data. | |
30754 | @var{nn} is a hex-encoded @code{errno} value. | |
30755 | ||
30756 | @item | |
30757 | An empty reply indicates the @var{object} string was not | |
30758 | recognized by the stub, or that the object does not support writing. | |
30759 | @end table | |
30760 | ||
30761 | @item qXfer:@var{object}:@var{operation}:@dots{} | |
30762 | Requests of this form may be added in the future. When a stub does | |
30763 | not recognize the @var{object} keyword, or its support for | |
30764 | @var{object} does not recognize the @var{operation} keyword, the stub | |
30765 | must respond with an empty packet. | |
30766 | ||
0b16c5cf PA |
30767 | @item qAttached:@var{pid} |
30768 | @cindex query attached, remote request | |
30769 | @cindex @samp{qAttached} packet | |
30770 | Return an indication of whether the remote server attached to an | |
30771 | existing process or created a new process. When the multiprocess | |
30772 | protocol extensions are supported (@pxref{multiprocess extensions}), | |
30773 | @var{pid} is an integer in hexadecimal format identifying the target | |
30774 | process. Otherwise, @value{GDBN} will omit the @var{pid} field and | |
30775 | the query packet will be simplified as @samp{qAttached}. | |
30776 | ||
30777 | This query is used, for example, to know whether the remote process | |
30778 | should be detached or killed when a @value{GDBN} session is ended with | |
30779 | the @code{quit} command. | |
30780 | ||
30781 | Reply: | |
30782 | @table @samp | |
30783 | @item 1 | |
30784 | The remote server attached to an existing process. | |
30785 | @item 0 | |
30786 | The remote server created a new process. | |
30787 | @item E @var{NN} | |
30788 | A badly formed request or an error was encountered. | |
30789 | @end table | |
30790 | ||
ee2d5c50 AC |
30791 | @end table |
30792 | ||
a1dcb23a DJ |
30793 | @node Architecture-Specific Protocol Details |
30794 | @section Architecture-Specific Protocol Details | |
30795 | ||
30796 | This section describes how the remote protocol is applied to specific | |
30797 | target architectures. Also see @ref{Standard Target Features}, for | |
30798 | details of XML target descriptions for each architecture. | |
30799 | ||
30800 | @subsection ARM | |
30801 | ||
30802 | @subsubsection Breakpoint Kinds | |
30803 | ||
30804 | These breakpoint kinds are defined for the @samp{Z0} and @samp{Z1} packets. | |
30805 | ||
30806 | @table @r | |
30807 | ||
30808 | @item 2 | |
30809 | 16-bit Thumb mode breakpoint. | |
30810 | ||
30811 | @item 3 | |
30812 | 32-bit Thumb mode (Thumb-2) breakpoint. | |
30813 | ||
30814 | @item 4 | |
30815 | 32-bit ARM mode breakpoint. | |
30816 | ||
30817 | @end table | |
30818 | ||
30819 | @subsection MIPS | |
30820 | ||
30821 | @subsubsection Register Packet Format | |
eb12ee30 | 30822 | |
b8ff78ce | 30823 | The following @code{g}/@code{G} packets have previously been defined. |
ee2d5c50 AC |
30824 | In the below, some thirty-two bit registers are transferred as |
30825 | sixty-four bits. Those registers should be zero/sign extended (which?) | |
599b237a BW |
30826 | to fill the space allocated. Register bytes are transferred in target |
30827 | byte order. The two nibbles within a register byte are transferred | |
ee2d5c50 | 30828 | most-significant - least-significant. |
eb12ee30 | 30829 | |
ee2d5c50 | 30830 | @table @r |
eb12ee30 | 30831 | |
8e04817f | 30832 | @item MIPS32 |
ee2d5c50 | 30833 | |
599b237a | 30834 | All registers are transferred as thirty-two bit quantities in the order: |
8e04817f AC |
30835 | 32 general-purpose; sr; lo; hi; bad; cause; pc; 32 floating-point |
30836 | registers; fsr; fir; fp. | |
eb12ee30 | 30837 | |
8e04817f | 30838 | @item MIPS64 |
ee2d5c50 | 30839 | |
599b237a | 30840 | All registers are transferred as sixty-four bit quantities (including |
8e04817f AC |
30841 | thirty-two bit registers such as @code{sr}). The ordering is the same |
30842 | as @code{MIPS32}. | |
eb12ee30 | 30843 | |
ee2d5c50 AC |
30844 | @end table |
30845 | ||
9d29849a JB |
30846 | @node Tracepoint Packets |
30847 | @section Tracepoint Packets | |
30848 | @cindex tracepoint packets | |
30849 | @cindex packets, tracepoint | |
30850 | ||
30851 | Here we describe the packets @value{GDBN} uses to implement | |
30852 | tracepoints (@pxref{Tracepoints}). | |
30853 | ||
30854 | @table @samp | |
30855 | ||
7a697b8d | 30856 | @item QTDP:@var{n}:@var{addr}:@var{ena}:@var{step}:@var{pass}[:F@var{flen}][:X@var{len},@var{bytes}]@r{[}-@r{]} |
9d29849a JB |
30857 | Create a new tracepoint, number @var{n}, at @var{addr}. If @var{ena} |
30858 | is @samp{E}, then the tracepoint is enabled; if it is @samp{D}, then | |
30859 | the tracepoint is disabled. @var{step} is the tracepoint's step | |
7a697b8d SS |
30860 | count, and @var{pass} is its pass count. If an @samp{F} is present, |
30861 | then the tracepoint is to be a fast tracepoint, and the @var{flen} is | |
30862 | the number of bytes that the target should copy elsewhere to make room | |
30863 | for the tracepoint. If an @samp{X} is present, it introduces a | |
30864 | tracepoint condition, which consists of a hexadecimal length, followed | |
30865 | by a comma and hex-encoded bytes, in a manner similar to action | |
30866 | encodings as described below. If the trailing @samp{-} is present, | |
30867 | further @samp{QTDP} packets will follow to specify this tracepoint's | |
30868 | actions. | |
9d29849a JB |
30869 | |
30870 | Replies: | |
30871 | @table @samp | |
30872 | @item OK | |
30873 | The packet was understood and carried out. | |
30874 | @item | |
30875 | The packet was not recognized. | |
30876 | @end table | |
30877 | ||
30878 | @item QTDP:-@var{n}:@var{addr}:@r{[}S@r{]}@var{action}@dots{}@r{[}-@r{]} | |
30879 | Define actions to be taken when a tracepoint is hit. @var{n} and | |
30880 | @var{addr} must be the same as in the initial @samp{QTDP} packet for | |
30881 | this tracepoint. This packet may only be sent immediately after | |
30882 | another @samp{QTDP} packet that ended with a @samp{-}. If the | |
30883 | trailing @samp{-} is present, further @samp{QTDP} packets will follow, | |
30884 | specifying more actions for this tracepoint. | |
30885 | ||
30886 | In the series of action packets for a given tracepoint, at most one | |
30887 | can have an @samp{S} before its first @var{action}. If such a packet | |
30888 | is sent, it and the following packets define ``while-stepping'' | |
30889 | actions. Any prior packets define ordinary actions --- that is, those | |
30890 | taken when the tracepoint is first hit. If no action packet has an | |
30891 | @samp{S}, then all the packets in the series specify ordinary | |
30892 | tracepoint actions. | |
30893 | ||
30894 | The @samp{@var{action}@dots{}} portion of the packet is a series of | |
30895 | actions, concatenated without separators. Each action has one of the | |
30896 | following forms: | |
30897 | ||
30898 | @table @samp | |
30899 | ||
30900 | @item R @var{mask} | |
30901 | Collect the registers whose bits are set in @var{mask}. @var{mask} is | |
599b237a | 30902 | a hexadecimal number whose @var{i}'th bit is set if register number |
9d29849a JB |
30903 | @var{i} should be collected. (The least significant bit is numbered |
30904 | zero.) Note that @var{mask} may be any number of digits long; it may | |
30905 | not fit in a 32-bit word. | |
30906 | ||
30907 | @item M @var{basereg},@var{offset},@var{len} | |
30908 | Collect @var{len} bytes of memory starting at the address in register | |
30909 | number @var{basereg}, plus @var{offset}. If @var{basereg} is | |
30910 | @samp{-1}, then the range has a fixed address: @var{offset} is the | |
30911 | address of the lowest byte to collect. The @var{basereg}, | |
599b237a | 30912 | @var{offset}, and @var{len} parameters are all unsigned hexadecimal |
9d29849a JB |
30913 | values (the @samp{-1} value for @var{basereg} is a special case). |
30914 | ||
30915 | @item X @var{len},@var{expr} | |
30916 | Evaluate @var{expr}, whose length is @var{len}, and collect memory as | |
30917 | it directs. @var{expr} is an agent expression, as described in | |
30918 | @ref{Agent Expressions}. Each byte of the expression is encoded as a | |
30919 | two-digit hex number in the packet; @var{len} is the number of bytes | |
30920 | in the expression (and thus one-half the number of hex digits in the | |
30921 | packet). | |
30922 | ||
30923 | @end table | |
30924 | ||
30925 | Any number of actions may be packed together in a single @samp{QTDP} | |
30926 | packet, as long as the packet does not exceed the maximum packet | |
c1947b85 JB |
30927 | length (400 bytes, for many stubs). There may be only one @samp{R} |
30928 | action per tracepoint, and it must precede any @samp{M} or @samp{X} | |
30929 | actions. Any registers referred to by @samp{M} and @samp{X} actions | |
30930 | must be collected by a preceding @samp{R} action. (The | |
30931 | ``while-stepping'' actions are treated as if they were attached to a | |
30932 | separate tracepoint, as far as these restrictions are concerned.) | |
9d29849a JB |
30933 | |
30934 | Replies: | |
30935 | @table @samp | |
30936 | @item OK | |
30937 | The packet was understood and carried out. | |
30938 | @item | |
30939 | The packet was not recognized. | |
30940 | @end table | |
30941 | ||
f61e138d SS |
30942 | @item QTDV:@var{n}:@var{value} |
30943 | @cindex define trace state variable, remote request | |
30944 | @cindex @samp{QTDV} packet | |
30945 | Create a new trace state variable, number @var{n}, with an initial | |
30946 | value of @var{value}, which is a 64-bit signed integer. Both @var{n} | |
30947 | and @var{value} are encoded as hexadecimal values. @value{GDBN} has | |
30948 | the option of not using this packet for initial values of zero; the | |
30949 | target should simply create the trace state variables as they are | |
30950 | mentioned in expressions. | |
30951 | ||
9d29849a JB |
30952 | @item QTFrame:@var{n} |
30953 | Select the @var{n}'th tracepoint frame from the buffer, and use the | |
30954 | register and memory contents recorded there to answer subsequent | |
30955 | request packets from @value{GDBN}. | |
30956 | ||
30957 | A successful reply from the stub indicates that the stub has found the | |
30958 | requested frame. The response is a series of parts, concatenated | |
30959 | without separators, describing the frame we selected. Each part has | |
30960 | one of the following forms: | |
30961 | ||
30962 | @table @samp | |
30963 | @item F @var{f} | |
30964 | The selected frame is number @var{n} in the trace frame buffer; | |
599b237a | 30965 | @var{f} is a hexadecimal number. If @var{f} is @samp{-1}, then there |
9d29849a JB |
30966 | was no frame matching the criteria in the request packet. |
30967 | ||
30968 | @item T @var{t} | |
30969 | The selected trace frame records a hit of tracepoint number @var{t}; | |
599b237a | 30970 | @var{t} is a hexadecimal number. |
9d29849a JB |
30971 | |
30972 | @end table | |
30973 | ||
30974 | @item QTFrame:pc:@var{addr} | |
30975 | Like @samp{QTFrame:@var{n}}, but select the first tracepoint frame after the | |
30976 | currently selected frame whose PC is @var{addr}; | |
599b237a | 30977 | @var{addr} is a hexadecimal number. |
9d29849a JB |
30978 | |
30979 | @item QTFrame:tdp:@var{t} | |
30980 | Like @samp{QTFrame:@var{n}}, but select the first tracepoint frame after the | |
30981 | currently selected frame that is a hit of tracepoint @var{t}; @var{t} | |
599b237a | 30982 | is a hexadecimal number. |
9d29849a JB |
30983 | |
30984 | @item QTFrame:range:@var{start}:@var{end} | |
30985 | Like @samp{QTFrame:@var{n}}, but select the first tracepoint frame after the | |
30986 | currently selected frame whose PC is between @var{start} (inclusive) | |
081dfbf7 | 30987 | and @var{end} (inclusive); @var{start} and @var{end} are hexadecimal |
9d29849a JB |
30988 | numbers. |
30989 | ||
30990 | @item QTFrame:outside:@var{start}:@var{end} | |
30991 | Like @samp{QTFrame:range:@var{start}:@var{end}}, but select the first | |
081dfbf7 | 30992 | frame @emph{outside} the given range of addresses (exclusive). |
9d29849a JB |
30993 | |
30994 | @item QTStart | |
30995 | Begin the tracepoint experiment. Begin collecting data from tracepoint | |
30996 | hits in the trace frame buffer. | |
30997 | ||
30998 | @item QTStop | |
30999 | End the tracepoint experiment. Stop collecting trace frames. | |
31000 | ||
31001 | @item QTinit | |
31002 | Clear the table of tracepoints, and empty the trace frame buffer. | |
31003 | ||
31004 | @item QTro:@var{start1},@var{end1}:@var{start2},@var{end2}:@dots{} | |
31005 | Establish the given ranges of memory as ``transparent''. The stub | |
31006 | will answer requests for these ranges from memory's current contents, | |
31007 | if they were not collected as part of the tracepoint hit. | |
31008 | ||
31009 | @value{GDBN} uses this to mark read-only regions of memory, like those | |
31010 | containing program code. Since these areas never change, they should | |
31011 | still have the same contents they did when the tracepoint was hit, so | |
31012 | there's no reason for the stub to refuse to provide their contents. | |
31013 | ||
d5551862 SS |
31014 | @item QTDisconnected:@var{value} |
31015 | Set the choice to what to do with the tracing run when @value{GDBN} | |
31016 | disconnects from the target. A @var{value} of 1 directs the target to | |
31017 | continue the tracing run, while 0 tells the target to stop tracing if | |
31018 | @value{GDBN} is no longer in the picture. | |
31019 | ||
9d29849a JB |
31020 | @item qTStatus |
31021 | Ask the stub if there is a trace experiment running right now. | |
31022 | ||
31023 | Replies: | |
31024 | @table @samp | |
31025 | @item T0 | |
31026 | There is no trace experiment running. | |
31027 | @item T1 | |
31028 | There is a trace experiment running. | |
31029 | @end table | |
31030 | ||
f61e138d SS |
31031 | @item qTV:@var{var} |
31032 | @cindex trace state variable value, remote request | |
31033 | @cindex @samp{qTV} packet | |
31034 | Ask the stub for the value of the trace state variable number @var{var}. | |
31035 | ||
31036 | Replies: | |
31037 | @table @samp | |
31038 | @item V@var{value} | |
31039 | The value of the variable is @var{value}. This will be the current | |
31040 | value of the variable if the user is examining a running target, or a | |
31041 | saved value if the variable was collected in the trace frame that the | |
31042 | user is looking at. Note that multiple requests may result in | |
31043 | different reply values, such as when requesting values while the | |
31044 | program is running. | |
31045 | ||
31046 | @item U | |
31047 | The value of the variable is unknown. This would occur, for example, | |
31048 | if the user is examining a trace frame in which the requested variable | |
31049 | was not collected. | |
9d29849a JB |
31050 | @end table |
31051 | ||
d5551862 SS |
31052 | @item qTfP |
31053 | @itemx qTsP | |
31054 | These packets request data about tracepoints that are being used by | |
31055 | the target. @value{GDBN} sends @code{qTfP} to get the first piece | |
31056 | of data, and multiple @code{qTsP} to get additional pieces. Replies | |
31057 | to these packets generally take the form of the @code{QTDP} packets | |
31058 | that define tracepoints. (FIXME add detailed syntax) | |
31059 | ||
00bf0b85 SS |
31060 | @item qTfV |
31061 | @itemx qTsV | |
31062 | These packets request data about trace state variables that are on the | |
31063 | target. @value{GDBN} sends @code{qTfV} to get the first vari of data, | |
31064 | and multiple @code{qTsV} to get additional variables. Replies to | |
31065 | these packets follow the syntax of the @code{QTDV} packets that define | |
31066 | trace state variables. | |
31067 | ||
31068 | @item QTSave:@var{filename} | |
31069 | This packet directs the target to save trace data to the file name | |
31070 | @var{filename} in the target's filesystem. @var{filename} is encoded | |
31071 | as a hex string; the interpretation of the file name (relative vs | |
31072 | absolute, wild cards, etc) is up to the target. | |
31073 | ||
31074 | @item qTBuffer:@var{offset},@var{len} | |
31075 | Return up to @var{len} bytes of the current contents of trace buffer, | |
31076 | starting at @var{offset}. The trace buffer is treated as if it were | |
31077 | a contiguous collection of traceframes, as per the trace file format. | |
31078 | The reply consists as many hex-encoded bytes as the target can deliver | |
31079 | in a packet; it is not an error to return fewer than were asked for. | |
31080 | A reply consisting of just @code{l} indicates that no bytes are | |
31081 | available. | |
31082 | ||
f61e138d | 31083 | @end table |
9d29849a | 31084 | |
a6b151f1 DJ |
31085 | @node Host I/O Packets |
31086 | @section Host I/O Packets | |
31087 | @cindex Host I/O, remote protocol | |
31088 | @cindex file transfer, remote protocol | |
31089 | ||
31090 | The @dfn{Host I/O} packets allow @value{GDBN} to perform I/O | |
31091 | operations on the far side of a remote link. For example, Host I/O is | |
31092 | used to upload and download files to a remote target with its own | |
31093 | filesystem. Host I/O uses the same constant values and data structure | |
31094 | layout as the target-initiated File-I/O protocol. However, the | |
31095 | Host I/O packets are structured differently. The target-initiated | |
31096 | protocol relies on target memory to store parameters and buffers. | |
31097 | Host I/O requests are initiated by @value{GDBN}, and the | |
31098 | target's memory is not involved. @xref{File-I/O Remote Protocol | |
31099 | Extension}, for more details on the target-initiated protocol. | |
31100 | ||
31101 | The Host I/O request packets all encode a single operation along with | |
31102 | its arguments. They have this format: | |
31103 | ||
31104 | @table @samp | |
31105 | ||
31106 | @item vFile:@var{operation}: @var{parameter}@dots{} | |
31107 | @var{operation} is the name of the particular request; the target | |
31108 | should compare the entire packet name up to the second colon when checking | |
31109 | for a supported operation. The format of @var{parameter} depends on | |
31110 | the operation. Numbers are always passed in hexadecimal. Negative | |
31111 | numbers have an explicit minus sign (i.e.@: two's complement is not | |
31112 | used). Strings (e.g.@: filenames) are encoded as a series of | |
31113 | hexadecimal bytes. The last argument to a system call may be a | |
31114 | buffer of escaped binary data (@pxref{Binary Data}). | |
31115 | ||
31116 | @end table | |
31117 | ||
31118 | The valid responses to Host I/O packets are: | |
31119 | ||
31120 | @table @samp | |
31121 | ||
31122 | @item F @var{result} [, @var{errno}] [; @var{attachment}] | |
31123 | @var{result} is the integer value returned by this operation, usually | |
31124 | non-negative for success and -1 for errors. If an error has occured, | |
31125 | @var{errno} will be included in the result. @var{errno} will have a | |
31126 | value defined by the File-I/O protocol (@pxref{Errno Values}). For | |
31127 | operations which return data, @var{attachment} supplies the data as a | |
31128 | binary buffer. Binary buffers in response packets are escaped in the | |
31129 | normal way (@pxref{Binary Data}). See the individual packet | |
31130 | documentation for the interpretation of @var{result} and | |
31131 | @var{attachment}. | |
31132 | ||
31133 | @item | |
31134 | An empty response indicates that this operation is not recognized. | |
31135 | ||
31136 | @end table | |
31137 | ||
31138 | These are the supported Host I/O operations: | |
31139 | ||
31140 | @table @samp | |
31141 | @item vFile:open: @var{pathname}, @var{flags}, @var{mode} | |
31142 | Open a file at @var{pathname} and return a file descriptor for it, or | |
31143 | return -1 if an error occurs. @var{pathname} is a string, | |
31144 | @var{flags} is an integer indicating a mask of open flags | |
31145 | (@pxref{Open Flags}), and @var{mode} is an integer indicating a mask | |
31146 | of mode bits to use if the file is created (@pxref{mode_t Values}). | |
c1c25a1a | 31147 | @xref{open}, for details of the open flags and mode values. |
a6b151f1 DJ |
31148 | |
31149 | @item vFile:close: @var{fd} | |
31150 | Close the open file corresponding to @var{fd} and return 0, or | |
31151 | -1 if an error occurs. | |
31152 | ||
31153 | @item vFile:pread: @var{fd}, @var{count}, @var{offset} | |
31154 | Read data from the open file corresponding to @var{fd}. Up to | |
31155 | @var{count} bytes will be read from the file, starting at @var{offset} | |
31156 | relative to the start of the file. The target may read fewer bytes; | |
31157 | common reasons include packet size limits and an end-of-file | |
31158 | condition. The number of bytes read is returned. Zero should only be | |
31159 | returned for a successful read at the end of the file, or if | |
31160 | @var{count} was zero. | |
31161 | ||
31162 | The data read should be returned as a binary attachment on success. | |
31163 | If zero bytes were read, the response should include an empty binary | |
31164 | attachment (i.e.@: a trailing semicolon). The return value is the | |
31165 | number of target bytes read; the binary attachment may be longer if | |
31166 | some characters were escaped. | |
31167 | ||
31168 | @item vFile:pwrite: @var{fd}, @var{offset}, @var{data} | |
31169 | Write @var{data} (a binary buffer) to the open file corresponding | |
31170 | to @var{fd}. Start the write at @var{offset} from the start of the | |
31171 | file. Unlike many @code{write} system calls, there is no | |
31172 | separate @var{count} argument; the length of @var{data} in the | |
31173 | packet is used. @samp{vFile:write} returns the number of bytes written, | |
31174 | which may be shorter than the length of @var{data}, or -1 if an | |
31175 | error occurred. | |
31176 | ||
31177 | @item vFile:unlink: @var{pathname} | |
31178 | Delete the file at @var{pathname} on the target. Return 0, | |
31179 | or -1 if an error occurs. @var{pathname} is a string. | |
31180 | ||
31181 | @end table | |
31182 | ||
9a6253be KB |
31183 | @node Interrupts |
31184 | @section Interrupts | |
31185 | @cindex interrupts (remote protocol) | |
31186 | ||
31187 | When a program on the remote target is running, @value{GDBN} may | |
9a7071a8 JB |
31188 | attempt to interrupt it by sending a @samp{Ctrl-C}, @code{BREAK} or |
31189 | a @code{BREAK} followed by @code{g}, | |
31190 | control of which is specified via @value{GDBN}'s @samp{interrupt-sequence}. | |
9a6253be KB |
31191 | |
31192 | The precise meaning of @code{BREAK} is defined by the transport | |
8775bb90 MS |
31193 | mechanism and may, in fact, be undefined. @value{GDBN} does not |
31194 | currently define a @code{BREAK} mechanism for any of the network | |
31195 | interfaces except for TCP, in which case @value{GDBN} sends the | |
31196 | @code{telnet} BREAK sequence. | |
9a6253be KB |
31197 | |
31198 | @samp{Ctrl-C}, on the other hand, is defined and implemented for all | |
31199 | transport mechanisms. It is represented by sending the single byte | |
31200 | @code{0x03} without any of the usual packet overhead described in | |
31201 | the Overview section (@pxref{Overview}). When a @code{0x03} byte is | |
31202 | transmitted as part of a packet, it is considered to be packet data | |
31203 | and does @emph{not} represent an interrupt. E.g., an @samp{X} packet | |
0876f84a | 31204 | (@pxref{X packet}), used for binary downloads, may include an unescaped |
9a6253be KB |
31205 | @code{0x03} as part of its packet. |
31206 | ||
9a7071a8 JB |
31207 | @code{BREAK} followed by @code{g} is also known as Magic SysRq g. |
31208 | When Linux kernel receives this sequence from serial port, | |
31209 | it stops execution and connects to gdb. | |
31210 | ||
9a6253be KB |
31211 | Stubs are not required to recognize these interrupt mechanisms and the |
31212 | precise meaning associated with receipt of the interrupt is | |
8b23ecc4 SL |
31213 | implementation defined. If the target supports debugging of multiple |
31214 | threads and/or processes, it should attempt to interrupt all | |
31215 | currently-executing threads and processes. | |
31216 | If the stub is successful at interrupting the | |
31217 | running program, it should send one of the stop | |
31218 | reply packets (@pxref{Stop Reply Packets}) to @value{GDBN} as a result | |
31219 | of successfully stopping the program in all-stop mode, and a stop reply | |
31220 | for each stopped thread in non-stop mode. | |
31221 | Interrupts received while the | |
31222 | program is stopped are discarded. | |
31223 | ||
31224 | @node Notification Packets | |
31225 | @section Notification Packets | |
31226 | @cindex notification packets | |
31227 | @cindex packets, notification | |
31228 | ||
31229 | The @value{GDBN} remote serial protocol includes @dfn{notifications}, | |
31230 | packets that require no acknowledgment. Both the GDB and the stub | |
31231 | may send notifications (although the only notifications defined at | |
31232 | present are sent by the stub). Notifications carry information | |
31233 | without incurring the round-trip latency of an acknowledgment, and so | |
31234 | are useful for low-impact communications where occasional packet loss | |
31235 | is not a problem. | |
31236 | ||
31237 | A notification packet has the form @samp{% @var{data} # | |
31238 | @var{checksum}}, where @var{data} is the content of the notification, | |
31239 | and @var{checksum} is a checksum of @var{data}, computed and formatted | |
31240 | as for ordinary @value{GDBN} packets. A notification's @var{data} | |
31241 | never contains @samp{$}, @samp{%} or @samp{#} characters. Upon | |
31242 | receiving a notification, the recipient sends no @samp{+} or @samp{-} | |
31243 | to acknowledge the notification's receipt or to report its corruption. | |
31244 | ||
31245 | Every notification's @var{data} begins with a name, which contains no | |
31246 | colon characters, followed by a colon character. | |
31247 | ||
31248 | Recipients should silently ignore corrupted notifications and | |
31249 | notifications they do not understand. Recipients should restart | |
31250 | timeout periods on receipt of a well-formed notification, whether or | |
31251 | not they understand it. | |
31252 | ||
31253 | Senders should only send the notifications described here when this | |
31254 | protocol description specifies that they are permitted. In the | |
31255 | future, we may extend the protocol to permit existing notifications in | |
31256 | new contexts; this rule helps older senders avoid confusing newer | |
31257 | recipients. | |
31258 | ||
31259 | (Older versions of @value{GDBN} ignore bytes received until they see | |
31260 | the @samp{$} byte that begins an ordinary packet, so new stubs may | |
31261 | transmit notifications without fear of confusing older clients. There | |
31262 | are no notifications defined for @value{GDBN} to send at the moment, but we | |
31263 | assume that most older stubs would ignore them, as well.) | |
31264 | ||
31265 | The following notification packets from the stub to @value{GDBN} are | |
31266 | defined: | |
31267 | ||
31268 | @table @samp | |
31269 | @item Stop: @var{reply} | |
31270 | Report an asynchronous stop event in non-stop mode. | |
31271 | The @var{reply} has the form of a stop reply, as | |
31272 | described in @ref{Stop Reply Packets}. Refer to @ref{Remote Non-Stop}, | |
31273 | for information on how these notifications are acknowledged by | |
31274 | @value{GDBN}. | |
31275 | @end table | |
31276 | ||
31277 | @node Remote Non-Stop | |
31278 | @section Remote Protocol Support for Non-Stop Mode | |
31279 | ||
31280 | @value{GDBN}'s remote protocol supports non-stop debugging of | |
31281 | multi-threaded programs, as described in @ref{Non-Stop Mode}. If the stub | |
31282 | supports non-stop mode, it should report that to @value{GDBN} by including | |
31283 | @samp{QNonStop+} in its @samp{qSupported} response (@pxref{qSupported}). | |
31284 | ||
31285 | @value{GDBN} typically sends a @samp{QNonStop} packet only when | |
31286 | establishing a new connection with the stub. Entering non-stop mode | |
31287 | does not alter the state of any currently-running threads, but targets | |
31288 | must stop all threads in any already-attached processes when entering | |
31289 | all-stop mode. @value{GDBN} uses the @samp{?} packet as necessary to | |
31290 | probe the target state after a mode change. | |
31291 | ||
31292 | In non-stop mode, when an attached process encounters an event that | |
31293 | would otherwise be reported with a stop reply, it uses the | |
31294 | asynchronous notification mechanism (@pxref{Notification Packets}) to | |
31295 | inform @value{GDBN}. In contrast to all-stop mode, where all threads | |
31296 | in all processes are stopped when a stop reply is sent, in non-stop | |
31297 | mode only the thread reporting the stop event is stopped. That is, | |
31298 | when reporting a @samp{S} or @samp{T} response to indicate completion | |
31299 | of a step operation, hitting a breakpoint, or a fault, only the | |
31300 | affected thread is stopped; any other still-running threads continue | |
31301 | to run. When reporting a @samp{W} or @samp{X} response, all running | |
31302 | threads belonging to other attached processes continue to run. | |
31303 | ||
31304 | Only one stop reply notification at a time may be pending; if | |
31305 | additional stop events occur before @value{GDBN} has acknowledged the | |
31306 | previous notification, they must be queued by the stub for later | |
31307 | synchronous transmission in response to @samp{vStopped} packets from | |
31308 | @value{GDBN}. Because the notification mechanism is unreliable, | |
31309 | the stub is permitted to resend a stop reply notification | |
31310 | if it believes @value{GDBN} may not have received it. @value{GDBN} | |
31311 | ignores additional stop reply notifications received before it has | |
31312 | finished processing a previous notification and the stub has completed | |
31313 | sending any queued stop events. | |
31314 | ||
31315 | Otherwise, @value{GDBN} must be prepared to receive a stop reply | |
31316 | notification at any time. Specifically, they may appear when | |
31317 | @value{GDBN} is not otherwise reading input from the stub, or when | |
31318 | @value{GDBN} is expecting to read a normal synchronous response or a | |
31319 | @samp{+}/@samp{-} acknowledgment to a packet it has sent. | |
31320 | Notification packets are distinct from any other communication from | |
31321 | the stub so there is no ambiguity. | |
31322 | ||
31323 | After receiving a stop reply notification, @value{GDBN} shall | |
31324 | acknowledge it by sending a @samp{vStopped} packet (@pxref{vStopped packet}) | |
31325 | as a regular, synchronous request to the stub. Such acknowledgment | |
31326 | is not required to happen immediately, as @value{GDBN} is permitted to | |
31327 | send other, unrelated packets to the stub first, which the stub should | |
31328 | process normally. | |
31329 | ||
31330 | Upon receiving a @samp{vStopped} packet, if the stub has other queued | |
31331 | stop events to report to @value{GDBN}, it shall respond by sending a | |
31332 | normal stop reply response. @value{GDBN} shall then send another | |
31333 | @samp{vStopped} packet to solicit further responses; again, it is | |
31334 | permitted to send other, unrelated packets as well which the stub | |
31335 | should process normally. | |
31336 | ||
31337 | If the stub receives a @samp{vStopped} packet and there are no | |
31338 | additional stop events to report, the stub shall return an @samp{OK} | |
31339 | response. At this point, if further stop events occur, the stub shall | |
31340 | send a new stop reply notification, @value{GDBN} shall accept the | |
31341 | notification, and the process shall be repeated. | |
31342 | ||
31343 | In non-stop mode, the target shall respond to the @samp{?} packet as | |
31344 | follows. First, any incomplete stop reply notification/@samp{vStopped} | |
31345 | sequence in progress is abandoned. The target must begin a new | |
31346 | sequence reporting stop events for all stopped threads, whether or not | |
31347 | it has previously reported those events to @value{GDBN}. The first | |
31348 | stop reply is sent as a synchronous reply to the @samp{?} packet, and | |
31349 | subsequent stop replies are sent as responses to @samp{vStopped} packets | |
31350 | using the mechanism described above. The target must not send | |
31351 | asynchronous stop reply notifications until the sequence is complete. | |
31352 | If all threads are running when the target receives the @samp{?} packet, | |
31353 | or if the target is not attached to any process, it shall respond | |
31354 | @samp{OK}. | |
9a6253be | 31355 | |
a6f3e723 SL |
31356 | @node Packet Acknowledgment |
31357 | @section Packet Acknowledgment | |
31358 | ||
31359 | @cindex acknowledgment, for @value{GDBN} remote | |
31360 | @cindex packet acknowledgment, for @value{GDBN} remote | |
31361 | By default, when either the host or the target machine receives a packet, | |
31362 | the first response expected is an acknowledgment: either @samp{+} (to indicate | |
31363 | the package was received correctly) or @samp{-} (to request retransmission). | |
31364 | This mechanism allows the @value{GDBN} remote protocol to operate over | |
31365 | unreliable transport mechanisms, such as a serial line. | |
31366 | ||
31367 | In cases where the transport mechanism is itself reliable (such as a pipe or | |
31368 | TCP connection), the @samp{+}/@samp{-} acknowledgments are redundant. | |
31369 | It may be desirable to disable them in that case to reduce communication | |
31370 | overhead, or for other reasons. This can be accomplished by means of the | |
31371 | @samp{QStartNoAckMode} packet; @pxref{QStartNoAckMode}. | |
31372 | ||
31373 | When in no-acknowledgment mode, neither the stub nor @value{GDBN} shall send or | |
31374 | expect @samp{+}/@samp{-} protocol acknowledgments. The packet | |
31375 | and response format still includes the normal checksum, as described in | |
31376 | @ref{Overview}, but the checksum may be ignored by the receiver. | |
31377 | ||
31378 | If the stub supports @samp{QStartNoAckMode} and prefers to operate in | |
31379 | no-acknowledgment mode, it should report that to @value{GDBN} | |
31380 | by including @samp{QStartNoAckMode+} in its response to @samp{qSupported}; | |
31381 | @pxref{qSupported}. | |
31382 | If @value{GDBN} also supports @samp{QStartNoAckMode} and it has not been | |
31383 | disabled via the @code{set remote noack-packet off} command | |
31384 | (@pxref{Remote Configuration}), | |
31385 | @value{GDBN} may then send a @samp{QStartNoAckMode} packet to the stub. | |
31386 | Only then may the stub actually turn off packet acknowledgments. | |
31387 | @value{GDBN} sends a final @samp{+} acknowledgment of the stub's @samp{OK} | |
31388 | response, which can be safely ignored by the stub. | |
31389 | ||
31390 | Note that @code{set remote noack-packet} command only affects negotiation | |
31391 | between @value{GDBN} and the stub when subsequent connections are made; | |
31392 | it does not affect the protocol acknowledgment state for any current | |
31393 | connection. | |
31394 | Since @samp{+}/@samp{-} acknowledgments are enabled by default when a | |
31395 | new connection is established, | |
31396 | there is also no protocol request to re-enable the acknowledgments | |
31397 | for the current connection, once disabled. | |
31398 | ||
ee2d5c50 AC |
31399 | @node Examples |
31400 | @section Examples | |
eb12ee30 | 31401 | |
8e04817f AC |
31402 | Example sequence of a target being re-started. Notice how the restart |
31403 | does not get any direct output: | |
eb12ee30 | 31404 | |
474c8240 | 31405 | @smallexample |
d2c6833e AC |
31406 | -> @code{R00} |
31407 | <- @code{+} | |
8e04817f | 31408 | @emph{target restarts} |
d2c6833e | 31409 | -> @code{?} |
8e04817f | 31410 | <- @code{+} |
d2c6833e AC |
31411 | <- @code{T001:1234123412341234} |
31412 | -> @code{+} | |
474c8240 | 31413 | @end smallexample |
eb12ee30 | 31414 | |
8e04817f | 31415 | Example sequence of a target being stepped by a single instruction: |
eb12ee30 | 31416 | |
474c8240 | 31417 | @smallexample |
d2c6833e | 31418 | -> @code{G1445@dots{}} |
8e04817f | 31419 | <- @code{+} |
d2c6833e AC |
31420 | -> @code{s} |
31421 | <- @code{+} | |
31422 | @emph{time passes} | |
31423 | <- @code{T001:1234123412341234} | |
8e04817f | 31424 | -> @code{+} |
d2c6833e | 31425 | -> @code{g} |
8e04817f | 31426 | <- @code{+} |
d2c6833e AC |
31427 | <- @code{1455@dots{}} |
31428 | -> @code{+} | |
474c8240 | 31429 | @end smallexample |
eb12ee30 | 31430 | |
79a6e687 BW |
31431 | @node File-I/O Remote Protocol Extension |
31432 | @section File-I/O Remote Protocol Extension | |
0ce1b118 CV |
31433 | @cindex File-I/O remote protocol extension |
31434 | ||
31435 | @menu | |
31436 | * File-I/O Overview:: | |
79a6e687 BW |
31437 | * Protocol Basics:: |
31438 | * The F Request Packet:: | |
31439 | * The F Reply Packet:: | |
31440 | * The Ctrl-C Message:: | |
0ce1b118 | 31441 | * Console I/O:: |
79a6e687 | 31442 | * List of Supported Calls:: |
db2e3e2e | 31443 | * Protocol-specific Representation of Datatypes:: |
0ce1b118 CV |
31444 | * Constants:: |
31445 | * File-I/O Examples:: | |
31446 | @end menu | |
31447 | ||
31448 | @node File-I/O Overview | |
31449 | @subsection File-I/O Overview | |
31450 | @cindex file-i/o overview | |
31451 | ||
9c16f35a | 31452 | The @dfn{File I/O remote protocol extension} (short: File-I/O) allows the |
fc320d37 | 31453 | target to use the host's file system and console I/O to perform various |
0ce1b118 | 31454 | system calls. System calls on the target system are translated into a |
fc320d37 SL |
31455 | remote protocol packet to the host system, which then performs the needed |
31456 | actions and returns a response packet to the target system. | |
0ce1b118 CV |
31457 | This simulates file system operations even on targets that lack file systems. |
31458 | ||
fc320d37 SL |
31459 | The protocol is defined to be independent of both the host and target systems. |
31460 | It uses its own internal representation of datatypes and values. Both | |
0ce1b118 | 31461 | @value{GDBN} and the target's @value{GDBN} stub are responsible for |
fc320d37 SL |
31462 | translating the system-dependent value representations into the internal |
31463 | protocol representations when data is transmitted. | |
0ce1b118 | 31464 | |
fc320d37 SL |
31465 | The communication is synchronous. A system call is possible only when |
31466 | @value{GDBN} is waiting for a response from the @samp{C}, @samp{c}, @samp{S} | |
31467 | or @samp{s} packets. While @value{GDBN} handles the request for a system call, | |
0ce1b118 | 31468 | the target is stopped to allow deterministic access to the target's |
fc320d37 SL |
31469 | memory. Therefore File-I/O is not interruptible by target signals. On |
31470 | the other hand, it is possible to interrupt File-I/O by a user interrupt | |
c8aa23ab | 31471 | (@samp{Ctrl-C}) within @value{GDBN}. |
0ce1b118 CV |
31472 | |
31473 | The target's request to perform a host system call does not finish | |
31474 | the latest @samp{C}, @samp{c}, @samp{S} or @samp{s} action. That means, | |
31475 | after finishing the system call, the target returns to continuing the | |
31476 | previous activity (continue, step). No additional continue or step | |
31477 | request from @value{GDBN} is required. | |
31478 | ||
31479 | @smallexample | |
f7dc1244 | 31480 | (@value{GDBP}) continue |
0ce1b118 CV |
31481 | <- target requests 'system call X' |
31482 | target is stopped, @value{GDBN} executes system call | |
3f94c067 BW |
31483 | -> @value{GDBN} returns result |
31484 | ... target continues, @value{GDBN} returns to wait for the target | |
0ce1b118 CV |
31485 | <- target hits breakpoint and sends a Txx packet |
31486 | @end smallexample | |
31487 | ||
fc320d37 SL |
31488 | The protocol only supports I/O on the console and to regular files on |
31489 | the host file system. Character or block special devices, pipes, | |
31490 | named pipes, sockets or any other communication method on the host | |
0ce1b118 CV |
31491 | system are not supported by this protocol. |
31492 | ||
8b23ecc4 SL |
31493 | File I/O is not supported in non-stop mode. |
31494 | ||
79a6e687 BW |
31495 | @node Protocol Basics |
31496 | @subsection Protocol Basics | |
0ce1b118 CV |
31497 | @cindex protocol basics, file-i/o |
31498 | ||
fc320d37 SL |
31499 | The File-I/O protocol uses the @code{F} packet as the request as well |
31500 | as reply packet. Since a File-I/O system call can only occur when | |
31501 | @value{GDBN} is waiting for a response from the continuing or stepping target, | |
31502 | the File-I/O request is a reply that @value{GDBN} has to expect as a result | |
31503 | of a previous @samp{C}, @samp{c}, @samp{S} or @samp{s} packet. | |
0ce1b118 CV |
31504 | This @code{F} packet contains all information needed to allow @value{GDBN} |
31505 | to call the appropriate host system call: | |
31506 | ||
31507 | @itemize @bullet | |
b383017d | 31508 | @item |
0ce1b118 CV |
31509 | A unique identifier for the requested system call. |
31510 | ||
31511 | @item | |
31512 | All parameters to the system call. Pointers are given as addresses | |
31513 | in the target memory address space. Pointers to strings are given as | |
b383017d | 31514 | pointer/length pair. Numerical values are given as they are. |
db2e3e2e | 31515 | Numerical control flags are given in a protocol-specific representation. |
0ce1b118 CV |
31516 | |
31517 | @end itemize | |
31518 | ||
fc320d37 | 31519 | At this point, @value{GDBN} has to perform the following actions. |
0ce1b118 CV |
31520 | |
31521 | @itemize @bullet | |
b383017d | 31522 | @item |
fc320d37 SL |
31523 | If the parameters include pointer values to data needed as input to a |
31524 | system call, @value{GDBN} requests this data from the target with a | |
0ce1b118 CV |
31525 | standard @code{m} packet request. This additional communication has to be |
31526 | expected by the target implementation and is handled as any other @code{m} | |
31527 | packet. | |
31528 | ||
31529 | @item | |
31530 | @value{GDBN} translates all value from protocol representation to host | |
31531 | representation as needed. Datatypes are coerced into the host types. | |
31532 | ||
31533 | @item | |
fc320d37 | 31534 | @value{GDBN} calls the system call. |
0ce1b118 CV |
31535 | |
31536 | @item | |
31537 | It then coerces datatypes back to protocol representation. | |
31538 | ||
31539 | @item | |
fc320d37 SL |
31540 | If the system call is expected to return data in buffer space specified |
31541 | by pointer parameters to the call, the data is transmitted to the | |
0ce1b118 CV |
31542 | target using a @code{M} or @code{X} packet. This packet has to be expected |
31543 | by the target implementation and is handled as any other @code{M} or @code{X} | |
31544 | packet. | |
31545 | ||
31546 | @end itemize | |
31547 | ||
31548 | Eventually @value{GDBN} replies with another @code{F} packet which contains all | |
31549 | necessary information for the target to continue. This at least contains | |
31550 | ||
31551 | @itemize @bullet | |
31552 | @item | |
31553 | Return value. | |
31554 | ||
31555 | @item | |
31556 | @code{errno}, if has been changed by the system call. | |
31557 | ||
31558 | @item | |
31559 | ``Ctrl-C'' flag. | |
31560 | ||
31561 | @end itemize | |
31562 | ||
31563 | After having done the needed type and value coercion, the target continues | |
31564 | the latest continue or step action. | |
31565 | ||
79a6e687 BW |
31566 | @node The F Request Packet |
31567 | @subsection The @code{F} Request Packet | |
0ce1b118 CV |
31568 | @cindex file-i/o request packet |
31569 | @cindex @code{F} request packet | |
31570 | ||
31571 | The @code{F} request packet has the following format: | |
31572 | ||
31573 | @table @samp | |
fc320d37 | 31574 | @item F@var{call-id},@var{parameter@dots{}} |
0ce1b118 CV |
31575 | |
31576 | @var{call-id} is the identifier to indicate the host system call to be called. | |
31577 | This is just the name of the function. | |
31578 | ||
fc320d37 SL |
31579 | @var{parameter@dots{}} are the parameters to the system call. |
31580 | Parameters are hexadecimal integer values, either the actual values in case | |
31581 | of scalar datatypes, pointers to target buffer space in case of compound | |
31582 | datatypes and unspecified memory areas, or pointer/length pairs in case | |
31583 | of string parameters. These are appended to the @var{call-id} as a | |
31584 | comma-delimited list. All values are transmitted in ASCII | |
31585 | string representation, pointer/length pairs separated by a slash. | |
0ce1b118 | 31586 | |
b383017d | 31587 | @end table |
0ce1b118 | 31588 | |
fc320d37 | 31589 | |
0ce1b118 | 31590 | |
79a6e687 BW |
31591 | @node The F Reply Packet |
31592 | @subsection The @code{F} Reply Packet | |
0ce1b118 CV |
31593 | @cindex file-i/o reply packet |
31594 | @cindex @code{F} reply packet | |
31595 | ||
31596 | The @code{F} reply packet has the following format: | |
31597 | ||
31598 | @table @samp | |
31599 | ||
d3bdde98 | 31600 | @item F@var{retcode},@var{errno},@var{Ctrl-C flag};@var{call-specific attachment} |
0ce1b118 CV |
31601 | |
31602 | @var{retcode} is the return code of the system call as hexadecimal value. | |
31603 | ||
db2e3e2e BW |
31604 | @var{errno} is the @code{errno} set by the call, in protocol-specific |
31605 | representation. | |
0ce1b118 CV |
31606 | This parameter can be omitted if the call was successful. |
31607 | ||
fc320d37 SL |
31608 | @var{Ctrl-C flag} is only sent if the user requested a break. In this |
31609 | case, @var{errno} must be sent as well, even if the call was successful. | |
31610 | The @var{Ctrl-C flag} itself consists of the character @samp{C}: | |
0ce1b118 CV |
31611 | |
31612 | @smallexample | |
31613 | F0,0,C | |
31614 | @end smallexample | |
31615 | ||
31616 | @noindent | |
fc320d37 | 31617 | or, if the call was interrupted before the host call has been performed: |
0ce1b118 CV |
31618 | |
31619 | @smallexample | |
31620 | F-1,4,C | |
31621 | @end smallexample | |
31622 | ||
31623 | @noindent | |
db2e3e2e | 31624 | assuming 4 is the protocol-specific representation of @code{EINTR}. |
0ce1b118 CV |
31625 | |
31626 | @end table | |
31627 | ||
0ce1b118 | 31628 | |
79a6e687 BW |
31629 | @node The Ctrl-C Message |
31630 | @subsection The @samp{Ctrl-C} Message | |
0ce1b118 CV |
31631 | @cindex ctrl-c message, in file-i/o protocol |
31632 | ||
c8aa23ab | 31633 | If the @samp{Ctrl-C} flag is set in the @value{GDBN} |
79a6e687 | 31634 | reply packet (@pxref{The F Reply Packet}), |
fc320d37 | 31635 | the target should behave as if it had |
0ce1b118 | 31636 | gotten a break message. The meaning for the target is ``system call |
fc320d37 | 31637 | interrupted by @code{SIGINT}''. Consequentially, the target should actually stop |
0ce1b118 | 31638 | (as with a break message) and return to @value{GDBN} with a @code{T02} |
c8aa23ab | 31639 | packet. |
fc320d37 SL |
31640 | |
31641 | It's important for the target to know in which | |
31642 | state the system call was interrupted. There are two possible cases: | |
0ce1b118 CV |
31643 | |
31644 | @itemize @bullet | |
31645 | @item | |
31646 | The system call hasn't been performed on the host yet. | |
31647 | ||
31648 | @item | |
31649 | The system call on the host has been finished. | |
31650 | ||
31651 | @end itemize | |
31652 | ||
31653 | These two states can be distinguished by the target by the value of the | |
31654 | returned @code{errno}. If it's the protocol representation of @code{EINTR}, the system | |
31655 | call hasn't been performed. This is equivalent to the @code{EINTR} handling | |
31656 | on POSIX systems. In any other case, the target may presume that the | |
fc320d37 | 31657 | system call has been finished --- successfully or not --- and should behave |
0ce1b118 CV |
31658 | as if the break message arrived right after the system call. |
31659 | ||
fc320d37 | 31660 | @value{GDBN} must behave reliably. If the system call has not been called |
0ce1b118 CV |
31661 | yet, @value{GDBN} may send the @code{F} reply immediately, setting @code{EINTR} as |
31662 | @code{errno} in the packet. If the system call on the host has been finished | |
fc320d37 SL |
31663 | before the user requests a break, the full action must be finished by |
31664 | @value{GDBN}. This requires sending @code{M} or @code{X} packets as necessary. | |
31665 | The @code{F} packet may only be sent when either nothing has happened | |
0ce1b118 CV |
31666 | or the full action has been completed. |
31667 | ||
31668 | @node Console I/O | |
31669 | @subsection Console I/O | |
31670 | @cindex console i/o as part of file-i/o | |
31671 | ||
d3e8051b | 31672 | By default and if not explicitly closed by the target system, the file |
0ce1b118 CV |
31673 | descriptors 0, 1 and 2 are connected to the @value{GDBN} console. Output |
31674 | on the @value{GDBN} console is handled as any other file output operation | |
31675 | (@code{write(1, @dots{})} or @code{write(2, @dots{})}). Console input is handled | |
31676 | by @value{GDBN} so that after the target read request from file descriptor | |
31677 | 0 all following typing is buffered until either one of the following | |
31678 | conditions is met: | |
31679 | ||
31680 | @itemize @bullet | |
31681 | @item | |
c8aa23ab | 31682 | The user types @kbd{Ctrl-c}. The behaviour is as explained above, and the |
0ce1b118 CV |
31683 | @code{read} |
31684 | system call is treated as finished. | |
31685 | ||
31686 | @item | |
7f9087cb | 31687 | The user presses @key{RET}. This is treated as end of input with a trailing |
fc320d37 | 31688 | newline. |
0ce1b118 CV |
31689 | |
31690 | @item | |
c8aa23ab EZ |
31691 | The user types @kbd{Ctrl-d}. This is treated as end of input. No trailing |
31692 | character (neither newline nor @samp{Ctrl-D}) is appended to the input. | |
0ce1b118 CV |
31693 | |
31694 | @end itemize | |
31695 | ||
fc320d37 SL |
31696 | If the user has typed more characters than fit in the buffer given to |
31697 | the @code{read} call, the trailing characters are buffered in @value{GDBN} until | |
31698 | either another @code{read(0, @dots{})} is requested by the target, or debugging | |
31699 | is stopped at the user's request. | |
0ce1b118 | 31700 | |
0ce1b118 | 31701 | |
79a6e687 BW |
31702 | @node List of Supported Calls |
31703 | @subsection List of Supported Calls | |
0ce1b118 CV |
31704 | @cindex list of supported file-i/o calls |
31705 | ||
31706 | @menu | |
31707 | * open:: | |
31708 | * close:: | |
31709 | * read:: | |
31710 | * write:: | |
31711 | * lseek:: | |
31712 | * rename:: | |
31713 | * unlink:: | |
31714 | * stat/fstat:: | |
31715 | * gettimeofday:: | |
31716 | * isatty:: | |
31717 | * system:: | |
31718 | @end menu | |
31719 | ||
31720 | @node open | |
31721 | @unnumberedsubsubsec open | |
31722 | @cindex open, file-i/o system call | |
31723 | ||
fc320d37 SL |
31724 | @table @asis |
31725 | @item Synopsis: | |
0ce1b118 | 31726 | @smallexample |
0ce1b118 CV |
31727 | int open(const char *pathname, int flags); |
31728 | int open(const char *pathname, int flags, mode_t mode); | |
0ce1b118 CV |
31729 | @end smallexample |
31730 | ||
fc320d37 SL |
31731 | @item Request: |
31732 | @samp{Fopen,@var{pathptr}/@var{len},@var{flags},@var{mode}} | |
31733 | ||
0ce1b118 | 31734 | @noindent |
fc320d37 | 31735 | @var{flags} is the bitwise @code{OR} of the following values: |
0ce1b118 CV |
31736 | |
31737 | @table @code | |
b383017d | 31738 | @item O_CREAT |
0ce1b118 CV |
31739 | If the file does not exist it will be created. The host |
31740 | rules apply as far as file ownership and time stamps | |
31741 | are concerned. | |
31742 | ||
b383017d | 31743 | @item O_EXCL |
fc320d37 | 31744 | When used with @code{O_CREAT}, if the file already exists it is |
0ce1b118 CV |
31745 | an error and open() fails. |
31746 | ||
b383017d | 31747 | @item O_TRUNC |
0ce1b118 | 31748 | If the file already exists and the open mode allows |
fc320d37 SL |
31749 | writing (@code{O_RDWR} or @code{O_WRONLY} is given) it will be |
31750 | truncated to zero length. | |
0ce1b118 | 31751 | |
b383017d | 31752 | @item O_APPEND |
0ce1b118 CV |
31753 | The file is opened in append mode. |
31754 | ||
b383017d | 31755 | @item O_RDONLY |
0ce1b118 CV |
31756 | The file is opened for reading only. |
31757 | ||
b383017d | 31758 | @item O_WRONLY |
0ce1b118 CV |
31759 | The file is opened for writing only. |
31760 | ||
b383017d | 31761 | @item O_RDWR |
0ce1b118 | 31762 | The file is opened for reading and writing. |
fc320d37 | 31763 | @end table |
0ce1b118 CV |
31764 | |
31765 | @noindent | |
fc320d37 | 31766 | Other bits are silently ignored. |
0ce1b118 | 31767 | |
0ce1b118 CV |
31768 | |
31769 | @noindent | |
fc320d37 | 31770 | @var{mode} is the bitwise @code{OR} of the following values: |
0ce1b118 CV |
31771 | |
31772 | @table @code | |
b383017d | 31773 | @item S_IRUSR |
0ce1b118 CV |
31774 | User has read permission. |
31775 | ||
b383017d | 31776 | @item S_IWUSR |
0ce1b118 CV |
31777 | User has write permission. |
31778 | ||
b383017d | 31779 | @item S_IRGRP |
0ce1b118 CV |
31780 | Group has read permission. |
31781 | ||
b383017d | 31782 | @item S_IWGRP |
0ce1b118 CV |
31783 | Group has write permission. |
31784 | ||
b383017d | 31785 | @item S_IROTH |
0ce1b118 CV |
31786 | Others have read permission. |
31787 | ||
b383017d | 31788 | @item S_IWOTH |
0ce1b118 | 31789 | Others have write permission. |
fc320d37 | 31790 | @end table |
0ce1b118 CV |
31791 | |
31792 | @noindent | |
fc320d37 | 31793 | Other bits are silently ignored. |
0ce1b118 | 31794 | |
0ce1b118 | 31795 | |
fc320d37 SL |
31796 | @item Return value: |
31797 | @code{open} returns the new file descriptor or -1 if an error | |
31798 | occurred. | |
0ce1b118 | 31799 | |
fc320d37 | 31800 | @item Errors: |
0ce1b118 CV |
31801 | |
31802 | @table @code | |
b383017d | 31803 | @item EEXIST |
fc320d37 | 31804 | @var{pathname} already exists and @code{O_CREAT} and @code{O_EXCL} were used. |
0ce1b118 | 31805 | |
b383017d | 31806 | @item EISDIR |
fc320d37 | 31807 | @var{pathname} refers to a directory. |
0ce1b118 | 31808 | |
b383017d | 31809 | @item EACCES |
0ce1b118 CV |
31810 | The requested access is not allowed. |
31811 | ||
31812 | @item ENAMETOOLONG | |
fc320d37 | 31813 | @var{pathname} was too long. |
0ce1b118 | 31814 | |
b383017d | 31815 | @item ENOENT |
fc320d37 | 31816 | A directory component in @var{pathname} does not exist. |
0ce1b118 | 31817 | |
b383017d | 31818 | @item ENODEV |
fc320d37 | 31819 | @var{pathname} refers to a device, pipe, named pipe or socket. |
0ce1b118 | 31820 | |
b383017d | 31821 | @item EROFS |
fc320d37 | 31822 | @var{pathname} refers to a file on a read-only filesystem and |
0ce1b118 CV |
31823 | write access was requested. |
31824 | ||
b383017d | 31825 | @item EFAULT |
fc320d37 | 31826 | @var{pathname} is an invalid pointer value. |
0ce1b118 | 31827 | |
b383017d | 31828 | @item ENOSPC |
0ce1b118 CV |
31829 | No space on device to create the file. |
31830 | ||
b383017d | 31831 | @item EMFILE |
0ce1b118 CV |
31832 | The process already has the maximum number of files open. |
31833 | ||
b383017d | 31834 | @item ENFILE |
0ce1b118 CV |
31835 | The limit on the total number of files open on the system |
31836 | has been reached. | |
31837 | ||
b383017d | 31838 | @item EINTR |
0ce1b118 CV |
31839 | The call was interrupted by the user. |
31840 | @end table | |
31841 | ||
fc320d37 SL |
31842 | @end table |
31843 | ||
0ce1b118 CV |
31844 | @node close |
31845 | @unnumberedsubsubsec close | |
31846 | @cindex close, file-i/o system call | |
31847 | ||
fc320d37 SL |
31848 | @table @asis |
31849 | @item Synopsis: | |
0ce1b118 | 31850 | @smallexample |
0ce1b118 | 31851 | int close(int fd); |
fc320d37 | 31852 | @end smallexample |
0ce1b118 | 31853 | |
fc320d37 SL |
31854 | @item Request: |
31855 | @samp{Fclose,@var{fd}} | |
0ce1b118 | 31856 | |
fc320d37 SL |
31857 | @item Return value: |
31858 | @code{close} returns zero on success, or -1 if an error occurred. | |
0ce1b118 | 31859 | |
fc320d37 | 31860 | @item Errors: |
0ce1b118 CV |
31861 | |
31862 | @table @code | |
b383017d | 31863 | @item EBADF |
fc320d37 | 31864 | @var{fd} isn't a valid open file descriptor. |
0ce1b118 | 31865 | |
b383017d | 31866 | @item EINTR |
0ce1b118 CV |
31867 | The call was interrupted by the user. |
31868 | @end table | |
31869 | ||
fc320d37 SL |
31870 | @end table |
31871 | ||
0ce1b118 CV |
31872 | @node read |
31873 | @unnumberedsubsubsec read | |
31874 | @cindex read, file-i/o system call | |
31875 | ||
fc320d37 SL |
31876 | @table @asis |
31877 | @item Synopsis: | |
0ce1b118 | 31878 | @smallexample |
0ce1b118 | 31879 | int read(int fd, void *buf, unsigned int count); |
fc320d37 | 31880 | @end smallexample |
0ce1b118 | 31881 | |
fc320d37 SL |
31882 | @item Request: |
31883 | @samp{Fread,@var{fd},@var{bufptr},@var{count}} | |
0ce1b118 | 31884 | |
fc320d37 | 31885 | @item Return value: |
0ce1b118 CV |
31886 | On success, the number of bytes read is returned. |
31887 | Zero indicates end of file. If count is zero, read | |
b383017d | 31888 | returns zero as well. On error, -1 is returned. |
0ce1b118 | 31889 | |
fc320d37 | 31890 | @item Errors: |
0ce1b118 CV |
31891 | |
31892 | @table @code | |
b383017d | 31893 | @item EBADF |
fc320d37 | 31894 | @var{fd} is not a valid file descriptor or is not open for |
0ce1b118 CV |
31895 | reading. |
31896 | ||
b383017d | 31897 | @item EFAULT |
fc320d37 | 31898 | @var{bufptr} is an invalid pointer value. |
0ce1b118 | 31899 | |
b383017d | 31900 | @item EINTR |
0ce1b118 CV |
31901 | The call was interrupted by the user. |
31902 | @end table | |
31903 | ||
fc320d37 SL |
31904 | @end table |
31905 | ||
0ce1b118 CV |
31906 | @node write |
31907 | @unnumberedsubsubsec write | |
31908 | @cindex write, file-i/o system call | |
31909 | ||
fc320d37 SL |
31910 | @table @asis |
31911 | @item Synopsis: | |
0ce1b118 | 31912 | @smallexample |
0ce1b118 | 31913 | int write(int fd, const void *buf, unsigned int count); |
fc320d37 | 31914 | @end smallexample |
0ce1b118 | 31915 | |
fc320d37 SL |
31916 | @item Request: |
31917 | @samp{Fwrite,@var{fd},@var{bufptr},@var{count}} | |
0ce1b118 | 31918 | |
fc320d37 | 31919 | @item Return value: |
0ce1b118 CV |
31920 | On success, the number of bytes written are returned. |
31921 | Zero indicates nothing was written. On error, -1 | |
31922 | is returned. | |
31923 | ||
fc320d37 | 31924 | @item Errors: |
0ce1b118 CV |
31925 | |
31926 | @table @code | |
b383017d | 31927 | @item EBADF |
fc320d37 | 31928 | @var{fd} is not a valid file descriptor or is not open for |
0ce1b118 CV |
31929 | writing. |
31930 | ||
b383017d | 31931 | @item EFAULT |
fc320d37 | 31932 | @var{bufptr} is an invalid pointer value. |
0ce1b118 | 31933 | |
b383017d | 31934 | @item EFBIG |
0ce1b118 | 31935 | An attempt was made to write a file that exceeds the |
db2e3e2e | 31936 | host-specific maximum file size allowed. |
0ce1b118 | 31937 | |
b383017d | 31938 | @item ENOSPC |
0ce1b118 CV |
31939 | No space on device to write the data. |
31940 | ||
b383017d | 31941 | @item EINTR |
0ce1b118 CV |
31942 | The call was interrupted by the user. |
31943 | @end table | |
31944 | ||
fc320d37 SL |
31945 | @end table |
31946 | ||
0ce1b118 CV |
31947 | @node lseek |
31948 | @unnumberedsubsubsec lseek | |
31949 | @cindex lseek, file-i/o system call | |
31950 | ||
fc320d37 SL |
31951 | @table @asis |
31952 | @item Synopsis: | |
0ce1b118 | 31953 | @smallexample |
0ce1b118 | 31954 | long lseek (int fd, long offset, int flag); |
0ce1b118 CV |
31955 | @end smallexample |
31956 | ||
fc320d37 SL |
31957 | @item Request: |
31958 | @samp{Flseek,@var{fd},@var{offset},@var{flag}} | |
31959 | ||
31960 | @var{flag} is one of: | |
0ce1b118 CV |
31961 | |
31962 | @table @code | |
b383017d | 31963 | @item SEEK_SET |
fc320d37 | 31964 | The offset is set to @var{offset} bytes. |
0ce1b118 | 31965 | |
b383017d | 31966 | @item SEEK_CUR |
fc320d37 | 31967 | The offset is set to its current location plus @var{offset} |
0ce1b118 CV |
31968 | bytes. |
31969 | ||
b383017d | 31970 | @item SEEK_END |
fc320d37 | 31971 | The offset is set to the size of the file plus @var{offset} |
0ce1b118 CV |
31972 | bytes. |
31973 | @end table | |
31974 | ||
fc320d37 | 31975 | @item Return value: |
0ce1b118 CV |
31976 | On success, the resulting unsigned offset in bytes from |
31977 | the beginning of the file is returned. Otherwise, a | |
31978 | value of -1 is returned. | |
31979 | ||
fc320d37 | 31980 | @item Errors: |
0ce1b118 CV |
31981 | |
31982 | @table @code | |
b383017d | 31983 | @item EBADF |
fc320d37 | 31984 | @var{fd} is not a valid open file descriptor. |
0ce1b118 | 31985 | |
b383017d | 31986 | @item ESPIPE |
fc320d37 | 31987 | @var{fd} is associated with the @value{GDBN} console. |
0ce1b118 | 31988 | |
b383017d | 31989 | @item EINVAL |
fc320d37 | 31990 | @var{flag} is not a proper value. |
0ce1b118 | 31991 | |
b383017d | 31992 | @item EINTR |
0ce1b118 CV |
31993 | The call was interrupted by the user. |
31994 | @end table | |
31995 | ||
fc320d37 SL |
31996 | @end table |
31997 | ||
0ce1b118 CV |
31998 | @node rename |
31999 | @unnumberedsubsubsec rename | |
32000 | @cindex rename, file-i/o system call | |
32001 | ||
fc320d37 SL |
32002 | @table @asis |
32003 | @item Synopsis: | |
0ce1b118 | 32004 | @smallexample |
0ce1b118 | 32005 | int rename(const char *oldpath, const char *newpath); |
fc320d37 | 32006 | @end smallexample |
0ce1b118 | 32007 | |
fc320d37 SL |
32008 | @item Request: |
32009 | @samp{Frename,@var{oldpathptr}/@var{len},@var{newpathptr}/@var{len}} | |
0ce1b118 | 32010 | |
fc320d37 | 32011 | @item Return value: |
0ce1b118 CV |
32012 | On success, zero is returned. On error, -1 is returned. |
32013 | ||
fc320d37 | 32014 | @item Errors: |
0ce1b118 CV |
32015 | |
32016 | @table @code | |
b383017d | 32017 | @item EISDIR |
fc320d37 | 32018 | @var{newpath} is an existing directory, but @var{oldpath} is not a |
0ce1b118 CV |
32019 | directory. |
32020 | ||
b383017d | 32021 | @item EEXIST |
fc320d37 | 32022 | @var{newpath} is a non-empty directory. |
0ce1b118 | 32023 | |
b383017d | 32024 | @item EBUSY |
fc320d37 | 32025 | @var{oldpath} or @var{newpath} is a directory that is in use by some |
0ce1b118 CV |
32026 | process. |
32027 | ||
b383017d | 32028 | @item EINVAL |
0ce1b118 CV |
32029 | An attempt was made to make a directory a subdirectory |
32030 | of itself. | |
32031 | ||
b383017d | 32032 | @item ENOTDIR |
fc320d37 SL |
32033 | A component used as a directory in @var{oldpath} or new |
32034 | path is not a directory. Or @var{oldpath} is a directory | |
32035 | and @var{newpath} exists but is not a directory. | |
0ce1b118 | 32036 | |
b383017d | 32037 | @item EFAULT |
fc320d37 | 32038 | @var{oldpathptr} or @var{newpathptr} are invalid pointer values. |
0ce1b118 | 32039 | |
b383017d | 32040 | @item EACCES |
0ce1b118 CV |
32041 | No access to the file or the path of the file. |
32042 | ||
32043 | @item ENAMETOOLONG | |
b383017d | 32044 | |
fc320d37 | 32045 | @var{oldpath} or @var{newpath} was too long. |
0ce1b118 | 32046 | |
b383017d | 32047 | @item ENOENT |
fc320d37 | 32048 | A directory component in @var{oldpath} or @var{newpath} does not exist. |
0ce1b118 | 32049 | |
b383017d | 32050 | @item EROFS |
0ce1b118 CV |
32051 | The file is on a read-only filesystem. |
32052 | ||
b383017d | 32053 | @item ENOSPC |
0ce1b118 CV |
32054 | The device containing the file has no room for the new |
32055 | directory entry. | |
32056 | ||
b383017d | 32057 | @item EINTR |
0ce1b118 CV |
32058 | The call was interrupted by the user. |
32059 | @end table | |
32060 | ||
fc320d37 SL |
32061 | @end table |
32062 | ||
0ce1b118 CV |
32063 | @node unlink |
32064 | @unnumberedsubsubsec unlink | |
32065 | @cindex unlink, file-i/o system call | |
32066 | ||
fc320d37 SL |
32067 | @table @asis |
32068 | @item Synopsis: | |
0ce1b118 | 32069 | @smallexample |
0ce1b118 | 32070 | int unlink(const char *pathname); |
fc320d37 | 32071 | @end smallexample |
0ce1b118 | 32072 | |
fc320d37 SL |
32073 | @item Request: |
32074 | @samp{Funlink,@var{pathnameptr}/@var{len}} | |
0ce1b118 | 32075 | |
fc320d37 | 32076 | @item Return value: |
0ce1b118 CV |
32077 | On success, zero is returned. On error, -1 is returned. |
32078 | ||
fc320d37 | 32079 | @item Errors: |
0ce1b118 CV |
32080 | |
32081 | @table @code | |
b383017d | 32082 | @item EACCES |
0ce1b118 CV |
32083 | No access to the file or the path of the file. |
32084 | ||
b383017d | 32085 | @item EPERM |
0ce1b118 CV |
32086 | The system does not allow unlinking of directories. |
32087 | ||
b383017d | 32088 | @item EBUSY |
fc320d37 | 32089 | The file @var{pathname} cannot be unlinked because it's |
0ce1b118 CV |
32090 | being used by another process. |
32091 | ||
b383017d | 32092 | @item EFAULT |
fc320d37 | 32093 | @var{pathnameptr} is an invalid pointer value. |
0ce1b118 CV |
32094 | |
32095 | @item ENAMETOOLONG | |
fc320d37 | 32096 | @var{pathname} was too long. |
0ce1b118 | 32097 | |
b383017d | 32098 | @item ENOENT |
fc320d37 | 32099 | A directory component in @var{pathname} does not exist. |
0ce1b118 | 32100 | |
b383017d | 32101 | @item ENOTDIR |
0ce1b118 CV |
32102 | A component of the path is not a directory. |
32103 | ||
b383017d | 32104 | @item EROFS |
0ce1b118 CV |
32105 | The file is on a read-only filesystem. |
32106 | ||
b383017d | 32107 | @item EINTR |
0ce1b118 CV |
32108 | The call was interrupted by the user. |
32109 | @end table | |
32110 | ||
fc320d37 SL |
32111 | @end table |
32112 | ||
0ce1b118 CV |
32113 | @node stat/fstat |
32114 | @unnumberedsubsubsec stat/fstat | |
32115 | @cindex fstat, file-i/o system call | |
32116 | @cindex stat, file-i/o system call | |
32117 | ||
fc320d37 SL |
32118 | @table @asis |
32119 | @item Synopsis: | |
0ce1b118 | 32120 | @smallexample |
0ce1b118 CV |
32121 | int stat(const char *pathname, struct stat *buf); |
32122 | int fstat(int fd, struct stat *buf); | |
fc320d37 | 32123 | @end smallexample |
0ce1b118 | 32124 | |
fc320d37 SL |
32125 | @item Request: |
32126 | @samp{Fstat,@var{pathnameptr}/@var{len},@var{bufptr}}@* | |
32127 | @samp{Ffstat,@var{fd},@var{bufptr}} | |
0ce1b118 | 32128 | |
fc320d37 | 32129 | @item Return value: |
0ce1b118 CV |
32130 | On success, zero is returned. On error, -1 is returned. |
32131 | ||
fc320d37 | 32132 | @item Errors: |
0ce1b118 CV |
32133 | |
32134 | @table @code | |
b383017d | 32135 | @item EBADF |
fc320d37 | 32136 | @var{fd} is not a valid open file. |
0ce1b118 | 32137 | |
b383017d | 32138 | @item ENOENT |
fc320d37 | 32139 | A directory component in @var{pathname} does not exist or the |
0ce1b118 CV |
32140 | path is an empty string. |
32141 | ||
b383017d | 32142 | @item ENOTDIR |
0ce1b118 CV |
32143 | A component of the path is not a directory. |
32144 | ||
b383017d | 32145 | @item EFAULT |
fc320d37 | 32146 | @var{pathnameptr} is an invalid pointer value. |
0ce1b118 | 32147 | |
b383017d | 32148 | @item EACCES |
0ce1b118 CV |
32149 | No access to the file or the path of the file. |
32150 | ||
32151 | @item ENAMETOOLONG | |
fc320d37 | 32152 | @var{pathname} was too long. |
0ce1b118 | 32153 | |
b383017d | 32154 | @item EINTR |
0ce1b118 CV |
32155 | The call was interrupted by the user. |
32156 | @end table | |
32157 | ||
fc320d37 SL |
32158 | @end table |
32159 | ||
0ce1b118 CV |
32160 | @node gettimeofday |
32161 | @unnumberedsubsubsec gettimeofday | |
32162 | @cindex gettimeofday, file-i/o system call | |
32163 | ||
fc320d37 SL |
32164 | @table @asis |
32165 | @item Synopsis: | |
0ce1b118 | 32166 | @smallexample |
0ce1b118 | 32167 | int gettimeofday(struct timeval *tv, void *tz); |
fc320d37 | 32168 | @end smallexample |
0ce1b118 | 32169 | |
fc320d37 SL |
32170 | @item Request: |
32171 | @samp{Fgettimeofday,@var{tvptr},@var{tzptr}} | |
0ce1b118 | 32172 | |
fc320d37 | 32173 | @item Return value: |
0ce1b118 CV |
32174 | On success, 0 is returned, -1 otherwise. |
32175 | ||
fc320d37 | 32176 | @item Errors: |
0ce1b118 CV |
32177 | |
32178 | @table @code | |
b383017d | 32179 | @item EINVAL |
fc320d37 | 32180 | @var{tz} is a non-NULL pointer. |
0ce1b118 | 32181 | |
b383017d | 32182 | @item EFAULT |
fc320d37 SL |
32183 | @var{tvptr} and/or @var{tzptr} is an invalid pointer value. |
32184 | @end table | |
32185 | ||
0ce1b118 CV |
32186 | @end table |
32187 | ||
32188 | @node isatty | |
32189 | @unnumberedsubsubsec isatty | |
32190 | @cindex isatty, file-i/o system call | |
32191 | ||
fc320d37 SL |
32192 | @table @asis |
32193 | @item Synopsis: | |
0ce1b118 | 32194 | @smallexample |
0ce1b118 | 32195 | int isatty(int fd); |
fc320d37 | 32196 | @end smallexample |
0ce1b118 | 32197 | |
fc320d37 SL |
32198 | @item Request: |
32199 | @samp{Fisatty,@var{fd}} | |
0ce1b118 | 32200 | |
fc320d37 SL |
32201 | @item Return value: |
32202 | Returns 1 if @var{fd} refers to the @value{GDBN} console, 0 otherwise. | |
0ce1b118 | 32203 | |
fc320d37 | 32204 | @item Errors: |
0ce1b118 CV |
32205 | |
32206 | @table @code | |
b383017d | 32207 | @item EINTR |
0ce1b118 CV |
32208 | The call was interrupted by the user. |
32209 | @end table | |
32210 | ||
fc320d37 SL |
32211 | @end table |
32212 | ||
32213 | Note that the @code{isatty} call is treated as a special case: it returns | |
32214 | 1 to the target if the file descriptor is attached | |
32215 | to the @value{GDBN} console, 0 otherwise. Implementing through system calls | |
32216 | would require implementing @code{ioctl} and would be more complex than | |
32217 | needed. | |
32218 | ||
32219 | ||
0ce1b118 CV |
32220 | @node system |
32221 | @unnumberedsubsubsec system | |
32222 | @cindex system, file-i/o system call | |
32223 | ||
fc320d37 SL |
32224 | @table @asis |
32225 | @item Synopsis: | |
0ce1b118 | 32226 | @smallexample |
0ce1b118 | 32227 | int system(const char *command); |
fc320d37 | 32228 | @end smallexample |
0ce1b118 | 32229 | |
fc320d37 SL |
32230 | @item Request: |
32231 | @samp{Fsystem,@var{commandptr}/@var{len}} | |
0ce1b118 | 32232 | |
fc320d37 | 32233 | @item Return value: |
5600ea19 NS |
32234 | If @var{len} is zero, the return value indicates whether a shell is |
32235 | available. A zero return value indicates a shell is not available. | |
32236 | For non-zero @var{len}, the value returned is -1 on error and the | |
32237 | return status of the command otherwise. Only the exit status of the | |
32238 | command is returned, which is extracted from the host's @code{system} | |
32239 | return value by calling @code{WEXITSTATUS(retval)}. In case | |
32240 | @file{/bin/sh} could not be executed, 127 is returned. | |
0ce1b118 | 32241 | |
fc320d37 | 32242 | @item Errors: |
0ce1b118 CV |
32243 | |
32244 | @table @code | |
b383017d | 32245 | @item EINTR |
0ce1b118 CV |
32246 | The call was interrupted by the user. |
32247 | @end table | |
32248 | ||
fc320d37 SL |
32249 | @end table |
32250 | ||
32251 | @value{GDBN} takes over the full task of calling the necessary host calls | |
32252 | to perform the @code{system} call. The return value of @code{system} on | |
32253 | the host is simplified before it's returned | |
32254 | to the target. Any termination signal information from the child process | |
32255 | is discarded, and the return value consists | |
32256 | entirely of the exit status of the called command. | |
32257 | ||
32258 | Due to security concerns, the @code{system} call is by default refused | |
32259 | by @value{GDBN}. The user has to allow this call explicitly with the | |
32260 | @code{set remote system-call-allowed 1} command. | |
32261 | ||
32262 | @table @code | |
32263 | @item set remote system-call-allowed | |
32264 | @kindex set remote system-call-allowed | |
32265 | Control whether to allow the @code{system} calls in the File I/O | |
32266 | protocol for the remote target. The default is zero (disabled). | |
32267 | ||
32268 | @item show remote system-call-allowed | |
32269 | @kindex show remote system-call-allowed | |
32270 | Show whether the @code{system} calls are allowed in the File I/O | |
32271 | protocol. | |
32272 | @end table | |
32273 | ||
db2e3e2e BW |
32274 | @node Protocol-specific Representation of Datatypes |
32275 | @subsection Protocol-specific Representation of Datatypes | |
32276 | @cindex protocol-specific representation of datatypes, in file-i/o protocol | |
0ce1b118 CV |
32277 | |
32278 | @menu | |
79a6e687 BW |
32279 | * Integral Datatypes:: |
32280 | * Pointer Values:: | |
32281 | * Memory Transfer:: | |
0ce1b118 CV |
32282 | * struct stat:: |
32283 | * struct timeval:: | |
32284 | @end menu | |
32285 | ||
79a6e687 BW |
32286 | @node Integral Datatypes |
32287 | @unnumberedsubsubsec Integral Datatypes | |
0ce1b118 CV |
32288 | @cindex integral datatypes, in file-i/o protocol |
32289 | ||
fc320d37 SL |
32290 | The integral datatypes used in the system calls are @code{int}, |
32291 | @code{unsigned int}, @code{long}, @code{unsigned long}, | |
32292 | @code{mode_t}, and @code{time_t}. | |
0ce1b118 | 32293 | |
fc320d37 | 32294 | @code{int}, @code{unsigned int}, @code{mode_t} and @code{time_t} are |
0ce1b118 CV |
32295 | implemented as 32 bit values in this protocol. |
32296 | ||
fc320d37 | 32297 | @code{long} and @code{unsigned long} are implemented as 64 bit types. |
b383017d | 32298 | |
0ce1b118 CV |
32299 | @xref{Limits}, for corresponding MIN and MAX values (similar to those |
32300 | in @file{limits.h}) to allow range checking on host and target. | |
32301 | ||
32302 | @code{time_t} datatypes are defined as seconds since the Epoch. | |
32303 | ||
32304 | All integral datatypes transferred as part of a memory read or write of a | |
32305 | structured datatype e.g.@: a @code{struct stat} have to be given in big endian | |
32306 | byte order. | |
32307 | ||
79a6e687 BW |
32308 | @node Pointer Values |
32309 | @unnumberedsubsubsec Pointer Values | |
0ce1b118 CV |
32310 | @cindex pointer values, in file-i/o protocol |
32311 | ||
32312 | Pointers to target data are transmitted as they are. An exception | |
32313 | is made for pointers to buffers for which the length isn't | |
32314 | transmitted as part of the function call, namely strings. Strings | |
32315 | are transmitted as a pointer/length pair, both as hex values, e.g.@: | |
32316 | ||
32317 | @smallexample | |
32318 | @code{1aaf/12} | |
32319 | @end smallexample | |
32320 | ||
32321 | @noindent | |
32322 | which is a pointer to data of length 18 bytes at position 0x1aaf. | |
32323 | The length is defined as the full string length in bytes, including | |
fc320d37 SL |
32324 | the trailing null byte. For example, the string @code{"hello world"} |
32325 | at address 0x123456 is transmitted as | |
0ce1b118 CV |
32326 | |
32327 | @smallexample | |
fc320d37 | 32328 | @code{123456/d} |
0ce1b118 CV |
32329 | @end smallexample |
32330 | ||
79a6e687 BW |
32331 | @node Memory Transfer |
32332 | @unnumberedsubsubsec Memory Transfer | |
fc320d37 SL |
32333 | @cindex memory transfer, in file-i/o protocol |
32334 | ||
32335 | Structured data which is transferred using a memory read or write (for | |
db2e3e2e | 32336 | example, a @code{struct stat}) is expected to be in a protocol-specific format |
fc320d37 SL |
32337 | with all scalar multibyte datatypes being big endian. Translation to |
32338 | this representation needs to be done both by the target before the @code{F} | |
32339 | packet is sent, and by @value{GDBN} before | |
32340 | it transfers memory to the target. Transferred pointers to structured | |
32341 | data should point to the already-coerced data at any time. | |
0ce1b118 | 32342 | |
0ce1b118 CV |
32343 | |
32344 | @node struct stat | |
32345 | @unnumberedsubsubsec struct stat | |
32346 | @cindex struct stat, in file-i/o protocol | |
32347 | ||
fc320d37 SL |
32348 | The buffer of type @code{struct stat} used by the target and @value{GDBN} |
32349 | is defined as follows: | |
0ce1b118 CV |
32350 | |
32351 | @smallexample | |
32352 | struct stat @{ | |
32353 | unsigned int st_dev; /* device */ | |
32354 | unsigned int st_ino; /* inode */ | |
32355 | mode_t st_mode; /* protection */ | |
32356 | unsigned int st_nlink; /* number of hard links */ | |
32357 | unsigned int st_uid; /* user ID of owner */ | |
32358 | unsigned int st_gid; /* group ID of owner */ | |
32359 | unsigned int st_rdev; /* device type (if inode device) */ | |
32360 | unsigned long st_size; /* total size, in bytes */ | |
32361 | unsigned long st_blksize; /* blocksize for filesystem I/O */ | |
32362 | unsigned long st_blocks; /* number of blocks allocated */ | |
32363 | time_t st_atime; /* time of last access */ | |
32364 | time_t st_mtime; /* time of last modification */ | |
32365 | time_t st_ctime; /* time of last change */ | |
32366 | @}; | |
32367 | @end smallexample | |
32368 | ||
fc320d37 | 32369 | The integral datatypes conform to the definitions given in the |
79a6e687 | 32370 | appropriate section (see @ref{Integral Datatypes}, for details) so this |
0ce1b118 CV |
32371 | structure is of size 64 bytes. |
32372 | ||
32373 | The values of several fields have a restricted meaning and/or | |
32374 | range of values. | |
32375 | ||
fc320d37 | 32376 | @table @code |
0ce1b118 | 32377 | |
fc320d37 SL |
32378 | @item st_dev |
32379 | A value of 0 represents a file, 1 the console. | |
0ce1b118 | 32380 | |
fc320d37 SL |
32381 | @item st_ino |
32382 | No valid meaning for the target. Transmitted unchanged. | |
0ce1b118 | 32383 | |
fc320d37 SL |
32384 | @item st_mode |
32385 | Valid mode bits are described in @ref{Constants}. Any other | |
32386 | bits have currently no meaning for the target. | |
0ce1b118 | 32387 | |
fc320d37 SL |
32388 | @item st_uid |
32389 | @itemx st_gid | |
32390 | @itemx st_rdev | |
32391 | No valid meaning for the target. Transmitted unchanged. | |
0ce1b118 | 32392 | |
fc320d37 SL |
32393 | @item st_atime |
32394 | @itemx st_mtime | |
32395 | @itemx st_ctime | |
32396 | These values have a host and file system dependent | |
32397 | accuracy. Especially on Windows hosts, the file system may not | |
32398 | support exact timing values. | |
32399 | @end table | |
0ce1b118 | 32400 | |
fc320d37 SL |
32401 | The target gets a @code{struct stat} of the above representation and is |
32402 | responsible for coercing it to the target representation before | |
0ce1b118 CV |
32403 | continuing. |
32404 | ||
fc320d37 SL |
32405 | Note that due to size differences between the host, target, and protocol |
32406 | representations of @code{struct stat} members, these members could eventually | |
0ce1b118 CV |
32407 | get truncated on the target. |
32408 | ||
32409 | @node struct timeval | |
32410 | @unnumberedsubsubsec struct timeval | |
32411 | @cindex struct timeval, in file-i/o protocol | |
32412 | ||
fc320d37 | 32413 | The buffer of type @code{struct timeval} used by the File-I/O protocol |
0ce1b118 CV |
32414 | is defined as follows: |
32415 | ||
32416 | @smallexample | |
b383017d | 32417 | struct timeval @{ |
0ce1b118 CV |
32418 | time_t tv_sec; /* second */ |
32419 | long tv_usec; /* microsecond */ | |
32420 | @}; | |
32421 | @end smallexample | |
32422 | ||
fc320d37 | 32423 | The integral datatypes conform to the definitions given in the |
79a6e687 | 32424 | appropriate section (see @ref{Integral Datatypes}, for details) so this |
0ce1b118 CV |
32425 | structure is of size 8 bytes. |
32426 | ||
32427 | @node Constants | |
32428 | @subsection Constants | |
32429 | @cindex constants, in file-i/o protocol | |
32430 | ||
32431 | The following values are used for the constants inside of the | |
fc320d37 | 32432 | protocol. @value{GDBN} and target are responsible for translating these |
0ce1b118 CV |
32433 | values before and after the call as needed. |
32434 | ||
32435 | @menu | |
79a6e687 BW |
32436 | * Open Flags:: |
32437 | * mode_t Values:: | |
32438 | * Errno Values:: | |
32439 | * Lseek Flags:: | |
0ce1b118 CV |
32440 | * Limits:: |
32441 | @end menu | |
32442 | ||
79a6e687 BW |
32443 | @node Open Flags |
32444 | @unnumberedsubsubsec Open Flags | |
0ce1b118 CV |
32445 | @cindex open flags, in file-i/o protocol |
32446 | ||
32447 | All values are given in hexadecimal representation. | |
32448 | ||
32449 | @smallexample | |
32450 | O_RDONLY 0x0 | |
32451 | O_WRONLY 0x1 | |
32452 | O_RDWR 0x2 | |
32453 | O_APPEND 0x8 | |
32454 | O_CREAT 0x200 | |
32455 | O_TRUNC 0x400 | |
32456 | O_EXCL 0x800 | |
32457 | @end smallexample | |
32458 | ||
79a6e687 BW |
32459 | @node mode_t Values |
32460 | @unnumberedsubsubsec mode_t Values | |
0ce1b118 CV |
32461 | @cindex mode_t values, in file-i/o protocol |
32462 | ||
32463 | All values are given in octal representation. | |
32464 | ||
32465 | @smallexample | |
32466 | S_IFREG 0100000 | |
32467 | S_IFDIR 040000 | |
32468 | S_IRUSR 0400 | |
32469 | S_IWUSR 0200 | |
32470 | S_IXUSR 0100 | |
32471 | S_IRGRP 040 | |
32472 | S_IWGRP 020 | |
32473 | S_IXGRP 010 | |
32474 | S_IROTH 04 | |
32475 | S_IWOTH 02 | |
32476 | S_IXOTH 01 | |
32477 | @end smallexample | |
32478 | ||
79a6e687 BW |
32479 | @node Errno Values |
32480 | @unnumberedsubsubsec Errno Values | |
0ce1b118 CV |
32481 | @cindex errno values, in file-i/o protocol |
32482 | ||
32483 | All values are given in decimal representation. | |
32484 | ||
32485 | @smallexample | |
32486 | EPERM 1 | |
32487 | ENOENT 2 | |
32488 | EINTR 4 | |
32489 | EBADF 9 | |
32490 | EACCES 13 | |
32491 | EFAULT 14 | |
32492 | EBUSY 16 | |
32493 | EEXIST 17 | |
32494 | ENODEV 19 | |
32495 | ENOTDIR 20 | |
32496 | EISDIR 21 | |
32497 | EINVAL 22 | |
32498 | ENFILE 23 | |
32499 | EMFILE 24 | |
32500 | EFBIG 27 | |
32501 | ENOSPC 28 | |
32502 | ESPIPE 29 | |
32503 | EROFS 30 | |
32504 | ENAMETOOLONG 91 | |
32505 | EUNKNOWN 9999 | |
32506 | @end smallexample | |
32507 | ||
fc320d37 | 32508 | @code{EUNKNOWN} is used as a fallback error value if a host system returns |
0ce1b118 CV |
32509 | any error value not in the list of supported error numbers. |
32510 | ||
79a6e687 BW |
32511 | @node Lseek Flags |
32512 | @unnumberedsubsubsec Lseek Flags | |
0ce1b118 CV |
32513 | @cindex lseek flags, in file-i/o protocol |
32514 | ||
32515 | @smallexample | |
32516 | SEEK_SET 0 | |
32517 | SEEK_CUR 1 | |
32518 | SEEK_END 2 | |
32519 | @end smallexample | |
32520 | ||
32521 | @node Limits | |
32522 | @unnumberedsubsubsec Limits | |
32523 | @cindex limits, in file-i/o protocol | |
32524 | ||
32525 | All values are given in decimal representation. | |
32526 | ||
32527 | @smallexample | |
32528 | INT_MIN -2147483648 | |
32529 | INT_MAX 2147483647 | |
32530 | UINT_MAX 4294967295 | |
32531 | LONG_MIN -9223372036854775808 | |
32532 | LONG_MAX 9223372036854775807 | |
32533 | ULONG_MAX 18446744073709551615 | |
32534 | @end smallexample | |
32535 | ||
32536 | @node File-I/O Examples | |
32537 | @subsection File-I/O Examples | |
32538 | @cindex file-i/o examples | |
32539 | ||
32540 | Example sequence of a write call, file descriptor 3, buffer is at target | |
32541 | address 0x1234, 6 bytes should be written: | |
32542 | ||
32543 | @smallexample | |
32544 | <- @code{Fwrite,3,1234,6} | |
32545 | @emph{request memory read from target} | |
32546 | -> @code{m1234,6} | |
32547 | <- XXXXXX | |
32548 | @emph{return "6 bytes written"} | |
32549 | -> @code{F6} | |
32550 | @end smallexample | |
32551 | ||
32552 | Example sequence of a read call, file descriptor 3, buffer is at target | |
32553 | address 0x1234, 6 bytes should be read: | |
32554 | ||
32555 | @smallexample | |
32556 | <- @code{Fread,3,1234,6} | |
32557 | @emph{request memory write to target} | |
32558 | -> @code{X1234,6:XXXXXX} | |
32559 | @emph{return "6 bytes read"} | |
32560 | -> @code{F6} | |
32561 | @end smallexample | |
32562 | ||
32563 | Example sequence of a read call, call fails on the host due to invalid | |
fc320d37 | 32564 | file descriptor (@code{EBADF}): |
0ce1b118 CV |
32565 | |
32566 | @smallexample | |
32567 | <- @code{Fread,3,1234,6} | |
32568 | -> @code{F-1,9} | |
32569 | @end smallexample | |
32570 | ||
c8aa23ab | 32571 | Example sequence of a read call, user presses @kbd{Ctrl-c} before syscall on |
0ce1b118 CV |
32572 | host is called: |
32573 | ||
32574 | @smallexample | |
32575 | <- @code{Fread,3,1234,6} | |
32576 | -> @code{F-1,4,C} | |
32577 | <- @code{T02} | |
32578 | @end smallexample | |
32579 | ||
c8aa23ab | 32580 | Example sequence of a read call, user presses @kbd{Ctrl-c} after syscall on |
0ce1b118 CV |
32581 | host is called: |
32582 | ||
32583 | @smallexample | |
32584 | <- @code{Fread,3,1234,6} | |
32585 | -> @code{X1234,6:XXXXXX} | |
32586 | <- @code{T02} | |
32587 | @end smallexample | |
32588 | ||
cfa9d6d9 DJ |
32589 | @node Library List Format |
32590 | @section Library List Format | |
32591 | @cindex library list format, remote protocol | |
32592 | ||
32593 | On some platforms, a dynamic loader (e.g.@: @file{ld.so}) runs in the | |
32594 | same process as your application to manage libraries. In this case, | |
32595 | @value{GDBN} can use the loader's symbol table and normal memory | |
32596 | operations to maintain a list of shared libraries. On other | |
32597 | platforms, the operating system manages loaded libraries. | |
32598 | @value{GDBN} can not retrieve the list of currently loaded libraries | |
32599 | through memory operations, so it uses the @samp{qXfer:libraries:read} | |
32600 | packet (@pxref{qXfer library list read}) instead. The remote stub | |
32601 | queries the target's operating system and reports which libraries | |
32602 | are loaded. | |
32603 | ||
32604 | The @samp{qXfer:libraries:read} packet returns an XML document which | |
32605 | lists loaded libraries and their offsets. Each library has an | |
1fddbabb PA |
32606 | associated name and one or more segment or section base addresses, |
32607 | which report where the library was loaded in memory. | |
32608 | ||
32609 | For the common case of libraries that are fully linked binaries, the | |
32610 | library should have a list of segments. If the target supports | |
32611 | dynamic linking of a relocatable object file, its library XML element | |
32612 | should instead include a list of allocated sections. The segment or | |
32613 | section bases are start addresses, not relocation offsets; they do not | |
32614 | depend on the library's link-time base addresses. | |
cfa9d6d9 | 32615 | |
9cceb671 DJ |
32616 | @value{GDBN} must be linked with the Expat library to support XML |
32617 | library lists. @xref{Expat}. | |
32618 | ||
cfa9d6d9 DJ |
32619 | A simple memory map, with one loaded library relocated by a single |
32620 | offset, looks like this: | |
32621 | ||
32622 | @smallexample | |
32623 | <library-list> | |
32624 | <library name="/lib/libc.so.6"> | |
32625 | <segment address="0x10000000"/> | |
32626 | </library> | |
32627 | </library-list> | |
32628 | @end smallexample | |
32629 | ||
1fddbabb PA |
32630 | Another simple memory map, with one loaded library with three |
32631 | allocated sections (.text, .data, .bss), looks like this: | |
32632 | ||
32633 | @smallexample | |
32634 | <library-list> | |
32635 | <library name="sharedlib.o"> | |
32636 | <section address="0x10000000"/> | |
32637 | <section address="0x20000000"/> | |
32638 | <section address="0x30000000"/> | |
32639 | </library> | |
32640 | </library-list> | |
32641 | @end smallexample | |
32642 | ||
cfa9d6d9 DJ |
32643 | The format of a library list is described by this DTD: |
32644 | ||
32645 | @smallexample | |
32646 | <!-- library-list: Root element with versioning --> | |
32647 | <!ELEMENT library-list (library)*> | |
32648 | <!ATTLIST library-list version CDATA #FIXED "1.0"> | |
1fddbabb | 32649 | <!ELEMENT library (segment*, section*)> |
cfa9d6d9 DJ |
32650 | <!ATTLIST library name CDATA #REQUIRED> |
32651 | <!ELEMENT segment EMPTY> | |
32652 | <!ATTLIST segment address CDATA #REQUIRED> | |
1fddbabb PA |
32653 | <!ELEMENT section EMPTY> |
32654 | <!ATTLIST section address CDATA #REQUIRED> | |
cfa9d6d9 DJ |
32655 | @end smallexample |
32656 | ||
1fddbabb PA |
32657 | In addition, segments and section descriptors cannot be mixed within a |
32658 | single library element, and you must supply at least one segment or | |
32659 | section for each library. | |
32660 | ||
79a6e687 BW |
32661 | @node Memory Map Format |
32662 | @section Memory Map Format | |
68437a39 DJ |
32663 | @cindex memory map format |
32664 | ||
32665 | To be able to write into flash memory, @value{GDBN} needs to obtain a | |
32666 | memory map from the target. This section describes the format of the | |
32667 | memory map. | |
32668 | ||
32669 | The memory map is obtained using the @samp{qXfer:memory-map:read} | |
32670 | (@pxref{qXfer memory map read}) packet and is an XML document that | |
9cceb671 DJ |
32671 | lists memory regions. |
32672 | ||
32673 | @value{GDBN} must be linked with the Expat library to support XML | |
32674 | memory maps. @xref{Expat}. | |
32675 | ||
32676 | The top-level structure of the document is shown below: | |
68437a39 DJ |
32677 | |
32678 | @smallexample | |
32679 | <?xml version="1.0"?> | |
32680 | <!DOCTYPE memory-map | |
32681 | PUBLIC "+//IDN gnu.org//DTD GDB Memory Map V1.0//EN" | |
32682 | "http://sourceware.org/gdb/gdb-memory-map.dtd"> | |
32683 | <memory-map> | |
32684 | region... | |
32685 | </memory-map> | |
32686 | @end smallexample | |
32687 | ||
32688 | Each region can be either: | |
32689 | ||
32690 | @itemize | |
32691 | ||
32692 | @item | |
32693 | A region of RAM starting at @var{addr} and extending for @var{length} | |
32694 | bytes from there: | |
32695 | ||
32696 | @smallexample | |
32697 | <memory type="ram" start="@var{addr}" length="@var{length}"/> | |
32698 | @end smallexample | |
32699 | ||
32700 | ||
32701 | @item | |
32702 | A region of read-only memory: | |
32703 | ||
32704 | @smallexample | |
32705 | <memory type="rom" start="@var{addr}" length="@var{length}"/> | |
32706 | @end smallexample | |
32707 | ||
32708 | ||
32709 | @item | |
32710 | A region of flash memory, with erasure blocks @var{blocksize} | |
32711 | bytes in length: | |
32712 | ||
32713 | @smallexample | |
32714 | <memory type="flash" start="@var{addr}" length="@var{length}"> | |
32715 | <property name="blocksize">@var{blocksize}</property> | |
32716 | </memory> | |
32717 | @end smallexample | |
32718 | ||
32719 | @end itemize | |
32720 | ||
32721 | Regions must not overlap. @value{GDBN} assumes that areas of memory not covered | |
32722 | by the memory map are RAM, and uses the ordinary @samp{M} and @samp{X} | |
32723 | packets to write to addresses in such ranges. | |
32724 | ||
32725 | The formal DTD for memory map format is given below: | |
32726 | ||
32727 | @smallexample | |
32728 | <!-- ................................................... --> | |
32729 | <!-- Memory Map XML DTD ................................ --> | |
32730 | <!-- File: memory-map.dtd .............................. --> | |
32731 | <!-- .................................... .............. --> | |
32732 | <!-- memory-map.dtd --> | |
32733 | <!-- memory-map: Root element with versioning --> | |
32734 | <!ELEMENT memory-map (memory | property)> | |
32735 | <!ATTLIST memory-map version CDATA #FIXED "1.0.0"> | |
32736 | <!ELEMENT memory (property)> | |
32737 | <!-- memory: Specifies a memory region, | |
32738 | and its type, or device. --> | |
32739 | <!ATTLIST memory type CDATA #REQUIRED | |
32740 | start CDATA #REQUIRED | |
32741 | length CDATA #REQUIRED | |
32742 | device CDATA #IMPLIED> | |
32743 | <!-- property: Generic attribute tag --> | |
32744 | <!ELEMENT property (#PCDATA | property)*> | |
32745 | <!ATTLIST property name CDATA #REQUIRED> | |
32746 | @end smallexample | |
32747 | ||
dc146f7c VP |
32748 | @node Thread List Format |
32749 | @section Thread List Format | |
32750 | @cindex thread list format | |
32751 | ||
32752 | To efficiently update the list of threads and their attributes, | |
32753 | @value{GDBN} issues the @samp{qXfer:threads:read} packet | |
32754 | (@pxref{qXfer threads read}) and obtains the XML document with | |
32755 | the following structure: | |
32756 | ||
32757 | @smallexample | |
32758 | <?xml version="1.0"?> | |
32759 | <threads> | |
32760 | <thread id="id" core="0"> | |
32761 | ... description ... | |
32762 | </thread> | |
32763 | </threads> | |
32764 | @end smallexample | |
32765 | ||
32766 | Each @samp{thread} element must have the @samp{id} attribute that | |
32767 | identifies the thread (@pxref{thread-id syntax}). The | |
32768 | @samp{core} attribute, if present, specifies which processor core | |
32769 | the thread was last executing on. The content of the of @samp{thread} | |
32770 | element is interpreted as human-readable auxilliary information. | |
32771 | ||
f418dd93 DJ |
32772 | @include agentexpr.texi |
32773 | ||
00bf0b85 SS |
32774 | @node Trace File Format |
32775 | @appendix Trace File Format | |
32776 | @cindex trace file format | |
32777 | ||
32778 | The trace file comes in three parts: a header, a textual description | |
32779 | section, and a trace frame section with binary data. | |
32780 | ||
32781 | The header has the form @code{\x7fTRACE0\n}. The first byte is | |
32782 | @code{0x7f} so as to indicate that the file contains binary data, | |
32783 | while the @code{0} is a version number that may have different values | |
32784 | in the future. | |
32785 | ||
32786 | The description section consists of multiple lines of @sc{ascii} text | |
32787 | separated by newline characters (@code{0xa}). The lines may include a | |
32788 | variety of optional descriptive or context-setting information, such | |
32789 | as tracepoint definitions or register set size. @value{GDBN} will | |
32790 | ignore any line that it does not recognize. An empty line marks the end | |
32791 | of this section. | |
32792 | ||
32793 | @c FIXME add some specific types of data | |
32794 | ||
32795 | The trace frame section consists of a number of consecutive frames. | |
32796 | Each frame begins with a two-byte tracepoint number, followed by a | |
32797 | four-byte size giving the amount of data in the frame. The data in | |
32798 | the frame consists of a number of blocks, each introduced by a | |
32799 | character indicating its type (at least register, memory, and trace | |
32800 | state variable). The data in this section is raw binary, not a | |
32801 | hexadecimal or other encoding; its endianness matches the target's | |
32802 | endianness. | |
32803 | ||
32804 | @c FIXME bi-arch may require endianness/arch info in description section | |
32805 | ||
32806 | @table @code | |
32807 | @item R @var{bytes} | |
32808 | Register block. The number and ordering of bytes matches that of a | |
32809 | @code{g} packet in the remote protocol. Note that these are the | |
32810 | actual bytes, in target order and @value{GDBN} register order, not a | |
32811 | hexadecimal encoding. | |
32812 | ||
32813 | @item M @var{address} @var{length} @var{bytes}... | |
32814 | Memory block. This is a contiguous block of memory, at the 8-byte | |
32815 | address @var{address}, with a 2-byte length @var{length}, followed by | |
32816 | @var{length} bytes. | |
32817 | ||
32818 | @item V @var{number} @var{value} | |
32819 | Trace state variable block. This records the 8-byte signed value | |
32820 | @var{value} of trace state variable numbered @var{number}. | |
32821 | ||
32822 | @end table | |
32823 | ||
32824 | Future enhancements of the trace file format may include additional types | |
32825 | of blocks. | |
32826 | ||
23181151 DJ |
32827 | @node Target Descriptions |
32828 | @appendix Target Descriptions | |
32829 | @cindex target descriptions | |
32830 | ||
32831 | @strong{Warning:} target descriptions are still under active development, | |
32832 | and the contents and format may change between @value{GDBN} releases. | |
32833 | The format is expected to stabilize in the future. | |
32834 | ||
32835 | One of the challenges of using @value{GDBN} to debug embedded systems | |
32836 | is that there are so many minor variants of each processor | |
32837 | architecture in use. It is common practice for vendors to start with | |
32838 | a standard processor core --- ARM, PowerPC, or MIPS, for example --- | |
32839 | and then make changes to adapt it to a particular market niche. Some | |
32840 | architectures have hundreds of variants, available from dozens of | |
32841 | vendors. This leads to a number of problems: | |
32842 | ||
32843 | @itemize @bullet | |
32844 | @item | |
32845 | With so many different customized processors, it is difficult for | |
32846 | the @value{GDBN} maintainers to keep up with the changes. | |
32847 | @item | |
32848 | Since individual variants may have short lifetimes or limited | |
32849 | audiences, it may not be worthwhile to carry information about every | |
32850 | variant in the @value{GDBN} source tree. | |
32851 | @item | |
32852 | When @value{GDBN} does support the architecture of the embedded system | |
32853 | at hand, the task of finding the correct architecture name to give the | |
32854 | @command{set architecture} command can be error-prone. | |
32855 | @end itemize | |
32856 | ||
32857 | To address these problems, the @value{GDBN} remote protocol allows a | |
32858 | target system to not only identify itself to @value{GDBN}, but to | |
32859 | actually describe its own features. This lets @value{GDBN} support | |
32860 | processor variants it has never seen before --- to the extent that the | |
32861 | descriptions are accurate, and that @value{GDBN} understands them. | |
32862 | ||
9cceb671 DJ |
32863 | @value{GDBN} must be linked with the Expat library to support XML |
32864 | target descriptions. @xref{Expat}. | |
123dc839 | 32865 | |
23181151 DJ |
32866 | @menu |
32867 | * Retrieving Descriptions:: How descriptions are fetched from a target. | |
32868 | * Target Description Format:: The contents of a target description. | |
123dc839 DJ |
32869 | * Predefined Target Types:: Standard types available for target |
32870 | descriptions. | |
32871 | * Standard Target Features:: Features @value{GDBN} knows about. | |
23181151 DJ |
32872 | @end menu |
32873 | ||
32874 | @node Retrieving Descriptions | |
32875 | @section Retrieving Descriptions | |
32876 | ||
32877 | Target descriptions can be read from the target automatically, or | |
32878 | specified by the user manually. The default behavior is to read the | |
32879 | description from the target. @value{GDBN} retrieves it via the remote | |
32880 | protocol using @samp{qXfer} requests (@pxref{General Query Packets, | |
32881 | qXfer}). The @var{annex} in the @samp{qXfer} packet will be | |
32882 | @samp{target.xml}. The contents of the @samp{target.xml} annex are an | |
32883 | XML document, of the form described in @ref{Target Description | |
32884 | Format}. | |
32885 | ||
32886 | Alternatively, you can specify a file to read for the target description. | |
32887 | If a file is set, the target will not be queried. The commands to | |
32888 | specify a file are: | |
32889 | ||
32890 | @table @code | |
32891 | @cindex set tdesc filename | |
32892 | @item set tdesc filename @var{path} | |
32893 | Read the target description from @var{path}. | |
32894 | ||
32895 | @cindex unset tdesc filename | |
32896 | @item unset tdesc filename | |
32897 | Do not read the XML target description from a file. @value{GDBN} | |
32898 | will use the description supplied by the current target. | |
32899 | ||
32900 | @cindex show tdesc filename | |
32901 | @item show tdesc filename | |
32902 | Show the filename to read for a target description, if any. | |
32903 | @end table | |
32904 | ||
32905 | ||
32906 | @node Target Description Format | |
32907 | @section Target Description Format | |
32908 | @cindex target descriptions, XML format | |
32909 | ||
32910 | A target description annex is an @uref{http://www.w3.org/XML/, XML} | |
32911 | document which complies with the Document Type Definition provided in | |
32912 | the @value{GDBN} sources in @file{gdb/features/gdb-target.dtd}. This | |
32913 | means you can use generally available tools like @command{xmllint} to | |
32914 | check that your feature descriptions are well-formed and valid. | |
32915 | However, to help people unfamiliar with XML write descriptions for | |
32916 | their targets, we also describe the grammar here. | |
32917 | ||
123dc839 DJ |
32918 | Target descriptions can identify the architecture of the remote target |
32919 | and (for some architectures) provide information about custom register | |
08d16641 PA |
32920 | sets. They can also identify the OS ABI of the remote target. |
32921 | @value{GDBN} can use this information to autoconfigure for your | |
123dc839 | 32922 | target, or to warn you if you connect to an unsupported target. |
23181151 DJ |
32923 | |
32924 | Here is a simple target description: | |
32925 | ||
123dc839 | 32926 | @smallexample |
1780a0ed | 32927 | <target version="1.0"> |
23181151 DJ |
32928 | <architecture>i386:x86-64</architecture> |
32929 | </target> | |
123dc839 | 32930 | @end smallexample |
23181151 DJ |
32931 | |
32932 | @noindent | |
32933 | This minimal description only says that the target uses | |
32934 | the x86-64 architecture. | |
32935 | ||
123dc839 DJ |
32936 | A target description has the following overall form, with [ ] marking |
32937 | optional elements and @dots{} marking repeatable elements. The elements | |
32938 | are explained further below. | |
23181151 | 32939 | |
123dc839 | 32940 | @smallexample |
23181151 DJ |
32941 | <?xml version="1.0"?> |
32942 | <!DOCTYPE target SYSTEM "gdb-target.dtd"> | |
1780a0ed | 32943 | <target version="1.0"> |
123dc839 | 32944 | @r{[}@var{architecture}@r{]} |
08d16641 | 32945 | @r{[}@var{osabi}@r{]} |
e35359c5 | 32946 | @r{[}@var{compatible}@r{]} |
123dc839 | 32947 | @r{[}@var{feature}@dots{}@r{]} |
23181151 | 32948 | </target> |
123dc839 | 32949 | @end smallexample |
23181151 DJ |
32950 | |
32951 | @noindent | |
32952 | The description is generally insensitive to whitespace and line | |
32953 | breaks, under the usual common-sense rules. The XML version | |
32954 | declaration and document type declaration can generally be omitted | |
32955 | (@value{GDBN} does not require them), but specifying them may be | |
1780a0ed DJ |
32956 | useful for XML validation tools. The @samp{version} attribute for |
32957 | @samp{<target>} may also be omitted, but we recommend | |
32958 | including it; if future versions of @value{GDBN} use an incompatible | |
32959 | revision of @file{gdb-target.dtd}, they will detect and report | |
32960 | the version mismatch. | |
23181151 | 32961 | |
108546a0 DJ |
32962 | @subsection Inclusion |
32963 | @cindex target descriptions, inclusion | |
32964 | @cindex XInclude | |
32965 | @ifnotinfo | |
32966 | @cindex <xi:include> | |
32967 | @end ifnotinfo | |
32968 | ||
32969 | It can sometimes be valuable to split a target description up into | |
32970 | several different annexes, either for organizational purposes, or to | |
32971 | share files between different possible target descriptions. You can | |
32972 | divide a description into multiple files by replacing any element of | |
32973 | the target description with an inclusion directive of the form: | |
32974 | ||
123dc839 | 32975 | @smallexample |
108546a0 | 32976 | <xi:include href="@var{document}"/> |
123dc839 | 32977 | @end smallexample |
108546a0 DJ |
32978 | |
32979 | @noindent | |
32980 | When @value{GDBN} encounters an element of this form, it will retrieve | |
32981 | the named XML @var{document}, and replace the inclusion directive with | |
32982 | the contents of that document. If the current description was read | |
32983 | using @samp{qXfer}, then so will be the included document; | |
32984 | @var{document} will be interpreted as the name of an annex. If the | |
32985 | current description was read from a file, @value{GDBN} will look for | |
32986 | @var{document} as a file in the same directory where it found the | |
32987 | original description. | |
32988 | ||
123dc839 DJ |
32989 | @subsection Architecture |
32990 | @cindex <architecture> | |
32991 | ||
32992 | An @samp{<architecture>} element has this form: | |
32993 | ||
32994 | @smallexample | |
32995 | <architecture>@var{arch}</architecture> | |
32996 | @end smallexample | |
32997 | ||
e35359c5 UW |
32998 | @var{arch} is one of the architectures from the set accepted by |
32999 | @code{set architecture} (@pxref{Targets, ,Specifying a Debugging Target}). | |
123dc839 | 33000 | |
08d16641 PA |
33001 | @subsection OS ABI |
33002 | @cindex @code{<osabi>} | |
33003 | ||
33004 | This optional field was introduced in @value{GDBN} version 7.0. | |
33005 | Previous versions of @value{GDBN} ignore it. | |
33006 | ||
33007 | An @samp{<osabi>} element has this form: | |
33008 | ||
33009 | @smallexample | |
33010 | <osabi>@var{abi-name}</osabi> | |
33011 | @end smallexample | |
33012 | ||
33013 | @var{abi-name} is an OS ABI name from the same selection accepted by | |
33014 | @w{@code{set osabi}} (@pxref{ABI, ,Configuring the Current ABI}). | |
33015 | ||
e35359c5 UW |
33016 | @subsection Compatible Architecture |
33017 | @cindex @code{<compatible>} | |
33018 | ||
33019 | This optional field was introduced in @value{GDBN} version 7.0. | |
33020 | Previous versions of @value{GDBN} ignore it. | |
33021 | ||
33022 | A @samp{<compatible>} element has this form: | |
33023 | ||
33024 | @smallexample | |
33025 | <compatible>@var{arch}</compatible> | |
33026 | @end smallexample | |
33027 | ||
33028 | @var{arch} is one of the architectures from the set accepted by | |
33029 | @code{set architecture} (@pxref{Targets, ,Specifying a Debugging Target}). | |
33030 | ||
33031 | A @samp{<compatible>} element is used to specify that the target | |
33032 | is able to run binaries in some other than the main target architecture | |
33033 | given by the @samp{<architecture>} element. For example, on the | |
33034 | Cell Broadband Engine, the main architecture is @code{powerpc:common} | |
33035 | or @code{powerpc:common64}, but the system is able to run binaries | |
33036 | in the @code{spu} architecture as well. The way to describe this | |
33037 | capability with @samp{<compatible>} is as follows: | |
33038 | ||
33039 | @smallexample | |
33040 | <architecture>powerpc:common</architecture> | |
33041 | <compatible>spu</compatible> | |
33042 | @end smallexample | |
33043 | ||
123dc839 DJ |
33044 | @subsection Features |
33045 | @cindex <feature> | |
33046 | ||
33047 | Each @samp{<feature>} describes some logical portion of the target | |
33048 | system. Features are currently used to describe available CPU | |
33049 | registers and the types of their contents. A @samp{<feature>} element | |
33050 | has this form: | |
33051 | ||
33052 | @smallexample | |
33053 | <feature name="@var{name}"> | |
33054 | @r{[}@var{type}@dots{}@r{]} | |
33055 | @var{reg}@dots{} | |
33056 | </feature> | |
33057 | @end smallexample | |
33058 | ||
33059 | @noindent | |
33060 | Each feature's name should be unique within the description. The name | |
33061 | of a feature does not matter unless @value{GDBN} has some special | |
33062 | knowledge of the contents of that feature; if it does, the feature | |
33063 | should have its standard name. @xref{Standard Target Features}. | |
33064 | ||
33065 | @subsection Types | |
33066 | ||
33067 | Any register's value is a collection of bits which @value{GDBN} must | |
33068 | interpret. The default interpretation is a two's complement integer, | |
33069 | but other types can be requested by name in the register description. | |
33070 | Some predefined types are provided by @value{GDBN} (@pxref{Predefined | |
33071 | Target Types}), and the description can define additional composite types. | |
33072 | ||
33073 | Each type element must have an @samp{id} attribute, which gives | |
33074 | a unique (within the containing @samp{<feature>}) name to the type. | |
33075 | Types must be defined before they are used. | |
33076 | ||
33077 | @cindex <vector> | |
33078 | Some targets offer vector registers, which can be treated as arrays | |
33079 | of scalar elements. These types are written as @samp{<vector>} elements, | |
33080 | specifying the array element type, @var{type}, and the number of elements, | |
33081 | @var{count}: | |
33082 | ||
33083 | @smallexample | |
33084 | <vector id="@var{id}" type="@var{type}" count="@var{count}"/> | |
33085 | @end smallexample | |
33086 | ||
33087 | @cindex <union> | |
33088 | If a register's value is usefully viewed in multiple ways, define it | |
33089 | with a union type containing the useful representations. The | |
33090 | @samp{<union>} element contains one or more @samp{<field>} elements, | |
33091 | each of which has a @var{name} and a @var{type}: | |
33092 | ||
33093 | @smallexample | |
33094 | <union id="@var{id}"> | |
33095 | <field name="@var{name}" type="@var{type}"/> | |
33096 | @dots{} | |
33097 | </union> | |
33098 | @end smallexample | |
33099 | ||
f5dff777 DJ |
33100 | @cindex <struct> |
33101 | If a register's value is composed from several separate values, define | |
33102 | it with a structure type. There are two forms of the @samp{<struct>} | |
33103 | element; a @samp{<struct>} element must either contain only bitfields | |
33104 | or contain no bitfields. If the structure contains only bitfields, | |
33105 | its total size in bytes must be specified, each bitfield must have an | |
33106 | explicit start and end, and bitfields are automatically assigned an | |
33107 | integer type. The field's @var{start} should be less than or | |
33108 | equal to its @var{end}, and zero represents the least significant bit. | |
33109 | ||
33110 | @smallexample | |
33111 | <struct id="@var{id}" size="@var{size}"> | |
33112 | <field name="@var{name}" start="@var{start}" end="@var{end}"/> | |
33113 | @dots{} | |
33114 | </struct> | |
33115 | @end smallexample | |
33116 | ||
33117 | If the structure contains no bitfields, then each field has an | |
33118 | explicit type, and no implicit padding is added. | |
33119 | ||
33120 | @smallexample | |
33121 | <struct id="@var{id}"> | |
33122 | <field name="@var{name}" type="@var{type}"/> | |
33123 | @dots{} | |
33124 | </struct> | |
33125 | @end smallexample | |
33126 | ||
33127 | @cindex <flags> | |
33128 | If a register's value is a series of single-bit flags, define it with | |
33129 | a flags type. The @samp{<flags>} element has an explicit @var{size} | |
33130 | and contains one or more @samp{<field>} elements. Each field has a | |
33131 | @var{name}, a @var{start}, and an @var{end}. Only single-bit flags | |
33132 | are supported. | |
33133 | ||
33134 | @smallexample | |
33135 | <flags id="@var{id}" size="@var{size}"> | |
33136 | <field name="@var{name}" start="@var{start}" end="@var{end}"/> | |
33137 | @dots{} | |
33138 | </flags> | |
33139 | @end smallexample | |
33140 | ||
123dc839 DJ |
33141 | @subsection Registers |
33142 | @cindex <reg> | |
33143 | ||
33144 | Each register is represented as an element with this form: | |
33145 | ||
33146 | @smallexample | |
33147 | <reg name="@var{name}" | |
33148 | bitsize="@var{size}" | |
33149 | @r{[}regnum="@var{num}"@r{]} | |
33150 | @r{[}save-restore="@var{save-restore}"@r{]} | |
33151 | @r{[}type="@var{type}"@r{]} | |
33152 | @r{[}group="@var{group}"@r{]}/> | |
33153 | @end smallexample | |
33154 | ||
33155 | @noindent | |
33156 | The components are as follows: | |
33157 | ||
33158 | @table @var | |
33159 | ||
33160 | @item name | |
33161 | The register's name; it must be unique within the target description. | |
33162 | ||
33163 | @item bitsize | |
33164 | The register's size, in bits. | |
33165 | ||
33166 | @item regnum | |
33167 | The register's number. If omitted, a register's number is one greater | |
33168 | than that of the previous register (either in the current feature or in | |
33169 | a preceeding feature); the first register in the target description | |
33170 | defaults to zero. This register number is used to read or write | |
33171 | the register; e.g.@: it is used in the remote @code{p} and @code{P} | |
33172 | packets, and registers appear in the @code{g} and @code{G} packets | |
33173 | in order of increasing register number. | |
33174 | ||
33175 | @item save-restore | |
33176 | Whether the register should be preserved across inferior function | |
33177 | calls; this must be either @code{yes} or @code{no}. The default is | |
33178 | @code{yes}, which is appropriate for most registers except for | |
33179 | some system control registers; this is not related to the target's | |
33180 | ABI. | |
33181 | ||
33182 | @item type | |
33183 | The type of the register. @var{type} may be a predefined type, a type | |
33184 | defined in the current feature, or one of the special types @code{int} | |
33185 | and @code{float}. @code{int} is an integer type of the correct size | |
33186 | for @var{bitsize}, and @code{float} is a floating point type (in the | |
33187 | architecture's normal floating point format) of the correct size for | |
33188 | @var{bitsize}. The default is @code{int}. | |
33189 | ||
33190 | @item group | |
33191 | The register group to which this register belongs. @var{group} must | |
33192 | be either @code{general}, @code{float}, or @code{vector}. If no | |
33193 | @var{group} is specified, @value{GDBN} will not display the register | |
33194 | in @code{info registers}. | |
33195 | ||
33196 | @end table | |
33197 | ||
33198 | @node Predefined Target Types | |
33199 | @section Predefined Target Types | |
33200 | @cindex target descriptions, predefined types | |
33201 | ||
33202 | Type definitions in the self-description can build up composite types | |
33203 | from basic building blocks, but can not define fundamental types. Instead, | |
33204 | standard identifiers are provided by @value{GDBN} for the fundamental | |
33205 | types. The currently supported types are: | |
33206 | ||
33207 | @table @code | |
33208 | ||
33209 | @item int8 | |
33210 | @itemx int16 | |
33211 | @itemx int32 | |
33212 | @itemx int64 | |
7cc46491 | 33213 | @itemx int128 |
123dc839 DJ |
33214 | Signed integer types holding the specified number of bits. |
33215 | ||
33216 | @item uint8 | |
33217 | @itemx uint16 | |
33218 | @itemx uint32 | |
33219 | @itemx uint64 | |
7cc46491 | 33220 | @itemx uint128 |
123dc839 DJ |
33221 | Unsigned integer types holding the specified number of bits. |
33222 | ||
33223 | @item code_ptr | |
33224 | @itemx data_ptr | |
33225 | Pointers to unspecified code and data. The program counter and | |
33226 | any dedicated return address register may be marked as code | |
33227 | pointers; printing a code pointer converts it into a symbolic | |
33228 | address. The stack pointer and any dedicated address registers | |
33229 | may be marked as data pointers. | |
33230 | ||
6e3bbd1a PB |
33231 | @item ieee_single |
33232 | Single precision IEEE floating point. | |
33233 | ||
33234 | @item ieee_double | |
33235 | Double precision IEEE floating point. | |
33236 | ||
123dc839 DJ |
33237 | @item arm_fpa_ext |
33238 | The 12-byte extended precision format used by ARM FPA registers. | |
33239 | ||
075b51b7 L |
33240 | @item i387_ext |
33241 | The 10-byte extended precision format used by x87 registers. | |
33242 | ||
33243 | @item i386_eflags | |
33244 | 32bit @sc{eflags} register used by x86. | |
33245 | ||
33246 | @item i386_mxcsr | |
33247 | 32bit @sc{mxcsr} register used by x86. | |
33248 | ||
123dc839 DJ |
33249 | @end table |
33250 | ||
33251 | @node Standard Target Features | |
33252 | @section Standard Target Features | |
33253 | @cindex target descriptions, standard features | |
33254 | ||
33255 | A target description must contain either no registers or all the | |
33256 | target's registers. If the description contains no registers, then | |
33257 | @value{GDBN} will assume a default register layout, selected based on | |
33258 | the architecture. If the description contains any registers, the | |
33259 | default layout will not be used; the standard registers must be | |
33260 | described in the target description, in such a way that @value{GDBN} | |
33261 | can recognize them. | |
33262 | ||
33263 | This is accomplished by giving specific names to feature elements | |
33264 | which contain standard registers. @value{GDBN} will look for features | |
33265 | with those names and verify that they contain the expected registers; | |
33266 | if any known feature is missing required registers, or if any required | |
33267 | feature is missing, @value{GDBN} will reject the target | |
33268 | description. You can add additional registers to any of the | |
33269 | standard features --- @value{GDBN} will display them just as if | |
33270 | they were added to an unrecognized feature. | |
33271 | ||
33272 | This section lists the known features and their expected contents. | |
33273 | Sample XML documents for these features are included in the | |
33274 | @value{GDBN} source tree, in the directory @file{gdb/features}. | |
33275 | ||
33276 | Names recognized by @value{GDBN} should include the name of the | |
33277 | company or organization which selected the name, and the overall | |
33278 | architecture to which the feature applies; so e.g.@: the feature | |
33279 | containing ARM core registers is named @samp{org.gnu.gdb.arm.core}. | |
33280 | ||
ff6f572f DJ |
33281 | The names of registers are not case sensitive for the purpose |
33282 | of recognizing standard features, but @value{GDBN} will only display | |
33283 | registers using the capitalization used in the description. | |
33284 | ||
e9c17194 VP |
33285 | @menu |
33286 | * ARM Features:: | |
3bb8d5c3 | 33287 | * i386 Features:: |
1e26b4f8 | 33288 | * MIPS Features:: |
e9c17194 | 33289 | * M68K Features:: |
1e26b4f8 | 33290 | * PowerPC Features:: |
e9c17194 VP |
33291 | @end menu |
33292 | ||
33293 | ||
33294 | @node ARM Features | |
123dc839 DJ |
33295 | @subsection ARM Features |
33296 | @cindex target descriptions, ARM features | |
33297 | ||
33298 | The @samp{org.gnu.gdb.arm.core} feature is required for ARM targets. | |
33299 | It should contain registers @samp{r0} through @samp{r13}, @samp{sp}, | |
33300 | @samp{lr}, @samp{pc}, and @samp{cpsr}. | |
33301 | ||
33302 | The @samp{org.gnu.gdb.arm.fpa} feature is optional. If present, it | |
33303 | should contain registers @samp{f0} through @samp{f7} and @samp{fps}. | |
33304 | ||
ff6f572f DJ |
33305 | The @samp{org.gnu.gdb.xscale.iwmmxt} feature is optional. If present, |
33306 | it should contain at least registers @samp{wR0} through @samp{wR15} and | |
33307 | @samp{wCGR0} through @samp{wCGR3}. The @samp{wCID}, @samp{wCon}, | |
33308 | @samp{wCSSF}, and @samp{wCASF} registers are optional. | |
23181151 | 33309 | |
58d6951d DJ |
33310 | The @samp{org.gnu.gdb.arm.vfp} feature is optional. If present, it |
33311 | should contain at least registers @samp{d0} through @samp{d15}. If | |
33312 | they are present, @samp{d16} through @samp{d31} should also be included. | |
33313 | @value{GDBN} will synthesize the single-precision registers from | |
33314 | halves of the double-precision registers. | |
33315 | ||
33316 | The @samp{org.gnu.gdb.arm.neon} feature is optional. It does not | |
33317 | need to contain registers; it instructs @value{GDBN} to display the | |
33318 | VFP double-precision registers as vectors and to synthesize the | |
33319 | quad-precision registers from pairs of double-precision registers. | |
33320 | If this feature is present, @samp{org.gnu.gdb.arm.vfp} must also | |
33321 | be present and include 32 double-precision registers. | |
33322 | ||
3bb8d5c3 L |
33323 | @node i386 Features |
33324 | @subsection i386 Features | |
33325 | @cindex target descriptions, i386 features | |
33326 | ||
33327 | The @samp{org.gnu.gdb.i386.core} feature is required for i386/amd64 | |
33328 | targets. It should describe the following registers: | |
33329 | ||
33330 | @itemize @minus | |
33331 | @item | |
33332 | @samp{eax} through @samp{edi} plus @samp{eip} for i386 | |
33333 | @item | |
33334 | @samp{rax} through @samp{r15} plus @samp{rip} for amd64 | |
33335 | @item | |
33336 | @samp{eflags}, @samp{cs}, @samp{ss}, @samp{ds}, @samp{es}, | |
33337 | @samp{fs}, @samp{gs} | |
33338 | @item | |
33339 | @samp{st0} through @samp{st7} | |
33340 | @item | |
33341 | @samp{fctrl}, @samp{fstat}, @samp{ftag}, @samp{fiseg}, @samp{fioff}, | |
33342 | @samp{foseg}, @samp{fooff} and @samp{fop} | |
33343 | @end itemize | |
33344 | ||
33345 | The register sets may be different, depending on the target. | |
33346 | ||
33347 | The @samp{org.gnu.gdb.i386.sse} feature is required. It should | |
33348 | describe registers: | |
33349 | ||
33350 | @itemize @minus | |
33351 | @item | |
33352 | @samp{xmm0} through @samp{xmm7} for i386 | |
33353 | @item | |
33354 | @samp{xmm0} through @samp{xmm15} for amd64 | |
33355 | @item | |
33356 | @samp{mxcsr} | |
33357 | @end itemize | |
33358 | ||
33359 | The @samp{org.gnu.gdb.i386.linux} feature is optional. It should | |
33360 | describe a single register, @samp{orig_eax}. | |
33361 | ||
1e26b4f8 | 33362 | @node MIPS Features |
f8b73d13 DJ |
33363 | @subsection MIPS Features |
33364 | @cindex target descriptions, MIPS features | |
33365 | ||
33366 | The @samp{org.gnu.gdb.mips.cpu} feature is required for MIPS targets. | |
33367 | It should contain registers @samp{r0} through @samp{r31}, @samp{lo}, | |
33368 | @samp{hi}, and @samp{pc}. They may be 32-bit or 64-bit depending | |
33369 | on the target. | |
33370 | ||
33371 | The @samp{org.gnu.gdb.mips.cp0} feature is also required. It should | |
33372 | contain at least the @samp{status}, @samp{badvaddr}, and @samp{cause} | |
33373 | registers. They may be 32-bit or 64-bit depending on the target. | |
33374 | ||
33375 | The @samp{org.gnu.gdb.mips.fpu} feature is currently required, though | |
33376 | it may be optional in a future version of @value{GDBN}. It should | |
33377 | contain registers @samp{f0} through @samp{f31}, @samp{fcsr}, and | |
33378 | @samp{fir}. They may be 32-bit or 64-bit depending on the target. | |
33379 | ||
822b6570 DJ |
33380 | The @samp{org.gnu.gdb.mips.linux} feature is optional. It should |
33381 | contain a single register, @samp{restart}, which is used by the | |
33382 | Linux kernel to control restartable syscalls. | |
33383 | ||
e9c17194 VP |
33384 | @node M68K Features |
33385 | @subsection M68K Features | |
33386 | @cindex target descriptions, M68K features | |
33387 | ||
33388 | @table @code | |
33389 | @item @samp{org.gnu.gdb.m68k.core} | |
33390 | @itemx @samp{org.gnu.gdb.coldfire.core} | |
33391 | @itemx @samp{org.gnu.gdb.fido.core} | |
33392 | One of those features must be always present. | |
249e1128 | 33393 | The feature that is present determines which flavor of m68k is |
e9c17194 VP |
33394 | used. The feature that is present should contain registers |
33395 | @samp{d0} through @samp{d7}, @samp{a0} through @samp{a5}, @samp{fp}, | |
33396 | @samp{sp}, @samp{ps} and @samp{pc}. | |
33397 | ||
33398 | @item @samp{org.gnu.gdb.coldfire.fp} | |
33399 | This feature is optional. If present, it should contain registers | |
33400 | @samp{fp0} through @samp{fp7}, @samp{fpcontrol}, @samp{fpstatus} and | |
33401 | @samp{fpiaddr}. | |
33402 | @end table | |
33403 | ||
1e26b4f8 | 33404 | @node PowerPC Features |
7cc46491 DJ |
33405 | @subsection PowerPC Features |
33406 | @cindex target descriptions, PowerPC features | |
33407 | ||
33408 | The @samp{org.gnu.gdb.power.core} feature is required for PowerPC | |
33409 | targets. It should contain registers @samp{r0} through @samp{r31}, | |
33410 | @samp{pc}, @samp{msr}, @samp{cr}, @samp{lr}, @samp{ctr}, and | |
33411 | @samp{xer}. They may be 32-bit or 64-bit depending on the target. | |
33412 | ||
33413 | The @samp{org.gnu.gdb.power.fpu} feature is optional. It should | |
33414 | contain registers @samp{f0} through @samp{f31} and @samp{fpscr}. | |
33415 | ||
33416 | The @samp{org.gnu.gdb.power.altivec} feature is optional. It should | |
33417 | contain registers @samp{vr0} through @samp{vr31}, @samp{vscr}, | |
33418 | and @samp{vrsave}. | |
33419 | ||
677c5bb1 LM |
33420 | The @samp{org.gnu.gdb.power.vsx} feature is optional. It should |
33421 | contain registers @samp{vs0h} through @samp{vs31h}. @value{GDBN} | |
33422 | will combine these registers with the floating point registers | |
33423 | (@samp{f0} through @samp{f31}) and the altivec registers (@samp{vr0} | |
aeac0ff9 | 33424 | through @samp{vr31}) to present the 128-bit wide registers @samp{vs0} |
677c5bb1 LM |
33425 | through @samp{vs63}, the set of vector registers for POWER7. |
33426 | ||
7cc46491 DJ |
33427 | The @samp{org.gnu.gdb.power.spe} feature is optional. It should |
33428 | contain registers @samp{ev0h} through @samp{ev31h}, @samp{acc}, and | |
33429 | @samp{spefscr}. SPE targets should provide 32-bit registers in | |
33430 | @samp{org.gnu.gdb.power.core} and provide the upper halves in | |
33431 | @samp{ev0h} through @samp{ev31h}. @value{GDBN} will combine | |
33432 | these to present registers @samp{ev0} through @samp{ev31} to the | |
33433 | user. | |
33434 | ||
07e059b5 VP |
33435 | @node Operating System Information |
33436 | @appendix Operating System Information | |
33437 | @cindex operating system information | |
33438 | ||
33439 | @menu | |
33440 | * Process list:: | |
33441 | @end menu | |
33442 | ||
33443 | Users of @value{GDBN} often wish to obtain information about the state of | |
33444 | the operating system running on the target---for example the list of | |
33445 | processes, or the list of open files. This section describes the | |
33446 | mechanism that makes it possible. This mechanism is similar to the | |
33447 | target features mechanism (@pxref{Target Descriptions}), but focuses | |
33448 | on a different aspect of target. | |
33449 | ||
33450 | Operating system information is retrived from the target via the | |
33451 | remote protocol, using @samp{qXfer} requests (@pxref{qXfer osdata | |
33452 | read}). The object name in the request should be @samp{osdata}, and | |
33453 | the @var{annex} identifies the data to be fetched. | |
33454 | ||
33455 | @node Process list | |
33456 | @appendixsection Process list | |
33457 | @cindex operating system information, process list | |
33458 | ||
33459 | When requesting the process list, the @var{annex} field in the | |
33460 | @samp{qXfer} request should be @samp{processes}. The returned data is | |
33461 | an XML document. The formal syntax of this document is defined in | |
33462 | @file{gdb/features/osdata.dtd}. | |
33463 | ||
33464 | An example document is: | |
33465 | ||
33466 | @smallexample | |
33467 | <?xml version="1.0"?> | |
33468 | <!DOCTYPE target SYSTEM "osdata.dtd"> | |
33469 | <osdata type="processes"> | |
33470 | <item> | |
33471 | <column name="pid">1</column> | |
33472 | <column name="user">root</column> | |
33473 | <column name="command">/sbin/init</column> | |
dc146f7c | 33474 | <column name="cores">1,2,3</column> |
07e059b5 VP |
33475 | </item> |
33476 | </osdata> | |
33477 | @end smallexample | |
33478 | ||
33479 | Each item should include a column whose name is @samp{pid}. The value | |
33480 | of that column should identify the process on the target. The | |
33481 | @samp{user} and @samp{command} columns are optional, and will be | |
dc146f7c VP |
33482 | displayed by @value{GDBN}. The @samp{cores} column, if present, |
33483 | should contain a comma-separated list of cores that this process | |
33484 | is running on. Target may provide additional columns, | |
07e059b5 VP |
33485 | which @value{GDBN} currently ignores. |
33486 | ||
aab4e0ec | 33487 | @include gpl.texi |
eb12ee30 | 33488 | |
2154891a | 33489 | @raisesections |
6826cf00 | 33490 | @include fdl.texi |
2154891a | 33491 | @lowersections |
6826cf00 | 33492 | |
6d2ebf8b | 33493 | @node Index |
c906108c SS |
33494 | @unnumbered Index |
33495 | ||
33496 | @printindex cp | |
33497 | ||
33498 | @tex | |
33499 | % I think something like @colophon should be in texinfo. In the | |
33500 | % meantime: | |
33501 | \long\def\colophon{\hbox to0pt{}\vfill | |
33502 | \centerline{The body of this manual is set in} | |
33503 | \centerline{\fontname\tenrm,} | |
33504 | \centerline{with headings in {\bf\fontname\tenbf}} | |
33505 | \centerline{and examples in {\tt\fontname\tentt}.} | |
33506 | \centerline{{\it\fontname\tenit\/},} | |
33507 | \centerline{{\bf\fontname\tenbf}, and} | |
33508 | \centerline{{\sl\fontname\tensl\/}} | |
33509 | \centerline{are used for emphasis.}\vfill} | |
33510 | \page\colophon | |
33511 | % Blame: doc@cygnus.com, 1991. | |
33512 | @end tex | |
33513 | ||
c906108c | 33514 | @bye |